yashsingh1/xdaforums huggingface dataset:
[Raspberry Pi Original Development] jjakajonas:
I totally agree that its in my end theres something wrong.

Also the the reason I asked after help on how to work whit it.

I have tryed do it separately and mixed because what ever I did it ended up up whit an error.

So I think that the next step is to start over whit a fresh install on another machine whit more RAM and try it all over.
[Raspberry Pi Original Development] KonstaT:
warning != error

Build system again tells you exactly what is wrong (ninja: error: unknown target 'ramdisk-recovery'). You're missing the patch the instructions tell you to apply. Don't skip steps!

cd build/make
git am 0001-add-target-to-build-ramdisk-recovery.patch
cd ../..

Copy the patch to build/make first of course.
[Raspberry Pi Original Development] jjakajonas:
Thats (as i see it) the only step theres not making sens.

I can't find the file.

Do I have to download that manually or is it hiding somewhere in the repo download?
[Raspberry Pi Original Development] KonstaT:
Manually. Here's a direct link (https://raw.githubusercontent.com/l...01-add-target-to-build-ramdisk-recovery.patch).

Also look into using repo branches ('repo start branchname path/to/project') if you want your patches automatically rebased after a 'repo sync'. Otherwise you need to apply them again after each 'repo sync'.
[Raspberry Pi Original Development] jjakajonas:
Thanks.

I will look at it later.

I made an mistake when I installed the machine so I have to start over... Again.
[Raspberry Pi Original Development] jjakajonas:
Okay...

I changed the hard drive to get enough space (thought I had I bigger one in the machine)

Any how....

I followed every step on the preparing side at AOSP + a few more to get openjava 8, make and a fed other things (not documented) to work..

I followed all the steps at github (also got the patch applied).

But still this spits errors at me like crazy...

I don't say something is wrong whit your repo or guide.

I just say this is NOT newbie friendly at all....
[Raspberry Pi Original Development] KonstaT:
What errors? I don't know what you've done so I can't know what have went wrong.

This shouldn't be any more difficult than building any Android from source.
[Raspberry Pi Original Development] jjakajonas:
This is my steps after i installed Ubuntu server 18.04.1.

sudo apt-get update
sudo apt-get install openjdk-8-jdk (gave an error "E: Unable to locate package openjdk-8-jdk")
added "deb http://security.ubuntu.com/ubuntu bionic-security main universe" to /etc/apt/sources.list
sudo apt-get update
sudo apt-get install openjdk-8-jdk
export OUT_DIR_COMMON_BASE=~/WORKING_DIRECTORY/OUT
mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
mkdir WORKING_DIRECTORY
cd WORKING_DIRECTORY
mkdir twrp-8.1
mkdir lineage-15.1
cd twrp-8.1
sudo apt-get install kpartx python-mako
repo init -u git://github.com/lineage-rpi/android_local_manifest.git -b twrp-8.1
curl --create-dirs -L -o .repo/local_manifests/manifest_brcm_rpi3.xml -O -L https://raw.githubusercontent.com/lineage-rpi/android_local_manifest/twrp-8.1/manifest_brcm_rpi3.xml
repo sync
copied patch to folder
cd build/make
git am 0001-add-target-to-build-ramdisk-recovery.patch
cd ../..
export ALLOW_MISSING_DEPENDENCIES=true
. build/envsetup.sh
lunch omni_rpi3-userdebug
mka ramdisk-recovery (error: missing make)
sudo apt install make
export ALLOW_MISSING_DEPENDENCIES=true
. build/envsetup.sh
lunch omni_rpi3-userdebug
mka ramdisk-recovery (error: missing m4)
sudo apt-get install m4
sudo apt-get install gcc-arm-linux-gnueabihf
export ALLOW_MISSING_DEPENDENCIES=true
. build/envsetup.sh
lunch omni_rpi3-userdebug
mka ramdisk-recovery

Latest error:

