But we, and I mean, a big 'we' as everyone in XDA Developers, Lineage OS developers etc, have as a group a tremendous knowledge in this area.In fact, for the most developed phones, we know almost everything about them. If only everyone could get toghether and do something _better_ than an Android derivative...
I've been thinking for a while in Libhybris. There's a lot of people working on tweaking a library that talks to closed vendor blobs, on which every single one of them is different, to be able to use native libraries directly with files that were compiled for a framework that isn't available on the target system.
What if we could use the Android Framework as an API layer, instead of rewriting everything for every single version of every single library ever shipped with an Android phone? I am talking on stripping down most of an Android AOSP image, just up to the point where the System Server kicks in (just up to a modified Zygote or something like that), and then use the open Android API specifications to actually talk to the hardware through it. Then we could make a standard library which would work with _every single Android phone_
Ubuntu touch, Firefox OS were a failure because they weren't compatible with the existing ecosystem and because developers wouldn't invest in making apps for _yet_ another framework. But Sailfish OS has an Android compatibility layer that lets them run Android apps in their Nemo/Mer/Maemo/Meego hybrid. Chrome OS can also run Android apps.
If you can get those two poins toghether, you can have a platform where most of the available phones can run your OS, and you can also take advantage of the million of applications developed for Android. If you add that to either Ubuntu Touch, Purism's OS, KDE Mobile or any other OS which is still in development, you could have the biggest the Community has had for the last 10 years.
Edit: typos everywhere
Sounds like project Treble?
They certainly didn't go for an Android-compatible app layer though.
With HIDL it should be easier to build a clean abstraction on top of any Android base starting at Oreo.
Heck, even the carriers would be so much better off if they spent some money on similar projects. They don’t need to spend too much, and if one of them takes off, especially if it’s open source, then it helps reduce the tremendous risks they face since the mobile OS market is currently completely owned by 2 of their competitors.
However, they're not going to release that until they finish the CShell that they're working on the past several years.
No new phones being manufactured as of about a year ago, and support is ending at the end of next year.
If your device doesn't already support 15, then it's highly unlikely that it will ever seen an official release with 15, or 16, or anything >14.1.
Generally speaking you still depend on the device manufacturer to ship a compatible vendor partition in order to run a given version of LineageOS. This means that if your device doesn't have an official version of Android 8, then it will never be able to run LineageOS 15.
That is to say Duval based his product on whichever LineageOS release was 'current' at the time but plans to sync to the next available release when his next development cycle allows (which is Oreo, currently).
In other words, they're making the complete package and they plan to target average people.
It looks like a very slight variation of iOS. Not particularly original at all.
Will have a look at /e/ this weekend!
Life is compromise.
So really, its not just the OS/distribution/custom-tweaked-environment/game-engine. Its also the hardware.
Like, how can I get the hardware I need to try this out, without going through hoops?
To me that's a bit more of an issue than a broiled and flailed distro-dejour re-incarnate...
Also, no lineageos support at this point. not surprising, given its newness. But looks like one to keep an eye on!
Google says the OnePlus 3 doesn't have it either, is that wrong?
Samsung brought back SD to their flagship line with the S7/Note7 generation. The S6 / Note5 generation is the only one that didn't have SD, as I recall.
I mean, I woulnd't want to depend on one of these things unless the people behind them has shown a enough defiance against the buying power of money.
While it's awesome you're building a competing infrastructure, it's dead in the water (at least to me) if it doesn't integrate with what I have already.
“the chat application is Telegram”
Is this satire?
Discussion appears to be here: https://www.indidea.org/gael/blog/leaving-apple-and-google-e...
I appreciate the reason for the name change, but if the goal is to target laypeople, /e/ is not obviously pronounceable or meaningful for my mom or kids/teens.
> We understand that this textual representation is not ideal for talking about the project and searching about it.
> We have decided to hold off on change to the name for the beta release. Along with the v1 stable version, we will introduce a new name for the mobile system that will be easy to remember and to adopt.
So: They are aware and have a plan.
If you're not googleable, you're going to have a hard time
Now we're using common nouns as names for everything and it has completely broken the ability to search for both the product AND the common nouns.
I think /e/ cute and that plenty of brands have succeeded despite being unrecognizable and unsearchable.
The meaningful symbol seems related to AirBnb and their bélo , which I think was largely successful.
and the 2e was //
"Slashy McSlash Face"
On the contrary, it's a scientific notation for a specific pronunciation of the letter e.
/e/ represents in linguistics an unrounded closed-mid front vowel.
'Linux' was non obvious to the point that Linus issued his own voice recording. 'gif' vs 'jif' for the image format, etc.
It is not easy to say, remember, or look for.
This was dead before it even got off the ground, which is unfortunate because the OS looks nice.
OP is right - they should really fix their name to address all these issues:
(1) Search engine-ability. Zero people are going to be able to discover this.
(2) Unique domain name. e.com/io/whatever is already taken (so is eos.com).
(3) Not trademarked.
If you want to make a better Lineage, I think having built in default app stores like Apkpure, encrypted system proxies, isolating apps from each other in better ways... Aren't those more worthy privacy oriented things to work on?
Now this idea still needs a lot of work. But, IMO we need to get away from the app model onto some new paradigm. Present us with our information /data directly without having to open apps. Think android widgets on steroids. Windows phone actually had some of this, with letting you create tiles that where contacts or other info.