Database Develop

nueDynamicClock 1.3 works on Imagio! Yay battery life!

Im so happy Have run the battery down low & not experianced any problems locking up when waking up from battery (provided you dont set the mhz too low when you suspend!!! It doesnt "lock up" so much as takes an eternity to wake back up, haha)
No good settings for you (running automatic voltage), 528mhz for 10 seconds, 245.76 system idle, 122.88mhz on backlight off, 61.44mhz on suspend.
19mhz suspend takes too long to wake to be worth it.
Anywho... Unplugged from the charger around 10pm last night @ 100%. Still on 85% almost 12 hours later! (haven't really used the phone much until right now hah)
http://forum.xda-developers.com/showthread.php?t=507212
http://www.nuerom.com/BlogEngine/post/2009/05/09/nueDynamicClock-13.aspx

Works out overall to over > 2 more days of standby VS what I was getting yseterday. Killer!
Fast enough underclocked @ 61mhz to play mp3/aac/htc FM player audio no skipping or problems.
Gotta love that LoL!
Personally, got it set to 528mhz for 10 seconds, then 61mhz after for anything else.

Don't think it is working for me. Says....
Current processor speed and voltage:
0.00 MHz @1.1V

Confirmed! It worked but it didn't help to improve my battery even i ran at power saving mode.

I bricked my phone doing some stupid registry edit (it was stupid... should have known better... Had Hex selected instead of Dec) anyways hard reset my phone installed everything including this and now it works ... I love happy accidents lol

i try to install this and it says it is being blocked by something on the phone? it says it will try to fix but needs to restart and then nothing? any help

anybody else have a problem installing this?

DadamsJR said:
anybody else have a problem installing this?
Click to expand...
Click to collapse
Down this file below and install it before installing nueDynamicClock

thank you very much! Davey

leonarderman said:
Down this file below and install it before installing nueDynamicClock
Click to expand...
Click to collapse
That did the trick for me

Seems to lock up my phone coming out of suspension. I have tried the settings on the first post but seems to always lock up. Timmay!!!

Problems after Repair (Battery or Processor)

I sent my phone in for the purple camera problems and I got it back last week.
When I received it, it was updated to 4.3 Sense 5, most likely from the latest RUU.
Since I got my phone back, my battery has been horrendous and I noticed it had heat problems. I checked battery health and it said it's good, so I figured I just needed to re-calibrate my battery so I gave it a week of use. It's been the same horrible battery life.
I checked for wakelocks but there were no significant ones I haven't seen before. I've attached some screenshots of battery use. One thing that confuses me is that it shows Wifi running for 9 hours, even though I had it off for most of that. Is this normal?
To deal with the heat, I had to install a custom kernel and undervolt/underclock a bit. Before flashing, I noticed this thing is forcing itself to max frequency (1.7 GHz) which explains the heat. So the battery is draining because of this, presumably. I switched to intellidemand and lowered the clock a bit so it can last 12 hours (Doing nothing at all) instead, but that's still horrible compared to what I had before I sent it in.
Before I sent my phone in I typically had stock kernel while using insert coin or trick, Power Saver On, Auto-Sync Off, All Play Services/Google Now On and got 4-5 hours OST. Now I can barely get 2 hours.
Does anyone know where I can look to find the cause of my processor forcing itself to max frequency? I want to figure this out before I annoyingly have to send it in again. (Have to S-On/Re-Lock again =\)I was thinking maybe something shorted when they replaced the camera.

PcFish said:
One thing that confuses me is that it shows Wifi running for 9 hours, even though I had it off for most of that. Is this normal?
Click to expand...
Click to collapse
Settings -> Wi-Fi -> Advanced (in the menu) -> uncheck scanning always available

nkk71 said:
Settings -> Wi-Fi -> Advanced (in the menu) -> uncheck scanning always available
Click to expand...
Click to collapse
Thanks, I guess it's normal then since I never turned that off before.
Now to figure out why the cpu is forcing max frequency all the time on stock kernel/firmware.

PcFish said:
Thanks, I guess it's normal then since I never turned that off before.
Now to figure out why the cpu is forcing max frequency all the time on stock kernel/firmware.
Click to expand...
Click to collapse
must be some rogue app, maybe best to factory reset, install (or restore) apps one by one.
if you're rooted use Titanium Backup, and check out Greenify for facebook and similar apps.

nkk71 said:
must be some rogue app, maybe best to factory reset, install (or restore) apps one by one.
if you're rooted use Titanium Backup, and check out Greenify for facebook and similar apps.
Click to expand...
Click to collapse
Those screenshots were from after factory resetting. I'm considering RUUing back to 4.1.2 and flash my way back to 4.3 and see if that helps.

PcFish said:
Those screenshots were from after factory resetting. I'm considering RUUing back to 4.1.2 and flash my way back to 4.3 and see if that helps.
Click to expand...
Click to collapse
see how it goes with the wifi scanning off

nkk71 said:
see how it goes with the wifi scanning off
Click to expand...
Click to collapse
That gained me maybe an hour. Just applied a Sense 5.0 4.3 and it seems to be better. 10 hours on idle with 40% left. A lot better than 8 hours to dead. I'll give it a couple days and re-calibrate the battery to see if it's all okay. I've noticed very steep drops from when the screen is on. Thanks again for the help.

PcFish said:
That gained me maybe an hour. Just applied a Sense 5.0 4.3 and it seems to be better. 10 hours on idle with 40% left. A lot better than 8 hours to dead. I'll give it a couple days and re-calibrate the battery to see if it's all okay. I've noticed very steep drops from when the screen is on. Thanks again for the help.
Click to expand...
Click to collapse
"I've noticed very steep drops from when the screen is on" <- try lowering the max screen brightness

I officially give up on Lollipop

regarding the wifi battery drain bug. I've been scouting the Internet and found different suggestions from:
1. Changing Wifi Frequency
2. Turn off High Accuracy mode for GPS
3. Use custom kernel
4. Use custom Rom with R7 code
5. Uninstall apps, by using WLD to detect.
Some of my own:
1. Turn down screen brightness
2. Change my Wifi channel to N-only mode (5Ghz)
3. Flash back to KK 4.4.4 and OTA to L (UPDATE)
But nothing seems to help the drain while USING the freaking phone. I mean I surf the web with Wifi on and the battery drains quickly. I can't turn off wifi because I need it badly due to the fact I have the T-Mo $30 plan.
So therefore, I'm giving up trying and just have to charge more.

I never had this issue
Sent from my Nexus 5 using XDA Free mobile app

You could just try to live with it, i don't have this bug at all, but also i dont need wifi so much, have 15 GiB Data from Vodafone DE and just use it up like 90%..
You could also try to flash factory image and don't import ur apps, just go fresh

Out of curiosity, how much better was you phone on 4.4.4?
And, who can point me in the direction of how best to downgrade to 4.4.4?
Thanks.

Same here man. Here is what I've done so far to try to get back to Kitkat battery life.
I've fresh flashed the image at least 10 times using the flash all.bat on 2 different computers with matching MD5 downloads.
I've used it both stock/stock rooted, both unlocked/locked bootloader, both with/without user apps.
I've used several builds of Nexus 5 Experience, Slim , and Cataclysm ROMs.
I've used stock, Slim, Franco, ElementalX, Code Blue, Hellsgod, and Faux kernels.
I've used the setup as new device option at least 5 times on clean ROM flashes.
I've used Greenify and Lean Droid.
I've tried deleting all of but the most basic needed system apps.
I've turned off all battery drainers: Google Now, Location Services, Auto Brightness, Google Fit.
I've set mobile data to 2g only, set wifi to turn off while asleep, set wifi to 2.4 or 5 only, set it to device only GPS.
I've turned off auto brightness.
I've tried undervolting, tried underclocking, tried conservative governors.
I've tried doing a battery calibration.
.....there's probably a few more things I've tried as well but am not remembering right now.
I've tried quite literally every possible thing I can think of that I've picked up over the years as battery tips.
I'm still only able to get around 3 MAAAAAYBE 4 hours of combined usage on a good day which for me is listening to music over bluetooth and SOT combined. Compared to Kitkat that is about 2 hours give or take 30 minutes of less than before. Luckily I'm always near a charger.
Project Volta my patooty.:silly:

ronnienyc said:
Out of curiosity, how much better was you phone on 4.4.4?
And, who can point me in the direction of how best to downgrade to 4.4.4?
Thanks.
Click to expand...
Click to collapse
Did you flash via the OTA update or through adb sideload on stock recovery?
Either way, you're going to have to unlock your phone to downgrade to 4.x, because you'll need to flash the factory image for it. Here's a quick overview of the process:
1. Download the factory image for your phone at https://developers.google.com/android/nexus/images
2. If you haven't already unlocked your N5, you need to --- and back up anything important first, cuz it all gets erased. Google how to do it -- there are toolkits to do this quickly and painlessly (I think WUG's is one?). Look in the dev section for it.
3. Once you're backed up, unlocked, and factory image downloaded, you use fastboot to flash the factory image. Google how to flash nexus factory images, and substitute the image you have in place of the image any guides have.

