I seem to have been bitten by whatever it is that's causing Note 8s to freeze. In my case, it seems to freeze when idle - case closed, always-on display showing a clock. Sometimes the digital clock - just stopped; the last time, the analog clock with the second hand ticking, but an otherwise unresponsive phone.
It seems like this is happening to other people, in a variety of other applications - and the only advice anybody is giving is to see what happens in safe mode, then uninstall applications one-by-one. All of which seems rather time-consuming, and counter-intuitive -- if a single App is freezing the system, that suggests on o/s or hardware issue -- the o/s should be isolating the rest of the system from app misbehavior.
Which leads me to wonder how one might track down what's actually going on. If this were one of our servers, I'd crank up logging and look at crash logs. But... those options don't seem to be available without rooting the phone. (Why does Google insist on making syslogs unreadable by normal users - that puts a big crimp in the ability to do any kind of real trouble diagnosis.)
Any suggestions on how to do crash analysis? Any tools that someone can recommend?
Any insight on the matter?
I have not had this problem, so I would not know how to tackle all down to pinpoint the exact culprit, but I would start by controling what apps I dont want to run in background, in maintenance>battery>always sleeping, I put all the apps I dont need to be in always running state, I would also try to unistall or freeze apps I installed just before the problem began, if you have bk disabler this is a rather easy process, as you can batch-disable/enable apps, in the end it is a trial-error exercise
You can use logcat extreme, Catlog or somthing similiar from playstore. But you need some knowless to see wat happend and root. Perhaps you can pull the log file without root to your computer with ADB.
Sounds like impending motherboard failure. My wife's S7 Edge started doing the same thing then one day it just wouldn't start up at all.
Common thing for Samsung phones unfortunately .... and if you're out of warranty they won't repair without a charge.
Related
Hi, I looked for other threads in which someone else faced the same problem, but I have not found any answer nor good solution.
The problem is that the screen of my S3 MINI turns on automatically.
I changed the ROM twice (2 different ones, CM 10 and 11), so I don't think the reason is a single "defective" app: I believe in another explanation, according to which the reason would be a broken pin inside the microUSB port of the smartphone.
That pin let turn the screen on like if it was put /unput in charge.
The Question: is there a ROM / KERNEL / APP that prevent the screen from making this error?
How much is hard to edit a rom/kernel in order to avoid that the screen lightness wolud depend from that pins?
And if the reason is a defective app, has someone ever discovered which one is?
I'm afraid it's a way to screw the consumer: this automatic and uncontrollable activity of the display destroys the battery life. It's like if the smartphone is broken: you should change it.
I cannot accept that a 440€ smartphone acts in this way. I'll never buy a Samsung product.
I won't talk about the home button broken (could someone give me an advice on which app that simulates the virtual buttons is better?).
Thank to you all!
Pietro C.
UPDATE 28/12/2014 h14:34 ITA
I did a screenshot and I also photographed with a camera the display while it was showing the CPU activity. I noticed something (an app? a opened file? a function?) that appears only when the display turns on automatically. Some green words. I'm going to upload photos.
UPDATE 16:30
Cannot upload photos. Here are the scripts that appears on my phone:
com.android.system
surfaceflinger
system_server
com.teslacoilsw.launcher
kworker/u4
com.android.phone
com.facebook.katana
com.facebook.orca
kworker/2
kworker/6
kworker/1
irq/72...
irq/474
mmcqd
ueventd
rild
mediaserver
admsrv
org.cyanogenmod.voiceplus
dhd_dpc
com.google.processo.location
org.whispersystems.whisperpush
com.textra
com.google.android.googlequicksearchbox.search
AND the last 5 listed down here are the green scripts that appears only when the phone turns on automatically.
migration/I
kworker/I:0
ksoftirqd/I
watchdog/I
kworker/I:I
UPDATE 03.01.2015
I fixed the issue at the moment. I installed CM 11-20140823 after wiping and formatting data.
I installed the lowest number of Google Apps (here I chose Nano Modular Package: http://forum.xda-developers.com/showthread.php?p=44417509#post44417509 ).
I'm quite sure it's a issue caused by a unidentified google app, because when the phone was "clean", the screen kept turned off ALWAYS, unless I pressed the accension button.
Now that I installed ONLY Google Play and Google Services, the screen is ok.
So I will download only the most useful Google Apps, hoping that won't find the one infected (if I'm right about the cause of the automatic flash of the screen).
I also discussed about this issue here , and I discovered that many people are searching for a solution.
Maybe someone could confirm or contradict my theory.
I'm really stumped here. I haven't been able to find any solution to this issue through searching, so I figure I might as well post something about it.
For the past few months, I've been having an issue with my watch screen turning itself on then dimming after a few seconds. This seems to occur every few minutes or so even when theater mode is enabled and when always on screen and wrist gestures are disabled. This issue persists even after unpairing with my LG G4 and after a factory reset (on both the watch and phone). It should also be worth noting that I have recently rolled my phone back from the latest VZW Marshmallow OTA to a rooted 5.1 image in an attempt to resolve the aforementioned problem, but from what I can tell, it has only become worse.
From what I've been able to gather from battery/wakelock monitoring apps and bug reports is that the phone is regularly sending wake requests at semi-regular intervals. I have not installed any third-party wear apps and I've disabled pretty much every Google sync function but the problem persists.
I am at wits end here as to what I can do here. This coupled with my phone suddenly developing a severe wakelock problem has made me seriously consider switching to another manufacturer, and this time I may not exclude Apple as a choice.
Has anyone else experienced an issue like this that might have some insight as to what's going on?
Thanks!
PS: If needed, I can provide the full bug report along with a quick spreadsheet I made to organize the kernel wake source info found in the report.
I've seen this problem all over the internet for quite a few years on many different models of phones and Android. I have it happening on both my 6P and Note 9, figured I'd post here since it's the newer device.
It's mainly happening with Greenify and App Volume Control Pro. I already did all the fixes I've found online, such as making sure the apps are not being optimized by battery optimization settings, and whitelisting them in any where else that might be causing them to be disabled. The only thing I've not done is lock the apps in the recent apps viewer from being closed when you tap close all because it shouldn't matter anyways, I don't leave them open (truthfully I rarely open the actual apps anyways). They don't need to be left open to do their things, that's what persistent notifications are for, to make sure they keep running in the background. Now that I notice though, Greenify does not have a persistent notification on the Note for some reason. I checked all settings, it's not blocked or hidden anywhere. IDK. And AVCP doesn't have one on either device, don't think it ever has for as long as I've been using it. Can only lock apps in the recent list on the Note anyways afaik. (But this issue isn't happening to anything else under accessibility access settings)
I don't use programs like CCleaner or anything, the only thing similar I have on the devices is Samsung's Device Maintenance app, but that obviously is only on the Note so I don't see how it's the cause since it's happening in the 6P as well.
Both phones are running Oreo 8.1. The only thing not stock is that I have elementalx and TWRP installed on the 6P, otherwise it's the stock ROM and whatnot, no root.
This problem happens what I will say is randomly, because it can happen after rebooting the phone or after waking it up. Whether that seems to be 10 minutes or 10 hours doesn't seem to matter. Checking my accessibility has just become habit. The way I first found this was happening was because AVCP makes a toast message when I open an app that I have it set to change the volume for, like a game. The messages were not popping up so I looked into things a bit more when it kept happening.
Anyone have any suggestions other than what's been said in the past?
Same Problem, my device : Vivo Nex S 8/128gb Android Oreo 8.1 no stock rom it has Funtouch OS and no solution for the Bug/Issue.
I don´t know what keeps accessibility resetting several times a day. very annoying!
The knowledge in your article is very useful, thank you
Maybe you guys can help me, because the P30 Pro is driving me nuts. How on earth do I get it to stop saving power?! If I wanted a phone that only does single tasking and isn't able to do anything in the background, I'd get a Nokia 3210.
For example: I'm listening to music in the car. Then I pause the music playback via my in car controls. After a few minutes I want to continue, so I press play. What happens? Nothing. The music app stopped running, because Huawei thought it is absolutely necessary to achieve 2 days of battery life. Here's a trick for you if you want to achieve that: Turn off the phone! I'd rather have half a day than something that is this useless. It gets worse. I use an app to warn me about speed cameras. Well, it doesn't work on the P30 Pro. Because even when I go to the settings and go to the app, then details about battery usage, and then tell it to continue running in the background... the app doesn't get any GPS information in the background. Which is bad enough to begin with. It NEEDS to run in the foreground. As soon as it is in the background... IF it even keeps running, because it usually doesn't, despite me telling it to... no GPS, no function. I'm also using a GPS Logger for my photography. Guess what: Doesn't work on the P30 Pro. Because the app just won't run in the background. I've even set the phone to the power mode. Jup, doesn't help.
What. The. Hell.
How can anyone live with this sort of insane "optimization"? If Huawei had ONE place where we can RELIABLY tell it which apps to keep running in the background, and maybe a setting where it just doesn't optimize at all, then great. But this...?
Edit:
Ok, so I did find ANOTHER setting, well hidden, under Apps, then Apps, then the three dots, special access, battery optimization, then select all apps. And THEN are you able to AGAIN tell it not to optimize. Why is this so hidden? And why aren't users, like, warned? Normally, you can reasonably expect your apps to run in the background. And you can rely on it. If the phone does not want to behave that way, tell me. Then I can say if I want this behavior or not.
Ok, some more testing, and... some apps just won't keep running in the background. They just won't. Any ideas? They work on other phones. I've never had a phone they didn't. But the P30 Pro... no chance. Screen goes off or I go to a different app... and goodbye.
you can read it here, its for mate20pro, but it works for p30 aswell
https://forum.xda-developers.com/mate-20-pro/themes/remove-powergenie-to-allow-background-t3890409
Cool, thank you.
I did try a bit further, and without changing anything else, it looks like after a couple of restarts and some more attempts of running the apps in the background, the phone is starting to behave. Still no final verdict, but it's getting better. If it's still too annoying, I'll try the Power Genie thing.
Disabling Power genie has finally fixed my Softphone problem. it finally keeps running in the background to receive my business numbers.
"DEVICE OVERHEATING" Message and Apps Closing - even though phone not hot. how 2 fix?
So non rooted phone note 4 working well till today when i got ""DEVICE OVERHEATING" Message and phone force Apps to Close. I have tried several different batteries. And to double check i left phone with some desiccant in tupperware in freezer - and even stone cold phone tells me its overheating..i dont remember dropping it and it is in a otterbox defender case... so think it could be some internal temp sensor. but not sure what do do with this phone - is there something else i could try? Lucliky i have another note 4 that was able to bring back online but would be nice to get this pseudo 'overheating' issue fixed..... im hoping its not the mainboard... any advice with respect to how to fix this phone?
additional notes:
https://updato.com/how-to/how-to-fix-an-overheating-galaxy-note-4-issue/
https://www.technobezz.com/how-to-fix-galaxy-note-4-overheating-issue/
https://us.community.samsung.com/t5...5?cid=au_affiliate_adpump_imecom2017_20170331
Some of these are different i have not tied safe mode or looked at the temps reported by the cpu... trying to install a few aps to help debug this..
mos tof the time the device shots down within 45 seconds so not much to go on...
Safe mode is worth try. Factory reset is also an option but at least for me a last resort. Personality, I have never had this happen on my Note 4. Obviously, its not something that has been modified in the system as you are running stock. Small possibly it could be related to denied permissions, however not very likely.
As far as one of the links you posted, I would disagree that updating apps is a fix to overheating issues at least user apps. Google play is set to update by default.
If I understand correctly, you device is coldand popup notification states device is overheating. One thing yu mentioned especially cought my attention was the phone shuts down in 45 seconds. Not to jump to conclusions and I hope this is not the case but might be the dreaded emmc problem.
https://www.google.com/amp/s/forum.xda-developers.com/note-4/help/awful-emmc-problem-t3808257/amp/