XDA-developers has been dancing to this particular beat for a very long time. Many of you who have joined after 2008 will probably have no clue about this, but when the original Manila 3D (precursor to Sense) came about, HTC claimed that it would be impossible for older hardware to run it (even the HTC Tilt, which was their top of the line device before the Diamond and TP hit the market). Devs got functional ports of the UI and roms for virtually every device on XDA. However, the journey to get this going was not an easy one. Most images and animations were compiled in lua and were made exclusively for VGA devices (keep in mind that the grand majority of devices back then were QVGA). Only a handful of developers were able to get some progress going on these ports. Some of them were successful, some others were not. Right now, history seems to be repeating itself with the leak for the HTC Sensation. Most devs in the high end device fora are trying to iron out the kinks to get the 3D UI going for the “old devices” like the EVO, Thunderbolt, Desire HD, and Inspire 4G. XDA member r2DoesInc made a very interesting post in the port thread for the Thunderbolt where he states that the biggest problems with everything being out of resolution is not a matter of screen density, or some values hidden in some xml files. The issue lies within some files with extension .m10, which according to the dev are not files in readable format and that contain some values that are for some unknown function or process (needless to say, I am paraphrasing this).
In an attempt to help others get into the development of this new UI, the dev has put together a very comprehensive tutorial on the tools needed to try and crack this one open. Keep in mind that this is only for experienced devs. The devs working in the project will not be helping others with basic set up questions. If you are able to contribute to the project somehow, please leave your feedback and findings.
So I’m sure all of you realize that the biggest issue with this rom is the screen not fitting. Theres a huge group of developers working on this over on the DesireHD, and they have come a huge way so far.
The issue isn’t the image size, isn’t in some xmls, no, not that simple. The issue are these .m10 files. These are files that tie in with the new libmode10 and fusion graphics engine. basically, it means we have a non-human readable file with a buch of crap in there, and some relevant values that we aren’t quite positive of.
This is going to get complicated, so if your not tech savvy, you should just leave this to someone else, because I’m not going to get into setup details etc. You need to have some idea of what your doing beforehand. All the tools needed for this can be found at the bottom of the post.
You can find more information in the original post.
Want something published in the Portal? Contact any News Writer.