How to figure out what is causing heat and battery usage (CPU and Battery usage) - General Questions and Answers

Hello. I have the GS5. For over three months it overheats like hell. Why because I did the firmware update and it all started with this.
TL;DR: I need an app or program that shows detailed percentage of usage and temperatures of apps. It would be great if you can find a real-time monitoring one like on PCs. My phone is rooted so feel free to recommend any app that suit my needs.
It overheats so much that I can barely able to hold the phone because it slips through so easily from my hand (nope my hands are not dirty, I wash them with lots of soaps ).
I bought a case and it is still somewhat hard to hold the phone with one hand but the case surely helped. Can use it with two hands but was able to use with one hand without any problems so why should I accept this right?
The cpu is around 40 Celsius at idle to very low usage. The battery is around 28 Celsius at idle. The room temps is 26 Celsius.
After using my phone for about fifteen mins, the battery is going up to 36-38 Celsius. The cpu is around 50 Celsius. Not playing games at all, just surfing on the web and installing one to two apps from Android Market. Do you think it is normal or excessive? I fell the heat in my hands. It was not been like this before the firmware update.
Although I did all wipes and flash the whole rom from scratch (even ticked Nand Erase All), my problem still persists so I am out of ideas. Maybe I can buy a new battery and a charger but I would like to make sure that the problem is not causing by software. Thank you.

karasahin said:
Hello. I have the GS5. For over three months it overheats like hell. Why because I did the firmware update and it all started with this.
TL;DR: I need an app or program that shows detailed percentage of usage and temperatures of apps. It would be great if you can find a real-time monitoring one like on PCs. My phone is rooted so feel free to recommend any app that suit my needs.
It overheats so much that I can barely able to hold the phone because it slips through so easily from my hand (nope my hands are not dirty, I wash them with lots of soaps ).
I bought a case and it is still somewhat hard to hold the phone with one hand but the case surely helped. Can use it with two hands but was able to use with one hand without any problems so why should I accept this right?
The cpu is around 40 Celsius at idle to very low usage. The battery is around 28 Celsius at idle. The room temps is 26 Celsius.
After using my phone for about fifteen mins, the battery is going up to 36-38 Celsius. The cpu is around 50 Celsius. Not playing games at all, just surfing on the web and installing one to two apps from Android Market. Do you think it is normal or excessive? I fell the heat in my hands. It was not been like this before the firmware update.
Although I did all wipes and flash the whole rom from scratch (even ticked Nand Erase All), my problem still persists so I am out of ideas. Maybe I can buy a new battery and a charger but I would like to make sure that the problem is not causing by software. Thank you.
Click to expand...
Click to collapse
Please provide further information in regard to your device e.g. ROM, kernel etc.

noc.jfcbs said:
Please provide further information in regard to your device e.g. ROM, kernel etc.
Click to expand...
Click to collapse
Sure. I haven't touched to kernel yet but I have a custom rom installed. I just installed it yesterday. Was using stock rom of Lollipop 5.0 of my country before. I also tried the UK rom (BTU) but all the same.

karasahin said:
Sure. I haven't touched to kernel yet but I have a custom rom installed. I just installed it yesterday. Was using stock rom of Lollipop 5.0 of my country before. I also tried the UK rom (BTU) but all the same.
Click to expand...
Click to collapse
Despite only little information available, I assume the issue is kernel related. Had you e.g. overclocked and over-voltaged? Most likely not as you were on stock.
Your custom ROM certainly came with its own, new kernel. I suggest to monitor the overheating first as you just recently flashed the custom ROM. However, you can also play with the kernel settings (my current one has its own control-apk, or by using e.g. an apk called "Kernel Adiutor") to see what's best serves your requirements. If you're not happy with the custom ROM's kernel, you can flash a custom kernel but check compatibility first. And remember, when you're on a custom kernel every time you flash the custom ROM you'll have to re-flash the kernel.
Here's a real good guide regarding CPU governors, I/O schedulers and more:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957

noc.jfcbs said:
Despite only little information available, I assume the issue is kernel related. Had you e.g. overclocked and over-voltaged? Most likely not as you were on stock.
Your custom ROM certainly came with its own, new kernel. I suggest to monitor the overheating first as you just recently flashed the custom ROM. However, you can also play with the kernel settings (my current one has its own control-apk, or by using e.g. an apk called "Kernel Adiutor") to see what's best serves your requirements. If you're not happy with the custom ROM's kernel, you can flash a custom kernel but check compatibility first. And remember, when you're on a custom kernel every time you flash the custom ROM you'll have to re-flash the kernel.
Here's a real good guide regarding CPU governors, I/O schedulers and more:
http://forum.xda-developers.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
Click to expand...
Click to collapse
So I think I should update kernel on this custom rom with a new one? Because the OP says that flash hispasian kernel after flashing his rom. I haven't do that yet, nor I have experience about it. I believe I have a custom rom with stock kernel right now. I don't think it is related to custom rom. It overheats like I was on stock rom. Could be kernel. Can kernel be updated through the firmware update? It may explain why it starts to overheating after that. No, I haven't overclocked and over-voltaged the cpu. Maybe it came overclocked or over-voltaged with this custom rom but it isn't described.

