Database Users

4.1.83 - random reboots a thing of the past?

I realized today that I hadn't had a random reboot in a while. From day 1 I could count on 1-2 random rebooted with my Atrix.
Sure enough, my uptime is 280hrs+, which is in line with when I took the OTA update. My wife's phone appears to be the same, and it was rebooting at a similar rate to mine before the update.
Both are rooted/non market enabled but not modded.
How's your stability been on 4.1.83?
Sent from my MB860 using XDA App

I had one strange reboot this morning, my phone had been lagging up a lot, along with the screen not turning on when I pressed the sleep button.
I look down a minute later and I see the Motorola logo. But afterwards it seemed just dandy.

Random reboots
I just bought this phone Friday at 7:45pm. It was working fine when I got home Friday night after purchasing it. I hooked it up to my pc and got the needed updates to 4.1.57.MB860.ATT.en.US. Saturday morning I installed one game bejeweled and advance task manager before heading out to work.
I got back home around 1:30pm and started setting up my contacts on the phone. Around 6:00pm I left the phone plugged into my pc and heard the phone rebooting from the other room. At first I thought maybe there was an update and that's why it was rebooting.
Two hours later it did the same thing again with no warning about a reboot when I was manually adding new contacts. I notice there was another update available to version 4.1.83 which I now have installed on the phone and it's still rebooting on its own.
I also noticed that my battery was right at 60% and while plugged up to my pc it was only recharging 10% every hour on the hour not sure if that's normal for this phone.
(Two hours later battery power at 90% with a solid green power light visible but taking forever to reach 100%)
Also right after the 4.1.83 update the phone would reboot and then the battery light on the phone would just randomly flash red with the motorola logo sitting on the screen. I had to pop the battery out, waited for about 30's before putting the battery back in and powering it back up and it still sat on the logo screen with the red flashing light.
(The battery is now at 100% but 3mins after unplugging it from the pc it displays 90% again all I've did is watch it reboot on its own.)
I removed the battery again but waited for about 5mins before powering it up and this time it actually booted up like normal and about 30mins later another reboot.
I also noticed that as soon as I finish watching a video with youtube the phone reboots a few seconds after the screen goes to sleep. Now as I am writing this comment I decided to uninstall that advance task manager program and do a reboot. The phone is at 80% and after I watch about three videos with youtube the phone didn't reboot.
I have no idea what's up with this phone and I really like it alot except for this mysterious rebooting not to mention other people experiencing random reboots. I read online where a lot of people where saying it was due to a bad battery and that they got a new battery from Att and the problem went away.
I am really thinking about turning this one in for a new replacement but some people are saying even after doing that they still kept having the problems.
Could this really be something wrong with the updates that is causing issues with the phone or is it just a bunch of bad batteries?

Battery?
Back again, in the post I made earlier I mentioned how the phone wouldn't randomly reboot when the battery was around 80% well the battery charged to 90% and the random rebooting has started up again and it has rebooted 3 times back to back now that it is at 90%.......I think I am going back to the Att store when they open today and try getting a new battery............

nickleboy said:
Back again, in the post I made earlier I mentioned how the phone wouldn't randomly reboot when the battery was around 80% well the battery charged to 90% and the random rebooting has started up again and it has rebooted 3 times back to back now that it is at 90%.......I think I am going back to the Att store when they open today and try getting a new battery............
Click to expand...
Click to collapse
If I were you I would get a replacement phone. I did have one random reboot since updating to 4.1.83 and that was the first ever I've noticed with my phone. Otherwise I haven't noticed any issues. As for charging via a pc I did hear that was slow. I charge via power outlet or using a car adapter and both are fairly quick. Good luck.

Battery?
I decided to do a factory reset on the phone first and the funny thing is after the reset, the phone still showed that it had the latest update installed even though I still had to go through the setup process just like when I first purchased the phone. So far it appears to be working and hasn't rebooted on me yet. No rebooting after playing Youtube videos either. The only small pet peeve I have at the moment is the Facebook & MySpace contact photos will not show up for some unknown reason in the contacts sections, they're just empty picture frames. The contact photos that do show up are the ones from my google gmail account and I manually added those online myself so those automatically transfer when my phone syncs with the gmail account.
And the MySpace widget doesn't show a photo as well but the info in the widget is current. That's way better than experiencing random rebooting when you really need your phone the most.

nickleboy said:
I decided to do a factory reset on the phone first and the funny thing is after the reset, the phone still showed that it had the latest update installed even though I still had to go through the setup process just like when I first purchased the phone........
Click to expand...
Click to collapse
This is normal. A FR cleans all of the user data reseting it back to a "clean" version of the flashed rom.
I can say that I have also not had any reboots since .83 but it is also the first time i have loaded gingerblur.

[Q] i9505 turns off when stressed

Dear Friends,
I'm having a rare problem with my S4.
All used to be fine but now suddenly the device turns itself off when it's stressed. By stressed I mean during a call while switching to another application or watching a video for more than a few minutes. To me it seems like a battery broken because once I unplug the AC cable and run the benchmark the phone shuts off and usually when it gets to the GPU/Video related tests. When I plug in the AC cable and run the test everything works as usual.
Also when the phone has turned off randomly the phone has problems booting up. It will get to the omega boot animation restart again. The intervals are always different. Sometimes the logo spins for a few seconds and then it reboots again, sometimes it happens right away when the logo appears. Its almost that the phone does not have enough juice to boot up eventhough the battery is charged with 40% or so.
Once I plug in the AC cable the phone boots up normally. I doubt that it's the custom Rom (Omega 9.0 with stock omega kernel) that is causing the problem. It seems hardware related. I'm guessing:
- GPU
- Battery
What do you think is causing those random turn-offs ?
Should I exchange the battery or flash stock rom to check if it still happens?
Why does it make a difference if the AC cable is plugged in? can it be anything that is not battery related?
I'd love to have your opinions!
Best,
Thomas

Hello Hello my favorite people!
Guide me to the light

exxi said:
Hello Hello my favorite people!
Guide me to the light
Click to expand...
Click to collapse
Your using XXUBMGA right? I had this weird problem where the screen wouldnt turn back on unless i pulled the battery. I switched to the german firmware and all is fine. Its not hardware, trust me, same prob.

First go to stock rom mate, then check
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2

drakexpl said:
First go to stock rom mate, then check
Wysyłane z mojego GT-I9505 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Weird thing is i was using stock, even though exxi is using a modified rom it might not play nice with root/custom kernels. Dont know for sure though; just what i have observed directly.

Friends,
I've installed the Pre-Rooted Stock Rom UBMGA via Odin. Cleaned the phone completely. It booted up and during the first Sign up process (google account, wifi network setup etc.) it went off again with 80% charge. When I plug it to the charger I can continue the setup normally. It seems that whenver it starts any GPU related process (Video animation, Antutu menchmark, Quadrant, Games) it turns off without warning. I ordered a new bat. hopefully it will arrive next week but until then I will not know if the issue is battery or phone related. at this point I doubt that it's ROM related. What's your judgement on this?
Best,
Thomas

exxi said:
Friends,
I've installed the Pre-Rooted Stock Rom UBMGA via Odin. Cleaned the phone completely. It booted up and during the first Sign up process (google account, wifi network setup etc.) it went off again with 80% charge. When I plug it to the charger I can continue the setup normally. It seems that whenver it starts any GPU related process (Video animation, Antutu menchmark, Quadrant, Games) it turns off without warning. I ordered a new bat. hopefully it will arrive next week but until then I will not know if the issue is battery or phone related. at this point I doubt that it's ROM related. What's your judgement on this?
Best,
Thomas
Click to expand...
Click to collapse
My dears,
any ideas?

exxi said:
My dears,
any ideas?
Click to expand...
Click to collapse
Any news? I've had Omega v7 and like two weeks ago it started to turn off suddenly... I thought battery run of or something, later on when this turn off happened and I turned phone on I had "black screen of death" or what to call it.. no launcher but status bar was ok, when I dragged status bar down I could open settings and change "homescreen" to basic and than back to normal and it worked...but... I couldn't use home button, it just showed black window that disappeared immediately. I backed up data and flashed Omega v11, after "tutorial" just after choosing language it showed this black screen again, so I've begun being suspicious it's hardware related. Morning after that it was working okey. Well...not really.. in app list one page of app was showing shadows of icons instead of icons, when i scrolled trough all pages it fixed. Later that day it turned off again. No turning off omega symbol, just.. like if you pull out battery. And those shadow icons were on two app pages. I've flashed nandroid backup of original ROM and when I browse gallery fast it turn off again... I suppose it's hardware related as it's not stuck to specific ROM. Maybe wrong battery? but more like motherboard I think. It also broke my sd card, because of multiple power failures probably. Also after this turn off battery drops down for like 10% or more. First screenshot - shadow icons..second screenshot - battery % drop

exxi said:
Friends,
I've installed the Pre-Rooted Stock Rom UBMGA via Odin. Cleaned the phone completely. It booted up and during the first Sign up process (google account, wifi network setup etc.) it went off again with 80% charge. When I plug it to the charger I can continue the setup normally. It seems that whenver it starts any GPU related process (Video animation, Antutu menchmark, Quadrant, Games) it turns off without warning. I ordered a new bat. hopefully it will arrive next week but until then I will not know if the issue is battery or phone related. at this point I doubt that it's ROM related. What's your judgement on this?
Best,
Thomas
Click to expand...
Click to collapse
i have the same problem with one of the last stock release, in last 2 days my phone's system was totaly burnt because i've played a lot with roms kernels and tweak, and it started to give me also this kind of problem. So i flash by odin one of last stock firmware and it's ok, after a few minutes i've rooted again the rom and charged phone from 19% (at this percentage the phone turn off) to 100%. it seems to be okay, but at 63% it turn off again, so i pull out battery for some minutes, and after it continues to turn of after a few seconds...
(one of the tweak that i made was using "battery calibration" it clean battery stas that can be damaged by skipping between various rom, i used it a lot on galaxy nexus but maby this can be one of/the reason of problem)
Have u resolved by changing the battery???

Dear folks,
It's a battery related problem. When I changed the battery for a mumbi type new battery the phone works with no turning off. Problem resolved
Sent from my GT-I9505 using XDA Premium 4 mobile app

Bootloop Related To Battery Percentage?!

It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry ?. What do you guys think of that issue? anyone else had the same problem?

Hrmmm... Try disabling battery saver all together. A similar situation I had with my Pixel XL. Good luck. I miss my 6P!...:crying:

nagoo1 said:
It's my brother's phone. out if nowhere, it started bootlooping.
Click to expand...
Click to collapse
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.

v12xke said:
Fastboot format userdata, system and cache then install NOF27B full image using flash-all.bat.
Click to expand...
Click to collapse
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.

nagoo1 said:
Isn't NOF27B a PIXEL rom? ... If yuo mean N4F26T for nexus 6p, then I sadly tried that. I did it with twrp recovery though.
Click to expand...
Click to collapse
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.

v12xke said:
Yes, sorry N4F26T. You cannot install a full image with TWRP. You need to fastboot format your cache, userdata and system partitions (not wipe with TWRP) and then fastboot flash the full Google image (not the OTA) using flash-all. bat.
Click to expand...
Click to collapse
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man

nagoo1 said:
I meant that I wiped everything with twrp then flashed factory image with Flash-all. I don't know if formatting with fastboot will make a difference but I will try it, hope it works.
Thanks man
Click to expand...
Click to collapse
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.

v12xke said:
Yes, formatting is different than wipe. Note any errors during the formatting. Cap your screen if you get any. Good luck.
Click to expand...
Click to collapse
I tried formatting, got no errors, and the same freakin boot-loop. The thing is we bought this phone from USA and the warranty expired 3 weeks ago :s .. anyways, if you have any other ideas plz suggest
Thanks

@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.

v12xke said:
@nagoo1
Your case is different from (almost) all others. People with the BLOD have no recovery mode and you are using TWRP with no issues. A few have recovery but cannot format userdata or cache and get terminal errors attempting to format. You say the phone works normally under 10% but not above. Maybe there is something wrong with the battery? Try running an app called Accubattery. Once installed, charge the phone from below 10% until the APP tells you the phone is full. Don't go by what the phone says. Don't take it off the charger until Accubattery tells you it is full. After doing this check under the "Health" tab for the estimated battery capacity.
Click to expand...
Click to collapse
Thanks for replying. I'd like to try your method but I don't think it's gonna work for me as the phone starts bootlooping after the 10% mark and the app wouldn't stop it from doing that. I also think that battery health is OK because if I keep charging it up to a 100% while off then try to boot it, it keeps bootlooping for about 5 hours until it reaches 10% then boots normally.
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
I tend to believe that it's a ram issue as I've seen this before in other phones, PCs and Laptops, but what does any thing have to do with this 10% battery??????

nagoo1 said:
I don't know if I said this before, sometimes it boots up at a higher percentage but as soon as I start using it (open any thing or even swipe left and right), it bootloops again till it reaches 10%
Click to expand...
Click to collapse
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)

