Re: Community update: The 850 MHz issue

2007-11-05 Thread Steve
Thanks for letting us know so quickly. This definitely gives me something to think about purchase wise. Please keep us informed as to any future plans for alternate tri-band or quad-band hardware. -Steve Michael Shiloh wrote: Unfortunately, this also affects the GTA02, which is now far too

Re: Community update: The 850 MHz issue

2007-11-05 Thread Michael Shiloh
Joe Pfeiffer wrote: Michael Shiloh writes: The chipset is capable of quad band but the board was laid out to only support 3 bands. So, 850Mhz is not supported on the GTA01 board. Instead we support 900/1800/1900MHz. How does the board layout affect the supported bands? Is it a jumper or

Re: Community update: The 850 MHz issue

2007-11-05 Thread Tupshin Harper
FWIW, I was planning on buying a GTA02 as soon as its available, but no 850 is a deal breaker since I would be using it on ATT's network in California. I would certainly be willing to buy it without 900MHZ support, though. -Tupshin Michael Shiloh wrote: Unfortunately, this also affects the

Re: Community update: The 850 MHz issue

2007-11-05 Thread Michael Shiloh
Will do. Michael Steve wrote: Thanks for letting us know so quickly. This definitely gives me something to think about purchase wise. Please keep us informed as to any future plans for alternate tri-band or quad-band hardware. -Steve Michael Shiloh wrote: Unfortunately, this also affects

Re: Community update: The 850 MHz issue

2007-11-05 Thread Jon
On Nov 5, 2007 5:58 PM, Michael Shiloh [EMAIL PROTECTED] wrote: Would that it were a jumper. Unfortunately it's much more complicated: it's a combination of circuit, components, firmware, and certification. Michael ___ OpenMoko community mailing

Re: Community update: The 850 MHz issue

2007-11-05 Thread Joshua Layne
I hate to add to the fire on this one, but no 850 is a definite deal breaker. No quad-band is a serious limitation, as it has been marketed since inception as a quad-band phone. I'm not sure that I am willing to spend $450 for a non-world phone. Regards, joshua Tupshin Harper wrote: FWIW, I

Re: Community update: The 850 MHz issue

2007-11-05 Thread Joe Pfeiffer
Michael Shiloh writes: How does the board layout affect the supported bands? Is it a jumper or something? Would that it were a jumper. Unfortunately it's much more complicated: it's a combination of circuit, components, firmware, and certification. Drat -- when firmware gets into it, it

Re: Community update: The 850 MHz issue

2007-11-05 Thread Justin Wong
Quick (sorta stupid) question. I'm in Vancouver, Canada. What does not having 850 support mean? Thanks, Justin On Nov 5, 2007 6:08 PM, Tupshin Harper [EMAIL PROTECTED] wrote: FWIW, I was planning on buying a GTA02 as soon as its available, but no 850 is a deal breaker since I would be

Re: Community update: The 850 MHz issue

2007-11-05 Thread Michael Shiloh
That's a good point, Tupshin. You (and the community) can guide us as we try to figure out how to proceed. How many of you must have 850 MHz support, and would be satisfied with an 850/1800/1900MHz variant, and how many of you must have full quad-band? Please put your answers on

Re: Community update: The 850 MHz issue

2007-11-05 Thread digger vermont
That's to bad. Like many people I've been looking forward to getting a Neo and using OM. Now I'm not sure if I will. I do a fair amount of camping and canoeing, at times in rural areas. I wonder how often the lack of the 850 band would cause problems? I looked around some and couldn't find any

Re: Community update: The 850 MHz issue

2007-11-05 Thread Jon
On Nov 5, 2007 6:23 PM, Michael Shiloh [EMAIL PROTECTED] wrote: That's a good point, Tupshin. You (and the community) can guide us as we try to figure out how to proceed. How many of you must have 850 MHz support, and would be satisfied with an 850/1800/1900MHz variant, and how many of you

Re: Community update: The 850 MHz issue

2007-11-05 Thread Michael Shiloh
I agree. We realize that this is a very grave issue and are treating it with the utmost concern. Michael digger vermont wrote: That's to bad. Like many people I've been looking forward to getting a Neo and using OM. Now I'm not sure if I will. I do a fair amount of camping and canoeing,

Re: Community update: The 850 MHz issue

2007-11-05 Thread Mathew Davis
Is there a way to do both? Can you have the 900/1800/1900MHz phones along with the 850/1800/1900MHz variant? I don't know if that would raise cost or anything. That way at order time you could select which one you would like. Who uses the 900 band does anyone know? I would think the

Re: Community update: The 850 MHz issue

2007-11-05 Thread Randall Mason
Generally, my rule of thumb is that rural places have more 850MHz, urban places have the 1900MHz. The only place I would usually see 850MHz was on road trips, but now that I live on the North Shore, there is only about 50% coverage for 1900MHz (and it's always like 1 bar). Randall

Re: Community update: The 850 MHz issue

2007-11-05 Thread Doug Sutherland
The big deal about 850Mhz vs 1900Mhz is that 850Mhz specification is higher power. Higher power means different, and probably more stringent, testing and certification requirements. Presumably that is why it's more than just a software/firmware issue requiring board design and component changes.

Re: Community update: The 850 MHz issue

2007-11-05 Thread Michael Shiloh
I would guess that if we make such a variant, we would offer both, but I don't know for sure. Please realize that I'm just asking the question in anticipation that the information might be useful at some point. I'm not suggesting that we have any plans yet to do so. Michael Mathew Davis

Re: Community update: The 850 MHz issue

2007-11-05 Thread Doug Sutherland
Mathew Davis: Who uses the 900 band does anyone know? Nobody in North America uses 900 or 1800. Originally all GSM phones were 900Mhz. The GSM specs were created in Europe. Due to congestion on the 900Mhz band most providers added support for 1800Mhz. North America was late in the GSM game

Re: Community update: The 850 MHz issue

2007-11-05 Thread ian douglas
Agreed, I'm in California as well, and though I bought a pre-paid T Mobile card, it doesn't work either because of the 3G issue. It would seem the 850 issue plus the 3G issue has just 'bricked' my Neo (in a metaphorical sense) without me writing a single line of code. And given that the

Re: Community update: The 850 MHz issue

2007-11-05 Thread Shawn Rutledge
On Nov 5, 2007 7:36 PM, Jon [EMAIL PROTECTED] wrote: http://www.gsmworld.com/roaming/gsminfo/cou_us.shtml which is the US list for GSM based operators, you will see it is universally 850 or 1900 (or both). In the case of ATT you can take a quick look at the two coverage I guess I'm in luck -

Re: Community update: The 850 MHz issue

2007-11-05 Thread Michael Shiloh
I hear you. Now that the 850MHz update is posted, I'll turn my attention to the 3G issue (GSM firmware update) and the GPS driver. I've only just starting to look into these (since I arrived in Taiwan) and I'll report in a new thread once I get a bit more information. Michael ian douglas

Re: Community update: The 850 MHz issue

2007-11-05 Thread Mike Hodson
On 11/5/07, Jon [EMAIL PROTECTED] wrote: I think then the question is (for us slightly less technically adept): How do we find out what support we have in our area? I have previously worked for a reseller of Cingular/ATT(used to work at radioshack for 4 years. joy!) and the stores login to

Re: Community update: The 850 MHz issue

2007-11-05 Thread Mike Hodson
On 11/6/07, Mike Hodson [EMAIL PROTECTED] wrote: On 11/5/07, Jon [EMAIL PROTECTED] wrote: I think then the question is (for us slightly less technically adept): How do we find out what support we have in our area? I have previously worked for a reseller of Cingular/ATT(used to work Also,

Community Update GPS comments...

2007-11-04 Thread Paul Breed
At the lowest level GPS runs hardware ranges or time offsets from each satellite. This does not directly give you a position. Some significant spherical trig is necessary to turn this into position. A lot of (AGPS) phones only have that hardware and rely on some system software (maybe not

Re: Community Update

2007-11-01 Thread Marcin Juszkiewicz
Dnia środa, 31 października 2007, Shawn Rutledge napisał: On 10/31/07, Michael Shiloh [EMAIL PROTECTED] wrote: That seems utterly ridiculous to me. A binary is a binary. If you have source *IF* you have a source... It looks like OpenMoko Inc lack source and got OABI binary from vendor of

Re: Community Update

2007-11-01 Thread Doug Sutherland
Okay this is what confuses me regarding this GPS source code. I have worked with several GPS modules. I have written code to configure them and read and parse their output. Why you would need the vendor's code is beyond me. They provide the specs. The specs are all you need to write your own

Re: Community Update

2007-11-01 Thread Karsten Ensinger
Doug Sutherland wrote: Okay this is what confuses me regarding this GPS source code. [...] Why you would need the vendor's code is beyond me. They provide the specs. The specs are all you need to write your own drivers. [...] I am baffled why there should EVER be a need for any kind of binary

Re: Community Update

2007-11-01 Thread Gabriel Ambuehl
The Global Locate device does a lot of GPS processing on the HOST CPU which is why it REALLY needs that driver to work. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community

Re: Community Update

2007-11-01 Thread Doug Sutherland
Karsten wrote: Some time ago, someone (I can not remember who it was) mentioned that the current GPS chip of the GTA01 does some calculations in software (means within the driver code), which is done by firmware in other GPS chips. Okay that makes some sense then what is being discussed, but

Re: Community Update

2007-11-01 Thread Doug Sutherland
By the way I should mention that not only Neo is experiencing the white screen phenomenon. I am doing tech support for phones and many off the shelf motorola and other standard brands are doing this. It's not a huge phenomenon but it has become regular in the past six months or so. Based on

Re: Community Update

2007-11-01 Thread Doug Sutherland
Gabriel wrote: The Global Locate device does a lot of GPS processing on the HOST CPU which is why it REALLY needs that driver to work. I am guessing, possibly wrongly, that this would be stuff like altitude and velocity calculations. When you look at every bit of a GPS spec there isn't a lot to

Re: Community Update

2007-11-01 Thread Doug Sutherland
Mikko wrote: 2) Yes, it can make sense not to have a bazillion CPUs on board from various perspectives. I evaluated no less than 25 different GPS modules some years ago and compared them in all important aspects. Every single one had a microcontroller onboard. I do not agree that it makes any

Re: Community Update

2007-11-01 Thread Mikko Rauhala
to, 2007-11-01 kello 06:00 -0500, Doug Sutherland kirjoitti: If this one is only sending raw data ie no actual coordinates then it makes no sense to use that part. *sigh* 1) Yes, it pretty much sends raw data. 2) Yes, it can make sense not to have a bazillion CPUs on board from various

