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. Re: Openmoko Bug #2216: Call = there is no sound
(Openmoko Public Trac)
2. Re: Openmoko Bug #2217: Noise screen of death: Freerunner
looses SDIO connection (Openmoko Public Trac)
--- Begin Message ---
#2216: Call = there is no sound
----------------------+-----------------------------------------------------
Reporter: octavsly | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.12
Component: unknown | Version: GTA02v6
Severity: major | Keywords: call, mute, no sound, no audio
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
----------------------+-----------------------------------------------------
Comment(by mzanetti):
For me, this happened after some hours of uptime. Sometimes already after
10 mins of uptime. The very first phonecall after rebooting was working
most of the times.
Anyways, I have been able to work around this issue by using Korbinian's
workaround for the openmoocow-not-mooing issue. It consists basically of
switching speech-dispatcher from alsa to oss. After switching, all 2008.12
sound issues are gone - at least on my FR.
See this URL for a detailed description:
http://lists.openmoko.org/nabble.html#nabble-td2175057
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2216#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2217: Noise screen of death: Freerunner looses SDIO connection
-----------------------------+----------------------------------------------
Reporter: xbaldauf | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: major | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible:
-----------------------------+----------------------------------------------
Comment(by andy):
Actually thinking about this there is probably some middle ground between
the two choices. I added a patch which allows the inbetween settings to
be selected as well
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=7f859d161097631a3c76ed1dbb1cfcb08ebe9759
If someone with a "bad Glamo" can try the other settings, it may be
possible to still get some improvement over the 2.6.24 settings without
triggering this issue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2217#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
