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 228] openmoko applications(contacts, appmanager ...)
easily crash on the phone ([EMAIL PROTECTED])
2. [Bug 228] openmoko applications(contacts, appmanager ...)
easily crash on the phone ([EMAIL PROTECTED])
3. [Bug 262] New: Indicate different charging mode in battery
applet ([EMAIL PROTECTED])
4. [Bug 262] New: Indicate different charging mode in battery
applet ([EMAIL PROTECTED])
5. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
6. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
7. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
8. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
9. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
10. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
11. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
12. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
13. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
14. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
15. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=228
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 18:00 -------
Maybe fix to #245 solves this too?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=228
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 18:00 -------
Maybe fix to #245 solves this too?
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=262
Summary: Indicate different charging mode in battery applet
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: openmoko-panel-battery
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
Since we can be on 100mA or 500mA charging modes, it would be nice to indicate
the mode in the battery dockapp while charging.
The kernel exports this via sysfs (see http://wiki.openmoko.org/wiki/Kernel).
Ideally we would wrap this in some hardware abstraction layer, but for now a
quick hack might be applicable
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=262
Summary: Indicate different charging mode in battery applet
Product: OpenMoko
Version: current svn head
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: openmoko-panel-battery
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
Since we can be on 100mA or 500mA charging modes, it would be nice to indicate
the mode in the battery dockapp while charging.
The kernel exports this via sysfs (see http://wiki.openmoko.org/wiki/Kernel).
Ideally we would wrap this in some hardware abstraction layer, but for now a
quick hack might be applicable
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-12 22:24 -------
I've made a partial fix:
trunk/src/target/u-boot/patches/early-powerdown.patch
Since this is experimental, it's not in
trunk/src/target/u-boot/patches/series. It should be placed between
uboot-20061030-neo1973.patch and uboot-s3c2410-misccr-definitions.patch
What it does: at the earliest opportunity, it checks if the phone was
woken up by the power button of an RTC event. If not, it powers down
immediately. This can be skipped by pressing the AUX button (e.g., if
you want to do just a software or hardware reset).
This gets the board out of the 1.2 and 0.6 second cycles. It doesn't
help against the 120 ms cycle, but that one may actually be just an
artefact of my test setup.
Unfortunately, this hack conflicts with the idea of powering up the
phone when a charger/PC is connected, so that the phone can request
500 mA from the USB host, instead of the meager 100 mA it gets by
default.
------- 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=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-13 04:16 -------
Once Bug 255 is fixed you could check the voltage/capacity at boot and only
enter slow charging mode if it is below a given threshhold. Then the Neo could
check periodically (via RTC wakeup?) and boot into fast charging mode once the
battery is charged partially.
------- 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
