[Q] Random Crashy behavior on stock unrooted MM. - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Since the upgrade to MM, I've had weird pseudo-crashes on my phone. The phone will suddenly get really hot in my pocket and vibrate once. When I try to use it again it has apparently rebooted because it won't take my fingerprint and asks for a backup password just like after a reboot. However, when I go into about device>status, the up-time hasn't started over like it would on a reboot. This phone is running stock unrooted MM that I upgraded OTA.
I have three questions:
1. Is this happening to most people running stock MM?
2. Is this possible a poorly behaving app or is it a bug in the update
3. Any suggestions on how to track it down and fix this other than doing a factory wipe and restore.
I really don't want to do the factory wipe because it will take quite some time to put things back the way they were.
Thanks for the suggestions

poit said:
Since the upgrade to MM, I've had weird pseudo-crashes on my phone. The phone will suddenly get really hot in my pocket and vibrate once. When I try to use it again it has apparently rebooted because it won't take my fingerprint and asks for a backup password just like after a reboot. However, when I go into about device>status, the up-time hasn't started over like it would on a reboot. This phone is running stock unrooted MM that I upgraded OTA.
I have three questions:
1. Is this happening to most people running stock MM?
2. Is this possible a poorly behaving app or is it a bug in the update
3. Any suggestions on how to track it down and fix this other than doing a factory wipe and restore.
I really don't want to do the factory wipe because it will take quite some time to put things back the way they were.
Thanks for the suggestions
Edit: And just after I posted this I received an update to PD1. Supposedly a security update, but maybe it will help with the crashes too.
Click to expand...
Click to collapse
Try doing a wipe of the cache only?

hammerchucker said:
Try doing a wipe of the cache only?
Click to expand...
Click to collapse
Did that several times, seems to calm down for a day or two after that. It's so random that I can't tell that it makes a difference.

poit said:
Did that several times, seems to calm down for a day or two after that. It's so random that I can't tell that it makes a difference.
Click to expand...
Click to collapse
It's very random and mine has been doing the same thing since the MM update. I wish now I hadn't done the update because for awhile, it was rebooting twice an hour. Since uninstalling the iHeart app, it's not doing it as often but still at least once or twice a day. And it's not just the Samsung devices. I've seen Nexus as well as other owners reporting the same problem.
I think I've wiped the system cache a hundred times now and wiped the apps cache repeatedly too. It doesn't help. And there's no rhyme or reason to it. Also, people who have done factory resets report that the problem does NOT go away. In a couple forums, people who returned their phones and had the motherboards replaced claimed the problem stopped, but I have a hard time believing that thousands of us would need to do that.
Sucks when I'm on a business call!!

Tigrisan said:
It's very random and mine has been doing the same thing since the MM update. I wish now I hadn't done the update because for awhile, it was rebooting twice an hour. Since uninstalling the iHeart app, it's not doing it as often but still at least once or twice a day. And it's not just the Samsung devices. I've seen Nexus as well as other owners reporting the same problem.
I think I've wiped the system cache a hundred times now and wiped the apps cache repeatedly too. It doesn't help. And there's no rhyme or reason to it. Also, people who have done factory resets report that the problem does NOT go away. In a couple forums, people who returned their phones and had the motherboards replaced claimed the problem stopped, but I have a hard time believing that thousands of us would need to do that.
Sucks when I'm on a business call!!
Click to expand...
Click to collapse
I've taken to manually killing apps a few times a day, it might be my imagination but it seems like it's helping. I've noticed that even after a reboot there will still be tons of apps in the recently used apps screen. Maybe this is a memory management or system resource issue.

poit said:
I've taken to manually killing apps a few times a day, it might be my imagination but it seems like it's helping. I've noticed that even after a reboot there will still be tons of apps in the recently used apps screen. Maybe this is a memory management or system resource issue.
Click to expand...
Click to collapse
I've tried killing aps, I've tried setting Do Not keep activities on, neither helps this issue. My suspicion is a baldy behaving app. perhaps BeyondPod.
I've moved to the beta version of Beyondpod which claims to have some fixes for Marshmallow. Still grasping at straws.

