So the past two nights iv let my rezound battery go dead. The problem is it wont charge a dead battery. It charges if there is some battery and its on but when it is dead it is dead. The fix was I had to put the rezound battery in my tbolt to get a little bit of juice.
Any ideas or similar problems? I am unlocked with the htc unlock tool and running nils business sense?
Could it be a rom bug?
Don't let your battery die. It's bad for it anyway.
Sent from the Rez Beast
Once the battery is dead what does the LED on the phone do? If it blinks for a while it is either too hot or too dead to turn on, but it can still charge eventually. If the LED is not coming on at all I would pull the battery out and connect the charger with no battery and see if the LED comes on. If still no luck, get a new charger.
Blinks then Charges
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
If I hit he power button with or without the battery in the led will light for a short time. I had it plugged in all night and no charge. I used two different plugs.
As for not letting it die. I know its not ideal but I couldn't help it.
jdmba said:
I had the battery die on me once (on a prior battery and prior rezound). The phone will blink orange for a WHILE (I tried 3 different chargers not knowing what it was), but eventually started to charging. I think patience is needed. If, after 15 minutes, you still aren't charging, then that's something (but longer if the phone was also hot).
Click to expand...
Click to collapse
+1. Same thing here.
KORM via the beast known as the Rezound.
I let my phone die completely once. I freaked out that my phone wasn't charging. I went onto HTC's site and it said that it could take 20 or more for the led to turn on while charging if the phone was completely dead. Just plug it in and be patient. It will charge and the led will eventually turn on.
Sent from my Vigor using xda premium
I had this problem too, and am a little concerned I have a defective phone
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
My phone will turn on then off and im starting to think it has something to do with the battery. But when it started it was in tue yelllow on the status bar, now i have it charging without being turned on and the indicator light is on but hopping mine will fire up soon. This all just happened to me within the last two hours lol, already called verizon to get a replacement but still going down there tomorrow.
Sent from my SCH-I800 using xda premium
DLink888 said:
So I had this issue happen this weekend. My daughter was using the phone when it died. Couldn't get it restarted. (I am unlocked via HTC, stock ROM with bloat removed. Phone is a week old.)
After messing with it using the factory charger/cable and other chargers/cable combinations I got nothing. Light would only intermittently come on for a second or two then go back off.
I charged it over night with the factory charger/cable. Didn't work the next day. Charged it all day and night with my old charger/cable that I know works. Didn't work.
Tried multiple variations of taking out the Battery/Sim/SD card and using the plug-in chargers & CPU USB variations with no success.
Luckily, I had ordered a new spare battery and it came in the mail before I returned the phone. Plugged it and it started up fine.
But my concern is that my phone is not properly charging. I have also had other similar charging/battery life issues that raise concern.
As far as not letting it die, **** happens and phones die, if this is a reoccurring problem, that in my mind is pretty unacceptable. A phone should charge when its plugged in no matter what. I may end up returning it to see If just got a defective phone/battery.
Click to expand...
Click to collapse
As far as not letting it die, **** happens and phones die.
--I agree, but once it gets down to 5%, why not just turn it off knowing the problems people are having so wide spread now.
Under the exact same conditions I have had the same problem with a warm battery reboot. It seems to occur when you are talking on the phone and let it die. Once it dies the phone will not reboot. My wife has the exact same phone. When I put her battery in my phone the phone works fine. My wife’s phone dies every night and she simply plugs it in the wall and it charges no problem. Again the conditions seem to be related to the battery dying while it is hot. If the battery dies while the phone is cool and not used then it seems to reboot no problem. I will go to Verizon tomorrow to look for a fix. I will let you know what happens.
I'm also having this problem but i can return my phone because i unlock it or can i return it ?
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
mjh68 said:
Check and see if your battery is 3.7 or 3.8v . I wonder if it is related to the charging issue with the 3.8v battery some people seem to be having.
Click to expand...
Click to collapse
it's a 3.8v what do you recommend i do ?
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
I had the same issue with my OG Droid. Would kill the battery and it would stay dead, even after a whole night of charging. The above method seemed to work for me.
I make 100% sure mine never goes totally dead after an experience I had with my Droid Charge.
I accidentally let it die completely (I fell asleep when it was almost dead & it ran all night). The next morning it was off, I put in a fully charged battery & it fired right up but started FCing like crazy. Every single thing I clicked on force closed immediately, I had never seen anything like it.
I was running a custom ROM & kernel & had done a nandroid BU the day before. I restored the BU & the phone ran perfectly again, but that scared me enough that I made darn sure it never happened again LOL........
gsgleason said:
I had this happen, and here is what worked:
Unplug charger
remove battery
plug charger in
insert battery (while charger is plugged in)
I got an immediate orange LED and after a little while I was able to run the phone back on.
Click to expand...
Click to collapse
That didn't work for me i just won't let it run down i guess.
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
thehomebiscuit said:
Holy ****!!! I think I may have found the fix! I have had the same exact problem as everyone in here. It seems to happen once I root. My Rezound would die completely, then after plugging it in, the light would come on for 5 seconds or less then shut off. I plugged it into my computer and Windows makes the USB Connected sound, so I figured something is happening.
I went into my command prompt and *adb devices*. It showed my device, but says in recovery mode. I then *adb reboot bootloader* and the bastard rebooted into bootloader! From there, I chose "REBOOT" and it fired right back up! Anyone who is having this problem, please try this and let me know if it works for you!
***UPDATE***
It appears when the battery dies all the way and then doesn't charge, the phone is automatically going into recovery mode even though nothing shows on the screen. I had my SIM card out when I tried this the first time, then when putting my SIM back in, it started doing the same thing. But again, it was going directly into recovery mode. This time, I tried a simple *adb reboot* and BAM! I'm back up and running! Again, let me know if this works for you, or if you need help doing this, let me know.
Click to expand...
Click to collapse
Yes... HTC phones never charge "powered off" When you turn it off and then put it on the charger, it is actually entering/booting a special screen off recovery mode during charging.
CWM recovery on the rezound has trouble charging a completely dead battery.
Use Amon RA recovery.
Related
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
encima said:
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
Click to expand...
Click to collapse
Turn off the phone and put it on charging. Once it beeps that its fully charged, quickly unplug the battery for 5-10 minutes. Should work and 'recalibrate' your battery
Sent from my GT-I9100 using XDA App
Thanks, giving a go now.
Do you need root to calibrate though? I am on stock firmware and not in front of a windows machine to use ODIN.
Vlad the Cat said:
Turn off the phone and put it on charging. Once it beeps that its fully charged, quickly unplug the battery for 5-10 minutes. Should work and 'recalibrate' your battery
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
OK, charged to 100% and got the full notification.
Left battery out for 10 mins and whacked it back in.
Turned on and it went to the overheating sign again.
Booted into the samsung recovery and I can boot into android from there.
Battery says it is as 88, cannot calibrate as I do not have root atm.
Any ideas?
encima said:
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
Click to expand...
Click to collapse
i am actually having the exact same problem FYI im using exynos extreme rom 7.2 i think nt sure its getin worse before it used to detect usb mode somrtimes now it dosent!
encima said:
OK, charged to 100% and got the full notification.
Left battery out for 10 mins and whacked it back in.
Turned on and it went to the overheating sign again.
Booted into the samsung recovery and I can boot into android from there.
Battery says it is as 88, cannot calibrate as I do not have root atm.
Any ideas?
Click to expand...
Click to collapse
Get root and use the battery calibration tool from the market. The best idea so far. I suggest rooting with CF-Root, its fast and easy - its basically still your stock kernel but just with root.
If you really need the warranty or you'r scared of root you can install cf-root, calibrate the battery, then re-flash a stock kernel (unroot)
Sent from my GT-I9100 using XDA App
If i helped you, press thanks. Thanks.
Done and done.
Calibrated, even bought a new battery. Tried various other roms and appears to be an issue. Phone knows when USB is plugged in but does not seem to recognise the unplugging of the charger. And stays at 100% for a while before dropping down to like 80.
One thing to note is that this seemed to happen around the time of buying a dock for the samsung from Amazon, by Kidigi. I plugged the phone in to the dock without a USB cable connected to the dock and the dock LED lit up, making the phone think it was charging. Is this likely to have caused it/messed up the micro usb forever?
Thanks again guys!
well i think ive figured out what the problem was
Its due to overcharging or keeping the charger connected after battrey is full which has caused a hardware damage
im not sure if this is true but this is the closest explanation i can get the phone shows connected to charger even when diconnected only when i keep it connected for long time even after its battrey is full my usb connection has completely stopped working
---------- Post added at 01:56 PM ---------- Previous post was at 01:49 PM ----------
encima said:
Done and done.
Calibrated, even bought a new battery. Tried various other roms and appears to be an issue. Phone knows when USB is plugged in but does not seem to recognise the unplugging of the charger. And stays at 100% for a while before dropping down to like 80.
Thanks again guys!
Click to expand...
Click to collapse
well that the same problem with me when it shows connected to charger at 100% i restart it then the phone drops to ~80% battery although its 100% which makes the app battery monitor widget think i have a 1977mah battery while i have the standard 1650mah battery this must be the extra 20% which disappeared after the restart for me
I thought it may have been an overcharging problem, although no other phone I have owned has had this problem.
I let the battery charge all the way down (it stayed at 1% for about 3 hours) until it shut itself off. I left it on the side and it created a clicking noise, it was trying to turn the phone on as it knew the battery was in, even though it was depleted.
I plugged it in via USB to charge and it tried to turn on straight away. Shut it down and charged by plug until the 100% notification then turned on.
Still the same problem but one of my battery widgets warned that the battery was over voltage for a while before calming down.
If the phone cannot be off with the battery in, what could be causing that?
encima said:
If the phone cannot be off with the battery in, what could be causing that?
Click to expand...
Click to collapse
It has been known to be caused by a defective circuit board for the USB connector.
So, it needs a samsung return, I assume?
i have the same problem with overheating and usb plugged when there is nothing connected
i changed the usb port from the phone but it still having the problem!!!
i will try to put a new battery and see if it work and after post a reply
My Rezound is broken
I unlocked and de-sensed it, but that was when the unlock first came out and it's been working fine since, so I don't thing that's the problem.
The phone won't come on, and when I plug it in the charge light doesn't even come on. If I leave it plugged in, then take the battery out and put it back in the charge light comes on for a few seconds, then turns off.
I was at a new years party the night before and I may have laid down on top of it while it was in my pocket, but the water sensors are fine, and I don't remember it ever getting wet.
I notice there are a lot of connections between the phone and the back cover. Is it possible that something could be bent and these connections aren't being made, so the phone refuses to do anything? I tried putting wires across them where they would normally be connected, but it didn't seem to help.
So what do you guys think? Is there something else I can try? I guess if it's totally broken then they can't tell that it's unlocked, so I could try getting a replacement :/
First off, I wouldn't have put any wire across any of the antenna leads like that. Second, if the phone is not coming on with the cover off then you may have another problem. The phone should turn on without the cover. You just wouldn't have signal.
My opinion, try another batter if you know anyone who has one. Or maybe go to your VZW store and see if they will let you use one of theirs. If the battery/phone is too hot the LED will blink orange, once it is cool enough, or full enough to turn on/charge again it will become solid. The fact you get an indication when there is no battery leads me to believe there may be a problem with the battery itself.
with the phone off, pull the battery for several minutes. Then put it back in and plug it in to the charger. Do not try and turn the phone on. If the charge light comes on and stays on, just let it charge for a few hours until it turns green.
I've read of rezounds dying from the battery going completely out. Screws it up somehow. Verizon also has thunderbolt external chargers for 5 bucks. You could use that to charge the battery (it fits), then try and turn it on. If it still won't turn on after charging, put the battery in and try and boot into the bootloader menu (power on and vol down at the same time), from there you can restore your nandroid or flash another ROM if it will boot to it.
I tried leaving the battery out for a few minutes, and then for the rest of the day. No dice in either case. I'll try to get an external charger tomorrow :/
Thanks for the ideas, I'll let you know how it goes.
Mine died overnight. Same symptoms, charging light for a few seconds then nothing. I plugged it in, let it sit for a while (didn't time it, but not more than 15 minutes). Unplugged it, then: held power, volume up and volume down all at the same time. It booted up, as soon as the screen came on, I plugged it back into the charger. Running fine now. Hope this helps someone else.
Went to Verizon today. I bought another battery and ordered an external charger. Swapped in the new battery and the phone started right up
Now I just hope I didn't screw anything up messing with the antenna contacts :/
ministroni said:
Went to Verizon today. I bought another battery and ordered an external charger. Swapped in the new battery and the phone started right up
Now I just hope I didn't screw anything up messing with the antenna contacts :/
Click to expand...
Click to collapse
After getting the new battery, does the orange LED come on while charging the phone when powered off? I replaced my battery after having the same problem and now the orange light does not stay on while the phone is charging when it is powered off. I guess it's no big deal, but it bothers me.
flie4wtguy said:
After getting the new battery, does the orange LED come on while charging the phone when powered off? I replaced my battery after having the same problem and now the orange light does not stay on while the phone is charging when it is powered off. I guess it's no big deal, but it bothers me.
Click to expand...
Click to collapse
Yeah, it still works just fine. I turned it off just now and then plugged it in to check and the charging light came on immediately.
Maybe the battery is faulty or you got a thunderbolt battery by mistake and the phone is confused? Otherwise I have no clue why that would happen :/
I have them same problem. My phone is completely dead, won't turn on and a orange light comes on for 3 seconds and goes away and nothing happens. What do I need to do?
Sounds like your battery died. Pull the battery and let it sit for a few, then try to boot it back up and plug it in immediately.
I was reading a thread about this last night on RootzWiki. Dude did a lot of testing, came to find out it was ClockWorkMOD keeping a completely dead battery from charging at all. Is that the recovery you have? If so, I would put AmonRa on, try that.
Agreed, almost definitely a dead battery. You can try this:
1) Take out the battery and put it back in
2) Hold down power and volume down to enter the bootloader
3) Immediately plug the phone in and leave it there for 10 minutes or so
4) Reboot the phone now that you have enough power to make it through booting
This should work as long as your battery is completely dead.
My suggestion for the future though is to buy an external charger and a second battery. That's what I did, and now any time I accidentally let my battery die I just swap it out and I'm good to go at 100% while the other one recharges. Also an external charger is the easiest way to fix this if your battery is too dead for the above method.
ministroni said:
Went to Verizon today. I bought another battery and ordered an external charger. Swapped in the new battery and the phone started right up
Now I just hope I didn't screw anything up messing with the antenna contacts :/
Click to expand...
Click to collapse
Also, remember that if you are using Clockwork Recovery for some reason that makes the phone not charge when its powered down. I had the similar issue where i couldnt get it to charge or come on at all, i put in a battery from my TBolt and it turned right on, switched Recovery to Amon Ra (Blue one, not the Red one) and from there it charged no problem!
worked...
slim6596 said:
Mine died overnight. Same symptoms, charging light for a few seconds then nothing. I plugged it in, let it sit for a while (didn't time it, but not more than 15 minutes). Unplugged it, then: held power, volume up and volume down all at the same time. It booted up, as soon as the screen came on, I plugged it back into the charger. Running fine now. Hope this helps someone else.
Click to expand...
Click to collapse
this worked for me! thank you!! also to come to think of it, the problem happened after installing clockworkmod recovery. so there certainly seems to be a connection
slim6596 said:
Mine died overnight. Same symptoms, charging light for a few seconds then nothing. I plugged it in, let it sit for a while (didn't time it, but not more than 15 minutes). Unplugged it, then: held power, volume up and volume down all at the same time. It booted up, as soon as the screen came on, I plugged it back into the charger. Running fine now. Hope this helps someone else.
Click to expand...
Click to collapse
This absolutely helped me! I'm really liking this Rezound I picked up but the damn thing is also just very temperamental in general. Still a fantastic underrated device overall though.
My wifes d2g did that once. I ended up taking an old charger, stripping the ends off and taping it to the contacts on the battery for 30 minutes. It charged it up and after that it would charge thru the phone again. A lot cheaper than a new battery.
Sent from my ADR6425LVW using xda app-developers app
So I am on my second battery right now. The first one just decided it shouldnt turn on. I could plug the charger in and the notification light wouldnt turn on, pull the battery and it would. Well, now my second battery is doing the samething. I had left it on the charger while I was outside doing stuff, came in in the afternoon, dead phone. Pulled and replaced battery a few times, phone still wouldnt turn on. Then I plugged in the charger and no notification light would come on. So I finally pulled the battery and with the battery out I plugged in the charger and then the notification light would come on. What the hell is going on here?
Anyone else have these problems? Now I have to drive 30+ miles one way to my nearest Verizon store to replace this damn thing and I am not happy about this one bit. Anyone on here have any suggestions for me?
remmy5r said:
So I am on my second battery right now. The first one just decided it shouldnt turn on. I could plug the charger in and the notification light wouldnt turn on, pull the battery and it would. Well, now my second battery is doing the samething. I had left it on the charger while I was outside doing stuff, came in in the afternoon, dead phone. Pulled and replaced battery a few times, phone still wouldnt turn on. Then I plugged in the charger and no notification light would come on. So I finally pulled the battery and with the battery out I plugged in the charger and then the notification light would come on. What the hell is going on here?
Anyone else have these problems? Now I have to drive 30+ miles one way to my nearest Verizon store to replace this damn thing and I am not happy about this one bit. Anyone on here have any suggestions for me?
Click to expand...
Click to collapse
If you bought it from Verizon and not second hand, then you have 1 year warranty. I suggest you call Verizon's customer service and speak with them and get a replacement sent. I've done this multiple times with just about every phone I've had. 1800-922-0804 is what I dial. to get to them, press 0, then press 0 again, and it will ask for your account password, then a rep will get on the phone.
best of luck.
If the phone is older than 30 days, or maybe it's 14 now with Verizon, they give you a refurbished phone, if you are over that period and went to the store I'm pretty positives all they would do is order you the replacement refurb phone. 30+ miles each way is a hike, save the gas money
remmy5r said:
So I am on my second battery right now. The first one just decided it shouldnt turn on. I could plug the charger in and the notification light wouldnt turn on, pull the battery and it would. Well, now my second battery is doing the samething. I had left it on the charger while I was outside doing stuff, came in in the afternoon, dead phone. Pulled and replaced battery a few times, phone still wouldnt turn on. Then I plugged in the charger and no notification light would come on. So I finally pulled the battery and with the battery out I plugged in the charger and then the notification light would come on. What the hell is going on here?
Anyone else have these problems? Now I have to drive 30+ miles one way to my nearest Verizon store to replace this damn thing and I am not happy about this one bit. Anyone on here have any suggestions for me?
Click to expand...
Click to collapse
Just had my Rezound battery die last night. It was freezing outside and my battery was at 1%. The screen just went blank. When I got home, plugged in the charger. The notification led came on for 3 seconds then went back off again. Tried several chargers I had and pulling the battery and plugging it in.
Weird.
Verizon has the 14 day return/exchange policy now. I was at 12 days so I just went in and they replaced the battery with a brand new one from a Rezound box. I assume they will send that unit back RMA. My phone works now.
You're not the only person having battery death issues. Not sure why this is a problem on the Rezound. I recently purchased an extended battery ironically. It will be arriving tomorrow.
Here's to hoping that it won't die. I should buy some spares just in case. Make sure you call customer service and report the issue. It is tracked.
I was also having an issue charging from a dead battery (would charge just fine otherwise). The charging indicator would not stay lit, but after giving it 10 minutes or so, repeated attempts to power on would eventually work and then it would charge normally.
Had this happen several times and then reflashed the stock image. Seems to be working as it should now. However, when I got my phone it had a dead battery it wouldn't charge. So we'll see what happens.
Note: was running Senseless 1.0 and de-bloated. Stock rom kernel. If it matters....I probably didn't get a clean install when doing it all.
Rezound has a known issue that if the battery dies to far you'll need something else to charge the battery. Some people have used their old thunderbolts to give it a pre charge, buy the stand alone charger from Verizon. Or just don't let your phone discharge tthat far.
Sent from my ADR6425LVW using XDA App
nosympathy said:
Rezound has a known issue that if the battery dies to far you'll need something else to charge the battery. Some people have used their old thunderbolts to give it a pre charge, buy the stand alone charger from Verizon. Or just don't let your phone discharge tthat far.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Good to know - is that all or most Rezounds? Because I wonder if I should swap mine while I still can.
Like I said, I was having that issue and after flashing the stock RUU (updated one, .6) my phone is charging a dead battery just fine (2 for 2 so far, fingers crossed).
Actually brand new in the store mine had a dead battery and it would not charge, so they gave me a new battery. Perhaps there was a fix in that updated RUU. It's just a suggestion - after I confirm this works consistently I'll see what happens with some other roms.
Alternatively, it's also possible the stock RUU doesn't let you drain the battery as far as the roms do. I was able to power back on several times until it finally wouldn't (and no led flashing at that point), but now it charges from there.
Yea, I woke up one morning and my phone was deader than a door nail. Popped on the charger and no notification light, called Verizon to whine and prepared to stop by the store to get a replacment battery. However just for kicks I plug the phone back on the charger (ok my laptop) and after 1/2 hour the notification light popped back on and the battery started to charge. Now Prior I was having a high rate of discharged getting about 2 hours of use and 5 on standby (airplane on, WiFi and Data off) and still having the high rate of discharge. I started to investigate why the phone was getting hot and discharging so fast. Now I couldn't fine the culprit (I think WIFI was the cause) but I just did a factory reset, reloaded my rom and kernal and poof, everything return to normal including much longer discharge rates and I'm much happier now (Adult Beverages and household chemicals indigestation).
If you go to HTC's website it actually has a faq on this. Their response goes pretty much like this. If you drain your battery till the phone shuts off, plug your phone in. It will flash the notification light then there will be no charging light. The light could take 20 minutes or more to turn on. I also had this problem like you guys but just put it on charge over night and it will be fine. Just don't kill it to 0 anymore.
Found the Quote: My phone won’t power on. What can I do? close
If your phone will not power on, your battery may be drained or not seated correctly.
Tips:
If the battery is completely dead, the phone will need to charge for a few minutes and then should power on once this happens. When plugging the phone into the charging, the notification light may not light up immediately as the battery is completely dead. Let it charge for about 20 minutes before trying to power on.
Make sure you are using the AC charger that was supplied with your phone
Sent from my Rezound using xda premium
battery discharges while plugged in and using it
ok, so this happened with the stock rom, and two other roms i had.
What would happen is if you plug the phone in, and use it, you would expect it to charge while you are using it. It did on my dinc. it actually discharges while you use it and it is plugged into the supplied charger.
This is not a good thing. I am wondering if anyone else is having a similar experience.
One interesting side note.
I installed rezrom recently, and after the initial install i didn't experience this problem and got a 24 hour charge out of the battery. Now on my second charge only lasted 7 hours, and i get that drain while plugged in again.
Are you using the stock charger or a different one? You might not be charging at 1amp.
Sent from my ADR6425LVW using xda premium
I am using the stock charger. I have two actually, one from my dinc, which also supply 1 amp of power
That's really crappy and definitely an issue they need to address. My Rezound sucks on the battery like a wine-o on a Friday night, but it's never gotten to the point of blacking out.
I am just interested to know if anyone else is experiencing this issue of it being plugged in and not charging when u surf the net, but actually discharges.
The whole issue of it not powering up for 15 minutes after it dies is a bunch of crap too. my dinc does not do this, and god forbid that my phone dies in an emergency situation and i need to get a hold of someone fast!
oh i forgot to add that i called VZW and complained about this, and they going to send a new battery. Something tells me this won't resolve this issue though
I have the official HTC 2750 battery and Its been good except 2 mornings I woke up to an unresponsive phone with no charge notification after plugging it in.. Pulling the battery and reinstalling let me start the phone up. I have had this phone/battery combo for 2 weeks.. should I try to get a replacement battery or is this normal. There have been two different answers here and I want to do the right thing here...
Sent from my Xoom using xda premium
UgXvibe said:
I have the official HTC 2750 battery and Its been good except 2 mornings I woke up to an unresponsive phone with no charge notification after plugging it in.. Pulling the battery and reinstalling let me start the phone up. I have had this phone/battery combo for 2 weeks.. should I try to get a replacement battery or is this normal. There have been two different answers here and I want to do the right thing here...
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
So you are saying the phone died, then refused to charge on the extended battery?
carm01 said:
So you are saying the phone died, then refused to charge on the extended battery?
Click to expand...
Click to collapse
Yes, exactly. Not sure if it was entirely discharged. I'll leave it off the charger tonight and see if it does it again by morning. I'll let you know battery % once I get it booted.
Sent from my ADR6425LVW using xda premium
From the beginning, phone was on charger, charging then came back later (phone still on charger) no led, nothing, phone wouldnt turn on.
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
I read loads of similar issues, but mine is a little different:
I heavily used my stock-rom, unrooted phone today, recorded long videos in Full HD, when I got back home, I had 18% battery, plugged it into my computer's USB to get the videos (unaware of the issue of insufficient current on USB ports) and windows did not recognize it.
I then unplugged it planning to plug it into the wall socket, and when I woke the phone, it died on my arms
A little annoyed, I plugged it into the wall socket, and got the slow, orange blinking LED, and was not able to turn the phone on. After 30 minutes, the LED stabilized and it seemed to be charging (while off), so I left it there for another 20 minutes.
When I tried to turn the phone on, it worked, normally, but showed 2% battery life remaining. I had Wi-Fi on, but normally it wouldn't be an issue, so I left it charging for another 20 minutes.
I then woke the device and it showed 1% battery left! While plugged in! I tried to wake it and it died again.
I left it there for an hour or so, turned it back on, 6% battery left, I then turned Airplane Mode on so it would charge faster. After 10 minutes in Airplane Mode, it still shows 6%. It is not charging, I'm using the original HTC charger and cable.
It seems like it is not charging at all when on, and charging VERY slowly when off.
Tried a few tricks I read online, such as holding the volume up + volume down + power button for 2 minutes, but all I got was a steady flashing recovery screen, which says my battery is too low for flashing.
So the difference between mine and other posts is that my stock phone is turning on, but not charging anymore. If I turn Airplane Mode off, it drains itself even while plugged into the charger.
I'm really looking for a solution for this, instead of simply returning it (it's more than one year old, and I bought it overseas) or buying a new phone.
EDIT: Battery Widget app showed Charging Speed: n/a. Testing says battery health: good, 3666 mv, "charging" status
EDIT II: Tried running it in Recovery Mode, got a 3d exclamation point with a phone icon. Rebooted it normally, it turns back on, still not charging. This does not look good at all.
EDIT III: Read about Mr Hofs idea, of running custom recovery via the PC, but I can't get it to connect. Have newest version of Sync Manager yet windows says the "device malfunctioned" and could not be recognized.
EDIT IV: Done factory reset, no luck. Phone is still draining while plugged in. After 8 hours of charging while off, all I got was 40/50% I'm really desperate as the phone is virtually bricked and I need it for work. Willing to tip/donate to whoever finds solution, if that is ok according to forum rules (not sure)
Are you using a stock charger... With at least 1amp output
Sent from my HTC One X+ using xda app-developers app
yokozuna82 said:
Are you using a stock charger... With at least 1amp output
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
I am, HTC charger, 5V, 1A
Back to the blinking led
I tried plugging the phone into the computer's USB port, got the red blinking led again. Held the volume down + power button while connected to the PC and it seemed to be constantly rebooting - windows popped up "device not recognized" several times and the power led started flashing much slowlier. Sometimes the lower leds would also flash. I held it like that for 2 minutes.
After a while the lower lads and the screen backlight lit up. I then realeased the buttons and quickly plugged it into the wall socket.
Now I have the fast blinking again. Awesome. I can't tell if I'm doing it right or brutally murdering my phone
You might just factory reset once your charged as .much as you can. I believe your problem. Is having to do with using or somehow got a bad current or USB port/cord etc. Anyway its software related and a hard reset doesn't help I'd RMA ..you go flashing mods to do yourself probably won't work especially if its hardware. Hope this helps. I say this as it happened to me. I used a lower amp wire charger socket. Same thing happened. After many hours of trying stuff. Factory reset never used bad or non OEM again. But in your case it may be just some IDD quirk. It happens bro. Hope you get it up and running. ..
Sent from my Nexus 4 using XDA Premium 4 mobile app
Droid2drummer said:
You might just factory reset once your charged as .much as you can. I believe your problem. Is having to do with using or somehow got a bad current or USB port/cord etc. Anyway its software related and a hard reset doesn't help I'd RMA ..you go flashing mods to do yourself probably won't work especially if its hardware. Hope this helps. I say this as it happened to me. I used a lower amp wire charger socket. Same thing happened. After many hours of trying stuff. Factory reset never used bad or non OEM again. But in your case it may be just some IDD quirk. It happens bro. Hope you get it up and running. ..
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Left it charging while off overnight, now I have 40% (!) battery. Any time I try flashing the default recovery, it'll show a red exclamation. The PC won't recognize it at all, even with downloaded drivers. And doind all that seem to have drained it to 30%.
Will try to get my important files and then factory reset it.
yukifujita said:
Left it charging while off overnight, now I have 40% (!) battery. Any time I try flashing the default recovery, it'll show a red exclamation. The PC won't recognize it at all, even with downloaded drivers. And doind all that seem to have drained it to 30%.
Will try to get my important files and then factory reset it.
Click to expand...
Click to collapse
Done factory reset, no luck. Phone is still draining while plugged in.
So that's it? Phone is bricked then?
Charge to 100%
Try a different charger
Try flashing a different ROM/kernel
Try flashing RUU
Contact HTC
That's what I would do and the order I would do it in. Leave it alone until it is charged up to 100% before you do any of this though. Even if it takes a week. For all I know, charging to 100% will reset the charging circuit. I doubt it, but who knows.... Stranger things have happened.
ridethisbike said:
Charge to 100%
Try a different charger
Try flashing a different ROM/kernel
Try flashing RUU
Contact HTC
That's what I would do and the order I would do it in. Leave it alone until it is charged up to 100% before you do any of this though. Even if it takes a week. For all I know, charging to 100% will reset the charging circuit. I doubt it, but who knows.... Stranger things have happened.
Click to expand...
Click to collapse
Well this is awkward.
After many days, and since HTC is not present in Brazil anymore, I have no ways of contacting support, I gave up, bought an S4. After two days with my new phone, guess what? The HOX+ charged 100%, and it seems to be discharging normally. GOD DAMMIT.
So, ridethisbike, your suggestion worked, kudos for you and boo for me for not being patient and giving a shot.
Out to look for a buyer then. :silly: