[Nexus S Android Development] djjonastybe:
This is a ROM currently being tested for deep idle. I made it to make sure issues can only be caused by custom kernels. More features will come very soon. Just let me know how this ROM runs the Deep Idle mod from Ezekeel.

This ROM doesn't have any fancy things yet. But I tend to add more and more things as I see they are stable.

This ROM will guarantee Deep Idle to work on my settings! Feel free to overclock further if necessary

Features:

-Deodexed

-Rooted

-Zipaligned

-Tweaked

-Cleaned unnecessary applications which are downloadable in Android Market

-init.d support

-Busybox 1.19

-Stable deep idle support

Coming soon

- Ultra fast GPS (preset for European users, can be changed to other countries easily!)

News

- 72 hours and no crashes, freezes or reboots yet with deep idle enabled (posted at 9:00 am 8 December 2011)

Devices

-I9020T

-I9023

-I9020A

Installation

1. Boot into CWM

2. Install official stock GRK39F for best results with deep idle

3. Do not leave CWM

4. Install my ROM immediately over it

5. Install latest GLaDOS kernel, or any other deep idle kernel you like.

6. Wipe data/cache/dalvik

7. Boot your Nexus S

8. Download NSTools from Market

9. Deep idle should now run very stable

Enabling Deep Idle

Flash the kernel of your choice if you want deep idle. This ROM is guaranteed to have deep idle work on your device. If deep idle doesn't work then it is most likely a kernel issue or your device can't handle deep idle. If your phone was having problems with deep idle before on every ROM you tried. Try this one.

Always make sure that when you try deep idle first:

If your Nexus S is more idle than being used:

Freq range: 100-1000

Governor: lazy

Deep Idle: On

Maxfreq: On (Make sure this setting is turned on when using lazy, else your device will run unstable)

Unstable ROMs list for me

- NSCollab: Crashes, freezes and reboots on lockscreen with deep idle enabled when turning on the screen.

- MIUI.us: Giving me random reboots with deep idle and maxfreq enabled

Possible reasons why deep idle is unstable without screenoff_maxfrequency

When using lazy governor. The device stays idle at 100mhz (with its corresponding voltages) and will boost to 1000 mhz or something else when the device becomes active. When deep idle is enabled and the device is in deep idle mode. The device may seem to 'forget' or be 'slower' updating the voltages. When going 1000mhz at the voltage of 100mhz, this will result in a freeze and a reboot. When forcing max frequency with the screen off, this is also avoided. So the device might never freeze and reboot.

When using conservative governor. There may be reboots. But the conservative governor goes up in small steps: 100-200-400-...

So the conservative governor is possibly stable. I even believe 100 mhz and 200 mhz are using the same voltages.

Now this is just a theory I am having. Feel free to have your own.

Coffee fund/beer fund

Feel free to donate if you like my work. But remember I didn't do anything special YET here. More features will come soon! IF you are a developer and you wish to help me on some features, you are welcome. We are a community and should help each other.