[DEV] LineageOS 15.1 (Android 8.1.0) for Raspberry Pi 3 B and B+

[Konsta]

Here’s my build of LineageOS 15.1 for Raspberry Pi 3 Model B and Model B+ (bluetooth does not currently work on the new plus model). It is unofficial and unsupported by the LineageOS team. It’s for advanced users only. This build currently uses Google’s SwiftShader software renderer so display performance is probably not what you’d expect. This build is not meant as a daily driver and it’s certainly not suitable for media device use.

Screenshot_Settings_20180630-144620.png (45.52 KiB) Viewed 56612 times

https://konstakang.com/devices/rpi3/LineageOS15.1/

Sources:

• lineage-rpi

[Konsta]

Pie on Pi! LineageOS 16 booted on Raspberry Pi3.

https://twitter.com/konstatuomio/status ... 8983569408

[globiboulga666]

Hi, very cool work !

Had you used an original Android Kernel 4.14, or an original Vanilla Kernel 4.14, or current Raspberry Pi modified Kernel 4.14 ?
Did you have to write HAL/HIDL layers for having Android to work ?

According to all the things written in there : https://source.android.com/devices/architecture/
It seems that there is a huge work to do if not already delivered by founders, and updated with new and new versions of Android.
But it also seems that Android 9 requirements about drivers will be able to permit Android System updates without reworking the others layers.

But I'm not sure I understand everything, and I'm not sure if all of this layers are made available for the RPi, so I guess there is a chance you didn't have to do all this ?

Thank you again !

[Konsta]

Hi, very cool work !

Had you used an original Android Kernel 4.14, or an original Vanilla Kernel 4.14, or current Raspberry Pi modified Kernel 4.14 ?
Did you have to write HAL/HIDL layers for having Android to work ?

According to all the things written in there : https://source.android.com/devices/architecture/
It seems that there is a huge work to do if not already delivered by founders, and updated with new and new versions of Android.
But it also seems that Android 9 requirements about drivers will be able to permit Android System updates without reworking the others layers.

But I'm not sure I understand everything, and I'm not sure if all of this layers are made available for the RPi, so I guess there is a chance you didn't have to do all this ?

Thank you again !

My kernel is a combination of official Raspberry kernel (https://github.com/raspberrypi/linux/tree/rpi-4.14.y) and Google's Android kernel (https://android.googlesource.com/kernel ... oid-4.14-p) with latest Android security patches which I've merged together and configured for this device and Android.

There's bunch of open source HALs (audio, gps, and light). Display HALs are currently from Android Things. Using whatever works is common in the Android custom ROM scene. Switching to mainline graphics and VC4 driver would be great if someone had the required skills and experience (not sure I do). HIDL HALs have been used since Oreo but many things can be worked around to support older HALs.

I'm not an OEM and I'm not shipping official Android so passing Google's CTS (Compatibility Test Suite) or certification doesn't really concern me. This is initially based on what Google has made available through AOSP (Android Open Source Project) with great improvements by the LineageOS team.

[globiboulga666]

Cool, it sounds pretty clear. Thank you for those explanations, as I'm trying to understand a maximum of things about all of this, and because I would have no idea of "how to transform Raspberry Pi Kernel 4.14 into an RPi Android Kernel 4.14 plus all of the things needed to have Android working", these details are giving me some help in my quest

[Konsta]

Cool, it sounds pretty clear. Thank you for those explanations, as I'm trying to understand a maximum of things about all of this, and because I would have no idea of "how to transform Raspberry Pi Kernel 4.14 into an RPi Android Kernel 4.14 plus all of the things needed to have Android working", these details are giving me some help in my quest

Good thing it's open source (https://github.com/lineage-rpi) so that makes your quest a lot easier.

[Samgivesls]

when everything is perfectly plugged in to my pi i just get a black screen when turning on the pi, is this an issue with my micro sd card or os? i have been using the monitor for multiple tests so i do not think that is the issue. power is good and everything. This has to be a boot issue but i used Win32DiskImager and Etcher and everything and it has not worked out! please help!

[Konsta]

when everything is perfectly plugged in to my pi i just get a black screen when turning on the pi, is this an issue with my micro sd card or os? i have been using the monitor for multiple tests so i do not think that is the issue. power is good and everything. This has to be a boot issue but i used Win32DiskImager and Etcher and everything and it has not worked out! please help!

More likely an issue with your display. You need to use a display that supports 720p resolution (it's the maximum resolution this build supports). Maybe try with a different display or modifying config.txt (https://www.raspberrypi.org/documentati ... t/video.md) for your current one?

[Samgivesls]

when everything is perfectly plugged in to my pi i just get a black screen when turning on the pi, is this an issue with my micro sd card or os? i have been using the monitor for multiple tests so i do not think that is the issue. power is good and everything. This has to be a boot issue but i used Win32DiskImager and Etcher and everything and it has not worked out! please help!

More likely an issue with your display. You need to use a display that supports 720p resolution (it's the maximum resolution this build supports). Maybe try with a different display or modifying config.txt (https://www.raspberrypi.org/documentati ... t/video.md) for your current one?

Now that i have tried a new display, it boots but, I have a certain variation of the "stuck rainbow screen" where it gets past the rainbow box but now there are rainbow pixels on the edge of the screen while the rest of the screen is black. I have tried messing with my config and everything, nothing works for me!

[Konsta]

Now that i have tried a new display, it boots but, I have a certain variation of the "stuck rainbow screen" where it gets past the rainbow box but now there are rainbow pixels on the edge of the screen while the rest of the screen is black. I have tried messing with my config and everything, nothing works for me!

Sorry, can't reproduce such issue so difficult to say. It's also difficult to get logs from the boot unless you have a serial console adapter. You could try LineageOS 14.1 build as well and see if you have better luck with that.

[shripal17]

Hi, can we control the gpio pins through shell commands? Does your kernel support it? If yes, would you mind writing a few sample commands for usage?

Thanks for your android builds, they're great!

[Konsta]

Hi, can we control the gpio pins through shell commands? Does your kernel support it? If yes, would you mind writing a few sample commands for usage?

Thanks for your android builds, they're great!

Yes, kernel supports it and you can control GPIO pins in shell. I haven't played around with this much, though. See e.g. viewtopic.php?t=193096

Some sample commands on Android:

Code: Select all

su
echo 18 > /sys/class/gpio/export

echo out > /sys/class/gpio/gpio18/direction
echo 1 > /sys/class/gpio/gpio18/value

cat /sys/class/gpio/gpio18/direction 
cat /sys/class/gpio/gpio18/value

echo 18 > /sys/class/gpio/unexport

[shripal17]

Hi, can we control the gpio pins through shell commands? Does your kernel support it? If yes, would you mind writing a few sample commands for usage?

Thanks for your android builds, they're great!

Yes, kernel supports it and you can control GPIO pins in shell. I haven't played around with this much, though. See e.g. viewtopic.php?t=193096

Some sample commands on Android:

Code: Select all

su
echo 18 > /sys/class/gpio/export

echo out > /sys/class/gpio/gpio18/direction
echo 1 > /sys/class/gpio/gpio18/value

cat /sys/class/gpio/gpio18/direction 
cat /sys/class/gpio/gpio18/value

echo 18 > /sys/class/gpio/unexport

Alright Thanks a lot great work
Your and previous contributions to aosp on RasPi open up a lot of new possibilities for RasPi!

[sundar247]

How do I enter into the recovery mode to install Gapps?

[Konsta]

How do I enter into the recovery mode to install Gapps?

Please read the FAQ on my site because there's a section that answers this question.

This build has been discontinued for ages and you should use my LineageOS 16.0 build (https://www.raspberrypi.org/forums/view ... 3&t=243832) instead anyway.

[vishal.shukla]

hi i am trying to install andriod pie on raspberry 4 my question is does raspberry 4 support the andriod pie if yes then which version

[Konsta]

hi i am trying to install andriod pie on raspberry 4 my question is does raspberry 4 support the andriod pie if yes then which version

Why post on an Android Oreo thread then?

There's no Android images publicly available for the Pi 4.

[derletztename]

Hey Konsta,
awesome job you did there. Thank you. I just have to tiny questions.
Is there any remote control that does work out of the box?
Also the system is sometimes a little slow in performance, is there a way it can be improved? I already bought a new and faster SD card. And a cooler for the RasPi 3 B+

[Konsta]

Hey Konsta,
awesome job you did there. Thank you. I just have to tiny questions.
Is there any remote control that does work out of the box?
Also the system is sometimes a little slow in performance, is there a way it can be improved? I already bought a new and faster SD card. And a cooler for the RasPi 3 B+

This build has been discontinued over a year now. Please update to using LineageOS 16.0 (https://www.raspberrypi.org/forums/view ... 3&t=243832) build which also has significantly better graphics performance.

It depends what you mean by remote? I have an USB air mouse with function keys on one side and full keyboard on the other side and it works fine as a remote.

[derletztename]

I am very sorry, I wrote into the wrong thread. I already use 16.
Still the performance is not very good, I am escpecially focused on the KiKa Player for my kids. Much better content than Netflix. But even in the menus like the home screen it does not react very fluently. I use a big ass copper block as temporary cooling solution as my raspi case is still on its way. Not very beautiful, but should be very effective. At least for some time. Do you have any requirements or recommendation for a cooler for your system?

Yeah Air Mouse would be absolutely sufficient. Only that the one I bought does not work out of the box. Do you have any recomendation for a working one?

[Konsta]

I am very sorry, I wrote into the wrong thread. I already use 16.
Still the performance is not very good, I am escpecially focused on the KiKa Player for my kids. Much better content than Netflix. But even in the menus like the home screen it does not react very fluently. I use a big ass copper block as temporary cooling solution as my raspi case is still on its way. Not very beautiful, but should be very effective. At least for some time. Do you have any requirements or recommendation for a cooler for your system?

Yeah Air Mouse would be absolutely sufficient. Only that the one I bought does not work out of the box. Do you have any recomendation for a working one?

Hardware specs of the Pi 3 B+ match low-end Android devices from three years ago to give some perspective. There's also very limited amount of RAM on the Pi as part of is allocated to the GPU. As this not an Android device to begin with there's no drivers to support hardware video decoding/encoding so this is really not meant as a media device. If you use active cooling, you can try overlocking just like on any other OS (https://www.raspberrypi.org/documentati ... locking.md).

Any USB air mouse that works with Linux in general should work here as well. Grab 'dmesg' while plugging in your device to see what's going on.

[Gabrielpveras98]

[translation made by moderator using google translate]
I need help, I can't even install the system, in mine instead of starting normally it goes straight into TWRP


Preciso de ajuda, não consigo nem istalar o sistema, no meu ao invés de inicializar normalmente ele entra direto na TWRP
[please don't use Portuguese on this non Portuguese section of the forum!]

[Konsta]

[translation made by moderator using google translate]
I need help, I can't even install the system, in mine instead of starting normally it goes straight into TWRP


Preciso de ajuda, não consigo nem istalar o sistema, no meu ao invés de inicializar normalmente ele entra direto na TWRP
[please don't use Portuguese on this non Portuguese section of the forum!]

This build is discontinued and seriously outdated. You should use the latest LineageOS 16.0 or 17.1 build instead.

Similar issue has been discussed e.g. here viewtopic.php?f=73&t=261228&p=1653284&h ... p#p1649865

[joser369]

[translation made by moderator using google translate]
I need help, I can't even install the system, in mine instead of starting normally it goes straight into TWRP


Preciso de ajuda, não consigo nem istalar o sistema, no meu ao invés de inicializar normalmente ele entra direto na TWRP
[please don't use Portuguese on this non Portuguese section of the forum!]

This build is discontinued and seriously outdated. You should use the latest LineageOS 16.0 or 17.1 build instead.

Similar issue has been discussed e.g. here viewtopic.php?f=73&t=261228&p=1653284&h ... p#p1649865

hello Konsta
This happens to me, I use zoom in 16, 17 both in rpi3 and rpi4, there the microphone does not work but the camera does, but in this version 15 the microphone works, but the camera no longer works.
thanks