Hi,
I dropped my FreeRunner one time too many, and the AUX button stopped
working. Opening the case, I found that the switch wasn't in place
anymore; it was moving freely around. Since it's legs are broken, I will
need to get a new one to solder it in. Anyone can tell me what's the
part number I'l
polz writes:
> openmoko10 (or whatever that firmware was called) hasn't fixed the issue for
> me. And no, a software workaround which still drains the battery in less than
> a day IMO is not enough.
Have you actually measured that the workaround draws so much power?
>> > 3. A stable, FSO-based
Happened to me before. Are you sure the switch is broken? Mine was just
loose. The legs are tiny. I used a soldering iron with a very small tip.
Good luck!
Sven
On Sun, 2008-12-14 at 06:50 -0500, Simon Comeau Martel wrote:
> Hi,
>
> I dropped my FreeRunner one time too many, and the AUX button
On Sunday 14 December 2008, arne anka wrote:
> > 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!
>> > 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 worka
2008/12/13 Bobby Martin :
> As much as I hate to chime in on such a busy and unproductive thread...
Yeah, the same here.
> That's my whole reason for posting - to thank Andy, Harald, etc. etc. in the
> OM group, Lorn, etc. of Trolltech, mwester, Julien, quickdev, MarcOChapeau,
> etc. of the commu
On Sunday 14 December 2008 15:40:58 arne anka wrote:
...
> can't confirm that. the battery lasts as long as before -- about 48h,
> maybe more (i never let it run down more than about 35% which is reached
> after almost two days).
I presume you're talking about a gta02, which has a bigger battery. M
I use a FreeRunner (GTA02) with the OM2008 distribution. I turned it off
while it was connected to my desktop PC by pressing the power button for a
short time (the screen slowly faded as usual). The problem is that I have
**not been able to turn it back on** since then. It does absolutely nothing;
i got this issue with 2007.2 back then and with debian now, both with
dropbear and fullblown openssh, so i suppose it's not a distribution
specific one.
after working a while via ssh, suddenly ssh freezes . obviously task
started end, but i can't do anything but killing the ssh client from my
"Alexander Kappner" writes:
> What can I do to bring my FreeRunner back to live?
I am not an expert on hardware stuff but I would remove battery, sd
card and sim card for a while. Then reinsert battery and try to boot
to NOR uboot. If that fails then it really sounds like a bit more
persistent ha
and thus no point to start from searching a resolution.
>
> any hints?
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
> ______ Information from ESET NOD32 Antivirus, version of virus
> signature database 3690
"arne anka" writes:
> host computer (which is not the easiest since it's hard to distinguish
> which of the different clients it is).
RET ~ .
will kill your client (see man ssh for escape sequences).
___
support mailing list
support@lists.openmoko.o
hi,
i think the built-in microphone of my moko died!
i am usually running a customized FSO on my moko, but at sometime in the
last weeks the microphone built into it stopped working. (it was working
fine before)
i have no clue what caused this.
i can make and receive calls, hear the other side b
gt;
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>
> __ Information from ESET NOD32 Antivirus, version of virus
> signature datab
2008/12/14 Timo Juhani Lindfors
> "Alexander Kappner" writes:
> > What can I do to bring my FreeRunner back to live?
>
> I am not an expert on hardware stuff but I would remove battery, sd
> card and sim card for a while. Then reinsert battery and try to boot
> to NOR uboot. If that fails then i
2008/12/14 arne anka
> i got this issue with 2007.2 back then and with debian now, both with
> dropbear and fullblown openssh, so i suppose it's not a distribution
> specific one.
> after working a while via ssh, suddenly ssh freezes . obviously task
> started end, but i can't do anything but kil
> 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
I wonder what the 1157 means. Looking thru earlier logfiles, it happened
once for Dec 1, 3 and 4, 3 times for Dec 10, 5 times for Dec 14 and just
once some minutes ago for Dec 15. Needless to say that
FilesystemSize Used Available Use% Mounted on
rootfs 246.6M
2008/12/14 arne anka
> > 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,
>>> There are still hardware problems that exist with almost every
>>> freerunner out there (GPS signal levels, for one). I would like to
>>> see them fixed by Openmoko, Inc.
> The kernel fix for GPS is a mere quirk. Ideally it should get fixed in
> hardware.
Huh? The kernel fix seems to work OK
I noticed this as of today in SHR, but it must be evident for all Angstroem
based distributions: in /etc/init.d/rc in function startup there is a case:
when the script to be called ends with "*.sh" then it is sourced instead of
called - with fantastic results when the script contains an "exit"
stat
2008/12/14 Joachim Ott :
> I wonder what the 1157 means. Looking thru earlier logfiles, it happened
> once for Dec 1, 3 and 4, 3 times for Dec 10, 5 times for Dec 14 and just
> once some minutes ago for Dec 15. Needless to say that
>
> FilesystemSize Used Available Use% Mounted
I have been thinking about the possible causes for the echo bug. I
have a feeling that it's actually feedback and not an echo. I think
what's happening is the sound is being picked up by the mic and being
sent to the remote phone for an extra round of fun.
Does anyone know how I would start test
On Fri, Dec 12, 2008 at 5:08 PM, arne anka wrote:
> by actually _READING_ mails for starters!
> the misunderstanding with the term gta03 has been corrected several times
> already!
> if you refuse to check archives and to read mails and instead insist on
> perpetuating your misstatement, nobody ca
On Mon, Dec 15, 2008 at 5:35 AM, Stefan Monnier
wrote:
There are still hardware problems that exist with almost every
freerunner out there (GPS signal levels, for one). I would like to
see them fixed by Openmoko, Inc.
>> The kernel fix for GPS is a mere quirk. Ideally it should get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Karthik-
>>> hardware.
>> Huh? The kernel fix seems to work OK for those people who have old
>> FRs. Newer FRs have a hardware fix. E.g. my FR doesn't need any
>> kernel workaround. No need to wait for GTA03 to get a hardware fix.
>
> So, this
Is the echo still an issue when people are using the earbud headphone/mics
that come with the phone?
On Mon, Dec 15, 2008 at 12:15 AM, Paul wrote:
> I have been thinking about the possible causes for the echo bug. I
> have a feeling that it's actually feedback and not an echo. I think
> wha
On Mon, Dec 15, 2008 at 1:32 AM, Lon Lentz wrote:
>
> Is the echo still an issue when people are using the earbud headphone/mics
> that come with the phone?
>
That is an excellent point. I do not believe the earbuds work on mine
(Om2008.9), I tried it a while back. How do I get this working?
28 matches
Mail list logo