I've never had very much luck with 'dirty' updates. Either via OTAs or direct ODIN flashing. Have you tried completely wiping the phone and restoring?
I have a Sprint Note Edge (SM-N915P) and I was having a similar issue. Turned out to be a conflict between a manual change I had made to the system and an automatic one. I went ahead and did a clean reload of the phone even after I figured out the issue and it is running a LOT better.

I've been having constant reboots since I upgraded to MM. People keep telling me it's a hardware issue, but I never had this trouble UNTIL the upgrade. Since then... nothing but headaches and trouble.

Well, the problem wasn't Beyondpod. another thing that keeps crashing is Apex Launcher which hasn't had an update since June 2015. Maybe not MM compliant. Replaced it with Nova, lets see if that makes a difference.

I started getting this when I got my phone. It happened on LL 5.0.1, but didn't go away after updating to 5.1.1, after rooting, after removing all the bloatware, etc. I noticed that it happened a lot more frequently when I had the Samsung Messages application open. Like you, I tried wiping the cache partition, etc. Wiping the app cache for Messages really seemed to help, but only temporarily.
My sister's phone, also N910P, was fine until 5.1.1; then the same thing started happening to her.
I finally did a full wipe and flashed a fresh stock OS. It took me an entire Saturday, and lost me my root, but I highly recommend it. This phone is too good to be brought down by some sort of OS glitch. Now I've gotten the OTA, though, so I have to wait for a PD1 root.

kittsil said:
I started getting this when I got my phone. It happened on LL 5.0.1, but didn't go away after updating to 5.1.1, after rooting, after removing all the bloatware, etc. I noticed that it happened a lot more frequently when I had the Samsung Messages application open. Like you, I tried wiping the cache partition, etc. Wiping the app cache for Messages really seemed to help, but only temporarily.
My sister's phone, also N910P, was fine until 5.1.1; then the same thing started happening to her.
I finally did a full wipe and flashed a fresh stock OS. It took me an entire Saturday, and lost me my root, but I highly recommend it. This phone is too good to be brought down by some sort of OS glitch. Now I've gotten the OTA, though, so I have to wait for a PD1 root.
Click to expand...
Click to collapse
Well, I gave up and did a full factory wipe through recovery (3 times data and 3 time cache just for good measures). I allowed google to reinstall all the apps, and restored most of the app data using Helium. Not too confident that it helped because I kept getting the same type of crash while restoring helium data. It took most of the day to restore things and it's still not totally back to normal.

I have the same problem when I did the OTA update but first I thought I have a problem with my phone only me so I odin flashed PD1 and since then my phone is stuck at "installing system update" after odin flash. I took out the battery and anytime I switch my phone on it boots to recovery mode. Any help please? Would appreciate it. Can't use my phone.

Well, a full factory reset didn't help either. Thinking this is either an app that doesn't like MM, a bug in this implementation of MM, or my phone developed a fault at the exact same time it upgraded to MM.
Anyway, since it seems to happen most often either during or after I have listened to podcasts I'm going to switch podcast managers from BeyondPod to Podcast Addict. Did I mention I'm grasping at straws here?

Vortex421 said:
I've been having constant reboots since I upgraded to MM. People keep telling me it's a hardware issue, but I never had this trouble UNTIL the upgrade. Since then... nothing but headaches and trouble.
Click to expand...
Click to collapse
You didn't happen to update google services around the same time did you? I just recently updated google services and my phone started being weird . Uninstalled the update abd phone is back to normal
cheryl

my wife's phone has been acting up as well. I WAS an experienced flasher and all things android but i have since switched to iphone and now everything feels like a foreign language. She has Sprint N910P on MM 6.0.1 everything stock. Her phone will randomly reboot and it will completely shut off as if it died around 38%. I was going to try to root it and flash a new rom and/or kernel but I've read that's not working for some so Im at a loss on what to do or try.

