Related
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.
Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
goentillsundown said:
Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
Click to expand...
Click to collapse
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
suljo94 said:
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
Click to expand...
Click to collapse
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
Looks like faulty battery, try change the battery with new one and see what will happend
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
Thant said:
Looks like faulty battery, try change the battery with new one and see what will happend
Click to expand...
Click to collapse
in the OP he said that he did that already
suljo94 said:
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
in the OP he said that he did that already
Click to expand...
Click to collapse
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Thant said:
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Click to expand...
Click to collapse
Surely if it's the light sensor it would be irrelevant if it was turned off or on though, same with the CPU. I'm going to spend some time getting power into it today, charge, then put in freezer to cool it, and repeat.
Once some power is into it I'll start with suggestions, one at a time, and get some screen shots up, and logs of the current drain.
Thanks for the help so far, would be good to get it going again, instead of having a $350 paper weight.
An update:
Changed the recovery from Philz recovery to an older CWM recovery program, and now possibly just through coincidence the battery isn't super heating to the point it needs to live in the freezer to charge.
I have restored to stock ROM, and have a couple of pictures of the battery history, which are neither here nor there, apologies as I wiped a lot of things off, including my WLD pictures from the ARHD ROM.
I purchased trickstermod and had a look into the CPU settings, and nothing seemed out of the ordinary. Also turned on the dev options of graphic CPU usage on the homescreen - not really showing unusual signs of anything. About to flash the original recovery on and email HTC to see if they might feel sorry enough to accept it as a straight manufacturing defect, without evidence of where we purchased it (as it was a second hand phone off the net).
subscribing to this thread - I have the exact same issue. I have installed CM11 and ParanoidAndroid. Torched and Bubba kernel... turned off lots of stuff.
I have whatsapp, soundcloud and facebook as the only background running apps. not sure what's the issue
sensors drain battery
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Laccee said:
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Click to expand...
Click to collapse
I have checked all the sensors in the testing menu by dialing *#*#3424#*#* and they all turn off and on as required properly. I noticed yesterday that I've actually burnt out the charging system as it has got too hot at one point, so no use pursuing anymore. I will stick with my HOX until it too breaks in some way. Received an email back from HTC saying "Not under warranty, not our problem" after asking if they had had any phones with similar issues pass through.
Hell0
Getting vertical lines on smt700 non rooted after over the air update (U.S)
After update I did a factory reset installed apps One by one and I started to notice a flicker of VERTICAL lines appearing at start of boot and also when batter is low it will freez slightly and do the vertical line thing before freezing a little then shutting off..
this only also with games...
Thanks a lot..
-AHMED-
My sister noticed an occasional black screen flash after updating her Tab S 10.5 to Lollipop. I have the same model upgraded to Lollipop and have never experienced this issue but twice, once on KitKat and once with Lollipop I saw part of the screen look scrambled (like an old set tuned to a channel that WA not in range), for a second after hitting the home key.
Sent from my SM-T800 using XDA Premium HD app
Green flicker
Smt700 wifi screen flashes green and gets vertical lines....
Sometimes when the screen does this flickering it restarts...
-Ahmed-
My 10.5" T800 has been on for over 200 days and has never been turned off or rebooted since i got it, no problems at all with flickering, but the older you get the less sensitive you get, I am not a gamer so my tablet is not stressed.
If you are having problems get your tablet repaired or replaced.
John.
I ve the same issue after upgrading to lollipop, I cant find the solution
Still flickering
try everything to solve this flickering with vertical line issue.
Nothing worked..
Factory reset, disable hardware overlays and limit performance ultimately won't fix this issue...
I have the same issue.
Downgrading does not solve the problem
I have seen that it happens when battery is lower than 50%.
To mitigate the problem I have set seen brightness to 30% fixed and also losing mobile segnala makes the screen flicker or the tablet to reboot
When you rotate the tablet do the vertical lines rotate as well.
John.
All problems started only after lollipop update.well most of us are getting them,,random reboots,green flickering lines,grey bars etc,,
But the only available solution for flickering Is turning the power saving mode on which is what I have done
iam facing this issue with my t705
its not the lollipop fault
its an hardware problem, the battery connector socket
This happened to me before and after the lollipop update. Someone suggested to use power saving mode to restrict CPU usage. It seems as if the tablet goes crazy whenever theres a high cpu load involved.
I have the same problem after update to lolipop. Most often occurs when there is a lot of notifications and low battery.
In my opinion is a software problem, what do you think ?
edit:
8% battery, lot of vertical lines during using notifications center, tablet reboots - this never happened before (on 4.4).
[SOLVED]
Fixed screen flickering issue !!
did this by governing the frequency to not pass more than 1.6 ghz...
Rooting then installing overclock widget and setting frequency to not pass 1.6ghz. Max..
From what I know about chips ''they are not all baked alike'' the same chip could come out with lower stable frequencies ..
I hope this helps someone for it has 100% solved the screen flickering problem for my smt700...
Thanks...
-Ahmed-
I found this, might be worth a try.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
Tinderbox (UK) said:
I found this, might be worth a try.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
Click to expand...
Click to collapse
My relative has complained of an odd flicker (screen goes briefly black) after updating to Lollipop. Usually happens while moving from an app to the home screen. I sent them instructions based on that article so they can test if it fixes their issue. I'll post the results but likely after a few days to make sure it actually works. Oddly enough I have an identical model SM-T800 on Lollipop and do not have the issue that they find so annoying.
Thanks for posting the article.
Sent from my SM-T800 using XDA Premium HD app
I've seen it on mine since Lollipop came along. In my case I get the screen with snow - like a TV tuned to a channel with no signal - . It's happened when the screen was timed out and then awakened. I've not been bothered by it more than about 5 or 6 times so I've just not bothered with doing anything about it.
Sefto said:
I have the same problem after update to lolipop. Most often occurs when there is a lot of notifications and low battery.
In my opinion is a software problem, what do you think ?
edit:
8% battery, lot of vertical lines during using notifications center, tablet reboots - this never happened before (on 4.4).
Click to expand...
Click to collapse
Video:
https://www.youtube.com/watch?v=4iBDVirN_XM
Service center in Poland (CCS) replaced screen and repaired motherboard. It seems to be fixed.
I thought it was a lollipop issue, but having followed the advice to force GPU screen rendering through developer options, I found the problem did not go away. Thus, it must be a hardware issue.
corvus.corax said:
I thought it was a lollipop issue, but having followed the advice to force GPU screen rendering through developer options, I found the problem did not go away. Thus, it must be a hardware issue.
Click to expand...
Click to collapse
Hello,
Did you try to set the default CPU frequency to 1.6 ghz... maybe even try to govern it down to 1.4ghz.
For my WiFi smt700 simply underclocking the cpu completely fixed the issue...
The issue is due to either your tab cpu wasn't from a set baked that could handle Higher work loads or quick raises in frequency like from sleep or switching between apps.. forcing GPU rendering take away resources from cpu and forces the GPU to do the work.. Hopefully an official kernel update could help with this in the future...
But for now under clocking the cpu or force GPU rendering or powersave mode all appear to help resolve the screen flickering issue and the only constant that I can determine is that these fixes all involve taking away workload from the cpu...
UNDER CLOCK FOR NOW !!
Thanks... (hope underclocking helps some members here)
-Ahmed-
Sent from my SM-T700 using XDA Free mobile app
That's interesting. Unfortunately, my device is not rooted yet and I don't plan to do that in the near future. So while I can use powersaving, I can't underclock. If there is a problem with the quality of the CPU, then IMO Samsung owes me a fully working device. I mean, they sold the device with the idea it was able to run at correct speeds.
I don't know if GSAM is simply not reporting it right but since I got my Exynos ultra GSAM is indicating AoD is my highest battery drainer by far, every single day (phone is turned off overnight so it has had multiple reboots and nothing changes). See attached 3 screenshots which show the typical stats I am getting. Any ideas??
In addition to that, every time I reboot the phone, a minute or so after rebooting, it opens the sim card settings screen all by itself, no messages, no errors, just an ok button at the bottom. I have no clue what it wants me to do. It does it every single time I reboot it. I press ok on the bottom of it and it closes that screen and then continues as normal. I have one sim card and one SD card and both seem to be functioning fine (the first time I put the sim in, it did not read it so I had no mobile signal, I took it out and checked it was seated properly in the tray, put it back in and it has read the sim ok ever since so I don't think it is related to that).
On my S20U Exynos GSAM doesn't work at all... Always shows "used 0% in 0h0m" and it doesn't track anything.
I just tried turning off AoD and now I get the same thing but from "com.samsung.android.app.routines" which comprises of packages System UI, Always On Display, Bixby routines which I have already turned off), Sstem UI (again), and LED Cover Service (which is useless to me, I do not use a case).
No idea what is going on.
ewokuk said:
I just tried turning off AoD and now I get the same thing but from "com.samsung.android.app.routines" which comprises of packages System UI, Always On Display, Bixby routines which I have already turned off), Sstem UI (again), and LED Cover Service (which is useless to me, I do not use a case).
No idea what is going on.
Click to expand...
Click to collapse
As soon as i get mine from Vodafone, I'm going on a major debloating session!
Solved it. I was using the default animated lockscreen wallpaper with the bubbles on it. Noticed in my screenshots of gsam it was saying "video" was on the entire entire duration that the AoD was on. Assumed this might be related to the wallpaper so I switched it to the same one but the static version and suddenly AoD is no longer showing as stupid high battery drain in gsam.
I am also no longer getting the sim card issue. I doubt that was related to the wallpaper, it was probably something else I fiddled with that seems to have resolved that!
GSAM's reporting is buggy on the S20U so far.
It will often put one of my random unused apps at #1 with a ridiculous number like 90%, even if they are deep-sleeped.
Unfortunately, none of the big battery monitors seem to be compatible either (BetterBatteryStats has fallback to boot problems etc).
Keive said:
GSAM's reporting is buggy on the S20U so far.
It will often put one of my random unused apps at #1 with a ridiculous number like 90%, even if they are deep-sleeped.
Unfortunately, none of the big battery monitors seem to be compatible either (BetterBatteryStats has fallback to boot problems etc).
Click to expand...
Click to collapse
I wasn't aware that Accubattery Pro or GSAM fully worked on Android 10 , last time I checked they didn't .
Sent from my EVR-L29 using Tapatalk
They seem to work now and yes, I am seeing the same issue (AOD consuming a lot) despite AOD being off. I now package disabled AOD and will keep an ee on it. I am also using the animated stock bubbles, as I quite like them
Checked after posting, indeed disabling the package did not seem to help - I now switched to the one and only wallpaper - pitch black