Re: Official Debian port with FSO
In 'phonebookTupleToNumber' in 'const.py' I changed the 'assert' to just spit out a message, like this: # assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype if not ntype in ( 129, 145, 185, 208 ): print unknown type %i for %s % ( ntype, str(nstring) ) This is the output I saw: unknown type 255 for #225# unknown type 255 for #646# unknown type 255 for #674# T-Mobile (USA) had pre-programmed these three phone numbers into the SIM card, then I made duplicates (by way of a confusing UI on a Samsung phone). I don't know if the originals or my duplicates had the unknown type. Is there a more formal place I should report this? - Bruce P.S. I now have FSO/zhone working under Debian on my FreeRunner! Joachim Breitner wrote: Hi, Am Samstag, den 16.08.2008, 18:07 -0400 schrieb xaos x: That worked for outgoing calls. I'm still receiving the following upon incoming calls: Traceback (most recent call last): File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 218, in _readyToRead self.readyToRead( data ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 354, in readyToRead self.parser.feed( data, not self.q.empty() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 127, in feed nextstate = self.state( b, haveCommand ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 177, in state_inline_r return self.unsolicitedLineCompleted() File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 237, in unsolicitedLineCompleted self.unsolicited( self.lines ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py, line 45, in logIt result = fn( *args, **kwargs ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 526, in _handleUnsolicitedResponse method( values.strip() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/modems/ti_calypso/unsolicited.py, line 128, in percentCPI info[peer] = const.phonebookTupleToNumber( number[1:-1], int(ntype) ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/const.py, line 805, in phonebookTupleToNumber assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype AssertionError: unknown type 161 The FSO stack does not yet know and support all possible number types. The 185 was recently added by me after a similar error... Please do the following: * Check if that error also happens when you open the phonebook * Add the 161 to the list of numbers in const.py * Find out what number was causing this (e.g. by adding print statements around the above line outputting the number) and tell us about it. Thanks, Joachim ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Hi, Am Freitag, den 22.08.2008, 11:32 -0400 schrieb Bruce Adams: In 'phonebookTupleToNumber' in 'const.py' I changed the 'assert' to just spit out a message, like this: # assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype if not ntype in ( 129, 145, 185, 208 ): print unknown type %i for %s % ( ntype, str(nstring) ) This is the output I saw: unknown type 255 for #225# unknown type 255 for #646# unknown type 255 for #674# T-Mobile (USA) had pre-programmed these three phone numbers into the SIM card, then I made duplicates (by way of a confusing UI on a Samsung phone). I don't know if the originals or my duplicates had the unknown type. Probably the original ones, as the duplicate will be created as „normal“ entries, I assume. Is there a more formal place I should report this? Yes, please see file it at http://trac.freesmartphone.org/ticket/, preferably after checking that it also happens with the milestone2 FSO image. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
arne anka wrote: Is there any chance someone might be interested in making an image of their Debian-SD card available on the 'web, so that all we would need shouldn't be to hard -- but where to put the image? it would at least be about 512mb -- with a reasonable number of downloads ones traffic limit might be reached very soon. I'd be happy to host this on downloads.openmoko.org. Michael ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Michael Shiloh wrote: arne anka wrote: Is there any chance someone might be interested in making an image of their Debian-SD card available on the 'web, so that all we would need shouldn't be to hard -- but where to put the image? it would at least be about 512mb -- with a reasonable number of downloads ones traffic limit might be reached very soon. I'd be happy to host this on downloads.openmoko.org. Michael I don't know where downloads.openmoko.org is hosted, or what the impact of servicing multiple lagrge downloads would be, but bittorrents always an option. ~ Matt ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
On Sat, Aug 16, 2008 at 4:48 PM, xaos x [EMAIL PROTECTED] wrote: I notice that upon a successful outgoing call connection, it looks like the GUI is not receiving or maybe not checking for the call status as the dialpad is not closing to display the call status screen. You can close the pyphone_phone manually and open zhone again, which will display the pyphone_call screen, but I should think the intuitive response of it would be to call pyphone_call once an active call state is acheived. I'm digging through this code for the first time today so I'm still trying to familiarize myself with the flow and I can't figure out where the checking would best be performed as yet or else I'd suggest something. Till then, I leave that to you guys. :} -Tom There's a bug you could add info to http://trac.freesmartphone.org/ticket/59 ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Is there any chance someone might be interested in making an image of their Debian-SD card available on the 'web, so that all we would need to do is copy the image to a compatible-sized SD card and away we go? I'd sure like to test this, if someone wants to do it .. ; -- Jay Vaughan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
On Mon, 18 Aug 2008 14:17:30 +0200 Jay Vaughan [EMAIL PROTECTED] wrote: Is there any chance someone might be interested in making an image of their Debian-SD card available on the 'web, so that all we would need to do is copy the image to a compatible-sized SD card and away we go? I'd sure like to test this, if someone wants to do it .. Well I have no SD-Reader so I try to do it by ssh with: ssh [EMAIL PROTECTED] 'cd ; tar czvf - *' | cat debian_image.tar.gz I dunno if this works they way you want it but I'll upload it if it's ready and you can test it. signature.asc Description: PGP signature ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Is there any chance someone might be interested in making an image of their Debian-SD card available on the 'web, so that all we would need shouldn't be to hard -- but where to put the image? it would at least be about 512mb -- with a reasonable number of downloads ones traffic limit might be reached very soon. to do is copy the image to a compatible-sized SD card and away we go? mounting the iso and rsync'ing works too, that was the way i moved my debian from a 512 to a 1024mb sd card. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Well I have no SD-Reader so I try to do it by ssh with: ssh [EMAIL PROTECTED] 'cd ; tar czvf - *' | cat debian_image.tar.gz I dunno if this works they way you want it but I'll upload it if it's ready and you can test it. I don't think (correct me if I'm wrong, can't say I've used tar like that before) that will give you a true image, i.e. including partition tables and such. You could use 'dd' along the following lines in your SSH command: dd if=/dev/mmcblk0 of=debian_image.iso bs=512 The resulting ISO should compress down a reasonable amount (especially if the Debian install doesn't consume all of the SD card, not sure how much it takes up as I haven't tried it) for downloading over the internet, the only problem is that you'd need to use an image taken from the same sized card as the one you're flashing it to. Aaron ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Aaron Sowry wrote: Well I have no SD-Reader so I try to do it by ssh with: ssh [EMAIL PROTECTED] 'cd ; tar czvf - *' | cat debian_image.tar.gz I dunno if this works they way you want it but I'll upload it if it's ready and you can test it. I don't think (correct me if I'm wrong, can't say I've used tar like that before) that will give you a true image, i.e. including partition tables and such. You could use 'dd' along the following lines in your SSH command: dd if=/dev/mmcblk0 of=debian_image.iso bs=512 That'll include residual information you had on the card before installing debian. dd if=/dev/zero of=/dev/mmcblk0, then reinstalling debian, and doing this would zero out the card and yield a better compression ratio. I've done the tar trick in the past to upgrade desktop hard drives. It works fine if you're careful. Also, the resulting image is compatible with anything that's large enough to hold it. Note that FR's cd sometimes goes to /root or /home/root. This is better (and untested): 'tar --exclude=/wherever/internal/flash/is/mounted --exclude=/proc --exclude=... -C / czvf - .' (add an --exclude for each mounted filesystem...) To install the tarball, you have repartition, reformat and untar the image. Then recreate any mount points that you --excluded (/proc, etc...) Also, you might have to muck with u-boot, depending on how u-boot works. (You have to muck with u-boot either way the first time you install debian, so this isn't a big deal...) -Rusty The resulting ISO should compress down a reasonable amount (especially if the Debian install doesn't consume all of the SD card, not sure how much it takes up as I haven't tried it) for downloading over the internet, the only problem is that you'd need to use an image taken from the same sized card as the one you're flashing it to. Aaron ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Am Sonntag 17 August 2008 00:07:28 schrieb xaos x: That worked for outgoing calls. I'm still receiving the following upon incoming calls: Traceback (most recent call last): File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.p y, line 218, in _readyToRead self.readyToRead( data ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.p y, line 354, in readyToRead self.parser.feed( data, not self.q.empty() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py , line 127, in feed nextstate = self.state( b, haveCommand ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py , line 177, in state_inline_r return self.unsolicitedLineCompleted() File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py , line 237, in unsolicitedLineCompleted self.unsolicited( self.lines ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py , line 45, in logIt result = fn( *args, **kwargs ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.p y, line 526, in _handleUnsolicitedResponse method( values.strip() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/modems/ti_cal ypso/unsolicited.py, line 128, in percentCPI info[peer] = const.phonebookTupleToNumber( number[1:-1], int(ntype) ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/const.py , line 805, in phonebookTupleToNumber assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype AssertionError: unknown type 161 Heh, it's amazing with all these out-of-spec numbers :) The only ones mentioned in the official spec are 129 and 145. I'd be grateful for additional information, since I want to classify these numbers to perhaps treat them specially. -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
How did you do suspend??? I just get the screen darkened and if touch it I get the screensaver you are talking about but I couldn't find out how to do suspend? I didn't suspend it manually. The display switches off on a timeout. I press the power button to wake it up. Btw, USB networking is working. My bad. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
On Sat, Aug 16, 2008 at 2:10 PM, sparky mat [EMAIL PROTECTED] wrote: I tried out the official debian port with FSO (http://wiki.debian.org/DebianOnFreeRunner) and it works quite nicely!! Great! 3) Zhone. Zhone looks quite nice and simple and I do like it. However, I would like a standard Xfce4 desktop (which I am gonna customize). Is this as simple as installing gdm + xfce4, and making a launcher for Zhone? As far as I know, yes. I would have done it but didn't have enough space on my 512MB card. 4) Touchscreen calibration (Atleast that's what i think it is) - Every time I resume from suspend, 4 boxes with 1-4 come up and (assuming its touchscreen calibration) I press them in order to make it go away. How can I turn this off? Is this a Zhone feature? I suppose it's called keylock or something like that, not calibration :) So it's there only to prevent unintentional actions. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
how many mb needs debian by default on freerunner? oO 2008/8/16 sparky mat [EMAIL PROTECTED] I suppose it's called keylock or something like that, not calibration :) So it's there only to prevent unintentional actions. Ahh.. ok! That makes sense! And yeah, this would hardly suffice for ts calibration .. lol ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
On Sat, Aug 16, 2008 at 2:50 PM, Thomas Bertani [EMAIL PROTECTED] wrote: how many mb needs debian by default on freerunner? oO About 400-450M so you can do it on 512M card but can't install much more there, for example no space enough for xfce4 r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
2008/8/16 Risto H. Kurppa [EMAIL PROTECTED] On Sat, Aug 16, 2008 at 2:50 PM, Thomas Bertani [EMAIL PROTECTED] wrote: how many mb needs debian by default on freerunner? oO About 400-450M so you can do it on 512M card but can't install much more there, for example no space enough for xfce4 in your opinion could I (without free space problems, installing xfce) use a 2 gb sd for debian AND asu? (how many megabytes needs asu?? oO) And, sorry, another question... gnome could run? how many mbs needs? Maybe I want too XD Thx ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
And, sorry, another question... gnome could run? how many mbs needs? Maybe I want too XD haha.. I really don't think Gnome would be a good idea! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
On Sat, Aug 16, 2008 at 5:40 PM, Thomas Bertani [EMAIL PROTECTED] wrote: 2008/8/16 sparky mat [EMAIL PROTECTED] And, sorry, another question... gnome could run? how many mbs needs? Maybe I want too XD haha.. I really don't think Gnome would be a good idea! lol but if I want it could run XD :-) . trying gdm + xfce4 now.. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
2008/8/16 sparky mat [EMAIL PROTECTED] On Sat, Aug 16, 2008 at 5:40 PM, Thomas Bertani [EMAIL PROTECTED]wrote: 2008/8/16 sparky mat [EMAIL PROTECTED] And, sorry, another question... gnome could run? how many mbs needs? Maybe I want too XD haha.. I really don't think Gnome would be a good idea! lol but if I want it could run XD :-) . trying gdm + xfce4 now.. sbav sbav how it runs? pleeease post some screenshots!!! :D ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
On Sat, 16 Aug 2008 17:04:49 +0530 sparky mat [EMAIL PROTECTED] wrote: I didn't suspend it manually. The display switches off on a timeout. I press the power button to wake it up. That's no suspend what you mean. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Hi, Am Samstag, den 16.08.2008, 16:40 +0530 schrieb sparky mat: I tried out the official debian port with FSO (http://wiki.debian.org/DebianOnFreeRunner) and it works quite nicely!! However, i ran into some problems. 1) Can't make calls. It shows my operator and signal strength correctly. However, when I dial a number and hit the big green tick button (which I am assuming is the call button), nothing happens. Am I pressing the wrong button? None of the others work anyway. Not sure what’s wrong there. Once you get ssh to work, you should run frameworkd and zhone from the command line to check the error messages. 2) No USB networking. Is the module called g_ether? I couldn't find it. How can I recompile the kernel? Is it the same as mentioned here - http://wiki.openmoko.org/wiki/Manual_Debian#.28Optional.29_Recompiling_Kernel_to_Add_Drivers ? Now that’s strange, it works for me and I have not heard from others having problems. Is your /etc/network/interfaces file ok? 3) Zhone. Zhone looks quite nice and simple and I do like it. However, I would like a standard Xfce4 desktop (which I am gonna customize). Is this as simple as installing gdm + xfce4, and making a launcher for Zhone? Should be, but if you install gdm, make sure you remove zhone-session (well, it should conflict anyways) 4) Touchscreen calibration (Atleast that's what i think it is) - Every time I resume from suspend, 4 boxes with 1-4 come up and (assuming its touchscreen calibration) I press them in order to make it go away. How can I turn this off? Is this a Zhone feature? This is just the key lock featuer. Press them in order to unlock the phone. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
sparky mat wrote: I tried out the official debian port with FSO (http://wiki.debian.org/DebianOnFreeRunner) and it works quite nicely!! However, i ran into some problems. 1) Can't make calls. It shows my operator and signal strength correctly. However, when I dial a number and hit the big green tick button (which I am assuming is the call button), nothing happens. Am I pressing the wrong button? None of the others work anyway. Same for me. (Optus 3g usim) Not able to dial. I can receive calls, but not answer them. Just rings. mj ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
the frameworkd shows this when the dial button is pressed:
(framework.subsystems.ogsmd.modems.ti_calypso.channel.CallChannel object at
0x5d2ed0 queue is: deque([(u'ATD4078972297;\r\n', bound method
CallHandler.responseFromChannel of
framework.subsystems.ogsmd.modems.ti_calypso.mediator.CallHandler object at
0x615550, bound method CallHandler.errorFromChannel of
framework.subsystems.ogsmd.modems.ti_calypso.mediator.CallHandler object at
0x615550, 3600)]))
Traceback (most recent call last):
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 230, in _readyToSend
self.readyToSend()
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py,
line 45, in logIt
result = fn( *args, **kwargs )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 345, in readyToSend
self.serial.write( self.q.peek()[0] ) # channel data
File /usr/lib/python2.5/site-packages/serial/serialposix.py, line 330, in
write
raise TypeError('expected str, got %s' % type(data))
TypeError: expected str, got type 'unicode'
phone won't dial.
Upon incoming call, it displays this:
ogsmdINFO
(framework.subsystems.ogsmd.modems.ti_calypso.channel.MiscChannel object at
0x615350: unsolicited data incoming: '+CRING: VOICE')
for every ring but the phone doesn't actually display any notification of an
incoming call.
Hope this helps.
-Tom
- Original Message -
From: Matt [EMAIL PROTECTED]
To: Support for Openmoko Device Owners support@lists.openmoko.org
Sent: Saturday, August 16, 2008 11:18:52 AM GMT -05:00 US/Canada Eastern
Subject: Re: Official Debian port with FSO
sparky mat wrote:
I tried out the official debian port with FSO
(http://wiki.debian.org/DebianOnFreeRunner) and it works quite nicely!!
However, i ran into some problems.
1) Can't make calls. It shows my operator and signal strength correctly.
However, when I dial a number and hit the big green tick button (which I
am assuming is the call button), nothing happens. Am I pressing the
wrong button? None of the others work anyway.
Same for me. (Optus 3g usim)
Not able to dial.
I can receive calls, but not answer them. Just rings.
mj
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Sorry I left out an error traceback. The output below is the initial error upon
incoming call:
Traceback (most recent call last):
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 218, in _readyToRead
self.readyToRead( data )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 354, in readyToRead
self.parser.feed( data, not self.q.empty() )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py,
line 127, in feed
nextstate = self.state( b, haveCommand )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py,
line 177, in state_inline_r
return self.unsolicitedLineCompleted()
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py,
line 237, in unsolicitedLineCompleted
self.unsolicited( self.lines )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py,
line 45, in logIt
result = fn( *args, **kwargs )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 526, in _handleUnsolicitedResponse
method( values.strip() )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/modems/ti_calypso/unsolicited.py,
line 128, in percentCPI
info[peer] = const.phonebookTupleToNumber( number[1:-1], int(ntype) )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/const.py,
line 805, in phonebookTupleToNumber
assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype
AssertionError: unknown type 161
ogsmdINFO
(framework.subsystems.ogsmd.modems.ti_calypso.channel.MiscChannel object at
0x615350: unsolicited data incoming: '+CRING: VOICE')
ogsmdWARNING CALLCHANNEL: UNHANDLED INTERMEDIATE: +CRING: VOICE
-Tom
- Original Message -
From: xaos x [EMAIL PROTECTED]
To: Support for Openmoko Device Owners support@lists.openmoko.org
Sent: Saturday, August 16, 2008 4:37:59 PM GMT -05:00 US/Canada Eastern
Subject: Re: Official Debian port with FSO
the frameworkd shows this when the dial button is pressed:
(framework.subsystems.ogsmd.modems.ti_calypso.channel.CallChannel object at
0x5d2ed0 queue is: deque([(u'ATD4078972297;\r\n', bound method
CallHandler.responseFromChannel of
framework.subsystems.ogsmd.modems.ti_calypso.mediator.CallHandler object at
0x615550, bound method CallHandler.errorFromChannel of
framework.subsystems.ogsmd.modems.ti_calypso.mediator.CallHandler object at
0x615550, 3600)]))
Traceback (most recent call last):
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 230, in _readyToSend
self.readyToSend()
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py,
line 45, in logIt
result = fn( *args, **kwargs )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 345, in readyToSend
self.serial.write( self.q.peek()[0] ) # channel data
File /usr/lib/python2.5/site-packages/serial/serialposix.py, line 330, in
write
raise TypeError('expected str, got %s' % type(data))
TypeError: expected str, got type 'unicode'
phone won't dial.
Upon incoming call, it displays this:
ogsmdINFO
(framework.subsystems.ogsmd.modems.ti_calypso.channel.MiscChannel object at
0x615350: unsolicited data incoming: '+CRING: VOICE')
for every ring but the phone doesn't actually display any notification of an
incoming call.
Hope this helps.
-Tom
- Original Message -
From: Matt [EMAIL PROTECTED]
To: Support for Openmoko Device Owners support@lists.openmoko.org
Sent: Saturday, August 16, 2008 11:18:52 AM GMT -05:00 US/Canada Eastern
Subject: Re: Official Debian port with FSO
sparky mat wrote:
I tried out the official debian port with FSO
(http://wiki.debian.org/DebianOnFreeRunner) and it works quite nicely!!
However, i ran into some problems.
1) Can't make calls. It shows my operator and signal strength correctly.
However, when I dial a number and hit the big green tick button (which I
am assuming is the call button), nothing happens. Am I pressing the
wrong button? None of the others work anyway.
Same for me. (Optus 3g usim)
Not able to dial.
I can receive calls, but not answer them. Just rings.
mj
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
I'm not sure what string type the write function is expecting the variable data to be, but doing a data = data.encode(utf-8) before the isinstance() check in def write(self,data) gets rid of the error output, however it still will not dial. -Tom ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Hi,
Am Samstag, den 16.08.2008, 16:37 -0400 schrieb xaos x:
the frameworkd shows this when the dial button is pressed:
(framework.subsystems.ogsmd.modems.ti_calypso.channel.CallChannel object at
0x5d2ed0 queue is: deque([(u'ATD4078972297;\r\n', bound method
CallHandler.responseFromChannel of
framework.subsystems.ogsmd.modems.ti_calypso.mediator.CallHandler object at
0x615550, bound method CallHandler.errorFromChannel of
framework.subsystems.ogsmd.modems.ti_calypso.mediator.CallHandler object at
0x615550, 3600)]))
Traceback (most recent call last):
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 230, in _readyToSend
self.readyToSend()
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py,
line 45, in logIt
result = fn( *args, **kwargs )
File
/var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py,
line 345, in readyToSend
self.serial.write( self.q.peek()[0] ) # channel data
File /usr/lib/python2.5/site-packages/serial/serialposix.py, line 330, in
write
raise TypeError('expected str, got %s' % type(data))
TypeError: expected str, got type 'unicode'
phone won't dial.
Upon incoming call, it displays this:
ogsmdINFO
(framework.subsystems.ogsmd.modems.ti_calypso.channel.MiscChannel object at
0x615350: unsolicited data incoming: '+CRING: VOICE')
for every ring but the phone doesn't actually display any notification of an
incoming call.
Hope this helps.
Thanks for the report. We are currently debugging it, and try to find a
proper fix. For a quick workaround, just do the change described in
http://trac.freesmartphone.org/ticket/90.
Thanks to mickey into looking at that!
Greetings,
Joachim
--
Joachim nomeata Breitner
Debian Developer
[EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
That worked for outgoing calls. I'm still receiving the following upon incoming calls: Traceback (most recent call last): File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 218, in _readyToRead self.readyToRead( data ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 354, in readyToRead self.parser.feed( data, not self.q.empty() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 127, in feed nextstate = self.state( b, haveCommand ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 177, in state_inline_r return self.unsolicitedLineCompleted() File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 237, in unsolicitedLineCompleted self.unsolicited( self.lines ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py, line 45, in logIt result = fn( *args, **kwargs ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 526, in _handleUnsolicitedResponse method( values.strip() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/modems/ti_calypso/unsolicited.py, line 128, in percentCPI info[peer] = const.phonebookTupleToNumber( number[1:-1], int(ntype) ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/const.py, line 805, in phonebookTupleToNumber assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype AssertionError: unknown type 161 -Tom - Original Message - From: Joachim Breitner [EMAIL PROTECTED] To: support@lists.openmoko.org Sent: Saturday, August 16, 2008 5:13:38 PM GMT -05:00 US/Canada Eastern Subject: Re: Official Debian port with FSO Hi, Am Samstag, den 16.08.2008, 17:00 -0400 schrieb xaos x: I'm not sure what string type the write function is expecting the variable data to be, but doing a data = data.encode(utf-8) before the isinstance() check in def write(self,data) gets rid of the error output, however it still will not dial. I have applied an work-around after all and uploaded a new package that you might want to try out (apt-get update; apt-get -u upgrade should do it), see http://git.debian.org/?p=pkg-fso/frameworkd.git;a=commitdiff;h=8f6b1bf96759b73b98e5e210f825ce1318179cb0 for the diff. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Hi, Am Samstag, den 16.08.2008, 18:07 -0400 schrieb xaos x: That worked for outgoing calls. I'm still receiving the following upon incoming calls: Traceback (most recent call last): File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 218, in _readyToRead self.readyToRead( data ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 354, in readyToRead self.parser.feed( data, not self.q.empty() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 127, in feed nextstate = self.state( b, haveCommand ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 177, in state_inline_r return self.unsolicitedLineCompleted() File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/parser.py, line 237, in unsolicitedLineCompleted self.unsolicited( self.lines ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/decor.py, line 45, in logIt result = fn( *args, **kwargs ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/channel.py, line 526, in _handleUnsolicitedResponse method( values.strip() ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/modems/ti_calypso/unsolicited.py, line 128, in percentCPI info[peer] = const.phonebookTupleToNumber( number[1:-1], int(ntype) ) File /var/lib/python-support/python2.5/framework/subsystems/ogsmd/gsm/const.py, line 805, in phonebookTupleToNumber assert ntype in ( 129, 145, 185, 208 ), unknown type %i % ntype AssertionError: unknown type 161 The FSO stack does not yet know and support all possible number types. The 185 was recently added by me after a similar error... Please do the following: * Check if that error also happens when you open the phonebook * Add the 161 to the list of numbers in const.py * Find out what number was causing this (e.g. by adding print statements around the above line outputting the number) and tell us about it. Thanks, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
Adding 161 to const.py fixed it. Adding print(%s % nstring) output the incoming number which was my own home number as I was testing. It was in the format of 1222333. I don't see the error upon opening the phonebook. - Original Message - From: Joachim Breitner [EMAIL PROTECTED] To: support@lists.openmoko.org Sent: Saturday, August 16, 2008 6:13:20 PM GMT -05:00 US/Canada Eastern Subject: Re: Official Debian port with FSO Hi, AssertionError: unknown type 161 The FSO stack does not yet know and support all possible number types. The 185 was recently added by me after a similar error... Please do the following: * Check if that error also happens when you open the phonebook * Add the 161 to the list of numbers in const.py * Find out what number was causing this (e.g. by adding print statements around the above line outputting the number) and tell us about it. Thanks, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port with FSO
I notice that upon a successful outgoing call connection, it looks like the GUI is not receiving or maybe not checking for the call status as the dialpad is not closing to display the call status screen. You can close the pyphone_phone manually and open zhone again, which will display the pyphone_call screen, but I should think the intuitive response of it would be to call pyphone_call once an active call state is acheived. I'm digging through this code for the first time today so I'm still trying to familiarize myself with the flow and I can't figure out where the checking would best be performed as yet or else I'd suggest something. Till then, I leave that to you guys. :} -Tom ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port
Not sure if this is the reason, but I used the OM2008.8 kernel [1] and had no problems with Debian. There are a few minor error messages while the boot sequence, but so far no problem on my GTA02v5. (I remember a complaint about a driver that was only available on gta01). Thomas [1] http://downloads.openmoko.org/releases/Om2008.8/ Joerg Lippmann wrote: I tried it just yesternight. It didn't work. The SD(HC)-Card was prepard on my main machine like this: 1. partition: 8MB formatted vfat for uImage.bin (apart from that: empty). I wasn't sure which kernel-Image to use so I took one from ASU. 2. partition: 2GB formatted ext2. I copied all the directories from the .tar.bz2 (Prebuilt Filesystem) to this partition. wasn't sure which kernel-Image to use so I took one from ASU. It did indeed boot, but when the kernel tried to start init, it panicked: Kernel panic - not syncing: No init found. Try passing init= option to kernel. ... but I really don't know how to do that without screwing up Neo. [EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port
Am Freitag 15 August 2008 schrieb Thomas Krahn: Not sure if this is the reason, but I used the OM2008.8 kernel [1] and had no problems with Debian. There are a few minor error messages while the boot sequence, but so far no problem on my GTA02v5. (I remember a complaint about a driver that was only available on gta01). Tried that kernel. Now my old problem is fixed but I encountered another one. I get lots of messages: /sbin/getty: cannot excute binary file So do neo1973 and freerunner use different binary formats? btw: how can I reset the device once it panicked? Do I really have to remove the battery everytime? [EMAIL PROTECTED] -- We will bring freedom and Leberwurst to the Welt, ob sie will oder nicht. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Official Debian port
Joerg Lippmann wrote: Am Freitag 15 August 2008 schrieb Thomas Krahn: Not sure if this is the reason, but I used the OM2008.8 kernel [1] and had no problems with Debian. There are a few minor error messages while the boot sequence, but so far no problem on my GTA02v5. (I remember a complaint about a driver that was only available on gta01). Tried that kernel. Now my old problem is fixed but I encountered another one. I get lots of messages: /sbin/getty: cannot excute binary file So do neo1973 and freerunner use different binary formats? btw: how can I reset the device once it panicked? Do I really have to remove the battery everytime? i know there is a button on the debug board can reset the device [EMAIL PROTECTED] ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
