Not that I know of. It would be great f you could give it a try and report back
Of these LOS official devices, only xz2c,mermaid,discovery,aurora succeeded. I will try to look into the build failures for pdx203,pdx215,pdx234,pdx206,pdx214,pdx237,kirin,voyager sometime over the weekend.
I have dirty flashed the xz2c build via recovery & adb sideload , and it seems to be working fine.
All of these builds succeeded. I have dirty flashed the lilac build via recovery & adb sideload , and it seems to be working fine
Have fun!
1 Like
What was the fail with the Kirin build? @petefoth The demo’ phone is still working fine although I haven’t tried to update it yet.
Probably due to my build setup. I hope to have time to look at it this weekend
I sent the demo (Kirin) out yesterday so hopefully it will continue to behave itself as it has up till now. As for the Discovery XA2, I will spend a few quid on it and get it up and running so as I can load iode 5.0 on it. It’s too scruffy looking for me to sell anyway, so can earn its corn by using it for install and update testing. Could maybe use it as another demo’ box if needed.
These are failing because of changes in how repo init needs to be called: see this comment in the LOS4Microg issue tracker. Unfortunately, the fix involves restructuring the main script I use when building. That isn’t going to happen any time soon - certainly not this month - so neither will builds for these devices - sorry!
Now I’ll have a look at the kirin & voyager builds
These are done and uploaded.
Oh dear, that’s sad. Well, let me know if I can help in any way. I’m not very technical.
But always up to help 
happy Christmas to you to
The guy I sent the Kirin demo to came back to me this morning with a couple of relatively trivial questions regarding the installation of a couple of apps he couldn’t find on the repositories which I have since resolved, but the OS appears to be working fine for him. Will the latest Kirin version be released as an update or should I do a new install when he sends it back?
My unofficial builds are not available as OTA updates - they need to be installed manually
Just downloaded & installed the 5.8 for maple (XZ Premium) via sideload. The first install failed and the phone ended up in TWRP again. Same reason as here:
https://xdaforums.com/t/rom-14-lineageos-21-0-unofficial-1-1-2024-06-16.4658907/post-89850230
(first image) “Android rescue party trigger” etc. I then formatted /data, reinstalled and then the phone booted. Just wanted to mention that.
Thx a lot for your work!
I’m aware of that, I think you mentioned it earlier in this thread. It’s just that I’ve set the phone up with app’s that are most likely to be of interest to your regular user, so as to appeal more toward their tendency for instant gratification. 
An update rather than a reinstall would save me having to do it again. Whilst I’m on I’ve got a charging port on its way for the XA2 Ultra that should be here for tomorrow so give me something to do on boxing day.
Had to wait an extra couple of days for the charging port PCB for the XA2 Ultra to arrive @petefoth but got on with it this afternoon and can report another preliminary success.
Need to spend some time with it so as I can test it more thoroughly but the Kirin version I installed on the XA3 has continued to work fine throughout the trial. I’m tempted to leave the XA3 running the previous version on the basis of… if it ain’t broke, don’t fix it. What do you think?
I usually work with the latest available version, but what you do is up to you
1 Like
If I was planning to use it as my own phone I would, but its purpose as a demonstrator doesn’t really demand it. If I sell it on I will reinstall instead of factory reset. Looking at your list what else is still on the list as untested? Right now I have an Xp 5 ii (working but no screen), I also have an aurora (XZP), screen works but has a motherboard fault. I also have an XZ2 compact that shows signs of life but needs work. Everything else I have has already been tested or is on the supported list. I’ve got a Dual Sim XA2 coming in (working but heavily ghosted screen), just not enough of them around to justify a build.
With the exception of xz2c, none of these builds are tested.
I don’t know what you are trying to achieve: I am just making these builds for people to use as they wish, but no warranty, no testing done and no support
Not trying to achieve anything specifically as such, was just that you said you don’t have any sony’s as you use a pixel as your daily driver. Just thought it might be useful to know that some of them at least have been installed and tested. Once I’ve tested this one I’ll put it in the demonstrator pool along with pioneer and kirin. There’s probably no point in adding any more. Sony’s anyway, samsung’s might be worth a looking at as they are way more popular, but I’ve never had one, so probably best left to someone that knows their way around them.
It’s like I said before I’m retired now and need to find things with which to occupy my time. I believe that iode is something worthy of promotion, but given the total lack of interest within the iode community of finding some actual users for it in the real world, I guess truth is that in reality all I’m attempting to do is extend the time it takes before it inevitably ends up going the way of DivestOS. Same as all the other ‘great’ OSS projects.
You can’t project your joy and enthusiasm onto others and then act offended when things don’t go the way you imagined…
I would agree, but that doesn’t mean that I have to sit on my ass neither saying anything or doing anything about it either. The fact remains that statistically speaking the project is almost certain to fail in the longer term without the support of a substantial n-umber of users.
The problem I see is that iode does not offer support for users who have problems and post them here.
I would think twice about using iode… if I read that here in the forum.
That’s how you dig your own grave.
just my opinion… honest but unfortunately true!