Another pretty good collaboration by Google and Gizmo a week back added SIP support for Google Voice through Gizmo.  I just got my Google Voice and Gizmo integrated for both incoming and outgoing calls.  Google Voice call quality is amazing.  Its very easy to use and integrates well with your google address book.  Now, my next project is to get my phone, google and ovi to sync contacts and appointments so that I have a single list of contacts across all my collaboration services.

Several new USB devices have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After that (and on every consecutive plugging) this driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up. The WWAN gear maker Option calls that feature “ZeroCD (TM)”.  Reliance Netconnect modems are of type ZeroCD.

The first thing that you notice when you plug-in the modem is that, it mounts as a storage device.

Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: new full speed USB device using uhci_hcd and address 7
Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: configuration #1 chosen from 1 choice
Jul 11 17:07:34 jjaimon-ibm kernel: usbserial_generic 1-2:1.0: generic converter detected
Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: New USB device found, idVendor=19d2, idProduct=fff6
Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: Product: USB Storage
Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: Manufacturer: ZTE, Incorporated
Jul 11 17:07:34 jjaimon-ibm kernel: usb 1-2: SerialNumber: 000000000002
Jul 11 17:07:34 jjaimon-ibm kernel: Initializing USB Mass Storage driver...
Jul 11 17:07:34 jjaimon-ibm kernel: usbcore: registered new interface driver usb-storage
Jul 11 17:07:34 jjaimon-ibm kernel: USB Mass Storage support registered.

As you notice, the modem is not connected as a serial device and its registered to usb-storage.  One way of getting the serial device created is by unloading the usb-storage module and reloading the usbserial.  For eg.
modprobe -r usb-storage usbserial; modeprobe usbserial vendor=0x19d2 product=0xfff6

However, this alone will not be sufficient as the product id is still pointing to storage device.  This is where usb-modeswitch comes handy.

The device was listed as ZTE 8710 and there is an entry for this device already in my /etc/usb_modeswitch.conf.  All that I had to do was uncomment the following lines

# No. 2

TargetVendor=   0x19d2
TargetProduct=  0xfff1

You must run usb_modeswitch once the modem is connected.  You will see the following output if everything goes well.

jjaimon-ibm:/etc # usb_modeswitch -W

 * usb_modeswitch: tool for controlling "flip flop" mode USB devices
 * Version 1.0.2 (C) Josua Dietze 2009
 * Works with libusb 0.1.12 and probably other versions

Reading config file: /etc/usb_modeswitch.conf
DefaultVendor=  0x19d2
DefaultProduct= 0xfff6
TargetVendor=   0x19d2
TargetProduct=  0xfff1
TargetClass=    not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check enabled, settle time 2 seconds

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 005
usb_os_find_busses: Found 002
usb_os_find_busses: Found 004
usb_os_find_busses: Found 001
usb_os_find_busses: Found 003
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 004
usb_os_find_devices: Found 002 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 014 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003

Looking for target devices ...
 No devices in target mode or class found
Looking for default devices ...
 Found default devices (1)
Accessing device 014 on bus 001 ...
Using endpoints 0x0a (out) and 0x89 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached

Received inquiry data (detailed identification)
-------------------------
 Vendor String: ZTE
 Product String: USB Storage FFF1
Revision String: 2.31
-------------------------

Device description data (identification)
-------------------------
Manufacturer: ZTE, Incorporated
 Product: USB Storage
 Serial No.: 000000000002
-------------------------
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x0a ...
 OK, message successfully sent
USB error: could not clear/halt ep 10: Protocol error
Device is gone, skipping further steps ...
Checking for mode switch after 2 seconds settling time ...
USB error: failed to open /dev/bus/usb/001/014: No such file or directory
USB error: could not claim interface 0: Bad file descriptor
 Original device can't be accessed anymore. Good.
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 001 on 002
usb_os_find_devices: Found 003 on 004
usb_os_find_devices: Found 002 on 004
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 001 on 004
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 015 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
 Found a new device in target mode or class

Mode switch succeeded. Bye.

After this, you must have a /dev/ttyUSB0 device created. You can verify this with lsusb command.  You should see the new product id now.  wvdialconf should also report the presence of new modem device.

And with the following entries in your /etc/wvdial.conf, you should be able to connect...

[Dialer zte]
Init2 = AT+CRM=1
Stupid Mode = 1
Modem Type = Analog Modem
ISDN = 0
SetVolume = 0
FlowControl = Hardware (CRTSCTS)
Phone = #777
Modem = /dev/ttyUSB0
Username = 93xxxxxxx
Password = 93xxxxxxx
Dial Command = ATDT
Baud = 460800


