Re: Call noise on buzz-fixed freerunner with Qtmoko
Al Johnson wrote: Depending on what NeoControl does my suggestion below may or may not help. Well... it did. A bit. But not enough to make people I call happy :( So, I tried install SHR-unstable from 19th. June on another partition and according to a quick test/poll, the sound in the other end is crystal clear with SHR. It puzzles me that I should be the only one experiencing such big a difference. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Call noise on buzz-fixed freerunner with Qtmoko
Hi, I've installed Qtmoko V24 on a buzzfixed Freerunner, but people still complain that there's so much noise in the other end that it's impossible to understand. I've checked that the ALSA state file is about the same a recommended for buzz fixed phones. I'm wondering whether there some echo-cancellation missing in the modem configuration. Where is that configured on Qtmoko? /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Call noise on buzz-fixed freerunner with Qtmoko
Radek wrote:
You can tweak alsa state in NeoControl application.
Yeah,.. but I'm ok with editing
/usr/share/openmoko/scenarios/gsmhandset.state
for now.
However... I discovered that NeoControl shows 127 for playback while my
gsmhandset.state has 110.
Is it so, that Qtmoko will apply it's own setting (127) temporarily
every time I make a call and the reason for my noise is feedback to my
microphone from my speaker?
Echo cancelation is enabled by default. It's hardcoded in modem plugin
and cant be disabled.
Ahh.. ok.. that explains why I couldn't find where it was defined :)
Al wrote:
Can you try it yourself to see exactly what the problem sounds like?
My guess is that your voice is distorted when you're speaking, there
may be some distorted echo when they're speaking, and it doesn't buzz
when nobody's speaking.
It sound like a lot of electric interference. I hear the other part load
and clear though.
The recommended setting is just a reasonable starting point. What are
your settings?
I've included the alsa state file below:
state.neo1973gta02 {
control.1 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'PCM Volume'
value.0 0
value.1 0
}
control.2 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 255'
iface MIXER
name 'ADC Capture Volume'
value.0 0
value.1 0
}
control.3 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Headphone Playback Volume'
value.0 0
value.1 0
}
control.4 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 127'
iface MIXER
name 'Speaker Playback Volume'
value.0 127
value.1 127
}
control.5 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 127'
iface MIXER
name 'Mono Playback Volume'
value 110
}
control.6 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 7'
iface MIXER
name 'Bypass Playback Volume'
value.0 7
value.1 7
}
control.7 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 7'
iface MIXER
name 'Sidetone Playback Volume'
value.0 0
value.1 0
}
control.8 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 7'
iface MIXER
name 'Voice Playback Volume'
value.0 0
value.1 0
}
control.9 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Headphone Playback ZC Switch'
value.0 false
value.1 false
}
control.10 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Speaker Playback ZC Switch'
value.0 false
value.1 false
}
control.11 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 7'
iface MIXER
name 'Mono Bypass Playback Volume'
value 0
}
control.12 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 7'
iface MIXER
name 'Mono Sidetone Playback Volume'
value 7
}
control.13 {
comment.access 'read write'
comment.type INTEGER
comment.count 1
comment.range '0 - 7'
iface MIXER
name 'Mono Voice Playback Volume'
value 0
}
control.14 {
comment.access
Re: Detecting 1024 on qtmoko
Peter Mogensen wrote: So do anyone have pointers to fool-proof 1024 bug detection on QtMoko Ok... upgrade to V22 and the problem with no network seemed to be solved by a cold start. Now QtMoko runs and the phone works with deep_sleep enabled, though it is not 1024-fixed. This is probably too good to be true, so how do I verify that there's no 1024 problem on QtMoko? (assuming I've warmed the phone enought for it to appear.) Also... do QtMoko really log to files on flash or have I missed something. I would prefer logging to a ramfs like on SHR. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Detecting 1024 on qtmoko (and others)
Hi, I'm about to wake up from having spend the last year being 100% dependent on a always working phone, so the FR have been on the shelf. Now, I'm trying to figure out if I should have the phone #1024 fixed. Initial tests on SHR using the deep-sleep-check.py script from the Wiki and trying the AT-command sequence from handheld-linux.com seems to show no signs of the bug. However, when I tried with QtMoko and changed the deep sleep modem conf Active=never to Active=always, the PIN dialog never came up and QtMoko just showed a No network message. So do anyone have pointers to fool-proof 1024 bug detection on QtMoko and SHR? It seems what I've done until now points in 2 different directions. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: One second Openmoko boot?
Robin Paulson wrote: i've never understood the fascination of linux users with keeping systems up for days and months on end. sure, it's great for a server hosting web sites, or in a corporate environment, but for a home system? it comes across as nothing more than who's the most '1337', which is really lame. add to that the power wasted and it's verging on the pointless AFAIK, theres' only one problem with the fascination of never rebooting - and it's not power consumption. If you never reboot your servers under controlled circumstances, you have no guarantee that they will come up nicely in event of a forced reboot. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: [shr-u] wifi timeout with mokonnect
arne anka wrote: well, i did right now # fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf which resulted in [snip a lot] indefinitely. I get excatly the same. Only once have I managed to get a DHCP lease, but the network failed just after that. What has gone wrong with WiFi during the summer? In april, I had an almost working phone with almost stable WiFi - at least the first connect after boot was never a problem. Now I got it buzz-fixed, moved to the other end of the country and had holiday and when I return WiFi is broken and I have to use slow USB net. Some one must know what has changed? New kernel? /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: [shr-u] wifi timeout with mokonnect
Paul Fertser wrote: Adam Jimerson vend...@gmail.com writes: Same here I would like to know how to connect to a network without using the ifconfig commands 0. So, clean boot, you didn't touch resource policies in any way (SHR settings/mdbus/whatever). 1. Then ``vim /etc/wpa_supplicant/wpa_supplicant.conf'' and configure the way you need. 2. Then ``fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf'' and wait for it to associate. 3. ``dhclient eth0'' (or whatever your favourite client is) 4. enjoy If the step 2 or 3 fails, then 2.5 ``wmiconfig -i eth0 --power=maxperf'' No luck... If I omit doing step 2.5 as step 1.5 eth0 just disappears after using step 2 (fsoraw). If I do step 2.5 just before fsoraw it just goes quoted below. I'm curious. WiFi used to be easy to get going. I just edited my wpa_supplicant.conf, added the wpa-conf to /etc/network/interfaces and did an ifup eth0. What went wrong? $ ./fsoraw -r WiFi -- wpa_supplicant -ieth0 -Dwext -c/etc Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged Using **pending_return in dbus_connection_send_with_reply_setup() without pending_setup is deprecated and strongly discouraged ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-SCAN-RESULTS ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Finger friendly keyboards
Jon Levell wrote: div class=moz-text-flowed style=font-family: -moz-fixedHi, So far on my FR, I've mostly been typing non-dictionary words so the predictive keyboard has been getting in my way. Me too... Actually... I think I have only one finger friendly solution which will remedy that. What I wish for is a large transparent fullscreen keyboard which is activated by a short press on AUX. (long press = some menu) Combine this with auto-rotation and writing an SMS will just be turning you Neo and pressing AUX. You'll have large keys, to easily hit and you'll be able to see the text you write through the keyboard overlay. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Getting deleted SMS back / Freerunner as a card reader?
Hi, A friend of mine asked if he could get some accidentally deleted text messages back from his SIM card - so I started looking into how a SIM works and how to communicated with it. It seems that there's no AT-commands which will give you deleted messages - right? If AT+CMGR or similar will get you a deleted message, than that's of course the easy solution. I can see that there's several mobile forensic products on the market which seems to be just smart card readers with the right software. I have a smart card reader, but I have not tested if it takes SIM cards (or RUIM cards ... have to find out), but I figured, that another easy solution was to access the card-reader directly in the FreeRunner if the hardware allowed for that. So, can the SIM card in a FreeRunner be accessed like a card reader on a serial interface? /Peter PS: Any other solutions are welcome, btw :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: FreeRunner Happiness
Yaroslav Halchenko wrote: Unfortunately it still does lack some basic phone functionality (mailbox alters, stable alarm etc) SHR seems to have stable alarm, so it'll come. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
dualboot. u-boot now, Qi later
I was considering starting to use the Neo as a daily phone, so I need to dualboot. Are there anything special I need to consider to make the partitioning compatible with future Qi bootloader? I thought of making a few smaller partitions for different kernels and a few larger of different rootfs + one large for my personal data. But that will mean more than 4 partitions. Will logical partions work just as well with Qi? Are there any special order which is better? Or will I have wipe all systems and start over when Qi arrives? /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
FSO M4 - nice GSM sound
Hi, I just wanted to congratulate the FSO team for their new images. For the first time I have perfect sound over GSM. No echo, no buzz. There's some other problems though, but I'm sure they are minor. One problem I have had with every distribution and I haven't seen mentioned else where is that the phone takes too long to answer a call. First it takes too long for it to start ringing (only vibrate). Then there's a delay before the ring tone play. Then there's a delay from I press the answer button to it reacts .. and by then my voice mail has usually given up and taken the call. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: FSO M4 - nice GSM sound
Warren Baird wrote: I haven't tried FSO yet - maybe I should now - but I've been using QTExtended 4.4.2 for a bit over a week now, and it seems to be much more responsive - when I was running the 2008.8 based images I regularly missed calls because by the time the phone started to ring, my voice mail had already picked up. With QtE, I haven't had that problem. Qtopia 4.4.2 crashed before I could to answer my first call. Anyway... I had it only installed to see the changes. On the other hand... FSO4 managed to send all my SMS messages back to their sender tonight. ... you have been warned: Think carefully before pressing any buttons :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ``Freerunner reliable and stable''?!
Ole Kliemann wrote: Me as well as several others - as I read here on the lists - have bought our FR when it was released somehow expecting it being consumer-ready. It was the general notion that GTA01 was for developers, GTA02 for end-user. Well... It would be too optimistic to expect a consumer-ready device. It was no secret that the software was lacking. But I think it was not unreasonable from the initial messages from OM to expect a device with no critical irrecoverable hardware errors. Which is simply not true. Qtopia of course suffers from the same hardware and kernel issues as just any other distro. Excatly. And I hope 1st. priority from OM is to solve all these basic kernel problems, so (for example) the confusion about GSM/audio noise/echo can end. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Where are actions configured for buttons in FSO?
Michael 'Mickey' Lauer wrote: Am Montag, den 29.09.2008, 20:18 -0400 schrieb digger vermont: Yeah, I'm all for frameworkd! Problem is as far as I can see it's not currently being used to configure the PWR button, at least as far as I can see. So what is currently telling the PWR button to suspend if it is pressed for 3(?) seconds? Zhone is doing that currently. Slightly on the topic... I was wondering about that too, since I don't really agree with the way the buttons/LEDs are currently used on 2008.X We only have 2 buttons, so letting AUX be LOCK seems like a real waste of functionality for me. LOCK can be done ether automaticly or via a GUI menu and it doesn't have to be accessible through a single key press. It would be much better if AUX brought up a utility menu like on Qtopia. This could include some nice-to-have stuff like a task-manager ... and maybe a LOCK option. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: [2008.9] What, no updates?...
Dr. Morpheus wrote: I get the impression updates are staged fairly well for stable. I use testing (and it runs fantatsic at the moment, can use as a daily phone) and updates are pushed pretty much every day. Testing = FSO / Zhone? No. FSO release images are available here: http://downloads.openmoko.org/framework/milestone3/ There's also a FSO-testing available here: http://downloads.freesmartphone.org/fso-testing/ Zhone is just a demo-application for the FSO framework. It does have some practical use as a phone-application though. The framework (D-bus API/framework-daemon) is the primary product of FSO. If not, where do I get this? Are there testing feeds for 2008.9? If so, which one? http://downloads.openmoko.org/daily/ Read: http://wiki.openmoko.org/wiki/Downloads#Om_2008.8_images_.28ASU.29 /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Getting Zhone to work on Om-testing
Hi, I've been trying to get FSO D-bus api working on the OM-testing distribution (from http://downloads.openmoko.org/daily/) The zhone package available in testing installs fine and D-bus seems to work. I can query with mickeydbus and I can see incoming events when I call the phone. The Neo vibrates, but Zhone doesn't react. I can also use Zhone to call another phone. The other phone rings and Zhone detects that it has been answered, but that's about it. No sound and Zhone doesn't detect when I hangup. Zhone says No dbus, but cleary it can do something with the D-bus. As registering on the GSM network and make call. Also strange: frameworkd seems to consume a lot of CPU. (around 80%). What is needed to get a basic FSO framework to run on testing? /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bye bye 2008.8, you wont be missed :(
William Kenworthy wrote: I am afraid I am going to have to delete 2008.8 and forget it ever existed. Despite very little of it working, I was giving it a go but I just had a bug I raised on the keyboard closed with works for me saying in effect they are only willing to work on the existing keyboard and its working as designed, so there isnt a problem and no changes/new keyboard alternatives are needed. Well, that was not exactly what was said, but I understand your disappointment. And I'm desperately trying not to draw the same conclusions. The keyboard works for me (technically), but it's FAR FROM living up to my expectations. It's nice - but only for certain applications and for some it really sucks. /Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: New Qtopia-Images fixes suspend problem nearly complete!
Yaroslav Halchenko wrote: qtopia has 1 very annoying to me issue though -- if I receive a phone call, and click on answer button -- it takes 2-4 seconds for the phone to actually react -- thus I often lost some phone calls which is annoying. well... part of the problem is that the hangup button appears where the answer call button was, so if you click one time too many, you hang up immediately. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 2008.08 - First Impressions
Dale Maggee wrote: Firstly, it's *gorgeous* - eyecandy city! I *really* like the look and feel of it! It's much more friendly and less 'clunky' feeling than 2007.2. Hmm.. let's just say I'm impressed by how good Qtopia on X11 actually performs. Some of the earlier snapshots were really slow, but this is acceptable. The graphical installer is great! I really like this, although I agree with the opinion stated elsewhere that the text is too big, and I'd really like to see the 'description' text on the package details screen, so that I know what the package is (names aren't always that informative). So you don't think it should be usable without a stylus? * keyboard - Predictive text is annoying as hell. Agreed. There seem to be some kind of interface nazism (to quote Thorvalds) going on. Apart from the predictive keyboard being *really* annoying - especially if you are typing URL's, shell commands or a non-english language!! then I don't understand this idea that there can't be a bring-up-the-keyboard button. (yes I know I can install a qwerty-button). For me the correct way is like qtopia: * Have a bring-up-the-keyboard button * Have change-input-method option * Have a set of different keyboards (multitap,full qwerty,handwriting,om2008-like) to toggle between. * Be able to turn predictive keyboard OFF ... and for goods sake... don't make a keyboard without a delete key. - I'd like to see letters on the numeric keypad screen. For example, the PIN on my sim card is a word typed using the numbers on my phone keypad, not a number - I have no idea what the numbers in my PIN are! in order to enter my pin using this numpad, I have to get out my nokia and look at it's keypad and then type in the numbers. Arhh... go write it down, then. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Om 2008.8 doesn't ask for my pin so no gsm available
I flashed the new kernel and image but if I boot now I'm not getting asked for a pin. There's no gsm in 2008.8 for me... This seem to be a common problem. The PIN-dialog does come up once in a while though. Restarting the X-server can make it appear. But even though to enter the correct PIN and the dialog closes without error, there's no GMS available. Trying to talk AT to the modem manually doesn't seem to work either. It just hangs. I tried move the SIM to an old phone an it still works OK. Somehow the FreeRunner seemded to have disabled PIN on the SIM though, so I had to re-enable. Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
