[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices

Search This thread
By:
Advanced…
M

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,356
The Hague
github.com
Xiaomi Mi 11
Samsung Galaxy Watch 4
mybeshoo said:
When i installed the Stock one on
http://xdaforums.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864

all aps such time,keyboard return FC , so i deside to install the nano version .
now the Keyboard FC with this catlog error report

the FC of AOSP Here you go :
it happend each 3 seconds!
Click to expand...
Click to collapse
It appears because AOSP keyboard is incompatible with the newest Google Keyboard libs. So we decided to drop it (the post just before yours) because of the issue becoming more common now. So tomorrow's build (14 Oct) should not give you this trouble anymore.

I am still interested in the FCs you got when installing stock. Do you have any logcats of those?

PS: The debug logs of the installation you can find in the same location where you had the installer zip.
 
Last edited:
M

mybeshoo

Senior Member
Jul 18, 2011
145
8
MastahF said:
It appears because AOSP keyboard is incompatible with the newest Google Keyboard libs. So we decided to drop it (the post just before yours) because of the issue becoming more common now. So tomorrow's build (14 Oct) should not give you this trouble anymore.

I am still interested in the FCs you got when installing stock. Do you have any logcats of those?
Click to expand...
Click to collapse

Thank God not only me :)

Regarding the Stock , well no i dont but i will be more than happy to make it for you , how can i uninstall the Nano and install the stock but please dont tell me i need to format my device :):D
 
androcraze

androcraze

Senior Member
Jan 11, 2013
2,254
1,661
MastahF said:
It appears because AOSP keyboard is incompatible with the newest Google Keyboard libs. So we decided to drop it (the post just before yours) because of the issue becoming more common now. So tomorrow's build (14 Oct) should not give you this trouble anymore.

I am still interested in the FCs you got when installing stock. Do you have any logcats of those?
Click to expand...
Click to collapse

If the ROM doesn't have the swipe feature enabled, you just can't add the library:

http://xdaforums.com/nexus-4/general/guide-how-to-enable-googles-gesture-t2012628

Or are you talking about something else?

If not, will older versions of the library still work? I think most users will probably care about usability rather than being current.... But then again (if that were the case) , you'd only have to build GApps ONCE for each Android version....
 
Last edited:
K

kchaisu

Senior Member
Jan 27, 2014
896
738
Bangkok
Xiaomi Mi Pad 5
MastahF said:
Another addendum, we decided to drop the 'keybdlib' that added Swype capabilities to the AOSP keyboard, because it gave issues to quite a lot of users. Instead we will drop the 'clean install' requirement from the Google Keyboard installs, hoping that it won't pose any unexpected issues by now anymore (like it could give in the past).
Click to expand...
Click to collapse
Thanks MastahF for your kind info. I also have an issue on Keyboard stop working when I installed Open gapps 20151013 Pico 511.So it ended up to going no where without keyboard. I have a debug log file, but I could not find a way to upload. Thank you very much for your kind contribution.

Sent from my Desire S using Tapatalk
 
LordNerevar

LordNerevar

Senior Member
Feb 21, 2012
353
657
Google Pixel 3a XL
MastahF said:
Are you sure that -1 is necessary? I tested the 4.4 installs to /data/app/ quite some time ago and without -1 it worked properly on clean installs :-/
Could you maybe upload your installation debug log?
Click to expand...
Click to collapse
You're right. It does appear to work with a clean install. Assuming upgrades to these 3 apps work from the play store, this should be fine if you're only targeting clean installs. I'm not really sure what happened with my dirty install, but I was able to recover so no big deal.

Good luck with the project. It seems very well documented and professional!
 
  • Like
Reactions: yungyung888
I

imcrazyz

Senior Member
Jan 29, 2015
72
6
Calendar sync has stopped working on the 13th build pico gapps, instead of popup of error, by noticing my calendar event doesn't appear on my calendar widget. Previous version was totally fine.
Anyone having the same issue?
 
M

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,356
The Hague
github.com
Xiaomi Mi 11
Samsung Galaxy Watch 4
androcraze said:
If the ROM doesn't have the swipe feature enabled, you just can't add the library:

http://xdaforums.com/nexus-4/general/guide-how-to-enable-googles-gesture-t2012628

Or are you talking about something else?

If not, will older versions of the library still work? I think most users will probably care about usability rather than being current.... But then again (if that were the case) , you'd only have to build GApps ONCE for each Android version....
Click to expand...
Click to collapse
Yup, we are exactly talking about that. And it used to work as described in that post. But somehow, it did break recently in e.g. Cyanogenmod. And while we we hardly received any feedback about problems before, it became suddenly much more frequent. @MNBooZe did do some testing for us on his device with current ROMs and the various library versions, and the conclusion was that either the libs made the keyboard crash, or it did not crash but swype would not work. The sum of all this information did decide us to drop it.
Instead, we will now enforce no clean installs for Google Keyboard anymore. Because a year ago when Keyboard was still new, there were many problems with it on dirty installations. But Google is now several iterations further with development of Keyboard, so I am willing to take the gamble that those problems could be resolved by now. We will see how it behaves, if it still gives trouble on dirty installations, we might choose to enforce clean installations again.

imcrazyz said:
Calendar sync has stopped working on the 13th build pico gapps, instead of popup of error, by noticing my calendar event doesn't appear on my calendar widget. Previous version was totally fine.
Anyone having the same issue?
Click to expand...
Click to collapse
Calsync has not been updated for a month: https://github.com/opengapps/all/tree/master/app/com.google.android.syncadapters.calendar/15/nodpi
Maybe an issue on Google's side or on your ROM?
Otherwise please try to capture a logcat if any errors related to this problem appear in it.
 
ADB100

ADB100

Senior Member
Nov 3, 2006
1,495
119
Hangouts 5.0?

I have been offered Hangouts 5.0.104885319 from the Playstore and can see this was released on 12th October so assumed this would already be in the GApps for Android 5.1.
It appears version 4.2.102354210 is still the current version. Will this get updated soon or is it being left out as its 'targeted' at Android 6.0?

Andy
 
Dkadr1

Dkadr1

Senior Member
May 4, 2011
189
49
Madrid
Facelock gives FC when trying to set it in 5.1

Are you including the Marshmallow files? Because in app version it says 6.0
 
I

imcrazyz

Senior Member
Jan 29, 2015
72
6
MastahF said:
Calsync has not been updated for a month: https://github.com/opengapps/all/tree/master/app/com.google.android.syncadapters.calendar/15/nodpi
Maybe an issue on Google's side or on your ROM?
Otherwise please try to capture a logcat if any errors related to this problem appear in it.
Click to expand...
Click to collapse

Not sure about it, but I do trust the work from cm team.
*I'm using the official cm12.1 nightly.
Btw, thanks for acknowledging.

EDIT: Is it possible to download the previous version of gapps? I really find the previous versions are more useful and stable.
 
Last edited:
M

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,356
The Hague
github.com
Xiaomi Mi 11
Samsung Galaxy Watch 4
ADB100 said:
I have been offered Hangouts 5.0.104885319 from the Playstore and can see this was released on 12th October so assumed this would already be in the GApps for Android 5.1.
It appears version 4.2.102354210 is still the current version. Will this get updated soon or is it being left out as its 'targeted' at Android 6.0?

Andy
Click to expand...
Click to collapse
Actually 5.0 is in the package since the 13th. I just have to update the version information script, since it cannot handle the situation where higher SDK versions are outdated compared to lower SDK versions. The package builder does pick the highest applicable version correctly, though. So you can be sure of it to be in the package :)

Dkadr1 said:
Facelock gives FC when trying to set it in 5.1

Are you including the Marshmallow files? Because in app version it says 6.0
Click to expand...
Click to collapse

We use the newest Facelock available, which is indeed version 6.0 but should be completely backward compatible. But it is known that Facelock is broken on *a lot* of devices. So did Facelock ever work for your before? If yes, could you give a logcat of the FC?

imcrazyz said:
Not sure about it, but I do trust the work from cm team.
*I'm using the official cm12.1 nightly.
Btw, thanks for acknowledging.

EDIT: Is it possible to download the previous version of gapps? I really find the previous versions are more useful and stable.
Click to expand...
Click to collapse
Yes, we also trust the work of CM. But our suspicion is just that binary compatibility is broken, so we better leave the original CM keyboard libs then in place, instead of destroying their functionality with the Google libs that were never officially meant to be used that way.
You can fetch the old packages from the Github releases pages. They are organized per CPU architecture and in respective repos you will find the releases.
Also, you can of course build your own package using the source and add the 'ingredients' you like and find most stable.
 
  • Like
Reactions: Ultramanoid
Dkadr1

Dkadr1

Senior Member
May 4, 2011
189
49
Madrid
MastahF said:
We use the newest Facelock available, which is indeed version 6.0 but should be completely backward compatible. But it is known that Facelock is broken on *a lot* of devices. So did Facelock ever work for your before? If yes, could you give a logcat of the FC?
Click to expand...
Click to collapse

