Blame Google if you will for this innovation, but Pepper came about because of a collaboration between Adobe and Google to reduce the need for a standalone program on the O/S. The first steps of Pepper are the first steps toward a seamless integration of browser and O/S implementation during use… like it or not.

If It Doesn’t Work Across the Board, How Can It Be Good?

Pepper might not be a plugin that has 100% implementation, but it does carry with it come advantages that are worth considering. At the top of the list is the fact that this program is supposed to more secure than Adobe is. That’s great if you’re using a fairly modern PC that has the speed capabilities to handle the plugin and the media you’re attempting to view. Older PCs, however, tend to struggle with Pepper and that can create problems.

From a running standpoint, the Flash does seem to work a little quicker when using Pepper within Chrome than it does if you’re using the Adobe version from your O/S. Maybe it was just in perception only, but the stability of the entire experience was a little better, which made the full UX better from and end user perspective. It’s also super easy to disable if you wish, and that’s a benefit for many too.

So You Need To Disable Pepper…

Whether it is because of personal preferences, apps that don’t recognize the plugin, or you’ve got an ancient PC that won’t even accept a newer version of Adobe’s Flash, then disabling Pepper becomes the priority. Here’s how you can make that happen in just a couple of clicks.

1. Go into the plugins page for your Chrome browser. Type in chrome://plugins into the URL address bar.
2. Hit the + box next to Details on the far right of the screen in the Plugins bar.
3. Find Flash. You could have 3 or more files in this section.
4. Look for the Shockwave Flash version that has “PepperFlash” in its location.
5. Click the “Disable” link.
6. Close and restart Chrome.

Once you’ve taken these steps, you won’t have to worry about Pepper any more. As with any new programming, it takes time for 100% implementation to occur, so you may need to take these steps now. In the future, however, PepperFlash could be the upgrade the internet has been wanting to make interacting with each other in a faster way that is much more fun.

One of those plugins that you’ve got to install right away is the Adobe Flash plugin. It works just as well as it does in any other O/S or browser, but there are a few things you should know.

It Works Much Better In the SUSEfox Extension

Meant to be for a group of features that were just too massive for the general modifications of Firefox into the openSUSE system, this is an optional feature to consider using because it doesn’t alter the functionality of Firefox when it is disabled. What’s nice about this is the improved plugin finder service because it includes many of the plugins that are available in the various repositories. Forget about using just the latest version of Flash, for example, because you’ll get access to the various Flash players that are compatible with your O/S.

The RPM package flash player should be installed on the first run of your manager, but you can install it manually if you need to do so. That’s the flexibility that is nice about openSUSE. Just remember that the main repository NON-OSS is required and you’ll be good to go.

The Plugin Also Operates As a Standalone Player

Unlike the other O/S installations or browser plugins, the Flash plugin for openSUSE can double for you as a standalone player. This gives you the high level of functionality that you need for your PC without the headaches that other users have on other systems. If you love Linux and want to be watching any sort of multimedia content online, then you’ve got to use the plugin. It’s thankfully convenient and easy, so it’s not much of a hassle for the average openSUSE user.

For those who are looking for alternatives and may not be as savvy from a tech standpoint, however, the plugin is going to cause some difficulties to get going. For the most part, as long as you find the Adobe RPM from their Flash installation page and then just open the file that you’ve downloaded with the Apper Installer and you should be ready for some online video action. You can go into the about, plugins screen to confirm if it is there.

It’s really nice to see that in this current day and age when an O/S can go for hundreds of bucks when you consider all the extra apps and add-ons that people want that you can pick up something that’s good for more sweat equity than monetary equity. Use this plugin and you’ll have the same experience, if not a better one, that every other person does. Period.

Is there a way that this can be fixed?

The Problem Is the Lack of Adobe Support

The reason why Flash and Android aren’t the best of friends is because Adobe stopped supporting Flash content on Android devices that are 4.1+. Before getting rid of Dolphin for something else, however, it is possible to get Flash support within the browser itself instead. You must manually enable Flash support from within the browser. Dolphin Jetpack will then work to stabilize the viewed content that requires Flash.

The first thing you’ve got to do is install the Flash Player app onto your device. That can be done in a couple minutes and just put that exact thought into a search string: Flash Player app for Android. Once you’ve installed that, you simply go to the Settings command in Dolphin. Select “Web Content,” and then select “Flash Player.” Then you’re ready to use the Jetpack plugin.

But I Did This And I Got an Error! What Gives?

So not every Android device actually allows for you to enable the Flash settings within the Dolphin browser, even though it says that it does. You can go through the above steps, attempt to enable Flash, and you’ll get an error message that says Flash can’t work on devices such as yours. If that’s you, then you need to go deal with the root access on your device.

What you’ve got to do is delete the setting’s preferences file that Dolphin uses. When this happens, you’ll force Dolphin to recreate the file with the default values. That means you’ll also have to go back and reset all of your personal preferences, but there’s a good chance that you’ll have the ability to access Adobe Flash through Dolphin once again.

And here’s a final tip for consideration: Adobe offers archived versions of Flash to download on their website. Go into the Android 4.0 archives and make sure that you’re downloading the version that was created to be compatible with your device. When you do that, you’ll automatically activate Jetpack and get all the Flash content you love from the browser without having to download zillions of apps to be productive.

The Problem is the Relationship With Adobe Flash

Unlike other web browsers, Google Chrome and Adobe flash would never be considered BFFs. When using Flash, you’re subjecting yourself to slow downs and crashes that can leave you so annoyed that you’d be willing to stop using all Google products forever. It happens because Chrome calls upon the internal installation of Flash within its browser, whereas the other browsers call upon the installation of the operating system.

On a good day, you can’t tell the difference. The problem starts when Chrome tries to use both installations of Flash that are on your system. Yeah that’s right… Chrome has Flash and your O/S has Flash and when both are used, you don’t get supersonic speed. You get a locked-up internet browser that crashes all of your active windows.

How Can This Get Fixed?

It’s important to note that the Shockwave warning you get doesn’t have anything to do with the Shockwave program. The resolution of this problem is pretty simple. You just need to get into the plugin settings for Chrome and disable the browser’s internal installation of Flash manually. It’s very important that you disable the AppData folder one and not the installation that acts as the one for the O/S.

Once you’ve done this, then you just need to close your browser windows. Don’t refresh the closed tabs if you get the option when you restart Chrome. From there, all you’ve got to do is resume your normal browsing and it should happen in real-time for you.

Are there any consequences to this action? The only real problem that you’ll have is that you’ll need to manually check for updates of Flash because the browser won’t automatically update.

What About Software Conflicts?

The other issue with this Shockwave error is that sometimes software or malware can make Chrome conflict with your computer. You can check if this is going on by going to the Chrome conflicts page [chrome://conflicts] to see if you’ve got any warnings going on. Update the software as necessary, remove the malware, and you should be set. Worst case scenario? Turn off your O/S Flash anyway and see what happens.

The Shockwave crash can be pretty irritating, but it can also be fixed in just a couple minutes. Now stop being annoyed and get back to being productive.