yashsingh1/xdaforums huggingface dataset:
[Milestone XT720 Android Development] Mioze7Ae:
I used root explorer to create /sd-ext/dalvik-cache and rebooted. The phone sat at the M for a while and the rebooted itself once more and came up just fine. After the reboot /cache/dalvik-cache was gone, /cache was mostly empty and /sd-ext/dalvik-cache was full of files. I then updated 8 apps in Market without problem. I then used wipe dalvik-cache in androidiani recovery and that worked, too. (Should work in vanilla open recovery also)

TL;DR: Migrating to /sd-ext/dalvik-cache works as expected.
[Milestone XT720 Android Development] Mioze7Ae:
After a second test I don't think wipe dalvik cache is working. I see if I can come up with something.
[Milestone XT720 Android Development] Knoedelkopf:
Uhm question:

I set that dalvik cache should be moved to sd-ext... when I use root explorer I can see the dalvik-cache folder in /sd-ext/link2sd/

but there is also another dalvik-cache folder in /data/

so there are two different dalvik caches ?! one at internal storage & one at sd-ext partition??:confused:

at the dalvik cache folder @internal storage there is also the cache from apps that were moved to sd-ext (dalvik cache was also moved with link2sd to the ext-partition, )

I mean apps that were moved to sd-ext with their dalvik cache shouldn't have their dalvik cache at internal storage AND sd-ext
[Milestone XT720 Android Development] Mioze7Ae:
Aha! That's a really good question! That might explain some of the strange reports I've been puzzling over.

Link2SD is a special case because it will let you manually move dalvik-cache with app that you move to /sd-ext. In the same way that using link2sd+/sd-ext/app at the same time doesn't make sense, link2sd+/sd-ext/dalvik-cache might not make sense. However, the boot scripts forbid link2sd+/sd-ext/app, but don't forbid link2sd+/sd-ext/dalvik-cache.

I'm hesitating making the change to forbid link2sd+/sd-ext/dalvik-cache, though because I'm not sure the correct way to wipe the link2sd dalvik-cache. One challenge with this feature in link2sd is that there's no way I know of to correctly rebuild the cache with some of them moved to sd-ext and some of them internal. Open Recovery's Wipe Dalvik Cache and the the boot system certainly don't understand that some files shouldn't be rebuilt somewhere other than the default location. This is dangerous because in principle you can end up with a phone that doesn't have enough space to rebuild dalvik-cache after it's been wiped.

At the moment, I don't know what to do about this other than advise people not to use link2sd's move dalvik-cache feature.
[Milestone XT720 Android Development] ktylife:
I am also using link2sd, but I did not intentionally order him to move the Dalvik cache.

I find dalvik-cache in the following location;

* /cache/dalvik-cache

* /data/dalvik-cache

* /data/sd-ext2/dalvik-cache

* /sd-ext/dalvik-cache

Please advise ! :confused::D
[Milestone XT720 Android Development] Tavinsky:
This how I do it? After installing the ROM patches Dexter and I have not set anything sd-ext partition.

Yesterday I cleaned the cache dalvik to download some applications of 4 megs, the download but could not install, the message says "Invalid package", which may be malfunctioning?
[Milestone XT720 Android Development] Tavinsky:
Why use the application Link2sd, if with Froyo can move applications to the sd? is not the same? Link2sd used for something else?
[Milestone XT720 Android Development] Knoedelkopf:
App2ext moves ALL apps automatically to ext-partition... Link2SD moves SELECTED apps to ext-partition... native Froyo app2sd moves just half of the apps and also only if the developer allowed to.

in my opinion apps that are automatically started after boot shouldn't be moved to sdcard.. for example launcher or so..
[Milestone XT720 Android Development] Knoedelkopf:
WOW, VERY confusing !

so what should I do now.. using link2sd I moved many apps including their dalvik cache to sd-ext. maybe because of the chaos with all those "dalvik-caches" my phone crashes pretty often while playing games (that were most moved to sd)??

and which "dalvik-cache" does OR clean up ? :confused:

and which "dalvik-cache" can I delete by using root explorer ? :confused:

UUAARRGH ! :D:D

wow ktylife even found FOUR "dalvik-cache" folders !:p
[Milestone XT720 Android Development] d23wilson:
The cache/dalvik-cache and data/dalvik-cache are the same directory...just a pseudonym I suppose. If u have root explorer u can see more accurately I think.

