Develop Bugs

[DEV] cram that nand - gain space on your partitions

Modifying your nand adress space is okay, but that means that you have to modify your recovery along with the new rom each time you want to flash a new one.
What I propose is a new, flexibile approach (mainly for devs).
This is just a placeholder atm, but once I get some free time, I'll write about making compressed partitions (mainly static data) using squashfs (this has been done to a certain extent in the past for /system/lib/modules), but adding a bit of flexibility with unionfs/aufs.
The advantages are numerous, as are the uses.
For example: no need for complex apps2sd scripts!
Just mount your unionfs in /data and mount-bind that to another folder on the SD partition of your choice, and voila, apps2sd.
;]
This is of course synonymous to modifying the initrd, but a few lines of really simple script and it's done.
I have successfully tested that with /system, and have to further test with /data
I also have to test unionfs / aufs and make a choice. The ideal one without hesitation is aufs, which has practically superseeded unionfs, but there are a few stability issues involved in the 2.6.29 patches.
There are a few knowledgeable (real) devs around (dunno about any in the Hero forum though), so they probably know what I'm writing about.
You know who you are, so just drop in a post in this thread in case you you would have some ideas regarding the implementation.
n.b. I might have to rewrite that post. It's 01:40 and I'm really tired after my training and work.

placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
>edit 201008181214<
I've successfully patched the tattoo 3G/Slide kernel to build a healthy Hero kernel with aufs.
It kindda hangs in the beginning, but runs just fine afterwards.
Prolly due to my OC settings.
>leak<
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.

good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.

dkelley said:
good concept. I'm curious about performance - this would compress read/write on the fly, right? cpu resources etc, no problem there? no major lag issues in real use (startup doesn't matter much which you mentioned).
No I'm not a rom dev, but I AM a full time career developer.
by the way - I never found a workaround for the audio issue I had with your froyo rom. But it was a good project and I'm happy it's working well for you.
Click to expand...
Click to collapse
I am puzzled as well (audio issue).
You might've noticed that I'm no longer as active in the Hero forum.
I'm done with mdpi devices.
;]
In any case:
I have been working these past few days on optimising the kernel (I have based my work on the tattoo kernel) and aufs is working atm.

adwinp said:
placeholder and a note:
I have patched the reverse-patched kernel (desirec) for this.
I've run into trouble building the official htc-release 2.6.29 kernel with aufs.
Click to expand...
Click to collapse
you should use ninpo's repo, most uptodate kernel sources with a lot of fixes/patches included (http://github.com/Ninpo/kernel-hero/). aufs compilation worked at the first try.
I am also playing around with kernel hacking, since I want to get 2.6.32 on the Hero. Epic wip.
Click to expand...
Click to collapse
ninpo works with elemag on porting 2.6.34, they already made a lot in porting the board files.
btw nice idea with overlaying the file system, I think a lot of nand protected device use that already? (Desire, Wildfire..) http://forum.xda-developers.com/showthread.php?t=748025
unfortunately I have nearly no spare time to play around, but I'm very interested to see how the compressed squashfs affects cpu load and thus the overall phone performance.
found an old but still interesting thread, so even cyanogen experimented with it, maybe there are unresolved issues?
http://forum.xda-developers.com/showthread.php?t=523662
http://groups.google.com/group/andr...36603d429a/646a017892783e2b?#646a017892783e2b

