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"
Today my Epic no longer mounts for some reson to anything,i tryed pc and ps3.
It wont even show "usb debugging" and "mount" optioms in the pulldown bar!
Only thing it does is charges and orange led comes on when pluged in.
I tried swithing usb debuging on and off,tried with usb debugging off,cleared cache,cleared dalvic cache,pulled out battery and sd,mounted and unmounted sd,reformated sd,cleared battery stats and nothing!
It wont even show up under "adb devices",and I can switch "usb debugging" on and off while its pluged in-which is not normaly possible(it has to be unpluged first in normal circumstances).
Any ideas?
Not sure about the PS3, but for the computer try reinstalling the drivers and see if that does it. Do you know if you did anything to trigger this? Have you experienced any other bugs lately?
Sent from my Samsung Epic
lviv73 said:
Today my Epic no longer mounts for some reson to anything,i tryed pc and ps3.
It wont even show "usb debugging" and "mount" optioms in the pulldown bar!
Only thing it does is charges and orange led comes on when pluged in.
I tried swithing usb debuging on and off,tried with usb debugging off,cleared cache,cleared dalvic cache,pulled out battery and sd,mounted and unmounted sd,reformated sd,cleared battery stats and nothing!
It wont even show up under "adb devices",and I can switch "usb debugging" on and off while its pluged in-which is not normaly possible(it has to be unpluged first in normal circumstances).
Any ideas?
Click to expand...
Click to collapse
Let me guess.. You're using the stock Samsung Cable?
acer1096xxx said:
Not sure about the PS3, but for the computer try reinstalling the drivers and see if that does it. Do you know if you did anything to trigger this? Have you experienced any other bugs lately?
Sent from my Samsung Epic
Click to expand...
Click to collapse
I have no idea what trigered it.Its not my pc-i know that much.Yesterday it mounted to my pc and my ps3,and today it doesnt mount to anything,lol.
I did flash the Genocide kernel yesterday on my Syndicate rom but it monted fine with it.
I even flashed back to my previous kernel(Twilight) and still no mount!I installed firefox today too but I dobt that it has anything to with it.
Yeah,bassicly it just stoped working,maybe I need to clear data/cache for some app or something,sht im out of ideas.
qbking77 said:
Let me guess.. You're using the stock Samsung Cable?
Click to expand...
Click to collapse
Well my stock went dead for no reason,then I used good thick usb that I got at radioshack and that went dead,now im using usb from my old Samsung Memoir which is probably the best cable out of these 3,but it dint see much use untill lately because its real short.
I dont think the cable is dead because the phone still charges-with my other two dead cables it didnt.
Plus I always had this cable pluged in ps3 for easy transfers between Epic.
I think it got something to with with my rom but I dont wanna reflash and waste 2-3 hours off setting up my phone just to find out that it wasnt the problem.
Another thing I noticed is that lately when transferimg files to ps3 it would just unmount in the middle of a transfer.
qbking77 said:
Let me guess.. You're using the stock Samsung Cable?
Click to expand...
Click to collapse
I would bet on that, the same thing happened to me the other day with the stock cable. Its only good for charging really
Sent from Z's phone with an ever-changing sig.
I'd highly recommend going and buying a blackberry cable... only like 5 bucks and I'm sure your problems will be solved.
qbking77 said:
Let me guess.. You're using the stock Samsung Cable?
Click to expand...
Click to collapse
would this be my issue as well, even though it shows up as mounted in odin and i can odin modems and roms?
Do you have debugging turned on? Mine requires it be on.
Sent from bat country!
lviv73 said:
Today my Epic no longer mounts for some reson to anything,i tryed pc and ps3.
It wont even show "usb debugging" and "mount" optioms in the pulldown bar!
Only thing it does is charges and orange led comes on when pluged in.
I tried swithing usb debuging on and off,tried with usb debugging off,cleared cache,cleared dalvic cache,pulled out battery and sd,mounted and unmounted sd,reformated sd,cleared battery stats and nothing!
It wont even show up under "adb devices",and I can switch "usb debugging" on and off while its pluged in-which is not normaly possible(it has to be unpluged first in normal circumstances).
Any ideas?
Click to expand...
Click to collapse
What was the end result of this? Did you get it sorted out?
My Epic started showing this same behavior yesterday. Not recognized in ODIN, ADB, Mass Storage mode or downloader mode. Tried three cables (two Samsung and one HTC) and four different computers and the result is the same: charges but not detected as a USB device.
Bad USB port on the Epic?
same problem for me
started having the same problem here after flashing back to stock ec05 from the new mtd cm7. im using the blackberry cable but it wont recognize my phone in odin or anything. i did everything correctly to get back to ec05 so i tried updating ota to gingerbread and it didnt fix it. only blessing is everything is stock so i can just take it into sprint but id rather not have to
i installed a file explorer program that runs as an FTP site...
and just ftp my files over...
maybe i'll setup soemthing with JPsoft.com's take command to automate it..
since it does batch file like ftp usage.
either that or tasker...
i'm a little disturbed at all the clutter on my sd card from various aps though.
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?
I have Samsung galaxy s4. The phone was working fine for about 6 months but from last month it hasn't. Whenever i charge my mobile either through wall charger or usb cable, the phone freezes. I have to unplug the charger in order to get it back working. I have tried removing battery for 30 seconds still the problem exists. I have the latest android kitkat. I am attaching the screenshots about phone. Please help me i m really getting irritated.
Plzzz helpp
harvir46 said:
I have Samsung galaxy s4. The phone was working fine for about 6 months but from last month it hasn't. Whenever i charge my mobile either through wall charger or usb cable, the phone freezes. I have to unplug the charger in order to get it back working. I have tried removing battery for 30 seconds still the problem exists. I have the latest android kitkat. I am attaching the screenshots about phone. Please help me i m really getting irritated.
Click to expand...
Click to collapse
No this issue before. Have you root your device? try to clear cache see if it solve the problem
kenji1996 said:
No this issue before. Have you root your device? try to clear cache see if it solve the problem
Click to expand...
Click to collapse
Changing the charger solved the ptoblem. Btw thanks for ur suggestion
Randomly out of the blue I started getting mhl_wake draining my battery, it's stopping my phone from deep sleeping and never stops running. It just happened randomly and haven't changed anything. Reboots do nothing as it just starts again, is there something I can do?
imlgl said:
Randomly out of the blue I started getting mhl_wake draining my battery, it's stopping my phone from deep sleeping and never stops running. It just happened randomly and haven't changed anything. Reboots do nothing as it just starts again, is there something I can do?
Click to expand...
Click to collapse
Hi experts,
I am also having the same issue. And my laptop is not detecting the internal storage but charges the device.
Device: AT&T Samsung Galaxy S4 SGH-i337
Running 5.0.1 Lollipop
Please help.
Many thanks in advance,
TVS
thoppays said:
Hi experts,
I am also having the same issue. And my laptop is not detecting the internal storage but charges the device.
Device: AT&T Samsung Galaxy S4 SGH-i337
Running 5.0.1 Lollipop
Please help.
Many thanks in advance,
TVS
Click to expand...
Click to collapse
clean your usb port or replace it.
Lennyz1988 said:
clean your usb port or replace it.
Click to expand...
Click to collapse
In fact, less than a week ago, there was an intermittent charge problem. Even if I plugged in to the charger for the whole day, the battery never reached 80%.. So I took it to the repair shop. The tech tried to replaced with the new port two times and still had the same issue. We tried a brand new battery too. So I came back with the original port. Now, the charging has become faster after doing the factory data reset. But I figured out the mhl_wake causing the battery drain continuously with the help of BetterBatteryStats app. I wanted to root my device as well as access the internal storage but unfortunately my laptop or any other PC doesn't detect my device at all. I am suspecting bigger hardware problem unless it is a bug in the code. Btw, I am running the official AT&T Lollipop code only.
Thanks,
TVS
thoppays said:
In fact, less than a week ago, there was an intermittent charge problem. Even if I plugged in to the charger for the whole day, the battery never reached 80%.. So I took it to the repair shop. The tech tried to replaced with the new port two times and still had the same issue. We tried a brand new battery too. So I came back with the original port. Now, the charging has become faster after doing the factory data reset. But I figured out the mhl_wake causing the battery drain continuously with the help of BetterBatteryStats app. I wanted to root my device as well as access the internal storage but unfortunately my laptop or any other PC doesn't detect my device at all. I am suspecting bigger hardware problem unless it is a bug in the code. Btw, I am running the official AT&T Lollipop code only.
Thanks,
TVS
Click to expand...
Click to collapse
One more info, the battery draining stops when the cache is cleared from storage settings or formatted in the recovery mode. But it is temporary workaround only because the battery starts draining due to mhl_wake wakelock after sometime.
You have the memory leak bug( all that i know if a process is doing a heavy usage,even if you kill it [force stop] then its memory leak bug)
Sent from my GT-I9505 using Tapatalk