Hi,
my problem is that, completely out of the blue, the Meny and Back buttons stopped behaving as they should.
One minute they were working normally.
The next if they tap them I feel the normal vibration-feedback... but nothing happens.
If I set them to perform different functions, they work.
It is just the "Open Menu" and "Go Back" functions that somehow refuse to be executed.
This happened while my old DesireHD was running the Gimme-A-Break 1.7 rom.
So I flashed a new rom (Mokee Opensource) and after a day or two the same problem reappeared. (along with the "Insufficient Storage" bug, but that's a different problem).
Does anyone have any idea about what's happening to my poor phone?
It happened again in less than a few hours after a clean install of the latest Cyanogen.
Also I noticed the problem doesn't appear when I am navigating the Recovery mode (4Ext)
Related
Well my phone has been acting weird recently. It seemed right after I upgraded to radio 4.49.25.77 as well as upgrade to cell evo 7.5 (http://forum.xda-developers.com/showthread.php?t=622883) now when in the os it seems unresponsive and acts weird as well as it is unable to boot now. (it booted fine for a while until now) Is it the radio i flashed bad or what? Ive tried a different rom as well and it turns out the same.
All it does it gives me the white att screen, then the red info comes up. then the screen dims a bit and freezes.
Any ideas? thanks
change radios and see what happens
Rhodium500 said:
change radios and see what happens
Click to expand...
Click to collapse
Tried, changed from that to 4.49.25.91 and no go.
Could it be the device is corrupt? I flashed back to orig radio and then tried to restore the phone by hitting the power + end and start and it does the same thing.
did you install any applications after you flashed the device? you mentioned that it worked fine for a while and then the issues started. Sometimes, applications conflict with one another and either the phone freezes or one of the conflicting applications become unusable. I would try to recreate step by step any applications you may have installed to identify the culprit.
hard reset.
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
I'm running CM 6.1.1 Stable on my G2 (just a couple weeks old) and I've noticed that my home button doesn't work sometimes. It works about 95% of the time, but then it will do the occasional hiccup where nothing happens. If I touch it a few more times it will eventually start working again. Not sure what it is, but I read in another thread here that it could have something to do with how the CM ROM is configured for capacitive touchscreen sensitivity. And I believe I read that this has only been reported in CM and not other ROMs.
dutman said:
Okay, so I had the g2 for a little now. However, I just recently rooted it. I used visionary r14, and eventually got s-off. I then downloaded ROM manager, and tried installing cyanogenmod 6.1.1. The installation didn't give me any errors, and when it was finally done, everything seemed like it didn't work, as if I had just done a normal factory reset.
I had assumed nothing changed, I didn't even have the superuser app installed. So then I tried going back to my homescreen and it wouldn't let me. The home button is not working. I can use the other three touch sensible buttons, but the home one seems to have been disabled. Would anyone know what could have led to this, and more importantly how can I fix it? For those curious, yes I still have s-off. Is there any way I can remove it, if only it would assure my home button would work again? Thanks in advance.
If anyone has any form of information at all, it would be extremely appreciated.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Does it completely not working??, delayed maybe??
Sent from my HTC Vision using XDA App
Had this issue yesterday. I did a factory wipe from Clockwork and reflashed CM. Fixed it.
even iam facing the problem, but i guess mine is worst as the all(4) softkeys doesn't respond, but when i press it, i receive the feedback i.e it vibrates.
2nd issue: my physical keyboard layout is pretty much messed up, the symbol key which i press on my keyboard doesn't display the exact symbol
it would be kind if someone offer some solution for this
Rom: CM 6.1.1 (even tried nightly build #85)
Build: HK
P.S: i never had those problems in the stock rom
I'm having the same problem with CM6.1.1. I noticed it after installing Twidroyd app. I couldn't exit it via the home button...had to back all the way out. Uninstalled and still having the problem. Doesn't seem to be working at all now.
I had this sort of problem with my G1, I flashed the BiffMod ROM and some day, the phone just randomly did a factory reset, the background is set to how it was when I first flashed it and the home screen was back to normal like how it was when I first flashed it. My home button would not work, when I pushed the end call button to put the phone in sleep mode, it would turn off but if I were to press it again,the screen would turn on but it didn't go to the lock screen it just turned on. To fix it I went into recovery and wiped all five(I'm using Amon_Ra's recovery on it) then I booted back up and my home button worked again and when I put the phone to sleep, it turned back on like normal with the lock screen. That has happened a few times, some times when I did the wipe, every thing would start working again and my home screen still had everything placed where it is suppose to be. You could try to wipe everything, but I can't guaranty it because I don't even have my G2 yet so this has never happened to me on a G2.
i wiped everything data / cache ,flashed GingerVillain 1.4 , the softkeys won't work even in this rom, the only place where softkeys work is HTC's Stock rom. iam just wondering is it due to my build, as its Hong Kong build, so there is a possibility that the keymap for softkeys are different?
Update: Fixed! http://forum.xda-developers.com/showpost.php?p=9353194&postcount=1
Hi all,
i've been using ARHD Roms since a few months and never had any serious issues with that (except proximity sensor fail ..) but now i'am a bit clueless.
Since flashing ARHD 6.1 (using SuperWipe first, no other Mods, everything was fine after flashing) and using it a few days i noticed two things:
First: Random Force close of different apps. I saw that even SuperUser app does FC every single time. Cleared cache - fine.
Second: I noticed that i somehow pressed 2 or more keys at the same time (i can reproduce it now - hold "power" button and shortpress "home"-button) and did a "screenshot" out of the box (in the ARHD FAQ-Thread is an info which says it does not work without modifications/3rd party tools) and - now it comes - ecaxtly since this day my power menu doesn't work anymore.
Long-pressing doesnt work, i can even hold it for 20 seconds and nothing happens until i stop pressing, then the screen goes off but no power menu appears - so the hardware of the button is fine, i still can power on the phone as well
Tried rebooting several times, even flashed ARHD 6.1 again (checksum is fine) but the issue still exists... everytime i'd like to reboot i need to use rom manager and boot in recovery or remove battery.
Is this a known bug? found nothing via search function :/
You can try this post:
http://forum.xda-developers.com/showpost.php?p=17623012&postcount=51332
Thanks, enabling the Secure Credentials fixed the problem. Unfortunately only until reboot, then the box isn't ticked anymore and i've to enable it again - but thanks anyway, i can live with that for now.
Strange issue ... i wondered why not more useres experiencing it, my phone is "stock" arhd 6.1 without any mods or somehting like that ...
I can confirm that his happends to me alot too.
On the same rom.
Still no solutions other than Secure credentials?
Same situation here. Although I update to 6.1.5 the problem still happens. Any idea rather than secure credential ?
My wife's phone is having issues with the capacitive menu button.
It doesn't matter what ROM is installed, it will work for a little while and then it stops working completely.
What I have done already:
Wipe in cache and davlik cache in TWRP.
-No change
Wipe/Factory reset in TWRP
-Works for a little while and then stops
(nothing crazy installed, can't find anything that would be disabling it)
Flash different ROM
-Works for a little while and then stops
(nothing crazy installed, can't find anything that would be disabling it)
This began about 2 months ago and she just lives with it. I cannot, too many things she does not have access to without it.
Any ideas? If not, I may just bring it to sprint and see if there is a physical issue with it. Strange that it works for a little while though.
We both had the same phone for a while, just upgraded mine, but she does not have anything installed that was different from mine or different from what she used for the first few months of owning it. Everything was working fine for a while.
Thanks for the help.
Hi guys,
So I recently converted my phone to a GPE edition with the RUU in order to experience Lollipop.
After a while I missed the Sense features a lot, so I decided to go back to Sense.
I followed the steps in this thread and succesfully flashed the firmware and a stock nandroid. (http://forum.xda-developers.com/showthread.php?t=2733523)
I booted up and discovered that root had persisted. I wanted a fully clean Sense wipe, so I decided to do the following.
I installed TWRP, did a factory reset and formatted /system/. I then installed the stock recovery again and flashed the following RUU through the SD-card + hboot method.
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 (the 1.12.401.17 one)
Everything ran succesfully, no errors popped up and the process said "succes, press power to reboot" or something.
I set my phone up again, not restoring from backups and keeping a minimal amount of apps installed. Ever since the RUU flash I have noticed the following things:
-The phone will turn on randomly from sleep. When it's on my desk, even when nothing is prompting it to wake up (no notifications or anything). Like it's responding to phantom wake gestures.
-Music playback will quit at a random point through a song. The music boomsound icon will still display in the status bar but the music player completely quits and the app reloads when opened.
-Apps refresh during use. When i'm using some apps, like the settings or music app, it will "refresh" and scroll back to the top. Not due to excessive ram usage.
-The auto rotate toggle doesn't work. Even with auto rotate disabled, it still rotates to landscape and upside down. I redid the g sensor calibration but didn't help
I experience this issue on every update, and i've updated back up to 4.4.4 sense. Neither a factory reset nor a reflash of the ruu fixes these issues. I'm very certain that the RUU is flashing succesfully.
I looked at memory use and it's sitting at a very modest 800mb out of 1.8Gb.
Anyone have any idea what is happening to my phone?
mw2fan said:
Hi guys,
So I recently converted my phone to a GPE edition with the RUU in order to experience Lollipop.
After a while I missed the Sense features a lot, so I decided to go back to Sense.
I followed the steps in this thread and succesfully flashed the firmware and a stock nandroid. (http://forum.xda-developers.com/showthread.php?t=2733523)
I booted up and discovered that root had persisted. I wanted a fully clean Sense wipe, so I decided to do the following.
I installed TWRP, did a factory reset and formatted /system/. I then installed the stock recovery again and flashed the following RUU through the SD-card + hboot method.
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 (the 1.12.401.17 one)
Everything ran succesfully, no errors popped up and the process said "succes, press power to reboot" or something.
I set my phone up again, not restoring from backups and keeping a minimal amount of apps installed. Ever since the RUU flash I have noticed the following things:
-The phone will turn on randomly from sleep. When it's on my desk, even when nothing is prompting it to wake up (no notifications or anything). Like it's responding to phantom wake gestures.
-Music playback will quit at a random point through a song. The music boomsound icon will still display in the status bar but the music player completely quits and the app reloads when opened.
-Apps refresh during use. When i'm using some apps, like the settings or music app, it will "refresh" and scroll back to the top. Not due to excessive ram usage.
-The auto rotate toggle doesn't work. Even with auto rotate disabled, it still rotates to landscape and upside down. I redid the g sensor calibration but didn't help
I experience this issue on every update, and i've updated back up to 4.4.4 sense. Neither a factory reset nor a reflash of the ruu fixes these issues. I'm very certain that the RUU is flashing succesfully.
I looked at memory use and it's sitting at a very modest 800mb out of 1.8Gb.
Anyone have any idea what is happening to my phone?
Click to expand...
Click to collapse
What rom are you on?
shiniyoyo said:
What rom are you on?
Click to expand...
Click to collapse
Currently stock GPE after a full conversion. But the issue also occured on stock sense and all sorts of different firmwares, kernels etc.