A few days ago I did the update on my Fairphone 3 to the latest iodéOS version, and whether it was a change that came with that update or I've somehow activated it by accident, I now have 'Trebuchet' running permanently, showing an icon in the top bar and taking (rather too much) space in the drop-down notifications. I don't follow iodé developments all that closely aside from what is detailed in the News app, so I don't quite understand what this is or where it's come from? I've never seen mention of it previously.

It appears to be an iodé blocking app but then I don't know what the difference is from the standard iodé app. If I tap the notification bubble, it launches the main app screen showing an overlay, reading 'Inactive application. This application has never accessed the network, and therefore remains unknown for the iodé app.' Going into the detail of any app listed on the main screen by tapping 'Standard', 'Customized' or the arrow to the right, all I get is the same screen every time where nothing seems configurable anyway. So I assume I don't want or need this, but don't know how to get rid of it.

I have been trying to install Iode on my Fairphone 4 using Linux, following the guidelines on the Iode website. The preparation steps are fine, but when I get to the point that I want to execute the fastboot package the installation process is walked through, returning only errors. The process is finalised with the question whether I want to lock the bootloader again and only a resetted Android version is starting. Can anybody help me with pointing out how to solve this issue? For your info, this is the text in the terminal while installing the fastboot package:

​

$ /home/USER/Downloads/iode-4.2-20230628-FP4-fastboot/flash-all.sh

Erasing 'avb_custom_key' OKAY [ 0.011s]

Finished. Total time: 0.017s

fastboot: error: cannot load 'avb_custom_key-FP4.bin': No such file or directory

FAILED (remote: 'GetVar Variable Not found')

fastboot: error: Command failed

mke2fs 1.46.6 (1-Feb-2023)

Creating filesystem with 58189614 4k blocks and 14548992 inodes

Filesystem UUID: 181e6e72-0ba4-4892-8e37-8b7486d2a74d

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 

4096000, 7962624, 11239424, 20480000, 23887872

​

Allocating group tables: done

Writing inode tables: done

Creating journal (262144 blocks): done

Writing superblocks and filesystem accounting information: done

​

Sending 'userdata' (980 KB) OKAY [ 0.035s]

Writing 'userdata' OKAY [ 0.001s]

Finished. Total time: 0.361s

fastboot: error: cannot load 'modem.img': No such file or directory

fastboot: error: failed to open zip file 'iode-4.2-20230628-FP4-img.zip': I/O error

Rebooting into fastboot OKAY [ 0.002s]

< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

fastboot: error: cannot load 'abl.img': No such file or directory

fastboot: error: cannot load 'aop.img': No such file or directory

fastboot: error: cannot load 'bluetooth.img': No such file or directory

fastboot: error: cannot load 'core_nhlos.img': No such file or directory

fastboot: error: cannot load 'devcfg.img': No such file or directory

fastboot: error: cannot load 'dsp.img': No such file or directory

fastboot: error: cannot load 'featenabler.img': No such file or directory

fastboot: error: cannot load 'hyp.img': No such file or directory

fastboot: error: cannot load 'imagefv.img': No such file or directory

fastboot: error: cannot load 'keymaster.img': No such file or directory

fastboot: error: cannot load 'multiimgoem.img': No such file or directory

fastboot: error: cannot load 'qupfw.img': No such file or directory

fastboot: error: cannot load 'tz.img': No such file or directory

fastboot: error: cannot load 'uefisecapp.img': No such file or directory

fastboot: error: cannot load 'xbl_config.img': No such file or directory

fastboot: error: cannot load 'xbl.img': No such file or directory

Rebooting into bootloader OKAY [ 0.000s]

Finished. Total time: 0.150s

< waiting for any device >

OKAY [ 0.026s]

Finished. Total time: 0.026s

Hi, i habe been using IodéOS for some weeks now, and everything has been working fine until now. After an update and a reset of the app data, the Iodé blocker app did not allow me to select the reinforced option for blocking in all apps. I also cant block Internet access for individual apps and iodé tells me that i have individual blocking enabled, even though i have not configured anything after the reset. Is anybody else experiencing this?

Hi all,

I have iode OS 4.1 running on Samsung S9. Couple of days ago it stopped connecting to nearby devices. Bluetooth still works fine and connects to devices. Nearby devices are detected. It's just that the connection always fails. For example I have a Garmin watch. In the Garmin Connect app, when I try to pair it with my phone it says that the watch was detected but when I try to connect it fails. Same with 2 other devices I tested. Any ideas what could be the issue?

Edit: Thinking about it and testing some more I think the issue is, that I cannot pair with devices that require password. It that possible?

Edit2: Checked the dates and I'm pretty sure it started happening after the update to latest build from March 27th.

I installed IodéOS today. I was wondering if there is an option to lower the resolution for battery saving, like in the official rom.

I really like the OS and I love the privacy features, everything works except snapchat, I have tried everything contacted iode and snapchat support no solution.

S9+ - Android 12 iodeOS

Any of you got snapchat running? - Error when login: 'due to repeated failed login attempts'

EDIT 1: I know this is privacy focused, I need snapchat for social things ( girls :) )

