Related
THIS TOOL HAS BEEN DISCONTINUED. IF YOU REALLY NEED A LAGFIX, USE VOODOO. HOWEVER, WITH LATEST ROMS I DONT PERSONALLY FEEL A LAGFIX IS STILL NEEDED, THUS I DON'T USE ONE, AND WILL NOT CONTINUE DEVELOPING ONE
About
Here it is, yet another LagFix tool. It's certainly not the first, but it does offer some things others do not (at the time of this writing).
This patch uses the ext2/ext3 image in /data method.
IMPORTANT NOTICE FOR FROYO USERS
(1) Use ext2. ext3 is NOT supported on Froyo, only Eclair
(2) The installation will fail if you apps installed to SD. Go to Settings -> Applications -> Manage -> On SD card. Click each app and click "Move to phone". In the end, the "On SD card" list should be empty. Reboot. Install CFLagFix. When the fix is installed, you can move apps back to the SD card if you wish.
Features
- Lots of checks to make sure the fix is possible
- This is not just based on a script, but a lot of commands are performed and their results rigorously checked to be what is expected
- You can select (from a set of presets) which folders you want to lagfix
- You can select how big the image should be (between 128mb and all the free space in /data minus 250mb, to prevent low storage space warnings)
- The actual moving of data from RFS to the image is done in a boot loop, while the files are not in use. This minimizes the chance of corruption during move (settings being lost, etc)
- Comes with e2fsprogs, and e2fsck is performed each boot to fix a corrupted image
- Comes with it's own busybox, so no need to install it, and no chance for conflicts
- If an ext2 image is used, it is tuned to not reserve any blocks
- If an ext3 image is used, it is tuned to not reserve any blocks and use journalling
- Also moves databases (safely)
- Uninstall option
- Resize option, resize your partition whenever you want, to whatever (possible) size you want
- "Full automatic" option, this will max out the image size while still preventing the low storage space warning, and will also reclaim the space from the backup folders and automatically resize the image to max again after that space is reclaimed. This generally results in an image of about 1.5 GB. It'll also leave some space in case the system still needs to write in /data but not in the image.
- Progress monitor ("educated guess" about progress, not exact, but pretty close, usually!)
A fair number of these seem to be unique at the time of this writing.
Notes
- e2fsck result is stored in /data/cflf/e2fsck_result.txt
- list of mounted directories is stored in /data/cflf/mountlist.txt
- if ext3 is used /data/cflf/imageisext3 file will be present
- my own test rom is JM2+root-with-update.zip+ClockworkMod
Known issues
- In case the image is heavily corrupted, e2fsck may take longer to fix it than the rest of the boot process. Theoretically this could result in data loss
- ext3 does not seem to be supported on Froyo ROMs JP1/JP2/JP3
Credits
- mimocan, ykk_five, RyanZA, and all others who have chipped in for various lagfixes
- cynogen, e2fsprogs built for ARM
- kalpik, busybox APK
- ofcourse the original authors of those tools as well
- myself, this is all based on ADB Magic code
Donations
Please feel free to donate: http://www.jongma.org/dx.php
Requirements
- Windows
- Microsoft .Net 3.5 framework
- Phone in USB debugging mode
- SuperUser
Before using ...
I strongly recommend using ClockWorkMod and making a backup of your ROM. Just in case Also, during any operation, I advise having your phone hooked up so I can draw power from the computer.
Usage
- Unzip the attached file somewhere
- Make sure your phone is connected in USB debugging mode
- Make sure you have SuperUser installed
- Run CFLagFix.exe
There are three tabs:
Install LagFix
This tab allows you to install the LagFix, and lets you configure some options.
I recommand leaving the "Full automatic" option turned on, if you do, just press "Install !" and everything will be arranged for you. If you turn this option off, you can configure some settings manually, but note that using this does not reclaim wasted space of the backup files.
Note that you can still select to use ext3 instead of ext2, even if in "Full automatic" mode.
When you press "Install !", the program will be finished quickly, but your phone may continue working for 30 minutes or so, and keep rebooting very often. If you have a lot of data installed, it may take even longer.
Do NOT even touch your phone until Android boots up again!
A lot of things are checked before the install will start. You will need about 50% free in /data for the operation to work, but it will check this before making any modifications on your phone.
Resize Partition
This tab allows you to change the current ext2/ext3 partition size. The slider will only let you select values that are actually possible, i.e., bigger than your current data usage and smaller than the total space that could be occupied by the image.
Clicking "Resize !" will reboot your phone and resize the partition. Again, this can take an awfully long time! Don't panic, just wait it out.
Uninstall LagFix
This will uninstall the LagFix. It will completely remove it. Before removing it, however, it will move all files out of the image and back into the normal filesystem again, so no data is lost.
Clicking "Uninstall !" will reboot your phone and perform the uninstallation. Again, this can take an awfully long time! Don't panic, just wait it out.
Note that uninstallation will only work if you are using less than 50% of the device's capacity, but again the program will check this before making any modifications on your phone.
You can only uninstall installations of CFLagFix 1.20 and newer !!
BETA
This is very beta, use at your own risk!
WARNING
This patch is NOT compatible with ANY other lagfix tools. Either undo those completely, or just don't use this. If you were using one of those, I'd personally recommend a complete reflash of the firmware before using this patch.
WARNING #2
Before trying 1.80, please see this post.
Download
<< 1.70: 632
Changelogs
1.80, 15-08-10
- Redone some crucial parts of the patching procedure (for all install, resize and uninstall). Should fix all remaining issues!
1.70, 13-08-10
- Added /data/app-private/ folder
- Added progress monitor (estimates.... not exact)
- Moved /dbdata/databases to it's own partition, much faster for smaller read/writes
1.60, 12-08-10
- Updated codebase to ADB Magic 0.9, fixes issues with some weird pre-existing installations of busybox
1.50, 12-08-10
- Added "full auto" mode, "one click" solution for beginners
- Added ext3 support
- Added resize support
- Added uninstall support
- Fixed some issues
- Update scripts
1.20, 11-08-10
- Everything has been moved to /data/cflf/ , this - amongst other things - fixes issues with JP3
1.01, 11-08-10
- Adusted a permission error which could cause the system to be unable to create any new databases
Fix for 1.00 users: there isn't any yet. This is *beep* to fix manually. I would advise this "unpatch" method posted here: http://forum.xda-developers.com/showpost.php?p=7616676&postcount=29, then repatch with the latest version.
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
lyno said:
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
Click to expand...
Click to collapse
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Chainfire said:
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Click to expand...
Click to collapse
Ah yes! I removed all .net frameworks on this works laptop to be able to install some old COM files. Will re-install and test.
This looks so awesome! Thank you!
Any chance for open sourcing this?
installing now
Well im gonna give this a shot, have just installed the african jg8 and rooted,am doing this fix now.
Then ill try the 1.2 overclock on top, ill post a score shortly .
Not bad though i see one problem... it's windows only ^^
select which folders you want to lagfix
Click to expand...
Click to collapse
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this? -> it doesn't recognize both my internal & external sd, but i can browse them properly in Estrongs/astro
veenone said:
After the process finished, the Android displayed information about damaged internal SD, but everything was working.?
Click to expand...
Click to collapse
That sounds scary, think I'll wait a while before trying!
RyanZA said:
This looks so awesome! Thank you!
Any chance for open sourcing this?
Click to expand...
Click to collapse
Not at the moment, but maybe in the future
Tayutama said:
Not bad though i see one problem... it's windows only ^^
Click to expand...
Click to collapse
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
danamoult said:
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
Click to expand...
Click to collapse
You can't really lagfix all folders, as the process where the image is mounted is run asynchronously with the rest of the boot process. There will be havoc if the system can't load certain files because the image is not mounted yet. This is why you can't just lagfix the entire system, but only certain parts.
In the presets I have only added those folders that I feel are mostly safe to lagfix AND would actually benefit the speed of the phone.
Also, for some folders there is some discussion to whether or not it is beneficial to have them in the image, like /dbdata/databases. I personally feel it should be lagfixed, but not everyone agrees.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
Click to expand...
Click to collapse
I have not seen the "damaged internal SD" message before in any of my tests. It might be ROM specific (I'm personally using JM2). I would recommend rebooting (using the "hold power button + press power off" method) and see if the message still comes up. Let me know what happens.
And yes, feel free to post about it in your blog.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this?
Click to expand...
Click to collapse
Replying to the same message again, hehe.
Now that I'm thinking about, how exactly did your device got wiped ? Anything less than an actual firmware flash does not completely remove mimocan's fix, AFAIK. To completely undo it you'd have to completely reflash (and get stock kernel back), and possibly remove the ext partition from your SD. In other words, if you "wiped" from recovery, this is not a removal of mimocan (AFAIK).
Gallery is working fine for me, by the way, and as stated above, I have not seen that message in my tests with JM2 (neither with a lot of apps installed nor a clean flash).
(Then again, this is the first release, so there might be issues )
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
This fix is using exactly same space that is already reserved for user data and programs. And it is on the internal SD. So I really can't think how this fix could cause any damage at all. Thoughts?
I selected maximum Space, and now i have low internal memory. How to remove this fix or change the Space?
Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
Use mimocan's fix if you want to use external SD - it is especially made for that! His thread is a sticky (at the top) in this forum.
veenone said:
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Click to expand...
Click to collapse
Mimocan's fix uses Odin. Like update.zip's, a "factory reset" does not remove patches made in this way, only a real flash does.
Either way, happy to see your problem is solved
I think the problem was the system didn't mount sd cards properly after several boots from CFLagFix. So it needs more reboots to mount the sdcard with structure change properly...
Chainfire said:
Not at the moment, but maybe in the future
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
Click to expand...
Click to collapse
It's a shame you can't open source this.
Personally, there is no way I'm going to run something like this without source - I believe you are just trying to help us out, but there is always the chance that you could be doing something damaging by mistake, or even installing a trojan on purpose.
I'll be following release though, looks awesome and hopefully you'll be able to open source this soon!
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
In recent years I've used CM on my Android devices but now that I have a G4 and the camera and camera app is so good, I'm unhappy to give that up if I can find a way to get the other features I want. (eg, CM/Lineage Privacy Manager, etc)
So I thought one option might be to dual-boot either a stock image or stock-based ROM for when I want to use the high-performance camera, and my regular AOSP-based image the rest of the time. Can I do this on a G4?
One thing that worries me is it seems the base system takes up about ~10GB and G4's only have 32GB onboard. Can I share some storage between the OS's? Presumably at least the MicroSD?
TIA
Here you go https://forum.xda-developers.com/g4/help/dual-boot-t3241460/page6 . I I used to dual boot Imperium/CM14.1.
The storage wasn't a problem. It took only a few GBs and the rest of free space was shared (you see files in different places, something like /sdcard on main, /data/dualboot/romname/sdcard if I remember correctly. I recommend full backup first. Dual booting can bring some additional bugs.
You can share data between apps, but I haven't managed to make it working properly.
Amightypotato said:
Here you go https://forum.xda-developers.com/g4/help/dual-boot-t3241460/page6 . I I used to dual boot Imperium/CM14.1.
Click to expand...
Click to collapse
Ooh, thanks. I was considering Imperium.
Amightypotato said:
The storage wasn't a problem. It took only a few GBs and the rest of free space was shared (you see files in different places, something like /sdcard on main, /data/dualboot/romname/sdcard if I remember correctly. I recommend full backup first. Dual booting can bring some additional bugs.
You can share data between apps, but I haven't managed to make it working properly.
Click to expand...
Click to collapse
I wasn't so much thinking about sharing app data (which I'd assume would be a very dicey proposition), more just having common folders like Downloads/pics/audio available to both instances. (Since you only end up with about ~22GB out of 32GB total storage available in a fresh install, I assume adding another OS instance would leave only ~12GB left for local storage, which could become be a real issue for me. (Just my APK/app data archive on my current daily driver takes up around 9GB right now)
I'm still trying to get my head around the various symlinks and fused partitions that Android uses. The FAQ from TWRP on what the /data/media folder is I just read yesterday and had no idea that was like that. (Or that their nandroid backups don't bother to backup anything at all under /sdcard, basically.. )
I am a power user and I mostly switch a lot between apps, so I don't like discarding.
I use a custom ROM which is less heavy than MIUI ROM yet Still my background apps take a lot of memory that multitasking without discarding is not possible even with 4GB + 2GB zRAM I have.
Do you know any workaround for this without buying a new phone nor sacrificing apps, knowing that when I run cpuinfo in terminal: It doesn't show swp in features, so I don't think the swap will work out of the box with me and using a swap partition in my SD card will make the phone slow also except if there is a way to partition the internal storage or /data.
tberma said:
I am a power user and I mostly switch a lot between apps, so I don't like discarding.
I use a custom ROM which is less heavy than MIUI ROM yet Still my background apps take a lot of memory that multitasking without discarding is not possible even with 4GB + 2GB zRAM I have.
Do you know any workaround for this without buying a new phone nor sacrificing apps, knowing that when I run cpuinfo in terminal: It doesn't show swp in features, so I don't think the swap will work out of the box with me and using a swap partition in my SD card will make the phone slow also except if there is a way to partition the internal storage or /data.
Click to expand...
Click to collapse
go to system build.prop and look for
ro.lmk.kill_heaviest_task=true
set it to false
(just an idea,not sure)
let me know if it worx
loopypalm said:
go to system build.prop and look for ro.lmk.kill_heaviest_task=true set it to false (just an idea,not sure) let me know if it worx
Click to expand...
Click to collapse
loopypalm said:
go to system build.prop and look for
ro.lmk.kill_heaviest_task=true
set it to false
(just an idea,not sure)
let me know if it worx
Click to expand...
Click to collapse
No I don't have the option anyway in build prop.
tberma said:
No I don't have the option anyway in build prop.
Click to expand...
Click to collapse
if you don't have it make it
ro.lmk.kill_heaviest_task=false
loopypalm said:
if you don't have it make it
ro.lmk.kill_heaviest_task=false
Click to expand...
Click to collapse
is this working for Android 11 too?
tberma said:
is this working for Android 11 too?
Click to expand...
Click to collapse
should work
tberma said:
is this working for Android 11 too?
Click to expand...
Click to collapse
copy build.prop somewhere you remember
edit it
reboot
if something goes wrong restore it
tberma