/bin/sh: 1: gcc: not found
scripts/Makefile.host:104: recipe for target 'scripts/basic/fixdep' failed
make[3]: *** [scripts/basic/fixdep] Error 127
/home/jjakajonas/WORKING_DIRECTORY/twrp-8.1/external/busybox/Makefile:364: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
/home/jjakajonas/WORKING_DIRECTORY/twrp-8.1/external/busybox/Makefile:526: recipe for target 'include/autoconf.h' failed
make[1]: *** [include/autoconf.h] Error 2
Makefile:119: recipe for target 'prepare' failed
make: *** [prepare] Error 2
make: Leaving directory '/home/jjakajonas/WORKING_DIRECTORY/twrp-8.1/external/busybox'
[ 1% 190/10170] target thumb C++: init <= system/core/init/init.cpp
ninja: build stopped: subcommand failed.
11:20:13 ninja failed with: exit status 1

#### failed to build some targets (24 seconds) ####

and i have been searching on google and havent yet got it fix..
[Raspberry Pi Original Development] KonstaT:
You haven't installed the required packages on your machine like it says in the 'Establishing a Build Environment' guide (https://source.android.com/setup/build/initializing).

sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev libgl1-mesa-dev libxml2-utils xsltproc unzip

Required packages also depend on the Ubuntu version you're using so read that guide with care. build-essential package includes make, gcc, etc that build system complains you're missing.
[Raspberry Pi Original Development] jjakajonas:
Yeah...

About that part.

I forgot it on the list...

Everyone of those parts throwed me an error about I couldn't be found so I basically have to find the the deb line for those...

Google is your friend.. I know... But it takes time to find undocumented steps to do the documented steps...

For now I just mods on a android destro to fits the needs there is now so that I can take the time and figure this one out on my own... Again....
[Raspberry Pi Original Development] KonstaT:
Those packages should be available in Ubuntu main repositories so I actually find that quite hard to believe. You can check Ubuntu's 'Software & Updates' to see which repos are enabled (or command line https://help.ubuntu.com/community/Repositories/CommandLine). If you choose a Linux distribution other than what's recommended and documented (Ubuntu server?, Arch Linux, etc), you of course need to figure some stuff out yourself. You still should be able to build this with any 64-bit Linux distro.
[Raspberry Pi Original Development] jjakajonas:
You know what?

I just think I stop here....

You was so busy with getting me to use your build.

Now I'm here and then I'm more or less on my own an you are just so pollite to tell me that that it in my end the errors are, that I need to filollow a guide and so..

But help me to get started? Nope?

So I just find some other thing to do instead....
[Raspberry Pi Original Development] KonstaT:
LOL, what? I thought I was helping you get started.

No one is forcing you to do anything. Also I don't owe you assistance of any kind and I get to choose how I spend my spare time. Good luck with everything. :)
[Raspberry Pi Original Development] Nypan sr:
Like i told you earlier, if you plan on using your Pi as a mediaplayer, install LibreELEC.

Its now updated even further:

v8.90.005 ALPHA:

– updated to Kodi 18 Beta 3

– Kernel updated to 4.18.11 for Generic, RPi and Slice

and good support at https://forum.libreelec.tv/
[Raspberry Pi Original Development] jjakajonas:
Yeah i have to follow some guides that I have done over and over after I got the patch problem fixed.

But I still got problems and still I get told to follow the same guide again (as I have done over and over a few times now whit same results)

Right now Google have been an even better help than this tread.

Yeah I know you don't owe me anything at all..

But I was working on one project that worked for me, you talked about it was better to work on this project instead.

So I changed over to this.

I now got problems and therefore try to ask for help on how to fix som errors that I can't find the solution to my self.

And instead of making a tread about a so specific problem do I ask here.

But excuse me...

But the help so far have been "you miss some steps" or "you need this to work" instead of "you need this to work and this may help you"

Or ask into what I have done so far or even given me some help to how to find the error message explained in the output text...

Most of my own work here is guess work on how to work this out.

For what I know could I just make more damage than good to get this to work.

So yeah...

I choose to work with google now...

And hope for the best that way....

---------- Post added at 08:30 PM ---------- Previous post was at 08:23 PM ----------

That doesn't help my project I any way...

