Was /data mounted correctly when you pushed the rootfs? Did you format userdata? Also, you seem to have overlaystore enabled but overlayfs in kernel is not enabled (unless I missed something). Anyway, it is better for you to ask in t.me/ubports_porting, there are more knowledgeable than me people there that can help you, and real-time communication is preferred because porting can take a long time to succeed.

Looking further I guess that setRadioPower is the actual function returning the error: https://android.googlesource.com/platform/frameworks/opt/telephony/+/master/src/java/com/android/internal/telephony/PhoneInternalInterface.java#576 /** * Sets the radio power on/off state (off is sometimes * called "airplane mode"). Current state can be gotten via * {@link #getServiceState()}.{@link * android.telephony.ServiceState#getState() getState()}. * <strong>Note: </strong>This request is asynchronous. * getServiceState().getState() will not change immediately after this call. * registerForServiceStateChanged() to find out when the * request is complete. This will set the reason for radio power state as {@link * android.telephony.TelephonyManager#RADIO_POWER_REASON_USER}. This will not guarantee that the * requested radio power state will actually be set. * See {@link #setRadioPowerForReason(boolean, boolean, boolean, boolean, int)} * for details. * * @param power true means "on", false means "off". */ default void setRadioPower(boolean power) { setRadioPower(power, false, false, false); } So this seems to be just a general on/off toggle and should not have power saving implications. Disabling the "Cellular data" seems to only disable the data connection, not the telephony connection, and does not affect this message. Enabling "Flight Mode" does seem to make the message stop. Flight Mode also does seem to work because I can't call the mobile number anymore when flight mode is on. So is this maybe just a bogus error?

@RobTheBold I've tried this phone (Global model) with AT&T, RedPocket (AT&T) and Mint Mobile (T-Mobile). The first two don't work at all. Mint works for voice and SMS but not MMS or data. I'm giving up on this one and returning it to EBay.

@Twigg said in Fairphone "gen" 6 is there !: From what I have read above, it looks like there haven't been too many changes from FF5 to FF6, so perhaps that makes it easier for Ubuntu Touch to get released on the FF6? I said that ram and rom are the same amount, and screen only 30hz more. But SoC is completely different, hardware is different. I guess you misunderstood me, I didn't say FP6 is the same as FP5, I said Ubuntu Touch experience should be the same under FP5 and FP6.

@Smirftsch Yeah, the idea of Dekko or another email client as a core app makes sense to me. Longer term, I thought at one point I heard talk about trying to fork Thunderbird, possibly via Snaps, which will be enabled by default in 24.04. But I'm sure that'll require some work to function well in UT. Meanwhile, I hope some other input about email usage, and Dekko specifically, can help make UT more useable for you.

@peat_psuwit Thanks!

Thanks for this reaction. Looking at the repowerd source explains why I did not find more hits for "FastDormancy": most of the time, it is "fast_dormancy", with an underscore . I'll check if this brings me any further.

@sixwheeledbeast What you are describing is the same as I have. GPS: I still need to test (for you it works). Camera Glitchyness could be happening, did not have that myself. USB Dac and similar stuff can be tricky even on Android. For me it works better in UB-Touch then Android. Desktop mode / USB Video is clunky and/or broken depending on the Hardware used. Vibration and Notification is more about Waydroid then the os (It is part of a sublist in the waydroid row). The Libertine issues is FP5 unrelated. Waydroid and Vibration, Notifications passthrough and GPS are know limitation or issues. I just noted them down so if I check back on my own website later to check if something changed its working state i can know for sure. This list is just a copy of my website entry and you are right, a redundant list of "working" in the forums is no longer needed at this stage. Someone here asked for an updated and I was testing at the moment anyway so I just updated the first entry in this topic by copying my personal list to it. Calling waydroid a stopgap is a little hard that's right... I just use it that way on my phone. It is great and makes Ubuntu Touch extremely powerful in software compatibility but is mostly used to fill in for apps that are not ported or supported by the makers of the apps. On platform's like PCs it is more used as a "emulation" tool.

Screen Recorder in the OpenStore. It doesn't support sound yet though.

@uwahl This was the place. By writing a new file named places.conf in /home/phablet/.config/filemanager.ubports/, I was able to get the File Manager app to access the server. Thanks all. Technically solved issue. And yet, performance is incredibly poor. Very slow to load, and read-only.

On two Pixel 3a devices I have access to, I'm unable to reproduce the issue without Waydroid (Waydroid is installed but disabled using sudo systemctl disable waydroid-container.service). However, once Waydroid is started, the problem occurs after recording the first video. I don't have definitive proof that Waydroid is the cause in every case, but the correlation is strong enough that I attribute most of the video recording issues I've experienced to Waydroid running in the background.

@Caedem perhaps a bit late. But I installed the focal branch and tested a few things, mainly the wireless display using AnyCast device and it works bit of lagging here and there can't determine my device is too damaged. Waydroid also works pretty well. I can't test the sim or the fingerprint. And the device charging board was fried if I replaced it I won't mind testing or help port features I can test. Pretty happy to see this device alive again thanks buddy.

@TotalSonic thanks for that, really I'm interesting to see what possible solutions might be available.

@haagch im currently working on the nix-manager project + in between somethings, so it will take me a while to test. LibreWolf is secure by default like that and i will not change it, maybe a call out that this is an extremely hardened version of firefox. location is not something i can fix, this is something for librewolf devs/ ut devs to work on. UI bugs relating to clipboard are due to xwayland and will be "fixed" by running under wayland when subsurface support is introduced.

Currently only the subcategories "Volla Phone", "Volla Phone 22", "Volla Phone X" and "Volla Phone X23" exist. For example: the Volla Phone X23 has comments in this forum in https://forums.ubports.com/category/118/volla-phone-x23

To progress further with the initial flashlight idea, controlling the flash directly appears to work fine in the following way. #!/usr/bin/env bash flashOff() { printf '%s' "0" > /sys/class/leds/led:torch_0/brightness printf '%s' "0" > /sys/class/leds/led:switch_0/brightness } flashOn() { # 2 appears to be the minimum brightness value possible printf '%s' "2" > /sys/class/leds/led:torch_0/brightness printf '%s' "1" > /sys/class/leds/led:switch_0/brightness } So with a loop I can have a nice flashing pattern at the minimum brightness. Just need to find what to hook into so I can have it only running only while there is a green notifications icon. As for using the screen, I think the green envelope icon, possibly slowly moving along the top edge of the screen (to minimise any burn in); would be a nice option there.

finally got it resolved, deleted ~/Pictures (it was a symlink to other place on sdcard) and rebooted