[DEV][ROM][UNOFFICIAL] LineageOS 16.0 (Android 9) for Raspberry Pi 3 B and B+

Search This thread
By:
Advanced…
W

witzyz

Member
Jan 31, 2008
24
1
KonstaT said:
No, not the official one at least. But I guess the answer also depends on the exact touchscreen hardware you're talking about.

LineageOS 14.1 & 15.1 builds support the official 7" touchscreen and it should be fairly straightforward to get some Waveshare DPI touchscreens working as well (ADS7846). I don't know if people have had any luck with ones that use HDMI & USB combo.
Click to expand...
Click to collapse

witzyz said:
hi 2/7/2020 i install os = lineage-16.0-20191222-UNOFFICIAL-KonstaKANG-rpi3
how to install lcd 3.5inc for resberry pi3 model Bv1.2

thank ^^
Click to expand...
Click to collapse

KonstaT said:
It depends what display you have and what hardware it uses. How would you do it in some other OS e.g. Raspbian?
Click to expand...
Click to collapse

my hardware lcd 3.5inc xt2046 touch controller 480*320 pixel with android LineageOS 16.0 (Android 9) for Raspberry Pi 3

https://www.img.in.th/image/T5ecfA
 
KonstaT

KonstaT

Senior Member
Jan 20, 2016
668
422
KonstaKANG.com
witzyz said:
my hardware lcd 3.5inc xt2046 touch controller 480*320 pixel with android LineageOS 16.0 (Android 9) for Raspberry Pi 3

https://www.img.in.th/image/T5ecfA
Click to expand...
Click to collapse

Well, have you tried it with LineageOS? Can you get logs?

Kernel already has TOUCHSCREEN_ADS7846 driver that is used with those displays. There's still some other modifications needed for the touchscreen (https://konstakang.com/devices/rpi3/CM14.1/#comment-3865392433). As for the display itself, I honestly don't know how the graphics drivers used in LineageOS 16.0 currently handle displays like that (uses SPI?) I think someone had some luck with VGA666 that uses DPI, though. I should probably get myself one of those displays to test with.
 
Last edited:
KonstaT

KonstaT

Senior Member
Jan 20, 2016
668
422
KonstaKANG.com
New build. A lot of new stuff in this one. :)

https://konstakang.com/devices/rpi3/LineageOS16.0/

  • add camera HAL to support Pi camera modules and USB webcams (thanks to Android-x86)
  • update to MESA 19.3.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
  • enable hardware overlays (improves graphics performance)
  • add option to switch to SwiftShader software renderer e.g. to use official 7" touchscreen or to boot without any display connected (see FAQ)
  • fix portrait apps on forced landscape orientation (thanks to Ladehunter)
  • update GPS HAL
  • option to use DIY hardware power button to boot to TWRP recovery (see FAQ)
  • initial support for IR modules and remotes (tested with TSOP4838)
  • update to Linux 4.19.102 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
  • Android security patch level: 5 January 2020 (merged)
 
Last edited:
  • Like
Reactions: Allhunt
KonstaT

KonstaT

Senior Member
Jan 20, 2016
668
422
KonstaKANG.com
hfmls said:
Thank you for new build. Do you think we will ever get video acceleration or simply not possible?
Click to expand...
Click to collapse

I assume you mean hardware video decoding & encoding here (i.e. offloading e.g. H.264 dec/enc to hardware). I've done some research on this and Linux kernel has a thing called V4L2 MEM2MEM driver that can be used for this. With 4.19 kernel and going forward there is now bcm2835-codec driver that makes it possible to use the M2M kernel interface on the Pi for video dec/enc (https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=234778). GStreamer and FFMPEG can utilize the M2M driver on Linux distros. Problem is how to utilize it on Android and hook it up with Android's media stack. LineageOS used to have FFMPEG for extra codec support but it was dropped after Nougat (LineageOS 14.1). Android-x86 project still uses FFMPEG but it's an old version that doesn't yet support M2M codecs. So, one option is to bring up newer version of FFMPEG for Android. Or someone needs to come up with some other framework to utilize it. It's also very possible that this might happen eventually because this is a cross-platform thing that can be used on wide range of devices as it uses generic Linux interface. So yes, this might be possible sometime in the future when things mature. With the current state of things with the kernel and graphics drivers, Pi 3 will likely also run any new Android version in any foreseeable future...

