Raspberry Pi Forums

Posted: **Thu Feb 28, 2019 4:23 pm**

licux wrote: ↑
Wed Feb 27, 2019 12:18 pm

hzak wrote: ↑
Fri Feb 15, 2019 5:50 pm

Mister_Ed wrote: ↑
Fri Feb 15, 2019 8:53 am

I builded it from the source per as you described.

Now I have the images boot.img, rpiboot.img system.img, vendor.img and userdata.img.

Can you please describe how to write the images to a sdcard?
I have tried making partitions manually and writing the data from the images to it but it doesn't boot.

Thanks.
The instructions can be found here: https://github.com/brobwind/pie-device- ... /README.md
I will upload a script to create partition later.

Thanks.
Hi,

I want to know how to launch u-boot to write Android images on Raspberry Pi.
I think it is necessary to write some files including u-boot.bin to SD card.

Is detail procudere described somewhere except for below page?
https://github.com/brobwind/pie-device- ... /README.md

Thanks.

You call follow this guide to setup serial console: https://developer.android.com/things/ha ... al-console
While system boot up, press any key to interrupt auto bootup and enter u-boot interactive mode, then run 'run fastbootcmd' command to make the bootloader enter fastboot mode, then you can use fastboot command to flash images. (assuming wired network connected)
The 'u-boot' is in the rpiboot.img (a vfat filesystem) named u-boot-dtok.bin.

Hope it helps.

Posted: **Fri Mar 01, 2019 3:00 am**

Great job, I think this is the best Android implementation yet.
Are you still planning to make all the source available?

Regards

Posted: **Fri Mar 01, 2019 9:13 am**

hzak wrote: ↑
Mon Feb 25, 2019 9:22 pm

