yashsingh1/xdaforums huggingface dataset:
[General Paranoid Android Discussion] TKruzze:
The advice from above will likely fix your issue.

However, you would be much better off installing GApps the same time as you install your ROM, rather than setting up your device and THEN installing GApps.

Most every ROM developer, including Paranoid Android, recommends doing it this way.

Sent from my ΠΣΧỤŞ 7 ²°¹³ tablet
[General Paranoid Android Discussion] iXNyNe:
I'm surprised this didn't exist before in the keyboard. Can't wait to see it in action.
[General Paranoid Android Discussion] tangcla:
I'm not sure if I should be asking in this thread or the ParanoidAndroid thread - I've got the Google Dialler installed but noticed that every so often it stops working, I have to reflash the Google Dialer addon to get business names showing again.

Does the Google Dialer need reflashing after each ROM and/or GAPPS upgrade?
[General Paranoid Android Discussion] Sc4ryB3ar:
I'm experiencing fc when updating the Google keyboard to the new 3.0.

On slimkat, have pa stock gapps installed, not their own, works just fine so far.

Have cleared cache and data. Have uninstalled an manually installed both old and new, and manually replaced neccesary lib, with correct permissions.

I'm lost at this point. Any suggestions?
[General Paranoid Android Discussion] StormTrooper89:
can you just install the apk only? and dont uninstall the aosp keyboard.
[General Paranoid Android Discussion] iXNyNe:
See OP. Having both aosp and Google keyboard installed in /system causes issues.

