So i bought an android tv and when i went in toDevice preferences, i couldn't find accessibility menu anywhere. I searched it in all the menus in settings. i updated all apps and cleared data of apps and restarted the tv several times. I even factory resetted the Tv
Tv- vu premium 50 inch
Android ver - 9
.
please help
broyoto said:
So i bought an android tv and when i went in toDevice preferences, i couldn't find accessibility menu anywhere. I searched it in all the menus in settings. i updated all apps and cleared data of apps and restarted the tv several times. I even factory resetted the Tv
Tv- vu premium 50 inch
Android ver - 9
.
please help
Click to expand...
Click to collapse
I have the same problem with my TV, as I found out the problem is from the brand side. They choose a rom that that does not have this... The only way to give permision to an app is only through ADB that it is not an easy job
I also have the same issue with my TV, waiting for the solution.
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
{
"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"
}
The same way I resolved this and other apps
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Perhaps anyone knows this:
In my tv sony XH900 (it has accessibility menu, it's not my problem), when i use button mapper and give accessibility permission through the menu, it works fine, but there is one bug:
Volume buttons +- doesn't work continually.. By keep press + for example, it just increase sound only 1 step. I have to press and left, the button many times to increase sound more steps..
Is this the default for all tv if you use button mapper or only mine?
Is there any solution?
Thanks,
I have the accessibility menu but when I install any app it doesn't appear on accessibility menu at all.
sophiesaelig said:
I also have the same issue with my TV, waiting for the solution.
Click to expand...
Click to collapse
flar2 said:
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Click to expand...
Click to collapse
Wow...Din't expect your reply. If you're official developer or team of Button Mapper, just want to tell you one thing.
"You saved my ass so many times". I just love your app and have been using it since a year, happy to say I paid for full version since starting.
ReX-Hell2heAven said:
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
Click to expand...
Click to collapse
Thank you, I did it at the same app.
I tried to do it for this app " Mouse toggle for Android tv" but it didn't work, Can you help me?
Deleted member 1198227 said:
Perhaps anyone knows this:
In my tv sony XH900 (it has accessibility menu, it's not my problem), when i use button mapper and give accessibility permission through the menu, it works fine, but there is one bug:
Volume buttons +- doesn't work continually.. By keep press + for example, it just increase sound only 1 step. I have to press and left, the button many times to increase sound more steps..
Is this the default for all tv if you use button mapper or only mine?
Is there any solution?
Thanks,
Click to expand...
Click to collapse
If any have found workaround let me know, this bug is very annoying
ReX-Hell2heAven said:
I've gone crazy **** about this issue. I badly wanted to use Button Mapper but couldn't find the app under Accessibility Services. After 1 whole day of head storming, I was able to do it. It's the only way for now as the above user said some TVs not enabled accessibility menu in settings. This can be solved by their system update but till then we have to do manually with ADB.
You should have knowledge of ADB shell commands running through USB debugging with the help of ADB minimal tools or android SDK(please google if you don't know).
Enable developer settings and USB debugging. Connect TV to your computer having ADB tools. Remember only USB 2.0 port will work so don't use 3.0
Run "adb devices" to check whether TV got connected.
If connected then run this command
"adb shell settings put secure enabled_accessibility_services PKGname/ServiceName"
,here package name is your app package name where as service name is one of the app's services which seeking accessibility service.
For example I tried for Button Mapper(to map the remote buttons and it won't run without accessibility service enabled).
"adb shell settings put secure enabled_accessibility_services flar2.homebutton/flar2.homebutton.utils"
After that run another command for WRITE_SECURE_SETTINGS(this is must)
"adb shell pm grant PKGname android.permission.WRITE_SECURE_SETTINGS"
in my case it is "adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS"
This will resolve the issue without any problem. If you know adb commands then you can play with all the permissions and services for the apps.
Run above commands without quotes. To check apps package,permissions,services you can user any app manager/analyser app. I'm using FX explorer which is best file explorer and app manager. I'm attaching snaps which will be helpful. Let me know if you still face issues.
Click to expand...
Click to collapse
flar2 said:
The only thing you need to do with Button Mapper is this:
adb shell pm grant flar2.homebutton android.permission.WRITE_SECURE_SETTINGS
The app will take care of the rest after it has that permission
Click to expand...
Click to collapse
Bought a tv in europe ( developper and usb debuggibg activated) can't run any adb command though. Adb: not found
Related
I just bought a Pixel XL Verizon phone yesterday that has been updated to Oreo. I am coming from a Nexus 6 that I rooted and ran PureNexus on for 2 years. I had Samsung Galaxy phones before it. So I have always had my back button on the right and recents on the left. Is there any way to change it on a locked bootloader Pixel XL running Oreo? I have tried searching and everything I have seen says that I need root to do it. And from I can tell so far, there isn't a system UI tuner anymore.
Am I screwed? Should I just sell this Verizon version and get a Google version?
fatphatboy88 said:
I just bought a Pixel XL Verizon phone yesterday that has been updated to Oreo. I am coming from a Nexus 6 that I rooted and ran PureNexus on for 2 years. I had Samsung Galaxy phones before it. So I have always had my back button on the right and recents on the left. Is there any way to change it on a locked bootloader Pixel XL running Oreo? I have tried searching and everything I have seen says that I need root to do it. And from I can tell so far, there isn't a system UI tuner anymore.
Am I screwed? Should I just sell this Verizon version and get a Google version?
Click to expand...
Click to collapse
I would buy Google. I'm on Verizon and I did. I'll never buy another phone from them.
I used this app to make the edit then uninstalled - https://www.xda-developers.com/customise-the-navigation-bar-android-oreo/
If you don’t have root access, you’ll need to download either Minimal ADB & Fastboot or the official Google binaries to enable the required WRITE_SECURE_SETTINGS permission for the application.
To do so, you’ll need to first enable USB Debugging by going to the Developer Options menu. If you don’t see Developer Options, scroll down to “About” and tap “Build number” seven times until the “You are now a developer” toast appears. Back out and above “About” will be the “Developer options” menu. Enter this and enable USB Debugging. Launch adb from your computer by pressing shift + right click in the same folder containing your adb files, then choosing to “open command prompt here” if you’re on Windows. For Mac and Linux users, you’ll need to open terminal then cd to the directory where you downloaded the files. Follow the instructions in the app to grant the appropriate permissions.
Click to expand...
Click to collapse
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Thank you so much! Very easy and no apps to install. Used this method on my Pixel 2 xl
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Any risks at all to doing this? I detest the placement of the back and home buttons on the Pixel 2 XL. Am i risking any bricking with this method? I find it to be incredibly annoying that Android doesn't allow this swap via settings. Putting the back on the left is just bad design. Thanks in advance.
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
I don't have a Pixel 2 XL, just a Pixel XL but I am on Oreo. I have had absolutely ZERO issues since doing this. I love my phone after changing the layout. Maybe localfinesse can chime in and let us know if there are any issues on Pixel 2 XL's phones doing this.
Works very well and very easy to config. Thanks!
Glad it is working for everybody.
Does this technique void the warranty like rooting would?
silverghozt said:
Does this technique void the warranty like rooting would?
Click to expand...
Click to collapse
no, it should not... and I do know someone who rooted their pixel and later needed an RMA for other reasons. their warranty wasn't void and they got a replacement...
edit; scratch my other comment / removed. that u were the same user as the pixel 2 Xl user.
Swap back and recent button
I have found a quick fix to swap the navigation buttons instead of going through the root and downloading, blah blah blah. The only issue is that when you do this, many of your toggles/menus in settings and google apps will be reversed on your screen. This isn't an issue for me because the priority is getting these two buttons reversed more than anything else.
Settings
System
(Tap) 'About Phone' 7 times
"You are now a Developer"
Go back to System menu
Developer Options
Scroll down to 'Drawing'
turn on 'Force RTL layout direction'
Finished
Your navigation buttons are now flipped.
You will now notice when you go into many Google apps, everything will be from right to left now. Your contacts dots will be on the right now. If this is an issue, then go back and switch it back and go through the download process to fix the navigation bar on its own.
T
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Thank you so much. I tried the other method but it didnt work for me but your one worked flawlessly and instantly. You helped me a lot.
Menu button
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
I am curious if this method could be used to bring back the menu button, since long press on the recent apps button opens multitasking. Thoughts?
There is also an app in Playstore called Custom Navigation Bar that lets you do some cool things.
https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner&hl=en
Kentguy86 said:
I am curious if this method could be used to bring back the menu button, since long press on the recent apps button opens multitasking. Thoughts?
Click to expand...
Click to collapse
It is a bit wordy and you need a png for your system to point to and use but yes, you can add a menu button this way:
adb shell
settings put secure sysui_nav_bar "key(82:file:///storage/emulated/0/custom/ic_sysbar_menu.png),recent;home;back,space"
My png is in a folder on my internal sdcard in a folder called custom.
{
"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"
}
Or add dpad left and right
settings put secure sysui_nav_bar "key(21:file:///storage/emulated/0/arrowleft.png),recent;home;back,key(22:file:///storage/emulated/0/arrowright.png)"
You have to link to a png because there's no native icon any longer?
You are the man!
Worked like a charm! Thanks a million! It's instant, too.
fatphatboy88 said:
I figured it out with a lot more searching and trying a lot of different things. Here is what works for me. I have restarted the phone multiple times just to make sure the settings would stick
You have to install the ADB and fastboot
plug you phone into your computer
turn on debugging mode
open up a command prompt window in the adb folder on your computer
these are the following commands I used. I did notice if you have small hands you could type ";home;recent,back" and it will put the home icon in the middle and the other two buttons on the right. What ever button you put the semi colons around will be in the center of the screen.
adb shell
settings put secure sysui_nav_bar "space,recent;home;back,space"
Click to expand...
Click to collapse
Anyone tried this on P w the gestures enabled?
settings put secure sysui_nav_bar "space,recent;home;back,space"
i am Confused.
Does Space means we have to press space button before coma .
Or Does it mean we havr to copy paste comand as its written.
I am soory but what doest space means?
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire TV so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. It is set to a 'root user' but the user is ONLY root in three tiers explained here. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire TV so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. It is set to a 'root user' but the user is ONLY root in three tiers explained here. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
Click to expand...
Click to collapse
Tried it on my 2nd gen fire stick (not rooted), nothing, but I think it'd work if I could disable alexa. The alexa_enabled flag doesn't do anything. Maybe we could work together, seeing as you don't have a fire stick?
Nootboot64 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire TV so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. It is set to a 'root user' but the user is ONLY root in three tiers explained here. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Tried it on my 2nd gen fire stick (not rooted), nothing, but I think it'd work if I could disable alexa. The alexa_enabled flag doesn't do anything. Maybe we could work together, seeing as you don't have a fire stick?
Click to expand...
Click to collapse
What happens when you try to set up the assistant and what version of the Google app are you using
DragonFire1024 said:
What happens when you try to set up the assistant and what version of the Google app are you using
Click to expand...
Click to collapse
I already had my voice set up previously and I'm using the latest. I'll have to find out which one that is when I get home.
EDIT: It is version 10.20.2.21.arm
Nootboot64 said:
I already had my voice set up previously and I'm using the latest. I'll have to find out which one that is when I get home.
EDIT: It is version 10.20.2.21.arm
Click to expand...
Click to collapse
On the HD I have to start with the Google app 8.33.5 beta. Then setup your assistant doing the ADB steps reboot and then you can let it auto update to the latest version that's how I've been doing it.
DragonFire1024 said:
On the HD I have to start with the Google app 8.33.5 beta. Then setup your assistant doing the ADB steps reboot and then you can let it auto update to the latest version that's how I've been doing it.
Click to expand...
Click to collapse
Thank you, I'll try that
Nootboot64 said:
Thank you, I'll try that
Click to expand...
Click to collapse
Also note that I have made the Google app system application because we have root but I don't know if that matters. not sure if you guys are rooted or how that happens with the stick.
Nootboot64 said:
Thank you, I'll try that
Click to expand...
Click to collapse
One more thing it's important to remember that when you have your assistant setup from ADB also set up the voice commands and what not. That's important because the idea is to have your voice commands already set up when the Google app updates. As long as that happens you won't have to go back and setup assistant with your voice all over again. As long as it remembers your settings from the beta version of the old app the new app version will also take on those settings, voice included. I think that was the main problem before is it wasn't doing that and something else internally with the Google app wasn't allowing you to save your voice commands to the device again. would you still can't do so don't try and go and set up the voice again because it won't work you'll have to downgrade back to the 8.33 version and start all over.
you can also uninstall delete or do whatever you want with the two Amazon applications that have to do with the speech user interface and speech interaction manager they have nothing to do with anything that goes on with the Google app or the assistant or anything Android for that matter.
Where can I get the Google app 8.33.5 beta
thx
yenmax said:
Where can I get the Google app 8.33.5 beta
thx
Click to expand...
Click to collapse
Maybe you can just use google search?
https://www.google.com/search?q=Google+app+8.33.5+beta
https://www.apkmirror.com/apk/google-inc/google-search/google-search-8-33-5-release/
Do we need to have Google Play Services on the Firestick for this to work? Or will installing the Google app be enough?
gogorman said:
Do we need to have Google Play Services on the Firestick for this to work? Or will installing the Google app be enough?
Click to expand...
Click to collapse
I'm pretty sure assistant will only work with play services but I could be wrong. I do know there's somewhat of an assistant ability built into Google go. But it is not nearly as sophisticated.
Sent from my Google Nexus 10 using XDA Labs
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better
How can I disable double tap of home button who activates the "voice input", who is no longer avaible as Amazon decided... THANKS THEM
DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
The more who confirm this, the better
Click to expand...
Click to collapse
Hi DragonFire1024,
Thanks for this very interesting post I was just wondering by to see if anyone had unlocked the bootloader :laugh:
Problem with the fire phone is probably 98% of users here use one of @ggow custom ROM's LineageOS 11 or the AOSP based SlimKat and Nexus Rom. Those running the Stock ROM are likely not interested in development hence why no reply's.
To be honest I never even gave the Fire OS a chance before rooting and switching to the Nexus ROM. I am not sure our fire OS has Alexa :silly: or at least as we know it today yes you heard correct a Premium Amazon Device and they see fit not push it out to Amazon device owners. In fact they just went one better and removed the voice service altogether. https://forum.xda-developers.com/fire-phone/general/amazon-voice-services-fire-phone-t3681235 Pretty amazoning :laugh
I was kinda hoping it was to make way for Alexa and a Massive OS Update but I guess thats just wishful thinking. :laugh:
Help me out guys... TCL Android TV (55 P8S). Every time a button is pressed on the remote it utters a confirmation noise. Infuriating. I can't seem to find any menu to change button-press noise confirmation off. Any thoughts? It's like listening to a teenager texting in the mid 2000s lol.
On p8m it's in sound options or system settings (don't remember exactly). Not the android settings of course.
Hope you found your answer.
If not :
Go Settings > Sound > Advanced Settings > Sound Feedback > Off
I have a TCL P8M and this worked for me. In case yours is slightly different, go ahead and fiddle around till you find 'sound feedback' which is usually in Sound settings.
This can be fixed with ADB.
1. Enable ADB debugging on device
2. install ADB on your computer.
3. Start a shell (cmd for example if Windows) on computer, if ADB is not in your $PATH variable - navigate to folder where it's installed
4. Find the device IP of your Android TV
5. Connect to the TV using ADB from your computer:
NB! Replace the all of the X characters with the IP of your TV, e.g: 192.168.0.2:5555
Code:
adb connect x.x.x.x:5555
6. On the TV, allow ADB device
7. Run the following command in your shell on the computer:
Code:
adb shell settings put system SOUND_EFFECTS_ENABLED 0
I dont have the setting on my TV and the adb command dosent fix the problem.
Help?
please try:
adb shell settings put system sound_effects_enabled 0
this fixed the issue for me. It had to be small letters in my case.
There is also this apk if anyone in the future doesn't want to use adb
iangry0/TCLButtonSound: Disables or enables TCL android TV button sound (github.com)
TheNoobIsHere said:
There is also this apk if anyone in the future doesn't want to use adb
iangry0/TCLButtonSound: Disables or enables TCL android TV button sound (github.com)
Click to expand...
Click to collapse
Hello,
sorry for my ignorance. How can I use TCLButtonSound, can I obatain an apk files? I'd like to try to mute my menu sounds in a Telefunken tv.
.
Currently, in Wear OS there are four methods (that I know of) for installing apps on the watch, each more convenient to use depending on the situation:
The first method, is the obvious one, that is, through the Play Store of the watch, you search for the app you are interested in, install it and that's it. In the watch's search engine, only apps optimized for Wear OS will appear.
The second method, is installing apps from a computer and through ADB commands. This method should be used when you want to install from your computer applications that are not found in the Play Store. With this method you could install any android application whether it is optimized for Wear OS or not. I explain this method in the section "Install apps from a computer (ADB commands)". You can use "Wear OS Tools" for Windows to facilitate the whole process.
The third method, is installing apps from the phone, using an app called "Bugjaeger Mobile ADB". The app is an ADB command emulator that can be run from an android phone. This method is recommended when you want to install an app that is not found in the Play Store, or the app is not optimized for Wear OS. Below, I explain in more detail in the section "Install apps from the phone (Bugjaeger Mobile ADB)".
There are other apps that are recommended in the same situations as for Bugjaeger, they are "Wear Installer 2" or "Easy Fire Tools".
The fourth method, is installing apps from the phone, using an app called "Wear Installer" (by the developer u/malbry). This method is recommended when the application not found in the Play Store and you want to install uses the old embedded application model, which means that the version of an app for Wear OS is added inside the version for Android phones. This application filters the applications installed on the phone (or simply downloaded to the internal memory) that contain the app optimized for Wear OS. When you choose to install, it sends it over Wi-Fi and installs the Wear OS-specific module that is contained within the phone app. In the section "Install apps from the phone (Wear Installer)" I explain how to install it. A help page for Wear Installer is here.
Important when you want to use the installation methods: "Allow Debugging"
When you first connect your watch via apps like Wear Installer, Bugjaeger, Wear OS Tools, or even with ADB commands, the watch will show a notification asking "Allow debugging?", select "Always allow from this computer". If you do not allow debugging you will not be able to connect.
{
"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"
}
If the notification is not displayed, go to Settings > Developer Options, and select "Revoke debug authorizations" and try to connect again.
2nd Method. Install applications from a computer (ADB commands)
This method should be used when you want to install from your computer applications that are not hosted on the Play Store. With this method you could install any android application whether it is optimized for Wear OS or not. The steps for Windows environment are as follows:
1. If you have not done it yet, prepare watch for advanced functions:- On the watch, go to Settings > system > About and repeatedly tap "Build number" until You see a message that says 'You are now a developer'. Then go to Settings > developer options and enable 'ADB debugging' and 'Debugging over Wi-Fi '.- On your computer, download and install the ADB tools, such as Tiny ADB & Fastboot.2. On your computer, open a command window, to do this in Windows type 'cmd' in the toolbar.3. Then enter the following command to connect to the watch. Then accept a message on the clock that allows the computer to connect.
Code:
adb connect watch_ip:5555
4. Now, it is the step to send the APK application to the watch, install it and delete APK file finally. Make sure to enter the path correctly in the following commands.
Code:
adb -e install filename.apk
Alternatively, you can use Wear OS Tools for Windows, which will make it easy to install apps via ADB commands.
3rd method. Install apps from the phone (Bugjaeger Mobile ADB / Wear Installer 2)
Another alternative, in this case from the phone and via Wi-Fi, is to use the Bugjaeger Mobile ADB app (also Wear Installer 2" or "Easy Fire Tools"). You don't need to install anything on the watch, the app is an ADB command emulator that can be run from an android phone. To connect and be able to run the functions, just do the following:
On the phone, download Bugjaeger here and install from Play Store.
On the watch, If you have not yet done so, go to Settings > System > About and tap "Build number" several times until you see a message that says "you are now a developer". Then go to Settings > Developer options and enable "ADB debugging" and "Debugging over Wi-Fi".
Make sure both your watch and mobile are connected to the same Wi-Fi network, momentarily disable Bluetooth on your watch if Wi-Fi is not enabled on the watch. Now go to Settings > Connectivity > Wifi, click on the network you are connected to and enter the IP of your network.
In the Bugjaeger app on your phone, click on the plug icon, enter the IP of your network and click "Connect".
When connected, you will see a notification appear on your watch where you have to give permission to link the phone to the watch, so click on "Always allow from this computer". Now in the app you will see the notification "Connected".
Now go to the "Packages" tab, click on the "+" icon at the top, and choose to install on the watch an APK file that is downloaded to the phone, or an application installed on the phone.
4th Method. Install apps from the phone (Wear Installer).
This method should be used when you want to install from the phone applications that are not hosted on the Play Store, however these apps must be optimized for Wear OS. The steps for installing and using Wear Installer are as follows:
On the phone, download Wear installer here and install from Play Store.
On the watch, If you have not yet done so, go to Settings > System > About and tap "Build number" several times until you see a message that says "you are now a developer". Then go to Settings > Developer options and enable "ADB debugging" and "Debugging over Wi-Fi".
Make sure both your watch and mobile are connected to the same Wi-Fi network.
On the phone, open "Wear installer" app, enter the IP of your network and press OK. You will see 2 tabs, the first one is the list of all the apps installed on your phone, and the second tab is the list of the apps you have downloaded to the phone (APK files) and found in the "Download" folder.
Select the app you want to install on the watch, it must have the Wear OS APK inside for it to be installed. Accept the debugging on the watch and Wear Installer will extract the component, send it and install it on the watch.