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 #1734: [WiFi] wifi show up "unknow"
(Openmoko Public Trac)
2. Re: Openmoko Bug #1739: [Exposure] Sometimes Profile will
show up "unknow" message (Openmoko Public Trac)
3. Re: Openmoko Bug #1685: [Suspend/Resume time] The device
insist to go suspend even after touch the screen to wake it up
from blank time (Openmoko Public Trac)
4. Re: Openmoko Bug #1685: [Suspend/Resume time] The device
insist to go suspend even after touch the screen to wake it up
from blank time (Openmoko Public Trac)
5. Re: Openmoko Bug #1533: The keypad shows brackets number in
dialer screen and creat new message (Openmoko Public Trac)
6. Re: Openmoko Bug #1422: Device doesn?t wake up from blank
time when incoming a call and SMS (Openmoko Public Trac)
7. Openmoko Bug #1751: distro-feed-configs package breaks
2007.02 feeds (Openmoko Public Trac)
8. Re: Openmoko Bug #1422: Device doesn?t wake up from blank
time when incoming a call and SMS (Openmoko Public Trac)
--- Begin Message ---
#1734: [WiFi] wifi show up "unknow"
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: accepted
Priority: high | Milestone: ASU
Component: Exposure | Version:
Severity: blocker | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by marek):
* status: new => accepted
* component: Network Manager => Exposure
Comment:
Please check again, some things were fixed in the recent version. If it
does not work provide a distinct path to reproduce the problem.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1734#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1739: [Exposure] Sometimes Profile will show up "unknow" message
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: accepted
Priority: normal | Milestone: ASU
Component: Exposure | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by marek):
* owner: Marek => marek
* status: new => accepted
Comment:
Only device #68 is affected ? You can show me later - we start the
application with debug options enable to trace it down. I can't reproduce
it here.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1739#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1685: [Suspend/Resume time] The device insist to go suspend even after touch
the
screen to wake it up from blank time
-------------------------+--------------------------------------------------
Reporter: wendy_hung | Owner: raster
Type: enhancement | Status: assigned
Priority: low | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Changes (by wendy_hung):
* cc: [EMAIL PROTECTED] (added)
* status: in_testing => assigned
Comment:
Tested with the image below:
kernel:20080723-asu.stable-uImage.bin
root file system:20080806-asu.stable-rootfs.jffs2
It's just only a little bit different than before, for us that still looks
the same.
Sorry Raster, we have to fix it. Please discuss on the devel list how to
solve this issue.
Thank you!
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1685#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1685: [Suspend/Resume time] The device insist to go suspend even after touch
the
screen to wake it up from blank time
-------------------------+--------------------------------------------------
Reporter: wendy_hung | Owner: raster
Type: enhancement | Status: assigned
Priority: low | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Comment(by raster):
not going to be able to do anything between now and august 8 about this
beyond move ALL screen blanking to client-side. also need to add signals
to ompower to indicate coming out of suspend and why.
i think you don't have the same thing thats in asu.dev - holger was
working on moving to asu.stable just a few hours ago, so you're probably
not seeing anything different. you will know it's different as on actual
suspend the screen doesnt come back with backlight just before suspend and
a small grey cursor top-left of the screen (this is no hidden).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1685#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1533: The keypad shows brackets number in dialer screen and creat new message
-----------------------------+----------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: closed
Priority: highest | Milestone: ASU
Component: System Software | Version: GTA02v5
Severity: blocker | Resolution: fixed
Keywords: keypad | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Changes (by zecke):
* status: reopened => closed
* resolution: => fixed
Comment:
Your installed Xglamo version does _not_ contain the fix for the bracket
handling. I don't know why this is the case but if you upgrade it it
should work for you as well. Closing the bug due this again. Feel free to
reopen if the upgrade doesn't fix the bug.
Also I'm interested how you ended up with Xfbdev running and Xglamo not
being installed? Which image did you build?
Your glamo version:
commit d1ab8c0ec48821ef866e927c52b47587a0affc56
Author: Holger Hans Peter Freyther <[EMAIL PROTECTED]>
Date: Wed Jun 25 10:41:29 2008 +0200
[keyboard] Use the proper source for the high keyboard. fix bugs
I saved the input for the high keycodes to high_keys but to
generate
the keycode I went back to use b[1] and b[2] and this happened to
work
most of the time. Fix the bug and use high_keys.
You want to have at least:
commit aa7488dd64a716e7c3efae672bb74130205b4eb4
Author: Holger Hans Peter Freyther <[EMAIL PROTECTED]>
Date: Wed Jul 23 20:04:12 2008 +0200
[keyboard] Do not send keycodes >= NR_KEYS to kdrive as they are not
handled
NR_KEYS as of linux/keyboard.h is 256. That fits into unsigned
char, the
linux_to_x_keymap is of that size, KdEnqueueKeyboardEvent takes
unsigned
char that will happily take up to 256 different values. Now with
the linux
input framework we can report high keys. KEY_POWER2 (365) is such
a high
keycode, we get this properly reported through extended keycode's
but the
rest of kdrive fails to handle this. So these 365 get casted to
unsigned
char (365&0xff) and then something will happen...
In the Openmoko case we managed to hit a modifier that changed our
keyboard.
Do not report keys to kdrive that it currently can not properly
handle.
(https://docs.openmoko.org/trac/ticket/1533)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1533#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1422: Device doesn’t wake up from blank time when incoming a call and SMS
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: assigned
Priority: high | Milestone: ASU
Component: Qtopia | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------------------+--------------------------------------
Comment(by zecke):
So it goes to sleep during a call? Is that the first boot of the device?
Could you reboot and check if that is still the case?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1422#comment:9>
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: new
Priority: normal | Milestone: OM-2007.2
Component: unknown | Version:
Severity: major | Keywords:
Blocking: | Blockedby:
----------------------+-----------------------------------------------------
The distro-feed-configs_1.0-r0_om-gta02.ipk package in the archive breaks
the feeds if one doesn't pay attention and answers Y in differences
prompts.
See discussion at
http://lists.openmoko.org/pipermail/support/2008-August/001139.html
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1751>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1422: Device doesn’t wake up from blank time when incoming a call and SMS
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED]
Type: defect | Status: assigned
Priority: high | Milestone: ASU
Component: Qtopia | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-------------------------------------+--------------------------------------
Comment(by zecke):
Also were you able to answer the call? did you see the callscreen? could
you pick it up? what was your blank time set to?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1422#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
