Android 2.2 (Froyo) features • Hacker News Board

Re: Android 2.2 (Froyo) features

#11

Post by wanderr » Sun, Apr 25, 2010, 12:47 AM UTC

ebiester wrote: post #3

I'm worried about developer-side automatic update. I can think of more than a few times where I wouldn't want such an update, or bad things that a developer could do to a user. As a developer, I'd like it, but I'm not so sure as a user.

There was a streaming music app not too long ago that accidentally wiped people's SD cards entirely if the update was installed. Definitely glad I waited a few days and checked the comments before updating.

Re: Android 2.2 (Froyo) features

#12

Post by wanderr » Sun, Apr 25, 2010, 12:57 AM UTC

Can anyone elaborate on how JIT is new to 2.2 and how that compares to how <=2.1 handles it? I haven't touched Java in ages, but I thought JIT was a fundamental part of how Java works, so I'm a bit confused.

Re: Android 2.2 (Froyo) features

#13

Post by tvon » Sun, Apr 25, 2010, 12:59 AM UTC

machrider wrote: post #6

Has there been any update on the Nexus Two rumors from a month or two ago? I want an Android phone and I'm tempted to get the Nexus One, but I don't want it to instantly be obsolete... Recommendations?

I don't follow Android phones that closely, but the HTC Incredible[1] and HTC Evo[2] both look very nice, I'm not sure of the details but it looks like the Incredible is Verizon and the Evo is Sprint...?

[1] http://www.engadget.com/2010/04/19/droid-incredible-review/

[2] http://www.geekogle.com/2010/htc-evo-the-soon-to-be-released...

Re: Android 2.2 (Froyo) features

#14

Post by teilo » Sun, Apr 25, 2010, 1:14 AM UTC

wanderr wrote: post #12

Can anyone elaborate on how JIT is new to 2.2 and how that compares to how <=2.1 handles it? I haven't touched Java in ages, but I thought JIT was a fundamental part of how Java works, so I'm a bit confused.

Android does not have a JVM. While Android applications are written in Java, and initially compiled to Java bytecode, that bytecode is then translated into Davlik bytecode, and saved to a compact .dex executable, and run in the Davlik virtual machine. The Davlik virtual machine is quite different from the JVM. It is optimized for small devices. It is register-based rather than stack-based. It does not (currently) include a JIT compiler.

Re: Android 2.2 (Froyo) features

#15

Post by hyperbovine » Sun, Apr 25, 2010, 1:23 AM UTC

jaybol wrote: post #7

Froyo as in frozen yogurt right?

Yeah. Although how this is supposed to be an improvement over cupcake is anyone's guess.

Re: Android 2.2 (Froyo) features

#16

Post by dschobel » Sun, Apr 25, 2010, 1:33 AM UTC

Here's hoping for a software fix for the N1's crappy multi-touch: http://androidandme.com/2010/03/news/is-multitouch-broken-on...

Re: Android 2.2 (Froyo) features

#17

Post by risotto » Sun, Apr 25, 2010, 1:38 AM UTC

mey wrote: post #5

I'd really love Bluetooth HID profile support. Even just keyboard.

I want mouse too! My phone should/could be a little VNC/KVM type device for many computers

Re: Android 2.2 (Froyo) features

#18

Post by wanderr » Sun, Apr 25, 2010, 1:40 AM UTC

teilo wrote: post #14

wanderr wrote: post #12

Can anyone elaborate on how JIT is new to 2.2 and how that compares to how <=2.1 handles it? I haven't touched Java in ages, but I thought JIT was a fundamental part of how Java works, so I'm a bit confused.

Android does not have a JVM. While Android applications are written in Java, and initially compiled to Java bytecode, that bytecode is then translated into Davlik bytecode, and saved to a compact .dex executable, and run in the Davlik virtual machine. The Davlik virtual machine is quite different from the JVM. It is optimized for small devices. It is register-based rather than stack-based. It does not (currently) inc…

Wow, I had no idea! Thanks for the summary. :)

Re: Android 2.2 (Froyo) features

#19

Post by eli » Sun, Apr 25, 2010, 1:48 AM UTC

wanderr wrote: post #18

teilo wrote: post #14

Earlier quoted context omitted.

Android does not have a JVM. While Android applications are written in Java, and initially compiled to Java bytecode, that bytecode is then translated into Davlik bytecode, and saved to a compact .dex executable, and run in the Davlik virtual machine. The Davlik virtual machine is quite different from the JVM. It is optimized for small devices. It is register-based rather than stack-based. It does not (currently) inc…

Wow, I had no idea! Thanks for the summary. :)

Yup, seems like a really clever way to give developers a familiar language with a huge library without having to make a deal with Sun (err Oracle) for a JVM license

Re: Android 2.2 (Froyo) features

#20

Post by jsz0 » Sun, Apr 25, 2010, 1:54 AM UTC

ebiester wrote: post #3

I'm worried about developer-side automatic update. I can think of more than a few times where I wouldn't want such an update, or bad things that a developer could do to a user. As a developer, I'd like it, but I'm not so sure as a user.

I'd be happy with an "Update All" button.