There is an issue i found. The wifi keeps dropping, my wifi is working for all devices except this pixel it says no internet. I tried deleting the connection and restarting, trued 5.0 and 2.4, is this an issue with iode, lineage, or something new ?
Its still usable by either turning the mobile data off or using with only mobile data.
I haven’t heard of these issues before, this is certainly a problem. Is this the same behavior on other wifi networks?
Can you confirm that there wasn’t an issue with wifi when lineage was on it? (and was it Lineage 22.2, before that A15 from Google?) Possibly starting again with Google A15 would be the most reliable way to proceed, effectively following the LOS instructions, just replacing the iode zip for the lineage one.
My bad I thought I had update here. The problem was wifi scanning was on by default, once I turned that off it works fine.
Been using as my daily and it works perfect now.
The problem stems from the Official Devices Page not listing it, so I have requested that an update be made there (and for it to also include the newly supported Pixel 9 tokay).
Anyway, now we are in a place where it would probably be best for me to discontinue the builds for Sunfish and guide people to migrate to the official builds. But this raises a few points:
My builds are userdebug which means you can use adb root with them for full backups (and other things but that is the main advantage).
Official builds will get OTA updates from iodé (I haven’t taken care of that for the Unofficial builds, but have intentions, it is achievable).
Official builds will allow you to re-lock the bootloader. Note that locking or unlocking the bootloader will delete all userdata.
If you want your userdata to persist, it will need some testing as to how the best way to do this is (if it is possible). At at minimum you will need to this from fastboot / recovery, as the iodé installer will wipe the device. The default flash-all.sh script will also completely wipe your device, so you will need to do a bit of tinkering on it.
I don’t currently own a device that has an Unofficial Build and and Official Build available for it, so I can’t really test migrating from Unofficial to Official. I know @petefoth owns a sunfish he may be willing to try this on in his free time, but that takes time and motivation. Anyone else want to give it a go?
I am actively looking into whether it is possible to enable rooted debugging in official user builds by e.g. changing values in .prop files on the device. For me this is the biggest issue with IodéOS, and I really do not understand why Iodé have always refused to make userdebug builds instead of the crippled (IMHO) user builds.
My main motivation is that I am thinking of buying a device for a which an official build is available but I will not run a build that does not support backup and restore via rooted debugging. If I can’t get rooted debugging working for this device and I do go ahead with the purchase, I will add the device to the list of devices for which I make unofficial builds so there will be both official and unofficial builds (which is a waste of time and effort, but a phone with no rooted debugging, and therefore no usable effective backup / restore functionality is no use to me )
I am planning to try my luck with installing on a Pixel 8a.
What are the additional boot partitions that I have to flash?
Btw, my phone is currently running GrapheneOS but that seems to be a huge drain on the battery (I am not sure why) but it used to last 4x as long as with CalyxOS.
Do I actually need to go back and install stock in order to install iodeOS unofficial? I am hoping not.
I have completed v6.7 Unofficial Pixel builds and have uploaded them to the download server (same link as listed in the table above as those links are only to the device folder).
I have confirmed a successful update on a Pixel 3a XL bonito using the “Updater app > 3 dots > Local update” option.
Yes, sorry about that. It has become available now. However, i notice now that my grapheneos version is android 16 so i guess i will be stuck here for a while (i don’t really want to go and install stock).
Btw, there are a bunch of files there (super_empty, init_boot, vbmeta) which are not mentioned at all on the LOS webpage. I ignored them, or should I not have?
An official Pixel 8a akita build (but it is beta and hasn’t yet been tested) has been made available by the iodé team:
If you have my unofficial Pixel build installed I think it would be best to do a clean install of the iodé official beta image, using the flash-all.sh (or .bat) found inside the fastboot.zip. So that will be a bit of a hassle getting your data out and in, but then you will be positioned going forward with OTA updates, etc. from the official iodé builds.
Note that with Pixel 4a, 9, 9 Pro, and 9 Pro XL official builds also available now, I would recommend users migrate to them also.
I installed the unofficial iodeOS version. Android Auto is not displayed in the pre-installed apps. Is this supposed to be the case?
I now need to root the mobile phone and will set up aa4mg.