Database Info

Random Shutdowns and LauncherPro

I've been very careful not to point a finger at a particular app as a cause of random shutdowns (other than aggressive user settings within SetCPU). Before I continue, let me say that I believe there is more than one culprit responsible for shutdowns and that most are caused by non-app related issues.
I've had my third device for 2-1/2 months. No shutdowns whatsover...until I installed LauncherPro last week. Then they started. I removed LauncherPro and - back to normal. Another user on another forum experienced the same effect and caused me to start this thread. I hereby declare an official suspicion that LauncherPro is one of the causes of random shutdowns. Before you react, I understand that many use LauncherPro with no problems. Great. I'm not saying that the app itself is poorly coded, but rather that it may begin a chain reaction in some devices that causes random shutdowns. I have not taken this declaration lightly. I waited a long time before openly stating my theory. I hope it proves of interest.

Are you using Task Killer? I was having the same issue and thought it was Launcher Pro for a while but when I stopped using Task Killer my random shutdown problems stopped.
Captivate Cog 2.2 Beta 9

No task killers.

I've recently had some extended freezes and one force close with launcher pro, and one shutdown when I was launching Vlingo and/or starting bluetooth, can't recall which step. Might be something to do with the recent update.
Sent from my SAMSUNG-SGH-I897 using XDA App

I suppose I can test this out on mine. I'll let you know what I find.

I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.

I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky

pezx44 said:
I suppose I can test this out on mine. I'll let you know what I find.
Click to expand...
Click to collapse
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.

pfroo40 said:
I was using LauncherPro on my previous handset which experienced random shutdowns, but the shutdowns continued even after reflashing to factory with no add-ons or apps. Not saying that LP isn't causing problems of it's own, but power issues exist regardless.
Click to expand...
Click to collapse
Agree. LP, IMHO, is simply offered as one possible culprit.

tysj said:
I've been using LauncherPro (and upgraded to Plus when that came out) since release. No random shutdowns. Actually no random shutdowns at all. But I guess I'm lucky
Click to expand...
Click to collapse
You are fortunate, as there are multiple scenarios under which shutdowns have occurred...e.g., during high charge percentages as experienced repeatedly by some. My LP experience is being offered as my phone has served as an otherwise stable environment.

Jack45 said:
Your device would have to be inherently susceptible to shutdowns caused by the action of LauncherPro for your test to work. If your internals are solid, nothing will happen.
Click to expand...
Click to collapse
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.

pezx44 said:
Oh I'm quite susceptible. I get it regularly until my battery is down to about 82. I've used LP the whole time I had the phone. Currently I am using Captivate Keep Alive and it seems to work. I also started another thread where I found that running Grooveshark keeps the phone alive for me. I can guarantee that my phone will shut off within a couple of minutes of unplugging it without these things.
I'm charging now. I have already backed up and removed LP and CKA. When it is fully charged I will unplug it and leave it alone for a bit and report back. I agree with people who say "hardware issue - return it" but I can't do that and don't mind testing different workarounds. So far CKA has been working pretty well for me but I'm open to running less instead of more to solve it.
Click to expand...
Click to collapse
Excellent. Two separate potential culprits - charge level and LP. I'm looking forward to your assessment.

I decided to reinstall LP to get a baseline. 6 minutes after unplugging it I tried to turn the screen back on and found that it had shut down. I recharged and repeated. Again I found it had shut down when I checked after 6 minutes.
I then recharged and removed LP. I waited 6 minutes and found that it was still on. I am recharging and will try again after a longer period of time but it looks promising. I will let you know when I have more info.

Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.

pezx44 said:
Well, no dice. I checked after a half hour and it was off. I'm open to any other experiments though.
Click to expand...
Click to collapse
You have no complaints, my friend. A half hour of uptime is better than 6 minutes!
So, yours is a power-related issue and it looks like CKA is the answer. I wonder if Froyo will address this.

But it was only a half hour when I saw it was off. It could have been 6.5 minutes in.
I'm currently running Froyo (Cognition 8.1). This has been an issue for me since before that though. One thing I can't quite remember is if it happened before I unlocked my phone. Is yours unlocked? I needed to do this because I do not live in the US.

