[Q] dalvik cache (in laymans terms) - Xperia Play Q&A, Help & Troubleshooting

hi! i'm not a complete noob or anything. but i do like to understand the things i know.
please dont start insulting me and shout "just google it" at me, as i have and it all gets my head in a spin. and to make matters worse, i have a medical condition that hinders my understanding of "big words". lol.
but quite simply, in an easy to understand way, could someone please explain to me what the dalvik cache is, what it does, why it's important, the need (or lack of need) to clean it, and the difference's between it and other cache types?
any info would be appreciated. i would love to help support dev's more, and understand what phones do (os wise) and how to tweak them. and this is just one of the questions that bugs me a fair bit, for some reason
thanks in advance

You have 5 apps and yet for some reason you have more used memory than you should
Sent from my R800i using XDA App

Got this from another fourm here
Dalvik cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. Sounds confusing. It's similar to the prefetch files in Windows.
Click to expand...
Click to collapse
or even this from here
When Android starts up, the DalvikVM looks thru all of your applications (.apk files) and frameworks, and builds a tree of dependencies. It uses this dependency tree to optimize the bytecode for every application and stores it in the Dalvik cache. The applications are then run using the optimized bytecode.
Click to expand...
Click to collapse
or read about it fully on wiki http://en.wikipedia.org/wiki/Dalvik_virtual_machine

Mozza2k11 said:
Got this from another fourm here
or even this from here
or read about it fully on wiki http://en.wikipedia.org/wiki/Dalvik_virtual_machine
Click to expand...
Click to collapse
Yep the 2nd quote from mozza sums up the dalvik cache. The dalvik vm builds a tree of dependencies on boot, this is used to run applications with optimal bytecode

so it's basically a storage space that tells the phone the best way of running an app through the OS you have installed? take it it takes the hardware into account too? i'd like to understand the prefetch thing, but that confuses me too

Related

[Q] Removing stock apps to save space?

I noticed some threads for different phones with regard to this but didn't see an answer for the EVO so I'll ask here.
I would like more space on my phone as I'm tired of seeing the little low space hard drive icon. I've already moved all the apps to SD via app2SD. I was thinking of installing the latest rooted stock Sprint ROM (3.70.651.1) and then deleting the stock apps that I do not use but I have read elsewhere that this will, in fact, not free up any more space for applications. Is this true?
If so, can I get a recommendation for the "most stock" ROM that's stripped of the Sprint added apps. If it has some ubiquitous and useful add-ons than that is OK
Thanks!
There's a couple of ROMs in the Dev section that are optimized for speed, and I'd recommend those. A lot of them have them already removed, but you can remove the ones that aren't
Thanks for the response... I apologize if I didn't state my question correctly. I understand that I can remove the apps that I want if I'm rooted, what I'm not sure about is if that space will be made available for other applications when I do remove the programs (in ROM) that I do not want.
Hope that clarifies the question.
Wayno-san said:
Thanks for the response... I apologize if I didn't state my question correctly. I understand that I can remove the apps that I want if I'm rooted, what I'm not sure about is if that space will be made available for other applications when I do remove the programs (in ROM) that I do not want.
Hope that clarifies the question.
Click to expand...
Click to collapse
A small amount of space will be freed. If you move Dalvik Cache to the Cache partition this will free up a lot more space than removing apps.
leenypost said:
A small amount of space will be freed. If you move Dalvik Cache to the Cache partition this will free up a lot more space than removing apps.
Click to expand...
Click to collapse
That sounds intriguing... can you point me to a "how-to" link or someplace where I can learn more about how to do this?
Wayno-san said:
That sounds intriguing... can you point me to a "how-to" link or someplace where I can learn more about how to do this?
Click to expand...
Click to collapse
Search on XDA for "move dalvik to cache". There should be a zip file you can download that will do it for you.
Thanks again for the info. I did as you suggested and now have 266 MB left where before I had less than 50. Using ap2sd with Azrael ROM and do far have not run into any issues. Keeping my fingers crossed.
Note, however, that most of the stock apps are in your system partition. The free space you care about for installing apps is in the data partition. So removing them doesn't free up the space you care about. Even on ROMs that have removed them, I'm not sure if they actually do (or can) resize the partitions to give you the space where it counts (/data).
You can, however, move apps to the system partition if you want. I've done this with some of the updates to stock apps -- GMail, Qik, and Flash, for example. That's freed some space up.
bkrodgers said:
You can, however, move apps to the system partition if you want. I've done this with some of the updates to stock apps -- GMail, Qik, and Flash, for example. That's freed some space up.
Click to expand...
Click to collapse
This sounds like it is worthwhile to learn how to do. Is there a thread or program that you could point me to for some guidance on how to do this?
I've also read that ap2sd can move programs that have not yet been modified to enable the regular android 2.2 "move to SD" function to work; but after flashing that app and using it to move the Dalvik cache I do see any obvious front-end for it.
Wayno-san said:
This sounds like it is worthwhile to learn how to do. Is there a thread or program that you could point me to for some guidance on how to do this?
I've also read that ap2sd can move programs that have not yet been modified to enable the regular android 2.2 "move to SD" function to work; but after flashing that app and using it to move the Dalvik cache I do see any obvious front-end for it.
Click to expand...
Click to collapse
Basically you just move the APK file from /data/app to /system/app using ES File Explorer (need to enable root mode in prefs) or Root Explorer. Or you can do it with adb or even terminal emulator on the phone if you prefer. I think Titanium Backup Pro (the paid version) has an ability to do this too. You also want to look in /system/app and see if there's an older version under some other name that should be deleted. Titanium Pro may handle this part for you automatically as well. I haven't bought it yet, so I'm not sure (though I plan to, the free version is great and the paid version adds some nice things). I think you can still get updates from the market after you've done this, but the update will go to /data/app. You'd need to move it and delete the prior version again after receiving such an update.
I haven't enabled a2sd yet. My understanding is that it's not so much something you need a front end for. Once you set it up, that's just where your apps go. You don't move your apps to the sd card manually. I could be wrong. I used whatever form of a2sd was available for XDAndroid on my old Touch, but that's been a little while and the DarkStar A2SD that people use might be a little different than that method. I haven't done it at all yet on the evo.
Thank you sir, that's very good info and I'll give it a shot.

