Hi,
I was looking at google for my problem quite a while now, but didnt find anything related to my problem.
I was using a stock 4.1.2 on my phone until this morning, when i decided to try the omnirom 4.4.2 nightly.
When I was trying to load my battery with the phone turned off, the normal charging picture of the battery getting loaded was there for about some seconds and after that theres only a black and white battery with a questionmark in the middle that jumps from the top to the bottom of the display.
Has anyone ever seen this issue?
I was charging it earlier with the same screen, but the battery was definitely getting charged, but it was drained like really quickly from 50%-0% in like 1-2h with surfing etc.
Thanks in advance.
Edit:
I just tried starting it while it was charging.
First the black/white battery with ? came visible, then after some seconds the regular battery charging animation was shown for 1-2 seconds and then the display turned off again.
I can only start the S2 while its not plugged to the usb cable.
I have the same issue on newest omni from 15.12.13.
Wysłane z mojego GT-I9100 przy użyciu Tapatalka
Yes, this issue happened with me as well today and after that the phone won't boot.
It would just stay on the samsung boot logo.
I finally had to do a clean install through recovery.
I read on infected's thread that it's a known bug.
Did it work after reinstalling?
After installjng the New njghtly the logo atleast doesnt jump around anymore.
apologix said:
Did it work after reinstalling?
After installjng the New njghtly the logo atleast doesnt jump around anymore.
Click to expand...
Click to collapse
Yes it worked.
First I tried a system format but that didn't work then I had to do a data format and that worked.
It seems like you guys are having a bad experience on omni.
It has not happened to me, the battery will charge despite the white outlined question mark battery icon. It will also boot even during this stage.
what build are you using? is ART on?
mine (working)
4.4.2-20131216 built by infected
art enabled
PA gapps mini modular
It has to do with kernel or something. I had that chargingscreen too but it was just normal charging without problem
Sent from my GT-I9100 using Tapatalk
Related
yesterday the battery of my s3 was very low (around 2%) and i went to sleep without charging it. When i woke up after about 4 hours or so the phone was dead. I plugged it to wall charger but nothing changed i mean there was no battery sign or LED light. I thought the battery is completely drained so i left it there for about 15 min. When i checked again there was still nothing. I tried to turn in on but no response, unplugged the charger took out the battery then put it in , still no response. so i just left it there to charge for half about half an hour. Then i tried to turn it on again but still nothing. I tried recovery mode but no response. then i tried download mode and it did got to download mode. Now i thought it was OK so i restarted the phone but again it wont respond (Black Screen). I tried the download mode again(wall charger was plugged in the whole time). The phone did go to download mode but the screen started to Flicker and when i restarted it the boot screen(I-9300) turned up(still a little flickerish). and then it stuck there for a while. Then it went black. Again i left it to charge for about another half an hour. Now when i tried to turn it on, recovery mode or download mode Nothing happened, there was no response.
Then i started reading different threads on internet but couldnt seem to find anyone else with similar problem. Btw i checked the charger on Note and it was charging fine. then i tried to charge my s3 through laptop and the battery sign appeared and phone started to charge. I turned it after a while and it turned on Ok.
My phone is rooted , custom rom -Omega 39 with Custom Kernel Yank555 and Philz Recovery v4
Now my question is, Is there something wrong with my set? i mean the non responsive state and screen flickering. Should i get it checked or was it something that just sort of happens. Has anybody else faced a similar problem?. what can i do to avoid it in the future.
*Sorry for such a long post, its my first time. and i read about the S3 Sudden Death and now i am freaking out!..
genius5151 said:
yesterday the battery of my s3 was very low (around 2%) and i went to sleep without charging it. When i woke up after about 4 hours or so the phone was dead. I plugged it to wall charger but nothing changed i mean there was no battery sign or LED light. I thought the battery is completely drained so i left it there for about 15 min. When i checked again there was still nothing. I tried to turn in on but no response, unplugged the charger took out the battery then put it in , still no response. so i just left it there to charge for half about half an hour. Then i tried to turn it on again but still nothing. I tried recovery mode but no response. then i tried download mode and it did got to download mode. Now i thought it was OK so i restarted the phone but again it wont respond (Black Screen). I tried the download mode again(wall charger was plugged in the whole time). The phone did go to download mode but the screen started to Flicker and when i restarted it the boot screen(I-9300) turned up(still a little flickerish). and then it stuck there for a while. Then it went black. Again i left it to charge for about another half an hour. Now when i tried to turn it on, recovery mode or download mode Nothing happened, there was no response.
Then i started reading different threads on internet but couldnt seem to find anyone else with similar problem. Btw i checked the charger on Note and it was charging fine. then i tried to charge my s3 through laptop and it the battery sign appeared and phone started to charge. I turned it after a while and it turned on Ok.
My phone is rooted , custom rom -Omega 39 with Custom Kernel Yank555 and Philz Recovery v4
Now my question is, Is there something wrong with my set? i mean the non responsive state and screen flickering. Should i get it checked or was it something that just sort of happens. Has anybody else faced a similar problem?. what can i do to avoid it in the future
*Sorry for such a long post, its my first time.
Click to expand...
Click to collapse
I know this sounds silly but its not in "hardsleep" as some people would call it, where the phone is idle for too long and basically shuts its self down? Or it could be the sudden death issue associated with the s3. This probably isn't much help but its a suggestion, I've never come across this before
Sent from my Nexus 7 using xda app-developers app
samkent6 said:
I know this sounds silly but its not in "hardsleep" as some people would call it, where the phone is idle for too long and basically shuts its self down? Or it could be the sudden death issue associated with the s3. This probably isn't much help but its a suggestion, I've never come across this before
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I certainly hope its not a sudden death issue..:crying:
Try a different charger and cable. The s3 ones are notoriously crap.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
corrsea said:
Try a different charger and cable. The s3 ones are notoriously crap.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
Click to expand...
Click to collapse
I disagree.... No trouble with my stock charger came with the phone...
Sent from my GT-I9300 using xda premium
mustang2012 said:
I disagree.... No trouble with my stock charger came with the phone...
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It's been a known issue since the S3 was released. You've been lucky
http://forum.xda-developers.com/showthread.php?t=1727540
[Q] Galaxy S3 charging problem?
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
Try another battery first .
jje
Hi guys,
Yesterday, I have encountered a strange problem with my S3. I was using CM 12- Beta 1. I had a strange bug with charging. Unless I enable unstable charging power, the charging rate falls down to 100mA. So, I have used @JustArchi's ArchiKernel ( @Moster2's build ) for LP. I have used kernels like Archi Kernel, Boeffla Kernel with unstable charging power enabled since past few months and had no problems previously.
I, then kept my phone for charging and when I saw it after 5-10 min, a charging animation with 0% battery shown up and the device got hot. I took off the charger and tried to switch on but it didn't work. I'm only able to switch on the device when it is connected to charger. But, it got stuck at Samsung logo. I have quickly entered the download mode and flashed a stock rom via odin.
I'm trying to switch on while charger is connected but the phone keeps on switching off at Samsung logo or even before the appearance of Samsung logo. When I left it for charging, the same thing started happening. Charging animation shows up and suddenly it becomes like a dead phone and restarts again to show up charging animation. Once, I was able to get past the boot screen to Samsung's lock screen but it switched off within fraction of seconds. What could be the problem? Is this an end to my S3? Please help me to find out the problem.
chvenkatf said:
Hi guys,
Yesterday, I have encountered a strange problem with my S3. I was using CM 12- Beta 1. I had a strange bug with charging. Unless I didn't enable unstable charging power, the charging rate is falls down to 100mA. So, I have used @JustArchi's ArchiKernel (@Moster version) for LP. I'm using this kernel with unstable charging power enabled since past few months and I have no problems previously.
I, then kept my phone for charging and when I saw it after 5-10 min, a charging animation with 0% battery shown up and the device got hot. I took off the charger and tried to switch on but it didn't work. I'm only able to switch on the device when it is connected to charger. But, it got stuck at Samsung logo. I have quickly entered the download mode and flashed a stock rom via odin.
I'm trying to switch on while charger is connected but the phone keeps on switching off at Samsung logo or even before the appearance of Samsung logo. When I left it for charging, the same thing started happening. Charging animation shows up and suddenly it becomes like a dead phone and restarts again to show up charging animation. Once, I was able to get past the boot screen to Samsung's lock screen but it switched off within fraction of seconds. What could be the problem? Is this an end to my S3? Please help me to find out the problem.
Click to expand...
Click to collapse
You need battery replacement.
JustArchi said:
You need battery replacement.
Click to expand...
Click to collapse
Thank you Archi. Is it because I have enabled unstable charging power?
chvenkatf said:
Thank you Archi. Is it because I have enabled unstable charging power?
Click to expand...
Click to collapse
Can't tell you. It may be that, or your battery simply ended it's life. Nobody will assure you that unstable charging is secure, moreover, under certain circumstances it may NOT be secure.
Hi All,
I wanted to turn my tablet on this afternoon, and it did.
Plugged it right in the wall power socket, but after my Cyanogenmod logo, my tablet says it is empty and turns off...
I have charged it now for 2 hours, but still switching off...
I have flashed different roms, including the stock rom, but nothing helped.
Does someone has something to repair this, or is it just a dead battery?
I hope to hear something soon.
Greetings,
Rik
Bump
FYI: The TWRP recovery mode works.
But it says CPU: 0C (zero degrees Celsius).
I can flash any rom, except the stock one...
I can't boot further than my lockscreen, then it says something about the battery is empty, and it turns off.
This keeps cycling until I stop trying to boot it...
Please help me!
Bump
Nobody with a Mediapad that can help me???
Bump
Nobody with a Mediapad that can help me???
Hi,
i have exaclty the same issue - did you manage ot get it working again?
taeblov said:
Hi,
i have exaclty the same issue - did you manage ot get it working again?
Click to expand...
Click to collapse
No, until now my tablet is still stuck in that loop.
Therefore a BUMP!
Some new information for you..
I bought a new battery, swapped it with the original one - still the same.
I can update the system via sd card, by starting the tablet and pressing all buttons together.
Flashing works fine, it boots until i see the android beginng menu (with language selection etc..) and then it turns off.
The only thing i can see from then on is the red battery symbol, showing low battery..
taeblov said:
Some new information for you..
I bought a new battery, swapped it with the original one - still the same.
I can update the system via sd card, by starting the tablet and pressing all buttons together.
Flashing works fine, it boots until i see the android beginng menu (with language selection etc..) and then it turns off.
The only thing i can see from then on is the red battery symbol, showing low battery..
Click to expand...
Click to collapse
Damn that the new battery didn't work.
I have got the same problem as you...
You do not have found an other solution??
I hope someone can resolve this problem... :crying:
Make sure the battery plug is connected correctly. After changing battery I had to reopen the pad twice because battery stayed at 0%. It is a bad plug, maybe it can already get loose because your tablet fell of the table.
Also look at the manufacture date of your "new" battery. Mine was from 2011 !!! Surprisingly it works, but yours could be bought dead.
Hi everyone.
I've just installed the last build of Dorimanx/Gsstudios kernel Here, and the first thing which I've noted is that when the phone is turned off and under recharge, the battery animation is missing. The screen is completely dark. This is very annoying, since I cannot see the percentage of charge. Do you know if this is normal or if there is a workaround to put the battery charge animation in its place?
Many thanks in advance...
I've forgot to say that I've installed the Dorimanx's kernel on the latest release of the official CM12.1 nightly.
No answers? Am I the only one who has this problem?
Isn't there a white battery logo when charging when phone is off? If not, this will need to be investigated further. Have you tried reflashing the kernel?
The white logo appear regularly at the beginning of the charge, but when it disappear, there isn't any way to show it again. Pushing any button doesn't have any effect. I've flashed the kernel a couple of times just after the flashing of a Cm12 nightly, but the behavior of the logo is always the same.
However, the kernel is great. The phone works very smoothly and some freezing problems seem resolved after its installation.
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.