And LineageOS for microG
Thank you for answering me and for your tests According to wikipedia (and what I initially thought):
The app was initially released as Google Camera and supported on all devices running Android 4.4 KitKat and higher. However, in October 2023, coinciding with the release of the Pixel 8 series, it was renamed to Pixel Camera and became officially supported only on Google Pixel devices
So Pixel camera is actually a newer Google Camera with better optimization for Pixel phones (dedicated only to Pixel phones).
Gcam should be a port for Pixel/Google camera so that would be enough for me.
Thank you for testing this!
Camera performance is what I think it’s the only trade-off if you use custom ROMs (that don’t use proprietary bits for camera).
As a photographer this is important to me to obtain better pictures when needed. For work/usual stuff Aperture would be ok.
Hi brinerustle
Thank you for your suggestions. I’m not interested in CalyxOS and would use microg for Lineage OS if no better solution.
I think community is not the same as unofficial, but that is how I see it. Official /e/ gets tested and there are OTAs allowing passage from one Android version to the next one. Community probably gets some/less testing.
Community builds are endorsed by Murena, unofficial builds (that exist also for /e/) are not. So if I use a community build I get OTAs and if I report bugs someone might try to solve them while for unofficial I don’t think it’s like that.
But for “ready for production” I guess you are right. Community builds are not near official (ex-stable) builds.
Sorry for the /e/ off-topic but that was what I have extensively used on many phones in the past 3 years.
I got it wrong and am actually using a Pixel 5a (barbet) with android 15 / Lineage 22.1-20250321-NIGHTLY-barbet.
I will most likely try to migrate at some point soon and will report here. Wish me luck

I got it wrong and am actually using a Pixel 5a (barbet) with android 15 / Lineage 22.1-20250321-NIGHTLY-barbet.
I made the P5a barbet
unofficial builds, and hope to hook up OTA updates on them in the somewhat near future. Until then, updated builds (which I will make after iodé releases new versions) will have to be applied by adb sideload
in recovery.
I’m moving this thread to the GSI & Community Builds
category.

Until then, updated builds (which I will make after iodé releases new versions) will have to be applied by
adb sideload
in recovery.
Hey @rik, if you build iodeOS ROMs for Pixel devices and use an Pixel 3a XL bonito yourself, you should know the update option Local update, which has been available since iodeOS 5.x.!
.
Manuel update : A manual update can be carried out very easily without a PC and without data loss directly on the device via local update. The *.zip file downloaded directly to the ‘kirin’ is imported by the system and the update can be started. The procedure is as simple as with the OTA update.
Is there also a chance that your Pixel ROMs will receive an avb_custom_key-*****.bin to be able to relock bootloader
again?
PS: Thank you for building your iodeOS ROMs, @rik
Hi rik
Can you please share when 6.2 builds will be available? Since I don’t have much time now I’m to decide if I wait for 6.2 or go ahead with 6.1 sometime next week.
Thank you again for your work!
Hi
Sorry for the off-topic (not Pixel related)…I’ve tried local update for a Sony Xperia XZ2 premium (from 5.8 to 5.10) and it doesn’t work. I get the error
Local update
Failed to import local update
@petefoth Do you have any idea why?

Sorry for the off-topic (not Pixel related)
@Cooler
For the good of clarity, you should place your request here: Unofficial builds for Sony Xperia devices

you should know the update option Local update, which has been available since iodeOS 5.x.!
Manuel update : A manual update can be carried out very easily without a PC and without data loss directly on the device via local update. The *.zip file downloaded directly to the ‘kirin’ is imported by the system and the update can be started. The procedure is as simple as with the OTA update.
Thank you! I didn’t know that, but will try it with the next builds I make after v6.2
is released.
Is there also a chance that your Pixel ROMs will receive an avb_custom_key-*****.bin to be able to
relock bootloader
again?
I haven’t looked deeply so far, but my builds are made using the LineageOS 4 microG docker image, as userdebug
builds (allowing ADB root
for full backups / restores using various tools). I will need to learn a bit more on if it is possible to build the needed avb_custom_key
using this method.
Hi iodysseus
I’m a “frequent” poster on that thread. My post was regarding Local updates which was mentioned by you. Petefoth has not promised anywhere that the Local updates would work for his Sony unofficial builds, but I’m curious if they work for some phones and for others not what would be the reason/difference.
v6.2 was just published, I will try to get builds made in the next week. Stay tuned!
Wow. Super col!
Thank you!
I have published v6.2 builds, see the top post from me on links and install information.
Successful updates via Local update
sargo
Thank you very much for building iodéOS 6.2, @rik
Hi
How is the crosshatch working on 6.2? Any problems? I want to install it on a phone with original ROM this week (as soon as I find time and after I get my XZ2 premium on 6.2)
Thank you rik!
I coordinated with @ronnz98 to use this thread as a consolidated list for all unofficial Pixel builds. The top post is an editable wiki, so if any other unofficial Pixel builds are made, post them here!
Hi Rik, any news on this about lock the bootloader again ? Thanks!

Hi Rik, any news on this about lock the bootloader again ? Thanks!
No I didn’t get time to look into that yet, but with some work it is theoretically possible, I got a bit of advice now I need to research more and then test how to implement it.
Ok cool thanks! I will install your rom today on my Pixel 3a Thansk for your great work !