Develop Bugs

VillainROM 12.0.0 Wi-Fi system hang...

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...

4.4-based ROMs cause the Galaxy Nexus to overheat. Can we fix this?

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.

CPU frequency sometimes lock on maximum frequency values

Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.

iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
i have samne problem on 8.8.16

Just uninstall CPU Z and accu battery problem solve

iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Problem will back soon on stock kernel

SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Actually bad solution, you know
Zanr Zij said:
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
Click to expand...
Click to collapse
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors

iFreeMan said:
Actually bad solution, you know
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors
Click to expand...
Click to collapse
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases

Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly.
Try to boot to safe mode for several hours to check if it really caused by user app. Turn off your phone > Hold power to turn on > As soon as mi logo appear, quickly hold volume down until the phone finish booting (can be up to 30 seconds). You should see "safe mode" watermark at the bottom left corner, indicating all user app has been temporary disabled. Leave it for several hours to see if the battery still drain or the phone stay awake all the time (high cpu usage). To exit from safe mode, simply reboot.
I always found it is kind of a habit to blame MIUI for everything. I am not defending MIUI here, they bloat a lot. I also hate it and I am using RR now. But on several occassions when we troubleshoot, we found out it is one of the user app that cause the trouble, ads, or slow charging; not anything related to MIUI. Blaming MIUI won't solve the problem, only troubleshooting will lead us to the real culprit. In your case, it still can be caused by the MIUI itself. But until you troubleshoot it out, you won't know who is the real culprit.
For comparison, when still using MIUI 9.5.17.0 I can easily achieve 10+ hours SOT within 1,5 days (max is 14 hours). When switched to RR, affected by the wifi deep sleep drain, I rarely get 10 hours SOT anymore. Still in the process of troubleshooting the problem.

Zanr Zij said:
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases
Click to expand...
Click to collapse
I don't mind to have additional applications.. But I don't like when my CPU works incorrect O_O
Desmanto said:
Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly..
Click to expand...
Click to collapse
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event

iFreeMan said:
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event
Click to expand...
Click to collapse
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.

Desmanto said:
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.
Click to expand...
Click to collapse
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.

iFreeMan said:
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.
Click to expand...
Click to collapse
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.

Desmanto said:
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.
Click to expand...
Click to collapse
Yes, I understand that and understand why it would occurs and tried to investigate in this way, but...
I have equals application list which I had on previous device except...CPU-Z and AccuBattery (the AccuBattery for now is removed) because of I faced with this frequencies issues.
This morning it happened again. But I just.. woke up, saw on frequencies - everything OK. Then I just.. Instagram, Telegram, Facebook Messenger and Google Chrome and no more. Then I realized that the phone became a bit warm.. I saw on frequencies - it was locked again
As it happened, I've came to office, connected via ADB to laptop and made several screenshots from `top` utility and looked a bit into `adb logcat`. But nothing... IDLE ~798%. And then I've tried to go to all apps and do force stop for ALL apps. But nothing.
I just rebooted device again...
Please look on it.. https://drive.google.com/open?id=1yXjQQ4rsF3MURh1PF0DZ1Z_Gtgc4-m4_

Just concerning about.. there are a lot errors in logcat. But I understand that.. that's ok.
But 90% of logs flowing from system processes, not from apps. But there is nothing critical.. Nothing something what could flow unstoppable text and caused over-loading CPU.
I'm afraid that it could be manufacturing defects
I event tried to re-flash firmware with fastboot (I thought that byte-by-byte flasing into ROM memory could fix some random small issues). But after flashing with fastboot this CPU locking happening again.
Actually.. dunno what to do with that. The last thought to try any custom ROM (may be Lineage OS) with custom kernel and make sure that it is just bug in Xiaomi's ROM..

And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.

iFreeMan said:
And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.
Click to expand...
Click to collapse
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.

Desmanto said:
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.
Click to expand...
Click to collapse
I just used custom firmware just for check is that factory defect. But seems that's issue only with xiaomi's firmware.
Yes, I thought that could be governor likewise. But.. Don't think so, because this low-level things, I think, debugged and enhanced successfully by default. Seems some conflicts between system applications.
On custom ROM I haven't faced with this issue, so...
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..

iFreeMan said:
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..
Click to expand...
Click to collapse
Yes, I've got first lock on maximum frequencies.
So, after researches.. I could say that it's a bug in xiaomi firmware. Definitely.

