Difference between revisions of "Adding flash support"
| Line 48: | Line 48: | ||
==== Step 6. Edit system files ==== | ==== Step 6. Edit system files ==== | ||
| + | ''Obsolete as of 21/03/2011.'' | ||
| + | |||
Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!) | Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!) | ||
:<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line: | :<br />Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line: | ||
Revision as of 21:20, 21 March 2011
Adobe Flash
Adobe Flash is not included in this webOS 2.1 doctor, but can be added with files from a VZW Pre 2 2.0.1 doctor.
Adding Flash Support
The easiest way to enable Adobe Flash on your webOS 2.1.0 legacy device is by creating a modular package and installing that, along with a patch to make the Adobe Flash preferences visible in the browser.
Step 1. Prerequisites
- Download the Verizon 2.0.1 Pre 2 Doctor (here)
- Download Jason Robitaille's IPK Packager (here)
- Download webOS Quick Install (here)
- Download temporary directory (here) and unzip the FlashPluginContainer folder to your desktop
- Download patch to enable Flash preferences in the browser (here)
Step 2. Unpack
- Open the 2.0.1 doctor with an archive manager, like 7zip. Navigate to "
resources/webOS.tar/./nova-cust-image-roadrunner.rootfs.tar.gz/./" This is where the Flash files are stored. - Extract the following files from the webOS ROM:
/etc/adobe/mms.cfg
/etc/adobe/oem.cfg
/usr/lib/BrowserServerPlugins/libflashplayer.so
/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
/usr/lib/libFlashGraphics.so
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so
Step 3. Drag 'N' Drop
- Simply place the files from the ROM into the FlashPluginContainer folder in their respective locations.
- Pay close attention to where each file/folder is stored inside the webOS ROM.
Step 4. Packaging
- Open Jason's IPK Packager and point the program to the files folder. Do NOT point to FlashPluginContainer, as the install will fail.
- The rest of the fields will populate on their own.
- Save the IPK file somewhere using "Create IPK Package." You may want to keep it handy.
Step 5. Wrap Up
- Use webOS Quick Install to install both IPK and patch.
Note: The patch to enable Flash preferences is also available in Preware.
Step 6. Edit system files
Obsolete as of 21/03/2011.
Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
this.controller.get("flashPref").hide();
this.controller.get("autoLoadPref").hide();
Step 7. Reboot
Reboot your devices for changes to take effect
Support thread: http://forums.precentral.net/canuck-coding/276703-how-get-flash-legacy-devices-2-1-0-a.html
Adding Flash Support Manually
- Extract WebOS.tar from the Resources folder in the VZW doctor to a location on your hard drive
- Copy the following files from the extracted WebOS.tar to their equivalent locations in your MetaDoctor (alternatively, you can copy them manually to a live device using Novaterm)
/etc/adobe/mms.cfg
/etc/adobe/oem.cfg
/usr/lib/BrowserServerPlugins/libflashplayer.so
/usr/lib/BrowserServerPlugins/resource/plugin-icon-noplay.png
/usr/lib/BrowserServerPlugins/resource/plugin-icon-play-down.png
/usr/lib/BrowserServerPlugins/resource/plugin-icon-play.png
/usr/lib/BrowserServerPlugins/resource/plugin-icon-unknown.png
/usr/lib/BrowserServerPlugins/resource/plugin-scrim.png
/usr/lib/libFlashGraphics.so
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-noplay.png
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-play.png
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-icon-unknown.png
/usr/lib/BrowserServerPlugins/FlashMiniAdapterData/plugin-scrim.png
/usr/lib/BrowserServerPlugins/FlashMiniPlugin.so
- 3. Open /usr/palm/applications/com.palm.app.browser/app/controllers/preferences-assistant.js (either in your MetaDoctor or on your live device -if on a live device, remember to make a backup!)
Find the following two lines (should be lines 46 & 47) and comment them out by adding // to the beginning of each line:
this.controller.get("flashPref").hide();
this.controller.get("autoLoadPref").hide();
- 4. Reboot your Pre if the editing was done on a live device
Flash preferences should now be visible under browser preferences.
Flash Troubleshooting
After adding Flash support, you may find that visiting any page with the browser will never completely load, and then automatically refresh in a loop. Disabling and the enabling Flash content in the browser preferences will fix this issue.