For unlocking your Nexus 5 Bootloader, you first need to boot into fastboot mode. This can be done by turning off your phone, holding vol down and power and wait till the screen responds.
Now you need to connect your phone to your pc, be sure you installed the google usb driver for full support of fastboot mode.
Now you can go ahead and install Fastboot/ADB, there are plenty of Tutorials in this section for this.
Now open your cmd, and type
Code:
fastboot oem unlock
On your phone you will now see a selection, which you have to answer with YES.
Voilla, you have an unlocked Bootloader.
ALL YOUR DATA IS NOW LOST
Now just flash Factory 4.4.4 with flash_all.bat

This is true the battery is not very good but when you are using custom kernels please tweak them and learn how to tweak them using several kernel tuning apps like synapse faux clock, kernel tweaker, trickster mod etc
And if after tweaking u still are not getting results please try changing your kernel settings to new ones keep testing until you find suitable settings
All the best

Anyone want to comment on how LL battery life compared to 4.4.4 on their nexus?
In any case, I see little improvement in LL.
IMO 4.4.4 was better. At least you didn't have to swipe away notification screen every time you power on the screen.
If all we are gaining is slightly "smoother" experience, and encryption, then who gives a sh!t.
---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------
Kartoffelrudi said:
For unlocking your Nexus 5 Bootloader, you first need to boot into fastboot mode. This can be done by turning off your phone, holding vol down and power and wait till the screen responds.
Now you need to connect your phone to your pc, be sure you installed the google usb driver for full support of fastboot mode.
Now you can go ahead and install Fastboot/ADB, there are plenty of Tutorials in this section for this.
Now open your cmd, and type
Code:
fastboot oem unlock
On your phone you will now see a selection, which you have to answer with YES.
Voilla, you have an unlocked Bootloader.
ALL YOUR DATA IS NOW LOST
Now just flash Factory 4.4.4 with flash_all.bat
Click to expand...
Click to collapse
And yes, thank you. Fortunately, I have rooted tons of phones before, so I shouldn't get too lost
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
Just for comparison's sake, I have been using my iPhone 6 for the past 4 hours, and it reads 94% remaining battery.

