I'm posting video footage of CPU usage after the phone reboots until all activated services are running.
It's PE+ with Magisk, EdXposed, GravityBox, CallRecorder, Viper4Android FX and more, core NetErnels.
The first video has the standard CPU clock, the second video has the lowest frequency reduced.
In the upper part you can see the performance of the individual CPU cores, in the lower right part you can see the CPU temperature as a whole.
Currently, the processor's performance does not respond to the temperature reached and continues to run at full power until the core crashes and shuts down.
Spoiler: Video
1.mp4 | on-line video
ulozto.cz
2.mp4 | on-line video
ulozto.cz
EDIT: Fixed duplicate link.
Get rid of EdXposed and get LSPosed since it has improved my performance a lot.
Weird In video 1 it shows temperature hits 54°,47°,.. and there is no halt in cores.
hmm That's really a problem that worth to look on it.
Is That some companies weird politics to get device retires quickly ? Or I'm just exaggerated.
There will be some sort of fuse for actual overheating. The core only shuts down when it's overloaded and overheated for a long time. Once it cools down, it runs again even at maximum.
It will be a hardware protection, probably integrated in the CPU chip. There is no software protection or regulation. Only governor-controlled power gain curves.
Well, I was curious to Finding out what's going on.
But the results on mine seems normal? as WITH NO MAGISK = NO MODULES.
- Project lighthouse Rom
- Neternels V2.0 Kernel
(Recorded Video Represented as Gif)
Spoiler: My results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, the CPU load will drop after all modules are loaded. That's not the problem. I took advantage of the longer load times to demonstrate the CPU behavior. If the CPU is not under load, you won't see anything.
Without add-ons and modules, the startup phase goes very quickly and you don't see the CPU under load.
You can also see the no-load phase at the end of my videos.
I'm attaching one more video.
The split screen is running moto navigation with ride video and CPU tracking on.
This time we can see temperature overload up to 60°C and also crashes of individual CPU cores.
https://thv1.uloz.to/9/1/9/9199cfa33bce506f904e16313adcac10.720.mp4?fs=AcJivfR2RM99&fide=unUCnGU&vt=1628632799&sg=G_V0sdr29Or3sy_5QVE0nQ&bl=
CPU power was allocated by the Governor himself.
Got some tips to force cpu usage to 100% to try to replicate? I tried benchmarks + recording etc and could not get it to push constantly past 50 on mostly stock pe+ with magisk.. and it didn't fail on like a 10-15m test
The application must not run in the background.
The split screen makes this possible.
CPU power is allocated by the Governor upon request by applications. For maximum performance, therefore, presumably Governor PERFORMANCE.
Edit: change governor
Today I tested the CPU in pure crDroid.
I turned on CPU tracking in crDroid and compared it with 3C tracking.
crDroid does not monitor the CPU temperature, but maybe the battery, or something else. Throughout the test, it showed 37°C, although 3C showed over 53°C and the cores were shutting down. crDroid did not even detect disconnected cores. So maybe the problem is monitoring a different temperature sensor.
StaryMuz said:
Today I tested the CPU in pure crDroid.
I turned on CPU tracking in crDroid and compared it with 3C tracking.
crDroid does not monitor the CPU temperature, but maybe the battery, or something else. Throughout the test, it showed 37°C, although 3C showed over 53°C and the cores were shutting down. crDroid did not even detect disconnected cores. So maybe the problem is monitoring a different temperature sensor.
Click to expand...
Click to collapse
How did the phone "feel" during your tests, i mean did you noticed it was actually hot? what about responsiveness?
The longer test was conducted while driving the car and running the navigation with video recording of the drive (5 min. loop). Heat was radiating from the area around the camera. The phone was quite hot. On the sunny side, the phone was shaded by a white, opaque cover (outside the lens). After warming up, the navigation stopped working. The navigation was freezing and the touch screen was not responding. It wasn't until a shorter test at home that I discovered that the CPU cores must have been out of order.
Navigation is Sygic with Dashcam recording.
I've used it in the past with slower processors, and never had that problem. It also got hot, but there was no crash.
StaryMuz said:
The longer test was conducted while driving the car and running the navigation with video recording of the drive (5 min. loop). Heat was radiating from the area around the camera. The phone was quite hot. On the sunny side, the phone was shaded by a white, opaque cover (outside the lens). After warming up, the navigation stopped working. The navigation was freezing and the touch screen was not responding. It wasn't until a shorter test at home that I discovered that the CPU cores must have been out of order.
Navigation is Sygic with Dashcam recording.
I've used it in the past with slower processors, and never had that problem. It also got hot, but there was no crash.
Click to expand...
Click to collapse
interesting... thanks for sharing!
did you report it to CrDroid dev ?
It's something to do with the phone. So far I have not found a ROM or kernel that does not have this problem. The problem manifested itself on Miui as well. It would be good if someone else could test Sygic with Dashcam running.
Related
Hey everyone...
So today while i was trying to download an app, my cpu temperature became 63C (145F).
I was wondering if this temp is even possible and what the temperature the phone is set to turn itself off at.
EDIT: Moto Atrix btw, tegra2 processor
I'm not sure about a mobile processor, but a desktop processor can well above 70, 80, or even 90 under heavy load.
63C sounds wayyy too high for a low voltage/power mobile cpu. Then again its hard to say, as the mobile chips are passively cooled.
Sent from my MB860 using Tapatalk
I was able to achieve overheat at a balmy 131°... I was driving in my car, it was charging and running navigation/trapster/iheartradio... I also live in Florida.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also seen 63. And suprising to me its one of the few times it didn't reboot
56 is normal "hot" for me.
Sent from the bowels of hell...
GatorRuss said:
I was able to achieve overheat at a balmy 131°... I was driving in my car, it was charging and running navigation/trapster/iheartradio... I also live in Florida.
Click to expand...
Click to collapse
thats your battery though, i am talking about processor.
I wopuld assume that this temperature is damaging to phone itself, i just wonder what the overheat level for the nvidia tegra2 is.
hmmm, still very intrigued. part of me wants to runn my phone as hot as it can till it over heats and reboots, and part of me is saying im a dumba** for even thinking of that, lol.
EDIT: just wanted to say im running greyblur, if that affects anything at all, lol.
Haha, I guess I really don't know much about mobile hardware then ^^
KefkaticFanatic said:
Haha, I guess I really don't know much about mobile hardware then ^^
Click to expand...
Click to collapse
I probably know more for hardware than software, don't feel bad, lol
But, actually, overheat status isn't true overheat function. When there is a true overheat, the phone either turns off or reboots itself. When the battery becomes too hot, the processor ignores that in most cases, while if the processor itself gets hot, it shuts itself down.
Yay, my first true member post, not junior anymore!!!! hahaha
I am also getting these high tempuratures on my cpu and not my battery.
My idle tempurature lowest was 35C and averages 55C and my highest was 70C and averages 65C. I really need help on how to fix this. My battery temp is around 40C
I set up a SetCPU profile so that if the CPU temp reaches 60C, it will max out the processor at 750 Mhz. For me, it pretty much cools off instantly. You may want to set yours lower. It doesn't reach that level often.
I've started a thread early today regarding the atrix's heat issues. Soon as I started playing games on my Atrix I got pretty scared with the temperature I felt on the exterior, and more scared after using temp. monitor apps.
http://forum.xda-developers.com/showthread.php?t=1249757
The idea is to mod the phone to help dissipating heat. Besides undervolting with setcpu I guess there isnt much that can be done at software level to reduce the main chip's heat.
The ideas are still being formulated. I opened the thread so I could get some help and suggestion from other atrix owners, to have a good idea of what to do when I finally open my phone
If anyone wants to try it or have any ideas, please comment there!
WolfFX, your link has actual "...." in the URL and doesn't work.
Regarding maximum temperature before shutdown, I'm wondering if anyone has EVER seen their phone shut off due to high heat? Does it even happen? I'm not meaning reboot either, but actual shut down to cool off.
palmboy5 said:
WolfFX, your link has actual "...." in the URL and doesn't work.
Regarding maximum temperature before shutdown, I'm wondering if anyone has EVER seen their phone shut off due to high heat? Does it even happen? I'm not meaning reboot either, but actual shut down to cool off.
Click to expand...
Click to collapse
Thanks man, I've corrected it. It got messed up due to copy - paste.
palmboy5 said:
Regarding maximum temperature before shutdown, I'm wondering if anyone has EVER seen their phone shut off due to high heat? Does it even happen? I'm not meaning reboot either, but actual shut down to cool off.
Click to expand...
Click to collapse
Yeah. Left the screen to never time up and setcpu to stress test. Left it on my bed covered by a pillow (accidents do happen, I'm quite forgetful and idiotic). Came back and the phone was in "emergency cool down mode"
Sent from my MB860 using XDA App
with faux 1.9 ive seen temps as high as 165± if its reading right and i did have profiles to back it down to 1100 but it hasnt shut off "yet"
unlocked bootloader att. atrix. honeycomb rom. faux oc kernal
Guys, I will repeat this just one more time. DO NOT let your CPU temperature get higher than 50C... Constant minor overheating causes long term damage to your phone, shortens it's life span.
One major overheating can toast your phone just like that.
These aren't desktop PCs, use common sense. Overclocking to higher than 15% doesn't come unpunished.
Also posted the same in the other operating temperature thread.
Did a bunch of looking around and after a while found some white papers with the following temperature ranges:
General operating temps of -40C to +85C.
Practical usage will start to drop off below -20C and above +70C.
This tells me that our safe operating range should be limited to the practical usage temperatures. Anything outside of these and there is a good chance you will see performance drop off fast, and also may suffer hardware lockups, etc.
Personally I will stick to +65C which is the rule of thumb I go by with my PC's under full load.
<edit> I would also add that while our phones are not desktops/laptops/workstations, the CPU's can all handle around the same temperatures in all devices. Materials used and manufacturing techniques are almost identical. The solder used has a melting point of around 180C - 190C, so there is no fear of melting the solder. The main difference is that phones do not have active cooling, so you will see much larger jumps and swings in temperature. This being the reason you cannot OC in the extreme ways you can with PC's.
i read a post somewhere that 75 degrees c was the max it should go to, anything higher is way too much
I read somewhere that if you overheat yer phone it eventually breaks. Pretty much it. Just don't let it out in the sun too long or anything silly. However, keep in mind that if you do break your phone, you can always donate it to XDA. I think they're looking for bricked and broken phones.
xploited said:
Guys, I will repeat this just one more time. DO NOT let your CPU temperature get higher than 50C... Constant minor overheating causes long term damage to your phone, shortens it's life span.
One major overheating can toast your phone just like that.
These aren't desktop PCs, use common sense. Overclocking to higher than 15% doesn't come unpunished.
Click to expand...
Click to collapse
Mine gets above 50C, and usualy around 57C, every time I open any kind of game... Should I be worried?
when i used my phone to play cricket game within 5 minutes it got hot near the camera and i couldnt continue playing the game. I was totally puzzled. Also when i speak a long call for more than 20minutes of continuous the same heat is felt near the camera. Why is it happening. What is the remedy for this? I really feel bad when it happens
How hot did it get?
Why couldn't you keep playing?
Most likely the temperature isn't hot enough to cause problems but I'm surprised search couldn't help you.
Sent from my GT-I9100 using XDA Premium App
its is so hot that if u keep on playing you feel that u may burn your fingers placed over the camera region and the heat transfers to the whole unit as well.
might be an idea to underclock to 800mhz
I must say that playing PES2011 or Reckless Racing for ~15 minutes makes SGS2 really hot. Not hot enough to "burn your fingers", but it's still hot. Elixir says that battery temperature after play equals ~41 Centigrades, so the GPU is about ~60, 70 maybe? Can't check it, dunno how.
Does anyone else have that problem?
Same here, i played Order and chaos for about 6 min and it got extremly hot, so i quit and went to set cpu where i saw temperature was 51ºC...
However, i usually have it underclock to 800mhz and theres no heat(max. 31 i think), but i havent tried to play at 800mhz, i always overclock it to 1200 minimum for playing HD games and still do little stops sometimes while playing...
r4aurean said:
I must say that playing PES2011 or Reckless Racing for ~15 minutes makes SGS2 really hot. Not hot enough to "burn your fingers", but it's still hot. Elixir says that battery temperature after play equals ~41 Centigrades, so the GPU is about ~60, 70 maybe? Can't check it, dunno how.
Does anyone else have that problem?
Click to expand...
Click to collapse
the same problem... but how do i under clock the device and how does that work for me to get out of my heat problem????
If you guys are playing at night time under low light conditions I suggest you get the App screen filter. It reduces the brightness below the lowest brightness settings that the phone can offer. I have noticed a big difference in gaming as my screen doesn't get hot anymore, only the back which is better than nothing.
kar111 said:
If you guys are playing at night time under low light conditions I suggest you get the App screen filter. It reduces the brightness below the lowest brightness settings that the phone can offer. I have noticed a big difference in gaming as my screen doesn't get hot anymore, only the back which is better than nothing.
Click to expand...
Click to collapse
I read some threads and they say that it has to be flashed, upgraded, rooted... confused...
Same Problem
Same problem here. Phone gets really hot around the front and back cameras, while playing games like RF11 or Asphalt6. Should I return it or flash a custom rom/different firmware. I am on XWKF3.
Same here on gaming..
The maximum battery temperature I've seen was 55 C while charging the battery, a game (Gangasta on message that data was downloaded successfully via Wifi) got stuck in background consuming a lot of CPU (~50%+).
Sorry guys, this phone as a severe design issue and the temperature problem can't be solved. You only can keep the cpu clock down.
He guys,
It's not only with playing games. My phone was doing nothing and the temperature raised (don't now the temp. but very hot) and the phone shut down, and was completely dead. Could not start it up. Could not charge it, because I thought it was empty. After cooling down, I took off the back and replaced the battery and I could boot it again. I was using internet 10 min. before. I think the cpu's where max. and getting hot. This is a serious problem, and I don't want to root my phone to clock down cpu. I am not a gamer so thats not a problem for me. First time this hapened in 1 1/2 month.
I feel realy bad about this. Did it shutdown because of the heat? Is there a safety thing build in? Is it damaged?
I' m wondering how the guys with overclocked devices cope with the heat. I have my phone only 5 days and it already crashed few times while playing games. Once it was getting hotter and hotter and it wasn't responding. i was worried so I had to hold the power button 10 seconds to turn it off. Maybe you(Frank-HTC) had a similar situation but with an app that was working in background?
jjegan2111 said:
when i used my phone to play cricket game within 5 minutes it got hot near the camera and i couldnt continue playing the game. I was totally puzzled. Also when i speak a long call for more than 20minutes of continuous the same heat is felt near the camera. Why is it happening. What is the remedy for this? I really feel bad when it happens
Click to expand...
Click to collapse
Update your ROM.
I flashed XXF2 and it does appear to be running comparatively cooler now.
Sent from my galaxy S2
Had a similar issue - the phone used to get quite hot while playing games.
However, Samsung seems to have fixed this issue (at least for SGS2 India users)
I can confirm that updating the stock firmware (KF1) to stock KF3 has solved this. Intense gaming for 2 hours straight, with Wifi and lots of processes running, the phone is only mildly warm.
If you are experiencing this issues, please try backing up your data and updating your firmware via Kies.
My phone doesn't have this issues, I'm using a water-cooling system now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
May this thread die in peace...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is unfortunate, it is not even hot so I don't know what's up.
Sent from my LG-E970 using xda premium
There is the temp as says setCPU
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Tim4 said:
Whats your max. level?
My one going only till 63%
Oh there a screenshoot attached.
Anyway its far higher than the 63% at 39C
Click to expand...
Click to collapse
I am unsure if this is just over caution on their part of if this is something we need to be worried about... honesty even yours at 39c is not that hot 102 F which for a computer is whatever... but I thought this chip was supposed to run cooler and everything being the new architecture.
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
gafalas said:
I have been doing a lot of CPU testing and noticed a couple of things:
First of all the issue with the screen not turning brighter is simple: the heat within the device reached a certain limit that could potentially damage it.
the CPU, RAM and the screen light are the main culprit. Especially the CPU and RAM, try CPU stats and after heavy use you will notice the phone gets warm/hot and the freq gets capped out at 1.1 GHz by the kernel. This is mainly to reduce the heat obviously....I guess keeping the phone running at 1.5 GHz with all 4 cores and the screen cranked up to max will definitely turn the phone into a Coleman stove in no time.
So i guess this powerful CPU doesn't do any better than any dual core running constantly and stable for the same amount of time to crunch performance levels. Sigh...I guess until they wont figure out to make things run cooler powerful CPU's wont get far-only on paper
Just my 2 cents
Click to expand...
Click to collapse
You are right on point. I have seen it drop (I believe to 1180) when running a bunch of benchmarks. The manufacturer sets the heat threshold at a very safe level. Kernel devs are usually able to safely bump that up another 10 to 15 degrees. I am one of the lucky ones that got the variant 3 of the international One X. Variant 3 was the strongest version and I ran all 4 cores at 1600 with 51 minimum. Faux usually figures out how to uncap and raise the throttle temperature... but he's on a N4. I am going to keep an eye on the kernel threads there and see how far they push things. Chainfire's "PerfMod" app is perfect to watch this while running different apps
Sent from my LG-E970 using Xparent ICS Tapatalk 2
While trying to diagnose my marginal to moderate battery life on my DNA, I realized that the battery level was dropping significantly while idle; anywhere from 3-6% or more per hour. After installing Betterbatterystats and monitoring/testing for a couple of days, one of the main culprits appears to be a mysterious kernel wakelock identified as "msm_hsic_host". There have been postings in the Nexus 4 forums about the same thing, as well. It seems to be a mystery because no one seems to know what is causing it or what it is related to other than these two Qualcomm S4pro phones both seem affected by it.
The msm_hsic_host KWL seems to reduce deep sleep from anywhere between 10 to 30%. No solutions or information have turned up in the Nexus 4 forums yet, unfortunately. Anyone have any ideas or more information? Below is a screenshot from BBS demonstrating this problem. Even though the time period isn't terribly long, it is really compounded at night, keeping the phone awake anywhere from 1-4 hours over a 6-8 hour idle period.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I doubt that is the real reason.
Mine was dropping 8% over 6 hours while idle. it is in Wifi environment, not bad 3G/4G of course.
8% over 6 hours is acceptable to me. And my kernel wakelock for that entry is even higher than yours. 18%.
I don't think it is the culprit.
Did you check the partial wakelock? What is the biggest entry there? Is it above 3%?
I've been having problems as well and found that mediaserver and adaway for some reason were eating away at my battery at about the same rate as your phone. What I did to fix it was install rescan media and just uninstall adaway and use adblock plus instead. Msm_hsic_host is still the highest on my kernel wakelock, but only at 2.2% now.
jiwengang said:
I doubt that is the real reason.
Mine was dropping 8% over 6 hours while idle. it is in Wifi environment, not bad 3G/4G of course.
8% over 6 hours is acceptable to me. And my kernel wakelock for that entry is even higher than yours. 18%.
I don't think it is the culprit.
Did you check the partial wakelock? What is the biggest entry there? Is it above 3%?
Click to expand...
Click to collapse
After unlocking the boot-loader last night - which factory resets the phone - I am getting upwards of 63.4% of my wake time from msm_hsic_host, with total awake time at 99.1% over a 1.5 hour period. So I'm not sure what's happening. It's possible that the kernel is still settling down some as it is prone to do after a factory reset or new install. Will have to experiment more.
My partial wakelocks are slightly higher than I would like, but still reasonable, and nowhere near the number of the KWLs.
I am having this same exact issue with my dna.
Number 1 for me as well. All stock with nova launcher.
Very good!
That issue is fixed in Faux123's N4 kernel, and my DNA kernel.
D
.
No way around it if you aren't rooted?
Qualcomm strikes again. You are experiencing what us N4 users are getting too. This phone stays awake too much of the time. Qualcomm needs to update their drivers or something. Any other SoC sleeps much more than this one it seems. Maybe it's the early adopter curse. All other use of these S4 pro equipped phones seems to point to great battery life. It's a great gaming SoC but what I wouldn't give for the Exynos 5 dual to be put into a phone that doesn't have touchwiz. That baby sips battery and really has some power despite being "only" a dual core.
This is my top or second most used process draining my battery as well. I use GSam battery app and under the "kernel wakelock" it shows up as 155 wake locks after being unplugged for 8 hours. Is this a lot? I have no idea what wakelock and kernels are, I just know this is in the top for battery usage.
spinkick said:
No way around it if you aren't rooted?
Click to expand...
Click to collapse
Not that has been reported. I turned off most of the Latitude stuff and that seemed to help a little. Also, in the N4 forum, we seem to have corroborated that noisy wifi environments with lots of clients on the AP seem to cause a lot of wlan_rx_wake wakelocks.
Simple explanation
I am an N4 user, both devices use the APQ8064 qualcomm chip (note not an msm chip) APQ8064 DOESNT have a built in modem, the modem is connected via USBOTG and is read as a USB device (thats the wakelock there its OTG modem
Cubed Kernel
If I'm not mistaken, I think the Cubed kernel addressed this issue.
I'm stock and locked, had a misbehaving app (OpenSignalMaps) that would bring me down 40% overnight. Uninstalled that and now am 1% per hour.
Well since I love getting into technical results with this Rezound since I got it, I'm pretty much really late to the game with this phone. My Thunderbolt took a crap on me during deployment and I've been spending the last 2-3 weeks working on it here and there to make it the best battery life for my OWN personal usage.
People may say *Oh dur turn on 4G* I know 4G eats battery, but where I'm at, I get very very spotty signal, Most I use is 3G sending MMS. I keep data off all day since I just text.
Since I get spotty signal, obvious answer is my phone will use more battery for itself. I'm am well aware of this. I have most of the stuff memorized I have done to this phone, rom wise, build.prop, Kernel Tweaker etc. So if you have any questions about what I've done just ask me. It's hard enough to search through a ton of threads and get VERY VERY vague answers. Seems like it's been like this since I jumped on the HTC Inc back in the day
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did take these with my camera because screenshot didn't wanna work properly with me so I just grabbed my camera and shot the pics off. If anyone wants me to post my usuage from yesterday via battery_stats I can.
EclipticRez 5.2.1
Funky v2.3, S2W disabled.
The best results I've found in regards to battery life is with using Kernel Tuner and giving each processor core a different governor (cpu0 Badass, cpu1 Conservative) and underclocking and tweaking some settings in MPdecision. Also, turn off auto-brightness. Take it to around 35-40% and just leave it there.
I also leave LTE on at all times, but I also use WiFi wherever available.
Granted, I don't have my extended battery (yet - just ordered one earlier in the week), but I finished yesterday with 17 hours and 2 hours and a few minutes of screen on time. That's just with the standard 1620 mAh battery.
liqwidzero said:
The best results I've found in regards to battery life is with using Kernel Tuner and giving each processor core a different governor (cpu0 Badass, cpu1 Conservative) and underclocking and tweaking some settings in MPdecision. Also, turn off auto-brightness. Take it to around 35-40% and just leave it there.
I also leave LTE on at all times, but I also use WiFi wherever available.
Granted, I don't have my extended battery (yet - just ordered one earlier in the week), but I finished yesterday with 17 hours and 2 hours and a few minutes of screen on time. That's just with the standard 1620 mAh battery.
Click to expand...
Click to collapse
Well I will defiantly try that out, I was also using auto the whole day since I was constantly inside/outside when the sun was blaring.
What are your current MPDecisions in Kernel Tweaker?
Also in Kernel Tweaker, does it not sometimes load your settings for the CPU? I heard it was kernel related and not ROM related. Sometimes my CPU0 would stay at 1080MHz where I set it at but CPU1 would reset to 1.5Ghz
savagebunny said:
What are your current MPDecisions in Kernel Tweaker?
Also in Kernel Tweaker, does it not sometimes load your settings for the CPU? I heard it was kernel related and not ROM related. Sometimes my CPU0 would stay at 1080MHz where I set it at but CPU1 would reset to 1.5Ghz
Click to expand...
Click to collapse
Mine jumps back up to 1.5 on CPU1 as well, but that's a non-issue. Set it to Conservative. Make sure that the minimum is set at 384 MHz for each core. Otherwise it will just start jumping around (at least, that's what happens to me). I don't know if it's exactly kernel related, though. I was able to run Funky 2.4 on a Sense 4 ROM (Newt's OneXxX 6.0.2, I think) and cpu1 stick, though.
MPdecision:
Service Start Delay: 10000 ms
Pause: 10000 ms
Threshold Up - Load: 40 ms
Threshold Up - Time: 450 ms
Threshold Down - Load: 5 ms
Threshold Down -Time: 250 ms
Idle Frequency: 192
liqwidzero said:
Mine jumps back up to 1.5 on CPU1 as well, but that's a non-issue. Set it to Conservative. Make sure that the minimum is set at 384 MHz for each core. Otherwise it will just start jumping around (at least, that's what happens to me).
MPdecision:
Service Start Delay: 10000 ms
Pause: 10000 ms
Threshold Up - Load: 40 ms
Threshold Up - Time: 450 ms
Threshold Down - Load: 5 ms
Threshold Down -Time: 250 ms
Idle Frequency: 192
Click to expand...
Click to collapse
Thanks. Ya that's what I just set it too. I was using dancedance on both cores when I posted up the screen shots. Will see how it goes for the most of the day. Yesterday I sent out almost 300 texts maybe or more so that was a majority of screen time with 3 different people to say the least.
Oh and another anomaly I can't quite figure out. Some days my phone only pulls less than -100mA and then only ~-20mA on average in screen off sleep. Now today instead of doing the same thing yesterday, todays average has been more near ~ -280mA+ with screen off sleep
I have changed nothing on the phone. Did a restart, no change. Shut phone down completely, pull battery and reboot and still the same result. And even when people ask me what my wakelocks are, I post them and then no one knows what they are nor can I find documentation on the software itself.
did u tried to check it with gsam battery to see what drain or what waking up the phone ?
Try uninstalling some memory intensive apps and reinstall them. Sometimes restored files, for me, just need to be reinstalled.
Also, I just received my extended battery and I'll see how far I can go with it.
How has your phone been doing since the new settings?
Sent from my ADR6425LVW using xda app-developers app