pezx44 said:
Is yours unlocked? I needed to do this because I do not live in the US.
Click to expand...
Click to collapse
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.

Jack45 said:
Unlocked, rooted, and stable (which is more than I can say for myself).
On a more serious note, when I first received my replacement I created the following settings to try to avoid the shutdowns until I was confident that the phone was o.k.
For your consideration:
1. Wi-Fi was always on and is set to never sleep. The "never sleep" settings can be accessed via the Wi-Fi settings page menu, Advanced tab at the bottom. Reason: I'm attempting to generate additional under-the-cover activity (plus I do use Wi-Fi). As I'm not a technician, this may be nonsense.
2. Power saving mode was not checked. Reason: "Don't do me any favors, Captivate. Your idea of power saving may get out of hand."
3. I never let the phone go into sleep mode on its own (that's still the case). Default is 30 minutes, but I always push the button to get it to sleep and get it to wake. Reason: Just in case the built-in sleep timer thinks that "sleep" and "coma" are synonymous.
You can try these three mods to see if they work for you. Remember to uninstall CKA for now to make the above a valid test.
Don't forget to write.
Click to expand...
Click to collapse
1. I have the same setting for wifi (I use my phone for SIP calls often).
2. I absolutely agree with you on this and it is also already my setting.
3. I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
I'll let you know how things go.
And just in case, by unlocked we are talking SIM unlocked right?

>>> I always turn off my screen too, but I will set it to 30 minutes to see if that makes a difference and test again without LP/CKA. I can't see how it would be related but I certainly don't mind trying it if for no other reason than to rule it out.
As the timeout for sleep mode is power-related, I wanted to take that out of the Captivate's hands. The on-off switch is OURS to deal with at will. Want the room light on? Turn it on. Etc. Basically, I wanted to generate persistent under-the-cover activity (WiFi) while eliminating decision making activity on the part of the device.
>>> And just in case, by unlocked we are talking SIM unlocked right?
I can place any non-AT&T SIM in the phone and it will work.

No LP issues here since I've owned the phone.
I've had LP on with full charge all the way down to 30% +/- and still ran like a champ.
Currently on Cognition beta 9 - still the same story.
I truly think you have a lemon phone. And I just flashed and haven't tweaked any of the default settings that are "out of the box" after a flash... so I assume they are all default.
The only FC/shutdown issues I've had recently were with Cognition beta 7 and advanced audio manager. I removed it and *poof* no more FC's. And since I was never that concerned with my sound settings (it's on vibrate 99% of the time anyways due to work environment and a lil' guy) I didn't care.
I'd look into getting a refurb - or flashing to Cognition's latest and greatest (hmm... well I would wait for 9.2 as he is having some "growing pains" with his new kernel) and see how it goes then. Can always Odin back to stock if needed.

Random reboot temporary fix?

So i've had random reboots starting on my phone recently and was thinking about ordering a replacement phone through LG here soon.
However, after speaking with a T-Mobile rep, they advised me that after hearing complaints about it, they've found (or heard of) a temporary fix for it, and it has seemed to stop MY random reboots too.
They're saying theres an issue with the software and the GPS crashing, a tmobile rep told me to just try and turn off the GPS option in the settings and, ONLY turn it on if its REALLY needed, and it should solve the reboot issue.
Now mind you my phone rebooted randomly about 2-3x a day. After following this very easy step, it no longer reboots AT all... and whenever i need GPS for anything, i just turn it on for those moments, then turn it back off.
( not sure if this has been mentioned before, but if it hasn't then give it a try, if it has then just hit the back button and continue on with your life )

Have tried that because I feel its probably partially GPS related too but I've had the phone reboot while GPS was off. I don't know if even using it for a bit seals your doom. What's weird though is I've never had a reboot while actually using the GPS including in Navigation for hours at a time. I think we just need a patch at this point.
javolin13 said:
So i've had random reboots starting on my phone recently and was thinking about ordering a replacement phone through LG here soon.
However, after speaking with a T-Mobile rep, they advised me that after hearing complaints about it, they've found (or heard of) a temporary fix for it, and it has seemed to stop MY random reboots too.
They're saying theres an issue with the software and the GPS crashing, a tmobile rep told me to just try and turn off the GPS option in the settings and, ONLY turn it on if its REALLY needed, and it should solve the reboot issue.
Now mind you my phone rebooted randomly about 2-3x a day. After following this very easy step, it no longer reboots AT all... and whenever i need GPS for anything, i just turn it on for those moments, then turn it back off.
( not sure if this has been mentioned before, but if it hasn't then give it a try, if it has then just hit the back button and continue on with your life )
Click to expand...
Click to collapse
Sent from my LG-P999 using XDA App

[q] major bugs in samsung droid charge

Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.

nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
I haven't experienced any of the problems you bring up.
Sent from my Gummy Charged GBE 2.0 using xda premium

1. Are you sure that you are not pressing the power button while in the camera application. Doing so will toggle the screen lock and appear to freeze the phone.
Sent from my SCH-I510 using Tapatalk

I haven't experienced any of those issues either.
As for number 4, I think that was a conscious design decision. I don't really like it either, but you can use Tasker or Locale to detect when you're in a call and change your timeout to whatever you want.

nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
Click to expand...
Click to collapse
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
Click to expand...
Click to collapse
Never had this issue on either phone.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
Click to expand...
Click to collapse
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
Click to expand...
Click to collapse
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Out of curiosity, are you on EE04?

I have not experienced any of these on the 3 months with my phone. It locked up maybe once on the camera but never more than that.

I've had none of these issues and furthermore I second the above thoughts regarding locking three camera and the status bar brightness.
Sent from my SCH-I510 using xda premium

Count me in the camp that says I havent seen any of those issues. As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
All the other issues you are seeing are unique.
Search these forums for them, if others have had the problem you will find someone asked about it.
If you do find them, I am sure that they will be very isolated.

I couldn't say about a totally stock phone as I flashed mine to gummy 1.9.1 on its very first boot, but I have never had a single problem with my phone.
I absolutely LOVE this thing, I have owned a TON of phones and IMHO this is hands down the best phone I've ever owned.
My boss bought a new Bionic last Friday and after playing with it for the day Friday I wouldn't swap my phone even for the Bionic (among other things, the screen SUCKS on the Bionic). My boss doesn't like it either, he is returning it tomorrow.
~John

Never experienced number 1,2 or 4. But I have experienced number 3. Only happens though every couple of weeks. Hardly ever basically. It is weird though. I have no idea why my brightness changes even with my auto brightness off. Still a great phone though.
Sent from my GummyCHARGED Charge using Tapatalk

kelmar13 said:
Have not experienced on my stock Charge nor on my rooted Charge. Just tried both to try to get this to happen.
Never had this issue on either phone.
When you have the auto brightness turned off you can push and hold the notification bar and slide your finger to the right or left to raise/lower brightness. Is it possible you are doing this?
The phone isn't supposed to be waken by shaking it. You can change the time-out timing through the settings. I've never hung up the phone via the power button so I can't even comment on that one.
Out of curiosity, are you on EE04?
Click to expand...
Click to collapse
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk

piizzadude said:
As far as the camera goes, the only issue is the substandard SD card that Sammy sends. You cannot record in HD because the card speed is too slow.
.
Click to expand...
Click to collapse
Mine must have come with a different card as I have had no problem recording in HD (I just tried it again to make sure)

ms0chez said:
Omg just read your post about the auto brightness. Never knew that. Thanks!
Sent from my GummyCHARGED Charge using Tapatalk
Click to expand...
Click to collapse
Lol, anytime!
It's a feature I don't think I could live without now.

I can honestly agree with ur first concern. My camera is wonky. I can take pics all day without flash enabled. But I turn on the flash and try to focus (tap to focus), and as soon as the pic is snapped, the screen goes black, causing me to do a battery pull. Happened to me on my former Charge, my current replacement Charge and my wife's Charge. Happened on stock unrooted, stock rooted, and with custom Roms on all firmware versions. And I can easily replicate it.
Sent from my SCH-I510 using XDA Premium App

Please use the Q&A Forum for questions Thanks
Moving to Q&A

nikchapman said:
Hi. I write for AOL News and am looking for some feedback on the droid charge. I've used two different phones so far and found several bugs that no one has apparently been focusing on:
1.The camera/camcorder will freeze the entire phone sporadically forcing the user to reboot the system. This occurs about 1 in every 8 times the camera is used. especially if it's on more than a minute or two.
2. Clicking the 'Message' Icon will open the browser or even 'settings'. Again, forcing reboot.
3. The 'brightness' automatically changes to 0 even when the 'auto' option isn't selected and the phone isn't outside.
4. This one constantly happens; when in phone mode, the screen will go dark after only about 10 seconds and nothing will bring it back except hitting the power button. I've been told you're supposed to be able to 'shake' the phone to awake it out of sleep mode but this is not the case. Additionally, if you've set the power button to end calls, the phone will sometimes end calls on the first push and sometimes not.
The phone could be a great device but it's obvious there are SERIOUS design flaws inherent in the OS.
Click to expand...
Click to collapse
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.

jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
I think the fact that he is a journalist with some very pointed questions is the dead giveaway for his agenda. He's looking for a sensationalist angle to play for an article. Whether it's against Verizon or Samsung, I don't know, but it's pretty certain he came here with an agenda.

jpolzner said:
Sounds like you have some sort of agenda. Seeing as how nobody here so far has experienced this issues your referring to, I would say nothing is "obvious" at this point, nor do any of the issues above seem to be "serious", save for maybe the camera lockup issue but that very well could be user ignorance.
Click to expand...
Click to collapse
Well put, I agree 100%
~John

never experienced those issues either..probably a android issue..
Sent from my Gummy Charged GBE 2.0 using XDA App

I've had my Charge for about three months. I ran bone stock EE4 for a few weeks and have been using the various iterations of Humble Roms ever since. I never encountered any of the 4 issues brought up by the OP.
As for HD recording, I recall posts mentioning that some phones shipped with class 2 and some with class 4 sd cards. I got a class 4 card in mine and I've never had an issue with recording HD. Likely the source of the recording issue.

[Bug Reports]

MODS : Please move to GENERAL SECTION. Thanks.
Hi, starting this thread to roll up on bugs reporting. Will compile all your reports, verify them and inform Samsung about it and hopeful for a fix.
Sent from my GT-P6200 using XDA App
1) Sleep of Death (two users)
2) Floating Dialer popped up without being asked for... (two user + myself)

sleep of death. Its rare for me but still annoying when it happens. Plus, sometimes when I have the browser set to quick menu when you drag from off screen for the toolbar. The right side will bring up the dial for a second and disappear. Other than that awesome tab!

I get randon reboots and shutdowns, at least one of each everyday, usually right after I first turn it on for the day. It also sometimes is a bugger to wake up, sleep of death? I thought it might be powersaver mode causing me problems but they persist after I turned it off.

kzoodroid said:
I get randon reboots and shutdowns, at least one of each everyday, usually right after I first turn it on for the day. It also sometimes is a bugger to wake up, sleep of death? I thought it might be powersaver mode causing me problems but they persist after I turned it off.
Click to expand...
Click to collapse
I do not have this issue at all.
Try to flash the original firmware and hard reset. Do not root or install apps. Run it for a couple of days and see the result.
But I do believe it can be related to the motherboard.
Example, my original P1000 tablet was superb, no hangs or SODs... but I bricked it (excessive tinkering) and Samsung changed the motherboard. Since then, I started to experience hangs and a few SODs... sold it off...

PandaHandz said:
sleep of death. Its rare for me but still annoying when it happens. Plus, sometimes when I have the browser set to quick menu when you drag from off screen for the toolbar. The right side will bring up the dial for a second and disappear. Other than that awesome tab!
Click to expand...
Click to collapse
happens a couple times a day to me.. I am getting tired of it for sure..

Not trying to be mean, but not development related. Should be just Q&A
Sent from my Insanity powered SGS2

I've been fortunate so far also but if I start to get SOD then I would root grab set cpu and raise your minimum to 400
Sent from my Nexus S using xda premium

sorry for not posting sooner, removed the Micro SD card and reinstalled everything, that was a week ago, not one single SOD or reboot.
Not sure what it means, but it could be looking for the SD to index or update files and not reading the card causing the reboot?
What do I know, it just could be luck, but worth a try.
Let me know how it works for you.

[Q] Touchscreen Issues

I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.

This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.

I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet

I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.

I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:

I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet

Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.

There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.

2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.

So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk