I confirm this issue on my FP3+, 100% times when I boot it under 10%. Additionally, it's exactly 10%, so it seems either firmware or UT software. If it were hardware, I would expect this 10% to drift over years (with the battery getting old), or being slightly different on different devices.

@homer there are no bugs about any of that on github, you should report it so more people who develop or work on the app can know about the bugs, and try to fix it.

@luksus I don't think I enabled adb while in developer settings. So this part was probably my mistake

@domubpkm works well for me thanks

I upgraded to the latest waydroid images and faced the same issue. Executing sudo sed -i '/aidl/s/2/3/' /etc/gbinder.d/anbox.conf after making rootfs writable did solve it. (like described in the thread posted above)

@kugiigi I think it's the same issue as this old bug report: https://gitlab.com/myii/ut-tweak-tool/-/issues/32 instead of copying an old value over this time the default for the device changed ¯\_(ツ)_/¯

@arubislander unfortunate, but no surprise there ¯\_(ツ)_/¯ I installed UT20.04 on my Fairphone 4 (which is waiting for waydroid for me to make the switch) and that works for music. Even BT multipoint works between the Momentum 4, FP4, and an ubuntu laptop :party_popper:. not sure yet about calls on any of them. @muskist No, it clearly identifies the headphones as "MOMENTUM 4" and claims to be connected, but without signal strength @RedXXIII I don't have any other bluetooth devices to test this with, but at least I can confirm music working on a FP4/UT20.04.

@fp3plusrt Alright, have fun :-).

@3r853n or just use this link from the ubports-installer: https://androidfilehost.com/?fid=7161016148664787652

@luksus hm... I have deinstalled and reinstalled the cam app, now it maybe works, haven't had this error since I've reinstalled the app some days ago...maybe it is solved...thanks but I'm now still in the stable repo...

Hi @homer There is this: https://docs.ubports.com/en/latest/systemdev/index.html Most documentation is there @ docs.uports.com At least the documentation I know of. The rest is diluted in the aether of internet forums and chat rooms as well as in people's brains.

@homer what do you mean by "now"? Now after you updated the bootimage, Or now after you did an OTA-Update? If you are not already there, try the RC or devel update channels. For me, bluetooth is not crashing the UI. Maybe you could check the archived unity8.log.*.gz files in /home/phablet/.cache/upstart.

@arubislander OMG, I am a moron. You ere right. I installed uAdBlock and without paying attention, I simply checked ALL the filters on. I looked through their filter list and, sure enough, there were several Social Media Block lists that were checked. Once unchecked, all my social media sites work again.

@luksus I do like auto brightness the bug is not always present. When its the case I fight with the device to switch off the screen

I nearly forgot that I posted this already as I didn't use the hotspot recently... @Luksus @kugiigi Thanks for both hints to restart Unity through the UTT and flight mode. It looks like my observation about the restart of Unity was a bit backwards. Restarting Unity enables the hotspot indicator, but turns off the hotspot immediately oO In any case I can now disable the hotspot and get the wifi back. @domubpkm can confirm the micro shenanigans. After a successful call the mic won't work in waydroid/whatsapp until I reboot. luckily I don't do that many calls either way For the camera disabling and enabling the permission worked for me so far in all instances of that happening.

@oden Glad to hear it worked.

@stemy I can't confirm this. When were you notified of the missed calls?

@lakotaubp many thanks, that worked for me ... great .. have now installed the microG, workes great, I think maybe better than on /e/...

@mikeand if you are still interested in solving this issue, you could try the following: with Ubuntu Touch started, open a terminal and make the root partition writable writeable: sudo mount -o rw,remount / Edit the ril_subscription.conf (There are two files, the FP3.conf should be leading, but to be sure, edit both): sudo nano /etc/ofono/ril_subscription.conf # and sudo nano /etc/ofono/ril_subscription.d/FP3.conf Add useDataProfiles=true: # Ofono configuration for FP3 [Settings] #EmptyConfig=false #Identity=radio:radio #3GLTEHandover=true #SetRadioCapability=auto SetRadioCapability=off emptyPinQuery=false radioPowerCycle=false confirmRadioPowerOn=false useDataProfiles=true [ril_0] transport=binder:name=slot1 name=slot1 [ril_1] transport=binder:name=slot2 name=slot2 Then save it, selecting the "Nano" keys at the burger-menu above the keyboard and tapping "Ctrl-X", then hitting "y". If everything is done, reboot the device.

@007fred50 for the new camera module to work, you need to upgrade to android 10 first and then reinstall Ubuntu Touch using the ubports installer. The camera has a 48 megapixel sensor, but still produces 12 megapixel images, using a technique called pixel-binning. It combines 4 pixels to one to improve image quality, mainly in low light conditions.