Plus with links2sd the original dalvik-cache will remain only with reference (I.e. a link reference) to where the "real" cache now sits...in the sdcard..which can be seen under data/sdext

Those that are linked can usually be seen (via root explorer) as having a ridiculous long set of attributes...like rwrrrrrxwr..bit exaggerated but something like that.

The multiple directories and versions are all valid as far as I can see...so nothing to get overly concerned with.

On another note...a FYI ...smart keyboard allows you cursor control via volume buttons...sometimes its really hard to get the cursor exactly where u want it? Then u have to toggle they the keyboards to get to the movement arrow keys?? (Ie pain in the butt) With smart keyboard the latest version gives u cursor control via the up down buttons...just mentioning it cos I love that feature

Sent from my XT720
[Milestone XT720 Android Development] d23wilson:
Duuudes

Additional info I found for link2sd...if u wipe your dalvik cache..at reboot all dalvik caches are built again on internal memory...maybe that is what u are seeing different from me (if u read my previous post) which sees 2 versions of dalvik cache files. I think (suckily) we have to go to links2sd and redo them all manually...or ask the app author if they could do something about that?

Sent from my XT720
[Milestone XT720 Android Development] Mioze7Ae:
So, in theory, we can add a boot script to clean some of this up. We compare the directories and move/remove duplicates.

The problem is: suppose there is not enough disk space to rebuild all of the dalvik internally. Suppose you have 40MB of space for the internal dalvik-cache. Then you install apps and fill up say 30MB of the 40MB. Then you use link2sd to move 20MB of the 30MB from internal to external. Then you've got 10MB of 40MB used internal and 20MB additional on external. Then you install more apps and end up with an additional 25MB on internal cache. So in internal memory you've got 10MB+25MB=35MB (5MB free) and you've got another 20MB dalvik on external. Then you wipe dalvik-cache. On next boot you have to build 55MB dalvik, but you've only got internal space for 40MB. What happens? Do you get a bootloop? What can we do about this?

Idea: Maybe we can forbid wiping cache in the link2sd external and automatically recreate links at boot so that link2sd dalvik is never rebuilt?
[Milestone XT720 Android Development] d23wilson:
Yeah exactly...maybe restriction is best in this case...as the functionality to cater for it might be more effort than reward returned.

Sent from my XT720
[Milestone XT720 Android Development] ktylife:
Duuuuuuuudes :D

I am totally lost with this Dalvik cache topic; hope you can solve it for me :cool:

What I can say though is that, very often, maybe after installing an apps, whenever I reboot I got stuck into bootloop. I need to go into recovery mode and wipe (or try to) the Dalvik-cache. After this I can boot fine.

Does it help you guys to draw a genius conclusion ? :o:D
[Milestone XT720 Android Development] d23wilson:
Not a genius conclusion...but one that works :) when u have ur phone up and running, go into links2sd and select every program you currently have on sdcard and redo the create link so the dalvik cache is moved....I just did it after I trial the issue and I now have around 60mb free on the cache partition where I had only 22mb free before that...so that will give u back loafs of space...it will take u a couple of.mins to do...and vigilance is the price u pay for a clean smooth running xt720 ;)

Sent from my XT720
[Milestone XT720 Android Development] Tavinsky:
Should there be any partition on sd?
[Milestone XT720 Android Development] d23wilson:
Sorry...I meant the cache partition (internal) went from 22mb free to 60mb free when I manually re linked all the programs...because all the meat of the dalvik cache went to sdcard...remember the file stays on cache...but is only a pointer to the real file now on sdcard.

The dalvik cache that resides on the sdcard directory increased in size...but who cares. That one was created by link2sd app author.

So ultimately you have 2 dalvik cache directories...one that is internal (resides on internal cache partition) and 100 mb in size...that should have loads of free space after the link exercise...those apps dalvik cache references (within this directeory) will just point to the links2sd directory on the sdcard.

That directory on sdcard size can go well over 100mb...depends on how much space u allocated to your sdcard partition.

