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 #1739: [Exposure] Sometimes Profile will
show up "unknow" message (Openmoko Public Trac)
2. Re: Openmoko Bug #1734: [Exposure] wifi show up "unknown"
(Openmoko Public Trac)
3. Re: Openmoko Bug #1482: [oe]AUX bottom doesn't shine red
light while charging (Openmoko Public Trac)
4. Re: Openmoko Bug #666: 3G SIM capability (Openmoko Public Trac)
5. Re: Openmoko Bug #1802: Suspend/resume corrupts SD card's
partition table (Openmoko Public Trac)
6. Re: Openmoko Bug #1808: No accelerometer data
(Openmoko Public Trac)
7. Re: Openmoko Bug #1788: Maps - Please do not store offline
data in /tmp (Openmoko Public Trac)
8. Re: Openmoko Bug #1621: it will show white screen when press
power button from suspend time(it only happens specific
phone(no.51)) (Openmoko Public Trac)
9. Re: Openmoko Bug #1765: No pin-dialog appears after boot, so
no gsm is working in 2008.8 (Openmoko Public Trac)
--- Begin Message ---
#1739: [Exposure] Sometimes Profile will show up "unknow" message
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: accepted
Priority: high | Milestone: Om2008.9
Component: Exposure | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by will):
* milestone: Om2008.8 => Om2008.9
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1739#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1734: [Exposure] wifi show up "unknown"
------------------------+---------------------------------------------------
Reporter: wendy_hung | Owner: marek
Type: defect | Status: accepted
Priority: high | Milestone: Om2008.9
Component: Exposure | Version:
Severity: major | Resolution:
Keywords: | Blocking:
Blockedby: |
------------------------+---------------------------------------------------
Changes (by will):
* milestone: Om2008.8 => Om2008.9
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1734#comment:7>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1482: [oe]AUX bottom doesn't shine red light while charging
-----------------------------+----------------------------------------------
Reporter: wendy_hung | Owner: julian_chu
Type: defect | Status: assigned
Priority: high | Milestone: Om2008.9
Component: System Software | Version:
Severity: critical | Resolution:
Keywords: must have | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Changes (by will):
* milestone: Om2008.8 => Om2008.9
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1482#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#666: 3G SIM capability
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: michael
Type: defect | Status: new
Priority: highest | Milestone:
Component: GSM Modem | Version: unspecified
Severity: critical | Resolution:
Keywords: SIM att 7300g 71234 4022 | Blocking:
Blockedby: |
----------------------------------------+-----------------------------------
Comment(by Kev):
Replying to [comment:68 sirkha]:
> How can one tell if they are using a 1.8V or 3.0 V simcard?
I've readthat it is written on some simcards. I'm astonished that there
seem to be nothing to get some infos, like manufacturer and model number,
out of an simcard.
Nothing new from openmoko in this issue?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/666#comment:69>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1802: Suspend/resume corrupts SD card's partition table
-----------------------------+----------------------------------------------
Reporter: montgoss | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: critical | Resolution:
Keywords: | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by andy):
Mike Westerhof sent in a patch earlier that impacts GSM suspend / resume
behaviour and might be connected with this.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1802#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):
The accelerometers seem to be working on some level. I'm suspecting
something strange with the kernel.
[EMAIL PROTECTED]:~# echo 1 >
/sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/power/wakeup
[EMAIL PROTECTED]:~# cat /sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/dump
(lying flat on desk)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3b
09 84 89 01 00 08 12 94 11 1e 0e 01 00 00 00 00
47 00 e4 00 00 00 00 ff 00 fe 00 00 00 35 00 00
95 25 14 00 00 00 00 00 00 00 00 00 00 00 00 00
[EMAIL PROTECTED]:~# cat /sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/dump
(perpendicular to desk)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3b
09 84 89 01 00 08 12 94 11 1e 0e 01 00 00 00 00
47 00 e4 00 00 00 00 ff 00 d7 00 da 00 02 00 00
95 1a 14 00 00 00 00 00 00 00 00 00 00 00 00 00
[EMAIL PROTECTED]:~# cat /sys/devices/platform/spi_s3c24xx_gpio.1/spi0.0/dump
(flat on desk again)
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3b
09 84 89 01 00 08 12 94 11 1e 0e 01 00 00 00 00
47 00 e4 00 00 00 00 ff 00 fe 00 01 00 34 00 00
95 25 14 00 00 00 00 00 00 00 00 00 00 00 00 00
Looks like it's able to tell what orientation my phone is in, but the
input event interface device gives me nothing.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1808#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1788: Maps - Please do not store offline data in /tmp
--------------------------+-------------------------------------------------
Reporter: Sjors | Owner: jeremy
Type: enhancement | Status: assigned
Priority: normal | Milestone: Om2008.8
Component: Diversity | Version: OM-2008.08
Severity: normal | Resolution:
Keywords: maps offline | Blocking:
Blockedby: |
--------------------------+-------------------------------------------------
Comment(by noha):
In tangogps it works ok. /tmp is default but you can change configuration
to point the cache dir to your preferred location
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1788#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1621: it will show white screen when press power button from suspend time(it
only
happens specific phone(no.51))
-----------------------------+----------------------------------------------
Reporter: regina_kim | Owner: openmoko-kernel
Type: defect | Status: new
Priority: high | Milestone: Om2008.8
Component: System Software | Version:
Severity: blocker | Resolution:
Keywords: must have? | Blocking:
Blockedby: |
-----------------------------+----------------------------------------------
Comment(by tfm):
It happens with the Om2008.8 release too. Sometimes after resuming it only
shows a white screen. It then sometimes takes some seconds until the
screen recovers, sometimes it takes minutes, sometimes I lose patience
first and turn it off. ;)
The white screen predominantly appears after long suspend; e.g. 8h over
night. When I wake it up in the morning it takes really long until the
white disappears. But then almost every subsequent suspend/resume creates
the white screen, no matter how long suspend was. After reboot the
probability for white screen is significantly lower.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1621#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1765: No pin-dialog appears after boot, so no gsm is working in 2008.8
-----------------------+----------------------------------------------------
Reporter: Rorschach | Owner: openmoko-devel
Type: defect | Status: closed
Priority: highest | Milestone:
Component: Qtopia | Version: OM-2008.08
Severity: critical | Resolution: worksforme
Keywords: | Blocking:
Blockedby: |
-----------------------+----------------------------------------------------
Comment(by apm):
This shouldn't be in a bug tracker, but I must say I've never experienced
so disappointing a behaviour when I've spent time providing debug data.
Just for the record, I'm not here to keep this ticket open, I'm here to
help provide data until I can see the problem has been diagnosed and
bottom line is that you closed the bug report with a wrong and arrogant
diagnose.
Replying to [comment:41 zecke]:
> Come on. Instead of actually fixing any bug and moving packages to
.testing I'm busy with
> helping people to use a bugtracker... (seen globally on all incoming
bugs)
This is insane. You're not learning me anything. I do this every day, just
from your point of view, and I never tell a reporter to get lost with a
claim that he's running unsupported software, when he is not.
> Replying to [comment:37 apm]:
> > Oh... I just discovered: Incoming calls work, but using the dialer to
call out still says: "No phone call is possible. Reason GSM phone is not
registred, No network".
>
> Yes, we at least have four reports for that. I have witnessed this as
well.. I have done a fix, but I'm not able to put a potential fix for that
into .testing as I'm completely busy with assisting people to use a
bugtracker....
>
Well - then that was what you should have written as diganose.
> > I'm reopening this, and please take it serious this time. WE DO NOT
RUN gsmd
>
> At least one user did and I was referring to the log message.
Yes, but a lot of us wasn't.
> See, I acknowledge there is an issue. There is no doubt that there is an
issue. But there is no way I can "solve" what this bug report has been
turned in. I can not set it to "in_testing" as there is no way QA can
verify that all the mentioned issues have been fixed. So the best thing I
can do is to close this bug, and open one bug for one issue mentioned, or
rely on people doing that. Reopening the bug does not change anything but
keeps me away from putting bugfixes into .testing.
But you don't close a bug report by telling people the reason for their
trouble is something they know and can prove is false.
> > Symptoms are:
> > * PIN dialog does not appear after boot!
> > * It can appear later - for me it sometimes work to restart X
> > * When it appears it seems to take the PIN correctly
> > * But afterwards, there's no outgoing GSM calls. (for me incoming
calls work though)
>
> This is all related to the QAtChat (see my 1st vs 2nd) and highly
dependent on timing. So by restarting, or killing qpe, or changing configs
can change it. See the last five commits in
http://git.openmoko.org/?p=qtopia.git;a=summary
Thanks.
>
> > * However... GSM has been seens to start working after waiting >30
minutes.
>
> Random luck. I think the scanning of external media is just wasting
power but is not blocking anything inside Qtopia.
Hmm.. it seems pretty consistant though, that once it has started to work
it work.
> Please keep that bug closed, that does not mean there is no issue, but
we engineers have to have a good signal noise ratio to do our work and
sadly we really head to a bad direction with this bugtracker.
Sure I'll keep it close. Now I know that this problem is diagnosed. ...
see the difference?
Your S/N ration can be kept down by not giving people bogus explanations.
Write that you suspect this is a duplicate. Convince people that you're on
top of it. Don't tell people falsehood - it only gives the impression that
you don't know what your're talking about which will achieve the exact
opposite of what you want.
> Like in the two closing attempts. Your options are:
> - File a bug for 1st (no one did that)
> - File a bug for 2nd (the initial reporter did)
No reason - now I know you're on top of it.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1765#comment:42>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
