[TIPS] [HOW TO] [NO ROOT] [ADB] [6.0+] Better Battery Life & Multitasking - Sony Cross-Device General

Yo guys! Today I’m gonna share to you some lil’ tips for better battery life WITHOUT ROOT.
If your device already rooted I’m pretty sure you won’t get profit that much by using below tips (Greenify already done those jobs or find another thread you can do with it).
By following this may disrupt your apps function so I don’t care, you are fully responsible of your device.
Consider the big cons for this whole tips is you have to run below apps server from ADB once after your device reboot.
(I can live with that cz I’m rarely reboot my device )
D.W.Y.O.R​
Click to expand...
Click to collapse
This thread aim for better battery life (of course) through stopping unnecessary wakelock & useless running background apps this may give you more available free RAM.
HIGHER ANDROID API = BETTER COMPATIBILITY
(I’m highly recommends minimum Android 6.0+)​
Preparation & Explanation
ADB: Download from HERE and setup as insctructed.
You can skip if ADB already install in your pc, however in case ADB can’t detect your device it may require driver depending on model manufacturer
Brevent: Download from playstore HERE
IMO this app works better than Greenify for NON ROOT user, provides us to custom brevent method, how long we want put apps to background mode or standby mode. EZ step below:
Install Brevent from playstore link above
Plug your device to pc with usb debugging enabled
Open cmd / terminal within adb folder (shift + right click)
Type
Code:
adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh
Open brevent
Setting as your need
If you rebooted device then repeat step 2 to 4
Note: If you dislike this way choose Greenify. Don’t disable usb debugging on Android 8.0+. Repeat step above once you restart device. Original thread here.
AppOps: Download from playstore HERE
Missing appops xposed module? Here we go just install from PS link above. Read description carefully I think even noob like me will understand.
Shizuku Manager: Download from playstore HERE
Familiar with Magisk or Xposed? So you won’t face any difficult using this one which is needed by AppOps to run. Full setup steps are in the description within app:
Install Shizuku from playstore link above
Plug your device to pc with usb debugging enabled
Open cmd / terminal within ADB folder (shift + right click)
Type
Code:
adb -d shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh
Open Shizuku app
Tap on authorized to get token and allow AppOps
If you rebooted device then repeat step 2 to 4
Since here, you can use AppOps as you wish nearly the same as AppOps xposed module did alongside Brevent. Shizuku are safe to brevented while AppOps not, so you have to whitelist it.
Another tips is disable carrier / manufacturer’s bloatware as much possible using script
Code:
adb -d shell pm uninstall -k --user 0 <name of package>
​
Tested with:
Xperia XZ1 Compact - 8.0 Non Rooted
Samsung S7 Edge - 7.0 Non Rooted​

ryandxter said:
Yo guys! Today I’m gonna share to you some lil’ tips for better battery life WITHOUT ROOT.
If your device already rooted I’m pretty sure you won’t get profit that much by using below tips (Greenify already done those jobs or find another thread you can do with it).
This thread aim for better battery life (of course) through stopping unnecessary wakelock & useless running background apps this may give you more available free RAM.
HIGHER ANDROID API = BETTER COMPATIBILITY
(I’m highly recommends minimum Android 6.0+)
Preparation & Explanation
Install Brevent from playstore link above
Open cmd / terminal within adb folder (shift + right click)
Open brevent
If you rebooted device then repeat step 2 to 4
Note: If you dislike this way choose Greenify. Don’t disable usb debugging on Android 8.0+. Repeat step above once you restart device. Original thread here.
[/LIST]
Install Shizuku from playstore link above
Open cmd / terminal within ADB folder (shift + right click)
Open Shizuku app
If you rebooted device then repeat step 2 to 4
[/LIST]
Since here, you can use AppOps as you wish nearly the same as AppOps xposed module did alongside Brevent. Shizuku are safe to brevented while AppOps not, so you have to whitelist it.
Another tips is disable carrier / manufacturer’s bloatware as much possible using script
Tested with:
Xperia XZ1 Compact - 8.0 Non Rooted
Samsung S7 Edge - 7.0 Non Rooted
Click to expand...
Click to collapse
Why's is there no communication on this lol, decent thread.

Thank you!!!! This not only helped me save battery, also showed me a new app that I desperately been looking for (Shizulu Manager)

ryandxter said:
Yo guys! Today I’m gonna share to you some lil’ tips for better battery life WITHOUT ROOT.
If your device already rooted I’m pretty sure you won’t get profit that much by using below tips (Greenify already done those jobs or find another thread you can do with it).
This thread aim for better battery life (of course) through stopping unnecessary wakelock & useless running background apps this may give you more available free RAM.
HIGHER ANDROID API = BETTER COMPATIBILITY
(I’m highly recommends minimum Android 6.0+)​
Preparation & Explanation
ADB: Download from HERE and setup as insctructed.
You can skip if ADB already install in your pc, however in case ADB can’t detect your device it may require driver depending on model manufacturer
Brevent: Download from playstore HERE
IMO this app works better than Greenify for NON ROOT user, provides us to custom brevent method, how long we want put apps to background mode or standby mode. EZ step below:
Install Brevent from playstore link above
Plug your device to pc with usb debugging enabled
Open cmd / terminal within adb folder (shift + right click)
Type
Code:
adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh
Open brevent
Setting as your need
If you rebooted device then repeat step 2 to 4
Note: If you dislike this way choose Greenify. Don’t disable usb debugging on Android 8.0+. Repeat step above once you restart device. Original thread here.
AppOps: Download from playstore HERE
Missing appops xposed module? Here we go just install from PS link above. Read description carefully I think even noob like me will understand.
Shizuku Manager: Download from playstore HERE
Familiar with Magisk or Xposed? So you won’t face any difficult using this one which is needed by AppOps to run. Full setup steps are in the description within app:
Install Shizuku from playstore link above
Plug your device to pc with usb debugging enabled
Open cmd / terminal within ADB folder (shift + right click)
Type
Code:
adb -d shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh
Open Shizuku app
Tap on authorized to get token and allow AppOps
If you rebooted device then repeat step 2 to 4
Since here, you can use AppOps as you wish nearly the same as AppOps xposed module did alongside Brevent. Shizuku are safe to brevented while AppOps not, so you have to whitelist it.
Another tips is disable carrier / manufacturer’s bloatware as much possible using script
Code:
adb -d shell pm uninstall -k --user 0 <name of package>
​
Tested with:
Xperia XZ1 Compact - 8.0 Non Rooted
Samsung S7 Edge - 7.0 Non Rooted​
Click to expand...
Click to collapse
Thank You

I'm having trouble with the app. it doesn't seem to be Force stopping any of the applications

Related

[GUIDE][NO ROOT][STICK 2] Playing With Matches v1

