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

Root MIUI port questions

Wheee!..... this is like waiting for Christmas to come when i was a little kid. I am sooooo stoked about MIUI! Love all the work isaacj87! Thanks for all your effort!
Ran the wifi only version but got a million FC's so i'm gonna try and load it again a different way just to oogle it some more.
 
apsterling said:
Gotcha. I'm really excited and thankful that you're taking this on!
Click to expand...

I'm enjoying it. You guys are probably wonder what's taking so long for me to put a build up. There's one big hurdle I'm trying to get over: getting our missing RAM back.

When I rebuilt the kernel to fix the keymapping (the spice kernel sources *should* work, but they don't for whatever reason), I adjusted the kernel to VMSPLIT3G (3G/1G). The transition went okay, but we lost 256 megs of our RAM. The ROM still runs okay, but if you start downloading and using apps, the system will slow down. I don't use apps, so I don't have this problem.

The good news is, however, that most of the things not working on the X6 port are fixed in ours. I fixed GPS, WIFI (it got broke when I rebuilt the kernel), RIL/3G (obviously, and the carrier label "Virgin Mobile" is fixed), and MMS (can send, but not receive). The camera app (back only) actually works, but it's very picky. You have to run the app immediately after booting or else it won't ever come up. I also went ahead and bumped us up to the latest version of MIUI (1.9.30). I'm just trying to figure out how to get us back to 512 MB.

Worse comes to worse, I'll just package everything I have right now and put out a "caveman" build preview.

screenshot_2.png
 
isaacj87 said:
I'm enjoying it. You guys are probably wonder what's taking so long for me to put a build up. There's one big hurdle I'm trying to get over: getting our missing RAM back.

When I rebuilt the kernel to fix the keymapping (the spice kernel sources *should* work, but they don't for whatever reason), I adjusted the kernel to VMSPLIT3G (3G/1G). The transition went okay, but we lost 256 megs of our RAM. The ROM still runs okay, but if you start downloading and using apps, the system will slow down. I don't use apps, so I don't have this problem.

The good news is, however, that most of the things not working on the X6 port are fixed in ours. I fixed GPS, WIFI (it got broke when I rebuilt the kernel), RIL/3G (obviously, and the carrier label "Virgin Mobile" is fixed), and MMS (can send, but not receive). The camera app (back only) actually works, but it's very picky. You have to run the app immediately after booting or else it won't ever come up. I also went ahead and bumped us up to the latest version of MIUI (1.9.30). I'm just trying to figure out how to get us back to 512 MB.

Worse comes to worse, I'll just package everything I have right now and put out a "caveman" build preview.

screenshot_2.png
Click to expand...


Tjstyles comments didn't fix the problem?
 
isaacj87 said:
I'm enjoying it. You guys are probably wonder what's taking so long for me to put a build up. There's one big hurdle I'm trying to get over: getting our missing RAM back.

When I rebuilt the kernel to fix the keymapping (the spice kernel sources *should* work, but they don't for whatever reason), I adjusted the kernel to VMSPLIT3G (3G/1G). The transition went okay, but we lost 256 megs of our RAM. The ROM still runs okay, but if you start downloading and using apps, the system will slow down. I don't use apps, so I don't have this problem.

The good news is, however, that most of the things not working on the X6 port are fixed in ours. I fixed GPS, WIFI (it got broke when I rebuilt the kernel), RIL/3G (obviously, and the carrier label "Virgin Mobile" is fixed), and MMS (can send, but not receive). The camera app (back only) actually works, but it's very picky. You have to run the app immediately after booting or else it won't ever come up. I also went ahead and bumped us up to the latest version of MIUI (1.9.30). I'm just trying to figure out how to get us back to 512 MB.

Worse comes to worse, I'll just package everything I have right now and put out a "caveman" build preview.

screenshot_2.png
Click to expand...

Sounds good to me.
 
JollyRoger87 said:
You work for GEICO?
Click to expand...

haha nice. no, I live inside a cave and bang on stuff with rocks. I also grew my beard like moses.

the last build if miui I was on musta been something like 1.1.28... I'm super pumped to see the changes. the lockscreens they implemented with their gb update were pretty much awesome. I haven't even flashed the other build because I don't have a compatible recovery and I've been too lazy to change it.
I'm glad we have a good chef cooking this rom up. over on miui.us we had stiffspliff and a few other guys who took on the responsibility of keeping the port updated. could u imagine if we couldn't flash roms and actually had to wait for ota updates from service providers? ha, what a joke.
 
apsterling said:
Good thing to hear! :D
Click to expand...

Yeah, I just had to fix this. It was driving me nuts. I'm not exactly sure I got all of it either.

Code: 
<6>[    0.000000] Initializing cgroup subsys cpu 
<5>[    0.000000] Linux version 2.6.32.9-perf ([B]ikarosdev@chaos76[/B]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT [B]Sun Oct 2 00:52:32 CDT 2011 [/B]<--- [I]WTF, Isaac? You should be asleep![/I]
<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] Truncating RAM at 20000000-2fffffff to -2e1fffff (vmalloc region overlap). 
<5>[    0.000000] Ignoring RAM at 80000000-8003ffff (vmalloc region overlap). 
<7>[    0.000000] On node 0 totalpages: 105984 
<7>[    0.000000]   Normal zone: 1472 pages used for memmap 
<7>[    0.000000]   Normal zone: 0 pages reserved 
<7>[    0.000000]   Normal zone: 104512 pages, LIFO batch:31 
<4>[    0.000000] BUG: mapping for 0x07b00000 at 0xf2000000 overlaps vmalloc space 
<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 19922944 bytes at c2000000 (2200000 physical) for sf pmem arena 
<6>[    0.000000] allocating 25165824 bytes at c7e00000 (8000000 physical) for adsp pmem arena 
<4>[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 104512 
<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) 
<6>[    0.000000] [B]Memory: 60MB 128MB 226MB = 414MB total [/B]
<5>[    0.000000] [B]Memory: 350336KB available (7048K code, 2011K data, 184K init, 0K highmem) [/B]
<6>[    0.000000] Hierarchical RCU implementation.
...but for those who tried out the X6 version, you'd would be disappointed with the performance of my port with only 256MB available. Everything was so sluggish and nasty. Now that it's back, it's much smoother and on par with before. :)
 
isaacj87 said:
Yeah, I just had to fix this. It was driving me nuts. I'm not exactly sure I got all of it either.

Code: 
<6>[    0.000000] Initializing cgroup subsys cpu 
<5>[    0.000000] Linux version 2.6.32.9-perf ([B]ikarosdev@chaos76[/B]) (gcc version 4.4.0 (GCC) ) #1 PREEMPT [B]Sun Oct 2 00:52:32 CDT 2011 [/B]<--- [I]WTF, Isaac? You should be asleep![/I]
<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] Truncating RAM at 20000000-2fffffff to -2e1fffff (vmalloc region overlap). 
<5>[    0.000000] Ignoring RAM at 80000000-8003ffff (vmalloc region overlap). 
<7>[    0.000000] On node 0 totalpages: 105984 
<7>[    0.000000]   Normal zone: 1472 pages used for memmap 
<7>[    0.000000]   Normal zone: 0 pages reserved 
<7>[    0.000000]   Normal zone: 104512 pages, LIFO batch:31 
<4>[    0.000000] BUG: mapping for 0x07b00000 at 0xf2000000 overlaps vmalloc space 
<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 19922944 bytes at c2000000 (2200000 physical) for sf pmem arena 
<6>[    0.000000] allocating 25165824 bytes at c7e00000 (8000000 physical) for adsp pmem arena 
<4>[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 104512 
<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) 
<6>[    0.000000] [B]Memory: 60MB 128MB 226MB = 414MB total [/B]
<5>[    0.000000] [B]Memory: 350336KB available (7048K code, 2011K data, 184K init, 0K highmem) [/B]
<6>[    0.000000] Hierarchical RCU implementation.
...but for those who tried out the X6 version, you'd would be disappointed with the performance of my port with only 256MB available. Everything was so sluggish and nasty. Now that it's back, it's much smoother and on par with before. :)
Click to expand...
Very nice! It'll be nice to not have the phone Force Close constantly too.
 
Hey Isaac,

Back when I had the EVO 4G, MIUI was known for having AMAZING battery life. Have you noticed this variant having good battery life too?

Just curious.
 
You must log in or register to reply here.
Back
Top Bottom