Related
Anyone come across this? I put it on standby last night after reading a bit of my book on it, and it had around 50% power remaining. This morning, it was totally unresponsive; pressing the power button does nothing at all. I've charged it for 12 hours in the meantime.
I've done the following all with and without the power attached:
- Pressed and held power for 15 seconds through to a minute
- Pressed and held volume up with power to attempt to get into recovery for up to a minute
- Pressed and held volume down with powerfor up to a minute
- Pressed and held power while touching screen (read that one off another forum)
I guess potentially it could be on and in a crashed state and unresponsive to the power, so maybe in a weeks time when it runs out of juice, I'll be able to charge it and power it back up, but in the meantime, I'd welcome suggestions.
A few weeks ago I updated it to the official ICS build that was released, but did the update myself rather than using KIES, as KIES didn't even recognise my Tab's firmware original version. It's been absolutely fine before the update, and since. I only mention it because I've read about the Samsung build of ICS being prone to self bricking itself, but I couldn't determine what the symptoms of this vulnerability were.
Thanks for any help offered,
Will
did you try connecting USB cable and plugging it into your PC? did u get any activity? can ADB recognize your tab?
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Had the same problem while on holidays. Once the battery goes below a certain level, you won't be able to charge it through USB any more. Instead you need to use the wall charger.
I think it's bad enough that the 7.7 doesn't have a micro USB port, but things like that are just stupid and Samsung made a big mistake here. It don't think it's the same with the newer tablets though. It's also not possible to just buy cables or chargers for this strange Samsung port, so when you forget your wall charger at home at some point you won't be able to use your tablet any more.
As long as you charge with the USB cable early enough, you can avoid it though.
A few months ago I experienced the same thing, the Tab just wouldn't turn on anymore.
I tried all there is without any luck.
Contacted amazon and they replaced it with a new one in less than 48 hours.
So far not Problems with the new device.
I have the P6800 and this morning I took it off charge. Put it into standby and only used it for about 20 mins then left in standby all day. It had about 95% remaining when I did so.
Picked it up this evening and the lower left area of the screen was warm and it would not switch on. Didn't think of the ADB idea but will try this next time but I had to reset it and when it powered on tonight after the reset, it was down to 15%. Within about 2 mins of checking stuff it was down to 3%.
Something is running when it is in standby but as I can't switch it on I can't check with BetterBatteryStats or CPUState to know what is wrong.
It does this every day. I am tempted to do a factory reset and reinstall only limited software.
Dave...
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Cluey said:
I see this thread is a little old but this has just happened to my P6810 too. A pity nobody reported back what the end result was.
My device had at least 95% battery last night but today I can't get it to respond at all, I've tried the wall charger and still nothing.
Anything else someone could suggest for me?
Edit. I tried getting anything from it connected to my PC but it couldn't find a device there. However I then tried it on the wall charger again and now get a blue battery icon, quite big, with a five step animation indicating that it is charging.
No idea how it went flat as the battery on this lasts a long time assuming the screen isn't on. When it boots properly I'll have a look at what the most recent apps I installed were as it has only done this once. Before this it has been perfect for the three weeks I've had it.
Click to expand...
Click to collapse
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
TeeeJaay said:
This is the infamous Sleep-Of-Death issue that is randomly experienced by myself and other users here, usually happens when WiFi bugs out due to weak signal
Click to expand...
Click to collapse
hhmmm, interesting.
I was having trouble with wifi just before this happened. Both my GS2 and this have been claiming to connect to my wifi but aren't actually getting an IP address from it.
I can't remember if it was last night or the night before but I manually set an IP address, the signal strength is fine as my abode isn't very big.
After it has recharged I'll have a poke and see what I can find, thanks for the reply.
So my device seems to be working fine again. It had gone SO flat that the date and time were incorrect!
After I could power it on I had a look at Better Battery Stats and nothing looked wrong so I have no idea what happened. None of the apps I'd installed the day before it played up had long wakelocks and weren't running when I turned it off.
For reference they were:
My Tracks
MyTrails
Google Earth
AndSMB
I'd turned both of the GPS tracking devices off before I turned it off for the night.
It hasn't played up since but it hasn't been long so I'll see what happens.
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
A similar thing happens to me every once in awhile. The way i check to make sure everything alright is to see if it boots into download mode. I just leave it plugged in for a couple hours and it eventually comes back on.
someth1ng said:
Yeah, the sleep of death is incredibly annoying. Honestly, the GTab 7.7 is a **** device. Samsung made way too many mistakes and won't do anything to fix it.
Click to expand...
Click to collapse
this is why my 7.7 is the last tablet/phone from Samsung i'll never trust them they are just bombarding the market with new devices and leaving the old ones to dust
^thats what I thought too but that gs4 is really tempting. I've heard worse about HTC in that regard anyways so that why I'm not going with the one.
Finally.. i bought Sony xperia Z.
I'll sell my galaxy tab 7.7. I.m very disappointed with samsung.
Sent From XPERIA Z
kishd said:
I think your tab just ran out of juice and the battery's protection circuit has kicked in. Try taking it to an electronic shop and plugging in different chargers preferably one with an output more than 2.1 amps to kickstart the charging. Plug it in and wait till the charging animation starts.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Unbelievable! ... this trick still works ... thank you very much for you help ...
^^ yo, this 'trickle charge' trick did NOT work on my (long) dead P6800... any other suggestions??
Quite strange because my Samsung GT-P6800 tablet was fully charged, it went completely blank dark as if it was off. To my amazement, SMS keeps dropping and calls kept coming in. Yet it is still as blank as though the tab was off. I pressed the power button and the volume up bottom for it to reboot. It rebooted without the screen coming up. It has been blank for two days now. What could be the cause? And what possible solution can be given?
Update 14/09/2012
Ok, I don't think what I had in mind helped. On 13th, I had multiple shutdown while trying to use cameras and today had multiple shutdown while on the phone to someone.
Think I will try doing something with Firmware next, now have a feel it might be the cause. I have no idea what is wrong, so just going to give with anything really. Will report back soon.
Update: 13/09/2012
After a complete drain the first time, by booting into recovery and bootloader (just want to remind everyone that this is because I can't make my phone boot). Then I left it on charging for the whole night, and I did this through wall charger NOT USB. I think I read it somewhere that they recommended this when calibrating your battery. Then the next day got 1 random shutdown, then I used it until it is completed drain again. Then followed by another full charge using wall charger. Today I have been using it for 6 hours and 21 minutes, haven't had a single problem. I don't know how not doing this would cause the phone to shutdown, but doing what I did seems to be working so far. I can actually rely on it for something now, say important phone calls.
Here was my reply to elvisypi:
Just to answer your question, it would random shutdown (not so much reboot) at anytime, at any battery percentage. I could do be doing anything, using any app, sometimes when I am not even using the phone.
I don't think it's a hardware/battery/ROM/kernel problem, I tried to say that it is a combined problem caused by flashing a phone too many times maybe or too often in a period of time. Also I was just about to update saying that calibrate battery does help. I had no reboot so far and this is only the second full charge and full drain I did.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Original post 11/09/2012
After reading kushXmaster's post (click here) about how to add an object to help the battery stay in position (or get better connection), I found evidence that my issue was different. Before anyone ask, yes I have tried kushXmaster's idea, and no it did not work for me.
Ok, this is what I found. I had this problem not only with my current phone (htc sensation) but also with my previous phone (htc desire). So now thinking about it, it can't be the hardware problem. Cos the same problem happening to 2 different phones is pretty unlikely, not impossible, but very unlikely. The other thing was that my phones (both) didn't do this at the start when it was new, and it has only been like this a few months later (since I rooted it). For those who already guessed, yes I believe it's the flashing phones which is messing it up. However I don't know the reason or understand what is wrong with the phone. I have tried wipe battery stats and calibration, nothing worked, the only thing I found was when I go back to Sense 4 roms the problem seems better, but it is still there.
The last and most important reason why I am don't think this is a battery or hardware problem, is that my phone boots into bootloader or recovery with no problem (no reboot or shutdown). But when i tell it to boot normally it decides it hates me and turns it self off.
I am currently experiencing this problem, my phone is in recovery and I am waiting for battery to drain completely. Then gonna do calibration from there, hopefully this will work. I will keep you guys updated. Also if anyone has suggestions please leave a comment, and also let me know if anyone else is in the same position, good luck!
If you want to drain your device battery faster or more nicer way put screen timeout to never and like this you can still use your phone normal and drain the battery aswell just a little tip
Sent From My Sexy Sensation.
shahkam said:
If you want to drain your device battery faster or more nicer way put screen timeout to never and like this you can still use your phone normal and drain the battery aswell just a little tip
Sent From My Sexy Sensation.
Click to expand...
Click to collapse
If I could get it to turn on then I have a lot of ways to drain it quickly, but like I said it won't boot without shutting down before I could do anything. I turn it on, and I see the lock screen then bam it is shut down again.
lavafire said:
If I could get it to turn on then I have a lot of ways to drain it quickly, but like I said it won't boot without shutting down before I could do anything. I turn it on, and I see the lock screen then bam it is shut down again.
Click to expand...
Click to collapse
Ohhh sorry didn't get that
Sent From My Sexy Sensation.
To drain battery.. switch on wifi and bluetooth.. thn use 3g for 20 mins.. u will drain compltly
Sent from my HTC Sensation using xda premium
lavafire said:
After reading kushXmaster's post (click here) about how to add an object to help the battery stay in position (or get better connection), I found evidence that my issue was different. Before anyone ask, yes I have tried kushXmaster's idea, and no it did not work for me.
Ok, this is what I found. I had this problem not only with my current phone (htc sensation) but also with my previous phone (htc desire). So now thinking about it, it can't be the hardware problem. Cos the same problem happening to 2 different phones is pretty unlikely, not impossible, but very unlikely. The other thing was that my phones (both) didn't do this at the start when it was new, and it has only been like this a few months later (since I rooted it). For those who already guessed, yes I believe it's the flashing phones which is messing it up. However I don't know the reason or understand what is wrong with the phone. I have tried wipe battery stats and calibration, nothing worked, the only thing I found was when I go back to Sense 4 roms the problem seems better, but it is still there.
The last and most important reason why I am don't think this is a battery or hardware problem, is that my phone boots into bootloader or recovery with no problem (no reboot or shutdown). But when i tell it to boot normally it decides it hates me and turns it self off.
I am currently experiencing this problem, my phone is in recovery and I am waiting for battery to drain completely. Then gonna do calibration from there, hopefully this will work. I will keep you guys updated. Also if anyone has suggestions please leave a comment, and also let me know if anyone else is in the same position, good luck!
Click to expand...
Click to collapse
If you get random reboots, shutdowns, than don't even bother to calibrate the battery. It has nothing to do with the calibration. Tell us more info, how do the reboots happen, how often, what are you doing when it happens, etc. It could be a kernel/ROM problem, charger, battery, hardware. Pls give us more detailed info
shahkam said:
Ohhh sorry didn't get that
Sent From My Sexy Sensation.
Click to expand...
Click to collapse
No problem, appreciate the help :good:
elvisypi said:
If you get random reboots, shutdowns, than don't even bother to calibrate the battery. It has nothing to do with the calibration. Tell us more info, how do the reboots happen, how often, what are you doing when it happens, etc. It could be a kernel/ROM problem, charger, battery, hardware. Pls give us more detailed info
Click to expand...
Click to collapse
Thanks for the tip, but tbh if i know all that I don't really need to be asking anyone. For example, if it is a ROM problem, i just change ROM. The problem is that I don't know the cause and it seems to be everything and anything, it will shut down at different length of time, sometimes when it just starts, others 30 seconds after boot has completed. I am not looking for a solution, I am more wondering what everyone else has experienced when they say they have random reboots or shutdown, because after tones of research no one has provided anything that fixes my problem.
Just to answer your question, it would random shutdown (not so much reboot) at anytime, at any battery percentage. I could do be doing anything, using any app, sometimes when I am not even using the phone.
I don't think it's a hardware/battery/ROM/kernel problem, I tried to say that it is a combined problem caused by flashing a phone too many times maybe or too often in a period of time. Also I was just about to update saying that calibrate battery does help. I had no reboot so far and this is only the second full charge and full drain I did.
I had a same reboot problem and tried the kushXmaster's trick with the business card and did not worked for me either, at the beginning…
There was no reboot or shutdown in bootloader mode in my device either. When I flashed new firmware and ROM the problem was gone, but only for few weeks. I tried multiple ROMs also, but always with the same result. This is why I was skeptic with the business card battery fix also.
But then I read kushXmaster's thread again and put an alu foil as shown by Shreyas Jani and pulled the ground pin as described by StuartTheFish. I still do not understand what happened, but my phone is working perfectly more than a month now, without restarts and shut downs. I do not know which solution helped (not sure if I placed a business card correctly before). But I do not want to experiment with this anymore. I did not even removed a battery cover since that time and I'm glad it is all working now.
Hope this helps.
prgab said:
I had a same reboot problem and tried the kushXmaster's trick with the business card and did not worked for me either, at the beginning…
There was no reboot or shutdown in bootloader mode in my device either. When I flashed new firmware and ROM the problem was gone, but only for few weeks. I tried multiple ROMs also, but always with the same result. This is why I was skeptic with the business card battery fix also.
But then I read kushXmaster's thread again and put an alu foil as shown by Shreyas Jani and pulled the ground pin as described by StuartTheFish. I still do not understand what happened, but my phone is working perfectly more than a month now, without restarts and shut downs. I do not know which solution helped (not sure if I placed a business card correctly before). But I do not want to experiment with this anymore. I did not even removed a battery cover since that time and I'm glad it is all working now.
Hope this helps.
Click to expand...
Click to collapse
I experienced exactly what you experienced, when i flash a new ROM it is ok for a while. Then just gets to the stage where it happens again. I also tried almost every single ROM I could find, only sense 4 seemed to help but still didn't solve this problem completely.
Thanks for the help, really useful. If what I am trying now doesn't work then what you suggested will definably be my next hope. Cheers!
Edit: I know what you mean, if it works that back cover is not coming off.
same as you
I experience now typically the same problem as yours.
Did changing firmware helped? And how to do this?
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
metal man007 said:
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
Click to expand...
Click to collapse
SOLUTION:
Turns out my phone was stuck in a "boot loop"
Followed Champdood's instructions:
http://forum.xda-developers.com/showthread.php?t=2144101
Thanks everyone.
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
RomanKasp said:
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
Click to expand...
Click to collapse
ICS may just have battery stats that don't work for your batteries. Try calibrating the battery:
http://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en
If I remember the instructions properly, install the app, charge to full (or half hour past full), open the app to press the button, run it dry, and charge it fully with it turned off (note the LED on mine turns green at the 90% mark, so leave it plugged in and off for about an hour past the time it turns green).
I found with the app, it takes forever to get that last 1% after using it, and it takes a while before dipping below it again, but it seems to be more accurate than CM thinking I had the stock battery installed (I have a couple Ankers now). Hope this helps.
Thank you but doesn't work
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
RomanKasp said:
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
Click to expand...
Click to collapse
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
joel.maxuel said:
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
Click to expand...
Click to collapse
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
RomanKasp said:
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
Click to expand...
Click to collapse
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
joel.maxuel said:
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
Click to expand...
Click to collapse
I tried everything, including wiping data/cache/Dalvik cache, then installing the file, I even tried to install the GApps too. Nothing seems to happen. It just gets stuck in the bootloop. When you first turn it on, it stops at "Starting apps", then if you reboot it, it stops working at CM logo (bootloop). I waited for 10 minutes or more, no result. Luckily, I did a full backup so I went back to CM 9. Seems like my phone is simply incompatible with this mod. No luck for me here .
Hi, i have an s6 (non edge), i do have it insured so not sure if i would be best trying to get it swapped or see how it goes?
I have had no problems up to now, been using it most of the day fine, the last time i looked at my phone was probaby about 30 mins before this happened and it had about 75% battery.
before i took my phone out my pocket and it was completely off, i kept pushing the power button in and getting no response at all, i plugged the phone into the mains and nothing happened, no charge light etc..
So i just left it connected to the mains with nothing happening for about 15 mins, then out the blue i pressed the power button in again and it come on, at it was starting i noticed it said android is updating an app (as it does when you have just installed a new fw) but this was only for 1 app by the looks, i hadn't installed anything new i can think of, not sure if thats related or not important?
Anyway my phone seems ok at the moment but now im not sure if i should just take it back the shop and get it changed seems i have it insured anyway, the phone is around 3 months old now.
Sorry, i am just editing this, i have just remembered one main point which i forgot i done earlier when reading that it can help your phone, i did go into dev options and i changed the 'limit background processes to 4' as i read this can help it, not sure if this was a bad idea?
Any advice?
Thanks
James
Possibly a defective battery.