Related
AndroidCantral wrote yesterday an article about fine tuning android multi-tasking
about fine tuning android multi-tasking. They show a small tutorial to free some space using a MinFreeManager application.
Application discussion:
http://forum.xda-developers.com/showthread.php?p=5529436
I have tried this application in the aggressive preset setting and Galaxy was much faster and snippier with opening applications. It's running now for a day without any problems so far..
You do need root the Galaxy first!
Have anybody else tried this app?
I have been using this task killer.
Thanks for the info. Learn something new.
Will try later after I have completed charging my phone.
that program minfreemanager didnt work on my phone after reboot the file in /sys/module/lowmemorykiller/parameters/minfree was not updating.. got the program referenced in the thread called autokiller and that is updating the file on reboot correctly.
getting rid of the lag
Memory management helps (I use autokiller) but what really solved this annoyance
was moving the applications' data to the NAND (see http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/)
Its like a completely different device
One caveat is that the size of the NANDs is limited so you better know what you're doing and make sure that your /data/data dir is small enough to fit there
I am nervous about doing this since android is not designed that way. until paul or someone comes up for a fix so you dont have to reinstall os if you go over the limit.
lgkahn said:
that program minfreemanager didnt work on my phone after reboot the file in /sys/module/lowmemorykiller/parameters/minfree was not updating.. got the program referenced in the thread called autokiller and that is updating the file on reboot correctly.
Click to expand...
Click to collapse
AutoKiller is ideed better. I still new to Android, still have to lern a lot
arnonrgo said:
Memory management helps (I use autokiller) but what really solved this annoyance
was moving the applications' data to the NAND (see http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/)
Its like a completely different device
One caveat is that the size of the NANDs is limited so you better know what you're doing and make sure that your /data/data dir is small enough to fit there
Click to expand...
Click to collapse
What kind of data is that? Does this include mails, contacts, appointments, games save data?
can someone please explain to me what journaling means? what it does? and if needed how do i get it? im new to this and want to start flashing roms but im trying to collect as much info before i actually do something. thanks
halowizard said:
can someone please explain to me what journaling means? what it does? and if needed how do i get it? im new to this and want to start flashing roms but im trying to collect as much info before i actually do something. thanks
Click to expand...
Click to collapse
I am going to be nice and answer your question after 2 words 1)search and 2)Google
Journalling is when the phone writes all things back to the phone twice so that it verifies everything. Then if you drop your phone and the battery pops out and it corrupts your data, there is a non-corrupted version still on your phone and the operating system checks and uses that one. Journalling due to writing twice is supposed to slow down your performance some (I never noticed). Choice is yours. It takes me like a half hour to recover from multiple crashes from a dropped phone.
Oh and it depends on the ROM whether it is on, off or a choice is given. If you install a ROM with no journalling, it mostly can be turned on by doing a nand backup and restore. If you are stock, you are on.
Thanks that helped
Sent from my PC36100 using Tapatalk
kennyglass123 said:
I am going to be nice and answer your question after 2 words 1)search and 2)Google
Journalling is when the phone writes all things back to the phone twice so that it verifies everything. Then if you drop your phone and the battery pops out and it corrupts your data, there is a non-corrupted version still on your phone and the operating system checks and uses that one. Journalling due to writing twice is supposed to slow down your performance some (I never noticed). Choice is yours. It takes me like a half hour to recover from multiple crashes from a dropped phone.
Click to expand...
Click to collapse
this the q & a part of the forum right?.
halowizard said:
this the q & a part of the forum right?.
Click to expand...
Click to collapse
Indeed it is. But before you ask a Q, double check that there isn't already an A. Save yourself the trouble of waiting, and save the rest of us from repeatedly writing the same thing. 99.9% of the time you're asking something that's been answered many times and can be easily found.
This one, for example, Kenny himself answered a couple weeks ago HERE.
And someone else asked months ago HERE.
And all I had to do was Google "Journaling XDA".
Journaling file systems use various techniques to keep a log of changes to files as they are written, and in the event of data corruption these logs can be used to repair the damage. This makes it much more unlikely that a crash will corrupt data. Here's a link to Wikipedia's entry:
http://en.wikipedia.org/wiki/Journaling_file_system
Anyway, using a non-journaling file system on your phone can result in corrupt files if a program FC's or the phone is shut down by pulling the battery. The benefits are faster file writes and better battery life because there is less writing to disk with each file change.
Thank you...in my head I compare it to computer write verifies, but it is more like the backup copy of the master boot record...got it..thanks. Was just trying to keep it simple.
kennyglass123 said:
Thank you...in my head I compare it to computer write verifies, but it is more like the backup copy of the master boot record...got it..thanks. Was just trying to keep it simple.
Click to expand...
Click to collapse
Gota luv the high horse riding trolls in here. Guy comes in and asked a question and trolls tell him to google it. Lol. Trolololol
so do the stock roms use journaling? are the custom roms more prone to crashing and losing data?
SINNN said:
Gota luv the high horse riding trolls in here. Guy comes in and asked a question and trolls tell him to google it. Lol. Trolololol
Click to expand...
Click to collapse
Thanks for trolling. Feel free to criticize when you make a useful post this year.
You may notice that, despite asking he search ahead of time in the future, his question was answered twice, regardless.
Are you too high up on your horse to accept an answer given to someone else in an existing thread? Must you have your own, brand new, completely identical answer in a brand new, redundant and forum-flooding thread?
Thanks for playing!
murso4 said:
so do the stock roms use journaling? are the custom roms more prone to crashing and losing data?
Click to expand...
Click to collapse
Journaling is a stock feature, yes. Custom roms are not more prone to crashing, generally. It is apps that may crash, due to their own nature, or incompatibility with a rom, which will result in data loss in the absence of journaling.
SINNN said:
Gota luv the high horse riding trolls in here. Guy comes in and asked a question and trolls tell him to google it. Lol. Trolololol
Click to expand...
Click to collapse
If a question has been asked (and probably just freaking yesterday!) then yeah! SEARCH is your friend. Would you like to look for a thread you were posting in and see 20 questions on "what is an apk"? If people are able to find XDA they are able to use google. Not a high horse, but obviously can't teach basic knowledge here. And for the record, I answered the question as well...but as you were trolling too fast I guess you missed that.
halowizard said:
can someone please explain to me what journaling means? what it does?
Click to expand...
Click to collapse
It's already been posted, but journaling is a feature of journaling file systems.
Most operations performed by a file system consist of multiple fundamental "steps". Should the file system stop running (i.e., a bug causes the kernel to panic or the computer/phone loses power) before all the steps for a given operation completes, then the file system is left in an inconsistent state.
Consider the example of moving a file from one directory to another. In simplified terms, this consists of two steps: (i) copying the file to the destination directory, and (ii) deleting the file from the source directory. Now, suppose the phone crashes after copying the file (step i) but before deleting it (step ii). When the phone boots again, the file exists in both directories when it should only exist in one. That's the basic idea of file system inconsistency. Although that particular scenario is relatively harmless, there's more complicated situations in which a phone crash can result in deleted-but-not-freed data, half-written files, and all sorts of other inconsistencies.
Now, journaling file systems are different in that they maintain a transaction log (a journal) where the fundamental steps for operations are recorded before they are carried out. In the event of a crash, the file system replays the jounal on reboot and performs any outstanding operation that has been committed to the journal.
In the above example, a journaling file system would: (i) record in the journal that it is copying & deleting the file, (ii) commit the journal, then actually (iii) copy the file to the destionation directory, and (iv) delete the file from the source. In the event of a crash, the operation either has been committed to the journal, in which case it's verified that the subsequent steps were performed and are performed if not, or the operation hasn't been committed yet, in which case no changes have been made. This guarantees that, following a journal replay, the file system is always in a consistent state.
Now, it's true that maintaining a journal carries some performance penalty as operations have to be written to the file system twice. Modern file systems, like ext4, get around this by delaying the non-journal write operations until a later time when the file system is (relatively) idle. So the actual decrease in performance is minimal if any. This also means that running these file systems with journaling disabled is potentailly more dangerous than non-journaled file systems as operations may remain outstanding for far longer than they would otherwise, increasing their succeptability to loss in the event of a crash.
It's also worth noting that the primary purpose of file system journaling is to gurarantee file system consistency, not avoid data corruption. Most journaled file system only journal metadata, that is, only the operations carried out on a file are journaled, not the actual data content. This is why a battery pull is always a bad idea and should be avoided unless absolutely necessary.
Still, in the worst case, a journaling file system after reboot will only suffer data corruption in the files most recently modified before a crash, whereas a non-journaled file system may suffer corruption of the underlying file system structure, possibly rendering many non-recently modified files inaccessible. In other words, with a journaled file system, in the worst case you might have to "Clear data" on one or two apps to recover, whereas with a non-journaled one the entire file system might be hosed.
RandomKing said:
It is apps that may crash, due to their own nature, or incompatibility with a rom, which will result in data loss in the absence of journaling.
Click to expand...
Click to collapse
Just to note: journaling is irrelevant with regard to data corruption on an application-level crash. Any outstanding changes made by the application to the file system are still performed by the kernel, even after the application itself crashes.
Journaling protects in situation where the kernel itself is unable to complete any outstanding changes due to crash (kernel panic) or powerloss.
do you have to reenable journaling every time you flash a rom?
RandomKing said:
Journaling is a stock feature, yes. Custom roms are not more prone to crashing, generally. It is apps that may crash, due to their own nature, or incompatibility with a rom, which will result in data loss in the absence of journaling.
Click to expand...
Click to collapse
I would say, before rooting and after, before installing a custom rom, I got crashes all the time. About 70% were twLauncher (which is pathetic, this phone has convinced me I will never own another from Samsung - and I have a long history with Samsung phones) about 25% were from Maps (again, just sad) with the remaining 5% being other apps. twLauncher crashed more than any piece of software I have ever used on any electronics device in my life, something was wrong with it on this phone,i am quite sure it wasn't normal.
Either way, i am happy to say it wasn't the hardware (knock on wood). Not a single thing has crashed since installing Frankenstein Android. I am supremely happy with it.
In regards to three re-posting: I can't wait to hit 10 posts so that I can post in the thread about it Frankenstein. I have been lurking at xda a long time, finally decided I needed to post to share my experiences and gratitude to the developer. But I am having a hard time hitting the requisite 10 posts. Trying to post things that haven't been said before here is really hard if you aren't a developer yourself.
Sent from my Epic 4g with Frankenstein Froyo
murso74 said:
do you have to reenable journaling every time you flash a rom?
Click to expand...
Click to collapse
Mostly, if the ROM disables it. In other words every time you flash a no journal ROM it disables it.
The new Bonsai ROM will let you choose and then it will stick whether you reflash it or not.
Thanks for being all smart asses. You just ruined my birthday jerks
Sent from my SPH-D700 using XDA App
halowizard said:
Thanks for being all smart asses. You just ruined my birthday jerks
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You're welcome...just remember to hit the thanks button.
Dude, seriously, we DID answer the question and also tried to point you in the right direction to avoid getting responses in the future like what happened here. I try to answer the question and remind the person to use the search function or even look at all the similiar threads that pop up before posting. And if we really ruined your birthday, you take life and these threads MUCH too seriously.
But Happy Birthday anyway.
Lol. Im jk dude. It was really my bday. I thought this thread was getting to heated so I made a joke.
Sent from my SPH-D700 using XDA App
halowizard said:
Lol. Im jk dude. It was really my bday. I thought this thread was getting to heated so I made a joke.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
lol, So I can leave in my happy birthday wish.
I saw this on the frontpage of xda http://www.xda-developers.com/android/boot-up-to-4-different-roms-with-dualromx2/
was wondering if this works or can be ported to the g2?
Wow, that's frickin awesome. I want that and I really hope it might be possible for us... I don't see why it would be too hard (maybe I'm mising something big though). Although... couldn't files on the SD used for one ROM mess up another ROM when used?
Would be very nice!
Sent from my HTC Vision using XDA Premium App
What would that be useful for though? Testing loads of different roms?
Sent from my HTC Vision using XDA App
KalC87 said:
What would that be useful for though? Testing loads of different roms?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Some people like variety! And switching it up without setting it up everytime!
xsteven77x said:
Some people like variety! And switching it up without setting it up everytime!
Click to expand...
Click to collapse
I don't understand why you would dual boot though as its not really the same as dual booting a PC for example as you don't boot a mobile device as its turned on most of the time?
Don't get me wrong I'm sure it appeals to some, personally though I don't think it takes that much time switching between ROMs anyway!
Sent from my HTC Vision using XDA App
My main build is PyroMod 2.3.4 and I have a backup of CM 7.1.0 on an 8GB card. Is something like that what you have in mind?
I just think it would be nice to switch it up whenever you want without having to wipe. I like variety
dual boot, ok, i remember doing that. why not just make a nandroid backup of your current likable rom, with all your personal data and then flash the new one, setting up personal data again.
nandroid both of them, and switch in 10 minutes, if that ?
personally, dual boot went away when i quit using gentoo.
ahhh, gentoo.
This is genius. The implementation is absolutely perfect and completely logical. However there is one major flaw of our phones compared to the droid incredible: Storage space. DI has 8Gigs of rom (6.5G available), G2 has 2 Gigs(1.3Gigs available). The team has not yet figured out how to remap all of the storage space. We MIGHT be able to fit 2 roms but we would have practically no space on internal for apps, forcing us to use A2SD, which, IMO increasesSD card wear, causes lag when launching large apps, and wastes battery.
If we WERE able to fully repartition the 2 Gigs of our NAND, it would work out much simpler: 200 megs to each /system partition, and 800 megs to each /data partition (with /cache symlinked to /data). However, the team has not yet figured out how to do that, so it wouldn't really be worth it just yet.
You can also use Rom manager for making backups and switch
Sent from my HTC Vision using XDA Premium App
jojo_16 said:
You can also use Rom manager for making backups and switch
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
You could do that.... But thats not a true dual boot. It takes 10+ minutes each way. What these people figured out is how not put multiple roms on the internal memory and boot between them instantly at will.
mejorguille said:
This is genius. The implementation is absolutely perfect and completely logical. However there is one major flaw of our phones compared to the droid incredible: Storage space. DI has 8Gigs of rom (6.5G available), G2 has 2 Gigs(1.3Gigs available). The team has not yet figured out how to remap all of the storage space. We MIGHT be able to fit 2 roms but we would have practically no space on internal for apps, forcing us to use A2SD, which, IMO increasesSD card wear, causes lag when launching large apps, and wastes battery.
If we WERE able to fully repartition the 2 Gigs of our NAND, it would work out much simpler: 200 megs to each /system partition, and 800 megs to each /data partition (with /cache symlinked to /data). However, the team has not yet figured out how to do that, so it wouldn't really be worth it just yet.
Click to expand...
Click to collapse
Hell 2 would be great, I run mexdroid as my main, but there are others I would like to run and be able to switch back and forth easily would be nice.
Wishful thinking I guess. If I had any experience and the means to compile that type of programming I'd be doing it, but, alas I'm not very well versed in that kind of intense development.
mejorguille said:
You could do that.... But thats not a true dual boot. It takes 10+ minutes each way. What these people figured out is how not put multiple roms on the internal memory and boot between them instantly at will.
Click to expand...
Click to collapse
agree, at this point it's just like restoring selected image rather than loading a preset.
that would be so sweeeet
Hoping this can become a reality!
Sent from my HTC Vision using XDA Premium App
I would like to see also dual boot and not nandroid backups...Actually i would love a dual boot between windows phone 8 and android but this is almost impossible right now,there was a device i think htc hd2 that actually has a dual boot...For now i enjoy the goodies of android on my lg g2 and from windows phone in my lumia 1020...I cant decide so i bought both...
Ok, so my wife has been battling the 'out of space' issue on her droid inc for some time.
Finally, GB comes out for her inc... I think "hey, this was a huge problem, and never really solved, im SURE GB fixed this up"
Flashed the other day, and today she says it showed up again.
What the heck? Come on HTC!!
ALL of her apps are on the SD card, she has it rooted, and uses the stock email app, as well as handcent for txting.
How do i fix this?!?!
Hm, how many apps does she have installed?
Sent from my DROID3 using xda premium
Well before This happened she had about 30-35? now its 20 or so other than the stockers
How large is the sd card?
It may b custom rom time
Sent from my DROID3 using xda premium
Is it me, or have there been a lot of these kinds of problems cropping up? I'm kinda curious what the reason and solution is since I'm probably gonna put my dInc back on Sense sometime.
its the stock 2gb card, but both the card, and her 'sd card' report over 500mb free...
IIWY I'd check directories for usage files and phone dumps that can fill up phone space (700mb) fast — you can't delete the directories (causes some FCs; annoying), but you can delete all the files, then make the directories read-only so they stay empty:
/data/tombstone
/data/system/dropbox
/data/system/usagestats
And def. install/use an app cache cleaner if you haven't already.
There's a program here (search for SD maid) that helps clean up, too. I haven't tried it but I've read about it; looks great.
Clear out or back up and delete old mms messages.
Sent from my ADR6300 using XDA Premium App
Trebuchette said:
IIWY I'd check directories for usage files and phone dumps that can fill up phone space (700mb) fast — you can't delete the directories (causes some FCs; annoying), but you can delete all the files, then make the directories read-only so they stay empty:
/data/tombstone
/data/system/dropbox
/data/system/usagestats
And def. install/use an app cache cleaner if you haven't already.
There's a program here (search for SD maid) that helps clean up, too. I haven't tried it but I've read about it; looks great.
Click to expand...
Click to collapse
Did this. There was a bunch of stuff, alas, icon is still there were working on cache clearing now, but weve done that before with different apps.
kodakeos said:
Did this. There was a bunch of stuff, alas, icon is still there were working on cache clearing now, but weve done that before with different apps.
Click to expand...
Click to collapse
If she's rooted, download NotEnoughSpace. It will give you direct access to the 150 megabyte \data\data partition. Every application and any contacts synced to the Incredible are dumped in there. If less than 10% is free, you'll get a low memory message, and performance will degrade.
NotEnoughSpace lets you relocate stuff out of \data\data and frees up space in that directory.
I also discourage folks from downloading all their Facebook contacts. Completely unnecessary, and all dumped into \data\data anyway.
BTW, with NotEnoughSpace, I recommend moving what can be moved until you get up to about 20% free (i.e. 30megabytes) only to emmc or a NES partition, *not* the cache. You might have to clear the cache and then the info will be missing from the apps.
When I backup my app data using titanium, does it delete any old data and save the newer data over it or does it create separate files for the backups each time?
3bs11 said:
When I backup my app data using titanium, does it delete any old data and save the newer data over it or does it create separate files for the backups each time?
Click to expand...
Click to collapse
Believe if you have the PRO version, you can have multiple backups for a single app. If you have the free, it overwrites.
martonikaj said:
Believe if you have the PRO version, you can have multiple backups for a single app. If you have the free, it overwrites.
Click to expand...
Click to collapse
I have the Pro. Is it set to overwrite by default?
3bs11 said:
I have the Pro. Is it set to overwrite by default?
Click to expand...
Click to collapse
I'm sure it is. That'd be a big memory waster if it wasn't. Very few people would actually want this feature.
Don't have my phone beside me; but in Preferences you can set the maximum number of b/u's. Once you reach whichever number you set it to, it will begin to overwrite. As mentioned above, it does mean more space taken up, but there's an option (defaulted to "on" I believe) that backs up the apk once only, so you're not using even more space by continually backing up huge apps, but are backing up their associated data.
^a little long winded, when I'm tired I suck at explaining **** efficiently or even using periods instead of an explosion of commas.
martonikaj said:
I'm sure it is. That'd be a big memory waster if it wasn't. Very few people would actually want this feature.
Click to expand...
Click to collapse
mudferret said:
Don't have my phone beside me; but in Preferences you can set the maximum number of b/u's. Once you reach whichever number you set it to, it will begin to overwrite. As mentioned above, it does mean more space taken up, but there's an option (defaulted to "on" I believe) that backs up the apk once only, so you're not using even more space by continually backing up huge apps, but are backing up their associated data.
^a little long winded, when I'm tired I suck at explaining **** efficiently or even using periods instead of an explosion of commas.
Click to expand...
Click to collapse
Yeah I actually only want one backup for each app. Thanks for the feedback guys