Help.
My xda suddenly became slow, the backlight switched off, and flashes on/off every 15 seconds. When soft rebooting, it stays on the initial screen for sometimes, continuing to flash as before. The phone does not start, and the battery meter will not show how charged the battery is.
I have v1.2 rom, which i installed a last week. All has been working fine, and i havent really installed any apps since. It just did this by itself this morning.
Anyone experienced this? It could be i didnt manage to charge my battery last night, though it was in the charger. Is this what it does, when the battery is very low?
I fixed it, by doing a hard reset.
Its all working again. I can only imagine it was something in the v1.2 rom.
Anyone else experienced this?
Strange Thing,
same happend to my MDA today. Battery was Full 100%
Mda does the same then yours.
Bootloader says GSM error.
Then i did a cold boot an everything is fine again!
I changed nothing for 4 weeks, and i have only the official
upgrades in my MDA!
Did you phone up your provider to ask if they had any problems on their network?
Related
After flashing PAC rom (http://forum.xda-developers.com/showthread.php?t=1957299) I've started experiencing some problems on my phone.
At seemingly random times when I am using the phone the screen flickers a bit then goes black and dies. When I try to power it up again it shows the battery as having something like 1% left and the phone usually dies again pretty fast. It doesn't matter if I had a freshly charged phone or 50% left when this happens, it still most often shows as having 1% left after it dies and restarts. I have never experienced this kind of problem before.
Sometimes the battery shows up as a bit higher than 1% left but still a lot lower than it was before. Earlier today it came on again with 12% left. When this happens I am usually unable to unlock the SIM-card with my pin even though I am 100% sure i input the correct code - it just refuses to accept it and i have to let the phone "rest" or charge it or just pray to the old gods for a few minutes to get it to start again.
I've used a few custom roms and I haven't done anything strange lately with it (except flashing). I flashed the rom with CWM, I followed the instructions and it went through problem free, and I was able to use the rom and phone for a day before this problem showed.
So... Does anyone have any idea what the problem might be? Battery related? Hardware related? Software related? I just hope my phone will survive this so I don't have to buy a new one yet since I've grown fond of this one. I appreciate any and all help!
Try different battery with your phone to rule out battery related problem. try changing kernel...
Sent from my GT-I9100 using Tapatalk 2
Hello!
I have this problem with my s2.. I was browsing for my joy when suddenly the screen flashed couple times and my phone suddenly shut down (when battery was about 70%).
I already had this kind of problem but last time it was the battery (it swelled) but i replaced the battery and for a month or so everything was fine.
now with no warning it happened again!
I checked the battery its fine...
now when I boot my phone up it stays up for a minute or so and freeze or shutting down..
and also the signal icon shows that there's no signal!!
when its off and plugged to the charger its all fine looks like charging...
sometimes when it shows the samsung logo on boot I can see the the lights on the back button and menu button flickering and then shutting down.
I didnt download anything new in the past week..
did anyone here had this kind of problem? how can I fix it?
PLEASE help me I was at a job interview and they should call me today !! T_______T
David2404 said:
Hello!
I have this problem with my s2.. I was browsing for my joy when suddenly the screen flashed couple times and my phone suddenly shut down (when battery was about 70%).
I already had this kind of problem but last time it was the battery (it swelled) but i replaced the battery and for a month or so everything was fine.
now with no warning it happened again!
I checked the battery its fine...
now when I boot my phone up it stays up for a minute or so and freeze or shutting down..
and also the signal icon shows that there's no signal!!
when its off and plugged to the charger its all fine looks like charging...
sometimes when it shows the samsung logo on boot I can see the the lights on the back button and menu button flickering and then shutting down.
I didnt download anything new in the past week..
did anyone here had this kind of problem? how can I fix it?
PLEASE help me I was at a job interview and they should call me today !! T_______T
Click to expand...
Click to collapse
ROM?Kernel?Did you try Factory reset or flashing stock ROM?
Are you using a genuine s2 battery or it's just a generic one?
It's a generic, isn't it?
Sent from the little guy
I did hard reset, now running Samsung's original ROM and stock kernel..
the battery is original..
somehow everything is now fine.. but I don't think that this is a normal problem.. it really freaked me out today.. I wanna know if any one knows what its all about and how to prevent it from happening.. thank you very much
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
--yep mine too. I'm thinking it has to do with the heaying problem. Mine crashes and dies when there are many apps running/ wifi on with downloads while watching youtube., etc. another is when I recprd videos at 4k pr 720p for about 8-10 mins. My phone heats up real hard. I'll try resetting it and hopefully this fixes it. ps. Haven't done anything to my z5c yet. no unlocked bootloader, no root.,etc.
Same problem
I had the same problem
Device have charge (50,60,70 or more), show 0% and turn off.
Hardware problem maybe ???
any solution found?
hi,
I know it's been a long time you posted this but I'm currently facing that exact same problem.
Could you find any solution in the end?
Thanks
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
It looks like your battery is just dying. This was a common issue with Nexus 6p and other phones.
Resetting batterystats won't help... it doesen't have anything to do with it