ducehlmg said:
my wife's phone has been acting up as well. I WAS an experienced flasher and all things android but i have since switched to iphone and now everything feels like a foreign language. She has Sprint N910P on MM 6.0.1 everything stock. Her phone will randomly reboot and it will completely shut off as if it died around 38%. I was going to try to root it and flash a new rom and/or kernel but I've read that's not working for some so Im at a loss on what to do or try.
Click to expand...
Click to collapse
You may have two different issues. The phone dying at 38% is often a sign of a worn out battery. It was with mine.
I've still been fighting the random reboots, although I haven't had one in 2 days now. (I probably just jinxed myself.) For me it seems to somehow be related to listening to music/podcasts via bluetooth. Still leaning towards thinking it's a wonky app that isn't properly written for MM.

poit said:
You may have two different issues. The phone dying at 38% is often a sign of a worn out battery. It was with mine.
I've still been fighting the random reboots, although I haven't had one in 2 days now. (I probably just jinxed myself.) For me it seems to somehow be related to listening to music/podcasts via bluetooth. Still leaning towards thinking it's a wonky app that isn't properly written for MM.
Click to expand...
Click to collapse
Well i am really upset now. I started having this problem about a month ago. I was on ob7 5.01. It SEEMED to be related to google play services. I downgraded the service and things seemed better. But my apps needed the upgrade so i decided to just jump into mm. So even thoughboth Google and Samsung were suppose to be backing up my text mags i lost all of them. That would be fine if my problem went away but it dud not. Random reboots random freezes. Sometimes i take the battery out Causey it is locked up and it won't turn on at all or if it does it stays at the note 4 screen.
I am so annoyed is there anyway to find out what is the problem?
Sent from my SM-N910P using Xparent Purple Tapatalk 2

poit said:
You may have two different issues. The phone dying at 38% is often a sign of a worn out battery. It was with mine.
I've still been fighting the random reboots, although I haven't had one in 2 days now. (I probably just jinxed myself.) For me it seems to somehow be related to listening to music/podcasts via bluetooth. Still leaning towards thinking it's a wonky app that isn't properly written for MM.
Click to expand...
Click to collapse
Any chance this is sd card related?
Sent from my SM-N910P using Xparent Purple Tapatalk 2

cherylbaker said:
Any chance this is sd card related?
Sent from my SM-N910P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
Possible if you didn't delete the Android folder coming from Lollipop; I'd suggest both Android folders be deleted but you should also wipe data and internal too (rooted users should read the 3rd paragraph). Many reported factory reset after MM update cured a lot of problems. ItsOn is so prevalent and pervasive, I'm thinking Lollipop remnants of ItsOn can pose problems for even un-rooted users. Need a clean break from Lollipop.
This thread is for un-rooted users (the remainder of post applies to rooted users) but one thing I found happening to some rooted users is remnants of ItsOn causing reboots if not coming to MM cleanly.
The ItsOn apk in /carrier/ItsOn will cause issues if rooted users factory reset and don't wipe data and internal.
(/ is root menu; a current rooted ROM or rooting stock may not remove these but possibly will on future ROMs; if you fully activate stock and not wipe data and internal memory, these remain and will continually try to reboot the phone to establish the ItsOn bootstrapper but the phone says it needs to reboot to complete activation).
Rather deceptive. But ItsOn and Knox just don't play nice with root; they have to go.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you see this in hidden menu, it's an indicator you need to check for ItsOn and wipe. If you're wondering if you've activated ItsOn, check /data/local/tmp for an ItsOn log. Developers remove ItsOn but think about what you do after flashing a stock tar, boot and activate phone. ItsOn is a done deal at that point. Just wipe when rooting again.
Sent from my SM-N910P using Tapatalk

