Hello, I have installed BetterBatteryStats and CPU SPY, because I noticed that I had a faster than normal battery consumption when the tab was left alone.
I made a 30 mins test Wifi OFF, Flight Mode On, where the 29 mins of them showed me l2_hsic under Kernel Wakelock -> Since Unplugged.
Does anyone know what causes this and how to prevent it ?
Thank you.
( I am running Stock ICS 4.0.4 rooted)
Same problem here.
I am also having this issue as well using stock ics.
Hopefully someone might have an idea on solving this issue.
seems its a bug in 4.03 or 4.04 Roms , I searched internet and could not find any solution , The idea is this kernel wakelock is caused by some settings related issues like gps or wife or... , now I'm doing some investigation and try to find the root cause, however I wish an expert could bring some solution here
As I promised to report here is what I experienced:
My Tablet is P7500 and I did wipe , remove many applications , put in flight mode , disable this and that ,..... none of them where effective
and finally:
2 weeks ago I removed my simcard from tablet , Just to try to solve the issue I reinsert the sim and as you can see in attachment after around 45 minutes no l2_hsic wakelock .
what I mentioned above doesnt mean everybody have the same issue but I think its related to the sim and network discovery because during last 2 weeks I received notification in my status bar that says can not find network although it was on flight mode
taha_e said:
As I promised to report here is what I experienced:
My Tablet is P7500 and I did wipe , remove many applications , put in flight mode , disable this and that ,..... none of them where effective
and finally:
2 weeks ago I removed my simcard from tablet , Just to try to solve the issue I reinsert the sim and as you can see in attachment after around 45 minutes no l2_hsic wakelock .
what I mentioned above doesnt mean everybody have the same issue but I think its related to the sim and network discovery because during last 2 weeks I received notification in my status bar that says can not find network although it was on flight mode
Click to expand...
Click to collapse
You said 2 weeks ago you removed simcard from tablet and no more l2_hsic wakelock. Is your problem solved permanently?
l2_hsic
sooramma said:
You said 2 weeks ago you removed simcard from tablet and no more l2_hsic wakelock. Is your problem solved permanently?
Click to expand...
Click to collapse
Hi,
I have the exact same problem.
Tried all possible solutions with no result.
The only way is to let the Flight mode OFF, at least in my case, with stock rom TPH, WLP5.
I'm going nuts with this problem.
Yesterday I thought I had found the problem. DId several tests of getting in and out of the Flight Mode and everything was looking perfect, 5 & 6 hours of deep sleep. Then i connected a usb flash drive, that apparently also causes a kernel problem (see other posts about usb unmount). Rebooted the Tablet to solve the problem and here i go again with the l2_hsic preventing the device to deep sleep....:crying:
Hello,
I have the exact same problem and it's driving me crazy. Was anyone able to find out something new?
Thanks,
hugo.
A Custom ROM is the Solution
Hey guys, I am also a proud owner of the Galaxy Tab 10.1 GT-P7500 but unfortunately, Samsung forgot about their flagship tablet and screwed up the kernel in an otherwise utterly awesome ICS Update. The only method to solve this problem is flashing another ROM no other go. This fixed the Deep Sleep issue for me, 12 and a half hours and I'm only down to 96%. So I suggest you Root your tab ( Instructions in this link:http://www.youtube.com/watch?v=kBd9gMFCCrA ) and flash Toldo's JellyBeanRom ICS v6 ( This link:http://forum.xda-developers.com/showthread.php?t=1813651 ) and then enjoy the great Honeycomb battery standby on ICS (If you can't understand how to flash the ROM PM me :good
Happy Flashing Guys
i have toldo jellybeanrom v6 already flashed few weeks ago.. nothings changed, battery drain still remaining.
The problem is still there. AOKP 4.1.1 JellyBean, P7500 with sim card in. Same on CM10.
BTW. This is not a system issue (ICS or JellyBean). Rather something wrong in the kernels that come from Samsung. On my HTC One X (ICS) there is no such issue. Maybe some skilled developer could look at the difference in the source of this module between HOX and P7500?
Originally Posted by funky81
After search codes in the kernel related with this problem, I've found out the conclusion is that this wild uncontrolled wake lock related with data communication (modem)
Code:
./drivers/misc/modem_if/modem_link_device_hsic.c:wake_lock_init(&pm_data->l2_wake, WAKE_LOCK_SUSPEND, "l2_hsic");
I will try to update the code w/ Samsung Galaxy S3 source code in my kernel...
I will inform you if there's any progress with this
Click to expand...
Click to collapse
Related
Greetings from (cloudy) Germany. Many battery problem threats exist in this forum and the world wide web. Unfortunately most of them reach hundreds of pages and after the 3rd or 4th page it slides away from any technical discussion and becomes very emotional. This is the reason why i´m going to open another one, which hopefully helps me. So here is my ....
... frame what happened:
I own a SGS2 GT-I9100, branding free. It´s almost half a year old. When i bourght it, it came with GB 2.3.4 which worked fine for me. At the beginning of this month i recived ICS via Kies. As a result of this update my phone became super slow. Almost all applications hung and chrashed. So i decited to manually go back to an older FW. I´ve choosen GB 2.3.5, as the look and feel was better for me, then 2.3.4.
... Problem:
Since i did the update to 4.0.3 my battery performance is 10 times worse in ->standby<- as it was with 2.3.4.
... what i did so for, to isolate the problem:
Many threads talk about an Android OS bug. After a long search it is still not clear to me, what this bug excatly means!?!? Apps, which drain the battery are not installed (there are no special Apps installed, except the ones which come with the FW). I have no widgets running and the phone is in Airplane mode. If is switch off the phones display i loose about 30% battery during one night (8 - 9 hours). With 2.3.4 it was about 3% per night. If i use my phone during the day (SMS, Calls, Wireless, 3G and music) it does not increase the battery usage very much. maybe 40% per 8 - 9 hours. I did a factory reset to my phone, installed cpu spy and switched the display off. Analysis show 99% Deep Sleep. nevertheless it uses 30% battery during this time.
In summary:
- German GB 2.3.4 got an update from K.I.E.S. to ICS 4.0.3 -> bad phone performance and battery drained
- Downgrade from German ICS 4.0.3 to German GB 2.3.5 following a procedure and firmware from android-galaxy dot info
- With GB 2.3.5 the performance returned back to normal but battery was still bad.
- Installed German GB following a procedure and firmware from android-galaxy dot info
- Performance was still good, but battery drained.
- Installed netherlands GB 2.3.5 and battery was still draining.
- Received ICS 4.0.3 via software update. Fortunately the phones performance is still very good but the battery drains anyway.
All test where performed without any app installed and in flight mode.
Questions:
1. what ist the so called Android OS bug in connection with battery problems?
2. does anybody have the same problem and solved it?
3. is there any way to recive the stock rom, which came with my phone?
-> a friend of mine have the same SGS2 with GB 2.3.4 and without any battery problem.
Thanks for constructive, helpfull and unemotional technical feedback. If you have further question, send me a PN. I´ll summarize them, and add them to this post. It will keep it clearly and in coherence.
Why not rename General forum Q&A then users wont break the rules .
1. what ist the so called Android OS bug in connection with battery problems?
No search ???? read the Android OS Bug Post .
2. does anybody have the same problem and solved it?
Long time ago Android 2.3.6 .
3. is there any way to recive the stock rom, which came with my phone?
YES if you know what it was and can search for it .
BASICS
FAQ
http://forum.xda-developers.com/showthread.php?t=1065995
NEW HERE
http://forum.xda-developers.com/showthread.php?t=1134290
bible
http://forum.xda-developers.com/showthread.php?t=1473577
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
Thanks for your quick reply. I found many things for "Android OS Bug", also solutions. For example: "Disable widgets" or "stop wireless sharing". Unfortunately nothing helped me.
If you kow about the same problem with the battery and how to solve it, please tell me. I searched for it and was not successful.
I know the page for Stock Roms and how to apply them. As you can read in my initial post i did some up- and downgrades. I went back to official 2.3.4 with existing battery problem.
Maybe this was a missunderstanding. I need to know if ther is any "smart" way, without rooting etc., to get a rom out of an existing phone, without the battery drain.
Regards, ... ibmuser2
theres a zip file for os drain prblm thts for ,wen the phone dosnt charge uptill 100..but still every android user faces a batt prblm,,but android phones r more like a pc..so it s power hungry
rocky23 said:
theres a zip file for os drain prblm thts for ,wen the phone dosnt charge uptill 100..but still every android user faces a batt prblm,,but android phones r more like a pc..so it s power hungry
Click to expand...
Click to collapse
Thx for your information.
My phone charges up to 100% (as far as it does not lie to me). ;-)
I do not complain about the power consumption. I complain about the difference between stock 2.3.4 and any ohter stock ROM / update i installed.
Regards, ibmuser2
ibmuser2 said:
Thx for your information.
My phone charges up to 100% (as far as it does not lie to me). ;-)
I do not complain about the power consumption. I complain about the difference between stock 2.3.4 and any ohter stock ROM / update i installed.
Regards, ibmuser2
Click to expand...
Click to collapse
Have you tried any custom roms?
Or contacted the retailer about this?
Maybe it is a hw problem.
It would suggest a battery fault tbh.
Flashing repeatedly can put strain on the battery (from my own experience), also as far as I am aware, the official update via KIES did cause battery related issues; I never experienced, but my friends did, and Samsung UK where troubleshooting by, removing the battery for 10 minutes, letting it drain out when put back in the phone, then performing a full charge when switched off. If not resolved > factory reset - which did help one of my friends surprise, surprise lol.
If you are still in first 6 months I would advise contacting Samsung Germany for a replacement battery to see if any improvement. Otherwise you can buy cheap online.
Hey superthug & T__. Thx for your good comments. I´ll give it a try. One of my friends have a SGS2 without any problem. I´m going to x-change it with him.
Cheers.
Hey Guys. I made some further testing, but it´s getting more ande more worse.
1. I x-changed the battery with another SGS2. My battery is draining and the other SGS2 is good. -> No battery fault.
2. I did many factory resets, installed betterybatterystats, but it shows no wake locks. all values are below 4%
3. I installed cpu spy, and it shows 98% Deep sleep, when not using it <---- as expected!
4. I changed my FW to:
I9100XWLP7_I9100XXLPS_I9100XEULP5
ICS 4.0.3
Base: I9100XXLPS
Kernel: 3.0.15-i9100XWLP7-CL340913
[email protected]#3
Build: IML74K.XWLP7
All was downloaded from this Forum. I9100XWLP7_I9100XXLPS_I9100XEULP5 is the default, which came with KIES. I verified this with another SGS2, running this FW trouble free!
5. When i charging my SGS2 now, it heats up extremly. The CPU is running at 1Ghz while external power is connected (not only during charging)
Any ideas?
Hi,
I am seeing the same issue. I noticed after upgrading to ICS that the phone was working well for a few days and battery life was good, then after I plugged it in to charge overnight (as I always do) I found that the battery had decreased and the phone was hot to touch near where the camera is located on the back the following morning.
I reset the phone to defaults and I was able to charge a couple of times but this didn't fix the problem and it started happening again.
I have tried charging from my laptop, and 2 separate USB chargers with different cables and the same fault has occured.
A reset of the phone seems to temporarily fix the issue and I can charge the phone again but when I plug in again to charge I see the battery decreasing.
It seems as if something is screwing up and causing the CPU to run at 100% when the charger is attached which would explain why the phone is warm/hot to touch.
I'm just testing at the moment to see if I can get the phone to a state where the charger is connected and the battery is decreasing to try to identify the cause. I suspect that it may have something to do with when the phone goes to sleep and the screen turns off so I will try to set the timeout to 10 mintues to see if this helps and the battery starts to charge again.
Suspend Mode bug + linux power management regressions: flight/airplane drains battery
Hi, I experienced a similar issue with GS2 i9100G. I also haven't found a clear and definite answer in the various forums I have been digging into.
To sum it up here's what I found:
Android 2.3.4 worked perfectly fine with GS2, but upgrade to 2.3.6 introduced a suspend mode bug. Basically Suspend mode would cause the system to enter a loop, thus the battery drain while in flight mode.
The best solution would be to downgrade/stay with Android 2.3.4 (when it ain't broke don't fix it).
Possible workarounds if you'd rather not fiddle with your OS version:
Wifi settings > advanced settings > Policy: Wifi always on (so as not to trigger suspend mode with wifi), then (optional) use a Battery Manager App to fine-tune the wifi activation. Wifi always on drains your battery, but less than the system loop if you're not constantly on the move.
Don't use flight mode, shut you phone at night and use a good old clock) (and redirect calls to your landline if you must)
Try and find the apps that require regular sync thru wifi and might be the sole culprit causing the system to enter the loop
Note that Android 2.3.4 is based on Linux kernel 2.6.32 and that Android 2.3.6 is based on kernel 2.6.35 which introduced a major power management regression.
The fix for this regression has not been fixed before current kernel 3.3 (although some developer may have backported the fix into 3.2), so I would advise to stay away from current Android 4.0.3 ICS which is based on kernel 3.0 (later versions will be based on kernel 3.2 though)
I am not sure if this is the root for the suspend mode bug or if both issues are independent, but in the meantime 2.3.4 works perfectly fine.
EDIT: upgrade to 2.3.6 then 4.0.3 really stand as blunders from Samsung on such high-end Smarphones. Regardless of the device, waiting for the upcoming Android version 4.0.5 seems the better choice if you want to enjoy ICS and not regret iOS...
Android 4.0.3, a version with well-documented problems, including the battery problem, rather than 4.0.5, which solves many of those problems?
Probably not. Probably, the slow nature of Android updates is to blame. It took six months for version 4.0.3 to wend its way through the system, meaning it could yet be months more before the updated update, version 4.0.5, reaches users.
Right now, it seems their only option is to go back to 2.3.6, just like they’re asking.
from Samsung users bitten by upgrade bug (May 7th, afr.com)
Click to expand...
Click to collapse
Suspend Mode bug causing flight/airplane mode to drain battery
After trying different things I came to the conclusion that it all comes down to apps who force themselves to run in the background when you install them and request frequent syncs (free apps will do whatever it takes to boost their ad revenue).
To me it's still a bug in the suspend mode (Apps shouldn't be allowed to request a connection while in Airplane mode, doing it triggers a loop of failed attempts) and Samsung overlooked it.
In the meantime the previous solutions I mentioned do work:
n°1 (lazy fast) - Wifi settings > advanced settings > Policy: Wifi always on (so as not to trigger suspend mode with wifi), then (optional) use a Battery Manager App to fine-tune the wifi activation. Wifi always on drains your battery, but less than the system loop if you're not constantly on the move.
n°2 (depends on the number of apps) - Try and find the apps that require regular sync thru wifi and might be the sole culprit causing the system to enter the loop
n°3 (last resort) - Don't use flight mode, try to turn off data instead or shut you phone at night and use a good old clock) (and redirect calls to your landline if you must)
Click to expand...
Click to collapse
A battery calibration shouldn't be of much help.
Eventually I read someone, with Android ICS 4.0.3 installed, who mentioned DTIM and explained that changing the default 5ms to 1ms solved his battery life problem (note that you usually set this parameter to the highest possible latency to save your battery on mobile devices)
this is by far the most interesting battery problem thread i have found in the past 2 weeks. this exactly describes the problem I've been having.
initially nothing was wrong for me either. straight out of the box went ok for months. i'm not sure, but i think it was 2.3.4. shortly after the stock official update (unbranded) update to android 4.0.3 i noticed the battery died in about a day, instead of 2 days.
things i tried thus far:
- flash 2.3.6 back. same problem.
- flash 2.3.4 back, same problem.
- since it sucks either way, i flashed the stock 4.0.3 again.
- disabled a whole ****load of apps i normally use. same problem.
- decided to root and flash dragonICS 4.0.4 with default siyah kernel
- swapped battery with a colleague who does not have this problem. same problem.
- reset battery thingy in extweaks, battery % reporting sucks big time since then, but essentially: same problem
- tried a lot of suggested tweaks in extweaks which are supposedly better. same problem.
- set syncing at a longer interval (even though it worked fine out of the box). same problem.
- disabling all the sensors i could (including rotation for the apps), wifi, data traffic in general. same problem.
- cut the light sensor polling interval in half (from 1sec to 2sec). same problem
- removed the SD-card, because god knows what conflict it could cause. same problem.
- removed sim card, since problems were reported between this phone, android4 and my provider. same problem.
- full battery drain and charge cycle. same problem
problem verification:
- battery monitor widget, which logs an obvious higher battery usage than my colleagues phone.
- badass battery monitor which clearly shows "kernel" and "android system" way up there, where it should never be.
- "system tuner" in the "task manager" section which shows "android system" and "/system/bin/surfaceflinger" using the most cpu time by far
- "cpu spy" shows the cpu most of the time in deep sleep, which looks pretty good to me.
i can see the android system is using a lot of time reading 2 sensors, which seem required by basic functioning of the device. screen rotating and brightness.
i am unable to find out what the kernel is doing with all it's time. but whatever the rom, it's doing something.
ps: not all tests were in this order or seperated as they are described.
better battery stats shows a few processes on top:
kworker/0:3
kworker/0:1
kworker/0:0
kworker/0:2
in this order
It was a hardware fault! Samsung replaced the planar, ... now it´s fine. Thanks to all replys and your help.
while i'm happy there is a solution i am wondering about the following:
how can software introduce a hardware fault?
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.
SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.
The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)
This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.
I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
only sleep of death in almost 10 months of use is when i tried xwlp9.
so no its not common
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
Sent from my GT-P6810 using XDA Premium HD app
From the sound of it, it seems to be a software problem.
I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.
I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.
Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
victorator said:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
Click to expand...
Click to collapse
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Ray_Grey said:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Click to expand...
Click to collapse
Or just flash the newer build. No SOD there.
wanewon said:
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
Click to expand...
Click to collapse
How about this?
I answered your question. Read the edit I made to my post.
wanewon said:
How about this?
Click to expand...
Click to collapse
MistahBungle said:
I answered your question. Read the edit I made to my post.
Click to expand...
Click to collapse
Thank you for the answer.
Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
victorator said:
Or just flash the newer build. No SOD there.
Click to expand...
Click to collapse
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
Never faced such issues ever.
Sleep of death
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
MX 007 said:
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
Click to expand...
Click to collapse
bah bye
SOD
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
?
darkm1st87 said:
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
Click to expand...
Click to collapse
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
tkrokod said:
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
Click to expand...
Click to collapse
Hi,
I'm also trying to solve this problem, since weeks.
My observations:
SOD happens most on higher battery status (e.g. more SOD's at 80% battery then at 20%
The Phone gets hot after SOD and also before the SOD comes.
While loading the Phone SOD's happen more often
The battery status drains rapidly while SOD (cause of the resulting heat)
My SOD's are independent of kernel, rom, firmware or what ever.
I think it's a hardware problem, but I've no warranty and what to solve the problem without changing the mainboard. It couldn't be a really defective of an important part, cause the phone works apart of this SOD-problem.
Maybe we could find out together howto solve these anoying sod's
Hey. Im trying to solve the SOD problem myself cause its been happening every day and its really annyoing since the phone isnt even a month old.
I got the newest cyanogen mod running.
The phones model is GT-i9100
Android is 4,2,1
I still have warranty on it, do you think I should go back to stock, go exchange my phone where I got it and see if the new one has SOD too or should I just try fixing it first.
Also apps I use constantly : go launcher and dragonvale
I have a 8 gb micro SD inside as well, dunno if that could cause this.
Hello!
I've searched for help on some threads and got no answer yet.. so I'm creating a new one, to see if i can finally find someone to help me!
Here is my problem:
Since 2 days ago, after flash a new version of the rom I use (I know this may have been caused by the updated, thats why I downgraded to check, and still got the problem), I noticed a battery drain. My phone loss 10% charge overnight(10h +-), on 100% deep sleep time (according to BetterBatteryStats) with everything off, including Wi-Fi, GPS, Mobile Data, 2G network, no apps running, etc. I searched for what was draining it, and found out that Cell Standby was active 100% of the time also. Did a search on BBS, and found out that 2 things were active, again, all the night: "No or Unknown Signal" and "No data conexion". Then, changed and tried some different modems. thinking that it was the problem (matching RILs also). I was wrong.. after testing 6-7 different modems, in all of them my phone still got the drain. After that, my last alternative was to think it was a carrier fault! Well, it wasn't.. Just bought 3 different carrier Chips to test all of them.. and yet, "No or Unknown Signal" , "No data conextion" and Cell Standby were there, in top of consumption list.
I hope someone can help me.. this drain is freaking me out, because before this issue, I was losing only 1-2% over night with Android 4.2.1!
Some info:
-Model: Int SGS3(gt-i9300);
-ROM: Latest CM10.1(4.2.1) kang by Temasek;
-Kernel: Temasek's Custom Kernel;
-Modem/Ril: XXELKC (matching);
-Carrier: TIM - Brasil (gsm = 1800);
Thanks for reading
lucas.viana said:
Hello!
I've searched for help on some threads and got no answer yet.. so I'm creating a new one, to see if i can finally find someone to help me!
Here is my problem:
Since 2 days ago, after flash a new version of the rom I use (I know this may have been caused by the updated, thats why I downgraded to check, and still got the problem), I noticed a battery drain. My phone loss 10% charge overnight(10h +-), on 100% deep sleep time (according to BetterBatteryStats) with everything off, including Wi-Fi, GPS, Mobile Data, 2G network, no apps running, etc. I searched for what was draining it, and found out that Cell Standby was active 100% of the time also. Did a search on BBS, and found out that 2 things were active, again, all the night: "No or Unknown Signal" and "No data conexion". Then, changed and tried some different modems. thinking that it was the problem (matching RILs also). I was wrong.. after testing 6-7 different modems, in all of them my phone still got the drain. After that, my last alternative was to think it was a carrier fault! Well, it wasn't.. Just bought 3 different carrier Chips to test all of them.. and yet, "No or Unknown Signal" , "No data conextion" and Cell Standby were there, in top of consumption list.
I hope someone can help me.. this drain is freaking me out, because before this issue, I was losing only 1-2% over night with Android 4.2.1!
Some info:
-Model: Int SGS3(gt-i9300);
-ROM: Latest CM10.1(4.2.1) kang by Temasek;
-Kernel: Temasek's Custom Kernel;
-Modem/Ril: XXELKC (matching);
-Carrier: TIM - Brasil (gsm = 1800);
Thanks for reading
Click to expand...
Click to collapse
Problem solved.. Just reporting here, someone may need ^-^
Here's what I did (ofc I don't really know this whole process is necessary, but it worked):
1. Mega Wipe Script (Formats the whole internal sd card; BE CAREFUL);
2. Flash stock 4.0.4 rom;
3. Wipe Data/Factory Reset;
4. Flash CM10.1;
5. Discharged the phone completely (untill it doesn't boot anymore);
6. Charged the phone to 100%;
7. Yet with the AC plugged in, deletted batterystats.bin;
8. Turn the phone off;
9. Unplug the cable;
10. Boot phone :good:
This thing about deleting the batterystats.bin is not to calibrate battery, because it only containts data about processes and their battery consumption.
Was just a way to fix a wrong value the phone was getting from the Cell Standby, idk if the fix is there ^-^
Peace.
Basically two days is not long enough to recalibrate or test a battery .
jje
Hello!
I've searched for help on some threads and got no answer yet.. so I'm creating a new one, to see if i can finally find someone to help me!
Here is my problem:
Since 2 days ago, after flash a new version of the rom I use (I know this may have been caused by the updated, thats why I downgraded to check, and still got the problem), I noticed a battery drain. My phone loss 10% charge overnight(10h +-), on 100% deep sleep time (according to BetterBatteryStats) with everything off, including Wi-Fi, GPS, Mobile Data, 2G network, no apps running, etc. I searched for what was draining it, and found out that Cell Standby was active 100% of the time also. Did a search on BBS, and found out that 2 things were active, again, all the night: "No or Unknown Signal" and "No data conexion". Then, changed and tried some different modems. thinking that it was the problem (matching RILs also). I was wrong.. after testing 6-7 different modems, in all of them my phone still got the drain. After that, my last alternative was to think it was a carrier fault! Well, it wasn't.. Just bought 3 different carrier Chips to test all of them.. and yet, "No or Unknown Signal" , "No data conextion" and Cell Standby were there, in top of consumption list.
I hope someone can help me.. this drain is freaking me out, because before this issue, I was losing only 1-2% over night with Android 4.2.1!
Some info:
-Model: Int SGS3(gt-i9300);
-ROM: Latest CM10.1(4.2.1) kang by Temasek;
-Kernel: Temasek's Custom Kernel (CM10.1 stock kernel + up to date linux stuff + OC/UV hability);
-Modem/Ril: XXELKC (matching);
-Carrier: TIM - Brasil (gsm = 1800);
Thanks for reading
lucas.viana said:
Hello!
I've searched for help on some threads and got no answer yet.. so I'm creating a new one, to see if i can finally find someone to help me!
Here is my problem:
Since 2 days ago, after flash a new version of the rom I use (I know this may have been caused by the updated, thats why I downgraded to check, and still got the problem), I noticed a battery drain. My phone loss 10% charge overnight(10h +-), on 100% deep sleep time (according to BetterBatteryStats) with everything off, including Wi-Fi, GPS, Mobile Data, 2G network, no apps running, etc. I searched for what was draining it, and found out that Cell Standby was active 100% of the time also. Did a search on BBS, and found out that 2 things were active, again, all the night: "No or Unknown Signal" and "No data conexion". Then, changed and tried some different modems. thinking that it was the problem (matching RILs also). I was wrong.. after testing 6-7 different modems, in all of them my phone still got the drain. After that, my last alternative was to think it was a carrier fault! Well, it wasn't.. Just bought 3 different carrier Chips to test all of them.. and yet, "No or Unknown Signal" , "No data conextion" and Cell Standby were there, in top of consumption list.
I hope someone can help me.. this drain is freaking me out, because before this issue, I was losing only 1-2% over night with Android 4.2.1!
Some info:
-Model: Int SGS3(gt-i9300);
-ROM: Latest CM10.1(4.2.1) kang by Temasek;
-Kernel: Temasek's Custom Kernel (CM10.1 stock kernel + up to date linux stuff + OC/UV hability);
-Modem/Ril: XXELKC (matching);
-Carrier: TIM - Brasil (gsm = 1800);
Thanks for reading
Click to expand...
Click to collapse
Problem solved.. Just reporting here, someone may need ^-^
Here's what I did (ofc I don't really know this whole process is necessary, but it worked):
1. Mega Wipe Script (Formats the whole internal sd card; BE CAREFUL);
2. Flash stock 4.0.4 rom;
3. Wipe Data/Factory Reset;
4. Flash CM10.1;
5. Discharged the phone completely (untill it doesn't boot anymore);
6. Charged the phone to 100%;
7. Yet with the AC plugged in, deletted batterystats.bin;
8. Turn the phone off;
9. Unplug the cable;
10. Boot phone
This thing about deleting the batterystats.bin is not to calibrate battery, because it only containts data about processes and their battery consumption.
Was just a way to fix a wrong value the phone was getting from the Cell Standby, idk if the fix is there ^-^
Peace.
Hi Folks,
Recently, I updated my Samsung Galaxy Tab 10.1 from Honeycomb to ICS (Android 4.0.4). As a result, I now find that battery capacity falls at 1.4% per hour even when the display is off and the tab is in airplane mode! The culprit would appear to be the l2_hsic kernel wakelock. Is there anything I can do about this? My tab is not rooted.
Thanks in advance.
AD
Anne Droid said:
Hi Folks,
Recently, I updated my Samsung Galaxy Tab 10.1 from Honeycomb to ICS (Android 4.0.4). As a result, I now find that battery capacity falls at 1.4% per hour even when the display is off and the tab is in airplane mode! The culprit would appear to be the l2_hsic kernel wakelock. Is there anything I can do about this? My tab is not rooted.
Thanks in advance.
AD
Click to expand...
Click to collapse
Never had ICS running on my tab, went from android 2.3 stock to cm10 and now cm10.1, but i heard everywhere on the gtab forum that stock ICS came out with a battery drain issue on tab, so i don't think that there is a fix for it now..
L2_hsic has to do something with the usb connection, most of the time after you full charge, the wakelock becomes active. You should try to restart the tab in order for wakelock to go back to normal again
DefQoN_BE said:
Never had ICS running on my tab, went from android 2.3 stock to cm10 and now cm10.1, but i heard everywhere on the gtab forum that stock ICS came out with a battery drain issue on tab, so i don't think that there is a fix for it now..
L2_hsic has to do something with the usb connection, most of the time after you full charge, the wakelock becomes active. You should try to restart the tab in order for wakelock to go back to normal again
Click to expand...
Click to collapse
Hello,
Many thanks for your reply.
You have confirmed my findings. Clearly, there is a battery drain issue with stock ICS on the tab. I think it may also extend to some Samsung phones.
I will try your suggestion of restarting my tab to see if it has any effect on l2_hsic.
AD
Hi,
I restarted my tablet but, this morning, same again. The only kernel wakelock that had been active overnight was, you guessed it - l2_hsic. Once again, battery fell by 1.4% per hour. I really hope that Samsung do something about this soon.
AD
Samsung? I wouldnt bet on it......
GV
Anne Droid said:
Hi,
I restarted my tablet but, this morning, same again. The only kernel wakelock that had been active overnight was, you guessed it - l2_hsic. Once again, battery fell by 1.4% per hour. I really hope that Samsung do something about this soon.
AD
Click to expand...
Click to collapse
As I said in another thread, my problem is solved. 3 months passed and the tablet works as it should.
If you need any help...
http://forum.xda-developers.com/show...y+drain&page=6
Phibs said:
As I said in another thread, my problem is solved. 3 months passed and the tablet works as it should.
If you need any help...
http://forum.xda-developers.com/show...y+drain&page=6
Click to expand...
Click to collapse
link not working, please repost