Maybe Mr.Artine could give some advice on this matter.
Considering Artine did all his magic on GB I don't know if the advice will work as well on ICS especially a custom one like CM9.
Yes but Artine is brilliant with this stuff he'd be a great person to have help with this ROM
Hall of Fame lvl. 4,6,7,8,10
There are many simple tweaks that can vastly improve a ROM's battery life - things like using JuiceDefender and DroidWall help greatly, and things as simple as just completely debloating a ROM entirely can give a large boost to performance as well as battery life. What surprises me is that this still applies to NAND/flash memory devices, such as Android phones. As for everything else, I'm just pretty good at combining things and figuring out how things work - there's a disclaimer for both Hydra and Sleipnir to boot. I've done plenty on my own, but Sleipnir - and as a direct result, Hydra - is a product of the community. It's a result of everyone's effort, not just my own.
That being said, I am excited for CM9, and I would love to do a build for it, but as of right now it is true that I won't be able to offer much advice with regard to ICS, because I've never even poked it with a really long stick. I'm starting to do some research on my own about it now, though, in anticipation for when all of the kinks of CM9 get worked out. I'm even more excited about CM10.1, though. Phenom and the others are incredible, and I can hardly wait for future improvements to come out - no matter what CM version they're for.
I don't know if anyone else has noticed this, but after flashing this new build and removing my battery cover to reinsert my sd card, I notice a faintly glowing neon colored light coming out from near the usb charging port. I turned the phone on to look around at some settings to see if there was anything different. I noticed that in an option somewhere in the accessibility settings, there was a menu that says Access Delta9 security mechanism. I enabled it and immediately this florescent secret compartment slid out from the bottom of the phone.... Now, what I found inside... Well, I don't know if I should say.... I'll wait to see if this has happened to anyone else first.
I know I'm a little behind in only reading this now, but it made my night.
Really well than don't help! Just kidding u know when Artine is busy I need a go to guy and u were very helpful in the past now as for the area u said I tried that before I started asking where to put it cause it wasn't working I thought I was in the wrong area so maybe I need to make it RW or something like that so how do I do that I have ES MANAGER AND TOTAL COMMANDER
For Total Commander, hit the far-right button with the green arrows at the bottom of the app. Tap the new button that pops up with a green "+" sign. For "Function Type," choose "Internal Command," then tao the ">>" symbol. Scroll down to "119 Remount (requires root access)," select it and hit "OK / Apply." Now navigate to /system/media, and use your new "RW" button to remount the directory to R/W, then drop in your bootanimation.zip file there (in /system/media). Now hit the "RW" button again to switch the directory back to read-only, and reboot the phone.
Your boot animation should override the default one, and if you have a PowerOn.mp3 file in /system/sounds/poweron, the song will play with the boot animation (it doesn't for legacy bootanimations, which are in framework-res.apk, not in /system/media in the form of a .zip file). Things may be different with CM9 though, or ICS in general, as it is my understanding that the filesystem layout is very different from that of GB. In fact, compared to other GB phones, apparently this phone's filesystem is weird in general. My apologies for not getting back to you on this sooner.
Just wondering if I were to.flash a rom and forget to wipe davlik would I need to reflash that rom to avoid problems? with the update to cm9 I am not sure if I. wiped davlik should.I reflash? will it cause problems if I do reflash our don't reflash?
My rule of thumb is if you're flashing anything to /system, always wipe the dalvik-cache to avoid problems. If everything's going smooth now though, there's no need to reflash, but I would wipe it in the future.
Has anyone thought to ask phenom what all he changed in the kernel for the newer versions? Giantpune mentioned early on that he had the option to add clock capabilities up to 1.9ghz on stock. However he felt that 1.6 was high enough for stability purposes. I'm just thinking that just opening up a few options to allow for higher over clocking, wouldn't effect everything overall and make the entire ROM less stable, especially if the higher speeds aren't being used.
I agree. If those higher speeds are unstable, but aren't being used, there shouldn't be any problem caused by simply having them available. If there's any worry about it, one could - at least on GB - edit init.qcom.post_boot.sh in /system/etc to change the minimum and maximum frequencies they can use (doesn't affect the kernel, only limits what you can set yourself post-boot), including the default governor for the CPU. I figured that out on my own when I tore apart the stock ROM as much as I could, and that's how/why Sleipnir's default governor is smartassV2, and the 122MHz minimum frequency is disabled from being selected entirely.
pretty please?