I'm doing OTA updates since at least a year and installed magisk only once when i set up my phone. That's not true.
Same for me. The xz2c is my daily driver.I prefer to be safe than sorry I use my xz2 as a daily one
regards
Yes, there's a bug report see https://gitlab.com/LineageOS/issues/android/-/issues/308Hi, many thanks for your great work!
- I own a Sony Xperia XZ2, model number H8216. After installing lineage-18.1-20220119-nightly-akari-signed.zip and Gapps (MindTheGapps-11.0.0-arm64-20210920_084011.zip) I disabled USB debugging in developer options, disconnected the phone and rebooted.
And there it is: USB debugging is enabled again. When I connect the phone to my computer a message appears, telling me that USB debugging is enabled and in developer options the respective switch is activated.
- No Magisk or anything similar else installed.
Is there any solution, maybe in the next release?
Please see also: https://www.reddit.com/r/LineageOS/comments/s8ff6w Greetings
adb shell setprop persist.vendor.usb.config ""
adb shell getprop persist.vendor.usb.config
Hi dtrunk90Yes, there's a bug report see https://gitlab.com/LineageOS/issues/android/-/issues/308
Afaik this can be fixed by us in a qcom usb script. I'll have a look over the weekend.
Please see my edit aboveHi dtrunk90
Thanks a lot for your quick response and the promising prospect.
All the best
HelloYes, there's a bug report see https://gitlab.com/LineageOS/issues/android/-/issues/308
Afaik this can be fixed by us in a qcom usb script. I'll have a look over the weekend.
EDIT: Weird, I just checked our common device tree and this fix was already present. You did a clean install with wiping data/doing a factory reset before? If not, please run:
Code:adb shell setprop persist.vendor.usb.config ""
You could also check that persistent property before re-setting it with:
Code:adb shell getprop persist.vendor.usb.config
It was worth a try. I'll have a look on the weekend.Hello
Sorry to bother you once again.
I did a clean new install after formatting/wiping all data in the recovery.
This time I installed lineage-18.1-20220119-nightly-akari-signed.zip
without Gapps or anything else.
After booting first time USB debugging was activated and consequently after deactivating it via developer options and reboot. So unfortunately there was no improvement.
Using the commands you suggested resulted in mainly empty lines:
>> BT-iMac:~ b_o_t$ adb shell getprop persist.vendor.usb.config
BT-iMac:~ b_o_t$ adb shell setprop persist.vendor.usb.config ""
usage: setprop NAME VALUE
Sets an Android system property.
BT-iMac:~ b_o_t$ <<
Will be fixed with the next build. Thank you for reporting.Hello
Sorry to bother you once again.
I did a clean new install after formatting/wiping all data in the recovery.
This time I installed lineage-18.1-20220119-nightly-akari-signed.zip
without Gapps or anything else.
After booting first time USB debugging was activated and consequently after deactivating it via developer options and reboot. So unfortunately there was no improvement.
Using the commands you suggested resulted in mainly empty lines:
>> BT-iMac:~ b_o_t$ adb shell getprop persist.vendor.usb.config
BT-iMac:~ b_o_t$ adb shell setprop persist.vendor.usb.config ""
usage: setprop NAME VALUE
Sets an Android system property.
BT-iMac:~ b_o_t$ <<
Hello
Sorry to bother you once again.
I did a clean new install after formatting/wiping all data in the recovery.
This time I installed lineage-18.1-20220119-nightly-akari-signed.zip
without Gapps or anything else.
After booting first time USB debugging was activated and consequently after deactivating it via developer options and reboot. So unfortunately there was no improvement.
Using the commands you suggested resulted in mainly empty lines:
>> BT-iMac:~ b_o_t$ adb shell getprop persist.vendor.usb.config
BT-iMac:~ b_o_t$ adb shell setprop persist.vendor.usb.config ""
usage: setprop NAME VALUE
Sets an Android system property.
BT-iMac:~ b_o_t$ <<
https://review.lineageos.org/c/LineageOS/android_device_sony_tama-common/+/322473
Once this is merged it should be fixed.
Again: You don't have to reinstall magisk everytime after an OTA update. You're doing something wrong.
with v24 you can use https://github.com/kdrag0n/safetynet-fix and add stuff you want to hide root for (e.g. some google services) to zygisk denylist - but v23 is pretty stable on 18.1 - you have to root it only once. after every OTA update magiskinit will do the rest automatically for you.Maybe. No matter. I test now magisk v24 but safetynet broken and new magisk do not have hide components.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
Uploaded a new lineage-18.1-20210515-unofficial-akari.zip again.I don't have battery drain issue to begin with so can't tell the difference sadly, but yeah flashed and everything still works fine as before!