Database Users

Why does my DZ fail me when I need it the most

Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?

Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer

makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms

skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?

As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium

Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.

redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.

its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said

Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App

redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.

i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.

swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.

makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html

[Q] Random Freezing

I'm currently having intermittent problems with random freezes. My nook freezes up and becomes unresponsive to input. I'm forced to manually shut down the nook by holding the power button for 4-5 seconds, and restart.
The last time the nook froze was when I tried to download the doubletwist player app from the market. After it froze, i restarted, and then the installation went on just fine.
I'm currently running CM 7.1 stable on a sandisk 32gb class 4 card using verygreen's method. I got the latest gapps (i think 0828), and the market is at version 3.3.11. I don't have much loaded on the nook just yet since it's still new to me, so it's strange that I'm having instability issues so early. I have also tried fixing permissions by using ROM Manager without much effect.
Also, on a side note, it seems like my nook does not update any accounts (gmail, imap email, facebook, etc) when my screen is off - is that normal? My wifi is always on and active, but the accounts don't update/sync until the screen is turned on.

Hmmm... so no one has experienced freezing issues for the Nook Color? My nook seems to freeze at least once a day - it ranges from downloading apps, playing games, all the way to typing an email...
Any insight would be greatly appreciated!

I rooted and had my Nook all for a day, but rooted it immediately.
Only thing I can think of:
1. Are you OCing?
2. Did you format data before installing the rom?
3. Did you flash a different kernel?
Sent from my SPH-D700 using XDA App

About the syncing issues, I don't know if the nook is setup to sync like that? It has wifi but I don't believe it is on all the time to save battery... in all honesty its all new to me, but we can learn together.
Sent from my SPH-D700 using XDA App

Well it does seem like it syncs some data now... for instance my yahoo mail, and my work's exchange mail. But it doesn't seem to be very frequent... i guess maybe that's just how it is?
It still does freeze on me though, but to answer your questions:
1. Are you OCing - Yes, I do have it OC'ed to 1200mhz
2. Did you format data before installing the rom? - I'm back onto MIrage's 7.2 RC, but i did not format the data beforehand... maybe that's it.
3. Did you flash a different kernel? - Yes, i flashed to the new kernel that fixes SOD.
It's all new to me too, but i'm beginning to think you get what you paid for in this instance.

switch81 said:
Well it does seem like it syncs some data now... for instance my yahoo mail, and my work's exchange mail. But it doesn't seem to be very frequent... i guess maybe that's just how it is?
It still does freeze on me though, but to answer your questions:
1. Are you OCing - Yes, I do have it OC'ed to 1200mhz
2. Did you format data before installing the rom? - I'm back onto MIrage's 7.2 RC, but i did not format the data beforehand... maybe that's it.
3. Did you flash a different kernel? - Yes, i flashed to the new kernel that fixes SOD.
It's all new to me too, but i'm beginning to think you get what you paid for in this instance.
Click to expand...
Click to collapse
1. OC to 1100. OC'ing to 1200 has no noticeable increase in performance, it overheats the device, and burns through battery like no tomorrow. I also suggest setting your minimum frequency to 1100. It sounds counter-intuitive, but the minimum frequency shows no real effect on battery. LeslieAnn (Harmonia dev) linked to a thread about the effects of overclocking on the battery (The OP was testing on the LG Optimus V to be precise). This person benchmarked and tested at different clocking speeds and found that if you set your CPU to it's highest stable clock speed (806 for the Optimus, 1100 for the Nook) it's actually better on battery life. So, my suggestion is set it to 1100/1100 min/max.
2. *facepalm* Tsk, tsk, tsk. I tried the Mirage port for the Nook and found it to be very buggy. The keyboard was always glitching, apps FC'd, etc. I'm not necessarily putting Mirage down, but it has quite a way to go before it's ready to be run on Nook. ATM I'm running Dalingrin & Fattire's CM9/ICS build (though it's only an early build, an RC maybe an alpha build at most at this point), it is amazing, aside from some bugs (you have to use a bootable microSD to utilize recovery) it's superb. If you feel a need to change ROMs, I'd go with either CM9/ICS: http://tinyurl.com/7ny5r5c Or one of the CM7 nightlies (they are fairly stable for nightlies and include plenty of goodies).
3. SOD... never had that. So I have no advice there, apparently you got it patched. I'm running Fattire's 2.6.32.9 kernel for ICS (comes standard with the ROM), no problems so far.
Edit: Clock to 1100/1100 on the interactive or interactiveX governor. Forgot to write that.
Edit #2: I'm a bit unattentive today (3.5 hours of sleep...). To address your email sync issue, I'd go into settings and see what your sync interval is (mine is set to every 15 minutes, screenshot here: http://tinyurl.com/cgkjnxe). If you have it set to something low like that and still have sync issues, it may be due to ROM bugs, or a plethora of other reasons (possibly WiFi speed?). If setting it to a lower sync interval helps, so be it, but if not, I'll look further into the problem. And by the way, check out that sexy ICS interface. This shall be my last edit.

