Re: Entry level Ubuntu smartphone
2013/1/4 Dr. H. Nikolaus Schaller h...@goldelico.com: The OpenPhoneux should not be tied and favour one specific OS. It should be and remain open to run everthing! I meant only branding. Like putting a sticker with Ubuntu Logo on back/front of the phone. For me it was obvious, that the phone itself would remain open - sorry if I was not clear enough :) No worry - but then we have to put a lot of stickers on it or people start to think that it is only for that one OS, although it isn't. I think there is something to this idea here, and my thoughts are more related to different ways OpenPhoenux products could be branded or marketed than any technical aspect. I could envision other retailers that would do the marketing effort / extra polishing into a more complete / _slightly_ broader target market out-of-the-box product. So built on GTA04, the most open phone platform out there, running the best free software UX that exists (when such exists and is ported), ready to use right away. Kind of like what Openmoko Inc did in its time. They did pretty good marketing, even a little too good for their own good considering the actual problems as a phone in first years. As a small example, Pulster seemed to have a try at a consumer friendly GTA04 simply by buying 10 full GTA04:s ready to use and then re-selling. I could easily see also myself in the group of people that orders something that needs zero additional work and is on stock, if I didn't already have a GTA04 (for which I had the motherboard switch as a service). With the current small screen the future free UX:s (Ubuntu, Mer's Nemo Firefox OS?) are challenging possibly. Although since we've resistive screen the small size of objects can be partially fixed by promoting it as a small pen usable device - like Galaxy Note but tiny - oh see, marketing! It's really like a smaller, sturdier Samsung Galaxy Note ;) On the other hand, both the UX:s and fitting them onto GTA04/OpenPhoenux will take until end of the year easily, at which point there might be advances in possibilities of having somewhat newer case/screen options. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: server update
2012/5/23 Harald Welte lafo...@gnumonks.org: Also, the fact when a particular event happens, and how it is publicized is always considere important in the corporate world. Now if you like that or not, Openmoko Inc. was (and still is) a commercial entity. And it's up to its management to decide when and to whom to publish something. As a sidenote, I'd say that's something FLOSS communities should actually learn from commercial entities. Transparency is one thing, but preparing something well and getting it publicized in the right way is essential for any sort of success, community or otherwise. Way too often communities work in the way that kind of says well there's me and a couple of other guys/gals who know how the thing really goes, others can always ask on IRC. Meanwhile, there is always the larger public perception that matters to success and eg. attracting new people that can be only affected by proper marketing and other PR. This naturally is very much seen in Openmoko - the public perception is very twisted and confused, and has always been since at least Spring 2009 when Om Inc stopped with the handset business. Even before that community vs. company picture wasn't clear and we all struggled to understand what Openmoko actually is, and what the community itself should take responsibility of or manage. The end result together with various other problems like with the hardware was a uniquely spread out and non-organized community. And so it is still today, with the exception that everyone has needed to find their places elsewhere but some still have stayed and understood the value of this gathering of people. To re-cap for historians again: 1) Openmoko Inc - the company - stopped phone business in May 2009 2) Openmoko - the Linux distribution - stopped likewise circa 2009. Several community distributions supporting Openmoko hardware and other phones still active and developed. SHR, Debian, QtMoko, Android4FreeRunner. 3) Openmoko - the hardware - GTA02 'Neo FreeRunner' still available from selected stores for tinkerers, non-Openmoko Inc GTA04 upgrade now available, before that there was work on-going on gta02-core, various hardware tools and knowledge on free hw creation have improved 4) Openmoko - the project and community - the 'Free The Phone' people are still here and even more there: in distributions, in FreeSmartphone.Org/oFono, freeing up nonfree-by-default-phones (Mer/Replicant/etc), helping GTA04 effort and other new hardware projects. Wiki is still relevant and even updated in many parts, as are mailing lists, while most other services like software development have moved elsewhere like the single software projects or distributions One of the most important things that happened when Om Inc still was in the phone business was the birth of the (idea of) Om2009 distribution and the freesmartphone.org middleware. At that point the idea that Openmoko software would be needed kind of shifted away, the software side of the problem called 'phone' externalized to its own software project. Later on also oFono materialized as an alternative for the subset of the same problem space. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian + phoneui-apps
2012/4/2 Brendon Schumacker brendon.s...@gmail.com: Unfortunately it seems I have killed my openmoko from playing with it too much. Perhaps you have some advice for this? I can not start the phone with the regular power button anymore, it might show a red light for a moment on the aux button, but then it dies. If I do aux + power I can get into NOR boot menu sometimes, but it will die again when I try to boot. Can you guess what the problem might be? It sounds like it'd be functioning normally, the red light being the Qi's only UI. If you press AUX when the red light shows, or alternatively just remove the SD card temporarily, it should boot from the NAND flash instead of MicroSD card. So most probably you've a problem with the Debian installation on the MicroSD card, but Qi tries to boot from there by default. AUX + power always brings the NOR boot menu, but you need to press and hold them for some time. Same goes for interacting with Qi, you need to press the AUX in a right way :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian + phoneui-apps
2012/3/26 Timo Jyrinki timo.jyri...@gmail.com: However, after that I get an Enlightenment complaint about not being able to create a new window for each of the same apps that complained about the D-Bus interface earlier. phoneui-apps apparently is missing some dependency, filed bug #665951. After installing the e17 meta package, the apps start. Furthermore, phone calls work! I removed the phoneui-wrapper.sh from .xsession again, and switched from matchbox-window-manager to enlightenment_start. Starting phoneui-dialer from command line works and phone calls can be made and received. Sound works from FreeRunner to the other phone, but I don't seem to get audio from FreeRunner with the default settings (nor the speaker switch works). Enlightenment seems to also have kept to its tiny font size (on Debian, hard-coded away in SHR distribution and elsewhr), which should be probably fixed in either Debian's E17 packages or in configuration otherwise. The phoneui apps (or any apps) also aren't visible in the home screen. Anyway, it's nice to see the new generation FSO2 in action on Debian. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian + phoneui-apps
2012/3/26 Brendon Schumacker brendon.s...@gmail.com: I have phoneui-apps install, and I have both XFCE4 and e17 installed and working fine, but they can't open Dialer, Contacts, etc. When I try phoneui-dialer at the cli I get: Error: No such interface `org.shr.phoneui.Dialer' on object at path /org/shr/phoneui/Dialer Which makes sense because debian is not SHR, I suppose, but phoneui-apps is in the debian repositories so I'm assuming there must be a way to config it? SHR is both a distribution and name for a couple of applications. The SHR applications have been packaged to Debian, and also updated a couple of times. I've the same problem as you, since I wanted to experiment with the FSO2 + SHR on top of Debian, now that they've been packaged for some time and updated a couple of times. I haven't yet gotten any answers either unfortunately, but I've understood the phoneui-apps are working at least for the Debian maintainers who packaged them, and probably some else as well. It's probably about us not understanding about how the apps are supposed to work, and the fact that they haven't yet been configured in Debian to work out-of-the-box apparently. I did find a fix to the specific problem you're mentioning, though. You need to have phoneuid running, and in its current Debian form it's not configured to be automatically run as as service. Therefore I added /usr/share/phoneuid/phoneui-wrapper.sh to the /root/.xsession. However, after that I get an Enlightenment complaint about not being able to create a new window for each of the same apps that complained about the D-Bus interface earlier. I'd be happy to hear usage information from this point forward :) It'd be nice to upgrade from FSO1 + Zhone combo eventually. I will be incredibly happy if I can be running debian on my openmoko! Please let me know if you have any ideas. Let's hope you (also) can get up and running with the phoneui-apps included soon! -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: openmoko.org servers
2012/3/25 Bob Ham r...@bash.sh: admins are still Roh and Gismo afaik ownership (aka payment) went to Harald Welte (see Name Server above) I'm a little confused. Perhaps I'm being obtuse here but why haven't any of these people responded to my original email? I'd guess Roh and Gismo are mostly acting as people that are able to do something in case of emergency, but are working on other things. Harald has his hands in so many important things that I'd guess he cannot follow everything everywhere while doing all the work he's doing, but he has initially been the one that acted to keep things working and donated the money. I'd appreciate, though, a complete periodical mirroring of data (and a report and so has been done): - mailing lists can probably be just crawled? - wiki should be possible to save even without admin help with a couple of scripts utilizing pages http://wiki.openmoko.org/wiki/Special:Allpages and http://wiki.openmoko.org/wiki/Special:Export - git:s could obviously be pushed all to gitorious as mirrors Those there would be a good start. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian with illume
2012/3/25 arne anka openm...@ginguppin.de: zhone is dead. use phoneui-apps. ...updated the openmoko wiki to reflect this. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] Preinstalled minimal image available for Neo FreeRunner
2012/3/23 Thomas Günther thomas.guent...@gmx.de: With your rootfs my Neo does boot. I can login via ssh but I only have a white bar at top on display. If I stop nodm I get a debian login prompt at top on display. Any idea what happens? That's the minimal part of it. It is generous enough to offer you a tray icon area, yet prudent enough not to overwhelm your screen with so called graphical user interfaces. :D So you need to for example apt-get install what I proposed, although that was just applications. Then something either stylus of finger usable for application switching/launching. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] Preinstalled minimal image available for Neo FreeRunner
2011/9/12 Timo Jyrinki timo.jyri...@gmail.com: Just to let you know, that since I tested that install.sh [1] is working now, I'm making available a snapshot of a minimal Debian installation since I had a clean install anyway [2] - see file Debian_NeoFreeRunner_minimalrootfs_20110912.tar.xz. About the same story repeated, but for 2012. I was asked about the pre-installation image which prompted me to update it. And while updating it I noticed that install.sh had a couple of problems, which I fixed: - Removed obsolete fso-gpsd - Install fso-gtaXX instead of fso-config-gtaXX - Removed obsolete zhone - Offer phoneui-apps in COM - Switch from experimental (unneeded) to unstable for the main Debian repository I only tried minimal installation still, though. I also updated instructions for install.sh usage at http://wiki.debian.org/DebianOnFreeRunner - note mainly that you probably want to remove openmoko-panel-plugin since its functionality starts to be limited and it eats most of the CPU for no good reason. The pre-installed minimal rootfs is now at: http://people.debian.org/~timo/NeoFreeRunner/ (Debian_NeoFreeRunner_minimalrootfs_20120321.tar.xz) It expects a single partition on the MicroSD card where the tar.xz is unpacked and a Qi bootloader. SSH:ing in works after booting (root password 'changeme'), and after apt-get install foxtrotgps gpsd navit omhacks monav midori wicd lxterminal phoneui-apps you may actually get something useful done. If you want some home UI to use when not attached to computer, you may try my hacky and ugly https://github.com/tjyrinki/tihos As for my own setup, it's still the old http://wiki.openmoko.org/wiki/User:TimoJyrinki with FSO1 actually, but I now did this update to enable others more easily to do something useful. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Gta04-owner] Status GTA04 GroupTour
2011/12/29 Neal H. Walfield n...@walfield.org: First, if someone orders a GTA04, that person doesn't get all the hardware--that person needs to have a GTA01 or GTA02 and do some non-trivial assembly. I realize that you have some cases that you are selling, which is the route that I went, but I think these are limited and independent of the group tour. If this option hadn't been available, I would not have signed up for a GTA04. In my opinion the GTA02 requirement is the unfortunate limiting factor (in additition to lack of publicity, but it perhaps wouldn't help to enough extent with the GTA02 requirement). That, and the fact that many GTA02 buyers are not _that_ interested in GTA04 as they could and should be. This is just speculation, but I believe that since FreeRunner was well advertised, too well from some perspectives, it was bought by many people expecting a working phone out-of-the-box, freedom issues important but secondary. They got disappointed over a long period of problems, and possibly lost their hope for similar free phone efforts since Om Inc also stopped phone business and years passed. Another big part of the FreeRunner owners are people interested in general in cool hackable devices, and in 2008 FreeRunner was IMHO easily the coolest hackable and own OS installable mobile computer device in existence. The freedomness was a plus but not necessarily the driving factor for the big mass of FreeRunner buyers. Now there is a multitude of cool hackable devices - Pandaboard, Raspberry Pi and many others, in addition to mainstream phone devices like at least Nokia N9 which also can be run with alternative OS like Mer/Nemo(/SHR/Debian), while the default OS is very hackable Debianish GNU/Linux as well. They are free enough for many of the original FreeRunner buyers, I'd believe. Both of these groups, I think, have the majority of currently available GTA02:s ie. the target group for GTA04 buyers, but the devices are possibly sleeping in the drawers while a lot of other cool hacker devices are out there. GTA04 is just one another option, and it has the minus side of not being the coolest gadget of 2012, unless you are interested in precisely 100% free software phone, while the GTA02 interest group who also ended up buying GTA02 was larger. The GTA02 case was also kind of cool or at least ok in 2008, but nowadays to make similar wow effect you'd need GTA04 to be not just an expensive motherboard upgrade to an used and old pretty bulky external case from 2008. And as mentioned, still a few people also have FreeRunner as a functional, primary phone, and they can't risk it. I have two FreeRunners and also N9 so I could risk mine and ordered a piece of GTA04 group order of course. Also notable is that I didn't even consider doing the motherboard upgrade myself, but ordered the service from Golden Delicious. The various marketing ideas seem great, since GTA04 is a _really_ cool device for many user/hacker groups. I just fear the GTA02 requirement problem doesn't go away since it's very hard to reach current GTA02 owners so that they could eg. pass their GTA02 on if they're not interested themselves of buying GTA04. -Timo (btw: I can let go of my other FreeRunner, GTA02a5, for just postage costs + eg. 10/15€ extra if it helps to get another GTA04 buyer. It has a slight screen related problem which shouldn't cause too much grief though: it requires a small plastic piece to be in place between screen and case that adds a bit of pressure so that touch works fluently - but it has been working nicely for over a year after I discovered the workaround. you can also of course just order a new screen together with GTA04) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Nokia N9 and Meego
2011/10/24 Xavier Cremaschi omega.xav...@gmail.com: is there anyone here following the Nokia N9, the new Nokia's phone with Meego ? What exactly is free-as-in-speech in this one ? Well I touched the issue a bit in Debian's wiki: http://wiki.debian.org/Mobile/Nokia_N9 The whole MeeGo Touch Framework, used also in Nemo/Mer user interface, is the same as used on Nokia N9. Therefore, a lot / most of the N9's stack until applications themselves is free (and developed in pretty open projects unlike eg. Android) with the few exceptions like the swipe gesture itself and a custom compositor based on the free mcompositor (well, maybe the swipe is in there). This is my current understanding. Some information may also be tinkered at http://harmattan-dev.nokia.com/pool/harmattan-beta2/free/. Notably in other sections the so called non-free is relatively small, although there are a few ogg things in there as well... and most of the really non-free stuff is in the authentication token needing nokia-binaries directory. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Sharing literki work
2011/10/17 Neil Jerram n...@ossau.homelinux.net: Yes. My idea about that is that I'd like the Input Method (IM) system to tell a small server program (which is pretending to be an IM engine) when keyboard input is needed, and then that program could run literki and make sure that it is on top. Do you think that might work? Well, yes if it implies mostly that existing literki is found and made to be on top. Although, I feel that at least for FreeRunner purposes ibus might be preetty heavy. Not sure though, and it is nice if someone does things actually in a right way. For myself personally, I'd just probably continue my poor hack approach of https://github.com/tjyrinki/tihos and make literki to be on top every time an application switch is done :) When I looked at it the last time, and it was probably almost a year ago, I just didn't find the literki from X resources, ie. it's not shown in the same list I happened to find the other running X apps from. I don't know anything about X so my approach is blind guessing around functions found in X documentation or the (few) examples found on the web ;) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Sharing literki work
2011/10/16 Neil Jerram n...@ossau.homelinux.net: Hi there. I'm doing some incremental work with literki, and wanted to share that in case it's of interest to more than just me. Yes! I still found literki the most interesting keyboard around, which is why I packaged it in Debian (some patches at [1], probably not interesting if not the 03). If only I could find out how to force it to stay on top on my setup so that I wouldn't need to restart it every time I switch a window and want to write something... (I have a button for that in my tihos program). -Timo [1] http://anonscm.debian.org/gitweb/?p=pkg-fso/literki.git;a=tree;f=debian/patches;h=76282552a74781095cb65e8330a4383eea5df808;hb=debian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] Preinstalled minimal image available for Neo FreeRunner
2011/9/20 Aditya Gandhi aditya...@gmail.com: Hi I have installed your image and have given the commands via ssh apt-get install foxtrotgps gpsd navit omhacks monav midori wicd lxterminal but no gui is up, how do I get it working? I do not have a sim, do I need it? Like I said, It is very much not functional as a phone out-of-the-box, because of the ongoing FSO1-FSO2 transition. X however starts automatically and SSH answers, and you may work your way from there,. So, you have X but for more you need to connect via SSH and install something workable. The Debian unstable repository is ongoing changes, and there is no simple functional GUI at the moment. You can install Zhone from experimental as instructed at http://wiki.debian.org/DebianOnFreeRunner#Current_Status_of_Installation_via_install.sh , but people reported problems with it although it starts. Alternatives include installing a Debian stable and using Zhone there, although if you don't have SIM Zhone is mostly about phone functionality only anyway. So, it is a work in progress and currently requires a lot of manual work. My solution at the moment has been using circa Debian 6.0, Zhone and my own dirty hack control app (https://github.com/tjyrinki/tihos), but unfortunately I haven't done a clean install of my way that I could share with others. Some others use for example IceWM for window manager and launching applications like GPS. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: openmoko neo --- Debian install from scratch now works
2011/9/20 Aditya Gandhi aditya...@gmail.com: I did this but I only have the thin bar on top of freerunner, how do I start zphone after this? If you installed Zhone from experimental, you still need to add it to .xsession file (eg. zhone ) so that it automatically starts together with X similar to the openmoko-panel-plugin. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Debian] Preinstalled minimal image available for Neo FreeRunner
Hi, Just to let you know, that since I tested that install.sh [1] is working now, I'm making available a snapshot of a minimal Debian installation since I had a clean install anyway [2] - see file Debian_NeoFreeRunner_minimalrootfs_20110912.tar.xz. The only additional thing that was done was apt-get install xorg omhacks before I added those as being done by install.sh automatically. [1] http://wiki.debian.org/DebianOnFreeRunner [2] http://people.debian.org/~timo/NeoFreeRunner/ It expects a single partition on the MicroSD card where the tar.xz is unpacked and a Qi bootlader. It is very much not functional as a phone out-of-the-box, because of the ongoing FSO1-FSO2 transition. X however starts automatically and SSH answers, and you may work your way from there, see [1] or even [3] (although it doesn't contain information on how to enable FSO2 at this moment when not everything new is yet in). When FSO2 is eventually in, together with some UI that can use it, let's improve install.sh again and maybe make a snapshot of a phone-working Debian unstable. I'm lazy enough not to try to replicate from clean state what I've running on my daily FreeRunner at the moment - it'd mean using install.sh but with stable repositories instead of unstable to have FSO1 and phone functionality, and then tweaking until all my little details work. It's anyhow going to be a thing of the past with FSO2 and new UI versions. [3] http://wiki.openmoko.org/wiki/User:TimoJyrinki -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2011-09-01 issue is out
Updates FoxtrotGPS 1.0.1 FoxtrotGPS is a tangoGPS fork adding multiple improvements - Hungarian, Spanish and French translations completed - Bug fixes to tile downloading - gpsd 2.96 support - more bug fixes Homepage: http://www.foxtrotgps.org/ Package: foxtrotgps-1.0.1.tar.gz Tested on: Debian *** General News *** Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc.. - Tiago Vaz blogged about his VoIP setup in Neo FreeRunner: http://tiagovaz.org/posts/VoIP_in_Neo_Freerunner_with_Qtmoko_and_Linphone/ - Timo Jyrinki blogged about free software smartphone distributions overall, MeeGo and FSO middlewares: http://losca.blogspot.com/2011/08/meego-ce-and-freesmartphoneorg.html *** Event News *** 2011-11-11-13 FSCONS - one track is Development for Embedded Systems. Last year there was a presentation about Neo FreeRunner's history. 2011-12-02-04 Open Hard- and Software Workshop(german) | Time and place of the third OHSW have been fixed. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] [Community Updates] 2011-09-01 issue is out
2011/9/1 Simon Busch morp...@gravedo.de: Thats not correct. Aurora is not only a new UI based on the FSO2 middleware. It is a distribution too and is not based on SHR! Aurora will be the default development base for FSO in the near future as we need to target the needs of a user and for that we need to develop our simple but powerfull user interface. Ok, sorry and thanks for correcting. I seem to be approaching the standard quality of modern day journalist. I saw the OpenEmbedded mentioned and then some incorrect link in my brain from somewhere said SHR (also OpenEmbedded based) when I was writing the bit. Could you by the way add some screenshots to the Aurora page? It'd make a much nicer impression. As soon as Debian has the rest of the FSO2 in, I will start looking at using Aurora since Zhone is not FSO2 compliant and the patches of it being have gone bad. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: openmoko neo --- Debian install from scratch now works (was: fails)
2011/7/20 e.waelde ew.ng7...@nassur.net: as of yesterday evening, installing a neo from scratch fails. I compiled again the 2.6.34 kernel yesterday evening, and uploaded it and got it finally properly into pkg-fso repository where as the working kernel used to linger in the incoming directory because of a few reprepro problems. I also updated install.sh to use that by default and tested that an install.sh run now works properly and the device boots! Try these to get started with Debian minimal installation at the moment: 1. Boot to other distribution that is on NAND, like QtMoko or SHR 2. wget -O install.sh http://pkg-fso.alioth.debian.org/freerunner/install.sh 3. QI=true SINGLE_PART=true ./install.sh all 4. Reboot 5. Login via USB/ssh (default root password changeme) 6. Get a bit more software manually: apt-get install foxtrotgps gpsd navit midori wicd lxterminal xorg zhone/experimental python-ecore/experimental python-edje/experimental python-evas/experimental zhone-illume-glue/experimental Debian still has those E17 Python bindings only in experimental, which is why a working Zhone is also now only in experimental. Note that there is a problem with the old FSO1 stack reported by Dmitry Chistikov in July. A new FSO2 stack is being uploaded to Debian now finally soon by the great work of Rico Rommel. After that we need people to work on updating eg. the Zhone2, SHR UI sofware and other FSO2 compliant stuff into Debian, together with needed E17 stuff. (more information at http://wiki.debian.org/DebianOnFreeRunner , or IRC/Freenode #openmoko-debian) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: openmoko neo --- Debian install from scratch now works
2011/8/17 Timo Juhani Lindfors timo.lindf...@iki.fi: Timo Jyrinki timo.jyri...@gmail.com writes: 6. Get a bit more software manually: apt-get install foxtrotgps gpsd navit midori wicd lxterminal xorg zhone/experimental python-ecore/experimental python-edje/experimental python-evas/experimental zhone-illume-glue/experimental Mandatory advertisement: Add monav to the list :-) And most of all, I forgot: omhacks. The essential tool. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] cannot bootstrap libc6
2011/7/1 Dmitry Chistikov dd1em...@gmail.com: I'm trying to install Debian on Openmoko Freerunner and have encountered the following problem. Both cdebootstrap and debootstrap fail to install a basic Debian system (stage debian of install.sh). Packages are downloaded and extracted, but dpkg is refusing to install libc6: ... Does this mean that Debian sid (unstable) armel is broken at the moment? How can this problem be dealt with? Changing --force-depends to --force-all does not help. I'm not an expert on the installer, but unfortunately it may mean so. You can try to use stable repositories instead by modifying the install.sh script - you just need to make sure that you then don't specify any phone software like Zhone at the install time, since those are only available with the E17 that is in unstable and not in the latest Debian release. I've been meaning to try out if that'd work for some time, but haven't got a suitable extra microsd card and time slot to check it out. Then if you get a minimal installation ongoing, it's much easier to install more software and experiment in a bootable system. The unstable anyway is in a shaky situation at the moment, as still the Python E17 dependencies are not in so they are also not installable. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [pkg-fso-maint] udev 171-1 and linux 2.6.29 and 2.6.34
2011/6/16 Timo Juhani Lindfors timo.lindf...@iki.fi: udev 171-1 does not support linux 2.6.29 or 2.6.34 on ARM. This is due to use of accept4 syscall among other reasons. Afaik it was implemented in 2.6.32 but not wired (=enabled) for ARM until 2.6.36(?). As Frederic Wagner pointed on IRC it might be just enough to add http://uboot.jcrosoft.org/git?p=linux-2.6.git;a=patch;h=21d93e2e29722d7832f61cc56d73fb953ee6578e to our 2.6.34 package. I created linux-image-2.6.34-openmoko-gta02_20101212.git049b71de-2 overnight and it seems to be now free of the udev CPU consuming problem I saw before upgrading to it. It's also now compiled with sid's gcc 4.6, possibly improving ARM optimizations. It's now uploaded to pkg-fso, but is currently stuck in incoming because alioth doesn't have the reprepro command previously used to update the repository. Ideas? Anyway, one can manually download and install it from http://pkg-fso.alioth.debian.org/incoming/ Also as a general reminder to the community at large, the 2.6.34 kernel, especially this new one, is a better choice for most Debian users than the 2.6.37 which has slight booting problems at the moment :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ZX spectrum emulator doesn't appears
2011/6/2 Dmitry Shalnoff shaln...@gmail.com: Hi everybody, I'm trying to install ZX spectrum emulator form official repository but it's doesn't appears in the list of games and home/you/.qspectemu directory wasn't created. Is Spectemu btw developed somewhere still? At least the places I could find were dead ends (sourceforge has last stuff from 2004 and the link on radek's Qspectemu page is 404). It seems that Fuse-emulator (http://fuse-emulator.sourceforge.net/) is the one Spectrum emulator that will outlive the others, and I'm happy that there is at least one fully developed open source emulator for the dear childhood memories :) In the 90s and beginning of 00s there were some pretty good emulators for eg. Windows, but of course they're all dead end without the sources. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ZX spectrum emulator doesn't appears
2011/6/6 Radek Polak pson...@seznam.cz: http://activationrecord.net/radekp/qspectemu/ Erm sorry i was reading wrong. the original page really does not work now (except i get 403 ;-) Right, just that :) Ok anyway, thanks for information. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: About QtMoko future
2011/5/16 Alfa21-mobile freerun...@my.is.it: Then we need debian packages for FSO stack (anyone know if they exists and what is the current status?) and we can start using it. you can look here: http://packages.debian.org/search?keywords=fsosearchon=namessuite=allsection=all + a few newer versions of the packages and fso-deviced at http://pkg-fso.nomeata.de/sid/allpackages (those should be moved to Debian proper where applicable) - and a graph explaining the relations between packages and FSO1 vs. FSO2 at http://wiki.debian.org/Teams/DebianFSO?action=AttachFiledo=viewtarget=pkgdeps.png In practice most of the basic packaging work is there, but packages have been now untouched for a year. All packagings should be at http://git.debian.org/ (repositories pkg-fso/*). More information at the pkg-fso group's page http://wiki.debian.org/Teams/DebianFSO -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: About QtMoko future
2011/5/9 Radek Polak pson...@seznam.cz: qtopia = qt extended = qt extended improved = QtMoko ... From technical point of view QtMoko is using regular Qt as framework for GUI, networking and other nice features that Qt supports. Qt is just compiled with custom configure switches. We can upgrade Qt from upstream and receive new Qt features quite easily. Great to hear that! I obviously thought Qt Exte... QtMoko is more stuck in the Qt 4.4 time than it it is in reality. Sounds pretty great, maybe actually at some point QtMoko or some part of it could be pushed back to upstream as part of the ongoing improvements in the Open Governance model :) Especially if there is something that would help maintaining QtMoko in the longer term. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: About QtMoko future (and Qt Extended - Qt in general)
2011/5/7 Joif fdvj...@vodafone.it: But to date, I have not a clear vision about the current situation and the future of QtMoko, so I want to ask some questions to developers. I'm a Debian developer, but not QtMoko developer. I feel though that I can answer some of the questions from my perspective. 1) QtMoko is based on Qt Extended, is this Qt base still in development or is it an ended project? I mean, the main work on QtMoko is about bringing new and improved code or about solving bugs? 2) Is there a new environment, in step with the times, that could be convenient to use as a base for a new QtMoko? Qt Extended was a project formerly known as Qtopia, and created by Nokia (Trolltech), and abandoned in 2009. Qt Extended Improved (http://wiki.openmoko.org/wiki/Qt_Extended_Improved) was found by the community to continue from there. AFAIK there has not been much development besides bug fixes, although well the amount of also new things radek and the people helping him have put to QtMoko is impressive to say at least. When talking about a base, the Debian 6.0 is a really good base for QtMoko. When talking about the Qt Extended Improved put on top of it, it's relatively easy to say that it's not the future proof way - at least there will not be much incentive to start rewriting big parts of it, since the actual APIs used to do those are obsoleted upstream. Qt Extended Improved would be needed to be maintained as its own upstream indefinitely. So far QtMoko is doing great and is an awesome out-of-the-box experience, but if one wants to think about longer term future, there is this chance: start investigating porting Qt Extended Improved / QtMoko applications to upstream Qt, on top of the Qt Lighthouse branch (I guess will be included in Qt 4.8 release properly). The Qt lighthouse is essentially abstraction of the lowest graphics layer so that like Qt Extended, Qt applications can be again directly run directly on top of framebuffer instead of X. Maybe that way, with a simple full screen window manager, could be a way forward? 3) If FSO, how many parts of the current QtMoko have to be rewritten? Will FSO be more difficult to use (in terms of writing new code)? I don't have much knowledge of QtMoko, but indeed switching to FSO would help avoiding writing multiple modem drivers for different platforms. For FreeRunner, the current one in QtMoko is working quite well though, and again all the connectivity code is already written in Qt Extended. There is also oFono in addition to FSO when talking about projects including modem drivers. 4) What about Qt Mobility? Qt Mobility is an extension of various libraries to Qt, and might include some of the stuff that was abandoned when Qt Extended was abandoned. 5) Will QtMoko still remain Debian-based? (I hope so! :) ) I guess it has shown to be worthy base :) It also helps to concentrate on purely the Qt / applications side, which is a big enough area by itself. 6) Is (or will be) there a way to write new apps (or modify extisting ones) in a relative easy way such as using Qt Creator? Well indeed yes, if the porting from Qt Extended to Qt 4.8 / Qt Mobility would be evaluated (is it any semi sensible amount of work to get it started) and done. Qt Creator also allows plugins, like QtMoko plugin to automate application deployment et cetera. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2011-05-01 issue is out
Newest community update now available at http://wiki.openmoko.org/wiki/Community_Updates/2011-05-01 and plain text version below. This issue was brought to you by: * Hns * Nhv * Psonek * TimoJyrinki ( as usual, you can help out with the next issue at http://wiki.openmoko.org/wiki/Community_Updates/Draft_2011-06-01 ) Also http://wiki.openmoko.org/wiki/Community_Updates/2011-03-01 was published in March but not seemingly announced on the mailing lists. Thanks additionally to Jeepingben, Toams, Kukide, Papa-piet, Nightshade, Siteplanet and Jluis for that issue. Period 2011-03-01 to 2011-04-30 *** Hardware *** Freerunner RFID Board - new hardware mod announced http://wiki.openmoko.org/wiki/Freerunner_RFID_Board Freerunner Navigation Board v3 - new version ready http://wiki.openmoko.org/wiki/Freerunner_Navigation_Board_v3 GTA04 - engineering hardware (A2 revision) boots to Linux/Debian/LXDE - YouTube Video: [1] http://wiki.openmoko.org/wiki/GTA04 http://www.youtube.com/watch?v=3KnJc7eImQ4feature=channel_video_title *** Distributions *** Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices. Android Cupcake [Stable, January 2011] The AoF community has uploaded an update of the stable Cupcake release of AoF. This release contains: * All fixes from Android Cupcake (Google via scarhill) * Separate NAND or SD based installations (ran) * Improved GPS timestamps (Michael) * Updated APN list from Cyanogenmod (scarhill) * WMIConfig for boosting WiFi power (Niels) * Improved backup script (Teodor, ran) Codename: 'Android Cupcake on Freerunner' Homepage: http://code.google.com/p/android-on-freerunner/ Image: How to install Android Froyo [Experimental, April 2011] The AoF community has uploaded an update of the experimental Froyo release of AoF. This release contains: * All fixes from Android Froyo (Google via scarhill) * Separate NAND or SD based installations (ran) * Improved GPS timestamps (Michael) * Updated APN list from Cyanogenmod (scarhill) * WMIConfig for boosting WiFi power (Niels) * Improved backup script (Teodor, ran) * GPRS fix (scarhill) * Bluetooth, sound an performance improvements (ran) * Freeze fixes (ran) * Improved battery status indication (ran) * CMUX fix (panicking) Codename: 'Android Froyo on Freerunner' Homepage: http://code.google.com/p/android-on-freerunner/ Image: How to install Debian GNU/Linux Debian is a universal operating system used on many embedded devices, servers and home computers. Using Debian on the FreeRunner gives access to the huge army of software packaged in the Debian repositories, already compiled for the Neo's ARM(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. General news: * Debian 6.0 was released! * First (Openmoko specific) Linux 2.6.37 kernel is available. Highlights: * Rebase on qtmoko-2.6.37-v35 branch of QtMoko (2.6.37.6 stable branch + openmoko patches) * Add back a few wishlist configuration items not yet in QtMoko, including NFSv4, XATTR, CONFIG_OPENMOKO_RESUME_REASO * Caveats: See Community_Updates/2011-02-01 * New E17 packages uploaded to Debian unstable * Still work to do, not all packages updates with also prevents uploading a few Openmoko related packages like Zhone and Intone * Call for help in E17 packaging posted at http://lists.debian.org/debian-devel/2011/04/msg00907.html * Debian unstable is currently... unstable because of E17 transition, a touch screen driver change et cetera. Recommended Debian usage at the moment would be Debian 6.0 + only what you need from testing or unstable (like E17/Zhone). * New xf86-video-glamo uploaded to work with new X.org * omhacks 0.13 and 0.14 uploaded with new features and fixes Codename: 'sid' Homepage: http://wiki.debian.org/DebianOnFreeRunner Image: http://wiki.openmoko.org/wiki/Debian QtMoko [Stable, March and April 2011] New experimental (v34) and then stable (v35) QtMoko release: * QX installs Xglamo as debian package * WLAN with wpa-psk can now connect more then once (Alfa21) * QNetWalk package has been fixed * accelerometers in QtMaze now work * NeronGPS moved back to old nice version * disabled disk cache in Arora * qtmoko bookmarks in Arora * usb mass storage has now param removable=y for happy winxp (Alfa21) * faenqo theme - added golden debian background (Tiago Bortoletto Vaz) * themes now use jpg for backgrounds to save space (Tiago Bortoletto Vaz) * docked keyboard - fix ctl and alt keys always pressed (Gennady Kupava) * disabled login on tty1..tty6 to
[Debian] 2.6.37 kernel available (and about the touch screen X driver problem)
Hi, During the night my native Neo compilation of 2.6.37 kernel succeeded, and is now uploaded to Debian's pkg-fso repository [1]. The sources are in git [2] as well, although this was again a complete rebase. [1] http://pkg-fso.alioth.debian.org/debian/pool/main/l/linux-2.6-qtmoko/ [2] http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git The new package name reflects the fact that the upstream is QtMoko's git repository, which adopted our Debian packaging as well recently. There was a hint reportedly on IRC that the recent touch screen problem with Debian unstable would be caused by xserver-xorg-input-tslib being compiled against more recent kernel headers. Alas, it seems that touch screen even on this 2.6.37 kernel didn't start to work right away. Maybe with 2.6.39/2.6.40 then, which also have more upstreamed Openmoko drivers once again (thanks to those people). Anyway, it's now available for experimentation, and if you are staying more with Debian 6.0 like I do on my daily phone, it might be actually a great kernel to use - I haven't tested it yet. Below is the changelog including the previous Debian version (QtMoko took the packaging of one before it) and QtMoko: --- linux-2.6-qtmoko (20110412.git425779c72-1) pkg-fso; urgency=low * Rebase on qtmoko-2.6.37-v35 branch of QtMoko - Packaging of which was based on 20101108.git1508bbb5-1 * Add back requested configuration switches: - CONFIG_TASKSTATS, CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING - CONFIG_LBDAF, CONFIG_PROC_EVENTS, CONFIG_EXT*_FS_XATTR - CONFIG_NFS_V4, CONFIG_NFDS_V4 - CONFIG_OPENMOKO_RESUME_REASON * Add patches that still apply: - 0007-Make-PTRACE_SINGLESTEP-work-with-user-helpers.patch - 0008-Do-not-print-debug-messages-on-every-touchscreen-eve.patch * Adjust Maintainer and Uploaders -- Timo Jyrinki t...@debian.org Thu, 28 Apr 2011 18:22:36 +0300 linux-2.6-openmoko (20101212.git049b71de-1) pkg-fso; urgency=low * Merge from qtmoko-v31 - Kernel 2.6.34.7 - Integrated GPS suspend patch, resume reason patch - Dumb battery support * Disable sysrq, unneeded * Add configuration from wishlists: - NFSv4 - XATTR for EXT* - CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING - CONFIG_OPENMOKO_RESUME_REASON * Remove 2.6.29 era patches and others that don't apply anymore -- Timo Jyrinki t...@debian.org Wed, 15 Dec 2010 19:32:13 +0200 linux-2.6-qtmoko (v34-1) unstable; urgency=low * Update sources to 2.6.37 from openmoko git * Port qtmoko patches from 2.6.34 * QtMoko config -- Radek Polak pson...@seznam.cz Wed, 23 Mar 2011 14:33:56 +0100 --- -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2011-02-01 issue is out!
Newest community update now available at http://wiki.openmoko.org/wiki/Community_Updates/2011-02-01 and plain text version below. This issue was brought to you by: - Toams - Hns - PaulWise - Ssam - TimoJyrinki ( as usual, you can help out with the next issue at http://wiki.openmoko.org/wiki/Community_Updates/Draft_2011-03-01 ) Remember that when the date for the next issue arrives, feel free to do this publishing and wrapping up instead of me. - Period 2010-12-01 to 2011-01-31 *** Hardware *** In this issue there is a dedicated section to hardware. There has been no such section in the Community Updates mainly because after the 2008 launch of Neo FreeRunner, there hasn't been continuation to the Openmoko Inc's pioneering phone hardware with (mostly) CC-BY-SA schematics, 100% free software stack and all the other freedom joy... until now. GTA04 GTA04 is a project by the long time distributor and hw developer, German company Golden Delicious. The name is loaned from Openmoko project because of the spiritual continuation - GTA01 was the codename for Neo1973, GTA02 was the Neo FreeRunner, and GTA03 was the canceled successor product. Besides offering improved versions of Neo FreeRunner (better battery life, better audio output), they've a complete replacement board planned to fit an existing Neo FreeRunner case and use the existing display. The key details of GTA04 include among else: * OMAP3530 ARMv7 CPU * UMTS/3G (HSPA) * USB 2.0 OTG * WLAN, BT, FM transceiver * Barometric Altimeter, Accelerometer, Compass, Gyroscope * Optionally camera Find your GTA04 information at the following addresses: * http://www.gta04.org/ - technical: u-boot, kernel, Debian... * http://www.handheld-linux.com/wiki.php?page=GTA04 - shopping page * http://www.handheld-linux.com/wiki.php?page=GTA04-Early-Adopter - the early adopter program, although already finished Latest news: * gta04-owner mailing list founded, although occasionally you will find news also from the openmoko-community list among else; join the list at http://lists.goldelico.com/pipermail/gta04-owner/ * First engineering sample (GTA04A2) is working in PDA mode (U-Boot in NAND Flash) * GTA04A3 is getting final PCB layout fine tuning * UMTS (3G) modules have arrived. And GTA04 likely to have 512 MB RAM, 512 MB NAND Flash and 1GHz DM3730 CPU. http://lists.goldelico.com/pipermail/gta04-owner/2011-January/25.html Visit the FOSDEM in Brussels, Belgium next weekend (5th/6th of February, 2011) to see GTA04 in action and discuss about it! See http://fosdem.org/2011/ , http://wiki.openmoko.org/wiki/FOSDEM_2011 , http://lists.openmoko.org/pipermail/community/2010-December/063899.html *** Distributions *** Distributions lists releases and other significant updates in distributions that have some support for the Openmoko devices. Debian GNU/Linux Debian is a universal operating system used on many embedded devices, servers and home computers. Using Debian on the FreeRunner gives access to the huge army of software packaged in the Debian repositories, already compiled for the Neo's ARM(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. General news: * Third Openmoko specific Linux 2.6.34 kernel is available. Highlights: o Merge from qtmoko-v31 (2.6.34.7 stable patches, GPS suspend patch, resume reason patch) o Disable sysrq, unneededEXT4 support, UbiFS support o Configuration wishlist items: NFSv4, XATTR for EXT*, CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING, CONFIG_OPENMOKO_RESUME_REASON o Caveats: 1) No updated fso-config-gta02 yet in Debian, get your state files from eg. http://iki.fi/tjyrinki/moko/2.6.34/ 2) X.Org eats all the CPU unless you disable AutoAddDevices or remove extra /dev/input files, 3) Sys paths have changed, so you most probably want to add om gsm power 1 to /etc/rc.local (and install newest omhacks from pkg-fso if you already haven't) * Debian 6.0 is nearing completion! Planned release date is the weekend of FOSDEM, ie. 5/6th of February, 2011. For Neo FreeRunner, the Debian 6.0 status is the following: o No Openmoko support in the Debian kernel yet, you need to install one from pkg-fso repository: http://pkg-fso.nomeata.de/sid/allpackages o Otherwise you could survive with official, released Debian packages, but you are probably interested... + Newer versions of fso-config-gta02, fso-frameworkd and omhacks in pkg-fso + E17 wasn't released on time for Debian 6.0, so you need to get it from unstable (sid) repositories, or after the Debian 6.0 release from testing (wheezy in case of 7.0) to get for example Zhone software working * Omhacks
Re: [ANN]: GTA04 (Beagleboard inspired Openmoko Upgrade) - Early Adpoter Program
2010/12/21 Dr. H. Nikolaus Schaller h...@goldelico.com: So we are very confident that the already scheduled redesign (GTA04A3) will work right from the beginning and boot Linux. This looks like the start of the aera of new Openmoko devices. This is indeed the first time after Neo1973 and FreeRunner that there is equally exciting news. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] 2.6.34 Openmoko kernel package available
2010/12/16 Neil Jerram neiljer...@gmail.com: Even after removing the /dev/input files as you suggested (in /etc/rc.local), my observation is that XOrg still eats all CPU after an initial boot-up, but that if I then do /etc/init.d/nodm stop and /etc/init.d/nodm start, it returns to using a normal (small) amount of CPU. Is that as you would expect? That doesn't happen to me, but it's probably related to starting X in parallel with rc.local, so X gets to probe those before they are removed? Anyway, if one can come up with a perfect xorg.conf that disables the extra devices there and only configures glamo + touch input + hw buttons, that'd be nice. I noticed that wifi is powered on after boot-up. Is that expected? Note that I am not currently running frameworkd or other FSO daemons - so perhaps this is normal, and I haven't seen it before because the FSO daemons turn wifi OFF when they start up. (Alternatively, could wicd be powering on the wifi?) If I recall correctly that was always so in the old kernels as well, so even though it makes not much sense it may be so also now. But I'm using FSO so possibly it shuts the power off when starting (although, on the other hand, I wouldn't expect the FSO1 to know the sys paths in 2.6.34). For me, iwconfig shows the device but om wifi power confirms that it's not really powered up (and iwconfig says Tx-Power=off). I guess the interface is always there as ar6000 support is compiled into the kernel? -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] 2.6.34 Openmoko kernel package available
2010/11/14 Timo Jyrinki timo.jyri...@gmail.com: http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git;a=shortlog;h=refs/heads/debian-2.6.34 New Debian pkg-fso kernel available: And another one thanks to having inspirational time yesterday evening. Note that the original three 2.6.34 related caveats are still there: - No updated fso-config-gta02 yet in Debian, therefore you need to manually fix ALSA state files, see for example http://iki.fi/tjyrinki/moko/2.6.34/ - X.Org eats all the CPU unless you disable AutoAddDevices or remove extra /dev/input files - Sys paths have changed, so you most probably want to add om gsm power 1 to /etc/rc.local (and install newest omhacks from pkg-fso if you already haven't) --- http://pkg-fso.nomeata.de/sid/linux-image-2.6.34-openmoko-gta02 http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git;a=shortlog;h=refs/heads/debian-qtmoko-v31 linux-2.6-openmoko (20101212.git049b71de-1) pkg-fso; urgency=low * Merge from qtmoko-v31 - Kernel 2.6.34.7 - Integrated GPS suspend patch, resume reason patch - Dumb battery support * Disable sysrq, unneeded * Add configuration from wishlists: - NFSv4 - XATTR for EXT* - CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING - CONFIG_OPENMOKO_RESUME_REASON * Remove 2.6.29 era patches and others that don't apply anymore -- Timo Jyrinki t...@debian.org Wed, 15 Dec 2010 19:32:13 +0200 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No plans for fennec on the FR
2010/12/3 Delian deli...@gmail.com: Seems there's no hope of seeing a native FR version of fennec right now. [0] Well, we already have nice browsers so, it's not a real big problem (IMHO). :P [0] https://bugzilla.mozilla.org/show_bug.cgi?id=450929#c4 Well, Mozilla is not very famous of having much interest themselves in building end-user binaries for Linux platforms. Distributions do that for them, and similarly if Fennec will get mature at some point to the point it's feasible to package it into distributions, we'll get them through distributions that support FreeRunner's ARMv4, like Debian. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2010-12-01 issue is out!
Newest community update now available at http://wiki.openmoko.org/wiki/Community_Updates/2010-12-01 and plain text version below. This issue was brought to you by: - Toams - Valos - TimoJyrinki ( as usual, you can help out with the next issue at http://wiki.openmoko.org/wiki/Community_Updates/Draft_2011-01-01 ) Remember that when the date for the next issue arrives, feel free to do this publishing and wrapping up instead of me. - Period 2010-11-01 to 2010-11-30 *** Distributions *** Debian GNU/Linux Debian is a universal operating system used on many embedded devices, servers and home computers. Using Debian on the FreeRunner gives access to the huge army of software packaged in the Debian repositories, already compiled for the Neo's ARM(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. General news: * Second Openmoko specific Linux 2.6.34 kernel is available. Highlights: o EXT4 support, UbiFS support o GPS suspend handling patch from Gennady Kupava o Jitterless touch patch o CONFIG_HZ=100 o Miscellaneous configuration wishes fulfilled Codename: 'sid' Homepage: http://wiki.debian.org/DebianOnFreeRunner Image: http://wiki.openmoko.org/wiki/Debian *** Applications *** New Applications Micromoko Micromoko is a Twitter primarly for SHR/OE. It is written in C using Elementary, it has a builtin Twitter library. It's not available on SHR yet, you need to compile it manually. It depends on libmokosuite: http://gitorious.org/mokosuite2/libmokosuite Homepage: http://gitorious.org/mokosuite2/micromoko Package: sources Tested on: SHR Application Updates Podboy 1.7.2 A podcast aggregator / player written in Python / Elementary. * New release due to Elementary API changes in Icon, List and Toolbar widgets (python-elementary revision = 53901) Homepage: http://code.google.com/p/podboy/wiki/Overview Package: [1] Tested on: SHR Minneo 1.0.2 A classic Memory game * New release due to Elementary API changes in Icon, List and Toolbar widgets (python-elementary revision = 53901) Homepage: http://code.google.com/p/minneo/ Package: [2] Tested on: SHR Chroneo 1.0.1 A Stopwatch and Timer * New release due to Elementary API changes in Icon, List and Toolbar widgets (python-elementary revision = 53901) Homepage: http://code.google.com/p/chroneo/ Package: [3] Tested on: SHR Neomis 1.0.3 A computer version of the well-known electronic game named Simon * New release due to Elementary API changes in Icon, List and Toolbar widgets (python-elementary revision = 53901) Homepage: http://code.google.com/p/neomis/ Package: [4] Tested on: SHR NeoTool v1.3 NeoTool is a bash script for your desktop system to provide a friendly GUI frontend to some common management tasks, like for example flashing Openmoko smartphones. It is aimed at being very intuitive and easy to use, and flexible enough to make it useful in a wide variety of circumstances. * Added (broken) ubifs support per chris' patch Homepage: http://users.on.net/~antisol/neotool Package: [5] Tested on: openSUSE / CentOS / Fedora / Mandriva / RHEL *** General News *** Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc.. * Latest news on the ”GTA04” project from Golden Delicious - a project to create modern replacement board for the FreeRunner case + display, using ARMv7 CPU and 3G modem: http://lists.openmoko.org/pipermail/community/2010-November/063760.html * Presentation ”Tuning an old but free phone” was held at FSCONS 2010: http://losca.blogspot.com/2010/11/free-society-conference-and-nordic.html (video not yet available, only slides) *** Event News *** * 2010-12-04 German Open HardSoftware Workshop on 4th/5th December 2010 in Munich; will cover Openmoko, Beagle Board, Arduino, OpenPandora, ...; still in planing phase; to stay and participate in planning loop please subscribe to: http://lists.goldelico.com/mailman/listinfo/open-hard-software-event * 2010-12-?? Buzz fix and free beer brewing party in Washington, DC: http://wiki.openmoko.org/wiki/BuzzFixParty#Washington.2C_DC_-_United_States - tell about your interest! Mailing list post http://lists.openmoko.org/pipermail/community/2010-November/063770.html * 2011-01-24 Mobile FOSS MiniConf at LCA2011 announced a call for papers that closes on Friday 22nd October 2010. So submit something about OpenMoko today! * 2011-02-05/06 FOSDEM 2011 calls for Main Speakers and Devrooms [6] that closes on Saturday 16th October 2010. So submit something about OpenMoko today! ___ Openmoko community mailing list
Re: [Debian] aplay/mplayer broken with pkg-fso linux-image-2.6.34-openmoko-gta02?
2010/11/19 Gennady Kupava g...@bsdmn.com: I've noticed problem with alsa too. Guess that this may be related to 100hz patch, probably need to review neo-specific code in kernel. Ok, if that's it, even though it seemingly depends on other factors as well, please Debian users notice the following: * http://pkg-fso.alioth.debian.org/debian/pool/main/l/linux-2.6-openmoko/ has also all the previous kernels * If you hit this audio playback problem, install the previous kernel http://pkg-fso.alioth.debian.org/debian/pool/main/l/linux-2.6-openmoko/linux-image-2.6.34-openmoko-gta02_20100921.gitec52149c-2_armel.deb -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] aplay/mplayer broken with pkg-fso linux-image-2.6.34-openmoko-gta02?
2010/11/19 Paul Wise pa...@bonedaddy.net: Is anyone else having broken audio on Debian with pkg-fso linux-image-2.6.34-openmoko-gta02? Timo Jyrinki can reproduce it with one GTA02 but not with another one. Here are some symptoms: And the one I can reproduce it with is up-to-date sid, while the one where I have no problem is mostly pure Debian squeeze (only E17 and Zhone from sid and kernel from pkg-fso) with 127 unupgraded packages (ALSA among else). Paul mentioned he mostly has squeeze as well, so it might be even something in testing, just recently migrated? Same kernel is used on each device, and same modules loaded (audio support built-in). Mostly it would be good to hear from other Debian users if they are seeing the problem, or if they are not seeing it. Maybe we could then pinpoint what's causing the problem. My guess so far is that it wouldn't be kernel related, since I at least have audio perfectly functional on one device. I wouldn't have even noticed the problem if I hadn't tested audio on my playground Neo after Paul mentioned it... I will try to upgrade my working Neo to latest squeeze a few packages at a time at some point, but right now I don't have time and need that phone to be working :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: MeeGo 1.1 for FreeRunner?
2010/11/16 Gay, John (GE Energy Services, Non-GE) john@ge.com: Does anyone know how difficult it would be to port MeeGo to the FreeRunner? Well, it would require re-compiling MeeGo for ARMv4. I've been thinking about it, but more likely though I'll take a look at the handset UIs available and see about packaging such things to Debian... after all, I don't see that much extra value in a new distro as such, but I would see benefit in any handheld suitable applications/UIs that come out of MeeGo. Of course, both should be fun to do which is what matters... -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] 2.6.34 Openmoko kernel package available
2010/10/18 Timo Jyrinki timo.jyri...@gmail.com: [1] http://pkg-fso.nomeata.de/sid/linux-image-2.6.34-openmoko-gta02 [3] http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git;a=shortlog;h=refs/heads/debian-2.6.34 New Debian pkg-fso kernel available: linux-2.6-openmoko (20101108.git1508bbb5-1) pkg-fso; urgency=low * Merge from qtmoko-v29 - CONFIG_HZ=100 - Jitterless touch support - UbiFS support * As per request, enabled CONFIG_PROC_EVENTS and CONFIG_TASKSTATS * Add GPS suspend handling patch from Gennady Kupava - Needs also qi or fixed u-boot * Add also disabled patches which were missing from git * From lindi's patches: - Magic sysrq key enabled - Make PTRACE_SINGLESTEP work with user helpers - Do not print debug messages on every touchscreen event - Resume reason patch included, but disabled since fails to build -- Timo Jyrinki t...@debian.org Sat, 13 Nov 2010 15:53:24 +0200 Enjoy. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2010-11-01 is out!
Hi, Newest community update now available at http://wiki.openmoko.org/wiki/Community_Updates/2010-11-01 and plain text version below. In addition to myself, the latest edition was brought to you by: - Hns - Rohezal - PaulWise - Vanous ( as usual, you can help out with the next edition at http://wiki.openmoko.org/wiki/Community_Updates/Draft_2010-12-01 ) Remember that when the time comes, feel free to do this publishing. I didn't do it a month ago, so no-one did :) - Period 2010-09-01 to 2010-10-31 *** Distributions *** Debian GNU/Linux Debian is a universal operating system used on many embedded devices, servers and home computers. Using Debian on the FreeRunner gives access to the huge army of software packaged in the Debian repositories, already compiled for the Neo's ARM(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. General news: * New Openmoko specific Linux 2.6.34 kernel is now available as a package in the pkg-fso repository! Just do apt-get install linux-image-2.6.34-openmoko-gta02 (and check the symbolic links in /boot). Details at http://lists.openmoko.org/pipermail/community/2010-October/063463.html * While Debian itself is in freeze, omhacks 0.12 with newer kernel support and more was released at the pkg-fso repository: http://pkg-fso.nomeata.de/sid/omhacks * The main information wiki page was put up-to-date: http://wiki.debian.org/DebianOnFreeRunner * Even the most conservative daily FR phone users might be willing to upgrade at least to latest FSO1 stack: http://wiki.openmoko.org/wiki/User:TimoJyrinki#currentphonestack - of course, FSO2 (fso-gsmd) is also packaged and waiting for users... Codename: 'sid' Homepage: http://wiki.debian.org/DebianOnFreeRunner Image: http://wiki.openmoko.org/wiki/Debian *** Applications *** New Applications aTrack 0.8 APRS tracker and communicator for mobile devices. It turns your Neo into bidirectional APRS unit and besides others it allows you to track your position, do text messaging, object creation or display stations around. Homepage: http://atrack.googlecode.com/ Package: [1] Tested on: SHR-Unstable Application Updates Gamerunner GnuBoy 0.8 A gameboy emulator which runs very nice, even with sound (sometimes it freezes, then you have to press the A button and everything is ok). You need the gamerunner distro or a gamepad to use it. Using frameskip to run smooth at 320*240 pixel. In second controll mode in gamerunner you can use savestates by pressing top right corne to save and left lower corner to load. Select is right lower corner. Homepage: http://jlime.com/forum/viewtopic.php?f=117t=3005 Package: [nopacket no packet sorry] Tested on: Gamerunner, QTMoko FoxtrotGPS 1.0.0 FoxtrotGPS is an offshoot of Marcus Bauer's excellent Free Open Source tangoGPS application, with a focus on cooperation and fostering community innovation. 1.0.0 announcement. * Gracefully recovering from gpsd shutting down * GPX routepoints support * Integration of distribution patches * Map tiles are displayed immediately after downloading * GeoRSS points can be imported as POIs (script) * Various other fixes and improvements * Since no feedback gotten from the sister project and some changes will not be imported, version number 1.0.0 was selected to show that there is divergence Homepage: http://www.foxtrotgps.org/ Package: foxtrotgps Tested on: Debian *** General News *** Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc.. GPRS * GPRS on FreeRunner is unstable? Too many connections hang the modem? Unfixable? NO MORE! Our magician lindi has conjured a tc (traffic control) command that makes the data flow more stable even under heavy load. Huge thanks! http://docs.openmoko.org/trac/ticket/2264#comment:21 (use the lower one for faster operation) Kernels * Debian wiki now includes generic view on the multitude of Openmoko related kernel branches out there: http://wiki.debian.org/DebianOnFreeRunner#KernelBranchesinAutumn2010 * State of upstreaming kernel parts was updated by Lars-Peter Clausen and others in this thread: http://lists.openmoko.org/pipermail/openmoko-kernel/2010-September/011205.html - as always, help is welcome in the land of the kernel! Spin-off Hardware Projects * Another spin-off project possible: Always Innovating MiniBook would be a great basis for a free phone - it just lacks a GSM/3G chip... for now: http://lists.openmoko.org/pipermail/community/2010-October/063358.html * Openmoko Beagle Hybrid moving to OMAP4/Cortex-A9: http://lists.openmoko.org/pipermail/community/2010-October/063437.html Event News * 2010-10-12 Next
[Debian] 2.6.34 Openmoko kernel package available
Hi,
During the weekend I did a few cross-builds, emulated native builds
and finally native builds of the 2.6.34 Openmoko kernel for Debian.
It's now available at the pkg-fso repository [1]. It's basically
identical in code and configuration to Radek's qtmoko-v27 git branch
[2], with the added compilation of LED/vibration support. Debian
packaging [3] is virtually the same as with 2.6.29, only minimal
needed changes to bring it to 2.6.34 time. Huge thanks to Radek of
QtMoko fame and SHR people for dwelling through the git trees and
patching up on top of the git.openmoko.org trees to create an usable
kernel.
[1] http://pkg-fso.nomeata.de/sid/linux-image-2.6.34-openmoko-gta02
[2] http://github.com/radekp/linux-2.6/tree/qtmoko-v27
[3]
http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git;a=shortlog;h=refs/heads/debian-2.6.34
I think the 2.6.34 is a great step forwards, although with a few
caveats for existing Debian w/ 2.6.29 users:
- ALSA switches have changed names. You need to update your state
files manually for now. Some reference can be found at
http://users.tkk.fi/~tajyrink/moko/2.6.34/ for a) phone calls and b)
so that also alerts are heard. I also hacked the headphones out
profile but didn't put it there. Those are probably not optimal, but
work. Updated state files should of course started to be offered by
us, Debian's FSO team.
- Many SYS paths have changed. I've om gsm power 1 in /etc/rc.local
as one easy workaround for GSM functionality, and I have also been
using the om tool (from omhacks) also otherwise. Newest omhacks is in
pkg-fso repository, and yet more 2.6.34 fixes for it coming reportedly
soon from lindi co. Most programs probably also don't know anymore
how to control the vibrator, since its path has also changed.
- X.org auto-configuration is in troubles compared to 2.6.29 kernel
(where at least I used xorg.conf with only glamo driver section). I
didn't have time to look at it, so I've just rm /dev/input/event{3,4}
/dev/input/js{0,1} /dev/input/mouse0 in /etc/rc.local for now...
But with those caveats / upgrade problems everything seems to work:
GSM, GPS, Bluetooth, WLAN, LEDs, suspend/resume, and reportedly also
power consumption under suspend is ok...
Note that of course this is not the correct way to do the kernel in
the long term, but I was just willing to spend some of my limited free
time on offering this 2.6.34 branch to the Debian users. What is
really needed to be done (yet again re-iterated) is upstreaming the
rest of the code needed by FreeRunner [4] and helping official s3c24xx
support in the Debian installer / kernel [5]. It is however noticeable
how huge improvement this is over the old 2.6.29 branch. The 2.6.29
kernel was based on _rc3_ of Linus' 2.6.29. There was a rc8 before the
stable 2.6.29 release and six stable updates. After the rc3 however
the git.openmoko.org:s andy-tracking tree was patched over the
following 1.5 years without merges from the stable tree. Compared to
that, with the current 2.6.34 tree [6] we're able to see stable/final
2.6.34 commit by Torvalds already on the second page of the commit
log.
[4]
http://lists.openmoko.org/pipermail/openmoko-kernel/2010-September/011205.html
[5] http://git.debian.org/?p=pkg-fso/kernel.git;a=shortlog;h=refs/heads/s3c24xx
[6]
http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git;a=shortlog;h=refs/heads/debian-2.6.34
As a final note, Radek didn't yet include Glamo KMS/DRM support in the
2.6.34 (I think a bit more KMS/DRM problems have been seen with 2.6.34
than 2.6.32), and I didn't start doing it either. Naturally that's the
biggest omission we now don't yet have regarding the work done on
FreeRunner kernels during last and this year. The KMS support is
available in Thomas' branch [7] and SHR's patches [8] - I don't know
what's the delta between them.
[7] http://git.bitwiz.org.uk/?p=kernel.git;a=shortlog;h=refs/heads/gdrm-2.6.34
[8]
http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-openmoko-2.6.34
-Timo
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: New Phone Project (MiniMoko) : Which functionalities ?
2010/10/6 Edder ed...@tkwsping.nl: Will it support headphone, with a microphone? I think it's safe nowadays to just assume Bluetooth headphones, ie. not all devices need the extra plugs if something has to be sacrificed. 2010/10/6 giacomo 'giotti' mariani giacomomari...@yahoo.it: Looks like it miss USB connectivity and I need SSH strongly! Well SSH over Bluetooth personal area network works just fine, but indeed I'd also like USB port for charging and connecting other devices (host mode) 2010/10/6 Maksim 'max_posedon' Melnikau maxpose...@gmail.com: Sorry, I don't have skills in GPS, I just see that FR have a problem with getting fix It doesn't have a problem getting fix hardware-wise, probably just the software you use is not similar in features to eg. separately sold navigators. Which means that you have it always getting a fix starting without any data, where it takes similar time (or less) to most separate GPS devices. Basically the GPS hw on FreeRunner is quite good. I don't know what's the status of saving the GPS data and re-uploading those when turned on. Is it implemented in some version of FSO/gpsd or other software. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: wiki.openmoko.org unreachable?
2010/10/7 Joerg Reisenweber jo...@openmoko.org: hetzner moved irons. fs needed fsck and other service, after 2 years 'uptime' Central Services (aka roh, gismo) is taking care of it. ETA unknown yet. Thanks for letting us know. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2010-09-01 is out
Hi, Newest community update now available at http://wiki.openmoko.org/wiki/Community_Updates/2010-09-01 and plain text version below. In addition to myself the latest edition was brought to you by: - Sre - Leadman - Toams ( as usual, you can help out with the next edition at http://wiki.openmoko.org/wiki/Community_Updates/Draft_2010-10-01 ) --- Period 2010-08-01 to 2010-08-31 *** Distributions *** Debian GNU/Linux Debian is a universal operating system used on many other embedded devices, and also on home computers. Using Debian on the FreeRunner gives access to the huge army of software packaged in the Debian repositories, already compiled for the Neo's arm(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. General news: * The ARM servers sponsored by ARM Ltd. got activated, thus experimental packages are built for arm now. That means also fso-gsmd got built for the Freerunner. * SHR packages have been removed from pkg-fso repository, they all arrived in Debian unstable, and just in time for Debian 6.0 freeze. The biggest hurdle for official FreeRunner support in Debian is the kernel, since basically everything else starts to be in, in one form or another. There are currently two places with FreeRunner related kernels in Debian: * Official kernel support for Neo FreeRunner devices is being developed by worked in a s3c24xx branch at http://git.debian.org/?p=pkg-fso/kernel.git;a=shortlog;h=refs/heads/s3c24xx - thanks to Thibaut Girka and Google Summer of Code. * The legacy 2.6.29rc3 kernel at http://git.debian.org/?p=pkg-fso/linux-2.6-openmoko.git also saw a slight update in August - this is still included in Debian installations by default Codename: 'sid' Homepage: http://wiki.debian.org/DebianOnFreeRunner Image: http://wiki.openmoko.org/wiki/Debian QtMoko [v26] Qtmoko is distribution for Openmoko Freerunner phone based on debian and qtopia. Here is a list of notable changes since previous stable version (v24): * Fixed WS (white screen) problem in qmplayer QX rotation (Gennady Kupava) * Fixed unresponsive touchscreen after resume (Gennady Kupava) * Use blue indicator is used for wifi activity (Alex Samorukov) * Reconnect wifi after resume (Alex Samorukov) * Updated QtMaze with better graphics and other enhancements (Anton Olkhovik) * We use kernel modules for bluetooth * Many updates and bugfixes to QMplayer * More reliable GPRS connection (Alex Samorukov) * Bluethooth updates * APGS and GPS standby support (Piotr Gabryjeluk) * Fixed When locked power management mode * Bigger QTerminal (no tabs whith only one session) * Raptor - GUI for apt package manager * New nice theme called finximod (Joif) * Many updates and bugfixes to Arora (Ant+Alex) * New apps - qweather (Anton Olkhovik) and qneoriod game (Bala) * PDF support in eyepiece (Alex Samorukov) For a more complete list of changes and some additional info please read the announcement mail Codename: 'v26' Homepage: http://qtmoko.org Image: images *** Applications *** Application Updates eStarDict 0.3 Offline dictionary reader made in C with Enlightenment Elementary UI. Version 0.3 of eStarDict adds support for czech-english dictionary. You have to remember, that right now it can manage only one dictionary per instance. Homepage: http://www.vaudano.eu/wiki/en/estardict Package: http://www.vaudano.eu/wiki/en/estardictDownload Tested on: SHR-Unstable,SHR-Testing *** Community *** Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc.. * TI OMAP3 SoC + 3G replacement board preserving Neo case display - discussion about the prospect is heating up: http://lists.openmoko.org/pipermail/community/2010-August/062671.html * WikiReader sales and the future of Openmoko - Martix shares a truly interesting interview with Sean Moss-Pultz: http://lists.openmoko.org/pipermail/community/2010-August/062687.html * Glamo timing improvements (= more speed without caveats) can be done also in run time, and also pre-compiled Qi with settings set by Qi are available: http://wiki.openmoko.org/wiki/Smedia_Glamo_3362#Timing_settings *** Event News *** * 2010 Autumn German Open HardSoftware Workshop in Munich; will cover Openmoko, Beagle Board, Arduino, OpenPandora, ...; still in planing phase, Doodle scheduling link: http://www.doodle.com/93cu86vm2s69zsxc ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: WikiReader sales and the future of Openmoko
2010/8/20 Jim Ancona j...@anconafamily.com: True with respect to most phones, because hardware manufacturers don't release their drivers. Not true with respect to the Freerunner. In any case, Android is exactly as free as Linux is, because you would have exactly the same problem running any Linux-based OS on that hardware, correct? So Linux is not free by your definition. I think the confusion usually arises from the fact that Android is usually used to indicate devices sold with Android. No Android shipping phone runs on just free software (on the main CPU) currently, except if all the limits with HTC Dream, which I think people have been hacking on the most, have been surpassed. But there are also other aspects than being free or non-free, like being a successful open-source project in terms of open development, external developers in the core components (besides kernel) et cetera. In that sense I and probably many others still very much prefer GNU-userland / something-we-all-know-better type of distributions over Android software. On the other hand, talking from hardware vendor point of view, free and ready touch device softwares are still a bit lacking, so Android could be a solution for something to ship on the device, similar to Om2007.2. Remember that if doing some FreeRunner successor kind of thing, it doesn't matter that much what is shipped with it. And if it frees up developer resources to doing just hardware and kernel support by not doing a huge effort like OE-based Om2007.2/Om2008/Om2009 on the software distribution, I'm all for it. But if the vendor is going to build some application software, I'd vote for doing that for some other platform than Android stack, if for nothing else then for increasing competition in the free software touch/mobile applications. By the time any successor hardware would be available, MeeGo with handheld packages is probably anyway a better starting place, since it's a true GNU/Linux distro. I'm not saying Android has serious flaws, I just strongly think that the longer roots in the open world the better for the healthiness of the open software. Big piles of code-dropped code takes time to become an open project, similar to what we'll certainly see with Symbian that is now all open. Personally I'd go for Debian all the way but I know the real-world-use touch applications will first arrive somewhere else and only later will be packaged on Debian, like we do in the pkg-fso group. But if the vendor would like to spend some time on the distribution software as well, I think Debian is The way to go for longevity of the product and its software. As a major component of it involves getting all the kernel code upstream :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
2010/3/3 Sebastian Reichel elektra...@gmail.com: I think both ext3 and jffs2 should be built-in since they are the two kinds of filesystems most widely used on the FR. Ok, I will reenable this one, too. I uploaded a new 2.6.29 kernel to Debian's pkg-fso repository yesterday. It includes some of Sebastian's earlier commits that were not yet released, and furthermore patches to fix the following: http://docs.openmoko.org/trac/ticket/2327 (workaround delay patch) http://docs.openmoko.org/trac/ticket/2328 (patch from the ticket, not thoroughly tested) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2010-08-01 is out
Hi, Newest community update now available at http://wiki.openmoko.org/wiki/Community_Updates/2010-08-01 and simplified text version below. Thanks for the latest edition to: - Martix - Sre - Hns - TimoJyrinki - Cmair ( as usual, you can help out with the next edition at http://wiki.openmoko.org/wiki/Community_Updates/Draft_2010-09-01 ) Period 2010-07-01 to 2010-07-31 *** Distributions *** Debian GNU/Linux Debian is a universal operating system used on many other embedded devices, and also on home computers. Using Debian on the FreeRunner gives access to the huge army of software packaged in the Debian repositories, already compiled for the Neo's arm(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. * A new e17 - http://wiki.openmoko.org/wiki/E17 - snapshot has been uploaded to Debian (0.7.0.49898) * The remaining SHR packages were prepared for main inclusion and are now in the NEW queue: libphoneui-shr, phoneuid, phoneui-apps * Intone - http://wiki.openmoko.org/wiki/Intone - got updated to the most current revision (r77) * FoxtrotGPS - http://wiki.openmoko.org/wiki/FoxtrotGPS - was uploaded to Debian main archive and replaced TangoGPS * fso-gsmd is still depending on vala version that is only in the experimental branch, and therefore not compiled for FreeRunner yet Codename: 'sid' Homepage: http://wiki.debian.org/DebianOnFreeRunner Image: http://wiki.openmoko.org/wiki/Debian Qtmoko [v24] QtMoko is a distribution based on Debian and Qt Extended Improved (formerly Qtopia). There is no new version since the latest update. However, a few news items are available: * QtMoko v25 is in development and will be using the 2.6.32 kernel by default. * Joif announced a new theme for QtMoko: http://lists.openmoko.org/pipermail/community/2010-July/062571.html Codename: v24 Homepage: http://www.qtmoko.org Image: http://sourceforge.net/projects/qtmoko/files/ Applications No application reports this month, although surely there are new releases all the time :) Community Most important and change making mails on the mailing lists, blogs etc.. Coolest hacks, screenshots, themes etc.. * Gennady Kupava proceeded onwards in his amazing work from overclocking FreeRunner (see Community Updates/2010-07-01) to speeding up Glamo graphics chip's timing settings: http://lists.openmoko.org/pipermail/community/2010-July/062495.html . As always, proceed with your own risk, but indeed this is not overclocking but pure timing settings tweaking similar to DDR latency settings in ordinary computer BIOSes. * While ordinary users might stick to the venerable 2.6.29 (andy-tracking) branch or try out 2.6.32, the newest development actually already happens in branches based on Linux kernel 2.6.34: http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/om-gta02-2.6.34 . Work done by Thibaut Girka, Lars-Peter Clausen, Thomas White and Martin Jansa - thanks to all effort by these guys, testers and other helpers! * The 2.6.32 kernel branches at git.openmoko.org are not currently completely ready for end users. SHR maintains a big bunch of patches that are needed for some components to work: http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-openmoko-2.6.32 * Golden Delicious Computers released Openmoko Beagle Hybrid Boards including GPS and a gyroscope. At the same time, they announced - http://lists.openmoko.org/pipermail/community/2010-July/062609.html - plans to develop the next open hardware phone. Based on a OMAP3530 SoC this device will bring a lot of computing power to your pocket. * The Freerunner Navigation Board v2 - http://wiki.openmoko.org/wiki/Freerunner_Navigation_Board_v2 - is being tested right now. The first fully assembled boards are expected to arrive within the next two weeks. If you are interested in buying one you can still specify - http://wiki.openmoko.org/wiki/Talk:Freerunner_Navigation_Board_v2 - which chips you'd like to have preassembled. More about community on the Community Resources page / http://wiki.openmoko.org/wiki/Community_Resources. Event News * 2010 Autumn German Open HardSoftware Workshop in Munich; will cover Openmoko, Beagle Board, Arduino, OpenPandora, ...; still in planing phase ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] [Community Updates] 2010-08-01 is out
2010/8/4 Patryk Benderz patryk.bend...@esp.pl: Thanks guys! Although QtMoko v24 was released and described in June: That's why it says there has been no new releases since last update, and reports on what's happening regarding the future release :) I think the distribution parts do not need new releases to be included, if there is just something newsworthy going on. I thought (I was the one adding the QtMoko section) that the permanent switch to 2.6.32 in QtMoko sounds interesting, and found also the bit about new theme being available. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Glamo slowness question. Glamo transfer speed improvements (+33%). Video sofdecoding playing profile. Glamo dma transfer.
2010/7/17 Gennady Kupava g...@bsdmn.com: Here is my next rant to freerunner slowness :) A great way to rant :) The glamo timing fix seems to work great here so far. Regarding the older thread, I finally tested also it with the 500/83 CPU/memclock setting (533/88 hanged during boot when most of the system was already running), and it also worked fine. However, CPU overclocking probably increases power consumption, while the glamo boosting is probably quite pure win over-all, especially considering that glamo is the biggest bottle-neck anyway in the device. Expecting some reports from users, did it work for you flawlessly? So far, yes. 2. --- DMA transfers ... Conclusion - implementing dma for mmc and glamo may provide speedup to system, also it may reduce emergy consumption (as cpu may sleep while dma transfer is active) That's interesting as well, since it would be again be overall win in all aspects. Thanks a lot for the work so far, you are the heroes making FreeRunner project all the more interesting and unique :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: My N900 experience compared to my FR experience (was: Re: [QtMoko] handset is (almost) unusable for voice calls with background noise)
2010/7/7 Brolin Empey bro...@brolin.be: I know the N900’s kernel is relatively old (2.6.28.x) and the N900 is less open than the FR, but this does not matter to me because it is an acceptable compromise in order to have a far better experience with a more powerful and current device. Sure, a finished product from world's biggest phone manufacturer no doubt works better (even if also their first Linux phone). And I also recommend N900 to anyone. FreeRunner is the no-compromise way for freedom enthusiasts like me, or people liking to hack otherwise but have some actual spare phone for basic phone usage (because the phone part is one of the most difficult aspects to get working trustworthily if using a heavily hackable and changing distribution like Debian). I'm myself also quite happy with my FR (running Debian) overall, given that I have a separate 3G modem for computer use, but with FR you know you always need to do some hacking :) Well, maybe not much with QtMoko but I've heard it specifically has had some SMS problems. The other distributions need tweaking for sure, even SHR. Then if you have one working setup and don't touch it, you can safely use it for months trouble-free, but it's not always apparent what versions of the FSO stack for example are good for daily use. FreeRunner is a bit like an old (classic) car - you know it will need great care, you know it's not the fastest four-wheel on the block, but damn it's elegant when you've yourself made it go so smoothly and know how beautiful it is inside :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: My N900 experience compared to my FR experience (was: Re: [QtMoko] handset is (almost) unusable for voice calls with background noise)
2010/7/7 Sebastian Reichel elektra...@gmail.com: https://elektranox.org/website/debian_on_n900.html Thanks for your great work with Debian on N900. I do look forward to 2011 or 2012 to eventually do a switch from FreeRunner, and N900 is one (and currently best) possibility. It wouldn't hurt, though, if some truly (with some definition near FR's definition or better) open phone would come out by then. I know I _could_ make the switch the day the N900 ofono driver is ported to FSO or GUIs for ofono would be made (and the modem driver would be stable in the first place, which might take time), but my main line of thought is that now that I have a working phone running Debian, I'm not that eager to switch just for the sake of it or just for speed, especially if it means sacrificing a few freedoms. Maybe if something new in the spirit of Openmoko would arise... like the leviathan's prospect that he mentioned on the gta02-core mailing list last month. Let's hope for the best, and meanwhile freeing not-completely-free-but-near phones is the next best thing to do. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: andy-tracking and gdrm-2.6.32
2010/5/16 mobi phil m...@mobiphil.com: I am a bit confused with the kernel branches... I assume that om-gta02-2.6.32 is the 2.6.32 kernel version one people are experimenting in distros... However I was reading references to the drm/kms changes in those distros, but your kms/drm changes do not seem to be merged into om-gt02.6.32. Yes, the KMS/DRM stuff is so interesting distributions are probably basing off gdrm-2.6.32. I am working on gdrm-2.6.32, but the only problem is that bluetooth is not working at all.. Did you ever use bluototh on gdrm-2.6.32, or did anybody else do so? I haven't recently tried it out, but all in all you may be interested in using http://git.bitwiz.org.uk/?p=kernel.git;a=shortlog;h=refs/heads/gdrm-for-merging, which is basically the very latest om-gta02-2.6.32 + KMS/DRM support. It's not currently available at git.openmoko.org. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Netbook Launcher EFL on FreeRunner for launching applications
Hi, I compiled Ubuntu's Enlightenment version of their Netbook Launcher on FreeRunner, and it's working relatively nicely! My main problem is the green background :P http://users.tkk.fi/~tajyrink/moko/netbook_launcher_efl_on_freerunner.png Has anyone else tried it out? Or just feel free to jump in. On my Debian I just: dget -x http://archive.ubuntu.com/ubuntu/pool/main/libl/liblauncher-0.1/liblauncher-0.1_0.1.10-0ubuntu1.dsc dget -x http://archive.ubuntu.com/ubuntu/pool/main/n/netbook-launcher-efl/netbook-launcher-efl_0.2.6-0ubuntu2.dsc and compiled. I think it needs also at least gnome-menus package to be installed. I think I could happily switch from my lower left corner application menu to this totally finger usable thing. The touch should be made a bit less sensible, but otherwise eg. animations are already smooth. I would just want one more thing - long AUX press for getting a selectable list / grid of running applications, so I could get rid of my matchbox top bar (see http://wiki.openmoko.org/wiki/User:TimoJyrinki, netbook-launcher-efl is just drawing over it in the above screenshot)). Any idea of such an application? -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Netbook Launcher EFL on FreeRunner for launching applications
2010/5/7 Vinzenz Hersche hers...@puzzle.ch: hey, wow, looks nice :) could you pack this to a image/tar? Sure. http://users.tkk.fi/~tajyrink/moko/netbook-launcher-efl/. Both debs and tar.gz:s created with alien. Zero guarantees, dependencies look to be: libeina, libecore, libevas, libeet, libedje, libelementary, libglib2.0, libgconf2, libgtk2.0, libdbus-glib-1, libnotify, libcanberra, libunique, libwnck and libgnome-menu. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Debian package for v21
2010/4/14 Vincent Meurisse openmoko-commun...@meurisse.org: Debian package for QtMoko v21 are ready. Instruction for update are located at http://qtmoko.org/wiki/Update. Can those be used to install Qt Extended Improved / QtMoko on top of normal Debian? Or any plans on properly packaging Qt Extended Improved to Debian? Just asking out of curiosity, and if anyone is working on that. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Triggering Literki from command line?
2010/4/16 Neil Jerram neiljer...@googlemail.com: literki But is that what you meant? He certainly meant unhiding the keyboard of already running literki process. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: tangoGPS community development, patches (was: tangoGPS magnify patch)
2010/4/12 Joshua Judson Rosen roz...@geekspace.com: So, how *should* I collaborate? What mailing-list should I use? When I fix an upstream bug, in what BTS should I publish the patch? Where can we talk on IRC about current developments in tangoGPS, if anywhere? I agree. After my second translation patch (fixing a few typos and adding a few more translations) was not included, found out only by waiting a few months for the next TangoGPS code drop, I dropped contributing until there is a proper version control system where one can see if changes are committed or not, and a mailing list. It's now been a year or two since that. There is unofficial, non-endorsed IRC channel nowadays. I wouldn't mind if there was an unofficial, non-endorsed version control system and mailing list as well. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: tangoGPS community development, patches (was: tangoGPS magnify patch)
2010/4/12 Marcus Bauer marcus.ba...@gmail.com: Essentially it is the constant threads about forks that have been started and fuelled over and over again by Risto that keep me having always a few aces in my sleeve and restricting access to people who I have confidence that they keep the project over their ego. I don't know what egos you are discussing (I haven't followed previous TangoGPS discussions that closely). You can restrict any access even if you allow read-only following of the development version source control. It's essential for any open source development project with more than one person interested in developing it. The fear of forks is probably simply because currently there is no way to really have a development project where others than one person can eventually affect the future of the project. E-mail patches without return channel or follow-up possibility does not really work. Anyway, I personally wouldn't want a fork, if it can be avoided. The developer community, if there is more than one person, just completely needs developer tools like version control and mailing lists, which are currently not available for this project, and have been in absence even despite months of silence on the front (so no shutting up of anyone needed). I was thinking about a system where latest source code is imported and patches can be tracked, which are applied, which are pending review, which are rejected etc. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: beautiful qt based
2010/4/8 Christoph Pulster openm...@pulster.de: excellent idea - this is exactly what Openmoko missed to do to get more interested customers (besides geeks). Yes. I check status of Openmoko and come to the result: OM Inc.: zombie Mostly, but especially they have moved away from phones to other areas. Community: nearly dead Not true. The problem is just that Openmoko the distribution is no more, and Openmoko the company is no more a phone company. People have now moved to distribution communities like SHR, Debian or QtMoko, and this so-called Openmoko community, what remains of it, is basically a set of people possibly caring of wiki.openmoko.org content, hardware owners that want to sometimes have a glance on whatever new distributions there are for the FreeRunner (like me) or people having belief Openmoko Inc. will come up with other interesting non-phone gadgets like the Wikireader. But mostly it always was about FreeRunner owners wanting to have official software distribution usable on their phones, but then the effort was stopped and moved to mostly SHR, which has its own forums. sales: 2/week (talking as the major distributor) Probably not that many FreeRunners sold at this point of time indeed, but I think many are currently interested in the pre-fixed versions, ie. #1024 and bass fix also included. If I'd be buying a new phone, like I just did with another FreeRunner, I'd enjoy that the hardware bugs, as many as possible, would be already fixed. FreeRunner had a good amount of those... lets wake up, the game is over :-( It has only begun in my opinion :) Neo FreeRunner is still the only phone (really) usable with free software like the FSO via SHR, Debian etc., but within a year we should some of the current development efforts on other devices - HTC Dream, Nokia N900, Palm Pre etc. - bring some more mature status where people can flash / reinstall their device and just use it as a phone. Before I can use Debian problem-free including phone functionality on some other device, I cannot see myself moving from FreeRunner to any other device. With luck, we will some more free-software friendly phone products coming out as well, to be a better continuation of the pioneering work Openmoko Inc's devices started and indeed not being a game over for resellers that did have some business being an Om Inc delivery channel. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Community Updates] 2010-04-01 is out
Hi all, Recent Community Update is out! Take a look at News link in Community box on wiki pages to read it. A text version of the update is included beneath this text, but it's partially more readable, and especially clickable, in the wiki. For your convenience here is direct link: http://wiki.openmoko.org/wiki/Community_Updates/2010-04-01 and feel also free to contribute to the new draft at: http://wiki.openmoko.org/wiki/Community_Updates/Draft_2010-05-01 Thanks to all contributors of this issue of CU: * Zeusone * Faltantornillos * TimoJyrinki * Hns * Multi * Vanous * Martix * Valos * Kichkasch ps. Feel free to do this announcement yourself in the change of the next month, there is no dedicated maintainer of community updates, ie. it's all of us :) Community Updates/2010-04-01 Period 2010-03-01 to 2010-03-31 ** Distributions ** Debian GNU/Linux Debian (http://wiki.openmoko.org/wiki/Debian) is a universal operating system used on many other embedded devices, and also on home computers. Using Debian on the FreeRunner gives access to the Huge army of software packaged in the Debian repositories, already compiled for the Neo's arm(v4) processor. Moreover, one can build one's own source files for programs without having to learn the OpenEmbedded way. For an existing Debian/Ubuntu user, choosing Debian for Neo FreeRunner makes phone a very familiar, trustworthy and flexible place to hack in. The following new noteworthy packages have appeared in the pkg-fso repository, a staging area for FreeRunner related packages not yet in official Debian: - literki (http://pkg-fso.nomeata.de/sid/literki), keyboard with configurable layout and transparency - woosh (http://pkg-fso.nomeata.de/sid/woosh), minimalistic browser optimized for touch screens - libdrm-glamo (http://pkg-fso.nomeata.de/sid/libdrm-glamo1), userspace interface to glamo-specific kernel DRM services, more info at http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2010-March/002731.html Each of the above has varying reasons they are not yet uploaded to official Debian archives. Literki included a version of png++ in its sources, and png++ has now been separated and literki will soon follow it to official Debian archives. The future of woosh browser is a bit uncertain, so it's waiting a bit eg. for a better replacement. Finally, libdrm-glamo is naturally waiting for the eventual inclusion of Glamo code in an upstream release, together with the hopeful integration of all Glamo code in upstream (Torvalds') Linux kernel. Besides applications, the following FSO components have been recently uploaded to official Debian archives: libphone-utils 0.1+git20091220-2, libgsm0710_1.2.1+git20100218-1, libfsobasics_0.9.0+git20100304-2, libfsoframework_0.2.4+git20100222-1, libfsotransport_0.9.5.9+git20100308-1, libgsm0710mux_0.9.1+git20100310-1, libfso-glib_0.2.1+git20100304-1 Codename: 'sid' Homepage: http://wiki.debian.org/DebianOnFreeRunner Image: http://wiki.openmoko.org/wiki/Debian HardwareWorks Neo 1973yes FreeRunner yes HTC-Dream yes Other yes ** Applications ** *** New Applications *** eStarDict 0.2 Offline dictionary reader made in C with Enlightenment Elementary UI Homepage: http://www.vaudano.eu/wiki/en/estardict Package: estardict Tested on: SHR-Unstable,SHR-Testing Chroneo 1.0.0 Stopwatch and Timer Homepage: http://code.google.com/p/chroneo/ Package: chroneo Tested on: SHR-Unstable *** Application Updates *** Bright Player 0.3 Quick and easy music player * bug fixes * SHR- testing compatible Homepage: http://www.faltantornillos.net/gnu/bright-player/ Package: [http://www.opkg.org/packages/brightplayer_0.3_all.ipk Bright Player 0.3] Tested on: SHR-Testing NeoLight 1.4.0 An application to turn your phone into a flashlight * Allocate Display resource when flashlight is active (no display blank, no suspend) Homepage: http://code.google.com/p/neolight/ Package: neolight Tested on: SHR-Testing, SHR-Unstable Podboy 1.5.0 Podboy is a podcast aggregator/player. Its interface aims to be easy and finger friendly. Main changes since version 1.3.0 are: * Played episodes that are older than a specified amount of days (defined in Settings) can be auto-deleted on every startup. * Episodes can now be tagged as (un)deletable in page Episodes. All episodes with status undeletable will be ignored when auto-deletion of old episodes will be done on startup. * Podcasts can be renamed. * Downloads can be canceled. * Add possiblity to activate multi selection in lists (a new option is available in section Interface of Settings). * Lot of improvements in feed parsing (add and update). * Now, when a Check For Updates is done for several podcasts, a full report is displayed in a dialog. * Podcasts source URLs can be edited. Homepage: http://code.google.com/p/podboy/ Package: podboy Tested on:
Re: AAVA Mobile?
2010/4/6 arne anka openm...@ginguppin.de: The issue is really what they mean by open. So far I think it means we have not restricted flashing different software on the device, the restrictions can be added by you, our future customer with deep pockets, who will be selling the actual end-user hardware to people. I'll be glad if it would turn out otherwise and be more concretely about freedoms. which of intel's hardware does not have open source, intel supported, drivers? The embedded graphics hardware they have licensed from powervr. ie. poulsbo / GMA 500. Powervr chips are used on about all embedded platforms, be it as part of Intel's poulsbo or independently. There is no pure intel graphics hardware usable on embedded platforms. All of powervr related graphics stuff is currently worse than even smedia glamo regarding the state of free software drivers. I'm also not sure if there is any Intel WLAN hardware suitable for devices of this size (and battery power). if they really make all drivers available (as with their graphic adaptors and wifi), it would be more open than the freerunner, wouldn't it? If, and a strong if, then software-wise yes. I'm quite sure Aava can do nothing to affect PowerVR, if even Intel, Nokia and Canonical have not been able to squeeze free, functional and maintained drivers out of there so far. Then there is also the hardware schematics and CAD side of things, where FreeRunner has also a degree of freedoms. Of course the software side is the most interesting for us software people. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian,QtMoko] X server and rotation
2010/3/25 Radek Polak pson...@seznam.cz: I tried xserver-xorg-video-glamo, but no success either. I thought so, just had to check. I have (had) a button (for a year) in my Debian that switches between xrandr -o right and xrandr -o normal without problems. Can you please tell, which kernel are you using and how did you install xserver-xorg-video-glamo? Is it from regular debian testing repos? I'm using http://users.tkk.fi/~tajyrink/moko/kernel_20100108_nodebug_nopreempt/ but it should be very close to http://pkg-fso.nomeata.de/sid/linux-image-2.6.29-openmoko-gta02 and others, I think, have xrandr working as well with 2.6.29. I installed it simply with apt-get install xserver-xorg-video-glamo. xorg.conf consists only of: Section Device Identifier Videocard0 Driver glamo EndSection xrandr tells me: Screen 0: minimum 240 x 320, current 480 x 640, maximum 480 x 640 LCD connected 480x640+0+0 (normal left inverted right) 43mm x 58mm 480x64072.5*+ 240x32050.2 Since you mention QtMoko, are you sure you're not using QtMoko's 2.6.32 kernel with KMS support? There the result might be a bit different, especially because the latest fix from git is not yet in Debian. Also note that xrandr --output LCD --rotate xyz doesn't work currently, only xrandr -o xyz. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian,QtMoko] X server and rotation
2010/3/24 Radek Polak pson...@seznam.cz: i have been struggling for some time to get X server working in landscape mode. I was trying: - Xglamo with xrandr - screen always goes white, reboot needed - Xglamo -screen 480x...@90 - does not work either, screen is somehow shifted - Xorg with fbdev driver and CCW option in xorg.conf - seems to have no effect - Xfbdev - does not support tslib in debian Hmm. Why use long-dead Xglamo or dummy fbdev instead of xserver-xorg-video-glamo? http://wiki.debian.org/DebianOnFreeRunner#Graphics.28SmediaGlamo3362.29 I have (had) a button (for a year) in my Debian that switches between xrandr -o right and xrandr -o normal without problems. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Debian] Timo's Debian instructions available for Neo FreeRunner
Hi, Setting up my second FreeRunner, I took time to find out and document how I ended up with my current Debian setup in use (or close to something like it) and cleaned up my configs while at it. This information might be interesting to beginning Debian / Neo users, who may find the default Debian installation a bit lacking or empty. Nothing earth-shattering to see here, but it works for me and I haven't tweaked any big stuff lately so I might as well publish it. So here goes, images included: http://wiki.openmoko.org/wiki/User:TimoJyrinki It's divided in Good, Ugly and Bad parts, for obvious reasons. Main ideas are that phone + GPS + keyboard + music playing are finger usable, and then for more fancy stuff a stylus can be brought to help. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Comparing A5 and A7 sound settings
2010/3/16 Rui Miguel Silva Seabra r...@1407.org: ' You may call my tests misinformation, but I'll calmly go on with usable sound settings with which I can be heard even from a noisy restaurant by *NOT*USING* the Correct setting. I am not claiming the wrong settings would not help. The main thing is that it should be possible to achieve the same situation with other settings, while keeping the audio path more sane. If it works for you, fine, but it's not exactly how the audio path should be configured in general. I did use wrong settings myself to a satisfaction for a long time, but they shouldn't be used in general. If you see http://www.mail-archive.com/community@lists.openmoko.org/msg58185.html - for example the same effect as raising control.12 from 5 to 7 like some people do when they feel they have too little microphone volume can be had by increasing control.5 by 6 values, but without having additional stage of amplifying (keeping control.12 at 5 means 0dB). The exact effect of setting Mic Sidetone Mux (control.63) to Right PGA instead of Mic 2 is not known, but it uses a wrong audio path and a similar way of lessening noise and mic volume should be done by using control.5 (mono playback) instead. I have also experimented with these on my A5 + buzz fix, and have not found there is any way to cheat the system so that using wrong audio paths would magically generate better audio quality compared to using correct audio paths (control.48 '3', control.12 '5', control.63 'Mic 2') and compensating with control.5 to the level wanted. And even if there was, my point is that the default configuration should be for A7, if there is only one configuration by default. Sorry for stating the information misinformation so strongly - I don't claim the information couldn't help some people finding values that happen to work for them, it's just not the optimal way to do that. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Comparing A5 and A7 sound settings
2010/3/16 Neil Jerram neiljer...@googlemail.com: I have to support Rui here. I find this over-theoretical argument really annoying. Sorry about that, and sorry about the term misinformation I used in the first post. Do you understand 100% the operation of the Wolfson codec? No. But I do believe Jöerg has better understanding about it than most others, and therefore I would not like to dispute http://docs.openmoko.org/trac/ticket/2121#comment:5 until there is such empirical proof that, like I said, changes in these wrong controls will create behavior that is better than is reachable by lowering control.5 while keeping control.63, control.48 and control.12 in the correct settings. And note I do use quotes, I don't claim there is one uttermost truth out there. It's easily seen in eg. that Jöerg's .new file has control.12 at 7 (not to speak about the original statefile suggested in the ticket which was quite bad), while the conclusion in the thread (link at http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem#Alsamixer_channel_controls) in Dec 09 pointed out that it should be 5. In the same post, btw, Al Johnson also agrees that there should be no point in routing via PGA (control.63). So, please could we have a bit more respect for people's empirical findings? I don't mean to disrespect empirical findings, I just find that since they are individual, they should not be generalized on a distribution level. For example, Debian recently switched control.63 to non-Mic 2 because of an individual finding, while I think this should not be done while the best knowledge is that control.63 should be kept at Mic 2, because other values mean extra routing. Even though it means more noise, simply because it raises the mic level and control.5 should be lowered until the noise is gone. I agree that being purely theoretical is not helpful, but I believe it's a good foundation to having correct default settings. And by correct default settings, I mean such that new owners of A7 phones would have a good experience, in which case empirical findings from A5/A6, buzz-fix or not, are not helpful when trying to make eg. SHR and other distributions good for the occasional newbies we still have. One problem is that mailing lists are not really optimal for collecting experimentation results, and on the other hand when people find something that works for them, they are probably not willing to experiment if it would also work otherwise. But I'd be happy if distributions would agree that proper default settings should be directed towards A7 users, unless detection of the model is offered. To give some more non-theoretical vibe to this thread, I started a new empirical mic data table at http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem#Empirical_Data_for_Mic_Settings - it's probable it will not be that helpful in searching any one true defaults, but it might be helpful to have known good experiences documented on a wiki, in a form of a table. I also added an experiment 1 there which is basically what I would think is interesting knowledge, if people just have the patience and devices (and subscriptions) to test it through. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Comparing A5 and A7 sound settings
Hi, I just bought myself A7+ FreeRunner since my A5 started to have its USB port breaking, buzz fix faltering, display problematic, plastic case pins broken etc. (1,5+ years of very heavy use:)). I just noticed that A7 requires much lower microphone settings than A5, something known but often forgot. I settled on the ones below for the A7. Having the Mono higher, I heard buzzing but with these settings it's gone and I can hear my voice in the other phone clearly/loudly still. I'm using one spare LG phone I have for the other end. Mic Sidetone Mux: 'Mic 2' = the correct setting, please try to not spread misinformation that it'd be wrong simply because it happens to also increase the volume and therefore buzzing as well if other settings are high Mic 2: '3' (= 0dB) Mono Sidetone: '5' (= 0dB,) Mono Playback '100 (= -21dB) (for buzz-fixed A5 I had this around 115) Just my two cents. I think at this point distributions' defaults should be towards A7 users, since all new users are anyway A7 users and A5/A6 owners by now are surely aware of the ALSA setting problematics. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: What to do with Freerunner / neo1973?
2010/3/7 Jay Vaughan j...@synth.net: ' Well after a year I've finally dug out these two gadgets and am wondering .. what to do with them? Anyone got any tips / tricks / suggestions for what to do with these old devices? I'd really like to catch up with you guys that are getting some value out of these devices and what you're doing with them .. I think for example this old thread lists quite a lot of what do you do with them items: http://www.mail-archive.com/community@lists.openmoko.org/msg49299.html Of course, some simply use it as a phone and nothing much more. so how about telling us old- timers just waking up what the current 'nicest OS' for the Freerunner is? Popularity wise it's SHR (http://shr-project.org/). I like Debian (http://wiki.debian.org/DebianOnFreeRunner) more because of its familiarity, universalness, stability when upgrading etc., but you need to enjoy tinkering since out-of-the-box it's not perfect and even installation may not be problem-free. QtMoko (http://qtmoko.org/) is a Debian + QtExtended based distribution with totally enjoyable out-of-the-box experience, probably the most normal users suitable distribution out there, at least in the sense it looks the most productized. From my perspective those are the top-3 distros, but of course there are loads of others as well - http://wiki.openmoko.org/wiki/Distributions. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
2010/2/21 Neil Jerram neiljer...@googlemail.com: ' Apart from factoring out those modules, is the new kernel improved in some way? And is it built without the debug settings? It's the latest upstream andy-tracking, mostly meaning that if compared to July snapshot Bluetooth, GPS etc. should handle suspend better among else. Debug is disabled. WLAN should work, but because of the debug being disabled one usually hits this bug quite soon: http://docs.openmoko.org/trac/ticket/2327 Also unfortunately due to some refactoring of touch screen code in andy-tracking, this happens from time to time, but luckily quite rarely: http://docs.openmoko.org/trac/ticket/2328 -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] minor enhancements
(forgot to answer to this) 2010/1/12 Neil Jerram neiljer...@googlemail.com: - In zhone, keep current SMS selected when returning from the SMS display screen. You could try to submit that to upstream [1] as well. I regard all of my patches as submitted upstream, by virtue of having been announced here. Is there a specific further step that I should take to offer and flag them to git.freesmartphone.org ? Well, I think you could discuss with FSO team if you could commit rights to the zhone repository there. It's the most obvious/known place anyway, and I'd think it'd bring more visibility to the patches in your tree if they would be there. If no one else wants to do it, I would be happy to be responsible for collating further zhone development. Exactly, and thanks a lot for your current work. The problem is that it's just too good-looking! I quite agree. Despite its limitations (like to send SMS receiver has to be in the addressbook, and the lack of proper phone log) I like it a lot. Can someone from freesmartphone.org comment on possible processes here? Maybe ask on http://projects.linuxtogo.org/pipermail/smartphones-userland/ list, or file a ticket in their trac asking commit permissions? Thanks, I will integrate these. [2] looks easy, but [3] looks like it will need a tweak to retain the current SIM-backed contacts too. Yes, it would probably need a bit more work. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: debian/fso on freerunner
2010/1/20 Michael 'Mickey' Lauer mic...@vanille-media.de: IMO Debian will eventually assimilate everything, including SHR. (Unless there is some major advantage of the OE build and packaging ... Well, I've been hearing that for almost a decade now, but still systems like buildroot, OpenEmbedded, OpenWRT, t2-project, etc. are being preferred on lots of embedded systems. Why do you think is that? (I might be partially wrong and it's not so black-and-white most certainly, but just trying to express why I love Debian over OE) I think it's largely because embedded developers often come from a different IT sector and tend to think the embedded device is something special and small, and that the approach of doing one single image / firmware fits the idea of embedded devices. But as FreeRunner is really a full-blown computer, not a router or other really small device by today's standards, Debian is something that removes the limits of this thinking. Debian has working upgrades, no removal of functionality wrt. i386 computers (unless you want it) and is simply vast in its scope - the fact you can run 95% of the 20k+ packages on FreeRunner and that they are all up-to-date is one statement of how much work has been achieved to keep up the scope of the project for all architectures. Of course most of those are not that practical to use on touch screen, but I wouldn't give the flexibility away. With the (in my opinion) old way of thinking towards this class of embedded devices, Emdebian is probably behind OpenEmbedded. But I think really it's becoming gradually less relevant, device class by device class. The only thing FR is lacking is large enough integrated flash memory, which is why a full Debian is usually used from SD card. Given the storage space of next generation mobile phones, I'd guess 2GB of flash is not a problem and you can fit a full Debian with compilation environment, documentation, office software etc. (and yes, phone software) without any problems. Partially OE is also about cross-compiling. Debian also supports it, but mostly the automatic package building is done on powerful enough ARM computers (512MB memory, 1GHz etc.). So in the old embedded world of thinking, you couldn't/shouldn't also compile on the target hardware (or target architecture) itself, but you have the development machine separately and you simply target the so-called small hardware. For an existing Debian/Ubuntu user, I cannot think of anything better than using Debian also on embedded devices. I use it on FreeRunner and my NAS device. With OE it very often seemed to be that when wanting newer software, flashing was recommended. And OE is simply a much smaller project packaging wise. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian/fso] how to enable wlan again?
2010/1/16 arne anka openm...@ginguppin.de: qdbus --system org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy WiFi enabled lindi found out that the new kernel is too fast which randomly fails the ar6000 initialization: http://docs.openmoko.org/trac/ticket/2327 I also noticed the problem last evening, although before that it had worked when I tested (as it works randomly). I now quickly recompiled the kernel with the suggested patch and put the resulting kernel at the familiar place: http://users.tkk.fi/~tajyrink/moko/kernel_20100108_nodebug_nopreempt/ According to the last comment in the bug report, the patch is not necessarily enough, but if it makes it better it's good. I have no time at the moment to test it extensively, but WLAN worked on first boot at least... -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qspectemu - zx spectrum emulator port for Freerunner
2010/1/13 Radek Polak pson...@seznam.cz: i have just finished porting of spectemu[1] to Qt and Freerunner. Thanks. I have to check how my BASIC programs from ca. 1989-1990 work on my Neo :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: literki update
And here you can find the source code (thanks to Christof and Christian): http://git.senfdax.de/?p=literki;a=summary I switched from matchbox-keyboard to literki yesterday evening on Debian. I wanted just the keyboard, so I patched it to remove everything else especially as those elements seemed to somehow block other items I liked to click. Furthermore, I added ä, ö and € letters and did some other mods. Put them now quickly at http://users.tkk.fi/~tajyrink/moko/literki_mods/ Thanks for the work, it's quite nice improvement over matchbox-keyboard at least. Of course there have been other options as well but I've been too lazy to try others out before this. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] minor enhancements
2010/1/12 Neil Jerram neiljer...@googlemail.com: - In zhone, keep current SMS selected when returning from the SMS display screen. You could try to submit that to upstream [1] as well. Since it's demo UI only, the upstream isn't developing it much but probably accepts patches. I've a patch I need that adds support for letters ä and ö [2], it wouldn't hurt to include that as well. [1] http://git.freesmartphone.org/?p=zhone.git;a=summary [2] http://users.tkk.fi/~tajyrink/moko/zhone-umlaut2.patch Then maybe [3] for reading addressbook entries also from a .vcf file wouldn't hurt those users that are only using SMS contacts. I like the ability to copy, backup and edit entries directly in a file. [3] http://users.tkk.fi/~tajyrink/moko/zhone-vcffile.patch Anyway likewise, feel free to use :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
New significant speedups coming to FreeRunner
Hi, Just FYI to the community list, as slowness has been one of the biggest problems with Neo. Quite nice speedups are coming: http://lists.openmoko.org/pipermail/openmoko-kernel/2010-January/010811.html (performance testing by Gennady Kupava) Apparently, and unfortunately, no-one had really questioned Om Inc:s (who mainly did the kernel work back in the days of the still mostly used 2.6.29) choices of kernel configuration. Disabling kernel debug features and pre-empt has resulted eg. these kind of improvements (from IRC, #openmoko-fi): - boot time 68.5% of original - apt-cache search nano 20s - 14.8s - emacs -f kill-emacs 3.8s - 2.2s These configuration changes are not yet in andy-tracking (the 2.6.29 kernel still being used in most distros), I don't know what's the situation in the new om-2.6.32 branch. Together with the quite recent commit from Thomas White that doubled theoretical glamo speeds (in practice at least 20% in general), I feel that Neo FreeRunner is not anymore terribly slow, but only slow by today's standards, which is quite an improvement. Especially after having been used to the terribly slow general behavior ;) Please tell if some distro happened to have those disabled already, and if someone knew about these speedups via the options already - and please arrange a commit to git.openmoko.org next time! Anyway, this all goes to show that in a project with limited resources like Openmoko, especially now that it's completely in the hands of the community when it comes to Neo FreeRunner development, you have to have the courage to question anything suspicious etc. you are seeing, not trusting that someone has actually optimized something to the extent assumed. If you want to have a quick grab of the new kernel for Debian (or any distro that loads uImage from a file), I put my compilation of kernel and modules to http://users.tkk.fi/~tajyrink/moko/kernel_20100108_nodebug_nopreempt/ -Timo, wishing everyone a speedier new year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Alternatives to FR
2010/1/4 William Kenworthy bi...@iinet.net.au: Nokia n900 - probably the best choice at this time. Probably, but to be more precise not yet instead of at this time. It's the only one that seems to have realistic possibility of some day having a free distribution running with all features enabled. But it's not today, and it remains to be seen how active the community around it is. I'm personally thinking that in 1-2 years I could have a pure Debian (maybe custom kernel) running on N900, with everything except probably 3D working. That assumes some people will reverse-engineer the battery loading etc. whatever is needed. But until then there is simply no choice besides Neo FreeRunner, unless something new appears or community around Palm evolves to reach the level of free distribution hackers around Maemo and the modem stuff is reverse-engineered. And even with those, I would have to give up free hardware :S I'd really hope for FreeRunner with 3G and Glamo ripped off, possibly newer CPU some day. For example some company joining gta02-core effort to semi-productize something new... -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Alternatives to FR
2010/1/9 Warren Baird wjba...@alumni.uwaterloo.ca: having a free distribution running with all features enabled. But it's Depends a bit on how you define 'free'... I interact with a phone mostly as a user, and possibly as a app developer - so for me if I can run free software on it, and I can develop free software for it using free tools, it's 'free enough'... I understand. I meant free distribution as a whole, most preferably Debian without any binary blobs. But, as you define, N900 is definitely the way to go, not a bad choice by any means and allows to continue working on the free software ecosystem... and there is even the possibility of running truly free distributions some day on it. It might easily take the lifecycle of N900 anyway before something like FreeRunner again appears. I'm also recommending N900 to any normal person as well. I've been using my FR for 1.5 years, as my primary phone for a lot of that time(on QtEI and the more recently shr-u), and I must admit I'm getting more and more frustrated with it - between the regular crashes and hangs, the incredibly slow performance (so slow that I still occasionally miss a call because I can't unlock the phone in time to answer it), the horrible GPRS performance, and the various idiosyncracies (like the recent 'feature' to progressively dim the screen while I'm trying to use it, inability to connect to wifi much of the time, etc.)... There have been improvements, but it's been very slow, and IMO we're still a *long* way from having a phone with even a half-decent user experience... and there is nothing we can do can fix issues like the poor glamo bandwidth, and the crappy GPRS performance. Well first the glamo bandwidth I think just doubled some time ago in andy-tracking thanks to Thomas White ;) Slow still, and in practice the benefit is not double, but still nice. Together with the another 30-50% speedup all in all regarding these disabling of debug features in kernel, I really feel FreeRunner is a lot more usable performance-wise now than it was ca. 2 months ago. What's incredible of course that it took so long time to notice those two things. This is truly a project of obstacles... But the GPRS is crappy. It works fine (=slow) if I use it on Neo, or if I browse via Bluetooth from computer with images disabled in browser, but otherwise it's easy to hang it with multiple connections. Some people rumor the newest muxers are able to do something about it, but I'm not sure if they have stress-tested it or only used it on FreeRunner itself. And anyway - 3G would be nice of course. But I'd take reliable GPRS gladly as well. When I'm out of the house and need to look something up on the web, I borrow my wife's Iphone - I can look up what I need before the FR's browser finishes launching, let alone loading the google homepage... I'm using woosh quite successfully for quick web browsing nowadays. And I just checked that with the new debug-disabled-kernel (see another thread) Midori isn't too bad either starting up. Of course it's not iphone or other smartphone-like, but usable. Unfortunately, I've been actively looking for a device lately to replace my FR - I'm just too fed up with it. Even though I'm defending FreeRunner, I completely understand you! I hate these problems myself as well, even though it's also rewarding to have many of those actually fixed in the long run. Coupled with the fact that I'm not willing to go for a less free phone (at least software-wise) yet, I'm staying with FreeRunner. But it is _very_ easy to understand that people are fed up, even despite the whatever slow progress has been made. And to be blunt, I don't give a damn if the battery loading software isn't open... I could also live with otherwise free Debian if the battery loading software isn't eg. incompatible with some libraries or something, but completely self-sustaining. But I think it will be possible to replace it with a free software alternative, according to some estimates. Good tinkering with N900! -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Quick e-mail poll: Still using your Freerunner?
2009/12/29 Risto H. Kurppa ri...@kurppa.fi: Do you use FR as your daily/primary phone? Yes. Do you use FR as your primary PDA? Yes. What distribution you run most of the time? Debian. Quite happy nowadays to about everything except lack of 3G data and well, also the GPRS hickups that need some care not to bump into when using Neo's connection from a laptop. Replaced midori with woosh which starts up very fast (compared to midori). It would need packaging, though... One more thing is that some day I should try my luck with navit + speech again. I'm quite fine with TangoGPS for my needs, but navit would make it a real navigator. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FOSDEM 2010: Devroom for openmoko declined
2009/12/2 PieterC freep...@gmail.com: I do not think we should shake our heads (please don't ;-) ). We should team up with the mobile and embedded guys and do our thing. Definitely! I'm not sure about the deadlines, but the sooner the better. I'm not sure if I should again cover the kernel mode-setting and tell people what Thomas (and possibly others...) have come up with by that time. I like the time amount in a lightning talk myself, but do note that if you plan to do a lighting talk, deadline for those requests are 2009-12-20. I guess there might be some more time for deadlines for a session in a track, unless the track fills up of course. If anyone from the gta02-core team could give a presentation, that would be IMHO fabulous. Just for example. See you at FOSDEM! Carry your Neo on your neck so it's easier to spot you ;) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/9/6 Timo Jyrinki timo.jyri...@gmail.com: http://wiki.debian.org/DebianOnFreeRunner#CurrentStatusofInstallation For those of you (like me) who don't read help texts, I added the pretty useful information about needing to install perl on the host system before running the install script :) Also linked to the latest success report of installing Debian, requiring 1 workaround to finish. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/9/6 Nikita V. Youshchenko yo...@debian.org: Doing debian install with (c)debootstrap, as current install.sh does and as debian installer does, although being a standard way, is somewhat questionable on slow devices such as freerunner. This is plainly slow, compared to reflashing or archive unpacking. Also it is vulnerable to temporary archive breakages, as the current story with dpkg 1.15.4 shows. There is truth to that, but I just personally prefer real installation to .tar.gz:s. Of course, with a grain of trustworthiness of having the .tar.gz:s hosted under Debian it would be better than downloading from random places around the web. Remenber, zhone is not intended to be end-user phone app. We should package paroli, and/or litephone, and/or shr phone tools. However, zhone works quite well. But yes paroli for example definitely - and we're on a very good path now. Elementary is now (again) in NEW queue (http://ftp-master.debian.org/new.html), after that there is only python-elementary bindings left to have everything ready for packaging paroli (and intone). For example, it's nice that mokomaze is in debian, but if you install it ... And it was just an example. Another one: after aptitude install mplayer, I Yeah, thanks for bringing me back to Earth :) I just accept almost anything if I just get to use Debian, and I'm happy the ground work starts to be ready, but those two examples are quite good about the real polishing need. TangoGPS of course works quite flawlessly at the moment, but MPlayer with Tremor support and without confusing GUI option would be good, as well as a fixed mokomaze. I believe there are always ways to fix the problems in an acceptable way, but it may indeed need some work. Maybe something can be done in the openmoko-files-config to trigger some stuff in eg. mokomaze. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] help: working fso packages, anbody?
2009/9/7 arne anka openm...@ginguppin.de: could someone please post a working set of fso packages for debian? the last working configuration i had were packages from july, but i did not save them anywhere ... I have the following set working. Ie. everything from Debian main repository, nothing from pkg-fso repository (except for kernel): dpkg -l *fso* | cat ... un fso-config none (no description available) ii fso-config-gta02 20090224-1 configuration files for Openmoko GTA02 Neo F ii fso-frameworkd 0.8.5.1-1 freesmartphone.org Framework Daemon un fso-frameworkd-wireless-glue none (no description available) ii fso-gpsd 0.8-3 gpsd compatibility daemon for the freesmarpt ii fso-gsm0710muxd0.9.3.1-3 GSM 07.10 Multiplexer un fso-sounds none (no description available) ii fso-sounds-none0.8.5.1-1 void ringtones for the freesmartphone.org fr pn fso-sounds-openmoko-nonfreenone (no description available) ii fso-sounds-yue-base20081031-2 Yue base ringtones for the freesmartphone.or ii fso-sounds-yue-full20081031-2 Yue full ringtones for the freesmartphone.or pn fso-utils none (no description available) pn pkg-fso-keyringnone (no description available) Zhone is the just updated one which brings libevas-svn-03-engines-x among else. You may need to remove the old pkg-fso cruft first. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/8/29 Timo Jyrinki timo.jyri...@gmail.com: Unfortunately it was found out installing Debian via the install.sh script is broken until dpkg 1.15.4 lands in unstable. 1.15.4 ARM build has now landed in the Debian archive (at least ftp.debian.org, mirrors soon follow, check ftp://ftp.XX.debian.org/debian/pool/main/d/dpkg/ for armel 1.15.4 deb). Additionally install.sh was earlier updated to offer optional debootsrap-instead-of-cdebootstrap option. For this and future updates on the status of installing Debian, until proper debian-installer support is there, please see the page / section: http://wiki.debian.org/DebianOnFreeRunner#CurrentStatusofInstallation I (at least) will try to keep that up-to-date. Currently the chances of getting Debian installed with install.sh sound quite high, but I haven't tested it myself right now. Please tell your experiences if you try the installation with the tips on that page... meanwhile, I will also update the page myself if I test it with an extra SD card again some time next week. I'm quite glad with the new E17 and Zhone packages in the main Debian archive. The only package you really need from the (still enabled by default) pkg-fso archive is the kernel, so this is very good progress. The kernel is of course a hard thing and involves work from all Openmoko kernel developers who have time to get stuff upstream, but after that it would be not a big way to proper Debian installer support - which eventually even leads to a Debian stable release with official support for FreeRunner. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/8/29 Nikita V. Youshchenko yo...@debian.org:
GPRS worked fine.
Could you please post an explanation on how to test/use gprs on debian?
Maybe see http://wiki.openmoko.org/wiki/GPRS_FSO#Using_scripts ? I
added now a link to that page also from DebianOnFreeRunner.
I'm myself actually using old method from my Om2008.12, since it seems
to work. I launch this from a PyGTK application:
identvar=$(date +%s)
ptsvar=$(dbus-send --system --print-reply --type=method_call
--dest=org.pyneo.muxer /org/pyneo/Muxer
org.freesmartphone.GSM.MUX.AllocChannel string:$identvar | grep string
| awk -F '' '{ print $2 }')
sleep 2
echo $identvar $ptsvar
pppd $ptsvar 115200 call gprs
...and have setup /etc/ppp/gprs-connect-chat + /etc/ppp/peers gprs.
But I guess it's pretty useless if FSO stack takes care of all that
when sending a single dbus message like described on the GPRS_FSO wiki
page.
-Timo
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/8/28 Radek Polak pson...@seznam.cz: Risto H. Kurppa wrote: Tried to install debian today: ... E: Internal error: install Unfortunately it was found out installing Debian via the install.sh script is broken until dpkg 1.15.4 lands in unstable. So, keep eye on http://packages.qa.debian.org/d/dpkg.html Only manual installation using debootstrap is possible meanwhile. Updated http://wiki.debian.org/DebianOnFreeRunner#CurrentStatusofInstallation -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/8/27 Lee Grime lee.gr...@gmail.com: Re-camping. I can only tell it is doing this because I left it near my PC and the speakers were picking it up! Happens about every 5-10mins. I did not have this problem with SHR, it is stable for GSM. SMS has a few quirks, but nothing major. I know there is a hardware fix for this, but why no problems with SHR? Possibly because newest FSO release (5.5?) has not yet come to Debian. Coming soon(ish). Wifi, could not connect to my T-Com (Germany) wireless router (WEP). It was picked up using wifi-radar, but failed to get an IP address. I don't remember if 2.6.28 or 2.6.29 is now the default in Debian. One should generally install the 2.6.29 kernel - but the lingering problem regarding 2.6.29 there is the omission of the patch that makes wifi really work there http://docs.openmoko.org/trac/ticket/2277 . 2.6.28 has other problems, but 2.6.29 with that patch basically rocks for everything. I have a self-compiled 2.6.29 + patch in use. Midori and tangoGPS do not pick anything up from the internet via USB connection to PC. I can ping google no problem. Midori worked via GPRS. Works fine with my USB, I have the usual NAT forwarding on my laptop. Though nowadays I actually forward the network via Bluetooth to Neo :) (and also the other way around, from Neo to laptop when on road). Not sure how to put it into suspend, seems a bit flakey! Press the power button? Also, in the wiki guide there are instructions about suspend settings in general. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Debian first experience made a bit easier...
Hi, With the gust of fresh air everywhere, I took the liberty of joining the mess that was combined http://wiki.openmoko.org/wiki/Debian + http://wiki.debian.org/DebianOnFreeRunner , so that in the end the Openmoko wiki page is just a brief showcase about Debian and all information is included in a sensible, structured way on the Debian's wiki. There is still the problem of install.sh having problems, but besides that (waiting for debian-installer support) I believe trying Debian out is much more easier now if you just tumble upon the wiki and start exploring, instead of already knowing someone who uses Debian. Using Debian on the FreeRunner is quite a great joy for anyone using Debian/Ubuntu/etc. on the desktop. Feel free to continue the work of cleaning up wiki(s). I was inspired by Risto's call for wiki cleaning, and I had already for some time thought the Debian side of instructions is in a terrible state. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Debian first experience made a bit easier...
2009/8/27 Risto H. Kurppa ri...@kurppa.fi: showcase (add your OpenOffice screenshot there!) Done :) 2009/8/27 Edder ed...@tkwsping.nl: I had been looking at installing debian a couple of days ago and it seems that this is a definite improvement! The only suggestion I have is to add some more examples for the install.sh script. Thanks. I added some examples, though I haven't myself installed Debian for a while since everything works and I haven't had a working spare SD card to try out. mount /dev/your-partition /mnt/debian ./install.sh debian apt fso configuration tasks kernel cleanup unmount This should theoretically be correct, though the possible environment variables matching the previously done partition setup would not hurt. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel Mode-Setting (KMS) on Neo FreeRunner + Debian
2009/8/19 Martin Jansa martin.ja...@gmail.com: I'm using this driver for some time and it behaves realy good. I didn't even noticed any garbled text or artifacts, which is great for this state of development :). You are probably talking about the non-KMS, normal xf86-video-glamo? It's been working ca. since February (bugs fixed since). But this new thing is a huge renewal of the whole gfx architecture, including new branches of kernel, libdrm and xf86-video-glamo. Read the blog post :) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel Mode-Setting (KMS) on Neo FreeRunner + Debian
2009/8/19, Martin Jansa martin.ja...@gmail.com: I'm using this driver for some time and it behaves realy good. I didn't even noticed any garbled text or artifacts, which is great for this state of development :). You are probably talking about the non-KMS, normal xf86-video-glamo? No I'm really talking about KMS :). Today I've seen first garbled text in midori, but the rest looks the same as it looked with normal xf86-video-glamo or Xglamo before.. Wow, ok :) Some time sounded so long as it's not that many days away when the X started working for the first time :) Good for you, I'm mostly still seeing garbage in all but Zhone, though I haven't tried many applications besides TangoGPS, lxterminal and some more GTK programs. Even the fbpanel with the start menu, battery information and Bluetooth icon is garbled. As for those asking for instructions: I built the kernel branch [1] with the http://wiki.openmoko.org/wiki/Toolchain instructions. Transferred the uImage.bin.xxx and modules to device, symlinked /boot/uImage.bin to this uImage.bin.xxx and unpacked the modules package. Then I built libdrm branch [2] and xf86-video-glamo [3] on the phone itself. Using Debian from SD, so the only reason I didn't build also kernel on the device was simply to save time. When trying to build the xf86-video-glamo, use autoreconf -vi first. I installed libdrm simply by make install (under /usr/local/lib) and xf86-video-glamo by copying the library from .src/libs to /usr/lib/xorg/modules/drivers/. [1] http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/drm-tracking [2] http://git.bitwiz.org.uk/?p=libdrm.git;a=shortlog;h=refs/heads/glamo [3] http://git.openmoko.org/?p=xf86-video-glamo.git;a=shortlog;h=refs/heads/kms Mesa [4] can be AFAIK ignored at this point (?), though you get even neater X.org log lines by using it :) Since it hasn't been updated for some months, I took a ready made binary from http://www.bitwiz.org.uk/openmoko/dri-binaries/ and unpacked it manually into my Debian. [4] http://git.bitwiz.org.uk/?p=mesa.git;a=shortlog;h=refs/heads/glamo -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel Mode-Setting (KMS) on Neo FreeRunner + Debian
2009/8/20, Timo Jyrinki timo.jyri...@gmail.com: As for those asking for instructions: I built the kernel branch [1] with the http://wiki.openmoko.org/wiki/Toolchain instructions. Forgot to note: config is arch/arm/configs/gta02_drm_defconfig. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel Mode-Setting (KMS) on Neo FreeRunner + Debian
2009/8/18 Chris Samuel ch...@csamuel.org: I haven't seen anyone else post about this yet, but this looks really neat! (Found via Planet Ubuntu) http://losca.blogspot.com/2009/08/kernel-mode-setting-kms-on-neo.html Yes, I thought to give some sneak peak to it as I was so happy to get Thomas' work working that far. Now FreeRunner is usable as a phone (=Zhone) when using KMS-enabled glamo driver. 2009/8/18 Dan Staley daniel.l.sta...@gmail.com: Also +1 on the video. I added now a video to the blog post. Hope you enjoy it! It's somewhat cutted at two points, let the public think we can actually boot Debian with all the software in 1:40 ;) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANN] Freerunner GTA02A7 on regular sales
2009/8/12 Dr. H. Nikolaus Schaller h...@computer.org: we are happy to announce that we and our partner TRISOFT now have the GTA02A7 models on regular sale and can ship from stock. Great! If I manage to break my FreeRunner at any point of time (I had a good attempt with some snow earlier this year), I'm happy to know I can select FreeRunner also as my next phone ;) -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Rustling noise on phonecalls
2009/7/31 Michael Zanetti michael_zane...@gmx.net: I have been able to solve it now and have put all the information from this thread into the wiki. https://wiki.openmoko.org/wiki/Alsa_state_a7 Do note that page linked to the wrong statefile, which was earlier erroneously called the one statefile. The actual one statefile is in the same ticket with .new prefix. The erroneous state file had Mic2 set to 0, which is clearly wrong. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
2009/7/18 Christian Adams mor...@morlac.de: Indeed. I've run the latest GIT from http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary maybe a dumb question .. but could you give me some hints howto actually build it? Not a dumb question. I'm using Debian, so I have all the compilation software directly on the phone, and also git. So, something like: apt-get install git-core build-essential gcc xserver-xorg-dev git clone git://git.openmoko.org/git/xf86-video-glamo cd xf86-video-glamo At this point you should run autotools, and I don't directly remember what I ran. Probably something like: aclocal libtoolize --automake automake --add-missing autoconf ...but I still had some problem so I simply ran autoreconf -vi also. then: ./configure make I installed the driver manually with: cp -a src/.libs/glamo_drv.so /usr/lib/xorg/modules/drivers/glamo_drv.so Hope this helps. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian 2.6.28|29 xserver-xorg-video-glamo] wsod when xserver stops
2009/7/16 Sebastian Krzyszkowiak seba.d...@gmail.com: since i installed 'xserver-xorg-video-glamo' instead 'xserver- xglamo', every 2nd (or so) time i try to shutdown/reboot i get a WSOD when x11 stops. has someone an idea what i should do? Wait for upgrade. It's already fixed AFAIK. Indeed. I've run the latest GIT from http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary for over a week now and haven't experienced the problem (nor the filling of Xorg.0.log bug) anymore. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Anti-Whining: Happy Moko Moments
Gonna first answer this one small ogg bit. 2009/7/17 The Digital Pioneer digitalpion...@gmail.com: That said, if anyone knows a way to make it not cut and skip when playing OGG with mplayer niced at -19, I'd love to hear it. It's not too bad right now, but there's usually at least one cut per minute. :( My mplayer (on Debian) didn't skip when left alone when I was on a trip, but it usually started to skip if I had frameworkd + wicd + zhone + tangogps all running in the background. I mostly just needed frameworkd and tangogps, though. The key to success is probably compiling some program (eg. mplayer) with the integer-only tremor ogg decoding support. I'm going to have a look at that soon now that I noticed this severe enough multi-tasking problem with ogg playing. Without it the CPU load is 60-70% which is pretty high for a 400MHz ARM CPU. But right. I think I mostly covered my anti-whining already in the whining thread, even though this thread would have been a much better place for it. In addition to the Cool Stuff, I'm also one of the people who also use it as the only daily phone, and mostly since August 2008. Of course buzz and echo fixes made GSM life much easier settings wise. I love RSA authentication to home 24h NAS box (running ARM port of Debian as well, like the FreeRunner). Having instant messengers and IRC there gives a possibility to check those from FreeRunner at will. And I mentioned already in that other post that copying photos from camera to Neo via USB host mode is a neat feature and then Neo can be also used to back them further up to eg. the home server from anywhere around the world (...with WLAN access points). Om2009 as a dual-boot backup OS is useful sometimes as well, though less so now that the occasional xf86-video-glamo WSOD problem on shutdown got fixed (I then booted to Om2009 to run fsck on the SD card...). -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: why openmoko is so slow? Is it a joke? (latest whining thread)
Because July is so boring month, joining the latest complains thread. Btw, I just came back from a week's trip where FreeRunner was absolutely a gem to have. GPS was trustworthy, I was able to backup photos from camera to Neo via USB host mode (and onwards to USB stick or over WLAN/SSH to home computer 1000km away). While using GPS I played back music from Neo via rented car's AUX input, and charged Neo as needed with a car USB charger. Oh, and used Neo as a phone as well (the obligatory postscriptum). 2009/7/14 Joerg Lippmann jl_li...@donalbain.de: When will that be? When the device is completely obsolete? When it's ready, and capable developers willing to spend time found. Anyone with time and skills can try the latest dev branches of DRI-aware driver, kernel drm driver etc. and start testing or developing. As for obsolete, I don't currently see any competing product on the market, and I expect it will be at least two years we have something comparable from some other vendor. And even still, I expect to be using FreeRunner if it works for me as well as it does now. as a proper phone (speaker still WAY to low, too unstable, too slow, too battery-hungry) nor as a PDA (no usable software available). Cannot reproduce those, but sorry for you. It all depends on software, which as it happens is completely replaceable. without good software. I cannot help it. I haven't found a single distro that works well out of the box. The best ones so far were QTopia/QTe and Android. I use Debian myself, but I find the latest Om2009 snapshot I use as a backup dual-boot option to function pretty cool for GSM, GPS, GPRS and WLAN usage although at least I still needed to tweak two settings (speaker volume and mono playback volume) in gsmhandset.state. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Hello world. Is the Neo Freerunner dead?
2009/7/7 Helge Hafting helge.haft...@hist.no: If alive, can the Freerunner be used reliably for business on a day to day basis? Under what system? I use it with Debian on a day to day basis. Requires more work than eg. SHR or Om2009 distros, but then you get... Debian. I do have Om2009 as a dual-boot option, though, for backup (and since I don't have anything better to do with the flash storage). You may also need a powered hub - I believe the phone won't provide power to your keyboard. It does. I've used both mouse and keyboard with a simple mini USB male - USB female adapter. -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
