Re: [Debian -FSO -GPS] No Fix
On Wed, 19 Nov 2008 23:56:33 -0800 (PST) Fragggy [EMAIL PROTECTED] wrote: I think so. cat /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron shows a 1 I have put the Freerunner next to a window over Night and logt the output of /dev/ttySAC1. After a few minutes I got Messages like this: $GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*66 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E [...] but still no fix this morning. [...] I am not sure that I follow. The 'A' in the third field above indicates valid autonomous GPRMC data, i.e., you do have a fix. Regards, Gora ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian] openmoko-panel-plugin v0.6
Hi everyone, after some work we are happy to release a new version of the openmoko-panel-plugin (0.6). the openmoko-panel-plugin is a gtk based plugin for the nice bars in common windowmanagers like xfce or gnome. it shows you status' of i.e. your battery or your gps and i.e. handles keyboard applications. Changelog: porting the software to fso framework milestone 4 this is just a porting release. new features will arrive as soon as chris merged his new module structure with the new release. it can be downloaded from our project page: https://projects.openmoko.org/projects/panel-plugin/ or via the pkg-fso debian repository (apt-get install openmoko-panel-plugin) i hope that all your problems with the old version and the new milestone now vanished. regards sebastian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
On Thu, Nov 20, 2008 at 04:51, Walter Chang [EMAIL PROTECTED] wrote: read the comments at the bottom: http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html On Thu, Nov 20, 2008 at 6:09 AM, Tomas Riveros Schober [EMAIL PROTECTED] wrote: I'm not familiar with the android environment so here are a couple of questions do I need the android SDK to install this keyboard? if I don't need it then, how do I ssh into android once it's running? I've tried the usual ifconfig usb0 x.x.x.x ssh [EMAIL PROTECTED] but the connection is refused. if i dont need to ssh to install it, then how to do it? for example I do the ifconfig usb. thing, then : export ADBHOST=192.168.0.202 ./adb install yourapp.apk (download adb from SDK, or from here : http://people.openmoko.org/sean_mcneil/ ) But you can also just copy the .apk file directly on the SD card second partition, under /app (by exemple via ssh if you booted another distro, just copy under /media/mmcblk0p2/app/ ) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Would it be (legally and technically) possible to reuse the best keyboard around on Openmoko (read Illume) in Android? On Thu, November 20, 2008 09:41, Cédric Berger wrote: On Thu, Nov 20, 2008 at 04:51, Walter Chang [EMAIL PROTECTED] wrote: read the comments at the bottom: http://onlinedev.blogspot.com/2008/11/getting-started-with-android-on-neo.html On Thu, Nov 20, 2008 at 6:09 AM, Tomas Riveros Schober [EMAIL PROTECTED] wrote: I'm not familiar with the android environment so here are a couple of questions do I need the android SDK to install this keyboard? if I don't need it then, how do I ssh into android once it's running? I've tried the usual ifconfig usb0 x.x.x.x ssh [EMAIL PROTECTED] but the connection is refused. if i dont need to ssh to install it, then how to do it? for example I do the ifconfig usb. thing, then : export ADBHOST=192.168.0.202 ./adb install yourapp.apk (download adb from SDK, or from here : http://people.openmoko.org/sean_mcneil/ ) But you can also just copy the .apk file directly on the SD card second partition, under /app (by exemple via ssh if you booted another distro, just copy under /media/mmcblk0p2/app/ ) ___ 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: Your favorite ringtones? (especially .sid?)
The Best SID ever is the theme from R-Type, IMHO. It also makes a fantastic ringtone. The only problem with having this as a ringtone is that you tend not to answer the phone because you're boogie-ing along to the awesome ringtone. Other notable Sids include music from: - IK+ (International Karate Plus) - Maniac Mansion - Robocop - Bubble bobble There are literally thousands of SIDs available. To find them, you really can't go past the High Voltage Sid Collection, which somebody else linked to. When it came out, the SID chip in the c64 was considered a very advanced sound chip, so the C64 music scene thrived. There are still people (like me!) who still listen to sid files to this day. If you can't be bothered looking at the thousands of sids in the HVSC, try checking out the top 100: http://www.transbyte.org/SID/HVSC_Top100.html I was gratified to see all of my recommendations except for bubble bobble and maniac mansion in the top 100. If you can't be bothered testing each SID tune on your Neo, get yourself a sid player plugin for your audio software (personally, I use XMMS and the XMMS-SID plugin) to listen to them on your PC. There are also standalone SID players if you can't find a plugin. Enjoy! -Dale [EMAIL PROTECTED] wrote: Hi, I'm looking for a new ringtone (I like the arkanoid theme, but I need a change). If you have one you like, could you let me (us) know? Tobias mentions a place to find .sids in his email below -- I just couldn't go through all of them. Thanks, Eric Tobias Gruetzmacher wrote: Hi, Here is a patch for frameworkd that allows to inject gstreamer options into file names for the audio playing service. I wrote it because I wanted to use the title music from Giana Sisters as a ring tone, which is tune number 5 in Great_Giana_Sisters_PSID.sid ;) This patch is very generic to allow any option to be injected from the file name. It may be desirable to restrict this to specific options, but currently this allows everything, so you can easily break playing altogether... So if you really want to hear Einigkeit und Recht und Freiheit in glorious 3-channel SID, grab yourself a copy of http://hafnium.prg.dtu.dk/HVSC/C64Music/GAMES/S-Z/Summer_Games.sid, place it in /usr/share/sounds and set Summer_Games.sid;tune=5 as your ring tone. Or a manic laughter when an SMS arrives? Try http://hafnium.prg.dtu.dk/HVSC/C64Music/MUSICIANS/L/Lieblich_Russell/Ghostbusters_PSID.sid and set Ghostbusters_PSID.sid;tune=4 as your message tone. Well, you get the idea. :) Since I'm not very fluent with Python, please point out anything I might have done wrong. Hope you like the patch. Greetings, Tobias ___ smartphones-standards mailing list [EMAIL PROTECTED] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards ___ 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: The forbidden topic: Glamo OpenGL
hehehe, it's good to see OM people having a sense of humour as well! :) Steve Mosher wrote: they don't already? please issue a ticket. we'll fix the bug. George Brooke wrote: On Wed, 19 Nov 2008 00:01:47 +1100 Dale Maggee [EMAIL PROTECTED] wrote: Tig wrote: Ok I will bite :) Q: Why did OM cross the road? A: To get to another toolkit :) Q: How many OM devs does it take to change a lightbulb? A: Well first we need to abandon the old lightbulb holder because at a later date we may not be able to plug a floodlight in, bring in a new lightbulb holder and adapt it to multiple floodlights, meanwhile the engineering team has realized that this will only run green floodlights and has started rewiring the whole house.. :) The burnt out lightbulb is due to be fixed at a later date :) Please not this is not a cue for a thread on lightbulb analogies :) Q: What is the difference between a professional photographer and OM user? A: The OM user has to flash more often :) Q: Why did the OM newbie log onto #openmoko? A: Because they had not read: a) the wiki and b) the topic As then they would know you slide your finder up on the keyboard to get the numbers to enter your sim pin. I will be here all week, try the salad :) Regards (apologies for posting via gmane moving e-mail around) Hehe, love the lightbulb one! Q: What's the difference between an iphone and a freerunner? A: One works but takes away your freedom, the other is free but needs your work Knock, Knock Who's There? A Neo User A Neo User Q: What did the Neo say to the insomniac? A: At least when you go to sleep you know you'll wake up! Ancient chinese proverb: Neo owner is man carrying wall charger And I've saved my favorite for last: Q: What's the difference between a brick and a freerunner? A: A brick isn't designed to make phone calls. ;) -Dale (All in good fun) Maybe these should appear on the splash screen of the Neos solar.george ___ 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 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: The forbidden topic: Glamo OpenGL
Warren Baird wrote: OM2008.9 and FSO walk into a bar. How are you? How are you? asks FSO. Buzzz says OM2008.9 LOL! (for once, usage of that horrible acronym is actually appropriate - I really did laugh out loud!) this is my new splash screen... :D moko_bar.gz Description: GNU Zip compressed data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Will there be a hardware revision for the buzzing issue?
On Thu, Nov 20, 2008 at 3:00 AM, Joerg Reisenweber [EMAIL PROTECTED] wrote: Am Mo 17. November 2008 schrieb robert lazarski: Hi all, I'm about to buy an openmoko, as I finally have some time and cash. However, my understanding is that the latest phones for sale have a buzzing issue and its confirmed to be hardware related. Will there be a hardware revision? Or I'm a stuck using a soldering iron and new parts to fix it? Please correct me if I'm misinformed. We are actually in the process to figure out how to fix *all* devices sold, by implementing the so-called big-C fix (which means add a 100uF, replace one R), which can be done by those experienced in soldering. Not yet clear where this will end, but we're on it. Very next thing is we will publish a rework SOP paper. Also see other answer in this thread. cheers jOERG Thanks for the info. While I'm good at soldering, I'd prefer to wait for an A7 revision if that happens. Searching the hardware archives mentioned there might be one: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00696.html I realize it may take a while. I'm guessing A7, if it happens, may also have other updates which may help some other issues of the phone. Looking at the hardware wiki, I see no list of confirmed or even suspected hardware issues. My interest in openmoko is kernel and bootloader related, and there's just somethings that can't be fixed in hardware despite the steady stream of patches I see on the kernel list. So I'm unclear if some issues like suspend, battery life amd missed calls are perhaps hardware issues? Just trying to make an informed choice between buying now or later. Best regards, Robert ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Will there be a hardware revision for the buzzing issue?
On Thu, Nov 20, 2008 at 6:07 AM, robert lazarski [EMAIL PROTECTED] wrote: On Thu, Nov 20, 2008 at 3:00 AM, Joerg Reisenweber [EMAIL PROTECTED] wrote: Am Mo 17. November 2008 schrieb robert lazarski: Hi all, I'm about to buy an openmoko, as I finally have some time and cash. However, my understanding is that the latest phones for sale have a buzzing issue and its confirmed to be hardware related. Will there be a hardware revision? Or I'm a stuck using a soldering iron and new parts to fix it? Please correct me if I'm misinformed. We are actually in the process to figure out how to fix *all* devices sold, by implementing the so-called big-C fix (which means add a 100uF, replace one R), which can be done by those experienced in soldering. Not yet clear where this will end, but we're on it. Very next thing is we will publish a rework SOP paper. Also see other answer in this thread. cheers jOERG Thanks for the info. While I'm good at soldering, I'd prefer to wait for an A7 revision if that happens. Searching the hardware archives mentioned there might be one: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00696.html I realize it may take a while. I'm guessing A7, if it happens, may also have other updates which may help some other issues of the phone. Looking at the hardware wiki, I see no list of confirmed or even suspected hardware issues. My interest in openmoko is kernel and bootloader related, and there's just somethings that can't be fixed in hardware despite the steady stream of patches I see on the kernel list. So I'm unclear if some issues like suspend, battery life amd missed calls are perhaps hardware issues? Just trying to make an informed choice between buying now or later. Best regards, Robert s/can't be fixed in hardware/can't be fixed in software/ - R ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Refund policy
What's the refund policy for the FreeRunner? Nothing wrong with the phone. Something wrong with me. I can't handle the complexity. i don't think there's one for this kind of problem. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO M4] What a wonderfull world
I had the restart the phone in order to read the message ... shouldn't it suffice to restart frameworkd? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Illume dictionary for Dutch (Nederlands)
Hi all, I intent to generate the following: - a full list utf-8 (for 8 bit SMS and regular use, default) - b full list utf-8 GSM 03.38[1] (for 7 bit SMS) - c truncated list utf-8 (for 8 bit SMS and regular use) - d truncated list utf-8 GSM 03.38[1] (for 7 bit SMS, default) [1] These utf-8 characters in this list are within the 7-bit range of GSM 03.38, see http://en.wikipedia.org/wiki/Short_message_service#GSM Note that more characters a and b will both have 250,000 words b will be conversion, remapping and normalisation of a c and d are truncations and normalisation of respectively a and b For utf-16, a simple conversion of the utf-8 files can be used, but I'll leave this for now. This could result in two extra files. Note that nor extended nor non-extended ASCII is available. Is this desirable? This can result in four extra files. So, I can come up with 10 different files. Which are according to you the most useful? Regards, Pander On Thu, November 20, 2008 08:58, Rui Miguel Silva Seabra wrote: On Thu, Nov 20, 2008 at 03:02:41AM +0100, Marco Trevisan (Treviño) wrote: Pander wrote: Of course this particular word list is very long and contains about 250,000 words and has a typical lng tail. Many words or compositions or occur seldom in average day use. What would be a good cut off point in number of words, also in terms of performance? The Portuguese list contains 56,609 words. Is this workable? How many does the English contain? The Italian one can count also 500'000 words (to be short), but I can get a well working dictionary only using a smaller one (with about 150'000 words that I've taken counting its google popularity). Btw I've written more complete posts about this on the list... Well, since my basis was based on a million words taken from the most printed daily newspaper in Portugal (I didn't count but still I removed a lot of non words like numbers, etc...) already with frequency data, my job was so much easier... :) As for writing SMS/text messages... I haven't found yet a word that wasn't there (in fact my problem is that it so often is the first of several matches so I have to use the menu on the left) but I must confess to not be one of those whose primary use of the phone is SMS/text! Rui -- Frink! Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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: Illume dictionary for Dutch (Nederlands)
I have no idea... I might only make a new version with utf-8 encoded characters. :) On Thu, Nov 20, 2008 at 10:40:46AM +0100, Pander wrote: Hi all, I intent to generate the following: - a full list utf-8 (for 8 bit SMS and regular use, default) - b full list utf-8 GSM 03.38[1] (for 7 bit SMS) - c truncated list utf-8 (for 8 bit SMS and regular use) - d truncated list utf-8 GSM 03.38[1] (for 7 bit SMS, default) [1] These utf-8 characters in this list are within the 7-bit range of GSM 03.38, see http://en.wikipedia.org/wiki/Short_message_service#GSM Note that more characters a and b will both have 250,000 words b will be conversion, remapping and normalisation of a c and d are truncations and normalisation of respectively a and b For utf-16, a simple conversion of the utf-8 files can be used, but I'll leave this for now. This could result in two extra files. Note that nor extended nor non-extended ASCII is available. Is this desirable? This can result in four extra files. So, I can come up with 10 different files. Which are according to you the most useful? Regards, Pander On Thu, November 20, 2008 08:58, Rui Miguel Silva Seabra wrote: On Thu, Nov 20, 2008 at 03:02:41AM +0100, Marco Trevisan (Treviño) wrote: Pander wrote: Of course this particular word list is very long and contains about 250,000 words and has a typical lng tail. Many words or compositions or occur seldom in average day use. What would be a good cut off point in number of words, also in terms of performance? The Portuguese list contains 56,609 words. Is this workable? How many does the English contain? The Italian one can count also 500'000 words (to be short), but I can get a well working dictionary only using a smaller one (with about 150'000 words that I've taken counting its google popularity). Btw I've written more complete posts about this on the list... Well, since my basis was based on a million words taken from the most printed daily newspaper in Portugal (I didn't count but still I removed a lot of non words like numbers, etc...) already with frequency data, my job was so much easier... :) As for writing SMS/text messages... I haven't found yet a word that wasn't there (in fact my problem is that it so often is the first of several matches so I have to use the menu on the left) but I must confess to not be one of those whose primary use of the phone is SMS/text! Rui -- Frink! Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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 -- You are what you see. Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Illume dictionary for Dutch (Nederlands)
Small correction to my text: Note that more characters must be Note that certain special characters are in GSM 03.38 which are not in extended ASCII Nevertheless, one complete utf-8 dictionary could be used by most applications, also SMS. The conversion I do for GSM 03.38 could also be done later just before sending the SMS. On Thu, November 20, 2008 10:44, Rui Miguel Silva Seabra wrote: I have no idea... I might only make a new version with utf-8 encoded characters. :) On Thu, Nov 20, 2008 at 10:40:46AM +0100, Pander wrote: Hi all, I intent to generate the following: - a full list utf-8 (for 8 bit SMS and regular use, default) - b full list utf-8 GSM 03.38[1] (for 7 bit SMS) - c truncated list utf-8 (for 8 bit SMS and regular use) - d truncated list utf-8 GSM 03.38[1] (for 7 bit SMS, default) [1] These utf-8 characters in this list are within the 7-bit range of GSM 03.38, see http://en.wikipedia.org/wiki/Short_message_service#GSM Note that more characters a and b will both have 250,000 words b will be conversion, remapping and normalisation of a c and d are truncations and normalisation of respectively a and b For utf-16, a simple conversion of the utf-8 files can be used, but I'll leave this for now. This could result in two extra files. Note that nor extended nor non-extended ASCII is available. Is this desirable? This can result in four extra files. So, I can come up with 10 different files. Which are according to you the most useful? Regards, Pander On Thu, November 20, 2008 08:58, Rui Miguel Silva Seabra wrote: On Thu, Nov 20, 2008 at 03:02:41AM +0100, Marco Trevisan (Treviño) wrote: Pander wrote: Of course this particular word list is very long and contains about 250,000 words and has a typical lng tail. Many words or compositions or occur seldom in average day use. What would be a good cut off point in number of words, also in terms of performance? The Portuguese list contains 56,609 words. Is this workable? How many does the English contain? The Italian one can count also 500'000 words (to be short), but I can get a well working dictionary only using a smaller one (with about 150'000 words that I've taken counting its google popularity). Btw I've written more complete posts about this on the list... Well, since my basis was based on a million words taken from the most printed daily newspaper in Portugal (I didn't count but still I removed a lot of non words like numbers, etc...) already with frequency data, my job was so much easier... :) As for writing SMS/text messages... I haven't found yet a word that wasn't there (in fact my problem is that it so often is the first of several matches so I have to use the menu on the left) but I must confess to not be one of those whose primary use of the phone is SMS/text! Rui -- Frink! Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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 -- You are what you see. Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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: Illume dictionary for Dutch (Nederlands)
On Thu, 20 Nov 2008 10:55:02 +0100 (CET) Pander [EMAIL PROTECTED] babbled: any dictionary should not care about gsm encodings. it should be just a utf8 dictionary file. it is the job of the sms app to convert normal utf8 unicode to whatever encoding used by the network, and back. :) Small correction to my text: Note that more characters must be Note that certain special characters are in GSM 03.38 which are not in extended ASCII Nevertheless, one complete utf-8 dictionary could be used by most applications, also SMS. The conversion I do for GSM 03.38 could also be done later just before sending the SMS. On Thu, November 20, 2008 10:44, Rui Miguel Silva Seabra wrote: I have no idea... I might only make a new version with utf-8 encoded characters. :) On Thu, Nov 20, 2008 at 10:40:46AM +0100, Pander wrote: Hi all, I intent to generate the following: - a full list utf-8 (for 8 bit SMS and regular use, default) - b full list utf-8 GSM 03.38[1] (for 7 bit SMS) - c truncated list utf-8 (for 8 bit SMS and regular use) - d truncated list utf-8 GSM 03.38[1] (for 7 bit SMS, default) [1] These utf-8 characters in this list are within the 7-bit range of GSM 03.38, see http://en.wikipedia.org/wiki/Short_message_service#GSM Note that more characters a and b will both have 250,000 words b will be conversion, remapping and normalisation of a c and d are truncations and normalisation of respectively a and b For utf-16, a simple conversion of the utf-8 files can be used, but I'll leave this for now. This could result in two extra files. Note that nor extended nor non-extended ASCII is available. Is this desirable? This can result in four extra files. So, I can come up with 10 different files. Which are according to you the most useful? Regards, Pander On Thu, November 20, 2008 08:58, Rui Miguel Silva Seabra wrote: On Thu, Nov 20, 2008 at 03:02:41AM +0100, Marco Trevisan (Treviño) wrote: Pander wrote: Of course this particular word list is very long and contains about 250,000 words and has a typical lng tail. Many words or compositions or occur seldom in average day use. What would be a good cut off point in number of words, also in terms of performance? The Portuguese list contains 56,609 words. Is this workable? How many does the English contain? The Italian one can count also 500'000 words (to be short), but I can get a well working dictionary only using a smaller one (with about 150'000 words that I've taken counting its google popularity). Btw I've written more complete posts about this on the list... Well, since my basis was based on a million words taken from the most printed daily newspaper in Portugal (I didn't count but still I removed a lot of non words like numbers, etc...) already with frequency data, my job was so much easier... :) As for writing SMS/text messages... I haven't found yet a word that wasn't there (in fact my problem is that it so often is the first of several matches so I have to use the menu on the left) but I must confess to not be one of those whose primary use of the phone is SMS/text! Rui -- Frink! Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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 -- You are what you see. Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ 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 -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [2008.x] Settings app not working
Ivar Mossin a écrit : November 1st I upgraded from 2008.9 stable to 2008.x testing, using opkg update opkg upgrade. This broke the settings applications which no longer starts. I have just now updated and upgraded again to see if there would be a fix in the repository without any luck. I have also searched google and the mailing lists without finding anything relevant. Did you try opkg dist-upgrade ? I'm not even sure it exists in opkg, but on debian/ubuntu-systems, upgrade doesn't install new packages, if needed. So it could hang somewhere between two versions. dist-upgrade, on the other hand, will happily install new needed packages. Linus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian -FSO -GPS] No Fix
Hi, On Wed, Nov 19, 2008 at 11:56:33PM -0800, Fragggy wrote: I think so. cat /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/neo1973-pm-gps.0/pwron shows a 1 I have put the Freerunner next to a window over Night and logt the output of /dev/ttySAC1. After a few minutes I got Messages like this: $GPRMC,073904.00,A,5127.73160,N,00651.01957,E,0.229,279.62,201108,,,A*66 $GPVTG,279.62,T,,M,0.229,N,0.424,K,A*3E $GPGGA,073904.00,5127.73160,N,00651.01957,E,1,09,0.92,26.1,M,47.5,M,,*6E $GPGSA,A,3,05,04,09,29,12,30,02,14,321.49,0.92,1.17*07 $GPGSV,3,1,11,05,78,276,25,17,03,039,,04,21,068,32,09,48,135,28*7A $GPGSV,3,2,11,29,19,200,27,12,83,044,28,30,50,263,37,02,18,113,29*78 $GPGSV,3,3,11,14,42,290,33,32,05,344,33,31,04 but still no fix this morning. Restart and then please do not read/write from/to /dev/ttySAC1. For further informations, search the ml archives... Greetings, Sascha ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Announce: omnewrotate 0.5.0
El día Wednesday, November 19, 2008 a las 11:21:42PM +, Rui Miguel Silva Seabra escribió: http://blog.1407.org/2008/11/19/openmoko-newrotate-050-lazy-edition-is-out/ Hi, I???ve just release a new version of omnewrotate (OpenPGP signature), the ???Lazy Edition??? because it uses so much less CPU than any version I did before. Oh, I forgot to mention it in the release commit, but at least with FSO M4 I???m getting a very stable rotation BUT if the screen looks garbled, please wait a few seconds until the graphic user interface adjusts to the screen changes. I don???t think I can do much about that??? ... Hi, Is there somewhere a binary for installation? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Q: What's the difference between an iphone and a freerunner? A: One works but takes away your freedom, the other is free but needs your work. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Announce: omnewrotate 0.5.0
On Thu, Nov 20, 2008 at 11:09:47AM +0100, Matthias Apitz wrote: El día Wednesday, November 19, 2008 a las 11:21:42PM +, Rui Miguel Silva Seabra escribió: http://blog.1407.org/2008/11/19/openmoko-newrotate-050-lazy-edition-is-out/ Hi, I???ve just release a new version of omnewrotate (OpenPGP signature), the ???Lazy Edition??? because it uses so much less CPU than any version I did before. Oh, I forgot to mention it in the release commit, but at least with FSO M4 I???m getting a very stable rotation BUT if the screen looks garbled, please wait a few seconds until the graphic user interface adjusts to the screen changes. I don???t think I can do much about that??? ... Hi, Is there somewhere a binary for installation? Thx Yes, in the tarball. It works under FSO, and should also work under Om2008.x, FDOM, and others, but I don't have time to do those tests regularly. Rui -- Fnord. Today is Prickle-Prickle, the 32nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Will there be a hardware revision for the buzzing issue?
Am Do 20. November 2008 schrieb robert lazarski: On Thu, Nov 20, 2008 at 6:07 AM, robert lazarski [EMAIL PROTECTED] wrote: On Thu, Nov 20, 2008 at 3:00 AM, Joerg Reisenweber [EMAIL PROTECTED] wrote: Am Mo 17. November 2008 schrieb robert lazarski: Hi all, I'm about to buy an openmoko, as I finally have some time and cash. However, my understanding is that the latest phones for sale have a buzzing issue and its confirmed to be hardware related. Will there be a hardware revision? Or I'm a stuck using a soldering iron and new parts to fix it? Please correct me if I'm misinformed. We are actually in the process to figure out how to fix *all* devices sold, by implementing the so-called big-C fix (which means add a 100uF, replace one R), which can be done by those experienced in soldering. Not yet clear where this will end, but we're on it. Very next thing is we will publish a rework SOP paper. Also see other answer in this thread. cheers jOERG Thanks for the info. While I'm good at soldering, I'd prefer to wait for an A7 revision if that happens. Searching the hardware archives mentioned there might be one: http://www.mail-archive.com/[EMAIL PROTECTED]/msg00696.html I realize it may take a while. I'm guessing A7, if it happens, may also have other updates which may help some other issues of the phone. Looking at the hardware wiki, I see no list of confirmed or even suspected hardware issues. My interest in openmoko is kernel and bootloader related, and there's just somethings that can't be fixed in hardware despite the steady stream of patches I see on the kernel list. So I'm unclear if some issues like suspend, battery life amd missed calls are perhaps hardware issues? Just trying to make an informed choice between buying now or later. Best regards, Robert s/can't be fixed in hardware/can't be fixed in software/ - R for A7 there's no bugfix changes to expect, except beforementioned big-C rework for buzz issue. There are some minor improvements on audio quality for headset stereo (1u-4.7u). That's no bugfix in the end :-/ Currently we are not planing any hw-fixes for known bugs, that didn't make it to A7 version, means we aren't aware of such bugs that could be fixed for A8. For an eventual A8 we are planning some minor layout changes (3 beads) to make even more sure buzz is gone. (maybe this might also improve situation of buzz while using wired headset for a call. However it's not aimed at that topic) All A5 and A6 versions can be updated to A7 version by cumulative application of the changes done from A5 - A6 - A7 (again that's nothing more than big-C for recent A6) All this to the best of my knowledge, without any warranty ;-) HTH cheers jOERG signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO M4] What a wonderfull world
well, it should work, although I couldn't test it, as at this moment I had'nt any computer around me ... 2008/11/20 arne anka [EMAIL PROTECTED] I had the restart the phone in order to read the message ... shouldn't it suffice to restart frameworkd? ___ 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: [Qt Extended] Mapping Demo (was Re: [FSO] Stability and other problems)
Michael 'Mickey' Lauer wrote:
Am Wednesday 19 November 2008 12:18:28 schrieb superalex:
Hi, I'm using FSO since yesterday and found that the famous echo bug was
still appearing. I found a solution that is working for me based in the
2008.8 one.
In file
/usr/lib/python2.5/site-packages/framework/subsystems/ogsmd/modems/ti_calyp
so/unsolicited.py, function percentCPI, line 210 aprox
Where it says:
info = {}
I have:
devchannel =
self._object.modem.communicationChannel(DeviceMediator)
devchannel.enqueue( %N0187 )
info = {}
Guess we should make this configurable, FSO is using -6db, not -12db since
this sounds pretty harsh for many people.
That's a good idea, but I think the issue may be a bit different. With
Qtopia people were reporting no echo for the first call, but echo on
subsequent calls. Since we're using an undocumented feature of the modem
we don't know under what conditions it might be disabled, even though we
don't disable it explicitly. Currently we only set the echo suppression
in init, while this patch sets it on every call state transition. It may
be worth moving it down a few lines so it only happens when a call
connects, but this way we can be certain that echo suppression is
enabled for every call.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Om2008.9] gsmspeakerout.state - headset working
What about the headset working on qt mediaplayer? When I use the earphones with qt mediaplayer, the external speakers are still working. I don't know how to disable the loud speakers, in order to listen the sound only through the earphones. Any hint? On Thu, Nov 20, 2008 at 8:48 AM, Tom Yates [EMAIL PROTECTED] wrote: On Wed, 19 Nov 2008, Matthias Apitz wrote: one don't need extending the desktop to launch 'alsactl -f gsmspeakerout.state restore'; when you're in a call there is a small menue on the left buttom side called 'Options' which let you switch between 'handset' and 'speakerout'; you star! from that, moving gsmspeakerout.state to one side and linking gsmheadset.state to gsmspeakerout.state means that, whilst i don't need speakerphone mode much, i can now switch to headset - which is very important for me - inside a call. i notice now that there's a headset option that shows up there *sometimes*, but it's less-easy to access than speakerphone and anyway it doesn't work as well. perhaps it loads headset.state instead of gsmheadset.state? if anyone else wants the details, they're at http://www.teaparty.net/technotes/openmoko-2.html#Headset . interestingly, this has reduced the list of things that prevent my 'moko from being a perfectly good everyday phone to zero. -- Tom Yates - http://www.teaparty.net ___ 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: Refund policy
Better sell it directly sure will be someone interested 2008/11/20 arne anka [EMAIL PROTECTED]: What's the refund policy for the FreeRunner? Nothing wrong with the phone. Something wrong with me. I can't handle the complexity. i don't think there's one for this kind of problem. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[OM2008.9 - FDOM] Re: Will there be a hardware revision for the buzzing issue?
Dear members, I follow the list since October, although I own my Freerunner since July. I owned a A5 before I needed its substitution from my seller because the handsfree speaker stopped working so now I own a A6 revision. I live in Italy and my carrier is Vodafone. I noticed this (appeared in both hardware revisions): during a call, if the signal strength becomes lower than midrange (looking at the top icon, can't know exactly the level) the buzz appears, while in the middle-high levels I have no buzzing at the other side. Furthermore, when the signal is around the mid range, if I put my hand on the bottom side of the phone (I remember the GSM antenna is located in the arc under the hole) the signal increases a bit its level and the buzz disappears (not always but in a sensible number of situations it does). Maybe the buzz is relative (or not only) to the GSM signal strength so via software is it possible to amplify it or issue some commands to the modem to avoid it? My 2 cents :) Thank you for your great work from a proud Freerunner user ;) Bye! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
El día Monday, September 29, 2008 a las 10:17:49AM +0200, Matthias Apitz escribió: El día Monday, September 22, 2008 a las 11:17:58PM +0200, Matthias Apitz escribió: Hello Stacy, I've stumbled over your page http://www.millions.ca/~stacy/mintyboost/ and as an owner of the FreeRunner I will build this nice box; thanks for your pioneer work on this; ... It seems that here in Germany they don't sell this type of Chewing Gum boxes, the boxes here have other length and width, bigger in width but maybe shorter in length; could someone mail me please the values of length and width in millimeter of the original box to see if the batteries will fit; Hello, A colleague of me was kind enough to build that MintyBoost for me. And it is working fine. I'm attaching a screen shoot of it using 'battery.py'; some questions remain: - sometimes you can hear in the MintyBoost box (not in the FR) some kind of buzzing, is this normal? - sometimes the chip and the electromagnetic coil get very hot, sometimes only warm, anything to worry about? - if the FR battery gets charged by the MintyBoost, the MintyBoost at the same time has also to provide the energy for the running FR, correct? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Q: What's the difference between an iphone and a freerunner? A: One works but takes away your freedom, the other is free but needs your work. attachment: mintyCharging.jpg___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
What about this soft keyboard? http://groups.google.com/group/android-dotphone/ -- Denis On 19/11/2008, at 07:07, Walter Chang wrote: i can't wait till q1 of next year for google to come out with a soft keyboard so i made one. I used the copy-and-paste functionality on Android so the keyboard works with other apps without changing them. to download: http://code.google.com/p/netgents/downloads/list and download qad-keyboard.apk. for instructions on installation and usage: http://code.google.com/p/netgents/wiki/QadKeyboardHowto . enjoy, walter chang -- ...__o ...\, ( )/ ( )... ___ 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: Minty Boost FreeRunner
Matthias Apitz wrote: El día Monday, September 22, 2008 a las 11:17:58PM +0200, Matthias Apitz escribió: Hello Stacy, I've stumbled over your page http://www.millions.ca/~stacy/mintyboost/ and as an owner of the FreeRunner I will build this nice box; thanks for your pioneer work on this; ... Shouldn't it be easy to add this 'wall charger indicator resistor' to the mintyboost circuit? I don't remember where that resistor needs to go, but this can be researched on the wiki... -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
El día Thursday, November 20, 2008 a las 01:47:43PM +0100, Tilman Baumann escribió: Matthias Apitz wrote: El día Monday, September 22, 2008 a las 11:17:58PM +0200, Matthias Apitz escribió: Hello Stacy, I've stumbled over your page http://www.millions.ca/~stacy/mintyboost/ and as an owner of the FreeRunner I will build this nice box; thanks for your pioneer work on this; ... Shouldn't it be easy to add this 'wall charger indicator resistor' to the mintyboost circuit? I don't remember where that resistor needs to go, but this can be researched on the wiki... What would be the bennefit of this? I'm not an electronic guy anymore :-( matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Q: What's the difference between an iphone and a freerunner? A: One works but takes away your freedom, the other is free but needs your work. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
Matthias Apitz wrote: El día Thursday, November 20, 2008 a las 01:47:43PM +0100, Tilman Baumann escribió: Matthias Apitz wrote: El día Monday, September 22, 2008 a las 11:17:58PM +0200, Matthias Apitz escribió: Hello Stacy, I've stumbled over your page http://www.millions.ca/~stacy/mintyboost/ and as an owner of the FreeRunner I will build this nice box; thanks for your pioneer work on this; ... Shouldn't it be easy to add this 'wall charger indicator resistor' to the mintyboost circuit? I don't remember where that resistor needs to go, but this can be researched on the wiki... What would be the bennefit of this? I'm not an electronic guy anymore :-( 1A charging out of the box with no software needed. -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
El día Thursday, November 20, 2008 a las 02:04:22PM +0100, Tilman Baumann escribió: Matthias Apitz wrote: El día Thursday, November 20, 2008 a las 01:47:43PM +0100, Tilman Baumann escribió: Matthias Apitz wrote: El día Monday, September 22, 2008 a las 11:17:58PM +0200, Matthias Apitz escribió: Hello Stacy, I've stumbled over your page http://www.millions.ca/~stacy/mintyboost/ and as an owner of the FreeRunner I will build this nice box; thanks for your pioneer work on this; ... Shouldn't it be easy to add this 'wall charger indicator resistor' to the mintyboost circuit? I don't remember where that resistor needs to go, but this can be researched on the wiki... What would be the bennefit of this? I'm not an electronic guy anymore :-( 1A charging out of the box with no software needed. Here is what the Wiki page says: http://wiki.openmoko.org/wiki/Neo_FreeRunner_Battery «DIY external battery pack from a Minty case Mintyboost: Charge from a couple of AA batteries: Minty Boost!, report on a Neo FreeRunner application. Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Second, the ID pin is in the USB micro connector, so you would either need to put a micro connector on your minty boost (with the correct resistor installed) or use a hacked cable. Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.» My FR switches outomagically to 1A charging mode, but maybe it's better to only use 500mA matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ Q: What's the difference between an iphone and a freerunner? A: One works but takes away your freedom, the other is free but needs your work. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
Matthias Apitz wrote: El día Thursday, November 20, 2008 a las 02:04:22PM +0100, Tilman Baumann escribió: Matthias Apitz wrote: El día Thursday, November 20, 2008 a las 01:47:43PM +0100, Tilman Baumann escribió: Matthias Apitz wrote: El día Monday, September 22, 2008 a las 11:17:58PM +0200, Matthias Apitz escribió: Hello Stacy, I've stumbled over your page http://www.millions.ca/~stacy/mintyboost/ and as an owner of the FreeRunner I will build this nice box; thanks for your pioneer work on this; ... Shouldn't it be easy to add this 'wall charger indicator resistor' to the mintyboost circuit? I don't remember where that resistor needs to go, but this can be researched on the wiki... What would be the bennefit of this? I'm not an electronic guy anymore :-( 1A charging out of the box with no software needed. Here is what the Wiki page says: http://wiki.openmoko.org/wiki/Neo_FreeRunner_Battery «DIY external battery pack from a Minty case Mintyboost: Charge from a couple of AA batteries: Minty Boost!, report on a Neo FreeRunner application. Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. Ups, that's a pitty. I did not anticipate this. Even if the Linear Technology step up voltage converter is supposed to be able to do 600mA, the AA cells seem to have a problem with supplying 500mA. They get a little toasty :-). One powerpack built using D cells doesn't seem to have any issues with supplying 500mA.» Well, Batteries usually put out a great much of current without suffering too much. I could not find any specifications (which of course vary) on a short notice, but I don't think that 5W (plus a little bit loss in the converter) is too much. Maybe we just need to make a heavy duty mintyboost with a bigger converter... My FR switches outomagically to 1A charging mode, but maybe it's better to only use 500mA Probably. The reports of hearing the converter when it is under load support this. -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Denis Galvão wrote: What about this soft keyboard? http://groups.google.com/group/android-dotphone/ This one requires that programs be modified in order to use it. So it can't be used with Android's built-in programs, unless you first modify their source and rebuild them. Walter's keyboard can be used with any program that supports cut paste, although it's obviously not as convenient as a true soft keyboard. Speaking of programs that support cut paste, has anyone managed to paste in an SSID in the Add a Wi-fi network dialog? Jim ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
On Thu, Nov 20, 2008 at 15:14, Matthias Apitz [EMAIL PROTECTED] wrote: Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Yes 1A is a lot. I am not an electronician but would not it be possible to have a little circuit in the minty boost limiting current to 500mA (or other value), even though the freerunner tries to get 1A ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
Cédric Berger wrote: On Thu, Nov 20, 2008 at 15:14, Matthias Apitz [EMAIL PROTECTED] wrote: Adding the 47k resistor to the minty boost so that the Freerunner fast charges at 1A is a poor idea for a couple reasons, the biggest one being that the minty boost can't supply 1A the max is 600mA. as far as I know, there is no magic resistor to identify a 500mA charger to the Freerunner, it depends on USB host telling it that it can provide 500mA. Yes 1A is a lot. I am not an electronician but would not it be possible to have a little circuit in the minty boost limiting current to 500mA (or other value), even though the freerunner tries to get 1A ? Nope. Current is a effect not a cause. *g* -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
Matthias Apitz wrote:
Hello,
A colleague of me was kind enough to build that MintyBoost for me. And
it is working fine. I'm attaching a screen shoot of it using
'battery.py'; some questions remain:
- sometimes you can hear in the MintyBoost box (not in the FR) some kind
of buzzing, is this normal?
According to the MintyBoost FAQ
http://www.ladyada.net/make/mintyboost/faq.html
{ When I plug in a device, sometimes theres a 'hum', 'hiss', 'squeak',
{ 'whine', etc noise...is this normal?
{
{ Yes, sometimes the inductor resonates with the boost converter and
{ that resonance leaks into the audible range. While it's not good for
{ it to always vibrate, it does happen occasionally and is not harmful
{ to the charging device. you can try moving the inductor a little with
{ your finger but the noise is electrical in nature so its hard to stop
{ completely.
{
{ Another thing is that it depends on how much power the device is
{ drawing and what kind of batteries are inside.
- sometimes the chip and the electromagnetic coil get very hot,
sometimes only warm, anything to worry about?
Again, from the FAQ
{ When I use the kit, the chip/batteries seems warm...Is this OK?
{ Its normal for the chip and batteries to be warm or a little hot,
{ especially when charging a device that is nearly drained. The chip
{ should not get hot or very warm when nothing is plugged in.
{
{ However, if the batteries/chip are so hot that its painful to touch,
{ start to smoke, or melt or leak fluidsomething is wrong! :)
Also, your screenshot indicated you are charging at 1A, the step up
voltage converter in the MintyBoost is only capable of 600mA, so that
could explain some of the excess heat and noise.
- if the FR battery gets charged by the MintyBoost, the MintyBoost at
the same time has also to provide the energy for the running FR, correct?
My understanding of the power system on the FR is that some components
draw their power only from the battery even when an external power
source is available. But I am sure there are others on the list with a
more complete understanding of the power system.
-stacy
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Qt Extended] Mapping Demo (was Re: [FSO] Stability and other problems)
Well, I suppouse it may be better and it's more logical to execute the command only when a call connects but I was doing some testing and found that worked better setting the echo supression on every transition :) Guess we should make this configurable, FSO is using -6db, not -12db since this sounds pretty harsh for many people. That's a good idea, but I think the issue may be a bit different. With Qtopia people were reporting no echo for the first call, but echo on subsequent calls. Since we're using an undocumented feature of the modem we don't know under what conditions it might be disabled, even though we don't disable it explicitly. Currently we only set the echo suppression in init, while this patch sets it on every call state transition. It may be worth moving it down a few lines so it only happens when a call connects, but this way we can be certain that echo suppression is enabled for every call. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- View this message in context: http://n2.nabble.com/-FSO--Stability-and-other-problems-tp1479821p1557654.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: Will there be a hardware revision for the buzzing issue?
Joerg Reisenweber wrote: for A7 there's no bugfix changes to expect, except beforementioned big-C rework for buzz issue. There are some minor improvements on audio quality for headset stereo (1u-4.7u). That's no bugfix in the end :-/ Currently we are not planing any hw-fixes for known bugs, that didn't make it to A7 version, means we aren't aware of such bugs that could be fixed for A8. For an eventual A8 we are planning some minor layout changes (3 beads) to make even more sure buzz is gone. (maybe this might also improve situation of buzz while using wired headset for a call. However it's not aimed at that topic) All A5 and A6 versions can be updated to A7 version by cumulative application of the changes done from A5 - A6 - A7 (again that's nothing more than big-C for recent A6) All this to the best of my knowledge, without any warranty ;-) HTH cheers jOERG Please could you update the GTA02 hardware wiki about the newer hardware revisions? Thanks... -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
On Thu, Nov 20, 2008 at 16:10, Tilman Baumann [EMAIL PROTECTED] wrote: Cédric Berger wrote: I am not an electronician but would not it be possible to have a little circuit in the minty boost limiting current to 500mA (or other value), even though the freerunner tries to get 1A ? Nope. Current is a effect not a cause. *g* -- I did not have a look at neo's circuitry. But whatever the method it uses, it cannot force 1A if 1A is not available (wall charger unplugged from the wall won't give 1A :-p ) ? Probably the voltage will have to be dropped so that less current (and/or power) is given to Neo... remains to be seen to what point this can (?) be done with the neo still accepting charging ? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Jim Ancona wrote: Denis Galvão wrote: What about this soft keyboard? http://groups.google.com/group/android-dotphone/ This one requires that programs be modified in order to use it. So it can't be used with Android's built-in programs, unless you first modify their source and rebuild them. Would be patching so hard? I didn't look to the test sources... However here there are some news about this keyboard: - http://dotphone.org/viewthread.php?tid=249 -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
Cédric Berger ha scritto: I did not have a look at neo's circuitry. But whatever the method it uses, it cannot force 1A if 1A is not available (wall charger unplugged from the wall won't give 1A :-p ) ? Uhm...not exactly true... Ohm Law says: V = R * I - I = V/R, and if R-0 then I-oo In practice if you power a load with a little impedance (in real systems the load is not always only resistive) the current requested will grow and the source could be damaged (try to short circuit a normal battery, you'll see a flash and if you maintain the circuit closed you'll meld the battery). This is why you should not ask 1000mA from the USB port (for example) unless you're sure the hardware could give it. Bye :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
On Thu, Nov 20, 2008 at 17:24, DJDAS [EMAIL PROTECTED] wrote: Cédric Berger ha scritto: I did not have a look at neo's circuitry. But whatever the method it uses, it cannot force 1A if 1A is not available (wall charger unplugged from the wall won't give 1A :-p ) ? Uhm...not exactly true... Ohm Law says: V = R * I - I = V/R, and if R-0 then I-oo In practice if you power a load with a little impedance (in real systems the load is not always only resistive) the current requested will grow and the source could be damaged (try to short circuit a normal battery, you'll see a flash and if you maintain the circuit closed you'll meld the battery). This is why you should not ask 1000mA from the USB port (for example) unless you're sure the hardware could give it. Bye :) Yes but I also have some car adapters that did not mind being shorted (12v to 5v adapter, given for 350mA). So I doubt a device wanting 1A would be worst than a short circuit... but what would be the output in such a case I do not know. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Tom R wrote: I'm not familiar with the android environment so here are a couple of questions do I need the android SDK to install this keyboard? if I don't need it then, how do I ssh into android once it's running? I've tried the usual ifconfig usb0 x.x.x.x ssh [EMAIL PROTECTED] but the connection is refused. if i dont need to ssh to install it, then how to do it? regards Tom I thought it was worth mentioning here that adb is also what you need to get a shell on your android-freerunner. ADBHOST=192.168.0.202 adb shell -- View this message in context: http://n2.nabble.com/-Android--Soft-keyboard-tp1518369p1558099.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: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
2008/11/18 The Rasterman Carsten Haitzler [EMAIL PROTECTED] [...] evas supports opengl too. no it doesn't have an advantage, as glamo won't be doing opengl at VGA (the resolution of the device) so you won't be doing it for normal 2D UI's (thus my comments of it being of limited use for some fullscreen games for example where you drop to QVGA for the game). also the 256x256 max texture size leads to problems even if it could do VGA output. Oh this is a definitive limit, I would appreciate 3d acceleration to speedup everyday apps, and not some small 3d games, this is secondary for the freerunner actually. *) when necessary you can use directly Xlib because X is 2d accelerated ? you ALWAYS use xlib* - if you want to interact with x in any way. I mean, if my preferred toolkit does not advantages of hardware acceleration, I may use Xlib and call for example XCopyArea to do fast blits in video memory? I wrote a small code snippet to test XCopyArea performance, and it seems to do about 25fps smoothscrolling but at the cost of XGlamo using 70/80% of CPU. This seems very strange, it maybe my code is wrong (I repeat I'm not an expert :) ), or XCopyArea is not full accelerated, or Xglamo has to be optimized, or that the Glamo GPU is simply slow :) Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Le jeudi 20 novembre 2008 04:49:36 Walter Chang, vous avez écrit :
nope. lets hope the next release from sean fixes that.
I've modified and compiled the Phone application ton answer by pressing the
power (menu) button.
It seems to work in emulator but i don't know how to transfer it to FR since
the rootfs is read-only:
[EMAIL PROTECTED]:~/Documents/neo/mydroid$ /opt/android-sdk/tools/adb install
./out/target/product/generic/system/app/Phone.apk
466 KB/s (733077 bytes in 1.534s)
pkg: /data/local/tmp/Phone.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[EMAIL PROTECTED]:~/Documents/neo/mydroid$ /opt/android-sdk/tools/adb install
-r
./out/target/product/generic/system/app/Phone.apk
465 KB/s (733077 bytes in 1.539s)
pkg: /data/local/tmp/Phone.apk
Failure [INSTALL_FAILED_REPLACE_COULDNT_DELETE]
Does anybody know if i can make the rootfs rw to allow change system apps?
Thanks
Yann
Ho and the modification i've made is in
packages/apps/Phone/src/com/android/phone/CallNotifier.java.
I've just modified line 969:
} else if (keyCode == KeyEvent.KEYCODE_CALL || keyCode ==
KeyEvent.KEYCODE_MENU ) {
in public boolean onKeyUp(int keyCode, KeyEvent event) method ...
Really quick and dirty but just a test to know if i'm able to personnalize
it.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
On Thu, 20 Nov 2008 20:41:13 +0100
Yann neveu [EMAIL PROTECTED] (YN) wrote:
Le jeudi 20 novembre 2008 04:49:36 Walter Chang, vous avez écrit :
nope. lets hope the next release from sean fixes that.
I've modified and compiled the Phone application ton answer by
pressing the power (menu) button.
It seems to work in emulator but i don't know how to transfer it to FR
since the rootfs is read-only:
[EMAIL PROTECTED]:~/Documents/neo/mydroid$ /opt/android-sdk/tools/adb
install ./out/target/product/generic/system/app/Phone.apk
466 KB/s (733077 bytes in
1.534s)
pkg: /data/local/tmp/Phone.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
[EMAIL PROTECTED]:~/Documents/neo/mydroid$ /opt/android-sdk/tools/adb
install -r ./out/target/product/generic/system/app/Phone.apk
465 KB/s (733077 bytes in 1.539s)
pkg: /data/local/tmp/Phone.apk
Failure [INSTALL_FAILED_REPLACE_COULDNT_DELETE]
Does anybody know if i can make the rootfs rw to allow change system
apps?
Thanks
Yann
Ho and the modification i've made is in
packages/apps/Phone/src/com/android/phone/CallNotifier.java.
I've just modified line 969:
} else if (keyCode == KeyEvent.KEYCODE_CALL || keyCode ==
KeyEvent.KEYCODE_MENU ) {
in public boolean onKeyUp(int keyCode, KeyEvent event) method ...
Really quick and dirty but just a test to know if i'm able to
personnalize it.
This sounds great! You can boot another distro from the uSD card and
then mount the root rw:
mount -t jffs2 /dev/mtdblock6 /media/cf
Petr
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Yann neveu wrote: Does anybody know if i can make the rootfs rw to allow change system apps? adb remount is supposed to do it, but doesn't seem to work on my device. Instead, it returns remount failed: Unknown error: 0. Besides the suggestion of booting another distro from SD and updating the rootfs, you can also follow the instructions at http://wiki.openmoko.org/wiki/Userspace_root_image to create a new rootfs and then flash the device with it. Not a simple process, I know. Jim ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Le jeudi 20 novembre 2008 21:01:48 Petr Vanek, vous avez écrit : This sounds great! You can boot another distro from the uSD card and then mount the root rw: mount -t jffs2 /dev/mtdblock6 /media/cf Ok, have to prepare a distro on sd card so, thanks. The Phone.apk is here: http://gabuzomeu.fr/openmoko/Phone.apk Don't know if it's work, i think it should answer AND open the menu... Anyway, backup before use Yann ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Is there any kind of network manager?
Hi! As in the subject - is there any connection manager available for Freerunner to switch and manage between WiFi, GPRS and usb? I've seen connection manager in Illume, but it seems to be empty. What is left to implement to get it working? Are there any alternatives? It's possible to connect to WiFi with command line or mofi, to GPRS with simple script, but maybe there is something better already? Are there any particular plans for network management? Leonti ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Minty Boost FreeRunner
Cédric Berger wrote: On Thu, Nov 20, 2008 at 17:24, DJDAS [EMAIL PROTECTED] wrote: Cédric Berger ha scritto: I did not have a look at neo's circuitry. But whatever the method it uses, it cannot force 1A if 1A is not available (wall charger unplugged from the wall won't give 1A :-p ) ? Uhm...not exactly true... Ohm Law says: V = R * I - I = V/R, and if R-0 then I-oo In practice if you power a load with a little impedance (in real systems the load is not always only resistive) the current requested will grow and the source could be damaged (try to short circuit a normal battery, you'll see a flash and if you maintain the circuit closed you'll meld the battery). This is why you should not ask 1000mA from the USB port (for example) unless you're sure the hardware could give it. Bye :) Yes but I also have some car adapters that did not mind being shorted (12v to 5v adapter, given for 350mA). So I doubt a device wanting 1A would be worst than a short circuit... but what would be the output in such a case I do not know. According to the MAX756 datasheet (the step-up converter used in the minty boost AFAICS), the switching mosfet should be protected due to the operating principle: The coil is shorted to ground until the current reaches about 1A, then switched off automatically (and then the coil discharges in series to the battery, effectively boosting the voltages). So the only things relevant to a overload situation are the coil rating and the diode rating. If both are capable of handling 1A continously, then switching the Freerunner to 1A can't break anything. The 1N5818 can handle 1A and the coil used has a saturation current of 1.5A. (However, it is _not_ short-circuit-proof, since in that case the current would flow directly from the battery over coil and diode to ground and will likely destroy the diode first) Switching noise is nothing to worry about (Switching frequency depends on load and battery voltage). Of course thermal dissipation can still be an issue. HTH, -- Tobias PGP: http://9ac7e0bc.uguu.de このメールは十割再利用されたビットで作られています。 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [FSO] First steps
Le mercredi 19 novembre 2008 à 13:39 -0800, VirtuAlex a écrit : I had similar problem. I pushed the button and nothing happened, then I tried to push it again, but before I did, it actually started suspending (got into text mode, some lines started pass by). So the second press obviously interrupted normal suspend routine and put FR into unusable state. Only removing battery helps. I can reproduce it. But if I press power button once and wait for it to suspend properly, next short press wakes it up reliably. I changed my kernel to mwester's and I can resume with POW now. But illume's settings names seem to be misleading : Blank time is blank time susped time is lock time ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Thu, 20 Nov 2008 19:00:02 +0100 Nicola Mfb [EMAIL PROTECTED] babbled: 2008/11/18 The Rasterman Carsten Haitzler [EMAIL PROTECTED] [...] evas supports opengl too. no it doesn't have an advantage, as glamo won't be doing opengl at VGA (the resolution of the device) so you won't be doing it for normal 2D UI's (thus my comments of it being of limited use for some fullscreen games for example where you drop to QVGA for the game). also the 256x256 max texture size leads to problems even if it could do VGA output. Oh this is a definitive limit, I would appreciate 3d acceleration to speedup everyday apps, and not some small 3d games, this is secondary for the freerunner actually. *) when necessary you can use directly Xlib because X is 2d accelerated ? you ALWAYS use xlib* - if you want to interact with x in any way. I mean, if my preferred toolkit does not advantages of hardware acceleration, I may use Xlib and call for example XCopyArea to do fast blits in video memory? you can. I wrote a small code snippet to test XCopyArea performance, and it seems to do about 25fps smoothscrolling but at the cost of XGlamo using 70/80% of CPU. This seems very strange, it maybe my code is wrong (I repeat I'm not an expert :) ), or XCopyArea is not full accelerated, or Xglamo has to be optimized, or that the Glamo GPU is simply slow :) it's accelerated - but likely polling the command queue status as you have no interrupts thanks to the linux kernel's policy of not exporting interrupts to userspace, so you're stuck with a poll loop. i can't remember if glamo had a i'm done interrupt for the command queue or operations - i know it had several interrupts it can generate (but as the kernel wouldnt allow userspace to make use of them i pretty much ignored them). -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Fast screen rotate app
Hi, i've used FDOM(great distro) for just a while and the only thing I didn't like was the really slow rotate app. So here is a slightly faster one. The source is in a bazaar repository. It can be get from here: https://turmspitze.org/pubbzr/rotate I will build binaries on request. Have fun! Moritz ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Android] Soft keyboard
Le jeudi 20 novembre 2008 21:23:33 Yann neveu, vous avez écrit : Le jeudi 20 novembre 2008 21:01:48 Petr Vanek, vous avez écrit : This sounds great! You can boot another distro from the uSD card and then mount the root rw: mount -t jffs2 /dev/mtdblock6 /media/cf ok, i've installed a fresh om-testing on card ( nicer than ever ) and modified init.rc to mount rootfs rw. Copied Phone.apk in /system/app/Phone.apk, rebooted and... placed a call to myself. I've successfully answered using power button. So, seems to work :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
Hi, On Fri, Nov 21, 2008 at 09:16:15AM +1100, Carsten Haitzler wrote: On Thu, 20 Nov 2008 19:00:02 +0100 Nicola Mfb [EMAIL PROTECTED] babbled: I wrote a small code snippet to test XCopyArea performance, and it seems to do about 25fps smoothscrolling but at the cost of XGlamo using 70/80% of CPU. This seems very strange, it maybe my code is wrong (I repeat I'm not an expert :) ), or XCopyArea is not full accelerated, or Xglamo has to be optimized, or that the Glamo GPU is simply slow :) it's accelerated - but likely polling the command queue status as you have no interrupts thanks to the linux kernel's policy of not exporting interrupts to userspace, so you're stuck with a poll loop. i can't remember if glamo had a i'm done interrupt for the command queue or operations - i know it had several interrupts it can generate (but as the kernel wouldnt allow userspace to make use of them i pretty much ignored them). ??? What's wrong with: interrupt handler - wait queue - file operations read/poll? Greetings, Sascha ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Fri, 21 Nov 2008 02:18:25 +0100 Sascha Wessel [EMAIL PROTECTED] babbled: Hi, On Fri, Nov 21, 2008 at 09:16:15AM +1100, Carsten Haitzler wrote: On Thu, 20 Nov 2008 19:00:02 +0100 Nicola Mfb [EMAIL PROTECTED] babbled: I wrote a small code snippet to test XCopyArea performance, and it seems to do about 25fps smoothscrolling but at the cost of XGlamo using 70/80% of CPU. This seems very strange, it maybe my code is wrong (I repeat I'm not an expert :) ), or XCopyArea is not full accelerated, or Xglamo has to be optimized, or that the Glamo GPU is simply slow :) it's accelerated - but likely polling the command queue status as you have no interrupts thanks to the linux kernel's policy of not exporting interrupts to userspace, so you're stuck with a poll loop. i can't remember if glamo had a i'm done interrupt for the command queue or operations - i know it had several interrupts it can generate (but as the kernel wouldnt allow userspace to make use of them i pretty much ignored them). ??? What's wrong with: interrupt handler - wait queue - file operations read/poll? the policy of the kernel developers is not to export interrupts to usersapce in a generic way - or it hasn't been in the past. this may have changed recently. so u can patch and create a specific driver just for glamo just to export an interrupt - and it'll never go upstream most likely, and the kernel supports no generic hook to an interrupt from userspace. one way or another something will block your path (be it getting patches upstream back to mainline kernel or just living without interrupts etc.). this is last i checked. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
Hi, On Fri, Nov 21, 2008 at 12:28:44PM +1100, Carsten Haitzler wrote: the policy of the kernel developers is not to export interrupts to usersapce in a generic way - or it hasn't been in the past. this may have changed recently. so u can patch and create a specific driver just for glamo just to export an interrupt - and it'll never go upstream most likely, and the kernel supports no generic hook to an interrupt from userspace. one way or another something will block your path (be it getting patches upstream back to mainline kernel or just living without interrupts etc.). this is last i checked. I have never tried it but userspace i/o [1] is a more or less generic way to export interrupts to userspace (in the kernel since ~2.6.23). Greetings, Sascha [1] http://www.kernel.org/doc/htmldocs/uio-howto/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Fri, 21 Nov 2008 04:11:58 +0100 Sascha Wessel [EMAIL PROTECTED] babbled: Hi, On Fri, Nov 21, 2008 at 12:28:44PM +1100, Carsten Haitzler wrote: the policy of the kernel developers is not to export interrupts to usersapce in a generic way - or it hasn't been in the past. this may have changed recently. so u can patch and create a specific driver just for glamo just to export an interrupt - and it'll never go upstream most likely, and the kernel supports no generic hook to an interrupt from userspace. one way or another something will block your path (be it getting patches upstream back to mainline kernel or just living without interrupts etc.). this is last i checked. I have never tried it but userspace i/o [1] is a more or less generic way to export interrupts to userspace (in the kernel since ~2.6.23). this is relatively new. :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
Lally, how long is OM going to be using the Glamo? The glamo will be kept for the lifetime of gta02, i.e. every gta02 will have the glamo chip. For gta03, release date unknown, the decision is to not have a glamo, we use the acceleration of the SoC. The GTA02's been on the brink of obsolescence since the day it was introduced. Don't agree with you. In the long run everything is obsolete. GTA02 is a real pioneering device for Linux in mobile phones, and is still advancing the state of Free Software in mobile phones in many areas. We owe the community better hardware, and have made decisions internally to only focus on hardware and lower-level software. But that will not remove the pioneering status of GTA02, not even when GTA03 ships, again release date unknown at this point. It can't even take most modern (3G) SIMs. Thanks to great work from Dieter, Joerg and Werner, this bug (trac #666) seems to be fixed now, GSM reflash utility and instructions are available, etc. Next they target trac #1024 (network re-registration). If the Glamo (or something compatible) is going to be around for a while, either in a long production life of the GTA02, or in newer phones, Long production life of GTA02. Hence, my earlier suggestion on just using the acceleration for some Gtk operations. Small, effective changes. Get that done to make the device feel responsive. If someone wants to do the big OpenGL implementation later, fine, use this Gtk work as a sandbox for getting a feel for the device. Very good idea. I always prefer breaking a large idea into smaller pieces. $400 for a phone is a reasonable investment. But months of work in one's spare time is much bigger. Before anyone commits to a large-scale project, I think it's fair to ask OM what their plans are with this chip. Absolutely. I have already answered many aspects in other mails, but let me summarize again: 1. We currently are disappointed about s-media. To be fair to them I do not want to quote from contracts we have with them, but let me tell you at the bottom line we feel there have been some broken promises with regards to opening documentation. 2. Because of this situation, we decided to not use s-media chips in future Openmoko products. 3. At the same time, we decided to not come out with GTA02 versions that had the glamo removed, because that would have been hard to do technically, and it would have created too much technical fragmentation. 4. Even with raster's bashing, the glamo chip is a really nice mobile graphics chip. I say this also considering when it was released. Openmoko's speed of progress still does not match industry speed. While the other (closed) chip vendors are already 2 generations ahead, we (Openmoko and the Free Software community) are still writing drivers for older chips. But we shouldn't let others distract us. Our software is 100% Free Software. We want to be able to install mainline kernel.org kernels one day. We want to be able to run many Linux distributions on the phone one day. We are coming from behind, but I'm sure with the help of the community we can even drag something like the glamo out into the open. 5. We will have the same problem with open 2D/3D acceleration again in the future, so breaking the glamo free could be considered a good 'exercise'. No matter whether you look at future Samsung, TI, Marvell chips. The 3D acceleration part is always closed. In other words needs to be opened by us. We might as well start with the glamo now, better than waiting for the 'perfect moment' which will never come... Best Regards, Wolfgang On Nov 17, 2008, at 3:40 PM, Lally Singh wrote: Well then, Therein lies the question, how long is OM going to be using the Glamo? There's apparently some real potential in the device, but that's really measured as much by the chip's relevance as its functionality. The GTA02's been on the brink of obsolescence since the day it was introduced. It can't even take most modern (3G) SIMs. If the Glamo (or something compatible) is going to be around for a while, either in a long production life of the GTA02, or in newer phones, then all this makes sound engineering sense to work on. Otherwise, I have real doubts about the longevity of a software project aggressive enough to attempt major work (e.g. accellerated OpenGL) on this chip. Lots of open source projects start off with a bang of enthusiasm, and die with a whimper. If the chip's gone in a few months, I don't think we'll see the project survive. Hence, my earlier suggestion on just using the acceleration for some Gtk operations. Small, effective changes. Get that done to make the device feel responsive. If someone wants to do the big OpenGL implementation later, fine, use this Gtk work as a sandbox for getting a feel for the device. $400 for a phone is a reasonable investment. But months of work in one's spare
Re: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
On Fri, 21 Nov 2008 11:59:42 +0800 Wolfgang Spraul [EMAIL PROTECTED] babbled: Lally, how long is OM going to be using the Glamo? The glamo will be kept for the lifetime of gta02, i.e. every gta02 will have the glamo chip. For gta03, release date unknown, the decision is to not have a glamo, we use the acceleration of the SoC. The GTA02's been on the brink of obsolescence since the day it was introduced. Don't agree with you. In the long run everything is obsolete. i think he is referring to using an old soc, old gfx chip etc. something that has been out for many years - where the competition (not in open phones, but in phones in general) is busy building new devices on chips not yet in mass production as they follow the curve and by the time it is in production - their device is ready. it's perfectly understandable why openmoko is building on an old platform - but it still makes the hardware very much behind the curve :) GTA02 is a real pioneering device for Linux in mobile phones, and is still advancing the state of Free Software in mobile phones in many areas. We owe the community better hardware, and have made decisions internally to only focus on hardware and lower-level software. But that will not remove the pioneering status of GTA02, not even when GTA03 ships, again release date unknown at this point. It can't even take most modern (3G) SIMs. Thanks to great work from Dieter, Joerg and Werner, this bug (trac #666) seems to be fixed now, GSM reflash utility and instructions are available, etc. Next they target trac #1024 (network re-registration). If the Glamo (or something compatible) is going to be around for a while, either in a long production life of the GTA02, or in newer phones, Long production life of GTA02. Hence, my earlier suggestion on just using the acceleration for some Gtk operations. Small, effective changes. Get that done to make the device feel responsive. If someone wants to do the big OpenGL implementation later, fine, use this Gtk work as a sandbox for getting a feel for the device. Very good idea. I always prefer breaking a large idea into smaller pieces. one thing everyone seems to think that is wrong. this gtk acceleration is already done. blits, fills. xvideo too. :) aa text isn't possible as the glamo doesn't meet xrender specs for doing aa text, so it's software or bust (unless you upload ARGB glyphs and pre-colour them. the end result will be slower rendering that current software - that's my bet). so you are about as good as it gets - acceleration-wise for gtk (2d). only thing that could be done is some basic xrender accel (composite ARGB32 src to rgb565 dest if src and dest 640x640). and that also involves having to have uploaded the ARGB32 pixel source first - which is double the bandwidth needs of 16bit... across the bus to the glamo (thus why i originally was so focused on trying to squeeze more out of that bus - that is a real killer). so right now other than bugs and trying to minimise cpu overhead on handling the commandqueue 2d is done - it's not getting faster. only thing left is 3d. and that comes with a long list of gotchas. this is the bit where someone needs to make a call on what is the effort needed, and the result. this is up to openmoko to decide what to do as the docs are in their hands. 2d is pretty much done. :) $400 for a phone is a reasonable investment. But months of work in one's spare time is much bigger. Before anyone commits to a large-scale project, I think it's fair to ask OM what their plans are with this chip. Absolutely. I have already answered many aspects in other mails, but let me summarize again: 1. We currently are disappointed about s-media. To be fair to them I do not want to quote from contracts we have with them, but let me tell you at the bottom line we feel there have been some broken promises with regards to opening documentation. 2. Because of this situation, we decided to not use s-media chips in future Openmoko products. 3. At the same time, we decided to not come out with GTA02 versions that had the glamo removed, because that would have been hard to do technically, and it would have created too much technical fragmentation. 4. Even with raster's bashing, the glamo chip is a really nice mobile it's a professional opinion based on what i have seen in my years of doing graphics. i think it's a very very weak graphics chip with lots of missing holes in its featureset - given the kind of screen attached to it and the OS and windowing system as well as the goals and desires of users. if you take the OS and windowing system and goals as a given, the weak point is the glamo. a spade is a spade. :) you can cover it with topping all you like. :) graphics chip. I say this also considering when it was released. indeed. when it was released it was good. but that was long ago. i agree here. in the
Re: Buzzing (was :The forbidden topic: Glamo OpenGL)
Timo, You will find echo fixed in Openmoko's 2008.11 release, if you keep using the Openmoko distro, and responsiveness and touch screen usability will also improve with 2008.11 release. End call / accept You are right that people are working on these things and fixes appear. However, please don't expect a real Om 2008.11 'release' before the end of the month. There is simply too much progress in all areas right now, we need a bit more time for everything to settle before calling something another 'release'. Maybe a few months. Maybe we come out with snaphost in between, similar to FSO's milestone builds. If someone proves me wrong then great, I am just telling you please keep your Om 2008.11 release expectations low. Wolfgang On Nov 17, 2008, at 6:35 PM, Timo Jyrinki wrote: 2008/11/14 Gothnet [EMAIL PROTECTED]: It really needs work on the basics. I mean, responsiveness is not there, interface is dodgy (the end call button being in the same spot as the accept call button, and being unresponsive, made me hang up s many calls). Echo on calls, battery life... These are all small issues as such, as they are all on the software side and many have been either fixed or are different on different distributions (you don't need to use Openmoko's distribution - you can use Debian, Qt Extended, SHR, ...). You will find echo fixed in Openmoko's 2008.11 release, if you keep using the Openmoko distro, and responsiveness and touch screen usability will also improve with 2008.11 release. End call / accept call stuff are just UI things, easy to fix, but maybe you should file a bug report about it since otherwise no-one might notice. The buzzing issue is the only real, serious issue. Also, I know everyone loves X, but is it really the best choice for a low powered device that needs a responsive UI? Yes :) Any unresponsiveness in the UI is not because of the X. I think maybe I had the wrong impression about the state of the software when I bought it. Probably. It's not a phone product yet, it's a phone in development. From your point of view I can understand the frustration with the other issues, but for me they are just a few things to work on / test fixes. The buzzing / hw issue is really the only thing I'm worried about, since it needs to be fixed and there is no known software fix for it yet. -Timo ___ 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: Calling interested Glamo OpenGL developers (was: The forbidden topic: Glamo OpenGL)
Wolfgang, Raster: On Thu, Nov 20, 2008 at 11:28 PM, The Rasterman Carsten Haitzler [EMAIL PROTECTED] wrote: The GTA02's been on the brink of obsolescence since the day it was introduced. Don't agree with you. In the long run everything is obsolete. i think he is referring to using an old soc, old gfx chip etc. something that has been out for many years - where the competition (not in open phones, but in phones in general) is busy building new devices on chips not yet in mass production as they follow the curve and by the time it is in production - their device is ready. it's perfectly understandable why openmoko is building on an old platform - but it still makes the hardware very much behind the curve :) I suspect the Glamo was designed for a much less sophisticated setup, with a lower-res screen and probably a slower CPU. Hence the texture sizes and I/O speed limitations -- choices made for cost power. snip If the Glamo (or something compatible) is going to be around for a while, either in a long production life of the GTA02, or in newer phones, Long production life of GTA02. I'm all for longer production lives. But, IMHO in the next incarnation, some more thought to a longer useful life should be given. Specifically, a few more ports on the device are necessary to keep its useful life long. LInuxer's will add drivers for new devices as they come, extending the life of the device, but we need I/O. Additionally, the components chosen shouldn't be as overtaxed from the beginning as the glamo. Only after the driving software has been written does a team find out the real limitations of the device. Started from a burdened position usually only leads downward after trying to get aggressive on the software side. IMHO 3D was/is a great idea, so I can't blame OM for trying with the glamo. But there are alwasy some lessons to come out any development effort. Finally, the next device should have stable support for basic phone operation when it's released: suspend, resume, calling, and answer-while-suspended. Without that, it's hard to get the imagination going for what else to do with the phone. The GTA02's release should have been in two phases for hackers and users. The former as it was, the latter after those functions were stable. If that's not possible for the GTA03, then a two-phase release is appropriate for it, too. The nice consequence of it is that it brings in larger community participation of the device's commercial lifecycle, which will lead to a better feeling of community ownership over it. I admit I was quite embarrassed to show the device off upon reception, considering how really raw it was. I'm happy with the results of the optimization team, and it looks like OM's going the right way now. But it was quite painful for too long, and shouldn't be repeated. Hence, my earlier suggestion on just using the acceleration for some Gtk operations. Small, effective changes. Get that done to make the device feel responsive. If someone wants to do the big OpenGL implementation later, fine, use this Gtk work as a sandbox for getting a feel for the device. Very good idea. I always prefer breaking a large idea into smaller pieces. one thing everyone seems to think that is wrong. this gtk acceleration is already done. blits, fills. xvideo too. :) snip so right now other than bugs and trying to minimise cpu overhead on handling the commandqueue 2d is done - it's not getting faster. only thing left is 3d. and that comes with a long list of gotchas. this is the bit where someone needs to make a call on what is the effort needed, and the result. this is up to openmoko to decide what to do as the docs are in their hands. 2d is pretty much done. :) As Raster's already pushed hard on Glamo acceleration, and I know he's quite capable (I was an old enlightenment WM user back in the day), I consider the glamo issue closed. We're stuck with what we have, and simply have to find ways to be efficient with what what's already there. 1. We currently are disappointed about s-media. To be fair to them I do not want to quote from contracts we have with them, but let me tell you at the bottom line we feel there have been some broken promises with regards to opening documentation. 2. Because of this situation, we decided to not use s-media chips in future Openmoko products. 3. At the same time, we decided to not come out with GTA02 versions that had the glamo removed, because that would have been hard to do technically, and it would have created too much technical fragmentation. 4. Even with raster's bashing, the glamo chip is a really nice mobile That isn't stuff you could've known before committing this far. I'm sorry it happened to a platform I like so much. I support your decision of keeping it in, otherwise you'd lose a lot of your community. Nobody likes buying an iPod the day before the new ones come out. 3D was the right way
