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 #2020: USB connection messes with
suspend/resume state machine (Openmoko Public Trac)
2. Re: Openmoko Bug #2020: USB connection messes with
suspend/resume state machine (Openmoko Public Trac)
3. Openmoko Bug #2028: gpsd does not install libgpsmm.h and
gpsd_config.h in staging dir (Openmoko Public Trac)
4. Re: Openmoko Bug #1562: 12 hour time format does not work
(Openmoko Public Trac)
5. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
6. Openmoko Bug #2029: Class 0 SMS wrongly decoded (no UTF-8?)
(Openmoko Public Trac)
7. Re: Openmoko Bug #2026: [qtopia-phone-x11-addressbook]
Overwrites home phone num with mobile phone num for VCF from
Sharp GX17 Mobile (Openmoko Public Trac)
8. Re: Openmoko Bug #2029: Class 0 SMS wrongly decoded (no
UTF-8?) (Openmoko Public Trac)
--- Begin Message ---
#2020: USB connection messes with suspend/resume state machine
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by vnevoa):
NOTE: whenever I say "let FR go to sleep", please make sure it is really
sleeping!! (touch screen - if it glows, it wasn't really sleeping) :)
Otherwise, the test isn't valid.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2020#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2020: USB connection messes with suspend/resume state machine
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by vnevoa):
I'm thinking this has little or nothing to do with USB.
From the point of view of usage, USB plug-in and plug-out looks like just
another APM event, like for example clicking the power button.
New use-case info: (after opkg update + upgrade today = no pkg changes)
1 - let FR go to sleep (without USB cable);
2 - click power button -> FR wakes up, glows screen;
3 - wait for timeout -> FR dims screen but does not go to sleep (icons
still showing if strong light used);
4 - touch screen -> FR glows screen;
5 - wait for timeout -> FR dims screen and goes to sleep.
This is consistent with the first description, but without the USB thing.
Another interesting fact:
1 - let FR go to sleep (without USB cable);
2 - click power button -> FR wakes up, glows screen;
3 - touch screen once -> nothing happens! (illume does not receive the
click);
4 - touch the screen again -> illume receives the click and acts normally
(launch app, slide icons, etc.);
However, after step 3 (touching the screen and nothing seems to happen)
the timeout starts to count down, because if we don't do anything after
that it effectively goes to sleep.
My conclusion: when FR wakes up, there is "something X11" waiting for a
click to initiate the power management countdown. If there is no screen
tapping, there is no countdown to sleep (although there is countdown to
screen dimming).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2020#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2028: gpsd does not install libgpsmm.h and gpsd_config.h in staging dir
---------------------+------------------------------------------------------
Reporter: Niko! | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible:
Blocking: |
---------------------+------------------------------------------------------
gpsd provides libgpsmm.h, a c++ wrapper for libgps, but this and
gpsd_config.h (required by libgpsmm.h) are not installed in the staging
area of build tree, so c++ applications using libgps fail to compile.
I copied them from the work directory to the staging area and it works
fine.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2028>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1562: 12 hour time format does not work
---------------------------+------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: reopened
Priority: normal | Milestone: Om2008.10
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Changes (by regina_kim):
* milestone: Om2008.9 => Om2008.10
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1562#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by werner):
Finding a replacement jack should be easy, but ...
Unfortunately, removing the jack is extremely hard: you have to melt the
solder on all six pads, which are large, far from each other, surrounded
by small components, and one even attaches to the ground plane, which
acts as a large heat sink.
So without special equipment and plenty of experience using it, I'd say
that the most likely outcome of trying to remove the jack would be that
you'd end up damaging some of its surrounding components, without moving
the jack itself a tenth of a millimeter.
The most likely outcome of trying to unsolder the jack is that you'll
damage or remove some of its surrounding components and that you'll
apply too much heat to its pads, damaging the PCB.
You could improve the odds by cutting the jack into pieces, e.g., with a
dremel, and then unsoldering the remaining metal parts. Again, one slip
and some other components get shredded. This kind of mechanical removal
also has the risk that you apply too much force on a pad and lift the
pad off the PCB, breaking the connection and possibly also damaging
layers inside the board.
These are not just hypothetical risks. I've seen this happen numerous
times on circuits that were much easier to work on.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:29>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
---------------------+------------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
---------------------+------------------------------------------------------
Class 0 SMS messages (the kind that show up immediately on screen and
don't get saved) are not decoded right in my GTA02.
When I finish a GSM call, my operator sends me a class 0 SMS with the
remaining amount in my pre-paid account. This used to work ok until one of
those UTF-8 patches some time ago (sorry, don't know when it happened).
Now the message shows up like a string of numbers instead of text.
For example, my FR just showed me this:
00340035002E00370033002000
Which I presume means this:
45.73 €
My SW is a OM2008.8-update jffs2 image that has been upgraded everyday via
opkg.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2029>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2026: [qtopia-phone-x11-addressbook] Overwrites home phone num with mobile
phone
num for VCF from Sharp GX17 Mobile
------------------------+---------------------------------------------------
Reporter: csamuel | Owner: zecke
Type: defect | Status: new
Priority: normal | Milestone:
Component: Qtopia | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* owner: julian_chu => zecke
* component: Distro => Qtopia
Comment:
Please read http://wiki.openmoko.org/wiki/Bug_Filing_Policy. Please do not
set a Component until you know what you do.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2026#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
------------------------+---------------------------------------------------
Reporter: vnevoa | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by vnevoa):
Actually, it looks more like UTF-16.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2029#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
