Develop Bugs

Phones with only open drivers

So I'm back to Android after a few years, and I read that the stock ROM is now the most stable choice on most phones due to closed source proprietary drivers being used.
This sucks. Stock sucks. Are there any phones that are all open source drivers, so one can flash ROMs without immediately sacrificing stability no matter how well the ROM is designed?

http://en.wikipedia.org/wiki/List_of_open-source_mobile_phones ?

Alexandre-P said:
http://en.wikipedia.org/wiki/List_of_open-source_mobile_phones ?
Click to expand...
Click to collapse
Thanks I didn't see you had responded. It says in that article that android devices aren't included because of heavy use of proprietary drivers and applications so I'm guessing that an android phone shipping with open source drivers doesn't actually exist?

An Android phone that can only rely on open-source drivers? not that I know of. From what I've quickly read, the main obstacles to a full open-source Android phone are the radio and the graphic drivers, which are not opensorced and only available as binary blobs.

Alexandre-P said:
An Android phone that can only rely on open-source drivers? not that I know of. From what I've quickly read, the main obstacles to a full open-source Android phone are the radio and the graphic drivers, which are not opensorced and only available as binary blobs.
Click to expand...
Click to collapse
Yeah that's all I've seen too, was hoping there was a manufacturer making one somewhere that I hadn't found

[ROM] [DEV] Archlinux Phone - GNU/Linux for Android devices project

Archlinux Phone for Sony Xperia S
Part of GNU/Linux for Android devices project
First of all, this project is not ready for end users but everything is provided to build an archlinux system for the Sony Xperia S. So you will be able to have a complete system with GPU hardware acceleration, support of vibrator, sensors, GPS, wifi etc (everything is not yet tested like bluetooth, nfc...). Graphical applications are already able to display (Qt/Kwin tested but GTK3/kwin should be ok too).
This project is not just for this device and is really open to support multiple devices and GNU/Linux distributions. So you can share this project everywhere (xda, distributions forum...) ! Contribution are welcome and can be discussed directly on this thread to share efforts.
Introduction
This is a project to create a convergence between the desktop and the mobile/phablet/TV... so to build new mobile OS based on existing GNU/Linux distributions with the most common parts possible. We share some common base between mer-hybris (SailfishOS) and Ubuntu Touch but the architecture and integration are different (refer to Architecture).
Cell phone are powerful and expensive for flag ship so why just use it as a phone ?
Imagine that your cell phone can become your core device ! Plug it to a big screen and this is your workstation ! Plug it to an 'empty' laptop (no CPU, no RAM needed ...) and this is your laptop ! Move everywhere and this is just your mobile phone !
This is what motivate this project.
Applications
Applications are critical on a mobile platform and we hope to support Android application as soon as possible (need further studies to complete the architecture).
GNU/Linux applications are already compatible but not always adapted for a mobile phone for now but... We hope a lot of plasma mobile and KDE convergence guideline for Application developers
Source code
There is few projects and some fork available under my github but if you want to start to port a new distribution or a new device, everything is documented in the gnulinux_support project.
Android needs to be modified but we deliver a solution that permit to be integrated upstream and so to compile Android or Android for GNU/Linux with the same code.
For now we have only Android 5.1.1 patches available but 6.0 will come soon. CyanogenMod 12.1 and 13.0 can be a good target to support a lot of devices in the future (or at least to simplify the portage process per device).
manifest for Sony Xperia S
manifest for Pure AOSP 5.1.1 (can be used for Nexus devices)
Documentations
Architecture schema
Main documentation
Archlinux installation
Videos
https://vimeo.com/177893595
Distributions supported
archlinux (archlinuxarm)
Project status
This project is in an early stage and for developers but we created solid base of works and the portage of plasma mobile, ofono, ... and amazing features will start over those solid base to provide an end user product
Todo :
pulseaudio support for GNU/Linux - Android Hw (and maybe for Android to support sound from Android application)
fix libinput/kwin environment
ofono (or maybe an alternative/hybrid solution that can use the Android Telephony Framework ? no study yet on this point)
flashing after boot.img package update + generation of a custom initramfs
security with crypto, firewall and SELinux (SELinux or equivalent integration will mainly depend of the distribution support but for now this is disabled)
plasma mobile or other ?
localisation framework (see freedesktop project)
OMX
merge everything possible to every upstream projects used to create GNU/Linux for Android devices
overlayfs into kernel ? (not mandatory but can be a great solution for the Android rootfs and schroot)
... (a lot that I forget)
BUT despite this long list of todo... We already did :
New architecture (GNU/Linux and Android integration, systemd, libhybris, chroot, wayland ...)
SurfaceFlinger Composer supported by Qt and Kwin
schroot for Android (Android can run into a chroot and we can interact easily with it)
systemd integration (with reboot to bootloader and recovery, Android /init support, etc)
libhybris_ext (compatibility version with support of Android 5+)
Android integration with GNULINUX_SUPPORT (rc, init, busybox, ramdisk, OTA ... adaptation)
clean rootfs with only 2 symlinks that permit to see that we are on an Android device (nothing more)
OpenGL support (with backend hwcomposer or SurfaceFlinger)
Archlinux support (OTA and packaging)
Design a possible solution for a lot of other GNU/Linux distributions (share architecture and Android adaptation)
Documentation
Download
Binaries will be available when really usable for end user. For now everything can be compiled from source code