Due to the open nature of things here there are actually very few things that are impossible. It's just a matter of if something is possible to achieve with any reasonable amount of effort.
 
Last edited:
  • Like
Reactions: hfmls
KonstaT

KonstaT

Senior Member
Jan 20, 2016
668
422
KonstaKANG.com
Priyansu67 said:
I followed the exact procedure of flash gapps and wiping data and I thought we can flash any gapps let that be pico or tv stock.
Click to expand...
Click to collapse
Nope, regular gapps in different sizes are for regular Android builds and Android TV gapps are for Android TV builds.

Priyansu67 said:
Having some size issue from all sides of the screen, the status bar and navigation bar appears to be outside the screen. Any solution?
Click to expand...
Click to collapse
Try adjusting your display's settings if you can.

Normally you could remove/comment out 'disable_overscan=1' in /boot/config.txt but this seems to cause some issue with hardware overlays enabled. You could also disable hw overlays from Settings -> System -> Developer options -> Disable HW overlay or more permanently uncomment/add 'hwc.drm.use_overlay_planes=0' in /system/build.prop.
 
xChr11s

xChr11s

Member
May 23, 2013
26
2
Cologne
Thanks for your effort, it works like a charm.
But I have one question: Is it possible the completely remove the root?
The App I was testing detected the root, even when it was deactivated in the developer settings.

Kind regards
 
KonstaT

KonstaT

Senior Member
Jan 20, 2016
668
422
KonstaKANG.com
xChr11s said:
Thanks for your effort, it works like a charm.
But I have one question: Is it possible the completely remove the root?
The App I was testing detected the root, even when it was deactivated in the developer settings.

Kind regards
Click to expand...
Click to collapse

You can flash addonsu-remove-16.0-arm-signed.zip from https://download.lineageos.org/extras in TWRP to remove su binary.

I doubt that's going to help, though. Most secure apps these days also test various other things besides root access. Many apps use Google's SafetyNet API to determine the device status.
 
  • Like
Reactions: xChr11s
J

justjoin

New member
Apr 25, 2020
2
0
Hey KonstaT thanks for build.. but i have questions, im using DS3231 on i2c port on Raspi 3.. but its doesn't detected automatically, even it's error when i try hwclock -s
 
J

justjoin

New member
Apr 25, 2020
2
0
KonstaT said:
You need to uncomment the line under RTC section in /boot/config.txt first.

After that e.g.
Code: 
su
hwclock -s -f /dev/rtc0
Click to expand...
Click to collapse


Its working now.. but i can't change the hwclock file.. after i hwclock -s -f /dev/rtc0 then hwclock it won't change.. it still on /dev/misc/rtc and everytime i create symlink to it, its gone after reboot..
 
You must log in or register to reply here.

Similar threads