I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.

marc_alv said:
I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.
Click to expand...
Click to collapse
I have no problem with Miui based custom Rom + custom kernel

Zanr Zij said:
I have no problem with Miui based custom Rom + custom kernel
Click to expand...
Click to collapse
Could you specify the rom and kernel, please?

[H932 ONLY!!!!!!!!!] [WIP]Resurrection Remix V6.1.0 Oreo 8.1

I PRESENT TO YOU THE H932 ONLY
RESURRECTION REMIX V6.1.0[WIP]
DISCLAIMER:
Of course flashing this rom you resume the risk of a non-functional device or destruction of a ultimate world war outbreak and adhere the responsibility that comes with flashing a file to your device. If you brick your device, you did something foolish and don't know what you are doing and maybe should not be rooting/roming(that simple). Remember that you are the one taking the risk of flashing/modding your device. Please don't come harassing me due to messing up your device. YOU HAVE BEEN WARNED!!!!!!
ABOUT:
This is a port of Lineage 15.1 and Resurrection Remix V6.1.0 that I have ported over for the H932, it is currently a Work In Progress state. Will continue to work on it as time allows, built it and seen that it is working pretty good and wanted to share with the H932 community
Prerooted(Magisk-systemless), rctd disabled, no verity-force encrypt already installed for your next journey
Due to being a Work In Progress rom, it will have some bugs/issues till they are resolved(hopefully), most of the bugs currently are the ones inherited from Lineage, which this Resurrection Remix is based off of, so please be patient
INSTALLATION NOTES/KNOWN ISSUES:
The percentage meter does not move while installing, simple fix within updaterscript, average install is 5-10min, do not interrupt and it will complete and finish on it own
Install your flavor of Gapps before rebooting to RR, Magisk will force close once after reboot due to Gapps trying to get setup, but don't worry you didn't loose Magisk/Root. After reboot update Magisk binaries
Noticed phone will run a little warm during setup and pre-installation period(reinstalling of backups). After phone settles down and settled in it runs pretty damn smooth
SPECIAL THANKS:
runningnak3d - Making all this possible for the H932. Thank You Running!!!!!!!
me2151 - Bringing Lineage 15.1 to the H932
SGCMarkus - Porting RR to H930
Josh McGrath - Testing & Ideas
Addiso - Testing & Ideas
*If I missed anyone please let me know*
DOWNLOADS:
RR-O-V6.1.0-h932-102318
IN THE NEED OF FLASHING BACK TO STOCK, VISIT THE ALL-IN-ONE FIRMWARE STOP:
H932 T-Mobile Only!!!! All-in-One OEM Firmware Stop
As Always, Thanks for stopping by and ENJOY!!!!:silly:​

reserved

reserved-1

I've been running this for the majority of the day. The only thing I'm worried about is my phone running warmer than usual. Especially when on a wireless charger. I can feel the heat just putting my hand on the screen. I'm hoping that this is just the phone "settling in" but I didn't see this behavior when I was on Lineage OS before flashing this. Everything is running smooth otherwise. I'm loving all the customization.

jsgraphicart said:
I've been running this for the majority of the day. The only thing I'm worried about is my phone running warmer than usual. Especially when on a wireless charger. I can feel the heat just putting my hand on the screen. I'm hoping that this is just the phone "settling in" but I didn't see this behavior when I was on Lineage OS before flashing this. Everything is running smooth otherwise. I'm loving all the customization.
Click to expand...
Click to collapse
RR isn't exactly known to be the most coolest (slim ROM, less services, etc.), most battery efficient, most smoothest, etc.
its strenghts are the huge customizability mostly of the UI,
AEX, AOSiP, dot os (having my doubts now with the Smart Pixel overlay and issues with app installations, calls of kang, etc.) - might be better candidates for a reliable daily driver

jsgraphicart said:
I've been running this for the majority of the day. The only thing I'm worried about is my phone running warmer than usual. Especially when on a wireless charger. I can feel the heat just putting my hand on the screen. I'm hoping that this is just the phone "settling in" but I didn't see this behavior when I was on Lineage OS before flashing this. Everything is running smooth otherwise. I'm loving all the customization.
Click to expand...
Click to collapse
It ran a little warm when I first installed it, after adjusting the schedulers and frequencies it runs really cool now(which is what public release is set to), adjustments made was changed scheduler to interactive and changed the max freq. to under what it was set at out of the box, the min was set all the way down to 300mhz so it wouldn't be running max while screen off.
after making adjustments and adding root for public release I reflashed to make sure there was no errors on install, it ran a little warm setting up and installing backups through titanium backup, once set up and settled in it ran way cooler for me
running a bunch of backups of my pc and sd cards, soon as this is done, I will reinstall what I released and give it another go to see if I can replicate what you are experiencing, nothing different should of changed from when I flashed and when you flashed it, unless possibly an app hanging in the background constantly running

