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. [Bug 747] uicmoc4-native_4.3.1.bb
([EMAIL PROTECTED])
2. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
3. [Bug 756] New: Device appears to not charge or have failed
([EMAIL PROTECTED])
4. [Bug 757] New: Patch to openmoko-dialer to handle CREG: 2
responses ([EMAIL PROTECTED])
5. [Bug 755] Dialer assumes UNREG_BUSY will eventually register
correctly ([EMAIL PROTECTED])
6. [Bug 757] Patch to openmoko-dialer to handle CREG: 2
responses ([EMAIL PROTECTED])
7. [Bug 756] Device appears to not charge or have failed
([EMAIL PROTECTED])
8. [Bug 758] New: libmokogsmd2 doesn't handle CB and DS events
([EMAIL PROTECTED])
9. [Bug 759] New: GSM_REGISTER_TIMEOUT is too short
([EMAIL PROTECTED])
10. [Bug 759] GSM_REGISTER_TIMEOUT is too short
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=747
------- Additional Comments From [EMAIL PROTECTED] 2007-08-27 03:22 -------
adding the line:
QT += network
to examples/desktop/screenshot/screenshot.pro allowed me to get through my first
error, unfortunately the build failed with the same error on the next example
program being built.
technil, I think you might be having a different issue, the error you reported
doesn't seem to match this one. My apologies if I mislead you by steering you
here.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at them, and
decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
else. (Hint: if you don't know who to reassign it to, make sure that
the Component field seems reasonable, and then use the "Reassign bug to
owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Just use the "Accept bug" command.
To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL
PROTECTED]
Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.
Appended below are the individual URLs to get to all of your NEW bugs that
haven't been touched for a week or more.
You will get this message once a day until you've dealt with these bugs!
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=466
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=624
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=630
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=700
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=704
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=756
Summary: Device appears to not charge or have failed
Product: Neo1973 Hardware
Version: GTA01v4
Platform: Neo1973
OS/Version: All
Status: NEW
Severity: blocker
Priority: P1
Component: PMU (Power Management Unit)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected],[EMAIL PROTECTED]
The device I have here will not power up.
At first I thought it was probably the battery was depleted but it will not
power up on the cable nor does it appear to charge (it doesn't get warm).
I have tested this on a couple of different machines.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=757
Summary: Patch to openmoko-dialer to handle CREG: 2 responses
Product: OpenMoko
Version: 2007.2
Platform: PC
URL: http://pastebin.ca/672064
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
It seems that registration on my cellular provider's network takes more than 5
seconds.
This patch allows openmoko-dialer to properly handle a
MOKO_GSMD_CONNECTION_NETREG_SEARCHING event from the libmokogsmd2 library, and
wait for registration to complete, instead of continually retrying the
registration request and thereby causing the phone *never* to register.
The patch is at http://pastebin.ca/672064
Basically, I replace the boolean reg_request and registered private variables
with a new version of the registered private variable of type
MokoGsmdConnectionNetregType. This allows the code in register_network_cb to
handle the different cases of NONE, SEARCHING, DENIED, and HOME/ROAMING.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=755
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From [EMAIL PROTECTED] 2007-08-27 09:48 -------
*** This bug has been marked as a duplicate of 757 ***
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=757
------- Additional Comments From [EMAIL PROTECTED] 2007-08-27 09:48 -------
*** Bug 755 has been marked as a duplicate of this bug. ***
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=756
------- Additional Comments From [EMAIL PROTECTED] 2007-08-27 10:05 -------
a brief update, the device does power up but if there is much movement on the
device (ie. it's inverted or the battery is tapped) it reboots so i wonder if
this isnt a device fault?
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=758
Summary: libmokogsmd2 doesn't handle CB and DS events
Product: OpenMoko
Version: 2007.2
Platform: PC
URL: http://pastebin.ca/672079
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: libgsmd
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
moko-gsmd-connection.c complains about not handling cell broadcast and delivery
status reports. This patch puts in default null handling for them, so we don't
pollute the error output with red herrings when trying to debug why calls don't
work.
The patch is at http://pastebin.ca/672079
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=759
Summary: GSM_REGISTER_TIMEOUT is too short
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
#define GSM_REGISTER_TIMEOUT 5000
My phone takes more than 5 seconds to power up the gsm modem according to
/tmp/gsm.log, and when the AT+COPS=0 occurs before the modem is fully powered
up, then the modem fails to register correctly after that.
Doubling the timeout fixes this. In reality, gsmd shouldn't accept or submit a
new command to the modem until it gets the acknowledgement that the modem has
powered up successfully.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=759
------- Additional Comments From [EMAIL PROTECTED] 2007-08-27 11:48 -------
(I'm not suggesting that doubling the timeout is the correct fix - but it is a
good workaround to get people's phones registering reliably until the correct
fix is put in place).
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
