How to rebuild android-x86-9.0-r2

447 views
Skip to first unread message

co...@naic.edu

unread,
Nov 11, 2020, 1:55:06 PM11/11/20
to Android-x86
Hi,
I followed the instructions in: https://www.android-x86.org/source.html
to rebuild android-x86 9.0.
Essentially what I did was:

mkdir android-x86 ; cd android-x86
repo init -u http://scm.osdn.net/gitroot/android-x86/manifest -b pie-x86
repo sync --no-tags --no-clone-bundle
make -j<n> rpm TARGET_PRODUCT=android_x86_64


The resulting rpm package was called android-x86-YYYY-MM.x86_64.rpm
where YYYY and MM are the year and month when the package was build.
My intention was to rebuild android-x86-9.0-r2.x86_64.rpm but the result
I obtained was different: in my build the kernel is 4.19.122 while in 9.0r2
the kernel is 4.19.110 and, of course, there are other differences.

Is there a way to recreate/build exactly android-x86-9.0-r2.x86_64.rpm?

Thanks.

Michael Goffioul

unread,
Nov 11, 2020, 2:29:08 PM11/11/20
to Android-x86
There is a manifest for 9.0-r2 at https://osdn.net/projects/android-x86/scm/git/manifest/tree/pie-x86/
So I guess it's just a matter of specifying the manifest file with 'repo init -m <manifest>' then resync.


--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/5e9703e0-1104-42de-b2e9-b00df66a1150n%40googlegroups.com.

Clock Zhong

unread,
Nov 11, 2020, 10:39:18 PM11/11/20
to Android-x86
If you only want to build android-x86-9.0-r2 instead of latest version of android-x86-9.0, you just need run:
repo init -u http://scm.osdn.net/gitroot/android-x86/manifest -b pie-x86 -m android-x86-9.0-r2.xml
instead of running:
It'll only checkout source code of version pie-x86-r2. Your steps will build lastest version android-x86-pie, not the r2.

co...@naic.edu

unread,
Nov 14, 2020, 7:12:58 PM11/14/20
to Android-x86
Following the suggestions I used this workflow:
# mkdir android-x86 ; cd android-x86
# repo init -u http://scm.osdn.net/gitroot/android-x86/manifest -b pie-x86 -m android-x86-9.0-r2.xml
# repo sync --no-tags --no-clone-bundle
# make -j<n> rpm TARGET_PRODUCT=android_x86_64
Now the kernel in my rpm is the same as 9.0-r2 however there are still some differences:
The rpm package is still called android-x86-YYYY-MM.x86_64.rpm instead of  android-x86-9.0-r2.x86_64.rpm
Some apps are missing. The default apps from 9.0-r2 are:
r2.jpg
and what I get with my build is:
custom.jpg

So probably some other options are needed. Any Idea which one?

Michael Goffioul

unread,
Nov 14, 2020, 8:28:29 PM11/14/20
to Android-x86
The prebuilt android-x86 ISO contains bundled opengapps. However this is not part of the regular build process (when you clone the manifest/repo like you did). If you want to bundle opengapps in your build, you have to do it yourself.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

ouija

unread,
Nov 15, 2020, 12:24:16 AM11/15/20
to Android-x86
Well shoot.  You learn something new everyday.  I didn't realize you need to specify the manifest of the later releases when building from source, I was under the assumption that repo init -u http://scm.osdn.net/gitroot/android-x86/manifest -b pie-x86 was defaulting to using the latest r# release.   Damn, now I gotta rebuild some images.

I wanted to mention that a good guide to follow in order to build with openapps can be found here: https://groups.google.com/g/android-x86/c/XkPdT1hwpps/m/HyAzet3CAwAJ

ar...@sat-infotech.com

unread,
Dec 15, 2020, 11:15:39 PM12/15/20
to Android-x86
I tried to build with the instructions provided... But pretty much everything of google playstore crashes.

Is there a source tree of R2 (containing opengapps), which i can download .. probably with a script

ouija

unread,
Dec 18, 2020, 4:19:39 PM12/18/20
to Android-x86
This is likely due to recent issues with native bridge nor working/downloading properly.  See this post: https://groups.google.com/g/android-x86/c/mlU4ajAdr7A/m/-1FTBg9dCAAJ
Reply all
Reply to author
Forward
0 new messages