As a matter of fact, Elemag PM'd me about his work.
To be frank, I am only playing around with this out of boredom, till I buy myself a hdpi device (I am waiting for the Glacier, hopefully)
;]
Thx for the links.
I can see that I was not the only one. lol
Despite a totally different approach, Maxisma's posts about a bigger data partition got me thinking, and ultimately reminded me of some work I did in the past with linux livecd's, which gave me the idea to try it on android.
To answer your question: decompressing squashfs is very fast, with little additional load/overhead (although, running a lot of running apps/widgets on our poor 528MHz/729MHz cpu in addition to a compressed system is generally a bad
idea)
I have another idea (from my linux administrating experience as well ;]) I would like to implement, but that would only work on newer devices, which have a lot of RAM.
My idea is to modify the init.rc in order to copy over the SYSTEM: partition ENTIRELY into RAM (essentially create a tmpfs mount point), do a switch_root, and let android take it from there.
This would of course also mean redefining the ANDROID_ROOT env variable to point to the new location.
A further modification would be to mount the WHOLE /system and /data into RAM (provided it fits and leaves enough for runtimes), and THEN further mount aufs in order to write to disk - or write to tmps, but, in the case of aufs, no further work is required, but in the case of tmpfs, you just have to #find all newer files than $uptime (taken from uptime, obviously), and recompress it to the original compressed fs.
That WORKS on a few linux systems I tried.
whew. a lot of ideas, but no device to test on.
;]

[DEAD][UTIL] LagFix using update.zip's - v2.3.3

Made a new thread for the update.zip versions of the LagFix since i have had people asking me to do that so it doesn't get cluttered up together with RyanZA's fix in his thread.
Only one file included... Will overwrite old root version.
Testet on firmware: (Did a fresh reflash every time)
I9000:
I9000XWJG5 (Eclair - Europe)
I9000XWJM1 (Eclair - Europe)
I9000XWJM5 (Eclair - Europe) (Thanks Peaster111)
I9000XXJP2 (Froyo - Europe)
I9000JPJG8 (Eclair - Africa)
Captivate: (Thanks to Zilch25 for testing)
I897UCJH2
I897UCJH3
Instructions:
(Note that i recommend that you do a fresh reflash through ODIN.)
1. Download the update.zip of your choice and rename it to update.zip.
2. Place it on your internal sdcard.
3. Turn off your phone.
4. Hold down Vol Up+Power button+Home Button for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it.
7. After install, the phone restarts.
8. Go to the newly installed 'SL4A' application from the app list, open it and choose either LagFix_Ext2.sh or LagFix_Ext4.sh to install the fix.
9. The script should run takes around 2-4 mins before it reboots.
10. First reboot after applying script will take some time as it's moving data around and mounting folders.
Regarding Step 4: What is written is for GT-I9000 version.
For Captivate and Vibrant as other people with that phone.
For Captivate people that are trying this on I897UCFJ6 please read the following post: http://forum.xda-developers.com/showpost.php?p=7939738&postcount=177
Notes:
The current version works on Froyo BUT you can only use the ext2 option as the current kernels in Froyo doesn't support ext4.
Known Bugs:
Got no idea if people still will have problems with changing fonts with ext2 since it works for me.
Credits:
RyanZA - Original bat fix
husq510 - Supplied files needed to enable ext4 support
Zilch25 - For being my test subject on the Captivate board
Donations:
Had a few people ask for donation link so here it's: Donate
Do note though that you don't have to donate if you don't want to.

Changelog:
v.2.3.3
Minor bug fixes.
Put all into one file that will remove old root and reapply new root in the same zip file.
v2.3.2
Removed custom hosts file for ads blocking as that was the problem with SL4A crashing.
v.2.3.1
Changed version of SL4A which should fix the FC that SL4A is giving.
v2.3.0
Scripts redone to do all moving of data on boot to minimize chance of loosing applications and settings.
Firmware check added to scripts to check if your firmware needs GPS Logging fixed.
Removed support for Ext3 as there is no reason to have it since we can use ext4
Added custom apn-conf.xml file for APN settings.
Added hosts file for blocking ads.
v2.2.2
This fix is for Captivates running firmware I897UCJH2
Turns off GPS logging and removes whatever logs that might already have been made
v2.2.1
Fixed old bug with /data/app-private
Added checks to scripts so they check if your system has support for the filesystem you choose
v2.2
Added Check_Space.sh to sl4a
Added support for ext4 (Only works on eclair builds)
Busybox 1.17.1 is NOT required anymore, but is the version i'm including.
v2.1
Based on RyanZA's v2.3
Added support for ext3 (Only works on eclair builds)
Removed support for /dbdata/databases
Changed /data/app-private from mount to symlink
Added two versions of the zip's. One for people who already have a rooted SGS and one that will root the SGS.
v2.0
Based on RyanZA's v2.0
Initial release.
Added support for /dbdata/databases
Added support for /data/app-private

