How to debug unreponsive N7100? - Galaxy Note II Q&A, Help & Troubleshooting

Hello XDA world,
My note 2 has been having the occasional fit.
By fit, I mean the screen goes unresponsive, and the capacitive buttons might light up.
I have to hold the power button and reboot.
It is intermittent. One day it want totally crazy and after the reboot, it hung again before it even finished booting.
I've noticed if I try to do anything while it's booting up, it's even more likely to hang. It hung during 5 restarts in a row which almost drove me insane.
Then it totally stopped for days. Then the occasional hang. Then today it decided to go insane again and lock up 20 times in a row.
How the #($#@ do I debug this?
Some notes:
1) I don't see anything in logcats. I've tried various programs, and just doing a "logcat > logcat.out &" in terminal window.
I'm thinking my phone is hanging before it's able to flush the logcat output to memory.
2) It happens if I have no sdcard in the phone, so it's not that.
3) I'm now trying to uninstall programs that 'auto startup'. It's hard to tell if it works since it's intermittent. Hangs could be a week apart.
4) Is there any way to memory test the memory inside the phone? Once I was trying to copy the logcat off the phone via MTP and it hung. Could be coincidence.
5) There are signs of 'degrading death'.
a) I have 'show touches' in options turned on. At some point the screen isn't responding.
For example, if I'm at the lockscreen - I can see that it is registering my touches. (the option makes dots appear where you touched the screen). However the phone doesn't unlock (i.e. the thing that you click and drag to unlock doesn't appear').
I can still see processes running/not running (the 'show cpu usage' option.).
Or, if I'm at the launcher, I can touch the screen, home screens don't scroll.
b) After being in state 'a' for a while, the screen eventually goes black and that's that.
My phone is now in a 'totally refuse to work' state now, hanging after every reboot.
I'm trying to uninstall anything/everything - there's a program I'd ideally like to back up before I wipe.
- Frank

The widgets take forever to load after startup sometimes, which is usually precursor to a hang.

ChodTheWacko said:
The widgets take forever to load after startup sometimes, which is usually precursor to a hang.
Click to expand...
Click to collapse
Is your cpu temperature high when your problem encounter?
Sent from my GT-N7100 using xda app-developers app

SDS!

Related

TF3D launches at startup but have to tap screen to display home screen.

When I boot up after reset or power off, the homescreen displays top task bar, bottom soft keys, and displays "launching TouchFlo3D..." and then... nothing. The screen stays like this until I tap it, and then it displays the home screen. Anybody else seeing this?
Even when just switching it on from a while on standby, I get a black screen.
I press the home or start buttons, and the home screen comes on ...... when it feels like it
I have never got no one to answer a question on here good luck...
PaulusUK said:
Even when just switching it on from a while on standby, I get a black screen.
I press the home or start buttons, and the home screen comes on ...... when it feels like it
Click to expand...
Click to collapse
Does touching the screen make it start?
I know that not turning off TF3D before installing some cabs can make it behave oddly- TF3D restarts, fails to launch at boot, etc...
Mine does the same thing except its just a plain screen until I touch it then it says launching tflo
Might have something to do with locking the device with a PIN/password. Try to disable that and see if many of your problems go away (switching to home screen on coming out of sleep or turning the screen on when in call and taking the phone away from the ear etc).
acrh2 said:
Might have something to do with locking the device with a PIN/password. Try to disable that and see if many of your problems go away (switching to home screen on coming out of sleep or turning the screen on when in call and taking the phone away from the ear etc).
Click to expand...
Click to collapse
It has something to do with the PIN lock code, you're right.. now we just need someone to look into this further who knows how to troubleshoot these issues from the back-end.
Bump for more answers!
-mak
so i've tried checking on/off Today/Item/TF3D, tried Flight Mode, and it still won't work. i'm talking like only 30-50% of the time it does work. and I never had PIN1 enabled!
i'm no programmer but it is conflicting with apps we install because TF3D works perfectly when the phone was fresh or hard-resetted. btw i'm using 6.1 Stock T-mobile