ronnienyc said:
[/COLOR]Just for comparison's sake, I have been using my iPhone 6 for the past 4 hours, and it reads 94% remaining battery.
Click to expand...
Click to collapse
You weren't using it full screen on and playing anything intensive....
Iphones drain just a badly when you use them. When screen off sitting, they have wonderful battery. But who cares? I leave my phones on chargers when Idle.

tweaked said:
You weren't using it full screen on and playing anything intensive....
Iphones drain just a badly when you use them. When screen off sitting, they have wonderful battery. But who cares? I leave my phones on chargers when Idle.
Click to expand...
Click to collapse
You're right - I wasn't using my iPhone 6 to "play" anything. I was using it to get work done: Emails, web, phone calls, SMS etc. It lasts two days for these purposes. My Nexus 5? 4-5 hours.
(and uh, no. It doesn't drain as badly. There's no contest there.. I prefer Android, but goddamn...I can't run around with a charger in my pocket. Not gonna happen)

2 days is my usual battery time. Same as kitkat, don't know what you r talking about wifi battery drain. Wifi is 90% turned on.

ronnienyc said:
You're right - I wasn't using my iPhone 6 to "play" anything. I was using it to get work done: Emails, web, phone calls, SMS etc. It lasts two days for these purposes. My Nexus 5? 4-5 hours.
(and uh, no. It doesn't drain as badly. There's no contest there.. I prefer Android, but goddamn...I can't run around with a charger in my pocket. Not gonna happen)
Click to expand...
Click to collapse
4-5 Hours? You should re-image it man. You have something wrong. I get 4-5 hours of game, email, and music stream time on battery. If I Only do internet, email and phone I get an entire day.
Lucky for me these are toys. I would never be beholden to my electronics. lol

I'm not seeing any of these issues on Lollipop. Battery life has increased for me over KitKat.
I've been using Stock rooted with Code Blue.
A couple questions though...
Do you only make one change at a time and then test?
After making changes, how long do you test those settings before making additional changes?
Why did you switch it to 5GHz only? 5GHz has more trouble with walls and has a smaller coverage area than 2.4GHz.

Never had any issues with the WiFi but I turned off Google Now listening and almost tripled my daily battery life.
Sent from my Nexus 5 using XDA Free mobile app

I've just gone back to 4.4.4 - will see if battery improves or not.
I really did not see anything particularly better about LL anyway.

I'm having my share of problems with Lollipop (though things have been improving over the past week or two,) but the wifi power drain never hit me. Wi-Fi battery life is a bit worse than I had on Kitkat: idle drain is excellent, but SOT has gone from a comfortable 4 - 5 hr to 3 - 4 hrs (in a 12 - 15 hr day***), I can easily get well over 5 hrs, but that'll be at the cost of a significantly shorter 'day'. 3G, on the other hand, is chawing through battery rather aggressively compared to Kitkat & it hurts.
On both Kitkat & Lollipop I was/am running pure stock with everything on (Always listening, precise location, location reporting, bluetooth, etc. The only thing I've knowingly turned off is NFC (after accidentally setting my phone on a tag & tag-calling my mom at 4 AM ) No gaming, but several hours of podcast listening or Tune-In radio listening every day.
*** Usual average day from full charge to ~12% but early on there were a few days that barely lasted 10 hrs with under 3 hrs SOT.

I've been using the stock factory image and haven't encountered this wifi draining bug.

Update with reverting back to KK 4.4.4 from factory images and OTA to L in OP but only help with idle but not when using phone.

ronnienyc said:
Just for comparison's sake, I have been using my iPhone 6 for the past 4 hours, and it reads 94% remaining battery.
Click to expand...
Click to collapse
ronnienyc said:
I was using it to get work done: Emails, web, phone calls, SMS etc.
Click to expand...
Click to collapse
I'm not sure if you realize this, but you claimed you can get 66.6 hours of active usage on a single charge with your iphone 6. I don't think I need to explain how ridiculously impossible that is. Maybe you should stop exaggerating so much if you want people to take you seriously. Assuming what your battery life is and knowing, are two very different things.
I'd put money down the phone wasn't actively used for more than 1 hour in that time. 16 hours of usage is within the realm of possibility.
For the record, my colleague beside me right now has an iPhone 6 PLUS (more battery) and confirms that is impossible. You couldn't even read ebooks at 0% brightness for 66 hours. I'd ask for proof but your phone of choice has no way to do so and we all know it could never happen anyways.

[Q] Nexus 6 Overheating issue

My new Nexus 6, is now too hot to start, when booting up it turns off before it can ask for the pattern to decrypt the phone. It loads up fine in Fastboot and Recovery, but the CPU temperature in recovery is displayed ranging between 67-70 degrees Celsius. The phone is a month and a half old.
It was performing well without a glitch (apart from the random reboots and 'not charging' at times when plugged in).
Over the last week it started charging really slowly, showing 9 hours to a full charge when the battery was 15%., and after being on charge for that amount of time, the battery topped charging at 65% each time. I suspected that the Turbo Charger/Cable were faulty but other chargers (turbo/normal) and cables showed the same results. The displayed battery health was shown as good. I figured out that the phone could charge up from )% to full in 1.5 - 2 hrs approximately on any of those chargers and cables including the original ones when in Fastboot or Recovery mode. I started charging my phone in recovery mode. The CPU temperature used to be around 65 C. I had done a complete factory reset/data wipe/cache wipe to try and fix the problem.
The phone is rooted, running stock 5.1 rom, latest official TWRP recovery although no apps that use root.
Since day before yesterday the phone started randomly shutting down every 15 - 60 min, overheating I suspect. The battery health was displayed as 'overheat' and he phone completely refused to charge when powered on, and now shuts down when powering on before it can ask for the decryption pattern, though it runs fine in Fastboot/TWRP Recovery. CPU Temp shows as 70C in Recovery.
Please help.

Ahmer Jamil Khan said:
My new Nexus 6, is now too hot to start, when booting up it turns off before it can ask for the pattern to decrypt the phone. It loads up fine in Fastboot and Recovery, but the CPU temperature in recovery is displayed ranging between 67-70 degrees Celsius. The phone is a month and a half old.
It was performing well without a glitch (apart from the random reboots and 'not charging' at times when plugged in).
Over the last week it started charging really slowly, showing 9 hours to a full charge when the battery was 15%., and after being on charge for that amount of time, the battery topped charging at 65% each time. I suspected that the Turbo Charger/Cable were faulty but other chargers (turbo/normal) and cables showed the same results. The displayed battery health was shown as good. I figured out that the phone could charge up from )% to full in 1.5 - 2 hrs approximately on any of those chargers and cables including the original ones when in Fastboot or Recovery mode. I started charging my phone in recovery mode. The CPU temperature used to be around 65 C. I had done a complete factory reset/data wipe/cache wipe to try and fix the problem.
The phone is rooted, running stock 5.1 rom, latest official TWRP recovery although no apps that use root.
Since day before yesterday the phone started randomly shutting down every 15 - 60 min, overheating I suspect. The battery health was displayed as 'overheat' and he phone completely refused to charge when powered on, and now shuts down when powering on before it can ask for the decryption pattern, though it runs fine in Fastboot/TWRP Recovery. CPU Temp shows as 70C in Recovery.
Please help.
Click to expand...
Click to collapse
Flash factory image, lock bootloader, and RMA.

Evolution_Tech said:
Flash factory image, lock bootloader, and RMA.
Click to expand...
Click to collapse
What is RMA?

Ahmer Jamil Khan said:
What is RMA?
Click to expand...
Click to collapse
Returning the phone to the seller to be exchanged for a new device. RMA https://www.google.nl/search?q=rma&ie=utf-8&oe=utf-8&gws_rd=cr,ssl&ei=sihYVcWrCcyBU-vVgIgM.

gee2012 said:
Returning the phone to the seller to be exchanged for a new device.
Click to expand...
Click to collapse
Thanks a lot. Flashed a stock ROM/Recovery and locked the bootloader again. Will be shipping it off.
Just wondering, what caused this kind of an issue?

Ahmer Jamil Khan said:
Thanks a lot. Flashed a stock ROM/Recovery and locked the bootloader again. Will be shipping it off.
Just wondering, what caused this kind of an issue?
Click to expand...
Click to collapse
Probably a hardware issue, it can happen

Probably not a good idea to charge in recovery as all cores are always maxed out, causing it to be hot anyway.

Reflash the stock kernel using the flashify app from app store. This will rule out software issues
https://play.google.com/store/apps/details?id=com.cgollner.flashify

After looking at thread like these , i am reluctant to use the Quick Charger that came with the phone. I normally charge the phone with USB (PS4) or a normal Samsung Charger

Where people go wrong is using the phone while fast charging. Playing a graphics intensive game or streaming video while fast charging isn't typically good for battery temps

No amount of re-flashing will fix the problem. The Nexus 6 has a known overheating problem. I am using a workaround and so far have not had a single incident. I was getting two or three reboots a day before this. Set the screen resolution to 1080p. Instructions here:
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
This also works with rooted Marshmallow with Elemental kernel. You will not notice a difference - other than the reboots stopping and your battery lasting longer.

madmartian said:
No amount of re-flashing will fix the problem. The Nexus 6 has a known overheating problem. I am using a workaround and so far have not had a single incident. I was getting two or three reboots a day before this. Set the screen resolution to 1080p. Instructions here:
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
This also works with rooted Marshmallow with Elemental kernel. You will not notice a difference - other than the reboots stopping and your battery lasting longer.
Click to expand...
Click to collapse
not true. first off, describe "overheating".
i run my cpu set to 3033mhz high and low. no matter what i do, i can not get it to "overheat". when the n6 overheats, it reaches 100C, at which it will either power off or reboot at that point. thus happens to let the cpu cool off.
remember, you are running a quad core cpu, at 2649mhz by default. now i ask again, describe "overheating".
oh, and one more. it has been proven already that lowering your resolution does not save battery. you arent disabling pixels, that where the same amount of the power is lost, no matter what you change your resolution.
anything else? :silly:

simms22 said:
not true. first off, describe "overheating".
i run my cpu set to 3033mhz high and low. no matter what i do, i can not get it to "overheat". when the n6 overheats, it reaches 100C, at which it will either power off or reboot at that point. thus happens to let the cpu cool off.
remember, you are running a quad core cpu, at 2649mhz by default. now i ask again, describe "overheating".
oh, and one more. it has been proven already that lowering your resolution does not save battery. you arent disabling pixels, that where the same amount of the power is lost, no matter what you change your resolution.
anything else? :silly:
Click to expand...
Click to collapse
It solved the problem for me. That is a fact. Others have also posted that it has solved the problem for them. When playing certain graphic-intensive games, the battery would drain quickly and the phone would overheat and reboot. It is of course true that the screen pixels are still lit, however, the system doesn't have to keep track of all that extra data and the app has less work to do, thus it really does save battery and prevent overheating. It's the same as speeding up your fps in a PC game by lowering your game resolution, even though you're still using the same monitor.

madmartian said:
It solved the problem for me. That is a fact. Others have also posted that it has solved the problem for them. When playing certain graphic-intensive games, the battery would drain quickly and the phone would overheat and reboot. It is of course true that the screen pixels are still lit, however, the system doesn't have to keep track of all that extra data and the app has less work to do, thus it really does save battery and prevent overheating. It's the same as speeding up your fps in a PC game by lowering your game resolution, even though you're still using the same monitor.
Click to expand...
Click to collapse
i give you a few points with the gpu, but the amount saved would be extremely minimal. unless thats all you do, play games all day. then you might see an extra 5%, maybe.

I have huge heating issues when bulk-gaming. I even tried capping the GPU at 300 MHz. It's fine just gaming but gaming and charging is a no no for me. It *used* to work fine, but now it just throttles, even though it is only running at maybe 60 Degrees C. (I set my thermal throttle at 75). It's not really so much of an overheating issue as it is a throttling issue. Throttling on this device is poor and hard to work around.

danarama said:
I have huge heating issues when bulk-gaming. I even tried capping the GPU at 300 MHz. It's fine just gaming but gaming and charging is a no no for me. It *used* to work fine, but now it just throttles, even though it is only running at maybe 60 Degrees C. (I set my thermal throttle at 75). It's not really so much of an overheating issue as it is a throttling issue. Throttling on this device is poor and hard to work around.
Click to expand...
Click to collapse
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
this always works for me, no throttling issues

simms22 said:
i give you a few points with the gpu, but the amount saved would be extremely minimal. unless thats all you do, play games all day. then you might see an extra 5%, maybe.
Click to expand...
Click to collapse
My results are specific to certain high-battery-drain games. I am seeing my battery usage HALVED while playing certain games after making this change. These games tend to have a lot of animation. General use or "normal" (not unusually high) battery drain games are likely closer to your 5%.
Likewise, I noticed these games use a lot less battery on my older phones (with lower resolution screens).
If a phone is overheating during "normal" (not high drain) situations, then lowering the resolution may not be effective.

my phone only heats up when it is charging goes up to 45c

simms22 said:
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
this always works for me, no throttling issues
Click to expand...
Click to collapse
Sorry, missed this post.
Will it survive reboot?
Sent from my Nexus 6 using Tapatalk

danarama said:
Sorry, missed this post.
Will it survive reboot?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no. it has to be run every time you boot up.

I9295 becomes very hot and huge battery drain

Hey guys
I already posted my problem in the thread related to LineageOS, but since the issue couldn't be solved I want to try it this way.
So what is my problem?
While using my phone it gets very hot. According to Powerful Monitor the CPU gets up to 65 °C and battery up to 35 °C, while under load. Besides this my battery goes down rapidly. So watching 10 minutes of YouTube sucks up 8-9 % battery. Just a plain normal video.
What is my setup?
I9295, running LineageOS 14.1-2017-06-06-UNOFFICIAL-jactivelte, OpenGApps 06-07-17 nano, only apps installed manually are GeekBench, Powerful Monitor and YouTube. Baseband is I9295XXUDOB4 (German unbranded DBT). I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
What have I already tried?
- flashed stock firmware (all available for Germany that are unbranded). With and without erasing NAND, with different Odin versions. Last time I flashed I used Odin 3.07
- different batteries: the old ones the phone came with (bought it used), the new one I bought separately, a new one from PowerCell with higher capacity (2900 mAh)
- different phones. I have a second I9295 from a friend, that worked definitely without any issues. Same problem.
- different custom ROMs: now I'm running LineageOS, but I also tried CM13 (20161228), CM12.1, MIUI and Super WizCyan (everything from xda)
Is it possible break something ciritcal when disassembling the phone? Both phones came with broken covers for the USB port, so I opened it, but only removed the screws and the mid-frame (?) and replaced the cover. Nothing was damaged, at least I was very carefully and didn't see anything that looked suspicious.
Another very strange thing I noticed:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
I really have no idea what else to do.
Any help is appreciated.

dotnano said:
Hey guys
While using my phone it gets very hot.
I bought a new original Samsung battery and currently using it. So it's basically stock LineageOS.
Any help is appreciated.
Click to expand...
Click to collapse
Hey there. Well, there are tons of possible reasons why your phone acts like that. My modest opinion is that you have some sort of wakelock active in background. Install both Wakelock Detector and Gsam Battery Monitor, grant all the permissions and let it obtain data for some minutes. Than look at the results, and check if there's any Wakelock active. If instead Gsam shows an excessive consume by the kernel, try in terminal the following commands:
Code:
su
setenforce 1
setenforce 0
Then see if there's still the drain (you have to wait some minutes).
If it still doesn't work, I'd advice you to update to the latest stock firmware (doesn't matter which Country, just select a non-branded one), reinstall LOS again and verify if with nothing installed you still get the battery drain.
Anyway, IMHO it's not an hardware related problem, even messing up with the components this shouldn't happen. The only hardware fault could be the battery short-life, but 1st you said you just replaced it, 2nd it would not justify the thermal overload. Let us know

Thank you very much for your answer. I'm quite short on time next days but maybe I have a few minutes on sunday.
On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now. Maybe sunday.
But still thank you

Finally I found some time to try your suggestions
I skipped the part of trying it on the old setup, so I flashed everything new with latest stock(UDOB4-DBT, not the last one but still Android 5.0.1), then TWRP 3.1.0, after that LOS 14.1-20170606 and OpenGApps 7.1 nano from 17-06-06. Only apps I installed beside that are GSam Battery and Wakelock Detector. Root activated and granted where asked and needed.
Here I uploaded the pictures I took from GSam Battery.
So what seems strange to me:
- why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?

dotnano said:
- Why is Phone Radio used at all? I don't have a SIM card inserted...?! It's on a very high level, even if the screen isn't on.
- The battery gets hot quite fast. If it's not in use, everything is fine. But as soon as I use the phone it gets hot.
- As you said: kernel usage seems quite high, tried to install "Terminal Emulator" and executed the commands - no difference.
According wakelock: where do I check that?
Click to expand...
Click to collapse
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.

IvanCristina said:
Sorry for the delay, but if you do not quote/reply me I cannot see the message cause I'm not extremely active on XDA. Anyway...
- Phone Radio is used even without SIM, at least in TouchWiz, dunno in LOS, but it looks like so. The only way to disable it is Airplane Mode.
- It gets hot due to kernel usage, what I still do not understand is why it does so.
- Those commands where the only commands I think could be useful in this case (they set SELinux Permissive/Enforcing)
But if you say you get the Drain on TouchWiz too, the problem is serious and there's a (little?) chanche it would be HW related.
Click to expand...
Click to collapse
No need to apologise, you're doing this in your free time...
Besides that, I wasn't at home all week, so I couldn't try anything even if you had answered.
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?

dotnano said:
Thank you very much for your answer. On the matter latest stock firmware: already tried that on monday, still too much battery drain, but I didn't install LOS till now.
Click to expand...
Click to collapse
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
dotnano said:
So, how do I get the kernel to calm down and stop draining my battery? I mean, I didn't install anything besides clean LOS and GApps. So what could lead to so much kernel usage? Are there any further information that could help you?
Click to expand...
Click to collapse
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About:
dotnano said:
If I use the phone a lot (lets say 30 minutes, so almost 25 % battery!) and after that the phone is not in use for an hour or so, the battery goes up for up to 7-8 %. How it that possible?
Click to expand...
Click to collapse
Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.

IvanCristina said:
I didn't read this post before, the points are two:
- No need to write Thanks, there's a button for it. It's free and very grateful
- If it drains even on stock it's a serious problem.
The situation is very weird. Let's analyze.
1) TW/LOS doesn't matter. Battery drain in both
2) No apps installed which could cause wakelocks
3) Battery SHOULDN'T be the problem
4) The drain is recognised as kernel "usage", though it couldn't be real 'cause of point 1
5) Neither Permissive nor Enforcing SELinux mods helped
At this point it doesn't look so much a SW problem, but more an HW one. About: Well, sometimes the discharge happens so fast the battery doesn't calculate the remaining capacity so well, and after some minutes the real charged cells are more than the "estimated" ones. It would explain the "goes up" of the percentage, but still not the drain.
It's very strange and very rare, but there's an infinitesimal possibility that the thermal paste went to the hell. And in this case there's not that much to do.
That's pretty pessimist though. I'd advice you to format everything, reinstall the latest stock TW and stick with it, and if it still doesn't work, try with some apps like Greenify and ForceDoze (this one works just with 6.0+) in order to at least TRY to reduce the drain.
I'm sorry I cannot help you more, if anyone has some suggestion, please let us know.
Click to expand...
Click to collapse
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.

