My stock S7 exhibits random reboot behavior. 1-2x per week. Once in a while it happens 2x in one day. Once it a while it happens at the most inopportune time, like when I'm trying to take a picture of an event. When the reboot occurs usually it boot loops several times (and the phone gets warm while this is happening) and then finally stops. For the first year or so of owning the phone, no reboot problems. I did see the unmounted SD card notification issue that others reported (with a Samsung SD card). A while after the nougat update and after the 1 yr warranty period of course....random reboots. Also after the boot loops stop and I'm able to use my phone again, my Spotify login is lost and I have to re-download my playlists that I had saved locally. This is a real PITA if I'm traveling and not near any wifi connection.
Any ideas?
I've done the following:
- factory reset twice
- removed the SD card, not using it anymore -> I could consistently get the phone to reboot when scrolling through my pics in google photos. I do not get this behavior anymore with the sd card removed
- install a minimal amount of apps
I've read countless search results from Google search results and nothing has solved my problem. I'm past the 1 yr warranty period. I called a local shop and was told the cost of replacing the mainboard pretty high, I'm better off just getting a new phone...which I would like to avoid. Today I disabled the built in weather app to never refresh. I have little hope that this will fix my problem, we'll see.
I don't have any launcher apps. No games. Basic apps like Bank of America, Evernote, Flixster, Spotify, Swiftkey, Todoist, Logitech Harmony, etc. I disabled the built in Amazon app and installed the Amazon app from the google play store.
I have the same problem. Also after almost 1 year I am now getting random reboots. Especially but not exclusively uwhen using google maps. Mine is still under warranry.
Update: did a factory reset via recovery, working fine again.
Overnight while charging, my phone decided to bootloop until the battery died. Woke up to a warm phone that would not power on for about 20 min. I put the phone on a gel ice pack and now it's finally on. Uninstalled and disabled a bunch of apps, always on display, bluetooth etc. Just need this thing to stay alive until I can trade it in for the new Pixel.
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.
Hi Everyone,
I'm just received my AT&T Nexus one last night. I'm upgrading from a Touch Pro 2 and was excited to try Android. However, I have already encountered a very troublesome and annoying issue with the phone. After setting the phone up with my Google account I proceeded to start to become familiar with the phone and programs on it. One of the applications I was interested in using was Google Maps and navigation. I opened the application and browsed around the map for about 30 seconds until the phone spontaneously rebooted - showing the 4 color X logo for about 2 minutes and then continuing to boot into the operating system. I wasn't sure what happened so I tried to continue using the phone as usual, but this quickly became rather frustrating.
I had been able to use all the other applications on the phone without any issues. However, any time I opened the Maps application for about 30 seconds or so the phone would reboot. Sometimes it would come back into the operating system but other times it would sit at the 4 color X screen for at least 5 minutes before I pulled the battery to reset the phone. After this happening a few times I decided to try a factory reset on the device. Again, after this had finished and I used the maps application the phone rebooted after about 30 seconds of use.
This morning I was hoping my luck had changed and I wanted to see how the navigation application worked. I set the phone up to navigate to my workplace and began my drive. However, as I feared, the phone promptly rebooted after about 30 seconds of use (those 30 seconds seemed promising, if I could actually use the phone). The operating system came back up and I decided to give it another shot. Unsurprisingly, the phone once again rebooted after about 30 seconds of maps/navigation use. Even more frustrating, upon reboot the connection to the cellular network does not always come back online. Sometimes turning off the phone and turning it back on again works but other times I have to power off the phone, pull the battery and SIM for at least a minute, and try again.
This problem is extremely frustrating since the rest of the phone seems to work properly. I can use all of the other applications, send email, SMS, make calls - all the other things I would want to do on the phone. However, the maps and navigation feature was a huge draw for me to this phone and I am very frustrated that it is not working properly. While trying to figure this issue out I have already done 4 factory resets and even tried using the maps application before setting up my Google account, but I have not been able to find anything to keep the phone stable while using maps/GPS.
As of right now the phone is sitting back in the box ready to be shipped to Google/HTC/whoever support (if they ever get back to me). This is one of the most frustrating experiences I've had with a phone, and coming from a Windows Mobile user that's saying something. I tried to do a lot of searching online but couldn't find anyone else who had the same kind of problem that I was reporting. I have two friends who also own N1's (on Tmobile) and they have had nothing but great experiences with them. Does anyone know of what could be causing this issue and any way to fix it?
Thanks in advance!
That is crazy! Sounds like a bad lemmon... more likely the maps program didn't install correctly when it was flashed at the factory... have you tried using it with GPS turned off? This would isolate the issue to whether it is the maps app, or the GPS unit itself.
In either case, I would have the phone warranty swapped. Even if you could just re-install Google Maps, and it would be fixed, I would still be worried it was something more substantial. If you wouldn't be worried, and a re-install of google maps fixes it and that is good for you, there are places to get the .apk for google maps. I am at work, so no link is possible to a download for the google maps app on my end right now.
I agree that there is probably something wrong with the hardware. I did notice that there was a maps update available in the marketplace (sometime between the 2nd and 4th factory resets) but upgrading didn't seem to make a difference. I have contacted both Google and HTC support hoping that they will offer me a replacement device. However, I'm worried that the US holiday on Monday may slow my progress on the issue.
Thanks for the tips anyway!
Welcome! I would just demand that they declare it Dead On Arrival... that way they will ship you a brand new unit, then you return yours in the pre-paid packaging they send you. You probably won't get it until Tuesday/Wednesday because of the holiday.
I've had my Galaxy Tab (Verizon edition) now for under a week. Naturally, that means I've been installing apps on it every day.
Last night an issue cropped up that turns out to be a deeper problem than I thought.
To start, I'd randomly see a force close for the built-in Google Maps app. Force closes aren't necessarily unusual, but this was force closing every 10 seconds or so. And it wasn't running. No sign of it in any of the task manager or application manager or running services areas. Yet, it was crashing.
(Don't worry, the fun doesn't end there.)
So, I suspected the last couple of apps I installed and uninstalled them (more on this later). The problem didn't go away. Around this time, other apps started crashing randomly -- often without a force close (much more like how iOS apps crash -- a return to the home screen).
The crashing always coincides with a single short vibrate then a triple-vibrate about 5 seconds later when the app closes or the force close dialog comes up. This happens in nearly any app -- from the home screen (less common) to the Browser, maps, settings, gmail, 3rd party apps, etc.
But wait, there's more...
I wasn't observant enough the first time to notice that the suspected apps were never uninstalled. Now no app will actually install. When I perform the uninstall, everything seems fine. Until I reboot. Then the app is back, fully functional.
None of the apps are installed to the SD card. The device is not rooted. The device claims just over a gigabyte of internal memory free, and slightly under half the SD card free.
Anyone see any of this behavior? I'm hoping to avoid doing a factory reset -- while also unsure that it would even do anything if something else is wrong. And the two issues (crashing and uninstalls-not-sticky) aren't necessarily related.
This isn't my first Android device, either... I haven't seen this or anything like it on the G1, N1, Droid, Evo, Archos, or any other device, for that matter.
Thoughts? Ideas? Musings? Questions?
[Update: Device was replaced. If it wasn't a hardware problem, it was still good enough to prompt the retailer to replace it. They easily accepted, "The factory reset doesn't work." as a reason.)
Sounds to me like there is something wrong with the internal memory chip. I would return the device within the DOA warranty if I were you.
Seems that it probably is a hardware issue.
I tried a factory reset (which appears to be a very convenient way to boot in to recovery mode, BTW) and it was only able to delete a portion of data. All of the apps are still there, all the data, etc. (The SD card aside, the factory wipe doesn't touch that.)
So, back it goes for exchange!
I just started having the same problem today and I have not installed any new apps although I did update date my existing apps a few days ago. My phone is rooted but by your discription that's not the cause.
I did reset my phone and I formated my SD memory. I also use a code that I found to reset the phone to factory and reset everything. Non of this has solved the problem.
I'm still trying and I'll let you know it I have any positive results.
I'm on a Galaxy S Vibrant with 2.2 Firmware, Froyo and a 2.6.32.9 kernel
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
My Note4 was updated to Lollipop about 2 weeks ago and it was running ok until 3 days ago where it keeps on restarting, freezing up, not responsive etc.
The last application that I installed was "FACEBOOK GROUP" but I'm sure this isn't the problem because of the factory reset as explained below.
I have done a factory reset, but I reinstalled all the applications (except Facebook Group), but the problem still persists. It even restarting without it's being touched. Per day, it could restart up to 15 times.
Most of the problem appears when the phone goes into an idle state and won't turn on unless I do a battery pull (like Blackberry).
But sometimes it would respond from the idle state after a 20-30 seconds.
I did find an article that the motion and gestures are causing the unresponsive issue, in which I have followed and disabled all the motion and gestures, this doesn't help. Problem persists.
I have talked to the Samsung Tech support and they told me that I would have to bring it to the service center in Singapore (I live in Jakarta) and they would need to diagnose it. I did mentioned that I want a new phone but they said that they don't have exchange policy. This is really bad because Iphone has an exchange policy, why doesn't Samsung have one too??
Anyone in Singapore maybe have the same issue? or have a knowledge about the exchange policy?
Have you tried uninstalling Facebook Group from your Note 4? It seems to me that the Facebook Group App must be causing some sort of problem with your Note 4.
DarkGuyver said:
Have you tried uninstalling Facebook Group from your Note 4? It seems to me that the Facebook Group App must be causing some sort of problem with your Note 4.
Click to expand...
Click to collapse
After I did a factory reset. I didn't install Facebook Group
UPDATE 1 :
I uninstalled DU Speed Booster, and the problem seems to be better, but still hangs after unplugging from charger.
Does anyone use DU Speed Booster with Lollipop?
bankir said:
UPDATE 1 :
I uninstalled DU Speed Booster, and the problem seems to be better, but still hangs after unplugging from charger.
Does anyone use DU Speed Booster with Lollipop?
Click to expand...
Click to collapse
OK, seems like DU Speed Booster may have messed with the system settings of your phone somehow. Are you using the stock firmware that came with your Note 4?
DarkGuyver said:
OK, seems like DU Speed Booster may have messed with the system settings of your phone somehow. Are you using the stock firmware that came with your Note 4?
Click to expand...
Click to collapse
Yes sir, it is the stock rom.. and it's not rooted. Still original except that it has been updated to Lollipop.
Uninstalling DU Speed Booster seems to make it a little better, but occasionally it still freezes and restart but it's not as many times as before.
If the system setting has been messed up, then I will do another hard reset tonight and see if that would fix the issue. I'm tired of waiting for the phone to come alive after idle or when it restarts by itself.
UPDATE 2 :
I did a factory reset last night and left it to sleep while it was updating stock applications (I have not installed any of my application).
This morning when I woke up. I couldn't turn on the phone. It was frozen and it has a solid red LED light on the top left. This happens quite frequently before too. So I'm not sure what the issue is. Btw, my note 4 is the first batch. Bought it when it first came out.
I had to take the battery out and started the update again.
Then it got restarted when I tried to swipe my finger to enter the homepage.
Why doesn't Samsung give an exchange policy? their rival Apple does..
Yeah, I think you need to return your device to Samsung for repairs. As for why Samsung doesn't have a exchange policy, because retailer's tend to have a exchange policy where if they can't fix your device they will replace it with another one. Since retailer's give you a 1 year standard retailer's warranty with the purchase of any electronic device. Apple has a exchange policy, because as well as being a device manufacturer they are also a retailer for their own devices.
My Note 4 has been a lot better since I reseated the SD Card. I did that before too.
I'm starting to think that my SD Card was not reseated properly causing the system to hang / freeze.
As of now, I think the culprit is the SD Card.. I will monitor and update again.
I think I posted too quicky.
The problem still persists, so it is not the 'reseating' of the SD Card.
I notice though, the problem with hanging, restarting, MOSTLY occurs when the battery is less than 40%. And sometimes, it won't even start / turn on even after I take out the battery. But when it is succeeded, sometimes, it would come out with the message (shown in the attachment). Every time this comes out, I have to take out the battery and wait 30+ seconds before trying again.
I really don't know what is the problem with the phone and this phone is bought overseas. Local Samsung Store can't fix it because they don't have the base band or software.
Please note that this phone has never been dropped / root. I have taken care of it carefully.
I'm really disappointed.
It does seem like a hardware error either with the internal memory chip or the battery. You could try replacing the battery to see if that would fix the problem, I doubt that would work. But I would prefer to just send it back to Samsung for repairs as they have the equipment to fix the problem.
Alternatively you could install Kies 3 from the Samsung website onto your computer and use that to do a firmware reinstall of your Note 4 and see if that helps. If that doesn't work then you really don't have much of a choice other than sending back to Samsung for repairs.
Similar Problem
My Note 4 has locked up three times after a full charge.. I noticed a solid RED LED after the phone fully charged and attempts to turn it on are unsuccessful, it's frozen. Nothing I do can wake it up short of removing and replacing the battery. The Lollypop update was done over a month ago so I doubt that is the cause. I'm still checking things out but it has occurred to me that if this happens to the S6, what would one do if you can't remove the battery?????