Related
How to improve the performance of Firestick?
Please write any tips you know.
Kodimaster said:
How to improve the performance of Firestick?
Please write any tips you know.
Click to expand...
Click to collapse
To improve the performance on Fire TV Stick:
Disable UI animations using ADB:
1. Enable USB debugging in developer options
2. Connect ADB over Wi-Fi
Code:
adb connect <Fire TV's IP address>
3. Run ADB shell
Code:
adb shell
4. Disable any UI animations
Code:
settings put global animator_duration_scale 0.0
settings put global transition_animation_scale 0.0
settings put global window_animation_scale 0.0
Done.
Disable any following dangerous settings:
-> Location based services
-> Interest based ads (advertising ID)
-> Collect App usages
-> Device usage data
Disable System sounds in settings
ADVANCED PERFORMANCE IMPROVEMENT:
Magisk Add-ons for Fire TV Stick 4K. Including with Google services installition, Amazon services removal (debloating to improve performance), Leanback Launcher, and more.
https://forum.xda-developers.com/fi...iretv-4k-stick-add-ons-magisk-module-t3979117
Kodimaster said:
How to improve the performance of Firestick?
Please write any tips you know.
Click to expand...
Click to collapse
When you use it too much. its best clear the cache memory. its very good thing for best performance of the amazon firestick
I tweeked the props and set the CPU to performance based off this thread...
https://forum.xda-developers.com/fire-tv/general/fire-tv-stick-4k-tweaks-root-keyboard-t4064269
Get a 4k or even better an ATV device. No matter how much you "tweak" performance you will not have ram to switch between 2-3 apps without them reinitialize. Even the 4k really cant do 3, but it can do 2 pretty well.
adb returning this error on executing the shell command
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
hiteshp said:
adb returning this error on executing the shell command
adb.exe: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
It sounds like you are making a connection to your FireTV from a new device (your computer). When you do this, an authorization prompt should appear on the FireTV, press ok to give your computer authorization to access your FireTV.
If the authorization prompt is not appearing on your FireTV make sure you have ADB debugging turned on in the FireTV settings menu
Try the following steps to speed up your firestick:-
Restart/Reboot Your FireStick
Remove Unwanted Apps
Clear Cache of Apps
Keep Your FireStick Up to Date
Disable Automatic App Updates
Turn Off Collect App Usage Data
Factory Reset
Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
bino_mat said:
Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
Click to expand...
Click to collapse
Tasker is running fine on my X2 EU version. No problems up to now
Note4Addict said:
Tasker is running fine on my X2 EU version. No problems up to now
Click to expand...
Click to collapse
That is is interesting !! - 2 problems I encountered are
1.Tasker toasts are working only with in Tasker context - I mean if open the tasker and a do a flash message ,it flashes the message- But when on a normal working (Tasker is in background) - no toast message appears.
2.Even if I enable all of the permission,when Tasker tries to switch on the WIfi with in Tasker context as window popes out asking Tasker want to switch on Wifi - Allow or Prohibit -
If Tasker is in background,this window can't appear and nothing happens.
Finally ,I went to Developer options,Disabled the permission monitoring(last option) s- that this started working
Can you please confirm on these 2 points?
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Note4Addict said:
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Click to expand...
Click to collapse
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
bino_mat said:
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
Click to expand...
Click to collapse
Good news that Tasker works well in Color OS 7 which will get around March it seems. Regarding the initial ADB permission, I meant the message you get when you first install Tasker on a non-rooted device. In that case you need to execute a specific permission command via ADB to get Tasker up and running correctly.
What I meant with "Try if you can..." is that If you have the opportunity you may want to check if perhaps one of the new ADB wifi commands would be capable of setting wifi on and off despite permission monitor being active instead of disabled as we're doing now. Hope that will work so we can keep permission monitor active.
Guess ,it is more of Color OS issue , with the battery saved enabled,Tasker is missing the Alarm - I did a simple experiment of logging of BAttery level to a file in every 10 minutes.
If I look at the file now ,either the logging is not continuous or stopped after sleeping for one or hour or so !!! -- But this is not the case with MIUI - It's sharp on time with battery saver or not.
More importantly one thing I noticed is that when battery saver is on ,you can't lock the application in memory - Flip side , with battery saver on ,if I invoke recents and clear the memory ,evrything will be wiped and even when battery saver is off,the applications which you want to be in memory in normal condition will not be there!!!
Bluetooth problems with Android 10:
With my Realme X2 and Realme Ui 1.0 (Android 10) i can not start Bluetooth because my smartphone always asks with an popup for an permission ("Tasker needs the following permission: set Bluetooth on/off"). My desktop links give me the error code "action bluetooth failed".
How can i disable this popup asking for an permission? Or can i made tasker to click on yes itself?
Hi, didn't feel like this is worth making a thread but didn't really find anywhere else to ask for assistance nor any recent help on google.
I'm trying to disable some preinstalled bloatware on my s20 ultra, such as Samsung pay framework though abd but I keep getting this message: adb delete failed owner blocked
I am using the following command: pm uninstall -k --user 0 (package name)
Any insights? thanks.
Did you try the disable method? This one is safer than the uninstall one.
Pm disable 'package name'
You can always re-enable if something goes wrong.
I have same issues mate. Have your found a solution ?
You tried the disable method?
Make your life easier and use ADB AppControl.
ADB AppControl - android applications manager and debloat tool. Official website. Free download.
cucumber42 said:
Make your life easier and use ADB AppControl.
ADB AppControl - android applications manager and debloat tool. Official website. Free download.
Click to expand...
Click to collapse
Privacy Policy
When using this software, the following data may be collected, transmitted to a remote server and processed:
- IP address, information about CPU, RAM, operating system version and installed components from user's PC.
- Android device model and list of applications that have been disabled or removed on this device using this software.
- Activation key and additional identifier for this software.
- Data on user actions within the graphical interface of this software, like buttons clicks.
The user can at any time stop collecting and processing this data by refusing to use this software.
Hi all,
I'm trying to use SecondScreen app ( https://forum.xda-developers.com/t/...screen-mirroring-for-android-devices.2766268/ ) on my Oneplus 9 PRO but this feature it seems doesn't work....
I have asked to releaser and he told me that he would need to know the "sysfs path for turning off the OnePlus 9 Pro's backlight" but I'm not able to find it...
Is there anyone knows this path ?
If so, I could tell it to the releaser and he could add this info into its app by an update...
Many thanks to all !
The SecondScreen app is designed to work with devices that have a secondary display, and unfortunately, the OnePlus 9 Pro does not have a secondary display. However, if you still want to use the SecondScreen app on your OnePlus 9 Pro, you can try the following steps:
Download and install the SecondScreen app from the Google Play Store.
Go to Settings > Developer options on your OnePlus 9 Pro and enable USB debugging.
Connect your OnePlus 9 Pro to your computer using a USB cable.
Download and install the ADB (Android Debug Bridge) tool on your computer.
Open a command prompt or terminal window on your computer and navigate to the folder where you have installed ADB.
Type the following command and press Enter: adb shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS
Disconnect your OnePlus 9 Pro from your computer.
Open the SecondScreen app on your OnePlus 9 Pro, and you should be able to use its features.
Please note that these steps may not guarantee the SecondScreen app's full functionality on your OnePlus 9 Pro, as the app is primarily designed for devices with secondary displays. However, the above steps will allow you to access the app's features and settings.
OpenAL said:
The SecondScreen app is designed to work with devices that have a secondary display, and unfortunately, the OnePlus 9 Pro does not have a secondary display. However, if you still want to use the SecondScreen app on your OnePlus 9 Pro, you can try the following steps:
Download and install the SecondScreen app from the Google Play Store.
Go to Settings > Developer options on your OnePlus 9 Pro and enable USB debugging.
Connect your OnePlus 9 Pro to your computer using a USB cable.
Download and install the ADB (Android Debug Bridge) tool on your computer.
Open a command prompt or terminal window on your computer and navigate to the folder where you have installed ADB.
Type the following command and press Enter: adb shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS
Disconnect your OnePlus 9 Pro from your computer.
Open the SecondScreen app on your OnePlus 9 Pro, and you should be able to use its features.
Please note that these steps may not guarantee the SecondScreen app's full functionality on your OnePlus 9 Pro, as the app is primarily designed for devices with secondary displays. However, the above steps will allow you to access the app's features and settings.
Click to expand...
Click to collapse
Thanks but I have a secondary screen connected to my phone with HDMI ( montior 1080p OLED ) that I'm using to play the games....
Everything goes well with it but I would like to swtich off the phone backlight during mirroring and this app could be the right choise.
I have already tried with root and unroot phone ( with adb commands ).
I already have done all the steps needed
I have already write a PM to the releaser and he told me what I have already above write.....
I repeat my question : is anyone who knows the "sysfs path for turning off the OnePlus 9 Pro's backlight" ?
Thanks !
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet. (Edit 27/06/2023: new updated apk available here)
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Not works for me... I have the italian operator PosteMobile
Doesn't work for me... I tried to use a custom ROM so I could have VoWiFi, but I felt something was off. I got back to OOS13 on my OnePlus 8 Pro (IN2023) with AT&T and tried this method but no success...
omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh. You should see somewhat like "Shizuku is running" at your phone.
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Thank you! It worked on a LE2121 with Android 13!
Update:
I just updated to 13.1 and lost VoLTE. Re-did the steps and got it back.
Added an edit to step 5 in OP, as with 13.1 I had to uncheck "Disable permission monitoring" in developer settings).
It's not work. Oneplus 10 pro. Oxygen os 13.1
yasador said:
It's not work. Oneplus 10 pro. Oxygen os 13.1
Click to expand...
Click to collapse
Need to be more specific.....
Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please
momiloco said:
Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please
Click to expand...
Click to collapse
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.
omar302 said:
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.
Click to expand...
Click to collapse
Thanks bro.
I tried like what you suggested but still the same error.
Managed to do it using wireless USB debugging. Much easier.
Thanks
omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?
kmahesh said:
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?
Click to expand...
Click to collapse
I think you missed reading the first paragraph. It worked for me on my OnePlus 9 Pro on OOS 13 & 13.1. I am using a Tello (US) line which is basically T-Mobile and got VoWifi to work using these steps.
Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP
kmahesh said:
Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP
Click to expand...
Click to collapse
It seems that it doesn't work for all SIM cards. I also tried the same with a 1+ 7 Pro using another SIM and it did not work. Maybe I'll try with the Tello SIM on the 7 Pro just to test if it's an issue with the phone or SIM.
Thanks Omar for trying. All I am trying to find out (1) Is my phone the culprit (or) my T-Mobile is the culprit (2) Is there a solution (with or without rooting) to make this work for USA carriers?
Any help would be appreciated.
Thanks
Mahesh
Hello everybody. I have Oneplus 9R OOS 13.0 Android 13. I did everything according to the instructions using wifi debugging. The volte switch slider has become active. However, when making a call, the phone still falls into the H+, H or 3G network. I have 2 SIM cards installed, before starting the algorithm, I did not deactivate the second one. Could this be a problem? If so, what would you recommend to do in this case?
I tested SIM card 1 used for calls and the Internet in another device, Volte works on it.
Updated to LE2123_13.1.0.580(EX01) and off course lost VoWifi, however, repeating the steps re-enabled it.
Also found an updated Pixel IMS apk (link to download) that has more options when enabling VoLTE or VoWifi.