Sure, that’s the final solution if you don’t want to even start understanding why something is not working, and it could be the right solution if you don’t care about the data you could lose together with the installation, or if you do not have a lot of customizations running, but guess what? Chance is that at some point, while restoring the system to his previous state, the same conditions that caused the first malfunction will recur, catapulting you back to the beginning.

If you’re reading this, you’re possibly willing to better your knowledge of the OS involved and tinkering with it. Keep in mind that if you’re learning something about it, next time it will be easy to understand and solve a problem, you will also be faster at moving around and testing things.

“Clean” images and backups.
Do you already have an image of your disk with a clean installation? No more data to backup before wiping everything? No customizations done after image creation or new applications installed? Hardware changes?
Image creation is optimal for companies were you have a lot of machines with the same exact configuration, or servers where is easy to schedule incremental backups and there aren’t a lot of modifications going on, but is not always good for small firms or personal use. Keep also in mind the time needed to create the images every time a substantial change occurs in your system.

Solving the problems
Today, even in Windows OS, almost any software issue can be solved, you just have to start digging in the right direction. For Linux and generally Unix-based OSes it’s practically impossible to get to a problematic condition that can only be solved by a new, clean installation. The Win95 era, when after the wrong driver and a pair of uninstalls wasn’t possible to clean up the mess, is almost finished.
You biggest friend here is The Internet, there’s an high probability that someone else had the same problem and solved it, or is at least able to point you in the right direction.

This is an actions shortlist you can use to diagnose and correct the problems, you can see an ugly flow chart (scanned from cheese paper) representing it on the left:

Diagnostic flow chart for everyone

1. Define the problem (or problems, one at a time)

Is it hardware or software, is it related to what or to which component?

2. Are you able to solve it in an easy manner?
Reinstall a single program, update or replace a driver,…

3. No, let’s get more info, search for it on the net from multiple sources
Follow the leads, search for error messages and codes to better understand them, search for configurations and problems that are similar but maybe spelled differently. Try some diagnostic software (or targeted antivirus, or whatever applies to your case)

4. Are there instructions to solve it and they’re working?

5. No, let’s do some deduction and link the problem to known issues, enlarging the initial search and, if needed, putting some assumptions in place.

6. Further research on the subjects suggested by the previous point. Extrapolate possible solutions and try them.

7. Is the solution working?

8. No, more research on the general subject is needed to have a better understanding of it: do it!

9. Go back to 5 and change the parameters or assumptions as the research suggested

Conclusion.
So it’s a decision between:

1)the time needed to preserve all your data and bring back the system to the same level of functionality, configuration and customization and

2)digging and finding the real problem and solving it.
The choice depends on how much you feel comfortable in learning and understanding the technical issues and solving them and how much you like to (mainly) wait for reinstallation, remembering all the stuff there was, and of course the “backup and restore” of data.

Also, maybe you don’t like redoing the same exact things you’ve done at least once before….

Of course if you don’t have an overall knowledge of hardware and software you cannot start by digging in complex problems, but many common felons, including most spywares, adwares and common viruses, are enemies you can easily tackle.

And next time you’ll be ready for something uglier!

The post Computer systems diagnostics for everyone (on reinstalling OSes) appeared first on Scattered Islands.

I’m using version 1.1.6, maybe the issue will be solved in future releases. That’s the plugin homepage: http://www.wpbeginner.com/floating-social-bar/.

Modified Floating Social Bar Graphics w/ transparency

To customize the background and top and bottom bars color:

the file “class-floating-social-bar.php” in “/wp-content/plugins/floating-social-bar/” contains the background and colors settings (search for “background” and “color”), you can easily edit it by using WordPress interface:

Plugins -> Installed Plugins -> Edit (under Floating Social Bar), on the right you have all the editable files related to the plugin.

Also the areas around each icon stay white, it’s a problem with the png file image stored here:

“/wp-content/plugins/floating-social-bar/images/fsb-sprite_1.png”.

For my needs, at the end I modified directly the png file containing the graphics (if you’re willing to do the same, you will need to upload the new file to your installation directory on the hosted space/server).

It’s possible not to overwrite the file, instead changing name and folder references from the previous php file.

The white background around the icons can be changed to your color, or you can just remove it and make it transparent (it’s a .png, so alpha channel or transparency information can be included in it), so it will show what’s underneath, also you can probably use the file shown above, if you save it in png format.

The post WordPress Floating Social Bar plugin and background color appeared first on Scattered Islands.

The problem shows up a few minutes after booting, sometimes the error message is displayed while other apps are running. If, after getting the error, apps that use the camera directly (usually torch and camera) are opened they get stuck for several seconds, later giving another error message.

It’s not an hardware issue because just after rebooting or turning on the phone everything works fine, the problem affects camera and torch applications (both kinds want to access the camera resource). I’ve done some researches and testing, full of articles suggesting the clearing of data and cache from the camera apps, uninstall of all torch apps, factory resetting the phone*, wiping it*, camera’s firmware version changes, etc.

At the end the FASTEST AND SIMPLEST SOLUTION for me was: just clear cache and data from camera and all the other apps using it, remember to save your relevant saved data from each application if you have some. In my case the culprit was the default Gallery app, it has camera access permissions because it can switch to camera mode. When I deleted cache and data my photos weren’t deleted, but you probably wouldn’t take any chances.

To do so you can easily go to Settings -> Applications -> Manage applications, and don’t forget to reboot the phone afterwards. “Clear cache” removes temporary files related to the app, while “clear data” restores it to a clean install, removing settings, saves, etc.

That’s it, now it’s almost 2 weeks without problems so I guess it’s gone..

From what I’ve read the same thing shows up with different phone models, mostly Samsung, so the solution is probably the same if the same error is displayed.

If you want to read some more info on the matter and find some useful apps related to permissions management and diagnostic, I’ve found THIS to be a good source.

Onward!:
Verify if the XPrivacy system is commonly circumvented, if not let’s try it…

*before doing something drastic, read my other article on fully reinstalling OSes

The post Android smartphone: failed to initialize camera appeared first on Scattered Islands.