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 #1580: Implement qtopia keyboard for ASU
(Openmoko Public Trac)
2. Re: Openmoko Bug #1580: Implement qtopia keyboard for ASU
(Openmoko Public Trac)
3. Re: Openmoko Bug #1252: usb0 no longer comes up if booting
with usb plugged in (Openmoko Public Trac)
4. Re: Openmoko Bug #1252: usb0 no longer comes up if booting
with usb plugged in (Openmoko Public Trac)
5. Re: Openmoko Bug #1252: usb0 no longer comes up if booting
with usb plugged in (Openmoko Public Trac)
6. Re: Openmoko Bug #1252: usb0 no longer comes up if booting
with usb plugged in (Openmoko Public Trac)
7. Openmoko Bug #1690: Missed call cannot be marked as viewed,
must be deleted to stop notification (Openmoko Public Trac)
8. Openmoko Bug #1691: [Qtopia] qpe crash happened after flash
the new image (Openmoko Public Trac)
--- Begin Message ---
#1580: Implement qtopia keyboard for ASU
-------------------------+--------------------------------------------------
Reporter: will | Owner: raster
Type: enhancement | Status: in_testing
Priority: low | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by will):
* status: new => in_testing
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1580#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1580: Implement qtopia keyboard for ASU
-------------------------+--------------------------------------------------
Reporter: will | Owner: raster
Type: enhancement | Status: in_testing
Priority: low | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: must have | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by will):
* status: new => in_testing
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1580#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1252: usb0 no longer comes up if booting with usb plugged in
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------------------+------------------------------------------
Changes (by mickeyl):
* status: closed => reopened
* resolution: fixed =>
Comment:
With recent andy kernels I cansee this behaviour again. dmesg shows:
usb 3-1: new low speed USB device using uhci_hcd and address 2
usb 3-1: new low speed USB device using uhci_hcd and address 3
usb 3-1: new low speed USB device using uhci_hcd and address 4
usb 3-1: device not accepting address 4, error -71
usb 3-1: new low speed USB device using uhci_hcd and address 5
usb 3-1: device not accepting address 5, error -71
usb 3-1: new low speed USB device using uhci_hcd and address 6
usb 3-1: new low speed USB device using uhci_hcd and address 7
usb 3-1: new low speed USB device using uhci_hcd and address 8
usb 3-1: device not accepting address 8, error -71
usb 3-1: new low speed USB device using uhci_hcd and address 9
usb 3-1: device not accepting address 9, error -71
usb 3-1: new full speed USB device using uhci_hcd and address 10
usb 3-1: new full speed USB device using uhci_hcd and address 11
usb 3-1: new full speed USB device using uhci_hcd and address 12
usb 3-1: device not accepting address 12, error -71
usb 3-1: new full speed USB device using uhci_hcd and address 13
usb 3-1: device not accepting address 13, error -71
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1252#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1252: usb0 no longer comes up if booting with usb plugged in
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------------------+------------------------------------------
Comment(by andy):
This is different from your original report: it was a timeout then and
this is something else, for example your host is misunderstanding the
device as "low speed" USB half the time. Can the device be in host mode,
is the cable definitely good?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1252#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1252: usb0 no longer comes up if booting with usb plugged in
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------------------+------------------------------------------
Comment(by mickeyl):
* cables ok (tried multiple cables and multiple ports on multiple
machines)
* no host mode
* needs one or more reboots to work again
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1252#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1252: usb0 no longer comes up if booting with usb plugged in
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: reopened
Priority: high | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------------------+------------------------------------------
Comment(by andy):
I use the USB port all day to send new kernel images to SD Card, I would
notice this immediately if it was happening here. "one or more reboots"
does not make it sound like a software issue. Can you reproduce it on a
second physical device with the same software patchlevel?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1252#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1690: Missed call cannot be marked as viewed, must be deleted to stop
notification
-----------------------------+----------------------------------------------
Reporter: brianwc | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone: OM-2007.2
Component: System Software | Version: GTA02v6
Severity: normal | Keywords:
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
From http://lists.openmoko.org/pipermail/community/2008-July/024191.html
On Tuesday 29 July 2008, reaper527 wrote:
> is there any way to mark a missed call as seen?
>
> for example on my old phone, if i got a missed call, i would get
> notification on the main screen, and then hitting a button would take me
to
> the list of missed calls, and the phone would acknowledge i looked at
the
> calls, and it would stop counting those towards totals for the next
missed
> call.
>
> with the freerunner, if i get a missed call, it goes into the call log
as
> missed, and then keeps adding on to that count. if i miss 2 calls, click
> the "you missed 2 calls" thing, and then later miss 1 call, it will say
i
> missed 3 calls at that point instead of saying i missed 1. the only work
> around i have been able to find is to manually delete all my missed
calls,
> which isn't ideal.
>
> anything obvious i've overlooked?
[Al Johnson replied]
I've seen the same thing, and deleting the missed calls is the only thing
that's worked for me. I should have checked for bug reports I suppose, or
better yet dug out the source and patched it.
I also get this behavior. OM2007.2 with recent rootfs and kernel.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1690>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1691: [Qtopia] qpe crash happened after flash the new image
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: ASU
Component: Qtopia | Version:
Severity: blocker | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
kernel:20080723-asu.stable-uImage.bin
root file system:20080730-asu.stable-rootfs.jffs2
Summary:
qpe crash happened after flash the new image
Step + current result:
1) flash the new image
2) launch the device
3) the qpe crash error message pop up
4) error message :
-Application Error-
The qpe process Vanished. This is bad. This is not meant to happen and is
likely a sign of a bug in Qtopia. Please try to reproduce it and report
the issue to http://docs.openmoko.org.
To be able to use your phone as a phone again you will have to restart
Qtopia.
[(F1)Restart] [(F2)Exit]
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1691>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
