Please distribute release images https://help.github.com/en/github/managing-large-files/distributing-large-binaries

After flashing your release sdcard image and load my sdcard. My opi only stuck on Android logo more than 1hours. I don't know to get log.

dd command using libreelec, win32diskimg, and etcher

Noticed that pressing the power button leads to varying delay in the display going off or coming back on again. The delay is mainly on the turning-back-on side and can be 1-2secs but can sometimes remains black for several minutes - at which point I usually hard reboot

Today I had the phone plugged into the usb socket of my pc and pressed the power button to turn the display off - but it would not come back on. Un/re-plugging the usb cable made no difference but pressing the power button several times appeared to force the screen on. Here are the parts of the dmesg log which seem relevant - I disconnected the usb cable when the black screen was stuck and plugged it in again once the display returned:

[13029.862907] healthd: battery l=69 v=3903 t=0.0 h=2 st=3 c=46 chg=au
[13075.159656] alloc_contig_range: 334 callbacks suppressed[13029.862907] healthd: battery l=69 v=3903 t=0.0 h=2 st=3 c=46 chg=au
[13075.159656] alloc_contig_range: 334 callbacks suppressed
[13075.159666] alloc_contig_range: [b0a00, b0df5) PFNs busy
[13075.179255] alloc_contig_range: [b1a00, b1df5) PFNs busy
[13075.188142] alloc_contig_range: [b1b00, b1ef5) PFNs busy
[13075.198083] alloc_contig_range: [b1c00, b1ff5) PFNs busy
[13075.203852] alloc_contig_range: [b1d00, b20f5) PFNs busy
[13075.209596] alloc_contig_range: [b1e00, b21f5) PFNs busy
[13075.219281] alloc_contig_range: [b1f00, b22f5) PFNs busy
[13075.225044] alloc_contig_range: [b2000, b23f5) PFNs busy
[13075.230639] alloc_contig_range: [b2100, b24f5) PFNs busy
[13075.240137] alloc_contig_range: [b2200, b25f5) PFNs busy
[13076.103133] PM: suspend entry (s2idle)
[13076.107170] Filesystems sync: 0.000 seconds
[13076.115515] Freezing user space processes ... (elapsed 0.002 seconds) done.
[13076.128516] OOM killer disabled.
[13076.131784] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[13076.144687] printk: Suspending console(s) (use no_console_suspend to debug)
[13126.742290] musb-sunxi 1c19000.usb: Error unknown readb offset 112
[13126.742351] PM: Some devices failed to suspend, or early wake event detected
[13126.742456] musb-sunxi 1c19000.usb: Error unknown writeb offset 112
[13126.742645] android_work: sent uevent USB_STATE=DISCONNECTED
[13127.545762] OOM killer enabled.
[13127.548929] Restarting tasks ... done.
[13127.571285] healthd: battery l=68 v=3847 t=0.0 h=2 st=3 c=442 chg=
[13127.571422] PM: suspend exit
[13127.594630] healthd: battery l=68 v=3847 t=0.0 h=2 st=3 c=442 chg=
[13127.603005] healthd: battery l=68 v=3847 t=0.0 h=2 st=3 c=442 chg=
[13127.610679] healthd: battery l=68 v=3847 t=0.0 h=2 st=3 c=442 chg=
[13127.711749] android_work: did not send uevent (0 0 00000000177a9e42)
[13127.723275] read descriptors
[13127.726437] read strings
[13127.730404] init: processing action (sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1) from (/init.usb.configfs.rc:20)
[13127.780817] init: Untracked pid 10736 exited with status 0
[13127.786905] alloc_contig_range: 172 callbacks suppressed
[13127.786915] alloc_contig_range: [b0a00, b0df5) PFNs busy
[13127.859332] alloc_contig_range: [b0a00, b0df5) PFNs busy
[13127.876448] alloc_contig_range: [b1a00, b1df5) PFNs busy
[13127.887613] init: Command 'write /config/usb_gadget/g1/UDC ${sys.usb.controller}' action=sys.usb.config=adb && sys.usb.configfs=1 && sys.usb.ffs.ready=1 (/init.usb.configfs.rc:23) took 67ms and succeeded
[13127.909030] alloc_contig_range: [b1b00, b1ef5) PFNs busy
[13127.914924] alloc_contig_range: [b1c00, b1ff5) PFNs busy
[13127.922057] alloc_contig_range: [b1d00, b20f5) PFNs busy
[13127.931263] alloc_contig_range: [b1e00, b21f5) PFNs busy
[13127.947291] alloc_contig_range: [b1f00, b22f5) PFNs busy
[13127.961990] alloc_contig_range: [b2000, b23f5) PFNs busy
[13127.978973] alloc_contig_range: [b2100, b24f5) PFNs busy
[13128.063505] type=1400 audit(1594400767.204:435): avc: denied { syslog_read } for comm="dmesg" scontext=u:r:untrusted_app_27:s0:c98,c256,c512,c768 tcontext=u:r:kernel:s0 tclass=system permissive=1 app=com.arachnoid.sshelper
[13128.085121] type=1400 audit(1594400897.584:436): avc: denied { read } for comm="[email protected]" name="iio:device2" dev="tmpfs" ino=12837 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:iio_device:s0 tclass=chr_file permissive=1
[13128.106698] type=1400 audit(1594400897.584:436): avc: denied { read } for comm="[email protected]" name="iio:device2" dev="tmpfs" ino=12837 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:iio_device:s0 tclass=chr_file permissive=1
[13128.127881] type=1400 audit(1594400897.584:437): avc: denied { open } for comm="[email protected]" path="/dev/iio:device2" dev="tmpfs" ino=12837 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:iio_device:s0 tclass=chr_file permissive=1
[13138.630306] healthd: battery l=68 v=3811 t=0.0 h=2 st=3 c=674 chg=
[13138.717105] android_work: did not send uevent (0 0 00000000177a9e42)
[13138.759641] healthd: battery l=68 v=3878 t=0.0 h=2 st=3 c=116 chg=au
[13138.771147] healthd: battery l=68 v=3878 t=0.0 h=2 st=3 c=116 chg=au
[13138.821096] healthd: battery l=68 v=3878 t=0.0 h=2 st=3 c=116 chg=au
[13138.959280] android_work: sent uevent USB_STATE=CONNECTED
[13138.986621] android_work: sent uevent USB_STATE=CONFIGURED
[13139.118452] type=1400 audit(1594400897.584:437): avc: denied { open } for comm="[email protected]" path="/dev/iio:device2" dev="tmpfs" ino=12837 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:iio_device:s0 tclass=chr_file permissive=1
[13139.140026] type=1400 audit(1594400908.636:438): avc: denied { read } for comm="[email protected]" name="in_accel_z_raw" dev="sysfs" ino=22057 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[13139.161146] type=1400 audit(1594400908.636:438): avc: denied { read } for comm="[email protected]" name="in_accel_z_raw" dev="sysfs" ino=22057 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[13139.182095] type=1400 audit(1594400908.636:439): avc: denied { open } for comm="[email protected]" path="/sys/devices/platform/soc/1c2b000.i2c/i2c-1/1-0068/iio:device2/in_accel_z_raw" dev="sysfs" ino=22057 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[13146.138716] type=1400 audit(1594400908.636:439): avc: denied { open } for comm="[email protected]" path="/sys/devices/platform/soc/1c2b000.i2c/i2c-1/1-0068/iio:device2/in_accel_z_raw" dev="sysfs" ino=22057 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
[13146.155178] audit: audit_lost=101 audit_rate_limit=5 audit_backlog_limit=64

Can I build Android 10 for OPi3? Looks like latest linux kernel contains almost all required drivers

On the latest pinephone release, the screen auto rotates apps to the opposite direction of the physical orientation.

Reading whole boot partition into RAM takes a lot of boot time. Usually boot partition on production devices
used only on about 30-50%, remaining space are reserved for debug builds.

Map (numbers may be not correct):
Sector 0: Header
Sector 1-V: Kernel image, ramdisk, etc
Sector V-(TOTAL-8): Unused
Sector (TOTAL-8)-TOTAL: AVB Footer.

Read process:

1. Read Header sector into the RAM
2. Parse heaer with new abootimg get_valuable_size sub-command
3. Read only sectors with valuable data from sdcard/emmc.
4. Read AVB footer.
5. Fill remaining area with zeros using CPU.

This should save from 0.5 to 1 second of boot time.

Upstream changes.

Please add playstore dan root access in this rom

Is it possible to install microg to get their functionality? As written in their FAQ it is stated that some features like push-messaging won't work.

Microg FAQ

Currently GloDroid graphics pipeline supports only LINEAR buffers.
Since tiled buffers can increase UI performance (increase GPU cache hits), it makes sense to try to enable it.

After fixing mesa issue with modifiers: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6045 ,
now it possible to use different (mixed) buffer modifiers.

