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. Openmoko Bug #1552: it shows the numbers while enter the SIM
pin (Openmoko Public Trac)
2. Openmoko Bug #1553: sometimes it shows "sending : 2 messages"
even i sent one. (Openmoko Public Trac)
3. Openmoko Bug #1554: when press option still will shows "save
to contacts" even number already saved in contacts
(Openmoko Public Trac)
4. Openmoko Bug #1555: can't input pin numbers again after press
"cancel" in the option menu (Openmoko Public Trac)
5. Openmoko Bug #1556: Kernel suspend/resume backglight and
resume "reason" bugs. (Openmoko Public Trac)
6. Re: Openmoko Bug #1542: gps does not get fix
(Openmoko Public Trac)
7. Re: Openmoko Bug #1542: gps does not get fix
(Openmoko Public Trac)
8. Openmoko Bug #1557: Don't use absolute paths in MokoMakefile
(Openmoko Public Trac)
9. Re: Openmoko Bug #1557: Don't use absolute paths in
MokoMakefile (Openmoko Public Trac)
--- Begin Message ---
#1552: it shows the numbers while enter the SIM pin
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: unknown | Version:
Severity: major | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
Kernel ： 20080705-asu.stable-uImage.bin
Root file system ：20080708-asu.stable-rootfs.jffs2
steps:
1) input a SIM card which need pin
2) launch the device, after boot time it show up
3) in put the pin numbers but show up the original input numbers
expect:
show up "*" instead of characters
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1552>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1553: sometimes it shows "sending : 2 messages" even i sent one.
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: unknown | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
kernel : 20080705-asu.stable-uImage.bin
rootfs : 20080708-asu.stable-rootfs.jffs2
summary : sometimes it shows "sending : 2 messages" even i sent one.
step :
1. go SMS
2. new messages
3. input letter and send it
reproducible: 5~6 out of 10 tries.
current result :it should show "sending: 2 messages" even i sent 1
expected result : it should show "sending: 1 message"
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1553>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1554: when press option still will shows "save to contacts" even number already
saved in contacts
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: normal | Milestone: ASU
Component: unknown | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
kernel : 20080705-asu.stable-uImage.bin
rootfs : 20080708-asu.stable-rootfs.jffs2
summary : when press option still will shows "save to contacts" even
number already saved in contacts
step :
1. go to SMS
2. new message
3. input letter and select number which saved in contacts and sent it
4. go to sent box and select sent item
5. press option and select save to contacts
current result :save to contact still activate and when press that no
reactivate
expected result : remove that function when contact is already saved
contacts.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1554>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1555: can't input pin numbers again after press "cancel" in the option menu
-------------------------+--------------------------------------------------
Reporter: wendy_hung | Owner: [EMAIL PROTECTED]
Type: enhancement | Status: new
Priority: high | Milestone: ASU
Component: unknown | Version:
Severity: normal | Keywords: pin
Blocking: | Blockedby:
-------------------------+--------------------------------------------------
Kernel ： 20080705-asu.stable-uImage.bin
Root file system ：20080708-asu.stable-rootfs.jffs2
steps:
1) at input pin number screen
2) press option and show up the menu
3) press"cancel" and disappear the "pin screen"
expected:
remove the option menu, or can find somewhere to input the pin again
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1555>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1556: Kernel suspend/resume backglight and resume "reason" bugs.
-----------------------------+----------------------------------------------
Reporter: raster | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: high | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
in:
/sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/backlight/pcf50633-bl
* now... before suspend:
#cat brightness
21
# cat actual_brightness
21
* now suspend:
# apm -s
* now resume (press power)
#cat brightness
21
# cat actual_brightness
63
seems wrong to me. the brightness should be restored on resume exactly as
it was left. the same happens to bl_power. if it was off on suspend - it
should be off on resume (also i guess he inverse logic above fixed too).
am i right? or am i missing something?
also while i am at it...
/sys/devices/platform/neo1973-resume.0/resume_reason
never seems it indicate the resume reason - no entry has an '*' next to it
ever... :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1556>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1542: gps does not get fix
----------------------+-----------------------------------------------------
Reporter: emdete | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: normal | Milestone:
Component: hardware | Version:
Severity: blocker | Resolution:
Keywords: | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Comment(by HdR):
I can confirm this, too.
I didn't get a fix at my window even after 60 minutes of waiting.
In the garden i tried about 30min to get a fix without any success, on the
other hand i got a fix after <5min at a second test in the garden, the
third test was disappointing again (>20min without a fix)
If I had a fix, it is lost by going into the house, and doesn't come back,
if i go outside again (at leat not in the next 5 minutes)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1542#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1542: gps does not get fix
----------------------+-----------------------------------------------------
Reporter: emdete | Owner: [EMAIL PROTECTED]
Type: defect | Status: new
Priority: normal | Milestone:
Component: hardware | Version:
Severity: blocker | Resolution:
Keywords: | Blocking:
Blockedby: |
----------------------+-----------------------------------------------------
Comment(by proquar):
I have the same problem.
With the internal antenna I can wait hours and get no fix, on places where
I usually receive ~8 satellites. Only thing I get is the time after about
30 minutes.
When I connect an external antenna I get a fix in less than 2 minutes,
usually in less than 1 minute. I get the time after about 20 seconds.
If I got a fix with an external antenna and switch back to the internal
one, it still receives all satellites it has seen before and easily
maintains it's fix and even recovers it when I take the Freerunner inside
for a short time.
I'm using a MP Freerunner, 900MHz-version, assembly was on 2008-06-18.
(maybe it matters?)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1542#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1557: Don't use absolute paths in MokoMakefile
------------------------+---------------------------------------------------
Reporter: uzytkownik | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version: current svn head
Severity: normal | Keywords:
Blocking: | Blockedby:
------------------------+---------------------------------------------------
In MokoMakefile there is a fixed path /sbin/mkdosfs. In gentoo mkdosfs is
in /usr/sbin/mkdosfs. Could you change the absolute paths into a calls or
search standard dirs ({/,/usr/,/usr/local/}{s,}bin)?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1557>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1557: Don't use absolute paths in MokoMakefile
------------------------+---------------------------------------------------
Reporter: uzytkownik | Owner: openmoko-devel
Type: defect | Status: new
Priority: low | Milestone:
Component: unknown | Version: current svn head
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by uzytkownik):
* priority: highest => low
Comment:
It is customable but it still would be nice if it was autodetected...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1557#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
