Related
Hi, I have recently acquired (mid Sept. 2007) a TyTN II device: really a very good and nice device ... till yesterday.
Maybe my experience could be shared with some of you...
Yesterday my device suddenly turned off apparently because battery very low (i.e. less than 5% according to the manual): this is strange because as far as I remember my battery was charged enough to survive more than one day considering that I did not use Wifi/Bluetooth or many phone calls.
By the way, the problem occurred when I attempted to recharge the device: it spent hours under recharge but the power led never become green, but remained orange. I attempted anyway to startup the device, but as soon as the Windows OS started it automatically shutdown because battery too low was detected.
I performed several software reset and finally an hardware reset, while attempting also to recharge it also via USB but without any positive effect.
I contacted HTC which suggested me ... to provide back the device most likely for being replaced according to the DOA (Dead On Arrival) policy.
Please note that according to some tests I performed on the battery, this seems to be charged and the problem relying on the device or OS which do not recognize it as charged but so low that no operations are permitted.
Has some one experienced a similar issue with this new HTC device ?
Cheers,
Max
GF's 8125 did almost the same thing; wouldnt charge past 10% and kept sending notification after notification; this was literally right out of the box. Cingular/AT&T suspected the battery but replaced the 8125 as well.
So far I have not seen other reports of this for TyTn II. It is however a reasonably common problem with many different brands of phone.
Mike
Could be a Power managment issue its not uncommen at all. things go wrong in all electronic devices think of the millions of Kaisers that will be sold in the coming months a few are bound to messed up from the factory. Its like buying a car you know ****s guna happen but you buy it anyway since it looks really nice that first day!
Did you all charge using the supplied wallcharger instead of via USB?
JwY said:
Did you all charge using the supplied wallcharger instead of via USB?
Click to expand...
Click to collapse
Make your kaiser power off, and use wallcharger. If it still doesn't work, call for HTC..
Some problems are solved by letting the internal battery drain, by leaving the device without the battery for a couple of days.
That issue can happen if you (almost) run out of battery.
Best practice: NEVER EVER run down your battery below 5% ! As soon as it reach 10%, switch off if you dont have charger at that time.
You might go below 10%, but take the risk .... !
It is known to us that the new Windows Mobile 5.0 supports persistant memory (your data will not lost when the battery runs out 0%), but it does not say that you will not be able to charge the battery!
More explanation? And how to revive the battery?
Read this thread:
http://www.modaco.com/Warning-Battery-Chargin-t233233.html
It is well explained, how that happen and how to recover the battery
gogol said:
That issue can happen if you (almost) run out of battery.
Best practice: NEVER EVER run down your battery below 5% ! As soon as it reach 10%, switch off if you dont have charger at that time.
You might go below 10%, but take the risk .... !
It is known to us that the new Windows Mobile 5.0 supports persistant memory (your data will not lost when the battery runs out 0%), but it does not say that you will not be able to charge the battery!
Click to expand...
Click to collapse
ey man, i followed the recommended procedure for the three firsts battery charges. First i plug the PDA and let charge at 100%, then i let the battery goes to 0% (yes, the PDA goes off, of course) and then plugin onto the wall charger, and let charge to the 100%, repeating this procedure three times.
I do this also with my previous PDA, Hermes. And no problem leting the PDA going to 0%...never see this problem before.
What is the supossed problem leting the battery goes to 0%?
Regards.
EDIT: Found this interesting information about LiIon... http://en.wikipedia.org/wiki/Lithium_ion_battery and http://www.batteryuniversity.com/parttwo-34.htm
jcespi2005,
I simply dont know I just shared the link that I knew from modaco which is useful in this case.
Maybe this is not 100% the case, but as I said "best practice" ... something that it is better to follow to avoid this issue as you should read already that quite a lot of people affected by this very low depleted battery.
gogol said:
jcespi2005,
I simply dont know I just shared the link that I knew from modaco which is useful in this case.
Maybe this is not 100% the case, but as I said "best practice" ... something that it is better to follow to avoid this issue as you should read already that quite a lot of people affected by this very low depleted battery.
Click to expand...
Click to collapse
The modaco thread talks about Wizard, i think it's not 100% the same as Kaiser, cause is not the same battery, and the hard charge interface on the PDA can be different. I'm going to make a deep research about model and manufacturer for the Kaiser Battery, to see what can be the issue.
Anyway, i let my Kaiser goes 0% three times and charge fine for the three times. So i beleave the issue is not related with the battery itself. Can be the charger? don't know...
What is the model and manufacturer for your Kaiser battery, please?
Mine is Samsung model KAIS160.
Just checked and I have the same battery, SAMSUNG KAIS160.
I have now seen another report on another forum with this problem (Kaiser). I suggested the standard method as used when the refusing to charge issue arose with the Hermes (TyTn).
(It worked by the way!)
i.e.
1
Remove the battery for half an hour or so
2
With the battery still removed connect and switch ON the official (1000mA) MAINS charger (Not other brands that deliver only 500mA)
3
Now insert the battery
4
Wait for up to 5 mins for the Red LED to change to Orange
Repeat steps 3 and 4 if you have no success after waiting for a reasonable time.
(If that fails then elsewhere I have reported the technique of delivering a charge to the battery using a couple of AA batteries)
My view for what it's worth:
Although in rare cases there may be a faulty battery, in the main the problem is not caused by the battery. The likely explanation is that the circuit that detects the battery's presence, fails to detect the battery when the battery charge is very low. In other words there is no problem with battery but the battery charge detection circuit is either frozen or does not switch on when the battery charge is too low.
This issue I see reported across many brands of phone and is not a WM specific problem.
Mike
mikechannon said:
My view for what it's worth:
Although in rare cases there may be a faulty battery, in the main the problem is not caused by the battery. The likely explanation is that the circuit that detects the battery's presence, fails to detect the battery when the battery charge is very low. In other words there is no problem with battery but the battery charge detection circuit is either frozen or does not switch on when the battery charge is too low.
This issue I see reported across many brands of phone and is not a WM specific problem.
Mike
Click to expand...
Click to collapse
Many thanks for the information, this confirms my suspects about the interface to the battery, and not the battery itself... i see this issue time ago with one Nokia 6100, and solve it with the same procedure you write. Sometimes LiIon battery gain some charge if you place in the refrigerator for a while (cool helps LiIon batterys, and warm hurts).
Regards.
EDIT: More info about charging LiIon battery here http://www.batteryuniversity.com/partone-12.htm
Seems there is no need to make three charge/discharge cycle before use the LiIon battery. Simply you can use and charge in any moment. Really is better sorts and many charges rather than less and longs charges/discharges.
Power Failure.
Hi guys,
Well the USB did the trick.
Don't forget the Red Wire is the + (Positive)
and
the black Wire is the - (Negative).
A few minutes holding in place did the trick.
Thanks a lot for this thread, I actually had the feeling that I have lost the Kaiser.
Ronen
irsw said:
Hi guys,
Well the USB did the trick.
Don't forget the Red Wire is the + (Positive)
and
the black Wire is the - (Negative).
A few minutes holding in place did the trick.
Thanks a lot for this thread, I actually had the feeling that I have lost the Kaiser.
Ronen
Click to expand...
Click to collapse
what USB trick? what wires, and where do you put them in the phone? thanks!
nevermind, just tried it and it definitely charged the phone, but when i then plugged it into the charger it the battery just decreased like before
theromanone said:
what USB trick? what wires, and where do you put them in the phone? thanks!
Click to expand...
Click to collapse
Hello,
Take a USB cable (the one like you use to sync your pda) cut it in the middle, expose the wires inside.
The red wire (+) is to be attached to the PLUS of the battery, and the balck wire (-) is to be attached to the minus of the battery.
About one minute and fater re-install the battery and try charging again, this should do the trick.
You can also use 2 AA batteries in the same manner.
Yours,
Ronen
just happened to mine after only a month. Contacted att and the forum and had to get it replaced. So far nothing wrong with this one!
jcespi2005 said:
Many thanks for the information, this confirms my suspects about the interface to the battery, and not the battery itself... i see this issue time ago with one Nokia 6100, and solve it with the same procedure you write. Sometimes LiIon battery gain some charge if you place in the refrigerator for a while (cool helps LiIon batterys, and warm hurts).
Regards.
EDIT: More info about charging LiIon battery here http://www.batteryuniversity.com/partone-12.htm
Seems there is no need to make three charge/discharge cycle before use the LiIon battery. Simply you can use and charge in any moment. Really is better sorts and many charges rather than less and longs charges/discharges.
Click to expand...
Click to collapse
Hi Mike,
Had my Kaiser sent to a lab, they are checking it but they are saying it is a faulty board.
The battery is ok although I bought a new one and tested it to find still the same problem.
Thanks.
Hey guys,
Wondering if any of the Hero-ologists here can help.
I have a CDMA Hero, running the most current radio, kernel, etc. Currently I'm running the CM6 nightly with JIT enabled, (Linpack is ~4.9, Quadrant ranks higher than average Motodroid, FTW)
Anyway, I've had the issues below for months now. Nothing changes with kernel, ROM, anything.
From the moment I bought my Hero it's run exceptionally hot. I've come to believe that perhaps it's simply due to the fact that I live in a 1X area, averaging about -100db signal. Battery has always gone extremely fast as well, but that's pretty common.
I have two batteries and an extra charger, and generally I keep a rotation throughout the day, and often I use all 3 batteries. I'm a pretty heavy user (hah, sounds like a drug).
Alright, so here are my symptoms, besides the rapid battery drain:
-Sometimes when my battery states it is somewhere around 20-30%, it will suddenly restart, then it will say it's around 3-7% and to connect my charger.
-Randomly, occasionally, my phone will simply give up charging. This happens plugged into USB, my car charger, or the factory charger.
-When it gives up charging, sometimes the light will stay orange anyway.
-Usually, the LED will instead switch to a rapid-flash of orange/green/2 seconds/orange/green/2 seconds...and so on....and it most certainly is not receiving any power.
Usually I just tolerate the issue. When it happens, I'll swap the battery and it works fine, charges fine. Here are the things I've tried that don't seem to make a difference:
-Battery wipe
-Full battery conditioning
-Ensuring I'm plugged into a USB 2.0 port on the PC
-Swapping to the wall from USB
None of these things work. But it happens with any of my 3 batteries, and when I swap with whichever battery is charged, it fixes the problem.
A bit more storyline here, for record:
When I first got my phone, the battery went so fast, I contacted Sprint. Unfortunately there's no service center for about 120 mi from where I am, and I was too stupid to buy Best Buy's Black Tie when I bought the phone.
They said to go to the local dealer and see if they'd give me a new battery. The local dealer is run by a complete *****, and Best Buy looked at me like I was crazy.
I bought the phone in February, and I believe it's under a 1 year warranty, so perhaps Sprint would swap it for me. I would of course have to unroot my phone, which I'm fine with. But the litmus paper is slightly smudged, and I'm not sure what Sprint would say if they got the phone that way either.
Anyway...that's my story. If anyone has any input, I would be greatly appreciated.
Thank you!
EDIT:
Note that because of the spare charger, normally this isn't a real issue. But I fear things may get worse, and just in case, I'd rather fix this issue now than later. And being that tonight I left my charger and spare batteries at work, my battery officially depleted and I have no phone until tomorrow. And it's like having your crack-pipe taken away.
Right off the bat, my Revo is non-responsive, no buttons will light, backlight, vibration, sound, and of course no splash screen since the screen isn't lighting. The only sense that it is partly there is after a time connected to USB/wall charger the battery warms as if it is charging. Yet, there is no indication during charge on the screen, it stays totally black as described above.
I have been poring over forum posts, CWR threads, and the like, but have come up short on a method of reviving this puppy. thecubed had posted something that seemed promising but doesn't work for me here. At all steps, the phone remains non-responsive and connecting it to the PC yields no mass storage connection. The only step I have abbreviated is letting it charge for an hour since the phone had charged about four hours since it shut down.
Two evenings ago, I flashed from Revolt ROM 1.0 to 1.1. It was successful but since I had just gone through battery calibration and running my battery down until the phone shut down the day before when I flashed it to 1.0, I was hoping (naive?) that I wouldn't have to do it this time (yes, naive!). So, I left the phone on all night, on the wall charger.
I was using it the next day and at one point, while using it in a low reception area, browsing the web, it rebooted on me. No biggie, had that happen in the past. After reboot however, the battery level seemed different so I wanted to get it topped off then calibrate. 1-2 hours later I noticed that the calibration app was showing the mV lower and capacity was at 70%. The battery felt unusually hot. I shut it down, removed the battery and cooled both battery and phone in a small fridge to accelerate the process (was near time to leave work).
Next boot was I recall having an extra FC, one beside the CarHome normal FC with Revolt ROM 1.1. This boot the battery showed maybe 20% capacity so I said "screw it" and deleted battery.bin with the battery calibration app (I recall the mV was low, in the 3600 range). I discharged it on the way home and left the display on to run the last couple percent down. It appeared to try and shutdown but ended abruptly. That was the last time I saw any life from my Revo.
The day after its first and only ever root, I did have an odd occurrence which I posted.
Boot Trouble - Rooted After Phone Downloaded OTA, Not Installed
That time, I had not installed a ROM yet but the phone got itself into a boot up funk. Removing the battery, connecting to wall charger, watching buttons flash ~5 times, disconnecting (which stopped the flashing lights), then battery in, power on... success! I was hoping that would happen this time around but I haven't been able to.
Full history, being my first root, I used S1C successfully, installed Titanium Backup (ran system and app backup), and RevoToolkit. The phone did download the OTA but I never let it install, instead selecting to delay it by 24hrs when it asked to install. Fearing that deadline and getting one more warning that it wanted to reboot and install the OTA, I went ahead and installed the Revolt ROM 1.0. All went fine, no drama. The next afternoon I thought going to 1.1 was going well too, until this brick hit me.
My hope of hopes is it's just a bad battery and the phone won't respond because the mV is too low. Reading thecubed's comment in his first link (above) how recoverable this phone is lends me hope.
It sounds like a bad battery. I would take it to a verizon store and see if you can try a different battery. If it still will not boot then they should warranty it out for you.
Sent from my VS910 4G using XDA Premium App
P.s. I never do anything for my battery. I charge until full then use until empty. Yesterday with moderate tI heavy use I made it from 6am until 8:30 pm
Sent from my VS910 4G using XDA Premium App
Thanks for the responses. I will be going to VZW shortly to figure this out. This phone is maybe two months old so hopefully the battery is the answer *fingers crossed*
Impressive battery life! At my office, I'm in a bit of a metal cubicle area and a bit low on signal strength. My phones will sometimes use up the battery trying to keep connected, it seems, so I am usually plugged in most of the time.
While I have your ear, thanks for the great work on Revolt ROM. I am very happy with it and look forward to its future development
Good news and bad.
The good news was they swapped in a new battery and the phone worked. Having the warranty, it didn't cost anything.
The bad news is that it looks like there may be another problem. On the way out of the store the battery was indicating 1% so I quickly got it on the charger in the car. Driving home, about 10 minutes later, I got a warning for battery temperature. Thinking the low battery may just be taking a charge and getting hot from that, I turned the car A/C on full, took the back cover off, and kept the phone in the cold air.
In about two minutes, just feet from home, I noticed the display was off. Faintly I could see the battery charge symbol that shows when the phone is powered down and charging, but the backlight was off and I couldn't see if there was any color or animation to it.
As soon as I shut the car off and the power quit, that faint display disappeared, full black, dead. Now it seems it is behaving exactly the same. I haven't fiddled with it much, holding out hope of hopes it can be started and maybe recovered.
Could calibrating the battery at the wrong time have caused something like this? Do batteries have a safety lockout if they overheat? To be fair, I was running an intensive app at the time, Waze GPS. Maybe the battery didn't keep up and the phone decided it was too low and shut off. I will post back after letting it sit, cool, hopefully charge, and see what comes of it.
My phone is behaving exactly the way you describe too. A couple of days with Revolt 1.1, and this is the only problem. I had my phone hooked to a lithium ion usb battery pack all day, and it showed "100%" while hooked up, but as soon as I disconnected the battery pack, the battery icon changed to red, then it refused to boot like the situation described in the Revolt 1.1 thread in Development. It also would not go into charge mode on the battery pack, but when I came home and hooked it to a genuine AC adapter and it went into power-off charge display. I'm going to give it a few hours on the charger before I attempt to boot it again, and I'll report back.
Still no luck. I haven't charged it too much yet for fear that it isn't charging properly. Seeing the new battery work for about 20 minutes yesterday lent me hope that if I figure out how to get a fresh battery in or just shell out for another new one, I can have a window of opportunity to change ROMs and see if that has anything to do with it.
This morning I got out my digital multimeter to measure the battery pos to neg and am getting nothing (unless you consider 0.01v something). I tested my old LG clamshell's bulging, old, and damaged 1000mAh battery and it reads 3.99v but couldn't keep my old phone up (lacks oomph now).
Comparing that battery to the Revo's, they have the same four contact pattern but different connection scheme which just stops contact when test fitting. After shaving down its casing on the bottom a little bit, it was just enough to make contact. Using four hands (yes, I am very talented ) to hold the phone, hold the test battery properly, and hold the power button, I was able to get the power-up vibration and the first LG splash screen. We lost it after that but that's likely due to the very weak test battery and/or losing contact while holding it in the Revo.
Since the spankin' brand-new battery is now reading zero, I'm left second guessing my decision of not shutting the phone down when I got the temperature warning. Maybe these batteries do have an internal protection to prevent runaway failure and it too is trash. I have no experience with this otherwise so this is just guesswork.
I'm contemplating rigging the new battery into my old LG phone to see if it can tell it "all clear" and charge it up. I'll post anything I find out here. Any other suggestions are highly welcome. Still, last ditch, I'm pretty certain I can set up another ROM to flash on the SD ahead of time, get another battery, and Clockwork to test another ROM if it's the phone or ROM. I may have had 20 minutes of uptime on the last battery.
I think I've gotten to the bottom of my problem. It's a syndrome of things that I have hopefully untangled.
First off, I had been messing with Power Manager, and wanted the phone to not sleep or timeout the display when plugged into both AC and USB. I figured that would help when I'm plugged into the computer, but it was probably a bad choice.
Yesterday I was out on a boat, which probably put me into a weak signal area, causing the phone to expend extra energy staying locked on a tower. In addition, I had plugged it into the external USB power pack, and thrown them in a bag together. This did two very bad things: 1) It allowed heat to build up from both the charging and 2) it invoked the "USB powered" Power Manager profile which kept the display active which created both additional heat AND crazy battery drain.
Here's what I think happened:
1. The battery overheated
2. The USB battery pack couldn't charge as fast as the display and radio could suck it out -- so five hours in that mode BOTH drained the internal battery AND tapped into about 30% of the external battery pack.
3. The USB battery pack will not provide enough initial juice to restart a flat-dead, overheated phone, or the firmware "knows" it is hooked to USB and refuses to start the phone -- for some bizarre reason.
So, I think my phone demonstrated normal behavior for a flat-dead, overheated phone, and hooking it up to AC brought it right back to life -- after about 5 hours of continuous charging. The battery also got very warm during charging -- more than I recall feeling ever in the past.
I'm hoping there is nothing that software power management could have done to physically damage the battery, but I assume Verizon would claim it could -- as part of the reason they forbid system modifications, and therefore withdraw their warranty if you modify.
At this point I think I have dodge a bullet, and my phone is fine -- other than a few of the quirks others are seeing in Revolt 1.1 (Phone occasionally FC, etc.)
Good to hear your phone is fine. Seems like mine is too as posted above but time will tell. I got the Revo battery set up and charging on my old phone. It seems to be connected well enough. The phone complained the first try that there was no battery but my second try has it displaying that it is charging. The battery isn't warm at all but maybe that's due to a different charging rate for the old phone's 1000mAh battery vs. the Revo's 1500mAh. Or, it really isn't connected perfectly. We shall see.
Success. The surrogate charge setup got the Revo battery up to 4.11v and indicated charge complete. The Revo completed a full boot on the battery and appeared normal.
Not normal was quick heating (still unsure of the cause). Going straight to Battery Calibrator, it indicated 68% and around 3.7v and falling. Not wanting to push my luck, I shut it down. Battery now read 3.9v. Not bad but it sure seems to be getting drained quickly which would explain all the heat. Going to set up later and see if I can get it back to stock and see if the behavior persists.
I don't know how to fix any of your issues but I would like to say thanks for giving such a detailed display of what you've been doing to fix this problem should anyone else run into this issue. Also, That picture in you one post: That is the most jerry rigged set-up to charge a phone I have ever seen in my life and I love it. Good luck getting your phone working I hope everything turns out for the best.
You're welcome. It was a bit of impromptu brainstorming with some fellow tinkerers that helped come up with a way to test charge the battery. Having it come back to life
I've come to a conclusion. Somehow, I think when the battery overheats, it must internally soft protect itself. Charging it on the old phone reset it and then it worked again on the Revo. Why the old phone works and not the Revo, unsure. That would at least explain why the battery tested at zero volts before the charging rig.
After many starts and stops on my Revo now, I have found that what was heating up first was the casing of the phone. I'm guessing heat conduction of heat from the processor as it wasn't the display which was set to minimum brightness (those are the main heat sources, right?). Looking into Settings > About > Battery Stats, it only showed Android System at 98%. It seems like the processor got locked into some some high power continuous use situation which survived reboots.
The battery gets hot later due to the high consumption and proximity to the hot casing (processor), especially with the back on. Withing 1-2 minutes from start, the sides of the phone would be quite warm and after 5 minutes becomes concerning. It seems that's why the battery was never able to get to 100%, but instead its percentage was always falling, phone over consuming greater than charge rate.
With the processor going full tilt, battery cover on, protective case on phone, sitting in a warm car without A/C, that got the battery too hot within 20 minutes. It was a similar situation with the prior battery when the problem cropped up.
I don't know what the cause of this predicament was in the first place however. The phone was plain stock, then rooted, later flashed Revolt 1.0, then Revolt 1.1. Between Titanium Backup, RevoToolkit for CWM, basically nothing unusual, I have no idea how it happened. Maybe I should have done Decrap first since I've read others doing such. Thinking back to my first post/thread, I had a boot issue and only had rooted, Titanium, and RevoToolkit, no ROMs yet.
And, don't get me wrong. I'm not placing blame anywhere, just documenting my "progress." There was a time I was on Revolt where it wasn't behaving this way. I am left without a solid conclusion as to the cause.
How to avoid the battery drain?
I had a similar situation, downgraded and then installed Revolt 1.3. Can't say what did it, but the battery got hot and drained so far it would even start charging.
I got the battery charged on the old phone, and the new one, with Revolt 1.3 is working. But I'm not sure how to make sure the overheating/draining problem doesn't occur again. After 10 minutes the phone is starting to get hot again, battery is down to 57%. With the phone on or off, it does not charge the battery, even with an AC wall charger. With the phone on, it indicates 57% charge, with the phone off, the battery icon just sits at red, no charging is happening. I erased the battery stats in ClockworkMod, but is there anything else to do? Any other ideas?
It sounds like Haxid had it happen and he got back to LG stock and unrooted, all good.
http://forum.xda-developers.com/showthread.php?t=1233668
Mine happened again this time totally dead battery. Trying to get some charge in it now to boot and remove cwm so I can take it to verizon.
Decrap 1.0 rom this time w/ CWM
I do not believe it is the rom. It has to be an app or hardware.
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Bait-Fish said:
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Click to expand...
Click to collapse
No my phone is actually super stable it just is sucking battery like its candy. Been off charger only 1 hour right now and its down to 83%. It has to be an app doing it but I have no idea which one. The phone shows 64% battery usage by android system.
When mine was hogging battery, same here. All I saw was Android process.
just to add my 2 cents here. I noticed my phone draining like crazy, I tried everything, then I changed the battery. boom. everything is now stable. I'm going to try to exchange that battery I think its my drain and reboot culprit.
No technical skills here. I have a "regular" Nook HD Plus with no modifications. Version 2.2.1
Started w/weird charging ... It would say battery full when on the charger, then as soon as taken off charger would say a random % charge like 15%.
Then had some overheating problems - if running on battery it would heat up and turn off then restart - If I ran it with the charger connected, had no problems.
Now, not taking a charge. The indicator light turns amber for a few seconds then goes to green. Says discharging even though plugged in.
Have tried shutting it down but that had no effect.
Found a replacement battery online w/tools to open the unit up and replace but am not sure if it's the battery, the charging cable, or if the unit heating up damaged a board or something. Currently have about 15% charge left, and can access programs and games w/no problem.
So what's your educated guess ... if I replace the battery will that fix it, or should it be retired.
If you think it should be retired, a recommendation for a new tablet would be appreciated.
Mostly use it for reading, games, Facebook - things like that.
Appreciate the help.
What would you lose by opening it up and replacing the battery if you're considering retiring it?
I had a problem where it would restart whenever the speaker was on the highest setting and it made a loud noise. I simply opened it up, checked it out, and somehow that fixed it. Maybe it was a short circuit? I don't know, but I didn't have anything to lose by it. I recently also thought my battery was bad as the HD plus didn't turn on but all I had to do was keep trying a hard reset. You could also put a custom rom on it. That helped with my overheating issues and usually does the same with Android phones that I have had.
Cool to see someone else from Miami here too.
It MAY be the battery, but I would strongly suggest backing apps up, then going into the stock recovery, and doing a full factory reset from there.
Have a Note 8 that was draining the battery real fast all the sudden. It's on android 9. I would charge it to 100, let it sit with screen off and in about 30min. it was down 59%. This kept happening. One day it went down to 0% and didn't charge anymore. So I changed the battery. It did the same thing. Depleted too fast. When it went down to 0%, again phone would not turn on nor charge again. This is what I have gone thru so far with this phone:
Replaced the battery 3 times.
Replaced the charging port flex cable
Tried several Samsung chargers
Wipe data/factory reset X2
Wiped cache X2
No apps are on the phone.
Even with all that the batteries still drain quickly. If they go to 0%, phone won't charge again. Phone will not turn on and charge until I put a new battery replacement in it-only for it to drain fast.
The only thin I have not replaced was the logic board. Could this be a logic board issue or software issue?
prahsper said:
Have a Note 8 that was draining the battery real fast all the sudden. It's on android 9. I would charge it to 100, let it sit with screen off and in about 30min. it was down 59%. This kept happening. One day it went down to 0% and didn't charge anymore. So I changed the battery. It did the same thing. Depleted too fast. When it went down to 0%, again phone would not turn on nor charge again. This is what I have gone thru so far with this phone:
Replaced the battery 3 times.
Replaced the charging port flex cable
Tried several Samsung chargers
Wipe data/factory reset X2
Wiped cache X2
No apps are on the phone.
Even with all that the batteries still drain quickly. If they go to 0%, phone won't charge again. Phone will not turn on and charge until I put a new battery replacement in it-only for it to drain fast.
The only thin I have not replaced was the logic board. Could this be a logic board issue or software issue?
Click to expand...
Click to collapse
To rule out it being a software/firmware problem update it if you can or if you can't update then downgrade but stay with the same bootloader version.. If it does it after doing that then it's 100 percent a hardware problem.
Both my wife and I have Verizon Note 8s. We received the June patch a few days ago and have experienced SEVERE battery drain. In the battery usage stats there is no application that seems to be causing the drain. We've not had these phones very long (maybe 16-18 mo) and believe this is absolutely related to the June 2020 security update. I'm not sure if this issue is specific to the Verizon version of the patch or if this would affect more Note 8s. I'm just trying to find proof that it was the update.
I am a tech so yes I did the repair myself. Just looking for a second opinion on this. I bought the batteries from amazon and had a good condition battery from an old Note 8 repair leftover.
However, I cannot do anything more as far as testing because I need to purchase another battery. That is the only way to get the phone back on because like I mentioned once the battery drains out phone doesn't charge anymore unless I put a new battery in. As long as I don't let the phone drain to 0% I can keep using it and charging it.
But for now to do any of the tests mentioned here I would need to get another battery first.
prahsper said:
I am a tech so yes I did the repair myself. Just looking for a second opinion on this. I bought the batteries from amazon and had a good condition battery from an old Note 8 repair leftover.
However, I cannot do anything more as far as testing because I need to purchase another battery. That is the only way to get the phone back on because like I mentioned once the battery drains out phone doesn't charge anymore unless I put a new battery in. As long as I don't let the phone drain to 0% I can keep using it and charging it.
But for now to do any of the tests mentioned here I would need to get another battery first.
Click to expand...
Click to collapse
Some of the phones that would drain to 0 wouldn't charge again and Samsung was replacing the batteries in those ones but some people have been able to get them to charge again so if you have a wireless charger put the phone on BOTH the wireless charger AND the wired cable charger and leave it over night and it may or may not work but you have nothing to lose so..
Well I have found the issue and only issue. It was the logic board. The power IC chip is bad. After purchasing and connecting the new logic board everything on this note 8 is working perfectly. Battery charges, holds its charge like it supposed to. Battery drain is gone. And I can let the battery drain to 0% and charge it up again with no problem. So eventually, when I get the time, I will replace the power IC on the bad board. But for now, all is good.
Thanks to you all for your assistance.
prahsper said:
Phone will not turn on and charge until I put a new battery replacement in it-only for it to drain fast.
Click to expand...
Click to collapse
What exactly do you mean when you say "put a new battery replacement in"? You mean that you have opened the phone and put in new batteries? How did you put it back together? It is supposed to be sealed, and many things can go wrong after opening the enclosure.
Master_yoda said:
What exactly do you mean when you say "put a new battery replacement in"? You mean that you have opened the phone and put in new batteries? How did you put it back together? It is supposed to be sealed, and many things can go wrong after opening the enclosure.
Click to expand...
Click to collapse
Instead of for someone typing out the answer to that just go to YouTube and search for Samsung Galaxy Note 8 battery replacement and you'll see the entire process!
MrMike2182 said:
Instead of for someone typing out the answer to that just go to YouTube and search for Samsung Galaxy Note 8 battery replacement and you'll see the entire process!
Click to expand...
Click to collapse
My comment was not so much about the process, but about the result. Or shall I say consequences of the action? If one opens the seal, replaces the battery (not just once, but several times) and then complains about the battery not working normally is in my opinion a bit cheeky.