Hey, would you like me to test this on JP3??
Thread

is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work

Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)

Thread Astaire said:
Hey, would you like me to test this on JP3??
Thread
Click to expand...
Click to collapse
You are welcome to test it on JP3 if you want to but just remember Clockworkmod Recovery can have problems with applying the update.zip's
rbanaco said:
is it possible to undo this lag fix? what scores in quadrant are we expecting with this?
All lag is gone with this or is there some left as I encounter in ryan's? tnks in advance for the hard work
Click to expand...
Click to collapse
There is a script included to remove the lagfix. From test with stock kernel quadrant score is excepted to be around 2100-2200 with ext2 and 1800-1900 with ext4.
From all the testing we have been doing on this release when fixing bugs there haven't really been that much lag... you might see small lag when opening an application for the first time or when installing an app since we are using a different method this time where we don't move the application's apk's after it's installed, but personally i haven't seen this yet.
omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
Hmm no idea tbh... You might be able to open the zip, replace the files and close it again without losing the signature that it's signed with, but this is something that i haven't tried yet so don't know if it will work.

thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you

rbanaco said:
thanks for the answer.. one more question if you don't mind answering.. what would you advise ext2 or ext4? which provide better performance despite of the score? thank you
Click to expand...
Click to collapse
I would recommend ext4 since it have journaling, which means there is a smaller chance on losing data if your phone lose power by pulling the battery or if the battery reach 0%.
Other people would say ext2 since ext4 might reduce the lifetime on the NAND since it has journaling
I have only tested the ext4 myself pretty much while i have had others to test both ext2 and ext4. Also this is what Zilch25 has posted about ext2 and ext4 on the captivate forum:
Is EXT2 for me?
If you want your Quadrant scores to be bloated beyond belief and don't care if your data spontaneously combusts (Results may vary). Alternatively if you're worried about your NAND wear leveling not being able to handle the strain of EXT4 journaling.
Okay EXT2 is scary, how about EXT4?
You can't afford for your things to get corrupted? Weirdo. Real world performance between EXT4 and EXT2 is barely noticeable if at all, for the everyman this is probably your best bet.
Click to expand...
Click to collapse

omrij said:
Hi
Great tool
if i'll replace files in the zip will it still work?
(like replacing busybox with version 1.18 and replacing apn-conf with one who has Israeli carriers or adding fonts library for hebrew fonts)
Click to expand...
Click to collapse
i think u can replace or delete files as u like.
i replaced, delted or added files every time before i flashed a new ROM, like HACKECLAIR or SamSet.
Works well.

applying ext4 gives me the stopped unexpectedly google error

Yeah I can second that... after a full wipe SL4A is giving me FC's now too =P

Just wanted to add:
EXT2 may be less safe than EXT4, but to-date, there has been no reports of any corrupt or lost data using the EXT2 fixes. This is over a pretty huge sample over a fairly long period. Not to say there are no problems with EXT2, but there has not been any impact to anyone for using EXT2 as yet.
Other than that, awesome job Tayu! Looks great!

yep, i get the force close for either script from sla4

OK ill reupload with the old version of sl4a then.

Im still not sure wether i should go for Ryan's one-click .apk fix or this one.
Anyone tested this one on I9000XXJM2? wich is stock firmware for me.

Tayutama said:
OK ill reupload with the old version of sl4a then.
Click to expand...
Click to collapse
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close

Tayutama said:
v2.3.1 uploaded which replaces sl4a_r1 with sl4a_r0 which was the one used in the older versions of the fix. Should fix the problem with getting force close
Click to expand...
Click to collapse
Applying it now, I'll let ya know how it goes

do i need to remove the previous sl4a?

A.VOID said:
do i need to remove the previous sl4a?
Click to expand...
Click to collapse
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk

Tayutama said:
would be the best as they each got a different name.
If you got root explorer you can remove it from /system/app
It's called: sl4a_r1.apk
Click to expand...
Click to collapse
Yeah you might need to... I just reapplied without removing it and only r1 shows up =P

[DEV HOWTO] Use Voodoo in your kernel - Easy method - ready to use.

Until now Voodoo lagfix and tools required to be built from sources: https://github.com/project-voodoo/lagfix
As it's still the preferred and most powerful method, a much easier one exist now.
HOWTO:
1/ Pick your initramfs (ramdisk)
downloads / voodoo initramfs list
This directory contains ready-to-use initramfs for a lot of models and Firmware/Kernel versions.
full-uncompressed.cpio.gz is the recommended option. you can also gunzip it or recompress the .cpio to lzma
full-lzma-loader.cpio.gz allow you to build smaller kernels for Eclair, at the expense of loading time.
Benefit of using direct .cpio images is that you don't have to worry about permissions.
2/ Make menuconfig
General setup --->
[*] Initial RAM filesystem and RAM disk (initramfs/initrd) support
(/choose/your/full-uncompressed.cpio.gz) Initramfs source file(s)
Make sure you also enabled the Ext4 driver in
File systems --->
<*> The Extended 4 (ext4) filesystem
Exit
3/ Build the kernel
nice -n 20 make -j8
Congratulations !
You now have a Voodoo able kernel

Very good work supercurio. Love it.
I think Samsung needs to appoint a whole cell of staff to interact here on XDA. That would be an ultimate.
XDA <-> Samsung. Lug it out boys, let the best come out.
Angry Birds <-> Lazy Pigs.
Edit : Competition brings out the best. But who should tell them???

Samsung developers work also their ass off.

supercurio said:
Samsung developers work also their ass off.
Click to expand...
Click to collapse
This has a touch of genius.

I'm replying just to give ragin some company.
Ps. supercurio rocks! Ds.

Thanks curio!

awesome, thanks supercurio

NST-Kernel v0.1 USB-Host and Multitouch enabled (for software versions 1.1 and 1.1.2)

Hi,
after the great work from verygreen, wheilitjohnny and arkusuma I decided to build a kernel with both of their improvements included.
Features:
based on the BN kernel for the software versions 1.1 and 1.1.2
USB-Host by verygreen http://forum.xda-developers.com/showthread.php?t=1457971
Multitouch by wheilitjohnny and improved by arkusuma http://forum.xda-developers.com/showthread.php?t=1563645
Additional USB related drivers (usb-storage, usb-serial ...)
This is just the kernel, you still need to perform additional steps to get this features working, please look into the corresponding threads.
Howto install the kernel:
Download the file with the kernel and extract it, you should get a file called UImage
Use Noogie or adb to replace the uImage on the /boot partition
Reboot
DISCLAMER and WARNING:
I'm not responsible for bricked devices, dead SD cards, lost data, fried USB-Devices. Make a backup before you try anything described here!
USB-Host support is still WIP (work in progress), the battery drain is noticeable higher. If you don't plan on using the USB-devices you should use a kernel without USB-Host support.
Downloads:
NST-Kenel_v0.1_uImage.zip
github repository for the sourcecode
Thanks to:
verygreen for the USB-Host support
wheilitjohnny for the initial Multitouch support
arkusuma for the improvements to the multitouch support
Renate NST for testing

Great work! Thanks mali100!
by the way, this is the kernel for 1.1, right?
just better state that avoid asking XD
P.S.: I didn't look at the kernel for previous versions, is the kernel actually changed?

wheilitjohnny said:
Great work! Thanks mali100!
by the way, this is the kernel for 1.1, right?
just better state that avoid asking XD
Click to expand...
Click to collapse
Thanks, totally forgot to mention this. It is for 1.1 and 1.1.2
P.S.: I didn't look at the kernel for previous versions, is the kernel actually changed?
Click to expand...
Click to collapse
The kernel changed from 1.0 to 1.0.1 and also with the update to 1.1. But no changes for the last update from 1.1 to 1.1.2

