Related
i tried installing the new Eb13 (froyo) alongside Clockword mod 3. power went out now my phone wont turn on go to recovery nor download!!! is my phone bricked beyond repair????
You can look at other forums about the same problem and a few tricks you can try. It can be something as simple as replacing the battery.
Sent from my SPH-D700 using XDA App
notsosmrtgeek said:
You can look at other forums about the same problem and a few tricks you can try. It can be something as simple as replacing the battery.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
no i have a spear battery and no dice!!! ill keep searching and thanks for the info!!! =)
Caballero777 said:
i tried installing the new Eb13 (froyo) alongside Clockword mod 3. power went out now my phone wont turn on go to recovery nor download!!! is my phone bricked beyond repair????
Click to expand...
Click to collapse
did the power go out while you were installing it? or did you try to flash a rom that was rfs not ext4? also my phone has a had time goint into download or recovery cuz ive done it so much the buttons are worn out i think. i have to hit it multiple times before it works. keep trying... but we may need more info as to what all happened to assist you further
fury15 said:
did the power go out while you were installing it? or did you try to flash a rom that was rfs not ext4? also my phone has a had time goint into download or recovery cuz ive done it so much the buttons are worn out i think. i have to hit it multiple times before it works. keep trying... but we may need more info as to what all happened to assist you further
Click to expand...
Click to collapse
yeah their is a picture of a cellphone and a computer with an exclamation point in the middle!!! i post it to download and the computer doesnt read it!!! =(
Yeah that happened to me before
Your phone got disconnected when using odin
Well it kinda of a hassle to get the computr to read it, and get it into download mode, but I can assure you your phone isn't bricked! just keep trying
Sent from my SPH-D700 using XDA Premium App
I had this problem before also, I fixed it by rebooting my PC, and then booting into download mode, and Odin back to stock. It did take a few tries though.
Caballero777 said:
i tried installing the new Eb13 (froyo) alongside Clockword mod 3. power went out now my phone wont turn on go to recovery nor download!!! is my phone bricked beyond repair????
Click to expand...
Click to collapse
I've had this before. You need to purge the power in your phone. Take battery out and hold down the power button a few times.
This will purge power and memory.
Then boot into download. # 1 and power and then odin.
Sent from my SPH-D700 using XDA App
castro08 said:
Yeah that happened to me before
Your phone got disconnected when using odin
Well it kinda of a hassle to get the computr to read it, and get it into download mode, but I can assure you your phone isn't bricked! just keep trying
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Odin is not working for me what so ever!! this is so frustrating!!! lol everytime i connect the usb without the download i get the update zip!!!
Caballero777 said:
Odin is not working for me what so ever!! this is so frustrating!!! lol everytime i connect the usb without the download i get the update zip!!!
Click to expand...
Click to collapse
Caballero. Pm me your number. I can call you.
Sent from my SPH-D700 using XDA App
zenvita said:
Caballero. Pm me your number. I can call you.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
thats the thing!!! this is my only phone! no relatives or anything!!! =( facebook is facebook.com/Caballero777
Try using different usb ports. After rebooting the computer. The pc will try to find ur phone again but if u get it to the download screen. Its just the matter of getting odin to work for you
Sent from my SPH-D700 using XDA App
I had my phone do the exact same thing (die during flash). What you can try doing is leaving your battery out overnight, and in the morning, plug the phone in to your computer/wall, then plug your battery in.
Really what you need is to get your battery charged. If worse comes to worse, you could go to a Sprint Store, and tell them your phone died and you don't have insurance, and ask them to charge your battery, OR if you know someone else with your phone you could swap.
zenvita said:
I've had this before. You need to purge the power in your phone. Take battery out and hold down the power button a few times.
This will purge power and memory.
Then boot into download. # 1 and power and then odin.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This is how I have delt with the same problem.. that and rebooting computer with phone still plugged in, with battery removed
I've Odin'd before and had the process freeze in the process and was forced to pull my battery in the middle. I got that same symbol described with the pc and the cell phone when trying to use the phone again after putting the battery back in. All I had to do was pull the battery again to get it back into download made.
Animas1020 said:
I've Odin'd before and had the process freeze in the process and was forced to pull my battery in the middle. I got that same symbol described with the pc and the cell phone when trying to use the phone again after putting the battery back in. All I had to do was pull the battery again to get it back into download made.
Click to expand...
Click to collapse
Yeah it happened to me like that before and i solved it that way, but this time my computer is not reading my phone!!! So odin doesnt work and when it does read it odin stops all process and shuts off!!! ='(
Caballero777 said:
Yeah it happened to me like that before and i solved it that way, but this time my computer is not reading my phone!!! So odin doesnt work and when it does read it odin stops all process and shuts off!!! ='(
Click to expand...
Click to collapse
How much is a bricked epic worth to you? Pm me with a price!
Sent from Bonsai 6
Top Nurse said:
How much is a bricked epic worth to you? Pm me with a price!
Sent from Bonsai 6
Click to expand...
Click to collapse
haha thats certainly an option!!!
Hi every one! Everything was ok with my GNote and for months with ics update. yesterday I tried to reboot it because the battery was empty after long time use. I connected the phone to the charger but nothing happens. I waited a few hours but nothing too. It does not pass to download mode and recovery mode too. I tried the battery on the GNote of my brother and it works and its battery does not help to boot up on my GNote. So the problem is on the phone. What is the solution please?
PS: i don't changed anything on the Gnote since Mounths
Thank you
awcabdou said:
Hi every one! Everything was ok with my GNote and for months with ics update. yesterday I tried to reboot it because the battery was empty after long time use. I connected the phone to the charger but nothing happens. I waited a few hours but nothing too. It does not pass to download mode and recovery mode too. I tried the battery on the GNote of my brother and it works and its battery does not help to boot up on my GNote. So the problem is on the phone. What is the solution please?
PS: i don't changed anything on the Gnote since Mounths
Thank you
Click to expand...
Click to collapse
Just a long shot, but is it a faulty battery connection on your device.
have you tried to flash another gb or ics rom?
Im guessing you run on stock ics, you could be superbricked if you deleted a big file from your phone, deleting big files could trigger the eMMC brick command. Just guessing here so i could be wrong.
Sent from my GT-N7000 using xda app-developers app
SquirtingCherry said:
Im guessing you run on stock ics, you could be superbricked if you deleted a big file from your phone, deleting big files could trigger the eMMC brick command. Just guessing here so i could be wrong.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Wrong.
Seems to be battery connection problem from your tests as it was said before. If your warranty is not void..should go for SAV.
Sent from my GT-N7000 using xda premium
i'll send it to SAV Later. Thanks for all of you
Have you tried charging your battery in your brothers note, and then placing it in yours? If your phone boots, then its a faulty connector issue.
Sent from my GT-N7000 using xda premium
I tried it but no result
Sent from my GT-I9300 using Tapatalk 2
PoisonWolf said:
Wrong.
Click to expand...
Click to collapse
+1:thumbup:
Sent from my GT-N7000 using xda premium
PoisonWolf said:
Wrong.
Click to expand...
Click to collapse
+100
Sent from my GT-N7000 using Tapatalk 2
awcabdou said:
It does not pass to download mode and recovery mode too.
Click to expand...
Click to collapse
If it was a faulty battery connection, as seems to be a consensus here, than your phone wouldn't boot at all; yet you say that you can reach Download and Recovery mode.
It's something else.
No i cant reach any mode
Sent from my GT-I9300 using Tapatalk 2
PoisonWolf said:
Wrong.
Click to expand...
Click to collapse
Yup
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
PsyOr said:
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
Click to expand...
Click to collapse
Thanks for tour reply, but if i do that and of doesnt help, will i lose waranty?
Sent from my Nexus 4 using XDA Premium 4 mobile app
soylukral said:
Thanks for tour reply, but if i do that and of doesnt help, will i lose waranty?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, as long as they didn't know you opened it.
Are you sure the phone doesn't turn on or is it a black screen. Did you try holding Power + Volume Down to get into the fastboot menu? From there you can use fastboot to flash recovery, which is the recommended way.
eksasol said:
No, as long as they didn't know you opened it.
Are you sure the phone doesn't turn on or is it a black screen. Did you try holding Power + Volume Down to get into the fastboot menu? From there you can use fastboot to flash recovery, which is the recommended way.
Click to expand...
Click to collapse
Nope it doesnt turn on at all, also treid volume down and power button, still no succes. But like i said if i put the charger on it and try to power on, the red light goes on. The phone was at 35% when i flashed the twrp update
Sent from my Nexus 4 using XDA Premium 4 mobile app
Just give it a few hours of charge, it will be back.
Mercado_Negro said:
Just give it a few hours of charge, it will be back.
Click to expand...
Click to collapse
Thanks i did, i will wait till in the morning. But i was wondering, how Can it be the battery. Because i had still 35% of power.
Sent from my Nexus 4 using XDA Premium 4 mobile app
soylukral said:
Thanks i did, i will wait till in the morning. But i was wondering, how Can it be the battery. Because i had still 35% of power.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It happens. Battery stats in our device isn't too accurate. I've had that a couple of times. In fact, when my Nexus 7 2012 runs out of battery and I don't charge it for 4 hours or so it always needs half an hour to turn on.
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
soylukral said:
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
soylukral said:
Guys need help here...
I just updated twrp from 2.6.0.0 to 2.6.3.0 with the zip file via recovery. After flashing, the recovery asked me to fix root. After that the phone turned off en wont turn on anymore. Any One knows why and how i can fix this?? If i plug in the charger and try to turn on the device, the red led goes on.
Please help!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
frankvcs said:
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:02 PM ----------
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
---------- Post added at 07:03 PM ---------- Previous post was at 07:03 PM ----------
Just let charge it completely. And then try to turn it on again. I experienced the same thing with twrp 2.6. asking me to fix the root part and then I did not boot up again.I just uninstalled it afterward. I rather use CWM. I like it better. Might be a battery issue, but CWM have not given me any warning with root fix.
Just my personal experience. :good:
Click to expand...
Click to collapse
Waited about 8 hours, but still nothing. Btw i did connect it to my PC, and it says searching drivers for QHSUSB_DLOAD. I think i have a hardbrick here. Can i solve this myself, or do i have to send it for repair?
Sent from my Nexus 4 using XDA Premium 4 mobile app
PsyOr said:
The "magic" way - open the back cover (2 screws), disconnect the battery flex cable, reconnect it, close the back cover and....viola.
Click to expand...
Click to collapse
I had a similar issue, I ran antutu and my phone went into a coma, no button combos were working and when I plugged in my phone I got the flashing red death light. But like PsyOr says just take of the back undo the two little screw's the hold the battery connector on, pop it off the put it back on and you're good. Worked like a charm for me.
Sent From a Slim Sexy Nexy
Actually seems like a hard brick. http://forum.xda-developers.com/showthread.php?t=2347060 try this.
And don't forgot to thank that guy, it's a brilliant post
No, its not a hardbrick, its the red light issues which is well known. Just remove the battery and reinsert it: http://forum.xda-developers.com/showthread.php?t=2250454
A hardbrick is when a piece of hardware stop working completely and needs to be physically replaced, I don't know why people like to use that term for anything.
eksasol said:
No, its not a hardbrick, its the red light issues which is if en't it ll known. Just remove the battery and reinsert it: http://forum.xda-developers.com/showthread.php?t=2250454
A hardbrick is when a piece of hardware stop working completely and needs to be physically replaced, I don't know why people like to use that term for anything.
Click to expand...
Click to collapse
That doesn't explain why the pc is asking him to use drivers for download mode. If the phone really dint have enough battery shouldn't it have not connected to the pc.
Also the device will be hard bricked even if a wrong kernel/rom is flashed. But it can be unbricked by the above method.
Try the Nexus 4 toolkit. There are options to re-install everything up again. If you are sure that your battery is in good working order, then it might be software related issue. I don't think it's a hardware problem.
soylukral said:
Waited about 8 hours, but still nothing. Btw i did connect it to my PC, and it says searching drivers for QHSUSB_DLOAD. I think i have a hardbrick here. Can i solve this myself, or do i have to send it for repair?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are in download mode as indicated by your pc detecting the phone as QHUSB_DLOAD this is not the common battery fault.
You will likely get here by the bootloader failing
At this point you are more bricked than a general soft brick. But still not completely hard bricked.
There is a very useful thread in the general section about how to fully flash using download mode.
You can find the info below, note that there are a lot of steps involved so if your not confident. Rma is probably your best bet
http://forum.xda-developers.com/showthread.php?t=2347060
Sent from my Nexus 4 using xda app-developers app
Thanks guys for all of tour help. I wil try everything to bring the phone back. I will report if something happens. Btw what is RMA?
Sent from my Nexus 4 using XDA Premium 4 mobile app
RMA is return merchandize authorization.
sent from xda premium app
eksasol said:
RMA is return merchandize authorization.
sent from xda premium app
Click to expand...
Click to collapse
ok, and that is??
Guys, i did send it back to LG for repair. I want to thank all of you for the help you gave!!!
Sent from my Nexus 4 using XDA Premium 4 mobile app
One day, it randomly shuts down, and I haven't been able to turn it on ever since.
Actually, I can, but then it shuts down a few seconds after. I can't even get into recovery or download mode becasue of this.
It vibrates when I try to turn it on, if that matters.
I would try to put it in download mode, and then flash a stock fresh Rom, to see if it solves the problem.
Sent from my GT-I9300 using xda app-developers app
Drakenfall said:
I would try to put it in download mode, and then flash a stock fresh Rom, to see if it solves the problem.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
As stated above, it won't last long enough to go into download mode.
Well, when I start in download mode, it goes straight to there, even without battery but connected to usb for example.
It should allow to do it, how do you try to go to download mode?
Sent from my GT-I9300 using xda app-developers app
You need a JIG to start it, have a look here http://forum.xda-developers.com/showthread.php?t=1767763
pham818 said:
One day, it randomly shuts down, and I haven't been able to turn it on ever since.
Actually, I can, but then it shuts down a few seconds after. I can't even get into recovery or download mode becasue of this.
It vibrates when I try to turn it on, if that matters.
Click to expand...
Click to collapse
Is your phone an I9300 ??
I think your eMMC just died on you.
If you're in any luck it's just your battery failing. Borrow one from a friend and give it a try. My dad's gnexus was in the very same situation, turns out his battery was malfunctioning. A 3€ cheapo new one off ebay and all is well again.
earthman5678 said:
I think your eMMC just died on you.
Click to expand...
Click to collapse
What is that?
And I have tried a friend's working battery, it's the same thing.
JJEgan said:
Is your phone an I9300 ??
Click to expand...
Click to collapse
It's a T-Mobile one.
I had a similar issue. My power button was stuck once pressed and therefore the boot did not get past the Samsung screen. Rebooted before it got to recovery or download. Fixed it with some oil
pham818 said:
What is that?
Click to expand...
Click to collapse
It's called "Sudden Death Syndrome" (or SDS), but it only affects some I9300's with 16GB of internal memory.
UrbanDrawer said:
It's called "Sudden Death Syndrome" (or SDS), but it only affects some I9300's with 16GB of internal memory.
Click to expand...
Click to collapse
Only 19300s and not other variants right?
pham818 said:
Only 19300s and not other variants right?
Click to expand...
Click to collapse
Maybe I9305, I'm not 100% sure.
UrbanDrawer said:
Maybe I9305, I'm not 100% sure.
Click to expand...
Click to collapse
alright thanks!
TMOBILE I9300 International MODEL or a different model suplied by TMobile ?
Actual model is critical to advise wrong model and you may brick your phone .
Sent from my GT-N8010 using XDA Premium 4 mobile app
Been this way past two days.
any ideas?
What kernel and what ROM you running? Also any new apps, battery managers, downloads, etc out of the ordinary?
Sent from my SM-N900T using Tapatalk
Airplane mode
Wait 1m
Power off
Pull battery
Wait 1m
Reinsert battery
Boot recovery (no normal boot in between ! )
Clear cache
Reboot
-----
Also disable location services in google setting app
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Killberty said:
Airplane mode
Wait 1m
Power off
Pull battery
Wait 1m
Reinsert battery
Boot recovery (no normal boot in between ! )
Clear cache
Reboot
-----
Also disable location services in google setting app
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Click to expand...
Click to collapse
Is this a permanent fix of some kind?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
---------- Post added at 07:48 AM ---------- Previous post was at 07:48 AM ----------
KarimSalloum said:
Been this way past two days.
any ideas?
Click to expand...
Click to collapse
Get bbs app or wakelock detector in play store, will tell u the problem
For me, yes it is a permanent fix
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Battery Life after MJ7 firmware has been TERRIBLE! Simple!
KarimSalloum said:
Been this way past two days.
any ideas?
Click to expand...
Click to collapse
You can try many things, also the remove battery if you want to do that, its a firmware fault, I even tryed running total stock for some days after full recovery, it comes back. Only fix i have so far is restart the phone a few times untill it works again, then it can work for few hours or sometimes a day. resetting cache moving battery etc. shouldn't help at all. atleast I dont see the logic in removing the battery if you wipe cache...? Someone please explain what els you achieve!
Yeah I'm having the same " android os" wakelock since the latest mj7 update and it's killing the battery! Reboots didn't help much, I'll try the advice above for clearing cache and if it works
Sent from my SM-N9005 using XDA Premium 4 mobile app
I have tried many many things, nothing has worked so far. It just has to be the ROM.
This helped me:
http://forum.xda-developers.com/showpost.php?p=47213318&postcount=71
Never unplugging the charger while screen off and no problem since... Please try and report!
onyxogen said:
This helped me:
http://forum.xda-developers.com/showpost.php?p=47213318&postcount=71
Never unplugging the charger while screen off and no problem since... Please try and report!
Click to expand...
Click to collapse
Have u tried it yourself?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Goodm7sn said:
Have u tried it yourself?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I tried it. like I said, it helped me!
onyxogen said:
This helped me:
http://forum.xda-developers.com/showpost.php?p=47213318&postcount=71
Never unplugging the charger while screen off and no problem since... Please try and report!
Click to expand...
Click to collapse
For how long have it worked for you? I tried this thing aswel, still ended in a no deep sleep state.. :/
What @onyxogen said makes sense now. I know that on one or 2 occasions, my battery lasted normally and i think i might have started using it right out of the socket. I mean start using it after battery full while still plugged in then disconnect later. But i did it without knowing then... I will try for real now and know for sure.
stanley08 said:
What @onyxogen said makes sense now. I know that on one or 2 occasions, my battery lasted normally and i think i might have started using it right out of the socket. I mean start using it after battery full while still plugged in then disconnect later. But i did it without knowing then... I will try for real now and know for sure.
Click to expand...
Click to collapse
Well, it doesn't hurt to try. I'll give it a go tomorrow morning
Sent from my SAMSUNG-SM-N900A using xda app-developers app
For me the Problem was a fake S-View Cover with fake Chip. Removing it, stops the Android OS drain for me.
Rivendel said:
For me the Problem was a fake S-View Cover with fake Chip. Removing it, stops the Android OS drain for me.
Click to expand...
Click to collapse
Mate I'm pretty sure that's not the main issue for me... As I never used cover
slimslim said:
Well, it doesn't hurt to try. I'll give it a go tomorrow morning
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
I did. Doesn't work
I posted this in many posts so far, because I am ****ing mad about no quick optimization for this "so called flagship"! The no deep sleep problem is ****ing huge, they must install something into the kernel that can regonize what apps have multiple uses of alarm_manager or something!
In the end, this problem is nothing we can do anything about. As it is samsung/android that have made the problem. I even tried this restart phone and unplug from charger while screen are on... My phone since 6hours ago have had 2m and 37s deep sleep..
I think it is so poor, that we pay so much for a phone and then the only thing samsung do is just put their trust in having android kitkat fixing it, instead of being proactive....
zipn said:
For how long have it worked for you? I tried this thing aswel, still ended in a no deep sleep state.. :/
Click to expand...
Click to collapse
This would only work if it would be the only reason that stops your phone from entering deep sleep of course, so it's far from sure that it works.
For me it works since 2 weeks, but I have to repeat it every time I disconnect. Sometimes I have longer periods of no deep sleep but if I just plug it out while charging than the bug appears every time if I remember correctly.
It's an partly known android bug, since 4.1 I believe.
Note that you have to use the display for a while before unplugging!
onyxogen said:
This would only work if it would be the only reason that stops your phone from entering deep sleep of course, so it's far from sure that it works.
For me it works since 2 weeks, but I have to repeat it every time I disconnect. Sometimes I have longer periods of no deep sleep but if I just plug it out while charging than the bug appears every time if I remember correctly.
It's an partly known android bug, since 4.1 I believe.
Note that you have to use the display for a while before unplugging!
Click to expand...
Click to collapse
Hmm gotta try use my phone for scrolling forums and mail in the morning then.. didnt know that I would have to use it for some time first.. It actually sounds like that could be the problem, if you say its a well known bug since 4.1... because everyday i do get it fixed after a few resets and then it works rest of the day... untill the next day when its been charged..