maemo.org - Talk - [Announce] qgvdial: Google Voice client for Qt platforms

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [Announce] qgvdial: Google Voice client for Qt platforms (https://talk.maemo.org/showthread.php?t=56397)

Re: [ANNOUNCE] Multi-platform Google voice dialer

Quote:

Originally Posted by uvatbc (Post 937039)

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.

1. I was referring to the contacts integration component. I was just recommending that you make it open the window to send a text message instead of the chatroom window if that is possible (until you fix the chatroom).

2. I was actually referring to switching forwarding phones in a google voice account (which phones ring when your number is called).

I was just (today) looking into how to get mosquitto run on the n900 so I could try to setup a push service to the device. Let me know when you have a package ready.

Re: [ANNOUNCE] Multi-platform Google voice dialer

Quote:

Originally Posted by xur17 (Post 937175)

1. "I would, if I knew how" :) The fact that it opens up a chatroom is an unintended side effect.
2. Oh ok. I see what you mean. That too has similar design constraints, and I will get to it.

I've managed to compile and run mosquitto on n810 and n900. I have also managed to run the pub sub across the following configs:

With mosquitto broker on Ubuntu and:
pub: Ubuntu, sub: Ubuntu: success
pub: Ubuntu, sub: n810/n900: success
pub: n810/n900, sub: Ubuntu: success
pub: n810/n900, sub n810/n900: success

With mosquitto broker on n810 and:
pub: Ubuntu, sub: Ubuntu: success
pub: Ubuntu, sub: n810/n900: success
pub: n810/n900, sub: Ubuntu: success
pub: n810/n900, sub n810/n900: success

I haven't tried the broker on n900, but I'm confident it will work, and besides, the point is to keep the broker on a server. My n810 is going to be that server until such time that I manage to make it run on DD-WRT.

What I'm blocked at right now is debianization (my arch enemy).
Building the deb in scratchbox works, but fails on the maemo.org build servers.
The error I get is:

Code:

dpkg-shlibdeps: error: couldn't find library libmosquitto.so.0 needed by debian/mosquitto/opt/maemo/usr/bin/mosquitto_pub (ELF format: 'elf32-littlearm'; RPATH: '').

Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.

To help dpkg-shlibdeps find private libraries, you might need to set LD_LIBRARY_PATH.

dh_shlibdeps: dpkg-shlibdeps -Tdebian/mosquitto.substvars debian/mosquitto/opt/maemo/usr/lib/libmosquitto.so.0 debian/mosquitto/opt/maemo/usr/lib/libmosquittopp.so.0 debian/mosquitto/opt/maemo/usr/bin/mosquitto_sub debian/mosquitto/opt/maemo/usr/bin/mosquitto debian/mosquitto/opt/maemo/usr/bin/mosquitto_pub returned exit code 2

make: *** [binary-arch] Error 9

dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

To me, this means that probably I'm not putting the shared library info into the dependencies, but I don't understand that either.
From what I understand, dependencies are on other packages, not within a package... or am I missing something here?

Re: [ANNOUNCE] Multi-platform Google voice dialer

Have you packaged mosquito yourself?
Have a look at http://maemo.crochik.com/qt-developm...-lib-for-maemo

If you don't have how to change the mosquito library and this is indeed the issue you can fix the issue by manually adding the dependencies to the buildep on your control file.

Re: [ANNOUNCE] Multi-platform Google voice dialer

Quote:

Originally Posted by fcrochik (Post 937433)

I had looked at your site for help, and it did help
From what I understand, the control file makes the debhelpers create 2 debs: One with the actual library and one with the headers for the dev package.

Is there no way to package it all into one?
Is that not the normal way to do it?
Does the unix philosophy of "do only one thing and do it well" apply even to packaging?
Do I have to stop thinking of it as a way to "install everything"?

Re: [ANNOUNCE] Multi-platform Google voice dialer

After following fcrochik's instructions and creating two packages - one for the library and the other for the binaries that depend on that library - I have the next error!

There are two libraries: libmosquitto.so.0 and libmosquittopp.so.0 (the cpp interface)
Technically libmosquittopp a library, so it should sit in the same deb as libmosquitto, right?
Beeep! Wrong! libmosquittopp.so depends on libmosquitto.so
I'm back to the same problem.

The easy way is to create yet another package for libmosquittopp, but I feel I'm overdoing it.

Re: [ANNOUNCE] Multi-platform Google voice dialer

Looks like I stand corrected.
I checked up synaptic on my Ubuntu 10.10 and found that there are separate cpp bindings for for many libraries.
I'm going to stop wasting time and just create the third package.

Re: [ANNOUNCE] Multi-platform Google voice dialer

I just figured out why my battery life has been aweful for the past few days.

QGVDial was eating up ~25% of the processor constantly for the past few days. Looking at batterygraph, it appears that it began when I tried to make an outgoing call, and it failed to go through (it took forever trying to get the number to dial, and then gave some sort of error).

I glance at my log file, but didn't see anything that looked very useful. I'm not sure what can be done about this, but just something to keep in mind.

Re: [ANNOUNCE] Multi-platform Google voice dialer

Quote:

Originally Posted by xur17 (Post 939626)

Wow... thats not good. I need to repro this somehow.

Re: [ANNOUNCE] Multi-platform Google voice dialer

Quote:

Originally Posted by uvatbc (Post 939731)

Wow... thats not good. I need to repro this somehow.

Yeah, agreed. I notice it when I looked at batterygraph, and saw a lot of cpu useage. I'll take a better look again tonight, and see if I can find anything usefull in the log file.

Re: [ANNOUNCE] Multi-platform Google voice dialer

Any chance you could add 406 number support for contacts when direct dialing? I know you can't get access to the numbers, but you can a person's 406 number when they text you.

Could you check for something like the following in the notes section for each contact?:
GV:406-201-5689

If that exists you could dial it instead, which would make outgoing dialing even faster (and not always require a data connection).