Develop Bugs

[Q] Strange charging problems/MTU data Doesn't work

Ok here's the rundown:
Found out about the fast charging feature of Franco's kernel.
Flashed Winner's build onto my phone.
Flashed Franco's Milestone 2 build
Purchased/played around with multiple fast charge togglers. Decided to just let Tasker do it when the phone went into car mode.
Tasker did a good job of turning on fast charge but was sloppy in turning it off.
Several days later while playing GTA I had to plug it into my computer, fast charge was on. Shortly afterwords my niece and daughter get into a fight and I put my phone down, break up the fight and take my daughter outside to calm her down (She's 14 months) forgetting about the phone.
Phone sits on the computer's USB for about an hour maybe hour and a half.
Come back, it's at about 86% realize fast charge is on and turn it off.
That night the phone won't charge.
Now, here's what I have figured out.
Phone will charge in a powered-off state.
Phone will usually charge after a battery pull.
Phone will not connect to Windows 7 machines or XP machines except to charge when off or after a battery pull. (Device not recognized, latest Samsung drivers installed)
Phone will not connect in recovery mode.
When the phone does not charge it does maintain the current battery level unless I'm using up more battery than it can replenish.
Flashing multiple roms doesn't work.
Re-flashing Franco's kernel doesn't work.
Manually entering fast-charge commands doesn't work.
Oh and when I say it doesn't charge that is on either AC or USB.
I'd send this thing back to Verizon but I can't stock and lock it.

I would guess there are at least 20 threads here with this exact issue.

Yea, sorry about that. I did look around but besides 1 or 2 threads of people doing the usual rom swapping and just going out to get a new phone. I just wanted to start a thread for real diagnostics of this problem.
Oh yea, I also found the phone while plugged in will maintain the charge on the battery but will not actually charge the battery. Next time I'm in the car I'm going to see if the charge script will enable fast charge (Maintain) off of a USB connection.

This is the real thread: http://forum.xda-developers.com/showthread.php?t=1427539

I did read that thread, I don't think that is the same problem I'm having. I actually had that issue before (Shorted contacts) and had my previous Gnex warrantied.
To tell you the truth this will be the last samasung phone I'm ever going to get. Samsung is great on glitz but short on substance. My previous i760 was the same story. Fantastic out of the box but once it was 4 months old it was a royal pile of junk. It's pretty bad when you send the things into warranty enough to where the call center people get to know you by your voice. We currently have 4 of these things in the enterprise I have had to call in on them 6 times already.
Edit: well **** on a stick, it is related. Good I can continue ranting on the absence of the 3 pin dock(s) with more vigor than before. Now off to Ebay to find a replacement charge board.

I know, Samsung has not handled this problem well. I have read threads where they claim water damage on this exact issue, and refuse to fix the problem under warranty. After so many issues with it, they REALLY should have fixed it under warranty.
After having this issue twice, and after replacing my USB charging board twice I know that you have the same issue in the sense that it is the USB charging board that it failing.
You really should star/comment here if you have not: http://code.google.com/p/android/issues/detail?id=23789

[Q] No power, no charging LED, no Fastboot

Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?

none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go

Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.

When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-

musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!

[Q] Phone gives no response, but heats. Fixable?

Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c

Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.

Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?

Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck

Pixel C bricked after first charge

Purchased as a Christmas gift a couple of weeks ago and worked great out of the box. It was put on the charger at the end of the day to charge. Next day come back to the tablet only to find it will not power on.
Tablet gives no indication that is plugged into the original charger. Pressing and holding the power and volume up to try and access the bootloader provided no response.
Calling this one bricked unless anyone else has thoughts or suggestions. Have seen this with other Android devices in the past but where going on 3 years old. This guy is only a couple weeks old. 1 day powered on even.

Can you try a different charger? How much battery was left when you put it on the charger?

Couldn't say what the battery percentage was at, it wasn't dead though. I was given the tablet back to try and troubleshoot and only have as much info as I was given.
As for the charger, this is my one and only USB Type C device and only have the original charger it came with. I was told however that a type c cable was used from a laptop to see if anything worked. No response I am told.
Have a few days to wait until I can RMA it. I will see if I can source another power adapter.

there are many [upwards of 20 or so] reports that it takes between 15 and 20 seconds of holding power button down to power up the device. i have had it happen twice. the largest thread for this issue i have read is on reddit.

I've had it happened to me twice on my first unit and twice on my RMA'd one now. Every time it happened it was after leaving the tablet unattended for several (12+) hours, regardless of battery % (anywhere between 10 and 60%). I never turn it off to make sure I don't get the touchscreen issues again as these come back everytime I reboot the tablet but when this happens there isin't much I can do as it turns off by itself. I can confirm that a very long push of the power button (agree with the 15-20 seconds mentionned above) also does the trick for me. Same pattern on my first unit and my 2nd one.
I'm realllllly hoping Google will have a software fix for all of this (touchscreen issues, awful Wi-Fi download speeds/range on 2.4 Ghz and this (tablet going dead without any apparent reason and being hard to reboot)) as I want to love the tablet but it's a mess right now.

Thanks for the reports.
I held down the power button till my finger went numb. Still don't know if the tablet has a charge and if the charger even works.
Same thing happened with my GPe htc one. Charged, freaked out, rebooted and then bricked never to come back to life.
Would have been nice to have found reports of issues before. Every search brings up reviews however. Hopefully this thread gets indexed.

Don't know if this is related: I've had the tablet for about two weeks and have twice had it not turn on (or respond at all) when I pressed the power button (short press, long press--although possibly not >15s). Even though I thought there was well over 50% battery left and even though though tapping under the cute LEDs showed four greens, I plugged it in and just left it for hours. Then when I came back, everything was fine--it turned on immediately.

I know this is old thread, but though this might help someone: my pixel c won't charge unless I
1) with the device plugged in
2) hold power-vol up-vol dn all at the same time
3) un plug the cable
Can be hard to do with only two hands. "Charging" will pop up on the screen immediately for just a second when you pull the cable if you did it right. I often need to do it more than once. Thanks Google!
support .google. com/pixel/answer/6328598?hl=en (sorry, guess I can't post links)

Fried it good, me thinks (SM-T700, green screen flash, then dead)

After a long day streaming Pandora from my Tab S in my car, running on battery, no charger connected, I decided to put it on a charger and turned on navigation about an hour from my destination as I was in an unfamiliar city. After about 45 minutes, I saw a bright green flash from the screen. A few seconds later, and there were more flashes and it turned off. I have not been able to get it to come back on. I have tried charging it, on a charger and on PC. I have tried every combination of home+vol up/down+power I have seen in several threads, while connected to a PC, to a charger, and not connected at all. The PC does not recognize the Tab at all, ever, during any of the manipulations.
I have seen where some have luck just letting the tab sit for a few days, and it will be miraculously revived by charging, so I will try that. I have also seen where some force charge the battery using the wires from a stripped USB cable directly on the battery terminals, and as my warranty is long past void, I will try that too.
Here's my question: If none of that works, given the description, does anyone have a good idea that it may be just the screen or the battery that may need to be replaced? Or is it more likely a motherboard issue? Is there any way of telling? Despite the heavy use, the TAB did not seem excessively hot. I have felt it much hotter in the past .
I'm a tab-a-holic, and use this thing all day, every day. I use it for work, and for reading and movies at home. I'm a little frustrated as I have yet to own any tablet that lasted two years. I really don't want to spend the money for another one right now, and, if needed would prefer to repair this one if I can save a few bucks.
And, if it's relevant, the Tab is rooted, running AOSP 6.0.

I don't know too much about this - but if I were in this situation, I'd put it in a refrigerator for about 1 minute and try booting it up.
As for the cause - AOSP 6.0 has been known to have some overheating issues on this tablet under heavier loads.

Yeah, still don't think overheating was the cause. Not gonna put it in a fridge either. ;-P

Thanks to all for your concern and helpful comments!
My Tab S is unbricked as of just a few minutes ago! I just let it sit for a few days, and then left it on a charger for a few hours today. I was not expecting anything as the battery icon did not pop up when I plugged it in. But, when I came back to it a few hours later, I pressed the power button and there was the battery icon showing a full charge. It booted up normally with no issues and is working fine.
I can't tell you how happy I am!