Mister_Ed
Posts: 9
Joined: Wed Feb 06, 2019 9:44 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Tue Mar 19, 2019 7:25 am

hzak wrote:
Mon Mar 18, 2019 4:51 pm

I guess your LCD television can not accept 720p resolution.
And the Android 9 Pie on Raspberry Pi should not run in 1080p resolution(It takes too much memory)
I am thinking if I can make a fake 720p display (show 720p screen on a 1080p display). Is it ok for you?

Can you send me the kernel log and SurfaceFlinger's log by executing follow commands:

Code: Select all

$ adb shell dmesg
$ adb shell dumpsys SurfaceFlinger

Thanks.
Hello,

Thank you, that sounds interesting. So I guess it's ok with me.

For the adb commands I'm sorry but I'm not able to provide that information because the Android doesn't seem to start hence there is no network connection to connect to with adb.

Best regards,

Angels-group
Posts: 2
Joined: Sat Mar 23, 2019 12:11 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Sat Mar 23, 2019 12:12 pm

Hello! Thanks for your work, hzak !

Is it possible to add Bluetooth A2DP Sink mode to this firmware (model B)?

rpikick0
Posts: 1
Joined: Sun Mar 24, 2019 11:10 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Sun Mar 24, 2019 11:21 am

Hello everyone,
New to the forum and evolving noob.....the responsiveness on this image is really impressive. its great to see android run this well on pie. im trying to get the img to expand to the whole sd card though and not having much luck is there something im missing? also would rooting be as simple as pushing supersu or magisk over adb? thanks.

Angels-group
Posts: 2
Joined: Sat Mar 23, 2019 12:11 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Sun Mar 24, 2019 6:34 pm

hzak wrote:
Tue Mar 05, 2019 4:23 pm
A simple way to use software decoder to play video:
1. Download this file: https://www.brobwind.com/wp-content/upl ... tch.tar.gz which contain gralloc.drm.so and libstagefright.so
2. Replace /system/lib/libstagefright.so and /vendor/lib/hw/gralloc.drm.so by following commands:

Code: Select all

$ adb connect 192.168.5.211 # replace you Raspberry Pi 3's IP address
$ adb remount
$ adb push gralloc.drm.so /vendor/lib/hw/
$ adb push libstagefright.so /system/lib/
$ adb reboot
I try this libraries, but video playback still don't work.
Video work only on youtube site via chrome. But in apps what used native media API - video don't work.

But your ROM (Android PIE) very very very nice! Best android build for RPI3 (try on 3B).
Clean, fast! Super! Thank you)

Have you plans to fix bugs and problems? Or development stopped?

newsy
Posts: 1
Joined: Wed Mar 27, 2019 10:22 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Wed Mar 27, 2019 10:40 am

Hi, nice work!
But i have a problem, if i use RPI without monitor, keyboard and mouse, as a background data controller device then Android boot hanging with Fatal signal 11. Do you have any idea?
Thanks

My logcat is:

Code: Select all

