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 1192] unknown reason cause TI GSM modem always return
"+CME ERROR: 512" ([EMAIL PROTECTED])
2. [Bug 1192] unknown reason cause TI GSM modem always return
"+CME ERROR: 512" ([EMAIL PROTECTED])
3. [Bug 1198] Audio (via headphone jack) doesn't couple well to
some line-inputs ([EMAIL PROTECTED])
4. [Bug 1192] unknown reason cause TI GSM modem always return
"+CME ERROR: 512" ([EMAIL PROTECTED])
5. [Bug 1192] unknown reason cause TI GSM modem always return
"+CME ERROR: 512" ([EMAIL PROTECTED])
6. [Bug 847] Shutdown if battery level goes too low
([EMAIL PROTECTED])
7. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1192
------- Additional Comments From [EMAIL PROTECTED] 2008-01-25 18:08 -------
Hi,
probably not very helpful, but I remember my Calypso modem on GTA01 sometimes
getting into a loop where it would only give a +CME error on anything I do until
I reset it. It was not reproducible - when it happened for the first time, I
tried to reproduce it and couldn't, but another day ran into it again. It was a
long time ago.
I don't know what the error code was because I was using the AT+CMEE=2 mode
(textual errors) so it was something like:
+CME: Operation in progress
or something similar, but it was a non-standard error (i.e. it was not in the
GSM specs when I checked). I only hit it when manually using the serial port
with "cu".
The modem was printing this error on every *character* I typed, not every
command (unless pasting commands). So if I typed AT+ABC slowly, I would get:
A
+CME: Operation in progress
T
+CME: Operation in progress
+
+CME: Operation in progress
A
+CME: Operation in progress
B
+CME: Operation in progress
C
+CME: Operation in progress
------- 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=1192
------- Additional Comments From [EMAIL PROTECTED] 2008-01-25 18:08 -------
So I think it's not a gsmd bug.
------- 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=1198
------- Additional Comments From [EMAIL PROTECTED] 2008-01-25 18:58 -------
UPDATE.
It works PERFECTLY through a ground-loop isolator, this one from Radio Shack in
particular:
http://www.radioshack.com/product/index.jsp?productId=2062214
Part No. 270-054, US$16.99.
This suggests to me that there's probably a DC offset originating somewhere
(Car->Neo or Neo->Car) that the receiving device doesn't react well to. I don't
have a 'scope so I can't really verify which direction it comes from.
But in either case, it appears the audio output stage of the Neo is non-standard
to some extent, and I'm leaving this bug open for now.
------- 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=1192
------- Additional Comments From [EMAIL PROTECTED] 2008-01-25 20:03 -------
Yes, not gsmd problem, the problem definitely is coming from GSM firmware. If we
remove the "AT+COLP=1" in gsmd_initsettings2(), then it won't happen anymore.
------- 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=1192
------- Additional Comments From [EMAIL PROTECTED] 2008-01-25 20:32 -------
Is this really the latest firmware from TI? I have the very uncomfortable
feeling that some of our problems are not due to kernel serial port or gsmd but
actually due to the firmware. Can we double check that with TI?
------- 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=847
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2008-01-26 01:01 -------
I agree. Neod is the best short-term solution for that. Assinging to me.
------- 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=934
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=935
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1012
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1081
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1107
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1127
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1133
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1136
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1158
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1161
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1162
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
