Pete, as we discussed privately, I put kebab and lemonades on my build list. They did take a bit of tinkering with making a few commit adjustments (that you helped with), but in the end the succeeded and I uploaded 7.5 builds for them a bit ago.
However it seems I didn’t put them in my Unofficial OnePlus Builds post (now correcting):
Sorry, I’d forgotten you’d taken them over. Glad you got them to build OK. I’ll stop trying I’ll try and remember to remove yhmd from my build scripts, and you and I should have a shared list (wiki page?) listing who is building what. Another rainy day job
Hello iodeos community, I’d like to try iodeos on my Samsung a21s, there is also microg build available. Is there any community member with some spare time and necessary knowledge willing to build one for testing? thanks
The 5.24 update for billie will not appear in the Updater app on the 5.23 build. It is available here and can be installed using Recovery and adb sideload. If you don’t install 5,24 manually, then future updates will not appear either. Apologies for the inconvenience.
Hi there! I want to request a build for Samsung Galaxy A15 5G (Model: SM-A156B/DSN). This phone is built on Mediatek Dimensity 6100+ (6 nm) chipset, which is similar to the Brax Phone which runs on iode and also has a Mediatek dimensity chipset. So I am hoping that this could be a quick build, and it could also provide the community with a quick win to add a supported device! Samsung Galaxy A15 5G is a very capable and affordable phone, so adding it to the list of iode supported devices will definitely help expand the reach of iode to a wider audience
PS: The above list was not editable, so I am not sure if this is the best way to request a build? If not please let me know how, and I can follow the steps to make a formal request.
There is no LineageOS build for this phone that I could find, either official or unofficial on XDA Forums. iodéOS is built on LineageOS, so without a LineageOS build - official or unofficial - making an iodéOS build would be a lot of work.
‘Similar to’ does not mean very much when it comes to creating a custom ROM for a device: as I understand it, much of the work involved comes from dealing with the things that are specific to the exact model you are working on. The similarity may reduce the needed work, but it still leaves a lot to do.
If you have one of these devices, it looks like the only available custom ROM for it is the unofficial CRDroid build from XDA Forums, and you miught want to check out that thread in details to see if the ROM actually works.
My apologies: looking again in XDA, it seems there are no custom ROMs at all for A15 5G. So the only way for the OP to get iodéOS on the device would be if they can install the GSI.
According to this post running a GSI is possible for the 4G model, and GSIs are supposed to run on anything that is Treble-capable. Worth running the Treble Info app from F-Droid to see if it’s possible on the 5G model
Hi there,
can you try building IodeOS for the Samsung Galaxy S23? Recently, official LOS support was added for this device. I haven’t touched my S23 yet, bc I’m waiting for IodeOS. Thankyou!
PS: is the first Post still meant to be editable? I can’t seem to edit.
The edit button is hidden in the top right hand corner of the table. Then right clik on the row above where you wish to place your entry. Choose ‘row below’ from drop down box, then double clik the empty boxes to enter your text.
It doesn’t appear to work for me either (ungoogled chromium), on this particular thread Pete, but that is how it works for me on the GSi and official/unofficial supported thread lists. I have yet to post a request on this thread I admit. The edit button is hidden and only appears in the top RH corner when I hover the pointer over the list.
Could be editing is not enabled for some reason. Maybe @rik could check it out for the OP.
One thing is that the list at the top is not comprehensive with requests that have been already fulfilled. I don’t think (?) we want to have the list be a comprehensive “these are all the unofficial builds” list, instead it is just about requests for not-yet created unoffiicial builds, right? So in that case maybe they get deleted when fulfilled? But then a new person to the thread doesn’t know it exists (I guess a forum search should reveal the thread where the actual build is?)
Agreed. We have a post (I believe) which lists all builds, official & unofficial (in different tables). That post should be the definitive list, so it needs to be easily editable when new device builds - official or unofficial - are added.
I think what should happen is
This post should be locked so no new requests are made here
Create a ‘Request a device build’ template post (along the lines of the ‘Issue’ template post)
People use that template to create a post requesting a build for a specific device.
If / when a build for that device is made, the post requesting it is marked as solved (and locked?), and the ‘definitive list’ post is updated.
So if people want a build for a device we can say 'Check the definitive list. If your device is not there, request a build it by creating a post using the template.
@rik@petefoth Regarding your question about the list in OP. I can only add to the line of thoughts, so no definitive opinion here. My experience finding this thread was, that the list of devices with already successful builds was definitely good to see! as in: people are posting requests and these builds are actually getting built. Thats pretty sick to see and definitely not normal.
I agree with all suggestions though. Reducing this list to the devices withOUT successful builds but with open requests is probably more functional for the actual goal of this thread. And I checked the thread which lists all official and unofficial builds. It is quite informative and helpful!
I guess it does make sense to ‘centralize’ this type of information, instead of spreading it across different threads. I myself made the mistake today, to not see the other thread about Samsung Galaxy S23 builds, so I posted a request here from lack of awareness.
As is, the template (such as for a “new issue”) only gets applied when creating a new post, and the logic to use a template on a new post is based on the category it is created under. That was part of the reason I made “issues” a new separate category.
So we will have to think about how to do that part, but agreed on the other points. I think the “definitive list” needs a few column adjustments to make it not need monthly updates when new OTA updates (for L4M hosted builds) are made (to just update version and date). Let’s take this part of the discussion over to that thread though.