Yesterday I noticed that my NC has an issue with the ADW launcher. It just keeps giving me a force close error. I eventually gave up and put it to "sleep" but apparently it was still sort of running with the screen off because the battery was down to 20% by the end of the day.
This morning it's still doing it. I tried going into recovery and wiping Dalvik Cache but I'm still getting the same FC error. What do I do to fix this as I basically can't do anything since the launcher doesn't work?
The next thing that i would try is either from ROM Manager or Recovery do a fix permissions and see if that nets any results.
obsidianblackhawk said:
The next thing that i would try is either from ROM Manager or Recovery do a fix permissions and see if that nets any results.
Click to expand...
Click to collapse
I tried that and then I also flashed 102 nightly thinking that maybe that would reset things, but I still have my original background and all of my apps and stuff so maybe something didn't take? I flashed 102, Gapps and the OC kernel. I thought that flashing 102 would reset me back to square one and I'd have to rebuild everything so the fact that I seem to be back to where I was and I am still having the FC issue leads me to believe that something went wrong with the flash.
I'll try running Fix Permissions again just for the hell of it.
No dice. Just ran fix permissions and it still doesn't work.
Sounds to me then (as terrible as this will sound), you may just want to go into recovery, manually wipe system, data, and both caches and start from scratch. i know it sucks, but i have encountered less than a handful of similar situations, and that was the only remedy i could find. Also a thought: I am having awesome results with n105 and Dal's 6/18 OC kernal @ 1325 on both my own and my wife's NC's.
Also if you like ADW Launcher (the one that comes with CM7), might i suggest VTL Launcher, it is built from ADW Code and optimized for a tablet. I fell it is a bit more option friendly, and i have had no issues with it at all... and MOST ADW Themes work well with it.
obsidianblackhawk said:
Sounds to me then (as terrible as this will sound), you may just want to go into recovery, manually wipe system, data, and both caches and start from scratch. i know it sucks, but i have encountered less than a handful of similar situations, and that was the only remedy i could find. Also a thought: I am having awesome results with n105 and Dal's 6/18 OC kernal @ 1325 on both my own and my wife's NC's.
Also if you like ADW Launcher (the one that comes with CM7), might i suggest VTL Launcher, it is built from ADW Code and optimized for a tablet. I fell it is a bit more option friendly, and i have had no issues with it at all... and MOST ADW Themes work well with it.
Click to expand...
Click to collapse
Thanks for the help. I ended up restoring to a previous save and that seemed to work. At first I freaked out because I got the Launcher FC again. But once that went away everything seemed to be fine. I reflashed 102, Gapps and the Kernel. Hopefully everything will be ok. I'll check out the launcher you suggested. I assume you can get it from the market? Sorry but I'm pretty much a complete noob with this stuff. I don't even have a cell phone so this is my first experience with apps and modding electronics. I am barely familiar with ADW.
I had this issue at one point, once I flashed a new nightly one day, it just stopped. /shrug
darien87 said:
Thanks for the help. I ended up restoring to a previous save and that seemed to work. At first I freaked out because I got the Launcher FC again. But once that went away everything seemed to be fine. I reflashed 102, Gapps and the Kernel. Hopefully everything will be ok. I'll check out the launcher you suggested. I assume you can get it from the market? Sorry but I'm pretty much a complete noob with this stuff. I don't even have a cell phone so this is my first experience with apps and modding electronics. I am barely familiar with ADW.
Click to expand...
Click to collapse
You are most welcome, i hope i was of some help That link i gave you for the VTL Launcher is a link to download it direct from the dev.
Thanks guys, I've gotten everything working again. But now I just realized that I probably lost all my Plants vs. Zombies game data. Oh well.
Related
Sprint HTC Hero
DarchDroid v2.8
Recovery: RA-Darchstar (v1.7... I think)
PRL: 60667
I bought this phone last week, rooted it, and attempted three or four different ROMs before settling on DarchDroid (which is awesome, by the way!). I was initially having issues with multiple FCs and it eventually became unusable until I read up that my device might not be able to handle the OC to 710mhz. I installed the OC widget and throttled it down and now it works like a champ and is still WAY faster than the stock 2.1 ROM. I am still having issues though, that hopefully, somebody can help me with or point me in the right direction. I've spent the last hour scouring almost all parts of the forum and can't find any answers to these issues. Forgive me if I looked them over...
1) All incoming calls go directly to VM. I can make calls and send / receive texts, but no incoming voice calls.
The next one is a two-parter...
2a) The phone will occasionally become so sluggish (borderline non-operational) that I need to reboot it. When I do, I clear the cache and it will reboot then function normally. Could this be a result of a widget that I have installed? (OC widget, battery monitor?)
2b) When I reboot the phone without booting into recovery (normal reboot) it goes into a continuous boot loop. When I try to restore my Nandroid, it still boot loops and I have to wipe and re-flash the ROM. Is this normal?
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
I had the same issue with the latest Fresh Rom so I ended up switching to Zen Hero and have never had a FC on an incoming call since. I tried all the fixes for Fresh and never had any luck. I would suggest trying another rom.
p.s. I was able to OC the rom also and it still works fine.
chromiumleaf said:
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
Click to expand...
Click to collapse
Thanks for the advice. I ended up biting the bullet and calling Sprint and it turns out all that was needed was a refresh on my account, the phone works like a champ now! I'm using the OC widget and throttled it down to 595mhz, and even OC'd that little bit, it still BLAZES when compared to the Pre that I came from. No hitches or waiting - when I open a program or app, IT ACTUALLY OPENS QUICKLY... an amazing concept!
One more question though: in case I need to reboot, is there a way to save all of my phone settings? I already moved all of my apps to the SD card so I don't have to download them again, but it would be really helpful if I could just load a save file that would re-set my settings to the way I had them before. Is there an app or setting in the ROM for that?
Make a nandroid backup through recovery. It saves every little detail of your phone and if you ever need to go back to that you can simply restore that backup. Titanium Backup is another popular tool but I've never used it myself so I don't know anything about it.
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
HTCOmega said:
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
Click to expand...
Click to collapse
Kernel flashing doesn't always go smoothly. Repeated kernel flashing without complete system wipes in between can cause some things to start going horribly wrong.
Don't use SetCPU to set clockspeeds. Just stick with voltage control.
If you forgot to disable any lagfixes at any point along the way, that could explain alot of the problem.
Suckerpunch kernel is a great concept and is showing alot of promise, but I personally have had alot of stability issues while using it, including random freezes (YMMV, of couse).
Just my opinion, but I would just back up all your data, flash back to stock, master clear, wipe all your cache data, reflash your rom, pick a kernel and stick with it for a while. If you want pure stability and battery life, use the most recent version of either DG's Firebird kernel 2 or Hardcore's speedmod kernel. If you want stability and oc/uv enabled, stick with Glitterball's kernel. Those 3 have been the best for me personally (again, YMMV).
Hey, I am not sure if anyone has mentioned this before, but I just purchased and installed App Mod: http://www.appbrain.com/app/anim-mod-*root*/com.jrummy.animation.changer and it is AWESOME! I am running ACS Frozen and it is working great!
When I first installed it and tried to change a transition, it prompted me to install busy box (which I thought I already had ) I did the recommended install and it shut my phone off. I thought there was a problem and that I would have to restore from backup...but when I turned the phone back on...everything was fine. It worked like a charm!
EDIT: **** After about 2 hours of use, the phone shut off and when it rebooted, it was unusable! All apps force closed...had to do a factory reset! Damn....oh well...
Alright, so the first install and crash seems to have been an isolated incident. I flashed ACS Frozen 1.0.2 and installed it right after. I downloaded and applied the flip transition and it has been working fine. It has been only about 13 hours or so, but so far, no problems. I will report back in a few days to let you know how it's working.
It's been 3 days now and still no problems. I think the initial crash was unrelated. I have read many posts about people having issues with all apps force closing after an unplanned reboot when the fs has jounaling turned off. I am not entirely sure, but I think this might have been my issue.
If you are looking to spice up your transitions, I would totally recommend this app.
Thanks.
Nice find will use this thanks
I looked into this app and really like the concept but after looking around in my launcher Go Launcher EX I found it had the animation effects built in for free.
Guys my Nook is freezing sometimes.
I have to shut down manually with the power button .
I am running right now nightlies 102 with OC 18/06.
But I had this problem and with Phiremod test Rom.
I have install the rom to my internal emmc.
any suggestion?
Isolate the machine..by this run without the OC kernel..or try running a different version of cm..many time on my machine with the nightly updates it does also freeze..I always to back to one that does not freeze..remember you are flashing test builds and they must be treated as such. Also..what speeds are you using...are you running setcpu with at boot option on..which you should not do. It WILL lock up..have you deleted any of the .apk files? Did you clear the cache and dalvic?
life64x said:
Isolate the machine..by this run without the OC kernel..or try running a different version of cm..many time on my machine with the nightly updates it does also freeze..I always to back to one that does not freeze..remember you are flashing test builds and they must be treated as such. Also..what speeds are you using...are you running setcpu with at boot option on..which you should not do. It WILL lock up..have you deleted any of the .apk files? Did you clear the cache and dalvic?
Click to expand...
Click to collapse
I will try to clear the cashe adn dalvin. No I dont use setcpu I know that it will crach with the preinstalled performance settings.
Try a complete flash with a differently nightly..what I mean is wipe all 3 (dalvic, data and cache and try just to boot) some times the nightlife are not very friendly... Build 110 comes to mind...it froze up..had to do a complete restore..frankly...I am getting tired of always flashing theses...my favorite is build 64 with the 1.3 sped kernel. For me this was running just right. I am going to flash 112 later tonight and I want to write a guide to which apks to remove safely for new flashers..I been meaning to write one for awhile..
life64x said:
Try a complete flash with a differently nightly..what I mean is wipe all 3 (dalvic, data and cache and try just to boot) some times the nightlife are not very friendly... Build 110 comes to mind...it froze up..had to do a complete restore..frankly...I am getting tired of always flashing theses...my favorite is build 64 with the 1.3 sped kernel. For me this was running just right. I am going to flash 112 later tonight and I want to write a guide to which apks to remove safely for new flashers..I been meaning to write one for awhile..
Click to expand...
Click to collapse
maybe I will try a new build tonight.
I will report back.
cool......
searius said:
Guys my Nook is freezing sometimes.
I have to shut down manually with the power button .
I am running right now nightlies 102 with OC 18/06.
But I had this problem and with Phiremod test Rom.
I have install the rom to my internal emmc.
any suggestion?
Click to expand...
Click to collapse
Try the new CM7.1 RC release. I always do a clean install whenever i have freezing issues or i feel that nook is running slow.
http://download.cyanogenmod.com/?type=RC&device=encore
To many freezes,
Oh how dare you mock me so.
Power off again.
sounds like SOD...
SOD: http://forum.xda-developers.com/show....php?t=1108964
I have put nightlies 112 now.
For the moment I had not any freeze only one time SOD.
But I have not use too much the Nook those days. I have exams
It doesn't look like Sleep of Death. My NC is not sleeping. Just when I'm in some application (for example, Angry Birds) it becomes extraordinary slow.
I exit the application and it is slow in launcher screen. Looks like frozen, then after several seconds it starts reacting on previous gestures. Then long delay again. Have to power off or reboot Nook.
I saw it yesterday for first time. My Nook was turned off for ~2 weeks. Then I turned it on and updated some apps in market. I noticed Netflix app was in memory. I don't think it loaded automatically at start up before.
I have CM7.0.2 stable, with normal kernel at 925MHz. I installed more than 100 apps, maybe one of them is the reason. It happens quite often, maybe once in half an hour. It can also happen in market during update. Nook is unusable right now.
But my friend has CM7.0.3 and he didn't install that many, I believe he has the same problem.
Will try to wipe stuff and to prevent unnecessary apps from starting with autostarts. Will see how it goes.
With that many apps...make sure you clean out the cache frequently...there are a few apps that do that free on the market....when got got my first android device...a evo I would load everything I could under the sun and delete and installed like crazy....now I have a few trusty apps and I clean out my cache everyday....browsing along will fill up the cache like crazy...
searius said:
I have put nightlies 112 now.
For the moment I had not any freeze only one time SOD.
But I have not use too much the Nook those days. I have exams
Click to expand...
Click to collapse
Glad to see you up and running.....
life64x said:
With that many apps...make sure you clean out the cache frequently...there are a few apps that do that free on the market....when got got my first android device...a evo I would load everything I could under the sun and delete and installed like crazy....now I have a few trusty apps and I clean out my cache everyday....browsing along will fill up the cache like crazy...
Click to expand...
Click to collapse
The only reason to do this kind of nonsense is if you need more space in /data, which is unlikely a problem on the Nook Color.
khaytsus said:
The only reason to do this kind of nonsense is if you need more space in /data, which is unlikely a problem on the Nook Color.
Click to expand...
Click to collapse
I have to disagree...I use firefox on the nook and after a few hours of surfing..it will slow down dramatically...clear my data cache and speed goes up...Also...the more apps loaded the more processess and services runningcin the background which results in overall slowdown...I really don't know why you call it nonesense when it is simple math..the more you have and use the more it is caches and or memory is gutted down with more crap running on it in the background and or swapping in and from cache.
I wiped cache partition and Dalvik cache using CWM recovery. NC looks better now. Didn't freeze so far, but I need to test more.
Thanks
PS. I rarely use browser. It froze while playing some game, or immediately after exiting game, in Zeam launcher.
micksh said:
I wiped cache partition and Dalvik cache using CWM recovery. NC looks better now. Didn't freeze so far, but I need to test more.
Thanks
PS. I rarely use browser. It froze while playing some game, or immediately after exiting game, in Zeam launcher.
Click to expand...
Click to collapse
I don't do the dalvic cache...I am talking about the general cache...currently using 'cache cleaner' from marketplace and works like a charm.
my nook has been freezing a lot lately too. randomly. it doesn't slow down or anything, it just freezes and I have to hard reboot. at least 3 times a day. I am on nightly 116, this has been happening since beta 3.1. using 6/18 kernel. overclocked to 1175.
sometimes it will even freeze right after the bootanimation as soon as it gets to the main screen. Any ideas on what I can do? I have changed the kernel from conservative to ondemand and that didn't help. I lowered the overclock from 1200 to 1175 and that didn't help.
edit: as I was typing this it froze while clicking on the dropbox app. I restarted and it froze as soon as it got to the homescreen. also just cleaned the cache. freed up a lot of memory but it didn't help.
Slow clock down to stock..or flash another build...also just use cm for over clocking if you are using setcpu..uninstall it..I don't know if you are. Try interactive...if still freezing..with setcpu..yes..reinstall..basically try different combos...when you find one that is stable...backup and use that as your daily driver and then experiment with different build.
I cleaned program cache too, with Android Assistant. I guess it's the same. Nook froze badly today. Played Angry Birds, froze completely. Pressed "n" button, exited to launcher, but could not do much in it. Only long-press power button helped.
The thing is it worked well two weeks ago. Then I didn't use it, then I downloaded few free apps from Amazon and ran out of space on eMMC. Then I moved some apps to microSD (I don't think I moved Angry Birds but it looks like it is on SD for some reasons). And my microSD has bad random access times. Can this be the reason?
People in this thread http://forum.xda-developers.com/showthread.php?t=1005633 reported problems when booting OS from slow cards. It probably applies to apps on SD too. I bought Sandisk card now, but it will take time to deliver.
Hello!
TW stops working several times a day, I've haven't managed to narrow down the apps that might crash it (unless everything I use on the phone crashes it). It sometimes crashes in the home screen, in Chrome, in YouTube. The two apps I use the most are WhatsApp and Facebook, and it has crashed when I'm using them, too.
I have the habit of pressing the home button to leave an app, and the phone always takes a little bit to reload all the icons. I know TW lags and stutters for many, this is not a complaint but an observation. I used phase beam as the wallpaper before, so I changed it to a solid black picture. That hasn't helped.
My phone is not rooted, though processes unused are stopped in App Manager.
Any assistance and suggestion would be much appreciated. Thank you.
Reset phone
BAD ASS NOTE 4
Hey guys,
I am facing the same issue, where TW crashes and I receive the message that TW has stopped working, however in my case it happens each time I reboot the phone. Once I OK the error message, TW reloads, and remains stable until I next reboot my baby, which I tend to do once a day, for good measure. This is not the end of the world, something I can live with, yet I do find it irritating that I cannot figure out what is causing this.
Anyone with a suggestion would be greatly appreciated. FYI, I am running stock at the moment.
Regards,
Raziel
I'd be tempted to odin to stock or flash firekat.
Raziel, I cleared TW cache and then wiped the cache partition earlier this afternoon. It seems TW hasn't crashed as often as it usually does, but it has crashed. It might remedy your problem, though, if you haven't tried this already. I'm avoiding resetting my phone.
If you rooted and tw goes crazy on you something went wrong. Delete everything you got. Turn of antivirus software. Download everything. Start by going back to stock then update then root then your good to go. If you start with a bad hicupp it will just keep getting worse.
BAD ASS NOTE 4
ChinWonder dude! Thanks a bunch for this suggestion... I cleared TW cache in Application Manager, then booted into Recovery and proceeded with wiping the cache partition. Honestly I feel like a bit of a noob right now LOL, I should have thought about this myself!! But hey thanks nevertheless, much obliged .
BACARDILIMON, as stated above by the OP, ChinWonder, as well as myself, in both cases the devices are not rooted. Thanks for the effort though . I'd like to add however that all of my previous and current Androids (S2, S3 and Nexus 7 2013) have been rooted, and in the last 2 cases, on day 1... hell I even made my own custom ROM for the S3 based on stock Bell 4.1.1 and stayed on it despite several available upgrades, I was getting such good performance and battery out of it, and FULL compatibility since I used a firmware base from my carrier, which is not the case for most custom ROMs found here, since none of them (or close to) are using Bell, but AT&T in most cases. From my experiences, I was always getting issues receiving voicemail notifications when using those. Long story short, I have been on the flashing bandwagon for a few years now, and tweaking the hell out of all my devices up to now, but this time, I feel this is the perfect (ok nothing is perfect) smartphone for me, as is, stock, and it performs like no other device I've had until now, and battery is just incredible!! getting regularly well over a day of charge, mostly average 36 hours, with 6 to 8 hours screen on time!!! WOW!!! seriously for the time being, I don't feel I want to root and flash and all that jazz, but instead I just want to enjoy this beast, the way Samsung thought of it, for a little while.
Again ChinWonder, thanks!
Raz