I got the orb for my Nexus and ever since I used it my phone doesn't go into deep sleep. I opened BetterBatteryStat and I have something called WirelessChargerDetector at the top of my list of kernel wakelocks. Also when I look at CPU state it goes to 384MHz instead of deep sleep when I am not using my phone. Obviously, this has hurt my battery life pretty hard. If I reset my phone after taking it off the charger, it seems to not have the kernel wakelock.
Can anybody with the charging orb see if they have the same issue?
easyxtarget said:
Can anybody with the charging orb see if they have the same issue?
Click to expand...
Click to collapse
This happened to me once, I don't think it has anything to do with the orb, any wireless charger can trigger it. It seems to be a service added in 4.2.2 to help the phone figure out when it's on or off the charger.
I rebooted my phone after seeing this and it hasn't happened since over several charge cycles. I wonder if moving your phone on and off the charger frequently can trigger it, because that's the only thing I can think of that I've avoided doing since then.
easyxtarget said:
Can anybody with the charging orb see if they have the same issue?
Click to expand...
Click to collapse
This has happened to me multiple times using the orb charger. Kernel wakelock stay active and the phone never goes to deep sleep. I've been rebooting to fix the issue but gets rather annoying to do every few days.
easyxtarget said:
Can anybody with the charging orb see if they have the same issue?
Click to expand...
Click to collapse
Looks like I'm having the same issue after 4.2.2 update
The wakelock is caused by PowerManagerService.WirelessChargerDetector. The only way to fix the issue is by doing a reboot of the phone EVERY time you use the wireless charger. This obviously defeats the convenience of the charger.
The issue appears to have popped up with the 4.2.2 update. I found this post in /r/nexus4 complaining about the bug as well: http://en.reddit.com/r/nexus4/comments/1988qm/powermanagerservicewirelesschargerdetector/ and there are some people reporting it on the Accessories thread: http://forum.xda-developers.com/showthread.php?p=38075837&highlight=wakelock#post38075837
Hopefully someone can figure out the issue or Google releases an update soon (not likely). Until then I'm back to my wired charger
EDIT: Found a Google bug tracker for this. Please star it: https://code.google.com/p/android/issues/detail?id=52034
Racer Of All said:
The wakelock is caused by PowerManagerService.WirelessChargerDetector. The only way to fix the issue is by doing a reboot of the phone EVERY time you use the wireless charger. This obviously defeats the convenience of the charger.
The issue appears to have popped up with the 4.2.2 update. I found this post in /r/nexus4 complaining about the bug as well: http://en.reddit.com/r/nexus4/comments/1988qm/powermanagerservicewirelesschargerdetector/ and there are some people reporting it on the Accessories thread: http://forum.xda-developers.com/showthread.php?p=38075837&highlight=wakelock#post38075837
Hopefully someone can figure out the issue or Google releases an update soon (not likely). Until then I'm back to my wired charger
EDIT: Found a Google bug tracker for this. Please star it: https://code.google.com/p/android/issues/detail?id=52034
Click to expand...
Click to collapse
I'll chime in that I too have this issue. It's pretty annoying.
AW: Wireless Charger Detector -- Orb
Is there a homebrew fix for this?
Just wanted to post here (instead of starting a new thread) about the latest update. 4.3 does NOT fix this issue. For the past two days I have charged my phone on the wireless charger and the wakelock eventually comes up just like in 4.2.x
Hopefully with the new Nexus 7 having wireless charger there will be more people charging wirelessly and more demand for Google to fix this annoying issue.
I can second that 4.3 does not fix the problem.
I know it would be inconvenient, but could tasker automatically reboot the phone once removed from the charger? I could live with this every morning when I grab it off the charger.
If I manually reboot when I pull it off the charger right away, I can get well over two days one the Nexus 4 now with 4.3
I would love a better home brew fix, knowing it will be a long time before a new update comes from google now.
TaintedByte said:
Just wanted to post here (instead of starting a new thread) about the latest update. 4.3 does NOT fix this issue. For the past two days I have charged my phone on the wireless charger and the wakelock eventually comes up just like in 4.2.x
Hopefully with the new Nexus 7 having wireless charger there will be more people charging wirelessly and more demand for Google to fix this annoying issue.
Click to expand...
Click to collapse
Agreed, noticed the issue again today after my 4.3 update a couple of days ago, drained down to 50% after 7 hours rather than the more usual 70%. I use two different wireless chargers (the official orb and a different LG charger) and only notice the wakelock about once every two weeks. Bit annoying to keep an eye out for it and I try not to move my phone off and on the charger (which negates some of the utility of a wireless charger as others have noted above). A reboot usually fixes it. Bugtracker starred.
RTNetwork said:
I can second that 4.3 does not fix the problem.
could tasker automatically reboot the phone once removed from the charger? I could live with this every morning when I grab it off the charger.
Click to expand...
Click to collapse
It should be able to but you would have to set a second activation point. Remember that when the battery gets full chargers will "stop" charging the phone. Qi chargers do this too so as soon as the battery tops off and it stops charging Tasker will consider this as an actuation point for the reboot and do so. Essentially you would end up with endless reboots until you take it out of the charger in the morning.
feelfreetoblameme said:
Agreed, noticed the issue again today after my 4.3 update a couple of days ago, drained down to 50% after 7 hours rather than the more usual 70%. I use two different wireless chargers (the official orb and a different LG charger) and only notice the wakelock about once every two weeks. Bit annoying to keep an eye out for it and I try not to move my phone off and on the charger (which negates some of the utility of a wireless charger as others have noted above). A reboot usually fixes it. Bugtracker starred.
Click to expand...
Click to collapse
Yeah it's not very fun. What is interesting is that the New Nexus 7 doesn't have this issue. At least not so far, I've been testing it since I got it and there have been no wakelocks. This either means that the issue is only with the Nexus 4 or the newer build fixes this issue... So I wonder if using build JSS15J on the N4 would fix this problem...
EDIT: Nope, JSS15J still has the problem I wonder why the New Nexus 7 does not though...
TaintedByte said:
It should be able to but you would have to set a second activation point. Remember that when the battery gets full chargers will "stop" charging the phone. Qi chargers do this too so as soon as the battery tops off and it stops charging Tasker will consider this as an actuation point for the reboot and do so. Essentially you would end up with endless reboots until you take it out of the charger in the morning.
Yeah it's not very fun. What is interesting is that the New Nexus 7 doesn't have this issue. At least not so far, I've been testing it since I got it and there have been no wakelocks. This either means that the issue is only with the Nexus 4 or the newer build fixes this issue... So I wonder if using build JSS15J on the N4 would fix this problem...
EDIT: Nope, JSS15J still has the problem I wonder why the New Nexus 7 does not though...
Click to expand...
Click to collapse
Could a software solution be the answer? Maybe someone could write an app (or even a tasker profile) to somehow kill the wirelesschargerdetector service with a button or when it stops charging?
PickleHead said:
Could a software solution be the answer? Maybe someone could write an app (or even a tasker profile) to somehow kill the wirelesschargerdetector service with a button or when it stops charging?
Click to expand...
Click to collapse
Maybe but then that same software will also use up some battery as well to monitor the wakelock.
The issue hasn't been acknowledged on the AOSP bug report (star it here if you haven't yet). So I started a thread on the Google Products Forums, reply to it and lets see if Google will at least say something there:
https://productforums.google.com/forum/#!category-topic/mobile/android-devices/other-google-products/c4HRzEUNmFk
Also seeing this problem. Didn't have it in Android 4.2.2, but DO have it in 4.3
Happens to me on Nexus 4 and Nexus 7 (2013), both on 4.3.
Anyone know the command to kill the PowerManagerService.WirelessChargerDetector service via Terminal Emulator? This would save us from rebooting.
aa_chow said:
Happens to me on Nexus 4 and Nexus 7 (2013), both on 4.3.
Anyone know the command to kill the PowerManagerService.WirelessChargerDetector service via Terminal Emulator? This would save us from rebooting.
Click to expand...
Click to collapse
Did you try to plugin USB charger for a second ? For me, it removes the wakelock and no need to reboot anymore.
Update: I was wrong, wakelock reappear soon again....
I've written a small app to try to fix this problem.
It needs root access.
I haven't tested it much yet but I think it should work.
All it does is kill the qualcomm sensors daemon when you lift the phone off the charger.
This lets the wireless charger detection service release it's wakelock because the gravity sensor starts working again when the daemon restarts.
Open the app once and click the button, it will ask for root permission. After this, you never need to open the app again.
Let me know if this works.
you could set Tasker to reboot when unplugged from the charger...right?....because with wireless charging it still acts as if plugged in when charging...
Thanks for the app. Will try it out.
I have been starting to wonder if something else is going on. One I have started using the wireless charger and even with a reboot noticed a ton of wake locks and a noticeable difference in battery life.
Anyone else seeing this?
Related
I recently purchased my tab and am loving it so far however 1 problem seems to be happening regularly whenever i go to charge it says "charging paused. Battery temperature too high or low"
Now im not really sure how to check the temp(this is my 1st ever android device) but the back of it does not seem hot nor cold , so i was wondering whether or not it is my device or my charger or something.
If anyone else has had this issue or knows whats causing it it'd be great if you could share
Forgot to mention its still stock rom with nothing fancy added
Atrophi said:
I recently purchased my tab and am loving it so far however 1 problem seems to be happening regularly whenever i go to charge it says "charging paused. Battery temperature too high or low"
Now im not really sure how to check the temp(this is my 1st ever android device) but the back of it does not seem hot nor cold , so i was wondering whether or not it is my device or my charger or something.
If anyone else has had this issue or knows whats causing it it'd be great if you could share
Forgot to mention its still stock rom with nothing fancy added
Click to expand...
Click to collapse
Are you using a wall Charger or a USB charger? I have found that some 3rd party usb wall chargers charge with a different voltage and the tab does not like it, and will either not charge at all or will complain about battery temp
Download an app called elixir and it will tell you temperature stats of your battery. I never experienced such an issue. Discharge the battery completely and recharge it. If you still face such issues and indeed temperatures are up consider returning and exchanging the device.
I downloaded the app it says its -5 celcius. And im using the standard wallcharger that came with the device.
Atrophi said:
I downloaded the app it says its -5 celcius. And im using the standard wallcharger that came with the device.
Click to expand...
Click to collapse
-5 degrees C? you aren't standing outside in alaska are you? normal running temp should be about 29 degrees C. I would have to say that you have a bad device.
Thats weird. Reboot the phone and recheck temp again. If its still stuck something might not be quite right with the temperature sensors.
DarkPal said:
Thats weird. Reboot the phone and recheck temp again. If its still stuck something might not be quite right with the temperature sensors.
Click to expand...
Click to collapse
I tried rebooting but its completely dead now, and still not charging when plugged in.
If it is the sensors i need to send it in then? or there might be another way to fix it? (i really dont trust the tmobile guys i'll probably never get my tab back once i send it in"
I'm having trouble charging my device.
For some reason, after updating to the new 3.2.1 my tablet win not charge either from the adapter, usb pc connection.
Tried rebooting to no avail.
Globespy said:
I'm having trouble charging my device.
For some reason, after updating to the new 3.2.1 my tablet win not charge either from the adapter, usb pc connection.
Tried rebooting to no avail.
Click to expand...
Click to collapse
I don't think this has anything to do with the update. Mine updated and charges ok.
I did however have a problem charging once (before the update) and I searched the web for solutions. I think you will find it's a problem with the mains charger. It overheats and the thermal cut-out fails to reset. As mad as it sounds the solution is to pop the charger in a plastic bag and pop it in the freezer for 30 minutes. It worked for me and countless others and is worth a try.
Good luck though.
had same issue. seems my charger was not well seated with the clip on plug.
Non issue
apprentice said:
I don't think this has anything to do with the update. Mine updated and charges ok.
I did however have a problem charging once (before the update) and I searched the web for solutions. I think you will find it's a problem with the mains charger. It overheats and the thermal cut-out fails to reset. As mad as it sounds the solution is to pop the charger in a plastic bag and pop it in the freezer for 30 minutes. It worked for me and countless others and is worth a try.
Good luck though.
Click to expand...
Click to collapse
gotta try this.mine already can't charge about 1 month ago.
apprentice said:
I don't think this has anything to do with the update. Mine updated and charges ok.
I did however have a problem charging once (before the update) and I searched the web for solutions. I think you will find it's a problem with the mains charger. It overheats and the thermal cut-out fails to reset. As mad as it sounds the solution is to pop the charger in a plastic bag and pop it in the freezer for 30 minutes. It worked for me and countless others and is worth a try.
Good luck though.
Click to expand...
Click to collapse
Wow! I tried to google search on unable to charge after updates, but could not find any meaningful matches.
I will try this fridge trick, although it's another example that asus really rushed this entire project out! We have been beta testing an unfinished product.... But I guess that's the norm these days.
Thanks!
I find that sine the latest update, the battery drains faster and I have to plug it in and out a couple of times until I see that it's charging..Also, all of a suddent the touchpad (not the keys) will wake up the tablet when it's docked
fldude99 said:
I find that sine the latest update, the battery drains faster and I have to plug it in and out a couple of times until I see that it's charging..Also, all of a suddent the touchpad (not the keys) will wake up the tablet when it's docked
Click to expand...
Click to collapse
The touch pad will not wake up the tablet if you turn wifi of MANUALY before putting the tablet in sleep mode !
It's how I fixed it, waiting for Asus to fix it
Thor_Asgard said:
The touch pad will not wake up the tablet if you turn wifi of MANUALY before putting the tablet in sleep mode !
It's how I fixed it, waiting for Asus to fix it
Click to expand...
Click to collapse
Hmmm..I tried that but the touchpad still turns on the screen
fldude99 said:
Hmmm..I tried that but the touchpad still turns on the screen
Click to expand...
Click to collapse
If it bothers you then you can always disable the touchpad... I'm still on 3.2 but the touchpad always intefered with my typing so I have it disabled by default.
Sent from my Transformer TF101 using Tapatalk
Same problem for me :-( I found that a reboot will solve this until it happens again. Need ASUS to fix.
Sent from my Dell Streak using XDA App
Hopefully yes, a reboot fix the situation. Today, i'm trying to not disabled the wifi (or, turn wifi off manually each time), and i'll see if the USB/SD disconnet again !
BuPe said:
If it bothers you then you can always disable the touchpad... I'm still on 3.2 but the touchpad always intefered with my typing so I have it disabled by default.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
It's not really a bother, but it shouldn't happen. Turns out the tablet, with the new 3.2.1 update is not able to sleep. I think it's something to do with the new wifi "improvement". Using cpuspy, the tablet is not sleeping at all unless I manually turn off wifi and reboot. This needs to be looked into and corrected by Asus, unless I'm incorrect or have an isolated incident.
no, it's note an isolated incident, i have approximatly the same situation here !
Thor_Asgard said:
no, it's note an isolated incident, i have approximatly the same situation here !
Click to expand...
Click to collapse
Thanks for the feedback! It's annoying but not life changing
fldude99 said:
It's not really a bother, but it shouldn't happen. Turns out the tablet, with the new 3.2.1 update is not able to sleep. I think it's something to do with the new wifi "improvement". Using cpuspy, the tablet is not sleeping at all unless I manually turn off wifi and reboot. This needs to be looked into and corrected by Asus, unless I'm incorrect or have an isolated incident.
Click to expand...
Click to collapse
Not the case for me. I had all sorts of sleep/reboot issues with 3.2 (using custom roms and kernels), and nothing resolved them other than a complete return back to stock with a full bios wipe.
Since updating to 3.2.1 and then to Prime 2.01 (sticking with stock kernel), my tablet is turning wifi off when the screen goes off, and is going into deep sleep as evidenced by the fact that it is only using around 2% over 9 hours while not being used. I was concerned that like others I would have sleep/reboot issues when docked as this seems to be a problem, but tested that issue last night and when I checked today after not using it for 10 hours, no reboots, no ramdump.log and battery life used was minimal in line with deep sleep.
I truly believe that the solution to all these issues is to completely return to stock - including the part where after you have removed CWM (if you have it), you start the tablet holding down power and up to enter the asus startup mode and then select the option that wipes everything. But YMMV....
As for my original issue when I started this thread, it turned out the charging issue was indeed a problem with the charger overheating as pointed out by another member (THANKS), as a quick 30 minutes in the freezer seemed to reset the internal thermostat. From now on I unplug when not using the charger.
^^^ That's cool that yours is under control, but mine is stock, unrooted. Don't really have the inclination or motivation to root this thing..But it appears that it is a definite issue for stock, unrooted Transformers, judging by response
Same here, stock, unroot ! But I prefer waiting for Asus inseed of turning back to custom ROM...
Globespy said:
I'm having trouble charging my device.
For some reason, after updating to the new 3.2.1 my tablet win not charge either from the adapter, usb pc connection.
Tried rebooting to no avail.
Click to expand...
Click to collapse
Solution to this is unplug your transformer, keep it as tablet only, press and hold the power button for over 30 seconds, plug in and then switch on.
Worked for me Asus says the issue is a static build up on the device with having external devices plugged in, like hard drives, not sure if thats accurate, but the fix has been solid for me!
My Tablet and Dock have the same issue since the last OTA, charge doesn't works. PLIZ ASUS FIX THIS ISSUE !
8-10 in the freezer and my tablet off for those 10 mins worked for me.
When I first got my nexus 7 it said that it was "charging" when I plugged it in. A few hours later I updated the software, and it always says that the battery is "not charging". However, if I press the refresh button on the battery status page in settings, the charge percentage still goes up slowly. Is anyone else having this problem? I can't figure out how to fix it. I'm worried that the battery might keep trying to charge even after it hits 100% capacity, since it thinks that it is "not charging".
N7 displays battery not charging, though it is.
carnivalkid32 said:
When I first got my nexus 7 it said that it was "charging" when I plugged it in. A few hours later I updated the software, and it always says that the battery is "not charging". However, if I press the refresh button on the battery status page in settings, the charge percentage still goes up slowly. Is anyone else having this problem? I can't figure out how to fix it. I'm worried that the battery might keep trying to charge even after it hits 100% capacity, since it thinks that it is "not charging".
Click to expand...
Click to collapse
I ran into this problem myself where it displays it's not charging under the battery settings and there is no charge icon in the battery icon in the upper right corner. However it is charging. Anyone know of a fix?
Running 4.1.1
Thanks in advance.
Spoke with Google Customer support today, and they aren't aware of this issue. Think it's an issue with the battery sensor. They are sending me a replacement device.
Le sigh.
Thanks for the heads up. I'll try calling Google tomorrow. Do you need to send your device back first? Or will they send a replacement unit to you first?
Rottenbot said:
Spoke with Google Customer support today, and they aren't aware of this issue. Think it's an issue with the battery sensor. They are sending me a replacement device.
Le sigh.
Click to expand...
Click to collapse
I'm having the same problem. Any news on this?
I'm having the exact same issue.
It's weird, because when the tablet is off, then it shows the big charging logo when short-pressing the lock/unlock button.
But still the battery loads OK !
When connecting the charger, loading status of the battery is "disconnected"...
For me the problem persisted for a few weeks then it randomly disappeared, I think after one of the reboots. I first noticed that it resumed working after I charged the Nexus when it was switched off and the big battery sign came on.
Either way, it's probably a software problem so I just ignored it while it was going on...
Its a known software bug. Especially with car chargers. Just check batt level before plugging in then again in a few minutes. You will see its charging regardless of charge indicator.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
madman604 said:
Its a known software bug. Especially with car chargers. Just check batt level before plugging in then again in a few minutes. You will see its charging regardless of charge indicator.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Is the bug supposed to happen even with the original charger ?
My phone is shutting down automatically after showing “google” logo. I went back to stock lollipop 5.0.1 but the problem still persist. It’s working fine with the charger plugged in. If I remove the charger after switching on, if I kept it idle, it will stay on till the battery is empty. But if I try to do something it will shutdown. In recovery mode it works well without the charger.
Please help me is anyone facing the same issue.
may be you should try flashing a new kernel
i tried stock Google images still no use.
Is there any noticeable bulge to the battery? It might be a battery issue.
This is almost certainly a battery issue.
lolcakes203 said:
Is there any noticeable bulge to the battery? It might be a battery issue.
Click to expand...
Click to collapse
I don't think its a battery issue, because if i keep my device idle it'll last 1 day.
It only crashes if i use the phone, even swiping home screens crashes the phone.
Well, you've already gone back to pure stock which rules out a software issue, and so the next thing I thought would be a battery issue. I have read here about defective batteries causing all sorts of problems like losing signal, non responsive touchscreens and bootloops, and so it's a possibility that this is a battery problem.
I got strange problem with my n4..
Battery % randomly change and shut down, unsensible touchscreen, battery icon disappear from menu..
Maybe this hw problem could touch the SW part
that's how my problem started
Battery problem symptoms can manifest themselves in many different ways.
lolcakes203 said:
Battery problem symptoms can manifest themselves in many different ways.
Click to expand...
Click to collapse
ordered a new battery, waiting for the delivery thanks guys for the reply.
zni3h said:
ordered a new battery, waiting for the delivery thanks guys for the reply.
Click to expand...
Click to collapse
me too
No problem at all. Please report back.
lolcakes203 said:
No problem at all. Please report back.
Click to expand...
Click to collapse
battery arrived everything is good
I have a same problem
My nexus 4 cant't turn on without charger plugged in. But when I go to Recovery, it work fine. A few days ago, it's sometime shutdown suddently when I was playing game. Then it worked fine after I plugged charger in and turn it on. Is this battery issue?
So even when the device is fully charged it won't boot into Android?
CalculatedRisk said:
So even when the device is fully charged it won't boot into Android?
Click to expand...
Click to collapse
It can boot with a little trick (press the lock icon on boot screen continuously) and work fine with charger plugged in. When unplugged the phone shutdown immediately
zni3h said:
battery arrived everything is good
Click to expand...
Click to collapse
Does the same issue exists even with a new battery?
Sturdy_99 said:
Does the same issue exists even with a new battery?
Click to expand...
Click to collapse
after the replacement the phone worked perfectly, i had used it for 3 months then i sold it, i can confirm that i was having the exact same issue as karsondang
This is a battery issue. it happened to me too.replacing the battery will fix the issue.
Sent from my Nexus 4 using Tapatalk
I've been having power drain issues for a couple of months now, have tried almost everything but issue isn't resolved. Will replacing the motherboard solve the issue? Coz I suspect a wakelock issue. Below are what I've tried.
The battery has started to drain big time and the Android system is consuming most of the power.
1. Calibrating my battery.
2. Factory reset to January update.
3. Stopping the apps running in the background.
4. Turning off location, wifi and internet.
5. Tried disabling backup of photos.
6. Disabled app preview messages under Google.
7. Tried replacing the physical battery at the service center.
8. Currently running on the June 2018 patch.
Despite doing all this the battery drains big time, even when it's idle, when I'm sleeping.
I'm unable to upload screenshot because it keeps saying that there's a network issue. But the screenshot stats say that the android os consumes most of the battery and SoT was 30 minutes. Phone was idle for most of the time. It came down 100-20% in a few hours.
Android OS is eating away most of the battery.
AkCullen said:
I've been having power drain issues for a couple of months now, have tried almost everything but issue isn't resolved. Will replacing the motherboard solve the issue? Coz I suspect a wakelock issue. Below are what I've tried.
The battery has started to drain big time and the Android system is consuming most of the power.
1. Calibrating my battery.
2. Factory reset to January update.
3. Stopping the apps running in the background.
4. Turning off location, wifi and internet.
5. Tried disabling backup of photos.
6. Disabled app preview messages under Google.
7. Tried replacing the physical battery at the service center.
8. Currently running on the June 2018 patch.
Despite doing all this the battery drains big time, even when it's idle, when I'm sleeping.
I'm unable to upload screenshot because it keeps saying that there's a network issue. But the screenshot stats say that the android os consumes most of the battery and SoT was 30 minutes. Phone was idle for most of the time. It came down 100-20% in a few hours.
Android OS is eating away most of the battery.
Click to expand...
Click to collapse
No, motherboard replacement won't fix the issue. It looks like there's an issue with deep sleep. try a custom kernel and see if that helps
While my drain is not as bad as the OPs, it is bad. I have taken to turning on Airplane mode when the phone is not in use. Overnight drain is 20%+ when idle if not in Airplane mode, 1% if it is. SoT has gone from the original 6-7 hours to about 2.5 to 3 hours. Battery health is at 96% according to battery app. Held awake seems to be very high if not in Airplane mode, with almost 3 hours overnight when the phone is not in use. Main battery use is from Kernel and Phone. HOPEFULLY these issues will be resolved with 8.1 or P, but I won't hold my breath.
Unfortunately none of these issues were addressed in 8.1 and I'm not sure if they even recognized this issue, for it to be solved in future updates.
AkCullen said:
Unfortunately none of these issues were addressed in 8.1 and I'm not sure if they even recognized this issue, for it to be solved in future updates.
Click to expand...
Click to collapse
You're probably the only one or one of the very few with bad battery drain (80% in just a few hours while idle) on the stock rom so you probably got a lemon or its damaged from a fall.
Flashing the Jan 2018 rom wasn't smart at all since there was alot of news that the first Oreo update was very buggy and was pulled. 8.1 is also buggy and also got pulled. Best to flash the stock April rom for less problems.
barrack1 said:
You're probably the only one or one of the very few with bad battery drain (80% in just a few hours while idle) on the stock rom so you probably got a lemon or its damaged from a fall.
Flashing the Jan 2018 rom wasn't smart at all since there was alot of news that the first Oreo update was very buggy and was pulled. 8.1 is also buggy and also got pulled. Best to flash the stock April rom for less problems.
Click to expand...
Click to collapse
Thank you for your response. The phone does not have any physical damage. Flashing the Jan 2018 rom was a move by the service center despite telling them it wouldn't help.
I managed to figure out using GSAM that the issue is being caused by 700000.ssusb kernel wakelock and I have no clue how to fix it. Do you have a workaround for it?
As this option is USB related, you could try changing the usb mode in developer options:
Settings>System>Developer options>Select USB configuration - change it to "charging" (I note mine is currently MTP)
I'm 100% guessing here but maybe if it's set to charging it won't be looking for OTG devices?
kudos1uk said:
As this option is USB related, you could try changing the usb mode in developer options:
Settings>System>Developer options>Select USB configuration - change it to "charging" (I note mine is currently MTP)
I'm 100% guessing here but maybe if it's set to charging it won't be looking for OTG devices?
Click to expand...
Click to collapse
I've tried setting it to all possible modes under USB configuration including "charging", but doesn't seem to help.
OK, it was only a thought.
I did read on another thread someone say they plugged and OTG adaptor (no OTG device attached) and it stopped the problem, not a solution but worth a try, if you have one.
Have you inspected carefully with a torch inside the USB hole for any debsit that has got in there?
kudos1uk said:
OK, it was only a thought.
I did read on another thread someone say they plugged and OTG adaptor (no OTG device attached) and it stopped the problem, not a solution but worth a try, if you have one.
Have you inspected carefully with a torch inside the USB hole for any debsit that has got in there?
Click to expand...
Click to collapse
Yes I read about that work around too. Haven't tried it yet as I do not have an OTG adapter. Will post a response once I try.
Haven't inspected the USB port either, will do.
AkCullen said:
Yes I read about that work around too. Haven't tried it yet as I do not have an OTG adapter. Will post a response once I try.
Haven't inspected the USB port either, will do.
Click to expand...
Click to collapse
Can you try this:
Reboot phone, when its rebooted, plug the charger in and out once.
kudos1uk said:
Can you try this:
Reboot phone, when its rebooted, plug the charger in and out once.
Click to expand...
Click to collapse
Will do and update the thread.
AkCullen said:
Will do and update the thread.
Click to expand...
Click to collapse
Most of the threads have a reboot method that works for the user but they all vary a little bit, this works for this user:
In my case a kernel wakelock called "7000000.ssusb" was keeping my phone from entering deep sleep. I resolved it by plugging my charger, unplug it and turn it off immediately, wait a few minutes and reboot. However it is a specific solution for that bug.
Click to expand...
Click to collapse
I think you might need to play around a bit and see what works for you.
Don't forget to do the Better Battery Stats dump I posted in the other thread.
kudos1uk said:
Most of the threads have a reboot method that works for the user but they all vary a little bit, this works for this user:
I think you might need to play around a bit and see what works for you.
Don't forget to do the Better Battery Stats dump I posted in the other thread.
Click to expand...
Click to collapse
I've already tried the plug in - screen on - unplug - reboot, but did not work for me. I'll post the dump over the weekend.
kudos1uk said:
As this option is USB related, you could try changing the usb mode in developer options:
Settings>System>Developer options>Select USB configuration - change it to "charging" (I note mine is currently MTP)
I'm 100% guessing here but maybe if it's set to charging it won't be looking for OTG devices?
Click to expand...
Click to collapse
I'm just noticing this today,
When I click on the USB configuration and set it to "Charging" from "MTP", it doesn't actually change.
The pop up that shows different options shows that it's in charging but it's actually still in MTP. I'm not sure if this could be the cause.
Do you know how to fix this?
AkCullen said:
I've already tried the plug in - screen on - unplug - reboot, but did not work for me. I'll post the dump over the weekend.
Click to expand...
Click to collapse
Screenshots for USB configuration not getting switched.
AkCullen said:
Screenshots for USB configuration not getting switched.
Click to expand...
Click to collapse
You need to back out of developer options and go back in again to see the change.
Plug the charger in
Change mode to charging
Back out of developer options
Re enter developer option - should no be on charging.
Plugging in, changing the selection, backing out and going back in does not show changes: Change setting to Charging->back->back. Developer options-> Select USB Configuration shows Media Transfer Protocol, while the Selection itself shows charging. (it's plugged in, so makes sense) I tried changing this to Music Transfer Protocol last night and it made zero difference in the battery drain. I just tried the plug in, turn off, unplug thing. I will let you know if I see any difference. USB port is clean under 5x magnification. NETLINK and timerfd shows more activity than 7000000.ssusb on my device, but all of them are higher than they should be I think.. NETLINK shows 324644 wakelocks!!! Timerfd shows 65337 and 7000000.ssub shows 33256! The thing is, the phone has been used very little since the last full charge!
That's odd, I dont have the issue and when I choose "charging" it stays on that setting even after unplugging the charger. Each time I re-enter developer options it's still set to charging.
The fact yours changed links in with the wakelock, your phone appears to think something is plugged in which is why I asked you to check for debris in the port. I'm wondering if you have a damaged usb port?
If it's software related, I don't think resetting it will help, I'm no expert but I'm assuming as its a kernel wakelock & I'm sure a reset has no effect on the kernel? maybe others can advise.
I wonder if flashing the stock Kernel would help, I'm only thinking out loud, I'm sure others can give better flashing advice.
Do the wakelocks show up while charging?
Your next step really has to be to post a dump on the official thread, a few people are complaining about this battery drain but nobody has posted a dump to the official thread yet.
KB_Thailand said:
Plugging in, changing the selection, backing out and going back in does not show changes: Change setting to Charging->back->back. Developer options-> Select USB Configuration shows Media Transfer Protocol, while the Selection itself shows charging. (it's plugged in, so makes sense) I tried changing this to Music Transfer Protocol last night and it made zero difference in the battery drain. I just tried the plug in, turn off, unplug thing. I will let you know if I see any difference. USB port is clean under 5x magnification. NETLINK and timerfd shows more activity than 7000000.ssusb on my device, but all of them are higher than they should be I think.. NETLINK shows 324644 wakelocks!!! Timerfd shows 65337 and 7000000.ssub shows 33256! The thing is, the phone has been used very little since the last full charge!
Click to expand...
Click to collapse
Yes that's exactly what's happening as described in first point.
I observed NETLINK sends more wakelocks but if you see the time it kept the system awake in the background would be comparitively less.