This started last night. My galaxy nexus is around a year and a half old. Last night the phone started not charging with any wall plug including connecting to to multiple ac and computer outlets with multiple cables. I have used a new battery too and it is not working. I tried updating my kernel and that wont work. I moved the usb pin up and still nothing. My only solace is that it will charge while turned off. But VERRRRYYYY slowly. Thanks for your help.
Edit: The battery when off does not actually charge but the charging screen gets shown
stringcheese166 said:
This started last night. My galaxy nexus is around a year and a half old. Last night the phone started not charging with any wall plug including connecting to to multiple ac and computer outlets with multiple cables. I have used a new battery too and it is not working. I tried updating my kernel and that wont work. I moved the usb pin up and still nothing. My only solace is that it will charge while turned off. But VERRRRYYYY slowly. Thanks for your help.
Edit: The battery when off does not actually charge but the charging screen gets shown
Click to expand...
Click to collapse
I had this issue recently and I believe it is due to TWRP v2.6 go back to 2.5 and see if that fixes it
LibertyMonger said:
I had this issue recently and I believe it is due to TWRP v2.6 go back to 2.5 and see if that fixes it
Click to expand...
Click to collapse
I'm using TWRP 2.6 and no charging problems here. Is it a known issue on TWRP's site?
DroidOnRoids said:
I'm using TWRP 2.6 and no charging problems here. Is it a known issue on TWRP's site?
Click to expand...
Click to collapse
I bet if you make a nandroid backup using TWRP 2.6 and then try to copy it to your pc it will not copy. This is how I found out TWRP 2.6 was causing USB issues. Now that I am back on 2.5 all is fine.
Nah it's not TWRP problem
I'm using 2.4 but still having exactly same problem
I guess it's charging port related problem
Sent from my Galaxy Nexus using xda premium
seriousia said:
Nah it's not TWRP problem
I'm using 2.4 but still having exactly same problem
I guess it's charging port related problem
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Just 3 days ago I couldn't get my phone to charge through USB or AC outlet, I thought it was kernel related so tried flashing other kernels and that didn't fix it. I wanted to flash back to stock to see if that fixed it but couldn't cause I wanted to keep a nandroid backup on my PC in case my sdcard got wiped, I tried all day to copy my nandroid to my PC and it would never copy more than 8mb, the small files so I finally thought to change TWRP back to 2.5 and make a new nandroid and BAM it worked and my phone started charging again. Weirder things have happened and the truth is sometimes stranger than fiction! lol
So maybe it was caused from restoring TWRP 2.6 nandroids or something related all I know is this was true in my case. May not happen to everyone but i have seen others with these same issues recently.
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
DroidOnRoids said:
I'm using TWRP 2.6 and no charging problems here. Is it a known issue on TWRP's site?
Click to expand...
Click to collapse
There is something with TWRP 2.6 that triggers it, maybe restoring a nandroid that was made with 2.6 did it. I don't know, all I know is 2.5 fixed all my issues.
---------- Post added at 12:18 AM ---------- Previous post was at 12:14 AM ----------
So I called Google warranty to claim it to get it fixed and have the RMA all set up with a shipping label but now that I have it fixed I am not sure what to do, should I go ahead and send it anyway or not. My warranty was going to expire the next day so I caught it just in time. If I send it will it renew my warrenty? Should I send it just in case there is something wrong hardware related? I been fighting with these issues for the last 3 days but now my GNex is like new again. I can sure use some advice.
[/COLOR]So I called Google warranty to claim it to get it fixed and have the RMA all set up with a shipping label but now that I have it fixed I am not sure what to do, should I go ahead and send it anyway or not. My warranty was going to expire the next day so I caught it just in time. If I send it will it renew my warrenty? Should I send it just in case there is something wrong hardware related? I been fighting with these issues for the last 3 days but now my GNex is like new again. I can sure use some advice.[/QUOTE]
Me personally, I'd send it in.
Sent from my Galaxy Nexus using Tapatalk 2
LibertyMonger said:
Just 3 days ago I couldn't get my phone to charge through USB or AC outlet, I thought it was kernel related so tried flashing other kernels and that didn't fix it. I wanted to flash back to stock to see if that fixed it but couldn't cause I wanted to keep a nandroid backup on my PC in case my sdcard got wiped, I tried all day to copy my nandroid to my PC and it would never copy more than 8mb, the small files so I finally thought to change TWRP back to 2.5 and make a new nandroid and BAM it worked and my phone started charging again. Weirder things have happened and the truth is sometimes stranger than fiction! lol
So maybe it was caused from restoring TWRP 2.6 nandroids or something related all I know is this was true in my case. May not happen to everyone but i have seen others with these same issues recently.
---------- Post added at 12:14 AM ---------- Previous post was at 12:08 AM ----------
There is something with TWRP 2.6 that triggers it, maybe restoring a nandroid that was made with 2.6 did it. I don't know, all I know is 2.5 fixed all my issues.
Click to expand...
Click to collapse
In your case may be its true but for me I'm damn sure that's my nexus's charging port is f*cked up
Climate here is killing my phone
The day before yesterday it was turning on and off by itself and made me pullout the battery from mobile
Sent from my Galaxy Nexus using xda premium
seriousia said:
In your case may be its true but for me I'm damn sure that's my nexus's charging port is f*cked up
Climate here is killing my phone
The day before yesterday it was turning on and off by itself and made me pullout the battery from mobile
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I was running LiquidSmooth 2.6 and upgraded to 2.7 while running the A.S.K.P kernel at the time, like I said I thought it was kernel related then tried different kernels and it didn't work so my only other choice was to return to stock, I tried many different charging cables and I started to think it was hardware related until I tried copying my nandroid to my PC and couldn't do it. So then my only choice was to try making a new nandroid with a different recovery and then everything was back to normal. Sorry to hear your issue isn't as easy as this but maybe if someone else has the same issue as me this might help. There seems to be an issue with TWRP 2.6 and nandroids.
I am running CM 10.1 and the most recent franco build for 4.2.2 . I charged it last night all night while off and the battery went from 11% to wont even boot. So charging says it is working but is not.
stringcheese166 said:
I am running CM 10.1 and the most recent franco build for 4.2.2 . I charged it last night all night while off and the battery went from 11% to wont even boot. So charging says it is working but is not.
Click to expand...
Click to collapse
change battery......
stringcheese166 said:
This started last night. My galaxy nexus is around a year and a half old. Last night the phone started not charging with any wall plug including connecting to to multiple ac and computer outlets with multiple cables. I have used a new battery too and it is not working. I tried updating my kernel and that wont work. I moved the usb pin up and still nothing. My only solace is that it will charge while turned off. But VERRRRYYYY slowly. Thanks for your help.
Edit: The battery when off does not actually charge but the charging screen gets shown
Click to expand...
Click to collapse
Actually when I had my issue with charging, the same thing occurred, I could only charge when phone was turned off. I have 2 batteries with a charging dock for the spare and it was the same with both batteries. But like i said my phone is back to normal. Does anyone know if I send it back for warranty repair will it extend me a new warranty? Also since my phone is fine now, if i send it what will be their reaction if they see nothing wrong with it? Sorry don't mean to hijack your thread but you are describing the same issues I had. I hope you have the luck I had.
Related
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Any takers? If it is a hardware issue i want to fix it ASAP before my warranty is up!
I have it too, wipe doesn't help. I will try flash a stock rom..
dymex said:
I have it too, wipe doesn't help. I will try flash a stock rom..
Click to expand...
Click to collapse
i've found myself at 99% when it's plugged in and it won't charge anymore. not sure if it's a hardware thing or a rom thing. it's intermittent though... haven't found a fix yet...
Please share what you find out after you revert back!
Sent from my Galaxy Nexus using XDA
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
tokuzumi said:
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
Click to expand...
Click to collapse
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Hydera5 said:
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I've seen a similar issue where the device will not charge while connected to power. A reboot will resolve the issue but, for obvious reasons, this is less than optimal.
Is there any way to identify what application (since this only changed recently) might be causing the issue?
Thanks!
M
Oh come on!! Don't people use the search function anymore!?!? See http://forum.xda-developers.com/showthread.php?t=1676711 or the other 20-30 threads regarding this issue.
Basically, you need to replace your USB charging board, and Samsung will claim water damage and make you pay for the whole repair...
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Sorry, I'm not targeting you. I'm just not okay with people creating new threads instead of contributing in existing threads regarding the exact same issues.
MJMcMahon said:
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Click to expand...
Click to collapse
Problem solved (sorta) i called customer care and they said that it was a "common problem" and usually was a result of using a charger other than the one that came with the phone... Long story short they are sending me a new one, new post here if you are still in the helping mood (;
http://forum.xda-developers.com/showthread.php?p=26729008#post26729008
This issue just started happening on my Galaxy Nexus last week. I just called Verizon and explained what was going. I told the rep I hard reset the phone and it still occurs. He said it was a known issue and overnight ed a replacement. If you're having this issue Verizon seems very aware of it.
I had the same issue .... for me it went away with the newer CM builds [VZW].
Hydera5 said:
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Click to expand...
Click to collapse
Mine just started doing this yesterday. Tried a couple of battery pulls but it still seems to think it's constantly charging. When it starts flopping back and forth between charging and discharging the phone becomes unusable. I'm just wondering if the battery pull was a permanent fix for you or did you have to send it in eventually?
So I bought my Nexus on Craigslist about a month ago. Everything went smooth, but i noticed the phone would frequently think it was charging when not plugged in or not charging when plugged in. This was because the previous owner did not use the charger that came with it and presumably bent the Micro USB connection. Nothing my trusty razor couldn't fix, just bent that dude back int place. Worked like a charm. I knew i should replace the USB port... eventually.
A few nights ago, I noticed that while I was plugged in charging, my battery was draining even though the little battery lightning bolt was showing. I figured it just needed to be bent again. Didn't fix it. I must've stayed up all night trying to fix it, flashing new ROMs, factory resets, new kernals, plugging it into a computer, new cables, new chargers, new A/C ports... EVERYTHING. I caved and ordered a replacement USB port on eBay which arrived crazy fast. Upon replacing it.... the problem persisted. I've tried more cables, more ports, more ROMs, more kernals, and more resets.
Needless to say, I'm frustrated. Any input...?
EDIT: I'm on CM10 M2 with the stock kernal
Seriously, is this some kind of joke? Every day, a thread like this pops up... if it is legit, search for one of the many other threads with your issue, I passed two scrolling down the page to yours.
Sent from my Galaxy Nexus using xda app-developers app
Did you even read my post? I've spent two days scanning these boards for solutions. I've tried everything.
No, I didn't.
But I'm not making this up, again, I passed the big one on the way down to this one, it's a very common issue, and like I said to the other guy who just posted one of these threads, some say you can straighten out the port in your phone with a fine screwdriver-like instrument, or you need to order a new USb port + board and take your GalNex apart... Otherwise, with no warranty, I'd bail and get an entirely new and different phone, because this issue is unacceptable.
Oh... you could try a class-action suit. I also mentioned this to the others, I mean really, there are so many of you with this problem, I'll probably be one of them soon enough, may as well start the legal process now...
Sent from my Galaxy Nexus using xda app-developers app
Yeah I did all that, straightened the port, replaced the USB flex, and all that. I'm still under warranty, so my fingers are crossed that they can't tell that I was inside it. Otherwise, it's off to getting the charger that charges the batteries with a dock.
I had similar issue with my rooted GNex while I was running one the ROMs. I also search everywhere on this forum and Google but i couldn't find a solution. So I tried following steps and it worked for me.
1. Using twrp I reset battery stats
2. I wiped calvik cache and system
3. Instead of a flashing a newer zip I restored one of the Nandroid backups of the system.
After reboot I tested if my phone was behaving normal and certainly it was and I haven't had same problem since.
I don't know if there is a way but may be you can go through my post and I had mentioned same issue on this forum and didn't get a response from no one.
Sent from my Galaxy Nexus using xda app-developers app
I did restore to an earlier ROM, maybe I'll try some of my other backups. If that fails, I think I'll give unrooting, relocking and going to he stock ROM and give that a shot. It's a really frustrating endeavor, I've got to say. I will post an update after trying even more methods.
Just don't settle for battery docking, fight for that warranty. Although don't tell them you took it apart.
Sent from my Galaxy Nexus using xda app-developers app
Alright, so going back to stock, unrooting, relocking, and all that didn't fix the problem. I managed to squeeze a service ticket for my Samsung warranty. I'll be shipping it off later today, hoping they fix the issue free of charge. I hope they don't notice I swapped the USB flex, I don't want to end up paying money for repairs.
I'll post back here if I ever get any relevant info about the issue from Samsung. Thanks for the input, folks!
So I updated my phone from CM10.1.0 to CM10.1.2 today. I used the updating feature found in settings.
Everything seemed to go well, the rom updated, phone rebooted, and 140 or so apps updated. Got to home screen and everything works fine. About 5 mins later the phone shuts down. I turn my phone on again, 1 app updates, and I get the home screen. I checked my email and such and put my phone in my pocket. About 5 mins later I notice my phone has turned off again, cept this time now it won't come back on :/
I've searched google and some people point to the battery being the culprit.
http://www.sebertech.com/2013/03/sam...-problems.html Issue #16
and
http://forums.androidcentral.com/spr...turn-help.html
Both say to remove battery, plug the phone in, watch for the charging light to come on, then reinsert the battery. This doesnt work either.
If I take my battery out and plug in the charger, the charging light does come on. If I hold the power button down in this state after a few seconds the light will turn off until I release the power button. With the light on and after reinserting the battery the light goes back out after a few seconds. I just went and got a new battery, but thats not working either :/ I havent been able to boot into recovery mode or download mode.
If the update bricked my phone would it turn on and work just fine before dying? I used a data connection just fine after the update.
Any help with this issue would be greatly appreciated.
0.e pages not found, derp.
The rom shouldn't be an issue at all because CMTeam... Why would they do such a thing.
When you updated from 1.0 to 1.2 did you:
Wipe Dalvik Cache and Cache before you updated.
reset permissions via Custom Recovery after update?
I saw a few people with S3's that went through exactly the same problem but it turns out the phone's main-board was fried because of a corrupted NAND right after a flash.
If there's no haptic feedback or led when you try to turn on the phone ( With a battery ), it's a possible brick but its not super-bricked.
If you put a usb / charger on the phone with no battery in it and it indicates a red LED. There is a possible 50/50 you can restore it but
it'll cost around some 40-60 bucks for having it JTAGGED.
If there is no LED when the phone's plugged to a charger wall port / USB via computer with no battery.
It is completely dead and you'd wanna send that in to get a brand new phone.
It just looks like you need it JTAG Repaired.
Hopefully others would have a better and possible way of finding what happened. Because mines would be a last resort
type of thing and its the only thing I know when the SIII Bricks after completely doing a clean flash or if the phone ends up dying
for no reason after a flash.
Spark91 said:
The rom shouldn't be an issue at all because CMTeam... Why would they do such a thing.
When you updated from 1.0 to 1.2 did you:
Wipe Dalvik Cache and Cache before you updated.
reset permissions via Custom Recovery after update?
Click to expand...
Click to collapse
I used the method provided by CM found in settings -> phone info, like I have many many many times. I dont remember the full process, but I dont think those options are provided in that method, just download the rom then click update.
red300zx99 said:
I used the method provided by CM found in settings -> phone info, like I have many many many times. I dont remember the full process, but I dont think those options are provided in that method, just download the rom then click update.
Click to expand...
Click to collapse
You claim it booted up after the flash and everything worked, so it can't be that you flashed a cm rom for a different device. It doesn't even attempt the boot splash?
Have you tried putting the battery in and plugging the charger for several hours? Could just be a bad usb port and or bad charger cable and your device simply is out of power. Find a different cable or charger all together and try see if anyone has a similar phone that you can try their battery in your phone.
Sent from the future via Tapatalk 4
edfunkycold said:
You claim it booted up after the flash and everything worked, so it can't be that you flashed a cm rom for a different device. It doesn't even attempt the boot splash?
Have you tried putting the battery in and plugging the charger for several hours? Could just be a bad usb port and or bad charger cable and your device simply is out of power. Find a different cable or charger all together and try see if anyone has a similar phone that you can try their battery in your phone.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Yeh, the fact that it started fine twice is what is baffling me. Though it did turn itself off after a few mins both times.
Yeh, I plugged the charger in overnight last night just in case. I took it to the sprint store where the guy took out my battery and tested it, he said it was bad and that was the issue. As of now I've tried 4 different batteries. My own, a new one I bought and fully charged and 2 borrowed from people at work.
That's really weird.... And none of the led come on at all? Really weird, it's not a brick issue because it would give some symptoms but it's like it's not getting power at all. It could just be a major hardware failure. The power button is defective on the S3 but it usually makes an attempt to turn on.
Sent from the future via Tapatalk 4
edfunkycold said:
That's really weird.... And none of the led come on at all? Really weird, it's not a brick issue because it would give some symptoms but it's like it's not getting power at all. It could just be a major hardware failure. The power button is defective on the S3 but it usually makes an attempt to turn on.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
If I take my battery out and plug in the charger, the charging light does come on. If I hold the power button down in this state after a few seconds the light will turn off until I release the power button. With the light on and after reinserting the battery the light goes back out after a few seconds.
It really sounds like it flashed an International rom from those symptoms. But you said it turned on after the flash.
Sent from the future via Tapatalk 4
edfunkycold said:
It really sounds like it flashed an International rom from those symptoms. But you said it turned on after the flash.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
It flashed whatever rom was downloaded from the phone info screen. But yeh, it booted up, updated apps, and made it to the home screen after the update.
Sorry wish I could be more insightful, but I think your going to have to take it in to Sprint
Sent from the future via Tapatalk 4
edfunkycold said:
Sorry wish I could be more insightful, but I think your going to have to take it in to Sprint
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
NP, thanks for trying to help though.
Could it be that CM might have messed somthing up? I would ask them for help or tell them to look in to things.
Sent from my Phone
sprkat85 said:
Could it be that CM might have messed somthing up? I would ask them for help or tell them to look in to things.
Sent from my Phone
Click to expand...
Click to collapse
I've posted in the CM10.1 thread, I'm not sure if Ive heard anything from anyone on the CM team though. I guess it's possible they messed something up, but I havent seen anyone else with this issue and CM, so I'm guessing the issue is on my end.
I would let the phone sit on the charger and try to boot into recovery and try to flash a tw rom. If you haven't tried that already its worth a shot.
Sent from my Phone
red300zx99 said:
NP, thanks for trying to help though.
Click to expand...
Click to collapse
When you connect phone to a computer what does it recognize he device as?
Sent from the future via Tapatalk 4
edfunkycold said:
when you connect phone to a computer what does it recognize he device as?
sent from the future via tapatalk 4
Click to expand...
Click to collapse
qhsusb_dload
sprkat85 said:
I would let the phone sit on the charger and try to boot into recovery and try to flash a tw rom. If you haven't tried that already its worth a shot.
Sent from my Phone
Click to expand...
Click to collapse
It's doesn't power up at all regardless of how long it charges, he tried different batteries and bought a new one also. How would he be able to flash or even get into recovery if it doesn't power on?
Sent from the future via Tapatalk 4
---------- Post added at 08:15 PM ---------- Previous post was at 08:12 PM ----------
red300zx99 said:
qhsusb_dload
Click to expand...
Click to collapse
Oh yeah forget it. It's not a power issue it's bricked. That's exactly what they say when they are bricked by flashing international roms. Jtag is your only option.
Try this can't hurt, this guy claims he revived a phone which was hard bricked. The method has not been confirmed but you have nothing to loose http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
edfunkycold said:
It's doesn't power up at all regardless of how long it charges, he tried different batteries and bought a new one also. How would he be able to flash or even get into recovery if it doesn't power on?
Sent from the future via Tapatalk 4
---------- Post added at 08:15 PM ---------- Previous post was at 08:12 PM ----------
Oh yeah forget it. It's not a power issue it's bricked. That's exactly what they say when they are bricked by flashing international roms. Jtag is your only option.
Try this can't hurt, this guy claims he revived a phone which was hard bricked. The method has not been confirmed but you have nothing to loose http://forum.xda-developers.com/showthread.php?p=43305728
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Sweet, will def try and report back on the results. TY
Have you tried my method of unbricking a hard brick without JTAG? The link is on my signature.
Sent from my SPH-L710 using xda app-developers app
Hello people,
I got a GT-i9300 for about 7 months now and since yesterday i got problems charging it.
2 days ago i went to sleep and as always putted it on charge and i saw the charging notification. When i woke up ~8h later the phone was not charged at all and while connected it was not charging.
I tried reconnecting it a couple of times but nothing. I tried connecting it to a pc but nothing. Then i used the charger that came with S4 and after a couple of seconds it started charging, few minutes later it just stopped again. Reconnected it and it was charging, made it to 100% normally.
Today i tried connecting it again but now it won't charge, likewise i won't connect to pc the moment i connect it but after ~5m at least and it's only charging, the pc won't see the phone anywhere.
Also tried another S3 charger but nothing.
I only have official samsung chargers. 2 x s3 and a s4 one. None works on it at the moment while they work normally on my s4.
I tried it turning it off and removing battery but nothing, did a full wipe but still nothing.
The usb itself looks alright plus yesterday when i was charging it i moved the wire around a bit to check if it was the connection but it was not.
I was looking around the web but found nothing and the similar threads here ain't the same as my case.
Also the phone is on official firmware and not rooted.
Does anyone know anything about it ? I will most likely take it to service tomorrow but since i need the phone i would prefer not to have a ~5 days delay from them.
I have the same problem and the only thing that will charge it is a higher voltage playbook charger. I'm not too sure what the problem is but if you do get it serviced could you please post the cause of this issue?
BCSC said:
I have the same problem and the only thing that will charge it is a higher voltage playbook charger. I'm not too sure what the problem is but if you do get it serviced could you please post the cause of this issue?
Click to expand...
Click to collapse
Sadly i don't have a higher voltage charger plus i don't think it's a good idea to use that, at least not all the time.
Will take it for service tomorrow unless i solve it somehow. Will report back with what they will tell me.
I had previously flashed official 4.2 on my s3 but i reverted to the carrier official version, about 2 months ago. Any chance i will have problems with warranty with the flash count being 3 ?
I read that you normally don't have a problem but i want to know if someone had first hand experience with that.
Esteriol said:
I had previously flashed official 4.2 on my s3 but i reverted to the carrier official version, about 2 months ago. Any chance i will have problems with warranty with the flash count being 3 ?
I read that you normally don't have a problem but i want to know if someone had first hand experience with that.
Click to expand...
Click to collapse
This can very well be a problem. Your best option is to root and reset flash counter with triangle away. After reset, re install original firmware with Odin. If they do warranty fix it, it will be by replacing the motherboard, so if there is anything you need off of it, be sure to back it up on a computer. Also, flashing original with Odin can wipe the device so back up before then. If they look and see a custom flash counter of 3, your warranty will be void.
Alright, took it to service yesterday ( official samsung service ) and got it today. They changed the usb port and all is good, warranty had it covered.
I didn't reset counter before giving it but they either didn't check the counter or checked it and it was not an issue.
Have the initial release of the Tab 3 8.0 from last July. I run rooted stock firmware. About 3 months ago I started having issues with the battery - it would not charge past 60-70% most of the time. Yes, I am using the 2A standard charger that came with it and have tried several others and other outlets. The problem occurs most but not all of the time; occasionally I'm able to get it to charge fully.
I've tried reverting to factory settings (ie stock and non rooted and standard recovery)
Reflashing the ROM and carefully managing the first two charge cycles (up to 100, down to 15, up to 100, then normal)
Two online tickets submitted to Samsung have provided the above "helpful" suggestions which I had already tried and told them that I tried.
Installed battery monitor widget and a screenshot is attached (couldn't figure out how, if possible, to export the history) but you can see the salient points. Plugged it in at 15% at about 1015 PM, happily charging until 10:57 PM when it inexplicably stops at 63%...to resume charging at 8:12 AM and it had almost full 99% at about 9:15 when I opened it to use. (I did not touch it during the charge time).
I also installed the Galaxy charging current app/widget. I'm not 100% certain it supports the Tab 3, but the reference current swings wildly - 800mA is the most I've seen with lows of around 160mA.
Is this a hardware or a firmware problem?
How can I narrow it down?
How can I get Samsung to actually listen to me and do a warranty repair before it runs out?
Advice? Thoughts? Exorcisms?
I called Samsung today and expected a battle, but got them to agree to let me send it in for service. Hopefully they will do more than just reflash it.
tthoma said:
I called Samsung today and expected a battle, but got them to agree to let me send it in for service. Hopefully they will do more than just reflash it.
Click to expand...
Click to collapse
interesting. I have the no charging issue. It will charged after I reboot. wonder If I should call samsung to see if they service it. I haven't rooted that one yet.
tthoma said:
I called Samsung today and expected a battle, but got them to agree to let me send it in for service. Hopefully they will do more than just reflash it.
Click to expand...
Click to collapse
Any update on your situation? I'm interested to hear what happened or is happening?
Sent from my SM-T310 using XDA Premium HD app
You have good timing. I just received it back today. They replaced the internal USB connector, see attached for the replaced parts. Can't comment on the charging performance yet but I'm pleased to see they at least replaced HW.
tthoma said:
You have good timing. I just received it back today. They replaced the internal USB connector, see attached for the replaced parts. Can't comment on the charging performance yet but I'm pleased to see they at least replaced HW.
Click to expand...
Click to collapse
how long did it take? from the time you shipped to the time you got it back?
Sent it 4/2 and got it back 4/15, so just under 2 weeks (NC to TX and back for what it's worth)
Sent from my SM-T310 using Tapatalk
The USB is a common problem with these tablets, luckily I haven't had that issue. I had pretty severe battery drainage issues when I first got my T217s in December, but greenify helped significantly. I hibernated a lot of bloatware I was hesitant to remove. If you are confident with messing with your system apps, there are quite a few you can remove safely. I will try and find the guide of system apps that are safe to remove, but use at your own risk. Also, Xposed is amazing. If you have it, you should get the Samsung DVFS Disabler module, it did wonders for me.
Sent from my SM-T217S using xda app-developers app
---------- Post added at 01:54 AM ---------- Previous post was at 01:45 AM ----------
http://forum.xda-developers.com/showthread.php?t=2258952
http://techspooler.com/guides/remove-bloatware-apps/1868
These aren't exactly specific for the Tab 3, but it is most of Samsung's bloatware and whether safe to remove or not. I hope I helped ya out! If battery drainage isn't an issue it is still fun to mess with your device and try different things, but remember to always make a backup!
Sent from my SM-T217S using xda app-developers app
tthoma said:
Sent it 4/2 and got it back 4/15, so just under 2 weeks (NC to TX and back for what it's worth)
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Just got off the phone with samsung. The lady didn't want to hear it till the end. She kept insisting its normal for the tablet not to charge while on and running apps. (WTF). I had to get a bit loud with her. I told what's the point. Then she said I should just charge by tablet while its off.. lol.. ok... she finally gave the ok to send it in. I'm going to get a video of this so they can see I'm not BS. I even told her it doesn't recognized when I connect to the computer.
edit: my just jumped from 49% to 100%.. sending it back. might as well.