Alright well i can't post in the Android Development section yet but need to get this problem solved.
I flash CM10 and keep getting an error that the Android Keyboard (ASOP) has stopped working.
I cannot get the keyboard to pop up at all, I've tried to reinstall CM10 and factory resets. Nothing is helping it and I can't find anywhere to solve this problem.
Rlacsamana89 said:
Alright well i can't post in the Android Development section yet but need to get this problem solved.
I flash CM10 and keep getting an error that the Android Keyboard (ASOP) has stopped working.
I cannot get the keyboard to pop up at all, I've tried to reinstall CM10 and factory resets. Nothing is helping it and I can't find anywhere to solve this problem.
Click to expand...
Click to collapse
You can try this:
-Reboot in recovery
-Make a full wipe (cache, data, partition, advanced/dalvik-cache)
-Install CM10 Rom and GApps
-Make all wipes again
-Reboot
This maybe works. I hope it helps you
I had the same issue, was suggested NOT to use 4.2 gapps. So I re-flashed with 4.12 gapps, and it worked.
Hope that helps.
wowmail said:
I had the same issue, was suggested NOT to use 4.2 gapps. So I re-flashed with 4.12 gapps, and it worked.
Hope that helps.
Click to expand...
Click to collapse
Thank you, I'll try and reinstall later and test it out.
Use the gapps from 7-26-2012
Sent from my GT-P3110 using xda app-developers app
Keyboard doesn't work
So, I'm trying CM 10 on a Nexus 7 (wifi) and as described in the original post in this thread, the AOSP keyboard doesn't work. I tried both the 201212 and 20120725 G apps, neither made the keyboard work. Any other suggestions to fix this? I've wiped the caches, reinstalled, etc., numerous times, with the same result. Resetting the cache for this and the dictionary provider, as suggested at the CM forum didn't work either. I've tried sideloading an alternative keyboard (Swiftkey) but it won't initialize because it can't download its dictionaries which it can't do because it can't connect to wifi, which it can't do because I can't input the &([email protected]#* security key for the wifi . . . I suppose I can keep trying alternative KBs until I find one that works without a wifi connection, but if anyone does have an alternative idea, I'd be grateful.
R_Lowe said:
So, I'm trying CM 10 on a Nexus 7 (wifi) and as described in the original post in this thread, the AOSP keyboard doesn't work. I tried both the 201212 and 20120725 G apps, neither made the keyboard work. Any other suggestions to fix this? I've wiped the caches, reinstalled, etc., numerous times, with the same result. Resetting the cache for this and the dictionary provider, as suggested at the CM forum didn't work either. I've tried sideloading an alternative keyboard (Swiftkey) but it won't initialize because it can't download its dictionaries which it can't do because it can't connect to wifi, which it can't do because I can't input the &([email protected]#* security key for the wifi . . . I suppose I can keep trying alternative KBs until I find one that works without a wifi connection, but if anyone does have an alternative idea, I'd be grateful.
Click to expand...
Click to collapse
There might be issues with the rom itself. I would suggest you check in the nexus 7 thread as this is for the samsung gt 2.
wowmail said:
I had the same issue, was suggested NOT to use 4.2 gapps. So I re-flashed with 4.12 gapps, and it worked.
Hope that helps.
Click to expand...
Click to collapse
4.2 g apps are most def only going to work on jb 4.2.... Very bad idea to try...
atrix2 running majicmod
galaxy tab 2 3113 running cm10.1 nightlys
iPhone 4 traded for some computer work... just sits there...
Related
The new Android Market (vending.apk) had lot's of alignment issues on MIUI ROMs. Here's a fixed vending.apk that Absolute on MIUI-Dev put together. Just flash it and enjoy!
DO A BACKUP BEFORE INSTALLING! It works for some but for some it causes FC's. There's currently no information what's causing this.
http://www.mediafire.com/?z55qwqw5wmwtxx5
Original thread: http://miui-dev.com/forums/showthread.php?1196-New-Android-Market&p=13875&viewfull=1#post13875
Still not working. Force closes every time
No issues for me, simply flashed and all is good. Fixed the alignment issues aswell.
Have you tried removing the old market app and then try installing this one?
cobz91 said:
Still not working. Force closes every time
Click to expand...
Click to collapse
There are some random issues with new market and MIUI. When I first installed the market I pushed it via ADB and that caused the market not to work. The next time I flashed a zip and it worked. I've seen people reporting that sometimes it takes many attempts to get it to work.
Fc on my Desire too...removed old market first ... What now?
Send by me! d[°_°]b
Toisan said:
Fc on my Desire too...removed old market first ... What now?
Send by me! d[°_°]b
Click to expand...
Click to collapse
You made a backup right? You should be able to find the old market somewhere by googlint it. What MIUI version are you using btw? I consider it weird that it works so randomly.
Managed to install 1 app, then force closed the whole time. Erasing user data didn't helped.
Hey, running 12.11, at the beginning it works and i downloaded some apps, than it crashed, tried to delete, wipe cache and reflash the zip, but now it crash every time im startet it twice... Btw, old market is ok, backuped it!
Send by me! d[°_°]b
Well that's definately weird Have any of you tried installing it a few times again? Like I said earlier I had crashes at first install but after recovering and installing again it started working correctly.
Jiia said:
Well that's definately weird Have any of you tried installing it a few times again? Like I said earlier I had crashes at first install but after recovering and installing again it started working correctly.
Click to expand...
Click to collapse
Wiped rom, reflashed 2 times, didn't helped.
EleCtrOx666 said:
Wiped rom, reflashed 2 times, didn't helped.
Click to expand...
Click to collapse
On my the same, wiped, new flash, nothing woukd help, have to wait for later reales of the market, or change the rom xD but nope, i can w8, now i have to put the market back on my Desire, its not an Android Phone without an Market app
see u!
anybody know if this works on the dinc?
it works for me..try this method
i dunno if thisll help anyone but ive been trying for the past week relentlessly to get this to work and i think ive found a solution..at least for me..
i did a clean wipe [data and dalvich] twice to be safe even with amon_ra's..i know its amon's but im just picky
installed miui 12.3_final.zip and booted into it WITHOUT installing the new market yet, and then i opened up the old market to make sure even that was working and to get everything in the cache's memory
reboot..
install barnacles-update-vending-v2.2.6.zip [he claims this fixes the fc issues]
reboot..
let everything load and try the market it should work..it did for me
reboot..and installed the 12.3.1.update.zip over that and it still worked..
the alignment issues are still off so far and i havent tested the fixed alignment .zip yet and ill update after i have..
if anyone is successful in this, or unsuccussful let me know
i have a stock miui kernal also so that might be it...i dunno yet
im flashing the trickle battery kernal now, update in a bit
credit goes to barnacles for his work
[Note: I posted this a few minutes ago as a reply to another post in the "4.3 ROM" thread in this forum, then realized it would likely be overlooked there. Please forgive the duplicate post. n00b]
Great news that albinoman887 got 4.3 off the ground. Unfortunately, I have a problem, and since I'm the junior...est of members, I can't yet post in the development thread where I could ask him this directly.
I did a factory reset on my MyTouch 4G, installed Albinoman's 4.3 (cm-10.2-20130813-Albinoman887-glacier.zip) ROM and the new GApps (gapps-jb-20130726) zip linked to in his thread, rebooted, and everything appeared to be working until it was time to enter and sync to my GMail account, at which point I received an error message indicating that the AOSP Android keyboard had closed. Sure enough, every time I attempted to input anything, the message reappeared and I had no way of logging into my Google account. Touch screen input works, but without a keyboard, that's as far as I could go.
Thinking maybe I had a corrupted GApps zip, I did another full wipe, re-flashed the ROM, and this time tried the 07/13 GApps zip; unfortunately, when I rebooted, I got identical behavior. Since I needed to use my phone as a, you know, phone (they still do that!) tonight, I did yet another wipe, flashed the latest 4.2 ROM (also from Albinoman) and, to make sure it worked, the newest 07/26 GApps. No problems, seems to work perfectly.
I've checked albinoman's 4.3 thread, and, while there are a few bug reports, no one else seems to be having this keyboard problem.
Any suggestions? As a n00b, is there any way for me to message albinoman directly without coming off as a whiny d-bag?
Thanks in advance...
Re: Flashed albinoman887's new 4.3 ROM - keyboard not working
jdburns said:
[Note: I posted this a few minutes ago as a reply to another post in the "4.3 ROM" thread in this forum, then realized it would likely be overlooked there. Please forgive the duplicate post. n00b]
Great news that albinoman887 got 4.3 off the ground. Unfortunately, I have a problem, and since I'm the junior...est of members, I can't yet post in the development thread where I could ask him this directly.
I did a factory reset on my MyTouch 4G, installed Albinoman's 4.3 (cm-10.2-20130813-Albinoman887-glacier.zip) ROM and the new GApps (gapps-jb-20130726) zip linked to in his thread, rebooted, and everything appeared to be working until it was time to enter and sync to my GMail account, at which point I received an error message indicating that the AOSP Android keyboard had closed. Sure enough, every time I attempted to input anything, the message reappeared and I had no way of logging into my Google account. Touch screen input works, but without a keyboard, that's as far as I could go.
Thinking maybe I had a corrupted GApps zip, I did another full wipe, re-flashed the ROM, and this time tried the 07/13 GApps zip; unfortunately, when I rebooted, I got identical behavior. Since I needed to use my phone as a, you know, phone (they still do that!) tonight, I did yet another wipe, flashed the latest 4.2 ROM (also from Albinoman) and, to make sure it worked, the newest 07/26 GApps. No problems, seems to work perfectly.
I've checked albinoman's 4.3 thread, and, while there are a few bug reports, no one else seems to be having this keyboard problem.
Any suggestions? As a n00b, is there any way for me to message albinoman directly without coming off as a whiny d-bag?
Thanks in advance...
Click to expand...
Click to collapse
The same issue did occur for me as well a couple of times, however I already had SwiftKey as the default keyboard prior to installing the update. So I could at least get in to the system. Once the phone booted up, I navigated to Settings -> Language and Input, and tapped on Android keyboard. The error doesn't show up for me anymore.
You can try setting another keyboard as the default before updating to 4.3. It may work for you too.
Hope this helps.
Same thing happened to me. I just went back to 4.2.2 for now since I need a stable DD. I'm sure albino will get it going!
Sent from my myTouch 4G using xda app-developers app
Solution for Keyboard issue 10.2
Hi everyone.
The problem is gapps package. The package that Goo Manager suggests is only for 4.2 not for 4.3
You have to download this and install it from recovery.
Look here, the second link on the post
http://forum.xda-developers.com/showthread.php?p=44607338
Unless in my HTC Sensation worked like a charm
Regards
Jorge
i'm using nexus 4, installed latest PAC ROM nightly (pac_mako-nightly-20130824.zip).
whenever i try to bring up the ring by swiping up from bottom of the phone, i get a " system UI has crashed. blame Tyler"
anyone faced the same problem?
jakejake99 said:
i'm using nexus 4, installed latest PAC ROM nightly (pac_mako-nightly-20130824.zip).
whenever i try to bring up the ring by swiping up from bottom of the phone, i get a " system UI has crashed. blame Tyler"
anyone faced the same problem?
Click to expand...
Click to collapse
I have asked the mods to move your post to the nexus 4 section. Maybe some members over there would have faced this issue. :good:
Have you followed the ROM's instructions properly? Did you do a dirty flash? Have you tried a factory reset?
immortalneo said:
I have asked the mods to move your post to the nexus 4 section. Maybe some members over there would have faced this issue. :good:
Have you followed the ROM's instructions properly? Did you do a dirty flash? Have you tried a factory reset?
Click to expand...
Click to collapse
i wiped everything. factory, cache, then dalvik cache, then flash rom, gapps. tried the alternate path by flashing rom, reboot, gapps. still the same issue. then i tried the pac_mako-milestone.1.RC1 version instead, same problem occurred.
jakejake99 said:
i wiped everything. factory, cache, then dalvik cache, then flash rom, gapps. tried the alternate path by flashing rom, reboot, gapps. still the same issue. then i tried the pac_mako-milestone.1.RC1 version instead, same problem occurred.
Click to expand...
Click to collapse
Try re-downloading the file, that has caused system corruptions like this for me. Has the dev posted this as a bug?
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.
Hey guys. I just recently updated to Android 7 via the resurrection ROM. I have flashed 2 different rooms and this problem still persists. I have done absolute full wipes in between and I have also tried flashing other kernels. This only started as a problem when I went from 6 to 7. Any ideas?
SiqMawsh said:
Hey guys. I just recently updated to Android 7 via the resurrection ROM. I have flashed 2 different rooms and this problem still persists. I have done absolute full wipes in between and I have also tried flashing other kernels. This only started as a problem when I went from 6 to 7. Any ideas?
Click to expand...
Click to collapse
Try different GApps packages.
Gapps solution didn't work. I tried all the way back to Feb gapps packages. I can't get any 7.0 Roms to work without crashing when location is requested. I am back to 6.0 and working fine. What could the issue be? I might try to go fully back to stock then back again.
I'm also having the same problem. I've tried both Resurrection and Lineage.
OP - did you find any solution?
I was having problems with Google Play Services, related to location, and I did type this command on the terminal:
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
See if it works.
Sorry bad english
I've tried Lineage, AOKP, AICP, AOSCP, RR; Delta Gapps, Open Gapps. This problem won't go away.
As far as I can tell there aren't any MM ROMs still being updated? At least the threads are all dead. Really at this point I'm debating going back to stock and waiting for Moto to give me something. Maybe the same bug is what's tripping them up.
purplegreendave said:
I've tried Lineage, AOKP, AICP, AOSCP, RR; Delta Gapps, Open Gapps. This problem won't go away.
As far as I can tell there aren't any MM ROMs still being updated? At least the threads are all dead. Really at this point I'm debating going back to stock and waiting for Moto to give me something. Maybe the same bug is what's tripping them up.
Click to expand...
Click to collapse
Did you try the command, mate? I don't know if someone did try it, and I want to know if it works, because it did work for me
smsporto said:
Did you try the command, mate? I don't know if someone did try it, and I want to know if it works, because it did work for me
Click to expand...
Click to collapse
Just got several messages telling me the action wasn't allowed, even with root
purplegreendave said:
Just got several messages telling me the action wasn't allowed, even with root
Click to expand...
Click to collapse
I tried the command it didn't work for me. The command itself went ok without errors, but it did not fix the rebooting issue. The only solution for me is to put GPS onto battery saver mode, which is not ideal.