[ROM] MinimalX

[magman]

get file manager or winzip and open it touch it and click install <<<that almost sounds sexual

edit i ment to say use androzip

 

[LancerV]

You have to copy blur calendar Google calendar sync to /system/app you also have to copy the odex for each one

Sent from my DROID X2 using Tapatalk

 

[LancerV]

BlurCalendear
BlurCalendearProvider
GoogleCalendarSyncAdaptor
GoogleContactsSyncAdaptor

You need the apk and the odex for each file and than copy them from the androzip folder to /system / app and than reset the permissions to look like every other file

Sent from my DROID X2 using Tapatalk

 

[zeppelinrox]

As for the supercharger script, I'm getting mixed reports of it improving performance, and also it bogging down the system. My future plan is to test a multitude of settings to see which cooperates best with this ROM and bake them in -- in other words, you won't have to worry about installing the script yourself.

Yes so, more often than not, the user is doing something wrong.
The same mod can't have the opposite effect on the same phone.

Logic dictates that any number of outside factors is the reason.

The biggest issue has been the settings not sticking on boot.
Lagginess was a rare occurrence that was narrowed down to compcache on OG droids.
I can't recall anybody reporting lagginess on a DX2 strictly due to supercharging.

edit: oh yeah, to cook it into the ROM, using the latest update, you can change the variable (rcpath=) on line 120 to the path of your *rc file.
Then use the modified *rc file in the rom

 

[LancerV]

As for the supercharger script, I'm getting mixed reports of it improving performance, and also it bogging down the system. My future plan is to test a multitude of settings to see which cooperates best with this ROM and bake them in -- in other words, you won't have to worry about installing the script yourself.

Yes so, more often than not, the user is doing something wrong.
The same mod can't have the opposite effect on the same phone.

Logic dictates that any number of outside factors is the reason.

The biggest issue has been the settings not sticking on boot.
Lagginess was a rare occurrence that was narrowed down to compcache on OG droids.
I can't recall anybody reporting lagginess on a DX2 strictly due to supercharging.

edit: oh yeah, to cook it into the ROM, using the latest update, you can change the variable (rcpath=) on line 120 to the path of your *rc file.
Then use the modified *rc file in the rom

Yea i don't think it's the script but doesn't android usually close background applications more often I have background applications running that I haven't ever had as a background application

Sent from my DROID X2 using Tapatalk

 

[LancerV]

Haven't opened up half of these applications and there are 10 more not on those 3 screen shots

Sent from my DROID X2 using Tapatalk

 

[zeppelinrox]

Did you try option 9?
I personally think that 40mb is too low in slot 3 for 512 mb devices but users really liked it for multitasking so that's what I went with.

I'd probably put at least 60 in slot 3 then something like 75, 90, 100 for the last 3

edit: wow yeah thats alot of stuff. install something like autostarts to stop certain apps from loading on startup

 

[C21johnson]

As for the supercharger script, I'm getting mixed reports of it improving performance, and also it bogging down the system. My future plan is to test a multitude of settings to see which cooperates best with this ROM and bake them in -- in other words, you won't have to worry about installing the script yourself.

Yes so, more often than not, the user is doing something wrong.
The same mod can't have the opposite effect on the same phone.

Logic dictates that any number of outside factors is the reason.

The biggest issue has been the settings not sticking on boot.
Lagginess was a rare occurrence that was narrowed down to compcache on OG droids.
I can't recall anybody reporting lagginess on a DX2 strictly due to supercharging.

edit: oh yeah, to cook it into the ROM, using the latest update, you can change the variable (rcpath=) on line 120 to the path of your *rc file.
Then use the modified *rc file in the rom

Thank you for clarifying. I agree, the script will run the same, no matter what. If there is an issue, it is most likely related to the user. Here I'm speaking of the installation/running of the script. Still, whether or not the phone has desirable or adverse effects is dependent on the phone.

You're the guy who knows a lot about this, so please correct me if I am wrong. But Android utilizes memory in a very intelligent fashion. Background-ing important processes that are not needed to be called for or have not been called for within 'x' amount of time. Android will also kill any unnecessary processes that have been inactive for 'y' amount of time. Most importantly, Android will keep those essential processes in the foreground and prevent them from being terminated. What this creates is a balance of memory to allow multitasking on the device. For the standard user, default or named values (such as ones given in your script) will do just fine. A more advanced user who is, say, running a lot of demanding applications, running side-loaded launchers, running a multitude of widgets, will need their own "personalized" free values depending on how they use their device. It is going to be impossible there to be a set of values that will work for every user, and I don't believe that some of the users of your script realize this. What works for one person may not work for the other. Fortunately, you have added the ability in your script to set your own values, which is highly recommended for the advanced user who knows how he or she wishes to run their device.

Please correct me if I'm wrong with any of this. I'm not the most technical user when it comes to this stuff, and haven't researched it as much as I would like to.

Thanks again for posting. Your script is fabulous and works flawlessly. I've yet to have a problem getting the values to stick at boot when following the instructions carefully and correctly.

As for baking the script by changing the rcpath, I am planning on doing this eventually. I'm currently in the search for free values that will work effectively for this ROM and allow the user to still have a good amount of breathing room with their own customization.

Have a good evening everyone.

 

[zeppelinrox]

Yes you are correct and don't disagree about anything you said.
The longer a process in inactive, the higher it's "badness" score.
If memory gets low enough, say launching a large app, the apps with the highest badness scores get killed first in its OOM grouping.

The way I like to do it is to find the "sweet spot" where more free memory does not enhance performance.
For example, anything above 30 mb free ram on my milestone doesn't really make a difference in performance - anything more than 30 mb free and the performance just plateaus.
I tested the other day using mega ram 1 and had 50 mb free ram and benchmarks (I really like SmartBench 2011) were either the same or lower than when I have 30 mb free ram.

I figure on a DX2 the "sweet spot" is probably in the 75 mb range.
And I'd imagine that having 75 mb free ram at all times on a DX2 would not kill widgets or apps unnecessarily while keeping performance at it's peak level.

 

[in99flames]

BlurCalendear
BlurCalendearProvider
GoogleCalendarSyncAdaptor
GoogleContactsSyncAdaptor

You need the apk and the odex for each file and than copy them from the androzip folder to /system / app and than reset the permissions to look like every other file

Sent from my DROID X2 using Tapatalk

Trying to copy...tells me the move fails each time. Copying also fails each time.... hmm

 

[LancerV]

How are you trying to copy?

Sent from my DROID X2 using Tapatalk

 

[in99flames]

Using the copy or move options from androzip. I would select the files i want to move this way. It does fail when i try to paste.

Sent from my DROID X2 using DroidForums

 

[LancerV]

Using Autostarts to kill a bunch of rouge apps seems to have stopped it

Sent from my DROID X2 using Tapatalk

 

[hobby31]

Sorry, I didn't have time to read through all the post. When is the contacts "popping up"? Is it after waking the phone? Mine was doing this on stock rooted and I finally tracked it down to my "pinky" finger touching the corner or the bottom left hand side just below the dailer icon. I would wake my phone and the contacts would be up and I couldn't figure out why. Then one day as I was reaching up with my index finger to turn the screen off I happen to catch a glimpse of the contacts popping up as the screen went off. I started paying attention and when I would reach up with my index finger my pinky finger would grip the phone a little tighter and slightly touch that area of the screen. Since then i've been more careful and haven't had that since. Anyway, just throwing out a possibilty.

 

[riot]

Alright I found my first issue. If I restart my phone it sticks on the boot screen causing me to have to remove the battery and bitting again. I am not sure what causes it, where do I go to see a system log or something so I can do some digging? Thanks

Sent from my DROID X2 using DroidForums