01-01 01:03:48.372  3340  3340 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8 in tid 3340 (surfaceflinger), pid 3340 (surfaceflinger)
01-01 01:03:48.461  3359  3359 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 01:03:48.462  3359  3359 F DEBUG   : Build fingerprint: 'Android/rpi3/rpi3:9/PPR2.180905.006.A1/hzak01212311:eng/test-keys'
01-01 01:03:48.462  3359  3359 F DEBUG   : Revision: '0'
01-01 01:03:48.462  3359  3359 F DEBUG   : ABI: 'arm'
01-01 01:03:48.462  3359  3359 F DEBUG   : pid: 3340, tid: 3340, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
01-01 01:03:48.462  3359  3359 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8
01-01 01:03:48.462  3359  3359 F DEBUG   : Cause: null pointer dereference
01-01 01:03:48.462  3359  3359 F DEBUG   :     r0  ef69eb58  r1  00000000  r2  6e33d705  r3  efc2a88c
01-01 01:03:48.462  3359  3359 F DEBUG   :     r4  ef686d00  r5  00000000  r6  ef68710c  r7  ffffffff
01-01 01:03:48.462  3359  3359 F DEBUG   :     r8  00000000  r9  ef698ae0  r10 00000001  r11 ef6e4a38
01-01 01:03:48.462  3359  3359 F DEBUG   :     ip  fff96328  sp  fff96850  lr  f03cd03b  pc  f03c70ea
01-01 01:03:48.538  3359  3359 F DEBUG   : 
01-01 01:03:48.538  3359  3359 F DEBUG   : backtrace:
01-01 01:03:48.538  3359  3359 F DEBUG   :     #00 pc 0004c0ea  /system/lib/libsurfaceflinger.so (android::FramebufferSurface::FramebufferSurface(android::HWComposer&, int, android::sp<android::IGraphicBufferConsumer> const&)+206)
01-01 01:03:48.538  3359  3359 F DEBUG   :     #01 pc 00076721  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::processDisplayChangesLocked()+1472)
01-01 01:03:48.538  3359  3359 F DEBUG   :     #02 pc 00070bf1  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::processDisplayHotplugEventsLocked()+564)
01-01 01:03:48.538  3359  3359 F DEBUG   :     #03 pc 000721a3  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::onHotplugReceived(int, unsigned long long, HWC2::Connection)+282)
01-01 01:03:48.538  3359  3359 F DEBUG   :     #04 pc 0005008b  /system/lib/libsurfaceflinger.so (_ZN4HWC212_GLOBAL__N_122ComposerCallbackBridge9onHotplugEyN7android8hardware8graphics8composer4V2_117IComposerCallback10ConnectionE$ff7ff70f3e3aac89dae835355ade5464+18)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #05 pc 0001b4d9  /system/lib/android.hardware.graphics.composer@2.1.so (android::hardware::graphics::composer::V2_1::BnHwComposerCallback::_hidl_onHotplug(android::hidl::base::V1_0::BnHwBase*, android::hardware::Parcel const&, android::hardware::Parcel*, std::__1::function<void (android::hardware::Parcel&)>)+160)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #06 pc 0001bcc5  /system/lib/android.hardware.graphics.composer@2.1.so (android::hardware::graphics::composer::V2_1::BnHwComposerCallback::onTransact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+288)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #07 pc 00016059  /system/lib/libhwbinder.so (android::hardware::IPCThreadState::executeCommand(int)+436)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #08 pc 00016961  /system/lib/libhwbinder.so (android::hardware::IPCThreadState::waitForResponse(android::hardware::Parcel*, int*)+256)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #09 pc 00015bb7  /system/lib/libhwbinder.so (android::hardware::BpHwBinder::transact(unsigned int, android::hardware::Parcel const&, android::hardware::Parcel*, unsigned int, std::__1::function<void (android::hardware::Parcel&)>)+90)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #10 pc 0001f725  /system/lib/android.hardware.graphics.composer@2.1.so (android::hardware::graphics::composer::V2_1::BpHwComposerClient::_hidl_registerCallback(android::hardware::IInterface*, android::hardware::details::HidlInstrumentor*, android::sp<android::hardware::graphics::composer::V2_1::IComposerCallback> const&)+284)
01-01 01:03:48.539  3359  3359 F DEBUG   :     #11 pc 00024a07  /system/lib/android.hardware.graphics.composer@2.1.so (android::hardware::graphics::composer::V2_1::BpHwComposerClient::registerCallback(android::sp<android::hardware::graphics::composer::V2_1::IComposerCallback> const&)+14)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #12 pc 00046679  /system/lib/libsurfaceflinger.so (android::Hwc2::impl::Composer::registerCallback(android::sp<android::hardware::graphics::composer::V2_1::IComposerCallback> const&)+24)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #13 pc 0004caa5  /system/lib/libsurfaceflinger.so (HWC2::Device::registerCallback(HWC2::ComposerCallback*, int)+136)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #14 pc 000705bb  /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::init()+762)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #15 pc 00002679  /system/bin/surfaceflinger (main+232)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #16 pc 0008bac9  /system/lib/libc.so (__libc_init+48)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #17 pc 0000254f  /system/bin/surfaceflinger (_start_main+46)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #18 pc 00018037  /system/bin/linker (__dl__ZN6soinfoD1Ev+14)
01-01 01:03:48.540  3359  3359 F DEBUG   :     #19 pc 00020bda  [stack:fff77000]
01-01 01:03:48.761  3320  3355 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 3355 (HwBinder:3320_2), pid 3320 (composer@2.1-se)
01-01 01:03:48.859  3383  3383 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 01:03:48.859  3383  3383 F DEBUG   : Build fingerprint: 'Android/rpi3/rpi3:9/PPR2.180905.006.A1/hzak01212311:eng/test-keys'
01-01 01:03:48.859  3383  3383 F DEBUG   : Revision: '0'
01-01 01:03:48.859  3383  3383 F DEBUG   : ABI: 'arm'
01-01 01:03:48.859  3383  3383 F DEBUG   : pid: 3320, tid: 3355, name: HwBinder:3320_2  >>> /vendor/bin/hw/android.hardware.graphics.composer@2.1-service <<<
01-01 01:03:48.859  3383  3383 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
01-01 01:03:48.859  3383  3383 F DEBUG   : Cause: null pointer dereference
01-01 01:03:48.859  3383  3383 F DEBUG   :     r0  ea40b000  r1  00000001  r2  00000000  r3  00000000
01-01 01:03:48.859  3383  3383 F DEBUG   :     r4  00000000  r5  ea40b000  r6  ea413100  r7  ea42d310
01-01 01:03:48.860  3383  3383 F DEBUG   :     r8  ea43999c  r9  ea42d2d0  r10 ea00f020  r11 ea7e5c75
01-01 01:03:48.860  3383  3383 F DEBUG   :     ip  e9c3cd38  sp  e918b810  lr  e9c3071f  pc  00000000
01-01 01:03:48.912  3383  3383 F DEBUG   : 
01-01 01:03:48.912  3383  3383 F DEBUG   : backtrace:
01-01 01:03:48.912  3383  3383 F DEBUG   :     #00 pc 00000000  <unknown>
01-01 01:03:48.912  3383  3383 F DEBUG   :     #01 pc 0001771d  /vendor/lib/hw/hwcomposer.drm.so (android::DrmHwcTwo::RegisterCallback(int, void*, void (*)())+64)
01-01 01:03:48.912  3383  3383 F DEBUG   :     #02 pc 000055db  /vendor/lib/hw/android.hardware.graphics.composer@2.1-impl.so (android::hardware::graphics::composer::V2_1::passthrough::detail::HwcHalImpl<android::hardware::graphics::composer::V2_1::hal::ComposerHal>::unregisterEventCallback()+18)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #03 pc 000084e9  /vendor/lib/hw/android.hardware.graphics.composer@2.1-impl.so (android::hardware::graphics::composer::V2_1::hal::detail::ComposerClientImpl<android::hardware::graphics::composer::V2_1::IComposerClient, android::hardware::graphics::composer::V2_1::hal::ComposerHal>::~ComposerClientImpl()+52)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #04 pc 0000849b  /vendor/lib/hw/android.hardware.graphics.composer@2.1-impl.so (_ZTv0_n12_N7android8hardware8graphics8composer4V2_13hal6detail18ComposerClientImplINS3_15IComposerClientENS4_11ComposerHalEED0Ev+18)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #05 pc 000097fb  /system/lib/vndk-sp-28/libutils.so (android::RefBase::decStrong(void const*) const+70)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #06 pc 0003f3b5  /system/lib/vndk-sp-28/libhidltransport.so (android::hidl::base::V1_0::BnHwBase::~BnHwBase()+120)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #07 pc 000254e3  /system/lib/vndk-28/android.hardware.graphics.composer@2.1.so (android::hardware::graphics::composer::V2_1::BnHwComposerClient::~BnHwComposerClient()+122)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #08 pc 000255df  /system/lib/vndk-28/android.hardware.graphics.composer@2.1.so (_ZTv0_n12_N7android8hardware8graphics8composer4V2_118BnHwComposerClientD0Ev+18)
01-01 01:03:48.913  3383  3383 F DEBUG   :     #09 pc 000097fb  /system/lib/vndk-sp-28/libutils.so (android::RefBase::decStrong(void const*) const+70)
01-01 01:03:48.914  3383  3383 F DEBUG   :     #10 pc 0000f1e7  /system/lib/vndk-sp-28/libhwbinder.so (android::hardware::IPCThreadState::joinThreadPool(bool)+134)
01-01 01:03:48.914  3383  3383 F DEBUG   :     #11 pc 00015371  /system/lib/vndk-sp-28/libhwbinder.so (android::hardware::PoolThread::threadLoop()+12)
01-01 01:03:48.914  3383  3383 F DEBUG   :     #12 pc 0000c053  /system/lib/vndk-sp-28/libutils.so (android::Thread::_threadLoop(void*)+166)
01-01 01:03:48.914  3383  3383 F DEBUG   :     #13 pc 00063955  /system/lib/libc.so (__pthread_start(void*)+22)
01-01 01:03:48.914  3383  3383 F DEBUG   :     #14 pc 0001df1d  /system/lib/libc.so (__start_thread+22)

