AOSP Keyboard crashes - 8.9" Kindle Fire HD Q&A, Help & Troubleshooting

Hey guys... Got a weird issue wherein every rom I install on my 8.9 Kindle (JEM) ... the AOSP keyboard crashes every time i try to use it...
Wouldnt normally care, would just install a different keyboard... But it crashes at the very begining of the loading of the rom... cant even connect to the network because I cant type in a password for it...
Anyone ever have an issue like this? Any suggestions on how to overcome the issue?
Ive tried CM10 (Old builds and new) and Ive tried PAC (Old builds and new... as well as stable builds)... all have the same effect... AOSP keyboard crashes as soon as I try to use it... everything else SEEMS to work ok...

RBThompsonV said:
Hey guys... Got a weird issue wherein every rom I install on my 8.9 Kindle (JEM) ... the AOSP keyboard crashes every time i try to use it...
Wouldnt normally care, would just install a different keyboard... But it crashes at the very begining of the loading of the rom... cant even connect to the network because I cant type in a password for it...
Anyone ever have an issue like this? Any suggestions on how to overcome the issue?
Ive tried CM10 (Old builds and new) and Ive tried PAC (Old builds and new... as well as stable builds)... all have the same effect... AOSP keyboard crashes as soon as I try to use it... everything else SEEMS to work ok...
Click to expand...
Click to collapse
You don't want to use older ROM builds. Use the most up to date ROM's for which ever ROM you choose. So lets make sure to do a clean flash. CM 10.2 to get you started. After the Gapps and ROM are on the internal SD card then swipe to factory reset and do this twice. Now flash the ROM and Gapps. After this is completed wipe Dalvik/CACHE only and repeat this twice. Now boot into system and see how you fare.
You can also try booting into recovery and wipe CACHE and DALVIK only and see if this clears things up. The reason I give these instructions is because the keyboard crashing, to my knowledge, was never really an issue using either CM stable builds.

LinearEquation said:
You don't want to use older ROM builds. Use the most up to date ROM's for which ever ROM you choose. So lets make sure to do a clean flash. CM 10.2 to get you started. After the Gapps and ROM are on the internal SD card then swipe to factory reset and do this twice. Now flash the ROM and Gapps. After this is completed wipe Dalvik/CACHE only and repeat this twice. Now boot into system and see how you fare.
You can also try booting into recovery and wipe CACHE and DALVIK only and see if this clears things up. The reason I give these instructions is because the keyboard crashing, to my knowledge, was never really an issue using either CM stable builds.
Click to expand...
Click to collapse
Newer is not always better... but that point is moot...
I have wiped, rewiped, installed, wiped, wiped cahce, dalvik, reinstalled, wiped dalvik, wiped cache, ....
If theres a combination of installing and wiping to be done, Ive done it...
Workaround Ive found has been to install a google keyboard after skipping setup and then using the replacement keyboard as default... AOSP just fails...
(FYI.. not my only android device... so not really a noob at getting these things working...)

Newer is better when working with CM 10.2 as the newest build has given me no problems ever.
Sent from my Amazon Kindle Fire HD running Paranoid Android using xda app-developers

Related

[Q] ROM with Settings Profiles besides CM9?

