Has anyone tried to apply the video calling over 3G fix yet? I believe that the fix was for Talk 1.3, but it seems that the version on the Galaxy Nexus is running 4.0.1.
I'm able to start a video call from the contacts screen, but I can't initiate one from the chat or when I receive a call.
Sent from my Galaxy Nexus using Tapatalk
k0sun7eash3d said:
Has anyone tried to apply the video calling over 3G fix yet? I believe that the fix was for Talk 1.3, but it seems that the version on the Galaxy Nexus is running 4.0.1.
I'm able to start a video call from the contacts screen, but I can't initiate one from the chat or when I receive a call.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
It works fine for me.
Seeing as how it's merely an entry into gservices.db I don't see how it's version specific unless the newer version doesn't adhere to the old way to doing things. Fortunately it's an easy test and it appears to operate in the exact same manner.
That's great to hear. I left my laptop at my girlfriend's apartment and I won't be able to get it back to very until the weekend. I'll definitely post a verification once I get the laptop back and rooted.
Out of curiousity, did you input the string manually or use one of the apps available in the market?
k0sun7eash3d said:
That's great to hear. I left my laptop at my girlfriend's apartment and I won't be able to get it back to very until the weekend. I'll definitely post a verification once I get the laptop back and rooted.
Out of curiousity, did you input the string manually or use one of the apps available in the market?
Click to expand...
Click to collapse
It's very easy to do manually, no reason to try to rely on some app Before you make any changes I'd suggest backing up gservices.db in case it gets hosed somehow.
Code:
Pull /data/data/com.google.android.gsf/databases/gservices.db
Edit with sqlite3 (part of the SDK): sqlite3 gservices.db
insert into overrides (name, value) VALUES ('gtalk_vc_wifi_only', 'false');
ctrl-c to break
Push gservices.db back to the device and reboot
If you don't have an insecure boot image (I don't use one) you can use the sd card to stage for the pull and the push (you'll need to be root).
Code:
adb shell
$ su
# cp /data/data/com.google.android.gsf/databases/gservices.db /mnt/sdcard/gservices.db
Exit the shell or use a second console to adb pull /mnt/sdcard/gservices.db
sqlite3 gservices.db
insert into overrides (name, value) VALUES ('gtalk_vc_wifi_only', 'false');
ctrl-c
adb push gservices.db /mnt/sdcard/gservices.db
# cat /mnt/sdcard/gservices.db > /data/data/com.google.android.gsf/databases/gservices.db
# reboot
Just verified that the process of adding the wifi false value does indeed work. Voice calls can be initiated and received over a 3g data network.
I did run into a couple of issues during the process though:
For starters, I'm using a Galaxy Nexus 4.0.1 stock (google) build, XXKK6 radio.
1. I was unable to pull /data/data/com.google.android.gsf/databases/gservices.db through adb. I believe it has something to do with the current version of Superuser not correctly granting root access to adb shell. The workaround I used for this was using a root explorer on the phone and using the app to copy and paste into /mnt/sdcard/gservices.db
2. After pushing gservices.db back into the /data/... folder and rebooting, I was only able to start the video calls. It took another reboot before notifications popped up that I was receiving calls.
This may be due to me having my gmail open on my laptop web browser at the same time, however. I closed it before the second reboot completed. I believe it may have something to do with Google Talk routing the video call to the PC/Web browser client before going to the mobile client, but that is just speculation.
Hello,
I was given a Galaxy Wonder to repair, the problem is the kid who's phone it is, forgot the lock screen password/code nor did he have a google account on the device. And the best part, is he want's the data!
I would backup and flash the device, but adb commands requiring root privileges won't work directly - it complains that "adbd cannot run as root in production builds"...
I got ADB up and running and installed "su" (root privileges in shell).
I've tried many suggestions with changing and deleting entries in the "data/data/com.android.providers.settings/databases/settings.db" file on the device.
There are no more references left in the "system" or "secure" tables to any kind of "locking". According to many posts the lock screen should not be present after reboot or it should be anything random (or nothing).
Also, I've deleted the gesture and password files from /data/system/...
Nothing has worked to remove the screen lock. Please help.
~confuded
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:
So....I was 'experimenting' with my rooted LG G3 running android 4.4.2 and I accidentally managed to make my Bluetooth unusable (greyed out) while using 'ROM Toolbox' App.
I accidentally made it a system app, and then used Titanium Backup Pro to convert it back to a user app, but it still remained greyed out. I then tried using ADB to turn it back on using the following from another post;
adb shell service call bluetooth_manager 6' (I've tried a few numeric variables but none seem to work),
then I tried;
adb shell
su
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
That didn't work either as I got this error 'app_process has text relocations. This is wasting memory' etc......I think this is because I have Xposed Framework installed also.
Next I tried sQlite,
sQlite3 settings.db
update global set value=1 where name='bluetooth_on';
Then I got the error..... no such table: global
I'm not a developer but I do enjoy messing around with these things, until it all goes wrong of course......I know I could un-root and see what happens, but I'd rather try and figure this out rather than go through the hassle of rooting again...Anyone have any ideas how to turn my Bluetooth back on? Thanks......