mcnolimits
Posts: 2
Joined: Mon Apr 15, 2019 10:16 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon Apr 15, 2019 10:23 pm

Can someone upload this .img to a Cloud. I already tried download 3 times e take 10 hours and failed. If someone could upload I would be apreciated thanks

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Sat Apr 20, 2019 5:25 pm

Please upload the image for the rpi 3B+ to github as downloading it from your website is awfully slow

n0tiert
Posts: 1
Joined: Mon Apr 29, 2019 5:42 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon Apr 29, 2019 5:48 am

Hi,

How do i generate the *.img flash file from the out directory files after successfully build ?

Rgds,

n0tiert

dmahurin
Posts: 1
Joined: Mon Apr 29, 2019 8:08 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon Apr 29, 2019 8:24 pm

Thanks for the effort in getting this to work.

HDMI works, though I was trying to get the Raspberry Pi touchscreen to work.

Has anyone been successful in getting the Raspberry pi official display working?

It seems that the needed changes in the raspberry pi kernel were not added to this android kernel.

I added all that I think were relevant for the touchscreen, but still only HDMI works.

The changes I added all apply cleanly to the android kernel.

See below for a kernel that cherry-picks the touchscreen changes, and adds the kernel config options.

---

repo init -u https://android.googlesource.com/platform/manifest -b android-9.0.0_r33 --depth=1