mali100 said:
Hi,
after the great work from verygreen, wheilitjohnny and arkusuma I decided to build a kernel with both of their improvements included.
Features:
[*]Additional USB related drivers (usb-storage, usb-serial ...)
[/LIST]
Click to expand...
Click to collapse
Very nice! I haven't been able to make proper use of usb-serial converters yet because the permission of the created device (eg /dev/ttyUSB0) is always set to 0600 when the device is connected. From what I've read, usually an entry in ueventd.rc solves this. Unfortunately ueventd seems to be omitted from the B&N image..

How are you trying to open the device? It worked fine when I tried directly from the terminal or with this app https://play.google.com/store/apps/details?id=android_serialport_api.sample

My USB keyboard does not work with this kernel. Multi Touch works so I uploaded the file right (Noogie). It worked before with the original "USB-Host" kernel.

Just to be clear, what's the difference between:
usb-host-mt-pack_0.1.zip
&
NST-kernel_0.1_uImage.zip
?
The mt-pack update should go over the uImage or can it be applied direct?

The mt-pack includes this kernel, and all the other stuff mentioned there. It's not necessary to use both. If you want an automated way of installing multitouch and usb-host support, just use the mt-pack, if you want to do everything manually take the uImage and figure out what else you have to change.

Hi
Have anybody such kernel for nook with Glow 1.1.5?

up

pasha4ur said:
Hi
Have anybody such kernel for nook with Glow 1.1.5?
Click to expand...
Click to collapse
Hi, I'm also wondering if somebody with a Glow has already tested this?
Thanks in advance!

OK, so I'm an idiot - I've searched high-and-low, and I can't find a solid method for easily moving this kernel over to my touch. I'm building a survey tablet for a non-profit, and the e-ink screen would be awesome for them - having a multitouch keyboard even better.
Any pointers? I tried CWM SD card, and can't mount /boot, ADB doesn't show /boot.
Is it as simple as connect via adb and:
mkdir /boot
mount <some point> /boot <some flags>?
profit!
?

Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot

Renate NST said:
Code:
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
Click to expand...
Click to collapse
Thanks, that did it. 2 years of .Net and my Linux has just about evaporated!

Hi,
I already have multitouch enabled for a long time using another tutorial.
Does yours fix the problem with the screen sometimes locking up (where you have to slide with two finger to release it again)?
Or does this version also have that problem? Thanks!

rhhd said:
Hi,
I already have multitouch enabled for a long time using another tutorial.
Does yours fix the problem with the screen sometimes locking up (where you have to slide with two finger to release it again)?
Or does this version also have that problem? Thanks!
Click to expand...
Click to collapse
It's based on the other kernel and has the same problems.

[APP] LagFix (fstrim) v1.5.1 2013.03.04

