fluid navigation gestures ADB command not working on note 9 pie - Android Q&A, Help & Troubleshooting

Hi.
The app was working on my phone before the update, but then it started acting funny. So I reinstalled it and tried the ADB stuff again but it's not working anymore.
I tried revoking the USB debugging authorization, and still no joy.
Whenever i type this command: "adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE SETTINGS"
I get this message:
"Exception occurred while executing:
java.lang.IllegalArgumentException: Unknown permission: android.permission.WRITE_SECURE
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:2368)
at com.android.server.pm.permission.PermissionManagerService.access$1100(PermissionManagerService.java:131)
at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:3240)
at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:6402)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:1730)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:217)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:25694)
at android.os.Binder.shellCommand(Binder.java:642)
at android.os.Binder.onTransact(Binder.java:540)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:3315)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:4732)
at android.os.Binder.execTransact(Binder.java:739)".
Please help.

anyone, please ?

Follow these steps:
-Restart Mobile Phone
-Enable Developer Mode in the Android settings.
-Enable USB Debugging
-Install Adb (links bellow)
-Run the following adb command to grant the permission
Open PowerShell window. You can use SHIFT+right click in abd folder.
Now enter the following command and hit ENTER:
./adb shell wm overscan 0,0,0,0
and then
./adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE_SETTINGS
now check Problem will solve.

vedz86 said:
Follow these steps:
-Restart Mobile Phone
-Enable Developer Mode in the Android settings.
-Enable USB Debugging
-Install Adb (links bellow)
-Run the following adb command to grant the permission
Open PowerShell window. You can use SHIFT+right click in abd folder.
Now enter the following command and hit ENTER:
./adb shell wm overscan 0,0,0,0
and then
./adb shell pm grant com.fb.fluid android.permission.WRITE_SECURE_SETTINGS
now check Problem will solve.
Click to expand...
Click to collapse
Thanks for the trick. It works fine.

Same error message on my Mi 10 Lite and the Powershell commands didn't help, anything else I could try ? Thanks !

webvan said:
Same error message on my Mi 10 Lite and the Powershell commands didn't help, anything else I could try ? Thanks !
Click to expand...
Click to collapse
Hi, I saw your issue and I found the fix because I also faced this. Just enable these two options under Developer Options before entering those commands. These are two extra security measures introduced in Mi and Redmi phones. You need to sign in via Mi Account to continue. Make sure to disable it after use. Hope it helps:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

Which Apps are safe to remove?

