Ice Cream Sandwich on HD2

Thanks to TyTung, I now have Ice Cream Sandwich / Android 4.0 running on my phone!

You can view his work here:

• Google Sites: NexusHD2-IceCreamSandwich
• XDA Thread
• Google Code Project Site

Market Issue

The market wouldn’t install anything at first.  After the first reboot, the market started working for some reason. I found this fix, but I didn’t end out having to use it:

You can change screen density in build prop to 160 before installation and all apps should be compatible in matket. I tried to chsnge it when it was already installed with root explorer but mo luck. So unzipped file with root explorer than changed build prop. Rezipped file and installed and all the apps are compatible. The rom was a little slow but after I rebooted it got faster. I’m impressed at how good ICS looks especially compared to GB and Froyo.

One thing I noticed was that it adds a shortcut to the home screen when you install an app.  You have to pay attention to which home screen you are on when you open the Market because that is where it will drop the shortcut.

When all else fails, you should always check the settings.  You can turn this feature off in the settings for the market.

YouTube Issue

Videos don’t seem to play right.  The sound is fine, but the video part doesn’t work.

In landscape, it looks even worse:

Here are some of the messages that I get in the log:

11-27 22:50:12.310: W/SoftwareRenderer(69): Surface::dequeueBuffer returned error -22
11-27 22:50:12.353: W/GraphicBufferAllocator(66): alloc(352, 288, 842094169, 00002930, ...) failed -22 (Invalid argument)
11-27 22:50:12.353: E/SurfaceFlinger(66): GraphicBufferAlloc::createGraphicBuffer(w=352, h=288) failed (Invalid argument), handle=0x0
11-27 22:50:12.353: E/SurfaceTexture(66): [SurfaceView] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed
11-27 22:50:12.353: W/SoftwareRenderer(69): Surface::dequeueBuffer returned error -22
11-27 22:50:12.380: W/GraphicBufferAllocator(66): alloc(352, 288, 842094169, 00002930, ...) failed -22 (Invalid argument)
11-27 22:50:12.380: E/SurfaceFlinger(66): GraphicBufferAlloc::createGraphicBuffer(w=352, h=288) failed (Invalid argument), handle=0x0
11-27 22:50:12.380: E/SurfaceTexture(66): [SurfaceView] dequeueBuffer: SurfaceComposer::createGraphicBuffer failed
11-27 22:50:12.380: W/SoftwareRenderer(69): Surface::dequeueBuffer returned error -22

Camera Issue

You won’t find any camera app in the ROM.  According to the XDA thread, the camera won’t connect.  So, that is something I will have to live without for a bit while on the bleeding edge.

Unlock Issue

One thing I am not sure that I like is that you can’t see which way to unlock the phone until you begin to drag the ring.  It is just a small nuance.

Here’s what it looks like when you begin to drag the ring:

Settings Screen Issue

I had been able to use the Settings screen before writing this post.  But, when I went to take the screenshot, it broke.

The log reads something like this:

<pre>11-28 00:05:22.809: I/WindowManager(177): createSurface Window{41611908 Starting com.android.settings paused=false}: DRAW NOW PENDING
11-28 00:05:22.819: I/ActivityManager(177): Start proc com.android.settings for activity com.android.settings/.Settings: pid=2003 uid=1000 gids={1015, 3002, 3001, 3003, 3007}
11-28 00:05:22.979: W/NetworkManagementSocketTagger(177): setKernelCountSet(1000, 1) failed with errno -2
11-28 00:05:23.170: D/pppd(1931): rcvd [IPCP ConfReq id=0xf4]
11-28 00:05:23.170: D/pppd(1931): sent [IPCP ConfAck id=0xf4]
11-28 00:05:23.659: D/AndroidRuntime(2003): Shutting down VM
11-28 00:05:23.700: W/dalvikvm(2003): threadid=1: thread exiting with uncaught exception (group=0x409f41f8)
11-28 00:05:23.710: E/AndroidRuntime(2003): FATAL EXCEPTION: main
11-28 00:05:23.710: E/AndroidRuntime(2003): java.lang.NoSuchMethodError: ex
11-28 00:05:23.710: E/AndroidRuntime(2003): 035
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at com.android.settings.Settings.updateHeaderList(Settings.java:320)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at com.android.settings.Settings.onBuildHeaders(Settings.java:312)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.preference.PreferenceActivity.onCreate(PreferenceActivity.java:542)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at com.android.settings.Settings.onCreate(Settings.java:91)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.Activity.performCreate(Activity.java:4465)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1919)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1980)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.ActivityThread.access$600(ActivityThread.java:122)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1146)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.os.Handler.dispatchMessage(Handler.java:99)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.os.Looper.loop(Looper.java:137)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at android.app.ActivityThread.main(ActivityThread.java:4340)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at java.lang.reflect.Method.invokeNative(Native Method)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at java.lang.reflect.Method.invoke(Method.java:511)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
11-28 00:05:23.710: E/AndroidRuntime(2003): 	at dalvik.system.NativeStart.main(Native Method)
11-28 00:05:23.739: W/ActivityManager(177):   Force finishing activity com.android.settings/.Settings</pre>