Experimental results showed that using TILED modifiers for all buffers except HWFB (Composition on client side) gives huge performance gain comparing to using linear buffers (Composition on client side case).
UI performance increase feels like about 4x on v3d GPU, and about 1.5x-2x on MALI-400.

Action items:

1. Import modifier by drm_hwomposer generic importer.
2. Allow to override modifiers with gbm_gralloc, (enable AFBC, different tiling models, etc.). Similar is hard-coded here: https://gitlab.collabora.com/spurv/gbm_gralloc/-/commit/c61679f897f76ddbab2ff3dd11a7cde9847fbfd9
   Overriding should be enabled via properties for different buffer usage flags separately.

/home/admin/GloDroid/build/blueprint/pathtools/glob.go:166 +0x455
github.com/google/blueprint/pathtools.startGlob(0xaf7260, 0xf18568, 0xc0041420c0, 0x12, 0x0, 0x0, 0x0, 0xc004142001, 0xda00000000000020, 0x0, ...)
/home/admin/GloDroid/build/blueprint/pathtools/glob.go:52 +0xb2
github.com/google/blueprint/pathtools.osFs.Glob(...)
/home/admin/GloDroid/build/blueprint/pathtools/fs.go:154
github.com/google/blueprint.(*Context).glob(0xc0000989c0, 0xc0041420c0, 0x12, 0x0, 0x0, 0x0, 0x2a2a2f6b64732f73, 0x2a2f, 0x0, 0xc004142080, ...)
/home/admin/GloDroid/build/blueprint/glob.go:64 +0x217
github.com/google/blueprint.(*baseModuleContext).GlobWithDeps(0xc00e76fd40, 0xc0041420c0, 0x12, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/home/admin/GloDroid/build/blueprint/module_ctx.go:277 +0x6d
android/soong/android.(*androidModuleContext).GlobFiles(0xc080cbe340, 0xc0041420c0, 0x12, 0x0, 0x0, 0x0, 0x12, 0xc000076300, 0xc036b41218)
/home/admin/GloDroid/build/soong/android/module.go:1504 +0x7e
android/soong/android.expandOneSrcPath(0xb0ca20, 0xc080cbe340, 0xc036b41218, 0x4, 0x0, 0x0, 0x0, 0xc000076300, 0x0, 0x0, ...)
/home/admin/GloDroid/build/soong/android/paths.go:330 +0xd99
android/soong/android.PathsAndMissingDepsForModuleSrcExcludes(0xb0ca20, 0xc080cbe340, 0xc080ff9790, 0x1, 0x1, 0x0, 0x0, 0x0, 0x6, 0x6, ...)
/home/admin/GloDroid/build/soong/android/paths.go:289 +0x446
android/soong/android.PathsForModuleSrcExcludes(0xb0ca20, 0xc080cbe340, 0xc03141b790, 0x1, 0x1, 0x0, 0x0, 0x0, 0xc000076300, 0x0, ...)
/home/admin/GloDroid/build/soong/android/paths.go:236 +0x9b
android/soong/android.PathsForModuleSrc(...)
/home/admin/GloDroid/build/soong/android/paths.go:226
android/soong/java.(*ExportedDroiddocDir).GenerateAndroidBuildActions(0xc043133100, 0xb0ca20, 0xc080cbe340)
/home/admin/GloDroid/build/soong/java/droiddoc.go:1818 +0x1af
android/soong/android.(*ModuleBase).GenerateBuildActions(0xc043133100, 0xb0ae00, 0xc00e76fd40)
/home/admin/GloDroid/build/soong/android/module.go:860 +0x706
github.com/google/blueprint.(*Context).generateModuleBuildActions.func2.1(0xc006876f00, 0xc00e76fd40)
/home/admin/GloDroid/build/blueprint/context.go:2303 +0x80
github.com/google/blueprint.(*Context).generateModuleBuildActions.func2(0xc006876f00, 0x0)
/home/admin/GloDroid/build/blueprint/context.go:2304 +0x339
github.com/google/blueprint.(*Context).parallelVisit.func1.1(0xc080c200c0, 0xc006876f00, 0xc00006e9c0, 0xc00006e960)
/home/admin/GloDroid/build/blueprint/context.go:1709 +0x30
created by github.com/google/blueprint.(*Context).parallelVisit.func1
/home/admin/GloDroid/build/blueprint/context.go:1708 +0x124
10:01:03 soong bootstrap failed with: exit status 1
ninja: build stopped: subcommand failed.build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1

Pinephone VTS results on v0.6.1 are available:HERE

The screen constantly pulses below approx 60% brightness. Pulsing becomes more noticeable as brightness is reduced to minimum.

I tried to following step on PinePhone.

1. get gd-pinephone-v0.3.0.tar.gz and extract
2. create boot microSD , "sudo bmaptool copy deploy-sd.img /dev/sdb --nobmap"
3. insert microSD
4. connect PinePhone and Ubuntu PC
5. PinePhone into fastboot mode ,but no display.
6. execute flash-sd.sh on Ubuntu PC. start to write on PinePhone
7. PinePhone reboot, but no display...
8. execute "adb logcat" on Ubuntu PC

PinePhone was no display and no LED.
But, adb shell is worked.

07-01 13:16:21.618 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.618 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.619 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.620 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.620 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6) 07-01 13:16:21.645 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.645 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.648 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.649 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.649 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6) 07-01 13:16:21.673 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.673 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.676 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.677 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.677 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6) 07-01 13:16:21.699 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.699 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.705 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.705 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.706 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6) 07-01 13:16:21.729 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.729 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.731 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.731 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.731 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6) 07-01 13:16:21.757 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.758 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.761 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.767 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.767 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6) 07-01 13:16:21.785 342 395 E hwc-platform-drm-generic: failed to import prime fd 20 ret=-1 07-01 13:16:21.785 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.788 342 395 E hwc-platform-drm-generic: failed to import prime fd 19 ret=-1 07-01 13:16:21.788 342 395 E hwc-drm-two: Failed to import layer, ret=-1 07-01 13:16:21.789 354 354 E HWComposer: presentAndGetReleaseFences: present failed for display 0: NoResources (6)

