[Connected Car] donaldta:
Yep, "mount -o rw,remount -t ubifs /tmp/udev/dev/sda1 /tmp/udev/dev/.mnt/sda1" is all you need inside the file if you're going to hard code the arguments for mount. A shell script is nothing much more than a list of commands that you can type from the command prompt. Okay, maybe I'm oversimplifying, but in your case that is all you need. The reason why I add .sh to the filename, indentation, and even the "#!/system/bin/sh" is to follow some common practices for writing scripts to support them and make it easier to read.

Anyways, you'll have to "chmod 744 {scriptname}" otherwise you'll need to specify the command interpreter, e.g. "/system/bin/sh {scriptname}" or "sh {scriptname}" in order to execute it. For that, I think you need to have the script in a directory other than /mnt/sdcard or its sub-directories. I am not sure if it is possible to set the eXecute flag in the sdcard space, so /system/xbin would probably be a good place for it.

You're welcome. In retrospect after recently going through a firmware update on my PAS, installing apps directly into /system/app is generally bad practice. All your additions under the /system directory will be wiped with a firmware update which is not fun having to go through restoring them. But, I guess it's just one of those things we have to put up with since we are using the device beyond the manufacturer's intentions.

Yes, that's actually iGo's preferred method of licensing (anti-piracy). Every SD Card has a 128-bit Card IDentifier (CID) and it contains; Manufacturer ID, OEM/Application ID, Product Name, Product Revision, Product Serial Number, Manufacturing Date, CRC7 Checksum, and some reserve data. It resides in a space which should not able to be re-written at least by the average user. So, iGo (and many others) depend on this as proof of licensing by associating it to a physical item so they don't lose revenue because of piracy.

Personally, I don't use iGo and have deleted it from my /system/app to directory to make way for TomTom. In my opinion, it is a much better app and the maps are updated quarterly and doesn't depend on a unique CID. That empowers me with the ability to use any size SD Card. However, there are many different turn-by-turn software available to Android and you can probably find one better suited for you to release you from the chains of requiring a small SD Card.

It is possible but I do not know if Spotify supports symlinks. You'll have to remount USB drive as read-write then copy the Spotify cache directory into it. Then you would delete the original directory and replace it with a softlink with "ln -s (real.file.or.directory) (softlink)"., eg "ln -s /tmp/udev/dev/.mnt/sda1/spotify-cache-dir /mnt/sdcard/spotify-cache-dir". I actually don't know the name or location of Spotiy's music cache directory but the example should give you an idea of how to use the "ln" command. Otherwise there's always Google search.

The default location should be in a sub-drectory of "/data/data/{package.name}". Though it is probably stored in a SQLite Database. There are apps in Google Play which will allow you to manipulate them though, my favorite is SQLite Debugger. You could always make a copy of the files and directories in its original state so that you can avoid having to perform a factory reset. You will have to force close the app before restoring the original copies though, otherwise you might corrupt them.

Well, [MENTION=2123836]jaanusj[/MENTION] did post a brief how-to but I think it might be beyond the technical abilities of most Volvo users. That's because Volvo designed their launcher to be used in a very limited fashion and all the apps in the launcher are hard coded in the APK. So, if you want to customize it then you'll need to decompile it, make the appropriate changes, recompile it, then use a masterkey exploit script to create an APK that can sneak the changes back into the system. It is probably easier just to find another launcher off of Google Play.