Develop Bugs

Serious stability issues unrooted Galaxy Nexus

I've been having some pretty big issues with this phone ...it's unrooted running stock ITL41F still on 4.0.1 in the UK
Its been 7 days that I've owned this phone now. And few times it has just crashed. I could be in the middle of typing something, or anything else just coming out of an app, and the screen will freeze go black. And done! Crashed.
And crashed such that it doesn't start I have to take the battery out and reboot. It just dies. It happened a few times but I was setting my phone up so I let it go but now this is just downright annoying. It happens once in two days or so.
Second, and this is even worse. The phone is not dying but goes in a sort of coma. The screen becomes unresponsive.. and the keyboard doesn't work!! And in most apps only selective touch input works...let's say in whatsapp I was talking to a friend and it was working okay but suddenly it stopped accepting my input for a new mesg. And then I couldn't open another chat. Lots of things started being unresponsive...
I went to the home screen and even the Google search bar ..when I clicked on it the keyboard came up ( which it wasn't coming while middle of whatsapp chat) but it didn't accept any input.
I tool the battery out. Rebooted. And it worked initially but then after a few minutes. Exact same problem.
Rebooted again. But again same problem !! That was a bit of a horror really
Right now it seems to be accepting my text input but ... really don't know what the heck is going on for both these issues above. Any advise will be appreciated
Also yeah I do have quite a few apps installed on this device ... considering its stock ROM this should be safest against a vulnerability but any advise on if I should install one of those anti virus apps on it? Or any sorts of apps that I should avoid which cause such major stability issues with ur phone ??
Cheers
Dhruv
Sent from my Galaxy Nexus using XDA App

I've only experienced few of your issues.
Coma and reboot happened a couple of time while I was on 4.0.1.
But since getting 4.0.2 a few weeks ago those issues went away.
Sent from my Stock Galaxy Nexus using XDA App

4.0.2 ftw.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

There are a few threads here with people experiencing similar problems. My screen goes black and also requires a battery pull.

@rbiter said:
4.0.2 ftw.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.
Click to expand...
Click to collapse
4.0.3 ftw. Either flash a custom rom or get the 4 0.2 update to help with your problem.
Definitely a software issue that you're having.
Sent from my Galaxy Nexus using xda premium

I refuse to believe it is 4.0.1 it has been long delayed in the UK
That wouldn't be the case by Google if it was fixing such serious stability issues with the phone
Why do you come here doling out suggestions when you have no clue?
I am having the same problem again now everything is very slow and even the keyboard doesn't open in even Google search most functions unresponsive

And now most apps are force closing on me
IMDB and now xda app too. The phone is half dead the back buttons don't work either
This is the same thing that happened earlier in the day when I posted, and then the phone worked okay but now its back killing my phone
Anyone has any clue what could be going on ? Also this is the GSM version in the UK on 4.0.1 so only if you have a clue please respond else thank you very much

Now even settings page says its not responding
I can post on xda and it works but when I press back that doesnt.
Back doesn't work in any screens. The settings page not working was a classic screenshot will attach here from a PC.
Sorry for the continues rant folks. Just giving as much info as I can to those knowledgeable folks who might be able to help

The crashes arent stopping ..and the 4.0.3 isn't coming to the UK for some reason either ( which leads me to believe that it has some fixes for LTE which isn't available here anyway)
Aren't other users in the UK facing this crash problem - like once in 2 days or so??
Sent from my Galaxy Nexus using XDA App

Uninstall some of the apps you've downloaded that run in background. Battery Monitory was causing my phone to randomly reboot every other day or so. I uninstalled it and it was fine.
If that doesn't work, there's always Factory Reset.

Random Extreme Lag on VZW GNex

So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?

Bump. Any help? Still happening, though not as common, when I flashed stock

Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?

Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium

Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium

I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.

Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..

@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.

+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2

I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag

Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.

Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app

Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?

Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app

SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.

solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you

Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be

anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2

I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.

Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!

[Q] s3 stuttering/twitching

I have tried searching for this problem but I must be using the wrong terms... so sorry in advance if I missed a post that addressed this issue.
My sprint S3 does this twitchy/glitching thing on every touchwhiz based jellybean rom (does not do it on TW ICS ROMS) I have tried. It basically makes it nearly impossible to do sliding animations, IE it can actually get stuck and start flashing halfway between screens, or when pulling down the top menu, however you can open new programs just fine if you are already on the right screen for them. Luckily it does not do this all the time, but when it happens it keeps doing for 10 minutes or so and its annoying as hell.
I figured this must be a rare issue even though it effects both my wifes phone and mine, since I have never read anything about it, however I just got a new replacement phone and it does the exact same thing, even on dead stock TW JB ROM.
Oddly enough I discovered last night that if I turn on my screen filter app it stops completely, but it starts right back up when I turn off screen filter..... any ideas how to fix this?

Try grabbing cache clear from the play store and set it to run every 12 hours. It helped my phone a good bit.
Sent from my SPH-L710 using xda premium

No one else ever has this issue?

joelespinoza said:
No one else ever has this issue?
Click to expand...
Click to collapse
I had it dude, but it was just on the CleanBean ROM, it was annoying as hell!
So I changed the ROM, Its weird that its happening on a Stock ROM, any suspicious app?

Root or stay stock?

I still haven't rooted my note 2. I want to root and get custom roms but scared the roms might not have good battery like stock. I'm not sure what's you guys opinion?
Sent from my SGH-T889V using xda app-developers app

Everything gets better with custom roms
Sent from my SGH-T889 using xda app-developers app

Stock.
Sent from my SGH-T889 using Tapatalk 2

I have rooted every Android I ever owned including ny Note 2... This is the only phone I have unrooted and went back to fully stock. I am very happy with the way this phone runs stock.
Sent from my SGH-T889 using xda premium

I absolutely had in my mind I wasn't going to root etc. but im running the latest jedi rom and it is phenomenal!
Sent from my SGH-T889 using xda app-developers app

There are some cool features tied in with touch wizard specific to our pen capability. If you go custom you may lose that. So I would look more at rooting like such. Do I want root to bypass tethering lockdown from the vendor or to make backups with Titainium? Do I really need to overclock or undervolt? Do a new ROM's features negate the potential loss of pen related features
Sent from my GT-N7105

Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.

zellroot said:
Im rooted running stock, tried jedirom 10 and had to pull the battery after every phone call. Still havent gotten an answer as to why this was happening. Went back to stock rooted and done with custom roms until this gets ironed out.....on a positive note, that jedi 10 with that kernel was flying and im very disappointed that I couldnt stick with it as it has awsome features.
Click to expand...
Click to collapse
I was running stock rooted since I got my phone late last December. But today I finally decided to run a custom rom and jedi 10 was it. Flashed with no problems and do not see the problem you have. The rom is really nice. Here are some features I would suggest rooting for:
1. Free wifi tethering (it's a must for me since T-mobile charges $15 for me to use data that I'm already paying for).
2. Wifi calling (good option to have in case I do not have signals) - the jedi 10 rom offers this.
3. Multi-windown (any app) - a cool feature. I don't think I will use it much though. But it's good to use to show off.
4. Samsung keyboard with auto-correct. I wanted to keep the samsung keyboard so that I can use the s-pen sometimes. But the jedi rom has the auto-keyboard switcher embedded.

??????
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?

SAMOANBK47 said:
I rooted my phone I think but now I dont know what to do next! How do I pick a rom and where do I go to pick a rom or download one? Also what are kernals and overclicking?
Click to expand...
Click to collapse
Before you do anything else, search "nandroid" learn all about it, and make one.
Sent from my SGH-T889 using xda premium

I was stock until about 3 days ago. I moved into the Jedi ROM. I used CWM, the non-touch version. I don't know if I'm old school or worried about a non responsive screen but eh.
Originally I'd just thought to stay stock and not rooted so I could get OTA'S. Though with a ROM, I'm already miles ahead of the game.
As another person stated, using the tethering has really been good for me. I'm paying $70 a month, $15 more for the hot spot would of been ridiculously overkill.
Also, I've never seen or witnessed a phone become so buttery smooth and perform so well. I'm happy. ^_^
Just make sure you do back ups through TiBu and do nandroids.
Sent from my SGH-T889 using Xparent Green Tapatalk 2

I rooted, went to Jedi ROM, but had issues, like screen tearing, slow response (probably aggressive underclocking) and some other weirdness. Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.

Meanee said:
...Went to Tweaked ROM, and had to pull battery after using CNN app for 5 minutes. Also phone is very slow to wake. Turning screen off makes music player unusable. I think I should go to stock, but I would love to have TSM Parts thing on it. Wonder if there's a way to install it.
Click to expand...
Click to collapse
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty

Fyi...noting what I said before, I am currently running one of Tesh's rooted stock ROMs for the international version. I can run backups, do tethering (no carrier lockdown for international), and run another kernel if I wish. It also allows me to use some of the Exposed installer tweaks to keep the Note2 touchwiz benefits and still use things like per app resultions and all apps in multiwindow.
Sent from my GT-N7105

