Database Info

[Q] An app that logs?? pls read.

Alright, I'm wondering if there's an app that will log most everything that happens on the phone. I have a captivate and have the random shutdown issue after a full charge and today I watched it very closely as it went to sleep and noticed something tried to pop-upabout a milisecond before darkness. Turned it back on and it did it again, but without a log I have no idea what it is, and it could possibly offer a solution. I myself am returning the phone for a new one as soon as they get them back in stock, but would like to try and help people that do not have that option while I can. Thanks!

Random shutdown solution!

Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App

Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app

I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.

Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.

Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.

Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App

Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App

. .

Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.

I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App

I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk

galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...

It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.

My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.

My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.

Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.

I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).

Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.

i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?

Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem

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 Reboots.. any new info?

Hi everyone.. I searched a bit but couldn't come up with any more answers so I'm wondering if I missed something.
I've had my TF since like May, and for as long as I've had it, I've had this issue.
No matter what kernel or Rom or anything, my TF always randomly reboots ONLY when my screen is shut off and the wireless is left on. It doesn't reboot if I'm using it, and the only way to make it not happen is to turn on airplane mode when I'm done with it.
Its not a big deal, but it is annoying, especially if I leave it in the living room and forget airplane mode. Then whoever is in there gets to watch my TV constantly and randomly reboot every few minutes.
Its just more annoying than anything. Id love to just keep wifi active so it automatically connects when I turn the screen on.
Other than this, my TF has been flawless for like 6 months
Thanks if anyone has any information!

I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?

avlon said:
I've suffered through the same issue with my 16gb TF. By any chance do you have your pattern lockscreen turned on? Can't quite remember where, but I read that having it stops the reboots.
I tried it on mine and haven't had one since...but it's only been a day or 2. Can anyone confirm if the lockscreen stops or limits the issue?
Click to expand...
Click to collapse
Wow, ill have to give this a try. I've never used the pattern lockscreen.

random reboots
I get this after about an hour of use. If I sitch it off via the button then when I press it again it reboots. If I just let th TF switch itself off (after 5 mins) it switches on normally when I press the start button.

I also had similar problems with my wife's TF, it rebooted randomly just about anytime (not just with screen off), apps crashing randomly. When I returned it to the store where I bought it, they immediately replaced it with a new one that doesn't suffer any of those problems.
If you have such problems, I'd recommend taking it back to the store for repair, because that is definitely not the expected behavior.

unfortunately the lock screen thing didn't work
Can't really take the thing back, I've had it for months.... fortunately this is the only issue I have... I can live with it. Its purely an annoyance that doesn't affect me when using it...

[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