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. [Bug 264] package libelf-0.8.6-r0: task do_populate_staging:
      failed ([EMAIL PROTECTED])
   2. [Bug 421] systray applet only shows white rectangles
      ([EMAIL PROTECTED])
   3. [Bug 419] dfu download doesn't clean jffs2 partition
      ([EMAIL PROTECTED])
   4. [Bug 135] Finger applications need close functionality
      ([EMAIL PROTECTED])
   5. [Bug 571] New: Fonts in menus / home screen / terminal
      emulator are      too small ([EMAIL PROTECTED])
   6. [Bug 572] New: Screensaver needs to ignore first click,   and
      probably should force user through "unlock" sequence
      ([EMAIL PROTECTED])
   7. [Bug 93] test 4GB microSD card compatibility
      ([EMAIL PROTECTED])
   8. [Bug 93] test 4GB microSD card compatibility
      ([EMAIL PROTECTED])
   9. [Bug 312] sim card holder too frail (SIM holder/microSD
      holder is crappy) ([EMAIL PROTECTED])
  10. [Bug 383] Display is unreadable in sunlight
      ([EMAIL PROTECTED])
  11. [Bug 573] New: Screen flickers
      ([EMAIL PROTECTED])
  12. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
  13. [Bug 93] test 4GB microSD card compatibility
      ([EMAIL PROTECTED])
  14. [Bug 93] test 4GB microSD card compatibility
      ([EMAIL PROTECTED])
  15. [Bug 93] test 4GB microSD card compatibility
      ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=264

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2007-05-21 12:15 -------
sorry for reopening this bug... the problem was with frozen revision of
openembeded when using Mokomakefile. Rod Whitby just commited the patch (thanks
again).



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=421

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #160 is|0                           |1
           obsolete|                            |



------- Additional Comments From [EMAIL PROTECTED]  2007-05-21 12:30 -------
(From update of attachment 160)
Patch is in svn now




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=419

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major



------- Additional Comments From [EMAIL PROTECTED]  2007-05-21 17:05 -------
Upping the priority because this can lead to all kinds of strange errors from
panic on boot to erratic behavior on some of the apps.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=135





------- Additional Comments From [EMAIL PROTECTED]  2007-05-21 23:05 -------
I guess top and bottom bars should be merged at the top of the screen... that
should make area big enough to operate by finger, and I guess "close" button
would fit there.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=571

           Summary: Fonts in menus / home screen / terminal emulator are too
                    small
           Product: OpenMoko
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Theming
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


...they are fine indoors, but neo1973 screen sucks on direct sunlight, and small
fonts are almost imposible to read.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572

           Summary: Screensaver needs to ignore first click, and probably
                    should force user through "unlock" sequence
           Product: OpenMoko
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Host Software
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


Ok, so I power openmoko on, it boots, logs into the network... and turns screen
off after timeout. I want to work with it, so I touch the screen...

...and machine starts to launch some application. Probably click on the dark
screen should be ignored.

And then... I put neo into my pocket and go on bycicle or something. When I pull
it out of my pocket, screen is shining most of the time. That means that:

1) neo was wasting power with backlight on in my pocket, because of the random
touchscreen touches

2) it was performing random operations.

Probably some kind of "touchscreen lock" should be implemented. "Screen locked,
press 911 button to unlock"? "Screen locked, touch top right corner then bottom
left corner to unlock"?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=93





------- Additional Comments From [EMAIL PROTECTED]  2007-05-21 23:46 -------
Hmm, Bv4 machine here works ok (after some complains in syslog) with provided
128MB card, but errors out with A-data 2GB microSD card :-(.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=93





------- Additional Comments From [EMAIL PROTECTED]  2007-05-21 23:46 -------
(Actually, even with provided 128MB sdcard, I got errors after streaming 40MB of
data over scp).



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=312

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|sim card holder to frail    |sim card holder too frail
                   |(SIM holder/microSD holder  |(SIM holder/microSD holder
                   |is crappy)                  |is crappy)





------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=383





------- Additional Comments From [EMAIL PROTECTED]  2007-05-22 00:02 -------
I removed the protective layer now. It is _better_, but not good. I can read
"big" letters with some difficulty... Other cellphones are a lot better.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=573

           Summary: Screen flickers
           Product: Neo1973 Hardware
           Version: GTA01v4
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Screen
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


...and default theme makes it more visible. It is hardly perceptible in
"default" condition, but ssh in, and find / makes it very visible in dark room.

(I seen same effect on Bv3 hardware, and my brother seen it, too, so I'm not
dreaming).



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=536
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=540
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=541
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=93





------- Additional Comments From [EMAIL PROTECTED]  2007-05-22 07:08 -------
Do you have a dmesg so we can see what the error is?



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=93





------- Additional Comments From [EMAIL PROTECTED]  2007-05-22 11:26 -------
> Do you have a dmesg so we can see what the error is?

Hmm, it now says:

<4>adc_read: entering (pcf=c07dac00, channel=0, data2=00000000)
<4>pcf50606_irq: entering(irq=60, pcf=c07dac00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x00 INT3=0x01:SECOND ADCRDY
<4>adc_read: returning 647 0
<4>mapped channel 0 to 0
<7>mmc_set_power(power_mode=0, vdd=0
<6>s3c2410-sdi s3c2410-sdi: powered down.
<7>mmc_set_power(power_mode=1, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 0kHz (requested: 0kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<6>s3c2410-sdi s3c2410-sdi: initialisation done.
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 99kHz (requested: 98kHz).
<7>mmc_set_power(power_mode=0, vdd=0
<6>s3c2410-sdi s3c2410-sdi: powered down.

<4>adc_read: entering (pcf=c07dac00, channel=0, data2=00000000)
<4>pcf50606_irq: entering(irq=60, pcf=c07dac00): scheduling work
<4>pcf50606_work: INT1=0x40 INT2=0x00 INT3=0x01:SECOND ADCRDY
<4>adc_read: returning 647 0
[EMAIL PROTECTED]:/lib/modules/2.6.21.1-moko10/kernel$

...but I'm pretty sure I seen scarier messages before...? Kernel is
may-19 one from .../tmp/deploy, this is generated while modprobing the
hci module.




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=93





------- Additional Comments From [EMAIL PROTECTED]  2007-05-22 11:28 -------
Successful attempt (on phase1 openmoko, with original kernel) looks like:

<6>Freeing init memory: 108K <7>mmc_set_power(power_mode=1, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 0kHz (requested: 0kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20 <6>s3c2410-sdi s3c2410-sdi: running at
130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 130kHz (requested: 129kHz).
<7>mmc_set_power(power_mode=2, vdd=20 <6>s3c2410-sdi s3c2410-sdi: running at
130kHz (requested: 129kHz).
<4>mmc0: Problem switching card into high-speed mode!
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 16625kHz (requested: 25000kHz).
<7>mmc_set_power(power_mode=2, vdd=20
<6>s3c2410-sdi s3c2410-sdi: running at 16625kHz (requested: 25000kHz).
<6>mmcblk0: mmc0:e624 SU128 123008KiB
<6> mmcblk0: p1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1
<7>PM: Removing info for No Bus:vcsa1
<7>PM: Removing info for No Bus:vcs1 <7>PM: Removing info for No Bus:vcsa1
<6>yaffs: dev is 266338304 name is "mmcblk0"
<4>yaffs: Attempting MTD mount on 254.0, "mmcblk0"
<6>yaffs: dev is 266338304 name is "mmcblk0"
<4>yaffs: Attempting MTD mount on 254.0, "mmcblk0" 



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to