iodéOS 6.9 has just been released, be on the lookout for it in your Updater app!
From the announcement, “this release is all about giving you more control, better security, and improved flexibility. Whether it’s protecting your data with auto-reboot, securing your lock screen, or making multi-user setups more powerful, iodéOS 6.9 delivers meaningful upgrades for everyone.”
You can read more about it by following the link to our blog below:
Here is the full changelog from the new release (you can also find this in the “iodé News” app):
Auto-reboot timeout (v5 and v6): the device can automatically reboot after a configurable period without any user activity. This puts the phone in a more secure state where user data is not decrypted (Settings → Security & Privacy → More security & privacy).
Quick settings can now be disabled globally from the lock screen (v5 and v6, in Screenlock settings). This option extends an existing one that only affects quick settings considered sensitive (airplane mode, wifi, bluetooth…).
Secondary users can now be fully logged out (v4 to v6), instead of simply being switched to a different profile.
Private space (v6) and work profiles (v5 and v6) are now available for secondary users: apps such as Shelter can be used in secondary users.
App links can now be automatically validated by the apps themselves (v4 to v6). App links are URLs that can trigger the opening of an app instead of the browser, if these links are authorized by that app (in App infos → Open by default). Some apps attempt to validate these links in order to manage them instead of the browser, which was previously blocked by the system until the links were manually allowed by the user.
Blocker: a bug related to the widget has been fixed, which could cause the network to freeze. The workaround was to open the iodé app, which immediately unblocked the network.
Aurora Store: handling unattended upgrades for apps installed by Aurora Store has been improved in the system. In addition, the confirmation pop-up allowing the installation of apps has been removed: once one or more app installations have been launched, they will be completed without any confirmation from the user, even if Aurora Store is closed. These improvements are only available for the official version of Aurora Store (from gitlab) embedded into iodéOS.
iodé Browser: the onboarding process has been simplified and the icon is now vectorized, which improves its display, especially when launching the app.
Brax 3 phone: Wi-Fi calling has been fixed. For this to work, it is necessary to reset the mobile network settings (Settings → System → Reset options → Reset Mobile Network Settings). In addition, the delay before sound start-up that was sometimes occurring when booting the device has been fixed.
This is correct if you want to not be on the beta update channel anymore @d3sox . Then your updater app will only notify of stable updates starting with the next stable update newer than your existing beta (so starting with v6.10).
If you have your device re-locked and have all microG settings enabled it gives you the best chance, there are some banking apps that had issues a few months ago that now are working correctly again, such as Capital One that I use. But there are of course still others that don’t work. We don’t develop microG ourselves, but incorporate it. They still don’t have full “Play Integrity: Device Integrity” level compatibility, it is unknown when that would be supported as it is a very challenging issue to do this outside the Google ecosystem.
So I guess to answer your question (but not really answer it): you will have to inquire about your specific banking apps in posts with those apps in the title name to better get feedback from other users.
Fastboot commands provide reliable information about whether the device’s bootloader is locked or unlocked. Since not every command sequence works on every device, here are three examples.
Execute the commands in your Fastboot terminal or CMD:
fastboot oem device-info
fastboot getvar unlocked
fastboot getvar all
By the way: N26 contains 7 Tracker | 39 Permissions εxodus privacy found the code signature of seven trackers and thirty-nine permissions in the N26 banking app version 4.38.
I don’t think it’s a matter of bootloader. I’ve reinstalled FairphoneOS on my FP5 for testing (Bootloader still unlocked), and N26 is working like a charm.
I think this is due to the microG (need update) features that doesn’t match the new Google policy. Sorry, I have somme difficulties to explain
I am guessing the Developer Options variable you are referring to is “OEM Unlocking: Allow the bootloader to be unlocked”? This doesn’t actually lock a device, instead it prevents the fastboot command to unlock again in the future.
To re-lock an existing unlocked install, using fastboot flashing unlock is needed, but note that locking (or unlocking) will wipe out your userdata partition, effectively performing a factory reset and all your personal data will be gone.
Regarding the banking issue, if you have all microG options enabled including all “Self-Check” options, “Google device registration: On”, and “Google SafetyNet: On” then I believe that is the best that can be done without full Google Play Services. Sorry.
For N26 specifically, there are sadly “broken” reports from Plexus on it for Android 15 based ROMs with microG (I think you need to use the Plexus app to see more details which showed me this).
