Notices

Originally Posted by uvatbc

Is there anything in particular that is difficult to understand? If there's anything that I can do to make qgvdial easier to use and understand, tell me and I'll work through it.

Originally Posted by Swirnoff

Didn't mean to aggrivate(?) you with that question. I was just curious if you were planning on any other updates since I haven't read the whole thread. But thanks for the work anyway.

Originally Posted by uvatbc

No-no I didn't mean it like that. I was stating my desire for user feedback.

Originally Posted by xur17

I tried installing the most recent version of qgvdial, and I am getting the following issue:

Code:

--- 2011-02-21 12:26:10 ---
Start reading package lists
--- 2011-02-21 12:26:19 ---
Finished reading package lists
--- 2011-02-21 12:26:19 ---
Start fetching package dates
--- 2011-02-21 12:26:20 ---
need to fetch date for 0 packages
--- 2011-02-21 12:26:20 ---
sent 0 requests, received 0 replies with 0 errors
--- 2011-02-21 12:26:20 ---
Finished fetching package dates
--- 2011-02-21 12:26:31 ---
/usr/bin/apt-get -qsy --allow-unauthenticated -o Dir::Etc::sourcelist=/opt/fapman-cache/sources.list -o Dir::State::lists=/opt/fapman-cache/lists -o Dir::Etc::sourceparts="" --auto-remove install qgvdial
--- 2011-02-21 12:27:14 ---
Output from last process:
---
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  qgvdial
0 upgraded, 1 newly installed, 0 to remove and 38 not upgraded.
Inst qgvdial (0.2.385-1 Extras-devel:2.0/fremantle)
Conf qgvdial (0.2.385-1 Extras-devel:2.0/fremantle)

--- 2011-02-21 12:27:42 ---
/usr/bin/apt-get -qy --allow-unauthenticated -o DPkg::options::=--force-confnew -o Dir::Etc::sourcelist=/opt/fapman-cache/sources.list -o Dir::State::lists=/opt/fapman-cache/lists -o Dir::Etc::sourceparts="" --auto-remove install qgvdial
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  qgvdial
0 upgraded, 1 newly installed, 0 to remove and 38 not upgraded.
Need to get 0B/422kB of archives.
After this operation, 1180kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  qgvdial
Authentication warning overridden.
Selecting previously deselected package qgvdial.
(Reading database ... 26659 files and directories currently installed.)
Unpacking qgvdial (from .../qgvdial_0.2.385-1_armel.deb) ...
Setting up qgvdial (0.2.385-1) ...
2011-02-21 12:27:59.712 : 3 : qgv-tp account not found. Creating .. 
2011-02-21 12:27:59.776 : 3 : Error creating qgvtp telepathy account  QDBusError("org.freedesktop.Telepathy.Error.InvalidArgument", "Protocol qgv not found") 
dpkg: error processing qgvdial (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 qgvdial
E: Sub-process /usr/bin/dpkg returned an error code (1)

I even tried running "apt-get remove --purge qgvdial" and then reinstalling it, but I am getting the same issue. Any ideas?

Originally Posted by uvatbc

I finally managed to get into a Starbucks. 2 hours of debugging and sugar = Tons of bugfixes which fixes the starbucks effect at least on my laptop.
I'll fire a build to get this on the n900.
Please test!

Originally Posted by uvatbc

Reboot n900 and install qgvdial. I haven't yet pinned down the cause of this, but a reboot *always* fixes it.

Originally Posted by kbyork

Looks good!
I tested at 2 hotspots. Calls timed-out after 15-16 secs.
Then I established a good WiFi connection, and made a call... success. (I did NOT get the "Another call is in progress" message)

Testing done with version 0.2.383-1

I only tested "making a call" [i.e. did NOT test "canceling a call", etc]

Originally Posted by kbyork

WISH-LIST:

1. Fallback Google Dialing (if data connection fails)... via {GV-voicemail}pp{*}p{pin}p{destination-number}
   (On GV website, under PHONES > ADVANCED SETTINGS > VOICEMAIL ACCESS: there are options for whether the {*} and|or the {PIN number} is required. Hopefully you will be able to add a matching user setting.
   This is just an elaboration of a previous request)
   
2. When reading in the GV INBOX, you do a CallerID look-up using GV CONTACTS list.
   If the look-up fails, then label it with its phone number (rather than labeling it as "Unknown").
3. Increase font-size for INBOX menus (like you did for CONTACTS menus)
4. Remember previously selected INBOX (rather than defaulting to INBOX ALL)
5. When enumerating Telepathy Accounts; skip disabled telepathy accounts.

comments:

1. Unfortunately time consuming to add; but it will also be damn useful.
2. If you can't find the Caller's Name, then the phone number is still more useful than the word "unknown":

   Inbox: Number could not be identified: "+1315280????" Labeling it as unknown.
   Inbox: Number could not be identified: "+1315849????" Labeling it as unknown.
   Inbox: Number could not be identified: "+1315790????" Labeling it as unknown.

3. just ergonomics.
4. just heuristics.
5. just aesthetics.
   I have one VoIP provider for USA calls, and another for International calls.
   The International provider is usually DISABLED:

   "Account cmName = sofiasip ADDED!"
   Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)

   Obviously, this will effect very few people; so if this is a chore, then please ignore this request.