• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help . Battery or Hardware problem ?

Hey guys .

My phone suddenly keep drain too much even on DEEP SLEEP . I charged 100% overnight 7hours after I woke up already 10% or less left :(

I flashed stock ROM as NeatROM 4.1.2 from 4.2.2. But the battery drain issue still here.

Is it hardware problem ? Or battery problem and need to change a new battery?

The battery had used one year and half already when I bought the S2 on that time untill now. (Never change a new one)

Even on flight mode also same :(
 

Attachments

Hey guys .

My phone suddenly keep drain too much even on DEEP SLEEP . I charged 100% overnight 7hours after I woke up already 10% or less left :(

I flashed stock ROM as NeatROM 4.1.2 from 4.2.2. But the battery drain issue still here.

Is it hardware problem ? Or battery problem and need to change a new battery?

The battery had used one year and half already when I bought the S2 on that time untill now. (Never change a new one)

Even on flight mode also same :(

Hello and welcome to Android Forums SilenceOfH! :)

It would appear that you are only getting 0.5% Deep Sleep, mine is about 97%. Therefore I believe it is a wakelock and not hardware or battery.

You can either start looking at your wakelocks, see here, or take the following, draconian but effective, steps...

1. Format USB and External memories.

2. Factory reset phone.

3. Flash a stock Samsung JB firmware using Odin. Reboot.

4. Flash NEAT ROM LSS, full or lite.

5. Flash Siyah kernel 6.0beta4 or stick with PhilZ kernel that the ROM comes with. Not Apolo, to begin with.

6. Re-install app's from Play Store. DO NOT use Titanium backup to restore either app's or settings.

This will ensure a clean, "vanilla", install of all your app's and settings.
 
Hello and welcome to Android Forums SilenceOfH! :)

It would appear that you are only getting 0.5% Deep Sleep, mine is about 97%. Therefore I believe it is a wakelock and not hardware or battery.

You can either start looking at your wakelocks, see here, or take the following, draconian but effective, steps...

1. Format USB and External memories.

2. Factory reset phone.

3. Flash a stock Samsung JB firmware using Odin. Reboot.

4. Flash NEAT ROM LSS, full or lite.

5. Flash Siyah kernel 6.0beta4. Not Apolo, to begin with.

6. Re-install app's from Play Store. DO NOT use Titanium backup to restore either app's or settings.

This will ensure a clean, "vanilla", install of all your app's and settings.

Thanks Mate!
And How about this BBS ? deep sleep on 99.7% .
Or also same, Just do the steps that you teach me ? :confused:
 

Attachments

Thanks Mate!
And How about this BBS ? deep sleep on 99.7% .
Or also same, Just do a steps that you teach me ? :confused:

To be honest... I have not got the time to go through BBS logs mate. ;)

However, if you are now saying that you are getting 99.7% Deep Sleep overnight, then that is amazing and it must be a battery problem. Try re-calibrating it as follows:-

The Best Way to Calibrate our S2 Battery ! [No root needed, Simple, Accurate]

See if that helps, first. If not, you may need to take your phone to a Samsung Service Point and ask them to check the battery for you or, simply get another one.
 
To be honest... I have not got the time to go through BBS logs mate. ;)

However, if you are now saying that you are getting 99.7% Deep Sleep overnight, then that is amazing and it must be a battery problem. Try re-calibrating it as follows:-

The Best Way to Calibrate our S2 Battery ! [No root needed, Simple, Accurate]

See if that helps, first. If not, you may need to take your phone to a Samsung Service Point and ask them to check the battery for you or, simply get another one.

Sorry mate :D
Because I had did some test and do the bbs log. Some of bbs log deep sleep was 98%/97% , So really not sure what issue on my phone.
 
Hey guys :)

Here is my latest bbs log with NeatROM v4.7 and kernel with XWLSS-v5.00.4-PhilZ. I'm re-flashed the ROM with Gs2ROMwipe , After I just re-install apps from play store (Only install few apps that I always used, Haven't install all) , Never use TB . Just use TB for freezer some apps.

BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-16 07:51:04
Statistic Type: Unplugged to Current
Since 7 h 8 m 2 s
VERSION.RELEASE: 4.1.2
BRAND: Samsung
DEVICE: GT-I9100
MANUFACTURER: samsung
MODEL: GT-I9100
OS.VERSION: 3.0.31-1156082
BOOTLOADER: unknown
HARDWARE: smdk4210
FINGERPRINT: samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XWLSS:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: dpi
PRODUCT: GT-I9100
RADIO: I9100XXMS2
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -78% (100% to 22%) [10.9%/h]
Voltage lost [mV]: (4181-3678) [70.5%/h]
===========
Other Usage
===========
Deep Sleep (): 7 h 5 m 24 s (25524 s) Ratio: 99.4%
Awake (): 2 m 38 s (158 s) Ratio: 0.6%
Screen On (): 33 s (33 s) Ratio: 0.1%
No Data Connection (): 7 h 8 m 2 s (25682 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 8 m 2 s (25682 s) Ratio: 100.0%
Screen dark (): 33 s (33 s) Ratio: 0.1%
=========
Wakelocks
=========
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 4 s (4 s) Count:2 0.0%
AlarmManager (Android System): 4 s (4 s) Count:100 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:30 0.0%
PhoneWindowManager.mBroadcastWakeLock (Android System): 2 s (2 s) Count:28 0.0%
================
Kernel Wakelocks
================
"l2_hsic" (): 55 s (55 s) Cnt:(c/wc/ec)104/29/104 0.2%
"alarm_rtc" (): 38 s (38 s) Cnt:(c/wc/ec)57/0/22 0.2%
"radio-interface" (): 38 s (38 s) Cnt:(c/wc/ec)41/0/0 0.1%
"sec-battery-monitor" (): 35 s (35 s) Cnt:(c/wc/ec)85/50/0 0.1%
"alarm" (): 25 s (25 s) Cnt:(c/wc/ec)104/0/0 0.1%
"umts_ipc0" (): 25 s (25 s) Cnt:(c/wc/ec)51/0/51 0.1%
"PowerManagerService" (): 11 s (11 s) Cnt:(c/wc/ec)97/0/0 0.0%
"mmc1_detect" (): 6 s (6 s) Cnt:(c/wc/ec)97/0/0 0.0%
"rpm_hsic" (): 1 s (1 s) Cnt:(c/wc/ec)12/0/0 0.0%
"power-supply" (): 1 s (1 s) Cnt:(c/wc/ec)57/0/0 -0.0%
"sync_system" (): (0 s) Cnt:(c/wc/ec)3/0/0 0.0%
"tx_hsic" (): (0 s) Cnt:(c/wc/ec)196/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)250/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)132/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)97/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.apps.maps (): Wakeups: 30
Alarms: 29, Intent: com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
Alarms: 0, Intent: com.google.android.apps.maps.nlp.ALARM_WAKEUP_ACTIVE_COLLECTOR
Alarms: 1, Intent: com.google.android.apps.maps.nlp.ALARM_WAKEUP_CACHE_UPDATER

com.google.android.gsf (): Wakeups: 15
Alarms: 0, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 0, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 0, Intent: com.google.android.intent.action.SEND_IDLE

com.google.android.gms (): Wakeups: 3
Alarms: 1, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_CACHE_UPDATER
Alarms: 1, Intent: com.google.android.gms.recovery.WAKEUP
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE

android (): Wakeups: 1
Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 53, Intent: android.intent.action.TIME_TICK
Alarms: 14, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 29, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 0, Intent: android.app.backup.intent.RUN
Alarms: 1, Intent: android.content.syncmanager.SYNC_ALARM

com.google.android.location (): Wakeups: 1
Alarms: 1, Intent: com.google.android.location.nlp.ALARM_WAKEUP_CACHE_UPDATER

======================
Network (requires root)
======================
==========
CPU States
==========
1.2 GHz (): 10 s 0.0%
1 GHz (): 1 s 0.0%
800 MHz (): 1 m 11 s 0.3%
500 MHz (): 10 s 0.0%
200 MHz (): 1 m 4 s 0.3%
Deep Sleep (): 7 h 5 m 24 s 99.4%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 1 d 2 h 29 m 41 s (Wl: 0 elements; KWl: 24elements; NetS: 21 elements; Alrm: 7 elements; Proc: 0 elements; Oth: 6 elements; CPU: 6 elements)
ref_charged: Reference ref_charged created 1 d 2 h 29 m 42 s (Wl: 1 elements; KWl: 24elements; NetS: 21 elements; Alrm: 7 elements; Proc: 0 elements; Oth: 6 elements; CPU: 6 elements)
ref_current: Reference ref_current created 1 d 9 h 37 m 44 s (Wl: 4 elements; KWl: 24elements; NetS: 21 elements; Alrm: 7 elements; Proc: 1 elements; Oth: 6 elements; CPU: 6 elements)




How about this bbs log guys ? :confused:
Is it need to change a new battery? Hardware problem? or need factory reset my phone?
I need a answer because tomorrow I gonna do that.


Cheers.
Take care
 

Attachments

Back
Top Bottom