Database Users

Back button pressing itself now.

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

[Q] rebooting

My Asus Transformer wont stop rebooting and when I turn it off, it takes me countless times to hit the power on/off button to turn it on, then it just randomly reboots every time I am connected to the internet. I have not rooted my device nor have I done anything to affect its stock state, any help at all would be much appreciated!!

I always have to hold my power button for a few second to boot it from a completely off state... Are you doing that? Or just quick pressing it?
As for the rebooting issue, since you are completely stock with out root, then I would start by uninstalling any recent apps. maybe if you remember what new apps were installed around the time the issues began... I would start there. otherwise, factory reset and see if that helps... Beyond that, i'm not sure what you can do with a stock non rooted device. good luck
Sent from my SAMSUNG-SGH-I997 using XDA App

I have managed to do a factory reset, and no apps were present, yet still when I went to the browser it rebooted and now I am struggling to turn it on, after the first lock screen, it reboots again. Yes, I am also holding the power button untill the screen glows. Thanks for the quick reply!

If a factory reset does not fix it, then back up any important data and get on the phone with asus to do a warranty repair (assuming you are past the return date from where you bought it)

I have returned the device and am getting a new one in a few hours. I hve done some research and i understood that the new firmware update does that to the transformer 101. Can anyone confirm that? Or am I safe to update the new device which i will recive? Thanks!

Major software issues with stock Nexus 7 FLO and how to deal with them

It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.

I've had a few apps quit on me and one time at the very first boot after the ROM update I had to force restart BUT I hardly consider these as "Major Issues".

There are always bad ones. Shipping, heat, cold, lightning, the chupacabra, darth vader, moisture, the blob, gremlins, or the Jaberwoky could have caused these "major" issues you have,
You're thread is bunk. Return it....

In stock recovery (when it says no command) have you tried pressing Vol+ to get the recovery menu.

I had the launcher force close on my Nexus 4 a few times shortly after I updated but after a few restarts it went away. Other than that I haven't had any issues with my Nexus 7.
Sent from my Nexus 7 using xda app-developers app

idheitmann said:
It seems that there are some major issues with the new Nexus. This is unrooted, with locked bootloader.
People are reporting not being able to turn theirs on, or having random reboots.
My first boot never got past the Nexus X, and I had to hold the power button to restart.
Then I have had several times where the screen wouldn't come back on after sleep. Again, holding the power button down to restart worked fine.
Then I had gcore and gapps quit unexpectedly, followed by a reboot. I had just rebooted, and only opened one app: Evernote.
So I used the factory wipe option in the settings. Within seconds of completing and booting up the same processes quit unexpectedly.
I tried to reboot into recovery (by holding volume down and power) and got "no command". I tried 'adb reboot recovery' and got the same.
As far as I can tell, the factory ROM is not available for download at https://developers.google.com/android/nexus/images yet.
I obviously don't want to risk unlocking or installing anything custom if there's something wrong with the device.
I will probably have to return it to Amazon.
I haven't found much in the way of information out there, just a few complaints. If there are any well developed threads about how to deal with these issues, please let me know.
Click to expand...
Click to collapse
Had I had these issues off the bat I would have returned the device for exchange or refund (if non where available for exchange). Definitely would not have rooted if I was experiencing issues, right back to the store I would of been.
Mine works very well and I LOVE it!

Thanks for all the encouraging words guys
I'm pretty sure the problem originated when the first boot failed and I forced reboot. The OS update must not have installed cleanly.
Anyway I just installed CleanROM and everything is peachy now. I guess whether shipping improperly flashed devices is a major issue or not is a matter of opinion, but I would expect better quality control from Google. I hope it's not too wide spread, and that anyone suffering this issue has the know how and confidence to install a stable ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta

Here's a major issue. Do NOT install widget locker, and then turn on talkback! You can no longer unlock the tablet!
I thought it was a goner, and that I was going to have to return it, but I googled and found out about safe mode, and then once I got that running, found another link on how to turn off talkback.
My God, is that the most annoying feature you could ever think of!
I was reading the google library information, and it said you had to turn an assessibility feature on in order for google books to readbooks out loud.
I'm back to square one with that now... anyone know how to accomplish this?

No issues here. I absolutely love the device!!
Sent from my Nexus 7 using Tapatalk 2