been waiting for a pretty long time on
"Fetching projects: 98% (754/763) platform/tools/tradefederation".
how big is it?

AOSP needs some modifications to become consumer product (to get into your commercial mobile phone)
Usually AOSP passed via 3 stages:

[AOSP (developed by GOOGLE)] -> [Reference Android (Enhanced by SOC Owner)] -> [Commercial Android designed for end-user (Customised by mobile phone Brand)]

GloDroid is a Reference Android, which means it is not very friendly for end-user.

Basically the idea is get benefit from final customization by Lineage OS team using the following flow:
[AOSP]->[GloDroid]->[LineageOS]

AOSP supply default wallpaper as large resolution image.
Since PinePhone and PineTab display resolution is known, we can scale-down default wall-paper to match that resolution.

This will reduce RAM usage and increase UI performance, since SurfaceFlinger won't scale wallpaper every frame anymore.

It looks as GloDroid has no OTA-update-feature yet. Would be really nice having it in.

Please add Android tv os and support remote control

Hi,

I have a SSID with a pretty long key - 26 chars to be exact :)

I could connect to this SSID using UBPORTS but in GloDriod it goes disabled. I am not sure what more debugging to send you, please ask :)

SSID is using WPA Personal, WPA2 Only - with CCMP encryption.

Thanks !

I formatted my card with deploy-sd.img at first, and tried again with deploy-sd-for-emmc.img, and both times my phone couldn't boot from it. Holding power does nothing and the LED stays unlit. The phone can boot fine from both eMMC and SD, and I've tested this with UBports on eMMC, and Jumpdrive on SD. I used the same tool to format it for Jumpdrive as I did for the recovery image (gnome-disk-utility 3.28.3).

ADB doesn't detect a device with any combination of power button presses, so it doesn't appear to be booting at all.

GmsCore:
https://github.com/microg/android_packages_apps_GmsCore

I'm wondering if we could port Android 10 to Allwinner H5 devices? The H5 has been supported by mainline kernel since 4.14 (or 4.18, I'm not sure).

And most of the Prime's drivers have also been integrated into the kernel since then. So I guess we can make a port for it?

*Edit: I'm really tired of Xunlong's Android ROM for it, well, buggy and unfinished. Really drove me mad :<

The Display is glowing sometimes and there are white borders everywhere.

Hello, could you please answer on few questions:

1. How to connect by adb via usb wire? For now when i plug it i can not see any activity. And command adb devices returning empty result.
2. What happen with video playing ? In the first your release it is worked, but for now not. How to return this possibility?

Hi,

I noted that you "needed" someone to test the eMMC install on PinePhone. I have done this - at the moment Wifi doesn't seem stable but let me know if you want any more tests.

Thanks !

The listed steps don't work with a fresh install of Ubuntu.
14.04 is recommended by Google in the linked build page. 20.04 has the same issues.

Missing:
apt-get install git gettext python3-pip libncurses5
( I think I forgot one or two too. Please try)
Not needed:
apt-get install repo

