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
Related
i'm running a Gingerbread build based off of the latest nightly with stock kernel.
i've formatted my device with the formatall.zip and reloaded the ROM. i've even gone back to a stock ROM and still got the same issue. after doing this, if i plug my device up, it charges just fine while on. if i unplug the device later and plug it back up, the charging light will come on, then quickly go off and the device won't charge.
the only way i've been able to get around this is to turn it off, in which case it then charges. i get these same results whether i'm plugged into the wall or to PC.
if it were a hardware issue, wouldn't that mean it wouldn't charge at all, whether on or off?
anyone have any ideas or experience with this issue?
Same Here...
Anyone found solution yet?
My only guess would be a kernel issue or a hardware problem. Wipe your dalvik and cache and reflash your kernel. If that doesn't fix it, I do know some evo's micro usb ports go bad. I don't know if this is a symptom of that but it may be.
Thanks alot **TheSilverStig **
It was the kernel.
My phone is charging now...
Will test for a couple days and will let you know again..
For some reason www dot qap dotla/~netarchy/ is not working (Error 404)
Try http home(dot)comcast(dot)net/~evoreviews/downloads(dot)html
For now...
For me
netarchy-toastmod-4.3.1-cfs-havs-nosbc worked...
Hope that helps for you too...
Good Luck
*Happy Rooting*
(I don't have 8 posts yet so no links)
HELP evo only charges turned off
I have a problem.. my evo only charges when turned off. sometimes the charging light will come on when it is on but the settings say its discharging.. also i reinstalled a driver once and it started charging fine until i unpluged it from the computer now back to not charging.. this is very frustrating.. it not the port or the cable or the charger.. is there a way to force it to charge with android terminal emulator maybe??
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 ^^
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
I'm using a T-Mobile Samsung Note 2 w/ Gummy Nightlies installed currently
Gummy: M3.0-09-02-14-NIGHTLY-t0ltetmo
The problem I'm running into happens consistently but not at predictable intervals. When the phone powers on, every so often while I'm using the phone, whether it be using the internet, browsing through Instagram or Twitter, or just scrolling through the apps my phone will perform a soft reboot.
I've tried multiple ROMs, stable releases, ROMs that aren't CM11 based, nothing seems to fix this issue.
Can anyone shed some light on what might the problem be and possibly a fix?
I'm not sure what else to include that might help anyone with diagnosing the problem, but if there is something that I forgot, I could definitely get you that information.
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Coug76 said:
Have you noted this issue on TouchWiz Roms or is it happening on AOSP Roms exclusively?
Click to expand...
Click to collapse
It hadn't happened on TouchWiz ROMs, but this just started happening about 2-3 weeks ago. I havent used a TouchWiz ROM in months. I've gone from OmniROM to LiquidSmooth to PacMan, to the most recent Gummy. From what I can remember its happened on the two latter ROMs.
It's strange because, I've called T-Mobile to have them send out a replacement battery, I figured that was the issue. I've had no issues with soft reboots while the phone was plugged into the charger, only when unplugged.
T-Mobile decided to just send me a new phone, so I reflashed to stock and im using my phone to send this message with no issues. So maybe AOSP problems?
What can I do to fix this?
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Coug76 said:
Easy answer is stick with TW. That or try an older AOSP build and see if your issues go away. It may be that a specific commit messed with a setting you are running and issues start. I would do a wipe on the offending rom, avoid restoring data via titanium and see if the issues return.
Click to expand...
Click to collapse
The funniest thing just happened, it did it on the stock Firmware. My best guess would still be the battery. Good thing T-Mo sent the phone via Priority Next Day Air. I'll have it some time tomorrow
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
_lolzack said:
UPDATE: It now constantly just gets stuck in a boot loop when unplugged from the charger, but when plugged into the charger it has not a single issue. I've ordered a battery from Amazon, but I would still love to know what the issue might be. For example, I want to know why the battery isn't working correctly.
Click to expand...
Click to collapse
Did the new battery work?
I've got a similar issue ...
I was running Liquid Smooth 3.2 (4.4.4) with TWRP v2.7.0.1 and up until about a month ago, my 2 OEM batteries worked fine.
I was going to head out for the night, so I swapped to battery #2, it went into a boot-loop.
I thought it was a ROM issue, so I reflashed the ROM and still had the boot-loop, even after charging the battery to 100%
It wasn't until the next morning that I re-installed battery #1 and the phone booted fine.
Every time I swap to battery #2, the phone goes into a boot loop.
I ordered another OEM battery from Amazon and the phone goes into a boot loop as well.
The battery contacts on the back of the phone look fine.
I used the following procedure to delete the battery stats and it didn't help:
http://forum.xda-developers.com/showpost.php?p=38500258&postcount=8
I also switched to the JEDI Open Source Project (4.4.4) ROM and only battery #1 works.
I just removed battery #1 from the phone with it plugged into a charger and it remained powered up. I then installed battery #3 and it worked fine. When I rebooted the phone it went into a boot-loop again.
Hi guys. A relative asked me if i can repair his note 2. I think his network was locked and the phone keeps restarting everytime. I flashed a new firmware on the phone. The one I use on mine..XXUFNG1, and also I went into recovery and clear data and cache after flashing. But still the phone keeps rebooting everytime. Why is that and how can I fix this?
Note : It's not bootloop or anything. You can switch on the phone, use it for like 5mins and then it freezes and restarts itself. And it goes on like that. Sometimes it doesn't restart also and you can use for more. But most of the time after 5mins, it restarts.
naeem86 said:
Hi guys. A relative asked me if i can repair his note 2. I think his network was locked and the phone keeps restarting everytime. I flashed a new firmware on the phone. The one I use on mine..XXUFNG1, and also I went into recovery and clear data and cache after flashing. But still the phone keeps rebooting everytime. Why is that and how can I fix this?
Note : It's not bootloop or anything. You can switch on the phone, use it for like 5mins and then it freezes and restarts itself. And it goes on like that. Sometimes it doesn't restart also and you can use for more. But most of the time after 5mins, it restarts.
Click to expand...
Click to collapse
ROM?kernel?
hishamnoobie said:
ROM?kernel?
Click to expand...
Click to collapse
Everything stock..like I said! Before flashing to the newest rom too, everything was stock.
Was the phone dropped or exposed to moisture? Possible battery problem? Reboots even when connected to a charger?
audit13 said:
Was the phone dropped or exposed to moisture? Possible battery problem? Reboots even when connected to a charger?
Click to expand...
Click to collapse
Hi..thanks for reply. I tried another battery in it. The one I use myself. But it still restarts. I don't know if the phone was dropped or anything though. The relative just told me that it needs to be unlocked. Do you think it's software related? Or something is damaged in the phone?
Since it is running a stock ROM and still behaves this way after a factory reset, I think there is a hardware problem.
I might have a similar problem. I copy from another thread:
Hey guys,
I like this rom so far. But since 2 weeks I got an issue.
My phone randomly turns off, atleast I guess that's what happens. Sometimes the "notify" LED is on permanently but the display won't go on. To start the phone again I have to put out the battery and put it back in.
My battery is randomly empty pretty fast even if I just let the phone turned off. This happens like every 5 minutes.
I already bought a new battery but the problem hasn't changed.
What to do now? :>
Click to expand...
Click to collapse
I like the phone. It's over 5 years old and runs like the first day. Except it DOESN'T wake up anymore after a short time when the screen is off. I can press the power/home button as many times as I want and wait for 5 minutes, screen will still be off. Only way to "wake" it up again is to put the battery out and in again.
Currently I don't have enough money to buy a new phone and I can get a new motherboard for 25$. But I'm not sure if this will fix my problem.
I'm not even sure if this is the ROMs problem since it worked with all earlier versions of this rom perfectly and even the latest release worked for weeks/months.
Click to expand...
Click to collapse
As long as I leave the screen turned on the display/phone won't go off and I can use it as always. Even the battery don't drop drastically then.
It might be exposed to moisture tho. When I take a hot shower I'll leave it on the window sill and the room gets steamy.
ROM: [7.1.2 r24] LineageOS for N7100 [Unofficial] - Version from 08.10.2017
GAPPS: Open Gapps ARM 7.1 Aroma - 03.05.2017
Baseband: N7100XXUFND3
Ril and other stuff I don't know where to check.
Some years ago I had the SDS and the motherboard was changed without the EMMC bug.
Sometimes my phone only charges in slow mode too.
I try a clean install and newer pico gapps now. Maybe it will solve the problem. I'll reply then if it worked or not.
[EDIT]
Since my phone was low on battery I turned it off completly and put it on the charger. After an hour or so I wanted to look after it.
The green charging light stays on and if I want to turn the phone on nothing happens. The light stays on even after removing the charger.
Seems like a hardware, not a rom problem? Will changing the motherboard fix this?
[EDIT 2]
Quick update. I fully wiped/factory resetted and clean installed newest version of this ROM + newest mini pico GApps. Still the same problem. Gonna try it with another ROM/kernel now and if the problem persists it's a hardware fault.
[EDIT 3]
Fully wiped again and changed ROM+Kernel. Still the same problem.