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 #1898: Phone subsystem does not always
suspend/resume properly (Openmoko Public Trac)
2. Re: Openmoko Bug #1206: Even when "Dim only, don't lock"
slected, screen is locked (Openmoko Public Trac)
3. Re: Openmoko Bug #1562: 12 hour time format does not work
(Openmoko Public Trac)
4. Re: Openmoko Bug #1884: [suspend/resume] if press power
batton right after suspend, the device won't wake up
(Openmoko Public Trac)
5. Re: Openmoko Bug #1722: [GSM] taking signal is too slow
(Openmoko Public Trac)
6. Re: Openmoko Bug #1762: [illume bar menu] menu will hiding
after qt-keypad when creating texts (Openmoko Public Trac)
7. Re: Openmoko Bug #1878: infinite recursion in
om-locations-map-pack.c (Openmoko Public Trac)
8. Re: Openmoko Bug #1762: [illume bar menu] menu will hiding
after qt-keypad when creating texts (Openmoko Public Trac)
--- Begin Message ---
#1898: Phone subsystem does not always suspend/resume properly
-----------------------+----------------------------------------------------
Reporter: robolange | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: Om2007.2
Component: unknown | Version: GTA02v5
Severity: major | Keywords:
Blockedby: | Reproducible: sometimes
Blocking: |
-----------------------+----------------------------------------------------
Using OM2007.2 with the power management turned on, after the phone
suspends, the phone subsystem does not always resume properly. When this
happens, a reboot seems to be required to regain phone functionality.
When first booting the phone, once network registration happens, you can
make and receive phone calls. Let the phone go unused for a while, so
that it suspends itself. Now make a call to the phone.
With some probability (p), the phone will wake up and you can receive the
call, and then make other calls. With (1-p), the phone will not wake up.
In this case, even if you wake it up manually by pushing the power button,
you will not be able to send or receive calls. Regardless, the icon for
signal strength and the operator name remain the same as they were before
the suspend.
Using `libgsmd-tool -m shell`, I get the error "Can't connect to gsmd". I
restart gsmd. I invoke `libgsmd-tool -m shell` again, and attempt to
power up the antenna using command `O`. It will fail often; see bug
#1415. Once it powers up, use the registration command `r`. You will see
signal strength and a registration printed to the console. However, you
do not get the pop-up announcing the registration, and the signal strength
and operator name does not change. You still will not be able to make or
receive phone calls.
Something must not have woken up correctly. At this point, the only way I
know to fix it is to reboot the phone. :(
This bug seriously affects my ability to use the device as a phone,
because I need suspend/resume, else the battery does not last even one
business day. I consider the bug quite severe, but its severity would be
less if I knew of a way to regain phone functionality without a time-
consuming reboot.
Also, I don't know this for sure, but it seems that the probability of the
phone resuming correctly is inversely correlated to how long it has been
suspended. It seems that when I frequently resume the phone, I rarely
have to reboot, whereas when I go a "long" time without resuming, I almost
always have to reboot.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1898>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1206: Even when "Dim only, don't lock" slected, screen is locked
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: Om2007.2
Component: openmoko-screensaver | Version: GTA02v5
Severity: normal | Resolution:
Keywords: | Blockedby:
Blocking: |
----------------------------------+-----------------------------------------
Comment(by robolange):
From my experience, I think that this is simply a poorly worded dialog.
It seems that the actual options are intended to be:
1. Dim, lock, then suspend
2. Dim, lock, but don't suspend
3. Minimal power management*
Personally, I am okay with those options, as long as the dialog is worded
correctly.
* Note that (3) does not dim the screen, but the screen backlight goes off
after a while.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1206#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1562: 12 hour time format does not work
---------------------------+------------------------------------------------
Reporter: regina_kim | Owner: zecke
Type: defect | Status: new
Priority: normal | Milestone: Om2008.9
Component: E - Illume | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Comment(by regina_kim):
sound good. thanks i hope so ^^
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1562#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1884: [suspend/resume] if press power batton right after suspend, the device
won't wake up
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: andy
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
--------------------------------+-------------------------------------------
Comment(by Treviño):
I've just tried to kill X and loading apm -s.
Phone suspends but, again, it freezes and won't come up until forced
reboot :/
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1884#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1722: [GSM] taking signal is too slow
--------------------------------+-------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: Om2008.9
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by erin_yueh):
it's like the normal procedure. When we boot the cellphone, it takes time
to register with the GSM network. During this period, we cannot make phone
calls obviously. Also, i agree with Holger. We can put this to a
performance bug, and then we can decide our booting procedure. Then adjust
the GSM modem starting time or when we can start to use all
applications.....etc
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1722#comment:4>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1762: [illume bar menu] menu will hiding after qt-keypad when creating texts
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: raster
Type: defect | Status: reopened
Priority: high | Milestone: Om2008.9
Component: E - Illume | Version:
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
---------------------------+------------------------------------------------
Changes (by wendy_hung):
* reproducible: => always
* status: closed => reopened
* resolution: worksforme =>
* milestone: Om2008.8 => Om2008.9
Comment:
Hi raster, the qt-keypad partially covered by illume bar. I think it's
still one part or this bug, can you take a look of this??
kernel:20080826-asu.stable-uImage.bin
root file system:20080828-asu.stable-rootfs.jffs2
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1762#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1878: infinite recursion in om-locations-map-pack.c
--------------------------+-------------------------------------------------
Reporter: xbaldauf | Owner: jeremy
Type: defect | Status: in_testing
Priority: normal | Milestone: Om2008.9
Component: Locations | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
--------------------------+-------------------------------------------------
Changes (by olv):
* status: assigned => in_testing
Comment:
Thanks for pointing out. 665e46ef6e76b414a055945761eed7e82fc5cead should
fix the problem.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1878#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1762: [illume bar menu] menu will hiding after qt-keypad when creating texts
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: raster
Type: defect | Status: closed
Priority: high | Milestone: Om2008.9
Component: E - Illume | Version:
Severity: major | Resolution: wontfix
Keywords: | Blockedby:
Reproducible: always | Blocking:
---------------------------+------------------------------------------------
Changes (by raster):
* status: reopened => closed
* resolution: => wontfix
Comment:
cannot reproduce. keyboard is below the illume shelf (the top bar with the
down arrow, remove button and battery etc. gadgets) is on top of the
keyboard (keyboard is below it) as intended.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1762#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
