Database Users

Slider unlock sometimes doesn't work with incoming call

Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?

Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.

I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?

question... are the phones plugged in to a wall charger when this happens?

Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).

DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place

ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).

cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there

My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers

I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.

Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.

problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel

Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App

swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago

I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?

[Q] Unique Nexus One power up issue

Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?

chota_shivaji said:
Hi Moderators,
Please feel to delete or move this thread, if you find it repetitive. Apologies for starting a new thread.
Hi All,
I have a unique issue with my Nexus one. Sometimes it fails to reboot and then does not start even pressing power button multiple times. Sometimes it starts but then screen does not come up after the display time expires. Whenever it is ON, power button works good, ALWAYS. When it goes into the weird state, I am not able to put it in recovery mode as well. Whenever, I am able to put it in recovery mode, power button ALWYAS works good. Also I have seen that sometimes, even after boot-up it is not able to detect the SD card even when battery is at around 30%.
I have tried all the methods I could find related to "Nexus One power issue" here on XDA as well as via Google search. Sometimes the "remove battery multiple times while plugged into AC" works but at times it also does not help either.
I visited the local HTC service station. The guy there showed me that the small strip of Litmus paper on battery and phone has turned reddish. For normal phone it should be white. This indicates that phone was in contact with something acidic in nature. I tried swapping batteries with my friends and colleagues, but no luck. I have replaced the power button strip of my phone which seems to be trouble some as per the discussions here.
I have tried CM7.x, RCADS, MM super hybrid, eVil's desire port and of course stock 2.3.x ROMs. All seem to have similar issue one or another time. I have also tried Amon_RA's 2.2.0 and 2.2.1. Somebody told me to try with CM6.1 which I will try now if I am able to boot it in recovery.
My warranty is long gone, BTW. Also I bought my phone from US and it is not possible for me to go there again in near future. This issue cropped up approximately 3/4 weeks back. I have default radio.
Having said that, does anybody know what could be the issue with my phone? Has anyone faced such an issue?
Click to expand...
Click to collapse
Hi Moderators,
Apologies for posting this thread in this sub-forum. I forgot that question threads should be in Q&A section. Having said that, if its not too much to ask, can you please move this thread to Nexus One's Q&A sub-forum?

Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware...
Sent from my GT-S5830 using XDA Premium App

Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
shreyasvb said:
Just update d firmware wit any of the ones which r available here...m pretty sure this ll solve yor issue as I think its related to software not hardware..
Sent from my GT-S5830 using XDA Premium App
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App

b1337 said:
Firmware update lol seriously ...try updating your radio to the 5.08 or 5.12 then flashing a stock rom and go from there
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.

chota_shivaji said:
Thanks a lot for your suggestions. I somehow manage to put my Nexus one in recovery mode by pressing power + volume down buttons multiple times. Then flashed the radio 5.08 on it. I already have CM 7.x ROM.
With this combination, my phone is working good so far. The power down issue would have reoccured by now. So it looks like my issue is resolved. I will use it for 24 more hours and come back if I am able to hit the power down issue again.
Once again thanks for the suggestions. As usual, XDA rocks. Had been experiencing this since good old Windows Mobile + HTC Touch days :-D.
Click to expand...
Click to collapse
I tested my Nexus one for past approx ~36 hours. In this time, I was hit by the issue mentioned in this thread twice.
Out of those 2, 1 was probably caused due to a soft reboot as I was able to get some output from cat /proc/last_kmsg but could not save it for sharing. The other one did not had last_kmsg entry so I am not sure what caused the phone to go haywire. The battery charge was ~30% when I booted it next time.
Now, I am on CM 7.x stable + 5.08 radio + Amon_Ra' 2.0.0 recovery and I explicitly have wiped the cache and Dalvik-cache via recovery. Since then, phone seems to be working OK. I will keep this thread updated if I am again able to get into the "Not able to power-on with power button" issue.

[Q] Help! auto/random reboot and stuck

Hi dude?!! I dont know if you ever experiences random reboot.
I got my phone not responding (when touch power or menu button) and i could see the Samsung logo hazy. But always resolve by reboot (hold the power button for 8 seconds)
I didnt root or apply lag fix. Is this probably cause by certain app ??? i use some of optimizer or tweaking app.
Usually this happen when i didnt touch my phone over 2 hours. This is very annoying to me. How could i resolve this problems. Does anyone know? please share!!!

