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 900] New: Power cycles on and off while charging
([EMAIL PROTECTED])
2. [Bug 176] libgsmd need a mechanism to avoid dead waiting.
([EMAIL PROTECTED])
3. [Bug 176] libgsmd need a mechanism to avoid dead waiting.
([EMAIL PROTECTED])
4. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
5. [Bug 666] 3G SIM capability
([EMAIL PROTECTED])
6. [Bug 839] Call history does not work
([EMAIL PROTECTED])
7. [Bug 901] New: openmoko-today is displaying wrong count of
missed calls ([EMAIL PROTECTED])
8. [Bug 901] openmoko-today is displaying wrong count of missed
calls ([EMAIL PROTECTED])
9. [Bug 902] New: openmoko-dialer display isn't cleared after
pin is sent ([EMAIL PROTECTED])
10. [Bug 902] openmoko-dialer display isn't cleared after pin is
sent ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=900
Summary: Power cycles on and off while charging
Product: Neo1973 Hardware
Version: GTA01v4
Platform: PC
OS/Version: OpenBSD
Status: NEW
Severity: normal
Priority: P2
Component: PMU (Power Management Unit)
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
Several times I have noticed my GTA01v4 will, when being charged from a
standalone USB charger (from a used Blackberry) turn on at least to the point of
showing the first OpenMoko splash screen, show this screen for a short while,
then blank it again. This is, ahh, slightly unusual, and while it's probably
harmless it (a) is a visual distraction and (b) probably isn't helping the
charging.
------- 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=176
------- Additional Comments From [EMAIL PROTECTED] 2007-10-01 04:56 -------
Created an attachment (id=324)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=324&action=view)
for unable to wakeup. (adding a wakeup work around)
There is a very strong assumption that every sent AT command gets a response.
However the firmware with power saving mode will not response first AT command
until it gets a "\r" when modem is in sleep mode.
That is the AT sent by gsmd when moden is in sleep mode will be block forever.
If not changing firmware and hardware design, there is a work around.
Adding an additional " \r" as a atcmd before each real comman.
If modem is in sleep mode, it will not response but will wake up in 1 sec and
keep awaken for about 10 secs.
If modem is awake, it will reply an "OK" immediately.
Therefore, if modem is in sleep mode, we can set a 3 sec timeout and discard
the additional atcmd and then passthrough the real atcmd.
Because modem been awaken will keep awaken for about 10 secs , we can
almost very sure that the modem is awaken in this moment, and will response
correctly.
------- 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=176
------- Additional Comments From [EMAIL PROTECTED] 2007-10-01 05:00 -------
There is a very strong assumption that every sent AT command gets a response.
However the firmware with power saving mode will not response first AT command
until it gets a "\r" when modem is in sleep mode.
That is the AT sent by gsmd when moden is in sleep mode will be block forever.
If not changing firmware and hardware design, there is a work around.
Adding an additional " \r" as a atcmd before each real comman.
If modem is in sleep mode, it will not response but will wake up in 1 sec and
keep awaken for about 10 secs.
If modem is awake, it will reply an "OK" immediately.
Therefore, if modem is in sleep mode, we can set a 3 sec timeout and discard the
additional atcmd and then passthrough the real atcmd.
Because modem been awaken will keep awaken for about 10 secs , we can almost
very sure that the modem is awaken in this moment, and will response
correctly.There is a very strong assumption that every sent AT command gets a
response.
However the firmware with power saving mode will not response first AT command
until it gets a "\r" when modem is in sleep mode.
That is the AT sent by gsmd when moden is in sleep mode will be block forever.
If not changing firmware and hardware design, there is a work around.
Adding an additional " \r" as a atcmd before each real comman.
If modem is in sleep mode, it will not response but will wake up in 1 sec and
keep awaken for about 10 secs.
If modem is awake, it will reply an "OK" immediately.
Therefore, if modem is in sleep mode, we can set a 3 sec timeout and discard the
additional atcmd and then passthrough the real atcmd.
Because modem been awaken will keep awaken for about 10 secs , we can almost
very sure that the modem is awaken in this moment, and will response correctly.
------- 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=41
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
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=129
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=276
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=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=661
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=675
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=696
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=714
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=727
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=742
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=800
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=846
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=847
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=862
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=864
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=865
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=870
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=881
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666
------- Additional Comments From [EMAIL PROTECTED] 2007-10-01 08:37 -------
Latest update, new gsm firmware could work with AT&T 3G fireball USIM now.
------- 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=839
------- Additional Comments From [EMAIL PROTECTED] 2007-10-01 09:57 -------
Created an attachment (id=325)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=325&action=view)
call history fix
Attached patch fix call history
------- 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=901
Summary: openmoko-today is displaying wrong count of missed calls
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-today
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
openmoko-today is displaying count of all calls instead of only
missed incoming calls.
------- 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=901
------- Additional Comments From [EMAIL PROTECTED] 2007-10-01 10:01 -------
Created an attachment (id=326)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=326&action=view)
today incoming missed calls count fix
Attached patch should fix this issue.
------- 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=902
Summary: openmoko-dialer display isn't cleared after pin is sent
Product: OpenMoko
Version: current svn head
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-dialer
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
------- 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=902
------- Additional Comments From [EMAIL PROTECTED] 2007-10-01 10:05 -------
Created an attachment (id=327)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=327&action=view)
clear dialer display after pin is sent
Attached patch:
- clear openmoko-dialer display after pin is sent
- disable tips on inserting numbers in pin_mode
------- 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
