Besides some bug fixes, generalizing of CSV contacts (supports Google Contacts export and GrandCentral export), hopefully startup time improvements, and present but disabled GoogleVoice support (there is a hack for to enable it), this has a lot more debugging output.
Installed dialcentral 0.9.1 from your link, still no go on BT tethering. Error msg is:
/media/mmc1 $ python2.5 /usr/bin/dialcentral.py
/usr/lib/dialcentral/dc_glade.py:74: GtkWarning: gtk_widget_grab_default: assertion `GTK_WIDGET_CAN_DEFAULT (widget)' failed
self._widgetTree = gtk.glade.XML(path)
python2.5[6506]: GLIB DEBUG ConIc - con_ic_connection_send_event(0x195aa8, 75388a19-8943-4b2b-bb41-78c03f7ef734, DUN_GSM_PS, 0)
/usr/lib/dialcentral/dc_glade.py:250: UserWarning: Attempted to login before initialization is complete, did an event fire early?
"Attempted to login before initialization is complete, did an event fire early?"
/usr/lib/dialcentral/gc_backend.py:89: UserWarning: Performing download of http://www.grandcentral.com/mobile/s...warding_select
forwardSelectionPage = self._browser.download(self._forwardselectURL)
/usr/lib/dialcentral/dc_glade.py:270: UserWarning: Traceback (most recent call last):
File "/usr/lib/dialcentral/dc_glade.py", line 256, in attempt_login
if self._phoneBackend.is_authed():
File "/usr/lib/dialcentral/gc_backend.py", line 98, in is_authed
self._grab_token(forwardSelectionPage)
File "/usr/lib/dialcentral/gc_backend.py", line 323, in _grab_token
raise RuntimeError("Could not extract account number from GrandCentral")
RuntimeError: Could not extract account number from GrandCentral
That error you are getting is very perplexing to me. It was able to find some but not all of the information on the webpage it was looking for. It found the login token but not what your account number is. I'm tempted to just allow it to be ignored but concerned about what else might behave in strange ways.
Oh, I have a guess as to whats going on. Does your data plan include any "phone optimizing" of webpages? DialCentral is very dumb. Until there is an API, it just downloads the GrandCentral/GoogleVoice webpages and searches them for relevant information. If your cell service that you are using when you are tethered modifies webpages, it might change the GrandCentral mobile pages just enough that we cannot find all of the relevant information. If you are able to download the following link through wifi and through tethering and PM me with it, hopefully that'll give me the clue I need to make it flexible enough to still work with your data plan. http://www.grandcentral.com/mobile/s...warding_select
As for arbitrary forwarding numbers, you should be allowed to. The forward selection combo box is editable and I just read the code and its theoretically possible though I don't have extra phones to try it with. If there are issues let me know.
Also, thanks for all of your efforts in working with me on resolving these issues.
That error you are getting is very perplexing to me. It was able to find some but not all of the information on the webpage it was looking for. It found the login token but not what your account number is. I'm tempted to just allow it to be ignored but concerned about what else might behave in strange ways.
Oh, I have a guess as to whats going on. Does your data plan include any "phone optimizing" of webpages? DialCentral is very dumb. Until there is an API, it just downloads the GrandCentral/GoogleVoice webpages and searches them for relevant information. If your cell service that you are using when you are tethered modifies webpages, it might change the GrandCentral mobile pages just enough that we cannot find all of the relevant information. If you are able to download the following link through wifi and through tethering and PM me with it, hopefully that'll give me the clue I need to make it flexible enough to still work with your data plan. http://www.grandcentral.com/mobile/s...warding_select
As for arbitrary forwarding numbers, you should be allowed to. The forward selection combo box is editable and I just read the code and its theoretically possible though I don't have extra phones to try it with. If there are issues let me know.
Also, thanks for all of your efforts in working with me on resolving these issues.
Clicked the above link with wifi and BT tethering, the web page showed up exactly the same on n810 web browser. Guess T-mobile is not the problem.
When I use wifi, after I launch dialcentrial, the "dial" bottom turns gray from green and then turns gree again.
When I use BT tethering, the "dial" button is grayed out and it says "Login failed". Re-entering the correct username/passwd still gave me "Login failed".
I just gotta say thank you, this is why I love the OSS community, a quick update got DialCentral working with Google Voice, flawlessly. For the iPhone crowd, having to wait for "GV Mobile" is hilarious to me.
P.S. Would love to see an SMS add in, but not that important... after receiving a reply to sms messages from a contact, a google voice telephone number for each contact is given (ie: 1-406-***-****), which also simplifies calling using 'GV'. It's almost as if Google is killing DialCentral.
I am prepping the release of 0.9.2 which better integrates GoogleVoice while maintaining GrandCentral support.
So this might sound a bit pedantic being as how this is a very simple app. I've been thinking about it and am concerned over what features to add. I've always been someone in favor of the Unix philosophy and to me dialing has always been the main purpose. I've heard comments for SMS, voicemail playback, and am concerned over the loss of simplicity in the UI.
Also keep in mind, this is coming from a guy who can probably count on two hands in unary the number of texts he has sent/received. Also, I mainly use the mail client for voicemails especially with the new transcription feature.
As for GoogleVoice being a DialCentral killer, I kind of agree. The big thing that keeps me using DialCentral (besides as part of maintaining it so it doesn't die) is I have a large set of contacts for my Church that instead of trying to make one-way-sync somehow with google contacts I just download the latest CSV every once in a while and have DialCentral use that directly.
I just promoted 0.9.2, updated first post on this thread.
Works great, though contacts display a little odd (all of them preceeded with 'GV').
I agree that SMS doesn't appropriately belong in this app. It should be combined with the chat client, or the email client, or something else entirely.
