Desire Freezes when plugged in - Desire General

I have a Telstra Desire. Had it a few weeks now, been fine.
Last few days it has started freezing when plugged into the USB on my laptop.
When it happens it totally freezes. When I unplug it the charge light stays on and everything is totally frozen. Only way to get it back is a battery pull.
It seems random and can happen within a minute or hours of plugging in.
Has done it in charge only and also hard disk mode. I have tried rooting and installing a new ROM (latest T-Mod) and it still does it. I'm using the SD card supplied.
Happens with no extra apps installed.
Anyone else had this problem ? any ideas ?

Bumping This as i also have a telstra desire and this issue has started to occur.

It was happening with mine but I figured out that it was because I was using an aftermarket charger. Once I switched back the original one I no longer had the issue

Related

[Q] Touch screen not working

Anybody know what would cause the touchscreen to stop operating when the phone is plugged in? It happens when plugged into the wall charger and the computer.
Thanks in advance,
Stew
Maybe it's improper grounding?
That was causing it to not work right when it wasn't held in people's hands...
I guess it must have been ROM related, was on CM6 switched back to Baked Snack and don't have the issue. Weird.
This happened to me today at work. Was in my hand and it started out just jittery and slowly completely stuck. I unplugged and turned it off and on and it started working again. I just rooted with the new 2.2 method

Phone keeps crashing

When charging, my phone works fine, but when I unplug it, it crashes within a few seconds. If I turn it on without pluging it in first, it boots, and a few seconds after fully booting, it shuts off.
Phone is rooted and I'm using the IceColdSandwich ROM, always on the newest test build.
Help me please, this is really annoying
Sent from my Microwave using Tapatalk
Help, please.
Sent from my Microwave using Tapatalk
I have a similar problem - but its imho ROM independent. I left my phone in direct sun for about 30 minutes and the phone was afterwards wery hot and it crashed...
No I can run the phone only, when the charger is plugged in. Without charger attached the phone shut down in 5 - 20 seconds. I think, the extreme temperature demaged the battery. Unfortunetaly Im in Mexico right now and Im unable to buy another battery, to verify my hypothesis.
Its very likely battery related, bacause after every higher energy drain - flash light or similar it crashes even on charger...
Any ideas - suggestions or similar problem? Thx.
check for battery pins bent if they are ok try changing the rom like cyanogen as they are very stable if issue still there replace ur battery with a new one.
had the same...
i had the same problem and when I tried Ascension ICS, never had crashing issue since lastweek....but....it is starting to act weird this morning...not good
XoXFaby said:
When charging, my phone works fine, but when I unplug it, it crashes within a few seconds. If I turn it on without pluging it in first, it boots, and a few seconds after fully booting, it shuts off.
Phone is rooted and I'm using the IceColdSandwich ROM, always on the newest test build.
Help me please, this is really annoying
Sent from my Microwave using Tapatalk
Click to expand...
Click to collapse
Check the health of your battery. There are battery monitoring apps on the market that can do this.
Do you charge using a wall charger or USB port on your PC? The phone cannot run by itself using wall power or USB power and needs the battery to function.
I have a feeling it's the ROM. Can you try a ROM based off an official RUU? Or maybe revert to a stock ROM? Or you could full-wipe your phone and reflash Ice Cold Sandwich.
Hi guys, thx for replies.
In my case its 99% not ROM related - yesterday I tried around 5 custom ROMs (gingerbread and ICS), flashed another recomended radio and RIL and finaly reverted to stock... still the same problem - reboot after several seconds or minutes...
Unfortunetaly Im unable to replace the battery, to see if its battery-related or not.
Regard Pylorus
Problem Solved
After returning back home, I replaced the battery with a new one and the phone works flawlessly again... so voila, problem solved
pylorus said:
After returning back home, I replaced the battery with a new one and the phone works flawlessly again... so voila, problem solved
Click to expand...
Click to collapse
same here ^^

Note 2 Rogers Canada acting very very strange