zacharias.maladroit said:
RR isn't exactly known to be the most coolest (slim ROM, less services, etc.), most battery efficient, most smoothest, etc.
its strenghts are the huge customizability mostly of the UI,
AEX, AOSiP, dot os (having my doubts now with the Smart Pixel overlay and issues with app installations, calls of kang, etc.) - might be better candidates for a reliable daily driver
Click to expand...
Click to collapse
Yeah, I used to prefer complete AOSP with Xposed and GravityBox but there's nothing available for the T-mobile V30 yet. Just Lineage and now this.
wills3gslide said:
It ran a little warm when I first installed it, after adjusting the schedulers and frequencies it runs really cool now(which is what public release is set to), adjustments made was changed scheduler to interactive and changed the max freq. to under what it was set at out of the box, the min was set all the way down to 300mhz so it wouldn't be running max while screen off.
after making adjustments and adding root for public release I reflashed to make sure there was no errors on install, it ran a little warm setting up and installing backups through titanium backup, once set up and settled in it ran way cooler for me
running a bunch of backups of my pc and sd cards, soon as this is done, I will reinstall what I released and give it another go to see if I can replicate what you are experiencing, nothing different should of changed from when I flashed and when you flashed it, unless possibly an app hanging in the background constantly running
Click to expand...
Click to collapse
It could get better as time goes on. I'll give it another day at least to see how it goes. Do you use wireless charging? That seems to be when it gets the hottest. I also tested out charging with a cable and it wasn't as hot. Again, I'll give it another day. If it continues, I'll try and reinstall

jsgraphicart said:
Yeah, I used to prefer complete AOSP with Xposed and GravityBox but there's nothing available for the T-mobile V30 yet. Just Lineage and now this.
It could get better as time goes on. I'll give it another day at least to see how it goes. Do you use wireless charging? That seems to be when it gets the hottest. I also tested out charging with a cable and it wasn't as hot. Again, I'll give it another day. If it continues, I'll try and reinstall
Click to expand...
Click to collapse
Agree, I normally have xposed installed for all the extra customizing that which ever rom I was running in the past, had it installed on the 20k before I finished RR. Haven't used the wireless charging much due to flashing and constantly having the phone hooked to the computer, but did test it out and did notice it did get a little warmer but not to terribly warmer, have noticed in the past if using NFC to another device or wireless charging the device will usually run a bit warmer, kinda what you are experiencing but not real hot

Is there a way to fix the ctsProfile showing false in magisk? I guess it has something to do with the fingerprint of the device. Maybe a build.prop change?

jsgraphicart said:
Is there a way to fix the ctsProfile showing false in magisk? I guess it has something to do with the fingerprint of the device. Maybe a build.prop change?
Click to expand...
Click to collapse
Have someone pull the fingerprint off the 20k stock LG rom with the following on terminal
getprop ro.build.fingerprint
Or you can simply use the magisk hide module to use a different devices official fingerprint but take note that apps will see your app as that device.

Addiso said:
Have someone pull the fingerprint off the 20k stock LG rom with the following on terminal
getprop ro.build.fingerprint
Or you can simply use the magisk hide module to use a different devices official fingerprint but take note that apps will see your app as that device.
Click to expand...
Click to collapse
Thanks. I'll have to see if someone can get the 20k fingerprint. I don't really want my device showing as something else.

I ended up rerooting/flashing my phone last night. I went back to stock (stock lafs/20k) the other week because I couldn't stop blowing everything out trying roms. Got bored, something about breaking our phones makes it fun. Anyways I loaded this last night once I got everything unlocked. I really like this rom. It's very smooth. The only issue I have run into is not being able to register my fingerprint. On the set up it does nothing. (*I did just read that usually this issue is related to not being on Oreo firmware. Makes sense, I did not goto 20k after unlocking/rooting phone. I will give it a try and report back*)
Only other issue I noticed, my device shows as UNKNOWN. This caused Podcast Addict to have an issue setting language by default.

