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 #1654: [illume] Manually showing and hiding
the keyboard. (Openmoko Public Trac)
2. Re: Openmoko Bug #1665: use dnsmasque for local dns caching
(Openmoko Public Trac)
3. Re: Openmoko Bug #1567: cannot re-flash the debug board
(Openmoko Public Trac)
4. Re: Openmoko Bug #1542: gps does not get fix
(Openmoko Public Trac)
5. Re: Openmoko Bug #1980: [Location] the tag list is jumping
too serious when you scroll it (Openmoko Public Trac)
6. Re: Openmoko Bug #1976: Redial last called number
(Openmoko Public Trac)
7. Re: Openmoko Bug #1728: SMS parser bug? (Openmoko Public Trac)
8. Re: Openmoko Bug #1728: SMS parser bug? (Openmoko Public Trac)
--- Begin Message ---
#1654: [illume] Manually showing and hiding the keyboard.
---------------------------+------------------------------------------------
Reporter: kenrestivo | Owner: openmoko-devel
Type: defect | Status: closed
Priority: highest | Milestone:
Component: unknown | Version: GTA02v5
Severity: major | Resolution: fixed
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Changes (by zecke):
* status: reopened => closed
* resolution: => fixed
Comment:
And AFAIK people can install packages to get the QWERTZ button and toggle
visibility, so the initial complain is resolved?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1654#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1665: use dnsmasque for local dns caching
----------------------------+-----------------------------------------------
Reporter: candrews | Owner: openmoko-devel
Type: enhancement | Status: assigned
Priority: normal | Milestone:
Component: Distro | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
----------------------------+-----------------------------------------------
Changes (by zecke):
* component: Network Manager => Distro
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1665#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1567: cannot re-flash the debug board
-------------------------+--------------------------------------------------
Reporter: asappia | Owner: hardware
Type: defect | Status: closed
Priority: highest | Milestone:
Component: hardware | Version:
Severity: normal | Resolution: worksforme
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------+--------------------------------------------------
Changes (by zecke):
* status: new => closed
* resolution: => worksforme
Comment:
Closing this as works for some as werner didn't get a response and one can
easily edit the openocd.cfg.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1567#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1542: gps does not get fix
-----------------------------------------+----------------------------------
Reporter: emdete | Owner: hardware
Type: defect | Status: new
Priority: high | Milestone:
Component: hardware | Version:
Severity: blocker | Resolution:
Keywords: gps antenna fix internal | Blockedby:
Reproducible: | Blocking:
-----------------------------------------+----------------------------------
Comment(by zecke):
Can we resolve this?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1542#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1980: [Location] the tag list is jumping too serious when you scroll it
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: jeremy
Type: defect | Status: new
Priority: normal | Milestone: Om2008.9
Component: Locations | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
---------------------------+------------------------------------------------
Comment(by will):
If this has to do with scrolling, I'm not sure if this is even a Locations
bug.
I'm not sure what 'bounce' means. Bounce when scrolling to the bottom of
the screen?
Please show me tomorrow.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1980#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1976: Redial last called number
----------------------------+-----------------------------------------------
Reporter: Treviño | Owner: zecke
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: normal | Resolution:
Keywords: HasPatch | Blockedby:
Reproducible: | Blocking:
----------------------------+-----------------------------------------------
Comment(by Treviño):
Replying to [comment:1 zecke]:
> @Implementation: It is fine, maybe the valuespace is not populated from
the callhistory
No, it isn't... What do you think about implementing the "search-last-
dialed-number" feature? Do you think it would be much slower?
> @Approach:
> - Having a feature that is not easy to discover (no button for it),
that can be accidently triggered (someone pressed call with an empty
number accidently and then a complete number gets dialer) are violations
of common usability standards.
Well, that's not completely true... Yes, there's no button for it, but
redialing pressing the "green button" is a common phone feature. However
With my patch to re-dial the "LastDialedCall" you need to press the call
button twice, not once!
In fact, if the text string is empty and you press the call button, that
text area just populated with the latest called string. If you want to
dial that number, instead, you've to press the call button another time. I
think that this is a reasonable approach.
> @Proposal: Add a redial action to the menu of the dialer. This will take
two clicks (open menu, click on redial) and we can consider exchanging the
SMS button with the redial action (easy once the code for the action is
there) in the future. Would you be willing to give that a try?
I could do it, but imho adding a button is redundant while using the menu
action is not so intuitive. I'd exchange the SMS button with a "clear
number", instead...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1976#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1728: SMS parser bug?
-----------------------+----------------------------------------------------
Reporter: odlg | Owner: tick
Type: defect | Status: closed
Priority: high | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: major | Resolution: fixed
Keywords: | Blockedby:
Reproducible: | Blocking:
-----------------------+----------------------------------------------------
Comment(by Treviño):
Yes it is... But that PDU is not the PDU of the badly-decoded SMS I've
screen-shotted above. Unfortunately I can't find that PDU!
Any way to recover it? Thanks!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1728#comment:31>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1728: SMS parser bug?
-----------------------+----------------------------------------------------
Reporter: odlg | Owner: tick
Type: defect | Status: closed
Priority: high | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: major | Resolution: fixed
Keywords: | Blockedby:
Reproducible: | Blocking:
-----------------------+----------------------------------------------------
Comment(by wjbaird):
Yup - I just started getting garbled messages from google again last
night. It doesn't seem like all of them are garbled - I last upgraded
(via OM2008.8 testing) yesterday, but I got some google SMSs yesterday and
today that were fine, but the last two that I got today were garbled.
I was only able to find the PDU for one of them:
0791446742949940040BD0C7F7FBCC2E0300008090013102126964D2723BED2697E53A50D10AA296C36D50B35CA6A7DD671000742D9341D3321C14830CDE06B54032DD0C066F83D26ED0531E1EB3CBA066B94C4FBBCF7076785C06DD6A379B0D067A816EB59BCD0603A1AE
However, when I tried to decode this at http://twit88.com/home/utility
/sms-pdu-encode-decode I see the same thing I see on the OM - the first
half of the message is fine, and the last half garbled:
Reminder: EV Team Meeting @ Wed Sep
1Δ¥oùj$ΦS€¥¥oùJvùzΛåßf.ùj,.&Ov>ùgÅß.ù:+;33¥¥z$:+;33¥¥B:é
I assume this means that the SMS itself was garbled by google? Or could
something at a lower level be scrambling the PDU itself?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1728#comment:32>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
