search

GloDroid / glodroid_manifest

Android port that aims to bring both user- and developer-friendly experience in using AOSP with a set of single-board computers (SBC), phones and other devices.
471 stars 67 forks source link

Integration builds #58

Closed rsglobal closed 2 years ago

rsglobal commented 4 years ago

Latest validation builds: https://github.com/GloDroid/glodroid_manifest/releases/tag/v0.6.1

rsglobal commented 4 years ago

https://github.com/GloDroid/glodroid_manifest/releases/tag/v0.5.1

nas00 commented 4 years ago

Pulsing display issue gone Wifi stability appears improved Bluetooth can see devices but not pairing so far Youtube videos only work reliably at 240p and below No audio at all now

dewitpj commented 4 years ago

Sorry - no luck with the encrypted password - it's almost as if it forgets the password. The network goes into "Saved" but it keep prompting for the password and never connects

rsglobal commented 4 years ago

PinePhone integration build updated.

@nas00 , Could you test proper selection of PinePhone 1.2 dts, in case you have v1.2? It can be done by executing adb shell cat /proc/device-tree/compatible command.

nas00 commented 4 years ago

I have a braveheart device v1.1 - if you're after ubports edition devices, I can post a call for testers on the pine64 forum?

rsglobal commented 4 years ago

I will appreciate if you do this. I also own Braveheart v1.1. So it is only feature I can't test.

nas00 commented 4 years ago

@rsglobal is the build compatible with 3gb devices? a user on the forum is having a problem with the flashing script.

rsglobal commented 4 years ago

@nas00 , It should be compatible. According to logs from forum, there is some problem with script. Or ./fastboot file is corrupted for some reason

Count042 commented 4 years ago

@rsglobal This fails. This is a separate issue from the one that you addressed earlier with regards to the usb tethering thing.

When I flash the generated image to an sdcard, the pinephone 3gb LED will light up red. Nothing else happens. This is the same experience with if I flash either of the provided deploy images. This was done with the latest integration build. This also fails when I flash the generated sdcard image that you also suggest trying. Same result.

If you look here, at the very bottom of the page: https://wiki.pine64.org/index.php?title=PinePhone_Common_Issues

There is a small change required to address the different memory structure of the 3gb Pinephone.

I will link to the specific commit that enabled this support in uboot when I find it (I'm not sure why they didn't include the link in the pinephone wiki)

heneknenipes commented 4 years ago

Hi, I have pinephone postmarket edition (I have 3GB and 2GB RAM version). When I install Glodroid v. 0.4.0 - when I press powerbutton the screen is on all the time. Power button doesnt work as it should. How I can fix this? Thanks.

rsglobal commented 4 years ago

@heneknenipes ,
Sleep mode is currently broken. You can enable it with reverting commit https://github.com/GloDroid/glodroid_device/commit/90994b291ca55a4d747ecf21ab1b8bf2a5fc3136

Shatur commented 3 years ago

@rsglobal, I tested latest master (not next) with this commit reverted and phone always wakes from sleep.

rsglobal commented 3 years ago

Latest validation builds uploaded: https://github.com/rsglobal/glodroid_manifest/releases/tag/v0.6.0-validation

squidink7 commented 3 years ago

Just tested that build on my pinephone, and the flash-sd.sh script seems broken. I could only get it to finish by removing the line where it rebooted into fastboot before flashing the a partition, and then it still failed when it came to formatting userdata and metadata to ext4, which I did in gparted manually, now it boots up but is stuck at the android splash screen for about 20 minutes before it turns off.

AnhDQHE181109 commented 3 years ago

@rsglobal I just tested the latest validation build v0.6.0 on the Orange Pi Prime and surprisingly it successfully flashed the system onto the sd card. But then it hung at the android boot screen without any signs of going any further.

Here's what happened in the UART console: https://pastebin.com/AfawK4yH And on the screen (weird artifacts..):

1615168976295

Nice work btw! :D

dilinger commented 3 years ago

Just tested that build on my pinephone, and the flash-sd.sh script seems broken. I could only get it to finish by removing the line where it rebooted into fastboot before flashing the a partition, and then it still failed when it came to formatting userdata and metadata to ext4, which I did in gparted manually, now it boots up but is stuck at the android splash screen for about 20 minutes before it turns off.

I had the same problem with the 0.6.0 validation build. When the flash-sd.sh script runs './fastboot reboot-fastboot', it reboots into the attached screen. The script hangs forever. I tried the various options, but they don't allow the script to continue.

IMG_20210310_015203 IMG_20210310_015146

rsglobal commented 3 years ago

