[I9100] Samsung Galaxy S2 battery problem on CyanogenMod 12.1 - Galaxy S II Q&A, Help & Troubleshooting

Hello everybody !
I have problem with my battery in S2 on CM 12.1 ... Battery is very weak, battery becomes flat very fast When I use apps like Instagram, Facebook, Snapchat battery 100% down in 15 minutes to 82%, when i use apps which need more power battery can down to 60% very fast.
I really don't know what I can do. I try used battery calibration applications and other such as but it gives no results. I try tried stop apps in backgrounds, turn off animations. Brightness is very low too.
Please help I need working S2 to my work where is a lot call but battery does not work with me.

Did you also try to modify the Privacy settings? There you can allow which apps are allowed to auto-launch, avoid that the phone goes in deep sleep etc. Also see the "advanced" option there. Check that Location etc. is disabled.
Sometimes there appear problems that can be solved with a new, clean flash. If nothing helps, think about buying a new battery.
BTW, I have the feeling that the percentage of battery isn't very accurate. Sometimes the battery seems to drain very fast, and later it stays the same for half an hour. Perhaps just ignore it.

Try Greenify, it will help save battery when your device is locked.

BenjyTec said:
Did you also try to modify the Privacy settings? There you can allow which apps are allowed to auto-launch, avoid that the phone goes in deep sleep etc. Also see the "advanced" option there. Check that Location etc. is disabled.
Sometimes there appear problems that can be solved with a new, clean flash. If nothing helps, think about buying a new battery.
BTW, I have the feeling that the percentage of battery isn't very accurate. Sometimes the battery seems to drain very fast, and later it stays the same for half an hour. Perhaps just ignore it.
Click to expand...
Click to collapse
I tried this. Battery in my S2 is not broken for sure ! I do not remember behavior battery when i haved stock ROM :/ :laugh:

Kevin3014 said:
Try Greenify, it will help save battery when your device is locked.
Click to expand...
Click to collapse
I using this program. Yee its good app but little correct my battery :/ Hmm... I think I can install other kernel or back to older version CM but CM 11 and older is not good for me

Had similiar problems with CM12.1. But I assumed that I've caused it myself with my app usage and hadn't the time and didn't want to search for the culprit. Now I am on CM13 and hoped that the clean flash would solve my problem. Didn't do it so I invested some time reading many things about Better Battery Stats and its usage.
You should also try to record your App behaviour when the screen is off then we could see if our problems are the same
Did a clean record with airplane mode (with BBS) last night and got nice results
===========
Other Usage
===========
Deep Sleep (): 8 h 11 m 20 s 99.5%
Awake (Screen Off) (): 1 m 40 s 0.3%
Screen On (): 35 s 0.1%
Wifi On (): 0.0%
Wifi Running (): 0.0%
No Data Connection (): 8 h 13 m 36 s 100.0%
No or Unknown Signal (): 8 h 13 m 36 s 100.0%
Screen dark (): 35 s 0.1%
Click to expand...
Click to collapse
I would say that this result shows me that it is not my battery. The nights before I did some tests with settings I normally use: wifi always on/wifi off if not in use.
Results were not nearly as good as before
===========
Other Usage
===========
Deep Sleep (): 6 h 44 m 32 s 86.3%
Awake (Screen Off) (): 1 h 3 m 14 s 13.5%
Screen On (): 47 s 0.2%
Wifi On (): 7 h 48 m 34 s 100.0%
Wifi Running (): 18 m 6 s 3.9%
No Data Connection (): 6 m 2 s 1.3%
No or Unknown Signal (): 6 m 2 s 1.3%
Good Signal (): 1 m 57 s 0.4%
Screen dark (): 47 s 0.2%
Click to expand...
Click to collapse
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
GCM_CONN_ALARM (Google-Dienste): 7 m 49 s Count:112 1.7%
SnetLaunchService (Google-Dienste): 1 m 55 s Count:143 0.4%
bluedroid_timer (com.android.bluetooth.Bluetooth-Freigabe): 42 s Count:62 0.1%
...
================
Kernel Wakelocks
================
"multipdp" (): 37 m 6 s Cntc/wc/ec)326/0/326 7.9%
"secril_fd-interface" (): 34 m 24 s Cntc/wc/ec)597/0/0 7.3%
"PowerManagerService.WakeLocks" (): 13 m 55 s Cntc/wc/ec)1056/0/0 3.0%
....
======================================================
Processes (requires root / system app on Android 4.4+)
======================================================
logd (0): Uid: 0 Sys: 1 m 18 s Us: 17 m 37 s Starts: 0
system (CyanogenMod-System): Uid: 1000 Sys: 7 m 42 s Us: 11 m Starts: 0
com.microsoft.office.outlook (com.microsoft.office.outlook.Outlook): Uid: 10069 Sys: 2 m 13 s Us: 3 m 8 s Starts: 0
....
======================
Alarms (requires BATTERY_STATS permissions)
======================
com.google.android.gms (): Wakeups: 133 (17.1 / h)
com.android.phone (): Wakeups: 65 (8.3 / h)
com.android.bluetooth (): Wakeups: 36 (4.6 / h)
...
==========
CPU States
==========
1.2 GHz (): 1 m 57 s 0.4%
1 GHz (): 11 s 0.0%
800 MHz (): 4 m 21 s 0.9%
500 MHz (): 5 m 3 s 1.1%
200 MHz (): 52 m 28 s 11.2%
Deep Sleep (): 6 h 44 m 32 s 86.3%
Click to expand...
Click to collapse
With my current knowledge I would say that some apps often trigger the google push service (GCM_CONN_ALARM & com.android.google.gms - if I am not mistaken) and this service will wake the phone and the google service will download some data for the apps. But even if this is correct I cannot find a way to analyse which apps are the culprits. I tried with catlog but did not find anything I would understand and bind to my problem

Related

[Q] Which ROM is the bast for your battery?

My battery can be use only 1/2 day (from 1-2 days) after I put android ROM into my phone.
Thank you very much.
--------------------------------------
Sorry, bast=best
My favorite is mccmjoon76 build 2.5 with 2.14 Radio Rom & VBNROM Reloaded, michyprima's r11 AXI.
Battery lasts 35-40 h in normal use. (30 min Nav, 30 min surfing, twitter, email, mms, 20 min games, double checking time every hour
Set CPU settings: 998 max -> 245 min conservativ.
screen off: 576 max -> 254 min
screen brightnes about 30%
i think in these settings the device consumes less energy than with stock WM 6.5

How do I stop google c2dm

Since charging my phone this has been on wakelock since unplugging and it's draining my battery unplugged for 1hr 50 mins c2dm has been awake for 1hr 48 mins and battery has gone down to 78 per cent already nothing else has been using anything apart from screen on 7 mins
Sent from my GT-I9100 using XDA Premium App
Turn off background data and don't use anything that uses c2d.
Sent from my GT-I9100 using xda premium
it's never taken this much I have background data on all time and with phone screen off and same settings I've used for last 3 months battery normally takes at least 6 hr to get as low as that with screen off
Sent from my GT-I9100 using XDA Premium App
Reboot should fix it.
i have rebooted but still it is in use..... any solution to stop c2dm?
infra4800 said:
i have rebooted but still it is in use..... any solution to stop c2dm?
Click to expand...
Click to collapse
Hello,
was there any solution?
Got the same Problem with a S II from a friend.
Over Night the battery goes down to 30%.
Gsam Battery told me the c2dm with 8h wakelock.
:-/
the same with tab3
I am having the same problem with this Tab 3 (Kitkat) - I tried another custom rom, etc. nothing helped.
"GSam Labs - Battery Monitor" says in its Analysis:
Kernel (Android OS)
25 Feb 2016 10:23:58
Usage Details
CPU Usage:2h 58m 31s
CPU Usage (Background Only):2h 58m 31s
Keep Awake:21h 55m 17s
Number of Wake Locks:145
Bytes Sent:103.61 KB
Bytes Received:431.05 KB
App UID:0
Wakelock Detail
GOOGLE_C2DM24.3s(145)
Included Packages
Included Processes
ksdioirqd/mmc2
vold
migration/1
file-storage
tmp-mksh
ecryptfs-kthrea
daemonsu:10113
MOAL_WORK_QUEUE
kworker/u:4
kworker/u:3
daemonsu:10035
kworker/u:5
kthreadd
loop0
kworker/0:0
kworker/u:0
kworker/0:1
kworker/u:2
kworker/0:2
kworker/0:3
kworker/u:1
bdi-default
daemonsu:mount:master
daemonsu:master
toolbox
kcryptd_io
flush-254:0
sh
*wakelock*
jbd2/mmcblk0p6-
kdmflush
ueventd
jbd2/mmcblk0p14
jbd2/mmcblk0p15
jbd2/mmcblk0p12
debuggerd.real
daemonsu:10113:3169
jbd2/mmcblk0p16
jbd2/mmcblk0p17
mmcqd/0boot0
krtccd
mmcqd/0boot1
ext4lazyinit
kswapd0
flush-179:72
galcore daemon
daemonsu:10084
woal_reassoc_se
/init
ksoftirqd/0
ksoftirqd/1
daemonsu:10113:2584
flush-0:18
irq/36-88pm800
irq/222-bt532_t
mmcqd/1
irq/73-GFX Laye
app_process
netd
mmcqd/0
watchdog/0
watchdog/1
zygote
kworker/1:2
flush-0:21
flush-179:0
kworker/1:1
kworker/1:0
kcryptd
daemonsu:10035:9528
healthd
workqueue_trust
fsck_msdos
MOAL_RX_WORK_QU
ext4-dio-unwrit
sync_supers
I THINK THAT THE CAUSE MUST BE SOME HARDWARE-RELATED THING - the screen is flickering all the time - despite changing settings in brightness, etc.:cyclops:

[Q] new gMaps with offline tiles - white screen / ray 18i / cwm / cm7.2

xperia ray with gingerbread cyanogen mod 7.2.
somewhere along my travels the maps app 6.2.x or so, has stopped working. when i start it, i get a white screen then nothing happens. sometimes it force-closes on its own, other times i have to kill it. map never shows up.
if i install older versions that do NOT have the option of storing offline maps, they do work. this leads me to believe that something may be wrong with the downloaded map tiles. i'm unable to figure out where in the phone they're stored - and not 100% if that could be the root of the trouble.
how to troubleshoot / fix?
below a chunk of logcat:
12-23 22:08:58.782 I/InputDispatcher(434): Application is not responding: Window{2b4a9f00 com.google.android.apps.maps/com.google.android.maps.MapsActivity paused=false}. 5001.1ms since event, 5001.0ms since wait started
12-23 22:08:58.782 I/WindowManager(434): Input event dispatching timed out sending to com.google.android.apps.maps/com.google.android.maps.MapsActivity
12-23 22:09:00.072 E/ActivityManager(434): ANR in com.google.android.apps.maps (com.google.android.apps.maps/com.google.android.maps.MapsActivity)
12-23 22:09:00.072 E/ActivityManager(434): +0% 4139/com.google.android.apps.maps: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): +0% 4186/com.google.android.apps.maps:GoogleLocationService: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): +0% 4202/com.google.android.apps.maps:FriendService: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): +0% 4211/com.google.android.apps.maps:LocationFriendService: 0% user + 0% kernel
12-23 22:09:00.072 E/ActivityManager(434): 3% 4186/com.google.android.apps.maps:GoogleLocationService: 3% user + 0% kernel / faults: 125 minor
12-23 22:09:00.072 E/ActivityManager(434): 1.5% 4139/com.google.android.apps.maps: 1.5% user + 0% kernel / faults: 46 minor
12-23 22:09:00.812 W/ActivityManager(434): Activity idle timeout for HistoryRecord{2b4ff668 com.google.android.apps.maps/com.google.android.maps.MapsActivity}
12-23 22:09:02.802 W/ActivityManager(434): Force finishing activity com.google.android.apps.maps/com.google.android.maps.MapsActivity
12-23 22:09:02.802 I/ActivityManager(434): Killing com.google.android.apps.maps (pid=4139): user's request
12-23 22:09:02.832 I/ActivityManager(434): Process com.google.android.apps.maps (pid 4139) has died.
12-23 22:09:02.832 I/WindowManager(434): WIN DEATH: Window{2b4a9f00 com.google.android.apps.maps/com.google.android.maps.MapsActivity paused=true}