Me too
Hello, I have the same issue.
My phone is rooted and i'm using the rom: I9003XXKB1 from Movistar ( spanish operator ).
Compilation number: FROYO.BGKB3
Kernel: 2.6.32.9
The phone freezes randomly and i need to force a reboot holding the power button.
Sometimes it directly reboots alone.
Greetings.

The phone freezes randomly and i need to force a reboot holding the power button.
Click to expand...
Click to collapse
Funny ****, got the same issue on my i9000 on 2.3.4 JVP with CF-Root... also had it on Froyo 2.2.1... this sucks big time, any input or hints appreciated.

Try a new fw first and post the results. Dont add anything else then observe. If all else fails, take it to where you bought it from and get a new 1.
Sent from my GT-I9003 using XDA App

konx777 said:
Hi dude?!! I dont know if you ever experiences random reboot.
I got my phone not responding (when touch power or menu button) and i could see the Samsung logo hazy. But always resolve by reboot (hold the power button for 8 seconds)
I didnt root or apply lag fix. Is this probably cause by certain app ??? i use some of optimizer or tweaking app.
Usually this happen when i didnt touch my phone over 2 hours. This is very annoying to me. How could i resolve this problems. Does anyone know? please share!!!
Click to expand...
Click to collapse
I occasionally have a random reboot as well though I haven't had any again after disabling the live wallpaper i had running from GO Weather.
Mine is a GT-9000 / 2.3.3 stock /I9000XXJVO/GINGERBREAD.XWJVH/ stock kernel at the moment
Didn't have the reboots/freezes before the last standard KIES update though.
You said "i use some of optimizer or tweaking app."
I'd say start by disabling/uninstalling all stuff that you don't really need.
Check if there are apps configured to run in the background and disable those as well

eriamel said:
I'd say start by disabling/uninstalling all stuff that you don't really need.
Check if there are apps configured to run in the background and disable those as well
Click to expand...
Click to collapse
I ever think that maybe cause by bad memory management in Froyo, thats why i use that kind of tools.
But, i'll try to get rid of it, and lets see.
*Sent from my GT-I9003 using XDA App*

Everybody seem concern to latest Gingerbread that actualy still trial ROM
Buts every feedback really needed for I9003 sake.
I have upgrade to 2.3.4 and getting worst after 10min idle. But with some trick from this forum getting better and now still evaluate.

Try this
Select all animations from display menu
go to Settings>Display>Animations>All animations

utkarshshrivastava1 said:
Select all animations from display menu
go to Settings>Display>Animations>All animations
Click to expand...
Click to collapse
Hi utkarshshrivastava, i did it. But still no hope
is it related to battery calibration or something like that ???
Now, iam back to xxkb3 an experienced with this reboot issue again
just rooted and use some apps like TitaniumBackup, Go Launcher Ex, Go Weather.
hmm...just dunno how to figure this out, not only with latona, the other device in other brand also experienced it.

Could be a brick, Could be hardware...

A Little History: :silly:
I have been running i9220ZCLP1...known bad kernel since whenever it was first available, April I think. Anyways, acquired that through flashing Rocketrom v5, according to the instructions provided at the time. Everything worked fine, other than contacts crashing and the wlan some times not enabling until reboot...common issues, as far as I've seen on these forums. One thing to note, is that unless the instructions at the time asked for a full wipe after flashing 5 (I'm almost certain they did not), then there has not been a full wipe performed while in this kernel.
The current issue:
The other day my phone froze on me...months after flashing and having used this kernel, waiting for something more solid to come out. After it froze...holding the power button turned it off, but the phone would not boot afterwards...to ics, to recovery, to download mode, nothing.
After some fiddling, I realized that it will charge and once it buzzes and the screen comes on showing a full battery, I can turn the phone on and it will boot...then freeze after getting past unlock screen. Or freeze and go black in download mode...didn't try recovery, wasn't interested in it at the time, but I'd imagine the same.
After removing the battery for a few days, then plugging it in til full charge notification, I was able to get it to boot again, where it froze at the boot screen, but went dark. After one more full charge...oddly, like a minute later, it booted to ICS fine and worked for 24 hours or so.
Now:
With a mind to flashing away from the bad kernel, I restarted the phone tonight from the menu in ics... it booted fine, so I left it plugged in to get a full charge and came back to a phone, screen still on, that shows same battery % as when I left it. And I'm back to where I started with this problem, powered off after holding power button a few seconds and now nothing.
Waiting for a full charge again, to see what happens...I'm guessing/hoping I'll be able to get it to boot again, with some more fiddling...
My question is whether this sounds like it's hardware (battery etc) or software (bad kernel etc) that is causing the problem.
If I can get it into download mode...plugged in, obviously, should I try OdinPC to a safe kernel?
Thoughts would be awesome. :fingers-crossed:

