Database Develop

Non-neon Gapps (Android 4.2) dev-discussion thread

Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.

Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.

Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium

Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...

bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app

Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir

Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please

natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?

Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat

Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.

tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?

ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app

For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing

Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).

I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.

Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store

Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip

New google keyboard is available: link

DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.

tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!

ROMs with Signature Spoofing

I want to use MicroG instead of using GApps. Are there any ROMs with signature spoofing enabled for Xperia SP?

Possible ways to add signature spoofing
I was just reading about this yesterday, as I too had the intention of replacing GApps with MicroG. The usual methods require you to install a module called 'FakeGApps' in Xposed before flashing MicroG. But since there's no Xposed available for 7.1, there seem to be a few workarounds.
Here's what I found:
Guide to allow signature spoofing on any LOS14.1 device without Xposed (http://www.gabsoftware.com/tips/how-to-use-microg-on-lineageos-or-cyanogenmod-without-xposed/)
You need a PC-based tool made by @ale5000 to first patch your rom to enable signature spoofing (https://forum.xda-developers.com/android/development/tingle-fork-needle-t3438764)
I'm not sure if you have to flash MicroG files before or after patching your rom with the above mentioned tool. Anyway, here's a couple of links to MicroG posted in other devices' forums: Link 1, Link 2
Alternatively, I think we can use a Magisk-based module called NanoMod made by @Setialpha.
I haven't tried either method yet. Will try it out later today. Meanwhile, you may experiment with one of the two methods posted above at a time; I don't think its wise to try installing both at the same time. Just saying. Do share the results with us!
Have a nice day!

lex.vr7 said:
I'm not sure if you have to flash MicroG files before or after patching your rom with the above mentioned tool. Anyway, here's a couple of links to MicroG posted in other devices' forums: Link 1, Link 2
Click to expand...
Click to collapse
It is always better to patch before installing microG, but in most cases is the same.
To install microG, there is also microG unofficial installer (compatible with all devices and all ROMs).

ale5000 said:
It is always better to patch before installing microG, but in most cases is the same.
To install microG, there is also microG unofficial installer (compatible with all devices and all ROMs).
Click to expand...
Click to collapse
Whoa, thanks! I didn't come across this installer before. Guess I didn't do my research properly.

Wow I didn't see the replies till now. I actually tried tingle on RR and it worked fine and did use that flashable zip for microg.
Sadly Mozilla location is horrible compared to Google's for me here in India. Even playing around with TopNTP didn't help even though that helps usually if GPS is wonky.

ale5000 said:
It is always better to patch before installing microG, but in most cases is the same.
To install microG, there is also microG unofficial installer (compatible with all devices and all ROMs).
Click to expand...
Click to collapse
In the tingle repo please mention that you need p7zip-full I was confused for so long why it wasn't working.

__ganeshanand said:
In the tingle repo please mention that you need p7zip-full I was confused for so long why it wasn't working.
Click to expand...
Click to collapse
@__ganeshanand: I have to make a lot of changes but I didn't have time yet, I will do it surely.
I will add a possibility to configure and maybe add other backends in the installer in the future.

ale5000 said:
@__ganeshanand: I have to make a lot of changes but I didn't have time yet, I will do it surely.
I will add a possibility to configure and maybe add other backends in the installer in the future.
Click to expand...
Click to collapse
Oh cool. Looking forward to that then.

AICP now has implemented signature spoofing into their latest nightly builds

[ROM][March 2018]CottonmouthOS [8.1.0] [OPM1.171019.021.2018]

CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.​
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch

If anyone wants to reupload to a better file hosting site please do.

OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps​
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28

Does copperhead have the pixel navbar animation?

File not yet uploaded

ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1

ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP

I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?

ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.

jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.

how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp

Thank you for building this, I tried and failed miserably. Will flash it today :good:

Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?

KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.

smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.

Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg

jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now

KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.

jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.

smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.

LineageOS 18.1 Self Build, Wanting to learn how to customize

So I was able to get my Custom LineageOS 18.1 built with signature spoofing and I was able to install it and boot it up and MicroG is able to see that Sig Spoof in enabled. So now I'm wanting to start customizing the ROM to my needs, like adding APK's and general customization of the menus or other little tweaks and was just wanting to know is there any guides out there for Customizing a lineageOS rom? Any tips or pointers? Also, if anyone would like to download my ROM and check things out, please DM me for the link.
And thanks in advance!

drarkanex said:
So I was able to get my Custom LineageOS 18.1 built with signature spoofing and I was able to install it and boot it up and MicroG is able to see that Sig Spoof in enabled. So now I'm wanting to start customizing the ROM to my needs, like adding APK's and general customization of the menus or other little tweaks and was just wanting to know is there any guides out there for Customizing a lineageOS rom? Any tips or pointers? Also, if anyone would like to download my ROM and check things out, please DM me for the link.
And thanks in advance!
Click to expand...
Click to collapse
If you ask about customizing the ROM like menus and other styles then you can do them with the help of third-party apps , eg. Substratum. What it does basically is applying a customised overlay over the stock overlay , you can find the app and themes from the google play store itself. There are many options available and you can customize it your way.
Talking about device tweaks then you'll need to refer to your device maintainers.

Question How can I Degoogle my Redmi Note 10 Pro (sweet)?

I recently found out about CalyxOS, a custom ROM that replaces Google Apps with Open source apps, and that whenever Google Play Services is required, it uses MicroG instead. I like this approach, as I think it is the best one for degoogling without compromising a lot the functionality. However, this ROM is only available for Pixels, and I wanted to replicate something similar with my Redmi Note 10 Pro, but I don't know if it's possible.
I think of installing a Custom ROM, and instead of flashing GApps, I flash MicroG, hopefully getting a similar result. I think that LineageOS has a way to do this, but to be honest, I don't really feel comfortable knowing that the only version of it available for this phone is an unofficial one.
Is this possible with another ROM? What ROM would you exactly recommend me and how could I do this?

Any vanilla roms are mostly degoogled (Lineage OS, Havoc OS, crDroid, Carbon ROM etc...). Basically, if you want a degoogled experience, find the vanilla variant of the said rom though most roms nowadays copy pixel experience and degoogling is not really popular. As for a degoogled MIUI experience, you can only get it through a china port and only one miui china port rom exists in RN10Pro and it was last updated Nov.2021.

And after flashing the vanilla ROM, I guess that I have to install MicroG, right?
BigChungus321 said:
Any vanilla roms are mostly degoogled (Lineage OS, Havoc OS, crDroid, Carbon ROM etc...). Basically, if you want a degoogled experience, find the vanilla variant of the said rom though most roms nowadays copy pixel experience and degoogling is not really popular. As for a degoogled MIUI experience, you can only get it through a china port and only one miui china port rom exists in RN10Pro and it was last updated Nov.2021.
Click to expand...
Click to collapse

ADB AppControl. Can uninstall any app

ByteSeb said:
And after flashing the vanilla ROM, I guess that I have to install MicroG, right?
Click to expand...
Click to collapse
You also need to make sure the rom support signature spoofing, or ask the maintainer to build one with that if it's default not supported
Signature Spoofing
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com

ByteSeb said:
And after flashing the vanilla ROM, I guess that I have to install MicroG, right?
Click to expand...
Click to collapse
Yes you can choose between 4 options to install MicroG. Either MinMicroG (Magisk/TWRP), MicroG Installer Revived (Magisk), NanoDroid (Magisk/TWRP but only for A11), or manually installing and giving MicroG permission. Personally, I find MicroG Installer Revived and MinMicroG to be the best as it also support patched Play Store installation (because I rely on my old purchase). Also don't worry about the ROM you choose if it doesn't support signature spoof. You can always use FakeGapps LsPosed module to spoof that part. Just make sure to use a vanilla build to avoid hectic uninstallation of Google services and actually have a clean slate to work with. Also if you're wondering, banking apps (and some apps that check for latest Play Services) will not work. Safety Net can still be passed with MicroG. You can even get L1 Certificate and get Google Photos spoofed even on MicroG.

Thanks. Do you think there is any way for me to try it with a VM before doing it or something like that?
BigChungus321 said:
Yes you can choose between 4 options to install MicroG. Either MinMicroG (Magisk/TWRP), MicroG Installer Revived (Magisk), NanoDroid (Magisk/TWRP but only for A11), or manually installing and giving MicroG permission. Personally, I find MicroG Installer Revived and MinMicroG to be the best as it also support patched Play Store installation (because I rely on my old purchase). Also don't worry about the ROM you choose if it doesn't support signature spoof. You can always use FakeGapps LsPosed module to spoof that part. Just make sure to use a vanilla build to avoid hectic uninstallation of Google services and actually have a clean slate to work with. Also if you're wondering, banking apps (and some apps that check for latest Play Services) will not work. Safety Net can still be passed with MicroG. You can even get L1 Certificate and get Google Photos spoofed even on MicroG.
Click to expand...
Click to collapse

ByteSeb said:
Thanks. Do you think there is any way for me to try it with a VM before doing it or something like that?
Click to expand...
Click to collapse
Degoogling? Nope, I personally tried VM's like vmos, nox, bluestack, parallel space and they can't mostly because the OS they function with requires Google Play Services. If you still wanna try degoogling then I guess try on some old devices which support custom ROM (especially lineage). Worst you can do is soft brick which is still recoverable. But if you get more knowledge on custom ROMs and your plan to degoogle then you can't really fail. Just research more and ask for guide on others.

BigChungus321 said:
Degoogling? Nope, I personally tried VM's like vmos, nox, bluestack, parallel space and they can't mostly because the OS they function with requires Google Play Services. If you still wanna try degoogling then I guess try on some old devices which support custom ROM (especially lineage). Worst you can do is soft brick which is still recoverable. But if you get more knowledge on custom ROMs and your plan to degoogle then you can't really fail. Just research more and ask for guide on others.
Click to expand...
Click to collapse
You're right. That's why I tried it on BlueStacks but it didn't work.
What else does not work with MicroG?

ByteSeb said:
You're right. That's why I tried it on BlueStacks but it didn't work.
What else does not work with MicroG?
Click to expand...
Click to collapse
Most banking apps, apps that check for specific version of play services and above (microg version is like taken from android KitKat or smt so really outdated) example is MuseScore. So really, secure apps that implement safety net check most likely doesn't work with microg. Still you can spoof device attestation to basic and pass safety net for some apps like Netflix.

BigChungus321 said:
Most banking apps, apps that check for specific version of play services and above (microg version is like taken from android KitKat or smt so really outdated) example is MuseScore. So really, secure apps that implement safety net check most likely doesn't work with microg. Still you can spoof device attestation to basic and pass safety net for some apps like Netflix.
Click to expand...
Click to collapse
Is there any way to force apps like banking apps to work with MicroG? Maybe with some Magisk module or something like that?

ByteSeb said:
Is there any way to force apps like banking apps to work with MicroG? Maybe with some Magisk module or something like that?
Click to expand...
Click to collapse
Sometimes I guess so... It did work on a few apps for me. Magisk 25.1 only uses zygisk and Shamiko magisk module is used to hide the root. But magisk hide on v23 can hide root better on some apps. But that is with root, not spoofing the microg to work with banking apps. So I guess there is not. Still worth a shot though. I find using website version of my banking app better cause the browser doesn't actually check for root.

What to think of this Unofficial /e/OS rom
A rom based on lineage without all of google
I run it with recovery orangefox, Magisk 25,2 and adaway
And all i use is working
Sweet
Murena - Choose freedom
ecloud.global

chabula said:
What to think of this Unofficial /e/OS rom
A rom based on lineage without all of google
I run it with recovery orangefox, Magisk 25,2 and adaway
And all i use is working
Sweet
Murena - Choose freedom
ecloud.global
Click to expand...
Click to collapse
Pls send some screenshots like settings and special settings, Battery consumption and so on. Thanks

Hey ByteSeb,
First I want to tell you that privacy is a journey, there are a lot of aspects to it, and is not a on or off switch. Don't be disheartened if you can't accomplish everything, every step you take to regain your privacy counts.
The best thing you could do is buy a pixel phone if you can afford, and use either calyx or graphene os, maybe even divestOS. AOSP is not completely degoogled, for eg it still has google dns, gps, etc. (example).
You can always make changes to open source roms. The only decent vanilla rom for this device I found is ArrowOS, or you could even try Lineage GSI.
One of the most important things you can do is: use open source apps, like newpipe instead of youtube. And lets say you want to be signed in to your social media account or email, use different browsers. For eg you can use one browser where you do all your stuff where your one identity is tied. But I would recommend just use pc or laptop for most things, as they are much better at privacy than android (use linux/unix).
PS: don't look for privacy advices on xda or reddit...

Laptapper said:
Pls send some screenshots like settings and special settings, Battery consumption and so on. Thanks
Click to expand...
Click to collapse
Unofficial /e/ OS - Android S/12 - Xiaomi redmi note 10 pro **sweet** ​
/e/OS DevicesUnOfficial Builds
unofficial-builds xiaomi sweet s
ChimpthepimpI Build ROM's
10d
Another S/Android 12 build for the Xiaomi Redmi Note 10pro - sweet
A big thanks to pulkit077, whose sources have premitted me to assemble this rom.
- Please make sure you use the latest twrp version, 3.7.0-a12.0 to flash the ROM.
- It is recommended to clean flash, for this device with dynamic partitioning, that means flash the rom and then format data.
- If you are coming from a different vendor version please make sure to flash miui vendor first, accordingly to your region.
- If you are coming from a different Android version make sure to rollback to android 12 firmware.
I have tested this rom the past 2 weeks myself and am happy about feedback or to assisst if needed.
Find the rom file here 3
Enjoy /e/ on the Xiaomi Redmi note 10pro
/e/OS - e Foundation - deGoogled unGoogled smartphone operating systems and online services - your data is your data
ECOSYSTEMKEY FEATURESGET /E/OSNEED HELP /e/OS is a complete, fully “deGoogled”, mobile ecosystem /e/OS is an open-source mobile operating system paired with carefully selected applications. They form a privacy-enabled internal system for your smartphone. And it’s not just claims: open-source...
e.foundation
/e/OS product description - a pro-privacy mobile operating system and cloud services

chabula said:
Unofficial /e/ OS - Android S/12 - Xiaomi redmi note 10 pro **sweet** ​
/e/OS DevicesUnOfficial Builds
unofficial-builds xiaomi sweet s
ChimpthepimpI Build ROM's
10d
Another S/Android 12 build for the Xiaomi Redmi Note 10pro - sweet
A big thanks to pulkit077, whose sources have premitted me to assemble this rom.
- Please make sure you use the latest twrp version, 3.7.0-a12.0 to flash the ROM.
- It is recommended to clean flash, for this device with dynamic partitioning, that means flash the rom and then format data.
- If you are coming from a different vendor version please make sure to flash miui vendor first, accordingly to your region.
- If you are coming from a different Android version make sure to rollback to android 12 firmware.
I have tested this rom the past 2 weeks myself and am happy about feedback or to assisst if needed.
Find the rom file here 3
Enjoy /e/ on the Xiaomi Redmi note 10pro
/e/OS - e Foundation - deGoogled unGoogled smartphone operating systems and online services - your data is your data
ECOSYSTEMKEY FEATURESGET /E/OSNEED HELP /e/OS is a complete, fully “deGoogled”, mobile ecosystem /e/OS is an open-source mobile operating system paired with carefully selected applications. They form a privacy-enabled internal system for your smartphone. And it’s not just claims: open-source...
e.foundation
/e/OS product description - a pro-privacy mobile operating system and cloud services
Click to expand...
Click to collapse
Sounds very good!
/e/OS product description - a pro-privacy mobile operating system and cloud services
Pls make a separate thread for this ROM

Laptapper said:
Sounds very good!
/e/OS product description - a pro-privacy mobile operating system and cloud services
Pls make a separate thread for this ROM
Click to expand...
Click to collapse
I run this Rom
On my old poco F1 Offcial
Samsunf Tab SN T585 year 2016 unofficial Android 10
and the aredmi Note 10 pro

Stan m said:
Hey ByteSeb,
First I want to tell you that privacy is a journey, there are a lot of aspects to it, and is not a on or off switch. Don't be disheartened if you can't accomplish everything, every step you take to regain your privacy counts.
The best thing you could do is buy a pixel phone if you can afford, and use either calyx or graphene os, maybe even divestOS. AOSP is not completely degoogled, for eg it still has google dns, gps, etc. (example).
You can always make changes to open source roms. The only decent vanilla rom for this device I found is ArrowOS, or you could even try Lineage GSI.
One of the most important things you can do is: use open source apps, like newpipe instead of youtube. And lets say you want to be signed in to your social media account or email, use different browsers. For eg you can use one browser where you do all your stuff where your one identity is tied. But I would recommend just use pc or laptop for most things, as they are much better at privacy than android (use linux/unix).
PS: don't look for privacy advices on xda or reddit...
Click to expand...
Click to collapse
According to /e/OS
They stated this
DeGoogling / UnGoogling in /e/OS​The goal of “deGoogling” is
To remove or disable any feature or code that is sending data to Google servers, or at least to anonymize those accesses
To offer non-Google default online services, including for search.
the Google default search engine is removed and replaced by other services (see below in default apps and services)
Google Services are replaced by microG and alternative services (see below for more details)
All Google apps are removed and replaced by equivalent Open Source applications. The one exception is the Maps Application
No use of Google servers to check connectivity
NTP servers are not Google NTP servers anymore
DNS default servers are not Google anymore, and their settings can be enforced by the user to a specific server
Geolocation is using Mozilla Location Services in addition to GPS
CalDAV/CardDAV management and synchronization application (DAVDroid) is fully integrated with the user account and calendar/contact application
More details about the state of /e/OS OS deGooglisation can be found in this white paper.
It seems that all what you mentionesd is replaced in this OS

chabula said:
According to /e/OS
They stated this
DeGoogling / UnGoogling in /e/OS​The goal of “deGoogling” is
To remove or disable any feature or code that is sending data to Google servers, or at least to anonymize those accesses
To offer non-Google default online services, including for search.
the Google default search engine is removed and replaced by other services (see below in default apps and services)
Google Services are replaced by microG and alternative services (see below for more details)
All Google apps are removed and replaced by equivalent Open Source applications. The one exception is the Maps Application
No use of Google servers to check connectivity
NTP servers are not Google NTP servers anymore
DNS default servers are not Google anymore, and their settings can be enforced by the user to a specific server
Geolocation is using Mozilla Location Services in addition to GPS
CalDAV/CardDAV management and synchronization application (DAVDroid) is fully integrated with the user account and calendar/contact application
More details about the state of /e/OS OS deGooglisation can be found in this white paper.
It seems that all what you mentionesd is replaced in this OS
Click to expand...
Click to collapse
Not a new post..... A new thread with this ROM