I thought I'd share my relatively less dangerous methods to turn a Fire TV Stick 2 into an Android TV clone.
First up follow my GApps/Google Services installation guide. This will provide the necessary backbone to install every other application.
You can either install Backdrop as below or ignore those instructions and use my newly ported Android TV settings app to select your screensaver! (no root required!).
Get it here: https://github.com/rockon999/TvSettingsOnFire/releases
Note this settings app requires addition permissions that must be granted via adb. They are listed on the releases page.
First let's install Backdrop (this provides a chromecast-like screen saver for your Fire TV).
Here is the APK link.
adb connect [IP of FTV]
adb install [APK PATH]
adb shell
settings put secure screensaver_components com.google.android.backdrop/.Backdrop
Now you have the Android TV screensaver! Look here for how to configure the timing of the screensaver/sleep.
Now let's install the Leanback launcher. Unfortunately the only Leanback launcher that will load on the Fire TV (without root) is one circa ~2015 and it is *buggy*. To aid this guide (and my sanity) I've taken the decompiled sources of LeanbackLauncher, stripped them of Google services, added features, improved stability, and added Fire TV specific features. You can find that here.
Now let's install Google's TV search app. I've found a working 2.x series version that is better looking, more stable, and much faster. You can get the APK here. Unfortunately the latest version is incompatible but an older version works surprisingly well. I've found version 1.0.6.2108324 to be the most stable. You can download the APK here.
UPDATE: I've figured out how to get Google's voice search working! (this only works w/ voice remotes not apps)
Running this command will disable global Alexa and allow Google to work (if you're on an old enough firmware): adb uninstall -k --user 0 com.amazon.vizzini
And there you go! Your Fire TV Stick is an almost-Android TV stick.
Stay tuned because this guide and Leanback on Fire is being continuously updated!
Very good work!
Thank you, this is what I've been looking for.
rockon999 said:
I thought I'd share my relatively less dangerous methods to turn a Fire TV Stick 2 into an Android TV clone.
Click to expand...
Click to collapse
Could you also include that activities in your launcher-mod ?
Code:
com.amazon.tv.settings/.tv.applications.ApplicationsActivity
And for a rooted version of your launcher (just as an idea):
Code:
com.android.tv.settings/.MainSettings
For com.android.tv.settings/.MainSettings you need to simply install TvSettings.apk with root and you will get almost all functions of the standard Android TV settings menu!
Code:
adb push TvSettings.apk /sdcard/
adb shell su -c mkdir /system/priv-app/TvSettings
adb shell su -c chmod 755 /system/priv-app/TvSettings
adb shell su -c cp /sdcard/TvSettings.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c rm /sdcard/TvSettings.apk
rainman74 said:
Could you also include that activities in your launcher-mod ?
Code:
com.amazon.tv.settings/.tv.applications.ApplicationsActivity
And for a rooted version of your launcher (just as an idea):
Code:
com.android.tv.settings/.MainSettings
For com.android.tv.settings/.MainSettings you need to simply install TvSettings.apk with root and you will get almost all functions of the standard Android TV settings menu!
Code:
adb push TvSettings.apk /sdcard/
adb shell su -c mkdir /system/priv-app/TvSettings
adb shell su -c chmod 755 /system/priv-app/TvSettings
adb shell su -c cp /sdcard/TvSettings.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c rm /sdcard/TvSettings.apk
Click to expand...
Click to collapse
For the first suggestion app settings are accessible by pressing menu while on a specific application and selecting "App Settings". I think that's what you're after, but if not correct me. The issue with launching the settings activity itself is that it will crash (at least on my FTV Stick 2). I have solved crashes before, though, so I'll look into it. As for your second suggestion I can simply look into re-adding the default ATV settings code (which should interface with this app well). Unfortunately, I'll have no way to test this (I only have an un-rootable FTV sticks) so it may take longer.
rockon999 said:
For the first suggestion app settings are accessible by pressing menu while on a specific application and selecting "App Settings". I think that's what you're after, but if not correct me. The issue with launching the settings activity itself is that it will crash (at least on my FTV Stick 2). I have solved crashes before, though, so I'll look into it.
Click to expand...
Click to collapse
No, I actually meant the global app menu. With me this doesn't crash when I start it directly via adb, but via Confireator I get a crash.
So it works without crash:
adb shell at the start -n com. amazon. tv. settings/. tv. applications. ApplicationsActivity
As for your second suggestion I can simply look into re-adding the default ATV settings code (which should interface with this app well). Unfortunately, I'll have no way to test this (I only have an un-rootable FTV sticks) so it may take longer.
Click to expand...
Click to collapse
That would be great!
I tried the microphone. I held the microphone button on my remote and talked. it worked. I don't think you intended it to work at all. So you should probably update about that. And it feels good to have leanback. Also is the recommendations thing impossible?
Pix12 said:
I tried the microphone. I held the microphone button on my remote and talked. it worked. I don't think you intended it to work at all. So you should probably update about that. And it feels good to have leanback. Also is the recommendations thing impossible?
Click to expand...
Click to collapse
The normal leanback recommendations system will either 1) crash or 2) display recommendations w/o their images (neither of those things are particularly pleasant). Together they mean you end up with a bunch of giant grey blocks (that never update) on your screen. So, essentially, the best way forward (I think) is to attempt to completely rewrite the recommendations code from scratch so that it can function in the user space. There is maybe a 50/50 chance that it will actually work though as recommendations operate over the notifications system and with Amazon's notification systems and Google's recommendations setup on the same machine they don't like to get along.
Side note, I'm surprised the microphone worked as Amazon coded it to always go to Alexa. I have some questions
1) Have you debloated? If so, what?
2) Are you rooted?
3) Any special mods?
Thanks!
rockon999 said:
Side note, I'm surprised the microphone worked as Amazon coded it to always go to Alexa. I have some questions
1) Have you debloated? If so, what?
2) Are you rooted?
3) Any special mods?
Thanks!
Click to expand...
Click to collapse
I debloated the FireTV, it's not rooted and I used Launcher Hijacker 3 to use as home screen. It might've been me using the
Code:
adb shell pm grant com.google.android.katniss android.permission.RECORD_AUDIO
command for the Google app to allow the microphone.
Pix12 said:
I debloated the FireTV, it's not rooted and I used Launcher Hijacker 3 to use as home screen. It might've been me using the
Code:
adb shell pm grant com.google.android.katniss android.permission.RECORD_AUDIO
command for the Google app to allow the microphone.
Click to expand...
Click to collapse
I'm guessing it's because your debloat removed the package that forces Alexa. Similar to how removing the launcher allows other launchers to work without modification apps. I'll poke around and see if I can replicate/find the package.
rockon999 said:
I'm guessing it's because your debloat removed the package that forces Alexa. Similar to how removing the launcher allows other launchers to work without modification apps. I'll poke around and see if I can replicate/find the package.
Click to expand...
Click to collapse
Yeah, I removed really everything Amazon. It showed the launcher menu.
Pix12 said:
Yeah, I removed really everything Amazon. It showed the launcher menu.
Click to expand...
Click to collapse
which is the package that forces Alexa?
is a new version of LeanbackLauncher coming soon?
rainman74 said:
is a new version of LeanbackLauncher coming soon?
Click to expand...
Click to collapse
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
rockon999 said:
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
Click to expand...
Click to collapse
WOW! :good::good::good:
rockon999 said:
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
Click to expand...
Click to collapse
Awesome work!
rockon999 said:
I'm completely rewriting a lot of the database storage code (there are a lot of broken/missing database calls) and am close to done. I'm just trying to fix the favorites row at this point but moving apps elsewhere is working. I've also re-added the code to link to the native android tv settings app and I also ported the native android tv settings app to Fire TV (without root required!). In addition, I've gotten the leanback keyboard fully working! I'd say a day or two and I'll update the guide
Click to expand...
Click to collapse
Awesomeeeee!!!!!!!!!:laugh::laugh::laugh:
UPDATE: I've figured out how to get Google's voice search working! (this only works w/ voice remotes not apps)
Running this command will disable global Alexa and allow Google to work (if you're on an old enough firmware): adb uninstall -k --user 0 com.amazon.vizzini
rockon999 said:
UPDATE: I've figured out how to get Google's voice search working! (this only works w/ voice remotes not apps)
Running this command will disable global Alexa and allow Google to work (if you're on an old enough firmware): adb uninstall -k --user 0 com.amazon.vizzini
Click to expand...
Click to collapse
working perfectly with the newer apk from OP
ALPHA 2 OF LEANBACK IS OUT AND ATV SETTINGS APP PORTED
https://github.com/rockon999/Leanbac...leases/tag/0.2
NOTE: You must completely remove Alpha 1 (and clear its storage - instructions on the release page) as Alpha 1 had database storage bugs that make Alpha 2 inoperable.
The first alpha of my port of Android TV's settings app, TvSettingsOnFire, is also available (note the permission requirements)! https://github.com/rockon999/TvSettingsOnFire/releases
Also, if you've ever actually wanted to see what your were editing while you were typing Leanback Keyboard works perfectly in conjunction with my TvSettings port! You can grab it here.

[GUIDE] microG - Deodex - Signature Spoofing - Debloat Gapps!

microG
I am no longer working on this, or updating any information here! This was created back in the day of Oreo.
I've personally moved on and I'm presently using /e/ which you can see the info here and get the ROM for OP5T.
/e/OS documentation - OnePlus 5T
Info about OnePlus 5T - dumpling
As of this post edit on 10/20/22 I'm using 'e-1.4-r-20220922220394-dev-dumpling' and /e/ uses microg. It runs quite nice, so check it out!
microG is Freedom, Security & Privacy from Google, by replacing the Google Services & Framwork, also improving phone and battery performance!
This guide shows you the steps needed to Deodex, Signature Spoofing, Debloat Gapps and install microG.
This is not just a OxygenOS guide, this works on any ROM with Gapps baked in, lack signature spoofing, or doesn't come with microG installed! The only areas specific to OxygenOS is using Xposed and the microG permissions, both which might not be needed on other ROMs, everything else you follow in this guide for any ROM.
The information is here to give you a complete understanding of the process, it's just the Android way is all! Without the information and only steps to follow, there are a lot of areas you could experience problems, and not know how to deal with them.
There is no shorter, or easier way to accomplish this, if there was I would of made a smaller quickie guide, this is the way it works in Android! If you want to do microG you're going to have to read, it looks like a lot but it's not, once you've done it a few times!
Remember, the information is here to help you!
Pie is not supported in Xposed, and at the present moment OxygenOS requires Xposed.
You need to WIPE and install the ROM and start fresh, otherwise it can get complicated, you've been warned! You also need to follow the steps exactly, do not deviate, the process is picky, that is why the steps are to be done this way!
When you go online for the first time do not allow any Google updates! Do not install any Gapps, or anything, other than what is mentioned in this guide!
Keep online time limited to the steps needed in this guide. Connect only to accomplish what is needed and keep an eye out for Google updates and cancel them!
I highly recommend making TWRP backups every step of the way, in case of a mistake, then you don't have to start all over!
Once you get the steps down, the entire process takes around 30-60 minutes to complete!
Each of the RED sections are the STEPS, just read and follow them one by one!
DEODEX OR FAKEGAPPS
For stock or custom roms that don't support signature spoofing, you can either deodex the rom with the VDEXEXTRACTOR steps and use the Nanodroid-patcher to apply signature spoofing, or use the Xposed FakeGapps module which enables signature spoofing support.
If you use an application called "Signature Spoofing Checker" with the Xposed FakeGapps module installed and it shows the support disabled, ignore it. FakeGapps is working, it's a bug in the "Signature Spoofing Checker". 5.1.5 shows Green/Enabled and 5.1.6 shows Red/Disabled.
If you use the Xposed FakeGapps module skip to the [MAGISK] SYSTEMLESS XPOSED section! If you know how to compile for vdexExtractor, there is no reason to use FakeGapps!
VDEXEXTRACTOR
This method shown below is a simple Deodex that NanoDroid uses. SuperR's Kitchen also uses vdexExtractor, but instead does a Full Deodex. The NanoDroid method is simpler, without the need for SuperR's Kitchen. I plan on eventually adding a method of using SuperR's Kitchen to the guide at some point in time.
This NanoDroid Deodex method shown here is good, it's just not a Full Deodex, it hurts nothing, it's not better or worse, just different! So, if you aren't concerned with needing/wanting the full customization capability that a Full Deodex offers, or you have no idea of what is being said here, then don't worry!
ROMs that are either in a state of VDEX or ODEX need to be DEODEX in order to apply Signature Spoofing! So depending on the ROM, check to find out which state it is in, and then you will apply either the VDEX or ODEX methods outlined in this guide; https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
In this guide for OxygenOS you will be following the VDEX method. OxygenOS follows the VDEX method because it has both .odex and .vdex files in the system.
You will have to compile the vdexExtractor source on either Windows, MacOS, or Linux, this guide doesn't cover compiling.
At the end of this section where you download vdexExtractor on GitHub, under the Dependencies section being mentioned there, this is a brief explanation of that information to help get you started.
This is only the basics explained to help get you now moving in the right direction for compiling. If you have any other concerns or questions please search on Google, there is a wealth of information online to help you.
1. macOS users will need to compile by installing Homebrew https://brew.sh/ and adding the dependency zlib-devel as brew install zlib-devel. Then you should be able to use the terminal in macOS to run the command, ./make.sh gcc or sh make.sh gcc to now compile.
2. For Linux users you need to make sure you have libz-dev installed and then at a terminal run either, ./make.sh gcc or sh make.sh gcc to compile.
3. For Windows users you'll need to install cygwin, https://www.cygwin.com/ cygwin helps to give you a Unix/Linux like build environment. Make sure to install zlib-devel from the cygwin installer, it should be listed under the Devel section which you click it so it changes from the word Default to Install, if you don't see zlib-devel listed there, then search for it. There is a lot of information online about installing and using cygwin, hopefully this link below is still working fine for Windows 10 to help you setup the Cygwin Path to the Windows Environment Variable, to make it easier to use the command prompt to compile from. In Windows you'll also run the commands, either ./make.sh gcc or sh make.sh gcc to compile.
Install Cygwin and How to Use Linux Commands in Windows with Cygwin
https://www.howtogeek.com/howto/41382/how-to-use-linux-commands-in-windows-with-cygwin/
If compiling is a problem you can always use the Xposed FakeGapps module, but it's best to DEODEX/PATCH the ROM!
Learn to compile, you'll be better off for it in the long run, switch to Linux it makes the process of compiling a lot easier than any other OS.
Be sure to look at the vdexExtractor Github for basic compile information, where you'll download the source; https://github.com/anestisb/vdexExtractor
NANODROID PATCHER
Download the NanoDroid-patcher; https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Download from Stable Download (Nanolx) - As of to date it's version NanoDroid-patcher-20.2.20181122.zip
DEODEX SETUP
Boot to TWRP and mount the /system read-write.
Once you have mounted the /system in TWRP run these commands on your computer to deodex!
DEODEX COMMANDS
Code:
adb pull /system/framework framework
cp framework/services.jar services.jar-backup
vdexExtractor -i framework/oat/arm64/services.vdex --ignore-crc-error
mv framework/oat/arm64/services_classes.dex classes.dex
zip framework/services.jar classes.dex
zip -j framework/services.jar classes.dex
adb push framework/services.jar /system/framework
adb shell
chmod 644 /system/framework/services.jar
chown root:root /system/framework/services.jar
SIGNATURE SPOOFING
Unmount the /system read-write - TWRP > Mount > uncheck System
Install the NanoDroid-patcher in TWRP. (This takes around 10 minutes!)
If you did the deodex correctly, when flashing NanoDroid-patcher it will say Deodex.
When the patch has completed reboot the phone.
[MAGISK] SYSTEMLESS XPOSED
Xposed does not pass SafetyNet!
Download [Magisk] Systemless Xposed - XposedInstaller_3.1.5-Magisk.apk; https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
MAGISK ROOT
Boot to TWRP and install Magisk to root your phone.
Reboot the phone and update Magisk.
MAGISK MODULES
Do not reboot until you have installed all three modules!
Install the Xposed Framework (SDK 27) - For Xposed to install, Systemless Xposed and Magisk need to be the only two things first installed in the rom!
Install the Debloater (Terminal Emulator) - Debloats the phone Systemlessly!
Install the F-Droid Privileged Extension - Read about it here; https://f-droid.org/en/packages/org.fdroid.fdroid.privileged/
After installing these three modules reboot your phone!
XPOSED MODULES
Open Xposed while connected online, it should be displaying in Green! If it is Red you might not of followed the steps correctly, especially the part about doing this on a "Fresh Clean ROM", and following the guide step by step.
Install FakeGapps if you did not deodex the rom, and then apply the signature spoofing NanoDroid-patch!
The XposedGmsCoreUnifiedNlP module will be installed later with microG, mentioned in the MICROG section!
If you installed FakeGapps, go to the Modules section and check the module to enable it, then reboot the phone.
F-DROID
You have basically 3 choices for applications; Aurora Store, F-Droid, Yalp Store.
For now I recommend you install F-Droid, download from https://f-droid.org/en/
After installing F-Droid go to Settings, toggle on Expert mode, make sure Privileged Extension is checked, close and reopen F-Droid and then update F-Droid if a new version is available!
You'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with many features.
Search for an install Termux!
DEBLOATING APPS SYSTEMLESSLY
Do not debloat the Google Play Store if you plan on using it!
Do not create/add a Google Account, it will only get removed when you debloat out Google, instead wait to the last section I WANT MY GOOGLE & STAY PRIVATE TOO, and add it after you have installed and setup microG!
If you want to keep some Gapps that's your choice! Be sure to run any Gapps that you want to keep before debloating. This is not always the common situation where you need to run Gapps before debloating, it's typically rare, but some odd applications will have a hard time working with microG if this isn't done. For applications you are not sure of, be sure to run them, especially applications that use Location, such as OnePlus Weather and the Camera, etc., before debloating!
Make sure you are connected online when you run Termux for the first time.
With Termux running, at the command prompt type su for superuser access and grant root access.
Type debloat and you'll remove from 1 - System Apps & 2 - System Priv-Apps.
Type the numbers with spaces in between for the applications you are debloating, as an example; 15 16 17.
When you have the applications typed in and you are ready to debloat, tap enter.
For the best Gapps Free experience debloat all of these;
Android Setup
Calendar
Chrome
Drive
Duo
Gboard
Gmail
Google
Google Backup Transport
Google One Time Init
Google Partner Setup
Google Pay
Google Play Movies
Google Play Music
Google Play Services
Google Play Store - (Do not debloat if you're going to use!)
Google Services Framework
Market Feedback Agent
Maps
Photos
On a note of Privacy, there's information online in regards to OnePlus and Analytics/Data Mining as it relates to the below applications.
I highly recommend that if you're serious about privacy to do your own research and judge for yourself, but if you're asking me I debloated all of them!
BugReportLite
EngSpecialTest
FactoryMode
Insight Provider
LogKitSdService
OnePlusLogKit
Oneplus System Service
RfToolkit
After debloating you are suppose to reboot your phone for the changes to take effect!
If you debloated Chrome, make sure you update the Android System WebView in either the Aurora Store or Yalp Store, after you've completed the installation of microG!
Make sure you debloated Gboard, be sure to install another keyboard before rebooting! I recommend installing AnySoftKeyboard from F-Droid!
If you make any mistakes, you have the option to reinstall applications!
Reboot the phone...
If any updates occurred, after debloating some Gapps might still appear in the system. These now turn into User-Installed applications, so either in the Settings > Apps > Application List, you'll have the option to uninstall, or if the application is in the App Drawer, you can now uninstall it from there!
If the Google Play Services is listed in the phone but no option shown to uninstall, follow the GMS PROBLEMS section! Regardless of what you see or don't see in the Application List be sure to still follow the GMS PROBLEMS section!
GMS PROBLEMS
Before installing microG you need to make sure this GMS directory com.google.android.gms is out of the system!
Run this command;
Code:
adb uninstall com.google.android.gms
If com.google.android.gms exists and you were able to remove it, you'll see this reply; Success
If you see a lot of output with this line, then you have no changes or updates installed, there's nothing to remove;
java.lang.IllegalArgumentException: Unknown package: com.google.android.gms
If com.google.android.gms exists and the Google Play Services is still active, you'll see this reply; Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
If the Google Play Services is still active you will have to manually remove com.google.android.gms.
Run these commands;
Code:
adb shell
su
cd /data/data
rm -rf com.google.android.gms
If you run rm -rf com.google.android.gms and get this reply back; rm: databases: Directory not empty, just run the command over!
Even if the command gave you a success response, or unknown package, be sure to visually check for the presence of com.google.android.gms in /data/data!
Exit and reboot your phone!
If you had to manually remove com.google.android.gms, go to the Settings > Apps > Application List > Three Dots (Upper Right) > Show system apps. If you see the Google Play Services uninstall it, the option to uninstall should now be available. Click uninstall and wait a few seconds for a popup to appear and click ok to remove.
microG creates com.google.android.gms, do not remove it after you have microG installed!
DALVIK CACHE & CACHE
Before installing microG, boot into TWRP and Wipe the Dalvik Cache and Cache!
When done wiping reboot the phone back into the system.
NANODROID-MICROG
At the present moment it is better to use the NanoDroid-microG version! Official microG is not getting as much development!
Visit the NanoDroid post on XDA;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Down from the Stable Download (Nanolx) link!
If you use the NanoDroid-microG version, take the "FakeStore" "GmsCore" "GsfProxy" from the zip, look for them in the folders under /system/priv-app/ use the "GmsCore_NanoDroid" and "GsfProxy_NanoDroid" and be sure to rename them, and follow the MICROG steps below using these versions instead of the Offical microG!
MICROG
microG on stock Android sometimes take a little more effort with Gapps installed compared to custom roms without Gapps, but the process typically only involves dealing with the preinstalled Gapps and Google updates. Most of the time you only need to follow the GMS PROBLEMS steps outlined in the guide when running into problems.
If you debloat the Play Store and then later reinstall it, make sure you do not have FakeStore installed, Play Store will not go back in with FakeStore installed!
microG DroidGuard Helper is only required if you want to use applications that require SafetyNet or to test DroidGuard!
The microG UnifiedNlP package at this point in time is not supported in OxygenOS, for this reason the XposedGmsCoreUnifiedNlP Xposed module needs to be installed!
Open Xposed and install XposedGmsCoreUnifiedNlP, go to the Modules section, check the module to enable it!
Android 7 (or later) needs to have microG installed to the /system.
If you use the Official microG download FakeStore GmsCore GsfProxy! (It's higly recommened to use the Nanodroid-microG version!)
FakeStore - (Only needed if you're not using the Play Store)
https://github.com/microg/android_packages_apps_FakeStore/releases
GmsCore
https://github.com/microg/android_packages_apps_GmsCore/releases
GsfProxy
https://github.com/microg/android_packages_apps_GsfProxy/releases
Rename all the APK!
FakeStore.apk
GmsCore.apk
GsfProxy.apk
Create theses directory names and place the APK in them!
FakeStore
GsfProxy
GmsCore already has a directory in /system/priv-app!
Debloater (Terminal Emulator) places a file .replace in all the /system/priv-app directories that you debloated.
In GmsCore the contents of ".replace" is "Google%Play%Services", so that the Google Play Services apk doesn't populate the directory. If you were to remove or rename ".replace" and rebooted, you would see the actual Google Play Services GmsCore.apk in the directory!
Do not touch these hidden ".replace" files!
Because GmsCore already has a directory in /priv-app, copy the microG GmsCore.apk to your phone with a File Manager that gives you root access to /system/priv-app/GmsCore.
Do not adb push GmsCore.apk in TWRP, it will only get removed when you reboot!
Boot to TWRP and mount the /system read-write.
Use this command to push the directories for FakeStore and GsfProxy. - (FakeStore is only needed if you're not using the Play Store)
Code:
adb push FakeStore /system/priv-app
adb push GsfProxy /system/app
Make sure /system is still mounted in TWRP, then > Advanced > Terminal.
Run these commands to make sure you have the correct permissions! - (FakeStore is only needed if you're not using the Play Store)
Code:
chmod 755 /system/priv-app/FakeStore
chmod 644 /system/priv-app/FakeStore/FakeStore.apk
chown -R root:root /system/priv-app/FakeStore/FakeStore.apk
chmod 755 /system/priv-app/GmsCore
chmod 644 /system/priv-app/GmsCore/GmsCore.apk
chown -R root:root /system/priv-app/GmsCore/GmsCore.apk
chmod 755 /system/app/GsfProxy
chmod 644 /system/app/GsfProxy/GsfProxy.apk
chown -R root:root /system/app/GsfProxy/GsfProxy.apk
Do not update microG through Aurora Store or Yalp Store, only update through F-Droid!
If at any time there are any new updates, you'll need to follow the steps over for adb push, copying GmsCore, and the permissions for FakeStore - GmsCore - GsfProxy! Delete all the old APK first before copying and doing adb push!
If you use the Official microG Open F-Droid, Settings, tap on Repositories and add in the microG repo; https://microg.org/fdroid/repo so you can keep microG updated!
If you use NanoDroid-microG, in F-Droid, Settings, tap on Repositories and add in the NanoDroid-microG repo; https://nanolx.org/fdroid/repo/ so you can keep microG updated!
Unmount the /system read-write and reboot the phone.
MICROG SETUP
Open F-Droid and search for microg. The Network-based Geolocation choices are, Deja VU - MozillaNlPBackend - Local GSM Location. It's good to just install all three, or experiment to see which works best for you, either alone or in combination. For address lookup and to also test Geocoder, install NominatimNlPBackend.
Make sure WiFi, Mobile data, "Location ( Mode - High Accuracy)" are all turned on in the phone before opening microG!
Open microG, you'll notice at the top it says Permission missing, tap on this, tap on the words REQUEST MISSING PERMISSIONS and ALLOW all of them!
If your deodex went successful, or you went with FakeGapps, you should notice at the top System spoofs signature checked.
You should now only see two check marks missing at the bottom for Location backend(s) setup and UnifiedNlP do not have Location to test Geocoder.
Network-based location enabled should be checked if you didn't turn off Location in the Phone Settings.
Make sure Battery optimizations ignored is also checked!
To get Location working properly in microG, under Self-Check tap on Google device registration and toggle it ON.
Google device registration needs to be ON, when signing up or logging into your Account, or the Play Store for the first time, afterwards it can be turned OFF if you don't need Location support! If at any time an application doesn't run, trying turning Google device registration back ON to see if it helps.
Go to the phone Settings > Location and put the Mode on "High Accuracy".
In the "UnifiedNlP Settings" configure the "Network-based Geolocation" backends you just installed!
Under "Address lookup" for the NominatimNlPBackend, tap Choose Nominatim API Server and pick MapQuest! I recommend using MapQuest, you'll need to sign up for a free account at MapQuest to get an API key.
https://developer.mapquest.com/
When you get your key, tap on MapQuest Developer API Key and add it in.
The MapQuest API key only allows 15,000 transactions a month!
MICROG PERMISSIONS
To get UnifiedNlP do not have Location to test Geocoder checked in microG, you need to add these two permissions.
Code:
adb shell
su
pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
After adding the permissions reboot your phone.
If you go into the microG settings before it's updated the Location, you will still see UnifiedNlP do not have Location to test Geocoder unchecked. Go back out of Self-Check and wait a few seconds then check it again, sometimes you need to scroll up and down a few times too. After a few seconds your Location should be updated and everything should be checked.
This time you'll see it says Geocoder provides address resolution from location checked. Also scroll up and down for a few seconds, and this time under UnifiedNlP status you should have 6 sections now checked.
Over a period of time, depending on what you do, you might see UnifiedNlP do not have Location to test Geocoder become unchecked, if this happens just run the permissions over!
I WANT MY GOOGLE & STAY PRIVATE TOO
All of this just depends on your level of privacy and concerns in regards to Google!
If you debloated Chrome, before you can add a Google Account in the phone settings through microG, you need to update Android System WebView!
These steps below are only if you need paid applications through the Play Store! Free and paid applications can also be downloaded through Aurora Store and Yalp Store, F-Droid can only download free applications.
If you want to stay away from Google, you can use your Google Account on either Aurora Store or Yalp Store. Some paid applications with their License Checks might not work without being downloaded through the Play Store, or if the Play Store isn't installed, you'll have to test this out with various applications to see how they work.
Besides paid applications, system applications will also appear through Aurora Store and Yalp Store, so you can limit the time using the Play Store for privacy, and update everything through either Aurora Store or Yalp Store, possibly even paid applications too.
Aurora Store and Yalp Store violates §3.3 of Google Play Terms of Service, so your account could be disabled, but as it's mentioned on the Yalp Store site, they've never heard of any real cases of accounts being disabled.
https://github.com/yeriomin/YalpStore
https://gitlab.com/AuroraOSS/AuroraStore
To make this step of privacy work, you will need to create a Google account for the first time, because if you did it the normal way on your phone, then you have exposed your device, given up your carrier name, mobile or wifi ip address, geo location etc... If you signed up on a computer, depending on what you did, you might of also exposed yourself!
If you want to create your Google account on a computer, be sure to cover your tracks, like using a VPN!
If you need paid applications from the Play Store, create your Google account after you've done all the steps outlined in this guide for privacy!
Before you follow the steps, make sure Location is off, WiFi is off, Mobile Data is off, and switch the sim card! You do not need an active sim card to use the Play Store! With dual sims, deactivate the good one, and activate the dead/spoofed one! Make sure the spoofed sim card is also the sim card set as the default for the Phone, text, mobile data!
Follow these steps even if you are signing up through a computer, to make sure you are ready to sign into the Play Store on your phone you've prepared!
Every time you sign into the Play Store on your device, if you want privacy with as little attention drawn to the account, then you need to always connect to the Play Store with all of the same phone settings, sim card, etc., otherwise you will get a new device added to the account.
Make sure you never sign into a Google account using your real sim, wifi/mobile network IP, or Location on! Anything that can track you, make sure it's spoofed or off!
For the best Privacy use a VPN that does not log, then sign into the Play Store over wifi using this VPN! As an example you can also use some throw away sim card that you paid for by cash that has no trail to you, but remember the Carrier Network does place you locally! If Geo Locality is a concern, use a VPN!
It's also recommended to maintain the same network(s) and GEO location when signing into the Play Store!
If at anytime you want to update, or get more applications, follow the steps over repeating the process!
Here's a break down in the steps! - (1 - 4)
1. You can sign up for the Google account on your computer, then add it into your phone, but don't forget to follow step #2 when you add the account in the device.
2. When signing up or adding your Gmail/Google account on your device, use another sim card in your phone so the mobile network goes through a different carrier, or a spoofed sim card that doesn't work, or wifi over a VPN, Phone, text, mobile data all set on the spoofed sim card, Location is off! Make sure anything that can track you is off or spoofed!
3. If you are either signing up, or logging into your Account on your device, make sure Google device registration is ON in microG! This also needs to be ON the first time you log into the Play Store!
4. When you are done using the Play Store for the first time you can turn Google device registration OFF in microG, if you don't need phone Location! If at any time applications aren't working properly try turning Google device registration ON!
Be careful with the Account and Play Store on the phone, that you don't access either of them with anything that gives up your identity, as you can see there are a few things you could forget!
NANODROID PHONESKY
If at anytime you have problems with the original Play Store, you can get Phonesky.apk from NanoDroid-microG, it's a patched version to work with microG. Download it from Stable Download (Nanolx), it's located in the /system/priv-app/Phonesky directory.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
Copy Phonesky.apk with a File Manager to the Download directory.
Boot to TWRP and mount the /system read-write.
Rename the original Phonesky.apk in /priv-app to keep a backup, also so it won't run. Rename it like; Phonesky.bak - Phonesky.orig
In TWRP copy the Nanodroid version to /priv-app/Phonesky.
In TWRP > Advanced > Terminal, run this command to make sure you have the correct permissions on the Nanodroid version of Phonesky!
Code:
chmod 644 /system/priv-app/Phonesky/Phonesky.apk
Unmount the /system read-write and reboot the phone.
The Nanodroid version of the Play Store is now located in the App Drawer.
If Privacy is a concern, when you are done using the Play Store you can go to Settings > Apps > Application List > Google Play Store - Tap Disable to stop the Play Store from running, then you can Enable it later when you want to run it again! You do not need to debloat the Play Store! You can also tap Permissions and disable all of them!
Settings > Security & lock screen > Apps with usage access > Google Play Store > Permit usage access - Disable this for better privacy!
That's all there is to accomplishing microG on OxygenOS, Stock Android ROMs, and Custom ROMs!
>
>
>
If this post helped you in any way, please press the THANKS button!
Thank you for your time and effort with this detailed tutorial.
I understand every step except for the VDEX bit. Can I bypass this part? I don't use Playstore but one app (BT sport) after some updates refuses to work without it. Even on Lineage microG.
bluegrass55 said:
Thank you for your time and effort with this detailed tutorial.
I understand every step except for the VDEX bit. Can I bypass this part? I don't use Playstore but one app (BT sport) after some updates refuses to work without it. Even on Lineage microG.
Click to expand...
Click to collapse
BT Sport wants the Play Store in order to work?
For VDEX I mentioned it before, but this time I changed it to make it more noticeable.
Look back up at ---> DEODEX OR FAKEGAPPS
What computer OS you running?
DoR3M3 said:
BT Sport wants the Play Store in order to work?
For VDEX I mentioned it before, but this time I changed it to make it more noticeable.
Look back up at ---> DEODEX OR FAKEGAPPS
What computer OS you running?
Click to expand...
Click to collapse
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Excelent guide, I run microg about 3,5 years, now with oxygen the only thing i miss is signature spoofing but I didn't have any problem except of some messages eg when opening tapatalk. Is there any way to deodex on macos?
Sent from my ONEPLUS 5T
vagkoun83 said:
Excelent guide, I run microg about 3,5 years, now with oxygen the only thing i miss is signature spoofing but I didn't have any problem except of some messages eg when opening tapatalk. Is there any way to deodex on macos?
Sent from my ONEPLUS 5T
Click to expand...
Click to collapse
Everything is mentioned in these steps, please look them over again, you can always use FakeGapps...
DEODEX OR FAKEGAPPS
VDEXEXTRACTOR
I made some changes to make it clearer. But if you went to the vdexExtractor Github, you would of seen mention of MacOS if you want to compile and DEODEX instead of FakeGapps.
bluegrass55 said:
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Click to expand...
Click to collapse
Play Store is mentioned in the Guide, so if you need it, just follow these steps;
I WANT MY GOOGLE & STAY PRIVATE TOO
I would also suggest filing an Issue on the microG Github, maybe the microG DEVs will have some suggestions/ideas on how to do this without the Play Store;
https://github.com/microg/android_packages_apps_GmsCore
bluegrass55 said:
Windows 8.1 Pro.
Yes BT sport needs to feel the presence of Playstore to work. Even though I'm not logged into Playstore, full restriction using XprivacyLua and blocked internet access via AFWall+. When on dedicated Lineage 15.1 microG it used to work. But not anymore.
Click to expand...
Click to collapse
Managed to install this via the Fake Gapps route but it failed the Signature Spoofing check via the app from Fdroid. Flashed the NanoDroid Patcher which fixed it.
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-19.1.1.20181103.zip
For some strange reason I still have Faceunlock function even with all Google stuff uninstalled.MicroG self test has everything ticked and Fdroid is working.
This was a test run on an already debloated stock 5.1.6 ROM. Will try again on a later date with clean fresh ROM as recommended. Looked into the Deodex thing again but still non the wiser on how to achieve it.
bluegrass55 said:
Managed to install this via the Fake Gapps route but it failed the Signature Spoofing check via the app from Fdroid. Flashed the NanoDroid Patcher which fixed it.
https://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-19.1.1.20181103.zip
For some strange reason I still have Faceunlock function even with all Google stuff uninstalled.MicroG self test has everything ticked and Fdroid is working.
This was a test run on an already debloated stock 5.1.6 ROM. Will try again on a later date with clean fresh ROM as recommended. Looked into the Deodex thing again but still non the wiser on how to achieve it.
Click to expand...
Click to collapse
The 5.1.6 OTA is available for me to download, and I checked it, and it's VDEX!
Do you remember when you were installing the NanoDroid-patcher, at the beginning it said "Deodex"?
See the attached image where it says; services.jar status: VDEX this is on 5.1.5 & 5.1.6 showing that the ROMs have not be DEODEX yet. It needs to say; services.jar status: DEODEX in order for the Nanodroid-patcher to work...
I noticed too that the Signature Spoofing Checker shows "Disabled" in 5.1.6. microG shows the support, so it appears that the "Signature Spoofing Checker" has a bug and I'll remove it from the post until it can be fixed.
BT Sports is complaining about the Google Play Services, which is not the Play Store. So as I mentioned, just follow the last step of the Guide for the Play Store and see if BT Store works, and if not, make the Issue at the microG GitHub for help.
OB19 deodex possible?
deszczuXS said:
OB19 deodex possible?
Click to expand...
Click to collapse
Did you read the guide?
This is a microG guide for Android not just Oxygen...
But there are slight differences between ROMs, all you have to do is avoid all the OxygenOS parts for Android.
FakeGapps isn't supported in PIE, so if you use PIE then you have to DEODEX, otherwise you can use FakeGapps.
DoR3M3 said:
The 5.1.6 OTA is available for me to download, and I checked it, and it's VDEX!
Do you remember when you were installing the NanoDroid-patcher, at the beginning it said "Deodex"?
See the attached image where it says; services.jar status: VDEX this is on 5.1.5 & 5.1.6 showing that the ROMs have not be DEODEX yet. It needs to say; services.jar status: DEODEX in order for the Nanodroid-patcher to work...
I noticed too that the Signature Spoofing Checker shows "Disabled" in 5.1.6. microG shows the support, so it appears that the "Signature Spoofing Checker" has a bug and I'll remove it from the post until it can be fixed.
BT Sports is complaining about the Google Play Services, which is not the Play Store. So as I mentioned, just follow the last step of the Guide for the Play Store and see if BT Store works, and if not, make the Issue at the microG GitHub for help.
Click to expand...
Click to collapse
Thanks for the detailed reply.
Don't remember if it said "Deodex" at the beginning but about to have another ago as the phone is bootlooping. Using the Terminal Debloat I removed all the Google stuff but for some reason Google Services Framework and Google One Time Init were still was showing up in the system. Used Titanium, System Uninstall app and Root Browser to remove but without luck. Changed their permissions but ended up in bootloop.
bluegrass55 said:
Thanks for the detailed reply.
Don't remember if it said "Deodex" at the beginning but about to have another ago as the phone is bootlooping. Using the Terminal Debloat I removed all the Google stuff but for some reason Google Services Framework and Google One Time Init were still was showing up in the system. Used Titanium, System Uninstall app and Root Browser to remove but without luck. Changed their permissions but ended up in bootloop.
Click to expand...
Click to collapse
After a second attempt and reading the guide more carefully with fresh clean stock ROM have managed to do this. The only issue is these remaining Google things which were also present on my previous attempt even though I got rid of them with Terminal Debloat.
Regarding the BT sports app if I want to use it then microG isn't the way to go. It was a free offer but don't use it that much.
bluegrass55 said:
After a second attempt and reading the guide more carefully with fresh clean stock ROM have managed to do this. The only issue is these remaining Google things which were also present on my previous attempt even though I got rid of them with Terminal Debloat.
Regarding the BT sports app if I want to use it then microG isn't the way to go. It was a free offer but don't use it that much.
Click to expand...
Click to collapse
Try not to double post to keep things together...
I went back and edited the post over, with greater details, explaining, that if you Debloat and still see stuff in the system or app drawer, that is because of updates, but now all of these apps can be uninstalled, and that is what you do, manually uninstall them all from the Settings or App Drawer, it's also a reason for trying to do all this on a Clean ROM with no updates, otherwise you deal with this next.
Also for BT Sport, run it and set it all up on Clean Stock Oxygen first, then debloat next. I did mention that if someone wants to keep any Gapps, to run them first before debloating. Hopefullly doing this, it will then run with microG, but if not, I highly recommend making a bug report at the microG Github;
https://github.com/microg/android_packages_apps_GmsCore
As far as the Nanodroid-Patcher, if you did not DEODEX the rom, I have no idea how that managed to work, but I'm assuming it just did a little bandaid on the system is all, which helped a little, but wasn't a real complete patch. So for any concerns questions, problems or help with that, please post and ask Setialpha;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
P.S. As far as the DEODEX goes it's very simple, it only take a few minutes, the biggest issue would be for people who have never compiled before, understanding and getting that setup on their box/computer, but in Linux compiling is really easy. Once vdexExtractor is built, all you have to do is run a few DEODEX commands and install the Nanodroid-patcher...
DoR3M3 said:
Try not to double post to keep things together...
I went back and edited the post over, with greater details, explaining, that if you Debloat and still see stuff in the system or app drawer, that is because of updates, but now all of these apps can be uninstalled, and that is what you do, manually uninstall them all from the Settings or App Drawer, it's also a reason for trying to do all this on a Clean ROM with no updates, otherwise you deal with this next.
Also for BT Sport, run it and set it all up on Clean Stock Oxygen first, then debloat next. I did mention that if someone wants to keep any Gapps, to run them first before debloating. Hopefullly doing this, it will then run with microG, but if not, I highly recommend making a bug report at the microG Github;
https://github.com/microg/android_packages_apps_GmsCore
As far as the Nanodroid-Patcher, if you did not DEODEX the rom, I have no idea how that managed to work, but I'm assuming it just did a little bandaid on the system is all, which helped a little, but wasn't a real complete patch. So for any concerns questions, problems or help with that, please post and ask Setialpha;
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
P.S. As far as the DEODEX goes it's very simple, it only take a few minutes, the biggest issue would be for people who have never compiled before, understanding and getting that setup on their box/computer, but in Linux compiling is really easy. Once vdexExtractor is built, all you have to do is run a few DEODEX commands and install the Nanodroid-patcher...
Click to expand...
Click to collapse
I removed the remaining Google stuff using Root Browser but after reboot it resulted in Bootloop.
After any ROM install I never used to allow data access till Xprivacy Lua & AFWall+ were up and running. But for some reason this phone (unlike my Nexus 5) doesn't like Xposed installed directly from TWRP. So I have to allow data and install directly via Xposed Installer. I think the best route is the Deodex way but I have tried looking for guide without success. It's really annoying.
bluegrass55 said:
I removed the remaining Google stuff using Root Browser but after reboot it resulted in Bootloop.
After any ROM install I never used to allow data access till Xprivacy Lua & AFWall+ were up and running. But for some reason this phone (unlike my Nexus 5) doesn't like Xposed installed directly from TWRP. So I have to allow data and install directly via Xposed Installer. I think the best route is the Deodex way but I have tried looking for guide without success. It's really annoying.
Click to expand...
Click to collapse
To begin with, I edited over the "DEODEX OR FAKEGAPPS" section, "Signature Spoofing Checker" is a BUG, so forget it saying disabled, FakeGapps is working, so use FakeGapps and you are good to go!
As far as everything else, if you follow the GUIDE 100% EXACTLY IT WORKS! I've done this for almost a year on 3 devices so far, and I just did it on 5.1.5 and 5.1.6 without any problems!
You must follow the guide, do not divert from it, like how you used Root Browser as example, you don't need to do this, and that means after the OTA with 5.1.6, the OTA update for 5.1.6 should of wiped your phone clean, then you start from there.
Personally, after the 5.1.6 OTA update, I booted into TWRP and made a BACKUP, then if you mess up, you wipe everything, Dalvik, cache, system, vendor, data and then RESTORE the backup...
P.S. I am now going to start out on 5.1.6 and do the entire Guide, then I'll come back and post the images of 5.1.6 so you'll see it was done with success...
DoR3M3 said:
To begin with, I edited over the "DEODEX OR FAKEGAPPS" section, "Signature Spoofing Checker" is a BUG, so forget it saying disabled, FakeGapps is working, so use FakeGapps and you are good to go!
As far as everything else, if you follow the GUIDE 100% EXACTLY IT WORKS! I've done this for almost a year on 3 devices so far, and I just did it on 5.1.5 and 5.1.6 without any problems!
You must follow the guide, do not divert from it, like how you used Root Browser as example, you don't need to do this, and that means after the OTA with 5.1.6, the OTA update for 5.1.6 should of wiped your phone clean, then you start from there.
Personally, after the 5.1.6 OTA update, I booted into TWRP and made a BACKUP, then if you mess up, you wipe everything, Dalvik, cache, system, vendor, data and then RESTORE the backup...
P.S. Look at the time of this post, I am now going to start out on 5.1.6 and do the entire Guide, then I'll come back and post the images of 5.1.6 so you'll see it was done with success... BRB
Click to expand...
Click to collapse
Thank you. Looking forward to it. Will attempt again during weekend. I formatted device and installed stock 5.1.6 so no OTA.Don't want to give up especially as you've gone to some effort.
bluegrass55 said:
Thank you. Looking forward to it. Will attempt again during weekend. I formatted device and installed stock 5.1.6 so no OTA.Don't want to give up especially as you've gone to some effort.
Click to expand...
Click to collapse
By the way, the apps you debloat, that ended up getting updates, now appear to you as user installed apps with the ability to uninstall them in the Settings or the App Drawer is what I meant to say, which I'll add that in. So since they turn into user installed apps, that's why you don't need anything to uninstall them...
P.S. @bluegrass55 Sorry it took longer then expected, got tied up a bit with some things, anyhow it's all done and as I mentioned before FakeGapps works fine in 5.1.6, it's just a bug with the Signature Spoofing Checker, so ignore it. I did a DEODEX on my phone for 5.1.6 and here's the screen shots!
I made some changes to the post, so be sure to read it all over, and follow it step by step exactly! If you deviate just a little, it's enough to screw up the entire process and you'll have to start over, it's that picky!
P.S. I went back looking over your replies and you mentioned Xposed through TWRP, and I never mentioned installing Xposed this way. Please be sure to follow the guide and use the Magisk Module for Xposed. I'd also stick to 5.1.5, 5.1.6 hasn't been Officially released yet, just a partial rollout.
Please ignore my last message. Couldn't resist doing it again ( don't want to be defeated). Have Decrypted phone to see if it makes any difference.
bluegrass55 said:
Please ignore my last message. Couldn't resist doing it again ( don't want to be defeated). Have Decrypted phone to see if it makes any difference.
Click to expand...
Click to collapse
Re did the install for the 4th time and wow. Phone runs so much better.
Just two questions.
1- Using Root Browser I notice that GooglePackageInstaller.apk is still present is system-priv. Since it's not included in the Debloat list am I right to assume it should be in the system?
2- Face Unlock function is still present and works. Since it needs Gapps to work does it mean I've missed something?I have checked several times and all the items in the Debloat list have been removed.

HOW TO: Turn Nvidia Shield into Portable Stadia Device

Full Disclosure: I'm an Android development scrub, but I'm pretty familiar with flashing various ROMs, kernels, etc. I have long since moved on from the Nvidia Shield Tablet as a daily driver, but I had a custom 3D printed mount for the tablet and controller (this one: https://www.shapeways.com/product/WFSFW85NB/nvidia-shield-2015-controller-nvidia-shield-tabl )that is perfect for portable gaming. Enter Stadia, with all it's flaws, I wanted to put together a quick how-to to save some people time that want to do something similar. There are probably easier ways to do this, but this is what worked for me.
The end goal is to follow the XDA Stadia guide, but I ran into a few issues along the way: https://www.xda-developers.com/enable-google-stadia-any-android-smartphone/
If you already have Magisk and MagiskHide Props Config enabled and working, the guide above is all you need (except for maybe Step 8)
Step 1) Get a custom ROM flashed that still has support for Nvidia software. This is probably only important if you plan to use the Shield controller, though. I used this one: https://forum.xda-developers.com/sh...rom-hyperstock-mra58k-shield-k1-v1-5-t3522897
Step 2) Make sure that Magisk is working and install the MagiskHide Props Config module from within Magisk Manager
Step 3) Verify adb tablet connectivity 'adb devices' and enter a shell 'adb shell'
Step 4) At this point, you want to go through the MagiskHide Props Config text menu by entering 'props' at the shell. However, Props Config requires busybox, and it recommends busybox by osm0sis as a download in Magisk Manager, but I could never get it to detect busybox. Spent a lot of time on this, and the best I could tell from Google is that the ROM debloater was somehow interfering with Magisk busybox, but YMMV. If you don't get this error in your ROM, skip ahead to step 7.
Step 5) Since the Busybox by osm0sis Magisk Module didn't work, I installed one of the busybox implementations on the App Store: https://play.google.com/store/apps/details?id=stericson.busybox
Step 6) Once you open the app, it will ask you to install, but warns you that without the pro version, the busybox install won't survive a reboot. That was fine for me as I just wanted to see if MagiskHide Props Config would work, and it did. Now I could move on to running the script by 1) 'adb shell' and 2) 'props'
Step 7) For this step, the XDA guide works pretty well. The only change is that 'add/edit custom props' was option 4, not 5 as it indicates in the guide, but YMMV: https://www.xda-developers.com/enable-google-stadia-any-android-smartphone/
Step 8) Next major problem -- after you reboot, you will get a constant window notification that "Nvidia Gamecast Service has stopped" and this makes the tablet entirely unusable. The solution is to disable the app with adb and reboot. Once again, connect the shield to a laptop, enter the adb shell, and then disable this service with the following command in adb shell: "adb shell pm disable-user --user 0 com.nvidia.nvgamecast". After you disable, make sure to reboot your tablet.
And that's it. I imagine the Venn Diagram of people that have an Nvidia Shield Tablet + an Nvidia Shield Controler + Stadia is probably quite small, but this was enough for me to dust it off and get some new life out of it.
Wow thank you for this guide drowd !
Followed this guide to the T.
Except Step 8). Damn, getting past that "Gamecast has stopped" message took a lot of patience. My device wouldn't detect since "USB Debugging" wasn't turned on. Took a ton of super fast triple taps to enable developer options, then go in there, turn on usb debugging and then "Allow this device" to connect. Man... phew. Finally got my laptop to detect the device, and your command did the trick after.
In recovery mode, it complained that the "pm" command was not found. How did you get this working without turning on USB Debugging ?
Anyway, I thought I was part of that Venn Diagram that you mention, but, I just realized that I had cancelled my Stadia Pro, and I have no other games on there, so..... I have no idea if this worked, but just wanted to say, THANKS !
Oh, hmmm, now that I think about it, it's possible I forgot to include that as one of the steps, I think because I had already enabled USB debugging in an earlier step, but I should probably modify the guide to say this!
And you are right! Those triple taps required in Step 8 were awful, took quite a bit of patience on my end as well.
I think the easier method (and the route I took on my Shield TV) is to install the custom APK, and run stadia in desktop mode. This still feels very clunky to me compared to the Stadia app, but it works just fine. Hopefully they continue to open up support though.
Also, your Stadia Pro sub might not be current, but they are giving 2 months of Pro away for free, as well as opening up the free tier as well! So check that out, if you haven't already.

Do we need proper root and custom roms for this device

Okay let me start by saying this " This device has potential " but we need some one to help unleash it
I bought this mobile a week ago and every day I cry myself to sleep regretting for opting this device and adding fuel to the fire they released the M31 with better camera and a massive battery
Do not get me wrong its has good display, nice camera and a battery that lasts almost a day. But performance wise it has been a disaster , at this price range there are other device that are really super at their performance
I tried playing pubg on this and multi task and it has been a nightmare
SO WHAT NOW
Looking into the device threads and activity and it only being a few months old , I hope that some dev will take a little interest and get us some custom roms and proper root
SO DO WE NEED TO ROOT AND CUSTOM ROMS
HELL YEAH
Reason
So i kept checking all the device settings and changing a few hoping to improve performance and battery and in the process i used an app called " ICEBOX " set it up via adb and BOOM
PUBG ran Butter smooth on HDR and high fps settings
Multi tasking was good
Battery lasted for about 36 hours ( Depends and may vary on your personal usage )
imagine what else a good custom rom can do
And then i thought may be this device hardware has been burdened with all this bloatware running in background and crappy settings and performance regulating code stuff
So with a good custom rom may be this device would get a max performance boost and other tweak stuff
I HAVE SEEN Developer ACTIVITY FOR SOME SAMSUNG DEVICES AND YOU KNOW there has been a very little hope
Can you elaborate which settings you changed and what commands you used for installing icebox
Sure
Heads up
1. You need to have the pro version to freeze more than 10 apps
2. Some of your system settings may stop working or disappear depending on the apps frozen
3. If you wish to uninstall the application you first need to defrost all the apps and then proceed to uninstall
4. some times it requires a reset is required for the app to be uninstalled { I DO NOT KNOW WHY }
Now SETUP PROCESS
just go to this page for the app Dev instructions
https://github.com/heruoxin/Ice-Box-Docs/blob/master/Device Owner (Non Root) Setup.md
1.INSTALL THE ICEBOX APP
2.REMOVE ALL YOUR ACCOUNTS { DISCONNECT G MAIL SAMSUNG WHATS APP AND OTHERS APPS }FOR ACCOUNT SETTINGS
3.HAVE USB DEBUGGING SETUP
4.CONNECT IT TO YOUR PC
4.NOW USE THE CMD
adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver
5.You will receive a prompt saying its activated
Now you can reconnect your accounts and start freezing
Absolutely. OneUI is, in my opinion, more substantial compared to stock in terms of design and usage. However, that experience is bogged down by junk preloaded into devices and poor optimization, despite a setting make specifically for that option. I'd love to have the choice of unlocking and using TWRP to flash custom ROMs specifically designed for this phone. Unfortunately, Samsung has been a b**** about unlocking but maybe we'll find a solution to bypass such measures? If so, that would be incredible and breathe new life into this phone, but I do believe right now we'll have to suffer on OneUI as of this moment.
whiteTee said:
Sure
Heads up
1. You need to have the pro version to freeze more than 10 apps
2. Some of your system settings may stop working or disappear depending on the apps frozen
3. If you wish to uninstall the application you first need to defrost all the apps and then proceed to uninstall
4. some times it requires a reset is required for the app to be uninstalled { I DO NOT KNOW WHY }
Now SETUP PROCESS
just go to this page for the app Dev instructions
https://github.com/heruoxin/Ice-Box-Docs/blob/master/Device Owner (Non Root) Setup.md
1.INSTALL THE ICEBOX APP
2.REMOVE ALL YOUR ACCOUNTS { DISCONNECT G MAIL SAMSUNG WHATS APP AND OTHERS APPS }FOR ACCOUNT SETTINGS
3.HAVE USB DEBUGGING SETUP
4.CONNECT IT TO YOUR PC
4.NOW USE THE CMD
adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver
5.You will receive a prompt saying its activated
Now you can reconnect your accounts and start freezing
Click to expand...
Click to collapse
I am curious what apps did you freeze to get better performance? I don't want to just start freezing apps willy nilly and end up freezing something that glitches out my phone.
Alfalfalaffa said:
I am curious what apps did you freeze to get better performance? I don't want to just start freezing apps willy nilly and end up freezing something that glitches out my phone.
Click to expand...
Click to collapse
am not able to insert screenshots ! whatever you freeze just do not freeze
payment service kgclient app framework it will lock your device ( and you may have to reset to get it back to normal )
Beside i had no issue of device freezing up
ill try to upload the screenshots if possible ( it says bad request in here )
whiteTee said:
Okay let me start by saying this " This device has potential " but we need some one to help unleash it
I bought this mobile a week ago and every day I cry myself to sleep regretting for opting this device and adding fuel to the fire they released the M31 with better camera and a massive battery
Do not get me wrong its has good display, nice camera and a battery that lasts almost a day. But performance wise it has been a disaster , at this price range there are other device that are really super at their performance
I tried playing pubg on this and multi task and it has been a nightmare
SO WHAT NOW
Looking into the device threads and activity and it only being a few months old , I hope that some dev will take a little interest and get us some custom roms and proper root
SO DO WE NEED TO ROOT AND CUSTOM ROMS
HELL YEAH
Reason
So i kept checking all the device settings and changing a few hoping to improve performance and battery and in the process i used an app called " ICEBOX " set it up via adb and BOOM
PUBG ran Butter smooth on HDR and high fps settings
Multi tasking was good
Battery lasted for about 36 hours ( Depends and may vary on your personal usage )
imagine what else a good custom rom can do
And then i thought may be this device hardware has been burdened with all this bloatware running in background and crappy settings and performance regulating code stuff
So with a good custom rom may be this device would get a max performance boost and other tweak stuff
I HAVE SEEN Developer ACTIVITY FOR SOME SAMSUNG DEVICES AND YOU KNOW there has been a very little hope
Click to expand...
Click to collapse
#####################################################################
Really my language is full Spanish, so forgive me if I write something wrong.
I believe that a root is not necessary to improve the SM-A515F, use the same method of ADB, uninstall garbage apk, gaining space and battery improvement. So until now I have a mobile, super optimized and they could even remove 100% bixby those who do not like that apk, but the method is by ADB, with parameters like:
pm uninstall -k --user 0 'com.android.stk' (this apk is rubbish, and with ADB you can delete it and others more ...)
So really, my opinion is that the phone is super stable and has a good performance. The only thing I found, would be to improve the operation of Dolby and put a better audio with the two speakers, otherwise everything is perfect.
As for your suggestion i looked into this guide of de-bloating bloatware and i found two adb commands
1. first one would be (as you suggested) " adb shell pm uninstall -k --user 0 "
This command does not really uninstall any apps from the storage but it makes it unavailable for the " User 0 "
I used this method and and i found some services running background despite uninstalled ( Dev Options > Running Services )
Apps like ant hal , appstore , device care , wellbeing Hiya .
2. The Second command would be " adb shell pm disable-user --user 0 " Where as this command disables the apps but will still be listed in your apps list " DISABLED "
Here i found that the "device care" and " storage booster " were force enabling some times ( But not all the other apps which i have disabled )
So i think that disable adb cmd would do be better than uninstall adb cmd
-----------------[Adb Cmd vs IceBox]----------------------------------------------------------------------------------
If you are going to use " disable " or " unistall " cmds and if your device goes crazy you can revert it either by factory reset or using cmds " adb shell pm enable "/ " adb shell cmd package install-existing "
Comparing this to "Icebox" 1. Its Easy setup
2. Need pc just for the initial setup
3. Can enable and disable just by selecting and removing them from the list
Again you will have ICEBOX running constantly in the back ground
As for stability it pretty much good , Optimization standards may differ for user to user and the same goes for the performance
so would it be the unarguable
Root alone cannot suffice better performance its the Custom Rom that does all the magic (Again Opinions may be )
I am just frustrated with the amount of bloatware it has and its mediocre performance for its price tag
-----------------------------------------------------------------------------------------------------------------------------------------
Links for " debloat list" and "enable or uninstall adb cmds" ( All thanks to them ) and these are the same apps which i froze in icebox @ Alfalfalaffa user
https://forum.xda-developers.com/galaxy-a50/how-to/heavy-debloat-ui-lag-ota-t3929189
https://forum.xda-developers.com/galaxy-a50/how-to/debloat-phone-uninstall-root-ota-t3964080
disabled more than 250 apk applications via adb
Thailand
2020-03-22
10
A515FXXU3ATC3
A515FOLM3ATC3
Download from the android site platform-tools (adb) you should get a folder with files, put in the root of the disk.
hold shift and right-click in the adb folder select launch powershell
enable usb debugging on the phone
. \\ adb (start)
. \\ adb devices (connected)
. \\ adb shell pm list packages -d (which apk are disabled)
. \\ adb shell pm list packages (which apk are installed)
(example, delete data from apk)
. \\ adb shell pm clear --user 0 com.microsoft ...
(example, remove completely apk)
. \\ adb shell pm uninstall --user 0 com.microsoft ...
(example, delete apk but leave data)
. \\ adb shell pm uninstall -k --user 0 com.microsoft ...
(example, install apk (return as it was))
. \\ adb shell cmd package install-existing com.microsoft ...
(example, disable apk)
. \\ adb shell pm disable-user com.microsoft ... (for all)
. \\ adb shell pm disable-user --user 0 com.microsoft ... (with you)
I personally used
. \\ adb shell pm clear --user 0 com.microsoft ...
. \\ adb shell pm uninstall --user 0 com.microsoft ...
(com.microsoft ... this is an apk example, everywhere)
total. the phone was fully charged after the procedures. Installed programs from fdroid. put on a shelf. exactly a month has passed !!! Now the charge is 52% !!! consumption a little more than 1% per day in a calm state !!! fantastic!!!
I don’t use the phone. I need a root. I need to install a firewall. so that the system and applications that do not need to, do not know about the existence of the network. This is the main reason for getting root should be for everyone. the rest is secondary. give the root. you are welcome. Sorry for my English. all health and good mood!
GuestD2795 said:
Sure
Heads up
1. You need to have the pro version to freeze more than 10 apps
2. Some of your system settings may stop working or disappear depending on the apps frozen
3. If you wish to uninstall the application you first need to defrost all the apps and then proceed to uninstall
4. some times it requires a reset is required for the app to be uninstalled { I DO NOT KNOW WHY }
Now SETUP PROCESS
just go to this page for the app Dev instructions
https://github.com/heruoxin/Ice-Box-Docs/blob/master/Device Owner (Non Root) Setup.md
1.INSTALL THE ICEBOX APP
2.REMOVE ALL YOUR ACCOUNTS { DISCONNECT G MAIL SAMSUNG WHATS APP AND OTHERS APPS }FOR ACCOUNT SETTINGS
3.HAVE USB DEBUGGING SETUP
4.CONNECT IT TO YOUR PC
4.NOW USE THE CMD
adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver
5.You will receive a prompt saying its activated
Now you can reconnect your accounts and start freezing
Click to expand...
Click to collapse
Hello! PLEASE, I need help - ICEBOX it is a MUST for me.
I have A71 with the latest Firmware ( september U.I. 2.1)
I sign out from all accounts and I delete fingerprint and the login passord, I uncheck or unninstall all ap with admin permission, I check the debug USB in developer menu ....but I get this error:
PS C:\adb> adb shell dpm set-device-owner com.catchingnow.icebox/.receiver.DPMReceiver
java.lang.RuntimeException: Can't set package ComponentInfo{com.catchingnow.icebox/com.catchingnow.icebox.receiver.DPMReceiver} as device owner.
at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:204)
at com.android.commands.dpm.Dpm.onRun(Dpm.java:115)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:56)
at com.android.commands.dpm.Dpm.main(Dpm.java:41)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:342)
P.S. I tried even with clean fw after reset the mobile and I get the same error again and again!
Hello,
You can try this
Note:
1. Your phone Unlock Bootloader >> Click here for tutorial Unlock Bootloader
2. TWRP >> Click here to install TWRP for A51
3. Making GSI_Flasher >> Click here how to make GSI Flasher
Link download
Havoc-OS-v3.12-20201230-Official-GApps-arm64-ab.img.xz
All files >> Click here
My thread
https://forum.xda-developers.com/t/...al-android-10-for-samsung-galaxy-a51.4212741/
GuestD2795 said:
Okay let me start by saying this " This device has potential " but we need some one to help unleash it
I bought this mobile a week ago and every day I cry myself to sleep regretting for opting this device and adding fuel to the fire they released the M31 with better camera and a massive battery
Do not get me wrong its has good display, nice camera and a battery that lasts almost a day. But performance wise it has been a disaster , at this price range there are other device that are really super at their performance
I tried playing pubg on this and multi task and it has been a nightmare
SO WHAT NOW
Looking into the device threads and activity and it only being a few months old , I hope that some dev will take a little interest and get us some custom roms and proper root
SO DO WE NEED TO ROOT AND CUSTOM ROMS
HELL YEAH
Reason
So i kept checking all the device settings and changing a few hoping to improve performance and battery and in the process i used an app called " ICEBOX " set it up via adb and BOOM
PUBG ran Butter smooth on HDR and high fps settings
Multi tasking was good
Battery lasted for about 36 hours ( Depends and may vary on your personal usage )
imagine what else a good custom rom can do
And then i thought may be this device hardware has been burdened with all this bloatware running in background and crappy settings and performance regulating code stuff
So with a good custom rom may be this device would get a max performance boost and other tweak stuff
I HAVE SEEN Developer ACTIVITY FOR SOME SAMSUNG DEVICES AND YOU KNOW there has been a very little hope
Click to expand...
Click to collapse
Custom ROM for A51 >> https://forum.xda-developers.com/t/rom-a515x-refinedui-v1-0-oneui2-1-android10.4220373/

Debloat Samsung A51 (No root) and get crazy performance!

Hello fellow A51 users today i want to share with you a debloat guide so you can get the max performance out of you new smartphone without Samsung clutter.
All credits goes to Khlam and his Samsung Oneui debloat list:
https://github.com/khlam/debloat-samsung-android
I tested it on my device with uninstalling the complete list and it works great.
You do lose some functionality so be careful with what you delete this does only delete the apps one your install of the OS doing a factory reset will reset all apps back to normal this will not void any warranty so i suggest making a backup and trying it on a fresh install and see if you like it.
This guide will strip Oneui to its bare bones so its not for everyone but if you like speed over functionality than give it a try.
Guide:
The following instructions assumes you are familiar with using a command-line interface.
1. On your phone, enable Android's "Developer Options"
2. In "Developer Options", turn on "USB Debugging"
3. On your computer, download Android SDK Platform-Tools for your OS.
https://developer.android.com/studio/releases/platform-tools
4. Extract Android SDK Platform-Tools and start a command-prompt/shell session in the extracted folder's directory.
(The way i do this is putting the platform tools folder in My Documents and en opening the folder then type cmd in the navigation bar and hit enter this will open a command prompt in the folder directory.)
5. Connect your Samsung Android phone to your computer with USB debugging enabled. Verify that adb sees your device and the daemon is running with the following command
adb devices
You should see the device name listed as a "device".
At this point your device should prompt you to accept USB debugging from your computer. Tap "Allow".
6. Enter your device's shell with the following command: adb shell
Once in the device's shell, copy and paste all desired commands from:
https://raw.githubusercontent.com/khlam/debloat-samsung-android/master/commands.txt
(What i do is making a notepad file and copying the whole list in notepad file removing the spaces then copy and paste the whole list in the command prompt.)
Let the script run and when the command prompt reaches the last command you only have to hit enter ones the finish the script.
Thats it you now have a fast bare bone debloated A51 you can close the command prompt and disconnect your phone from your pc.
Enjoy if this all sounds to difficult i suggest you read up on the following articles/guides
https://github.com/khlam/debloat-samsung-android
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
They explain it in more depth if you have any questions please put them bellow and im happy to help.
Zoqy :laugh:
Amazing, was looking for this.
Thanks.
very cool... thx for sharing this
I'm not able anymore to access "Sound quality and effects" in the settings.
Anyway to reinstall?
I found out what the solution was.
So when deleting
pm uninstall -k --user 0 com.samsung.aasaservice
And reinstalling
pm install-existing --user 0 com.samsung.aasaservice
How to fix sms app?
pm install-existing --user 0 com.samsung.android.messaging
it's not helping
senq87 said:
How to fix sms app?
pm install-existing --user 0 com.samsung.android.messaging
it's not helping
Click to expand...
Click to collapse
The ADB-Command for reinstalling is:
adb shell pm enable com.samsung.android.messaging
I get a popup message when trying to edit a picture from the gallery app. It asks to download a picture editor but when i click on download it says "no apps availbe to do this action".
edit: got it myself. this fixed it:
pm install-existing --user 0 com.sec.android.mimage.photoretouching
Just found another one today:
upday for Samsung - Zeropage
a51:/ $ pm uninstall -k --user 0 de.axelspringer.yana.zeropage
Success
tried, broke, fixed
ran this script on the sm-a515u verizion. Lost signal, data, and my nova google companion (no edge swipe). Factory reset works as normal again.
this deletes pretty much everything on your phone, including things like image cropping, youtube or the "find my galaxy" thing
some of these functions are much needed so would sort out whatever you need from that list before attempting to do that
I only deinstalled what I really didn't need, what was about 20 apps and services
seems that one of these packages depends on calling and texting. i'm on a spectrum mobile device and after running the entire script i can use mobile data but can't make or recieve phone calls and text messages. of course a factory reset does the trick but i wonder what app is causing this?
EDIT: i finally got around to troubleshooting it. it was most likely these services i had to re-enable again (through adb shell cmd package install-existing <package name>:
com.sec.ims
com.sec.imslogger
com.sec.imsservice
I am getting frequent reboots and will have to factory reset.
FBK2904 said:
The ADB-Command for reinstalling is:
adb shell pm enable com.samsung.android.messaging
Click to expand...
Click to collapse
This did not help, messaging app crashed. But text message retrieval works.
---------- Post added at 20:26 ---------- Previous post was at 20:23 ----------
AOD no longer works.
Frau Son said:
this deletes pretty much everything on your phone, including things like image cropping, youtube or the "find my galaxy" thing
some of these functions are much needed so would sort out whatever you need from that list before attempting to do that
I only deinstalled what I really didn't need, what was about 20 apps and services
Click to expand...
Click to collapse
would you share those 20 apps and services?
settings not opening. what is the solution to that?
albusdanbledore said:
would you share those 20 apps and services?
Click to expand...
Click to collapse
did you get it ?
hhniloy said:
settings not opening. what is the solution to that?
Click to expand...
Click to collapse
Same here, after Update to Android R (11). My Settings still crash. I reinstalled the bloated s***. then settings works again. But I will try which app it caused.
albusdanbledore said:
would you share those 20 apps and services?
Click to expand...
Click to collapse
for me exactly the same question. Please answer.
I suggest using this debloater instead. More recent, covers many more things (not just Samsung specific) and every single setting is documented and tested. The Samsung Debloater uninstalls things that are better left alone if you don't want an unstable device.
chrisimre747 said:
Same here, after Update to Android R (11). My Settings still crash. I reinstalled the bloated s***. then settings works again. But I will try which app it caused.
Click to expand...
Click to collapse
The app which cause the crash is:
com.osp.app.signin
Tested on my Galaxy A51.

Categories

Resources