Community Update

2007-10-31 Thread Michael Shiloh
Hello, I apologize that my bi-weekly update is a little late for this period. This is mostly due to traveling on my part. The update today is more organizational than technical. OpenMoko has added some key positions and some key people in those positions. This should help move the project

Re: Community Update

2007-10-31 Thread Mike Montour
Michael Shiloh wrote: To save time, please refrain from re-opening previous discussions. Re-opening implies that there has been some previous closure, vs. a discussion that just trailed off into silence. Could you please provide regular updates on important items that are still open, even

Re: Community Update

2007-10-31 Thread Adam
The current neo1973 is not FCC approved to operate in the 850Mhz band. It would be illegal for FIC to sell the device in the US with it activated. BT and PCS is the only approved band currently. http://www.phonescoop.com/phones/fcc_query.php?gc=EUNpc=GTA01BV4 Mike Montour wrote: Michael

Re: Community Update

2007-10-31 Thread Shawn Rutledge
On 10/31/07, Mike Montour [EMAIL PROTECTED] wrote: - Delivery of the promised 'gllin' GPS binary to GTA01 owners (anything that can be made to work, OABI/EABI/chrooted/whatever) Yes. Again, it has been much, much, much too long that we have been waiting for this.

Re: Community Update

2007-10-31 Thread Michael Shiloh
Mike Montour wrote: Michael Shiloh wrote: To save time, please refrain from re-opening previous discussions. Re-opening implies that there has been some previous closure, vs. a discussion that just trailed off into silence. Could you please provide regular updates on important items that

Re: Community Update

2007-10-31 Thread Shawn Rutledge
On 10/31/07, Michael Shiloh [EMAIL PROTECTED] wrote: Yes. You do realize that it is a legal issue that has been holding this up. But true, this is needed, and I'll find out what's going on. I thought the legal issue was resolved. ___ OpenMoko

Re: Community Update