Another thing to note....when u download market updates they get stored on the cache partition too (don't know how long for...does not happen 100% of the time but it does happen). I had about 20mb in downloaded updates consuming my cache partition. So u have various things affecting the cache paartition...and if dalvik cache is not available for apps then u know what can happen.

Sent from my XT720
[Milestone XT720 Android Development] modry:
EDIT: Nevermind I figured it out.
[Milestone XT720 Android Development] Mioze7Ae:
Here's an untested best-guess patch for entering fastboot by holding volume down while booting.

Place in /sdcard/OpenRecovery/updates

OpenRecovery > nandroid > backup > Backup system.img (just in case)

OpenRecovery > Apply update > update-volumedown-mot_boot_mode-Mz01.zip

Reboot (no need to wipe anything)

Hopefully you boot up into Android

Reboot and hold volume down while booting

Hopefully you enter fastboot

Messing with the hijacks may leave your phone unbootable (worst case you'll have to sbf). In this case, I'm pretty confident you will be able to renter OpenRecovery if things go bad and restore the nandroid backup of system.img.

Probably works on Dexter 1.3-based ROMs (Khals ROMs, MIUI XT, RusMod).

This patch will not work on eclair-strikes-back

If you're not certain, you can compare the /system/bin/mot_boot_mode.p1.sh on your phone to the one in the update. The only difference should be the call to /system/xbin/extra_boot_mode.

Please report success or failure in appropriate ROM thread. I don't have time to test this on all the ROMs myself, but I do monitor every XT720 thread so I will see problems.
[Milestone XT720 Android Development] syrenz:
This would potentially allows us to enable fastboot every time just by holding volume down? I've seen people talk about improvements when using swap/fastboot, but I never actually bothered trying it out when I found that I would have to connect my phone to my pc and enter ADB command every time I wanted to use it. Or am I not understanding something?
[Milestone XT720 Android Development] Mioze7Ae:
No, you still have to boot from USB. It's just a minor shortcut for the phone side of the process.
[Milestone XT720 Android Development] syrenz:
Alright. Well, thanks anyways :)
[Milestone XT720 Android Development] mchlbenner:
This does take you into fastboot but you can't boot to Droid know I was wondering if you fastboot a different bootloader on this though fastboot USB.
[Milestone XT720 Android Development] Mioze7Ae:
I think fastboot is part of the bootloader. The patch isn't doing anything fancy other than reading the key state and running "/system/bin/reboot bootloader" if volume down is pressed.
[Milestone XT720 Android Development] LibertyMonger:
Very nice feature bud

Very much appreciated! Very handy and helpful, it enables us to enter fastboot directly from power on to avoid Powering on then rebooting back and then fastbooting the fjfalcon kernel. Especially nice for me since I am always swapping in my backup batteries. Nice work dude! Thanks for all your good work.
[Milestone XT720 Android Development] polda78:
Yess, it's very handy indeed. But i really wish that we could also apply fjfalcon directly from our phone
[Milestone XT720 Android Development] fwals:
thank you ...I have upgraded nearly 170 mobile phone memory .Space larger. Faster

My English is very poor im sorry .But this will not compare to waste electricity??
[Milestone XT720 Android Development] ktylife:
FYI, the second link you gave links to Mioze7Ae-XT720-patch-stock221v13-bugfix-2-0-g2e2362d.zip (19MB, update fails) while the first one links to stock221v13-bugfix-2_signed.zip (9MB, update works).

They totally different content :D
[Milestone XT720 Android Development] fwals:
2 are not the same as the content? My second link to upgrade ah
[Milestone XT720 Android Development] Mioze7Ae:
I've been running this update for the last week and I did not notice a change in battery drain, but I have not been focusing on battery use. Any suggestions or tweaks for improving battery performance are welcome.
[Milestone XT720 Android Development] Mioze7Ae:
Thanks for pointing that out. I've updated the second link. Sorry for the inconvenience.
[Milestone XT720 Android Development] hellmonger:
LOL GPS off

APN off and on 2G if in use

WIFI off when screen off screen

Screen to max dim

TskM set to maxkill When screen off

Stock clock OC

You want max batt???? don't use it unless your using it!!
[Milestone XT720 Android Development] Mioze7Ae:
Experimental patch for conservative governor

c19932 requested enabling the conservative governor.

I found that nadlabak's pre-compiled module from http://android.doshaska.net/conservative seems to load and work fine.

Attached is an experimental patch that installs and loads the conservative governor. I've done very, very minimal testing on a phone running bugfix-2 (it loads, SetCPU can select it, and it seems to do what it's supposed to do based on watching the CPU speeds displayed SetCPU). It should also work on bugfix-1
[Milestone XT720 Android Development] ktylife:
edit: found info !
[Milestone XT720 Android Development] fwals:
This is not to be upgraded?
[Milestone XT720 Android Development] fjfalcon:
With fastboot we have it module enabled.
[Milestone XT720 Android Development] sariugur:
worked perfectly fine on my xt720 with dexter's froyo v1.3 and Mioze7Ae's first bugfix patch 1. just applied this update and wiped dalvik-cached then rebooted device and it's really good. performance is better now(in general use and games too), all the apps(both on internal memory and sdcard) remain fine and i had almost 50MB more free internal space(it was 95MB before patch, now i got 138MB free space). so the bottom line is, u gotta install this patch and say thnx to our developer ;))

