yashsingh1/xdaforums huggingface dataset:
[General Paranoid Android Discussion] TheDannemand:
[MENTION=2777334]TKruzze[/MENTION]: A weekly Friday update is plenty fine, if you ask me. Seriously, whatever makes your life workable. You're doing amazing work, and the last thing we want is for you to get tired of it.
[General Paranoid Android Discussion] yanner2012:
Thanks you very much [emoji106]
[General Paranoid Android Discussion] chewdaniel:
agreed to weekly update too. will make ur life easier and also for those with ORD :p
[General Paranoid Android Discussion] apatal:
Weekly update seems like a good idea. Just get rid of the "0-day" qualifier in the thread title so people would know that policies have changed regarding releases. :)
[General Paranoid Android Discussion] svnhvn:
Couldn't agree more.
[General Paranoid Android Discussion] plageran:
Safely remove apps

I've installed the full package, but now I want to get rid of some like: "Play Music" "Play Games", as these files don't work in my country, also want to change the google now launcher.:o
[General Paranoid Android Discussion] nexs5:
Hey guys

Im a newbie to the android scene but have gone through the whole upgrading process etc etc.

Im amazed at the amount of talented guys on this forum, my hat goes off to all of you.

Just updated to the following on my nexus 5

Paranoid Android ROM 4.2beta5

Franco kernel #47

Recovery CWM

Im not sure if this is an issue or im just missing it but i dont have any settings to customize the pie control or toolbars ? (this was the same with the 4.2beta4 release aswell)

Im also getting this translucent answer option on the dialer, so not too sure if this is normal in the new update as i had the previous PA rom installed and this wasn't coming up.

I performed a clean flash, the whole device was wiped.

Cleaned delvik cache twice and shutdown and restart twice, same thing.

Any info would be good, if it's a current bug then all sweet as im not sure if i messed something up.
[General Paranoid Android Discussion] hanschke:
new Hangout

https://mega.co.nz/#!tFVGHJiC!mbGsV4JPfTOjQYX5WTccqSylWMSayLmLdQKY3FyAMi0
[General Paranoid Android Discussion] SpasilliumNexus:
Not sure what the .01 version bump from 1.2.563.31 is about but here's Google Drive 1.2.563.32
[General Paranoid Android Discussion] Braxos:
Anyone else getting fc when trying to open settings of the Google camera?

Omni ROM N7000
[General Paranoid Android Discussion] :
First of all, welcome!

To answer you:

1. PA Pie Control is no longer customizable, meaning no settings exposed which you can tweak. It's designed that way by PA Developers. You may read their previous posts about that.

2. The semi-transparency of the incoming call UI is a new feature in PA 4.2 Beta 5. Please read the changelog.

Lastly, your questions were ROM-related, not GApps related, so next time post these questions in the proper forum/appropriate thread.

Enjoy your phone. Cheers!

---------- Post added at 04:19 PM ---------- Previous post was at 04:15 PM ----------

Go to root/system/app and delete the apps you don't like. Or just disable them from settings and they will no longer appear in your app drawer.

If you want to change your launcher, then just install another launcher of your choice.
[General Paranoid Android Discussion] ahmed dzico:
I have a problem , when update any app from play store it give me error ??

Sent from my Nexus 5 using Tabatalk
[General Paranoid Android Discussion] Quality0528:
The same:crying:
[General Paranoid Android Discussion] psydex:
I've just installed the latest Gapps 21/04 including the Google Camera moddule. Everything works fine but Google Play still shows an install button (instead of "installed")... I'm a lil bit confused. Will i still get an update of the camera if available?
[General Paranoid Android Discussion] crazycaveman:
Just out of curiosity, how do you generate the GApps zip? Do you manually update the scripts and apps, or do you have a script that generates it all for you?

Also, I was poking around your install-prep.sh script and came across this:

echo -n -e "installing_gapps_type=$installing_gapps_type\ntotal_system_size_kb=" >> /tmp/gapps.prop

# I know it's not pretty, but it does get the job done
df -k system | grep '% /' | tr -cs '0-9' ' ' | sed 's/^[ \t]*//;s/[ \t]*$//' | sed 's/\(.*\) /\1+sys_pct=/' | sed 's/\(.*\) /\1+free_system_size_kb=/' | sed 's/\(.*\) /\1+used_system_size_kb=/' | sed 's/+/\n/g' | sed '/sys_pct/d' >> /tmp/gapps.prop

If you wanted to, you could change it to this to get it all on one line and in one sed call:

echo "installing_gapps_type=$installing_gapps_type" >> /tmp/gapps.prop

# Still might not be pretty, but it works
df -k system | grep '% /' | tr -cs '0-9' ' ' | sed 's/^[ \t]*\([^ \t]*\)[ \t]\+\([^ \t]*\)[ \t]\+\([^ \t]*\)[ \t]\+[0-9]\{1,3\}[ \t]*$/total_system_size_kb=\1\nused_system_size_kb=\2\nfree_system_size_kb=\3\n/' >> /tmp/gapps.prop
[General Paranoid Android Discussion] claytonjn:
[MENTION=2777334]TKruzze[/MENTION]

Is there a specific reason that Google Search (Velvet.apk) is placed into /system/priv-app rather than /system/app? Is it just because that's where it's located on stock Nexus devices?

The reason I ask is because on my S4, when it's in /system/priv-app hotword detection does not work. As soon as I move it to /system/app (and reboot) it works. Curiously, on my Note 10.1, with the same ROM, it works in /system/priv-app.

I know apps in priv-app are considered to be more "systemy" (https://android.googlesource.com/platform/frameworks/base/+/ccbf84f) then apps in /system/app but do you know if Google Search needs the higher level of privileges?

I can keep moving it manually, but I also have to update the scripts so that when I flash nightlies it doesn't get removed. If it could be addressed directly in your packages not only would it make things a little bit easier for me, but it may fix the issue for others.

Thanks!
[General Paranoid Android Discussion] albertusac:
don't priv-app have a bigger permission to do something compared to /app ? :confused:
[General Paranoid Android Discussion] pesche80:
camera not working

Unfortunately I have similar problems too.

I'm running CM11 M5 on a i9300. Everythings fine with following GAPPS:

pa_gapps-modular-micro-4.4.2-20140123-signed.zip

pa_photosphere-module-4.4.2-20140123-signed.zip

I've installed(updated) Googles Camera app via Play Store and was able to take pictures. But I couldn't open the settings, because of a FC.

So I've decided to try a current nightly (cm-11-20140421-NIGHTLY-i9300.zip)

Now the settings were working and I was able to take pictures. But not for really long. After one day I was able to take only one picture. Then the camera preview froze. Only a restart helped to reanimate the camera.

So I've decided to do a clean install. Wiped system, data, dalvik and cache partitions.

Installed the newest nightly, newest gapps and camera module. Settings page is working. But after one shot, the camera preview freezes and I have to reboot.

Well something is really buggy with the i9300 camera.

On a Galaxy Nexus with CM11 everything is working perfectly! Even the camera app came as an update via the play store. Of course the dual-core cpu is much slower while rendering Photospheres, but it is working flawlessly.

So. Does anybody has an working i9300 CM11 installation? Could you please provide the exact version numbers and installations procedures?

Update 1:

Allright. Seams like I found a fix.

Somebody in the following thread wrote, that Samsungs used different camera modules for S3's.

(http://www.android-hilfe.de/aosp-ao...300-4-4-2-cyanogenmod-11-official-builds.html)

I've installed the provided Camera-Fix zip (http://xdaforums.com/attachment.php?attachmentid=2662409&d=1396356535), which solved the camera preview freeze problem.

So I've reverted back to my CM11 M5 backup. Updated to CM11 Nightly from 2014-04-21 (with M5 I can't open the settings!), the current micro GAPPS package and cameramodule from this thread. Afterwards installed the fix for the camera libraries (OmniRom-Fixed_camera_Lib_V4.zip).

Now Google Camera Apps seams to be working.

I hope I won't get any other problems.
[General Paranoid Android Discussion] hanschke:
Hangouts (replaces Talk) v2.1.076 (1133037-30)

http://www.tusfiles.net/i8yg4tt3b8yn
[General Paranoid Android Discussion] xanthrax:
Please delete this crap, full of adds server and third party apps for downloading

Have you ever heard about a decent cloud storage that you can use it if you want to share and not to spam?
[General Paranoid Android Discussion] michierusama:
Hi. Good morning everyone.

When I flash the stock package on cm11 04/22 nightly Galaxy nexus. At the end there's a note: insufficient space to install Google chrome. Download from play store.
[General Paranoid Android Discussion] osm0sis:
Do what it says. ;)
[General Paranoid Android Discussion] michierusama:
I did. So that means I wont get it to install over the AOSP browser anymore?
[General Paranoid Android Discussion] osm0sis:
Nope. CM takes up too much space in the system partition. You could still make it work if you switch to a ROM that isn't so heavy.
[General Paranoid Android Discussion] michierusama:
Thanks for answering. Rom size is the thing.
[General Paranoid Android Discussion] Dwillian:
That means the system partition isn't large enough to hold the entire PA GApps pkg. So, chrome is not installed so that the rest of the pkg can be installed.

