Related
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Are you using apps2sd?
No, I'm not using the apps2sd feature.
The lockscreen text showed "No service" and the notification bar icon showed the same. The "phone" application was the only one that would attempt to restart after being forced closed. After a second fc though, it would apparently give up.
Oh, and just remembered one other oddity.. Once booted and all force close messages removed, attempting to turn on the mobile network resulted in a hard reboot. I really didn't expect anything since there was no service link, but I was just clicking various shortcuts to see what did or didn't work.
Good part is that a Nandroid restore saved the day, so it's more of a curiosity at this point to what the root cause might have been.
I wouldn't have thought that a battery drain could have corrupted the apps or prevented the root filesystem from mounting.
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
mkhopper said:
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Click to expand...
Click to collapse
oddly enough I've had a similar experience. it was 2 days before christmas and i was doing all my last minute shopping. heavy use of the phone caused the battery to die, so i just threw it on my car charger. it booted, but REFUSED to get any data at all (i didn't run into any fc's, however). I rebooted it 3 times and each time the issue persisted.
I was running the AOSP 2.0 build at the time, so i flashed my backup of 2.1 and everything was fine from there...
patches11 said:
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
Click to expand...
Click to collapse
Hmm, good possibility there. Just did a count and I do have 85 apps installed.
(whoof, I had no idea the number had gotten that high. just too many useful apps for this phone.
Had my Verizon 7.7 i815 since 4-30 and love it except for one issue - it reboots at least
once a day usually when its connected to the charger.
I need help figuring out if this is a hardware issue so I can just exchange it or if is
software/other issue that I can resolve myself.
When it reboots it goes to a black screen with a single white dot in the center.
It is playing the reboot jingle when this happens.
Sometimes it will bootloop and I have to press the power button for a few seconds to
reset the tab.
Honeybar is installed and AdwLauncherEx is the launcher.
I have tried booting to stock recovery and clearing the cache and did a factory reset - didnt help.
The tab is rooted.
I also removed the Sandisk 16gb microsdhc card after a reboot at 5 am because I had read about users who were having issues with their tabs until removing or switching out their sd cards. The tab went without rebooting after that for 19 hours until I installed
Hidebar. After installing hidebar the tab rebooted twice within a minute so these two instances may be because of that app. I uninstalled it after that and went back to
Honeybar.
I have only experiened a white dot reboot when trying to swap the phone.apk (it was a never ending reboot). I otherwise haven't had it reboot on me. I don't use any bar hiding apps.
Sent from my SCH-I815 using xda premium
Just to be clear my tab was having the reboot issue long before
I installed hidebar - I only installed hidebar tonight and have
owned the tab for a week.
I am however able to cause the reboot consistently with hidebar.
Well the reboots started again after almost an entire weekend reboot free.
Going to exchange it at Verizon for another 7.7 tonight.
Good luck! hopefully the new one is error free.
I've had the same issue with mine, also a vz 7.7.
It was happening in a loop the other day and I managed to capture a video of the entire sequence.
I don't actually think this is a reboot but instead seems to be more of a screen and radio lockup.
I get the little dot in the middle of the screen. After 20 seconds or so the tab goes back to the lock screen. Once unlocked it has to re-connect to either Verizon or Wifi.
I tried disabling the wifi and 3g/4g networks and this seemed to improve the situation but yesterday I was able to get it to do the same thing with the radio's disabled so probably not chip related.
I'm still within my return window I think. Seriously considering returning the thing mainly due to this problem and the lack of ICS.
Had a GT8.9 previously and even though the screen isn't quite as nice it was a pretty great tab and cost half as much *and* can access the awesome AOKP ICS rom.
--tr
Yep, development for this tab is non-existent at the moment.
I'm stickin' it out tho and hoping for CM9 sooner or later.
Same here. I can't find a pattern to what triggers it. The first time i was installing a bunch of apps from my computer via Google Play (not tethered to PC). I pull my microsd and sim and it continues for several cycles. Did a bunch of the stuff you did also w/ clearing the cache and actually the first time i couldn't get it out of the loop (it would actually get into the desktop where it looks like it would be ok, then suddenly screen w/ the white dot in the middle and looping again). Never got close to depleting the built-in storage, so that's not the factor.
Sometimes I can get it to stop by turning it off by holding power down and turning it back on again. It doesn't happen a lot, but it's freakin annoying when it starts.
I don't have honeybar, but am running ADW.
Wow, good to know others who are going through the same issue...I thought I was the only one! I still have the reboot loop issue even after performing a hard reset. For me, the reboot loop only occurs when I'm on a cellular connection. If I'm on wifi or on airplane mode, it doesn't happen. I'm well past the exchange/return policy so this is extremely irritating.
Personally, the most frustrating thing is that my tab will be fully charged at the start of my day, then in my bag for the morning while I'm at work and then, when I take it out to use it, the battery is completely drained because of the reboot loop!!!
I'm hoping an update (ICS?) will fix the issue but I'm not holding my breath for it...
Same issue here. I am rooted, and originally thought the reboot was from Gesture Control app (awesome app!) when hiding navi bar. But after reading this thread, I'm not so sure.
I've only had the reboot loop once, here is my setup when it happened....
-had just unplugged from charger after full charge
-Mobile data was off, Wifi was set to sleep....never when plugged in..
-The device kept rebooting, so I powered off, went into recovery, wiped cache. I also turned off Gesture Control app functions (not sure if this was necessary however). This seemed to stop the reboot loop.
Would be nice if we could keep gathering info on the conditions that cause this, and potentially find a solution. It sucks having a dead tablet because of this issue.
My 7.7 does the same thing. I don't use the tab constantly, but I do notice the reboot on a fairly regular basis. Same symptoms as everyone above, except for me it doesn't go into a loop, it just reboots once with the white dot and then comes back fairly quickly, so not really a full reboot. I don't see the Verizon & Samsung splash screens, just the white dot then the login screen.
Mine is not rooted, has the stock ROM, and does not have any UI enhancing apps or mods. It's pretty much stock other than having applications installed, and nothing that really runs in the background because I have Advanced Task Killer kill auto kill every 30 minutes.
Not that big of an issue for me right now, but would definitely like to see it resolved.
gawd! It doesn't happen a lot, but when it does it's friggin annoying. Yes, it's the white dot and doesn't show the full bootup splash, kinda just goes to the desktop again seems ok for a minute and then boom- black screen w/ dot in the middle and it starts over again.
This last bout was pretty bad and it didn't respond to shutting it completely down by holding the power button and letting it boot again, which has sometimes fixed this in the past when it's looping like this.
Can't tell what is causing it, at first i thought maybe a live wallpaper, the 64GB sandisk microsd card, or a faulty sim (sometimes my tablet says SIM not inserted, even if it is). I tried changing all of those but it still happens. I haven't found a pattern of usage or other type of trigger to make it do this though.
I've only ever experienced this when I tried adding in the mms and dialer app from the GSM 7.7. Otherwise my tab has been rock solid.
Sent from my SCH-I815 using xda premium
Ok guys. I don't post often since I can usually find my answers by lurking the forums....but I'm at my wits end here. My 2012 Wi-Fi nexus 7 all of a sudden started acting funny one day. It would freeze u randomly, then reboot, then get stuck in a boot loop for about 10-15 minutes, then boot up, then freeze after about 1-2 minutes of use and repeat the whole process. This was on stock 4.4.2. I've since tried using the toolkit to reflash stock, fix bootloop, unlock and root...all of which I was able to do. None of which helped my issue. Although flashing AOKP DID seem to fix it for about an hour.
Anyway, I gave up on it for about a week and came back to it this morning. Although it wasn't even going to te google boot animation, just stuck on the google logo. So I reflashed stock 4.4.2 again. Now I'm back to square 1. So it boots and will function for maybe about a minute or 2 (or less) before freezing and rebooting.
Is this device shot? I'm out of Google AND ASUS warranty now
I posted something in the big help thread yesterday (probably a mistake). Mine is doing exactly what you describe in terms of working for about 2 minutes before freezing, then rebooting. Mine is 100% stock 4.4.2. Never rooted, unlocked, etc. I have the adb stuff, but I haven't even attempted anything, because it seems so unstable. I don't want a partial flash to screw it up even worse. I feel slightly better knowing that someone else is dealing with exactly the same thing in a similar time frame, so maybe it is a software thing, not a totally dead unit.
Well I may have made some progress. Since the warrenty is up anyway, I decided to crack it open. I noticed the GPU was getting extremely hot for just sitting at the home screen. So I enabled developer options and turned on some monitoring options (the fact that it stayed on long enough to do this is a miracle in itself).
Right now I have some overlay monitoring on including cpu usage and gpu rendering (on screen as lines). I also checked the "stay awake" while charging option. It's been on about 2 minutes so far, although graphics performance is horrible atm. Almost like project butter is disabled and it's running at half power....that could just be the monitoring overlay though. We'll see what happens...
*Update*
It made it 21 minutes, but it did reboot again. On restart, the OS smoothness is back to normal, and it does seem like it goes longer stretches without restarting now, however the issue is obviously still there. I should add that the back cover is currently off. which is starting to make me think this has to do with cooling
9629464420
Okay....I just admitted defeat with this issue. Just ordered a replacement board for $30 because the resets are still happening. Upon reset, I can actually hear a part of the main board buzzing for about 5 seconds (not the speakers). Not to mention that prior to this issue, I was having a lot of wifi connectivity issues anyway. Hopefully the board arrives before my long bus ride to new york...
Thought I would share this here - though I believe this is effecting other Moto models as well.
The Moto app "CQATest" seems to be the culprit with major instability issues I've had since the Android Marshmallow update. Before the update, my phone was so smooth and fast. Then the update came, and I blamed it on Marshmallow. Screen response to anything was very slow. Sometimes completely unresponsive. If i tried to touch a notification in my notification bar, it might be 5-10 seconds later before anything would happen, and the app would open. Sometimes it wouldn't ever open at all. Or when Facebook did open, it might take another 10-15 seconds before it went to the item it had notified me about. The camera in particular was slow to respond - with visible lag whenever trying to take a video - or would just crash. The phone itself got into a fairly normal habit of rebooting itself several times a day. And on startup, sometimes it would take 3-5 minutes before it would finally get to the home screen. Simply unacceptable.
So yesterday I started Googling for answers, and ran across a thread on Android Forums talking about issues people were having with CQATest. I immediately went and found the app in the settings>applications menu, under "All Apps" - force stopped and disabled it, then rebooted.
Guess what? The phone boots normally again! And the general responsiveness and functionality are back to what it was prior to the Marshmallow update. I couldn't be more pleased right now - because I was getting very frustrated with what is a relatively new phone.
I'd be interested if others have experienced something similar? Or are having similar lag issues and try this solution to see if it works for you.
Mods - if this CAN be confirmed, it really should be shared with ALL Moto users who've been upgraded to Marshmallow and have similar issues. The Android Forums thread user was originated by someone on the Moto X for instance.
Thanks for your time and feedback.
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
No apparent issues with anything else since disabling it that I can see. And yes, I'm on a DT2.
Zeljko1234 said:
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
Click to expand...
Click to collapse
I have had CQA Test disabled before and after Marshmallow and notice no misbehavior. I also have been using advanced calling since i got the phone on launch day and have never had a problem with the call quality as others have.
CQATest not causing problems on my Droid Turbo(1)
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
GeckoDad said:
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
Click to expand...
Click to collapse
My DT2 was suffering from slow-downs for a couple weeks, then suddenly had the random shutdown and power-only-on-charge scenario yesterday. I was getting ready to do a factory reset.
On one of the reboots, I had a notification about CQA test. When I acknowledged it, I got notifications that "CQATest wants to access this," and "CQATest wants to access that." I denied them all and started hunting up this app I'd never heard of. That's when I came across this thread. I disabled CQATest, but still had the problem. I then remembered that the "old" Amazon app had just updated. I force-closed it, disabled it, and now the phone is back to normal. I see no need for CQATest, so I'm leaving that disabled, but I firmly believe that the Amazon app was culprit.
EDIT: I may have typed to soon. The phone shut off randomly twice today, requiring connection to a power cord to bring it back to life. It does, however, remain powered up upon disconnection (for now?).:-/ I did not clear the cache after deactivating those apps, though, so we'll see if that does the trick.
..
Hi there.
Backstory: My DT2 is almost 3 years old. I already had to send it back to Motorola once for a camera issue, but generally I didn't have any major performance issues for the first year and a half or so. Then it started to decline. Namely OS was taking longer to respond, battery life declining. Then when it was about 2 years old it began the random shutdowns. For the last several months I haven't really had the random shutdowns, however, my battery has been pitifully horrible at holding a charge, and it will usually shut down before the battery indicator hits 0%. First it was around 15%, gradually getting worse. Now it often shuts down between 30-40%, especially if I haven't been on battery saver since disconnecting from the charger.
Now today, I ran down my battery within a few hours to about 30% and it shut off, which was not abnormal. However, upon connecting to charger and attempting restart, the battery indicator jumped from 30 up to 40, then down to 4. Got a weird screen before startup that looked like a system error screen and was afraid it was going into factory reset without my prompting it. Pressed the power key once briefly and the phone went into normal startup, but when it turned on, CommServer was stuck in notifications bar and battery indicator was stuck at 3%, similar story to the others in this thread and others.
I disabled the apps suggested by GeckoDad, and so far the phone can operate, but I've had it plugged in for maybe 30 minutes and it's still hanging out at 3%. Was planning to get a new phone soon, but had hoped to wait another month or two... Probably going to head over to Verizon this afternoon to see if they have any suggestions to keep my DT2 alive until I'm able to replace it.
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Sounds like your battery is on its way out. Have you tried a new battery?
Already mentioned in post above
tiguy99 said:
Sounds like your battery is on its way out. Have you tried a new battery?
Click to expand...
Click to collapse
QCube said:
I've tried everything, bought a replacement (genuine) battery and not fixed it.
Click to expand...
Click to collapse
Earlier in the week I had an error I've not seen before. Phone restarted and went to black screen sort of looking at a recovery screen with android logo and in the centre of the screen was the message
"Kernal Panic" with some information on the top. This only has happened the one time and hasn't happened since. Took the battery out and restarted again...
Try hardreset or flash via odin
Krprem said:
Try hardreset or flash via odin
Click to expand...
Click to collapse
How do I go about doing either of these....
Still happening and it's driving me insane, It won't last me until the end of my contract (January)
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
ithehappy said:
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
Click to expand...
Click to collapse
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
phonepie said:
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
Click to expand...
Click to collapse
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
grizzylemon said:
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
Click to expand...
Click to collapse
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
While upgrading a phone, especially for major upgrades like from LP to MM, OTA method should always be avoided. You MUST do a clean flash of the ROM, otherwise you are bound to have problems. 80% of time people complain because they didn't flash the ROM cleanly, so whatever you want to do now, do it, but if it doesn't solve it (very likely it won't), then kindly flash the ROM via Odin after a full wipe. And if even that doesn't solve it then its hardware.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
phonepie said:
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
Click to expand...
Click to collapse
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
QCube said:
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
Click to expand...
Click to collapse
Are you able to wedge a folded small piece of paper between the bottom edge of the battery and the phone to make the battery fit tighter? I mean it's not good to have a loose battery. But I can't see how that would cause the screen to stay on. If anything I would think it would cause the phone to shut off or reboot.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
grizzylemon said:
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
Click to expand...
Click to collapse
why don't you reflash you device with supported PIT file and stock F.W ?
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Aside from the previously proposed wake lock solution, members in the T-Mobile Note 4 threads have experienced limited success with a downgrade to LP from MM.
From my reading, these issues seem to be common across all Snapdragon models, not to say it Exynos is excluded (I don't frequent Exynos threads).
himuslg123 said:
why don't you reflash you device with supported PIT file and stock F.W ?
Click to expand...
Click to collapse
I tried that and it didn't work for me. The only surefire solution is a replacement device, but even then there's no guarantee the device won't start acting up in the future.
pls help stuck in download mode
this is the issue I'm getting...I did a complete data wipe using twrp...now stuck on this screen...cant even push files...device not recognized in adb or fastboot mode....
what to do...??
imgur(dot)com/a/gKPaL
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
hathertonwood said:
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Click to expand...
Click to collapse
Wow, that sounds promising. I'm sending mine for replacement, and although I'm not getting a new MB installed, hopefully the incoming unit will be similar in performance to yours.
ithehappy said:
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
Click to expand...
Click to collapse
Your reasoning sounds plausible, but my phone suffered similar issues and I only flashed my unit 2-3 times in the 14 months I had it.