u-boot:
make: Entering directory `/home/m/GloDroid/GloDroid/external/u-boot'
Makefile:37: *** missing separator. Stop.

Line 37: undefine MK_ARCH

That's it. I'm quite amateur, so it's not something I can fix.

Host message:

Writing 'bootloader'                               FAILED (remote: 'cannot find partition')
fastboot: error: Command failed

Workaround: reboot the board and run script one more time.

Possible reason: U-boot thinks that active partition table is MBR, and can't find GPT partition.

=> mmc dev 1
switch to partitions #0, OK
mmc1(part 0) is current device
=> mmc part

Partition Map for MMC device 1  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     1               524287          00000000-01     ee


# After updating partition list:
=> part list mmc 1

Partition Map for MMC device 1  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000100      0x00000fff      "bootloader"
        attrs:  0x0000000000000000
        type:   0fc63daf-8483-4772-8e79-3d69d8477de4
        guid:   048c6e5c-5001-444a-bbd0-655f6413ffd9
  2     0x00001000      0x000011ff      "uboot-env"
        attrs:  0x0000000000000000
        type:   0fc63daf-8483-4772-8e79-3d69d8477de4
        guid:   8cab7add-9aaa-4094-b2c8-64cba5e86bbd
  3     0x00001800      0x0000d7ff      "recovery_boot"
        attrs:  0x0000000000000000
        type:   0fc63daf-8483-4772-8e79-3d69d8477de4
        guid:   5a6cdcc2-8534-4b05-bb06-39f0cc33ca9b
=> mmc part    # now partitions appeared correctly an we can continue to use fastboot   

Partition Map for MMC device 1  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000100      0x00000fff      "bootloader"
        attrs:  0x0000000000000000
        type:   0fc63daf-8483-4772-8e79-3d69d8477de4
        guid:   048c6e5c-5001-444a-bbd0-655f6413ffd9
  2     0x00001000      0x000011ff      "uboot-env"
        attrs:  0x0000000000000000
        type:   0fc63daf-8483-4772-8e79-3d69d8477de4
        guid:   8cab7add-9aaa-4094-b2c8-64cba5e86bbd
  3     0x00001800      0x0000d7ff      "recovery_boot"
        attrs:  0x0000000000000000
        type:   0fc63daf-8483-4772-8e79-3d69d8477de4
        guid:   5a6cdcc2-8534-4b05-bb06-39f0cc33ca9b

if i try to run sudo repo init -u https://github.com/glodroid/glodroid_manifest in kubuntu 20.04 this is what it shows

warning: gpg (GnuPG) is not available.
warning: Installing it is strongly encouraged.

warning: templates not found /build/git-repo-publish/parts/git/install/usr/share/git-core/templates
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
Traceback (most recent call last):
  File "/home/_______/GloDroid/.repo/repo/main.py", line 49, in <module>
    import event_log
  File "/home/_______/GloDroid/.repo/repo/event_log.py", line 167, in <module>
    _EVENT_ID = multiprocessing.Value('i', 1)
  File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 253, in Value
    return Value(typecode_or_type, *args, **kwds)
  File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/sharedctypes.py", line 108, in Value
    lock = RLock()
  File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/__init__.py", line 183, in RLock
    return RLock()
  File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 172, in __init__
    SemLock.__init__(self, RECURSIVE_MUTEX, 1, 1)
  File "/snap/git-repo/18/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
    sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied

if i try to run sudo ./.repo/repo/main.py where the error happends this message apear:

repo: warning: Python 2 is no longer supported; Please upgrade to Python 3.6+.
no --wrapper-version argument

btw: the package repo does not exists into apt,just able to install using snap,and package python-dev also does no exist anymore,has been replaced by python-dev-is-python2

Os: v0.2 (your img)
Device: plus2e
Problem:

1. Leanback launcher and Android tv launcher Fc
2. Unable download using default browser, we must using fdroid first time to install another browser
3. Unable set display resolution, so some text cropped

Ask:

1. How to enable ir remote tv/set top box?

The next branch of the device repo has already landed PinePhone support, which needed rtl8723cs that is only available in this repo at next branch.

Are there plans to support any of the Orange Pi Zero variants?

Hi,

I'm quite interested in this project but I was wondering:

1. Is there WiFi Aware https://www.wi-fi.org/discover-wi-fi/wi-fi-aware support?
2. If no, how could we contribute to add WiFi Aware Support especially for the Pi -type of phones?

Max

When trying to power up Orangepi plue2e using sd card with the deploy-sd-for-emmc.img file, nothing shows up on the monitor and the flash-emmc.sh command ends in the following error.

• ./fastboot flash gpt deploy-gpt.img
  ./flash-emmc.sh: line 4: ./fastboot: cannot execute binary file

Frequent disconnects and/or very slow connection if no clear line of sight to router, especially when battery not full. Experienced same issue on linux distro when wifi driver was changed for one with hotspot support.

I tried to build the project. Yesterday everything worked fine. Today I synced the repo and now it gives me this error:

`============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.4.0-42-generic-x86_64-Ubuntu-18.04.4-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200605.002.A1
OUT_DIR=out