I'm not familiar with the Galaxy Nexus, but on my Droid RAZR I can increase the system partition size when I create my ROM slot (using SafeStrap recovery). The default size is 700 MB. I usually increase that to 1 GB and the full and stock PA GApps pkgs fit fine with room to spare (in case the pkgs grows, and they most likely will over time).

---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------

Yes.

And chrome is now installed in the user partition instead of the system partition. Should be OK, but you now have less user space available for other apps and data.

If you are using SafeStrap you can boot into recovery and click on your active ROM slot (under boot options) and see how much space is used and how much space is available in the system, user, and cache partitions.
[General Paranoid Android Discussion] marcinq24:
freezes all the time I google the camera (Tamasek v70, pa gapps 4.4, boefla kernel)
[General Paranoid Android Discussion] JekaPinsk:
Camera app is FC after taping settings.

How can i install Gallery and Faceunlock?

I have .forcegallery and .forcefaceunlock files on my sdcard, but when i install the gapps, i have got this in the log file

install.faceunlock=false
install.gallery=false
[General Paranoid Android Discussion] TDSJR:
Delete
[General Paranoid Android Discussion] Daekin:
just uncheck use download manager and click direct download link :p
[General Paranoid Android Discussion] marcinq24:
what to do with suspending the google still camera?

how to fix it?

I'm on tamasek v70 and kernel boefla
[General Paranoid Android Discussion] xanthrax:
You can't be serious, are you part of this...?

Sent from my Darkside of Xperia Z1
[General Paranoid Android Discussion] Daekin:
hmmm...too dymamic page for a mobile phone. I did it on my SP2 inside IE11 and worked OK :p
[General Paranoid Android Discussion] leungclj:
I have just flashed the APRIL 21, 2014 - 20140421 build, the phone cannot connect to the camera. Did a clean flash of the ROM and still not working at all.

Device: OPPO Find 5

ROM: Omni Rom
[General Paranoid Android Discussion] tennispro820:
PLEASE Fix Camera!

Having problems with the camera, too. Please fix ASAP! In the Google camera the photosphere, panorama and lens blur are all not working. PLEASE FIX!!! (like this post if you are having a similar problem so it can be fixed as soon as possible).
[General Paranoid Android Discussion] PiggySmalls:
1: This is not a good way to accomplish things here.

2: This is a Google app, and complaining about functionality problems needs to go to Google, not [MENTION=2777334]TKruzze[/MENTION], as he does not make the apps,.
[General Paranoid Android Discussion] svnhvn:
Demanding are we?
[General Paranoid Android Discussion] tennispro820:
No..It is a request if it can be fixed as soon as possible. Sorry if it seemed demanding.
[General Paranoid Android Discussion] michierusama:
But he cannot fix those issues... He just collects the apps into packages for us to flash. Mine is working on Galaxy Nexus.
[General Paranoid Android Discussion] tennispro820:
Help?!

Is there a way it can be fixed? Anyone?
[General Paranoid Android Discussion] apatal:
What's your device and setup?
[General Paranoid Android Discussion] tennispro820:
I am running Liquidsmooth Kitkat (4.4.2) 4-21-2014 on galaxy s3 tmobile. I have installed the latest GAPPS 4-21-2014. It worked before but I was trying to flash a custom google dialer then it stopped working. I had a nandroid backup but after restoring, the google camera features weren't working.
[General Paranoid Android Discussion] Emersooh:
I'm thinking of going back to Stock ROM. I'll need to delete the Gapps?

And if I totally wipe the system can even flashing stock ROM?

:confused:

Sorry for the English
[General Paranoid Android Discussion] jorceshaman:
You should be able to wipe the system partition which will delete the custom ROM and GAPPs.
[General Paranoid Android Discussion] psydex:
Uhmmm, anyone?
[General Paranoid Android Discussion] leungclj:
I am having issues with camera too...
[General Paranoid Android Discussion] hanschke:
Quickoffice v6.1.183 by Google

http://ul.to/6731hr4w
[General Paranoid Android Discussion] dannyella:
I flashed Google camera module. The drawer icon didn't change to the new one. It's still old one even though the ui is the new one. Not a big deal but is it normal??
[General Paranoid Android Discussion] FDisk80:
Try clearing the cache.
[General Paranoid Android Discussion] iceolate:
It looks like Gmail is messed up on mine. It's missing the message controls, archive, delete etc. I guess I'll deal with it until another update is available.