Youre are not alone. My Phone was/is also getting hot.
Then I did a full wipe ( format also internal memory partition!)
I'm current running cm13 (CM13 (20161228)). Batterie works now / normal ok / 1 / 2 Day s ( no great usage ). But when i telephone with someone it's getting hot in 15 min. Modem Version is I2995XXUDPB3.

dotnano said:
Next strange thing is, I have two S4 Active devices, both have the same problems. Am I just unlucky enough to get two broken phones?
Still, the device I got from I friend was ok the moment he gave it to me. He said battery lasted for only one day, but that would be ok. So it has to be something I did with the phone.
Click to expand...
Click to collapse
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)

JASONRR said:
Have you flashed any custom ROM? Try downloading an entire stock firmware for your country / carrier from sammobile and flash through odin 3.09 and check. The S4 active generally gets hot on usage but should not get very hot. You can also try using powersave mode that limits cpu max freq and prevents heating. Battery on normal usage shoukd last for little under a day to a day with normal usage unless you are using data (otherwise set mobile networks to GSM only which saves battery and reduces heat)
Click to expand...
Click to collapse
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.

dotnano said:
I have flashed the latest DBT (unbranded German) and I have the same problems. Does the version of Odin make a significant difference? I used 3.10.6.
Click to expand...
Click to collapse
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.