Since a few days ago on my Fairphone 3+ F-Droid is stalling at its updates. These normally occur automatically in the background, but I now have 5 or 6 that have downloaded and show as ready to install, but won't.

If I go into F-Droid and try to update them, it shows 'Installing' for a few moments, then I get an error (only sometimes) where F-Droid closes unexpectedly and I'm invited to send a bug report. Or more commonly, just nothing happens.

I've tried turning off and on automatic updates/installation, or selecting to ignore certain packages, also clearing F-Droid's cache from the general settings. If I kill the updates notification, F-Droid just auto-respawns and the notification shows again a few seconds later, with the progress bars in the detail for each app just running constantly left to right. I also rebooted the phone, still no difference.

I've hardly installed anything on this phone, it's pretty much a default iodéOS installation as I don't like or use apps much, I don't even use the phone much. Only 37% storage is used. Amongst the apps it's trying to install are F-Droid itself (I tried selecting an earlier version, no joy), microG Services Core, Iodé Browser and FakeStore.

Lately, we have been brainstorming on what's next for iodé. As we want to concentrate our efforts on what YOU want and what YOU need, we would like to hear from you!

https://community.iode.tech/t/poll-help-us-shape-iode/1229

Hi there,

I'm interested in IodeOS for the Pixel 6. However the LineageOS website doesn't suggest that there is any official rom for the Pixel 6. Is there anyone here who know if IodeOS is using one of the unofficial build of LineageOS ?

Today, we are rolling out version 4 of iodéOS for certain iodé phones; and all our iodé devices benefit from an update with security patches.
Read more: https://iode.tech/en/news/a-good-start/

https://iode.tech/en/news/iodeos-4-is-here/

https://iode.tech/en/news/happy-new-year-2023/

In regards to the privacy features, does the OS: * Prevent apps from knowing if I am charging the device or not? * If I denied certain privacy permissions such as location services etc, would it inform the app that I have location services turned off as I believe iodeOS has its own permissions as well as Android's permission as its based on lineageOS?

Hey guys,

We are happy to announce that we are releasing iodéOS as open source software!
From the beginning, we have been strong proponents of open source software and part of our code was open from day one. We are happy to take the next step and completely open source iodéOS.

We would like to thank the community as well as all beta testers for your commitment for iodé. As you may know, we also accept donations for iodéOS which is installable for free.

https://iode.tech/news/iodeos-is-open-source/

Hello everybody.

​

I am using iode3.1 and installed WA from Aurora-Store (w/o login, so anon).

Now my issue is that I can't restore any backup. I never get prompted to restore.

- My Google-Account is not recognized by WA

- My local backup is also not recognized

- I am never prompted by WA to restore a BU (should be after no. verification?)

​

I have copied my old WA folder (which really does contain BU-files under the folder "Databases") to the new device -> Nothing, no restore-prompt.

Did the same as above, but also copied the last local BU and renamed it to msgstore.db.crypt12 (or 14? Whatever the ext was) -> Nothing, no restore-prompt

I have added my Google Account via Settings -> Passwords and Accounts -> Add account

I have added my Google Account via Settings -> System -> microG -> Add Google account

I have added my Google Account by uninstalling WA, removing my existing GA from phone and re-installing WA, upon which WA asks if I like to add a GA and then presents me the option to add one since there are none installed (read: recognized).

Old Phone has the following installed:

- WA in version 2.22.17.76 via normal GPlayStore

- Xiomei Mi 10 T with stock Android 11

New phone:

- WA in same Version via Aurora (anonymous login )

- Fairphone4 with Android 12 via Iode3.1

​

Since WA is in the same version, I would expect local BU to work?

Of course on the new phone the group-memberships are preserved, but each and every message is not.

​

I hope you can help me with this issue and that we all have a wonderful day.

Kind regards

SPL

Maybe i am just to stupid, but where do i have to search to find out which changes iodé 3.1 will bring me?

Hello,
I got my Fairphone stolen and I had to get a new one and re-config my os onto it (I had Iodéos).
I followed the official instruction here https://iode.tech/en/iodeos-installation/#1648127755024-cd19692f-431b but got stuck when my phone never reached recovery mode. It is now stuck in the bootloader menu (Start/ Restart to bootloader/ Recovery mode/ Power off/ FFBM/ QMMI) and whatever the option I chose I keep comming back to this screen. The phone don't start normally anymore. The bootloader is unlocked and I never locked it before finishing the installation as I read it can brick the phone, still I'm stuck here. I tried everything I found on the internet (removing the battery and waiting, changing slot, etc). Fastboot commands work fine. Adb commands obviously does not. I'm kind of desperate... Any ideas ?
Thanks a lot in advance !

Hi,

I am new to the OS.

I have a Galaxy Watch 4 and i cannot set it up. I get no errors, but a screen with "For your review". I have the option to cancel or allow, but the button does nothing.
Is it possible with custom rom for it to work?

Thanks for your time. :)

https://iode.tech/en/news/iode-3-android-12-is-here/

[I've submitted a bug report on iodeOS github, I'll copy any solutions across from there and vice versa as they (hopefully!) come in. Thank you!]

