Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 472

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 487

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 494

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php on line 530

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 594

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 611

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 705

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 728

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/cache.php on line 425

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/theme.php on line 623

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/class.wp-dependencies.php on line 15

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/4/d289104336/htdocs/embeddedflash/wp-content/plugins/eminimall/eminimall.php on line 341

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/comment.php on line 227

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/classes.php on line 230

Warning: Cannot modify header information - headers already sent by (output started at /homepages/4/d289104336/htdocs/embeddedflash/wp-settings.php:472) in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/feed-rss2-comments.php on line 8
Comments on: Flash 10.1 on Android- myth and reality http://www.embeddedflash.com/?p=711 Read all about Flash/AIR/HTML 5 Sun, 26 Jan 2020 09:13:36 +0000 http://wordpress.org/?v=2.6.1 By: admin http://www.embeddedflash.com/?p=711#comment-28109 admin
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Sun, 10 Oct 2010 22:26:01 +0000
http://www.embeddedflash.com/?p=711#comment-28109 @ Hayden- well- the requirements remain the same.For Flash 10- ARM 11 class CPU at 600 Mhz. But that doesn't mean that every screen resolution is supported and all the content will play satisfactorily with that CPU! As far as I know, there isn't any CPU requirement specified by Android 2.2. @Scott- I had a fortune of playing with couple of different phones sporting different Android versions recently and realized that one showed availability whereas other one didn't! So clearly either the Marketplace or the Flash player knows the version of the OS/device requesting the download. I think for Flash, the fragmentation would be no different for any other application. If I was to look at the comments made on different Android applications that I tried till date- some of them work well on some phones and not on others. So Flash applications would be similar - they may work on Droid but not on Samsung Vibrant for example. But for Flash applications, the publisher could clearly specify that 'Flash player 10 required'. @ Hayden- well- the requirements remain the same.For Flash 10- ARM 11 class CPU at 600 Mhz. But that doesn’t mean that every screen resolution is supported and all the content will play satisfactorily with that CPU! As far as I know, there isn’t any CPU requirement specified by Android 2.2.

@Scott- I had a fortune of playing with couple of different phones sporting different Android versions recently and realized that one showed availability whereas other one didn’t! So clearly either the Marketplace or the Flash player knows the version of the OS/device requesting the download. I think for Flash, the fragmentation would be no different for any other application. If I was to look at the comments made on different Android applications that I tried till date- some of them work well on some phones and not on others. So Flash applications would be similar - they may work on Droid but not on Samsung Vibrant for example. But for Flash applications, the publisher could clearly specify that ‘Flash player 10 required’.

]]>
By: Scott Janousek http://www.embeddedflash.com/?p=711#comment-28032 Scott Janousek
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Sat, 09 Oct 2010 13:39:56 +0000
http://www.embeddedflash.com/?p=711#comment-28032 At least new bits can be sent OTA to a lot of these devices. Previously, a stagnant player with a bug would will any app that encountered that bug forcing developers to come up with kludgy workarounds. Flash 10.1 is not perfect, but it's a step up from some of the issues experienced with Flash Lite. I am curious to see just how much frag affects all these Android devices running Flash 10.1 At least new bits can be sent OTA to a lot of these devices. Previously, a stagnant player with a bug would will any app that encountered that bug forcing developers to come up with kludgy workarounds.

Flash 10.1 is not perfect, but it’s a step up from some of the issues experienced with Flash Lite.

I am curious to see just how much frag affects all these Android devices running Flash 10.1

]]>
By: Hayden http://www.embeddedflash.com/?p=711#comment-27257 Hayden
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Tue, 21 Sep 2010 19:30:18 +0000
http://www.embeddedflash.com/?p=711#comment-27257 Has adobe published the minimum hardware requirements for Flash 10 for Android 2.2? Are these hardware requirements different than what Google recommends for a device to run Android 2.2 (with or without Flash)? Is it likely there will be devices that have minimum requirements for 2.2 but not for Flash 10? Has adobe published the minimum hardware requirements for Flash 10 for Android 2.2?

Are these hardware requirements different than what Google recommends for a device to run Android 2.2 (with or without Flash)?

Is it likely there will be devices that have minimum requirements for 2.2 but not for Flash 10?

]]>
By: TJ Downes http://www.embeddedflash.com/?p=711#comment-27248 TJ Downes
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Tue, 21 Sep 2010 14:18:52 +0000
http://www.embeddedflash.com/?p=711#comment-27248 Interesting, thanks for the info. It will be interesting to see how Adobe handles this moving forward and how much of a challenge this proves to be in keep the players updated as more and more devices are introduced. Interesting, thanks for the info. It will be interesting to see how Adobe handles this moving forward and how much of a challenge this proves to be in keep the players updated as more and more devices are introduced.

]]>
By: admin http://www.embeddedflash.com/?p=711#comment-27225 admin
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Tue, 21 Sep 2010 02:14:10 +0000
http://www.embeddedflash.com/?p=711#comment-27225 Well- I don't know what CPU Droid 2 and Galaxy uses, but if the CPUs are different, then yes, they'll need different binary. If the CPUs are the same, then it is upto the chipset and OS implementation. Android provides a uniform API structure for Java application development but Flash requires support from the Linux kernel and there are some loose ends that can cause the binary to behave differently. That is where the certification comes in that ensures that Flash on the device works as it is expected to be. Even with ARM there are plenty of variations- ARM9, ARM11, ARM Cortex A8, XScale etc. In theory, the binaries for ARM are supposed to be compatible but in reality that doesn't always hold up. Well- I don’t know what CPU Droid 2 and Galaxy uses, but if the CPUs are different, then yes, they’ll need different binary. If the CPUs are the same, then it is upto the chipset and OS implementation. Android provides a uniform API structure for Java application development but Flash requires support from the Linux kernel and there are some loose ends that can cause the binary to behave differently. That is where the certification comes in that ensures that Flash on the device works as it is expected to be.

Even with ARM there are plenty of variations- ARM9, ARM11, ARM Cortex A8, XScale etc. In theory, the binaries for ARM are supposed to be compatible but in reality that doesn’t always hold up.

]]>
By: TJ Downes http://www.embeddedflash.com/?p=711#comment-27216 TJ Downes
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Mon, 20 Sep 2010 20:56:18 +0000
http://www.embeddedflash.com/?p=711#comment-27216 Excellent, thanks for the clarification. So to further clarify, are you saying that the current Flash runtime for Android won't run on just any Android 2.2 device using an ARM processor, and that there will need to be a different binary for each Android device type? So, for example, a Droid 2 will have a different binary than a Samsung Galaxy? Excellent, thanks for the clarification. So to further clarify, are you saying that the current Flash runtime for Android won’t run on just any Android 2.2 device using an ARM processor, and that there will need to be a different binary for each Android device type? So, for example, a Droid 2 will have a different binary than a Samsung Galaxy?

]]>
By: admin http://www.embeddedflash.com/?p=711#comment-27215 admin
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Mon, 20 Sep 2010 20:44:27 +0000
http://www.embeddedflash.com/?p=711#comment-27215 Yes- you'll need different binaries on different devices. This is not to say that Adobe can not put together one package at some point that'll contain all the binaries and the relevant binary can be extracted on your phones, but at the moment they all are different. On point #2- Windows OS hides details of the underlying devices from the application by providing common APIs. Linux on the other hand comes in different flavors which can be customized per requirements. For example, Ubuntu Linux and Fedora linux use differnet kernels, could use different UIs (KDE vs Gnome), audio/video interface etc. etc. So lets take an example of X86 device running Ubuntu and Fedora Linux. If the Flash binary is created for Ubuntu, there's no guarantee that it'll run on Fedora because the packages that support audio, video, graphics could be different. Essentially Flash depends on platform for device specific features. Also, the binary created for X86 is not going to work on ARM or MIPS processor. The PC world is quite uniform with Wintel configuration but embedded isn't. So now in addition to the OS dependency, you also have to deal with CPU dependency and create as many binaries. Yes- you’ll need different binaries on different devices. This is not to say that Adobe can not put together one package at some point that’ll contain all the binaries and the relevant binary can be extracted on your phones, but at the moment they all are different.

On point #2- Windows OS hides details of the underlying devices from the application by providing common APIs. Linux on the other hand comes in different flavors which can be customized per requirements. For example, Ubuntu Linux and Fedora linux use differnet kernels, could use different UIs (KDE vs Gnome), audio/video interface etc. etc. So lets take an example of X86 device running Ubuntu and Fedora Linux. If the Flash binary is created for Ubuntu, there’s no guarantee that it’ll run on Fedora because the packages that support audio, video, graphics could be different. Essentially Flash depends on platform for device specific features.

Also, the binary created for X86 is not going to work on ARM or MIPS processor. The PC world is quite uniform with Wintel configuration but embedded isn’t. So now in addition to the OS dependency, you also have to deal with CPU dependency and create as many binaries.

]]>
By: TJ Downes http://www.embeddedflash.com/?p=711#comment-27207 TJ Downes
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/4/d289104336/htdocs/embeddedflash/wp-includes/functions.php on line 41
Mon, 20 Sep 2010 17:04:59 +0000
http://www.embeddedflash.com/?p=711#comment-27207 I'm not sure I follow the point here, but I am under the impression you are saying that Flash for Android won't work on just any Android device? I am especially confused by your comparison to the PC world. PCs come in all flavors, with all sorts of different hardware and CPU combinations, and varying OSes and OS versions. Yet the Flash Player seems to work essentially the same across these operation systems. It seems to me that if Adobe can do this for the PC then they can apply the same techniques to the ARM-based devices that run Android. Would you mind clarifying the main point? Thanks! I’m not sure I follow the point here, but I am under the impression you are saying that Flash for Android won’t work on just any Android device?

I am especially confused by your comparison to the PC world. PCs come in all flavors, with all sorts of different hardware and CPU combinations, and varying OSes and OS versions. Yet the Flash Player seems to work essentially the same across these operation systems. It seems to me that if Adobe can do this for the PC then they can apply the same techniques to the ARM-based devices that run Android.

Would you mind clarifying the main point? Thanks!

]]>