Overheating and Battery Drain

My Samsung Galaxy S2 i9100 gets really hot (near the camera area) and the battery drains really fast. I'm running CM13, Android Marshmallow 6.0.1. Any help on how to reduce the heat and lower battery drain would be greatly appreciated, thank you!
We cant fight the heat on S2 anymore. Is just too old phone(almost 5 year old). You need to live with that.
Sent from my GT-I9100 using Tapatalk
Media scanner going nuts??
Sent from my SM-G920F using Tapatalk
I also suspect some media service being the culprit. When I play music with the CM music app, the battery drains extra fast. Here's what top reports:
User 36%, System 11%, IOW 0%, IRQ 0%
User 113 + Nice 7 + Sys 37 + Idle 170 + IOW 0 + IRQ 0 + SIRQ 1 = 328
PID PR CPU% S #THR VSS RSS PCY UID Name
1929 0 35% S 20 102072K 9396K fg media /system/bin/mediaserver
1853 0 2% S 7 11112K 3356K bg logd /system/bin/logd
10163 0 2% R 1 2172K 1000K fg shell top
2371 0 1% S 103 914396K 93388K fg system system_server
Can this mediaserver be disabled or is it responsible for too many tasks, e.g. also ring tone? I would replace the stock music app with VLC. IIRC, it uses its own sound backend. But I may be mistaken.
---------- Post added at 10:09 AM ---------- Previous post was at 09:41 AM ----------
I found some posts that may be related:
http://forum.xda-developers.com/nexus-4/general/how-to-avoid-battery-draining-media-t2079879
http://androidforums.com/threads/my...drain-within-hours.481966/page-3#post-4344054

Swift 2 Plus drains the battery after using the main camera. Help!