jjaimon-ibm:/etc # wvdial zte
--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: AT+CRM=1
AT+CRM=1
OK
--> Sending: ATM0
ATM0
OK
--> Modem initialized.
--> Sending: ATDT#777
--> Waiting for carrier.
ATDT#777
CONNECT
--> Carrier detected.  Starting PPP immediately.
--> Starting pppd at Sat Jul 11 18:04:31 2009
--> Pid of pppd: 14798
--> Using interface ppp0
--> local  IP address 115.240.5.100
--> remote IP address 220.224.141.129
--> primary   DNS address 202.138.97.193
--> secondary DNS address 202.138.96.2
--> Script /etc/ppp/ip-up run successful
--> Default route Ok.
--> Nameserver (DNS) Ok.
--> Connected... Press Ctrl-C to disconnect

This can be automated by using a udev rule.  More information is provided here. There are also some references in reliance usergroups.   Here is one post that helped me to look at usb_modeswitch

Phoneboy posted the instructions to post to wordpress from lifeblog last year.  I have been using this in my N70 and it used to work great.  I knew he is smart enough to find a way to post from share online.   I was not surprised when I saw this post a few weeks back.

However, it was not that easy since I use N96 and Share Online 4.x.  I could add my blog as one of the service in the Share Online configured services in the phone.  I couldn’t post as it always failed.   I was not ready to gave up.  Setup requires two php scripts as described in the phoneboy post.  All instructions remain same.  I tried to debug this with the help of phoneboy.

Share Online sends two or more xml files depending on your post.   This can be tracked by enabling (by default) complete dump of phone upload. The first xml file looked something like this…

2009-04-08T01:17:02Z: method: POST
2009-04-08T01:17:02Z: rawpostdata:


2009-04-08T19:15:53Z
1
/9j/4AAQSkZJRgABAQAAAQABAZsoO6heBU7x81CykCsnFrckaxFMBwwIpcZ5NN2mkJm1avujHParKHmsvT5D930rTXpVJ3OWasyXGaa8YIoVscU5m4qiTMlG1yKrTcCr90uTkVQmBKmo
aNosqGXBxTfOqKUYY1HmoSNrk5mpPNqIAmlKEdaLIdx5kNKHPao1U5qxHFmk7IaQICRUypxUkceBUqrxSKsQeXRjFTEcVE3BxQFgBxShvWmAc08CmIkU04NUPSl3UCZ/
/2Q==

Nokia N96 (12.043) Series60/3.2 ISF/4.0.08.45

2009-04-14T01:09:15Z: action: post
2009-04-14T01:09:15Z: postaction
2009-04-14T01:09:15Z: filetype: .jpg
2009-04-14T01:09:15Z: filename: /lifeblog-10042009010.jpg
2009-04-14T01:09:15Z: id: url:/lifeblog-10042009010.jpg,type:Image,format:Image,summary:

The data is in the base64 encoded content tag.  lifeblog.php used to parse the code something like this…


} elseif(preg_match('/(?P

So the regular expression for preg_match need to be changed to <title.*> in all places.

I have been trying with sample icons in the phone since they are very small and easy to upload.  Problem started when I started uploading actual photographs.  I noticed that preg_match fails when the base64 encoded data is large.  (50-70KB approx).  I googled and found that this is a known problem with PCRE library that php uses for preg_match.   Some references suggested to increase the pcre backtrack_limit as a work around in the php.ini.

[Pcre]
;PCRE library backtracking limit.
pcre.backtrack_limit=5000000

I can post  to my wordpress blog now.  Here are the modified shareonline.php and lifeblog.php.  You will have to change all references to jjaimon.net/blogs in shareonline.php.  Follow the instructions given in the phoneboy blog.

Nokia provides a video converter software.  Its slow and works only on Windows.  Since I can mount Nokia mass-storage directly on my openSUSE11.1 laptop, I decided to use ffmpeg to convert videos.  You can copy the converted files to your Nokia device over cable or bluetooth.  Video Center recognizes the new video file and list them in the list of available videos.  I use h264 + AAC codecs which provides the best quality/compression rate for Nokia phones currently.  Surprisingly, I found this works better compared to Nokia’s software on my phone

Here is the script. Usage is very simple.
videoencode.sh source_file dest.mp4

#!/bin/bash

ffmpeg -y -i "$1" -acodec libfaac -ab 72k -s 320x240 -aspect 16:9 -vcodec libx264 -b 300k -qcomp 0.6 -qmin 16 -qmax 51 -qdiff 4 -flags +loop -cmp +chroma -subq 7 -refs 6 -g 250 -keyint_min 25 -rc_eq 'blurCplx^(1-qComp)' -sc_threshold 40 -me_range 12 -i_qfactor 0.71 -directpred 3 "$2" > /dev/null


Anyway, cloud computing is a different paradigm.  Cloud computing is not fluff, its future of IT. For end users, cloud computing means there are no hardware acquisition costs, no software licenses or upgrades to manage, no new employees or consultants to hire, no facilities to lease, no capital costs of any kind — and no hidden costs. Just a metered, per-use rate or subscription fee. Cloud computing is changing the economics of Computing from being a Capital investment to Utilities.  The only question is how secure is your data in the cloud?  How do you trust your cloud provider?  Do you place mission critical data in the cloud?

I was looking for an option to avoid this.  Then, I came across the sleep.d scripts.  You can place a script in

/usr/lib/pm-utils/sleep.d 

directory.  This has the format of pam scripts and will be executed based on the prefixed number on the filename.  I have the following file in my sleep.d to suspend my running VM before the laptop is suspended.

/usr/lib/pm-utils/sleep.d/11pm-suspend-vm
#!/bin/bash

exit $?


My first disappointment started with desktop itself.  I have been upgrading my desktop from openSUSE 10.2 days.  So, I decided to go for a re-install instead of upgrade.  The first blow was in terms of inability to restore my MBR using grub.  I have a dual boot system and I knew that I will not be able to boot into Windows  XP if I format my ‘/’ volume without restoring MBR.

I tried all possible windows CDs and they all _consistently_ failed to restore MBR.  Further googling helped me to locate mbrfix.  mbrfix is a nice little windows executable that helps you repair some of the low level issues (if you know what you are doing)

I decided to create a small partition for /boot because of this bad experience.  Obvious choice was to split / partition and create a 100MB volume for /boot.  My partition table looked something like this now.

fdisk -l

Disk /dev/sda: 100.0 GB, 100030242816 bytes
240 heads, 63 sectors/track, 12921 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Disk identifier: 0x00000021

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        2174    16435408+   7  HPFS/NTFS
/dev/sda2           12193       12921     5511240   12  Compaq diagnostics
/dev/sda3            2175        2452     2101680   82  Linux swap / Solaris
/dev/sda4   *        2453       12192    73634400    f  W95 Ext'd (LBA)
/dev/sda5            3808        5433    12292528+   7  HPFS/NTFS
/dev/sda6            5434        8142    20480008+   b  W95 FAT32
/dev/sda7            8143       10174    15361888+  83  Linux
/dev/sda8           10175       12192    15256048+  83  Linux
/dev/sda9            2453        3795    10146937   83  Linux
/dev/sda10           3795        3807       96358+  83  Linux

Partition table entries are not in disk order

You might notice an out of order start point for sda10 and that was exactly what fdisk was trying to tell me. After successfully installing VMWare Workstation 6.5.1, I tried to bring up my existing VM. VMWare continues to complain about its inability to retrieve disk information.

Unable to retrieve disk information: The partition table on the physical disk has changed since the disk was created. Remove the physical disk from the virtual machine, then add it again

I tried to contact VMWare and no one could help me here.  I figured out after a lot of research that an out of order partition table can cause problems with many applications and VMWare is one of them.  The suggestion was to reorder partition table.  Fun started here.

Note: Do not try the following instructions unless you know what you are doing.  These changes require some knowledge about your disk layout and linux boot process.  I will not take any responsibility if you can’t boot into your machine after following the instructions.

I used fdisk’s expert mode and re-ordered my partition table.  I noted down my old partition table layout and mapped the start, end and Id with the new layout.  This is required to adjust some of the configuration files. It looks like this now.

Disk /dev/sda: 100.0 GB, 100030242816 bytes
240 heads, 63 sectors/track, 12921 cylinders
Units = cylinders of 15120 * 512 = 7741440 bytes
Disk identifier: 0x00000021

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        2174    16435408+   7  HPFS/NTFS
/dev/sda2            2175        2452     2101680   82  Linux swap / Solaris
/dev/sda3   *        2453       12192    73634400    f  W95 Ext'd (LBA)
/dev/sda4           12193       12921     5511240   12  Compaq diagnostics
/dev/sda5            2453        3795    10146937   83  Linux
/dev/sda6            3795        3807       96358+  83  Linux
/dev/sda7            3808        5433    12292528+   7  HPFS/NTFS
/dev/sda8            5434        8142    20480008+   b  W95 FAT32
/dev/sda9            8143       10174    15361888+  83  Linux
/dev/sda10          10175       12192    15256048+  83  Linux

This is not enough.  You need to readjust your boot order.  I did the following as well.

1. Updated /etc/fstab entries based on the new partition layout
2. Updated /etc/grub.conf and /boot/grub/menu.lst based. Note that, partition table starts from 1 and grub count starts from 0 (number Zero)

I rebooted my machine and it doesn’t find a valid boot record. I tried to use the recovery option from the install DVD. Though YaST says, grub is reconfigured, I still can’t boot. After further googling and some research, I decided to use grub command line option and re-intialize grub.

In grub command line mode,
grub> root (hd0, 5)
grub> setup (hd0)

Everything looks okay now and I’m writing this blog using Windows Live Writer from one of my Windows VMs hosted on my openSUSE 11.1.