Related
I am now under the assumption that my TF thinks the battery is dead even though there was a full charge in it before I shut it down yesterday. I have been having issues regarding turning it on and couldn't even get into APX mode. I have just tried APX again and manged to get connected, started to run NVflash, then the screen came on showing the large battery image with the red power amount tne just disconnected. I had the TF on charge all night to so there should be full battery.
Anyone else have this issue or know about a fix?
Thanks
Seg
Can you get to recovery? Have you tried reseting battery stats?
Also are you using stock charger or have you charged the tablet with another device?
AzureusPT said:
Can you get to recovery? Have you tried reseting battery stats?
Also are you using stock charger or have you charged the tablet with another device?
Click to expand...
Click to collapse
Cheers for your reply m8. At this moment in time, I can't get into anything. Managed to get APX mode earlier, but like I say, it shut down thinking it had no battery, even though it should have been full. Yes it is stock charger and not I haven't used any other method of charging. I am unrooted and stock so other than using CWM, I don't know how to wipe battery stats. Will wiping Battery stats help? What does it wipe?
Thanks
Seg
Well I emailed ASUS this morning and have got an email back from them saying it needs to go for service. Just filled out the form for RMA, now just waiting for return details.
Gutted, not even 4 weeks old.
Seg
Wiping battery stats clears the data that the device has of the battery. Its like reseting or recalibrating it if the device's battery level isn't displayed as it should be.
EDIT: Seems you posted before I finished with this one... Since ASUS told you to service it, it might came like that from the start. Good thing you didn't root or install a custom ROM.
AzureusPT said:
Wiping battery stats clears the data that the device has of the battery. Its like reseting or recalibrating it if the device's battery level isn't displayed as it should be.
EDIT: Seems you posted before I finished with this one... Since ASUS told you to service it, it might came like that from the start. Good thing you didn't root or install a custom ROM.
Click to expand...
Click to collapse
Thanks Azureus.
I looked at wiping the battery stats when I first rooted, but wasn't sure what it did so just left it.
Yeah it is a good job it aint rooted. Just wondering now on what the turn around will be. This thing has grown to be like my right hand, lol
Seg
Well looks like I am getting a replacement tommorrow all being well. Just got an email back from the place where I bought my TF from and they have 1 left in stock. Gonna leave the RMA ongoing until I have the new one in my hands.
Ooooh, can't wait.
Hello guys.
I installed Slim Bean 4.1.1 version(3.0.31 Semaphore) few months ago(from this THREAD) on my Galaxy S I9000, and everything worked really well, until last week.
First problem- my speakerphone started to automaticly turn on on every phone call, and my screen sometimes used to rotate randomly after I turn display on. I couldn't fix this, but I think somehow my phone turned on the dock mode, but I didn't know how to switch it off. I also couldn't connect my phone with computer, when I connected it, it just charged battery. And this lasted about for a week, until today. Today everything came back to normal, speakerphone wasn't activated on calls, and I think screen stopped rotating when screen was off, but when I wanted to charge my batter, the phone didn't show any signs of charging, like I didn't put charger in. I'm left with 4% of the battery, I tried to charge it through pc cable, but It didn't work either.
So, is there a solution, can anyone help me?
I forgot to mention, I never updated Slimbean, it's still on 4.1.1. version.
Thank you in advance, and sorry for my bad english.
Could be a bad battery. Try using the phone on A/C power, with no battery installed, & see if you get the same weird behavior.
post-mortem said:
Could be a bad battery. Try using the phone on A/C power, with no battery installed, & see if you get the same weird behavior.
Click to expand...
Click to collapse
You mean connected to charger, without battery at all?
It won't turn on like that at all. I never knew that was even possible tbf.
Maybe some devices won't, but AFAIK, most devices should power on & be functional, which doesn't help diagnose your problem.
Now it's working, I fixed it somehow, I pulled battery out couple of times, and did couple of restarts, so it's finally charging. And now it's back to old problems where my speakerphone turns on automaticaly on every phone call.
I get the feeling that the problem's gonna come back. 1st priority should be to charge the battery fully.
I did that last night. What's next? :laugh:
I'm guessing it's either a bad motherboard, or a bad battery. Be prepared for the worst.
post-mortem said:
I'm guessing it's either a bad motherboard, or a bad battery. Be prepared for the worst.
Click to expand...
Click to collapse
Battery is working well(at the moment), so I don't see how could damaged baterry affect software problems such as automaticaly turning on the speakerphone, and not being able to connect phone with PC.
You'd be surprised what abnormal voltage levels can do to electronic devices.
post-mortem said:
You'd be surprised what abnormal voltage levels can do to electronic devices.
Click to expand...
Click to collapse
Okay, I'll probably change it in few days.
Now, I have other problem.. I wanted to install Slim Bean 2.7, but when I enter recovery mode, do full wipe, installation aborts around 26% saying, "E: Error in /sdcard/Slim-i9000-2.7.0-OFFICIAL.zip (status 0) ", and above "installation aborted".
You sure that ROM was intended for your device? Sounds like the difference between update-script and updater-script. Different devices use different methods to flash ROMs.
post-mortem said:
You sure that ROM was intended for your device? Sounds like the difference between update-script and updater-script. Different devices use different methods to flash ROMs.
Click to expand...
Click to collapse
The file name is Slim-i9000-2.7.0-OFFICIAL, it is the right ROM surely?
I have no idea. You need to check the thread from where you downloaded it.
post-mortem said:
I have no idea. You need to check the thread from where you downloaded it.
Click to expand...
Click to collapse
I will, I need 2 or 3 more posts. Anyway, tnx for your time friend.
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
---Edit---
I should note that I can have all the radios on when it is plugged in, I just can not have them on when unplugged right now.
mikeoconnor said:
Yesterday my phone started an issue where it will not stay on when unplugged. I have tried
1) clearing the cache
2) clearing the cache and dalvak cache
3) backup up the phone wiping (reset) wiping cache and dalvak cache.
none of those work
I have found that if I boot with it plugged in the phone works fine till it is unplugged. Also I have noted that when it power downs when I unplug it it will reset the wall paper. Also I have noted if I put the phone in airplane mode and turn off the GPS (I have to do both) it will stay on when unplugged but all wireless connection must be off. Also I don't have this problem in clockworkrecovery mode. (also I have noted that starting with this issue I see another issue, might be related might now, that on some boot up I see Trebuchet has stopped error)
Right now I can "live" with it for a short time if needed (I can turn off all radio com stuff when I unplug it to move it to a battery powered case, and turn everything on, but it will be anoying while I have to do this)
So my questions are
1) what could be causing this?
2) what logs can I look at to see what the issue might be (or logs should I post here for some one with more knowledge then I can look at)
3) is the phone savable, the battery seems to be fine when all the radios are turned off (ether via the OS, or when booted into recovery mode)
Thanks for any advice I can get.
Click to expand...
Click to collapse
What ROM are you running? Rooted or not?
If you're rooted/on a custom ROM, I would make a backup of all non-system apps and settings and try to start over. The fact that you dont get that when in recovery is the biggest indicator.
First, back up all NON-SYSTEM apps/settings with Titanium backup (or something similar).
Then follow my fix >>>HERE<<< and see if that helps
I am currently on CM-10-20130728-NIGHTLY, I should also note one thing I did try was to update the ROM yesterday AFTER the problem started (problem started at 4pm I updated the ROM at 7pm), it use to be CM-10-20130526-NIGHTLY. I will look at your link and see if that works.
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
I hope you are wrong, but I fear you are right. But I am going to do the steps cited above and see if that helps, right now I am doing a second back up (first was Titanium backup, now is the CWRM backup) and I am going to do the flashing stuff who knows. Don't have much to loss, and I am still open to other ideas, if any one else has them.
tommyboy8125 said:
To me it sounds like you have a fried battery. It only has enough power to run your phone if everything is turned off or its plugged in.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
That's a distinct possibility, but not the only cause for what he's experiencing. Jumping the gun and buying new hardware usually results in money spent on hardware that wasn't needed a good portion of the time.
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
mikeoconnor said:
Well I did both wipes, installed the ROM (did not do any data restore, just to be safe) powered it up, unplugged it and it looked like it was going to stay on, I opened the web browser and the phone turned off again. I fear it just might be the battery now, maybe I can get to a t-mobile store and see if they will let me test a new battery to see if it will work (before I buy a new one) unless any one have other things to look at first. (right now I am restoring my phone to a state from before I started all this work, so as if I did nothing)
Click to expand...
Click to collapse
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
jparnell8839 said:
what color is the battery indicator? If it's still white, Tmo might just replace the battery as is
Click to expand...
Click to collapse
It is white (indicating no water damage) also the other indicators on the phone are white. I hope you are right on that that would be sweet, I will stop by the tmo store before I head home tonight. And thanks for all the help (I now have to go back and "Thank" all the posts by you two, it is appreciated)
Funny part is I took the battery out to double check the sticker (even though I was sure it was still white) and the phone died even though it was still plugged in (so I guess I need both the battery and power plug for now)
mikeoconnor said:
It is white (indicating no water damage) also the other indicators on the phone are white.
Click to expand...
Click to collapse
you might get lucky and get a free one out of it. cant hurt to ask
Thanks all I picked up a new battery today and I looks like it is working. Sadly T-Mobile did not replace it for free but the phone is working again.
Sent from my Thrive using Tapatalk 2
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Nobody?
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
denzel09 said:
Before to think if it's a battery problem you have tried to switch to dalvik and see what happens on long time?
Click to expand...
Click to collapse
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
rogeriorp said:
Not exactly, mainly because it never happened before. I am using ART since it updated to KK, started recently only.
Click to expand...
Click to collapse
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
fabus said:
Can you grab logcat log? Maybe it can say something when it happens.
The best way to do this is by Eclipse -> CatLog viewer. You won`t loose log messages when device will be rebooted.
Did you try wiping cache / dalvik ? System will rebuild everything so you won`t loose your data and it can fix your problem.
Cheers,
Click to expand...
Click to collapse
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
rogeriorp said:
I did only wipe cache partition before, never the dalvik. I might give it a try the next time it happens.
Also, to catch a logcat requires root? If so I can't grab one.
Click to expand...
Click to collapse
Try catlog, i don't remember if need root honestly
Alright, got the guidances. Thank you both for the help, will leave some feedback later on.
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
rogeriorp said:
I found those sudden reboots happening on my device, XT1033 with ART unrooted running the single sim firmware. Everything was fine for a long time, but the last weeks its been happening. It simply freezes, no matter doing what going into a point that when I press the power/lock, the screen won't even turn itself back on, forcing myself to force-reboot in order to work again. I also notice that when it happens, the device has a downfall in the battery graph even tho not much was consumed and even losing a couple minutes on the screentime. I will embed a photo.
Maybe switching back to Dalvik fixes it? Or something else is the issue? I got no "weird" apps installed. Suggestions?
Click to expand...
Click to collapse
I just unlocked, rooted, flashed recovery and custom ROM on a refurb unit. I had kinda the same issue with this phone out the box stock. Mine will work perfect as long as its plugged in to either PC or wall charger. Once unplugged, pushing power to wake causes screen to shutoff after a few seconds or freeze, then reboot. Doesn't seem to be software related, as a clean install of pacman did nothing different. Touchscreen gets very unresponsive, also causing reboots.
sent from my Gs3
rogeriorp said:
An update: it happened twice in a row just now. Switched back to Dalvik just in case. Will keep this one post updated to not spam.
Click to expand...
Click to collapse
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
rogeriorp said:
I have this phone for 4 months already, its weird it happens out of no where tbh. Switched back to Dalvik yesterday and no issue yet, switching runtimes compile them all over again right?
Click to expand...
Click to collapse
yes, you should see "Updating Android" with application number every time you switch DALVIK<->ART.
Cheers,
fabus said:
- LogCat requires root to see system messages, otherwise you will see only high layer user messages.
- I tryied ART and didn`t have such issue, just came back to Dalvik because I noticed that ART uses more cache (which impacts overall virtual SD capacity) and didn`t see any improvement in performance.
@joeyhdownsouth - could you give us logcat / dmesg log on some share? It seems you have some issues while charging. It can be causes either by wrong charger (too high/low current, but moto should control it) or maybe some app causes this when you unplugs usb cable.
Anyway - without log we cannot say anything.
Cheers,
Click to expand...
Click to collapse
Waiting on Motorola charger to come in, then if no change, I'll pull a logcat.
sent from my Gs3
I also experienced the last 3 days complete freezes. No idea what was going on...
Unfortunately I couldn't pull any log messages from the phone by that time. Half an hour later it just responded normally... Didn't see if it rebooted in between or what exactly happened
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
rogeriorp said:
Just a heads up: going back to Dalvik got me rid off those freezes. Something on ART was messed up.
Click to expand...
Click to collapse
I never even checked to see which one it was using when I first got it.
sent from my Gs3
joeyhdownsouth said:
I never even checked to see which one it was using when I first got it.
sent from my Gs3
Click to expand...
Click to collapse
By deault it is Dalvik. If you have new phone so it will be Dalvik.
Did you said two posts before that you were using some 3rd party charger (not Motorola cable)?
Funny, but yesterday I had similar issues with freezes and random reboots. I was using some cable taken from Friend (not Motorola) and weird things started to happening:
- It was indicated on a screen that phone is charging (probably discovered usb cable plugged it), but it was discharging faster and started rebooting (because it reached below 1% battery state) and after some reboots battery was so discharged that phone couldn`t come up.
This usb cable was attached all the time to my phone and a computer.
- Next I connected phone to my reglar charger for night (from Zte Tablet, but really good and charges fast, never had issues with it) and it was fully charged.
On the morning I played music for 15 minutes by loudspeaker and then put phone into my pocket for 10 minutes (walk to take a bus).
When I took my phone back into my hand battery was dropped to 1%! (from over 95% to 1% in 10 minutes), but phone didn`t shut down.
This 1% remain for couple of hours (something like 2-3) without shutting phone down.
I took another charger and connected to it again - phone was charged to 100% in less than 30 min (usually takes up to 3hrs) and now works like before (no huge and weird battery drain).
Btw. I`m on faux kernel 007m.
Weird... looks like moto g doesn't like be connected to a PC by other cable than Motorola
Hi All,
I'm facing a weird issue with my phone from more than 2 months and it has reached a frustrated level now. It used to shut off at levels like 15%, sometimes between 15-25%. But nowadays, it shuts down automatically at 40-60% and that is really unreliable. So, i wanted to check if there are other people facing the same issue or is it only my device. Please share your views, any possible solutions, possible reasons, and if applicable, similar experiences.
thanks for the info, i got my oneplus one back in 2013, hopefully it will not shutdown after a while. i have not found such problem and hope i will not in the future as i want to have the phone for at least 5 years
karthics4 said:
thanks for the info, i got my oneplus one back in 2013, hopefully it will not shutdown after a while. i have not found such problem and hope i will not in the future as i want to have the phone for at least 5 years
Click to expand...
Click to collapse
Well i do hope you won't face any issues with your phone. But this is totally weird. This is making my phone unreliable for me.
Sent from OnePlus One
abhibnl said:
Hi All,
I'm facing a weird issue with my phone from more than 2 months and it has reached a frustrated level now. It used to shut off at levels like 15%, sometimes between 15-25%. But nowadays, it shuts down automatically at 40-60% and that is really unreliable. So, i wanted to check if there are other people facing the same issue or is it only my device. Please share your views, any possible solutions, possible reasons, and if applicable, similar experiences.
Click to expand...
Click to collapse
Clear all data from recovery and reflash system with fastboot images. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
kushal.purkar said:
Clear all data from recovery and reflash system with fastboot images. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Click to expand...
Click to collapse
If you won't mind asking, how actually will that help with this issue? I'm just curious to know
abhibnl said:
If you won't mind asking, how actually will that help with this issue? I'm just curious to know
Click to expand...
Click to collapse
I had the same issue after I updated to MM and recently after latest update also. I had to do the same thing. Reason behind that was xposed was incompatible. But as I flashed everything. (/system/data too ) now its working fine
kushal.purkar said:
I had the same issue after I updated to MM and recently after latest update also. I had to do the same thing. Reason behind that was xposed was incompatible. But as I flashed everything. (/system/data too ) now its working fine
Click to expand...
Click to collapse
Thanks for the details. Unfortunately, i would need some time to perform this as i barely get time to flash roms. Thanks again!
Sent from OnePlus One
Dude... just get a new battery...
Traace said:
Dude... just get a new battery...
Click to expand...
Click to collapse
Just the answer i was looking for [emoji106] [emoji106]
Sent from OnePlus One
abhibnl said:
Well i do hope you won't face any issues with your phone. But this is totally weird. This is making my phone unreliable for me.
Sent from OnePlus One
Click to expand...
Click to collapse
thanks so much, bought it after my nexus4 died which im still sad about because its one of my 1st real android phones after having a contract android phone.
As an update, i kept my phone on charge for straight 4-5 hours. and now it shuts down after 20-25%. Definitely an improvement. But still it's a mystery why does it show this bug in the first place.
Umm, how has no one mentioned maybe trying battery calibration!? Seems like a fairly obvious first step here to take before swapping out for a new battery.. Plug the phone in and let it charge entirely. Even at 100% in Settings > Battery it will still show "100% - Charging on AC" (or USB whatever you've got connected)
You need to wait for that to turn into "100% - Charged." Then, calibrate using any battery calibration app from the playstore, ( I use this one )
After it charges to 100% - Charged, hit "calibrate" in the app, disconnect the charger, and let it drain entirely. You might find it dying out before 0% once again, but this hopefully should have been the last time. Plug the phone in and switch it on as soon as you can while it starts to charge. Let it charge uninterruptedly to 100% - Charged, again.
Not saying this might solve it 100% but it is an option to try.
GuitarGuy96 said:
Umm, how has no one mentioned maybe trying battery calibration!?[emoji14]Seems like a fairly obvious first step here to take before swapping out for a new battery.. Plug the phone in and let it charge entirely. Even at 100% in Settings > Battery it will still show "100% - Charging on AC" (or USB whatever you've got connected)
You need to wait for that to turn into "100% - Charged." Then, calibrate using any battery calibration app from the playstore, ( I use this one )
After it charges to 100% - Charged, hit "calibrate" in the app, disconnect the charger, and let it drain entirely. You might find it dying out before 0% once again, but this hopefully should have been the last time. Plug the phone in and switch it on as soon as you can while it starts to charge. Let it charge uninterruptedly to 100% - Charged, again.
Not saying this might solve it 100% but it is an option to try.
Click to expand...
Click to collapse
Well already tried and i may sound a bit silly, but studies have proved that battery calibration is a myth. Android automatically cleans the batterystats.bin file after every single full charge. Rest assured, i have already done that with no avail.
Sent from OnePlus One
I had the same problem, phone was switching off @ 40% and at times @35%. Battery calibration certainly helped. No more problems now. Works well if the phone is rooted.