wireeater said:
I ended up rerooting/flashing my phone last night. I went back to stock (stock lafs/20k) the other week because I couldn't stop blowing everything out trying roms. Got bored, something about breaking our phones makes it fun. Anyways I loaded this last night once I got everything unlocked. I really like this rom. It's very smooth. The only issue I have run into is not being able to register my fingerprint. On the set up it does nothing. (*I did just read that usually this issue is related to not being on Oreo firmware. Makes sense, I did not goto 20k after unlocking/rooting phone. I will give it a try and report back*)
Only other issue I noticed, my device shows as UNKNOWN. This caused Podcast Addict to have an issue setting language by default.
Click to expand...
Click to collapse
The fingerprint sensor does work on this ROM. I use it. And my device shows as LGE LG-H932SV on the play store on my desktop browser. So I do think it's probably not being on Oreo firmware first.
The only other issues I see (and I think they are known in other threads) the always on display causes some issues when turning the screen on sometimes. It also doesn't always turn on after turning the screen off. And the auto brightness is a bit off. I have to turn auto brightness on and slide the brightness bar all the way up for it to work right. This is also the only way the always on display can be seen. Otherwise it's too dim to even use. I have turned off auto brightness and the always on display for now. These two things were also issues in Lineage though.

Fingerprint issue fixed by flashing Oero 20k in twrp then flashing rom. Last night rom was flashed over 10d so firmware wasn't correct. Also device type has corrected itself so that was probably also in relation to firmware versions.
And yes, I noticed the always on display last night. I don't really ever use it anyways so I have no issue disabling it.

I just restored my Lineage OS backup because I just felt the heat issue was too much. It was also causing my battery to drain quickly and not charge as fast on a charger. After restoring Lineage, the phone is a lot cooler and battery seems better. It could have been just me. It could have been something in the background running for some reason but I couldn't find it. Maybe when the next RR update is release, I will do another clean install and see if I still have the issue. But I have to stick with Lineage for now even though I do think Resurrection Remix is better in a lot of ways.

jsgraphicart said:
I just restored my Lineage OS backup because I just felt the heat issue was too much. It was also causing my battery to drain quickly and not charge as fast on a charger. After restoring Lineage, the phone is a lot cooler and battery seems better. It could have been just me. It could have been something in the background running for some reason but I couldn't find it. Maybe when the next RR update is release, I will do another clean install and see if I still have the issue. But I have to stick with Lineage for now even though I do think Resurrection Remix is better in a lot of ways.
Click to expand...
Click to collapse
If you ever decide to go back try kernel managing app and mess with the governors and frequencies, every device is different.

Addiso said:
If you ever decide to go back try kernel managing app and mess with the governors and frequencies, every device is different.
Click to expand...
Click to collapse
I looked into that. I tried other governors but didn't really notice a change. And he already said he set the max CPU to less than what it came with before releasing it so I didn't mess with that all that much. But I'll take another stab at it eventually.

jsgraphicart said:
I just restored my Lineage OS backup because I just felt the heat issue was too much. It was also causing my battery to drain quickly and not charge as fast on a charger. After restoring Lineage, the phone is a lot cooler and battery seems better. It could have been just me. It could have been something in the background running for some reason but I couldn't find it. Maybe when the next RR update is release, I will do another clean install and see if I still have the issue. But I have to stick with Lineage for now even though I do think Resurrection Remix is better in a lot of ways.
Click to expand...
Click to collapse
I'm with you. When I left work my pocket was way too warm. My phone is inside or a thin silicone case. I just tossed it on charge after 6 hours of last full charge because it was already at 5%. System had used over 40% battery use. Only 3hr screen time. Kind of bummed out because I like this rom.

wireeater said:
I'm with you. When I left work my pocket was way too warm. My phone is inside or a thin silicone case. I just tossed it on charge after 6 hours of last full charge because it was already at 5%. System had used over 40% battery use. Only 3hr screen time. Kind of bummed out because I like this rom.
Click to expand...
Click to collapse
Just got home from work, looking in to issues posted

wireeater said:
I'm with you. When I left work my pocket was way too warm. My phone is inside or a thin silicone case. I just tossed it on charge after 6 hours of last full charge because it was already at 5%. System had used over 40% battery use. Only 3hr screen time. Kind of bummed out because I like this rom.
Click to expand...
Click to collapse
Glad to hear someone else's feedback. At least I know it's not just me now. Maybe this can be looked into and fixed with an update.

Question High battery consumption on idle

My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?

With AOSP ROMs, I even had worst experience when I installed one of the custom kernels because they somehow didn't put the phone into deep doze correctly. But yeah, the idle consumption is quite high - even on stock Kernel.
Currently I use HavocOS and its stock Kernel - and SuperFreeze (from F-Droid store) to freeze most apps right after screen lock. Idle consumption has dropped to 0.1-0.2%/h as a result. I made a thread some days ago regarding this topic... see here.

Thanks. Im gonna try your guide but it's not the most noob friendly guide I've seen
Just Kidding, thanks for your time.

Oh, my thread wasn't meant to be a guide... I did put it in "Question" like you did, but a mod seems to have moved the thread to "General"
My "solution" is only temporary - at least I hope there are still developers out there who value a low idle drain more than fast charging and benchmark numbers...

esszett said:
... and SuperFreeze (from F-Droid store) to freeze ...
Click to expand...
Click to collapse
Sorry for the OT, could it be that the app. is called SuperFreezZ?
Have you noticed any good battery life gains with this app.?

Yeah, sorry, SuperFreezZ: https://f-droid.org/en/packages/superfreeze.tool.android/
For several months I had the problem that from a certain moment, the consumption at idle suddenly increased enormously (from 0.1-0.2 % to 2-3% per hour). Even if I manually forced all apps to stop, In Android's battery info "Android OS" and "Android System" showed up with double-digit percentages. I could only get the phone back to its previous behavior with a restart.
To date, however, it is not clear to me what triggered this. I suspected GCam for a while, then Osmand+, but I couldn't ever confirm that because the problem didn't start whenever I used those programs, just sometimes.
I never found a real solution for this, but SuperFreezZ did.

The best thing I've used for years now is Greenify, its hasn't received an update in more than a year but still works perfectly

Do we need root to use these apps? I remember using greenify before onmy older devices with root but havent used it for a while. Gonna see how much it drops tonight and then try to tweek some things and recheck it tomorrow night.
Weird thing is, I was getting an awesome battery life out of poco x3 nfc, could it be because of the cpu idle? Because that's the only thing that seems different between the 2 devices. (X3 even had an lcd which is supposedly less battery friendly)

Kianush said:
Do we need root to use these apps?
Click to expand...
Click to collapse
Yes.
Kianush said:
I was getting an awesome battery life out of poco x3 nfc
Click to expand...
Click to collapse
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.

esszett said:
Yes.
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
Click to expand...
Click to collapse
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues? I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores. I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?

Kianush said:
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues?
Click to expand...
Click to collapse
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
Kianush said:
I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores.
Click to expand...
Click to collapse
I've never heard of it... This seems to be a powerful tool! Nice!
Kianush said:
I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Click to expand...
Click to collapse
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).

Kianush said:
My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
Click to expand...
Click to collapse
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.

Zaiaku said:
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Click to expand...
Click to collapse
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!

You could try BBS or similar apps. Maybe it's an app which prevents the phone to go to deep doze (wakelocks).
BTW: MIUI sucks

Kianush said:
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
Click to expand...
Click to collapse
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.

Zaiaku said:
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Click to expand...
Click to collapse
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.

Kianush said:
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Click to expand...
Click to collapse
Someone made a auto script for it, but you will have to reflash rom and factory reset data. You really shouldn't have to change cpu feqs. Also uploading a screenshot of my last 2 hours. I know its only 21min of SoT but also 2 hours off charger but playing pandora as well as some other app usage but still at 100%

esszett said:
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
I've never heard of it... This seems to be a powerful tool! Nice!
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Click to expand...
Click to collapse
Konabess without root won't start, any idea?
thanks

tojdvd said:
Konabess without root won't start, any idea?
Click to expand...
Click to collapse
Ah, ok... I thought you could load a separate boot.img - my fault, sorry!
Then you've to have root for Konabess...

Just to show what's possible with HavocOS 4.9 and 12.5.6 EEA firmware, see atached screenshot... It's with the stock kernel of HavocOS, but with the modifications I did mention here.
Running for almost 2 days
~8 hrs SOT (2 hrs of which with 120 Hz and 2 hrs of which with 100 % brightness, otherwise 60 Hz and brightness between 25 and 50 %) and still 50 % battery left.