Honeycomb seems to be a new beast altogether. There are lots of changes from the original versions of Android, changes that go rather deep down and force us to change the way things are done to roms. For instance, deodexing roms has been common practice since the days of the G1. This method of treating roms and apks, in case you are not familiar, has several advantages one of which is that it makes theming a much simpler ordeal as all files are located in a single place rather than spread out (odexed). With the birth of Honeycomb, this seemed to be a much more complicated order as using smali and baksmali to compile and decompile the dex files present in dalvik was proving difficult. Luckily, XDA member Roach2010 has found a way to use baksmali when coming from using smali 1.2.6 by XDA member JesusFreke. The dev basically tweaked the 1.2.7 baksmali and has been able to deodexed Honeycomb successfully.
This is only meant for chefs and devs. If you are into developing for Android 3.0/3.1, then this is an absolute must have tool. Please take it for a spin and leave some feedback for the devs.
I recently made a discovery regarding the baksmali issues we used to encounter while trying to deodex honeycomb’s framework. Here is a working baksmali tool based on JesusFreke’s 1.2.7 patch that allows us to recompile using smali 1.2.6.
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer._________
Join us for xda:devcon 2014. For a limited time, XDA Portal readers get 20% off registration!