Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
porting-notes
A repo to keep in-progress device ports information and information useful to porters that is not in official docs yet
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
One problem with relying on emulation is that Google has moved a lot of functionality from the open source Android layer to Google Play Services, and they obviously wont publish that on someone else's platform.
https://developers.google.com/android/guides/overview
I switched from rooted Android to an iPhone that has the checkm8 bootrom exploit and use a tool called checkra1n[0] to 'jailbreak' it. It's been really nice, super stable (i.e. months between restarts) and unlocks so many little comforts for me coming from custom Android. To an android user, it's similar to Xposed, but with almost every change to the system going through Xposed instead of modules, random scripts, etc.
[0] https://checkra.in
> what is the remaining work I would need to have done in order to get it working under
A good chunk of the Linux community on phones didn't want to have to rely on binary drivers for non-technical reasons, and that's one of the reasons why it isn't exactly well taken care of today.
For Ubuntu Touch specifically:
https://docs.ubports.com/en/latest/porting/introduction/Intr... for Ubuntu Touch.
https://github.com/ubports/porting-notes/wiki/Generic-System...
An upgraded Halium (https://github.com/Halium) image on a can work unmodified across the whole ecosystem of Android devices.
However, the latest currently developed experimental Halium works on an Android 11 base at most, so that devices launched with Android 12 might be using drivers too new for it at this point in time.
(https://gitlab.com/ubports/community-ports/jenkins-ci/generi...)
This can be fixed with an engineering effort to do so to make it work on devices launched with Android 12. The Linux on phones community is very small and that causes problems in this case. Together with the unified kernel image (GKIs) on Android 12, a full experience can be made possible.
I wonder how big the audience would be for such a project though. :)
> what is the remaining work I would need to have done in order to get it working under
A good chunk of the Linux community on phones didn't want to have to rely on binary drivers for non-technical reasons, and that's one of the reasons why it isn't exactly well taken care of today.
For Ubuntu Touch specifically:
https://docs.ubports.com/en/latest/porting/introduction/Intr... for Ubuntu Touch.
https://github.com/ubports/porting-notes/wiki/Generic-System...
An upgraded Halium (https://github.com/Halium) image on a can work unmodified across the whole ecosystem of Android devices.
However, the latest currently developed experimental Halium works on an Android 11 base at most, so that devices launched with Android 12 might be using drivers too new for it at this point in time.
(https://gitlab.com/ubports/community-ports/jenkins-ci/generi...)
This can be fixed with an engineering effort to do so to make it work on devices launched with Android 12. The Linux on phones community is very small and that causes problems in this case. Together with the unified kernel image (GKIs) on Android 12, a full experience can be made possible.
I wonder how big the audience would be for such a project though. :)