Mine does it too. Just freezes then reboots randomly. I think it has to do with the sd card because when i unmount it i have no problem. I'm stock pe1. If anyone has a solution i would appreciate it.

Related

Error messages, process failure

Hello, I have a weird situation on my hands here and was wondering if you might be able to help.
Firstly...
HTC incredible.
CM-7.0.3 stable (most recent)
CM kernel2.6.37.4 #27
Overckocled 1.1GHz
radio 2.15.00.09.01 (going to work now, need to update, just saw it was outdated)
Long story short.
my phone has been working fine, no issues whatsoever until yesterday. Yesterday my Market app and browser started crashing as soon as I started them.
Today more things are crashing, and at a much higher rate of failure. Normally I would just clear the cache, and the applications cache, and the problem would be fixed (this has been a problem in the past) however this is more than just one application.
popup error reporting reports that specific applications have failed (market, browser, etc), but I also get general "framework" crash popups. Ideas?
Side note. I am also noticing a very long startup time on restarts, much longer than in the past.
I have not made any recent changes to my phone (over-clocking, kernels, radios, ROMS) other than of course installing apps.
Warning message example.
com.android.market
com.google.processes.gapps
android.processes.media
Ideas
first thing i would do is clear cache and dalvik cache and try fixing permissions.
If those don't work which I won't be surprised if they don't I would...
clear all data and reflash the ROM. Quick and Painless with titanium backup.
I already cleared the caches and fixed permissions.
I know re-flashing everything will work, and I have doen that in the past, however I am really tired of it. It seems to be mort stable now, and almost fixed completely. (I didn't change anything after repair attempts stated above)
My question is really what ic causing this, and is there anything I can do to stop this from happening.
If this is something that happens all the time.... must be something you are specifically doing.
My friends inc was doin the same.thing. I couldn't even get into Rom manager or titanium. Never ran into that problem before in almost a year with the inc. Reflashing was the only thing that worked. As for the cause... its a computer. Computers don't need reasons to go hay wire.
There was a time my inc wouldn't stop rebooting... multiple times a day... very annoying. Did everything including goin back to stock. One day after a couple months of that crap.... it just stopped randomly rebooting...
Well...
Firstly I agree, but dont know why...
This happens with different severity levels on average .9 times a month.
The strange thing is that I do nothing specifically at the time to cause this. No kernel installs, reflashes, rom updates, radio updates, or anything specific. It is just general use. It is not as if this happens as soon as I do anything in particular.
Any thought on any specific configurations that might cause this to happen over time, or settings that I can change? I would understand this happening on a system update, or major change, but that does not seem to be the cause in this case, or any other times this has happened.
What I would do...
Go completely back to stock. Run that for a month. If it STILL happens... take it to Verizon to exchange for a new one cause this isn't normal.
Thats the thing...
Hmmm... I have considered doing that. I am not sure I want to go through the trouble. Any other thoughts? (assuming that the phone itself is fine for the sake of this thread.)

So is there no fix/ solution for random reboots?

I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.
Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.
I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/
Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.
So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.
Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."

VS985 non-random Reboots during phone calls any help would be amazing

I have a Verizon VS985 running 5.1.1 completely stock, never rooted or anything.
My phone works perfectly I can use it for days with no problems....
That is unless I make or receive a phone call. During phone calls my phone will freeze for a second lockup, then reboot itself. Once it reboots it's usually fine. It used to happen pretty infrequently like once every couple of weeks, so I ignored it. But now its happening at least once a day.
So I ask does anyone have any ideas at all what might be causing this? It seems to me it's gotta be software related, maybe?
I have 3 different batteries all genuine LG, it happens with all 3 of them, so it seems to be it can't be a battery issue (correct me if I'm wrong).
If there's any other information you need, please ask. Thank you xda community you are awesome.
Same issue
My phone will randomly reboot itself during a phone call. It has happened as many as four times during the attempt to finish one phone call.
Long story short, since my first message got erased by accident. I don't know if mine is fixed or not, since it happens hit and miss. I went to storage options and saw I had like 12 gigs of cached data, since it was counting all of the system files as cached data. I tapped cached data and cleared it. All the system files went back to misc folder where they normally are, and so far after about a week I haven't had a restarted. Could just be a coincidence. Clearing the cache daoesnt lose anything, although for some odd reason some apps seemed to lose random settings,and some required I relogin.