by the way, what is "conservative governor"?? i think its about overclocking right?
[Milestone XT720 Android Development] klayton76:
I have a problem after installing the patch being ... V2 conficurazione initial account access google me crashes
[Milestone XT720 Android Development] reaperzero:
i just applied the patch on top of the stock221v13-bugfix-1.

no problems so far.
[Milestone XT720 Android Development] klayton76:
Patch Fix V2 Problem Crash Configuration initial Google Account...!!! Please Help Me...
[Milestone XT720 Android Development] scumm_boy:
A quick question: is the interactive governor not enabled in this patch? Every time I try to enable it, SetCPU force closes.
[Milestone XT720 Android Development] Mioze7Ae:
Try "Wipe Dalvik Cache" and "Wipe Cache Partition" in OpenRecovery. If that doesn't work, try "Factory Reset". Do you have an ext partition?
[Milestone XT720 Android Development] Mioze7Ae:
It works for me. In the past when interactive is listed and doesn't work, the entire phone freezes and you have to pull the battery. I've not seen force close behavior in SetCPU. Both interactive and conservative are working for me.
[Milestone XT720 Android Development] IronMit:
quick question; am I supposed to go into open recovery and wipe dalvik cache every now and again? and wipe cache partition? I'm on dexters 1.2 still and have an ext partition.

I'm going to update later when i have more time....just seems like I'm slowly getting more lag over time on my current rom
[Milestone XT720 Android Development] ktylife:
Best patch ever so far !

Phone is finally smooth and responsive (thanks to the 40-50MB of free RAM), it's enjoyable, at last !

I am also running at 1GHz@56vsel, governor set to ondemand for everything expect interactive when screen is off. :cool:

On the "hopeless" side, the camera of this phone is a disaster, I am so disappointed, this was false advertisement. :mad:
[Milestone XT720 Android Development] klayton76:
Thanks ... I have done a factory reset but the problem does not solve it ... no I do not have a partition EXT
[Milestone XT720 Android Development] c19932:
hello Mioze7ae. I applied the patch but for no reason conservative is still not listed in setCPU? I am currently using the ramdisk you posted a whil ago for interactive governor
[Milestone XT720 Android Development] Mioze7Ae:
Ok. I would reinstall starting from nandroid restore of Dexter's stock221v13, apply bugfix-2, factory reset, reboot.
[Milestone XT720 Android Development] Mioze7Ae:
The conservative patch requires the ramdisk from bugfix-1 or bugfix-2. If you extract the .zip you can maybe figure out how to port it. The ramdisk starting in bugfix-1 is designed to make modular updates easier.

I can't remember the nuances of the old ramdisk, but maybe it may work to move 00_conservative from /system/etc/init.c/ to /system/etc/init.d/
[Milestone XT720 Android Development] klayton76:
I applied the patch v1 a work ... but v2 does not set up the account google :cool:
[Milestone XT720 Android Development] c19932:
ok thanks. I will extract and replace my current ramdisk with the one from bugfix-2 and see if that works once I get home. Will report later
[Milestone XT720 Android Development] scumm_boy:
Sorry, this was my own stupidity. I uninstalled and reinstalled SetCPU and it works fine now.
[Milestone XT720 Android Development] Tavinsky:
Then I can update the patch 2 without problems after I did the following:

Before, ROM 2.1

Later, Dexter's v1.3 ROM

Then Patch 1

The telephone changed totally, smoother, softer, more stable, and a "little" more space by moving apps to the SD.

Now I continue to question whether I should upgrade the second patch having already installed the first?

After changing the ROM I have not done anything to clean cache or system changes, I've been just installed my apps and move some of the sd. I guess I should not have problems after applying the update?

Greetings!
[Milestone XT720 Android Development] c19932:
Success!

First I tried applying the new ramdisk. That did allow conservative governor in setCPU but sdcard/oc-settings stopped working. However, most likely that is a problem with the rom I am currently using because sdcard/oc-settings did not work initially with the rom, and I had to apply your interactive-fix ramdisk for sdcard/oc-settings to work.