Devices supported
Sony Xperia S (nozomi): work in progress (this is our reference device)

RESERVED

I will provide OTA file, binaries (archlinux packages), images and video to show what is working and how really soon

Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk

Demetris said:
Very interested in this,is HDMI out working?
Στάλθηκε από το 6045Y μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
Multi screen is not yet supported on kwin_wayland so for now I have just focused to render on the main screen (0) but it will be possible to do it for hdmi (1). But for sure I hope to support hdmi output.
For now I will focus to port plasma-mobile/ofono/pulseaudio.

Impatient to try another gift from genius mickybart.
Waiting............

wow something new
waiting eagerly...

lovely, cannot wait to try it
finally there is hope to ditch android, ios and windows

I have not a lot of time to work on this project with the release of nAOSP b11 but once done I will rework on it and provides binaries for Devs.
But, I think that this "new OS" powered with plasma is a good choice and I'm happy to see that plasma 5.7 integrate such kind of features :
https://www.kde.org/announcements/plasma-5.7.0.php
https://blog.martin-graesslin.com/blog/2016/05/virtual-keyboard-support-in-kwinwayland-5-7/
Great improvement have been done on Wayland support too.
If some of you are interesting to do some packaging with Archlinux, I'm really interested to get some help to provide a usable system for end user. The work for now is more too package/install user tools (so integration of components). I miss pulseaudio and ofono patching but I'm optimist to solve every issues.

finally nAOSP 6.0 b11 and b12 took me more time than expected but I'm back on this project.
For information, I updated everything to Qt 5.7.x support.
Some pull request have been done and are in discussion for at least qt5-qpa-hwcomposer-plugin (mer-hybris).
I decided to don't provide binaries for now as there is not a lot of sense to do it except if you are interesting to help the project (mainly to package some stuffs, integrate tools for GPS, ofono, pulseaudio etc).
I just finalized to record a small video. I will cut it and upload it to prove that archlinux arm phone can be a reality with the proposed new architecture (and on our Xperia S).
I will work again on the kwin/libinput issue. Maybe just a logind/dbus/kwin discussion issue. Once fixed that should permit to have a graphical keyboard by default (I know that for iOS or Android this is normal... but not really on a GNU/Linux desktop) !
I continue to look for help on this project and if you can create some packages like the one for plasma-mobile and derived repo let me know in PM or in the thread.

small video of the project
https://vimeo.com/177893595

