My local box store had a PrePaid TCL A30 at a good price which I bought with the intent of building/installing my own privacy firmware. It comes with Android 11 so it should be treble compatible.
TCL A30 specs at gsmarena
Background. I currently run GrapheneOS on a Pixel 3A with F-Droid apps only and have built firmware with OpenWRT (MediaTek MT7621a based router build accepted), and test built GrapheneOS,, Treble_experimentations and Lineageos.
I like the barebones minimalist approach that GrapheneOs took with the included apps with a few added apps from F-Droid.
I think there are several ways to reach that goal.
GrapheneOS has a generic build but I am worried about the lack of Mediatek roms. Still, if it is truly Treble compatible, theoretically, it should work. Anyone tried a GrapheneOS GSI?
phhusson treble_experimentations with FOSS seems ideal although I would like to substitute either Vanadium or Ungoogled Chromium for browser/webview.
Has anyone gone down this road?
Related
Google has made it mandatory for devices launched with Android Oreo to have Linux Kernel 4.4 and Project Treble but
Older Android devices released prior to Android O but that will be upgraded to Android O can continue to use their original base kernel version if desired.
Click to expand...
Click to collapse
From AOSP/Google (I can't yet put links to source as I don't have 10 posts yet)
Which includes our OnePlus 3T. As OnePlus has already said Android Oreo will be the last major update for our device (officially) we might not get Project Treble (like Nexus 5X and 6P) and Linux kernel 4.4 (a major update from our current 3.18) making it very difficult for the developer community to port future updates as Android P and above might only have Treble base unlike Android Oreo.:crying:
That would be a another bummer after there limited support announcement for 3t. For know I keep my fingers crossed for a better message on this front.
Still if images are released for AOSP you still will get development for our phone though. ?
Goku80 said:
Still if images are released for AOSP you still will get development for our phone though. ?
Click to expand...
Click to collapse
Exactly. Honestly I don't see why Project Treble matters to the average ROM user. I just want my phone to work and perform well and have a decent battery life. Besides that I don't really care. Currently I have a Nexus 6 and just replaced the battery in it but I'm perusing the forums for various devices (this was one of them) that I may be interested in. I want to see how the development community is for each one before I decide. Reason I may be considering this over the OP5 is I have heard bad things about the screen and jelly scrolling.
rjmxtech said:
Honestly I don't see why Project Treble matters to the average ROM user.
Click to expand...
Click to collapse
You don't see why?
Let me help you out:
Ars Technica said:
Custom ROMs shouldn't need to be painstakingly hand-crafted for individual devices anymore—a single build should cover multiple Treble devices from multiple manufacturers. Imagine the next time a major new version of Android is released. On Day One of the AOSP code drop, a single build (or a small handful of builds) could cover every Treble device with an unlocked bootloader, with a "download Android 9.0 here" link on XDA or some other technical website.
Click to expand...
Click to collapse
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
I totally agree this !
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Exactly! Development and porting of Custom ROMs will become easier than ever before and porting of future versions of Android will also become way lot easier (if possible at all as future versions of Android might become completely dependent on Project Treble unlike Android Oreo which is compatible with both)! And porting Project Treble is very very difficult if not impossible (unless you are the Silicon Manufacturer) !
So lets together spread the information about the importance of Project Treble and pressure OnePlus to provide Project Treble with #WeWantTreble
We shall Never Settle!
#WeWantTreble
Sent from my ONEPLUS A3003 using XDA Labs
Lets spam Carl Pei twitter with questions regarding this..
(Well not really spam, that would be rude, more like a lot of people asking him same question in shorts period of time)
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
i have red somewhere that pixel devices support treble. Same Soc, should have supported. idk.
From my experience as a Junior Android developer and reading the papers about the project treble, i could say that if there is a little group op3t developers who want this, this can be possible.
UltimateGoblin said:
You don't see why?
Let me help you out:
Click to expand...
Click to collapse
Interesting. But I assume there would still be issues even if they tried to make a universal solution.
Lyokacanthrope said:
I could be wrong but I think Treble integration is likely more on the SoC vendor than it is the OEM making the device. While they work hand-in-hand, I kind of doubt QCOM is going to make a Treble-compatible BSP for the 821 at this point.
Click to expand...
Click to collapse
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
DelicatePanda said:
Treble is mostly dependent on the SoC vendor as Project Treble is all about a vendor implementation with a vendor interface layer connecting it to the Android OS Framework unlike before when (parts of) Android OS Framework had to be compiled along with the vendor implementation as there was no interface layer in between them.
But Google Pixel which is also on the Qualcomm Snapdragon 821 as the OnePlus 3T has Project Treble but I also doubt how did they manage to get the silicon specific code required for implementing Project Treble during Developer Previews as generally the source code of Developers Previews is available only to Google and Qualcomm generally doesn't share the uncompiled silicon specific code even with OEMs (I might be wrong and Qualcomm and Google might be having partnership).
As there is already Project Treble for Qualcomm Snapdragon 821 (Google Pixel) I think it might be upto OnePlus to choose if it wants to implement it.:fingers-crossed:
Click to expand...
Click to collapse
Friggin' derp. How did I forget about the Pixel?
That being said, we'd still need to see how its implemented on the Pixel...As far as I know Treble also relies in a specific type of device partitioning which may be problematic for existing device adaptations. The Pixel phones already used the /vendor partition how it's supposed to be used so adapting Treble is almost a non-issue. I don't think our phone uses the same partition layout.
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
DelicatePanda said:
As of open beta 16 Oxygen OS we didn't get the new v4.4 kernel and also project Treble:crying:
Click to expand...
Click to collapse
That sucks .. even for OnePlus 5?
why the heck Carl is not replying officially on it, anywhere???
A question concerning LineageOS and "project treble":
Will LineageOS be available/compatible for/with every phone that is sold with Android 8.1?
Short answer: No.
Long answer: LineageOS support is made possible by drivers and source code for various devices being available. If they aren't, then the amount of work required to support a device is nearly impossible.
Project Treble makes security updates easier for OEMs to maintain. It does not mean they all use exactly the same hardware.
But why is there a problem to use LineageOS on every phone that supports project treble?
If all hardware specific code/drivers are sitting on the "vendor partition", which is not touched, then it should be very easy to build just one LineageOS that fits for all devices with project treble.
Or do I miss something?
Nexxus23 said:
But why is there a problem to use LineageOS on every phone that supports project treble?
If all hardware specific code/drivers are sitting on the "vendor partition", which is not touched, then it should be very easy to build just one LineageOS that fits for all devices with project treble.
Or do I miss something?
Click to expand...
Click to collapse
I think same but there is to little information about it. In that case if i install any UnOficial LineageOs and it works fine i could instal latter any oficial LineageOs trable (without vendor partition) and it should work.
But there is not any oficial explanation about it.
If only it were so easy .....
Nexxus23 said:
But why is there a problem to use LineageOS on every phone that supports project treble?
If all hardware specific code/drivers are sitting on the "vendor partition", which is not touched, then it should be very easy to build just one LineageOS that fits for all devices with project treble.
Or do I miss something?
Click to expand...
Click to collapse
On the one hand, yes, it might be not all that difficult to contrive an LOS build for originally configured as Treble-compliant devices going forward, but the vast majority of devices running LOS are never going to see a Treble-compliant ROM for a starting point in the first place. So what you are "missing" is that re-writing the HAL for every current LOS device would be a HUGE pain in the rear end. Asking for that much re-write effort is, well, not something I would consider to be terribly realistic, or even feasible. Eventually - perhaps. In any foreseeable time frame going forward - not much of a chance. You need to keep in mind that many if not most people probably head towards Lineage because their devices are no longer supported in the first place. Sure, some are just allergic to vendor bloatware or want a more generic UI, but I would wager on vendor neglect as the main driver. Could be wrong .....
Im just sharing Rom link with sources and download links.
There are many reasons why free and open source software is great. It allows someone to take a project and evolve it into something else that they see fit. Naturally, they have to follow the proper licenses that come with those projects, but when done right we can get software projects like /e/. /e/ is a fork of LineageOS that aims to be completely free of everything Google. Not only that, but there are a number of goals the developer has in mind for /e/ that more people feel are vital to a mobile operating system. This week it has been announced that the first beta of /e/ is now available for a limited number of devices (linked down below).
The original idea of /e/ came from Gaël Duval, an open source advocate, last year when he wrote a series of articles titled “Leaving Apple & Google. . .” It was in this series of articles when he announced that a new smartphone OS was currently being planned. The new mobile operating system had three goals including:
Be free from Google (no Google services, no Google search, no Google Play store, etc.)
Be far more respectful of user’s data privacy
Be attractive enough so that Mom and Dad, children and friends would enjoy using it even if they aren’t technophiles or geeks
It’s been a year and now the first beta of /e/ is available to the public. As mentioned, /e/ is a Google-free fork of LineageOS with this first beta being based on version 14.1. The ROM comes bundled with microG by default with the Mozilla Network Location Provider backend so location functionality will work even without GPS. The mail app is forked from K9 mail, the SMS app is Signal, the default chat app is Telegram (or you can use Signal), there’s a weather app, a note-taking app, a tasks app, and a map app (that, unfortunately, isn’t open source yet.) The account manager allows you to choose a single /e/ account for all services. The search engine is a fork of Searx, but Qwant and DuckDuckGo are available alternatives in the default browser (LineageOS’ Jelly.)
Depending on the addition of more build servers and more contributors who can maintain or port to specific devices, they are hoping to see the list of supported devices grow. Speaking of, here is the official list of devices that can test out this first beta of /e/ right now.
Essential Phone
Essential PH-1 – “mata”
Fairphone
FP2 – “FP2”
Google
Nexus 4 – “mako”
Nexus 5 – “hammerhead”
HTC
One (M8) – “m8”
Huawei
Honor 5X – “kiwi”
LeEco
Le 2 – “s2”
LG
G5 (International) – “h850”
Motorola
Moto E – “condor”
Moto G – “falcon”
Moto G 2014 – “titan”
Moto G 2015 – “osprey”
OnePlus
OnePlus 2 – “oneplus2”
OnePlus 3/3T – “oneplus3”
OnePlus One – “bacon”
OnePlus X – “onyx”
Samsung
Galaxy A5 (2017) – “a5y17lte”
Galaxy s6 – “zerofltexx”
Galaxy s7 – “herolte”
Galaxy S III (International) – “i9300”
Xiaomi
Mi 5s – “capricorn”
Mi 5s Plus – “natrium”
Redmi 3S/3X – “land”
Redmi Note 4 – “mido”
The developers are working on changing the DNS server from Google’s and bringing up the ROM to the LineageOS 15.1 (Android 8.1 Oreo) base.
Download links of the first beta build of /e/ for supported devices
https://gitlab.e.foundation/e/wiki/en/wikis/devices-list
Download link for Mi 5s Plus natrium
https://gitlab.e.foundation/e/wiki/en/wikis/device/natrium/info or
https://images.ecloud.global/nightly/natrium/
-source :https://hackernoon.com/leaving-apple-google-e-first-beta-is-here-89e39f492c6f?gi=da3aa461de7c
Credits: Romain Hunault , Gaël Duval for project e
Its Good to know new rom are still coming for our natrium devices
Screenshots
link no work natrium
I think mobile phone must need to use gapps. what is this rom different comparing the previous rom?
kuto232 said:
link no work natrium
Click to expand...
Click to collapse
https://images.ecloud.global/nightly/natrium/
Try this
Penchock said:
I think mobile phone must need to use gapps. what is this rom different comparing the previous rom?
Click to expand...
Click to collapse
There is micro G which worls alternative to google services. So all your apps runs without google services. This rom is google free rom.
I am not able to import contacts from the SIM option does not stop
I don't get why this is becoming a big thing, it's just LOS with microG. There are already automatic builds found at https://lineage.microg.org which are the exact same thing, but directly built from LOS roms. Maybe the difference is that there are different system apps?
Is there any watch/band focused on compatibility and based in open standards or at least with a documenteded protocol?
I am seeing that all watches supported by Gadgetbridge app for android, required reverse engineering/hacking efforts.
Is there any watch open for interconnectivity?
In my opinion buying one that doesn't require reverse engineering to sync/manage will be potentially supported by opensource software and will not make you slave of the provider app.
PineTime looks a great project but it is still on an early stage.
Can you recommend any watch/band?
I will reply to myself, the bangle.js project is the most stable and advanced smartwatch ecosystem.
It is based in espruino and apps are coded in javascript
Long story short, I went and bought a OP7T, thinking it's bootloader unlock capability would land me my choice of ROM.
I wanted to install Lineage and it's the only model that is not supported on the 7 family and it has problems with TWRP.
I need a phone that is well supported and can run Lineage microG. From my reading something like the Xiaomi F1 is well supported, tons of ROMS but a bit old. the X3 is not on the Lineage list I think.
My goal is a simple, plain google less phone, with decent camera. I'd go for the Asus ROG 3, but again don't need the gaming. just a plain googleless phone, under 2 years old. Android 10 is ok. don't want anything less.
Thanks!
I'm in the same boat as you and have done a fair amount of research. I'm likely going to buy a recent OnePlus or a Pixel phone, but waiting until these devices are officially supported (or well supported unofficially).
There is a list of devices that are currently supported by Lineage with microG
Linext - a list of LineageOS devices
anton-z-s.github.io
But a ROM with signature spoofing may work with microG
Signature Spoofing
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
The Pixel 4a with 5G is likely to be supported by Lineage within a few months, that phone seems like a good value and so could work for you.
mycorrado said:
Long story short, I went and bought a OP7T, thinking it's bootloader unlock capability would land me my choice of ROM.
I wanted to install Lineage and it's the only model that is not supported on the 7 family and it has problems with TWRP.
I need a phone that is well supported and can run Lineage microG. From my reading something like the Xiaomi F1 is well supported, tons of ROMS but a bit old. the X3 is not on the Lineage list I think.
My goal is a simple, plain google less phone, with decent camera. I'd go for the Asus ROG 3, but again don't need the gaming. just a plain googleless phone, under 2 years old. Android 10 is ok. don't want anything less.
Thanks!
Click to expand...
Click to collapse
I can confirm you that the Xiaomi Poco F1 is working extremely well with Lineage OS 18.1 (our maintainer is very active and has done a ton of work on the device).
The phone is so fast and so smooth, I never feel like getting any newer phone.
Also, Gcam ports are working near perfection on the device, and people cannot believe the quality of the shots taken with the F1 (easily compares with recent iPhones for example and can produce great pictures even in bad situations).