I haven't seen any other threads and if I have over looked anything based on this topic that is helpful please redirect me. I was just wondering what apps that are preinstalled in ROMs are safe to remove e.g Twitter, Flickr, Footprints etc. I do not need help removing them I already have I am just curious as to what else can be removed safely with out creating an problems/FC.
For anyone interested in removing these apps here is how to do so: (I absolutely do not take any credit for figuring out how to removes these I found it on google and I cannot remember where)
Code:
Type "adb remount"
to remove Peep: "adb shell rm /system/app/*Twit*" then press enter
to remove Stocks: "adb shell rm /system/app/*Stock*" then press enter
to remove Flickr: "adb shell rm /system/app/*Flickr* then enter
to remove Footprints: "adb shell rm /system/app/*Footprints*" then press enter
Additional Apps that are possible to remove thanks to shelnes for the info
to remove Teeter (the HTC game like labyrinth): "adb shell rm /system/app/*Teeter*"
to remove Mail: "adb shell rm /system/app/*Mail*"
to remove HTC Sync: "adb shell rm /system/app/*Sync*" *NOTE* THIS MAY CAUSE YOUR WEATHER TO NO LONGER WORK (the weather info clock) WHEN I REMOVED ALL OF THESE FOR SOME REASON OR ANOTHER MY WEATHER CEASED TO WORK
to remove QuickOffice: "adb shell rm /system/app/*Quickoffice*"
to remove Jbed Java: "adb shell rm /system/app/*Jbed*"
PLEASE NOTE this directory did not work for me if it does not work for you try
"adb shell rm /system/sd/app/*Jbed*"
*NOTE*: Please note that you must run command prompt to do this, either click start, run and type 'cmd' or anyone with Vista or higher type 'cmd' in search, also AndroidSDK must be installed search the forums youll find a guide then in cmd type 'cd\' enter, and 'cd yourdrive:\AndroidSDK(or whatever you named the folder)\tools\' e.g cd c:\AndroidSDK\tools\ after doing this you can enter the commands in the code box
where do u type these? i have ra 1.6.2 and no idea where to put these in
edit: no worries i found it. For any1 else wondering its the cmd prompt on your pc after remounting your phone (should have done this in the early stages of making your goldcard!)
so are there no other apps that are safe to remove?
You also can remove Teeter, Mail, HTC Sync, Mail, Jbed Java and QuickOffice without it causing any problems.
thank you =D
No problem
-------------------------------------
Sent via the XDA Tapatalk App
How to remove Stocks, Nascar and other useless apps...
Hmm cant get it to work?
Just asks me if I want to remove what I just entered and cant enter y for yes?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sorted forgot to adb remount: also get rid of unwanted ring tones eg:
adb shell rm /system/media/audio/ringtones/*Blippy*

[E2333 ] Ads

Hi, I have a problem, I keep receiving subscription ads requests, it seems that it is from my cellphone company, since you can see the sim image in there but I am not sure. This are some examples:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background info: (running Android 6.01, 26.3.B.0.131)
So I used to be on a cell phone company which had this subcription ads request (Movistar), but I changed to another one which they say they do not have any of that (Tuenti), with the same number, and they are both owned by the same company (Otecel), so maybe some settings from the old operator were kept in the new ones, I have talk and talk and talk with them, and i just keep receiving this ads.
Is Root the solution?
Maybe if root my device, I can disable the sim services app, or I do not know something else, and I would not receive this ads again, or what do you guys recommend me.
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Pixelado said:
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Click to expand...
Click to collapse
No, I have not tried not, because I do not know how to do it, could you please teach me , please noob steps
Sorry for being so late haha.
I'll assume you're using Windows 7 or newer.
Steps:
- Get ADB and proper drivers for your devices (Flashtool ships with all of this)
- Enable dev settings on your phone
- Enable USB debugging. Disregard all warnings
- Connect your Xperia to your PC via USB cable
- Wait for drivers to install
- Open a terminal/command prompt on your PC, point it to a directory where you have an ADB executable (adb.exe) (you can do this by opening the flashtool libs folder, eg: c:\flashtool\x10flasherlib, and right-clicking anywhere on the window while keeping the SHIFT key pressed)
- Issue the following command:
-- adb devices
Your phone should ask for authorization now. Grant it
- Issue the following command(s):
-- adb shell (this gives you access to your device's terminal from your PC)
-- pm disable com.android.stk
If the above command fails, try:
-- pm hide com.android.stk
- You're done
You can avoid using a PC by using a terminal emulator on your device AFAIK. I might be wrong though.

[SOLVED][HELP][DPI "bootloop:] Pocophone F1

Good evening,
So I wasn't aware of this DPI bootlooping issue until it happened to me today. I tried changing my DPI to 1000, since it worked to me before (not yet MIUI 11)
Here are some points to consider:
> USB debugging OFF
> bootloader LOCKED
>basically just stock pocophone f1 without any trace of modding.
>Mi Flash Unlock might unlock my bootloader, but I dont want to lose personal data. I tried logging in and my account has permissions to unlock. I only consider this as a last resort. (Is this feasible by the way?)
Here are some things I discovered
1. Using command prompt:
> fastboot devices - detects my phone
> adb devices - detects my phone if I select "Connect with MIAssistant" on stock recovery
> adb shell wm density -doesn't work (I think because bootloader is locked)
> fastboot flash recovery - doesn't work either(bootloader locked)
"adb devices" did not work at first. I tried doing it on fastboot to no avail.
But after some time exploring, "adb devices" worked when selecting "Connect to MIAssistant" on stock recovery
2. It actually is not "not booting", because I tried connecting a mouse using OTG when the loading circle appeared, then a very small mouse cursor appeared.
Here is a picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. What I can tell is, it actually boots but encounters a problem when trying to display with that DPI setting. Correct me if I am wrong with #2 and #3.
Is there any solution to this without wiping my personal data?
Edit1: My solution here: https://forum.xda-developers.com/poco-f1/how-to/pocophone-f1-flash-stock-rom-locked-t4084979
Issue Solved with flashing stock rom. I will edit the post with a link on a new thread on how I did it even with a locked bootrom and USB debugging OFF. I hope that new thread will help others in this same problem.
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Kunalkp123 said:
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Click to expand...
Click to collapse
you need to time it correctly, or use adb's wait for device command
Can I copy somehow the files from my dead phone to PC, using fastboot command? Maybe by EDL mode

Question Issue with notifications after the 12.5.1 update

Since the last MIUI update I am experiencing an issue with notification. When using a video player (like Plex, VLC, YouTube Vanced), I usually see a notification icon when using background playback. This is now gone. Also, and this is the main issue actually, when I close the app I still see it in the notification center and when I swipe it away it still occupies the same space. The notifications below it won't move up. And when I put the phone in stand-by and then open it again, the multimedia notification is there again. The only way to get rid of it is to force close the app.
Is anybody else experiencing this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i have the exact same issue after 12.5 update
Yes is a known bug of this release.
The only solution is by ADB
Open developer tools, connect by USB, and by ADB shell type the following command:
adb shell settings put secure qs_media_resumption 0
That's all
adb shell settings put secure qs_media_resumption 0
thank you, fixed the issue
rello1976 said:
Yes is a known bug of this release.
The only solution is by ADB
Open developer tools, connect by USB, and by ADB shell type the following command:
adb shell settings put secure qs_media_resumption 0
That's all
Click to expand...
Click to collapse
Thanks for this. I'm trying to get this to work, but I don't have much experience using adb. Could you perhaps tell me why it's not working for me ?
adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
renoir:/ $ settings put secure qs_media_resumption 0 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:2105) at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1615) at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1566) at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:408) at android.content.ContentProvider.call(ContentProvider.java:2486) at android.content.ContentProvider$Transport.call(ContentProvider.java:522) 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.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98) at android.os.ShellCommand.exec(ShellCommand.java:44) at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49) at android.os.Binder.shellCommand(Binder.java:932) at android.os.Binder.onTransact(Binder.java:816) at android.os.Binder.execTransactInternal(Binder.java:1162) at android.os.Binder.execTransact(Binder.java:1126)
UPDATE: nvm, I figured it out. I had to also enable the debugging feature that allows secure access. (and log into my Mi account, blegh).
Thanks again
Thank you, the above fixed the issue
Here is a simpler way to fix that, you just need to update MIUI Notifications built-in app to a newer version.
I have attached the apk file, just install it on top of the existing version.
Gonna try it now. Thanks!
Hi, I did the adb process adb shell settings put secure qs_media_resumption 0 but now i'm having issues when the phone connects to the car bluetooth as the song names aren't being updated. How can I revert this, which is the default value for it? I would like to try and see if fixes the issue with the car system and then try to update the notif apk.
thanks!
anyone?

Question Rase to wake not working

Rase to wake not working.
Phone waking up even Rase to wake in off position
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It may be a bug. You can try to upgrade the system
红豆生南瓜 said:
It may be a bug. You can try to upgrade the system
Click to expand...
Click to collapse
Hi
It is up to date
Fixed.
Follow these steps:
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.
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...
forum.xda-developers.com

Categories

Resources