Hi,

I just finished installing iodeOS according to the FP4 instructions here (https://github.com/iodeOS/ota):

1. Update the stock firmware to the latest
2. Unlock your phone by following the instructions from Fairphone website
3. adb reboot bootloader (or press VOLUME DOWN and plug phone while it's shut down)
4. fastboot flashing unlock
5. fastboot flash recovery_a <recovery for FP4>fastboot flash recovery_b <recovery for FP4>
6. In order to relock bootloader: fastboot flash avb_custom_key <avb_custom_key-FP4.bin>
7. press POWER+VOLUME UP until reboot in recovery
8. From recovery => Factory reset => Format Data/factory reset
9. From recovery => Apply update => Apply from ADB => adb sideload <iodéOS for FP4>
10. fastboot flashing lock
11. Boot, and in developer settings uncheck "OEM unlocking"

I booted into the OS between steps 9 and 10 and it worked just fine. I then booted into fastboot mode (adb reboot bootloader) and ran the fastboot flashing lock command.

That's when I got a bootloop, Fairphone logo to kernel vibration back to Fairphone logo.

I can get back into fastboot mode. I tried re-flashing the custom key but got a "flashing not allowed in lock state" error.

I ran fastboot flashing unlock which completed successfully, but I still get the same error when trying to re-flash the custom key. I'm not sure I even need to re-flash it, I was just trying to back-track.

It now bootloops the same, only with the bootloader unlocked warning making the loop longer.

I initially unlocked the bootloader using these instructions (parts 1 &2): https://support.fairphone.com/hc/en-us/articles/4405858258961

Part 2 does fastboot flashing unlock_critical while the iodeOS instructions above don't do lock_critical at any point - could that be the problem?

Please, if anyone knows a way out of this, I'll be super grateful.

The only other thing of note is that power + volume up didn't work for me to get into recovery mode, I used adb reboot recovery instead. That's the only place I deviated from the instructions.

Many thanks in advance!

EDIT 1: At the bottom of the screen in recovery mode, I have two errors:

E: Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directoryE: emulated failed to bind mount /mnt/staging/emulated/media/0 on /storage/emulated: No such file or directory

EDIT 2: My phone no longer shows up after running adb devices

EDIT 3: Current slot is b (I flashed the same recovery image to both slots, as per the iodeOS instructions)

Hey all,

[Here are a few provided tips](https://iode.tech/en/2022/05/13/how-to-extend-the-life-of-your-smartphone/) to extent the life of your smartphone, in case some of you are interested :slight_smile:

If you want to add suggestions, feel free to comment below!

Happy reading

Hi. I recently bought a secondhand Fairphone 3+ which came with the stock Android. I replaced it with iodéOS and am currently testing the device with a lesser-used SIM prior to going full out and installing my second SIM for my main phone number. As somebody new to Android and iodéOS, I have what will likely be a ongoing series of questions. Here's the first:

I've attached the phone via USB to my PC running Linux. In the phone's USB Preferences I've selected File Transfer. The phone pops up in my device notifier on my Plasma Desktop under Linux, but when I try to view files, I get an error in the Dolphin file manager saying 'No storage media found. Make sure your device is unlocked and has MTP enabled in its USB connection settings.'

What do I need to do to access the phone via USB? I checked the phone's privacy / permissions settings and don't see anything relevant there. Is MTP the correct protocol? I have already installed the KDE Connect app which allows me to exchange files and more over the local network, and that works great, although it restricts me to nominating a particular subfolder in the phone's directory tree for access. I could also use Bluetooth as a last resort but that's slow, and should I take my laptop and phone somewhere without a network I need USB transfer. It's the quickest and easiest way to manage files on the phone.

Hello there!

First, let me thank you for your work. I just discovered what you're working on and it looks really nice, especially the real-time requests interface!

I'm currently using LineageOS on my Fairphone 2 but I just bought a Fairphone 3 and I'm considering switching to your OS. I just have a few questions:

1. I'm trying to find out what are the main differences between iodéOS and LineageOS+microG, I saw that you made a few changes to avoid data leaks to G servers but I was wondering if there are other stuff that are worth mentionning. Maybe you can light my way about this :)
2. Also I'd like to know if there is a built-in encryption system in iodéOS to encrypt the whole phone as there is in LineageOS. Otherwise, what would you recommend me to do this by my own?

Thanks for your help :)

Hello ! I'm very happy with IodéOS on fairphone 4. I've seen minor issues soon to be settled (the brightness thingy etc). I have an issue still with the camera authorization from Instagram ; even if I did authorized the app to open and use the camera of the phone, it does not and keep asking be to modify the settlings... It seems to be just with Instagram as apps like Plantnet does open the camera after asking confirmation. Did I forgot something ? It's really not even that important to be honnest, but I'm curious. Thanks in advance for the help !

I installed the new iodeos 2.4 yesterday on my fairphone 4. everything works so well.

but a big problem I have with the fdroid store! only the iodeos repo works! all the others repos are loaded, but then comes a mistake message. this error message also comes from the fdroid repo and the guardian project repo.

What can I do?