Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
yap, I have two gnexs both have had this problem.
I can get a screenshot with vol-down + power
but the screen is totally black.
Yeah I've had this screen of death issue too. I've been trying forever to diagnose what is causing the problem. It happens on any kernel including stock. I factory reset, flashed stock images, everything.
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
i not have restaert using apk franco updater and set :good:
The sudden battery drop is normal when you pull out the battery. Basically, the phone loses it's calibration on the battery capacity. And that " auto charge" is your phone slowly trying to get a better estimate of your phone battery capacity.
Sent from my Galaxy Nexus using Tapatalk 2
I believe that SODs are a common problem faced by many on 4.2 i personally havn't faced it yet =] running arhd with ak kernel
I was able to reproduce this using Velis Auto Brightness https://play.google.com/store/apps/...SwxLDEsImNvbS52ZWxpcy5hdXRvLmJyaWdodG5lc3MiXQ
After messing with the brightness it wents black screen.
I'm sure this has to do with the autobrigtness!
Best regards
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
klobkelosh said:
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
Click to expand...
Click to collapse
I think you just helped me pin it on animation off. I have had the black screen happen to me 3 times in the 3 days that I disabled animations (stock rooted ROM, developer options). I kept trying to find an app that caused it but the animation off matches the start of my problem.
EDIT: Well, animation off isn't the cause since I just had another black screen.
simms22 said:
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
Click to expand...
Click to collapse
Totally agree with you!happened to me many times too,especially when crashing after tweaking\benchmarking.
My Galaxy Nexus is running CM11 since day one and before that I was running PlayfulGod's Unnofficial port.
Every couple of days the phone simply crashes/hangs. It happened at night few hours after I last touched it, it happened during the day while simply laying at sleep in the desk and even while using it. The phone simply stops responding.
If it crashes while sleeping the phone appears to be dead, while active, the screen will remain frozen until the battery is dead (guessing... didn't really wait until the battery ran out).
Removing the battery and re-inserting and the phone will work, typically showing a big hit on the battery level.
I assume there's some CPU activity going on because I can feel the area near the camera warmer (not hot) than the rest.
I opened this topic to follow the issue raised on this post:
VuDuCuRSe said:
I just had the same problem! (I'm using the official Jan05)
It happened a few times on the last days. The phone seems to be off, but in complete dark I can see a bit of back light. Once happened during sleep and it even registered screen on activity (weird).
Never really tried connecting it to the computer, always removed the battery right away. =(
Click to expand...
Click to collapse
At least amrs seems to be having this issue.
amrs said:
My phone had a hang yesterday and again today. Running 0104 nightly. Just a black screen with a faint backlight, no reaction to buttons or anything.
Today I managed to get some info finally as to what happens. Turns out the phone didn't crash, I was able to get in via adb, so dmesg and logcat attached. Also I noticed from the process list system_server was a zombie. As I understand it, system_server is a fairly major part of Android so that's probably a problem...
Click to expand...
Click to collapse
Maybe with more reports we may understand what is causing this crashes.
VuDuCuRSe said:
My Galaxy Nexus is running CM11 since day one and before that I was running PlayfulGod's Unnofficial port.
At least amrs seems to be having this issue.
Click to expand...
Click to collapse
I didn't have any problems for a few days, after installing 0112 nightly. Turns out I didn't have any deep sleep either according to Better Battery Stats. A reboot fixed that but then I got a crash quickly again. I realized weather info was odd in the lock screen so locked and tried to unlock and nothing. Couldn't even get in with adb shell this time.
So I guess deep sleep has something to do with this. I've been using the hotplug CPU governor most recently but I think this happened with interactive too.
I'm all stock... kernel, CPU/GPU settings and so on... so I guess that it shouldn't be related to that.
Do you know of any good debugging app to eventually save some sort of evidence of the crash?
I tried plugging the USB cable on the last crash but the computer/adb didn't detect the phone.
Hello, I have recently re-flashed to stock on my E980, I am running the phone on the AIO network as an unlocked device (although it would run fine if it were ATT locked as well).
I am looking for ideas to why I am having a problem. So it goes like this...
The phone randomly turns off. It seems to happen in my pocket, not on the desk. When I go to turn it back on, it is unresponsive unless I pull the battery or plug it into AC. If I plug it in before pulling the battery, it says not enough power to turn on. If I pull the Battery and turn it on the homescreen loads and I have plenty of battery in the upper corner (75% or so). When the homescreen loads, its fine for awhile, then back to step 1.
I am currently unrooted (just flashed back using LG flash tools) however the problem was first noted on a rooted stock ROM. I installed CM11 thinking that maybe it was something in the ROM that was initally causing this and a new ROM was in store for me... Did it on CM 11 too. Then I reflashed to Stock and I am still having this issue.
I have tried most everything and my thought is that the battery is either toast or not being recognized properly. I do not have immediate access to a different battery, but I think i can get my hands on one... If I replace it, I'm thinking it would take me an hour or so to replicate the problem and I still wouldn't be certain that was the culprit.
Anyone have any ideas, or things I could try out before trying to source a test battery, or does this not sound like a battery issue?
hey
i got the same problem
gonna have new battery soon and see if its from this
the sell man told me its could be the ROM
gonna try the modem of e980H
I've been having a similar problem as you, and actually had the device factory reset while in my pocket. Going to try and find a battery around my area, and hoping it fixes the problem. Have you noticed any heating issues as well before the reboot?
yea its getting so heated and drain the battery so fast
i think cos its trying to find single i had that problem with rezound too
i think there connection when its got heat -> drain the battey > and also kills the battery after few times
Hello there
I've installed cm11 on my Xperia ZL and I love it. But I've noticed some problems with this Rom. My phone gets very hot after a short time of using it. My phone is throughout on 55C even now, although I have just opened chrome. This hight Temperature also let my battery drain very fast. I woke up today with 100% and now, after 5 hours I've got just 36% . I'm sure that can't be normal, maybe you have a solution for me
And I've got a second question. I wanted to install the lightning Kernel in hope that the temperature gets normal. I've installed the Kernel with success but my phone randomly reboots itself. Do you have maybe also a solution for that?
Actually I am back on cm11 Kernel.
So I hope for help
And sorry for my English, I'm German
1st, on my opinion, cm11 is full of lag... For example the notification bar.... Sorry, i can't find any solution bcs i'm not on your rom
2nd, Well, it's normal to random reboot... I got no random reboot whe i'm using AICP, and CandyKat..
But sadly, i lost my phone sorry i can't find any solution
Hello everyone,
I recently decided to unlock my bootloader and install pixel experience latest ROM (android 10 plus) and after few hiccups I successfully installed it. Everything went great until I realized when the battery reaches 25-20% the phone starts registering random touches whenever I touch it. For example, let's say I'm typing "to" it will become "toooo" or "too sfo fo" and other random touches when I'm swiping or anything. What's mind-boggling is the moment I plug in the charger the problem disappears until the battery reaches 20-ish% again!
I tried playing with battery settings like adaptive battery and battery saver but to no avail.
Thanks for any help