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 #1158: Charging stops even while connected
(Openmoko Public Trac)
2. Reg:Multitap Pad Keyboard (veena s)
3. Re: Openmoko Bug #2035: [2008.8 updated]White screen of death
at startup (Openmoko Public Trac)
4. Re: Openmoko Bug #2039: dfu-util recognize 044e:300c Alps
Electric Co., Ltd as an openmoko phone (Openmoko Public Trac)
5. Re: Openmoko Bug #2038: Qtopia USSD requests support
(Openmoko Public Trac)
6. Re: Openmoko Bug #2036: resize2fs /dev/mmcblk02p2 128m seg
faults (Openmoko Public Trac)
7. Re: Openmoko Bug #2035: [2008.8 updated]White screen of death
at startup (Openmoko Public Trac)
--- Begin Message ---
#1158: Charging stops even while connected
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.10
Component: System Software | Version: unspecified
Severity: critical | Resolution:
Keywords: power management | Blockedby:
Reproducible: sometimes | Blocking:
---------------------------------+------------------------------------------
Comment(by johndoesacc):
I have experienced the same issue. It seems that it happens after it's
completely charged. I tried it now while i was connected to it through
USB. I run the Om distro fully updated with the 2008.8 repository as of
today. I ran some commands while it happened. I split the output into two
to illustrate when it happened:
{{{
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery charging: 100% (0:00:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery charging: 100% (0:00:00)
}}}
This is when it started showing the battery icon instead of the lightning
bolt icon on the phone's screen.
{{{
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (45d+12:15:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (1d+1:05:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (1d+14:40:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (7d+5:26:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (3d+21:21:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (3d+8:54:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (20:45:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (5d+11:43:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 100% (1d+12:55:00)
[EMAIL PROTECTED]:~# cat /sys/devices/platform/s3c2440-i2c/i2c-
adapter/i2c-0/0-0073/charger_type
charger 1A mode 500mA
[EMAIL PROTECTED]:~# apm --verbose
APM BIOS 1.2 (kernel driver 1.13)
On-line, battery status high: 99% (20:28:00)
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:27>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
Hi All,
I have cross Compiled the Multitap pad
[multitap-pad_svn.o-hand.com_.repos.misc.trunk_373_.tar.gz] for Arm Target ..
and my etc/gtk-2.0/im-multipress.conf[keys] contains the following key mappings
..
KP_0 = +;=;/;\\
KP_1 = .;,;/;-;?;!;@;:;(;)
KP_2 = a;b;c;2
KP_3 = d;e;f;3
KP_4 = g;h;i;4
KP_5 = j;k;l;5
KP_6 = m;n;o;6
KP_7 = p;q;r;s;7
KP_8 = t;u;v;8
KP_9 = w;x;y;z;9
KP_10 = A;B;C;2
KP_11 = D;E;F;3
KP_12 = G;H;I;4
KP_13 = J;K;L;5
KP_14 = M;N;O;6
KP_15 = P;Q;R;S;7
KP_16 = T;U;V;8
KP_17 = W;X;Y;Z;9
Xmodmap is done as shown below...
xmodmap -e "keycode 49 = Shift_L"
xmodmap -e "add shift = Shift_L"
xmodmap -e "keycode 61 = Shift_R"
xmodmap -e "add shift = Shift_R"
xmodmap -e "keycode 114 = Menu"
xmodmap -e "add shift = Menu"
xmodmap -e "keycode 65 = Caps_Lock"
xmodmap -e "add lock = Caps_Lock"
xmodmap -e "keycode 36 = Control_L"
xmodmap -e "add control = Control_L"
xmodmap -e "keycode 96 = Control_R"
xmodmap -e "add control = Control_R"
xmodmap -e "keycode 63 = Alt_L"
xmodmap -e "add mod1 = Alt_L"
xmodmap -e "keycode 100 = Alt_R"
xmodmap -e "add mod1 = Alt_R"
xmodmap -e "keycode 101 = Num_Lock"
xmodmap -e "add mod2 = Num_Lock"
xmodmap -e "keycode 112 = Super_L"
xmodmap -e "add mod3 = Super_L"
xmodmap -e "keycode 113 = Super_R"
xmodmap -e "add mod3 = Super_R"
The problem is when i enable the caps lock on the multitap pad & try to press
the keys CAPITAL Keys are entered in the text edit box but at rare time it
displays the small charaters in the text box..
so please tell me whether is a bug in the multitap pad Source package or the
way i am doing is wrong ...
Thanks & Regards
Veena
Unlimited freedom, unlimited storage. Get it now, on
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html/
--- End Message ---
--- Begin Message ---
#2035: [2008.8 updated]White screen of death at startup
----------------------------------------------------+-----------------------
Reporter: jollyr0ger | Owner:
openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Om2008.9-dev
Severity: normal | Resolution:
Keywords: white, screen, death, startup, boot | Blockedby:
Reproducible: always | Blocking:
----------------------------------------------------+-----------------------
Comment(by jollyr0ger):
Here is the complete error message:
The gpe process vanished. This is bad. This is not meant to happen and is
likely a sign of a bug in Qtopia. Please try to reproduce it and report
the bug to http://docs.openmoko.org.
To be able to use your phone as a phone again you will have to restart
Qtopia.
(F1) Restart (F2) Exit
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2035#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2039: dfu-util recognize 044e:300c Alps Electric Co., Ltd as an openmoko phone
------------------------+---------------------------------------------------
Reporter: GNUtoo | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution: invalid
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* status: new => closed
* resolution: => invalid
Comment:
Sorry, this is not a bug. dfu-util is implementing the
DeviceFirmwareUpgrade (DFU) Protocol. The freerunner is not the only
device implementing this protocol. Many bluetooth devices implement it as
well. dfu-util -l is listing all devices that can be upgraded with dfu-
util.
http://wiki.openmoko.org/wiki/USB_DFU should have more information on the
protocol.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2039#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2038: Qtopia USSD requests support
----------------------------+-----------------------------------------------
Reporter: Treviño | Owner: zecke
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Qtopia | Version: Om2008.9-dev
Severity: normal | Resolution:
Keywords: HasPatch | Blockedby:
Reproducible: always | Blocking:
----------------------------+-----------------------------------------------
Comment(by zecke):
Wow. Good stuff. I will need some time to apply it though.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2038#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2036: resize2fs /dev/mmcblk02p2 128m seg faults
------------------------+---------------------------------------------------
Reporter: Niko! | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone:
Component: unknown | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Changes (by zecke):
* owner: julian_chu => openmoko-devel
* component: Distro => unknown
Comment:
Okay. I think I already pointed you to
http://wiki.openmoko.org/wiki/Bug_Filing_Policy this means the next bug
will be just closed as "Invalid" according to the policy. This is not bad
will but writing this consumes engineering time that could be better spend
on reviewing patches or fixing actual bugs.
You set a component and shouldn't have set one, you are supposed to append
the output of opkg list_installed and you didn't. Specially the last part
is something that is really missing in this case.
Please append the required files.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2036#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2035: [2008.8 updated]White screen of death at startup
----------------------------------------------------+-----------------------
Reporter: jollyr0ger | Owner:
openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Om2008.9-dev
Severity: normal | Resolution:
Keywords: white, screen, death, startup, boot | Blockedby:
Reproducible: always | Blocking:
----------------------------------------------------+-----------------------
Comment(by Toscho):
Seems to be a duplicate of #1691. Try the solutions there.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2035#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
