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
Related
Hi,
I search for a solution since end of december, I searched xda, duckduckgo and others known search engines.
I can't figure the way to have LineagsOS 16 alpha and MicroG (Pie based version) because of the need of 'signature spoofing'.
I can't use Uber or any application using gApps Play Store and don't want to install gApps nor Play.
Posted this https://github.com/anestisb/vdexExtractor/issues/47#issuecomment-455893286 the guys said to search, but I need help because I'm not finding relevant solutions.
I do have *dex files, but dunno how to repack/sign in the hope I have the good deodexed files :
Code:
system_new/framework/arm64/vdexExtractor_deodexed/boot-framework/boot-framework_classes3.dex
system_new/framework/arm64/vdexExtractor_deodexed/boot-framework/boot-framework_classes2.dex
system_new/framework/arm64/vdexExtractor_deodexed/boot-framework/boot-framework_classes.dex
system_new/framework/vdexExtractor_deodexed/boot-framework/boot-framework_classes3.dex
system_new/framework/vdexExtractor_deodexed/boot-framework/boot-framework_classes2.dex
system_new/framework/vdexExtractor_deodexed/boot-framework/boot-framework_classes.dex
system_new/framework/oat/arm64/vdexExtractor_deodexed/services/services_classes.dex
system_new/framework/arm/vdexExtractor_deodexed/boot-framework/boot-framework_classes3.dex
system_new/framework/arm/vdexExtractor_deodexed/boot-framework/boot-framework_classes2.dex
system_new/framework/arm/vdexExtractor_deodexed/boot-framework/boot-framework_classes.dex
I don't really care to stay on LineageOS if I can't use MicroG, but I prefer to stay if possible on LOS.
Any pointers please ?
I'm considering many other options, like buying a new device if necessary, but don't know what the best device in middle prices with a size close too 146 x 71.4. and a LineageOS + microG support
As the title says: I'm looking for a ROM (preferably security / privacy focused) that ships with MicroG out of the box. Is there anyone planning to make such ROM for alioth?
What are your objectives.
I have bitten the microG fruit. It really depends on what you are trying to do. If you want a balance of Google and privacy and you are ready to let go of Gmail then it's possible but if you want Gmail then I suggest sticking to Gapps.
PM me for the telegram channel or search minmicroG.
My fav is following the offcial MicroG instruction
Personally I would recommend using a vanilla build for a ROM and then flashing some form of GAPPs:
https://t.me/s/WeebGAppsChannel (this one might be decent. However you can look around)
WM-Sef said:
As the title says: I'm looking for a ROM (preferably security / privacy focused) that ships with MicroG out of the box. Is there anyone planning to make such ROM for alioth?
Click to expand...
Click to collapse
As LineageOS is now official for our device, you can download LineageOS with MicroG from following url-
https://download.lineage.microg.org/ very soon. All LineageOS official devices have builds on it.
Magisk Patched Unofficial GrapheneOS for the Pixel 6 / 6 Pro (oriole/raven)
This ROM will allow you to lock the boot loader. Do not ever disable the OEM unlocking checkbox when using a locked bootloader with root.
This is critically important. With root access, it is possible to corrupt the running system, for example by zeroing out the boot partition.
In this scenario, if the checkbox is turned off, both the OS and recovery mode will be made unbootable and fastboot flashing unlock will not be allowed.
This effectively renders the device hard bricked.
I am not responsible for any harm you may do to your device, follow at your own risk etc etc, Rooting your device can potentially introduce security flaws, I am not claiming this to be secure. If you would like to have more security and peace of mind then I highly recommend you follow This Guide to build this rom using your own encryption keys.
GrapheneOS is a privacy and security focused mobile OS with Android app compatibility developed as a non-profit open source project. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. It was founded in 2014 and was formerly known as CopperheadOS.
The features page provides an overview of the substantial privacy and security improvements added by GrapheneOS to the Android Open Source Project (AOSP). Many of the past features were contributed to AOSP, Linux and other projects to improve privacy and security for billions of users so they're no longer listed on the features page.
More info:
Official releases are available on the releases page (Not Magisk Patched) and installation instructions are on the install page.
GrapheneOS also develops various apps and services with a focus on privacy and security. Vanadium is a hardened variant of the Chromium browser and WebView specifically built for GrapheneOS. GrapheneOS also includes our minimal security-focused PDF Viewer, our hardware-based Auditor app / attestation service providing local and remote verification of devices, our modern privacy / security focused camera app, and the externally developed Seedvault encrypted backup which was initially developed for inclusion in GrapheneOS.
No Google apps or servicesGrapheneOS will never include either Google Play services or another implementation of Google services like microG. It's possible to install Play services as a set of fully sandboxed apps without special privileges via our sandboxed Google Play compatibility layer. See the FAQ section for more details on our plans for filling in the gaps from not shipping Play services and Google apps.
Installation Instructions: Fashing-factory-image
Locking the bootloader is Optional but does increase the device security Locking-the-bootloader
Update Instructions: simply follow these instructions Updates-sideloading to sideload the latest patched OTA update package (You can update from any previous version if using full ota update)
Android OS Version: 13
Current Version: See Post #2
Download: See Post #2
Sources: GrapheneOS - AVBRoot - Magisk - Patch Guide
PayPal Donation Link
Builds for Pixel 6 Pro (Raven)
Magisk-Patched GrapheneOS Factory Install Build
Full system install builds for clean and new installs
Build based on release#2023061402 (2023-06-14)
SourceForge_Download
Build based on release#2023050100 (2023-05-01)
SourceForge_Download
Build based on release#2023041100 (2023-04-11)
SourceForge_Download
Build based on release#2023032000 (2023-03-20)
SourceForge_Download
Build based on release#2023022300 (2023-02-23)
SourceForge_Download
Build based on release#2023020600 (2023-02-06)
SourceForge_Download
Build based on release#2023020200 (2023-02-02)
SourceForge_Download
Build based on release#2023012500 (2023-01-25)
SourceForge_Download
Build based on release#2023011000 (2023-01-10)
SourceForge_Download
Build based on release#2023010300 (2023-01-03)
Anonfiles Download | 1fichier Download | SourceForge_Download
Build based on release#2022122000 (2022-12-20)
Anonfiles Download | 1fichier Download
Build based on release#2022121400 (2022-12-14)
Anonfiles Download | 1fichier Download
Build based on release#2022121100 (2022-12-11)
Anonfiles Download | 1fichier Download
Build based on release#2022120300 (2022-12-03)
Anonfiles Download | 1fichier Download
Build based on release#2022113000 (2022-11-30)
Anonfiles Download
Build based on release#2022112500 (2022-11-25)
Anonfiles Download
Build based on release#2022111800 (2022-11-18)
Anonfiles Download
Build based on release#2022111000 (2022-11-10)
Anonfiles Download
Build based on release#2022101800 (2022-10-18)
Anonfiles Download
Click to expand...
Click to collapse
Magisk Patched OTA Update packages
Full OTA Builds will let you update from any older version
Patched OTA based on release#2023061402 (2023-06-14)
SourceForge_Download
Patched OTA based on release#2023050100 (2023-05-01)
SourceForge_Download
Patched OTA based on release#2023041100 (2023-04-11)
SourceForge_Download
Patched OTA based on release#2023032000 (2023-03-20)
SourceForge_Download
Patched OTA based on release#2023022300 (2023-02-23)
SourceForge_Download
Patched OTA based on release#2023020600 (2023-02-06)
SourceForge_Download
Patched OTA based on release#2023020200 (2023-02-02)
SourceForge_Download
Patched OTA based on release#2023012500 (2023-01-25)
SourceForge_Download
Patched OTA based on release#2023011000 (2023-01-10)
SourceForge_Download
Patched OTA based on release#2023010300 (2023-01-03)
Anonfiles Download | 1fichier_Download | SourceForge_Download
Patched OTA based on release#2022122000 (2022-12-20)
Anonfiles Download | 1fichier_Download
Patched OTA based on release#2022121400 (2022-12-14)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022121100 (2022-12-11)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022120300 (2022-12-03)
Anonfiles Download | 1fichier Download
Patched OTA based on release#2022113000 (2022-11-30)
Anonfiles Download
Patched OTA based on release#2022112500 (2022-11-25)
Anonfiles Download
Patched OTA based on release#2022111800 (2022-11-18)
Anonfiles Download
Patched OTA based on release#2022111000 (2022-11-10)
Anonfiles Download
Patched OTA based on release#2022110800 (2022-11-08)
Anonfiles Download
Click to expand...
Click to collapse
Builds for Pixel 6 (oriole)
Always do a backup of your data before flashing any updates, just in case.
I make no promises that this works or that I will provide regular updates. I will attempt to provide updates when they are available and I have time, you may have issues with this rom, you could lose your data or brick your device (although it's very unlikely if you follow the instructions and use common sense)
#Reserved
Isn't there already an official build for graphene for Raven?
iBe.Jacob said:
Isn't there already an official build for graphene for Raven?
Click to expand...
Click to collapse
Yes. But not for a rooted version of it.
New Release 2022111800
Changes since the 2022111000 release:
don't skip ahead-of-time (AOT) compilation of apps that weren't recently used since we depend on full AOT compilation being done for performance rather than JIT compilation with background JIT profile guided AOT compilation like Android
battery usage UI: use fallback name for unknown components
change minimal value of battery saver schedule to 5% again as it was before Android 13
enable the post-upgrade "Optimizing apps" progress indication UI
app crash UI: show process uptime and optional extra text
Sandboxed Google Play compatibility layer: show version of GmsCompatConfig in the crash UI
Sandboxed Google Play compatibility layer: stop splitting multi-package PackageInstaller sessions
Sandboxed Google Play compatibility layer: improve handling of activity starts
Sandboxed Google Play compatibility layer: bugfix: Parcel position wasn't reset by dynamic stubs
Sandboxed Google Play compatibility layer: bugfix: missing handling of ListSlices in dynamic stub
GmsCompatConfig: make sure Play Store PhenotypeFlags are overridable by Gservices flags (further deterring Play Store trying to update Play services / Play Store beyond supported versions)
Pixel 7, Pixel 7 Pro (adevtool): drop unused face unlock components since we have no plans to enable support for an insecure face unlock implementation incapable providing reasonable security due to lack of dedicated face unlock hardware (Pixel 4 and Pixel 4 XL had dual infrared cameras, IR dot projector and IR flood illuminator providing a more secure biometric unlock system than fingerprint unlock as opposed to simply using the front camera in a way that could be done on any device)
Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 7, Pixel 7 Pro: include gril library to avoid qns crash on Pixel 7 and Pixel 7 Pro
Pixel 7, Pixel 7 Pro: include vendor_kernel_boot partition requirement in factory images metadata to force an error with an incompatible fastboot such as the currently buggy Arch Linux package
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro): update GKI to Linux 5.10.150
Auditor: update to version 66
Click to expand...
Click to collapse
Download in Post #2
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
96carboard said:
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
Click to expand...
Click to collapse
Sorry but I am not interested in arguing about this stuff
I didn't create this thread to argue about potential security issues or how secure phones really are
it seems you have more of an issue with the security of Android in general
I would recommend everyone who just wants to share opinions like this which are essentially unrelated to the ROM, please just don't
I am not claiming rooting your phone to be perfectly secure and I am not interested in arguing about it
Although as explained here https://forum.xda-developers.com/t/...pdated-november-9-2022.4343431/#post-85733797
there are advantages to using a locked bootloader, even with root.
optimumpro said:
The rom could be used on locked bootloader with ROOT (donate feature) with or without Gapps.
The benefits of LOCKED BOOTLOADER combined with WORKING AVB-2 protection are:
Get back your DRM L1 certificate. Most banking apps will work regardless of Magisk.
Security: Nobody and nothing can modify Kernel, Recovery and Virtual Partitions without triggering a red screen of death with the message 'your device is corrupted and cannot boot'.
At that point, the only option is to unlock bootloader. But, if a user had previously disabled OEM unlock in Developer settings, then unlocking becomes unavailable, and so does flashing via fastboot. In other words, if your phone gets into the hands of an adversary, their only option is to use MSM tool to make the phone work again, but no access to your data or any other partition.
Why prebuilt Magisk? Because you can't modify kernel or recovery on locked bootloader post installation, and that's exactly what Magisk does.
Click to expand...
Click to collapse
I am offering this as a free feature, not a donate feature and I have also created a guide so that anyone is able to build the rom and sign it using their own keys for even greater security than trusting me.
Magisk isn't just some unknown third party, Graphene, Magisk, AVBRoot, they are all open source projects
FireRattus said:
Sorry but I am not interested in arguing about this stuff
I didn't create this thread to argue about potential security issues or how secure phones really are
it seems you have more of an issue with the security of Android in general
I would recommend everyone who just wants to share opinions like this which are essentially unrelated to the ROM, please just don't
I am not claiming rooting your phone to be perfectly secure and I am not interested in arguing about it
Click to expand...
Click to collapse
I'm not talking about the utility or security of root (hint: Its perfectly safe and secure when used RESPONSIBLY). I'm talking about the value of using a security hardened OS with modifications made by someone who you don't know and can't trust. Doing so throws away ALL security because there is no way to tell what else someone has changed.
96carboard said:
I'm not talking about the utility or security of root (hint: Its perfectly safe and secure when used RESPONSIBLY). I'm talking about the value of using a security hardened OS with modifications made by someone who you don't know and can't trust. Doing so throws away ALL security because there is no way to tell what else someone has changed.
Click to expand...
Click to collapse
So just follow the guide I provided so you can build the rom yourself, you can inspect all the source code and work out exactly what it's all doing if you are so inclined
https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
FireRattus said:
So just follow the guide I provided so you can build the rom yourself, you can inspect all the source code and work out exactly what it's all doing if you are so inclined
https://forum.xda-developers.com/t/...-using-rooted-grapheneos-magisk-root.4510295/
Click to expand...
Click to collapse
Yes exactly!
@FireRattus is there any chance we can see pre-build images for Oriole in the future? I'm having trouble building it myself.
KainoaK said:
@FireRattus is there any chance we can see pre-build images for Oriole in the future? I'm having trouble building it myself.
Click to expand...
Click to collapse
What are the troubles you are having with building it yourself? I can try my best to help
I would be able to build images for Oriole probably but I wouldn't be able to test them myself and building for more variants would take more time making updates slower so I don't want to invest in that currently.
I do think it's best to build it yourself if you are able so I am glad you have tried already
> What are the troubles you are having with building it yourself? I can try my best to help
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
KainoaK said:
> What are the troubles you are having with building it yourself? I can try my best to help
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
Click to expand...
Click to collapse
I will try to build it for you, since the pixel 6 and 6 pro share the same Build ID, I should be able to build it without needing to download everything again
New Release #2022112500
Changes since the 2022111800 release:
Sandboxed Google Play compatibility layer: fix missing handling of APEX ListSlices in dynamic stubs (improves compatibility when granting Nearby devices permission to Play services with a WearOS device connected)
Sandboxed Google Play compatibility layer: mark PackageInstallerStatusForwarder as not exported
Settings: avoid OBB toggle unnecessarily force stopping app
extend original-package renaming to static launcher shortcuts to fix Vanadium new tab shortcut for users with an install predating the package rename
Camera: update to version 57
Vanadium: update Chromium base to 107.0.5304.141
Contacts: add support for dark mode
kernel (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro): restore fix for CVE-2022-3176 which was reverted upstream (GKI LTS branch) due to not being marked as a security fix and changing the GKI ABI
Pixel 4, Pixel 4 XL: set frozen patch level string to 2022-11-01 (has been provided since the 2022110800 release but we initially left the patch level string at the previous value)
port GrapheneOS changes to Linux 5.15 GKI LTS branch in order to prepare for 6th/7th generation Pixels potentially moving to the Linux 5.15 LTS and late 2023 devices which will be based on it
Click to expand...
Click to collapse
Download in Post #2
KainoaK said:
My computer just doesn't have enough RAM + Disk space to build it, plus I seem to keep getting stuck at getting all the tools to work together
I'd be happy to donate monthly or whatnot to help keep up oriole builds though
Click to expand...
Click to collapse
I am not able to test them myself but I have provided a patched, signed build which should work
just check post #3 for the download links, I would appreciate a donation if you feel it's worth it but no pressure
Edit: Moved it to post #2 with the other downloads
96carboard said:
I don't see a real value in locking the bootloader. In theory, the only thing it protects is undetectable modification being made when the device is out of your direct control. However, strong security practices require you to assume that *anything* could have been done to the device when it is outside of your direct control, so the "security" you get from the locked bootloader is artificial.
ANY time a device leaves your physical control, you have to assume it to be compromised. No exceptions.
I would also like to point out that, no offense to OP, but using a "high security" operating system that *HAS* been modified by an unknown 3rd party.... is insane. I'd recommend that anyone interested in this actually take the time to understand the process and reproduce it on their own.
Click to expand...
Click to collapse
To be fair you'll always be using something done by a third party, including android itself, unless it's you writing and compiling your own OS.
MidnightDevil said:
To be fair you'll always be using something done by a third party, including android itself, unless it's you writing and compiling your own OS.
Click to expand...
Click to collapse
Android is open source. Open source code is auditable. Compiled binaries are NOT.
So i managed to get a virtual android machine running via virtualbox, i used android project x86 for that.
However it contains the typical google-mass-surveillance-spyware, a no go.
How would i get a generic system image (gsi lineage) running in virtualbox?
What more do i need other than the GSI and VirtualBox?
Privacydroid said:
So i managed to get a virtual android machine running via virtualbox, i used android project x86 for that.
However it contains the typical google-mass-surveillance-spyware, a no go.
How would i get a generic system image (gsi lineage) running in virtualbox?
What more do i need other than the GSI and VirtualBox?
Click to expand...
Click to collapse
A kernel. GSIs are system only images, so they don't include kernels.
Privacydroid said:
So i managed to get a virtual android machine running via virtualbox, i used android project x86 for that.
However it contains the typical google-mass-surveillance-spyware, a no go.
How would i get a generic system image (gsi lineage) running in virtualbox?
What more do i need other than the GSI and VirtualBox?
Click to expand...
Click to collapse
As far as i know, LineageOS doesn't provide Android x86 image. You can use BlissOS instead, they actively develop Android for PC
khusika said:
As far as i know, LineageOS doesn't provide Android x86 image. You can use BlissOS instead, they actively develop Android for PC
Click to expand...
Click to collapse
Thanks! Never heared of bliss. This forum is really great, learning about so many new things here.
May i ask some noobish questions.. bliss has multiple download variations.
GApps (thats google apps...)
FOSS
AOSP
I'f been reading aosp quiet a few times, but foss is enitrely new to me.
Is there a documentation on what they stand for and what the differences are?
If possible i preffer a virtual android device without any trace of google/facebook.
I went for AOSP (not sure what foss is still).
In virtualbox would i choose other linux 64bit or other 64bit ?
Privacydroid said:
Thanks! Never heared of bliss. This forum is really great, learning about so many new things here.
May i ask some noobish questions.. bliss has multiple download variations.
GApps (thats google apps...)
FOSS
AOSP
I'f been reading aosp quiet a few times, but foss is enitrely new to me.
Is there a documentation on what they stand for and what the differences are?
If possible i preffer a virtual android device without any trace of google/facebook.
Click to expand...
Click to collapse
FOSS is Free and Open Source software. FOSS build doesn't include Google Play Service in it. Most of users using it for privacy concerns. They only replace Google things with F-Droid. Based on their website they are using Aurora Droid for open-source apps from F-Droid repos, and Aurora Store for accessing the Google Play library of apps
khusika said:
FOSS is Free and Open Source software. FOSS build doesn't include Google Play Service in it. Most of users using it for privacy concerns. They only replace Google things with F-Droid. Based on their website they are using Aurora Droid for open-source apps from F-Droid repos, and Aurora Store for accessing the Google Play library of apps
Click to expand...
Click to collapse
Interesting, privacy is also my nr 1 priority.
AOSP must stand for android open source project, blissos aosp seems to not use any gapps.
What really are the differences from aosp and foss if neither uses google?
Hey Guys,
Hope you're doing great
For the people who wanted privacy based roms like CalyxOS or GrapheneOS
you have to
1. install vanilla version from ArrowOS or LineageOS
2. Flash Magisk
3. Then in Magisk go to Modules tab, click top button 'Install from storage' install LSPosed-(...)-zygisk-release.zip (has to be zygisk version)
4. then install FakeGapps.apk like an regular app
5. Reboot
6. Popup will came out that ask you to add shortcut icon to desktop for LSPosed, just add it and open it
7. Go to Modules and enable FakeGApps
8. Go to Magisk and install microG_Installer_Revived.zip as a Module
9. Reboot
10. Open microG Service Core and ensure all boxes are selected. The most important is signature spoofing - this is what LSPosed and FakeGapps is for.
For working push notifications go to microG Service Core app and enable Google devices registration and Cloud Messaging.
For working location at least two apps will be needed - MozillaNlpBackend and NominatimNlpBackend. After installing they need to be enabled in microG Service Core app (Location modules). Sometimes MozillaNlpBackend refuse to be enabled, then you just have to go to it's permissions and select "Allow all the time" for location permission.
For working SafetyNet additional Magisk module may be needed.
SMS and Location in background didn't work for me, reinstalled the microG installer module and it worked
Few Alternative apps that you can use:
* Aurora Store, fdroid for app downloads
* Briar for messaging
* Orbot for enhancing security
* Bromite, Tor Browser for secured browsing
How to unlock bootloader for Redmi K40s
try looking into this video also if you have created an new mi account you may have to wait for 1week for getting your bootloader unlocked using miunlocktool you can also download the tool from https://en.miui.com/unlock/download_en.html
Also sorry everyone I forgot the metion the alternative apps that you could have used,
* Aurora Store, fdroid for app downloads
* Briar for messaging
* Orbot for enhancing security
* Bromite, Tor Browser for secured browsing
SparkOS also has a vanilla version, with a lot more UI customisation options compared to ArrowOS.
However, Spark got signature spoofing built in so you'd only need Magisk or similar for CTS profile / safety net.
If you don't need that, just take Spark vanilla and install microG / F-Droid / Aurora...
UniNick said:
SparkOS also has a vanilla version, with a lot more UI customisation options compared to ArrowOS.
However, Spark got signature spoofing built in so you'd only need Magisk or similar for CTS profile / safety net.
If you don't need that, just take Spark vanilla and install microG / F-Droid / Aurora...
Click to expand...
Click to collapse
Thx a lot for mentioning, note: nevest version of spark is an erofs build so for the who didn't wanted erofs version can download previous versions of it
You can use this guide in every rom just make sure it's an vanilla build and it's has signature spoofing
The question is, if you focus on privacy, does it make sense to install magisk, lsposed and other modules, where you can't really be sure what data they track and use and what backdoors they open.
So if you take a vanilla ROM with signature spoofing and just install microg etc from their website (normal .apk files) you can avoid rooting with it's vulnerabilities.
The only problem remaining is that some banking apps don't work due to safety net / CTS profile mismatch.
UniNick said:
The question is, if you focus on privacy, does it make sense to install magisk, lsposed and other modules, where you can't really be sure what data they track and use and what backdoors they open.
So if you take a vanilla ROM with signature spoofing and just install microg etc from their website (normal .apk files) you can avoid rooting with it's vulnerabilities.
The only problem remaining is that some banking apps don't work due to safety net / CTS profile mismatching
Click to expand...
Click to collapse
We'll I'll try to get more info about it, if I get any fix for it I'll update the guide
Btw I'm also working on safe lineageos based rom in which microg is pre-installed and there's no need to root for it
If there's an official LineageOS available, the guys at lineage.microg.org do this already.
Have a look also at IodéOS, available for some other devices, they manage somehow that the banking apps work. I haven't found out yet how they do it, must be something with the devices keys.
UniNick said:
If there's an official LineageOS available, the guys at lineage.microg.org do this already.
Have a look also at IodéOS, available for some other devices, they manage somehow that the banking apps work. I haven't found out yet how they do it, must be something with the devices keys.
Click to expand...
Click to collapse
I know, as the official release is not available I'm doing it
Vinc3nt.exe said:
Btw I'm also working on safe lineageos based rom in which microg is pre-installed and there's no need to root for it
Click to expand...
Click to collapse
Cant wait for LineageOS for Munch. take your time, King.
Hello Guys
Hope you guys are great
this is to inform you that unfortunately i couldn't build the microg version of lineageOS but i have successfully builded it's vanilla version and it's avaliable on xda