I've had this happen once before, on stock though. The phone is in my pocket and I take it out only to notice the device had factory reset, but I didn't ask it to. This happened a few years ago, even before I rooted and happened again a few days ago, but now I'm on a custom AOSP ROM. Has anyone else experienced this before? I called Verizon the first time it happened and all they came up with was pressing certain combination of the physical buttons while it was in my pocket, something I don't really believe.
Related
So I'm a stickler for stability and it drives me nuts (we all have our weird problems ) when things don't run stably.
i.e. I take very good care of my Windows XP PC, it's been running for 12 weeks straight now without needing a reboot, power down, nothing. Rock solid. I love it.
I'm running the Cing 8125 with the new QTEK AKU2 ROM. It's been running pretty well but I'm having the same problem I had witht he original Cingular ROM.
For whatever strange reason and ONLY when I'm not using the 8125, it seems it will soft reset which makes it impossible to pinpoint the cause. I know it has soft-reset because
a) My memory is back at like 23MB free which is what I have after soft-reset.
b) None of my apps are running anymore - duh!
c) Best of all, I have a today plug-in that keeps track of uptime so I know EXACTLY when the soft-reset happened.
I can't understand what would trigger it, when I'm actually using it, the device is fast and solid. I'm not running any crazy apps that I would think could lead to this unstability.
How long have you gone without a soft-reset? What's bizzare is the most recent soft reset happened this morning at exactly 1:00AM!!!! What are the odds of a random reset happening exactly at 1AM? No, I don't have any notifications, alarms or anything around that time.
Here's the uptime meter I'm using if you want to try it out:
http://www.freewareppc.com/utilities/uptimemeter.shtml
I wish it would soft-reset when I was using it so I could at least know what was causing it.
The same is happening to me, although it soft resets once every 2 weeks or so. I must say I turn off the device every night, but it has happened to me 3 o 4 times since I installed de Qtek AKU2 ROM.
Any solution?
I mentioned this once before on here. I catch mine doing it at night sometimes (in the day its usually in my pocket so I don't know if it does it there).
I've only seen it a few times, maybe once every 2 weeks.
The odd thing is, that when restarting after it's random soft reset, it doesn't require me to enter my pin code. It's almost as if it knows that it's been naughty and was hoping I wouldn't notice
Maybe it's a "feature" of WM5?? :roll:
Saw some older posts on other forums regarding issues with WM6 changing the password after power loss, but nothing here, so I'm posting to see if anyone's had this issue.
I'm running ITsPapaBlackDiamond, latest version for the Wing, only set it up a couple of days ago. I know that I can get around the password with a hard reset, that'll kill all the data on the device. Luckily, I've got a backup from then (prior to installing all the extra software I like, but that's life I guess).
Has anyone had this problem? Seems like last night my Wing's battery lost it's power, and the device shut down. This morning, when I went to login using my password (and I'm 1000% it was correct, if not the first time I entered it the second and third time for sure), it said my password was incorrect.
Has anyone else had this issue? Is there any way to get around having to hard reset, restore my backup, and lose whatever messages I got the past few days?
Hey guys, im on my pc, and im literally watching my phone press the return button really quickly, constantly for a few seconds at a time. I know theres a topic about the back button but im not sure if its the same issue, im running Cm7 with Honity, and I dunno what to do, ill be using my phone and suddenly it will spaz out and continuously hit back until were on home, then just keep pressing it!
I am running stock, unrooted 2.3.2. I also occasionally have this issue. I have not really been able to reliably reproduce this issue. Sometimes it happens middle of the day, sometimes towards the end of the night after the phone has been in use all day. Other times I can go days without having an issue. I had chalked it up to a quirk of my phone, but it is nice to see other people having the issue too.
Hopefully it is a firmware/software error and not something physically wrong with the phone. I would have to have to send it in for repairs.
i tightened the 6 screws on the back of the phone and i stopped having that issue. try and see if it will work for you
Yeh your not alone.
I have done a factory reset and not experienced the issue as of yet, its been 2 days, however if it should happen again i will try tightening the screws a bit.
Back button issue
There are a few longer threads in this forum about the back button issue on the Nexus S -- for some people the back button doesn't work at all, and for others it turns on all by itself. There were a few replies from a Google employee (ryguy) who said it would be fixed in an upcoming OTA update, etc. but some reported having problems AFTER getting 2.3.2 when the problem didn't exist before. There are also other reports of tightening the screws on the back of the phone, which haven't tried but seemed to improve things for people whose back button WASN'T working at all.
For my phone around 2-3 weeks after buying it I had the back button come on all by itself. I fixed it by doing hard resets, as suggested on an earlier thread that deals with this issue (it's like 10 pages long but has the complete story of everyone's experience and fixes with this issue). Anyway, the point is for me after the first hard reset the problem persisted, so I did it a few more times (like maybe 5 times) and now it's gone.
There are some people who tried a hard reset (factory settings restore) and the problem still persists but I think that you have to do as many hard resets as possible (like, over and over and over) until the problem disappears. I'm rooted so I did a Nandroid backup first, then did 5 hard resets through Clockwork Recovery (select the "Wipe User Data" option), and after five hard resets I just flashed by backup and I was back to where I was, minus the back button issue. You don't have to be rooted, of course, to do this, but if you are, doing that ROM Manager backup allows you to quickly reinstall everything to the exact way it was after you're done with the five or 10 hard resets or whatever.
If you're unrooted you can power off the phone, then turn it on while holding the Up Volume button. This boots you into Bootloader mode and you can navigate around to do a factory reset. Or, if you are rooted and have ROM manager, you can use ClockworkMod Recovery like I did (see other threads on how to use these programs).
Anyway, hope this helps - TC
Samsung Nexus S with root access
Stock Android 2.3.1
My capacitive back button is going crazy!!! I figured it was just the rom or a program running in the background. So I rebooted into recovery and it happened then too!!! Definitely a hardware issue. I didn't drop the phone and I wiped the screen clean. So I'm not sure what the problem is. Is there any way I can disable the back button completely and remap it to the Search button? I never use the Search button, so this would work for me. Please help!
I have had this happen to me, it would randomly act up. After two weeks or so, it just stopped happening.
I have seen reports on forums that some people have tightened the screws on the back of the phone and had luck with that fixing the problem.
Sorry I can't be more helpful.
Yeah happened to me too when I first rooted it, found out it wasn't the root that did it but an application that I put on there that was not compatible with the phone.
I had the same problem too -- I posted this a few days ago on another thread dealing with this problem. I'm not sure why it's happening but it many people think it's a software incompatibility issue. I did five hard resets and the problem went away. Most people who tried the hard resets only did it once, and the problem persists. It'll even persist in recovery. I think you need to do enough hard resets until the problem disappears. Mine now is glitch-free -- good luck.
http://forum.xda-developers.com/showthread.php?t=952535&highlight=back+button+issue&page=2
Nexus S
Rooted Stock 2.3.1
T-mobile unlocked
Try installing the stock 2.3.4 just for trial. The new update fixed all my issues with the back button
Sent from my Nexus S using XDA App
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
SphericalPuma said:
I had this happened on a recently purchased nexus s. It was on 2.3 stock, and the back button just went crazy, the screen would flicker on and off, and no matter how many factory resets I performed, the problem was still there. I eventually returned it and the new nexus s has been problem free.
Click to expand...
Click to collapse
Your new nexus s are using latest version or not?
I have this issue sometimes too. Mine doesn't go crazy though, it just becomes unresponsive and dark. I have to wait a couple of seconds and then it comes back. Kinda of like the phone freezing while the damn button come back.
Running Nexus S4G 2.3.4
I've been having a pretty bizarre issue with my Nexus 10 for the last two months, and I'm curious if I'm the only one. At some point, my touchscreen will stop responding to input, and it will stay that way. Even after restart, the touchscreen will work for a few seconds, and then suddenly freeze again. If I factory reset, it will seem to work again, but at some point (sometimes hours, sometimes days), it will happen again, just as I described. This only seems to occur in 5.0+ roms, but it happens no matter what rom I'm using -- I've tried Cyanogen, Lineage, Remix OS, and even stock, with and without root, with the same result. This issue doesn't occur with KitKat roms (I've been running stock 4.4 just to keep my tablet functional), and it also doesn't occur in TWRP. The behavior seems like a driver issue, but the fact that nobody else seems to have it and it didn't occur at all for me until a few months ago makes that somewhat unlikely. Any ideas?
Am I seriously the only person who is having this problem?
I swear, it's just bizarre. This is the first time I've ever had a tech problem and found absolutely nothing about it on the internet.
I did finally get this resolved, and I thought I'd come back and document the solution in case anyone has anything similar happen and is as dumbfounded as I was.
What I ended up doing was completely wiping the system, cache, and data partitions, and then restoring the original factory ROM using the Nexus Root Toolkit. Once I did that, I no longer encountered the freeze-ups. Never did find the root cause, but the tablet is working again, so I'm fine with that.