How about flashing stock GB via pc odin first and getting safe?

apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Sent from my GT-N7000 using xda premium

apurvapatel said:
How about flashing stock GB via pc odin first and getting safe?
Click to expand...
Click to collapse
OK, that's one vote for flash if I can get it running again. Thx, glad you read my post.

SpyderTracks said:
+1 I've read a few people on ICS having charging/battery related issues over time. Worth seeing if it still happens on a gb kernel.
Click to expand...
Click to collapse
Hmm, but how to get there...GB and all.
So now the vote is software. Any idea why this would happen much much later? No battery issues at all, just suddenly.
Maybe I'll buy a battery.

nebreprah said:
Hmm, but how to get there...GB and all.
Click to expand...
Click to collapse
A little searching would show you DrKentan's guide @ http://forum.xda-developers.com/showthread.php?t=1424997

[GUIDE]Jelly Bean on 8013

I have put this all together on the uk release and put it out as a rom here:
http://forum.xda-developers.com/showthread.php?p=34971303#post34971303
So here is a thread to talk about getting the German release of Jelly Bean on the 8013 and the 8010
I cross referenced the way that pimpmaneaton did his redemption rom, being able to work on the 8013 and 8000 with the aroma installer, checked what was different between the two for ICS.
With the build.prop, it was mostly just some changes to from 8000 to 8013 in the naming of things, but there were also a couple things coded out to get it better on the 8013
We have been looking into the dialer commands to see if any will disable the radio, more on post 11 for that testing.
I have had success with no reboots as well as removing the pesky no signal icon. I have included a flashable zip file that will take care of the build.prop, delete the files we know are not needed, disable the telephone by replacing the framework-res, adding in darkman-rs circle 1% battery mod, removing the null signal and airplane mode icons by replacing the systemui.apk
Step one: Download a jelly bean rom
I have been using darkman_rs version of the JB since it is stock and works nicely, also he has a lot of other nice stuff for it like a circle battery mod I like, and the telephony disabler.
Here is a link to his rom http://forum.xda-developers.com/showthread.php?t=1909950
***
Flash rom, clear cache/dalvik
Reboot, login/setup/etc until you reach a fully installed state.
Then reboot to recovery and install the fix zip.
Set cpu to ondemand
***
fix zip for 8013:
https://www.dropbox.com/s/xkb3spitb5vhlas/Complete_jb80xx_v2.zip
fix zip for 8010:
http://db.tt/tNMC0ZAv
The only difference between the two is the device name in the build.prop
-------------------------------------------------
Other fun stuff:
Adding in the 4 way reboot
I got this from Team Unions ROM here http://forum.xda-developers.com/showthread.php?t=1995700
It is a great rom and all the stuff here should work for that rom as well
https://www.dropbox.com/s/v97fqjyuvjkx7f2/reboot2.zip
there are a lot of nice tweaks from pimp my rom
here http://www.xda-developers.com/android/pimp-my-rom-install-tweaks-on-any-android-device/
Set your governor to ondemand has gotten a lot of good reports for stopping the reboots. This can be done with several tools from the market, I use rom toolbox pro, others use setcpu.
This was posted by darksabre_x
Here's SetCPU. It's been released free for XDA members. Donate when you are able.
http://forum.xda-developers.com/showthread.php?t=505419
Also check out this thread for more multiwindow apps and how to add more!!
http://forum.xda-developers.com/showthread.php?t=1985240
Super cool!!
I found this, some more information on the Pegasusq Governor
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
I removed the non flashable zips because a lot of people were getting confused, all the same stuff is in the fix zips above and will be easier to update if need be.
If there are any more things, add them, lets see if we can get this up and running perfectly before samsung does!
Thanks to everyone here for working together to get this running on the 8013!

what do you think is causes the reboots?

TramainM said:
what do you think is causes the reboots?
Click to expand...
Click to collapse
In my experiences as well as what others have had, it only reboots when it is idle, so it would be an issue with the sleep mode of something, maybe when it tries to go to sleep, something tries to tell the radios to do something different and it doesn't like it to it reboots.
I am going to try getting my csc changed to germanys to see what that does.

smaw51 said:
In my experiences as well as what others have had, it only reboots when it is idle, so it would be an issue with the sleep mode of something, maybe when it tries to go to sleep, something tries to tell the radios to do something different and it doesn't like it to it reboots.
I am going to try getting my csc changed to germanys to see what that does.
Click to expand...
Click to collapse
Sounds like a Dormancy thing, how could one get rid of that?
EDIT: How come airplane mode doesn't help, and the shutdown while charging? I mean I can keep my screen on all day and while its charging but won't that damage it

