Related
Hey ho fellas ,
I was working on adding power management + initialisation/de-initialisation sequence for rhodium´s lcd panel. Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
I would like that all of you users that are willing to help to test the kernel ( zImage+modules + latest commits included ) and give some feedback.
Test the power on/off sequence, leave it sleeping for ~30mins and unlock it,...then give me here some feedback on your lcd panel behaviour.
zImage + modules ( mediafire or attachment ):
http://www.mediafire.com/?ny18wpc3z8utxrf
Prerequisites:
- Backup your data.img if you have some valuable data on it ( anyway it should not affect it )
- Delete pm_sleep cmd from your startup.txt
What do you mean by this?
Till now rhodium´s panel was always on ( initialised ) in deep-sleep aswell those meaning that the display was never de-initialised and was consuming more battery then normal.
Click to expand...
Click to collapse
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Lennyz1988 said:
What do you mean by this?
Do you mean that although the display is off, the panel is still on? Or am I getting this the wrong way? If you could explain this to me then I am willing to test
Click to expand...
Click to collapse
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
lilchicano said:
yeah im curious as well because the only time the lcd is on even when the screen should be sleeping is when its in autobacklight in wm.
Click to expand...
Click to collapse
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
uub11 said:
I think that even though it looks like the screen is turned off it still draws power, so this should eliminate that issue allowing better battery life
Click to expand...
Click to collapse
Yeah, its a little bit hard to explain, but its like you said.
arrrghhh said:
Yea the way it was explained to me (by the OP on IRC) is that you can't really tell necessairly that the panel isn't being properly de-initialized... I questioned that at first as well.
I played with the new zImage, seems pretty smooth. Had a few hiccups on wakeup, but nothing crazy. Test it out guys, let the OP know how it worked!!
Click to expand...
Click to collapse
Yeah, test it out and post your feedback
ReWind402 said:
Yeah, its a little bit hard to explain, but its like you said.
Yeah, test it out and post your feedback
Click to expand...
Click to collapse
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
I uploaded it here on xda, check the 1st post.
uub11 said:
I'm at work and can't download off mediafire can anyone either upload here or on rapidshare.
Click to expand...
Click to collapse
Ha, responded a little late. I removed it...
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Lennyz1988 said:
Does it matter for the testing if you use pm sleep 2 or 1? Just curious. Testing now
Click to expand...
Click to collapse
It would better that pm_sleep has the default value.
Will give this a try as I go about my day today. I don't OC and use pm_sleep=1 yet still get terrible battery life (b/c I'm a power-user, on e-mail constantly). Any positive change will be wonderful We'll see how it goes.
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Lennyz1988 said:
My findings:
- Device does not go into standby, but I used sleep 2, maybe that is the cause.
- The Led keeps blinkin red. (never seen that before on android)
- The device reboots itself.
and a really negative effect is that I lost all my settings... My launcher pro settings, setcpu, whatsapp...
Click to expand...
Click to collapse
1. Try deleting pm_sleep from your startup.txt ( then the default value will be used - i recommend that ) or put 1
2. never seen that on android
Anyway i am really sry for the inconvenience regarding launcer pro, kernel change should not affect those kind of settings :s
solevi said:
Hi,
As far as i understood there is no way to know exactly is display in standby mode or not?
I did some tests for now with light sensor ON and OFF (in WM) so here we go (PM is set to 2).
With sensor turned ON in WM:
After going standby screen gone completely off, no glow from backlight in dark environment like it was in previeous kernels and here is an answer to my guess above, screen IS truly going into standby. Also I've noticed some strange behaviour, the debugging led which was intended to go green in standby, randomly (i guess) flashes in around 2 Hz frequency with amber and then stays for 3-4 secs and cycleing like this, no green at all. Returning from standby is not OK, after pressing end button screen is not turning on as expected BUT, after touching at the place where unlock or mute sliders should be screen wakes, so i can assume that after pressing end button screen is just not turning on but touch panel does. Wake on call works as before, as like as wake from HWkeyboard slide (both with 2-3 sec delay). Shutdown actually turn the phone OFF.
It seems With sensor turned OFF in WM, phone acts same way.
I was testing with Matthew's RAR - Android v2.2 Froyo: BLAZN from Aug 30, 2010
Click to expand...
Click to collapse
Yeah its a common problem for now we are investigating this.
So i have a confirmation that the screen is really powered off?
Anyway guys try putting 1 into pm_sleep or deleting it from startup.txt (i recommend the 2nd choice ).
I ran into an interesting problem however I did not see the previous post...
Several time it went into standby (I assume) and the screen was pitch black meaning the backlight was not on. To get it out of standby, I woul click the end button like normal. after a couple of hours I pulled the phone out of my holdster, and it was abnormally hot. I do not have an overclock and my pm sleep is set to 1. I did not press the screen to see if it would respond so maybe that is what was being mentioned in the last post. None of the buttons would bring it back to life and the LED was amber and solid, where typically it would flash with this new zimage and modules. I will try to get it back to that state and see if I can click the screen even though it is dark. One thing that worries me is the battery though. Could this be damaging to it? Even when I did have it overclocked it never reached that temperature.
Anything else I can do to help troubleshoot?
EDIT: Sorry, forgot to mention I am on a Sprint RHOD400
I'm on the RHOD400 model, no OC, pm_sleep=1
Couldn't really get it to be stable, had to switch back to WinMo for the day (and trust me, that's desperation ). Once restarted in my pocket without any interaction on my part. I would press the end key to turn on screen, and had it auto reboot at that point as well. Also got a "sleep of death" twice and had to restart. While in your kernel I didn't have notification LEDs as well (not even for power events), vs the guy above that had blinking red.
I'm sure you'll get it eventually, keep up the hard work!
Hi!
Any news? Are we gonna wait for new kernel with committed code or it development is stalled?
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
UPD: There is a parial fix for this issue by Maruzko by installing an app that prevents deep sleep (but thats battery consuming offcourse).
I think that there should be some internal fix for this issue, only devs can help up with that.
UPD2: My opinion that problems that people have with clock not synced is somehow connected, coz when you turn on the phone in that state, you see the clock changing rapidly and stopping at wrong time, so changed title to include that also.
UPD3: There is an alternative way to fix the issue, but not much tested. Thanx to sideshow03.
Tests and reports are much appreciated.
Hey! I'm having the same issue as you. I'm surprised no one came up with a solution yet.
kekehi said:
I'm surprised no one came up with a solution yet.
Click to expand...
Click to collapse
Yup, me too. Currently at miui based on pac rom, havent noticed the issue, but cant be sure its really gone, or just "lucky time" until reboot.
Sent from my SGH-I927 using xda app-developers app
I'm having the same issues on a couple roms but later on today I'll flash CM10.1 and see if it goes away...
Just did with cm10.1
im in the club
braintweaker said:
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
Click to expand...
Click to collapse
I have the same 'No response to a call' issue after flashing AT&T UCLJ3 rooted on a Rogers i927R Glide.
Essentially, after the Glide has been idle for a while, not sure how long, at least 30 mins I think,
there is no response from the Glide when calling it, and it goes to voice mail, but not straight away though.
I can hear a ringing tone from the phone I'm calling from, but the Glide just sits there in sleep mode.
Try several calls but the Glide does not wake up.
Haven't tried sending it an SMS when this has happens though.
If I then wake up the Glide manually, and then put it into standby again and call it, it responds as normal and starts ringing.
The thing is, it doesn't happen every time, sometimes the phone could be idle for 2 hours and still respond to a call, others times it doesn't after say 30mins on standby.
Hard to troubleshoot as its so intermittent.
This did not seem to happen on stock Rogers GB.
braintweaker said:
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
Click to expand...
Click to collapse
Should this thread be merged into this one ?
http://forum.xda-developers.com/showthread.php?t=2057948
Yup, the threads are the same, but mine is older
Sad thing - cm and other jb roms higher than 4.0.4 have the issue aswell
Currently have the 312 min value with interactive governor - this does not help, some deep sleep problem not frequency related
braintweaker said:
Yup, the threads are the same, but mine is older
Sad thing - cm and other jb roms higher than 4.0.4 have the issue as well
Currently have the 312 min value with interactive governor - this does not help, some deep sleep problem not frequency related
Click to expand...
Click to collapse
It doesnt appear to be just a Glide problem with ICS from internet searching but there doesnt appear to be a solution anywhere.
I found a reference to using an App called Wake Lock which some have found may fix it but at the cost of some battery life.
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDMsImV1LnRoZWRhcmtlbi53bCJd
Choose PARTIAL_WAKE_LOCK in the config apparantly.
Ive installed it but not activated it yet.
Still testing with WiFi sleep policy set to "Only when plugged in", where as previously I had it set to "Always".
Anyways, there are devices on ICS that do not have such issue. May this be connected only with the tegra2 platform? Even have no idea how is this issue called to search.. sleep of death? As i know, its the state, when device does not wake at all, even after pressing power. Not our case.
braintweaker said:
Anyways, there are devices on ICS that do not have such issue. May this be connected only with the tegra2 platform? Even have no idea how is this issue called to search.. sleep of death? As i know, its the state, when device does not wake at all, even after pressing power. Not our case.
Click to expand...
Click to collapse
Good point, maybe it is to do with the Tegra 2 platform or the sub revision of this ICS 4.0.4.
Yes, 'sleep of death' seems something different, when ieven the power button does not wake it.
I think our issue is referred to as not coming out of 'deep sleep' when a call/sms is supposed to wake it up.
Yesterday I had WiFi sleep policy set to be on only when on charge.
So all day I was on 3G data not WiFI. I called the Glide intermittently through out the day and it always woke up.
Today going back to normal setting of WiFi Always on to stay connected to an access point when in sleep mode. Will see how that goes.
Next I'll try:
https://play.google.com/store/apps/...t#?t=W251bGwsMSwxLDEsImV1LnRoZWRhcmtlbi53bCJd
Choose PARTIAL_WAKE_LOCK in the config apparently.
I don't have any issues with that.. sounds like a sysctl or build.prop mod though.. that's all I have changed myself without the community here.. everything works well in ICS and I do run litekernel 1.1.1 which may also be a + for the no hang issue
Maruzko said:
I have the same 'No response to a call' issue after flashing AT&T UCLJ3 rooted on a Rogers i927R Glide.
Essentially, after the Glide has been idle for a while, not sure how long, at least 30 mins I think,
there is no response from the Glide when calling it, and it goes to voice mail, but not straight away though.
I can hear a ringing tone from the phone I'm calling from, but the Glide just sits there in sleep mode.
Try several calls but the Glide does not wake up.
Haven't tried sending it an SMS when this has happens though.
If I then wake up the Glide manually, and then put it into standby again and call it, it responds as normal and starts ringing.
The thing is, it doesn't happen every time, sometimes the phone could be idle for 2 hours and still respond to a call, others times it doesn't after say 30mins on standby.
Hard to troubleshoot as its so intermittent.
This did not seem to happen on stock Rogers GB.
Click to expand...
Click to collapse
I'm running CM10.1 and not having this issue.
I did notice something though.
Hypothesis: Each ICS leak came with a different baseband. So there is an I927UCLG9 baseband, a I927UCLH2 baseband, and a I927UCLJ3 baseband. UCLJ3 introduced some ABI change that the libsec-ril we're using in AOSP ROMs doesn't know how to handle (or it straight up just has a bug).
I currently have the I927UCLH2 baseband as I never flashed UCLJ3.
Could someone more wizardlike than me whip up some baseband-only Odin images for testing?
---------- Post added at 02:18 PM ---------- Previous post was at 02:15 PM ----------
braintweaker said:
Anyways, there are devices on ICS that do not have such issue. May this be connected only with the tegra2 platform? Even have no idea how is this issue called to search.. sleep of death? As i know, its the state, when device does not wake at all, even after pressing power. Not our case.
Click to expand...
Click to collapse
"Sleep of death" already has an established meaning. It means there's an intermittent whole-system freeze that only happens when the device is in standby, giving a "dead" appearance. It's been the bane of Kindle Fire developers for some time now.
I'd call this "no radio wake" personally.
roothorick said:
Could someone more wizardlike than me whip up some baseband-only Odin images for testing?
...
I'd call this "no radio wake" personally.
Click to expand...
Click to collapse
Nice term, tottaly agree.
I just can say, that I have tested the lite rom, based on 4.0.4, that has a baseband chooser in aroma installer. I've tried running it with a baseband from 2.3.6 stock rom (that was my only hope), that did not give any difference, radio still did freeze Anyway, I cant be sure I did everything right that time, and your way of solving this must be tested.
Also, my thoughts are about some ATT frequency specific things, as I cant say everybody here is complaining (most are from North America, right?). May this be caused by using glide outside of US and Canada?
braintweaker said:
Nice term, tottaly agree.
I just can say, that I have tested the lite rom, based on 4.0.4, that has a baseband chooser in aroma installer. I've tried running it with a baseband from 2.3.6 stock rom (that was my only hope), that did not give any difference, radio still did freeze Anyway, I cant be sure I did everything right that time, and your way of solving this must be tested.
Also, my thoughts are about some ATT frequency specific things, as I cant say everybody here is complaining (most are from North America, right?). May this be caused by using glide outside of US and Canada?
Click to expand...
Click to collapse
That's quite possible, as I'm on AT&T towers even though I don't have service through them (I'm with a prepaid MVNO) and I'm not having problems.
roothorick said:
That's quite possible, as I'm on AT&T towers even though I don't have service through them (I'm with a prepaid MVNO) and I'm not having problems.
Click to expand...
Click to collapse
I'm also on AT&T towers but I don't have service through them, I'm with a prepaid MVNO just like you but I'm having these problems
yivkhar said:
I'm also on AT&T towers but I don't have service through them, I'm with a prepaid MVNO just like you but I'm having these problems
Click to expand...
Click to collapse
What is your baseband version (under About Phone)?
roothorick said:
What is your baseband version (under About Phone)?
Click to expand...
Click to collapse
I927UCLJ3
braintweaker said:
Well, for the moment ICS (any version) is making my phone unusable as a phone itself.
I saw some people complaining about the GSM hangups (including me), so if you let the phone sleep, you wont recieve any call. The caller will hear the same tones, as if you dont pick up the call. If you send an sms on a phone in such state, it will only appear after turning it on manually (often having duplicate SMS). When you turn the phone on - you wont even get a missed call, no signs of anything.
This problem is very hard to reproduce, it happens from time to time.
I've tried to flash any other ICS based rom on the phone - any has the same problem. The only rom i hadn't such issue is 2.3 stock/modified. But i want ICS!
Anyone have any thoughts, what can be causing this? I'm tired of this happening, people complain that the cant tell me something urgent, and i dont even know they wanted to.
Click to expand...
Click to collapse
I'm having this issue too ;(
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
its called sod, sleep of death. its a common problem with 4.2.1 kernel source. just about everyone has experienced them, some a lot more than others, root and not rooted, custom rom/kernel and stock. google needs to fix it in its source. there are some anecdotal fixes, some claim work, others say dont work.
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
063_XOBX said:
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
Click to expand...
Click to collapse
im loving 4.2.1, cant say that i have any real issues with it. but, i do get sod occasionally, about once every ten days or so. if you around the forums, just about everyone has experienced them. some get them several times an hour, some several times a day, some several times a week, some just have had sod once or twice total. every device is different, they will have differing experiences.
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
just go back to 4.1.2 if you are having issues.. 4.2.1 is a hit or miss IMO, some ppl get issues while for others it works great
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
bk201doesntexist said:
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
Click to expand...
Click to collapse
Interesting idea. I never use it and have never had any issues.
i never use bluetooth, but have had sod.
Same here.
063_XOBX said:
Interesting idea. I never use it and have never had any issues.
Click to expand...
Click to collapse
I've had issues with BT on 4.2.1 (OTA), turned it off after a) sending first file OK b) second file fail, and it stuck on " turning off".
Read below.
simms22 said:
i never use bluetooth, but have had sod.
Click to expand...
Click to collapse
dakota.breeden said:
Same here.
Click to expand...
Click to collapse
I've experienced a "black screen" on 4.2.1 (OTA), due to what i think was a crash from XDA app, probably from using it with an ad blocker, at least from what i could see. I could adb shell to the device, remount system, no problem. I've removed the ad blocker from the system, while still on 4.2.1 (OTA), and have not experienced the "black screen of death" again.
I have not experienced a "sleep of death" yet on this device. Note: definition of sod from my galaxy s days: device is in a state (after going into deep sleep) in which the only way to get it back is pulling the battery out. System is unresponsive.
I've flashed JOP40D through stock images, and haven't seen black screen/sod scenarios, recreating the same system, more or less.
As i rarely use BT, i haven't tested it again, but we shall see.
Op, what apps do you have installed? Do you use SR/AVS? If not, please raise voltages by 50mv at each step, or at least the lowest and highest step, for mpu, core and iva.
While the device is in this state, no communication is possible? Can you logcat? dmesg? Can you receive calls?
Sent from my i9250
I have not had that issue or any SOD and I am running CM10.1 with LeanKernel, my wife runs the same setup and she also has not had any issues.
I've seen SoD's on Jellybro CM10.1 with ZenSERIES kernel v14.1, but only when using the ZenX governor. If I change to Pegasusq, the SoD's stop. I guess ADA is still working out some of the kinks in ZenX. Ooo, and it looks like v15 was released a few days ago. Something new to flash.
Is it a bug?
Ripshock said:
Is it a bug?
Click to expand...
Click to collapse
Nope... it's a state to where the device "goes" after a certain amount of inactivity in order to save battery, turning off all that is not necessary... keeping the minimum working so you can receive calls, sms and (i'm not sure about this) pushing notifications.
It's not a bug... it's a good thing when works correctly, when it come to enter into it and getting off
ps. Forgive my english
RockasKane said:
Nope... it's a state to where the device "goes" after a certain amount of inactivity in order to save battery, turning off all that is not necessary... keeping the minimum working so you can receive calls, sms and (i'm not sure about this) pushing notifications.
It's not a bug... it's a good thing when works correctly, when it come to enter into it and getting off
ps. Forgive my english
Click to expand...
Click to collapse
Thanks for the response. I thought it was a bug because some guys with their roms consider it as an issue but idk why after what you have told me? So tell me when it's a bug?
I guess it's probably when the device just doesn't come out of it correctly, hardware failures, services that don't restart, etc...
Sometimes it becomes, apparently, an issue, also when some applications or services don't allow the device to enter deep sleep... hence the battery drain issues or others similar.
I hope someone better informed than me and with more knowledge can explain you in a better way.
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…)