Earlier quoted context omitted.
The rumors are they're still doing one last ditch, Surface Phone due to the growing Surface ecosystem that is making them money and people liking it so far. However, they're not going to release that until they finish the CShell that they're working on the past several years.
Is Surface making money or just stemming the bleeding?
Leaving Apple and Google: /e/ first beta
51–60 of 129 posts
Re: Leaving Apple and Google: /e/ first beta
#52I don't understand what this Android fork has to do with Apple.
Re: Leaving Apple and Google: /e/ first beta
#53I just want a high end phone that supports something like lineageos, has a micro SD slot, and decent battery life. Somehow it's hard to find.
Re: Leaving Apple and Google: /e/ first beta
#54I just want a high end phone that supports something like lineageos, has a micro SD slot, and decent battery life. Somehow it's hard to find.
Then go with Oneplus. 2 years and 2 months and my oneplus 3 with dual sim or 1 sim/ 1 sd card is still working perfectly fine and receiving updates, getting Android P before 2019 (in theory)
Google says the OnePlus 3 doesn't have it either, is that wrong?
Re: Leaving Apple and Google: /e/ first beta
#55Re: Leaving Apple and Google: /e/ first beta
#56Re: Leaving Apple and Google: /e/ first beta
#57So 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...
Re: Leaving Apple and Google: /e/ first beta
#58Earlier quoted context omitted.
and without the slashes one of many names of a particularly popular party drug
To be fair, people call drugs by myriads of names. Context usually helps to disambiguate between LSD and MySQL.
Re: Leaving Apple and Google: /e/ first beta
#59But 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
Re: Leaving Apple and Google: /e/ first beta
#60I just want a high end phone that supports something like lineageos, has a micro SD slot, and decent battery life. Somehow it's hard to find.