A lead on the bluetooth audio suspend problem (QtMoko v26)
As far as I can remember there is an issue with bluetooth audio, where the FreeRunner user cannot hear audio over the bluetooth headset/handsfree device on outgoing calls until one incoming call has been received. I'm using QtMoko v26 and once in a while I can get this to happen. I have found a workaround, by accident: After pairing / connecting your bluetooth headset (handsfree in my case), go to the Profile Editor and play your selected ringtone or alarm tone (go to select a new ringtone, and let it play once.) Bluetooth audio then works for me for outgoing calls. I'm guessing the fact that the phone rings for incoming calls is what is making it work. :) Hypothesis: Some sort of initialization routine is taking place when audio is played over the sidetone. I don't have the skills to patch, but if this helps anyone, you're welcome. :) -- --Brian Kemp brian.k...@gmail.com PGP Key fingerprint: 1E5BF363 signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Bluetooth Profile selection on Resume from Suspend (QtMoko v26)
Hello all: No clue if this is a known issue or not. I can file a bug if it is not. (I'm not sure which tracker.) I have a Plantronics Explorer 220 bluetooth headset. It supports Headset and Handsfree BT profiles. When I try to connect w/ Headset Profile in qtmoko v26, the connection fails. When I try to connect w/ Handsfree Profile, connection succeeds. When I suspend the phone, and resume it, I must reconnect manually. I assume that the phone is trying to reconnect to the plantronics headset using the Headset profile. Is the connected profile of my device saved on suspend, or simply that it was connected? -- --Brian Kemp brian.k...@gmail.com PGP Key fingerprint: 1E5BF363 signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: A lead on the bluetooth audio suspend problem (QtMoko v26)
Brian Kemp wrote: As far as I can remember there is an issue with bluetooth audio, where the FreeRunner user cannot hear audio over the bluetooth headset/handsfree device on outgoing calls until one incoming call has been received. Yup, i remember :) I'm using QtMoko v26 and once in a while I can get this to happen. I have found a workaround, by accident: After pairing / connecting your bluetooth headset (handsfree in my case), go to the Profile Editor and play your selected ringtone or alarm tone (go to select a new ringtone, and let it play once.) Bluetooth audio then works for me for outgoing calls. I'm guessing the fact that the phone rings for incoming calls is what is making it work. :) Hypothesis: Some sort of initialization routine is taking place when audio is played over the sidetone. The problem was alsa scenario switching. I don't have the skills to patch, but if this helps anyone, you're welcome. :) Maybe you can enable logging for audio states switching. It could be obvious then where is the problem if it alsa state switching is wrong. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bluetooth Profile selection on Resume from Suspend (QtMoko v26)
Brian Kemp wrote: Is the connected profile of my device saved on suspend, or simply that it was connected? I dont know very much about it, but IIRC sometimes it can be that the headset connects to the phone. Not sure if this is the case. It could be seen in the bluetooth log how it works. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
Issue Resolved!!! Thanks Jose... /opt/Qtopia/etc/default/Trolltech/Storage.conf showed: /dev/mmcblk0p1 instead of: /dev/mmcblk0p4 I thought that it looked for Documents in: /media/card/Documents but clearly, I was wrong... Thanks, Nashvin On Wed, Oct 20, 2010 at 9:55 AM, Jose Luis Perez Diez jl...@escomposlinux.org wrote: A Dimarts 19 Octubre 2010 16:41:24, Nashvin Gangaram va escriure: Hi Sferic Thanks for the suggestion. I'm not sure what you mean by cleaning the sqlite3-document database. Is this performed in the Rescan System, or separately? Anyway, I tried to umount, rescan, mount, rescan with no luck... Have you checked the entries for /dev/mmcblk0p# of your fat partition on /opt/Qtopia/etc/default/Trolltech/Storage.conf? There are some docs abouth the contents of this file on http://doc.qt.nokia.com/qtopia2.0/html/devices.html http://doc.qt.nokia.com/qtextended4.4/integration-guide.html#document-content- system ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
Hi Nashin, the document-informations are stored in several tables in the sqlite3-database /home/root/Applications/Qtopia/qtopia_db.sqlite. You can take a look into this database for example with sqliteman (and edit, if you are sure what you are doing). Every time you rescan your documents the database should be updated - it should, but it didn't. This is on my qtmoko v25 and on your qtmoko v26 too. Only when I umount /media/card/ and rescan the documents, this database is clear - all document-informations are cleaned up. When I mount this partition again, the system finds all documents and update the database. As you described it seems to me, qtmoko v26 has a fault in this. Hope this helps - Greetings Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v26-Qtopia-Documents-System-tp5650006p5653740.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
A Dimarts 19 Octubre 2010 16:41:24, Nashvin Gangaram va escriure: Hi Sferic Thanks for the suggestion. I'm not sure what you mean by cleaning the sqlite3-document database. Is this performed in the Rescan System, or separately? Anyway, I tried to umount, rescan, mount, rescan with no luck... Have you checked the entries for /dev/mmcblk0p# of your fat partition on /opt/Qtopia/etc/default/Trolltech/Storage.conf? There are some docs abouth the contents of this file on http://doc.qt.nokia.com/qtopia2.0/html/devices.html http://doc.qt.nokia.com/qtextended4.4/integration-guide.html#document-content- system ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v26 Qtopia Documents System
Hi everyone My Current Config is: Qi Bootloader 1.02 (from SHR-testing feed) uSD Card (16GB) Partitions: 512 MB: ext2: QtMoko v26 512 MB: ext2: SHR-testing (2010/05/29) 512 MB: ext2: GameRunner 0.2 Rest: fat32: General Stuff... NAND Flash: QtMoko v26 (again, backup for when SD Card removed) When booting from either QtMoko v26 (uSD Card or NAND Flash): In the File Manager, i can see the General Stuff files above in: /media/card/Documents/ (so I believe that I have set up /etc/fstab correctly) but, they are not being imported into the Qtopia Documents System, so I cannot use them... Any ideas / suggestions? Thanks, Nashvin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
On Tuesday 19 October 2010 10:32:35 Nashvin Gangaram wrote: Hi everyone My Current Config is: Qi Bootloader 1.02 (from SHR-testing feed) uSD Card (16GB) Partitions: 512 MB: ext2: QtMoko v26 512 MB: ext2: SHR-testing (2010/05/29) 512 MB: ext2: GameRunner 0.2 Rest: fat32: General Stuff... NAND Flash: QtMoko v26 (again, backup for when SD Card removed) When booting from either QtMoko v26 (uSD Card or NAND Flash): In the File Manager, i can see the General Stuff files above in: /media/card/Documents/ (so I believe that I have set up /etc/fstab correctly) but, they are not being imported into the Qtopia Documents System, so I cannot use them... Any ideas / suggestions? You can try Rescan documents from Documents screen (the bottom right icon in main menu). Otherwise you can try give me output of mount and ls /media/card/Documents. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
Hi Radek Thanks, I forgot to mention I had tried to Rescan documents unsuccessfully. Here is some stuff from the terminal (manually typed, so forgive typos...): r...@neo:/# mount rootfs on / type auto (rw,noatime,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/mmcblk0p4 on /media/card type vfat (rw) Kind Regards, Nashvin On Tue, Oct 19, 2010 at 11:51 AM, Radek Polak pson...@seznam.cz wrote: On Tuesday 19 October 2010 10:32:35 Nashvin Gangaram wrote: Hi everyone My Current Config is: Qi Bootloader 1.02 (from SHR-testing feed) uSD Card (16GB) Partitions: 512 MB: ext2: QtMoko v26 512 MB: ext2: SHR-testing (2010/05/29) 512 MB: ext2: GameRunner 0.2 Rest: fat32: General Stuff... NAND Flash: QtMoko v26 (again, backup for when SD Card removed) When booting from either QtMoko v26 (uSD Card or NAND Flash): In the File Manager, i can see the General Stuff files above in: /media/card/Documents/ (so I believe that I have set up /etc/fstab correctly) but, they are not being imported into the Qtopia Documents System, so I cannot use them... Any ideas / suggestions? You can try Rescan documents from Documents screen (the bottom right icon in main menu). Otherwise you can try give me output of mount and ls /media/card/Documents. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
Hi Nashin in a similar situation I found it helpfus to umount the document-partition, scan the system and after cleaning the sqlite3-document-database re-mount the document-partition and scan again. After this I can reach my new Documents. Hope, this help. Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v26-Qtopia-Documents-System-tp5650006p5650969.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 Qtopia Documents System
Hi Sferic Thanks for the suggestion. I'm not sure what you mean by cleaning the sqlite3-document database. Is this performed in the Rescan System, or separately? Anyway, I tried to umount, rescan, mount, rescan with no luck... Thanks Nashvin On Tue, Oct 19, 2010 at 4:06 PM, sferic sfe...@gmx.net wrote: Hi Nashin in a similar situation I found it helpfus to umount the document-partition, scan the system and after cleaning the sqlite3-document-database re-mount the document-partition and scan again. After this I can reach my new Documents. Hope, this help. Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v26-Qtopia-Documents-System-tp5650006p5650969.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: usb-mass-storage, data corruption, QtMoko v26
On Wednesday 29 September 2010 15:42:30 Alfa21-mobile wrote: so the fix is: ... I suggest to Radek (and all the community in general) to review this fix and possibly include it in the next release of qtmoko or asap. (data corruption is not a nice thing) if something is unclear, here I am! ;) I'll put it on my list for next release. If i forget it, please ping me :) Btw new kernel has combined driver for usb ethernet+usb mass storage. It would be nice to make it working... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: usb-mass-storage, data corruption, QtMoko v26
btw I'm not sure if this is acceptable by OSes others than linux, because in
this way we expose a storage without a partition table.
(I'll check this on a windows computer asap)
ok, sorry... I was away from any kind of windows pc :P
now I can confirm this fix is ok and my phone is viewed as a regular
single partition usb mass storage (atleast in win XP and Linux)
so the fix is:
!!!- I assume /dev/mmcblk0p1 being the fat32 partition used as storage
/opt/qtmoko/bin/usb-mass-storage-on.sh
[begin]
#!/bin/sh
DEV_NAME=/dev/mmcblk0p1
ifdown usb0
# sync all buffers
sync ; echo 3 /proc/sys/vm/drop_caches
umount ${DEV_NAME}
rmmod g_ether
modprobe g_file_storage file=${DEV_NAME} stall=0 removable=y
[End.Of.File]
in my /etc/fstab I've this line:
/dev/mmcblk0p1 /media/card auto defaults 0 0
and
/dev/mmcblk0p2 / autodefaults,errors=remount-ro,noatime 0 1
instead of the rootfs one. (yes, my qtmoko is on the second
partition of uSD and I've qi bootloader)
[I've also a swap on /dev/mmcblk0p3 but it's another topic]
and in my /home/root/Documents/ I have a symlink like:
card - /media/card/
so I can see its contents in qtmoko documents (remember the Rescan
System option in menu!!)
- with this modification you can start the mass storage (USB mass
storage on) an your /media/card data will be visible as an usb stick.
- it will be unmounted in qtmoko untill you select USB mass storage
off in qtmoko.
- your qtmoko will not corrupt the uSD.
- you'll be able to use your phone as always and you can also forget
to switch the storage off (but meanwhile you cannot do ssh or ip
connection via usb cable or read your /media/card inside qtmoko)
I suggest to Radek (and all the community in general) to review this
fix and possibly include it in the next release of qtmoko or asap.
(data corruption is not a nice thing)
if something is unclear, here I am! ;)
kind regards, a.
On Sat, Sep 11, 2010 at 3:31 AM, Alfa21 wrote:
2010-09...@18:13 Alfa21-mobile
and now a question from me:
when the usb mass storage mode is enabled, all the used partitions is
in read only mode..
I see qtmoko exports also the rootfs and imho it's not good because if
I forget to switch off the usb storage ... it's bad for the whole
system.
the question is: how I can configure qtmoko to use only a specific
partition? eg the one mounted on /media/card only?
about g_file_storage...
we have this DOGMA: an usb host will not expect to see any changes in the
storage other than the ones it makes.
I found a critical (if the rootfs is on uSD) bug concerning the use of
g_file_storage with the scripts in qtmokoV26!!
- the # mount checking if, in /opt/qtmoko/bin/usb-mass-storage-on.sh is too
weak because:
1) by default /etc/fstab in qtmoko contains rootfs for / and any root
partition on the uSD is not found by that grep
2) any swap partition is not found by that grep
so we could corrupt our storage if it remains mounted inside the freerunner
and both exported with usb!
a fix could be:
- in storage-on script
1) modify the DEV_NAME with the name of the specific partition we want to
export
2) umount it and really verify it's not mounted
3) modprobe g_file_storage (and we should add removable=y to the modprobe
line)
btw I'm not sure if this is acceptable by OSes others than linux, because in
this way we expose a storage without a partition table.
(I'll check this on a windows computer asap)
...else we could make a partition table inside the exported partition and use
kpartx in the freerunner to read the storage (yes, it's like a matryoshka of
partitions)
bye, a.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 battery life
On Thursday 23 September 2010 17:59:35 Timo Juhani Lindfors wrote: Tony Berth tonybe...@googlemail.com writes: when pressing the on/off button once and setting to suspend, the battery doesn't last more than 8h! Is that supposed to be like this? Are you hit by http://docs.openmoko.org/trac/ticket//2349 ? Not likely - only possible with experimental version v25. Please set proper suspend intervals in Settings-Power management: unplug the phone from charger/PC and make sure you have On battery suspend interval set to something reasonable (20s..5minutes - depends how you use your phone.). Otherwise you phone can wake up (e.g. because call/SMS/alarm) and will never suspend again. I think i will set some intervals right in the image for next version. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 battery life
Thanks a lot for your reply. I did change that value and I'll test it. Thanks Tony On Fri, Sep 24, 2010 at 8:58 AM, Radek Polak pson...@seznam.cz wrote: On Thursday 23 September 2010 17:59:35 Timo Juhani Lindfors wrote: Tony Berth tonybe...@googlemail.com writes: when pressing the on/off button once and setting to suspend, the battery doesn't last more than 8h! Is that supposed to be like this? Are you hit by http://docs.openmoko.org/trac/ticket//2349 ? Not likely - only possible with experimental version v25. Please set proper suspend intervals in Settings-Power management: unplug the phone from charger/PC and make sure you have On battery suspend interval set to something reasonable (20s..5minutes - depends how you use your phone.). Otherwise you phone can wake up (e.g. because call/SMS/alarm) and will never suspend again. I think i will set some intervals right in the image for next version. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 battery life
Tony Berth tonybe...@googlemail.com writes: when pressing the on/off button once and setting to suspend, the battery doesn't last more than 8h! Is that supposed to be like this? Are you hit by http://docs.openmoko.org/trac/ticket//2349 ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 battery life
В Чтв, 23/09/2010 в 17:54 +0200, Tony Berth пишет: when pressing the on/off button once and setting to suspend, the battery doesn't last more than 8h! Is that supposed to be like this? Hi, Tony. No, 8h is far from being normal. Be sure your phone is actually suspended. #2349 should affect only .32 and .34 kernels. Does your phone have #1024 fix? If yes, check that in NEOTool you turned on deep sleep. Try to turn on/off all devices like GPS, bluetooth and wifi. Which bootloader you using? If u-boot, try qi. Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko v26] online via GPRS
On 09/18/2010 06:40 PM, Marcel Meyer wrote: * on demand does not seem to work. When I use NeronGPS and a map is missing, it seems as GPRS _tries_ to get online but that's all ;-) I never tested on demand mode. Now i see that there is a bug in original qtopia. When pppd is started in ondemand mode its not opening serial port (as designed). QPE expects its to be open and start to write to the closed tty and hangs. Bug is somewhere inside QPE pppd manager, if i will have some free time i will fix it, it is trivial (e.g. - by initing serial port before running pppd). There are 2 other related bugs: 1) Default gateway is already set to 192.168.0.200 (usb), so traffic never comes to pppd. as far as i remember - linux support weight for the gateways, so fix is also trivial, but will require some work. Another bug is related to indicator - it doesnt work correctly in on demand mode, showing irrelevant status. Probably also not too hard to fix. * Staying online over a longer period of time seems to lead to a complete failure of the GPRS-stack so that I have to reboot the Neo to be able to get online again. I believe that this was fixed by me - GPRS session used the same ID numbers as Voice calls. I found that when fixed voice calls with active GPRS. Patch is done and probably will be in next qtmoko release. * Choosing always on leads to the phone trying to get online after booting and then hangs on the QtMoko-startscreen (after entering the PIN) when it tries to get online. See above. May be i will fix this, but not sure if i will have a free time. Fix is trivial, looks like nobody tested ondemand mode at all, bug is inside QPE core. GPRS Status fix may be will get some more time, i`m not really understand how this indicators works :) But i`m afraid ondemand mode, especially if i`m in roaming :) * I meanwhile managed to immediately switch to the internet settings after rebooting the phone (hard-reset) and deactivate the GPRS-connection before QtMoko managed to get online. You can ssh to the phone, delete default route (route delete default), add ppp0 as defroute (route add default ppp0) and ping any host - pppd will open port and system will be alive again :) If you want to test the fix - write me to samm at os2.kiev.ua and i will send you modified libs. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On 09/14/2010 11:08 AM, Christ van Willegen wrote: I, too, have experienced QtMoko. The one thing that annoys me, is that sometimes (well, more often than sometimes...) my FR turns on at night, and stays on until it wakes me from sleep indicating it's hungry... My wife doesn't approve :-( I have the same issue. Today i had some time to find the reason (cold-flue is really great thing for qpe development ;-)). This alarm is set by atd daemon, because BROKEN_RTC_ALARM is defined. This define is used for RTC devices which are not able to handle more then 24 hrs alarm (/* Workaround for broken same day only RTC */), so it sets alarm to 23:59:59-UTC. As far as i could see in the SC32442B specs - openmoko RTC alarm is able to handle day/month/year without problems, so probably this is defined by mistake. I now compiled atd w/o this define to see if it will work correctly. If it will - then this will be fixed in the next release. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
2010-09...@19:14 Alex Samorukov I now compiled atd w/o this define to see if it will work correctly. If it will - then this will be fixed in the next release. please take a look at: http://bugs.qtmoko.org/view.php?id=144 also kind regards -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On 09/20/2010 07:59 PM, Alfa21 wrote: I now compiled atd w/o this define to see if it will work correctly. If it will - then this will be fixed in the next release. please take a look at: http://bugs.qtmoko.org/view.php?id=144 also Thats me (Samm :)) Once again - to do the same as 'hwclock --systohc' do with running atd just run printf W\n /var/spool/at/trigger This fill force atd to update RTC clock. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko v26] GSM Multiplexer (GPRS)
Alex Samorukov wrote: After debugging i found that most of gprs related issues are coming from qtopia multiplexer. I decided to try to use external multiplexer with qtopia. For the initial experiment i did: 1) compiled latest gsm0710muxd on debian (i know that there is fso-abyss, but i got some problems on compilation, gsm0710 is much easer to build, so i started with it). Hi Alex, what about using the multiplexer in kernel? We will probably need quite recent kernel but otherwise do see any problem with it? It was commited in mainline kernel - i think it's this commit [1] Regards Radek [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e1eaea46bb4020b38a141b84f88565d4603f8dd0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko v26] GSM Multiplexer (GPRS)
On 09/19/2010 01:44 PM, Radek Polak wrote: 1) compiled latest gsm0710muxd on debian (i know that there is fso-abyss, but i got some problems on compilation, gsm0710 is much easer to build, so i started with it). Hi Alex, what about using the multiplexer in kernel? We will probably need quite recent kernel but otherwise do see any problem with it? It was commited in mainline kernel - i think it's this commit [1] I think that its very good idea - because it will be supported by community and also speed should be better then in user-land process (less userland-kernel jumps). Its interesting, how easy is to backport it to the current kernel. Also its currently in experimental status, so not sure how stable it is (but its not hard to be more stable then qtopia multiplexer ;)). It will also require to use another serial port driver in qtopia device profile, but its not a problem at all. May be i will try it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko v26] online via GPRS
Hi, I tried QtMoko in it's latest incarnation as the changelog said the GPRS- handling got improved :-) . I stumbled upon the following things: * In the chat file there is a missing at the end of the first line. So you always have to edit that file by hand after you opened the settings in the GUI. * on demand does not seem to work. When I use NeronGPS and a map is missing, it seems as GPRS _tries_ to get online but that's all ;-) * Staying online over a longer period of time seems to lead to a complete failure of the GPRS-stack so that I have to reboot the Neo to be able to get online again. * Choosing always on leads to the phone trying to get online after booting and then hangs on the QtMoko-startscreen (after entering the PIN) when it tries to get online. * Starting the phone without SIM does not work. After trying to switch to the GUI it just stays on a black screen. I tried that to prevent the phone going online. * I meanwhile managed to immediately switch to the internet settings after rebooting the phone (hard-reset) and deactivate the GPRS-connection before QtMoko managed to get online. Greetings, Marcel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Well I have played with the BT operations on qtmoko and here are my results... 1. With a plantronics headset once paired, it will work if you tell it to connect as a headset, the buttons work, and audio is ok. However when the bluetooth headset is subsequently turned on or comes in range of the FR, it seems to connect briefly automatically then disconnect, and you have to go in and connect as headset again from the UI. If you connect as handsfree the buttons no longer work for hangup and accept calls. 2. The Bluetooth is very flaky, while testing I had it lock up on me, or the bluetooth UI just would not come up without a reboot. 3. With one of my handsfree devices (the VR3 car speakerphone) if I connect as handsfree device, it actually works very well, the buttons accept and reject calls, and the incoming number shows on the devices LCD. This is surprising as the qt implementation of the handsfree profile looks incomplete, but I may be looking in the wrong place. 4. With my preferred device the Motorola T505 handsfree device, it has trouble connecting on occasions. If connecting as a handsfree device, the devices buttons do not accept or hangup a call, and the incoming number is not detected. But it does seem to work, although not in a usable way. If I try to connect as a headset it does not seem to work at all. Conclusions are that the system needs to be made more sturdy (maybe upgrade to bluez4, which would be a lot of work). The Handsfree profile code needs to be looked at closely and made to work with more devices. We need to make it automatically connect to a preferred device when in range with the preferred profile (headset or handsfree), having to go to the UI to connect everytime is not very usable. However I am impressed with how far Radek has got with this so far, especially as he doesn't use BT much :) I'll see if I can fix some of these issues, time permitting. (Special thanks to Paul Fertser for helping me out on IRC last night, it really helped to get me started on this). Thanks Jim -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris wrote: 4. With my preferred device the Motorola T505 handsfree device, it has trouble connecting on occasions. If connecting as a handsfree device, the devices buttons do not accept or hangup a call, and the incoming number is not detected. But it does seem to work, although not in a usable way. If I try to connect as a headset it does not seem to work at all. After rebooting and unpairing and repairing with the motot505, it did in fact work, the button accepted the incoming call and hangup again when pressed again. I did see the incoming number being sent to the device in hcidump, but the device did not recognize it. When I powered off the bluetooth device and started it up again the bluetooth daemon died, when started again I failed to be able to connect getting authentication errors. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko v26] online via GPRS
On 09/18/2010 06:40 PM, Marcel Meyer wrote: Hi, I tried QtMoko in it's latest incarnation as the changelog said the GPRS- handling got improved :-) . I stumbled upon the following things: It was a minor fix with adding +++ to the chat script. Not too much, but helps in some cases. * In the chat file there is a missing at the end of the first line. So you always have to edit that file by hand after you opened the settings in the GUI. Known problem, see Radek posts, fixed in git. * on demand does not seem to work. When I use NeronGPS and a map is missing, it seems as GPRS _tries_ to get online but that's all ;-) Needs to be checked, but for me its very low priority. * Staying online over a longer period of time seems to lead to a complete failure of the GPRS-stack so that I have to reboot the Neo to be able to get online again. Yes, it happens some time. You don`t need to reboot the NEO btw, restarting qtmoko should help. * Choosing always on leads to the phone trying to get online after booting and then hangs on the QtMoko-startscreen (after entering the PIN) when it tries to get online. I don`t think that always on is a good idea for qtmoko. First generation GPRS and voice works very bad together. I`m recommending to switch it off when not used. * Starting the phone without SIM does not work. After trying to switch to the GUI it just stays on a black screen. I tried that to prevent the phone going online. Non gprs related :) * I meanwhile managed to immediately switch to the internet settings after rebooting the phone (hard-reset) and deactivate the GPRS-connection before QtMoko managed to get online. Its very easy to do by removing chat script using SSH connection to the phone. P.S. I believe that some of the problem are related to openmoko multiplexer, but a lot of them - to the ancient modem with first generation gprs. I`m now trying to get qtmoko running with external demuxer, to see if it will improve the situation. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko v26] online via GPRS
P.S. I believe that some of the problem are related to openmoko multiplexer, but a lot of them - to the ancient modem with first generation gprs. I`m now trying to get qtmoko running with external demuxer, to see if it will improve the situation. I wonder if that may explain why I have never been able to authenticate successfully to ATT's GPRS network here in the states (maybe they're blacklisting older hardware?) I'm also having trouble translating their network settings information to what QtMoko accepts. If anyone's gotten it to work, I'd love to know what you did. I can supply the connection settings if that helps. --Brian Kemp brian.k...@gmail.com PGP Key fingerprint: 1E5BF363 signature.asc Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko v26] online via GPRS
On 09/19/2010 02:53 AM, Brian Kemp wrote: P.S. I believe that some of the problem are related to openmoko multiplexer, but a lot of them - to the ancient modem with first generation gprs. I`m now trying to get qtmoko running with external demuxer, to see if it will improve the situation. I wonder if that may explain why I have never been able to authenticate successfully to ATT's GPRS network here in the states (maybe they're blacklisting older hardware?) I'm also having trouble translating their network settings information to what QtMoko accepts. If anyone's gotten it to work, I'd love to know what you did. I can supply the connection settings if that helps. Please provide connection settings and the log file (/var/log/messages) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko v26] GSM Multiplexer (GPRS)
Hi, After debugging i found that most of gprs related issues are coming from qtopia multiplexer. I decided to try to use external multiplexer with qtopia. For the initial experiment i did: 1) compiled latest gsm0710muxd on debian (i know that there is fso-abyss, but i got some problems on compilation, gsm0710 is much easer to build, so i started with it). 2) Connected to phone using ssh and stopped qtmoko (/etc/init.d/qpe.sh stop) 3) started gsm0710muxd -v and requested virtual channel using dbus dbus-send --system --print-reply --type=method_call --dest=org.pyneo.muxer /org/pyneo/Muxer org.freesmartphone.GSM.MUX.AllocChannel string:$id I got pts /dev/pts/3, and modified /opt/qtmoko/qpe.env with export QTOPIA_PHONE_DEVICE=/dev/pts/3:115200. Also i disabled qtmoko multiplexing in the /home/root/Settings/Trolltech/Modem.conf ([Mutiplexing] section, Active=no). 4) Then i started qpe. It started correctly, detected network, etc. Then i requested another virtual tty (see #3) and started manually pppd on it. From the first view - qtmoko works stable, gprs starts/stops much better, no problems found so far. I want to test this for some time and if it will work fine then i will try to build qtopia with QMultiPortMultiplexer to use external mutiplexer. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Thursday 16 September 2010, Jim Morris wrote: Ori Pessach wrote: I didn't mention it, but I did just that. I stood in a field, looking at grasshoppers for 5 minutes. That's when I decided to take a walk. Â This weekend, I left my FR on a table in the back yard for 20 minutes. Still no fix. Ok, so a couple of things you can try... take out the memry card if you have one in, on older models having that in could cause enough interference to stop the gps getting a fix Not unless there's been a kernel regression. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Thursday 16 September 2010 19:54:12 Ori Pessach wrote: It doesn't work this way for me. How do I debug it? Close NeronGPS and all other apps that might use GPS. Then use console and do: /opt/qtmoko/bin/gps-poweron.sh cat /dev/ttySAC1 You should see what GPS chip is sending - it will be similar to this output: $GPTXT,01,01,02,ANTSUPERV=AC SD OD PDoS *0A $GPTXT,01,01,02,ANT$GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 $GPGSA,A,1,99.99,99.99,99.99*30 $GPGSV,1,1,00*79 $GPGLL,,V,N*64 $GPZDA,00,00*48 $GPRMC,,V,,N*53 If this works then your problem is probably just GPS satelite visibility. The output should contain GPGSA,A,3 substring once you get a fix (i am not 100% sure about this - you should search google and try to find something about nmea to be sure...). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Fri, Sep 17, 2010 at 12:05 AM, Al Johnson openm...@mazikeen.demon.co.ukwrote: On Thursday 16 September 2010, Jim Morris wrote: Ori Pessach wrote: I didn't mention it, but I did just that. I stood in a field, looking at grasshoppers for 5 minutes. That's when I decided to take a walk. Â This weekend, I left my FR on a table in the back yard for 20 minutes. Still no fix. Ok, so a couple of things you can try... take out the memry card if you have one in, on older models having that in could cause enough interference to stop the gps getting a fix Not unless there's been a kernel regression. And it doesn't make a difference in my case, so I think we can safely rule out a kernel regression. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Fri, Sep 17, 2010 at 5:52 AM, Radek Polak pson...@seznam.cz wrote: On Thursday 16 September 2010 19:54:12 Ori Pessach wrote: It doesn't work this way for me. How do I debug it? Close NeronGPS and all other apps that might use GPS. Then use console and do: /opt/qtmoko/bin/gps-poweron.sh cat /dev/ttySAC1 You should see what GPS chip is sending - it will be similar to this output: $GPTXT,01,01,02,ANTSUPERV=AC SD OD PDoS *0A $GPTXT,01,01,02,ANT$GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 $GPGSA,A,1,99.99,99.99,99.99*30 $GPGSV,1,1,00*79 $GPGLL,,V,N*64 $GPZDA,00,00*48 $GPRMC,,V,,N*53 If this works then your problem is probably just GPS satelite visibility. The output should contain GPGSA,A,3 substring once you get a fix (i am not 100% sure about this - you should search google and try to find something about nmea to be sure...). Regards Radek Well, here's what I'm getting: $GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 etc. (I'm copying this off the phone's terminal so I think I can be excused if I don't copy the whole output.) It's very similar to what you listed above, except that there are no $GPTXT lines. Any idea what that means? -- Ori Pessach ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Fri, Sep 17, 2010 at 5:52 AM, Radek Polak pson...@seznam.cz wrote: On Thursday 16 September 2010 19:54:12 Ori Pessach wrote: It doesn't work this way for me. How do I debug it? Close NeronGPS and all other apps that might use GPS. Then use console and do: /opt/qtmoko/bin/gps-poweron.sh cat /dev/ttySAC1 You should see what GPS chip is sending - it will be similar to this output: $GPTXT,01,01,02,ANTSUPERV=AC SD OD PDoS *0A $GPTXT,01,01,02,ANT$GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 $GPGSA,A,1,99.99,99.99,99.99*30 $GPGSV,1,1,00*79 $GPGLL,,V,N*64 $GPZDA,00,00*48 $GPRMC,,V,,N*53 If this works then your problem is probably just GPS satelite visibility. The output should contain GPGSA,A,3 substring once you get a fix (i am not 100% sure about this - you should search google and try to find something about nmea to be sure...). Regards Radek Oh, and one other thing: I'm doing all these tests outdoors, in a residential area with nothing over two stories high, and a clear view of a blue sky. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Ori Pessach wrote: Well, here's what I'm getting: $GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 etc. (I'm copying this off the phone's terminal so I think I can be excused if I don't copy the whole output.) It's very similar to what you listed above, except that there are no $GPTXT lines. Any idea what that means? Sorry i dont know much about GPS. There was an application which was showing GPS sattelites, but needs GPSD daemon running. This application would be very useful now, but i dont know of easy way to make it working now... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Fri, Sep 17, 2010 at 12:14 PM, Radek Polak pson...@seznam.cz wrote: Ori Pessach wrote: Well, here's what I'm getting: $GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 etc. (I'm copying this off the phone's terminal so I think I can be excused if I don't copy the whole output.) It's very similar to what you listed above, except that there are no $GPTXT lines. Any idea what that means? Sorry i dont know much about GPS. There was an application which was showing GPS sattelites, but needs GPSD daemon running. This application would be very useful now, but i dont know of easy way to make it working now... Regards Radek The GPGSA line is consistently showing that the GPS isn't getting a fix. (The line would start with A,2 or A,3 if it had 2D or 3D fix, respectively, according to the NMEA documentation I found.) I don't see any other information being dumped out of the GPS - is there perhaps an initialization procedure I can look at? Also, does anyone know which external antenna I would need to connect to the FR's GPS antenna connector? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Christ van Willegen wrote: On a related note, I have a car with integrated BlueTooth support. Recently, I tried pairing my FR with it. At some time in that process, the car displays a PIN that should be entered on the phone to complete the pairing, but there is no PIN dialog showing on the FR. Is there support for pairing w/ a PIN? If I can only pair it with my When I paired with my headset, it asked for a PIN and there was a screen that I was able to type in which is the default for most headsets. When you pair with the car there should be two options to connect, connect headset and connect handsfree unit, I got the PIN screen when I clicked the connect handsfree unit. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris m...@e4net.com writes: Anyway I tried to get my bluetooth headset to work, and I am not sure exactly what needs to be done to make this work seemlessly. This [1] page and this guy might help. Also feel free to ping me or him on irc, we do know some bluetooth tricks :) Also keep in mind that if you've got an ordinary (non-stereo, non-A2DP) headset, it's not supposed to work with mplayer and such. See [2] for the reference. [1] http://wiki.openmoko.org/wiki/User_talk:Gabrys [2] http://piotr.gabryjeluk.pl/bluetooth-on-shr -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
On Thu, Sep 16, 2010 at 7:58 AM, Jim Morris m...@e4net.com wrote: Christ van Willegen wrote: Is there support for pairing w/ a PIN? If I can only pair it with my When I paired with my headset, it asked for a PIN and there was a screen that I was able to type in which is the default for most headsets. But not for the car. It generates a PIN to use for that pairing. When you pair with the car there should be two options to connect, connect headset and connect handsfree unit, I got the PIN screen when I clicked the connect handsfree unit. Ok, let me see again and try to get this set up. I can probably check tonight. Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Thanks for the pointers Paul. Paul Fertser wrote: This [1] page and this guy might help. Also feel free to ping me or him on irc, we do know some bluetooth tricks :) Unfortunately frameworkd and the dbus stuff does not appear to be relevant for qtmoko. However those pointers did explain what the start gsm bt audio fix does which is hidden in the tools menu on qtmomo. I guess I can sniff around what you guys did for the other dists, and try to do the equivalent here, seems Radek got most of it working, but going into a shell and typing stuff to connect and disconnect would probably make the California Highway Patrol come down on you like a ton of bricks, especially since texting while driving is illegal (although it doesn't say typing shell commands is illegal ;) Anyway the main point is I need to integrate all this into the system so it all happens automatically, like on most other phones, otherwise it defeats the object of having a handsfree device. Has this been automated on the other dists, or do people still need to setup everything manually? Does qtmoko use the same version of bluez as the other dists? Do those dists handle the buttons for answering and hanging up calls? If so I can probably port some of that over unless it all uses frameworkd and dbus commands. If nothing else I can use it as a pointer to how to do it. Also keep in mind that if you've got an ordinary (non-stereo, non-A2DP) headset, it's not supposed to work with mplayer and such. See [2] for the reference. Ok that makes sense, I do have another A2DP headset, I'll see if that works differently. Thanks Jim -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
2010-09...@08:22 Christ van Willegen which is the default for most headsets. But not for the car. It generates a PIN to use for that pairing. I was able to pair my FR with my toyota and during the process I entered my pin on the dialog showed by the FR. I also was able to pair my FR with a garmin navigator. have you tried both directions for the pairing process? eg: initiate the process on the car searching your FR or vice versa ? btw I'm able to access my phone-book and last dialed numbers and also get the battery and signal status of the FR on the paired device :) -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris m...@e4net.com writes: Paul Fertser wrote: This [1] page and this guy might help. Also feel free to ping me or him on irc, we do know some bluetooth tricks :) Unfortunately frameworkd and the dbus stuff does not appear to be relevant for qtmoko. Some dbus stuff (calls to org.bluez) is relevant :) seems Radek got most of it working, but going into a shell and typing stuff to connect and disconnect would probably make the California Highway Patrol come down on you like a ton of bricks, especially since texting while driving is illegal (although it doesn't say typing shell commands is illegal ;) ROTFL -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris wrote: Also keep in mind that if you've got an ordinary (non-stereo, non-A2DP) headset, it's not supposed to work with mplayer and such. See [2] for the reference. Ok that makes sense, I do have another A2DP headset, I'll see if that works differently. Holy crap it worked! I paired with an a2dp headset and it asked to install the bluez audio via apt, then after a restart plays though the headset, Radek you are a genius ;) -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Jim Morris wrote: Jim Morris wrote: Also keep in mind that if you've got an ordinary (non-stereo, non-A2DP) headset, it's not supposed to work with mplayer and such. See [2] for the reference. Ok that makes sense, I do have another A2DP headset, I'll see if that works differently. Holy crap it worked! I paired with an a2dp headset and it asked to install the bluez audio via apt, then after a restart plays though the headset, Radek you are a genius ;) Actually all you guys that figured out the blue tooth stuff are geniuses, Radek gets special Kudos from me for getting it to work relatively seemlessly on qtmoko... Now can I get handsfree to work seemlessly? Still working on that. Sounds like it does though from Alfa21's comments. I have several handsfree devices to test it out on. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
2010-09...@00:02 Jim Morris Jim Morris wrote: Also keep in mind that if you've got an ordinary (non-stereo, non-A2DP) headset, it's not supposed to work with mplayer and such. See [2] for the reference. Ok that makes sense, I do have another A2DP headset, I'll see if that works differently. Holy crap it worked! I paired with an a2dp headset and it asked to install the bluez audio via apt, then after a restart plays though the headset, Radek you are a genius ;) hey! how I can verify my bt device supports a2dp? :S -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
On Thursday 16 September 2010 07:44:41 Jim Morris wrote: I have not tried to make a GSM call yet using the headset, but was wondering how far the BT integration has gone? Once you connect to the headset (which looks is working for you) it should work automatically. But there is problem with 2.6.29 kernel - you will have no sound until you get first incoming call. Then it should work good. Gabrys (who did all the hard work to make it working) said that with newer kernels this problem is fixed. I am now testing qtmoko v27 with 2.6.34 kernel but i have my headset at home, so i cant try right now. 1. Should it work with a GSM call? If so what else has to be done to make it work? 2. Will the headset button answer an incoming call? Yes. For me also the button was working. But beware some headsets which do not work well with freerunner [1] - i have Jabra which is ok, but motorola does not have sound. 3. Do I have to manually connect everytime I want to use the headset? or will it automatically connect when in range (like my other cells phones). My jabra connects automatically to Freerunner when it's turned on. 4. I notice in the tools there is a start gsm bt audio fix, what does that do? does it need to be done every time I start up the phone or connect to the BT headset? It's called automatically after connecting to the headset. I have it there for debugging purposes. Thanks all for the great work, this looks very good at last, maybe after waiting several years, if the BT headset stuff works, I can start using my FR as a phone ;) (BT handsfree is a legal requirement here). I am not using headset for calls so i cant tell if it's daily use ready, but it would be interesting to hear some experience... I did contribute way back to the power monitoring for qtmoko and fixing some bugs in that code, and can contribute to making BT work seemlessly, if that is possible, but I need to know how far the current integration has gone, and if anyone is actually using BT for phone calls. You are already in the hall of fame [2] :) I do not really need BT to work for the media players, or voice recording but it would be nice. It works in qtmoko too - if your headset supports it. You will have to select something like available services from device context menu and then there should appear connect A2DP button. It's bug that the button does not appear automatically but then it should work. Regards Radek [1] http://wiki.openmoko.org/wiki/List_of_bluetooth_headsets [2] http://activationrecord.net/radekp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Am 16.09.2010 00:09, schrieb Francesco De Vita: I also noted this issue, but the proper icon is there! Maybe something went wrong during compilation and the conversion process form the .png to .pic. Anyway, just for a momentaneous workaround, put the call.png (attached) in to /opt/qtmoko/pics/themes/finximod and rename the file call.pic in something else like callOLD.pic or whatever you want (the theme configuration file looks for the files without the file extensions). Restart QtMoko and you will have the icon for missed calls ;) Joif Hello Radek and Team, Just flashed v26 and I've got a totally new FR in my hands. Thanks alot guys! Just one thing: Is it possible that the icon for missed phone calls is - well - missing? I'm using that new theme and it displays an icon for missed text-messages. If I miss a call there's just a blank space and the call counter. Daniel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Joif, speedy answer sir! Works like a charm - thanks. I'd notice the same glitch with the neronGPS-icon. Everything got installed correctly but no icon in the launcher... Anyway everything's working now... BTW: great theme Daniel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
Hi Radek, Great job, I have been away from the FR for a while, but I am back to see if I can finally use it as a phone, and it looks like I may be able to now with this bluetooth stuff. Its nice to see that my qtpedometer (with car finder) still works, which is just as well as I have totally forgotten how to build apps for qtmoko ;) I have several bt headsets and handsfree devices, so this is what I have found so far My plantronics earpiece works great, automatically connects when it is on, and the button accepts and hangs up calls. My Motorola T505 handsfree device also works, but the button does not accept or hangup calls, ditto with the VR handsfree device I have. (This is a serious problem for me when in the car). My IOGear stereo headset connects via A2DP, and works with mplayer (although rather choppy), and only appears to be mono. I have an in-car builtin bluetooth, which I haven't tried yet, it has buttons on the steering wheel to accept and hangup calls. I'll do some research to see why the headset button works but the handsfree doesn't, unless someone can point me to the problem. Its amazing that you were able to integrate all this into qtmoko! The incoming call first is a bit of a problem but I can live with that for a while. Thanks Jim Radek Polak wrote: On Thursday 16 September 2010 07:44:41 Jim Morris wrote: I have not tried to make a GSM call yet using the headset, but was wondering how far the BT integration has gone? Once you connect to the headset (which looks is working for you) it should work automatically. But there is problem with 2.6.29 kernel - you will have no sound until you get first incoming call. Then it should work good. Gabrys (who did all the hard work to make it working) said that with newer kernels this problem is fixed. I am now testing qtmoko v27 with 2.6.34 kernel but i have my headset at home, so i cant try right now. 1. Should it work with a GSM call? If so what else has to be done to make it work? 2. Will the headset button answer an incoming call? Yes. For me also the button was working. But beware some headsets which do not work well with freerunner [1] - i have Jabra which is ok, but motorola does not have sound. 3. Do I have to manually connect everytime I want to use the headset? or will it automatically connect when in range (like my other cells phones). My jabra connects automatically to Freerunner when it's turned on. 4. I notice in the tools there is a start gsm bt audio fix, what does that do? does it need to be done every time I start up the phone or connect to the BT headset? It's called automatically after connecting to the headset. I have it there for debugging purposes. Thanks all for the great work, this looks very good at last, maybe after waiting several years, if the BT headset stuff works, I can start using my FR as a phone ;) (BT handsfree is a legal requirement here). I am not using headset for calls so i cant tell if it's daily use ready, but it would be interesting to hear some experience... I did contribute way back to the power monitoring for qtmoko and fixing some bugs in that code, and can contribute to making BT work seemlessly, if that is possible, but I need to know how far the current integration has gone, and if anyone is actually using BT for phone calls. You are already in the hall of fame [2] :) I do not really need BT to work for the media players, or voice recording but it would be nice. It works in qtmoko too - if your headset supports it. You will have to select something like available services from device context menu and then there should appear connect A2DP button. It's bug that the button does not appear automatically but then it should work. Regards Radek [1] http://wiki.openmoko.org/wiki/List_of_bluetooth_headsets [2] http://activationrecord.net/radekp/qtmoko/ -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Hi, I installed v26 over the weekend and had some time to try and use it. I've seen a few serious issues, and some improvements. First, the good news: * WiFi works - for the first time for me. The browser isn't terribly useful, I'm afraid, but it's nice to at least have the phone connect properly. Nice! * I was able to use my bluetooth headset to make and receive calls. That's also a first for me. The UI is maddeningly confusing, I can never figure out whether the headset works or not until I try it, but at least I can use the headset, which is an improvement. I noticed a few problems: * The number one issue I'm seeing is power management. The phone doesn't seem to switch to the correct power management profile when I unplug the charger, resulting in it draining the battery in a couple of hours. This is a significant problem for me since I usually grab it, unplug the charger, and leave the house in a hurry before my brain is fully engaged and functional in the morning, so workarounds like going into the power management screen and out of it to apply the correct settings aren't really an option for me. :) * GPS doesn't work. The longest I left it running to try and get lock was 20 minutes - no luck with that. What should I look at? * The software has an ongoing problem processing T-Mobile's (USA) text messages that are sent when calling voice mail. A message from 129 is delivered as soon as I call voice mail, and the software insists on displaying a dialog right away. The stacking order for dialogs appears to be arbitrary, sometime making it impossible to dismiss the dialog while in the dialer with the numeric pad active. This can make it impossible to use the voice mail voice prompts. Ideally, the messages should be filtered and not delivered to the text message inbox at all - instead, they should be used to flip an indicator in the UI that voice mail is available. * The UI crashes when I play with the BT headset too much - pressing the headset's button a few times reliably crashes the UI, resulting in a black console screen with a few garbage characters in the corner. The UI restarts, eventually, but it takes a couple of minutes during which the phone is effectively dead. Any pointers on where to start fixing some of these would be appreciated. Thanks, -- Ori Pessach On Sat, Aug 28, 2010 at 2:31 PM, Radek Polak pson...@seznam.cz wrote: Hello, qtmoko has new v26 release. You can get it from our sourceforge page [1]. Qtmoko is distribution for Openmoko Freerunner phone based on debian and qtopia. You can find more info here [2] [3] [4]. Here is list of changes since previous stable version (v24): * Fixed WS (white screen) problem in qmplayer QX rotation (Gennady Kupava) * Fixed unresponsive touchscreen after resume (Gennady Kupava) * Better mass storage scripts (Alex Samorukov) * Use blue indicator is used for wifi activity (Alex Samorukov) * Reconnect wifi after resume (Alex Samorukov) * Updated QtMaze with better graphics and other enhancements (Anton Olkhovik) * We use kernel modules for bluetooth * QMplayer supports command line arguments (Anton Olkhovik) * QMplayer support for youtube videos (Anton Olkhovik) * QMplayer can encode videos suitable for Freerunner's screen * More reliable GPRS connection (Alex Samorukov) * Dont mount /var/cache/apt for SD card images which makes apt work better * Working for bluetooth hands free for GSM calls * Shell scripts that are executed on suspend/resume (Piotr Gabryjeluk) * APGS and GPS standby support (Piotr Gabryjeluk) * Fixed When locked power management mode * Bigger QTerminal (no tabs whith only one session) * Support for A2DP bluetooth audio * Raptor - GUI for apt package manager * QMplayer - support for playlists (Anton Olkhovik) * New nice theme called finximod (Joif) * Stripped kernel modules for saving more space * Deleted unused dejavu fonts for more space * Use stylesheet for better html forms rendering in Arora (Ant+Alex) * Arora supports downloading and playing youtube videos (Anton Olkhovik) * Arora is smaller uses tab labels and better animation (Alex Samorukov) * Tab bar size and zooming as upstream Arora does (Alex Samorukov) * Fixed not found error page in Arora (Alex Samorukov) * We have kernel sources on github [5] * New apps - qweather (Anton Olkhovik) and qneoriod game (Bala) * PDF support in eyepiece (Alex Samorukov) * Fixed crashing qdictopia (Alex Samorukov) Most of the changes dont need comments, but some require explanation. First of all kernel fixes from Gennady deserve big credit. Finally after years you should not see any white screen. Watching videos in qvga and rotating X server now works flawlessly. Thanks! Kernel sources with current .config can be found on github [5]. Updated instructions for building are in rootfs howto [6]. You can now watch youtube videos from Arora web browser. Nice howto is here [7]. There is currently problem that mplayer cant handle flv
Re: QtMoko v26
Hi, Ori, * GPS doesn't work. The longest I left it running to try and get lock was 20 minutes - no luck with that. What should I look at? So far FPS worked in 100% of cases if you'll follow this procedure 1. start nerongps. 2. cache maps 3. close nerogps 4. go to street (really) 5. start nerongps. 6. wait for 5(!) minutes (usually only 1-2minutes needed) 7. it should work. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Seriously? I think you and I might have different ideas about what works mean. :) The only network connectivity I have with this phone is WiFi. I can't get GPS lock indoors, and I probably can't get a WiFi signal outdoors. Besides, if I can get a WiFi signal, I probably don't need GPS to know where I am... Very curious. Is there, perhaps, another application I can use to just get GPS coordinates and verify that this works, at least? -- Ori Pessach On Thu, Sep 16, 2010 at 9:27 AM, Gennady Kupava g...@bsdmn.com wrote: Hi, Ori, * GPS doesn't work. The longest I left it running to try and get lock was 20 minutes - no luck with that. What should I look at? So far FPS worked in 100% of cases if you'll follow this procedure 1. start nerongps. 2. cache maps 3. close nerogps 4. go to street (really) 5. start nerongps. 6. wait for 5(!) minutes (usually only 1-2minutes needed) 7. it should work. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
В Чтв, 16/09/2010 в 10:52 -0600, Ori Pessach пишет: Seriously? I think you and I might have different ideas about what works mean. :) Seriously? Even my Garmin can't get fix indoors. Have you tried other devices? GPS is FR is not best one, but it is open for fixes. on qtmoko it is not less or more functional than in other distros. Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
2010-09...@10:52 Ori Pessach The only network connectivity I have with this phone is WiFi. I can't get GPS lock indoors, and I probably can't get a WiFi signal outdoors. gennady was saying just to save your maps (using any kind of internet connection, eg your wifi) before your trip outdoor... so you'll see your fixed point on your cached maps. once you have your maps saved on your moko you do not need any kind of connection, just your gps fix in open air. gps does not get a fix in indoor by gps design, and it's not a bug. -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
I don't think I explained myself very clearly. I don't expect the GPS to get a fix indoors - only to get a fix outdoors without also being indoors so it can pick up a WiFi signal which is required in my case to go through the rest of the steps you listed. (caching the maps - is this really necessary for getting a fix?) I just took my FR outdoors for a walk. I was holding it in my hand, there was a clear view of most of the sky, and it didn't get a fix after 15 minutes. So, where do I start? Is there a log file somewhere that I can look at to see what's going on? -- Ori Pessach On Thu, Sep 16, 2010 at 10:05 AM, Gennady Kupava g...@bsdmn.com wrote: В Чтв, 16/09/2010 в 10:52 -0600, Ori Pessach пишет: Seriously? I think you and I might have different ideas about what works mean. :) Seriously? Even my Garmin can't get fix indoors. Have you tried other devices? GPS is FR is not best one, but it is open for fixes. on qtmoko it is not less or more functional than in other distros. Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Again, I don't expect to get GPS fix indoors, or underground, in instantaneously. I would expect to get a fix after 15-20 minutes in my back yard or outdoors in an area with low buildings and a clear view of the sky. I live in Colorado - that's what we have here. It doesn't work this way for me. How do I debug it? -- Ori Pessach On Thu, Sep 16, 2010 at 11:40 AM, Alfa21 freerun...@my.is.it wrote: 2010-09...@10:52 Ori Pessach The only network connectivity I have with this phone is WiFi. I can't get GPS lock indoors, and I probably can't get a WiFi signal outdoors. gennady was saying just to save your maps (using any kind of internet connection, eg your wifi) before your trip outdoor... so you'll see your fixed point on your cached maps. once you have your maps saved on your moko you do not need any kind of connection, just your gps fix in open air. gps does not get a fix in indoor by gps design, and it's not a bug. -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Ori Pessach wrote: Again, I don't expect to get GPS fix indoors, or underground, in instantaneously. I would expect to get a fix after 15-20 minutes in my back yard or outdoors in an area with low buildings and a clear view of the sky. I live in Colorado - that's what we have here. Try getting qtpedometer, it can be installed via the qt package manager. It will give a simple fix with coords. I found that sometimes I need to leave the FR standing upright outside and do not move it for 2-5 minutes to get a fix. The reason is that initially it needs to download the entire ephemeral, and everytime it drops a byte it has to start again, So leaving it stationary while it is downloading helps. Once it gets the entire ephemeral the next fix should be very quick, especially with the new save of agps. I was surprised that I actually got a fix indoors and instantly got them again after the first one after upgrading to v26. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
В Чтв, 16/09/2010 в 11:51 -0600, Ori Pessach пишет: I don't think I explained myself very clearly. I don't expect the GPS to get a fix indoors - only to get a fix outdoors without also being indoors so it can pick up a WiFi signal which is required in my case to go through the rest of the steps you listed. (caching the maps - is this really necessary for getting a fix?) To get first fix, _stay at one position_ outdoor for a while (try 5 minutes, but you should get it 1-2 minutes). After you'll get a fix, it will work without problems. If not, try restart your nerongps. To debug, open GPS serial port in terminal but i don't know details. And yes, really i just told you to download map before going outdoor :) Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
В Чтв, 16/09/2010 в 11:51 -0600, Ori Pessach пишет: (caching the maps - is this really necessary for getting a fix?) Of course not, just it is not fun to watch empty nerongps screen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
I didn't mention it, but I did just that. I stood in a field, looking at grasshoppers for 5 minutes. That's when I decided to take a walk. This weekend, I left my FR on a table in the back yard for 20 minutes. Still no fix. -- Ori Pessach On Thu, Sep 16, 2010 at 11:25 AM, Gennady Kupava g...@bsdmn.com wrote: В Чтв, 16/09/2010 в 11:51 -0600, Ori Pessach пишет: I don't think I explained myself very clearly. I don't expect the GPS to get a fix indoors - only to get a fix outdoors without also being indoors so it can pick up a WiFi signal which is required in my case to go through the rest of the steps you listed. (caching the maps - is this really necessary for getting a fix?) To get first fix, _stay at one position_ outdoor for a while (try 5 minutes, but you should get it 1-2 minutes). After you'll get a fix, it will work without problems. If not, try restart your nerongps. To debug, open GPS serial port in terminal but i don't know details. And yes, really i just told you to download map before going outdoor :) Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
I can now attest to the fact that staring at the maps without getting a fix is only marginally more fun than that. -- Ori Pessach On Thu, Sep 16, 2010 at 11:26 AM, Gennady Kupava g...@bsdmn.com wrote: В Чтв, 16/09/2010 в 11:51 -0600, Ori Pessach пишет: (caching the maps - is this really necessary for getting a fix?) Of course not, just it is not fun to watch empty nerongps screen. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Ori Pessach wrote: I didn't mention it, but I did just that. I stood in a field, looking at grasshoppers for 5 minutes. That's when I decided to take a walk. Â This weekend, I left my FR on a table in the back yard for 20 minutes. Still no fix. Ok, so a couple of things you can try... take out the memry card if you have one in, on older models having that in could cause enough interference to stop the gps getting a fix, The other thing to try is check the gps external antenna connector, sometimes it can come loose and stop the signal. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
What would be considered an older model? Are you referring to the model of the FR, or the memory card? And where should I look at the GPS antenna connector? It looks secure from the outside. I'd also like to mention that I was able to get GPS fix before with this hardware, but that was a while ago. -- Ori Pessach On Thu, Sep 16, 2010 at 12:48 PM, Jim Morris m...@e4net.com wrote: Ori Pessach wrote: I didn't mention it, but I did just that. I stood in a field, looking at grasshoppers for 5 minutes. That's when I decided to take a walk. Â This weekend, I left my FR on a table in the back yard for 20 minutes. Still no fix. Ok, so a couple of things you can try... take out the memry card if you have one in, on older models having that in could cause enough interference to stop the gps getting a fix, The other thing to try is check the gps external antenna connector, sometimes it can come loose and stop the signal. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Thu, 16 Sep 2010, Ori Pessach wrote: I'd also like to mention that I was able to get GPS fix before with this hardware, but that was a while ago. I don't know if this is available on QtMoko and don't know the package managing system - on SHR I did in such cases: opkg install gps-utils gpspipe -r localhost Check if there comes out some NMEA data which looks somehow reasonable (changing) or rather static. opkg install openmoko-agpsui Run openmoko-agpsui (from the console maybe) It shows the output of gpspipe in a GUI, and even if you don't have a fix, you can see if the GPS chip receives signals from satelites, how many of them, the signal strength etc. You also can cold/warm/hot reset the GPS chip etc. Extremely useful tool for such cases. I had a similair case where first the kernal support for GPS changes/was broken, then in the same time I somehow managed to break the _very_ thin coax cable to the GPS antenna, and it was very troublesome to track this down... A. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Thanks - I'll give this a try. On Thu, Sep 16, 2010 at 1:10 PM, Alexander Lehner leh...@edv-buero-lehner.de wrote: On Thu, 16 Sep 2010, Ori Pessach wrote: I'd also like to mention that I was able to get GPS fix before with this hardware, but that was a while ago. I don't know if this is available on QtMoko and don't know the package managing system - on SHR I did in such cases: opkg install gps-utils gpspipe -r localhost Check if there comes out some NMEA data which looks somehow reasonable (changing) or rather static. opkg install openmoko-agpsui Run openmoko-agpsui (from the console maybe) It shows the output of gpspipe in a GUI, and even if you don't have a fix, you can see if the GPS chip receives signals from satelites, how many of them, the signal strength etc. You also can cold/warm/hot reset the GPS chip etc. Extremely useful tool for such cases. I had a similair case where first the kernal support for GPS changes/was broken, then in the same time I somehow managed to break the _very_ thin coax cable to the GPS antenna, and it was very troublesome to track this down... A. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Ori Pessach wrote: Hi, I installed v26 over the weekend and had some time to try and use it. I've seen a few serious issues, and some improvements. * The software has an ongoing problem processing T-Mobile's (USA) text messages that are sent when calling voice mail. A message from 129 is delivered as soon as I call voice mail, and the software insists on displaying a dialog right away. The stacking order for dialogs appears to be arbitrary, sometime making it impossible to dismiss the dialog while in the dialer with the numeric pad active. This can make it impossible to use the voice mail voice prompts. Ideally, the messages should be filtered and not delivered to the text message inbox at all - instead, they should be used to flip an indicator in the UI that voice mail is available. I have this same issue, its been there since day one. I'd be happy to fix this issue if someone can point me in the rough direction of where in qtmoko you would handle these messages. I think this was fixed in the other dists, but every carrier has different codes for different things, so handling it in a way that does not break other carriers will be the challenge. -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Am 28.08.2010 22:31, schrieb Radek Polak: Hello, qtmoko has new v26 release. You can get it from our sourceforge page [1]. Qtmoko is distribution for Openmoko Freerunner phone based on debian and qtopia. You can find more info here [2] [3] [4]. Here is list of changes since previous stable version (v24): * Fixed WS (white screen) problem in qmplayer QX rotation (Gennady Kupava) * Fixed unresponsive touchscreen after resume (Gennady Kupava) * Better mass storage scripts (Alex Samorukov) * Use blue indicator is used for wifi activity (Alex Samorukov) * Reconnect wifi after resume (Alex Samorukov) * Updated QtMaze with better graphics and other enhancements (Anton Olkhovik) * We use kernel modules for bluetooth * QMplayer supports command line arguments (Anton Olkhovik) * QMplayer support for youtube videos (Anton Olkhovik) * QMplayer can encode videos suitable for Freerunner's screen * More reliable GPRS connection (Alex Samorukov) * Dont mount /var/cache/apt for SD card images which makes apt work better * Working for bluetooth hands free for GSM calls * Shell scripts that are executed on suspend/resume (Piotr Gabryjeluk) * APGS and GPS standby support (Piotr Gabryjeluk) * Fixed When locked power management mode * Bigger QTerminal (no tabs whith only one session) * Support for A2DP bluetooth audio * Raptor - GUI for apt package manager * QMplayer - support for playlists (Anton Olkhovik) * New nice theme called finximod (Joif) * Stripped kernel modules for saving more space * Deleted unused dejavu fonts for more space * Use stylesheet for better html forms rendering in Arora (Ant+Alex) * Arora supports downloading and playing youtube videos (Anton Olkhovik) * Arora is smaller uses tab labels and better animation (Alex Samorukov) * Tab bar size and zooming as upstream Arora does (Alex Samorukov) * Fixed not found error page in Arora (Alex Samorukov) * We have kernel sources on github [5] * New apps - qweather (Anton Olkhovik) and qneoriod game (Bala) * PDF support in eyepiece (Alex Samorukov) * Fixed crashing qdictopia (Alex Samorukov) Most of the changes dont need comments, but some require explanation. First of all kernel fixes from Gennady deserve big credit. Finally after years you should not see any white screen. Watching videos in qvga and rotating X server now works flawlessly. Thanks! Kernel sources with current .config can be found on github [5]. Updated instructions for building are in rootfs howto [6]. You can now watch youtube videos from Arora web browser. Nice howto is here [7]. There is currently problem that mplayer cant handle flv files. I think this is due to changes in youtube videos format, because it worked with apt-get installed mplayer before. But you can download the video and encode it to mp4 in qmplayer right on the device. QtMoko should now save AGPS data before GPS is switched off (e.g. after you end NeronGPS). After GPS is switched on, it will supply those stored data and you will get fast fix. AGPS data is stored in /var/cache/agpsdata. Bluetooth headsets can be now used for both audio and GSM calls. GSM calls needed fix because of kernel bug. The fix is userspace program gta02-gsm-bt-fix by Gabrys and is started/stoped when handsfree connects/disconnects. There is problem that you must have incomming call first. If you make outgoing call first, you will have no audio. This should be fixed in newer kernels but we dont know fix for 2.6.29 kernel used in this release. A2DP (bluetooth audio) support works too but with some glitches. You need headset with A2DP support. After pairing press Supported services from bluetooth device context menu. New button Connect audio (A2DP) should then appear. Sometimes it fails to connect. For me it help putting headset in pairing mode, restart phone and then the button works. If you make the bluetooth audio device default it will work in all alsa programs, but expect problems e.g. with GSM calls. If you dont make it default GSM will be ok. However only QMplayer can detect it and use it now. Other changes should not need more explanation, but if you would like to know some details i will be happy to answer questions. Thanks for everybody who helped with this release. I hope you'll like the changes and new features. Cheers Radek [1] https://sourceforge.net/projects/qtmoko/files/ [2] http://qtmoko.org/ [3] http://activationrecord.net/radekp/qtmoko/ [4] http://github.com/radekp [5] http://github.com/radekp/linux-2.6 [6] http://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt [7] http://activationrecord.net/radekp/pub/qtmoko_youtube_howto.jpg ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Hello Radek and Team, Just flashed v26 and I've got a totally new FR in my hands. Thanks alot guys! Just one thing: Is it
Re: QtMoko v26
I also noted this issue, but the proper icon is there! Maybe something went wrong during compilation and the conversion process form the .png to .pic. Anyway, just for a momentaneous workaround, put the call.png (attached) in to /opt/qtmoko/pics/themes/finximod and rename the file call.pic in something else like callOLD.pic or whatever you want (the theme configuration file looks for the files without the file extensions). Restart QtMoko and you will have the icon for missed calls ;) Joif Hello Radek and Team, Just flashed v26 and I've got a totally new FR in my hands. Thanks alot guys! Just one thing: Is it possible that the icon for missed phone calls is - well - missing? I'm using that new theme and it displays an icon for missed text-messages. If I miss a call there's just a blank space and the call counter. Daniel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community attachment: call.png___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtmoko v26 bluetooth headset
Hi, I upgraded to v26 of qtmoko and it looks pretty darn good! Wifi worked out of the box with wpa/psk which is an awesome feat! Anyway I tried to get my bluetooth headset to work, and I am not sure exactly what needs to be done to make this work seemlessly. I paired OK, I connected as handsfree, and the headset beeped. Clicking the headset button did not do anything, it should usually recall the last number or bringup the dialing screen. Neither of the media players (mplayer and the other one) played through the headset, and voice record did not record or playback through the headset either. I have not tried to make a GSM call yet using the headset, but was wondering how far the BT integration has gone? 1. Should it work with a GSM call? If so what else has to be done to make it work? 2. Will the headset button answer an incoming call? 3. Do I have to manually connect everytime I want to use the headset? or will it automatically connect when in range (like my other cells phones). 4. I notice in the tools there is a start gsm bt audio fix, what does that do? does it need to be done every time I start up the phone or connect to the BT headset? Thanks all for the great work, this looks very good at last, maybe after waiting several years, if the BT headset stuff works, I can start using my FR as a phone ;) (BT handsfree is a legal requirement here). I did contribute way back to the power monitoring for qtmoko and fixing some bugs in that code, and can contribute to making BT work seemlessly, if that is possible, but I need to know how far the current integration has gone, and if anyone is actually using BT for phone calls. I do not really need BT to work for the media players, or voice recording but it would be nice. Thanks -- Jim Morris, http://blog.wolfman.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v26 bluetooth headset
On Thu, Sep 16, 2010 at 7:44 AM, Jim Morris m...@e4net.com wrote: Anyway I tried to get my bluetooth headset to work, and I am not sure exactly what needs to be done to make this work seemlessly. On a related note, I have a car with integrated BlueTooth support. Recently, I tried pairing my FR with it. At some time in that process, the car displays a PIN that should be entered on the phone to complete the pairing, but there is no PIN dialog showing on the FR. Is there support for pairing w/ a PIN? If I can only pair it with my car to make phone calls, that's OK. I don't need the 'fancy' stuff like downloading my phone book into the car (and stuff like that). Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
I've got a messag from my girlfriend, who wants to thanks a lot Radek Team ! Their work makes me have a phone that works, with more battery, and audible voice. So she can reach me while I'm at my Linux User Group, telling me I have to come back to home instead if drinking beers explaining Freerunner is a great machine So a great thanks from her, and a half one from me ;-) Virginie Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
I, too, have experienced QtMoko. The one thing that annoys me, is that sometimes (well, more often than sometimes...) my FR turns on at night, and stays on until it wakes me from sleep indicating it's hungry... My wife doesn't approve :-( What could be wrong? Christ van Willegen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
В Втр, 14/09/2010 в 11:08 +0200, Christ van Willegen пишет: I, too, have experienced QtMoko. The one thing that annoys me, is that sometimes (well, more often than sometimes...) my FR turns on at night, and stays on until it wakes me from sleep indicating it's hungry... My wife doesn't approve :-( What could be wrong? hehe ThibG even had QTMoko booted then it were shut down! We found in IRC that this is someone spirit. It comes almost exactly at 2:00. But probably this is just alarm. And +2 seem just default timezone. Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Tuesday 14 September 2010 11:08:56 Christ van Willegen wrote: I, too, have experienced QtMoko. The one thing that annoys me, is that sometimes (well, more often than sometimes...) my FR turns on at night, and stays on until it wakes me from sleep indicating it's hungry... My wife doesn't approve :-( What could be wrong? This happened to me several time too. No idea what is reason for such wake up, but you should set suspend intervals in Settings-Power management. I am personally using: On battery: suspend 5minutes When locked: suspend in 20 seconds I think these are quite safe settings. I am always locking screen and it suspends after 20s. If you forget to lock the screen the 5minutes on battery interval will trigger and you should never endup with suddenly empty battery. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Tue, Sep 14, 2010 at 11:37 AM, Radek Polak pson...@seznam.cz wrote: On Tuesday 14 September 2010 11:08:56 Christ van Willegen wrote: I, too, have experienced QtMoko. The one thing that annoys me, is that sometimes (well, more often than sometimes...) my FR turns on at night, and stays on until it wakes me from sleep indicating it's hungry... My wife doesn't approve :-( What could be wrong? This happened to me several time too. No idea what is reason for such wake up, but you should set suspend intervals in Settings-Power management. I am personally using: On battery: suspend 5minutes When locked: suspend in 20 seconds I have settings like these, and it still drains the battery... I'll check what I have in config. On battery: Suspend 1m Plugged in: Suspend 5m When locked: Suspend 40s But, I know for sure that it still drains the battery... Christ van Willegen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Tue, Sep 14, 2010 at 11:55 AM, Christ van Willegen cvwille...@gmail.com wrote: I have settings like these, and it still drains the battery... I'll check what I have in config. On battery: Suspend 1m Plugged in: Suspend 5m When locked: Suspend 40s But, I know for sure that it still drains the battery... At this moment, my FR is showing the 'lock' screen, full brightness. After a few seconds, I can see the screen dim. A few seconds after that, the screen turns fully off, and within a second goes back to full brightness. Repeat ad inf. Christ van Willegen -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Tuesday 14 September 2010 12:01:17 Christ van Willegen wrote: At this moment, my FR is showing the 'lock' screen, full brightness. After a few seconds, I can see the screen dim. A few seconds after that, the screen turns fully off, and within a second goes back to full brightness. Repeat ad inf. You can try mine intervals. If it does not help, we need to know what wakes the phone up. There should be file called resume_reason or something like that in /sys which reads what made the phone resume from suspend. You could make a script that periodically outputs content of that file. Then run the script (in qterminal) and try to make the phone sleep. After it wakes you should have the reason for wakup - it will be interesting for us and we could try to find the reason. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
2010-09...@11:37 Radek Polak On battery: suspend 5minutes When locked: suspend in 20 seconds hi radek and hi to all the community in general :) on this topic I'd like to open a debate... I think the suspend setting in on cable (I'm personally using it as disabled timeout here) should have priority over the suspend setting in locked because if you are on ssh over usb (or usb mass storage) and put (or keep) your FR in locked mode you'll loose the connection. this also because I usually have the on battery and when locked both with battery saving schemes as you (I am always locking screen too!) and I forget to unlock my FR when I plug the usb cable in it. what do you think? is it possible to change the priorities like: CABLE over LOCK over BATTERY ? do you think this use case is reasonable/common? -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
what do you think? is it possible to change the priorities like: CABLE over LOCK over BATTERY ? do you think this use case is reasonable/common? Hi, one should take into consideration whether the battery will be charged in suspend or not. If the battery can not charge while the phone is suspended, then cable should have maximum priority and avoid suspending the device (unless we are on 100mA USB-power only). But generally having cable override everything sounds reasonable because of the ssh case. Peter ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
+1 have the same issues with the current settings Raphael On Tue, 14 Sep 2010 19:30:45 +0200, Alfa21 freerun...@my.is.it wrote: 2010-09...@11:37 Radek Polak On battery: suspend 5minutes When locked: suspend in 20 seconds hi radek and hi to all the community in general :) on this topic I'd like to open a debate... I think the suspend setting in on cable (I'm personally using it as disabled timeout here) should have priority over the suspend setting in locked because if you are on ssh over usb (or usb mass storage) and put (or keep) your FR in locked mode you'll loose the connection. this also because I usually have the on battery and when locked both with battery saving schemes as you (I am always locking screen too!) and I forget to unlock my FR when I plug the usb cable in it. what do you think? is it possible to change the priorities like: CABLE over LOCK over BATTERY ? do you think this use case is reasonable/common? -- Dipl.-Medieninf. Raphael Wimmer Wiss. Mitarbeiter / Research Assistant Doktorand / PhD student Ludwig-Maximilians-Universität München E-Mail: raphael.wim...@ifi.lmu.de LFE Medieninformatik Skype: real_raphman Amalienstr. 17 / Raum 206WWW: http://www.medien.ifi.lmu.de 80333 MünchenTel:+49 (89) 2180-4659 Germany Fax:+49 (89) 2180-99-4659 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Alfa21 wrote: what do you think? is it possible to change the priorities like: CABLE over LOCK over BATTERY ? do you think this use case is reasonable/common? Yes it's reasonable, but the way how it works was easiest to implement ;-) I will try to take a look if i can fix it so that it works as you suggest - or maybe some else want to send patch? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26 power priorities debate
2010-09...@20:39 Radek Polak Alfa21 wrote: what do you think? is it possible to change the priorities like: CABLE over LOCK over BATTERY ? do you think this use case is reasonable/common? Yes it's reasonable, but the way how it works was easiest to implement ;-) I will try to take a look if i can fix it so that it works as you suggest - or maybe some else want to send patch? Regards Radek mhm... IIRC that was a workaround done because there was a bug (in an old qtmoko's monolithic kernel / module) which prevented to tell apart battery or cable status (now fixed also without this workaround) the alternatives I see are: 1) (maybe really the easiest to implement) imho we could do a rollback to the previous state before that hack and take the habit of pressing the powerbttn shortly to immediately activate the sleep if desired (or wait for the suspend timeout if set) as it's possible also when the screen is locked 2) fix the priority as said before, so if we have the cable connected (and now i see it's correctly detected, can you confirm?) we follow the full triplet (dimm/disp.off/suspend) of the on cable whit priority over all the triplet of the locked state 3) find a way to check if we have a connection open and in this case ignore the suspend timeout. this could be interesting also when we are talking about a wifi connection or a car bluetooth system connection (if the FR goes in suspend we loose the ability to make outgoing calls from the system because we can't wake it by bluetooth) ...more or less the same way FR does not go in suspend during a phone call :P I would choose the 1+3 solution... with 1 ready there and 3 implementable in a more future release. what do you think? the debate is still open to the whole community! hehe ;) -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Thomas HOCEDEZ wrote: Whooo, using QTMokov26 for some days now, and it's a really allday phone now. But allday until when ? Because when I try an apt-get update... Bing!* : no space left on device ! Does anyone has a turnaround aor a real solution to this ? Hi Thomas, if you are you running from NAND it could be because apt-get uses mmap which is not available on jffs2. Because of it we have tmpfs mount in /etc/fstab which mounts RAM filesystem for apt with only limited capacity. It can help to reboot FR which clears the tmpfs mount. Or you can do: mount -o bind /path/to/some/dir/on/ext3/filesystem/on/SD/card /var/cache/apt I hope this will be later fixed by switching to some newer flash filesystem (there are lot of choices in 2.6.34 kernels). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community That's what I did, and of course, it works like a charm ! Thanks a lot, but don't spend too much time on this list, go back to work on the v27 ;-) Cheers, Asthro -- Thomas HOCEDEZ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gprs bug QtMoko v26
Alex Samorukov wrote: My idea is to disable internal qtmoko multiplexer and use external daemon and configure qtopia to use multiply ports. IIRC there is some multiplexer also in recent linux kernel. It would be also nice to check if it works. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Thomas HOCEDEZ wrote: Whooo, using QTMokov26 for some days now, and it's a really allday phone now. But allday until when ? Because when I try an apt-get update... Bing!* : no space left on device ! Does anyone has a turnaround aor a real solution to this ? Hi Thomas, if you are you running from NAND it could be because apt-get uses mmap which is not available on jffs2. Because of it we have tmpfs mount in /etc/fstab which mounts RAM filesystem for apt with only limited capacity. It can help to reboot FR which clears the tmpfs mount. Or you can do: mount -o bind /path/to/some/dir/on/ext3/filesystem/on/SD/card /var/cache/apt I hope this will be later fixed by switching to some newer flash filesystem (there are lot of choices in 2.6.34 kernels). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
[cut] Hi Thomas, if you are you running from NAND it could be because apt-get uses mmap which Hi Radek, could this also trigger this bug? http://bugs.qtmoko.org/view.php?id=175 [cut] -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Email secured by Check Point ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v26
gr8t work... Radek and Team. :-) -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v26-tp5473480p5521183.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Patryk Benderz wrote: Hi Radek, could this also trigger this bug? http://bugs.qtmoko.org/view.php?id=175 [cut] Yes i think it's the same problem. See my comment there. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gprs bug QtMoko v26
Alfa21 wrote: hello, I'm having troubles too... I tried also an old (at the time was working) gprs chat file for my provider found in a backup of mine, but without success now. I checked also empirically with my HI-FI amplifier the rf noise: when I check my credit, start a call or send an sms I'm able to listen the typical tarata-tarata-tarata... but when I launch the gprs connection all is quiet! deep silence! so, imho, something is not working in the latest qtmoko release. (I can remember v19 was ok for sure) kind regards, a. I tried with v26 after correcting the line in /home/root/Applications/Network/chat/connect-dialup and it worked. But i had sometimes problems to get GPRS online too. Maybe it can be also related to debug/nodebug kernels, because i am not aware that anyting GPRS related changed in rootfs. You can try to experiment with AT log or disable multiplexing, but i dont know anything better for now. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gprs bug QtMoko v26
You can try to experiment with AT log or disable multiplexing, but i dont know anything better for now. Regards Radek hi radek, i tried rebooting with mux and deepsleep both disabled (neocontrol) and checked the at log (temporarily enabled)... all was ok and i can use arora with my gprs connection. i reverted back mux and deepsleep, rebooted with on/on and my gprs is still ok! :) i do not understand what was wrong before... but now all should be the same again, instead my gprs works a lot well :D btw, i can confirm sometimes the first attempt to start the gprs blink a while but fails... just try again and it's ok. kind regards, a. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gprs bug QtMoko v26
On 09/10/2010 10:50 AM, Radek Polak wrote: I tried with v26 after correcting the line in /home/root/Applications/Network/chat/connect-dialup and it worked. But i had sometimes problems to get GPRS online too. Maybe it can be also related to debug/nodebug kernels, because i am not aware that anyting GPRS related changed in rootfs. Hi Radek, I think that it is caused by internal multiplexer - sometime it start to work incorrectly. I don`t think that its kernel related. My idea is to disable internal qtmoko multiplexer and use external daemon and configure qtopia to use multiply ports. I hope i will have some time to play with this in the feature, but still not sure when this could happens. You can try to experiment with AT log or disable multiplexing, but i dont know anything better for now. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Whooo, using QTMokov26 for some days now, and it's a really allday phone now. But allday until when ? Because when I try an apt-get update... Bing!* : no space left on device ! Does anyone has a turnaround aor a real solution to this ? thanks you all (and a special big up to Radek ;-)) AstHrO / Openmoko-fr.org http://www.tlbc.fr/Espace_Client/html/suivilivraisons/html/recherche/detailtransporteur.php?NumCdeTrans=82125*(tm)(c)(r) 2010 Micro-somerthing Corp. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Fri, Sep 10, 2010 at 4:13 PM, Thomas HOCEDEZ thomas.hoce...@free.fr wrote: But allday until when ? Because when I try an apt-get update... Bing!* : no space left on device ! Does anyone has a turnaround aor a real solution to this ? buy a bigger uSD ;) I've a 4GB partitioned as: 1 - 2GB as /media/card (fat32) 2 - 1.7GB as rootfs (ext3) 3 - 300MB as swap (swap) /* OT I've also added the following line in my /etc/sysctl.conf vm.swappiness=0 */ on v26 I can use my FR as a usb drive, with the 2GB partition (1) visible also in a windows system. bye ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
Le 10/09/2010 16:29, Alfa21-mobile a écrit : On Fri, Sep 10, 2010 at 4:13 PM, Thomas HOCEDEZ thomas.hoce...@free.fr wrote: But allday until when ? Because when I try an apt-get update... Bing!* : no space left on device ! Does anyone has a turnaround aor a real solution to this ? buy a bigger uSD ;) I've a 4GB partitioned as: 1 - 2GB as /media/card (fat32) 2 - 1.7GB as rootfs (ext3) 3 - 300MB as swap (swap) /* OT I've also added the following line in my /etc/sysctl.conf vm.swappiness=0 */ Why ? what is it ? on v26 I can use my FR as a usb drive, with the 2GB partition (1) visible also in a windows system. bye - Nice idea ! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Thomas HOCEDEZ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
/* OT I've also added the following line in my /etc/sysctl.conf vm.swappiness=0 */ Why ? what is it ? please read this: http://lists.openmoko.org/pipermail/community/2010-September/062911.html on v26 I can use my FR as a usb drive, with the 2GB partition (1) visible also in a windows system. bye - Nice idea ! and now a question from me: when the usb mass storage mode is enabled, all the used partitions is in read only mode.. I see qtmoko exports also the rootfs and imho it's not good because if I forget to switch off the usb storage ... it's bad for the whole system. the question is: how I can configure qtmoko to use only a specific partition? eg the one mounted on /media/card only? tnx. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: gprs bug QtMoko v26
2010-09...@13:22 Alfa21-mobile i reverted back mux and deepsleep, rebooted with on/on and my gprs is still ok! :) i do not understand what was wrong before... but now all should be the same again, instead my gprs works a lot well :D sorry, I was wrong I've doublechecked this and if I keep the multiplex the gprs doesn't connect. the only problem with this is I cannot hear incoming calls (yeah, = no multiplex) if I'm on gprs. bye ps: someone here is able to send/receive mms with qtmoko26? (I'm not sure about operator's settings I have) -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Contacts lost in QtMoko v26
В Чтв, 09/09/2010 в 13:33 -0700, Brolin Empey пишет: Rashid wrote: Hi guys, when i updated from v22 to v24 i lost my contacts but they showed up sometimes (when i called someone by number which was added before I flashed the device). New contacts were there. At the first start after flashing all contacts were there. No are all gone. Someone knows a way to fix the problem? Have you continued restarting QtEI to see if your contacts reappear? Have you used another phone or a SIM card reader to verify your contacts are still on your SIM? Yes, i something like this in qtmoko. I have to wait ~30 seconds after entering pin and after that contacts appear in list. Very rarely they do not appear, and i have to restart qtmoko. Also, in some older release (in june i think) i noticed that if i wait too long and pin question visible for may be 15 minutes, contacts always not loaded. To workaround try to delete 1 contact (last) on other phone and see if they reappear. (just guess) Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
usb-mass-storage, data corruption, QtMoko v26
2010-09...@18:13 Alfa21-mobile and now a question from me: when the usb mass storage mode is enabled, all the used partitions is in read only mode.. I see qtmoko exports also the rootfs and imho it's not good because if I forget to switch off the usb storage ... it's bad for the whole system. the question is: how I can configure qtmoko to use only a specific partition? eg the one mounted on /media/card only? about g_file_storage... we have this DOGMA: an usb host will not expect to see any changes in the storage other than the ones it makes. I found a critical (if the rootfs is on uSD) bug concerning the use of g_file_storage with the scripts in qtmokoV26!! - the # mount checking if, in /opt/qtmoko/bin/usb-mass-storage-on.sh is too weak because: 1) by default /etc/fstab in qtmoko contains rootfs for / and any root partition on the uSD is not found by that grep 2) any swap partition is not found by that grep so we could corrupt our storage if it remains mounted inside the freerunner and both exported with usb! a fix could be: - in storage-on script 1) modify the DEV_NAME with the name of the specific partition we want to export 2) umount it and really verify it's not mounted 3) modprobe g_file_storage (and we should add removable=y to the modprobe line) btw I'm not sure if this is acceptable by OSes others than linux, because in this way we expose a storage without a partition table. (I'll check this on a windows computer asap) ...else we could make a partition table inside the exported partition and use kpartx in the freerunner to read the storage (yes, it's like a matryoshka of partitions) bye, a. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Contacts lost in QtMoko v26
Rashid wrote: Hi guys, when i updated from v22 to v24 i lost my contacts but they showed up sometimes (when i called someone by number which was added before I flashed the device). New contacts were there. At the first start after flashing all contacts were there. No are all gone. Someone knows a way to fix the problem? Have you continued restarting QtEI to see if your contacts reappear? Have you used another phone or a SIM card reader to verify your contacts are still on your SIM? -- Sometimes I forget how to do small talk: http://xkcd.com/222/ “If you have to ask why, you’re not a member of the intended audience.” — Bob Zimbinski, http://webpages.mr.net/bobz/ttyquake/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
