Related
Welcome to YABD – Yet Another Battery Drain thread
or Everything you wanted to know about Battery Drain but was too afraid to ask about
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Corrupt media database
Explanation: thumbnails and some database's could get corrupted making the media scanner running berserk, resulting in battery drain.
Fix: Using SGS Tools, Press [Apply script] select [clean_thumb_db.txt] and execute the script, this will delete the files that might get corrupted and reboot the phone so the database files and thumbnails get recreated.
WIFI Bug
Explanation: This is a mix of bugs and wrong settings, hardcore found some leftover debug code in the driver, tc80tc80 tested different routers seeing this effected the WIFI too, other users reported that the distance to the router effects battery drain as well. On top of this there are some settings that makes the WIFI running all the time that are not easily found.
Fix #1: Check your settings,[Wireless and network] select [Wi-Fi settings] uncheck [Network notification] press the menu key and select [Advanced] in [Wi-Fi sleep policy] select [When screen turns off]
Fix #2: See if you could try your phone with another router and compare to your home router, also check your signal that you have good coverage on the WIFI.
Fix #3: Use an updated Kernel, either hardcore's or trasig's and apply the wifi-fix (wifi-driver from JPA): View attachment update-wifi-dxjpa.zip
SGS Email 2.2.1
Explanation: The new email client has a bug making it drain the battery a lot if you set it to update every x minutes or manual update instead of push (exchange accounts)
Fix #1: Setup your account to push both on peak and off-peak, if you use imap or pop you can't do anything.
Fix #2: Use another email application, K9 or Improved Email have been reported to work much better. If you remove Samsung email you might need a fix if you have applications using your camera available here:View attachment CameraappsNoEmail.zip
Battery not "calibrated" - we don't have real facts on this one yet, so consider this our best guess
Explanation: It is said that the battery looses track of it's capacity (or rather the phone does) so it needs calibration.
Fix #1: Always flash new ROM:s with full battery.
Fix #2: Follow the guide TechnicR have on recal:
· Turn phone off and charge till full
· Start recovery and wipe battery stats
· Reboot and start the phone
· Use it heavily until it turns of by itself
· Connect charger and turn on the phone and wait until fully charged
Hardcore 256Hz vs. 500 Hz
Explanation: this is the system tick in the Linux system, number of interrupts per second for timesharing, gives a smoother appearance
Fix: None needed, the difference is not noticeable in battery drain.
Battery level drop to 95-98% when disconnecting charger
Explanation: We are used to that the battery is 100% chraged when we disconnect the charger, but with 2.2.1 we gat anything from 95-98%.
Fix: Not needed, this is a change in the charging cycle to prolong the life of the battery, but please take this in consideration of reporting battery drain, start counting from the actual value and not from 100%
For more info, check under Expert witnesses in the next post.
Could someone help me to explain the following phenomens as they are mentioned in so many various ways:
3D Gallery bug
Sensor driver hangs
Auto rotate bug
Link to my current phone config and battery life:
http://forum.xda-developers.com/showpost.php?p=10521024&postcount=613
If you wan't to support me more than by contributing to this thread, consider if you would like a easy and automatic backup for your PC, 2Gb free plus a 256Mb bonus space for both you and me, thats 2.25Gb of free backup space for your mail and documents (and anything else you want) and for each referal you make in the future you get an extra 256Mb space added to your account.
I have been using Mozy for 3 years now and I'm very happy with it.
Sign up from here: https://mozy.com/home/free/ at the end of the registration please enter my referal code: BQBF53
Gathering the suspects
Let’s get rid of the “I think” “If you only do” and “I’ve heard that” and start arresting the suspects, line them up, and execute them (oops, did I say that out loud?), and put them in quarantine until further notice.
To keep this thread cleaner, we’ll only focus on 2.2.1 mainly XXJPU/X/Y and not bother with to old 2.2 ROMS
Let's end the guesswork and start a scientific approach on this, it’s ok to suspect something, but you must have some evidence.
We need repeatability on the problems, so if you did something that started to drain your battery, describe this in as much detail as possible so someone else can verify your findings.
I have gathered some suspects but now I need your help in Collecting Scientific Information (CSI) to round up more suspects or eliminating them so we might find the truth about the drainage problem.
Forensic tools:
Free/Pay, Application name + author
Both, SystemPanel by NextApp
Free, OS Monitor by eolwral
Free, Android System Info by ElectricSheep
Free, Shark for Root by Elviss Kustans (not native version)
Free, Shark Reader by Elviss Kustans
Battery Monitoring / Saving tools:
Free/Pay, Application name + author
Free, JuicePlotter by Latedroid
Free, JuiceDefender by Latedroid
Free, Battery snap by Xhelas
Free, Brightness Level by CurveFish - let you lower the brightness another 8% and give you some extra milage
Free, Screen Filter by haxor industry, reduce the brightness a lot! thanks for the tip lpy
List of suspects:
#1 SGS Email 2.2.1 sync set on every x minutes - will be charged as an environmental villain, is put in custody pending trial
#2 Battery not “calibrated”
#3 Corrupt database files for media scanner
#4 Modem version X
#5 Voodoo lagfix
#6 WIFI bug - could be organized crime here, many villains involved. hardcore has infiltrated them and so far he has put 2 of them behind bars!
#7 Non KIES updates - could Samsung original updates be better
Prosecutor’s witnesses:
For suspect #1, SGS Email 2.2.1:
http://forum.xda-developers.com/showpost.php?p=8554755&postcount=546
http://code.google.com/p/android/issues/detail?id=9307 - very strong witness
For suspect #2, Battery not calibrated:
http://forum.xda-developers.com/showthread.php?t=722862
http://forum.xda-developers.com/showpost.php?p=9075485&postcount=5653
http://forum.xda-developers.com/showpost.php?p=9149156&postcount=143
http://forum.xda-developers.com/showpost.php?p=10092321&postcount=11053
For suspect #3, Corrupt database files for media scanner
http://forum.xda-developers.com/showpost.php?p=9075485&postcount=5653
For suspect #6, WIFI bug
http://forum.xda-developers.com/showpost.php?p=10038645&postcount=29
http://forum.xda-developers.com/showpost.php?p=10042758&postcount=6627 - hardcore found some leftover code in WIFI driver
http://forum.xda-developers.com/showthread.php?t=873779 - tc80tc80 tested different wifi routers with scary result!
For suspect #7, Non KIES updates
http://forum.xda-developers.com/showpost.php?p=10057892&postcount=69
http://forum.xda-developers.com/showpost.php?p=10061398&postcount=73
Defender’s witnesses:
For suspect #6, WIFI bug
http://forum.xda-developers.com/showpost.php?p=10043778&postcount=49
Expert witnesses / interesting battery info:
http://www.androidpolice.com/2010/12/14/your-battery-gauge-is-lying-to-you-everything-you-need-to-know-about-bump-charging-and-inconsistent-battery-drain/
http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
If you want to support me me more than by contributing to this thread, consider if you would like an easy and automatic backup for your PC, 2Gb free plus a 256Mb bonus space for both you and me, that’s 2.25Gb of free backup space for your mail and documents (and anything else you want) and for each referral you make in the future you get an extra 256Mb space added to your account.
I have been using Mozy for 3 years now and I'm very happy with it.
Sign up from here: https://mozy.com/home/free/ at the end of the registration please enter my referral code: BQBF53
A little stuff that could be good
Usefull stuff and help will be collected here
To find out if suspect #3 has visited your phone (frequent flashers should suspect this) then this might help:
In SGSTools ther is a script to do that procedure of removing thumbnails and also delete two databases so they get rebuilt after reboot. In SGSTool (search market, need root) press Apply script then select clean_thumb_db.txt
----------
Modems could have a positive/negative effect on battery life, it could depend on what carrier you are on different regions could also matter.
pele78 have made a very good page about different modems, please take a look at it:
http://forum.xda-developers.com/showpost.php?p=9579987&postcount=11945
And DocRambone has a great collection of modems if you want to test another to see if it gives you a couple of extra hours in you SGS:
http://forum.xda-developers.com/showpost.php?p=9724862&postcount=14434
-----------
lpy hooked up a multimeter to the battery and did some live measurements, I have put them in one post that you find here:
http://forum.xda-developers.com/showpost.php?p=10137241&postcount=387
-----------
TheYar has a batterythread over at the captivates forums, you might find some interesting things over there as well:
http://forum.xda-developers.com/showthread.php?t=806211
-----------
rigor.m made this suggestion:
To check for wifi bug, from a pc, log in to your router, check what IP your phone got, ping that IP from your PC does the phone respond when wifi should be off? - Report your findings!
-----------
Added January 11:
About the battery meter, hardcore found something weird, please see his post:
http://forum.xda-developers.com/showpost.php?p=10505720&postcount=8811
Regarding these things, please check the links under Expert witnesses in the previous post.
-----------
Feel obliged to recommend a visit to hardcore's Speedmod kernel thread:
http://forum.xda-developers.com/showthread.php?p=10056736#post10056736
Also this post for a different wifi firmware:
http://forum.xda-developers.com/showpost.php?p=10056736&postcount=6706
And a direct link to his download page:
http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-download-speedmod.html
And now I also add trasig's Advanced Voodoo 5 kernel with OC/UV:
http://forum.xda-developers.com/showthread.php?t=823300
Direct link to his download page:
http://kernel.1ug.org/
If you want to support me me more than by contributing to this thread, consider if you would like an easy and automatic backup for your PC, 2Gb free plus a 256Mb bonus space for both you and me, that’s 2.25Gb of free backup space for your mail and documents (and anything else you want) and for each referral you make in the future you get an extra 256Mb space added to your account.
I have been using Mozy for 3 years now and I'm very happy with it.
Sign up from here: https://mozy.com/home/free/ at the end of the registration please enter my referral code: BQBF53
Extra - useful CWM files
Info moved to post #1 - reserved for additional info
If you want to support me me more than by contributing to this thread, consider if you would like an easy and automatic backup for your PC, 2Gb free plus a 256Mb bonus space for both you and me, that’s 2.25Gb of free backup space for your mail and documents (and anything else you want) and for each referral you make in the future you get an extra 256Mb space added to your account.
I have been using Mozy for 3 years now and I'm very happy with it.
Sign up from here: https://mozy.com/home/free/ at the end of the registration please enter my referral code: BQBF53
I have tested mine overnight (JPX) and lost 10% in around 8 hrs. 2.2.1 email client set to sync every hour on two accounts. I have now turned it off and will update once tested again.
Using built in monitor and SGSInfo, I've found no anomalies in battery usage, but it is higher than previous firmwares.
Good idea for a thread!
Ah, this is the perfect thread for me. I'm in the midst of trying to recalibrate my battery. I can say though, that with wifi and 3g off, I get next to no drain. (A bit annoying having to have them off though). I do however get drain with 3g on. I currently have gmail sync on and I've updated with the AOSP email now with push sync for exchange to see if it helps.
OK, I'll share my current status.
I've been using XWJPA with JPM modem for more than a month and was very satisfied with battery life.
Recently I upgraded to Doc's rom v5.1 (XXJPX based) and that introduced a battery drain problem.
When WiFi is connected, the phone fails to sleep properly and is running more than 50% of the time when idle, which results in huge loss of power (more than 10% per hour on several ocasions).
I've since upgraded to Doc's v6, v6.1, v6.2 as well as stock XXJPY, kernels Voodoo 5.0.3, Hardcore's K12, and stock, modems JPM, JPP, JPY = problem persists. All testing done on clean flashed roms with no additional software installed.
Another (well known) issue i'm having since JM1 is "Time without signal: 50%" which is easily solved by switching Airplane Mode On and Off, but it's annoying nonetheless, especially if you forget to do it upon restart only to find your battery is flat 5 hours later.
Darkyy has fixed this wifi battery drain issue and a load of other stuff in his latest ROM
http://forum.xda-developers.com/showthread.php?t=814091
Excellent ROM, pure speed and looks tasty
check wifi sleep policy too
I experienced quite a ridiculous amount of drain on the stock + voodoo kernel bundled with Doc's JPY 6.1 ROM as well as on SpeedMod k11c. I literally saw my battery dwindle down as I was using it normally yesterday.
No games, no music or video...just exchanging a few text messages and setting up my apps and such again after a fresh flash. Wifi, 3g, Bluetooth, Auto-Rotate, GPS were all off. Brightness set to the lowest possible. Still lost as much as 10-15% in an hour and let's say within that one hour the screen was on for half the time (I was out of the house so I didn't time it or anything)...
Have not had good battery life since Doc's JP8 ROM sadly and that was back in the days of 2.2...
hydrouk said:
Darkyy has fixed this wifi battery drain issue and a load of other stuff in his latest ROM
http://forum.xda-developers.com/showthread.php?t=814091
Excellent ROM, pure speed and looks tasty
Click to expand...
Click to collapse
AFAIK he has not fixed it, but thinks XXJPY has the fix included, which is not the case for me.
hydrouk said:
Darkyy has fixed this wifi battery drain issue and a load of other stuff in his latest ROM
http://forum.xda-developers.com/showthread.php?t=814091
Excellent ROM, pure speed and looks tasty
Click to expand...
Click to collapse
I've read through the latter posts on there and the problem still persists for a lot of people. Wifi battery drain issue still doesn't seem resolved in his latest ROM according to recent posts.
From my side, i have noticed a quite a big difference in battery drain when switching from voodoo to speedmod's kernel. (speedmod's being much better in terms of drain in my case), but having said this, I never came any close to JPO in terms of battery drain yet. That was much better for me.
I installed the latest voodoo kernel last night, and noticed that in my Battery info history, the infamous "0" process did not appear at all in network usage, and battery drain was not that bad (still nowehere close to JPO) but not bad either. Basically I removed the phone from the charger at 4AM this morning (after trying the suggested "trick" of fully draining the phone and charging while the phone was off, have no idea if this makes any difference at all ... but am out of ideas at this stage) and am at 66% battery at 3:00 PM. I would say on less than normal usage today, since I did not use it much, but I have seen worse.
I hav now just flashed the latest speedmod kernel, based on JPX (http://forum.xda-developers.com/showthread.php?t=822756) K12 and will revert back.
I have also tried all the wipe battery stats suggested (with charger, without charger, at 100%, at 1% and so on, none ever helped)
Also the script to clear the thumbnails and the possibly corrupted databases ... still no joy
hydrouk said:
Darkyy has fixed this wifi battery drain issue and a load of other stuff in his latest ROM
http://forum.xda-developers.com/showthread.php?t=814091
Excellent ROM, pure speed and looks tasty
Click to expand...
Click to collapse
Ok, thanks for the insight, but please don't use this thread as an adverising space.
So for some facts:
"this wifi battery drain issue" guess you refer to the previous poster, but I would really like to know a little mor details about the problem, and how has Darkyy fixed this?
Refering to the 1 post in a thread is not the kind of scientific facts that will help finding the true causes so could you be a little more specific?
bokbacken said:
Ok, thanks for the insight, but please don't use this thread as an adverising space.
So for some facts:
"this wifi battery drain issue" guess you refer to the previous poster, but I would really like to know a little mor details about the problem, and how has Darkyy fixed this?
Refering to the 1 post in a thread is not the kind of scientific facts that will help finding the true causes so could you be a little more specific?
Click to expand...
Click to collapse
It's a "fix" that came with JPY, not actually one done by darky..and it still isn't fixed according to recent posts by those who've recently updated to his JPY (v7) ROM.
Interesting thread! I went from 2.2 JP8 to 2.2.1 JPU and found that my battery drain decreased, it went from 2 days between charges to (almost) 3 days. I then flashed JPX and then JPY and found the battery drain terrible with both, I was lucky to get a day and a half before recharging. I've just flashed back to JPU and then flashed the BUJP5 modem (which is the correct stock one for my phone / country). I'm waiting to see what happens to the battery life now... I'll post results as soon as I get a feel for whether it's any better / worse.
anoneemooz said:
It's a "fix" that came with JPY, not actually one done by darky..and it still isn't fixed according to recent posts by those who've recently updated to his JPY (v7) ROM.
Click to expand...
Click to collapse
Hi!
Yes I know that, I only want the posters to start thinking a few steps ahead, I don't really care for this "If you only install xxxx:s ROM, all problems are fixed", it's not the kind of posts any of us wish to see here.
Both you and I know for a fact that there are no quick fixes
i have no problems on anyfirmware. my phone works like a 7 days or more on each firmware all i use is a stock rom and a app killer i kill all apps everytime i put it into standy. working great for me so far.
bokbacken said:
Hi!
Yes I know that, I only want the posters to start thinking a few steps ahead, I don't really care for this "If you only install xxxx:s ROM, all problems are fixed", it's not the kind of posts any of us wish to see here.
Both you and I know for a fact that there are no quick fixes
Click to expand...
Click to collapse
True that!
Hm I left my phone untouched for an hour and a half and checked battery history and I'm down to 98%. Apparently my wifi doesn't sleep even if I already set the wifi sleep policy to "Never when plugged" :|
SKeijmel said:
i have no problems on anyfirmware. my phone works like a 7 days or more on each firmware all i use is a stock rom and a app killer i kill all apps everytime i put it into standy. working great for me so far.
Click to expand...
Click to collapse
7 days?! lol do you do anything with your phone besides kill apps?
Last Edited 4/25/2011 @ 1:00PM EST
*** I’ve updated on my previous post on HTC EVO Best Practices for Battery Management that I’ve put together. There were certain steps that were fine tuned and others that were either added or removed. I just wanted to share with everyone in order to save the time I spent researching, applying and testing these fixes on my EVO and a couple of other EVO’s I’ve tested. ***
*** Just an FYI, I didn’t write any of the apps/codes listed below. I just spent a lot of hours researching methods to improve the battery life on my EVO on several different sites. I’ve linked the sites where I got the information and giving ALL credit to the original posters. If I missed any names and If there are anybody that needs credit to be added for any of the steps below, please let me know and I’ll add them right away. ***
*** These steps have been ONLY tested to work on AOSP ROMs like Destroyer v2, CyanogenMod and MIUI. ***
*** Finally, this is meant to just be a guide for Best Practices for Battery Management. I’ve tested these steps on several HTC EVO’s which had Destroyer v2, CyanogenMod 7 or MIUI and had no issues. If you decide to try these steps in the guide, I take no responsibility for any items that might go wrong with your phones . ***
All that said, let’s get started. I’m looking to keep this as a “Living Document”, so I will continue to update and edit this original post with any new info that is shared by others or get discovered over the next few weeks. For anyone that’s new to rooting and flashing ROMS, I’ve added the first two steps. Most 99% of everyone else on this site, please move onto Step 3.
Step One, Root Your Phone.
Easiest way to do that is to go to http://unrevoked.com/ and select your phone. Then select Unrevoked3 “Painless root and flash”. If you’re a MAC or Linux user, just download the software. If you’re on a Windows computer, download and install the HBoot Drivers by clicking on “More Info?” Once you launch the software, just follow the onscreen prompts and your phone should be rooted within 5-10 minutes.
Step Two, Backup and then Flash a ROM.
Easiest way to do that, is after you’ve rooted the phone, go to the market and download the app ROM Manager by ClockworkMod. Once you access the app, it's very important to first backup the ROM that came prepackaged with your phone in case you ever need to flash back to it. Click on "Backup Current ROM", I even saved a copy of that backup on my computer incase I need to copy it back to my phone.
To flash a new ROM, click on click on “Download ROM” and you’ll be able to install CyanogenMod 7.0.0 Stable Release. Or you can go to their site and download the ROM from them at http://www.cyanogenmod.com/ Another ROM that this works well with the steps below is MIUI and you can download that ROM from http://www.miuiandroid.com/
Step Three, Upgrade the Kernel.
I’ve found that every person’s phones are setup differently. Also different kernels work better on certain phones then others. The two best kernels are SavagedZen and Tiamat. Personally, just my opinion, I got better performance from SavagedZen kernels, so that’s what I go in detail below. Although test for yourself, as Tiamat 3.3.7 has gotten great reviews also.
There are also different type of kernels as CFS, BFS or SBC and no-SBC. What are the differences?
SBC is Super Battery Charge. Basically, it enables a trickle charging effect on the charger. It fills the battery up to 100% so when you pull it off of the charger, it's absolutely full. The noSBC kernels use the stock battery driver and charge differently. Some users are not comfortable with SBC and prefer not to use it. They do not trust it and believe it may cause failure although there has been no evidence that it will actually do so. Again, this is a user preference and why both builds are created at this time.
As for CFS or BFS, they are schedulers. CFS is the default Android scheduler that all stock kernels use. Its called the Completely Fair Scheduler and schedules the CPU fairly. BFS, or Brain F*** Scheduler, gives the present task a higher priority and background tasks less CPU. Which one to use is more or less on the user.
Most people wouldn't notice any difference. In theory, watching videos, playing games, and listening to music should be smoother with BFS, because it emphasizes the foreground task. CFS should be better for running background tasks, because it gives equal priority to everything. And some peoples' phones don't play nicely with BFS, so CFS is generally the reliable fall-back option.
Above is just a summary, although if you want to read more in detail about kernels, I got all the info above from this link http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf
Finally, once you’ve installed CM7 or MIUI, next step is to upgrade the kernel to Savaged-Zen. Go to this link http://mirror.savaged-zen.com/ and download the kernel from April 7th named “SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB-signed.zip” and copy it to your SD card. Then turn off the EVO and turn it back on in recovery mode (Holding down the down volume button then then pressing power). Once ClockworkMod Recovery loads up, scroll down and select “Install zip from sdcard”, then scroll down and select “choose zip from sdcard”. After that, just scroll down to where you’ve saved the Savaged-Zen kernel and install it. Once the phone reboots, check to see if the kernel has been applied properly by going into Settings\System\About Phone (from MIUI menu) and then click on More Information. Kernel version should now have SavagedZen listed.
Step Four, Lower voltages on AOSP kernels.
–viperboy- had a great post on this topic, below is the link for his instructions http://forum.xda-developers.com/showthread.php?t=1028322 . I usually start off first by flashing the 50mV.zip and if it’s stable for a day or two, then I upgrade to 75mV.zip. On one EVO, I went up to 100mV and it started rebooting until I lowerd it back to 75mV. Haven’t had any issues with it since. On another EVO, I had to lower it from 75mV to 50mV to resolve freezing issues and haven’t had any issues with it since. Point is, you have to find the best voltage level that works best for your phones.
Step Five, change the Heap levels.
After updating the kernel and voltage levels, download VM Heap Tool from the Market. That tool will let you adjust the heap size on your phone, which Heap is the amount of memory each application can use. By default, your phone is set to 32m, which has issues with force closers of the launders and files. After you download the app, adjust the heap level to 40+. I've gone with 44m and haven't had any force closers, where before I would get 1 or 2 a day.
People running the latest build of MIUI release 1.4.22 Beta 7, stiffspliff changed the default MIUI Heap level to 64. So any MIUI users on the new release do not need to install\use this tool anymore.
Step Six, download BatteryCalibration app from the Market.
Useful tool especially if you like to keep switching\testing new ROMs on your phone. Calibration needs to be done after flashing a new ROM, since the program will remove the batterystats.bin system file. The OS generates a new clean batterystats file soon, thus any fake information from the previous ROM is removed.
Step Seven, manually setup the display settings.
When checking the Battery Settings\Battery Use, the Display is usually the biggest battery drain. To help offset this a little bit, go to Display Settings and turn automatic brightness off. Then manually setup the display at 25-30% brightness. Usually just take it down as far possible that you feel you’re comfortable seeing the screen properly.
Step Eight, condition the battery
Below are the steps to follow from a XDA member HipKat that have worked nicely to condition the battery.
1 - The "HTC Method w/10 Time Unplug"
Charge to full, unplug, turn off the phone, charge while off for another hour. Unplug, turn the phone on for 2 minutes, turn it off again, charge for another hour.
Unplug til the light goes off, plug back in til it turns green.
Do that 10 times.
Boot to Recovery, while plugged in. Clear battery stats, boot to system. And wait 2 mins, THEN unplug.
Also, I keep my GPS, mobile data and WiFi off unless I need it. You don't need either of those to make phone calls or texts.
Step Nine, what to AVOID
This step isn’t anything to install or update on your phone, it’s more meant for what type of apps to avoid.
First is Juice Defender, who with more research I’ve found could either help or drain your battery life. If you have JD on all day when you're not really using your phone much, in an area where your phone would normally be searching for data all day, wasting power, the battery savings are HUGE.
Although, if you're constantly using your phone, the battery savings are negligible at best, and negative at worst, since it would be constantly turning your data service on and off. So depending on each person’s definition of how they use the phone, JD might be an application to avoid, especially if you’re a mid to heavy user of your phone.
Next is any type of Task Killers. XDA poster Justin.G11 has a in detail blog on this topic and below is the link for anyone interested.
http://egotoobigtovirtualize.blogspot.com/2011/03/android-battery-goodies.html
In a quick summary, using a Task Killer puts a little program in memory that will routinely scan your phone for running applications and forcefully close them, returning that memory to your phone. The problem is that this is a bad idea and the result of people assuming that multi-tasking in android is the same thing as multi-tasking in a desktop OS.
In it’s best moment, a task killer does absolutely nothing for your phone. It kills apps in memory that the process lifecycle service would have freed the moment it was needed anyway. The power consumed by your memory is constant weather it’s storing a 0 or a 1. So that doesn’t save you in battery at all. Instead, it nearly costs you battery because you just added a regular 15min scheduled task to monitor your apps. Which gives your android system more to do. Not only that but remember normally android stores the “activities” before it kills the app. Something the force close of a task killer will skip. This why you often have to re-login to apps that were force closed by a task killer, as opposed to that illusion of always running when android does the job. What’s funnier is because it registers background tasks with android, they will simply re-launch anyway. Meaning task killer will constantly find itself shutting down the same process over and over again, making the whole thing extra pointless.
Short of it is: 100% of any battery gains are placebo, and better battery gains could be easily achieved by changing the polling cycle of your apps so the android service doesn’t have to launch so many things so regularly. Forcefully closing apps with a task killer does not go to the root of your battery problem, does nothing to help, and simply impacts the user experience by skipping the storage of activities.
Step Ten, Control the polling of e-mail
Again another great write up by Justin.G11 in his blog linked above is Control the polling of e-mail. What we need to do is ratchet down on the polling and and background syncing our phones do to keep our battery life up. Most times, our #1 offender is e-mail, and more times than that, it’s POP3 or IMAP.
Let’s just throw it out there: POP3 is terrible for battery life. We are basically telling our phones to launch an email app every x minutes and sync/download. This means I have to choose between fast polling intervals to get mail instantly (5 minutes or faster) which will drain my battery with regular processes, or save battery with slower polling but mean that I may not get important emails for 30 minutes or more (in the land of instant gratification and IT support … this could be a deal breaker).
Thankfully ActiveSync provides us with an easy way out (ditto for Google Gmail, but that’s not my focus at them moment.)
Systems like Gmail and ActiveSync use a clever mechanism known as long-lived http to do their mail polling. What happens is a client will log into the target server, check for mail, then say “if any mail comes in the next 30 minutes, ping me at this IP” then stop. The actual time is a variable, that the phone cranks up slowly until it’s too long to make through the firewalls in the path of communication, but 30mintues is not uncommon. So after the initial poll the mail program can stop, be removed from memory/CPU, and a simple listener trigger is left on android for 30minutes incase the Exchange Server decides to “wake up” the mail client in order to deliver a new message.
This is really nice because it means I can have a slow 30minutes polling interval and save battery while having the email delivery time of a constant poll. But it means I have to stop using POP3… and start using ActiveSync for work, and perhaps Gmail for home use.
So how do I do that? Well you have Gmail if you have an android phone, and in the Accounts and Imports section of your mail settings you can setup Google to poll your various POP3 services for you. Bingo: best of both worlds. As a final “but I like keeping my messages separate”, you can label each message as it gets delivered to your gmail inbox so you can keep your messages sorted by POP3 account, and even register multiple smtp names for sending. A full solution.
By doing this I can now bring my battery down _significantly_ without sacrificing the ability to get emails at all. Major win in that department. Once I have all my personal POP sources tunneled through Gmail, I can simply rely on ActiveSync for work!
That’s it guys! Hope this post has been helpful in extending your phones battery life.
Here are my phones specs at the time of the testing...
HTC EVO
Model Number: PC36100
Build Number: MIUI-EVO-1.4.15-ENG
Kernel version: 2.6.38.2-SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB+
Battery type: Stock battery that came with device (prior shelf life 4-6 hours of heavy use)
After following all 10 steps I get the following performance from my battery
Heavy Use - 15+ Hours
Only about 4-5 hours phone is idle
30-60 minutes on the phone
Using WiFi at home and work, 3G while in my car or out on the town
20+ text messages
Download 5-10 apps per day
Play games 2-3 hours, maybe more if stuck in a meeting
Listen to music to and from work, about an hour per day.
On the internet most of the day, especially since I like to access facebook and twitter via my phones browser instead of their apps.
Watch 2-3 hours of videos\Youtube
Spend about 1 hour customizing my themes and\or downloading new themes
Finally, did a movie test on Sunday. After a 100% full charge, disconnected and played two movies on the phone. After about 4 hours when the movies were done, battery was still at 52%.
On Average, battery would drain 8-12% per hour of constant continual use when playing games, watching videos or listening to music.
As I said earlier in this post, I want this Best Practices for Battery Management to be a Living Document and I’ll be constantly updating\editing it once new or better practices\apps have been discoved for improving the battery life.
CREDITS
unrevoked.com for the “Painless root and flash”
ClockworkMod for “Rom Manager”
Guys at CyanogenMod for a great ROM
Guys at MIUI for a great ROM
Guys at Savaged-Zen for a great kernel
Taylor Groves, Jeff Knockel and Eric Schulte on their indetail info on kernel differences
-viperboy- for his instruction on how to lower voltages on AOSP kernels
Martino for “VM Heap Tool”
stiffspliff for increasing the MIUI default Heap level to 64
HipKat for the battery conditioning method
NeMa for “Battery Calibration”
Justin.G11 for his blog about Task Killers and Control the polling of e-mail
Define 15+ hours of heavy use. If the phone is on for most of that time and using data, then JD is not going to be doing much is it?
Your tips are well written - a good starting point for someone new.
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Good read though.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Click to expand...
Click to collapse
Obviously, you should that someone is talking about the stock battery unless otherwise noted.
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
instructions are a little biased.
jalai said:
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
instructions are a little biased.
Click to expand...
Click to collapse
maybe he didn't think sense users deserved attention?
Definitely I good starting point. I would recommend tasker over jd, but that's just me
Swyped from my cyanogenized and gingerbreaded EVO
Step 11. Get a kernel with SBC for maximum battery life!
Sent from my EVO using Tapatalk
I found this useful. I knew everything else but it introduced me to the battery calibration app and lowering my voltages.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Good read though.
Click to expand...
Click to collapse
would these instructions be applicable to someone using an extended battery? If so, should the battery life be extended in that scenario?
ECrispy said:
Define 15+ hours of heavy use. If the phone is on for most of that time and using data, then JD is not going to be doing much is it?
Click to expand...
Click to collapse
Sorry, I just signed up to this site and this was my first post. I've edited my original post above to reflect what my definition of 15+ hours of heavy use was and give a detailed breakdown.
goodboynyc said:
What bothers me is people say "I got X hours on Y type of usage." Without specifying what battery they're using.
Click to expand...
Click to collapse
I edited my original post to detail that I'm using just the stock battery that came with the phone. I also added the specs of my phone for those that were interested in what ROM and Kernel I was running during these tests after I did all 10 steps.
jalai said:
you should reset the title for HTC EVO Best Practices for Battery Management on AOSP ROM's.
Click to expand...
Click to collapse
Good ideal, I just edited the subject.
twiz0r said:
maybe he didn't think sense users deserved attention?
Click to expand...
Click to collapse
Meant no disrespect to any sense ROM users.
I'll be testing a few sense ROMs next weekend, I'll do a similar post once I've tweaked these steps to fit sense ROMs I'll upload and do some more battery tests.
twiz0r said:
Definitely I good starting point. I would recommend tasker over jd, but that's just me
Click to expand...
Click to collapse
Thanks for the feedback, that's exactly what I'm looking for. As I want to best tweak these Best Practices for Battery Management on AOSP ROMs as much as possible. I'll test out tasker compared to juice defender to see if it'll help my battery life.
another good tip would be to spell AOSP correctly. What the hell is ASOP? a fable?
if you can't remember how to spell it, here's a tip:
Android Open Source Project
deathsled said:
another good tip would be to spell AOSP correctly. What the hell is ASOP? a fable?
if you can't remember how to spell it, here's a tip:
Android Open Source Project
Click to expand...
Click to collapse
LOL.....great tip, that's what I get for trying to edit my posts quickly.
Madvillebuck said:
would these instructions be applicable to someone using an extended battery? If so, should the battery life be extended in that scenario?
Click to expand...
Click to collapse
As long as your running an AOSP ROM like CM7 or MIUI, these instructions would be applicable to anyone, including those using an extended battery.
Since I don't have an extended battery, I'd love to hear feedback on performance from anyone who tried all these steps on an extended battery.
NYG27 said:
Thanks for the feedback, that's exactly what I'm looking for. As I want to best tweak these Best Practices for Battery Management on AOSP ROMs as much as possible. I'll test out tasker compared to juice defender and will try a kernel with SBC to see if they help my battery life.
Click to expand...
Click to collapse
Are you sure you're not already using an SBC kernel? SZ are SBC unless you specifically download the non SBC version. Also, kernel performance is phone dependent. Some people may see better battery life on the stock kernel or Tiamat (AOSP).
Which kernal should i get for improved battery performance? Im on Destroyer v2 mod & battery drains fast...Link would help to kernal!
Maybe I think too logically, but wouldn't all those apps you say to d/l be using battery to run in the background??
No offense, but I get excellent battery life just by keeping data off when I'm not using it.
jstalford said:
Are you sure you're not already using an SBC kernel? SZ are SBC unless you specifically download the non SBC version. Also, kernel performance is phone dependent. Some people may see better battery life on the stock kernel or Tiamat (AOSP).
Click to expand...
Click to collapse
Reason I mentioned “SavagedZen-1.1.0-CFS-HAVS-WiMAX-GB-signed.zip” as the kernel to download, is that I've read about and tested that kernel to be more stable. (Maybe just my personal preference).
By all means test out the BFS kernel and see if you get better performance. There are also none non-SBC kernel but I haven't tested them out yet.
I try to flash a different ROM and kernel each week and test them out. As I do, I'm going to update my original post as much as possible to try to get a true Best Practices for Battery Management for both AOSP and Sense ROMs. So far I've only tested these steps with CM7 and MIUI, which is why I only caution people to test these steps with those ROMs or other aosp roms. The more testing I do with sense roms, I'll update my original post on this thread to be compatible with both aosp and sense roms.
HipKat said:
Maybe I think too logically, but wouldn't all those apps you say to d/l be using battery to run in the background??
Click to expand...
Click to collapse
If you look at Battery Settings\Battery Use, those apps hardly take up 1-2% of my battery running in the background. That's a trade off I'll take for having them improve the overall performance of my battery.
HipKat said:
No offense, but I get excellent battery life just by keeping data off when I'm not using it.
Click to expand...
Click to collapse
No offense taken. Although truth be told about your comment, you have listed in your sig that you use the Sedio Extended battery 3500 mAh. If I had an extended battery and kept data off when I'm not using it, I'd have great battery life also. Although I don't like the look and the bulkier feel of the extended battery (no offense, just my personal preference).
That's why I created this thread to help people extend the life of their stock battery that came with the EVO.
Tiamat>SZ for battery life.
Hello all,
Following XDA for years, but wasn't posting that much. My apologize for that, trying to give my contributions now
So, to start, hereunder, a sum up of my recent tests over last German ICS rom, Stock XXLRG.
======================
This is the second version of this post, taking in account various comments so far.
Firtsly, this is aimed to share my feelings about my own experience. Hope this could help anyone in anything. Nothing more
Accordingly to Roy_W, I provide which I will call my "test phase" description at the end of post, as simple infos for you to better make your opinion according to your own use. It is not about precise calculations & results, but about comparing the same things.
Hope this helps.
======================
Tests
1. Stock LRG + Stock Kernel, No root
2. Stock LRG + Stock Kernel + Root + remove some samsung apps.
3. Stock LRG + Speedmod 3-7 + remove some samsung apps
4. Stock LRG + CF-Root LRG + remove some samsung apps.
Impressions
1. In my opinion, do not use this setup. Rom feels very laggy, many little freeze here and there but the must annoying is the battery drain and heat while wifi download.
I think this is due to screen ON + heavy download (1GB+, games like Max Payne or Nova)
Pen is not well reponsive also.
Note : Except in test 3, there should be no difference with pen responsiveness between 1,2 and 3. but that was the case to me. Dunno why ^^
2. Starting to feel better, due to the removal of some Samsung apps (Rooting should not have this kind of effect .
Complete list of removed applications at the end of this post.
The phone is more responsive, lesser lags, but other things from test 1 (battery drain, pen responsiveness) remains the same.
3. Very good setup.
Lags are mostly gone, and Pen responsiveness is far better.
Don't know if Speedmod have done some special work for that, or is just due to his overall tweaks. I think it is also related to Samsung S-Suite updates. (look at test 4)
Good battery, feels like it could be better but mostly due to Samsung Roms than kernel. With normal use (sms, few calls, internet, XDA app , new review, some always active sync like Weather, Gmail, Talk, ...), you can easily achieve 2 days (48h) before running out of juice.
Also lesser memory consumption in idle (maybe related to samsung apps that were removed)
But, bluetooth was not working and since it is a must have for me, I needed to go to test 4.
4. Currently in test. Don't have my bluetooth headset with me, so this test will be updated tonight or tomorrow for feedback about battery, bluetooth and other.
So far, overall responsiveness of the phone is ok, but not as good as with Speedmod.
Maybe a placebo ( ), but I always felt that Chainfire's kernel is behaving a little better than stock one even if the only difference is root rights.
Also lesser memory consumption in idle (maybe related to samsung apps that were removed)
Samsung Removed Apps
Always doing this since my GS. It always make the system smoother to me. Can't tell about battery save.
- All Hubs (Reader, Music, ...)
- All apps related to hubs. (Zinio, Press reader, kobo...are examples of ones eating too much storage space).
- the big one : Samsung social Hub (2 apks)
- All stock live wallpaper (storage space eater)
I did not removed the Kies apps, since there were never launched, do not bother me and was having some weird warnings about missing apks while trying.
I advised to keep All Share (which is functionnal and useful for cross hardware connection) and Samsung Apps (but deactivate sync from app settings)
Go also for setting, and deactivate Wifi sync for system updates (About Phone -> System updates).
I did not test NOTECore kernel which has good feedback (3.1 version) because of the bluetooth not working.
Test Phase
Mostly due to my work, I have quitely the same daily use.
- Kernel were flashed the morning, at full charge, with cache/dalvik cache wipe.
- Only 3G, no Wifi/GPS/Blutooth. Auto Brightness, no added/removed apps (except for tests cases above).
- Betterbattery stats, stock battery monitor and Go power master for battery monitoring
- Facebook sync off (for battery save)
- Gmail sync on
- Google+ sync & Instant Upload off (for battery save)
- Weather sync every 4 hours
- Samsung apps sync off (for battery save)
- 1h call
- Gtalk & Whatsapp always connected
- No Flash installed (feels like I should mention this)
- No kills or memory clean
- Fixed wallpaper (for battery save) & lesser lags for screens transitions and opened drawer using NOVA.
What I take into account while making my opinion about battery :
- screen on time versus battery lost for the same period of time. Having used different 720p androphones, I have my own appreciation of that.
For 2000mah full charged batteries in my use with full stock, 2-3h screen on time is really bad, 3-5h should be considered as a good average, 6h+ is a dream.
GNote has a 2500 maH battery, so I have my expectation and maybe that's why I feel bad battery bahaviour when it won't hurt you at all.
- if apps were differently used by me according to their respective impact on battery
- if the basic services of Android are stable towards battery (custom kernels often reduce that )
- any wake locks
- if battery seems not affected by side-effects like mentionned above, then wait for one week of use before stating.
What I take into account while making my opinion about smoothness:
It is about shutters between screens transition, apps transition, feeling about time for the usual apps to be launched, multitasking...nothing more that a simple user feelings
Bests
thanks for the tests... but we prefer the wiping tests... just kidding...
thanks for the info,
which method do you use to remove these apps please ?
Haha..only wipe caches & dalvik from speedmod and CF kernel. I won't take any rosk from stock kernel
For system apps removal, jusy need root and titanium backup
Sent from my GT-N7000 using xda premium
CF-root and stock kernels are identical. No tweaks. Nada. Just root and Clockworkmod recovery.
So, how can the phone lag with stock kernel and be OK with CF-root ???
Placebo ?
Maybe related to the init scripts. For sure the main thing is the root with this kernel but wihin these tests and also for all samsung devices I had with Cf, it were always behaving better.
As I also said, should be related to samsung apps removal, especially the hubs.
Sent from my GT-N7000 using xda premium
Phenryth said:
Hello all,
Following XDA for years, but wasn't posting that much. My apologize for that, trying to give my contributions now
So, to start, hereunder, a sum up of my recent tests over last German ICS rom, Stock XXLRG.
Hope this helps some of you.
Tests
1. Stock LRG + Stock Kernel, No root
2. Stock LRG + Stock Kernel + Root + remove some samsung apps.
3. Stock LRG + Speedmod 3-7 + remove some samsung apps
4. Stock LRG + CF-Root LRG + remove some samsung apps.
Impressions
1. In my opinion, do not use this setup. Rom feels very laggy, many little freeze here and there but the must annoying is the battery drain and heat while wifi download.
I think this is due to screen ON + heavy download (1GB+, gamers like Max Payne or Nova)
Pen is not well reponsive also.
2. Starting to feel better, due to the removal of some Samsung apps.
Complete list of removed applications at the end of this post.
The phone is more responsive, lesser lags, but other things from test 1 (battery drain, pen responsiveness) remains the same.
3. Very good setup.
Lags are mostly gone, and Pen responsiveness is far better.
Don't know if Speedmod have done some special work for that, or is just due to his overall tweaks. I think it is also related to Samsung S-Suite updates. (look at test 4)
Good battery, feels like it could be better but mostly due to Samsung Roms than kernel. With normal use (sms, few calls, internet, XDA app , new review, some always active sync like FB, Weather, Gmail, Talk, ...), you can easily achieve 2 days (48h) before running out of juice.
Also lesser memory consumption in idle (also related to samsung apps that were removed)
But, bluetooth was not working and since it is a must have for me, I needed to go to test 4.
4. Currently in test. Don't have my bluetooth headset with me, so this test will be updated tonight or tomorrow for feedback about battery, bluetooth and other.
So far, overall responsiveness of the phone is ok, but not as good as with Speedmod.
Should be related to various tweaks, and ChainFire always aimed to provide his kernels, with Root and few tweaks.
I had GS, GS2, and CF kernels were always really nice for those looking to a Rom not too far from Stock, but with some performance tweaks and root.
Also lesser memory consumption in idle (also related to samsung apps that were removed)
BUT, having some troubles with NOVA with this setup. Several freezes, and needs to restart the launcher.
I think it is related to root access which needs to be set again coming from Speedmod to CF. Will keep you informed.
Samsung Removed Apps
Always doing this since my GS. It always make the system fly
- All Hubs (Reader, Music, ...)
- All apps related to hubs. (Zinio, Press reader, kobo...are examples of ones eating too much storage space).
- the big one : Samsung social Hub (2 apks)
- All stock live wallpaper (storage space eater)
I did not removed the Kies apps, since there were never launched, do not bother me and was having some weird warnings about missing apks while trying.
I advised to keep All Share (which is functionnal and useful for cross hardware connection) and Samsung Apps (but deactivate sync from app settings)
Go also for setting, and deactivate Wifi sync for system updates (About Phone -> System updates).
I did not test NOTECore kernel which has good feedback (3.1 version) because of the bluetooth not working.
Hope this helps.
Bests
Click to expand...
Click to collapse
Got to be honest I disagree with a lot thats written here.
Point 1 :- Why shouldn´t we use this set up??You might have or had problems but a lot of other users don`t,me being one of them.I have had NO laggs,my battery doesn´t heat up that much with WiFi,nothing freezes and the battery life is 100% top,all what you did in Point 3 with usage I get in Point 1 plus a few hours more.
Point 2 :- Once again I disagree,I´ve had no problems what so ever,only rooted for a few extra apps and removed NONE of the Samsung apps,still fast and smooth.Battery life still top,even upto 3 day usage depending on what I´m doing.
Point 3 and 4.....can´t say anything about these points because I won´t go this far,why should I ,everything is super fast,no laggs,a lot less battery drain:good: no need for any mods.(bluetooth also works )
Maybe I´m one of the lucky ones with a good Note :laugh:but this report won`t help me,maybe a few with problems.
Hi I think you don't agree wih my report cause of different perceptions between you and I.
Battery perf is linked to what is acceptable or not for both of us and also from various comparison through many flashes since GB.
And for sure, Linked to the type of use we both have.
It is the same for smoothness. I must say I am very sensible to lags and freezes even milliseconds one For instance, I am so maniac with it that I can detect a lag in a movie while no one noticed around me.
Plus, you can tell about many things to explain mobile OS perf and I will not accept this since I can not accept that a phone running a spec near to a PC ones, suffers such perf issues.
The best example is the smoothness experienced with my nexus with Jellybean against ICS. It is day and night.
Sent from my GT-N7000 using xda premium
Thanks OP for the comparison :victory:
Good initiative from OP for the comparison. Each person use the Note in a different way and will have different results surely from OP. But the main point of this thread was to give us a basic idea on the different setups OP has used. Thanks!
Thanx for making thread with detail study, thogh i can not be agree with many of statements.
Here something i like to say
- There is nothing much difference between test 1 & 2 except you have Root and removed some applications.
So does it mean
*Rooting can improve performance - I dont think so
*Removing application just making space on system ROM, so does making room on system ROM, can increase performance? I dont think so
many application you have removed may not be activated on start, naturally that doesn't have any relation with performance, b'coz it just occupy space not RAM
Now some application which may have enabled on boot, even that gives you temporary extra RAM, As android itself have LMK(low memory killer) which auto kills background applications which is not in used - LRU(least recently used), and when there is enough RAM available, even you exit from applications it remains in background for quike reopening, that is basic android mechanism. So if your aim to remove some application to make available more RAM, it won't be fulfilled, b'coz that application will be replaced by recently used application by users till android system dont sense as RAM is full. (you ca test it - when you have many applications removed, sure you will have much free RAM on boot, but if you look again after 15 min of play with device, it will be again full, same as who dont have remove blotwares, so wat benefits we got by removing those?)
Yes atleast i can say applications which was running in background for some time can consume little juice, but if you believe me, my experience is it can save maximum 3-4%(of full cycle) nothing more than that. But performance? I dont have any logic to believe it.
-I can't comment on test 3, as i have never used any custom kernel, and leaving your opinion untouched.
-Again between 2 and 4
yes you have also not tested much, but somewat if your opinion goes in favor of 4 (as you said in 1&2 responce is not good but in test 4 you saying it is OK) then if i am not wrong chainfire himself said, his kernel is complete stock (minus mmc_erase_cap command +root+su binary+CWM)
so in that case your opinion may not be placebo?
Anyway dear don't feel bad. appreciate your workout, but some points which i said dont favor me to agree completely.
Regards
I think my note must have been XXLRG when I got it but after trying to do some rooting things and bricking it, then finally loading XXLR1 (ICS) It is working great with no lag or freezing what so ever. Also have scored up to 4050 on Quadrant!
Da mOnKeY said:
Got to be honest I disagree with a lot thats written here.
Point 1 :- Why shouldn´t we use this set up??You might have or had problems but a lot of other users don`t,me being one of them.I have had NO laggs,my battery doesn´t heat up that much with WiFi,nothing freezes and the battery life is 100% top,all what you did in Point 3 with usage I get in Point 1 plus a few hours more.
Point 2 :- Once again I disagree,I´ve had no problems what so ever,only rooted for a few extra apps and removed NONE of the Samsung apps,still fast and smooth.Battery life still top,even upto 3 day usage depending on what I´m doing.
Point 3 and 4.....can´t say anything about these points because I won´t go this far,why should I ,everything is super fast,no laggs,a lot less battery drain:good: no need for any mods.(bluetooth also works )
Maybe I´m one of the lucky ones with a good Note :laugh:but this report won`t help me,maybe a few with problems.
Click to expand...
Click to collapse
I have to agree with this post. I didn't recognize any of the problems stated in the 1st option. I am currently running stock everything after having tried several different combinations of ROMS/Kernels.
There is also a lot of missing information in relation to what exact tests were performed and how they were measured : Whats apps were running at the time, were Wifi / GPS / Power Saving active, what was the state of the battery, how was "lag" measured, what brightness setting was used, Was a good 3g station nearby or was the telephone continually searching for a stronger signal, etc etc etc , The list could go on eternally.
As for anything batttery related, I do not understand how tests can be performed that have not been run over a relatively long period.
There are far too many parameters and options possible, that it would appear that the tests are merely personal interpretation.
I appreciate that you have taken the time and effort to do the testing but I am not convinced that the results can be treated as anything other than one persons thoughts at a given time.
I think that you can only perform these kind of tests when they are performed "identically" on a device that is reset from scratch and that the tests performed are measurable with precise calculation rather than the human eye/sentiment.
It is an almost impossible achievement outside of a qualified environment with a very strict set of controls.
Can the results be reproduced, is there any possibility that the results could change, would a third party be able to reproduce the same results ?
Unless of course detailed results and calculations are actually available, in which case it would be very interesting to be able read them.
Hi Dr. Ketan. Again, thanks for your guide, test 1 & 2 was done following it
Do not worry, I won't feel bad about your feedback, as for the previous one.
For sure, I think you and Chainfire knows that type of things better than me (no needs to tell why ^^), just reporting here my feelings over my tests.
*Rooting can improve performance - I dont think so
Click to expand...
Click to collapse
Think the same.
*Removing application just making space on system ROM, so does making room on system ROM, can increase performance? I dont think so
many application you have removed may not be activated on start, naturally that doesn't have any relation with performance, b'coz it just occupy space not RAM
Now some application which may have enabled on boot, even that gives you temporary extra RAM, As android itself have LMK(low memory killer) which auto kills background applications which is not in used - LRU(least recently used), and when there is enough RAM available, even you exit from applications it remains in background for quike reopening, that is basic android mechanism. So if your aim to remove some application to make available more RAM, it won't be fulfilled, b'coz that application will be replaced by recently used application by users till android system dont sense as RAM is full.
Click to expand...
Click to collapse
Removing samsung apps does not affect that much battery, but smoothness. I certainly wrongly express myself.
Maybe CF kernel has nothing to do with it since I was always flashing this and removing the hubs (especially the social one) together.
But fore sure, since my galaxy S, even on the S2, and now on the NOTE, doing this does increase system smoothness.
I do not know that much about Android memory system managment, but the first time I've done this was because I was sick about seeing these services running in background, even without ever launching them once and it does consume memory.
Yes atleast i can say applications which was running in background for some time can consume little juice, but if you believe me, my experience is it can save maximum 3-4%(of full cycle) nothing more than that.
Click to expand...
Click to collapse
I believe you without any problems
You know the deal, 1% here and there...at the end, it saves some battery.
I will update my post, but I can now say that Speedmod provides better battery than Stock/CF, looking at my battery stats for today.
Roy_W said:
I have to agree with this post. I didn't recognize any of the problems stated in the 1st option. I am currently running stock everything after having tried several different combinations of ROMS/Kernels.
There is also a lot of missing information in relation to what exact tests were performed and how they were measured : Whats apps were running at the time, were Wifi / GPS / Power Saving active, what was the state of the battery, how was "lag" measured, what brightness setting was used, Was a good 3g station nearby or was the telephone continually searching for a stronger signal, etc etc etc , The list could go on eternally.
As for anything batttery related, I do not understand how tests can be performed that have not been run over a relatively long period.
There are far too many parameters and options possible, that it would appear that the tests are merely personal interpretation.
I appreciate that you have taken the time and effort to do the testing but I am not convinced that the results can be treated as anything other than one persons thoughts at a given time.
I think that you can only perform these kind of tests when they are performed "identically" on a device that is reset from scratch and that the tests performed are measurable with precise calculation rather than the human eye/sentiment.
It is an almost impossible achievement outside of a qualified environment with a very strict set of controls.
Can the results be reproduced, is there any possibility that the results could change, would a third party be able to reproduce the same results ?
Unless of course detailed results and calculations are actually available, in which case it would be very interesting to be able read them.
Click to expand...
Click to collapse
Many good hints in your posts.
For sure, I've made my tests with some knwoledge about that, and trying to be in the same scenario each time.
I will update my post towards the parameters activated and other you stated.
Thanx
yes custom kernel may have improvement, b'coz that is made for that purpose, and we know developer adds some tweaks to improve performance. though i have not tested it, i can be agree on that point. but i have not make review just b'coz i have not used.
Regards.
Phenryth said:
Many good hints in your posts.
For sure, I've made my tests with some knwoledge about that, and trying to be in the same scenario each time.
I will update my post towards the parameters activated and other you stated.
Click to expand...
Click to collapse
Phenryth,
I look forward to your results, the basic idea of what you are doing has the potential of becoming a very interesting article.
These are tests without any statistical significance.
So in the end your heart or gut decided.
Everyone has there own view on how their phone should perform. If you are happy with it then there is no need to change it. If not then this guide provides some tips on how to improve it.
Sent from my GT-N7000 using xda premium
To me for the first time ever since the ICS was introduced the 1- setup is absolutely the best I have tried, and I did try all four of them including removing Samsung bloatware.
The touch response is super sensitive, the pen works not just perfect but it also marks when in a diagonal position something never happened before, my one and only complain is the same one since seven months: the lag which comes when opening the Contacts application for the first time ,which is absolute outrageous other than that I am satisfied.
DOWNGRADING TO LOLLIPOP:: --- B151 from B331
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
----
THX @skeppley
THX @Demian3112
----
Figured the above was an important surprise for some of you... OP still valid
Hello Everyone! Im new to the whole Honor 5x thing, coming from an m8 now, and before that a nexus 6, and before that a z3 then before that an S4 and before that an HTC Evo 4G LTE... Along with some minors, LG Risio, Moto E, S5...
Im just happy to say that so far I really enjoy this phone! Within the first few days of using it on Lolipop, i was getting 1d 15h type battery life which if youve looked at the phones ive mentioned so far... Really..really..wasnt what I was used to. A Day? For sure, the htc would be at 18% getting back on the charger... and it would die at 10%... with how long id had it. But... A Day was doable.
Ive been looking for a phone for SOOooOOO long now that had good enough battery to last a day at max brightness... Tweaking kernels, and Installing various ROMS (all of them per device)... Crack Flashing, as some would say. It just became a hobby... Ive noticed many weird things about the community, to those reading... let me list them now...
1. People all of the sudden(within the last 2 years?) prefer stock android over anything, regardless of what additional features are being added... Such as battery life improvements, Multitasking improvements, theme improvements, usability improvements... People like stock android... hmmm?
2. People want to be nexus so bad they will theme other UI's to death, just to make it look like stock, generic android... hmm..
3. Battery life, while a common complaint, seems to be indifferent to how frequently people update their phones.. (note: Marshmellow EMUI has a multi core battery bug, listed on XDA under mods..) or what ROM they choose (note the most popular rom being one with significantly worse battery life than stock)
4. Security improvements are completely unnecessary to the community (note the most popular rom being one that hardly supports the fingerprint sensor)
5. No matter how many bugs (even those listed in OP) people will always flock to the latest update of android. And then subtly complain to the developer about the bugs they already know about..
Such a strange mixture of people...to be sure.
However what ive noticed here, is a complete lack of readily available information, so i am hoping some of you might be able to assist me.
TL;DR
So I succeeded in downgrading my phone from MM to LP, as the battery life thing is a legit problem for me, as much as it may not be for other people. However the fingerprint sensor has been disabled, and no longer exists in the settings list... nor is it part of the startup. (confusing to be sure, you would think it would be there, and just FC when clicking on it were there to be a bug, or if the OS didnt detect the sensor or something... it should still be there yeah? If i understand how it works...
Also I cant seem to flash a B151 rom at all, being on B33...3? <- marshmellow... and im assuming at this point that means i wasnt supposed to be able to downgrade... (oops)
So i got TWRP installed (whats up with all the random errors twrp is throwing? Assuming thats normal...?) and am awaiting a BMarshmellow rom to finish... Which leads me to...
Where are the Emui ROMS? Unless its closed... but if this rom maker can do it... ?
and also, is the fix to the battery life on marshmello noticable to those of you who also care about battery life at all?
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Demian3112 said:
Marshmallow battery is really bad compared to lollipop.. we had a BIG.little concept that worked great. But Huawei decided to make it a 8 Core CPU even when idle. If someone could make a kernal that activates the 4 BIG cores only when needed it would be approciated! Stock it runs almost always with 8 cores and the highest freq. This phone is really let down by poor software..
Click to expand...
Click to collapse
Well there is a fix for it in the mods section that fixes battery. Finally got this phone back to functional lol..
Anyway, the fix for the moment anyway looks like it works, just has to be redone every reboot but really isn't that hard. After applying mincores mincpu 0 the big cores only light up when necessary. So far its helping a lot with battery life at least noticeably. Listented to music the whole way to work this morning and was still at 97% when I got there (I have an hour drive) , and that's using Youtube Music over 4g.. Not too shabby.
Yesterday I got to work doing the same thing on marshmallow at about 85-90 so it is doing something, and watching Kernel Auditor shows the big cores turning off when not in use. Worth checking out, applying the settings that are mentioned there don't do much im afraid, as I cant get them to stick through a reboot yet.
Currently writing an init.d script to make that happen every boot.
For now to my knowledge though it is working. Though I think lollipop was for sure better apps on screen off actually worked properly -_-; which im noticing more and more it doesn't anymore. Its more like a Doze control which is annoying because Doze is not near as good as stock lollipop control. I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know!
TL;DR
I cant seem to revert back to lollipop and keep the fingerprint sensor though, if anyone figures that out please let me know! Id much rather downgrade than continue to fix marshmallow.
Though for those of you wondering, Viper|Atmos//Sony Beats the audio mod works perfectly on this phone
Just finished Init.d for Mincpus to fix the whole Big Little problem Super good stuff. Phone now booting in the big little mode you were talking about. super easy stuff.
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
skeppley said:
I also lost fingerprint when going back to lollipop. I'll let you know if i come up with any fixes for it.
Click to expand...
Click to collapse
U need the firmware had same.. revert though dload
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
You should try CyanogenMod 13: excellent battery life, USB OTG and gyro working, much better CPU & RAM management...
FP reader is working, but you must upgrade to MM first (to update trust zone and radio firmwares).
igotlostintampa said:
@Demian3112
So Dload for lollipop will revert back from Marshmallow and keep fingerprint reader? Interesting... Does the Dload relock the bootloader? Sorry for the somewhat noobish question, new.
Just looking through sys at the moment to understand the language used for big.little, seems to be a comma separation for them. Wondering if I can set min max this way and keep cores 4-7 at min freq 200000. Also looking for a way to get all big cores to disable when not in use, not just 3 of them which is the current.
Swap set to 0 in marshmellow, seems to speed the phone up a little.
testing Xposed here in a bit to get a few different features, debloated the phone, mostly normal stuff. Playing with other CPU files at the moment in root browser to see what I can do regarding the power draw from the CPU...
set SElinux to permissive to allow for proper audio playback through Viper//Atmos//Sony//Beats...Found Multiwindow, enabling that soon, don't know why it was ever disabled?
Otherwise mostly enjoying the phone at the moment, still above 80% battery with all this that im doing and im half way through my day. the CPU thing really helped with the battery draw.
Click to expand...
Click to collapse
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Demian3112 said:
Anymore u tried? I posted that script but still EMUI is an heavy OS im waiting for CM to be abit more stable. U can revert back to LP using a local update though dload. I did it aswell when my phone was bricked. Fp is not working because u miss the firmware
Click to expand...
Click to collapse
Demian3112 said:
It stays unlocked.. u Miss firmware thats why it doesnt work get stock firmware for your device and it should work not sure how you reverted.. keep in mind u will lose all data and stuff.
Click to expand...
Click to collapse
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on your bed at night? And then never again?
As for CM13, im fairly apathetic to the topic... Not to be annoying, or rude, but ive heard the excellent battery life claim a million times about stock android, and while ive noticed its improvements over something like...say, Sense, or Touchwiz... Ive never seen it beat the z3's battery saving tool (before marshmallow), or as of the day I got this phone, Huaweis non-debloated lollipop.
Ive never seen a phone still be at 30-40%, at the end of work, the day after the day I charged. Until this phone. The Z3 would make it a little past lunch if I barely used it on day 2, but this phone played pokemon go for 2 hours the day I charged it, I spent the day listening to streaming music, browsing for various small things, watching a few youtube videos, a little navigation... And it had 40% when I left work the next day lol at 100% auto brightness. Id love to see some screen on vs idle drain comparisons between this phones CM13 and Stock, at that point, ill believe a battery claim.
It played pokemon go at 60fps and the game is a known battery/gpu hog (s7 plays slower than this phone, likely due to lack of gyroscope?)
other than some various laggy UI glitches, the phone was pretty much what id been looking for (I Prefer Miui over stock android, this phone is similar)
igotlostintampa said:
Oh of course, I loose data all the time anyway so im used to that flash far too often to be healthy.
I reverted via a twrp backup, used emergency data recovery to factory reset using stock recovery, then it let me boot into lollipop, just missing that all important fingerprint reader//navigation tool. Will most def do that soon, at 60% :/ not sure where the random drain came from. just an hour later and lost 20%? Has to have to do with Screen off app closing. Huawei probably did the lazy thing and just changed over from their own tools to doze I guess that helps while its on yuur bed at night? And then never again?
Click to expand...
Click to collapse
What buildnumber and Custom version/Cust do you have? Might be able to link you the right firmware.. twrp backup doesnt backup firmware that explains that you dont have a finger print, is the H from Honor at boot logo Red also?
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
skeppley said:
I got it all sorted fellas.
Went to the 5X Repository. Downloaded the Stock 1.51 firmware. Placed the "update.app" from it under "dload" on sd card.
Opened up SuperSU on phone and went to settings to remove root and reboot.
After reboot hooked phone to computer and adb flashed the stock 1.51 recovery found in the repository. "same method as flashing twrp, only use 1.51 recovery.img instead"
Reboot phone again and then powered off.
Hold Volume up/down and power to restart and it updates form the 1.51 stock firmware on the SD card WIPING ALL DATA.
Now fingerprint and all factory settings are restored!
Thanks to all, and hope this helps others coming back from Marshmallow or CM13 like i did.
Click to expand...
Click to collapse
Your Reply has been added to the OP for those concerned with Downgrading. Figured it might be nice to stumble upon the directions that, after reading many posts throughout the various roms, many people might actually be looking for. Will likely try this tonight when I get home, battery is much better with the battery fix, but not as good as lolipop
Great.
Hope to help others that were stuck the same way
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Demian3112 said:
@igotlostintampa flashed CM13 today.. Im sold on this device i would suggest you to upgrade aswell.. Everything works no bugs so far and its smooth as hell. Battery is insane.. Every core has a task and with normal use it doesnt even scale above 800mhz and the other 4 are offline all the time only when needed they get activated.. Since 1PM i lost only 20% battery (Im on 23 now) while i was installing CM also.. Deffinitaly recommended
Click to expand...
Click to collapse
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
igotlostintampa said:
Alright so question for you, im interested in that CM13 seems to be using the big little concept we have been speaking about...
((Marshmellow Big.Little Fix does not function properly. It resets without reboot being required, just takes longer to apply than the core modifications under smart power saving, init.d through kernel auditor on smart battery saving mode does not run script on boot, must be manually executed))
Does the CM13 Fingerprint reader allow you to pull down notifications? Will likely check it out, interested... Also, how about a screen off task killer? Is that present... Looking through its forums.
Click to expand...
Click to collapse
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Demian3112 said:
No fingerprint pull down.. No gestures for it yet. No off screen taskkiler but thats fine its stock android you will have enough memory spare.. Got 10 apps open right now no issue and u can instant change to one. CPU is tweaked already with kernal adiutor u can turn off cores manually and tweak it to what ever you like.. Day 2 of using battery is better.. ALOT smoother u can switch from app in a instant no waiting time at all. If u have any questions just ask it. Rom is stable enough for daily use no bugs so far!
Click to expand...
Click to collapse
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
igotlostintampa said:
Ah see im not worried about memory usage, I never run low on a stock rom in the first place. Stock android has this problem where it allows some apps to sit open eating battery life when the screen is off. Instances of this include facebook, Google maps, general overall "Wakelocks" not present inside of the stock Huawei rom, that prevent the phone from going to sleep even though they aren't doing anything. The off screen task killer is there to close apps hogging battery life in the background that should have turned off when they weren't needed but didnt, after your screen turns off. For the most part this is the cause of the smoothness that you feel inside of a rom. Its going to be smooth because none of the apps are ever turning off, its a balance scale.
Not a big problem, I don't mind fixing that its really easy lol, just curious. As for the gestures that's a little disappointing.. It just seems like I may have to add a bit, but I can try it before I run over to lollistock, ill test it out today. You've convinced me with a claim of good battery though lol, and your previous comments about marshmallow, don't let me down!
Click to expand...
Click to collapse
Im using Force doze app.. U can whitelist apps and as soon as you turnoff your screen it starts doze... You wont get notifications from apps you didnt whitelist until you turn it back on
This is a very powerful mod that changes the brightness of the Xperia flashlight / torch.
This can cause damage if left on for extended periods of time. It is advised you install the medium version.
Source
Pre-Caution:
I take no responsibility to any burnt hands, burnt phones, or bricked phones. The chances of getting into a brick or bootloop is very low and I will aid you as much as possible, but will take no responsibility for this happening.
CAUTION:
The extreme version sets the torch to 1,000,000 Ua - in other words, its basically an industrial flashlight now, meaning it will get very hot, very quickly. Please take caution with using the extreme version.
DOWNLOAD:
Medium
Extreme
Uninstaller
SmarTemperature (To increase the temperature limit)
Installation:
1. Have a rooted device with /system access (So not the temp root method)
2. Download and move one of the zips to your SD Card
3. Enter recovery and backup your phone (Incase you want to revert back to default values)
4. Flash the Torch ZIP, and then flash the SmarTemperature ZIP
5. Enjoy!
Code:
# LED If setting for Indicator(uA)
if_indicator_level = 4125
# LED If setting for Torch or video recording (uA).
if_torch_vr = 500000
# Vf measured at factory (mV).
vf_factory = 2869
# Min voltage for VBat (mV)
v_batt_min = 3500
This mod works by modifying /etc/flashled_calc_parameters.cfg with custom values
NOTE:Take caution if you plan to modify this config file yourself.
XDA:DevDB Information
Xperia Brighter Torch Mod, Tool/Utility for the Sony Xperia Z5 Compact
Contributors
nzzane
Version Information
Status: Stable
Current Stable Version: V2
Stable Release Date: 2016-10-04
Created 2016-10-03
Last Updated 2016-11-22
Reserved:
My device shutdown when turning on the LED on medium, could you provide the initial value please?
raphoun said:
My device shutdown when turning on the LED on medium, could you provide the initial value please?
Click to expand...
Click to collapse
What firmware are you on & what Kernel are you using?
I have updated the OP with the first few lines of code for the medium version - as well as adding an uninstaller zip
nzzane said:
What firmware are you on & what Kernel are you using?
I have updated the OP with the first few lines of code for the medium version - as well as adding an uninstaller zip
Click to expand...
Click to collapse
The last firmware with OM5Z kernel. Thanks for the uninstaller
raphoun said:
The last firmware with OM5Z kernel. Thanks for the uninstaller
Click to expand...
Click to collapse
Very weird, do you still have "Allow OEM Unlock" enabled?
I am having the same issue here...
I am on Xpower 5.0 androplus kernel and it also happened on previous kernel... what could be the problem?
mine shutting down to , last stock rooted rom
If someone can find where the temp warning config file is, I will update this mod with that in.
i have tried to increase the temp warning temp but it has failed..
nzzane said:
If someone can find where the temp warning config file is, I will update this mod with that in.
i have tried to increase the temp warning temp but it has failed..
Click to expand...
Click to collapse
i dont think its the temp warning because my device doesnt over heat at all it just turns off...
if it was temp warning then it should get hot first then shut down am I right or ?
hey every one I just found this :
http://forum.xda-developers.com/xpe...-smartemperaturex-best-balanced-s810-t3438890
smartemp mod fixed my issue! had the extreme mod installed and turned on for couple of minutes , no shut down no warnings and also device doesnt even heat after the first couple of minutes on EXTREME TORCH
hope it works for you guys
@Gewiz told me about this so credit for him
madshark2009 said:
i dont think its the temp warning because my device doesnt over heat at all it just turns off...
if it was temp warning then it should get hot first then shut down am I right or ?
Click to expand...
Click to collapse
From what I have seen. The device, for Some reason, detects that it is heating quickly even thought it's not. This prompts the over heating warning.
It could be that the phone has a procedure in place to stop modification of the flashlight, but I have not seen this yet
madshark2009 said:
hey every one I just found this :
http://forum.xda-developers.com/xpe...-smartemperaturex-best-balanced-s810-t3438890
smartemp mod fixed my issue! had the extreme mod installed and turned on for couple of minutes , no shut down no warnings and also device doesnt even heat after the first couple of minutes on EXTREME TORCH
hope it works for you guys
@Gewiz told me about this so credit for him
Click to expand...
Click to collapse
Thanks, will add this to the OP
Hi, first of all, sorry in advance if it is a stupid post, I am no developer. Is it possible that everybody is running an extreme version and getting thermal problems because of a typo? I ve tried this mod (the medium version), and read the thread.
I opened the default configuration file, and compared it to the same file in the zip.
Two values change:
___________________default_____Medium________Extreme
if_indicator_level = _____3125_______4125___________5125
if_torch_vr = _________25000_____500000_________1000000
Isn't that strange? In the medium and the extreme versions, the indicator current is increased by 30% and 60% respectively, but the flash led's current goes from 25k to 500k and 1 million
The values seem to be in μA, that makes the default value of 25.000μA equal to 25mA, which seems about right for a led.
I ve modified the medium vetsion to the value "if_torch_vr =50.000 instead of 500.000. No shutdown, but I cannot judge how bright it is right now.
argotera said:
Hi, first of all, sorry in advance if it is a stupid post, I am no developer. Is it possible that everybody is running an extreme version and getting thermal problems because of a typo? I ve tried this mod (the medium version), and read the thread.
I opened the default configuration file, and compared it to the same file in the zip.
Two values change:
___________________default_____Medium________Extreme
if_indicator_level = _____3125_______4125___________5125
if_torch_vr = _________25000_____500000_________1000000
Isn't that strange? In the medium and the extreme versions, the indicator current is increased by 30% and 60% respectively, but the flash led's current goes from 25k to 500k and 1 million
The values seem to be in μA, that makes the default value of 25.000μA equal to 25mA, which seems about right for a led.
I ve modified the medium vetsion to the value "if_torch_vr =50.000 instead of 500.000. No shutdown, but I cannot judge how bright it is right now.
Click to expand...
Click to collapse
Hey, not a stupid post - So with the Z5 series they have a pretty low thermal limit, so thats why it is so retarded and shuts down, unless you have flashed the thermal limit raiser. (created for the purpose of the z5 thermal limit being so low)
Let me know if you notice a change in brightness, as the I may have miss-typed some of the code
Hi, I haven't looked it since.
I did not want to try that thermal mod. The posts on its thread weren't very encouraging. Decided to leave it set at if_torch_vr =50000
I can test again with other values but it won't be in the next days. Probably when I decide to jump to nougat
The Medium mod send my phone in temperature protection, if someone have Xposed try this module to increase the temperature limit
http://repo.xposed.info/module/michele2.thermal.disabler
Edit:
The module does not solve the problem, after a minute with the LED on the Z5c turns off after a temperature warning message.
cioce said:
The Medium mod send my phone in temperature protection, if someone have Xposed try this module to increase the temperature limit
http://repo.xposed.info/module/michele2.thermal.disabler
Edit:
The module does not solve the problem, after a minute with the LED on the Z5c turns off after a temperature warning message.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=69743947&postcount=11
Did you tried that? I recommend v1.6.1
EDIT
WORKING FOR FEW SEC AND SHUTTING DOWN!
on my 1.54
im using green kernel for stock rom
Links dead, reupload? Thanks