Active Topics

 



Notices


Reply
Thread Tools
Posts: 61 | Thanked: 27 times | Joined on Jul 2010
#241
Originally Posted by uvatbc View Post
Sounds like the Starbucks free wifi effect.
I'll try this out.
Just to be sure I understand: when you say the failure is just like the previous time, does this it mean it says "Another call is in progress, please try again later" ?
Or does it just fail with an error in about 45 seconds?
I'm not sure if I waited 45 secs before I tried canceling that call.

But on the next call attempt, it showed "Another call is in progress, please try again later".

I can try again in the morning, if you need more detail.
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#242
Originally Posted by kbyork View Post
I'm not sure if I waited 45 secs before I tried canceling that call.

But on the next call attempt, it showed "Another call is in progress, please try again later".

I can try again in the morning, if you need more detail.
qgvdial has a network timeout of 45 seconds.
If you abort the call, qgvdial has to send another network request to Google voice to cancel the call.

Here's my theory of what happens: In the scenario you describe, the first call is pending, then you cancel it, which causes qgvdial to send more network data (which isn't going anywhere because of the terms and conditions page).
Because of this, the next call says "Another call is in progress".

You'll have to wait for 45 seconds per request for that timeout to expire.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#243
New build: "Yes, I'm crazy about performance."

This one is specifically to enhance the performance of retrieving and updating Contacts and Inbox entries.
Before this update, if you were a new user, retrieving and caching contacts and Inbox could take up to 5 minutes. Now it should happen within 10 seconds ... assuming your internet connection is fast enough.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 61 | Thanked: 27 times | Joined on Jul 2010
#244
Originally Posted by uvatbc View Post
qgvdial has a network timeout of 45 seconds.
If you abort the call, qgvdial has to send another network request to Google voice to cancel the call.

Here's my theory of what happens: In the scenario you describe, the first call is pending, then you cancel it, which causes qgvdial to send more network data (which isn't going anywhere because of the terms and conditions page).
Because of this, the next call says "Another call is in progress".

You'll have to wait for 45 seconds per request for that timeout to expire.
ok,... I tried it again.
I did not get a time-out.
I waited 3.5 mins., and it was still trying to dial.
 

The Following User Says Thank You to kbyork For This Useful Post:
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#245
Thanks. I'll try getting into a starbucks asap to debug this.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 356 | Thanked: 123 times | Joined on Dec 2008
#246
I just reflashed my n900, and restored everything from a backup (including applications).

qgvdial didn't get installed (I installed the dev version, so that is probably why), but after I installed it there are now two copies of qgvtp in my accounts (one of which has a network issue).

How do I go about removing the second one?

edit: I ended up doing: "apt-get remove --purge qgvdial", and then reinstalled it. This took care of the extra qgvtp.

Last edited by xur17; 2011-02-01 at 03:25.
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#247
Originally Posted by xur17 View Post
edit: I ended up doing: "apt-get remove --purge qgvdial", and then reinstalled it. This took care of the extra qgvtp.
Good to know.

By the way, for everyone using qgvdial: If you'd like to see qgvdial in extras, you need to vote for it.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Posts: 356 | Thanked: 123 times | Joined on Dec 2008
#248
Originally Posted by uvatbc View Post
Good to know.

By the way, for everyone using qgvdial: If you'd like to see qgvdial in extras, you need to vote for it.
Here's the link to vote for it: http://maemo.org/packages/package_in...ial/0.2.349-1/

(it took me a little while to find it).
 

The Following User Says Thank You to xur17 For This Useful Post:
Posts: 356 | Thanked: 123 times | Joined on Dec 2008
#249
I was looking at your dbus support for qgvdial:
http://code.google.com/p/qgvdial/wik...d=DBusCommands

I have 2 quick suggestions / requests:
1. The last dbus command "To text a number without any text (open a text input dialog)" should be the action that occurs when I select "Text via QGV" for a user. Right now it opens a new chat room that doesn't work (displays an error).
2. How difficult would it be to include a dbus action to switch forwarding phones? I wrote a queenbeecon widget that switches my forwarding phones based on my wifi network, but it requires a web server, which makes it difficult for other people to use. My recommendation would be to have a dbus action that allows you to enable and disable arbitrary phones, and maybe some way to verify that the phones were actually switched.
 
Posts: 1,048 | Thanked: 979 times | Joined on Mar 2008 @ SF Bay Area
#250
Originally Posted by xur17 View Post
I was looking at your dbus support for qgvdial:
http://code.google.com/p/qgvdial/wik...d=DBusCommands

I have 2 quick suggestions / requests:
1. The last dbus command "To text a number without any text (open a text input dialog)" should be the action that occurs when I select "Text via QGV" for a user. Right now it opens a new chat room that doesn't work (displays an error).
2. How difficult would it be to include a dbus action to switch forwarding phones? I wrote a queenbeecon widget that switches my forwarding phones based on my wifi network, but it requires a web server, which makes it difficult for other people to use. My recommendation would be to have a dbus action that allows you to enable and disable arbitrary phones, and maybe some way to verify that the phones were actually switched.
1. That dbus command does not open a chat room. You're confusing it with the contacts integration component that I introduced 2-3 months back. And yes, that button is broken. I'm not sure how I'm supposed to fix it yet, but I'll get to it.
The dbus API itself is working fine. I've tested it several times using my test utilities. You should be able to use it in QB.
2. That is something I've thought about for some time... It is kind of cumbersome right now to open qgvdial then click the dialpad and then click the switch button. It's not difficult to add the dbus api, it is difficult to make the api good enough that it will never need to change in the future. Also, the plumbing is difficult.

Besides, at this moment, I'm concentrating on mosquitto. I have been able to compile and run it on n810 and n900 and hopefully I'll be able to debianize and upload to extras devel soon (on both).
Once that is done, I'll be adding a mqtt subscriber in qgvdial that will wait for an "update now" message to refresh contacts, inbox or settings.
The publisher will be released for n810 and generic Linux - it will poll continuously for changes and post update messages to the server.
__________________
qgvdial: Google Voice client. All downloads
qgvtp: Phone integration for the n900 that dials out and sends texts using qgvdial.
mosquitto: message broker that implements the MQ Telemetry Transport protocol version 3.
qgvnotify: Google voice and contacts notifier for diablo and maemo.

If you want to thank me, click the Thanks button.
If you'd like to thank my applications, vote to move them to extras.
 
Reply


 
Forum Jump


All times are GMT. The time now is 17:48.