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. Openmoko Bug #2009: [battery] The battery stops with
charching, if it's fully charched. (Openmoko Public Trac)
2. Re: Openmoko Bug #2008: Suspend exceptions: Do not suspend
when certain apps are running (Openmoko Public Trac)
3. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
4. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (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 #1789: 2008.8 screen blanks and refuses to
wakeup (Openmoko Public Trac)
7. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
8. Re: Openmoko Bug #1904: om2008.8 wifi don't get always an
ipv4 ip (Openmoko Public Trac)
--- 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 | Keywords:
Blockedby: | Reproducible: always
Blocking: |
---------------------+------------------------------------------------------
I have noticed it after the updates from 2 days ago (om 2008.8). I plug my
Neo FreeRunner on the wall charger at night. It starts to charge. When
it's fully charged, it stops with charging and starts using the battery.
So if I check my phones battery in the morning, I see the battery icon
stands on 3 of the 4 blocks.
Step to reproduce:
- put your FreeRunner at the wall charger (delivered with the FreeRunner).
You may choose to suspend or not. I tested once while it never suspends
and once while I had manually suspended it.
- wait for the morning
- look at the battery icon
Expected result:
- the FreeRunner is fully charched
Actual result:
- the FreeRunner is only 3/4 charged.
Distro: 2008.8 updates (Updated 2 days ago)
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2009>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2008: Suspend exceptions: Do not suspend when certain apps are running
----------------------------------+-----------------------------------------
Reporter: Benih | Owner: openmoko-kernel
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: System Software | Version: Om2008.8
Severity: minor | Resolution:
Keywords: suspend exception | Blockedby:
Reproducible: | Blocking:
----------------------------------+-----------------------------------------
Comment(by beni):
An even better solution would be to just implement some "plugin" interface
to the suspender.
The suspender may only call a "suspend.deny" executable with predefined
return codes.
If that executable returns "0", then suspend can occur. If it returns
something else than "0", then suspend should be aborted.
"suspend.deny" executable could then be set via the update-alteratives
procedure.
This way, users have all possibilitys to implement their own suspending-
denial scripts. The user could easily install the one he likes (via opkg)
while developers can happily implement their own suspend.deny stuff. Users
may even decide to not install some suspend.deny implementation at all.
Openmoko devs only need to implement that call to suspend.deny, the
community could provide the rest.
I already have some simple suspend.deny with the above mentioned features
in mind, that could serve as some proof-of concept and may even be the
default suspend.deny program.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2008#comment:5>
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 dolfje):
I've tested a little bit:
If my FreeRunner is freshly started, I can always connect and reconnect
with 'ifdown eth0' and 'ifup eth0'. And it's working reliable. (I'm
sitting 3 meters away from the router)
--- 192.168.1.100 ping statistics ---
150 packets transmitted, 150 received, 0% packet loss, time 149150ms
rtt min/avg/max/mdev = 15.457/283.288/2083.016/385.093 ms, pipe 3
If I use the installer interface I always get 'cannot connect to the
network'. No matter what I do.
If I'm connected to a network and I'm going into suspend. After I'm
comming out of suspend, I still have internet.
If I'm trying to reconnect after a suspend, It never connects again. It
fails always.
Mofi will mostly work, but when it doesn't work, it brings down the usb0
device with him. So I cannot connect trough the usb anymore. Also 'ifup
eth0' doesn't work anymore.
I hope you can use the information.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:11>
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 elfo):
Thanks, Dolfje.
Please, could you share your router security settings?
I'm going to try wifirouter + WEP128 + FSO milestone3 and post results...
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:12>
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 elfo):
Already tested (WEP 128bit ASCII 54Mbit/s) in FSO milestone 3.
iwconfig eth0 essid XXXX mode managed channel 1 key s:xxxxxxxxxx
ifconfig eth0 192.168.1.123 up
ping 192.168.1.1 (router's ip)
~88% packet loss being at 10cm/1m/3m and it seems to get worse over time.
Does signal strength = 192/94 (or similar values) in iwconfig make any
sense?
I'll try changing WEP key but I'd like to know if there's any way I could
sniff packages using the FR and see what's actually going on between FR
and router
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:13>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#1789: 2008.8 screen blanks and refuses to wakeup
----------------------------------------------------+-----------------------
Reporter: billk | Owner:
openmoko-kernel
Type: defect | Status: new
Priority: highest | Milestone: Om2008.9
Component: System Software | Version: Om2008.8
Severity: major | Resolution:
Keywords: wakeup screen display sleep suspend | Blockedby:
Reproducible: | Blocking:
----------------------------------------------------+-----------------------
Comment(by octavsly):
I just had the same problem with the releases at:
I need to remove the battery :-(
{{{
http://downloads.openmoko.org/releases/Om2008.8-update/
Om2008.8-gta02-20080903.uImage.bin 16-Sep-2008 00:31 1.8M
Om2008.8-gta02-20080916.rootfs.jffs2 16-Sep-2008 00:31 68M
gta02v5_and_up-u-boot.bin 16-Sep-2008 00:31 211K
}}}
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1789#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 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.
A good way is use a laptop with its WLAN network device set to Monitor
Mode on the same channel and tcpdump that, then watch the sequence of
packets and retries.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:15>
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):
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.
A good way is use a laptop with its WLAN network device set to Monitor
Mode on the same channel and tcpdump that, then watch the sequence of
packets and retries.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/1904#comment:15>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