worldindo1 - do you run CM9 off of your emmc? or a sdcard? I'm thinking about moving over to the emmc, and wondering what the benefits would be.

switch81 said:
worldindo1 - do you run CM9 off of your emmc? or a sdcard? I'm thinking about moving over to the emmc, and wondering what the benefits would be.
Click to expand...
Click to collapse
By default, the way Dal and Fattire have it set up, it automatically installs the boot to eMMC. Which means the loss of 5GB of storage space. But with another .9GB on internal, and up to 32GB of external, app and media storage should be no problem. So there is a con, but the pro is that you never have to worry about inserting SD to get into it.
Take heed to a few warnings:
1. Don't try to boot into recovery by using ROM manager or by Power+Home button. Use a CWR bootable. Otherwise, you corrupt your boot and have to restart.
2. GApps is still a bit buggy (unless you build straight off from their most current source) so it can/will FC on you.
3. Make sure you flash the proper version of GApps: http://db.tt/ujcVWK1U All other versions of GApps for ICS have nfc (Nook doesn't have nfc) which leaves you with a completely unusable device due to cont.force close of nfc service.
4. USB transfer DOES NOT WORK! D: If you want to put files on your SD, either use a phone or use a microSD adapter.
Note: Took down the link because something in the ZIP (not quite sure what) may have corrupted. Now I say this, but don't freak out if you already downloaded it. Whatever happened within the ZIP wont harm your Nook so don't worry about it.

The CM9 zip can either install to emmc or SD depending on which installation method you use.
Which you choose to do is entirely dependent on your usage of the device and whether the NC is a working tablet or an experimental device. Some are OK with current state of CM9 and put it on the emmc for convenience.
At the moment I chose to leave CM7 on the emmc for normal usage and swap in a CM9 SD card to play with the current state of play in its development.
On the subject of OC I have pretty much always run at 1200 On Demand with the default minumum. I do tweak the voltages down to the value originally suggested by Dalingrin. I have no overheating and battery life is great.
For freezing it maybe be worth upping the version or trying out the KANG MiRaGe which has all known fixes in.

bobtidey said:
The CM9 zip can either install to emmc or SD depending on which installation method you use.
Which you choose to do is entirely dependent on your usage of the device and whether the NC is a working tablet or an experimental device. Some are OK with current state of CM9 and put it on the emmc for convenience.
At the moment I chose to leave CM7 on the emmc for normal usage and swap in a CM9 SD card to play with the current state of play in its development.
On the subject of OC I have pretty much always run at 1200 On Demand with the default minumum. I do tweak the voltages down to the value originally suggested by Dalingrin. I have no overheating and battery life is great.
For freezing it maybe be worth upping the version or trying out the KANG MiRaGe which has all known fixes in.
Click to expand...
Click to collapse
I've found it to be more stable on eMMC. Installing via recovery menu by default put it on my eMMC. The loss of space doesn't bother me, even on other ROMs. There is actually a way to trick the device into thinking that eMMC is an SD card (basically the ability to install apps on "SD" without a mounted SD card, as well as media storage)

So I have not yet tried CM9, or putting the OS on the emmc... however I did switch over to LauncherPro recently.
I have to say... I've been having a lot less issues with LauncherPro... and not to mention, there is a HUGE performance difference. The scrolling of the home screens are so much smoother with LauncherPro than ADW. So I would recommend anyone to give that a shot!

[Q] CM10.1 - Ready for Prime Time on the Nook Color (encore)?

I have a Nook color wiped with a full version of the last stable release of CM7. It works well, but with that irritating problem of wifi reliability.
I would like to upgrade to CM10.1. The goal is to use the Nook as a development platform, while still sharing it with my wife to actually read books.
Here is the questions: Is release candidate two (RC2) of Cyanogenmod 10.1 stable enough on the Nook for daily use? I want the latest and greatest, but I don't have the time to constantly be chasing down problems, nor do I want my wife to kill me because her "book reader" has become unstable.
Do I hold out for RC3, wait for a stable release, or jump right in with RC2?
All comments and suggestions are welcome.

While CM10/4.1 was promising, CM10.1/4.2 has been a pain.
The interface seems all weird (it use a Phone interface instead of Tablet), and the performance makes the Nook Color nearly unusable. I'm talking single-digit framerates and choppy scrolling.

Personally, I found PA to be smoothest I tried... surprisingly smooth for the NC.
YMMV

I don't know about the others, I lost WiFi connections once every 2-3 hours using the most recent builds including rc2.
The fix is just turning the eifi off and on again.
However I never got sod so it is acceptable for me.

Thanks for the info guys, but the question is still up in the air. What condition is CM10 in for the nook? The wifi issues in CM7 make it useless as a connected device anywhere except with my home router (go figure). Is anyone using CM10 as their daily driver, and if so what build are you using, and where would you place the frustration level on a scale from one to 10?

codingCat said:
Thanks for the info guys, but the question is still up in the air. What condition is CM10 in for the nook? The wifi issues in CM7 make it useless as a connected device anywhere except with my home router (go figure). Is anyone using CM10 as their daily driver, and if so what build are you using, and where would you place the frustration level on a scale from one to 10?
Click to expand...
Click to collapse
I'm using CM10.1, RC2, and I'm having only very minor issues that are probably due to the ancient hardware (Flipboard sometimes freezes on me after 10 minutes, and browsers are slow, except for the very light Naked Browser). Everything I need works great, including wifi. I took it on a three week business trip to South America recently and only used my laptop once, doing email every day with no hiccups. I think it helps to tweak some settings, and use the Seeder app. Scrolling isn't butter smooth, but it's very good. Frustration level close to 0. Go figure.

I used CM10.1 for few months, it worked very good. I would say my frustration level maybe 1, and pretty much nothing compared to the satisfaction. I liked the key board, wifi connection, HD video play (for example in youtube), Browser and new UI in CM10.1 over 7.2.
recently I upgraded to CM10.1 RC4. I also did the following things to make it better. after boot up, it still has close to 150 MB memory.
1. tablet UI by autopatcher.
2. V6 SuperCharger
3. ES Task Manager to disable some startup services like Email, Email Exchange and etc.
4. Seeder.
The result is very good. It runs very smooth.
Only frustration is the speaker's volume which is low. I am using Speaker Boost, looks like helped little ( but not very sure).

xflier said:
1. tablet UI by autopatcher.
Click to expand...
Click to collapse
Has anybody posted a zipfile for this version?
Only frustration is the speaker's volume which is low. I am using Speaker Boost, looks like helped little ( but not very sure).
Click to expand...
Click to collapse
I find that it works for some apps, DSP Manager works for others.
Sent from my NookColor using xda premium

I uploaded RC4's tabletUI patches, and you can get them in my signature link for My 4 Shared.

