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.

Anybody having reboots/freezes, have you tried this?

Don't ask why but try doing the following:
- Settings -> Sound -> Haptic Feedback. UNCHECK (turning it off)
- Settings -> Language and Keyboard -> Android Keyboard Settings -> Vibrate on KeyPress. UNCHECK (turning it off)
I've had good results since doing this without changing anything else, phone has been more stable and no random reboots or freezes yet. Theory is due to the custom driver/vibrator used in the LG G2X (per CM7 team) there's a memory leak or some bug that over time causes the phone to reboot/freeze.
Why I think this:
- A few times in the last few weeks it froze was when a notification came in (GMail, SMS, etc.) that would have caused the phone to vibrate but instead of doing so it just did the SOD. Know this because I have a XOOM with me (3G) and emails come to both XOOM and G2X same time
- If I leave everything on, after about 2-3 days of use the vibrations start getting wonky with some lasting longer than they should or just not doing it properly
- Had a similar issue with CM7 on my Verizon Incredible where vibration issues would eventually lead to a reboot/freeze
NO GUARANTEES THIS WORKS. But I wanted to share and get more feedback. Please make these changes and then restart so its fresh. You don't need to disable vibration alerts, just the haptic feedback and keyboard vibrate.
Please post your feedback. Thanks.

I dont have reboots and never have those on...I'm gonna turn em on and see what happens..

I just turned mine off as suggested... I am on my 2nd G2x and am experiencing reboot issues already. I will keep you posted after a couple days on the results.
Thanks for posting this potential fix.

Had these off ever since I got the phone, haptic feedback gets really annoying. Will put them on and see what I find

I have had those on and had no reboots.
Sent from my LG-P999 using XDA App

witeboy07 said:
I have had those on and had no reboots.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Might be related to hw. The vibrator in the phone is a piece of hw so maybe some versions have problems and some don't. I know while my Incredible had vibration problems on CM7 others didn't with same exact software.
I wanted to see more if people getting reboots benefitted at all from these or not. It you don't have reboots at all this post is irrelevant.

mobilehavoc said:
Might be related to hw. The vibrator in the phone is a piece of hw so maybe some versions have problems and some don't. I know while my Incredible had vibration problems on CM7 others didn't with same exact software.
I wanted to see more if people getting reboots benefitted at all from these or not. It you don't have reboots at all this post is irrelevant.
Click to expand...
Click to collapse
It might have more to do with the software. I've used the stock ROM, the leaked 2.3.3, and Cyanogenmod, and all three use different vibration models. The 2.3.3 was particularly bad, CM7 is probably the best.

