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 #1719: sd card not recognized
(Openmoko Public Trac)
2. Re: Openmoko Bug #1719: sd card not recognized
(Openmoko Public Trac)
3. Re: Openmoko Bug #1656: Bad A2DP performance
(Openmoko Public Trac)
4. Re: Openmoko Bug #1751: distro-feed-configs package breaks
2007.02 feeds (Openmoko Public Trac)
5. Re: Openmoko Bug #1656: Bad A2DP performance
(Openmoko Public Trac)
6. Re: Openmoko Bug #1750: Range-based automatic network
configuration (Openmoko Public Trac)
7. Re: Openmoko Bug #1743: Intenso SDHC 4GB gives glamo errors
(Openmoko Public Trac)
8. Re: Openmoko Bug #1743: Intenso SDHC 4GB gives glamo errors
(Openmoko Public Trac)
9. Re: Openmoko Bug #1656: Bad A2DP performance
(Openmoko Public Trac)
--- Begin Message ---
#1719: sd card not recognized
----------------------+-----------------------------------------------------
Reporter: feydreva | Owner: hardware
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: hardware | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Comment(by andy):
What you pasted from dmesg looks exactly like your card takes too long to
respond to the first bulk packet, something that was seen before in #1743.
But, your other syslog traffic is funny. What version is this kernel?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1719#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1719: sd card not recognized
----------------------+-----------------------------------------------------
Reporter: feydreva | Owner: hardware
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: hardware | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Comment(by andy):
What you pasted from dmesg looks exactly like your card takes too long to
respond to the first bulk packet, something that was seen before in #1743.
But, your other syslog traffic is funny. What version is this kernel?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1719#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1656: Bad A2DP performance
---------------------+------------------------------------------------------
Reporter: Mercury | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Changes (by montgoss):
* cc: montgoss (added)
* version: unspecified =>
Comment:
I get slightly better performance than the OP, but still have issues. I
noticed distance between the freerunner and headset has a large impact on
the number of glitches while playing. Also, sample rate makes a big
difference.
I ran some tests with the headset about 2.5 feet from my Freerunner. A
song played at the lowered 16 KHz has just a few glitches and produces the
following output:
Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Stereo
6746 frames decoded (0:02:56.2), +0.6 dB peak amplitude, 36 clipped
samples
If I play the same song at the same distance, but at the original 44.1
KHz, it's unbearably glitchy. I get:
Playing WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
6746 frames decoded (0:02:56.2), +0.6 dB peak amplitude, 187 clipped
samples
I notice the worse it sounds, the higher the "clipped samples" number is.
Are those clipped samples the glitches I'm hearing? Or is that clipping
something else?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1656#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1751: distro-feed-configs package breaks 2007.02 feeds
----------------------+-----------------------------------------------------
Reporter: olberger | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone: OM-2007.2
Component: Assassin | Version:
Severity: major | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Changes (by graeme):
* status: new => closed
* resolution: => fixed
* component: unknown => Assassin
Comment:
This should be fixed in tonights build.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1751#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1656: Bad A2DP performance
---------------------+------------------------------------------------------
Reporter: Mercury | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by andy):
Clipped means that it got decoded / amplified / filtered beyond + or -
32767. It will cause a little "tick" sound usually. So this is enough to
make the problem... try using switches in your decoder to "amplify" to
-1dB or somesuch and see if it helps.
But the datarate for your raw data in the second case is pretty high,
1.4Mbits/sec sustained. I don't know much about Bluetooth to say if it
makes trouble, EDR BT seems to provide 3Mbits/sec raw bandwidth so it
isn't crazy if that is what we provide.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1656#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1750: Range-based automatic network configuration
-------------------------+--------------------------------------------------
Reporter: Mercury | Owner: openmoko-devel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: minor | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by Mercury):
* severity: normal => minor
Comment:
Perhaps a GPS based option as well (i.e. 'Never connect to GPRS when
you're at home or at the office even if wifi is unavailable.' Or 'Only
connect to access point SSID when at location LATLONGRADIUS)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1750#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1743: Intenso SDHC 4GB gives glamo errors
---------------------+------------------------------------------------------
Reporter: beni | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by rhk):
So will this be/is this included in the kernel or if one faces this, he
needs to fix it on his device?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1743#comment:11>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1743: Intenso SDHC 4GB gives glamo errors
---------------------+------------------------------------------------------
Reporter: beni | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution: fixed
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by beni):
It is currently not included and must be fixed manually by providing
kernel start parameters.
Please may one of the devs comment on this if it will be implemented in
the kernel.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1743#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1656: Bad A2DP performance
---------------------+------------------------------------------------------
Reporter: Mercury | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by montgoss):
Following the thinking that it's a signal strength issue (since distance
affects performance), is there a way to boost the signal? That would
definitively confirm or disprove my theory.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1656#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
