Randomly this morning my phone started acting very strange. It makes its own touches. Goes into apps on its own. Sometimes, call me crazy, it even seems like it can guess what you're going to do next. Goes to Facebook and wants to post status. Opens camera. Goes to pinterest, board and searches.
Tried to wipe in recovery, but it even did it there too. Lead me to the wipe screen, I backed out, then it went into install screen. Finally got a clean flash in, still doing it. I've never seen anything like this before. Any ideas? Running PA 10/26 build, 26A bootstack. I don't know what to do.
hawkstwelve said:
Randomly this morning my phone started acting very strange. It makes its own touches. Goes into apps on its own. Sometimes, call me crazy, it even seems like it can guess what you're going to do next. Goes to Facebook and wants to post status. Opens camera. Goes to pinterest, board and searches.
Tried to wipe in recovery, but it even did it there too. Lead me to the wipe screen, I backed out, then it went into install screen. Finally got a clean flash in, still doing it. I've never seen anything like this before. Any ideas? Running PA 10/26 build, 26A bootstack. I don't know what to do.
Click to expand...
Click to collapse
Its probably just a bug in PA. Ask them for a patch or something because it doesn't seem to be tapping randomly.
Related
Hi, I have an AT&T Nexus One, running FRF85B currently. As of lately, even before update I noticed my home and search button stopped working. The haptic feedback responds when I touch them but they don't do anything. I searched the forums so please don't flame me if I missed a thread. Much thanks to anyone that can help!
P.S. I soft reset the phone a few times and also have reflashed
can you post a logcat of what happens when you press the buttons? and also try wiping cache and dalvik cache
Try to wipe and reflash and post logcat
Gfs stock phone just started doing this. Will try to get some kind of logs... A reset wouldn't make her very happy, fffuuuu
http://www.google.com/support/forum/p/android/thread?tid=3c3ae39887a83bbc&hl=en
&
http://code.google.com/p/android/issues/detail?id=8503
according to this we arent the only ones. it looks like a factory reset can fix the problem, but some on the link above re-encountered the problem weeks later.
surprised XDA hasnt run into this before...
in addition to home/search buttons haptic'in but not doing anything, slide lock screen goes away and the phones cannot receive calls.
Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?
'Programmable'? How can I set Search to ixquick?
Quantumstate said:
'Programmable'? How can I set Search to ixquick?
Click to expand...
Click to collapse
The app's manifest needs to mention that it can handle that event
britoso said:
Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?
Click to expand...
Click to collapse
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.
turbosix said:
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.
Click to expand...
Click to collapse
This is exactly what is happening to me. I'm going to wipe now.
god damn it. this **** just started happening again... n1 has been running the OTA stock GB 2.3.3...
we ended up getting HTC to warranty the phone and everything was fine until this morning..
any help?
same
So i started having this problem about 3 weeks ago as well right after i flashed CM7's newest experimental build. first thing I witnessed was not being able to receive calls. I figured that this was a problem with CM7 and flashed modaco's r26, after a full wipe, when it just came out a few days ago. After a day, i got the problem with the lock screen and the home and search buttons not working. I again thought this was a problem with gingerbread for some reason and flashed MIUI Mod Rodriguez style rom, again full wipe. I had restored everything through titanium backup and other forms of recovery and within about 60 minutes my home button and search keys stopped working.
So I finally figured that it was some settings that I must have adjusted and carried through numerous different ROMs that caused the problems. So next time around I didn't restore anything, running on MIUI mod, and didn't restore anything for the remainder of the day to see what happened. Low and behold, after a reset the problem came back. One other complication is that the phone will always forget my google account and i'll have to re-connect it. Then I realize that the home key doesn't work. So even not importing anything from my old Rom's with a clean wipe didn't get rid of it.
I still get haptic feedback, but the buttons just don't do anything. I changed the setting for how home and search respond in both scenarios and can't get any response either. I flashed back to an old version now and so far i'm alright. But if someone can figure out why this is happening that would be awesome.
For the other people who are having this problem, when you're doing a clean wipe are you then restoring things back via titanium back up or otherwise? and when did you first start to experience these problems?
Istarted having this same problem today. I recently flashed over to cm7 rc2 and then the same thing happened. It seems like after I do a titanium backup and then change a setting it will reset to the cm boot screen and when it comes back there's no home screen or search buttons. All the same issues. Haptic feedback works but nothing happens. I'm on an evo btw.
Same thing occuring for me after flashing CM7. Reverted back to Miui, but so far no luck in fixing this. Numerous factory resets have yet to resolve as well. This is pretty frustrating...
Having this issue as well on CM7. DEFINITELY Titanium related.
I had this problem too. I just had to shut down the phone then leave it for about 10-15 minutes then turn it on again. Everything should be fine again. ^^
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
thelistening said:
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
Click to expand...
Click to collapse
Try to upgrade to the 27.08 Radio/SPL combo. Follow all of the instructions contained within that post. It will suggest you also re-install your recovery. Do it. Once all of this is said and done, if its a software issue, it should be solved.
I had this same issue prior to the upgrade, and all is fine now. Mine didn't FC tho. If I touched the bottom of the screen, it would select something at the top. any questions or a perfect walkthrough, my direct email to my cell is in my info on the left.
<<<<<<<<<< Over there.
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
thelistening said:
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
Click to expand...
Click to collapse
Oh crap. You have the funky color camera?! That might actually be a hardware issue. But we can certainly try this out. I have the gTalk PC app, and it's up and running now if you wanna run through this.
hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.
alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.