Okay, I'm on a rooted Nexus 4. I had the Jellybam 8.x.x rom installed and everything was working fine. I went to update today to Jellybam 10.0.0 and the home key did not work. I thought this was just a bug in that particular version since it's so new. I then tried flashing SlimBean, Paranoid Android, and earlier versions of Jellybam (9.2 and 8.x.x, of course, factory resetting in between all of them). I'm now on the Jellybam I started with and the home key still isn't working. I can change the NavBar settings and make it so that when I long press the home key it goes home, but it's inconvenient. Also, the home key under pie controls doesn't work. All of the other keys work fine (menu, apps and back). I found a couple sources that said people were having similar problems after upgrading to Android 4.3, but I tried a rom on 4.2 and still nothing. If anyone can help I would appreciate it.
spencerj17 said:
Okay, I'm on a rooted Nexus 4. I had the Jellybam 8.x.x rom installed and everything was working fine. I went to update today to Jellybam 10.0.0 and the home key did not work. I thought this was just a bug in that particular version since it's so new. I then tried flashing SlimBean, Paranoid Android, and earlier versions of Jellybam (9.2 and 8.x.x, of course, factory resetting in between all of them). I'm now on the Jellybam I started with and the home key still isn't working. I can change the NavBar settings and make it so that when I long press the home key it goes home, but it's inconvenient. Also, the home key under pie controls doesn't work. All of the other keys work fine (menu, apps and back). I found a couple sources that said people were having similar problems after upgrading to Android 4.3, but I tried a rom on 4.2 and still nothing. If anyone can help I would appreciate it.
Click to expand...
Click to collapse
If this problem still persists after flashing new roms + wiping data, I suggest you return to original stock.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Related
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
trevorftard said:
I'm sorry to sound noobish, but every time I flash a ROM on my Nexus 4 (mako) that isn't a Cyanogenmod build (10.2-20130904-NIGHTLY-mako) , my home softkey becomes completely useless and the AOSP or AOKP keyboard constantly crashes. I was told this is a known bug in certain source codes as far as the keyboard is concerned in 4.2.2 builds, but I'm still mystified by the home button issue and as to why I other people can be using the same ROMs that I can't without a problem. Is there a certain version of GAPPS that I can flash to avoid this problem, or is there a known fix? I always wipe data and cache when flashing, so I'm pretty sure this isn't a user error, other than which version of GAPPS I'm flashing (gapps-jb-20130813-signed.zip).
Click to expand...
Click to collapse
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
You should also format the /system partition when you flash a new rom.
For some roms the Home button stop working for me and to fix it I had to install gapps, but most CM based roms I use don't have that issue.
As for keyboard, I always delete the default keyboard from the rom and use Google Keyboard.
Andre_Vitto said:
The known issue you are talking about is the JSS deadlocks? if yes, then it is not the problem with you.. for you it force closes the keyboard.. are you following the procedure of installing rom properly? are you doing dirty flash (flash without wiping data)? you can find out if gapps is responsible by booting into a freshly installed rom without installing gapps and see if the problem persists..
Click to expand...
Click to collapse
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
trevorftard said:
Please explain what JSS deadlocks are. I don't dirty flash. I always wipe data. As for the keyboard and home buttons not functioning properly,I have this problem with XenonHD, PACman ROM, AOKP and CM variants.
Click to expand...
Click to collapse
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Andre_Vitto said:
No your problem is not the jss deadlocks.. it happens when you type very fast or something.. it phone vibrates for like 5-10 sec and then restarts. I dont think its your problem. Sorry mate I have no idea why you are having the keyboard and homescreen issue even when you are are doing a factory reset every time you flash.. and why its not happening with CM 10.2..
Click to expand...
Click to collapse
Well, that's unfortunate. I've found that the RevoltHD ROM doesn't have problems, but that's because it's got integrated GAPPS.
Been having the same issue with my Nexus 4, after installing GAPPS the keyboard crashes and the home button stops responding. Did anyone figured it out by any chance? Thanks.
I still don't know what caused it, but I figured out that more recent nightly versions of those ROMs don't have that problem. I'm using AOKP currently and that used to be a problem ROM.
Take off vibration and sound and all the bells and whistles and your keyboard should be fine if the issue isn't Rom specific. Also, it could be kernel related.....try boosting touch input if nothing else
Sent by flying midget
I get the same problem, I factory reset each time I switch ROMs. I was trying with Vanir a couple of days ago and couldn't get the home button to work, tried OmniROM and it worked perfectly, went back to Paranoid it worked perfectly again, went back to Vanir and it didn't work. Was odd.
Hello Everyone,
Nexus 4
Paranoid Android 4.2Beta1
Franco Kernel
I just upgraded to PA 4.2Beta1 from PA 4.1.......
after installing the rom.....when i use my browser or messenger where we require keyboard....the Keyboard doesnt pop up....whats up with this....and also the back button of my navigation bar doesnt work.......this even happened with carbon rom a few days back...when i was experimenting with it.....but then i restored to PA4.1 due to the above given problems....plz offer a solution to this...
The same problem
keyboards not working
please help me my keyboards are not working . i have installed an custom rom.
Hello all,
My apologies if this is a common issue. I have searched but the only old thread about it is the following:
http://forum.xda-developers.com/showthread.php?t=2190960
and no real answer was suggested there, which is why I am asking it again.
So the issue is the same as in that previous thread: quite often, when I longpress the power button, the menu (to shut down, put it on vibrate mode, ...) does not pop up. The only way to get it back is to hold the power button until the phone shuts down, and then reboot the phone, after which it works again (for god knows how long).
I was rooted (with stock rom) before 4.3, but lost my root when updating to 4.3, so I was on stock ROM without root when the problem first appeared. Now yesterday I rooted again and flashed paranoid android ROM (first factory reset, clearing cache and dalvik cache), but the problem remains.
In that old thread one member solved the problem by flashing the stock kernel, however I have never flashed another kernel so I doubt the kernel is the problem?
If anybody knows the issue and a way to solve it, please let me know, it would be greatly appreciated.
Thanks,
Maarten
You did flash a kernel when you flashed the rom
Wayne Tech Nexus
Hey there
No, as in the first post, I have never flashed another kernel on the nexus. Neither did I flash a new radio.
I had not flashed anything yet when the problem started, I only unlocked the bootloader and rooted my phone when I first got it (but it worked a long time without any problems)
Delete this post
Nobody had this issue ?
Found a solution at last!!
wolfway said:
Nobody had this issue ?
Click to expand...
Click to collapse
After quite a long search and a lot of worries, I finally found THE solution...
https://www.youtube.com/watch?v=d8dbrerUacw
how to get out of factory mode for a s4 but it worked on my N7105
- efs/factoryApp/factorymode/ouvrir avec/editeur de texte/ON
- efs/factoryApp/keystr/ouvrir avec/editeur de texte/ON
I have this issue too. I'm using paranoid Android beta 4 with franco kernel and since The moment o rooted my phone this issue started
Sent from my Nexus 4 using XDA Free mobile app
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
foxguard said:
Ok, I was running PA 4 Beta3 but was having problems with the screen delay so thought I would completly wipe my phone, fresh install PA and install the mini Gapps (I had prev installed the stock but didnt want all the apps)
Here is where it started to go wrong, Phone would not start ptopery, would get past animation screen but that was it, would then just crash with small date in corner.
Wiped and flashed just the Rom and this also failed.
Wiped and installed 3.99 and this seem to work but then the wizard crashed and I had to power down.
Booted back up into recovery and dirty flashed Beta 3 again and this seemed ok. Flashed Stock Gapps and rebooted.
All apps have installed again, titanium back has been run but I still have no network what so ever.,
If i go into settings, more, vpn, mobile networks I get 'unfortunately settings has stopped'.
I have dirty flashed again but still have same problem.
I cant do a complete wipe and install again as need to get out of the office, however with the prev problems I had I am weary about doing so.
Can anyone shed any light on any of the issues i had at all?
Click to expand...
Click to collapse
Sounds like a radio issue. If you are running 3.99, you need the radio for 4.3 which I do believe 3.99 is based on. You need the radio for KitKat when running the new betas.
Sent with my Nexus® 10 minus 3
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
I think I basically said that. Sometimes I believe in not holding hands and let the guy/gal do some of the, legwork.
Sent with my Nexus® 10 minus 3
Thank you every one. I have reverted back to my recovery and all is well but I don't understand why when I flash the ROM ad gapps it happens. My recovery is the same ROM and gapps. No idea.
Oh well stuck with the screen delay for now!
Sent from my Nexus 4 using Tapatalk
mrhiab said:
This is the easiest way to flash a new radio http://forum.xda-developers.com/showthread.php?t=2607221
If you went up to a 4.4 based rom and it changed your radio to .97 or .98 then you'll need to flash back to a .84 or before.
to go back to 4.3.
Click to expand...
Click to collapse
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
foxguard said:
Hi mate, thanks for this. I have reflashed my phone again and still have the same problem. My baseband is showing as 84 though s that is correct?
EDIT, dont worry a reboot has fixed this issue. Odd.
Thanks again though.
Click to expand...
Click to collapse
Ohh you are having issues with ur network !! Seen people completely losing their Imei during flashing !! Not to scare you but its better to get the imei files backed up !!
Check my post on the below mentioned link
http://forum.xda-developers.com/showpost.php?p=49753344&postcount=11
Hit the thanks button if you find my post useful
Hi, I recently got an A5 (2015) that hasn't been used for a while. It had lollipop on there so I updated it through OTA to the newest version and after that the recent apps and back key stopped working. I tried factory resseting, reinstalling the newest version of the firmware through odin, and now i rooted it and installed Aryamod ROM (note 7 port) and still no change. Only thing that fixes it is going back to lollipop, but i do not like that firmware because its buggy, laggy and outdated. Does anyone know the fix for this? Thanks for your help in advance
I apologise if this is a well known issue or something, but I couldn't find a solution through search or google. Also sorry for my fails in speaking English
EDIT: I also noticed that the phone gets stuck in sleep. Sometimes it takes really long for the screen to turn on, and sometimes it won't turn on at all and i must reboot the phone by holding power and volume down keys. Not sure if this is relevant, but it sure is annoying.. Currently running aryamod with hadeskernel v2.0
I flashed latest release version of Mokee MM Rom from their website yesterday. I'm in love with this rom mainly because it has Viper4android pre installed in it.
But the capacitive home button is not working in this Rom. (Like with previous roms such as nuclearom, just by swiping left or right in the home button I could access recent apps, Back button)
So, is there any way to bring the capacitive home button functionality to this Rom.
I already tried a flashable zip which was meant for CM 12.1, but it didnt work, My phone went to bootloop.
Someone please suggest a solution here.
Same Problem
Alwin123 said:
I flashed latest release version of Mokee MM Rom from their website yesterday. I'm in love with this rom mainly because it has Viper4android pre installed in it.
But the capacitive home button is not working in this Rom. (Like with previous roms such as nuclearom, just by swiping left or right in the home button I could access recent apps, Back button)
So, is there any way to bring the capacitive home button functionality to this Rom.
I already tried a flashable zip which was meant for CM 12.1, but it didnt work, My phone went to bootloop.
Someone please suggest a solution here.
Click to expand...
Click to collapse
It seems there are two fiiles in system/usr/keylayout called Generic and Goodix-CTL. The issue is because CM 12.1 uses the FPC1020 file (driver) whereas Mokee uses something else. I tried changing the Goodix-CTL 158 to HOME but it makes the Back button work as BACK! Really confused as to what is to be done.