Noah E. Koeppel

I see, i tried the linux version of ImageRepacker but couldn't get it to work, i'll give it another shot or try the windows version

Curious to know how you'd get the dtb from the image, I can't figure out how to access the boot partition. All the extraction tools I found appear to be outdated.

Direct rendering is enabled

It is still the 3.10 kernel

i plugged it into the wrong power supply

Sure but it'll probably only boot on the One Plus if at all, I didn't configure ram/bt/wifi or anything it should all be default and I fried mine so I can't test it. (I might have changed something in the ram settings but it didn't seem to make a difference for me) It's a PhoenixCard image. https://drive.google.com/file/d/1l5cFJKIHqBw-nDYOPlKBXI5iGkcGC9rS/view?usp=sharing

I was able to compile the 4.9 BSP with android so if you want to give it a shot it's doable though I haven't been able to do much with it.

The https://xtrx.io/ I was looking at uses the PCIe lanes, there are no shortage of alternatives though, not a huge setback.

Lame, I was hoping to get to use a PCIe SDR on it, looks like it will be a while if ever before it's even usable

Yeah, i tried to warn you, it's not configured at all for anything specific, hopefully we'll get an actual repository for the modified source at some point.

before you make you have to $ extract-bsp in the same directory I honestly don't know the difference between a couple of those, i'd like to know.

yes, run from the android root directory $ source build/envsetup.sh or $ . build/envsetup.sh and lunch should work

yes, only for the pine image, the orange pi image is missing the rest of the framework but there are ways to fudge it

Maybe it just converts everything in that folder?

You're right, now I'm super confused, maybe it's in one of the other packages? Try building the kernel without it, if you don't get an error that says mkbootimg not found then it's all good. Otherwise I can try reinstalling 16.04 and track down what i did to make it work. edit: you can also try 'android-tools-fsutils' but I can't verify that it has that file at the moment as for new lichee I haven't tried it but it might work better (or worse) and i wouldn't even bother with the 4.9 BSP as takiser said

The sdk download from pine doesn't seem much different than the orange pi one, they're both only really usable as a starting point. The Android image for pine runs really nicely on pine and I wouldn't bother trying to build it from source at this point.

Here's what I did, I guess i skipped some irrelevant parts: (I've done this in Ubuntu 16.04 and 17.10 must be x64 ) 1. Extract the sdk and bsp into a directory, no spaces. (Get it from OrangePi MEGA or PineH64 Wiki page) You'll have an 'android' directory and a 'lichee' directory 2. Install gawk, awk will give you an error otherwise, mkbootimg(the included one didn't work for me), and java if it's not installed, as well as the android build requirements $ sudo apt-get install gawk openkjdk-8-jdk $ 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 ccache libgl1-mesa-dev libxml2-utils xsltproc unzip 3. cd to lichee and run: $ ./build.sh -p sun50iw6p1_android -c 7.x -k linux-3.10 or $ ./build.sh config then select 2 - 0 - 2 for H6 android 7.x note: if you get an error such as 'mkbootimg not found' and you're on 17.10 try 'sudo apt-get install android-tools-mkbootimg' and running the config again. 4. cd to ../android and run (must be in android root directory): $ source build/envsetup.sh or $ . build/envsetup.sh $ lunch I've had luck with petrel_*_p1 eng number 22-26 5. Extract the kernel $ extract-bsp 6. Make! $ make or optionally $ make -j# where # is number of cores for multi-thread (faster) Now you'll have a populated 'out/' folder, your android rootfs is in here if you want to do stuff to it before packing. 7. Pack for phoenixcard $ pack this will create an image in ../lichee/tools/pack/sun50iw6p1_android_petrel-p1_uart0.img 8. Flash and boot! Transfer the image to windows and burn it in startup mode using phoenixcard 4. Congratulations, you have a very buggy allwinner stock android build but hopefully you can make it work for you. A default settings image will probably work on the orangepi one plus but the further from that you get the more you'll have to configure it.

strange, i never had any issues, i'll try and make instructions for what worked for me. edit: now that I say that i have issues reproducing what I did, figures...

It's the same process, just use the new source Edit: I'll make a little guide elsewhere at some point.

http://www.orangepi.org/Docs/BuildingyourownAndroidfirmware.html That should give you a very basic allwinner image, just use the config for sun50iw6p1

maybe because I have the 4gb one

What Xalius is doing is getting Linux to boot and run on the PineH64, this probably won't be helpful for Orange Pi users anytime soon. The pine is configured a bit differently and won't boot using the default Allwinner settings.

I tried that, for me I needed supersu and zidoo had it pre-installed and beelink didn't. I think beelink also bumps the os to 7.1. I'll mess with that ota at some point and try and get su to work.

I compiled my own from the source on the website but it was even less stable. I think we either have to work with what we have or wait until more serious developers have a chance to work out some of the bugs. Personally i disabled all the Zidoo stuff with titanium backup and I don't get any errors. Aditionally I pushed a different systemui that I compiled from aosp that replaces the annoying zidoo one, i'll attach it. it goes in syste/priv-app/SystemUI/ So far i'm still having issues with play services but i'm able to use a browser on my PC to trigger apps to install so it could be worse. If you're getting errors you can try pushing an updated play store, search google, it goes in /system/priv-app/Phonesky/Phonesky.apk you can push Launcher2.apk in to /system/priv-app/Launcher2 for a functional launcher SystemUI.apk Launcher2.apk

So for the wifi one or even the regular one instead of using a firewall you can just replace /system/framework/services.jar with the original one from before flashing the zidoo ota and it won't load system/lib/libzdauth_jni.so which is the culpret for those popups. I'll attach the file, then just use adb; adb remount adb push services.jar /system/framework adb reboot services.jar