Re: QtMoko v22
On Friday 14 May 2010 00:33:48 Gand' wrote: Do you mean it's significantly more unstable than the v20 ? 'Cause i've been using it for a while, and there was nothing critical in it ... It should be better then v20, but both have the problem that it eats battery in suspend - much more then stable ones. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v22
Oh ok, so i'll give it a try :) Improved reactivity worth the shorter battery :D -- Gand' On Fri, May 14, 2010 at 10:24 AM, Radek Polak pson...@seznam.cz wrote: On Friday 14 May 2010 00:33:48 Gand' wrote: Do you mean it's significantly more unstable than the v20 ? 'Cause i've been using it for a while, and there was nothing critical in it ... It should be better then v20, but both have the problem that it eats battery in suspend - much more then stable ones. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v22
On Friday 14 May 2010 11:52:09 Gand' wrote: Oh ok, so i'll give it a try :) Improved reactivity worth the shorter battery :D I think v22 is most reactive - after debug stuff was removed i subjectively think it's the fastest what we had. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The Phoenux is coming: Openmoko Beagle
Dr. H. Nikolaus Schaller wrote: We can soon provide a printed circuit board (Openmoko Beagle) that can carry a Freerunner display module (incl. touch screen) and is connected to a Beagleboard. It fits into a (slightly cut) Freerunner case (although you can do everything without destroying a Freerunner; only the buttons are a little more difficult to use). Nice. Combining the FR display with a faster processor is interesting. It'd be even better if it either fit in the FR case, or some alternative case can be ordered instead. Expanding the FR case by making it thicker is also an option. Is the touchscreen the only FR component that can be reused? The gps unit is rather good - could it be connected to the new board with only simple soldering? Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Java ME for QtMoko
Hi, 2010/5/14 Georgy wrote: Hello, I try it out and it's work with the demo apps. I try it out with remoco (http://code.google.com/p/remuco/, but crashed with message : javax/bluetooth.BluetoothStateException. Any hint, or apps can't work with PhonetiQ ? Anyway, thanks for your work Georgy It seems that Bluetooth classes within the Virtual Machine is not ported to Qtopia. So, applications that uses Bluetooth can't be run currently. Anton -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/Java-ME-for-QtMoko-tp5042260p5051182.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02-core] Openmoko Beagle Hybrid
Dr. H. Nikolaus Schaller wrote: There is now a new Wiki page for the project: http://wiki.openmoko.org/wiki/Openmoko_Beagle_Hybrid Kewl. But where's the duct tape ? :-) I have received some questions why we did not put all this into a nice design. The main reason is that we can't redesign the Beagleboard (it has fixed dimensions) and we can't afford to build plastic injection moulds (if someone has an idea how to reduce cost this is very welcome). Low-volume injection molding should be quite affordable if you provide the cast (aluminium) or at least a machine-ready design. Of course, if you have to pay for the entire design work too, things will get expensive. However, you may also want to consider making the parts directly, without going via a cast. This is much more expensive for larger quantities, but if you only need a handful of cases anyway, it should be more efficient. The issue then becomes access to equipment and experience. I think making a simple case should be little more than a weekend project for someone who's set up to do such things. The challenge seems to be to find such a person, or - if you're looking for an exciting new hobby - to become one :-) - Werner ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Running SHR in Qemu
saravanan T saravana...@gmail.com writes: How can I run SHR in the qemu. What's your objective, man? Why run SHR in emulator when you can run it natively on any device (including your PC)? What are you trying to do and why? -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [gta02-core] Openmoko Beagle Hybrid
Am 14.05.2010 um 16:36 schrieb Werner Almesberger: Dr. H. Nikolaus Schaller wrote: There is now a new Wiki page for the project: http://wiki.openmoko.org/wiki/Openmoko_Beagle_Hybrid Kewl. But where's the duct tape ? :-) Between PCB and LCM :-) I have received some questions why we did not put all this into a nice design. The main reason is that we can't redesign the Beagleboard (it has fixed dimensions) and we can't afford to build plastic injection moulds (if someone has an idea how to reduce cost this is very welcome). Low-volume injection molding should be quite affordable if you provide the cast (aluminium) or at least a machine-ready design. Of course, if you have to pay for the entire design work too, things will get expensive. We have done some research and asked for quotation and the result is that if you want to get below 50 USD per unit (which is still a lot of money) you need a volume of 200 units. If you make any small mistake, you have to repeat the process and cost will increase by factor 2... So it is not good for learning and protoyping. However, you may also want to consider making the parts directly, without going via a cast. This is much more expensive for larger quantities, but if you only need a handful of cases anyway, it should be more efficient. The alternative would be 3D-Printing. There are now some quite good machines that can produce in ABS. Unfortunately these machines are rather expensive and operators want to have fast amortization. This raises cost of small quantities of cases like the freerunner well beyond 100 USD. So our observation is that there is no method which allows to produce 1-100 units for experimenting and testing - and still meets the expectations in quality and cost. But we may have missed something. When I walked through the Golden Mall during CeBIT this year, I wondered how approx. 500 small asian booths could display approx. 50 different products each (headsets, mice, keyboards, batteries, plugs, covers, fake phones, real phones, etc...). Each one must have its own plastics. So I would estimate several million USD in moulds have been on display :) The issue then becomes access to equipment and experience. I think making a simple case should be little more than a weekend project for someone who's set up to do such things. The challenge seems to be to find such a person, or - if you're looking for an exciting new hobby - to become one :-) A third alternative could be to experiment with Makerbot / Cupcake. Anyone tried to print a Freerunner case from the open 3D data? BR, Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The Phoenux is coming: Openmoko Beagle
Am 14.05.2010 um 14:19 schrieb Helge Hafting: Dr. H. Nikolaus Schaller wrote: We can soon provide a printed circuit board (Openmoko Beagle) that can carry a Freerunner display module (incl. touch screen) and is connected to a Beagleboard. It fits into a (slightly cut) Freerunner case (although you can do everything without destroying a Freerunner; only the buttons are a little more difficult to use). Nice. Combining the FR display with a faster processor is interesting. It'd be even better if it either fit in the FR case, or some Unfortunately the Beagle Board is too large. We have evaluated if wen can put an OMAP on a cheap board - but the OMAP needs the latest micro- via technology. alternative case can be ordered instead. Expanding the FR case by making it thicker is also an option. The general problem is making plastics. This is the most expensive investment if you want high quality (as used to from the Freerunner). But we will look into that and as soon as we have a solution... Is the touchscreen the only FR component that can be reused? Well ,we also reuse the earpiece and speaker. The gps unit is rather good - could it be connected to the new board with only simple soldering? Unfortunately no. The GPS system consists of ca. 50 components in addition to the pure chip. But you will see that the board has an area for a Wi2Wi GPS module (W2SG0004) with less external components - but we have not yet tested that. So it may be totally inoperable. Nikolaus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Browser Fennec for SHR?
Has somebody thought about getting Browser Fennec to SHR?: support for HTML5: http://www.mozilla.com/en-US/mobile/ 22 December 2009 Firefox for mobile 'days away' from launch: http://news.bbc.co.uk/2/hi/technology/8425906.stm Glenn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] Browser Fennec for SHR?
Am Freitag, 14. Mai 2010 20:15:05 schrieb Tom Hacohen: On Fri, May 14, 2010 at 8:04 PM, Glenn glenn.mh...@gmail.com wrote: Has somebody thought about getting Browser Fennec to SHR?: We had it in the past, it just sucks though. and even more important... it does not build for our arm architecture :/ -- Klaus 'mrmoku' Kurzmann ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[ANN][SHR][Debian] New Emacs interface for FSO
Hi, http://wiki.github.com/paulfertser/fso-el/ M-x fso I'm pleased to announce here my little pet project, something that is my only phone UI for more than two weeks already and is almost what i dreamed of when i was ordering a FreeRunner: it's a console-compatible, flexible and easily extensible, keyboard (and mouse) friendly Emacs module that enables me to use my cellphone both locally and remotely via ssh with ease. For those who haven't tried to use Emacs on FR yet it might seem like a strange idea: who could have guessed a virtual keyboard is good enough for emacsing? Well, i've tried that and in fact it works decently. I used Emacs on device for IRCing and IMing, for occassional shell commands, for reading manuals and even writing some code. It works and it rocks, at least i couldn't find anything that felt more comfortable ;) Furthermore, emacs allows you to have a consistent experience: you come home, plug your FR to USB, ssh in, do ``emacsclient -c'' (which is another great feature of emacs 23: multitty) and here you go, having exactly the same environment but with a larger screen and a real keyboard. Emacs as a programming environment is also nice and fun, no wonder there're so many extension modules for it written over the years. Though elisp might feel constrained and ancient to a modern programmer, it's still quite enjoyable. So, enough of Emacs praising, now back to the subject. :) It's already useable, among the basic functionality only contacts editing is missing. Please do not be harsh about the code, as this module is my first elisp (and first FP (though Haskell adpets will disagree elisp is FP ;) ) experience as well). Special thanks go to John Sullivan who has written the first emacs interface for FSO, Michael 'Mickey' Lauer, the main FSO framework architect and Joerg Reisenweber, the hardware wizard, without his buzzfix i wouldn't be able to use the device at all. Of course, i'm open for suggestions, bug-reports, feature-requests, patches etc., feel free to contact me via e-mail or irc at #openmoko-cdevel. Here goes the copy of the project's main page for your convenience: This project is an attempt to create an Emacs interface for the most typical GSM telephony-related usecases: calling, text messages, contacts management and everything that makes smartphone usage more productive. The objectives: • make the UI usable directly on the device with touchscreen • make the UI usable via ssh • integrate well with other Emacs applications (please drop me a line with explanations what exactly do you want from BBDB - opimd integration, i also need feedback about Linphone integration: do you need it, whether the linphone mode works for you at all and what modifications are required) • provide user with reasonable customisation options Requirements: • FreeSmartphone.org middleware running on host (currently tested only with fsogsmd, framework version cfc0a5c3 Apr 21, cornucopia version c742460d Apr 21, please take into account i’m following FSO HEAD closely so you can expect to find a compatible version in SHR unstable, less so in SHR testing or Debian) • Emacs 23 (with dbus support) (available both from SHR feeds and Debian repositories) Download options: • git clone git://github.com/paulfertser/fso-el.git or • http://github.com/paulfertser/fso-el/raw/HEAD/fso.el Hints: • configuration options can be edited with M-x customize-mode RET • xterm-mouse-mode enables mouse clicks for the text-mode frames • you can open another frame (either text-mode or X11) with emacsclient -c thanks to Emacs23’s multitty support • you can have FSO running on device and fso.el running in host’s Emacs with dbus-daemon-proxy[1] (thanks ZaPPaS for testing). Unfortunately, it’s not currently possible for one emacs process to use both local and remote dbus message buses due to bindings’ limitation. General Emacs on smartphone hints: • Emacs takes very long to start if you have no network connectivity and non-empty /etc/resolv.conf • ido-mode saves quite some typing when switching buffers and opening files • in customisation options for erc disable the fill module, it’ll save you some precious screen estate, timestamps should either be disabled or Erc Insert Timestamp Function set to Left (alternatively, activate Hide Timestamps and Echo Timestamps and you’ll be able to see the timestamp of any message by moving point to it) • BitlBee is a nice IRC-IM (Jabber/XMPP and others supported by libpurple) free gateway software and service, you might like to use it for your IM’ing needs. Please send your feedback to: Smartphones-userland mailing list with Cc to “Paul Fertser fercer...@gmail.com” Enjoy and happy hacking! :) [1] http://blog.shr-project.org/2010/05/howto-develop-and-debug-the-shr-phone-stack-on-your-desktop.html -- Be free, use free
[qt-moko] QX config being ignored
Hey all,
First, thanks to Radek and other qt-moko contributors. V22 realy gave us a
quite stable system for daily usage.
Now the phone is working well I'm trying to have some fun with X apps. The
first issue I noted is that a few settings in /opt/qtmoko/etc/qx/profiles.conf
seem to be broken. For now I can list the following:
* kbd=false launches an empty keyboard area
* rotate=true doesn't work
My system has the v22 /opt tree. I've tried above with both fbdev and glamo
setup in xorg.conf.
neo:~# uname -a
Linux neo 2.6.29-rc3-v21 #10 Tue Apr 6 22:54:31 CEST 2010 armv4tl GNU/Linux
neo:~# dpkg -l xserver-xorg* |grep ii
ii xserver-xorg1:7.5+5 the X.Org X
server
ii xserver-xorg-core 2:1.7.6.901-3Xorg X server
- core server
ii xserver-xorg-input-all 1:7.5+5 the X.Org X
server -- input driver metapacka
ii xserver-xorg-input-evdev1:2.3.2-4X.Org X server
-- evdev input driver
ii xserver-xorg-input-synaptics1.2.2-2 Synaptics
TouchPad driver for X.Org server
ii xserver-xorg-input-wacom0.10.5+20100416-1X.Org X server
-- Wacom input driver
ii xserver-xorg-video-fbdev1:0.4.2-2X.Org X server
-- fbdev display driver
ii xserver-xorg-video-glamo0.0.0+20091108.git9918e082-2 X.Org X server
-- SMedia Glamo display drive
Btw, it would be great if I could bring a chroot from my full Debian system in
/media/card to QX. Can you think an elegant way to perform this?
Best regards,
--
.''`. Tiago Bortoletto Vaz GPG : 1024D/A504FECA
: :' : http://tiagovaz.org XMPP : tiago at jabber.org
`. `' tiago at {tiagovaz,debian}.org IRC : tiago at OFTC
`-Debian GNU/Linux - The Universal OS http://www.debian.org
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v22
Hi, The new version appears to work fine here (just a quick test so far). BTW, my Ubuntu laptop (Xubuntu 9.10) exhibits a strange symptom: each time I connect my FR, the network interface name increases: eg. it started out with 'eth9' (what happened with usb0?), the next time I connected the FR the interface was 'eth10', then 'eth11', 'eth12' and so on. What gives? -- Regards, Torfinn Ingolfsen ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ANNOUNCE] qi-bootmenu-0.1 for GTA02
Hello, I finally found time to test this. Without a SD card in my FR, I only get the power off button. Cool! I hav a SD card partitioned like this: /dev/mmcblk0p1 - vfat, for storage /dev/mmcblk0p2 - ext3, QtMoko V22 /dev/mmcblk0p3 - ext3, QtMoko V23 /dev/mmcblk0p4 - swap with the SD card inserted, I see no bootmenu - it just boots /dev/mmcblk0p2 every time. What's wrong? On Sat, Feb 13, 2010 at 3:25 PM, Marc Andre Tanner openm...@brain-dump.orgwrote: Hi, I finally found the time to package up my current state of things which works ok here at least for GTA02. Kernel + Qi can be downloaded from: http://www.brain-dump.org/projects/qi-bootmenu/ It would be nice if the various distros out there could place their kernels in /boot/uImage-$MACHINE.bin where $MACHINE is either GTA01 or GTA02. This makes sure that they will be detected by qi-bootmenu. You can optionally also place a logo in /boot/bootlogo.png which will be displayed along the partition name. As for GTA01 support I'm playing around with a 2.6.32 based kernel but with the initramfs embedded the result is to big ~2.4M. So we need to shrink it by 400K to fit into the kernel partition. Not yet sure how this should be done without either losing features (usb network access for example) or repartitioning NAND (dropping the uboot splash screen partition) but I personally don't want to take the latter route, so we will see... Thanks, Marc -- Marc Andre Tanner http://www.brain-dump.org/ GPG key: CF7D56C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- mvh Torfinn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
using multiple window systems - selecting at boot
i'm investigating changing to debian as the os for my fr. it appears i can use either qtmoko, or the shr suite of apps on top of this. if i install both, how would i go about choosing which environment (Qt/X) boots at startup? on my desktop i'd probably see if grub could do it, but as there is no grub i'm a bit stuck here. any suggestions? cheers ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
