• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][4.0.4][BETA] CM9 for Virgin Mobile and Sprint 10/3/2013

I love the progress that this ROM has made! I would love to use it but was wondering if there was any overclocking compatibility with the ROM and it's kernel? If not, would it be possible to flash giantpune's kernel?
 
You can clock this kernal At 1800 but giantpoons Kernal goes to I think 1600 and no you can't mix and match these cuzz giantpoons Kernal is for GB and cm9 is for ICS...
 
Phenom (or whoever else) here are the relevant sections of the logcats when opening both mx camera and pudding camera.

https://gist.github.com/LowEndGeek

if you need the full logs they are here

MX Camera

Pudding Camera

the two lines

[HIGH]07-17 12:42:46.117 E/MsmCameraDevice(137): __ioctl:: failed. cmd = 21, error = Bad address
07-17 12:42:46.117 E/MsmCameraDevice(137): Failed to get I2C sensor data.[/HIGH]

are common on both
 
ronii said:
You can clock this kernal At 1800 but giantpoons Kernal goes to I think 1600 and no you can't mix and match these cuzz giantpoons Kernal is for GB and cm9 is for ICS...
Click to expand...

Alright, thanks! It's great that you're able to overclock that high. I'll try flashing this when I get the chance.

P.S Have you yourself tried the max overclock on the CM9 ROM?
 
Ganoly3 said:
Alright, thanks! It's great that you're able to overclock that high. I'll try flashing this when I get the chance.

P.S Have you yourself tried the max overclock on the CM9 ROM?
Click to expand...

I have. It's stable for me but YMMV. Not all CPU chips are the same and only been tested on stock speeds for stock ROM.
 
Bluntmagic95 said:
So if i understand this correctly. I have to have stock kernel and i can not restore apps from backup?
Click to expand...

The rom has its own kernel. And restoring any apps with data that are from a previous GB rom may cause issues. GB is API 10 & ICS is API 14...and if they're market apps with no backward compatibility you'll have issues.
 
phenomx4 said:
Only the "cannot connect to camera" error can be fixed with changing ro.product.device=VM696/LS696 to m3s but the camera crashes.
Click to expand...

Okay. What if changing ro.product.device=VM696/LS696 to ro.product.device=m3s and also change ro.build.version.release=4.0.4 to 2.3.7
That should fix the force close for the camera.
 
starkraving said:
Maybe on another device but I've gotten erroneous behavior on the elite...restoring from GB to ICS using TB. ICS to JB no issues.(N4)
Click to expand...
Worked on my elite on my v my n4 and my transformer. I brought stuff from my v to my newer devices without a problem.
 
You must log in or register to reply here.
Back
Top Bottom