karasahin said:
So I think I should update kernel on this custom rom with a new one? Because the OP says that flash hispasian kernel after flashing his rom. I haven't do that yet, nor I have experience about it. I believe I have a custom rom with stock kernel right now. I don't think it is related to custom rom. It overheats like I was on stock rom. Could be kernel. Can kernel be updated through the firmware update? It may explain why it starts to overheating after that. No, I haven't overclocked and over-voltaged the cpu. Maybe it came overclocked or over-voltaged with this custom rom but it isn't described.
Click to expand...
Click to collapse
I suggest to surf your custom ROM's thread and to figure out, which kernels can go with this ROM and which are the experiences of other users with the respective kernel.
Firmware updates (I assume you mean now updates of your ROM) won't solve your problem because with the update comes its own kernel i.e. you need to flash afterwards the kernel you want again.
I always flash my custom kernel through recovery. As recovery, I personally recommend TWRP in its latest version (as you see in my signature block, I'm using TWRP v3.0.2). An in my opinion very good tool, to install (actually flash through your current recovery) TWRP is via an App (apk) called "Flashify".
After you've flash TWRP and rebooted, google how to flash a kernel or search XDA for my postings. I think I already describe somewhere how to do so.

noc.jfcbs said:
I suggest to surf your custom ROM's thread and to figure out, which kernels can go with this ROM and which are the experiences of other users with the respective kernel.
Firmware updates (I assume you mean now updates of your ROM) won't solve your problem because with the update comes its own kernel i.e. you need to flash afterwards the kernel you want again.
I always flash my custom kernel through recovery. As recovery, I personally recommend TWRP in its latest version (as you see in my signature block, I'm using TWRP v3.0.2). An in my opinion very good tool, to install (actually flash through your current recovery) TWRP is via an App (apk) called "Flashify".
After you've flash TWRP and rebooted, google how to flash a kernel or search XDA for my postings. I think I already describe somewhere how to do so.
Click to expand...
Click to collapse
I mentioned firmware updates because I was wondering if stock (Samsung) rom firmware update did break something in stock kernel. Is it possible? I'm %99 positive this happened after the latest firmware update. I mainly flashed this custom rom to get rid of overheating problem but the problem persists.
I just flashed HispAsian kernel, which the creator of this custom ROM recommended, through TWRP and works fine for now. But nothing's changed about overheating.

karasahin said:
I mentioned firmware updates because I was wondering if stock (Samsung) rom firmware update did break something in stock kernel. Is it possible? I'm %99 positive this happened after the latest firmware update. I mainly flashed this custom rom to get rid of overheating problem but the problem persists.
I just flashed HispAsian kernel, which the creator of this custom ROM recommended, through TWRP and works fine for now. But nothing's changed about overheating.
Click to expand...
Click to collapse
Look into the kernel settings as mentioned in post #4 (http://forum.xda-developers.com/showpost.php?p=67135599&postcount=4).
Before you change anything I suggest to educate yourself via the thread mentioned in that post, too.

noc.jfcbs said:
Look into the kernel settings as mentioned in post #4 (http://forum.xda-developers.com/showpost.php?p=67135599&postcount=4).
Before you change anything I suggest to educate yourself via the thread mentioned in that post, too.
Click to expand...
Click to collapse
I actually don't care about custom roms. As long as I can find a solution for stock roms I would return to them. Could you please give me your solution for stock roms?

karasahin said:
I actually don't care about custom roms. As long as I can find a solution for stock roms I would return to them. Could you please give me your solution for stock roms?
Click to expand...
Click to collapse
It's always your decision and desire. I think everything said also applies to stock ROM. Check your kernel settings and manipulate to your needs. Some tools were mentioned before.

noc.jfcbs said:
It's always your decision and desire. I think everything said also applies to stock ROM. Check your kernel settings and manipulate to your needs. Some tools were mentioned before.
Click to expand...
Click to collapse
It is too complicated for me. If you could just point how to downlock the CPU's clock speed then I can try and see if it works to prevent overheating.
Also let's say I decide to return to stock rom. Will current kernel replace with stock one?

karasahin said:
It is too complicated for me. If you could just point how to downlock the CPU's clock speed then I can try and see if it works to prevent overheating.
Also let's say I decide to return to stock rom. Will current kernel replace with stock one?
Click to expand...
Click to collapse
I'm not familiar with your phone (wasn't it a Samsung Galaxy S5) or your stock ROM (Lollipop?). I suggest that you address your questions in the GSG5 forum, where the gurus for your phone rest. Sorry for that.
Anyhow, I added two screenshots of the apk "Kernel Adiutor" (first two), and two of AGNi control, which came with my kernel. As you see both of them support manipulation of kernel settings.
IRT your last question: I'm convinced flashing stock ROM is also replacing current kernel. ...but as said: GSG5 forum.

Related

Issues with installing certain ROMS [SUCCESS!!!]

Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.
[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.
Doh! He said rectify lol
Sent from my Xoom using XDA Premium App

[Q] Diagnosing Random Crashes/Freezes

Hello android gurus/deities (too much?),
Just got my first smartphone, a Droid Charge. Great phone, especially for the price. The screen is freaking fantastic and of course Android is amazing as ever.
However, since first activating it, I seem to get random crashes. I can't replicate the problem, since it doesn't seem connected to anything visual. First time it happened when I decided to check out the camera, took a picture, and tried to view it. Other times have been the first time trying out netflix, first time sending a text. Seems to happen the first time I use some apps.
The crash basically consists of a short 5-10 second freeze followed by a reboot. Any ideas? Is this a hardware issue I need to have addressed or more likely a software issue that I just need to wait for updates to come along and fix it? Or is this a common occurence with Android and I just need to suck it up? lol
Edit: Has also happened 3 or 4 times while browsing the web, including this site...
charges hardware are pretty great for the price the software is a big issue for the charge whitch is why most of us myself included suggest rooting your device whitch literally a dummy could do using odin... i am running a stock based of a leak called infinity rom pretty amazing for a stockish rom for now so reboots are known at least for me but i really think the majority of the problem for this phone is the software gps loss signal going in and out as in data (this is a hit and miss) ..... hope this helped you iron things out...
Out of curiosity, what will rooting my device accomplish with respect to the reboots? Anything?
I rooted the device, then tried infinityROM but ran into so many problems I flashed back to the factory rom X(... Rooted again, but still get reboots, any ideas?
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
RevTorA said:
Where can I get a more solid kernel? From reading around it sounds like that "might" solve the reboots :\
Click to expand...
Click to collapse
http://rootzwiki.com/topic/4847-guide-new-users-guide-everything-how-to-root-rom-kernels-radios-cwm/
Also depends what rom you are running.
If it keeps happening after you root and flash a new kernel (and maybe install a rom) upload a logcat to a filesharing place and hop on IRC to ask for help.
irc.andirc.net
#charge
Port 6666
Sent from my SCH-I510 using xda premium
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
RevTorA said:
Thanks... once that site's back up I'll download a the kernel from there... The kernel on that page should work my Charge if it's currently the factory rom right?
Edit: Just to check, Imoseyon's kernel (listed here is the only available kernel aside from the factory kernel? I should try flashing this to see if it fixes my problem? Where can I get the factory kernel (just the kernel :\) if things go awry?
Edit2: Also found imnut's PBJT kernel here. I'm unaware of some of the terminologies (I've only messed with a couple Ubuntu/Fedora distros of linux), can this and any other kernel for the Charge work with Gingerbread (2.3.6)?
Click to expand...
Click to collapse
PBJ is a Froyo kernel. It will only work with Froyo.

How to Overclock device?

i have unlocked my boot loader i have rooted and i have s-off!
the attached images give my complete firmware info:
i have noticed that my phone feels very stable but somewhat less on performance and battery life.
besides there are strange things i have observed (which happened even before rooting)
a) that my battery takes a lot of time to recharge!
b) at times it wont make it up to 100% will be stuck at 99%
c) and if i power off my device and start it up it just drastically reduces by 10% or so
also my phone doesn't heat up it much 34 C is the temp i see in those battery monitoring apps and the battery drop is stable when the phone is not used. And power saver doesn't make much difference!
so i wanted to flash a kernel..
ttherefore i wanted to ask which kernel will work with my present firmware?
and
how to flash a kernel?
any guide about kernels which will help me get through can also work!:good:
PS m a complete noob but trying to learn things so some detailed help regarding the procedure will be appreciated!:angel:
Sonone said:
a) that my battery takes a lot of time to recharge!
Click to expand...
Click to collapse
What is a "long time"? Can you be more specific? Mine usually charges for near empty to full in maybe 1.5 to 2 hours.
Rooting and S-off won't effect charge time or battery life. Going to Sense 5 might has some effect on battery life (I personally haven't seen a significant change), but would not have any effect on charge time, per se. But if there is fast battery drain, then the phone will take longer to charge, if you are charging with the phone on (as many of us do).
Are you on the 2.15 firmware? You might be having a signal issue affecting battery drain.
Sonone said:
b) at times it wont make it up to 100% will be stuck at 99%
Click to expand...
Click to collapse
How many times did you charge the phone after updating to Sense 5? It takes at least one full discharge/charge cycle after updating the ROM, for the battery meter to be accurate.
Also, charging will automatically shutoff once the battery is charged (this is a mandatory safety feature). Then once the charge has dropped a bit, it will top off again. So I've often seen it drop to 99% while on the charger.
Sonone said:
c) and if i power off my device and start it up it just drastically reduces by 10% or so
Click to expand...
Click to collapse
Probably just a metering error, and the new reading is the correct one. I've seen this happen to myself and others when rebooting the phone. Although, it shouldn't be common. Although might be, if you haven't calibrated the meter properly as I mentioned above.
Sonone said:
ttherefore i wanted to ask which kernel will work with my present firmware?
and
how to flash a kernel?
Click to expand...
Click to collapse
I beleive Beastmode is your only choice for Sense 5 ROMs at the present time: http://forum.xda-developers.com/showthread.php?t=2165880
Just download to your phone, and flash in recovery. Wipe cache and Dalvik after flashing, then reboot.
redpoint73 said:
What is a "long time"? Can you be more specific?
Rooting and S-off won't effect charge time or battery life. Going to Sense 5 might has some effect on battery life (I haven't seen a significant change), but would not have any effect on charge time. I haven't seen any change in charge time across many ROM flashes. It charges from almost empty to full, in about 1.5 hours, or maybe 2 hours.
How many times did you charge the phone after updating to Sense 5? It takes at least one full discharge/charge cycle after updating the ROM, for the battery meter to be accurate.
Also, charging will intentionally shutoff once the battery is charged (this is a mandatory safety feature). Then once the charge has dropped a bit, it will top off again. So I've often seen it drop to 99% while on the charger.
Probably just a metering error, and the new reading is the correct one. I've seen this happen to myself and others when rebooting the phone. Although, it shouldn't be common. Although might be, if you haven't calibrated the meter properly as I mentioned above.
I beleive Beastmode is your only choice for Sense 5 ROMs at the present time: http://forum.xda-developers.com/showthread.php?t=2165880
Just download to your phone, and flash in recovery. Wipe cache and Dalvik after flashing, then reboot.
Click to expand...
Click to collapse
Thanks a lot for your reply.:good:
it takes 2 hours to charge.. slightly more...
i have read people saying getting a 2 0r 3% battery drop in 5 hours or so.. for me its around 6% an hour..
i dont play games...i have removed unecessary apps some bloatware.. i dont use greenify module or set cpu etc.. besides my usage is normal.. and "auto sync" and blink feed is off.. its only whats app messenger but even thats not on auto sync
i use 3g for data plans... thats pretty much about my usage.
about the kernel you recommended is it compatible with my present scenario (ie firmware and 4.2.2 etc)
and it wont affect anything like the "sim(carrier unlock), bootloader,radio etc" [m sorry as i said m a newbie] ?
and which version of beastmode exactly u will recommend?
Sonone said:
Thanks a lot for your reply.:good:
it takes 2 hours to charge.. slightly more...
Click to expand...
Click to collapse
That sounds pretty normal. I assume the phone is on when you are charging, so if you are seeing higher battery drain on Sense 5, then this will of course affect charge time (1 step backward for every 2 steps forward, so to speak).
So if you are seeing slower charging on Sense 5 than before, it might not be charging time per se, but a battery drain issue.
Sonone said:
i have read people saying getting a 2 0r 3% battery drop in 5 hours or so.. for me its around 6% an hour..
Click to expand...
Click to collapse
2-3% per 5 hours seems extremely low. I can get 48 hours on a charge with low usage (phone mostly with the phone idle), on WiFi at home and LTE at work. So about 2% per hour. And I haven't heard reports of battery life much better than that, unless you turn the phone to airplane more or otherwise turn off the data network, which of course will greatly extend battery life but makes the phone much less useful.
And many people have battery life much worse than I've just stated (2% per hour while idle). It depends a lot on how you use your phone, and your location/reception. Drain of 6% per hour with the phone idle is not unheard of, probably even pretty common. When you say 6% per hour, is that with the phone idle and screen off? Is this much different than before you were on Sense 5?
One important question: How did you get on Sense 5? Was it by OTA, or did you flash a custom or stock rooted ROM from Development?
If you flashed a ROM, did you install the 2.15 firmware? This is not to be confused with the OS or ROM, but the 2.15 firmware contains the Sense 5 hboot, radio, as well as several other modules.
If you are not already on the 2.15 firmware, this may help. Of course, a different kernel may help also.
Sonone said:
about the kernel you recommended is it compatible with my present scenario (ie firmware and 4.2.2 etc)
and it wont affect anything like the "sim(carrier unlock), bootloader,radio etc" [m sorry as i said m a newbie] ?
and which version of beastmode exactly u will recommend?
Click to expand...
Click to collapse
Of course it works on your present setup. I already said its the kernel to use for Sense 5, and I wouldn't be recommended it to you if it didn't work on your setup.
Some folks are saying to flash Beastmode version 2.0, reboot, than flash 3.5. But I assume that many folks do just fine flashing the latest 3.5 version.
Flashing a kernel will not touch the radio or bootloader. Also, SIM unlock survives just about anything.
redpoint73 said:
One important question: How did you get on Sense 5? Was it by OTA, or did you flash a custom or stock rooted ROM from Development?
If you flashed a ROM, did you install the 2.15 firmware? This is not to be confused with the OS or ROM, but the 2.15 firmware contains the Sense 5 hboot, radio, as well as several other modules.
If you are not already on the 2.15 firmware, this may help. Of course, a different kernel may help also.
Click to expand...
Click to collapse
Well thats the mystery part. I had purchased this phone from ebay from a local vendor. I live in India as HTC one XL is not available all over the world this phone was 'sim/carrier unlocked' to work with the gsm service providers in India( a known fact) Interestingly when i checked it already came with Sense 5 and 4.2.2 and guess what also with the "SOFF" and "Unlocked Bootloader" as well as Super Cid (11111111) the rom however was not rooted it dint have any custom recovery flashed everything else was stock. Every HTC app worked.
so with this background i obviously thought that it may have some ported rom of sense 5 or a custom rom like 'magio' not 'clean rom 7' since it had some htc bloatware (not carrier bloatware) BUT then it dint have any trace of the developer or a signature or anything that could help me to actually understand which rom I am running!
it has hboot version 2.15.0000 and radio i1.30a.32.45.18
now its not a assembled or a fake version i used many apps like Setc cpu ,An tutu,Trickster Mod(every htc sync manager recognizes it) and it gives the detailed version of hardware which is the one that htc one Xl has so its definitely genuine and legit besides it has an 'imei number.
So that's what i m confused about!! I believe its from Asia hong kong or some where probably! Buts its definitely geniune
redpoint73 said:
Of course it works on your present setup. I already said its the kernel to use for Sense 5, and I wouldn't be recommended it to you if it didn't work on your setup.
Some folks are saying to flash Beastmode version 2.0, reboot, than flash 3.5. But I assume that many folks do just fine flashing the latest 3.5 version.
Flashing a kernel will not touch the radio or bootloader. Also, SIM unlock survives just about anything.
Click to expand...
Click to collapse
I read the thread much of it.. I guess the 3.5 version is jus the 3.0 version with Aroma,surprisingly when i flash try to flash it with TWRP 2.6 it says "FAIL"
besides the developer also mentioned to rename two files in the bin folder with" _old" as an extension does it need to be done with the latest kernel version?
and m a bit scared to do so because many have reported that the file for WiFi fix is missing!
About the battery thanks a ton for the explanation M really happy its normal.. and many apps do say that the health is good so YAY!! =)
now the only reason for flashing a kernel will be to get the extra juice out of my Snapdragon S4!!
*excited*
Sonone said:
Well thats the mystery part. I had purchased this phone from ebay from a local vendor. I live in India as HTC one XL is not available all over the world this phone was 'sim/carrier unlocked' to work with the gsm service providers in India( a known fact) Interestingly when i checked it already came with Sense 5 and 4.2.2 and guess what also with the "SOFF" and "Unlocked Bootloader" as well as Super Cid (11111111) the rom however was not rooted it dint have any custom recovery flashed everything else was stock. Every HTC app worked.
so with this background i obviously thought that it may have some ported rom of sense 5 or a custom rom like 'magio' not 'clean rom 7' since it had some htc bloatware (not carrier bloatware) BUT then it dint have any trace of the developer or a signature or anything that could help me to actually understand which rom I am running!
it has hboot version 2.15.0000 and radio i1.30a.32.45.18
now its not a assembled or a fake version i used many apps like Setc cpu ,An tutu,Trickster Mod(every htc sync manager recognizes it) and it gives the detailed version of hardware which is the one that htc one Xl has so its definitely genuine and legit besides it has an 'imei number.
So that's what i m confused about!! I believe its from Asia hong kong or some where probably! Buts its definitely geniune
I read the thread much of it.. I guess the 3.5 version is jus the 3.0 version with Aroma,surprisingly when i flash try to flash it with TWRP 2.6 it says "FAIL"
besides the developer also mentioned to rename two files in the bin folder with" _old" as an extension does it need to be done with the latest kernel version?
and m a bit scared to do so because many have reported that the file for WiFi fix is missing!
About the battery thanks a ton for the explanation M really happy its normal.. and many apps do say that the health is good so YAY!! =)
now the only reason for flashing a kernel will be to get the extra juice out of my Snapdragon S4!!
*excited*
Click to expand...
Click to collapse
How long ago did you purchase the phone? It seems to me that the seller has just loaded a stock ROM on it before selling it. You're lucky though, you've ended up with a phone that's already unlocked and already s-off, win win.
I may be wrong but I think the renaming of those files was only applicable to an older version of the kernel. I've flashed 3.0 (3.5 is exactly the same kernel but with an updated/different aroma installer) without renaming them a few times and have no issues. I saw someone mention that after the kernel install failed, that fixing permissions in recovery/advanced and then flashing the kernel worked.
Sent from my Evita
timmaaa said:
How long ago did you purchase the phone? It seems to me that the seller has just loaded a stock ROM on it before selling it. You're lucky though, you've ended up with a phone that's already unlocked and already s-off, win win.
Click to expand...
Click to collapse
its just been 4 or 5 days or so.. M sorry if m desperately over enthusiastic but as i said m a total noob and m jus learning!
Thats great my phone is unlocked and good to go!
btw htc is different god knows why they use lithium polymer batteries and that too do which have a relatively less capacity..
and one brief update m using "ondemand" as my governor i hope thats fine!?
timmaaa said:
I may be wrong but I think the renaming of those files was only applicable to an older version of the kernel. I've flashed 3.0 (3.5 is exactly the same kernel but with an updated/different aroma installer) without renaming them a few times and have no issues. I saw someone mention that after the kernel install failed, that fixing permissions in recovery/advanced and then flashing the kernel worked.
Sent from my Evita
Click to expand...
Click to collapse
So u suggest i should try and flash the 2.0 and then the 3.5? i will try that!
and friends btw just realized that my phone actually beats up the international version in Antutu Benchmarks its so close to Nexus 4 atleast on the graph (sorry for the off topic discussion its just that m very happy)
and as always god knows what i would have done without this forum and the explanations i get from you people!:angel:
Sonone said:
its just been 4 or 5 days or so.. M sorry if m desperately over enthusiastic but as i said m a total noob and m jus learning!
Thats great my phone is unlocked and good to go!
btw htc is different god knows why they use lithium polymer batteries and that too do which have a relatively less capacity..
and one brief update m using "ondemand" as my governor i hope thats fine!?
So u suggest i should try and flash the 2.0 and then the 3.5? i will try that!
and friends btw just realized that my phone actually beats up the international version in Antutu Benchmarks its so close to Nexus 4 atleast on the graph (sorry for the off topic discussion its just that m very happy)
and as always god knows what i would have done without this forum and the explanations i get from you people!:angel:
Click to expand...
Click to collapse
There's nothing wrong with being enthusiastic, and I always encourage people who actually want to learn how to modify their device. The ondemand governor should be fine, I've always used that or intellidemand (on the kernels that have it).
You can try flashing 2.0 before 3.5 or you can just try fixing permissions in recovery before just flashing 3.5, apparently either way works. I've never been a huge fan of benchmarks, but Zarboz asked me to do a couple while we were testing the Beastmode kernel, and apparently the result was half decent. I'll attach a screenshot in a minute.
Sent from my Evita
timmaaa said:
There's nothing wrong with being enthusiastic, and I always encourage people who actually want to learn how to modify their device. The ondemand governor should be fine, I've always used that or intellidemand (on the kernels that have it).
You can try flashing 2.0 before 3.5 or you can just try fixing permissions in recovery before just flashing 3.5, apparently either way works. I've never been a huge fan of benchmarks, but Zarboz asked me to do a couple while we were testing the Beastmode kernel, and apparently the result was half decent. I'll attach a screenshot in a minute.
Sent from my Evita
Click to expand...
Click to collapse
was the benchmarking app quadrant?
well it does seem good though like personally m a bit skeptical about benchmarks as they give a different result every time BUT what matters to me is the feedback the kernel has which is really great. And since it gives me a little more control of the functioning of my device m very much inclined to try it out!!
Sonone said:
so with this background i obviously thought that it may have some ported rom of sense 5 or a custom rom like 'magio' not 'clean rom 7' since it had some htc bloatware (not carrier bloatware) BUT then it dint have any trace of the developer or a signature or anything that could help me to actually understand which rom I am running!
it has hboot version 2.15.0000 and radio i1.30a.32.45.18
Click to expand...
Click to collapse
It has the version number (5.05.707.1) and baseband for the Singapore/Singtel Sense 5 OTA. So I'm going to guess that the seller actually RUU'ed to stock and than OTA'ed to the latest official OS, which is actually pretty impressive (went a bit beyond the call of duty, as a seller).
If this is true, all the 2.15 firmware modules should be installed, and you shouldn't need to mess with those.
redpoint73 said:
It has the version number (5.05.707.1) and baseband for the Singapore/Singtel Sense 5 OTA. So I'm going to guess that the seller actually RUU'ed to stock and than OTA'ed to the latest official OS, which is actually pretty impressive (went a bit beyond the call of duty, as a seller).
If this is true, all the 2.15 firmware modules should be installed, and you shouldn't need to mess with those.
Click to expand...
Click to collapse
and finally mystery solved :good::laugh: Genius :good:
but I dint get you? So u mean to say that everything is normal and i can go ahead withe flashing?
and its all good i mean the phone,all legit right?
one thing that i have often thought is that are the custom roms build to work specifically for a particular region or is it universal??
Sonone said:
and finally mystery solved :good::laugh: Genius :good:
but I dint get you? So u mean to say that everything is normal and i can go ahead withe flashing?
and its all good i mean the phone,all legit right?
one thing that i have often thought is that are the custom roms build to work specifically for a particular region or is it universal??
Click to expand...
Click to collapse
Well, its not a sure thing (my assumption on how the phone go to Sense 5). But its the likely scenario.
I'd say all is legit. I wouldn't expect there to be any signal issues due to mismatched firmware modules, as it appears that hboot, radio, and other modules are updated to 2.15 versions meant for the Sense 5 stock ROM.
Although, a few folks have reported poor reception on the Sense 5 radio (baseband), and getting better reception by flashing an older radio. But I think most people are going to see better performance with the newest (Sense 5) radio. Unless you have a reason to believe that reception is an issue, I'd leave it alone.
Any ROM meant for the EVITA will work on your phone (they are not region dependent). The one hitch, if the APN for your carrier is not included on the custom ROM, you will have to enter the APN info manually. But this is a minor issue. And if you already have the phone running on the stock Sense 5 ROM, it looks like you've already figured this out (or it was done for you).
There is also presently an exception, in that some AOSP ROMs do not play well with hboot 2.15. But each AOSP ROM will likely be compatible as the individual developers update their ROMs.
A thread about overclocking that lead to so many things! =)
redpoint73 said:
Well, its not a sure thing (my assumption on how the phone go to Sense 5). But its the likely scenario.
I'd say all is legit. I wouldn't expect there to be any signal issues due to mismatched firmware modules, as it appears that hboot, radio, and other modules are updated to 2.15 versions meant for the Sense 5 stock ROM.
Although, a few folks have reported poor reception on the Sense 5 radio (baseband), and getting better reception by flashing an older radio. But I think most people are going to see better performance with the newest (Sense 5) radio. Unless you have a reason to believe that reception is an issue, I'd leave it alone.
Any ROM meant for the EVITA will work on your phone (they are not region dependent). The one hitch, if the APN for your carrier is not included on the custom ROM, you will have to enter the APN info manually. But this is a minor issue. And if you already have the phone running on the stock Sense 5 ROM, it looks like you've already figured this out (or it was done for you).
There is also presently an exception, in that some AOSP ROMs do not play well with hboot 2.15. But each AOSP ROM will likely be compatible as the individual developers update their ROMs.
Click to expand...
Click to collapse
M happy its all good!
Ya Timmaaa had also mentioned that PAC man in particular is not compatible with 2.15... Access Points ya i can do that..
Reception has been good.... it was the same i had on my earlier cell!
i have to thanks the seller though.. Nice job done..
btw does the clean rom or magio for that matter have any at&t or telstra stuff!?
for clean rom its mentioned i guess anyways i can remove that,coz its actually of no use?
MagioRom has no carrier bloatware at all, it's been removed. I haven't run the new Cleanrom but I think Scott usually removes the bloatware too.
Sent from my Evita
timmaaa said:
MagioRom has no carrier bloatware at all, it's been removed. I haven't run the new Cleanrom but I think Scott usually removes the bloatware too.
Sent from my Evita
Click to expand...
Click to collapse
so no extra bars for network and dat at & t start up screen?
and completely debranded?
thanks for the feedback =)
Sonone said:
so no extra bars for network and dat at & t start up screen?
and completely debranded?
thanks for the feedback =)
Click to expand...
Click to collapse
I'm honestly not sure because I haven't flashed Cleanrom, he should have a list of features in his thread though.
Sent from my Evita
i installed Beastmode version 3.5 my phone is stuck on the start up screen with some something written in red "that its meant for development etc.... what to do?
Download Beastmode 2.0, flash that and then 3.5 afterwards and see if that works.
Sent from my Evita
Sonone said:
so no extra bars for network and dat at & t start up screen?
and completely debranded?
Click to expand...
Click to collapse
CleanROM 7 is actually based on the German T-Mobile stock ROM, but as scrocler says in the top post of the CleanROM thread "infused with AT&T settings!" Probably due to the fact that some 60% of One X/XL users here are on AT&T (based on a survey by Turge), and some things don't always play quite well on AT&T's network without AT&T build.prop, signal icons etc. Although, the stock German ROM is working fantastic for me on AT&T.
I haven't flashed the latest CleanROM either, so I'm not actually sure what AT&T aspects are present or not. You can read through the CleanROM thread, or post the question there. Or just flash it, and see for yourself.
I think scrosler is working on an AROMA version of CleanROM 7, in which case you may be able to customize what AT&T features are included or not.
when trying to install beast mode kernel i was stuck in bootloop so i went into twrp and by mistake wiped everything (i was such a fool my sddata along with my nandroid back up) got erased so i had no os..
when i rebooted it was again in bootloop
so i first flashed twrp
then i mounted usb storage and copied cyanogen mod {cm-10.0.0-evita} and flashed it!
{the version i downloaded was the only tsbale version}
it booted up and now my touch screen nor the capacitive buttons work please tell me what to do??
rilly messed up!

custom rom and kernals, should one install them?

I recently ordered the OPO and I was wondering if there was any point to installing a rom and a kernal.
Are there any important/good/large beneficial features and stuff to installing them?
Is it recommended to install one?
I'm just trying to decide whether or not to install rom/kernal before I get the phone so when I get it, I can work on it right away.
dlwhdrlf said:
I recently ordered the OPO and I was wondering if there was any point to installing a rom and a kernal.
Are there any important/good/large beneficial features and stuff to installing them?
Is it recommended to install one?
I'm just trying to decide whether or not to install rom/kernal before I get the phone so when I get it, I can work on it right away.
Click to expand...
Click to collapse
The phone works great out of the box, although it has some bugs.
So you install custom ROMs and/or kernels if you want to get the bugs fixed (e.g. the battery drain), you have a ROM you like for other devices you had (e.g. Paranoid), or you just like the idea of flashing something every couple of weeks, when the ROM is updated...
Dzhedaj said:
The phone works great out of the box, although it has some bugs.
So you install custom ROMs and/or kernels if you want to get the bugs fixed (e.g. the battery drain), you have a ROM you like for other devices you had (e.g. Paranoid), or you just like the idea of flashing something every couple of weeks, when the ROM is updated...
Click to expand...
Click to collapse
I have to disagree with your first statement. I've had no bugs or battery drain with stock CM11s except for 30O which is now obsolete. Custom ROMs are for different feature sets and those who like to tinker
dlwhdrlf said:
I recently ordered the OPO and I was wondering if there was any point to installing a rom and a kernal.
Are there any important/good/large beneficial features and stuff to installing them?
Is it recommended to install one?
I'm just trying to decide whether or not to install rom/kernal before I get the phone so when I get it, I can work on it right away.
Click to expand...
Click to collapse
Nobody can answer this question for you. There are points to installing custom ROMs and kernels, and each user has their own reasons for doing so. Only you can decide whether CM11S is a good fit for you, if not then try custom ROMs. It all depends on what you want to get out of your phone.
Transmitted via Bacon

