I've always got it changed and then go to the uot kitchen and make it in to an update.zip file that can be done from recovery and then pull my original out for easy flashing just in case
It could very well be that more XML edits or smali code to be more specific are needed to activate the CRT animation. The framework-res.apk recompiled fine so I'm surprised its causing issue for a basic one word XML change from "true" to "false" to enable the CRT animation.
The true is changed to "false" to enable the CRT animation.
Only other thing I can think of is this is probably a "odex" file system which could be causing problems with recompiling without the odex file portion.
Thanks, I figured that was the case that this was an odex file system.
It could very well be something to do with the odex file system causing my XML edit not to take or it could be that there is further smali code editing needed which is causing the framework to crash at boot.
Got a guy I know over at XDA working one up for us so we will se what happens when he cracks into it, supose to give him a shout Monday and will hopefully have it shortly after and will kepp you posted
We still need to de-odex the system before we can do anything. An odex'd system uses md5 hash checks on every file, so having the modified one would cause a boot loop. If he is in the process of de-odexing the system for us, that would be greatly appreciated as that would help out immensely.