JASONRR said:
Normally i have seen issues flashing through odin 3.10 and prefer 3.07 or 3.09. If the firmware flashed correctly and you do not have any issues then it should be fine.
CPU temp of 65% without powersave mode is fine and watching youtube videos does consume battery. Try a different charger / cable combination as that too can have issues. If the battery gets charged quickly (on stock kernel under 2 - 2.5 hours from 0 to 100) then there is definitely an issue with the charger and it will drain quickly too.
Click to expand...
Click to collapse
I tried 3.10, 3.12 and 3.07 so far. Not successfully. Tried 3.09 now, we'll see.
I have a Sony Xperia Z1C as comparison, YouTube needs maybe 1% for 5 Minutes.
Cables/Chargers shouldn't be the problem. I have the original Samsung, also cable. Charged to 0 to 75 % in 90 Minutes. Same with cable and charger from Anker. So should be fine?

So no new ideas?

dotnano said:
So no new ideas?
Click to expand...
Click to collapse
I have no idea too but i have the same Trouble with mine BUT I'm still using the original Rom and didn't flash it. So maybe it is an Hardware issue.
My Battery is getting old, yes, but it is the third one. The Phone gets hotter than in its first years.
I hope you'll find a reason!

My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.

Vardion said:
My i9295 always has been like this: 1 minute on-screen time = 1% battery loss. So this basically is a 2 hour phone... Stock or custom rom didn't matter. A friends i9505 used a lot less power, therefore I assume that the LCD (instead of the S4's AMOLED) is the problem.
Click to expand...
Click to collapse
Nah, why should it? There are a lot of i9295 users that don't have any problems.