KonstaT
[DEV][ROM][UNOFFICIAL] LineageOS 17.1 (Android 10) for Raspberry Pi 4 B
Replies
404
Views
87K
L
locness3
KonstaT
[DEV][ROM][UNOFFICIAL] LineageOS 18.1 (Android 11) for Raspberry Pi 4 B
Replies
426
Views
69K
KonstaT
KonstaT
KonstaT
[DEV][ROM][UNOFFICIAL] LineageOS 19 (Android 12L) for Raspberry Pi 4 B
Replies
350
Views
51K
pi_saab
pi_saab
M
OmniROM Android R (11) for Pi 4
Replies
413
Views
126K
pi_saab
pi_saab
KonstaT
[DEV][ROM][UNOFFICIAL] LineageOS 15.1 (Android 8.1.0) for Raspberry Pi 3 B and B+
Replies
56
Views
35K
S
sebagsm

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 9
    KonstaT
    KonstaT
    Here’s my build of LineageOS 16.0 for Raspberry Pi 3 Model B and Model B+. It is unofficial and unsupported by the LineageOS team. It’s for advanced users only.

    Important! This image includes parts that are licensed under non-commercial license (Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International). You may use this build freely in personal/educational/etc use. Commercial use is not allowed with this build!

    Screenshot_20190627-114323_Settings.png


    https://konstakang.com/devices/rpi3/LineageOS16.0/

    lineage-16.0-20200713-UNOFFICIAL-KonstaKANG-rpi3.zip
    https://www.androidfilehost.com/?fid=8889791610682891697
    md5:3689e767c41858bb53db20190b6542a5

    Working:
    • Audio (HDMI, 3.5mm jack, USB microphones, bluetooth speakers/headsets, etc)
    • Audio DAC (using PCM512x DACs e.g. Hifiberry DAC+)
    • Bluetooth
    • Camera (using official Pi camera modules & UVC USB webcams)
    • GPIO
    • GPS (using external USB modules e.g. U-Blox 7)
    • Ethernet
    • Hardware accelerated graphics (VC4)
    • HDMI display
    • I2C
    • IR remotes (using external GPIO IR modules e.g. TSOP4838)
    • RTC (using external GPIO I2C modules e.g. DS3231)
    • Serial console (using external GPIO serial console adapters e.g. PL2303)
    • SPI
    • Touchscreen/multi-touch (using official 7” display with SwiftShafer software renderer)
    • USB (mouse, keyboard, storage, etc)
    • Wifi
    • Wifi tethering

    Not working:
    • Hardware video decoding & encoding

    Issues:
    • SELinux is in permissive mode
    • and more…

    Sources:

    Thanks:
    • peyo-hd and everyone who has contributed to android-rpi
    • brobwind for graphics and bluetooth fixes
    • Eric Anholt for VC4 graphics driver
    • Google for Android Things platform
    • Android-x86 project
    • LineageOS team & everyone who has contributed to LineageOS 16.0
    View
    4
    KonstaT
    KonstaT
    How to install:
    1. Follow the official Raspberry Pi instructions for writing the image to the SD card (Linux, Mac, Windows).

    FAQ:

    Q: I can’t find developer options, why?
    A: Settings -> About tablet -> Click ‘Build number’ several times

    Q: I have no root, why? What is that hashtag on my status bar?
    A: You need enable root access under Settings -> System -> Developer options -> Root access. Root management is now integrated as part of LineageOS’ Privacy Guard and you can manage per app permissions under Settings -> System -> Developer options -> Manage root access. You’ll have a persistent notification in the status bar when you’re running an app that uses root permissions.

    Q: Settings -> Storage shows total system size of 4 GB. There's unallocated space on my sdcard. What should I do?
    A: This is a 4 GB image, remaining space on your sdcard will remain unallocated. You can use e.g. GParted and extend /data partition (/dev/block/mmcblk0p4) to cover the unallocated space. Resizing the partition manually will break support for encrypting /data. Format /data in TWRP recovery (Wipe->Format data) after resizing to leave required space for crypto footer.

    Or you can flash my resize zip in TWRP.

    Q: My display is not working. I can only see the rainbow screen but no Android boot animation. What should I do?
    A: This build only supports HDMI displays that report supported resolutions using EDID. See this page under 'Which values are valid for my monitor?' to see how to check which resolutions your display supports using Raspbian. 1280x720 resolution is used by default with this build. If your display doesn't support 1280x720 resolution, you can try changing value in /boot/resolution.txt to something it does.

    Q: I have official 7” LCD display and touchscreen. What should I do?
    A: Official 7” touchscreen is only supported using SwiftShader software renderer. See below how to switch between different graphics drivers. You will also need to change display size under Settings -> Display -> Display size (or change ro.sf.lcd_density to 120 in /system/build.prop) to adapt to the smaller resolution.

    Q: I need to use SwiftShader software renderer to use the official 7” display or I want to boot without any display connected. What should I do?
    A: Warning, SwiftShader is a software renderer and using it affects graphics performance. You can switch between MESA and SwiftShader graphics drivers by executing following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal):

    Code: 
    su
rpi3-graphics.sh swiftshader
    Code: 
    su
rpi3-graphics.sh mesa

    Q: Raspberry Pi doesn’t have power button, how do I power off/reboot my device?
    A: Following keyboard keys work as Android buttons: F1 = Home, F2 = Back, F3 = Multi-tasking, F4 = Menu, F5 = Power, F11 = Volume down, and F12 = Volume up. You can also use one of many third party reboot applications.

    Q: How to create a DIY hardware power button?
    A: You can send power button events by connecting GPIO21 to ground.

    powerbutton.png


    Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal) to enable the feature and reboot your device:

    Code: 
    su
rpi3-powerbutton.sh

    You can also use the DIY power button to boot the device to TWRP recovery. Press and hold the button while powering on the device until you see the TWRP screen. If you use this method to boot to recovery, you can ignore what is said about booting into/out of TWRP later in the FAQ.

    Q: How to enable audio through 3.5mm jack?
    Execute following commands in 'adb shell'/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal) to enable the feature and reboot your device:

    Code: 
    su
rpi3-audio-jack.sh

    Q: How to boot from USB device?
    A: Warning, this is an experimental feature and there’s still some issues with it. Android shows USB storage notification for each partition and you should ignore these. TWRP shows errors in few places but everything seems to be working regardless of this.

    1. Follow the official instructions on how to enable USB boot on Pi 3 B (this step is not needed on Pi 3 B+)
    2. Write image to your USB device as above
    3. Mount the USB device on your computer and rename following files on the boot partition:
      Code: 
      mv ramdisk.img ramdisk-sdcard.img
mv ramdisk-usb.img ramdisk.img
mv ramdisk-recovery.img ramdisk-recovery-sdcard.img
mv ramdisk-recovery-usb.img ramdisk-recovery.img
    4. Plug in the USB device to your Raspberry Pi, remove any sdcard, and boot

    Q: How to boot to TWRP recovery?
    A: There’s currently no proper way to boot between Android and TWRP, but this can achieved by renaming the ramdisk you want to boot. Execute following commands in ‘adb shell’/serial console/terminal (you can enable built-in terminal app from Settings -> System -> Developer options -> Local terminal) and reboot your device:

    Code: 
    su
