Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 12 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 8 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 17 hrs ago - more...
|
2010-12-04
, 10:21
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#152
|
New build. Also: Telepathy connection manager.
Very very very alpha stage. Please help: test!
Very very very alpha stage. Please help: test!
__________________
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.
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.
 |
|
2010-12-04
, 14:18
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#153
|
Originally Posted by uvatbc
Is your CM calls only or also texts?
New build. Also: Telepathy connection manager.
Very very very alpha stage. Please help: test!
At what phase of the call do you send the request? Do you close the call immediately or wait for the request to finish?
How do you handle checking for new texts if you support them?
How do you plan to handle voicemails?
EDIT: Also how are you planning to handle contacts?
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
Last edited by epage; 2010-12-04 at 14:49.
|
|
2010-12-04
, 18:23
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#154
|
Originally Posted by epage
At the moment, calls only because the code I copied from did only calls. But I've started fixing it so that it can do texts too.
Is your CM calls only or also texts?
Originally Posted by epage
I have used the VICar sources. vicar uses a caller daemon separate from vicar-telepathy (the CM). My CM follows the same model: qgv-tp is the CM. When it gets a streamed media request, it calls qgvdial to make a phone call.
At what phase of the call do you send the request? Do you close the call immediately or wait for the request to finish?
Originally Posted by epage
Not handled. I don't like the idea of polling for texts, nor do I have a defined interface for asking qgvdial for new texts. So the answer right now is also: "Not designed yet". I will look at the google voice plugin for chrome to see what it does to get notifications because it seems to get them almost instantaneously, but thats still some time in the future.
How do you handle checking for new texts if you support them?
Originally Posted by epage
Not desgined yet. Probably tell qgvdial to play it.
How do you plan to handle voicemails?
Originally Posted by epage
The plan is to NEVER pull in Google contacts. There might be a separate contacts app that will sync Google contacts with the n900 contacts. Since I intend to work like vicar, there should be a "Call with qgvdial" button on all n900 contacts.
EDIT: Also how are you planning to handle contacts?
qgv-tp is a CM shim to qgvdial, just in the way vicar-telepathy is the CM shim to the vicar daemon.
qgvdial can run without the CM; the CM cannot do without qgvdial. qgv-tp is therefore an "addon" to qgvdial. I intend to keep it that way unless there is a compelling reason to do otherwise - primarily because qgvdial is cross platform, but qgv-tp is not.
__________________
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.
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.
|
|
2010-12-04
, 19:43
|
|
Posts: 356 |
Thanked: 123 times |
Joined on Dec 2008
|
#155
|
My device appears to be randomly trying to dialout to a null number. It did this right after I installed the program, and kept doing it every few minutes.
It pops up the outgoing call program, and then displays a call to no one, which fails.
edit: and if I try to close qgvdial (cntrl-q) it forces it keeps re-opening itself every few minutes to relogin.
Here's the end of my log file:
Last edited by xur17; 2010-12-04 at 19:47.
It pops up the outgoing call program, and then displays a call to no one, which fails.
edit: and if I try to close qgvdial (cntrl-q) it forces it keeps re-opening itself every few minutes to relogin.
Here's the end of my log file:
Code:
2010-12-04 14:36:05.694 : 3 : Self Contact is null 2010-12-04 14:36:05.695 : 3 : "Yet to figure out how to get phone number from ring" 2010-12-04 14:36:05.696 : 3 : " key = "account", value = "ring"" 2010-12-04 14:36:05.697 : 3 : Self Contact is null 2010-12-04 14:36:07.641 : 3 : "User is not logged in yet. Cannot make any calls." 2010-12-04 14:36:07.747 : 3 : "User is not logged in yet. Cannot make any calls." 2010-12-04 14:36:09.367 : 3 : Login page loaded 2010-12-04 14:36:25.086 : 3 : "User logged in" 2010-12-04 14:36:25.687 : 3 : "Re-selecting inbox entries. This will take some time" 2010-12-04 14:36:25.828 : 3 : "Inbox entries selected." 2010-12-04 14:36:28.359 : 3 : "Completed work 2: login" 2010-12-04 14:36:28.359 : 3 : No work to be done. Sleep now. 2010-12-04 14:36:29.223 : 3 : Login success 2010-12-04 14:37:37.588 : 3 : "Enqueued 7: dialOut." 2010-12-04 14:37:37.589 : 3 : "Starting work 7: dialOut" 2010-12-04 14:37:38.004 : 3 : "Another call is in progress. Please try again later" 2010-12-04 14:37:38.289 : 2 : "access number = """ 2010-12-04 14:37:38.381 : 3 : "Callout in progress" 2010-12-04 14:37:38.402 : 3 : "Dial successful to subscribe." 2010-12-04 14:37:38.406 : 3 : "Completed work 7: dialOut" 2010-12-04 14:37:38.408 : 3 : No work to be done. Sleep now. 2010-12-04 14:37:39.834 : 2 : Channel could not become ready 2010-12-04 14:39:07.584 : 3 : "Enqueued 7: dialOut." 2010-12-04 14:39:07.585 : 3 : "Starting work 7: dialOut" 2010-12-04 14:39:07.933 : 3 : "Another call is in progress. Please try again later" 2010-12-04 14:39:08.169 : 2 : "access number = """ 2010-12-04 14:39:08.197 : 3 : "Callout in progress" 2010-12-04 14:39:08.317 : 3 : "Dial successful to subscribe." 2010-12-04 14:39:08.320 : 3 : "Completed work 7: dialOut" 2010-12-04 14:39:08.321 : 3 : No work to be done. Sleep now. 2010-12-04 14:39:08.438 : 2 : Channel could not become ready 2010-12-04 14:39:15.599 : 3 : Contacts widget was NULL. 2010-12-04 14:39:15.600 : 2 : Inbox widget was NULL.
Last edited by xur17; 2010-12-04 at 19:47.
|
|
2010-12-04
, 20:13
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#156
|
Originally Posted by xur17
I have also been facing this issue. I think I know what may be causing it, so a fix should come out by the end of today.
My device appears to be randomly trying to dialout to a null number. It did this right after I installed the program, and kept doing it every few minutes.
It pops up the outgoing call program, and then displays a call to no one, which fails.
Until then please do the following:
Code:
/opt/qgvdial/bin/qgv-util REMOVE
Originally Posted by xur17
qgvdial is now a "service". When the telepathy CM wants to use the qgvdial service, it requests the system to start the service if it is not already started.
edit: and if I try to close qgvdial (cntrl-q) it forces it keeps re-opening itself every few minutes to relogin.
Since every call goes through qgvdial, every time a call if made, qgvdial is started if it is not already running.
In other words, this is a feature.
Shutting off qgv-tp (telepathy CM) using the code above should prevent spurious usage of the feature.
__________________
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.
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.
|
|
2010-12-04
, 20:31
|
|
Posts: 356 |
Thanked: 123 times |
Joined on Dec 2008
|
#157
|
I'm not sure which thread is the best to post this in, but I was reading this thread, so I guess here works:
I was playing around with the Google Voice extension for google chrome (by google), and trying to figure out what they do to get new messages, since (like uvatbc mentioned) new messages appear to arrive fairly quickly (hoping to find some way to accomplish push messages).
This page shows what requests are being made by chrome, and is very helpful on deciphering the protocol that the google voice extension uses.
Two useful things I noticed:
Requests are made to: https://www.google.com/voice/b/0/request/messages/ to get a list of the text messages in an account. Each message has a unique ID, and each conversation has a separate unique id.
https://www.google.com/voice/b/0/request/unread/?b=0 returns the number of unread messages in all of the different folders.
I'm not sure how it logs in, etc, but hopefully this makes it easier to check for new text messages, since the current method is to scrape the mobile website, which presents some difficulties. This was the result of a few minutes of playing with the extension, so I am sure there is plenty more to learn about it.
I was playing around with the Google Voice extension for google chrome (by google), and trying to figure out what they do to get new messages, since (like uvatbc mentioned) new messages appear to arrive fairly quickly (hoping to find some way to accomplish push messages).
This page shows what requests are being made by chrome, and is very helpful on deciphering the protocol that the google voice extension uses.
Two useful things I noticed:
Requests are made to: https://www.google.com/voice/b/0/request/messages/ to get a list of the text messages in an account. Each message has a unique ID, and each conversation has a separate unique id.
https://www.google.com/voice/b/0/request/unread/?b=0 returns the number of unread messages in all of the different folders.
I'm not sure how it logs in, etc, but hopefully this makes it easier to check for new text messages, since the current method is to scrape the mobile website, which presents some difficulties. This was the result of a few minutes of playing with the extension, so I am sure there is plenty more to learn about it.
|
|
2010-12-05
, 00:06
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#158
|
Originally Posted by uvatbc
Lately I've been leaning towards contact providers rather than sync, a lot less complicated logic and guessing. libfolks is possibly the direction things will move in but its still a very early project. I've got plans for a couple contact sources I'd love to write.
The plan is to NEVER pull in Google contacts. There might be a separate contacts app that will sync Google contacts with the n900 contacts. Since I intend to work like vicar, there should be a "Call with qgvdial" button on all n900 contacts.
Originally Posted by uvatbc
Seems like it has the potential for an odd user experience but oh well. Though I'm always disappointed in competition rather than help I wish you good luck and hope it turns out well. By this I mean that I'm already spread thin and would appreciate assistance plus it brings up tough questions like "what is the future role of my app? should I just encourage my users to transition or should I keep maintaining".
qgv-tp is a CM shim to qgvdial, just in the way vicar-telepathy is the CM shim to the vicar daemon.
qgvdial can run without the CM; the CM cannot do without qgvdial. qgv-tp is therefore an "addon" to qgvdial. I intend to keep it that way unless there is a compelling reason to do otherwise - primarily because qgvdial is cross platform, but qgv-tp is not.
The external daemon approach could have some benefits though (like already being logged in).
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
|
|
2010-12-05
, 18:27
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#159
|
New build: Connection manager fixed!
-> No more spurious calls from the CM.
-> "Call with qgvdial" and "Text with qgvdial" button on contacts.
-> Calls and texts work!
Please note: Upgrading *may* require a reboot. I don't know why this happens every once in a while.
2. Unfortunately the extension seems to be pulling unread messages every few seconds - thats what I infer from the events page. This means polling (boooo) and I'm not yet willing to give up on a REST type api.
3. The "current" method of scraping the website is no longer current. I pull messages from https://www.google.com/voice//inbox/recent/ and it comes as XML-JSON. Easy to parse and not dependent on the whims and fancies of the web page format.
Some of these users prefer to sync to Google (like me) others like Google but don't want to store all their information with them.
I'm aiming for a CM that works with all these cases.
How much time and effort will it take me to learn Python well enough to hack at TOR and DC, versus do what I know well - C++ and QT - and make use of the information that people like xur17 keep finding?
What is the possibility of me ever getting to use Python professionally when even C++ and QT is a far cry from what I'm really doing?
I'm doing this for fun and I don't want it to be too much hard work (although it has become that), so it comes down to what method has the least effort to enjoyment ratio.
I have ulterior motives as well: I like QT a lot and I wanted to promote it to my team as "the one way" to do almost any userland app on multiple platforms. When the inevitable "show me examples of what it can do" came up, it was so easy to show my own app.
qgvdial uses networking, dbus, gui, sql, webkit, xml, scripting, json and qml. It is the perfect QT showcase!
-> No more spurious calls from the CM.
-> "Call with qgvdial" and "Text with qgvdial" button on contacts.
-> Calls and texts work!
Please note: Upgrading *may* require a reboot. I don't know why this happens every once in a while.
Originally Posted by xur17
1. Thanks for the chrome link - for everyone else, that is not a clickable link. Copy URL and post into address bar of your chrome window.
This page shows what requests are being made by chrome, and is very helpful on deciphering the protocol that the google voice extension uses.
Two useful things I noticed:
Requests are made to: https://www.google.com/voice/b/0/request/messages/ to get a list of the text messages in an account. Each message has a unique ID, and each conversation has a separate unique id.
https://www.google.com/voice/b/0/request/unread/?b=0 returns the number of unread messages in all of the different folders.
I'm not sure how it logs in, etc, but hopefully this makes it easier to check for new text messages, since the current method is to scrape the mobile website, which presents some difficulties. This was the result of a few minutes of playing with the extension, so I am sure there is plenty more to learn about it.
2. Unfortunately the extension seems to be pulling unread messages every few seconds - thats what I infer from the events page. This means polling (boooo) and I'm not yet willing to give up on a REST type api.
3. The "current" method of scraping the website is no longer current. I pull messages from https://www.google.com/voice//inbox/recent/ and it comes as XML-JSON. Easy to parse and not dependent on the whims and fancies of the web page format.
Originally Posted by epage
A contact provider is the obvious direction, but there are some users who want to store their contacts on the phone or already have contacts on the phone.
Lately I've been leaning towards contact providers rather than sync, a lot less complicated logic and guessing. libfolks is possibly the direction things will move in but its still a very early project. I've got plans for a couple contact sources I'd love to write.
Some of these users prefer to sync to Google (like me) others like Google but don't want to store all their information with them.
I'm aiming for a CM that works with all these cases.
Originally Posted by epage
Your disappointment is understandable, but that was not my intention.
Seems like it has the potential for an odd user experience but oh well. Though I'm always disappointed in competition rather than help I wish you good luck and hope it turns out well. By this I mean that I'm already spread thin and would appreciate assistance plus it brings up tough questions like "what is the future role of my app? should I just encourage my users to transition or should I keep maintaining".
How much time and effort will it take me to learn Python well enough to hack at TOR and DC, versus do what I know well - C++ and QT - and make use of the information that people like xur17 keep finding?
What is the possibility of me ever getting to use Python professionally when even C++ and QT is a far cry from what I'm really doing?
I'm doing this for fun and I don't want it to be too much hard work (although it has become that), so it comes down to what method has the least effort to enjoyment ratio.
I have ulterior motives as well: I like QT a lot and I wanted to promote it to my team as "the one way" to do almost any userland app on multiple platforms. When the inevitable "show me examples of what it can do" came up, it was so easy to show my own app.
qgvdial uses networking, dbus, gui, sql, webkit, xml, scripting, json and qml. It is the perfect QT showcase!
Originally Posted by epage
Yes. Also: separated testing and upgrades.
The external daemon approach could have some benefits though (like already being logged in).
__________________
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.
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.
|
|
2010-12-05
, 18:38
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#160
|
Known isssues:
SMS from the contacts button is borked for the moment - I haven't as yet figured out the sequence of steps th CM takes when it sends text messages.
Also for reasons unknown, the Call and Chat buttons are on different lines in the contacts view.
SMS from the contacts button is borked for the moment - I haven't as yet figured out the sequence of steps th CM takes when it sends text messages.
Also for reasons unknown, the Call and Chat buttons are on different lines in the contacts view.
__________________
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.
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.
Proxy support!! This build primarily is to make qgvdial work even when there is a restrictive proxy - meaning http/https works only if it goes through a proxy.
This build works perfectly well on Ubuntu and since it is written to work equally well on standard Linux platforms, should work for maemo as well.
For those who are interested, I look up the environment variables "http_proxy" and "https_proxy" to get the proxy settings.
Assuming that these vars are the same on Maemo, I think it should work.
I have tested it on ubuntu behind a proxy, but not on Maemo behind a proxy. I need testers!
Thanks!
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.