My S7 BSOD'd, should I install a custom ROM?

My S7's firmware kicked the bucket yesterday and had the black screen of death. Currently out the house so I had no way to recover anything and ended up factory resetting via the recovery menu.
I was planning to root before all this happened but I was waiting for Samsung Pay in UK since I wanted to try it out, but I don't really want my device locking up again and having to reset it again.
I'm thinking of installing a custom ROM since it would prevent the issue from occuring again but I'm wondering if theres anything I should know before I do, since I've seen people say that the stock Samsung camera app is the best and that any stock custom ROM camera makes the quality bad. Is there anything else I should know?
Just install a different stock based ROM, BSODs are caused by a myriad of reasons ranging from Kernel instability to a system modification gone wrong.
Just make sure to stick with a stock-friendly kernel or the stock based kernel to avoid BSODs
Revontheus said:
Just install a different stock based ROM, BSODs are caused by a myriad of reasons ranging from Kernel instability to a system modification gone wrong.
Just make sure to stick with a stock-friendly kernel or the stock based kernel to avoid BSODs
Click to expand...
Click to collapse
Alright, thanks!
I'll probably install superstock ROM or some other de-bloated stock ROM then.
Superstock ROM + Superstock Kernel make for a killer combo, go for it
Revontheus said:
Superstock ROM + Superstock Kernel make for a killer combo, go for it
Click to expand...
Click to collapse
Sounds good! I'll install it tomorrow when I get back home
Would rather not lose my data than have access to Samsung Pay, so it's all good.

Categories

Resources