Is contant battery pull-out harmful to the phone in anyway? - Fascinate Q&A, Help & Troubleshooting

I'm not sure if this is exactly the cause, but I feel my phone gets warmer these days, especially around the USB charger port at the top left.. Is constant battery pull out (to install things via odin) in any way responsible for this? Like say, once in every couple of days? How often do you guys pull out your batteries? Has anyone faced an issue with this practice?

Not sure as to harm, but I'd guess eventually, seeing as components wil be in a low voltage state the instant the battery is pulled, unless Samsung inserted a cutoff circuit (questionable). This will, sooner or later, cause one or two components to fail and things will only get worse from there. This is the reason the phone turns itself off before the battery dies completely.
When the phone is off, however, you should be fine.
If you are pulling the battery because of phone lockups, be aware you can force a hard reboot by holding up-vol/power for ten seconds (until the SAMSUNG logo appears. This will always reset the phone, no matter how locked it is. A side benefit of this is forcing CWM or download mode by altering the volume button pressing. For example, vol-down/power for ten seconds will bring you into download mode, where vol-up+vol-down/power for ten seconds will force CWM to come up.

Related

battery problem

so every once in a while, i'd say every 4 or 5 days... i'll take my phone off the charger and start my day like normal. but on these days, (sometimes i notice and do a hard reset before all this happens) the upper half of the phone will get really warm and even if i do absolutely nothing on my phone, my battery will drain from full to dead in 3-4 hours.
has anyone else noticed this? i'm thinking it may be some sort of cpu cycle leak or some sort of infinite loop some background driver might get itself into.
its pretty annoying if i dont catch it right away and an hour after i unplug my phone while i'm at work to take my phone out of my pocket and have it over half battery gone already.
sheep_duck said:
so every once in a while, i'd say every 4 or 5 days... i'll take my phone off the charger and start my day like normal. but on these days, (sometimes i notice and do a hard reset before all this happens) the upper half of the phone will get really warm and even if i do absolutely nothing on my phone, my battery will drain from full to dead in 3-4 hours.
has anyone else noticed this? i'm thinking it may be some sort of cpu cycle leak or some sort of infinite loop some background driver might get itself into.
its pretty annoying if i dont catch it right away and an hour after i unplug my phone while i'm at work to take my phone out of my pocket and have it over half battery gone already.
Click to expand...
Click to collapse
I have noticed the 'staying warm after charging sometimes' phenomenon....I also sometimes leave it charging all night but it doesn't seem to charge, even though the light is on. I think this is somehow connected to the wonky power button behavior...I get a green light on full charge sometime....i've never seen it turned green while powered off.....sometimes it won't turn on while plugged in, sometimes I need to do a battery pull, sometimes the SD card too, sometimes I need to press the power button a million times or hold it extra extra long....sometimes the charging light doesn't come on and it does charge, sometimes the light comes on and it doesn't...sometimes it gets really hot after charging and doesn't cool down after sitting idle....I usually just shut it off for a minute and turn it back on...somehow.
This is definitely one of my pet peeves with this phone...I also think this is linked to some phones never turning back on again, corrupted bootloader/recovery after a 'fastboot' shut-down or hot restart...
I'm diggin' the phone, don't get me wrong, but....I can't wait for the nPrime...
yeah, but it's less so the problem of it getting warm (pre or post charging) and moreso that it will start heating up a lot and you can tell that something is running the battery down in the background, the only way to stop this is to do a battery pull restart.
has anyone had similar issues with their phone going from full battery to dead in a few hours because of a hidden bugged process or something similar?
bump 10 char
I had that happen after tuning airplane mode off then back on. But that's itt
Sent from my HTC Evo 3D.
This happened to me this morning, first time and it was very weird. I've left it charging overnight per usual and this morning when I woke up and unplugged it, it had only 10% battery left. I tried charging it in my car on my way to work and have it plugged in to my computer USB now. I disabled a bunch of stuff as shown on this thread:
http://forum.xda-developers.com/showthread.php?t=1141221
And it's now starting to charge.
I did however just update to showdown rom and had setcpu on 1.7 conservative. It still should have charged but I'm guessing a stuck process/bug drew all the power last night.

Samsung Galaxy S2 - Wont turn on.

Well back again with new problem.
Have just had my phone back after it was repaired only a week ago by samsung; they repaired the software, replaced screen, battery and USB port. Now my unrooted phone, with only usual apps, has again failed on me. Was on the home screen, nothing else running, and it turned itself of. After a minute turned itself back on, held at the Logo, and then turned of again. Now it wont turn on what so ever. Its not got hot, its not got cold, its not been in a room with steam, its been sat in a decent zenus case, in a house with radiators etc on.
I seem rather unlucky with phones, my old Nokia 5800 went into repair 6 times, until I gave up and brought a £10 phone, that I'm having to use again now.
I have tried charging, despite the fact it was still 62% full when the phone went of. I don't do extreme sports with the thing, I barely use the phone, yet it still keeps breaking. Disappointed, because the phones pretty decent, but starting to feel like I don't do well with them.
Rant over.
Update: Just tried after 30 minutes to turn it on. It turned on for about 15 seconds, got into the unlock screen, unlocked, went to the menu screen and it turned itself of. I put the charger straight in, was charged up to 59% anyway, but thought maybe might be battery... But doesn't seem to be.
Wont turn on/Charge again. The phone is fine temp.
What you're describing could be a phone with a drained battery.
So check the battery with a voltmeter and check the charger. One (or both if you're really unlucky) of them could be busted.
Edit: You can check the charger by plugging your phone to your PC and charging it from there. If it works then it's the charger if it doesn't then check the battery.
Is all else fails return the phone to a service center.
Try this-
Take out the battery, then press and hold the ON button for 7-10 seconds (the longer the better). Reinsert the battery, then press ON button to start it. This is a soft reset, and wipes the temporary memory and empties all remaining power in the circuits. This helps on many phones and even laptops that won't start properly or show anything on screen.
If this does not work, try the next step. Again, do as above. But after inserting the battery, do not turn the phone on, but press and hold the ON button and the HOME button at the same time for 7-10 seconds. This is a hard reset, and works best if done after a soft reset. Just be sure the battery has at least some juice in it and isn't empty. If possible, try with another battery if this does not work.
I read earlier about a similar problem and it turned out to be a loose fitting battery. They put some foam or something at the bottom of the battery so that it would stay tight and retain contact.
You could probably test for this by removing the back cover and pushing the battery upwards while powering on.
Sent from my GT-I9100T
Thank you very much MichaelAmrs. you saved my Galaxy S2
Awesome Advice
Thanks MichaelAmrs
I have had some serious trouble with my GS2 not working and the latest has been it not turning on. I stuck my battery in the freezer and then did what you suggested and it worked like a charm. Instead of getting it to boot I tried putting it in Download mode and was able to install the Stock ROM on it and hopefully now it will last. But if nothing else at least it is turning on again.
Good luck.

[Q] SGH-i777 - From Shoebox to Brick

Hey Folks,
I have a Samsung Galaxy SII (SGH-i777) that I used a couple of years ago. It was my first Android phone and I loved it very much (until corporate made me an iSheep).
The phone was retired to a shoe box for the last 1+ years and I recently dug it up so I could get it set up for my little bro who somehow recently fell on his phone with it in his pocket and shattered the screen (don't ask... I don't get it either).
Anyways long story short -- the phone sat idle for a long time, when I pulled it out it wouldn't boot up at all. Assumed that the battery had discharged so I plugged it in to see if it would start up. The battery logo would intermittently flash on the screen and show a drained battery logo but even letting the phone sit for a day did not provide me any results.
Fast forward 3-6 months. Today I replaced the charging board thinking that there was some issue with the USB connector on the phone that was preventing it from getting power. Once that was done I discovered that I was able to get the phone to boot into Odin mode. Great! No boot, no recovery, but download mode seemed to be better than nothing.
I have tried, in vain, to flash stock firmware to this phone via Odin, and even though all indicators point to it being successful, once I finish the Samsung logo comes up on the screen, goes off and that's it. I can see the 4 LEDs on the buttons at the bottom of the phone flash every 5 seconds as well as a faint flicker on the screen staggered between the LED flashes.
Looking for any further suggestions as to what I may be able to try. I have searched various sources on XDA and other sources but I haven't quite found anything that matches my exact symptoms.
Furthermore, I can't be sure what Kernel/ROM I was last running on this phone. Maybe Siyah kernel, maybe CM 10,1 with Flux kernel. Idk.
Any input is appreciated!
Seems I should mention this other detail --
With the battery in, I cannot get into download mode -- it just states 'Low Battery!! Can't Download!!" This is presumably due to the fact that the battery is completely discharged -- maybe incapable of holding a charge but perhaps this is indicative of a more serious hardware failure.
I'd guess the battery is completely shot.
I bought a replacement battery from here: http://www.ebay.com/itm/111014533334?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
No problems with it.
bleggy said:
I'd guess the battery is completely shot.
I bought a replacement battery from here: http://www.ebay.com/itm/111014533334?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
No problems with it.
Click to expand...
Click to collapse
Very likely --
Since you got me to shift focus here, a quick search is telling me that it won't boot without a battery due to a feedback circuit. This would explain the ability to go into download mode but the lack of boot / flashing LEDs I guess.
Can someone confirm?
If the phone was working normally when it was put away, I would expect it to be working normally when it was pulled it back out. Your story is a little confusing, but did you ever try booting the phone with a fully charged battery? In the circumstances you describe, that would be the first logical trouble shooting step. And if you haven't tried that, then it is still the next logical trouble shooting step. Also, you can't assume that the original battery that you left in the phone is still able to hold a charge. It still may be good, but you can't assume that for testing purposes. Incidentally, the battery should have been pulled from the phone before it was put away.
I do not get any indication that the original battery is actually charging. Charging icon just flashes on the screen briefly in between LED and screen flashes (again, presumably due to the battery being completely dead/incapable of holding a charge since I left it in the phone this entire time).
I guess I'll go ahead and buy another battery and see what happens.
It is my understanding then that this phone will not boot on the charger without battery due to a feedback circuit. Correct?
kleinschmizzy said:
I do not get any indication that the original battery is actually charging. Charging icon just flashes on the screen briefly in between LED and screen flashes (again, presumably due to the battery being completely dead/incapable of holding a charge since I left it in the phone this entire time).
I guess I'll go ahead and buy another battery and see what happens.
It is my understanding then that this phone will not boot on the charger without battery due to a feedback circuit. Correct?
Click to expand...
Click to collapse
Even if the battery is good, but fully discharged, it may not charge in the phone. You would have to have an external charger. Phones are not consistent, and many phones probably would charge a fully discharged battery, but I have seen a number of people report that a fully discharged battery would cause the exact same behavior as you report. If it were mine, I wouldn't throw the battery away yet.
If you know anyone with an I777, you could borrow their fully charged battery for a few minutes just to see if your phone will boot.
You are correct that the phone will not boot on the charger when the battery is out, although you should be able to successfully flash firmware through Odin with the battery out, and the computer supplying the power, but still, as far as I know, it will not boot after the flash without a working battery.
The battery was indeed at fault. Ordered a new one on Amazon, popped it in and voila -- we're up and running.
Thanks for the input guys! Much appreciated!

Cure for "phatom touches" problem

As many of us are aware, there is a issue that can occur with a Nook Tablet going crazy with phantom touches. Essentially it looks as if you are tapping on the screen when you are not. It usually happens very quickly, one minute ok, the next everything is getting tapped all over the screen. This can cause data loss as the device thinks you are touching the screen. For example a file you were working on may abort before saving as it thought you hit "close".
I have been bugged by this issue on and off. Some people replace batteries to fix the issue, and while that will fix it 99% of the time, there is an easier (and cheaper way).
The problem appears to be the newton loses battery calibration. There has been talk in the past of deleting the battery file via CWM or other Android app that deletes this file (or even doing it manually with a file browser app, which may need root access). This battery file is only data since the LAST time you charged the device. Not the calibration data. And this file is deleted automatically everytime you plug it in to charge.
How I fixed it
After a lot of research I found that many Android devices there often a way of recalibrating the battery charge system. The steps are:
1. If you get phantom touches hit the power button as fast as you can to put it to sleep ande prevent anything occurring you might not want (aka a file deleted you wanted to keep etc).
2. Charge the battery to full, until the green light is lit on the charge indicator located on the Nook Tablet charge cable
3. Unplug the device from the charger
4. Use the Nook Tablet for 20 minutes with a high drain app (aka watch a video)
5. Plug the Nook tablet back into the charger and wait until the light turns green again.
6. Repeat steps 2-5 several times. I would suggest 3 or 4.
7. See if you get phantom touches again when the Nook Tablet power gets low. If you do try steps 2-5 again several more times.
In my experience after a few times of this, I no longer had the phantom touches issue.
Why it happens
I am not sure all the details as to why, but one time I do know for a fact that one time it happened after I had the tablet on the charger with a full charge (I had not got around to unplugging it yet) when the power to my home failed. It came back on a few minutes later but that night when I was using the device I got phantom touches at about 50% power left. Which I never had before. After doing the above method it is working fine again even down below 15% power (which I never let it get that low normally).
I suspect that the power failure caused the charger system to recalibrate and since the battery was already at full, messed up the whole system. I also would NOT leave the Nook Tablet on a charger for long periods. If it sits at 100% for a long enough period it is possible for the battery to drop down a little and start charging again. This could start a recalibration again, bringing back the phantom touches issue.
I have not posted until now as I was not certain what fixed it before. If it was the charge to full, use for 20 minutes, then charge again method or turn it off then charge method worked. I tried several before and wasn't sure which one worked. Now I can say the put to sleep, charge, use, charge again method does work. But don't turn off the device then charge if you can help it. If the Nook tablet is powered all the way off (not sleep) doesn't seem to do a battery recalibrate. Or at least my best experience is to plug it in while in sleep mode, charge to full (green light), use for 20 minutes, and then charge again.
Sorry if this has been posted before. But a quick search didn't reveal any hits.
UPDATE:
Upon further tests, often powering off the device fully (holding power for 30 seconds or pressing for 5 and saying yes to the popup to power off), then plugging it in, letting it turn on and charge to full will fix the problem as well.

Random shutdown issue after replacing battery - issue is still there after returning to original battery

A couple of days ago I replaced the battery on my Poco F1, because the phone is 2.5 years old and AccuBattery reckoned it was at 71% health. There were no issues with the phone, only that the battery life wasn’t as good as it once was (it was still running from 100% - 0% battery charge).
I bought the battery from AliExpress (this one to be precise) and the process of switching it out was easy and faultless, as far as I could tell.
The reassembled phone booted up fine and the new battery was at ~ 50% capacity. On the AliExpress listing it said to run the battery flat, which is what I did and it lasted quite a few hours - all good.
I then recharged the phone to full, as stated in the instructions. Regretfully, I interrupted the first recharge a couple of times by unplugging the phone for a few minutes each time. I'm telling you this for full disclosure - I'm unsure if this is likely to have caused the problem that I am now facing.
The fully recharged phone lasted a few hours and then shut itself down, whilst on ~ 70% battery I believe. This was the first time I realised there was a problem. The phone would not turn back on - holding down the power button and/or any combination of volume buttons did absolutely nothing. However, plugging the phone in caused the battery charging screen to appear instantly and subsequently, holding the power button whilst still plugged in would turn the phone on as normal. The phone would then boot up and battery percentage would be at ~70%, as it was when it shutdown (once booted, volume keys work fine). The phone would appear to charge as normal, but whenever I unplugged the phone, it would eventually shutdown on a high percentage after anything from a few seconds up to around an hour.
I thought I must have gotten a dodgy battery, so I took it out and put the original one back in. Now the old battery has all of the same symptoms as the new one – it won’t turn on unless plugged in and randomly shuts down after a period of time. If I manually turn the phone off when unplugged, it won’t turn back on unless it is plugged in. Also, a reboot just shuts it down.
I happened to have a spare charging port board, so I put that in to see if I’d fried something on there, but that hasn’t helped.
I’m tempted to reset the phone to stock (currently running Pixel Experience with TWRP installed) but am worried that it will brick the phone if it tries to reboot during the flashing process. Also, I believe that the fact I can’t force boot into fastboot with volume down/power buttons proves it is a hardware issue?
Any ideas are very welcome.
I think unless you have access to an EDL authorised account it's better to not flash MIUI at this stage. Risk of bricking the device...
07lema said:
A couple of days ago I replaced the battery on my Poco F1, because the phone is 2.5 years old and AccuBattery reckoned it was at 71% health. There were no issues with the phone, only that the battery life wasn’t as good as it once was (it was still running from 100% - 0% battery charge).
I bought the battery from AliExpress (this one to be precise) and the process of switching it out was easy and faultless, as far as I could tell.
The reassembled phone booted up fine and the new battery was at ~ 50% capacity. On the AliExpress listing it said to run the battery flat, which is what I did and it lasted quite a few hours - all good.
I then recharged the phone to full, as stated in the instructions. Regretfully, I interrupted the first recharge a couple of times by unplugging the phone for a few minutes each time. I'm telling you this for full disclosure - I'm unsure if this is likely to have caused the problem that I am now facing.
The fully recharged phone lasted a few hours and then shut itself down, whilst on ~ 70% battery I believe. This was the first time I realised there was a problem. The phone would not turn back on - holding down the power button and/or any combination of volume buttons did absolutely nothing. However, plugging the phone in caused the battery charging screen to appear instantly and subsequently, holding the power button whilst still plugged in would turn the phone on as normal. The phone would then boot up and battery percentage would be at ~70%, as it was when it shutdown (once booted, volume keys work fine). The phone would appear to charge as normal, but whenever I unplugged the phone, it would eventually shutdown on a high percentage after anything from a few seconds up to around an hour.
I thought I must have gotten a dodgy battery, so I took it out and put the original one back in. Now the old battery has all of the same symptoms as the new one – it won’t turn on unless plugged in and randomly shuts down after a period of time. If I manually turn the phone off when unplugged, it won’t turn back on unless it is plugged in. Also, a reboot just shuts it down.
I happened to have a spare charging port board, so I put that in to see if I’d fried something on there, but that hasn’t helped.
I’m tempted to reset the phone to stock (currently running Pixel Experience with TWRP installed) but am worried that it will brick the phone if it tries to reboot during the flashing process. Also, I believe that the fact I can’t force boot into fastboot with volume down/power buttons proves it is a hardware issue?
Any ideas are very welcome.
Click to expand...
Click to collapse
Exactly the problem I am going through. It's all started today. I am currently running stock MIUI. It keeps boot looping if I do not plug the charger. But once it's plugged, it will load up normal.
amn1987 said:
I think unless you have access to an EDL authorised account it's better to not flash MIUI at this stage. Risk of bricking the device...
Click to expand...
Click to collapse
I did flash stock MIUI in the end. Did not brick it, but also did not fix it. The phone now turns off immediately after being unplugged every time. I got myself a black Friday Poco X3 Pro so I'm now selling this phone for parts in UK
https://www.ebay.co.uk/itm/154819038771?mkevt=1&mkcid=16&mkrid=710-127635-2958-0
07lema said:
I did flash stock MIUI in the end. Did not brick it, but also did not fix it. The phone now turns off immediately after being unplugged every time. I got myself a black Friday Poco X3 Pro so I'm now selling this phone for parts in UK
https://www.ebay.co.uk/itm/154819038771?mkevt=1&mkcid=16&mkrid=710-127635-2958-0
Click to expand...
Click to collapse
It could be a buggy PMIC issue similar to https://forum.xda-developers.com/t/...android-11-0-vayu-bhima.4267263/post-85119331
Third-party batteries are mostly crap and probably the original battery is completely drained and the BMS isn't allowing it to be charged as a safety measure?
https://t.me/crDroidPoco/207293 Available in the EU.

Categories

Resources