[DEV][ROM][UNOFFICIAL] LineageOS 17.1 (Android 10) for Raspberry Pi 4 B

[KonstaT]

Hi, thanks to everyone involved in this build for their amazing work.
Now, I'd like to install NanoDroid and specifically its patcher script to add signature spoofing support and install microG. I have attached the particular zip file. When I try to install it in TWRP, it just fails with `failed to mount /system (unsupported A/B device?)`.
I tried disabling the option to unmount system before installing zips, mounting it then installing the zip but the script seems to try to mount it anyways. I assume this a problem with the partitioning scheme? What could I do to get the install to work? Thanks in advance to anyone who might help me with this.

This build is discontinued and you should use the latest LineageOS 18 images instead (https://forum.xda-developers.com/t/...18-1-android-11-for-raspberry-pi-4-b.4212945/).

Without further looking into I can't say why it would fail. There is nothing non-standard about system partition on this device (only boot partition is different from regular Android devices) so it shouldn't fail if the installer is done properly.

Would this be something that can be done with Magisk? I just recently added a Magisk patcher for my builds so you can use that now.

 

[locness3]

> This build is discontinued and you should use the latest LineageOS 18 images instead

They're not stable enough for me.

> Would this be something that can be done with Magisk?

I think it can.

I'll stay with degoogled los17. Thanks for your response.

 

[KonstaT]

> This build is discontinued and you should use the latest LineageOS 18 images instead

They're not stable enough for me.

> Would this be something that can be done with Magisk?

I think it can.

I'll stay with degoogled los17. Thanks for your response.

Care to specify what exactly makes them "not stable enough"? Difference in kernel is just one line in configuration. All the graphics drivers are much newer/better in later versions. I can't see any reason not to update which is why there's also no point in keeping this version maintained. Basically you're just missing out on all the latest features and updates by using an almost a year old build but your choice of course.

There never was any Google services included to begin with so you can't remove anything (and Android being Google OS you can't escape that in any case).

 

[locness3]

There never was any Google services.

That's what I'm saying.

> Care to specify what exactly makes them "not stable enough"?

Some small problems around, like the scrolling text in the quick settings slowing down everything (maybe this only happens with the french locale), or some crashes with video playback in certain cases - I wasn't aware that the los17 build wasn't updated anymore, so I'll consider making detailed bug reports for the newer builds.

 

[locness3]

It seems like most of my issues with the los18 builds are gone since the last time I tried (aside from quick settings), thank you. I appreciate it being 64-bit now too

 

[lesleylemmens]

You can check /boot/config.txt and see how this is implemented and use which ever GPIO pin you want. DIY power button works just like a power button on any Android device - short press to switch display on/off, long press to invoke power menu.

There's no support for booting the Pi from power off no matter which GPIO pin you'd use.

Hi, i changed config.txt to 03 but somehow it is not working, any suggestions?

 

[lesleylemmens]

Yes, bar. Sorry.

I just connected GPIO3 to GND with a button in between. When the Pi is turned off, you just need to push the button and the Pi will boot.
Nothing else to do for the boot button.

I also changed you shutdown script to use GPIO3. So if you connect GPIO3 for example to the ignition of a car using a relay (there are of course some more steps in between), it will boot when the car is turned on and shutdown when the car is turned off.

Hi, i did change config.txt to 03 but it is not working. Any suggestions?

 

[KonstaT]

Hi, i did change config.txt to 03 but it is not working. Any suggestions?

This build is seriously outdated and has been discontinued for over two years. Please use the latest Android 12/13 builds instead.

Also probably already elsewhere.

LineageOS 18.1 (Android 11)

for Raspberry Pi 4

disq.us

 

[eagledipesh]

Hello Dev, would it possible to create a generic script (Should independently work on various platforms AMLOGIC,, ARM etc...) to covert Normal ROM to ATV ROM.