rchtk said:
Did you watch the kernel logs? dmesg and after reboot /proc/last_kmsg (which will be empty unfortunately if RAM stops being powered)
Click to expand...
Click to collapse
Never done this before, I'll look it up and try to get it. I think I saw an option in twrp to copy logs.

nagoo1 said:
It's my brother's phone. out of nowhere, it started boot-looping. I tried everything I know to fix it, I was pretty sure it's a hardware issue once i saw it. It keeps trying to boot, some times it passes the google logo to the colored dots but with a very slow-motioned animation, then it boot-loops again. sometimes it boots though but once I try to put the google account and stuff it boot-loops again.
I started by clearing cache and data. I tried then installing the last factory image, when it didn't work I tried also last month's image and MM image, nothing worked. I went on and tried PureNexus, LineageOs, and a punch of kernels.
I left the phone boot-looping over night and when I woke up it was booted. The battery was 5% so I connected the charger and started putting my account and fingerprint. Suddenly it boot looped again at 12% battery. I unplugged the charger and left the phone. It kept boot-looping for a while the booted up with 10% battery. I didn't try to charge it again and everything went smoothly. I started trying the stock roms again, even the beta 7.1.2, I'm now sure that it only boot-loops above 10% battery, lower that 10% it works like a charm even with games and heat.
I know it's a long A$$ post but I'm not sorry . What do you guys think of that issue? anyone else had the same problem?
Click to expand...
Click to collapse
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.

