• Content Count

  • Joined

  • Last visited

About joaofl

  • Rank
    Advanced Member

Recent Profile Visitors

905 profile views
  1. True... As buggy as the previous.. development seems to be stagnant
  2. Xunlong have released a new android image (v1.3) with Google Play working. Have anybody tested it? Any other improvement expected? Here is the link:!wbRFwYyA!a-xbNcCcBQl8UlvTdwNj-g!9TBmCJAL
  3. Video drivers were added to the H6 GPU at Allinner's git repository: Is there any progress with Armbian for the H6 boards?
  4. To get the OrangePi image with the Pine H64 image, replace the whole boot_package.fex file from one to another. If you wanna hack the dtb files, then you have to unpack the .fex file into this 3 dtb files. The first 2 can not get converted from dtb to dts. The third one does seem to be the one we are interested.. Another important point is that, when I've tried to repack the fex file with dtb files mixed from one Orange to Pine, I got an unbootable image. So there is some dependencies among these 2 first dtb files and the main one. The first bytes seem to play a role on on getting the whole thing working, dont know which. Maybe it is simply because the main dtb file is referenced somewhere else by its byte position in the files. Maybe simply by changing the files size can mess it up (only guessing). @tkaiser follows the link to the dtb and dts files extracted from android image of the PineH64:!4MMQjbbC!gonZ69Vbx4rp3F5x9Y1Cig @Noah E. Koeppel I followed the steps from this post here on linux. If you cant get it right let my know.
  5. @tkaiser I'll upload it and drop you the link asap
  6. Compiled and tested, but it seems more buggy than the image they provide. Haven't tested much, but Ive noticed for example that it doesnt go Idle. Should test a bit more, but it seems that they dont include their tunning on the image they distribute.
  7. I missed that Now its compiling... Lets see how it goes... Ill test the output image as well to check if there is any improvement compared to the previous one.
  8. That worked. But now when I type make -j 6 (which I guess is missing in your tutorial), I get another error: ninja: Entering directory `.' ninja: error: 'device/softwinner/petrel-p1/kernel', needed by 'out/target/product/petrel-p1/kernel', missing and no known rule to make it build/core/ recipe for target 'ninja_wrapper' failed make: *** [ninja_wrapper] Error 1 But notice that I'm trying to compile the PineH64 android. I've tried with all options from 22 to 26 (the petrel ones).
  9. this command requires python-lunch to work, but still, after typing it it gives the error: No such file: /home/joao/.lunchrc Should I compile from an specific absolute directory? Wont make do the job?
  10. There is another tip I found on the PineH6 forums to get GooglePlay working on it. Consists of replacing /system/priv-app/GmsCore with the /system/priv-app/PrebuiltGmsCore from the Zidoo OTA. After that play services is said to work fine.
  11. But then in the end there is only one dtb file inside /lichee/out/sun50iw6p1/android/common/sunxi.dtb On that folder there are hundreds of dts files, for different platforms, chips and boards. Its somehow related to the compiling options you provide "sun50iw6p1" but not sure how.. But we can always do the dirty job of simply replacing the the dtb file before compiling android
  12. @tkaiser I'm looking at PineH64 kernel DTS files, and there are lots of them. More specifically to the h6 chip, there seems to have these ones: joao@machina ~/Repositorios/pineh64/lichee $ find -name sun50iw6*.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-soc.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-pro_v1_0.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-perf1_v1_0.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-petrel-p1.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-qc.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-perf2_v1_0.dts ./linux-3.10/arch/arm64/boot/dts/sun50iw6p1-fpga.dts Do you have any idea where this files are referenced from? Where in the kernel source can we chose which dts to be converted into dtb, and loaded to boot? And also, how to figure out which one is being loaded? That would be the first step to make PineH64 image also compatible with the OPi @Noah E. Koeppel So far the its working. The kernel have compiled successfully. Lets see the rest. Maybe its part of the android-sdk package...
  13. This is not on ubuntu's 16.04 repositories.. How could you get it?