Related
Hi guys. Today when I was trying to charge my GS2, there was popup said 'battery disconnected'. I've tried to take out the battery for a few minutes, but the problem has not been solved. I am running checkromv4 and siyah kernel right now, just updated to siyah 2.6.12 last night. Can anyone help me? BTW, I am using the stock battery.
Are you able to charge it ? If you are (even tho this probably won't make a difference, but it might), charge it to 100% & delete battery stats in RedPill Recovery.
If this doesn't work (probable), try an earlier build of Siyah. If that doesn't help, go back to stock firmware & see if you can reproduce the problem. If you have no problems with stock, then it would obviously be a problem with that build of Siyah or your rom.
If you still have the problem running stock firmware, it would probably indicate a problem with the battery or something else hardware related. Perhaps try another battery. Failing that, back to Samsung/your telco for repair.
just take out the battery again this afternoon for ten minutes, and the problem seems like sloved so far. I can charge now, but have to take a try tonight. Thanks for your help.
Sent from my GT-I9100 using XDA App
This is an old thread, but I recently had this same problem with my Galaxy Note i717. After worrying about it for awhile and searching to find this thread, I took my battery out and examined it, and of the three terminals, the middle one had a piece of plastic broken off of the battery, covering the terminal. So the phone was getting power, but apparently couldn't communicate with the battery, and so for its own safety, wouldn't let me charge
Hopefully this helps someone else!
-Tom
EDIT: Also I tried charging to 100%, and clearing the stats etc, to no avail.
battery disconnected simple fix
pull out the battery take a 12v battery of your car or UPS touch the terminals -+ to your phone's -+ as - to - and +to+ remember just two or three times kisses only . now put battery back in phone Done....
First....why revive a thread that no one has visited in over 3 years.....
And second.......seriously? Connect a high capacity 12 volt source directly across the phones battery terminals?
To whoever reads this.....
DON'T EVER ATTEMPT TO DO THIS.....
It is EXTREMELY DANGEROUS and incredibly stupid to even *think* of doing it. It WILL destroy your device and it will likely cause you to suffer burns and possibly start a fire.....
http://i.imgur.com/rVnFwJM.jpg
I'm hoping someone can shed some light on this problem.
I've been using my X10 Mini running CM7-2.2.0 for internet access (both USB tethered and Wi-Fi hotspot) for the past couple weeks while traveling. About a week ago I started having problems with the phone randomly shutting off during an internet session (usually preceded by a single vibrate). It's gotten progressively worse. Whereas at first it was only happening after surfing the internet for awhile, now it's at the point where I can power on the phone in airplane mode and use it for awhile, but as soon as I turn on the GSM or 3G radio, the screen simply goes dark and the phone is off.
I suspect it's one of two problems: either there's a power issue, or the phone (particularly the GSM/3G radio) has become defective. To back up the theory that it's a power issue, I've noticed some strange things with the battery and it's reported charge level. Today I left the phone plugged in while off (charging from the USB charger for my Kindle, which outputs 850mAh). After a few hours the screen showed it as being fully charged. Then I turned on the phone and it said the charge was 33% percent. Still, even if it was only 33%, as soon as I turned on the 3G radio, it died.
I've tried charged with 2 different microUSB cables, one supplied with my Amazon Kindle, one from a Nokia phone, so both are quality cables. I don't have the original charger and cable with me to try those, but it seems like I should be able to get a charge between 2 decent cables, 1 wall charger and the USB ports on my Thinkpad laptop.
I did try doing a wipe and factory restore of the MiniCM7 ROM just in case, and also tried reverting to a previous MiniCM7 version just in case that one would be problem free, but it's no different.
I guess there's a 3rd option: could it be an issue with the nAa kernel?
Any help or input is appreciated.
Something similar happened to me when i was on MiniCM7-2.2.0
It's definitely an issue with the ROM, not the kernel.
I went back to stock with xrecovery and did a couple of battery-calibrations (drain the battery, charge it on the wall-charger and do a battery-stat wipe when starting up the phone again)
I still can't get a 100% full charge and when the batterylevel sinks below roughly 30 percent getting and making calls results in the same behaviour as your phone (forced shutdowns), but i have a half-decent batteryperformance again.
I have a strong feeling that MiniCM7-2.2.0 doesn't like usb-charging very much, but i don't have any hard evidence to back that up, but i know some other people have the same sort of issues.
It's definitely not the kernel itself, becaue i'm using it now with a different rom for testing and the battery behaves roughly the same as on stock firmware. If you get your battery back to decent performance (don't think it will ever be completely good again), earlier versions of MiniCM7 don't seem to have this particular issue, so stay away from MiniCM7-2.2.0.
That's about all i could advice you, it seems to be the only rom that displays this particular behaviour.
Great to hear at least someone has had this problem. Have you tried other Gingerbread ROMs, such as GingerDX?
Thanks very much for your input.
Yes, i've tried GingerDX, quite like that one too, and i've tried MiniCM7-2.1.9, which is one version older than the 2.2.0, I'm testing a new one now GIngerZaraki, and none of those seem to have this particular issue.
Did you post in the MiniCM7 thread regarding the issue? Just wondering if I should pos there about this. This seems like a very serious issue if it is to do with the ROM. I just tried restoring MiniCM7 2.1.7 and I'm having the same problem though (although ometimes the phone just shows no signal rather than crashing). I also tried reflashing the kernel, but no luck. Right now I'm thinking stock ROM is my best bet.
It needs some time to get it back up working well, let the battery drain till about 10% and then charge it in one go until 100, that will probably take a short time because your battery won't accept full charge yet. Turn the phone on and reset the battery-stats in recovery, if you boot into the rom you can see the percentage, you can charge it again to 100 and repest the process, it took me about a week.
And i think there are posts about battery-issues in the MiniCM7 thread, but i'm not sure how much work still goes into that, since nAa is busy with MiniCM9 and the new kernel for ICS.
I've restored it back to original 2.1 ROM in factory restored state and thankfully the GSM/3G radios are working again. Only problem now is that Wi-Fi won't turn on, giving me an "unable to start Wi-Fi" error when I try to turn it on. Did this happen for you, SmG, in that first week of battery recovery?
kentchristopher said:
I'm hoping someone can shed some light on this problem.
I've been using my X10 Mini .........Any help or input is appreciated.
Click to expand...
Click to collapse
Well i think you are totally new to using this ROM so this issue is raised i have been using this ROM since the release.
There is no such Issue.
The actual issue that might happen (also happened in your case) is Flashing error, that means Bootloader is cracked, Kernel is flashed and rom is flashed but there was some minor glitch which got skipped and Flashing got successful, so you will have the problem even after factory resetting.
Here is what you should do Download Bootloader, kernel, ROM again. Delete old Files and use new ones to Unlock BootLoader Reflash the MiniCM Kernel and Flash The ROM, then go to recovery Wipe dalvik Cache,Battery Stats and then factory reset via recovery, after doing that everything should work fine.
also Xperia X10 Mini is not made for Tethering so if you use it you might get those problems again, try to avoid it.
if the problem persists install SEUS factory reset your mobile and update it by the SEUS or PC companion even if it says you have latest version, it will make your mobile factory reset.
I've been using CM7 since last year and 2.2.0 since its release. I have tethered before without problem though that was probably 2.1.7 and with less extensive use.
I ca say that the problem persists even though I am now back on stock 2.1 ROM. Wiped system before restore, wiped Dalvik cache, wiped battery stats, restored 2.1 and flashed stock kernel. I guess this means the problem has to be the bootloader?
As for repair with SEUS or PC Companion, I tried both and there is no way to force repair -- at least with CURRENT versions, and the versions I have won't run without an internet connection and you are forced to update. When run, both said I have the most curent version of the software on my phone and no option to repair anyway. I think this is a change from previous versions, but if you don't believe me, please try it yourself. Maybe I need to relock the bootloader?
Thanks for your input.
To follow up on this, the underlying issue seems to have been a my battery. Having just swapped out the original battery for my own self-built replacement, it seems to be working absolutely fine.
My battery life was fine before this issue. My theory right now is that the extensive tethering and internet use I was doing on the CM7 2.2.0 ROM and, most importantly, the heat that it was creating (I remember the phone getting hot) brought about a rather sudden death to my battery (heat being a known killer of battery health).
Download the battery calibration app,charge to max and leave it plugged in. Enter the app and see how many mv the battery is emitting. It should be 4200 at full charge.
Sent from my E10i using xda app-developers app
aloy99 said:
Download the battery calibration app,charge to max and leave it plugged in.
Click to expand...
Click to collapse
I assume you mean that I should do this with the old battery? Not really an option anymore since I clipped its cable to use on my new DIY replacement battery. However, back when trying to solve this problem, I did wipe the battery stats both from Battery Monitor (app) and from CWM recovery (separate occasions) and did full discharge/recharge cycles to calibrate. Obviously it didn't help, and I think it may have actually made the problem worse.
Same problem here, wifi Not working after relocking bootloader on my x10mini.
:crying:
After updating to ICS I cannot charge my phone while it's off.
I always charge the phone during the night and never let it fully die but today I didn't see that the battery level is so low and my phone died now I cannot turn it on to charge it. I get constant reset, my LED flashes blue/red and it resets non stop.
2 nights ago forgot about that problem and woke up at 3 o'clock to find out that my phone has been restarting for about 4 hours.
Give any advice.
P.s. My girl's also with Neo, also updated to 4.0.4, same problem there...
A quick video to show the issue: http://youtu.be/ajwFwEeg0gY
DNDimitrov said:
After updating to ICS I cannot charge my phone while it's off.
I always charge the phone during the night and never let it fully die but today I didn't see that the battery level is so low and my phone died now I cannot turn it on to charge it. I get constant reset, my LED flashes blue/red and it resets non stop.
2 nights ago forgot about that problem and woke up at 3 o'clock to find out that my phone has been restarting for about 4 hours.
Give any advice.
P.s. My girl's also with Neo, also updated to 4.0.4, same problem there...
A quick video to show the issue: http://youtu.be/ajwFwEeg0gY
Click to expand...
Click to collapse
I just found out after reading your post that I have the same problem but I removed some app so don´t know if has anything to do with removed app!
Downgraded to GB and you can charge your phone normally. After be careful to don´t let your phone battery complete drain.
I am trying some roms besides official to see if I found out one that can allow charging in off mode. Is annoying this….
EDIT1: I just made a clean update from GB to ICS without removing any app or installing any different kernel and is charging in off mode.
So this behavior any something to do or with removed app or with different kernel installation!
Have to find out.
EDIT2: No. Is not Kernell issue or Super User that I just flash by CWM. So last option is any removed app or eventually any combination of factors.
Yes, I am in the process of downgrading, good thing is that we have two Neo's so I can use the other one's battery
Dudes! I managed to charge my phone but darn it wasn't easy.
Now one of these is on the way: http://www.ebay.com/itm/190586739151?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649
Are you sure it's a hardware issue, because I've tried 4 different ICS ROMs (Stock ICS, JJDoctor's, KA20 and AOSP 4.0.4) and I've been able to charge my phone while off in all of them.
Maybe getting your phone to a service center will find the culprit.
Akath19 said:
Are you sure it's a hardware issue, because I've tried 4 different ICS ROMs (Stock ICS, JJDoctor's, KA20 and AOSP 4.0.4) and I've been able to charge my phone while off in all of them.
Maybe getting your phone to a service center will find the culprit.
Click to expand...
Click to collapse
Is not a hardware issue.
I also had the same problem but now I don´t!!!
I downgrade to GB and flash ICS again and problem is gone.
Why? Don´t know.
Probably is a combination of things.
I never said anything about hardware issue. At least don't remember it.
After flashing back to GB and upgrading to ICS the problem was gone until I removed all apps that don't use directly from system/vendor/app
Now I cannot charge again but hopefully I won't leave my battery to totally die again.
chargamon file nuff said
Sent from my Xperia neo using xda premium
Chargemon, if I'm not mistaken, is replaced when installing cwm. This means I should be facing this problem as well. Let me check...
Sent from my MT15i using XDA
EDIT: I couldn't replicate the problem. The phone started charging normally when off. A few seconds in the light went from green to red, but I think it recalculated the battery from 90% to 89%, hence the switch. Perhaps this only happens when the battery is fully drained?
If the NT just stopped charging any suggestions?
I know the charger is working because it works on the phone with a different cable. Also the phone adapter won't charge it, nor the pay for minutes things at the airport.
My thought is it is hardware related internal to the nook itself.
Thanks,
Fixed - If you have a similar problem use Mini Info App to toggle charging and see if it helps.
New info - charging Thurber off again. I toggled in Mini Info and had to restart Mini Info to turn charging back on. I have now taken Mini Info off home screen and will not use in case it is the problem. Not uninstalled yet, just off.
Are you using a cable other than the nook specific one?
Sent from my Xoom using Tapatalk 2
Yes. Nook cable is used from two different charging bricks with no charging indicator. Don't get the animated battery and MiniInfo indicate nook is discharging. At about 69% and in case someone has a suggestion I want enough juice to implement, otherwise return to stock. Had the nook since December so I doubt any warranty.
Thanks,
Bill
okay... it does "sound" like you have a hardware issue. the nook's connector is a little bit longer than normal... is it wobbly ? are you getting the 'orange' or 'green' LED glow ?
Not wobbley. Mine has shown green all the time since a week after I got it in December.
I'm wondering if it could be something with the kernel and if going back to stock may work. I doubt anything short a a repair will make it right.
Thanks,
Bill
Charging after Return to Stock
Wonders will never cease! I used the "acclaim" modified zip to return to stock and the tablet started to charge. I'm going to let it get up to 100% then use the SD version of CWM to create a stock backup. I will then try to restore my CM7 internal rom and see if it is still charging.
I'll post results tomorrow.
Thanks,
Bill
Just out of curiosity, what ROM/Kernal were you running when you noticed this charging problem?
NVM...... It says CM7 right there in your post.
Running CM7 the April 24th Build. It was working great for a month or so then just stopped charging. The Nook charges with stock and with the CM9 with the 3xx Kernal. When I restored the CM7 24th version charging was not happening.
I'm going to try the older Team B version tomorrow
miniblue said:
Running CM7 the April 24th Build. It was working great for a month or so then just stopped charging. The Nook charges with stock and with the CM9 with the 3xx Kernal. When I restored the CM7 24th version charging was not happening.
I'm going to try the older Team B version tomorrow
Click to expand...
Click to collapse
why not try the internal beta instead? works for both 8 and 16 GB variants
May do that. Really liked what I was using. Still there is a reason for the charging problem I want to track down.
Waiting for ICS or JB anyway.
Pilot Error
Charging fixed!!!
I have the Mini Info app and it has a button to turn charging off. I must have hit it when checking something.
Funny thing is in all other ROM's when charging is turned on they charge. I have to turn charging off on this version of CM7 for the Nook to charge.
It has been an interesting venture to say the least.
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Are you undervolting/ under clocking this can cause a sod
Hi. Nothing like that, just used neat Rom or disaster Rom as they come.
sent from my Westcrip powered S2
Your phone(battery) has insane gauge chip search for this it answer in your question(it's only for battery)
Happy new year
Paulius
Hi, thanks for the reply. I'm not sure my issue is to do with the guage chip directly, as my phone will switch itself off at any battery level. The issue designed in the other thread its having something like 56% and then having a much lower value after an intended reboot.
Shutdown it's called sleep of death( scary name) but it not death it's just sleeping forever... it problem with your kernel and battery problem is insane gauge chip...
Happy new year
Paulius
I've just charged to full charge, unplugged - and within 2 minutes, the phone froze, could not do anything - so i pressed the power button until it went off, and it booted back up again without me doing anything - when it booted, it showed i had 2% battery. Then it did the same thing, froze, i had to reboot - then it showed 37% battery.........no idea what's going on apart from maybe a faulty battery...
Buy new battery. It was here on the forum a few times.
Yes. When phone hot(sometimes not) it take battery about 50-60%(I don't know exactly) but sometimes it add battery...
If you flash siyah kernel with stweaks(5 version) you can reset it but chip do funny thing even you reset...
Happy new year
Paulius
try Battery caliberation app ...
if it doesnt work buy a new battery
What are you talking about ? It's not battery Fault it's Insane Gauge Chip.... And Battery Calibration not helping...
I decided to go the whole hog and go back to a stock unrooted ICS, after wiping everything, then CFRoot - then reinstalled Neatrom light - currently restoring apps via Titanium - fingers crossed...
I think you don't have anymore BSOD But if you have flash Syiah kernel
Try new kernel and reset fuel gage
Try installing a new kernel like siyah or dorimanx and then reset your battery log this should resolve your problem if not buy a new battery.
karfeef said:
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Click to expand...
Click to collapse
I think I have a very similar issue. The randomly reboots happens several times a day, it does not happen though when charging (never). By now I'm on jb leak and still have the issue. When it shuts down, the sreen dims a bit and then it's gone, the weird thing is that often I have to pull the battery or charge the phone before reboot is possible, the battery shows different values after rebooting, sometimes close to what was before (especially when rebooting on charger), and sometimes way off the values before. I came initially from slimrom with siyah or dorimanx kernel, I really hoped jb leak would help (also tried different kernels), but it didn't. It also seems to me that it happens more often with the sd card (32gb) and without the phone seems more stable, but still it happens from tme to time. Once the screen dim (only one or two steps) and shut down even happend when in CWM recovery, is it maybe hardware related? It's very hard to find the source of the problem, anybody else experience similar issues? By the way the shutdown I have is not a proper shut down, the phone doesn't show the message "is shutting down".
I've completely wiped, used Odin to go back to ics stock, installed cfroot, then installed neatrom light. Had the same issue, so I've installed siyah, and used stweaks to reset the battery fuel gauge. I've only been off charge for 10 mins so far, but normally it would have shut down by now, so here's hoping...
sent from my Westcrip powered S2
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
karfeef said:
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
Click to expand...
Click to collapse
I had the same problem - SOD several times a day. I change the batery with a fresh new samsung 2000 mA one.
Unfortunatelly SOD came back, but I found a trick: turn off WiFi. Use it only manually.
For the past 3 months I succeded to have 0 SOD's.
I know that manual WiFi is a setback but it works with those experiencing SOD.
Hope it will be usefull.