I have the unofficial iodeOS build for my Pixel 8a. However, I have noticed that many apps say that they are “Unavailable” for my device as soon as I type it. Is there a way out? Per F-Droid, I get that Aurora Store was Updated 4 weeks ago from the iodeOS repo.
For instance, Google’s Pixel camera continues to be unavailable for my device n Aurora.
If all apps show as “Unavailable” this is a common annoyance that is solved by force stopping Aurora and restarting.
But it could be that your “device spoof settings” in Aurora found in “Top right gear > Spoof Manager > Device” is listed as a non Pixel device, so check what device is active there.
If neither of those, you may need to possibly log out / login (as “Anonymous”) on Aurora and or clear Aurora’s storage and cache and re-try.
EDIT: I haven’t re-built the Unofficial Pixel Images since the fix for being able to install the Pixel Camera was made (on 10 September). I probably won’t re-build to include this patch until v6.8 is released later this month. Sorry about that…
Thanks! I was unaware of these settings but my Device is indeed set at Pixel 8a.
I will wait for 6.8 to try Pixel Camera then.
I thank you very much for all your work, and your efforts in getting this to be a supported device.
IF you want to migrate to the Official 6.7 (beta) for akita it was built after this patch was included 
Oh, I misunderstood the messages on that thread. I thought that there was an error, but it appears that only shows up while locking the bootloader.
Is this your “daily driver”? If so you may not want to muck around. But if it isn’t your daily driver, then are you willing to try out the beta build? Then we can understand better if it is a “one off” that the bootloader relocking isn’t working, etc. No pressure, just an invitation to help
Yes, it is my daily driver. however, i will get to it.
Btw, what is it about an official build (beta or otherwise) that makes the install process different? Why can’t the same thing be done for an unofficial build?
I honestly don’t get all the specifics here, but the official builds are fastboot images which do the formatting, etc. of all the partitions, but the unofficial builds are just (mainly) the system partition image which can be installed with adb sideload from recovery. I really should know a better answer here, also still learning
Partly because the people making the unofficial builds don’t have access to the build tools that Iodé use to make official builds. Neither do Iodé publish details of how they make their builds or what tools and scripts they use.
So for my unofficial builds, I use a branch of the LineageOS for microG CI/CD docker image that is modified to build IodéOS
I see, thank you both for the explanations! Perhaps, iode could make their build tools available and still keep the unofficial and the official builds separate.
Is there a benefit to keeping the iodeOS auorora, or can i uninstall it and install from the general repo? Or is it possible to keep both? Same with F-Droid. For example, breezy-weather still complains that there is a newer release available but this is not available to install. (I am still on the 8a unofficial build, not the beta.)
I use Aurora store from F-Droid (mostly on LinegaeOS for microG now: none of my regular devices are currently using IodéOS), and I have no encountered any problems with apps being unavailable.
A more interesting question would be why is Iodé making their own versions of Aurora Store and F-Droid instead of using the versions from F-Droid’s own repo? What benefit does it give, and does that benefit justify the problems these ‘not-forked’ versions seem to be causing/
I had a similar issue when setting up my new Pixel 8 pro. I has FileManager+ export the APKs from my old phone and saved to my NAS. Then, I used that file to install the app on the 8 pro. After that, Aurora/F-droid would update the apps. I used apkpure to do the same thing for 1 or 2 apps.