Related
After i hang up on a call (when the phone is in sleep mode and the screen is locked) the screen unlocks. this is quite contrary to what is mentioned in the phone manual chapter 1 page 45. this becomes an issue since i use a bluetooth headset and the phone remains in its sleeve/case and after every call, a whole bunch of applications will launch since the case is in contact with the screen. have i overlooked some settings or are there other owners who have faced this issue?
ideas and suggestions welcomed
did you check it out if any of the hardware buttons being pressed against the case hence wakening up the phone.?
i had it to only closed al my apps in taskm and it stoped flickering
My HD2 is also behaving in the same way even in controlled test conditions - the phone unlocks when a call comes in (I'm presented with slide to accept or reject call) The phone unlocks during the call, but fails to lock again on disconnect (either by pressing "end call" or hang up via bluetooth).
Can anyone verify this? Is it interacting with something I installed?
I believe I found a (complicated) workaround.
What I want: leave HD2 inside pocket, answer calls with bluetooth headset, hang up and phone will go back to lock.
Problem: After I hang up using bluetooth or press the big red "End Call" button or the other party hangs up, the phone stays unlocked! It stays powered on and all kinds of buttons gets clicked.
Practically all lock sw uses their own lock screen (which I don't want to install). CSDevCtrl does not trigger by phone. TouchLockPro uses its own transparent lock screen but can respond to phone events. Using the !SUSPEND for TAPI\Ended under settings does not seem to work when the screen dims about 50 secs into the call.
Solution: Use TouchLockPro together with LockAndOff. Get TAPI\Ended to run LockAndOff will turn phone off, whether by bluetooth, big red "End Call" button, or the other party hangs up.
BTW: I think there is some confusion on whether the phone locks when you
1. press the big red "End Call" button, or
2. the hard "End call" button
in the forums.
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
linivan said:
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
Click to expand...
Click to collapse
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
johncmolyneux said:
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
Click to expand...
Click to collapse
My proximity sensor does not work, when I am getting a call my screen turn off and when I am taking the phone out from my face it turn on only when I am out side at the sun!! the screen stay off when I am inside room. I tested it with flsh light and it is working also.
I have a T-Mobile US version of the HD2. I am having the same problem when using the bluetooth system in my car. After answering or making a call the phone stay unlocked. And then starts making random calls while I am driving!!!!
There has got to be an easy fix for this!!!
Buy pocketshield, problem solved.
i have this unlock problem with 1.48 rom and i solve it by pressing start button and lock. after that everything works fine unless i change theme in settings. then just repeat first step.
Solved
Same trouble with me until I use the following software. I tried it and it's almost perfect. unzip it and just copy to your HD2, run CallerLoc.exe and click Yes, you'll find:when you hang up, or he/she hang up a call, or a call is established, the screen will turn off.
Why say 'almost perfect', the software is in chinese, but the filename is in english. and it's a call location software but with the function we need.
To stop or before you delete the software, run Callerloc.exe and click Yes again.
Hope this will help you. Sorry I don't find a English version of this software. I esure and I'm using this software perfectlly with my Leo.
theciscokid said:
Buy pocketshield, problem solved.
Click to expand...
Click to collapse
Same for me
Greetings.
I understand this is quite an old thread I'm digging up but I need a little help as well and I didn't want to start a new topic just for that.
I've this silly problem, appeared right out of the blue:
You all know the standard manila behavior, when the phone is idle, the screen first dims and after some more time, depending on your preferences, the screen locks. It also locks if you press the power off button. This all was happening to me till this morning.
I added an event in the calendar (the only change I made today) and after that, my phone dims and then goes in sleep mode after the designated period of time, but DOESN'T lock!!! It doesn't even lock when I press the power off button. I can still lock it by pressing Start and then lock or by press and hold the power button and choose the lock phone option. So one would say that it's still operational, so why bother about it, but I kinda liked the standard function and I have to freaking idea why it changed!!!
I'd be most appreciative if you could offer some help with that.
Oh, I forgot to mention. Soft reset didn't solve the problem. Erasing the calendar event didn't either.
My phone runs the factory ROM (1.66.482.1 ELL), I haven't changed anything other than user settings (yeah, I'm a noob... )
Thanks in advance!
Nasos
Pocketshield could be the end of your problems. You can try it for 10 days and see how it goes...
But why do I need to buy third party software in order to revert my phone to it's original operation?
No, this is not the answer I am looking for. I was wondering if you know of any kind of settings that might have changed by accident and caused this undesired behavior.
Thanks.
The best to return to normal operation would be a hard reset. Or you can spend a while trying.
You can try
HKLM\Software\Microsoft\Shell\Lockscreen\Enable=1
HKLM\Software\Microsoft\Shell\Lockscreen\Active=1
Thank you very much. I opted for the hard reset option... I hope it stays ok this time!
My HD2 also had some strange unlocking and unwanted calling.
I noticed it appeared when using the android style lockscreen.
When I changed back to the original one, problem solved
i had this too. the andriod lockscreen seems to be a bit buggy last time i used it, i accidentially called 7 random numbers
so I just noticed the lights for my hardware buttons are stuck on, happens from the moment the phone turns on, and nothing changes it (though they seem to dim slightly) I've tried reflashing the phone (using mdj cyanogen 2.7, nand with magldr 1.12)
I tried searching and havent seen anything like this. Only thing I can think is maybe it got a little wet(?) while I was recording video during a snow storm here, but nothing else seemed wrong, just got home and noticed it. Any ideas?
I have the exact same problem. I've flashed back to the original windows mobile rom and the problem is still there! I've searched and yet to find the solution. Anyone got any ideas?
Check to see if you have a voicemail - you may have read it but closed VM before listening to all the message, it can on occasions do this - it I'm right just ring your phone leave a fresh VM then go into VM and listen to the whole message
Thanks for the reply, but no dice on this one. I tried the voicemail thing and I have no voicemails.
To clarify it's the bottom 5 buttons (call, home, windows, back and power) that are constantly lit up. Even when the phone goes on standby those buttons stay lit. I'm looking to see if there's an app that can just shut them off.
I got the same problem. My hd2 got some water on it and the problem started. The hardware keys now getting dim but not getting completely off. There is no other problem
Please help.
same problem on my father htc click
Ok guys try the bottom of post 4 here:
http://forum.xda-developers.com/showthread.php?t=926507
I use that rom (the 1.7) version and the fix works
johnerz said:
Ok guys try the bottom of post 4 here:
http://forum.xda-developers.com/showthread.php?t=926507
I use that rom (the 1.7) version and the fix works
Click to expand...
Click to collapse
Thanks, I will try the rom.
But do u really think its a rom problem ? The keys light were working fine before the water hazard in the same existing rom. Besides the problem is also there when u are in the boot menu of MAGLDR or Clockwork menu.
any updates from anyone? On miy HD2 the vol up, start, back & end call key don't respond to any presses but seem to be active. Calls will randomly end, vol up acts as if the button is kept pressed!
Help!
Hi guys,
A little bump in this thread, but is there already found a solution for this problem?
After a hard reset and replacing the digitizer of my htc HD2, the buttonlights remain on. Even when the phone gets in standby mode.
I'm using cyanogenmod 7. (bought it like this. Didn't put android on it myself)
After the hard reset and digitizer replacement there also came another problem.
When pushing the windows logo (key 158) the volume up button also reacts (key 115). Thesame problem occurs when pushing the dial button. With that key (231), key 114 (volume down) reacts.
So when i want to open a menu or make a call the volume goes up or down.
Do you guys think I screwed something up when replacing my digitizer or is it just an software issue caused by the hard reset?
All right guys, it was an hardware failure.
I reopened my htc and checked all the connectors and (re)placed some of the yellow tape. After the reassembly, my phone just works as it should. All problems are solved.
My HTC HD2 also got the keys stuck after only a week of use. T-Mobile is sending me a replacement phone today.
Is this a common problem? I'm afraid it may happen again.
Hey guys I'm having same issue. Going to try opening up and check connectors.
Okay I wasnt going to post about this cause there have been way too many posts and alot of back and forth and debates and even flaming, but I stumbled across something that I think is the cause for MAJORITY of the issues with why we keep having this happen. It Happened to me Today, and I Found the cause.
Before ANYONE Flames me for bringing this up, READ the post, Remember I solved the cause of why it happens to most of us, I dont take responsibility if you choose to take it upon yourself to fix it! And I know 90% of the users are going to tell me I'm wrong or I dont know what I am talking about, so be it.
If you have nothing to add other then flaming the post, just hit the back button and be on your merry way and pretend you never saw it. But I am 98% sure I am right about why its happening!
So if your interested read on:
I actually for the first time had this, and I know this is going to get flamed but its not the Screen thats the problem. And I think (BIG IF) that the dreaded unresponsive screen issue that we keep reading about Majority of them I think is not the screen.
I have 2 HD2s and both have worked flawlessly without any problems, but today I was playing with my test phone that doesnt get used that much and I noticed after installing a new rom that my screen after I played with it for a bit went black (sleep) and when I woke it up it wouldnt respond, first thing that crossed my mind is I just lost my digitizier, and started wondering okay why, I went as far to re-flash WinMo stock HD2 rom, same issue, so I decided its time to find out exactly whats causing this, and I found it. I wasnt going to make a post again cause I figured people would be "Not another thread about this" but I know whats causing the screen issue, at least this is my suspicision and I have temporarily fixed mine.
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
I completely agree with you. I've had the "dead digitizer" since December. It was pretty apparent it was a hardware key problem, as I could generally solve the issue by pressing the "Off" button to turn the screen off, and then one of the other keys (usually the back button, but occasionally one of the others) to wake the screen up, and the digitizer would be alive again.
As I am still under warranty, I sent mine off last week, and expect to hear back within a few days. But if I had the confidence to open it myself, I was sure it would be fixed with a good clean.
Anyway, thanks for crystallizing all this into a post. Thanked!
THANK YOU SO MUCH FOR THE INFO. i have had so much trouble with unresponsive screen after installing typhoon 2.6.3 and it from holding down the red button all the time for install and the past millions times for everything else.
Thanks for the heads up
Sent from my HD2 using XDA App
U maybe be right about why this issue happens but if u rely on other key then will also wear out soon ...
What I did is I remapped my volume up n down keys to power and back button which I believe are the most used in android and then found a app to manage my volume in android that way I don't lose my sound on rhw phone
Also I went ahead and got a another app which places virtual buttons on ur screen so u can use then instead of the actual hardware buttons
For button remapping
get the BUTTONREMAPPER for android and for on screen android buttons get BUTTON SAVIOR
hope this helps
Sent from my HTC HD2 using XDA App
Good to know... will now wake my phone up with the green key as its hardly used in Android. Button Savior is a great app, been using it a while now. Took a bit to retrain myself to not use the back key.
Sent from my HD2 using XDA App
i'm going to agree with your hypothesis or at least suspect that dirt is probably a bigger factor than most people think in these cases. i just bought a non-responsive phone today and while i stuck my nail (yes, i should probably clip them) around the edge, in between the screen and housing, i was surprised to see just how much dirt was in between that crack. same with the area around the buttons; there's a lot of grime there.
since i just got the phone i haven't even opened it up but the first thing i'm planning to do is give it a good interior clean around the buttons for sure as that seems to be the sensitive spot. touch screen devices are very delicate and the micro particles of dirt which build up over time probably create a hazard that people really don't really anticipate. compound that with having to mash on those buttons all the time probably crams the debris in there even tighter.
i'll attempt to clean and check the contact as you suggested and will report back if it helped in my case.
About hardware keys:
I don't use them at all, only for wake up the phone (it can be wake up with any key)
There is an app in market called "button saviour" it's just excellent app to keep your hardware keys for a long time
AngelDeath said:
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
Click to expand...
Click to collapse
You just hit d nail on d head pal...My HD2's touchscreen also stopped responding and nothing i did (software-wise) worked...i flashed several WinMo ROMs and Android builds with no luck, till i read somewhere online dat some guy seemed 2 solve his touchscreen issues by installing "CleanRam", ran a level 3 clean up (use MyMobiler for this) and by pressing real hard on the red end key button..I did just dat and voila it works!!
I have a Tmobile HD2 which is no longer covered under warranty and i'm not willing 2 part with almost $200 here 2 have d whole lcd & digitizer replaced...I recollected dat in d forum i read the suggestion from, a lot of ppl came n posed their views on why it's not possible but i tell u it is cuz it worked for me..Nw i'm comfortably dual-booting WinMo & Android via sd. i use "button savior" and "extended control" to navigate and power down/reboot respectively.
Hweva i believe its not a permanent fix as it simply refuses 2 allow me run android full-time thru MAGLDR, & i think i know y..pressing down on d end button 2 launch MAGLDR/CWR options after install messes up d connection with d digitizer underneath and d touch screen thereby causing it 2 fail again when android boots up....I just might try opening it up myself n cleaning dat area up as u suggest but dat'll be when my current fix fails cuz as d saying goes "If it aint broken? then don't fix it"
Just installed Button Remapper, and not to sound like an idiot, but can someone tell me which one I would have to remap to make the volume up key or down key to put the phone to sleep and wake it up, and would that still be able to use the volume key to turn up and down the volume as well?
AngelDeath said:
Just installed Button Remapper, and not to sound like an idiot, but can someone tell me which one I would have to remap to make the volume up key or down key to put the phone to sleep and wake it up, and would that still be able to use the volume key to turn up and down the volume as well?
Click to expand...
Click to collapse
Hmm...i don't use d app but from wat i can gather on d dev's thread, you would have 2 remap ur volume keys to "Power"...Also checkout dis review 2 learn hw 2 mk d remapped button work even in sleep-mode.
I can agree but mine's been in twice on repairs with the same error but screen was replaced both times amongst the digitizer, backcover (Can't understand why) and 3 other things were replaced. Buttons weren't replaced.
CaCtuZ123 said:
I can agree but mine's been in twice on repairs with the same error but screen was replaced both times amongst the digitizer, backcover (Can't understand why) and 3 other things were replaced. Buttons weren't replaced.
Click to expand...
Click to collapse
If I'm to base how the HD2 is setup internally, they wouldnt replace the buttons, they would replace the contact or contact board under the buttons, remember the buttons are like a keyboard, they dont wear out, its what they push on that gets dirty or worn.
I was traveling and this happen t me and became desperate.
Following the instructions I come to the clear conclusion that our HD2 has this hardware problem.
If I do not use the end call button no issues with the screen, really, no issues.
Hope my feedback will be helpfull as well. Great job done here!
pauloviegas said:
I was traveling and this happen t me and became desperate.
Following the instructions I come to the clear conclusion that our HD2 has this hardware problem.
If I do not use the end call button no issues with the screen, really, no issues.
Hope my feedback will be helpfull as well. Great job done here!
Click to expand...
Click to collapse
Yeah HTC screwed up on dat...its just as said,1 has 2 be careful n avoid using d red end key button as much as possible 2 enable d device last much longer...And if u do ave 2 use it, press on d left-most part of d key (closer 2 d back arrow button) to get d job done.
I just had this issue happen to me and thought it was my build... But I found another way, I use Cyanogen Mod 7, and in the drag down menu (from the top) I added a sleep option, because thats the only thing I use it for... and I never have a reason to press the end button now.
This is the best thing I have found to fix it without having to remap the buttons
I guess I'm lucky because I have never had a problem with the responsiveness of the touchscreen and/or end button. I got my HD2 a month before TMO release date and trust me it has been thru alot (scratches all over, even a piece of glass missing next to the call button). So my question is how much pressure and wear 'n' tear are you all putting on your end button or phone for that matter?
big3d said:
I just had this issue happen to me and thought it was my build... But I found another way, I use Cyanogen Mod 7, and in the drag down menu (from the top) I added a sleep option, because thats the only thing I use it for... and I never have a reason to press the end button now.
This is the best thing I have found to fix it without having to remap the buttons
Click to expand...
Click to collapse
Can that be done with other roms? And wouldnt a shortcut or a widget on the main screen also work?
on1ydabest said:
I guess I'm lucky because I have never had a problem with the responsiveness of the touchscreen and/or end button. I got my HD2 a month before TMO release date and trust me it has been thru alot (scratches all over, even a piece of glass missing next to the call button). So my question is how much pressure and wear 'n' tear are you all putting on your end button or phone for that matter?
Click to expand...
Click to collapse
It all depends really Understand that not all HD2's go thru the same testing process when it comes out of the manufacturer. Also take into consideration that it also depends on how often you flash a rom, if your flashing a rom every day or every week expect that you will shorten the life of the end button, also it doesnt always mean that the button is bad, it could clearly be dirt underneath that could also be causing the issue. And I said the same thing when I saw posts about people saying that android killed their screen. I even responded to it but always maintained it was hardware, even though I didn have the problem, and I bought both my HD2's used in Dec. and the day it happened and I found out why I posted this, if I was to guess, I would say that I probably flashed both my HD2's close to 200 times with different roms, or upgrades, or testing fixes out.
So if your not a flash nut, then your probably safe. There are many factors that can play a role in the end button life cycle, And no two people use their HD2's the exact same way.
the non-responsive touchscreen problem happened to me this morning. I woke up trying to unlock my phone only to find that it would not respond to any touch gestures. I was however able to uninstall HSPL and Flash the stock WM6.5 rom since I was going to T-Mobile to get a replacement. When I took it to T-Mobile the employee resetted the phone by holding the 2 volume buttons and the power button then somehow the touchscreen started to respond to touch again. I was completely puzzled as I thought it was for sure a hardware problem. But now I'm going to flash Android and hopefully the problem will not arise again, if it does, back to T-Mobile I'll go!
What Android really needs is some sort of "X" button, or even a widget on the main screen that you can just tap and put it to sleep. The three most keys used in my opinion is the windows key (Apps that use it for a menu), the back key (Since there is no damn close button), and the end key (sleep, flashing, booting to magdlr).
Some one had a concept here of buttons that looked very similar to The desire HD, the greatest thing would be if someone could make the bottom of the htc sense (app drawer, phone, and the personalize) auto hide and have the desire HD buttons come up with a power button at the end and this way if you hit menu it would bring up the original 3 button screen.
I've had a problem with my E900 since I got it with regards to the screen. I was hoping Mango might fix it but it doesn't seem to have.
Sometimes if I press the power button the screen backlight comes on (i.e. screen goes from off state to powered) but there is nothing on the screen. No amount of button pressing will cause the screen to show anything.
If this happens I have to turn the device off again (backlight then goes off) and try again. Sometimes it can take 2-3 times before it turns on successfully with the lock screen.
I also have this if an incoming call attempts to wake the phone and also alarms too.
Does anyone else have this issue?
I confirm this one popping sometimes. Not that often that it becomes annoying, but nevertheless.
Did you find a solution to this problem? I am experiencing it too and it is very annoying!
I've recently inherited one as well (E900 that is).
The one I have has been dropped, the backlight powers, but no drawing on the screen.
I've disassembled and re plugged everything (bugger stripping down!) but still no luck. I've done a VolUp+Down+Cam+power hard reset, and when I plug into PC Zune says setup needs completing (so it has reformatted) but still no luck.
I cant see anything fried, and no damaged ribbons as far as I can see, any ideas?
I sold the phone a while ago, and never solved the problem. I think it's a firmware issue.
PaulMdx said:
I've had a problem with my E900 since I got it with regards to the screen. I was hoping Mango might fix it but it doesn't seem to have.
Sometimes if I press the power button the screen backlight comes on (i.e. screen goes from off state to powered) but there is nothing on the screen. No amount of button pressing will cause the screen to show anything.
If this happens I have to turn the device off again (backlight then goes off) and try again. Sometimes it can take 2-3 times before it turns on successfully with the lock screen.
I also have this if an incoming call attempts to wake the phone and also alarms too.
Does anyone else have this issue?
Click to expand...
Click to collapse
hi.
What do you mean "somethimes if I press power button"?
Is it pressed with purpose to lock the phone, press it to turn off phone (background slider shows to power off - on Mango and beyond version) or press it accidentally?
Cheers.
So, I did a phone reset. Unfortunately the issue is still present!
Sometimes when I press the power button to unlock the phone the screen is lit, but stays blank i.e. no lockscreen wallpaper, no nothing. The same happens sometimes when I get a phone call - the phone rings and vibrates, the screen is lit but stays blank.
When this happens I have to press the power button to put the phone into sleep mode and press it again to wake it up.
What I found is, when the issue occurs the screen is actually responsive. For example I can slid up and unlock the phone then I hear the unlock "pop" sound. It's just that nothing is drawn on it!
I was wondering if anyone else experienced the same behavior and found a resolution. Also I am not sure if this is a software or a hardware problem. If I could confirm it was a hardware problem I would call LG and have the phone repaired or replaced.
i have exactly the same issue as you, it gets really annoying.
i heard from someone online that the only way to resolve it is to replace the motherboard
billybrown said:
i have exactly the same issue as you, it gets really annoying.
i heard from someone online that the only way to resolve it is to replace the motherboard
Click to expand...
Click to collapse
I am pretty certain this is a hardware issue. I am calling LG tomorrow and hopefully they'll take the phone for repair/replacement.
I sent my phone for repair. Today I got it back, and guess what?!
The issue is still present! It seems, they "couldn't reproduce" or something.
What should I do now?
EDIT: If anyone is interested, here is a video I just captured which clearly demonstrates the problem. http://youtu.be/38kF9RYs_bU
I'm sending the phone back for repair tomorrow with this video attached.
Hey, might not be an issue at all, but in the video, I saw that the two times you were able to get it to go blank you had your finger on or near the proximity sensor. I wonder if there is something that could be the trigger.
Just wondering if you can duplicated it or cause it only when you have the proximity sensor blocked, or if it truely is random.
You are right, it might has something to do with the proximity/light sensor.
On the other hand, this issue occurs even on incoming calls when the phone is placed on a table, screen up and nothing around the sensor.
Today, I visited my local carrier shop and left the phone for repair again. They told me, since this is a second claim they'll run it through the process faster, so I expect to get it back next week.
Will post an update.
UPDATE: My phone was replaced. Yesterday I got a brand new unit, yeah! It was stock wp 7.0. I plugged in my sim and used the phone the whole day, no sign of blank screen issues. Last nigh I installed all the updates (total 5 I think) up to OS 7.10.8107.79, FW 1.0.16.10. Guess what?! Same issue!
I am crushed
Phone was working with no issues until the other day. I was viewing a web page and noticed the text didn't look quite right, it seemed to be shimmering. Then a bit later on switching to the camera app the screen was just a lot of green flashing lines, pressing home button worked and then starting the camera again it would either be the same or would work properly. Then later that evening after using the phone fine opening the s cover the screen would not come on but the menu and back buttons would light up, pressing the power button a couple of times would make the screen appear. Then that stopped working as well, and no even then back and menu buttons don't light up. the phone still seems to work as plugging in the headphones and pressing the button on them starts my music playing, but I can't get the screen to turn on at all.
The phone has never been dropped has been very well looked after and is immaculate , there are no scratches on the screen and I can't see any cracks (from a pressure break) either.
Any ideas?
this might sound like im trolling, but did you try turning it off and on again?
seriously, your screen is probably broken. send it to sammys customer service or whereever you bought your phone and let them check and/or repair it