Interesting. I wasn't aware that apps could execute commands. Hmm... I suppose if you're coding using the NDK, there would be no way to stop this behaviour.

Very interesting indeed.

I would like to take the time out to welcome our BB breathren to the Android eco-system:

http://www.engadget.com/2011/03/24/r...erry-playbook/

The Playbook is confirmed to run BBOS (or whatever the playbook OS is called), Java and Android apps!

Great to have you aboard!

ADB makes it possible to run ARM console apps (like rageagainsthecage) without NDK. (You can issue command line commands in Android apps--and these trojan apps DO ask for this permission.. which a lot of people just OK without realizing it.)

NDK, if I understand it right, actually protects you more from this than you'd have expected. Ironic!

Those people can go sit at the kiddie table, though. Running the apps versus running the OS is a different world (and a far less reliable world, I'd wager).

Here we go... some more definite and elaborate details on how it works:
http://intrepidusgroup.com/insight/2...-the-c-skills/

It seems that Google is delaying the Honeycomb source-code release. The reason? It's not ready for prime-time:

http://www.engadget.com/2011/03/24/g...-its-not-ready

Better late and ready, than early and broken! I wonder how this affect Samsung's schedule...

Very interesting... As always, the exploits are rather clever!

On the one hand, I do believe that Google should decouple far more from the OS or provide a means of faster updates to patch exploits like this (ala Ubuntu).

On the other hand, I think that having a way in is still a key characteristic of hardware that I would want to purchase. Now, this entry point could be via USB only or something, in order to lock the system down from otherwise malicious programs, but it would be nice for some options to exist.

Are you ready for the wave of controversy? Here it comes:
http://www.androidcentral.com/google...says-bloomberg

One interpretation of the latest news about the honeycomb delay is that honeycomb won't be released as OSS at all. Instead, versiont 'I' (eg. Ice cream) will the OSS version built for tablets and (presumably) phones alike.

ORIGINAL ARTICLE: http://www.businessweek.com/technolo...324_269784.htm

I've not read the parent article, but if one major blog comes to this conclusion and others read it, it will be huge news in the coming hours. Expect a Google statement to follow.

I expect that android dissenters to come out of the woodwork, and just perhaps there's reason for them to. All eyes on tomorrow.

EDIT: Having read the original article and considered it somewhat, I think Google delaying the release helps Android more than it hurts Android. Some fanboys may get upset, but releasing a product that's not ready for mobile phones and knowing full well that companies will try to shoehorn it onto mobile phones, will only tarnish the Android brand. I would do the same thing.

It's not as if Android has gone closed source. I'm grateful that Google can make such level headed decisions in the anticipation of potential outrage.

Now that this is an Android Thread....

Take a look at Sprints Nexus S.

http://www.engadget.com/2011/03/24/g...rint-hands-on/ (w/ video)

Simply gorgeous, and running a new build of Gingerbread (v2.3.4)

I really like the styling of this device, and that screen is to die for.

But I thought this was the definition of open.

Sorry, no--come back, you just gave me such a good opportunity to use that. I couldn't help it.