Question Multiple restarts

Just got my 6p yesterday and Getting multiple restarts and system UI crashes , I did restore my phone with apps ect I wonder if that could be the issue anything helps thank you .
Sounds like it. If your using a custom launcher delete the widgets and readd them
No custom launcher should I factory reset? or try something else will delete the 1 widget and see if that helps any other solutions is welcomed thank you
There are some people here that had a similar issue (including me), I myself had to get a new device (replacement) from Google to solve that issue. We already had/have a thread about this, maybe you can find some info there.
Okay thank you back from a restore less restarts but still getting them & phone freezes up from time to time guess this is a serious issue & not just software smfh.
sunnybwoy1 said:
No custom launcher should I factory reset? or try something else will delete the 1 widget and see if that helps any other solutions is welcomed thank you
Click to expand...
Click to collapse
I'd do a FDR and start from scratch. I know it takes longer but I do it with every new phone and after a major OS update. I'm a firm believer in not bringing any data over from an old phone.
Can you define FDR? I have done a factory reset if that's what you mean but I think I have fixed the issue will report back after 12 hrs of testing & results
I had the same issue before but this is what I had done before and after, so I hope this advice may help you.
I had come from a OnePlus 8 Pro, so I naturally wanted to transfer all data from 1 phone to the other. BIG MISTAKE! I had several reboots during the 1st few days. So I started searching around this forum and found a few people suggesting that you factory reset your phone but DO NOT TRANSFER any data from your old phone to your new phone (using the cable). Instead, factory reset your Pixel 6 without restoring any data, then once you get through the initial setup, upgrade to the latest version using an OTA file. Once you did that, then start slowly manually transferring the data from your old phone manually. This is what I did and have had no issues since, no reboots and everything seems solid. Battery life seems way better doing is this way and the UI seems more stable as well, as before, it would be janky and the battery would drain.
I hope this helps
I had the exact same issue and it was only solved by getting the device replaced. I found the replacement device worked better in all respects, not just solving the reboot problem.
Just get a replacement!

Question Random reboots

Hi!
I own an SM-F926B/DS since April with latest updates, and the last couple of months it randomly reboots. Some times reboots without asking SIM PIN, some other times reboots asking SIM PIN, some other times it keeps rebooting and I have to press the side button to make it functional again. Most of the times, the phone is hot on the back. I don't have to use the phone, some times it has rebooted just when I pick it up from the table. There is not a specific pattern, at least from what I can tell, some times 2-3 days will pass without any reboots, some other times a couple of times per day, some other times it goes to a reboot loop. Some times, the phone freezes (usually in Chrome or in settings menu), or some random applications do not open.
I tried removing some apps which I installed the period I noticed the problem, but it didn't make any difference.
I understand that I must do a factory reset, but I'm trying to find other ways to debug the problem before doing this, because I have many apps with many settings and it will take me forever to reinstall them. also, by just restoring a previous backup after a factory reset, I'm afraid that probably I will restore the problem too.
Have you any other advises? Perhaps a way to log the state when the phone tries to reboot or which application requests it?
Are there any others with similar problems?
Thank you.
.
I have had the same problem. Ses after the last update it don't seem to be happening now.
I had a random reboot problem back in July and it was the Facebook Messenger app that caused it after an update they did. When they updated it again, the problem stopped. The app also had been eating battery like crazy during that time. So, I'd start with looking at what apps got updated at the time it began happening as well as see if any are killing your battery.
Sounds like a badly behaving app eating battery and CPU to the point it's getting turned off. I would start with usage stats and battery stats whenever this happens and see what's going on in the background and start there.
Thank you for your help.
As I have said, the phone has all the latest updates, so it is not an outdated app or OS issue. Also, I have hundreds of apps installed, taking 10 updates daily, so it is impossible to track down which app might have caused the issue two months ago.
The phone does not turn off, it reboots. This way I can't find the app which may consumes more battery. The only thing that could help and I have not already mentioned, is that in most cases I see issues related to "Google Play Services" like excessive battery usage or stopped responding.
nasos75 said:
Thank you for your help.
As I have said, the phone has all the latest updates, so it is not an outdated app or OS issue. Also, I have hundreds of apps installed, taking 10 updates daily, so it is impossible to track down which app might have caused the issue two months ago.
The phone does not turn off, it reboots. This way I can't find the app which may consumes more battery. The only thing that could help and I have not already mentioned, is that in most cases I see issues related to "Google Play Services" like excessive battery usage or stopped responding.
Click to expand...
Click to collapse
It has nothing to do with an app being outdated, but that when they updated it, they coded something wrong. You can try to track which one by looking at which apps consume too much battery in the Settings. Rebooting does not change that stat at all, and rebooting is what it did when Facebook Messenger caused my problem back in July.
ButterflyFlutterflyMyOhMy said:
It has nothing to do with an app being outdated, but that when they updated it, they coded something wrong. You can try to track which one by looking at which apps consume too much battery in the Settings. Rebooting does not change that stat at all, and rebooting is what it did when Facebook Messenger caused my problem back in July.
Click to expand...
Click to collapse
The usual suspect is Google Play Services. In device care I see different apps crashing daily, not the same.
This is a screenshot of battery consumption right now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nasos75 said:
The usual suspect is Google Play Services. In device care I see different apps crashing daily, not the same.
This is a screenshot of battery consumption right now:
View attachment 5718377
Click to expand...
Click to collapse
My Google Play Services are currently 1.5 and 0.3% (Secure Folder and regular one), so that's not excessive battery use for that. When Messenger caused me issues, it was like 40% or something. It also never crashed.
I tried a diagnostic log app, but it doesn't work to capture random reboots. I just had to wait until they updated the app, which I think was about a week after it started. It mostly happened while I wasn't using my phone.
Hmm.
Last week I eventually did a factory reset. After selecting language for the initial setup, the phone entered a reboot loop again, so it was obvious that it wasn't a software issue. I proceeded with the setup, but without restoring any applications. The phone did some reboots again.
I contacted local customer support, and when I went there they connected the phone to their software and they were able to see in the log files some kernel panicks, memory errors and boot loops since the factory reset. They told me that if I hadn't reset the phone,they would be able to see all the problems since the beginning.
They told me that they have to change the main board, and after two days I got my phone back. This happened on Friday, today is Monday and everything seems fine (I crossed my fingers). I reinstalled everything including applications from Samsung Cloud.
nasos75 said:
Last week I eventually did a factory reset. After selecting language for the initial setup, the phone entered a reboot loop again, so it was obvious that it wasn't a software issue. I proceeded with the setup, but without restoring any applications. The phone did some reboots again.
I contacted local customer support, and when I went there they connected the phone to their software and they were able to see in the log files some kernel panicks, memory errors and boot loops since the factory reset. They told me that if I hadn't reset the phone,they would be able to see all the problems since the beginning.
They told me that they have to change the main board, and after two days I got my phone back. This happened on Friday, today is Monday and everything seems fine (I crossed my fingers). I reinstalled everything including applications from Samsung Cloud.
Click to expand...
Click to collapse
Oh wow, what a hassle! Glad the phone seems to be working well now, though! That's crazy that it rebooted that early in the setup process. Did you have to pay for the fix?
No, it was covered by guarantee, the phone is less than 6 months old.
nasos75 said:
No, it was covered by guarantee, the phone is less than 6 months old.
Click to expand...
Click to collapse
Well that's a relief!

Categories

Resources