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 #1803: Installer reports all package
Download size as 0 bytes (Openmoko Public Trac)
2. Re: Openmoko Bug #1792: SMS not received properly during
suspend (Openmoko Public Trac)
3. Re: Openmoko Bug #1991: [Suspend] unable to suspend, just
stay black screen after wake up by power button from suspend
(Openmoko Public Trac)
4. Re: Openmoko Bug #1992: Suspend/Resume plays up when
initiated manually (Openmoko Public Trac)
5. Re: Openmoko Bug #1822: 2008.8 doesn't wake on alarm
(Openmoko Public Trac)
6. Re: Openmoko Bug #1822: 2008.8 doesn't wake on alarm
(Openmoko Public Trac)
7. Re: Openmoko Bug #1970: ar6k does not print newline after
disconnect message (Openmoko Public Trac)
8. Re: Openmoko Bug #1991: [Suspend] unable to suspend, just
stay black screen after wake up by power button from suspend
(Openmoko Public Trac)
--- Begin Message ---
#1803: Installer reports all package Download size as 0 bytes
------------------------------------------+---------------------------------
Reporter: peepsalot | Owner:
Type: defect | Status: assigned
Priority: normal | Milestone: Om2008.9
Component: Distro | Version: Om2008.8
Severity: normal | Resolution:
Keywords: opkg-util, size, HasPatch | Blockedby:
Reproducible: | Blocking:
------------------------------------------+---------------------------------
Changes (by regina_kim):
* owner: tick =>
* status: in_testing => assigned
Comment:
hey tick.
we will put this assign again. when it really ready then put in testing
please.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1803#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1792: SMS not received properly during suspend
------------------------+---------------------------------------------------
Reporter: thomasb | Owner: zecke
Type: defect | Status: in_testing
Priority: normal | Milestone: Om2008.9
Component: Qtopia | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by regina_kim):
hey thomasb
can you test this ticket again weather is happen still ?
what about get sms when not suspend status ??
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1792#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1991: [Suspend] unable to suspend, just stay black screen after wake up by
power
button from suspend
---------------------------+------------------------------------------------
Reporter: regina_kim | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: unknown | Version:
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
---------------------------+------------------------------------------------
Comment(by wendy_hung):
relate bug #1992, thanks for thepizzaking help us to get the log.
Let me discrib this bug more...
this bug means first time you set suspend time you'll have suspend time,
but once you wake it up by power button, the second suspend time will fail
(become blank time) you can click the screen to wake it up. So if this
time you press the power button try to wake it up, actually is bring it to
suspend time(use power button to suspend).
After second suspend (blank time) it still will go into suspend (third
suspend) than this time you'll have really suspend time....
Hope this is clear enough. :)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1991#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1992: Suspend/Resume plays up when initiated manually
-----------------------------+----------------------------------------------
Reporter: thepizzaking | Owner: openmoko-devel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution: duplicate
Keywords: | Blockedby:
Reproducible: always | Blocking:
-----------------------------+----------------------------------------------
Changes (by wendy_hung):
* status: new => closed
* resolution: => duplicate
Comment:
duplicate bug than #1991, thanks for your logread, lets comment more in
#1991. :)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1992#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1822: 2008.8 doesn't wake on alarm
-------------------------+--------------------------------------------------
Reporter: madjo | Owner: zecke
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: Qtopia | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------+--------------------------------------------------
Comment(by Treviño):
To prove what said above, I've tried to do this:
{{{
diff --git a/src/libraries/qtopia/qalarmserver.cpp
b/src/libraries/qtopia/qalarmserver.cpp
index a5a8bff..346768f 100644
--- a/src/libraries/qtopia/qalarmserver.cpp
+++ b/src/libraries/qtopia/qalarmserver.cpp
@@ -207,7 +207,7 @@ void TimerReceiverObject::resetTimer()
// from the Epoch in seconds.
//
int at_secs = nearest.toTime_t();
- QString fn = atdir + QString::number(at_secs) + "."
+ QString fn = atdir + QString::number(at_secs - 10) + "."
+ QString::number(::getpid());
if ( fn != atfilename ) {
QFile atfile(fn+".new");
}}}
Whith this code the phone woke up from suspend 10 second before than the
alarm time, but also with this workaround Qtopia doesn't ring at all.
Also if I enable the alarm, I make the phone suspend and then I wake-up it
about 30 seconds - 1 minute before the alarm time the phone doesn't ring
at all at the right time.
I figure that a workaround/fix could be appling the patch above, then
making qtopia check if an alarm was enabled (in its configuration) every
time that the phone is woked-up (is there a way to make qtopia aware of
this?). If it was enabled, it should re-enable it (informing
qtopiaalarmserver that should ring!).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1822#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1822: 2008.8 doesn't wake on alarm
-------------------------+--------------------------------------------------
Reporter: madjo | Owner: zecke
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: Qtopia | Version: Om2008.8
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-------------------------+--------------------------------------------------
Comment(by Treviño):
To prove what said above, I've tried to do this:
{{{
diff --git a/src/libraries/qtopia/qalarmserver.cpp
b/src/libraries/qtopia/qalarmserver.cpp
index a5a8bff..346768f 100644
--- a/src/libraries/qtopia/qalarmserver.cpp
+++ b/src/libraries/qtopia/qalarmserver.cpp
@@ -207,7 +207,7 @@ void TimerReceiverObject::resetTimer()
// from the Epoch in seconds.
//
int at_secs = nearest.toTime_t();
- QString fn = atdir + QString::number(at_secs) + "."
+ QString fn = atdir + QString::number(at_secs - 10) + "."
+ QString::number(::getpid());
if ( fn != atfilename ) {
QFile atfile(fn+".new");
}}}
Whith this code the phone woke up from suspend 10 second before than the
alarm time, but also with this workaround Qtopia doesn't ring at all.
Also if I enable the alarm, I make the phone suspend and then I wake-up it
about 30 seconds - 1 minute before the alarm time the phone doesn't ring
at all at the right time.
I figure that a workaround/fix could be appling the patch above, then
making qtopia check if an alarm was enabled (in its configuration) every
time that the phone is woked-up (is there a way to make qtopia aware of
this?). If it was enabled, it should re-enable it (informing
qtopiaalarmserver that should ring!).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1822#comment:10>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1970: ar6k does not print newline after disconnect message
--------------------------------+-------------------------------------------
Reporter: mattb | Owner: openmoko-kernel
Type: defect | Status: closed
Priority: normal | Milestone:
Component: System Software | Version: Om2008.9-dev
Severity: normal | Resolution: fixed
Keywords: HasPatch | Blockedby:
Reproducible: always | Blocking:
--------------------------------+-------------------------------------------
Changes (by andy):
* status: new => closed
* resolution: => fixed
Comment:
Thanks, I sent it into stable kernel branch.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1970#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1991: [Suspend] unable to suspend, just stay black screen after wake up by
power
button from suspend
---------------------------+------------------------------------------------
Reporter: regina_kim | Owner: openmoko-devel
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: unknown | Version:
Severity: critical | Resolution:
Keywords: | Blockedby:
Reproducible: sometimes | Blocking:
---------------------------+------------------------------------------------
Comment(by andy):
There's one thing extra about description that would help a lot, "black
screen" or "blank screen" is very hard to know exactly what it means.
What we need to know is if the backlight is on or not. If the screen
shows all black pixels with the backlight on, you can still see some light
coming through if you take the device to a dark place. If the backlight
is off though, it will be completely black all the time. Those two kinds
of "black screen" are very different for us.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1991#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