THIS APP REQUIRES ROOT!
READ FAQ! Read that FAQ BEFORE you try app!
Premium version is now ON SALE! -50% off of the price! Enjoy!
Some Android users suffer from poor performance after some days/weeks of heavy usage. This is due to a well-known TRIM bug affecting these devices (there are reports that some Galaxy Nexus devices also have affected memory chips). Users with -discard mount option are NOT affected!
The source of the problem is that internal storage is not properly TRIMmed when needed. You can find lots of information on XDA - http://forum.xda-developers.com/showthread.php?t=1971852 and http://forum.xda-developers.com/showthread.php?t=1929021 for example. It is also well-known fact that running fstrim Linux tool from time to time fixes the issue until internal memory runs out of free blocks. Other solutions like mounting with -discard or disabling fsync may be slow or dangerous.
LagFix is a user-friendly implementation of fstrim utility. It allows you to select which partitions to trim (you should leave defaults unless you know what you are doing) and run the process easily.
Please note that fstrim output depends on kernel and device. It works fine unless you see errors. You might see big amounts of bytes, zero amount or repeating amount. All are fine! Read fstrim manual to understand why all these outputs are valid.
It is also advised to reboot your device after the TRIM process so that kernel could reinitialize block data.
There are two versions of LagFix:
Premium version (v1.5.1) - no ads + ability to auto-run trimming on specified schedule. The best choise!
Free version (v1.5.1) - trims your memory with one click, has ads, no schedule.
Warning! Premium version comes from different publisher! This is because Google does not allow to publish paid apps from my country. Send your rage to Google Both versions are legit, don't worry.
Release notes:
v1.5.1
+ Added CWM SuperUser support;
+ Added android.permission.ACCESS_SUPERUSER permission;
* Fixed disabling scheduler;
+ New notification icons.
v1.5
Full rewrite, dropped RootTools lib, made my own. No more problems!
v1.4
+ Device compatability detection is now completely reworked
* Fixed a crash
Earlier changelogs:
v1.3
+ New UI
+ Added Info screen
+ Added device compatability detection (looks like it should be improved further)
+ Renamed Donate version to Premium
* Fixed scheduling dissappear after reboot (Premium version)
* Some other bug fixes
v1.2 premium
* Added auto-trim functionality which runs on specified schedule. Click Schedule button and you'll see the options. Setup the way you want and click Install. The button will change to Uninstall to remove auto-trim if needed.
* Added detection if your device supports TRIM - run it once and you will know.
* Fixed some bugs.
v1.1
* Fixed chmod not working on some custom Sense ROMs.
* Added Android 2.2+ support.
* Fixed crashes.
* App is now multi-threaded.
* Updated UI a bit.
* New icon.
* App is renamed.
P.S. If your ROM mounts /data with -discard then this app is NOT needed!
P.P.S. Free version is now attached for those, who do not have market for some reasons.

Excellent!
Thanks for this. only a day ago i pushed a load of music to my OneX and have been suffering ever since.
I'll give this a go and report back!
To be clear, should I now be able to fill the phone storage to almost capacity with this running? (not currently possible as it just slows down and heats up, draining the battery)
update: enabled the defaults and it said it was successful with some large numbers trimmed. rebooting now

zombiefly said:
To be clear, should I now be able to fill the phone storage to almost capacity with this running? (not currently possible as it just slows down and heats up, draining the battery)
Click to expand...
Click to collapse
You run this app every time your device becomes SLOW AS HELL. It does not work in background since it would impact performance. Previously I used backup/restore solution once a week to fix lags. So in my case I will now run this app once a week.

Wow, just used this on my gnex, and all I can say is: thanks!
I was originally running with the discard Mount option, but it turns out it wasn't doing anything as your app trimmed a quite big number. (I have since removed said Mount option)
Also, I used to have issues with an app that set settings on boot not actually doing so, but after this app it works again. And my phone feels snappy again.
Thanks for this app.
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
Wow, just used this on my gnex, and all I can say is: thanks!
I was originally running with the discard Mount option, but it turns out it wasn't doing anything as your app trimmed a quite big number. (I have since removed said Mount option)
Also, I used to have issues with an app that set settings on boot not actually doing so, but after this app it works again. And my phone feels snappy again.
Thanks for this app.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm glad my app helped! May I ask to do me a favour and rate app in Play Store? That would be nice

AuxLV said:
You run this app every time your device becomes SLOW AS HELL. It does not work in background since it would impact performance. Previously I used backup/restore solution once a week to fix lags. So in my case I will now run this app once a week.
Click to expand...
Click to collapse
thanks. This is brilliant
the problems i talked of in my earlier post appear to have gone now after running Lagfix. My Phone is back to it's usual speed.
I was also using the emergency restore rom image method, glad I don't have to do that anymore, was a major pain.
I was looking into an app i use called settings profiles as I wanted to run lagfix after every usb dismount, unfortunately it doesn't support running applications, which is a shame. Is there any other way of hooking this in to run automatically after (un)mounting as a usb drive?

zombiefly said:
I was looking into an app i use called settings profiles as I wanted to run lagfix after every usb dismount, unfortunately it doesn't support running applications, which is a shame. Is there any other way of hooking this in to run automatically after (un)mounting as a usb drive?
Click to expand...
Click to collapse
LagFix trims /data partition, it has nothing to do with /sdcard which is mounted/unmounted. I will add scheduler in the future releases.

