Database Develop

[SOLVED] problem WiFi hotspot

Finally found the solution with my z3c. Problem started with Lollipop. When I was using my phone as portable AP there was no Internet access on any device connected. There were many descriptions of solutions (manual settings, soft reset, deleting all APNs) but none of them worked for me.
My service provider suggested changing APN settings:
Use whatever APN you find working for you, and change "APN type" field from "default,supl" to "default,dun".
Now everything works just like it's supposed to.
Sorry if someone posted this already or if it's under wrong subject. This is my first thread. Thanks.

I use this solution and it works for me:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
------------------------------------------------------------
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed (any modern adb.exe works, the one included with FlashTool, for example)
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
------------------------------------------------------------

BarajaVLC said:
I use this solution and it works for me:
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
------------------------------------------------------------
This can be fixed permanently using the following procedure (UPDATE: no root required):
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed (any modern adb.exe works, the one included with FlashTool, for example)
Start an adb shell: adb shell
In the adb shell, run this command: settings put global tether_dun_required 0
------------------------------------------------------------
Click to expand...
Click to collapse
My post is about portable hot spot, not USB tethering. I'm not sure if your post is about the same thing
If yes, then I'm very glad that we have multiple solutions for the same problem

Whoa! My girlfriend had this same problem on a moto g 2014 she bought a year ago, so yesterday I changed her APN type as you said and now everything's working. Thanks a lot.
Sent from my D5833 using Tapatalk

dgaspa75 said:
My post is about portable hot spot, not USB tethering. I'm not sure if your post is about the same thing
If yes, then I'm very glad that we have multiple solutions for the same problem
Click to expand...
Click to collapse
Yes, the solution I provided makes portable WiFi hotspot work

APN Type change to "default,dun" worked like a charm for me.

'settings' is not recognized
i have same problem hotspot is not working i installed android studio 3.0.1 and ran command
settings put global tether_dun_required 0
i get error
C:\Users\log\AndroidStudioProjects\MyApplication>settings put global tether_dun_required 0
'settings' is not recognized as an internal or external command,
operable program or batch file.
any help please

APN Type change to "default,dun" worked like a charm for me...thanks brother

Thanks so much for this! Genius!!

Unable to grant permissions using adb

xiaomi mi max 2
I get an error:
adb -d shell pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
Operation not allowed: java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

Turn on the USB debugging (Security settings)

Permissions not allowed
I'm not able to get permission either
./adb -d shell pm grant com.asksven.betterbatterystats android.permission.BATTERY_STATS
Operation not allowed: java.lang.SecurityException: Permission android.permission.BATTERY_STATS is not a changeable permission type

Poley59 said:
Turn on the USB debugging (Security settings)
Click to expand...
Click to collapse
The option is enabled and still nothing!

MadK9 said:
The option is enabled and still nothing!
Click to expand...
Click to collapse
You have to turn all 3 usb debugging options on for miui.

thanks man
cpthero said:
You have to turn all 3 usb debugging options on for miui.
Click to expand...
Click to collapse
thanks dear it did worked for my Redmi Note 8 Pro :laugh:

cpthero said:
You have to turn all 3 usb debugging options on for miui.
Click to expand...
Click to collapse
Where you do that? Im on miui 11 android 9 (redmi note 8 pro)

danielofata said:
Where you do that? Im on miui 11 android 9 (redmi note 8 pro)
Click to expand...
Click to collapse
In the developers menu, you will find usb debugging and a bit more down the other one. I had to select both to get it working (mi 9t pro on miui 11 android 10)

Dxue said:
In the developers menu, you will find usb debugging and a bit more down the other one. I had to select both to get it working (mi 9t pro on miui 11 android 10)
Click to expand...
Click to collapse
Hi,
i am struggling with this right now. I got a Note 8 Pro with MIUI Global 11.0.3. I am trying to get BetterBatteryStats to show me what wakes up my phone. When using ADB i get the same error message ticatc3 got.
What exact setting do i need to activate? Most of them want me to "sign in to my Mi Account first" (what the heck for?).
If i knew how to attach a screenshot i would do so.
The Settings i got are:
USB debugging
Install via USB
USB Debugging (Security Settings)
Select debug app
Greetings

Realme X2 Pro - Color OS6 - USB debugging
Hey,
I just had the same problem with my Realme X2 Pro. USB debugging was not enough. It worked after I activated the bottom most option in the developer options:
"Disable Permission Monitoring" (English) / "Erlaubnisüberwachung deaktivieren" (German)
Just for completeness.

dadri said:
Hey,
I just had the same problem with my Realme X2 Pro. USB debugging was not enough. It worked after I activated the bottom most option in the developer options:
"Disable Permission Monitoring" (English) / "Erlaubnisüberwachung deaktivieren" (German)
Just for completeness.
Click to expand...
Click to collapse
thanks !
I was exactly looking for this

tschesny said:
Hi,
i am struggling with this right now. I got a Note 8 Pro with MIUI Global 11.0.3. I am trying to get BetterBatteryStats to show me what wakes up my phone. When using ADB i get the same error message ticatc3 got.
What exact setting do i need to activate? Most of them want me to "sign in to my Mi Account first" (what the heck for?).
If i knew how to attach a screenshot i would do so.
The Settings i got are:
USB debugging
Install via USB
USB Debugging (Security Settings)
Select debug app
Greetings
Click to expand...
Click to collapse
You have to enable all of them so that you can grant permissions

thanks a lot dadri, I was having the exact same problem on my x2 pro with realme ui and with yoyur input I finally got betterbatterystats working has it should

dadri said:
Hey,
I just had the same problem with my Realme X2 Pro. USB debugging was not enough. It worked after I activated the bottom most option in the developer options:
"Disable Permission Monitoring" (English) / "Erlaubnisüberwachung deaktivieren" (German)
Just for completeness.
Click to expand...
Click to collapse
Thanks, it worked on my realme 1

For COLOR OS you have to disable permission monitoring, is at the botton of developer options. USB Debugging and disable permissions, you have to select both options.

Not sure if this is the same issue or not but I am trying to run an adb command for the first time, the command is this
adb shell pm grant com.maxmpz.equalizer
android.permission.dump
These commands are listed under two different lines. When I try to run them separately I get an error saying no permissions specified. When I run them under one line I get an error that says,
Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown permission: android.permission.dump
on my LG G7 the developer options are a bit different, under USB debugging, this is what i see..
https://imgur.com/JbEFacE
What should I do to get this to work?

cpthero said:
You have to turn all 3 usb debugging options on for miui.
Click to expand...
Click to collapse
This worked for POCO X3 Pro. Thank you very much.

swagmuel said:
For COLOR OS you have to disable permission monitoring, is at the botton of developer options. USB Debugging and disable permissions, you have to select both options.
Click to expand...
Click to collapse
you are a savior!!!!
thank you!!!

I'm having this problem on my LG V20 with Oreo. It let me enable 2 of 3 permissions, but not PACKAGE.USAGE.STATS.
The error:
Operation not allowed: java.lang.SecurityException: Package com.asksven.betterbatterystats_xdaedition has not requested permission android.permission.PACKAGE_USAGE_STATS

dadri said:
Realme X2 Pro - Color OS6 - USB debugging
Hey,
I just had the same problem with my Realme X2 Pro. USB debugging was not enough. It worked after I activated the bottom most option in the developer options:
"Disable Permission Monitoring" (English) / "Erlaubnisüberwachung deaktivieren" (German)
Just for completeness.
Click to expand...
Click to collapse
THANK YOU!!!!! Man i thought i was screwed as a use taser a lot and needs a LOT of ADB functions like monitoring Clipboard. this should be the 1st google search entry when searching for this problem. I literally made an account just to post this .

how to auto override force dark mode in android Q

In AOSP based android Q roms, there is a force dark option in developer settings whoich makes almost all apps to be appreaded in dark mode.
This option gets unselected after reboot.
One has to enable it after every reboot.
However it's possible to enable it by default after reboot.
For rooted phone.
Just add the following line in your build.prop file
debug.hwui.force_dark=true
Thats all.
It's working in my phone. Tested.
For unrooted Phone
execute the following line after reboot
setprop debug.hwui.force_dark true
To make it auto after reboot use tasker or script manager app or smthing similer.
Check the space after setprop and dark.
Hit a thanks to me if you are benifited.

Screenshots.??

Screenshot

Hmmmm.
Screenshot for many apps.?
Thanks

LoveFootJob said:
Hmmmm.
Screenshot for many apps.?
Thanks
Click to expand...
Click to collapse
look at your back....its there already

[email protected] said:
For unrooted Phone
execute the following line after reboot
setprop debug.hwui.force_dark true
To make it auto after reboot use tasker or script manager app or smthing similer.
Check the space after setprop and dark.
Click to expand...
Click to collapse
Hi
How did you manage that?
As far as I know, setprop needs root or it won't work unless it's done via adb on a computer
Sent from my SM-N976B using XDA Labs

paolo200 said:
Hi
How did you manage that?
As far as I know, setprop needs root or it won't work unless it's done via adb on a computer
Click to expand...
Click to collapse
No...it will work...
Just auto execute it after every reboot thru tasker

[email protected] said:
No...it will work...
Just auto execute it after every reboot thru tasker
Click to expand...
Click to collapse
Ok. Thanks.
May I ask what is the action to use within tasker?
Sent from my SM-N976B using XDA Labs

davidking2893 said:
First, turn off regular dark mode (if enabled) and reboot your cell phone. Then, toggle the override-dark-mode option in developer settings and restart the settings app. This will force all apps into the override-dark-mode color scheme. Thats' it.
Click to expand...
Click to collapse
Question is how to do it auto after reboot

[email protected] said:
For unrooted Phone
execute the following line after reboot
setprop debug.hwui.force_dark true
To make it auto after reboot use tasker or script manager app or smthing similer.
Check the space after setprop and dark.
Hit a thanks to me if you are benifited.
Click to expand...
Click to collapse
I don't get you. Can you give a detailed tutorial?

Not working
Im on a non-rooted Galaxy S10e [Android 10, OneUI 2.0]. If I run the command with tasker, it gives me the following message ("Ausführen" is german and means "execute", "Fehler" means "error"):
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/Shell runBackground setprop debug.hwui.force_dark true root: false timeout: -1
05.06.39/Shell start process-thread ID 672
05.06.39/E add wait type Shell1 time 2147483647
05.06.39/E add wait type Shell1 done
05.06.39/E add wait task
05.06.39/E Fehler: 1
If I do it with the app "Android Terminal Emulator" it gives me the following error:
:/ $ setprop debug.hwui.force_dark true
setprop: failed to set property 'debug.hwui.force_dark' to 'true'
Either way, it doesnt work for me. Does anybody know what could be the issue here? Ive also tried setting it to "1" instead of "true", same result. Setting the real setting to enabled or disabled doesnt matter either.

RnKn98 said:
Im on a non-rooted Galaxy S10e [Android 10, OneUI 2.0]. If I run the command with tasker, it gives me the following message ("Ausführen" is german and means "execute", "Fehler" means "error"):
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/E Shell Ausführen: ->
05.06.39/Shell runBackground setprop debug.hwui.force_dark true root: false timeout: -1
05.06.39/Shell start process-thread ID 672
05.06.39/E add wait type Shell1 time 2147483647
05.06.39/E add wait type Shell1 done
05.06.39/E add wait task
05.06.39/E Fehler: 1
If I do it with the app "Android Terminal Emulator" it gives me the following error:
:/ $ setprop debug.hwui.force_dark true
setprop: failed to set property 'debug.hwui.force_dark' to 'true'
Either way, it doesnt work for me. Does anybody know what could be the issue here? Ive also tried setting it to "1" instead of "true", same result. Setting the real setting to enabled or disabled doesnt matter either.
Click to expand...
Click to collapse
In Samsung phone setprop command is diff i guess... Google it for command.

[email protected] said:
In Samsung phone setprop command is diff i guess... Google it for command.
Click to expand...
Click to collapse
Do you have proof it's working for non root??

[email protected] said:
In Samsung phone setprop command is diff i guess... Google it for command.
Click to expand...
Click to collapse
First thanks for the answer , but...
I dont think its different. The getprop command (getprop debug.hwui.force_dark) works fine, gives me true if its turned on.
If i do the setprop command over adb (adb shell setprop debug.hwui.force_dark true) it also works fine.
The only thing not working is the setprop command executed directly on my device. Which lets me conclude that i probably need root?

RnKn98 said:
First thanks for the answer , but...
I dont think its different. The getprop command (getprop debug.hwui.force_dark) works fine, gives me true if its turned on.
If i do the setprop command over adb (adb shell setprop debug.hwui.force_dark true) it also works fine.
The only thing not working is the setprop command executed directly on my device. Which lets me conclude that i probably need root?
Click to expand...
Click to collapse
No... Its working in non rooted device... Tested.
There may be one more thing... Shell need to have write secure settings permission. Its permission issue.

[email protected] said:
In AOSP based android Q roms, there is a force dark option in developer settings whoich makes almost all apps to be appreaded in dark mode.
This option gets unselected after reboot.
One has to enable it after every reboot.
However it's possible to enable it by default after reboot.
For rooted phone.
Just add the following line in your build.prop file
debug.hwui.force_dark=1
Thats all.
It's working in my phone. Tested.
Hit a thanks to me if you are benifited.
Click to expand...
Click to collapse
Hello,
Thank you so much for your solution that works very well on my rooted phone :good:
1) I would like to know how to totally disable this feature if I no longer want the override force-dark someday please ?
2) Actually, how to force the rest of the remaining white applications to become black please ?
Thank you in advance for your help.
Cordially

MobAndro said:
Hello,
Thank you so much for your solution that works very well on my rooted phone :good:
1) I would like to know how to totally disable this feature if I no longer want the override force-dark someday please ?
2) Actually, how to force the rest of the remaining white applications to become black please ?
Thank you in advance for your help.
Cordially
Click to expand...
Click to collapse
Just switch off dark theme... Force dark need not to be changed. Add dark theme icon in qs header

[email protected] said:
Just switch off dark theme... Force dark need not to be changed. Add dark theme icon in qs header
Click to expand...
Click to collapse
Hello,
I've been using the dark mode since I bought my S10.
I discovered the override force-dark a few days ago then I realized that after the reboot this option was disabled on its own and every time.
I did some research to have it automatically and I came across your tuto that worked very well for me. Only some applications had problems with the override force-dark.
Since yesterday, I don't know why now the override force-dark disables itself. When I turn it on, it immediately turns off itself without even restarting.
I don't understand what's going on because this option was automatically activated after each reboot.
I didn't again even touch the build.prop either...

MobAndro said:
Hello,
I've been using the dark mode since I bought my S10.
I discovered the override force-dark a few days ago then I realized that after the reboot this option was disabled on its own and every time.
I did some research to have it automatically and I came across your tuto that worked very well for me. Only some applications had problems with the override force-dark.
Since yesterday, I don't know why now the override force-dark disables itself. When I turn it on, it immediately turns off itself without even restarting.
I don't understand what's going on because this option was automatically activated after each reboot.
I didn't again even touch the build.prop either...
Click to expand...
Click to collapse
It's tough to tell the problem from here. U hv to find it.

[email protected] said:
It's tough to tell the problem from here. U hv to find it.
Click to expand...
Click to collapse
Do you think that I can delete this line "debug.hwui.force_dark=1" and put it back in the build.prop again after reboot please ?
Because it's the first time that I've modified this system file so I'm not used to manipulating it...
Thank you in advance for your answer.

Screen turning on by itself.

When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills

antz_77 said:
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping

thesoupthief said:
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
Click to expand...
Click to collapse
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills

antz_77 said:
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?

thesoupthief said:
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
Click to expand...
Click to collapse
I tried it, but nothing. Screen continue turning on whe moving the phone. I put pocket mode (even cover frontal cámara) and same result.
I have thinking about factory reset, but one user tried a factory reset ( another xiaomi forum ) , without results.
When the winds of change blow, some build walls, others build windmills

Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences

i have the same problem! thought im going crazy
i try update the system and will update afterwards

Mine has the same problem on global firmware but not on china firm

After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
adb shell
settings put secure wake_gesture_enabled 0
Click to expand...
Click to collapse

Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
thanks for the tip with adb it works perfectly

Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
It works for me. Thank you.
When the winds of change blow, some build walls, others build windmills

i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)

thesoupthief said:
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
Click to expand...
Click to collapse
Version here is QJOMIXM. Same problem.

arik100 said:
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
Click to expand...
Click to collapse
You must enable first these 2 options in developers menu

I'm stupid and I don't know how to do this and have the same issue, could someone walk me trough with how to get into ADB and use the commands

I have the same problem, I upgraded to MIUI12 and it didn't solve ... the solution would be only with adb ...
---------- Post added at 02:01 PM ---------- Previous post was at 01:25 PM ----------
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
...have a link that teaches "step by step" how to do this.....

Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
Thanks! That did the trick!!
And after a proper cleanup my GF's brand new Note 9 is really a good buy!
Removal/disabling pre-installed 'crapware' is always a good start, regardless of brand!

Solved!
I created my xda accout just to say thanks, this worked perfectly.
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse

logan3103 said:
I created my xda accout just to say thanks, this worked perfectly.
Click to expand...
Click to collapse
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perfom this trick..i have the same issue

1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all. Your phone screen should stay locked when you move it at this point.
Hope this helps you.
Dadaonacsil09 said:
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Pls help me how to perfom this trick..i have the same issue
Click to expand...
Click to collapse

How to rescue data from my 9T Pro

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