Great achievement today
libinput is working and so I'm now able to move windows, plug a keyboard to write a text file, plug the mouse (pointer is not visible) ...
Menus are well displayed now with the good size.
Next steps : pulseaudio, wifi, plasma-mobile... (and bug fix on the kwin backend).

wow mickybart !. u just struck my interest in coming back to this phone! amazing work. my phone was unusable and parts needed replacement. looking at the activity of yours in this section made me repair the device and try out your work.. cheers mate! keep going with ur awesome work!

OnePlus X (onyx) port
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?

latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !

latgarf1 said:
I'd like to port this to OnePlus X (onyx). What's a preferable Android OS that I should use? The device comes with manufacturer's OxygenOS, which was made open source. OxygenOS was based on Android 5.1.1. I've also used Cyanogenmod 13 on this device. Out of these 3 options, I prefer CM. Any considerations I should keep in mind making this choice?
Click to expand...
Click to collapse
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
nik012003 said:
I have a Sony Xperia S and a OnePlus One and I'd like this port!
On my OnePlus One I'm using Ubuntu Touch that is very cool but apt-get doesn't work so I can't install other apps.
I really like this on my "old" Xperia S !
Click to expand...
Click to collapse
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.

mickybart said:
...
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future !
Let me know your advice and if you thing to base your work on CM 13.0...
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Click to expand...
Click to collapse
I've not tried arch but have attempted similar to this project with Debian (raspbian) on ancient hardware with partial success.
As free time rears its rare head I'll be trying to adapt your project for my newer HTC based on cm13.
By the way, your work on N ril from github is great, allows my cm14 to get/make calls without rebooting. Now if I can just figure out why rild takes forever to stop dying and respawing and start actually running...

mickybart said:
Hi @latgarf1,
Sorry for my late answer. I'm busy with Android 7.
That would be nice to have another device on this project to have a better view and maybe have a real alternative in the future .
I will ask a moderator if we can move this thread to a general one.
Advantage to use Android 5.1.1, is that every patches are available and tested to run Archlinux with android Hw support.
But as OxygenOS is not pure AOSP you will maybe need to cherry-pick those patches.
So it is preferable to maybe try to use CM-13 but everything need to be done on that side. I have now a device (Samsung S3) that is able to run CM-13.0 so I will be able to help in case of an issue to port the code to CM-13.0.
The big advantage to try to do it on CM-13.0 is that we can touch a lot of device in the future ! If CM is open, we will be able to push the patches upstream because those patches will not interfere with Android build as this is the case for Ubuntu Touch and mer-hybris patches.
I have not take a lot of time to continue this project since a while but I'm able to run desktop applications with windows management + opengl acceleration etc... I need to work on audio part (in progress), modules to integrates sensors (but sensors are already working). The last video posted do not show those progress.
Let me know your advice and if you thing to base your work on CM 13.0, I will probably switch the development to the Samsung S3 instead of Xperia S (but I will try to keep Xperia S in sync ).
I'm really interested to have some help to speed up this project and to have more motivation for it
You can take a look on the documentation and let me know if you need some help (that will permit me to improve the documentation too).
Here I really want to don't do any difference between a PC and a smartphone. So every tools used on a PC should work on the smartphone (update the kernel and manage initrd should be, at the end, possible to do in the same way than on the desktop ).
Do you know if you are using pulseaudio on Ubuntu Touch ? And do you know in which way it is done ?
For now I'm following mer-hybris and Sailfish to implement it by creating a droid module for pulseaudio.
Click to expand...
Click to collapse
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles

nik012003 said:
I don't know how the audio works but I know that it works.
This is the ubports repo https://github.com/ubports?tab=repositories
If you want me to type some commands on the ubuntu touch terminal let me know.
EDIT : I searched and I think that the Oneplus port is using pulseaudio but I don't know how does it work.
https://wiki.ubuntu.com/Touch/Core/PulseaudioProfiles
Click to expand...
Click to collapse
Thanks. I will give it a try but to have a more automatic process I will maybe follow what is done in mer-hybris :
https://github.com/mer-hybris/pulseaudio-modules-droid

