Broken AUX button; Finding a replacement switch
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'll need, and where I could get it? Thanks -- Simon Comeau Martel si...@comeau.info https://comeau.info ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
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 distribution > ... >> there was just recently a mail from om lining out the development in this >> respect. > I must have missed it. To find it, what should I be googling for ? > On a related note, the latest FSO in debian (apt-get update; apt-get upgrade > about an hour ago) never asks me for a PIN. Who should I report this to, > which logs should I attach? 1) make sure frameworkd.conf has [ogsmd] # GTA02 has TI Calypso modemtype = ti_calypso ti_calypso_deep_sleep = never log_level = DEBUG 2) start frameworkd from terminal with something like script -c 'sudo frameworkd' frameworkd.log 3) start whatever phone program you use 4) send frameworkd.log to trac.freesmartphone.org in a bug report if it still does not ask for pin and report output of dpkg -l | grep fso dpkg -l zhone ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Broken AUX button; Finding a replacement switch
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 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'll need, and where I could get it? > > Thanks > --- Sven Kreiss personal: http://www.svenkreiss.com e-Mail: s...@videoschalter.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
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! > > does the relased firmware not apply? The moko10 firmware was intended to fix #666 and appears to have been successful according to the majority of reports. It did not, and was not expected to, do anything about #1024. That is being worked on for the next firmware release. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
>> > 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 which still drains the battery in less > than a day IMO is not enough. 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). >> > 3. A stable, FSO-based distribution > ... >> there was just recently a mail from om lining out the development in >> this >> respect. > I must have missed it. To find it, what should I be googling for ? well, mails wolfgang spraul of the last week, i think. should be in the thread about the disbanded optimization team. > On a related note, the latest FSO in debian (apt-get update; apt-get > upgrade > about an hour ago) never asks me for a PIN. Who should I report this to, > which logs should I attach? seems to be an issue for the smartphone lists, rather. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
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 community. +1. And the recent work with kernel 2.6.28 with regards to putting development back to upstream and co-working seems fabulous. I do think the communication and the social aspects of Openmoko community should still be improved, and are partially responsible for the portion of owners feeling frustrated (though there is always some percentage in even a perfect community), but such stuff is almost impossible to discuss in this thread. Managing hardware and software is hard, but so is managing people. Actually, everything Openmoko does is very far from easy, but that's the way it has always been for pioneers :) 2008/12/13 Karthik Kumar : > The kernel fix for GPS is a mere quirk. Ideally it should get fixed in > hardware. Like mentioned, you're totally misinformed. The GPS is perfectly fine with the current sw fix, and it's not a quirk. I can imagine how some people might even mix the problems with fix time etc. with hw problems of GPS - it's just that AGPS is not set up out of the box, and neither is GPS state information storage/retrieval. Hardware-wise everything is anyway ok, and I use AGPS to get good fixes in 10-20s from turning the GPS on. -Timo ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
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. My ?phone? is a gta01 and I've never had it last a whole day without recharging. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
FreeRunner does not boot although battery o.k.
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; the screen remains black and no LEDs light up (not even the LCD backlight). I connected it to the wall charger, tried to reboot it (both in NOR and in NAND mode) and even removed the battery, left the device for a few seconds and then put it back in. The battery is not discharged, a volt-meter shows me that its voltage is 4.16V (well above its nominal voltage of 3.7V). What can I do to bring my FreeRunner back to live? The last thing I did was establishing the Ethernet-over-USB connection; my phone behaved absolutely normal until I turned it off. [Great phone btw] Best regards Alexander ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
ssh dying constantly
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 host computer (which is not the easiest since it's hard to distinguish which of the different clients it is). it happens frequently when doing opkg (with 2007) or dpkg/apt taks, eg while updating the percent counter suddenly stops and that's it. i do not have the slightest idea what may cause that annoying behaviour 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
Re: FreeRunner does not boot although battery o.k.
"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 hardware issue and might need to find somebody with the debug board to start figuring out what is going on. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: ssh dying constantly
Have you tried different interfaces (WLAN, Ethernet-over-USB...)? If so, does the problem occur regardless of the interface in question? If not, which interface are you using right now? Of course, you can always use the nohup command to prevent apt from dying with the ssh connection. Best regards Alexander - Original Message - From: "arne anka" To: Sent: Sunday, December 14, 2008 7:00 PM Subject: ssh dying constantly >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 > host computer (which is not the easiest since it's hard to distinguish > which of the different clients it is). > > it happens frequently when doing opkg (with 2007) or dpkg/apt taks, eg > while updating the percent counter suddenly stops and that's it. > > i do not have the slightest idea what may cause that annoying behaviour > 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 (20081214) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: ssh dying constantly
"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.org https://lists.openmoko.org/mailman/listinfo/support
built-in mic broken?
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 but no one can hear me. this weekend i tried to get it working again. i tried many alsa-mixer-configurations and everything seems to work as expected (headset mic, headset speakers, both handset speakers, pcm out ...) except the built-in microphone (alsa mic2 right?)! to ensure that it is not a configuration problem i today reflashed my moko with these distributions (rootfs + matching kernel): fdom om2008.9 om2008.4 and tried to make a call. all showing the same problem, no sound from the built in mic to the gsm modem. (the wired headset works perfectly with e.g. om2008.4, and the built-in speaker also works...) now what can i do? this week i will try to contact my distributor (Golden Delicious Computers) and ask them how to proceed. anyone else with such problems? will someone repair my moko? always using the wired headset is not really an option. also all my friends calling me are slowly getting displeased not able to hear me :) flo. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
SOLVED: FreeRunner does not boot although battery o.k.
> 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 hardware issue and might need to find somebody with the > debug board to start figuring out what is going on. Thanks a lot for your advice - **I successfully managed to resurrect my FreeRunner using this method**. You saved me 300 bucks! Nevertheless, the whole thing remains a mystery to me: When I removed the SIM, I noticed that the whole FreeRunner had become heated up - not burning hot, but much warmer than it got during normal use. I'd love to know what exactly went wrong with my phone today. Has anyone had the same problem? Best regards Alexander - Original Message - From: "Timo Juhani Lindfors" To: "Support for Openmoko Device Owners" Sent: Sunday, December 14, 2008 7:17 PM Subject: Re: FreeRunner does not boot although battery o.k. > "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 hardware issue and might need to find somebody with the > debug board to start figuring out what is going on. > > > > ___ > 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 (20081214) __ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: FreeRunner does not boot although battery o.k.
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 it really sounds like a bit more > persistent hardware issue and might need to find somebody with the > debug board to start figuring out what is going on. It's okay to remove the battery for a while. You can remove SIM and SD too if you like, but I'll give you (Timo) one sixpack for every Volt you might find left in the SIM or SD. The first thing I would try a different battery or external power in that case. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: ssh dying constantly
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 killing the ssh client from my > host computer (which is not the easiest since it's hard to distinguish > which of the different clients it is). Try "netstat -tp" (on the host computer) to find the right PID to kill. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: ssh dying constantly
> 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 the fr just froze. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
JFFS2 warning: (1157) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1212
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.6M129.2M117.4M 52% / All this on SHR with Linux version 2.6.24 (s...@opmbuild) (gcc version 4.1.2) #1 PREEMPT Sun Dec 14 18:55:25 CET 2008. Should I take any care of this? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: ssh dying constantly
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, three, ... ssh connections to the fr just > froze. Well, if you have multiple ssh connections and one of them freezes, what prevents you from using one of the remaining sessions to find out, which is the frozen one? The command is very similar to the above. And yes, netstat gives you a very visible hint. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
>>> 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 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. Stefan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
/etc/init.d/rc speedup enhancement
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" statement. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: JFFS2 warning: (1157) jffs2_sum_write_sumnode: Not enough space for summary, padsize = -1212
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 on > rootfs 246.6M129.2M117.4M 52% / > > All this on SHR with Linux version 2.6.24 (s...@opmbuild) (gcc version 4.1.2) > #1 PREEMPT Sun Dec 14 18:55:25 CET 2008. Should I take any care of this? I'm using SHR as well and I noticed this same (or similar) error a day or two ago. It just so happened that I was at that time watching the logs with logread, and when it happened the system froze, the screen went black and I had to take the battery out to revive it. It's possible that those two events were unrelated. Did you notice any problem when you saw that message, or did it seem to be benign? Nathan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Other possible Echo Cause
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 testing this? In particular, I would like to try the following. 1. Disable the mic totally and raise the handset volume. I know the handset volume is set by Control.4 values in gsmhandset.state file. I would make some phone calls and have the remote party talk to see if an echo occurs. If not echo occurs, well then we know the mic is part of the cause. I also know that our telephone systems do not transmit the whole audible frequency range. Is there a way to clip the audio from the mic for phone calls? I think this would translate to reduce/elimination of buzz. Thanks in advance. -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: pointless ranting was: Re: Sad Story
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 can help you! Then this link be updated. http://wiki.openmoko.org/wiki/GTA03 > your shouting at andy's because he refuses to accept your attitude (see > above) is absolutely not helping. If I point out flaws about the focus of Openmoko, then I'm shouting? If I offer suggestions on what objectives the team should be working towards that's the wrong attitude? If I feel Openmoko is heading toward the wrong path, I should just clam up and be a "team player?" Re-read my emails. They are a critique of how things could be better. It's clear, I am far from alone. I have yet to villainize anyone yet. Constructive criticism can only be constructive, if both sides are willing to allow for improvements. -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
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 fixed in >> 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 kernel fix is a feature, according to Al Johnson? Then why do they need a hardware fix? Unless I am missing something, this software fix seems to be a lie. Or the hardware fix seems to be bogus anyway. I have one of the earlier freerunners released, so I'm sure Openmoko owes an explanation. > > >Stefan > > > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
-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 kernel fix is a feature, according to Al Johnson? Then why do > they need a hardware fix? Unless I am missing something, this software > fix seems to be a lie. Or the hardware fix seems to be bogus anyway. I > have one of the earlier freerunners released, so I'm sure Openmoko > owes an explanation. > The detailed explanation already document in wiki http://wiki.openmoko.org/wiki/GPS_Problems Most A6 boards as I knew (some very early stage A6 might not have this rework) came with hardware add capacitor fix for changed factory test process (lower power on relayed factory GPS emitter, and also for better quality control). And, for software fix, as we tested in lab and community helped GPS verification. Software fix good as hardware in most user scenarios. Personally, I also using neo as biking computer without hardware fix, and performance is acceptable as hardware fixed device (40 seconds to 2 or 3 minutes). If you really un-comfortable with your current neo status, please go support.openmoko.com and create ticket for this issue, we could help you there. Thanks, - -- Neng-Yu Tu (Tony Tu) Openmoko, Inc. Support. Some questions could be answered by reference following link: Wiki - http://wiki.openmoko.org Download - http://downloads.openmoko.org Community - http://lists.openmoko.org/nabble.html Freerunner Introduction - http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAklF+EgACgkQmV6sZhhBn2+YYwCYyYRYsUR5C6qgfVYg7/1OiZ7P 4QCdGpz6WP+x5v5mD5qJLQlW90g6FyI= =FfG/ -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Other possible Echo Cause
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 > 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 testing this? In particular, I > would like to try the following. > > 1. Disable the mic totally and raise the handset volume. I know the > handset volume is set by Control.4 values in gsmhandset.state file. I > would make some phone calls and have the remote party talk to see if > an echo occurs. If not echo occurs, well then we know the mic is part > of the cause. > > I also know that our telephone systems do not transmit the whole > audible frequency range. Is there a way to clip the audio from the > mic for phone calls? I think this would translate to > reduce/elimination of buzz. > > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Other possible Echo Cause
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? -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