TramainM said:
Sounds like a Dormancy thing, how could one get rid of that?
EDIT: How come airplane mode doesn't help, and the shutdown while charging? I mean I can keep my screen on all day and while its charging but won't that damage it
Click to expand...
Click to collapse
Yes, I would imagine that would cause damage to a few things. There is a screen dimmer that keeps the screen *on* but has it dimmed to it appears to be off. I don't know what kind of long term effects it would have on the screen would be, because it is still on and has a slight glow to it.
http://www.xda-developers.com/andro...-screen-with-screen-standby-xda-developer-tv/
It is used for things like hooking up to your tv or computer to run things without having the screen on as well. I don't know if that will work or not.
I didn't have any luck changing my csc stuff, but I did have luck with ROM tool box finally freezing apps I wanted to, so well see how that plays out.

Cheers Smaw51 used your buldprop and systemUI giving it another go hopefully the reboot will stop anyway thanks

Try this in the Dialer ##4636*##

TramainM said:
Try this in the Dialer ##4636*##
Click to expand...
Click to collapse
where did you find this? Hopefully it works, my note is on the charger right now, I'll go check on it in a few minuets to see if it is still on.

smaw51 said:
where did you find this? Hopefully it works, my note is on the charger right now, I'll go check on it in a few minuets to see if it is still on.
Click to expand...
Click to collapse
Friend who dev'd for HTC amaze gave it to me completely turns off the radio

TramainM said:
Friend who dev'd for HTC amaze gave it to me completely turns off the radio
Click to expand...
Click to collapse
How do you know if it works or not? I am still getting power off during charge. After code was put in, it just wiped clean the dialer. Other codes I found I tested on my phone and tablet for various things all brought up a different screen thing.

Here are some codes I found here http://forum.xda-developers.com/showthread.php?t=1894102
*#197328640# Service Mode
*#7353# Self Test (Menu of 12 tests to use)
*#12580*369# --- Main Version (AP, CP, CSC, RF cal, HW Rev)
*#0*# another test
*#0011# service mode
*#0283# --- Loopback Test
*#232338# --- WlanMacAddress (Enable/Disable WiFi Powersave Mode)
*#197328640# --- Service Mode (Debugging, Testing. Use menu > back to go back in menus)
These look more promising:
*#7284# --- Phone Utility (USB Settings) I set both to PDA, didnt really seem to fix anything
*#9900# sysdump, has a few different things you can get for diagnosis stuff

Ill contact him to see if I can get the right one

It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2

pimpmaneaton said:
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I believe it is kernel related, but the problem is we did not have the 4.1 kernel source code

pimpmaneaton said:
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was thinking it was Kernel Panics when it tried to sleep.

What's odd (in my experience with both JellyNote and the German JB) is that it doesn't happen at a specific period after the device goes idle. Once it happened 2-3 minutes later, other times my Note sat there running fine for an hour or more before suddenly rebooting. I tried both using the ROM as normal, as well as once doing a complete wipe and re-install (of JellyNote) and not installing any additional software or tweaking settings beyond the startup wizard. Didn't seem to matter, I still got reboots at random intervals while idle.
It'd be nice if Samsung rolls out an N801X rom next.

TramainM said:
I was thinking it was Kernel Panics when it tried to sleep.
Click to expand...
Click to collapse
In the v6 supercharger script there is an option to stop kernel panics and keep it from rebooting. Maybe this is the solution.
Sent from my GT-N8013 using Tapatalk 2

Have you tried it?
Sent from my Galaxy Nexus using xda app-developers app

I have put this version of Jelly Bean on my N8010.
To start with I had a couple of reboots when the tab was idle. What I have subsequently done is:
Frozen com.sec.phone 1.0
Frozen Phone 4.1.1 - N8000XXBLJ9
In settings turned Blocking Mode on
I used Titanium Backup to freeze the programs. So far after a reboot I have not had any further reboots on idle - touch wood
Ok, I am not totally sure which of my changes or combination thereof has done the trick. Am afraid I am too impatient to use the new Jelly Bean to determine absolutely.
What I will say from my experience so far is the the tab is much faster than on ICS and stable for me to use all the time. So this seems a very good temporary solution until the offical N8010/N8013 roms come along.

Using Ondemand governor in a N8010 an the moment no reboots...it seems that the problem is the pegasusq governor