Related
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
I would like to keep this short and sweet so...
Basically heres the low down: I got a G1 almost a year ago, got into Rooting/flashing 7 months ago. I noticed in the beginning almost every rom was giving me a problem, Freezing up, hanging for long periods of time, etc. I eventually found a very nice, stable rom thats been lasting me for about 6 months but as of late was being horrible. Force Closing everytime I got a text message, REALLY Hanging for long periods of time, freezing up. Etc.
So I finally got FED UP, and decide it was time for a change, so I grabbed MLIGN 3.3v having seen so many good reviews and what not, thinking it would be the remedy to my poison. I cried. So in short, here is whats going on:
1. It seems to only wanna cooperate when Plugged into the USB, which, isn't too practical.
2. When not plugged in, it is NOT sluggish, but when loading into apps I've noticed it will hang for quiet awhile or completely lock up to the point only popping out the battery will work.
3. I haven't noticed it yet, but on the old ROM it would randomly shut off during phone calls; which leads me too....
4. When ever I shut the screen off (by pushing endcall) it seems to freeze and lock up and eventually either SHUTOFF or REBOOT into a SHUTOFF of the phone and refuse to turn back on until it has been plugged into the USB, or enough time has passed for it to 'forgive me' and by that, I mean randomly work again.
5: Various other things I cant think of right now.
So, basically thats almost everything. Whenever its plugged into USB though, it works like a charm (for the most part).
Would a problem with my Battery be the case? Which, would be awkward but a possibility.
Or did I just do something wrong?
I made sure to factory wipe the phone twice, even 3 times on the last go, I updated the ENG.SPL and Radio every time I tried to reflash just to make sure.
I partitioned my SD Card for 32MB Swap; 512EXT2 (and 7xxEXT2 I forget what it was) and I also upgraded it to EXT3, which showed some improvement... I believe.
So, I just would like to have my phone working, in a peaceful, obedient manner xD.
Forgive me for the block of text, and all help will be appreciated. Thank you guys... I await sound advice
Try different ROM? See which one works best.
Like me, I found that SuperAosp is best suit for me (see my sig for DEV Site and Download, if you want to try it). It had been running fast and I had no issue, what so ever. Occasionally when I loaded apps that hogged the power usage it gets lags, but still good. FCs are at minimal to none (that's just because of the way I handle the apps). Once in a while I noticed that it reboot, when I tried to use the apps that hogged the memory (maybe that was the apps issue).
Only other thing I recommed is to download a different launcher, because the build-in ADW Launcher does not work too well in my opinion.
Another thing, if you wish to keep the ROM you had. I would suggest to change the partition size. (IE: Catch [128MB]/Ext 2 or EXT 3 [1024MB]/ FAT32[the rest]) Now I know other people might say that it's overkill, but to me my G1 performance it great.
I've tried multiple roms as of late, and the one I like the most does happen to be MLIGNs... everything seems to be working correctly for the most part with the exception of what I listed above... Now on the like, 23rd reboot most of the sluggishness that was there before is gone, and everything is pretty much being cooperative, with the exception of like the weather, which isn't updating properly but I can live with that. What I cant live with is the fact that this ROM when not plugged in, will freeze up when in the lock screen, a few minutes after it has darkened and gone black and wont respond at all. Or I'll unplug it and just do a test, swipe left, right for a good minute or two, go into apps and It'll just SHUT OFF. Maybe it really is the battery? I'm unsure. When I look at the battery it does look quiet bloated... I am unsure...
I'm gonna try to set it to what you recommended, and see if that works...
I don't think it's the battery.
Have you tried reformat/partion your SD card (be sure to backup your data first). See my last comment on sizes recommendation for each partition.
Also check on the swappiness setting.
Mhm... so I went back and followed everything you told me to do, including repartitioning to the exact file sizes you told me. (Also I'm guessing Cache meant Swap) So I set everything up and its really blazing fast and stable.... until I remove the USB cord. Then it shuts off, freezes at lock screen when the screen is dimmed to black, and will just randomly shut off while doing things (especially when trying to get into messages)
Also if it helps, I have a Class 2 8Gig SD card, and my Recovery is Ra 1.5.x(I forget.) I'm completely confused... I dunno what to do... I would really like this to just work and stop being a hassle D:
Hmmm, Try reading this thread, http://forum.xda-developers.com/showthread.php?t=1010932
See if it helps.
Nothing :/ Its okay... I'm gonna go play around with other roms, completely re do my phone, make sure everything is updated etc. Then go from there.
Thank you anyways, you were a big help, reguardless of my phones triumphing retardism
Long time lurker, first time poster.
I woke up today to see my captivate screen showing blank screen (active black screen with buttons lighted up) being unresponsive. It was on it's charger from the night.
I pulled the battery to shut it down. It rebooted. I thought nothing about it until I tried to use it about an hour later.
I have had it on stock Froyo, with no root. Never have flashed any other ROM besides updates through kies.
Problems and things I've noticed so far:
No puzzle lock screen. Can't find it under "set screen lock". Only None, Pattern, PIN, Password available.
Home button and search button do not function(they light up like they are pressed, but not action occurs in any apps or home screen).
No data. Usually i'd see edge or 3g, but I have no data connection.
Text messages wiped. None available through "Messages"(though call log shows history of messages).
Keyboard was on stock android rather than swype(since changed back to swype).
Holding power button only shows "Power off" option. Before there was at least Airplane mode.
GPS was on(I hardly ever use it).
Location settings seemed to be default("use wireless networks" was unclicked)
Most other settings/app data seems fine.
About phone info:
Model Number: SAMSUNG-SGH-i897
Firmware version: 2.2
Baseband version: I897UCKB1
Kerner version: 2.6.32.9
Build number: FROYO.UCKB1
Click to expand...
Click to collapse
Other related things:
Day or two before I received a text message from AT&T to download Kies and use Froyo(Don't remember exact wording, lost the text message, but something to the effect it looked like a mass mailing text to update to Froyo using Kies). I was already on Froyo(flashed as soon as I found out it was available few months back).
I also got a text message about downloading their at&t app to manage my minutes and pay my bill(also already had that app).
My Captivate would randomly freeze/unresponsive a few times, but I didn't think much of it.
Google Music app seemed to randomly start playing the audio file i paused(just in my pocket, or once when i put headphones in to make a call).
Searching the forums, haven't found too much related.
One thread suggested using "home switcher", which I have tried(both Froyo and regular versions, though can't press home button for Froyo version). Neither seems to know what my default Home App is, but it only sees TwLaucher(I only have TouchWiz).
Tried installing an alternative launcher(ADW,LauncherPro), still no home/search button.
I'm without my computer for the weekend, so I can't backup my files and reset to factory just yet.
Anyone have any thoughts to fix this or know what may have went wrong?
I might finally make the jump to a Custom ROM if it'll fix this.
Yes, you should either flash a custom rom or do a factory reset. I will say an event similar to this, also involving text messaging, is what made me make the leap to Assonance, and then Serendipity, and I haven't looked back.
Sent from a state of Serendipity
At the least, try a master reset.
You're not alone....
Two Saturdays ago, I woke up, grabbed my phone to see what time it was and my phone was going haywire. It as blinking, flickering and rebooted on its own a couple of times...without me touching it.
When I DID manage to access the phone after a reboot there was no connection. I couldn't call, send/receive texts, nor could I access most of the features (during one of the haywire moments, the phone popped open my "Gallery" folder and started running a slideshow and then shut down. Again, all without me touching it!) There was a distinct blue circle with a slash where the 3G bars used to be on the top right corner of the phone.
I did a factory reset and didn't help. Wiped everything off the phone, but the device was still going nuts.
I got the phone in mid-December and have absolutely pampered that thing. Never dropped, never scratched, never abused. So I was surprised when I took it into the AT&T replacement center that the lady told me that my battery was wet! Not the phone, but the battery. Those two white-that-turn-pink indicators are so close to each other on the phone that I can't see how one gets wet while the other doesn't.
So they give me a new phone. One thing I noticed right away was that my data usage went WAY UP with the new device. To put it in perspective, I used 100 mb of data in 29 days and 64mb IN ONE DAY with my new phone. I thought it may be a one-time fluke, but it's not. I am only 10 days into my new month and am already at 164mb out of 200mb in my plan. I have NEVER used 164 mb in the 6 months previous, let alone in 10 days.
Fun's not over yet. I noticed a lot of crashes and "Force Closes" with the new phone too. I didn't even have any apps downloaded yet and things were still crashing. Last night I pull my phone out to take a picture and...nope. Screen was all kinds of whacked out and it crashed. And still does now every time I open the camera function. I managed to get in camera mode fast enough to do a reset, but didn't work. The screen is fine otherwise. So looks like I'm back to A&T tomorrow for another round.
I'm glad you posted this, cause the same morning all this happened -- literally, within 10 mins of me waking up -- my computer (brand new - 2 days old) went berserk and shut off and my stereo started flipping channels, turning the volume, treble, bass up and down..BY ITSELF without me touching ANYTHING! It was pretty freaky. I wondered if I was struck by lightning the night before.http://media.xda-developers.com/images/smilies/eek.gif
I was finally able to get back home today and do a factory reset. This (somewhat) solved the problem. Everything is mostly back to normal(home button and search button work on home screen, lock screen is there).
Lost a couple of game saves as I had no method to pull a save file(was doing adb pull on some known file locations).
I did run adb logcat before resetting, and home button and search button seemed to trigger something, just not follow through(Search button did work in a card game as a forward button and home button worked in the kies app to exit, just never as a return to home button in apps).
I'll be looking to root and flash a custom ROM, especially root so I can do a proper backup in case anything like this happens again.
I just want to say thank you posting in q&a and doing research before and after your flashing started. Then searched after your problem. You're a new member of a breed that are few and far between. I will hit your thanks when I get on my computer, app doesn't have it. You will go far here.
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
For the last few weeks, my AT&T Note 3 has started randomly rebooting. It can happen when I'm viewing email, when the phone is in my pocket, or even in the middle of the night when it is just sitting recharging. The rebooting is roughly once per day: somedays more than once, other times it can go over 24 hours. The problem seems to have started after I updated to 5.0. I have tried a factory reset, but the problem came back. I called AT&T support and they said that they've had a lot of problems with Samsung devices after the 5..0 roll out, with random rebooting, or the Bluetooth failing, or the WiFi failing. They said that they need to replace the Note 3, but because it is over a year old I must pay $100 for the replacement through Asurion (I have been paying the insurance fee).
Searching on line has not provided much on this problem. Does the AT&T comment make sense? If I need to replace the phone, shouldn't it be for free because the problem was caused by AT&T?
I'd appreciate any comments.
Note that I realize it could be related to an App I use being incompatible with 5.0, but I need to use my phone for work pretty much constantly, so troubleshooting which one (if any) is not practical.
Mine started doing the same thing about a week ago. Till then it was not having any problems with the 5.0 version.
They need to figure out the problem and push out a update. Otherwise it is like they don't care about us, unless we go out every year and buy a new phone !
Problem solved?
After trying a reset and cleaning checking the battery contacts didn't work, I looked for other patterns. It seemed to me that one of the most common times it rebooted was when I checked my email with the K9 email client - something that is always running in the background, and could have caused it to reboot when on charge overnight.
I uninstalled K9 and that didn't help - the phone rebooted after about 9 hours. However, since that reboot it has now gone nearly 48 hours without rebooting. Maybe I was right about K9 and uninstalling it wasn't enough - I should have also manually rebooted the phone.
The phone has been rebooting at random times, sometimes as short as about 5 hours apart and sometimes more than a day apart. It could be that right now I'm at one extreme and it will reboot randomly today. But if it makes it through tomorrow morning without rebooting then K9 was probably the problem.
It has now been over 72 hours since the last reboot, which does suggest that the original problem was the K9 email client, crashing and forcing a reboot on the phone after the Android 5 update.
Problem NOT resolved!
A few minutes ago, roughly 76 hours after the last random reboot, when I thought that the problem was resolved, I heard the reboot tone coming from my phone that was sitting on the table.
So, while removing K9 reduced the frequency of the reboot, it did not solve the underlying problem.
Use Titanium Backup and backup all user apps and data. Factory reset and reflash stock if you want to take the extra step. Use standard Google and Samsung apps for a while. Do not restore accounts or system data automatically. Removing and reconnecting accounts and clear data for an app in app manager are always good quick troubleshooting options. Restore apps as you need them, if you really need them. Favor stability over extraneous features.
.......................................................
Galaxy Note 3 - AT&T (sm-n900a)
Since I removed K9 and rebooted the phone, it has only rebooted randomly once in 5 days: this was at 72 hours, and now it has been up for 65 hours since then. Trying what you suggest would take weeks, given the current frequency of random rebooting. Plus, my phone is used for work constantly - I couldn't get by with just the Samsung and Google apps built into the basic phone image.
For the moment, I will just live with the phone as-is and hope that Samsung issues a new version of 5 soon.
Now at nearly four days since the last crash/reboot, or only one in seven days. At that frequency, it is certainly not worth the effort of trying to track down the secondary cause (it could take months), now that I know that K9 was the main problem.
It has been a while since I started this discussion, with no conclusion. The phone still randomly reboots - only once all of last week, but then it woke me up on a reboot at 4:30 am this morning, and rebooted again while I was checking Facebook at 7 am.
I'm having a rebooting issue as well with my Note 3. It started about a week ago and will do it many times during the day. I have tried wiping the cache partition, doing a factory reset and the other day I downgraded the software from 5.0 to 4.4.2 and rooted it and froze the over the air update from AT&T but still have random rebooting. I have had the reboot issue with and without the SD card installed so I know that is not the issue either. I was thinking it was a software issue so that is why I did all of the stuff listed but now I'm wondering if it could be hardware. I guess I'm just at a loss of what to try know and was hoping someone on here had any suggestions.
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
jeffp25 said:
I hope that with your additional post that we'll get some answers. One thing: does it happen when sitting idle on charge too, or only when not sitting idle? In the later case, it could be a simple as dirty battery contacts.
Click to expand...
Click to collapse
It happens both when charging and when sitting unplugged. I even tried swapping the battery for a new one and the contacts and also clean
Well, it was an idea. I did the same thing, buying a new OEM battery and hoping it would help. It didn't. But then again, mine often reboots at night (it woke me up at 4 am this morning), so I knew it was unlikely to be a battery issue in my case.
Yeah thanks for the idea but it seems like I'm running out of things to try
I feel the same. The only thing left would be to wipe out the phone and try it with nothing but stock, non-upgrades, apps. But I use the phone for work, and it can go more than a week between reboots (or less than a day), so that isn't practical.
I might just end up mailing my phone into Samsung to be repaired but now that I have it rooted is there any special steps that need to be done to unroot it? I was just going to do a factory reset and let AT&T android 5.0 do it's update if that will kill the root. I'm not worried about warranty since it is no long under warranty.
Maybe use logcat and letting it run and wait for a reboot to happen so you can see what is going on. However the logs could get big and it might not capture what happens right before it reboots.