anikadam said:
happened to me just now, been bootlooping since morning, phone was being charged alternately with my wall charger and usb connected to my charger, in the middle of me trying to find a solution, so the phone was adequately charged. finally getting tired of the whole trial and error i forgot to charge and was busy restoring my old recoveries when an oct 2016 backup suddenly started booting with the running colored dots and when the security screen came in and the phone died because of low battery. I had tried the same backup before but it didnt boot. can this be true ? that the bootloops are battery related..
My bootloader shows Battery as OK and i can access TWRP recovery.
Click to expand...
Click to collapse
Seems to be the same issue. I hope we both can find a solution for this.
Here are two dmesg.log I got from TWRP, I got one below 10% and one above 10% (bootlooping). I really don't know what to do with these, so we'll need some experience here
Edit: too much characters for the post, I'll attach them instead

I hope this is actually what you guys are looking for.
View attachment 4089615
View attachment 4089616

It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.

jhs39 said:
It actually sounds like you might have a hardware issue where if the phone gets too hot from running or charging the phone bootloops. This could be because of damaged memory, a damaged CPU or damaged connections to the motherboard. The phone might work at 10% or less because the phone is running cooler when the battery is close to running out since the phone is trying to preserve what is left of the charge. I seriously doubt that there is anything you can do software wise to fix that phone. You could bring it into a repair shop. Frequently they give free estimates on a repair. Good luck.
Click to expand...
Click to collapse
Yeah I think it's a HW failure too, but what makes it work without any issues under 10%? keep in mind that sometimes I leave it bootloop for hours before it reaches 10% and boots-up, which means the device is hot. Also, if i leave it to cool down with airplane mode for a while, it keeps working. I even tried playing asphalt till the phone reached 0% and shut down. It has nothing to do with heat i think, which means its not connection issue like we used to see in graphics cards before.
I just wanna know what gets triggered under 10% that makes the phone work normally? it's not battery saving mode cause i've tried it, but I'm pretty sure something changes at exactly 10% that makes it work.
I don't have a service center that I can trust over here, I called them and they told me they will try flashing the SW (not free of-course) and that if ti's not SW then they will change the main board for almost the same price as a new phone :laugh:

I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.

I knew it wouldn't work, but I had to try
I found a thread over here that fixes bootloop for a certain situation, i knew it wouldn't work but i tried it anyways.
https://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938
Following the guide I have to Restore a backup through TWRP, It further proved that It's a HW issue when it kept freezing and rebooting when trying to restore. I left the battery drain till it reached 10% then tried to restore again and it worked and booted up, but again when I tried to charge beyond 10% it bootlooped :crying:

jhs39 said:
I could be wrong but I think the battery saver feature basically turns off your radios and reduces brightness so you can still make calls for as long as possible. But I think even with that off your phone likely consumes less energy when the battery is down to 10% because the cpu cores will no longer operate at full strength. You might be able to use the phone somewhat if you install Francos kernel and use the most battery restraining governor settings possible to keep the phone cooler and processor use at the minemum but even if that worked you would basically be turning the 6P into the equivalent of a hundred dollar phone usability wise so it's kind of pointless. I asked a repair shop here what it would cost to replace the motherboard and they said it was essentially replacing the whole phone and wouldn't make sense cost wise. I don't think any of these 6Ps will be around in a few years. It doesn't seem like they were built to last.
Click to expand...
Click to collapse
Nice Idea, but I don't know which kernel manager to use with franco & what settings would be best for limiting cpu. if there's a topic about that please point it to me or give me ur thoughts

Crappy battery management (MM stock rom)

...

cmmx said:
Had the phone shut down on me twice now, while using the camera and gps on (no cell network), after just a few hours of use from full load. First time, when I went to recharge it, the battery was at 24%; the second time, it was at 68%! WTF?
Click to expand...
Click to collapse
Looks a little erratic to me.
Did the phone shut down while using the Camera and GPS on both times? Do you have other apps running in the background?
It seems like an overheating problem.

...

cmmx said:
Yes, camera and gps both times; I was testing several cam apps, the second time. But it was because of the battery, not temp. - or so it said.
Update:
Tried again today, and, switching off all radios (Wifi, which "Smarter" Wifi Manager didn't disable, even though I was kms away from any known network, GPS, NFC, BT and Cell), it took the phone the whole of 9 (nine) minutes to go from 99% full to the ultra mode and switch off (which happened at the same time, btw) with 24% of power remaining.
Was testing different camera apps, cycling through them and flushing memory in between (unlike last time, where they all were loaded the whole time), and all I was able to take was 22 pics, and the battery was dead.
Then, 15 minutes after a last attempt to power it back on, connected it to usb, and the battery was at 74% - you go figure.
Click to expand...
Click to collapse
Can you try using the Battery Repair Life available in the Play Store and post your results of the Cell Map before fixing and the Information tab?

...

cmmx said:
Results from Repair Battery Life and Battery Repair Life, respectively.
Click to expand...
Click to collapse
Bummer...have you tried uninstalling every Camera app you have and use your phone for one day just using the preinstalled one?
In 22 camera apps, perhaps some of them are bad and may cause your phone to randomly shutdown (i have no explanation for the battery percentage randomly showing tough)
Can you provide a list of those camera apps before uninstalling them?
EDIT:
Does the phone shutdown if you're using those apps while charger is plugged in?

...

cmmx said:
It doesn't happen under regular use, so I don't think that's the cause - and it wasn't a system crash, anyway, the ultra mode warning showed up, and the low battery/shut down just popped up on top of it.
The apps I tried:
Open Camera 1.40
Bacon 1.10.2
FV-5 3.31.4
Snap 8.2.7
Proshot 5.0.8
Footej 2.11.113
Nope, the phone never shut down on me while plugged in - individual apps, yes, but the phone itself, no.
Click to expand...
Click to collapse
Have you tried wiping the cache?
To wipe the cache partition, follow these steps:
Shutdown phone
Hold the Power key and Volume Up for about 8 seconds.
Use the volume button to select Wipe Cache Partition
Press Power Key
Restart phone after "cache clean complete" by selecting "reboot now"

...

cmmx said:
I'm on stock, no TWRP or root, so volume up opens eRecovery, and no way to flush cache there.
Click to expand...
Click to collapse
You can use ADB to try to boot into recovery mode, do you know how to?

...

cmmx said:
Done, now what?
Btw, any opinion on 2950mAh (claimed) batteries for this phone? E.g.: https://www.aliexpress.com/item/1-P...90-N790-N790S-U805-U232-U230/32338796619.html
Update:
So, either the battery is dying, or something is wrong with the phone: just went to my veranda to take some pics and, in less than 2 minutes, it went from 100% to shutting down (again, shuts down as soon as ultra mode pops up); plugged it to usb, and it showed 83% battery; pulled the usb cable and it status icon was at 80%. Went to try it again, managed to take 2 more pics and it shut down again; went back to the pc and the status icon was empty; plugged to usb, and it was at 73%...
Click to expand...
Click to collapse
Sorry for the late reply.
Plugin your phone to the computer, open a Command window, navigate to the folder you have adb extracted and type:
adb reboot recovery.
See if you can clear the cache partition.
If you have questions about which option you should choose ask first before selecting!

...

cmmx said:
I already did that; the update was after that - apparently it didn't have any effect...
Click to expand...
Click to collapse
You said in a previous post that if you don't use any camera apps that the phone works perfectly right?

...

...

Note 4 (N910F) restarts itself

I finally upgraded from S5 to Note 4, I've had my phone now for 2 weeks but I have a problem!
If the phone is asleep (I mean screen off and I haven't touched it) after around 2 hours, it's like it's powering itself off! Because when I put the screen on, the samsung boot logo comes on, not the first galaxy note 4 screen but the second one. After that I can unlock the screen, so it doesn't really reboot completely because otherwise I would have been forced to unlock my Sim-card.
I'm rooted and I've tried different roms, norma v26, batman, black dog, apocalypse.. but now I'm very satisfied with AstraDream UX. Also I've tried flashpoint kernel but I'm satisfied with Ramkernel. But it doesn't matter what I run, the problem always occur. For example, this morning I missed my alarm clock.
I attached a screenshot where you can see that the phone went off around 3 am, I locked it a half hour earlier. Then I woke up 07.50 am and as you can see, the battery drained a lot. I had like 95% then in the morning it was 60 something.
On betterbatterysaver I can't see anything because it restarts its counting from boot, but on GSam, it says that since full charge, the device been on 4-5 o clock am. But it was full charged at midnight.
Someone who know about this problem? Or someone who know a good log program so I can see what's going on?

Isaac_T said:
I finally upgraded from S5 to Note 4, I've had my phone now for 2 weeks but I have a problem!
If the phone is asleep (I mean screen off and I haven't touched it) after around 2 hours, it's like it's powering itself off! Because when I put the screen on, the samsung boot logo comes on, not the first galaxy note 4 screen but the second one. After that I can unlock the screen, so it doesn't really reboot completely because otherwise I would have been forced to unlock my Sim-card.
I'm rooted and I've tried different roms, norma v26, batman, black dog, apocalypse.. but now I'm very satisfied with AstraDream UX. Also I've tried flashpoint kernel but I'm satisfied with Ramkernel. But it doesn't matter what I run, the problem always occur. For example, this morning I missed my alarm clock.
I attached a screenshot where you can see that the phone went off around 3 am, I locked it a half hour earlier. Then I woke up 07.50 am and as you can see, the battery drained a lot. I had like 95% then in the morning it was 60 something.
On betterbatterysaver I can't see anything because it restarts its counting from boot, but on GSam, it says that since full charge, the device been on 4-5 o clock am. But it was full charged at midnight.
Someone who know about this problem? Or someone who know a good log program so I can see what's going on?
Click to expand...
Click to collapse
Looks like you've got the dreaded emmc problem! Search and you will find!
Sent from my SM-N9500 using Tapatalk

robmeik said:
Looks like you've got the dreaded emmc problem! Search and you will find!
Sent from my SM-N9500 using Tapatalk
Click to expand...
Click to collapse
I don't think so, because everybody who have that problem describe that their phone reboots completely several times or they can't boot or they get error message. Also I checked emmc check and it passes. My phone only reboots if the screen has been locked for more than 2hours, and it doesn't completely reboot, just a fast reboot.
It's like it's not completely off because I can press home button, then the phone starts from Samsung logo and then I'm in, no sim card pin either.

if you leave it plugged in does it reboot after few hours of inactivity? If not then maybe try another battery.

raul6 said:
if you leave it plugged in does it reboot after few hours of inactivity? If not then maybe try another battery.
Click to expand...
Click to collapse
No, plugged in it doesn't reboot. I was thinking it was a battery thing, because one day it suddenly fast drained from 25% to 15% and then suddenly it died.
So I got a second battery when I bought the phone and I tried that one, and I got a better battery life and I thought no reboot problems.
But then, during a call after around 1hour, it did the same thing and rebooted to the samsung logo. Also during another call, when I unlocked the phone and opened Textra it rebooted.
Another day I saw it reboot during inactivity for around 15min after a full charge and now yesterday it rebooted when I was going to enter Google Home.
So now I'm back at stock and running stock kernel, so far so good.

You should try wake lock application and use partial wakeup to keep your device from freezing