Samsung Galaxy S – “The device is in use. Stop using the device then try again”

Samsung Kies, another error but at least this one isn’t really it’s fault. This error seems to be caused by the Galaxy S ‘One Click Lag Fix’ (OCLF) so it’s pretty easy to get around. Just unmount your phone if you haven’t already done it and then boot up the OCLF app and then hit ‘Undo OneClickLagFix V2+’ it takes a while but once you’re done you are done.

Samsung Galaxy S – Samsung Kies Connection Error

Okay so I went to check if I could get the SGS Froyo update which seems to be getting rolled out across the UK a little earlier than expected. I booted my laptop into Windows 7 64-bit, loaded Kies and was prompted to update it and once it was done I tried connected my SGS via USB and putting it in to Kies mode. Here’s where the error came about, it’d just sit there “connecting” on the Kies software on my laptop but just switching between MTP Application and the home screen on my phone.

Browsing the net I found a few “fixes” which involved deleting applications on my phone such as Soundhound (which I have never had) or more extreme and formatting the internal SD card only to have everything wiped.

The problem here though is actually just the drivers for 64-bit Win7 cannot handle corrupt data or bad files which are pretty common (say an app is loading an image from the net and you close it half way through BAM, broken file.)

So in order to fix this most annoying of errors you’re going to have to find those corrupt files on your phones memory.

  1. Close Samsung Kies
  2. Connect your phone and select ‘Mass Storage’ mode
  3. Mount USB via the notification bar
  4. Remove any corrupt files from the phones SD cards
    1. You can use this FileSearcherforKiesFix.zip to locate corrupt files
    2. Once found, navigate to the directory and remove them
    3. Research until none are found.
  5. Unmount, disconnect and reconnect the phone
  6. Open Kies and select the Kies option, it should now boot connect without any issues.

Source: (Post #50)  http://android.modaco.com/content-page/311526/samsung-galaxy-s-problems/page/40/

The list of sources could not be read – Ubuntu

E: Type ‘n’ is not known on line 2 in source list /etc/apt/sources.list.d/bean123ch-burg-lucid.list

E: The list of sources could not be read.

To fix this or similar errors open the file, for example “/etc/apt/sources.list.d/bean123ch-burg-lucid.list” and check for rouge characters. In this case there was new line with the letter ‘n’ in place, removing it solved the issue. Make sure to run “sudo apt-get update” to refresh the sources and everything should be fixed. I was also unable to see any software in the “Ubuntu Software Center” because of this.

HowTo: Fix “Briefly unavailable for scheduled maintenance. Check back in a minute.”

After installing an update to WordPress I received the error:

“Briefly unavailable for scheduled maintenance. Check back in a minute.”

I was unsure if this was down to my hosts servers being temporarily down, going down during the update or if WordPress had simply failed to update whatever it was updating. Turns out it was the latter and it’s really easy to fix, first log on to your ftp, file manager or whatever for your hosting and browse to your wordpress install, in the root of this there should be a .maintenance file, just delete this and everything should be back to normal. Once back in the WordPress dashboard you may be asked to reinstall whatever failed however sometimes it will have completed the install and just not managed to delete this file.

GIMP (2.6.8) Crashing On Some Toolbox Icons – Lucid

:~$ gimp
gimp: fatal error: Failed to register GObject with DBusConnection

(script-fu:3100): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

I fixed this error by removing opening Synaptic Package Manager and searching for appmenu-gtk, right click and mark for removal, once this has been done it should begin to work again.

HowTo: Fix “An error occurred while mounting” – Ubuntu Lucid (10.04)

An error occurred while mounting /dev/bus/usb (and/or)
An error occurred while mounting /proc/bus/usb

Press S to skip mounting or M for manual recovery

If you are seeing this error on boot an easy way to get rid:

  1. sudo gedit /etc/fstab
  2. Fine the following line (or lines if you are having both errors)
  3. none /proc/bus/usb usbfs defaults,devmode=0666 0 0
    none /dev/bus/usb usbfs defaults,devmode=0666 0 0

  4. Add a # infront of them to comment it out
  5. Save & Exit.

As far as I am aware everything is still working fine and it might just be something left in from Karmic which isn’t needed any longer but just to make sure comment out these lines rarther than removing them.

Yet Another OpenCV/Karmic error – symbol lookup error: /usr/local/lib/libhighgui.so.4

symbol lookup error: /usr/local/lib/libhighgui.so.4: undefined symbol: av_free_packet

To fix it simply make sure /usr/local/lib is in your library path by using the following command:

export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH

Howto fix: “error while loading shared libraries”

While installing opencv on an older version of debian for work I kept getting an error while loading shared libraries which turned out to be a pretty easy fix, just finding the libraries and adding them to the dynamic linker.

The libraries I was having trouble with below:
./blobtrack: error while loading shared libraries: libcxcore.so.1: cannot open shared object file: No such file or directory

ffmpeg
ffmpeg: error while loading shared libraries: libavdevice.so.52: cannot open shared object file: No such file or directory

I used the ‘locate’ command to find where the libraries were eg:
locate libcxcore.so.1
This outputted a few locations of where the library was, I decided to use the /usr/local/lib version as both libraries I needed were in there and did the following command to add them to ld.so.conf and reload the dynamic linker:
sh -c 'echo "/usr/local/lib" >> /etc/ld.so.conf && ldconfig'