FP3 - android Q is unreliable for me. Some help please?

Hi all,
after one year of perfect running with IMG-e-0.9-p-2020042851613-dev-FP3 I decided to switch to Q. Unfortunately it was not a good idea.
First test with IMG-e-0.17-q-20210621120946-dev-FP3: the phone turns off by itself, no apparent reason. To turn it on again I need to remove the battery. Tried it for 24h, unusable, continuous shutdowns.
I say ok, it’s dev, no problem.
So I try with IMG-e-0.17-q-20210621120947-stable-FP3
The phone works better: instead of shutting down, it reboots. I’ve been testing it for 4 hours and it has only rebooted 2 times so far.
The “Styles” settings were the cause of the reboot the first time, and other subsequent slowdowns. Settings no longer works after trying to set “Styles”. In general the phone is slow, all apps open with a delay and I can see the circle symbol spinning on the screen while waiting.
My actions on the installation: I disabled MicroG and removed Notes, Mail, the navigation app, Apps with
$ pm uninstall -k --user 0 nameofpackage
I don’t know where to start to identify the problem, any help?
Thanks!

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

I’m running e-0.17-q-20210621120946-dev-FP3 without such problems.

How did you do the switch? With the official guide at https://doc.e.foundation/q-upgrade-fp3? Including the user data wipe?

Keeping the power button pressed for about 15 seconds didn’t force a reboot or start? (It usually does.)

Thank you for your reply. I got an error on the fastboot -w command, which I already had last year on the first installation but didn’t remember. So I went ahead anyway. I have reason to think that the problem is there. I’ll work on it tonight.

The tests I did this afternoon:
reinstalled Q stable IMG-e-0.17-q-20210621120947-stable-FP3 as per instructions Install /e/ on a Fairphone FP3/3+ - “FP3”

$ fastboot -w

output this error:

wiping userdata...
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-g9Qu56: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

Same error last year:

to delete /data I used

$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [  0.205s]
finished. total time: 0.205s

also i tried

$ fastboot format userdata
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-35MXqu: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

I finished the process as per the guide to install Q stable, but the phone keeps randomly turning off.

I found this now:
Debian Bug report logs - #960123 fastboot -w fails with “mke2fs failed: 1”

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924591#130

There were quirky fastboot commands which did this around in some Linux distributions for a while. Using the current Android Platform Tools tended to help.

https://community.e.foundation/search?q=%22mke2fs%20failed:%201%22%20fairphone

1 Like

TL;DR: do not ignore any errors in the result of the fastboot -w command

Background: This all happened on Debian GNU/Linux 10 (buster).
The problem is due to the bug reported here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924591#130
From there on I had to fix the problem of fastboot not working, as shown here:
https://forum.fairphone.com/t/command-fastboot-device-is-not-recognising-the-fp3/67930
on both Debian and Win10.
After several attempts, I was able to install Q from Win10 with the help of Easy Installer, fixing the missing drivers as shown here:
https://doc.e.foundation/easy-installer-windows
See Solution 1: Use Windows update
After installation with Easy Installer, fasboot also worked correctly on Debian.
Now my FP3 is on 3 days, and so far it has turned itself off for no reason twice in the first 12 hours after installation.
I’m evaluating if it happens more times. I will update the post as this progresses.
Thanks for the help!

2 Likes

Update: For the last two days fp3 has been shutting itself down for no apparent reason about 10-15 times a day. After the shutdown the phone does not charge the battery, so all activities are inhibited. I have contacted support to see what can be done.