Bought my G2x on the 9th( So, hello! I'm new ) and everything was great until... yesterday actually. Had a bootloop and had to factory reset, then it locked up later. Then today it locked up and I pulled the battery and just now it didn't come on when I tried to unlock it.
So... I'm trying this. Hopefully it works. D:
If not, I'm gonna have to get a replacement or something. I'll be back with a follow up, some time.

For those of you who try this, please update here after a day or two. I am likely to let T-Mobile switch my phone out to a Sensation today so I may not have a G2x to play with any more. I really like it and if there is a simple fix I'd be willing to give it another go.

Trying it now
I haven't had it reboot on me since I did a factory reset last week...
I'm going to turn off the vibrate settings as described in the first post. I'll come back in a few days to respond if I've had any reboots, freezes, etc.
EDIT: I'm also going to reboot after changing these settings just to make sure they "stick" and the phone is "fresh".

Day 1, no freezes.
I charged the phone and it didn't freeze either...
It's Day 2 now and I'll let you know how this goes down as well.

I haven't had either of these options checked since I first got the phone. I have a reboot approx every 1-2 days and a freeze every 3rd time.

Another strange thing
It's been over a day and a half after I've turned off the haptic feedback settings described by OP and no reboots or freezes yet. Even while using wifi calling and heavy camera use and very heavy picture uploading directly from phone to picasaweb.
Something else strange that happened to me before that could be related to the vibrate software/hardware is when some one called me it would vibrate and ring like normal but after sliding the green arrow over to answer it stopped ringing, answered the call just fine, but the whole time while talking the motor continued to vibrate in the two pulse way it normally does! Has anyone else had this happen!?

harleyxlc said:
I haven't had either of these options checked since I first got the phone. I have a reboot approx every 1-2 days and a freeze every 3rd time.
Click to expand...
Click to collapse
Try wiping your dalvik cache as I've posted in a separate thread.

worked for me. 2 days no problems

day/charge 2 and 3... everything is going well.

Random turn-offs/reboots FRUSTRATION!

This tablet is a great piece of tech, however I've had two major problems with it. AMOLED screen burn-in and random reboots/shut-downs.
In the past week it's at least turned itself off or rebooted itself 9 times. Is anyone receiving this problem? Also in the past 3 hours or so, it's been rebooting to the Samsung Galaxy Tab 7.7 screen just before the tab turns on and gets stuck there. I managed to get out of that situation but I'm not sure how.
If you have problems list which version of the tablet you have, your firmware or kernel version and your specific problem.
Hopefully we can get Samsung's attention if theres enough people and have this patched with an update. Or maybe it'll all go away with ICS... just being optimistic lol.
If anyone knows any sort of customer service or someone from Samsung I can email about this problem that'd be appreciated.
Details:
GT-P6810
32GB WIFI Only
2.6.36 P6810DTKL5 Rooted.

I don't have the problem but if I can maybe suggest, have you reset the device back into factory setting?

Your not the first one to ask this nor your alone, this also happens with the Galaxy Note with some users, I've never been able to pinpoint the cause for this on the note.. I'll see if it happens on my Tab7.7 when I get it tomorrow.

Do you by any chance have a sim card inserted? I noticed yesterday as I was working with AT&T to get my device set up that each time I had to take my sim card out (to give them the serial number) the Tab would reboot on its own.

I have had 2 reboots since getting my tab, very weird.
Sent from my GT-P6800 using xda premium

We need more people to chime in and see how wide spread this issue is, it could be cause by a very aggressive deep sleep state that is used by samsung?

torakun said:
I don't have the problem but if I can maybe suggest, have you reset the device back into factory setting?
Click to expand...
Click to collapse
I thought that factory resetting it would help but as far as I can tell it hasn't. I tried that about a week ago but am willing to give it another shot if someone proves me wrong. Thanks for the input though.
lulugirl896 said:
Do you by any chance have a sim card inserted? I noticed yesterday as I was working with AT&T to get my device set up that each time I had to take my sim card out (to give them the serial number) the Tab would reboot on its own.
Click to expand...
Click to collapse
I have the wifi version so I don't have a sim slot. Sorry for not being more specific in the opening. Although I remember someone else mentioning that their sim may have been the problem. Thanks anyway.
EarlZ said:
Your not the first one to ask this nor your alone, this also happens with the Galaxy Note with some users, I've never been able to pinpoint the cause for this on the note.. I'll see if it happens on my Tab7.7 when I get it tomorrow.
Click to expand...
Click to collapse
Maybe something with the processor, they're relatively similar aren't they? Anyway hopefully I didn't discourage you from your tab, it's still one of the best pieces of tech. Lets hope this problem isn't that widespread and if it is lets hope for a patch or something, maybe with the ICS update hehe.

Have had my GT-P6800 for about a month and I have had several random reboots -- since the reboot is complete and I end up where I was I cannot determine what's behind it.

Haven't had reboots, but I've ran into issues with it turning itself off at least once a week. Currently on LA2 firmware.

I had about 4-5 reboots in a week . don't remember details .

Is everyone using 3G card that are having reboots? I did NOT have any reboots until getting a 3G card this weekend. It JUST did it. Also, I notice if it's on charger (not USB) that when it's full it will more likely reboot. That's my $.02.

My 7.7 p6800 has not exhibited any reboot. I am on KL1..but it has prompted me to update...
Please post
7.7 model wifi or 3g
Baseband Version
reboot yes or no
Sent from my SAMSUNG-SGH-I717

I just got my Tab7.7 but I do not have a spare simcard yet to test if its causing the issue but I will update this post for any findings
P6800
16GB 3G+WIFI
DXLA2 - Kernel Build Date Jan 2012
1 Sleep of death so far, watched a movie but locked the device to take a phone call from another phone. Had it in flight mode but wifi enabled.. so thats about 24hrs from initial power up.. I also performed a factory reset before using the Tab.

copualt3 said:
My 7.7 p6800 has not exhibited any reboot. I am on KL1..but it has prompted me to update...
Please post
7.7 model wifi or 3g
Baseband Version
reboot yes or no
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
yep, my tab prompted me to update as well, I it yes, it downloaded something over wifi, then it rebooted, then it goes to recovery and installed the new stuffs, then said "failed" lol
I only have one crash that is when I used the cam then hurriedly hit back several times, then it froze and rebooted, that's the only time it did it

I've structured the OP a bit better hopefully. I've provided my details and asked people for theirs.
Going to go look for who to complain to now lol.

No reboots yet but I did see it wake up to the lock screen while it was sitting on my desk, I have it in flight mode if it matters. It was actually spooky..

Ok I just had the sleep of death on my Tab7.7
Airplane mode but wifi is enabled, the last thing that I was doing was watching a movie and locked the tablet to take a phone call on my other phone. No SIMcard inserted only a 32GB microSD card.

Hi all.
Got my tab 7.7 3G about 3 weeks ago. Rooted on day 2 (this is my 4th droid so pretty confident doing so.... but...) using the simple root method posted somewhere here in XDA.
Not sure if this is related to the rooting, but I've had about 6-8 reboots, several shutdowns and one really strange rebooting which led to the tab unresponsive to anything (only showed the samsung name logo). I was about to factory reset again (I did about a week ago but only because I forgot to reboot after I rooted) when the tab suddenly woke up and started booting normally.
Normally until apps started loading and for almost all the apps, errors of some kind started popping up.
Since I had control again, I factory-resetted the tab.
Since then, I've had no reboots or shutdowns. I do not know why.
Other strange quirks - sometimes, when waking the device with a quick push of the power switch, the screen does this strange graphic swirly thing (almost seems like a graphic image gone mad while loading) and then loads the proper graphic/lock screen.
Sometimes too, when changing orientation, the graphic seems to lag behind the action. Not all the time though. I use Go Launcher as my default but I've noticed the TW screen do the same thing when I change orientation.
As far as Go launcher is concerned (I use it as well on my GS2), only the dock seems to have a problem - when flicking from one dock to another, the next dock does not 'center'.
So far I am a bit disappointed and hoping (hugely) that ICS releases this tab to its dual core, SAmoled glory.
Edit - if I were to say which was the biggest disappointment, that would be the media rescan. When I have a new photo or image, the image does not appear right away in Gallery. When I try to use the music player, the player will not load (rescanning) but the image appears in gallery after.

wujae said:
Hi all.
Got my tab 7.7 3G about 3 weeks ago. Rooted on day 2 (this is my 4th droid so pretty confident doing so.... but...) using the simple root method posted somewhere here in XDA.
Not sure if this is related to the rooting, but I've had about 6-8 reboots, several shutdowns and one really strange rebooting which led to the tab unresponsive to anything (only showed the samsung name logo). I was about to factory reset again (I did about a week ago but only because I forgot to reboot after I rooted) when the tab suddenly woke up and started booting normally.
Normally until apps started loading and for almost all the apps, errors of some kind started popping up.
Since I had control again, I factory-resetted the tab.
Since then, I've had no reboots or shutdowns. I do not know why.
Other strange quirks - sometimes, when waking the device with a quick push of the power switch, the screen does this strange graphic swirly thing (almost seems like a graphic image gone mad while loading) and then loads the proper graphic/lock screen.
Sometimes too, when changing orientation, the graphic seems to lag behind the action. Not all the time though. I use Go Launcher as my default but I've noticed the TW screen do the same thing when I change orientation.
As far as Go launcher is concerned (I use it as well on my GS2), only the dock seems to have a problem - when flicking from one dock to another, the next dock does not 'center'.
So far I am a bit disappointed and hoping (hugely) that ICS releases this tab to its dual core, SAmoled glory.
Edit - if I were to say which was the biggest disappointment, that would be the media rescan. When I have a new photo or image, the image does not appear right away in Gallery. When I try to use the music player, the player will not load (rescanning) but the image appears in gallery after.
Click to expand...
Click to collapse
Hm, mines rooted too. I wonder if that affects how often you get a reboot/shut-down? Still, it better get fixed with an update.
Btw, don't use this tablet as an alarm. I woke up half an hour late to find that the tab was off. I turned it on and the battery was at 60% so it definitely wasn't the battery running out. Maaan was I late for school lol.

tab 7.7
I have the same problem especially when watching the movie or downing torrents after the screen shutdown especially when the battery over 50%. when I want to switch on the screen, the tab will not response until long press on power button switch on with galaxy tab 7.7 screen. that means it was shut off !

Is there a ghost in my phone?[CASE SOLVED]

OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?

..

Sent from my sending thing.

I had the same problem. LG Service Center said, that they need to change the touchscreen. Try to flash another ROM, if you get the same problem, then unroot and flash stock firmware and go to LG Service Center or change the screen yourself
But I hope it's your ROM, good luck!

on my sgs i have this weird ghost while charging.. are you running ics?

sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
this one was the best query I have ever read tania hope u are not watching fear files these days

sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
It is surely a hardware problem i had the same problem. My screen had got damaged as it wud get wet regularly. I changed the touch screen and it is now as good as new
Running Ginger Snap v1.3 Best gaming rom ever

A developer told me that sometimes on some devices, it happens while charging, becaude of charger errors..

sweettaniyaa said:
OK now I know there isn't a Ghost in my phone but at times my phone behaves like its possessed. The problem is with the touch screen. At times my phones starts to do stuff on its own. Like open random apps, bring down the notification bar and then brings it back up. Once it even opened my whatsapp and then opened the keyboard and typed a message and sent it to an contact. And during this time it doesn't really respond to my touches. But it happens very rarely like ones in two days and that too for a min or two. Been happening for a two weeks now. I have the latest CM 7 Nightly installed. So what do u reckon is happening? Is it a software bug or an Hardware bug? And how do I fix it?
Click to expand...
Click to collapse
Change your kernel, these may be kernel panicks.
Sent from my LG-P500 using xda app-developers app

myawan said:
Change your kernel, these may be kernel panicks.
Click to expand...
Click to collapse
This could be a reason cause it all began when I flashed DJNoXD's Kernel 2.5.2. But then I re flashed the latest CM 7 nightly over it and it continued to show the symptom's. Also I did not over clock, never did.
Today when it showed the same possessed behavior, I pressed the power button and it at once came back to my control. So I guess its a temporary solution to it.
dafabsl said:
A developer told me that sometimes on some devices, it happens while charging, becaude of charger errors..
Click to expand...
Click to collapse
It never happened during charging.

Found the Culprit
It was being caused by a pair of external speakers, which has it own power source, which I connected to the phone. I am guessing the speaker was sending some kind of charge to the phone. When I connected the speaker, the touchscreen completely stopped working. and even after I disconnected the speaker the touchscreen would continue to behave the way I described in my first post. Probably stored that charge somewhere. Bottom line, now that I have stopped connecting the speakers its stopped that behavior. There case solved. Feel like Scooby Doo. There was no Ghost after all.

Lolzz..

[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