Related
[size=+2]This version is now deprecated in favor of the 2.0 APK version. Please see this link: http://forum.xda-developers.com/showthread.php?t=784691[/size]
This version is not recommended for use any longer.
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513
Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.
Oh, awesome. I managed to post this in the wrong forum. Doh!
Could a moderator please move this to Android Dev sub forum?
haha looks awesome dude but you are correct, wrong section im gonna try it now, will report in 5 mins!
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
abra-cadabra...
*POOF*
Done!
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
sirphunkee said:
abra-cadabra...
*POOF*
Done!
Click to expand...
Click to collapse
Thanks.
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
I'm running the manual ext2 fix with Q scores 2000+. I'll try 2.0 Util tonight and post feedback....
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
gonna test report in 5minutes
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
About what lag is this?
Sent from my HTC Desire using XDA App
Dominik06 said:
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Benchmarks are roughly the same as 1.0. You can expect about 100 points more on average though, at least on my phone.
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Zilch25 said:
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
Click to expand...
Click to collapse
Just as long as you point out that this fix isn't heavily tested yet!
RyanZA said:
Just as long as you point out that this fix isn't heavily tested yet!
Click to expand...
Click to collapse
Oh I know, I'm going to emphasize that heavily, lord knows I don't want to get stuck on tech support all night
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Thoughts? That's bad.
You should be seeing roughly 215mb free. Did you see any errors in the log at all?
Everything is working fine for me. First reboot after lagfix had some problems with downloading apps from market, but after a second reboot it got fixed.
"Biggest" problem now, is just the phone stating that my internal phone storage is too low, with an icon on notification bar that I cannot remove. Already deleted some .bak from /data folder, any more tips what I can delete to get rid from this message?
Regarding the fix. apps are indeed much more snappier, no lag on the system when installing apps from market, and overall if the phone would continue like this for the next 48 hours, lag fix form me is solved. I had some problems after some 24h, with some lag, even with the previous version of the lag fix.
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Looking through my old V1 remove script, I believe I was leaving behind the .bak files! Nastyyy... I'll update V2 to remove those if they're there on install. Will hopefully clear up any problems.
I think this better to be posted to Galaxy S I9000 Android Development.
So I posted it once more at here:
http://forum.xda-developers.com/showthread.php?p=7694817#post7694817
Board Admin, please feel free to delete this.
Hi all,
I took so many from here. It's time for me to contribute little to the community.
The lag issue of Galaxy S bother many ppl.
I tried many different method.
Yes the lag issue was improved and Quadrant score is higher.
But there are always some weird things happen... like sudden lag/black screen.
After I upgraded to firmwre I9000ZSJH1, the lag issue is improved a lot!
But still, there are rooms for improvement.
So I wrote a cmd which will help to generate a .sh file, which will move apps data stored under /data/data/ to the internal NAND memory (/dbdata/data) for faster access.
The Galaxy S built in 1xxMB of fast access NAND memory. It is a waste if we don't utilize them.
However, it is impossible to move all apps' data to the tiny NAND memory.
So here is a tool for you to customize what app's data you want to move.
Recommand to move the core Android apps and the apps that you use frequently.
Like Dialer, Contacts, Dolphin Browser, Facebook, Astro File Explorer......
Steps :
1. open [1.app.list.xls] and edit colume A and B.
colume A should be the data folder name of the apps you want to move.
colume B is the name of the apps (optional)
2. after you've done, simply "copy & paste" everything onto a notepad and save it as [2.apps.list.txt]
3. fireup the [3.Apps2NAND.cmd]
4. within few sec, a file [App2NAND.sh] will be created.
5. use Gscript to load and run the App2NAND.sh file. (the script requires root access. so make sure you have it!)
For experienced user :
Step 1 actually is just for user to manage the apps more clearly.
A user with little cmd knowledge may know the script only requires [2.app.list.txt] to work with.
You can skip Step 1 and directly go to Step 2 to edit the file.
The format should be { app data folder name + <tab> + app name }
Remarks :
Apps that moved to NAND may not be restore with Titanium Backup.
App link will be broken by doing so.
(I also include Linpack and Quadrant to the app list to cheat higher benchmark scores . You may remove it if you don't want to.)
Apps2NAND - fast data access - choose what to move! [added support for Froyo]
update 18 Nov 10:
Found some friends here still want to use this "old school" lagfix
1st of all, thanks to your support.
When I wrote this script, it was still the golden age of Eclair (2.1). So the script is definitely not prepared for Froyo (2.2).
However, just by changing few lines can make this script survives on Froyo. So here I updated a script for Froyo (apps2nand.Froyo.zip).
I haven't tested it since I am very satisfied with the [Spike Speedy Edition v3.0 OC], which comes with more advanced lagfix options (sztupy).
(I wrote something that even myself don't use now.... So it's really suprised and appreciated~)
But this script still has it merit ~~~~~~~~~ simple!
(and battery friendly, just a feeling~ no actually statistic~)
If you are interested in antique and brave enough, try it on Froyo. And let me know if any issues. I will try my best to fix.
===================================================
update 18 Aug 10:
Now included Installation and Uninstallation for this script.
Tried several times on my i9000 and it works.
Please read and follow the readme.txt inside the zip.
One tricky part for this script : it will failed when SU permission is not allowed in time during the script is running.
I have pause the script with 10 secs for you to allow the SU on i9000.
Make sure you allowed it.
If you failed to do so, no worry. it won't change anything.
Just simply re-run the script again.
===================================================
Hi all,
I took so many from here. It's time for me to contribute little to the community.
The lag issue of Galaxy S bother many ppl.
I tried many different method.
Yes the lag issue was improved and Quadrant score is higher.
But there are always some weird things happen... like sudden lag/black screen.
After I upgraded to firmwre I9000ZSJH1, the lag issue is improved a lot!
But still, there are rooms for improvement.
So I wrote a cmd which will help to generate a .sh file, which will move apps data stored under /data/data/ to the internal NAND memory (/dbdata/data) for faster access.
The Galaxy S built in 1xxMB of fast access NAND memory. It is a waste if we don't utilize them.
However, it is impossible to move all apps' data to the tiny NAND memory.
So here is a tool for you to customize what app's data you want to move.
Recommand to move the core Android apps and the apps that you use frequently.
Like Dialer, Contacts, Dolphin Browser, Facebook, Astro File Explorer......
For experienced user :
Step 1 actually is just for user to manage the apps more clearly.
A user with little cmd knowledge may know the script only requires [2.app.list.txt] to work with.
You can skip Step 1 and directly go to Step 2 to edit the file.
The format should be { app data folder name + <tab> + app name }
Remarks :
*** Apps that moved to NAND may not be restore with Titanium Backup. App link will be broken by doing so.
*** Please make a nandroid backup before apply this!
*** I am not responsible for any damage caused by this script.
(I also include Linpack and Quadrant to the app list to cheat higher benchmark scores . You may remove it if you don't want to.)
Is NAND where devices like HTC Desire and Nexus One store their Apps?
well this is almost what paul did some days after the phone got released...
lyno said:
Is NAND where devices like HTC Desire and Nexus One store their Apps?
Click to expand...
Click to collapse
Yes, which is why they needed APPS2SD in Froyo.
So....when are you posting the script?
If you want I'll create a program that spits out the .txt file rather than do it in excel, copy paste etc.
Jonas.M said:
well this is almost what paul did some days after the phone got released...
Click to expand...
Click to collapse
yes. that's what Paul did as I mentioned in my script.
But he simply push everything to NAND which oneday, you will find out of space.
Using my script, you can decide what to move, depending on the frequency of the apps usage.
lyno said:
So....when are you posting the script?
If you want I'll create a program that spits out the .txt file rather than do it in excel, copy paste etc.
Click to expand...
Click to collapse
the script is updated and posted.
the excel is just for user to maintain their app list easily.
my script only works with the txt file.
you may skip the excel part if you like.
and thanks for your offer, lyno.
Is it possible to make a script that automatically moves smaller apps to the nand?
I mean it's not worth moving large games, but anything under 2MB should be considered.
Maybe use some intellegent calculation, if all the apps under XMB use less than 50% of free space on nand, increase X until it is efficiently used up.
Also there is HEAPS of space to be freed in NAND, delete stock ringtones, and other.
seems great
hmm, would moving to nand make those specific apps run faster than they would be if they were previously running under ext2/3/4 partitions provided for by the various lagfixes out there?
What happens if an app in the list is not on the phone, does it just skip it?
sturmeh said:
Is it possible to make a script that automatically moves smaller apps to the nand?
I mean it's not worth moving large games, but anything under 2MB should be considered.
Maybe use some intellegent calculation, if all the apps under XMB use less than 50% of free space on nand, increase X until it is efficiently used up.
Also there is HEAPS of space to be freed in NAND, delete stock ringtones, and other.
Click to expand...
Click to collapse
MiG123 said:
hmm, would moving to nand make those specific apps run faster than they would be if they were previously running under ext2/3/4 partitions provided for by the various lagfixes out there?
Click to expand...
Click to collapse
sturmeh, that requires more complex scripting skills, which is out of my knowledge...
and I think instead of choosing the apps2NAND depending on size, I think the "Frequency" of using the apps may be more appropriate.
e.g. I use TouchPal IME a lot. So I move it to the NAND.
Now when I type, TouchPal act lightening!!!
MiG123, I haven't done a serious comparison. But as I remembered, Apps2NAND gives me more "smooth" feeling.
Actually, you shouldn't compare Apps2NAND to other Apps2SD or EXT.
Since Apps2NAND only offers you around 1xxMB of app storage space. Way too far from the others experts' methods.
I suggest using this is because I am using the latest 2.1 ROM, I9000TGYJH1 (http://www.multiupload.com/UTKSZPTKCG), which the lag problem seems improved a lot. But on top of it, I don't want to waste that 1xxMB of internal RAM, so I introduce this method.
To let user choose what core apps that should be put into NAND so
- space is not wasted.
- certain apps enjoy even faster response time.
lyno said:
What happens if an app in the list is not on the phone, does it just skip it?
Click to expand...
Click to collapse
yes.
the script will skip the apps that is not in the list.
MiG123 said:
hmm, would moving to nand make those specific apps run faster than they would be if they were previously running under ext2/3/4 partitions provided for by the various lagfixes out there?
Click to expand...
Click to collapse
Definitely, the hardware is multitudes faster.
Where's the file? Can't seem to find it on the first page
Anyhow. Do you symlink the old location to the new location, thus being able to keep the link intact? That should sort out any problems with backup solutions such as Titanium Backup.
How do you find the app's data folder name?
mekwall said:
Where's the file? Can't seem to find it on the first page
Anyhow. Do you symlink the old location to the new location, thus being able to keep the link intact? That should sort out any problems with backup solutions such as Titanium Backup.
Click to expand...
Click to collapse
lyno said:
How do you find the app's data folder name?
Click to expand...
Click to collapse
mekwall, sorry. removed by mistake.
have uploaded back again now.
yes. it uses symlink method (from Paul's concept) :
ln -s /dbdata/data/appsname /data/data/appsname
i dunno how's Titanium Backup works but it just failed to restore any apps that has used Apps2NAND...
that's why i provide the Uninstallation method to restore it back and then run Titanium Backup to backup all apps and data.
lyno, you may try the Astro File Explorer (market).
It has a function to backup the installed apps out to /sdcard.
The name of the backuped apps will be named exactly the same as it's data folder name.
e.g. Brut's Google Map -> brut.googlemaps.apk
this whoe procedure demands root-access, right?
yes. since it involves moving folders between /dbdata and /data.
Sent from my GT-I9000 using XDA App
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Bump thread...new version 2.7.5.3 Beta 02 is released.
Bump---new version available.
Most ROMs include most of the functionality you described.
What are the gains of getting this? If I read things a little, there is somekind of app whereby the user can control the parameters?
Some people believe this version makes the phone respond faster because rather than using a FAT32 implementation of Apps2SD, which (from my understanding) has to go through some form of encryption/decryption (could be wrong on that account), this version uses native Linux partitions to store the data. This also uses symbolic links (native to Linux) to redirect the files to the SD card.
Apparently, from what I have read as well, some programs leave traces of themselves in Internal storage even if they are moved to the SD card by Froyo (although I can't find any evidence of that on my phone), this would insure that the entire program is on the SD card.
On top of that, this version can move dalvik-cache to the SD card, which Froyo's implementation cannot do. That helps with freeing up more internal space.
The newer 2.7.5.3 also has a method of moving the program data (/data/data) to the SD card as well, freeing up even more memory. Froyo also can't do this.
While it is true that most roms offer similar functionality, most Apps2SD implementations are also designed for the rom they run. If you have a rom that does the same functionality as Darktremor, then you should stick with what you have. This is for people who need more functionality with their Apps2SD or people who use roms like CyanogenMod which doesn't have an Apps2SD implementation.
riemervdzee said:
Most ROMs include most of the functionality you described.
What are the gains of getting this? If I read things a little, there is somekind of app whereby the user can control the parameters?
Click to expand...
Click to collapse
tkirton said:
Some people believe this version makes the phone respond faster because rather than using a FAT32 implementation of Apps2SD....
{I edited out all of this stuff since the person you're replying to is an advanced kernel developer who knows all of this and was suggesting that all existing roms other than stock CM roms come with ext-based apps2sd which support dalvik2sd and so on, just like this does}...
...While it is true that most roms offer similar functionality, most Apps2SD implementations are also designed for the rom they run. If you have a rom that does the same functionality as Darktremor, then you should stick with what you have. This is for people who need more functionality with their Apps2SD or people who use roms like CyanogenMod which doesn't have an Apps2SD implementation.
Click to expand...
Click to collapse
So this is useful for CM roms - that is true. It's probably the main reason to use this since I too don't see anything that would really be better than the apps2sd built into the roms I've been using other than this taking more space.
Possibly this thread could be renamed with "for CM stock roms" or something so it's really clear to users of those roms that they could get these benefits easily.
My thought on this issue is this: I'm not going to attempt to convince you to try it. If you want to run it, great. If you don't, that's fine as well (some people feel Froyo Apps2SD is enough, and I respect that).
I always believe that, if you have something that works fine for you, don't change. If your Apps2SD implementation works for you, then stick with that.
dkelley said:
So this is useful for CM roms - that is true. It's probably the main reason to use this since I too don't see anything that would really be better than the apps2sd built into the roms I've been using other than this taking more space.
Possibly this thread could be renamed with "for CM stock roms" or something so it's really clear to users of those roms that they could get these benefits easily.
Click to expand...
Click to collapse
Do I need to turn on the Application moving thing in Cyanogen mod, or just DT just run in the background automatically?
I'm using CM7 by the way.
tkirton said:
My thought on this issue is this: I'm not going to attempt to convince you to try it. If you want to run it, great. If you don't, that's fine as well (some people feel Froyo Apps2SD is enough, and I respect that).
I always believe that, if you have something that works fine for you, don't change. If your Apps2SD implementation works for you, then stick with that.
Click to expand...
Click to collapse
interesting - you missed my point entirely LoL, but that is very fair what you said.
I was clarifying that this tool is really targetted at, and most useful for, CM users.
and from what I've been told this particular version beta3a is working perfectly with CM7 gingerbread.
takuhii said:
Do I need to turn on the Application moving thing in Cyanogen mod, or just DT just run in the background automatically?
I'm using CM7 by the way.
Click to expand...
Click to collapse
if you use this all you do is flash it and you're done. no more thinking about application control other than to move certain apps to "phone" memory if they FC after being installed and you find them defaulting to be in "sd card" memory (which often causes issues in some gingerbread installs).
Using this on CM7 with an ext4 partition, works very well. One thing I had to do manually is run 'a2sd cachesd', moving the dalvik to the sd card. Assuming the built in a2sd (ext) in other roms do this automatically, as my free internal space was much lower (with the same apps) until I did this step. Performance seemed the same either way, just the free storage number changed )
Quick question about the datasd command. Aside from saving space, would this (or could this) allow one to preserve apps in between wipes (i.e. different rom installs)? As a wipeaholic I'd love to just have my apps/data sitting on ext partition and have them show up automatically whenever I flash a new rom.
scrollo said:
Using this on CM7 with an ext4 partition, works very well. One thing I had to do manually is run 'a2sd cachesd', moving the dalvik to the sd card. Assuming the built in a2sd (ext) in other roms do this automatically, as my free internal space was much lower (with the same apps) until I did this step. Performance seemed the same either way, just the free storage number changed )
Quick question about the datasd command. Aside from saving space, would this (or could this) allow one to preserve apps in between wipes (i.e. different rom installs)? As a wipeaholic I'd love to just have my apps/data sitting on ext partition and have them show up automatically whenever I flash a new rom.
Click to expand...
Click to collapse
I am running this on CM7 too, I moved Dalvik-cache to the CACHE folder/partition. This ROM just blazes along now...
Application moving thing is Froyo Apps2SD. Darktremor does it automatically.
takuhii said:
Do I need to turn on the Application moving thing in Cyanogen mod, or just DT just run in the background automatically?
I'm using CM7 by the way.
Click to expand...
Click to collapse
I actually did get the point, but couldn't come up with an appropriate response. I don't know much about the HTC Hero GSM. My first Android phone was the HTC Hero CDMA, which I found out is a different beast altogether.
For the Hero CDMA, we have both CyanogenMod (AOSP) and SenseUI (HTC) roms. Darktremor is relevant to both types of rom types, so both AOSP and HTC rom users can use it. That's where I had troubles actually coming up with the appropriate response...I don't know if you guys have SenseUI and I'm not familiar with other roms you have.
Beta 04 should work better for CM users..
dkelley said:
interesting - you missed my point entirely LoL, but that is very fair what you said.
I was clarifying that this tool is really targetted at, and most useful for, CM users.
and from what I've been told this particular version beta3a is working perfectly with CM7 gingerbread.
Click to expand...
Click to collapse
Theoretically, it should preserve the data (though I don't think anyone, including myself, has done that yet). This should be useful if you were going between nightly builds (seeing that you are on CM7, I presume that's why you asked the question), but switching between two different roms may result in unpredictable operation.
scrollo said:
Using this on CM7 with an ext4 partition, works very well. One thing I had to do manually is run 'a2sd cachesd', moving the dalvik to the sd card. Assuming the built in a2sd (ext) in other roms do this automatically, as my free internal space was much lower (with the same apps) until I did this step. Performance seemed the same either way, just the free storage number changed )
Quick question about the datasd command. Aside from saving space, would this (or could this) allow one to preserve apps in between wipes (i.e. different rom installs)? As a wipeaholic I'd love to just have my apps/data sitting on ext partition and have them show up automatically whenever I flash a new rom.
Click to expand...
Click to collapse
tkirton said:
Application moving thing is Froyo Apps2SD. Darktremor does it automatically.
Click to expand...
Click to collapse
I think its time we refered to your A2SD as A2EXT, this is more suitable now since Google has as implemented A2SD(froyo fat32). Darktremor A2EXT is better name for this work.
Keep up the good work.
Sent from my HTC Hero
Or Apps2EXT...
Actually, on 2.7.6 (or 2.7.5.3 final), I was thinking on renaming everything to Darktremor Toolbox (or something along those lines...anything but Darktremor Apps2SD), since this thing does more than just move applications to the EXT partition. It also moves Dalvik-Cache (Dalvik2SD and Dalvik2Cache) and Program files (Data2SD), plus adjust Low Memory killer settings, sets the Dalvik heap size, converts partitions, implements the Evo SD Card speed fix (which not sure if this works for anyone else), fixes APK permissions, and possibly one or two more things I can't recall off the top of my head.
It seems the program has outgrown its name, plus the confusion between this program and Froyo Apps2SD is getting worse.
adisa said:
I think its time we refered to your A2SD as A2EXT, this is more suitable now since Google has as implemented A2SD(froyo fat32). Darktremor A2EXT is better name for this work.
Keep up the good work.
Sent from my HTC Hero
Click to expand...
Click to collapse
tkirton said:
Theoretically, it should preserve the data (though I don't think anyone, including myself, has done that yet). This should be useful if you were going between nightly builds (seeing that you are on CM7, I presume that's why you asked the question), but switching between two different roms may result in unpredictable operation.
Click to expand...
Click to collapse
It does preserve them. I use this to test different roms on the leo...makes it so I do NOT have to reinstall all the apps.
do I need to flash this every time I flash a new cm7 nightly?
Yes...CM 7 Nightly builds (as with other roms) will wipe out the /system partition before installing the rom, so Darktremor's files are wiped clean as well. You will need to reflash Darktremor in order to restore the boot scripts.
alioooop said:
do I need to flash this every time I flash a new cm7 nightly?
Click to expand...
Click to collapse
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Is there really any need for this if we have froyo? If so please fill me in, I just don't see the point.
Sent from my HTC Glacier
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Actually, there is. The dalvik-cache doesn't move to your FAT32 partition, so you will still eat up storage space with it.
Also, this program offers other features, such as Low Memory Killer tweaking and heap size adjustments.
Some people also reported that the apps run faster when they are placed on an EXT partition rather than using Froyo's FAT32 implemetation. Personally, I haven't really benchmarked it, so I can't tell you from personal experience if it is faster or not.
I guess it's a personal preference.
stoneyjonez said:
Is there really any need for this if we have froyo? If so please fill me in, I just don't see the point.
Sent from my HTC Glacier
Click to expand...
Click to collapse
That may be true right now, but apps are getting bigger in the Android market. I know for other phones, it can be a necessity.
As I said in the previous post...it's more of a preference.
stoneyjonez said:
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Click to expand...
Click to collapse
May I ask if this App2SD working in CM7 nightly ? Thanks to advise .
Depends on who built it.
I have users that say this works perfectly with CM7. During my testing using CM7, I didn't get it to work because the build I had didn't have EXT support (which is needed for Darktremor to work).
So, I would say do a backup of your phone and try it. If you can't get it working, you are more than welcome to send me the logs at [email protected] and I'll see what happened (logs are located on /data directory: files are dta2sd.log, dta2sd.lg1, dta2sd.lg2)
ajaxchen said:
May I ask if this App2SD working in CM7 nightly ? Thanks to advise .
Click to expand...
Click to collapse
Thanks for your promptly reply ; I will give it a try later . But i am wondering if it's a issue that CWM recovery 3.0.0.5 can not find my EXT partition (I had created my 1GB EXT3 with CWM recovery already) ?
That could be an issue. I'm not familiar with that recovery, but if it has a repair function, you should try to run it.
If you don't have that option or the repair was unsuccessful, I would offload the contents of your FAT32 partition on a computer and repartition the card.
ajaxchen said:
Thanks for your promptly reply ; I will give it a try later . But i am wondering if it's a issue that CWM recovery 3.0.0.5 can not find my EXT partition (I had created my 1GB EXT3 with CWM recovery already) ?
Click to expand...
Click to collapse
This would be way easier with amon RA recovery. I remember having it on my g1 and never had problems with it. Clockwork is good but making partitions and ext 3 and 4 is simple from the phone.
Sent from my HTC Glacier using XDA App
I added a new command in Beta 03 that should make it easier to convert EXT2 to EXT3:
a2sd convert-ext3
Killbynature said:
This would be way easier with amon RA recovery. I remember having it on my g1 and never had problems with it. Clockwork is good but making partitions and ext 3 and 4 is simple from the phone.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Is it possible to put the commands into an .apk, just to make it less intimidating and easier to use for some of us? I have no developer skills or I'd try.
stoneyjonez said:
Even if there are some advantages, has anyone actually filled their internal storage on the mt4g already? Hell, to be honest I don't even see the need for froyo's apps2sd. I've installed every app I could possibly find a use for (on internal storage) and still have over 500MB free.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Well there are people who like games and seeing that some of the games in marketplace are 80mb each and some even reach over 100. I filled my 500mb internal storage because i like to game on my phone.
It's in the planning stages. The goal is to build an interface so an average user can interact with it. Sadly, I'm not very good at Java yet and I haven't found a programmer to assist me in this quest. But it's still being planned and will happen eventually.
agriff said:
Is it possible to put the commands into an .apk, just to make it less intimidating and easier to use for some of us? I have no developer skills or I'd try.
Click to expand...
Click to collapse
is the performance changed when the cache isn't in the phone? How much is the card speed (class) important?
Card speed is important when writing. For dalvik-cache and apps, not that much. For moving /data/data to the SD card, it may make a difference.
Read speed is dependent on the quality of the card you are using.
As for performance, I only notice the speed difference when things like dalvik-cache is getting rebuilt. Normal operation...I don't notice the difference.
MuF123 said:
is the performance changed when the cache isn't in the phone? How much is the card speed (class) important?
Click to expand...
Click to collapse
What's the use? We've got plenty of internal storage space.
If you have plenty of space for everything, don't use it. It's not a requirement to use.
It's for people who may want to use it just because they can or they may have a need for it.
Part Four said:
What's the use? We've got plenty of internal storage space.
Click to expand...
Click to collapse
tkirton said:
If you have plenty of space for everything, don't use it. It's not a requirement to use.
It's for people who may want to use it just because they can or they may have a need for it.
Click to expand...
Click to collapse
Not really.
tried working on desire hd stock rom but its not working gets installed successfully but a2sd commands dont work!
My needs:
- underclocking cpu (NOT OVERclock)
- gamma correction for videos too dim
- move apps to microsd.
it's possible only rooting?
or i need also a custom kernel?
i don't want custom recovery and recovery.
parsifal968 said:
My needs:
- underclocking cpu (NOT OVERclock)
- gamma correction for videos too dim
- move apps to microsd.
it's possible only rooting?
or i need also a custom kernel?
i don't want custom recovery and recovery.
Click to expand...
Click to collapse
If you search throught the forums you will find this answered many times over.
For the sake of simplicity I will do so again here.
Yes, you will want to root your device in order to use the apps for underclocking.
Custom recovery is recommended. TWRP is your starter flavor.
You may use apps like link2sd and app2sd if you have your micro sdcard formatted to fat32 w/ two separate partitions, at least for link2sd.
Gamma has been corrected using a custom kernel on the Google Play Edition of the tablet. If you didn't buy it through the Google Play store, It's not the Google Play Edition.
There are (hopefully) some people working on a gamma corrected kernel for the 500, but as of now it has not been released. There is a thread in the development section on compiling your own kernel should you wish to give it a go. Regards,
parsifal968 said:
My needs:
- underclocking cpu (NOT OVERclock)
- gamma correction for videos too dim
- move apps to microsd.
it's possible only rooting?
or i need also a custom kernel?
i don't want custom recovery and recovery.
Click to expand...
Click to collapse
- Once rooted, get this app - CPU Tuner
- Like sleekmason mentioned above, no kernel for the v500 version. However you can get this app without root - Screen Adjuster
- Yes you can move apps to microsd. Follow these instructions - Prep SD Card for moving apps
Make sure to only take a maximum of 20% of the SD Card as a partition, e.g. 32GB should have max 6GB for partition.
Once you've done that, follow these steps to Link the apps to sd card - How to use Link2SD
Pman1342 said:
- Once rooted, get this app - CPU Tuner
- Like sleekmason mentioned above, no kernel for the v500 version. However you can get this app without root - Screen Adjuster
- Yes you can move apps to microsd. Follow these instructions - Prep SD Card for moving apps
Make sure to only take a maximum of 20% of the SD Card as a partition, e.g. 32GB should have max 6GB for partition.
Once you've done that, follow these steps to Link the apps to sd card - How to use Link2SD
Click to expand...
Click to collapse
thanks for the usefull reply...
and now:
1) it's better than setcpu? they underclock also the Gpu?
2) i will do a check.
3) why only 20% max? hour gpad support ext4 or i stick with ext2?
parsifal968 said:
thanks for the usefull reply...
and now:
1) it's better than setcpu? they underclock also the Gpu?
2) i will do a check.
3) why only 20% max? hour gpad support ext4 or i stick with ext2?
Click to expand...
Click to collapse
No probs.
1. Not sure about underclocking the GPU, what I do now is that it has profiles similar to setcpu. I would have recommended setcpu, but depends if you want to pay the £1.50 or not. There's plenty more on Playstore, check out the "similar apps" for cputuner/setcpu.
3. I saw it a few times here and there to only use no more than 20%. I think it's the optimal amount for Links2SD to work and with no loss of speed. Also anymore could cause stability issues to the partition and the unallocated space. To be fair, with a 32GB card, 6GB is more than enough space, I have that on my phone and only used 1.5gb with 100+ apps and some system apps on there too. Works great and faster to load apps than on internal.
For the partition, I've used ext4 on my phone, I haven't tried it yet on my g pad (not needed it). Try ext4 first, if the pad doesn't recognise it, then re-partition to ext2.
Pman1342 said:
No probs.
1. Not sure about underclocking the GPU, what I do now is that it has profiles similar to setcpu. I would have recommended setcpu, but depends if you want to pay the £1.50 or not. There's plenty more on Playstore, check out the "similar apps" for cputuner/setcpu.
3. I saw it a few times here and there to only use no more than 20%. I think it's the optimal amount for Links2SD to work and with no loss of speed. Also anymore could cause stability issues to the partition and the unallocated space. To be fair, with a 32GB card, 6GB is more than enough space, I have that on my phone and only used 1.5gb with 100+ apps and some system apps on there too. Works great and faster to load apps than on internal.
For the partition, I've used ext4 on my phone, I haven't tried it yet on my g pad (not needed it). Try ext4 first, if the pad doesn't recognise it, then re-partition to ext2.
Click to expand...
Click to collapse
Neither ext4 or ext2 were allowed for patitions on the sdcard on my device. This is the gpe which may be different in that, LG may allow for those types.
FAT32 works fine though. I am still working on whats required to allow ext2. Wouldn't think it would be so difficult. I know some of the roms allow for it.
sleekmason said:
Neither ext4 or ext2 were allowed for patitions on the sdcard on my device. This is the gpe which may be different in that, LG may allow for those types.
FAT32 works fine though. I am still working on whats required to allow ext2. Wouldn't think it would be so difficult. I know some of the roms allow for it.
Click to expand...
Click to collapse
Hmm that's strange, I haven't tried so can't tell you if it works or not on v500. There maybe a kernel for the GPE which would allow it, I believe there'es a few in the android development area mostly for GPE (v510).
Edit: Just found this thread, supposedly there's a permission issue on GPE versions, there's a fix though through this post:
http://forum.xda-developers.com/showpost.php?p=48635344
Pman1342 said:
Hmm that's strange, I haven't tried so can't tell you if it works or not on v500. There maybe a kernel for the GPE which would allow it, I believe there'es a few in the android development area mostly for GPE (v510).
Edit: Just found this thread, supposedly there's a permission issue on GPE versions, there's a fix though through this post:
http://forum.xda-developers.com/showpost.php?p=48635344
Click to expand...
Click to collapse
Heh, I'm am a kernel developer for the 510. In signature.
No, it's not a kernel issue as such. well, maybe, sorta. It is a permissions/fstab problem as far as I can tell. I haven't really messed with that yet. The kernel itself DOES allow for both ext4 and ext2, and if somebody wants it, I'll enable ntfs for the kernel as well.
I will need to rip apart a rom that allows it and see what is on file. That won't happen anytime soon as I am working on other items at the moment.
The link you posted is just to get rw permissions for the sd card. nothing to do with the format thereof.
sleekmason said:
Heh, I'm am a kernel developer for the 510. In signature.
No, it's not a kernel issue as such. well, maybe, sorta. It is a permissions/fstab problem as far as I can tell. I haven't really messed with that yet. The kernel itself DOES allow for both ext4 and ext2, and if somebody wants it, I'll enable ntfs for the kernel as well.
I will need to rip apart a rom that allows it and see what is on file. That won't happen anytime soon as I am working on other items at the moment.
The link you posted is just to get rw permissions for the sd card. nothing to do with the format thereof.
Click to expand...
Click to collapse
Interesting, didn't know that. I've got the 500 but not tried an sdcard yet (only had tab for couple of weeks). Do you know if the permissions is a problem for the 500 too?
Wasn't sure if it was the tab that wasn't reading the ext2/4 formats.
P.s. I'm new, didn't realise you are the kernel god for the LG v510. Apologies
Pman1342 said:
Interesting, didn't know that. I've got the 500 but not tried an sdcard yet (only had tab for couple of weeks). Do you know if the permissions is a problem for the 500 too?
Wasn't sure if it was the tab that wasn't reading the ext2/4 formats.
P.s. I'm new, didn't realise you are the kernel god for the LG v510. Apologies
Click to expand...
Click to collapse
Lol. It is a google problem as far as the permissions go. They saw a potential for abuse and removed the auto access as such. I don't know if lg left it the same or does what Samsung does and has their own fix.
In the development section under the kernel compile thread, if you read the last page or two you will see where muiriddin is working on a kernel for the 500 that should take care of the gamma issues and such. I believe he has a test kernel compiled and is working on getting it into a useable zip file for your device. There are still a few mysteries to work out
Anyway, there is a thread on these forums (gpad) that discusses the problem and the same fix you found.
sleekmason said:
Lol. It is a google problem as far as the permissions go. They saw a potential for abuse and removed the auto access as such. I don't know if lg left it the same or does what Samsung does and has their own fix.
In the development section under the kernel compile thread, if you read the last page or two you will see where muiriddin is working on a kernel for the 500 that should take care of the gamma issues and such. I believe he has a test kernel compiled and is working on getting it into a useable zip file for your device. There are still a few mysteries to work out
Anyway, there is a thread on these forums (gpad) that discusses the problem and the same fix you found.
Click to expand...
Click to collapse
Naughty Google!
Oh nice, you have many big threads, nice to be speaking to a clever person! Well i'll be happy to test the kernel out for muiriddin when it's up and ready, sound exciting.
Pman1342 said:
Naughty Google!
Oh nice, you have many big threads, nice to be speaking to a clever person! Well i'll be happy to test the kernel out for muiriddin when it's up and ready, sound exciting.
Click to expand...
Click to collapse
Good Day! Thought you, or whoever else has an interest may like to see this article by chainfire (lead developer),
and this one about android device specific configurations. ( I keep looking at this like there might be some magic there
http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
http://source.android.com/devices/tech/storage/config.html
apparently, the so-so work around for us was initiated by Samsung, and is a dirty hack that they still implement.
I was looking into the init.rc file for the 510 and found:
Code:
mkdir /storage 0751 root sdcard_r
I changed the above to rw thinking I found the golden calf, recompiled the kernel with the adjusted ramdisk and tested it to no avail.
I do however think I'm on the right track.
I dont think the problem is getting the device to user the sdcard(1), as a symlink maybe could do the trick, I think the problem is making it visible to programs like Dolphin when you want to download something, and then getting a request to do so, meaning programs can't arbitrarily write to the sdcard without our explicit permission (root or question).
Update...
Rooted my gpad and tryed almost all setcpu apps for underclock but no lucky.
At start only core0 seem to do the freq i set (1.2 for example) and others 3 core runs at 1.7 but after some seconds all 4 cores return to 1.7
Tested with perfmon app active and running antutu.
Someone help me!
Sent from my LG-V500 using xda app-developers app