Yes, it worked before. Now it does not even open the camera when trying to save a face.

Here is the logcat:

Code: 
java.lang.NoSuchMethodError: No virtual method checkSelfPermission(Ljava/lang/String;)I in class Landroid/app/Activity; or its super classes (declaration of 'android.app.Activity' appears in /system/framework/framework.jar)
	at com.android.facelock.SetupInstructionsScreen$SetupInstructionsFragment.onClick(SetupInstructionsScreen.java:121)
	at android.view.View.performClick(View.java:4789)
	at android.view.View$PerformClick.run(View.java:19881)
	at android.os.Handler.handleCallback(Handler.java:739)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:135)
	at android.app.ActivityThread.main(ActivityThread.java:5294)
	at java.lang.reflect.Method.invoke(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:372)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
 
C

chewdaniel

Senior Member
Feb 27, 2011
2,013
859
Kuala Lumpur
@MastahF

something in the latest gapps causing apps like google and fb messenger to FC (and few other random apps) at first i thought it was my CM nightly and i flashed a previous version and it was the same.... now i'm running 1010 with the latest 1410CM...

thanks :)

Code: 
E/msgr(:<default>):ACRA( 9785):         at android.view.View.layout(View.java:15686)
E/msgr(:<default>):ACRA( 9785):         at
E/AndroidRuntime( 9785): FATAL EXCEPTION: main
E/AndroidRuntime( 9785): Process: com.facebook.orca, PID: 9785
E/AndroidRuntime( 9785): com.facebook.widget.ba:
E/AndroidRuntime( 9785): View Hierarchy:
E/AndroidRuntime( 9785):   Class = OverlayLayout, ID = base_overlay_layout
E/AndroidRuntime( 9785):   Class = SoftInputDetectingLinearLayout
E/AndroidRuntime( 9785):   Class = NativeActionModeAwareLayout, ID = action_bar_activity_content
E/AndroidRuntime( 9785):   Class = ActionBarOverlayLayout, ID = decor_content_parent
E/AndroidRuntime( 9785):   Class = bn
E/AndroidRuntime( 9785):   Class = LinearLayout, ID = main_activity_container
E/AndroidRuntime( 9785):   Class = FrameLayout, ID = content
E/AndroidRuntime( 9785):   Class = LinearLayout
E/AndroidRuntime( 9785):   Class = DecorView
E/AndroidRuntime( 9785):   Original Throwable: java.lang.IllegalArgumentException: Unsupported ABI: null
E/AndroidRuntime( 9785):        at dalvik.system.VMRuntime.getInstructionSet(VMRuntime.java:324)
E/AndroidRuntime( 9785):        at dalvik.system.VMRuntime.is64BitAbi(VMRuntime.java:337)
E/AndroidRuntime( 9785):        at android.webkit.WebViewFactory.getWebViewNativeLibraryPaths(WebViewFactory.java:293)
E/AndroidRuntime( 9785):        at android.webkit.WebViewFactory.loadNativeLibrary(WebViewFactory.java:404)
E/AndroidRuntime( 9785):        at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:110)
E/AndroidRuntime( 9785):        at android.webkit.WebView.getFactory(WebView.java:2194)
E/AndroidRuntime( 9785):        at android.webkit.WebView.findAddress(WebView.java:1628)
E/AndroidRuntime( 9785):        at android.text.util.Linkify.gatherMapLinks(Linkify.java:469)
E/AndroidRuntime( 9785):        at android.text.util.Linkify.addLinks(Linkify.java:234)
E/AndroidRuntime( 9785):        at com.facebook.text.a.a(SafeLinkifier.java:31)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.cs.b(MessageItemView.java:1325)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.cs.k(MessageItemView.java:1292)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.cs.f(MessageItemView.java:1115)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.cs.setRowMessageItem(MessageItemView.java:932)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.ej.b(MessageListAdapter.java:594)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.ej.a(MessageListAdapter.java:494)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.ej.a(MessageListAdapter.java:53)
E/AndroidRuntime( 9785):        at com.facebook.widget.animatablelistview.d.getView(AnimatingListAdapter.java:389)
E/AndroidRuntime( 9785):        at android.widget.AbsListView.obtainView(AbsListView.java:2349)
E/AndroidRuntime( 9785):        at android.widget.ListView.makeAndAddView(ListView.java:1864)
E/AndroidRuntime( 9785):        at android.widget.ListView.fillUp(ListView.java:732)
E/AndroidRuntime( 9785):        at android.widget.ListView.layoutChildren(ListView.java:1654)
E/AndroidRuntime( 9785):        at com.facebook.widget.listview.BetterListView.layoutChildren(BetterListView.java:707)
E/AndroidRuntime( 9785):        at android.widget.AbsListView.onLayout(AbsListView.java:2153)
E/AndroidRuntime( 9785):        at com.facebook.widget.listview.BetterListView.onLayout(BetterListView.java:1000)
E/AndroidRuntime( 9785):        at com.facebook.orca.threadview.ThreadViewMessagesListView.onLayout(ThreadViewMessagesListView.java:161)
E/AndroidRuntime( 9785):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 9785):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 9785):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 9785):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 9785):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 9785):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 9785):        at com.facebook.widget.AdvancedVerticalLinearLayout.onLayout(AdvancedVerticalLinearLayout.java:219)
E/AndroidRuntime( 9785):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 9785):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 9785):        at com.facebook.widget.d.layoutChild(CustomViewGroup.java:179)
E/AndroidRuntime( 9785):        at com.facebook.widget.OverlayLayout.layoutChild(OverlayLayout.java:115)
E/AndroidRuntime( 9785):        at com.facebook.widget.d.onLayoutInternal(CustomViewGroup.java:127)
E/AndroidRuntime( 9785):        at com.facebook.widget.d.onLayout(CustomViewGroup.java:107)
E/AndroidRuntime( 9785):        at com.facebook.widget.OverlayLayout.onLayout(OverlayLayout.java:77)
E/AndroidRuntime( 9785):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 9785):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 9785):        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1703)
E/AndroidRuntime( 9785):        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1557)
E/AndroidRuntime( 9785):        at android.widget.LinearLayout.onLayout(LinearLayout.java:1466)
E/AndroidRuntime( 9785):        at com.facebook.widget.CustomLinearLayout.onLayout(CustomLinearLayout.java:290)
E/AndroidRuntime( 9785):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 9785):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 9785):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 9785):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 9785):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 9785):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 9785):        at android.support.v7.internal.widget.ActionBarOverlayLayout.onLayout(ActionBarOverlayLayout.java:499)
E/AndroidRuntime( 9785):        at android.view.View.lay
E/AndroidRuntime( 7962): FATAL EXCEPTION: main
E/AndroidRuntime( 7962): Process: com.google.android.apps.messaging, PID: 7962
E/AndroidRuntime( 7962): java.lang.IllegalArgumentException: Unsupported ABI: null
E/AndroidRuntime( 7962):        at dalvik.system.VMRuntime.getInstructionSet(VMRuntime.java:324)
E/AndroidRuntime( 7962):        at dalvik.system.VMRuntime.is64BitAbi(VMRuntime.java:337)
E/AndroidRuntime( 7962):        at android.webkit.WebViewFactory.getWebViewNativeLibraryPaths(WebViewFactory.java:293)
E/AndroidRuntime( 7962):        at android.webkit.WebViewFactory.loadNativeLibrary(WebViewFactory.java:404)
E/AndroidRuntime( 7962):        at android.webkit.WebViewFactory.getProvider(WebViewFactory.java:110)
E/AndroidRuntime( 7962):        at android.webkit.WebView.getFactory(WebView.java:2194)
E/AndroidRuntime( 7962):        at android.webkit.WebView.findAddress(WebView.java:1628)
E/AndroidRuntime( 7962):        at android.text.util.Linkify.gatherMapLinks(Linkify.java:469)
E/AndroidRuntime( 7962):        at android.text.util.Linkify.addLinks(Linkify.java:234)
E/AndroidRuntime( 7962):        at android.text.util.Linkify.addLinks(Linkify.java:273)
E/AndroidRuntime( 7962):        at com.google.android.apps.messaging.ui.conversation.ConversationMessageView.a(SourceFile:242)
E/AndroidRuntime( 7962):        at com.google.android.apps.messaging.ui.conversation.aj.a(SourceFile:26)
E/AndroidRuntime( 7962):        at com.google.android.apps.messaging.ui.C.onBindViewHolder(SourceFile:49)
E/AndroidRuntime( 7962):        at android.support.v7.widget.RecyclerView$Adapter.onBindViewHolder(SourceFile:5277)
E/AndroidRuntime( 7962):        at android.support.v7.widget.RecyclerView$Adapter.bindViewHolder(SourceFile:5310)
E/AndroidRuntime( 7962):        at android.support.v7.widget.RecyclerView$Recycler.getViewForPosition(SourceFile:4568)
E/AndroidRuntime( 7962):        at android.support.v7.widget.RecyclerView$Recycler.getViewForPosition(SourceFile:4461)
E/AndroidRuntime( 7962):        at android.support.v7.widget.LinearLayoutManager$LayoutState.next(SourceFile:1962)
E/AndroidRuntime( 7962):        at android.support.v7.widget.LinearLayoutManager.layoutChunk(SourceFile:1371)
E/AndroidRuntime( 7962):        at android.support.v7.widget.LinearLayoutManager.fill(SourceFile:1334)
E/AndroidRuntime( 7962):        at android.support.v7.widget.LinearLayoutManager.onLayoutChildren(SourceFile:538)
E/AndroidRuntime( 7962):        at android.support.v7.widget.RecyclerView.dispatchLayout(SourceFile:2847)
E/AndroidRuntime( 7962):        at android.support.v7.widget.RecyclerView.onLayout(SourceFile:3145)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1703)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1557)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.onLayout(LinearLayout.java:1466)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1703)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1557)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.onLayout(LinearLayout.java:1466)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.support.v7.internal.widget.ActionBarOverlayLayout.onLayout(SourceFile:437)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.layoutChildren(FrameLayout.java:579)
E/AndroidRuntime( 7962):        at android.widget.FrameLayout.onLayout(FrameLayout.java:514)
E/AndroidRuntime( 7962):        at android.view.View.layout(View.java:15686)
E/AndroidRuntime( 7962):        at android.view.ViewGroup.layout(ViewGroup.java:5039)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1703)
E/AndroidRuntime( 7962):        at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1557)
E/AndroidRuntime( 7962):        at android.widget.Lin
E/WifiStateMachine(  989): cancelDelayedScan -> 30
E/ThermalEngine(  274): [GPU_MON] ACTION: GPU - [GPU_MON] Setting GPU[0] to 450000000
E/WifiStateMachine(  989): WifiStateMachine L2Connected CMD_START_SCAN source -2 29, 30 -> obsolete
 
S

stephendt0

Senior Member
Apr 9, 2012
1,524
385
QLD, Australia
Hey guys, got a weird issue here. I'm using an AOSP based ROM called Androium 2.1.3 on the Lenovo K3 Note. It's a port from the Zapo 920.

If doesn't matter what ARM64 Gapps build I flash (even if I remove the Gapps manually), it will not go past a black screen with the status bar after boot. However, this only happens if I flash it directly after a clean install, or if I do a factory reset. If I let the ROM boot, then reboot and flash the Gapps, then it works fine (until the next factory reset). Any idea on what could be causing this and what could be done to avoid this? Reason I really want to be able to flash these Gapps is due to the fact that the stock Google Apps doesn't work with OK Google commands. Flashing these Gapps fixes this problem.

Advice would be appreciated :good: can submit logs and screenshots if needed.
 
Y

ym123

Guest
stephendt0 said:
Hey guys, got a weird issue here. I'm using an AOSP based ROM called Androium 2.1.3 on the Lenovo K3 Note. It's a port from the Zapo 920.

If doesn't matter what ARM64 Gapps build I flash (even if I remove the Gapps manually), it will not go past a black screen with the status bar after boot. However, this only happens if I flash it directly after a clean install, or if I do a factory reset. If I let the ROM boot, then reboot and flash the Gapps, then it works fine (until the next factory reset). Any idea on what could be causing this and what could be done to avoid this? Reason I really want to be able to flash these Gapps is due to the fact that the stock Google Apps doesn't work with OK Google commands. Flashing these Gapps fixes this problem.

