DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
[GUIDE] Milestone XT720 - Apps2SD and Froyo JIT
- Thread starter Navalynt
- Start date
Phone set to memory card access, and then format with Windows, just set "size of allocation unit" or what it's in English =)
I even did all the partitioning through this mode, and an app called
"MiniTool Partition Wizard Home Edition"
I'm glad to hear you guys testing out the other firmwares! I just don't have the time for that right now 
So, is the general consensus that the Russian firmware is the current performance leader? I had version 4 of the optimizer setup already for the Russian firmware but moved on to version 5 and altered for US CBW version. I can go back to the Russian firmware and juice up a version 6 tonight to test out. Specifically, I can edit a new build.prop to give it the fingerprint of the US version so the market shows in US dollars.
So, is the general consensus that the Russian firmware is the current performance leader? I had version 4 of the optimizer setup already for the Russian firmware but moved on to version 5 and altered for US CBW version. I can go back to the Russian firmware and juice up a version 6 tonight to test out. Specifically, I can edit a new build.prop to give it the fingerprint of the US version so the market shows in US dollars.
Russian build is Aug 4, i.e. about 2 weeks newer than CBW build, also some google services (if that is gms) are newer. I used your script to upgrade russian build, had to manually edit install.sh to comment out commands referencing to copying build.prop. This helps to keep proper locale, and language customizations. Ru firmware by default has RU-EN keyboard with easy switching between two. I also noticed that your script still copies MilestoneOverclock to memory, commented that out too.
I think we would be better off, if build.prop param experiments are explained so that people with various regional firmwares, can easily upgrade JIT and move Apps2sd, then manually add what is important to them, to build.prop.
I had to compare my current build.prop with one in the optimizer, and here is what I noticed
raised WiFi scan interval from 45 to 90
reduced call delay from 3sec to 800msec
windows manager 60 fps
dalvik int:jit
heapsize - raised from 28M to 38M. Here I am not sure that it is good for a device with so little memory. I actually try to reduce heap size to 24M to allow more programs stay in memory, to prevent closing of background apps.
also I noticed that you raised video encoing bps from 3MBps to 6. Will have to test if there is any improvement in video quality.
I think we would be better off, if build.prop param experiments are explained so that people with various regional firmwares, can easily upgrade JIT and move Apps2sd, then manually add what is important to them, to build.prop.
I had to compare my current build.prop with one in the optimizer, and here is what I noticed
raised WiFi scan interval from 45 to 90
reduced call delay from 3sec to 800msec
windows manager 60 fps
dalvik int:jit
heapsize - raised from 28M to 38M. Here I am not sure that it is good for a device with so little memory. I actually try to reduce heap size to 24M to allow more programs stay in memory, to prevent closing of background apps.
also I noticed that you raised video encoing bps from 3MBps to 6. Will have to test if there is any improvement in video quality.
gommers1978
New Member
Hi there, i'm allso on the russian firmware now, have a class 10 16Gig SDHC card on the european firmware still lags sometime so it is not the SD card that gives the recording problems. Now on russian firmware, removed the MobiDiv keyboard so have normal android keyboard now. Can confirm that HD recording is smooth now with 21fps in low light conditions. Will try in daylight and see if the fps will become better or stay at 21. Hope together we can come to a perfect HD recording as long as Motorola does not produce a fix.
gommers1978
New Member
I have the same problem with te prices in the app market. I do not buy things from the app market so it is not that big a problem for me. But still trying to make the prices OK, no success yet. Anybody has any idea how to solve this??
P.S. Recording with russian firmware in daylight still 20fps...... but stable no lag.
Strange, I get SEK which is the correct value for me.
And when I press buy, it has correctly converted the currency.
And I didn't change anything.
gommers1978
New Member
I allso have the right currency € but the price is 33,5 instead of 0,99 so it is still in russian price only the currency symbol has changed..
Mazinkaiser
New Member
Gommers please upload on megaupload or youtube for check video quality if you can.
(the choppy HD recording is the only thing that holds me to buy this phone)
AH
i forgot, is possible to zoom during a video? or zooming before start recording (on european milestone, that cannot do).
(the choppy HD recording is the only thing that holds me to buy this phone)
AH
i forgot, is possible to zoom during a video? or zooming before start recording (on european milestone, that cannot do).
Last edited:
Well, here's something to play with for the weekend:
European - STR_U2_01.1E.0
Italian - STR_U2_02.1E.0
Russian - STR_U2_03.20.1
US CBW - STR_U2_04.1E.1
TWO themes included: The NexTheme-Mod and a port of Slayher's Genesis theme from CM6. The script is updated to let you choose which one you want to install (if any). I'll upload screenshots of Genesis later this evening.
Each of the build.prop files has been modified with the fingerprint of the US CBW version to hopefully show the Market in US Dollars. I left a copy of the unmodified (original) build.prop file in the folders as well so you guys can make your own changes if you would like.
Also, cleanup script is a separate script in the folder, and it's not working just yet. I'll try to get that fixed later tonight as well and get a big update done to the first post.
Edit: Dalvik-cache is also back on the /system/sd (ext2 partition) for all of the scripts above because there was no performance increase by using the /cache partition
European - STR_U2_01.1E.0
Italian - STR_U2_02.1E.0
Russian - STR_U2_03.20.1
US CBW - STR_U2_04.1E.1
TWO themes included: The NexTheme-Mod and a port of Slayher's Genesis theme from CM6. The script is updated to let you choose which one you want to install (if any). I'll upload screenshots of Genesis later this evening.
Each of the build.prop files has been modified with the fingerprint of the US CBW version to hopefully show the Market in US Dollars. I left a copy of the unmodified (original) build.prop file in the folders as well so you guys can make your own changes if you would like.
Also, cleanup script is a separate script in the folder, and it's not working just yet. I'll try to get that fixed later tonight as well and get a big update done to the first post.
Edit: Dalvik-cache is also back on the /system/sd (ext2 partition) for all of the scripts above because there was no performance increase by using the /cache partition
Last edited:
Thank a lot Mr Navalynt. I wouldn't be feel bore this weekend.
By the way, i have a question to you about moving cache to system cache. When we move dalvik-cache to system cache partation, all system app cache move to cache partation or some part only? Let say our system memory is 173, normally 120 around left before using apps2sd. On my phone when never i use your optamizer v5 that include scripts to install busybox, only one dalvik-cache(system@[email protected]@classes.dex) is move to system cache partation.System memory is still left 120 around. Is this correct? In another way, i modify your install.sh(remove the script to install busybox) and use market busybox app to run apps2sd- all system app cache are move to system cache partation. Let's say system cache is down from 106 to 66.5 around.System memory left 165 around.
So which way is correct? or my phone is something wrong? I am still confusing because i am still new in this android OS. Thank!
By the way, i have a question to you about moving cache to system cache. When we move dalvik-cache to system cache partation, all system app cache move to cache partation or some part only? Let say our system memory is 173, normally 120 around left before using apps2sd. On my phone when never i use your optamizer v5 that include scripts to install busybox, only one dalvik-cache(system@[email protected]@classes.dex) is move to system cache partation.System memory is still left 120 around. Is this correct? In another way, i modify your install.sh(remove the script to install busybox) and use market busybox app to run apps2sd- all system app cache are move to system cache partation. Let's say system cache is down from 106 to 66.5 around.System memory left 165 around.
So which way is correct? or my phone is something wrong? I am still confusing because i am still new in this android OS. Thank!
Thank a lot Mr Navalynt. I wouldn't be feel bore this weekend.
By the way, i have a question to you about moving cache to system cache. When we move dalvik-cache to system cache partation, all system app cache move to cache partation or some part only? Let say our system memory is 173, normally 120 around left before using apps2sd. On my phone when never i use your optamizer v5 that include scripts to install busybox, only one dalvik-cache(system@[email protected]@classes.dex) is move to system cache partation.System memory is still left 120 around. Is this correct? In another way, i modify your install.sh(remove the script to install busybox) and use market busybox app to run apps2sd- all system app cache are move to system cache partition. Let's say system cache is down from 106 to 66.5 around.System memory left 165 around.
So which way is correct? or my phone is something wrong? I am still confusing because i am still new in this android OS. Thank!
Well, I did not see any improvement in performance by moving the dalvik-cache to /system instead of the ext2 partition so in the revisions above I actually put it back on /system/sd. Plus, it was flaky for people as to whether or not it would actually move to the /cache partition.
Right now I'm experimenting with bitrates and framerates defined by the build.prop to see if we can get 720p video recording smooth and higher quality across the board. If I get it working nicely I'll update the files linked to above.