CM7

rrs@researchut.com (Ritesh Raj Sarraf) — Sat, 07 May 2011 11:46:06 -0400

CyanogenMod does list Samsung Galaxy S in its list of devices, but given that it is marked experimental I was not very confident of trying it out. But yesterday, I took the plunge. Even though experimental, the ROM is pretty good. And the Cyanogen goodness just makes it awesome. This ROM (also being AOSP GingerBread) is Super Fast.

So in a day of use, my impressions:

Battery performance has turned out to be better than what I was used to.
Cyanogen’s enhancements are pretty impressive.
The CyanogenGalaxyS team’s work is of very good quality, even though they’ve marked it experimental. (Thanks codeworkx, coolya and the team)

The CyanogenMod experience is also good because it makes me feel like home, just like our Debian project.

Everything is AOSP Build
Non-Free Add-Ons are available from other sources pretty easily
Device support strategy is just like our architecture support strategy. If it qualifies QA standards, it gets listed as Officially Supported. Otherwise Experimental Support
Suffers the same proprietary drivers problem.

For anyone who hasn’t tried it on the Galaxy S, give it a [shot](http://forum.cyanogenmod.com/topic/17020-all-models-cyanogenmod-7-for- samsung-galaxy-s-phones-experimental/). It is good.

Samsung Galaxy S and Samsung Kies

rrs@researchut.com (Ritesh Raj Sarraf) — Thu, 21 Oct 2010 06:57:00 -0400

Well most must be knowing by now that Samsung is rolling out the Android 2.2 FROYO update in phases. And it would be available through Kies.

There have been numerous reports of Kies not detecting the Samsung Galaxy S phone.I think I have a pattern and know what has been causing the trouble.

Samsung Kies , by default, is set to auto-start and reside in the System Tray. The Kies application auto-detects the phone when plugged-in and starts up the applications. I guess this is where the problem lies.

In Windows (at least on my XP), when a PnP device is connected, Windows:

Detects the device
Loads driver and initiazlies the device
Executes appropriate action related to the device (Like open a folder if it is a flash stick)

The phones, when connected, are also detected by Windows as storage devices. So, if we can make Windows have 1st access to the Samsung Galaxy S phone upon connect, it can follow the above steps and detect the device.

This is where the catch is. On typical installations of Kies, it is already running. So as soon as the phone gets plugged in, Kies tries to access the phone first. I have no idea how bloated Kies is. Does it also hinder the driver initialization of the phone ? From the looks of when Kies is running and phone is plugged, yes.

So, simple steps to get your Samsung Galaxy S detected on Kies

Kill Kies
No Kies instance in System Tray
Connect Phone and select “Samsung Kies”
Let Windows detect the phone and initialize the device
Let Windows pop-up an action Window
After all this is done, now start Kies.

Leave a comment on the blog is this works for you.

Samsung Galaxy S on RESEARCHUT

CM7

Samsung Galaxy S and Samsung Kies