build issue on android-x86 #168
Comments
|
Today I build without/ exclude Phonesky then i build again include Phonesky. Then i get error again |
|
again to day so eone told me to do this but still build fail. I did LOCAL_DEX_PREOPT := false , but still error or fail. i don't know how to fix. |
|
I don't think opengapps has an "x86" or "x86_64" version of Phonesky (i.e. "com.android.vending"), which probably explains the "acp" error message. However, there are apks for "com.android.vending.leanback" in the "x86" and "x86_64" projects. You could try installing one of those. I think you will have to create a new build module for it. It should look something like this: # vendor/opengapps/build/modules/GooglePlayStoreLeanback/Android.mk
LOCAL_PATH := .
include $(CLEAR_VARS)
include $(GAPPS_CLEAR_VARS)
LOCAL_MODULE := GooglePlayStoreLeanback
LOCAL_PACKAGE_NAME := com.android.vending.leanback
LOCAL_PRIVILEGED_MODULE := true
include $(BUILD_GAPPS_PREBUILT_APK) |
|
please look at this screen. Do i need to exclude phonesky? I could see it on my harddrive and cloud. How can I just download or sync only for x86 and x86_64. It use to ok a few weeks ago i could build. It shows error recently. Is that possible to fix on source. so I can re-sync and build and we don't need to create every time (maybe there are some other people may face this issue.) Do I need to add this line. Maybe this line bring all the apks? Is this correct? |
|
You are going to have to experiment on your own a bit. I don't have all the answers :-) Note that I've never built android-x86.
Yes, you will need to create a new folder for the new build module:
Yes. |
|
@jamuir It did not help. I did exclude phonesky and add as you said. build ok, but no playstore. |
|
@jamuir |
After you define a new module, you need to explicitly add it to your build. You should have something like this in your device.mk file: GAPPS_EXCLUDED_PACKAGES += Phonesky
PRODUCT_PACKAGES += GooglePlayStoreLeanback |
|
@jamuir |
|
@jamuir After a few min, the app get auto update and it starts working. The apps updated to Google Play Store 9.0.15-all [0] [PR] 186388994 finally it is working. |
opengapps provides two apks for com.android.vending.leanback. One is in the x86 project and the other is in the x86_64 project. You installed one of those. If you check in those projects, you can see that those apks use sdk version 21. When android says "This version of the app isn't compatible with your device", I think it is just checking the sdk version of the apk and then forcing you to upgrade to a new apk that matches your platform. You mentioned previously that other people might be hitting this same build issue (btw, is this an oreo only issue?). Perhaps you could help them by contributing a PR to opengapps with your changes. |
|
I built nougat x86. I checked apk on setting and app, there it shows 8.7.08-xhdpi (8) (PR) 180622504. (8) is for android-tv? I faced same issue also on oreox86. Since oreo-x86 is not stable, I don't use them. only nougat x86. "Google Play Store 9.1.24 Info: https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-9-1-24-release/ [5] - For Android Wear devices https://github.com/opengapps/x86/tree/master/priv-app/com.android.vending.leanback/21/320 https://github.com/opengapps/x86_64/tree/master/priv-app/com.android.vending.leanback/21/320 I am happy that it solved my issue. one or other way. I don't know how to "PR". I wish it can help other and for me as well, then we don't need to make mkdir GooglePlayStoreLeanback folder and make Android.mk file. PLease guide me how to make "PR". |
|
PR stands for "pull request". Start by forking the project https://github.com/opengapps/aosp_build into your own github account. Make whatever fixes you like and then push them up to your forked copy. Then use the button "New pull request" to open a pull request so your changes can be considered for inclusion in the main project. |
|
And I have the same issue. |
|
@amezin : thanks for pointing out that change in x86! It seems likely that the apk was removed by mistake. |
|
@jamuir And I remember that it's not the first time. Some time ago when I tried opengapps for the first time, there was the same problem. Then com.android.vending suddenly appeared in x86 repo. And now it disappeared again. Another thing related to this issue, I think: Is it actually intended? |
|
My guess it that is it not intended. It doesn't make sense to put an arm apk in an archive for x86. There must be a bug in one of the opengapps scripts: |
|
It's not a bug, it's just incorrect commit. Phonesky was removed for all x86 platforms, and kept for ARM only. If we need only one APK for both platforms, than it should be moved to all source, not ARM. |
|
@Ganster41 but latest apk contains native libraries for arm only: It may work on x86 with Houdini, but what about x86 without houdini and other platforms? |
|
@amezin that's why I don't completely understand what is the purpose of that changes. |
|
The play store has never had an x86 variant. They have always been a single multi-arch APK. Google removed x86 and x86_64 from the current APK. AFAIK we have always counted on houdini for arm-x86 support... |
|
@NicholasBuse if it's exactly the same apk for all platforms, then +1 on moving it to "all" |
|
All is typically used for no-arch APKs (no processor dependent binaries) |
|
If it's the same APK for all arches - I see no difference from noarch. If we define "no-arch" as "for all architectures" - put the APK to "all", problem solved. Copying the apk to all arch-specific repos (as it was before) will work too, though for me it makes no sense. Leaving the APK only in "arm" causes problems for us - people who use aosp_build. We'll have to download extra arch-specific repository (a big one) just to get one APK (and also aosp_build scripts won't pick up the APK from "arm" for x86, AFAIK, so extra changes will be necessary). |
|
There doesn't seem to be any harm in storing multi-arch apks in "all" (along with no-arch). I agree that forcing devs to sync "arm" and "arm64" when they just want to build for x86 is inconvenient. |
|
Agreed. @NicholasBuse can you consider changing the scripts? |
|
quoting amezin:
That's right. The build system used by aosp_build currently searches for apks in the directories/projects |
Recenlty I built android*x86 without gapps with kernel 4.15 gapps without any nowissue. But, i am building new android-x86 with gapps and facing this issue.
and
The text was updated successfully, but these errors were encountered: