Looks like I've finally come across an issue I can't seem to solve by searching \ lurking:
TL;DR: Home button works fine on stock setup, but dies whenever I install custom ROMs. Used to work fine on custom ROMs.
I've got an AT&T SGH-I747. With the stock ROM, the home button works perfectly fine. I'd been running various incarnations of LiquidSmooth on it since I got it in late December, doing clean installs of each new release, with no issues. After 2.1, I stopped doing factory resets; just upgrading the ROM in place, as everything seemed to be working well. With the release of 2.3, I ran into various problems, so I decided to try a clean install. This worked, except that my Home button was no longer functional. I did a clean reinstall, same problem. I returned the device to stock, and the home button worked fine, so I decided to try going back to LiquidSmooth, but I had the Home problem again. I tried going back to 2.2, but had the same problem. Finally, I tried the nightly Carbon, and found the problem STILL exists.
Ideas?
UPDATE: I clean installed CM10.1 RC2, and the Home button worked. I then installed LiquidSmooth 2.2 without wiping anything, and the button still works. Is there something I am \ am not supposed to be clearing during ROM installs? Everything I read says to wipe data \ cache. . .
Related
have installed new rom a few weeks back defrost 3.1, was all working fine that i remember, i also have smart keyboard pro installed, I cant find any options that i turned it off, but for some reason, it doesnt work at all when you slide your fingers over it inside any text, the actual pressing of the button works just not the moving of the cursor for correcting typos
hardware failre? rom problem? or some setting?
thanks in advance
Got the same problem and i think its not integrated in the ROM yet
Loads of people are having this problem with loads of roms (non sense).
Will be fixed when HTC release their source apparently.
Had it on OD 4.0.3 and 4.0.4. It just required another full wipe and things are working perfectly since. I knew it was the ROM as I didn't experience this on HTC 2.2 and nor in Recovery.
-----------------------------------
- Sent via my HTC Desire -
hi are you saying that you have to use od and a full wipe to get it to work? or it should work on any with a full wipe? your right in recovery it works though!
It seems to be an issue with the driver being used in all Non-Sense roms.
I know of no non-sense roms that have it fully working (based on my readings)
jason4656 said:
hi are you saying that you have to use od and a full wipe to get it to work? or it should work on any with a full wipe?
Click to expand...
Click to collapse
I'm just mentioning that the trackpad has started working perfectly for me after a full wipe when using a non-Sense ROM. Wiping other caches didn't help until I did a full wipe>reflash clean ROM.
Here's the long version:
When using a previous version (3.1.0) of the same ROM (OpenDesire), the trackpad first stopped responding only intermittently, then had suddenly become buggy in registering most touches and after a few weeks, overnight, its functioning totally ceased. I then did a full wipe>reflash of my old saved HTC 2.2 ROM (Nandroid save) and the trackpad was just fine. So I did some checks. I flashed OpenDesire version 4.0.3 (latest then) but without a clean wipe (only caches) and the same trackpad problem reappeared. Then I did a full wipe>reflash of the same clean ROM and everything worked fine. But when I updated to the new version 4.0.4 of the same ROM without a full wipe, the same trackpad problems reappeared. Hence, I just did a full wipe and reflashed the clean version 4.0.4 and all works well since.
-----------------------------------
- Sent via my HTC Desire -
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
So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
noahajohnson said:
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
Click to expand...
Click to collapse
Thank you !!!
it's Work !
So I've recently been having an issue with my phone that I haven't been able to fix through various standard fix methods. I've tried searching for this exact issue but the only thing that seems to work for other people (albeit they were on different devices when they had this problem) hasn't fixed my issue.
Long story short, I went from SlimROM 2.2 (and many other 4.3 based ROMS) to ForkMyLife 4.4.2 to try out KitKat, and I eventually wanted to go back to SlimROM.
I always full wipe (System/Data/Cache/Delvik) and then flash my ROM (in this case it was Slim), a reboot netted me a bootloop/boothang on the bootanimation. Wiping Cache+Delvik cache will get me to Optimizing Apps, but then it hangs at Starting Apps. At which point I can battery pull, restart, and it will restart just fine (typically, I did have one time where this didn't work). But I'd have to do this series of events every single time I reboot. I've tried multiple ROMs, multiple kernels, but everything ends up doing the same thing after a reboot. I've even done a full Stock 4.2.2 Image flashing (full SDCARD/DATA wipe an everything) using mskip's Toolkit, re-rooted and re-did my entire phone to Liquid 2.37 booted up the first time no problems, but the boothang was back on the very first reboot.
What is somewhat odd to me, is that I can run a 4.4 based ROM with no boot issues though. I ran FML 4.4.2 for a few days and numerous reboots, and the same for OmniMetal 4.4.2 to see if it would lead to any boothangs and I had no problems with either.
Any ideas or thoughts from anyone on why reverting back to 4.3 after a 4.4 ROM would cause so many issues?