The project was so specific that I got my pi only to work on that one project...

A project on getting Android TV to my old flat screen TV that is to old to use as other than a monitor....

And it was a project that I work on whit my child. And we like to combine different things in this box and for our purpose is Android the best start point...

Basicly the best solution was to get a new flat screen...
[Raspberry Pi Original Development] Nypan sr:
The Pi have been around since 2012 and there is still no usable androidimage around...
[Raspberry Pi Original Development] jjakajonas:
And if every projects gets abandoned or new commers can help the development there will never be.

I changed to this project to help an image to be developed..

But hey...

The other project that I was on my way in to was more easy to work on a mod for than this one.
[Raspberry Pi Original Development] KonstaT:
That's a very good idea if you want to use your Raspberry Pi as media device.

I never intended this as TV/media device which is why I've chosen the tablet layout. I consider this mainly as an open source project and you're welcome to improve it if you can. It's just fun to have Android on a device that isn't supposed to have Android. ;)
[Raspberry Pi Original Development] jjakajonas:
I now got server to work more or less..

And have now testet your LA 14.1 & 15.1 and ether of them accepts the stock tv gapps.

So I ether have to mod your build or just combine yours with the other to get the system I want.
[Raspberry Pi Original Development] jjakajonas:
[MENTION=7223862]KonstaT[/MENTION]

I have made a choice.

I have made a fork of your build that i will mod a bit on so it will be a TV edition and make my touch on the build.

But credit goes to you at the moment do to that the build right now is a copy of your work.

This is my repo.

I hope that fork is okay. If theres some detail theres not okay then pleace tell me so i can change it.
[Raspberry Pi Original Development] KonstaT:
That's fine. Linux kernel is licensed under GPLv2 (https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) and you need to be aware of this when you work with open source software. XDA has their own additional rules regarding that stickied on each forum (https://xdaforums.com/showthread.php?t=2645321).
[Raspberry Pi Original Development] jjakajonas:
It was more ment as respect to your work.
[Raspberry Pi Original Development] Paul_it:
Hi and thanks for the great work with the builds, but I’m having a problem with both 15.1 and 14.1 builds and I hope you can help me. I wrote an app that needs root access and privacy guards pops up correctly and asks me to grant it, I tick remember my choice and allow, but whenever the system is rebooted the choice is somehow forgot and privacy guards pops up again to ask me to grant it again and that’s a big problem for me because I want to run it without screen, headless and I can't do it manually at every reboot. I already tried to change all privacy guard settings without solutions, but I'm starting to think that it's a problem with the builds.
[Raspberry Pi Original Development] KonstaT:
Yeah, I can reproduce this on LineageOS 15.1 at least. I can't tell any obvious reason why this is happening, though. Thanks for reporting this.

I've decided to discontinue my Android development on Raspberry Pi because someone took my free and open source work and sold it for his own personal profit (https://www.raspberrypi.org/forums/...sid=e6cd167e8af60a6520b2b77932ef6ec6#p1381343). There won't be any further updates to fix issues like this, but I hope you can find a solution.
[Raspberry Pi Original Development] Paul_it:
Yes I can understand, that's really bad, I didn't know that RaspAnd was just your build with some apps and I purchased it, but I will ask a refund for sure now. I think your open source project is way faster than RaspAnd and it's a pity you decided to discontinue it, also because people like me want to donate money to the person who made the work and improved the open source community and not to who just rebuilt the code.

I'm not really an expert of custom ROM development, but if you can point me in the right direction about my issue, like what you would do if you were trying to solve it or where you would start to search it in the code, I will be glad to try to solve the issue by myself and upload the code to your repository.
[Raspberry Pi Original Development] KonstaT:
How could you know because he's tried his best to withhold that information. Even I didn't know until certain article was brought to my attention. Link to lineage-rpi was added after I contacted him couple of months ago. Now I'm trying to raise community awareness about this because there seems to be no way to reason with him. Nothing new here either as android-rpi guys raised issues before (https://www.reddit.com/r/Android/comments/4q40gj/androidrpi_extons_9_build/) and seems he's got experience with selling other people's work for personal profit with his other Linux releases even before that (https://www.raspberrypi.org/forums/viewtopic.php?p=754229#p753831).

Arne Exton has failed to provide Linux kernel source for his RaspAnd releases. Linux kernel is licensed under GPLv2 (https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) which obligates anyone distributing a binary to provide corresponding source code. Any RaspAnd release since December 15th 2017 is built based on my sources (https://github.com/lineage-rpi) and Linux kernel includes my work that is licensed under GPLv2. I feel that I've done some significant work merging together Raspberry and AOSP reference kernels and configuring it for this device and Android. This kernel wouldn't boot on any other device nor boot any other OS on the Pi.

I've also requested Linux kernel source code for another one of his Linux releases for Raspberry Pi and he only gave me a link to kernel.org. Nothing that you find on kernel.org will even boot on Raspberry Pi as the code for Pi hardware support is not included in mainline Linux. You could expect a bit more from someone who is a lawyer and made various Linux releases over a decade. GPLv2 is most definitely something that anyone selling open source software commercially should be aware of.

Money was never much of motivation for me (I'm just a hobbyist hacker and I've been around long enough to know there really isn't any here) and there hasn't been much donations either (thanks to both of you who have donated for Raspberry Pi Android development past 18+ months :)). It still doesn't feel right someone else profiting off of it either (and it's not even legal if you don't comply with GPLv2). There's no point in me open sourcing my efforts when someone is just going to take it and sell it. If I can't do it open source, there's really no point in doing it at all. :(

You could check logcat for any clues. I can't think of any obvious reason why this is broken on this device. Flashing LineageOS's su addon in TWRP shouldn't make any difference (as it's already included in the build) but there's third party root management options as well (that I don't usually recommend).
[Raspberry Pi Original Development] JavaLord:
Hello. Yesterday i've got my raspberry pi 3b+ , so i'm new to raspberry pi and i've got a problem with android images burning to sd card. Yesterday i wrote lineage os 15 to my sd card with etcher and i'ts booted fine, but then i tried to wrote lineage os 14.1 to this card and it doesn't boot, pwr led flashes 4 times slowly and 4 times quickly, the same with other android images, android 6, android 7 from geektillithertz.com, on all images pwr led blinking or just glowing red, only raspbian image runs ok. I tried to burn image with etcher, win32 utility and dd command from linux and always the same. Maybe i doing something wrong, could you help me.
[Raspberry Pi Original Development] KonstaT:
None of those builds are even supposed to work on the B+. Like it says in the thread title and in the first sentence in the OP, this build is for Raspberry Pi 3 Model B.

