Hello guys!
I have an APP that connects with a external device throught wifi. From the beggining I was using wifi hotspot to connect them, but, on android 7.1.1 they disabled the posibility of enable it programatically and then in android 8.0 (API26) cant enable normal hotspot neither configure it.
On API 26 they have enabled "StartLocalOnlyHotspot" that enables a wifi hotspot but without internet connection. For me it's perfecte BUT! I can't find how to configure the name and password of that wifi. I can read it after starting it but in my project I need to set those external devices configured to automatically connect to a specified wifi configuration, so this is not fitting my needs.
So, anyone know if it's posible to customize the name and password of the LocalOnlyHotspot generated from API 26?
Thanks!
anyone has a remote idea please?
no you cant change ssid and password they are auto generated
no, you cant change SSID and password they are auto-generated, but if you want to know how to retrieve the generated password refer to this:
Code:
@Override
public void onStarted(WifiManager.LocalOnlyHotspotReservation reservation) {
super.onStarted(reservation);
hotspotReservation = reservation;
currentConfig = hotspotReservation.getWifiConfiguration();
Log.v("DANG", "THE PASSWORD IS: "
+ currentConfig.preSharedKey
+ " \n SSID is : "
+ currentConfig.SSID);
hotspotDetailsDialog();
}
shareeditdelete
How do i enable Secure Settings on Poco F1 MIUI 9.6.14.0? it always says "error occurred while executing Action: Password/Pin" i've already enabled Device Admin on my phone. USB debugging = ON, USB debugging (Security settings) = ON
Device Admin Apps: Tasker and Secure Settings checked
Notification access: Tasker checked
Hi. has anyone experimented with passing the SafetyNet check on an Android Studio x86 emulator? I have tried MagiskHide props config with forcing basic attestation together with Universal SafetyNet fix, as well as hiding Magisk and root denylist, but both Basic Integrity and CTF profile match output 'false' (Fail) in YASNAC safetynet checker. I understand there are other things at play here - Safetynet API is trying to detect whether the OS is running in an emulator, but, other than looking in build.props config file, what else does the Safetynet API check?
I currently have exactly the same problem. Have you by any chance found a solution for the problem in the meantime?
Also so it works on Android Devices, iam not sure if it works on an Emulator!!!
Magisk_Module_+_Uninstaller << Here the Files
-Install Magisk.apk App from /sdcard/ and start Magisk App
-go to Settings and Enable "Zygisk" Option
-Setup the Denie-List with Apps you would hide Root (Especially Banking-Apps and other the dont start in Rooted-Device)
-Setup "Hide-Magisk-App" and choose a name 4 the new Shortcut
-Now The App starts again
-goto Modules and choose "Setup from Internal_storage" and Install "MagiskHidePropsConf-v6.1.2.zip" & "safetynet-fix-v2.4.0.zip" without Restart the Device!!!
-After that reboot the Device
-Now Setup a Terminal_Emulator/Termux/etc.. from PlayStore!!!
-open your Terminal on Android and Type the following command
su
props
choose 1
choose f
choose your Device in next 2 Steps!!
(Samsung - 26 / Galaxy Tab A 10.1 2019 - 84)
choose y
choose y to reboot Device!!
-After Reboot open Settings and go to Apps
show all and choose
1# Google-PlayStore and Clear Stored-Datas/ Clear Cache
than goto
2# Google-PlayServices and Clear Stored-Datas/ Clear Cache
-Now you can Download "YASNAC SafetyNet Checker" from Playstore and can Check the Status!!!
-Finish!!!!!!
This is a thread for those who don't want to root their device to force 120Hz on every app.If you are looking for a root solution, then use the LSPosed module called MIUI Performance Saver - Download here
In this way, you can force 120Hz in applications such as: YouTube, MX Player, Google Maps and many others that run at 60Hz by default in MIUI.
You will notice the changes, but you can check it by turning on the refresh rate counter in developer options and check the changes before and after.
First method via ADB
1. In your device, in developer options, enable usb debugging and usb debugging (security settings) and connect your phone to the PC.
2. Download platform tools and extract to a folder
3. Open console in the platform tools folder
4. Enter the following command:
For MIUI 13:
Code:
adb shell settings put system user_refresh_rate 1
For MIUI 14:
Code:
adb shell settings put secure user_refresh_rate 1
If first method doesn't work for you, then try second method.
Second method via Settings Database Editor app
Download this app from the Play Store and for it to work properly, download and install this file from github (settings-database-provider.apk).
For MIUI 13:
1. Open Settings Database Editor app
2. Search "user_refresh_rate"
3. Cick on it to edit the value and replace 120 with 1 and save changes
4. Done
For MIUI 14:
MIUI 14 requires you to grant permissions to the Settings Database Provider app via ADB
1. In your device, in developer options, enable usb debugging and usb debugging (security settings) and connect your phone to the PC.
2. Download platform tools and extract to a folder
3. Open console in platform tools folder
4. Enter the following command:
Code:
adb shell pm grant com.netvor.settings.database.provider android.permission.WRITE_SECURE_SETTINGS
5. Open Settings Database Editor app
6. Search "user_refresh_rate"
7. Cick on it to edit the value and replace 120 with 1 and save changes
8. Done
Keep in mind that it may not work because Xiaomi changes something under the hood of the updates.
I dont know what to say, force fps can cause useless battery drain on app that dont really need ... Do you really need 120hz when you send sms or making call or even messenger ... All do what they want but i wont use it
snx413 said:
I dont know what to say, force fps can cause useless battery drain on app that dont really need ... Do you really need 120hz when you send sms or making call or even messenger ... All do what they want but i wont use it
Click to expand...
Click to collapse
I've been using this method since I had the Poco F3 and I've never noticed that the battery was draining much because of it. I'm used to 120Hz and find it irritating to suddenly switch to 60Hz when scrolling in YouTube or some other app. I am not forcing anyone to force 120Hz on their devices.
Yeah but its most of the time at 120 btw, only you tube and tik tok seems to lower it at 60,
I miss my poco f3... They have all custom rom they want pfff, i sold to my brother ...
root and non root method doesnt work for my poco f3 with xiaomi.eu, i tried global too
HappyTrix said:
root and non root method doesnt work for my poco f3 with xiaomi.eu, i tried global too
Click to expand...
Click to collapse
Can you provide more information? Any errors when executing commands in ADB? Can't find user_refresh_rate in setedit app? It's impossible that it wouldn't work on Poco F3, because I had this device until recently (now I don't have it anymore) and both methods worked perfectly in global ROMs and xiaomi.eu.
is there any way to force it from 120hz to 60hz instantly when i stop swiping? it only works when brightness is above 50%, if below 50% it's always 120hz
nhquocnam said:
is there any way to force it from 120hz to 60hz instantly when i stop swiping? it only works when brightness is above 50%, if below 50% it's always 120hz
Click to expand...
Click to collapse
This is MIUI, nothing can be done about it. You can try Magisk root + LSPosed "MIUI Performance Saver" module and force 120hz, which "maybe" will solve your problem, or you can wait for some custom rom that will hopefully come out for the Xiaomi 12T Pro someday, as long as Xiaomi releases kernel source code for this device.
I cant seem to get my ADB to work u have any guides? and there is no "console" in the platform tools folder please help me
uvzen said:
This is a thread for those who don't want to root their device to force 120Hz on every app.If you are looking for a root solution, then use the LSPosed module called MIUI Performance Saver - Download here
In this way, you can force 120Hz in applications such as: YouTube, MX Player, Google Maps and many others that run at 60Hz by default in MIUI.
You will notice the changes, but you can check it by turning on the refresh rate counter in developer options and check the changes before and after.
First method via ADB
1. In your device, in developer options, enable usb debugging and usb debugging (security settings) and connect your phone to the PC.
2. Download platform tools and extract to a folder
3. Open console in the platform tools folder
4. Enter the following command:
For MIUI 13:
Code:
adb shell settings put system user_refresh_rate 1
For MIUI 14:
Code:
adb shell settings put secure user_refresh_rate 1
Second method via SetEdit app
Download this app from Play Store
For MIUI 13:
1. Open Setedit app and scroll down to the end
2. Find "user_refresh_rate" "120"
3. Cick on it to edit the value and replace 120 with 1 and save changes
4. Done
For MIUI 14:
MIUI 14 requires you to grant permissions to the Setedit app via ADB
1. In your device, in developer options, enable usb debugging and usb debugging (security settings) and connect your phone to the PC.
2. Download platform tools and extract to a folder
3. Open console in the platform tools folder
4. Enter the following command:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
5. Open Setedit app
6. In the right corner, change the "System Table" tab to "Secure Table"
7. Scroll down to the end and find "user_refresh_rate" "120"
8. Cick on it to edit the value and replace 120 with 1 and save changes
9. Done
Click to expand...
Click to collapse
Thank you, useful af
I'm getting an error while running the adb command :
Exception occurred while executing 'put':
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2331)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1768)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1719)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:467)
at android.content.ContentProvider.call(ContentProvider.java:2533)
at android.content.ContentProvider$Transport.call(ContentProvider.java:530)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:382)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:278)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:50)
at android.os.Binder.shellCommand(Binder.java:1054)
at android.os.Binder.onTransact(Binder.java:882)
at android.os.Binder.execTransactInternal(Binder.java:1290)
at android.os.Binder.execTransact(Binder.java:1249)
SooRaj SuResh said:
I'm getting an error while running the adb command :
Exception occurred while executing 'put':
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2331)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1768)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1719)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:467)
at android.content.ContentProvider.call(ContentProvider.java:2533)
at android.content.ContentProvider$Transport.call(ContentProvider.java:530)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:382)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:278)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:50)
at android.os.Binder.shellCommand(Binder.java:1054)
at android.os.Binder.onTransact(Binder.java:882)
at android.os.Binder.execTransactInternal(Binder.java:1290)
at android.os.Binder.execTransact(Binder.java:1249)
Click to expand...
Click to collapse
Changing refresh rate via ADB doesn't work for me either. Xiaomi changed something in the permissions again during one of the updates. I just updated my thread, so try second method through the Settings Database Editor app, because I checked and it works for me on Xiaomi.eu weekly 23.5.22.
Very good find! I had it working on MIUI 13 but I had been waiting to get it working on MIUI 14 since forever, didn't know we had to modify the secure table for this. Also, do you know any more efficient ways to do this with root? I am always rooted.
SooRaj SuResh said:
I'm getting an error while running the adb command :
Spoiler: Code
Exception occurred while executing 'put':
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2331)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1768)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1719)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:467)
at android.content.ContentProvider.call(ContentProvider.java:2533)
at android.content.ContentProvider$Transport.call(ContentProvider.java:530)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:382)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:278)
at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
at android.os.ShellCommand.exec(ShellCommand.java:38)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:50)
at android.os.Binder.shellCommand(Binder.java:1054)
at android.os.Binder.onTransact(Binder.java:882)
at android.os.Binder.execTransactInternal(Binder.java:1290)
at android.os.Binder.execTransact(Binder.java:1249)
Click to expand...
Click to collapse
Try with granting permission to the app. Even with that you will get an error which you can solve as follows:
How can I use adb to grant permission without root?
Background I'm trying to create an app that can grant and revoke permissions of other apps. To do this I'm using adb commands: pm grant packageName permissionName This works great if I call it
stackoverflow.com
Unknown.Guy said:
Also, do you know any more efficient ways to do this with root? I am always rooted.
Click to expand...
Click to collapse
If you have root then use LSPosed module MIUI Performance Saver.
I got the following phone:
Moto G Pure | 2021 | 2-Day battery | Unlocked | Made for US by Motorola | 3/32GB | 13MP Camera | Deep Indigo
[https://www.amazon.com/gp/product/B09BTB5MKT/](https://www.amazon.com/gp/product/B09BTB5MKT/)
It has an Android 11 installed.
After installing RuskDesk Version: 1.1.10-1
and granting it the following 4 permissions:
Screen Capture, Input Control, Transfer File and Audio Capture
I was able to connect using the generated id and password and everything was working fine.
After rebooting my phone, I was not able to reconnect anymore. When I opened the app and went to the screen share tab, this what I saw there:
“A Service is not running Tap [Start Service] or OPEN [Screen Capture] permission to start the screen sharing service.”
All the other 3 permissions were already OPEN, it’s just the screen capture that wasn’t.
Is there a setting, adb permissions command or another way to make it automatically start the service/screen capture just like how TeamViewer Host does it?
I found this discussion on github page:
Android - Start on boot not working · rustdesk/rustdesk · Discussion #1516
On android the service doesn't start on boot. It appear that the permission to receive boot completion is commented on AndroidManifest.xml on line 14. <!--<uses-permission android:name="android.per...
github.com
I found in the end of that post they implemented this as a feature here:
Android start on boot (auto start after reboot) by Heap-Hop · Pull Request #3425 · rustdesk/rustdesk
#1516 Enable BootReceiver. Adapt to Android 12 (ACTION_IGNORE_BATTERY_OPTIMIZATION_SETTINGS, SYSTEM_ALERT_WINDOW). add Start on Boot setting option. Permissions detection before Start o...
github.com
But I don’t see an option anywhere in the RustDesk app where to enable start on boot setting assuming this feature already exists in the current version that I’m using? Do you have this option on your app?
I also try to give it the following adb permission:
adb shell cmd appops set com.carriez.flutter_hbb PROJECT_MEDIA allow
But I don’t see evidence it’s being granted when running:
adb shell dumpsys package com.carriez.flutter_hbb
Thank you.