[Battery] Fixing some of the battery bugs - Streak 5 General

TheManii said:
It's widely known that the s7 has pretty weak battery life.
In general all qisda dell devices do (the s5/s7/venue).
Many of the bugs exist in the phone/ril and some exist in the logging systems.
In a bug free rom these workarounds should be completely meaningless, but stock roms are not at all bug free.
Recommendation one: Enable airplane mode on wifi s7's
The wifi and 3/4g roms are nearly identical, including the fact that wifi roms still have a full RIL. It apparently is also still enabled even in wifi s7's. Turning airplane mode on while leaving wifi/bluetooth on (as desired) does in fact affect the system.
Ways of checking: with airplane mode off on mine, the s7 has major issues going into sleep mode. Even with the screen off if you check the battery graph it's still active most of the time. Airplane mode more or less fixes this.
Potential gains: 20-30% or so more life, I've only been testing this for half a day or so but it seems to be draining signifigantly slower in sleep.
Recommendation two: (this one is more valid for the s5 then the s7) Connect the s7 to a pc with the android SDK installed and run 'adb logcat'
The qisda devices are known to have far too much logging enabled and included in stock roms. Virtually all the custom roms for the s5/7 have it removed, but there is a known bug with logging.
If you run logcat so the output is directed to it, afterwards it takes care of another one of the bugs. I have not actually tested this specifically on the s7, but it likely is equally valid as the differences from AOSP (ie the customizations qisda does to the roms) are pretty similar in the s5 and s7.
Potential gains: nearly triple battery life after logcat and avoiding a yet different ril bug on the s5. The s5 can go from potentially 10%/hour to 0.3%/hour due to all/no bugs being active. The s7 MAY be a valid target too, but I havnt actually tested this one on the s7.
Roms used to compare:
S7: Stock 506-wifi
S5: Custom 406 based rom
Click to expand...
Click to collapse
Crosspost from the S7 forum, both are valid on the s5.
The largest battery bug is in the RIL, way of activing the bug: make a call. If you reboot everytime after making a call the battery life is much better then if you dont restart. Depending on how often you make calls though this is completly unacceptable to reboot after each call.

Are you saying that removing logcat daemon would give more battery life?
If I am not mistaken, that seems a obvious thing, am I wrong?
But if you remove the logcat daemon, then you can't hunt the bugs anymore, so for custom Roms that would be a very high price to pay for so little gain.

Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit

TheManii said:
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
Click to expand...
Click to collapse
So redirecting output from /dev/null to /dev/tty1 improves battery life ? Seems highly unlikely to me.
Can you explain the methodology used in your tests, bcs we can go somewhere this way, bcs s5 seems to have not a good battery life, and some strange things i have observed too in this device.

It's redirecting it to the adb console, this is why the bugs inherently make no sense as it should be otherwise discarding the log safely when not attached to adb.
But it's really consistant/reproducable on my device. Until it's attached it contributes about +2-3%/hour drain on standby.

TheManii said:
It's redirecting it to the adb console, this is why the bugs inherently make no sense as it should be otherwise discarding the log safely when not attached to adb.
But it's really consistant/reproducable on my device. Until it's attached it contributes about +2-3%/hour drain on standby.
Click to expand...
Click to collapse
2-3 % standby per hour is way too much , i am running the latest DSC 0.64b on top of 407 BB and have around 1-1.5 % , but that seems too much for me , you should check the background processes i think.

I can consistantly get 0.3/hour drain if the bugs taken care of.
If you also encounter the RIL bug you can easily hit 10%/hour possibly in combination with the log bug, it's relatively common too.

TheManii said:
I can consistantly get 0.3/hour drain if the bugs taken care of.
If you also encounter the RIL bug you can easily hit 10%/hour possibly in combination with the log bug, it's relatively common too.
Click to expand...
Click to collapse
So then something wrong with my system then, what Rom you running ?

TheManii said:
Running logcat with the device attached actually affects it. You dont remove it, you merely run it and let it write to your screen for a bit
Click to expand...
Click to collapse
I have the stock Olleh 407 ROM installed on my Streak. If I run the ADB LOGCAT with my Streak attached for a while, then the bug will be gone, even if I disconnect from my PC? Or the bug is only gone when Im connected to the ADB LOGCAT?

It's a heavily modified SD 2.4.4
The RIL bug seems to be more noticible in GB, I dont recall if it existed in 3xx roms. The logcat one is possible in 3xx or newer roms.

lunadomain said:
I have the stock Olleh 407 ROM installed on my Streak. If I run the ADB LOGCAT with my Streak attached for a while, then the bug will be gone, even if I disconnect from my PC? Or the bug is only gone when Im connected to the ADB LOGCAT?
Click to expand...
Click to collapse
It's really voodoo/magic, attaching it for <some unknown amount of time> will fix it for <some random amount of time>
For me it seems I just attach it until the battery is charged (as I would charge it anyway) and it seems to last for a day to a couple days. It's as voodoo as it sounds.
It doesnt stick past a reboot and more importantly the RIL bug is the more noticable one anyway.
It's only really noticible when the ril bug isnt active, as then you're going from 2-3% to 0.3%/hour. Going from <10% to 3% overshadows it if it's even active at all.
I cant really say for certian if it even effects everyone or happens every boot. I've been on the same rom for 2 months and have extremely consistant data with regards to these two bugs.
The logcat one is just as consistant for me on SD 19x roms.

