Re: Some light ahead...
On Wednesday 25 April 2007 01:51:45 Sean Moss-Pultz wrote: Oh and Imre Kaloz gets a freed phone, too. Thanks for being the first to tell us about Atheros. We're almost for sure going to use their AR6K chipset in our next product. I just have to ask: is there any broad schedule / specs for the P1.5 phone already? pgpazAnfGwp8H.pgp Description: PGP signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Some light ahead...
On Wed, 2007-04-25 at 08:26 +0200, Gabriel Ambuehl wrote: On Wednesday 25 April 2007 01:51:45 Sean Moss-Pultz wrote: Oh and Imre Kaloz gets a freed phone, too. Thanks for being the first to tell us about Atheros. We're almost for sure going to use their AR6K chipset in our next product. I just have to ask: is there any broad schedule / specs for the P1.5 phone already? Not yet. We're still working on the schematics. When things get finalized I'll make another announcement. -Sean ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Some light ahead...
Thank you so much for the update! I was frantically searching for HW since i heard it would be available in March and thought i was missing out. Glad to know i didn't miss the boat! This is also my first post to the list - i've been reading as many as i can since joining about a week ago. Also hoping to be of service to the community! I skimmed a thread regarding GPS in the phone - I haven't looked up the datasheet for the chipset being used, but I know many GPS chips spout NMEA-183 messages. I have some old C routines i wrote about 10 yrs ago for parsing NMEA-183 protocol - if anybody thinks they'd be of use i can dust 'em off and submit them. Thanks again for setting up such a fantastic project! --clayton On 4/24/07, Sean Moss-Pultz [EMAIL PROTECTED] wrote: Dear Community, We owe you all an update as to our status. Here it goes... Last week we finished 200 devices. Of these about 50 seem to have some problems but the rest are functionally complete, tested, and ready to go. We know the source of the problems for the 50 that failed and this is already corrected. This is great news because it means we can finally start to move out of engineering sample mode and into real production! These first 150 (or so) devices will go to phase 0 developers and our internal / external developers -- of which many still don't even have phones! Oh and Imre Kaloz gets a freed phone, too. Thanks for being the first to tell us about Atheros. We're almost for sure going to use their AR6K chipset in our next product. We must forewarn you all that we're having some supply issues with our 2.8 VGA LCM. Our vendor has had more than their fair share of troubles moving this LCM into mass production. We have some in stock now. But this might be the major bottleneck moving forward. There are only a few companies currently making LCMs of this size and resolution. Finally, we've already begun moving production into one of our factories in mainland China. There are two runs scheduled now: May 10th and May 20th. We're going to take those runs a bit slow just to make sure the quality is high. And then starting in June, things can run full speed. Thanks again for your continued support and patience. The light at the end of the tunnel is getting a little brighter :-) Sincerely, The Core Team ___ 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: Some light ahead...
On 11000 March 1977, Sean Moss-Pultz wrote: We owe you all an update as to our status. Here it goes... Great news, thanks. -- bye Joerg _DeadBull_ ohne speicher, tastatur, mouse, pladde, monitor, also nur die Hardware... ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Audio Jack 2.5 mm
Vladimi'r Lapa'c(ek wrote: Interesting thing to consider is how many people would like to use the headset and how many would it use for playing music. Wired connection usually preferred by those who listens to music.Others are often using bluetooth since it is more convenient (no wires).Usually I can see people with wired headsets only if 1)Wired headset was supplied with device by vendor and owner is too lazy to buy something else. 2)or owner likes music, bluetooth is not an option here due to lack of a2dp support by devices and quite low quality of headsets. As for me, I will prefer to listen to music on my phone (I'm already do and will do in future, that's just convenient).And yes, I will have headache with buying 2.5 to 3.5 mm jack converter since handsets with 2.5 mm jack are pretty low-quality and only suitable for calls (and for just calls, bluetooth is more convenient option). My estimate is much bigger for the second, but it may be pretty much skewed. Using an adapter might be an option but not for mainstream (I know, the phone is not mainstream). These adapters are popular up to some degree due to some portable devices using 2.5 mm jacks, but still this adds some headache with finding such adapter.That's not fair, at least for me. P.S. but 3.5 mm sockets are bigger than 2.5 mm ones - this may be an issue for small portable devices. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Audio Jack 2.5 mm
On Wednesday 25 April 2007 11:21:05 t3st3r wrote: These adapters are popular up to some degree due to some portable devices using 2.5 mm jacks, but still this adds some headache with finding such adapter.That's not fair, at least for me. You mean like the trouble of going to ebay and order one? From what I understand, Motorola V360 adapters will work (which might well be true, they look identical at least) and those are really cheap and widely available. pgpp1gwzOBqpl.pgp Description: PGP signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Widgets: Openmoko/Chumby transproject?
Florent THIERY writes: If you're about Macromedia Flash (er, now Adobe), isn't it closed source? The neo has a closed source real time OS running the GSM part... OS? It's been said pretty consistently that it's a user-mode daemon. Still one more piece of closed source software than I like to see, but not an OS. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Widgets: Openmoko/Chumby transproject?
I think Florent's point is that your argument is moot; You can rant an rave all you want but at the end of the day functionality is more important than all open source. Likewise there are going to be commercial applications developed on this handset as it's not fairy land open source world but a commercial project being developed here. I think the less religious arguments here the better this project will beif you don't like it go and write your own gsm stack and then release it for the community to use. Regards, Dean Collins Cognation Pty Ltd [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] +1-212-203-4357 Ph +61-2-9016-5642 (Sydney in-dial). http://click.mexuar.com/webuser/click/7/userurl/Cognation http://click.mexuar.com/webuser/nojs/7/userurl/Cognation -Original Message- From: [EMAIL PROTECTED] [mailto:community- [EMAIL PROTECTED] On Behalf Of Joe Pfeiffer Sent: Wednesday, 25 April 2007 10:24 AM To: community@lists.openmoko.org Subject: Re: Widgets: Openmoko/Chumby transproject? Florent THIERY writes: If you're about Macromedia Flash (er, now Adobe), isn't it closed source? The neo has a closed source real time OS running the GSM part... OS? It's been said pretty consistently that it's a user-mode daemon. Still one more piece of closed source software than I like to see, but not an OS. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community image001.gif Description: image001.gif ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Widgets: Openmoko/Chumby transproject?
On ke, 2007-04-25 at 08:23 -0600, Joe Pfeiffer wrote: Florent THIERY writes: If you're about Macromedia Flash (er, now Adobe), isn't it closed source? The neo has a closed source real time OS running the GSM part... OS? It's been said pretty consistently that it's a user-mode daemon. He's talking GSM, not GPS. The GSM chip indeed has its own proprietary OS. However, that's IMAO a special case and very different from any user-mode software on the SOC side. We want an open GNU/Linux system on this phone. It would be _nice_ to have an open GSM system as well, but not possible at this point. The GSM part is nicely encapsulated as an integrated peripheral providing a standard API. As such it's not of as much openness interest to the application developers and users as the base GNU/Linux OS with its application libraries is. Heck, apparently even Stallman only had a problem with the GPS plugin. -- Mikko J Rauhala [EMAIL PROTECTED] University of Helsinki ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Widgets: Openmoko/Chumby transproject?
Dnia środa, 25 kwietnia 2007, Joe Pfeiffer napisał: The neo has a closed source real time OS running the GSM part... OS? It's been said pretty consistently that it's a user-mode daemon. Still one more piece of closed source software than I like to see, but not an OS. Closed source daemon will be for GPS. GSM modem has own OS inside (firmware) which is closed and will not open due to NDA. -- JID: hrw-jabber.org OpenEmbedded developer/consultant Cats are like people: the females are the prickly ones and the males are good-natured idiots. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Widgets: Openmoko/Chumby transproject?
Dean Collins пишет: but at the end of the day functionality is more important than all open source. No it's not; why am I waiting for this device instead of buying Windows one? ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Fwd: Widgets: Openmoko/Chumby transproject?
-- Forwarded message -- From: J F [EMAIL PROTECTED] Date: Apr 24, 2007 11:03 PM Subject: Re: Widgets: Openmoko/Chumby transproject? To: t3st3r [EMAIL PROTECTED] On 24/4/07 8:23 pm, t3st3r [EMAIL PROTECTED] wrote: Florent THIERY wrote: Disclaimer: in no way I'm any official or whatever - I'm just a subscriber of this list like you.All following thing is just a my own private opinition.Other recipients or officials may feel this in slightly another way. As we can see, the neo and the chumby have a lot in common, be it ideas, hardware specs or even leaders ;) Yes, it uses flash7 for widgets. Which has'nt even been considered in the openmoko case... But what if the two projects shared the widget aspect? If you're about Macromedia Flash (er, now Adobe), isn't it closed source? There's gnash - www.gnashdev.org I'm stated my point of view.Personally, I will never buy open phone where UI toolkit is heavily based on closed source thing and requiring me to buy proprietary Adobe app to create\change UI parts.That's hardly in open source spirit. I do believe there are open source apps to create flash files, however, I'm no expert on the subject and am too lazy to hunt for links right now :p maybe someone who's had experience on this side of things could say something on their quality. Also, flash based UIs I seen while looking good are quite slow and jerky even on powerful (and power consuming) desktop machines so they're hardly usable.Of course this is my own private opinition and it is safe to ignore it. There are some youtube vids of the prototype chumby in action where it doesn't look too sluggish - it has similar specs to the p1 fic1973, however it is running an adobe closed source flash player that may be faster than gnash. I personally like the idea of having a ui that is designable by people who work on websites who have more design skills than the average c haxxor... Combined with an onboard webserver, one could do some fun things like transplant the phone's ui to whatever full computer you have handy. It would be fun to run some chumby things on the fic but I would imagine *JUST* having a flash ui might be limiting for some projects - as a musician I would dread using a flash metronome, it would never have the timing of gtick. ___ 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: Some light ahead...
Duncan Hudson wrote: Sean Moss-Pultz wrote: Finally, we've already begun moving production into one of our factories in mainland China. There are two runs scheduled now: May 10th and May 20th. We're going to take those runs a bit slow just to make sure the quality is high. And then starting in June, things can run full speed. I'm as anxious as anyone to get my hands on one of these, but it just concerns me that the date has slipped again. With each slip the competition gets closer and closer. Openmoko has been compared, favorably, by many sources to the iPhone - and it was originally scheduled to ship months before that device. Now we're talking about shipping after the iPhone, so the bar that you have to clear will have been raised considerably. 1) the Openmoko-for-customers is slated for 9/11/07, so it was going to ship after the Q207 date for the iPhone in any case. 2) the iPhone may slip too. Its all the rumor in the Apple world these days. We already know that Apple has slipped its next OS release (10.5) because it put some large number of its OS folks on the iPhone project, in order to get it out the door. Most of us understand that adding people to a slipping project typically makes it slip harder. 3) the iPhone is being sold (in the US) through ATT/Cingular's channels, which are deep and wide. Getting a consumer to the iPhone will be easy. Getting that same individual to an OpenMoko phone will be much more difficult. 4) Relax... you're not going to be able to add features to an iPhone. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Widgets: Openmoko/Chumby transproject?
I do believe there are open source apps to create flash files, however, I'm no expert on the subject and am too lazy to hunt for links right now :p maybe someone who's had experience on this side of things could say something on their quality. I _am_ a Flash designer/developer, and there are some very nice tools out there for doing Flash development in an open source way. There really is no equivalent for the visual-design portion of the Flash editing application, but MTASC is a Flash compiler that is very, very nice. http://www.mtasc.org/ There is also a web site called Open Source Flash that lists similar open source projects useful for creating Flash content: http://osflash.org/ Also, flash based UIs I seen while looking good are quite slow and jerky even on powerful (and power consuming) desktop machines so they're hardly usable.Of course this is my own private opinition and it is safe to ignore it. It depends on the designer/developer. Just as there are many, many bad C/C++ applications, and many, many bad HTML sites, there are many, many bad Flash interfaces. But, there will always be some really amazing, responsive examples of Flash interfaces, done by people who understand the limitations of the technology and ways around those limitations. There are some youtube vids of the prototype chumby in action where it doesn't look too sluggish - it has similar specs to the p1 fic1973, however it is running an adobe closed source flash player that may be faster than gnash. This is possibly true. I did talk to the lead developer of Gnash a few months back, however, and he said that they did recently get Gnash to play YouTube videos. So, I'm guessing it's not too terribly slow (I haven't checked the progress on it lately). I personally like the idea of having a ui that is designable by people who work on websites who have more design skills than the average c haxxor... Combined with an onboard webserver, one could do some fun things like transplant the phone's ui to whatever full computer you have handy. It opens up the phone to a whole different realm of developers, and that, in my opinion, is the best aspect of getting something like Gnash/Flash on the phone. It would be fun to run some chumby things on the fic but I would imagine *JUST* having a flash ui might be limiting for some projects - as a musician I would dread using a flash metronome, it would never have the timing of gtick. As a Flash developer, even I wouldn't want that. Options are good, especially considering the open nature of the phone. J. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Audio Jack 2.5 mm
High quality headsets designed for listening to music on cell phones are already available with 4-pole 2.5mm jacks. Take a look at Sennheiser (what I use). I'm sure there are others. http://www.sennheisercommunications.com/comm/icm_eng.nsf/root/products_mobile_mobile_music Don Wolfgang S. Rupprecht wrote: t3st3r [EMAIL PROTECTED] writes: I will have headache with buying 2.5 to 3.5 mm jack converter since handsets with 2.5 mm jack are pretty low-quality and only suitable for calls ... Agreed. Etymotic (http://www.etymotic.com/) makes a great set of very high fidelity headsets, but the stereo ones are all 3.5mm. The 2.5mm one is only monophonic, so it is pretty useless for listening to one's music. (They do make phone calls sound great though!) I've hoping that the combined stereo + microphone 2.5mm jack will catch on and we'll eventually be able to buy high-quality combined phone/stereo headsets. -wolfgang ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
