well, there's probably a lot of people finding _your_ message both
unneccessary and offensive!
- you hijackd a thread completely unrelated to vent your individual
frustration insdtead of respecting the request of the op
- you tried to force your personal opinion about the state of om on
so far your descriptions are not really helpful.
you see the openmoko logo but then nothing happens?
then there's neither a problem with the display nor the backlight, but
with your X.
please describe _exactly_ what happens from powering on the freerunner
until the moment the problem occurs
Now even I am not able to ssh on FR via my laptop. So I can not run any
of the command on FR.
remove the battery, wait a few minutes, put it back in and restart.
what happens?
___
support mailing list
support@lists.openmoko.org
http://catb.org/esr/faqs/smart-questions.html
isn't there an equivalent for smart answers?
most of the 12 mails were caused by people just throwing in their 2c w/o
requesting further information.
___
support mailing list
support@lists.openmoko.org
from your description, it could be the connector or cable connecting
display and board.
you could try to open the fr and check, if the connector still sits firmly.
btw: i guess it's better to write to commun...@om, no idea how many people
still read supp...@om.
Thanks for your thoughts. The problem with using Qi is that it can only
go into NAND which still means you have to push the Aux button when you
boot (and a 2nd time if there are file check errors).
huh? where did you get that from?
qi tries to boot all sd partitions and falls back to nand if
after few tries zhone eventually starts working.
known issue.
maybe related to dbus timeouts, very likely related to fso needing some
time to settle after start.
neil jerram posted recently a few patches to remedy that at least in zhone
(running through a loop until successful), somewhat
i still have 1 qustion how can i write files to FR throw the ssh
what are the commands?
tnx again for your time
please, always quote only the really necessary parts!
as for writing files: depends on your definition of writing.
once you are via ssh on the fr, you can use vim, nano, emacs,
ifdown usb0
ifconfig usb0 192.168.0.202 netmask 255.255.255.0 up
route add -host 192.168.0.202 dev usb0
for ubuntu, prefix every line with sudo.
the wiki page lists _all_ of the above!
http://wiki.openmoko.org/wiki/USB_Networking
please a) read the wiki and b) post useful and complete error
eth0 Link encap:Ethernet HWaddr 00:14:2a:a9:4d:fb
inet addr:192.168.0.200 Bcast:192.168.0.255
here's something wrong already.
a) eth0 should not have address 192.168.0.200 (for the purpose of easy
access to the fr, that is) and
b) specifically not, when everything is
tbh, i never really was happy mit nm or any intelligent automatism
trying to manage the connection to the fr.
nm usually is overcharged with the concept of _multiple_ network
interfaces being up and connected at the sam time and produces spretty
much a mess.
your best bet is to handle it by
On Fri, 20 Nov 2009 11:23:01 +0100, Iurii y...@reverseenterprises.com
wrote:
Davide wrote:
On Friday 20 November 2009 10:34:25 Iurii wrote:
Then:
ssh 192.168.0.200
ssh: connect to host 192.168.0.200 port 22: Connection refused
You're trying to ssh your own machine.
Default FR IP is
well, let's start with the output of
netstat -rn
and then, check, if ssh is running at all on the freerunner -- i can't
imagine the fr to be without a terminal emulator, even out of the box.
last, but not least, check your firewall etc.
___
support
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
192.168.0.202 0.0.0.0 255.255.255.255 UH0 0 0
usb0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0
usb0
where does that come from?
if your debian really is up to date, your frameworkd.conf isn't.
your description matches an issue i had with gsmwhatevermuxer instead of
fso-abyss. it might as well be related to using the deprecated ousaged
instead of the newer fso-usaged (both still the default afaik if not set
otherwise
an answer, so don't rely on anything you see here.
From http://en.wikipedia.org/wiki/MP3#Licensing_and_patent_issues
well, wikipedia is neither a trustworthy source, particularly with such an
issue.
the source refered to ([42]) does not cite any kind of reliable
information, it only
there are two possible explanations:
- you have to push in the headphone plug harder to actually connect --
hearing only in one earphone usually is a sign for that
- you needt to plug in _after_ establishing the call. not sure, how a) shr
handles that and b) if fso did fix it -- but with
On Wed, 12 Aug 2009 09:09:25 +0200, Tim Sterk t...@tim-sterk.nl wrote:
I've tried the image which is on the website:
http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz
I've put it on my MicroSD card using the following instructions found
on
the openmoko
r...@om-gta02 ~ $ fdisk /dev/mmcblk0
Unable to open /dev/mmcblk0
The same just hit me when I installed SHR-U on my sd card (8gb
kingston). It
worked for a little while, and then I started getting I/O errors.
Any hints on how to fix the partition table on the card, and what to do
to
Thanks for your help,
any chance, you'd tell us, _what_ you do exactly?
from your description it is rather hard to infer your steps.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
I've tried on different computersystems (all ubuntu 9.04).
Tried using different MicroSD card.
Tried different flash images and different distributions.
and i guess, you tried to tell us something?
what in exactly didn't you understand?
if you really want help, make it possible to help you by
No flaming needed, this is the SUPPORT list. You know, newbies welcome?
which means: newbie == unable to read?
if you call requesting _usefull_ information instead of it does not work
flaming, so be it.
___
support mailing list
I've tried the image which is on the website:
http://people.openmoko.org/joerg/calypso_moko_FW/moko11/flash-moko11_uSD-image.tar.gz
I've put it on my MicroSD card using the following instructions found on
the openmoko site:
sudo dd if=flash-moko11-2.image of=/dev/mmcblk0
- did you try to
I think it's the original bootloader.
my shot in the dark would be, you've been bitten by the old sd-clock bug
(or whatever the official name is -- has been too long since).
afaik it has been fixed long ago, but who knows what may have triggered it
again? wouldn't hurt, at least, to check.
I can't access my SD card.
kernel, distribution, bootloader, bootloader version?
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
2009? isn't it fso based?
auto suspend should be triggered by a rule in
/etc/freesmartphone/oevents/rules.yaml
i guess.
you would then need to disable that rule and either try
mdbus -s org.freesmartphone.oeventsd /org/freesmartphone/Events
org.freesmartphone.Events.ReloadRules
or restart fso.
Sorry, I should have mentioned that I have 2008.8. But plan to
install SHR soon. I am having trouble connecting via ssh in Ubuntu
9.04. Not sure what the problems is. Things worked flawlessly in
Ubuntu 8.04.
you don't need ssh to install 2009. just get the image and flash.
i don't think,
Okay, I don't have the wall charger
What may work is this:
- press and hold AUX
- insert USB power (from a PC)
- when the menu comes up, select Power off
This should leave the PMU in charging mode.
hey! that's quite interesting. could someone put that into the wiki,
probably on some
off. I'm waiting on a new wall charger; if that doesn't work, I'll
just get another battery.
simply usb is still sufficient, only it takes longer.
plug in, let it alone for the night and boot up next day.
___
support mailing list
i say, the battery is flat -- your symptoms perfectly match.
plug in the wallcharger, let it sit for a while (1h at least) and try
again.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
have you got wicd installed? it's a replacement for the endlessly
sucky network-manager (or something like that). it's a drop-in, no
need to change any config, but it makes things so much easier, and
it's in the ubuntu repos. i'd recommend that, and then come back if
things aren't fixed. even
- to bood from the SD in QT, but it is failing also (trying to mount
/var/something ) and stops
you could mount the sd card in your pc and modify the fstab of qt, to
mount only from sd.
besides that, i would have expected it to mount /var ... to tmpfs, not
nand (or any physical storage
I've still seen varying opinions on these mailing lists ranging from
'only
5% of people need the buzz fix' to 'everyone with an A5 or A6 needs the
buzz
fix'.
they're not really varying -- it's like learning to swim: if you are
absolutely sure, you'll never get into deep water, there's
it seems that this path doesn't exist
check that gps chip is online (echo 1
/sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron)
the file neo1973-pm-gps.0 does not exist and cannot be created.
find /sys -name \*gps\*
When I start tango gps it says gps not
freerunner, they're not optimized at all. Period.
that's certainly true -- but if you write your app for a commonly used
desktop pc it is rather a matter of effort/result relationship how much
energy one spends on optimization.
the estimated improvements are probably not worth mentioning, so
Sure. I would only like to use it to track commitment. Because I don't
want to buy the phone all by my self.
i don't know how cofundos works (needs some kind of registration probably,
which i am averse to), so no way i would register commitment there.
but when the share falls below 100€ i am
Hehe, do you want to imply that the FR will gain more horsepower over
not necessarily, it's an equation with two terms.
since the fr is not likely to change in that respect, navit in turn may --
and to be honest, i certainly hope it will, so far it is unusable as
navigation app on the fr and
Don't ask me what to do, I'm not a computer scientist. But I'm sure it
would be possible.
well, maybe we all should chip in and give the navit author a freerunner,
to spur his motivation :-)
___
support mailing list
support@lists.openmoko.org
First of all, I didn't succeed to make Wifi to work.
wouldn't that mean, it _is_ invulnerable? *scnr*
ok, first of all, please prefix the subjects of your mails _always_ with
the distribution concerned ([debian], [2008.x], [2009.x], ...).
secondly:
- what distribution are you using?
- what
a lot of searching later ...
a) python is mostly broken -- as far as i can see, every python apps
missed modules and is unable to import them.
seems i can work around that by setting
PYTHONPATH=/usr/lib/pymodules/python2.5/:/usr/lib/pymodules/python2.5/gtk-2.0
but i am not sure if i catch
hi,
yesterday i rebooted the fr again after several weeks and it immediately
turned out to be the wrong thing.
system is an up-to-date debain/unstable, most notably
- python2.5 2.5.4-1
- fso-frameworkd 0.8.4.9-20090130-3
Package: xserver-xorg
Version: 1:7.4+1
--
Package: xserver-xorg-core
Yes, and nothing happened.
Then I tried to double-tap on the assembled digits, and that
worked...
good lord, what usabilty genius created that?
to begin with, everybody aroudnyou can read your pin and then, you stay
there and tap the screen in the faint hope it might work somehow?
and, just
ah, i think i understand -- it's textfield for the pin and the standard
(predictive) keyboard.
well, i don't thinkl that's a good team. passowrd and pin shoudl then have
their own keyboards.
___
support mailing list
support@lists.openmoko.org
of the pool. I put my phone (plus stand alone charger, gps antenna, 4G
card w/ reader spare battery) up on Ebay shortly after my group
mailing a couple months ago.
so, what are you doing here anyway?
___
support mailing list
external in-ear head set that also features a microphone be a good
thing to have for this device.
afaik the package included a wired headset too.
I mean, there is already a 2.5mm socket
for an ear phone, but I know neither of such a head set (although there
should be some in the market),
afaik the package included a wired headset too.
mine didn't, and afaik, the offered headset does not include a
microphone.
the included has, see below.
resellers of the fr do imo offer the matching headset.
... w/o a microphone.
_with_ microphone, that's why it is called head_set_ not
- configure zhone to write to a log file (see the first lines of
/usr/bin/zhone or the archives)
- look at X.org.log
- look at ~/.xsession-errors
do you experience similar issues with other apps too?
___
support mailing list
just noticed that somehow my locales are gone.
when trying to recreate them, locale.gen ends up with
Generating locales (this might take a while)...
en_DK.UTF-8...cannot map archive header: Invalid argument
done
en_US.UTF-8...cannot map archive header: Invalid argument
done
Generation
Juan Lucas Dominguez Rubio jldoming...@prodevelop.es wrote:
please! do _NOT_ crosspost!
keep your postings to _ONE_ list only!
and those who answer: please, have a look at the reply-addresses and
remove unnecessary addresses.
___
support mailing
any chance you keep that on the support list only?
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
ACCESS has published an emulator, running palmos apps.
one of the bigger companies licensed it and distribute it with their
smartphones/tablets -- i am not sure, but it might be nokia and maemo.
anyway, i asked w long time ago if access is going to make that thing
avalibale to other linux
Does hwclock also show the correct date?
hwclock otoh shows the correct
time.
Which kernel version are you
running?
2.6.28-20090105.git69b2aa26
At least the andy-tracking branch suffers from this bug:
i don't think it is the same bug.
i repeat again:
- hwclock always shows correct
when i resume the fr, the time zhone shows (and the date command) is the
one when the fr suspended (ie, suspending the fr at 16:43 and resuming at
20:14, zhone and date bot show 16:43) -- hwclock otoh shows the correct
time.
i experienced it sometimes before, but the last two days it
Something along these lines should work:
- boot into NOR
- connect to the u-boot console on ttyACM*
- dynpart
- dynenv set u-boot_env
- saveenv
- try to boot from NAND. If this doesn't work, boot again from NOR
and DFU a new u-boot, then boot from NAND again
- DFU kernel and rootfs
It seems that it takes a long long while to mount the jffs2 partition
you have. The first thing CPU 0 stall is just a comment that you seem
to be stuck for two minutes, then the second thing is a diagnostic
talking about what you are stuck on. It seems you are stuck on mounting
the jffs2
Dunno what you can do about it, but the guy who owns the process for
generating the jffs2 image for Debian may get a hint from this to change
how he generates it. jffs2 mount should be a few seconds not 120.
oh, that's no flashed image or so.
it is the jiffs the fr came with. months ago i
Maybe, but the actual error here is to do with the format of the jffs2
partition. It can be broken in kernel but I think we would have heard
about it before, 2.6.28 is old now in kernel terms.
well, so the best i can do is backup my data and recreate/reformat the
jiffs2 fs in flash -- with
CHK include/linux/version.h
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `echo 2.6.29-GTA02_(no-mokodev
at a first glance. i'd say, the ( in the echo has to be escaped:
`echo 2.6.29-GTA02_\(no-mokodev
but i don't know how the line continues ...
since opp 0.9-1 of debian does not work correctly with the current
available framework i downloaded panel-plugin-20090212_src.tar.bz2 and
built my own deb.
opp works again well so far, but i notice that at least the settings for
vibration at activation are ignored.
i just unchecked every
I'm using the FSO distro.
Unfortunately the file unsolicited.py (which the link suggests to be
edited) does not exist on my OM.
In the tree
/usr/lib/python2.5/site-packages/framework/subsystems/ogsmd/modems/ti_calypso/unsolicited.py
I get as far as /usr/lib/python2.5/site-packages but then
the state files should be identical for all distributions -- fetch either
an opkg or a deb and extract them.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
eth0:avah Link encap:Ethernet HWaddr 00:12:CF:8F:33:91
inet addr:169.254.6.255 Bcast:169.254.255.255
It seems to look like it's connected
nope. it's not.
the ip address shown is a generic one, assigned by avahi in absence of a
real one.
i don't know, what you did to obtain an
What about eth0?
inet6 addr: fe80::212:cfff:fe8f:3391/64
same thing basically, though probably not assigned by avahi but something
random (do you use ipv6 at home? does the fr kernel support ipv6 at all?)
___
support mailing list
I couldn't find any either so I built my own with
http://iki.fi/lindi/openmoko/navit.txt
well, at least the conversion to debian structure is an unnecessary step
-- the navit page links to two repos holding navit (for x86, though) with
diff/dsc/orig.tar.gz.
you need to modify the configure
you're a better man, than i am, gunga din!
i'd say it fits he aux button contact.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
i inserted
allow send_requested_reply=true send_type=method_call/
into /etc/dbus-1/system.conf as proposed in the zhone/gsm/dbus thread and
now it works again. any hints what exactly is happening?
this dbus rights management is far to complex for me ...
I suggest you (and everyone not using root)
* copy (not move)
/etc/dbus-1/system.d/frameworkd.conf
to
/etc/dbus-1/system.d/my-frameworkd.conf
* remove every line that talks about allow own...
* change user=root to your user in every case.
forgot to mention, i did that already but
wolfgang,
could you put that in the wiki, together with the statements regarding the
buzz fix, for further reference? (Allegations, Accusations and Rumors or
so)
it would help a lot to stop needless complaints jamming the lists ...
___
support
two things:
- what about those maemo guys? don't they create something like that
already? besides the gui the relevant parts should be in some kind of
library which should ne portable, shouldn't it?
- re evolution: the same thing applies. shouldn't be the relevant parts in
a library and thus
About QT Extended. Anyone experiencing the Echo Bug?
Is there a resolution to it without turning down the volume?
well, it's not a battery related question anymore ...
anyway. there have been postings over time and one just recently, taht
several people incorporated the nedded at commands
with debian/fso when using suspend i get usually 48 to 72 hours standby
time (but i very seldom make or receive calls).
anyway, even qtopia should have suspend, or am i wrong here?
___
support mailing list
support@lists.openmoko.org
Any progress/information on this? It's still an issue here...
did you check the state file currently used when this occurs?
i would imagine that simply the state change mechanism failed -- but also
it could be that sound itself broke down ...
___
Does someone know of any large X-font, large enough to be readable on
the neo 300 dpi screen?
???
nowadays fonts are ususally scalable.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
here it is.
the code looks for addressbook.vcf in the user's $HOME and reads it in.
multiple numbers per contact are supported.
in /usr/bin/zhone search for
class pyphone_contacts(edje_group):
and find some lines below
def prepare( self ):
and modify like below (be aware of unintentional
can anyone explain if there is a way to connect to a wifi point that
uses a web-based username and password, without using my browser?
wget?
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
look for ding.
it's the same database as
http://dict.tu-chemnitz.de/
and works either as cli program or with a simple x interface, i wouldn't
be surprised if it is in ångström already.
if not, it is available in debian.
___
support mailing list
The only thing that prevents me of using FSO is the import of phone
numbers. I
couldn't found a hint on how to import a vcf file.
so far there's no pim implemented -- zhone only reads from sim.
but it is really simple to patch zhone accordingly.
search the archives, i think i posted a patch
i too have stability issues with the ssh connection.
i had them with dropbear (2007.2 and debian) really bad, and still have
them with standard sshd on the fr, though far less frequent.
mostly i experience it when doing apt-operations which take a bit longer,
so i somehow suspect a timeout
Here is the story. (Not to repeat!)
well, to rub salt in it ...
are you sure, mtd0 was the right device file to write to?
the kernel-ipk has a postinst script, that before flashing the new kernel
checks for the right device -- the same way allows for seeing what the
other devices are for (i
not in there by default. As it's fundamental to a working phone it should
be. And from the threads I;ve found it doesn't actually help everyone.
because the echo has many sources, the hw is only one -- the other is your
location. even with my old phone i had echos sometimes which had to be
anything but person who calls me hear everything. What is strange: after
dialing a number I can hear dialing tone - but when the call is answered
the sound disappears.
the moment the call is answered the alsa state file changes, so you most
likely corrupted the gsmhandset.state file
if you refuse to check archives and to read mails and instead insist on
perpetuating your misstatement, nobody can help you!
Then this link be updated. http://wiki.openmoko.org/wiki/GTA03
i give up.
you are deliberatly confusing things just to prove your point, imo.
eot for me.
Karthik:
I think I probably speak for a reasonable portion of the community when
I say this:
Go buy an iphone. Put your FreeRunner on ebay. You'll like the iphone -
+1
___
support mailing list
support@lists.openmoko.org
1. Recamping issue - http://docs.openmoko.org/trac/ticket/1024.
does the relased firmware not apply?
openmoko10 (or whatever that firmware was called) hasn't fixed the issue
for me.
seems, i confused the issues the fw should fix, not #1024 but #666.
And no, a software workaround
Try netstat -tp (on the host computer) to find the right PID to kill.
i have several ssh connections to the fr open -- just because they so
prone to freeze.
netstat does not give more information than ps. it's near to impossible to
determine which of the two, three, ... ssh connections to
1. Recamping issue - http://docs.openmoko.org/trac/ticket/1024.
I know it's hard and I presume people from TI aren't being helpful since
solving this issue isn't going to be very profitable for them. Still,
please,
someone solve this!
does the relased firmware not apply?
3. A stable,
A quick thought...if Openmoko feels the hardware of GTA02 is inadequate
to
even bother making it a stable phone, should there not be some sort of
what is so hard in actually reading answers instead of repeating the same
wrong statement over an dover?
it has been stated several times
I don't think a user can flash GSM firmware, only OM, due to NDA on the
Calypso.
yes, you can.
om perepared an image you put on sd and boot from, then the firmware will
be upgraded.
search the archives and the wiki for links and howto.
___
support
did you check if all contacts of the sim are connected? (yes, it used to
work before, i know)
I'm sorry, I don't understand the question. Connected to what?
to the contacts of the fr sim slot.
if i remember right, the fr's contacts are just some kind of springs which
might very well loose
what distribution?
please prefix the subject accordingly!
2008.12.10 08:11:10 ogpsdDEBUGDiscarded data not UBX
indicates that it uses fso -- and your bug is
http://trac.freesmartphone.org/ticket/265
for me, it helped to purge every fso-package (save modified configs like
cu: creat (/var/lock/TMP000e75): Permission denied
have a look at /var/lock/ -- anything unusual?
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
What is this still a 2.6.24 based kernel?
debian-gta02 2.6.24-20081103.git7172ec57
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
This is interrupted erase or flash action caused by the reset I think...
normally JFFS2 seems to either recover them itself or there is minimal
corruption of filesystem.
The freeze can be to do with garbage collection for jffs2 but could be
unrelated altogether.
anything i can do about it?
tar cf - --one-file-system / | cat /dev/null
did at least not fail :-)
tar -cPf /dev/null --one-file-system /
took slightly longer (giving the impression that actually something
happened ;-)
didn't see the message again so far ...
___
support
I would like to get GPS fix faster with debian on freerunner. From
files fetched by mokomakefile I found two things that mention agps:
i may be wrong -- but isn't agps done in frameworkd already? at least i
got the impression by browsing the logs due to the recent gps issue ...
please prefix any posting with the appropriate distribution (ie 2007.2,
2008.9, FDOM, Debian, FSo)!
To turn on FR after it gets suspended I just need to press the Power
button on the right side of the phone.
Am I right?
depends on the distribution used.
Cause sometimes it just stays
I'm using om2008.9.
But I've left the bootloader as it was from the very begining.
Don't think it can affect anything though.
oh, it pretty well can. in fact, it's one of the most important things
with suspend/resume.
there was a lot of changes to u-boot, not at least in respect to issues
Maybe it will fix all my GPS and WiFi troubles. =)
warning: it will not help with trouble with your
boss/wife/husband/girlfriend/boyfriend!
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
i noticed the issue occasionally, but never that extreme:
sunday night (at about midnight) the battery was at about 53%, thus i
plugged in the wallcharger.
at about 8:30 the led was blue and the battery at about 83%, re-plugged
the charger. when i left home it was at 99%, discharging. i
It wasn't the first time I had this issue, so I just took out the battery
and put it back in it's place.
leave the phone w/o battery for a while. i think, i recall something about
taking time to fully empty (and thus reset) internal parts.
___
1 - 100 of 216 matches
Mail list logo
