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 #1691: [Qtopia] qpe crash happened after
flash the new image (Openmoko Public Trac)
2. Re: Openmoko Bug #1862: stop boot (Openmoko Public Trac)
3. Re: Openmoko Bug #2019: Headphone Jack Event
(Openmoko Public Trac)
4. Re: Openmoko Bug #1691: [Qtopia] qpe crash happened after
flash the new image (Openmoko Public Trac)
5. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
6. Re: Openmoko Bug #2004: screen is blank (black) after resume
(Openmoko Public Trac)
7. Re: Openmoko Bug #1767: Enlightenment Error (Openmoko Public Trac)
8. Re: Openmoko Bug #1767: Enlightenment Error (Openmoko Public Trac)
9. Re: Openmoko Bug #1158: Charging stops even while connected
(Openmoko Public Trac)
--- Begin Message ---
#1691: [Qtopia] qpe crash happened after flash the new image
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: Om2008.10
Component: Qtopia | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Comment(by csamuel):
I was seeing the same issue on my FreeRunner with FDOM 2008-09-13 as
Toscho described (without the nano step). Digging in the logs it appeared
that qpe was having problems talking to the modem and logging lots of
timeouts, after a number of which QPE would exit and the watcher would pop
up the window.
I found that restarting the GSM daemon would fix the timeout problem (or
at least it would be able to talk to the modem successfully and stopped
crashing), but the phone still wouldn't register with the network (unlike
under the standard FDOM 20080913 release).
I'm upgrading to the OM 2008.9 release (pending the FDOM version) to see
whether that's working now.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1691#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1862: stop boot
--------------------------------+-------------------------------------------
Reporter: therippo | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: Om2008.9
Component: System Software | Version: GTA02v6
Severity: critical | Resolution:
Keywords: boot freeze | Blockedby:
Reproducible: | Blocking:
--------------------------------+-------------------------------------------
Comment(by octavsly):
In my case, using the latest release, the battery lasted slightly longer.
http://downloads.openmoko.org/releases/Om2008.9/
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1862#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2019: Headphone Jack Event
------------------------+---------------------------------------------------
Reporter: Zoup | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by werner):
By the way, if you build "gpio" from
http://svn.openmoko.org/trunk/src/target/gpio/
and copy it your Neo, then
# ./gpio f4
should show F0 if the plug is not inserted, and F1 if it is.
If it always shows F0, something is keeping the jack contact from
opening or there is some genuine hardware defect. If you see something
different from F0 or F1, then this would suggest a software problem.
Looking at the hardware, the side of R4406 facing the board center
should always be at about 3.3V. The side of R4406 facing the jack and
the board edge should change between 3.3V (plug inserted) and near 0V
(plug not inserted).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2019#comment:8>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1691: [Qtopia] qpe crash happened after flash the new image
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: zecke
Type: defect | Status: new
Priority: highest | Milestone: Om2008.10
Component: Qtopia | Version:
Severity: blocker | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
---------------------------+------------------------------------------------
Comment(by Toscho):
Somewhere on the mailing lists i found this workaround:
chmod a+rx /etc/X11/Xsession.d/89qtopia
but that didn't work, which means, after a reboot, the qpe-message again
popped up. I then tried chmod +rx /etx/X11/Xsession.d/89qtopia and it
worked although I don't understand why then.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1691#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- 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 werner):
> The problem here however is that the PMU stops charging even when the
> battery is not full and does not resume charging at any point either.
Okay, that's definitely bad. I had two GTA02v6 run with USB power on
and off during the last couple of weeks in the hope of finding charging
anomalies, but none of them powered down unexpectedly (well, unless I
forgot to plug in USB again :-)
> perceived loss of charger power by the kernel
Hmm, the PMU dump earlier in this thread shows that the charger function
is disabled but the USB voltage is fine.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2004: screen is blank (black) after resume
------------------------+---------------------------------------------------
Reporter: ssinger | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by ssinger):
I've updated again, and the problem hasn't reoccured (yet) but this was
not reproduceable on demand. I can also only tell the difference between
a crash on this problem when it happens near by PC so I can get in through
USB networking to verify the freerunner is still alive.
Is this the same problem described by #1789? (it sounds somewhat similar,
but the details on that ticket are less specific and no logs are
attached).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2004#comment:5>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1767: Enlightenment Error
---------------------+------------------------------------------------------
Reporter: ssweeny | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Blocking: |
---------------------+------------------------------------------------------
Comment(by shashank):
I'm using FDOM (version 20080913)
and I'm getting this *white box of death* too
I'm guessing that it occurs whenever a qtopia application is launched. (be
it Dialer, Calender...)
But it's not consistent. Sometimes it launches without errors also.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1767#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1767: Enlightenment Error
---------------------+------------------------------------------------------
Reporter: ssweeny | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Blocking: |
---------------------+------------------------------------------------------
Comment(by shashank):
I'm using FDOM (version 20080913)
and I'm getting this *white box of death* too
I'm guessing that it occurs whenever a qtopia application is launched. (be
it Dialer, Calender...)
But it's not consistent. Sometimes it launches without errors also.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1767#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- 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 andy):
Replying to [comment:25 werner]:
> > The problem here however is that the PMU stops charging even when the
> > battery is not full and does not resume charging at any point either.
>
> Okay, that's definitely bad. I had two GTA02v6 run with USB power on
> and off during the last couple of weeks in the hope of finding charging
> anomalies, but none of them powered down unexpectedly (well, unless I
> forgot to plug in USB again :-)
Did they have SIMs in? This 4mA drain seen by battery even when we give
USB power is consistent with the GSM side pulling it direct from battery.
> > perceived loss of charger power by the kernel
>
> Hmm, the PMU dump earlier in this thread shows that the charger function
> is disabled but the USB voltage is fine.
It's from 2 months ago, we changed things around since then and can do
with another register dump from a device that shows this behaviour. If it
really does show that it's a big clue.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1158#comment:26>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
