Rescue party is faulty. If triggered it may leave device in usable state.
I think it's better to disable it for users who install mods and other stuff from here.
Magisk module would be useful for that
In my case it reset all settings, even those related to setup wizard.
I had to use adb to put them back. Commands are
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
Click to expand...
Click to collapse
so i was searching for some settings to change through adb and i found this which seems to (slightly) increase the max volume on my headphones, enable debug mode, then using adb on a command line :
adb shell settings put system volume_music_headphone 9
adb shell settings put system volume_music_headset 9
adb shell settings put system volume_music 12
it seems like "volume_music_headphone" and "volume_music_headset" can be set to 9 maximum, if you try to set it higher it will go back to 9, the default value is 8 so it does increase the volume a bit, not that much but still noticable
the "system volume_music" doesn't seems to have a max value, i tried 12 but i didn't try higher
those modifications are saved even if the phone is restarted! :good:
to check the values :
adb shell settings get system volume_music_headphone
etc..
to get a list of various settings:
adb shell settings list global
adb shell settings list system
adb shell settings list secure
some settings are reset to default value after reboot,
does it work with bluetooth audio ?? I cant test right now.
Hi huys,
First of all it's my first post here. I have some questions:
I wanted to make the click to hide and swipe up to show system that huawei puts into some devices work on my Huawei P8 Lite 2017 (Pra-LX1) but I can only make the little arrow working using the Settings Database Editor and adding hide_virtual_key and changing the value to 1 therefore making it apear. Unfortunately, once I click the arrow I need to delete this setting because I can't make the navbar swipe up again.
Notice that I don't have root but I am considering rooting my device it that makes this work. I really wanted to make it work
Can anyone help me? I can use ADB and all of those things. i'm kinda of noob but I can manage myself. I just didn't want to change the stock rom because of the warranty...
My build is PRA-LX1C33B137
P.S: I'll leave a image of what I want to enable so you guys can see: g.oo.gl/cmVYHJ
Thank you all for your attention
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.emuitweaker
You can try this app that I found. I don't know if it works with your device because I'm using the old P8 lite.
OPTION 1 - Do not need root on the device (ADB command line)
To enable "NavBar Arrow":
Code:
adb shell settings put system hide_virtual_key 1
To disable "NavBar Arrow":
Code:
adb shell settings put system hide_virtual_key 0
OPTION 2 - Need root on the device (Edit build.prop)
Enable option on settings to show or hide "NavBar Arrow":
Code:
ro.config.showNavigationBar=true
brunolee said:
OPTION 1 - Do not need root on the device (ADB command line)
To enable "NavBar Arrow":
Code:
adb shell settings put system hide_virtual_key 1
To disable "NavBar Arrow":
Code:
adb shell settings put system hide_virtual_key 0
OPTION 2 - Need root on the device (Edit build.prop)
Enable option on settings to show or hide "NavBar Arrow":
Code:
ro.config.showNavigationBar=true
Click to expand...
Click to collapse
Thanks for ur help, the problem is after I click the arrow I can't swipe up the navbar
Can I remove the carrier icon / name at lock screen status bar with adb shell commands without root?
E.g. "adb shell settings put secure icon_blacklist ...(name of the carrier)".
I don't want to use any 3rd party tools for it.
So while walking it slipped out from my hand and hit the lower left corner.. The screen didnt even work anymore (after removing the glas, it was clear why, as the connector is lower left corner).
Good thing is, I have adb debugging enabled and my keys are known.. So I can access adb shell and various commands..
My problem is: It rebooted and now, the important stuff is NOT mounted.. Also via scrcpy or MonkeyRemote, I cannot send any touch event... Its not reacting at all.. Honestly, I dont know what it is doing, but its quite busy writing for ever logs in logcat, that the sensors have errors (which is no wonder).
So I tried various "adb shell input XXX", but its not working at all..
Tried to connect a mouse via normal usb-c hub, but I dont know if I would need an OTG cable or if it would even work.
DrFone and some other software, already wants the money, before unlocking anything.. And I would be Ok, if it would be 5-10€.. But buying the whole thing for 1 test, is a big no.
So my status:
adb shell working.
scrcpy at least showing a screen
phone is not reacting on anything else, besides the lockscreen to wake it up.. volume keys are also kinda ignored.
I tried the adb shell input stuff from stackoverflow, but nope.
Can I boot in any recovery thing and mount sdcard there? Does scrcpy work there?
What he heck is my phone even doing?? If I connect another phone in lockscreen and use scrcpy, I can also wake it up normaly.. So probably not only the screen got dmg while flying :/
Most annoying things: It has alarms going off all the time, as I can only snooze them -.-
Is there no command, to unlock it from adb/terminal? I know the damn pin
When I run top, the top most things are sufaceflinger and logd (between 2-15). So its not like sth is always at 100% cpu load..
So little status update:
all adb shell input XXX are simple not working, as Xiaomi needs another setting for that.. Which I cannot activate, without screen.
I will try a manual keyboard at home..
Is there a way, to root it with adb only? Would help me alot..
MIUI security center requires you bonded MI account to enable adb input commands in developer options. scrcpy has OTG mode and can emulate HID device.
scrcpy also didnt work, without that stupid setting set to be true/1.
Tested with my old Mi6. When I enabled the option in dev-settings, it worked fine.
But I was able to unlock it with a keyboard plugged in (+ mouse). Looks like the CPU also has some issues, as everything is slow-motion..
So I just tried, what do I need to press on the Mi6 -> then did it on the Mi9.
"hitting space -> pin -> enter", "hitting space -> pin -> enter".
But was able to rescue all my data + turn off the alarms.
PS.: I then tried to enable this setting, for inputs, but you need to have a SIM cart inserted, to activate it
PPS.: Oh.. Now I got you.. I have to enable this option in scrcpy.. OMG Will test that now
PPPS.: Yeah, with that otg mode, the keyboard and mouse would have also worked.. Well, for the next time I know it
alecxs said:
MIUI security center requires you bonded MI account to enable adb input commands in developer options. scrcpy has OTG mode and can emulate HID device.
Click to expand...
Click to collapse
Ok, thanks - that was missing
If you figure out the command line to enable it from adb settings put global I am very grateful
alecxs said:
If you figure out the command line to enable it from adb settings put global I am very grateful
Click to expand...
Click to collapse
Ok, so I dumped all settings and props to files:
Code:
adb shell settings list global > global.txt
adb shell settings list secure > secure.txt
adb shell settings list system > system.txt
adb shell getprop > props.txt
then searched for adb, usb and similar butfound only the following:
SETTINGS GLOBAL:
adb_enabled=1
adb_wifi_enabled=0
verifier_verify_adb_installs=1
GETPROP:
persist.security.adbinput=1
persist.security.adbinstall=1
(My phone: Mi 11 Lite 5G NE, MIUI 13)
That is, eg ADB can be enabled/disabled as settings global adb_enabled
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
IMO, it would be theoretically possible on the Mi 9T Pro, but not if display is broken where TWRP cannot be used (I doubt there is anything like scrpy that works for TWRP)
zgfg said:
Ok, so I dumped all settings and props to files:
Code:
adb shell settings list global > global.txt
adb shell settings list secure > secure.txt
adb shell settings list system > system.txt
adb shell getprop > props.txt
then searched for adb, usb and similar butfound only the following:
SETTINGS GLOBAL:
adb_enabled=1
adb_wifi_enabled=0
verifier_verify_adb_installs=1
GETPROP:
persist.security.adbinput=1
persist.security.adbinstall=1
(My phone: Mi 11 Lite 5G NE, MIUI 13)
That is, eg ADB can be enabled/disabled as settings global adb_enabled
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
IMO, it would be theoretically possible on the Mi 9T Pro, but not if display is broken where TWRP cannot be used (I doubt there is anything like scrpy that works for TWRP)
Click to expand...
Click to collapse
Btw (sorry, OT for the originally reported problem), Netflix cannot be fooled (DRM) to display over scrcpy, only subtitles are displayed on the PC
YT works fine (although without sound - I will try with sndcpy), and strcpy properly recognizes landscape orientation, hence window on the PC can be stretched over the whole monitor
Edit: On the other PC I tried, audio works fine with scrcpy
zgfg said:
However, ADB Input is not in settings but as persistent prop persist.security.adbinput and it can be only manipulated by Magisk - and by TWRP but on the old devices where System is not read-only
Click to expand...
Click to collapse
Nice! I was curious because I don't have Mi account. Although I didn't have this property, just set it from resetprop anyway and it worked!
We can set it from magisk patched boot.img ramdisk/overlay.d/custom.rc systemless. or just add it in init.rc directly.
Code:
on boot
setprop persist.security.adbinput 1