Related
Hello all. Kinda new here, but I've been flashing my hero with roms from here for a while now. My latest attempt at a good rom is the VillainROM 12.0.0, this is my first time with a VillainROM, and I don't know if this bug exists in previous versions. In my opinion it is a very minor issue, but maybe not for someone else. I'm not a developer, so I don't know what could be causing it, and I don't know if I should be reporting bugs on the VillainROM site, or here, so I'm going to start here...
I downloaded the ROM from the VillainROM12.0.0 thread...
Install was flawless, worked perfectly.
The ROM runs extremely well in all functions, so no complaints there.
The only issue is a slight (10+ seconds) hang when I press the power button to turn on the screen to unlock it and the WiFi connection has timed out. Other ROMs I've used, including the stock ROM would come out of this sleep mode, and then try to reconnect to the WiFi, and they've done so with flawless success. However, this ROM does not, at least not for a minute or so.
This is how I can reproduce the problem, and it takes a while. I usually plug my phone into a charger at night and let it charge over night, and unplug it in the morning to head off to work or whatever. Once the screen turns on on its own after the external power source is disconnected (which all ROMs have done) the screen is unresponsive, and all buttons are unresponsive. The screen remains lit up on the lock screen stuck for at least 10 seconds, then goes black, then pressing the power button to turn the screen back on will restore the phone to an unlocked state (assuming it remembered the swipe action from when the screen was locked and stuck) but takes about another 5 seconds to come back on. This only happens if I have the WiFi radio on while the phone is sitting idle for an extended period of time (long enough for the radio to automatically go into its sleep mode perhaps?).
Here's the info from my phone...
Firmware Version: VillainROM9.0.0
Baseband Version: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.29-ninpo-freqtwk{AT}titan-dirty-b7a296faninpo{AT}titan #39
Build Number: VillainROM12.0.0
Software Number: 3.32.405.1
Browser Version: 3.1
I'm not sure if this is just a fluke, if I should reflash and see if the problem persists. Anyone else able to reproduce this?
Again, if this is the wrong forum, please feel free to move it, and thanks XDA, this site is an awesome resource!
PS... I had to replace the at sign with {AT} in the Kernel Version due to Forum restrictions (It thinks it's an outside URL and I'm too green to be able to do that...)...
Are you running setCPU or OC Widget?
It look likes the lower CPU frequency is too low. Open SetCPU or Overclock Widget and increase it a little.
If you use profiles, in SetCPU:
> Check if you have a "Sleep Profile"
> Check if its frequences are too low.
> If yes, increase it.
It normaly happens when you have a 19Mhz - 2XXMhz on-demand sleep profile.
Increasing that 2XXMhz to 3XX or 4XX may solve the issue.
If not, try to reflash, or use VillainROM IRC at their website.
First your radio is a bit old. Try upgrading to the latest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
Second, especially regarding the wakeup issues, try my kernel for VR12 from here:
http://villainrom.co.uk/viewtopic.php?f=97&t=1928
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Turn up your minimum set cpu speed.
erasmux said:
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Click to expand...
Click to collapse
Pulser has no problems waking up at 19MHz with my kernel. Stable Min/Max frequencies are unique to each phone it has nothing to do with the kernel.
In theory I agree with you completely. But in practice with each kernel I get a different wakeup "performance" using the exact same frequencies. I always prefer setting the min to 160Mhz, but like many many others, in most kernels - including your kernel which comes with VR12 I get heavy wakeup issues which disappear only @ min 480. In other kernels (such as those by Radu) these wakeup issues still exist but are less pronounced (very very rare).
For me and others which have given my kernel a shot there have been no wake up issues @ min 160Mhz. Battery life and responsiveness also improved according to those who have tried my kernel (and optimizations).
BTW "my" kernel is just the HTC official kernel release + OC enable, so its more HTC's kernel than mine.
Like you said it is device dependent, ROM dependent, user dependent, everything.... I am just saying that until now I have not gotten any negative feedback on my kernel, and I think people should give it a shot and decide for themselves. Hopefully they will also be kind enough to share their experiences with me, so if there are problems I can try to fix them.
Thank you all for the suggestions. I do not use any OC utilities, it's the ROM as it was when I downloaded it. Barely any applications installed (some games, auto task killer, handcent...).
I've updated the radio to a version I found in a SenseHero 2.1 thread, but that radio broke MMS and some other data network features. I am in the US, on AT&T (I know, no 3G, but I'm ok with that ), will the radios listed work propperly on this network?
I was also able to reproduce the hanging issue by turning on the WiFi, browsing around the Market, and then exiting the market and turing off the WiFi. It seems that during the switch to the mobile network from WiFi is when something funky happens. Is there a way to get logs to show what might be going on?
First of all try the newest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
If 6.35.15.14 does not work well for you, try either 6.35.15.11 or 6.35.15.01 - If I am not mistaken they are all from the latest HTC release from different parts of the world, so one of them should work well for you.
If you want to get a log for the problem, use the adb logcat. Another simpler option to try and isolate the problem is check if reflashing the ROM (after a backup and a full wipe) solves the problem. Also check if the problem exists in other ROMs.
I have flashed the radio with the latest from the site as suggested (6.35.15.01 was no good when I flashed with that one before, caused all kinds of problems with MMS/SMS, and other network fuctions, but I didn't try that radio with the VillainROM). MMS and such still work, so that is good. I'm going to try to reproduce the other issue tonight, but that may have fixed the issue... I'll update the thread with the results.
Looks like the new radio did not solve the problem. Is the next step the new Kernel?
Sorry for the long delay in response...
The problem is still happening. I have now flashed with a different ROM (Chronos Droid 2.1.2) and the problem persists. However, the lockup doesn't seem to be as bad... Am I the only one with this problem? Should I change my wireless network settings to GSM only? Or leave it on Auto? I'll play around with that and see what happens. It just seems that changing from the mobile network to the WiFi network (and vise versa) is when the problem happens...
Nope, that didn't help. When I went to GSM only, I had no data network connection, and when I went to WCDMA only I had no connection at all. On GSM/WCDMA Only I have both... I wonder if it is something with this phone and the .29 kernel? But then wouldn't everyone here have this problem?
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
I don't see this being a kernel issue, I have a feeling its just a wifi issue on the new rom bases.
m4rk84 said:
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
Click to expand...
Click to collapse
Please let me know what happens.
I did not have these problems using the SenseHero ROMs (older Kernel), only Villain and now Chronos... :S I don't use any OC apps, just leave it all stock from the ROM. If I use one and increase the speed at sleep, (probably an obvious answer) will this drain the battery faster?
Still hanging. Does this have anything to do with wifi's android default sleep behaviour?
I'm having all kinds of lag issues when network queries are starting, especially during MMS/SMS operations. Could be a Handcent update, but the default messager thinger is also quite slow. I'm tempted to go back to an older ROM, this is getting frustrating...
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Sorry, read too quickly your post.
usually is a radio problem that hang the kernel. try with different radio firmware.
I seem to get one of those about 1 or 2 hours after every kernel flash (that may just be a cooincidence though), and maybe once or twice a week as well.
I haven't been able to identify any app or other thing that might have caused it, as they usually happen when I haven't been using the phone for a while.
Info:
Kaiser 130, 23-11-10 l1q1d kernel, Fat Free Froyo RLS5
I thought it might be something to do with the screen turning on (ie wrong panel type), as when it "freezes", the keyboard lights still go on and off when you open the keyboard. I've never been sure if my Kaiser is panel 2 or 3, but it's happened to me on both panel 2 and panel 3 nbhs, so maybe it's unrelated.
That is a known issue with the .25 kernel did it give you backwards text too? What's weird is its only froyo that has that issue these freezes are also why dzo started porting the new one
Sent from my HERO200 using XDA App
I've never seen the backward text. I'll look at rebuilding with the .32 kernel. Interestingly, it doesn't seem to happen when plugged in (so far). It's only happened once today so I may let it roll for a few days and see what it's like.
I observed it too
Adomatic said:
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Click to expand...
Click to collapse
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
have some patience guys, kernel .25 has this issues, and devs are working hard on kernel .32 to solve this problems, this is a linux kernel and has to mount the file system to read it and then unmount it on shutdown, but recently there have been some issues with the unmounting part on the shutdown (like when u just unplug the power cord on a PC and windows restart with the "blue screen") until devs find a solution, its wise to always keep on hand a recent /data backup. Another word of advice: read! i dont want to sound rude, but all this is commented extensively over the forum.... like l1qu1d would wisely suggest: use the search tool!
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
the old kernel only does this with froyo if you still want to use android use n eclair build or donut its not the latest and greatest but they are very stable though
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Adomatic said:
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Click to expand...
Click to collapse
yea not so super is a little bloated if you dont mind a little work fat free is very snappy i just has a blue theme
Okay does any one have this same problem or am i just doing something wrong?
Every time i let my kindle sit with the screen off after about 30 minutes or so, and I assume it keeps going and getting stuck in sleep mode but the only way for me to get it turned back on is to do the whole power button for 20 seconds and then reboot. Am I not being patient enough with it or is there some trick to getting the screen back on that i haven't found yet? Because I've tried multiple different things and there isn't a disable sleep mode option in my rom just the option to extend the time, even though its pretty much useless. But can anyone help me with this?
what rom are you on?
Right now I'm on Hell Fire 1.1 but last week i was running CM9 Reloaded and it did the same exact thing.
I was going to give a long speech about how people need to READ before installing any new roms but considering the Hellfire thread doesn't list what works and what doesn't, I guess it's not entirely your fault
It's called "sleep of death" (SOD). Some ICS roms have problems with it and some don't. The same could be said about certain individual devices. You could boost your minimum CPU usage to 600Mhz or more, or try a different rom. Though, it should be noted that changing your CPU settings will affect battery life.
okay that makes sense i had no idea that most of the new roms have problems with it. but I'll probably try to up the min cpu usage i suppose the difference between 600 MHz and 300 MHz isn't going to be a true killer for the amount i use it but which rom or roms would you recommend? That don't have this problem I'd really like to try barebones but every time i try to flash it my Kindle goes crazy so i gave up on trying with it.
I have perpetually experienced overheating issues while using 4.4-based ROMs; typically while using Navigation as part of Google Maps and while docked in the Galaxy Nexus Car Dock.
My frustration lead to inquiring with some skilled members of the Galaxy Nexus community, including @Ziyan, @freshgiammi, and @aosp. They have indicated that 4.4-based ROMs seem to be afflicted with this problem, but that it might also be tied to the kernel being used.
I have two phones; one running stock 4.3 (Sprint) and another running CM11 M8 (also Sprint).
Testing Setup:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
IMGUR link of screenshots while Navigating, idle temperature, overheating, etc.
So far, it appears when my phone has been asleep or idle, it's operating at 29-35 degrees C; so it's nearly doubling it's temperature when Navigating. Additionally, this behavior occurs at night, when the sun (and warmer temperatures) are no longer a factor, which seems to rule out the idea that the environment is a major contributor.
I have a good friend who also as a Sprint Galaxy Nexus running CM11; he is a Waze user, and is experiencing the same issue.
Is this a known issue/problem with 4.4-based ROMs? This has been speculated in other threads, but perhaps a more definite answer/explanation is warranted?
Might this be related to the kernel in use, and the thermal throttling limits? What would be the best method of testing such?
What tests or other steps should I take to gather more information or test more factors?
EDIT 1: At @aosp 's recommendation, I'm looking for thermal throttling capabilities via the Kernel Tuner (2014 beta) application. The "Thermal" button is available, but grayed out. Is it safe to assume that means the kernel I'm using has no thermal throttling capabilities, which would (probably) explain how the Galaxy Nexus seems to be able to work itself into an overheated state?
Shidell said:
I have perpetually experienced overheating issues while using 4.4-based ROMs; typically while using Navigation as part of Google Maps and while docked in the Galaxy Nexus Car Dock.
My frustration lead to inquiring with some skilled members of the Galaxy Nexus community, including @Ziyan, @freshgiammi, and @aosp. They have indicated that 4.4-based ROMs seem to be afflicted with this problem, but that it might also be tied to the kernel being used.
I have two phones; one running stock 4.3 (Sprint) and another running CM11 M9 (also Sprint).
Testing Setup:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
IMGUR link of screenshots while Navigating, idle temperature, overheating, etc.
So far, it appears when my phone has been asleep or idle, it's operating at 29-35 degrees C; so it's nearly doubling it's temperature when Navigating. Additionally, this behavior occurs at night, when the sun (and warmer temperatures) are no longer a factor, which seems to rule out the idea that the environment is a major contributor.
I have a good friend who also as a Sprint Galaxy Nexus running CM11; he is a Waze user, and is experiencing the same issue.
Is this a known issue/problem with 4.4-based ROMs? This has been speculated in other threads, but perhaps a more definite answer/explanation is warranted?
Might this be related to the kernel in use, and the thermal throttling limits? What would be the best method of testing such?
What tests or other steps should I take to gather more information or test more factors?
EDIT 1: At @aosp 's recommendation, I'm looking for thermal throttling capabilities via the Kernel Tuner (2014 beta) application. The "Thermal" button is available, but grayed out. Is it safe to assume that means the kernel I'm using has no thermal throttling capabilities, which would (probably) explain how the Galaxy Nexus seems to be able to work itself into an overheated state?
Click to expand...
Click to collapse
IMHO, handling of thermal throttling in 4.4 should be secondary thing to investigate about.
Shouldn't we first think of why for the same application, CPU is hogging this much?
Is it that CPU is not offloading its tasks to GPU which is supposed to happen, and happening with 4.3?
Good thing is that you have two tuna phones available to test out various scenarios.
If you use a ROM's stock kernel, thermal throttling is enabled correctly.
Give Omni and Trickster Mod a try. Omni is more stable & bug-free than CM, and Trickster will show you your CPU temps, as you only posted your battery temps - which are way too high! How the hell did you reach it? Even if I do some antutu, mine never reaches more than 40 °C. 58 °C is either a sensor misbehaving, or you put your phone in a jacket, lol, as it's far enough from the CPU to not heat up.
Post some Omni & Trickster temps with it's stock kernel something must be wrong, as I didn't notice anything like this on my maguro.
Ziyan said:
If you use a ROM's stock kernel, thermal throttling is enabled correctly.
Give Omni and Trickster Mod a try. Omni is more stable & bug-free than CM, and Trickster will show you your CPU temps, as you only posted your battery temps - which are way too high! How the hell did you reach it? Even if I do some antutu, mine never reaches more than 40 °C. 58 °C is either a sensor misbehaving, or you put your phone in a jacket, lol, as it's far enough from the CPU to not heat up.
Post some Omni & Trickster temps with it's stock kernel something must be wrong, as I didn't notice anything like this on my maguro.
Click to expand...
Click to collapse
My battery goes to about 44 degrees C when watching Netflix and charging and about the same during navigation and charging. Only time it's gotten hotter than that is due to environmental issues (such as very hot car interior before ac cools down). I run cm11 and faux123 kernel. Looks like OP is having some kind of hardware issues.
Shidell said:
I have Google Maps (and all other software, including Google Play and Play Services) completely updated. The screen brightness is set to auto. I've tested using Navigation initiated by WiFi, and then disabling the cellular radio (to ensure that the overheating is not being caused by radio activity.) I checked OS Monitor by switching through recent apps mid-testing; this gave me a snapshot of system temperatures and a glimpse of CPU usage.
Stock - Worked perfectly. Navigation, at any time of day, seems to work wonderfully. I do notice that the phone does get warm, and using OS Monitor, can confirm that it reaches 47 degrees C (and holds), never exceeding it. The phone continues to charge without issue. OS Monitor cited CPU usage of 29% at the highest (note that this does not indicate that Maps never used more than 29%, just that 29% was the most I witnessed while checking 15-20 times over the course of 10 miles.)
CM11 - Phone overheats within minutes of starting Navigation, reaching temperatures of 53 degrees C--and as high as 58 degrees C. The phone stops charging as soon as the system registers an "overheated" state. OS Monitor's highest CPU usage was 52%, which is almost double as high as I saw under the stock firmware.
Click to expand...
Click to collapse
I think it would be helpful to try to narrow down where the heat is coming from. Some possibilities:
1. Mobile data or LTE - a likely suspect, but you've already eliminated this one.
2. GPS - set Google Maps aside for a bit, get an app like GPS Status and Toolbox, set it to keep the screen on, and see if this still causes the heating issues.
3. GPU (or lack of proper use of GPU) - If Google Maps overheats the phone but GPS Status does not, it could be how CM is handling the display for Google Maps.
I got a chance to do some testing yesterday afternoon while driving. Toroplus on Page Plus, OmniROM 8-31 nightly, NukedTrinity kernel (was running it to test something else, will test stock kernel today but I fully expect results to be the same). Mobile data off as always. Started GPS right after a 15 minute phone call, battery was at 40 C. Hooked up the charger and ran GPS Status for 5 minutes, battery temp went up to 44 C. Ran Google Maps for 15 minutes (had previously downloaded offline maps for the area), still charging. Battery temp had gone back down to 40 C.
Sdobron said:
My battery goes to about 44 degrees C when watching Netflix and charging and about the same during navigation and charging. Only time it's gotten hotter than that is due to environmental issues (such as very hot car interior before ac cools down). I run cm11 and faux123 kernel. Looks like OP is having some kind of hardware issues.
Click to expand...
Click to collapse
Can you provide me with a link to the exact kernel you're using? I'd like to test it as well. Thanks!
Shidell said:
Can you provide me with a link to the exact kernel you're using? I'd like to test it as well. Thanks!
Click to expand...
Click to collapse
http://faux.romhost.me/tuna/kk44/tuna-kk-kernel-039m-sr.zip
Thank you. I'll test with this shortly as well.
@Ziyan
I agree that these temperatures are way too high; as you'll see below, though, my phone is reaching 46 degrees C simply by using GPS Status! I don't know what to make of that.
@musical_chairs
Thank you for testing as well. I agree that your hypothesis about separate testing is sound, and so I've been testing using GPS Status. I've tried @bsmitty83 's kernel, FancyKernel v56, and Laux123's kernels--all provide slightly different results, but to varying degrees of bizarre behavior using GPS Status.
Stock 4.3 works very well; it determines a bearing indoors without GPS fix and maintains it, with almost no change over a 10 minute period of time. Also, 4.3 warms up, but it never exceeded 44 degrees C.
CM11 w/ Laux123, Fancy Kernel and bsmitty83's all exhibit strange heading behavior. If you'll watch this youtube clip I uploaded (2:45), you'll notice that the phone is laying flat on a wooden table, and yet the Heading will change by 15 or more degrees on it's own. Later in the clip, I move the phone manually to force it to readjust, and you'll see that finds a new bearing from the beginning.
Laying both phones down next to one-another, stock 4.3 indicated the bearing was approximately 219 degrees. In this video clip (FancyKernel r56), my phone believes the bearing is 285 degrees (to begin with) and 260 degrees at the end.
Might GPS be the problem? I suppose I should flash Stock 4.3 to my phone, to make sure it does not continue to behave this way and rule out hardware problems/failure, right?
This just seems really bizarre. Especially that using a GPS fix application can ramp up the temperature so quickly, and so dramatically. Perhaps is the driver/kernel making too many callbacks, causing an escalation in CPU use and heat?
Finally, where can one find the CM11 M8 kernel (indivdually)? I'd like to re-flash it and compare it as well.
Thanks for the continued help in troubleshooting what's happening, everyone.
YouTube CM11 FancyKernel r56
@Shidell just download cm11 m8 and pull out the boot.img so you can fastboot flash it
I managed to gain -5°C on my maguro.
Basically just lowered the thermal throttle to stock values, and now it feels cooler. However still hotter than 4.3 so we're now sure that's not the culprit. Just FYI.
freshgiammi said:
I managed to gain -5°C on my maguro.
Basically just lowered the thermal throttle to stock values, and now it feels cooler. However still hotter than 4.3 so we're now sure that's not the culprit. Just FYI.
Click to expand...
Click to collapse
That's really interesting--5 degrees makes a pretty big difference.
I think I'm going to put stock back on my phone soon, in order to make sure it isn't some sort of hardware failure (maybe the chips in the GNex start to fail if they overheat too high/much? I've heard of that type of failure causing strange issues.)
I'm not sure what to chalk up as the culprit yet, but something is amiss.
If anyone else is reading this thread with a Galaxy Nexus and can comment on their experiences, that information would be useful.
@Ziyan A stock 4.2 or 4.3 kernel should work with any ROM, such as CM10.2 or CM11, is that correct?
I've tried pushing boot.img via fastboot, against both, but neither wants to boot. Am I doing something incorrectly?
Shidell said:
@Ziyan A stock 4.2 or 4.3 kernel should work with any ROM, such as CM10.2 or CM11, is that correct?
I've tried pushing boot.img via fastboot, against both, but neither wants to boot. Am I doing something incorrectly?
Click to expand...
Click to collapse
Yep, but you should only flash the zImage, as flashing the full boot.img flashes the 4.2/3 ramdisk too, which won't work.
BTW, it would be much easier to just flash the latest Omni to your phone. It uses a kernel close to stock, and it's close to AOSP... unlike CM
Ziyan said:
Yep, but you should only flash the zImage, as flashing the full boot.img flashes the 4.2/3 ramdisk too, which won't work.
BTW, it would be much easier to just flash the latest Omni to your phone. It uses a kernel close to stock, and it's close to AOSP... unlike CM
Click to expand...
Click to collapse
I plan on testing Omni today. The reason I ask about the kernel is because I'd also like to test various other ROMs using one of the stock 4.2 or 4.3 kernels.
Can I extract the zImage from the boot.img to ensure I'm only flashing the kernel?
Shidell said:
I plan on testing Omni today. The reason I ask about the kernel is because I'd also like to test various other ROMs using one of the stock 4.2 or 4.3 kernels.
Can I extract the zImage from the boot.img to ensure I'm only flashing the kernel?
Click to expand...
Click to collapse
Yes Connect the gnex via usb and "fastboot flash zimage zImage"
Thanks @freshgiammi I've done some extensive testing, so I hope that this helps us determine where the problem is. @Ziyan, @aosp, @musical_chairs, @poo706, @rkpeterson, @MWisBest, @BigBrother1984, @something15525 I'm hoping you might be able to lend a hand as well.
I created this thread based on the Galaxy Nexus tending to overheat when Navigating. However, I've found another discrepancy--live wallpaper performance with the Google Now Launcher. When using the GNL with the Phase Beam wallpaper, sometimes the GNex can draw it just fine; it's smooth, no (or few) dropped frames--it looks and works great. However, with other ROMs, it's very janky, stuttering and performing poorly.
(Note that GNL with a static picture works fine.)
I suspect that there might be a GPU driver issue, or perhaps a configuration issue, in some ROMs that's causing this behavior. Perhaps a certain GPU driver is used in some ROMs, and not others, causing the problem? Perhaps there is a config file with GPU settings where one has specific features enabled, others do not, and it results in poor performance in certain rendering cases?
I wonder if it might be related to overheating on the Galaxy Nexus when Navigating, watching video, playing games--items that tax the GPU. If it is such an issue, though, it might also mean extra work is being performed to compensate, and that would mean extra heat and battery use.
Here are two YouTube links displaying the behavior in question. First is Factory Stock 4.3--I wasn't able to directly record the screen (as that feature wasn't introduced with ADB until 4.4), but hopefully it's clear enough to see that it's smooth. (There is one hiccup when the cards are loading, but that's it.) The second video shows the same test, but running on CM11 M8--it's very choppy and lags behind input, and it's extremely noticeable in person.
I tried to capture video from OmniROM, but received this error while using ADB:
Code:
D:\Android\sdk\platform-tools>adb shell screenrecord /sdcard/omni44.mp4
WARN: Unable to set device connection state for audio submix IN
WARN: Unable to set device connection state for audio submix OUT
Unable to instantiate audio source (error -1)!
Factory 4.3
CM11 M8
I've conducted some tests on a spare Galaxy Nexus, and wiped my own personal model, to be sure that the behavior is the same on both devices--to ensure I don't have a damaged GPU or some other weird hardware issue that might be responsible.
Results:
Factory 4.2.1 - OK
Factory 4.3 - OK
LiquidSmooth LS-KK-v3.2-2014-09-03 - OK
Paranoid Android 4.6 Beta 1 - OK
OmniROM 4.4.4 - 20140905 Nightly - FAIL
CM10.2 RC 1 - FAIL
CM11 M8 - FAIL
Further, I extracted the kernel zImage from Factory 4.2.1 and 4.3, and flashed it into CM11 M8 just to see if the kernel alone made any difference. The 4.2.1 kernel wouldn't boot; 4.3 booted up properly, but the lag/choppiness persisted, which seems to indicate that the problem is not kernel related.
What should I investigate next? Clearly LiquidSmooth and ParanoidAndroid are getting smooth GPU performance, which I expect is also what's causing Navigation to cause my phone to overheat (but I can't prove that, unless we can solve this issue and then I can test with a fix and determine if it's the cause or not.)
Could a config file be at fault? A difference in drivers being used?
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
sagara.sandaru said:
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
Click to expand...
Click to collapse
Hm, I'm not sure I can answer that without more information.
What ROM and Kernel are you using? What type Galaxy Nexus? If you are using 4.4, can you do a screencap of what you're experiencing and upload it to YouTube as I have?
Shidell said:
Thanks @freshgiammi I've done some extensive testing, so I hope that this helps us determine where the problem is. @Ziyan, @aosp, @musical_chairs, @poo706, @rkpeterson, @MWisBest, @BigBrother1984, @something15525 I'm hoping you might be able to lend a hand as well.
I created this thread based on the Galaxy Nexus tending to overheat when Navigating. However, I've found another discrepancy--live wallpaper performance with the Google Now Launcher. When using the GNL with the Phase Beam wallpaper, sometimes the GNex can draw it just fine; it's smooth, no (or few) dropped frames--it looks and works great. However, with other ROMs, it's very janky, stuttering and performing poorly.
(Note that GNL with a static picture works fine.)
I suspect that there might be a GPU driver issue, or perhaps a configuration issue, in some ROMs that's causing this behavior. Perhaps a certain GPU driver is used in some ROMs, and not others, causing the problem? Perhaps there is a config file with GPU settings where one has specific features enabled, others do not, and it results in poor performance in certain rendering cases?
I wonder if it might be related to overheating on the Galaxy Nexus when Navigating, watching video, playing games--items that tax the GPU. If it is such an issue, though, it might also mean extra work is being performed to compensate, and that would mean extra heat and battery use.
Here are two YouTube links displaying the behavior in question. First is Factory Stock 4.3--I wasn't able to directly record the screen (as that feature wasn't introduced with ADB until 4.4), but hopefully it's clear enough to see that it's smooth. (There is one hiccup when the cards are loading, but that's it.) The second video shows the same test, but running on CM11 M8--it's very choppy and lags behind input, and it's extremely noticeable in person.
I tried to capture video from OmniROM, but received this error while using ADB:
Code:
D:\Android\sdk\platform-tools>adb shell screenrecord /sdcard/omni44.mp4
WARN: Unable to set device connection state for audio submix IN
WARN: Unable to set device connection state for audio submix OUT
Unable to instantiate audio source (error -1)!
Factory 4.3
CM11 M8
I've conducted some tests on a spare Galaxy Nexus, and wiped my own personal model, to be sure that the behavior is the same on both devices--to ensure I don't have a damaged GPU or some other weird hardware issue that might be responsible.
Results:
Factory 4.2.1 - OK
Factory 4.3 - OK
LiquidSmooth LS-KK-v3.2-2014-09-03 - OK
Paranoid Android 4.6 Beta 1 - OK
OmniROM 4.4.4 - 20140905 Nightly - FAIL
CM10.2 RC 1 - FAIL
CM11 M8 - FAIL
Further, I extracted the kernel zImage from Factory 4.2.1 and 4.3, and flashed it into CM11 M8 just to see if the kernel alone made any difference. The 4.2.1 kernel wouldn't boot; 4.3 booted up properly, but the lag/choppiness persisted, which seems to indicate that the problem is not kernel related.
What should I investigate next? Clearly LiquidSmooth and ParanoidAndroid are getting smooth GPU performance, which I expect is also what's causing Navigation to cause my phone to overheat (but I can't prove that, unless we can solve this issue and then I can test with a fix and determine if it's the cause or not.)
Could a config file be at fault? A difference in drivers being used?
Click to expand...
Click to collapse
Could you give FML a try? In particular the latest beta build...
not sure if you're on a maguro or a toro, so I'll link them both:
omni-4.4.4-20140825-maguro-FML.zip (159.56 MB)
omni-4.4.4-20140824-toro-FML.zip (159.41 MB)
With FML being based on OmniROM, if there's an issue with OmniROM but not FML or vice-versa it can help narrow down what might be the difference that causes the issue.
I'm also interested if screen record via adb works with that build for ya as well, so if you could test that it'd be much appreciated.
sagara.sandaru said:
I'm having a huge lag with the latest version of Chrome which updated with material design. I'm afraid will we be having these gpu related bugs with Android L as well.
Will these gpu drivers issues be fixed with 3.4 kernel?
Click to expand...
Click to collapse
The 3.4 kernel isn't looking to be the smoking gun we were hoping for, however if we can get Ducati (hardware video encode/decode and camera stuff) working with the updated GPU drivers in the 3.0 kernel that would definitely be helpful. The newer GPU drivers have better power management by a landslide.
Hi everyone
First of all, I'm not an expert and I'm not a developer as well; I'm just a geek who loves to understand things and solve problems. Now, since I first bought the Mi Mix 3, I noticed that I always had a problem with the battery discharge. When the phone was locked, in fact, it kept discharging very quickly and during the winter, now that my hands are colder than my ex-girlfriend heart, I could notice that even if the phone has been locked for hours, it's always a little bit warm. So he keeps doing something in the background. On the other hand, I never decided to go deeper into this, because I use two LTE sim cards and the network signal in my room is very bad, so I always end up thinking "Maybe the problem is the quality of the signal, the phone keeps attempting to connect to the mobile antennas and it needs a lot of energy". The fact is that my Mi Mix 3 kept discharging even with a very good signal, like 100m straight line to the tower. But again, I thought it was because of the bad optimization of the beta Chinese ROM (I was testing the MIUI 11).
Ok, Two days ago, I finally decided to flash a custom ROM. I love the MIUI but the temptation of flashing stuff is too high, so I went ahead, I downloaded the Evolution X 2.1 and I finally flashed it. The problem was still there. Moreover, now I'm using only one sim card. So let's flash Magisk and then BetterBatteryStats. And finally, I discovered the real problem: The DAMN CPU (both BIG cores and LITTLE cores) never go into the deep sleep state, literally. So I downloaded Kernel Auditor for more details and listen here: when the phone is locked, the BIG cores remain at their minimum frequency (825 MHz) as well as the Little ones (576 MHz, I could set it to 300 and actually I noticed a slight improvement). But no Deep Sleep at all; Kernel Auditor itself says "Never used frequencies: Deep Sleep".
So excellent! The Deep Sleep state doesn't exist at all into my phone, I'd understand having a small percentage of it, but nothing at all, what kind of problem is that? I checked the wakelocks anyway, but there was nothing weird going on. The highest value on the Kernel wakelocks was because of the display management and on the partial ones, the highest was the Google Play Services (Nah, just 1%). So wakelocks were fine. I ended up thinking that the problem was the FIrmware or the Kernel, that's something I'll never know maybe. But I managed to solve the problem.
How did I solve it?
Right at this moment I'm using the Evolution X 2.1 ROM and, to be frank, I thought it could solve the problem but it didn't. For instance, I also tried different governors instead of the schedutil set by default, like conservative or powersave, nothing changed again.
"Ok ok, enough about that, how can I solve it?"
You have to install the XASP (M.A.R.S.) mod. This will solve your problem.
Check the topic:
https://forum.xda-developers.com/mi-mix-3/development/rom-xasp-xiaomi-aosp-snapdragon-patch-t3931721
And the developer's website:
https://sites.google.com/view/miustone/HOME
And the developer's GitHub repository related to the project:
https://github.com/Miustone/MARS-Patch
Some hints:
You need an AOSP ROM in order to make it work. It won't work on any MIUI ROM (I think)!
The installation instructions say that you should flash it right after a fresh install of the ROM (It must be Android 9 / SDK 28 - AOSP ARM64), but I flashed it even after a few days of using and it worked as well.
You need to clone/download the repository, unzip it, move into the unzipped directory (where there's the META-INF), select everything and compress it into a zip file and that will be the patch you should flash using the TWRP recovery.
P.S. I know, it's not really a solution, I mean, If you don't want to root your phone, you have to rely on the original version of the MIUI, but from what I've seen, bot MIUI 10 global developer and MIUI 11 china developer have this problem. If you just don't want a custom ROM but you rooted your phone, you could try the MIUI EU ROM, I don't know if it has the same problem tho.
And finally, let your CPU rest a little bit!
UPDATE: The MIUI EU ROM works very well. The phone manages to go in the deep sleep state as well and everything works fine. So if you don't want to flash multiple zips and do tricky things, just use the MIUI EU ROM and you'll be ok. Let's keep reporting any deep sleep issue here tho!
And thanks everyone for the help!
EU MIUI 11 does not have the problem. I got fed up with the various inadequacies of the current AOSP-based roms and decided to give MIUI another go, although I previously disliked it intensely. Turns out that the EU version of MIUI 11 is stunningly good. Camera works properly, including with the slider, it's super-smooth and fast, notifications work correctly, but the biggest difference is battery life because when the screen is off there's almost no drain at all (in contrast to all the other ROMs I've tried). The only thing I didn't like about MIUI 11 was the launcher, even with the new app drawer option it's still not to my taste, but with Nova installed it works just like AOSP.
invisiblewave said:
EU MIUI 11 does not have the problem. I got fed up with the various inadequacies of the current AOSP-based ROMs and decided to give MIUI another go, although I previously disliked it intensely. Turns out that the EU version of MIUI 11 is stunningly good. Camera works properly, including with the slider, it's super-smooth and fast, notifications work correctly, but the biggest difference is battery life because when the screen is off there's almost no drain at all (in contrast to all the other ROMs I've tried). The only thing I didn't like about MIUI 11 was the launcher, even with the new app drawer option it's still not to my taste, but with Nova installed it works just like AOSP.
Click to expand...
Click to collapse
Well, this is a great thing to hear! Actually, the Evolution X 2.1 with that mod is just amazing, but the preinstalled GCam (Which works perfectly with pictures instead of the one you can install on the MIUI) can't take videos in 4K, only FHD; in general, I find the MIUI camera app excellent, but I can't find it and I'm quite sure I can't use it on this ROM. So maybe I'll give the MIUI 11 EU a try as well, thank you for sharing!
P.S. Turned out that I was having the deep sleep issue even after flashing the patch, but I was able to notice that it was because of the Google Photo app, so check for that if you're experiencing the battery drain problem.
Takenfal said:
Well, this is a great thing to hear! Actually, the Evolution X 2.1 with that mod is just amazing, but the preinstalled GCam (Which works perfectly with pictures instead of the one you can install on the MIUI) can't take videos in 4K, only FHD; in general, I find the MIUI camera app excellent, but I can't find it and I'm quite sure I can't use it on this ROM. So maybe I'll give the MIUI 11 EU a try as well, thank you for sharing!
P.S. Turned out that I was having the deep sleep issue even after flashing the patch, but I was able to notice that it was because of the Google Photo app, so check for that if you're experiencing the battery drain problem.
Click to expand...
Click to collapse
Yes! I'm somewhat shocked at how good MIUI 11 is. The app permissions are still a bit of an annoyance, they seem to install with no permissions by default, so you have to grant them, but there's a new option (I assume it's an Android 10 feature) to allow a permission only while an app is in use which is nice. I've been running it for a few days now and I can't see any reason to go back. The other huge thing it solved for me is the reboot issue with wireless charging that seems to afflict all the AOSP/LOS-based roms (random reboots and bootloops while charging, to test it put your phone on a wireless charger and reboot).
invisiblewave said:
Yes! I'm somewhat shocked at how good MIUI 11 is. The app permissions are still a bit of an annoyance, they seem to install with no permissions by default, so you have to grant them, but there's a new option (I assume it's an Android 10 feature) to allow a permission only while an app is in use which is nice. I've been running it for a few days now and I can't see any reason to go back. The other huge thing it solved for me is the reboot issue with wireless charging that seems to afflict all the AOSP/LOS-based roms (random reboots and bootloops while charging, to test it put your phone on a wireless charger and reboot).
Click to expand...
Click to collapse
Look like you're right! I rebooted my phone while charging it wirelessly and it kept rebooting on MI logo. Interesting bug lol
Takenfal said:
Look like you're right! I rebooted my phone while charging it wirelessly and it kept rebooting on MI logo. Interesting bug lol
Click to expand...
Click to collapse
Yes, and if you leave it on charge overnight, it will occasionally randomly reboot then bootloop until the light wakes you up. Ask me how I know..... I highly recommend you try MIUI 11, I still haven't found any problems with it and I even managed to get Google Pay working, which I wasn't able to do on any of the other roms.
I know that the collection of scripts and stuff posted above have been massively flamed as causing issues elsewhere in the forums. I would generally caution against installing them as many users ended up fastbooting other MIUI devices after trying to install them. I think the dev who made them is trying to do good things, but I would proceed with caution. As others have mentioned, MIUI11 does not seem to have this problem.
@PWn3R Yep, had a nice stressy afternoon with the patch. Managed to make a few aditional mistakes and was locked out of recovery and ended up flashing the phone through fastboot.
I did fix my battery issues though, and it is running quite well now. Instead of roughly 12 hours of battery life I now get over 24 with the same usage.
I really hate MIUI and will never go back for the simple reason that my phone that I used for development was unable to activate ADB sideloading because it has to validate this against Xiaomi servers. And there was an issue there. To much control over my device is in China, so that is a big no no for me. I rather deal with some custom rom issues than that.
I see, but It's the only way I was able to finally put the phone in deep sleep. I don't know what's wrong with the Mi MIX 3 but it's very hard to see the deep sleep state with any ROM, MIUI or customs doesn't matter. I'm trying the MIUI EU now and guess what? The CPU is constantly running at 576 MHz. Only 2 minutes of deep sleep over an entire day without charging it. I only installed Whatsapp, Telegram X, and BetterBatteryStats. The integrated battery tool shows that WhatsApp is the cause of the massive battery drain (don't know if it's really because it prevents the deep sleep state or because it had to restore all the media after the installation); in any case, BetterbatteryStats, on the partial wakelocks tab, shows WhatsApp but only 1% of wakelocks. So I don't really know what the cause is.
Hi - here's my device with over 150 apps installed. I am running Xaomi EU atm with the latest weekly beta.
PWn3R said:
Hi - here's my device with over 150 apps installed. I am running Xaomi EU atm with the latest weekly beta.
Click to expand...
Click to collapse
+1. That looks like mine, too. With the screen off, the drain is less than I've ever seen on any device previously. Modified versions of the rom optimized for a device always perform better than AOSP, particularly on battery. It all comes down to whether you can live with the rest of the crap they usually add. EU MIUI 11 is a pretty good compromise, imo, with a third party launcher installed it's very similar to the other roms anyway.
Takenfal said:
Hi everyone
First of all, I'm not an expert and I'm not a developer as well; I'm just a geek who loves to understand things and solve problems. Now, since I first bought the Mi Mix 3, I noticed that I always had a problem with the battery discharge. When the phone was locked, in fact, it kept discharging very quickly and during the winter, now that my hands are colder than my ex-girlfriend heart, I could notice that even if the phone has been locked for hours, it's always a little bit warm. So he keeps doing something in the background. On the other hand, I never decided to go deeper into this, because I use two LTE sim cards and the network signal in my room is very bad, so I always end up thinking "Maybe the problem is the quality of the signal, the phone keeps attempting to connect to the mobile antennas and it needs a lot of energy". The fact is that my Mi Mix 3 kept discharging even with a very good signal, like 100m straight line to the tower. But again, I thought it was because of the bad optimization of the beta Chinese ROM (I was testing the MIUI 11).
Ok, Two days ago, I finally decided to flash a custom ROM. I love the MIUI but the temptation of flashing stuff is too high, so I went ahead, I downloaded the Evolution X 2.1 and I finally flashed it. The problem was still there. Moreover, now I'm using only one sim card. So let's flash Magisk and then BetterBatteryStats. And finally, I discovered the real problem: The DAMN CPU (both BIG cores and LITTLE cores) never go into the deep sleep state, literally. So I downloaded Kernel Auditor for more details and listen here: when the phone is locked, the BIG cores remain at their minimum frequency (825 MHz) as well as the Little ones (576 MHz, I could set it to 300 and actually I noticed a slight improvement). But no Deep Sleep at all; Kernel Auditor itself says "Never used frequencies: Deep Sleep".
So excellent! The Deep Sleep state doesn't exist at all into my phone, I'd understand having a small percentage of it, but nothing at all, what kind of problem is that? I checked the wakelocks anyway, but there was nothing weird going on. The highest value on the Kernel wakelocks was because of the display management and on the partial ones, the highest was the Google Play Services (Nah, just 1%). So wakelocks were fine. I ended up thinking that the problem was the FIrmware or the Kernel, that's something I'll never know maybe. But I managed to solve the problem.
How did I solve it?
Right at this moment I'm using the Evolution X 2.1 ROM and, to be frank, I thought it could solve the problem but it didn't. For instance, I also tried different governors instead of the schedutil set by default, like conservative or powersave, nothing changed again.
"Ok ok, enough about that, how can I solve it?"
You have to install the XASP (M.A.R.S.) mod. This will solve your problem.
Check the topic:
https://forum.xda-developers.com/mi-mix-3/development/rom-xasp-xiaomi-aosp-snapdragon-patch-t3931721
And the developer's website:
https://sites.google.com/view/miustone/HOME
And the developer's GitHub repository related to the project:
https://github.com/Miustone/MARS-Patch
Some hints:
You need an AOSP ROM in order to make it work. It won't work on any MIUI ROM (I think)!
The installation instructions say that you should flash it right after a fresh install of the ROM (It must be Android 9 / SDK 28 - AOSP ARM64), but I flashed it even after a few days of using and it worked as well.
You need to clone/download the repository, unzip it, move into the unzipped directory (where there's the META-INF), select everything and compress it into a zip file and that will be the patch you should flash using the TWRP recovery.
P.S. I know, it's not really a solution, I mean, If you don't want to root your phone, you have to rely on the original version of the MIUI, but from what I've seen, bot MIUI 10 global developer and MIUI 11 china developer have this problem. If you just don't want a custom ROM but you rooted your phone, you could try the MIUI EU ROM, I don't know if it has the same problem tho.
And finally, let your CPU rest a little bit!
Click to expand...
Click to collapse
I fixed mine by disabling proximity sensor. My phone got to deep sleep just after
I am running the latest Xiaomi.eu MIUI 11. According the Kernel Adiutor Frequency Table it is going to Deep Sleep whenever not awake, but the lowest frequency for Cores 0-3 is 576MHz, (everything below is unused). Cores 4-7 are almost always in their lowest frequency, 825MHz.
So is this deep sleeping or not? I would not say battery life is amazing. The biggest battery drainer is cell standby, which is more even than screen. I can't get better battery stats to work (keeps repeatedly flashing up the superuser message).
Deep sleep is a know problem on most custom rom, solution: flash XENT kernel, been using RR with xent for a while and deep sleep work well.
patp said:
I am running the latest Xiaomi.eu MIUI 11. According the Kernel Adiutor Frequency Table it is going to Deep Sleep whenever not awake, but the lowest frequency for Cores 0-3 is 576MHz, (everything below is unused). Cores 4-7 are almost always in their lowest frequency, 825MHz.
So is this deep sleeping or not? I would not say battery life is amazing. The biggest battery drainer is cell standby, which is more even than the screen. I can't get better battery stats to work (keeps repeatedly flashing up the superuser message).
Click to expand...
Click to collapse
There should be a deep sleep state even for the BIG cores; the fact that they remain at the lowest frequency (825 MHz) is not good. Also, I don't understand why, when the phone is locked, the minimum frequency is not lower than 576 MHz when the LITTLE cores could go at 300 MHz, but that's not really a problem). Maybe it's related to the fact that your phone keeps searching for a good signal, and maybe that's why stats tell you that "cell standby" is draining a lot of battery. Is your phone the global version (the phone, not the ROM) or the Chinese one?
GVN.Gallus said:
Deep sleep is a known problem on most custom ROM, solution: flash XENT kernel, been using RR with xent for a while and deep sleep work well.
Click to expand...
Click to collapse
Interesting, I'd like to give it a try;
UPDATE : Anyway, besides the first deep issue problem, now the phone is working perfectly with the MIUI EU v 11 based on Android 10. When I lock the phone there's no more battery drain AT ALL. If I lock it at 15% and I unlock it after 2 hours, it's still at 15%. This is how deep sleep should Work. Maybe the first problem I had with the EU ROM was related to the google services syncing all my stuff (still don't understand why some things that keep the CPU from going in the deep sleep state are not shown even using BBS).
Note for anyone switching to the weekly MIUI/10 rom, I had microphone issues on calls which appear to be solved by flashing the latest firmware.
Edit: Firmware wasn't the fix. The workaround is to toggle the speakerphone on and off again. The microphone then works on all calls until you reboot the phone, then you have to do the toggle trick again.
GVN.Gallus said:
Deep sleep is a know problem on most custom rom, solution: flash XENT kernel, been using RR with xent for a while and deep sleep work well.
Click to expand...
Click to collapse
Where can I find XENT kernel, please?
ChienJian said:
Where can I find XENT kernel, please?
Click to expand...
Click to collapse
You can find it in the Mi Mix 3 Global Community telegram group: https://t.me/MiMix3Global
Takenfal said:
There should be a deep sleep state even for the BIG cores; the fact that they remain at the lowest frequency (825 MHz) is not good. Also, I don't understand why, when the phone is locked, the minimum frequency is not lower than 576 MHz when the LITTLE cores could go at 300 MHz, but that's not really a problem). Maybe it's related to the fact that your phone keeps searching for a good signal, and maybe that's why stats tell you that "cell standby" is draining a lot of battery. Is your phone the global version (the phone, not the ROM) or the Chinese one?
Click to expand...
Click to collapse
Global version. But I fixed the battery drain. Completely uninstalled WhatsApp, deleted folder and reinstalled latest. Deleted Play Services data. Set preferred network to LTE/WCDMA. Now I have minimal cell-standby and battery doesn't drop significantly when screen is off.
Frequencies remain the same, but maybe the min freq is a red herring - Kernel Adiutor says it spends plenty of time in Deep Sleep.