I am on the Elix-R Rom and after a few days the Google Dialer force closes on me. I flashed only that particular Gapp with Elix-R. I noticed this same thing happened when using the Paranoid Android Rom as well. I have tried re-flashing, changing kernels, updating TWRP, flashing the dialer again and nothing. Does anyone know why this might happen?
Maybe you need more gapps to enable it to work. Try flashing full gapps first
Sent from my Nexus 5 using Tapatalk
Related
I installed CM10 on my AT&T HTC One X and can't type anything as the keyboard keeps crashing. I've searched all over the net for a keyboard to install but everything like Swype requires you install it from the phone directly which I can't type on. Does anyone know of a solution to this crashing issue or somewhere that I can get an alternate KB?
Here's the issue, the keyboard keeps crashing and the home button doesn't work either.. the phone just vibrates when I press it. I installed the CM10 nightly build plus the gapps-jb-20121011-signed.zip GAPPS. I've been searching all over and search keeps breaking on xda so I can't find much on here right now.
-Keith
kelkin said:
I installed CM10 on my AT&T HTC One X and can't type anything as the keyboard keeps crashing. I've searched all over the net for a keyboard to install but everything like Swype requires you install it from the phone directly which I can't type on. Does anyone know of a solution to this crashing issue or somewhere that I can get an alternate KB?
Here's the issue, the keyboard keeps crashing and the home button doesn't work either.. the phone just vibrates when I press it. I installed the CM10 nightly build plus the gapps-jb-20121011-signed.zip GAPPS. I've been searching all over and search keeps breaking on xda so I can't find much on here right now.
-Keith
Click to expand...
Click to collapse
Try rolling back to the most recent stable version.
The new JB keyboard crashes on me whenever I try to save anything, but I'm running it on a Sense rom.
iElvis said:
Try rolling back to the most recent stable version.
The new JB keyboard crashes on me whenever I try to save anything, but I'm running it on a Sense rom.
Click to expand...
Click to collapse
I tried the last stable version too with the same results. Not sure why it keeps crashing on me :/
-Keith
kelkin said:
I tried the last stable version too with the same results. Not sure why it keeps crashing on me :/
-Keith
Click to expand...
Click to collapse
So you can't even interact with the "Select input method" dialogue in the notification pane? Because you should be able to remotely install a new keyboard through Play. Then once it's there, you can switch in the notification pane.
I'm having the same issue. Tried installing CM10 coming from CleanRom. Did a wipe before install.
Not only keyboard for me, home button doesn't work correctly and I cannot launch the browser.
Went back into recovery, flashed CM10 again, preformed not only a factory reset but also did a "system" wipe.
rebooted and things were fine.
rebooted back into recover and installed gapps, things are hosed again.
reproduced on gapps 4.2 and gapps-jb-20121130-signed.zip
phattychops said:
I'm having the same issue. Tried installing CM10 coming from CleanRom. Did a wipe before install.
Not only keyboard for me, home button doesn't work correctly and I cannot launch the browser.
Went back into recovery, flashed CM10 again, preformed not only a factory reset but also did a "system" wipe.
rebooted and things were fine.
rebooted back into recover and installed gapps, things are hosed again.
reproduced on gapps 4.2 and gapps-jb-20121130-signed.zip
Click to expand...
Click to collapse
Same here.. Browser won't open, home and recent apps key don't work also... glad it isn't just me.. So you're fine if you don't install gapps?
-Keith
iElvis said:
So you can't even interact with the "Select input method" dialogue in the notification pane? Because you should be able to remotely install a new keyboard through Play. Then once it's there, you can switch in the notification pane.
Click to expand...
Click to collapse
I can't even log into my google account, I can't get a keyboard to appear to type with.
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
phattychops said:
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
Click to expand...
Click to collapse
I can't seem to find Wipe "System" in the Factory Reset. The only options I am given to wipe are the data and cache which I have tried doing and afterwards reinstalling CM10 and GAPPS-jb-20121011-signed.zip yet the "Unfortunately Android's Keyboard (ASOP) has stopped working" still pops up
I know you have tried one of these but ill quote what Inflatedtitan gave to me when i had the same problem.
"Sounds like there could be a few problems so were gonna go with the most popular ones lol..
1. Sounds like you didn't wipe everything in twrp before you flashed. Make your you always wipe cache, dalvick, factory reset, and system. Then flash Rom followed by gapps.. then reboot
2. Have you restored from a titanium backup? If so, make sure next time its ONLY user apps.. if you restore system apps and data, think of your system settings from one Rom clashing with the system files from your new Rom. They won't play nice together. Only backup and restore user apps+data
3. If the above steps were taken correctly, I would delete the Rom.zip from phone. Maybe download using a different browser. Chrome browser is notorious for corrupting roms.. you could have had a bad download
Sent from my HTC One XL using Tapatalk 2"
With these steps I got my ROM working so maybe it could help you.
The issue y'all are having is coming from the newest gapps. Install a older gapps and you will be up and running. I had the same issue on my tab 7.0 and hox and reinstalling new gapps worked
Sent from my One X
Same Problem Over Here
majortaylor said:
The issue y'all are having is coming from the newest gapps. Install a older gapps and you will be up and running. I had the same issue on my tab 7.0 and hox and reinstalling new gapps worked
Sent from my One X
Click to expand...
Click to collapse
hi all i have sucessfully installed cm10 on my samsung galaxy s i9000
but i forgot to install gapps.
after installing gapps i just cant type anything it keeps telling me unfortunately andriod keyborad has stopped working.
what do i do?
what version of gapps can install for CM10 Stable?
xdagee said:
hi all i have sucessfully installed cm10 on my samsung galaxy s i9000
but i forgot to install gapps.
after installing gapps i just cant type anything it keeps telling me unfortunately andriod keyborad has stopped working.
what do i do?
what version of gapps can install for CM10 Stable?
Click to expand...
Click to collapse
Ask in the I9000 forums
Sent from my HTC One XL using xda app-developers app
phattychops said:
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
Click to expand...
Click to collapse
I had the same problem as others here, keyboard would stop working as soon as my One X started. The above fixed it. I only wiped System, did not Factory Reset. Make sure you're using the above version JB Gapps.
I've seen this issue when I accidentally forget to wipe something. I've found I have to wipe, flash previously working Rom, THEN go back, wipe and install new rom.
Sent from my HTC One X+ using xda app-developers app
So for some reason my phone doesn't like the dialer on every 4.3 AOSP ROM I've tried. I've been on Slim bean, Eclipse and now Liquid Smooth. I get a force close whenever I open the dialer on all these ROMs. I just Odin'd back to stock and rooted using the casual method. This hasn't happened on 4.1.2 or 4.2.2 ROMs. Something on my phone doesn't like it. I just can't figure it out. I thought going back to stock and starting from fresh would help it. Please don't ask if I dirty flash. I never do. I wipe everything a minimum of 3 times and have even wiped internal storage.
I'm using ex dialer and it works just fine. And I disabled the stock phone app. Makes me think it's a graphical issue.
Would switching kernels help?
Sent from my SCH-I535 using Tapatalk
Are you using the gapps that come with Slim? I believe that message means that the gapps package you're using is conflicted with something in the ROM or vice versa. I'm on Slim with their AIO and not having the same issue.
For example, I used to test Slim for Cordell and had the same thing happen. It happened because he forgot he had updated the gapps package he was using and I was still using the one from the site. Once I flashes the correct gapps, then the issue was solved.
I always download the correct gapps and I did so from the slim ROM website. I tried two different gapps packages from there, AIO and aroma gapps, and it still happened. This same thing happened on two other 4.3 ROMs as well, Eclipse 6.0(4.3) and LS 2.10 with the 20130813.zip gapps.
It just doesn't add up but it's still not enough of a deal breaker for me to leave 4.3 ROMs.
Sent from my SCH-I535 using Tapatalk
ExDialer is awsome, I never use the stock one anymore. I'd move on and not worry about it.
Sent from my GS3 running Pac-Man ROM 4.3 nightlies with KT747 Kernel
Sorry, not sure what it could be. Only other thing would be the kernel
So I had the issue on root box 4.2.2. I have been on this ROM before with no issues. It worked right after the initial boot up. But after I finished downloading apps from play store and a couple from my SD card is when it started not working. Pretty sure it's not rom, gapps or kernel related. If I felt like it and had the time, I'd wipe and start over but I just don't feel like doing that right now. If I ever switch to another AOSP ROM, I will try just downloading apps from the play store and seeing if that fixes it. It's just weird, that I removed all apps installed from my SD card and it still won't work. I install all of the same apps on tw ROMs and have never had these problems. Oh well. I will stick with ex dialer.
Sent from my SCH-I535 using Tapatalk
Wow! That was easier than I thought. I was using Super Backup and restoring my call logs across different ROMs. This is what was causing my dialer app to crash. All I did was go into the dialer app settings and looked at the permissions for the app and it just came to me. Maybe if I clear my call log it will work. So I did and immediately it worked. Didn't even have to reboot. Such a relief to know that the problems weren't with the ROM.
Sent from my SCH-I535 using Tapatalk
I attempted to search the forums, unfortunately the search function was unavailable. Installing any ROM forces me to exit setup during initial boot because ASOP keyboard error. After every flash first thing i do is exit setup and install another keyboard. Any reason this may be happening?
You are using the wrong gaaps package for your Rom. They must match in Android version.
Sent from my SCH-I535 using Tapatalk
I have been using gapps-jb-20130812-signed with all the 4.3 roms. In OSE-4.4-20131124-NIGHTLY-d2vzw.zip, It will boot, begin to load then start with the keyboard not responding, system not responding, even while using OSE GApps.
Switched to using gapps-jb-20130820-signed and that seemed to have fixed the issue.
philosoweed said:
Switched to using gapps-jb-20130820-signed and that seemed to have fixed the issue.
Click to expand...
Click to collapse
Use some more updated gapps, timpoh posted a link to a few different gapps packages on the thread. I'm using the slim 4.4 alpha 1.6 gapps, work great. You could also update the Google kb through playstore.
I'm waiting for Android Milky Way
Hey Guys,
i got a really annoying problem.
I'm at the moment on Android 4.4 GZR-Valdius Rom.
Since some days i'm experiencing the Problem, that the Keyboard just disappears.
It is just not opening, apps are still there and so on.
Also the Back-Key doesn't work in this phase.
I had this Problem on PAC-Man Rom 4.3 too and was Happy that has not been on 4.4. After some usage of the actual Rom the problem came back.
I have tried wiping cache, but it didn't change anything
Hope you can help me, i can't be the only one with that problem
Greetz
Esok
Did you flash the correct GAPPs package?
Sent from my HTC6525LVW using Tapatalk
You might want to try installing Google keyboard. Or if you already have it, try uninstalling and reinstalling.
If that's not an option, you could try finding a flashable zip for the aosp keyboard.
I had been running CM 10.2 for a while. Last night did a factory reset/wipe cache/dalvik and installed latest CM11 snapshot (M12). Stock camera app was crashing upon startup ("Unfortunately, camera has stopped."). Tried using 2 other camera apps (Google camera and open camera) and neither worked as well. Then tried flashing SlimKat and had the same problem. Already tried reflashing, rebooting, etc. multiple times. Anyone know why this is happening or have a fix?
I am using ClockworkMod Recovery 6.0.5.1, if that matters.
Also, already tried the CMFix thing from the play store, if anyone is planning on suggesting that, and it didn't work.
Also, I had unsuccesfully tried using the fix posted here: http://forum.xda-developers.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973 not realizing it was meant for the international version. Has that ****ed me over? I have since done a clean reflash of CM11
Update: Downgraded to CM 10.2. Camera does not even work here now! Gives the error, "Unfortunately, Gallery has stopped working". Please help