dwitherell said:
This would likely be better off reported in the Tweaked thread...
But, w/ the CNN freeze up (was this an app or website? Reading text or watching video/listening to audio?) was there any FC at all? What kernel were you using? What version of Tweaked were you running, and what sort of options did you have installed? A logcat of such an issue would be immensely helpful Also - were you charging the phone and have the MIUI battery bar active? On other phones I've experienced issues w/ video playback and that combo.
Turning screen off makes music player unusable - what do you mean? The long-press volume controls weren't working? The music stops? What app were you using to listen to music?
Very slow to wake - is there anything more specific you can offer here? Like an amount of time it takes to wake? That really shouldn't differ from stock at all - and there will always be a bit of lag there (though I never have anything more than a second or so).
And fwiw TSMParts is regrettably not an independently functional sort of apk. It requires a bunch of other edits throughout aspects of /system to actually work. But man that would be nifty
Click to expand...
Click to collapse
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.

Meanee said:
I didn't really so a lot of troubleshooting. It was a CNN app. I pushed Back button from an article and got a black screen only with top bar active. Pushed power button, screen turned off. Then it stayed off. Had to do a battery pull. Not charging, no MIUI battery bar.
As for music, turning off the screen makes it stutter and slow down. Turning screen back on fixed the issue. I am guessing with screen off, clock rate is way too low to support music playback.
Very slow to wake could mean 2-3 seconds after I push the power or home button. Same thing with phonecalls. I can hear the phone ring but screen would stay black. 2-3 seconds later I can finally see who's calling.
I guess I can resolve most of these issues by tweaking clock rates, just wish I had time to read up on it.
Edit: Forgot to mention, I am on 1.4. Downloaded and flashed yesterday.
Click to expand...
Click to collapse
Hmm... my thoughts:
- That may have just been wonkiness in the CNN app - not sure if anything I did could impact something in the way you described (but of course I could be wrong).
- Yeah that is way slow - and uncharacteristic from my experiences at least
- That plus the music issue makes me wonder - are you just using the stock kernel? If so you can't do much in the way of clock rate tweaking, but I also find it curious as I've heard little in the way of issues regarding the stock kernel.
- Did you do a full data wipe before installing?
Regardless - I am sorry to hear about the poor outcome - feel free to PM me if you want any suggestions/help troubleshooting. I'm not the best at it (especially remotely), but I'll try
Sorry for the off-topic stuff OP!

The question doesn't make sense.
Rooting just means you unlock the root account on the phone to have superuser access. This is required by some useful apps (ProxyDroid, Paragon NTFS & HFS+ which lets you mount any USB stick or hard drive using an OTG cable, backup programs...). You can very well keep the stock firmware and just root it, which is what I ended up doing on the Note II.
On my previous Galaxy S2 CM10 was working like a champ, so I figured I would try it on the Note II... I think at this point it's a total disaster and completely unusable, just not ready for prime time. Bluetooth is completely broken, the camera doesn't work, the video driver has problems, and most of all you lose a lot of the cool things you get with the stock firmware (multi-windows, stylus-specific features, etc...). Good enough if you're contributing to the ROM development and testing for bugs and missing features, but painfully not ready for prime time. The big problem is that you just don't know what feature will break next and will let you down right when you need it.
So for me, it's stock until CM10.1 goes RC. But of course I rooted it because I want to be able to use some apps that require rooting.
Note that some Samsung apps (Readers Hub) detect SuperSU and refuse to run. Uninstall SuperSU and use Superuser instead, and use Voodoo OTA Rootkeeper to temporarily unroot the phone if you need to use them.

Rooted on Stock Rom is the way to go.

I stay on stock ROM for Wi-Fi calling, but I had it rooted in order to transfer application data.

Backup your efs as well, because there has been several people that have lost their imei.

New Note 3 very glitchy ... is this common?

Hey guys. I moved up from a Verizon Note 2 to a T-Mobile Note 3 two weeks ago (and switched carriers obviously).
Since then, it has happened that the phone gets stuck and then reboots.
Three times it's happened while scrolling in the 9Gag app, once while in the Play Store and once as I was unlocking the phone using a pattern an e-mail came in and the vibration got stuck for a while and then rebooted.
I've also noticed that if I have WiFi on, Skype logs in fine, if I leave the house so I go on 4G and then come back to WiFi, Skype refuses to see a connection unless I turn off WiFi or reboot the phone.
Then yesterday the entire phone was in landscape mode even though I had auto-rotate enabled, and whether I turned it off and back on, it stayed on landscape mode until I rebooted the phone.
My wife also has a T-Mobile Note 3, bought at the same time. For her it's rebooted only once so far while using Google Maps.
I've had S3, Sprint Note 2, Verizon Note 2, and my wife has had S3 and S4. Now we both got these Note 3s and man, this is way too glitchy. On the Note 2 I went over 2 months once without rebooting the phone. This one has rebooted itself 5-6 times in 2 weeks!
We're updated to KitKat 4.4.2 (OTA) and not rooted or modified in any way (yet). So I'm wondering if it's KitKat that is glitchy, since our phones before weren't on KitKat, or the Note 3s in general, or just my specific Note 3.
Would love any info on this. Thanks.

