I've heard of the usual 2 or 3 second lag for most users. They'll try to wake up their phone with the power button, but there's about a two or three second delay. I wouldn't care at all if I had that!
My problem is far more sinister. I don't have the usual wake lag. It's dynamic and unpredictable.
Let me explain. When I first boot up my phone (or restart it) it works flawlessly. No lag—nothing. Not even the three second wake lag most people get. Then, out of nowhere (I can't pinpoint when it starts) I'll try to wake it up and... nothing! The backlight will turn on (that very dim black light) along with the soft keys. They'll turn on fine, but my display will not show up. Funny thing though, sometimes I'll tap the screen and it'll vibrate as if it was on. The only way to fix this is one of two ways: restart the phone (very annoying) or turn it on and wait. Sometimes, eventually the display will kick in but I have about a second to react before it shuts off. Then, I have to press the power button twice more to turn off the backlight and turn it back on and wait for the display to kick in. If I tap and swipe to unlock, I'm mostly in the clear. But, most of the time it takes SwiftKey about 30 seconds to respond. I'll tap and tap and nothing will be written, but after 30 seconds of spamming it'll finally start to write. Then, my phone has minor/no lag while the display is still on. But, if I let it shut off, then it starts all over again. Backlight, but no display.
Sometimes I'll be lucky: I had a three day streak of no lag at all, but then it happened. It really is random, and I have no idea what could be causing this. It wasn't always this way either.
I have this rooted and am running CarbonRom (Android 4.4)
ANY help would be appreciated. Nothing seems to fix this permanently.
Try another rom, or better yet... Try stock 4.1.2 for comparison. Install the same things on it and see. It could be certain apps slowing your phone down, or lack of ram, or your setup.
Mine is on stock 4.1.2...and I'm sometimes amazed when I do pick it up and use it, like when I'm charging my other phone, at how zippy it is. It's not way slower feeling like you'd think it would be, at all.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Also a cache and dalvik wipe can often help. Especially on older devices.
This is a common issue with KK ROMs & kernels. Try a JB ROM instead.
KJ said:
Try another rom, or better yet... Try stock 4.1.2 for comparison. Install the same things on it and see. It could be certain apps slowing your phone down, or lack of ram, or your setup.
Mine is on stock 4.1.2...and I'm sometimes amazed when I do pick it up and use it, like when I'm charging my other phone, at how zippy it is. It's not way slower feeling like you'd think it would be, at all.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
Also a cache and dalvik wipe can often help. Especially on older devices.
Click to expand...
Click to collapse
Agreed, a dalvik cache and a cache wipe will often help. What would be the best way to update to stock 4.1.2 from stock 4.0.3? It is not showing up in ota and I can't use kies or Odin as I don't have a Windows computer. Heimdall can only seem to successfully install ICS on this phone.
Sent from my SGH-T989
You could just flash a stock 4.1.2 rom... Tho its usually best to Odin stock first , then flash things 4.1.2 and higher.
Yeah, without a pc ... Not sure what you can do. Maybe you could visit someone that has Windows pc ?
You can try just flashing a stock rom, buy good chance you'd freeze at boot up.
KJ said:
You could just flash a stock 4.1.2 rom... Tho its usually best to Odin stock first , then flash things 4.1.2 and higher.
Yeah, without a pc ... Not sure what you can do. Maybe you could visit someone that has Windows pc ?
You can try just flashing a stock rom, buy good chance you'd freeze at boot up.
Click to expand...
Click to collapse
Don't know. All I know is when I try flashing 4.1.2 in Heimdall it freezes after Android is upgrading and then boot loops. I've tried wiping data, cache, and falcon after flashing and it still didn't work. I'll probably just stock with AOSPA since it is fairly stable right now and has decent battery life.
Sent from my SGH-T989
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
ayr0 said:
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
Click to expand...
Click to collapse
96mhz will definitely cause some things to lag on wake. Test it tho and then compare to 300. I very much doubt you'll see any difference in battery life at all.
Thanks for all the replies, and I just may have to try a ROM that's a bit older. This phone is basically ancient history now, but it suits me well. I'll try the stock JB ROM but probably won't keep it—I do enjoy having the features many custom ROMs include.
I've also installed and ran LagFix free from Google Play, and I can say it greatly reduced the frequency of the wake lag occurring. It still happens but for the most part it turns on fine.
ayr0 said:
I'm running CarbonROM + WildKernel. Currently, I have no problems with wakeup lag when tapping the power button. Though, when I recieve a call, it takes several seconds for the screen to wake. I have my kernel configured for 96Mhz when screen is off. You might try increasing the base cpu frequency and see if that helps. You might also try changing your cpu governor and see if that helps.
However, your tapping the power button twice description might be indicative of something wrong with your power button. Just a thought. These particular phones are known to have issues with the power button after time.
Click to expand...
Click to collapse
Twice in meaning once to turn off the backlight to put it to sleep and then once more to attempt to "wake" it up again.
KJ said:
96mhz will definitely cause some things to lag on wake. Test it tho and then compare to 300. I very much doubt you'll see any difference in battery life at all.
Click to expand...
Click to collapse
You are right, I just looked at the voltage tables in my ROM and everthing below 153Mhz uses the same amount of power.
I'm going to try 153Mhz for awhile and see if that helps. Thanks for bringing that to my attention.
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
Saturable said:
Thanks for all the replies, and I just may have to try a ROM that's a bit older. This phone is basically ancient history now, but it suits me well. I'll try the stock JB ROM but probably won't keep it—I do enjoy having the features many custom ROMs include.
I've also installed and ran LagFix free from Google Play, and I can say it greatly reduced the frequency of the wake lag occurring. It still happens but for the most part it turns on fine.
Twice in meaning once to turn off the backlight to put it to sleep and then once more to attempt to "wake" it up again.
Click to expand...
Click to collapse
How much time do you wait between button pushes. On my rom, it they are I press the button twice in immediately consecutive pushes, it does take a second or two for the phone wake. However, if I wait a second or two before pressing the power button again, wakeup is almost instantaneous. I attribute this to the fact that even though the screen is powered off, it takes a little bit of time for the phone to actually go to sleep. The phone might be lagging because it has to wait for the phone to sleep before it can wake up again.
Related
Hello Everyone,
Problem: Set up a word password for the lock screen, forgot the password, entered as many times what I could try to remember, couldn't remember it at all, forgot password option never appeared. Had data on sdcard so didn't care if I'm going to hard reset the phone.
From CWM Recovery 6.0.1.2 did the following ( a lot of times ) : wipe data/factory reset , wipe cache partition , format /system, format /cache, format /data, format /sdcard, format /external_sd as well ( different card ). Rebooted. Everything seemed normal, initial setup, google account, date/time, location/gps. browsing through the phone until the 30seconds backlight timeout passed and screen went off. I press unlock/power button and viola, password prompt back again. WTF ? I DID everything.. did the same thing again, this time, after the initial setup, did samsung's code *2767*3855#, started automatically doing factory reset. again after this, initial setup and still password prompt. did this again, went into settings and change screen lock, and it said to enter password. Seeing that's not helping, downloaded a stock rom, and flashed it through odin 4.43. everything seemed good until again went to screen lock settings and same thing. after screen went black, the same thing.
rooted again, installed cwm, flashed custom rom bagux-project-rom-v1.4, seemed good until went to settings and prompt there as well as screen went black turned it on and prompt again.
gbsIII rom - same problem
cow rom - same problem
ehndroix 12.9.13 - same problem
f.a.w. ris4 - same problem all these roms based on 2.3.6/2.3.7
flashed ancora_signed(cyanogenmod) - NO PROBLEM
flashed cm-9 experimental - NO PROBLEM
flashed RemICS_1.7 - NO PROBLEM
Problem is that I really want ENERGY SAVING OPTIONS because that way the battery lasted me two full days on normal/median usage, texting calling wifi and 3G. ICS DO NOT HAVE THIS AND therefore my battery on the same type of activity lasts not even a day.
ALSO, Somehow, wifi drastically downgraded it's performance meaning it takes really long to turn on, sometimes scans sometimes doesn't, when there is 100% a signal in one spot, it won't find it at all, and other time it will and the worse part is that when it connects, and connection is, ip and everything good, internet doesn't work. < this only on ICS or cyanogenmod. < but this is not what I'm concerned about. Just saying if It might help.
I don't know what to do anymore... I'm not a noob at this because I have rooted MYSELF and flashed roms and other stuff to Samsung Gio Samsung Galaxy S II and Htc Desire-Z (a7272) and now I have my wonder I8150 and this is just SHOCKING TO ME. I really did not expect something like this...
it looks like something easy to fix however on the other side..i don't know.. maybe I am not doing an extra step ?
Please, I really need assistance..
So let me get this straight. You couldn't get rid of your lockscreen in any GB rom, then decided to flash an ICS rom and it worked but you want to save battery. Then you discovered the wifi problem and you don't know what to do. Right?
Sent from my GT-I8150 using xda app-developers app
---------- Post added at 05:18 AM ---------- Previous post was at 04:40 AM ----------
So because you didn't reply as fast as i thought, i will just answer what i understood.
1-about your lockscreen problem, this is might be because of a restore you previously set to automatic. I actually don't have any other reason cuz this just never happened to me or ever heard of it.
2- And about the power saving you want to have in ICS. I have tried that build-in power saver, it doesn't work as well as some other power savers from the playstore.
Adding to (2) i don't use any power saver cuz they just turn down your phone's speed to save battery. I use setcpu (app from playstore) to create different profiles that work in different times (like when screen is off speed goes down as i don't need it and when screen is on speed comes back up).
3- The wifi problem you only noticed in ICS because its a bug in arco's kernel which almost every JB/ICS kernel is based on, but don't worry arco will soon find a cure. But until then, when this happens just long press the wifi icon in the statusbar and it will open the wifi settings, which will start an automatic search and connect from there.
Sorry for not waiting, i'm still 15 and have a test tomorrow and highschool life to worry about
Sent from my GT-I8150 using xda app-developers app
---------- Post added at 05:30 AM ---------- Previous post was at 05:18 AM ----------
If you need anything else just ask or pm me (i prefer asking here so if some gets the same problem, could read and solve it without asking or wasting his time)
Sent from my GT-I8150 using xda app-developers app
Hey &Amada
Thanks for replying and to my response time, I just got home, lol..
The problem I have is with the lockscreen (password prompt). if I flash a stock or custom gb rom, the lockscreen ( password prompt )turns on after the screen turns black ( after 30 seconds ) and returning to the "restore / backup , I didn't set it all, it was already ticked, the automatic part, on every gb rom too and worse was I couldn't untick it...
Right now I have ICS ancora beta 3 and there is a "performance" tab in settings before "about phone" and in thereis processor - change cpu governor and clock speed and types like consevative ondemand performance interactive powersave and minimum cpu frequency and max and set on boot. If setting a lower clock when screen is off would improve my battery or at least I would notice it then I would go for it but here's a great example. right now, on ics, when i take out the usb charger cable from phone, the second i take it out, 100% drops to 99%. in gb rom, stayed on 100% for about 30minutes minimum. just comparing. and this is on the same usage.
I went to a service guy, which my friend from school knows and recommendem I'm 18 btw and in high school as well and he said it might be faulty cache ( the memory part ) because it's similar to people's dead sdcards in phones and password prompts appear for them and the phone interprets it as a security exploit or break and therefore takes it as a password prompt.
& to the wifi, it's not a big problem, but it is annoying.
7amada100 said:
So let me get this straight. You couldn't get rid of your lockscreen in any GB rom, then decided to flash an ICS rom and it worked but you want to save battery. Then you discovered the wifi problem and you don't know what to do. Right?
Sent from my GT-I8150 using xda app-developers app
---------- Post added at 05:18 AM ---------- Previous post was at 04:40 AM ----------
So because you didn't reply as fast as i thought, i will just answer what i understood.
1-about your lockscreen problem, this is might be because of a restore you previously set to automatic. I actually don't have any other reason cuz this just never happened to me or ever heard of it.
2- And about the power saving you want to have in ICS. I have tried that build-in power saver, it doesn't work as well as some other power savers from the playstore.
Adding to (2) i don't use any power saver cuz they just turn down your phone's speed to save battery. I use setcpu (app from playstore) to create different profiles that work in different times (like when screen is off speed goes down as i don't need it and when screen is on speed comes back up).
3- The wifi problem you only noticed in ICS because its a bug in arco's kernel which almost every JB/ICS kernel is based on, but don't worry arco will soon find a cure. But until then, when this happens just long press the wifi icon in the statusbar and it will open the wifi settings, which will start an automatic search and connect from there.
Sorry for not waiting, i'm still 15 and have a test tomorrow and highschool life to worry about
Sent from my GT-I8150 using xda app-developers app
---------- Post added at 05:30 AM ---------- Previous post was at 05:18 AM ----------
If you need anything else just ask or pm me (i prefer asking here so if some gets the same problem, could read and solve it without asking or wasting his time)
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
By the time arco fixes the wifi bug, maybe I will get the gb rom working..
only the lock screen problem i got ..:/
baldusiek said:
By the time arco fixes the wifi bug, maybe I will get the gb rom working..
only the lock screen problem i got ..:/
Click to expand...
Click to collapse
Okay, maybe you could go back to gb or JB i am using pacman and it rocks i didn't face the wifi problem since flashed.
But if you really want to go back to gb here is my suggestion:
You said that after you flashed gb with sometime, the lockscreen comes back. So just as soon as you reboot from flashing just install a lock screen replacement from the market or such. And make sure they can be toggled in the accessibility section of the settings. That way it will automatically disable the lockscreen even if it comes back
Sent From My PACMAN Wonder Using xda-Developers app
7amada100 said:
Okay, maybe you could go back to gb or JB i am using pacman and it rocks i didn't face the wifi problem since flashed.
But if you really want to go back to gb here is my suggestion:
You said that after you flashed gb with sometime, the lockscreen comes back. So just as soon as you reboot from flashing just install a lock screen replacement from the market or such. And make sure they can be toggled in the accessibility section of the settings. That way it will automatically disable the lockscreen even if it comes back
Sent From My PACMAN Wonder Using xda-Developers app
Click to expand...
Click to collapse
Hey, I tried "MyLock utilities" but it did not work.. apps aren't an answer to keep bypassing the screen lock all the time.. I don't get why the phone "remembers" the password even though it's formatted... faulty memory ?
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?
i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.
Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
same issue here, I'll try to keep the brightness to manual to see if it works
chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019
Hi all,
After my Wildfire running CM7 being so unresponsive I've almost had the urge to throw it against a wall at times, last night I snapped and installed AOKP Lite v5. Wow. ICS yet amazingly fast.
All was fine and dandy until this morning when for some reason long pressing the power button (for anything more than half a second) results in an instant reboot - but not a full reboot - I don't get the HTC logo. What should be happening is that the power menu displays, but for some reason it's no longer doing this.
Some actions that may have contributed to the problem that I have reversed:
- I enabled trackballwake via the terminal (I've now reverted it, no effect)
- SuperSU updated - this apparently caused problems due to some "pro" features not available. I reverted to factory version, then, installed the CWM Superuser and disabled SuperSU. Playing with different Superuser apps hasn't helped get the power button menu back.
- Enabled USB Fast Charge (then disabled again).
- Enabled then disabled the Power Saver.
- Changed Scaling governor to smartassv2 from performance, for the sake of testing, reverted back to performance.
- Added Screenshot to power menu, later removed.
My guess is that what's actually happening is that the power menu is trying to display and is then catastrophically failing resulting in an instant reload of the ROM. Why this is the case I can't work out.
I'm not finding any reference to such a problem but I thought I'd put it out there in case someone has an idea. It's early enough on that I could just reload everything but I'd rather not have to go through that if I can avoid it seeing as (everything else) is set up how I'd like it. Also, what's to say it might not happen again in the future!
Thanks
@rguk,
I've also experianced this before, as I know it is caused by enabling the power saver options. Its best to let that be.
had to reflash the ROM again to solve it.
Cheers
just disabling power saver solves this issue.
Wasimk32 said:
just disabling power saver solves this issue.
Click to expand...
Click to collapse
not sure, didn't work for me...
Thanks for the quick reply guys. Oh well, re-flash it is then... Turning off the power saver options didn't fix it for me.
Hmmm. Received a call and the screen remained black. Did a quick search and I'm seeing some related stuff, let's hope a re-flash fixes that, too.
@Wasimk32
mate, I just found a guide about soft rebooting, I don't know whether this'll be helpful or not as I'm not a dev.
Thought this could, if it can, help you to solve the soft rebooting issue.
http://forum.xda-developers.com/showthread.php?t=2360936
Cheers
lakshan_456 said:
@Wasimk32
mate, I just found a guide about soft rebooting, I don't know whether this'll be helpful or not as I'm not a dev.
Thought this could, if it can, help you to solve the soft rebooting issue.
http://forum.xda-developers.com/showthread.php?t=2360936
Cheers
Click to expand...
Click to collapse
thanks mate,thats something we call hot reboot.This might not solve this issue but definitely could help me looking in a right place.
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…)
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
broky said:
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
Click to expand...
Click to collapse
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
levone1 said:
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
Click to expand...
Click to collapse
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
broky said:
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
Click to expand...
Click to collapse
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
levone1 said:
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
Click to expand...
Click to collapse
thanks mate i m working on it and i ll repopt back if i solve it and how or need more help
SOLVED:after a lot of testing found out that my problem was xposed framework v74-sdk22.
from the moment i installed xposeeed v75-sdk22 everything works as it should,not a single reboot and phone is rebooting faster also and no lag as i used to have before,fingers crossed it won t show up again:good: