Lately like the passed couple of months my Note 2 has been randomly rebooting like once every couple of days. Well, actually it doesn't exactly reboot its more like a sleep of death where for those that aren't familiar you go to turn the screen on and I don't know weather the phone went off or froze but it is non responsive. Like I said it really does not do it that often, not even really often enough for it to be an issue but I spent almost 800 dollars on this thing I don't want it rebooting or doing any of that.
I have had 3 smartphones in my day all being Samsung and they all did this starting with the Galaxy s2 which did it like 10 times a day. It was a really good phone despite that. Then I had the Galaxy s3 which would reboot occasionally, like this one not really enough for it to be an issue. Now with the note 2 I had had it since it dropped on sprint and when I first got it, it was rock solid. Now it is starting this. I am just wondering what anyone else thinks of the isssue. Am I the only one with the issue?
I am rooted and have been since like the second day I got the phone so I really can't say weather or not that has anything to do with it. It really does not seem to matter which ROM or Kernel I am on they all seem to do it every once in a while. All I can say is that my brother is an iPhone user and has had an iphone since the 4 and never once have any of his phones rebooted or locked up like this one does, and all my Samsungs have for that matter. I know its a little different since I am rooted running custom ROM's and all that but still for some reason when this thing does that it really irritates me, and I am just wondering if anyone might be able to help with the issue.
rbtrucking said:
Lately like the passed couple of months my Note 2 has been randomly rebooting like once every couple of days. Well, actually it doesn't exactly reboot its more like a sleep of death where for those that aren't familiar you go to turn the screen on and I don't know weather the phone went off or froze but it is non responsive. Like I said it really does not do it that often, not even really often enough for it to be an issue but I spent almost 800 dollars on this thing I don't want it rebooting or doing any of that.
I have had 3 smartphones in my day all being Samsung and they all did this starting with the Galaxy s2 which did it like 10 times a day. It was a really good phone despite that. Then I had the Galaxy s3 which would reboot occasionally, like this one not really enough for it to be an issue. Now with the note 2 I had had it since it dropped on sprint and when I first got it, it was rock solid. Now it is starting this. I am just wondering what anyone else thinks of the isssue. Am I the only one with the issue?
I am rooted and have been since like the second day I got the phone so I really can't say weather or not that has anything to do with it. It really does not seem to matter which ROM or Kernel I am on they all seem to do it every once in a while. All I can say is that my brother is an iPhone user and has had an iphone since the 4 and never once have any of his phones rebooted or locked up like this one does, and all my Samsungs have for that matter. I know its a little different since I am rooted running custom ROM's and all that but still for some reason when this thing does that it really irritates me, and I am just wondering if anyone might be able to help with the issue.
Click to expand...
Click to collapse
I have never had that happen. I'm running CM10.1 may or may not be the difference. Are you sure that the problem is not a app that you have installed? That would account for you having the same problem on different phones.
davidh59 said:
I have never had that happen. I'm running CM10.1 may or may not be the difference. Are you sure that the problem is not a app that you have installed? That would account for you having the same problem on different phones.
Click to expand...
Click to collapse
Hmm the only ones that I have had consistently with all those phones were the usual like facebook, twitter, titanium backup. I never messed with over or under clocking any of my phones or anything like that. Are there any apps that could detect a troublesome app that may cause a reboot? I have tried factory data resets but I always restore missing apps with titanium backup and never have just started fresh by re downloading everything, not sure if that makes a difference or not.
rbtrucking said:
Hmm the only ones that I have had consistently with all those phones were the usual like facebook, twitter, titanium backup. I never messed with over or under clocking any of my phones or anything like that. Are there any apps that could detect a troublesome app that may cause a reboot? I have tried factory data resets but I always restore missing apps with titanium backup and never have just started fresh by re downloading everything, not sure if that makes a difference or not.
Click to expand...
Click to collapse
Restoring with tibu across ROMs is frowned upon as it can cause issues.. I imagine its not good to restore across devices either.. Maybe starting with ur gs2 somethings didn't restore right and has been causing u problems ever since.. I would do a backup of ur current ROM, wipe everything and try starting fresh without restoring anything and see if that fixes ur problem.. Hope this helps..
Sent from my SPH-L900 using xda premium
sparytrainor said:
Restoring with tibu across ROMs is frowned upon as it can cause issues.. I imagine its not good to restore across devices either.. Maybe starting with ur gs2 somethings didn't restore right and has been causing u problems ever since.. I would do a backup of ur current ROM, wipe everything and try starting fresh without restoring anything and see if that fixes ur problem.. Hope this helps..
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Then what's the best way to restore apps across roms? Just start from scratch?
Sent from my SPH-L900 using xda app-developers app
rbtrucking said:
Then what's the best way to restore apps across roms? Just start from scratch?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
You can try ROM toolbox from the play store, but I usually just start from scratch when I switch ROMs and I definitely start from scratch when it comes to new phones.. Even if its a warranty swap for the same phone..
Sent from my SPH-L900 using xda premium
sparytrainor said:
You can try ROM toolbox from the play store, but I usually just start from scratch when I switch ROMs and I definitely start from scratch when it comes to new phones.. Even if its a warranty swap for the same phone..
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Well ya when I first got the note 2 and the gs3 I did start from scratch but over time I started just restoring apps using titanium backup. Ill bet that's why both phones were flawless for the first couple of months of ownership until I messed them up with my constant restores. Another thing I was thinking about is the way I said the gs2 would reboot the worst out of all the phones I ever had, when I got that one I had came from a HTC Evo 4g and when I put the sd card from the evo to the gs2 I didn't format it or anything. I am betting that had a lot to do with why that thing gave me so much trouble. I will try a complete factory reset, and just re download all my apps from scratch and see if that fixes the problem. I really appreciate the input.
I've hadn't had the sleep of death on the GN2. But I have had a the occasional freeze or reboot. Maybe one a month, probably less. It happens. Between running experimental apps or mods, and that developers developers--including Samsung or their contractors--can't test for every situation, it's not a big issue. Other than maybe having to do a battery pull, and divak and cache wipe in recovery.
As for the TB and restoring, especially on the first time run on the phone or rom, I find it best to install from scratch apps. I kept separate directories for different ROMs because of it. Plus, some apps just restore a bit off like Lookout and FlashPlayer; you can restore the app, but don't want to do the data. Some stuff, you can use the data restore after installing the app from Google Play or sideload with a new ROM without issue. Unfortunately, knowing with apps play nice in which situations is a lot of trail and error.
rbtrucking said:
Well ya when I first got the note 2 and the gs3 I did start from scratch but over time I started just restoring apps using titanium backup. Ill bet that's why both phones were flawless for the first couple of months of ownership until I messed them up with my constant restores. Another thing I was thinking about is the way I said the gs2 would reboot the worst out of all the phones I ever had, when I got that one I had came from a HTC Evo 4g and when I put the sd card from the evo to the gs2 I didn't format it or anything. I am betting that had a lot to do with why that thing gave me so much trouble. I will try a complete factory reset, and just re download all my apps from scratch and see if that fixes the problem. I really appreciate the input.
Click to expand...
Click to collapse
The freezing/rebooting issue plagued a few of my galaxy devices. My Epic 4G(GS1) and my GS2 would reboot/freeze/overheat all spontaneously and I never ran anything but stock root on either of them. I used tibu but never to restore from one device to another. My GS3 was fine for the few months that I had it with maybe a couple reboots but not enough that I would classify it as a persistent problem.
My N2 has rebooted spontaneously maybe 3 times since I picked it up on launch day. I've had it go into a unwakeable state a few times where pressing the power button won't bring up the lock screen forcing a battery pull. I've maybe had it freeze on me the same amount of times. Overall it's been the best phone I've ever had as far as stability goes. The AMC update was kinda wonky for the first few days after I applied it, causing my phone to lag a bit but it has since seemed to settle down and the phone runs like a champ.
I assume you're doing a tibu restore of app and data, maybe just try installing the app from the play store and then restore just the data from tibu and see if that makes a difference. I can only assume as others have said here that you have a rogue app that's causing your issues.
Good luck.
System apps are a no go. However I have restored all my apps from my gs2 and from rom to rom on the note and I have not had a single problem. But when in doubt just download fresh from playstore.
Sent from my SPH-L900 using Tapatalk 2
Thank you all for the replies, I have to say after doing a full wipe and installing all apps fresh everything seems to be working a lot better. No reboots or freezes, or SOD's in about 4 days (knock on wood)
my note 2 still keeps rebooting once a day.. n its really annoying!! please help
not rooted yet.. planning not to
Question
How do you warranty swap from one to a new phone is that possible if you a warranty from bestbuy.
Not sure if anyone is still experiencing problems but I'll share what I found in case someone else comes here looking for answers.
Is this possibly relevant to anyone's situation? The following thread talks about memory issues that certain models of the GN2 are prone to have.
http://forum.xda-developers.com/showthread.php?t=2093599
Related
I've racked my brain and searched the forums so I'm hoping someone has some insight here. Recently my phone has become unstable...I can't do too much in a single sitting without it rebooting. I've been on CM7 for a while now and had been trying the nightlies so I thought it was maybe that or just left over garbage from the upgrades so I decided to do a clean CM7 install yesterday (factory wipe). After I got through the setup and started to download gmail (1st non-stock app) from the market my inc rebooted. I flashed Chad's latest kernel thinking maybe it was a kernel issue...still reboots.
I then decided maybe it was the battery because at times I will get into a couple of reboots back to back and then the phone turns off and vibrates three or four times. But when I get the phone booted and check the battery temp it is maybe 98F which doesn't seem to be above average based on my forum readings. I then swapped batteries with my wife (unrooted inc) and we both launched plants vs. zombies and started playing. After maybe 10 min, I got my first reboot and then another a few minutes later so I just turned the phone off...she kept playing.
Now of course I have to point out my wife works for Verizon Wireless so I'm getting extra grief for rooting my phone and she is saying that is the cause since she never has reboots. Not that I want to prove my wife wrong, I really just want a phone I can do more than make phone calls on, but someone please tell me she isn't right. My reboots only seem to happen when I've had the screen on for a while...3 hour conference calls have no issues. Can you give me suggestions of things to try to help narrow down the issue? Thanks in advance!
Phone Info:
Baseband:2.15.00.07.28
Kernel: 2.6.37.6-incredikernel-gb-04192001
Mod Version: CyanogenMod-7.0.3-Inc
Build: GRI40
I get similar problems but it happens when i am watching youtube videos or playing games, or sometimes out of nowhere. Can't figure out and it is really annoying.
Copy sd to pc, reformat sd fat32, copy stuff back to sd. Helped a friend with hers.
Sent from my ADR6300 using XDA Premium App
Thanks I'll give that a try. I did try running the phone without a card at one point and it didn't help any.
AOSP Roms, like CM, interact with the sd on boot. Don't expect aosp roms to boot without sd.....
Sent from my ADR6300 using XDA Premium App
OK, performed the the SD format last night and just got around to running apps today. Again, I tried Plants vs Zombies and after about 20 mins the phone rebooted...I had been an hour long conference call before that. The phone rebooted and got to the startup screen and then rebooted again but at least this time it finished booting which is an improvement over before. Also, thanks for the tip about AOSP roms not booting without an SD card.
I did notice yesterday when it rebooted on me, after a couple of bootloops the screen then went black and the phone vibrated 5 times. I was only on a short phone call yesterday while in my car for 10 min.
On a side note, I haven't partitioned my SD card with an app partition but I was wondering if it is necessary for moving apps to the SD? I have moved several apps to SD so I want to make sure that isn't causing an issue either.
had the same problem myself, did a clean install which didn't help, finally reinstalled 7.0, all working fine now
Sent from my ADR6300 using XDA App
Snappyts said:
had the same problem myself, did a clean install which didn't help, finally reinstalled 7.0, all working fine now
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thanks Snappy...I never really thought about reverting. I've give it a try later today and report back.
Alright, so last night I performed a factory wipe and installed CM 7.0. Everything went fine but as soon as the ROM loaded and I opened the market it rebooted on me. This morning I just performed another factory wipe and installed MIUI thinking maybe it might be a ROM issue, but I got the same results. As soon as I opened the market to start installing stuff it rebooted on me...I tried this twice and reboot each time the market opened. I guess next I'll try a sense rom, Skyraider maybe...I'll post back with the results.
Warranty replacement
I was having pretty much the same issue. I tried everything from countless forums for the last month and a half. Finally had to cave and get a warranty replacement. - just pointing out that it might be a hardware issue (my device ran hot w/o sd and stock OS)
If the problem is following you on multiple roms it sounds like its probably a hardware issue.
Sent from my ADR6300 using XDA App
I've bounced around between various forums/posts and I think I have to agree it is probably a hardware issue. Being that I'm out of warranty, my only alternative is to upgrade or buy another Inc. Given the small pricing difference, buying another Inc versus upgrading, the logical choice seems to upgrade.
So my upgrade choices that are currently available are Inc 2, Thunderbolt, or Revolution. Another option is wait for the Bionic to come out in a few months. Any suggestions? I'm personally leaning towards the Thunderbolt...
Thanks again everyone for your help.
Well if you need to update now, I'd say the thunderbolt is probably your best choice. If you can wait, the bionic, if unlocked, looks like quite a phone, but IMHO the galaxy s2 is the phone to beat.
Have you tried getting a replacement? I suppose if you got your phone when it first came out the one year warranty might be up but it never hurts to try.
Sent from my ADR6300 using XDA App
k_nivesout said:
Well if you need to update now, I'd say the thunderbolt is probably your best choice. If you can wait, the bionic, if unlocked, looks like quite a phone, but IMHO the galaxy s2 is the phone to beat.
Have you tried getting a replacement? I suppose if you got your phone when it first came out the one year warranty might be up but it never hurts to try.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I haven't tried, but we did get the phone when they first came out last year so we are a couple of months past the one year warranty. My wife looked it up though and since we are available for an upgrade at this point the likely scenario is VZW pushing me to a new device rather than replacing my dying one.
I agree, the Galaxy S2 does look nice but since my wife works for VZW I'm kind of stuck with them.
I'm tempted to limp along until the Bionic comes out to see what it has to offer. As long as I can make calls I'll be ok...I guess Plants vs. Zombies will have to wait.
The GS2 is coming to Verizon. Not exactly sure when, there was a rumor that it'll be next month but I don't know how for sure that is.
Sent from my ADR6300 using XDA App
k_nivesout said:
The GS2 is coming to Verizon. Not exactly sure when, there was a rumor that it'll be next month but I don't know how for sure that is.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I had to go refresh my memory on the exact GS2 specs, then I had to wipe the drool from my mouth. I haven't heard of Verizon getting it within the next couple of months so now I'm even more bummed.
I guess it will kind of depend on how long my phone holds out. The random reboots and shutdowns can be annoying and have become all too frequent if I do anything more than make a phone call...sometimes even then it shuts down.
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
On ParanoidAndroid 2.54 + franco.kernel r300. None of the problems you mentioned are present or has ever happened with me. Perhaps if you didn't mod your phone so much as to NOT be able to pinpoint a problem is where you went wrong.
Who knows? I surely don't. Don't know you but I don't think I'll be noticing your absence. Good luck with everything!
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thats cool, you already tried your fair share of roms, if none of them worked for you the stock is the best with unsurpassed stability. Despite whats advertised about the nexus, the stock android firmware is excellent too, specially when you want something that just plain works.
Sent from my Galaxy Nexus using Tapatalk 2
Great story brother. Thanks for sharing.
Sent from my i9250
bk201doesntexist said:
Great story brother. Thanks for sharing.
Sent from my i9250
Click to expand...
Click to collapse
Keep coming..it works if you work it
Sent from my Galaxy Nexus
goodbye person ive never seen post before. hope you figure out your problems
Stock is the way to go, but you don't have to leave the xda because you no longer run a custom ROM. there is a lot of useful information that is shared here that doesn't necessarily apply to custom ROM.
I am also running stock rom from now on.
Sent from my Nexus 7 using xda premium
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I hope you really didn't write all of this from your nexus lol. But just go to stock...simple :thumbup:
Sent from my Galaxy Nexus using xda premium
I see how you feel abouyt this. I have had issues as well. It really stems from what Roms are and what we expect from them. The term Night lies have lost a little bit of its worry recently because they are fairly bug free. But that doesn't mean that little tweaks and mods aren't killing battery life and deteriorate over time due to bad patches and coding.
That said I would highly recommend checking out BuglessBeast. They are not night lies by any means. They are highly stable AOSP Roms that perform much better then anything else on the market. He has few commits aside from under the hood tweaks. Reboot menu, emoji and a slight few other things are it. I have never had an issue with them and recommend checking them out. Also they are pretty much the only VZW app compatible ROM. Peter has been building BuglessBeast since Eclair on the Droid1 (almost 3 years now). Always providing an excellent experience.
spjetrovic said:
Keep coming..it works if you work it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Flashaholics anonymous?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Stock + root is the way to go for me on Nexus phones. On my last non Nexus (SGS3) I was always flashing new roms trying to look for something that just works, but I am tired of it. On my Nexus S and GNexus, stock rom is amazing, I don't need anything else.
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I'm with this guy as well... I upgraded to a stock 4.2 rom (with root, but not a custom build).. and I have been smooth sailing since. It seems with all these custom roms and kernels there are nothing but issues. Sure, they're a TAD faster or offer little tweaks but when you need to use your device in the real world and it f*cking reboots while navigating somewhere because of a stupid tweak you made.. well, I can't see why it's even needed.
This phone runs very well with Stock+Root. I normally root devices because of different apps I like to use, and the ability to make custom backups...but I dont normally try anything bleeding edge...lol.
Partly because of my experience on an HTC phone...hated Sense and bought the GNex because of the AOSP.
akira02rex said:
I'm with this guy as well... I upgraded to a stock 4.2 rom (with root, but not a custom build).. and I have been smooth sailing since. It seems with all these custom roms and kernels there are nothing but issues. Sure, they're a TAD faster or offer little tweaks but when you need to use your device in the real world and it f*cking reboots while navigating somewhere because of a stupid tweak you made.. well, I can't see why it's even needed.
Click to expand...
Click to collapse
No need to bash the custom roms that some devs here work so hard to make, i agree that stock is amazing but android would be a boring scene without the custom roms out there
We would just be like Ios, Wp and blackberry users, stuck with what we've got
Others wouldnt even have the chance to use a newer OS version because their phone has been abandoned by official support.
Or many of u guys would have crappy colors or other issues that custom roms and kernels DID fix
I use stock but i love the fact that there are custom roms around
Sent from my Galaxy Nexus using Tapatalk 2
negrobembon said:
No need to bash the custom roms that some devs here work so hard to make, i agree that stock is amazing but android would be a boring scene without the custom roms out there
We would just be like Ios, Wp and blackberry users, stuck with what we've got
Others wouldnt even have the chance to use a newer OS version because their phone has been abandoned by official support.
Or many of u guys would have crappy colors or other issues that custom roms and kernels DID fix
I use stock but i love the fact that there are custom roms around
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I get that, it's good to see support for older devices but c'mon have you counted the amount of 4.1.2 roms that are available for the gnex? If I build android I'm automatically called a developer? Because that's the way it seems here...
I don't know why people keep bringing up the so crappy colors. In reality, the crappy colors are the ones custom ROM offer.
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
I don't know why people keep bringing up the so crappy colors. In reality, the crappy colors are the ones custom ROM offer.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its the kernels that offer the colors(the kernels that the ROM developers include too). of all the kernels available, only a very few distinguish themselves from the stock crappy colors.
This is ridiculous... who obligated you to install a custom ROM? F*cking emos.
Sent from my Galaxy Nexus using xda premium
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my...
Blah blah blah.....
Click to expand...
Click to collapse
No, please stay! We'll never survive without you! [/SARCASM]
GhoXt said:
This is ridiculous... who obligated you to install a custom ROM? F*cking emos.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Alright Captain, you keep Franco deep in your throat.
Sent from my Galaxy Nexus using xda premium
Recently had a Galaxy S2 do something strange and I wanted to see if you guys can decipher what really happened because I have no idea what caused this to happen.
Let's start off with some other info....I was running:
CWM Touch Recovery 6.0.1.8
Cyanogenmod10 Nightly 111212
I simply turned it off once the battery was getting low and charged it, once it was done I turned it on and it made it to the lock screen and then restarted. It would continue do that indefinitely until I removed the battery. So I thought maybe something went wacky and got corrupted so I went back to stock....When Odin restarted it I made it to the Android Welcome screen and it restarted again just like before. So then I got really desperate and did a factory reset and erased all my personal data along with a different stock rom...ICS stock. Nope, it STILL restarts.
Additionally, T-Mobile is replacing said device for a new SGS2, but now I'm afraid to root it. Which is why I want to figure out what happened to it. I'm starting to have suspicions about my extended battery I bought because when this restarting issue began, I've been using them for a little over a week and I haven't done any cyanogenmod updates or flashes recently.
on another note, if I do decide to root again, which Recovery should I use? Preferably one that doesn't require me to use Darkside Superwipe or cache scripts. I'd prefer a Recovery that can do it without scripts. And if you could provide the link, that would be great. I don't care if it's touch or not.
I have been using TWRP for awhile now. Supposedly the built in Wipes are very effective. I like the look and aesthetics of it. I don't think the issue you experienced had anything to do with rooting and romming. I think you may have had a legitimate phone issue. Don't be afraid, just be prepared with backups and knowledge and such.
jcnbama said:
I have been using TWRP for awhile now. Supposedly the built in Wipes are very effective. I like the look and aesthetics of it. I don't think the issue you experienced had anything to do with rooting and romming. I think you may have had a legitimate phone issue. Don't be afraid, just be prepared with backups and knowledge and such.
Click to expand...
Click to collapse
Thanks for your input, As a precaution, do you think I should stop using the unofficial extended batteries? Because this started about 2 weeks after using them.
goku1910 said:
Thanks for your input, As a precaution, do you think I should stop using the unofficial extended batteries? Because this started about 2 weeks after using them.
Click to expand...
Click to collapse
I would go a while without using it and see if the issue persist. If it does then you'll have your answer. Either way.
Sent from my SGH-T989 using xda app-developers app
Sounds like your phone's power button is messed. You can try using a small flathead screwdriver and put it into the sides of the power button and rock it around a little bit. If that doesnt work i guess youre going to have to take it to a repair shop or if you have warranty just bring it back.
Sent from my SGH-T989D using xda app-developers app
Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung
But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2
Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app
johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.
Try wiping your SD card
There is a lot of fear going around with people worried about bootlooping. I think it would be good to get some rough idea of what the chances are for this to occur through at least one means. So I want to find out just how many people this is effecting and how many (here) it is not.
I've rooted and flashed darthstalker on 3 different note 3's also upgraded them to v2 and no issues here. I read everything I needed on twrp, flashing, and not restoring.
All 3 devices are doing exceptionally well.
Sent from my SM-N900T using xda app-developers app
elracing21 said:
I've rooted and flashed darthstalker on 3 different note 3's also upgraded them to v2 and no issues here. I read everything I needed on twrp, flashing, and not restoring.
All 3 devices are doing exceptionally well.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Why not vote on the poll? Also have you restored?
I've flashed numerous times on my Note and never had any boot looping issues. Just followed the steps and all is well.
Sent from my SM-N900T now Free
Restoring nandroid works for me
I did a nandroid backup from my darthstalker v2 rom. Then after that I was using the phone one day and my signal went out on the phone and never come back on. I put the phone back to stock and took it to tmobile ( which tmobile never checked the bootloader to see if the knox counter was tripped ). The realized the phone was defective and gave me a brand new one. I got home and rooted the device. After that I backed up the current rom and moved the nandroid back up of darthstalker v2 to the new folder location. I installed darthstalker v2, I then did a factory reset, wiped system, cache, and dalvik cache. After that I restored the nandroid back up only restoring the system and data. The rom loaded right up and I have no problems whatsoever. All this was on the latest twrp I installed from the goomanager app. Seems that restoring nandroids is working just fine in my case.
I wonder if anyone with the boot loop restored only system and data...
I'm thinking that restoring more than those two options may play a role in this.
sgh-TWEAKED-889©
Warrior1975 said:
I'm thinking that restoring more than those two options may play a role in this.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
maybe because the other people getting boot loops from doing TB restores and that has to do with data right?, only thing i believe they can recover but we couldn't. I got my new note after giving up yesterday and i wont be the one to try that theory lol.
stress1ner said:
maybe because the other people getting boot loops from doing TB restores and that has to do with data right?, only thing i believe they can recover but we couldn't. I got my new note after giving up yesterday and i wont be the one to try that theory lol.
Click to expand...
Click to collapse
Haha same here...
Sent from my SPH-L900 using Tapatalk 2
I've flashed a stock deodexed rom and both versions of Darthstalker. Restored data only w/TWRP every time w/no bootloops whatsoever. Still probably gonna play it safe & just do TB restores until they figure out exactly what's causing all this though.
HughesNet said:
There is a lot of fear going around with people worried about bootlooping. I think it would be good to get some rough idea of what the chances are for this to occur through at least one means. So I want to find out just how many people this is effecting and how many (here) it is not.
Click to expand...
Click to collapse
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Steve Lazarus said:
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can promise you one thing Steve I will not considering I was the first one to have a boot looping note 3. I don't want to see that happen again.
Sent from my SM-N900T using Tapatalk 4
Steve Lazarus said:
Knowledge is power, so know this..
DO NOT RESTORE A BACKUP, PERIOD, END OF STORY.
I'm going to attribute this issue to the Knox security Samsung decided to include on the Note 3. I am of the opinion that whether it be the Knox container, partition, security issue, it could have been avoided by Samsung offering Knox related security to people who want it, not just including it on every device sold to the masses, most of which could care less about toting around top secret documents on their devices used mostly for social entertainment.
Just a poor decision in my opinion, which they're going to realize shortly, or already have. Reason being the pending release of a "Developer's" version of the Note 3..
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Stuff is pretty easy to remove either way. Typical carrier stunt. Nothing new.
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
And titanium backup is terrible. Most users I see that have problems with boot looping, force closes, etc... Are causing the issue. Hard to believe the device randomly decided to start having issues on its own.
d474corruption said:
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
Click to expand...
Click to collapse
If that was the case, xda would be a very quiet place.
Sent from my SM-N900T using Tapatalk 4
d474corruption said:
Stuff is pretty easy to remove either way. Typical carrier stunt. Nothing new.
This only proves the point that if you are incapable of diagnosing issues on your own, you shouldn't be messing with core related system apps, messing around with beta-ish recoveries, etc. Root and leave it alone if you don't know what you are doing.
And titanium backup is terrible. Most users I see that have problems with boot looping, force closes, etc... Are causing the issue. Hard to believe the device randomly decided to start having issues on its own.
Click to expand...
Click to collapse
I agree and disagree.. If we were to live by your motto, Google and Android development wouldn't be where they are now. The end user has doors open in front of them once they root for the first time, or flash their first custom ROM, and from there the imagination starts working it's magic.
Some first time rooters / modders go on to become great application developers due to the unfounded landscape they discover once they delve into writing code.. It's not rocket science to root, flash, tweak, mod. However, it does get tricky once a manufacturer makes a device with features that create problems doing the most menial of things. Knox was put on a device sold to the masses, which as stated, most of which could care less about toting around top secret documents, as compared to checking Facebook, email, YouTube, their favorite sites and forums.
The end user needs to do their research before just tossing themselves into the fire . But as we've seen thus far regarding this issue, even developers are still trying to figure it out. Most dev's encourage the end user to actually understand what the cause and effect of what it is they're doing. Also how they (the end user) can do the same thing with a different outcome using an alternative route, code etc..
You start alienating people from this process, we all suffer.
Sent from my SM-N900T using XDA Premium 4 mobile app
kabuk1 said:
I've flashed a stock deodexed rom and both versions of Darthstalker. Restored data only w/TWRP every time w/no bootloops whatsoever. Still probably gonna play it safe & just do TB restores until they figure out exactly what's causing all this though.
Click to expand...
Click to collapse
They just did. Apparently TWRP doesn't restore the EFS partition properly, causing a bootloop. If you don't restore the EFS partition, you'll be fine (which you would never have to do anyway unless you somehow blew up your IMEI and modem configuration).