This mod fixes the cell standby values in the power profile for stock roms. this will be apparent when your cell radio is off (wifi is on, or background data is off), the cell standby will report higher than normal usage).
CM 10 is based off of the sgs2 and uses it's power profile values (at least it did last time I checked) so you don't need to flash this. most custom roms include this fix so you don't need it.
Installation:
Reboot to recovery
Make a backup of your phone (I'm not responsible for bricks)
Flash the zip file
Reboot
Files:
CWM-ModStandby.1.0.zip (based on the stock UVALEM framework res apk)
CWM-ModStandby.2.0.zip (based on the stock UVALH2 framework res apk)
CWM-ModStandby.3.0.zip (based on the stock UVALJ4 framework res apk)
if you don't want to use the cwm update zip or have a stock build other than one of the ones listed above and / or want to apply the fix yourself, you can do that bydoing the following the manual update steps:
Manual Update:
download this apktool set and extract it somewhere simple like c:\apktools.
copy your framework.res.apk from your /system/framework folder to your computer to the c:\apktools folder
rename apktool.jar.1.4.2 apktool.jar
open a command window and run the following commands
java -jar apktool.jar if framework-res.apk
java -jar apktool.jar d framework-res.apk
browse the decompiled folder structure to your res/xml folder and locate your power_profile.xml file
edit it in notepad/notepad++
locate the device/array[name=radio.on]/value node (there will be two of these)
change the value from 34, to 3.4
save
rename apktool.jar back to apktool.jar.1.4.2 and rename apktool.jar.1.4.3 to apktool.jar
back in the command window recompile the framework.res.apk by issuing the command:
java -jar apktool.jar b framework-res (this will likely display a lot of warnings about "no default translation yatta, yatta" which is fine)
this will re-compile your edited power_profile.xml file and place it in your c:\apktools\framework-res\dist folder (assuming you put things in this default folder)
open this file with winrar or 7zip (DO NOT EXTRACT IT) and pull out the compile the power_profile.xml file
open your original framework-res.apk (AGAIN, DO NOT EXTRACT) with winrar or 7zip, browse to res/xml, and drag the newly compiled power_profile.xml file (the one that you just pulled out of the newly compiled framework-res.apk. you can't use the one you just compiled as its missing all the important files that we didn't really extract) over on top of the existing power_profile.xml file inside the winrar window. this will replace the existing erred compiled power profile with the fixed one, and winrar will re-save it.
now reboot to recovery, adb shell, mount system, rename your existing framework-res.apk, copy this modified one over, then reboot. If you can't adb you can always take one of the cwm files I've posted, open it in winrar (open, don't extract it) browse to the /system/framework folder, and drag your new framework-res.apk over the top of the existing file and let winrar update the zip file. then flash that updated file on your phone (remembering to make a nandroid first just in case).
If you have another build that you'd like to include in a flashable form, send me your framework-res apk and I'll mod it and upload it up here.
almighty bob said:
First, I'm a pretty casual user (so if I've royally messed something up someone let me know, but I think I've got it all right), I came across the fix to this issue somewhere else (though I think the authors didn't document their source as coming from the intl. forum), created a fix for my phone, and came here to post the fix. I did a few searches to make sure nobody else had posted something similar when I noticed a few of the stock rom dev's have included it in their roms, so it looks like someone has also done a cwm fix for this at some point too, though nobody has one listed here in the tmo section (wish I had searched for it before making my own cwm installer).
anyway, as some of you may or may not know, the power profile for our phones has a pretty aggressive value in its settings for standby power consumption which drains the battery pretty fast when on standby. this fix sets it back down to a much lower value (similar to something the s2 uses) which results in a much better battery life.
I've been using it now for a while and noticed a pretty decent improvement.
As far as I know this'll just be for the stock tmobile roms, everybody else flash at your own risk.
Installation:
Reboot to recovery
Make a backup of your phone (I'm not responsible for bricks)
Flash the CWM-ModStandby.1.0.zip file
Reboot and enjoy some better battery life
Files:
CWM-ModStandby.1.0.zip
Click to expand...
Click to collapse
Thanks, just flashed. Let's hope this gets me through a day without charging!
almighty bob said:
First, I'm a pretty casual user (so if I've royally messed something up someone let me know, but I think I've got it all right), I came across the fix to this issue somewhere else (though I think the authors didn't document their source as coming from the intl. forum), created a fix for my phone, and came here to post the fix. I did a few searches to make sure nobody else had posted something similar when I noticed a few of the stock rom dev's have included it in their roms, so it looks like someone has also done a cwm fix for this at some point too, though nobody has one listed here in the tmo section (wish I had searched for it before making my own cwm installer).
anyway, as some of you may or may not know, the power profile for our phones has a pretty aggressive value in its settings for standby power consumption which drains the battery pretty fast when on standby. this fix sets it back down to a much lower value (similar to something the s2 uses) which results in a much better battery life.
I've been using it now for a while and noticed a pretty decent improvement.
As far as I know this'll just be for the stock tmobile roms, everybody else flash at your own risk.
Installation:
Reboot to recovery
Make a backup of your phone (I'm not responsible for bricks)
Flash the CWM-ModStandby.1.0.zip file
Reboot and enjoy some better battery life
Files:
CWM-ModStandby.1.0.zip
Click to expand...
Click to collapse
This DOES NOT improve battery life at all. This only changed the value for call standby calculation from 34 to 3.4 thus giving a more accurate reading of the cell standby usage.
Sent from my SGH-T999 using xda premium
I can confirm that this does not work on CM10
uoY_redruM said:
This DOES NOT improve battery life at all. This only changed the value for call standby calculation from 34 to 3.4 thus giving a more accurate reading of the cell standby usage.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
that's not completely true. if your drain rate is computed by cell standby, and cell standby reported way more power than it actually used, then your phone's going to show power loss at a greater rate than it actually is and you're going to end up charging it before you have to. Cell standby was the #1 draw on my phone every day until this was applied, now its way down on the list, so its had a pretty significant impact on the calculation of the draw on the battery stats.
this just puts the consumption settings where it should have been to begin with but the effect is that the phone appears to drain power slower (the way it should have, and actually did from the beginning but was falsely reporting with the original power settings).
solrac.dc said:
I can confirm that this does not work on CM10
Click to expand...
Click to collapse
Steve's already fixed this in CM10--has it set at 2.7 which I think was the settings used by the s2, which I don't think are exactly accurate given that the phone probably has a different power draw, but shouldn't make as much difference as 34->3.4 mA.
Does the tmobile variant really have the stand by power drain issue? I am running stock rooted debloated and see a sample below. This is with wifi always on, background data sync on, 3 emails and 4 widgets and spotty cell reception. I would like to flash this if there is really a standby issue, but doesn't seem like it.
{
"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"
}
Sent from my SGH-T999
yea, cell standby shouldn't be reporting that high of usage. that's what first got me wondering about this to begin with.
It should look something like this:
almighty bob said:
yea, cell standby shouldn't be reporting that high of usage. that's what first got me wondering about this to begin with.
It should look something like this:
Click to expand...
Click to collapse
My point is when the phone was on standby for 8 hours it drained only 2%. How can we check if the value is really set to 34 instead of 3.4 because in stock mode i don't really see big standby drain. I read that happened only for the international model.
Sent from my SGH-T999
Fixed mines. It's reading accurate now. It was at 17 hrs forever.
Sent from my SGH-T999 using Tapatalk 2
rakeshchn said:
My point is when the phone was on standby for 8 hours it drained only 2%. How can we check if the value is really set to 34 instead of 3.4 because in stock mode i don't really see big standby drain. I read that happened only for the international model.
Sent from my SGH-T999
Click to expand...
Click to collapse
yea but your cell standby in that screenshot there is 76%, which it shouldn't ever be. 2-5% is closer to what it should be.
you can copy your /system/framework/framework-res.apk from off your phone to your pc. open it with winrar, and browse to /res/xml/power_profile.xml and right click the file and select "view" the xml file is compiled inside the apk, but look for the "radio.on value which is set to 34 in the stock roms and will be set to 3.4 after this patch (my patch renames your old framework-res.apk to framework-res.apk.back if you want to compare the two files after the fact).
rakeshchn said:
My point is when the phone was on standby for 8 hours it drained only 2%. How can we check if the value is really set to 34 instead of 3.4 because in stock mode i don't really see big standby drain. I read that happened only for the international model.
Click to expand...
Click to collapse
Seriously, if you only lost 2% in over 8 hours, I wouldn't touch a thing on your phone.
I find it hard to believe those numbers, however.
overground said:
Seriously, if you only lost 2% in over 8 hours, I wouldn't touch a thing on your phone.
I find it hard to believe those numbers, however.
Click to expand...
Click to collapse
Best I got was 5% in 8 hours with it sitting overnight
Anyway i will just try this coz when i checked framework apk its 34 mv. Can this be flashed in TWRP recovery, or only CWM?
rakeshchn said:
Anyway i will just try this coz when i checked framework apk its 34 mv. Can this be flashed in TWRP recovery, or only CWM?
Click to expand...
Click to collapse
Either works fine.
While it's a nice gesture to release this to everyone, I strongly suggest not giving false hopes of increased battery life with this.
All this fixes is the read out for cell standby. It does not increase battery life.
Sent from my SGH-T999 using xda premium
uoY_redruM said:
While it's a nice gesture to release this to everyone, I strongly suggest not giving false hopes of increased battery life with this.
All this fixes is the read out for cell standby. It does not increase battery life.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
well after about 8 hours my phone was red-lined (I never go on wifi @ work) before the fix since the day I bought it. after the patch (if I charge according to the readout on the phone, which is what its there for IMO), I usually plug it in before I got to bed after about 14-16 hrs (hitting wifi @ home levels out the power usage counters).
so either I'm confused about the purpose of the power consumption counters, and how I should use them to base my phone charging, the phone is, or you are, because the phone is staying on (it's not cutting off suddenly when it says it's still got 30% left on charge), the counters are where they should be, and I'm not charging as frequently, so unless you can spell it out a bit clearer, I'm leaving it at that.
fact is, the power consumption of the radio standby isn't 34mA. the system that computes battery consumption (ohms law) uses that to tell you when to plug in and amp up, and if the value of one of the stats is off, then yea, you're going around thinking your phone is draining like crazy when it isn't. with this fix, you'll be closer to where it *should* be assuming the mfg got the math right for the hardware they put in here.
so unless you have some better explanation for the purpose of the power profile of individual systems, the os keeping track of the battery consumption and an order of a magnitude power loss in the radio standby calculation than that, then yea, they're getting "better battery life" IMO whether its just a matter of perception (now that the system is just calculating it correctly now) or not.
i just hate seeing standby at 27% so it made me happy.:laugh:
I'm going to put it to the real test soon by completely draining the battery and then recharging. I'll post a screen when I get done with it. I'm at 21% right now so I'll just turn everything on and kill the battery.
Sent from my Samsung Galaxy SIII
Now my stats won't reset. I unplug my phone and it still says 10 hrs on battery. Shouldn't change immediately to 1 sec?
Sent from my SGH-T999 using Tapatalk 2
were you on the battery screen when you unplugged? you have to hit the refresh button.
Related
This is a formal request for any developer capable of doing so, to take a look at this problem.
There is a growing number of users noticing a severe battery drain and hot phone at times, caused by the runaway process; (gsiff_daemon)
The threads discussing this as of now are scattered and unorganized, and with the number of users experiencing this problem, it would be excellent to have one central thread for everyone to work together on this.
Here's what we know so far:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
It is not carrier specific, At&t, Tmobile, and Verizon users have all confirmed this problem.
The only reliable way to rid of this at this time, is a reboot, although some have had luck ending the gsiff_daemon process, or renaming the file, although this requires further testing.
Here are a few threads that have been started on the issue, with some good reading:
http://forum.xda-developers.com/showthread.php?p=30074303#post30074303
http://forum.xda-developers.com/showthread.php?t=1800812&page=3
Anyone capable of looking into this, and know what they are looking at enough to determine the cause, will be eternally thanked, and i will personally donate a case of beer(or soda) to whoever fixes it.
Thanks!
is this Gsiff_Daemon issue only for rooted users? I just got it too...after rooting...I never had this issue since june 30, since I've had the phone
I just renamed the file.. problem went away. it doesn't run anymore.. and haven't had any negative effects that I can tell....
do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app
tjb433 said:
The problem occurs for most on a hot-boot, and can be triggered by forcing a hot-boot.
Click to expand...
Click to collapse
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.
themadproducer said:
FULL REPORT
HARDWARE and OS
I747m, Stock LH1 4.0.4, Rooted
SOFTWARE
SetCpu 384-1512mhz OnDemand
System Tuner Pro 2.5.5 (STP)
Rebooter 1.6.0, Author: DAVIDJR621
BetterBatteryStats 1.11.0.0
Battery: /menu/settings/battery/
NORMAL OPERATION
- Reboot normally until system settles in fully loaded and in idle
- check SetCpu. Scaling should hover at 384mhz and with occasional spikes usually up to 1512.
- check BetterBatteryStats, switch top drop down selection to "Process" and secondary selection to "Since Unplugged". "gsiff_daemon" should NOT be listed there
REPRODUCING THE ISSUE
- Open Rebooter app and launch the HOT REBOOT option and wait for the system to reboot and settle.
- Open SetCpu and you should notice that the scaler will be at 1512mhz >90% of the time. IF NOT...repeat the hot reboot step.
- Open BetterBatteryStats as you did above and notice that "gsiff_daemon" is now listed in there.
- Open Battery info and notice that ANDROID SYSTEM is at the top of the list usually around 60%. Now STARE at Android system and click the refresh button...and notice for a brief Milli Second you will see,,,,"gsiff_daemon". Not sure about this but interesting.
- Open STP, launch it's built in Task Manager, make sure you allow viewing of SYSTEM and KERNEL. (at the bottom you can click on their ICONS) Scroll down near the bottom third of the list where it shows KERNEL elements, and you will see /system/bin/gsiff_daemon. Click on /system/bin/gsiff_daemon. Under CPU Consumption....you can watch the % climb.
- at this point, if you KILL /system/bin/gsiff_daemon, the CPU will settle back down to 384mhz and the statistics of cpu usage will not climb/grow.
WORKAROUNDS
- kill /system/bin/gsiff_daemon/ after a hot reboot or reboot your S3
- with a Root File Explorer, rename your /system/bin/gsiff_daemon to /system/bin/gsiff_daemonBAK and reboot normally. This should prevent the issue but it is not known whether it is adversely affecting any system components.
- /system/bin/gsiff_daemon/ should not show up in STP if you have renamed the file.
Click to expand...
Click to collapse
isn'ttthere a period before bak?
eyecon82 said:
Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).
78c10 said:
What JB ROM are you using? I had the issue when I was running stock, rooted, with the Sammy KT747 kernel, but after flashing CM10, landing the AOKP KT747 Kernel, and running Pimp My ROM on it, I've never seen it crop back up. (knocking on wood here).
Click to expand...
Click to collapse
I am using rooted stock rom
This is only an issue with touchwiz, so you won't see it on cm10
Sent from my SPH-L710 using xda app-developers app
eyecon82 said:
isn'ttthere a period before bak?
Click to expand...
Click to collapse
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.
themadproducer said:
NOPE!
Specifically though, I used uppercase BAK....doubt that makes a difference.
Click to expand...
Click to collapse
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though
eyecon82 said:
What is the difference of having or not having a period?
Upper casing probably doesn't make a difference though
Click to expand...
Click to collapse
Eyecon82...really...don't worry about the period. It's irrelevant.
So long is the file is renamed, it wont be triggered/found by whatever normally triggers/finds it.
http://pastebin.com/siAGdxp4
It looks like it's sending gyroscope and accelerometer data to the locapi, (location application interface) and there's some reference to sns there as well.
So, why would a location app need accelerometer data? Or maybe the question is why would someone who's getting my location data need my accelerometer data, too? What's in it for Samsung that they would bother developing it and roll it out? Why wasn't it there in June?
Ok, having a little fun speculating, but perhaps blackboxing for car accidents? Your phone log is the first thing they check and see if you were texting, or whatever, right before impact. Oh, wait, if they have a location-accessing app, they don't need your locally stored log. Nah, probably something technical with the compass....
Janis;34345281It looks like it's sending gyroscope and accelerometer data to the locapi said:
Yes, I don't have any evidence to support this other than what just happened on my phone. I was out for about a 15 minute walk and I got back. Phone was hot and i noticed a severe drop in battery. I remember reading that Goog Now tabulates how far you walked/jogged monthly or something. Maybe this process is capturing that motion/data for it? Just my speculation. No evidence. I think I'll try renaming the file as I dont really GAF about how far Goog thinks I've walked.
Click to expand...
Click to collapse
I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file
harryshepard said:
I am having this issue. I've just rooted my phone and the file seems to no longer be in /system/bin and running a search for it the file isn't found. Yet it's completely killing my battery. It's quite annoying to have to monitor battery use and kill this off or restart the phone so renaming it would be nice to disable it fully but I can't seem to find the file
Click to expand...
Click to collapse
You sure it's gsiff_daemon that's causing the issue? Have you renaming qosmgr in system/bin?
Sent from my SGH-I747 using Tapatalk 2
Sorry, didn't have reply notification. Yes I am sure. I Google'd it after seeing it using 30% of my battery with about 50s use. I will try renaming qosmgr but how do you diagnose which process is actually doing it? This time battery doesn't specifically say gsiff_daemon but not sure if that's where I saw it before.
I have attached my battery use screenshot. Game and screen a the top, fair enough. But 13 hours on battery and 75% drained, 6% of which is 7 seconds of the gpsd process. It's a little odd
Sent from my GT-I9300 using xda app-developers app
fix yet ? mines doing same
gsiff_daemon
Mine has been doing the same ever since the kitkat update.
I am running an unrooted EE note 3 (n9005) in the UK.
Gsiff_daemon is constantly my top battery drainer according to the battery app (35% - 47%).
I have not been able to find any consistent method to either activate this rogue app or to get rid of it.
Is there any solution without rooting it as I understand that renaming it should do the trick?
+1 from me about this problem.
Uprooted, up to date Note 3.
No solution so far, will try turning off WiFi when screen off and auto rotation... Let's see...
Hopefully it'll be fixed soon or in next version. It's a shame, though, my Windows phone pals are teasing me!
Best regards,
Doncho
On my new phone battery lasts for only 6 hours even if I don't use it (the phone is in the sleep). Battery lasts for same time if I use or don't use the phone. I did hard reset and nothing has changed. There are only few apps installed on the phone. What could be the problem?
When you first got the phone, you should charge it for 8 hours to check the battery.
Sent from my LT18i using xda app-developers app
you should charge and use it until 0% for about 3,4times
if it still drains,then you should ask again.
try using app called "battery mix" and post us screenshot.
popthosegaskets said:
When you first got the phone, you should charge it for 8 hours to check the battery.
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Bull****.
#licorice said:
you should charge and use it until 0% for about 3,4times
if it still drains,then you should ask again.
try using app called "battery mix" and post us screenshot.
Click to expand...
Click to collapse
Bull****.
Guys, you really need to learn about the Li type batteries, that are used in phones. These are old myths, that do not apply to our phones anymore.
Sent from my Xperia Arc S using xda premium
Someguyfromhell said:
Guys, you really need to learn about the Li type batteries, that are used in phones. These are old myths, that do not apply to our phones anymore.
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Finnaly someone with common sense. In no user manuals for last 10 years havent I seen an instruction to charge and discharge to 0% three times. If anyone noticed, these new batteries come precharged already, you can just put it in the cell phone and make some calls. It won't damage the battery at all.
How about we focus on the real question here, and find out, what are android phones are doing, that is so important, that it keeps them awake at night? Just today, i charged my cell phone to 100% around 1am, and after I woke up at 9 with 57% of battery left, because Android System kept the phone awake 5h 53m out of 5h 54m on battery.
Packages included:
Key Chain
CredentialManagerService_1_5
HDMI
Settings
System UI
AudioEffectService
Google Backup Transport
Settings Storage
Android System
FmRxService
So all these things seem to be very important, because they need to run in foreground all the time (so it seems)
@Dadovvv: check settings/battery to see what is using your battery the most.
issak42 said:
Finnaly someone with common sense. In no user manuals for last 10 years havent I seen an instruction to charge and discharge to 0% three times. If anyone noticed, these new batteries come precharged already, you can just put it in the cell phone and make some calls. It won't damage the battery at all.
How about we focus on the real question here, and find out, what are android phones are doing, that is so important, that it keeps them awake at night? Just today, i charged my cell phone to 100% around 1am, and after I woke up at 9 with 57% of battery left, because Android System kept the phone awake 5h 53m out of 5h 54m on battery.
Packages included:
Key Chain
CredentialManagerService_1_5
HDMI
Settings
System UI
AudioEffectService
Google Backup Transport
Settings Storage
Android System
FmRxService
So all these things seem to be very important, because they need to run in foreground all the time (so it seems)
@Dadovvv: check settings/battery to see what is using your battery the most.
Click to expand...
Click to collapse
Tnx for rply and help..
Yesterday i make reflash using pc, all fresh installed without installing any apps and gmail acount default settings... i put all night to charg battery, at 06,00 AM disconnected from charger and leave phone in standbay..i am now at work and in 07,00 PM ill check phone and ill post picture and info..
sry for bad eng
Ok so here is update....
Phone is 12 hrs in standby without touching
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will suggest NOT TO USE all those apps on market that promise battery saving cause they usually drain much more energy themselves. So on ics go to developer options in settings and tick third option from bottom (killing unused processes ASAP) and use task manager (hold home button a bit until recent apps show) then swype and kill them. If all this doesnt fix it buy new battery
Edit: so i saw on screenshots gingerbread, i suggest upgrading to ics. Its free and better os. But i also see that you should replace battery
DjDexter5GHz said:
I will suggest NOT TO USE all those apps on market that promise battery saving cause they usually drain much more energy themselves. So on ics go to developer options in settings and tick third option from bottom (killing unused processes ASAP) and use task manager (hold home button a bit until recent apps show) then swype and kill them. If all this doesnt fix it buy new battery
Edit: so i saw on screenshots gingerbread, i suggest upgrading to ics. Its free and better os. But i also see that you should replace battery
Click to expand...
Click to collapse
Ty.. How do you mean Gingerbread, I updatead to newest software (ICS)? I haven't installed any app from market. Phone is one month old. Please read my posts, I have explained everything..
Wow i am an idiot, but that doesnt change fact that you need new battery
ICS has a bug in its firmware, that causes Android OS or Android System to drain battery.
To avoid it, Restart your phone after every charging!
DjDexter5GHz said:
Wow i am an idiot, but that doesnt change fact that you need new battery
Click to expand...
Click to collapse
Ok..i tried another battery from a friend and still drain.
tnx
Someguyfromhell said:
ICS has a bug in its firmware, that causes Android OS or Android System to drain battery.
To avoid it, Restart your phone after every charging!
Click to expand...
Click to collapse
i agree that ics has a bug in firmaware..i tried and restart and same drain.
u think that the warranty applies to this case?
I dont know what you people are talking. In my case battery lasts at least 2 days even when i listen to music at least 3 hours a day and use wi-fi almost all day...
Using ICS 4.0.4 rooted stock rom (bloatware removed)
DjDexter5GHz said:
I dont know what you people are talking. In my case battery lasts at least 2 days even when i listen to music at least 3 hours a day and use wi-fi almost all day...
Using ICS 4.0.4 rooted stock rom (bloatware removed)
Click to expand...
Click to collapse
what release are u using? is it this one?
LT18i_4.1.B.0.431_Generic World Greece
cause im using this one aswell and i never manage to get 2 days out of it with heavy use...
Actually i dont know, how do i check that? (i think it is Nordic but not sure)
I think you can only check that in the filename of ftf that you flashed
@Dadovvv: Since the cell standby wastes a lot of energy, it may be, that you are on border of two cells, and your cell phone is constantly switching between them. Just for testing purposes, switch on airplane mode, and re-do the test (untouched cell phone until battery dies).
issak42 said:
I think you can only check that in the filename of ftf that you flashed
@Dadovvv: Since the cell standby wastes a lot of energy, it may be, that you are on border of two cells, and your cell phone is constantly switching between them. Just for testing purposes, switch on airplane mode, and re-do the test (untouched cell phone until battery dies).
Click to expand...
Click to collapse
I flashed Xperia Arc (LT18i)_4.0.2.A.0.42_CE.ftf and than updated to 4.0.4
(i have no idea what it is)
And nice idea for airplane mode test!
I decided to send mobile to repair.
To see, what uses the battery, you can also use BetterBatteryStats. Very useful app, shows a lot of info about the usage.
Search it on xda.
Sent from my Xperia Arc S using xda premium
Hey guys,
this thread is supposed to show you exactly, how you can change the charging voltage and charging current of the Xiaomi Redmi 5 Plus (vince). This could very well also work with other phones, as I first heard of them in a Magisk module, NOT related to this phone. This is my first thread on xda and I'm not a native speaker, so please excuse mistakes
So, there are two files associated with the kernel, that control voltage and current. For most kernels for vince, these files exist (DA, Zucc, Genom, and maybe also the others... doesn't work on Kirks Kernel) at the moment. Of course I don't know if these files still exist when a new android version is brought to this phone ^^
So let's start. The two files I mentioned are located here:
Current: /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Voltage: /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/voltage_max
For Linux 3.18 Kernels:
Current: /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max (stock value: 2000000 = 2000mA)
Voltage: /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/voltage_max (stock value: 4380 = 4,38V)
The values in constant_charge_current_max are measured in mA/1000. So that means, if you want to set 2000mA, you have to type 2000000 in this file.
The values in voltage_max are in mV, so if you want to set for example 4,2V as a maximum, you would have to type 4200 in this file.
MY RECOMMENDATIONS:
To set good values on these interfaces, we have to understand them correctly. Let's start with the voltage. The charging voltage (in order to charge) always has to be higher than the voltage the battery has. The battery of this specific phone ranges from 4,3V to 3,7V (4,3V on 100%, gradually going to 3,7V when reaching 0% (not sure about the 3,7V, correct me if you can )). I wouldn't change it. The voltage needs to be 4380 mA if you want you phone to charge until it's full. Even if you don't want that, I'd take another way to stop your phone from charging any further (there are good magisk modules that do exactly that, even with more features).
Now let's speak about the charging current, the holy grail of charging haha :laugh: Basically, if you want faster charging, go with values higher than 2000mA. I'd take 2500mA max, as the battery can get very hot. If you want your phone to stay cool while charging, which causes the battery to last way longer (https://www.sciencedirect.com/science/article/abs/pii/S0378775314004352), I'd recommend finding a charging current which keeps your temperature at about 25°C, which is the optimal temperature (see the reference, it's not a long text). For me, this is 1850mA, but if you live somewhere where it's very cold or hot, this can vary significantly. In the end, this is personal preference and should depend on how long you want to keep your phone, and how important charging speed is to you.
As for all kernel or /sys values, these will be reset on every reboot, so you'll have to find a way to set in on every boot. I tried creating a init.d file, but even though I set the permissions of the init.d file etc, it failed every time. So personally, I use Custom Controls in Kernel Adiutor, but I think EXKM has something similar. Of course I can only show the way with Kernel Adiutor and FKM in the following, as I don't have EXKM.
How to set these values with Kernel Adiutor:
For this, you have to enable the Custom Controls in Kernel Adiutor settings, if you disabled it previously.
Let's start with the current:
Go in the Custom Controls menu, click on the + and then "create". For this type of value, we need a seekbar. The title is irrelevant really, I'd choose "Charging Current". As a min, choose 0, and as max, choose the exact same value you want to use (if you're still unsure, just take 2000000/2500000, depending on if you want to increase it or not). I do this, because it is very hard to get the seekbar to an exact value (for example 1850000), because the numbers are so high. So i just set the max to what I want, and just max out the seekbar.
In "Progress", you have to put in exactly this:
For 3.18 kernels:
#!/system/bin/sh
head /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max
Press test to confirm you typed it in correctly. Otherwise you also won't be able to set this control
in "Applying", put in exactly this:
#!/system/bin/sh
progress=$1
echo $progress > /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max
Don't forget to delete the # before the second line (progress=$1), otherwise this will set nothing.
For 4.9 kernels:
#!/system/bin/sh
head /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Press test to confirm you typed it in correctly. Otherwise you also won't be able to set this control
in "Applying", put in exactly this:
#!/system/bin/sh
progress=$1
echo $progress > /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Don't forget to delete the # before the second line (progress=$1), otherwise this will set nothing.
That's it, you can use this control now ^^ But if you want this to set on every boot, after setting it up, you have to click on the 3 dots of this control and check "On boot".
Basically, for the voltage, I'd take 0 as minimum, and 4400 as maximum, and change the file location to the voltage (on progress and applying), and the rest is the same!
So, that's it! It's possible that someone will write a magisk module for that some day, but until then, I think this is a very easy solution. Have fun with it!
How to set these values with Franco Kernel Manager:
These screenshots are provided by @Niamotullah
{
"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"
}
Good job mate! Keep up the work!
8t really works and I get full control over charging speed now.
So i setup everything in kernel auditor and there is no save button besides in progress and applying fields, and when i press back button no custom control appears. Am i doing something wrong?
bot88 said:
So i setup everything in kernel auditor and there is no save button besides in progress and applying fields, and when i press back button no custom control appears. Am i doing something wrong?
Click to expand...
Click to collapse
Probably you didn't press "test" after typing in everything in "progress"
Doomkopf said:
Probably you didn't press "test" after typing in everything in "progress"
Click to expand...
Click to collapse
Yes i did press test but nothing shows up underneath.
I can't find files
mutlubas said:
I can't find files
Click to expand...
Click to collapse
What kernel and rom are you using?
bot88 said:
Yes i did press test but nothing shows up underneath.
Click to expand...
Click to collapse
Can you attach a screenshot? Can't help you this way ^^
Doomkopf said:
What kernel and rom are you using?
Click to expand...
Click to collapse
ı using global beta rom kirks kernel
mutlubas said:
ı using global beta rom kirks kernel
Click to expand...
Click to collapse
Then that kernel probably doesn't have those files, I'm sorry ^^ I'll add it to the thread so people know
Doomkopf said:
Then that kernel probably doesn't have those files, I'm sorry ^^ I'll add it to the thread so people know
Click to expand...
Click to collapse
Which kernel supports these files.
Can I set the charge rate with Kirks kernel kernel auditor
mutlubas said:
Which kernel supports these files.
Can I set the charge rate with Kirks kernel kernel auditor
Click to expand...
Click to collapse
Look at the OP. Zucc currently doesn't work, but it used to and the dev told me that he tries to implement it in the Linux 4.9 Kernel again.
With Genom and Dark Ages it works.
IDK about Kirks Kernel, never tried it. But you told me it doesn't work ^^ Check with your filemanager if you have those files please
Doomkopf said:
Can you attach a screenshot? Can't help you this way ^^
Click to expand...
Click to collapse
Sorry my bad, when i checked those files manually i figured the kernel "dark ages" i was using doesn't have those files, now I'm using "genom" kernel which is much better and stable. Also gives me default charging rate of 1800mah without modification of any files. After settings up this control 2500mah as maximum i tested different charging rates at different states of battery. As follows
34% = 2470mah
47% = 2240mah
69% = 1800mah
88% = 1430mah
96% = 836mah
4.2 volts in all states.
Given results are pure observation without any specific app made by just looking charging info given at lockscreen (feature provided by some custom ROMs in this case Havoc os2.1)
Thus i can't confirm if they are consistent throughout whole charging cycle.
Charger used: a third part charger rated at 5v 2.4amps.
You mileage may vary, my test also confirm that cables can also affect outcomes. Such as original one plus one cable from (1+1 first generation phone) does not go abve than 1500mah even when suitable charger is used. Only cable which works for me is a $15 cable i bought from store the other day, which is quite expensive but quality speaks for it self.
:good: :fingers-crossed: peace out
bot88 said:
Sorry my bad, when i checked those files manually i figured the kernel "dark ages" i was using doesn't have those files, now I'm using "genom" kernel which is much better and stable. Also gives me default charging rate of 1800mah without modification of any files. After settings up this control 2500mah as maximum i tested different charging rates at different states of battery. As follows
34% = 2470mah
47% = 2240mah
69% = 1800mah
88% = 1430mah
96% = 836mah
4.2 volts in all states.
Given results are pure observation without any specific app made by just looking charging info given at lockscreen (feature provided by some custom ROMs in this case Havoc os2.1)
Thus i can't confirm if they are consistent throughout whole charging cycle.
Charger used: a third part charger rated at 5v 2.4amps.
You mileage may vary, my test also confirm that cables can also affect outcomes. Such as original one plus one cable from (1+1 first generation phone) does not go abve than 1500mah even when suitable charger is used. Only cable which works for me is a $15 cable i bought from store the other day, which is quite expensive but quality speaks for it self.
:good: :fingers-crossed: peace out
Click to expand...
Click to collapse
Dark Ages doesn't have it? That's weird. I think I used lastest stable version and it worked
Yea, the problem is 4,2V I explained in my voltage recommendations why 4,2V is problematic. The voltage has to be a certain amount higher than the voltage of the battery (which I also mentioned in the OP). I'd recommend setting it to the standard, 4380(mV), so your battery charged faster when at higher percentages.
Wow, thank you very interesting information. True, I’m afraid to overclock the charge strongly so as not to squeeze the battery hard.
As you guys may have noticed, Linux 4.9 got ported to our device. It broke my setup (Kernel Adiutor said it can't get an integer value out of the file), but it still works! The symlinks got changed, so these are the new paths to the files:
/sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
/sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/voltage_max
Enjoy!
Is there any way to do this thing without root ?
Maybe by changing some files through twrp and adb.?
tanuj_mehta said:
Is there any way to do this thing without root ?
Maybe by changing some files through twrp and adb.?
Click to expand...
Click to collapse
I'd say no, because those values always reset after a reboot so they shouldn't stick if you set it in twrp and reboot to your system Maybe there is a way, but I don't see one :/
Thanks.. it's really helps me..
I did it using franco kernel manager
Niamotullah said:
Thanks.. it's really helps me..
I did it using franco kernel manager
Click to expand...
Click to collapse
Thanks again for providing the screenshots! They have been added to the OP
My story
I have The Tencent version of the Asus rog phone 2, I mainly bought it for battery life, I am not a gamer.
I also saw that some users report about excellent battery life while others suffer from battery drain issues.
In reality the battery life was similar to my previous Samsung Galaxy S8 Plus which had half the battery capacity.
The SOT was around 4-6 hours and the phone drained around 5-8 percent of battery per hour when it was suppose to sleep.
I tried BBS (Better Battery Stats), GSAM etc.
Eventually I found a solution, this solution is relevant to me and may not apply to others but it's worth a shot.
My solution
First off, your phone must be rooted and on Android 9 version.
Download the Kernel by the brilliant @Freak07 from here:
https://forum.xda-developers.com/ro...rnel-kirisakura-1-0-0-asus-rog-phone-t4028237
Download EX Kernel Manager.
Go to Tools - Block Wakelocks and see what is waking your device.
In my case a process called qcom_rx_wakelock kept my device awake and murdered my battery.
With the help of @HomerSp we found that the reason for this is a device in my network that is sending packets over the network, there are 3 possible solutions:
1. For root users - Disable the qcom_rx_wakelock from the EX Kernel Manager program (This is what I did and I did not experience any issues).
2. For root users - Edit this file - /vendor/firmware/wlan/qca_cld/WCNSS_qcom_cfg.ini find the variant "hostArpOffload " and change the number from "1" to "0".
3. For non root users - Go to your router settings and under "Local Network" set IGMP snooping off. (this solution is less efficient).
In addition I disabled 2 more processes that drained my battery - "hal_bluetooth_lock" and "c8c000.qcom.qup_uart" (again with no apparent issues).
In addition I've downloaded the Universal GMS doze module from Magisk which is basically optimizing my battery for Google Play Services.
As I mentioned in the beginning this solution worked for me, your battery drain cause might be different but you can easily check what is keeping your device awake with the EX Kernel Manager (this processes wasn't shown in BBS or GSAM).
I am now getting 7.5-9 SOT and the battery drain around 1% per hour while idle.
I have Bluetooth on all the time and I am connected to a Smartwatch, Location is off and 120hz refresh rate.
I hope this guide would help others.
Aviv.
So far the beta Android 10 seems to be much better with battery draining apps
Thank you for the guide, the only thing I couldnt manage to work is I have to run every time;
Disable the qcom_rx_wakelock from the EX Kernel Manager and "hal_bluetooth_lock" and "c8c000.qcom.qup_uart manually, switched on apply on reboot,
I open the app every time I boot and hit the apply on boot button, am I doing something wrong, is there a script for auto apply whenever I reboot ?
avivv said:
My story
I have The Tencent version of the Asus rog phone 2, I mainly bought it for battery life, I am not a gamer.
I also saw that some users report about excellent battery life while others suffer from battery drain issues.
In reality the battery life was similar to my previous Samsung Galaxy S8 Plus which had half the battery capacity.
The SOT was around 4-6 hours and the phone drained around 5-8 percent of battery per hour when it was suppose to sleep.
I tried BBS (Better Battery Stats), GSAM etc.
Eventually I found a solution, this solution is relevant to me and may not apply to others but it's worth a shot.
My solution
First off, your phone must be rooted and on Android 9 version.
Download the Kernel by the brilliant @Freak07 from here:
https://forum.xda-developers.com/ro...rnel-kirisakura-1-0-0-asus-rog-phone-t4028237
Download EX Kernel Manager.
Go to Tools - Block Wakelocks and see what is waking your device.
In my case a process called qcom_rx_wakelock kept my device awake and murdered my battery.
With the help of @HomerSp we found that the reason for this is a device in my network that is sending packets over the network, there are 3 possible solutions:
1. For root users - Disable the qcom_rx_wakelock from the EX Kernel Manager program (This is what I did and I did not experience any issues).
2. For root users - Edit this file - /vendor/firmware/wlan/qca_cld/WCNSS_qcom_cfg.ini find the variant "hostArpOffload " and change the number from "1" to "0".
3. For non root users - Go to your router settings and under "Local Network" set IGMP snooping off. (this solution is less efficient).
In addition I disabled 2 more processes that drained my battery - "hal_bluetooth_lock" and "c8c000.qcom.qup_uart" (again with no apparent issues).
In addition I've downloaded the Universal GMS doze module from Magisk which is basically optimizing my battery for Google Play Services.
As I mentioned in the beginning this solution worked for me, your battery drain cause might be different but you can easily check what is keeping your device awake with the EX Kernel Manager (this processes wasn't shown in BBS or GSAM).
I am now getting 7.5-9 SOT and the battery drain around 1% per hour while idle.
I have Bluetooth on all the time and I am connected to a Smartwatch, Location is off and 120hz refresh rate.
I hope this guide would help others.
Aviv.
Click to expand...
Click to collapse
@avivv, your tutorial is pure gold . c8c000.qcom.qup_uart was eating my battery, now the power consumption seems to be back to normal, especially when using bluetooth.
@fethi2, same happens here, after a restart I must go back and block those processes (apply on boot is disabled after restart). Maybe something related to the kernel not being fully compatible to the EXKernelManager.
That's odd for me it stays blocked after a reboot.
Did you update the kernel to 1.0.2? This if my version.
Also I am using the paid ex manager kernel software version 5.31
I think I found the problem, go to the phone settings, advances, mobile manager, powemaster and allow auto start for magisk and ex kernel
avivv said:
I think I found the problem, go to the phone settings, advances, mobile manager, powemaster and allow auto start for magisk and ex kernel
Click to expand...
Click to collapse
They are both enabled here in autostart menu. Weird...
Be aware that if you got valid warranty. then do not ROOT since ROOTING requires bootloader unlock and that will void your warranty.
I have the exact same problem with the battery and I have the global version.
I'm still not up for rooting the phone right now though so instead, I'm trying out Android 10 beta and hoping it improves my situation.
Currently just getting a day of light usage with about 4 - 6 hours SOT. Doesn't feel like a 6000 mAh phone.
Ryle333 said:
I have the exact same problem with the battery and I have the global version.
I'm still not up for rooting the phone right now though so instead, I'm trying out Android 10 beta and hoping it improves my situation.
Currently just getting a day of light usage with about 4 - 6 hours SOT. Doesn't feel like a 6000 mAh phone.
Click to expand...
Click to collapse
Just 4-6? I charged my phone before gaming to 88%. Currently 18% after 4.5 hr of gaming.
And I'm on latest beta
Ryle333 said:
I have the exact same problem with the battery and I have the global version.
I'm still not up for rooting the phone right now though so instead, I'm trying out Android 10 beta and hoping it improves my situation.
Currently just getting a day of light usage with about 4 - 6 hours SOT. Doesn't feel like a 6000 mAh phone.
Click to expand...
Click to collapse
You can try to turn off the wifi and Bluetooth and check if it helps without root.
Already tried that. Still drains fast.
apollo3x said:
Just 4-6? I charged my phone before gaming to 88%. Currently 18% after 4.5 hr of gaming.
And I'm on latest beta
Click to expand...
Click to collapse
You're lucky. I only get 4.5 to 6 hours even without gaming.
I'm not rooted and my battery life is very good
I downloaded the app "naptime" from play store
Then I followed the app's instructions to input two lines of code into adb (please only do this if you know what you're doing, even though adb is pretty harmless)
Then enable aggressive doze in the app
Hopefully it might solve the idle drain some of you guys are experiencing? Never compared the battery life between the app on or off though
Can't help with the heavy gaming drain though I don't game that much and have excellent battery life IMO
6k battery for nothing ...
I bought the tencent version,rooted w twrp, formatted everything and installed the last firmware from Asus on android 9-changed WW fingerprint and WW rom . WHAT A PIECE OF JUNK,CARRYING ALL THAT WEIGHT AND SIZE FOR 6 SOT ...if i only knew i would'eve got a other smartphone. DONT MAKE MY MISTAKE,6K BATTERY IS JUST a marketing move . Ops sorry from 4-6 hours(tried what aviv recommend ed and it didn't help). Just stay away ...
dragheorg said:
I bought the tencent version,rooted w twrp, formatted everything and installed the last firmware from Asus on android 9-changed WW fingerprint and WW rom . WHAT A PEACE OF JUNK,CARRYING ALL THAT WEIGHT AND SIZE FOR 6 SOT ...if i only knew i would'eve got a other smartphone. DONT MAKE MY MISTAKE,6K BATTERY IS JUST a marketing move . Ops sorry from 4-6 hours(tried what aviv recommend ed and it didn't help). Just stay away ...
Click to expand...
Click to collapse
Return your phone to seller and buy another one. You have crappy one. My SOT is 10-12h everytime
dragheorg said:
I bought the tencent version,rooted w twrp, formatted everything and installed the last firmware from Asus on android 9-changed WW fingerprint and WW rom . WHAT A PEACE OF JUNK,CARRYING ALL THAT WEIGHT AND SIZE FOR 6 SOT ...if i only knew i would'eve got a other smartphone. DONT MAKE MY MISTAKE,6K BATTERY IS JUST a marketing move . Ops sorry from 4-6 hours(tried what aviv recommend ed and it didn't help). Just stay away ...
Click to expand...
Click to collapse
Damn that's unfortunate. I made some tweaks with root and I get 15 to 18 hours SOT very easily.
vygneys_vyg said:
Damn that's unfortunate. I made some tweaks with root and I get 15 to 18 hours SOT very easily.
Click to expand...
Click to collapse
What kind of tweaks? Im curious
djisma86 said:
What kind of tweaks? Im curious
Click to expand...
Click to collapse
First off just many tweaks in settings app itself, like background check, adaptive battery.
I disabled most of the installed apps' background services.
Used servicely and disabled over 20 system services.
Used substratum and made almost the whole phone pitch black themed using Pitchblack origins theme.
13-15 hours easy at 120Hz. 18 hours possible with 60Hz.
vygneys_vyg said:
First off just many tweaks in settings app itself, like background check, adaptive battery.
I disabled most of the installed apps' background services.
Used servicely and disabled over 20 system services.
Used substratum and made almost the whole phone pitch black themed using Pitchblack origins theme.
13-15 hours easy at 120Hz. 18 hours possible with 60Hz.
Click to expand...
Click to collapse
Bro please inform us which one to keep/not keep:
{
"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"
}
{
"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"
}
Some battery life stats is what I'm most interested in. This thing discharges by just looking at it.
Still early, some wifi wakelocks but look promising. The guru of GSI, Phh has an S22 on the way so expect the GSI's to be more or less flawless in the future
NisseGurra said:
View attachment 5563881
Click to expand...
Click to collapse
How to flash GSI? Steps please
Steps:
1: Patch stock recovery.img to include fastbootd
Use script : https://github.com/phhusson/samsung-galaxy-a51-gsi-boot/blob/master/run.sh
"Put your recovery in the same folder named recovery.img, edit script to fix path to magiskboot, run run.sh as root, flash r.img"
2: Download vbeta.img from google
3: Download an GSI, https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Andriod 12, AB, arm 64
4: Reboot fastboot
5: Open command window, enter
fastboot flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash system system-xxxx.img ( the name of the gsi you use)
reboot to recovery and do an factory reset
reboot system
NisseGurra said:
Steps:
1: Patch stock recovery.img to include fastbootd
Use script : https://github.com/phhusson/samsung-galaxy-a51-gsi-boot/blob/master/run.sh
"Put your recovery in the same folder named recovery.img, edit script to fix path to magiskboot, run run.sh as root, flash r.img"
2: Download vbeta.img from google
3: Download an GSI, https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Andriod 12, AB, arm 64
4: Reboot fastboot
5: Open command window, enter
fastboot flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash system system-xxxx.img ( the name of the gsi you use)
reboot to recovery and do an factory reset
reboot system
Click to expand...
Click to collapse
Sorry I am nope
I have to edit the script run.sh?
".... edit script to fix path to magiskboot, run run.sh as root, flash r.img"
So you mean I have to download
GitHub - phhusson/treble_experimentations: Notes about tinkering with Android Project Treble
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
and it will download the magiskboot?
as it shows in the run.sh script.
Code:
mkdir d
cd d
~phh/Downloads/magisk/x86/magiskboot unpack ../r.img
~phh/Downloads/magisk/x86/magiskboot cpio ramdisk.cpio extract
# Reverse fastbootd ENG mode check
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery e10313aaf40300aa6ecc009420010034 e10313aaf40300aa6ecc0094 # 20 01 00 35
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery eec3009420010034 eec3009420010035
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 3ad3009420010034 3ad3009420010035
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 50c0009420010034 50c0009420010035
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 080109aae80000b4 080109aae80000b5
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 20f0a6ef38b1681c 20f0a6ef38b9681c
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 23f03aed38b1681c 23f03aed38b9681c
~phh/Downloads/magisk/x86/magiskboot hexpatch system/bin/recovery 20f09eef38b1681c 20f09eef38b9681c
~phh/Downloads/magisk/x86/magiskboot cpio ramdisk.cpio 'add 0755 system/bin/recovery system/bin/recovery'
~phh/Downloads/magisk/x86/magiskboot repack ../r.img new-boot.img
cp new-boot.img ../r.img
can you please share your run.sh script so I can have an idea how to edit that.
Here are the recovery with fastbootd included.
ONLY S22 exynos SM-S901B, SM-S901B_AVC6 firmware
recovery.img
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
NisseGurra said:
Here are the recovery with fastbootd included.
ONLY S22 exynos SM-S901B, SM-S901B_AVC6 firmware
recovery.img
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thank you so much. Can you please share your run.sh script too? I will be very thankfull. Did you use 7zip in order to compress the recovery image in to .lz4? I am using ubuntu.
Can someone please tell me how to manually add or include fastbootd in a stock recovery.img? I can't get this script to run properly. Thanks in advance.
Hi can anyone give detailed instructions how to enable fastboot on stock recovery ?
Late reply: join phh group on telegram and request an recovery with fastboot enabled. There are memebers that will help you.
Device name? GSI version? - #phh-treble
https://t.me/phhtreble/283195 <--- Read before any question ^^^
t.me
Still waiting for the battery life screenshots. I'm really curious how much better it is on GSI than on stock.
dragos281993 said:
Still waiting for the battery life screenshots. I'm really curious how much better it is on GSI than on stock.
Click to expand...
Click to collapse
As s22 exynos drain 30-40% from wifi bug every night there no way to make an real estimate of battery life.
NisseGurra said:
As s22 exynos drain 30-40% from wifi bug every night there no way to make an real estimate of battery life.
Click to expand...
Click to collapse
NisseGurra said:
As s22 exynos drain 30-40% from wifi bug every night there no way to make an real estimate of battery life.
Click to expand...
Click to collapse
When I get home tommorow night, I'll link you a few places to read and help you do some cleaning up because these Samsung phones are full of junk and services that the phone can live without. I've been going nuts trying to make this rubbish of a device perform better and I managed to get it to waste less battery while active and inactive by disabling and uninstalling A LOT of stuff I don't need and so on. And I came to the conclusion that for daily usage I didn't need 100% of the 8 Gen 1 chipset. I therefore cut in half the frequency for the 3rd cluster and decreased the ones of the other 2 as well. I basically limited the max freq of the CPU without noticeable effects on the performance. Probably benchmarks would should how much performance I wasted, but as I don't care about numbers on paper, I'm pretty ok with how the phone's running right now after cleaning it up. The battery is very small, the CPUs are very inneficient, both SD and Exynos, despite the marketing claims, the apps are very power hungry and the CPU gives the processing power in an aggressive and inneficient when the transition from a frequency to another should be smoother and not as quick to give it all up when it's actually not necessary. Paired with all the useless processes and services which work like lunatics to do whatever BS they're trying to do, whether it is while you're using the phone or in the background, and you're left with a terrible user experience that makes you contemplate throwing the phone away.
I used an iPhone 13 Pro for 4 months before buying this thing and I forgot to look at the battery level because iOS is that efficient. It was terrible for me overall but when it comes to smoothness and battery life, there's nothing in the Android world that comes even close to that. The best Android device that comes close to Apple's latest amd greatest is probably around 5,6 years behind. That's sad but it is what it is.
dragos281993 said:
When I get home tommorow night, I'll link you a few places to read and help you do some cleaning up because these Samsung phones are full of junk and services that the phone can live without. I've been going nuts trying to make this rubbish of a device perform better and I managed to get it to waste less battery while active and inactive by disabling and uninstalling A LOT of stuff I don't need and so on. And I came to the conclusion that for daily usage I didn't need 100% of the 8 Gen 1 chipset. I therefore cut in half the frequency for the 3rd cluster and decreased the ones of the other 2 as well. I basically limited the max freq of the CPU without noticeable effects on the performance. Probably benchmarks would should how much performance I wasted, but as I don't care about numbers on paper, I'm pretty ok with how the phone's running right now after cleaning it up. The battery is very small, the CPUs are very inneficient, both SD and Exynos, despite the marketing claims, the apps are very power hungry and the CPU gives the processing power in an aggressive and inneficient when the transition from a frequency to another should be smoother and not as quick to give it all up when it's actually not necessary. Paired with all the useless processes and services which work like lunatics to do whatever BS they're trying to do, whether it is while you're using the phone or in the background, and you're left with a terrible user experience that makes you contemplate throwing the phone away.
I used an iPhone 13 Pro for 4 months before buying this thing and I forgot to look at the battery level because iOS is that efficient. It was terrible for me overall but when it comes to smoothness and battery life, there's nothing in the Android world that comes even close to that. The best Android device that comes close to Apple's latest amd greatest is probably around 5,6 years behind. That's sad but it is what it is.
Click to expand...
Click to collapse
I swear all the **** Samsung installs on their devices is turning me crazy
No Samsung, I don't want Bixby, I don't want this side taskbar installed by default, I don't want your cloud services by default, no I don't want your "secure folder" thing, I don't want your Samsung Pass thing either
Like come on, the above list is like 25% of all the **** they install
Visually OneUI is awesome and I love it, I love some of the features and options that they provide / provided very early, even before Android sometimes, it's highly customizable and things like Goodlock are awesome, but it would be even better if you could allow us to remove ALL of their apps without having to use ADB or some weird stuff like this
I think Digital Wellbeing is a good example of what should be removable as I don't see everyone using it and it's even more of a shame when you realize that uninstalling it with ADB works perfectly fine and causes no issues...
Something that I love on Windows in the "services" tab where you can see each service, what it does, weither it is ok to disable it or not, what features you lose if you disable it... I think Android should do the same or something similar with system apps
jojos38 said:
I swear all the **** Samsung installs on their devices is turning me crazy
No Samsung, I don't want Bixby, I don't want this side taskbar installed by default, I don't want your cloud services by default, no I don't want your "secure folder" thing, I don't want your Samsung Pass thing either
Like come on, the above list is like 25% of all the **** they install
Visually OneUI is awesome and I love it, I love some of the features and options that they provide / provided very early, even before Android sometimes, it's highly customizable and things like Goodlock are awesome, but it would be even better if you could allow us to remove ALL of their apps without having to use ADB or some weird stuff like this
I think Digital Wellbeing is a good example of what should be removable as I don't see everyone using it and it's even more of a shame when you realize that uninstalling it with ADB works perfectly fine and causes no issues...
Something that I love on Windows in the "services" tab where you can see each service, what it does, weither it is ok to disable it or not, what features you lose if you disable it... I think Android should do the same or something similar with system apps
Click to expand...
Click to collapse
Exactly. They like to push down your throat their crap. All the stuff you mentioned I already disabled or uninstalled altogether. Digital Wellbeings was draining my battery in the background at all times without even having it configured. So that was deleted. Bixby is gone too and a bunch of other things. But the main issue for all this is the small battery for the terrible quality 8 Gen 1 or the Exynos 2200. 4nm is pure marketing at this point.
Sorry, @NisseGurra for not getting back here last night, like I said I would.
I also realized afterwards that you were on a GSI build but I intended to help you clean up the stock firmware.
The best advice I can give you right now though is to try doing what I did. Please don't take it personally if I explain or define stuff that you might already know or actually know even better than me. If someone else reads this, they might learn something from it or do some tweaking even if they're on the stock ROM or something custom. You take only what you need from this.
The whole thing starts with the process of opening the Apps section in the Settings, checking/turning on the "system apps" option and opening everything in there one by one. You'll have both apps and services showing up in there and what you wanna look for is the "Battery" section, or whatever it's named on your GSI. You basically need to see how much battery it's wasted since the last charge. High battery usage=no bueno. In that case, you google that app/service, weird name or not and see if it's rudimentary for the proper functioning of your phone. If it's not essential or it's used as a service for some apps that you don't even use but it's there just in case, then you can get rid of it. And obviously, you have to do this for every single app and service in there. It's a pretty time-consuming job but if you want to keep your sanity in the end, then it's a good activity. After that, for the remaining things, you can use "Servicely" from the Play Store and force the stuff you don't need at all times to sleep/Standby when the screen is off or even prevent it from running in the background altogether.
You should also download Naptime and use it to activate Aggressive Doze and disable Motion Detection too so the phone stays in doze mode even when you're moving around, a scenario in which by default the phone comes out of doze whenever it detects motion.
Stuff like "Find my phone" I had to turn off. There was one option for this thing somewhere in the google account section and also in the Samsung provided services in the Settings, on the stock firmware. Talk about a huge mess. I don't really need those. If I lose my phone, which never happened to me so far, it is what it is, but I'd rather have better battery life than have a service running at all times just for the moment I lose this crap if that ever happens.
This whole thing above is mainly meant to improve the standby time when the phone is idling.
And to not forget to mention this, I have Battery Saver active at all times. Normally, everything should be crippled while this thing is on including the refresh rate of the screen which gets stuck at 60Hz. For that, there's Galaxy Max Hz. It offers the ability to activate something called "Keep smoothness on power saving mode" and you won't even know that the thing Is even on. The essential part is that the OS is supposed to be less active, decrease the background BS and also the power of the CPU down to 75%. This part doesn't really matter because I already planned on downclocking it but if there's anything applied by default to make the CPU less aggressive along with the stock decrease to 75%, then downclocking it would make it even better because now you have lower frequencies which now jump up and down at a slower rate. I mean I hope it's done like that. I haven't monitored the difference in the activity of the CPU with Power Saver on/off so I can't tell for sure. It would be logical to happen that way though. Another important little part is that I installed "Universal GMS Doze" which allowed me to put the Google Play Services on "Restricted" in the Battery section. I had to restrict the "play services framework" too cause they liked to molest my battery too when I wasn't looking. But I digress.
On the stock firmware, I also use Battery Tracker made by Samsung. I really like it because I can easily select the period of time of activity/battery drain by dragging 2 sliders from one side to another and see what happened during that time, and you get background activity stats and what percentage of the battery it's wasted.
For the much better and more detailed Screen on/Screen off stats or charge/discharge information which all show in a useful notification, I use Battery Guru. It barely drains any battery so it's very well optimized.
Back to the technical part, the other important thing was to downclock the CPU, and this is essential for the active time which later translates into better SOT.
I'm using Smart-Pack Kernel Manager for the tweaks because it's the most detailed of them all and well rounded in my opinion and it's also the lightest on the battery, while in use, of course. It's got a side panel with all the sections that have the tweaks I'll mention in this post.
The following part is gonna be a bit more detailed. It's just a few tweaks in the end but I'll throw in some basic information here and there to make it a little more informative and nice to read. Keep in mind that even if I tweaked the stock firmware here, the tweaks are essentially the same for the kernel or at least similar. The values and options shown in the kernel manager can differ in terms of naming or the way you can change them, but they should be overall similar.
Note that this is more like a presentation of what I did on my phone, not a tutorial. You can open that kernel manager, look around and see for yourself the range of tweaks that are available of which a few are the ones I changed.
Now to business.
The stock max frequencies for the 8 Gen 1 on my S22 are something like this:
- 1785MHz for the 4 LITTLE Cores, 2496 for the 3 Middle cores, and 2995 for Core 8, which is also the big core (terribly inefficient "fat" bastard).
So we've got: 1785, 2496 and 2995 respectively.
My phone is running smoothly with all these downclocked right above the border between noticing and not noticing a difference in the UX department if you get what I'm saying.
So my current maximum clocks for all 3 clusters are 1363, 1555 and 1401 respectively. They're lowered pretty drastically, I know, but I don't care about benchmarks, in which you'd probably see a difference. In the real world, opening and closing apps among other regular things, are not gonna be noticeable. It's not like you're gonna sit with 2 phones next to you, a stopwatch in your hand and cheer when your phone is half a second faster than mine. It's just not gonna happen. That 30% increase and performance. blah blah, when a new generation of a CPU is announced you're not gonna notice especially when we're talking about CPUs that are only 1 generation apart.
Anyway, these lower frequencies will obviously help with thermals mainly but also with the battery life, although the difference for the latter is not that huge it's still better than before.
The CPU Governor for all 3 clusters is set "walt" by default. I couldn't find any information on how it's supposed to work and behave but because it's the default, I'm sure it's focused on something in between performance and battery savings. So I set it to "conservative" for all 3 clusters. This governor likes to get the frequencies back down as soon as possible after a task is done. So this is also gonna help with thermals.
Now to the CPU Hotplug. In the past when big.Little became mainstream, a whole performance cluster was called in for the heavy tasks and they followed a basic routine: when a certain threshold is crossed, the big cores take charge of the situation and when they cross a second threshold, which is a lower value, those big cores step away and they hand over the steering wheel back to the Little cores for the light tasks until they're needed again. They still pitched in but a bit more lightly. Now just one big core appears to be able to do that on its own, however, this time the job is split between the big core and the middle ones. So there's a bit more control over a situation because you've got those middle cores that are pitching in for the medium intensive tasks.
Anyway, I decided to up that threshold and basically make the CPU ask for the big core's help when the job gets a bit more difficult, heavier, essentially making it contribute less often. I don't want to reboot my phone to see what the default values were but now they're basically higher: "Busy down Threshold = 50", and "Busy up=70". I just explained what this threshold is, so you probably already got how this is supposed to work looking at these numbers.
And the last thing tweaked is the GPU. Sadly, the stock kernel doesn't allow for the downclock to stick. It's missing the parts which allow for this sort of functionality because it's stock and wasn't meant to be tweaked. The only thing I could do was to change the power level. You haven't got anything in there other than an option to let you change a value. The essence of it though is that the lower the number, the better the GPU performs. It's not gonna work outside of the defined parameters though. It only gets more active. Anyway, the default value is 10. I set mine to 12, which is the last level. This way I basically put the GPU in a more "conservative" state, so to speak. While gaming, I haven't noticed any performance loss, so hooray. It is doing its job but it's a bit less aggressive.
To finish this long a$$ post, I gotta say that after doing all this above, my battery life has improved quite drastically.
3, 3.5h SOT was what I consistently got without tweaking anything. Right now I'm at 4h49m SOT for only 64% wasted. I charged the phone only to 85% and the battery is down to 15%. The idle drain is only 0.3%/h.
I'll post a screenshot for the hell of it. Anyway, so far so good. One thing's for sure though. I'll do some research and if I manage to find any battery from another Samsung phone that's bigger but is very close in size to the one in this phone, it doesn't matter if I have to cut some of the lips inside to make it fit, I'll do it. I'll make that a project.
Edit: Everything I mentioned above is getting balanced out by other things somehow and 3.5h is the definitive SOT on average I have been getting since forever now. I therefore stopped trying anything, relocked the bootloader and I haven't done anything to the OS anymore. The SOT stayed the same and there aren't any improvements with any update. So this is pretty much how it is and there's nothing we can do about it. The phone is simply pure trash regarding the battery life.
dragos281993 said:
Sorry, @NisseGurra for not getting back here last night, like I said I would.
I also realized afterwards that you were on a GSI build but I intended to help you clean up the stock firmware.
The best advice I can give you right now though is to try doing what I did. Please don't take it personally if I explain or define stuff that you might already know or actually know even better than me. If someone else reads this, they might learn something from it or do some tweaking even if they're on the stock ROM or something custom. You take only what you need from this.
Click to expand...
Click to collapse
Thanks, an excellent post on how to get rid of battery leaks.
Its a pity that this work is needed 2022, should be optimized system from Samsung from start.
The problem now is the wifi bug, very strange that Samsung not noticed this in their testing.
How good does the GSI work on this device? Can you use it as daily driver? I am thinking of buying this phone, but don't want to use One UI.
dragos281993 said:
Some battery life stats is what I'm most interested in. This thing discharges by just looking at it.
Click to expand...
Click to collapse
You're welcome to check my thread then
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com