[ 61% 565/913] including device/glodroid/common/Android.mk ...
FAILED:
build/make/core/base_rules.mk:325: error: device/generic/goldfish/gatekeeper: MODULE.TARGET.SHARED_LIBRARIES.gatekeeper.ranchu already defined by device/generic/goldfish/gatekeeper.
16:39:52 ckati failed with: exit status 1
build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1`

hello, i just downloaded the sdcard_trunc.img.gz file from https://github.com/GloDroid/glodroid_manifest/releases/tag/v0.1.0
and extracted via gunzip, i write it via
dd if=sdcard_trunc.img of=/dev/sdd bs=4k count=300000
and also tried it with "disk image writer" that comes out from ubuntu.
i have 3 Apecer 8GB class 10 sdcards, formatted with Gparted to Ext4.
after more than 20 tries the board didn't boot at all.
it just booted once and the green led turned on, booted into Android boot animation and stuck there.
i don't have a serial to usb yet to debug it but from the adb logs it showed a failure at "service gatekeeper cannot started" and it looped.
now that error i faced it earlier from my custom Android 7 image and it turned out that the issue was some fex entries wasn't compatible with the board which is Plus2E, i think it was related to the mmc i don't remember exactly.
do you have another img to test? maybe the GloDroid preview v4 img that is missing.
thank you.

build/make/core/product_config.mk:223: error: Can not locate config makefile for product "opi_plus2e".
05:58:41 dumpvars failed with: exit status 1

h if we want to use this for orange pi what we have to do ?

This information isn't relevant anymore!!!!

mkdir -p GloDroid
cd GloDroid
repo init -u https://github.com/glodroid/glodroid_manifest -b next
repo sync -cq

pushd external/selinux
patch -p1 <<EOF
--- a/secilc/secilc.c
+++ b/secilc/secilc.c
@@ -270,2 +270,3 @@ int main(int argc, char *argv[])
 
+               if (file_size > 0) {
                buffer = malloc(file_size);
@@ -285,2 +286,3 @@ int main(int argc, char *argv[])
                }
+               }
 
EOF
popd

source ./build/envsetup.sh
lunch
# After that you have to select your device from the list
make images

Hey guys,

I know this is probably not the perfect place to ask this but I'm just getting into this and don't really know the right forums/chats to go to. Feel free to redirect me somewhere else!

I am trying to wrap my head around the Android Open Source Project and the pieces that come together to make it work on specific devices. The image attached is my current mental model of how Android can be built. I am trying to

1. refine/restructure the mental model it if it needs it, and

2. understand better if "vendor blobs" are the only thing one needs to make AOSP work on any given device or if more is needed.

Eventually the bigger picture question I have is whether one could build "vanilla" AOSP from source and use it on a Pinephone or whether other pieces are still missing in that architecture to make it work that I have not understood/accounted for. Implicit in this is the question of whether those "vendor blobs" are all available for the Pinephone.

Any help or readings or docs you can send me to to sharpen my understanding of the pieces of the puzzle this would be great!

It is possible to install Armbian to emmc https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-usb
It is also possible to burn LibreELEC image to emmc for LibreELEC
I think, it is possible to burn Android to emmc, but probably it will require some extra work.

I'm trying to port your project to run on an Orange Pi Plus / Plus 2 and thus contribute to more users.

I created a new device dir based on the plus2e configuration files, changed the dtb kernel to the respective one for this device (sun8i-h3-orangepi-plus.dtb), did the same for the uboot configuration.

After generating the sdcard.img, android starts, but I see the TV message "Android System: There's an internal problem with your device. Contact your manufacturer for details."

Attached ttyUSB log.

Is there anyone who can and wants to help me?
minicom-09042020.txt

Best Regards from Brazil

I reported it in the other thread, but it seems you only saw the dependency issue.
It does this with both the main and next branch.
Everything else seems to build.

[ 0% 451/90066] Building U-Boot:
FAILED: out/target/product/rpi4/obj/UBOOT_OBJ/u-boot.bin
/bin/bash -c "(echo "TARGET_PRODUCT = " rpi4: ) && (mkdir -p out/target/product/rpi4/obj/UBOOT_OBJ ) && (PATH=/usr/bin:/bin:$PATH ARCH=arm64 CROSS_COMPILE=$(readlink -f prebuilts/gcc/linux-x86/aarch64/gcc-linaro-aarch64-linux-gnu/bin/aarch64-linux-gnu-) BL31=$(readlink -f out/target/product/rpi4/obj/ATF_OBJ/rpi4/debug/bl31.bin) make -j1 -C external/u-boot O=$(readlink -f out/target/product/rpi4/obj/UBOOT_OBJ) rpi_4_defconfig ) && (PATH=/usr/bin:/bin external/u-boot/scripts/kconfig/merge_config.sh -m -O out/target/product/rpi4/obj/UBOOT_OBJ/ out/target/product/rpi4/obj/UBOOT_OBJ/.config device/glodroid/platform/common/uboot.config device/glodroid/platform/common/broadcom/uboot.config device/glodroid/platform/common/uboot-sd.config ) && (PATH=/usr/bin:/bin:$PATH ARCH=arm64 CROSS_COMPILE=$(readlink -f prebuilts/gcc/linux-x86/aarch64/gcc-linaro-aarch64-linux-gnu/bin/aarch64-linux-gnu-) BL31=$(readlink -f out/target/product/rpi4/obj/ATF_OBJ/rpi4/debug/bl31.bin) make -j1 -C external/u-boot O=$(readlink -f out/target/product/rpi4/obj/UBOOT_OBJ) olddefconfig ) && (PATH=/usr/bin:/bin:$PATH ARCH=arm64 CROSS_COMPILE=$(readlink -f prebuilts/gcc/linux-x86/aarch64/gcc-linaro-aarch64-linux-gnu/bin/aarch64-linux-gnu-) BL31=$(readlink -f out/target/product/rpi4/obj/ATF_OBJ/rpi4/debug/bl31.bin) make -j1 -C external/u-boot O=$(readlink -f out/target/product/rpi4/obj/UBOOT_OBJ) KCFLAGS="-fgnu89-inline " ) && (cp out/target/product/rpi4/obj/UBOOT_OBJ/u-boot.bin out/target/product/rpi4/obj/UBOOT_OBJ/u-boot.bin.sd )"
TARGET_PRODUCT = rpi4:
make: Entering directory /home/m/GloDroid/external/u-boot' Makefile:37: *** missing separator. Stop. make: Leaving directory /home/m/GloDroid/external/u-boot'
22:46:53 ninja failed with: exit status 1

failed to build some targets (47 seconds)

We can not always guarantee that KMS card will always have /dev/dri/card0 path,
This path can depend on different factors, e.g. DTS node order, driver compiled as a module or built-in, etc.
Both drm_hwcomposer and gbm_gralloc have to always use KMS driver, not GPU.

If possible, please add a custom recovery like TWRP.

Hi,

Yes, this is Google Play Store and yes, not what Pinephone was made for...but...

After installing all of the play store "things", I get the Play Store app on my phone. Once I run it, it prompts for a login and it doesn't matter what I do, it never progresses from that stage.

I do however note on the serial console that avc is blocking a few events/file accesses for Google Play Store - would this contrib. to the issue ? Is there an easy way to disable SELinux ? I have tried the adb setenforce 0 "thing" and it doesn't seem to make a difference - even to the messages.

I guess it's best to have a separate issue for Pine64

Props are set like this:
setprop hwc.drm.device /dev/dri/card1
setprop gralloc.gbm.device /dev/dri/card1

I verified that card1 the correct device

Logs
lsof2.txt
lshal2.txt
logcat2.txt
dmesg2.txt
dmesg2-drm-debug.txt

Not sure why allocator uses card0

If I set hwc.drm.use_overlay_planes=0 I managed to get boot logo showing

$ make sdcard

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
TARGET_PRODUCT=pinephone
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=cortex-a53
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a15
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.7.1-050701-generic-x86_64-KDE-neon-User-Edition-5.19
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ2A.200305.004.A1
OUT_DIR=out
============================================
[ 0% 4/27791] Creating sdcard image...
FAILED: out/target/product/pinephone/sdcard.img
/bin/bash -c "PATH=/sbin:/bin:/usr/bin:$PATH device/glodroid/platform/tools/gensdimg.sh -C=out/target/product/pinephone -T=SD -P=sunxi out/target/product/pinephone/sdcard.img"
===> Create raw disk image
dd: failed to open 'out/target/product/pinephone/sdcard.img': No such file or directory
[ 0% 6/27791] Target dtb image: out/target/product/pinephone/boot_dtbo.img
FAILED: out/target/product/pinephone/boot_dtbo.img
/bin/bash -c "out/host/linux-x86/bin/mkdtboimg.py cfg_create out/target/product/pinephone/boot_dtbo.img out/target/product/pinephone/gen/DTBO/dtbo.cfg"
Traceback (most recent call last):
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/internal/stdlib/runpy.py", line 72, in _run_code
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/main.py", line 12, in
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/internal/stdlib/runpy.py", line 72, in _run_code
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/mkdtboimg.py", line 1003, in
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/mkdtboimg.py", line 1000, in main
File "/home/julian/GloDroid/out/host/linux-x86/bin/mkdtboimg.py/mkdtboimg.py", line 857, in create_dtbo_image_from_config
IOError: [Errno 2] No such file or directory: '/home/julian/GloDroid/out/target/product/pinephone/obj/KERNEL_OBJ/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtb'
22:48:30 ninja failed with: exit status 1

failed to build some targets (10 seconds)