Fixed. Images updated. https://github.com/rsglobal/glodroid_manifest/releases/tag/v0.6.1-validation

squidink7 commented 3 years ago

I tried flashing it to my pinephone, but the deply-sd.img didn't allow my phone to boot into fastboot. I tried using the deploy-sd.img from the 0.5.1 release which worked but the flashing script got to about halfway through then stopped after 'fastboot oem format' and stayed on 'waiting for any device'

rsglobal commented 3 years ago

Thank you for reporting this. I do not have such issues on PP1.2. I'll try on v1.1 soon.

squidink7 commented 3 years ago

I'm using 1.2 Manjaro CE, are you trying to use it on your sd card or your emmc?

rsglobal commented 3 years ago

I was able to reproduce this on my device. Will fix soon. I'm using emmc.

rsglobal commented 3 years ago

Fixed. Images updated: https://github.com/rsglobal/glodroid_manifest/releases/download/v0.6.1-validation/v0.6.1_pinephone-userdebug.tar.gz

squidink7 commented 3 years ago

wow! that works awesome!! I had to change a line in flash-sd.sh to stop it from trying to reboot directly into fastboot because that caused issues, instead I rebooted manually and went into fastboot when it was done. Other than that amazing release! y'all are brilliant.

nas00 commented 3 years ago

Fixed. Images updated:

Is there a new pinetab image available?

rsglobal commented 3 years ago

https://github.com/rsglobal/glodroid_manifest/releases/download/v0.6.1-validation/v0.6.1_pinetab-userdebug.tar.gz

tophneal commented 3 years ago

For v0.6.1 on the PineTab: I couldn't get flash-sd.sh to write to the SD (sd img didn't seem to boot, adb couldn't find the device.) I used the gensdimg.sh and was able to write the resulting img to SD. It does appear to boot (dock keyboard backlights come on, and respond to quick presses of the power button,) but there is no video (or possibly just no backlight) on the display yet.

dilinger commented 3 years ago

Finally got around to testing this. It failed again, but I managed to work around it. Note that I was using the system fastboot (debian 11), rather than the fastboot from the package.

`Finished. Total time: 0.060s

I tried rerunning the script a few times, but it would just hang waiting for a device. My pinephone was at the fastboot screen, so I selected "reboot to recovery", and then from there "reboot to fastboot" (or whatever the selection is called), and then:

`dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ sudo fastboot flash boot_a boot.img couldn't parse max-download-size 'no' Sending 'boot_a' (28672 KB) FAILED (Write to device failed in SendBuffer() (Protocol error)) fastboot: error: Command failed dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ sudo fastboot flash boot_a boot.img < waiting for any device > Sending 'boot_a' (28672 KB) OKAY [ 2.597s] Writing 'boot_a' OKAY [ 2.424s] Finished. Total time: 5.079s dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ sudo fastboot flash dtbo_a boot_dtbo.img Sending 'dtbo_a' (103 KB) OKAY [ 0.012s] Writing 'dtbo_a' OKAY [ 0.067s] Finished. Total time: 0.115s dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ sudo fastboot flash super super.img

Invalid sparse file format at header magic Sending sparse 'super' 1/6 (262124 KB)

OKAY [ 23.699s] Writing 'super' OKAY [ 19.598s] Sending sparse 'super' 2/6 (262128 KB) OKAY [ 23.058s] Writing 'super' OKAY [ 14.569s] Sending sparse 'super' 3/6 (262140 KB) OKAY [ 19.631s] Writing 'super' OKAY [ 14.585s] Sending sparse 'super' 4/6 (230452 KB) OKAY [ 18.594s] Writing 'super' OKAY [ 13.154s] Sending sparse 'super' 5/6 (261112 KB) OKAY [ 21.559s] Writing 'super' OKAY [ 14.620s] Sending sparse 'super' 6/6 (19928 KB) OKAY [ 1.511s] Writing 'super' OKAY [ 7.953s] Finished. Total time: 195.083s dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ sudo fastboot --wipe-and-use-fbe Erasing 'userdata' OKAY [ 6.258s] setting FBE marker on initial userdata... Erase successful, but not automatically formatting. File system type raw not supported. Erasing 'metadata' OKAY [ 0.019s] Erase successful, but not automatically formatting. File system type raw not supported. Finished. Total time: 6.342s dilinger@e7470:~/03-03-2021-15h16m_release_next_pinephone-userdebug/gd-v0.6.1-pinephone-userdebug/artifacts/images$ sudo fastboot reboot Rebooting OKAY [ 0.005s] Finished. Total time: 0.055s`

It then successfully rebooted into glodroid. Thanks!