As for why, please read this (https://xdaforums.com/showpost.php?p=77593507&postcount=16).
[Raspberry Pi Original Development] JavaLord:
Thank you so much, I thought I was doing something wrong. I still do not understand, there are working versions of Android 7 for raspberry pi 3b+ ?
[Raspberry Pi Original Development] KonstaT:
None that is free and open source. This build doesn't support B+ for the reason stated before. I don't speak for anyone else.
[Raspberry Pi Original Development] bobscreations:
Hi, i build the kernel of link below to add eGalaxTouch USB driver and broken my wifi, even making no changes on kernel configs, just compiling, i try everything and no sucess to activate wifi for my car pi, please, give me a light.

My steps:

ARCH=arm scripts/kconfig/merge_config.sh arch/arm/configs/bcm2709_defconfig android/configs/android-base.cfg android/configs/android-recommended.cfg

(For Android-rPi)

KERNEL=kernel7

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j5 zImage

the kernel boot up normally and USB touchscreen works great, but no wifi.

https://github.com/lineage-rpi/android_kernel_brcm_rpi3/tree/cm-14.1
[Raspberry Pi Original Development] KonstaT:
It may boot but wifi is not the only thing that is broken...

There's build instructions available here (https://github.com/lineage-rpi/android_local_manifest/tree/cm-14.1) and it's the only 'correct' and supported way to build anything currently. It may of course feel unnecessary to sync the whole Android source if you only want to build a kernel. At least you can build only the kernel without building the whole Android (just use 'mka kernel' in step 5).

Standalone kernel build should also be possible but you need to adapt to bunch of things. First of all lineageos_rpi3_defconfig (https://github.com/lineage-rpi/andr...4.1/arch/arm/configs/lineageos_rpi3_defconfig) is the configuration that you need to use. Wifi firmware is included in the kernel so you need to place the firmware somewhere and adapt the path (https://github.com/lineage-rpi/andr...ch/arm/configs/lineageos_rpi3_defconfig#L1055). arm-linux-gnueabihf toolchain probably also works but AOSP toolchain is used when built with Android.
[Raspberry Pi Original Development] Paul_it:
I've managed to find a workaround for my issue after trying unsuccessfully to fix the bug in the code for a lot time, I post it here in case someone has my problem in the future.

I've also tried magisk and supersu as suggested but they don't work neither flashing or installing them manually.

My workaround consists of installing my app as a signature system app under the /system/priv-app folder and granting it permissions from the manifest instead of calling the SU binary directly, for example instead of rebooting executing "su -c reboot", I've added android.permission.REBOOT to the manifest and then execute just "reboot".

I've retrieved the keys for the signature of the apk from the Lineageos repo.
[Raspberry Pi Original Development] bobscreations:
This works man, thanks for you big help, my car pi is working now, very happy :D:D
[Raspberry Pi Original Development] bobscreations:
So, another question, any way to set wallpapers? here have a black background on launcher and i cannot set any image.
[Raspberry Pi Original Development] KonstaT:
OK, so it seems everything works exactly like it should if you power down/reboot your device through the power menu (F5 on keyboard is the power key). Using 'reboot -p'/'reboot' in terminal is not quite the same (I think a lot of third party reboot applications also work by using these commands).

So, you don't actually need to modify anything. After you've granted the root access for the first time you need to reboot your device through the power menu so the setting is stored. After that you can reboot using any method you like and it still works. Good to know. :)
[Raspberry Pi Original Development] KonstaT:
Well done. :)

That's one of known issues with the graphics drivers (VC4 doesn't support the color mode Android uses for wallpaper?). You can use LineageOS 15.1 build that uses different graphics drivers if having a wallpaper is the most important thing. ;)
[Raspberry Pi Original Development] bobscreations:
I use an apk "PhotoPhase" works great.

I have some paid playstore apps like poweramp, tasker etc, any way to install that without installing gapps?

poweramp unlocker verify true license using a google email account, and i cannot add an account without gapps and i do not want to install this.

Sorry for so much quesions, i'm very excited with my car pi project :D
[Raspberry Pi Original Development] KonstaT:
With root access you can of course backup apk file of any installed application. You can install that apk on a different ROM installation (without gapps) but if the app uses Google Play services or has other protective measures, there's probably not any easy way around that.
[Raspberry Pi Original Development] rafaelvinicio:
Any way to connect the raspberry via ethernet port with this rom?
[Raspberry Pi Original Development] KonstaT:
Sure, simply by plugging in the ethernet cable. Android doesn't have any settings options for ethernet but statusbar icon appears when you're connected using ethernet.
[Raspberry Pi Original Development] JavaLord:
Recovery

Hello. Can someone send me recovery image or zip file? Maybe i can use recovery and scripts for entering it from this image for emteria android image
[Raspberry Pi Original Development] KonstaT:
No. This is not the right place to ask tech support for other distributions either.

First of all Raspberry Pi doesn't have boot/recovery images/partitions in the traditional sense like other Android devices (as this is not an Android device to begin with). TWRP image included in this image only works with this build because of the partition structure. You couldn't even switch TWRP images included in LineageOS 14.1 and LineageOS 15.1 builds because of this (Oreo has additional vendor partition).
[Raspberry Pi Original Development] KonstaT:
Quick Google search tells me this is known issue building with Ubuntu 18.04. Try one of the suggested workarounds.

https://groups.google.com/forum/#!topic/android-building/0kzPnw3akxg

https://stackoverflow.com/questions/49301627/android-7-1-2-armv7