Related
I wasn't sure where to put this but any help would be appreciated. Lately my phone gets extremely hot, I'm running froyo 2.2 latest built. And I'm running launcher pro home replacement replacement with only 5 screens. And I have battery indicator telling me right now that the temp of my phone is 105.1F. How do I find out which app(s) is making my phone heat up?
Try looking at what's eating your battery then go from there.
It shows my display at 86% and android system at 8% those are the highest using battery...my backlight is at 50% brightness...would Anyone recommend having that set to auto brightness?
i have my n1 set to auto and it still gets pretty hot. i have not had any issues with it over heating though so maybe give it a try. also, are you running a task killer? ive got security set to low, and it auto kills apps every 30 minutes or so. it seems to help out a bit, saves battery too.
I've had this problem since I updated to Froyo.
After a while, the data connection seems to be used -constantly-
and I really mean -constantly-, I'm also running Launcher Pro - So maybe there's something there?
As an earlier post said, the Screen appears to be the top "battery" user when looking at the battery stats (I've found these to be EXTREMELY unreliable though )
My screen is set to Auto, so I doubt that's where the problem is.
Also, in my case, it's the very bottom of the phone that gets hot (I believe that's where the antenna / actual chipset for the radio is?)
One thing I've found that "helps" so far, is to disable account sync, then re-enable it. Apparently that's what's causing an overuse of 3G for me. This only helps in some cases though.
Usually I just turn off data completely for a few seconds and re-enable it.
Any "tips" on what could be using that much data all the time (Maybe it's not even using the data, but just somehow trying to keep a single connection alive?) would be greatly appreciated. I'm honestly not sure here!
Any ways, that's what I've found out "so far".
/T0yK4T
Thanks for all the feedback and tips I will try all these things. But I agree and ever since I upgraded to froyo it gets extremely hot. And I'm running launcher pro but I tested it with the stock launcher and still gets hot....who knows....
I'm having the same issue on my nexus. I have a custom rom with stack kernel and ADWLauncher with 3 screens and brightness on auto.
What should i do?
Sent from my Nexus One using XDA App
Run System Panel, it'll show you any apps using CPU, and network stats.
Something is clearly wrong with your phones/config/cache/something, my Nexus One stays ICE COLD all of the time even with K9 mail with push IMAP, weather syncing, GPS uploading to my website every 10 minutes, etc..
Hi,
i noticed months ago the following on my IDEOS X5 (german) concerning bad battery life. It could be the reason why there are so many different reports regarding bettery lifetime of the U8800.
First - why did I start to investigate: because the phone sucked about 5-10% per hour while not beeing used / lying on my desk, so after max 20 hours the battery was empty. But this did/does not always happen....
What I did: it took some time to get used to android (its my first droid) and learn how to troubleshoot. A month after I got this phone I learned that the GSM-code *#*#4636#*#* will show you very useful information concenring battery/phone usage. I started to play around with the phone (factory reset, install/remove apps, enable/disable different options like 2G/3G/WLAN etc...) always keeping an eye on the 4636-infos.
Result: When I use WLAN the phone simetimes enters an "state" when it never again enters "sleep state" and the battery gets sucked as stated above. I switched off WLAN for a week and this did not occur while standby time increased to 48 hours and 4636 stated an "phone awake" percentage of below 20% (normal usage). Once I reenabled WLAN again it took about an day of WLAN usage to reproduce the bug and "phone awake" time increased to 100% while standby time decreased to below 20 hours. ONLY rebooting the device recovers from this "state". I further noticed that this does not happen if just WLAN is available but no 2G/3G (phone had no SIM). My conclusion is, that the
"You May Be Charged"-Popup is the culprit. It does lock the phone to this "state" for some reason, mybe when the WLAN connection is dropped while the phone is not used (traveling). Can someone reproduce this on his phone (maybe not german)?
Resolution: IMHO none. I send the device twice to reseller for service. First time the complete mainboard was changed without success regarding the battery drain. Second time nothing was done - they just returned the device to me.
Thanks.
This is a known problem, that already has a thread...
http://forum.xda-developers.com/showthread.php?t=1043760
This is affecting ALL Froyo Roms, if you want battery life, install Oxygen or CM7...which are based on Gingerbread.
There is no point in discussing this issue anymore, this is a very well known problem and Huawei doesn't care.
Sending the phone back to manufacturer won't help at all.
Thank you for the hint - it realy looks like the same issue. Knowing more about the nature of this issue could give people not willing to install custom roms a possible solution. Can someone move this thread over to that one?
katu2006 said:
This is a known problem, that already has a thread...
http://forum.xda-developers.com/showthread.php?t=1043760
This is affecting ALL Froyo Roms, if you want battery life, install Oxygen or CM7...which are based on Gingerbread.
There is no point in discussing this issue anymore, this is a very well known problem and Huawei doesn't care.
Sending the phone back to manufacturer won't help at all.
Click to expand...
Click to collapse
But Huawei is about to release official 2.3 in Q3 atleast I hope...
andreasha said:
But Huawei is about to release official 2.3 in Q3 atleast I hope...
Click to expand...
Click to collapse
Everyone is looking forward to official 2.3, but we'll have to wait and see if the "sleep" bug will be sorted.
katu2006 said:
Everyone is looking forward to official 2.3, but we'll have to wait and see if the "sleep" bug will be sorted.
Click to expand...
Click to collapse
I hope some more bugs are straightened out like headphones and internal mic at the same time. Headset button to work. Battery time!
none of my android phones could use the phone's mic when headphones were plugged in
I saw a solution for the mic-with-headphones-problem a few days ago, either here or at modaco (do not know if it is confirmed working though).
fajabird, I know that you want this to work with the ROMs provided by Huawei. Huawei obviously does not care too much about providing the community with updates (they do not even have gingerbread-support by now). This is the downside of this low priced phone.
Let me just say this: It took me about one hour to understand the ultimate-guide at modaco. It took me another hour to decide which ROM I want to use. If anything goes wrong at the installation I can easily start over again. Now I have a fully working phone with Android 2.3.5 with a battery that lasts at least 2 days, sometimes 3(if I do not play any games within that time). Of course I understand that you are probably very pissed at Huawei for providing a ROM with a bug that serious.
if you find that fix again, let us know where to look
darkado said:
if you find that fix again, let us know where to look
Click to expand...
Click to collapse
It is to be found at the Android-development-section, right here. Note that you cannot use the mic of your headset after applying this
too bad, it would be awesome to be able to use both
XphX said:
I saw a solution for the mic-with-headphones-problem a few days ago, either here or at modaco (do not know if it is confirmed working though).
fajabird, I know that you want this to work with the ROMs provided by Huawei. Huawei obviously does not care too much about providing the community with updates (they do not even have gingerbread-support by now). This is the downside of this low priced phone.
Let me just say this: It took me about one hour to understand the ultimate-guide at modaco. It took me another hour to decide which ROM I want to use. If anything goes wrong at the installation I can easily start over again. Now I have a fully working phone with Android 2.3.5 with a battery that lasts at least 2 days, sometimes 3(if I do not play any games within that time). Of course I understand that you are probably very pissed at Huawei for providing a ROM with a bug that serious.
Click to expand...
Click to collapse
Hi, thank you for sharing your experience with me. I always wanted to update to some custom roms but the time I started investigating this issue there was no stable one out there. On the other hand I thought there might be a dev interessted in more details regarding this issue helping him to sort out this nasty bug for whatever reason.
Can someone tell me, if his U8800 also has the ambient light sensor but like mine does: it won't reduce the brightness, just increase works. Thanks.
fajabird said:
Hi, thank you for sharing your experience with me. I always wanted to update to some custom roms but the time I started investigating this issue there was no stable one out there. On the other hand I thought there might be a dev interessted in more details regarding this issue helping him to sort out this nasty bug for whatever reason.
Can someone tell me, if his U8800 also has the ambient light sensor but like mine does: it won't reduce the brightness, just increase works. Thanks.
Click to expand...
Click to collapse
Mine reduces brightness but does it quite weird sometimes like adjusting several times without the light around me changing...
Mine always adjusts it way too low. If I am inside the brightness is always on minimum. I use the power-widget on the homescreen. I only change it at night, it is on max. for the whole day (the max. brightness is still kinda low, especially if it's sunny).
fajabird said:
Hi,
i noticed months ago the following on my IDEOS X5 (german) concerning bad battery life. It could be the reason why there are so many different reports regarding bettery lifetime of the U8800.
First - why did I start to investigate: because the phone sucked about 5-10% per hour while not beeing used / lying on my desk, so after max 20 hours the battery was empty. But this did/does not always happen....
What I did: it took some time to get used to android (its my first droid) and learn how to troubleshoot. A month after I got this phone I learned that the GSM-code *#*#4636#*#* will show you very useful information concenring battery/phone usage. I started to play around with the phone (factory reset, install/remove apps, enable/disable different options like 2G/3G/WLAN etc...) always keeping an eye on the 4636-infos.
Result: When I use WLAN the phone simetimes enters an "state" when it never again enters "sleep state" and the battery gets sucked as stated above. I switched off WLAN for a week and this did not occur while standby time increased to 48 hours and 4636 stated an "phone awake" percentage of below 20% (normal usage). Once I reenabled WLAN again it took about an day of WLAN usage to reproduce the bug and "phone awake" time increased to 100% while standby time decreased to below 20 hours. ONLY rebooting the device recovers from this "state". I further noticed that this does not happen if just WLAN is available but no 2G/3G (phone had no SIM). My conclusion is, that the
"You May Be Charged"-Popup is the culprit. It does lock the phone to this "state" for some reason, mybe when the WLAN connection is dropped while the phone is not used (traveling). Can someone reproduce this on his phone (maybe not german)?
Resolution: IMHO none. I send the device twice to reseller for service. First time the complete mainboard was changed without success regarding the battery drain. Second time nothing was done - they just returned the device to me.
Thanks.
Click to expand...
Click to collapse
Hey there friend, I've detailed much of this and been through a lot of troubleshooting. It did not appear to be the "You may be charged" popup as I disabled that whenever I changed ROMs. I never did get a solution for any of the Huawei ROMs, it just seemed like bad code as Dzo pointed out with the WiFi driver.
A very simple solution for me was installing one of the 2.3 ROMs, they are quite stable at the moment, especially Oxygen (although I use MIUI). You will find much better battery life with these.
Best of luck,
Ryan
My stock rom 2.2.1 Shows Android System 97% battery usage and battery drains 50% in 19minutes! With wi-fi, 3g, Bluetooth, everything is off and even i do not use it.
Flash latest official 2.2.2, wait for official 2.3, flash the custom 2.2.2 rom void or flash a custom 2.3 rom. I would recommend flashing the latest 138 or 162 to get the latest modem baseband or manually install the AMSS.bin.
Sent from my Ideos x5
andreasha said:
Flash latest official 2.2.2, wait for official 2.3, flash the custom 2.2.2 rom void or flash a custom 2.3 rom. I would recommend flashing the latest 138 or 162 to get the latest modem baseband or manually install the AMSS.bin.
Sent from my Ideos x5
Click to expand...
Click to collapse
I can't because phone do not use my external SD card somehow. In android i see files but in recovery-it does not use external sd.. I ask in forum why-but nobody answers
Backup ur data on it and format it. If that doesnt work ill send you a guide how i fixed mine, its just a partition error.
Sent from my Ideos x5
andreasha said:
Backup ur data on it and format it. If that doesnt work ill send you a guide how i fixed mine, its just a partition error.
Sent from my Ideos x5
Click to expand...
Click to collapse
I formated it via phone, then via PC - it works in powered on phone in android, but in recovery it doesn't it only sees sdcard as internal memory, if i try mount sd-ext shows error, can't mount.
Also i have problem if i use pc to copy some files to internal memory-phone switches storage mode OFF! and i can't copy files to internal 2GB memory..strange
Heyo bros so I'm experiencing what I'm afraid might be a problem:
I've been getting watchdog alerts regarding the "Base System" process. It notifies me that the CPU % at the time of the captures range from 40% to 60+%. Coincidence or not, it usually happens when I wake my phone from sleep- not when I unlock it, just when I press the power button. The moment the lock screen pops up, the phone's already vibrating and the watchdog notification is up in the status bar.
Battery life so far is:
9h 22m @ 74%; Phone Idle- 56% | Cell Standby- 22% | Display 17% (40m) | Android OS 3% | Voice calls- 3%
Who knows, maybe this^ looks normal. I just want to be sure.
I've heard talk of 'wakelocks' but I don't know exactly what they are, what might cause them, and how I can track them.
I'm currently running:
Atrix 4G (not 2, just for clarification)
CM7 xB^xN
Baseband reads: N_01.77.30P
Kernel version reads: 2.6.32.39-MB860-GB-Faux123-v0.2.1 [email protected] #14
Build number: GWK74
Totally honest, I don't know if that might be able to help diagnose the problem, but for what it's worth, I want to check two things:
1) I flashed Faux's enhanced stock CM7 kernel, and am pretty sure it took, but does that look to be the proper kernel version? I just want to be sure.
2) While I also flashed the "latest radio" in the CM7 xB^xN thread, I was certain there was an xx.97 radio (vs the x.77 radio that mine appears to currently have). Am I indeed on the latest radio version?
Would it hurt to reflash these two? Could either one, or maybe both, be the cause of this?
It also occurs to me: I've been using SetCPU and have ONE profile set up that forces my CPU to min/max 216/216 when the screen is off. Could that be causing it?
Thanks so much for any and all insight bros. Also, please let me know if there's any more info you might want to help diagnose what the dealio is.
Heyo guys,
I hate to bump this kinda soon, but this is definitely a problem.
It's getting to be that I don't even have to wake the phone up for the Base System to spike. I was woken up a couple times in the middle of the night by notifications saying it was really high.
You guys have any thoughts? I'd really like to get this resolved as CM7 is AWESOME.
Yes, you guessed it- I'm not anal about the fingerprint scanner or webtop. Just a stable and fully functional release.
Thanks for any help bros I really appreciate it.
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
AX-MA said:
Hi, new member here.
I get the same weird spike to 50-60% (and was woken up too in the middle of the night by watchdog). I have narrowed this occurrence to when I have both Watchdog & Juice Defender enabled at the same time. (Yeah it took me a while to figure out)
When I disable Juice defender the problem seems to go away. So I'm thinking one of the power saving settings turns the radio off & a core system process really does not like that.
This is on a non-rooted Atrix, I have not tested on a rooted Atrix.
So far I had to turn off the watchdog alarm so I can sleep. If anyone can think of a solution it would be appreciated!
Click to expand...
Click to collapse
Thanks for the insight bro. For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Looks like a couple of us are having problems then, though. We'd both really appreciate any info, advice, or help.
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
xyrovice said:
For what it's worth, I'm not running Juice defender, or any other kind of battery saver app.
Click to expand...
Click to collapse
AX-MA said:
Ok, it seems it was just a coincidence with Juice Defender then.
The problem may be unrelated to power savings, but it is indeed a problem.
Click to expand...
Click to collapse
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
WiredPirate said:
It doesn't have to be unrelated to power saving just because xyrovice is not running Juice Defender, there is a option for power saving in the battery settings for the Atrix that does a similar function.. Before ruling out power savings as unrelated I would make sure xyrovice is set to "performance mode".
Click to expand...
Click to collapse
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
xyrovice said:
I'm running CM7 and skimmed through the settings menu and didn't find anything about 0ower features. I know that in Blue ROMs there's the battery manager section, but I don't think CM7 has this. Anything else I should look at, though?
Thanks for the insight too bro.
Click to expand...
Click to collapse
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
WiredPirate said:
oIc, no I dont guess you will have those settings in CM, I should have thought of that. I wish I could help because I had the exact same prob with Watchdog constantly alerting for "Android Core Processes" and "Android Media processes", but I dont get those alerts anymore. I haven't changed ROMs or anything.. The only thing I can think of is I changed the MinFree values, I used the app "AutoKiller Memory Optimizer" to change them.
Click to expand...
Click to collapse
Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
Also, is there any reason CM7 would have the minfree set to a default that causes this?
Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Thanks so much for saying this bro. Who knows, this might be the problem.
PS: I just tried this and am going to see if it works. Post #13 is the one that would really sum up my reaction of successful.
Hopefully maybe this helps my other bros.
xyrovice said:
1Do you know why that seemed to solve the problem...or if it even WAS the problem, per se?
2Also, is there any reason CM7 would have the minfree set to a default that causes this?
3Lastly, what did you alter the minfree values to? You think ROM toolbox might have this capability?
Click to expand...
Click to collapse
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
possible solutionary steps I've taken:
So Update:
I actually ended up checking out my (partial) Wakelocks with betterbatterystats, and I think I may have found a problem (diagnosed with alarmdump.txt from the Alarm Manager):
1) When I first flashed CM7 I thought, "Oh well why not really get comprehensive about keeping apps up to date" and I actually, for every single app, checked the "Automatically update" box in each one's market page. This led to a CATACLYSMIC wakelock that I'm now pretty sure could be the problem.
2)Google talk also seemed to be a little active with the screen off so I unticked the "sign me in auto..." box and made sure I signed out.
Lastly (not related to wakelocks), I checked on my TTS settings (see my last post about that).
Oh also LASTLY lastly I froze the modem fastdormancy manager in TiBU (kinda just for ****s and giggles). That said though, is the consensus on this that it's pretty harmless?
So, other bro who was having a problem, check and see if this might help you at all AYY
WiredPirate said:
1.) no I can't say for sure what the problem was or why I no longer get the Watchdog alerts. I was just trying to think what I have changed since they stopped because I haven't changed ROMs.. Since changing the MinFree has to do with how many or what apps are left running I'm just kinda throwing it out there as a possibility since your at a loss for things to try.
2.) no I can't think of any reason, and most with CM don't have this prob right..?
3.) It's posible it does have the capability because it does allot but I am not sure.
Foreground 12
Visible 18
Secondary 36
Hidden 121
Content 129
Empty 137
Click to expand...
Click to collapse
Thanks for posting this. I checked ROM toolbox and it does indeed have the capability. That said, if my aforementioned possible solutions don't work, I'm turning here. Thanks for the info bro.
Watchdog is flagging the "base process" app because IT IS using over 60% of your CPU BUT it is using 60% of your CPU that is running at 216MHZ.
It's your screen off setcpu profile of 216/216, if you bump up the max to 456 the alert will go away. When you have it set as 216/216 Watchdog (I believe) thinks that is the actual max cpu speed and bases its percentages off of that. I got that warning before and after a bit of troubleshooting (actually tried several different things) found that was the problem.
I am not sure but if you "whitelist" a app in watchdog it might ignore it as well. However my alert level was set at 80% and it would still set it off, so I think the higher speed might just be better.
[Solved] [Q] Battery drain due to "am2server" and "aes1750" on CM7
Hello.
Lately after flashing CM7 weekly #4 (Dec 10), I noticed that sometimes my battery drains rather quickly and nothing unusual is shown in "Battery use" (The phone is awake a lot more than the screen is on but "that's normal" I guess).
After a bit of digging around I found, using android terminal and the top command, that the processes " /system/bin/am2server" and "aes1750" are at 50% CPU each.
Rebooting the device helps for a while and they go back to 0% each, but after a seemingly random amount of time they go back to 50% each.
Killing the processes with "kill" or "killall" does nothing at all (with root permissions of course).
Searching XDA site and with google gave no relevant results, mostly something about Intel vs AMD and "am2 servers".
Since I have no idea what those process do, I can't provide any relevant information.
I can add that this problem wasn't there with Ba2tF.
Also since weekly #4 has finger print support, which by the way doesn't really work for me*, I am guessing this is related to it but no way to confirm.
* I can set FP for the lock screen after a full wipe and it works fine, after a while I can no longer unlock the device with the sensor and then pressing "Settings > Device settings >Fingerprint sensor navigation" and the fingerprint option in lock options do nothing (no error, just nothing.)
Any help or pointers would be highly appreciated.
masmddr said:
Hello.
Lately after flashing CM7 weekly #4 (Dec 10), I noticed that sometimes my battery drains rather quickly and nothing unusual is shown in "Battery use" (The phone is awake a lot more than the screen is on but "that's normal" I guess).
After a bit of digging around I found, using android terminal and the top command, that the processes " /system/bin/am2server" and "aes1750" are at 50% CPU each.
Rebooting the device helps for a while and they go back to 0% each, but after a seemingly random amount of time they go back to 50% each.
Killing the processes with "kill" or "killall" does nothing at all (with root permissions of course).
Searching XDA site and with google gave no relevant results, mostly something about Intel vs AMD and "am2 servers".
Since I have no idea what those process do, I can't provide any relevant information.
I can add that this problem wasn't there with Ba2tF.
Also since weekly #4 has finger print support, which by the way doesn't really work for me*, I am guessing this is related to it but no way to confirm.
* I can set FP for the lock screen after a full wipe and it works fine, after a while I can no longer unlock the device with the sensor and then pressing "Settings > Device settings >Fingerprint sensor navigation" and the fingerprint option in lock options do nothing (no error, just nothing.)
Any help or pointers would be highly appreciated.
Click to expand...
Click to collapse
I had the same problems. I think it's because I went from a previous non-FP enabled build without wiping then all the subsequent FP builds had this issue. Data wipe fixes it is all I know, I'm afraid.
Thank you for replaying.
I moved from Ba2tF without a full wipe and anything related to the FP didn't work, trying to set a lock screen returned a couple of errors.
But afterwards I did a full wipe and reapplied the zip of weekly #4.
This fixed the FP sensor for about 20 minutes, I eventually gave up and decided to wait for CM9; hoping it will work better then.
I am much more interested in the battery drain.
I don't want to go back to Ba2tF because I like scrolling with the sensor and I find it very useful.
Edit : seems that the problem was "fast reboot " application.
Stopped using it and so far am2server and aes1750 are acting normally, plus the FP scanner works fine.
Sent from my MB860 using XDA App
Hi all,
I know this is an old question, but all my googling thru online forums led to nothing conclusive yet, other than non-working suggestions or using apps. But having to live with this dimming thing is bothering and exhausting !!! Simply said, there aren't any useful settings. Max display timeout in my phone is 10 minutes but, no matter which value I pick, after some seconds my display gets dimmed. And the developer option "stay awake" serves no purposes aswell... it just prevents the screen from going to sleep completely when under charge, but still dims after few seconds of inactivity. Is there any trick to finally turn this infamous auto-dimming off ?? IF I CAN, I would like to achieve this result WITHOUT using any apps, if possible. Oh my J5 is rooted of course, I can even tamper with system scripts or variables, if u instruct me on how to do.
Thanks !
ElenaXX said:
Hi all,
I know this is an old question, but all my googling thru online forums led to nothing conclusive yet, other than non-working suggestions or using apps. But having to live with this dimming thing is bothering and exhausting !!! Simply said, there aren't any useful settings. Max display timeout in my phone is 10 minutes but, no matter which value I pick, after some seconds my display gets dimmed. And the developer option "stay awake" serves no purposes aswell... it just prevents the screen from going to sleep completely when under charge, but still dims after few seconds of inactivity. Is there any trick to finally turn this infamous auto-dimming off ?? IF I CAN, I would like to achieve this result WITHOUT using any apps, if possible. Oh my J5 is rooted of course, I can even tamper with system scripts or variables, if u instruct me on how to do.
Thanks !
Click to expand...
Click to collapse
It sounds like a problem with the Rom. What rom u using ?
Sent from my Honor 8 using XDA Labs
ElenaXX said:
Hi all,
I know this is an old question, but all my googling thru online forums led to nothing conclusive yet, other than non-working suggestions or using apps. But having to live with this dimming thing is bothering and exhausting !!! Simply said, there aren't any useful settings. Max display timeout in my phone is 10 minutes but, no matter which value I pick, after some seconds my display gets dimmed. And the developer option "stay awake" serves no purposes aswell... it just prevents the screen from going to sleep completely when under charge, but still dims after few seconds of inactivity. Is there any trick to finally turn this infamous auto-dimming off ?? IF I CAN, I would like to achieve this result WITHOUT using any apps, if possible. Oh my J5 is rooted of course, I can even tamper with system scripts or variables, if u instruct me on how to do.
Thanks !
Click to expand...
Click to collapse
On my J5 screen never gets dimmed unless the display is turning off due the timeout.
There are apps which can dim the screen, including apps which "save battery". Maybe you have a kind of this app which does this?
Your screen turn off after 10 minutes or after the screen gets dimmed?
It seems a very common and complained issue between Android users from what I read here and there, so more a wanted feature by the original developers than a rom bug... not sure if u are referring to Android version, it is 5.1.1 Kernel id 3.10.49-787809.
No of course I haven't any energy saver apps installed or such things.
All system energy saving options are disabled already.
My phone dims the screen after abt 10 seconds, no matter how long I set the timeout
Oh it suxxxxxx... !!!!
ElenaXX said:
It seems a very common and complained issue between Android users from what I read here and there, so more a wanted feature by the original developers than a rom bug... not sure if u are referring to Android version, it is 5.1.1 Kernel id 3.10.49-787809.
No of course I haven't any energy saver apps installed or such things.
All system energy saving options are disabled already.
My phone dims the screen after abt 10 seconds, no matter how long I set the timeout
Oh it suxxxxxx... !!!!
Click to expand...
Click to collapse
Go in download mode and tell me if ur screen is still diming
I tried... it is NOT dimming in download mode... but it's obvious isn't it ? Only some minimal kernel portion is ran there, not the whole OS with all its power saving features etc...