My recommendation is to install the keyboard add on and then download the update from the play store. The base will be in /system and the update will be in /data but it should work until the gapps package is updated.
[General Paranoid Android Discussion] moffa~:
When installing it from the Play Store, it just starts installing but then nothing happens. I tried copying the apk to /system/app as LatinImeGoogle.apk (to replace the current keyboard) but it just causes a bunch of force-closes
[General Paranoid Android Discussion] chewdaniel:
i updated google keyboard 3.0 without any issues. then i use TiBa to integrate into /system and FCs started happening. reflashed the 2.0 keyboard and upgraded to 3.0 leaving it in /data with no issues now
[General Paranoid Android Discussion] dannyella:
Deleted
[General Paranoid Android Discussion] Sc4ryB3ar:
OK, I have tried all of the suggestions given. It just isn't happening... Don't know what's up, I'll just wait, thanks guys for trying to help :)
[General Paranoid Android Discussion] shoeprano27:
can i use this for beanstalk or aospa on tmobile s4?
[General Paranoid Android Discussion] osm0sis:
It's the library files required, like [MENTION=2777334]TKruzze[/MENTION] explained to me a couple pages back.
[General Paranoid Android Discussion] TKruzze:
A few days ago I even added it to the FAQ (#18), since I've been reading more posts about using Titanium Backup to integrate updates.

Sent from my ΠΣΧỤŞ ⑤ ☏
[General Paranoid Android Discussion] pdeadm:
Where I can find 4.2.x GApps?
[General Paranoid Android Discussion] iXNyNe:
I don't think PA offered specific gapps for 4.2 (I could be wrong) but http://goo.im/gapps has some and so does http://wiki.cyanogenmod.org/w/Gapps
[General Paranoid Android Discussion] TKruzze:
PA GApps Update Announcement

PA GAPPS - MARCH 21 UPDATE

MARCH 21, 2014 - 20140321

Google Keyboard updated to v3.0.19373.1072412a

Google+ updated to v4.3.1.63038142

Google Text-to-Speech updated to v3.0.11.1070024

PLEASE CHECK THE OP for

Complete Summary of Recent Changes

List of Common Questions and Answers

Package Details and Download links
[General Paranoid Android Discussion] tangcla:
I've noticed that if I try to open a document (PDF, DOC) from Gmail, QuickOffice will force close - but saving the file and opening from a file manager works. This happens on both my Nexus 5 and my gf's Nexus 4.
[General Paranoid Android Discussion] GatoL0c0:
I can open a PDF from Gmail without force close.

---------------

Samsung Galaxy S3

CM11 Nightlies / PhilZ Touch Recovery 6.0 / TWRP / 0-Day PA GApps
[General Paranoid Android Discussion] Whosdaman:
I can open PDF and doc from gmail to QuickOffice without force close. Try reflashing apps and clearing data on QuickOffice
[General Paranoid Android Discussion] störte:
I made a clean flash of a rom and flashed the full modular Gapps from 21.03.14.

After reboot i got following error "Unfortunately Android Keyboard (AOSP) has stopped"

I tried it twice. Will test now the full Package
[General Paranoid Android Discussion] osm0sis:
Clear the AOSP Keyboard app data. Someone posted about it since the update. :good:
[General Paranoid Android Discussion] störte:
Sorry must have overread this.
[General Paranoid Android Discussion] osm0sis:
Nah my mistake, I can't find the specific post I was thinking of anymore; I think they edited it. Anyway, try what I suggested in my last (edited) post. :)
[General Paranoid Android Discussion] störte:
Hmm will try that just to see. With full Package it works well. You mean to setup the phone without any typing then clear app data. I test if that is working as i clean flash my phone anyway.

Doesnt work. I think i will stay on the previous version.
[General Paranoid Android Discussion] Dragonhide32:
Everything force closes if I try do disable google keyboard since it was giving Fc's only. But when I disable it everything started to give fc's and I can't use my phone at all. Even my pc won't recognize it.

OK: After reboot my phone is recognized by my computer and I flashed 2014-03-16 built again. Everything works fine but my pie Controls messed up. Back touch doesnt work anymore. OMG come on a Gapps can do these? I am no newbie by the way. Flashing since 2010:)
[General Paranoid Android Discussion] Ok_Kaleidoscope5109:
I've never installed Google Keyboard, and after the 2014-03-21 update, my AOSP Keyboard crashes left and right even though I don't even use it.
[General Paranoid Android Discussion] Dragonhide32:
Exactly. Don't ever try to disable it. Go back to to .16 built immediately. That fixed everything for me. My phone works as it should right now.
[General Paranoid Android Discussion] osm0sis:
I'm having no issues with the latest keyboard in the Stock package on CarbonROM.
[General Paranoid Android Discussion] pep0te:
I'm back to the previous version and obviously the keyboard works.
[General Paranoid Android Discussion] jorceshaman:
That's because the stock replaces the AOSP keyboard that's force closing. I use SwiftKey and I'm getting the AOSP FC messages.
[General Paranoid Android Discussion] PiggySmalls:
Having any combination of AOSP, Android, and Google keyboards installed at the same time can definitely cause problems, as they all share a lot of files.
[General Paranoid Android Discussion] culson_35:
Working great with PA ota update

ParanoidAndroid 4.4.2 (sgh-t999l)
[General Paranoid Android Discussion] andresee:
Still getting FC on Google keyboard after flashing the latest Stock GApps. I'm running Purity ROM. Any suggestions? I do not have any other keyboards installed.
[General Paranoid Android Discussion] FDisk80:
2014-03-21 is broken!

AOSP keyboard FC's on Mini Modular.

If you look under Apps/ALL the first app is without a name. Is "com.android.keyguard". It gone bad. :-\
[General Paranoid Android Discussion] papete:
Keyboard issue

I think it is pretty obvious that the new google keyboard does not seem to be compatible with everyone (me included). Could you please upload a version without the latest GKeyboard, or just tell me the files that I should delete from the latest package. Thanks
[General Paranoid Android Discussion] apatal:
Just use any other package aside from Stock. Or if you must use the Stock package, just delete the LatinImeGoogle.apk from the zip file before flashing.

