Hello !
I updated my X10 to 2.3.3 and I have a big problem with this rom.
When the battery level reduced to 40-50% my phone turn off. If I turn on it will be do it again.
I removed the SIM and the memory card, but it is not helped.
On 2.1/2.2 works perfect.
In xRecovery I wiped the cache, data, battery stats and I installed lots of custom ROM, but none of them helped.
Please help !
(sorry for my english)
Hi I think you should calibrate your battery with this app https://market.android.com/details?id=com.nema.batterycalibration&feature=search_result you must do at least twice, inform us
let the batery to fully discharge and then recharge 100% and calibrate
Thanx, I will try this
Sent from my X10 TripNMiUI-Iris using XDA App
unfortunately does not work
pppn said:
unfortunately does not work
Click to expand...
Click to collapse
This can be a side-effect from wiping battery stats.
Did it start happening after you wiped battery stats or before?
Make a few charge circles (charge it to full once it turns off)
and see if it will keep happening. If yes, consider reflashing or repairing with SEUS.
repair it with SEUS,then see what happens.
It start before I wiped the battery stats.
I repaired with SEUS and Flashtool many times, but not helped.
"Make a few charge circles (charge it to full once it turns off)"
I will try it
Thanx everybody
I did it 5-6 times, but always turn off on 80% ...
Sent from my X10i using XDA App
I've noticed this too.
I'll take my phone out of my pocket and it will be turned off. Then I then it back on and I'll have 30 - 50% battery left... strange.
Sent from my X10i using XDA Premium App
I've been having this same issue in various forms since I switched to Wolfbreak v007 a month and a half or so ago, and it has continued through over a dozen ROM and BB changes, and through 5 or 6 full wipes and completely fresh ROM installs (though I'll admit I didn't try using SEUS to reset things that way). It does seem to have gotten worse with the official 2.3.3 update however, as it happens with me around 80% battery as well (it used to be at less than 60%, usually closer to 45% or 50%).
I should also note that the phone isn't simply dieing, but actually shutting down properly when this happens. There's no advanced warning like there is when you hit 15% battery, but the phone will chirp and vibrate, and then will show the "Shutting down" dialog and power itself down just as if I had told it to do so, though when it does shut off the LED will blink red 3 times rapidly.
I have tried wiping the battery stats directly through xRecovery, as well as through the BatteryCalibration app available on the market. Doesn't seem to matter (for reference, I've attached my current batterystats.bin below).
The issue does seem to be at the OS level though, because as others stated the phone will shut itself off again if rebooted, but if I boot into xRecovery it will happily function there for a long time on battery power (I've never left it there long enough to have it shut itself off, but I have accidentally left it there at that point for well over an hour).
On what I think is a related note, my battery level seems to drain at odd rates. It'll sit at a percentage for a while, and then I check it again moments later and it's dropped by like 2-3%, where it'll again sit for a while before dropping rapidly. f I'm actively using the phone I can watch the battery percentage drop quite readily, yet all my usage statistics seem normal (deep sleep occurs, no extended wakelocks, CPU usage is normal according to SystemPanel).
I may try to re-install everything starting with a SEUS install, but any other ideas would be greatly appreciated.
I reflashed my phone with SEUS (many times) and is isn'thelped :/
And if we replace our battery stats to a well-functioning x10's battery stats ?
Just to note, I just upgraded to Wolf's 2.3.3 006 ROM. I wiped battery stats (as well as performed a phone wipe, cache wipe, and Dalvik wipe) in xRecovery before the install. Installed and then rebooted fresh without re-installing anything (ie: a clean ROM).
Battery was reporting around 95% when I started. I configured the base system prefs, lauched a few default apps (Talk, Gmail) and configured those too. Then my phone shut itself down just a few minutes ago while I was using it. I couldn't tell you the exact battery percentage as there's no numerical display in the stock theme, but it looked to be around 80%.
So it doesn't seem to have anything to do with any of the third-party apps I'm using.
And PPPN, I'd like to see what a well functioning batterystats for an X10 is. I've taken a look at my battery stats, and I can't figure out how it actually stores any useful data. I don't see any listings for direct battery charge, which is how I'd assume it would track.
Very interesting issue, I've been running various tests to rule out things like heat running stability test and the like. So far I suspect it's either a issue with some of our batteries, something related to power, or a little of both, maybe even SIM/SD access, suffice it to say I've been prodding at the possible hardware factors, as personal as they may be to my particular situation. I have a New battery on the way so if that changes anything at all I'll let you guys know.
Is log recording working for you guys?
I've tried three different logging programs to try to record a log of when the shutdown occurs to help diagnose the problem, and with all three logging apps (aLogcat, LogViewer Lite, and Log Collector) I get the same output and nothing more:
Code:
08-04 15:07:04.111 I/checkabortedflash( 1061): [125] Latest flash seems OK.
08-04 15:07:07.631 I/DEBUG ( 1078): debuggerd: Jul 13 2011 19:25:06
08-04 15:07:07.741 I/Vold ( 1076): Vold 2.1 (the revenge) firing up
08-04 15:07:07.741 D/DHCP ( 1088): failed to set ip addr for eth0 to 0.0.0.0: No such device
08-04 15:07:07.811 V/DrmIOService( 1082): instantiate
08-04 15:07:07.811 V/DrmIOService( 1082): created
08-04 15:07:07.821 D/Vold ( 1076): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
08-04 15:07:07.861 E/NetlinkEvent( 1076): NetlinkEvent::FindParam(): Parameter 'NPARTS' not found
08-04 15:07:07.861 W/DirectVolume( 1076): Kernel block uevent missing 'NPARTS'
08-04 15:07:07.861 D/Vold ( 1076): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
08-04 15:07:07.861 E/NetlinkEvent( 1076): NetlinkEvent::FindParam(): Parameter 'PARTN' not found
08-04 15:07:07.861 W/DirectVolume( 1076): Kernel block uevent missing 'PARTN'
08-04 15:07:07.861 D/Vold ( 1076): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
08-04 15:07:08.051 I/iddd ( 1101): Starting up...
08-04 15:07:08.061 I/Netd ( 1077): Netd 1.0 starting
The last line (not recorded in the log I saved) reads:
Code:
08-04 15:07:08.051 I/iddd Ready to serve the world.
This is the first time since a few ROMs ago that I've tried to run any logging software.
Actually, that log file resembles something I saw during my testing, specifically the snippet pertaining to "NPARTS" and all that.
OK, I got logs working... kind of.
In aLogcat (and only aLogcat) I set the buffer setting to "Events". This reports all the events that are going on. However since the app can only automatically save every 15 minutes (at best), I can't seem to get it to save the log file as the system shuts down. Launching the app after I boot back up doesn't seem to pull up any log data from before the shutdown from what I can tell (with my total lack of Android-coding experience). So no luck in getting a log of what's going on for me.
I can attest to the fact that on 4 separate occasions I have had my phone shut itself down at 88% battery as I was attempting to get this logging thing going.
At this rate, I may have to revert back to stock 2.1 just to have a usable X10.
Principle on UK Generic works fine, only bad on ARO.
Can somebody confirm this ?
Hi there!
You should try battery stats wiping when phone is on 100%. I googled it, and it says that you should first charge your battery to 100%, not just until green light, then drain it until phone turns itself off, then recharge to 100% again. You should give it a try. As I read, battery stats can go confused when you flash with battery level under 100% many times.
my Batttery went von 80% to 40% in like one minute. I put in on the charger and it still went down. After 5 min ist was soo low it restartet itself and when it finished starting the battery was 91% again. now it goes slowly down but it is still random because the Batterie wennt from 80% to 86% without charging. I updatet wb rom v007 today. Before i got wb v005 and hat no problems.
Related
On several occasions, after applying bstats.zip when at 100%, my phone shows only 60% battery afterr applying the zip.
Is this normal?
Also, as you might guess, having some general battery problems:
Rapid loss of battery reserve
Phone running "hot" when no visible programs are running
Difficulty getting phone back to 100%, even after several hours of charging.
Are there any suggestions on utilities to show
1) whether battery is holding a charge,
2) what programs are using up battery?
Badger51 said:
On several occasions, after applying bstats.zip when at 100%, my phone shows only 60% battery afterr applying the zip.
Is this normal?
Also, as you might guess, having some general battery problems:
Rapid loss of battery reserve
Phone running "hot" when no visible programs are running
Difficulty getting phone back to 100%, even after several hours of charging.
Are there any suggestions on utilities to show
1) whether battery is holding a charge,
2) what programs are using up battery?
Click to expand...
Click to collapse
This is definitely not normal. There are several things to try:
1)in terminal emulator, type"su" then hit return to get superuser access, then run the command "dumpsys power". near the bottom is a command "mLocks.size=0"
This will list any wake locks, which drain battery by preventing the phone from going into deep sleep. (In the example, 0 means no wake locks)
2)try a different kernel, maybe an undervolted one. I recommend imnuts' 50uv pbj kernel found here:
https://sites.google.com/a/imnuts.net/android/kernels
(try the 4th one down in the list)
thanks
will give that a try...
wake locks
The following is captured from the emulator screen, there is more above it, but this appeared to be the section on wake locks:
mLocks.size=3:
PARTIAL_WAKE_LOCK 'MAIL_SERVICE' activated (minState=0, uid=10212, pid=2731)
PARTIAL_WAKE_LOCK 'CoreReceiver getWakeLock' activated (minState=0, uid=10092, pid=2731)
PARTIAL_WAKE_LOCK 'NetworkLocation Check Location' activated (minState=0, uid=1000, pid=2731)
Not sure if it's good news or bad news..
Working to install the other kernel, as well.
It looks like you might be using an email client other than the stock one that is keeping your phone awake. If so, try uninstalling or disabling it for 24 hours and use your phone.
Being fed up with the random wakelocks that Dialer produced on my Gingerbread P500, I spent a while searching for the cause. It turned out to be DataTracker-FD (found out using the amazing BetterBatteryStats app - http://www.cri.ch/sven/doku.php/computing/android/betterbatterystats ), which deals with Fast Dormancy (http://www.computerworld.com/s/article/9191759/Fast_dormancy_to_improve_smartphone_networking_and_battery_performance_ ).
Now, in theory, Fast Dormancy should be a great feature! But, if your network does not support it, DataTracker-FD will still drain a lot of battery through the wakelock. The SGSII secret code for deactivating it doesn't work on the P500, and neither does the nwk_info.db method. Luckily, you can deactivate (or change its timeout) through the LG hidden menu...
1. Dial 3845#*500#.
2. Go to Modem Setting > PDP Setting > [0] Set Fast Dormancy
3. Select your desired timeout (or "Disabled"). You should now be done! (will look at Battery Usage in a little bit, to see if a reboot/Dialer FC is also needed)
Optional step 4. If you still see no difference, set your desired timeout (or "Disabled") a few more times.
Hope it helps.
/* Edit: It doesn't seem to help, we might be back to square one. Does anyone have any idea on how to completely disable Fast Dormancy? We might need a dev to look at the source code of Dialer and make some modifications... Right now, if your phone stays awake after using Data, the only current workaround is FCing Dialer from Applications. */
EDIT 2: A SECOND TEST, USING THE ABOVE METHOD TO DISABLE FAST DORMANCY, YIELDS POSITIVE RESULTS! THE WAKELOCK IS NOT THERE ANYMORE, EVEN AFTER SEVERAL RECONNECTIONS TO HSDPA!
It needs way more testing though, I will reconnect to data and leave the phone idle (screen off), then see what happens, and I will reboot the phone to see if the setting persists.
EDIT 3: Yes, the setting persists, and the wakelock is still not running! The final test will be done after it has completely charged, because there still is a small possibility that the wakelock is so far not active just because the phone was charging.
Edit 4: Straight after unplugging the phone, DataTracker-FD started running, without being connected to HSDPA (I was in a phonecall). In 17 minutes (of mostly talking on the phone) it drained 1% of the battery - so, it should last for about 29 hours with the same usage. Now I have started HSDPA and left the phone idle for 10 minutes, to see how much it drains and how much it drains after I turn data off. It just might be that, while the phone is still awake, it doesn't drain a large amount of battery. If it actually still drains a lot, this tweak definitely only /seems/ to work while charging (maybe BetterBatteryStats was reporting false data or FD just doesnt' work when charging).
Edit 5: Here's a pleasant surprise. Right after connecting to HSDPA and putting the phone to sleep, the Awake bar in Battery Usage faded out. In 5 minutes of idling with data activated, the phone drained another 1% battery - not sure how well that is, since it amounts to 8 hours of data on a full charge, but it's better than 12 hours of idling with no data on a full charge. Currently repeating the test. Just got an email on Yahoo pushed, I'll get to see the influence on awake time of that as well.
Edit 6: After 10 minutes of idling with data ON, a bit over 1% of the battery is gone. This is a fantastic value, and the Awake bar is only dotted in this period of time. DataTracker-FD seems to be running a bit in the background during the data connection, but stopped once I turned it off. It might just be me, though, because aLogCat still can't find any entries for Fast Dormancy. Now leaving the phone idle with no data for a while to look at the evolution of Awake time.
Edit 7: After about 45 minutes of complete idling, the battery went down 2%. This would mean the battery would last for about a day and a half, which is meh, considering I OC'd the phone to 730 and don't really use a task manager.
The conclusion: YES, disabling Fast Dormancy does work using the above method, and it does help battery life!
Edit 8: After another unrelated reboot, DataTracker-FD is once again awake after using data, but this time it draws significantly less battery. The Battery Usage graph shows no difference between sleep times and awake-because-of-FD times.
Edit 9: During the night, the phone drained 30% battery, once again because of some random action of DataTracker-FD. This is still not a definite fix.
"Connection problem or invalid MMI code" when I dial that number..
I remember that long ago I dialed the number and everything was fine.
Well you shouldn't literally call it, just type it in Dialer and it should open the hidden menu.
metalboy94 said:
Well you shouldn't literally call it, just type it in Dialer and it should open the hidden menu.
Click to expand...
Click to collapse
When I just type it in dialer, nothing happens.
I see. It might not work on CM.
Updated the OP a couple of times, you might want to read it.
Considering I am still on Froyo v2.2.2, could this be of interest for me too? There's no abnormal battery drain on my phone, but if I can improve the battery life by tweaking this setting, I'd gladly do it.
masteryx said:
Considering I am still on Froyo v2.2.2, could this be of interest for me too? There's no abnormal battery drain on my phone, but if I can improve the battery life by tweaking this setting, I'd gladly do it.
Click to expand...
Click to collapse
I didn't have such problems on Froyo either. It MIGHT help, but as you can see from the numerous edits to the OP, it's not a clear win yet.
So it need to be disabled twice to stop working?
I've been looking for this service since using that Battery App but theres not much information of that in the web.
I'm not sure just how many times, but it took about 3-4 times for me until I was completely sure the wakelock stopped running and the phone went into deep sleep each time I locked it.
Yeah I think I got it doing it twice, FC phone and rebooting, btw maybe you can check system/etc/flex/flex.db and flex.xml there are fast dormancy settings there
@metalboy94 I mailed LG regarding Fast Dormancy and the reply i got was that P500 does not support fast dormancy. My phone does not switch from H to 3G. I tried enabling it many times using secret menu but it does not work.
I asked him if GB ROM/Baseband supports fast dormancy, he replied saying GB hasn't been released for India
Roqu3 said:
Yeah I think I got it doing it twice, FC phone and rebooting, btw maybe you can check system/etc/flex/flex.db and flex.xml there are fast dormancy settings there
Click to expand...
Click to collapse
There are? Thanks a bunch, gonna try those methods as well!
@atulalvenkar: Well, it still draws power from the battery, so at least they could have done something to the Dialer if it's not supported at all.
Edited the OP once again.
Are you guys checking on GB or Froyo ROM ? I can't see flex.db or flex.xml in froyo ? Stock or CM7
atulalvenkar said:
Are you guys checking on GB or Froyo ROM ? I can't see flex.db or flex.xml in froyo ? Stock or CM7
Click to expand...
Click to collapse
Stock GB. I found it, but you have to fill in the info for your operator if it's not on that list. Guess which is my situation.
metalboy94 said:
Stock GB. I found it, but you have to fill in the info for your operator if it's not on that list. Guess which is my situation.
Click to expand...
Click to collapse
Yeah my operator isn´t there also (I´m on a custom V20g ROM and I´m not from Romania) but i got the flex files from the Froyo stock so im going to try using that information to replace one of the V20g operators.
Also tried putting the Froyo ones on GB but get a lot of FC
Updated the OP again...
I tried to change the FD settings in the hidden menu, but the setting does not "stick", so I don't know if it's actually OFF or not.
However, I found that DataTracker-FD only keeps the phone awake when Wifi is on. If I'm always on 3G, FD seems to work and keep the phone asleep. Overnight with wifi off and 3G on, it only drained 2% battery.
I'm on official GB2.3.3 with PaoloM's kernel v5.
Strange.
hey maybe let´s try this:
Code:
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,
have to put that on the build.prop then restart, the values must be changed to your carriers code, you can get that code from adb typing
Code:
adb shell
getprop gsm.operator.numeric
Then the system should show the number
tsuda said:
I tried to change the FD settings in the hidden menu, but the setting does not "stick", so I don't know if it's actually OFF or not.
However, I found that DataTracker-FD only keeps the phone awake when Wifi is on. If I'm always on 3G, FD seems to work and keep the phone asleep. Overnight with wifi off and 3G on, it only drained 2% battery.
I'm on official GB2.3.3 with PaoloM's kernel v5.
Strange.
Click to expand...
Click to collapse
But did you see how many MBs the phone used? Cause if it's too much, people will definitely prefer just turning the phone off.
@Roqu3: I think I tried that before and it didn't seem to make a difference.
Worth a shot tho.
I'll try both of your methods if I still have the issue when I get my phone back from the service center.
Sent from a crappy rebranded Huawei using my hands
Something strange happened to my phone. One night I installed an app that can turn the phone into sleep mode instead of pressing the button at the uppermost right of it. I still have around 70+% battery by that time. The next morning, I was surprised that my battery is already out. I charge it but was stuck at the cyanogen logo. I removed the battery and tried to open it, this time the animation boot happened twice before finishing. I removed the app but noticed that my battery begun draining much faster than before. Just letting it on idle state will reduce it to 40% in 9 hours. The bootup problem is also present every time I boot the phone - it will get stuck at first at the logo,remove the battery, turn it on again where the animation will happen twice before the phone become usable.
Checking the phone usage, mobile standby and phone idle have the largest usage. I read some threads mentioning something about wakelock or something that prevent the phone from going to sleep. Checking the Spare parts battery history, only two things are present - Running (100%) and Screeon on (5.1%).
Any help or tips to know the real problem? Thanks
sinscythex said:
Something strange happened to my phone. One night I installed an app that can turn the phone into sleep mode instead of pressing the button at the uppermost right of it. I still have around 70+% battery by that time. The next morning, I was surprised that my battery is already out. I charge it but was stuck at the cyanogen logo. I removed the battery and tried to open it, this time the animation boot happened twice before finishing. I removed the app but noticed that my battery begun draining much faster than before. Just letting it on idle state will reduce it to 40% in 9 hours. The bootup problem is also present every time I boot the phone - it will get stuck at first at the logo,remove the battery, turn it on again where the animation will happen twice before the phone become usable.
Checking the phone usage, mobile standby and phone idle have the largest usage. I read some threads mentioning something about wakelock or something that prevent the phone from going to sleep. Checking the Spare parts battery history, only two things are present - Running (100%) and Screeon on (5.1%).
Any help or tips to know the real problem? Thanks
Click to expand...
Click to collapse
this will happen when install every crappy tweak **** - i'm not understand why users have to install extra apps for buttons
to help you something:
wipe your system, not the data - only if it doesnt work after wiping the caches.
than try to boot ... if its doesnt nrmal booting, reinstall the rom and do a full wipe. sometimes apps installing libraries in system.
^
I was thinking of reducing the usage of the hard button so I used it. Will resintallation of the ROM afefct my partition? I have a nandbackup before this problem happened, but I still do not have the partition by that time.
And how do you do it by the way? Just flash again the ROM? Thanks
Edit: Wiping the cache seemed to help. It doesn't stuck at the logo, but the animation still happens twice instead of once. Gonna observe the battery usage. Thanks.
100% running, that means your phone is not in sleep, but only with LCD off. Grab betterbatterystats([email protected]) and check your wakelocks.
Sent from my LG-P500 using XDA App
Based on the betterbatterystats, the gpslocationprovider is the culprit. But my gps apps are off and are not running any services. Any idea how can I stop it?
sinscythex said:
Based on the betterbatterystats, the gpslocationprovider is the culprit. But my gps apps are off and are not running any services. Any idea how can I stop it?
Click to expand...
Click to collapse
Off GPS ,on only when needed
Sent from my LG-P500 using XDA App
I copid a gpa.conf somehere in this forum. I replaced it with the originial and I'm currently observing whether it will return to normal. My gps apps are off, and both wireless and gps sattelites are disabled on my location & security tabs.
I'm planning on doing a restore to at least remove the boot up problem. But my last nandbackup was still before I partitioned my sd card and flashed dark tremor, and configre a2sdgui. If I do the nandrestore, do I have to disable or remove dark tremor and a2sdgui, or remove the partition of my card? Thanks
sinscythex said:
I copid a gpa.conf somehere in this forum. I replaced it with the originial and I'm currently observing whether it will return to normal. My gps apps are off, and both wireless and gps sattelites are disabled on my location & security tabs.
I'm planning on doing a restore to at least remove the boot up problem. But my last nandbackup was still before I partitioned my sd card and flashed dark tremor, and configre a2sdgui. If I do the nandrestore, do I have to disable or remove dark tremor and a2sdgui, or remove the partition of my card? Thanks
Click to expand...
Click to collapse
I has the same gps wakelock even disabling GPS- reboot and the thing is gone
I changed it, but my phone still doesn't sleep. Although this time, the gpslocationprovider is no longer shown with the betterbatterystats. It just states that my phone is awake for around 47 minutes but my screen is just on for around 4 minutes. I've already rebooted several times and wipe the cache but its still like this. Still trying to find other ways.
I've been using the app BetterBatteryStats as recommended by XDA to determine why my RAZR is awake much of the time, even when the screen is off and data is turned off. It turns out the problem is the internal process IMS_Data_Retry. This process apparently keeps attempting to establish a data connection over cellular data, at least 4G LTE. It aquires a wake lock while doing its work. This one process can keep the phone awake 95% of the time. The only way I have found to semi-stop it is to turn on 4G LTE. Even then, while it stops consuming CPU time (supposedly), the count of retry attempts keeps going up. (Putting the phone in Airplane mode also stops it, but then calls are stopped as well.)
There is a setting in /system/build.prop that I thought controlled this process:
ro.cdma.data_retry_config=default_randomization=2000,max_retries=infinite, 0, 0, 120000, 180000, 540000, 960000
I looked at some code references I found ( http://hi-android.info/src/com/android/internal/telephony/cdma/CdmaDataConnectionTracker.java.html ) and learned that the above values are in milliseconds. It seems that the default_randomization value is added to the other values in the list to create a schedule of retry attempts, but I wasn't able to figure out all the parameters to the method, if I even have the right one. I tried changing "infinite" to a small number under 10, but it had no effect - the process just keeps retrying forever.
Is there a dev out there who knows more about this? I want to limit this process because I seldom use cellular data right now and am usually on WiFi. It hinders any attempt to extend battery life. Is it a bug? Is it fixed in a later release (I'm on .748 stock) ? Do any of the custom ROMs have this problem? Can the build.prop setting I found be given values that limit the amount of time this process holds wake locks?
Thanks.
Did you ever get any resolution on this? For me, I think the problem started with the ICS update this summer. I constantly have gsm_data_tracker, RILJ, and IMS_Data_Retry using up the battery (in that order from highest to lowest). I tried wiping cache which helped the 1st time it cropped up and then it came back. I also tried a tip I saw somewhere for turning on airplane mode, rebooting, and turning off airplane mode (though mine as soon as it reboots, it already turns off airplane mode which it shouldn't). That worked for several weeks, but I had to do it EVERY DAY when I got to work. I think it's something with the 3g repeaters in the building. I did have it so it was wifi only (mobile radio off) on my work profile in profile scheduler, but then I needed cell for some mms stuff, so I ended up enabling it again. Basically when I come in the building and forget about my phone for an hour or 2, I go to get it out of my backpack and it will be hot from processing and 20% or more of the battery gone when I've done nothing in 2 hours of being at work. I saw somewhere that someone though either gsm_data_tracker or RILJ was related to something with the alarm, which I do use my phone as my alarm, but I use a 3rd party app. With the time change, there were a few days I woke up before it ever went off, so I turned it off before it did alarm. There were no differences with the partial wakelocks or battery drain in those cases. Unfortunately, I don't have another alarm readily available to get up for work right now and on the weekends when I don't need an alarm, I can't replicate the cell repeater at work issues, since I wouldn't be around the cell repeaters. As fart as in the building at work, until I reboot with airplane mode and all of that, the cell signal will bounce between like 0 bars/3g and lots of bars (no indication of network) and some bars with 1x network. It's all over the place. The airplane mode/reboot used to stabilize that, but it doesn't seem to be doing the trick anymore the last few days that I've tried that. I have to leave my phone on the charger as much as possible at work so that I don't leave for the day with a dead phone.
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Nafiganado said:
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Click to expand...
Click to collapse
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
es0tericcha0s said:
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
Click to expand...
Click to collapse
Hi,
yes, i've used Wakelock detector app as well as its advanced colleague - BetterBatteryStats. So that's how I've found out about "s5p-ehci" wakelock. And I can see there is no other reason of phone insomnia, besides s5p-ehci.
All other apps and processes consume CPU moderately. When s5p-ehci activity is moderate - phone sleeps well. When it gets berserk and is active during several hours - phone does not sleep at all during whole this time (deep sleep is 0%), instead works on minimal frequency (300MHz), however, it's about 40% of battery draining per night.
If it's a hardware issue - I wonder who can help me with that investigation. Services do not deal with such cases, since there is no permanent problem signs. In my case the process can behave properly during a day. Then, all of a sudden, it's getting active and some its activity lasts hours! Then it's getting back to normal again. I've looked at kernel log and system log. There is a lot of various events happening there: something is going on, then device sent to sleep, then again something is going on, then wakeup, in various cases wakeup reasons are different, I was unable to find some relevant info... I would send this log to anyone who could help me to find source of the problem.
I've rolled back to Android 4.1 firmware and installed custom kernel.
Here situation is better, but what I have discovered:
phone seems not to detect when it's being plugged off from charger - no matter, USB cable from computer or wall socket wire. s5p-ehci does not go away and sucks off my battery. What only helps is manually resetting EHCI power: setting 0 in ehci_power file. As a result, something is reset, ehci power is on again, but this sucker goes away and after that everything is fine until next charge. But I need to find a root of the problem!
Going on investigation - too view info in Internet...