Release notes | Flash Player 10.2 | Android

Flash Player 10.2 for Android Release Notes

Welcome to Adobe Flash Player 10.2 software!  This document is for users installing Flash Player 10.2 on devices and for developers creating content for Flash Player 10.2. It addresses issues that are not discussed in the Flash Professional or Flex documentation. This document may be updated periodically for updated releases, and as more information becomes available.

Read these Release Notes carefully before downloading Flash Player 10.2 for Android. 

The current build number for Flash Player 10.2 for Android 2.2 and above is 10.2.157.51.  Flash Player 10.2 is a production GA (General Availability) release for Android 2.2 (Froyo), 2.3 (Gingerbread), and Android 3.01 (Honeycomb) devices.

System Requirements

Features and Enhancements

Fixes and Enhancements

Known Issues and Limitations

Reporting Issues

For current Flash Player system requirements, visit http://www.adobe.com/products/flashplayer/systemreqs/index.html#mobile. 

To view a list of certified devices, visit http://www.adobe.com/flashplatform/certified_devices/

Flash Player 10.2 is the newest runtime release of the Open Screen Project that enables uncompromised Web browsing of expressive applications, content and video across devices. For a general overview of new features and enhancements, visit the Flash Player 10.2 release notes: http://kb2.adobe.com/cps/890/cpsid_89050.html.

Hardware accelerated video rendering for H.264 (On upcoming Honeycomb OS release only)

Flash Player 10.2 leverages the Stage Video rendering pipeline to enable users of Android 3.0 tablets, like the Motorola Xoom, to enjoy smooth playback of high-definition  video in Flash Player.   Users will experience reduced CPU usage and higher frame rates for existing H.264 video content.

Deeper integration with the Android browser rendering engine (Android 3.01+ only)

Deeper integration of Flash Player and the enhanced Android 3.0 browser delivers faster and better rendering of rich, interactive web content resulting in a smoother and more responsive browsing experience. 

Flash Player can now render content as part of the web page along with other components such as HTML, images and gif animation. As a result, users will experience:

• Improved scrolling of web pages.
• Uncompromised viewing of rich, immersive content in the way intended by the page designer, including support for instances where HTML and other web content is composited over Flash Player rendered content.  Flash Player rendered content will continue to be placed in a separate window on top of HTML in the Android 2.2 and 2.3 browsers, as these browsers do not support the new Android 3.0 browser rendering model. 

Enhanced performance for the latest smartphones and tablets

Experience performance improvements designed to take advantage of the current generation of multi-core, GPU-enabled processors to deliver videos, games and other interactive Web content on the latest smartphones and tablets.

Automatic soft keyboard support

Users of touch screen devices will enjoy a more optimized experience interacting with rich content that requires keyboard input.  This feature simplifies the development of multiscreen applications that require keyboard input, making it easier for developers to optimize desktop applications for mobile devices. A new ActionScript API enables developers to automatically launch and display the soft keyboard. 

Fixes and Enhancements in Flash Player 10.2.157.51

