Getting Mount Manager working with Android 4.2

This post May Not apply to you but I hope it helps.

I have had some people that have reported issues connecting to a share with Mount Manager on a 4.2 device.

First, make sure you have the required modules for your kernel. This post will be using CyanogenMod 10.1 as the reference, but your ROM may differ and YMMV.

In CM10.1 you have to load 3 modules to get cifs to work correctly. cifs.ko depends upon dns_resolver and md4 modules. They have to be loaded before cifs.ko.

Once you have these modules loaded you should be able to mount your shares. If you are still having issues try looking at this post on XDA. It seems there is an issue with some builds of busybox that it needs the unc option added to the connection.

You can add a new option when creating a mount point and select custom. Then enter “unc” as the name. For the value you will enter the same path that you use for the network share, except you have to use “\” instead of “/”. And you have to escape them. So you need to use 2 of them for every one you enter.

Enable Soft-Keys on Samsung Galaxy Note 2

I wanted to enable the soft-keys on my Samsung Galaxy Note 2 after switching to the new nightly builds of CyanogenMod 10.1.

I found that it is actually rather easy to turn them on. It just requires modifying the build.prop with the following:

qemu.hw.mainkeys=0

If you want to disable them later just change it to:

qemu.hw.mainkeys=1

After you modify the build.prop you have to reboot for the changes to take affect.

This change will turn on the soft-keys, but it does not disable the hardware keys. But you can disable them too. You have to open /system/usr/keylayout/Generic.kl and comment out the following by added a '#' to the beginning of the line.

# key 158	BACK
# key 139	MENU

The home key is located in /system/usr/keylayout/gpo-keys.kl

# key 172	HOME	WAKE

To turn these back on just remove the '#' and reboot.

Connecting to Nook Color w/ CyanogenMod7 via ADB over USB

The Nook Color is a great device, especially when CyanogenMod is installed on the device. The only issue I was having with the device, I was unable to connect to the device via ADB over USB.

I followed the steps here, but was still unable to see the device via ADB. After looking through the “fix” that was linked from XDA, I noticed that it modifies, or creates a file in %USERPROFILE%\.android\ called adb_usb.ini. That file contains vendor id’s for the devices and it contains 0x2080. As I was digging around looking to fix this issue, I noticed that in the root of my Android SDK installation there is a folder called .android. In that folder, just like the one in my user profile, there is a file called adb_usb.ini. This file is empty, except a couple comments describing the file. I added the 0x2080 to this file, then I restarted adb by doing an adb kill-server, then an adb start-server.

Now when I do adb devices, I can see the Nook Color and I can perform any adb or shell commands on the device via adb over USB.

Getting GPS working again on the Vibrant w/ CM7 nightlies

I love CyanogenMod and I thank all of them for their hard work that they do for basically nothing except the “thrill”. I have been using that since the very first version on my HTC ADP1. Then I bought the Samsung Galaxy S Vibrant from T-Mobile and CM was not available for the device. I stuck with the “Stock” Samsung TouchWiz UI that I made some tweaks to here and there to get a better experience for myself. I did things like rooting the device, adding the CarDock, removing the crap software that I don’t ever use, removed the “WorldClock” and added the stock Alarm Clock and other things here and there.

The GPS on this device has always been a topic of discussion, as there were issues with it from launch. It would take up to 10 minutes or more, to get a lock, and once you got the lock, you would probably lose it. There were people much smarter then me that found ways to make the GPS usable on the Stock TouchWiz UI.

After some time, Team Whiskey released the Bionix ROM. This was/is a ROM still based off the TouchWiz version of Android at its core, but was a better experience as it included functionality that was not in stock TouchWiz, and it didn’t include the bloatware. The biggest thing that Team Whiskey brought to the Vibrant with Bionix was Voodoo. Now, I know they did not create Voodoo, and other ROMs had support too, but I am just babbling about what Bionix did for me. I ran this ROM for some time, and a mod that I created that brought the Gingerbread keyboard with working the hepatic feedback to FroYo ROM is even included in the distribution. But there was still something missing for me.

I believe, at least for me, that the Vanilla Android is a better user experience, and the CM modifications, is that experience, plus more for your “die-hard” android users. I would go to the CyanogenMod website often to see if there was any developments on getting a build of CM running on the Vibrant. Now, you may read this and say “It ran on the Vibrant for a while”, and that is true, but the steps needed to install it on the device was a pain in the ass, not to mention that there were a lot of things that were not working. These are the things that kept me on Bionix. Then the CM team that work on the Vibrant (and other Galaxy S devices too) got the install process to be a lot less of a pain. At that time, I decided to give it a try, and I knew that GPS, among some other bugs existed.

Then shortly after I started flashing these unofficial builds of CM, the nightlies started. At the time of this post, they have over 75 nightlies, but there are still some issues with it, including GPS. Which brings me to the actual title of this post. I found this thread over on XDA by stricklyrude27. He put together a set of scripts and files and steps that were created by other people (see thread for their credit) and placed them in to a single update.zip package.

I am running CM7.1-N76 with the GPSFix v1.4 and GPS works great. I get a lock in just a couple of seconds. If you are running CM7 on your Vibrant, head over to the thread and give it a try, at least until an official CM7 solution comes about.

Thank you to all that contribute to the CyanogenMod and especially to the SGS Team, also thanks to all that were involved in getting this fix working too. The android community is great and love that just about always, a solution to any issue is found.

CyanogenMod 7 on Galaxy S Vibrant

The nightly builds for CyanogenMod 7 for Samsung Galaxy S line of devices is now available via Rom Manager. It is now a “Single Update” install, 2 if you want to add gapps.

Here are some of the issues I had when doing the install, and how I worked around them.

• Follow the instructions Here and Read the FAQ here. This is just a “helper” for some of the issues I had, not a replacement or step by step.
• You will need to be able to get in to the Recovery via the 3 Button Method. If you cannot, then you will have problems.
• Before you start with ROM Manager, you need to download the gapps package and place it on the internal sdcard. You cannot use ROM Manager to install the gapps, it will not work.
• The easy part is installing CM7 from ROM Manager. Open up Rom Manager and download the CM ROM
• ROM Manager will now download the ROM. Once completed, it will prompt you to wipe data and cache and backup. You should do them ALL. Then Click OK.
• The device will reboot and it will install the CM package. Be patient, it can take a while.
• Once the device is rebooted you will want to turn the device off. DO NOT USE ROM Manager, or any other shiny thing, to get in to the recovery, it will not work correctly.
• Power the device back on using the 3 Button Recovery method. Hold down Vol+ & Vol- & Power. Once you see the “Vibrant” Screen release ONLY THE POWER button.
• Now that you are in Clockwork, select install package from sdcard and select the gapps package you downloaded before you started.
• Reboot your device and enjoy.
• Update: If your PC does not recognize your device any more, you need to install the Google USB Drivers.

I forgot how much I missed using AOSP + the things that the CM team adds to the party. Being stuck using TouchWiz for so long, it is like getting a new phone again. Even if you run ROMs like Trigger or Bionix, you are still stuck with the TouchWiz additions.

Thanks TeamHackSung, my Galaxy S is happy now.