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 #1682: Neo turns off before reaching X
(Openmoko Public Trac)
2. Openmoko Bug #1683: bluez-utils-alsa missing from repository
(Openmoko Public Trac)
3. Re: Openmoko Bug #1682: Neo turns off before reaching X
(Openmoko Public Trac)
4. Re: Openmoko Bug #1653: [QT-Contacts] view contact info,
option menu covered "Hide" (Openmoko Public Trac)
5. Re: Openmoko Bug #1551: [Messages]option menu is covered
"hide" button when press option. (Openmoko Public Trac)
6. Re: Openmoko Bug #1659: [QT-Dialer] Can't open the option
menu while call active or out going phone call (Openmoko Public Trac)
7. Openmoko Bug #1684: WLAN to default to off on Freerunner,
switchable down /sys (Openmoko Public Trac)
8. 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)
--- Begin Message ---
#1682: Neo turns off before reaching X
-----------------------------+----------------------------------------------
Reporter: queen6 | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: System Software | Version: GTA02v5
Severity: normal | Keywords:
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
Hi,
When I turn on my freerunner while battery is very weak, starts normally,
but turns itself off somewhere during INIT.
Where is the charing initiated (500mA from USB)? Is it in kernel,
userspace or u-boot?
The only way to boot it properly is to swap battery for more charged one,
fully boot (until X) and replace it with original one.
I'm using b-boot from 2008.07.27, all other packages have been updated
with Opkg update/upgrade at 2008.07.28. Still the same problem.
Some time ago (~2 weeks) it was possible to boot without battery (battery
was only needed only to power neo on. You could remove on u-boot screen).
Right now it seems it's more power hungry somewhere during INIT.
I'm not sure if that has anything to do with:
Jul 29 07:00:27 om-gta02 user.info kernel: [ 1520.155000] glamo-mci glamo-
mci.0: Error after cmd: 0x8021
Jul 29 07:00:28 om-gta02 user.info kernel: [ 1520.155000] glamo-mci glamo-
mci.0: Error after cmd: 0x8123
Jul 29 07:00:28 om-gta02 user.err kernel: [ 1520.155000] mmcblk0: error
-84 sending read/write command
Jul 29 07:00:28 om-gta02 user.warn kernel: [ 1520.155000] end_request: I/O
error, dev mmcblk0, sector 0
Jul 29 07:00:28 om-gta02 user.err kernel: [ 1520.155000] Buffer I/O error
on device mmcblk0, logical block 0
I will file another bug about it anyway.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1682>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1683: bluez-utils-alsa missing from repository
----------------------+-----------------------------------------------------
Reporter: montgoss | Owner: tick
Type: defect | Status: new
Priority: normal | Milestone: OM-2007.2
Component: Assassin | Version: GTA02v5
Severity: normal | Keywords: bluetooth, alsa, bluez-utils-alsa
Blocking: | Blockedby:
----------------------+-----------------------------------------------------
bluez-utils-alsa is required for A2DP (according to the wiki). It is
missing from the OM2007.2 repository.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1683>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1682: Neo turns off before reaching X
-----------------------------+----------------------------------------------
Reporter: queen6 | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: ASU
Component: System Software | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by andy):
Charging is handled by the kernel driver, 500mA is allowed after USB stack
informs us we are enumerated by a host for 500mA.
You shouldn't get forced off just because it wants to charge anyway, I
guess something else goes on.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1682#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1653: [QT-Contacts] view contact info, option menu covered "Hide"
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: in_testing
Priority: normal | Milestone: ASU
Component: Qtopia | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by zecke):
* status: assigned => in_testing
Comment:
The Xglamo XINERAMA removal should have fixed that.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1653#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1551: [Messages]option menu is covered "hide" button when press option.
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: in_testing
Priority: normal | Milestone: ASU
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by zecke):
* status: assigned => in_testing
Comment:
The Xglamo XINERAMA removal should have fixed that.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1551#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1659: [QT-Dialer] Can't open the option menu while call active or out going
phone
call
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: in_testing
Priority: high | Milestone: ASU
Component: Qtopia | Version:
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by zecke):
* status: assigned => in_testing
Comment:
The Xglamo XINERAMA removal should have fixed that.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1659#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1684: WLAN to default to off on Freerunner, switchable down /sys
-----------------------------+----------------------------------------------
Reporter: andy | Owner: [EMAIL PROTECTED]
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
-----------------------------+----------------------------------------------
GTA02 WLAN is actually always on, but it takes a power and reset signal
from GPIO.
Until now, machine init always powered the thing up by these, adding 300ms
to early boot and causing it to eat more power for the whole session.
I already have a patch that exposes the power_on and reset GPIO same as
done for bt, I will test it (particularly SDIO autodetect is a question,
the code seems to be there) shortly.
The impact on userspace is going to be that dumb initscripts that expect
eth0 there are going to fail now. It really needs to be done via udev, so
the WLAN device can randomly appear and then get configured by
NetworkManager or whatever.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1684>
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: new
Priority: low | Milestone: ASU
Component: E - Illume | Version:
Severity: normal | Keywords:
Blocking: | Blockedby:
-------------------------+--------------------------------------------------
kernel:20080723-asu.stable-uImage.bin
root file system:20080729-asu.stable-rootfs.jffs2
Summary:The device insist to go suspend even after touch the screen to
wake it up from blank time
Steps:
1) set the device with suspend time
2) touch the screen right away when the device goes to the blank time
Current results:
The device will show up the screen for a second than go suspend time what
ever
Expected:
The screen should be lock immediately
PS.
Raster, I know I've been discussed this with you before, but this will
happened when you think the device is wake up and you are ready to use
other applications. It's really annoy and confuse. Can we just lock the
screen once if it goes to blank time or something like this?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1685>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
