Couldn't run android 1.5

[Morris]

Dear All:

I follow the building steps of android web but after I get source and
build, my firmware version is 1.0.
The other example is that I could find the softkeyboard code but I
couldn't see it on the emulator when I want to edit email.
In my viewpoint, I think I have get the newest code of android because
I see the cupcake branch.

Please tell me whether I miss some steps.

Thanks a lot

Morris

[Jean-Baptiste Queru]

Thanks for not cross-posting.

I'm not an expert in that area, but I believe that the softkeyboard
behavior depends on whether the "hardware" (or the emulator) reports
that it has a hardware keyboard, and it's possible that the emulator
might report that it has a hardware keyboard in both orientations. I'm
probably entirely wrong here.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

[David Turner]

well, the emulator reports that the lid is closed in the default "portrait" orientation.

even if the window shows a functional keyboard.

this is an intentional decision that was made when we released the first SDK before any public announcement regarding the G1 hardware was made. we should probably modify the skin to get rid of the keyboard in this case.

And as far as I know, the soft keyboard works in both portrait and layout modes (though this could have changed lately).

[Morris]

Hi Jean:

Thanks!

I have another question. After I get the newest code(including
cupcake) from android and build it using "make", I run emulator in
portrait mode. But I couldn't see the new feature on it such as
softkeyboard.
Why do I have this question? It's because I see the below web.
http://wiki.cheyingwu.tw/Android/Firmware-Update/Android-1.5
I download its image from it and then I run emulator
I could see the new features. However I use my image from the android
using reop init, I still see the android 1.0.
Whether do I miss some steps?

Best Regards,
Morris

On 1月16日, 上午12時48分, David Turner <di...@android.com> wrote:
> well, the emulator reports that the lid is closed in the default "portrait"

> orientation.even if the window shows a functional keyboard.

>
> this is an intentional decision that was made when we released the first SDK
> before any public announcement regarding the G1 hardware was made. we should
> probably modify the skin to get rid of the keyboard in this case.
>
> And as far as I know, the soft keyboard works in both portrait and layout
> modes (though this could have changed lately).
>
> On Thu, Jan 15, 2009 at 4:26 AM, Jean-Baptiste Queru <j...@google.com> wrote:
>
> > Thanks for not cross-posting.
>
> > I'm not an expert in that area, but I believe that the softkeyboard
> > behavior depends on whether the "hardware" (or the emulator) reports
> > that it has a hardware keyboard, and it's possible that the emulator
> > might report that it has a hardware keyboard in both orientations. I'm
> > probably entirely wrong here.
>
> > JBQ
>

[Dianne Hackborn]

When running on the emulator or G1, the soft keyboard generally won't be shown when in landscape mode because the "keyboardHidden" flag is no longer set; the default behavior of an input method is to not show its UI when there is a keyboard, since that would be redundant.

--
Dianne Hackborn
Android framework engineer
hac...@android.com

Note: please don't send private questions to me, as I don't have time to provide private support.  All such questions should be posted on public forums, where I and others can see and answer them.

[Morris]

Hi Jean:

Thanks a lot.

I need to clarify some points.

a. If I get the newest android code(1.5) and build it, when I use
landscape mode, I did not see softkeypad. Right?
b. follow the previous question(a), if I use portrait mode and not
to disable softkeypad, I should see softkeypad. Right?
c. after I get the newest android code(1.5) and build it, why do I
see the android version is still 1.5 on emulator?

Thanks for your helop

Best Regards,
Morris

On 1月16日, 上午10時38分, "Dianne Hackborn" <hack...@android.com> wrote:
> When running on the emulator or G1, the soft keyboard generally won't be
> shown when in landscape mode because the "keyboardHidden" flag is no longer
> set; the default behavior of an input method is to not show its UI when
> there is a keyboard, since that would be redundant.
>
>
>
> On Thu, Jan 15, 2009 at 8:48 AM, David Turner <di...@android.com> wrote:
> > well, the emulator reports that the lid is closed in the default "portrait"

> > orientation.even if the window shows a functional keyboard.

>
> > this is an intentional decision that was made when we released the first
> > SDK before any public announcement regarding the G1 hardware was made. we
> > should probably modify the skin to get rid of the keyboard in this case.
>
> > And as far as I know, the soft keyboard works in both portrait and layout
> > modes (though this could have changed lately).
>
> > On Thu, Jan 15, 2009 at 4:26 AM, Jean-Baptiste Queru <j...@google.com>wrote:
>
> >> Thanks for not cross-posting.
>
> >> I'm not an expert in that area, but I believe that the softkeyboard
> >> behavior depends on whether the "hardware" (or the emulator) reports
> >> that it has a hardware keyboard, and it's possible that the emulator
> >> might report that it has a hardware keyboard in both orientations. I'm
> >> probably entirely wrong here.
>
> >> JBQ
>

> >> On Wed, Jan 14, 2009 at 7:17 PM, Morris <MorrisChen.C...@gmail.com>

> >> wrote:
>
> >> > Dear All:
>
> >> > I follow the building steps of android web but after I get source and
> >> > build, my firmware version is 1.0.
> >> > The other example is that I could find the softkeyboard code but I
> >> > couldn't see it on the emulator when I want to edit email.
> >> > In my viewpoint, I think I have get the newest code of android because
> >> > I see the cupcake branch.
>
> >> > Please tell me whether I miss some steps.
>
> >> > Thanks a lot
>
> >> > Morris
>
> >> --
> >> Jean-Baptiste M. "JBQ" Queru
> >> Android Engineer, Google.
>
> --
> Dianne Hackborn
> Android framework engineer

> hack...@android.com

[Jean-Baptiste Queru]

I have no idea, sorry.

JBQ

[Morris]

Dear All:

I have solved this issue.
The root cause is that I continually read the android SDK image so I
always see the android 1.0.

Sorry to waste your time.

Regards,
Morris