rpi3-recovery.sh

    If mouse cursor doesn’t appear, try replugging your mouse.

    Q: How to boot out of TWRP recovery?
    A: You can execute the same script in TWRP terminal (Advanced->Terminal) if you have boot and system partitions mounted (Mount->Boot & Mount->System):

    Code: 
    rpi3-recovery.sh boot

    Or you can flash my recovery2boot zip in TWRP.

    Q: How to update from previous LineageOS 16.0 build without losing data?
    A:

    1. Boot to TWRP recovery with the build you want to keep the data (see FAQ)
    2. Plug in an external USB storage device and select 'Backup'
    3. Use 'Select Storage' to choose the USB device and 'Swipe to backup' (it's only necessary to backup the data partition so you can uncheck other partitions to speed up the process)
    4. Write new LineageOS 16.0 image to the sdcard following installation instructions
    5. Boot to TWRP recovery with the new build (see FAQ)
    6. Select 'Restore' and find the backup you created from the USB device ('Select Storage')
    7. Make sure you only have data selected as partitions to restore (uncheck other partitions if available) and select 'Swipe to Restore'
    8. (Flash Google apps package/other add-ons you had previously installed)
    9. Boot out of recovery (see FAQ)

    Q: How to install Google apps?
    A: Warning, installing gapps slows things down especially on low-end devices with limited amount of RAM such as this one.

    1. Download open_gapps-arm-9.0-pico-xxxxxxxx.zip and save it to your device’s internal storage or use an external USB drive
    2. Boot to TWRP recovery (see FAQ)
    3. Install open_gapps-arm-9.0-pico-xxxxxxxx.zip from your selected storage
    4. Wipe->Factory reset!
    5. Boot out of recovery (see FAQ)
    View
    3
    KonstaT
    KonstaT
    Merged commits not mentioned in the changelog.

    13.7. changelog:

    • add ir-keytable tool to configure IR remotes
    • enable USB gadget support & fix adb toggle in developer options
    • add support for storage devices with exFAT filesystem
    • hide su binary when root access is not enabled in developer options
    • add support for PCM512x audio DACs (tested with Hifiberry DAC+)
    • improve support for Waveshare HDMI touchscreens
    • fix recording videos with camcorder
    • add TWRP flashable zip to resize data partition (see FAQ)
    • update TWRP to 3.3.1-1
    • update to MESA 20.1.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
    • update to Linux 4.19.132 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    • Android security patch level: 5 July 2020 (merged)

    7.2. 2020 changelog:
    • add camera HAL to support Pi camera modules and USB webcams (thanks to Android-x86)
    • update to MESA 19.3.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
    • enable hardware overlays (improves graphics performance)
    • add option to switch to SwiftShader software renderer e.g. to use official 7” touchscreen or to boot without any display connected (see FAQ)
    • fix portrait apps on forced landscape orientation (thanks to Ladehunter)
    • update GPS HAL
    • option to use DIY hardware power button to boot to TWRP recovery (see FAQ)
    • initial support for IR modules and remotes (tested with TSOP4838)
    • update to Linux 4.19.102 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    • Android security patch level: 5 January 2020 (merged)

    22.12. changelog:
    • update to MESA 19.3.1 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
    • set default resolution using a configuration file (see FAQ)
    • add vendor init library to set serial number, revision, and resolution properties
    • add health HAL to fake battery/charging
    • add script to enable audio through 3.5mm jack (see FAQ)
    • add initial support for RTC hardware (tested with DS3231)
    • update to Linux 4.14.160 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    • Android security patch level: 5 December 2019 (merged)

    27.6. changelog:
    • initial LineageOS 16.0 build
    • hardware accelerated graphics (thanks to brobwind for putting the final pieces together)
      • VC4 using Mesa 19.1 with drm_hwcomposer & minigbm gralloc
    • fix bluetooth on Pi 3 B+ (thanks to brobwind)
    • add initial support for booting from USB devices (see FAQ)
    • add support for DIY hardware power button (see FAQ)
    • update TWRP to 3.3.1-0
    • update to Linux 4.14.129 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    • Android security patch level: 5 June 2019 (merged)

    Previous builds:
    View
    2
    KonstaT
    KonstaT
    turtleletortue said:
    Nice! I like seeing stuff like this for the pi. I remember having so much fun tinkering with building the oreo lineage15.1 rpi3 stuff a bit ago. Also, I heard something about someone trying to sell your builds of lineage for pie, so will the lineage-16.0 branch for some of the files on the github page for this not be released to the public? Either way, I appreciate your work a lot and hope you can continue as these are amazing!
    Click to expand...
    Click to collapse

    Wasn't trying - was and still is selling builds for $9! Nothing but builds from lineage-rpi sources with some apps bundled in. It was even promoted on Pi Foundation's own MagPi Magazine as his work and the article was brought to my attention. I spent _a lot_ of time on this last fall but couldn't really get anywhere. You can read about it e.g. here and here.

    What makes this very problematic for Exton is that he is not complying with GPLv2 that Linux kernel is licensed under. GPLv2 obligates anyone distributing a binary to release a complete corresponding source code. Even if the only modification you make is stick your own name on other people's work...

    That is exactly why I haven't published lineage-16.0 branches apart from the Linux kernel (https://github.com/lineage-rpi/android_kernel_brcm_rpi3/tree/lineage-16.0) as that is naturally also my legal obligation. You can't do Android with just the Linux kernel source, though. I was thinking about putting up a private GitLab project where I could share the source code with reputable developers who actually have some ideas how they want to improve what is already available. I know some companies are you using my previous LineageOS builds which is why I've licensed some stuff under non-commercial license in this one. They've been asking for private tech support but I still can't get as much as a donation even when promised. :(
    View
    2
    KonstaT
    KonstaT
    New build.

    lineage-16.0-20191222-UNOFFICIAL-KonstaKANG-rpi3.zip
    https://www.androidfilehost.com/?fid=4349826312261681719
    md5:956962b364583917b47046ef8556db85

    -update to MESA 19.3 and latest upstream versions of minigbm gralloc, drm_hwcomposer, and libdrm
    -set default resolution using a configuration file (see FAQ)
    -add vendor init library to set serial number, revision, and resolution properties
    -add health HAL to fake battery/charging
    -add script to enable audio through 3.5mm jack (see FAQ)
    -add initial support for RTC hardware (tested with DS3231)
    -update to Linux 4.14.160 kernel and patch known vulnerabilities (CVE-xxxx-xxxx, and more)
    -Android security patch level: 5 December 2019 (merged)
    View

New posts