[ROM] MIUI.us-Sholes-1.8.26.0 [DEV]

[1FZFE]

So far so good. The swap scripts seem to be working well. Although I did initially have some trouble getting compcache started. I was getting an error message in the terminal. Ended up using gscript and its working now.

Has anyone noticed unusually high android OS battery usage ie 25-30%? Usually display uses most of my power with all of the operating system processes coming way behind. On SS5.5 it never got above about 8%. Is this kernel related or just different reporting by miui?


Sent from my CM7 NookColor using Tapatalk

[chewy74]

Still the same 2 issues for me. Wifi drop and reconnect and native browser fc trying to import bookmarks

________________________
You had me at herro

[mjh68]

Everytime I try to run a2sd command it just says a2sd not found ?

[groovydeus]

so...I have been playing with MIUI since, what, last October? Well, I had some time off yesterday from work (and wife and kids) and decided to do a study on kernels, speeds and voltages (the results of which are not important as each d1 seems to have different preferences). Anyhow - what I did stumble on is that my droid HATES a large VM Heap size. It seems that there is a movement to go with larger heap sizes as this 'seems' to make larger apps, such as big games, work faster. This obviously works well for devices with larger memories (512) but for the d1, particularly if you are running multiple apps and background processes...this seems counterproductive. For kicks I tested heap sizes of 24m, 32, 40 and 48m and then benchmarked using linpack and quadrant as well as running (the same) programs and just getting an overall feel for the devices responsiveness. Note: I use this phone for work and with the exception of solitare, rummy and jewels do not do any heavy gaming on my phone.

I did benchmark significantly higher with 24m heap size - but more importantly my d1 no longer lags to any degree and actually benchmarks faster than both the last froyo miui build and petes last froyo build. Is there anyone else out there that could validate what I am seeing? Thanks, and by the way...thanks Magi - I am really enjoying this build. Not seeing the WiFi issue.

I used VM Heap Tool to adjust, and would like to know if anyone else has played with this and what your results/feelings are with how it alters performance.

[1FZFE]

Thanks for the heads up on the VM heap size. I didn't even realize the default was 40. I have cranked mine back down to 24 as well. This has worked for me in the past. I don't think I have ever gone above 32.

Speaking of defaults, does anyone know what the compcache is set at as default? I generally use 10 or 18 I believe. And I couldn't get compcache working with Chevy LV kernel using the scripts.

[rck76]

I'm not sure if this is a rom issue or boot manager issue but when I flash chevyno1's 1100 MHz mv kernel, I get suck at the M. Anyone else have this problem?

Sent from my Droid using DroidForums

[nu2droid]

I have never played with the heap. How would you go about tweaking that?

[1FZFE]

I'm not sure if this is a rom issue or boot manager issue but when I flash chevyno1's 1100 MHz mv kernel, I get suck at the M. Anyone else have this problem?

Sent from my Droid using DroidForums

Clear cache and dalvik cache and try flashing again. Your phone might not like the combination.

[1FZFE]

I have never played with the heap. How would you go about tweaking that?

I used the VM heap tool from the market as suggested by groovydeus. Usually there is an option built into the ROM that allows you to do this as well as many more performance tweaks, such as Cyanogenmod tools or Chevy1 tools, but MIUI doesn't have this.

[rck76]

Clear cache and dalvik cache and try flashing again. Your phone might not like the combination.

Yeah, tried 3x but still won't go, works without Chevy's kernel but way too sluggish. The kernel has worked fine for any other rom I've ever flashed though. So maybe MIUI + Chevy's kernel =0?

Sent from my Droid using DroidForums