Database Develop

How to Disable Xposed on Lollipop when stuck in Bootloop

I have xposed running on my Nexus 5 lollipop 5.0.1.
After downloading and enabling a couple modules my phone is now stuck in a bootloop.
I tried clearing dalvik and cache it didn't help.
Is it possible to disable xposed from recovery?
EDIT: Solved.
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse

Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/xposed/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/xposed/disabled
Click to expand...
Click to collapse
Didn't work. Still stuck in bootloop.

bseos said:
Didn't work. Still stuck in bootloop.
Click to expand...
Click to collapse
what modules you have activated?
or
mv /system/lib/*.*.orig /system/lib/*.*
mv /system/bin/*.orig /system/bin/*

opssemnik said:
what modules you have activated?
Click to expand...
Click to collapse
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled

very good

bseos said:
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...

.Ryker said:
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
Click to expand...
Click to collapse
After disabling it I flashed the new xposed-arm-20150308.zip and installed XposedInstaller_3.0-alpha2.apk (I was on alpha1 previously)
Re-enabled xposed (deleted "disabled" file) and all is working fine now.

This thread definitely either needs to be made a sticky, or the contents needs to be in one of the already made sticky threads IMHO
Cheers
//edit
I tried this out on my phone to test (my xposed stuff is working just fine) but it doesn't seem to have disabled xposed at all?
Ex, app settings still functions (set my play store to be at 480 DPI and it's still opening in 480 DPI as it should...)
I made the necessary file you said with fx file manager, not through TWRP recovery though... I don't think it should make a difference though how I made the file, just that it's there.
Maybe my permissions on the file are messed up, I just thought of that..
//edit 2
Yup my perms were messed up, xposed is now disabled for me. Cheers for the info, now I know what to do when some shady looking module backfires on me lol

Thank you so much!!! This worked perfectly on Sprint LG G3 using Candy5 ROM!! Saved me!!

Just to report that the method failed on a Samsung Galaxy S6 Edge (SM-G925F).
I created succesfully the disabled file, but I was still having bootloops.
So I thought I forgot to set the file to 755, but then TWRP told me:
Code:
Updating partition details...
...done
E: Resource (font)-(fixes) failed to load
Kernel does not have support for reading SELinux contexts.
MTP Enabled
Now I hope to fix everything by reflashing the firmware again...

After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.

Nokiacrazi said:
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Click to expand...
Click to collapse
Delete the "disabled" file in the folder op showed

jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app

Nokiacrazi said:
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf

jkyoho said:
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
Click to expand...
Click to collapse
Thanks, method 2 worked a treat.
For some reason, even though I have root access, it wasn't showing in either root explorer or es file explorer, however, when looking through TWRP file management was all there.

jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...

cybercop007 said:
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
Click to expand...
Click to collapse
If you can't normally boot to system, boot to recovery(twrp or some other custom recovery which has file management function)
Try copy a small file like host or something, paste it the that /data/data/dev.*****installer/conf folder and rename it "disabled".

flashable zip´s

starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
these will be very good to have! thank you!

starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
Thank you!!!

Prevent home button from turning screen on?

I'm trying to find a way to stop the home button from turning on the screen. My wife puts the phone in her purse and I constantly turns the screen on. I read this:
http://android.stackexchange.com/qu...-home-button-from-waking-my-samsung-galaxy-s5
on StackOverflow that had me edit gpio-keys.kl, but it did not work on lollipop. From what I understand the xposed modules don't work at all with lollipop and touchwiz either, so using wanam probably won't work. I have root, so any suggestions would help. Thanks!

shaklee3 said:
I'm trying to find a way to stop the home button from turning on the screen. My wife puts the phone in her purse and I constantly turns the screen on. I read this:
http://android.stackexchange.com/qu...-home-button-from-waking-my-samsung-galaxy-s5
on StackOverflow that had me edit gpio-keys.kl, but it did not work on lollipop. From what I understand the xposed modules don't work at all with lollipop and touchwiz either, so using wanam probably won't work. I have root, so any suggestions would help. Thanks!
Click to expand...
Click to collapse
Wanam actually does work for me. I'm currently on OF2. It also worked on OC4.
Or if you're comfortable decompiling/recompiling you can try: http://forum.xda-developers.com/showthread.php?t=2799050 has it somewhere in there. I haven't tried this mod specifically.
Edit:
[Guide How-To] DISABLE HOME KEY WAKE
This will prevent the Home Key from waking the phone.
android.policy.jar smali edit:
smali/com/android/interal/policy/impl/PhoneWindowManager.smali
.method private isWakeKeyWhenScreenOff(I)Z
Add the new lines in BLUE
Code:
:sswitch_1
move v0, v1
goto :goto_0
[COLOR="Blue"]:sswitch_4
return v1
nop
[/COLOR]
:sswitch_data_0
.sparse-switch
[COLOR="Blue"]0x3 -> :sswitch_4
[/COLOR] 0x18 -> :sswitch_0
0x19 -> :sswitch_0

Thanks! I'll give it a shot

[MODULE] Privileged Permission Whitelist (Oreo)

**** This module is now obsolete as privapp permissions are now granted automatically when systemizing apps with Terminal App Systemizer. Please use that from now on. ****​
In Android 8.0 Oreo, permissions are not automatically granted to system privileged apps. This is automatically done by apps where the root method allows system modifications, but with systemless root that has to be done in a different way.
Therefore, apps systemized into /system/priv-app using App Systemizer or Terminal App Systemizer will not be granted some permissions. All privileged apps must be whitelisted in system configuration files in the /etc/permissions directory.
Entries can either be appended to /etc/permissions/privapp-permissions-platform.xml or separate files can be created for each package; i.e., /etc/permissions/privapp-permisisons-com.package.name.xml. The latter is easier and more modular (pun intended :laugh: ).
This module is more of a template. I've included XML files for BetterBatteryStats, Cerberus, F-Droid Privileged Extension, Greenify and Wakelock Detector Free. Before flashing it, you will want to add or remove XML files according to your needs.
Example XML file:
/etc/permissions/privapp-permisisons-com.package.name.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<permissions>
<privapp-permissions package="com.package.name">
<permission name="android.permission.WRITE_A_SETTING" />
<permission name="android.permission.WRITE_ANOTHER_SETTING" />
</privapp-permissions>
</permissions>
In order to determine what permissions are missing from your systemized app, you can compare the requested permissions and install permissions by running:
Code:
adb shell dumpsys package com.package.name
However, not every permission missing from the install permissions section needs to be granted in this manner. If you're not sure, contact the app developer for clarification.
A better version of this module would generate the permissions configuration XML file without having to get your hands dirty. However, that would require including aapt and I haven't figured out how to do it yet. Perhaps @stangri or @veez21 could help with that.
Download:
Module removed, please use Terminal App Systemizer

RESERVED

yochananmarqos said:
In
In order to determine what permissions are missing from your systemized app, you can compare the requested permissions and installed permissions by running:
Code:
adb shell dumpsys package com.package.name
Click to expand...
Click to collapse
Hi, I'm trying to get FakeGPS to work on Oreo. I think I've done everything correctly, but the app freezes when I try to engage the location.
Below is the output from ADB. Does this looks correct, or do I need further action? Thanks!
Activity Resolver Table:
Full MIME Types:
text/plain:
361e3e2 com.incorporateapps.fakegps/.Maps filter 67f598b
Action: "android.intent.action.SEND"
Category: "android.intent.category.DEFAULT"
Type: "text/plain"
Base MIME Types:
text:
361e3e2 com.incorporateapps.fakegps/.Maps filter 67f598b
Action: "android.intent.action.SEND"
Category: "android.intent.category.DEFAULT"
Type: "text/plain"
Schemes:
geo:
361e3e2 com.incorporateapps.fakegps/.Maps filter 35b935a
Action: "android.intent.action.VIEW"
Category: "android.intent.category.DEFAULT"
Category: "android.intent.category.BROWSABLE"
Scheme: "geo"
Non-Data Actions:
com.htc.laputa.map.action.REVERSE_ADDR_ON_MAP:
361e3e2 com.incorporateapps.fakegps/.Maps filter 7e66705
Action: "com.htc.laputa.map.action.REVERSE_ADDR_ON_MAP"
Category: "android.intent.category.DEFAULT"
android.intent.action.MAIN:
361e3e2 com.incorporateapps.fakegps/.Maps filter 38ce27c
Action: "android.intent.action.MAIN"
Category: "android.intent.category.LAUNCHER"
MIME Typed Actions:
android.intent.action.SEND:
361e3e2 com.incorporateapps.fakegps/.Maps filter 67f598b
Action: "android.intent.action.SEND"
Category: "android.intent.category.DEFAULT"
Type: "text/plain"
Receiver Resolver Table:
Non-Data Actions:
android.intent.action.BOOT_COMPLETED:
6e91373 com.incorporateapps.fakegps/.BootServiceReceiver filter abfc04e
Action: "android.intent.action.BOOT_COMPLETED"
mPriority=999, mHasPartialTypes=false
com.incorporateapps.fakegps.ACTION_STOP:
31c8230 com.incorporateapps.fakegps/.StopButtonListener filter a90d56f
Action: "com.incorporateapps.fakegps.ACTION_STOP"
Service Resolver Table:
Non-Data Actions:
com.incorporateapps.fakegps.STOP:
3ee3ea9 com.incorporateapps.fakegps/.Tasker filter c041f49
Action: "com.incorporateapps.fakegps.STOP"
com.incorporateapps.fakegps.ENGAGE:
3ee3ea9 com.incorporateapps.fakegps/.Tasker filter c910150
Action: "com.incorporateapps.fakegps.ENGAGE"
Key Set Manager:
[com.incorporateapps.fakegps]
Signing KeySets: 67
Packages:
Package [com.incorporateapps.fakegps] (33e5c2e):
userId=10091
pkg=Package{b3773cf com.incorporateapps.fakegps}
codePath=/data/app/com.incorporateapps.fakegps-7O6AqP-HQQ0wLXWBTXyOLw==
resourcePath=/data/app/com.incorporateapps.fakegps-7O6AqP-HQQ0wLXWBTXyOLw==
legacyNativeLibraryDir=/data/app/com.incorporateapps.fakegps-7O6AqP-HQQ0wLXWBTXyOLw==/lib
primaryCpuAbi=null
secondaryCpuAbi=null
versionCode=67 minSdk=8 targetSdk=20
versionName=4.9.6
splits=[base]
apkSigningVersion=1
applicationInfo=ApplicationInfo{cff915c com.incorporateapps.fakegps}
flags=[ SYSTEM HAS_CODE ALLOW_CLEAR_USER_DATA UPDATED_SYSTEM_APP ALLOW_BACKUP ]
privateFlags=[ PRIVILEGED ]
dataDir=/data/user/0/com.incorporateapps.fakegps
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
usesLibraries:
com.google.android.maps
usesLibraryFiles:
/system/framework/com.google.android.maps.jar
timeStamp=2017-09-26 08:41:14
firstInstallTime=2017-09-26 08:41:15
lastUpdateTime=1970-08-29 17:38:13
installerPackageName=com.android.vending
signatures=PackageSignatures{431c65 [15a9c792]}
installPermissionsFixed=true installStatus=1
pkgFlags=[ SYSTEM HAS_CODE ALLOW_CLEAR_USER_DATA UPDATED_SYSTEM_APP ALLOW_BACKUP ]
requested permissions:
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_COARSE_LOCATION
android.permission.INTERNET
android.permission.ACCESS_MOCK_LOCATION
android.permission.WRITE_SETTINGS
com.android.vending.CHECK_LICENSE
android.permission.INSTALL_LOCATION_PROVIDER
android.permission.WRITE_SECURE_SETTINGS
android.permission.RECEIVE_BOOT_COMPLETED
android.permission.UPDATE_APP_OPS_STATS
install permissions:
android.permission.WRITE_SETTINGS: granted=true
android.permission.ACCESS_FINE_LOCATION: granted=true
android.permission.INSTALL_LOCATION_PROVIDER: granted=true
android.permission.RECEIVE_BOOT_COMPLETED: granted=true
android.permission.INTERNET: granted=true
com.android.vending.CHECK_LICENSE: granted=true
android.permission.WRITE_SECURE_SETTINGS: granted=true
android.permission.ACCESS_COARSE_LOCATION: granted=true
android.permission.UPDATE_APP_OPS_STATS: granted=true
User 0: ceDataInode=1736796 installed=true hidden=false suspended=false stopped=false notLaunched=false enabled=0 instant=false
gids=[3003]
runtime permissions:
Hidden system packages:
Package [com.incorporateapps.fakegps] (a580d3a):
userId=10091
pkg=Package{617deb com.incorporateapps.fakegps}
codePath=/system/priv-app/FakeGPS
resourcePath=/system/priv-app/FakeGPS
legacyNativeLibraryDir=/system/priv-app/FakeGPS/lib
primaryCpuAbi=null
secondaryCpuAbi=null
versionCode=67 minSdk=8 targetSdk=20
versionName=4.9.6
splits=[base]
apkSigningVersion=1
applicationInfo=ApplicationInfo{ca26748 com.incorporateapps.fakegps}
flags=[ HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP ]
dataDir=null
supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity]
usesLibraries:
com.google.android.maps
timeStamp=1970-08-29 17:38:13
firstInstallTime=2017-09-26 08:41:15
lastUpdateTime=1970-08-29 17:38:13
signatures=PackageSignatures{64e19e1 []}
installPermissionsFixed=false installStatus=1
pkgFlags=[ SYSTEM ]
requested permissions:
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_COARSE_LOCATION
android.permission.INTERNET
android.permission.ACCESS_MOCK_LOCATION
android.permission.WRITE_SETTINGS
com.android.vending.CHECK_LICENSE
android.permission.INSTALL_LOCATION_PROVIDER
android.permission.WRITE_SECURE_SETTINGS
android.permission.RECEIVE_BOOT_COMPLETED
android.permission.UPDATE_APP_OPS_STATS
install permissions:
android.permission.WRITE_SETTINGS: granted=true
android.permission.ACCESS_FINE_LOCATION: granted=true
android.permission.RECEIVE_BOOT_COMPLETED: granted=true
android.permission.INTERNET: granted=true
com.android.vending.CHECK_LICENSE: granted=true
android.permission.ACCESS_COARSE_LOCATION: granted=true
User 0: ceDataInode=0 installed=true hidden=false suspended=false stopped=false notLaunched=false enabled=0 instant=false
gids=[3003]
runtime permissions:
Package Changes:
Sequence number=6
User 0:
seq=0, package=com.google.android.talk
seq=4, package=com.google.android.gms
seq=5, package=com.android.terminal
Dexopt state:
[com.incorporateapps.fakegps]
Instruction Set: arm64
path: /data/app/com.incorporateapps.fakegps-7O6AqP-HQQ0wLXWBTXyOLw==/base.apk
status: /data/app/com.incorporateapps.fakegps-7O6AqP-HQQ0wLXWBTXyOLw==/oat/arm64/base.odex[status=kOatUpToDate, co
mpilation_filter=quicken]
Compiler stats:
[com.incorporateapps.fakegps]
base.apk - 728
com.incorporateapps.fakegps.apk - 533

resarfekim said:
Hi, I'm trying to get FakeGPS to work on Oreo. I think I've done everything correctly, but the app freezes when I try to engage the location.
Below is the output from ADB. Does this looks correct, or do I need further action? Thanks!
pkgFlags=[ SYSTEM ]
requested permissions:
android.permission.ACCESS_FINE_LOCATION
android.permission.ACCESS_COARSE_LOCATION
android.permission.INTERNET
android.permission.ACCESS_MOCK_LOCATION
android.permission.WRITE_SETTINGS
com.android.vending.CHECK_LICENSE
android.permission.INSTALL_LOCATION_PROVIDER
android.permission.WRITE_SECURE_SETTINGS
android.permission.RECEIVE_BOOT_COMPLETED
android.permission.UPDATE_APP_OPS_STATS
install permissions:
android.permission.WRITE_SETTINGS: granted=true
android.permission.ACCESS_FINE_LOCATION: granted=true
android.permission.RECEIVE_BOOT_COMPLETED: granted=true
android.permission.INTERNET: granted=true
com.android.vending.CHECK_LICENSE: granted=true
android.permission.ACCESS_COARSE_LOCATION: granted=true
Click to expand...
Click to collapse
Notice the bit from the dump I left in the quote. These permissions are not granted:
Code:
android.permission.ACCESS_MOCK_LOCATION
android.permission.INSTALL_LOCATION_PROVIDER
android.permission.WRITE_SECURE_SETTINGS
android.permission.UPDATE_APP_OPS_STATS
What have you done so far?

Maybe make a companion app that helps with this? Not sure how one would do that though.

Would you believe I didn't notice BetterBatteryStats was missing permissions? :silly: I thought it was no longer necessary as the How-to & FAQ in the main BBS thread states it does not require the system app anymore.
However, it turns out (at least on Oreo) it is still necessary. I noticed these required permissions are not being granted:
android.permission.DUMP
android.permission.READ_LOGS
android.permission.DEVICE_POWER
You can verify the permissions are granted (or not) by going to BBS Settings > Advanced > Install as system app.
I updated the module to support the Play Store version and the XDA Edition. Download in the OP.
@chamonix The above permissions will also need to be granted via adb for those running BBS on a non-rooted device.
Thanks to @kd- for figuring this out :good:

yochananmarqos said:
Would you believe I didn't notice BetterBatteryStats was missing permissions? :silly: I thought it was no longer necessary as the How-to & FAQ in the main BBS thread states it does not require the system app anymore.
However, it turns out (at least on Oreo) it is still necessary. I noticed these required permissions are not being granted:
android.permission.DUMP
android.permission.READ_LOGS
android.permission.DEVICE_POWER
You can verify the permissions are granted (or not) by going to BBS Settings > Advanced > Install as system app.
I updated the module to support the Play Store version and the XDA Edition. Download in the OP.
@chamonix The above permissions will also need to be granted via adb for those running BBS on a non-rooted device.
Thanks to @kd- for figuring this out :good:
Click to expand...
Click to collapse
what version are you using and are there features not working when these perms are missing?

chamonix said:
what version are you using and are there features not working when these perms are missing?
Click to expand...
Click to collapse
I'm using the 2.2.2 XDA Edition. I see a lot more stats with those permissions than without. They are automatically granted when BBS is a system app on Nougat and below, however they are not on Oreo. See the link in the OP to the documentation. Also, @kd- was not able to see Partial Wakelocks until he enabled those permissions with my module. I don't know if he tried forcing the API method or not.
Seeing how this isn't the best place to troubleshoot BBS, shall we continue in the BBS thread? Mention me there if you want to do that.

How do you install this module? I downloaded the zip. Unzipped, edited the xml files as needed, rezipped and tried to install through Magisk app as a module. It said it's not a valid Magisk module.
I'm a little new to Magisk, so I'm sure this is a me issue... any guidance you can provide is appreciated.

robbieas said:
How do you install this module? I downloaded the zip. Unzipped, edited the xml files as needed, rezipped and tried to install through Magisk app as a module. It said it's not a valid Magisk module.
I'm a little new to Magisk, so I'm sure this is a me issue... any guidance you can provide is appreciated.
Click to expand...
Click to collapse
It installed fine in Magisk Manager for me. Try flashing it in recovery.
Sent from my Nexus 5X using XDA Labs

yochananmarqos said:
It installed fine in Magisk Manager for me. Try flashing it in recovery.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
As suspected, user error.... When I rezipped things I zipped the folder not the files, so everything was buried a level too deep.
This worked like a charm and got Tasker Tether working on stock rooted Oreo on a 6p. Thanks!

robbieas said:
As suspected, user error.... When I rezipped things I zipped the folder not the files, so everything was buried a level too deep.
This worked like a charm and got Tasker Tether working on stock rooted Oreo on a 6p. Thanks!
Click to expand...
Click to collapse
I'm glad you found it useful. :good:
Sent from my Nexus 5X using XDA Labs

robbieas said:
As suspected, user error.... When I rezipped things I zipped the folder not the files, so everything was buried a level too deep.
This worked like a charm and got Tasker Tether working on stock rooted Oreo on a 6p. Thanks!
Click to expand...
Click to collapse
Do you mind sharing how you got tether working with tasker and Oreo? I'm struggling to get it working on my Pixel 2.
I've tried just tasker alone, securetask, and nougat+ taker tether control and I just can't get it to work. (Manually toggling via the navigation tile works fine, just not programmatically.)
Sent from my Pixel 2 using Tapatalk

I fought with this forever, especially after 7.1 it became a real hassle. I feel your pain. But I think I've gotten it figured out at this point and happy to help. My use case is for my in-dash Nexus 7 tablet. I leave BT on, and anytime I get in my car it connects to my car stereo, and Tasker turns on my hotspot when it sees I connect to that BT device.
Start with the Tasker plugin "Nougat+ Tasker Tethering Control". This will show up in Tasker under plugins. First time you add it to a task, when you go to configuration you'll see a request to install it to system - do that and reboot.
Now go back to Tasker and and test run the task. If you get an error about "android.permission.TETHER_PRIVILEGED", then flash the attached module in Magisk and reboot. This should give Tasker Tether the permissions it needs to turn hotspot on/off. It worked perfectly for me.
Let me know if you have any issues and I'll help if at all possible. Also this assumes that you can turn on hotspot manually and it works.... this is not a way to get hotspot working if your carrier is blocking it, this just allows Tasker to automate the process.

use aapt to dump app permissions
Code:
aapt d permissions myapp.apk

Innfinite4evr said:
use aapt to dump app permissions
Code:
aapt d permissions myapp.apk
Click to expand...
Click to collapse
Right, but the whole point here is finding out which permissions are not being granted when an app is systemized via Magisk.

Accidental duplicate post.

Cool, I'll try to use it for Mi Fit app that seems to be kicked by Oreo. But right now, ADB seems broken on my device.
If someone kind enought could help me for the list of autorisation to give, I'd be very gratefull !

Kéno40 said:
Cool, I'll try to use it for Mi Fit app that seems to be kicked by Oreo. But right now, ADB seems broken on my device.
If someone kind enought could help me for the list of autorisation to give, I'd be very gratefull !
Click to expand...
Click to collapse
How would Mi Fit benefit from being a system app? I used it with my Mi Band 2 (before I lost it) on Oreo with no issues.
Sent from my LG G5 using XDA Labs

yochananmarqos said:
How would Mi Fit benefit from being a system app? I used it with my Mi Band 2 (before I lost it) on Oreo with no issues.
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
I suspect that doze "hibernate" MiFit while my watch is to far from my Phone. I've tried some things but still the same. I thought that systemize it would help.
If your experience is verified, it lets me 2 options :
- It's software, but rom related
- it's my watch...

[GUIDE] Enabel DT2W Nugat B388

If your double tap to wake (DT2W) is not enabled by default, and other how-tos
don't worki for you, try this:
1. You will need to edit the local build prop:
got to: /product/etc/prop and edit local.prop (your system must be rw)
2. Find the "ro.config.hw_easywakeup=false" and change the value to true, press save and exit
3. Now you need to mod the hw_easywakeupmotion_config.xml which is in /system/emui/base/xml:
Change the
Code:
<HwEasyWakeUpMotion>
<EasyWakeUpMotion name="Double_Touch" support="1" value="0" flag="11" keycode="142" />
to :
Code:
<HwEasyWakeUpMotion>
<EasyWakeUpMotion name="Double_Touch support="1" value="1" flag="11" keycode="142" />
you can edit other paramethers as well.
4. Save, exit and reboot.
5. After the reboot go to: Settings -> Smart assistance -> Motion Control -> turn the features on.

We already have a guide about this

i
Johnny TDN said:
We already have a guide about this
Click to expand...
Click to collapse
They did nkt work for me, so I tought I share my method

Question Settings in Developer Options

Is it possible to enable Install via USB and USB debugging (Security settings) without having a Mi account on the device? And what does MIUI optimisation options do?

Yes. MIUI optimizations heavily restrict background apps which lead to battery savings among other things.

Yes for the first question? Then how?
miravision said:
Yes. MIUI optimizations heavily restrict background apps which lead to battery savings among other things.
Click to expand...
Click to collapse

You need to root your phone. Here is a termux script that will achieve what you want without Mi account.
Code:
su
setprop persist.security.adbinstall 1
Edit file /data/data/com.miui.securitycenter/shared_prefs/remote_provider_preferences.xml
and change value to true if it's set to false or add line before the closing </map> tag. Reboot
Code:
<boolean name="security_adb_install_enable" value="true" />
Code:
reboot

I guess rooting will have to wait... can''t void warranty in a new phone before I have had a chance to test it fully. But, thank you. I will save the above.

I'm trying to disable automatic updates , i disabled them everywhere i could , including developer options but when i enable wifi , the updater app notifies me that i have a new update. Indeed, it won't update without my confirmation but i want to get rid of notifications completely . The notifications for this updater system app can not be turned off . Any workaround for this ?

miravision said:
You need to root your phone. Here is a termux script that will achieve what you want without Mi account.
Code:
su
setprop persist.security.adbinstall 1
Edit file /data/data/com.miui.securitycenter/shared_prefs/remote_provider_preferences.xml
and change value to true if it's set to false or add line before the closing </map> tag. Reboot
Code:
<boolean name="security_adb_install_enable" value="true" />
Code:
reboot
Click to expand...
Click to collapse
should this be valid in MIUI 13?
I did save the xml file twice, but after reboot the line for "install enable" was gone.
Any further ideas to mod this - without logging in to Mi Account?
Thaks
linolino
oops EDIT: I did an reboot via button instead of entering "reboot" in adb/termux - so I can confirm the toggel button is still on after command "reboot" in case of pressing button for reboot it was reverted ;-)

@miravision
is there another line for MIUI.
"Install via USB" worked to be turned on.
But still "USB debugging (Security settings)" can't be turned on in developer options.
This would be the toggle from this repeating screen shot: https://github.com/Genymobile/scrcpy/issues/70
Thanks
linolino

miravision said:
You need to root your phone.
Click to expand...
Click to collapse
this is a chicken egg problem:
in turn, root requires unlocking the bootloader (which requires logging in with a mi account over a cellular data sim, it doesn't allow this over wifi)