Then I tried using the old interactive-fix ramdisk and moved 00_conservative to init.d. That allowed conservative governor + working sdcard/oc-settings.

thank you very much for your help!
[Milestone XT720 Android Development] Tavinsky:
My Regards! Congratulations Gentlemen, The ROM and the patch works great on the phone, I'm super excited about these changes, before or dreamed of having more space, now 25 mgs I had, went up to 97 mgs, even though you installed the google maps, latitude and places.

Thanks again, now I will continue to review the operation, if I find an error, I comment, but apparently everything works fine.

Greetings!
[Milestone XT720 Android Development] Mioze7Ae:
The reason this didn't work is because in the old ramdisk, the oc-settings file is loaded by the monolithic /system/oc, but the newer ramdisks replaced the monolithic file with multiple files inside the new /system/etc/init.c/ directory (it's similar to init.d, but runs much earlier in boot).

When you tried to simply replace the ramdisk, 05_overclock was missing on your phone and the new ramdisk also didn't run /system/oc, so nothing tried to load your oc-settings. I think you could simply move or copy /system/oc to /system/etc/init.c/00_oc to use the new ramdisks. If you instead tried to port the init.c back, be aware that 10_sdext needs /system/xbin/e2fsck which is installed by bugfix-1 and bugfix-2.

Splitting the oc file up is convenient for using the OpenRecovery updates mechanism because it's easy to add, replace, delete files from an update.zip. With the new ramdisk, bugfix-1 split the functionality of /system/oc into 00_interactive, 05_overclock and 10_sdext (bugfix-2 also added 15_memhack and 99_stalelinks). The conservative update then just simply added the conservative module and 00_conservative. Another advantage to using separate files is they run in order, but independently. So if there's a bug/failure in one it won't prevent the later ones from running, whereas the monolithic oc would just stop and continue the boot process.
[Milestone XT720 Android Development] hellmonger:
I had a swap partition and i belive that it would cause a boot loop after this patch

Tokk me for ever to figure it out\

i might be wrong but if i have a swap partition on my SD card this wont booot...

but like i said i might be wrong

Without the swap partition the rom does what it says... very stable and my ext2 is reconized but not I think scaned at boot... not sure if its supposed to either
[Milestone XT720 Android Development] c_urbanek:
one mirror good, one bad

:)the version at the "multiupload" mirror works beautifully! the other, not so much for me....
[Milestone XT720 Android Development] scumm_boy:
I ran into the same problem with earlier patches. After getting rid of my swap partition (on the SD card) the patches worked fine.
[Milestone XT720 Android Development] queens49:
I've got a linux-swap partition on my SD card, and I have no issues. I've applied both patches, the stock221v13-bugifx-2 and the one for the conservative scaling in SetCPU. Everything works great.
[Milestone XT720 Android Development] Mioze7Ae:
I also couldn't reproduce the problem by creating a swap partition on the SD.

Dexter's 1.3 doesn't check for ext filesystem errors before mounting, but bugfix-1 and bugfix-2 do. Perhaps the issue is the filesystem check is detecting un(auto)repairable problems in the ext partition. I don't know how to create this sort of damage for testing so I'm not sure what happens in that case.

When you repartition to remove swap, it's likely that you also reformat--which gives you an error-free ext partition.

So... one way to test this would be to just reformat the ext partition. Or put the card in a linux box and fsck it.
[Milestone XT720 Android Development] bu2askoor:
my wife's phone was sluggish and bottom buttons were very slow. This patch fixed it in addition to the milestone cpu speed fix.

THANK YOU SO SO SO MUCH. :) also BIG THANKS goes to the original rom maker.
[Milestone XT720 Android Development] :
Nice update :) It's really fast :)

But unfortanetly, every app that needs the on-screen keyboard force closes :(

Did a fresh install from Dexter 1.3 and this bug-fix as update and wiped everything.

Bug or some other problem?
[Milestone XT720 Android Development] :
Never mind. After rebooting the phone, the problem is gone.
[Milestone XT720 Android Development] hellmonger:
Yeah i think Mioze7Ae is right prolly unreparible errors in the Ext partition il will try again but so far.

THIS PHONE IS FLYING thanx Mo you did so really good work + im able to fastboot the custom Kernel no problemo!

Still testing no issues so far

Well there is that phone crash after tasking 10 picktures nbut that has notthing to do with this patch i think it/s a 2.2.1 thing

might want to try this though 1 0 android and 0 1 xt... in lib/elg.conf i find its faster