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 #1808: No accelerometer data
(Openmoko Public Trac)
2. Re: Openmoko Bug #1808: No accelerometer data
(Openmoko Public Trac)
3. Re: Openmoko Bug #1766: GSM Antenna Signal (Openmoko Public Trac)
4. Re: Openmoko Bug #1798: No pin-dialog appears (the second)
(Openmoko Public Trac)
5. Re: Openmoko Bug #1697: [Battery] No Alert message when
battery is low (Openmoko Public Trac)
6. Re: Openmoko Bug #1697: [Battery] No Alert message when
battery is low (Openmoko Public Trac)
7. Re: Openmoko Bug #1766: GSM Antenna Signal (Openmoko Public Trac)
8. Re: Openmoko Bug #1721: [QT-Dialer] Sometimes can not hear
anything during connecting the call (Openmoko Public Trac)
--- Begin Message ---
#1808: No accelerometer data
---------------------+------------------------------------------------------
Reporter: Mercury | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: Om2008.8
Component: unknown | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by andy):
That isn't quite testing what you might imagine since a different
bitbanged implementation is used to service the interrupts for speed.
Is this an A6 or A5 revision device? Have a look in /proc/cpuinfo
Revision : 0350 <== A5 (0360 = A6)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1808#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1808: No accelerometer data
---------------------+------------------------------------------------------
Reporter: Mercury | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: Om2008.8
Component: unknown | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blocking:
Blockedby: |
---------------------+------------------------------------------------------
Comment(by Mercury):
A5
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1808#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1766: GSM Antenna Signal
--------------------------------+-------------------------------------------
Reporter: dexteruk | Owner: zecke
Type: defect | Status: accepted
Priority: high | Milestone:
Component: Qtopia | Version: GTA02v6
Severity: normal | Resolution:
Keywords: GSM Antenna Signal | Blocking:
Blockedby: |
--------------------------------+-------------------------------------------
Changes (by erl):
* cc: erl (added)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1766#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1798: No pin-dialog appears (the second)
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: new
Priority: highest | Milestone: Om2008.8
Component: unknown | Version: GTA02v5
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------+----------------------------------------------------
Comment(by Anasazi):
Replying to [comment:4 Rorschach]:
> Problem has finally been identified and workaround is available. Just
follow this thread on the ML:
http://lists.openmoko.org/pipermail/community/2008-August/026096.html
The described workaround does *not* work for me. I tried 5 times now and
*never* got a pin dialog (previously once in about 10 tries). So please
continue to analyze :-)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1798#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1697: [Battery] No Alert message when battery is low
-------------------------+--------------------------------------------------
Reporter: regina_kim | Owner: raster
Type: enhancement | Status: assigned
Priority: high | Milestone: Om2008.9
Component: E - Illume | Version:
Severity: minor | Resolution:
Keywords: pm | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Comment(by raster):
ok - reason why "config" is involved:
the battery gadget is e's own default battery meter - the same one i see
on my laptop. same code. exact same thng. it just has a different theme in
illume (on ASU). that exact same code ALREADY can pop up a warning dialog
if the battery reaches X percent or Y minutes left until empty. that code
has been there for years now. that is configured to be DISABLED in ASU.
there is a configuration dialog to enable/disable this and set the time or
percentage at which to show it. the problem is that ASU is set up in such
a way that the mechanism that has existed for years to do just this is not
available to a user. so there is no need to "add" a dialog... it's already
there! (in ASU it doesn't have a nice theme - but it would work... if you
could turn it on). so to me this is a design issue as design wanted to be
very particular about exactly what configuration is available and how. all
the existing code E has had for years and infrastructure to expose this
and make it accessible to users has been ignored, so i can't really do
much. (the start of the whole exposure thing. must be in python etc. etc.
i made a point of this but it was not my call) :)
i probably need to say "i told you so" in that life will just get harder
and everything be more and more work the more design tries to fight
against existing infrastructure and code. :(
anyway - as for battery going red - that is possible. it's just part of
the theme. but as design is to be pixel perfect, until design specifies a
red battery - i can't do it, as it's not specified in the design :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1697#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1697: [Battery] No Alert message when battery is low
-------------------------+--------------------------------------------------
Reporter: regina_kim | Owner: raster
Type: enhancement | Status: assigned
Priority: high | Milestone: Om2008.9
Component: E - Illume | Version:
Severity: minor | Resolution:
Keywords: pm | Blocking:
Blockedby: |
-------------------------+--------------------------------------------------
Comment(by raster):
ok - reason why "config" is involved:
the battery gadget is e's own default battery meter - the same one i see
on my laptop. same code. exact same thng. it just has a different theme in
illume (on ASU). that exact same code ALREADY can pop up a warning dialog
if the battery reaches X percent or Y minutes left until empty. that code
has been there for years now. that is configured to be DISABLED in ASU.
there is a configuration dialog to enable/disable this and set the time or
percentage at which to show it. the problem is that ASU is set up in such
a way that the mechanism that has existed for years to do just this is not
available to a user. so there is no need to "add" a dialog... it's already
there! (in ASU it doesn't have a nice theme - but it would work... if you
could turn it on). so to me this is a design issue as design wanted to be
very particular about exactly what configuration is available and how. all
the existing code E has had for years and infrastructure to expose this
and make it accessible to users has been ignored, so i can't really do
much. (the start of the whole exposure thing. must be in python etc. etc.
i made a point of this but it was not my call) :)
i probably need to say "i told you so" in that life will just get harder
and everything be more and more work the more design tries to fight
against existing infrastructure and code. :(
anyway - as for battery going red - that is possible. it's just part of
the theme. but as design is to be pixel perfect, until design specifies a
red battery - i can't do it, as it's not specified in the design :(
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1697#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1766: GSM Antenna Signal
--------------------------------+-------------------------------------------
Reporter: dexteruk | Owner: zecke
Type: defect | Status: accepted
Priority: high | Milestone:
Component: Qtopia | Version: GTA02v6
Severity: normal | Resolution:
Keywords: GSM Antenna Signal | Blocking:
Blockedby: |
--------------------------------+-------------------------------------------
Comment(by wilk):
Same here : I can enter the PIN Code, it's accepted (I can read the
addressbook on the SIM) but the phone won't register although it can
receive calls. Only once did it register, in less than a minute
surprisingly. I hadn't done anything special though.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1766#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1721: [QT-Dialer] Sometimes can not hear anything during connecting the call
------------------------+---------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: in_testing
Priority: highest | Milestone: Om2008.8
Component: Qtopia | Version:
Severity: blocker | Resolution:
Keywords: must have | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Comment(by geocode):
Using that command fixed it for me (using 2008.08 release).
First I had to:
opkg install alsa-utils openmoko-alsa-scenarios
Then the aforementioned file was available. So things are looking up for
sure! I still have a crazy echo on the receiving end. I will go look
into that now.
Thanks again.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1721#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
