Can someone explain this in layman's terms?
Gökhan Moral's port of Voodoo Sound implemented. Currently no configuration interface is available, so if you wish to play with the settings, refer to the sysfs interfaces in /sys/class/misc/scoobydoo_sound/ . If you wish to change the device name, you must do echo 0 > /sys/class/misc/scoobydoo_sound_control/enable , followed by an echo output to the same file with the target device driver name. You can use this to change the device path to /sys/class/misc/voodoo_sound/ and sub-sequentially make a certain configuration application work. Please do not ask me for support on the latter. You can disable the sound modifications completely by the same method, by of course not re-enabling it afterwards.
Can someone explain this in layman's terms?
Gökhan Moral's port of Voodoo Sound implemented. Currently no configuration interface is available, so if you wish to play with the settings, refer to the sysfs interfaces in /sys/class/misc/scoobydoo_sound/ . If you wish to change the device name, you must do echo 0 > /sys/class/misc/scoobydoo_sound_control/enable , followed by an echo output to the same file with the target device driver name. You can use this to change the device path to /sys/class/misc/voodoo_sound/ and sub-sequentially make a certain configuration application work. Please do not ask me for support on the latter. You can disable the sound modifications completely by the same method, by of course not re-enabling it afterwards.
I posted this as a reply on another thread, but as hard as it was for me a figure out a workaround for diag mode that doesn't involve the dialer codes, or trying to force the hidden menus with shortcut apps. If you don't have a dialer (Not included in the factory reset, for some odd reason...) there is seemingly NO WAY to get diag/modem mode actually working, and connecting to DFS or CDMA tool.
For some reason, I factory reset my tab, and it allowed me to add root perms during the reset, but now I have no phone or dialer app, and even if I install the official google dialer.apk it won't register the special codes for diag/modem. I tried anycut, and the quickshortcut guy, and when I hit any of the shortcuts it'll tell me "application not found." So I'm unable to activate diag/ modem mode through the gui...
BUT i found a script for an LG phone, that actually works to enable diag/modem mode on the tab 3 (t217s).
Download Smanager (script manager) from the play store.
Make sure you have root access (option when you factory reset, poot, towelroot... etc...)
PHP:
#!/system/bin/sh
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 631B > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo tty > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag,diag_mdm > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
Create a new script with this, and make SURE YOU CLICK "SU" when you save to run the script with root access. It will setup modem/diag mode, but it will require the LG drivers, because it is expecting that venid/devid.
You can get them here if you don't have them.
cdmatool .com, it's the "LG Electronics driver.zip" package.
(It won't let me post an actual link because I'm a new member)
After I ran the script, I didn't need to even unplug/plug the tablet in order for it to connect to diag mode.
NOTE:
You could change these two lines to pertain to drivers that are more compatible with the hardware in the galaxy tab 3, but it seems to work fine regardless.
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 631B > /sys/class/android_usb/android0/idProduct
I guess let us know if you try changing the vendor/devid to a different, more applicable set of drivers. If it seems to have better functionality, I'd like to know. This script with the LG drivers works for everything I've tried in DFS/CDMA ws, so if anyone encounters problems (presumably from the different drivers) please let me know.
Now, get out there and flash some tabs!! And please let me know what other carriers you can flash to. I'm curious if it's possible to switch to another CDMA network and simply disable to RIMM/SIM card.
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: