You realize that we (Android users) have had four major OS releases in less than a year, correct? 1.0, 1.1, 1.5, and 1.6. Eclair will almost definitely be out by year-end (it's tied to a product release).
How is this painfully slow?
However for those who have called on the FTC to help eliminate the other phone scourge - political robocalls - the new rules will not help. Calls from political campaigns are considered protected speech the FTC said. Ultimately consumers may get some help from state legislatures as many are regulating or looking to pass laws for more control over automated or robocall computer-generated phone-calling campaigns. One group, the National Political Do Not Contact Registry is campaigning to outlaw political robocalling altogether.
One of the huge benefits of 3G is that you can have a data connection while on a voice call. This isn't possible with EDGE. This also means that it's possible for a data connection to prevent a voice call from being received, if it does not yield the radio for an extended period of time.
Since you mentioned it, I'm not sure what this development means for the future of my GV application. You can read more about my thoughts on the matter in my blog post
For those slashdotters who are GV users--what are your thoughts on the matter? Is the official app sufficiently crippled that I should continue? Should I aim for a peaceful coexistence?
I personally use the X.Y.Z and increment each under the following conditions:
X++: New backwards-incompatible feature. For example, a new database schema would increment X.
Y++: New feature or feature set. For example: Adding a new widget.
Z++: Fixing bugs.
It works pretty well for me.
Why not just use a single version number that gets incremented by one every time there is a code change?
That's what your version control revision is for. Some of us would like to be able to tell at a glance whether having 2.3.4 might cause problems when transferring data to a 3.4.5 installation. You try doing that with between version 36978 and 87498.
Disclaimer: I wrote the GV Android app in question.
I didn't find the GV android app to be all that usable. The extra overhead ended up making me miss a lot of calls that I wouldn't otherwise have. Another problem was that dialing out either involved using the GV application which dials your Google Voice number and places the call via their system or making calls from your real number. The former put a 10 - 15 second overhead on making a call and the latter tends to confuse people because they are receiving a call from a different number than the one they (were told to) call.
If you haven't tried the latest version, I recommend you do so; it makes the dialing process much more seamless. If you still have problems with, don't hesitate to shoot me an email: gv {at} evancharlton {dot} com (that goes for anyone else that has questions or suggestions).
I would assume it would be the US due to the Aleutian islands that extend over the international date line (well, not really over it, since they bend the line around the islands. Doesn't get much later than that.
Slashdot Mirror
You realize that we (Android users) have had four major OS releases in less than a year, correct? 1.0, 1.1, 1.5, and 1.6. Eclair will almost definitely be out by year-end (it's tied to a product release). How is this painfully slow?
However for those who have called on the FTC to help eliminate the other phone scourge - political robocalls - the new rules will not help. Calls from political campaigns are considered protected speech the FTC said. Ultimately consumers may get some help from state legislatures as many are regulating or looking to pass laws for more control over automated or robocall computer-generated phone-calling campaigns. One group, the National Political Do Not Contact Registry is campaigning to outlaw political robocalling altogether.
One of the huge benefits of 3G is that you can have a data connection while on a voice call. This isn't possible with EDGE. This also means that it's possible for a data connection to prevent a voice call from being received, if it does not yield the radio for an extended period of time.
Since you felt the need to ask, no, it wasn't. You can choose believe that or not--it makes no difference to me.
Since you mentioned it, I'm not sure what this development means for the future of my GV application. You can read more about my thoughts on the matter in my blog post
For those slashdotters who are GV users--what are your thoughts on the matter? Is the official app sufficiently crippled that I should continue? Should I aim for a peaceful coexistence?
I personally use the X.Y.Z and increment each under the following conditions:
X++: New backwards-incompatible feature. For example, a new database schema would increment X.
Y++: New feature or feature set. For example: Adding a new widget.
Z++: Fixing bugs.
It works pretty well for me.
Why not just use a single version number that gets incremented by one every time there is a code change?
That's what your version control revision is for. Some of us would like to be able to tell at a glance whether having 2.3.4 might cause problems when transferring data to a 3.4.5 installation. You try doing that with between version 36978 and 87498.
No worries, I've gotten much worse ;-). And the app likely deserves it; it's a complete hack due to the lack of a public API.
Just a heads up: the current Android client (found here: http://www.cyrket.com/package/com.evancharlton.googlevoice) is *not* official in any way, shape or form.
I didn't find the GV android app to be all that usable. The extra overhead ended up making me miss a lot of calls that I wouldn't otherwise have. Another problem was that dialing out either involved using the GV application which dials your Google Voice number and places the call via their system or making calls from your real number. The former put a 10 - 15 second overhead on making a call and the latter tends to confuse people because they are receiving a call from a different number than the one they (were told to) call.
If you haven't tried the latest version, I recommend you do so; it makes the dialing process much more seamless. If you still have problems with, don't hesitate to shoot me an email: gv {at} evancharlton {dot} com (that goes for anyone else that has questions or suggestions).
Please see this search: http://www.google.com/search?q=200+billion+broadband+scandal
No, Sprint operates a CDMA network; all current Android phones only operate on GSM networks.
[Citation Needed]
I can sum up the reason that this will never happen in two words:
... fair and simple...
evan@evan-desktop:~$ echo "fair and simple" | wc -w
3
I would assume it would be the US due to the Aleutian islands that extend over the international date line (well, not really over it, since they bend the line around the islands. Doesn't get much later than that.
If you want to create a programming language, grow a beard.
Fixed that for you.