You can also do it without SDK installed, you just need to download terminal emulator from market and enter:
su
logcat
And you are ready

At least when I do it, i use it as an opportunity to charge anyway. I always do it on my pc as I need the SDK for other things so I always have it installed.

On a custom SD244 not OCed with airplane mode and after running logcat previously with wifi turning off when screen is off:
getting 15hours @5% lost.
I'm gonna keep testing till tomorrow then install 407

Surprisingly: the s5 has even better battery life then the s10 (ignoring the differences in battery life).
The s10 has amazing battery life too.
Current results:
S5 : 31 hours = 24%
S7 : 54 hours = 48%
S10:61 hours = 13%
Normalizing their results to the size of the S10's batt:
S5: 5.17 hours each %
S7: 2.63 hours each %
S10: 4.7 hours each %
Roms used:
S5: SD 2.4.4 <2.3.3>
S7: Stock 506-wifi <3.2>
S10: Chimeradroid r2 <3.2>
The S5 can be explained by the RIL bugs as mentioned earlier, and by airplane mode is also turning off the radio too. All 3 devices were left to idle for the entirety, with only battery graph checks and no actual use.

Guys , i have a really vad problems with my battery life. After i go on to Power Rom EVG (before that i was with StreakDroid 2.4.4) my battery is absolutely not good. I do this logcat trick, just a few programs is running, auto-brighness and ... nothing! please, help!

Related

[INVESTIGATION] Battery drain bug in 2.3.4 (JVP build for now)

It seems that our beloved Samsung did it again!
Now we can enjoy a fully functional, long waited, Gingerbread 2.3.4.
Although some sources say that it is only a leak, the JVP build seems to behave really well, according to the reports of many users.
Gingerbread 2.3.4 was build in order to fix some Android bugs and make the interface even faster. We have seen that the second task is a success, the user experience and crazy Quadrant scores being the best witnesses. But what about the first task, are there any android bugs in this build? Maybe we could find out together.
The key purpose of this thread is to find out if that Android OS bug, which made Gingerbread users a hard life, is still present.
You can help this investigation by keeping an eye on the battery stats and reporting the consumption (in percents, of course) of the Android OS. It is even better if you can add some screenshots.
Please don't forget to mention:
- The ROM and kernel you are using.
- Some apps or games you are using (known to fire this bug on previous builds).
- Whether you have autorotation on or off (some users reported they had no drain if kept off on 2.3.3 builds).
- What type of usage you applied to the phone (not really necessary, only you are kind enough).
If you have any kind of suggestion regarding some modifications for this thread you are welcomed to post them. It will helps us become more efficient.
Thank you very much for your effort!
EARLY CONCLUSIONS*:
- Battery life is indeed an improvement on JVP 2.3.4
- The Android OS bug is less aggressive. The reports show a maximum consumption of approx. 20%. We can't say for sure if we can talk about a bug anymore. Anyway, the drainage is not so bad, comparing to 2.3.3 versions.
- The Android System consumption is a bit scary (15-20%) especially after a flash. However, it tends to stabilize in time.
- A clean flash, factory resets, avoiding apps restoration with Titanium or similar, reducing consumers when you don't need them always helps. With or without battery draining bugs.
- JVP is a better alternative for previous versions due to improvements for battery life, speed and stability, even if it's a beta release. So you should go for it, it really is an upgrade!
*The statements above are based on reports and poll results collected until now and they may change. I take no responsibility if you will find those informations incorrect or incomplete. Flash JVP at your own risk, you could loose data or brick your phone, although there aren't reports that say that. Follow the instructions and you should be ok!
is this a new craze insted of train spotting or stamp colecting ....battery watching ....most of us have got a life and have better things to do then watch how much a battery uses ...do what i do charge the phone and enjoy these phones do use loads of battery
Updated with 2.3.4 I9000XXJVP,CSC = I9000OXAJVP and kept it on without sim and without even touching but fully charged. The battery life was just for one and half days.
Android OS running at 3%
using Damian's GTO Alpha kernel for JVP and Brotuck's gingerMod ROM.
Autorotation off.
Consistent q scores in the 2600 range, phone running very smoothly and very fast in daily use (internet, twitter, pics, camera, messaging, phone), 130+ apps installed, no issues. Seems a much better base firmware than any of the 2.3.3 variants.
It's a bit early to investigate this stuff.
Wait for Samsung to release 2.3.4 sources and devs to make some stable kernels based on this.
Until this time many stuff can be broken (well, you're free to beta test though ).
batery is much beter in 2.3.4
no since i flash JVP 2days ago!
anukilimanoor said:
Updated with 2.3.4 I9000XXJVP,CSC = I9000OXAJVP and kept it on without sim and without even touching but fully charged. The battery life was just for one and half days.
Click to expand...
Click to collapse
Keep in mind that after a reflash the battery life will stabilize after a while.
In my opinion, the cell standby may be the cause. If left without SIM, Airplane mode off, your phone will continue to search for signal and this really drains the battery.
If you can make a test again, check the battery usage and post your conclusion.
Thanks for your contribution!
got-petrol said:
is this a new craze insted of train spotting or stamp colecting ....battery watching ....most of us have got a life and have better things to do then watch how much a battery uses ...do what i do charge the phone and enjoy these phones do use loads of battery
Click to expand...
Click to collapse
This kind of activity is normal in community, especially here in XDA.
It will be useful for those kind of people who don't like to experiment in order to find some answers.
We could do like you but, what if we need to charge it again, after 8 hours, without using the phone?
That's why this "new craze" exists, because we want to avoid that kind of problems.
Tatsuya79 said:
It's a bit early to investigate this stuff.
Wait for Samsung to release 2.3.4 sources and devs to make some stable kernels based on this.
Until this time many stuff can be broken (well, you're free to beta test though ).
Click to expand...
Click to collapse
You're right but the 2.3.4 concentrates on fixing bugs, so even in beta stage we should see some changes.
Anyway, the thread is intended to test the firmware regarding this problem, so it can become an indicator for people asking weather they will experience this problem of they can enjoy using their phone without even thinking about this.
lgsshedden said:
Android OS running at 3%
using Damian's GTO Alpha kernel for JVP and Brotuck's gingerMod ROM.
Autorotation off.
Consistent q scores in the 2600 range, phone running very smoothly and very fast in daily use (internet, twitter, pics, camera, messaging, phone), 130+ apps installed, no issues. Seems a much better base firmware than any of the 2.3.3 variants.
Click to expand...
Click to collapse
Thanks for your feedback, happy user!
I must say that 2.3.4 battery is performing better than 2.3.3 so far.
After 11 hours with gps and auto rotate on, battery still have 30% of juice left.
EDT: Attached screenshots
Sent from my GT-I9000 using XDA App
Comming from Froyo JPY to stock deodexed JVP, I have noticed a higher battery drain.
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
I'm using stock deodexed rom from ramad, Dark core kernel and screen off animation. that's all I've changed to this rom, no games, and a few apps like titanium backup and atk.
When I tapped on the android system there was a huge list of included packages, I will list them here, maybe one of them (or all together) is causing that huge battery use:
com.samsung.InputEventApp
Service mode
Software update
Google Backup Transport (actually, I turned off google backup, idk why this is here)
Settings Storage
Mobile tracker
Account and Sync Settings
EncryptApp
Task manager
Error
Perso
com.sec.android.app.lcdtest
VPN Services
Factory Test
wssyncmlnps
PopupuiReceiver
Preconfig
BluetoothTest
Self Test Mode
WlanTest
Status Bar
Settings
Mobile tracker settings
Android System
DRM content
MTP Application
PhoneSetupWizard
Security Storage
Licence Settings
PhoneUtil
Those are all......
gtluis said:
Comming from Froyo JPY to stock deodexed JVP, I have noticed a higher battery drain.
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
I'm using stock deodexed rom from ramad, Dark core kernel and battery off animation. that's all I've changed to this rom, no games, and a few apps like titanium backup and atk.
When I tapped on the android system there was a huge list of included packages, I will list them here, maybe one of them is causing that huge battery use:
com.samsung.InputEventApp
Service mode
Software update
Google Backup Transport (actually, I turned off google backup, idk why this is here)
Settings Storage
Mobile tracker
Account and Sync Settings
EncryptApp
Task manager
Error
Perso
com.sec.android.app.lcdtest
VPN Services
Factory Test
wssyncmlnps
PopupuiReceiver
Preconfig
BluetoothTest
Self Test Mode
WlanTest
Status Bar
Settings
Mobile tracker settings
Android System
DRM content
MTP Application
PhoneSetupWizard
Security Storage
Licence Settings
PhoneUtil
Those are all......
Click to expand...
Click to collapse
It seems that you have a normal consumption on Android System. Also that app list is present on every ROM which has all system apps. On lite ROMs you can get a smaller list, because some of those apps are removed by the chefs.
Maybe your network coverage is not that good
After a flash, the battery needs stabilization, until then it can drain fast. Try to recalibrate it. Please tell me if you need a good guide.
Try a lite ROM. Maybe you will experience a good Android System consumption.
Thanks for the feedback!
Look at the poll results so far 72% say they have no battery issue, so it must be the apps on your phone that are at fault for any unusual battery drain.
Look at your own apps first before you blame the rom, mostly it's not the rom that's at fault.
gtluis said:
I lost 13% overnight, I had 21% battery use on cell standby (6hours of use). and I noticed something very strange, android system has a 18% battery use with only 5 minutes running, WTF???
Click to expand...
Click to collapse
When you're not really using your phone, Android System will have a higher battery use percentage, because nothing else is using battery.
Long periods of idle, you will see higher Cell Stanby and Android System percentages.
The more you use the phone, those percentages will lower.
mammenj said:
I must say that 2.3.4 battery is performing better than 2.3.3 so far.
After 11 hours with gps and auto rotate on, battery still have 30% of juice left.
EDT: Attached screenshots
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Good job! Enjoy your phone!
turn off data connection or wifi when youre not using them
and it will least even longer...
This is what i had with the previous JVO (2.3.3) and not using any task killer anymore. I moderately used the phone, made some calls, wrote some SMS, had blutooth on in the car, listening mp3. Ah, and i set display brightness to "auto" always, i don't use the manual setting with lowest brightness value anymore.
But i also can get the battery down in less than a day...
I'll give the new 2.3.4 a try.
It's funny to see that there is always somebody who needs to torture the board with reinventing the battery wheel. Strange battery behavior usually shows up (and is often dependent on them) in threads with special roms or kernels. The only thing this thread will brings us is more of the same on how to save juice if you don't want to fork for a larger/extra battery.

[Q] [SOLVED, kinda] Weird battery drain for no apparent reason

Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
gilboa said:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
Click to expand...
Click to collapse
Buy a new battery, maybe this will solve the problem...
gilboa said:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
Click to expand...
Click to collapse
Indexing your external SD maybe?
You could try the link in my sig and try again for your custom ROM.
First, thanks all for taking the time to answer.
I'm thinking about getting a new battery, but my gut feeling is that its not the source of amazing battery drain - ~20%/h while completely [!] idle (auto-sync/location/etc completely off).
I've attaching /d/wakeup_source in excel format sorted by count and total time - in-case someone has any idea what's completely broken.
As far as I can see, qpnp-vadc-ebd30a00, sec-battery-monitor, mmc0:0001:2 are the main culprits.
nicholaschum,
Before I attempt a complete wipe (as opposed to the normal wipe data / cache), how can I detect if someone is indexing my sdcard? (which may account for the mmc0:0001:2 in the wake lock dump).
- Gilboa
I know this is a long shot but try turning off developer options if you have it turned on(especially force gpu rendering). Somehow I found out that when I turned it on and the screen is idle. I get a battery drain. Not as big as yours. But not really sure because if I use the phone, the battery is actually pretty great(an hour of screen time is about 10% even more with internet apps like facebook youtube chrome etc.).
Clear cache. I know this is too common but it actually works for a lot of people.
Lastly, try airplane mode overnight and see if it doesn't drain. It might be your network that is causing the drain.
gilboa said:
First, thanks all for taking the time to answer.
I'm thinking about getting a new battery, but my gut feeling is that its not the source of amazing battery drain - ~20%/h while completely [!] idle (auto-sync/location/etc completely off).
I've attaching /d/wakeup_source in excel format sorted by count and total time - in-case someone has any idea what's completely broken.
As far as I can see, qpnp-vadc-ebd30a00, sec-battery-monitor, mmc0:0001:2 are the main culprits.
nicholaschum,
Before I attempt a complete wipe (as opposed to the normal wipe data / cache), how can I detect if someone is indexing my sdcard? (which may account for the mmc0:0001:2 in the wake lock dump).
- Gilboa
Click to expand...
Click to collapse
Hi, basically just check your phone using BBS (BetterBatteryStats), and see which individual process is eating up your battery.
Graffiti Exploit said:
I know this is a long shot but try turning off developer options if you have it turned on(especially force gpu rendering). Somehow I found out that when I turned it on and the screen is idle. I get a battery drain. Not as big as yours. But not really sure because if I use the phone, the battery is actually pretty great(an hour of screen time is about 10% even more with internet apps like facebook youtube chrome etc.).
Click to expand...
Click to collapse
I had the developer options off and on. Didn't seem to help.
Clear cache. I know this is too common but it actually works for a lot of people.
Lastly, try airplane mode overnight and see if it doesn't drain. It might be your network that is causing the drain.
Click to expand...
Click to collapse
If the current state doesn't hold (see below), I'll give it a try. Good thinking
nicholaschum said:
Hi, basically just check your phone using BBS (BetterBatteryStats), and see which individual process is eating up your battery.
Click to expand...
Click to collapse
Already installed - together with WakeLockDetector.
Short update, out of pure desperation I completely wiped the phone (including sdcard), tried installing stock ROM and, err, Odin failed. Managed to get CWM running again and installed the latest CM nightly.
...
As weird as it sounds, going from NF4 based ROMs (including stock) to CM nightly dropped to idle battery usage to ~2-6%/h, a huge drop from ~20%/h.
I'll update and mark resolved if this situation holds (crosses fingers).
- Gilboa
gilboa said:
I had the developer options off and on. Didn't seem to help.
If the current state doesn't hold (see below), I'll give it a try. Good thinking
Already installed - together with WakeLockDetector.
Short update, out of pure desperation I completely wiped the phone (including sdcard), tried installing stock ROM and, err, Odin failed. Managed to get CWM running again and installed the latest CM nightly.
...
As weird as it sounds, going from NF4 based ROMs (including stock) to CM nightly dropped to idle battery usage to ~2-6%/h, a huge drop from ~20%/h.
I'll update and mark resolved if this situation holds (crosses fingers).
- Gilboa
Click to expand...
Click to collapse
I heard there were problems with NF4 battery. But I haven't been on TW since ND4. No matter what on Note 3 TW the battery sucks. AOSP is great. But actually S5 port has the best battery.
Solved, at least for now.
nicholaschum said:
I heard there were problems with NF4 battery. But I haven't been on TW since ND4. No matter what on Note 3 TW the battery sucks. AOSP is great. But actually S5 port has the best battery.
Click to expand...
Click to collapse
I use Nova (and not TW)
Either way, latest nightly seems to solve the battery drain problem completely - using the same Nova and system configuration (widgets, active syncs, etc). Currently I'm at ~1.5-0.8%/h when idle with no issues going into deep sleep.
Seems that my specific model really dislikes NF4.
Thanks again for trying to help.
This thread has been quite helpful as I was suffering with a Battery Drain after the NF4 Upgrade.
Planning to go back to ND5, which was the last stable version.
JazonX said:
This thread has been quite helpful as I was suffering with a Battery Drain after the NF4 Upgrade.
Planning to go back to ND5, which was the last stable version.
Click to expand...
Click to collapse
I was thinking about doing the same, but in the CM 11 runs circles around both NF4 (duh!) and my previous ROM (not sure which revision it was) - plus I can actually get 2 days of standby time, even with the old batteries, so I'll stick with CM 11 for now.
- Gilboa
gilboa said:
I was thinking about doing the same, but in the CM 11 runs circles around both NF4 (duh!) and my previous ROM (not sure which revision it was) - plus I can actually get 2 days of standby time, even with the old batteries, so I'll stick with CM 11 for now.
- Gilboa
Click to expand...
Click to collapse
CM11 is not an option for me. No 4k Video Recording, Worse Camera than TW, S-Pen Functions Removed... Nope. Cant survive with CM11.
JazonX said:
CM11 is not an option for me. No 4k Video Recording, Worse Camera than TW, S-Pen Functions Removed... Nope. Cant survive with CM11.
Click to expand...
Click to collapse
I can relate.
Good luck, and post if you find a solution (in-case I decide to switch back to Samsung based).

Bad battery using unofficial CM13

I've tried using @MrColdbirds unofficial CM13. I'm still not allowed to post to the relevant forum so please bear with...
Whilst great respect is due for his work on this, I'm getting absolute garbage battery stats. I've flashed all of the required files, the updated firmware etc and have seen the battery prediction, even when not using the phone, decrease by roughly 100% compared to standard cos 12.1.
Many others claim fantastic battery life on the CM 13 and I'm wondering if anyone else has similar findings?
Of note was the fact that WiFi was way higher on the battery usage than anything else, like the WiFi wouldn't sleep even when phone sleeping.
I can't find anything obviously wrong as all settings were as per cos12.1 as far as WiFi sleep settings etc are concerned.
Anyone had similar, suggestions as to what I'm doing to get half battery life I'm used to?
I have marvelous battery life with the ROM, so I would assume it's some app that has a WiFi lock enabled that keeps the thing running. Could you post a wakelock detector log and maybe list your installed apps?
It seems to have settled down now. The screen on time also showed as 0% regardless of how long it had been used. Battery prediction now gone up to 1 day 1_23 hours as per cos ROM and deep sleep now fine.
Whatever had caused it may have been solved, a reflash was done.
Should it return I'll post a wakelock log but as of now thanks for your help but it has settled down for now.
Keep up this amazing work, many thanks.
Just realised the reflash was to latest build and as per your release notes I didn't flash the fingerprint reader packages. Without anything else changing I'd suspect my issues were around the fingerprint reader as others have also mentioned WiFi issues when the fingerprint reader package is installed.
Whatever, the latest setup running smooth and battery back to longevity.
I use unofficial and have a long battery life.

[RESEARCH] Mobile network standby drain (Oreo)

Since the first release of oreo I started using the rom as a daily driver, later on paired with a good kernel it had some good perfomance
But after some days of using the rom i started to notice a huge battery drain caused by the Mobile network standby process?
My battery was old (OEM 2014 battery) so i decided to revert back to lineageOS just after a couple of days where I haven't had any issues with that mobile network standby
Now I'm really curious what is causing this issue,drain because I am using the phone on the same settings as on 7.1 nougat, I am living in a country where all networks run on 3G,H+,2G etc. so no 4G if this can be a cause
Changed the network modes many times and tested throughout the days but there was no sucess the drain was still persist, tried updating,downgrading bootloaders swithing modems but again no sucess
If there, in the world of android is any solution, here is the thread to discuss about this issue. :fingers-crossed:
I've wondered this too. I've been running los15 on my g900v , I rooted and boot the first ROM that would work without having or remembering todomuch, I ran the first custom kernal I could find via google, and ran whatever was noted as the latest Verizon modems. its like right off the bat, smooth , consistent battery life and nice. Then the next day I noticed things would crash, my Bt temperamental at best and restarted it just to get by. if I have sync on at home, WiFi off, it just chills , if I turn sync off and drive around town, my battery life gets eaten by the unknown. I pulled some logs to see whats up with my BT but haven't got around to it yet. But my battery too is old (I literally found my s5 in the trash) and I run weird processes and tweak settings all the time just to mess with it, so that could be it to. If I see anything weird I'll let you know.
I'm struggling with this issue for months, since the first port of an Oreo custom ROM (LOS and RR) for the Galaxy A3 Duos (my device) started being developed.
From the beginning I had this problem, and what, since then, puzzles me the most is the fact that only some of us, flashing the same ROM in the same device, experience the issue. Whenever I flash any of those ROMs, even before installing any user apps (or when running in safe mode), the drain is there, which leads me to think that the culprit must be some setting: not an app, because I have none installed; not the ROM itself, because not everybody has this problem.
Unfortunately there seems to be no developers looking into this bug.
For the sake of information, I've observed two things that should help to narrow down the issue; or maybe not.
First, all the devices affected, as far as I've searched, are double SIM.
Second, the Mobile Network Standby (MNS from now on) drain is narrowy connected with the Bluetooth drain (which "also" occurs in Oreo). I've experienced the following: If, after a full charge, I don't switch on Bluetooth at all, then what drains my battery (according to Advanced Battery Usage information) is MNS. However, if I switch bluetooth on -even if only for one minute- then what apparentlyh drains my battery is Bluetooth, at the same speed as MNS did before switching bluetooth on.
Funny enough, the battery use info reports zero minutes activity for both Bluetooth and MNS. But how can a process which runs zero minutes drain 50% of the battery?? I'm afraid that the battery use information isn't reliable. But then that's very bad news, since, in such case, it might well happen that the real juice sucker is neither MNS nor Bluetooth!! We might be dealing with a "ghost" here, since we can't even trust the battery use information provided by the OS.
If someone has something with which to contribute to this research, or any ideas, please comment.
I'm having the same trouble on android 9 betas, even better, my phone gets without signal during those times and there's nothing I could do but rebooting the phone.
How can we help solve this? it looks like it's annoying a lot of people now

Modem WiFi issues and low battery performance issue on oreo b02

I finally decided to go public with my issues after trying to figure this out by myself for months. this is about wifi issues with the modem (any app that is loading something online, can't do anything because the phone doesn't send any up or download commands) and performance problems when the battery gets low (i think its either bad BCL driver or hotplug driver)
Modem issues.
I will try to explain this as best as i can and also hope that im not alone on this one.
Let me first talk about nougat b08 as that was the first time i have encountered the issue (on 2.4ghz networks only). And NO this is not because of interferances in my area or bad wifi channles or anything. Also it's only happening on my axon 7 (All other devices like my laptop, console etc are fine.
i noticed that any app/game when saying "connecting" (or any other indicator) the wifi icon at the top stays blank (meaning there are no up and down arrows for a period of time). This doesn't happen always but way too frequently to be a minor issue.
Let's take a few examples:
-chrome: when i try to open sites sometimes the loading bar stays at the left. Wifi icon doesn't show any up or downloads (the previous mentioned arrows).
-Sync (reddit client): loading circle spins and spins without any indication of any real progress. Again the wifi icon doesn't show anything happening either)
-XDA Labs: same thing here as in Sync.
-any game with internet connection required: Same thing again.
This often results in a connection error or timeout.
Reminder that this was while i was on nougat b08. This issue never happend in 5ghz but as i mentioned previously, this is not because of any 2.4 ghz interferances etc. here is why:
i fixed the whole issue by flashing the nougat b10 modem. Now the issue was fixed and i never ran into it again until Oreo b02.
This time tho the issue persists on both wifi bands (5ghz and 2.4ghz). The issues are exactly the same as in nougat b08 apart from 5ghz being affected now as well. Flashing the oreo b03 modem doesn't do anything since its the exact same. I also tried flashing the nougat b10 up to b12 modems but the nougat modems seem to break Calls. when i had the nougat modems installed on oreo, i couldn't hear the other person and they couldn't hear me. But they did fix the wifi issue (just tested again with nougat b10 modem)
so yeah thats the issue i have currently with the modems wifi stuff. i hope my explanation was somewhat understandable.
Low Battery Performance issue (starting between 50 and 40% battery left
Now this one is weird as idk what the real culprit is. I think its either a bad BCL driver or a bad Hotplugging driver.
Here is some info on BCL by @Infy_AsiX : https://forum.xda-developers.com/axon-7/how-to/degraded-battery-bcl-device-lag-t3752545
Now if you have read the linked BCL post, you should know that the device throttles the cpu if the voltage hits a certain low threshold which decreases performance big time.
I gotta say that my battery isn't degraded. Like not at all (aside from very little which is natural with any battery that gets older and older).
But the Voltage never drops below the 3.2-3.3 Volt threshold. in fact my voltage is over 3.5+ Volt at 15% battery left. fully charged its over 4.
The time when the phone starts to lag is around 50 to 40% remaining battery. the voltage there is around 3.7+ Volt which should not trigger the BCL to throttle my device.
So maybe the BCL driver is buggy i thought, so i tried disabling it through the shell but it stays/resets to enabled. So perhaps its locked by the kernel. i also tried editing the thresholds but they reset right after to their original value as well. rebooting doesn't help this. AND YES my device is rooted with the system write protection disabled so thats not the issue as i can freely modify any system file.
So i can't say for sure if BCL is buggy. If it isnt than its definetly not the culprit because i never hit the thresholds for it to start throttling in the first place.
And about Hotplugging, im not really sure if this is the culprit either. I only know that it can disable a certain number of cores at various scenarios which depends on how ZTE configured it. And idk how i can disable it through shell commands. If thats possible at all.
I will edit this post multiple times probably tomorrow (and will post a reply when i updated the OP and what i added) as im really tired. So bare with me for now if i couldn't explain something as good (and any possible typos)
I have also weird issues,does this look normal?it can't be ,it sit on 6% for like 20minutes now
Predatorhaze said:
I have also weird issues,does this look normal?it can't be ,it sit on 6% for like 20minutes now
Click to expand...
Click to collapse
Idk. But this isn't the same issue i described in the op. In the op i was talking about low battery performance issues which cause the device to lag heavily. Not about inaccurate percentages
GodOfPsychos said:
I finally decided to go public with my issues after trying to figure this out by myself for months. this is about wifi issues with the modem (any app that is loading something online, can't do anything because the phone doesn't send any up or download commands) and performance problems when the battery gets low (i think its either bad BCL driver or hotplug driver)
Modem issues.
I will try to explain this as best as i can and also hope that im not alone on this one.
Let me first talk about nougat b08 as that was the first time i have encountered the issue (on 2.4ghz networks only). And NO this is not because of interferances in my area or bad wifi channles or anything. Also it's only happening on my axon 7 (All other devices like my laptop, console etc are fine.
i noticed that any app/game when saying "connecting" (or any other indicator) the wifi icon at the top stays blank (meaning there are no up and down arrows for a period of time). This doesn't happen always but way too frequently to be a minor issue.
Let's take a few examples:
-chrome: when i try to open sites sometimes the loading bar stays at the left. Wifi icon doesn't show any up or downloads (the previous mentioned arrows).
-Sync (reddit client): loading circle spins and spins without any indication of any real progress. Again the wifi icon doesn't show anything happening either)
-XDA Labs: same thing here as in Sync.
-any game with internet connection required: Same thing again.
This often results in a connection error or timeout.
Reminder that this was while i was on nougat b08. This issue never happend in 5ghz but as i mentioned previously, this is not because of any 2.4 ghz interferances etc. here is why:
i fixed the whole issue by flashing the nougat b10 modem. Now the issue was fixed and i never ran into it again until Oreo b02.
This time tho the issue persists on both wifi bands (5ghz and 2.4ghz). The issues are exactly the same as in nougat b08 apart from 5ghz being affected now as well. Flashing the oreo b03 modem doesn't do anything since its the exact same. I also tried flashing the nougat b10 up to b12 modems but the nougat modems seem to break Calls. when i had the nougat modems installed on oreo, i couldn't hear the other person and they couldn't hear me. But they did fix the wifi issue (just tested again with nougat b10 modem)
so yeah thats the issue i have currently with the modems wifi stuff. i hope my explanation was somewhat understandable.
Low Battery Performance issue (starting between 50 and 40% battery left
Now this one is weird as idk what the real culprit is. I think its either a bad BCL driver or a bad Hotplugging driver.
Here is some info on BCL by @Infy_AsiX : https://forum.xda-developers.com/axon-7/how-to/degraded-battery-bcl-device-lag-t3752545
Now if you have read the linked BCL post, you should know that the device throttles the cpu if the voltage hits a certain low threshold which decreases performance big time.
I gotta say that my battery isn't degraded. Like not at all (aside from very little which is natural with any battery that gets older and older).
But the Voltage never drops below the 3.2-3.3 Volt threshold. in fact my voltage is over 3.5+ Volt at 15% battery left. fully charged its over 4.
The time when the phone starts to lag is around 50 to 40% remaining battery. the voltage there is around 3.7+ Volt which should not trigger the BCL to throttle my device.
So maybe the BCL driver is buggy i thought, so i tried disabling it through the shell but it stays/resets to enabled. So perhaps its locked by the kernel. i also tried editing the thresholds but they reset right after to their original value as well. rebooting doesn't help this. AND YES my device is rooted with the system write protection disabled so thats not the issue as i can freely modify any system file.
So i can't say for sure if BCL is buggy. If it isnt than its definetly not the culprit because i never hit the thresholds for it to start throttling in the first place.
And about Hotplugging, im not really sure if this is the culprit either. I only know that it can disable a certain number of cores at various scenarios which depends on how ZTE configured it. And idk how i can disable it through shell commands. If thats possible at all.
I will edit this post multiple times probably tomorrow (and will post a reply when i updated the OP and what i added) as im really tired. So bare with me for now if i couldn't explain something as good (and any possible typos)
Click to expand...
Click to collapse
are you sure modem = wifi? I really don't know, but I think they are separate, i.e. the modem file is probably only for cell connectivity
The battery stuff is a mess, but it's probably BCL... It was very badly set on stock G firmware when I had my G. Does your phone turn off if you set a very high CPU load like Gcam pics?
Choose an username... said:
are you sure modem = wifi? I really don't know, but I think they are separate, i.e. the modem file is probably only for cell connectivity
The battery stuff is a mess, but it's probably BCL... It was very badly set on stock G firmware when I had my G. Does your phone turn off if you set a very high CPU load like Gcam pics?
Click to expand...
Click to collapse
I think so at least since in nougat b08 i fixed that issue by using the nougat b10 modem.
It could also be that its just for cell connectivity like u said. But then is the question why it still interferes with wifi somehow.
About bcl. My phone never turned off. Yeah i tried getting a high load on cpu through various apps (like gcam, games, benchmark). But they all lag like hell because of some throttle on cpu and gpu. Not thermal throttling though as this only happens on the mentioned percentages (40-50%). And the voltages are not hitting the thresholds either
My wifi just random dissappears,mostly on pie gsi.When i try to download something trough wifi,wifi is disconnecting and then connects again...not able to download big files.And on 10% battery the voltage is 3.7+.This device knows a lot software issues.
Predatorhaze said:
My wifi just random dissappears,mostly on pie gsi.When i try to download something trough wifi,wifi is disconnecting and then connects again...not able to download big files.And on 10% battery the voltage is 3.7+.This device knows a lot software issues.
Click to expand...
Click to collapse
This thread is about stock oreo though. Not pie.
And 3.7+ voltage is perfectly fine and healthy for your battery at 10%.
I suggest you make your own thread with all the issues you encounter on your setup (rom, kernel etc) and try to give an explanation as detailed as possible.
Predatorhaze said:
My wifi just random dissappears,mostly on pie gsi.When i try to download something trough wifi,wifi is disconnecting and then connects again...not able to download big files.And on 10% battery the voltage is 3.7+.This device knows a lot software issues.
Click to expand...
Click to collapse
you using any custom kernel like kran's EAS? Those have those exact problems you mentioned
Choose an username... said:
you using any custom kernel like kran's EAS? Those have those exact problems you mentioned
Click to expand...
Click to collapse
No,but i was planning to flash the EAS version right now lol.
I did a clean flash ion gsi with hellsgate reborn sinister eas and the problem looks gone,or maybe not.Happens random but less then on bootleggers.
Clean flashed again latest bootleggers with schwifty r5 kernel and speedy vendor 5.1.Wifi also just random disconnects.But one thing i notice now,i charged my battery to 100% and unplugged it,it stays at 100%.Rebooted to twrp for transfer some files to my phone and it still sits on 100%.Booted system and still at 100%.I think its odd because most of the time when i unplug at 100 it drops directly to 99%.
---------- Post added at 06:23 AM ---------- Previous post was at 06:22 AM ----------
GodOfPsychos said:
This thread is about stock oreo though. Not pie.
And 3.7+ voltage is perfectly fine and healthy for your battery at 10%.
I suggest you make your own thread with all the issues you encounter on your setup (rom, kernel etc) and try to give an explanation as detailed as possible.
Click to expand...
Click to collapse
okay thanks,and sorry.We need a thread we can discuss everything
Finally found a command that works to disable bcl. Now gotta test for a few days if it solved the low battery performance issue.
I will update the OP once i confirmed it working
For anyone interested in trying it out (for stock oreo only!):
Requirements:
-you need to be rooted of course
-Selinux must be set to permissive. Otherwise terminal emulator doesn't work
-terminal emulator app (on playstore). Im using material terminal emulator
Type in:
su
echo -n disable > /sys/devices/soc/soc:qcom,bcl/mode
Don't reboot. This will revert the changes since those are kernel files (which are not real since they are temporary virtual files) and get loaded a new everytime at startup.
In short: bcl gets enabled again
Sidenote: most results after googling for disabling bcl all had false commands. Every one i found had the "-n" missing inside the command. At last an xda post for a sony xperia phone, had the right command. Funny how the only thing that was missing was entering "-n" after "echo"
Short update: Yes BCL was the culprit in my case and disabling it helped the low battery performance issue i was having. Also no sudden shutdowns for me (since my battery isn't degraded that much as previously stated). If you experience sudden shutdowns, don't worry. BCL gets re-enabled at every boot.
As for the wifi issues, i still haven't found a way to solve this problem.
Will edit the OP later.
Update on the bcl matter: right now it actually does seem my battery is degrading. The voltage readings jump up and down which shouldn't be happening. Perhaps this is the reason i thought my battery was fine since the voltage was fine when i checked it. But in reality it often jumps down and up randomly. This started to happen more often since yesterday
Disabling bcl worked without issues at first. But today i noticed that my battery has problems if i disable bcl. The percentage jumps down way too quick. It jumped from full charge to around 47% and stayed at that percentage for over an hour even tho i was actively using my phone (while the real percentage should have been higher since it hadn't used 53% in such a short time). So i guess the bcl lag i was experiencing was infact first symptoms of degradation of by battery.
I also had my first sudden shutdown at 9%
Its not certain tho yet. I ordered a new battery. Gonna replace it and then i will see if that really was the issue
GodOfPsychos said:
Its not certain tho yet.
Click to expand...
Click to collapse
Wow well i guess this answers that question (see screenshot)
1768mah at full charge. So yep, im so gonna change my battery
Battery health 56%...almost half.
Edit: i know accubattery is not THE most accurate way to show the actual degradation. But its a rough estimate. So the actual capacity could be slightly higher or lower. Nevertheless, it's still clear my battery is clearly degraded by now.
GodOfPsychos said:
Update on the bcl matter: right now it actually does seem my battery is degrading. The voltage readings jump up and down which shouldn't be happening. Perhaps this is the reason i thought my battery was fine since the voltage was fine when i checked it. But in reality it often jumps down and up randomly. This started to happen more often since yesterday
Disabling bcl worked without issues at first. But today i noticed that my battery has problems if i disable bcl. The percentage jumps down way too quick. It jumped from full charge to around 47% and stayed at that percentage for over an hour even tho i was actively using my phone (while the real percentage should have been higher since it hadn't used 53% in such a short time). So i guess the bcl lag i was experiencing was infact first symptoms of degradation of by battery.
I also had my first sudden shutdown at 9%
Its not certain tho yet. I ordered a new battery. Gonna replace it and then i will see if that really was the issue
Click to expand...
Click to collapse
I had these exacts same problems.Now with a new battery I have the idea the problem is still here

Categories

Resources