Advice would be appreciated :good: can submit logs and screenshots if needed.
Click to expand...
Click to collapse

Yes I had the same problem. I flash the ROM then I flash the GApps when I boot the ROM up its a black screen and can't pass it until I do a factory reset. @MastahF told me that the system was mounted read-only that's why there isn't a single Google app on my phone after the factory and reset.

Solution: Yesterday while I was trying I flashed the ROM then I went to Mounts ( in TWRP ) and I found that the system was already mounted so I unmounted it and unmounted cache and it solves the problem

Sent from my GT-I9082 using Tapatalk
 
Last edited:
F

foresto

Senior Member
Feb 13, 2010
164
65
Gesture typing is broken

I just tried open_gapps-arm-5.1-pico-20151014 with a couple recent CyanogenMod nightly builds, and discovered that gesture typing is broken.

The Gesture Typing option is available and enabled in Android Keyboard (AOSP) settings.

/system/lib/libjni_latinime.so exists, md5sum 869ef480a0cc869a455ae08eabd9d734.

Still, gesture typing doesn't work.

Gesture typing works fine when I use cgapps instead of opengapps.
 
M

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,356
The Hague
github.com
Xiaomi Mi 11
Samsung Galaxy Watch 4
dannyella said:
Something in new releases is causing AOSP keyboard to crash in CM. Flashing TK gapps fixed it. I would really hate to stop using Open gapps. Please fix.:(
Click to expand...
Click to collapse

foresto said:
I just tried open_gapps-arm-5.1-pico-20151014 with a couple recent CyanogenMod nightly builds, and discovered that gesture typing is broken.

The Gesture Typing option is available and enabled in Android Keyboard (AOSP) settings.

/system/lib/libjni_latinime.so exists, md5sum 869ef480a0cc869a455ae08eabd9d734.

Still, gesture typing doesn't work.

Gesture typing works fine when I use cgapps instead of opengapps.
Click to expand...
Click to collapse

Actually we removed in 14-10 the gesture typing libs from AOSP keyboard, because there were so many issues with it. So if you do a clean install on /system/ there should not be any gesture typing nor any AOSP keyboard crashes anymore.
If you do want gesture typing, please install the Google Keyboard, which is for now also set to be allowed on 'dirty installs'.


Ashish.akc said:
tried installing stock package on yureka(tomato) over latest AICP nightly but that gave me error 30. it was a clean install though @MastahF
Click to expand...
Click to collapse

Please post your debug log.
 
M

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,356
The Hague
github.com
Xiaomi Mi 11
Samsung Galaxy Watch 4
Dkadr1 said:
Yes, it worked before. Now it does not even open the camera when trying to save a face.

Here is the logcat:

Code: 
java.lang.NoSuchMethodError: No virtual method checkSelfPermission(Ljava/lang/String;)I in class Landroid/app/Activity; or its super classes (declaration of 'android.app.Activity' appears in /system/framework/framework.jar)
	at com.android.facelock.SetupInstructionsScreen$SetupInstructionsFragment.onClick(SetupInstructionsScreen.java:121)
	at android.view.View.performClick(View.java:4789)
	at android.view.View$PerformClick.run(View.java:19881)
	at android.os.Handler.handleCallback(Handler.java:739)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:135)
	at android.app.ActivityThread.main(ActivityThread.java:5294)
	at java.lang.reflect.Method.invoke(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:372)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)
Click to expand...
Click to collapse

Could you try to replace the Facelock apk on /system/ with this old version and see if the error still appears? https://github.com/opengapps/all/bl...com.android.facelock/15/nodpi/22.apk?raw=true
 
You must log in or register to reply here.

Similar threads

Deltadroid
  • Poll
[GAPPS][4.4.4][5/6/7/8/9.x.x] Delta Gapps With Modular Addons (All DPI)
Replies
4K
Views
2M
C
CyberBabay
osm0sis
  • Locked
[GAPPS][5.1.x] [CLOSED] Up-to-Date GOOGLE APPS (TK GApps) [2015-10-04]
Replies
26
Views
2M
osm0sis
osm0sis
Chainfire
[Android 2.1+][03.10.2011][v3.2] Chainfire3D [ROOT][OpenGL ES 2.0+]
Replies
3K
Views
3M
rignfool
rignfool
jajb
[GAPPS][2015-04-04] Google Apps Minimal Edition for Android 5.0.x & 5.1.x
Replies
1K
Views
1M
thiago_727
thiago_727
nathanchance
[GAPPS] [7.1.2] [ARM/ARM64] [July 25th] Beans GApps
Replies
838
Views
923K
mAnN14
mAnN14

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    A
    AnonVendetta
    G A S T said:
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    Click to expand...
    Click to collapse
    I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.
    View
    4
    A
    AnonVendetta
    MJPollard said:
    What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there.
    Click to expand...
    Click to collapse
    MindTheGApps has Android 14 builds. I'm using it on an A14 LineageOS gsi ROM right now. The only problem with MTG, is that it isnt customizable. The zips are take it or leave it, you're installing all the components in the zip, or not at all. There is only 1 version (all the zips are the same, excluding hardware/Android version-specific details) which is essentially 1 size fits all. But most other GApps providers have customization in that you can choose which parts you do/don't want. But MTG is also very minimal, it just includes the core GApps components and little to no bloat. So it's not a big deal to me. I don't need all the extra stuff, just Play Services/Play Store/calendar and contacts syncing, not much else.

    MTG for Android 14:

    Releases · MindTheGapps/14.0.0-arm64

    Contribute to MindTheGapps/14.0.0-arm64...
    github.com github.com
    View
    2
    MJPollard
    MJPollard
    G A S T said:
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    Click to expand...
    Click to collapse

    AnonVendetta said:
    I think it's safe to assume that OpenGApps is dead, it's well beyond the point of simply being temporarily on hold. The devs havent posted in many months, not even to say that it's just on hiatus and will return in the future. And besides that, the last OpenGApps releases are for Android 11, we are now on Android 14, and 15 is coming soon. Even if it comes back, they will have way too much catching up to do for the project to be manageable. There are a few other GApps providers out there that you can try, I'd move on. OpenGApps always was my fave, but I've managed without them.
    Click to expand...
    Click to collapse

    What he said. There are other GApps providers like MindTheGapps and NikGapps (which is the one I use) that have taken up the mantle from OpenGApps. NikGapps, in fact, still has releases going all the way back to Android 9 (Pie), and like OpenGApps, provides packages from "core" to "full" depending on how much GApps you need. MindTheGapps, unfortunately, stops at Android 13, so if you're using 14, you're SOL there.
    View
    1
    G
    G A S T
    Is there anything new to say?
    OpenGApps is still pretty dead atm, which is very sad...
    View
  • 837
    M
    MastahF
    ​
    Questions? Use Q&A!
    Please read the FAQ before reporting any bugs or errors!
    If you post in the main thread not having read the FAQ or error message itself, not included a debug log when reporting a malfuction or reporting a Force Closure without a logcat, your post will be ignored by the developers!
    Not because we are evil, but because the same questions keep popping up over and over again and too often we get a "X doesn't work, plz fix" without any clue what is happening. We don't have telepathic connection to your device and all the time unnecessarily wasted on this can't be spend on development of Open GApps itself.

    The Latest builds of Open GApps for Android can easily be downloaded from the:


    I work on this project for FREE and putting in a lot of hours into it. While not mandatory, donations encourage me to continue to further pursue this project and I'd deeply appreciate them, if you feel generous.
    Donate to The Open GApps Project

    Are you a ROM developer and want to hotlink to the latest Open GApps package? Then check this wiki entry for details.
    Please don't publicly mirror the prebuilt packages without explicit consent of @MastahF, to ensure that users will always be directed to the very latest version and the source code of the project.


    About The Open GApps Project
    Open GApps is a Google Apps package completely developed by writing buildscripts which allow for the automated creation of new up-to-date packages automatically.
    The development process is completely open-source (GPLv3) and the goal is to have multiple contributors involved, to secure and reinforce the sustainability of Open GApps development.
    Builds are generated every (European) night automatically (if there are any changes) and uploaded to GitHub.

    Official AROMA Open GApps package is developed in collaboration with long-time LP-AROMA-developer @raulx222 and has a dedicated XDA thread
    For any questions about the AROMA installer development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.

    Official Open GApps For Stock support is developed in collaboration with @Rapper_skull and has a dedicated XDA thread
    For any questions about the GApps for Stock development, please refer to that thread. Of course, general support questions can also be asked in our own Q&A thread.

    The x86 package branch of the package is focused on Zenfone support and is maintained by @deadman96385 of the famous Zenfone GApps packages and has its own topic for x86 related questions

    For those that cook their own ROM, an AOSP-build mechanism for Open GApps has been developed by @blystad and can be found at GitHub, remember that you should not bundle any pre-packaged Google Apps with any ROMs you want to distribute further though.

    To gather all the various APKs that are necessary for the packages our master of the APK Universe @MNBooZe has written a tool called APKCrawler that scrape these from the internet, e.g. from APKMirror, it can be found at GitHub too.

    Characteristic of Open GApps:

    • Some highlights about the characteristics of the Open GApps packages:
    • All platforms and and all Android versions are supported
    • DPI-optimized support for all Google packages (unlike other GApps)
    • Frequently updated Google Apps: The pre-built OpenGApps.org packages are updated every (European) night (if there are any updated Google Apps available)
    • Strong compression, allowing for relatively small downloads of even the most complete packages
    • Automatic backup: It is not necessary to re-flash Google Apps when you flash a ROM update. Most ROMs support this (addon.d) function
    • The installer checks your device’s capabilities, like the system partition size. It will notify you, before making any changes, if it finds any problems
    • Several package variations, from a Google Super Package (includes all applications that ever shipped on a Google device), to a Stock package that equals the set of applications found on the most current and complete Nexus, to smaller, minimalist packages and an AROMA package that allows graphically selection of what to install
    • A special ‘for Stock ROM’ installation mode that allows to update the Google Apps on Stock ROMs that conform to the original Google Nexus filesystem structure
    • All package installations can be customized to your individual preferences using our Advanced Features and Options

    The idea behind this project:
    I believe a big source of the problem for many GApps packages to stay up-to-date (or not be forfeited) is the lack of time for developers to do labour-intensive repetive every time a new google-app apk is released.
    That is why I have taken it upto myself to write some Linux shell scripts to automate the packaging and to share these efforts with the world with the goal to create a team to continue this package together under the name Open GApps.

    This project should not be managed by a person, but by a team, so volunteers willing to help are more than welcome!

    Open GApps installer uses open source third-party tools, like busybox and xzdec, compiled by @YashdSaraf; See his busybox thread for more info.
    Open GApps is originally based on the now discontinued PA GApps package of @TKruzze and @osm0sis
    View
    36
    ipdev
    ipdev
    HtHNightwolf said:
    Is it possible to get a test version of the arm version aswell?
    Click to expand...
    Click to collapse
    I run arm/arm64 builds of pico, nano and stock for testing.

    Once they are tested a bit and seem stable, I upload them to MediaFire.
    MediaFire - Link

    Android 12 builds are in the SDK31 folder.
    The 20211218 builds include some permission updates.​

    ---

    Last week I ran SDK32 builds to test on LineageOS.
    LineageOS is merging 12.1.0_r1 into the 19.0 branch instead of creating a 19.1 branch.
    LineageOS Gerrit - Topic 12L - Link
    Edit: I just checked and see they decided to bump up to 19.1 a few days ago.​

    Note:
    Now that Android 12L is official, the release props still show as 12 not 12.1 or 12L.
    The build tag was bumped to 12.1.0 and the boot image is now SDK32 but, the kernel version is still showing as 12.0.0
    The boot image was SDK31 on the 12L preview release.​

    The only way to determine if you are running 12 or 12L is by checking the SDK level.
    SDK31 = Android 12
    SDK32 = Android 12L

    The initial 12L OpenGApps test builds were blind builds and untested.
    I did not have a device/rom to test them on. 🙃

    I few days later I was able to test them on a Pixel C, Lineage 19.0 SDK32 build.
    Since it is a tablet, it utilized the large screen layout of SDK32.​

    The 12L pico and nano builds seem to be safe.

    The 12L stock build had issues with Pixel launcher so, I would suggest not using it for now.
    Unless you are using a gapps config script to customize the install.

    Android 12L (SDK32) test builds are currently on gDrive.
    gDrive - Link


    Everyone is welcome to give them a try.

    Cheers all. :cowboy:

    Edit:
    See additional posts.
    Post # 7,316
    Post # 7,319
    View
    25
    M
    MastahF
    Tomorrow there will be 7.0 builds
    Small update concerning Nougat: everything is almost in place, only HotWord Enrollment is not de-odexable yet.
    So tomorrow there will be 7.0 builds, ready for when the first source and custom ROMs will drop.
    Of course beta-quality because they cannot be tested yet, so be careful.
    There are some minor changes, Google changed their keyboard stuff, so there will be no swypelibs possible anymore.
    Google VR Services is backported to all Android versions (so all the way from 4.4 to 6.0) but ofc not yet known how well it will work.
    Also there are some new 7.0 core apps for Google's Shared Android Services (com.google.android.ext.shared; com.google.android.ext.services)
    Trusted Face's unlock has also some major changes, it seems the pittpatt suff is not necessary anymore for 7.0.

    That's it for now
    View
    25
    M
    MastahF
    For those who hadn't spotted it yet: we can celebrate 1 year of Open GApps :)
    http://opengapps.org/blog/post/2016/05/09/open-gapps-first-anniversary/
    View
    23
    mark manning
    mark manning
    Sorry to drop in but needed to clean up some unnecessary posts that were burying more legitimate posts to the thread.

    Going into someone's thread and demanding they make you something is not only just plain rude, it goes against everything XDA is about. Numerous people suggested a way for you to remove the gapps and you chose to ignore them. The dev isn't going to make an uninstaller just for you. You could also always use root explorer and remove the apps that way too. Anywho, there won't be an uninstaller made so no need to continue this conversation.

    Thread Cleaned
    View

New posts