I am currently using CM9 on my GNex because it has a built-in Profiles management application in Settings.
Is this feature exclusive to CM? Do other ROMs have this feature? I have tried various market apps to replicate this functionality, but none of them seem to work the way the CM9 one does.
I thought I had seen someone using AOKP and it had this in his Settings, but when I tried to Flash that ROM, I got a ton of errors on reboot and didn't find Profiles in the Settings section either.
Also, as I am relatively new to Android (this is my first Android device), should I do a complete wipe data before installing a totally different ROM to avoid process errors? I am using Clockwork Mod recovery to flash ROMs and just performing the default "wipe Dalvik cache" before installing a new ROM. So far, the only ROM I am able to install/update is CM9. AOKP and Codename Android just gave me a ton of process errors after booting and were just unusable. As such, i am currently stuck using CM9, but have really bad wifi performance with it.
TIA!
bryanus said:
Also, as I am relatively new to Android (this is my first Android device), should I do a complete wipe data before installing a totally different ROM to avoid process errors? I am using Clockwork Mod recovery to flash ROMs and just performing the default "wipe Dalvik cache" before installing a new ROM. So far, the only ROM I am able to install/update is CM9. AOKP and Codename Android just gave me a ton of process errors after booting and were just unusable. As such, i am currently stuck using CM9, but have really bad wifi performance with it.
TIA!
Click to expand...
Click to collapse
Yes. Yes Yes Yes Yes. ALWAYS do a full data wipe when moving from one ROM to another ROM. You can sometimes get away with not wiping if you are simply upgrading to a newer version of the same ROM, but anytime that you run into issues after installing a new ROM please do make sure that you wiped data before posting/complaining about issues.
Thank you for your clarification. The next time I try a completely different ROM I will do a full data wipe. I assume flashing new Nightlies of the ROM I am already running doesn't require a full data wipe?
But can you or anyone else tell me if AOKP or any other ROMs have the "Profiles" feature in Settings, like CM9 does? Or is this exclusive to the CM9 ROM?
Thanks again.
bryanus said:
Thank you for your clarification. The next time I try a completely different ROM I will do a full data wipe. I assume flashing new Nightlies of the ROM I am already running doesn't require a full data wipe?
But can you or anyone else tell me if AOKP or any other ROMs have the "Profiles" feature in Settings, like CM9 does? Or is this exclusive to the CM9 ROM?
Thanks again.
Click to expand...
Click to collapse
I haven't seen it anywhere else, though AOKP does offer a Quiet Hours option.
THANK YOU!
Using your suggestion to do a wipe data when flashing a rom, I downloaded the latest CM9 nightly, and just installed it wiping both the data and cache.
After my initial setup and installing the speedtest app, my ping is back to normal at ~25ms and 15mb down and 2 up!
Do you always (or recommend) wipe the data even if you are just updating the current ROM?
Hopefully one of my other apps wasn't the cause of this issue, but I'll soon find out once I have re-installed everything.
Thanks again.
bryanus said:
Using your suggestion to do a wipe data when flashing a rom, I downloaded the latest CM9 nightly, and just installed it wiping both the data and cache.
After my initial setup and installing the speedtest app, my ping is back to normal at ~25ms and 15mb down and 2 up!
Do you always (or recommend) wipe the data even if you are just updating the current ROM?
Hopefully one of my other apps wasn't the cause of this issue, but I'll soon find out once I have re-installed everything.
Thanks again.
Click to expand...
Click to collapse
The ROM developer will usually state in the changelog / release notes if a wipe is required/recommended for an upgrade. Rule of thumb though:
1) Updating ROM to newer version, same Android release (ex: 4.0.3 -> 4.0.3) ==> No wipe
2) Updating ROM to newer version, different Android release (ex: 4.0.3 -> 4.0.4) ==> WIPE
3) Changing from one ROM to another ROM (CM9 -> AOKP) ==> WIPE
Interesting. After reinstalling my apps one by one, I've been running speedtest and found that Airsync/Doubletwist is the cause of my slowness. Uninstalling and rebooting fixes the speed/ping issue right away. Glad I bought this app. Not.

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
nwjimmy said:
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
Click to expand...
Click to collapse
Are you wiping system and data before flashing? This is most likely your issue.
zelendel said:
Are you wiping system and data before flashing? This is most likely your issue.
Click to expand...
Click to collapse
yes, cache and dalvik, and a factory reset.
nwjimmy said:
yes, cache and dalvik, and a factory reset.
Click to expand...
Click to collapse
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
zelendel said:
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
Click to expand...
Click to collapse
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
nwjimmy said:
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
Click to expand...
Click to collapse
No wiping the system doesnt format the data partition. Wipe system then format the data and then wipe the caches and then flash the rom.
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
matt_schieman said:
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Agreed.
Double check your gapps and make sure uts the right version
sent from my 1920 overclocked note 2 running jedi xp12
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
nwjimmy said:
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Most rom threads have a download link to the gapps that work with the version of android that specific rom is on. Look in the rom thread for the one you're currently running. There are different gapps for each android version (4, 4.1, 4.2)
I have that same problem too
I was trying to install new roms for my phone i tried liquid smooth and avatar and CM 10. I also tried install a new kernel and also different recoveries but nothing seems to work. I never "dirty" flashed and i use the right gapps. Someone please help me here i hate stock roms!
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't work.
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
fig03 said:
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
That's a good point. You should be on TWRP 2.7.0.0 that's the latest version of that recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, but it constantly froze, tried to reset, stuck with the same issue. Never used TWRP, so if someone could actually point me in the right direction, that'd actually be helpful.
xantechie said:
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, though...it doesn't really look the way I remember it last it worked, but it's had the issue so long, I forget what it actually looked like before.
Click to expand...
Click to collapse
I have no idea how to use TWRP...it only lists a .img file and no instructions on how to use it. zip files can be used from the bootloader or recovery. WTF am I supposed to do with an .img file. And it can't be to use the terminal emulator because to do that I would have to be able to get passed the Setup Wizard...which is the issue.
I finally figured it out with CWM. Thankfully. The phone would've went flying otherwise.
If anyone else stumbles upon this thread (so they can find the answer for CWM also), you have to format the device from the CWM Recovery to get rid of the crap that is blocking it. I did the following:
Once in CWM Recovery, Remove your SD card to avoid formatting it by accident.
Use the Volume Key to scroll to "mounts and storage".
Format all existing options (this is why the SD needed to be removed); this will blank out the phone's system which was causing the Setup issue to begin with.
Put your SD card with the ROM to be installed back into the phone.
Follow the guide as normal after this (install ROM, then reboot, then KK_gapps, then wipe the two caches, then reboot.)

