Google Working On Wireless Home Entertainment System

[Rodimus Prime]

How quickly people forget that the first Android phone, the T-Mobile G1, didn't even have an on-screen keyboard, it relied completely on the hardware keyboard it had.

Virtual keyboards only came to Android with an update to version 1.5 and so called "Input Modules Framework" - that's March 2009, over 2 years after Apple announced the iPhone!

Source code headers in that Android framework confirm this by stating "Copyright (C) 2008-2009 Google Inc.".

These facts are undeniable. No matter how you twist things, or show videos of rushed, unusable, prototypes filmed 10 months after the iPhone.

Obviously, as kdarling said, full screen phones were not in Google's original plans until they got their "Oh ****" moment following the iPhone success. They probably originally had thought the same as Ballmer - screen keyboards would never fly.

The funny part is Google apparently didn't learn the lesson then, and years later was still repeating the same mistake:

Image

Exhibit A: Remote controller for Google TV

Going to point out again the header file means nothing. Just because the first device did not have it does not mean it was not there. The HTC choose not to put in on the G1. The test devices would of had the onscreen keyboard in it since it was pure testing.

You are going for bashing. The video posted proves that Google had it in place months before hand. To the OS it means nothing if it comes from an on screen keyboard or hardware. The keyboard sends the key press code to the OS and from there handles it. Standard code from keyboards.

All the API did was make it really easy to provide 3rd party keyboards. Nothing more nothing less.

 

[gkpm]

Going to point out again the header file means nothing. Just because the first device did not have it does not mean it was not there. The HTC choose not to put in on the G1. The test devices would of had the onscreen keyboard in it since it was pure testing.

Except HTC put it on as soon as the 1.5 update came out.

The video posted proves that Google had it in place months before hand. To the OS it means nothing if it comes from an on screen keyboard or hardware. The keyboard sends the key press code to the OS and from there handles it. Standard code from keyboards.

All the API did was make it really easy to provide 3rd party keyboards. Nothing more nothing less.

You mean 10 months after hand - and it wasn't really working at all. Come on, honestly, look at the video and tell me why he avoided popping up the on-screen keyboard even ONCE for the whole demo?

There's no such thing as "standard code from keyboards". Keyboards are a bit more complex than that (heard of debounce?), and modern on screen input methods even a "little" more.. [-]But clearly you're not interested in knowing the truth, just spreading BS.[/-]

Edit: I do apologise, just remembered you're not only interested in spreading BS, you're also into downvoting anyone who doesn't eat your BS. Sorry I missed that.

 

[Rodimus Prime]

There's no such thing as "standard code from keyboards". Keyboards are a bit more complex than that (heard of debounce?), and modern on screen input methods even a "little" more.. But clearly you're not interested in knowing in knowing the truth, just spreading BS.

You know that alone kind of proves how little you understand about software or even messed with it.
In terms of hardware keyboards the debounce is handled by the keyboard itself not by the OS. It so a clean signal can be transmitted by the keyboard.

Also the fact that you do not think there is a standard keyboard code is rather funny. Sorry but there are standard keyboard codes.
For example the enter key is '10'
the #1 key is "49'
Along with that code there is a key press and key release.

Here is a nice little java program that can help show you all the key codes from your keyboard
http://docs.oracle.com/javase/tutorialJWS/uiswing/events/ex6/KeyEventDemo.jnlp

Just because the API was not there it not like it not something that can be brought in later.

 

[gkpm]

You know that alone kind of proves how little you understand about software or even messed with it.
In terms of hardware keyboards the debounce is handled by the keyboard itself not by the OS. It so a clean signal can be transmitted by the keyboard.

Hahah really, you're going there.

So... Is that why Android has a debounce issue, and a kernel debounce algorithm?

http://code.google.com/p/android/issues/detail?id=15708

Not so clean now, is it...

We're talking a bit lower level than Java here. Maybe try to keep up.

 

[Rodimus Prime]

Hahah really, you're going there.

So... Is that why Android has a debounce issue, and a kernel debounce algorithm?

http://code.google.com/p/android/issues/detail?id=15708

Not so clean now, is it...

We're talking a bit lower level than Java here. Maybe try to keep up.

again that can easily be written and handled by the person making the keyboard to handle their own debound. Software in the OS handles it. iOS has it so does the others.

I also find it funny that you think iOS does not have debouncing. That is a hardware issue and interference from the outside world and from the hardware itself.

 

[gkpm]

In terms of hardware keyboards the debounce is handled by the keyboard itself not by the OS. It so a clean signal can be transmitted by the keyboard.

again that can easily be written and handled by the person making the keyboard to handle their own debound. Software in the OS handles it. iOS has it so does the others.

Amazing how you go from one post saying the operating system doesn't do debouncing right to another saying ALL operating system do.

Give up making things up.

 

[Rodimus Prime]

Amazing how you go from one post saying the operating system doesn't do debouncing right to another saying ALL operating system do.

Give up making things up.

first one I was talking about a hardware keyboard not about the software side.

The thing I find sad about some people here is they bash anything not Apple and try to attack android. Say it is just a copy of iOS yet they tend to pass over the very blatant coping iOS will do.

 

[gkpm]

first one I was talking about a hardware keyboard not about the software side.

Quite telling that you don't know it's used for both.

The thing I find sad about some people here is they bash anything not Apple and try to attack android. .

... and I find it sad that people make things up that never actually existed just to bash Apple and iOS.

Just to reiterate in case it was missed amongst all the noise you made (I know that trick too):

Argument: A modern style full screen, keyboard-less phone was not in Google's plans until after the iPhone came out.

Evidence:

1. The T-Mobile G1 - Google's first phone, released in late 2008 - did not have an on-screen keyboard, it relied completely on the hardware keyboard - until the 1.5 update several months later.
   
   
2. Full screen Android phones without a keyboard only became possible with Android version 1.5 in March 2009, which got code for something called IMF - the Input Module Framework.
   
   
3. All the IMF source code states "Copyright (C) 2008-2009 Google Inc.". One year after the iPhone was out.
   
   
4. Some 10 months after the iPhone was announced, Google posted a video showing a full screen Android prototype. However during the entire view an on-screen keyboard was never shown, not even to type in an URL on the browser .Clearly it was in a very early stage prototype.

In conclusion, unless you provide stronger facts than these, don't claim there was keyboard-less Android prototype before the iPhone and that this was "shown in some 50 threads". That's completely false.

 

[Renzatic]

... and I find it sad that people make things up that never actually existed just to bash Apple and iOS.

Show me one example where Rodimus has "bashed" Apple and iOS.

 

[matrix07]

Show me one example where Rodimus has "bashed" Apple and iOS.

Didn't he say "people"?

Let me get this straight. So now "It's been proven in at least 50 threads on MR (no, thats NOT an exaggeration)" is reduced to "the header file means nothing. Just because the first device did not have it does not mean it was not there."?
Seriously?

 

[rdowns]

Show me one example where Rodimus has "bashed" Apple and iOS.

Show me a post where he doesn't.

 

[Renzatic]

He usually comes in to correct people who seem to think Apple invented everything in a vacuum, and everyone else perpetually plays catchup. That's not exactly what I'd call bashing iOS and Apple.

Unless you're one of those people who also think that toeing the company line 100% is the only way to support Apple, and anyone who questions their decisions is a...gasp...ANDROID FANATIC!

 

[zep1977]

*sucks in a big hit of helium to get the voice down*

i wonder if it'll be open. boi google ftw! EPIC!

 

[samcraig]

Now here's a shock. An article about Google working on a wireless home entertainment system... on MacRumors... getting a tons of criticism. Well color me shocked! After all - clearly those posting here - who are big supporters of Apple and their products are NOT the primary target market. There are apparently (just by looking at the numbers) plenty of people who are in the Android ecosystem who would probably love to have the same/similar tight integration with their devices both mobile and at home that many people love about Apple's tight integration.

But by all means - let's all just bash on something that doesn't exist yet and that no one has used. Makes perfect sense.

 

[ftaok]

Huh?

Do cable operators pay Motorola Mobility for the privilege for handing out their current generation of cable boxes? LOL - No. cable operators buy these boxes from motorola Mobility and then lease them to customers.

The incentive for cable operators to lease cable boxes to customers is having cable customers able to watch cable tv.

You misunderstood my point. Google/MMI won't be able to penetrate the advertising/data collection market for cable subscribers. I have no doubt that they'll maintain/grow their market for selling STB/DVRs, but grabbing a portion of the advertising and consumer data revenue will require GOOG/MMI to play ball with the cable operators.

And I've seen very little indication that the Comcasts, TimeWarners, Cablevisions, Verizons of the world have any interest in sharing the information of their customers.

 

[TomPerfect]

****ers will probably insert ads between songs.

Heaven alone, a company making money through advertising? Shudder at the thought.


Those lambasting Google for its venture into hardware, while quietly championing Apple, fail to see the irony.

Apple, in its early days, was predominantly a computer company, before diverging into consumer electronics and software, to which it has been hugely successful.

If Google wishes to secure its long-term future, it must move away from Search (where revenue is overwhelmingly derived from) and into other areas.

 

[twoodcc]

i can't say i'm surprised by this. but it better stream video too if they want to sell it