My phone seems to be experiencing random lockups/screen freezes. These seem to be more frequent when I have the mobile internet activate and i’m in a lower signal area or when I try and end a call through my cars Bluetooth handsfree system but they can happen any time, even sometimes when rebooting the phone, pulling the battery after a lockup has occurred and switching back on, the phone will reboot but freeze once again on the unlock screen.
I have not updated the radio, I am currently on version 5.11.05.27, as I have heard all manner of stories about bricked devices, but could this be the issue or is it more likely to be the sd card, or something else completely?
Any help you guys can give me would be greatly appreciated as am going to break the back cover of my phone soon, with the number of times am having to pull the battery.
I've ordered a new sd card to see if that will make a difference. The last time I used CWM to create the ext partition, should I do it this way again when the new card arrives or try a different way?
try using gparted live cd to create a partition, but i do not think your problem lies with your sd card
have you tried another rom to see if the problem persists?
Ok, i'll try the gparted method next time.
Yeah the first rom I tried was Gingerburst, that seemed to be ok to start with but sense would crash quite often and then the screen freezes started, so I moved to leedroid and although sense never crashes, the screen lockups have continued. I have looked on various other rom threads and i noticed on the Insertcoin webpage there has been a lot of mentions about the latest kernals causing screen locks, so I might try Insercoins v1.1.3, which everybody seems to be reverting back to and see if I have any more success with that.
I have recently tried InsertCoin CM7/STOCK 1.1.3 and again I seem to be experiencing screen freezes which always seem to be happening when the signal is low or when travelling in the car so possible signal fluctuations.
Does anybody have an ideas on how to fix this issue, would flashing the newest radio help and if so what is the best/easiest way to do it? or could it be a kernel issue, if so what do you all recommend.
Any help would be greatly appreciated.
I would have the freeze issue only in camera mode,otherwise its fine...probably some glitch in my phone,try full wipe n reinstall
I see that this tread is quite old, but i have the same issue with screen freezing. I was useing Leedroid 3.3.3 port on my HTC desire, for 2,5 month and then it started. Ive been trying everything form more than a month now (factory reset, installing aps one by one....) How did you solve the problem if you did at all? or what was the couse
Thx
Do you use software / scripts to control CPU frequencies / voltages?
MatDrOiD said:
Do you use software / scripts to control CPU frequencies / voltages?
Click to expand...
Click to collapse
Well i thought of this as well since the freezing started around the same time as i installed SetCPU (+/- a couple of weeks) but since the 2nd factory reset and installation of apps one by one i excluded the program but the problem still occures.
Also PowerAMP was a problem since i dont install it the freezing is not as ferquent (only every 2nd day not every day....)
I've read it somewhere that UV can couse the porblem, but i've never change that.
Also if i have more apps installed then dose my cpu required higher UV? If yes so then i can try to higher their default level.
Related
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Do you have setCPU ?
i know sometimes when people set screen off properties to low it freezes and needs a batt pull
Funny enough, I guess the problem started after I installed that. I cleared its settings and cache and uninstalled the program hoping it would fix it, but no dice. I figured that would fix the issue if it was related
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
I tried that once, didn't seem to help but I will give it another shot.
I am running stock DK28 ROM, maybe a fresh install will help?
o and you wouldn't happen to be on viper rom would you ?
iSaint said:
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
Click to expand...
Click to collapse
Set it at 200 min.
not running viper ROM. I am running stock froyo with root access.
DiGi: Is that what you have it set on? I thought I read somewhere not to set it that low.
I was running on 200 min just fine. I haven't had setcpu on my phone for a little while though. I think 100 is too low and causing the problem. 200 didn't cause crashes for me.
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
djbacon06 said:
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
Click to expand...
Click to collapse
Odin
reflash your rom
probably something went wrong when flashing
this happens to me when my battery is low (stock dk28)
it's working for me
djbacon06 said:
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Click to expand...
Click to collapse
Recently changed my phone to android and my phone wouldn't wake up every time it goes to sleep more. (Radio 2.10.50.2)
looked and tried a lot of suggestions (format SD, flash ROM, update setup.txt file and etc) but nothing worked until I flashed the new radio 2.14.50.
And it's been working fine for a day now (finger crossed).
Do you have adjbrightness? Theres a problem with it on galaxy s phone where it won't wake up that they haven't been able to fix and that may be your problem.
Did you ever figure out how to fix this "no wake up" issue? I had this problem out of the box with my mini. So does my friend.
It started when I first installed leedroid 2.3d after rooting my fone, then with CM7 RC1, Modaco Fr11 (default options, with MoDaCo additions), CM7 RC2 and StarBurst Lite. I faced the same issue while using Google Maps (data & GPS on). It keeps rebooting. Sometimes it would reboot within a minute or so after starting Google Maps. Sometimes it would take 5 minutes. Not sure what the issue is, but I have a feeling this may not have anything to do with Google Maps or GPS. Cos couple of times the fone rebooted while playing some games with an active wifi connection. But the problem occurs 100% with Google Maps.
I never faced this issue before rooting the fone or even after rooting. The problem only started after flashing the first ROM. After that I have even tried restoring the previous backup for stock ROM, but even that started giving this issue.
Here are the details about my fone:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.14.05.17
8 GB micro sd card with 512 MB ext partition. I guess its class 4.
Another thing to note is that when I try use a memory card reader to read it on my windows 7 PC, it just wont show up. The same thing happens if I try to use gParted boot CD to read the card. However android seems to read it perfectly fine. I am even able to mount the card from fone using USB storage option.
Is this memory card the issue?
I forgot to mention that I was using apps2sd+ in some form or another for all ROMS except StarDust Lite which was using Data2SD script.
Have you tried running the application when it is stored entirely on the phone (not part or whole to SD)?
Reboots and Bootloops have been present in the latest ROMs. The latest Oxygen ROM has applied the Google update to apparently fix these. It's there to try in the ROM section for you 2.0.2.
Dude,
You're not gonna like what I'm gonna say, but your symptoms match those of mine. Check out the thread I created here.
Now, adding to that, the rebooting started again but this time when using Wifi for a long period, playing games and using mobile data.
What I'd do is try rule out Google Maps. Try use Navigon or iGo.
Two things I learned was that changing ROM's won't help. Neither will changing radio's.
Of course it could just be Brandall mentions.
brandall said:
Have you tried running the application when it is stored entirely on the phone (not part or whole to SD)?
Reboots and Bootloops have been present in the latest ROMs. The latest Oxygen ROM has applied the Google update to apparently fix these. It's there to try in the ROM section for you 2.0.2.
Click to expand...
Click to collapse
I haven't tried running an application purely from the internal memory. However when I restored my stock HTC Desire Froyo backup, the issue still existed. That didnt have any script for apps2sd+ so Google Maps was running purely from the internal memory. Anyways, I will try the Oxygen ROM later today evening and see if that fixes it. I have also ordered for a class 10 16 GB micro sd card. Lets see if that helps.
mr_norris said:
Dude,
You're not gonna like what I'm gonna say, but your symptoms match those of mine. Check out the thread I created here.
Now, adding to that, the rebooting started again but this time when using Wifi for a long period, playing games and using mobile data.
What I'd do is try rule out Google Maps. Try use Navigon or iGo.
Two things I learned was that changing ROM's won't help. Neither will changing radio's.
Of course it could just be Brandall mentions.
Click to expand...
Click to collapse
I have already ruled Google Maps out since I was able to re-produce the issue even with other navigation softwares like Sygic Mobile Maps & NDrive. I am even able to re-produce the issue without turning on GPS or using any navigation app. Just an active wifi and playing games will also reboot the phone randomly.
One thing I noticed today morning was that when the phone rebooted, the back of the phone was very hot. On removing the cover I noticed that the area below the SIM card gets hot. Is there where the processor chip is? Is it possible that may be somehow the CPU was over clocked by certain ROM which I have flashed before? Is there a way by which I can check this under current ROM (Stardust)?
thekonfuser said:
One thing I noticed today morning was that when the phone rebooted, the back of the phone was very hot. On removing the cover I noticed that the area below the SIM card gets hot. Is there where the processor chip is? Is it possible that may be somehow the CPU was over clocked by certain ROM which I have flashed before? Is there a way by which I can check this under current ROM (Stardust)?
Click to expand...
Click to collapse
I would suggest that first you monitor your CPU usage and battery temperature with SetCPU - it can be downloaded for free here http://forum.xda-developers.com/showthread.php?t=505419 (worth a donate though!)
You can set up a profile to monitor your battery temperature and sound an alarm if it's getting too hot. Running this whist testing your GPS may well diagnose the problem. You can also ensure that you are not somehow already overclocking (which I think is very unlikely).
If this is new to you, make sure you have a good read of the instructions so you don't blow your phone up!
Assuming overheating is the issue, then hopefully you are under warranty and you can return to stock and send the phone back.
For further diagnosis on CPU Usage, battery temperature levels and discovering apps that are taking up resource, I would suggest SystemPanel from the market https://market.android.com/details?id=nextapp.systempanel.r1 - it's pretty damn sh*t hot and has a monitoring service for diagnosis. I'm not sure if that's available on the free version though, but if you try it, you'll want to buy it anyway...
Let us know how you get on. Good luck!
I'm gonna be blunt, I've been through this.
You are wasting your time dude. If your phone is still under warrantee, flash an original RUU and take it back to get repaired.
Its a hardware problem.
brandall said:
I would suggest that first you monitor your CPU usage and battery temperature with SetCPU - it can be downloaded for free here http://forum.xda-developers.com/showthread.php?t=505419 (worth a donate though!)
You can set up a profile to monitor your battery temperature and sound an alarm if it's getting too hot. Running this whist testing your GPS may well diagnose the problem. You can also ensure that you are not somehow already overclocking (which I think is very unlikely).
If this is new to you, make sure you have a good read of the instructions so you don't blow your phone up!
Assuming overheating is the issue, then hopefully you are under warranty and you can return to stock and send the phone back.
For further diagnosis on CPU Usage, battery temperature levels and discovering apps that are taking up resource, I would suggest SystemPanel from the market https://market.android.com/details?id=nextapp.systempanel.r1 - it's pretty damn sh*t hot and has a monitoring service for diagnosis. I'm not sure if that's available on the free version though, but if you try it, you'll want to buy it anyway...
Let us know how you get on. Good luck!
Click to expand...
Click to collapse
brandall, I have now tried it all now but nothing stops the random reboots. I guess I will have to get it replaced while its still under warranty. Lately the phone reboots even without getting hot. Plus, it reboots even without having any active wifi or data connection. Just playing Angry Birds Rio or Angry Birds Seasons for a while will reboot the phone. The only time it doesn't reboot is if use the phone for listening to music or while taking calls or messages. Other than that, it will randomly reboot on using any "smart" application. Even the browser...its damn frustrating. Thanks brandall.
mr_norris said:
I'm gonna be blunt, I've been through this.
You are wasting your time dude. If your phone is still under warrantee, flash an original RUU and take it back to get repaired.
Its a hardware problem.
Click to expand...
Click to collapse
Thanks mr_norris, I guess I will have to get it repaired or replaced. Thats all that is left...
Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...
it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...
Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.
Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse
Try reinstalling the ROM or installing another ROM.
hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long
Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't
Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App
Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin
Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App
I got a freezing problem with my note2. It's quite a strange behavior, got worse pretty fast since yesterday (tried to reflect the situation exactly below).
The freeze behaves like: system freezes, apps freeze, buttons stop working, sometimes the notification bar pull-down still works for 1-2 seconds, BUT: animated icons in the notification bar are sometimes (not always) still animating up to 2-3 minutes. Can also happen with display off, can't turn on anymore.
Since I'm using a ROM that's safe from the SDS problem, it cant be that. Still I mention that I do have that insane chip (Type: VTU00M, FwRev: 0xf1).
My guess is its a hardware related problem, maybe the internal flash memory(?).
Still, it will be hard to restore back to stock for warranty with the usb not working to use Odin.
Original Baseband: XXALJ2
History of this phone (maybe not 100% accurate, it's hard to recall everything exactly):
Bought on release
rooted some weeks later
flashed CM ~spring, regularly updated
July: stopped showing modem signal strength
July: switched to Asylum CM10.x, updated on new version releases
September: USB stopped working correctly when connecting to computer (charging but no data, different cables, ports, computers)
October: started freezing randomly, approx every second day, getting slighly more often
Since Yesterday:
-did a full wipe/factory reset, reflashed rom. more and faster freezes
-as i was messing around, decided to do a modem update: from XXALJ2 to XXDMF1: radio signal strength working again. Freezing increased.
-reverted to backup, also restored old modem: Crazy fast freezings, withing 30sek after every boot.
-again some full wipes/clean install with different but still recent asylum roms: freezings a little better than with a backup, but still crazy fast.
-full wipe with format internal storage: freezes got better, occur after minutes instead of seconds. They still occur faster when using a backup instead of a new install. Same with CM 10.1.3.
No custom kernels used. Default governors. No TB restores or something that I could think of messing with stuff.
Any help or ideas are very appreciated
I could manage to restore stock via Odin (1 in 100 times it detects the usb connection on my laptop), with 4.1.1 Had a freeze, made the OTR update to 4.1.2. Had another freeze. After that 2 more updates. It also changed the Baseband every time, its now DMF1 (same as i upgraded). No freezes anymore. I mean, what the heck? This makes no sense for me at all. If someone can lighten me up, please, go ahead.
It all sounds like SDS. Don't forget that SDS happens if there is a memory block corrupted. If you were in an insane rom before (and you said you bought it in release so almost sure you did) the memory blocks got corrupted. that happened "a lot" of people in the SDS thread(between commas taking in account that here in xda there is not the whole group of people who bought it and percentatge is low).
I recommend you to use emmc brickbug check app and check the memory blocks(if you are rooted)
then if it is SDS the only thing that we can do is pray or wait to samsung not to give free repairs only to China.
hoping that you'll pass the blocks test and it was only a normal problem..
Sent from my GT-N7100 using xda premium
Thanks for your reply.
SDS was the first thing I thought could be the issue. But it run for months without a single freeze on a SDS-safe rom before it started.
The last thing I have done before reverting to stock was a memory check with emmc brickbug app, and it passed. I forgot to mention it, even it's very interesting: while the memory check was running I had the longest runtime without a freeze.
I'm thinking now of returning the phone for warranty because of the USB problem. It's probably too risky to get back to stock once again. If I even could manage to root it again. But tell them too I had freezes? hmm, it's really not happening now anymore
I have the same problem... no idea what should I do
well... Yesterday I took a try and swtiched the CWM. I had TWRP and I've switch to Phliz Touch, so far... 16 hours without freeze
Amit BL said:
well... Yesterday I took a try and swtiched the CWM. I had TWRP and I've switch to Phliz Touch, so far... 16 hours without freeze
Click to expand...
Click to collapse
hmm, I also switched back to CWM recovery (from TWRP) for the last boot (to restore the nandroid stock backup I did, but could manage to flash with Odin before I had to do it that way), that was the point where I was surprised that the emmc memory check did go through without a freeze. I didn't saw any relation to the problem here, but who knows?
So far 34 hours without a freeze
Sent from my Galaxy Note II using Tapatalk
dedors said:
I got a freezing problem with my note2. It's quite a strange behavior, got worse pretty fast since yesterday (tried to reflect the situation exactly below).
The freeze behaves like: system freezes, apps freeze, buttons stop working, sometimes the notification bar pull-down still works for 1-2 seconds, BUT: animated icons in the notification bar are sometimes (not always) still animating up to 2-3 minutes. Can also happen with display off, can't turn on anymore.
Click to expand...
Click to collapse
Same problem, been suffering with freezes for the last 3 weeks and the last 2 days have been 400% worse, found out about this emmc bug but cannot find any information as to how to fix it, some mention kernals, vodafone will not replace the phone unless their software update does not fix it, Running 3.99 RC2 Paranoid android. Anybody got any ideas?
Seems my phone is one of the effect chips with the emmc issue. Funny thing is i just flashed back to stock in order to take my phone back to the shop and its working fine.... not a single issue all day.
Is there something custom roms are doing that party causes this issue?
Sent from my GT-N7100 using xda app-developers app
Madnessx9 said:
Seems my phone is one of the effect chips with the emmc issue. Funny thing is i just flashed back to stock in order to take my phone back to the shop and its working fine.... not a single issue all day.
Is there something custom roms are doing that party causes this issue?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I was having different issues including freezes and WiFi/BT loss when kernels with undervolt installed. Usually from custom ROMs. The effect is prolonged sometimes till hardware reset done.
The only working solution (for me) is to use a kernel with controlled voltages and set all the voltages about 1000mV for frequencies below 800MHz. 100% stable,
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.."