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 1193] New: Severe performance problems with Pulseaudio
([EMAIL PROTECTED])
4. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
5. [Bug 1194] New: Touchscreen Jitter
([EMAIL PROTECTED])
6. [Bug 956] GTA02 charging with 1000mA using wall-outlet
charger ([EMAIL PROTECTED])
7. [Bug 956] GTA02 charging with 1000mA using wall-outlet
charger ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1192
------- Additional Comments From [EMAIL PROTECTED] 2008-01-22 15:39 -------
Created an attachment (id=508)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=508&action=view)
retrieve imsi when init gsm
------- 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
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2008-01-22 15:39 -------
Fixed it
------- 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=1193
Summary: Severe performance problems with Pulseaudio
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Host Software
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Pulseaudio's behavior on my Neo has annoyed me for a while, and now I got around
to poking it a bit, with not much results but some. The visible issue is that
eg. when playing music with openmoko-mediaplayer, the pulseaudio server hogs up
25-30% of the CPU, which is enough to cause serious skipping of the audio (at
least my sample ogg tracks from Harvey Danger,
http://www.harveydanger.com/downloads/ ). This with no other clients playing
anything, of course, so no mixing required, just pushing bits from buffer to
sound driver.
ogg123, not going through pulseaudio, plays the same tracks quite well at around
80% CPU. Pulseaudio behavior is the same whether I use native ALSA or OSS sinks.
I straced pulseaudio a bit while playing music. Obviously, the strace emphasized
the skipping severely and quite possibly isn't useful for diagnosis due to
altering a lot of the timing, but some stuff was still going through.
Anyway, the thing that caught my eye was that between each write to the audio
device there were 16 pairs of alternating calls:
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
I presumed this to be threading-related, but apparently pulseaudio doesn't do
threads after all. Then I presumed it to be rabid syncing with the shared memory
area the client uses to communicate with it, but it seems to persist with
--disable-shm (as does the CPU hogging, whether it's related or not). Now I just
presume pulseaudio is on crack.
One should hopefully be able to have a decent mediaplayer experience without
waiting for GTA-02 in order to have more CPU to feed to the relentless
pulseaudio. Hopefully it's easily fixable to consume sane amounts of CPU
regardless.)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1165
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1177
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=1194
Summary: Touchscreen Jitter
Product: OpenMoko
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
There's still a lot of jitter coming from the touchscreen. Apparantly the tslib
dejitter plugin is uneffective -- perhaps the data from the kernel are too bad
to make the tslib plugins do their job. This needs an optimization session as it
ruins the user interface when scrolling through lists.
------- 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=956
------- Additional Comments From [EMAIL PROTECTED] 2008-01-23 10:38 -------
Is there any update on this bug? Will the GTA02 follow the OMTP spec for
charging that may have been available at
<http://www.omtp.org/docs/OMTP_Local_Data_Connectivity_v1_0.pdf> but I sadly
have not come across?
The Battery Charging Specification of the USB Implementers Forum
<http://www.usb.org/developers/devclass_docs/batt_charging_1_0.zip>
does not mention any 48k resistor as in the bug description. Instead, it says
that dedicated chargers must identify themselves by shorting D+ and D- with at
most 200 ohms resistance. Unfortunately for me, this means that the only USB
port on the GTA02 can't be used for charging and talking to a USB device at the
same time. I hope you can implement some user-space hook that makes the GTA02
believe that an attached USB device (not host) also is a dedicated charger.
------- 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=956
------- Additional Comments From [EMAIL PROTECTED] 2008-01-23 11:05 -------
The "OMTP Local Data Connectivity" specification appears to be available here:
<http://www.omtp.org/recommendations_papers/publications_local_connect.html>,
<http://www.omtp.org/pdf/OMTP_Local_Data_Connectivity_v1_0.pdf>. It refers to
the Battery Charging Specification of the USB Implementers Forum
<http://www.usb.org/developers/devclass_docs/batt_charging_1_0.zip> that I
mentioned in my previous comment.
------- 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