I would do a master reset. Worst case Odin stock rom. Avoid send in for refurbished one
Def don't root yet. Try and get phone stable first.
TWEAKED N3

If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
EDIT: if you don't mind me doing the noob thing and just asking, what's the easiest way to get root? I don't particularly care about a customized rom, but definitely want system access to get rid of all this bloat and install my customized video ringtone program.

Max_Pain said:
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
Click to expand...
Click to collapse
It not harder it more steps and Odin is best. But if you have hardware issues on stock u need to know before root
TWEAKED N3

Yeah, doing it now. Going to go stock but rooted so I can have some control. Maybe later on i'll flash a custom rom when I have time to go through them and see which one suits my style.
Thanks.

I'd suggest doing a factory reset b4 anything, then if that dose not work, use odin and flash kit kat... then if ur issue persist, maybe contact samsung.
Sent from my SM-N900T using XDA Premium 4 mobile app
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Also one u have root, go to the play store and check out greenify. I swear by it. C:
Sent from my SM-N900T using XDA Premium 4 mobile app

I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?

Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
Hibernating battery hogging apps and their associated services when they aren't being used.
Sent from my SM-N900T using Tapatalk

Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
I be honest I don't use it and this kk really doesn't drain the battery like job did stock
TWEAKED N3

I haven't noticed any sort of glitches since I've had my N3. Even after putting the jedi ROM on it seems fine. As far as the battery goes, I know there are alot of complaints that kk has killed alot of the life out of it. I haven't noticed a difference in battery life either. It holds a charge all day and some. And greenify is to stop or freeze certain apps that run constantly in the background that could drain the battery. I personally didn't really like the app nor did I need it.
Sent from my SM-N900T using Tapatalk

Well, I went on a stock deodexed rom and got on lean kernel for a while... but it's still doing the stuck-and-reboot thing. It's always related to the touch screen, so i'm either scrolling or clicking to open an app or settings within an app. The phone gets momentarily stuck, then full reboot.
How long do I have to get it exchanged in store? I wonder if i'm within that time frame. It's definitely not normal and getting very annoying.
If i'm outside the time to get exchanged in store, what's my next best option?
I have to say that this experience with the Note III has been nothing short of disappointing and nothing like the two Note IIs I had before (different carriers for each, neither broke or gave any problems).

Here's an update for anyone who finds this and is in the same boat.
I had two issues: 1) the power button became so recessed that it's a hassle to turn on/off the screen, 2) the phone kept turning on and off, by the end almost constantly, without any obvious pattern beyond it getting stuck after me touching the screen (i.e. never just up and turned off while being idle).
Because of the recessed power button, T-Mobile shipped me a replacement phone. Should arrive tomorrow.
I still tried troubleshooting the rebooting issue. I think it came down to one or a couple of the following:
1 - Go Weather EX
2 - Freeza's CRT mod
3 - flashable 1% battery mod
4 - bootanimation.zip support flashable script
5 - something in the Deodexed version of the stock KitKat rom
In prepping to take the phone to T-Mobile, I did the return to stock thing with Odin, putting back stock kitkat odex non-rooted rom. The entire afternoon I got not a single reboot. Since I came back home with the phone, I restored a backup I had made before doing the Odin stuff. Back to rebooting.
So I thought, let's go back to the stock experience like I had earlier, and restore my apps through the play store and manually hunt it down.
Now i'm running the stock odexed kitkat rom, rooted, with lean kernel, with a whole bunch of stock apps frozen, and virtually all my apps and not a problem. I avoided 2-4 since those mess with the framework and I thought it could have something to do with it. I removed Go Weather EX because I experienced a reboot once while setting it up as a live wallpaper.
When the new phone arrives tomorrow I'll try to duplicate my current setup and hopefully won't have any more rebooting issues. I hope this helps anyone experiencing the same thing. I know it's kinda convoluted and not very concise, but then again this experience has been nothing short of annoying and confusing.