Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. [Bug 667] New: missing dependency on libusb in bluez-utils
([EMAIL PROTECTED])
2. [Bug 574] timing issues / buffer parsing issues in gsmd
([EMAIL PROTECTED])
3. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
4. [Bug 100] Implement Cell Broadcast support
([EMAIL PROTECTED])
5. [Bug 100] Implement Cell Broadcast support
([EMAIL PROTECTED])
6. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
7. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
8. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=667
Summary: missing dependency on libusb in bluez-utils
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: bluez
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
bluez-utils fails to build
see
http://wiki.openmoko.org/index.php?title=Talk%3AMokoMakefile&diff=14463&oldid=14393
manual building of libusb resolves the problem
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=574
------- Additional Comments From [EMAIL PROTECTED] 2007-07-27 13:58 -------
Another thing I just noticed with regard to the gsmd timer:
[EMAIL PROTECTED]:~$ tail -f /tmp/gsm.log
Wed Feb 2 02:08:27 2000 <1> usock.c:69:usock_cmd_cb() entering(cmd=0x1a7e8,
gu=0x1a8d0)
Wed Feb 2 02:08:27 2000 <1> usock.c:53:usock_cmd_enqueue() enqueueing usock cmd
0x1a968 for user 0x1a8d0
Wed Feb 2 02:08:27 2000 <1> usock.c:940:gsmd_usock_user_cb() successfully sent
cmd 0x1a968 to user 0x1a8d0, freeing
Wed Feb 2 02:08:27 2000 <1> usock.c:96:usock_rcv_passthrough() submitting
cmd=0x1a7e8, gu=0x1a8d0
Wed Feb 2 02:08:27 2000 <1> atcmd.c:452:atcmd_submit() submitting command
`at+creg'
Wed Feb 2 02:08:27 2000 <1> atcmd.c:180:ml_parse() buf=`OK'(2)
Wed Feb 2 02:08:27 2000 <1> atcmd.c:338:ml_parse() Calling cmd->cb()
Wed Feb 2 02:08:57 2000 <1> gsmd.c:74:alive_tmr_cb() gsmd_alive timer expired
Wed Feb 2 02:08:57 2000 <3> gsmd.c:80:alive_tmr_cb() modem alive!
Wed Feb 2 02:10:32 2000 <1> usock.c:904:gsmd_usock_user_cb() EOF, this client
has just vanished
Wed Feb 2 02:12:03 2000 <1> atcmd.c:180:ml_parse() buf=`%CSQ: 26, 99, 3'(16)
Wed Feb 2 02:12:03 2000 <1> atcmd.c:248:ml_parse() extd reply `%CSQ: 26, 99,
3' to cmd `+creg', must be unsolicited
Wed Feb 2 02:12:03 2000 <1> vendor_ti.c:78:csq_parse() entering csq_parse
param=` 26, 99, 3'
Wed Feb 2 02:12:03 2000 <1> unsolicited.c:69:usock_evt_send() entering evt=6
Wed Feb 2 02:12:06 2000 <1> atcmd.c:180:ml_parse() buf=`%CPRI: 1,2'(10)
Wed Feb 2 02:12:06 2000 <1> atcmd.c:248:ml_parse() extd reply `%CPRI: 1,2' to
cmd `+creg', must be unsolicited
Wed Feb 2 02:12:06 2000 <1> unsolicited.c:69:usock_evt_send() entering evt=13
Wed Feb 2 02:12:32 2000 <1> atcmd.c:180:ml_parse() buf=`%CSQ: 23, 99, 2'(16)
Wed Feb 2 02:12:32 2000 <1> atcmd.c:248:ml_parse() extd reply `%CSQ: 23, 99,
2' to cmd `+creg', must be unsolicited
Wed Feb 2 02:12:32 2000 <1> vendor_ti.c:78:csq_parse() entering csq_parse
param=` 23, 99, 2'
Wed Feb 2 02:12:32 2000 <1> unsolicited.c:69:usock_evt_send() entering evt=6
Wed Feb 2 02:13:27 2000 <1> gsmd.c:119:alive_interval_tmr_cb() interval
expired, starting next alive inquiry
Wed Feb 2 02:13:27 2000 <1> atcmd.c:452:atcmd_submit() submitting command
`ATE0'
Wed Feb 2 02:13:27 2000 <1> atcmd.c:180:ml_parse() buf=`OK'(2)
Wed Feb 2 02:13:27 2000 <1> atcmd.c:338:ml_parse() Calling cmd->cb()
Wed Feb 2 02:13:27 2000 <1> usock.c:69:usock_cmd_cb() entering(cmd=0x1a7e8,
gu=0x1a8d0)
Wed Feb 2 02:13:27 2000 <1> usock.c:53:usock_cmd_enqueue() enqueueing usock cmd
0x1a9d8 for user 0x1a8d0
Wed Feb 2 02:13:57 2000 <1> gsmd.c:74:alive_tmr_cb() gsmd_alive timer expired
Wed Feb 2 02:13:57 2000 <8> gsmd.c:77:alive_tmr_cb() modem dead!
gsmd - (C) 2006-2007 by Harald Welte <[EMAIL PROTECTED]>
This program is FREE SOFTWARE under the terms of GNU GPL
I can't really make much sense of it, but it seems to me that the alive timer
steals the first OK from the usock_cb and the next time the alive timer sends
ATE0 the OK is not passed back to the alive timer.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666
------- Additional Comments From [EMAIL PROTECTED] 2007-07-27 15:58 -------
To keep IRC, the lists, and bugzilla in sync many other people have reported
this problem. A gentleman on IRC said that the card AT&T uses is
http://www.oberthurcs.com/getpage.aspx?id=65#application (I guess by looking at
the numbers on it). Others have confirmed that the new "3g fireball" cards work
in older 2G phones and that AT&T does testing to unsure the sim cards have both
USIM and SIM applications on them. But, out of the 5 or so people on the IRC
channel who got their phone on had the new AT&T cards, none have been able to
get them to work.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=100
------- Additional Comments From [EMAIL PROTECTED] 2007-07-27 21:44 -------
Created an attachment (id=229)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=229&action=view)
Multiline unsolicited responses parsing.
+CMT, +CBM and +CDS responses two lines long in PDU mode and the parser has
problem with them. As it was mentioned earlier there's no way for the parser
to know if a new line is part of the most recent command response or
unsolicited response, or a completely new unsolicited response, without looking
at the contents of the first line. My idea is that the parser for the
particular response decides if the response is too short, and returns -EAGAIN
in which case the AT parser will append the following line to the response and
resubmit it to the response parser. The disadvantage is that the generic
parser gets one more special case to remember about, but it works quite well,
hopefully there are no more cases where we will need to modify the parser. (We
may need to use a separate multiline buffer (like the current mlbuf variable)
to account for situations when a multiline unsolicited response comes in the
middle of receiving a different response, which is also possible. Also, mlbuf
should probably be moved into the parser state struct instead of being a
global).
This patch also moves initialisation of SMS options to after we are registered
to the network, so that we don't get errors from the modem. Perhaps we want to
have a dynamic list of callbacks to call on succesfull registration.
Among other changes also prevents setting dev_state.on if the radio powering-on
fails. Depends on attachment #226.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=100
------- Additional Comments From [EMAIL PROTECTED] 2007-07-27 21:48 -------
Created an attachment (id=230)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=230&action=view)
Cell Broadcast message decoding and presentation in libgsmd-tool.
This time Cell Broadcast is tested to work, I should have made tests earlier.
Now I'm correctly getting a CB message with the human readable name of the city
and district when I'm connecting. In the previous patches the CB PDU was not
being decoded at all.
Depends on attachment #229.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666
------- Additional Comments From [EMAIL PROTECTED] 2007-07-27 23:48 -------
With my particular sim, it seems to randomly read it (maybe?) sometimes, and
other times not..
The 1st time I booted the phone, gsmd auto-started, and in the top toolbar,
it *appears* I had great reception. However, any AT+CFUN, or AT+CIMI command
spits out CME ERROR 13..
The 2nd time I booted the phone, gsmd did not auto start, and any
combination of starting it and using libgsmdtool -t atcmd, or straight cu,
produces the CME ERROR 10.
So not sure whats going on here, if any logs can be attached that would be
useful, let us know :)
Cheers
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=129
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=276
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=344
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=347
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=352
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=511
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=571
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=605
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666
------- Additional Comments From [EMAIL PROTECTED] 2007-07-28 09:41 -------
I can confirm that my device is in fact working perfectly fine. I tested it out
this evening with a t-mobile sim card (2g), and was able to make a phone call
ok. With audio as well.
So its definitely an issue with the other cingular/att 3g sim card (and/or
network?).
cheers,
-scott
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
