I wish there would be an /e/os build for Xperia 1 VI.
As far as an know there isn’t a LineageOS build yet, and I think Sony hasn’t released anything on the AOSP repo either.
But there is a community build of Xperia 1 V existing, so I have hopes 
2 Likes
Currently there is a 23.2 (and unreleased 24.0) tree of LineageOS for pdx245, the Sony Xperia 1 VI. Sadly there is no 23.0 tree which would be needed to build it against a current release of /e/os to be able to eventually create a community release. But at least there is a base for future images!
What I did do, is build an unofficial image against the 16.2 branch (but it is a dev branch, an unreleased branch!) which seems to be maintained as it contains the september security patches. As I use my 1 VI as my daily driver, I am a little bit reluctant to flash this dev based branch to my still supported (it should get a17 soon!) device. I built the image to get a little experience on how to work with /e/os builds, but if your 1 VI is lying around without usage, you might be interested in testing the image.
I must say that I can’t seem to find any other unofficial 16.2 builds and that there are already a few known bugs in 23.2 tree for pdx245 or 16.2 dev branch: * An aptX codec issue was reported, but it’s since been closed (LineageOS #10161). * VPN leak, data could be sent on the network bypassing VPN. Should be fixable with adb command (`adb shell device_config put tethering close_quic_connection -1`)
Also being a dev branch, I don’t know how the /e/os apps and os layers will function.
If you are still interested in testing, leave a note, I don’t want to post the image to the world right now as it has not been tested. Of course I completely understand if the risks are too high, an image from this user that has 0 reputation on this forum!
About me, happy /e/os user since June 2025 on a Fairphone 6. This is my first build of /e/os ever, so custom rom wise I’m not experienced. That being said I didn’t run into any issues building this rom (thanks for the great docker image team!) so there is not actually much effort from my side in this image. I do have common sense though and have many years of programming experience.
Facts about the build: checkout took 3 hours, Google blocked my IP completely three times (even regular searching wasn’t available) and because of one of those blocks was during the checkout of clang, after restarting the docker image the shallow checkout became a full checkout and clang was pulling in more than 170gb alone. I removed this repo, restarted the process and after 4gb it was done;) might be a bug in the repo sync flow, the missing shallow on restart, but I didn’t look into that further, because after a successful checkout I had everything I needed for starting the build. Building the image took around 90minutes on a AMD hx395 machine (112gb assigned as system ram).
1 Like
Hey,
I just today ran into /e/OS, I had an Oneplus 13, running on LineageOs 4 microG, but was still thinking about really making it my daily driver. Since I every now and then still think about privacy and used LOS quite a few years I decide to give /e/OS a try.
I actually wondered, if there will be a support for my, camerawise and headphone-jack-wise, beloved Sony Xperia 1 VI (it is actually running on LineageOs 4 mircoG pdx245). But I’m thinking about switching to /e/OS if there is a build for it. That’s why I came across this post and want to push things a bit further. Is there a chance to get a build for the Pdx245?