treble_experimentations

Unlock and install LineageOS or one of other alternatives. Good resource: https://github.com/phhusson/treble_experimentations/wiki

Android 12 requires Linux 4.4 for proper networking and cgroup handling, which the Pixel 1 doesn't support. Skipping those requirements isn't a good idea. p.s. status on this? thanks https://github.com/phhusson/treble_experimentations/issues/1...

Yeah, this is exactly what GSIs are meant to do - see https://github.com/phhusson/treble_experimentations/wiki/ for a nice wiki talking about taking advantage of that. I thought mobian was distributing a GSI to do non-Android on the Android base, but I can't seem to find it if they do that. Also, bear in mind that this almost intentionally doesn't solve some support problems - any bugs/vulnerabilities in the base layer won't get fixed by GSIs (which is why DivestOS says it explicitly doesn't ship a GSI).

Hey! We spoke on your Github https://github.com/phhusson/treble_experimentations/issues/2... Bootloader unlocking worked out of the box, and GSI installed without a hitch issues right now: - The flip doesn't turn on the internal screen - front screen is inoperable and just displays T-Mobile's logo after installing the APK for the radio - obviously there is no T9 keyboard with the GSI - PTT button DOES work with an add-on app that maps keys, it registers fine Happy to help anyway I can if you're interested

I just bought one of these and installed a GSI from phhusson Unfortunately there are a few things that keep me from daily use with the GSI, notably the lid switch doesn't work without the stock firmware. Less importantly, the front screen also doesn't work, but I can deal with that. WIP https://github.com/phhusson/treble_experimentations/issues/2... There is no T9 keyboard on F-Droid that I can find, and everything on the Play store is adware. Last complaint is that it's thick AF. Yes all the reviews mention it. But it's the same WxL as my iphone SE 2016, and TWICE the thickness. When I contacted CAT to retrieve the original ROM so I could fix the lid switch issue, I was met with "we do not redistribute ROMs outside of the company". Aside from the usual "You are not GPL compliant if you don't release your kernel now!" style response, this

I have an iphone SE 2016 because I too felt that new Androids were too big, switched in 2019. If too many people are upset at the price maybe you could have an Android Mini-a like the Pixel line. I had the first Pebble and have fond memories. I have high hopes for this!!!! I also love hardware but I never made it stick for work. I was one of the first engineers at Mesur.io, but things didn't work out. My other thought would be to make this highly configurable; there is a large cohort of HN crowd who also want an un-Googled Android phone, myself included. There are no un-Googled small android phones, however with Project Treble many of them can run GSIs such as this most popular one https://github.com/phhusson/treble_experimentations/releases . Of course Lineage OS deserves a mention, maybe you could ship with that, build on what the commu

Please try https://github.com/phhusson/treble_experimentations/wiki for recent devices (Android oreo and later). GSI is fine; of course not everything is perfect. Also google XDA GSI forums for specific advice

The whole GSI thing is allowing me to mess with ASOP roms on phones that would never have a customized Lineage OS release. Shoutout to Phhusson https://github.com/phhusson/treble_experimentations/releases

I had lots of luck with https://github.com/phhusson/treble_experimentations/wiki on Mi Max 3. In general any recent phone should work with these ROMs. On Mi Max 3 it works perfectly with only a few tweaks after flashing. https://github.com/phhusson/treble_experimentations/issues/1... This one, and one more for Bluetooth audio

That still leaves the option of using a GSI of whichever distribution. https://github.com/phhusson/treble_experimentations/wiki/Sam...

Right now you can get vanilla Android on most recent devices, same image for all of them thanks for the Treble project, that separated kernel and hardware drivers from Android system. https://github.com/phhusson/treble_experimentations

Prompted by your comment I reflashed my Xiaomi today with the latest A/B GSI [1], and the phone seems to be encrypted. Many thanks for your great work! https://github.com/phhusson/treble_experimentations/releases...

That's amongst the reason I do my AOSP GSI ( https://github.com/phhusson/treble_experimentations/releases... ; Generic System Image, an Android that works on pretty much all recent Android phones). Xiaomi devices are usually at sweet spots price/performance-wise (not really great hardware imo, but well). With custom ROMs (including my GSIs, but other custom ROMs are fine as well), buy a phone for their hardware, not for their software. (BTW my daily driver is a Pixel 5... not running Google adwares! Only high-end-ish device that fits my hand). However, Xiaomi devices are bricks for like a month, because before being able to install your own software, you need to be approved (connecting a smartphone on a Windows computer), and it's only once you get your smartphone that you can install your own software.

Thanks for the ROMs you produce. Do you recommend any particular devices (phones and tablets) to use a device-independent ROM? As far as I could see in your GitHub project wiki, most devices tend to have a few glitches (probably due to issues in the hardware abstraction layer from the manufacturers side?): https://github.com/phhusson/treble_experimentations/wiki I could see some that look mostly flawless, like Samsung Galaxy Tab 8.0 2019. It'd be good to have a curated list of preferred devices. Buying Android devices with ROMs in mind is quite frequent, and your generic ROMs are a huge leap ahead!