Re: WIKI is in read-only mode?
On Sunday, March 17, 2013 03:14:32 PM Dmitry Shalnoff wrote: But one day your GTA02 will stop working - it might fall on the floor or whatever. GTA04 is only replacement - that's why it's important to support GTA04 - either by donation or buying the device. how it connected with the subject? This is not a reason to move the wiki or close it. This is an open source project, the marketing stereotypes (that the new generation hardware is the better replacement for old one) just not applicable. My point was that if there is no living replacement project, openmoko will die. The number of users/devs will convert to 0. Sooner or later your device will stop working and only replacement will be android/windows phone/iPhone. Just because that targeted to stimulate consumer market for sales, but not to give ability to people to create whatever they want. I dont like buying new phone every year. But Freerunner HW is badly flawed in a few ways (e.g. Glamo) and this justified buying GTA04 for me. I'm as a user of wiki just don't care whether it contains some spam or not. I do - there is a lot of useful information and i dont like that some spam machined deletes it. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v54 - Some issues on GTA02
On Monday, March 18, 2013 07:31:54 PM francesco.dev...@mailoo.org wrote: I don't remember if they are known issues for v54, but for now I'm experiencing: - the same problem reported above with the media player; - random sound loss, I notice it after a suspend when I receive a sms, a call or an alarm starts, I have to restart QtMoko. Hmm it looks that new gstreamer engine is not working as it should. It's quite strange, because on GTA04 it works quite ok. We can easily switch back to old cruxus engine or we can try find where is problem. I think it will be best to rebuild with cruxus for now and try to find fix for gstreamer later... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko and WPA
On Thursday, March 21, 2013 01:14:06 AM Stefan Monnier wrote: Am I doing something wrong? Is there some way to get some info about what went wrong? Can I provide my network's password via the command line instead? Any help to connect to a home WPA network? I can connect to WPA/PSK from QtMoko gui after filling up password for the network. But since it's debian you can also do it the debian way via /etc/network/interfaces - it should be well documented, google can help here more then me... Regrards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v55
Hi, qtmoko v55 is now available. You can get it from here [1] or visit our homepage [2]. Changes since v54: * back to cruxus media engine until gstreamer bugs are fixed * whereabouts use gpsd (Stefan Wildemann) * navit bugs in town search and program exit fixed (Stefan Wildemann) Let's hope this release will fix the problems with sounds (it should) and can be our stable release for some time. If you are upgrading, you should manually add -b argument to gpsd, see http://lists.goldelico.com/pipermail/gta04-owner/2013-March/004155.html Btw i couldnt test GPS, because my Freerunner does not get fix, so i just hope it will be ok. Thanks Stefan for his work. It's really nice to have navit working properly. Cheers Radek [1] http://sourceforge.net/projects/qtmoko/files/GTA02/ [2] http://qtmoko.sourceforge.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v55
On Monday, March 25, 2013 08:49:17 AM Radek Polak wrote: Hi, qtmoko v55 is now available. You can get it from here [1] or visit our homepage [2]. Changes since v54: * back to cruxus media engine until gstreamer bugs are fixed * whereabouts use gpsd (Stefan Wildemann) * navit bugs in town search and program exit fixed (Stefan Wildemann) Let's hope this release will fix the problems with sounds (it should) and can be our stable release for some time. Hmms, i should have tested it better. It seems that web browser now does not start. I'll have a look and see what we can do... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v55
On Tuesday, March 26, 2013 08:07:06 AM nitpi...@arcor.de wrote: Hi, I updated and got the following problem: root@neo:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: qtmoko-navit 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. root@neo:~# apt-get install qtmoko-navit Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: qtmoko-navit : Depends: libgps20 (= 3.3) but it is not installable Depends: libssl1.0.0 (= 1.0.0) but it is not installable E: Broken packages root@neo:~# Yes, i noticed too, i need to rebuild navit with squeeze dependencies. Or rebuild QtMoko for wheezy - which is what i am doing now. Please give me a few more days... Regads Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Invitation to indicate interest in next batch of GTA04A5 boards
On Tuesday, March 26, 2013 11:22:39 AM Dr. H. Nikolaus Schaller wrote: If you have ideas how to stimulate demand, please do! Hi Nikolaus, first of all thanks for all your work. It's quite sad that such nice project is attractive for only such small group of people. I dont think there was any obvious mistake done. Most likely it's just wrong time for our project. Openmoko sold 1 phones with much worse HW and with crap software - maybe that's why there is so small demand for GTA04 now... Ideas: I think there might be interest in encrypted GSM calls - those customers would be not worried by big price. It's just matter of implementing SW for it. The board would be nice for some industrial solution. E.g. company where i work uses nearly identical OMAP board for reading smartcards in trains: http://www.odp.cz/index.php?id=53L=1 GTA04 board would be much better for this, but unfortunately the board was chosen before GTA04 was usable. High price is not problem here... Looking forward meeting you and Christoph in Berlin! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SOLVED] Re: Corrupt database OR How to get back applications without reinstallation
On Sunday, March 31, 2013 11:09:33 PM Sebastian Reinhardt wrote: Am 31.03.2013 22:17, schrieb Christ van Willegen: On Fri, Mar 29, 2013 at 8:05 PM, Sebastian Reinhardt s...@lmv-hartmannsdorf.de wrote: Found the solution: installing only one app of group games (i.e. chess) and one application (i.e. qtgps), rescans the list and all shortcuts/ symbols were shown again.Thanks Good! Great to see you have everything back! Christ van Willegen Yes, good news, but I think there should be an better way to start rescanning/ rebuilding the database. Somthing like rpm --rebuild (I know it is debian or better Qt should have a rebuild option) should be integrated in the creation of a new database! Not sure if possible.. You can do this (copied from qgcide.deb postinst action): # rescan .desktop files so that we appear on the list . /opt/qtmoko/qpe.env qcop QPE/DocAPI 'scanPath(QString,int)' /opt/qtmoko/apps/Applications 1 Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIM not ready(solved/closed)
On Friday, March 29, 2013 02:09:49 PM joerg Reisenweber wrote: On Fri 29 March 2013 13:58:17 Sebastian Reinhardt wrote: ... So only one dream is left: - a GTA04 with Qtmoko, incl. usable camera/ photo app - ALU-case with display cover (Nicolaus please discuss it with Radek, ref. my last mail, maybe we should discuss this in public?) You don't want an ALU case, unless you prefer old style pull-out antenna like that one: http://multimedia.pol.dk/archive/00573/Nokia2110_573233a.jpg Even that will not really help for BT and WLAN and NFC and FM-radio and... I can confirm that in our ALU case [1] radio signals were very poor. Maybe it would be possible to split the case into separate parts with dielectric between them and use the parts as antennas. I think iPhone or HTC phones do it this way. But it has not been tested yet. Regards Radek [1] https://picasaweb.google.com/114961040002008630266/GTA04AluCase?noredirect=1# ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SIM not ready(solved/closed)
On Friday, March 29, 2013 01:58:17 PM Sebastian Reinhardt wrote: So only one dream is left: - a GTA04 with Qtmoko, incl. usable camera/ photo app The photo app in QtMoko is more like demo. I think we could port some nice desktop Qt app for photos to qtmoko. - speaking navit, Latest navit for qtmoko should be speaking, but i havent tested this yet. - working bluetooth headset (NOLAN motorcycle helmet with N-COM this one: http://www.n-com.it/site/index.php?option=com_contentview=categorylayout= blogid=55Itemid=228lang=debrandid=1lang=enbrandid=1 I can connect but can not make calls/ listen music/ navit speech output) I tried A2DP with my Jabra BT phones and it worked - at least on some older version. So music/navit speech could work. I havent even tried to make GSM calls working yet... - working bluetooth Virtual Laser Keyboard (I can connect, but no key press is recognized) - for next hardware devel.: integration of DECT = so I can connect to our fixed wireless phone station and maybe, LTE? .and some other things :-) It should not be hard to make BT keyboard working. I have one at home for 1 year now, but didnt get time to play with it yet.. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Wish list WAS:Re: SIM not ready(solved/closed)
On Friday, March 29, 2013 02:34:13 PM Sebastian Reinhardt wrote: About my wish list: everybody is free to complete it. I like to get back the hand writing input, too and many other things. I think we need good touchscreen filters first. I wanted to make video how the GTA04 touchscreen driver works comparing it to Freerunner and N900. You can try yourself paint something with finger (not fingernail) and you'll realize that while it works 100% perfectly on Freerunner/QtMoko v26, nearly perfectly on N900 or Freerunner/2.6.34 kernel it's nearly impossible on GTA04. I have played a little with tslib, but without any good results. Maybe it would be best to port touchscreen filters used on Freerunner 2.6.28 kernel - they work really good. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko image for Freerunner based on debian wheezy
Hi, you can now download wheezy-based QtMoko image from here: https://sourceforge.net/projects/qtmoko/files/Experimental/ I have tested it a bit and havent found any obvious problems except that i cant connect to wifi router at work. But i couldnt even with squeeze based image. So please if you have time, give it a try and report if something does not work as expected. It would be really nice if we could move to wheezy so that GTA04 and GTA02 images are more similar. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Invitation to indicate interest in next batch of GTA04A5 boards
On Tuesday, March 26, 2013 11:22:39 AM Dr. H. Nikolaus Schaller wrote: The key to open the GTA04 door is getting more units into one production batch. But without demand (for the only free and open smart handheld that really is available) it does not work. So we unfortunately have to postpone the production of GTA04A5 boards, until someone manages to create more demand. I and maybe others can do this offer: i can send money for let's say 2 or 3 boards (sorry, i cant afford more now). If you can sell these units, then you can send back the money to me. If not you can send me the boards. I am afraid this solution wont save us, but it could improve a bit the numbers for group tour and we could have some more units in stock after the group tour ends. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko dev : script insertion in path by external application
On Sunday, April 14, 2013 12:40:31 PM Adrien Dorsaz wrote: Hello! I'm still working on getcal application which is a GUI to save calendar server settings and call scripts from ics2qtcal application. The first version is almost finished (see https://github.com/Trim/getcal ), but I'm stuck with a point : this GUI uses QProcess to call scripts from ics2qtcal and I don't know how I can put the scripts in path. Hi Adrien, you can place them in /opt/qtmoko/bin which is included in PATH during qtmoko startup. I think, I've to make a debian package to do this correctly, but up to now I didn't need to make debian package to run it on my phone (I updated my QtMoko directly using my own builds). Is there's some documentation/recommendation to make debian packages for QtMoko ? I've seen in documentation we could make qpk packages, but I suspect that this won't work anymore with recent QtMoko (because we install now .deb packages) and I wanted to add dependencies (e.g., on perl) to be useful, so I can't use them. It should be quite simple. Just modify debian subdir of some existing packaged app, e.g. https://github.com/radekp/qgcide/tree/master/debian For compiling such .deb you'll need native build working (either qemu or on GTA04 itself) or i can make the .deb and upload it to qtmoko apps. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QTmoko Wireless
On Monday, April 15, 2013 05:41:26 PM Rainer Glaschick wrote: Greetings, I currently revived my Openmoko, installed QTmoko V55 and was impressed; coming near to a useful distribution. It was about a time after 4 years :) As concerns the Wireless (WLAN) option: 1. How do I switch off a connection? Select Wireless LAN and use Stop from menu. 2. Is it on purpose that activating the WLAN stops the USB network access? That's one reason to be able to switch of WLAN. I think it's on purpose, but i dont know exact reasons, maybe because of default route? 3. It took me a long time to see that the passphrase could be entered in the line **below** the text; it would be helpful if the input area is not transparent. The wifi UI is quite crazy and complicated. It would be best to rewrite it so that it's more intuitive... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v55 for Freerunner upgraded to wheezy
Hi, i have now moved the experimental wheezy based qtmoko v55 to stable. I have also fixed the ubifs image so that it now boots ok (thanks to gena2x). I am not aware of any regressions and now it should be easier to support GTA02 and GTA04 because of same package versions etc... The wheezy images are now here: https://sourceforge.net/projects/qtmoko/files/GTA02/ the old squeeze images are here: https://sourceforge.net/projects/qtmoko/files/Old/ I will also update the build instructions when i have some more time. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko IMAP sync patch
On Thursday, April 18, 2013 12:26:14 AM Neil Jerram wrote: Hi Radek, Please would you consider the patch below? It's a minor IMAP sync optimization, or more precisely quite a significant optimization but for a scenario that I would guess is pretty rare. I've written more about it in the commit message. Hi Neil, applied and pushed, thanks! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v55 for Freerunner upgraded to wheezy
On Thursday, April 18, 2013 04:59:54 PM Tiago B. Vaz wrote: Thanks Radek! I don't know if it's a hardware issue, but after upgrading to v55 my wireless stopped working. Relevant output from dmesg: [3.72] AR6000 Reg Code = 0x4060 [ 8417.06] AR6000 disconnected [ 8420.02] AR6000 Reg Code = 0x807c [ 8432.35] ar6000_ioctl_siwauth(): Unknown flag 0xc [ 8432.36] AR6000 disconnected [ 8432.43] AR6000 connected event on freq 2437 with bssid 68:7f:74:cf:30:06 listenInterval=100, beaconInterval = 100, beaconIeLen = 26 assocReqLen=57 assocRespLen =59 [ 8631.83] ar6000_ioctl_siwauth(): Unknown flag 0xc [ 8649.86] ar6000_ioctl_siwauth(): Unknown flag 0xc [ 9176.57] ar6000_ioctl_siwauth(): Unknown flag 0xc [ 9196.61] ar6000_ioctl_siwauth(): Unknown flag 0xc Any hint? Hi, i dont think it is kernel related problem. You can try with squeeze compiled kernel: http://qtmoko.sourceforge.net/debian/gta02/armel/linux-image-2.6.34-qtmoko- gta02_55-1_armel.deb if it makes a difference. Btw for me worked connection to my open network - maybe encrypted networks are problematic now... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
On Thursday, April 18, 2013 07:15:35 PM Rainer Glaschick wrote: Tried to use Qx, installed xglamo, and got only trouble: Lauching xterm gives press AUX to leave in the middle, takes some time, then a terminal in the middle. But no keyboard to enter anything. The done button still visible, but does not work. Only way to get rid of it is using AUX twice and stop instead of resume. Anybody out who has a useful application for Qx? xclock works, but overlaps with the top status line. Trying a python script (xgps) just shows the boot console output for a while, then a message tells that Qx terminated due to application error. Starting Qx from the command line then give the reason for fail. Seems to me that Qx is nothing for normal use, only for debug, and thus should be removed from the normal applist and go either to the system debug menu, or should be, even better, started from the command line only to see the error messages that are likely to occur. Hi, you have to try more hard ;-) First explore the Favourites menu item. That way you can add installed X applications and configure them. There are many options that you can configure - e.g. for xterm it's important to enable window manager and virtual keyboard. I recommend also checking use matchbox. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v55 for Freerunner upgraded to wheezy
On Saturday, April 20, 2013 09:02:11 AM robin wrote: hi radek, thanks a lot again for the new gta02 version. what is the best way to do a clean upgrade (transferring sms and contacts?) if I remember correctly one can send the contacts to onself via email and then clicking on the mail would import them. is this still correct? do alternative options exist? Hi, yes this could work - i have all my contacts exported in vcf format using this method. I think that copying whole /home/root should work too. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: How can I run QtMoko on N900?
On Saturday, April 20, 2013 05:39:37 AM Flos Lonicerae wrote: Hello, After search, I found a nice post QtMoko on N900 written by Radek on Jan 02, 2011. I have a N900 in hand too, could someone please tell me how to build the QtMoko for it? Hi, that was just demo. I used Freerunner's tarbal and chrooted there and launched QtMoko with dummy modem in qpe.env I have no plans to support N900 myself, but if want to try you can go ahead. There are many devices in QtMoko under devices folder which can be used as examples. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Another wooden case for GTA02/GTA04
Hi, i have finally finished GTA02/GTA04 case based on Vladimir Zima's alu case model. You can find pictures and video here: https://plus.google.com/photos/114961040002008630266/albums/5869655975669623569 http://youtu.be/E1mOwDeRVkY The result is quite nice even though my milling machine is not very good yet. If it was done on professional machine the result would be IMO very cool. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
On Monday, April 22, 2013 09:11:29 PM Neil Jerram wrote: What X server and config are you using? With Xfbdev, I find that I don't have mouse/touchscreen input at all. With Xorg, I do have mouse/touchscreen input, using evdev, but it's quite inaccurate and jumpy. Hi, last time i tried it yesterday. Got the same issue with Xfbdev and Xorg. I wonder what happened with xserver-xorg-input-tslib for wheezy - it looks the package is missing: http://packages.debian.org/sid/xserver-xorg-input-tslib Maybe after installing it from sid it would work better. I also think that we need some touchscreen filtering - maybe use the filters from 2.6.28 Freerunner's image - they were really good. You can try compare Freerunner touschreen and GTA04 touchscreen and you'll notice how much better Freerunner is now. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Another wooden case for GTA02/GTA04
On Monday, April 22, 2013 06:04:41 PM Adrien Dorsaz wrote: Hi, That's great ! (I like your 3-D printer, so good !) Could you make a picture with wooden case and older plastic case beside to have an idea about the size of the new one ? I have Freerunner case at home, so maybe tomorrow i can make a picture. The sizes are nearly same - wooden/alu bounding rectangle is a bit smaller, because the gsm antenna is different/missing. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QTmoko] Qx problems
On Tuesday, April 23, 2013 09:21:04 PM Neil Jerram wrote: Can you point me more precisely to the relevant code? I'll take a look at it. The code is in openmoko's git or on my github. I really havent looked if it can be applied to GTA04, but here are some references: https://github.com/radekp/linux-2.6/commit/d082ca932a9d03105fe26881ee860e7ff7025a9d https://github.com/radekp/linux-2.6/tree/qtmoko-v26/drivers/input/touchscreen Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Unlock qtmoko v55
On Thursday, April 25, 2013 12:54:36 AM Liz wrote: This is surely a basic question, but I am stuck. If i lock my phone I can't unlock it. Pressing the power key brings up a tool tip press unlock then * to unlock phone I've tried following these instructions pressing the padlock (1) on the left hand border (2) on the bottom left corner or (3) in the tooltip and then the * of the favourites button on the left hand side but the phone doesn't unlock. Could someone assist me with this simple problem? Just drag the key to the lock? Like at 9:05 here: http://www.youtube.com/watch?v=KYZzmSicpyk Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko,GTA02] config files
On Thursday, April 25, 2013 10:47:44 AM francesco.dev...@mailoo.org wrote: Hi After a fresh install of QtMoko I usually change some parameters. I'm going to make a script to automatically do those changes, like to activate the deep sleep, to rise up the volume in gsmhandset.state and so on. But I don't know yet the config files to be changed for the power management and for the touchscreen calibration. For the latter, I'm looking for a way to avoid the calibration at each reinstallation of QtMoko. Can you help me? Hi, i think calibration is in /etc/pointercal and power management settings are either in qpe.conf - somewhere in /opt/qtmoko/etc should be the default values and in /home/root/Settings are changed values. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
On Thursday, May 02, 2013 06:51:35 PM francesco.dev...@mailoo.org wrote: Hi today I did a dist-upgrade on QtMoko v55 on GTA02, after an update of qtmoko-neo (55-1 ?) and the linux image (uname -r gives 2.6.34-qtmoko-v55) I have this error repeated again and again: udevd[667]: unable to receive ctrl connection: Function not implemented QtMoko eventually starts but it takes too much time, I can use ssh but the error is continuosly repeated on the screen. Hmm QtMoko on Freerunner does not need udev - we are using kernel devtmpfs which is enough. Can you try disabling udev? Something like: update-rc.d -f udev-mtab remove update-rc.d -f udev remove and reboot. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko GTA02] udevd errors on screen after update
On Friday, May 03, 2013 01:31:24 PM asteroid wrote: I disable udev and I haven't got udevd running after reboot. So, can we remove udev package completly ? I am not sure if it is removable because of dependencies. And udev is quite nice when you use usbhost, so i think disabling it is better then removing. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko PC] bluetooth segfault patch
On Sunday, May 05, 2013 10:53:16 AM Ivan Matveev wrote: Hi Thank you Radek for great instructions for PC build. There is no bluetooth on my PC so qpe segfaults on start. Here is a patch to fix it. Hi, thanks for the patch. It's applied now. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new version of FBReader with Qt4
On Tuesday, May 07, 2013 07:30:08 PM francesco.dev...@mailoo.org wrote: Hi There is a new version of Fbreader [1] and it now uses Qt4. Should it be easier to integrate in QtMoko now? Has someone tried it already? It is not yet in the Debian repositories but I wanted to give it a shot, so I downloaded the source code and I tried to compile it on my GTA02. Unfortunately it fails at some point with some errors related to the code, I think. I opened an issue on github here [2] but no answer yet. If you can take a look at the code, can you give me some suggestion? Thank you. Joif [1] http://fbreader.org/content/fbreader-beta-linux-desktop [2] https://github.com/geometer/FBReader/issues/236 Hi, i wonder which branch should i use for this beta... Anyways i have now also fixed FBReader sources used in QtMoko so that it compiles and runs on wheezy. I'll now try to figure out the problem when the application disappears after run. Regards Radek [1] https://github.com/radekp/FBReader/tree/qtmoko_hack ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new version of FBReader with Qt4
On Friday, May 10, 2013 01:57:49 PM Radek Polak wrote: Anyways i have now also fixed FBReader sources used in QtMoko so that it compiles and runs on wheezy. I'll now try to figure out the problem when the application disappears after run. I tried this [1] and now FBReader looks ok. At least for me the problem with application disappearing is gone now and FBReader is again usable. The armel package is now updated and will rebuild armhf now. Regards Radek [1] https://github.com/radekp/FBReader/commit/a1d5e9b663f81c43232e44012730c44f94651f8f ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko videoplayer
On Thursday, May 09, 2013 04:50:48 PM robin wrote: hi, I try to watch some video on qtmoko using qmplayer but I only have audio. I tried h264, mpeg2, mpeg4, vp3 but always the same result: audio only the aspect ratio is standard 320x240 and I installed the glamo version of mplayer when being asked for the first time. in case I would need the other mplayer version, how could I revert? I think glamo is the best option - it works for me on fresh v55 wheezy install. Maybe the video is wrongly encoded? Can you try over ssh: . /opt/qtmoko/qpe.env mplayer /path/to/video.mp4 if that prints anything useful? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v55 for Freerunner upgraded to wheezy
On Sunday, May 12, 2013 11:47:26 AM Raphael Wimmer wrote: On Tue, 16 Apr 2013 14:35:47 +0200, Radek Polak pson...@seznam.cz wrote: Hi, i have now moved the experimental wheezy based qtmoko v55 to stable. Just a heads-up for the next pure-wheezy version: Upgrading gpsd from 2.95 (squeeze, and installed in v55) to 3.6 (wheezy) results in gpsd no longer recognizing the GPS chip. Not sure if this is an error on my side but: I have installed v55 from the linked source. While playing around with additional packages, I had to uninstall and reinstall gpsd. At this point, apt chose the wheezy package for gpsd (3.6). After the upgrade, QtPedometer, qtgps don't get any data. NeronGPS even hangs when initializing the GPS chip. Downgrading back to gpsd 2.95 fixes the problem. with gpsd 2.95 - the DEVICE line appears after starting NeronGPS Raphael Hi, is it configured properly? Make sure you have these values in /etc/default/gpsd: START_DAEMON=true DEVICES=/dev/ttySAC1 GPSD_OPTIONS=-b Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANNOUNCE] openmoko.org server move
On Tuesday, May 14, 2013 03:42:21 PM Patryk Benderz wrote: [cut] Yes, a continuation is what we all dream of. Please consider subscribing to the OpenPhoenux mailing list Hi Nikolaus, I just do not get one thing... why you started new ML? Why don't you continue OpenPhoneux here? It was easier for You to write here, instead of forcing lots of people to subscribe to another ML. I think it's very important to have control over your project infrastructure. You can for example visit http://qtmoko.org/ - dont you want to have similar page on gta04.org? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANNOUNCE] openmoko.org server move
On Wednesday, May 15, 2013 05:32:15 PM Patryk Benderz wrote: well, i just hope Radek earned a lot for selling this domain ;) The story is quite sad for me personally. I have spent thousand hours on the project. I was against registering qtmoko.org, but still people did it and i had no control of it. And everybody started using qtmoko.org instead of sourceforge url so it's first in google result list. Now there is some crap on the site and the qtmoko project looks dead because of it. I really had no single cent from qtmoko.org nor from whole qtmoko project... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new version of FBReader with Qt4
On Sunday, May 26, 2013 09:59:53 PM francesco.dev...@mailoo.org wrote: Il 26/05/2013 19:13, Adrien Dorsaz ha scritto: Hello, I've tried latest qtmoko-fbreader and I was unable to run it. I've tried by console (by ssh) and I've found this error : loading /opt/qtmoko/lib/zlibrary/ui/zlui-qt4.so libgps.so.20: cannot open shared object file: No such file or directory So I've installed libgps-dev and I was able to run it (I haven't gpsd installed on my QtMoko v55 on GTA04). Maybe we should add dependency in the package ? but... why the hell should fbreader need a gps lib?? (: Debian has feature that automatically generates library dependencies. We started using libgps some time ago in QtMoko libs and because fbreader depends on qtmoko it somehow transitively bubbled also into fbreader. No idea if this is bug or feature. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] black screen after sms reception
On Monday, May 27, 2013 11:28:16 PM Adrien Dorsaz wrote: Hello! I've again the black screen after reception of an SMS bug using QtMoko v55 (self compiled) on GTA04 (I'm not sure if it depends on hardware). Hi Adrien, for some reason i dont believe cross compilers. Last time i was using cross compiled qtmoko was like 2 years ago, so i cant tell from my own experience if cross compiled qtmoko actually works as whole (i just cross compiled only one app/library). Now, I've some new notes about this bug : * When the SMS arrive, the screen light on and I see the lock screen during 3 seconds (during this time I see the 1 message received dialog appears) and after it normally suspends (with aux green blinking) * if I press power button to resume from suspend, screen stays black (even if I press several times) * some times after the screen power on (I don't know really exact time, but it seems to be long so about 20 seconds) We were already trying to solvethis problem. IIRC it seems to be related with dbus crashing on resume which causes QtMoko to crash too. QtMoko is responsible for setting screen brightness after resume and because of the crash the display stays dark. Can you try SSH to the device when the display is black and check if dbus and QtMoko are running? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: mqtim not working
On Tuesday, May 28, 2013 01:07:18 PM urodelo wrote: Hello. On v55 of openmoko mqtim doen't work for me. It' doesn't start either. The msg is something like the application has been closed due to an error of the app itself Is there a solution? Hi you can try run it from ssh to get more verbose message: ssh root@192.168.0.202 . /opt/qtmoko/qpe.env mqutim It will be probably some library missing. Unfortunately i have not managed to rebuild this app from sources, but i havent tried really hard so there might be solution... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: fingerkeyboard
On Thursday, June 06, 2013 10:35:45 PM Akli Mahroug wrote:
Hello!
Wanting to get back the fingerkeybaord, I unchecked
plugins/inputmethods/fingerkeyboard in
qtmoko/src/module_inputmethods.pri. Recompiling failed with the
following error in configure:
/Project (/extensions/projects.pri{file}) ERROR: Error parsing file
/home/tanit/qtmoko/src/module_inputmethods.pri at line 3//
//qbuild died with signal 6 at
/home/tanit/qtmoko/src/build/bin/configure line 3597/
What else do I have to do to compile the fingerkeyboard along with the
svgkeyboard ?
Hi,
you can easily compile even disabled project. Something like this:
cd qte/qtmoko/src/plugins/inputmethods/fingerkeyboard/
/root/qte/build-gta04/bin/qbuild
This will produce the .so
Btw fingerkeyboard does not currently compile with new gcc (something with
String(NULL) constructor) but it should be easily fixable.
Hmmm i should have already made packages for these old inputmethods. Maybe
i'll kick myself to it after my new GTA04 arrives ;-)
Regards
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Community] Growing the Community
On Thursday, June 13, 2013 10:44:22 PM Dr. H. Nikolaus Schaller wrote: I think you can - since the GTA04 is sort of an upgrade for the GTA01/02 and therefore can extend the life of the device. It was the logical extension of the Bas/Buzz/#1024 fix activities. I.e. a CPU/Glamo/WWAN-Data speed fix. From my point of view it appears that: 1/ board upgrade is not enough to attract new people. 2/ being free/open is also not enough - it's just additional value. The real value is the product itself. IMO to be succesfull we need to offer really working phone + something that others dont have. Some ideas probably already metioned: - modified case for AAA batteries instead of openmoko battery. Would be nice e.g. for travelling when you dont have charger - eink display on backside - cool for reading and great battery life - solar charging - induction charging - HW keys for playing games - like http://www.youtube.com/watch?v=l8VRABmJKSw - case with blackberry or similar HW keyboard like this: http://www.blackberrymall.net/blackberry-bold-9700-keyboard-qwerty-keypad.html - case which converts the phone to tablet or to notebook like this: http://www.engadget.com/2013/05/21/asus-padfone-infinity-review/ It appears now that we dont have demand/money for building new GTA04 but maybe that does not matter for now... Doing new designs and products on top of GTA04 board might be now more interesting and could bring interest to the openphoenux project. And of course fixing existing problems would be really nice. Especially: 1/ poor power management. We are still far behind Neo Freerunner. Try to really use GTA04 as a phone for some time and count how many times you found it discharged. My N900 which is very similar HW can live 5days and it even does not go to suspend. GTA04 if you are lucky can do 2 days. Unfortunately i cant really help much here, because i never worked with HW except sending some bits to kernel from userspace. 2/ i am willing to try to flash newer modem firmware on my broken GTA04 if it helps with modem reenumeration. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Community] Growing the Community
On Friday, June 14, 2013 09:19:37 AM Radek Polak wrote: It appears now that we dont have demand/money for building new GTA04 but maybe that does not matter for now... Doing new designs and products on top of GTA04 board might be now more interesting and could bring interest to the openphoenux project. Maybe we could ask e.g. comunity around blender to design some unusual and nice case for GTA04 board? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bluetooth Keyboard
On Monday, June 24, 2013 08:17:35 PM Ben Wong wrote: On Mon, Jun 10, 2013 at 1:36 AM, Giacomo 'giotti' Mariani giacomomari...@yahoo.it wrote: Thank you Radeck, I'm glad to have the Docked keyboard back: it is priceless when sending SMS via vnc! Nice tip, Giacomo. That reminds me that my biggest bugaboo with QtMoko is that I have never been able to get my bluetooth keyboard to work. It's quite frustrating to have to plug my Neo into a PC just so I can ssh into it with a proper keyboard. I seem to remember Radek saying about a year ago that the issue was not too hard to fix, but I think nobody has stepped forward to do it. I started reading the QT documentation myself, but was daunted. I suspect simple for Radek is still too hard for lesser-mortals. ;-) Well i have been playing with my bluetooth keyboard this weekend. I could connect it with hidd --connect but unfortunately it does not generate any input events (same on PC). So the HW might be broken. I though it could be quite easy, because input handling is handled by Qt and should be quite well documented/tested. The trick should be to correctly set QWS_KEYBOARD environment variable - you can google for it. E.g. this [1] link looks interesting. Also on PC HW keyboard worked for me in qtmoko. Regards Radek [1] http://buildroot-busybox.2317881.n4.nabble.com/Question-exporting-QWS- KEYBOARD-LinuxInput-dev-input-event0-quot-hang-application-td31600.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Bluetooth Keyboard
On Friday, June 28, 2013 11:23:53 AM Ben Wong wrote: On Mon, Jun 24, 2013 at 10:29 PM, Radek Polak pson...@seznam.cz wrote: Well i have been playing with my bluetooth keyboard this weekend. I could connect it with hidd --connect but unfortunately it does not generate any input events (same on PC). So the HW might be broken. Could it be a passkey problem? I dont think so. Devices are connected and i have new input event in /dev/input but there are no data when i press keys. I though it could be quite easy, because input handling is handled by Qt and should be quite well documented/tested. The trick should be to correctly set QWS_KEYBOARD environment variable. Where does one set that variable in QTMoko? /opt/qtmoko/qpe.env Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko on my GTA02 - first impressions and questions
On Monday, July 01, 2013 11:23:36 AM Nick wrote: Hi there, Yesterday I dug out my GTA02 from the shoebox it had been living in for the past year and a half and put QtMoko on it for the first time (it had always had SHR on it before that, but it proved too unreliable as a phone). My first impressions are that it is beautiful and seems to work much much better than SHR. I am very pleased to find that :) One major issue I had is that I put it to sleep by pressing the power button, then about 30 minutes later decided to call it using a different phone (to see what the ringtone was like, and how long it would take to wake up), and was sad to find that it did not wake up at all, even after pressing the power button. I had to pull the battery out and start it again. Is this a known bug? Should I report it? Is there somewhere I might be able to pull logs, or any other thing I can do to help track down the issue? Hi, nice to hear that you like it. I am also wondering what to do with kernel bugs. I dont have kernel skills to fix them and not many other people have them too it seems. Only thing i could do is to use old 2.6.29 openmoko kernel which was really stable IIRC. The other problem I have found so far is that it won't connect to the WPA-PSK-TKIP in my house for some reason. And when it was set to automatically reconnect the whole phone slowed to a crawl until I disabled that, I suppose as it continuously tried and failed to connect. Any suggestions on things to try to get the wifi to connect? And should I report the slowdown if it is set to autoreconnect on the issue tracker? There are issues with wpa_supplicant on GTA02 in debian wheezy. You can check https://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt and search wpa_supplicant for details. Maybe it's your case. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko on my GTA02 - first impressions and questions
On Sunday, July 21, 2013 07:15:27 PM Tiago Bortoletto Vaz wrote: It's the case here. I've tried wpa_supplicant 0.7.3-6 but it seems very unstable with the current qtmoko kernel version. And the default wpa_supplicant version is just broken. In short, we can't connect to wpa networks with qtmoko v55 :( Is there any chance to have the little patch applied to current wpasupplicant version in qtmoko? (http://patchwork.ozlabs.org/patch/167925/) That patch is applied in qtmoko tarball. See Step 6.2 here: https://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt Maybe you have upgraded wpa_supplicant to newer version from stock debian which does not have the patch? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Build application for QtMoko with qemu-armhf
On Friday, July 26, 2013 09:33:18 PM Adrien Dorsaz wrote: So, my question is : Now I'm able to emulate an armhf computer, what should I make to continue compilation ? Should I read the old QtExtended documentation [3] or should I take the qtmoko-chroot-armhf script and apply same methods ? Better is to follow Native compiling on GTA04 from this doc: https://github.com/radekp/qtmoko/blob/master/README Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko-eyepiece
On Tuesday, July 30, 2013 08:47:59 AM Griera wrote: Hi: I'm using GTA04 with Qtmoko v55 armhf from: http://sourceforge.net/projects/qtmoko/files/GTA04/ Please, where I can find the deb package of qtmoko-eyepiece? In: http://qtmoko.sourceforge.net/apps/qtmoko-eyepiece.html there is only the package for armel version. Thanks a lot. Griera. Should be fixed now (but not tested). BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko with 2.6.29 kernel
Hi, i wanted really stable QtMoko for Freerunner. With 2.6.34 kernel i noticed a few failed resumes. So i am now testing latest QtMoko with old openmoko 2.6.29 kernel. Because new udev requires at least 2.6.32 kernels i have udev disabled and using just backported devtmpfs. I have noticed that sometimes after boot QtMoko wont find modem, but restarting QtMoko from POWER button menu solves this. The images (v56) are here [1] now if you want to try. I have tested just jffs2 image... Regards Radek [1] http://sourceforge.net/projects/qtmoko/files/Experimental/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko with 2.6.29 kernel
On Thursday, August 08, 2013 02:11:46 PM francesco.dev...@mailoo.org wrote: Hi Radek I'm testing the v56 on uSD and I would like to report two errors encountered at boot. The first one: libkmod: ERROR ../libkmod/libkmod.c:505 kmod_lookup_alias_from_builtin_file: could not open builtin file '/lib/modules/2.6.29-qtmoko-v56-v26/modules.builtin.bin Hi, hmm i think i saw this too. Maybe running depmod solves it. About the second one, usually I use mmcblk0p2 for /home (I think that having a dedicated partition for /home could make easier to manage personal settings and data) and not for /media/card. This modification in fstab causes the error: /etc/rc.local: 14: /etc/rc.local: cannot create /media/card/etc/rc.local: Directory nonexistent [FAIL] startpar: service(s) returned failure: rc.local ... failed! IIRC till v55 I never saw this error, is there a particular reason to have /media/card/etc/rc.local? This is strange. I have no idea where /media/card/etc/rc.local path comes from. There should be just /etc/rc.local - qtmoko uses it for some iptables stuff. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: community Digest, Vol 353, Issue 3
On Friday, August 23, 2013 06:50:11 PM Lukas Märdian wrote: Again, I'd like to out point to some website designs I did quite some time ago, maybe for others to evaluate and improve upon: GTA04 project page: http://slyon.de/gta04/index.old.php OpenPhoenux preorder/crowd-funding page: http://slyon.de/gta04/preorder.html Hi, imo they are very nice and more attractive then current gta04.org. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crowdfunding an Ubuntu smartphone
On Friday, August 23, 2013 10:21:33 PM arne anka wrote: the missing money is just the indicator for this project's failure to create sufficient public interest or even awareness. while the GTA01/2 was a nice idea, it was already slightly outdated when it appeared -- and since then nothing has changed, the gap between what's considered standard and what the GTAxx is prepared to deliver rather has widened. to get even close to standard (and thus being a realistic alternative for smartphone users), the project would need backing of a far more potent entity than this tiny community is -- both money- and publicitywise. since the GTA02 i spend about 2000€ on this project, maybe more (well, i can afford it and it was worth supporting the idea behind it), and in my very personal and subjective opinion, the GTA04 has been a huge disappointment. i wouldn't spend the equivalent of a highend, state-of-art smartphone or even tablet just to buy yet another even more outdated device, free or not. compared to the shortcomings of the GTA04, even complete freedom is not sufficient to justify that amount of money. whenever i told somebody who had heard of OpenMoko that there's a successor, they were surprised -- and when i told them the features and the price, i got an incredulous grin and the question if someone really believed that people would spend that amount for such a device. i am still undecided if i should admire or pity the thread starter, if he honestly believed that this community would be able to succeed where ubuntu failed -- and on top of that to jump from todays GTA04 to the device as imagined by ubuntu ... all things considered, the realistic path is imo to cater to a tiny niche of institutional customers -- like jörg(?) proposed. while i am personally rather fond of the original GTA01 case (and think that's almost the only tangible unique feature), i, too, would prefer it to pick up where the n900 left. maybe then it could even tap into the pool of still active n900 fans ... Very well written. I can add a few more points. For me GTA04 is not usable as daily phone. It's now collecting dust in shelf. Why? 1/ poor power management 2/ bugged reenumerating modem GTA04 is good enough only in some situations. E.g. ok if i carry it to work where i can anytime charge it. When i am on bike 150km from home i must have reliable phone in case that the bike breaks up or in case that i need map. I took GTA04 with 2 batteries and N900 on my bike trip this summer. I used N900 as a phone with SIM card. GTA04 was switched off - i just used it for GPS. But after 4 hours one battery was empty and second battery was 50% empty during one night in suspend. On the other hand N900 was working whole 4 days. I used it for calls, for wifi in camps and in the end even for GPS. I though that self-made open source phone will have good power management. I though it will be easy or at least possible to identify where the power goes. I am even more dissapointed that noone except Neil Brown tried to improve the situation. Event GTA02 is s much better in this area. For me this is so important that GTA02 is now much more usable then GTA04. It's like having car that can go just 30km. And the reenumerating modem - i really dont understand why we havent tried newer firmware. For me missed calls is quite serious problem. I dont understand why produce more phones until these problems are fixed. I even dont understand the efforts to make PVR, camera, radio and other components working, unless we have working phone and not mobile heat generator. Well you can answer why i am just writing mails instead of doing something. But i always worked in userspace. I barely understand kernel and i have no EE skills and equipment to contribute. I can contribute only as a tester. I thought that i will deliver working userspace and IMO QtMoko is very good at it. But without working kernel and HW there is not much point to improve it. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Crowdfunding an Ubuntu smartphone
On Saturday, August 24, 2013 03:20:10 PM joerg Reisenweber wrote: On Sat 24 August 2013 14:22:55 Radek Polak wrote: 1/ poor power management [...] something. But i always worked in userspace. I barely understand kernel and i have no EE skills and equipment to contribute. I can contribute only as a tester. I thought that i will deliver working userspace and IMO QtMoko is very good at it. But without working kernel and HW there is not much point to improve it. many thanks for this contribution, it's already a better help than much of the discussion about what's wrong with our community and the GTA04 project at large. However one remark about it: it's not that simple to blame kernel for poor power management. What we learned from last maybe 6 years of different OM distros and from maemo and mer and nitdroid etc is: poor power management is way too often caused by userland, like sensorfw and WLAN connection manager and X11/windowmanager and audio (alsa/PA) and whatnot else. Yup, after playing with alsa settings i could save a few mAmps on GTA04 too. Often it's even rogue apps that do silly stuff like updating their system status icon 25 times per second or constantly chatting with internet or even just polling files when you should use inotify instead. Kernel power saving measures are relatively simple to test and fix, and usually it's not kernel to blame for abysmal standby time and/or operation time. To give you a simple example: on N900 maemo you have scanning period in settings-internet, which makes device scan for WLAN APs only every 5, 10, ... even 30 min. This is needed since the WLAN chip cuts thru the battery in less than 3 hours when you constantly scan for APs. Clearly a userland issue where kernel can't do much. Now you can start to blame kernel WLAN driver for not doing proper powersaving but that won't help establish a decently working usable OS on N900. I think in case of QtMoko on GTA04 we can blame kernel/HW a little bit more, since we are using suspend to RAM whereas N900 is always on (which really cool btw). So while GTA04 is in standby there should be idealy just PMU+RAM+modem turned on, everything else should be off. But something is wrong and noone has yet figured what it is. At best there is ~16mA with omap enable_off_mode - but then we hit imprecise external abort bug so currently we have ~22mA at best. If you compare this with GTA02 or N900 it's really bad. GTA02 is 12mA and i'd say N900 is even better. Together with reenumerating modem it makes GTA04 barely usable even for a few hardcore supporters but unusable for normal users. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Gta04-owner] Crowdfunding an Ubuntu smartphone
On Monday, August 26, 2013 01:17:09 PM Radek Polak wrote: To give you a simple example: on N900 maemo you have scanning period in settings-internet, which makes device scan for WLAN APs only every 5, 10, ... even 30 min. This is needed since the WLAN chip cuts thru the battery in less than 3 hours when you constantly scan for APs. Clearly a userland issue where kernel can't do much. Now you can start to blame kernel WLAN driver for not doing proper powersaving but that won't help establish a decently working usable OS on N900. I think in case of QtMoko on GTA04 we can blame kernel/HW a little bit more, since we are using suspend to RAM whereas N900 is always on (which really cool btw). So while GTA04 is in standby there should be idealy just PMU+RAM+modem turned on, everything else should be off. But something is wrong and noone has yet figured what it is. At best there is ~16mA with omap enable_off_mode - but then we hit imprecise external abort bug so currently we have ~22mA at best. If you compare this with GTA02 or N900 it's really bad. GTA02 is 12mA and i'd say N900 is even better. Together with reenumerating modem it makes GTA04 barely usable even for a few hardcore supporters but unusable for normal users. Btw you can try even with bare rootfs. E.g. Neil Brown is running very bare debian with just some custom made phone app, but the power consumption is the same - and it's quite expected because all the userspace is stopped in suspend. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Community] GTA04-N900 vel. Neo900
On Tuesday, September 03, 2013 11:51:50 AM joerg Reisenweber wrote: Hi! just as a short newsflash: we got 258 votes-of-interest and even 30 that are willing to pay =700EUR for a Neo900 aka GTA04-NeoN board plus housing and other needed parts. Follow the hype at http://talk.maemo.org/showthread.php?t=91142 You can count me too, but not for the first prototype. I wont buy until i know there is 100% working modem and power management. Until that i will keep working on GTA04. Anyways good luck and please keep us informed about the progress! BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Compiling QtMoko buildhost for Neo Freerunner
On Wednesday, October 23, 2013 11:07:09 AM Adrien Dorsaz wrote: My QtMoko buildhost is the official one with Debian 6.0.7 and kernel 2.6.32 (IIRC, I've upgraded Debian with apt-get upgrade). Have you any hint to find the error ? I think it is out of memory. You need either big swap (1GB) or much better is to use vexpress kernel [1]. You can download armhf buildhost and check start.sh for arguments - it was a bit tricky to find them out, because vexpress can work only with SD cards. And do you know how I can begin again QtMoko compilation without compiling again Qt (it's long and it worked well) ? Maybe after playing with qtmoko configure arguments it might work, but IIRC there were some problems with no easy solution. Instead i am now using ccache. First compiling is slow, but then it's quite acceptable. Regards Radek [1] http://packages.debian.org/wheezy/linux-headers-3.2.0-4-vexpress [2] http://sourceforge.net/projects/qtmoko/files/BuildHost/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: First small steps toward free GSM firmware
On Wednesday, October 30, 2013 08:33:28 AM Norayr Chilingarian wrote: I believe that I can do all those steps without difficulty. Also, I am motivated to try this firmware because with current moko11 fw, battery is getting drained too fast, it doesn't work for whole day. Do you have fixed hardware and enabled deep sleep? I can get standby of 4 days with my Freerunner. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v58 with 2.6.39 kernel and improved power management
Hi, QtMoko v58 for Freerunner is now out! You can download here [1] and visit our homepage [2] for more info. Here is list of changes since last Freerunner release: * gta02 kernel upgrade to 2.6.39 * hack to stop vibrating after resume * show end call button after 2s to avoid unwanted press * improved colors in qmplayer encoding * better name of encoded movie in qmplayer * using emdebian for some packages * using glamo-mplayer as package * suspend in locked screen is now after 3s * accelerometers are now in module and disabled by default (see below) 99% of the credit for this release goes to Paul Ferster. He managed to find the suspend/resume problem and finally after years we have stable kernel. Many thanks! As a side effect while playing with the new kernel i have discovered power management bug in lis302dl (accelerometer) driver. The module seems to eat ~6mA in suspend. So by default the module is now not loaded and accelerometers are not working. On the other side, the current in suspend is now between 4..6mA which gives ~200 hours in standby! If you want to use accels you do: echo lis302dl /etc/modules echo joydev /etc/modules As for the other changes. I plan to start using Freerunner as my daily phone now so i had to fix one old problem. When i answered phone call i often accidentaly pressed the Accept call button twice. After first press the button changed to End call and the second press ended the call immediately. This is now fix and there is 2s interval where second press is ignored. Another problem noticed was that sometimes the phone would start vibrating after resume. So there is now hack that stops vibrations after each resume. Another nice thing is that i am now using emdebian and i have rebuild a few packages with useless python dependencies. The result is that tarbal size went from 161MB - 88MB and ubifs 146MB - 102MB. So if you are still using Freerunner i hope it can work for you nicely. Cheers Radek Btw - anyone has working GPS on Freerunner? I cant get fix and it seems it's not SW problem. It would be nice to have it working again... [1] http://sourceforge.net/projects/qtmoko/files/GTA02/ [2] http://qtmoko.sourceforge.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Thursday, December 12, 2013 11:02:47 AM Neal H. Walfield wrote: To what degree are you still working on qtmoko for gta04? Will there be a release of v58 for the gta04? I have recently adapted it to Neil Brown's latest 3.7 kernels - so there are some improvements in charging on kernel level and probably some users space fixes. I can do v58 for GTA04 too. It could benefit from the GTA02 changes too - smaller tarball, answer button etc... But most likely i will get to it during xmas. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Thursday, December 12, 2013 10:47:41 AM Ed Kapitein wrote: Hi Radek, Thanks a lot! i am still on the old 2.6.29 kernel ;-) Will try it out soon. Can you tell a bit more about your GPS problem? Is there no output coming from cat /dev/ttySAC1 ? Does it work with the older kernels? I tried qtmoko v26 - very old one which had GPS 100% working and no luck. I can see nmea comming using gpsmon, it just does not get fix. I talked to Paul Ferseter on IRC and he has the same problem. He said he could get fix when using GPS amplifier. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Thursday, December 12, 2013 10:54:41 AM Dr. H. Nikolaus Schaller wrote: Some knowledge from GTA02 service: a) the U.FL-cable of the GPS antenna module can easily be broken (where it is soldered to the GPS antenna module PCB) b) there is no capacitor on the MMC clock line (this results in 63*25 MHz noise) - was fixed in factory on A6 and A7 boards Hi, i tried the antenna on GTA04 board and it worked perfectly. I have the MMC capacitor soldered, maybe it stopped working? Does it work with an external antenna? Unfortunately i dont have one to try... BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Thursday, December 12, 2013 10:09:19 AM Radek Polak wrote: So if you are still using Freerunner i hope it can work for you nicely. Hmm it seems that automatic suspending is not working as expected (but using lock and POWER button works welll). I hope to fix and release update soon. More bug reports are welcome :) BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Thursday, December 12, 2013 02:58:47 PM Guilhem Bonnefille wrote: Something you certainly tried, but I ask the question: did you try to automatically unload/reload module when going to suspend mode? I remember there is such framework around suspend/hibernate framework: simply list modules somewhere and they are automagically unloaded when goind to suspend mode and restored when resuming. Hi, yup tried, but this does not work. Once you load lis302dl the power remains high even after you rmmod it. It should not be hard to find and fix the driver. I am hoping someone will do it ;-) Hmm interesting idea - IIRC we have lis302dl on GTA04 too. It would be worth trying if they eat power on GTA04 too... BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Friday, December 13, 2013 01:03:07 AM Ben Wong wrote: Thanks for the update, Radek and Paul! I'm downloading v58 now and looking forward to having a stable system. By the way, I'm glad to see two big user interface bugaboos for me (vibration when resuming and hanging up when hitting answer twice) have been fixed. I think my only other bothersome bug is the way the Terminal interacts with the onscreen keyboard; almost always when switching applications the keyboard disappears and so does the button for showing the keyboard! I have to close the app and restart it to get a keyboard again. (Alternately, I can use one of the themes, like Finxi, that have a toggle keyboard icon builtin, but I prefer the look of Mokofaen.) Hi, i have noticed it too and i looked several times in code, but i havent found anything obviously wrong. But it should be possible to workaround it - if you edit the theme's context.xml and make the toggle keyborad button always visible - that's the element input-method-plugin and remove the active= attribute. Hope it helps Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 02:59:01 AM Ben Wong wrote: Hey Joif, You're not alone. I get the same message with v58 in NAND; haven't tried on SD yet. I thought it might be DFU transferring the file system incorrectly, but seeing that you have the same problem, I think perhaps the image on sourceforge is corrupted. What's the checksum supposed to be for the QTMoko files? 882cc204627226ffefda4e446fae3862 qtmoko-debian-gta02-v58.tar.gz a76072c1c9dce4eb2b07235f7cc307fe qtmoko-debian-gta02-v58.ubi 50baec96657802b5a053fa0ef6b777a2 uImage.bin-2.6.39-qtmoko-v58 The checksums look ok on SF. This is strange - it works for me. Are you booting with qi-v58.udfu? Is the tarball ok at least? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 01:25:47 PM Ben Wong wrote: I tried qi-v58 first then qi-v56 as a test. Neither worked. Haven't tried the tarball; I don't have an SD card handy and (correct me if I'm wrong) there's no way to unpack the tarball onto the NAND unless you've already booted from SD. I notice that v58's .ubi file is 101MiB. This is probably a red-herring, but is there any known problem with crossing the 100MiB threshold? [Oh wait, ignore that, I just checked and v54's .ubi was 142MiB.] The size should be ok. NAND is IIRC 256MB. Would you be interested to try jffs2? I can do it and upload quite easily. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 04:18:13 PM Francesco De Vita wrote: Is the tarball ok at least? Tested on the uSD and it is ok ...apart that I'm stuck at the PIN entry screen (that one with just the notice Please wait...) no matter how many times I restart. But from ssh all seems to work well. Hi, can you try enable modem logging? Long press AUX, from Favourites screen context menu use Add, select Logging. Then answer twice Yes, from context menu select Modem AT communication. After restart QtMoko should work as expected. This is most likely some bad timing bug, because in NAND it works ok. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Friday, December 13, 2013 04:18:13 PM Francesco De Vita wrote: Is the tarball ok at least? Tested on the uSD and it is ok ...apart that I'm stuck at the PIN entry screen (that one with just the notice Please wait...) no matter how many times I restart. But from ssh all seems to work well. Btw i have now uploaded even jffs2 image. You'll need qi-jffs-v58.udfu - both can be downloaded from here: http://sourceforge.net/projects/qtmoko/files/GTA02/ Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Monday, December 16, 2013 04:11:20 AM Jorge wrote: Me too, jffs works but had to enable modem logging to get trough the pin screen. There must be some timing problem. It can be quite tricky to debug it, because with logging it works and with debugging enabled it works too. But with logging it seems to work well. I am now using GTA02 again as my phone. My plan for v59 is: 1/ fix this problem 2/ autosuspend issue (the phone dims screen but instead of suspend it wakes again). 3/ implement better screen locking. Now if you lock screen and receive phone call the screen unlocks and never locks again. I'd like to have it locked once the call ends. 4/ maybe fix the wifi dialog The last points are optional, we'll se how easy will they be. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02] cannot boot from NAND
On Monday, December 16, 2013 10:12:08 PM Ben Wong wrote: There must be some timing problem. It can be quite tricky to debug it, because with logging it works and with debugging enabled it works too. Timing with the AT communications? Would that be the chat script? No idea, i guess it will be a lot of debug prints and recompiling to find this out. That would be a nice one to fix. If I don't notice that I've received a text message or call, I'll sometimes find later that the phone is very warm and the battery nearly dead even though I haven't been using it. It seems i understand the problem and have a workaround that works on v58. The problem seems to be in QtMoko power management handling. You can set intervals for dim, screen off and suspend. There are intervals between them and it always goes like: dim-screen off-suspend If you dont specify interval between screen off-suspend QtMoko automatically places 100ms there. But this is probably not enough and suspend never happens. The workaround: go to Settings-Power management-select On battery and fill in good intevals - e.g. Dim=off, Display off=30s, Suspend=40s and it will auto suspend ok. The trick is that Display off must be filled and must be more then 10s less then suspend. 4/ maybe fix the wifi dialog It would be nice if it was sane. But even just ditching it and having something simple, even trivial like OpenWRT's ewoc-cli script, would be an improvement. You can use standard debian networking (/etc/network/interfaces) even for wpa2 connections. There are some docs on internet how to do it. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 with 2.6.39 kernel and improved power management
On Wednesday, December 18, 2013 04:28:56 PM Dominic Walden wrote: Thanks Radek, I've been using the Freerunner as my primary (in fact only) mobile phone for about 2 years now, thanks in no small part to QtMoko. One question. Is it just me or is the battery capacity monitor not updated frequently enough, and not at all during suspend? For example, taking the phone out of suspend you have to wait 20-30 seconds before it shows you you've lost a bar of power. Hi, the update interval is now as often as uevents are comming from linux kernel. You can enable logging-power management and check in log how often it is - i think it could be those 20s. Is there a way of increasing the frequency, and making it work in the background while the phone is in suspend? AFAIK the battery charge is updated even when phone is suspended - the chip in battery does this. Maybe we could force QtMoko to read it immediately after leaving suspend. The values should be fresh. I can check if it's easily doable. Thanks again, and keep up the good work. Nice to hear that it works for you. Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko on Freerunner and WPA2
Hi, it seems that i have workaround for connecting to WPA2/PSK/AER wifi. The trick that works for me is to enter the scan dialog, select desired essid, from context menu change priorty and tap on the first item - this makes the network the first item in the list. Then leave the scan dialog. From context menu on Wireless LAN select properties and fill in Wireless Encryption. Finally select Start from context menu of Wireless LAN and at least for me it connects. Hope this helps someone and i also hope to make wifi more usable for next release. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
On Saturday, December 21, 2013 06:23:09 PM robin wrote: hi, i just did apt-get dist-upgrade and the install went fine. but now qtmoko get's stuck in the boot process at no more processes left in this runlevel. I can still ssh into the system, but don't know where to go from there to fix it if it is fixable. so if you have any suggestions on how to narrow down the problem (which logs to look at, ...) please let me know. Hi, you can try this: ssh root@192.168.0.202 /etc/init.d/qtmoko-neo stop . /opt/qtmoko/qpe.env qpe It should print someting useful. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
On Saturday, December 21, 2013 08:07:38 PM robin wrote: many thanks for the advice: this is what I am getting: root@neo:~# /etc/init.d/qtmoko-neo stop root@neo:~# . /opt/qtmoko/qpe.env root@neo:/root# qpe NeoKbdDriverPlugin:create() Before call NeoKbdHandler() 56788 0 writeFile failed /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633- gpio/reg-fixed-voltage.1/gta02-pm-gsm.0/power_on : No such file or directory writeFile failed /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/pcf50633- gpio/reg-fixed-voltage.1/gta02-pm-gsm.0/power_on : No such file or directory does this help in any way? Do you have good kernel? Does uname -r tell something like 2.6.39-qtmoko-v58? The kernel package is here: http://qtmoko.sourceforge.net/debian/gta02/armel/linux-image-2.6.39-qtmoko- gta02_58-1_armel.deb I wonder if we have somewhere wrong version uploaded... BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
On Saturday, December 21, 2013 08:51:04 PM robin wrote: so apparently there is something wrong: # uname -r gives # 2.6.34-qtmoko-v55 so I got your kernel: # wget http://qtmoko.sourceforge.net/debian/gta02/armel/linux-image-2.6.39- qtmoko-gta02_58-1_armel.deb and installed it: # dpkg -i linux-image-2.6.39-qtmoko-gta02_58-1_armel.deb but I still have the same situation: boot stops at INIT: no more processes left in this runlevel (installed on SD card if that makes any difference I checked # uname -r but I still got # 2.6.34-qtmoko-v55 so I went for: # dpkg -i --force-all ./linux-image-2.6.39-qtmoko-gta02_58-1_armel.deb (Reading database ... 28623 files and directories currently installed.) Preparing to replace linux-image-2.6.39-qtmoko-gta02 58-1 (using .../linux- image-2.6.39-qtmoko-gta02_58-1_armel.deb) ... Unpacking replacement linux-image-2.6.39-qtmoko-gta02 ... Setting up linux-image-2.6.39-qtmoko-gta02 (58-1) ... but still no luck and I still have: root@neo:~# uname -r 2.6.34-qtmoko-v55 It depends if you boot from NAND or SD. NAND: you need to flash it manually with dfu-util SD: qi loads /boot/uImage-GTA02.bin BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
On Sunday, December 22, 2013 08:11:47 AM robin wrote: hi radek, I went back to your previous reply and issued the commands that you suggested. now this is the output with the newer kernel loaded: root@neo:~# . /opt/qtmoko/qpe.env root@neo:/root# qpe NeoKbdDriverPlugin:create() Before call NeoKbdHandler() Cannot open input device for Headset Jack readFile failed /sys/class/power_supply/battery/status : No such file or directory 56788 0 QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) QDBusObjectPath: invalid path Method call /-DefaultAdapter() failed: QDBusError(org.bluez.Error.NoSuchAdapter, No such adapter) 0 snd_mixer_attach error -2 qpe: mixer.c:788: snd_mixer_first_elem: Assertion `mixer' failed. Aborted root@neo:/root# does this give you any hints on where this is going wrong? It looks that you dont have any modules loaded. Can you check if you have /lib/modules/2.6.39-qtmoko-v58 directory? If yes you can try depmod command and reboot. If no, you have to unpack it e.g. from the .deb Reagards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v58 - best way to upgrade
On Sunday, December 22, 2013 06:47:05 PM Nick wrote: Many thanks Radek for keeping QtMoko going! My FreeRunner has been my daily phone for about the last year thanks to it, and it generally works really well. Can I upgrade to v58 by just doing a 'apt-get update apt-get dist-upgrade', or should I flash it afresh? Hmm there have been a lot of changes, e.g. in apt sources.list, so reflash is IMO better. It should be ok to backup and restore your /home/root dir. Btw i have doubts that our 2.6.39 kernel is really bug free. My Freerunner failed like 3 times to resume during those 6 days i am using it :( I wonder if it is just my phone or others seen it too? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
2.6.39 failed resume
Hi, i am now running 2.6.39 on my Freerunner for 7days. It works well, except that 3 times it failed to resume, or something like that. The symptom is that after pressing POWER button it does not react. I tried to make a call to my number and it was not ringing the voice told me that my number is not responding. I also tried long POWER button press - but it was not reacting. And last thing i tried to plub USB cable, but no response. Anyone else seen this too? I am using QtMoko v58, the kernel sources are here: https://github.com/radekp/linux-2.6/commits/v2.6.39-gta02-qtmoko-v58 they should be same as SHR, same for kernel config. The kernel is natively compiled on wheezy armel qemu. Any ideas. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko: stuck at no more processes left in this runlevel
On Sunday, December 22, 2013 08:05:25 PM robin wrote: # cat /etc/modules g_ether ppp_generic joydev bq27000_battery This is not correct. From rootfs docs it should be: echo g_ether /etc/modules echo ppp_generic /etc/modules echo bq27x00_battery /etc/modules echo ohci_hcd /etc/modules echo snd-soc-neo1973-wm8753 /etc/modules echo ar6000 /etc/modules echo btusb /etc/modules echo bluetooth /etc/modules echo snd-soc-neo1973-wm8753 /etc/modules echo snd-soc-wm8753 /etc/modules echo snd-soc-dfbmcs320 /etc/modules echo snd-soc-neo1973-wm8753 /etc/modules echo snd_soc_s3c24xx /etc/modules To me this looks like upgrade from some old version, but since we have new kernel and apt sources and so on you have to do all the steps manually according to changes in git. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new svg keyboard
On Saturday, December 28, 2013 11:21:37 PM Francesco De Vita wrote: Hello everybody I took advantage of the holidays and I made a new SVG keyboard, cute, only qwerty, not so finger friendly but nailstylus friendly for sure. Hi, i just tested it and it looks great and it's also very pleasant to use. If you dont mind i'd make it default keyboard for QtMoko. I can keep the old one in git for reference. For now the keyboard is designed for the italian language. If you're not able to DIY and want a help for a different character set, I could help on request. As far as i tried i was only missing ESC key, which is quite nice for vim and mc. Happy holidays and happy new year! To you too! Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QTMoko v55 GTA02 flash issue
On Sunday, January 19, 2014 08:21:20 PM Peter Viskup wrote: After upgrade of QTMoko to latest v55 my GTA02 don't wake-up to fully functional state after some random time (more suspends/resumes and uptime of some days). Looks like the flash didn't become available/writable. Seeing these messages: [64691.81] s3c-sdi s3c2440-sdi: running at 400kHz (requested: 400kHz). [64691.81] mmc0: queuing unknown CIS tuple 0x01 (3 bytes) [64691.82] mmc0: queuing unknown CIS tuple 0x1a (5 bytes) [64691.825000] mmc0: queuing unknown CIS tuple 0x1b (8 bytes) [64691.83] s3c-sdi s3c2440-sdi: powered down. [64691.83] mmc0: error -110 whilst initialising SDIO card [64692.61] mapped channel 10 to 2 Full log available on http://pastebin.com/eA99YjHa Not sure whether anybody else experiencing the same or if it could be caused by some bad cells on internal mmc flash...or other HW components. I have experienced something similar and i can even reproduce it by repeated dialing FR from another phone (i do it from script on N900). Btw can you try if USB networking works in this state? I dont think this is HW problem, because under old 2.6.28 openmoko kernel it does not happen. I could do 2.6.28 based QtMoko image if you or someone else would like to try. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Looking for Info on Neo Freerunner
On Monday, January 20, 2014 03:24:13 AM Paul Wise wrote: On Mon, Jan 20, 2014 at 2:27 AM, auto78240314 wrote: I am wondering if someone can tell me about the Neo Freerunner's features? Please take a look at the wiki page: http://wiki.openmoko.org/wiki/Neo_FreeRunner How long does the battery last between charges? http://wiki.openmoko.org/wiki/Neo_FreeRunner_%28GTA02%29_Battery#Notes_abou t_expected_battery_life With 2.6.39 kernel you can get standby 100 hours Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Building qtmoko for Neo.
On Monday, January 20, 2014 07:51:54 PM Jorge wrote: Hi, I'm trying to build qtmoko from https://github.com/radekp/qtmoko , following the README., on a Ubuntu 13.04 64bits box, and have some weird behavior. Hi, I suppose I have to run sudo scripts/qtmoko-chroot-armel.sh, not armhf, right? yes, armel for Freerunner, armhf is for GTA04 1. The cdebootstrap step in the script fails unless I add --allow-unauthenticated. Not sure what is going on nor whose fault it is. Hmm maybe you have to install debian/emdebian apt keyring to get rid of this. I am on debian, that's maybe why it works for me... 2. At some point during the script running, something breaks in my box. Some applets hang, and chromium starts to fail to load complaining on incorrect permissions on /dev/shm. Doing sudo chmod 1777 /dev/shm seems to fix that, but I don't know what else is happening. Ahh interesting, i am getting this error too, but it never occured to me that this is because of qtmoko chroot. It can be related to binded mounts... 3. Finally, the script finishes, but the qtmoko-chroot:~/qte/build$ ../qtmoko/configure -device neo step (is the neo there right?) fails with: Yes, -device neo is ok. ... Testing for ALSA: FAIL ERROR: You requested -sound-system alsa but it was disabled. make: *** [src/build/mkconf/configure] Error 1 You can try append -verbose to see more details. Otherwise you might need the devel packages like libasound2-dev libssl-dev but i wonder why they are not installed - i have checked the qtmoko-chroot- armel.sh and they are there. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
On Monday, January 20, 2014 05:04:53 PM Jake Drexel wrote: the mmc0 device is actually where the ar6000 (wifi) is conneted. I had the same problem with the 2.6.39 kernel on shr. The issue looks hw and sw related. My wifi-board was not connected very well but with older kernel it still worked, which is strange. Here is the ticket where I tried to document the issue i saw: http://shr-project.org/trac/ticket/2103 Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail after 30 resumes before. So please if you are using 2.6.39 kernel edit /etc/modules, remove or comment out line with ar6000, reboot and report if your resume issues are gone. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
On Tuesday, January 21, 2014 10:53:08 AM robin wrote: hi radek, thank for digging in so deep to find the bug. If I remove the ar6000 does that also mean that I will not be able to use wifi (that would be my guess)? Yes Maybe it would be possible to use before-suspend.sh and after-resume.sh scripts to rmmod ar6000 and modprobe ar6000 + rfkill unblock wifi. This way wifi should work as before. But I hope we can find proper kernel fix for this. and as an off topic question: if I remove btusb and bluetooth (as I am not using bluetooth at all) would this somehow interfere with qtmoko (eg are those modules expected to be present somewhere else?) It can, i saw some errors during boot when bluetooth was not working. Maybe you would have to disable bluetooth service too to make it working. But i am not sure if it's worth the trouble. Bluetooth is by default off anyways so it should not eat your battery or CPU. best regards and as always: many thanks to you and the extended qtmoko development crew for keeping the GTA02 alive!!! Thanks :) I am also happy that things are moving on. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
On Tuesday, January 21, 2014 10:21:09 AM Jake Drexel wrote: On 1/21/14, Jake Drexel jackram...@googlemail.com wrote: Good to hear that. The strange thing is that the issue also is hw dependend. After I took apart my phone, reseated the wifi-board, put it back together, and replaced the two screws which I unsrcewed years ago, I didn't have a single resume (or rather suspend) problem in the last 6 weeks. The imminent problem why the kernel does not suspend again, is that in the kernel there is some handler registered which calls a function off mmc, when going into supend. But the function doesn't return (as it can't communicate with the ar6000?). So it just sits there. This sounds like a good explanation (although i am not kernel dev). Thanks! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko tethering
On Tuesday, January 21, 2014 10:56:25 AM robin wrote: I was just wondering if someone has managed to share a qtmoko-gsm connection via bluetooth to an android device. If so would you please share the steps necessary. I think it should work. You have to dial GSM on Freerunner. Then you should start bluetooth personal area network (PAN). There used to be pand command and IIRC the argument to start bluetooth net was -nap (network access point). Then you will have to connect with android - i think there are apps for this like this one: http://www.appsapk.com/tetherblu-free/ Once connected you will have network interface on Freerunner called pan0 and you can use iptables to enable IP forwarding (you can see qtmoko's share- gprs.sh script for inspiration). But i havent tried myself - i dont have any android devices. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
On Monday, January 27, 2014 02:29:10 PM Giacomo 'giotti' Mariani wrote: Hi Radek, all, Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail after 30 resumes before. So please if you are using 2.6.39 kernel edit /etc/modules, remove or comment out line with ar6000, reboot and report if your resume issues are gone. I've been using 2.6.39 with ar6000 commented in /etc/modules in the last week and I've not encountered the resume so far. Hi, well it's quite stable, but not rock stable, at least not for me :( I had encountered problem that the phone wouldnt wake with POWER button. So i tried call from another phone. The screen turned on, but was unresponsive. I tried connecting USB, but this did not work too. Editing /etc/modules I noticed that snd-soc-neo1973-wm8753 is repeated three times. Is it the right behaviour? No. It needs to be there only once. I messed it in the rootfs howto while trying to figure list of modules needed. It shouldnt hurt, but once is enough. Fixed this in git now. By the way, gnuchess does not seem to work on this last QtMoko release. Is this a my problem or is it a common one? Hmm maybe i can take a look. I've a suggestion for you developers: in the scripts menu (top left icon in the mail menu) it would be great if the script could be return some kind of feedback. For example, each category (such as GPS standby) should present a slide button with the two (or more) possible values (checked against the script behind, if possible). Indeed, it should be something similar to neocontrol... These are just shell scripts. But yes, with GUI helper tool they could work like this. I implemented tool for showing QT message boxes already here: https://github.com/radekp/qtmoko/tree/master/src/tools/qui maybe extending this with sliders could work. Sorry for proposing instead of coding, but my lack of knowledge is too big :-( No problem :) BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: X and navit on qtmoko v58
On Friday, January 31, 2014 07:07:04 AM J.Schröder wrote: Now I am stuck at getting navit up and running; there are various ways out there, and none seems to work for me; I can't even get X up and running using the built-in functionality (starting xterm for the first time and then choosing xglamo). Can you give us a short setup description for X and navit? Hi, hmm i have only used the native navit version: http://qtmoko.sourceforge.net/apps/qtmoko-navit.html I think i have tried Xglamo on v58 and it worked. Maybe you can try from ssh shell if Xglamo launches correctly. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: X and navit on qtmoko v58
On Monday, February 03, 2014 12:09:28 PM J.Schröder wrote: Hi Radek, Am Montag, 3. Februar 2014 schrieb Radek Polak: On Friday, January 31, 2014 07:07:04 AM J.Schröder wrote: Now I am stuck at getting navit up and running; there are various ways out there, and none seems to work for me; I can't even get X up and running using the built-in functionality (starting xterm for the first time and then choosing xglamo). Can you give us a short setup description for X and navit? Hi, hmm i have only used the native navit version: http://qtmoko.sourceforge.net/apps/qtmoko-navit.html I think i have tried Xglamo on v58 and it worked. Maybe you can try from ssh shell if Xglamo launches correctly. thanks for your feedback, Xglamo now worked after removing all X-related packages and selecting it again from the dialog; I now saw that navit wouldn't start after installation because of missing libssl file libcrypto.so.0.9.8 . There is only libssl1.0.0 available from the repo, so I still need help, but am not sure if this would be your topic, Radek :-) I am just guessing, but maybe symlink could solve this (unless there was some API change that's not backward compatible). BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] PyQt compatibility
On Wednesday, February 05, 2014 05:08:51 PM Giacomo 'giotti' Mariani wrote: Hello Radek, everyone, I'm looking at PyQt and, after installing all the necessary packages, I tried to run a simple program, but (as expected) I got: # python first.py Fontconfig error: Cannot load default config file first.py: cannot connect to X server Do you think it is possible to run it integrated in QtMoko? Hi, IIRC Qt-X11 and embedded Qt are not binary compatible - that could be problem. On the other hand they are API compatible. I havent checked how technically PyQt is working, so cant tell more. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko's downfall (was changing IMEI)
On Thursday, February 20, 2014 08:38:35 PM Michael Spacefalcon wrote: I am also convinced that the *real* reason why Openmoko = failure in the general public's perception is precisely because of that NDA and no one having broken it during the years when it mattered the most. That's your point of view. Point of view of a firmware hacker. But there are other points of view. E.g. some people expect the phone ring when friends/wife/customer calls. I had many phones before and 2 phones after (N900 and now Jolla). None of them had any problems with SMS and telephony. Openmoko is different - they never provided SW for reliable phone. Openmoko never provided stable maintainable kernel - instead they wasted their time on doing 4 ugly unusable distros while at the time they had perfectly stable usable and working Qtopia. And even 5 years after there is no good kernel for Freerunner. 2.6.29-rc seems quite stable but the patch against mainline is horrible, besides it's power management is worse then it could be. 2.6.39 has hardly nearly unreproducible problem with resume. Now we have free firmware which is cool, but the usablity of the phone hasnt changed much. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko's downfall (was changing IMEI)
On Friday, February 21, 2014 09:15:27 AM joerg Reisenweber wrote: Openmoko is different - they never provided SW for reliable phone. Openmoko never provided stable maintainable kernel - instead they wasted their time on doing 4 ugly unusable distros while at the time they had perfectly stable usable and working Qtopia. Granted, but then QTopia never been a true linux in my book. IIRC it had no X11, thus according to my definition of my dream companion Running X11 apps with QTopia is technically possible. QtMoko supports this, although it could be much better integrated - but only because it was not a big priority for me. it's as useless as Sailfish is now, and android ever been. Well, IMO you should always start with something simple and working. I'd been happy if Freerunner was running from day 0 simple, reliable, power management friendly distro with Accept call and Read SMS. Community does the rest. And do you suggest any of your other phones provided a maintainable kernel so far? I have some of them too and know a bit about their kernels, I don't think they are any better than what OM provided. Right, 2.6.29-rc is probably good one - i cant recall if it's 100% perfect, but it could be. It was probably mistake to abandon it, since 2.6.3x have the suspend problems. I recently patched it to work with recent debian and made QtMoko branch which works with it, but i never decided to completely revert to it, because: 1/ it eats battery more then 2.6.39 2/ there was so much energy put in making 2.6.39 working 3/ nearly impossible to apply any security patches Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re:
On Friday, February 21, 2014 11:43:08 AM David Matthews wrote: An occasional reboot is necessary, but no sporadic problem with resume. Power consumption is not great and I wonder if that would be improved by ripping out some stuff I don't need - I would forgo QtMaze for the odd micro amp ^_~ -- Power while suspended has improved very much with 2.6.39. For me it is ~6mA which makes nearly 200 hours in standby. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: booting qtmoko-debian-gta02-v58 hangs
On Friday, February 28, 2014 10:03:50 AM Matthias Apitz wrote: Hello, I've installed (for the first time) qtmoko-debian-gta02-v58 into mSD; the mSD contained a SHR distribution which I have moved away with # cd / # mkdir .SHR # mv * .SHT # tar xvpzf qtmoko-debian-gta02-v58.tar.gz on the 1st boot it asked me to callibrate the screen and set the timezone, time and date; after this it did not went further only showing in the center an analog clock. On 2nd boot (after power-off reset) it fsch'ed and rebooted, and the last lines on the screen are now: ... INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [ ok ] Starting system message bus: dbus. [ ok ] Starting bluetooth: bluetoothd rfcomm. [ ok ] Starting OpenBSD Secure Shell server: sshd. INIT: no more processes left in this runlevel and now it hangs again forever, with an analog clock in the center. Any advice? Thanks in advance Hi, can you try from SSH: /etc/init.d/qtmoko-neo stop . /opt/qtmoko/qpe.env qpe Maybe that'll print something useful. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: booting qtmoko-debian-gta02-v58 hangs
On Friday, February 28, 2014 12:57:03 PM Matthias Apitz wrote: Now I'm struggling with getting Wifi to work, I can see my home SSID, entered the correct values (WPA-PSK and phrase), but it is unwilling to connect; MAC filter in my AP is temp. disabled because I do not know the MAC addr of the Wifi card. is Debian using the wpa_supplicant daemon? seems so, because the values I have entered are written in the file with this name; but I do not see the proc itself; where is the log/debug output for this? In Settings-Logging there can be selected Wifi or Networking category. There is bug in QtMoko in case of many networks around it might connect to wrong one. So check if from the log if it connects to your ssid. It can be workarounded if you manually move your network on the top of the list. Then it should start working ok. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: booting qtmoko-debian-gta02-v58 hangs
On Friday, February 28, 2014 05:04:29 PM Matthias Apitz wrote:
El día Friday, February 28, 2014 a las 01:27:57PM +0100, Radek Polak
escribió:
On Friday, February 28, 2014 12:57:03 PM Matthias Apitz wrote:
Now I'm struggling with getting Wifi to work, I can see my home SSID,
entered the correct values (WPA-PSK and phrase), but it is unwilling
to connect; MAC filter in my AP is temp. disabled because I do not know
the MAC addr of the Wifi card.
is Debian using the wpa_supplicant daemon? seems so, because the values
I have entered are written in the file with this name; but I do not see
the proc itself; where is the log/debug output for this?
In Settings-Logging there can be selected Wifi or Networking category.
There is bug in QtMoko in case of many networks around it might connect
to wrong one. So check if from the log if it connects to your ssid. It
can be workarounded if you manually move your network on the top of the
list. Then it should start working ok.
I enabled logging for Networking (Wifi is not there) and from what I see
it tries to associate with my AP 'tarara', but either this does not
work, or DHCP does not work; this remains unclear from the log;
I did it by hand and I can associate with the config:
# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/lib/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
fast_reauth=1
ap_scan=1
network={
ssid=tarara
proto=WPA WPA2 WPA RSN
key_mgmt=WPA-PSK
#pairwise=TKIP
#group=TKIP
psk=XX
}
when I then do
# /sbin/wpa_supplicant -dd -c/etc/wpa_supplicant/wpa_supplicant.conf -ieth0
it associates fine; I can ifconfig' the interface and reach world.
when qtmoko does this, it modifies the config file
/etc/wpa_supplicant/wpa_supplicant.conf to some other values:
ctrl_interface=/var/lib/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
fast_reauth=1
ap_scan=1
network={
ssid=tarara
proto=WPA2 WPA RSN
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk=
}
and wpa_supplicant daemon can't associate.
it seems that the values are picked up from:
/home/root/Applications/Network/config/wlan0.conf
which is modified from the GUI... have to debug further...
Hmm maybe try to change encryption to use AES. For me AES works. But otherwise
i dont have much knowledge in this area..
BR
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko-v58] Spanish keyboard, ...
On Saturday, March 01, 2014 08:25:56 PM Matthias Apitz wrote: Hello, For Om2008.9 and SHR I hacked together my own keyboad files to get a Spanish keyboard with all the tilded letters, like áéíóñ¿¡ ... Is this someohow possible as well for qtmoko v5.8? Yes, QtMoko keyboard is svg image editable in inkscape. You can check [1] and [2] for details and nice keyboard by Joif. Related question, I'm (highly) used to use the Spanish dictionary with an application 'estardict' in SHR, is this running (or any similar application) in qtmoko? Probably yes, check [3] and especially [4] which is stardict compatible bilingual dictionary. Regards Radek [1] http://wiki.openmoko.org/wiki/QtMoko#SVG_Keyboards_.28from_QtMoko_v45_onwards.29 [2] http://lists.openmoko.org/nabble.html#nabble-td7563584 [3] http://qtmoko.sourceforge.net/apps/category-dictionaries.html [4] http://qtmoko.sourceforge.net/apps/qtmoko-dictopia.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko] running a script once usb-connection is detected
On Tuesday, March 04, 2014 08:16:28 PM robin wrote: hi, thanks to radek I am now able to launch the voicerecorder from the aux button (see bellow). now I would like the recordings to be processed as soon as the phone realises that it has an internet connection via usb. can anyone help me if either there is a script which polls for the usb-connection where I could insert another command or what other solutions there might be. what I would like to do in the end is to be able a) to quickly record a messege (DONE) aI) increase recording volume just for the message (??) I think you can use udev to launch scripts on USB insert event. Adjusting volume can be done either by restoring whole alsa state file using alsactl -f /path/to/alsa.state restore or it should be possible to use something like amixer set Master 5%+ - you'd have to figure out correct control names. ps @ radek: what does the Suspend.service actually launch so you get the shutdown/restart menu? Hmm i think this menu is just one dialog in qpe process. It's not application. BR Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtmoko] control the state of the battery
On Thursday, March 06, 2014 05:12:36 PM Matthias Apitz wrote: Hi, I'm missing in the qtmoko's system setting some screen to view and control the state of the battery (voltage, charging state and level, 100 or 500mA, ...). Please help me to pick it up. Thx matthias Hi, NeoControl is the app. On GTA04 it even shows charging graph, but i havent ported this feature to GTA02. It looks like this [1] And cat /sys/class/power_supply/battery/uevent is also nice ;-) Regards Radek [1] https://openrepos.net/content/radekp/battery-monitor ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