Replicating 4.2.X "sod" and what it means..

As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app

[Q] Phone keeps shutting off by itself

The model of my phone is SGH-T999. It is not rooted (I'm going to root it soon though), its running Android 4.3 and I do admit I've dropped it a few times but it has a cover. It shuts off at the most random moment and restarts itself, and sometimes it won't go past the Galaxy SIII logo before restarting itself once more. Theres a possibility the lock button has something to do because when it stays in that startup loop I play around with the lock button till it finally finishes the startup succesfully, but I don't know how the lock button can make it shut down on its own while its turned on without me touching the "power off" option in the window that comes up.
Let's assume for a minute that the Power Button is not the culprit of the reboot. Its certainly possible that the button causes reboots during Boot. Several people have discovered, this button can get stuck.
So given that, let examine your Reboot. You may have to try a factory reset to see if that helps. Typically if there are a lot of background apps running, the phone may get warm and reboot.
Speaking of temperature, you may want to use some Battery Temp monitor like TempMonitor. Stock firmware tends to have low tolerance for temperature and may force Reboot.
Holdin the power button will force a hard reset btw. So if itz sticking that'll do it.
Sent from my SGH-T999 using Tapatalk

[Q] phone is stuck at splash screen/lock screen

Hello, I could really use some help with this..
I have a rooted Samsung Galaxy Nexus (Verizon) using an older version of SuperSU (think around like .98). I also
installed the free version of Titanium Backup to uninstall apps... And everything was going fine. I consulated with forums and app lists of the safe apps to uninstall. I kept uninstalling apps and everything was fine, but then I rebooted my phone one day and everything wasn't. The phone boots and the nexus X splash screen appears. I think it usually stays stuck there unless I press buttons, boot in safe mode, or charge it. So then it gets to the lock screen in some of these cases. The notification bar at the top works and the screen will flash on for about 5 seconds before it goes black. And this will keep happening usually. Sometimes just the area where the wallpaper is supposed to be will be black, not everything is - the notification bar, lock symbol, and time all appear as normal on the lock screen.
The touchscreen doesn't appear to take any input really, expect that you can slide the lock symbol to unlock the phone... Only thing is, it doesn't actually do anything like bring you to the home screen like it should. This could be much easier to fix, but I uninstalled about 3 or 4 apps before this happened and off the top of my head I don't remember what they were. If I wrote them down I not don't know where that went. I recall that I uninstalled at least one package that had the word google in it. I also do not recall if I uninstalled the one time init.apk. I have data on this phone so if anyone could give me a direction to recovering the data or something.
My overall technical expertise is decent, but I'm more of a newbie when it comes to smartphone hacking.
One more thing, I forget to mention that the phone doesn't turn off from holding down the power button. I either have to wait until it dies or take out the battery.
Have you had any luck with this. Mine phone is having the same problem.

P600 Black screen, but android still runs(?)

Okay, so here's the issue:
My P600 starts normally, but I end up with a black screen (not the regular one caused by the LCD cable being loose). Not really sure when it started, parents say it's been like this for a day now. All I see is:
-The top bar (with time, audio/vibrate setting, Wi-FI signal and battery)
-The drop down menu
-I can start S voice
-I can see all the apps I launch by pressing the icon in the drop down menu (by holding the middle button, as you normally do)
The screen reacts fully, I can roll up the drop down menu and shut down the apps by moving my finger across the screen.
It throws out the "Process system isn't responding" error every once in a while.
The lock screen flashes through very briefly when I go back from the "all launched apps" menu (not really sure how to call it).
Steps I tried:
Restart
Wipe cache partition
Connecting to a PC doesn't do anything
System(Android) is fully stock, and was probably updated (not sure what was the last update Samsung put out).
Factory reset(or flashing a new android) is the last thing I want to try, thanks.

Categories

Resources