I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.
Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.
I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/
Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.
So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.
Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
Related
Although I have been doing a lot of reading the last few months, I am new to posting, so please bear with. My DINC just started randomly rebooting about 2 weeks ago and I am trying to figure out why. It was running great before with (rooted) Skyraider 3.0 RC3 Vanilla, kings BFS#5, S-Off, 2.15 radio and HBoot .79. The problems began when I installed Juice Defender, didn't really like it, and then un-installed it. I did not disable anything JD did before un-installing. Now, with the same set-up as before, I get random reboots when I'm on Explorer for a few minutes, when GPS Navigation is on, and then randomly on GChat and the Market. It seems to happen more when the temp is higher, but it's rarely over 100 degrees F. Half of the reboots end up in QualComm debug mode. I have tried a full wipe and reinstalling the ROM, kernel and prior settings. The only thing I can think of is that Juice Defender changed some type of setting, application or system, and now it's having fits. I downloaded aLogCat and had it running during the last reboot and can PM the .txt file if you think that would help. Does anyone know what's going on or how I can fix it? Any help is great appreciated!
Also, the current applications that I have are:
ad-free
advanced task manager
beautiful widgets
setCPU
amazon reader
scorecenter
Mint.com
switchpro
bump
battery indicator
astro
root explorer
rom manager
barcode scanner
facebook
goggles
dspmanager
handcent
linpack
metamorph
mixing
papertoss
pandora
shazam
spare parts
tapatalk pro
titanium backup
weather channel
widget locker
BUMP....anyone?
mjmdmd said:
BUMP....anyone?
Click to expand...
Click to collapse
Are you overclocking? Some phones can't handle much and it's known to cause similar problems. Other than that I'm not sure if anything JD changes would remain once it's un-installed; but if so you might install it again, change everything back to stock, then un-install it. Just a guess, hope you get it figured out
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
SynbiosVyse said:
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
Click to expand...
Click to collapse
Same here. Exchanged it with Verizon, almost no questions asked. Got AMOLED refurb, so far so good. Replacement was with OTA installed though, so waiting for new root.
You should revert your phone to fully stock, turn S-ON, unroot, stock ROM, etc. Make it look as legit as possible. If your problems go away then obviously something got screwed up in the flashing process. If your problems remain, then it's something wrong with the actual phone, and since you just made it completely stock you're in the perfect shoes to go exchange it.
In summary, the best measure to take if you're having reboot problems is to exchange it at a Verizon store; that's what most people are doing.
I'm going to exchange mine tomorrow. It should be covered under the 1 year warranty so you should not need insurance to do it.
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Sounds to me that you have the faulty overheating 3G radio..it is a somewhat documented problem and I believe it's the same problem I have. The only solution is to swap it at a verizon store. I'm afraid other ROMs or anything else you do will not solve the problem.
mjmdmd said:
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Click to expand...
Click to collapse
Odds are your radio is failing, which is a relatively common problem. Your symptoms are pretty much a textbook example and something that I experienced firsthand on my previous Incredible. The only fix is a warranty exchange.
That's disappointing. Thanks for the info everyone. I guess it's time to start the process of unrooting...
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Miltos1 said:
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Click to expand...
Click to collapse
Interesting. I'm using the big batt too, but my only reboots happen with GPS. As I'm driving (unfortunately) with my Nav on, all of a sudden, I look to see what my next turn is, and I'm on the "HTC Incredible" splash screen! Most annoying thing ever.
I'm still waiting for a fix. I really don't want to unroot, lose everything, and have to exchange for a warranty phone.
By the way, with a fix like this, I feel like my blackberry days again!
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
MdX MaxX said:
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
Click to expand...
Click to collapse
downgrading your phone shouldn't be a problem at all.
download stock, wipe clean, flash through odin.
MdX MaxX said:
I've been having the strangest issues lately.
I'm running task's AOKP with ktoonsez's kernel. For the past month or so I've been getting random home button lag, wakeup stuttering, and general stuttery animations.
And I've recently discovered that I absolutely cannot use my phone at all while it is playing audio. If I perform ANY sort of action, music will stutter really badly (unlocking the device, turning off the screen, opening a folder on my homescreen, opening an app, clicking something within an app, literally almost ANY action that involves tapping the screen will cause a stutter). Happening on both Underwear and ktoonsez kernels, even on stock settings.
I've tried clean wiping many times (at least 5 times in the past 3 days) and clean wipes tend to fix the issues initially, but things gradually get sluggish again after a few days. I've tried ktoonsez's kernel on straight up stock settings, and I've tried task's Underwear kernel on stock settings, and I still get these things.
Now, I see no one else in any of the threads having issues like this. So I really don't think I can blame the ROM or kernel.
So is my phone just all of a sudden hating custom ROMs and kernels? Is my processor caving or something? I can't think of any other good reasons why my phone and only my phone is buckling under the latest ROM releases. I've tested my SD card and speeds are what they should be.
Do I need to literally purge my phone, return to bone stock firmware, and start over? I'm not sure how else I can 100% determine whether it's my phone acting up or something software/firmware related. But I'm wary also of issues with jumping from 4.2 to 4.1 and back.
This is all just kinda frustrating. I'd just like to know whether it's possible that my phone is simply deteriorating before me in some form or fashion. Could the flash memory be acting up? Could the GPU be problematic? I really have no idea.
Click to expand...
Click to collapse
Try a full wipe and a clean flash first without ktoonz kernel. I know some phones just can't run it without issues.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've noticed AOKP's rom and Task's AOKP can sometimes have issues like these, even when doing a full wipe/clean install when coming from anything other than stock. Once you go back to stock, wipe and reflash, I think you'll be alright. When I flash aokp that way, it's usually such a good running rom I have to talk myself into even considering putting anything else on my phone
So. I decided to wipe, flash back to bone stock 4.1.1 through Odin, re-root (root-injected tar method), re-install TWRP, wipe, and re-install AOKP fresh (no ktoonsez kernel).
On the fresh install, I logged into Google, downloaded Play Music, and started playing an MP3. Aaaaand...the stuttering is still there. Music still stutters essentially every time I touch something on the screen.
And every few transition animations is still choppy.
What to do now?
I suppose I'll re-download AOKP to see whether I got a bad download, but I doubt it. EDIT: Nope, same hash.
My phone just doesn't seem to like the latest AOKP builds very much...
I'll play around with it some more.
Just go to recovery, wipe cache n dalvik, and you should be good
Sent from my SAMSUNG-SGH-I747 using xda premium
did you see if the problem persists while on stock?
sent from my i747 with xda-premium
Did you get the same lag and abrupt behaviour when using a different music player app?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I would try a different music player and perhaps even a 4.1.2 aokp instead of the latest 4.2. This would help narrow down/eliminate the issue
I also have this stutters in any rom/kernel i test. micro stutters here and there, when a few weeks ago there was none. all of a sudden stutters and lags on drawer and opening applications. antuntu benchs show the same results so i dont get it.
for future reference: benchmarks don't matter here. there are a few who use them to show how good their phone is, what really matters is real world performance.
if it's happening with everything including stock, I'd gander that it's a hardware issue and you should try for a warranty exchange.
sent from my i747 with xda-premium
Or just flash another ROM
Sent from an ATM machine
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
gaveup said:
Before I start with this, please forgive me if I have touched on something that has already been covered, but this is driving me crazy.
As of recent, I have noticed my phone is locking up while I am on a call. Kind of intermittent, so it has been hard for me to track down the source, but so far this is how it is working:
When I am on a call, I will pull the phone from away from my face and will notice it is locked up. It will freeze on the call screen itself, but I am still able to talk to the person on the line for about 10-20 seconds and then it kills the conversation. The only fix is to pull the battery and reboot.
At first I read somewhere this happened to others on the ROM I was currently using (Build 3 of Slimbean). To fix I figured I would revert to a build 2 version, but still had the issue sometimes. Flashed tasks AOKP and it was still doing it (seemed more frequent actually). Currently I am downloading a TW ROM and will be testing that as well.
At this point, I am pretty sure this is ROM related as it is only locking up when I am on a call (maybe 50% of the time and at different times)and it would be odd for hardware to be the cause of it. Just seems weird to me.
Before it is mentioned, I am using TWRP and never do dirty flashes. For testing purposes, I have been wiping cache, dalvik, factory reset, format system and formatting data. Never had this issue before and I dont recall having it before most AOSP roms updated to 3.4.
Click to expand...
Click to collapse
It's quite possible that your phone isn't handling the 3.4 kernel very well. Although, did you try Task's last update (4/9)? I haven't had lockups on the last couple builds.
But if you keep getting them, revert back to a 3.0 kernel/ROM build until 3.4 is more stable.
I bought my N7 (Flo) in early January and am loving it except for the random reboots. I did a factory restore and on the first boot got up to around 92hrs of uptime with about 50% battery usage before a crash. Subsequent boots aren't quite hitting that mark. As everyone knows it's hard to tell at exactly what intervals as it will crash while it is sleeping, not just in use.
Has switching to a custom kernel provided better stability for anyone?
Yes. I can only speak for CM11 but flashing Glitch kernel completely stopped the reboots and also the random buzzing noise from the speakers.
I didn't try the kernel on stock (also had reboots) but go ahead it might work. Make a nandroid first.
I really thought the reboots were hardware related but after going through three devices, 16 and 32gb models and 06, 07 and 08 build dates, they all randomly rebooted. Glitch has solved it (again at least on CM11). I'm sure it's a software problem now.
So, here's my experience with this. I bought my first nexus 7.2, at a best buy in north Dallas, in October. I experienced random reboots, right out of the box, about once a day, usually when I was browsing chrome, or when the tablet was sitting on the home screen without being touched. My gf bought a nexus 7.2 as well, at the same store in November, and she was not experiencing any random reboots, hers has always been stock, to this day (my suspicions began). I figured it was a software, or app problem, and waited for a fix from Google, or my app developers. Tried various custom Roms in the meantime (cm11, dirty unicorns, silmrom, and many more). I also tried various kernel's, in combination with said Roms (Franco, ElementalX, glitch, bulletproof). I had random reboots with all combinations of Roms and kernels. Did a factory data reset after every update from Google, and tried it for a week or so every time. Still experienced random reboots. I finally got fed up and took my table back in early January, to the same best buy in north Dallas. After receiving my second tablet, I kept it stock for a week, and then restored my preferred twrp backup, that I had taken with the rebooting tablet ( stock 4.4 krt16s, xposed framework, ElementalX 2.2 @1.7 and 450, with the motoX dalvik and bionic patches). With the new tablet, I have not experienced one random reboot, either with the stock software, or the custom software.
So, long story short, if your experiencing random reboots, if you have the ability to, I would take it back. Maybe you can fix it with software enhancements, but IMO it just shouldn't do this, stock or otherwise, and warrants a return.
Whatever you choose to do, I hope it works out for you, the reboots were personally driving me crazy, and I'm glad my second tablet doesn't reboot like its got a mind of its own.
thisguysayswht said:
So, long story short, if your experiencing random reboots, if you have the ability to, I would take it back. Maybe you can fix it with software enhancements, but IMO it just shouldn't do this, stock or otherwise, and warrants a return.
Click to expand...
Click to collapse
I also bought mine at a Best Buy but am a few weeks out of the return period. I'll give it a try and see if they'll take it back. I was really trying to avoid sending it to Asus. Thanks for your input.
I never had any random reboot issues however, it might have been due to having it running on CleanRom 2.6 and ElementalX Kernel since almost day 1. These two make the device so snappy I don't even care.
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.