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

Root [ROM][PORT][FINAL] MIUI 1.11.25-Triumph | 113011-2 (GB 2.3.7 based)

good question... why is the settings - running apps showing i only have around 300-310 mb of ram total? last build it was showing around 330-340 total

edit: now i'm seeing around 360mb free.... weird. and this is all on a fresh install first boot up after wiping and formating everything. very odd never seen that before.

Ok, guys.

Check dmesg. Stop trying to rely on inaccurate userspace tools. I've found that the memory measurement in MIUI does it's own thing. It's a nice way to estimate use, but not the definitive answer. Obviously, the memory stats fluctuate. This will all change depending on your personal usage. Don't worry about it. Let's all just bask in MIUI's sweet warmth and goodness.

MIUI_dmesg:

Code:
<6>[    0.000000] Initializing cgroup subsys cpu 
<5>[    0.000000] Linux version 2.6.32.9-perf (ikarosdev@chaos76) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Thu Nov 3 16:31:28 CDT 2011 
<4>[    0.000000] CPU: ARMv7 Processor [511f00f2] revision 2 (ARMv7), cr=10c53c7f 
<4>[    0.000000] CPU: VIPT nonaliasing data cache, VIVT ASID tagged instruction cache 
<4>[    0.000000] Machine: TRIUMPH 
<4>[    0.000000] Memory policy: ECC disabled, Data cache writeback 
<5>[    0.000000] Ignoring RAM at 80000000-8003ffff (vmalloc region overlap). 
<7>[    0.000000] On node 0 totalpages: 113664 
<7>[    0.000000]   Normal zone: 1532 pages used for memmap 
<7>[    0.000000]   Normal zone: 0 pages reserved 
<7>[    0.000000]   Normal zone: 112132 pages, LIFO batch:31 
<6>[    0.000000] allocating 5242880 bytes at c1024000 (1224000 physical) for fb 
<6>[    0.000000] allocating 2097152 bytes at c1524000 (1724000 physical) for audio pmem arena 
<6>[    0.000000] allocating 2097152 bytes at c1724000 (1924000 physical) for KGSL 
<6>[    0.000000] allocating 6291456 bytes at c1a00000 (1c00000 physical) for kernel ebi1 pmem arena 
<6>[    0.000000] allocating 24117248 bytes at c2000000 (2200000 physical) for sf pmem arena 
<6>[    0.000000] allocating 33554432 bytes at c7e00000 (8000000 physical) for adsp pmem arena 
<4>[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 112132 
<5>[    0.000000] Kernel command line: console=ttyMSM1 androidboot.hardware=triumph androidboot.emmc=true 
<6>[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) 
<6>[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) 
<6>[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) 
[B]<6>[    0.000000] Memory: 60MB 128MB 256MB = 444MB total [/B]
<5>[    0.000000] Memory: 368768KB available (7056K code, 2012K data, 188K init, 0K highmem) 
<6>[    0.000000] Hierarchical RCU implementation.
StockROM_dmesg:

Code:
<6>[    0.000000] Initializing cgroup subsys cpu 
<5>[    0.000000] Linux version 2.6.32.9-perf (amast@builder) (gcc version 4.4.0 (GCC) ) #1 PREEMPT Tue Jun 7 16:33:44 EDT 2011 
<4>[    0.000000] CPU: ARMv7 Processor [511f00f2] revision 2 (ARMv7), cr=10c53c7f 
<4>[    0.000000] CPU: VIPT nonaliasing data cache, VIVT ASID tagged instruction cache 
<4>[    0.000000] Machine: QCT MSM8X55 FFA 
<4>[    0.000000] Memory policy: ECC disabled, Data cache writeback 
<5>[    0.000000] Ignoring RAM at 80000000-8003ffff (vmalloc region overlap). 
<7>[    0.000000] On node 0 totalpages: 113664 
<7>[    0.000000]   Normal zone: 1532 pages used for memmap 
<7>[    0.000000]   Normal zone: 0 pages reserved 
<7>[    0.000000]   Normal zone: 112132 pages, LIFO batch:31 
<6>[    0.000000] allocating 10485760 bytes at 8102d000 (122d000 physical) for fb 
<6>[    0.000000] allocating 2097152 bytes at 81a2d000 (1c2d000 physical) for audio pmem arena 
<6>[    0.000000] allocating 2097152 bytes at 81c2d000 (1e2d000 physical) for KGSL 
<6>[    0.000000] allocating 6291456 bytes at 81f00000 (2100000 physical) for kernel ebi1 pmem arena 
<6>[    0.000000] allocating 31457280 bytes at 87e00000 (8000000 physical) for sf pmem arena 
<6>[    0.000000] allocating 33554432 bytes at 89c00000 (9e00000 physical) for adsp pmem arena 
<4>[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 112132 
<5>[    0.000000] Kernel command line: console=ttyMSM1 androidboot.hardware=qcom androidboot.emmc=true 
<6>[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) 
<6>[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) 
<6>[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) 
[B]<6>[    0.000000] Memory: 60MB 128MB 256MB = 444MB total [/B]
<5>[    0.000000] Memory: 356864KB available (6784K code, 2004K data, 184K init, 0K highmem) 
<6>[    0.000000] Hierarchical RCU implementation.
EDIT: I should also note that using the built-in task killer (long press "Home" button), does some wacky crap to the memory assessment too. It'll say it kills tasks and frees memory, but if you look in Settings, you actually "lose" RAM.
 
Same here. Except I started getting annoyed on the second boot up. First time I was like "Oh, Interesting.". Second time I was like....Uh Mmmkay...Third time I was like....Oh Mah Gawd ISAAAAAACCCCCC!!!!!!!

>_> Thanks for removing it by the way. (LOL)

All I know is I got caught in a bootloop while working on the last build and it just kept playing over and over. I wanted to punch a baby in the face and kick a kitten.

It wouldn't finish playing the sound either, it would start, freeze halfway through, and start over. I imagine that's what MIUI hell is like.
 
All I know is I got caught in a bootloop while working on the last build and it just kept playing over and over. I wanted to punch a baby in the face and kick a kitten.

It wouldn't finish playing the sound either, it would start, freeze halfway through, and start over. I imagine that's what MIUI hell is like.


Lol I've heard that sound two maybe three times total. it's meh, but never got bothersome.
 
I started using the 11/03/11 build, thanks Isaac for working on this. I use beautiful weather on the home page along with Smooth Calander. When I turn the phone and if I click unlock the screen within about the first 4 minutes after boot, it will either reboot or tell me that Gapps is not responding if I want to force close or it will freeze on the unlock screen with the slider all the way in the down position. I can click wait and let the phone finish loading all the apps and it's fine.

Seems it has an issue with the background apps I am using?
 
experiencing much better battery life on this build. went to bed at 3am and woke up at 10am with still 100% battery on my phone, unplugged the whole night. wifi off and 3g on while i slept.
 
experiencing much better battery life on this build. went to bed at 3am and woke up at 10am with still 100% battery on my phone, unplugged the whole night. wifi off and 3g on while i slept.

Hmmm, that sounds too good to be true! Maybe the battery meter isn't falsely reporting the percentage? At best with the old MIUI my battery would drain about 1.25%/hr, which I thought was pretty good. (this is with just 3G enabled).

I'm installing the update now... can't wait to see how my battery life fairs.
 
experiencing much better battery life on this build. went to bed at 3am and woke up at 10am with still 100% battery on my phone, unplugged the whole night. wifi off and 3g on while i slept.

That's good to hear! I left my phone uncharged and on all night (starting at 41%). Woke up to find it at 38%. So, that's definitely an improvement.

MIUI 1.11.4 has been released: MIUI, Redefining Android – MIUI Android Developers

I'm currently in the process of porting everything over. I'm considering writing a script (maybe in python or bash) to automate this process. That way if I no longer can work on this project, somebody else can take over.
 
Hmmm, that sounds too good to be true! Maybe the battery meter isn't falsely reporting the percentage? At best with the old MIUI my battery would drain about 1.25%/hr, which I thought was pretty good. (this is with just 3G enabled).

I'm installing the update now... can't wait to see how my battery life fairs.

it probably did a slight false report, but i left my phone charging all night before i went to bed and made it stay at 100% while charging for at least a couple hours, then took it off the charger and slept. i believe it's the "deep sleep" code that was added to the new build, but i'm going to try this again later today by leaving wifi on this time and doing an hourly check and reporting back on the subject matter at hand.
 
Also experiencing very good battery life. I use Batterycallibrate after installing or updating a new Rom. The app recommends that after using the app you let the phone go until it powers itself down. I turned off Juice Defender, left wifi on and expected the phone would be dead by morning but still had about 40%. This is just awesome in comparison to what I have come to expect from my phone. Thank you Isaac you truly do Rock.
One question, was the online themes one of the Miui features that has been disabled?
 
Also experiencing very good battery life. I use Batterycallibrate after installing or updating a new Rom. The app recommends that after using the app you let the phone go until it powers itself down. I turned off Juice Defender, left wifi on and expected the phone would be dead by morning but still had about 40%. This is just awesome in comparison to what I have come to expect from my phone. Thank you Isaac you truly do Rock.
One question, was the online themes one of the Miui features that has been disabled?

No, online themes were not disabled. I've used it recently, actually.
 
No, online themes were not disabled. I've used it recently, actually.

They are working now, was receiving unable to connect to server last night and this morning. I love these themes and can sit for hours checking them out. We have an engineer at work that had moved here from China a few years ago and she is also getting a kick out of it and am often using the excuse of needing a translation in order to talk with her more often than I should, thanks again Isaac.
 
Reflash the ROM, but don't wipe. It won't mess with your current set-up either. (Unless you made some changes to /system).

Oh, I definately tried it. Flashed with the current rom, then tried flashing old rom, then current. Both attempts didn't work.

And the bootscreen was the Nexus Prime one. I think its twice that its ****ed up and put me in a boot loop.
 
They are working now, was receiving unable to connect to server last night and this morning. I love these themes and can sit for hours checking them out. We have an engineer at work that had moved here from China a few years ago and she is also getting a kick out of it and am often using the excuse of needing a translation in order to talk with her more often than I should, thanks again Isaac.


As with most prepaid carriers, Sometimes there is data fluctuations or even complete loss of connectivity.

Though Miui won't always be working 100% of the time all the time. So if something isn't working try it later. =]
 
Wonderful. It seems the MIUI Android ports finally got their proper update to 2.3.7. I will have to do the conversion all over again. Sigh.

EDIT: The only major update (from me and our port) is PRL is now being grabbed from radio.
 
Just got my first random reboot ever on this don't.

Isaac I don't get some of your terminology. You keep talking about Pure Miui and Android Miui. Will there be a point that Miui is totally independent from Android?
 
Just got my first random reboot ever on this don't.

Isaac I don't get some of your terminology. You keep talking about Pure Miui and Android Miui. Will there be a point that Miui is totally independent from Android?

Pure MIUI as in MIUI given from Xiaomi. It has nothing to do with differentiating from Android stock (it's already different UI wise). MIUI is still an Android based OS with massive changes to its framework.

These groups (MIUIAndroid, MIUI.us, etc.) take the ROM that Xiaomi puts out and they translate it to English. This is fine (and much appreciated), but they also add some stuff that isn't found in the original version(s). I remove this stuff. I'm trying to give the ROM to you guys as if Xiaomi had built the ROM for our phones originally.

EDIT: There isn't anything necessarily wrong with what these groups are doing. They worked hard on translating and getting everything ported over nicely. They have every right to customize it however they see fit. Admittedly, the MIUIAndroid group doesn't change a lot (maybe a few new apps, themes and bootsplash), but I still like starting off fresh.
 
python.
bash is... well... no me gusta.
if you drop this project, i may pick it up. im a freebsd source committer, but i can always slide on over to the darkside and deal with linux for a little bit.

Porting MIUI requires a lot of smali coding and building parts from CM source as well. I'm thinking about writing a script to help this process, but I haven't determined the best way to automate decompiling and merging changes to smali code.
 
Wonderful. It seems the MIUI Android ports finally got their proper update to 2.3.7. I will have to do the conversion all over again. Sigh.

EDIT: The only major update (from me and our port) is PRL is now being grabbed from radio.


What will this change? What does PRL being grabbed from the radio mean/do?
 
What will this change? What does PRL being grabbed from the radio mean/do?

Up until recently, and this was on CM7 as well, the PRL was being "faked". To clarify, it was being set by a prop in the build.prop. It wouldn't show the actual PRL version. This is kind of a no-no. TG did this: https://github.com/tickerguy/android_frameworks_base/commit/024ca7b0d66f97cdab1bc44bc5b1ae50833b0769

So I backwards coded it into MIUI.

This won't necessarily change anything, but should users want to change their PRL, it would be nice if it would display the correct version.

Relevant: Preferred Roaming List - Wikipedia, the free encyclopedia
 
Just wanted to confirm that the battery life for me is way better (still 100% after 1 hr). Can't wait to test it overnight.

Also the Bluetooth pairing is fixed! Thanks so much Isaac!!
 
Back
Top Bottom