(Q) CarbonROM issue. G-apps?

Ok so ive been looking up different roms for the sprint GS3. I have found cm10, jellybam, freegs3, the peoples rom synergyROM, and carbonROM. So far i like jellybam, freegs3, and synergyROM. I was trying to use CarbonROM but every time i try to install g-apps for JB it has an error and kicks me out of the setup process. Ive tried a lot of different g-apps versions for JB and it gives the same error causing setup to FC. From there i have to battery pull and boot into recovery and revert to backed up rom. Ive fully wiped every time i have tried but still the same issue. Im trying to run CarbonROM v1.7 and the g-apps for JB dated 2013-03-01. Any ideas what is going wrong?
Sent from my SPH-L710 using xda premium
hawke591 said:
Ok so ive been looking up different roms for the sprint GS3. I have found cm10, jellybam, freegs3, the peoples rom synergyROM, and carbonROM. So far i like jellybam, freegs3, and synergyROM. I was trying to use CarbonROM but every time i try to install g-apps for JB it has an error and kicks me out of the setup process. Ive tried a lot of different g-apps versions for JB and it gives the same error causing setup to FC. From there i have to battery pull and boot into recovery and revert to backed up rom. Ive fully wiped every time i have tried but still the same issue. Im trying to run CarbonROM v1.7 and the g-apps for JB dated 2013-03-01. Any ideas what is going wrong?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
How exactly are you flashing, rom, then gapps, in the the same instance of recovery? what recovery are you currently using? How are you wiping phone prior to flashing?
Im using TWRP recovery v 2.5.0. Im also wiping cache, dalvik, system, and factory reset. The rom works fine without g-apps. But i cant access the android market or anything. I tried these ways: 1) perform full wipe, reboot into recovery, install rom, wipe cache/dalvik, reboot into recovery, install g-apps, wipe cache/dalvik, reboot system. 2) same as #1 but no rebooting into recovery. 3) same as #1 with no cache/dalvik wipe in between. 4) same as #2 with no cache/dalvik wipe in between. So im not exactly sure why its giving me a FC on setup with gapps.
Sent from my SPH-L710 using xda premium
Edit: Found the issue. Somehow the gapps were downloading and becoming corrupt. I opened the files on PC and then cleaned the old data up and redownloaded and it works just fine.

4.3 issues

I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
4.3
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
stormannorman said:
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
Click to expand...
Click to collapse
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
dkrcubsfan said:
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
Click to expand...
Click to collapse
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
kj2112 said:
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
Click to expand...
Click to collapse
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
if twrp keeps giving you problems like these maybe try doing it from cmw. ive read it gives way less problems than twrp:good:
Decimus Meridius said:
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
Click to expand...
Click to collapse
This. 2.6.1.0 twrp.
Sent from my cellular telephone

[Q] KK + GApps = Bootloop

Hello,
i have a Problem regarding KitKat in combination with GApps,
yesterday i installed some KK ROMs, to find the one that suits my needs (AOKP, PA, CM, Carbon and Omni), and all of them worked really great.
But as soon as i flash a GApps package (PA, AOKP or BaNkS' GApps), the phone becomes literally unusable. Every press of a button takes like 5 secs with shuttering animations and the device bootloops every minute.
Before flashing the KK ROMs i upgraded vrom an oldish CWM 6.0.0.x or sth in that timeframe (Android 4.1) to the latest TWRP.
Before every flash i wiped Dalvik, System, Cache and Data.
Any suggestions?
Infi<3 said:
Hello,
i have a Problem regarding KitKat in combination with GApps,
yesterday i installed some KK ROMs, to find the one that suits my needs (AOKP, PA, CM, Carbon and Omni), and all of them worked really great.
But as soon as i flash a GApps package (PA, AOKP or BaNkS' GApps), the phone becomes literally unusable. Every press of a button takes like 5 secs with shuttering animations and the device bootloops every minute.
Before flashing the KK ROMs i upgraded vrom an oldish CWM 6.0.0.x or sth in that timeframe (Android 4.1) to the latest TWRP.
Before every flash i wiped Dalvik, System, Cache and Data.
Any suggestions?
Click to expand...
Click to collapse
Have you tried frashing a rom and gapps immediately after (I mean before rebooting to see if the rom "works really great" ).
I've never tried using a rom without gapps myself, so I don't really know if that helps or not...
evilnoxx said:
Have you tried frashing a rom and gapps immediately after (I mean before rebooting to see if the rom "works really great" ).
I've never tried using a rom without gapps myself, so I don't really know if that helps or not...
Click to expand...
Click to collapse
Yes, that was on the first KK Rom i tried, because thats how i usually install as well (Jelly Bean), and it was unusable as well. First i thought it was the ROM, but since the other ones behaved the same way i tried one without GApps and it was fine. Same with the others without GApps.
Edit:
Retried now with Carbon ROM + GApps Core, seems that yesterday evening i forgot to wipe Cache and Dalvik after flashing GApps, now everything seems to run smooth.
Which CWM version are you using right now? And are you 100% sure you use the right gapps? And in which order do you wipe? (That shouldnt make a really big diffrence)
Edit: didnt saw your edit.
Sent from my Galaxy Nexus using XDA Premium HD app
Infi<3 said:
Yes, that was on the first KK Rom i tried, because thats how i usually install as well (Jelly Bean), and it was unusable as well. First i thought it was the ROM, but since the other ones behaved the same way i tried one without GApps and it was fine. Same with the others without GApps.
Edit:
Retried now with Carbon ROM + GApps Core, seems that yesterday evening i forgot to wipe Cache and Dalvik after flashing GApps, now everything seems to run smooth.
Click to expand...
Click to collapse
Wiping the caches is really important. It forces android to "optimize" all the apps. I believe it actually recompiles some of the code in order for the apps to work better, and in your case to actually work at all.

Categories

Resources