On Thu, Jan 7, 2010 at 5:10 PM, Shawn Brown <big.coffee.lo...@gmail.com>wrote:
> > We do understand the value of what you are asking > > for. It is one of our goals, but frankly it is not at the top of the > > list and we would not have held off on shipping Nexus One if we could > > not release every bit of the source code. > Thank you for confirming that Google tells HTC Android will have > bluetooth and that is what HTC tells consumers and we buy the phones > but you are too worried about your handset getting out to market so > you and HTC can't be bothered providing the bluetooth that HTC says on > it's sites in many different countries for many different handsets is > available.
*blink* Ooookay... and the connection between Mike's comment, and your rant is...?
Honestly, at this point it just looks like you have a big axe to grind. So fine, grind away, but it is not going to help anyone and it is certainly not worth spending further time on this discussion.
(And in response to your later comment -- no, we are not going to spend time back-porting features like Bluetooth from newer platforms to older ones. Given a choice between doing that and improving the current platform, well it just isn't any choice.)
Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them.
> (And in response to your later comment -- no, we are not going to spend time > back-porting features like Bluetooth from newer platforms to older ones. > Given a choice between doing that and improving the current platform, well > it just isn't any choice.)
My "rant" as you so inelegantly put it got me the information that I needed. Now if you at Google were a little more forthcoming with information then perhaps I wouldn't have to ask the way I did. I so do apologize.
I also bought a Nexus One with the understanding, based on a spec that I read, that it had support for RFCOMM. I have been trying to find the site where I read this but haven't located it yet. Can you help?
Don
On Jan 6, 7:10 pm, Shawn Brown <big.coffee.lo...@gmail.com> wrote:
> > Did you try to return the phone for a refund? It seems like a > > reasonable request if you were promised RFCOMM when you bought the > > phone.
> Well I guess that is an option but what about other users (of our lego > project) that are in the same boat. We should all take our phones > back? We've gotten them from different carriers (some in the U.S., > some Europe, some Japan) and whatnot so I don't expect a uniform > resolution that way.
> I think I'd feel better as a group trying to compel HTC and Google to > provide what they said they would. Maybe they will, and maybe they > intend to, but the fact that they won't say is bothersome. HaHa - you > bought it and we won't tell you if or when it will work!
> Sorry to be noise but I just hope someone at Google knows we care > about this. HTC is like send email here, call here (cycle, rinse and > repeat).
> I also bought a Nexus One with the understanding, based on a spec that > I read, that it had support for RFCOMM. I have been trying to find > the site where I read this but haven't located it yet. Can you > help?
> Don
> On Jan 6, 7:10 pm, Shawn Brown <big.coffee.lo...@gmail.com> wrote: >>> Did you try to return the phone for a refund? It seems like a >>> reasonable request if you were promised RFCOMM when you bought the >>> phone.
>> Well I guess that is an option but what about other users (of our lego >> project) that are in the same boat. We should all take our phones >> back? We've gotten them from different carriers (some in the U.S., >> some Europe, some Japan) and whatnot so I don't expect a uniform >> resolution that way.
>> I think I'd feel better as a group trying to compel HTC and Google to >> provide what they said they would. Maybe they will, and maybe they >> intend to, but the fact that they won't say is bothersome. HaHa - you >> bought it and we won't tell you if or when it will work!
>> Sorry to be noise but I just hope someone at Google knows we care >> about this. HTC is like send email here, call here (cycle, rinse and >> repeat).
>> Shawn > -- > You received this message because you are subscribed to the Google Groups "android-platform" group. > To post to this group, send email to android-platform@googlegroups.com. > To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.
Thanks but I don't see where there is any mention on this page of Nexus One support of RFCOMM or the SPP profile. Shawn says that he saw specs or was given the information that Nexus One would support RFCOMM or the SPP profile and I also read a spec that had this claim. Did HTC or Google ever make that claim publicly? If so, I would be interested in seeing it because I also bought a Nexus One under the same mistaken impression based on something that I read that claimed that there was such support. The page I read MIGHT have been this one http://www.mobiledia.com/phones/google/nexus-one.html but I am not sure. I realize that this page is neither from Google or HTC and if it is the source of my costly mistake, I am the one at fault for not making sure it was correct. But one wonders where these people (and Shawn) got this bit of misinformation. Like Shawn, I am distressed at having purchased a phone under a false impression.
Don
On Jan 12, 1:52 pm, Matthias Granberry <matthias.granbe...@gmail.com> wrote:
> > I also bought a Nexus One with the understanding, based on a spec that > > I read, that it had support for RFCOMM. I have been trying to find > > the site where I read this but haven't located it yet. Can you > > help?
> > Don
> > On Jan 6, 7:10 pm, Shawn Brown <big.coffee.lo...@gmail.com> wrote: > >>> Did you try to return the phone for a refund? It seems like a > >>> reasonable request if you were promised RFCOMM when you bought the > >>> phone.
> >> Well I guess that is an option but what about other users (of our lego > >> project) that are in the same boat. We should all take our phones > >> back? We've gotten them from different carriers (some in the U.S., > >> some Europe, some Japan) and whatnot so I don't expect a uniform > >> resolution that way.
> >> I think I'd feel better as a group trying to compel HTC and Google to > >> provide what they said they would. Maybe they will, and maybe they > >> intend to, but the fact that they won't say is bothersome. HaHa - you > >> bought it and we won't tell you if or when it will work!
> >> Sorry to be noise but I just hope someone at Google knows we care > >> about this. HTC is like send email here, call here (cycle, rinse and > >> repeat).
> >> Shawn > > -- > > You received this message because you are subscribed to the Google Groups "android-platform" group. > > To post to this group, send email to android-platform@googlegroups.com. > > To unsubscribe from this group, send email to android-platform+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=en.
> Shawn says that he > saw specs or was given the information that Nexus One would support > RFCOMM or the SPP profile and I also read a spec that had this claim.
Public HTC claims:
1) Specifically, the mytouch claims rfcomm support. http://www.htc.com/us/support/t-mobile-mytouch-3g/help/bluetooth What version of Bluetooth does my device come with? close Your device comes with Bluetooth v2.0 with EDR. Supported profiles GAP, RFCOMM, HFP, HSP, and A2DP.
2) and so does the magic http://www.htc.com/ca/support/magic-rogers/help/bluetooth What version of Bluetooth does my device come with? close Your device comes with Bluetooth v2.0 with EDR. Supported profiles GAP, RFCOMM, HFP, HSP, and A2DP.
I can find nothing specifically from HTC that the Nexus One supports rfcomm, but I bet they are the source of the article you saw.
Well generally, it is beyond dispute that HTC advertises Bluetooth 2.0 in all it's devices. Only in Japan could I find information stating accurate information on what it really provided.