mkdir -pv device/brobwind
[ -d device/brobwind/rpi3 ] || git clone git://github.com/brobwind/pie-device-brobwind-rpi3 device/brobwind/rpi3

mkdir -p .repo/local_manifests
ln -snfv ../../device/brobwind/rpi3/local_manifest.xml .repo/local_manifests/

repo sync -j$(nproc)

( cd kernel-v4.14; git fetch https://github.com/raspberrypi/linux.git rpi-4.14.y )
( cd kernel-v4.14; git reset --hard 1856689bc155; \
for c in \
c486cc038e0a \
f2ba7d21a347 \
9cd543527b03 \
8cc0290d28c4 \
8b95e3e5250a \
285cd814f018 \
7a95d43804a7 \
82afe061b073 \
7791d2b93c6d \
e08252e9eb97 \
f1f172ace5f5 \
; do git cherry-pick $c; done )

echo CONFIG_FB_BCM2708=y >> kernel-v4.14/arch/arm64/configs/bcmrpi3_defconfig
echo CONFIG_TOUCHSCREEN_RPI_FT5406=y >> kernel-v4.14/arch/arm64/configs/bcmrpi3_defconfig
echo CONFIG_BCM2835_SMI_DEV=y >> kernel-v4.14/arch/arm64/configs/bcmrpi3_defconfig
echo CONFIG_DRM_PANEL_RASPBERRYPI_TOUCHSCREEN=y >> kernel-v4.14/arch/arm64/configs/bcmrpi3_defconfig
echo CONFIG_BACKLIGHT_RPI=y >> kernel-v4.14/arch/arm64/configs/bcmrpi3_defconfig

export USE_CCACHE=1

( \
cd kernel-v4.14; \
export INSTALL_ROOT=`pwd`/../device/brobwind/rpi3/boot/kernel-v4.14; \
export CROSS_COMPILE=`pwd`/../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-androidkernel-; \
INSTALL_PATH=${INSTALL_ROOT} INSTALL_MOD_PATH=${INSTALL_ROOT} ARCH=arm64 make bcmrpi3_defconfig; \
INSTALL_PATH=${INSTALL_ROOT} INSTALL_MOD_PATH=${INSTALL_ROOT} ARCH=arm64 make -j 4; \
INSTALL_PATH=${INSTALL_ROOT} INSTALL_MOD_PATH=${INSTALL_ROOT} ARCH=arm64 make -j 4 dtbs; \
INSTALL_PATH=${INSTALL_ROOT} INSTALL_MOD_PATH=${INSTALL_ROOT} ARCH=arm64 make dtbs_install; \
INSTALL_PATH=${INSTALL_ROOT} INSTALL_MOD_PATH=${INSTALL_ROOT} ARCH=arm64 make install; \
)

. build/envsetup.sh
lunch rpi3-eng
make -j$(nproc)

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Fri May 03, 2019 9:38 pm

On boot up i get
Waiting for PHY auto negotiation to complete........ TIMEOUT!
Startup failed

Not sure what I did wrong

code_exec
Posts: 271
Joined: Sun Sep 30, 2018 12:25 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Sat May 04, 2019 5:00 am

Wouldn't Android Go work better? Android Go is a version of Android optimised for devices with 512MB-1GB RAM and low-powered processors.
Ubuntu 18.04 LTS desktop images for the Raspberry Pi 3.

https://github.com/CodeExecution/Ubuntu-ARM64-RPi

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 10:48 am

hzak wrote:
Sat Jan 26, 2019 4:50 pm
With several months hardware, The Raspberry Pi 3B and 3B+ can finally run Android 9 pie system.

Features:
1. Bootloader: u-boot as AndroidThings on RPi 3B v.1.0.4, run on 64-bit mode
2. Kernel: v.4.14.71 run on 64-bit mode
3. Display: 720p(1280×720) @ 60Hz through on board HDMI port
4. Audio: analog, 2 channel through on board audio jack
5. WiFi: 2.4G (RPi 3B & 3B+), 5G (RPi 3B+)
6. Bluetooth: HCI over UART(ttyAMA0), RPi 3B: 921600bps no flow control; RPi 3B+: 3000000bps with flow control with a2dp and bt-pan(no test yet) support.
7. Ethernet: both work, and IP from DHCP
8. OpenGL render: based on mesa3d vc4 driver.
9. Hardware composer based on drm_hwcomposer (overlay has been disabled due to mis-compose in some satuation)

Knowing issue:
1. Enable `Debug GPU overdraw’ in system settings will make app crash
2. Enable `Debug non-retangular clip operations’ in system settings will make app crash
3. Do not disable `Disable HW overlays’ in system settings
4. Audio over HDMI not support
5. Can not play video

You can check the demo video on youtube at https://youtu.be/tJJetgz53OI (Normal record speed)
The performance is quite acceptable

The image can be download from https://www.brobwind.com/wp-content/upl ... f2b.bin.gz

Thanks
I can’t get it to boot!

On boot up i get
Waiting for PHY auto negotiation to complete........ TIMEOUT!
Startup failed

I saw online that it has something to do with not getting an ethernet connection (which doesn’t make sense as why would it need a network connection to boot up?)...

I’ve connected it through ethernet and now instead of “TIMEOUT!” It says “done”. But then lists “broadcast 1” all the way to “broadcast 17” and then says “time exceeded; starting again”... it them starts over and the same issue occurs.

I’m using the image you’ve uploaded to github and I’ve flashed it exactly step by step just like you’ve done in the video. I even tried using both etcher and win32diskimager, but still with the same issue.

I’m trying to run it on a rpi 3B+ using USB boot, maybe that has something to do with the error?

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 3:07 pm

Mister_Ed wrote:
Tue Mar 19, 2019 7:25 am
hzak wrote:
Mon Mar 18, 2019 4:51 pm

I guess your LCD television can not accept 720p resolution.
And the Android 9 Pie on Raspberry Pi should not run in 1080p resolution(It takes too much memory)
I am thinking if I can make a fake 720p display (show 720p screen on a 1080p display). Is it ok for you?

Can you send me the kernel log and SurfaceFlinger's log by executing follow commands:

Code: Select all

$ adb shell dmesg
$ adb shell dumpsys SurfaceFlinger

Thanks.
Hello,

Thank you, that sounds interesting. So I guess it's ok with me.

For the adb commands I'm sorry but I'm not able to provide that information because the Android doesn't seem to start hence there is no network connection to connect to with adb.

Best regards,
I am sorry. I am too busy to find out a way to make it work. I checked with the EDID spec at the very early time, but without luck.

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 3:13 pm

Angels-group wrote:
Sat Mar 23, 2019 12:12 pm
Hello! Thanks for your work, hzak !

Is it possible to add Bluetooth A2DP Sink mode to this firmware (model B)?
It may work. There is a config file in the packages/apps/Bluetooth/res/values/config.xml.
Change the property profile_supported_a2dp_sink to true and check if it can work or not.

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 3:15 pm

rpikick0 wrote:
Sun Mar 24, 2019 11:21 am
Hello everyone,
New to the forum and evolving noob.....the responsiveness on this image is really impressive. its great to see android run this well on pie. im trying to get the img to expand to the whole sd card though and not having much luck is there something im missing? also would rooting be as simple as pushing supersu or magisk over adb? thanks.
I have made a video (https://github.com/brobwind/pie-device- ... hImage.mp4) for how to flash the image and extend the userdata partition.
The image is ENG build. It has root access.

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 3:27 pm

hzak wrote:
Mon May 06, 2019 3:15 pm
rpikick0 wrote:
Sun Mar 24, 2019 11:21 am
Hello everyone,
New to the forum and evolving noob.....the responsiveness on this image is really impressive. its great to see android run this well on pie. im trying to get the img to expand to the whole sd card though and not having much luck is there something im missing? also would rooting be as simple as pushing supersu or magisk over adb? thanks.
I have made a video (https://github.com/brobwind/pie-device- ... hImage.mp4) for how to flash the image and extend the userdata partition.
The image is ENG build. It has root access.
I see that you’re online, can u please have a look at my issue posted above? I need to get this working asap.

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 3:29 pm

code_exec wrote:
Sat May 04, 2019 5:00 am
Wouldn't Android Go work better? Android Go is a version of Android optimised for devices with 512MB-1GB RAM and low-powered processors.
It's actually Android Go configuration (Please check the device/brobwind/rpi3/rpi3.mk), inherit common Android Go 512M configuration.
The system performance is impacted by:
1. TF card performance (Maximum read/write speed: (83MHz * 4 bit / 8bit = 41MB). (TF card already overclock from 50MHz to 83MHz)
2. Large screen resolution(720p)
3. DDR speed

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 3:39 pm

ikk wrote:
Mon May 06, 2019 10:48 am
hzak wrote:
Sat Jan 26, 2019 4:50 pm
With several months hardware, The Raspberry Pi 3B and 3B+ can finally run Android 9 pie system.

Features:
1. Bootloader: u-boot as AndroidThings on RPi 3B v.1.0.4, run on 64-bit mode
2. Kernel: v.4.14.71 run on 64-bit mode
3. Display: 720p(1280×720) @ 60Hz through on board HDMI port
4. Audio: analog, 2 channel through on board audio jack
5. WiFi: 2.4G (RPi 3B & 3B+), 5G (RPi 3B+)
6. Bluetooth: HCI over UART(ttyAMA0), RPi 3B: 921600bps no flow control; RPi 3B+: 3000000bps with flow control with a2dp and bt-pan(no test yet) support.
7. Ethernet: both work, and IP from DHCP
8. OpenGL render: based on mesa3d vc4 driver.
9. Hardware composer based on drm_hwcomposer (overlay has been disabled due to mis-compose in some satuation)

Knowing issue:
1. Enable `Debug GPU overdraw’ in system settings will make app crash
2. Enable `Debug non-retangular clip operations’ in system settings will make app crash
3. Do not disable `Disable HW overlays’ in system settings
4. Audio over HDMI not support
5. Can not play video

You can check the demo video on youtube at https://youtu.be/tJJetgz53OI (Normal record speed)
The performance is quite acceptable

The image can be download from https://www.brobwind.com/wp-content/upl ... f2b.bin.gz

Thanks
I can’t get it to boot!

On boot up i get
Waiting for PHY auto negotiation to complete........ TIMEOUT!
Startup failed

I saw online that it has something to do with not getting an ethernet connection (which doesn’t make sense as why would it need a network connection to boot up?)...

I’ve connected it through ethernet and now instead of “TIMEOUT!” It says “done”. But then lists “broadcast 1” all the way to “broadcast 17” and then says “time exceeded; starting again”... it them starts over and the same issue occurs.

I’m using the image you’ve uploaded to github and I’ve flashed it exactly step by step just like you’ve done in the video. I even tried using both etcher and win32diskimager, but still with the same issue.

I’m trying to run it on a rpi 3B+ using USB boot, maybe that has something to do with the error?
I didn't encounter such a problem.
Maybe you can debug the boot progress by using following instruction:
https://www.raspberrypi.org/documentati ... bootmodes/

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Mon May 06, 2019 5:34 pm

hzak wrote:
Mon May 06, 2019 3:39 pm
ikk wrote:
Mon May 06, 2019 10:48 am
hzak wrote:
Sat Jan 26, 2019 4:50 pm
With several months hardware, The Raspberry Pi 3B and 3B+ can finally run Android 9 pie system.

Features:
1. Bootloader: u-boot as AndroidThings on RPi 3B v.1.0.4, run on 64-bit mode
2. Kernel: v.4.14.71 run on 64-bit mode
3. Display: 720p(1280×720) @ 60Hz through on board HDMI port
4. Audio: analog, 2 channel through on board audio jack
5. WiFi: 2.4G (RPi 3B & 3B+), 5G (RPi 3B+)
6. Bluetooth: HCI over UART(ttyAMA0), RPi 3B: 921600bps no flow control; RPi 3B+: 3000000bps with flow control with a2dp and bt-pan(no test yet) support.
7. Ethernet: both work, and IP from DHCP
8. OpenGL render: based on mesa3d vc4 driver.
9. Hardware composer based on drm_hwcomposer (overlay has been disabled due to mis-compose in some satuation)

Knowing issue:
1. Enable `Debug GPU overdraw’ in system settings will make app crash
2. Enable `Debug non-retangular clip operations’ in system settings will make app crash
3. Do not disable `Disable HW overlays’ in system settings
4. Audio over HDMI not support
5. Can not play video

You can check the demo video on youtube at https://youtu.be/tJJetgz53OI (Normal record speed)
The performance is quite acceptable

The image can be download from https://www.brobwind.com/wp-content/upl ... f2b.bin.gz

Thanks
I can’t get it to boot!

On boot up i get
Waiting for PHY auto negotiation to complete........ TIMEOUT!
Startup failed

I saw online that it has something to do with not getting an ethernet connection (which doesn’t make sense as why would it need a network connection to boot up?)...

I’ve connected it through ethernet and now instead of “TIMEOUT!” It says “done”. But then lists “broadcast 1” all the way to “broadcast 17” and then says “time exceeded; starting again”... it them starts over and the same issue occurs.

I’m using the image you’ve uploaded to github and I’ve flashed it exactly step by step just like you’ve done in the video. I even tried using both etcher and win32diskimager, but still with the same issue.

I’m trying to run it on a rpi 3B+ using USB boot, maybe that has something to do with the error?
I didn't encounter such a problem.
Maybe you can debug the boot progress by using following instruction:
https://www.raspberrypi.org/documentati ... bootmodes/
That won’t work since without a properly running OS, I can’t run the commands to enable it. Not sure what to do at this point, I’ve tried re-flashing the image several times, but still get the same issue. Even tried re-downloading it. But to no avail.

If you don’t mind, can you please re-upload it to github? Maybe it got corrupted when you initially uploaded it.

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Tue May 07, 2019 4:03 pm

ikk wrote:
Mon May 06, 2019 5:34 pm

That won’t work since without a properly running OS, I can’t run the commands to enable it. Not sure what to do at this point, I’ve tried re-flashing the image several times, but still get the same issue. Even tried re-downloading it. But to no avail.

If you don’t mind, can you please re-upload it to github? Maybe it got corrupted when you initially uploaded it.
The sha1sum of the uncompressed binary file is 13fa20076fc0bfbd773c00f5f74d8abcbda25b21:

Code: Select all

$ zcat 2019_03_02_rpi3_13fa200.bin.gz | sha1sum -
13fa20076fc0bfbd773c00f5f74d8abcbda25b21  -
(You should flash the uncompressed binary file)

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Wed May 08, 2019 10:57 am

hzak wrote:
Tue May 07, 2019 4:03 pm
ikk wrote:
Mon May 06, 2019 5:34 pm

That won’t work since without a properly running OS, I can’t run the commands to enable it. Not sure what to do at this point, I’ve tried re-flashing the image several times, but still get the same issue. Even tried re-downloading it. But to no avail.

If you don’t mind, can you please re-upload it to github? Maybe it got corrupted when you initially uploaded it.
The sha1sum of the uncompressed binary file is 13fa20076fc0bfbd773c00f5f74d8abcbda25b21:

Code: Select all

$ zcat 2019_03_02_rpi3_13fa200.bin.gz | sha1sum -
13fa20076fc0bfbd773c00f5f74d8abcbda25b21  -
(You should flash the uncompressed binary file)
I’m getting a different sha1sum value:
Image

Not sure whether I’m using sha1sum properly

Edit: I tried re-downloading the image from github again, the sha1sum value is still different than the one you posted... it’s the same as the one in the picture I posted in this post

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Thu May 09, 2019 4:32 pm

ikk wrote:
Wed May 08, 2019 10:57 am

I’m getting a different sha1sum value:
Image

Not sure whether I’m using sha1sum properly

Edit: I tried re-downloading the image from github again, the sha1sum value is still different than the one you posted... it’s the same as the one in the picture I posted in this post
Please extract the binary file with following command firstly:

Code: Select all

$ gunzip 2019_03_02_rpi3_13fa200.bin.gz

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Thu May 09, 2019 8:10 pm

hzak wrote:
Thu May 09, 2019 4:32 pm
ikk wrote:
Wed May 08, 2019 10:57 am

I’m getting a different sha1sum value:
Image

Not sure whether I’m using sha1sum properly

Edit: I tried re-downloading the image from github again, the sha1sum value is still different than the one you posted... it’s the same as the one in the picture I posted in this post
Please extract the binary file with following command firstly:

Code: Select all

$ gunzip 2019_03_02_rpi3_13fa200.bin.gz
Ok now i get the correct sha1sum value:

Image

Not sure what to do now

hzak
Posts: 37
Joined: Sat Jan 26, 2019 4:32 pm

Re: Android Pie on RPi 3B(+) with hardware acceleration

Fri May 10, 2019 4:49 pm

ikk wrote:
Thu May 09, 2019 8:10 pm
hzak wrote:
Thu May 09, 2019 4:32 pm
ikk wrote:
Wed May 08, 2019 10:57 am

I’m getting a different sha1sum value:
Image

Not sure whether I’m using sha1sum properly

Edit: I tried re-downloading the image from github again, the sha1sum value is still different than the one you posted... it’s the same as the one in the picture I posted in this post
Please extract the binary file with following command firstly:

Code: Select all

$ gunzip 2019_03_02_rpi3_13fa200.bin.gz
Ok now i get the correct sha1sum value:

Image
Flash the uncompressed image

Not sure what to do now

ikk
Posts: 55
Joined: Sat Feb 09, 2019 12:39 am

Re: Android Pie on RPi 3B(+) with hardware acceleration

Fri May 10, 2019 9:08 pm

hzak wrote:
Fri May 10, 2019 4:49 pm
ikk wrote:
Thu May 09, 2019 8:10 pm
hzak wrote:
Thu May 09, 2019 4:32 pm


Please extract the binary file with following command firstly:

Code: Select all

$ gunzip 2019_03_02_rpi3_13fa200.bin.gz
Ok now i get the correct sha1sum value:

Image

Not sure what to do now
Flash the uncompressed image
Won’t let me:
Image

Edit: I flashed it using

Code: Select all

blkid /dev/sda
dd if=2019_03_02_rpi3_13fa200.bin of=/dev/sda bs=4MiB
Then I followed the rest of the instructions on your video... I still get the same PHY auto negotiation error on boot up :/

Return to “Android”