I ask for help! My Swift 2 Plus, after using the main camera, the phone starts to consume 10-15% per night, if you restart the phone after using the camera - 0-1% per night. WLD logs do not show any gaming processes, hence Greenify does not help.
Third-party camera applications also do not solve the problem
As a temporary solution - restart the phone after taking pictures.
How to solve this problem?
My stats for 2 nights below
For the time of the experiment I never connected the charge \ of computers, I did not change any settings in the phone, I did not set any applications, the state of all sensors \ radio \ gps \ nfc \ bt \ wifi \ sync \ is one-to-one. Did so:
The first night: before going to bed I reset the phone, opened the camera, took a couple of pictures, put a custom label in BetterBatteryStats and went to bed. woke up - immediately saved the log from the user label to the current one.
The second night: before going to bed I reset the phone, put a custom label in BetterBatteryStats and went to bed. woke up - immediately saved the log from the user label to the current one.
Total face: 1.5% per hour drains after using the camera, against 0.1% per hour without camera
After using the camera:
/*
===================
General Information
===================
BetterBatteryStats version: 2.2.2.0
Creation Date: 2018-01-12 05:25:31
Statistic Type: Custom to Current
Since 7 h 34 m 5 s
Note:
VERSION.RELEASE: 7.1.2
BRAND: Wileyfox
DEVICE: marmite
MANUFACTURER: Wileyfox
MODEL: SM-N920C
OS.VERSION: 3.18.31-g6377f87
BOOTLOADER: marmite-N-ge8bbd8f
HARDWARE: qcom
FINGERPRINT: Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys
ID: N2G48B
TAGS: release-keys
USER: jenkins
PRODUCT: Swift2
RADIO: 937_GENNS_PACK-1.83666.1.89031.1
Root perms: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -11%(94% to 83%) [1,5%/h]
Voltage lost [mV]: (4151-4108) [5,7%/h]
===========
Other Usage
===========
Deep Sleep (): 7 h 26 m 31 s 98,3%
Awake (Screen Off) (): 7 m 8 s 1,6%
Screen On (): 25 s 0,1%
Wifi On (): 17 m 4 s 3,8%
Wifi Running (): 27 m 34 s 6,1%
Doze Interactive Time (): 24 s 0,1%
Sync (): 8 s 0,0%
Screen dark (): 0,0%
Screen medium (): 25 s 0,1%
======================================================
Without using the camera:
/*
===================
General Information
===================
BetterBatteryStats version: 2.2.2.0
Creation Date: 2018-01-13 07:55:30
Statistic Type: Custom to Current
Since 10 h 54 m 19 s
Note:
VERSION.RELEASE: 7.1.2
BRAND: Wileyfox
DEVICE: marmite
MANUFACTURER: Wileyfox
MODEL: SM-N920C
OS.VERSION: 3.18.31-g6377f87
BOOTLOADER: marmite-N-ge8bbd8f
HARDWARE: qcom
FINGERPRINT: Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys
ID: N2G48B
TAGS: release-keys
USER: jenkins
PRODUCT: Swift2
RADIO: 937_GENNS_PACK-1.83666.1.89031.1
Root perms: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -1%(50% to 49%) [0,1%/h]
Voltage lost [mV]: (3820-3836) [-1,5%/h]
===========
Other Usage
===========
Deep Sleep (): 10 h 48 m 3 s 99,0%
Awake (Screen Off) (): 5 m 56 s 0,9%
Screen On (): 19 s 0,0%
Wifi On (): 15 m 59 s 2,4%
Wifi Running (): 16 m 1 s 2,4%
Doze Interactive Time (): 18 s 0,0%
Sync (): 7 s 0,0%
Screen dark (): 0,0%
Screen medium (): 19 s 0,0%
======================================================
Interesting, but I hardly ever use the camera and I also have some nights where my phone loses about 20% and others where my phone loses only a couple (say, 5%). It cannot be ONLY due to the camera. I haven't been able to find out what's up, but a reboot every now and then keeps me performing ok.
Up
I'm thinking it's a camera software issue? I guess only an update with a patch could fix that.
Running Unofficial LineageOS 14.1.
The battery drainage in idle mode is about 3 times higher than normal after I use the camera.
Hello!
I see that there is no recent activity in this thread, but I hope to get some help...
I have Wileyfox Swift 2 and Swift 2 Plus phones. Swift 2 Plus has the battery drain possibly related to its camera usage. I tried to flash and use it with stock Android Nougat and Oreo as well as with unofficial Lineage 15 ROMs. Unfortunately, the battery drain appears with all of these ROMs. The only one solution I found is to restart the phone...
Did you have any other solutions or additional information?
Interesting that Swift 2 doesn't have this issue.
Thank you!

Categories

Resources