This question is for those of you that enable the on screen nav buttons on the 4.2 builds. Does anyone have issue's with the back button not working, or requiring you to hit the button sometimes numerous times to get it to work? I believe the only 4.2 ROM that doesn't have this issue for me is Paranoid Android. Cant figure out why, and it drives me nuts because I HATE the hardware buttons. Thanks for any input...
jmill75 said:
This question is for those of you that enable the on screen nav buttons on the 4.2 builds. Does anyone have issue's with the back button not working, or requiring you to hit the button sometimes numerous times to get it to work? I believe the only 4.2 ROM that doesn't have this issue for me is Paranoid Android. Cant figure out why, and it drives me nuts because I HATE the hardware buttons. Thanks for any input...
Click to expand...
Click to collapse
I had this problem when i was on an ICS rom on my vzw G-nexus. I just had to continue to wipe data and reflash again. i think it took 2-3 times on CWM recovery.
Related
been having a problem with the 2.2 roms. I install them and the screen will go to sleep during a call, and the only way to wake it up is to either hang up the call or plug in the charging cord. The phone will wake normal when i flash back to a 2.1 rom. Does anyone have any ideas how to fix on froyo roms.
Enable trackball to wakeup under cyanogen settings or something like that.
press send + vol up (or vol down, believe it's vol up) to wake up phone. mods please move to q&a thread. thanks and hope this helps.
mjb413 said:
press send + vol up (or vol down, believe it's vol up) to wake up phone. mods please move to q&a thread. thanks and hope this helps.
Click to expand...
Click to collapse
You almost had it.
Press and hold vol+, then while holding that, press and release the send button. That will wake the screen without disturbing the call.
push this to system/usr/keylayout
http://www.multiupload.com/AFKG4K2IBB
sorry 5thagent. remembered seeing the instructions somewhere around. thanks for the correction! :-( i tried. I had forgotten about the other fix.
was just about to post on this today. thx for the infoz
Also... all you should have to do is pull the phone away from your face and it should turn back on almost immediately. I've never ever had this problem lol
Hungry Man said:
Also... all you should have to do is pull the phone away from your face and it should turn back on almost immediately. I've never ever had this problem lol
Click to expand...
Click to collapse
I agree that should normally work,but at least for me when using speaker phone I can't just move the phone to wake it. using trackball wake/unlock works fine though
Sent from my FroShedYo.V6 using XDA App
tazzpatriot said:
push this to system/usr/keylayout
http://www.multiupload.com/AFKG4K2IBB
Click to expand...
Click to collapse
What is that and what does it do?
How hard is it to program the ROM so that the screen turns back on when you touch it?
Hungry Man said:
Also... all you should have to do is pull the phone away from your face and it should turn back on almost immediately. I've never ever had this problem lol
Click to expand...
Click to collapse
this is how i test my roms callin 226 and it alwayz works
Hungry Man said:
Also... all you should have to do is pull the phone away from your face and it should turn back on almost immediately. I've never ever had this problem lol
Click to expand...
Click to collapse
That works but if you have your phone on the table in front of you w/speakerphone enabled while some robot is giving you 5 minutes of number equations, the phone will timeout. When the trackball wake option is selected in CyanogenMod settings/input settings, it will wake the device after you've manually turned the phone off but it doesn't wake the screen after it's timed out. I have been trying to use tasker as a way around this problem but I haven't been able to successfully write a working profile
Blma617 said:
That works but if you have your phone on the table in front of you w/speakerphone enabled while some robot is giving you 5 minutes of number equations, the phone will timeout. When the trackball wake option is selected in CyanogenMod settings/input settings, it will wake the device after you've manually turned the phone off but it doesn't wake the screen after it's timed out. I have been trying to use tasker as a way around this problem but I haven't been able to successfully write a working profile
Click to expand...
Click to collapse
just use the vol up + send?
playpolo4life said:
just use the vol up + send?
Click to expand...
Click to collapse
I was never aware of this method.. Thanks dude
Sent from my FroShedYo V10-ERIS using XDA App
playpolo4life said:
just use the vol up + send?
Click to expand...
Click to collapse
I'm bumping this thread because I have the same problem but my volume rocker is broken/missing so it is very difficult for me to press vol up/down. I need to use a pen tip or needle, which I usually do not have readily available.
Is there any other option out there for me? Why can't I use the trackball or just the Send key????????????
If anyone can help, I would greatly appreciate it.
FYI, I'm running GSB 1.4 (CM-7 Gingerbread based ROM).
edit: Some users on the CM forums said that pressing the Menu or Home keys worked, but that doesn't work for me. They were on CM6, so maybe that doesn't work in CM7, I don't know.
CrayzeeCarl said:
I'm bumping this thread because I have the same problem but my volume rocker is broken/missing so it is very difficult for me to press vol up/down. I need to use a pen tip or needle, which I usually do not have readily available.
Is there any other option out there for me? Why can't I use the trackball or just the Send key????????????
If anyone can help, I would greatly appreciate it.
FYI, I'm running GSB 1.4 (CM-7 Gingerbread based ROM).
edit: Some users on the CM forums said that pressing the Menu or Home keys worked, but that doesn't work for me. They were on CM6, so maybe that doesn't work in CM7, I don't know.
Click to expand...
Click to collapse
I seem to recall that in CM settings, you can configure what buttons can wake the phone up. You should be able to set it to the trackball.
Has anyone else noticed that, at least when using an ICS rom, there is a different level of vibration for the "Home" button and the "back" button? It seems like the back button almost does a quick double vibrate, while the home button only has one. Its pretty annoying trying to get used to it!
Entropy is aware of the issue.
cjerk said:
Has anyone else noticed that, at least when using an ICS rom, there is a different level of vibration for the "Home" button and the "back" button? It seems like the back button almost does a quick double vibrate, while the home button only has one. Its pretty annoying trying to get used to it!
Click to expand...
Click to collapse
This is because the only ICS ROM bases we have (besides the buggy leak AT&T gave us) are i9100 ROMs... And they don't have a capacitive home button. It'll be fixed soon enough -- it isn't like it's the end of the world anyways.
shishir95 said:
This is because the only ICS ROM bases we have (besides the buggy leak AT&T gave us) are i9100 ROMs... And they don't have a capacitive home button. It'll be fixed soon enough -- it isn't like it's the end of the world anyways.
Click to expand...
Click to collapse
awesome. definitely not the end of the world, just wondering if there was a fix and I didn't know about it. thanks for the info!
Basically I installed Saurom Rom, and i've noticed that my home button doesn't vibrate when I press it anymore while the other capacitative buttons do. I've tried restoring to stock rom and that worked, but i'd like to keep Saurom for overclocking. Any ideas guys?
http://forum.xda-developers.com/showthread.php?t=1525341
Search next time or at least read the ROMs OP
its not hard
Ohp, my bad. But thank you!
Hello
The capacitive button lights come on when you touch the screen on ANY AOSP based roms (including CM), I know you can turn them off, but is there a way to have it act the same way as sammy based roms, where the buttons come on only when you actually use em?
xSpeced said:
Hello
The capacitive button lights come on when you touch the screen on ANY AOSP based roms (including CM), I know you can turn them off, but is there a way to have it act the same way as sammy based roms, where the buttons come on only when you actually use em?
Click to expand...
Click to collapse
When you go to the Settings>Display then you can actually modify the time at which the buttons remain on if you like for example set it to 1.5 seconds the buttons would go off after 1.5 seconds if there is no use and buttons would remain on if you are using the touch screen.
Hit the Thanks button if this Helped.
I am on resurrection rom 5.0.5 (kitkat 4.2.2)
Everything was working fine but suddenly the menu button has gone all crazy. Whenever I hit the menu button, it sends me to the screen displaying get google now. I tried reflashing rom and reflashing gapps. but no use. Can anyone help me sort out this problem?
ar.anmolrawat said:
I am on resurrection rom 5.0.5 (kitkat 4.2.2)
Everything was working fine but suddenly the menu button has gone all crazy. Whenever I hit the menu button, it sends me to the screen displaying get google now. I tried reflashing rom and reflashing gapps. but no use. Can anyone help me sort out this problem?
Click to expand...
Click to collapse
Try using CyanogenMod 11, SlimKat, OmniRom, Cyanfox, BeeanStalk, or any other KitKat based ROM just to make sure whether Resurrection Remix was causing the weird problem. If using a new ROM didn't solve your issue and you feel that the menu button is damaged, simply use a rom which supports a Navigation Bar to replace your hardware Navigation buttons. Good luck pal
are you sure ypu are not long pressing the button ? check you settings under buttons if you have by mistake set any custom actions for your buttons .. all the best and happy flashing
Forget about software tweaks that replace the physical buttons, These virtual buttons are only ever going to be any use as a backup for physical buttons...and then ONLY if you have a fully functional phone......
Get the button replaced......
If you end up in a bootloop, you'll need to access recovery or download to sort it out......a "virtual" button ain't gonna help at that point............
Sent from my Markox powered KitKatted S2
keithross39 said:
Forget about software tweaks that replace the physical buttons, These virtual buttons are only ever going to be any use as a backup for physical buttons...and then ONLY if you have a fully functional phone......
Get the button replaced......
If you end up in a bootloop, you'll need to access recovery or download to sort it out......a "virtual" button ain't gonna help at that point............
Sent from my Markox powered KitKatted S2
Click to expand...
Click to collapse
Are we talking about the touchscreen menu button or the physical home button?
robneymcplum said:
Are we talking about the touchscreen menu button or the physical home button?
Click to expand...
Click to collapse
Looks like this time I read it wrong.....
I think he's on about the capacitive touch button on the bottom left of the phone......NOT needed for recovery or download modes......
Sent from my Markox powered KitKatted S2
Hey. Thank you guys. I sorted out that problem. I did not recieve notification so sorry for late reply. I don't know how but the function was changed for short press of capacitive button. Its all good now.
Once again. Thank you