Hey Guys,
So i've done some research all evening here and I've done nothing different than i'd do any other day with the phone and all of a sudden today around 6 PM eastern the phone started acting up. I came home from work plugged it in and it started to lag and then froze, finally unfroze and got that error " Unfortunately, %1$S %2$S has stopped running. I only have the option to click (ok) So I would do that and I thought all was well, turns out this is not the case. When this error pops up it also disables the phone from charging. I unplug and plug back in, the phone starts to freeze and the error comes back. I've been doing some online re-search some people say it's a synch issue with google and to turn synch of, did so, still same error. Some people have said unplug charger, power off phone wait 10 seconds, plug charger back on and boot up, this also did not resolve my issue. I will say that if the power cable is not in the device, it works fine. After about 2 hours of trying different things, I plugged it back into the charger and the phone started acting out really strange, changing from screen to screen and indicating " The dock is connected" I don't own a dock and the phone has never been into dock. I'm using the stock charger that came with the Note 2.
I will say I have TWRP installed and I've been using the JEDI X Rom for this phone without any problems. I thought, okay well none of this is working maybe it's the rom acting up, so I decided to go into recovery wipe all cache & system and re-installed the rom, same thing. The dock is connected, phone freezing and Unfortunately, %1$S %2$S has stopped running. So, I re-did everything again, wiped all cache systems, fixed permission and put the stock rom back on the phone. Now the phone is indicating in stock mode that the "dock is connected" when really it's just the charger. The phone is going into the time out then pops back on automatically all by it's self. Not getting the Unfortunately, %1$S %2$S has stopped running anymore though. the phone is 3 weeks old, and i'm at a loss here as to what I should do next.
Any suggestions, if not, Is there away to erase the phone "call" time so I can get it down to below 30 minutes so I can return this one for a new one?
Thanks,
Well, after hours of reading, I came across this post for an Android EVO phone and it mentioned something about a connect point of the charging port in the phone and said slightly bend the charger cable when it's attached inside, I tried this at a last cause and everything fixed itself, I re-flashed Jedi X and all errors have cleared itself. I find it strange because I'm very gentle with inserting/disconnecting these cables...
Thanks,
I'm not surprised. I've had similar issues with a S2 and other Sammy phones. In fact my brothers Galaxy S as well. He had to get the whole board replaced. I hate MicroUsb. Although its nice to have a generic sync port that is the same across almost all Android devices, this port needs to change.
Just my $0.02. Glad to see you figured it out. Knock on wood my Note2 hasent had these issues yet.
Sent from my SGH-I317 using xda app-developers app

Phone Turning off by itself.

So I have this weird issue with my HTC ONE M7 for a few days now. It would turn off by its own when I was using it but I'd just turn it on and it will work again. I thought it may have something to do with a bad app or the rom might be acting up. Anyway I ignored it since turning it on was a minor inconvenience and I needed my phone functional. Today whilst using GPS, the phone suddenly went dead on me. Every time I boot it up, it passes the initial HTC screen but then doesn't boot into android. The screen goes black and the phone turns off by itself. I went it recovery, wiped dalvik and cache thinking it was an app causing a boot issue but that didn't help. The problem continued. I already had a backup so I went ahead and tried restoring it. It worked the first time. But the phone still won't boot. It would turn off automatically. Then I tried reflashing it with the backup. This time the phone would just turn off as soon as the restore process started. I finally got tired of it and decided to reflash with a new rom. The flash went fine. But lo and behold the same issue again. Boot animation and then black screen with the phone completely turned off.
I thought it might be the battery so I plugged it in to my laptop USB. It booted but when i was setting up android, it would just shut down again. Then I connected it to the wall socket thinking the phone will get more juice. This time around I was able to set it up. With the phone connected to the wall socket all was working splendidly. Please note that during all this time the phone was at 100% and there were no drastic falls in the battery levels.
As soon as I disconnect the phone from power, any power intensive operation shuts it down. I have been in recovery mode for 2 hours now and the battery hasn't even dropped by 3%.
So the question is, What the hell is going on? Is it the battery, is it phone's hardware or is it a software issue? Any help would be greatly appreciated. Cuz if it's something that can't be fixed, I have to start thinking about getting a new phone then. THANKS so much for bearing with me! Cheers!!
supratentorial said:
So I have this weird issue with my HTC ONE M7 for a few days now. It would turn off by its own when I was using it but I'd just turn it on and it will work again. I thought it may have something to do with a bad app or the rom might be acting up. Anyway I ignored it since turning it on was a minor inconvenience and I needed my phone functional. Today whilst using GPS, the phone suddenly went dead on me. Every time I boot it up, it passes the initial HTC screen but then doesn't boot into android. The screen goes black and the phone turns off by itself. I went it recovery, wiped dalvik and cache thinking it was an app causing a boot issue but that didn't help. The problem continued. I already had a backup so I went ahead and tried restoring it. It worked the first time. But the phone still won't boot. It would turn off automatically. Then I tried reflashing it with the backup. This time the phone would just turn off as soon as the restore process started. I finally got tired of it and decided to reflash with a new rom. The flash went fine. But lo and behold the same issue again. Boot animation and then black screen with the phone completely turned off.
I thought it might be the battery so I plugged it in to my laptop USB. It booted but when i was setting up android, it would just shut down again. Then I connected it to the wall socket thinking the phone will get more juice. This time around I was able to set it up. With the phone connected to the wall socket all was working splendidly. Please note that during all this time the phone was at 100% and there were no drastic falls in the battery levels.
As soon as I disconnect the phone from power, any power intensive operation shuts it down. I have been in recovery mode for 2 hours now and the battery hasn't even dropped by 3%.
So the question is, What the hell is going on? Is it the battery, is it phone's hardware or is it a software issue? Any help would be greatly appreciated. Cuz if it's something that can't be fixed, I have to start thinking about getting a new phone then. THANKS so much for bearing with me! Cheers!!
Click to expand...
Click to collapse
if you are s-off i would suggest doing an RUU and starting fresh. Its hard to pin point a problem without having the device handy and trying some things. The RUU will let us know if its a software problem or if its going to be hardware related.
Hey thank you so much for replying. I am s-off. But would going back to stock re S-On my phone? And how do I do RUU? Thanks again.
supratentorial said:
Hey thank you so much for replying. I am s-off. But would going back to stock re S-On my phone? And how do I do RUU? Thanks again.
Click to expand...
Click to collapse
Do not s-on! Just run the ruu eye dottat made
Installed RUU. The problem is still there. The phone can stay on for hours in recovery without a charger but as soon i want too boot into android it shuts down. It only boots up if it's connected to a charger and that too a wall socket not a usb hub cuz it goes some way into the boot process and shuts down half way. I am pulling my hair out here. Dunno if it's the battery or the mother board.
supratentorial said:
Installed RUU. The problem is still there. The phone can stay on for hours in recovery without a charger but as soon i want too boot into android it shuts down. It only boots up if it's connected to a charger and that too a wall socket not a usb hub cuz it goes some way into the boot process and shuts down half way. I am pulling my hair out here. Dunno if it's the battery or the mother board.
Click to expand...
Click to collapse
If ruu still has issues. It is motherboard or battery. From the symptoms, it sounds like battery as the phone needs to have some juice to fully boot the phone before being able to run off the charger.

The phone stops charging when it starts to quick charge.

Yesterday I installed a 8.1 rom to my phone and it started to fail charging after 2 or 3 seconds when I plug it. I realized that it happens when the quick charge starts but it gets back to normal if I restart the phone while plugged in. I tried to install another rom but didnt solve the problem so I am looking for a solution.
Which rom do you using? Try some different kernel like birigio's BG345. Maybe it'll help.
The problem first occured on ToxycOS and then I've switched to AOSP extended, it still didnt work. I've also tried the BG345 kernel and it also didnt help
i experienced the same thing but in my case it was my cable was broken. I buy a new one and everything is good now

Categories

Resources