I have had the launcher die a few times, but that's the only issue I've noticed on mine (and since it comes back, it isn't that big a deal).

[Q] After "Power Off", a few seconds after it shuts off, it starts back up again.

[Q] After "Power Off", a few seconds after it shuts off, it starts back up again.
I recently did a fresh install of CM 11 (M12), and I'm seeing that even if I choose to "Power Off" the phone, after a few seconds, it starts right up again.
I don't know if this is a bug in M12, or if some application is causing this.
Does anyone have an idea what could be going on and how I can fix this?

Is you power button functioning normally? That sounds like the symptom of a failed or failing power button. If you suspect a firmware or software issue, the first recommended trouble shooting step is to flash back to stock and see if the problem goes away.

The button is fine. The phone was previously running CM 10.2.1, and I was able to shut it down properly. I wiped it, installed CM 11 (M12), and started installing apps. The next time I tried to shut the phone down, it restarted a few seconds afterwards, and that's the way it's been behaving ever since.
So I'm pretty comfortable saying that this is likely a software issue, and I would think that it's far more likely to be O/S related as opposed to app related.

Haphim said:
The button is fine. The phone was previously running CM 10.2.1, and I was able to shut it down properly. I wiped it, installed CM 11 (M12), and started installing apps. The next time I tried to shut the phone down, it restarted a few seconds afterwards, and that's the way it's been behaving ever since.
So I'm pretty comfortable saying that this is likely a software issue, and I would think that it's far more likely to be O/S related as opposed to app related.
Click to expand...
Click to collapse
Do you have a backup of 10.2.1? If so, I'd try that first. Or can you resotre a nandroid on CM? I've hardly ever worked with it or other AOSP. Or reinstall 11 to see if it's just a glitch.

I can always go back or reinstall. This isn't that horrible a bug that it's worth doing that, though, as it doesn't affect normal operation.
I wanted to see if anyone was familiar with it, however, and see if there was a known workaround or nightly fix (the changelogs only show the most recent builds, as far as I can tell).

S5 SM-G900F : Black screen/Boot loop; Help?

tl;dr at the bottom
Alright so I'm out of ideas on how to fix this phone, couple of days ago my mom came to me complaining that her S5 was giving her trouble. When she handed me the phone, it was in a bootloop of showing the Samsung Galaxy S5 screen, playing the theme and vibrating afterwards then rebooting. I took out the battery and tried to power it on, it ended up successfully booting into android. So from here, I figured there must have been some malware on the device, I downloaded Malwarebytes from the Google Play Store and ran a scan on the device. However in the middle of scanning, the device turned off it's screen and rebooted. (Malwarebytes found 2 malware on the device at that point) So now I'm convinced it's most likely malware and eventually removed all the detected malware on the device. I gave it back to my mom thinking it was fixed.
Moments later she came back saying that it's still giving issues, my first thought "wdf, it was working wasn't it?". I looked at the phone again, and tried to wake up the device using the power button. The 2 soft keys at the bottom lit up however the screen was still black. At this point, the phone was still working fine, the only issue was the screen wouldn't wake up. So I decided to do a battery pull once again to reboot it and it results in the bootloop once again. I did some googling and found various solutions to this, one of them involved wiping the cache from recovery, so it tried it. Booted into recovery and wiped the partition cache (i think that was it), after it wiped and was about to reboot, I noticed a brief "error icon" just before it rebooted. After this point I could not boot into recovery at all (it would just show a black screen and I would assume that the phone turned off) and it was still in a bootloop. It was only after trying to turn on the phone after trying to boot into recovery that the idea of the phone wasn't off and the screen was just black entered my mind. (Because usually if the phone is off, you can turn it on by holding the power button, the phone would not turn on until after a battery pull)
So at this point, it was late at night and I was tired. I left the battery out and just went to bed. The next day I tried to turn it on again and to my surprise it booted up fine but I was skeptical. I had a theory that the device would work fine as long as the screen remained on, so I set the screen timeout to 10 minutes and kept it on for probably 30 minutes while I continued to google. Since it stayed working during that period of time, I thought perhaps locking the device triggers the issue. I turned of "Power Button instantly locks device" and proceeded to turn off the screen using the power button. When I tried to turn it on, it was back to the same problem (black screen, device is working fine, soft keys lit up). I did a battery pull once again in an attempt to reboot and now it was back to problem #2 (boot loop, can't enter recovery). At this point in time, I considered doing a factory reset but since I couldn't enter recovery, I'd most likely have to re-flash the stock firmware.
Since I didn't have much experience flashing android devices (I personally only flashed 2 or 3 devices ever, all of them were successful but I still didn't really trust myself), I had it sent to a local cellphone company and had them try to fix it. Eventually I got the device back, but they were unable to fix the problem (they tried to flash a stock and custom rom). Now I'm back to square 1, the phone is still in a bootloop, no sound, no vibration this time, I don't have much experience with phones since I've only owned 2 in my life. The phone seems to be soft bricked pretty good, I've still got 1 more trick to try (full stock firmware flash) before I call it quits, any ideas?
tl;dr
- device is stuck in a bootloop (issue 1)
- i was able to enter recovery mode once, now it's not accessible
- download mode is accessible
- the device has been able to boot successfully a couple times, but then it has another issue.
- device's screen would not wake up after turning off, softkeys still worked, everything else still worked. (issue 2)
- the device was sent to a local phone repair company to fix (unsuccessful)
- currently device is stuck on issue 1
additional notes
- device has not been dropped or wet
- device has been owned for more than a year without problems
- this problem was recent (3 days)
- no sd card
- dark screen was turned off
theories
- screen could be malfunctioning or defective somehow, but then if it can show the bootscreen and download mode screen fine it seems unlikely also since it's been working fine for over a year
- it's a software issue of some sort, but has already been flashed by local phone repair to no success, then again I'm assuming they just did a basic recovery flash and called it quits