Related
Custom MTD Partitions
This is an implimentaion of lbcoder's Custom partition layouts
be sure to checkout that thread for the full history
What does it do?
Well, basically Custom MTD Partitions resizes your MTD partitions
for instance this is a CM6.1RC1, ( heavily customised )
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock3 73.0M 72.8M 236.0K 100% /system
/dev/block/mtdblock5 134.8M 107.2M 27.6M 80% /data
/dev/block/loop0 896.0K 896.0K 0 100% /system/lib/modules
/dev/block/loop1 4.0M 4.0M 0 100% /system/xbin
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /sd-ext
/dev/block/mmcblk0p2 457.4M 201.8M 231.1M 47% /cache
/dev/block/mtdblock4 2.0M 776.0K 1.2M 38% /dev/cache
most of my Apps are on sd-ext, dalvik-cache is on data
/dev/cache is where the real cache partition is mounted, /cache is actually a bind mount from /sd-ext/cache
Applicable to..
Probably any device that uses the same kind of nand as the G1 MT3G ( msm_nand )
The intial scripts are geared towards G1 / MT3G. however I have 'rewritten' much of the script for v1.5 , it now reads the partition table in dmesg, so it _should_ be universal **
v1.5.3 confirmed to work on heroc
v1.5.6 confirmed to work on bravo + bravoc ( with S-OFF )
unsure if it will work with your device? checkout the source on github ( or ask your favourite dev to take a look )
The 'Tech' in Breif
This method is beautifully simple...
When booting we give the kernel the mtd partition table we want to use..
Thats it
In practice we need to do this when booting to recovery, and booting the rom.
below are files to make this as simple flashing a rom.
Credits :-
Lbcoder - for coming up with the idea
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Techjosh - for fixing the patchers for use with Rogers (EBi1)
Mblaster - for pointing out my nasty habit of using -r zip flag at the end of command ( breaks compatibility with older zip versions, fixed in AutoPatcher v1.5 )
Safety First
This method is safe, however it is not without risk
Two things could potentially go wrong
Recovery flash corrupt
This is extremely unlikely, and tbh could happen anytime you flash recovery
If in the very unlikely event that you find you can't reboot to recovery you have three options
re-flash recovery via fastboot ( the preferred option )
re-flash recovery via ROM ( not a great option with cm5.0.x/cm6 )
Do the whole root thing all over again ( no one wants to do that )
system, cache , data partition unmountable - corrupt
Under the right ( or wrong ) circumstances it is possible to get 'junk' files stuck in system ( or cache,data ), and in such away that recovery can not delete them, more serious corruption can render the partitions unmountable.
It is actually quite straight forward to fix this, but it does require fastboot
Code:
fastboot erase system -w
Clockwork Recovery 2.0.2.0 and later has erase_image binary, if you can adb shell in then
Code:
for i in system cache userdata;do erase_image $i;done
and reboot
I would advise you seek out how to 'fastboot', which tbh is a good thing to have regardless of using this 'hack' as it can get you out of so much trouble
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
Prevention is better than cure
I have only managed to corrupt partitions when switching partition layouts while having files on cache or data, for example going from System 67.5 Cache 67.5 to System 90 cache 5 with
cache approx 80% 'used'...
I have not been able to repeat this if I wipe Cache before rebooting,
therefore I advise that you wipe both cache and data * after patching recovery ( and rebooting )
* along with system if you are using clockwork
OK, now lets patch recovery and a ROM
Install Instuctions
It really is quite simple
download FR-recovery-v1.5.6-CustomMTD_S.zip and FR-boot-v1.5.6-CustomMTD_S.zip
create mtdpartmap.txt and put on /sdcard/ see configuration *
reboot to recovery
nandbackup
wipe cache + data
flash FR-recovery-v1.5.6-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Either : -
Nandrestore
Flash ROM + extras
flash FR-boot-v1.5.6-CustomMTD_S.zip
reboot
* configuration
The script in the recovery patcher checks for /sdcard/mtdpartmap.txt and reads that to override the default sizes.
e.g. for system 90mb and cache 2mb
NB make sure you mount sdcard first, else you won't write to sdcard/mtdpartmap.txt !
Code:
echo "mtd 90 2" > /sdcard/mtdpartmap.txt
data would be 117.8mb ( 116.7 useable )
e.g. for system 55mb and cache 2mb ( Purhaps a nice 'sugar free' Donut )
Code:
echo "mtd 55 2" > /sdcard/mtdpartmap.txt
data would be 152.8mb ( 151.7 useable )
NB, above data sizes are for G1s, MT3Gs should add ~78mb
All In One Patch runner ( New to v1.5.3 )
new option to run the All In One Patch script ( versions 1.3.6 and higher )
the format is
Code:
aio <option1> <option2> <option3>...
e.g.
Code:
aio swap remount shabang lwp
By default it will install the sd-ext mount ( option sdext )
so a line just reading aio will be fine
Note: the patch must be on the root of the sdcard, and its file name must start with "fr-patch" and end with ".txt"
if you have several versions the newest ( as per files datetime stamp ) will be used
Faking your SPL
If your using an SPL that is not officially supported by your ROM and that ROM checks your SPL you can 'patch' to fake it.
Code:
echo "spl 1.33.2005" >> /sdcard/mtdpartmap.txt
note that we are using ">>" here, this is to append to the file ( ">" would overwrite it )
you can by all means use any text editor you like, the script will automatically convert to unix format
NOTE : you are dodging the checks the ROM dev put in place, do not complain to them if this doesn't workout for you
in post 2 I have some 'CM6' Kernels I compiled for (1)0.95.xxxx SPLs
but I will only likely do these for RCs and Finals ( and there maybe a delay ).
In that post I point you towards the 'SafeSPL' ( 1.33.2003 ) this SPL is compatible with the current CM6 kernels ( so no need to wait for me or someone else to compile with bluetooth as modules ), but 1.33.2003 is not 'officially' supported ( its stock at 67.5mb system ) so you need to Fake your SPL ( say 1.33.2005 ) and resize to 90mb system ( or whatever you feel is optimum )
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
NB New Config option !!! to automatically run fr-patch136+
e.g.
Code:
mtd 90 2
spl 1.33.2005
aio swap remount shabang lwp a2sd
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.6.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
The Future....
lbcoder has already suggested ways in which we can implement this 'on the fly'
so for instance it would be possible for a ROM , to instruct recovery what MTD partition layout is required, reload mtd kernel modules, and then flash ROM + boot.img
for those with huge partitions
Hey, you could go all silly and dual boot between ROMs ..
Anyway, enjoy and feel free to modify/improve on these
Changelog
v1-5-6 : 2010-10-28
Calculate userdata size, greatly improves compatibility
Added a version to patch a boot.img ( boot-rpp ) with run-parts
didn't want to , but some are using roms which don't have run-parts, so the 06BindCache script wasn't running
Added a remove version ( remove )
flashing this will return the recovery to SPL's layout
I may well integrate that better, so you don't need a separate zip
AutoMTD_partitionPatcher can convert a recovery.img to a AutoMTD flashable zip
PatchUpdateScript.sh <full path to>/recovery.img
boot patcher is much cleaner, it just uses the cmdline of the running recovery
removed the default 90 2 sizing, you *must* set your own size in mtdpartmap.txt
v1-5-4/5
added stuff
removed stuff
moved stuff
see v1-5-6
v1-5-3 : 2010-08-13
This should be last version we need
greater compatibility with none dreams/sapphires
option to launch All in One Patcher
v1-5-2 : 2010-08-0
Bug fixes
recovery was getting written to boot ( flash_image <partition> is now a variable )
typo in env variable was causing cache and data calculations to fail
AutoMTD now prints version number ( when flashing patched Zip )
tided up system "0x" 'fudge' ( to be compatible with trout/sapphire fall back )
removes temp files from memory when done
v1-5-1 : 2010-08-06
Bug fixes, had an extra '0x' on the system start + functions had wrong env var for the location of dmesg derived partition map
v1-5 : 2010-08-06
Version numbers brought into sync
Zipe Filename - 'reordered' ( easier to see version numbers in CWR )
AutoMTD Patcher - changes as per boot Patcher + zip recursion fix ( my bad habit, thanks go to mblaster for pointing this out )
Boot Patcher - cleaned up cache bind mount
Now supports leagcy /system/sd mount point
[*]supports ROM Manager ( real cache partition mounted on /dev/cache, recovery dir symlinked from 'fake' to 'real' cache )
Recovery Patcher - can 'fake' your SPL ( see configuration )
Recovery Patcher - creates more noise ( advise wipe and reboot )
Single Patcher script ( so I don't have make the same changes to three different files that essentially do the same job )
No longer 'Hardcoded' to 32[a/b] Partition Layout ( figures out SPL layout via dmesg ) **
uses original boot/recovery img's base configuration ( i.e. EBi0 and EBi1 compatible )
=< v1.4
Recovery Patcher v1.3, added SPL faker
Boot Patcher v1.2, fixed oversite where boot.img was not 'dumped'
Recovery Patcher v1.1 initial
Boot Patcher v1.1 ( was a fail, it didn't patch boot.img on CM roms as the tmp boot.img was deleted, my fault for just using the AutoMTD Patcher's script ( which runs before the tmp boot.img is deleted )
Boot Patcher v1 initial
Todo
- 2010-08-13 redundent ( launching AIO script ) - I might add some stuff to cm5/6's backup routine via the Auto patcher, things like the "All in One" installed scripts: 05mountsd and remount
windows compatible AutoMTD script ( meh, I hate batch scripts )
- 2010-08-13 DONE - thinking of adding a config option to launch the "all in one" script, but have to make that recovery compatible first
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
Downloads
.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:.
mediafire downloads
http://tinyurl.com/customMTD
aab0fadf658ed275954aea8d0aed9c8f FR-AutoMTD_partitionPatcher_v1.5.6.tar.bz2
8857194cdbe34a52d173def4441ad2ae FR-AutoMTD_partitionPatcher_v1.5.6.zip
1f84a5ec50684a7830a93a8d455bc159 FR-boot-rpp-v1.5.6-CustomMTD_S.zip
bca0360f91aed0acf6e2dc82dfe01b56 FR-boot-v1.5.6-CustomMTD_S.zip
94b4238c2668cbe7cd52fb8ad5a2ee12 FR-recovery-v1.5.6-CustomMTD_S.zip
5404f1a41dbc60105d59c7fa0c335a70 FR-remove-v1.5.6-CustomMTD_S.zip
The attached files are OLD
Custom MTD FAQ
FAQ
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my SPL starts with 0 or 10, and I want to try CM5.0.8 or/and CM6. DO I need to do anything extra?[/b]
A yeap, it seems the newer kernels are just a bit too big for x0.95.x00x SPLs, you can get round it with the below kernels. And to flash CM6 you need to 'fake' your SPL ( see configuration in OP ) or edit the updater-script. faking is easier.
However, I would recommend the 1.33.2003 SPL ( you still need to fake your SPL, but you won't need the 'special' kernels )
guide for flashing 1.33.2003 SPL by Ezterry
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-11
I have compiled a kernel, which I hope is NoneDanger compatible
the source is simply CyanogenMod's github, I have taken the config from cm6rc1, and simply changed the bluetooth to modules
this approach has worked in the past
It is pre-patched with AutoMTD, so just flash cm6rc1, then flash this
FR-CM6RC1-bootimg4NoneD-AutoMTD.zip(MD5: 386D9A05A3C0FFC08E5B3F844D437AA7)
mirrors
http://rapidshare.com/files/406402016/FR-CM6RC1-bootimg4NoneD-AutoMTD.zip
http://www.mediafire.com/?152jnqwyme3
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-07-27
NoneDanger compatible Kernel for RC2
FR-CM6RC2-bootimg4NoneD-AutoMTD.zip (MD5: 7858a8a8d126919318d1718c6e5167ec )
http://www.mediafire.com/file/ttxfcocsti3mma3/FR-CM6RC2-bootimg4NoneD-AutoMTD.zip
I'll have to dig out the src
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
2010-08-15
NoneDanger compatible Kernel for RC3
2010-08-17 ( Sorry, old one had a status6 bug )
New one here
87F160F08FCD2233DDD40FBFC50D3711 FR-CM6RC3-bootimg4NoneD-AutoMTD.zip
src = http://github.com/CyanogenMod/cm-kernel/tree/48c57f11abaaf3de6c81f6f5c44cfe2637251184
no modifications its straight cm ( besides the config, which you can get from the compiled kernel or zcat /proc/config.gz )
#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
*NB* don't use a patched recovery to flash SPL or RADIO ( you should avoid using recovery to flash these anyway, feel free to ask for current advice on spl / radio flashing )
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q do I need to flash both of the files each time I install a new rom?
A No, you only need to flash the recovery patcher once, unless you want to resize or you install a new recovery.
the boot patcher *must* be flashed after you have installed a new ROM or Kernel update
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q my cache looks odd in df, I see two and its the same size as data or sd-ext, is something wrong?
A everything is fine, since we shrunk cache its no good for things like the Market, so a script is installed to 'bind mount' cache with /sd-ext/cache or data if sd-ext is not mounted.
it actually turns out that /cache is not actually used in CM6, so I might adapt the script a little in a future release.
EDIT: as of version 1.5 the cache bind mount script mount 'real cache' separately, which should reduce confusion
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Q When I tell ROM Manger to do something in recovery, it just reboots to recovery and does nothing. it used to do the action but not since I installed CustomMTD
A yeah, nearly forgot about that, I was going to fix it last week, basically ROM Manger writes commands to /cache, but its writing it to our bind mount so.. when recovery boots it doesn't see the commands.
In all honesty that one hasn't been pointed out to me yet, but yeah I can fix it..
EDIT: as of version 1.5 the cache bind mount is compatible with ROM Manager
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Scripts
'source' is now available on github
http://github.com/Firerat/CustomMTD
errm, tbh I'm not all that clued up on it yet
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
asb123 said:
looks very promising
So, will i need to change the values everytime i flash a different rom? or can i just set them to a large size and everything will work?
Click to expand...
Click to collapse
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Firerat said:
most roms have a target of 90mb system ( DangerSPL )
so 90 2 config will basically give you an extra 28mb on data than you would have with stock DangerSPL MTD map
so yeah
90 2 is a good all rounder
Click to expand...
Click to collapse
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead. I remember you said something about it being a miltiple of 128K.
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Ace42 said:
is it okay if I make system 70mb?
The rom im using is only using 66 out of 90, i want more space for data instead.
Click to expand...
Click to collapse
yeap, should be fine
personally I would be tempted to use clockwork, since you can erase system ( part of partition options )
.img files can be found here
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
I don't recommend flashing via ROM Manager with CM5 or CM6
fastboot it over, or flash via recovery
I may be a little over cautious recommending a full wipe, but I have never had problems when system, cache and data are clean.
if you are 'growing' system make sure cache and data are clean
if your 'shrinking' make sure system is clean ( so 'hangovers don't mess up /cache or data )
asb123 said:
With this, could Devs stop skimping on stuff like wallpapers and ringtones or additional apps, and surpass the 90MB danger spl mark? It would seem so. Also, I do not make roms so I do not know how it works but if there is compression or lower quality stuff they would now be able to use up as much space as wanted correct?
Click to expand...
Click to collapse
yes, you can 'grow' or 'shrink' at will
just hope it doesn't get used to be lazy and not trim bloat
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
TheNewGuy said:
Hi firerat,
you mentioned once before something about market data on the cahe... or something so downloads would be ok if a certain partition was big enough?....something like that... I am having a prob that might be related since it started when I tried to change from default to system 80 5 for data. now I cant sign in to google and after flashing gaaps there is no market? everything else in the gaaps zip is there...? It could be google i know but i remembered you saying that somewhere.
Click to expand...
Click to collapse
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Firerat said:
I very much doubt it is related in anyway
/cache is where the market downloads apks to prior to install
it should be bind mounted to /sd-ext/cache or /data/cache if sd-ext is not mounted
your missing Market is related to something else
Click to expand...
Click to collapse
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
Because he bind mounted it.
Ace42 said:
On my sdcard, why were my market Dls going to /Sdcard/Download folder?
I never seen them go there before, I'm used to seeing them in /cache.
Click to expand...
Click to collapse
JAguirre1231 said:
Because he bind mounted it.
Click to expand...
Click to collapse
sorry for confusion
When I download stuff with dolphin HD it goes to /sdcard/download
maybe its different with stock browser
the cache bind mount is
added a few extra comments to make it easier to follow
/system/etc/init.d/06BindCache
Code:
#!/system/bin/sh
# check we don't already have a bind mount
# ( so if ran manually multiple times we don't end up with strange things happening )
if [ "`awk '/\/cache/' /proc/mounts |sed -n '$='`" -gt "1" ];
then
echo "cache already bind mounted"
echo `awk '/\/cache/' /proc/mounts`
exit
fi
# check if /sd-ext mounted, if yes then bind to /sd-ext/cache, if not /data/cache
if [ "`grep -q sd-ext /proc/mounts;echo $?`" = "0" ];
then
CacheDir=/sd-ext/cache
else
CacheDir=/data/cache
fi
# check we have something to bind mount, and create if not
if [ ! -d $CacheDir ];
then
install -m 771 -o 1000 -g 2001 -d $CacheDir
fi
mount -o bind $CacheDir /cache
# check dalvik-cache exists ( this is really for magics )
# so they don't end up in bootloop because dex files can not be created
if [ ! -d $CacheDir/dalvik-cache ];
then
install -m 771 -o 1000 -g 1000 -d $CacheDir/dalvik-cache
fi
actually, errm yeah it is d/l to /sdcard/downloads
not my doing
I guess cache really is pointless on froyo
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
speedysilwady said:
hey firerat great job bro! again ive been really busy and i still didnt get to try this or the earlier betas you made...hell i havent even tried a froyo rom yet. ima try this right now and let you know how it goes!
Click to expand...
Click to collapse
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Firerat said:
Froyo has been nice so far
but you may run into issues
for one the updater-script is actively 'kicking' NoneDanger
you can just remove the getprop checks
I have had problems booting cm5.0.8's kernel, I did get round it by compiling a new one from cm github,
I
'm not sure is cm6's kernel has the same issue
it does seem SPL related, I flashed Danger and it was fine, I plan to go back to NoneDanger and confirm it still doesn't work.
but figured that while I was on Danger I might as well put this (Custom MTD) through its paces with a DangerSPL
Click to expand...
Click to collapse
lol yeah i was just gonna say the get prop error occured lemme remove those asserts resign and see what happens
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
double edit: i get the same error for any rom i try to flash when i look at the logcat. the only difference is cm's latest nightly build rebooted on the g1, super e freezes at the g1 screen...ima try to modify the .txt to go back to the stock layout so i can nandroid my cachehacked cm5.08 back if not...idk what to do..
speedysilwady said:
hmm oddly everything flashed fine on the latest nightly build but when it gets past the g1 screen it keeps rebooting to recovery? ima rewipe and try again and see if i can get a logcat if it happens again
edit: no dice when i run logcat =/
-exec '/system/bin/sh/' failed: permission denied (13) -"
Click to expand...
Click to collapse
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Firerat said:
Odd, but at leasat the kernel is booting, I wasn't getting anywhere with cm5.0.8
It could be a general error
Which build are you using
I'm on a nightly, but I know Defcon works
If its still not working, try the older v1 version of boot patcher in lbcoders thread
I did change boot v1.1 to the script I use in the automtd one
I'm on the nightly 0704 (944 I think ) btw
Click to expand...
Click to collapse
noo this wasnt cm5.08 this was the latest nightly, same one youre 0704 on.
it got to the g1 screen and right when its abt to hit the boot animation it reboots.
i tried super e but it froze on the g1 screen
trying to get back to 67 67 for cache and system so i can nandroid but its weird that the logcat wont show no matter what rom i use.
I had a hard time searching for full NTFS read-write support for android. This thread is the fruit of that search..
I am posting it here with the hope that it will be useful for many more users of android.
Warning: I will take no responsibility for data loss or corruption that may occur on NTFS drives, though ntfs-3g has been known to be safe.
Q. Why would someone need this?
1. To support NTFS formatted partition(s) of USB-OTG mounted drives
2. To support NTFS partition(s) in microSD card
Q. What are requirements?
1. Fuse driver fuse.ko (compiled for the ROM kernel sources)
2. Latest ntfs-3g binary (see download below)
3. arm powered rooted android device (including SONY, Samsung, Motorola, HTC etc devices)
Q. Steps to get it working?
1. Push fuse.ko to /system or /data, chmod 644, and insmod
2. Push ntfs-3g to /system/xbin/, chmod 755
3. Mount USB OTG device (See script below)
For sdcard, only minor changes required!
4. Unmount as usual with "busybox umount /path/to/mount/"
Download
ntfs-3g
mount script
Update: My USB OTG Helper app has been updated to include this and more. Check it out!!
All-in-one for Sony Xperia 2011 devices -> Here
All-in-one for Samsung Galaxy SII -> Here
Reported working on Samsung Galaxy Note - link - thanks globalthrasher
Touble-shooting!:
For debugging..
1. Download this script and extract to sdcard
2. Connect your drive (pen drive, flash disk, powered HDD)
3. Run the script with script manager
4. Copy the output file from /sdcard/usb_otg_debug.txt and post here
Technical details
---------------------------------------------------------------------------------------------
As the ntfs driver in linux 2.6 kernel does not have write support, the only feasible way was ntfs-3g
Steps:
1. Fuse support (fuse.ko) to be compiled for the respective device from kernel source.
2. The ntfs-3g module was compiled with codesourcery toolchain (arm-none-linux-gnueabi)
Code:
./configure --enable-really-static -host=arm-none-linux-gnueabi
make
ntfs-3g: Main site | More details | Release History
NTFS Utils
NTFS Utils reference:
NTFS UTILITIES
==============
The ntfsprogs includes utilities for doing all required tasks to NTFS
partitions. In general, just run a utility without any command line
options to display the version number and usage syntax.
ntfsfix - Attempt to fix an NTFS partition and force Windows to check NTFS.
mkntfs - Format a partition with the NTFS filesystem.
ntfslabel - Display/change the label of an NTFS partition.
ntfsundelete - Recover deleted files from an NTFS volume.
ntfsresize - Resize NTFS volumes.
ntfsclone - Efficiently create/restore an image of an NTFS partition.
ntfscluster - Locate the owner of any given sector or cluster on an NTFS partition.
ntfsinfo - Show some information about an NTFS partition or one of the files or directories within it.
ntfsls - List information about files in a directory residing on an NTFS partition.
ntfscat - Concatenate files and print their contents on the standard output.
ntfscp - Overwrite files on an NTFS partition.
Click to expand...
Click to collapse
This is great. The fat32 4 GB size limit suck. Hope to get some exFAT support in the future also since exFAT is currently supported by both Mac and Windows 7,8.
Sent from my EVO 4G LTE
david279 said:
This is great. The fat32 4 GB size limit suck. Hope to get some exFAT support in the future also since exFAT is currently supported by both Mac and Windows 7,8.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
exFAT is working just fine on my SGS III (XXALE9)
Thnx Shardul,
This is great.
This is great news, imma give it some time before trying it though !
Will try it tomorrow
Great news. I was able to make ntfs work with my SG2 and now i hope to do the same with my sg3. Thanks!
This is indeed awesome news. Thanks for the head's-up.
Ciao
Great news....
Gonna try it soon...my galaxy fit would have external hardisk from now
Is it posible to include it when i compile with my own kernel rather than push the fuse.ko directly to the system?
Sorry for my bad english...
Sent from my GT-S5670 using xda premium
dodoik said:
Great news....
Gonna try it soon...my galaxy fit would have external hardisk from now
Is it posible to include it when i compile with my own kernel rather than push the fuse.ko directly to the system?
Sorry for my bad english...
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Ofcourse you can compile it as built-in rather than a module
anything for Transformer Prime?
working on galaxy nexus?
Great!
Anyone tried it on Samsung Galaxy Tab 10.1 (P7500)?!?
HERE the way to use it on SGS2 (I9100), I didn't try it.
I'll try on SGT10.1, but there is a way to auto-mount devices on connect?
See update in OP.. Easier to use with my updated app!
Edit: and auto start also!
shardul_seth said:
See update in OP.. Easier to use with my updated app!
Edit: and auto start also!
Click to expand...
Click to collapse
Thank you! I'll try tomorrow on both devices!
A couple of quick question, as I'm not sure about this, although "microSD" is mentioned in the first post...
1. Will this work for 64GB microSDXC expansion cards to be formatted as NTFS, usable and fully recognized? Or this is only for USB-OTG support for NTFS storage?
2. Does updated app (Helper) in the other thread take care of all the steps mentioned in original post when it comes to enabling microSDXC support mentioned above?
3. Has anyone successfully done this for Samsung Galaxy Note yet?
Sorry, if those are questions for obvious answers...
Thx.
globaltrasher said:
A couple of quick question, as I'm not sure about this, although "microSD" is mentioned in the first post...
1. Will this work for 64GB microSDXC expansion cards to be formatted as NTFS, usable and fully recognized? Or this is only for USB-OTG support for NTFS storage?
2. Does updated app (Helper) in the other thread take care of all the steps mentioned in original post when it comes to enabling microSDXC support mentioned above?
3. Has anyone successfully done this for Samsung Galaxy Note yet?
Sorry, if those are questions for obvious answers...
Thx.
Click to expand...
Click to collapse
1. Yes, just issue the commands on terminal
2. No
3. Not tried, but possible if kernel support
How can I obtain a working fuse.ko for my Samsung Galaxy Tab 10.1 (P7500) with pershoot kernel?
maxwarp79 said:
How can I obtain a working fuse.ko for my Samsung Galaxy Tab 10.1 (P7500) with pershoot kernel?
Click to expand...
Click to collapse
Just ask pershoot and I am sure he will oblige..
Edit: I think it is already enabled. See here
*/Haters gonna hate/*
ROM currently "DISCONTINUED". But, the init.rc tweak remains :fingers-crossed:
Hi to all those who are reading this! Lemme answer a few questions before I get started.
First of all, What kinda name is this???
TBH, I haven't yet thinked of a name for this... So, I just named it Stock ROM MOD
And, the name has been thought of! The name is... CyanicSense! Why this name? More details later
What does this do?
Though this is gonna be as stock as possible, the major feature that I had planned out for this is reversed-mount. As you might know, stock ROMs definitely do have mounts2sd (which might give some trouble in setting up), but, complete reversed-mount (i.e. the /sd-ext partition mounted as the /data partition as the int2ext script does, hasn't been achieved yet (on stock ROM). So, practically, this does that stuff.
How is this even possible?
Believe me. This ain’t no magic. Simple init.rc tweak… Mounting the mtdblk0p2 partition, which is basically the sd-ext partition as we better know it, in the /data folder does the trick. In CyanogenMod, this is done via the famous int2ext script…This is a more or less similar command, done during startup. Just make some changes to init.rc, and Voila!!! Your sd-ext is mounted in the /data partition.
So, why make a new thread for this???
Erm, but that ain’t the end of story here. I am planning on some more features. Current features are minimal, reversed-mount, and updated apps. Yep. Updated apps, not one but all of them. I can assure you that you will have every single update including Google Play Store v4.0.xx in this ROM. Also, applications which were basically “stub’s” have also been updated, so that you wouldn’t have to download any more apps. P.S. I have added a small file explorer, named “Explorer”, by Speed Software, the same people who brought about “Root Explorer”. Planning to replace it with OI File Manager in next build, if people prefer it
So, those were the two features of this ROM. Also, I am planning to work on some other features, which mainly include, init.d script support, and, removing bloatware. Currently, there are around 10 apps which I don’t use, and presume that most other users wouldn’t be using it either. So, I am gonna either make them uninstallable, or remove them completely, so that one can get more /system space More features might come up too. You can request new features, but… be reasonable
Is it safe???
I can’t answer that question, but, I am guessing the answer is yes. Why I think so??? Because I am using this as my daily driver for the past few days. Also, “reverse-mount” via scripts like int2ext, and mounts2sd do the same thing, so, I don’t think its gonna create problems
Will it make my phone laggy?
Not sure. Works fine in my Class 4, 8 GB memory card. Anything Class 4 and above, I assure you it wouldn’t “visibly” lag.
What about gaming?
Well, this is the part where you come in. I don’t use my phone for gaming, so, I can’t be sure whether Temple Run 2 is lagging, or its I who can’t play it properly But, one fact can be sure that Stock ROM isn’t always the best choice for gaming.
Anything else left?
Yeah… This build is… kinda heavy. 160+ MB is definitely too big for the “stock” ROM. It is because of all the updated apps which were included. I will try to make subsequent builds lighter, and more bloatware free
Now that Q&A Section is over, let’s get back to business. The simple init.rc tweak is explained in the next post.
Instructions:
Pretty basic. Wipe everything, except SD-Card, and flash the ROM.
The following video might give you a slight idea
P.S.: Recovery used: TWRP 2.5.0.0 (http://forum.xda-developers.com/showthread.php?t=2123503)
Bugs:
I need help with that If you encounter any bugs, please report immediately in this thread.
Downloads:
Link: http://www.mediafire.com/?8grcxx1rbngr6g2
Here is the link… 162 MB approx. Why so big? You are the typical TLDR case. Read the Q&A section above.
Beta Link: http://forum.xda-developers.com/showpost.php?p=41966646&postcount=19
Any issues, please post in this thread. I will try to fix it, ASAP
init.rc tweak that I used:
First of all, get a stock boot.img, and boot_img tools from here: https://github.com/sakindia123/boot-image-tools
Unpack it to some location safe, and, copy-paste the boot.img into this folder.
Then, run the following commands:
Code:
mkdir -p unpack
Code:
./unpackbootimg -i ./boot.img -o unpack
Code:
mkdir -p boot
Code:
cd boot
Code:
gzip -dc ../unpack/boot.img-ramdisk.gz | cpio -i
Code:
cd ../
Thus, you will have the ramdisk of your boot.img in the "boot" folder. Open up that folder, and open "init.rc" with any of your favourite editor.
Now, search for this line:
Code:
mount yaffs2 [email protected] /data
Replace that line with this:
Code:
mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
Now, I know you are confused... I too was, at first. So, let me make things clearer for you...
This is basically a mount command, which is executed in this order
mount [type of partition] [partition] [mount directory] [options]
So, the partition type is ext3, to be made more compatible with most devices.
/dev/block/mmcblk0p2 is the sd-ext partition.
/data is the folder we are going to mount the partition in.
nosuid and nodev: Allow an ordinary (i.e., non-root) user to mount the filesystem if one of his groups matches the group of the device.
noatime and nodiratime: Access timestamps are not updated when a file is read. So, there is no writing on the partition everytime the disk is read.
barrier=0
This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance penalty. The ext3 filesystem enables write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure.
data=ordered
Specifies the journalling mode for file data. Metadata is always journaled.
commit=15
Sync all data and metadata every 15 seconds.
noauto_da_alloc
does give a slight performance increase, especially when working with databases..
nouser_xattr
Support "user." extended attributes (or not).
errors=continue
Define the behaviour when an error is encountered.
Reserved, for screenshots
Yo, screenshots will occupy this post
Reserved,
in case i forgot anything to say
i admit, i typed this in a hurry...
credits are yet to be given, so... please don't flame here
Nice work bro.
For I understand it, is a stock ROM with memory script by you only, yes?
Sorry my english lvl xDDD....
Good job
Edit: well.. must say brother you did good work..
Rom is purely stock with only this tiny mod..
No bugs till now
This ain't no memory script.
TBH, I haven't even enabled init.d support yet. This is solely related to boot.img's init.rc... Which initiates reverse mount when you start your phone.
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Yes.
@rcane said:
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Stock ROM, version: 1.43.720.2
Brother.. here's a big problem..
The data folder of the Rom is now empty and all the app's apk files and app data installed can't be accessed using the root explorer..
And it is no where.. o can't find them..
Did you make a link to the data folder while mounting the ext partition to data..??
Sent from noob machines
I recommend using another application.
P.s. you will find it in the data folder only. It won't be in the sd-ext folder.
P.s. sorry for the short reply. I ain't at home currently
Sent from my HTC Explorer A310e using xda app-developers app
I used solid explorer..
I got them.. but on es file explorer.. the folder is still empty..
And also there is no sd-ext folder in root... Because you didn't make one..
Sent from noob machines
Did you enable Root Explorer or so...
AFAIK, even in the latest update, root exploration should be first enabled.
Press menu key, and in tools option, there will be the "root explorer" option, or a similar option.
Enable that, and then, you will be able to browse the data partition.
P.S.: if you don't get a superuser request, it will not work.
OK got it...
Thanks brother...
I got my mistake... it works now..:good:
Ohk, tiny flashable zip's coming up!!! HELP NEEDED!
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
me..
vineethraj49 said:
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
Click to expand...
Click to collapse
if u find something i can do , feel free to tell..
Thanks
artistaditya said:
if u find something i can do , feel free to tell..
Click to expand...
Click to collapse
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
I have this..
vineethraj49 said:
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
Click to expand...
Click to collapse
Sorry i dont have access to all the roms but i can give you information on Nextgen and jaggyrom..
--JaggyRom [specific version 3.2.1 lite]
1.) init.d support - yes
2.) apps2sd script used [without gui]
boot.img here- jaggyrom_boot.img
--NextGen [specific version 1.5]
1.) init.d support - yes
2.) mounts2sd script used [without gui]
boot.img here- nextgen_boot.img
Note to Beta testers! Cyanic Sense Beta is out!
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Screenshots
vineethraj49 said:
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Click to expand...
Click to collapse
Seems the OP forgot to add the "obligatory" screenshots
No worries here I am xD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Seems OP is working great,waiting for future updates!
TURBO BOOST - Prepare to feel the Heat!
use Cache and Data and System partition as Swap Space
You want a really fast Device without overclocking it, but you have problems???
The responsiveness does not satisfy you?
Your device (sometimes) lags?
You have got Sense restarts after heavy use or after browsing?
After several days your phone becomes slower and slower?
You don’t like to create a swap partition on your sdcard?
You just hate unused internal memory?
Code:
Triple Swap Mod v3.04
- Unofficially Added Support For The HTC One XL
- Updated Scripts For Support Of Evita
Older and official changelog
- [URL]http://forum.xda-developers.com/showthread.php?t=2145133[/URL]
Idea
Android devices have got RAM memory and internal eMMC memory. The eMMC is separated into several partitions (e.g. /system, /boot, /data, /cache). In former times of Android, the /cache partition was used for caching. Nowadays, in ICS times, the applications are using the /data partition to save information, libraries and cache data. So /cache is no longer used by the operating system or applications. Therefore, this partitions is empty except 4ext-logfiles, last recovery-log and an obligatory and empty lost+found directory. So we have got another 114 MB of space that can now be used as fast swap space for the kernel.
Also, the /system partition normally is not fully used - depending on the rom, a more or less amount of this area is free and unused.
As these areas all are internal memory, these swaps are faster, than a swap area on the sdcard!
TRY IT – YOU WILL BE CONVINCED AT ONCE!
If you are afraid of too many read/write requests to /cache, /data, /system, which may harm your eMMC memory of your phone, then don’t read further – we are not afraid, because there are also a lot of read/write requests to the /data partition as well and this is in Android “by design”. Furthermore there are devices, that have a preconfigured eMMC-swap space "by design", as for exaple the HTC One V.
Installation
Just download the Aroma-Installer, copy it to your sdcard, reboot into recovery and flash it as you would do with a new rom. It also has an option for removing, if you don’t like it – but we think, that this option is useless …
To determine the right size for the swap files, refer to the point “How can I check the size of the partitions” of the Hints/FAQs section below.
Advantages / Disadvantages
Disadvantages of a swap file on your sdcard:
A sdcard is always slower than internal memory
You may NEVER unmount the sdcard or connect your phone to your computer, because you then just kill your swap file – it is the same as pulling out the Ram of your running computer!
Disadvantages of a swap partition on your sdcard a.k.a. HARD SWAP:
A sdcard is always slower than internal memory
You will need a separate partition on your sdcard
You can connect the sdcard to your computer, but you cannot unmount and remove it without powering off your phone – you would kill your swap space immediately!
Disadvantages of a swap file in RAM - a.k.a. ZRAM:
This reduces the already low RAM memory
Leads to many low memory problems, like sense restarts and lags
Advantages of 98swap_ compared to the methods above:
It uses internal memory – so it is fast!
This memory is not available to the user (/cache and /system) – so it does not decrease any space given to the user
It does not use your sdcard in any way – so feel free to unmount and remove your sdcard whenever you like – also without powering off your phone!
Disadvantages of 98swap_cache
None - you name it!
Download :
https://www.dropbox.com/s/34h8vhzhd53t9rs/[UNOFFICIAL]TURBO BOOST MOD V3.04-AROMA.zip
Sent from my HTC One XL using XDA Premium 4 mobile app
★Can I use Turbo Boost?
Yes, you can! I have tested it with ViperXL JB 4.20 , & KickDroidXL v4.0.0, works with ElementalX v8.3.2
★How can I check the size and free space of the cache , data and system partition ?
Open a Terminal Program.
- type
Code:
df /cache
or/and
df /data
or/and
df /system
to get the state of the cache , data and system partition .
You will see some ting like this:-
http://s20.postimg.org/6ui8zt171/Df_cache.jpg
Or
- open Android System Info (available in Google Play), switch to system tab and open the “Memory” section. The first point “Download Cache Max” will show you the size of the partition and the available free space.
★How can I check my current Swap Space(s) and Size(s) ?
Open a Terminal Program.
- type
Code:
cat /proc/swaps
to get the state of all swap spaces separately .
You will see something like this:-
http://s20.postimg.org/yj4w7bo7h/cat_proc_swaps.jpg
Or
- type
Code:
free -m
to get total information of all swap spaces.
You will see some ting like this:-
http://s20.postimg.org/ghlr9iu6l/free_m.jpg
★How can I uninstall Turbo Boost?
Simple – just reboot into recovery and flash Harbir’s Aroma-Installer again – it has an option to remove the script-
★How can I Disable/Enable the Swap file ?
Just flash the script again with the fantastic Aroma installer from Harbir.
or (for EXPERTS only)
For temporarily disabling/enable it:
- open a Terminal program.
- Disable/Off:
Code:
su
swapoff /cache/swap/swap.img
or/and
swapoff /data/swap/swap.img
or/and
swapoff /system/swap/swap.img
- Enable/On:
Code:
su
swapon /cache/swap/swap.img
or/and
swapon /data/swap/swap.img
or/and
swapon /system/swap/swap.img
(it will also be enabled again by the script by a reboot)
For disabling the cache beyond a reboot:
- Go to the init.d directory and
- Disable the script by
Code:
cd /etc/init.d
chmod 644 98swap_cache_v300
or/and
chmod 644 98swap_data_v300
or/and
chmod 644 98swap_system_v300
- Enable the script by
Code:
chmod 755 98swap_cache_v300
or/and
chmod 755 98swap_data_v300
or/and
chmod 755 98swap_system_v300
★How can I change the size of my Swap file ?
Just flash the script again with the fantastic Aroma installer from Harbir.
★Can I use 98swap_cache together with the ZRAM option of my Kernel / ROM?
THAT WILL BE QUITE USELESS AS OUR MAIN PURPOSE IS TO FREE UP SOME MORE RAM.
But of course you can use it with ZRAM enabled. In this case you can reduce the ZRAM option to e.g. 50-75 MB and use 50-75 MB for 98swap_cache.
The command
Code:
cat /proc/swaps
(see above) will then display two swaps.
★Triple or Dual or Single Swap - which one is better and what is the difference?
We started to use /cache as swap space, because this space is not used on most phones. But on /cache you have only about 110 MB free space, even less with CM10.1 ROMs, and that might be insufficient for heavy usage. Our experience is, that e.g. with a Sense ROM, the phone needs about 150 MB of swap space. Now, this new version gives you the possibility to create two swaps, e.g. 100 MB in /cache and another one with 75 MB in /data and also gives you the possibility to create three swaps, e.g. 50 MB in /cache , another one with 75 MB in /data and 50 MB in /system . This is also sufficient for heavy usage.
★Is there a difference in performance to have one or two swaps or three swaps?
No. Two swaps will just give you the advantage to make better use of your free memory space, depending on your ROM.
★Which size shall I plan for the Swap Space?
We have very good experiences with Swap Spaces in total of 175 MB. This can now be made by two Swaps, e.g. 100 MB in /cache and 75 MB in /data or can now be made by three Swaps, e.g. 50 MB in /cache , 75 MB in /data and 50 MB in /system.
★My phone runs fast with Turbo Boost, but gets laggy again after a few days - what can I do?
This happens, when the phone needs all of the configured Swap Space - so the size is not sufficient in comparison to your usage of the phone. Just raise your Swap Space or configure a second Swap Space on a different partition - the new Aroma even supports Dual Swaps as well as Triple Swap.
support your device
to do this, we will need your help. At fist you have to install the script manually to confirm that it's working. In the second step we will need a few details of your phones to modify the aroma setup. Let's start with the first step:
Installation instructions:
Download the aroma
extract the file 98swap_cache_v300 from the folder \swap\cache\50\etc\init.d in the aroma
what to do:
Enter es-explorer and:
Go to es-explorer settings/root settings/check (root explorer ,up to root and mount file as writable).
Copy the script 98swap_cache_v300 to /system/etc/init.d
don't reboot!
Open a terminal session and get superuser rights with the command: Su
command: Cd /system/etc/init.d (now you are in the init.d folder, where the script is)
command: Chmod 775 98swap_cache_v300 (now the script has execution rights)
reboot
now:
Open a terminal session and get superuser rights with the command: Su
command: Cat /proc/swaps (shall show the new swap file /cache/swap/swap.img)
with es-explorer navigate to /data/swap and look into the log file swap_cache.log
please, sent delta-roh the logfile swap_cache.log via pm!.
If it's working, we have to do the second step:
The second step is, to include your device in the aroma; we need the internal device name and the mount point of the file systems. Do the following:
Open a terminal session
get a superuser shell with the command: Su
now the command:getprop ro.product.device
(that's the internal device name - i will need that name exactly)
now the command: Mount
(we need the mount points from /cache and /data and /system; if you do not find them, just use the command "mount > file" - this will write all output to "file" - then send me "file")
done!!!
If you have questions - feel free ...
Click to expand...
Click to collapse
Credit :
To The OP Of This Forum ---- http://forum.xda-developers.com/showthread.php?t=2145133
Is this something that will work with 4.4 Roms?
red3gunner said:
Is this something that will work with 4.4 Roms?
Click to expand...
Click to collapse
Yes it should work, I have not tested on any AOSP roms, but it should work since I've completly made it compatible with our device
Sent from my HTC One XL using XDA Premium 4 mobile app
Is this safe... I mean I have beastmode kernel so will it work with that
Sorry newb question
Sent from my HTC One XL using xda premium
paras33 said:
Is this safe... I mean I have beastmode kernel so will it work with that
Sorry newb question
Click to expand...
Click to collapse
If it supports init.d I'm 90% sure it will.
Sent from my HTC One XL using XDA Premium 4 mobile app
After testing it for more than 7hrs i can say that Prefomance has improved without any bugs but facing a slightly higher battery drain while using triple swap.
coldfear00 said:
After testing it for more than 7hrs i can say that Prefomance has improved without any bugs but facing a slightly higher battery drain while using triple swap.
Click to expand...
Click to collapse
With this mod it gives your device a way to use swap memory when Ram is running low.. so with swap being on the emmc ( system, data, and cache ) the phone is constantly r/w so of course there will be slight decrease in battery... I could release a whole new mod to counteract the effect of battery drain, but then I'd be giving away to much of KickDroidXL Newest features.
Sent from my HTC One XL using XDA Premium 4 mobile app
I tried installing this mod on the latest miui but it hookup forever without telling me successful or not, I had to force reboot.
Sent from my HTC One XL using XDA Premium 4 mobile app
kemihansome said:
I tried installing this mod on the latest miui but it hookup forever without telling me successful or not, I had to force reboot.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What it hanged in recovery?
Sent from my HTC One XL using XDA Premium 4 mobile app
24ky said:
What it hanged in recovery?
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As in, It takes up to 30mins without finishing installation,
I had to force reboot
kemihansome said:
As in, It takes up to 30mins without finishing installation,
I had to force reboot
Click to expand...
Click to collapse
Had the same prob & here's the solution, wipe cache n dalvik then reboot back into recovery then start the installer without wiping anything & wola everything works fine.
kemihansome said:
As in, It takes up to 30mins without finishing installation,
I had to force reboot
Click to expand...
Click to collapse
It installs for me perfectly
Sent from my HTC One XL using XDA Premium 4 mobile app
24ky said:
It installs for me perfectly
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same problem. Left it for an hour, and still not done
Sent from my HTC One XL using Tapatalk
pandasa123 said:
Same problem. Left it for an hour, and still not done
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
Should not take more than 30secs
pandasa123 said:
Same problem. Left it for an hour, and still not done
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
Okay your having problems flashing in recovery? What recovery ? (TWRP, cmw, or phills ) also in recovery make sure system is mounted in mount section if so , choose reboot recovery and try flashing..... I use official twrp 2.6.3.0 I believe and when I've ran into that issue I just force reboot but upon boot I enter it in hboot and go to recovery that way and it works for me
Sent from my SPH-L710 using xda app-developers app
Working fine here... Noticing performance improvement... Waiting to test further
Sent from my HTC One XL using xda premium
paras33 said:
Working fine here... Noticing performance improvement... Waiting to test further
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SPH-L710 using xda app-developers app
I was going to release this as a ROM, but as you may know Rox is pretty busy these days so he hasn't replied to me yet to my request for permission to fork CM11 (if you're reading this, don't feel offended and take your time!) so I chose to reward the DIYers by releasing the differences from it... and of course devs that share my view of the ideal ROM will hopefully reuse them ~
So yes, this is basically an expansion pack for CM11. After downloading the sources, just before `brunch codina` you extract the zip over them.
What does this do anyway? What's included?
The main feature is that partitions 8 and 9 (sdcard/UMS and preload/HIDDEN) are ignored. You can completely delete them and get a 3 GB /data partition for ART or whatever. Unlike swapping storages (or not swapping them!), this doesn't confuse apps written with only one media partition available.
Camera photos, your songs, OBBs and ASECs from apps that use them, archived apps, ... all go to the card you can always remove from the phone if you want to sell it or need service (keep in mind though it's not 100% sure that nothing on it never ends up on NAND), likely formatted in FAT32 with loads of multiplatform undelete tools available, easy to swallow if you feel the CIA is nearby... (do not try this at home)
There are also some other minor tweaks that I consider a core part of my Android experience, see the text file in the zip for more details or just read this box ↓
Code:
External SD only (on sdcard0) with [STRIKE]ASEC, apps2sd,[/STRIKE] OBB, camera, card hotswap, mass storage all working
/preload disabled
device/samsung/codina/overlay/frameworks/base/core/res/res/xml/storage_list.xml
device/samsung/codina/rootdir/*
device/samsung/u8500-common/common.mk
packages/apps/DeviceSettings/src/com/teamcanjica/settings/device/fragments/AdvancedFragmentActivity.java
packages/apps/DeviceSettings/res/xml/advanced_preferences.xml
BUG: Mass storage mode creates an empty drive, I suspect this can be fixed by playing with the LUN setting in u8500 boardconfig
"battery saving" profile limits clock to 800MHz
device/samsung/codina/rootdir/*
200dpi default resolution
device/samsung/codina/system.prop
Default screensaver after 2 minutes
device/samsung/u8500-common/overlay/frameworks/base/packages/SettingsProvider/res/values/defaults.xml
Browser autocomplete window size increased
packages/apps/Browser/res/values/integers.xml
So if you want to have a look you can grab it there!
Good job!
However i have two suggestions:
1. You should separate "storage" part from other tweaks... It's great that we have somebody with creativity but not everyone wants to apply all that tweaks (and even less will want to separate that tweaks from storage part (considering that potentially interested in your patch are very few in count)
2. Do you have github account? is "githubish" version of your tweaks?
I played a bit with storages in that overlay (storage list) some time ago, but no success on that time... so i'm really interested in those changes.
When i try to compile stock OC kernel - i had to repartition my long time used custom partition scheme. And then i tried to recreate it without UMS partition but it ended with "no sd card" issue (you cannot take pictures for example) after memory swap... So i need something like your patch, but i don't have time to separate it from other tweaks...
judas1977 said:
Good job!
However i have two suggestions:
1. You should separate "storage" part from other tweaks... It's great that we have somebody with creativity but not everyone wants to apply all that tweaks (and even less will want to separate that tweaks from storage part (considering that potentially interested in your patch are very few in count)
2. Do you have github account? is "githubish" version of your tweaks?
I played a bit with storages in that overlay (storage list) some time ago, but no success on that time... so i'm really interested in those changes.
When i try to compile stock OC kernel - i had to repartition my long time used custom partition scheme. And then i tried to recreate it without UMS partition but it ended with "no sd card" issue (you cannot take pictures for example) after memory swap... So i need something like your patch, but i don't have time to separate it from other tweaks...
Click to expand...
Click to collapse
1- Just remove all the unrelated files, I listed the names for a reason (to leave maximum clock at 1 GHz, in device/samsung/codina/rootdir/init.samsungcodina.rc you can see 2 pairs of lines near the end with "scaling_max_freq" to be removed)
storage_list.xml → the highest level part, basically defines the functionality of settings/storage
fstab.samsungcodina → remove internal SD, change voldmanaged= part of external to match mount name in storage_list.xml, if you didn't rename it just change "sdcard1:auto" to "sdcard0:auto"
init.samsungcodina.rc → remove 3-line block related to internal SD, edit name and paths to fit previous configurations
u8500_common → remove swap option from build.prop
AdvancedFragmentActivity.java → remove swap feature from NovaThor Settings
advanced_preferences.java → remove swap option from NovaThor Settings
2- Nope, I don't know how to use git (or any equivalent) and if I was to add the extreme confusion of configuration files assembled from multiple places and quite illogical arrangement of stuff in the sources to a friendlier but completely different system as seen in the repos...
(and github doesn't seem to offer what I would be most interested in - highlighting differences from a previous version)
judas1977 said:
Good job!
However i have two suggestions:
1. You should separate "storage" part from other tweaks... It's great that we have somebody with creativity but not everyone wants to apply all that tweaks (and even less will want to separate that tweaks from storage part (considering that potentially interested in your patch are very few in count)
2. Do you have github account? is "githubish" version of your tweaks?
I played a bit with storages in that overlay (storage list) some time ago, but no success on that time... so i'm really interested in those changes.
When i try to compile stock OC kernel - i had to repartition my long time used custom partition scheme. And then i tried to recreate it without UMS partition but it ended with "no sd card" issue (you cannot take pictures for example) after memory swap... So i need something like your patch, but i don't have time to separate it from other tweaks...
Click to expand...
Click to collapse
Hmm.. Im thinking the author whom you said stopped working on oc stock kernel is you :/
Sent from my GT-I8160 using Tapatalk
Ryccardo said:
1- 2- Nope, I don't know how to use git (or any equivalent) and if I was to add the extreme confusion of configuration files assembled from multiple places and quite illogical arrangement of stuff in the sources to a friendlier but completely different system as seen in the repos...
(and github doesn't seem to offer what I would be most interested in - highlighting differences from a previous version)
Click to expand...
Click to collapse
github is quite logical and well organized . Beside of this, it would be easier to manage your patch when files that you modified will be modified by @Rox or other TC member: You will have to make your patches again or accept that their changes will be overwritten by your patch...
When you click on last (or any) commit you'll see the difference in code it made, btw.
And I try to implement your changes to github code as a commit (should be easy if the sources weren't changed in the meantime).
teddytsen said:
Hmm.. Im thinking the author whom you said stopped working on oc stock kernel is you :/
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Well, I never lied on that subject, never .
UPDATE:
https://github.com/judas77/android_...mmit/139b9d446ea13299b311a82c1973c177d24256e2
OI just compiled new carbon build using your tweaks...
Everything seems to work good (i was really happy), but then...
It seems you cannot install (from google play, from Titanium backup) apps that write additional data on SD(1?):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
judas1977 said:
OI just compiled new carbon build using your tweaks...
Everything seems to work good (i was really happy), but then...
It seems you cannot install (from google play, from Titanium backup) apps that write additional data on SD(1?):
Click to expand...
Click to collapse
Just checked a little better, there is a problem with ASEC creation (vold doesn't create disk images claiming something is mounted read only), cheap workaround is to use Link2SD or `pm` to force everything to install to internal storage
@judas1977 I think I found the problem, I should have confirmation in 5-6 hours
Ok, I'll wait for the info...
judas1977 said:
Ok, I'll wait for the info...
Click to expand...
Click to collapse
keeping all other changes I sent you, in fstab try changing the microSD line (sdi0[...]mmc1) so that it ends with noemulatedsd
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/mmcblk0p3 /system ext4 ro,noatime,errors=panic wait
/dev/block/mmcblk0p2 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p4 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p7 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
/dev/block/mmcblk0p5 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=/efs/metadata
# Vold managed volumes
/devices/sdi0/mmc_host/mmc1/mmc1 auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
# Recovery only
/dev/block/mmcblk0p15 /boot emmc defaults recoveryonly
# ZRAM
/dev/block/zram0 none swap defaults zramsize=104857600
I haven't managed to try it on last evening's Omni or CM11 as they both got stuck on bootanimation and I can't say if it's this mod or something from 4.4.3 still unpolished...
:good: :good: :good:
That did it. with "noemulatedsd", everything works fine including ASEC (and thus apps2sd)... the job is done :highfive:
So this should do the job?
https://github.com/judas77/android_...mmit/63aa54bd7e0465f8b3881184fd237188657c30ab
judas1977 said:
So this should do the job?
https://github.com/judas77/android_...mmit/63aa54bd7e0465f8b3881184fd237188657c30ab
Click to expand...
Click to collapse
Nope, noemulatedsd goes at the end (after voldmanaged=sdcard0:auto) :fingers-crossed:
Of course, that's because of that long lines
Wysłane z mojego GT-I8160 przy użyciu Tapatalka
judas1977 said:
Of course, that's because of that long lines
Click to expand...
Click to collapse
well, the latest diff you posted is wrong
Yes, i know
Wysłane z mojego GT-I8160 przy użyciu Tapatalka
So if i install that patch, i will not see again the error "could not install on usb storage or sd card" ?
There is patch only for disabling internal sdcard or i have to apply patch with tweaks?
Thanks
nikolas1274 said:
So if i install that patch, i will not see again the error "could not install on usb storage or sd card" ?
There is patch only for disabling internal sdcard or i have to apply patch with tweaks?
Thanks
Click to expand...
Click to collapse
You mean the bug where you swap storages but Google Play still checks the free space from the internal memory?
No problem with this method :good:
Ryccardo said:
You mean the bug where you swap storages but Google Play still checks the free space from the internal memory?
No problem with this method :good:
Click to expand...
Click to collapse
Yes i am talking for this.
Thanks
Hi!
As I see, TeamCanjica has changed the structure of the init scripts recently, so the changes you've made in "init.samsungcodina.rc" have to be applied in "u8500-common/rootdir/init.u8500.rc"
Bela