[7.X] [Official] LineageOS for MicroG (ether)

I did not make this rom. I'm simply letting people know this exists. It's LineageOS with built-in microG. From their FAQ:
Why all of this? Isn't OpenGApps free software?
Yes and no, the name "OpenGApps" is misleading. While OpenGApps uses free software to retrieve and bundle the GApps, the apps themselves are not free software, they are in fact the same Google Apps you find on a new phone.
Why should I use microG instead of the standard Google Play Services?
First of all, freedom. I can't explain here why free software is so important (this is a FAQ, not a 200 pages manual), but if you're interested you can start by reading this.
Second, the Play Services are very expensive in terms of resources, they drain lots of battery and they use lots of space, while microG requires much less resources. To give you an idea, the smallest possible package of OpenGApps ("Pico Package") on ARM 7.1 is ~125 MB, while the full microG suite (GmsCore, GsfProxy, FakeStore, MozillaNlpBackend and NominatimNlpBackend) is ~4 MB.
Isn't Android free software? Can't I just install LineageOS without both GApps and microG?
Android is based on the AOSP project, which is free software. However many common features are handled by the proprietary GApps, generally by the Google Play Services. You can use LineageOS without GApps/microG, but you will probably miss something. In particular, you won't have the:
network localization services, which means that you can only use the GPS for the positioning
Google Cloud Messaging, so you won't receive any push notification for any app that relies on it
the Maps API, which means that any app that uses Google Maps through the Maps API will probably crash
With microG these services (and many others) are reimplemented.
Is LineageOS for microG completely free software?
Unfortunately no, like LineageOS it still has some non-free components. See the Replicant project for more informations.
Which is the current status of microG? Which APIs are already implemented?
See here.
Why do we need a custom build of LineageOS to have microG? Can't I install microG on the official LineageOS?
MicroG requires a patch called "signature spoofing", which allows the microG's apps to spoof themselves as Google Apps. LineageOS' developers refused (multiple times) to include the patch, forcing us to fork their project.
Wait, on their FAQ page I see that they don't want to include the patch for security reasons. Is this ROM unsafe?
No. LineageOS' developers decided not to include this patch for various reasons.
The signature spoofing could be an unsafe feature only if the user blindly gives any permission to any app, as this permission can't be obtained automatically by the apps.
Moreover, to further strengthen the security of our ROM, we modified the signature spoofing permission so that only system privileged apps can obtain it, and no security threat is posed to our users.
Do you use test keys?
Heck, no! We sign all our builds with our own private keys.
Do you offer OTA updates?
Yes, once a week.
Do you offer delta updates?
Not currently, but it can be done if there's real demand.
Can I install apps from the Play Store on this ROM?
F-Droid is included in our ROM, so you can freely download all the FOSS apps on their repositories.
However, if you need apps which are available only on the Play Store, you're free to host your personal instance of PlayMaker (see this demo) or GPlayWeb and connect it to your F-Droid client, Playmaker will let you download apps from the Play Store and install them via F-Droid. Another solution is to use a local app, like Yalp Store.
Do I have to enable "Unknown sources" to install apps in F-Droid?
Our ROM includes "F-Droid Privileged Extension", which allows F-Droid to install and update apps without the need of user interaction or the unsafe "Unknown sources" option.
Can you add support for my device? It is officially supported by LineageOS
We already build LineageOS for microG for every device supported by LineageOS. Find your device in our Downloads page!
Can you add support for my device? It is not supported by LineageOS though...
No, I'm sorry.
I don't trust your build, I want to build it myself!
No problem! Our builds are done with this Docker image, feel free to build it yourself.
I am running a custom build of LineageOS, but yours is way cooler! How can I migrate to it without losing my data?
Replace the LineageOS official keys in our migration ZIP with your keys (or follow the suggestions in the LineageOS migration guide).
Click to expand...
Click to collapse
More information: https://lineage.microg.org
Download Links: https://download.lineage.microg.org/ether/
XDA:DevDB Information
LineageOS for MicroG, ROM for the Nextbit Robin
Contributors
EAT_CHICKEN
Source Code: https://github.com/lineageos4microg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2018-03-30
Last Updated 2018-03-29