2007-10-31 Thread Michael Shiloh
Yes. You do realize that it is a legal issue that has been holding this up. But true, this is needed, and I'll find out what's going on. Michael Shawn Rutledge wrote: On 10/31/07, Mike Montour [EMAIL PROTECTED] wrote: - Delivery of the promised 'gllin' GPS binary to GTA01 owners (anything

Re: Community Update

2007-10-31 Thread Michael Shiloh
Shawn Rutledge wrote: On 10/31/07, Michael Shiloh [EMAIL PROTECTED] wrote: Yes. You do realize that it is a legal issue that has been holding this up. But true, this is needed, and I'll find out what's going on. I thought the legal issue was resolved. Sorry for the confusion. I went back

Re: Community Update

2007-10-31 Thread Shawn Rutledge
On 10/31/07, Michael Shiloh [EMAIL PROTECTED] wrote: The first legal issue was to allow for the distribution of the driver in binary-only form. That was resolved. The next issue was technical, and resulted from the switch from OABI to EABI. That issue has a number of workarounds (wrapper,

Re: Community Update

2007-10-31 Thread Michael Shiloh
Shawn Rutledge wrote: On 10/31/07, Michael Shiloh [EMAIL PROTECTED] wrote: The first legal issue was to allow for the distribution of the driver in binary-only form. That was resolved. The next issue was technical, and resulted from the switch from OABI to EABI. That issue has a number of

Re: Community Update

2007-10-31 Thread Mark Arvidson
The modem licensing is a big deal breaker for me. I purchased a quad-band phone because I live in the US and need 850 coverage. I knew it is developer preview beta phone, and was willing to contribute and wait until the software is ready. If the phone is not going to be licensed for all four

Re: Bi-weekly OpenMoko community update

2007-10-16 Thread Robin Paulson
On 15/10/2007, Jay Vaughan [EMAIL PROTECTED] wrote: so no, we do want and require the source code to everything Change your government then. In the US for example, there are strict FCC-imposed regulations on how open certain portions of the carrier network can be, and this extends to

Re: Bi-weekly OpenMoko community update

2007-10-16 Thread Lars Hallberg
Robin Paulson skrev: on the other hand, we were specifically talking about the driver for the gps hardware, which is a receive only radio, and hence not covered by the same regulations as the gsm radio Yes. And I'm fully in suport for OpenMoko picking a new GPS unit with full os support.

Re: Bi-weekly OpenMoko community update

2007-10-16 Thread Derek Pressnall
On 10/14/07, Robin Paulson [EMAIL PROTECTED] wrote: hmm. this an open phone with open hardware and (where legal) open drivers. not having the source code to something would defeat the whole purpose of what sean et al are doing, and not attract any of the community that's here - the neo would

Re: Bi-weekly OpenMoko community update

2007-10-16 Thread Joshua Layne
Derek Pressnall wrote: If the gpsd falls into catagory 3 (and not 2), then for me that is ok, as long as it is bug free, will work with updated kernels, and has a defined api for talking to it from other apps. In that case, I can treat it as if I'm using a gps chip that spits out the protocal

Re: Bi-weekly OpenMoko community update

2007-10-16 Thread Michael Shiloh
Butt... For the old GTA01, that have the old chip, and that will not be used in the future, it is completely sufficient with a binary driver accessible thru the same interface as the GTA02 phones (even if it needs to be some function limitations). That's what originally stated anyway.

Re: Bi-weekly OpenMoko community update

2007-10-15 Thread Jay Vaughan
Absolutely agrree. GPS was one of my main points for buying the phone. I dont really care about the source for the driver as long as I can get the co-ordinates. Count me in the 'me too' crowd .. I'm really looking forward to having working GPS functionality on my GTA01, from the perspective

Re: Bi-weekly OpenMoko community update

2007-10-15 Thread Richard Bennett
On Mon, 15 Oct 2007 11:18:55 +0200, Jay Vaughan [EMAIL PROTECTED] wrote: so no, we do want and require the source code to everything Change your government then. Of course. This is but a small first step on the road to world domination ;o) ___

Re: Bi-weekly OpenMoko community update

2007-10-15 Thread Pranav Desai
On 10/14/07, Robin Paulson [EMAIL PROTECTED] wrote: On 15/10/2007, Pranav Desai [EMAIL PROTECTED] wrote: Absolutely agrree. GPS was one of my main points for buying the phone. I dont really care about the source for the driver as long as I can get the co-ordinates. hmm. this an open phone

Re: Bi-weekly OpenMoko community update

2007-10-14 Thread Thomas Wood
On Sat, 2007-10-13 at 12:02 +0200, Pedro Aguilar wrote: Hi, It would be nice that the software development your're doing at the moment would be backwards compatible with GTA01 (at least the parts that are not hw dependent and are different between GTA01 and GTA02), otherwise the users of

Re: Bi-weekly OpenMoko community update

2007-10-14 Thread Thomas Wood
On Sat, 2007-10-13 at 18:17 +0200, Jan Dittmer wrote: Hello Michael, it would be nice to have some info about this white screen of death plus vibrator which is affecting some people. Especially if that is a hardware or software problem. It's pretty annoying and generally happens if you want

Re: Bi-weekly OpenMoko community update

2007-10-14 Thread Pranav Desai
On 10/13/07, Shawn Rutledge [EMAIL PROTECTED] wrote: On 10/12/07, Michael Shiloh [EMAIL PROTECTED] wrote: We're very happy with the u-blox/Atmel ATR0635 GPS Receiver, and thus have made the decision to use this chip. That sounds like good news. It's not open-source but sounds like it

Re: Bi-weekly OpenMoko community update

2007-10-14 Thread Robin Paulson
On 15/10/2007, Pranav Desai [EMAIL PROTECTED] wrote: Absolutely agrree. GPS was one of my main points for buying the phone. I dont really care about the source for the driver as long as I can get the co-ordinates. hmm. this an open phone with open hardware and (where legal) open drivers. not

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Ryan Prior
I'd like to see a package of simply, fully working, high-quality example applications, including tutorials on cross-compiling and linking against different versions of the various OpenMoko libraries. It would provide an excellent starting point for developers such as myself who want to dive in but

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Michael Shiloh
Hi Ryan, That's a great idea. I too learn best from examples. I'll add this to the list. Thanks, Michael Ryan Prior wrote: I'd like to see a package of simply, fully working, high-quality example applications, including tutorials on cross-compiling and linking against different versions of

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Shawn Rutledge
On 10/12/07, Michael Shiloh [EMAIL PROTECTED] wrote: We're very happy with the u-blox/Atmel ATR0635 GPS Receiver, and thus have made the decision to use this chip. That sounds like good news. It's not open-source but sounds like it should be easier to interface with. However, FIC still needs

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Michael Shiloh
Shawn Rutledge wrote: On 10/12/07, Michael Shiloh [EMAIL PROTECTED] wrote: We're very happy with the u-blox/Atmel ATR0635 GPS Receiver, and thus have made the decision to use this chip. That sounds like good news. It's not open-source but sounds like it should be easier to interface with.

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Gabriel Ambuehl
On Saturday 13 October 2007 07:05:19 Michael Shiloh wrote: We're very happy with the u-blox/Atmel ATR0635 GPS Receiver, and thus have made the decision to use this chip. So does this mean we now have GPS hardware that outputs NMEA on a serial port (or something similar) without having to run

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Joachim Steiger
Gabriel Ambuehl wrote: On Saturday 13 October 2007 07:05:19 Michael Shiloh wrote: We're very happy with the u-blox/Atmel ATR0635 GPS Receiver, and thus have made the decision to use this chip. So does this mean we now have GPS hardware that outputs NMEA on a serial port (or something

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Jay Vaughan
We want to make it easier for developers to work with OpenMoko. We realize that many of our resources (e.g. wiki, website, development tools) are decidedly not user friendly at the moment and that other resources (e.g. documentation) are missing. I'm going to start putting a lot more

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Jan Dittmer
Hello Michael, it would be nice to have some info about this white screen of death plus vibrator which is affecting some people. Especially if that is a hardware or software problem. It's pretty annoying and generally happens if you want to show someone the phone :-( I cannot remember any

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Patrick Beck
Hello, this means that gta02v3 has bugs? Greets Patrick Beck Am Freitag, den 12.10.2007, 22:05 -0700 schrieb Michael Shiloh: GTA02v3, the third revision of GTA02, is still being verified and tested. This will take another couple of weeks, at which point we'll make GTA02v4. signature.asc

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Jay Vaughan
this means that gta02v3 has bugs? .. it means that the hardware is going through rigorous testing before it gets reproduced in large numbers. Certainly, hardware can have bugs .. the difference is that its very hard to fix these bugs 'at the user' once the hardware is shipped. I'm

Re: Bi-weekly OpenMoko community update

2007-10-13 Thread Patrick Beck
Hello, ok, than i am right = v3 has bugs and they musst be fix with v4. I dont think that this problem would be solved in one month. v4 has the same process like v3 = solve the bug problems = testing and validation. According to the wiki = they hoped that v3 is bug-free Greets Patrick Beck

Bi-weekly OpenMoko community update

2007-10-12 Thread Michael Shiloh
Hello everyone, I have some updates for you, and a question. First the updates: The GTA01 units that were shipped in the past two weeks have satisfied the back orders for GTA01. There continues to be demand for GTA01 so we are building some more. GTA02 Wifi hardware has been working for

<    1   2   3