(Apply HDMI related parameters in config.txt will not take effect, that's why I apply it on kernel?)

I did discover this problem with HDMI parameters in config.txt too on the releases from Konsta so then I decided to give it a try using the information I found in:

https://www.raspberrypi.org/forums/view ... p?t=159853

which gives you arm side v3d driver, supporting desktop GL from X, but using the original firmware for the kms part.

Using this, the changes in the HDMI settings were applied as expected.

I have absolutely no idea if this is usable information for you and I'm a total noob if it comes to programming so this might make no sense at all but I just wanted to let you know how I was able to get the resolution changed on Konsta's release (Lineage 14 / Android 7.1.2).

I still have no clue how to get yours working on my HD TV at home. I did not fiend enough information on how to compile new edid file for other than 720p resolution. I searched in the source that are in your rpi-device tree but was unable to find it.

Maybe you can give a little more information where to start?

Thank you.

Posted: **Sat Mar 02, 2019 5:33 pm**

Dobbey wrote: ↑
Fri Mar 01, 2019 3:00 am
Great job, I think this is the best Android implementation yet.
Are you still planning to make all the source available?

Regards

I have upload all the source code, you can get instructions from https://github.com/brobwind/pie-device- ... /README.md
You can also download the prebuilt image from https://www.brobwind.com/wp-content/upl ... 200.bin.gz
The system performance is much better than before:

And the Raspbery Pi 3 Model B+ performance is even better:

Thanks

Posted: **Sat Mar 02, 2019 6:02 pm**

Mister_Ed wrote: ↑
Fri Mar 01, 2019 9:13 am

hzak wrote: ↑
Mon Feb 25, 2019 9:22 pm

(Apply HDMI related parameters in config.txt will not take effect, that's why I apply it on kernel?)

I did discover this problem with HDMI parameters in config.txt too on the releases from Konsta so then I decided to give it a try using the information I found in:

https://www.raspberrypi.org/forums/view ... p?t=159853

which gives you arm side v3d driver, supporting desktop GL from X, but using the original firmware for the kms part.

Using this, the changes in the HDMI settings were applied as expected.

I have absolutely no idea if this is usable information for you and I'm a total noob if it comes to programming so this might make no sense at all but I just wanted to let you know how I was able to get the resolution changed on Konsta's release (Lineage 14 / Android 7.1.2).

I think the fkms v3d driver can not work with the mesa3d OpenGL driver, so I had to use kms v3d driver.
I still cannot download Konsta's release in my country, have not chance to try it.

I still have no clue how to get yours working on my HD TV at home. I did not fiend enough information on how to compile new edid file for other than 720p resolution. I searched in the source that are in your rpi-device tree but was unable to find it.

Maybe you can give a little more information where to start?

Thank you.

Please try this:
1. Get EDID file from another OS(raspbian) by using read-edid command, refer from:
- https://unix.stackexchange.com/question ... le-monitor
- http://manpages.ubuntu.com/manpages/tru ... did.1.html
2. Place the EDID file to the kernel source tree at firmware/edid/ folder and modify arch/arm64/configs/bcmrpi3_defconfig append the EDID file path at the end of the CONFIG_EXTRA_FIRMWARE.
3. Rebuild kernel and boot image
4. Modify kernel parameter: drm_kms_helper.edid_firmware=edid/1280x720.bin in device/brobwind/rpi3/boot/rpiboot/cmdline.txt and rebuild rpiboot image.
5 Flash rpiboot and boot image.

Posted: **Sat Mar 02, 2019 9:14 pm**

Thanks for releasing all the source, I have not had a chance to build from source yet.
I was looking a the release source but I do not see any of your commits to any of the following repos:
minigbm
drm_hwcomposer
mesa3d
Maybe you can clarify if I missed something.

Regards

Posted: **Sun Mar 03, 2019 1:58 am**

Dobbey wrote: ↑
Sat Mar 02, 2019 9:14 pm
Thanks for releasing all the source, I have not had a chance to build from source yet.
I was looking a the release source but I do not see any of your commits to any of the following repos:
minigbm
drm_hwcomposer
mesa3d
Maybe you can clarify if I missed something.

Regards

They are all in the pie-device-brobwind-rpi3 branch.
To simplify the download process, I place the download info in the local manifest: https://github.com/brobwind/pie-device- ... nifest.xml

All you need to do is download pie-device-brobwind-rpi3 (https://github.com/brobwind/pie-device- ... ource-code) and run `repo sync`.

mingbm -> device/brobwinnd/rpi3/hals/display/minigbm

drm_hwcomposer -> device/brobwind/rpi3/hals/display/drm_hwcomposer

mesa3d -> device/brobwind/rpi3/hals/display/mesa3d

Posted: **Sun Mar 03, 2019 2:15 am**

hzak wrote: ↑
Sun Mar 03, 2019 1:58 am

Dobbey wrote: ↑
Sat Mar 02, 2019 9:14 pm
Thanks for releasing all the source, I have not had a chance to build from source yet.
I was looking a the release source but I do not see any of your commits to any of the following repos:
minigbm
drm_hwcomposer
mesa3d
Maybe you can clarify if I missed something.

Regards
They are all in the pie-device-brobwind-rpi3 branch.
To simplify the download process, I place the download info in the local manifest: https://github.com/brobwind/pie-device- ... nifest.xml

All you need to do is download pie-device-brobwind-rpi3 (https://github.com/brobwind/pie-device- ... ource-code) and run `repo sync`.
mingbm -> device/brobwinnd/rpi3/hals/display/minigbm

drm_hwcomposer -> device/brobwind/rpi3/hals/display/drm_hwcomposer

mesa3d -> device/brobwind/rpi3/hals/display/mesa3d

Thanks,
I did not see the branch you created

Regards

Posted: **Tue Mar 05, 2019 8:02 am**

Hello!
No video in YouTube and in some other apps. Notices on the lack of codecs. Is it as should be? Or I doing something wrong?

Posted: **Tue Mar 05, 2019 4:23 pm**

sungale wrote: ↑
Tue Mar 05, 2019 8:02 am
Hello!
No video in YouTube and in some other apps. Notices on the lack of codecs. Is it as should be? Or I doing something wrong?

It can use software decoder, but need following patches to work:
framework/av:
diff --git a/media/libstagefright/colorconversion/SoftwareRenderer.cpp b/media/libstagefright/colorconversion/SoftwareRenderer.cpp
index 657a05b..8f2115d 100644
--- a/media/libstagefright/colorconversion/SoftwareRenderer.cpp
+++ b/media/libstagefright/colorconversion/SoftwareRenderer.cpp
@@ -126,9 +126,6 @@ void SoftwareRenderer::resetFormatIfChanged(
case OMX_COLOR_FormatYUV420SemiPlanar:
case OMX_TI_COLOR_FormatYUV420PackedSemiPlanar:
{
- halFormat = HAL_PIXEL_FORMAT_YV12;
- bufWidth = (mCropWidth + 1) & ~1;
- bufHeight = (mCropHeight + 1) & ~1;
break;
}
case OMX_COLOR_Format24bitRGB888:

device/brobwind/rpi3/hals/display/minigbm:
diff --git a/vc4.c b/vc4.c
index b3efd79..097a629 100644
--- a/vc4.c
+++ b/vc4.c
@@ -17,7 +17,7 @@
#include "util.h"

static const uint32_t render_target_formats[] = { DRM_FORMAT_ABGR8888, DRM_FORMAT_BGR565,
- DRM_FORMAT_XBGR8888 };
+ DRM_FORMAT_XBGR8888, DRM_FORMAT_RGB565 };

static int vc4_init(struct driver *drv)
{

-------------------
Thanks to brask comments at https://www.brobwind.com/archives/1541#comment-430

Posted: **Tue Mar 05, 2019 11:14 pm**

Hi,
I did launch Android in RPI3+.

It seems that i2c and SPI could not be used yet. Is it right?

Posted: **Wed Mar 06, 2019 1:04 pm**

I built it.

Posted: **Fri Mar 08, 2019 3:57 pm**

licux wrote: ↑
Tue Mar 05, 2019 11:14 pm
Hi,
I did launch Android in RPI3+.

It seems that i2c and SPI could not be used yet. Is it right?

I have already ordered a sense HAT. I will check if it can work or not.

Posted: **Sat Mar 09, 2019 1:42 am**

hzak wrote: ↑
Tue Mar 05, 2019 4:23 pm
It can use software decoder, but need following patches to work:
...

Thanks it's been helpful.
I had troubles with audio. The following helped solve they. In file config.txt:

hdmi_drive=1
hdmi_ignore_edid_audio=1

BT works very unstable

Posted: **Mon Mar 11, 2019 6:47 pm**

hzak wrote: ↑
Tue Mar 05, 2019 4:23 pm

sungale wrote: ↑
Tue Mar 05, 2019 8:02 am
Hello!
No video in YouTube and in some other apps. Notices on the lack of codecs. Is it as should be? Or I doing something wrong?
It can use software decoder, but need following patches to work:
framework/av:
diff --git a/media/libstagefright/colorconversion/SoftwareRenderer.cpp b/media/libstagefright/colorconversion/SoftwareRenderer.cpp
index 657a05b..8f2115d 100644
--- a/media/libstagefright/colorconversion/SoftwareRenderer.cpp
+++ b/media/libstagefright/colorconversion/SoftwareRenderer.cpp
@@ -126,9 +126,6 @@ void SoftwareRenderer::resetFormatIfChanged(
case OMX_COLOR_FormatYUV420SemiPlanar:
case OMX_TI_COLOR_FormatYUV420PackedSemiPlanar:
{
- halFormat = HAL_PIXEL_FORMAT_YV12;
- bufWidth = (mCropWidth + 1) & ~1;
- bufHeight = (mCropHeight + 1) & ~1;
break;
}
case OMX_COLOR_Format24bitRGB888:

device/brobwind/rpi3/hals/display/minigbm:
diff --git a/vc4.c b/vc4.c
index b3efd79..097a629 100644
--- a/vc4.c
+++ b/vc4.c
@@ -17,7 +17,7 @@
#include "util.h"

static const uint32_t render_target_formats[] = { DRM_FORMAT_ABGR8888, DRM_FORMAT_BGR565,
- DRM_FORMAT_XBGR8888 };
+ DRM_FORMAT_XBGR8888, DRM_FORMAT_RGB565 };

static int vc4_init(struct driver *drv)
{

-------------------
Thanks to brask comments at https://www.brobwind.com/archives/1541#comment-430

Hello. Sorry for bad english. Can someone post a img file with activated software decoding? Thank.

Posted: **Tue Mar 12, 2019 5:42 pm**

noctiuagus wrote: ↑
Mon Mar 11, 2019 6:47 pm

hzak wrote: ↑
Tue Mar 05, 2019 4:23 pm

sungale wrote: ↑
Tue Mar 05, 2019 8:02 am
Hello!
No video in YouTube and in some other apps. Notices on the lack of codecs. Is it as should be? Or I doing something wrong?
It can use software decoder, but need following patches to work:
framework/av:
diff --git a/media/libstagefright/colorconversion/SoftwareRenderer.cpp b/media/libstagefright/colorconversion/SoftwareRenderer.cpp
index 657a05b..8f2115d 100644
--- a/media/libstagefright/colorconversion/SoftwareRenderer.cpp
+++ b/media/libstagefright/colorconversion/SoftwareRenderer.cpp
@@ -126,9 +126,6 @@ void SoftwareRenderer::resetFormatIfChanged(
case OMX_COLOR_FormatYUV420SemiPlanar:
case OMX_TI_COLOR_FormatYUV420PackedSemiPlanar:
{
- halFormat = HAL_PIXEL_FORMAT_YV12;
- bufWidth = (mCropWidth + 1) & ~1;
- bufHeight = (mCropHeight + 1) & ~1;
break;
}
case OMX_COLOR_Format24bitRGB888:

device/brobwind/rpi3/hals/display/minigbm:
diff --git a/vc4.c b/vc4.c
index b3efd79..097a629 100644
--- a/vc4.c
+++ b/vc4.c
@@ -17,7 +17,7 @@
#include "util.h"

static const uint32_t render_target_formats[] = { DRM_FORMAT_ABGR8888, DRM_FORMAT_BGR565,
- DRM_FORMAT_XBGR8888 };
+ DRM_FORMAT_XBGR8888, DRM_FORMAT_RGB565 };

static int vc4_init(struct driver *drv)
{

-------------------
Thanks to brask comments at https://www.brobwind.com/archives/1541#comment-430
Hello. Sorry for bad english. Can someone post a img file with activated software decoding? Thank.

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

Posted: **Tue Mar 12, 2019 5:50 pm**

sungale wrote: ↑
Sat Mar 09, 2019 1:42 am

hzak wrote: ↑
Tue Mar 05, 2019 4:23 pm
It can use software decoder, but need following patches to work:
...
Thanks it's been helpful.
I had troubles with audio. The following helped solve they. In file config.txt:

hdmi_drive=1
hdmi_ignore_edid_audio=1

BT works very unstable

I think the audio can only output from on-board audio jack and bluetooth (a2dp). And audio over HDMI isn't work.
Does declare these two hdmi related parameter can make the audio go through the HDMI?

Due to the system take too much memory and slow I/O performance(TF card), the BT related process will be killed by low memory killer. I don't know how to fix it.

Posted: **Sat Mar 16, 2019 8:16 am**

hzak wrote: ↑
Sat Mar 02, 2019 6:02 pm

Mister_Ed wrote: ↑
Fri Mar 01, 2019 9:13 am

hzak wrote: ↑
Mon Feb 25, 2019 9:22 pm

(Apply HDMI related parameters in config.txt will not take effect, that's why I apply it on kernel?)

I did discover this problem with HDMI parameters in config.txt too on the releases from Konsta so then I decided to give it a try using the information I found in:

viewtopic.php?t=159853

which gives you arm side v3d driver, supporting desktop GL from X, but using the original firmware for the kms part.

Using this, the changes in the HDMI settings were applied as expected.

I have absolutely no idea if this is usable information for you and I'm a total noob if it comes to programming so this might make no sense at all but I just wanted to let you know how I was able to get the resolution changed on Konsta's release (Lineage 14 / Android 7.1.2).
I think the fkms v3d driver can not work with the mesa3d OpenGL driver, so I had to use kms v3d driver.
I still cannot download Konsta's release in my country, have not chance to try it.

I still have no clue how to get yours working on my HD TV at home. I did not fiend enough information on how to compile new edid file for other than 720p resolution. I searched in the source that are in your rpi-device tree but was unable to find it.

Maybe you can give a little more information where to start?

Thank you.
Please try this:
1. Get EDID file from another OS(raspbian) by using read-edid command, refer from:
- https://unix.stackexchange.com/question ... le-monitor
- http://manpages.ubuntu.com/manpages/tru ... did.1.html
2. Place the EDID file to the kernel source tree at firmware/edid/ folder and modify arch/arm64/configs/bcmrpi3_defconfig append the EDID file path at the end of the CONFIG_EXTRA_FIRMWARE.
3. Rebuild kernel and boot image
4. Modify kernel parameter: drm_kms_helper.edid_firmware=edid/1280x720.bin in device/brobwind/rpi3/boot/rpiboot/cmdline.txt and rebuild rpiboot image.
5 Flash rpiboot and boot image.

Hi,

I was able to run raspbian at home on my TV.

But the get-edid command does not produce any information because it is unable to detect edid.
So it seems my TV does not provide edid data.
Strangely, all other Linux distribs work well without this problem with the display on my TV.

The TV is an older Samsung LCD television.

I hope that you can do something in you source to make it work on my TV too.

Thank you.

Best regards,

Posted: **Sat Mar 16, 2019 4:04 pm**

Mister_Ed wrote: ↑
Sat Mar 16, 2019 8:16 am

Hi,

I was able to run raspbian at home on my TV.

But the get-edid command does not produce any information because it is unable to detect edid.
So it seems my TV does not provide edid data.
Strangely, all other Linux distribs work well without this problem with the display on my TV.

The TV is an older Samsung LCD television.

I hope that you can do something in you source to make it work on my TV too.

Thank you.

Best regards,

Please tell me the LCD resolution and I will try to figure it out.

Posted: **Sat Mar 16, 2019 4:13 pm**

The resolution is 1920 x 1080 @ 50 Hz

Thank you for the effort.

Best regards.

Posted: **Mon Mar 18, 2019 8:49 am**

Hi,

I have downloaded the source from https://github.com/brobwind/pie-device-brobwind-rpi3 and followed https://github.com/brobwind/pie-device- ... /README.md instructions. I am getting the below error. Am i missing something?

01-01 00:57:29.934 2712 2712 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 2712 (surfaceflinger), pid 2712 (surfaceflinger)
01-01 00:57:29.996 2736 2736 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 00:57:29.996 2736 2736 F DEBUG : Build fingerprint: 'Android/rpi3/rpi3:9/PPR2.180905.006.A1/rp93399703141207:eng/test-keys'
01-01 00:57:29.996 2736 2736 F DEBUG : Revision: '0'
01-01 00:57:29.996 2736 2736 F DEBUG : ABI: 'arm'
01-01 00:57:29.996 2736 2736 F DEBUG : pid: 2712, tid: 2712, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
01-01 00:57:29.996 2736 2736 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-01 00:57:29.996 2736 2736 F DEBUG : Abort message: 'couldn't find an OpenGL ES implementation'
01-01 00:57:29.996 2736 2736 F DEBUG : r0 00000000 r1 00000a98 r2 00000006 r3 f581f4c0
01-01 00:57:29.996 2736 2736 F DEBUG : r4 00000a98 r5 00000a98 r6 ffca02dc r7 0000010c
01-01 00:57:29.996 2736 2736 F DEBUG : r8 00000000 r9 00000000 r10 00000001 r11 f52647e8
01-01 00:57:29.996 2736 2736 F DEBUG : ip 00000000 sp ffca02c8 lr f57aaf9d pc f57a2d2a
01-01 00:57:30.033 2736 2736 F DEBUG :
01-01 00:57:30.033 2736 2736 F DEBUG : backtrace:
01-01 00:57:30.033 2736 2736 F DEBUG : #00 pc 0001cd2a /system/lib/libc.so (abort+62)
01-01 00:57:30.034 2736 2736 F DEBUG : #01 pc 00006dd5 /system/lib/liblog.so (__android_log_assert+156)
01-01 00:57:30.034 2736 2736 F DEBUG : #02 pc 000106cf /system/lib/libEGL.so (android::Loader::open(android::egl_connection_t*)+462)
01-01 00:57:30.034 2736 2736 F DEBUG : #03 pc 0000bc27 /system/lib/libEGL.so (android::egl_init_drivers()+54)
01-01 00:57:30.034 2736 2736 F DEBUG : #04 pc 0000be17 /system/lib/libEGL.so (eglGetDisplay+66)
01-01 00:57:30.034 2736 2736 F DEBUG : #05 pc 0006c667 /system/lib/libsurfaceflinger.so (android::RE::impl::RenderEngine::create(int, unsigned int)+26)
01-01 00:57:30.034 2736 2736 F DEBUG : #06 pc 00070519 /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::init()+600)
01-01 00:57:30.034 2736 2736 F DEBUG : #07 pc 00002679 /system/bin/surfaceflinger (main+232)
01-01 00:57:30.034 2736 2736 F DEBUG : #08 pc 0008bac9 /system/lib/libc.so (__libc_init+48)
01-01 00:57:30.034 2736 2736 F DEBUG : #09 pc 0000254f /system/bin/surfaceflinger (_start_main+46)
01-01 00:57:30.034 2736 2736 F DEBUG : #10 pc 00018037 /system/bin/linker (__dl__ZN6soinfoD1Ev+14)
01-01 00:57:30.034 2736 2736 F DEBUG : #11 pc 00020bda [stack:ffc80000]

Posted: **Mon Mar 18, 2019 10:08 am**

hzak wrote: ↑
Sat Mar 02, 2019 6:02 pm

I still cannot download Konsta's release in my country, have not chance to try it.

If you want it I can upload the image to you anywhere.

I don't know if this is okay by Konstakang?

Anyway, just let me know if you would like to have it I will ask Konsta if I'm allowed to upload it to you.

I think you would benefit.

Best regards,

Posted: **Mon Mar 18, 2019 4:41 pm**

ramkumarpothiraj wrote: ↑
Mon Mar 18, 2019 8:49 am
Hi,

I have downloaded the source from https://github.com/brobwind/pie-device-brobwind-rpi3 and followed https://github.com/brobwind/pie-device- ... /README.md instructions. I am getting the below error. Am i missing something?

01-01 00:57:29.934 2712 2712 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 2712 (surfaceflinger), pid 2712 (surfaceflinger)
01-01 00:57:29.996 2736 2736 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 00:57:29.996 2736 2736 F DEBUG : Build fingerprint: 'Android/rpi3/rpi3:9/PPR2.180905.006.A1/rp93399703141207:eng/test-keys'
01-01 00:57:29.996 2736 2736 F DEBUG : Revision: '0'
01-01 00:57:29.996 2736 2736 F DEBUG : ABI: 'arm'
01-01 00:57:29.996 2736 2736 F DEBUG : pid: 2712, tid: 2712, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
01-01 00:57:29.996 2736 2736 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-01 00:57:29.996 2736 2736 F DEBUG : Abort message: 'couldn't find an OpenGL ES implementation'
01-01 00:57:29.996 2736 2736 F DEBUG : r0 00000000 r1 00000a98 r2 00000006 r3 f581f4c0
01-01 00:57:29.996 2736 2736 F DEBUG : r4 00000a98 r5 00000a98 r6 ffca02dc r7 0000010c
01-01 00:57:29.996 2736 2736 F DEBUG : r8 00000000 r9 00000000 r10 00000001 r11 f52647e8
01-01 00:57:29.996 2736 2736 F DEBUG : ip 00000000 sp ffca02c8 lr f57aaf9d pc f57a2d2a
01-01 00:57:30.033 2736 2736 F DEBUG :
01-01 00:57:30.033 2736 2736 F DEBUG : backtrace:
01-01 00:57:30.033 2736 2736 F DEBUG : #00 pc 0001cd2a /system/lib/libc.so (abort+62)
01-01 00:57:30.034 2736 2736 F DEBUG : #01 pc 00006dd5 /system/lib/liblog.so (__android_log_assert+156)
01-01 00:57:30.034 2736 2736 F DEBUG : #02 pc 000106cf /system/lib/libEGL.so (android::Loader::open(android::egl_connection_t*)+462)
01-01 00:57:30.034 2736 2736 F DEBUG : #03 pc 0000bc27 /system/lib/libEGL.so (android::egl_init_drivers()+54)
01-01 00:57:30.034 2736 2736 F DEBUG : #04 pc 0000be17 /system/lib/libEGL.so (eglGetDisplay+66)
01-01 00:57:30.034 2736 2736 F DEBUG : #05 pc 0006c667 /system/lib/libsurfaceflinger.so (android::RE::impl::RenderEngine::create(int, unsigned int)+26)
01-01 00:57:30.034 2736 2736 F DEBUG : #06 pc 00070519 /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::init()+600)
01-01 00:57:30.034 2736 2736 F DEBUG : #07 pc 00002679 /system/bin/surfaceflinger (main+232)
01-01 00:57:30.034 2736 2736 F DEBUG : #08 pc 0008bac9 /system/lib/libc.so (__libc_init+48)
01-01 00:57:30.034 2736 2736 F DEBUG : #09 pc 0000254f /system/bin/surfaceflinger (_start_main+46)
01-01 00:57:30.034 2736 2736 F DEBUG : #10 pc 00018037 /system/bin/linker (__dl__ZN6soinfoD1Ev+14)
01-01 00:57:30.034 2736 2736 F DEBUG : #11 pc 00020bda [stack:ffc80000]

From the message 'Abort message: 'couldn't find an OpenGL ES implementation''
It seems the OpenGL driver hasn't included in the system/vendor image. Please check if the libGLES_mesa.so present in the vendor/lib/egl/ folder. Or execute following commands to make one:

Code: Select all

$ . build/envsetup.sh
$ lunch rpi3-eng
$ m libGLES_mesa gralloc.drm hwcomposer.drm

Posted: **Mon Mar 18, 2019 4:51 pm**

Mister_Ed wrote: ↑
Mon Mar 18, 2019 10:08 am

hzak wrote: ↑
Sat Mar 02, 2019 6:02 pm

I still cannot download Konsta's release in my country, have not chance to try it.

If you want it I can upload the image to you anywhere.

I don't know if this is okay by Konstakang?

Anyway, just let me know if you would like to have it I will ask Konsta if I'm allowed to upload it to you.

I think you would benefit.

Best regards,

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

My email address: brobwind _at_ gmail.com

Thanks.

Posted: **Tue Mar 19, 2019 7:15 am**

hzak wrote: ↑
Mon Mar 18, 2019 4:41 pm

ramkumarpothiraj wrote: ↑
Mon Mar 18, 2019 8:49 am
Hi,

I have downloaded the source from https://github.com/brobwind/pie-device-brobwind-rpi3 and followed https://github.com/brobwind/pie-device- ... /README.md instructions. I am getting the below error. Am i missing something?

01-01 00:57:29.934 2712 2712 F libc : Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 2712 (surfaceflinger), pid 2712 (surfaceflinger)
01-01 00:57:29.996 2736 2736 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-01 00:57:29.996 2736 2736 F DEBUG : Build fingerprint: 'Android/rpi3/rpi3:9/PPR2.180905.006.A1/rp93399703141207:eng/test-keys'
01-01 00:57:29.996 2736 2736 F DEBUG : Revision: '0'
01-01 00:57:29.996 2736 2736 F DEBUG : ABI: 'arm'
01-01 00:57:29.996 2736 2736 F DEBUG : pid: 2712, tid: 2712, name: surfaceflinger >>> /system/bin/surfaceflinger <<<
01-01 00:57:29.996 2736 2736 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-01 00:57:29.996 2736 2736 F DEBUG : Abort message: 'couldn't find an OpenGL ES implementation'
01-01 00:57:29.996 2736 2736 F DEBUG : r0 00000000 r1 00000a98 r2 00000006 r3 f581f4c0
01-01 00:57:29.996 2736 2736 F DEBUG : r4 00000a98 r5 00000a98 r6 ffca02dc r7 0000010c
01-01 00:57:29.996 2736 2736 F DEBUG : r8 00000000 r9 00000000 r10 00000001 r11 f52647e8
01-01 00:57:29.996 2736 2736 F DEBUG : ip 00000000 sp ffca02c8 lr f57aaf9d pc f57a2d2a
01-01 00:57:30.033 2736 2736 F DEBUG :
01-01 00:57:30.033 2736 2736 F DEBUG : backtrace:
01-01 00:57:30.033 2736 2736 F DEBUG : #00 pc 0001cd2a /system/lib/libc.so (abort+62)
01-01 00:57:30.034 2736 2736 F DEBUG : #01 pc 00006dd5 /system/lib/liblog.so (__android_log_assert+156)
01-01 00:57:30.034 2736 2736 F DEBUG : #02 pc 000106cf /system/lib/libEGL.so (android::Loader::open(android::egl_connection_t*)+462)
01-01 00:57:30.034 2736 2736 F DEBUG : #03 pc 0000bc27 /system/lib/libEGL.so (android::egl_init_drivers()+54)
01-01 00:57:30.034 2736 2736 F DEBUG : #04 pc 0000be17 /system/lib/libEGL.so (eglGetDisplay+66)
01-01 00:57:30.034 2736 2736 F DEBUG : #05 pc 0006c667 /system/lib/libsurfaceflinger.so (android::RE::impl::RenderEngine::create(int, unsigned int)+26)
01-01 00:57:30.034 2736 2736 F DEBUG : #06 pc 00070519 /system/lib/libsurfaceflinger.so (android::SurfaceFlinger::init()+600)
01-01 00:57:30.034 2736 2736 F DEBUG : #07 pc 00002679 /system/bin/surfaceflinger (main+232)
01-01 00:57:30.034 2736 2736 F DEBUG : #08 pc 0008bac9 /system/lib/libc.so (__libc_init+48)
01-01 00:57:30.034 2736 2736 F DEBUG : #09 pc 0000254f /system/bin/surfaceflinger (_start_main+46)
01-01 00:57:30.034 2736 2736 F DEBUG : #10 pc 00018037 /system/bin/linker (__dl__ZN6soinfoD1Ev+14)
01-01 00:57:30.034 2736 2736 F DEBUG : #11 pc 00020bda [stack:ffc80000]
From the message 'Abort message: 'couldn't find an OpenGL ES implementation''
It seems the OpenGL driver hasn't included in the system/vendor image. Please check if the libGLES_mesa.so present in the vendor/lib/egl/ folder. Or execute following commands to make one:
Code: Select all
$ . build/envsetup.sh
$ lunch rpi3-eng
$ m libGLES_mesa gralloc.drm hwcomposer.drm

Thanks for your time hzak. I have not cloned drm_hwcomposer, mesa3d and minigdm git repos to device/brobwind/rpi3/hals/display. With this the error is gone and android ui is coming up.

Raspberry Pi Forums

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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