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 #1864: Keyboard needs to have a
non-predictive mode (Openmoko Public Trac)
2. Re: Openmoko Bug #1728: SMS parser bug? (Openmoko Public Trac)
3. Re: Openmoko Bug #1864: Keyboard needs to have a
non-predictive mode (Openmoko Public Trac)
4. Re: Openmoko Bug #1267: Strong echo when calling a Neo from
another phone (Openmoko Public Trac)
5. Re: Openmoko Bug #1864: Keyboard needs to have a
non-predictive mode (Openmoko Public Trac)
6. Re: Openmoko Bug #1728: SMS parser bug? (Openmoko Public Trac)
7. Re: Openmoko Bug #1697: [Battery] No Alert message when
battery is low (Openmoko Public Trac)
8. Re: Openmoko Bug #1728: SMS parser bug? (Openmoko Public Trac)
--- Begin Message ---
#1864: Keyboard needs to have a non-predictive mode
-------------------------------------------------+--------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: 2008.8, keyboard, predictive, pm | Blockedby:
Reproducible: always | Blocking:
-------------------------------------------------+--------------------------
Changes (by zecke):
* status: closed => reopened
* resolution: duplicate =>
Comment:
Summary (from my point of view):
- One wants to be able to switch keyboard implementations fast
(qwertz, pickboard, chinese)
- One wants to be able to change "modes" fast (prediction on and off)
Discussion:
- Fast probably means one to two clicks. Either use a hardware key or
have it easily accessible in the decoration.
- Does mode vs. keyboard make sense? For the prediction case it might
not. In Opie we had multikeys which could load any layout and then a per
keyboard config made sense. Personally I would go for "keyboards" and have
per keyboard configs with the assumption that keyboard switching is fast
and config is only used once in a while.
A lot of this is probably duplicate to the "how to switch keyboard
discussion"
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:21>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1728: SMS parser bug?
-----------------------+----------------------------------------------------
Reporter: odlg | Owner: tick
Type: defect | Status: in_testing
Priority: high | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-----------------------+----------------------------------------------------
Comment(by zecke):
Sorry, I'm only on a GPRS line and managed to upload the packages to
om2008.8-testing. Could you please test that? You should get
4.3.2+git413+13101ab6ddaec380871ae8021a92140af526c4df-r39.1 as version for
Qtopia.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1728#comment:24>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1864: Keyboard needs to have a non-predictive mode
-------------------------------------------------+--------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: 2008.8, keyboard, predictive, pm | Blockedby:
Reproducible: always | Blocking:
-------------------------------------------------+--------------------------
Comment(by iknowjoseph):
Replying to [comment:21 zecke]:
> Summary (from my point of view):
> - One wants to be able to switch keyboard implementations fast
(qwertz, pickboard, chinese)
> - One wants to be able to change "modes" fast (prediction on and
off)
>
> Discussion:
>
> - Fast probably means one to two clicks. Either use a hardware key or
have it easily accessible in the decoration.
>
> - Does mode vs. keyboard make sense? For the prediction case it might
not. In Opie we had multikeys which could load any layout and then a per
keyboard config made sense. Personally I would go for "keyboards" and have
per keyboard configs with the assumption that keyboard switching is fast
and config is only used once in a while.
>
> A lot of this is probably duplicate to the "how to switch keyboard
discussion"
This all sounds good.
I like flicking the keyboard up to change the mode it's in. How about
flicking it up to a non-predictive mode? Perhaps differentiated from the
predictive keyboard by colouring the keys differently?
Thanks for re-opening the ticket; I tried to do the same myself but lacked
the permissions to do so.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:22>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1267: Strong echo when calling a Neo from another phone
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: sean_chiang
Type: defect | Status: assigned
Priority: high | Milestone:
Component: Audio | Version: unspecified
Severity: normal | Resolution:
Keywords: audio, echo | Blockedby:
Blocking: |
-------------------------------+--------------------------------------------
Comment(by [EMAIL PROTECTED]):
I'd like to know the development roadmap regarding an echo cancellation
module for the Neo. The speex AEC seems to be quite nice and may be useful
for a little copy and paste. Is someone from OM Inc. working on the
subject? I may be able to contribute to a solution, if someone is willing
to provide some guidance (implementation as an ALSA plugin, or as a sound
daemon plugin?).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1267#comment:12>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1864: Keyboard needs to have a non-predictive mode
-------------------------------------------------+--------------------------
Reporter: iknowjoseph | Owner: openmoko-devel
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: unknown | Version: Om2008.8
Severity: normal | Resolution:
Keywords: 2008.8, keyboard, predictive, pm | Blockedby:
Reproducible: always | Blocking:
-------------------------------------------------+--------------------------
Comment(by Yorick):
That seems to sum it up nicely zecke.
For predictive input it might also be nice to be able to add the word to
the wordbook from within the keyboard. For example: when typing a word on
the default kb by "pressing and holding" the letters, a button could
appear to add the resulting word to the wordbook.
I have *personally* a preference for mode over keyboard changing (e.g. a
button to turn predictive on an off) this will maybe make it more easy to
add the words to the dictionary while typing.
Thank you once more for your time and effort.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1864#comment:23>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1728: SMS parser bug?
-----------------------+----------------------------------------------------
Reporter: odlg | Owner: tick
Type: defect | Status: in_testing
Priority: high | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-----------------------+----------------------------------------------------
Comment(by odlg):
OK, that seems to help, new SMS's are shown correct, old SMS's seems to be
a mix of correctly shown SMS's and non-correct.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1728#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1697: [Battery] No Alert message when battery is low
----------------------------+-----------------------------------------------
Reporter: regina_kim | Owner: raster
Type: enhancement | Status: in_testing
Priority: high | Milestone: Om2008.9
Component: E - Illume | Version:
Severity: minor | Resolution:
Keywords: pm | Blockedby:
Reproducible: | Blocking:
----------------------------+-----------------------------------------------
Comment(by raster):
i assumed the battery going red was the simple solution/addressing of
this?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1697#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1728: SMS parser bug?
-----------------------+----------------------------------------------------
Reporter: odlg | Owner: tick
Type: defect | Status: in_testing
Priority: high | Milestone:
Component: Qtopia | Version: Om2008.8
Severity: major | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
-----------------------+----------------------------------------------------
Comment(by odlg):
OK, that seems to help, new SMS's are shown correct, old SMS's seems to be
a mix of correctly shown SMS's and non-correct.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1728#comment:25>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
