Re: N810 available in nokia shop Germany - but discount code fails
On Mon, 2007-12-10 at 18:22 +0100, Detlef Schmicker wrote: I read somewere in the list that the codes should work at 15. Dec. It's the 15th today. The code is still not working :-(. Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: H/W 3D on the N800
On Tue, 2007-04-10 at 10:56 +0300, Amit Kucheria wrote: On Sat, 2007-04-07 at 07:49 +0200, ext Daniel Wagner wrote: Seems as if H/W 3D is not open source compatible. Probably since they licensed the 3D core from PowerVR... That is one reason indeed. Could you please provide more detailed info? Like which other reasons are there and how possible solutions could look like? I.e. is it possible at all to make H/W 3D open source compatible and how? Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Maemo Language bindings and priorities
On Tue, 2007-04-10 at 16:20 +0300, [EMAIL PROTECTED] wrote: Hi Jukka-Pekka, I'm collecting developer feedback regarding language binding needs on maemo. Hildon and other APIs need bindings in order to have native support in languages other than C. See my comments inline. This topic partly interfers with the Java language bindings proposal for Google SoC by Clemens Eisserer for which I applied as mentor. Currently there exists unofficial bindings for C++, for example, and bindings for Python. So the question is what bindings do you need for your development, Bindings for hildon (GUI) and d-bus (communication with system services) + other Gnome related APIs would be needed for decent java support in maemo. for what language, Java. and why (if not obvious)? A tight integration (i.e. UI is not distinguishable from the UI of a C +hildon application while still as powerfull) of Java into maemo is still missing. General support for the Java language is already in place (as reported previously on this list). Currently Java has different APIs for UI programming. None of them directly fits with hildon. Among the most widely used are: 1. Swing (Java's own UI toolkit) [1] 2. SWT (based on GTK) [2] 3. AWT (Java's old own UI toolkit) [3] 4. java-gnome (bindings for GTK) [4] IMO one of these should serve as a starting point for any java-hildon binding activity. Greets, Jonek. [1] http://java.sun.com/javase/6/docs/api/index.html?javax/swing/package-summary.html [2] http://www.eclipse.org/swt/ [3] http://java.sun.com/javase/6/docs/api/index.html?java/awt/package-summary.html [4] http://java-gnome.sourceforge.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: SoC: 5 preliminary slots
On Sat, 2007-04-07 at 09:40 +0300, [EMAIL PROTECTED] wrote: Google has allocated 5 preliminary slots for the maemo project. We might still end up getting less than these, but definitely not more. As the light blue line in the list of proposals seems to have climbed up one further position I assume that Google has decided to give maemo only four instead of five slots. Correct? (If not, I hereby please the remaining mentors to vote for the Java proposal. It has got only votes from 5 mentors while other projects got votes from up to 9 mentors.) Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: SoC update
On Mon, 2007-04-02 at 11:49 +0300, Quim Gil wrote: [...] - I'm surprised about the small percentage of mentor votes we have for each project, even in the best ranked. I mean, all in all most of the mentors have ranked one or more projects, but only a few have gone through, say, more than 4-5 [...] I catched up on this now. - It has been (unofficially?) said that after tomorrow Google is going to assign slots to the projects. I believe we will have more chances if we have more mentors in place and a bigger collection of opinions ranking the best candidates. I would really like to see more comments on the Java proposal. I wounder why there a non except Quim Gil's and my own up to now. Please other mentors, tell me what you are missing in the proposal or what are your oppinions. I can't imagine nobody of you has an opinion on Java for maemo. Give the student and me a chance to probably clarify things for you. Remember you have the possibility to vote neutral (N/A). Greets, Johannes. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Java on Maemo and OpenMoko
Hi list, there are some news regarding Java for Maemo and OpenMoko. 1. Clemens Eisserer has submitted a worthy proposal for Google SoC entiteled Improve the phoneME JVM, to integrate well with Maemo and GPE enviroments. Any comments are also highly appreciated. If you are a SoC mentor, please support this proposal by either scoring it higher. 2. OpenMoko has started [1] a similar project [2] to bring 'Java phoneME advanced' to the FIC Neo1973 phone. Scott Oberg is addressing the GUI parts of Clemens' proposal for OpenMoko and has contacted [3] SUN for advice and me [4] asking if anybody is addressing the problem on the Maemo side. I think this is an opportunity to work together to reach a common goal! 3. Find information about Java for Maemo in the wiki [5]. Greets Jonek. [1] http://lists.openmoko.org/pipermail/openmoko-devel/2007-March/000747.html [2] http://projects.openmoko.org/projects/java-pkg/ [3] http://forums.java.net/jive/message.jspa?messageID=210309#210309 [4] http://tech.groups.yahoo.com/group/java-pkg/message/15 [5] http://maemo.org/maemowiki/JavaLanguage ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [Java] Mentor wanted for Summer of Code 2007 ;)
On Mon, 2007-03-05 at 20:26 +0100, Clemens Eisserer wrote: I wonder wether anybody would be willed to mentor me at Google's Summer of Code 2007. Hi Clemens, I would like to support your effort as a mentor. But currently I don't know what is needed to be accepted as a mentor and what the process to apply as a mentor would be. If anybody on this list is able to clarify the situation, please feel free to do so! Would it make sense to ask on sun's Java phoneME forum for support and possibly another mentor, too? I'm also interested in broader feedback and opinions from the list about Java integration into maemo. It seems at least three possibilities are currently considered by different people. 1. jamvm + classpath 2. cacaovm + classpath + java-gnome (jalimo by Sebastian Mancke) 3. sun's phoneME advanced Greets, Jonek. signature.asc Description: This is a digitally signed message part ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Maemo roadmap, SDK improvements...
On Fri, 2007-03-02 at 09:41 +0200, Quim Gil wrote: Here we go: http://test.maemo.org/community/roadmap.html Nice! I would like to know who the owner or target of a specific entry in the roadmap is. E.g. Nokia employee or garage user + contact info or at least a project website. It would be nice if one could get more specific information on an entry this way. Could this be integrated into the roadmap somehow? Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: Asking for information about programming in JAVA at Nokia device
On Tue, 2007-02-27 at 14:36 +, magda chelly wrote: In fact, I have a problem, it's that the Nokia N800 does not support JAVA and I must program with that language. You know something about that? What must I install to make my program runs on that? Feel free to try SUN's GPL'ed Java PhoneME advanced which comes with a virtual machine and API. It is available for download under [1]. Copy it one the device and unpack it via the command line. Don't expect a full featured Java platform. For current shortcomings have a look into this message [2]. Which virtual machine work on that, or maybe there is somewhere a virtual machine that work on NOKIA 770. The above mentioned virtual machine is known to run on the 770. Feedback on N800 usability is appreciated! I am very interested in your success stories as well as in any problems you may run into! Greets, Jonek. [1] http://i30www.ira.uka.de/p2p/ambicomp/phoneME_Nokia770/ [2] http://www.gossamer-threads.com/lists/maemo/developers/17898#17898 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] developing for 770 with IT2006 on Debian testing with 2.6.18 kernel
On Fri, 2007-01-12 at 22:30 +0100, Patrick Ohly wrote: Duh, replying to myself: I now found the hint about Maemo 2.2 in [1]. So hopefully I'll have a working SDK again soonish... [1] http://www.maemo.org/downloads/maemo_3_compatibility.html Why not put this kind of information on [1]? I think it fits in better there. Btw. [1] seems to be outdated. Yes, i know there will be a relaunch of the maemo.org site ;-). Greets, Jonek. [1] http://maemo.org/platform/docs/roadmap.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Java phoneME advanced for the 770
Hi list, for evaluation purposes I made up a build of Sun's GPL'ed Java phoneME Advanced MR1 release. The build only supports the Foundation Profile so far.That means there currently is no support for any GUI. From some mails on this list and from comments on #maemo I've got the impression that there are experienced people who might be interested in hacking on this topic and could help to bring more Java to the 770. Feel free to try the simple HelloWorld and the test suite on your Nokia 770 with a Sun VM :-) that come with the build. You can get it from [1]. I roughly described the steps I did to get it build and how to install it in [2]. Ongoing discussion about the development of phoneME Advanced happens in their forum/mailinglist [3]. Please join it with questions or suggestions. Happy hacking, Jonek. [1] http://i30www.ira.uka.de/p2p/ambicomp/phoneME_Nokia770 [2] http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatformsNokia770 [3] http://forums.java.net/jive/forum.jspa?forumID=100 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: Java on the 770
On Wed, 2006-11-22 at 15:57 +0100, Clemens Eisserer wrote: Furthermore I guess we would not really need Jazelle to archieve good performance. As far as I know Sun will release its ARM JIT also under GPL which should be enough to build a high-performance CDC JVM for the 770. I'm an enthusiast of the Java language and was excited to read that Sun started the phoneME community project [1] which centers around providing the JavaME (Java Micro Edition) platform as source code compilable for different target platforms (e.g. Linux/ARM). The 'phoneME advanced' [2] subproject seems to be te candidate to be suited for the Nokia 770 as it will provide the CDC [3] architecture. phoneME advanced has only one realease yet (MR1) and starts developing on the next relase (MR2) in the next month [5]. Documentation about how to build the Java runtime environment and other needed parts (APIs from the different profiles) of MR1 can be found under [6]. Maybe the Maemo SDK's ARM target in scratchbox could be used to build 'phoneME Advanced MR1 Software'. Unfortunately it seems to depend on an available Java SE 1.4.2 on the build system to run some of the Java Build Tools (see section 2.4.3 in [7]). It would be nice if anybody could suggest how to proceed. After I downloaded [8] into my scratchbox I was stuck. Greets, Jonek. [1] https://phoneme.dev.java.net/ [2] https://phoneme.dev.java.net/content/phoneme_platforms.html#phonemeadvanced [3] http://java.sun.com/products/cdc/overview.html [4] http://java.sun.com/javame/reference/apis.jsp#cdc [5] https://phoneme.dev.java.net/content/phoneme_advanced_r2.html [6] https://phoneme.dev.java.net/content/phoneme_advanced_guide.html [7] http://java.sun.com/javame/reference/docs/cdc_build_system.pdf [8] http://download.java.net/mobileembedded/phoneme/advanced/phoneme_advanced-mr1-rel-src-b06-10_nov_2006.zip ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VoIP through SIP
On Fri, 2006-10-06 at 15:27 +0200, Fred Lefévère-Laaoide wrote: Frédéric Crozat wrote: Well, I want to use my ISP (Free.fr) SIP platform, which allows me to call anywhere in France and various countries for free, as if I was calling from home. They only support g711 vocodeur ATM (because they are using Cirpack PBX) and their cirpack server is also sending dummy ping packet (see http://lists.digium.com/pipermail/asterisk-dev/2006-May/021033.html for more info on this, it would be nice to integrate a similar fix in Sofia-SIP). Any news on this ? Or a how to get started on adding g711 support? Sofsip-cli is already using G.711 as it's only supported codec. It makes use of gstreamer to setup a pipeline like this: dsppcmsrc - rtppcmupay - rtpbin If you look at the produced RTP packets with e.g. wireshark and decode the UDP packets as RTP traffic you can see they are tagged to carry G.711 PCMU payload. For a list of further codecs use gst-inspect |grep rtp on the device (you will maybe have to install the gstreamer-tools package). Be aware that you would currently have to change the code of sofsip-cli to enable usage of other codecs. Greets, Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: rebooting constantly after upgrading packages
Am Freitag, den 01.09.2006, 15:18 +0300 schrieb Kuosmanen Tuomas (Nokia-M/Helsinki): On Fri, 2006-09-01 at 09:26 +0200, ext Rainer Dorsch wrote: I appreciate that apt-get is there. It allows me to login into the device from my PC and work with the device like I am used to from debian or ubuntu boxes. There is one important thing to remember: Just because it has apt-get, does not mean it *IS Debian*. Assuming it works like debian in every sense will be a bad mistake currently. It contains stuff and tools from debian, but it's not the same thing. Sorry, but it is a bad idea [tm] to deliver a tool thousands of people (users of debian-based distros) are used to work with on a daily basis and then tell them it behaves different here and should NOT AT ALL be used. I wonder what your options are... 1. Change the situation and make apt-get upgrade usable by providing sane stable packages in repository.maemo.org which are always usable on the device too. 2. Provide a different repository which only contains packages meant to be installed on the device. 3. Patch apt-get to refuse to work when the upgrade option is given. There are a number of pros and cons attached to these options and probably there are even more. Jonek [tm] http://www.netzmafia.de/skripten/netze/etherkiller.jpg ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: rebooting constantly after upgrading packages
Am Donnerstag, den 31.08.2006, 16:24 +0300 schrieb Andrey Khurri: I followed the steps suggested above and in some previous threads and set the flag 'no-lifeguard-reset'. After that my device didn't reboot anymore. I completed upgrade with 'dpkg --configure -a' and it seemed to fix the mess with my packages. However, after that I decided to try to clear that flag back hoping that tablet now does not need it. Clearing the flag resulted again in cycle reboot of my system. I was wondering whether this behavior is alright? No, it certainly is not. Also as was mentioned by Johannes Eickhold in http://maemo.org/pipermail/maemo-developers/2006-August/005349.html video and audio players are not able to play files any more after this failure. This is caused by the upgraded gstreamer related packages. Gstreamer is not able to initialize anymore, because some plugins segfault on load. With regards to this problem is flashing device the only way to fix it? You can rollback the files of the affected packages to a previous version. Contact me for some tar balls. Although this method messes up package management system, it made it posible for me to reenable lifeguard-reset and get video and audio working again. Fixed packages in the repo would be another possibility *hint*. Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] SDK vs. device: libSM and libICE
Am Mittwoch, den 30.08.2006, 12:19 +0200 schrieb Christian Henz: On Tuesday 29 August 2006 14:50, you wrote: Cristian, have a look at this http://maemo.org/pipermail/maemo-developers/2006-July/004489.html My point is that the libs are only in the maemo repository. They are not on the device or the catalogue.tableteer.nokia.com repository. I do not want to install them on the device since I don't even need them. They are just linked because they are found on the SDK. And you can not uninstall them in the SDK because xlibs-dev depends on them. This implies some interesting questions which popped up on #maemo yesterday, too. Are packages from the catalogue.tableteer.nokia.com repository only meant to be installed on the device while packages from the repository.maemo.org repository are only meant to be installed in scratchbox? Are packages in repository.maemo.org assumed to allways work on the device or only in scratchbox? I don't think this is clearly documented anywhere and it's even less a common practise because some packages in the application catalog assume and suggest to enter the repository.maemo.org on the device. This is also related to the apt-get upgrade - Reboot Cycle problem which seems to appear more frequently lately. Cheers, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VoIP through SIP
Am Freitag, den 25.08.2006, 22:31 +0200 schrieb Frédéric Crozat: Le vendredi 25 août 2006 à 20:00 +0200, Johannes Eickhold a écrit : Am Montag, den 21.08.2006, 00:58 +0200 schrieb Jaime Ruiz Frontera: On Sat, 2006-08-19 at 18:18 +0200, [EMAIL PROTECTED] wrote: [snip] I just tried it. I used it with voipbuster (www.voipbuster.com). I could register with my username and password but when I try to make a call it finishes with a segmentation fault. If you need details just tell me. I was able to replicate your segfault using my own SIP provider. I made a new release of the package which fixes the problem. Should now work for incoming and outgoing calls even if you are behind a NAT. (hint: my provider provides a STUN server which was automatically found and used by sofsip_cli) Get the package from the link above. Is there any hope to get ApplicationInstaller compatible package ? Current packages can't be installed without root privilege. Hope dies last! *ZADONK* *PLINK* *smoke fades away* Add the following repository URL with default values to you ApplicationInstaller http://jonek.hexbox.de/maemo After that you will find sofsip-cli in the section Communication. Please tell me if that is working. Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VoIP through SIP
Datum: Sat, 26 Aug 2006 22:35:58 +0200 Von: Frédéric Crozat [EMAIL PROTECTED] Add the following repository URL with default values to you ApplicationInstaller http://jonek.hexbox.de/maemo After that you will find sofsip-cli in the section Communication. Please tell me if that is working. Thanks. I've tested : I'm able to add your repository and update catalog. Unfortunately, the package base seems incorrect : Application Installer tries to download your packages at http://jonek.hexbox.de/maemo/./libsofia-sip-ua-glib0_1.12.0-1_armel.deb In Package.gz, Filename: ./libsofia-sip-ua-glib0_1.12.0-1_armel.deb is relative to catalog url, causing the incorrect url. Should be fixed now. Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VoIP through SIP
Am Montag, den 21.08.2006, 00:58 +0200 schrieb Jaime Ruiz Frontera: On Sat, 2006-08-19 at 18:18 +0200, [EMAIL PROTECTED] wrote: Hello to all! Hi Jaime. I'm wondering if is there any voip application supporting SIP in which you can choose the server you want. If you don't fear the power of the command line please feel free to check out sofsip-cli. It is a command line SIP client based on Nokia's sofia-sip SIP stack. Debian packages for the 770 and further info are available here: http://jonek.hexbox.de/?page_id=43 Feedback is highly welcome. I just tried it. I used it with voipbuster (www.voipbuster.com). I could register with my username and password but when I try to make a call it finishes with a segmentation fault. If you need details just tell me. I was able to replicate your segfault using my own SIP provider. I made a new release of the package which fixes the problem. Should now work for incoming and outgoing calls even if you are behind a NAT. (hint: my provider provides a STUN server which was automatically found and used by sofsip_cli) Get the package from the link above. Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VoIP through SIP
Am Montag, den 21.08.2006, 00:58 +0200 schrieb Jaime Ruiz Frontera: On Sat, 2006-08-19 at 18:18 +0200, [EMAIL PROTECTED] wrote: Hello to all! Hi Jaime. I'm wondering if is there any voip application supporting SIP in which you can choose the server you want. If you don't fear the power of the command line please feel free to check out sofsip-cli. It is a command line SIP client based on Nokia's sofia-sip SIP stack. Debian packages for the 770 and further info are available here: http://jonek.hexbox.de/?page_id=43 Feedback is highly welcome. Hi Jonek, I just tried it. I used it with voipbuster (www.voipbuster.com). I could register with my username and password but when I try to make a call it finishes with a segmentation fault. If you need details just tell me. Nice to see somebody taking the challange of sofsip-cli :). It is not very userfriendly or pretty looking but serves testing purposes very well as it does as an introduction to the sofia-sip library. If you need support please refer to the sofia-sip mailing list at [1]. For further help on the 770 I definately need more info from you! At least enough to replicate your error or some debugging output as was suggested on the mailing list. You can find an unstriped version of the sofsip_cli binary here [2]. Greets, Jonek. [1] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel [2] http://jonek.hexbox.de/uploads/2006/07/sofsip_cli ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] VoIP through SIP
On Sat, 2006-08-19 at 18:18 +0200, [EMAIL PROTECTED] wrote: Hello to all! Hi Jaime. I'm wondering if is there any voip application supporting SIP in which you can choose the server you want. If you don't fear the power of the command line please feel free to check out sofsip-cli. It is a command line SIP client based on Nokia's sofia-sip SIP stack. Debian packages for the 770 and further info are available here: http://jonek.hexbox.de/?page_id=43 Feedback is highly welcome. Greets, Jonek. signature.asc Description: This is a digitally signed message part ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Re: 802.11g Ad-Hoc Link?
Am Dienstag, den 11.07.2006, 15:37 -0400 schrieb Andrew Barr: On Tuesday 11 July 2006 02:54, Kalle Valo wrote: That sounds like a bug. If there's an existing Ad-Hoc network, 770 should find it and connect to it like with normal infrastructure networks. The 'W' icon in the connect dialog just should be a bit more lighter blue in Ad-Hoc networks. I wouldn't say there's a bug in the 770 software just yet. There could be a bug in NetworkManager, the ipw2200 driver, or something on the other end. I'm going to do more testing and find out, especially now that I've ditched NetworkManager on my laptop. I just tried a $ iwlist wlan0 scan and found the ESSID of the Ad-Hoc network the WLAN card of my laptop was in. When I scanned for it with a tap on blue globe this Ad-Hoc network is always there regardless if it's currently reachable or not. The 770 also does not connect to this Ad-Hoc network automatically if it is reachable. Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Kernel images not working on IT2006 final
On Tue, 2006-07-04 at 17:55 +0200, Johannes Eickhold wrote: if I try to flash a self comiled kernel image, which I made with maemo2.0-BETA in scratchbox, to the device with a fresh SU-18_2006SE_1.2006.26-8_PR_F5_MR0_ARM.bin on it, it doesn't start anymore. After a while the Nokia logo fades out and some horizontal lines of flickering pixels appear on the screan. Another few seconds later the device restarts and enters a endless restarting loop with the same effects. Problem solved by recompiling the kernel in a fresh (apt-get dist-upgrade) maemo 2.0 final environment. Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Kernel images not working on IT2006 final
Hello list, if I try to flash a self comiled kernel image, which I made with maemo2.0-BETA in scratchbox, to the device with a fresh SU-18_2006SE_1.2006.26-8_PR_F5_MR0_ARM.bin on it, it doesn't start anymore. After a while the Nokia logo fades out and some horizontal lines of flickering pixels appear on the screan. Another few seconds later the device restarts and enters a endless restarting loop with the same effects. The same is the case with the kernel image that can be found in the busybox with IPv6 section in the ApplicationCatalog2006 [1]. Are kernel images that are compiled for and run under the IT2006 beta known to be incompatible with the final version? Does anybody here managed to get a self compiled kernel to run under IT2006 final? Or do I have to wait for an upgrade of the kernel package in maemo? I also would like to know if maemo2.0 beta will change into a final version in the near future. Or are developers safe while using the current maemo2.0 beta with the IT2006 final? Thanks, Jonek. [1] http://mummola.cs.tut.fi/n770/files/linux-2.6.16+IPv6 +nfsv3client-zImage ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Kernel compilation on Nokia 770
On Thu, 2006-03-09 at 19:40 +0200, Andrey Khurri wrote: Hi Andrey, I need to compile certain version of kernel with some patches on my Nokia 770. Let's say version 2.6.13.1 I had a look at HowTo KernelCompilation on maemo.org. It uses scratchbox for that. I've got already scratchbox environment working. What is not obvious to me is how to use this algorithm in my case. Should I add an entry to /etc/apt/sources.list which would link to a repository with the needed kernel version? In the given example the kernel source they fetch is kernel-source-2.6.12.3-osso22.tar.gz I am not sure whether this is kind of specific kernel source for Nokia 770. I think it is, because e.g. the source for the needed wlan module is included in that package. If so where I can get the same but for higher version (2.6.13.1)? Good question. I suppose it should be supplied by Nokia in the maemo repo. Why do you need a newer kernel version? As well as this the content and intention of packages kernel-package 8.083.tar.gz and su-18 kernel package are not clear to me. As far as I understand it, the su-18-kernel package is provided to enable developers to install this package into their scratchbox and after that flash it on the device. See the package desciption: ~ apt-cache show su-18-kernel Package: su-18-kernel Priority: optional Section: utils Installed-Size: 1496 Maintainer: Ed Bartosh eduard.bartosh... Architecture: all Version: 2.6.12.3-200550osso1 Provides: su-18-kernel Filename: pool//maemo1.1/free/s/su-18-kernel/su-18-kernel_2.6.12.3-200550osso1_all.deb Size: 1474108 MD5sum: c402beb5c79e798b4620b73004ae5243 Description: Flashable Linux kernel for SU-18 hardware This package provides a flashable kernel image for Nokia 770. scratchbox-architecture: uarm If you rebuild this package as the kernel HowTo suggests, you get manageable (i.e. in package form) modified versions of your kernel and kernel-headers package. I guess it is also feasible to put all the sources to Tablet and start compilation process there in usual way. But in that case it would be much slower and the memory size needs to be tremendous. Am I wrong? Yes and no :). It would be a bad idea to compile the kernel on the device due to the limited resources there. IMO it is better to follow the HowTo. To be honest, I have done it in a slightly different way because I didn't wanted to setup another scratchbox target (it would have been the 3rd) because I have limited space on the / partition of my development system. The steps were the following: 1. installed the gcc-3.4 toolchain in the host debian 2. installed the su-18-kernel, kernel-source-2.6.12.3 and kernel-package packages inside my existing ARM target in scratchbox (HowTo steps Compilation 1-5) 3. compiled the kernel source from outside scratchbox using the compiler from the gcc-3.4 toolchain with the usual make menuconfig, make zImage commands. 4. flashed the new zImage binary onto the device That means I haven't rebuild the package which I don't need anyway. I haven't copied the module binaries onto the device! Only needed the changes in the kernel image itself. It seems the new kernel is working with the old modules. Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] use shell script to start application
On Wed, 2006-01-18 at 15:18 +0100, Johannes Eickhold wrote: I have hildonized gpsdrive a bit and want it to appear in the task navigator after startup. For the following PWD=/var/lib/install. gpsdrive has to be started via the script usr/bin/gpsdrive.sh. If I specify this file in the .desktop file, gpsdrive can be started in the correct way from the menu and via run-standalone.sh usr/bin/gpsdrive.sh but doesn't show up in the task navigator. If I specify .../usr/bingpsdrive (the binary executable) in the .desktop file, only the application is startet broken (needed parts from the script are not executed) BUT it shows up in the task navigator after that. If I start it via run-standalone.sh everyting is fine (e.g. correct startup AND showing in task navigator). How can I fix this? Since nobody answerd my question yet I'm going to share my thoughts with you I had in the meantime. First a thx to Florian Boor for pointing me to http://maemo.org/platform/docs/tutorials/Maemo_tutorial.html#Automatic-connection which seems to descibe what I want to achieve. It says: ... This my_application.sh is then started from the desktop file where the runnable binary is normally specified. Read more about desktop files from this earlier chapter. ... That leads to the question HOW to start the _script_ if Exec specifies the _binary_ (gpsdrive.sh vs. gpsdrive)? That's not described in the referenced section. Every time I specified the binary in Exec, only the binary was started. Result: icon in task navigator but no script execution. Every time I specified the script in Exec, only the script was executed. Result: no icon in task navigator. I tried this inside scratchbox and on the real device. After each change to the desktop file maemo had to be restarted what I did. So far the only possible solution seems to be to move the work done by the script into the binary which in my opinion is ugly. I realy would like to get enlightened! Thanks, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
On Mon, 2006-01-09 at 20:04 -0700, Brad Midgley wrote: Johannes The two types of bluetooth audio are very different. You linked to a discussion about the other type. Sorry, I didn't made that clear enough. I was refering to the following said in http://article.gmane.org/gmane.linux.bluez.devel/6729 by Marcel Holtmann: The Nokia 770 is using a TI chip and basically nobody of us has real experiences with these chips. I have seen them in an iPAQ and now the 770, but that's it. Do you think Nokia is willing to donate some of the TI development kits to BlueZ? Especially the SCO and eSCO stuff needs a lot of testing and I would prefer to do it with an i386 or x86_86 based system. And the answer to that in http://article.gmane.org/gmane.linux.bluez.devel/6748 by Ville Tervo from Nokia: I'll try to arrange something. low-latency voice-quality mono audio uses a special transport (SCO) and is delivered from the bluetooth chip either over the regular data connection to the cpu (HCI) or it is connected to dedicated audio/analog hardware (PCM). The HCI formatting and negotiation differs from chip to chip and the linux driver is only complete for CSR chipsets. Thanks for the explanation - SCO is exectly what I need then. a2dp specifies one-way high-quality, traditionally stereo, audio. It is delivered over an L2CAP socket so linux can send and receive this audio with any bluetooth chip that has even the most basic support. So that is used for bluetooth stereo earphones to listen to e.g. CD music? We know what has to be done for a2dp. The SCO stuff is what I would like to see help from Nokia on. I would hope they can help us with the HCI interaction with the SCO transport since that gives us the most generic control over the audio stream. Thanks for that details! Jonek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Wavemon or other monitoring application for WLAN
On Mon, 2006-01-09 at 15:22 +0100, Dirk Kuijsten wrote: I wanted to make an application that can connect to a hotspot and test the connection and/or do an automatic weblogin (my hotspot provider here in the Netherlands doesn't support EAP). Or start scripts to test the connection. If I understand you correctly you want some actions executed automatically if you choose a connection from within the connection manager? That has been discussed on #maemo. I think the solution is to listen for the dbus messages that are generated upon establishment of a WLAN connection and use them to trigger scripts that do further work after a connection is established. Personally I don't like this kind of solution very much, because this had to be done by some kind of daemon listening on the dbus all the time. *think out loud* something like the options in debians /etc/network/interfaces stanzas should be used. Like post-up [command]. But there are no config files there on the 770 for interface configuration. Events (dbus messages) are way cooler (modern), but are they the easiest way to go for such things? The problem is: is there a way to interface with the connection manager? That is definately needed. One should be able to hook post-up scripts for the APs connection settings that are already saved on the 770! Everybody knows that WEP and WAP are insecure. To overcome that, many institutions use differnt kinds of VPN connections that should be integrated in the connection manager through script hooks. According to the Maemo package reference the packages osso-wlan and osso-wlan-security (EAP deamon) are from Nokia. But my question is: will the sources be available? http://repository.maemo.org/unstable/1.1rc5/package_reference.html Good question. I would also like it if the EAP daemon supported EAP-TTLS, which it doesn't yet. My university only supports ttls or cisco-vpn. My university uses cisco-vpn too and therefor I use VPNC on the 770 which works fine except that I would like to have it executed automatically when I connect to one of my universities APs. http://maemo.org/maemowiki/InstallVPNC 2. Thus I looked at the current modules loaded: cx3110x (lsmod). They are in /mnt/initfs/lib/modules/2.6.12.3-omap1/ It seems the license for the cx3110x module is GPL version 2 (do a strings on it). Thus Nokia should provide the source of the module. With it we could write the osso-wlan package ourselves. Note: I know this is a Conexant cx3110x wlan chip with a lower mac (umac), which is probably in the wlan-firmware package. I don't need those sources. The strings of this module also do give Proprietary as it should. Is the firmware integrated into that kernel module or does the module load it onto the hardware from a different file? Greets, Jonek. PS: Wavemon would be nice to have. Timo: it depends on ncurses! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Bluetooth headset - not really working?
On Tue, 2005-12-20 at 10:16 -0700, Brad Midgley wrote: I'm overseeing the bluetooth audio on linux project... Linux only supports SCO transfers for CSR chips. To use the current btsco stuff, Nokia is going to have to contribute a SCO driver to the kernel for whatever bluetooth chip they put in the 770. I found some further info at: http://thread.gmane.org/gmane.linux.bluez.devel/6713 Can anyone of the Nokia developers give us some more hints on the head set topic please? Can we only expect that to work when the 2006 software edition will be released or will the head set support be included in an earlier firmware update? This missing feature is very much appreciated! Greets, Jonek. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bi-di BT-link between two 770s
On Mon, 2005-11-07 at 00:00 +0200, Johan Hedberg wrote: On Sun, Nov 06, 2005, Patrick Ohly wrote: Another use of Bluetooth could be connecting the 770 to a GPS receiver. With its large screen it would make a nice moving map display, although my primary use would be to simply transfer waypoints and track data to and from a Garmin eTrex during cycling trips. I currently use an iPAQ with Familiar Linux for that purpose, but might replace that with the 770 if I can get it to work - currently I still wait for a Bluetooth-RS232 adapter (the eTrex only has a serial port). I'm sure it can be done with root access, but making the same functionality also available to users of the official firmware certainly would be nice. Searching for remote devices and creating outgoing RFCOMM connections (e.g. to serial port profile) doesn't require root privileges, so that should work just fine with the normal firmware. As the wiki states on http://maemo.org/maemowiki/BluetoothGPS root access is requiered to create the needed rfcommX device node. Following that HowTo i successfully read NMEA data from my GPS mouse. I don't know how to do this without such a device node. Jonek -- http://770.hexbox.de/blog ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] bi-di BT-link between two 770s
On Sun, 2005-11-06 at 15:32 +0200, Aleksandr Koltsoff wrote: Hello Since my BT skills are non-existant, I'm asking for help for this project. I'm thinking of implementing a simple util library that would provide two-way stream-communication between games running on two 770s (same game obviously). How should I proceed in this? The following issues come into mind, but I'm looking for someone who would have concrete information on how to solve these problems: 1) When starting the game, how does the end-user see the other 770-device? ie, is pairing necessary, and is there a GUI for this (connection damager?) ^ Hehe, that was a good one :). 2) What do I need to do to make 770 visible to the other 770 (assuming there is a GUI for this on the other side). Can this be done programmatically without requiring user intervention? This is called inquiry scan mode and has to be activated in /etc/bluetooth/hcid.conf on the 770. 3) Is using RFCOMM-sockets between the devices a suitable transport? (I'm looking for something akin to TCP). It can be assumed that only one program will be active on a device at one time that needs this, so I guess BT-MAC address is enough to connect? I just wrote a HowTo for setting up IP connections over bluetooth with the 770. http://maemo.org/maemowiki/HOWTO-BluetoothNetworking 4) Can all of this be done with a normal application installed via the AI on a stock 770? (not requiring the user to reflash from the sales sw version) So, mostly the questions arise from my lacking experience with BT-programming and my lack of experience with the 770 sw. If you know whether the problems above can be solved, I'm interested in hearing from you. I plan to release the utility lib under lgpl if it's possible to implement at all (I know that technically anything is possible, but question 4 might stop this from being possible). I would be interested in hearing from you about any successes. Greets, Jonek. -- http://770.hexbox.de/blog ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