• Adobe Flash Player 10.2.157.51 includes security enhancements described in Security Bulletins APSB11-02 (http://www.adobe.com/go/apsb11-02), APSA11-01 (http://www.adobe.com/go/apsa11-01), and APSB11-07 (http://www.adobe.com/go/apsb11-07).

Input:

• Soft keyboard is now launched when placing focus on a Text Layout Framework TextField.  (2733101)
• Improved resolution of touch coordinates; coordinates are now returned as floating point values, not integers.  (2798815)

Rendering:

•  getChildAt() returns correct values (2652935)

The following fixes are enabled for devices running Android 3.0 and higher:

• SWF content is now rendered at the appropriate depth in relation to other SWF and HTML content, including pop-ups.
• Overlapping SWF content now renders consistently at the same depth.
• Values for stage.fullScreenHeight and stage.fullScreenWidth are now correctly updated when the screen orientation changes from landscape to portrait.
• Crashes related to playing content while zoomed in have been resolved.

Video:

• Improved video performance of 10-15% on Qualcomm chipsets (2769706)
• Improved H.264 stream detection logic addresses playback problems with various non-standard encoding combinations (2769727)
• H.264 hardware decoding is enabled for Samsung devices with capable firmware (2796583)
• Fixed an issue where audio in a limited subset of H.264 videos was broken after upgrading to Android 2.3.3 (2818355)
  
  

This section documents known issues and limitations specific to Android. For additional information on known issues and limitations for Flash Player 10.2, visit the release notes. [http://kb2.adobe.com/cps/838/cpsid_83808.html#main_known issues]

Audio/Video:

• Playback pauses briefly when switching between multiple tabs that are simultaneously playing video (2804839)
• H.264 video wrapped in MP4 does not play (2800033)
• Audio and video streams can become out of sync when using RTMP Live Dynamic Streaming after bitrate transitions or re-buffering events (2789793)
• Peer-to-peer streaming with the RTMFP protocol does not work on mobile devices at this time. (2786105)
• AAC HE streaming over RTMP plays in Mono, and some frequencies above 8khz are truncated. (2763462)(FP-5749)
• If Flash Player encounters an untrusted SSL certificate when negotiating an RTMPS stream, the user will not be presented with a dialog allowing them to override the security problem, and the connection will automatically abort. (2790903)
• On Android 3.0+, an OS bug causes a hang when switching between the native camera application and a browser playing Flash video. (2803760)
• Seeking backwards requires streaming video to re-buffer in order to minimize memory usage for streaming video on mobile devices.  Flash Player uses a small circular buffer.  When seeking backwards in a video stream, Flash will flush and refill the buffer before resuming playback.  This will introduce a brief pause as the player fills the video buffer. (2807353)
• On the HTC Desire HD, a driver bug causes all video to fall back to software rendering. (2811530)
• There is a two second delay when switching bitrates in a multi-bitrate stream. (2829252)
• On Droid X running Android 2.3, a driver issue prevents videos larger than 800x480 from using hardware accleration. (2837476)

Browser Integration:

• Running SWF files on the Samsung Vibrant with Android 2.2 update results in a crash of the system browser (2796396)
• If an HTML element overlaps a SWF, a click on the overlapping element will be erroneously registered by the SWF. (2662317)
• When navigating to a page with SWF content using the Back button, Flash Player is given incorrect surface dimensions causing the SWF to render at an incorrect size; this can cause mouse event accuracy issues because the events may not get registered to the correct targets. (2827614)
• Paths to local files (i.e. file:///) are not supported when Flash Player is invoked in a WebView (2759306)
• In Android 3.0+, Screen Orientation locking does not work. (2795001)
• On Android 3.0+, the brower can sometimes provide Flash with incorrect coordinates for the window's top left corner.  This can cause Flash to draw in the incorrect place, obscuring HTML content.  (2800211)
• On Android 3.0+, a Browser bug causes video playback in pop-up windows to render incorrectly. (2814768)
• On Android 3.0+, a Browser bug creates rendering issues when scrolling a web page below an open pop-up window. (2823753)
• On Android 3.0+, a Browser bug prevents the Flash Player long-tap context menu from being displayed on m.armorgames.com. (2833380)
• On Android 3.0+, Browser scrolling performance on pages with more than 10 Flash instances has degraded. (2834606)
• On Android 3.0+, when changing screen orientation, there may be a slight delay in updating to the correct Flash texture, causing the browser to display a stale texture briefly after the transition.  This can appear to users like an application is cycling through multiple sized to try to fit to the screen. (2837272)
• On Android 3.0+, multiple browser bugs related to reporting the size of drawing surfaces available to or used by Flash Player cause some content to display like they're stretched, and/or corrupted. (2836132)
• On Android 3.0+, the Browser sometimes renders SWFs outside of an iFrame that should contain them. (2838159)

Input:

• Third Party on-screen keyboards are not supported at this time (2785832)
• In embedded mode, the second Mouse Down event normally generated by two consecutive double-taps is not fired (2803167)
• On the HTC G2, Flash Player stops responding when the keyboard is out and content remains frozen until the keyboard is dismissed. (2796202)
• After changing focus from an HTML text field to a Flash text field, the first single tap on a text field does not launch the soft keyboard (2783298)
• If a user taps twice outside of a text field, then taps the text field, the paragraph will be selected erroneously (2780650)
• Swiping across a text field to highlight the contents erroneously dismisses the virtual keyboard (2752919)
• The Area of Interest for the on-screen keyboard is sometimes erroneously shifted right by a few pixels (2743899)
• Cannot input Simplified Chinese characters into Text Layout Framework TextField using Google Pinyin and Sogou Pinyin. (2662299)
• Bitmap Objects with an Alpha value other than 1 experience problems with Mouse.CLICK events when the user presses on the bitmap 10 - 20 times in rapid succession (2659371)
• Keyboard.physicalKeyboardType returns ‘alphanumeric’ instead of ‘none’ on Nexus One (2728953)
• Users cannot select multiple lines of text in a multi-line TextField (2785064)
• Using Android 2.3, some users may encounter an infrequent crash when changing between input languages (2820315)
• Input events are not handled by SWFs in pop-up windows (2795184)
• On Android 3.0+, the browser does not respect the VisibleRectBounds provided by the Flash window.  From a user perspective, this can appear as a textfield that shifts or appears at the wrong scale when the soft keyboard is invoked. (2833636)

Memory Management:

• Out of Memory and Click To Play icons will not be displayed for SWFs less than 64 x 64 pixels in size (2795258)
• When a SWF goes out of memory (OOM), all running Flash Player instances should go OOM, but SWFs in different tabs sometimes stay in Click To Play mode instead. (2828509)

Performance:

• There is a very slight delay when a sound is played as the result of a Mouse or Touch event. (2671510)

Rendering:

• GraphicsBitmapFill.smooth = true is ignored on Android.  (2710762)
• As a rendering optimization for the Android platform, Bitmap Smoothing is disabled globally for Android devices
• When the blend modes DARKEN, SUBTRACT, DIFFERENCE, LIGHTEN, MULTIPLY and OVER are applied to Bitmaps, Fills and Gradients, they are rendered differently on devices with the GPU enabled. (2769642)
• On some devices, there is an infrequent problem where the ENTER_FRAME event does not fire in full-screen unless the user is interacting with the content.  Users can workaround the bug by refreshing the content. (2799920)(FP-6048)
• Flash content will flicker briefly when the users pinch-zooms in or out. (Android 2.2 and 2.3 only) (2822479)
• When running Android 3.0+, 1 x 1 pixel SWFs are not displayed; anything larger is rendered correctly. (2821993)
• On Android 3.0+, putting the SWF in focus enlarges items on the stage.  This can cause some SWFs to appear over-sized on a web page, and/or can cause some clicks to affect the wrong area of the SWF. (2803075)
• On Android 3.0+, the entire browser page is redrawn whenever the SWF content changes and updates its view.  This can lead to a performance lag for some SWFs rendered in embedded ,mode. (2809121)
  
  
• On Android 3.01 only, a Browser bug where OnSurfaceChanged events are inconsistently broadcast, causes intermittent problems in drawing some Flash content.  This generally appears to users as content that doesn't paint correctly, appears squished/stretched, as inconsistencies observed while pinch-zooming, and as buttons that do not respond to clicks.  (2810538)
• On Android 3.01 only, putting the SWF in focus enlarges items on the stage.  This can cause some SWFs to appear over-sized on a web page, and/or can cause some clicks to affect the wrong area of the SWF. (2803075)
• On Android 3.01 only, the entire browser page is redrawn whenever the SWF content changes and updates its view.  This can lead to a performance lag for some SWFs rendered in embedded mode. (2809121)
• When using hardware accelerated rendering, the Invert blendmode is ignored. (2779437)
• On the HTC Desire, all rendering stops when entering full-screen from a Landscape orientation.  Users can work around this issue by invoking Full Screen Mode while holding the phone in a Portrait orientation. (2834712)
• On Android 3.0+, Android applications that use Browser Plug-ins like Flash Player in WebView applications must have android:hardwareAcceleration set to True in their AndroidMainfest.xml for any plug-in output to be rendered. (2834793)
• On the HTC Desire HD, there is a unique rendering issue on some content which causes content to look black and white, and/or be missing several layers of rendered objects. (2841993)

Text:

• Text descent in multi-line text is clipped with autoSize=LEFT (2800633)
• Users cannot select multiple lines of text in a textfield (2785064) 
• On the HTC Desire HD, the soft keyboard does not pop up after focus is placed in a text input field. (2841966)
• On the HTC Desire HD, FTE CJK characters aren't displayed. (2841970)

Found a bug? Please send the detailed bug information via the online Adobe Bug and Issue Management System

SWF-based H.264 video may be decoded by your graphics hardware. There may be video bugs that can only be reproduced with your particular video card and driver. When reporting a bug involving video, it is essential to note your graphics card and driver, along with your operating system and browser, so that we can reproduce and investigate issues. Please be sure to include this information as described in Instructions for Reporting Video Bugs.

Note: Due to the high volume of email we receive, we are unable to respond to every request.

Thank you for using Adobe Flash Player and for taking the time to send us your feedback!