I’ll be writing up a few notes to review Froyo soon, but so far here is my take on the new Flash capability on the browser: http://www.theborgcollectives.com/2010/05/flash-on-nexus-one-browser.html

I also have a demo of the nexus one running flash on the browser, and i have to say it’s much better than i expected ( i didn’t expect much from it, after reading the Adobe hate letter of Steve Jobs).

just make sure that your N1 is on stock status, meaning you didn’t root it, or in iPhone terms: you didn’t jailbreak it.

and according to steve jobs: “You won’t be disappointed”

Source here:
http://www.macrumors.com/2010/05/23/steve-jobs-on-wwdc-announcements-you-wont-be-disappointed/

currently there are no android tablets and android ipod touch hehe

If you can wait a couple of years, and not bothered by the phone’s age, then yes, you can surely find “affordable” phones that fit your criteria.

http://www.engadget.com/2010/05/22/android-2-2s-froyo-goodness-hitting-the-nexus-one-already/

hayz, sana meron din yung Samsung Spica. Kaya ko lang naman pinili yung Spica kasi dahil sa Product Warranty. Sabi daw kasi kapag Nexus One binili ko yung terms nung warranty di applicable sa ibang bansa na hindi officially released ang Nexus One.

Only time will tell which OS is the best.. like what they say.. “Competition promotes innovation and even law suits!”

j/k

Only time will tell which OS is the best.. like what they say.. “Competition promotes innovation and even law suits!”

http://teknisyan.blogspot.com

j/k

Lol. Well, I wasn’t referring to the G1 only. There are still several phones stuck to pre-2.0 of Android.

Anyway, maybe Google should make an extra effort not to alienate people using older phones like:
1. Assemble a team to deal with backward compatibility with their new OS release, it may not be as good as Froyo or whatnot, just something like a compromise. They may even work with our dear android hackers/developers to come up with that. After all, Android is supposed to be “open source”.
2. Communicate with carriers and allow upgrade optionis at affordable or reasonable prices.

On the other hand, I guess it would be ideal for manufacturers to keep tabs, but it isn’t realistic. They are a business after all, and by doing that, they are probably reducing their sales by giving their customers less reason to buy a new phone they release.

Ah well I think the second one’s answer would be playing safe
On the bad side, they’ll be liable if it doesn’t work on one device that they advertised it’s going to work on.
On the good side, it’ll allow manufacturer’s to tinker with the core os and add abit of their own (like HTC’s Sense UI).

On the course of the discussion, I think we can narrow down our arguments to:

a.) Should Google release a version of the core OS that’s compatible with all known hardware
or
b.) Should Manufacturer’s ensure that they’ll be keeping tabs with Google’s updates and update their firmwares respectively.

Ok, so it “sounds like” Frodo. What’s your point? Should that be a basis for anything? How is the iPhone superior when it comes to mobile web browsing? Can the iPhone go to a website using voice recognition? Does it have flash?

I guess my only point would be, if some part-time hackers and developers can come up with good (if not better) results with their custom ROMs, why can’t Google, or even phone manufacturers do the same?

First, I should have clarified that I was talking about phones (android phones) already in the market prior to the release of a new version of the OS. So maybe we can blame Samsung if they did not release a 2.1 update and stuck to 1.6 (or was that 1.5?) since 2.1 was available already prior to their release. Good thing they released 2.1 after some time.

So my analogy with the laptop would be something like laptop is fairly new, like a couple of years old, runs the previous OS like a well-oiled machine, then suddenly, a new OS is released but you can’t run it on your laptop since it isn’t supported.

Will you jump to my ship now?

Doesn’t Android’s release go like:

1. Google releases New OS version
2. New OS version gets released to manufacturers
3. Manufacturer’s tinker with OS
4. Manufacturer release version of OS specific to phone model
5. People download #4.

because that’s the crux of my argument. We’re basically paying for the phone and the company’s (samsung, htc, et all) efforts to release a specified firmware for our phones.

If my analogy of the cycle for android OS releases is wrong then I’mma jump over to your ship now.

Anyway, it is not entirely Google’s fault for the fragmentation of the Google Market. Technology improves exponentially. But, Android and Google are almost synonymous, so I guess it is understandable such issue may be directed at them. I dunno, IMO, it seems like when Google gets tired with their new toy, back then, the G1, (now the N1), it seems they forget about it.

I don’t quite agree it should be directed at the phone manufacturers, since after all, they make the hardware. After all, I bet they would want the latest and greatest version in their phones, but they just can’t because of certain incompatibilities in terms of hardware specs.

Would you blame your laptop manufacturer if your unit cannot run Windows 7?

Yep, I know, that’s why I’d probably still root, even if I have the latest phone that can support Froyo. I just love the adventure of almost bricking a phone, but end up with a phone slightly better than the rest

Take note that I’m not defending Google against your argument since I have had to install 2.1 on my Spica via unofficial means (nearly bricked it too cause I installed the firmware for a different region), just pointing out that there’s more players than just you, me and google .