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

Galnet MIUI Ice Cream Sandwich :]

Nope, you can start the ball rolling. :)

It's merely 2.3.x build around the 4.x.x framework though, isn't it? Calling it ICS is a bit misleading.
 
It's merely 2.3.x build around the 4.x.x framework though, isn't it? Calling it ICS is a bit misleading.

Mine may be a very banal question, but what does the above mean? What exactly is a framework and how does it different from the build? :confused: I read the whole post on xda but didn't manage to understand.
 
Mine may be a very banal question, but what does the above mean? What exactly is a framework and how does it different from the build? :confused: I read the whole post on xda but didn't manage to understand.

It's based on the current Android Version (2.3.*) not ICS which will be 3.*. So it won't have any of the goodies that'll be bundled up with that, rather just themed to look like it.
 
It's based on the current Android Version (2.3.*) not ICS which will be 3.*. So it won't have any of the goodies that'll be bundled up with that, rather just themed to look like it.

So in this context "framework" only means the skin, the graphical interface, not any actual functionality of the underlying kernel/ROM, etc, right?

If that's the case, why is a specific "ICS build" required, and how is that different from, say, creating a MIUI theme which looks like ICS?
 
ICS which will be 3.*

Minor correction: Honeycomb is Android 3.x. Ice Cream Sandwich is v4.x.

So in this context "framework" only means the skin, the graphical interface, not any actual functionality of the underlying kernel/ROM, etc, right?

That's about it, yes. Until the source code for v4.0 is released we won't see a proper ground-up build.

If that's the case, why is a specific "ICS build" required, and how is that different from, say, creating a MIUI theme which looks like ICS?

MIUI is based around the AOSP code base, similar to the CyanogenMod builds. It's completely different (and incompatible) with the Samsung-based builds used by other ROMs.
 
[...]MIUI is based around the AOSP code base, similar to the CyanogenMod builds. It's completely different (and incompatible) with the Samsung-based builds used by other ROMs.

Fine, but I still don't understand why a specific build is required. If the change is only 'cosmetic', why didn't the author just create a MIUI theme which looks like ICS but can be installed on any MIUI rom? If instead the change is not only about the graphics, then what, specifically, has changed and is different from a traditional MIUI rom? The kernel, some core functionalities, etc? :confused:
 
It's merely 2.3.x build around the 4.x.x framework though, isn't it? Calling it ICS is a bit misleading.

Ahh :( I see, got me excited for nothing >.<
Guess we'll still have to wait for a reallyy longggg time then..

Thanks for enlightening the 'misconception' though! ^^
 
I assume specific framework-res.apk and SystemUI.apk files are required.

What you have been saying is technically incorrect Slug. The framework deals with pretty much everything that happens under the hood in the rom, the speed of the device and power management are two such elements of the framework.

Calling it ICS isn't misleading at all. What we have effectively done could technically be called Gingerbread Ice Cream Sandwich in a sense. Yes, there is an element of 2.3 in there, but what drives it is Ice Cream Sandwich.

Since there is no UI elements of ICS included in our ICS build, looking in the framework-res.apk and systemUI.apk will yeild absolutely no results. From a theme standpoint, everything is held in the theme .mtz files (outside of the default defacto imagery). Further to this, we even said in our initial release that this was framework only, and that there was no ICS UI elements included in the rom itself, as this is MIUI's job to develop the UI, not ours.

The way to see what he have done is to decompile the framework and then compare the sizes of the classes.dex files. As you will see, the ICS build's classes.dex file is significantly larger than the stock MIUI version. That is where the ICS framework is merged into the build.

And as for how we managed this with no source code? simple answer. We work with closed source code all the time, so we have become very good at working without the sources. That was demonstrated with getting the ICS SDK to even boot on the Galaxy S 1.

I hope this has cleared up any misconceptions.
 
What you have been saying is technically incorrect Slug

I think the term you're looking for is "wrong", LttlDvl. That's why you're a dev and I'm only a tinkering end-user. Please understand that I intended no disrespect. :o

I hope this has cleared up any misconceptions.

More than that, it's added greatly to the (little) understanding I have of what you magicians actually do to bring these wonders to our devices.

Thanks for taking time to explain, and for correcting my guesswork in such a kind manner.
 
The devs do indeed do amazing work, and great to get clarity from them directly. But many of us don't understand the techy stuff, and rely on guys like slug to put things into plain english. Thanks to you both for keeping us informed.
 
I think the term you're looking for is "wrong", LttlDvl. That's why you're a dev and I'm only a tinkering end-user. Please understand that I intended no disrespect. :o



More than that, it's added greatly to the (little) understanding I have of what you magicians actually do to bring these wonders to our devices.

Thanks for taking time to explain, and for correcting my guesswork in such a kind manner.

You can only be wrong if you knew what i was explaining. Not everyone can be expected to know all of the technical details, Im still learning even at the moment.

I am currently at Galnet's house just now, so hopefully we can come up with something even better than what is available now.
 
Back
Top Bottom