Video over gsm has been disabled on the device. If you are rooted, you can make a simple database edit to allow video over 3g. If you have already done the edit 2 weekes ago, its possible that there may have been an update and causing you to have to redo the change
Sent from my SAMSUNG-SGH-I747 using xda premium
Sent from my SAMSUNG-SGH-I747 using xda premium
Can you link me to the database edit please?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
There is an app on Play store for Root that allows this. https://play.google.com/store/apps/details?id=com.innodroid.gtalkenabler&hl=en
Here, you go, i just did it and it works perfect!
1. Download SQLight editor from the market
2. If you don't have a good file manager also get Root Explorer from the market.
3. After both are installed - use Root Explorer to browse to /data/data/com.google.android.gsf/databases/gservices.db and click on it
4. Now click on "main"
5. Scroll down to gtalk_vc_wifi_only - highlight and hold
6. Press "Edit Record" and change the "value" to false instead of true
I open Google Talk and click the camera icon next to a contacts name.
I don't really use hangouts.
I don't really use hangouts.
I did the procedure. Now I'm not getting the error when I select the Gtalk Enabler, then I reboot, go to talk, press video chat icon with whomever I want to video chat, it starts ringing a couple (2) of times (before I used to get the wi fi message), then it cuts out and it displays on the recepients box the following message: "Sorry! The video chat with Anglo (that's me) failed because of a problem with our servers at 11:15 AM. Please wait a bit and try again."
However, if I use Vtok this error doesn't happen.
Any help will help appreciated.
I'm having the same problem. I made the database fix, which now lets me attempt a video call without getting the wi-fi only message. But when the other side tries to answer the call, I get disconnected and they get an error saying that GTalk servers have an error.
Has anybody else gotten video chat to work on the SG3? If so, what other step do I need to take? And I don't really want to load another app to do what this one is supposed to do.
That sounds like a different problem. Mine shows the video camera icon on wifi and also on 3g, but it will only connect when I'm on wifi.
Just did this on my SGSIII and worked perfectly...Thanks!
The Gtalk Enabler worked while I was on CM10 but the bluetooth worked horribly so I went back to the stock JB rooted. I tested after I made the change and will uninstall the enabler now.
Last edited:
I looked at this database, and I don't see "gtalk_vc_wifi_only" in that database. If the key is not there, do I need to add it?
Ok, you're right. I downloaded the db to my PC, edited it and loaded it back onto the phone. Problem is that Gtalk video calls still don't work on my AT&T S3 even after the db change. Are other AT&T S3 users getting this to work?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7
Here, you go, i just did it and it works perfect!
1. Download SQLight editor from the market
2. If you don't have a good file manager also get Root Explorer from the market.
3. After both are installed - use Root Explorer to browse to /data/data/com.google.android.gsf/databases/gservices.db and click on it
4. Now click on "main"
5. Scroll down to gtalk_vc_wifi_only - highlight and hold
6. Press "Edit Record" and change the "value" to false instead of true1Video over gsm has been disabled on the device. If you are rooted, you can make a simple database edit to allow video over 3g. If you have already done the edit 2 weekes ago, its possible that there may have been an update and causing you to have to redo the change
Sent from my SAMSUNG-SGH-I747 using xda premium1
There is an app on Play store for Root that allows this. https://play.google.com/store/apps/details?id=com.innodroid.gtalkenabler&hl=en1
Just did this on my SGSIII and worked perfectly...Thanks!
The Gtalk Enabler worked while I was on CM10 but the bluetooth worked horribly so I went back to the stock JB rooted. I tested after I made the change and will uninstall the enabler now.1
In case anyone is still having this problem, I found that copying that entry from "main" to "overriides" and then changing it to false, will keep functionality. The entry in main will revert to true, but the one in overrides will stay set to false and will take precedent.
