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 #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
2. Re: Openmoko Bug #2009: [battery] The battery stops with
charching, if it's fully charched. (Openmoko Public Trac)
3. Re: Openmoko Bug #1982: [Location] the last line of tag will
only show up half (Openmoko Public Trac)
4. Re: Openmoko Bug #1982: [Location] the last line of tag will
only show up half (Openmoko Public Trac)
5. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
6. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
7. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
8. Openmoko Bug #2010: URLs in SMS messages appear in huge type
(Openmoko Public Trac)
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by dolfje):
My router security is WPA TKIP
(and I'm using 2008.8 updated to the latest updates)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:14>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2009: [battery] The battery stops with charching, if it's fully charched.
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
------------------------+---------------------------------------------------
Comment(by Nytowl):
This looks like a duplicate of 1158
https://docs.openmoko.org/trac/ticket/1158
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2009#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1982: [Location] the last line of tag will only show up half
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: tick
Type: defect | Status: accepted
Priority: normal | Milestone: Om2008.9
Component: Locations | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
---------------------------+------------------------------------------------
Changes (by tick):
* cc: [EMAIL PROTECTED] (added)
Comment:
Hi Jeremy,
I created three patches that. The first two patch can help you set the
extra margin for a scrolled_view. I think these two patches can help us
solving this issue.
adding four new API
void etk_scrolled_view_extra_vmargin_set(Etk_Scrolled_View
*scrolled_view, int margin);
int etk_scrolled_view_extra_vmargin_get(Etk_Scrolled_View
*scrolled_view);
void etk_scrolled_view_extra_hmargin_set(Etk_Scrolled_View
*scrolled_view, int margin);
int etk_scrolled_view_extra_hmargin_get(Etk_Scrolled_View
*scrolled_view);
Demo code:
diff --git a/etk/src/bin/etk_scrolled_view_test.c
b/etk/src/bin/etk_scrolled_view_test.c
index bc3650f..c0d7007 100644
--- a/etk/src/bin/etk_scrolled_view_test.c
+++ b/etk/src/bin/etk_scrolled_view_test.c
@@ -46,6 +46,7 @@ void etk_test_scrolled_view_window_create(void *data)
scrolled_view = etk_scrolled_view_new();
etk_scrolled_view_dragable_set(ETK_SCROLLED_VIEW(scrolled_view), 1);
+ etk_scrolled_view_extra_vmargin_set(ETK_SCROLLED_VIEW(scrolled_view),
60);
etk_container_add(ETK_CONTAINER(win), scrolled_view);
canvas = etk_canvas_new();
I will apply first two patches on OM.dev first. After writing more
comments, adding properties, I will send to them upstream.
Hope will be applied. :-P
For python binding, because it adds new API, so that that part should be
added to pxd and pxi files. (maybe after applied to upstream)
Cheers,
Tick
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1982#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1982: [Location] the last line of tag will only show up half
---------------------------+------------------------------------------------
Reporter: wendy_hung | Owner: tick
Type: defect | Status: accepted
Priority: normal | Milestone: Om2008.9
Component: Locations | Version: Om2008.8
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: always | Blocking:
---------------------------+------------------------------------------------
Changes (by tick):
* cc: [EMAIL PROTECTED] (added)
Comment:
Hi Jeremy,
I created three patches that. The first two patch can help you set the
extra margin for a scrolled_view. I think these two patches can help us
solving this issue.
adding four new API
void etk_scrolled_view_extra_vmargin_set(Etk_Scrolled_View
*scrolled_view, int margin);
int etk_scrolled_view_extra_vmargin_get(Etk_Scrolled_View
*scrolled_view);
void etk_scrolled_view_extra_hmargin_set(Etk_Scrolled_View
*scrolled_view, int margin);
int etk_scrolled_view_extra_hmargin_get(Etk_Scrolled_View
*scrolled_view);
Demo code:
diff --git a/etk/src/bin/etk_scrolled_view_test.c
b/etk/src/bin/etk_scrolled_view_test.c
index bc3650f..c0d7007 100644
--- a/etk/src/bin/etk_scrolled_view_test.c
+++ b/etk/src/bin/etk_scrolled_view_test.c
@@ -46,6 +46,7 @@ void etk_test_scrolled_view_window_create(void *data)
scrolled_view = etk_scrolled_view_new();
etk_scrolled_view_dragable_set(ETK_SCROLLED_VIEW(scrolled_view), 1);
+ etk_scrolled_view_extra_vmargin_set(ETK_SCROLLED_VIEW(scrolled_view),
60);
etk_container_add(ETK_CONTAINER(win), scrolled_view);
canvas = etk_canvas_new();
I will apply first two patches on OM.dev first. After writing more
comments, adding properties, I will send to them upstream.
Hope will be applied. :-P
For python binding, because it adds new API, so that that part should be
added to pxd and pxi files. (maybe after applied to upstream)
Cheers,
Tick
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1982#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by danielhedblom):
Replying to [comment:15 andy]:
> You can tcpdump stuff at the FR, but it doesn't tell you what is
happening "on the air". Because it is likely the problem is FR rejecting
packets from bad encryption, that matters.
I have the same problems on open systems too without any encryption at
all. Its not just the FR rejecting incoming packets. Trying to get packets
out through wifi also fails. If some of you could try on open systems too
we can rule out any encryption/wpa_supplicant problems.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by danielhedblom):
Replying to [comment:15 andy]:
> You can tcpdump stuff at the FR, but it doesn't tell you what is
happening "on the air". Because it is likely the problem is FR rejecting
packets from bad encryption, that matters.
I have the same problems on open systems too without any encryption at
all. Its not just the FR rejecting incoming packets. Trying to get packets
out through wifi also fails. If some of you could try on open systems too
we can rule out any encryption/wpa_supplicant problems.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:16>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1904: om2008.8 wifi don't get always an ipv4 ip
------------------------+---------------------------------------------------
Reporter: dolfje | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone:
Component: unknown | Version:
Severity: normal | Resolution:
Keywords: | Blockedby:
Reproducible: | Blocking:
------------------------+---------------------------------------------------
Comment(by andy):
Can you define a simple test that shows it, which is easily repeatable,
then?
For example, just pinging something on local network at one packet a
second shows high packetloss? Or we need to do bulk transfer?
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:17>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2010: URLs in SMS messages appear in huge type
---------------------+------------------------------------------------------
Reporter: pottage | Owner: julian_chu
Type: defect | Status: new
Priority: normal | Milestone:
Component: Distro | Version:
Severity: minor | Keywords:
Blockedby: | Reproducible: always
Blocking: |
---------------------+------------------------------------------------------
I have received an SMS from my Cellular network operator. There is a URL
in the message and it is displaying in letters that are about 4 times
larger than normal.
It is possible that the network operator has done something special in the
message to highlight the URL, and the SMS tool is misinterpreting that.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2010>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
