Hello,
The Google Voice users in XDA may know that with the last major change in the Google Voice apk, the team decided to institute a direct-dial facility to make outgoing calls through Google Voice.
History: Prior to this version, all call were routed through standard numbers (202-556-0000) for the Northeast region. The way it worked (for outgoing calls) was that GV would use the internet to inform their engine in the back-end to give a call-back from a fixed phone number. Thus if I added 202-556-0000 number to my (Fav-5) number, then all my outgoing calls would be free.
New Version update: Some say that google decided to sleep with the telcos and started to assign unique numbers to each telephone number in the contact list (at the back-end) so that the GV app can now initiate a call to 'directly' using the unique number without going through the internet call-back process.
Irrespective of principle, Google decided to inconvenience millions of people without an option to disable the direct dial 'feature' which has pissed many people and resulted in very long ranting threads on their help forum. And like all Google products - official support is almost zero.
Solution: To go back to the older technique of dialing - users have uninstalled the latest GV app from the ROM (e.g. using Titanium Backup) and installed the previous version of the apk file.
Current state and request: Google Voice application has seen another major update today where they have introduced the anticipated widgets but still no option to change the direct-dial feature.
Unfortunately, I am not a programmer but I was wondering if there was a way to extract the widget functionality from the new apk and use it in conjunction with the older GV version (without widgets and direct dial) or something to that objective?
Thanks for your help!
I need the Google Voice apk that dialed out to 202-556-0000
I need the Google Voice apk that dialed out to 202-556-0000.
Can't sustain on a 400 mins MyFaves plan without that.
This thread does NOT belong in development. I am moving it to Q&A.
Please read the forum stickies and rules next time.
willverduzco said:
This thread does NOT belong in development. I am moving it to Q&A.
Please read the forum stickies and rules next time.
Click to expand...
Click to collapse
Just in time too!
(OP is Sept '10)
I also need the GV app without direct access number...
any updates on that?
-greenboy- said:
I also need the GV app without direct access number...
any updates on that?
Click to expand...
Click to collapse
Someone posted a DropBox link to 0.3.4 in a similar thread on droidforums.net.
droidforums.net/forum/droid-applications/62483-google-voice-0-4-0-12-no-more-fnf.html#post660251 (I can't post external links yet.)
Sorry to resurrect an old thread, but I arrived here via Google and figured there are probably others looking for it also.
I have found several bugs in Kies but can't find any contact information as to where to send my reports. Anyone who knows?
Latest bug found:
When syncing Outlook contacts to the phone, the First Name and Surname swap places, so all contacts on the phone end up backwards. Google show that I'm not alone with this problem.
This issue is new to me. I know for a fact that I got a correct sync the first time I used it (approx 2 months ago), 'cause I remember that I've scrolled down to the letter 'E' to find "Emma Foobar" (where Emma is a first name).
I have upgraded the phone from Eclair 2.1-update1 to the latest Froyo 2.2, and Kies has been updated two or three times during this period. So either one, or a combination of both, must have introduced this bug.
It's Samsung, so /dev/null seems appropriate...
Valeo said:
It's Samsung, so /dev/null seems appropriate...
Click to expand...
Click to collapse
I sent a comment to the Swedish Samsung organization (via a web form).
I have no Idea if that did it, but yesterday, a new version of Kies was released and now contacts are synchronized correctly.
Only a minor bug is left:
The alphabet list to the right is still based on Sirnames even though the settings state that the display should order using First name. So even though I have contacts like "Emma Smith", I have a dash instead of an 'E' in the list.
Search in market for "voxtrot"
This App allows Android users can connect easily
Which makes it extra simple to use - no need to create a new user name, just use your phone number as your ID. No need to add your friends again, just use your phonebook.
To call just dial the number as usual. This App connect the call for free.
Note: Application force closes on gingerbread so i cant check it fully please try it and give a Reply
I am Sorry if anything wrong.
Thanks for your message, I'm actually one of the guys behind Voxtrot. You may have forgotten to say that we do provide free calling, but only if both persons are registered on the network.
Voxtrot was successfully tested on the Nexus S sporting Gingerbread, but never on a customized HD2, hence possibly the force quit issue.
Anyway I'm happily gathering feedback so if you have some, don't hesitate.
@romzzz
Thanks for your valuable Information and i also in same issue "Force Close"
anyway i hope someone will find a solution.
How it works? In europe too?
Hello all
I'm forwarding calls to my galaxy (using MIUI MintBerry).
I would like to know when the call is directly to my cellphone (The number in my SIM) and when the call is forwarded to me.
There is one application the supposed to do it (but it's doesn't work ):
https://play.google.com/store/apps/...SwxLDEsImRlLmR1ZW5uZG5zLmZvcndhcmRlZGNhbGwiXQ
BTW-
Maybe someone with CM can report if it works?
Link to free version :
https://play.google.com/store/apps/...sImRlLmR1ZW5uZG5zLmZvcndhcmRlZGNhbGwuZnJlZSJd
Thanks.
Syrex-OL said:
Hello all
I'm forwarding calls to my galaxy (using MIUI MintBerry).
I would like to know when the call is directly to my cellphone (The number in my SIM) and when the call is forwarded to me.
Click to expand...
Click to collapse
I try to get as many devices supported as possible. However, some ROMs provide major trouble in doing so (e.g. by breaking logcat or disabling some features). So far I have no reports for the Galaxy phone, only for Galaxy S II, where the alert works well with the Samsung ROM.
If you test out the free version, and use the "Request device support" feature right after getting a forwarded call, I can have a look if your phone/ROM combination can be supported. Also, the detection mechanism is the same for free and paid, so you can use the free version to see if the paid one would work for you.
Regarding ROMs, I have had the best experience with CM so far...
Ge0rG
Done.
Waiting for a new version
(If you need any other info don't hesitate to ask )
Hello everybody,
just started a temporary sale for NFC ReTag PRO...
Use any NFC tag (write protected and re-writable) to trigger multiple functions on your device!
You can use this app to associate multiple functions (e.g. toggle Wlan, Bluetooth, Mobile Data, Airplane mode, start navigation,run Tasker task, launch any installed app, use media buttons, call a phone number, add a timestamp, calendar entry and many more) to a specific NFC Tag via an app internal database.
Get it NOW and save some money
Link to the Support thread:
forum.xda-developers.com/showthread.php?t=1477138http://
Free version also available !
Nice and first! Downloading now...
Text to speech bug
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
GenePaton said:
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
Click to expand...
Click to collapse
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
ascsa said:
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
Click to expand...
Click to collapse
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
GenePaton said:
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
Click to expand...
Click to collapse
No Problem ... ... but let´s move to the official support thread (http://forum.xda-developers.com/showthread.php?t=1477138&page=100) ...because this is an old thread ...NFC Retag PRO is currently NOT on sale ... and we shouldn´t confuse the users ...
Just to clarify for any other readers, my e-mail answer to your last post :
The Galaxy S3 GT-I9300 (international model) is one of our main testing devices. Not sure if, there is a problem with the Vodafone Rom or the Australian T model, but it´s working fine here on 4.1.2.
Had a short look at our code and the official api and everything seems fine ... but without a log file or better a device on which we could reproduce the error it´s nearly impossible to be sure ...However, you mentioned it happens with other apps, too , so I would bet on some Vodafone "enhancements" ...
Btw. have you tried the Samsung TTS engine (settings--> language& input -->text-to-speech output--> preferred engine) instead of the Google engine?
I notice there are several versions of tasker. Which do I need?
Muscipula
Sent from my SM-G903F using Tapatalk