Hi Guys,
I have updated the device to TnT 2.0, thanks to the develoeprs and XDA forum. However, I am facing an issue in terms of calling over WiFi. Are calls over Skype, Fring or Nimbuzz working? Neither me nor a person whom I am calling can hear over Skype even thought the call connects smoothly in Skype. In Fring I here the jittery noise and no voice communication exchange possible.
Are you guys facing the same issue? Any fix for this ?
Thanks really appreciate all the help.
Regards,
Neil
Skype is working for sure, with the usual quality. My jawbone just took a sh!t so I can't say for sure that you can hear the party you're calling. But they can hear me, so I'm pretty confident that all is well.
Skype works it just mutes on first dial so you gotta unmute first.
FWIW at least on sipdroid and the built-in speaker, I cannot hear the other party during a call. However, they can hear me. I haven't tried skype yet though.
Hannigan174 said:
Skype works it just mutes on first dial so you gotta unmute first.
Click to expand...
Click to collapse
Good to know!! I didn't check, that was too obvious!! haha
VOIP calls on G-Tablet with Sipdroid + Google Voice
After weeks of trying different apps to be able to make and receive calls on the G-Tablet I've had success. (Rooted G-Tab running TnT Litev3.1.0, Android 2.2)
The info is from a post I came across at http://androidforums.com/android-applications/252222-google-voice-pbxes-org-sipdroid-free-calls.html.
The poster references the following blog which also has some helpful information for setting up correctly:
http://blog.kylehasegawa.com/google-voice-voip-on-android-just-got-a-lot-easier-with-pbxes-peering
Read through it but basically it is:
Get a google voice number and then install google voice app on G-Tablet
When you are in google voice on your computer click on "settings" and then the "phone" tab. Make sure that "Google Chat" has a check mark to the left of it indicating that it is a forwarding option. If it is not listed there, you need to enable Google Chat which you can do in Gmail (it's an option on the left side of your inbox).
Install sipdroid (free in market)
Run sipdroid and click the link at the bottom that says new PBX linked to my google voice
Verify your google voice account email is correct and enter your google voice password. Then enter a pbxes.org password which can be anything you want it to be.
Once you do that, pbxes and sipdroid will auto configure everything else.
To make calls you will need to use a headset plugged into your GTablet in order to hear your caller. My experience is that on the GTablet side I could hear the caller perfectly. They could hear me well, but there was a slight echo where they would hear themselves after they spoke.
leslye said:
Run sipdroid and click the link at the bottom that says new PBX linked to my google voice
Verify your google voice account email is correct and enter your google voice password. Then enter a pbxes.org password which can be anything you want it to be.
Once you do that, pbxes and sipdroid will auto configure everything else.
Click to expand...
Click to collapse
I realize this post is a bit old but it was all I could find so I thought I'd try and get an answer anyways...
So I followed the instructions above and it worked great. After, I installed another dialer app (stupid) which didn't work so I uninstalled it. Afterwards, GV no longer worked. I uninstalled and reinstalled with no luck so I uninstalled sipdroid.
After reinstalling that, I no longer had the option to auto config. When I click the button and put in a new PBX name, I get a message stating that the trunk is already in use. I attempted to configure manually but when I put in the user name and password I originally typed it doesn't appear to log into the server and I get a 'Mobile network not available' error.
I can't seem to remove all the previous sipdroid connections and I can't find any folders to delete after uninstalling it. I've cleared data but when reinstalling the app, I am no longer asked for my google voice number and the web site doesn't help much with manual configuration.
I created another google voice account but even after I reinstall GV and configure it using the new number, the SIPDROID still tells me the old VG account name. I assume it pulls it from elsewhere in the system.
So can anyone tell me how to manually configure this thing or how to remove all the previous sipdroid settings so I can start from scratch?
-Maj
Hi all, sorry for the new guy question (at least that's what I think it is):
Problem Statement - I have my phone set up to make all calls through google voice. This works fine. However, the phone.apk and thus the call log always shows the google voice routing number as opposed to the person I am actually calling.
Review - I have done some searching and it appears this is the same thing on, at least, some other devices (SIII for one). I have not found any way to "fix" this, however, and am reaching out here. It may be an LG thing or an ICS thing or no thing at all.
Solutions:
Question 1 - does anyone know if there is any solution to this?
Question 2 - in doing some looking around it seems that the best approach might be to try a different phone.apk. The best approach I have seen, but have not yet tried, is to download the stock ICS phone.apk from here: http://forum.xda-developers.com/showthread.php?t=1735507 or something. change permissions to rw-rw-rw- and copy into system/app . will this work? What is in there now is LGphone.apk, do I have to change the name of phone.apk to LGphone.apk?
Thanks in advance for any consideration of this.
Best Regards,
Dave
I'd like to find a resolution to this issue as well. it's rather frustrating. and no, i will not be adding the Google Relay# to my contact list as a workaround. i just want the call log to report the contact i called..
Anyone find a solution yet?
I figure once the AOSP 4.2 roms have their camera and GPS issues sorted out, I won't be bothered by this issue any more.
Sent from my LG-E970
GV outbound call log repair
The only way I found was to install this app called GV Outbound Call Log Repair. I've tested it and it does work. This app seems to periodically wake up, contact GV and replace the number in the call log with GV call log number.
saratv said:
The only way I found was to install this app called GV Outbound Call Log Repair. I've tested it and it does work. This app seems to periodically wake up, contact GV and replace the number in the call log with GV call log number.
Click to expand...
Click to collapse
Thanks for sharing. I just bought it and it's working great so far. The only concern I have is that it syncs your call log every 30 seconds which seems like a battery drain. I wish you could set how often it syncs. At any rate any fix is better than none :good:
Hi all
Just got the Gear S, do not own a Samsung Phone, using it standalone (for now).
Anyone figured out how to add contacts to the watch?
I select "Contacts" from the menu. All that is happening is the spinning animation with the text "Syncing contacts". I can't add a contact from the message app or the call log either.
I dont want to go back to memorize numbers again.
edit1: tried to add some contacts to SIM card. Not picked up by the watch.
edit2: added some contacts to SIM card. They do appare on incoming calls, and appares in phone application when searching in the dialer.
You can't. Majority of the functions of this watch requires a Samsung phone. The only thing you can do is make or receive calls, send or receive SMS. That's about it. Some built-in apps may work (weather, HERE) to certain extent. Most apps won't without a phone.
foxbat121 said:
You can't. Majority of the functions of this watch requires a Samsung phone. The only thing you can do is make or receive calls, send or receive SMS. That's about it. Some built-in apps may work (weather, HERE) to certain extent. Most apps won't without a phone.
Click to expand...
Click to collapse
Yepp, unpaired and alone this thing is dumber than a dumbphone. Not a problem for me actualy, I have a dual sim phone, so I just dump all the contacts to the sim card. I can see who's calling me and search my name in the dialer. The "contact" homescreen does not work, but that is fine by me.
hestflott said:
Yepp, unpaired and alone this thing is dumber than a dumbphone. Not a problem for me actualy, I have a dual sim phone, so I just dump all the contacts to the sim card. I can see who's calling me and search my name in the dialer. The "contact" homescreen does not work, but that is fine by me.
Click to expand...
Click to collapse
Thanks for the info. I'm looking to run the gear s as stand alone and getting my contacts to appear was the main issue holding me back. I was happy to discover the trick about activating it without a Samsung phone and your contact trick might be all I need.
I carry two phones - work and private. My private phone is a phablet that I love (Nokia 1520) which I do all my emailing and browsing on. My work phone is just for calls and sms so the smaller the better (carrying two phones is a pain especially one being a phablet), but I need my contacts to sync via my exchange account so I use a small smartphone (Nokia 800). I'm hoping I can go Nokia 1520 and gear s stand alone using the tricks posted here.
The gear s seems like a perfect solution - I actually need the two phone numbers (and, yes I have thought about a dual sim phone but there are issues with that scenario). Although, I am suspecting that as much as I love my 1520 I might end up getting a Note 4 to make it all more convenient, but I just hate the thought of android, sorry.
My SIM contacts automatically shown in Gear. But i want to add new contacts. Is that not possible?
Akram. said:
My SIM contacts automatically shown in Gear. But i want to add new contacts. Is that not possible?
Click to expand...
Click to collapse
I think Samsung may have out-of-the-box disabled that feature simply for that reason-- to encourage users to have to use it with a phone. However, on the Tizen Developer website they list the source code for a simple contact manager (ah! New user, can't post links yet... just Google the Tizen SDK) that is able to interface the contacts API. This should be pretty simple/straight forward to compile and implement for the watch with the SDK.
I haven't quite made a decision about whether to purchase the S, or if I had more time at the moment, I'd do it. However, my point being the contact restriction I believe is only concerned with the built in contact app... I see no reason why another app should not be able to access it and thus get around the apparent limitation.
Gear S: Contacts App and Delete Contacts
https://www.youtube.com/watch?v=Rymja31CGtU
choong001 said:
https://www.youtube.com/watch?v=Rymja31CGtU
Click to expand...
Click to collapse
how can i do that?
Adding contacts to your Gear S2
You can add contacts. I just did it. You have to log into your online account via your cell phone provider.
Just got the Gear S, do not own a Samsung Phone, using it standalone (for now).
Anyone figured out how to add contacts to the watch?
I select "Contacts" from the menu. All that is happening is the spinning animation with the text "Syncing contacts". I can't add a contact from the message app or the call log either.
I dont want to go back to memorize numbers again.
edit1: tried to add some contacts to SIM card. Not picked up by the watch.
edit2: added some contacts to SIM card. They do appare on incoming calls, and appares in phone application when searching in the dialer.[/QUOTE]
This module enables the use of other SMS apps to send and receive messages through Google Voice. When this module is activated, any SMS messages sent will be rerouted through Google Voice, and any messages that are received by the Google Voice app will be displayed in SMS apps.
Setup:
Download the APK and install.
Open the app, enable it, and select the account you want to use.
Open Xposed, activate the module, then soft reboot.
You will get a notification to sign in to authorizing the app to access your account. Tap the notification, then tap allow. For some reason the notification is not dismissed automatically; you can dismiss it manually.
If the module does not work at this point, try soft-rebooting again.
Known issues:
This module will only work with the old Google Voice app, version 0.4.7.10 or lower. If you already updated to a newer version, you must uninstall it and sideload the old version. You can find the latest working version here. Once you've downgraded, open the Play Store and set the app not to auto-update, so you won't run into the same issue later. This is fixed as of v3.1.2.
When I had the default SMS app is set to the AOSP Messaging app (com.android.mms, not to be confused with Google Messenger), the module would not work for outgoing messages. On one device, incoming messages did not work either. I was using version 5.1.1-720affab4e. I'm still not sure what causes it.
On my S3 test device, I sometimes experienced a crash of the system process on boot. This did not seem to affect the functionality of the module.
There is a known issue with Xposed reading SharedPreferences in certain situations, due to file permissions issues. With this module, this would cause that disabling the module from within its own settings would not help, and the only option would be to deactivate the module from inside Xposed Settings and soft-rebooting. I added some code to work around this, however it's possible that it could still occur. This is fixed (hopefully) as of v3.1.2.
Old issues:
Many of the old bugs present in the original XVoice+ are still in this version. These include:
Emojis may cause issues. (This issue should be fixed for incoming messages as of v3.2.0).
There is no support for MMS
Occasionally, messages may show up with the wrong timestamp, there may be duplicate messages, or there may be a delay before the messages appear.
Google Voice 5.0+
As mentioned above, the module will not work with the new updates to Google Voice. This is because they completely rewrote the code for the app, which would require XVoice++ to be rewritten as well to properly hook it. This is further complicated by the fact that Google obfuscated the code, making it much harder to figure out what is going on. Additionally, it is probable that with every update the code will be obfuscated diferently, requiring XVoice++ to be patched every time to support the new update. Since the whole point of this module is to replace the functionality of the Google Voice app, and it is functional with the old version, I will not be working on supporting the new versions of the app at this time. This is fixed as of v3.1.2.
Devices tested on:
Verizon LG G3 (vs985) running a custom build of CM 12.1
Sprint Samsung Galaxy S3 (d2spr) running CM 13.0 (11/17/2016 nightly) without phone service
Acknowledgements:
Koush
CM team
@runnirr
@B2OJustin
@iHelp101
Jake Hamby (a former engineer at Google, who helped maintain the internal SMS processing code for Android) for providing a lot of information about PDU structure and processing, and patiently answering my questions.
Xposed Repo
XDA:DevDB Information
XVoice++, Xposed for all devices (see above for details)
Contributors
BehindTheMath, @runnirr, @B2OJustin, @iHelp101
Source Code: https://github.com/BehindTheMath/XVoicePlus
Xposed Package Name: io.behindthemath.xvoiceplus
Version Information
Status: Stable
Current Stable Version: 3.2.1
Stable Release Date: 2017-05-08
Created 2017-02-15
Last Updated 2017-05-08
Reserved
Reserved
Nice to see something happening with this. I more or less abandoned it after switching over to Hangouts. What are your plans for it though? I'd probably consider hooking into Hangouts for any future development.
Edit: Btw, this latest source has also been tested and confirmed working on Nexus 7 stock (without cell service) and at least one other phone with a touchwiz based rom + smart watch (Don't recall which kind). Though rom updates may or may not have changed that since then.
B2OJustin said:
Nice to see something happening with this. I more or less abandoned it after switching over to Hangouts. What are your plans for it though? I'd probably consider hooking into Hangouts for any future development.
Edit: Btw, this latest source has also been tested and confirmed working on Nexus 7 stock (without cell service) and at least one other phone with a touchwiz based rom + smart watch (Don't recall which kind). Though rom updates may or may not have changed that since then.
Click to expand...
Click to collapse
Thank you for the feedback.
Truthfully, in my humble opinion, this app is mature. You guys have done a fantastic job of taking Voice+ and adapting it to a new platform. I only needed to fix the issues caused by new or changed Android internal code. Unless someone has a specific feature request, I think it's ready for a stable release.
That being said, there are a few things I would like to look into at some point in the future. The main one is the viability of supporting the new GV app. I never liked Hangouts. It was slow when it was first released, and it's still slow and buggy. 90% of my contacts use Whatsapp, and the GV app along with XVoice+ helped me with the handful that still use SMS. The only reason I still have Hangouts installed is to manage multiple accounts, and for VoIP calls. Now that the new GV app supports the former, and it looks like the latter is coming at some point, I would love to have XVoice++ support it so I could get rid of Hangouts entirely.
I am happy to see you figured out what I was unable to. In terms of Google Voice 5.0 you could in theory hook GCM messages directly. The class is "com.google.android.gms.gcm.GcmReceiver". You would use the same onRecieve hook already in the module. I have never seen GMS code obfuscated, so you likely would not have to worry about it. Even if a GCM message for some reason is not a text message the module would be able to filter it out (It checks the Intent contents).
iHelp101 said:
I am happy to see you figured out what I was unable to. In terms of Google Voice 5.0 you could in theory hook GCM messages directly. The class is "com.google.android.gms.gcm.GcmReceiver". You would use the same onRecieve hook already in the module. I have never seen GMS code obfuscated, so you likely would not have to worry about it. Even if a GCM message for some reason is not a text message the module would be able to filter it out (It checks the Intent contents).
Click to expand...
Click to collapse
That's an interesting approach. I'll have to look into it when I have time.
THANK YOU!
OP first of all thanks for doing this!
Second I have a question, I'm still running CM11, because I use Voice+, the original utility that XVoice+ was based on. I have updated my google voice app to the latest version and Voice+ still works, I'm not sure how. You might consider looking at the source code for Voice+ and see if the type of hooks it uses are possible with xposed.
Again thanks for what you have already done.
KnightTim said:
OP first of all thanks for doing this!
Second I have a question, I'm still running CM11, because I use Voice+, the original utility that XVoice+ was based on. I have updated my google voice app to the latest version and Voice+ still works, I'm not sure how. You might consider looking at the source code for Voice+ and see if the type of hooks it uses are possible with xposed.
Again thanks for what you have already done.
Click to expand...
Click to collapse
Voice+ works for you for incoming messages too?
Edit: I looked through the source for Voice+. They listened for the notification from the GV app, and then canceled it, which meant you had the notification flash for a second before being intercepted by Voice+. One of the benefits of XVoice+ was that you could disable the notifications completely in the GV app, and XVoice+ would intercept the message anyway.
iHelp101 said:
I am happy to see you figured out what I was unable to. In terms of Google Voice 5.0 you could in theory hook GCM messages directly. The class is "com.google.android.gms.gcm.GcmReceiver". You would use the same onRecieve hook already in the module. I have never seen GMS code obfuscated, so you likely would not have to worry about it. Even if a GCM message for some reason is not a text message the module would be able to filter it out (It checks the Intent contents).
Click to expand...
Click to collapse
I looked at the GV 5.0 code some more. I couldn't figure out how to hook com.google.android.gms.gcm.GcmReceiver, but I was able to hook the com.google.android.apps.voice.backends.gcm.GcmListenerService, which is the entry point for the message in the GV app. It appears to be very easy to intercept the messages from there. The issue is, since GV 5.0 added support for multiple GV accounts, there's no easy way to tell which account the message is for. The GCM message comes with a user_hash field, but it's just a hash, and I can't find a list of corresponding accounts in SQLite or in SharedPrefs. I presume it's decoded somewhere in the app, however, the only code that references it is obfuscated. It would technically be possible to implement a setup routine which would send a test message and grab the user_hash for that message, but that's a bit inelegant.
BehindTheMath said:
I looked at the GV 5.0 code some more. I couldn't figure out how to hook com.google.android.gms.gcm.GcmReceiver, but I was able to hook the com.google.android.apps.voice.backends.gcm.GcmListenerService, which is the entry point for the message in the GV app. It appears to be very easy to intercept the messages from there. The issue is, since GV 5.0 added support for multiple GV accounts, there's no easy way to tell which account the message is for. The GCM message comes with a user_hash field, but it's just a hash, and I can't find a list of corresponding accounts in SQLite or in SharedPrefs. I presume it's decoded somewhere in the app, however, the only code that references it is obfuscated. It would technically be possible to implement a setup routine which would send a test message and grab the user_hash for that message, but that's a bit inelegant.
Click to expand...
Click to collapse
Interesting, it is a nice discovery to have been made. Google has gone extremely with obfuscation recently. I also didn't realize they added multi-account support. My bad for giving any false.
iHelp101 said:
Interesting, it is a nice discovery to have been made. Google has gone extremely with obfuscation recently. I also didn't realize they added multi-account support. My bad for giving any false.
Click to expand...
Click to collapse
No, I think your idea is the best option for supporting GV 5.0. We just need to figure out how to identify the accounts. I'm going to try to dig through the code some more.
It has been a while since I've played with Xposed but when I get a little extra time I'll see what I can come up with. Figuring out exactly what to hook has always been the troublesome part though. If it turns out you do need to make use of the account hashes, I'd suggest looking lower in the callstack rather than higher. ie; Find the source of the hashes instead of the final target. You can then map those to usernames as soon as they're generated.
v3.1.2
I've released a new version, v3.1.2. The primary new feature in this version is support for Google Voice 5.0+.
I spent some more time poking through the GV sources, and I found that the list of accounts and corresponding user_hashes are stored in a Base64-encoded field in SharedPreferences called "registered_accounts". I added some code to decode the list and check the incoming message against user_hash of the account we want.
I also released the module on the XPosed Repo, so now it can be installed through the Xposed Installer.
Unfortunately, I lost the password to the signing key. I created a new key, but this means you will need to uninstall the old version before installing the new one.
New user. Tested on Voice 5.0+. Works flawless so far! This is excellent!
I have no idea why Google decided to NOT allow the Voice 5.0+ to be default SMS app.......but this module works around that issue AND allows me to use my fav texting app in its place. Thank you!
Could you explain the Sync settings a bit more. I just want to understand better. For example, why did you include those settings in the app Are there battery/data implications to using them? What is the downside to disabling all the sync settings?
Stupifier said:
New user. Tested on Voice 5.0+. Works flawless so far! This is excellent!
I have no idea why Google decided to NOT allow the Voice 5.0+ to be default SMS app.......but this module works around that issue AND allows me to use my fav texting app in its place. Thank you!
Could you explain the Sync settings a bit more. I just want to understand better. For example, why did you include those settings in the app Are there battery/data implications to using them? What is the downside to disabling all the sync settings?
Click to expand...
Click to collapse
When you send a message through XVoice++, XVoice++ doesn't put that message in the SMS database, the SMS app does. So if you send a message from another source, for example, the GV app or webapp, that message would not show up in your SMS app. Sync checks the master message list on GV's server to see if your device is missing any messages, and if it is, it sticks them into your SMS history.
It also has the benefit of catching any incoming messages that might have been missed. XVoice++ isn't perfect, and once in a while it won't catch an incoming message, sometimes because the GV app was sleeping (although I suspect this issue might be eliminated with GV 5.0+, since they switched to GCM). Enabling Sync will force XVoice++ to manually check if there are any new messages.
I personally have always had all the Sync options enabled, and the interval set to 15 minutes, and I haven't seen any issues. You can try it for yourself and monitor it. I don't think there's any reason it should impact battery or data usage, since it's just a quick request to GV's server. When I look the logs, it never takes more than a few seconds.
BehindTheMath said:
When you send a message through XVoice++, XVoice++ doesn't put that message in the SMS database, the SMS app does. So if you send a message from another source, for example, the GV app or webapp, that message would not show up in your SMS app. Sync checks the master message list on GV's server to see if your device is missing any messages, and if it is, it sticks them into your SMS history.
It also has the benefit of catching any incoming messages that might have been missed. XVoice++ isn't perfect, and once in a while it won't catch an incoming message, sometimes because the GV app was sleeping (although I suspect this issue might be eliminated with GV 5.0+, since they switched to GCM). Enabling Sync will force XVoice++ to manually check if there are any new messages.
I personally have always had all the Sync options enabled, and the interval set to 15 minutes, and I haven't seen any issues. You can try it for yourself and monitor it. I don't think there's any reason it should impact battery or data usage, since it's just a quick request to GV's server. When I look the logs, it never takes more than a few seconds.
Click to expand...
Click to collapse
Thank you for this explanation. So now I'd like to test how well these sync features work. if I understand correctly, I could test this by simply sending a text using GV app directly.....Then open my SMS app and check to see if my SMS app actually shows this newly sent message. The Sync features directly affect how and when SMS app grabs new Incoming/Outgoing GV messages. Am I understanding correctly?
Stupifier said:
Thank you for this explanation. So now I'd like to test how well these sync features work. if I understand correctly, I could test this by simply sending a text using GV app directly.....Then open my SMS app and check to see if my SMS app actually shows this newly sent message. The Sync features directly affect how and when SMS app grabs new Incoming/Outgoing GV messages. Am I understanding correctly?
Click to expand...
Click to collapse
Correct, besides for when you sent an outgoing SMS from the device itself, since then the SMS app stores it right away.
I'm so happy to see this working! Great job :victory:
one bug I've noticed, it seems to choke on accented characters. try sending " õœôöø ", for me it force closes both Voice and my SMS app