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

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
When i installed the Stock one on
http://forum.xda-developers.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!
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:

mybeshoo

Senior Member
Jul 18, 2011
145
8
0
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?
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

Senior Member
Jan 11, 2013
2,239
1,646
193
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?
If the ROM doesn't have the swipe feature enabled, you just can't add the library:

http://forum.xda-developers.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:

kchaisu

Senior Member
Jan 27, 2014
896
737
0
Bangkok
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).
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

Senior Member
Feb 21, 2012
350
656
133
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?
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

imcrazyz

Senior Member
Jan 29, 2015
71
6
28
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?
 

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
If the ROM doesn't have the swipe feature enabled, you just can't add the library:

http://forum.xda-developers.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....
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.

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?
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

Senior Member
Nov 3, 2006
1,485
115
93
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
 

imcrazyz

Senior Member
Jan 29, 2015
71
6
28
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.
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:

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
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
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 :)

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
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?

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.
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

Senior Member
May 4, 2011
189
49
0
Madrid
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?
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)
 

chewdaniel

Senior Member
Feb 27, 2011
2,013
859
183
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
 

stephendt0

Senior Member
Apr 9, 2012
1,444
369
103
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
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.
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:

dannyella

Senior Member
Jan 23, 2013
1,754
404
0
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.:(
 

foresto

Senior Member
Feb 13, 2010
128
46
48
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.
 

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
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.:(
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.
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'.


tried installing stock package on yureka(tomato) over latest AICP nightly but that gave me error 30. it was a clean install though @MastahF
Please post your debug log.
 

MastahF

Inactive Recognized Developer
Feb 10, 2015
811
2,342
123
The Hague
github.com
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)
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