Alright, so i sat down and did my first ROM flash (the clean update based off the DI01), then immediately downloaded ROM manager, and flashed the voodoo v0.2 with stock clock and voltage. Now every time I plug in the USB cable, I get the "battery is not connected" error. I have tried:
turning off phone, unplugging cable, pulling batt. then turning on, then plugging in cable
unplugging cable, pulling batt. while on, putting batt. in, turning on, then plugging in cable
... and every other possible configuration. I have left the battery out for 10 minutes now, and still no luck when I put it in.
suggestions?
EDIT:
waited a while longer, and it randomly worked. mods, feel welcome to delete this thread
It's been known to be related to phone being too hot.
hey..
That's what exactly what happened to me, so i actually flashed back to the stock rom
through the odin and wipe everything and started all over man..
I don't know..
Something is gotta be wrong with Voodoo kernel..
But in this way, i fixed it..
So i think im gonna stick with the lagfix for now..
and i guess when Dev comes out a different fixed verison, i'll take it again..
Good luck man
My phone was running at a fine temp to the touch, and I think the Battstat widget said it was at 30c, which should be fine. I think today i will flash over to a 1.1 or 1.2 Ghz voodoo kernel
Aidman...try this unplug the usb cord and shutdown pull the battery , then replace battery fire it up and charge....
post back results....
Voodoo busted my phone too. I could get the battery disconnected message to go away if I took the battery out and let it sit for a few minutes, but then it would come back later. It's a pain in the ass getting the message every time I try to charge my phone. Went back to stock until a fix can be found. My battery is nowhere near being hot when this happens, and I have only seen the message when using voodoo. I think I'll just wait for a later release. Too buggy for now...
Alright: for those of you who never read the full first post: THE PROBLEM IS SOLVED, thanks for everyone who decided to chip in. I had to try the battery pull about 10 times before it worked
Edit: I feel like an asshole after rereading my own post. I am sincerely sorry for my incredible stupidity.
aidman said:
Alright: for those of you who never read the full first post: THE PROBLEM IS SOLVED, thanks for everyone who decided to chip in. I had to try the battery pull about 10 times before it worked
Click to expand...
Click to collapse
I did read your post and understand the the problem wa solved for you, but not for me. I wanted to include my experience in case others are having the same issue. I was unable to fix the problem.
SnrSuave said:
Voodoo busted my phone too. I could get the battery disconnected message to go away if I took the battery out and let it sit for a few minutes, but then it would come back later. It's a pain in the ass getting the message every time I try to charge my phone. Went back to stock until a fix can be found. My battery is nowhere near being hot when this happens, and I have only seen the message when using voodoo. I think I'll just wait for a later release. Too buggy for now...
Click to expand...
Click to collapse
Not a lot of people get that error. I never did. And it never appeared either.
I had this issue too with the "no battery" indicator, and so did another individual in the lagfix release thread. No our phones were not hot, my own battery was nowhere near being hot, and we tried battery pulls, but that never worked. What worked for me was reflashing the voodoo 0.2 kernel on top of itself, the other guy tried that and had success with that too. You may give that a try, but I must say, that was only a temporary fix because after a while I got that annoying message back again.
I seem to have gotten rid of it for good, backed up all my apps in titanium, re-removed voodoo (be sure to get rid of "remove_lagfix" file when it's no longer needed), did a factory wipe, reflashed the stock Odin Kernel, did another factory wipe for the heck of it, then applied Voodoo, then reinstalled my data + app data using titanium backup (keep in mind I never wiped, restored, or returned system back to stock). Been running for a while, and I have yet to have the "no battery" annoyance and to be honest my phone boots quicker. So up to you, worked for me if you wanna give it a try.
Just wanted to update this thread. I have noticed that after flashing the voodoo kernel I too am getting the battery not connected error. However, I ONLY get this error when I have the usb cable plugged in when shutting down and starting back up again. If there is no usb cable plugged in when powering the device on, I have no problems with battery errors.
2 things stick out for me...
1. I had USB debugging on when doing the fix.
2. I removed the battery to go into initial Odin flash...PDA, etc.
The guide said my phone would reboot on its own, but it just sat at a blank screen. I had to unplug the cord and turn the power on. So do we have a fix for this yet?
i know earlier today my battery reading according tot he widget for setCPU said 66 degrees F.......which is kinda hard to believe seeing as the outside air temp is 80 degrees F outside and the inside air temp is 73 degrees F and my phone, although it had been sitting untouched for hours pluggen in inside, it was still on.....i cant believe the battery was running the best part of 10 degrees below ambient...even in idle state
Just flash the 1200 voodoo kernal u won't have that problem
Sent from my SCH-I500 using XDA App
Related
I put DL09 on and then added stupidfast v1.54. Worked fine at first but now it thinks its plugged in all the time and if i turn it off it wont boot unless plugged in. Is this a hardware issue or an issue with the kernel? Thanks for your help.
Had the same thing too. Started from scratch with Odin. Good as new now.
So i plugged my phone in and the notification for the USB went away. I havent tried to reboot yet, but the battery meter keeps going from 68% which the phone is at to 100%. Its very odd.
Is there a way to reset the battery? That might be way off but i dont know enough about it really.
see this thread
http://forum.xda-developers.com/showthread.php?t=919770
My computer sees my phone. The battery stopped jumping too. Im gonna try to clean the port when i get home from work. I still need to plug it in to get it to boot. I was gonna try reverting to stupidfast 1.98 to see if the kernel is the issue. If it makes a difference i had flashed the circle battery and it started about 12 hours after i did so. I reverted to a backup i had saved. As this didnt completely fix the problem i assumed it was the kernel. Battery life is good with the kernel as expected but the phone just seems a little testy, some things are just a little laggy like its struggling. Any additional help would be greatly appreciated. If i cant find a solution im just gonna have to re-odin everything.
Well, seems it was a dirty port. Throughout the night things got better. Got home didnt have any rubbing alcohol so i stuck some heavy paper in there to try to rub off the port. When i tried to reboot it was hit or miss, when i held the power button the battery charging screen would come up as if i was plugging the phone in while it was off to charge. Could be due to weather here maybe i had salt on my fingers from the snow and i touched the cable before i plugged it in. However GPS isnt locking in any better than it did with DI01. Ill take it for now, vast improvement over this afternoon.
Call me crazy but I seem to remember that while charging with power off, the batter icon would fill up with green, and the star looking symbol in the middle would be animated and spin around.
My phone doesn't do this anymore, and it looks like its occasionally resetting while powered off recharging. The screen blanks and the battery icon comes back after about 5 seconds. The LED doesn't turn on either. This happens with a fully charged battery or a battery that needs charging.
The phone acts perfectly fine when its on, no random reboots or anything like that, although my battery life has been sucking balls lately, 6-8 hours with moderate use after a full charge.
Any ideas what might be wrong? This happens on 2 different stock batteries, two different brand new Blackberry USB cables (much better quality than cable that came with the phone), plugged into wall charger or PC. Also, if I unplug the cable from the phone, the battery icon stays there unless I battery pull or camera/volume up/power reset.
Edit: I went from 100% battery to 42% battery in about 20 minutes of it being powered off, plugged in, in the state of what I believe to be a charging error that I described above.
Edit 2: This has been reported quite a few times and is a CWM issue, not ACS. I just wasn't using the right search terms last night lol
Sounds like a problem with your phone..
Also, what star? Lol
Sent from my SPH-D700 using XDA App
What recovery are you running, I saw this reported as an issue with CWM 3.0.0.6, but I am running that recovery, along with EB13, and the genocide 0.3a kernel and have no issues, charged my phone with it off last night, no issues.
A_Flying_Fox said:
Also, what star? Lol
Click to expand...
Click to collapse
Star was the best word to describe it lol, star looking icon that spins clockwise in the middle of the battery while its charging.
DCRocks said:
What recovery are you running, I saw this reported as an issue with CWM 3.0.0.6, but I am running that recovery, along with EB13, and the genocide 0.3a kernel and have no issues, charged my phone with it off last night, no issues.
Click to expand...
Click to collapse
I'm running 3.0.0.6 and EB13 too, with ACS kernel. I'm going to try going back to stock and see if that has anything to do with it.
I saw this too.
I've seen both this problem and a similar problem (also reported by others) of the phone freezing with the battery icon in place.
These problems went away after a flash to stock with Odin.
Subsequent re-installation of CW3 did not re-create the problem.
This only happens with twilight zone kernel
Sent from my SPH-D700 using XDA App
I think this may be a bug on ACS. I have the same problem.
Sent from my Epic running ACS Frozen 1.0
Well, a stock flash back to EB13 has fixed this problem for me. Going to try reflashing CWM and ACS to see if I get the same error.
Also, seems like that star I was mentioning only pops up right before the charging indicator starts lol, I couldn't remember what this screen normally looks like
THIS IS WHAT USING THE SEARCH BUTTONS WILL FIND YOU!
For me a similar situation, with a common solution! Thanxz!
RnS! Lol
So after a long fiasco of installing an old GB leak before installing the latest version, to running into force close loops and freezing at the M logo. So finally i reflashed everything and rebooted and bam! i finally got 596 to work. But i noticed that my battery logo had a question mark and that it basically wasn't recognizing my battery. I thought maybe a simple reboot will fix it, went in cwm and flashed the 596 deodexer and rebooted. Got into the lock screen when i noticed it immediately said Connect Charger. When i unlocked the screen after about 10 seconds it went black and my phone wouldn't turn on. If i connect it to pc the led flashes blue for a second meaning the battery is dead but with the battery not being recognized it cannot charge. If i connect it to a wall charger it loads up the M logo and goes to the battery charging screen, when you completely drain your phone and need to wait til its 5% to turn on, but again has a question mark in it. I don't have any external chargers either. Whats my best course of action? Do i have to go out and buy a new battery...? All helps appreciated.
im very sorry about bumping my thread.., but my phones just sitting here useless and its very aggravating and extremely inconvenient so once again, any and all help is appreciated please gentlemen(ladies).
If you can boot even for a second, boot into clockwork recovery and find the option to wipe battery stats. I would try that.
Also, even with a charge, booting while plugged into AC causes it to show the charging screen. Unplug it, turn on your phone, and in the middle of booting THEN plug it in.
Sent from my DROIDX using XDA App
djsupersoak said:
If you can boot even for a second, boot into clockwork recovery and find the option to wipe battery stats. I would try that.
Also, even with a charge, booting while plugged into AC causes it to show the charging screen. Unplug it, turn on your phone, and in the middle of booting THEN plug it in.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thank you for the reply, ill try wiping the batter stats asap might have to end up ghetto rigging a charge into it. Ive heard that car chargers/external chargers will still charge it, is this correct? I would love to try your second idea except for again i don't even have a charge anymore. i tap the lock button and the led flickers blue for half a second, which if im not mistaken means the battery is completely dead. While i guess its always possible, never really expected my phone to just randomly stop realizing there's a motorola batter inside of there.
Edit: also if im not mistaken i believe that i had tried to plug the charger into after/during boot up and it still says its not a certified battery or whatever the message is and refuses to charge.
Not entirely sure about the car charger idea. It might work. Kind of skeptical on that if it won't even charge when connected to a computer. You could always purchase a new battery, maybe the extended. If it doesn't work just return it. If you don't want to purchase one, I possibly could ship you an extra one just to borrow and try to see if it's a battery or phone issue.
If you have a friend with another droid x you could try borrowing his or her battery to see if the actual battery is the issue without buying one...
It sounds to me like the battery stats on your phone got corrupted when flashing the new software and need to be cleared, which as said before can be done in CW recovery. There is also an app called BatteryCalibration which will help the situation also after you actually get booted up.
Hope this helps!
Tone_Capone said:
If you have a friend with another droid x you could try borrowing his or her battery to see if the actual battery is the issue without buying one...
It sounds to me like the battery stats on your phone got corrupted when flashing the new software and need to be cleared, which as said before can be done in CW recovery. There is also an app called BatteryCalibration which will help the situation also after you actually get booted up.
Hope this helps!
Click to expand...
Click to collapse
I have actually seen the app before, at the time didnt really notice what it did but i understand a bit more now. If any of the actual charging methods work ill definitely try that. Might just have to hook it up to a split usb for a while to get a decent charge.
djsupersoak said:
Not entirely sure about the car charger idea. It might work. Kind of skeptical on that if it won't even charge when connected to a computer. You could always purchase a new battery, maybe the extended. If it doesn't work just return it. If you don't want to purchase one, I possibly could ship you an extra one just to borrow and try to see if it's a battery or phone issue.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it. Ill try the car charger i suppose, wont hurt. Worst case I do actually have a friend with a DX so i can see whats up with that. Ive been meaning to pick up the extended for a while now just never really got around to it, guess this might give me an excuse. thanks for the offer to send out a battery though
No problem. I've got a bunch of unused stock batteries for various phones from all the extended battery upgrades we've gotten.
In any case, if you can't wipe battery stats, trying a friends battery or something would be the next best thing.
What I would do if you borrow a battery, if it STILL shows the question mark then it is a phone problem. Boot into CWM and wipe battery stats while using your friends battery, then try your own.
Even if your friends battery works without giving the question mark, wipe stats anyways and maybe it will stop doing it for yours.
Best of luck to you with this!
Sent from my DROIDX using XDA App
djsupersoak said:
No problem. I've got a bunch of unused stock batteries for various phones from all the extended battery upgrades we've gotten.
In any case, if you can't wipe battery stats, trying a friends battery or something would be the next best thing.
What I would do if you borrow a battery, if it STILL shows the question mark then it is a phone problem. Boot into CWM and wipe battery stats while using your friends battery, then try your own.
Even if your friends battery works without giving the question mark, wipe stats anyways and maybe it will stop doing it for yours.
Best of luck to you with this!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Great news gentlemen! so after trying the usb split usb method to charge my phone, the first time it didnt work. i just figured i didnt have the wires pushing on the battery poles enough so i retried it. Ended up forgetting it was plugged in and about 30-45 minutes later took it off. plug her in and my phone started up, good signs so far. Finally my os loaded and lo and behold, there's my battery showing green! So i quickly throw it on my wall charger and its charging too. Wiped my battery stats just in case anyways and reflashed everything. Got 596 loaded up and running and deodoxed. After trying to install a battery mod i got a few boot loops but after a wipe didn't work luckily i made a 596 nandroid before trying it. Flashed back to that and everything loaded up fine. Cant thank you guys enough for the help you've been. making a nandroid once my full set up is back to normal haha
When I turn off the phone, it vibrates to let me know it is off, and then it waits two seconds or so then turns itself back on.
I have done hard reset after hard reset, put the latest KE8 on and it still does it. Could it be a battery fault?
Do you have Advanced Power Menu installed?
Nope. It is now not letting me switch it on unless plugged into the charger.
If I switch it on away from the charger, it shows me a battery on the screen with a flickering yellow warning triangle with a thermometer next to it.
Any thoughts?
sorry to hear that!
i've had this problem about one or two months ago, after i flashed a new rom (can'r remember which one, was it lightning?). did almost everything i could
imagine (flashed other recovery, kernel, modem) and nothing helped. also a
complete fresh install (wipe everything before) didn't solve this!
the only thing which worked for me was to go back to my old rom. after that
everything was fine again!
so, i cannot say what causes this, but if you flash another rom it should work again! if not, try to repartition with odin, using one of the provided PIT files!
yep also had this problem when i first flashed cognition. my phone would reboot after turning it off. and if the battery went dead, when i plugged it into charge it would turn itself on instead of going to the battery charging screen. all i did was reflash the rom and all was fine.
This morning I updated to Android 2.3.4.
If I root like this:
http://androidflip.com/root-samsung-galaxy-s2-android-234-xxkg1-firmware/
Will it help do you think?
Just to update, it seems to be resolved now using this:
http://www.theandroidsoul.com/root-xxkg1-android-2-3-4-firmware-rom-on-galaxy-s2/
Thanks for your help guys!
And now its doing it again lol
I can live with it, but a couple of things like it thinking there is a USB cable connected seem to happen every now and again...?
hmm thats the same way as i did it but i didnt do the yellow triangle trick so im not sure about that. everything else is standard, thats how i flashed my rom and i only had your problem the first time i flashed. did you do the yellow triangle removal?
I did the remove triangle thing yea.
I do think it is a problem with the USB connector, it could be touching itself inside, possibly causing a shortage as it occasionally thinks a USB cable is connected.
So, if I turn off, it could be thinking that the charger has initiated connection and starts up to charge, but can't charge so just continues to boot.
I have plugged the usb cable in and with nothing at the other end, and nothing pops up. So it could be something like what I suggest. It has been ok for an hour or so now so fingers crossed lol!
lol that cud be it then. it wud make sence. might wanna get that looked at tho if you dont wanna risk damaging the phone. if its doing what you said, then it cud end up killing the phone if it shorts it out permantly. let me know how its going in a day or so.
Even on lock screen if you press and hold the power button for 8 seconds the phone does shut off, is it happening for ya?
I had this a few weeks back. Reflashing cf root kernel fixed mine.
minty1978 said:
I had this a few weeks back. Reflashing cf root kernel fixed mine.
Click to expand...
Click to collapse
Likewise, solved my problems with the phone rebooting itself instead of turning off.
Ok this will be a bit lengthy but please bare with me and read...
Ive been running Darkyy 10.1 EE for months now and every has been fine.
Easily a couple of days battery, no force close issues of any sorts... Everything has been perfect.
Then the other day i noticed my battery started dropping fast. NO THIS IS NOT A BATTERY DRAIN THREAD SO PLEASE READ ON.
I took my phone off charge the other night within seconds of hearing the beep for battery full and the fully charged icon in the top right of the bar stayed there for a few seconds ( like maybe 10 ) and then the battery level dropped to 80%.
I thought hhmmm thats not right but left it and went to bed.
6 hours later i woke up to 31% battery.
I thought something must be running killing my battery so i did a reboot...
Now this is where it gets weird. Read on my friends...
after i rebooted the phone it kept rebooting itself every 2 minutes or so.
I pulled the battery of for 30 minutes and put it back but i had the same problem.
When i got home i did a factory rest and wipe cache partition and decided to flash Darkyy 10.2...
I had the same problems as above only now when my phone rebooted the battery lvl would drop by 20% then next time raise by 5% etc etc
NOW THIS BIT IS SCARY BUT READ ON!!!
I decided to flash back to froyo with ezbase using repartition to see if that would help.
I plugged my phone into the computer and nothing happened!!!! My computer wouldnt recognise my phone at all neither would my phone start charging whilst plugged into the computer.
I managed to get my computer to see my phone by booting into recovery and and then download mode and flashed ezbase.
Again same problems. So i thought OK this might be an insurance job so i flashed it back to stock JPY from samfirmware.com. I plugged it back into my computer and my PC says "the USB device you have connected has malfunctioned and windows cannot recognise..."
I have had my phone unplugged over night but the icon on the bar is still there showing USB connected, and in the pull down shade there is still the option to connect USB to copy files.
I have plugged it in this morning and it started charging but windows didnt even recognise that there was anything attached at all! No beep no fault deviced attached message... Nothing!
Oh i would also like to mention that when i flashed ezbase and tryied to do a reboot i would get the battery icon for a second like if you charged while the phone was off and then it would power down again... The only way i could get the phone to boot back up was to flash EZbase again with auto reboot ticked!
Yes that was very long sorry and thankyou to those who took the time to read it.
If anyone has any thoughts on why this would have happened please post.
Do you think this is something caused by the custom rom or is this a hardware issue completely out of my hands?
Thank you again for reading!
Have you tried another battery?
Sent using geek power
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
gsw5700 said:
Have you tried another battery?
Sent using geek power
Click to expand...
Click to collapse
I dont think its a battery issue because the battery wouldnt prevent the computer from seeing the device would it?
mammenj said:
First, I would try to check if its a hardware problem.
For that burn a stock rom and see how it is doing. If its working fine with stock, without any problem, then obviously its ROM issue.
Else if the stock also gives you the same problem, then I would say its a hardware problem.
Click to expand...
Click to collapse
Im running stock JPY right now and have the same problem
Could it be a damaged usb port, so that it doesn't always charge properly, and doesn't always detect the phone correctly when connected to the computer? That might explain the problems... Especially if that port is getting worse all the time.
Can you get it to detect on the computer if you wiggle the usb plug to the phone? Have you tried a replacement usb lead?
It does sound weird. Hope you manage to sort it out.
Mike
Garbled meaning induced by swype!
don wadte time if ur phone dosnt work on stock then its the port tht got damaged and the hardware,,,,something wrong .....better go to a service center..don expirement ,cause it might damage it more
I have just dropped it off at the shop i bought it from and they are sending it away for repair.
2 weeks of nokia 3210 magic for me!
Thanks for replies guys.