Cupcake Update Thread

[santaninja]

also to support your theory some games use trackball which will not be on all android devices. it can probably easily be changed to touch sensitive but still there is a point there

all ota's will be different that's what i mean when they put it on a new phone that has different hardware they have to change the the way the os converts!

[wedlim]

All buttons, hardware or not, would be regarded by Android as "input." No matter what type of keyboard it is, Android would receive the same "input" signal, and accept it, and respond just the same.

While it's probably true that the G1, as a handset, has an input driver inside the hardware that sends the correct signal to Android according to what button you press, that driver would be a function of the hardware, not the OS. The OS simply receives input data and processes it. Which it would do for BOTH soft AND hard keyboards.

Windows does that EXACT same thing. You can plug in a keyboard, or you can use the built-in virtual keyboard on the screen. There aren't any drivers that you need to install for either one. Both provide Windows with input data, and Windows processes it.

So no, the OS isn't converting anything. All it does is receive data, no matter what the input is.

[jiGsawyouth]

http://phandroid.com/2009/02/17/htc-magic-first-impressions/
shows the cupcake keyboard. i like how it auto suggests words still.

[santaninja]

your saying an app that use's the keyboard with out converting would open up the soft keyboard on the g2 instead of it thinking there is a hard key board right? so other then conflicting code how do i play a game where i can only use the keyboard it comes on the screen and i cant see what I'm doing, and if both have the same the g2 will be using the onscreen key board for every key board and on the g1 it would use both key boards they  HAVE TO HAVE "TWO" DIFFERENT OTA's because only one can run , the G2's OS will say there are no drivers for the hard keyboard, the G1 will see that there are drivers for the keyboard, and they will both have to work in two different way's, witch would mean two different coddings for  two different paths

[santaninja]

plus with out a multi-touch screen there are lots of actoins you cant do like copy past and short cuts so they have to  change it to implement these things

[Cloverdale]

your saying an app that use's the keyboard with out converting would open up the soft keyboard on the g2 instead of it thinking there is a hard key board right? so other then conflicting code how do i play a game where i can only use the keyboard it comes on the screen and i cant see what I'm doing, and if both have the same the g2 will be using the onscreen key board for every key board and on the g1 it would use both key boards they  HAVE TO HAVE "TWO" DIFFERENT OTA's because only one can run , the G2's OS will say there are no drivers for the hard keyboard, the G1 will see that there are drivers for the keyboard, and they will both have to work in two different way's, witch would mean two different coddings for  two different paths

Games are quite awkward with only an on screen keyboard. The bottom of the screen will have touch buttons (arrows, numbers, etc) that are used to play the game.

[wedlim]

your saying an app that use's the keyboard with out converting would open up the soft keyboard on the g2 instead of it thinking there is a hard key board right?

No. That's not what I'm saying. I'm saying the soft keyboard would be part of the OS, but separate. It would be TREATED as a separate application, so that the OS can remain universal for all handsets. Think of it as a "detachable" program. It's there, but not inside the main software. That way, they can update Android without having to deal with the keyboard software. It would just sit on top of Android, separately.

You don't understand what I'm saying at all. It makes perfect sense. You keep assuming that the OS itself is what "converts" input data depending on what input it is. But you're wrong. The OS wouldn't even necessarily need to recognize the difference in input in order for it to work, and that's why it wouldn't need to have two different versions depending on the handset. (Windows Media Player only plays videos in formats it understands. You don't open a video in WMP, and watch WMP convert the video into a format it can play, do you? No. You open a video it can play, and it plays it. The video is data input. All WMP does is receive it and play it. It's the SAME principle. Both keyboard provide input data in the same format, and Android receives it.)

I'll say it again: if there are input drivers for the hard keyboard they would be IN THE HARDWARE, not the OS. I gave you a perfect example of what I mean, I'm not really sure why you don't get what I'm saying.


EDIT: Now if they released an update for the Magic that was an update to Android AND included an update TO the actual soft keyboard as well, then they might make a separate full update with the soft keyboard update included. But to update Android itself, it would be easy to release the same update to G1 and Magic owners. In fact, it seems more logical to me that, if they wanted to update the soft keyboard itself as well, they'd probably just release the Android update first (to all Android users), then release the keyboard update separately later on for the handsets with soft keyboards. It's hard to say if they'll do that or not though.

[santaninja]

what you don't get is this isn't windows you can not run stuff like changing how a program works with out administrator privilege witch would mean root access they cant put out an ota for both the G! and the G2 and they say i want to up date the G2 they cant put out a patch or driver because your phone does not have root they have to send out the hole os with a patch  on it, this is not anything like windows!!!!

WITCH WOULD MEAN 2222222222 DIFFERENT VERSIONS OF ANDROID

[jeno]

santa you are completely correct there will be to different versions of the to implement the driver issue for hardware they use propitiatory drivers to work with certain hardware  this implies to windows mobile rim symbian and any other os for mobile phones thats why you cant just load an os for a different phone whether it be window mobile, rim, symbian, android the drivers to make the hardware controls are all different coded for the drivers and thats why we dont have everything in cupcake branch its a driver issue.

[wedlim]

Woah there, calm down.

If I remember correctly, the cupcake update was designed by Android programmers for Android before the HTC Magic was even known about. In other words, the update itself would have been designed to specifically work on the G1, not the Magic, since the G1 is the only handset running Android. Logic would state that because of this fact, there's no possible way that the update is delayed because of driver issues between Android and the G1 hardware, don't you think?

I'm not saying they absolutely WILL do it the way I've described. What I'm saying is, the way I've described makes perfect sense, and it seems kinda stupid to do it any other way. If there are two versions, fine. But it seems like a pretty dumb method considering my way would work, doesn't it?

[jeno]

Woah there, calm down.

If I remember correctly, the cupcake update was designed by Android programmers for Android before the HTC Magic was even known about. In other words, the update itself would have been designed to specifically work on the G1, not the Magic, since the G1 is the only handset running Android. Logic would state that because of this fact, there's no possible way that the update is delayed because of driver issues between Android and the G1 hardware, don't you think?

I'm not saying they absolutely WILL do it the way I've described. What I'm saying is, the way I've described makes perfect sense, and it seems kinda stupid to do it any other way. If there are two versions, fine. But it seems like a pretty dumb method considering my way would work, doesn't it?

actually your wrong the cupcake branch was deployed after the g1 was releaseed. its purpose was for future deployment of future android devices and not the g1. now they have merged it with the main android kernel. so if you did your research then you would know why its not implemented into the os and the main issues is stability no where usable on the g1 all because of drivers. and to correct you again cupcake is not an update my friend. it is a DEVELOPMENT BRANCH so please read the threads on this subject. 

[g1_mar]

This is one serious subject. But I am with Jeno on this one.

[constance_emma]

let's buy iPhone 5