ROM ❯ PIXEL 3a ❯ UNOFFICIAL ❯ ProtonAOSP 11

ProtonAOSP • Pixel 3a
Android 11 ROM​
ProtonAOSP is a minimal custom Android 11 ROM focused on UI/UX and performance, with a touch of privacy.
Instead of customization it is focused on more smoother experience.
Installation
1. Unlock Bootloader
2. fastboot flash boot boot.img
3. Reboot to factory and factory reset
4. adb sideload rom.zip
5. Reboot​Note:- Rom already comes with gapps included so no need to flash them
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Download Here​Known issues
No eSIM support(I plan to add in next build)
Join the Telegram group for support
Kernel source code
ROM source code
This is just a side project, I may or may not maintain it in future.
A huge thanks to @kdrag0n for the amazing rom and the work done on this rom.

Reserved

I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.

96carboard said:
I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.
Click to expand...
Click to collapse
1. Soon I'll push source
2. I do have microg build for sargo as it is my main device, but not for bonito, so I did not post here on xda, if you want it join the support link group in the thread. Regarding google crap, for some users flashing gapps externally had less fluid experience so I did it.

I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?

96carboard said:
I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?
Click to expand...
Click to collapse
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.

FoxA said:
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.
Click to expand...
Click to collapse
Thank you very much. I'll give that a go

Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
sorry, I don't have the device anymore.

The link download is not working, please update it

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
Here's a current source.
I don't know if it's trusted, or who the maintainer of this unofficial build is though. Just found it via telegram.
ProtonAOSP - Browse /ProtonAOSP at SourceForge.net
sourceforge.net

Nice one. It's really handy to be able to revive old, unsupported devices like the Pixel 3a, which is a perfectly usable phone and can be picked up for next to nothing.
Some of us don't care about de-googling our phones and really just want to extend their lifespan with security updates, so having gapps baked in to ProtonOASP is really nice. Especially when we're just trying to help out our non-technical friends get a bit more life out of their old phones. A consistent, familiar user experience is all they really want.
I was wondering though: Does your build (or any build of ProtonOASP) come with verified-boot signatures so that the device's bootloader can be locked down after the ROM is installed, or is CalyxOS the only option for this?
Unfortunately, Calyx are very puritanical when it comes to de-googling, and microG is just a terrible substitute for interacting with Google services. I tried it on the Pixel 3a, and it doesn't even sync the contact list from your Google account. My non-technical friend was not impressed.

GrapheneOS still has builds up for 3a, however new builds were terminated as of February. While it doesn't ship with gCrap preinstalled, installation is trivial as they've built a compatibility layer to make it work correctly (and much MUCH more securely) as user-installed software, which you can install from the program "Apps".

Question Privacy Custom Rom for Poco F3?

Is there anything besides LineageOS?

Kasygertu said:
Is there anything besides LineageOS?
Click to expand...
Click to collapse
https://downloads.blissroms.org/download/alioth/

Is AOSP without GApps privacy-friendly? If yes, then you could just get one of those AOSP ROMs, which offer a version without GApps.
But AOSP might not be privacy-friendly, I'm not sure. ^^ It's developed by Google after all.

cyanGalaxy said:
Is AOSP without GApps privacy-friendly? If yes, then you could just get one of those AOSP ROMs, which offer a version without GApps.
But AOSP might not be privacy-friendly, I'm not sure. ^^ It's developed by Google after all.
Click to expand...
Click to collapse
Android=GOOGLE
2 versions with or without gapps(vanilla).
That's all.

