Jump to content

4 Apr Ir13 (IMM76D / 4.0.4 / CDMA + GSM): MoDaCo Custom ROM for the Galaxy Nexus


Recommended Posts

Posted

Just fixed the FaceLock issue in the kitchen.

I noticed I haven't implemented my rotate speed tweak in this build, i'll add that this morning (with some other bits)!

P

Posted

I'm happy about your new release! Thanks a lot

but mhhh I was running the 4.0.3 AOSP Builds now and it's a bit hard to understand why your new Build isn't based on this.

Waiting for a new release, I don't want to go a step back :)

4.0.3 allready in pipeline?

Simply...

- MCR ROMs are based on ship or test ROMs

- These are tested much more than AOSP

- MCR ROMs can be flashed over stock without wipe

I actually have built a full AOSP ROM which I am also working with, but i'll just pull the best bits I think until we get the 4.0.3 OTA.

:)

P

Posted

Where do you get the Gapps from, Paul? there are so many ZIPs about online but surely Google must have a place to get them from?

Posted

Where do you get the Gapps from, Paul? there are so many ZIPs about online but surely Google must have a place to get them from?

Google doesn't licence them outside of ROMs so no, Google don't have a place to get them from.

I just pull the latest versions from the most recent stock ROM.

P

Guest duRin90
Posted (edited)

So I stuck on bootanimation for over 10 minutes now. Animations is lagging and I'm quite confused if I should wait more or just take battery out. Any suggestions?

Edited by duRin90
Posted

So I stuck on bootanimation for over 10 minutes now. Animations is lagging and I'm quite confused if I should wait more or just take battery out. Any suggestions?

did u user OC Kernel?

Maybe your Phone isnt able to run 1.4 GHz had nearly the same issues when I used 1.4 GHz Kernel

Guest wireagent
Posted

Apart from the FacebookSync issue and the facelock thing, everything is working REALLY great so far. I am on the undervolted kernel and I have AWESOME battery stats. Thanks Paul!

Guest AndyCr15
Posted

But also KK6 halved my battery life, as it has done quite a few other people. I still use KK1 myself, but I think it will be different for each person.

Guest Chris Jenx
Posted

@Paul

Not sure if this is a bug..

Can anyone else set voltages with SetCPU.. Seems to do nothing. (I say nothing, but I can set the voltage to lower values and it wont lock the phone up, when setting 1.2ghz it should lock the phone up at 600mV).

coolbro3000 kernel allows setting of the voltages, seems odd if you've pulled his kernel that the UV can't be changed.

Cheers,

Chris

Guest Stretlow
Posted

Officially recommended radio is XX6.

P

Is that the same as XXKK6?

Guest Garner2012
Posted

Does that come standard or do i need to choose it from the kitchen?

Guest duRin90
Posted

did u user OC Kernel?

Maybe your Phone isnt able to run 1.4 GHz had nearly the same issues when I used 1.4 GHz Kernel

Well it may be this. However, I've tried old franco's kernel in the past and I was able to run 1.4...

I'll do more research with normal kernel later during the day. Hopefully it's not this as I would like to uv and oc CPU a bit.

Weird thing this OMAP 4460 is. Technically should be able to run 1.5 but Samsung somehow blocked it...or dunno what is happening.

Guest sputnik99
Posted

Google doesn't licence them outside of ROMs so no, Google don't have a place to get them from.

I just pull the latest versions from the most recent stock ROM.

P

If I were you, I would delete this post. I remember Cyanogen getting a C&D from Googles lawyers for using their apps. Sad but that's the way it goes these days.

I saw this Nexus S link on xda direct link from xda-post , this is the thread: thread

Other than that: Thanks for your good work. Flashing pre-Ir8 now.

Guest Nikolas Skoufis
Posted

Is anybody else experiencing issues with superuser after updating to Ir8? It seems not even superuser is able to get superuser permissions.

I've tried rooting with superboot again, but this causes superuser to force quit. I then reflashed Ir8, but that brought me back to where I started.

Any ideas? I've seen something about changing permissions on /system/xbin/su, but what should I be changing them to? 755?

Posted

I am having some problem with the camera: after taking 4-5 pictures in rapid succession the application freeze and FC.

Here is the logcat:

12-22 14:18:21.406: E/AndroidRuntime(9629): FATAL EXCEPTION: main

12-22 14:18:21.406: E/AndroidRuntime(9629): java.lang.RuntimeException: Media server died.

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:31)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.hardware.Camera$EventHandler.handleMessage(Camera.java:736)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.os.Handler.dispatchMessage(Handler.java:99)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.os.Looper.loop(Looper.java:137)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.app.ActivityThread.main(ActivityThread.java:4340)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at java.lang.reflect.Method.invokeNative(Native Method)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at java.lang.reflect.Method.invoke(Method.java:511)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at dalvik.system.NativeStart.main(Native Method)

12-22 14:18:21.413: W/ActivityManager(216):   Force finishing activity com.google.android.camera/com.android.camera.Camera

Another thing: contrary to what was on 4.0.1, now seems to always make an autofocus before taking the picture.

Someone else can confirm this problem?

Guest Nikolas Skoufis
Posted

I am having some problem with the camera: after taking 4-5 pictures in rapid succession the application freeze and FC.

Here is the logcat:

12-22 14:18:21.406: E/AndroidRuntime(9629): FATAL EXCEPTION: main

12-22 14:18:21.406: E/AndroidRuntime(9629): java.lang.RuntimeException: Media server died.

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at com.android.camera.CameraErrorCallback.onError(CameraErrorCallback.java:31)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.hardware.Camera$EventHandler.handleMessage(Camera.java:736)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.os.Handler.dispatchMessage(Handler.java:99)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.os.Looper.loop(Looper.java:137)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at android.app.ActivityThread.main(ActivityThread.java:4340)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at java.lang.reflect.Method.invokeNative(Native Method)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at java.lang.reflect.Method.invoke(Method.java:511)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)

12-22 14:18:21.406: E/AndroidRuntime(9629): 	at dalvik.system.NativeStart.main(Native Method)

12-22 14:18:21.413: W/ActivityManager(216):   Force finishing activity com.google.android.camera/com.android.camera.Camera

Another thing: contrary to what was on 4.0.1, now seems to always make an autofocus before taking the picture.

Someone else can confirm this problem?

I'm having a different but perhaps related issue. Occasionally the camera will begin to misbehave, before force closing. Then, when I try and open the camera app again, I get the message "could not connect to the camera", which can only be fixed by rebooting.

Guest geovass
Posted

I never had any issues with the camera.

I suggest you wipe and try again with the ROM.

Posted

Changelog

22 Dec 13:50 (pre-Ir8)

  • Re-added rotation speed enhancement

Posted (edited)

Silly question, but changing the Launcher to one without the search bar gets rid of the speed enhancement doesn't it? It's your Launcher2.apk that's changed correct?

If so, and that's all you've changed, then I don't need to bake another ROM

Edited by EddyOS
Posted

No, it's a change in the system, not the launcher (it's system wide).

P

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.