I tried one of the RC's back in the day for CM10 and didn't like it much. It seemed slow and glitchy, and it kept corrupting my SD card, so I went back to CM7 for a while, and then tried the CM10.1 nightly for 6-17 yesterday and had SD card problems again. Switching to a higher quality SD card fixed that problem, seems 4.x's file access methods make it more finicky with external media than 2.3's. According to LMT's status bar, my NC is running at 1000mhz, and everything has been fairly stable, although there are a few apps that seem to grind it to a halt, most notably the new Opera browser, although I hear that may just be an issue with their new version, using Opera classic seems to run fairly well. As far as getting the true tablet experience, I had to switch the launcher over to Apex, which has a tablet mode that removes the phone-style dock. On another note, I have two Android phones, an older one running CM7, and a new one running ICS out of the box, tried wireless tethering on each and found that my NC could Ad-hoc into the newer one and share it's internet at remarkable speeds, but couldn't maintain a connection to the CM7 phone even if I skipped DHCP and manually set the IP. I tried Bluetooth on this one and found that neither Sixaxis or Wiimotecontroller worked, but the NC did detect the Wiimote I tried, so I know Bluetooth is working. If I can find my BT headset, I'll give it a try and see if I can't make some internet phone calls. At this point, I'm going to be using CM10.1 as a daily driver, I think it's VERY usable, with my only annoyance being that it's a little slow to boot - any custom boot animations I use other than the one that comes with it are choppy and freeze up, and once the OS has loaded, I have to wait 10-20 seconds while the lock screen says (WIDGET LOADING) to even get the lock screen clock, but after that it's smooth sailing.
On the subject of reading books, I installed Moonreader+ and read some books on it yesterday, so that's still working just fine.

Nook Color Sudden Shut Down CyanogenMod 10.1

Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.

Ethan_Kok said:
Recently I upgraded my Nook Color from CyanogenMod 7.2 to CyanogenMod 10.1 stable. After that, somehow, it kept shutting down every half a minute or so when in use and when left alone. I did not touch the battery, the CPU is clocked at 300 MHz to 1.1 GHz, screen set to 16 bit mode, GPU untouched. Has anyone else had this problem and is there a way to fix it? Thanks in advance.
Click to expand...
Click to collapse
I upgraded to the latest stable CM10.1.2 release and have started getting random sleep of deaths (SD install). I've had them while plugged in, not plugged in, with screensaver on, with screensaver off (thought maybe keeping it active would help prevent)... I can't seem to find a pattern. I've tried every nightly since and am still seeing it. I tried rolling back to the first stable release, still there. I'm going to try rolling back from 1100 MHz to 1000, then 800, to see if that helps at all.
I'm a total newb to debugging this thing, but I'm happy to try and pull any logs to post if someone can point me in the right direction (I've looked around before on how to do this but get confused easily). Also, I'd be willing to try a clean install, but don't want to go through the hassle of reinstalling everything again. If there is a quick way to backup programs, I'm all ears.
The good news is, it runs great when it's up. Quite smooth. Pretty awesome stuff.

I believe Titanium Backup should back everything up.....
I have downgraded to CyanogenMod 7.2 as I am very exasperated with this issue, the short battery life and lagginess that the upgrade has brought.

[Q] Apps Close

Hey guys I've been having a major problem with most apps and games on N& running P.A.C. This problem plagued my device when I was running PA as well. The main issue rests with apps closing by itself after a few minutes,as if the device had run out of memory even on a fresh boot. For example I would be in the middle of note taking on Evernote and few minutes in it would just close. Same goes for YouTube and ALL games. Funny, Lightning Browser seems to be the only one that stays in memory. I'm running it on stock kernel Android as well so tracing the root cause has been difficult.
Any advice would be great since I'm in the end of my ropes!

fliparsenal said:
Hey guys I've been having a major problem with most apps and games on N& running P.A.C. This problem plagued my device when I was running PA as well. The main issue rests with apps closing by itself after a few minutes,as if the device had run out of memory even on a fresh boot. For example I would be in the middle of note taking on Evernote and few minutes in it would just close. Same goes for YouTube and ALL games. Funny, Lightning Browser seems to be the only one that stays in memory. I'm running it on stock kernel Android as well so tracing the root cause has been difficult.
Any advice would be great since I'm in the end of my ropes!
Click to expand...
Click to collapse
Start by flashing stock and see if it still does it. If not, try a different rom. If it does it on stock....then you may have screen issues...like phantom touches of your home button?? Or something.
Try whatever the nexus 7's version of a log cat is and see what it says when it happens.
Sent from my cellular telephone