Call for testing FP3 (also for FP3+) config for UBports-installer

Luksus

@cr9c ok sorry, then I remembered it wrong.
Then please try it with the FP3 twrp recovery.
There you should be able to wipe the cache only.

Download it https://eu.dl.twrp.me/FP3/twrp-3.5.2_9-0-FP3.img.html
And boot it:
fastboot boot twrp-3.5.2_9-0-FP3.img

cr9c

Hi @luksus ,
I did wipe data through TWRP and try again with the installer, it's NOK !
Herewith my terminal lines ...

Me@home: ~/FP3_installer$ ubports-installer -f FP3.yml
info: Welcome to the UBports Installer version 0.8.8-beta!
warn: Please update: https://devices.ubuntu-touch.io/installer/?package=deb
info: Installing Ubuntu Touch on your Fairphone 3 (FP3)
info: configuring...
info: settings: {"channel":"16.04/arm64/android9/devel","wipe":false,"bootstrap":true}
info: Downloading 1 files
info: Downloaded file 1 of 1
info: Downloading 12 files
info: Downloaded file 1 of 12
info: Downloaded file 2 of 12
info: Downloaded file 3 of 12
info: Downloaded file 4 of 12
info: Downloaded file 5 of 12
info: Downloaded file 6 of 12
info: Downloaded file 7 of 12
info: Downloaded file 8 of 12
info: Downloaded file 9 of 12
info: Downloaded file 10 of 12
info: Downloaded file 11 of 12
info: Downloaded file 12 of 12
error: Error: adb:preparesystemimage: Error: {"error":{"code":1,"cmd":"adb -P 5037 shell mkdir -p /cache/recovery"},"stderr":"mkdir: '/cache/recovery': Required key not available"}
stack trace: Error: {"error":{"code":1,"cmd":"adb -P 5037 shell mkdir -p /cache/recovery"},"stderr":"mkdir: '/cache/recovery': Required key not available"}
    at /opt/ubports-installer/resources/app.asar.unpacked/node_modules/promise-android-tools/lib/module.cjs:117:20
    at ChildProcess.exithandler (child_process.js:319:5)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1021:16)
    at Socket.<anonymous> (internal/child_process.js:443:11)
    at Socket.emit (events.js:315:20)
    at Pipe.<anonymous> (net.js:674:12)
warn: error ignored

What do you think of this ?

cr9c

Hi @Luksus
I did succeed !
In fact I had to wipe data otherwise it didn't work ;o(
I've got now the following version : ubuntu 16.04 (2021-10-12/2)
... and again THANKS for your really good job

Luksus

@cr9c thanks for the info. I was hoping that it would work without wiping data. Espescially because you were running UT before.

But finally it is good to know, what is necessary to make it work, if that kind of issue appears.

revocarne

@luksus I have only wipe userdata with TWRP, the wipe option from the installer does not work for me.

Pajlow

Hi, for me the installer shows the Channel 16.04/arm64/android9/devel. The same applies to the installed ubports recovery (Halium 9). But the installation should be Halium 10, right?

Luksus

@pajlow yes that is right.
But it is still a halium 10 port, as the system image is Halium 10.

cr9c

@pajlow said in Call for testing FP3 (also for FP3+) config for UBports-installer:

Hi, for me the installer shows the Channel 16.04/arm64/android9/devel. The same applies to the installed ubports recovery (Halium 9). But the installation should be Halium 10, right?

I didn't say it but for me it was the same.

Homer

Hi, I've noticed a bug in FP3+. When taking a call the screen starts going into screen lock and back to unlocked, flickering with 1Hz frequency. It stops only ca. After 1 minute after the call ended. How can I file this bug?
Thanks

Luksus

@homer please look into the common issues, if its there again:
https://github.com/ubports/ubuntu-touch/issues/
^^This should be your first address for issues in general.

If not, open a new issue there, or here:
https://gitlab.com/ubports/community-ports/android10/fairphone/fairphone_fp3

I also experienced this behavior, but not always. Currently it does not appear. I have installed the OTA from 3 days ago.
Please Check, if an update to the latest OTA does fix it for you.

Homer

@luksus thanks a lot for pointing the way. After sim card/phone call fail I was reluctant to update the phone anymore. Is it working well for you? Then I would try to update and check ig the error disappeared.

Luksus

@homer current OTA seems to be alright.

Homer

@luksus thanks. I did the update today, everything seems to be working. Have not tested the screen behaviour with calls, though.

Homer

@Luksus
Would you mind to help me out again? I want to bring a qml app onto the FP3. Since adb does not work yet, is openstore the only 'workaround' ( I dont consider this publishable..)

AppLee

Hi @homer
Have you tried to enable SSH to your phone ?

That's the way I prefer, it's fast and reliable.
Not sure though if it works on the FP3

Homer

@applee thanks for the hint. Will give it a try...

Luksus

@homer btw: ADB work since todays RC/devel update.
You also could just copy it over an usb connection. No?

Homer

@luksus thanks for that info. I wasn' t aware this was an option option. I wouldnt know where to put the files, and which files exactly(.click?). Maybe I the the update, via clickable/usb is most conevenient for me

AppLee

@homer
Yes you can use clickable with the USB cable.
Or if SSH is available on your phone, clickable also can use it.

Or you can push the *.click file to your phone with:

SCP if SSH is enabled
MTP to copy into one of the standard folders (Download, Documents, Pictures or Music)
ADB if you update to RC or devel as per Luksus' post