On a side note, if I didn't reflash my rom, but wanted to downgrade from the stock package to say the micro one, how would you do that? I don't use half those apps so I think next time around, I'm just gonna install the micro and add on what I need from the play store.
[General Paranoid Android Discussion] Dwillian:
There are instructions in the original post under FAQs (actually post #3).
[General Paranoid Android Discussion] TKruzze:
Thanks for the suggestion. I'll test it out and maybe even include in next update. As to how I generate the GApps zips, I've actually written a couple of apps to automate the process and avoid 'typo' errors. The first app prepares the addon.d script, gapps-list.txt, and updates g.prop with current values. The second app actually builds, names, and signs the zip and also generates an .md5. Saves me 15-20 minutes per build and eliminates most common errors.

You'd need to ask Google this question as I only follow the standards and practices that they employ.

I coudln't find any details on this fix, but if it works, why wouldn't the ROM builder include it in the ROM? I don't see that I'll ever start supporting custom hardware libraries for anything but Nexus devices.

First of all, there is no such option as .forcefaceunlock. Either your device supports it or it doesn't. I think it's supposed to work on most devices with a front facing camera.

Secondly, to use the .forcegallery option you also need to type (inside the .forcegallery text file) the name of the Nexus device for which you want the gallery installed. Current options are "hammerhead, Flo, Deb, Manta, Mako, or Tuna".
[General Paranoid Android Discussion] MikeRL100:
Another Hangouts update came out.
[General Paranoid Android Discussion] TKruzze:
Google Camera Issues

I know that several of you have reported problems with the new Google Camera. While Google does say that this new version is for KitKat devices, I don't think they meant to include every 4.4.x ROM on XDA. I'm guessing that they meant this to include devices running stock or factory versions of Android 4.4.x.

While many legacy devices are able to run KitKat with a custom ROM, many of these ROM's do not have updated KitKat drivers and/or kernels. Instead, they're using modded, patched, or hacked versions of older drivers and kernels. IMHO, it's these situations that lead to problems and/or incompatibilities with Google's new camera app. This means that there's NOTHING I can do to fix this problem for you. Your only likely option is to NOT use the new Google Camera on your device.

To help make this easier for users who prefer to continue using our Google Stock GApps package without the Google Camera, I will be adding a new advanced option in the next update to bypass the installation of Google Camera on your device. All you'll need to do is add a file in /sdcard called . forcenocamera and the new Google Camera will not be installed on your device. I'll include further details when the update is announced, most likely in the next 24-36 hours. In the meantime, you can use the Full Modular package which does not include the new camera.
[General Paranoid Android Discussion] JekaPinsk:
Ok, installed Gallery, everything working good.

My phone have front camera, and on some roms faceunlock working good.
[General Paranoid Android Discussion] bill.allrobots.org:
In addition to forcing no camera, can we have a flag in .gapps-stock to keep the original camera? Thanks!
[General Paranoid Android Discussion] MikeRL100:
I like that idea. Use my custom ROM camera and the Google camera. If possible.
[General Paranoid Android Discussion] TKruzze:
Not at this time. Past history has shown problems when multiple cameras are installed in the system partition. Since the new Google Camera overwrites a couple shareable libraries (*.so) included in most ROM's, my concern remains.

If you want to keep both, you're best installing a Modular GApps package and then installing Google Camera from the Play Store.

Sent from my ΠΣΧỤŞ 7 ²°¹³ tablet
[General Paranoid Android Discussion] MikeRL100:
Oh I sort of felt that might be an issue… After I posted LOL.
[General Paranoid Android Discussion] dannyella:
Didn't work
[General Paranoid Android Discussion] hanschke:
YouTube v5.6.35

http://ul.to/8hns7e3l
[General Paranoid Android Discussion] oubeichen:
Google Latin ime kept crashing after installing mini gapps of 04/21.

Finally I found it is a lib issue ,libjni_unbundled_latinimegoogle.so is exactly the same as libjni_latinime.so in that package.(of course they are different modules)

You shouldn't put the libjni_latinime.so and the libjni_unbundled_latinimegoogle.so in it as the mini package doesn't contain the Google ime.

And BTW my Google ime locates at /system/app/GoogleIME.apk , I don't know whether it is a ROM specific, but you can add it to the delete list of keyboard add-on.

Thanks!
[General Paranoid Android Discussion] Dron_GTR:
why your packages of gapps don't include "GoogleCalendarSyncAdapter.apk"?
[General Paranoid Android Discussion] G U C C I:
I also received a Hangouts update!
[General Paranoid Android Discussion] hlxanthus:
The sync adapter apps are for syncing aosp (like browser and calendar) apps with Google sync. They are not needed for actual play store apps.

They allow play store like functionality from the open source versions of the apps
[General Paranoid Android Discussion] oubeichen:
but the package deletes it
[General Paranoid Android Discussion] TKruzze:
Please explain further....

I don't include Google Keyboard in Mini GApps. How is it then crashing? Are you referring to the version you installed from the Play Store?

You tell me 'I shouldn't...'. What is that based on? Your personal opinion or do you have a resource you can cite?

Every single GApps package out there has to include the Google keyboard library to insure that the stock/AOSP keyboards that come with most ROM's have full functionality, such as swipe support. Based on an extensive analysis by [MENTION=4509940]0s1ride[/MENTION] (see this post for the major details) where he analyzed the keyboard library requirements of the major stock/AOSP keyboards, we added the supported libraries - over 4 months ago.

However, despite the condescending tone of your message, you have got me to thinking that it might be time to remove libjni_unbundled_latinimegoogle.so and see if that helps with some of the keyboard issues that have cropped up since Google Keyboard 3.0 came out. I'll make that change with the update later today.

The reason I don't include it is that it's ONLY required to support the stock/AOSP Calendar app. It's not required for the Google Calendar app. Since all of my GApps packages include the Google Calendar app and remove the stock/AOSP calendar, it's not required.

The reason I delete it is because I'm looking for every extra byte of available system partition space to help users with small system partitions. Since the app serves no purpose if I allowed it to remain, I simply delete it.
[General Paranoid Android Discussion] gelberg3211:
Thanks
[General Paranoid Android Discussion] oubeichen:
Sorry for my bad English...

I just find that libjni_unbundled_latinimegoogle.so in 4/21 mini package is wrong...It is exactly a renamed version of libjni_latinime.so.. You can check the hash of those two files.

And the file in keyboard addon package is correct..

As for the calendar sync ... I don't know if it is just my ROM issue, but I cannot sync google calendar without this apk..
[General Paranoid Android Discussion] TKruzze:
I know it's a renamed version of libjni_latinime.so. I'm the guy who put it there, so I should know. :laugh: However, if you read the post I linked to, you might understand why the decision was made to do this.

The difficult part of making an apps package like this is I have to make it work across all devices and ROM's. That's not easy when the largest ROM developer (CyanogenMod) violates common AOSP standards and practices that almost all other developers adhere to.

The file in the Keyboard addon is different because the addon actually completely removes the stock/AOSP keyboard. Once that's done, I no longer have to be concerned with trying to support all the various stock keyboard variations and requirements and can do things as Google intended.

Also, as I mentioned, GoogleCalendarSyncAdapter.apk has nothing to do with Google Calendar. It's only purpose is to support the AOSP calendar. Something else must be happening on your device. A clean flash would probably fix all your problems.
[General Paranoid Android Discussion] Zorrich:
Any one have issues with keyboard not working (keyboard pops up but typing doesn't work). I've had this issue since the new keyboard made it's way into the GAPPS (not sure if that is related or just coincidence). Tried clean installs on multiple ROMS, including PA, Purity, and Rasta. Tried stock gapp package, and the full modular package. Have run stock settings with no additional apps installed after each clean flash and eventually the keyboard will "freeze". I have to force close app and then re-open.

Can't figure it out, any help that could be offered would be appreciated. Thanks.
[General Paranoid Android Discussion] oubeichen:
And there is no evidence that libjni_unbundled_latinimegoogle.so is exactly the same as libjni_latinime.so..

The things is it won't work and causes the GoogleIME(I think it is a stock AOSP version. Prebuilt, not compiled) FC.

Remove it from the package should be fine.

I am sorry that my previous opinion about GoogleCalendarSyncAdapter.apk is wrong..

It does nothing with Google Calendar. I have the issue is because I replaced the calendar back to the one in the ROM.
[General Paranoid Android Discussion] Dron_GTR:
But without it my calendar not synced with google account, what wrong? On any rom CM/Omni/MIIUI
[General Paranoid Android Discussion] TKruzze:
What is gacc?

Sent from my ΠΣΧỤŞ 7 ²°¹³ tablet
[General Paranoid Android Discussion] TMYINC:
I think he means Google account.