Kernel With Separate Cache Partition

Hello everyone,
I've compiled a kernel which separates the NAND memory into 3 partitions (well more then that but anyway). These partitions are system, data and cache like a native Android phone (which also has recovery but we don't need that). Previously cache was linked to a directory on the data partition which was constantly becoming corrupt causing errors on start-up. Often clearing dalvik-cache would allow Android to boot but data was lost. There's nothing to say that this will solve the problem but i'm giving it a go so thought I would post it up for you to try also.
The cache partition is 20mb which means the data partition is only 90mb or so. If you like a million apps on your phone either put some on your SD card or don't use it
I haven't completely incorporated this partition into the initrd which means that currently it will only mount if data is also on NAND but this can be changed easily enough, but for testing purposes I want everything on the NAND chip anyway.
Downloads from market on all versions of Android, unless the init.rc directory is changed in Gingerbread, all go to the cache partition and are deleted on restart. What this means is that you can't download and install an app larger then 20mb (which isn't recommended anyway with the small amount of data space available). This is a drawback but for those that use data on SD it should be possible in the future to utilise more of the NAND memory for cache so you can install whatever you want. I don't know of many apps larger then 20mb anyway though.
I have included a modified version of ATools in the zip. The standard version will overwrite the partition values and the kernel won't work properly so if you need to modify the kernel use the version included. It is also important that you DO NOT change the system or data partition sizes in ATools as this hasn't been modified to account for the cache partition so will mess it all up.
I have also included an androidupdate.tar modules update for the kernel in case your wifi doesn't work after flashing the kernel.
I think that's it for now, let me know how it goes!
EDIT::
One last thing, you will need to wipe your DATA partition to use this kernel because some of your data may be positioned where the cache partition is now, so if you load this kernel and android is heavily corrupt you know what you have to do!
To check the kernel is working correctly you can type "df -h" into a terminal and it should show all of the current partitions including one called cache on mtdblock4.
Should now work with polaris, kaiser and vogue. There is a VOGUEIMG.NBH included for those who have trouble with ATools. It is completely untested on Vogue so sorry if it doesn't work.
EDIT
I have re-uploaded a modified kernel because there was some issues with data with the last one. If you have already applied the last one flash the new one and apply the module update again
testing will leave feedback
Ok, using your Scoot CyanogenMod 6.1.2 (RLS6) [16.03.2011], overclock via atools+roguetools to 529, gpu oc, battery units tweaked to suit my battery.
No SIM card yet, don't have one to put there, sync with google to get contacts.
Installed GoLauncher. Enabled JIT and Keep Launcher in memory.
Once in a while, Android is killing all apps, launcher included... strange...
Nevermind that, it was Cyanogen and the LongPress BackKey. LongPress on our Kaisers during lag can become short press
First couple of days of heavy use I've had in ages with no corruption. First day of my new job today so it's been on Google Navigation for 3 hours and used extensively during the day. Had to do a hard reset at one point and everything was fine. had a few soft reset's too. Don't get me wrong, i'd be surprised if this is a fix, but it's been a while since I've used my Kaiser this much and not had to wipe my data partition!
Update: CM is a bit slow, trying:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
And everyting seems good. I've pushed it a little, several normal reboots.
Had to reflash system (didn't reflash data). No errors, FC's, whatevar. Everything works, yet didn't try to make/receive calls. Its 1am here...
Now this particular version, has a god damn bug that is get the best of me. The Power Button and the red button won't make the phone go to standby. If i long press, i get the normal reboot/power off/airplane etc menu, on both keys. But single press is ignore... Any idea ?
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Using this kernel with Valentine 1.02. GPU overclocked and CPU @ 520mhz. Super fast and for the first time... no data corruption! Verry happy so far!
daedric said:
scooter1556 , i have a question. It is not the purpose of the thread or kernel, but how difficult would it be to activate scalling of the cpu ?
Right now, the two 3 biggest issues with Android on the Kaiser are, IMHO, Data corruption, Battery life, performance.
Please share your thoughts
Click to expand...
Click to collapse
Well in theory not too hard, there is a feature built into the linux kernel called cpufreq which is currently disabled in our kernel because our cpu and chipset code doesn't support it but krazy-killa has been working on getting it working in his kernels with a little success as far as i'm aware but i'm not that sure. I haven't personally looked into it but if I get some spare time I definitely will. I've started a new job now which i'm sure will keep me quite busy but I still intend to so some work on the Kaiser when I get time
Best of luck on your new job! I wish i had enough knowledge to continue the kernel development, but i'm quite a ignorant
Still, thank you, till now it's one of the best kernels i've used.
Hi Scoot!
I love your kernel. No data corruption so far (two days). did a few stylus resets and stuff.. Magical =D. Now IMO we only need better sleeping and autofocus to call kaiser a fully android device! Please Keep up the awesome job, scoot! thanx, danke, sposeeba, bedankt, aciu, dzenkuja!
Nice job scooter, I've been using Scoot CyanogenMod 7.0.2 RLS2 [28/04/11] @ 500MHz, and it seems fine so far.
I tried Fat Free Froyo before CyanogenMod, which also worked great for the few hours it was running. I'm not sure which one to stick with though.
Keep up the good work. I wish I could help with the development, but I have yet to learn programming (been ten years now ).
This kernel looks pretty stable, but just a few quick questions:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Thanx for your great work, finally it seems to be fully usable for me and if you and Krazy-Killa would be able to work together to manage the power consumption, then it would be amazing, because I am going to get new phone (running some new extensive business and I can not afford to be not reachable when something happends on Kaiser) and give this lovely piece of HW to my son... And I really do not want him to have a WM machine But Android needs to be stable for him to use Well... he will get it for his 10th birthday at 6.9. so we still have some time to tweak it a bit more
if this works then it would be magical, your CM builds were so fast and awesome and if there's no data loss then... <3
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
PoXFreak said:
Made 2 mistakes when building kernel (selected tilt instead of normal and forgot to OC to 480MHz), and running kingshui's 12/15/2010 build 2.2.1. seems ROCK solid and fast! I applaud your use of ramzswap for the extra 20mb, bravo!
I'm just hoping I can go back and rebuild the kernel with the correct settings without messing up the system/data/cache partitioning.
Click to expand...
Click to collapse
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
a.s.j said:
1) What filesystem is used for the cache? If YAFFS, could it get corrupted? If Yes, what would happend then?
2) Is it really needed to have 20MB for the cache? ATM it seems to be used only by a like 1-2MB on the cache partition, would not it be enough to have for example 10MB for the cache leaving more space for apps?
3) What is the difference using apps in the system and data partitions? If I would run off the space on the data partition, can I put some apps in the system apps folder to save the space without wandering about how it works?
Click to expand...
Click to collapse
1) The cache partition is still using Yaffs2 because it is the easiest filesystem to configure at the minute, but the idea of making it a separate partition like on a native android device is that it can be changed to another filesystem in the initrd relatively easily. If it gets corrupted it will do what it used to I guess, but I haven't had any corruption as of yet so it's difficult to say. Hopefully if the cache partition get's corrupted it shouldn't affect data so you should just be able to wipe and format dalvik-cache in the install menu.
2) I made it 20mb because most android devices have 30mb or bigger and this is mainly because market app downloaded get downloaded here before being installed, so if you installed google maps for instance it would use up 6mb, plus the standard 1-2mb normally being used, but if you only had a 10mb cache for instance, you would only be able to install apps less then 8mb which is a little limiting really. I don't really care much about installing lots of apps in data or on the phone at all for that matter so having 95mb for data is more then enough for me.
3) You can put apps in the system partition in /system/app. The system partition is read only so all data for the app still goes to the data partition. You can still save a little data partition space though if you need it. Most installs of android are 80-95mb which should leave you 5mb or so to play with. Some all language builds pretty much use up all of the partition though so you need to look and see what space you have to play with before putting apps on the system partition. If you overload it you will probably end up corrupting it and having to reinstall. But to answer your last question, the system partition works in the same way as the data partition apart fro the fact that it is read-only and data is read/write.
I've modified my Kernel to use the NAND mtdblock3 (/data for everyone else) as the cache partition, since my NAND is pretty much shot to begin with, and have system and data on SD Card. So far it's made downloading Market Apps twice as fast, loading webpages pretty fast, and basically anything else that the cache is used for.
scooter1556 said:
They aren't mistakes, those are the settings I need for my Kaiser. I included a modified version of ATools for you all to modify the kernel for your devices as I stated in the first post
Click to expand...
Click to collapse
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
PoXFreak said:
Scoot:
I understand that the settings built into the .nbh are for your device. What I was meaning was I needed to modify the CPU clock up to 480MHz, and for some odd reason my device swaps the "@" and "!" buttons if I set it to "tilt", among other buttons being set wrong.
Also, I am used to having the left and right softkeys set as "vol up" and "vol down" respectively. Is this something I need to make an androidupdate for, or do I have to write a new NBH?
Click to expand...
Click to collapse
Can you not do all of this using the ATools i provided in the attachment in the first post? You should be able to load the nbh into ATools and then set the CPU speed, change the keyboard type and remap the buttons and then save it before flashing. Just don't change the partition sizes as this will mess up the cache partition I added until I make it more permanent.

[Q] Dalvik Cache and the Dalvik JIT compiler... What gives?

Okay, so i've done about three hours of digging, as i've yet to come up with a decent solution for my problem...
/data/dalvik-cache/ takes up about 80 mb of space. Its my understanding that the Dalvik cache contains the "enhancements and tweaks" that the Dalvik VM can use when running applications to make their response smoother. This directory is populated upon reboot, and will continue to be populated upon every reboot until you brick the phone, or it runs out of enhancements to make to the installed applications.
While looking for a way to reduce the size of this folder, I realized that if its a JIT compiler, why have the folder of enhancements? That makes no sense, because that folder would only be needed if the JIT compiler was disabled... Unless of course that the Dalvik VM is the JIT compiler, in which case this thread is useless.
Anyway, my question is, if the Dalvik VM and the JIT compiler are two different things, is there a way to prevent the Dalvik VM from running so you can use the JIT compiler?
PS: If someone could explain how this is all related, that would help very much, because everything i've read so far, either says very little about what it is, or it says everything that no one wants to know unless you're building a ROM and you need to tweak it accordingly. And even then it doesn't say a whole lot about what it is and what it does...
In case it matters, Its a GT-S5660M running Cyanogenmod 7.2.0 KANG built by Phiezx and Gang.
You got half the stuff wrong.
That /data/dalvik-cache is place where JIT compiler actually stores code it compiled to native from Java machine bytecode so it won't recompile the same code next time.
If you would somehow manage to turn off caching it would lower your phone performance, perhaps quite badly.
Lol, so my thread is essentially useless...
Although, if the Dalvik VM can make 80 MB of improvements to code already written, why not save that to the apps instead of using a separate folder?
Think about two things:
1) what to do with stuff you put into apps folder when apps change? say, you update them
2) what happens to your phone if you wipe dalvik-cache? and what if you wipe apps?
I mean, dalvik-cache stuff is to speed up your phone, but it would still work without cache. But it won't work without apps, so it's just logical to put them to different place.
BTW what bugs you that they place it separately? In terms of free disk space it doesn't matter - they're on same disk partition (unless you use extra partition on SD card).
Well, actually most of them are on the /System partition, instead of the /Data partition becasue i moved them around. I guess my point is, if you have xxMB of space used by the apps, and yyMB of space used by enhancements (where both xx and yy are within 15 MB of each other) why not just write the apps with the enhancements already coded into the apps? Then you wouldn't need to replace the code in the apps with the code from the enhancements, because that code would already be enhanced.
You're still not getting JIT stuff quite well.
Java is machine-independent bytecode (processor-independent if it's more clear). So one app can run on wide variety of machines without recompiling it.
What JIT does it compiles Java bytecode to your processor binary code. You cannot ship processor binary code with your application because this binary code differs from CPU to CPU. Well, actually you can ship it (just the way most desktop software does), but it would run on only one processor - the one you compiled it for. That would be really bad for software intended to run on bunch of different hardware.
Oh... Right... I KNEW THAT! .... sort of....
Okay, on to my next question. Is there any way of swapping out the java code for the binary code? Or would one need the source code to compile a binary version?

*SOLVED*[Market crashing constantly]-The app Market(process com.android.vending)

I just installed cyanogen mod 7.2 stable(It's a clean install and i have wiped every thing) following that installed the latest gapps package(gapps-gb-20110828-signed).
The market would not even load and crash constantly.
I have tried these tips:
1.Cleared data and cache (settings-> applications-> market -> Then clearing cache)
2.Wiped Dalvik cache
3.Fixed permissions.
4.Changed "language"
5.Re-installed gapps package.
All this was to no avail.
Downloaded "jelly bean" market and installed it.
Now the market would load ok but it crashes when i try to download some application.It sucks.
Any suggestion ?
Try Increase your MTD Partition if you have any... It should fix it... If not, delete your account from the settings (Accounts) and log on while opening PlayStore. Hope it helps.
Have you flashed the right Gapps? Some of the latest ones are for ICS Users and i have found they dont work.
Just google "Gapps" and then find the one without ICS
Hope this helps
MacGyver Jack said:
Have you flashed the right Gapps? Some of the latest ones are for ICS Users and i have found they dont work.
Just google "Gapps" and then find the one without ICS
Hope this helps
Click to expand...
Click to collapse
Not working....yes,I am flashing the right gapps zip.
http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
I have also verified the MD5 checksum.
olu.danNY said:
Try Increase your MTD Partition if you have any... It should fix it... If not, delete your account from the settings (Accounts) and log on while opening PlayStore. Hope it helps.
Click to expand...
Click to collapse
Deleting the account and factory reset is not working....even installing the CM 7.2 again and again is not working.
What does it have to do with MTD partition ?I have got sufficient internal memoery as i told you that it's a clean install and I don't have any app installed on my device except custom CM apps.
What about going to Setting > Manage applications > Market > Force close
I know you may have tried it and seems silly but i had a problem updating my apps and i did this and everything seems to work. What about a reboot?
Edit: I found this temporary workaround so see if this helps!
Here is what I did:
1- go to app manager from settings,
2- uninstall the latest version of google play store
3- clear data and cache of google play store
4- install version Google Play Store v3.5.19
5- when you open the market, google will still prompt you to update to the latest version (dont continue, leave it as it is)
6- if you want to update/install the apps do it thru the browser in your phone/computer (it will straight away update in your phone)
optimusodd said:
Deleting the account and factory reset is not working....even installing the CM 7.2 again and again is not working.
What does it have to do with MTD partition ?I have got sufficient internal memoery as i told you that it's a clean install and I don't have any app installed on my device except custom CM apps.
Click to expand...
Click to collapse
If you have Custom MTD partition, the issue may be, you have a low space reserved for System (Where GAPPS are installed) and more for Data.
Try using 175, 15... It is sufficent enough to run smoothly.
Cheers.
olu.danNY said:
If you have Custom MTD partition, the issue may be, you have a low space reserved for System (Where GAPPS are installed) and more for Data.
Try using 175, 15... It is sufficent enough to run smoothly.
Cheers.
Click to expand...
Click to collapse
Ah hell,why the hell didn't I ever think of this ?
Thanks for the life saving tip ,still not sure though if it was market version related or the system partition related.
Increased the partitons to [mtd 175 15].Market took a while,got updated to version 3.7.13 and it's working now.Really appreciate your help.
BTW,How did you figure out that [mtd 175 15] will work on "CM 7.2 Stable"?Just wondering can’t we take some more space from “system”.I have had [mtd 140 5] working well with "CM Nightly”.
Not sure how much we can take from system to flash CM 7.2 Stable but I guess we can still reduce "cache" to 5MB.
http://forum.xda-developers.com/showthread.php?t=1233340
What do you think ?
optimusodd said:
Ah hell,why the hell didn't I ever think of this ?
Thanks for the life saving tip ,still not sure though if it was market version related or the system partition related.
Increased the partitons to [mtd 175 15].Market took a while,got updated to version 3.7.13 and it's working now.Really appreciate your help.
BTW,How did you figure out that [mtd 175 15] will work on "CM 7.2 Stable"?Just wondering can’t we take some more space from “system”.I have had [mtd 140 5] working well with "CM Nightly”.
Not sure how much we can take from system to flash CM 7.2 Stable but I guess we can still reduce "cache" to 5MB.
http://forum.xda-developers.com/showthread.php?t=1233340
What do you think ?
Click to expand...
Click to collapse
I use mtd 140 20. Reducing the cache to 10 caused the force closing of market for me.
saadislam said:
I use mtd 140 20. Reducing the cache to 10 caused the force closing of market for me.
Click to expand...
Click to collapse
Are you sure you are running "CM 7.2 Stable" on HTC Buzz(Wildfire).
I tried [mtd 140 5] and it was causing "The application Market (process com.android.vending) has stopped unexpectedly. (FORCE CLOSE)".
optimusodd said:
Are you sure you are running "CM 7.2 Stable" on HTC Buzz(Wildfire).
I tried [mtd 140 5] and it was causing "The application Market (process com.android.vending) has stopped unexpectedly. (FORCE CLOSE)".
Click to expand...
Click to collapse
Try [mtd 140 20] . Like I said before reducing cache gave me force close. This configuration works fine for me. I was using cm7.2 stable since its release but now I am using lewa with the same partitions.
Sent from my HTC Wildfire using XDA
Don't ever, EVER underestimate olu.danNY's advice!
And search a lil' before posting... I've had the same problem not so long ago:
http://forum.xda-developers.com/showthread.php?t=1689239
I found out the partition size because I also wanted more space for Data as I don't like installing apps on SD (It can easily get corrupted as you use the SD with your PC during File Transfer, etc and or malfunction as some SD cards aren't that strong and I don't trust any!). That partition made it run.
Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need (My style). Anyway, I run Erwin P's ICS on Wildy now while having a backup of my CM7 incase I need to use the Camera/Video app again... LOL (I haven't tried using the dual booting thing... Always speculating, say I am lazy... Will try that out someday soon).
Anyways... Glad you have your phone working now.
Cheers.
olu.danNY said:
I found out the partition size because I also wanted more space for Data as I don't like installing apps on SD (It can easily get corrupted as you use the SD with your PC during File Transfer, etc and or malfunction as some SD cards aren't that strong and I don't trust any!). That partition made it run.
Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need (My style). Anyway, I run Erwin P's ICS on Wildy now while having a backup of my CM7 incase I need to use the Camera/Video app again... LOL (I haven't tried using the dual booting thing... Always speculating, say I am lazy... Will try that out someday soon).
Anyways... Glad you have your phone working now.
Cheers.
Click to expand...
Click to collapse
I kind of agree with most of your post,I only ever use ext for sense roms.
You say " Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need" I now what you mean but this doesn't increase your partition size,removing files etc from system only frees up space in the partition not increase it. Custom mtd is the only method I know to increase system partition. Regards slym.
MokeeOS
slymobi said:
I kind of agree with most of your post,I only ever use ext for sense roms.
You say " Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need" I now what you mean but this doesn't increase your partition size,removing files etc from system only frees up space in the partition not increase it. Custom mtd is the only method I know to increase system partition. Regards slym.
MokeeOS
Click to expand...
Click to collapse
Sorry... I guess that ain't clear enough... What I meant is this... Remove some stuffs from the ROM and Increase your Custom MTD partition... For example, if 100, 10 makes it run smoothly without edit, after edit, 90, 10 might run it good giving you extra 10MB for data... Hope I am clear here.
Cheers.
Sorry for double posting... Connection ish...
---------- Post added at 10:39 AM ---------- Previous post was at 10:27 AM ----------
slymobi said:
I kind of agree with most of your post,I only ever use ext for sense roms.
You say " Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need" I now what you mean but this doesn't increase your partition size,removing files etc from system only frees up space in the partition not increase it. Custom mtd is the only method I know to increase system partition. Regards slym.
MokeeOS
Click to expand...
Click to collapse
Sorry... I guess that ain't clear enough... What I meant is this... Remove some stuffs from the ROM and Increase your Custom MTD partition... For example, if 100, 10 makes it run smoothly without edit, after edit, 90, 10 might run it good giving you extra 10MB for data... Hope I am clear here.
Cheers.
HipHopBlond said:
Don't ever, EVER underestimate olu.danNY's advice!
And search a lil' before posting... I've had the same problem not so long ago:
http://forum.xda-developers.com/showthread.php?t=1689239
Click to expand...
Click to collapse
TBH I had done enough research to fix the issue.I did what one usually would have considered good research else it shouldn't have taken more than 5 endless days and nights
Even on CM forums,Android forums and several blogs.Don't know why couldn't find your post.
Anyway,"olu.danNY's" advice helped me else i was going to ditch CM7 for some other ROM .In my opinoin there should be a thread where users can update their working MTD partitions regarding their ROMs.
Right now I am running CM 7.2 Stable with [mtd 140 15] and some other users are running it even with [mtd 130 15]. i.e cache partiton was the root of the trouble.
olu.danNY said:
I found out the partition size because I also wanted more space for Data as I don't like installing apps on SD (It can easily get corrupted as you use the SD with your PC during File Transfer, etc and or malfunction as some SD cards aren't that strong and I don't trust any!). That partition made it run.
Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need (My style). Anyway, I run Erwin P's ICS on Wildy now while having a backup of my CM7 incase I need to use the Camera/Video app again... LOL (I haven't tried using the dual booting thing... Always speculating, say I am lazy... Will try that out someday soon).
Anyways... Glad you have your phone working now.
Cheers.
Click to expand...
Click to collapse
I also prefer removing pre-installed apps using TB but that doesn't really help you that much.
Custom MTD partition does the real rescue and you can also use "S2E" to gain more space by moving apps to Ext partition e.g games,maps.Just make sure you don't move app data to Ext.
SOLVED
P.S. Don't attempt to shrink the cache partition "too much".
Keep it(Cache) ≥ 15
optimusodd said:
SOLVED
P.S. Don't attempt to shrink the cache partition "too much".
Keep it(Cache) ≥ 15
Click to expand...
Click to collapse
YMMV - especially with CM7. It has been mentioned a few times over the forum that CM7 has a bind script which makes your whole /data partition used as cache - as long as it's activated (default) and not corrupted there shouldn't be any problems with the play store. No idea regarding other situations but I know of people running a 5MB cache partition on CM7...
eventcom said:
YMMV - especially with CM7. It has been mentioned a few times over the forum that CM7 has a bind script which makes your whole /data partition used as cache - as long as it's activated (default) and not corrupted there shouldn't be any problems with the play store. No idea regarding other situations but I know of people running a 5MB cache partition on CM7...
Click to expand...
Click to collapse
Yep,I know CM7 has some sort of script that automatically moves cache to data partition if it overflows(larger than the cache size).
I have had [mtd 140 5] working well with "CM Nightly”.
No idea why it is causing trouble with CM7.2-Stable. Maybe it's lacking that script which makes it sufficent enough to run smoothly if cahce partition is <15.

