@Luksus thanks, that worked. Gitlab CI build is so much smoother!
About FP3+: To use upgraded modules you need to install Android 10 and as far as I know nothing based on Android 9 works.
@Luksus I will try to report them there next time.
@dblake76 as luksus said, everything in first post is valid. Even possible errors you could encounter during flashing are covered there.
So after few days of using Gitlab CI I am experiencing few minor issues:
So far the phone is a bit more stable than with GSI build.
Speaking of issues/bugs, is it better for you @Luksus to write them down here or should I open them in GitLab?
So I had some time to try flashing again and I did not manage to flash Gitlab-CI build.
I am constantly receiving error with partition size (probably):
fastboot flash system ./ubports-ci/system.img Sending sparse 'system' 1/5 (520932 KB) OKAY [ 14.473s] Writing 'system' OKAY [ 9.115s] Sending sparse 'system' 2/5 (499041 KB) OKAY [ 13.816s] Writing 'system' OKAY [ 2.879s] Sending sparse 'system' 3/5 (521678 KB) OKAY [ 14.446s] Writing 'system' OKAY [ 4.476s] Sending sparse 'system' 4/5 (522239 KB) FAILED (remote: 'data too large') fastboot: error: Command failed
Android tools are latest version:
adb version Android Debug Bridge version 1.0.41 Version 30.0.5 Installed as /usr/bin/adb
I tried to look through internet and found that this can be caused by old version of android tools (but package manager does not know any newer and it is happening on x86 machine as well as on arm64) or wrong partition size. Does anybody have the same problem?
Finally I managed to setup propperly cellular data for my operator (O2 CZ). Trivial problem - fill the name of APN (on default it's empty). It would be great if there could be some default APN config file we could edit to have it set up.
@luksus do you have any idea if taking calls and sending/receiving SMS on Gitlab-CI build consumes any cellular data? Do we have any reliable tools to measure data traffic? I guess now that my Internet connection works even without WiFi I am ready to switch builds but I do have limited data (around 1.5GB per month).
Side note - during weekend I tried to flash Gitlab-CI build using Pinebook Pro but it seems like android-tools for ARM have some limitations as I was stuck on pretty old problem - system.img was too large to flash. (stopped on step 3/5)
Regarding sudo upgrade: vibration feedback works for me but is a bit laggy now. I guess it takes around 0,2 - 0,5s to vibrate after tap on icon but it can be caused by slow loading of an app. Keyboard vibrations work but I have them usually off. However while typing I can't change sound volume of the keyboard. It just sits at its level even though phone is in silent mode.
Regarding time-bug: while describing my issue I rebooted phone this morning. It took around an 1hr to set right time, I guess I need to be more patient next time.
In the mean time I noticed an error with missing
_apt user (command
apt could not get rid of permissions) so I tried to add it manually. For now error is gone but I have no idea if I did it right or if this user has to be in specific group.
As soon as the Gitlab CI build will be able to make calls and sms, will hop on it and try but for now phone calls are important to me and I do not always have access to internet connection.
I had some time to play around with the phone. I did fresh install of halium-boot.img from your build and sideloaded ubports_gsi.zip
I found very annoying bug - System time is set to 1st January 1970 and does not matter if I have set auto or manual time set. After reboot the phone still counts since 1970.
I tried to fix that by running
sudo mount -o rw,remount / and after that performing time change but without success. On next boot I have yet again year 1970.
I also tried to perform
sudo apt update and
sudo apt upgrade. Web browser seems to improve in performance but the time issue is still there. I also noticed the phone does not respect change of timezone and just sits with that picked on first boot during settings.
BTW, I noticed there is LineageOS build for FP3. Not sure if this could help but AFAIK SailfishOS build by default relies on Lineage so it might be helpful for UBports as well.
@Luksus yes, you understand right.
system.imgdoes not boot from fresh
So far I found strange combination which works for me: