This just started to happen today....every time my screen timeouts...it goes completely blank...i can still hear things and receive calls...but it will stay white for like 20 seconds and then come back on... i am using Ricky's Wm6.1 any help would be great...thanks
zdub27 said:
This just started to happen today....every time my screen timeouts...it goes completely blank...i can still hear things and receive calls...but it will stay white for like 20 seconds and then come back on... i am using Ricky's Wm6.1 any help would be great...thanks
Click to expand...
Click to collapse
Hard-reset if this doesn`t solve it re-flash...
stylez said:
Hard-reset if this doesn`t solve it re-flash...
Click to expand...
Click to collapse
Interesting.... I just started having this problem as well. I went hard reset... not solved. I re-flashed (using proper procedure)... and it was solved for a couple of days... and then returned.
I then used the forum search function, crazy how that works and found this thread.
Hope that helps.
Are you using maniac's AutoKeylock ?
I have experienced this issue ever since loading Rose ROMs - didn't happen on earlier ones.
However, this last time I flashed to the latest update, I did not install AutoKeylock immediately after flashing. I left this off as I had noticed that the screen was going white 30 seconds into calls (which was the timeout I had configured in AutoKeylock) and I wondered if there was a correlation.
Can anyone else who has seen the issue comment on whether they use AutoKeylock or not. It is possible there is some change in the ROM that AutoKeylock does not handle well.
Thanks.
LiverpoolFCfan said:
I have experienced this issue ever since loading Rose ROMs - didn't happen on earlier ones.
However, this last time I flashed to the latest update, I did not install AutoKeylock immediately after flashing. I left this off as I had noticed that the screen was going white 30 seconds into calls (which was the timeout I had configured in AutoKeylock) and I wondered if there was a correlation.
Can anyone else who has seen the issue comment on whether they use AutoKeylock or not. It is possible there is some change in the ROM that AutoKeylock does not handle well.
Thanks.
Click to expand...
Click to collapse
I think that the WSOA (white screen of annoyance) is tied to the low-light function and joggr bar. Go to joggr settings, and be sure that the checkbox with the lowlight function is disabled.
I had the white screen issue for a few days, tried everything.....as soon as I uninstalled GlyphCache 65535 found here, the problem went away
Capper5016 said:
I had the white screen issue for a few days, tried everything.....as soon as I uninstalled GlyphCache 65535 found here, the problem went away
Click to expand...
Click to collapse
it comes and goes its just something messed up that happenes probably nothing to worry about, just little anoying is all.
Check power management registry settings
Hi,
I had this problem once and fixed it by changing the registry settings that control what happens when the device enters various power states. Search the forum about this as the answer is in there somewhere Hope this helps.
Related
I've been running the 6.1 rom for about a week now and I'm seeing an issue where when the phone is synced with the pc or when I'm in the middle of a phone call the screen goes all white. I quick key press and it goes back to normal but this keeps happening over and over.
I tried reflashing the rom, reverting to official tmobile then reflashing 6.1 and it still does it.
Anyone else?
sledwrecker said:
I've been running the 6.1 rom for about a week now and I'm seeing an issue where when the phone is synced with the pc or when I'm in the middle of a phone call the screen goes all white. I quick key press and it goes back to normal but this keeps happening over and over.
I tried reflashing the rom, reverting to official tmobile then reflashing 6.1 and it still does it.
Anyone else?
Click to expand...
Click to collapse
Touch JOGGER 3 times in 10 seconds will open Lowlight.Attention,this will maybe make your backlight always on if you don't close it.
in 080318 this function has been closed as default
That did the trick! Thanks!
My phone recently started doing this as well. I try tapping the jogger bar 3 times, but doesn't seem to do anything. I'm I missing something this seems too simple for even me to mess up...
fiveohhh said:
My phone recently started doing this as well. I try tapping the jogger bar 3 times, but doesn't seem to do anything. I'm I missing something this seems too simple for even me to mess up...
Click to expand...
Click to collapse
Nvm, fixed it by ticking the box in the JOGGR setting area.
hey, i dont understand what that did. can anyone explain.
Did you try a hard reset ?
loser said:
Did you try a hard reset ?
Click to expand...
Click to collapse
yep, i dont understand that lowlight thing, might make me sound like a dumbass haha.
i did the lowlight, and the screen popped up. iono what was there to do.
Hey just want to state that the 3 click thing was unchecked on my phone when i installed kavana 6.1 so i've click on it and i'll report back what happenes.
We'll it seems clicking the 3 in 10 seconds option in the jogger options keeps the white screen from poping up on me, will keep posted soon.
White Screen
So it i havent had anymore issues today, click on 3 in 10 option in Jogger settings.
Seems to be pretty stable now for me seems better with the 3 in 10 setting checked.
will report if i get it again.
Microsoft branded S621 Pro WM6.1 6.1 Made in Taiwan overclocked to 288 stable.
Wonder if someone could make one, a visual plug-in be sweet the pocket pc verson has a visual plug-in, so i'm surprised this one doesn't.
pocket pc verson: HHCv10final.cab
plug-in for visuals HTC-Home-pluginv1-0.cab
I think I may have stumbled onto a solution to our dreaded quiet phone that doesnt notify us of a SMS or MMS and possibly email when the phone goes to sleep or standby. I have searched asked inquired, and beat every search engine and found absolutely nothing. So being frustrated of seeing msgs pop up when I hit the power button to wake the phone up I went hunting and I think I found it. I tested this all of today and so far I havent missed one yet, and normally I miss at least 3 a day. Its still in a testing phase so I DONT guarantee this works, but with some feedback with others, it might be the solution. I did alot of comparing with my other phones and my 8125 and 8525 had a different value so i changed it to that value.
I have made it a cab file so that anyone who wants to try it can uninstall it if it doesnt work, I suggest a soft reset after making this change. This changes the following location:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableSMSWakeUpEvent"=dword:00000001
to
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"DisableSMSWakeUpEvent"=dword:00000000
Good Luck! And if it works or doesnt, please leave feedback of either thanx or didnt work, like I said so far its working on my att tilt 2 stock eu rom 1.86
Nice one, but its already been solved here.
crachel said:
Nice one, but its already been solved here.
Click to expand...
Click to collapse
Well at least its here, I know there is a ton of posts going around in here about this problem, and I did munerous searches, but obviously if you dont get the right keyword you'll never find the post.
so what does this do? light the screen up everytime there is a message? or basically just solve the problem of message not ringing in sleep mode?
Basically it does the same thing it did with the 8125 and the 8525 when a msg comes in the screen wakes up from sleep, so far (I thought) I might have found a solution, but it seems I was beaten to it.
So far there isnt a solution found yet of the alert coming thru without lighting the screen up as far as I know.
yea, i thought it lights up the screen when msg comes. I have a habit of putting the phone to sleep without locking it, so it might cause problem when i put it in my pocket as i receive message more than calls.
Thanks anyway mate
mr_sheen said:
yea, i thought it lights up the screen when msg comes. I have a habit of putting the phone to sleep without locking it, so it might cause problem when i put it in my pocket as i receive message more than calls.
Thanks anyway mate
Click to expand...
Click to collapse
Yeah but if you have the end key setup as a long hold it will lock the screen to prevent that accidential tapping of the screen. Unless you have a modded rom then you would have to see what key it is. But hey for me its better then missing a msg.
Hi AngelDeath,
Just wanted to say thx for this one -I realise this thread is old, but it's sorted my no sms alert issue on my HD2. It had been driving me nuts for ages!
Hey everyone,
I'm currently running the latest Jackos and I believe everyone was fine with the speaker you hold to your ear in conversation until about 2 weeks ago. Maybe a week or so after I installed the newest Jackos. Now I can't hear anything on it, but the microphone works fine. Speakerphone works fine, and my bluetooth earpiece works fine. I've searched for help on this and can't find anything to fix this problem.
The other problem is right when I boot the phone, instead of getting the black screen with the red diagnostic text, I get a white screen with colored speckles all over the screen. The speckles don't move at all and if I let it sit for 20 seconds or so, it will then show the HTC logo on black and continue booting. I can't get into the bootloader, I can't hard reset the phone, etc. Any ideas how to fix this? I haven't tried flashing the same/another ROM yet, but I don't know if that's even possible with this snow screen problem.
I've run Task29 and all the usual stuff every time I've flashed and I have never seen this happen until a couple of weeks ago. It does it NEARLY every time I soft reset or shutdown and boot or pull the battery and boot. The battery charges fine and it runs fine otherwise.
The screen will get random glitches in it, even when the battery is full and it makes me suspect maybe the battery's going bad but it'll run all day without problems and it doesn't get warmer than usual or anything like that.
Also, sometimes it says there's no SIM inserted and I've pulled it out, the contacts are nice and gold and nothing seems wrong.
Any ideas?
My sig is out of date but I have to head out right now and can't switch it yet, but it's the latest Jackos with 6.5.
Thanks,
Eric
I would flash a different/stock ROM and see if anything changes.
If no, hardware problem. If yes, software problem .
You seem to think you cannot, but AFAIK if you can task29, you can flash a ROM. Either way, putting an nbh on the SD card and doing power+vol up+reset should work regardless, unless the device is really bricked - in which case it wouldn't be booting.
Okay thanks, I'll see what I can do with it.. It does boot fine, though for a week I thought it was bricked because of the snow, but I decided to just let it sit for a week and gave it a shot, and poof! no snow on the first boot. It had the regular red text on black. Then I reset it from the slide to reset menu item and it went to snow again. I let it sit there and about the duration that it would be on the diagnostic screen, it was snow, then magically showed me the HTC logo and booted normally.
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Thanks again,
Eric
shep2112 said:
So it seems to me that it somehow doesn't want to show diagnostic info but does everything else.. So maybe the bootloader mode IS working, I just can't view that. I'll see what I can do.
Click to expand...
Click to collapse
Flash stock, it re-flashes everything... Make sure it works, then flash back to Jacko's.
shep2112 said:
Does the screen corruption/no sound in earpiece seem like a ROM issue, or battery related, or phone going bad problem to you?
Click to expand...
Click to collapse
This is what we're trying to troubleshoot .
shep2112 said:
And I've been looking for a while trying to find a suitable replacement, but haven't seen anything that I really find appealing (either in Android or WP7).. Any thoughts on that?
Click to expand...
Click to collapse
Talk about loaded questions! I haven't found anything that's appealing with a hardware keyboard yet... The supposed TP3 (on Sprint it's the "Arrive"...) was a real disappointment.
MT4GS looks decent, if you can live with tmo...
Thanks for your replies, I'm going to try to flash to stock in a little while and see how that goes.
The new Glide phone that AT&T has sounded promising until I read a review of it. Slow camera, 480x800 on a larger screen, etc. It didn't seem as cool as I had hoped it would be after that.
I'll write back with my progress or lack thereof with this TP2.
Eric
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
shep2112 said:
I installed HTC's official AT&T ROM and the screen corruption seems to be less extensive but looks different too. The snow at startup is still present though.
There was a radio that came with Jackos ROM, is there any chance that's to blame? Though it worked fine for a couple weeks before these weird screen things started happening.
I haven't tried making a voice call yet to test the earpiece/earphone/loudspeaker or whatever the proper name is for it but since nothing else is really 'fixed' I'm not sure it will work either.
Thanks,
Eric
Click to expand...
Click to collapse
The stock ROM should've come with a radio as well...
task29 & flash stock? Otherwise perhaps you have a hardware problem... I don't know what to make of this snow .
The earpiece/loudspeaker thing isn't fixed either. I'll try a Task29 tomorrow or tonight if I can't sleep (thinking about this stupid phone! ) and then flash this ROM again and see what happens and let you know.
Thanks again
Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
The problem seems to be irrelevant to the Apps installed.
The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
I manually reboot my phone at most every two days.
Solutions tried, but don’t work
Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...