NOSS8 said:
Android=GOOGLE
2 versions with or without gapps(vanilla).
That's all.
Click to expand...
Click to collapse
Yeah I know, but is Vanilla Android still privacy-preserving, or does it send Telemetry too?
Cuz that would exclude most ROMs out of the equation for privacy.

cyanGalaxy said:
Yeah I know, but is Vanilla Android still privacy-preserving, or does it send Telemetry too?
Cuz that would exclude most ROMs out of the equation for privacy.
Click to expand...
Click to collapse
No idea because I don't care. (I don't have this device).

NOSS8 said:
No idea because I don't care. (I don't have this device).
Click to expand...
Click to collapse
Vanilla Android (the base) does not vary from device to device, the included device-specific drivers and other minor adjustments differ.

AOSP doesn’t come with Google’s suite of software applications which u might consider one of the biggest privacy issues on android devices, but unlike Apple u can install vanilla build which does not contain any data mining tools, as far as i know there is no telemetry in AOSP, i personally prefer caf which is more optimized repo for snapdragon devices, at the end of the day if u want total privacy stick with vanilla build (crdroid, BlissRom, SyberiaOS...) plus F-droid store or one of it's forks like Aurora droid app you will find plenty of useful open source apps provided by people like u and me and will not collect any data from ur device, if u still want to use apps from playstore you can flash MicroG: MinMicroG-NoGoolag-2.11.1-20220202153503.zip ( fyi u still have to update aurora apps from their website for them to work properly since this repo hasn't been updated since February ) auroraoss.com it will allow u to download apps from play Store anonymously but it does not guarantee ur privacy, if u are using accounts linked to you personally those apps will send private data no matter what and your device will be identified.

venomus001 said:
AOSP doesn’t come with Google’s suite of software applications which u might consider one of the biggest privacy issues on android devices, but unlike Apple u can install vanilla build which does not contain any data mining tools, as far as i know there is no telemetry in AOSP, i personally prefer caf which is more optimized repo for snapdragon devices, at the end of the day if u want total privacy stick with vanilla build (crdroid, BlissRom, SyberiaOS...) plus F-droid store or one of it's forks like Aurora droid app you will find plenty of useful open source apps provided by people like u and me and will not collect any data from ur device, if u still want to use apps from playstore you can flash MicroG: MinMicroG-NoGoolag-2.11.1-20220202153503.zip ( fyi u still have to update aurora apps from their website for them to work properly since this repo hasn't been updated since February ) auroraoss.com it will allow u to download apps from play Store anonymously but it does not guarantee ur privacy, if u are using accounts linked to you personally those apps will send private data no matter what and your device will be identified.
Click to expand...
Click to collapse
What ROM are you rocking at the moment? Any ROMs you generally recommend? Complete forks from CAF, or AOSP ROMs with CAF optimisations? Thinking of ArrowOS or LineageOS + GApps.. Don't need Pixel-features, just GApps ^^

cyanGalaxy said:
What ROM are you rocking at the moment? Any ROMs you generally recommend? Complete forks from CAF, or AOSP ROMs with CAF optimisations? Thinking of ArrowOS or LineageOS + GApps.. Don't need Pixel-features, just GApps ^^
Click to expand...
Click to collapse
currently using crdroid v8.7 and microg

May already be on XDA but just in case:
https://sourceforge.net/projects/cherish-os/files/device/alioth/

Never tried this
Info about Xiaomi POCO F3 / Redmi K40 / Mi 11X - alioth
/e/

extrem0 said:
Never tried this
Info about Xiaomi POCO F3 / Redmi K40 / Mi 11X - alioth
/e/
Click to expand...
Click to collapse
Have already heard about this rom. Its privacy oriented?

really nice topic the privacy stuff really becomes more and more important in the same manner like using Google apps. I tried many roms lineage / aicp / crdroid and now I am good with corvus. but the best you can do is install a pihole with anti telemetry lists on it and tunnel your devices with wireguard or OpenVPN over your own network than you even can run stock rom