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 932] New: not receive new SMS message event in
openmoko-today ([EMAIL PROTECTED])
2. [Bug 932] not receive new SMS message event in openmoko-today
([EMAIL PROTECTED])
3. [Bug 866] No number entered should recall last dialed number
when tapping Dial ([EMAIL PROTECTED])
4. [Bug 866] No number entered should recall last dialed number
when tapping Dial ([EMAIL PROTECTED])
5. [Bug 861] Aplication launcher does not notify category change
([EMAIL PROTECTED])
6. [Bug 867] Landscape mode support
([EMAIL PROTECTED])
7. [Bug 933] New: event import
([EMAIL PROTECTED])
8. [Bug 928] implement AT command interrupt/cancel
([EMAIL PROTECTED])
9. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
10. [Bug 911] GSM modem dies on registration with several
different SIM cards on Rogers GSM network
([EMAIL PROTECTED])
11. [Bug 842] Whenever possible, Amp Mode should be Off
([EMAIL PROTECTED])
12. [Bug 593] audio doesn't survive suspend/resume
([EMAIL PROTECTED])
13. [Bug 593] audio doesn't survive suspend/resume
([EMAIL PROTECTED])
14. [Bug 842] Whenever possible, Amp Mode should be Off
([EMAIL PROTECTED])
15. [Bug 894] gsmd locks-up if libgsmd-tool disconnects too
quickly ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=932
Summary: not receive new SMS message event in openmoko-today
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-today
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected],[EMAIL PROTECTED]
in openmoko-today, new message counter is not updated when we receive new SMS
message. But, missed call counter is updated by 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=932
------- Additional Comments From [EMAIL PROTECTED] 2007-10-15 12:17 -------
This is because SMS functionality is currently not implemented in libmokogsmd
------- 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=866
------- Additional Comments From [EMAIL PROTECTED] 2007-10-15 17:06 -------
Created an attachment (id=354)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=354&action=view)
Show dialed history on dialing empty number
So, first tap of dial button (when no number entered) with this patch
will show dialed history with selected last dialed number from history list.
* src/moko-dialer.c: (on_keypad_dial_clicked): Show dialed history
when dialing empty number.
* src/moko-history.c: (moko_history_set_filter): Select first item
in history list after filter was changed.
------- 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=866
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |LATER
------- Additional Comments From [EMAIL PROTECTED] 2007-10-15 18:32 -------
I've committed Roman's patch, but altered it slightly to select the first item
in the on_filter_changed() callback rather than in moko_history_set_filter().
This is more desirable as it also makes sure an item is always selected when the
user changes the filter.
Although this doesn't resolve the feature request exactly as described, I think
it is a better situation that trying to dial a blank number. It also solves the
problem of having no previously dialed numbers by displaying this information
rather than attempting to fill in the dialer display.
------- 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=861
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2007-10-15 18:39 -------
Appears to be working for me too. Please re-open if you can still reproduce the
bug in the latest software.
------- 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=867
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |REMIND
------- Additional Comments From [EMAIL PROTECTED] 2007-10-15 19:09 -------
This works correctly using the moko-gtk-engine theme because it has less padding
around the buttons. I'm not sure how we might fix this for themes that have more
padding.
------- 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=933
Summary: event import
Product: OpenMoko
Version: 2007.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: openmoko-calculator
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
I was able to import my palmpilot addressbook and calendar to evolution on my
PC, and then rsynced .evolution to my Neo. The contacts look roughly correct
(though no notes!), but the calendar entries showing seem to be a fairly random
assortment -- stuff for several different days, weeks and even years are in the
Today list.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
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=928
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 00:34 -------
Created an attachment (id=355)
-->
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=355&action=view)
Implement atcmd cancelling and VOICECALL_HANGUP
This is a proposed implementation of exactly what the bug report describes. It
applies on top of all the recent patches from the list the last one being the
Mike Westerhof's lgsmd_send fix, i.e. what's in OE at the moment. It adds an
atcmd_cancel call for cancelling the currently executing command and uses it to
fix VOICECALL_HANGUP. It may be a resolution to bug #906 but the patch is
untested on the physical phone because I was unable to charge my Neo enough to
do this for a couple of days, so submitting as is - please test.
------- 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=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=808
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=835
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=882
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=888
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=908
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=911
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- 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=842
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 05:26 -------
graeme, can you please investigate this issue and work on a patch, or at least
comment on the bug. thanks!
------- 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=593
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 05:31 -------
so you're basically saying that without ASOCv2 (which I assume is a major
change, introducing it's own issues and dependencies on e.g. later kernels) we
cannot have working suspend/resume on the audio driver?
This sounds a bit too odd for me to believe. Can you please provide more
details?
------- 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=593
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 08:23 -------
We dont have to go to ASoC V2, the change is also in ASoC V1 git, and requires
basically replacing soc.c and soc-dapm.c with ones from git with corresponding
headers. I think codec and machine drivers are unaffected.
The problem I was having at Wolfson was ASoC V1 tree is dead now, ASoC V2 will
be the basis for all new development. But ASoC V2 hasnt reached release status
yet.
The fix is the core has to keep track of all currently running PCM streams and
send a SUSPEND command to them on suspend and and RESUME command to them on
resume otherwise they are still playing over suspend and get upset. It did not
do this in the ASoC version used in Neo kernel.
------- 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=842
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 08:30 -------
I believe you checked in a patch to turn amp off in suspend yesterday. I guess
it also needs to turn it off in unload? I dont know the mechanism for powerdown
and what path it takes in the driver.
The rest of these cases are AFAIK user space cases. As the sound driver does not
know when we are inside a GSM call and therefore doesnt know to turn the amp
on/off. This should I believe be a function of neod/ohm/soundmanager.
------- 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=894
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From [EMAIL PROTECTED] 2007-10-16 11:00 -------
I'm seeing this too, so reopening. If a libgsm client disconnects too quickly,
gsmd gets confused, and locks-up, gdb showed this backtrace (it was echo n | ...
in my case):
#0 usock_cmd_enqueue (ucmd=0x308d0, gu=0x308d0)
at ../../include/common/linux_list.h:73
#1 0x0000e07c in network_ownnumbers_cb (cmd=0x30800, ctx=0x308d0,
resp=0x20060 "+CNUM: ,\"507328011\",129") at usock.c:597
#2 0x0000b2ac in atcmd_done (g=0x1db4c, cmd=0x30800, buf=0x1e3bc "OK")
at atcmd.c:268
#3 0x0000bf58 in atcmd_newdata_cb (opaque=<value optimized out>,
data=0x1f0ef "\r\n29,,,0\r\n6A3D100\r\nA3D168341A8D46",
len=<value optimized out>) at atcmd.c:174
#4 0x0001362c in uart_select_cb (fd=3, what=1, data=<value optimized out>)
at uart.c:115
#5 0x0000c1f8 in gsmd_select_main () at select.c:98
#6 0x0000ad98 in main (argc=<value optimized out>, argv=<value optimized out>)
at gsmd.c:463
I will have a look at it later and try to send a patch.
------- 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
