Re: [Shr-User] Quick e-mail poll: Still using your Freerunner?
On Tue, 2009-12-29 at 22:30 +0200, Risto H. Kurppa wrote: Do you use FR as your daily/primary phone? Yes, lately with great satisfaction. Do you use FR as your primary PDA? No, an N800 (which I owned way before my FR). What distribution you run most of the time? SHR-testing (the revived one, ;-) If you don't use FR as your daily phone/PDA, what phone did you change over to, and why? Thank you :) r I'm looking forward to the results! David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unknown boot options
On Sun, 2009-08-30 at 12:44 +0400, Paul Fertser wrote: David Fokkema dfokk...@ileos.nl writes: Qi reads factory partition to make ethernet gadget use fixed predefined MAC address. If g_ether is statically compiled in there's no way to set MAC address other than supplying it through the kernel command line. If g_ether is a module, the recent modprobe will look at the kernel command line and load the module with corresponding parameters. I guess Qi should support both modular and compiled in g_ether, hence it has use the kernel command line. To sum up, i don't know the answer how to hide those messages but at least now you know why they appear. :) So... either the FR kernels might include g_ether statically compiled or Isn't really a solution because most users might want to use another usb gadget by rmmoding g_ether. Probably unbinding will work too, needs checking, in this case we can compile g_ether statically but it'd still be a bad surprise for users who are not used to that. Ah, I see. So it must be a module, then. someone might fix the 'unknown command line' logger to be silent on 'g_ether' warnings? I can't see how that is possible. That's a shame... I really dislike the warnings as well... David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unknown boot options
On Thu, 2009-08-27 at 11:30 +0400, Paul Fertser wrote: Leonti Bielski prishe...@gmail.com writes: Unknown boot option 'g_ether.dev_addr=MAC' 4 times in a row. It does not affect anything but I hate to see error messages when my loglevel=1 quiet and my device is perfectly fine. It happens to me every time using Qi and I don't know how to make it stop. Qi reads factory partition to make ethernet gadget use fixed predefined MAC address. If g_ether is statically compiled in there's no way to set MAC address other than supplying it through the kernel command line. If g_ether is a module, the recent modprobe will look at the kernel command line and load the module with corresponding parameters. I guess Qi should support both modular and compiled in g_ether, hence it has use the kernel command line. To sum up, i don't know the answer how to hide those messages but at least now you know why they appear. :) So... either the FR kernels might include g_ether statically compiled or someone might fix the 'unknown command line' logger to be silent on 'g_ether' warnings? David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-u] Abyss or gsm0710muxd? (Was: Re: [SHR] opkg upgrade (10 Aug 2009))
On Wed, 2009-08-12 at 13:56 -0400, D. Gassen wrote: I had the same problem but I solved that (for me) by reinstalling a couple of packages: opkg install -force-reinstall libgsm0710mux0 libfsotransport0 \ libfsoframework0 libfsobasics0 fso-abyss fsousaged \ libgsm0710mux-config frameworkd frameworkd-config-shr \ libframeworkd-phonegui-efl0 \ shr-contacts shr-messages shr-dialer ophonekitd (I hope I got them all, I didn't use one command but several) After that the phone connected properly to the GSM network, was able to read all my contacts and I could make and receive calls again. That's funny. I don't have fso-abyss on my phone. Apparently, it is a new GSM muxer implementation by Mickey to replace fso-gsm0710muxd, which _is_ installed on my phone. I'm running SHR-unstable from July 31st (or a few days before that). Did something change in the latest images? Isn't SHR using nice metapackages to move people to the new daemon on upgrade? Or did you just custom install fso-abyss? David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Thu, 2009-08-13 at 10:34 +0200, arne anka wrote: Especially recommended for WiFi since due to the bugs in the firmware and the driver full power-cycle of the module is often advantageous. i am not quite sure, what to make from that sentence. Maybe s/advantageous/adventurous/ ? As in: cross your fingers, this will probably kill the module? David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: is wifi-driver developed anymore?
On Thu, 2009-08-13 at 16:06 +0400, Paul Fertser wrote: David Fokkema dfokk...@ileos.nl writes: On Thu, 2009-08-13 at 10:34 +0200, arne anka wrote: Especially recommended for WiFi since due to the bugs in the firmware and the driver full power-cycle of the module is often advantageous. i am not quite sure, what to make from that sentence. Maybe s/advantageous/adventurous/ ? As in: cross your fingers, this will probably kill the module? Powercycling the module can't kill it :D Ah, no, you're right, :-P However, IIRC, there were some posts and bug comments somewhere that show that unloading/reloading the module can cause severe breakage and render wifi unusable. David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Mon, 2009-08-10 at 20:06 +0400, Paul Fertser wrote: David Fokkema dfokk...@ileos.nl writes: On Sat, 2009-08-08 at 15:05 +0400, Paul Fertser wrote: David Fokkema dfokk...@ileos.nl writes: The fact that Freerunners differ in audio quality and settings has been stated on this list and on support. And going by the last paragraph, this is true. So, _why_ are Freerunners different? One of the problems is that some freerunner revisions are in fact different in hardware. Most devices have 1uF capacitors instead of R3004/R3005 (which should be 0R), and that's not a joke. That is 0R's are placeholders for possible future modifications, right? Is the 1uF capacitor deliberately (but mistakenly) inserted or is this a manufacturing bug? The first :( Hmmm... maybe the idea was to improve audio quality by inserting a filter? Too bad it didn't work out that way... Unfortunately, there's no way to find out which devices are affected by this bug judging only by revision and serial number as BOMs were lost due to an incorrect file format conversion, one needs to actually try and see for himself. If I open up my phone (have to do it someday, right?) how can I distinguish a 0R from a 1uF? Unlikely since those caps are under a can and dismounting it requires extra effort and you can damage something doing it. How many cans are there inside a freerunner? I'll have to study the schematics and really have to open this thing. AFAICT A7s are affected while at least some A6s (mine e.g.) not. Hmmm... that's bad. Are there many differences like these? I don't know of anything important except those fake 0Rs and that the bass was a bit improved in A7 (from 1uF to 4.7uF). If you're really that interested, ask Joerg. Maybe I will, yes. Would be nice to have an exhaustive list. Probably this can also be found in the core project. Thanks, David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Mon, 2009-08-10 at 15:53 +0400, Paul Fertser wrote: Alexander Shulgin alex.shul...@gmail.com writes: On Sat, Aug 8, 2009 at 14:05, Paul Fertserfercer...@gmail.com wrote: David Fokkema dfokk...@ileos.nl writes: The fact that Freerunners differ in audio quality and settings has been stated on this list and on support. And going by the last paragraph, this is true. So, _why_ are Freerunners different? One of the problems is that some freerunner revisions are in fact different in hardware. Most devices have 1uF capacitors instead of R3004/R3005 (which should be 0R), and that's not a joke. That is earpiece path and not surprisingly that devices that have those capacitors have considerably lower sound volume from the earpiece. And what do I do if I happen to have one? Tweak alsa state files appropriately. There's a routing diagram on the wiki that explains everything needed. If that doesn't really cut it, is it possible to swap the 1uF for a 0R? Gotta make a list of hardware fixes to perform, ;-) David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Mon, 2009-08-10 at 14:15 +0100, Al Johnson wrote: On Monday 10 August 2009, David Fokkema wrote: On Mon, 2009-08-10 at 15:53 +0400, Paul Fertser wrote: Alexander Shulgin alex.shul...@gmail.com writes: On Sat, Aug 8, 2009 at 14:05, Paul Fertserfercer...@gmail.com wrote: David Fokkema dfokk...@ileos.nl writes: The fact that Freerunners differ in audio quality and settings has been stated on this list and on support. And going by the last paragraph, this is true. So, _why_ are Freerunners different? One of the problems is that some freerunner revisions are in fact different in hardware. Most devices have 1uF capacitors instead of R3004/R3005 (which should be 0R), and that's not a joke. That is earpiece path and not surprisingly that devices that have those capacitors have considerably lower sound volume from the earpiece. And what do I do if I happen to have one? Tweak alsa state files appropriately. There's a routing diagram on the wiki that explains everything needed. If that doesn't really cut it, is it possible to swap the 1uF for a 0R? Gotta make a list of hardware fixes to perform, ;-) If you need to ask you probably can't do it yourself ;-) Schematics and No, I probably can't, :-/ component layout are available, and shorting a cap shouldn't be too hard. The components are small, and not far from the headset coupling caps. See sheet 3 of the component layout under the bottom right corner of U3001. I'm privileged to be working at a national institute which has a pretty advanced electronics lab. I've asked and they're willing to do this for me. They already told me that shortening would be easier than swapping components. However, they do this routinely and if I supply them with schematics and a list of fixes (buzz, bass, recamping, earpiece, etc.) they can probably do all this in one go. Components are already in stock, too, :-) David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Mon, 2009-08-10 at 16:33 +0300, Alexander Shulgin wrote: On Mon, Aug 10, 2009 at 14:53, Paul Fertserfercer...@gmail.com wrote: Alexander Shulgin alex.shul...@gmail.com writes: One of the problems is that some freerunner revisions are in fact different in hardware. Most devices have 1uF capacitors instead of R3004/R3005 (which should be 0R), and that's not a joke. That is earpiece path and not surprisingly that devices that have those capacitors have considerably lower sound volume from the earpiece. And what do I do if I happen to have one? Tweak alsa state files appropriately. There's a routing diagram on the wiki that explains everything needed. I'm quite experienced programmer, but this is just too deep for me (plus the documentation is sparse and decentralized). Could anyone assist me on this task? What exactly to change? Maybe someone already had similar problem and solved it? It would be really nice to see the solution and try it out. Well, if you read the first post in this thread, it tells you two things: 1) Yes, the documentation is too sparse and often self-contradictory 2) Use Angus Ainslie's mixer scripts (see http://lists.openmoko.org/nabble.html#nabble-td1676346) if that doesn't work (it doesn't currently on my phone) use pymixer.py instead of fsomixer.py. An older version, but very functional. When using pymixer.py, first make a call, _then_ run the script and play with the settings. In the OP, you can see what I have done. To maximize earpiece volume, just max out the bottom two settings. In this script, input and output are reversed (just the labels, nothing more). Good luck! David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Sat, 2009-08-08 at 15:05 +0400, Paul Fertser wrote: David Fokkema dfokk...@ileos.nl writes: The fact that Freerunners differ in audio quality and settings has been stated on this list and on support. And going by the last paragraph, this is true. So, _why_ are Freerunners different? One of the problems is that some freerunner revisions are in fact different in hardware. Most devices have 1uF capacitors instead of R3004/R3005 (which should be 0R), and that's not a joke. That is 0R's are placeholders for possible future modifications, right? Is the 1uF capacitor deliberately (but mistakenly) inserted or is this a manufacturing bug? earpiece path and not surprisingly that devices that have those capacitors have considerably lower sound volume from the earpiece. Probably mine has the capacitor, then. I have to max out the earpiece volume but still can hardly understand my wife when I'm outside (in relative quiet). Unfortunately, there's no way to find out which devices are affected by this bug judging only by revision and serial number as BOMs were lost due to an incorrect file format conversion, one needs to actually try and see for himself. If I open up my phone (have to do it someday, right?) how can I distinguish a 0R from a 1uF? AFAICT A7s are affected while at least some A6s (mine e.g.) not. Hmmm... that's bad. Are there many differences like these? Different components in audio paths? Or does it mainly come down to tolerances? Those are actually quite good, aren't they? Or could they really influence audio paths? Thanks for the info! David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Unabel to SSH into Neo Freerunner
On Sat, 2009-08-08 at 20:08 +, Niels Heyvaert wrote: Hi there, So far no luck with getting an SSH connection to the FreeRunner. I've followed the wiki man pages to the letter (http://wiki.openmoko.org/wiki/USB_Networking) as Angus suggests. But this did not change the result. Er... there are a lot of alternatives presented there. You need to be more specific, I'm afraid. Basically these were the same steps I was already doing (except I need to modprobe g_ehter first). You really don't. Really. I mean it. Modprobing g_ether shows up two new usb devices on my machine which are both not my freerunner. I'm using ubuntu 9.04, just like you. I'm still getting the no route to host error. Understandable. Disabling my PC wlan connection does not help. Correct. Any thoughts? I'm pretty sure my previous post (and some other posts as well) pretty much sums it all up: http://lists.openmoko.org/nabble.html#nabble-td3401779|a3402898 If you follow that to the letter, one new interface showed up. That is your freerunner. Good luck! David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unabel to SSH into Neo Freerunner
On Fri, 2009-08-07 at 01:12 +, Niels Heyvaert wrote: Hi, I'm currently having difficulties connecting to the Neo Freerunner (running OM2009) from Ubuntu 9.04. Initially I did not get the usb0 ethernet connection when plugging in the booted device, so I used Correct. Om2009 doesn't use usb0. See http://wiki.openmoko.org/wiki/Usb_networking#So_is_it_.22usb0.22_or_is_it_.22eth1.22.3F If you really want to be sure, do this: Before plugging the FR in: ifconfig -a (this will show _all_ interfaces, even inactive ones) After plugging the FR in: ifconfig -a Now, you should see one additional network interface. Using ubuntu, you don't need to modprobe anything. Since you already know how to manually activate the interface, I'll leave the rest to you, ;-) David (Happily ssh-ing into my FR (Om2009, SHR-u) from ubuntu 9.04) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Freerunner audio channels
Hi list, I finally took a lunch break to check out the various alsa channel settings. Angus's mixer scripts rock, BTW! Trying to track down the input for the handset, I've looked at the wolfson schematic, browsed through the handset state file and can only come to the conclusion that the audio path is completely circumventing the digital filter module. Why is that? We're only using the sidetone path and mixing that as the only channel into the output. The rest is disabled (volumes set to 0 and switches set to False). Reading up on what sidetone actually is (wikipedia) I get the feeling that we're not supposed to do this. Ok, it works, but the sidetone path was never intended for this purpose, I gather, but rather to provide feedback to the speaker's earpiece. I tried to decipher the various wiki pages dealing with audio and the conflicting posts on alsa settings and played with Angus's mixer during a phone call (FR in my one hand, landline with covered up mouth piece in my other) and noticed that setting Mic2 Capture Volume to 0 does _not_ mute the Mic. It _does_, however, enable me to set the Mono Sidetone Playback Volume quite high (6 / 7) as well as the Mono Playback Volume (100 / 127). This post is not intended to start another discussion on 'best' settings, but maybe some of you know the answer to these questions: - Why exactly are FR's different while I've never heard of Nokia users needing to tweak mixer settings. - Why does setting Mic2 Capture Volume to 0 _not_ (almost) mute the mic? - Why do we bypass the digital filters by using the sidetone path? Maybe this information is buried somewhere but I can't unearth it. Thanks! David PS: It seems that I can now use my FR to actually make phone calls, ;-) PPS: If these questions are answered, maybe I'll stick my neck out and delete all conflicting information on the wiki and write a small 'How to set your mixer settings appropriately?' PPPS: I'll not do anything rash, I promise. However, it would be nice to reach some kind of consensus and clean up the wiki. It took me far too much time to tweak my phone to make calls without noise, echo etc. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Fri, 2009-08-07 at 16:29 +0200, Sebastian Krzyszkowiak wrote: On 8/7/09, David Fokkema dfokk...@ileos.nl wrote: - Why exactly are FR's different while I've never heard of Nokia users needing to tweak mixer settings. WTF? Every phone user tweaks mixer settings by using volume up and volume down buttons during call... In Freerunner we only miss good UI (from user point of view) and infrastrucuture behind it (from programmer point of view). I've heard of phone users using their volume up and down settings, but I've never heard of setting _three_ volume sliders in some particular config which does not produce clipping, does not inhibit noise reduction, while keeping enough gain to be loud enough for the other side. And furthermore, by evidence of numerous threads on this mailing list and conflicting and incomplete information in the wiki, one particular statefile will _not_ work for all users. And I'm not talking about very subjective things either: clipping, noise, rustling, echo, etc. which makes conversations extremely difficult while using statefiles which are just about perfect for some users. The fact that Freerunners differ in audio quality and settings has been stated on this list and on support. And going by the last paragraph, this is true. So, _why_ are Freerunners different? Regards, David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Fri, 2009-08-07 at 16:52 +0200, Sebastian Krzyszkowiak wrote: On 8/7/09, Marcel tan...@googlemail.com wrote: Am Freitag, 7. August 2009 16:29:24 schrieb Sebastian Krzyszkowiak: On 8/7/09, David Fokkema dfokk...@ileos.nl wrote: - Why exactly are FR's different while I've never heard of Nokia users needing to tweak mixer settings. WTF? Every phone user tweaks mixer settings by using volume up and volume down buttons during call... In Freerunner we only miss good UI (from user point of view) and infrastrucuture behind it (from programmer point of view). Afaik, my Nokia 3510i doesn't even have such buttons and I never missed them... I'm pretty sure in Nokia 3510i up and down buttons control volume during call, as in Nokia 3310 and Nokia 3410. And most of users just set volume once, when they can't hear something or they think volume is too loud, and then they forgot about it - but it's still volume tweaking, and exactly the same is possible in Freerunner, just software is missing! Angus Ainslie's mixers (pymixer.py and the newer fsomixer.py) are excellent! Still, I needed to play with three sliders for input and two for output. I understand the need for several sliders. Looking at the wolfson I can see that you can mix just about everything so you can record phone calls while also playing soft piano music to _both_ sides for a very relaxing conversation (I _think_ that this is possible...) but still... David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Fri, 2009-08-07 at 16:45 +0100, Vasco Névoa wrote: I think you're all missing the point. David's initial post is a breath of fresh air into a long debated but (AFAIK) non-resolved issue. Thanks! I deeply welcome his investigation into this subject, and support his questions (which I also would like to see answered). Although the issue of low playback volume is rather well controlled in our FRs, the issue of low recording volume for GSM transmission remains - with callers still complaining and going what? I didn't hear you... now and then, especially in (even slightly) noisy environments. The whole audio settings for GSM issue is _not_ cut and dried, in my view. I still have to go into frameworkd.conf every time I flash the phone and set the DSP to long-aec to avoid echo and sporadic audio clipping, as well as raising the volume in playback and mic in gsmhandset.state... and I'm still not satisfied with audio quality. Exactly. So, can someone please humor David and me and explain this sidetone channel business? Yes, please! David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner audio channels
On Fri, 2009-08-07 at 17:12 +0100, Al Johnson wrote: On Friday 07 August 2009, David Fokkema wrote: - Why exactly are FR's different while I've never heard of Nokia users needing to tweak mixer settings. Most phones have a simple volume up/down control, often a pair of buttons on the left side of the handset. They hide most of the functionality of the mixer chip which is fine so long as it what you want and what they chose to implement are the same. So far nobody has written a similarly simple volume control for the FR. I understand that, but let me explain exactly why I think nobody has written one, by describing an algorithm which you could use, according to the 'one' statefile and information in the wiki: Max out Mic2 Capture Volume (48), (almost) max out Mono Sidetone Playback Volume (12), adjust Mono Playback Volume (5) as needed. So this simple volume control script should only adjust (5). Sounds simple. However, on _my_ freerunner, this resulted in _severe_ clipping, and the connection was never silent when I didn't speak. That is, background noise was sufficiently amplified to inhibit noise reduction, even when (5) was so low I could just hear myself. Why? I don't know, maybe the waveform? I had severe clipping, so maybe... Reducing Mic2 (48) to its _lowest_ setting, in exact contradiction with the wiki, greatly enhanced audio quality. So, maybe that's why... When you think you've found something great, lots of people start complaining on the mailing list that your volume control just sucks. - Why does setting Mic2 Capture Volume to 0 _not_ (almost) mute the mic? Mic2 has four fixed gain settings of +12dB, +18dB, +24dB and +30dB which are represented by 0, 1, 2 and 3 in the alsa driver. Mute is not an option, though IIRC you could switch that amp off. See page 20 of the Wolfson datasheet. Ah, found it! Thanks for the pointer, excellent information. I'll read this during some more lunch breaks, ;-) - Why do we bypass the digital filters by using the sidetone path? The digital filters are for ADC and DAC which we aren't using in phone calls. We are passing analogue signals through to the Calypso which has its own filters, ADC and DAC. The only possibly useful bit there is the AGC/Noise Gate, but AFAIK nobody has managed to get it to do anything useful so far. Ah, I see. The 'nicer' diagram on the wiki, with all the alsa mixer setting names has packed the ADC and DACs and their (hidden) outputs into one black box. It is elaborated upon on the bottom of the page, but it was not clear to me, thanks. Apps which record the phone call, or play sound into the call, will be using the ADC and DAC, so will include the filter blocks. Makes sense. Remember that our use of the chip is not typical. Most would probably be using the digital voice interface to connect to their GSM chipset instead of using an analogue passthrough as we are. We use the voice interface for a digital connection to the bluetooth module instead. Couldn't we have used both? I mean, using the digital voice filters (they seem nice) _and_ using a high quality bluetooth interface? Maybe I misunderstand the wolfson docs (just browsing, ATM) but the wolfson seems to be designed for this (smartphone (with voice filters) + bluetooth). Thank you for your answers! Best regards, David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Using gps from command line
On Sat, 2009-07-18 at 20:13 +0200, Laszlo KREKACS wrote:
So anybody can show me a working code using the gps through frameworkd?
Like this?
import dbus
import time
bus = dbus.SystemBus()
usage = bus.get_object('org.freesmartphone.ousaged',
'/org/freesmartphone/Usage')
gps = bus.get_object('org.freedesktop.Gypsy', '/org/freedesktop/Gypsy')
gps_device = dbus.Interface(gps, 'org.freedesktop.Gypsy.Device')
gps_position = dbus.Interface(gps, 'org.freedesktop.Gypsy.Position')
print usage.GetResourcePolicy('GPS')
print usage.GetResourceState('GPS')
usage.RequestResource('GPS')
print usage.GetResourceState('GPS')
t = time.time()
while True:
print 'Connection:', gps_device.GetConnectionStatus()
print 'Fix:', gps_device.GetFixStatus()
print 'Position:', gps_position.GetPosition()
time.sleep(2)
if time.time() - t 10:
break
usage.ReleaseResource('GPS')
print usage.GetResourceState('GPS')
David
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Anti-Whining: Happy Moko Moments
On Fri, 2009-07-17 at 08:31 +0200, David Reyes Samblas Martinez wrote: With my Freerunner, I am able to control a telescope 5000 miles away, and analyse the data, while I sit in a pizza parlor. It's the high resolution display and the X11 server that lets me do this. Ken, this is ... this is only a word comes to my mind, beautiful. there will be awesome to haves some pictures, screenshots, and if posible a video of this, Second that! We really need a gallery of cool applications! Since a picture is worth a thousand words, if we'd like to show the world there really is something to all this we don't need lists and lists of applications, we need a gallery. David (currently astroparticle physics PhD student, looking for some time to implement a nice cool app for monitoring our experiment on my N800 and FR) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The University of São Paulo's intent to join Openmoko development
On Thu, 2009-07-16 at 16:05 -0400, Jon 'maddog' Hall wrote: Don't give up. If you look closely, you can see the light at the end of the tunnel. It may be faint, but I have seen similar tunnels before, and I can see the light now. Warmest regards, maddog, to me you've just been a name for a long time. `The one with the beard, no not RMS, the other one'. Seems to be a trait of free software visionaries, I guess, ;-) Seeing how you're being a part of this community first-hand, reading your long mails and trying to appreciate the time it must take you to do all this, the energy you put forth to not only try to arrange things but also explain to people who are sometimes skeptical, has been a privilege. Thank you, David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Record call.
On Mon, 2009-07-13 at 01:39 +0200, Rask Ingemann Lambertsen wrote: On Fri, Jul 10, 2009 at 03:10:13PM +0200, David Fokkema wrote: And, in addition, if this works, will it be able to pick up GSM buzz on the outgoing signal? Or is that really happening way after wolfson, inside, or even after calypso? Probably the latter... The buzz is present all the way from the mic, so it should be perfectly possibly to record it. I've tried to do so but AFAIK not yet had GSM buzz. Ah, great! The thing is: with all the talk about buzz, bass, clipping due to alsa settings and stuff like that I always wonder: if it is possible to record it, why didn't someone put up some files so that you can really hear the difference between buzz, bass, background, clipping and all those things (including, of course, a best we can manage clear as a bell audio file). Maybe that'll end the confusion about whether alsa or the buzz fix will fix certain issues. Related: it appears that every freerunner is unique and needs it's own unique alsa settings. Why doesn't Nokia or Apple suffer from that? Those phones simply work out of the box, even after software upgrades. I'll try to answer my own question: those phones are unique as well (due to component tolerances), but are calibrated in the factory and the settings are preloaded in the phone somewhere software updates can't touch them (EPROM?). Thanks, David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Record call.
On Fri, 2009-07-10 at 14:48 +0200, Ed Kapitein wrote: Hi all, I would like to automatically record each call i receive. I did try to run arecord, but that doesn't record any sound (neo side or other side) I allready took a look at dictator, but that seems to be toying with the state files, if i read the source code corectly ( probably not...) Is there a simple way to record an ongoing conversation? what would be the input? can it be done with arecord (alsa)? And, in addition, if this works, will it be able to pick up GSM buzz on the outgoing signal? Or is that really happening way after wolfson, inside, or even after calypso? Probably the latter... David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re2: Image modules?
On Sat, 2009-07-04 at 17:52 +0200, Glenn Moeller-Holst wrote: At 14:47 +0400 04/07/09, Paul Fertser wrote: Glenn Moeller-Holst glenn.mh...@gmail.com writes: modules-2.6.28-stable+gitr0+f19f259d3c1afde8eae53983fd19f61831927413-r2-om-gta02.tgz Is it nessecary or advicable to flash it onto the phone? Flashing tar.gz archives makes little sense. You might want to untar it to your / though in case you don't have that modules already. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com This is what I am not able to read anywhere: *I actually do not know if I already having modules installed? How do I test it? Look in /lib/modules/kernel-version, or unpack the modules file and check. You'll find you already have it. *What is modules used for? Lots of hardware drivers are not needed by all pc's (or phones, for that matter) or are not needed all the time. To keep the size of the kernel binary small and to limit memory usage, these drivers are not compiled into the kernel, but rather as 'modules'. Usually, modules are loaded into memory if and when needed by the kernel. For our freerunners, this probably means that things like wifi and bluetooth are modules, which are not always active and thus not always loaded in memory. Generally, things like ati video drivers, ide drive drivers and braille tty drivers are not compiled and included at all, since that would make no sense. *Is modules (already) included the image? Not in the kernel image, but they are included in the root image. *Why is there a separate file called modules? Why not include it in the image? It _is_ included in the root image, as it lives in the root filesystem in /lib/modules. The thing is: if you decide to use that kernel but _not_ use that root filesystem (because you'd like to build your own, for example, or you just want to upgrade your kernel and _not_ your filesystem) you'll have to untar the corresponding modules into your own filesystem. *Is modules a standard Linux thing? It is a standard linux feature. But it is certainly not limited to linux, although naming conventions may vary. I am asking as a novice. I have not encountered information about modules at: http://wiki.openmoko.org/ Google 'linux kernel modules' and you'll find more than you'll ever want to know. HTH, David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [shr-unstable] making bricks...
On Mon, 2009-06-29 at 12:00 +0200, Rask Ingemann Lambertsen wrote: On Sun, Jun 28, 2009 at 09:02:28AM -0700, jeremy jozwik wrote: dmesg has given me this, most of which i do not understand. but i did try adding ip address command to usb3 and terminal reported back cannot find device [snip] usb 3-1: New USB device found, idVendor=1d50, idProduct=5119 usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1: Product: Neo1973 Bootloader U-Boot 1.3.2-moko12 You have to boot the Freerunner first. There's no USB Ethernet support in the boot loader. That's a very astute observation, :-) David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Why one cannot recommend the freerunner as a daily phone (was Re: Is a FreeRunner sufficient for me?)
On Fri, 2009-06-26 at 02:09 -0400, David Ford wrote: people have different ideas about how to use their devices. regarding netiquette, opinion varies and there is no one solution which fits everyone best. not every wants to use text based clients, nor scroll to the end of a page. regardless of it being near instant or several steps, they are still unnecessary steps. in the end this is, as it always has been, a religious preference that some people attempt to enforce passionately. thankfully the passionate argument of 40 column text has disappeared. What do you mean? 40 columns? Way too much for my terminal! I read this from punchcards (extended version) so that I really need your mails to wrap around much less than 40 columns. I hate people are making so many assumptions as to what terminal I'm using to read their mails. So, I agree with your first point. Regards, David PS: This thread alone has made for a nice stack of cards. Still think- ing about ways to use them... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: posting style preferences was Re: Why one cannot recommend the freerunner as a daily phone (was Re: Is a FreeRunner sufficient for me?)
LOL On Fri, 2009-06-26 at 12:32 +0200, DJDAS wrote: FINALLY :) Thumbs up! BWL snip FINALLY :) Thumbs up! (To not hurt anyone :P ) ROTFL David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Why one cannot recommend the freerunner as a daily phone (was Re: Is a FreeRunner sufficient for me?)
Talking about the memory usage of C++: On Wed, 2009-06-24 at 22:30 +0200, Michal Brzozowski wrote: Hmm, that is one very aspect of C++ I wasn't aware of. But it won't use more than, lets just mention some random language that's currently making up most of FSO / Paroli (thus Om2009), python. I'm very fond of python BTW, but I don't think efficiently using memory resources is one of its strengths, but you can prove me wrong any time, ;-) David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Why one cannot recommend the freerunner as a daily phone (was Re: Is a FreeRunner sufficient for me?)
On Wed, 2009-06-24 at 17:32 -0600, Laura Vance wrote: Interpreted languages are excellent for rapid prototyping and initial development, but once it's ready for any type of release, it should be ported to C (in this case) or C++. From the FSO website (http://www.freesmartphone.org/index.php/Cornucopia): Always remember: The python implementation is the chance for getting the API right; the vala implementation is the chance of getting the right API fast. ... which is basically what you are saying. David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: strange df behaviour
On Thu, 2009-06-25 at 00:01 +0400, ivvmm wrote: The filesystem on it is ext3. The df program from virtualbox reports it You really mean busybox, don't you? ;-) Virtualbox is a virtualization solution. David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