[Tip] Going 'Pristine' : What, Why, How

People keep asking me what "Pristine" means, and I'm tired of having to re-re-retype everything every time, so I think I'll just gather everything about "Going Pristine" in this thread
What does "Going Pristine" means
Going 'Pristine' means: Installing a ROM with no leftover from the previous ROM
Why should I "Go Pristine"?
Short answer: To prevent 95% of the problems experienced by others when installing a Custom ROM
Long answer:
When you install an App (.apk), the data saved by the App -- even the .apk itself! -- might be optimized/customized based on your previous ROM. This means that if you change your ROM, the data might cause problems due to the differences between your previous ROM and your latest ROM.
This is especially a problem if you 'change generations' (e.g., upgrading from GB to ICS or ICS to JB/JB+).
I *always* do Pristine ROM installations, and am glad to say that I managed to avoid about 95% of the problems experienced by other users of the ROM I used.
Additional Info: There's a hidden folder called .android_secure in the root directory of your SD Card. This folder is not visible when the card is mounted in your phone. It might contain settings that depends on what ROM you're using.
Are there Drawbacks of "Going Pristine"?
Unfortunately, there's no such thing as a free lunch. Here's a list of some potential drawbacks of Going Pristine. See if you can live with them; if you can't, then you shouldn't go pristine.
You will lose your savegames.
And thus, avid gamers will likely go insane due to having to repeat all the levels
However, please read the 2nd post of this thread for some interesting thoughts.
.
You will have to re-download all apps.
Which will be *very* time-consuming unless you have a fast HSDPA connection, or able to access a fast & free Wifi hotspot, or both.
Also, please read the 2nd post of this thread for some interesting thoughts.
.
You have to set some (relatively) significant time to do the process.
Trust me, copying 10 GB worth of stuff from/to the SD Card takes a loooong time, especially if there are a huge number of small files like porn pics cute kitten & puppies pics.
How do I "Go Pristine"?
Make sure that you have ClockWorkMod installed
.
Make a backup of important data, such as SMS Log, Call Log, Contacts (if you don't sync to Google), etc.
No need to perform backup of apps, especially System apps!
.
Create a Nandroid backup of your current system, I suggest in .tar format instead of dup format.
This will be necessary if you need to go back to your previous ROM.
.
Turn off your phone, eject the SD Card
.
Backup (copy) the whole contents of the SD Card to a PC (Windows, Mac, Linux, no matter)
-- or --
Prepare a new SD Card
.
(Optional, but recommended, especially if you want to use Link2SD later on) Repartition your SD Card, even if it's previously partitioned.
Make 2 primary partitions; the 1st one as FAT32, the 2nd one as ext2
(You *don't* want ext3/4 on a flash memory. Trust me)
.
Format your SD Card accordingly. (I.e., 1st partition as FAT32, 2nd partition (if you made one) as ext2
.
Copy the following to the root directory of your SD Card:
Your ROM installer updatezip
(If needed/specified by the ROM) GApps updatezip
The /clockworkmod directory from the previous SD Card contents (you did backup your SD Card, didn't you?)
.
Insert your (partitioned, formatted, and copied-to) SD Card into your phone
.
Boot into Recovery
.
Wipe/format the following (find the proper entry in the CWM menu structure):
/data
/system
/cache
Dalvik Cache -- please note that this is *different* from the /cache of the previous line!
Internal SD
Battery Stats
Leave the External SD alone!
.
Install your new ROM, following exactly the instructions by the ROM-cooker/dev
.
Now, this is VERY IMPORTANT: DO NOT EVER RESTORE ANY APP FROM YOUR PREVIOUS TITANIUM BACKUP SET!!!
ALWAYS DO FRESH INSTALLS FROM THE PLAY STORE!
You are allowed to restore some data, though: SMS Log, Call Log, and Contacts Book. That's it. Nothing else
However, please read the 2nd post of this thread for some interesting thoughts.
.
I have been installing my ROMs with "Pristine" way. Yes, reinstalling everything *is* tedious, but as a benefit, the new ROM runs smoothly, and a lot of problems that others (who did not go the "Pristine" way) never happened on me.
=====
There you have it, a clear and complete description of "Going Pristine", complete with the steps and explanations.
Feel free to link to this thread, and as usual, if you find this thread helpful, leave a Thanks and/or rate this thread 5 stars.
Thoughts and Considerations on Restoring Apps
After doing *lots* of Pristine installs, and some deep spelunking within the folders and settings of various apps...
... and based on valuable inputs from XDA friends ...
... I've come to the conclusion that:
Perhaps 90% of apps are safe to be reinstalled from Titanium Backup.
A sizable number of apps are also safe to have their data restored by copying the relevant data directory in /data.
The question is: How to make sure that the app you're trying to restore is part of the 90%?
My terse answer: Unless you know *exactly* what the app is doing (e.g., by perusing its source code), you can't really be sure.
You can always experiment, though; just remember to do a Nandroid Backup prior to restoring an app.
What I can give you, are several guidelines:
Games that are not too 3D-oriented are most likely safe; they are not likely to install additional libraries to mitigate whatever shortcoming the W has
Games that heavily rely on 3D ... unknown. Some of them are known to delve really deep into the Android library files, and even install their own custom libraries depending on your ROM/kernel capability
Productivity apps, e.g., Office Suites or To-Do Lists or PDF Viewer or ... many others of their ilk, are most likely safe to be restored. They are never known to install their own libraries, and/or have settings dependent on the ROM/kernel
Utilities... now we're getting into unknown territory... some of them are safe (the ones that don't mess up with the innards of Android); some of them are dangerous. I recommend re-downloading from Play Store
Be wary of apps that, when they were first installed, requested to add "additional files", either via Play Store (you can see in the Notification Tray, "Additional Files") or on first run (usually they will call it "Downloading assets"); these apps might be downloading binaries that depends greatly on what the system state is at download time. Let's call them the unknowns.
That's it. So, the warning that "You'll lose your savegames" is not really absolute; if you're lucky, you can restore from a TiBU-made backup.
Always remember to do Nandroid Backup.
========================================
Games known to be restore-able:
Funky Smugglers
Minecraft
Subway Surfer
Utilities known to be restore-able:
ClockSync
Solid Explorer
-- Sent from Opera Mobile for Windows --
I think this topic must be stickies
.... coz this topic very important
Sory if my english is noot good
In some way thats true, i do believe though that much people never have a look at the stickies. Would be a shame if this topic wouldnt be seen
Sent from Galaxy W with CM10 (thanks to Arco!)
actually i dont think extensive rom flasher will follow this guide but i do agree with pep about going pristine
Sent from my GT-I8150
hadidjapri said:
actually i dont think extensive rom flasher will follow this guide but i do agree with pep about going pristine
Sent from my GT-I8150
Click to expand...
Click to collapse
Hehe... too much things to do for them, likely...
But if you're like me, flashing only to fix bugs, and already settled on a (relatively) stable ROM, going Pristine should be a habit
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
hadidjapri said:
actually i dont think extensive rom flasher will follow this guide but i do agree with pep about going pristine
Sent from my GT-I8150
Click to expand...
Click to collapse
Well doing this just seems alot more effort if you have alot of apps and games and why alot of people won't do this. I mean I have 70 apps/games installed so having to manually install all of them again is just to much effort.
Broken Puzzles said:
Well doing this just seems alot more effort if you have alot of apps and games and why alot of people won't do this. I mean I have 70 apps/games installed so having to manually install all of them again is just to much effort.
Click to expand...
Click to collapse
Well, I also have a lot of apps and games, but for me the added stability is totally worth it.
Especially since there's a café providing fast and free wifi near my office
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Broken Puzzles said:
Well doing this just seems alot more effort if you have alot of apps and games and why alot of people won't do this. I mean I have 70 apps/games installed so having to manually install all of them again is just to much effort.
Click to expand...
Click to collapse
If you didn't want to install again all your apps one by one just backup your apps with titanium backup pro and then restore ONLY the apps after doing pristine route.
For me the pro version of titanium backup will automate the installation so just leave your phone after restoring from titanium backup cause it will automagically install all your backed up apps without you having to select it one by one.
And don't restore the apps data because it will ruins your halfway through pristine route.
Sent from my GT-I8150 using Xparent ICS Tapatalk 2
reddvilzz said:
If you didn't want to install again all your apps one by one just backup your apps with titanium backup pro and then restore ONLY the apps after doing pristine route.
For me the pro version of titanium backup will automate the installation so just leave your phone after restoring from titanium backup cause it will automagically install all your backed up apps without you having to select it one by one.
And don't restore the apps data because it will ruins your halfway through pristine route.
Sent from my GT-I8150 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Well... *most* .apk's *should* be safe...
But, considering that Play Store *can* detect what's your OS and *does* offer apps based on your OS, there's a possibility that the .apk has been optimized for your (previous) OS's generation (e.g., GB or ICS or JB). If you stick with the same generation, in general there shouldn't be any problems. But if you change generations, there *might* be problems.
I decided that it's better to be careful than sorry, so I don't restore any apps, even without attached data
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
pepoluan said:
Well, I also have a lot of apps and games, but for me the added stability is totally worth it.
Especially since there's a café providing fast and free wifi near my office
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Click to expand...
Click to collapse
Thats weird since the stability is the same after factory reset your phone 5 times before flashing anything new and restore from Titanium backup. Also I don't know if you see the flaw in your method especially if you play alot of games and thats if you only reinstall the apk and not the data you have to start all over again and let me tell you that pisses off any gamer when it happens. Not just on a phone but on anything but just saying.
reddvilzz said:
If you didn't want to install again all your apps one by one just backup your apps with titanium backup pro and then restore ONLY the apps after doing pristine route.
For me the pro version of titanium backup will automate the installation so just leave your phone after restoring from titanium backup cause it will automagically install all your backed up apps without you having to select it one by one.
And don't restore the apps data because it will ruins your halfway through pristine route.
Sent from my GT-I8150 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I do use titanium backup to restore all my apps but I was just pointing out that while this method is good and has a possibility of making the ROM more stable it does provide more problems like I said above if you are an avid gamer and losing all your save data and having to start again will drive you insane.
Broken Puzzles said:
Thats weird since the stability is the same after factory reset your phone 5 times before flashing anything new and restore from Titanium backup.
Click to expand...
Click to collapse
Factory reset 5 times?? What's the point? Since a single factory reset already means a reformatting of your partition...
Your flash memory is not like an overly-dirty carpet that needs to be shampooed and vacuumed several times before all the grime comes out of it. One format -- done. Nothing left.
I'm just pointing out the fact: Many problems that many experienced when they flashed CM9 -- did not happen to me. Ever. And I *strongly* suspect that leftover bits (settings, incompatible code, etc.) is the culprit.
Broken Puzzles said:
Also I don't know if you see the flaw in your method especially if you play alot of games and thats if you only reinstall the apk and not the data you have to start all over again and let me tell you that pisses off any gamer when it happens. Not just on a phone but on anything but just saying.
Click to expand...
Click to collapse
That is a flaw that I'm perfectly capable of living with.
As you note, in the thread's title, I'm not claiming of something along the lines of: "Want your CM9 to be stable? This is the way!!1!one!!eleven". I use a simple title of "Going Pristine: What, Why, How".
The onus lies on the viewer of this thread, whether they can live with the consequences or not.\
Broken Puzzles said:
I do use titanium backup to restore all my apps but I was just pointing out that while this method is good and has a possibility of making the ROM more stable it does provide more problems like I said above if you are an avid gamer and losing all your save data and having to start again will drive you insane.
Click to expand...
Click to collapse
For me -- and other non-gamers, or non-avid gamers -- losing save data is not a 'problem'. An 'annoyance', for sure, but not 'problem'.
Again, I am not forcing my methods on you or other W users here. I'm just stating the fact: 1) What is meant by 'going pristine', 2) Why 'going pristine' is good, and 3) How to 'go pristine'.
That said...
I understand your concerns, and I'll edit my first posting to warn avid gamers that they will go insane :cyclops:
pepoluan said:
Factory reset 5 times?? What's the point? Since a single factory reset already means a reformatting of your partition...
Your flash memory is not like an overly-dirty carpet that needs to be shampooed and vacuumed several times before all the grime comes out of it. One format -- done. Nothing left.
I'm just pointing out the fact: Many problems that many experienced when they flashed CM9 -- did not happen to me. Ever. And I *strongly* suspect that leftover bits (settings, incompatible code, etc.) is the culprit.
Click to expand...
Click to collapse
Well I had problems in the past with only 1 factory reset as some left over stuff from the old rom was carried over to the new one so I do that just in case and it cleared up the problems I was having.
That is a flaw that I'm perfectly capable of living with.
As you note, in the thread's title, I'm not claiming of something along the lines of: "Want your CM9 to be stable? This is the way!!1!one!!eleven". I use a simple title of "Going Pristine: What, Why, How".
The onus lies on the viewer of this thread, whether they can live with the consequences or not.\
Click to expand...
Click to collapse
Not saying your not fine with that flaw but just pointing out that while your method is best suited to someone not using their phone for its entertainment features but more serious stuff.
For me -- and other non-gamers, or non-avid gamers -- losing save data is not a 'problem'. An 'annoyance', for sure, but not 'problem'.
Again, I am not forcing my methods on you or other W users here. I'm just stating the fact: 1) What is meant by 'going pristine', 2) Why 'going pristine' is good, and 3) How to 'go pristine'.
That said...
I understand your concerns, and I'll edit my first posting to warn avid gamers that they will go insane :cyclops:
Click to expand...
Click to collapse
Well obviously its not a problem if your not a gamer otherwise you would freak when losing your save data, not just on a phone but on any gaming device.
Not saying your forcing others to do this but again just pointing out that unless you are more of a casual user of your phone and don't really bother with gaming then this method is great otherwise like me you are going to just restore all your apps with data anyway.
Broken Puzzles said:
Well I had problems in the past with only 1 factory reset as some left over stuff from the old rom was carried over to the new one so I do that just in case and it cleared up the problems I was having.
Click to expand...
Click to collapse
Ah, you mean doing a factory reset after flashing the ROM?
I see. That might help... but since the non-resetted portion of your phone (SD cards) still contain leftover bits from the previous ROM, there is a possibility of additional problems. Which will lead to yet-another-factory-reset, ad nauseam (or at least until it's stable enough).
I personally prefer having it started out stable, then adding bits and pieces until it becomes unstable... easier to troubleshoot which part is the culprit
Broken Puzzles said:
Well obviously its not a problem if your not a gamer otherwise you would freak when losing your save data, not just on a phone but on any gaming device.
Not saying your forcing others to do this but again just pointing out that unless you are more of a casual user of your phone and don't really bother with gaming then this method is great otherwise like me you are going to just restore all your apps with data anyway.
Click to expand...
Click to collapse
Point taken. :good:
I've edited the OP to more clearly indicate some (potential) drawbacks in a (hopefully) humorous way
Is link2sd still work in our phone? I read somewhere that link2sd never work with cmw 6. Even myself see a wierd note when I boot into recovery after flashing link2sd.
Another question, please give me a reason why I use ext2 compare to ext3/4? I search the net but I only found speed for ext2 and data loss prevention and stability in ext3/4. I wonder why if there's any benefit specifically in our phone.
Thank you...
Sent from my GT-I8150 using Tapatalk 2
vhick said:
Is link2sd still work in our phone? I read somewhere that link2sd never work with cmw 6. Even myself see a wierd note when I boot into recovery after flashing link2sd.
Click to expand...
Click to collapse
Yes, it still works.
The 'weird' note that you saw must have been CWM's warning that the ROM *seems* to want to install a Recovery that will overwrite CWM.
Just ignore it. Choose 'No' for the answer (that is, just press the Home button to execute the first answer, which should be 'No' IIRC).
CWM shows the warning because the method used by Link2SD to initialize the 2nd partition hooks directly into a known method of restoring Recovery.
vhick said:
Another question, please give me a reason why I use ext2 compare to ext3/4? I search the net but I only found speed for ext2 and data loss prevention and stability in ext3/4. I wonder why if there's any benefit specifically in our phone.
Click to expand...
Click to collapse
Okay, the explanation is technical, please bear with me.
ext3/4 introduce what is known as 'journaling' to prevent inconsistent metadata on unclean interrupted writes. The 'journal' is a region of storage set aside to write a 'log' of metadata changes, circularly. Due to the circular log, the region will be intensively used. No problem on magnetic disks, *big* problem on flash memory due to two factors:
1. Limited number of write cycles. Every update to the circular log shortens the life of the Flash memory extensively.
2. The necessity of wiping a whole block of memory (1 or 4 MB, depends on manufacturer) even if ext3/4 need to overwrite just 1 KB of data. This requires *extremely* expensive read-modify-write cycles. Compounded with the single core we have on the W, this means expensive context switching as writes get stalled and the OS hands over timeslice to other waiting threads.
ext2 has no journal, so it's much more flash-friendly, but if writes (in this case, creation/deletion of files) got interrupted uncleanly, you might lose some data or worse.
However, since Link2SD only put apk files in the 2nd partition, and these apk files are never edited (except on upgrades), the drawback of ext2 is not really applicable (IOW, ext2 is *extremely* suitable for nearly-read-only storage access pattern).
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Hi Pepoluan, hope you don't mind, but I've linked to this thread in my "Rooting, ClockworkMod and Custom ROMs" (sticky) thread....think it will help a lot of people
Sent from my CM10 powered Wonder with Tapatalk 2......it's all good......
keithross39 said:
Hi Pepoluan, hope you don't mind, but I've linked to this thread in my "Rooting, ClockworkMod and Custom ROMs" (sticky) thread....think it will help a lot of people
Sent from my CM10 powered Wonder with Tapatalk 2......it's all good......
Click to expand...
Click to collapse
No problem. In fact, the honor is mine
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
pepoluan said:
Yes, it still works.
The 'weird' note that you saw must have been CWM's warning that the ROM *seems* to want to install a Recovery that will overwrite CWM.
Just ignore it. Choose 'No' for the answer (that is, just press the Home button to execute the first answer, which should be 'No' IIRC).
CWM shows the warning because the method used by Link2SD to initialize the 2nd partition hooks directly into a known method of restoring Recovery.
Okay, the explanation is technical, please bear with me.
ext3/4 introduce what is known as 'journaling' to prevent inconsistent metadata on unclean interrupted writes. The 'journal' is a region of storage set aside to write a 'log' of metadata changes, circularly. Due to the circular log, the region will be intensively used. No problem on magnetic disks, *big* problem on flash memory due to two factors:
1. Limited number of write cycles. Every update to the circular log shortens the life of the Flash memory extensively.
2. The necessity of wiping a whole block of memory (1 or 4 MB, depends on manufacturer) even if ext3/4 need to overwrite just 1 KB of data. This requires *extremely* expensive read-modify-write cycles. Compounded with the single core we have on the W, this means expensive context switching as writes get stalled and the OS hands over timeslice to other waiting threads.
ext2 has no journal, so it's much more flash-friendly, but if writes (in this case, creation/deletion of files) got interrupted uncleanly, you might lose some data or worse.
However, since Link2SD only put apk files in the 2nd partition, and these apk files are never edited (except on upgrades), the drawback of ext2 is not really applicable (IOW, ext2 is *extremely* suitable for nearly-read-only storage access pattern).
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
Click to expand...
Click to collapse
For long searching....at last I found the solution! Kudos!
Thank you so much, and its clearly now, specially using link2sd and understanding ext2/3/4 filesystem
sorry for the noob question but y should i have 2 partitions on my sdcard and wts the use of the second partition (ext2) and if i have a 32 GB sdcard wt will be the best partitioning for it (how much for the fat32 and for the ext2)

Categories

Resources