Make of the Oreo RC1?

Torsten Appelhagen

unread,

Jul 5, 2018, 4:24:19 AM7/5/18

to Android-x86

Hello,

I'm trying to make an image for a new x86-based board. Unfortunately I have no experience in building Android yet.

I started by downloading the currently released RC1/64bit for Android 8 to see whether it would basically work and indeed, except for a stopping Bluetooth service the system comes up (very good work by the developers!).

Now I wanted to build this by myself to customize some details. I've set up a dev environment based on Ubuntu 16.04 according to the instructions on the android-x68 homepage and tried to make "oreo-x86/android_x86_64".

Regarding the environment I was a little confused as the page tells the Java SDK is part of the master branch (no installation required) and in the next step apt-install is described? In fact it needs to be installed...

Moreover I needed to install "python-mako" which was not mentioned.

Finally the process ended with a bootable image, but it's obviously not the same: Android starts, but there is no welcome screen for the basic configuration; I can only choose between 2 task managers and I am left on the desktop then. Moreover in the list of available apps there are none of the Google related ones, and the worst thing is I cannot open the settings (immediately crashes with the option to retry or keep it closed)...

I've redone build and redirected output to a logfile, but this is 28MB in size making it quite useless as long as I don't know what to search for.

This leaves me with some questions:

- Was my approach correct at all, or do I have to do additional steps to reproduce the RC1-image from source?

- In case I am wrong, what do I have to do additionally? I haven't found any further instructions...

- If this should have worked, how should I start debugging why there are components missing/crashing so I can start fixing these?

Thanks in advance,

Torsten

Michael Goffioul

unread,

Jul 5, 2018, 8:38:01 AM7/5/18

to andro...@googlegroups.com

Hi Torsten,

The Google apps are not part of the standard build process. This is something that Chih-Wei adds himself to the Android-x86 images. I suppose he's using OpenGapps (https://opengapps.org/), so I assume you should be able to do it youself too.

Regarding the crash of the Settings app, you should start by looking at the logs from (adb logcat) and see whether there's any backtrace. You can then post the backtrace here for further support.

Michael.

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

Torsten Appelhagen

unread,

Jul 5, 2018, 4:30:02 PM7/5/18

to Android-x86

Thanks Michael,

I will check it next week (I have to attend a fair the next days)!

Torsten

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

Torsten Appelhagen

unread,

Jul 11, 2018, 7:49:15 AM7/11/18

to Android-x86

Hello Michael,

fortunately the LAN connection works, so I was able to use adb via TCP. Otherwise this will become tricky, there doesn't seem to be any usable port for debugging on board...

This seems te be the relevant part:

07-11 11:01:34.048  4278  4289 I zygote64: Background concurrent copying GC freed 4320(898KB) AllocSpace objects, 2(40KB) LOS objects, 50% free, 1945KB/3MB, paused 33us total 112.448ms
07-11 11:01:34.055  2556  2578 I ActivityManager: Displayed com.android.settings/.Settings: +579ms (total +13s910ms)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry: No service published for: wifip2p
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry: android.os.ServiceManager$ServiceNotFoundException: No service published for: wifip2p
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.os.ServiceManager.getServiceOrThrow(ServiceManager.java:75)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.app.SystemServiceRegistry$49.createService(SystemServiceRegistry.java:569)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.app.SystemServiceRegistry$49.createService(SystemServiceRegistry.java:567)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.app.SystemServiceRegistry$StaticServiceFetcher.getService(SystemServiceRegistry.java:987)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.app.SystemServiceRegistry.getSystemService(SystemServiceRegistry.java:914)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.app.ContextImpl.getSystemService(ContextImpl.java:1667)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.view.ContextThemeWrapper.getSystemService(ContextThemeWrapper.java:171)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.app.Activity.getSystemService(Activity.java:5935)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at com.android.settings.wfd.WifiDisplaySettings.isAvailable(WifiDisplaySettings.java:218)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at com.android.settings.SettingsActivity.doUpdateTilesList(SettingsActivity.java:850)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at com.android.settings.SettingsActivity.-wrap0(Unknown Source:0)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at com.android.settings.SettingsActivity$5.run(SettingsActivity.java:747)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:245)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
07-11 11:01:34.208  4278  4306 E SystemServiceRegistry:         at java.lang.Thread.run(Thread.java:764)
07-11 11:01:34.212  2556  2947 W ActivityManager:   Force finishing activity com.android.settings/.Settings
07-11 11:01:34.222  2556  2572 I ActivityManager: Showing crash dialog for package com.android.settings u0
07-11 11:01:34.241  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3338' (No space left on device); fd=27
07-11 11:01:34.241  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3344' (No space left on device); fd=27
07-11 11:01:34.241  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3347' (No space left on device); fd=27
07-11 11:01:34.241  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3353' (No space left on device); fd=27
07-11 11:01:34.241  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3354' (No space left on device); fd=27
07-11 11:01:34.242  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3355' (No space left on device); fd=27
07-11 11:01:34.242  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3356' (No space left on device); fd=27
07-11 11:01:34.242  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3357' (No space left on device); fd=27
07-11 11:01:34.242  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3358' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3359' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3374' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3381' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3393' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3417' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3881' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3898' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3900' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3902' (No space left on device); fd=27
07-11 11:01:34.244  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '3904' (No space left on device); fd=27
07-11 11:01:34.245  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4278' (No space left on device); fd=3
07-11 11:01:34.245  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4283' (No space left on device); fd=3
07-11 11:01:34.245  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4284' (No space left on device); fd=3
07-11 11:01:34.245  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4285' (No space left on device); fd=3
07-11 11:01:34.245  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4286' (No space left on device); fd=3
07-11 11:01:34.245  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4287' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4288' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4289' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4290' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4291' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4292' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4294' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4302' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4303' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4305' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4306' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4307' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4308' (No space left on device); fd=3
07-11 11:01:34.246  2556  4295 W SchedPolicy: add_tid_to_cgroup failed to write '4309' (No space left on device); fd=3
07-11 11:01:34.290  4278  4278 D DashboardSummary: Stopped listening for condition changes
07-11 11:01:34.293  2556  2571 W BroadcastQueue: Skipping deliver [background] BroadcastRecord{2c27bb5 u-1 android.intent.action.BATTERY_CHANGED} to ReceiverList{168ce9f 4278 com.android.settings/1000/u0 remote:364203e}: process gone or crashing
07-11 11:01:34.336  2556  3173 I OpenGLRenderer: Initialized EGL, version 1.4
07-11 11:01:34.336  2556  3173 D OpenGLRenderer: Swap behavior 2
07-11 11:01:34.336  2556  3173 E OpenGLRenderer: Device claims wide gamut support, cannot find matching config, error = EGL_SUCCESS
07-11 11:01:34.393  4278  4302 D BatteryInfo: time to make batteryStatsHelper: 43ms
07-11 11:01:34.396  2556  2574 I WifiService: requestActivityInfo uid=1000
07-11 11:01:34.397  2556  2574 I WifiService: reportActivityInfo uid=1000
07-11 11:01:34.397  2556  2574 I WifiService: getSupportedFeatures uid=1000
07-11 11:01:34.398  2556  2574 E BatteryExternalStatsWorker: no controller energy info supplied for wifi
07-11 11:01:34.398  2556  2574 E BatteryExternalStatsWorker: no controller energy info supplied for bluetooth
07-11 11:01:34.399  3215  3215 E PhoneInterfaceManager: [PhoneIntfMgr] queryModemActivityInfo: Empty response
07-11 11:01:34.407  2556  2574 E KernelCpuSpeedReader: Failed to read cpu-freq: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state (No such file or directory)
07-11 11:01:34.413  2556  2574 E BatteryExternalStatsWorker: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
07-11 11:01:34.441  4278  4302 D BatteryInfo: time for getStats: 45ms
07-11 11:01:34.486  2556  2572 W Looper  : Dispatch took 147ms on android.ui, h=Handler (android.view.Choreographer$FrameHandler) {c4cdc14} cb=android.view.Choreographer$FrameDisplayEventReceiver@33ffcbd msg=0
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4278' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4283' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4284' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4285' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4286' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4287' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4288' (No space left on device); fd=25
07-11 11:01:34.493  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4289' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4290' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4291' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4292' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4294' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4302' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4303' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4305' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4306' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4307' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4308' (No space left on device); fd=25
07-11 11:01:34.494  2556  2571 W SchedPolicy: add_tid_to_cgroup failed to write '4309' (No space left on device); fd=25
07-11 11:01:34.818  3338  3898 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, dest

I wonder which device has no space left? This does happen with a live CD as well as when installed to SSD (it does NOT happen when using the RC1 image).

>adb shell df -h
Filesystem     Size  Used Avail Use% Mounted on
tmpfs          947M  3.2M  944M   1% /
/dev/loop0     1.4G  1.4G   84M  95% /system
/dev/mmcblk1p1 7.0G  1.6G  5.4G  24% /data
tmpfs          947M  460K  947M   1% /dev
tmpfs          947M     0  947M   0% /mnt
none           947M     0  947M   0% /cache
/data/media    7.0G  1.6G  5.4G  24% /mnt/runtime/default/emulated

BR

Torsten

Am Donnerstag, 5. Juli 2018 14:38:01 UTC+2 schrieb Michael Goffioul:

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.

Mauro Rossi

unread,

Jul 11, 2018, 12:43:54 PM7/11/18

to Android-x86

Hi Torsten,

Il giorno giovedì 5 luglio 2018 10:24:19 UTC+2, Torsten Appelhagen ha scritto:

Hello,

I'm trying to make an image for a new x86-based board. Unfortunately I have no experience in building Android yet.
I started by downloading the currently released RC1/64bit for Android 8 to see whether it would basically work and indeed, except for a stopping Bluetooth service the system comes up (very good work by the developers!).

Now I wanted to build this by myself to customize some details. I've set up a dev environment based on Ubuntu 16.04 according to the instructions on the android-x68 homepage and tried to make "oreo-x86/android_x86_64".
Regarding the environment I was a little confused as the page tells the Java SDK is part of the master branch (no installation required) and in the next step apt-install is described? In fact it needs to be installed...
Moreover I needed to install "python-mako" which was not mentioned.

Finally the process ended with a bootable image, but it's obviously not the same: Android starts, but there is no welcome screen for the basic configuration; I can only choose between 2 task managers and I am left on the desktop then. Moreover in the list of available apps there are none of the Google related ones, and the worst thing is I cannot open the settings (immediately crashes with the option to retry or keep it closed)...

This problem happens with the eng builds, in order to avoid it there is a quick & dirty hack that avoids the crashes happening in eng build:

cd ~/oreo-x86_kernel/packages/apps/Settings

git fetch x86 oreo-x86

git checkout FETCH_HEAD

git remote add maurossi https://github.com/maurossi/packages_apps_Settings

git fetch maurossi oreo-x86_810_hacks_v2

git cherry-pick 663f0f21cb8302023b32ec1c15d41b993eca016f

git cherry-pick 9999c0685d24b408947137f03a7e5f940fb017cf

If you build userdebug you will be probably be fine without hack, but pay attention to build id lenght not to exceed 91 chars

http://git.osdn.net/view?p=android-x86/build.git;a=blob;f=core/Makefile;h=ba5bfac2d2133969a2ae685df4f8d951a10e2ede;hb=refs/heads/multiwindow-oreo

line 177:

# The string used to uniquely identify the combined build and product; used by the OTA server.

ifeq (,$(strip $(BUILD_FINGERPRINT)))

ifneq ($(filter eng.%,$(BUILD_NUMBER)),)

# Trim down BUILD_FINGERPRINT: the default BUILD_NUMBER makes it easily exceed

# the Android system property length limit (PROPERTY_VALUE_MAX=92).

- BF_BUILD_NUMBER := $(shell echo $${USER:0:6})$(shell $(DATE) +%m%d%H%M)

+ BF_BUILD_NUMBER := $(shell echo $${USER:0:4})$(shell $(DATE) +%m%d%H%M)

else

BF_BUILD_NUMBER := $(BUILD_NUMBER)

endif

BUILD_FINGERPRINT := $(PRODUCT_BRAND)/$(TARGET_PRODUCT)/$(TARGET_DEVICE):$(PLATFORM_VERSION)/$(BUILD_ID)/$(BF_BUILD_NUMBER):$(TARGET_BUILD_VARIANT)/$(BUILD_VERSION_TAGS)

187 endif

I've redone build and redirected output to a logfile, but this is 28MB in size making it quite useless as long as I don't know what to search for.
This leaves me with some questions:
- Was my approach correct at all, or do I have to do additional steps to reproduce the RC1-image from source?
- In case I am wrong, what do I have to do additionally? I haven't found any further instructions...
- If this should have worked, how should I start debugging why there are components missing/crashing so I can start fixing these?

Why not starting from oreo-x86_8.1rc1 stock build to do the debug/assessment?

What is your hardware new x86-based board?

Mauro

Thanks in advance,
Torsten

Torsten Appelhagen

unread,

Jul 11, 2018, 2:30:00 PM7/11/18

to Android-x86

Hello Mauro,

I will give "userdebug" a try, it would be nice if it runs without "extra hacks", thanks for this hint!

The stock build doesn't show this behaviour, that's the reason why I asked what might be different when I compile by myself.

The board is a special one for an embedded system with a processor board (Q7 standard).

Torsten Appelhagen

unread,

Jul 12, 2018, 9:23:34 AM7/12/18

to Android-x86

Hi Mauro,

success!

userdebug with the patch below is functional except for Bluetooth, but that's not important at the moment.

Now I will try to find out how to include GApps directly... ;)

Thanks!

BR

Torsten

Am Mittwoch, 11. Juli 2018 18:43:54 UTC+2 schrieb Mauro Rossi:

Christian Jamoner

unread,

Jul 19, 2018, 7:04:33 PM7/19/18

to Android-x86

Here's how to add gapps.

https://github.com/opengapps/aosp_build

Torsten Appelhagen

unread,

Jul 20, 2018, 12:35:44 AM7/20/18

to Android-x86

Yes, I found that and got "pico" included (the "stock" version failed due to a missing "camera"-APK, more may be missing but I didn't check further).

But in the meantime I've read about licensing issues for bundled gapps, so we will most probably have to make this a user-installable feature. :(

There I'm facing another problem now - the "system" partition only leaves about 16MB free space but according to some instructions I found there is at least one part which must be installed as a system service. But this one is 80MB in size...

Reply all

Reply to author

Forward