Good keyboard works fine for me.
[General Paranoid Android Discussion] FDisk80:
The problem is not the google keyboard as I installed the "MINI MODULAR PACKAGE" that comes with AOSP keyboard and it FC'd anyway.

Going back to the apps from the 16th solves the problem.
[General Paranoid Android Discussion] tangcla:
Cleared data, reflashed, still no good...
[General Paranoid Android Discussion] mammenj:
same for me but after cleaning dalvik and cache, fc gone now
[General Paranoid Android Discussion] papete:
Actually, you are right. I thought about it afterwards and the keyboard is not included in the mini modular package (the one I use), so it must be some new lib or apk that is not compatible with the old keyboard (TTS maybe). Anyway, I installed the new keyboard add-on and voila! no more FC!!
[General Paranoid Android Discussion] chewdaniel:
yea... i read it too but somehow forgot about it. silly me. anyway i fixed it myself without bugging here since i knew i did something not-quite-right :p

was trying to save myself from the future hassle of uninstalling the update and flashing the updated version :D
[General Paranoid Android Discussion] tangcla:
I did that just now, still gets FC :(
[General Paranoid Android Discussion] andresee:
Ok so I assumed flashing the Keyboard would update those Libs that were causing the FCs but was I wrong? If so how can I get the updates libs for the new Google Keyboard?

Thanks
[General Paranoid Android Discussion] TKruzze:
I think I know the cause of the problems that certain people may be having with the keyboard. However, since NOBODY has given me any information to help with the diagnosis, it's going to have to wait.

I believe the problem is due to the fact that even stock/AOSP keyboards (especially CM's highly modified version) rely on Google supporting libraries (from GApps) for them to function properly/fully. Because the Google keyboard included an updated library, I'm thinking that it is conflicting with the stock/AOSP keyboard from GApps.

I would like to test this out, but until I get a proper report from someone, it'll have to wait. I'm building a couple test packages that I will make available via PM to the first couple of people who submit the information I need to make a proper diagnosis.

EDIT: Please do NOT PM with the information. I will send possible test packages/fixes via PM.
[General Paranoid Android Discussion] andresee:
Latest Stock PAGapps

Nexus 5

ART

Purity

# begin pa gapps properties

# This file contains information needed to flash PA GApps

current_gapps_version=20140217

current_gapps_type=stock

installing_gapps_version=20140321

installing_gapps_type=stock

total_system_size_kb=1033516

used_system_size_kb=630772

free_system_size_kb=402744

free_space_reqd_kb=24128

total_gapps_size_kb=389144

install.chrome=true

install.faceunlock=true

install.photosphere=true

photosphere.device=hammerhead

replace.launcher=true

replace.mms=true

replace.browser=true

device_name=hammerhead

# end pa gapps properties

# begin pa gapps properties

# This file contains information needed to flash PA GApps

current_gapps_version=none

current_gapps_type=none

installing_gapps_version=20140217

installing_gapps_type=stock

total_system_size_kb=1033516

used_system_size_kb=362492

free_system_size_kb=671024

free_space_reqd_kb=325764

total_gapps_size_kb=375276

install.faceunlock=true

install.photosphere=true

photosphere.device=hammerhead

replace.launcher=true

replace.mms=true

replace.browser=true

device_name=hammerhead

# end pa gapps properties
[General Paranoid Android Discussion] Dragonhide32:
1- Micro modular package.

2- 20140321

3- Nexus 4

4- Dalvik

5- Paranoid Android 4.2 Beta 1
[General Paranoid Android Discussion] TKruzze:
All 0321 GApps Removed

I have removed all 0321 GApps packages. I will be uploading new version WITHOUT the Google Keyboard as it appears to be incompatible with certain ROMs.

Thanks for the recent submissions, however, please include the link to the ROM you're using soI don't have to go on a hunt to find it. Believe it or not, I actually am downloading some of these ROM to help with the diagnosis.
[General Paranoid Android Discussion] andresee:
Purity Rom

http://xdaforums.com/showthread.php?t=2528265
[General Paranoid Android Discussion] tmorterlaing:
Maybe too late to be helpful, but same issue (AOSP Keyboard has stopped)

a.	GAPPS: Full Modular

b.	Gapps: pa_gapps-modular-full-4.4.2-20140321-signed

c.	Mako

d.	Dalvik

e.	Sorry I wiped the log!!

f.	The latest carbon ROM nightly: https://carbon-rom.com/downloads/?device=mako&type=nightly
[General Paranoid Android Discussion] chewdaniel:
pls do consider either reverting back to 2.0 keyboard or 3.0 as an addon... 0321 works flawless for me on FXP CM11.

tia
[General Paranoid Android Discussion] TKruzze:
PA GApps Update Announcement

PA GAPPS - MARCH 21 UPDATE II

MARCH 21, 2014 - 20140321a

Google Keyboard (and supporting libraries) reverted to v2.0.19133.927933a due to incompatibilities with certain ROM's if installed in system partition

Google Keyboard updated to v3.0.19373.1072412a

Google+ updated to v4.3.1.63038142

Google Text-to-Speech updated to v3.0.11.1070024

PLEASE CHECK THE OP for

Complete Summary of Recent Changes

List of Common Questions and Answers

Package Details and Download links
[General Paranoid Android Discussion] shibliaftab:
Fresh install with ROM, micro modular gapps (.21), google keyboard addon worked

I had made many hit and trial, ultimately, have been successful.

Firstly I would like to give my device info,

Xperia neo V

Cyanogenmod Rom unofficial (http://xdaforums.com/showthread.php?t=2545357)

pa_gapps-modular-micro-4.4.2-20140321-signed

keyboard latest addon (pa_keyboard-module-4.4.2-20140321-signed)

Gapps and addon downloaded from goo.im link ( I think it's worth mentioning)

here is my way of installation

1. Clear everything even the system

2. install ROM

3. install gapps

4. install addon

5. now reboot and check it out and do reply here, worked or not?
[General Paranoid Android Discussion] shoeprano27:
unless im blind, i cant find the updated GApps that has the reverted keyboard..
[General Paranoid Android Discussion] Dragonhide32:
Because you are blind and living in your own wonderland. You think this is real but no. You can't see these. You are asleep for 300 years.
[General Paranoid Android Discussion] TKruzze:
What I think a lot of folks may not be aware of, is that most every ROM's keyboard relies on Google Keyboard supporting libraries to achieve full functionality (swipe, etc). So, even though I don't include Google Keyboard in Full, Mini, or Micro GApps, I have to include the Google Keyboard supporting libraries in those GApps packages or you may not have full functionality of the keyboard that comes with your ROM.

When Google updated their keyboard to v3.x, the supporting libraries were updated as well. It appears that these updated libraries conflict with certain ROM's. I'm still trying to determine if there is even the possibility of making Google Keyboard v3.0 compatible with all the ROM's out there. If not, I will likely remove ALL Google Keyboard support.

I'm fairly certain I've fixed the keyboard FC's in Full, Mini, and Micro GApps by reverting the libraries to Google Keyboard v2.x. However I'm uncertain as to why anyone is having issues with Google Stock GApps. Everything works fine for me on PA 4.2 BETA.
[General Paranoid Android Discussion] defffizz:
Can someone help me out? I flashed Google stock package after flashing newest pa beta on my nexus 5 and I don't have Google dialer. How can I get it?

Bright Red Nexus 5, PA + franco
[General Paranoid Android Discussion] osm0sis:
Same. No issues on CarbonROM nightlies using Stock here. I even manually installed the apk (to /system) and 2 libs to my MX MediaBox set-top device running JB4.2.2 and it works great.
[General Paranoid Android Discussion] shoeprano27:
you woke up with a gerbil in your ass this morning?
[General Paranoid Android Discussion] Whosdaman:
No issues on cm11 nightly.
[General Paranoid Android Discussion] iXNyNe:
Hopefully the authors of these various firmware (Roms) will take the hint and include the libraries themselves.

Side note:

For me on my lg g2 using cm11 3/21 nightly and your stock package 3/21 (first release, no .pa_gapps file) the 3.0 keyboard works fine, but that's likely because my aosp keyboard (cm keyboard) is removed.

When I had your stock 3/18 pack installed with the 2.0 keyboard included I was able to update to the 3.0 keyboard from the play store.

I really like the Google keyboard and have no use for the firmware included keyboard, so here's a vote for keeping the Google keyboard in the pack.

It may be wise to pack the 2.0 keyboard/libs and let people update through the play store if they want 3.0.

Updating though the play store doesn't update the libs in /system right? Because the play store apps include the libs internally in the apk?
[General Paranoid Android Discussion] apatal:
Same here. Google keyboard working fine for rastakat for mako. I did a clean install though, so not sure if that matters or not.
[General Paranoid Android Discussion] chewdaniel:
[MENTION=2777334]TKruzze[/MENTION]: will u be uploading 3.0 as a separate download? i think i'll be expecting FCs for those of us who already flashed working 3.0 on the next gapps version... tks buddy :D
[General Paranoid Android Discussion] MWisBest:
I'm guessing that the crashing with the keyboard is happening only to people with gesture typing enabled.

This was a real pain for me last night, as I wasn't even able to decrypt my phone then to boot it up.

The only differences between the stock straight from AOSP keyboard and what's in my ROM is these:

https://github.com/MWisBest/android...mmit/33298f05ca26fd0e2a9ed766a3bafc144685ca56

https://github.com/MWisBest/android...mmit/e2a565092edc889061e38dfddc806581e0b190f6

https://github.com/MWisBest/android_vendor_omni/commit/ac0e0b37930dad1f6fd0adc5628b3394eaa51569

I also already have the gesture typing lib in there out-of-the-box, as it wasn't included with these GApps for a while:

https://github.com/MWisBest/android_vendor_omni/commit/5ca357f18c644a91af4c41c4699463120aea857b
[General Paranoid Android Discussion] WoodburyMan:
FC's for AOSP Keyboard in latest SlimRom custom built this morning. on hammerhead for 20140321. Downloading 21a now... flashing that.

*EDIT*

Flashing 21a over 21 fixed it for me no problems.
[General Paranoid Android Discussion] maverick_hunter:
I was getting FC's for Google Keyboard when dirty flashing yesterday's Gapps, but after a clean wipe and flash of the entire ROM, no more FC's. If you want the newest Google Keyboard, that seems to be the surefire way to get it working.

On latest PA beta, by the way.
[General Paranoid Android Discussion] andresee:
Clean flashed Purity and PAGapps with the Google Keyboard 3.0 and seems to be working fine now. Restoring apps now with titanium...
[General Paranoid Android Discussion] iXNyNe:
To anyone reporting that they had fc issues (or any issues) please include your pa_gapps.log

- or -

At least specify which pack (stock/full/mini/micro) that you're using (and the release date)

And as always include what firmware you're using (and the release date or version number)

This makes is much easier to track/fix problems
[General Paranoid Android Discussion] Summer Son:
I have FCs. Mini modular package from 21-03-2014, OmniROM 21-03-2014 nightly (also todays). Tried clear apps data, didn't work, tried replace apk with previous version, didn't work, tried disable Keyboard app at all, almost killed the launcher. Dirty install. Clean install is not an option, too many things to restore...
[General Paranoid Android Discussion] Frankie_Ho:
Im currently using lg optimus g pro with vanir

I flash the google stock pack but i dun hv photosphere choice in the camera
[General Paranoid Android Discussion] Wh1t3Rose:
[MENTION=2777334]TKruzze[/MENTION] The mediafire link for the 4.3 Mini Modular package points to non existent folder (Got removed).
[General Paranoid Android Discussion] Whosdaman:
Because its not a nexus device
[General Paranoid Android Discussion] Dragonhide32:
No you?
[General Paranoid Android Discussion] jorceshaman:
I did, and it felt AMAZING!
[General Paranoid Android Discussion] Eun-Hjzjined:
So... You like em small and hairy, eh?
[General Paranoid Android Discussion] sledge3n8:
I really, really hope that all of these changes that Cyanogenmod have been making by veering away from Google and AOSP are for the better good. I have been thinking of abandoning CM and moving to AOSP or AOKP because the number of overall issues people are having with kernels and Gapps are staggering.

I feel for you [MENTION=2777334]TKruzze[/MENTION]! CM has been keeping you very busy and I appreciate your dedication! :good:

---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------

ROTFLMFAO!

---------- Post added at 10:59 AM ---------- Previous post was at 10:53 AM ----------

+1

Clean wipe all the way! I haven't experienced any of the issues people have been having and I think it is because I have been doing clean flashes. Yes, it can be a pain in the ass and time consuming, but it is far less of a pain than debugging and fixing dirty flash issues IMO. :good:

---------- Post added at 11:02 AM ---------- Previous post was at 10:59 AM ----------

+1

Clean install...no issues

---------- Post added at 11:06 AM ---------- Previous post was at 11:02 AM ----------

"Clean install is not an option, too many things to restore" <== You are experiencing the problem of dirty flashes bro. You will have to take the long way to recovery then. Restoring all your stuff takes how long versus trying to fix your problems??? An hour or two to restore your stuff compared to...several hours or days to fix bugs? :good:

Peace!

---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------

+1

Clean flash...no issues!

---------- Post added at 11:09 AM ---------- Previous post was at 11:07 AM ----------

You guys seeing the trend that I am trying to show?
[General Paranoid Android Discussion] osm0sis:
This. Every now and then it's good to do. Not too difficult to cut your time in half either; I use Titanium Backup and have selectively chosen certain system apps, all user apps and a few things like sms history, desktop and accounts. I then batch redo all my current backups, clean wipe, batch restore, and then all I've got to do is set up some system Settings and I'm done.
[General Paranoid Android Discussion] apatal:
^ Same process for me like every 2 to 3 weeks or so. It's a good practice especially after a lot of dirty flashing in between clean ones.
[General Paranoid Android Discussion] MUTATED_FORM:
Yes
[General Paranoid Android Discussion] Noob911:
Evening folks .. One problem.. I am running xjparadroid have been since I got my nexus 5 .. Recently done update micro gapps via paranoid ota and it keeps telling me there is an update .. Please advise .. Also photo underneath to show .. Thanks
[General Paranoid Android Discussion] Noob911:
Please help
[General Paranoid Android Discussion] hlxanthus:
Because that is a new version. He released a bug fix update the same day, hence the "a" tag in the file name.

Sent from my Galaxy S4
[General Paranoid Android Discussion] dayv2005:
I'm using hangouts 2.0.303 from the march 18th release. I installed the first option (stock) for 4.4. I'm running the Lat eat cm 11 nightly.

I was wondering if others are having the following issues or know how to fix.

1.) MMS sometimes comes through instantly and sometimes I get it 24 hours later. L

2.) When you share an image from gallery with hangouts it looks all good with the preview except when the recipient gets the image it's all distorted. But if you share from within the hangout app it seems fine. Also if you take a photo to share with in app it distorts as well.

3.) Group messages don't come through as a group but a single message. Then if anyone replies to the group message it comes through as a single message as if they were messaging me singly and not the group.
[General Paranoid Android Discussion] Noob911:
Yes I figured that out .. I have already installed the A one twice .. Still saying same thing ...
[General Paranoid Android Discussion] FReaKRaNT:
Is because he released it with the "a" in it but it still has the original signature so updater thinks it is the same update.

Cheers, FReaKRaNT