@rik Have you considered selling iodé merchandise as well, e.g. T-shirts? (Does the iodé team themselves sell any branded T-shirts?)
P.S. With the company’s authorization, of course.
1 Like
I have run this in the past, but no phone calls in 3G-less land over here at the time (and group MMS messages didn’t work at all… sadly USA users need these due to iOS infestations :-). There may be one or 2 handsets that possibly support VoLTE now but I know it is still fairly unreliable. Anyway, point is that Droidian or Ubuntu Touch, mainline postmarketOS, or Sailfish are all possible for a tinkerer. Only FuriOS is polished enough I suspect and even then may not daily driveable just yet depending on use case (OK sorry now I am the one off topic!)
There are some serious downsides for anyone that feels the need to run MicroG I accept, but if you are used to getting every thing you need via webapps and you are only using Waydroid for FOSS apps then most all the functional snags are at least mitigated if not completely eradicated.
Only major downside on my system is that I can stream video but can’t record it. Some what ironic after what I was saying earlier about Sony and their camera tech’. I accept that it is going to need a lot of serious development before it will have any appeal for those that want to keep a foot in both camps, but I have a feeling that even they will have to bite on the privacy bullet at some point in the not too distant future if screwgle continue to have their way with android.
Thanks for the explanation! Especially the last point makes it a lot more understandable for my side.
I love the sustainable part of iode to give lots of devices a second life because they support the hardware of a variety of phones. Lately I switched most of the ones I own to the cleaner L4M with faster updates.
Yes, L4M is great for taking LineageOS and preinstalling microG. I contribute there (a bit behind on my contributions), and @petefoth is the lead there. We at L4M don’t have device relocking which personally not a big concern for me, but I think my customers prefer to not be warned their device may be compromised every time they boot . Also there are some extra bits of iodéOS like microG being able to report that the “CTS Profile” matches and also be seen as “bootloader locked” (even if it isn’t ) that we weren’t successful in implementing with L4M. iodéOS having these bits means it is a bit more compatible with some of the more “fussy” banking apps (but of course not all of them).
L4M also makes userdebug builds which means you can get full backups via adb root that aren’t possible on iodéOS (which makes user builds and thus no adb root availability).
I guess my point is that L4M is great, there are a few + and a few - to each, and we (L4M and iodéOS) collaborate together.
1 Like
Thanks for that thorough explanation!
Is Iode based on L4M or LOS actually?
As I mostly have Samsung phones which bootloaders can’t be relocked theres no difference there right? They get the warning everytime.
But it’s not possible on samsung phones right?
That sounds pretty interesting to me, how does that work? Only with rooted devices, right?
No, iodé uses their own build process, but it pulls in upstream LineageOS sources and vendor sources just the same as the others. The los4mg (l4m) build process is used to make the unofficial iodéOS builds for Sony devices (@petefoth ) and Pixel devices (me). Here is how that build process works: Home · lineageos4microg/docker-lineage-cicd Wiki · GitHub
Correct. Only if devices are able to be re-locked (manufacturer dependent) is that possible. Pixels, Fairphones, Motorola(?) yes, but several others “no” (Sony, Samsung?)
Using iodéOS (even with an unlocked bootloader), if you have the various microG SafetyNet bits enabled, many apps that think they are verifying the bootloader is locked will succeed, it is a bit of the part that iodé has that l4m doesn’t have. But you have to test to see what works or doesn’t work with both iodéOS and los4mg to confirm.
No root is needed. adb root runs on non-rooted userdebug builds (but not on user builds like iodé official builds). Here is the project commonly referenced that people use for full backup and restore (note I haven’t used it before myself): GitHub - AndDiSa/android_backup_project
2 Likes
How is the business going? I hope it’s going good.
1 Like
Thanks for checking back. To answer, I believe the very few customers are quite happy but I have not yet broken the marketing / awareness raising gap to raise that much interest. I can say the *few* people contacting me actually lead to a very high “contact to sale” ratio .
I do have a few older damaged devices (cracked screens) that I am testing repairs on (replacing the glass only not the digitizer) as I am realizing that cracked glass Pixels (with working digitizers) are a place I could get devices to then resell for lower prices. Full non OEM replacement screens are often not good enough quality (low refresh rate, low resposiveness, getting fingerprint sensor working correctly, and washed out colors etc.), but genuine replacement screens often nearly match the entire device price, so basically if it is a broken screen it is sadly nearly a disposable device 
.
2 Likes
Hi
If you want to go to the repair crack glass on screens you could check these:
I’ve bought a few of their kits but did not have time to check them..
1 Like
Yup, that is exactly the kit I purchased to test with a Pixel 3a XL: First to test on a totally dead display which went well to separate the glass, next when I get more brave is to do it on another Pixel 3a XL with a cracked screen but working display . Having kids that return phones to me when they have issues means I have a few of these to experiment on