This page is a list of the most common issues encountered by users downloading, installing, and configuring Flash Player for Android. If you are having trouble with Flash Player for a desktop system, visit the troubleshooting guides for Windows or Mac OS.
Select the problem you are encountering from the list below:
Adobe does not control the download or installation mechanism on Android. The Android Market system handles those activities.
The Android Market Known Issues page has some helpful troubleshooting advice for this issue.
Some devices that have shipped with Flash Player pre-loaded have set plug-ins to On Demand or Off by default. This setting could be incorrectly causing some end users to think that Flash Player is broken or not installed correctly. With the “On Demand” setting, for example, users are required to tap the rectangular container for a SWF file within a web page to load it.
It's necessary to ensure that the Android browser has plug-ins set to Always On by pressing the settings button when your browser is open. Then, click More, Settings, and Enable Plug-ins. A pop-up message appears that allows you to adjust your plug-in settings. Make sure that Plug-ins are set to Always On.
If you downloaded Flash Player from the market, you can uninstall by going to Settings > Applications > Manage Applications > Flash Player. Then click Uninstall.
If you're only presented with the Uninstall Updates option, it's because Flash Player was included on your phone by the manufacturer. Adobe has no control over the installation process in this scenario. It is subject to the behaviors configured by the manufacturer. In most instances, you cannot delete Flash Player (or any of the other applications pre-packaged on your device).
Flash Player for Android requires a CPU with support for the ARMv7-A instruction set. This instruction set allows the level of performance required for acceptable multimedia playback.
If your device has an ARM11 CPU, it only supports the ARMv6 instruction set. You can view a full list of Flash Player for Android devices on the certified devices page.
Note: For a detailed list of the system requirements for Flash Player for Android, see the system requirements page.
In some cases, you can encounter an error stating that the Flash Player for Android binary is not signed. Adobe ensures that the Flash Player binary is correctly signed. However, occasionally the Market application on your device is not able to correctly verify that.
Adobe has found that it is helpful to clear the Market cache on your device in this instance. Clearing the caches force it to reload the Market catalog, and the certificates necessary to validate that applications can be trusted.
To clear the Market cache, go to Settings > Applications > Manage Applications > All > Market and press Force Kill. Then click Clear Cache.
Press the Home button to return to the main menu. Then open the Market and search for Flash Player and try your installation again.
Because Flash Player is a browser plug-in and not a stand-alone app, Adobe can't enable movement to the SD card. Flash Player is dependent on the Android Browser and must be in the same data partition to load correctly.
There are some unofficial workarounds on various android forums. While they are unsupported and can yield unpredictable behavior in the player, they seem to work for many people. If you're desperate for internal storage space, that can be a good way to maximize the capabilities if your device's hardware.
With regard to the size of the binary distribution, the size of the code base is due to the complexity behind supporting so many Android devices. It's also due to the rapid innovation on the part of phone and hardware manufacturers. It's necessary for Flash Player to deliver optimized playback on hundreds of Android phones and tablets. (And these devices run various GPU and CPU architectures.)
The size of the code base is reflective of the complexity and fragmentation between the number of Android devices and the rapid innovation by device manufacturers.
Adobe is conscious of the distribution size and has taken every step possible to reduce the size of the compressed and installed binaries. Adobe spends much time and energy on keeping the player as small as it is. Any additional trade-offs that Adobe could make between file size would come at the expense of execution speed. A reduction in execution speed negatively affects video and multimedia playback performance. (And, it doesn't yield enough of an improvement to make the trade-off worthwhile.) Adobe feels it's arrived at the right balance.
To give you some perspective, current well-equipped Android phone models ship with at least 1 GB of internal phone storage. In this context, Flash Player's 12-MB footprint is negligible. While Adobe understands the impact on devices with minimal internal storage, there's not much Adobe can do for these legacy phones.