i'll give this a try on Nexus 4 since it's affected too by the slow down write performance if free space left less than 4GB. well done and thanks for keeping it free!

chrone said:
i'll give this a try on Nexus 4 since it's affected too by the slow down write performance if free space left less than 4GB.
Click to expand...
Click to collapse
I hope to hear your report if it will help in Nexus 4 case since I dont have one to test myself.

works great! :good:

Hey,
Work great on Nexus 10 AOKP
But not work on HOX on Renovate rom with Trip Kernel. I think Sense kernel is the probleme or other.Root acces is OK
# fstrim -v /data
sh: <stdin>[32] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
# fstrim -v / cache
sh: <stdin>[35] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
Thanks for your work

AuxLV said:
I hope to hear your report if it will help in Nexus 4 case since I dont have one to test myself.
Click to expand...
Click to collapse
Just updated my post above. It works! I chose all /system, /data, and forgot the other partition.
Much appreciated dude!! :good::good:
Care to adding fstrim for Nexus devices to your app name?

Doesn't work on Bindroid Sense 4+ ROM. Access denied and doesn't ask for root acces.

AlexNne said:
Hey,
Work great on Nexus 10 AOKP
But not work on HOX on Renovate rom with Trip Kernel. I think Sense kernel is the probleme or other.
# fstrim -v /data
sh: <stdin>[32] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
# fstrim -v / cache
sh: <stdin>[35] : /data/data/com.grilledmonkey.lagfix/files/fstrim : can't execute : Permission denied
Thanks for your work
Click to expand...
Click to collapse
Thanks for report, looks like chmod was not executed successfully. I'll look into this issue and add a fix in next version.
You can try to fix it manually if you are familiar with Linux console:
Code:
# su
# chmod 777 /data/data/com.grilledmonkey.lagfix/files/fstrim

Kroutnuk said:
Doesn't work on Bindroid Sense 4+ ROM. Access denied and doesn't ask for root acces.
Click to expand...
Click to collapse
Does not ask for root? This is very strange... I'll look into it too. Sorry for such problem - I don't have Sense ROM so I couldn't test...

AuxLV said:
Thanks for report, looks like chmod was not executed successfully. I'll look into this issue and add a fix in next version.
You can try to fix it manually if you are familiar with Linux console:
Code:
# su
# chmod 777 /data/data/com.grilledmonkey.lagfix/files/fstrim
Click to expand...
Click to collapse
Thanks !
I forgot the chmod
Fix manually with terminal emulator with chmod 777 and is OK.
Renovate Rom with Trip kernel 002 and Sense + are OK for fstrim

Nexus 4 16GB Storage Performance Over Time & TRIM
Before and after filling up the storage (coming from 5GB and filling it up to 1.2GB space available):
SW from 10 MBps to 4 MBps ~ 60% loss
RW from 1 MBps to 0.39 MBps ~ 61% loss
Did a reboot and the performance is getting better (1.2GB space available, deleted some files left with 2.2GB space available but the performance is more less the same):
SW from 4 MBps to 9.89 MBps ~ 147% gain
RW from 0.39 MBps to 0.51 MBps ~ 31% gain
Using the fstrim app (LagFix for Nexus 7 and HTC One X) and reboot (2.2GB space available):
SW from 9.89 MBps to 9.9 MBps ~ 0.1% gain
RW from 0.51 MBps to 1.07 MBps ~ 110% gain
:good::good:
i see a future request is in order, daily/weekly midnight crontab?

Odp: [APP] LagFix for Nexus 7 & HTC One X
Looks like it works on OrDroid 12.5.1, which is Sense Rom, no errors...
Wysyłane z mojego HTC One X za pomocą Tapatalk 2

It's working on ViperX JB, which is a sense based rom. It brings some smoothness, or Its a placebo effect, Im not sure )

tried it manually and then the app and now it worked i tried and in antutu the I/O is still at 896....and i get only 12828 points in antutu :/ ...hm i try it again with the trimming...