-
Notifications
You must be signed in to change notification settings - Fork 39
With v23, sound will come out of both the headset and the FreeRunner's speakers at the same time.
It is a known problem, for kernel 2.6.32 it is unknown how to use the trigger event.
Workaround:
- Use v22
- Manually switch using these commands:
For speakersound: alsactl -f /usr/share/openmoko/scenarios/stereoout.state restore
Of course this means that the phone rings via the headset only.
Source: http://lists.openmoko.org/pipermail/community/2010-May/061964.html
v18 was the same as v19 except that it had a newer kernel (2.6.32) and some problems related to it, but still quite usable.
v19 was thought to be more or less "stable" but had bugs with receiving SMS
v20-testing is again with the new .32 kernel and the problems related to it. The SMS problem should now be solved.
v21 is considered again quite stable, with the .29 kernel. Someone has reported that it has kernel problems, so you might want to try v21 software but flash v19 kernel in. The SMS problem should now be solved.
You can check this directory: /home/root/Applications/qtopiamail/mail
I think it's quite standard mail format, you can open it with kmail or with uudecode (command line) in the following format:
begin-base64 644 a [three lines of hash..] ====
Is there a plan to make qtmoko NOT touch the SMS's on the SIM..? Big fail to remove all SMS's from SIM without warning the user..
This should be fixed with recent versions (v20&v21)
If your touch screen is not responding to your actions, you might need to recalibrate your touch screen like this:
ssh to_neo source /opt/qtmoko/qpe.env qcop service send Launcher "execute(QString)" "calibrate"
and then touch the crosshairs firmly. Hope it helps!
Please use the AUX button. It is a pretty useful button/ feature.
Is qtmoko using the latest alsastate files ?
I think we need two sets for alsa state files - for buzz fixed and non buzz fixed freerunners. Mine freerunner does not have buzz fix, so i am shipping only non buzz fixed state files in my releases.
Or we can implement some volume control during call - i think the api is there and it should be quite easy.
Or application in feeds that replaces state files or it can be another step in the startup screen where you can selected that you have buzz fixed freerunner.
The alsa statefiles can be found at: /usr/share/openmoko/scenarios/gsmhandset.state
[hey!]
radek is the main devel but also other people participate on releases every now and then.
In short: I am focusing just on debian. I dont have time to do images for two rootfs.
There are basically 2 things we are now developing. Qtopia which is more or less just big application. It should run on any rootfs. I am trying to avoid debian specific stuff. I have reports that some users run Qtopia on Arch so it will probably run on FSO too. It would be interesting to run Qtopia on Openwrt with uclibc - could be faster then debian.
Second thing is the txt document HOWTO for creating debian rootfs: http://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt
It should give you idea which external packages and programs are needed for running QtMoko on any particular rootfs.
QTmoko doesn't have the calypso deep sleep enabled. To enable this, make sure you have the #1024 hardware fix made on your Freerunner, and then edit /opt/qtmoko/etc/default/Trolltech/Modem.conf
[Multiplexing] Active=yes
No, apt-get upgrade now just upgrades the rootfs. Upgrading kernel+qtopia had to be done manually.
Is the kernel provided at sourceforge (http://sourceforge.net/projects/qtmoko/files/) with or without DEBUG ie. is it the 'new, fast' or 'older, not so fast'?
The uImage-v18.bin is fast 2.6.32 nodebug kernel.
If you use qtmoko v19 then you have to decide between kernels (slow and reliable or fast with some problems debug/nodebug).
Where is the qtmoko community? Openmoko-community mailing list? This channel? Other places? Blogs, forums?
This mailing list and IRC, #[email protected], are probably the best choices.
It's possible, see http://pastebin.com/msjZrAqh
Easiest way is to use bluetooth to send files to your phone. But you can also transfer files manually. QtMoko searches documents in following dirs:
/media/card/Documents/audio/ogg/ /media/card/Documents/audio/x-wav/ /media/card/Documents/image/jpeg/ /media/card/Documents/image/png/
MP3 files should go to x-wav folder. If you don't have SD card you can use folders in /home/root instead of /media/sdcard
It is possible to reassign keys (or add other layouts) on the internal predictive keyboard. To do this - create file PredictiveKeyboardLayout.conf with customized settings in the /home/root/Settings/Trolltech directory. Below there are settings for russian layout:
[Board1]
Type=Words
Caps="QWERTYUIOP","ASDFGHJKL","ZXCVBNM'"
Rows="qwertyuiop","asdfghjkl","zxcvbnm'"
Equivalences="a\xe0\xe1\xe2\xe3\xe4\xe5\xe6","c\xe7","e\xe8\xe9\xea\xeb","i\xec\xed\xee\xef","n\xf1","o\xf2\xf3\xf4\xf5\xf6","u\xf9\xfa\xfb\xfc","y\xfd\xff","s\xdf"
[Board2]
Type=Numeric
Rows="12345","67890"
[Board3]
Type=Other
Rows="~!@#$\0^&*()_+|","`-=\\[];',./","\x2190{}:\"<>?\x21b5"
[Board4]
# utf8 is broken, use http://www.industrialtrainer.com/Unicode.shtm
Type=Letters
# ЙЦУКЕНГШЩЗХЪ
# ФЫВАПРОЛДЖЭ
# ЯЧСМИТЬБЮ
Caps="\x0419\x0426\x0423\x041A\x0415\x041D\x0413\x0428\x0429\x0417\x0425\x042A","\x0424\x042B\x0412\x0410\x041F\x0420\x041E\x041B\x0414\x0416\x042D","\x042F\x0427\x0421\x041C\x0418\x0422\x042C\x0411\x042E"
# йцукенгшщзхъ
# фывапролджэ
# ячсмитьбю
Rows="\x0439\x0446\x0443\x043A\x0435\x043D\x0433\x0448\x0449\x0437\x0445\x044A","\x0444\x044B\x0432\x0430\x043F\x0440\x043E\x043B\x0434\x0436\x044D","\x044F\x0447\x0441\x043C\x0438\x0442\x044C\x0431\x044E"
By default the predictive keyboard will not actually try to correct your input. To get it to offer corrections, you need to add a line to the end of Predictivekeyboard.conf. For example:
cd /home/root/Settings/Trolltech cp /opt/qtmoko/etc/default/Trolltech/PredictiveKeyboard.conf . echo "unpredictive=0" >> PredictiveKeyboard.conf
- on your phone goto:
cd /opt/qtmoko/etc/dict/
- create new folder for your language, for example:
cp -r en_EN de_DE
- enter folder:
cd de_DE
- replace existing words.dawg by one you can find here
rm words.dawg wget http://alasal.be/openmoko/keyboard/German/words.dawg
- change twice en_EN to de_DE in /opt/qtmoko/etc/default/Trolltech/locale.conf
- reboot
The active input method is not saved on shutdown; the default is loaded on startup. If you modify , you can change what the default input method is.
Before you modify the file, there is a section which looks like:
[InputMethods] DefaultIM=PhoneKeyPhoneKey refers to a physical keypad, which the Freerunner does not have. Some other options are:
- DockedKeyboard
- SmartKeyboard (the predictive keyboard)
- Keyboard
My guess is that there wont be any revolution. I would like to keep up with latest development so that we have latest kernel and QT. I would like to port some more applications and improve the phone a bit (there are still many places in which it could be better).
A modified version of x11vnc (courtesy of the author Karl J. Runge) works in conjunction with a Perl script (with a minor glitch - number keys on the main keyboard are offset by one key). The files can be found here: