Hi! With 200 apps installed i move this cache to /dev with this script. O1 startup 2-2.5 minutes while recreating dalvik-cache directory. Runs fast and 70-80MB is free on sdcard or phone memory. SDCard life is loooong! Run this on Mik_os CyanogenMod Beta 3.1-4 without A2SD or uninstalled A2SD.
P.S. If you use A2SD then first: 1-locate where is dalvik-cache creating. 2- move it to phone. 3- remove (.txt) from attached file. 4- add script into /system/etc/init.d with root explorer and change right permission
Does this really works? I'm really damn curious, but I don't want to mess with it right off the bat without you telling me how does it performs.
Yes it works! About battery eating... No more from stock mik_os Cyanogen beta4, and RAM 240-250Mb after phone is fully loaded. Phone is loading after Homescreen is visible about 2mins...so dont touch him- wait for cache is genering
I just did it, couldn't resist, and yes it worked. I only have 17 mb worth of "dalvik-cache" files anyway, but I guess having it on /dev provides more performance than having it on SD card (unless the card is a class 10).
"I only have 17 mb worth of "dalvik-cache" files anyway"- on SdCard? delete it...! Sorry for bad english...
pomka78 said:
"I only have 17 mb worth of "dalvik-cache" files anyway"- on SdCard? delete it...! Sorry for bad english...
Click to expand...
Click to collapse
Not on sd-card anymore ofc...Don't worry everything is working as it should, I know my stuff
For possible a2sd - dalvik to sd users this is what I did:
1. Moved dalvik back to data (with darktremors I just typed a2sd nocache in the terminal);
2. Rebooted;
3. Wiped dalvik-cache at recovery;
4. Booted;
5. Copied this script into init.d;
6. Rebooted;
7. ??
8. Profit.
Yes. The /dev subdirectory size is 200mb and not used for user!? Not right...;-)
I'll try move to /dev /data/dropbox- this is trash directory?
pomka78 said:
Yes. The /dev subdirectory size is 200mb and not used for user!? Not right...;-)
I'll try move to /dev /data/dropbox- this is trash directory?
Click to expand...
Click to collapse
As far as I know /dev isn't used by "us" the user, but I don't know much more about it.
What do you want to move to /dev? I didn't understand completely.
/data/dropbox -- this is temporary files from What?
I have the dropbox app and I dont have that folder, but your path belongs to dropbox I bet
/data/system/dropbox - - another folder with some files
Doesn't this mean the dalvik-cache is rebuilt on every boot?
Sent from my LG-P500 using Tapatalk
Yes its rebuild, but into fast memory,not use sdcard
Hi friends,
i would say: the idea to put the cache in ram is good, but /dev is the VERY,VERY WRONG place to do that! Why? the /dev folder is specially ONLY for devices and user-data or other system data has not a place in it.
To work better with this idea:
create a new folder in /system or /data and mount a tmpfs in it. after do this, link /data/dalvik-cache to this this created folder and all is fine
tmpfs is nothing other than a loop device, specially for temporay data store when system is running. on shutdown, the tmpfs gets automaticly unmounted.
But /dev - is a "devices" ,they reinitialize every boot phone. what's wrong be if cache would be reinitializing in their own directory.
3 days - flight normal...
pomka78 said:
But /dev - is a "devices" ,they reinitialize every boot phone. what's wrong be if cache would be reinitializing in their own directory.
3 days - flight normal...
Click to expand...
Click to collapse
yes, "/dev" are devices, and dalvik-cache isn't a device and doesn't contains devices - so this folder must be placed in another place in file system.
It works, there is no problem - but it's not conform to a FHS standard (i know, android has it's own standard...)
I'm with Andy on this one, /dev is not the place to do this. It's not a normal directory and should be left alone. I think Andy's solution is the way to with this. And I'm still wondering what the actual benefit will be apart from saving space.
Sent from my LG-P500 using Tapatalk
FHS standard? Not hear about... i try to change script. Maybe resize /cache partition? How? I'll try
pomka78 said:
FHS standard? Not hear about... i try to change script. Maybe resize /cache partition? How? I'll try
Click to expand...
Click to collapse
FHS = Filesystem Hierarchy Standard. It was invented to have a clear file system on Linux, and android is a similar system to Linux/*NIX.
Clear means, that developers shouldn't install binaries/libs or scripts wild around the system - so this standard gives a way to organize files in a clear way
/bin = essential binaries needed by system
/boot = system boot related files (kernel,bootloader config,static binaries for boot time)
/dev = system device drivers
/etc = system wide configuration files
/lib = essential system libraries (libc...)
/media = mount point for media like CD-ROM or USB drives
/mnt = mount point for internal mounts (mount other harddrives in system)
/opt = optional installation files or temporary (test-)installtion
/sbin = essential system service binaries
/tmp = temorary files (content of this folder gets removed before every boot, but is a normal directory node - here you can create a folder and mount a tmpfs in)
/usr = secondary file hierarchy, provided for installtion files/applications & other libraries not needed by system to boot to a shell
/var = variable data here you can create a folder and mount a tmpfs in
Hope, this information helps some
Hmm, there's quite good information here, I didn't know that much about FHS... is tmpfs loaded into RAM as well?
EDIT: Yes it is loadaded into RAM... should've go search before asking.
Related
I am not responsible for anything you do to your phone. If this goes wrong, it's not my fault. Read the whole post, and the last few pages of the thread. This will get you up to speed. Backup everything! Twice. No, I'm not joking. Do a nandroid, then do a titanium backup.
Important note! Ext4 does NOT work with ClockworkMOD 2.5.x. Nandroid backups will not work unless you upgrade to CWM 3! (data2ext4)
Greetings, earthlings! I have got a new version for you! Almost. Read this: http://forum.xda-developers.com/showpost.php?p=11931210&postcount=341
Update 26/01/2011
Ok, so someone asked about continuing support for ext2. So I will. Ain't I nice. Both scripts are updated, and should have improved performance, as well as a bugfix With both you don't need to start over, just flash the zip and you're done. Backup anyway (of course).
EXT4 version:
Yes, ext4 is slower in benchmarks. No, it doesn't have a real world impact. Not that I can see anyway. As always feedback is welcomed. I really mean that, if your phone genuinely becomes slower, let me know.
The zip is named data2ext4-V4.zip
Instructions (new users):
Ensure that mmcblk0p2 isn't mounted anywhere. You can do this by running "mount|egrep mmcblk0p2". If that returns anything, the ext partition is mounted. Unmount it using "umount directory/that/mmcblk0p2/is/mounted/to". Most often it's mounted to /sd-ext; in this case run "umount /sd-ext"
Format the ext partition to ext4:
Code:
mke2fs -m0 -b4096 /dev/block/mmcblk0p2
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -yf /dev/block/mmcblk0p2
tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
tune2fs -O ^has_journal /dev/block/mmcblk0p2
Flash the attached zip and reboot to normal mode
Open up a terminal or use ADB to execute "data2ext --enable"
Reboot
Click to expand...
Click to collapse
Intructions (upgrading from ext2):
This should keep all your existing data. Back it up anyway
Disable data2ext
Upgrade to ext4 thusly:
Code:
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -yf /dev/block/mmcblk0p2
tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
tune2fs -O ^has_journal /dev/block/mmcblk0p2
Flash the attached zip
Enable data2ext
Click to expand...
Click to collapse
EXT2 version:
This is rather simpler to set up, but is not as safe. It is slightly faster though
The zip is named data2ext2-v7.zip
Flash the zip
ensure /dev/block/mmcblk0p2 isn't mounted anywhere
Format the ext partition to ext2 with a 4KB block size
Code:
mke2fs -m0 -b4096 /dev/block/mmcblk0p2
Run this:
Code:
data2ext --enable
Reboot and enjoy
Click to expand...
Click to collapse
1st boot will take a while, it's copying stuff across.
Java on my PC sucks (it won't work), and I still can't sign zips. You'll live, just toggle signature verification in CWM
Semi-disclaimer:
This is my first real foray into scripting. I am still learning, so this is not as good as it could be. I release this to you to give me an incentive to make it better. I still need to look into mount options and the like, I'm sure this can go faster. Once again, I would class this as beta quality.
What is data2ext?
The phones internal memory is divided into several partitions. The 3 key ones are /system, /data and /cache. The rest we don't need to worry about too much. /system is where the ROM lives. By default it's read only (regardless of S-ON or S-OFF). All the data on our phones (apps, app data, game progress and a few other bits and bobs) is stored on /data. We have a pitiful amount of storage on /data (about 190MB), so we quickly run out when installing apps. 1 solution is to move /data/app (this is where most of the apps are stored) to a partition on your SD card (formatted to ext). But the internal memory still fills up, as anything not in /data/app stays on internal (caches, data and shizz). Other solutions have arisen, like moving dalvik-cache there to the ext partition too. But with the advent of fast SD cards it became possible to move the whole data partition to the ext partition. So people did; this means that the internal memory is barely used (aside from a few bits here and there, they're symlinked back to their original location).
Click to expand...
Click to collapse
It ain't workin'!
Ok. Get a logcat, and use pastebin to paste it here. Then we might be able to work it out, ye?
To use logcat:
Download this and extract it to a known location. Navigate to that folder, and press SHIFT while right-clicking. In the menu there should be a "Open command window here" option. Click it. Now type "adb logcat". Press CTRL+C to end the output. Right click and press mark, then click and drag over all the text and hit ENTER. It's now copied to the clipboard. CTRL+V to paste it somewhere... To debug issues with this script I need the first 5-10 seconds of the boot process.
To make life easier, I need the bit between "--START OF SCRIPT, PASTE LOGCAT FROM HERE ON!--" and "I DON'T NEED ANY MORE OF THE LOGCAT!"
Click to expand...
Click to collapse
Changelog
Version 1
initial release
Versions 2 through 4 were internal testing ones
Version 5
Fixed dalvik-cache rebuild
Made more likely to work
EXT4(v3) version initial release
EXT4 V4
Improved performance
Bugfix (unmount /sd-ext if it exists)
EXT2 V7
Improved performance
Bugfix (unmount /sd-ext if it exists)
Hereafter I shall rename these to make managing this changelog easier
Click to expand...
Click to collapse
Credits:
BlaY0
Anyone who's ever made data2ext scripts. I looked at a few
Click to expand...
Click to collapse
signd version attached
edit: removed
nooob.
but could you also make just ap2sd for ext3 ?
Sent from my Legend using Tapatalk
Noob?! Meh, s'pose I am. What can you do, eh?
http://krikun.ru/2010/10/28/app2sd-for-cyanogenmod-6-x/
TheGrammarFreak said:
Noob?! Meh, s'pose I am. What can you do, eh?
http://krikun.ru/2010/10/28/app2sd-for-cyanogenmod-6-x/
Click to expand...
Click to collapse
i tried that one but doesn't work on gingerbread cm7
OlegKrikun :
"Now cm7 exp. builds not support run start up scripts from /etc/init.d =( when is fix, I publish app2sd for cm7"
noob=== my noob wish.
I don't like to ask questions, so I try to introduce myself into those new things. But I need a confirmation if my theories are correct
1. Google's app2sd is kinda stupid. It uses the normal fat partition on your SD, correct?
2. The a2sd linked here copies all the stuff from /data/app to /sd-ext/app and remounts /data/app to /sd-ext/app
So the Phone means the App is stored on the Phone Memory but in real its stored on the sd.
Do I have to wipe everything after flashing the script. What happens to apps that are currently moved to the SD (by Google Apps2SD). Can I just copy them "to phone" again and they are inside the sd-ext then?
3. Data2ext => Speedup because everything from /data is now on the extfs on SD. Apps are also included, as they are located in /data/app so its has a2sd integrated, right?
EDIT: Damn, now I have to ask a question...
What's stored inside the dalvik-cache? I don't know much about dalvik, thats my biggest problem with android ...
Is it good to move it also to sd-ext with the a2sd script?
fabi280 said:
I don't like to ask questions, so I try to introduce myself into those new things. But I need a confirmation if my theories are correct
1. Google's app2sd is kinda stupid. It uses the normal fat partition on your SD, correct?
2. The a2sd linked here copies all the stuff from /data/app to /sd-ext/app and remounts /data/app to /sd-ext/app
So the Phone means the App is stored on the Phone Memory but in real its stored on the sd.
Do I have to wipe everything after flashing the script. What happens to apps that are currently moved to the SD (by Google Apps2SD). Can I just copy them "to phone" again and they are inside the sd-ext then?
3. Data2ext => Speedup because everything from /data is now on the extfs on SD. Apps are also included, as they are located in /data/app so its has a2sd integrated, right?
EDIT: Damn, now I have to ask a question...
What's stored inside the dalvik-cache? I don't know much about dalvik, thats my biggest problem with android ...
Is it good to move it also to sd-ext with the a2sd script?
Click to expand...
Click to collapse
1. Correct
2. No wipe needed for a2sd or this data2ext. Any app on what the phone believes to be internal memory is in fact sd-ext
3. Correct
Dalvik-cache is a shedload of dex files, quite important. The bug with re-creating it on every boot isn't major enough for me to worry about for now, as I don't think it affects anything other than the startup time. I need to investigate this, so be careful if you use this mod. My worry is that it's due to data being lost somewhere
When I used a2sd I had dalvik-cache on the sd card, but then I have a fast SD card. It can slow things down.
Anyhoo, I would like this thread to be for testing data2ext, not asking questions about a2sd. I have made this to help me learn how these things work, so feedback is welcomed. If anyone has tested this on CM6 then please let me know. And can you also post feedback about the dalvik-cache issue.
gyroing said:
i tried that one but doesn't work on gingerbread cm7
OlegKrikun :
"Now cm7 exp. builds not support run start up scripts from /etc/init.d =( when is fix, I publish app2sd for cm7"
noob=== my noob wish.
Click to expand...
Click to collapse
/system/etc/init.d is where this is run from. It works on CM7
@Grammar,
thx for your work!!! it works very good on my phone. ext2(1 gb) partition as ext3 formatted. i have the "signed" zip from exicar(thx) installs....
lwiss
quadrant: 1686
card: 8gb class 6
rom-version: CM 7 | Gingerbread, 01/03
TheGrammarFreak said:
Anyhoo, I would like this thread to be for testing data2ext, not asking questions about a2sd. I have made this to help me learn how these things work, so feedback is welcomed. If anyone has tested this on CM6 then please let me know. And can you also post feedback about the dalvik-cache issue.
Click to expand...
Click to collapse
Sorry for my Off-Topic-Questions.
I'll try it for you on CM6.
How fast has it to be? I've got a 8GB Class 6 Card, is it enough?
EDIT: Note to myself, never read an article description on amazon on a second screen while writing a reply.
It's a class 4, I looked for a Class 6 on Amazon -_-
But I'll try it anyway..
lwiss said:
@Grammar,
thx for your work!!! it works very good on my phone. ext2(1 gb) partition as ext3 formatted. i have the "signed" zip from exicar(thx) installs....
lwiss
Click to expand...
Click to collapse
What version of CM? And it's not my work, it's BlaY0's. I just made his script work on CM
fabi280 said:
Sorry for my Off-Topic-Questions.
I'll try it for you on CM6.
How fast has it to be? I've got a 8GB Class 6 Card, is it enough?
Click to expand...
Click to collapse
It's not the most off-topic I've seen. Look at the CM experimental build thread . I also have 8GB class 6. I get 1600+
Stupid question. Where to enable data2ext in cyanogenmod settings?
What version of CM?
Click to expand...
Click to collapse
from ali ba (thx)
CM 7 | Gingerbread, 01/03 (with gapps)
lwiss
FUXAS said:
Stupid question. Where to enable data2ext in cyanogenmod settings?
Click to expand...
Click to collapse
If you don't even read the first post I'm not gonna help you. If I haven't made the point clear enough:
This is in testing. There is a major bug where dalvik-cache is re-built on every reboot. This is not a good thing. I would advise that you not use this unless you know what you're doing
fabi280 said:
Sorry for my Off-Topic-Questions.
I'll try it for you on CM6.
How fast has it to be? I've got a 8GB Class 6 Card, is it enough?
EDIT: Note to myself, never read an article description on amazon on a second screen while writing a reply.
It's a class 4, I looked for a Class 6 on Amazon -_-
But I'll try it anyway..
Click to expand...
Click to collapse
Class 4 is definitely too slow, at least on CM6.
I will not provide a Quadrant Benchmark because my Phone is waaay too slow now. It really lags everywhere.
First Start:
Code:
I//system/xbin/run-parts( 59): Initiating Data2EXT...
I//system/xbin/run-parts( 59): Waiting for SD card to settle...
I//system/xbin/run-parts( 59): Executing file system check...
I//system/xbin/run-parts( 59): /dev/block/mmcblk0p2: 11/65664 files (0.0% non-contiguous), 4451/262144 blocks
I//system/xbin/run-parts( 59): Mounting /dev/block/mmcblk0p2 to /data...
I//system/xbin/run-parts( 59): EXT partition /dev/block/mmcblk0p2 mounted on /data...
I//system/xbin/run-parts( 59): First time initiation, copying files to EXT partition...
I//system/xbin/run-parts( 59): Data2EXT enabled...
I//system/xbin/run-parts( 59): Setting read-write /system overlay...
I//system/xbin/run-parts( 59): Checking for kernel aufs support...
I//system/xbin/run-parts( 59): No aufs driver present in kernel, trying to load aufs module...
I//system/xbin/run-parts( 59): Can not load aufs module, aborting...
Second start:
Code:
I//system/xbin/run-parts( 59): Initiating Data2EXT...
I//system/xbin/run-parts( 59): Waiting for SD card to settle...
I//system/xbin/run-parts( 59): Executing file system check...
I//system/xbin/run-parts( 59): /dev/block/mmcblk0p2: Entry 'CheckinService.xml' in /data/com.google.android.gsf/shared_prefs (25081) has deleted/unused inode 25583. CLEARED.
I//system/xbin/run-parts( 59): /dev/block/mmcblk0p2: Entry 'EventLogService.xml' in /data/com.google.android.gsf/shared_prefs (25081) has deleted/unused inode 25074. CLEARED.
I//system/xbin/run-parts( 59): /dev/block/mmcblk0p2: Entry 'googlesettings.db-journal' in /data/com.google.android.gsf/databases (25087) has deleted/unused inode 25564. CLEARED.
I//system/xbin/run-parts( 59): /dev/block/mmcblk0p2: 1834/65664 files (0.4% non-contiguous), 46535/262144 blocks
I//system/xbin/run-parts( 59): /dev/block/mmcblk0p2: 1834/65664 files (0.4% non-contiguous), 46535/262144 blocks
I//system/xbin/run-parts( 59): Mounting /dev/block/mmcblk0p2 to /data...
I//system/xbin/run-parts( 59): EXT partition /dev/block/mmcblk0p2 mounted on /data...
I//system/xbin/run-parts( 59): Data2EXT enabled...
I//system/xbin/run-parts( 59): Setting read-write /system overlay...
I//system/xbin/run-parts( 59): Checking for kernel aufs support...
I//system/xbin/run-parts( 59): No aufs driver present in kernel, trying to load aufs module...
I//system/xbin/run-parts( 59): Can not load aufs module, aborting...
I can send you the complete outputs for both starts (got em till the UI was visible)
EDIT: But is the Class4 Card fast enough to handle a2sd (maybe with Dalvik Cache)?
There are several factors affecting read/write speed to/from SD card not just class:
partition alignment
partition type
format options
mount options
readahead settings
etc.
Not going to try and use it yet, but I'm curious now. When using this, you're automatically having all of your apps on your sd card and the app2sd feature isn't needed anymore, right? And your phone gets a speed boost when using it?
m1schi said:
Not going to try and use it yet, but I'm curious now. When using this, you're automatically having all of your apps on your sd card and the app2sd feature isn't needed anymore, right? And your phone gets a speed boost when using it?
Click to expand...
Click to collapse
Apps on sd-ext = yes
Speed Boost, sometimes yes, sometimes its laggy as hell
Sent from my HTC Legend using XDA App
Stupid question. How do you guys get 1600+ in Quadrant on CM7?
For me Quadrant is not finishing tests due to the 3D graphics not working. But even if it'll work, I don't think I'd get so much. On CM 6.1 oc'ed to 787, I'd hardly get 1150. Is it just due to overclocking or this data2ext is speeding it up?
Sent from my Legend using XDA App
Hi all, Oleg Krikun was published app2sd and app2sd-dalvik for CM 7 01/03
I re-uploaded patch here: cm7_app2sd
and cm7_app2sd_dalvik
ktullanux said:
Hi all, Oleg Krikun was published app2sd and app2sd-dalvik for CM 7 01/03
I re-uploaded patch here: cm7_app2sd
and cm7_app2sd_dalvik
Click to expand...
Click to collapse
This has got nothing to do with this thread.
GuYWith a deodexed and de-bloated Samsung Rom we have 500mb plus of free space on System partition which is wasted space.
I just tried something to free up some space for shared data/sdcard partition by moving Dalvik Cache from /data to /system then creating a folder link back in data to keep original location settings.
Took 30 seconds and freed up 260mb! This is what you do:
1. Using root explorer or similar. Go to /Data.
2. Navigate to "Dalvik-Cache" directory. Long press on it and select "move".
3. Navigate back to root directory and then to /System.
4. Paste the directory you must select rw first top right hand corner. It will take a minute to copy.
5. Now long press on the moved Dalvik-Cache directory in /System and select "Link to this folder" option.
6. Navigate back to /Data and paste the link.
7. Done! You now have moved the Dalvik-Cache location to unused space on System partition and left a sym-linked directory so Android thinks nothing has changed!
Note!: If you wipe Dalvik Cache from recovery a new directory will be recreated in Data and your moved directory in System will no longer be used it will just sit in System taking up space.
AFTER A DALVIK CACHE WIPE FROM RECOVERY YOU MUST DELETE THE DIRECTORY YOU CREATED IN SYSTEM AS IT IS NO LONGER USED. SIMPLY REPEAT THE ABOVE STEPS TO ACTIVATE THE MOD AGAIN.
Good luck. A REAL Dev could you please turn this into a CMW zip with the reverse undo counterpart to be flashed before a Rom upgrade.
UPDATE: looking at the link posted by a helpful person below (thanks!) I think we need to make /system mount as rw for this to work. Please help develop this idea more if anyone can help thanks
Sent from my GT-I9300 using xda premium
Is it work on cm10? I have over 1gb free on system partition
jnr21 said:
Is it work on cm10? I have over 1gb free on system partition
Click to expand...
Click to collapse
I'M not sure haven't used cm10 yet but it should do. Just discovered a Dalvik Cache wipe from recovery recreates the directory in Data to the MOD needs to be repeated after this... makes it very safe to try on cm10!
I'm hoping a real Dev can take this idea and bake it into to custom Rom's and find more data we can move to free up more space
Sent from my GT-I9300 using xda premium
Hi,
Maybe it's possible to do this via init.d script? It will be more convenient.
It's possible via init.d script to move dalvik-cache to /cache for example... so...
Just a thought or simply move it to /cache.
EDIT:found this: http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
Is this similar to the function "Integrate sys Dalvik into ROM" from Titanium Backup?
[email protected] said:
Is this similar to the function "Integrate sys Dalvik into ROM" from Titanium Backup?
Click to expand...
Click to collapse
Yeah I guess it is but if you do it through titanium the Dalvik Cache files are put with their apk files so wipe Dalvik Cache in recovery no longer works... Not 100% sure this is right tho
Sent from my GT-I9300 using xda premium
viking37 said:
Hi,
Maybe it's possible to do this via init.d script? It will be more convenient.
It's possible via init.d script to move dalvik-cache to /cache for example... so...
Just a thought or simply move it to /cache.
EDIT:found this: http://petermolnar.eu/linux-tech-coding/how-to-move-dalvik-cache-to-system-partition-in-android/
Click to expand...
Click to collapse
Yeah should be possible. I think a CWM zip would be best along with an undo version. I now have /Data/app directory moved so before a Rom update or nandroid backup it will be necessary to undo the move. I'll see if I can work out how to do this. Hopefully someone could help out. I'M not code literate yet lol!
Sent from my GT-I9300 using xda premium
if u wanna free up the /data partition, it is a good and proper way to move the dalvik-cache elsewhere. but IMHO, the /system partition is not a good place to move to since by design the system partition is not suppose to have any frequent or unnecessary read write and thus it is ro by default. the other reason is its importance since it is the core part of the system. you can afford to pay for a corrupted data or cache partition but not the system partition since as long as the system files are save the whole system can be rebuilt in case of data loss etc
i am not against this trick and i only want to tell you my opinions. so if possible i would recommend u to put the dalvik cache somewhere else like the cache partition
ykk_five said:
if u wanna free up the /data partition, it is a good and proper way to move the dalvik-cache elsewhere. but IMHO, the /system partition is not a good place to move to since by design the system partition is not suppose to have any frequent or unnecessary read write and thus it is ro by default. the other reason is its importance since it is the core part of the system. you can afford to pay for a corrupted data or cache partition but not the system partition since as long as the system files are save the whole system can be rebuilt in case of data loss etc
i am not against this trick and i only want to tell you my opinions. so if possible i would recommend u to put the dalvik cache somewhere else like the cache partition
Click to expand...
Click to collapse
Yes I've discovered that it's prob not a good idea to leave System rw.... all that wasted space tho
Sent from my GT-I9300 using xda premium
rlorange said:
Yes I've discovered that it's prob not a good idea to leave System rw.... all that wasted space tho
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
u can resize the system partition, and then reassign the disk space freed up to other partitions
NOTE: this is risky and may brick your phone
if you r interested, you can get some more info in my blog posts (based on I9000)
Free more available disk space from NAND - PART I
Free more available disk space from NAND - PART II
freeNANDmod - get more space from NAND - PART III
freeNANDmod - get more space from NAND - PART IV
- symbolic linked dalvik-cache directory may cause issues in some application, use the bind mount instead of this
- titanium backup feature (integrate dalvik-cache to rom) is not mean what you think. it is not for moving dalvik-cache to the system partition
edit: i writed a script what can do exactly what we need.
auto check the dalvik-cache already moved to the cache directory, if yes bind mount the directory. if not, moved the cache then bind mount
you can adjust the cache and the data partition in the beginning of the file, dont touch anything else! default is defined for the SGS3
log file is /cache/dalvik_mover.log
after a full cache wipe the script will be move the dalvik cache after the next reboot
just unzip and put this file to the /system/etc/init.d/ folder
then set the permission to 0755
reboot
this script is not using the system partition, so no need to remount the system as r/w. its used the cache partition what have more free space anyway and always writeable.
and the bind mount method is compatible with everything.
rlorange said:
GuYWith a deodexed and de-bloated Samsung Rom we have 500mb plus of free space on System partition which is wasted space.
I just tried something to free up some space for shared data/sdcard partition by moving Dalvik Cache from /data to /system then creating a folder link back in data to keep original location settings.
Took 30 seconds and freed up 260mb! This is what you do:
1. Using root explorer or similar. Go to /Data.
2. Navigate to "Dalvik-Cache" directory. Long press on it and select "move".
3. Navigate back to root directory and then to /System.
4. Paste the directory you must select rw first top right hand corner. It will take a minute to copy.
5. Now long press on the moved Dalvik-Cache directory in /System and select "Link to this folder" option.
6. Navigate back to /Data and paste the link.
7. Done! You now have moved the Dalvik-Cache location to unused space on System partition and left a sym-linked directory so Android thinks nothing has changed!
Note!: If you wipe Dalvik Cache from recovery a new directory will be recreated in Data and your moved directory in System will no longer be used it will just sit in System taking up space.
AFTER A DALVIK CACHE WIPE FROM RECOVERY YOU MUST DELETE THE DIRECTORY YOU CREATED IN SYSTEM AS IT IS NO LONGER USED. SIMPLY REPEAT THE ABOVE STEPS TO ACTIVATE THE MOD AGAIN.
Good luck. A REAL Dev could you please turn this into a CMW zip with the reverse undo counterpart to be flashed before a Rom upgrade.
UPDATE: looking at the link posted by a helpful person below (thanks!) I think we need to make /system mount as rw for this to work. Please help develop this idea more if anyone can help thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yes, to get this working you need a system mounted Always in r/w.
So i suggest you to move dalvik on cache partition.
And it's better to do the mod inside ramdisk
vadonka said:
- symbolic linked dalvik-cache directory may cause issues in some application, use the bind mount instead of this
- titanium backup feature (integrate dalvik-cache to rom) is not mean what you think. it is not for moving dalvik-cache to the system partition
edit: i writed a script what can do exactly what we need.
auto check the dalvik-cache already moved to the cache directory, if yes bind mount the directory. if not, moved the cache then bind mount
you can adjust the cache and the data partition in the beginning of the file, dont touch anything else! default is defined for the SGS3
log file is /cache/dalvik_mover.log
after a full cache wipe the script will be move the dalvik cache after the next reboot
just unzip and put this file to the /system/etc/init.d/ folder
then set the permission to 0755
reboot
this script is not using the system partition, so no need to remount the system as r/w. its used the cache partition what have more free space anyway and always writeable.
and the bind mount method is compatible with everything.
Click to expand...
Click to collapse
thank you very much works perfect
After upgrading to trickdroids 4.2.2. based release I have some problems. Only with Grooveshark so far. It crashes every time I run it.
Here is a pastbin for it.
http://pastebin.com/VEHkWvZQ
I understand that
/storage/emulated/0/: to my knowledge, this refers to the "emulated MMC" ("owner part"). Usually this is the internal one. The "0" stands for the user here, "0" is the first user aka device-owner. If you create additional users, this number will increment for each.
/storage/emulated/legacy/ as before, but pointing to the part of the currently working user (for the owner, this would be a symlink to /storage/emulated/0/). So this path should bring every user to his "part".
My app that is crashing since upgrading to 7.? is Grooveshark it requires storage in
/storage/emulated/0/Android/data/com.grooveshark.android.v1/files/cache/player
I have no
/storage/emulated/0
I do have
/storage/emulated/legacy/
How would I make the link to this.
I have tried this but it fails
ln -s /storage/emulated/legacy /storage/emulated/0
link failed Read-only file system
Can somebody help with the commands needed to make this link that is required.
I've got the same problem. Have u solved it? if yes, how?
I've struck similar problem after accidentally deleting internal storage. I had no /sdcard in storage.
Apparently you need to run ;
mount -w -o remount rootfs /
Then ;
ln -s /data/media/0 /sdcard
You can check with ;
ls -l -a /sdcard
I have /sdcard0 now in /storage which appears to be the correct description. I use X-plore file manager and it can now see the internal storage correctly.
However CM File Manager (CM11) indicates internal storage should be at /storage/emulated/0 where as mine is /storage/emulated/legacy. Of course I can create a bookmark in CM File Manager to the folder and can see the storage.
All my apps and phone appear to function normally but i can't help wondering if the structure I have in /root for my internal storage is not quite correct. If anyone can tell me the folder and symlinks I should have it would be of great use.
I've tried recreating symlinks with succes so that CM File Manager can see the internal storage at /storage/emulated/0 but the moment I reboot the phone it's back the to the way it was. Have yet to find a simple explanation for what controls the folder structure in /root and why I can't get the symlinks I create to stick.
Update 5Feb - Did another factory reset and flashed CM11 M2. Everything OK now. Maybe needed a couple of resets to sort the ghosts in the machine.
Update something
[Edit Philz 6.2.3+ is perfect & does not mess with my swap anymore.]
messed with the install-recovery.sh!
So just reflash the swap , not sure what did it : an xposed modual?
v5 up.
Works now even if on bone stock.
Step 1: (for those rooted, on the ota or out of the box)
Install this https://play.google.com/store/apps/details?id=stericson.busybox
Use the smart install & choose 1.21.1 not 1.22. http://forum.xda-developers.com/showpost.php?p=50064227&postcount=4
Do not use Universal init d.
Reboot.
Step 2:
Flash v5 with Twrp2.6.3 e33 or Philz v6079.
For SafeStrap users using bootstrap, should work.
Reboot.
TWRP e33: http://forum.xda-developers.com/showpost.php?p=49509466&postcount=1
Fixed conflicts with my ◢ PurePerformances™X ◣ mod.
You can only successfully install with Plilz v6079. I only use, for now the one below.
Once installed TWRP does not seem to be a problem.
Plilz v6 for msm8960 phones: Atrix HD, Razr M & Photon Q is here
Took down the deodexed version as it was only the ui from this 1% battery mod that made it different. You can flash it to any deodexed 412 xt907 or xt905 rom.
All storage defaults to storage0 (your real SD card) which is the way it should have been from Motorola, well closer anyway.
Flash from recovery or SS bootstrap Philz v6. Wipe dalvik & cache only. Not for cm based, multuser, or anything but 4.1.2 stock roms!
My ◢ PurePerformances™X ◣ mod must be followed by the SD Swap. Because of a conflict with install-recovery.sh file.
Do not use cwmr 6044 as it messes up the swap by forcing data/media/0. Plilz is better as you can choose data/media only. See my goodies for Philz.
Always use TWRP 2.6.3 e33 OR Philz v6079.(for install use Philz only)
Always choose any NO when rebooting from Philz.
Go Recovery Goodies
Because install-recovery.sh is now an agent in the initd setup & needs to be protected.
Notes on the SD swap: When you choose "Device storage", sdcard0 or storage0 you will browsing your real SD card. When you choose "SD card", sdcard1 or storage1 you will be browsing the internal SD ("data/media").
This internal SD ("data/media") memory now has no purpose. You can move what you want to your real SD & delete everything else to let the phone use it all. All storage defaults to storage0 (your real SD card) which now is the way it should have been from Motorola, well closer anyway.
ZaYAC-ua's swap thread
The formerly unwanted file: install-recovery.sh is now an agent in the initd setup & needs to be protected, as noted above, and it's permissions, if altered, can be restored to rwxr-xr-x.
If this file is not protected you boot up with 2 internal SD cards.
Known issues:
Two things will Kill the SD swap: (by messing with install-recovery.sh)
1)Using TWRP older then v2.6. (To install use Philz only)
2)If you boot from CWMR and choose yes to "disable recovery flash".
Also) If you mess with multiuser roms feel free to delete 0 , obb & legacy folders in internal sd (storage1).
One more) It is expected for your settings-storage info to be out of whack.
Finally) Create folder in root of the phone with Root Explorer results in an error but is the same as the Rabbit's version & of no consequence. The folder does get created anyway. All else works in the root of the phone.
UsbMassStorage: BE SURE TO EJECT FROM PC/MAC BEFORE YOU UNMOUNT. DO NOT USE WITH ANDROID FILE TRANSFER.
".files" are a nuisance when mounting to osx: just delete them AFTER YOU UNMOUNT. Warning: If you do not enable your file browser to show hidden files & you unmount while your (os x is one) trash is full the .file can be huge!
More http://forum.xda-developers.com/showpost.php?p=43434787&postcount=3
V1 DL stats: deodexed-31, odexed-49
Reserved
V3 up. Fixes compatibility w/ PP mod. Twrp will not install the swap & let it work! Plilz v6 will & does twrp restores too....
I'm using this script to swap the storage on PACman and other 4.3 roms that lacks the swap option natively, I guess your solution is more or less the same, using the restore recovery script instead of the real init.d script.
Right ?
Code:
#!/system/bin/sh
sleep 3
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
chown system /data/media/0
chgrp sdcard_rw /data/media/0
chmod 0075 /data/media/0
mount -o remount, ro /
The Solutor said:
I'm using this script to swap the storage on PACman and other 4.3 roms that lacks the swap option natively, I guess your solution is more or less the same, using the restore recovery script instead of the real init.d script.
Right ?
Code:
#!/system/bin/sh
sleep 3
mount -o remount,rw /
mount -t vfat -o umask=0000 /dev/block/vold/179:97 /mnt/shell/emulated
mount -o bind /data/media/0 /storage/sdcard1
chown system /data/media/0
chgrp sdcard_rw /data/media/0
chmod 0075 /data/media/0
mount -o remount, ro /
Click to expand...
Click to collapse
Thanks. Did you have a link? I have never found one that works for 4.1.2 + !
aviwdoowks said:
Thanks. Did you have a link? I have never found one that works for 4.1.2 + !
Click to expand...
Click to collapse
A link ?
That's all I'm using, just copy it save it to (say) 02sdswap, put the file in the /etc/init.d folder and set the permissions as the other init.d files.
Then reboot the phone.
That's all
Keep in mind to use a decent editor and set the end line format to UNIX.
I'm using it on 4.3 on PhotonQ but it should work, as is, on other similar phones like the Razr M, or with little adjustment in other phones.
Is far from perfect but looks to be enough to solve the problem.
The Solutor said:
A link ?
That's all I'm using, just copy it save it to (say) 02sdswap, put the file in the /etc/init.d folder and set the permissions as the other init.d files.
Then reboot the phone.
That's all
Keep in mind to use a decent editor and set the end line format to UNIX.
I'm using it on 4.3 on PhotonQ but it should work, as is, on other similar phones like the Razr M, or with little adjustment in other phones.
Is far from perfect but looks to be enough to solve the problem.
Click to expand...
Click to collapse
Just tried it, removing the "/0" from each line w/ datamedia.
No go for 412.
aviwdoowks said:
No go for 412.
Click to expand...
Click to collapse
Practically I've never used JB 4.1.2, as I see no point in doing it.
Depending on my moot I use my internationalized ICS, or a good 4.3 unofficial rom.
Bacause this, I don't remember exactly the changes in paths and symlinks between 4.1.2 and 4.3
But very likely the /mnt/shell/emulated is not present on 4.1.2, just check if I'm not wrong, and eventually change the /mnt/shell/emulated to the correct mountpoint.
V4 up. Much improved. Only the install-recovery.sh annoyance to overcome. I am trying a "userint.sh" version. Anyone know if that is do-able on a moto phone? Htc phones use it with a swap.
Couple this concise commentary of the data media problem,
http://teamw.in/DataMedia
[translation: data/media is useless if you have ext sd as default storage.
It needs to be formatted for reliable rom flashes (esp. 4.4)
& you can do it from Philz! ]
With the ability to use a large sd card on our phone,
then you understand why keeping data media zeroed out along with a sd swap is so nice.
Where oh where is a swap for 4.4?
Btw a new Plilz with ext sd cwm folder detection :fingers-crossed: due out soon.
FIRST OF ALL, we should say thanks to @alvinhochun 's work on porting kexec hardboot patch to Xperia M. His original thread is here: http://forum.xda-developers.com/showthread.php?t=2568151
And @Tasssadar who has ported kexec hardboot patch on MSM chips. Original thread is here: http://forum.xda-developers.com/nexus-4/orig-development/kexec-hardboot-patch-t2472316/post46223952
As for the kernel patch and kexec binary for TX, they are here: http://forum.xda-developers.com/showthread.php?t=2747215
OK let's begin our tour on TX...
0. Disclaimer
This is a rather dangerous hack. I'm not responsible for data loss, broken SD cards, dead internal storage or bricked phones. Try this at your own risk. Proceed only when you know what you are doing.
1. Requirements
a. ROM with “kexec hardboot” patched kernel. My OmniROM build will do the job. Since Alx31Tse is also using my kernel source for TX, the Carbon builds for TX may be capable of handling this as well. This ROM should be installed into internal storage : just flash it in recovery as usual.b. External MicroSD card which is big enough for your ROMs. One ROM takes up ~4GB space.c. Some basic knowledge of partitions, device nodes, ramdisk modding(check this thread by letama: http://forum.xda-developers.com/showthread.php?t=2418893).
2. Partitioning the external sdcard
a. Plan the partitions
Each ROM need three partitions : system, data and cache. You need at least 1.4GB system + 2GB data + 400MB cache for stock ROMs. The system partition for third-party ROMs can be shrinked to ~900MB. Of course you can set your own data partition size if 2GB does not suit your needs. The space left can be used for storing data just like a normal sdcard.
For example, I'm using a 16GB card and going to install two stock ROMs (9.1.B.1.67 + 9.2.A.0.295). So I have to create at least 6 partitions for them:
1.4GB system for 295
2GB data for 295
400MB cache for 295
1.4GB system for 67
2GB data for 67
400MB cache for 67
There is ~8GB left after all these partitions. This can be used as a normal sdcard. Just create another partition for it.
b. Go partitioning it!
Everyone has his own way of doing this. I prefer using a USB card reader and Disk Utility that comes with Ubuntu.
Erase the card and initialize it with GUID Partition Table (GPT). Of course you can use MBR, but I didn't test it. Be careful in the following steps if you choose MBR.
Create the “normal sdcard” partition. In my example, create a 8GB partition here and format it with FAT32. THIS PARTITION SHOULD BE THE FIRST ONE ON THE CARD! Otherwise Android system may not be able to recognize it.
Create the partitions for guest systems. There are no particular order for the partitions. Just make sure you remember their order. DO NOT FORMAT them for now.
In my example:
PART 1: 8GB, FAT32
PART 2: 1.4GB unformatted
PART 3: 2GB unformatted
PART 4: 400MB unformatted
PART 5: 1.4GB unformatted
PART 6: 2GB unformatted
PART 7: 400MB unformatted
3. Kernel mods for guest systems
For each guest system:
a. Unpack its kernel.
If you are going to install a full stock ROM, please choose a corresponding kernel with recovery built-in in Android Development section.
If you are going to install a third-party ROM (OmniROM, CM etc) or customized stock ROM (Rockers etc), chances are that their kernels have recovery built-in already and you can proceed.
Now unpack the kernel.
We have zImage(sec0.bin), ramdisk(sec1.bin) now. The rest can be ignored.
b. Modify the mount entries in fstab (and other files)
fstab is the file that suggests the real device for the /system, /data and /cache mount points. Modding it will make it possible to mount the partitions other than the ones in internal storage on /system /data and /cache, so that we can separate different systems into different partitions.
Now you have to be clear about “how the partitions on external card will be presented in your phone” (their device nodes). In my example (GPT with 7 partitions):
PART 1: 8GB → /dev/block/mmcblk1p1
PART 2: 1.4GB → /dev/block/mmcblk1p2
PART 3: 2GB → /dev/block/mmcblk1p3
PART 4: 400MB → /dev/block/mmcblk1p4
PART 5: 1.4GB → /dev/block/mmcblk1p5
PART 6: 2GB → /dev/block/mmcblk1p6
PART 7: 400MB → /dev/block/mmcblk1p7
As has been mentioned above, mmcblk1p1 is for normal file storage, p2~p4 is for 295, p5~p7 is for 67.
Files that need modding:
(sec1.bin/sbin/ramdisk.cpio) /fstab, /fstab.qcom, /init.target.rc
Click to expand...
Click to collapse
(sec1.bin/sbin/ramdisk-recovery.cpio) /fstab, /fstab.qcom, /etc/recovery.fstab, /etc/twrp.fstab
Click to expand...
Click to collapse
The fstabs are easy to deal with. Just change the block device name for /system /cache and /data to /dev/block/mmcblk1p* accordingly. The init.target.rc has only one line that should be modded. For example,
FOR 9.1.B.1.67 in my example:
ramdisk.cpio/fstab:
/data ext4 /dev/block/mmcblk1p6
/cache ext4 /dev/block/mmcblk1p7
/boot/modem_fs1 raw /dev/block/platform/msm_sdcc.1/by-name/modemst1
/boot/modem_fs2 raw /dev/block/platform/msm_sdcc.1/by-name/modemst2
Click to expand...
Click to collapse
ramdisk.cpio/fstab.qcom:
/dev/block/mmcblk1p5 /system ext4 ro,barrier=1,discard wait,check
/dev/block/mmcblk1p6 /data ext4 nosuid,nodev,noatime,barrier=1,noauto_da_alloc,discard wait,check,encryptable=footer
/dev/block/mmcblk1p7 /cache ext4 nosuid,nodev,noatime,barrier=1,discard wait,check
/dev/block/platform/msm_sdcc.1/by-name/SDCard /mnt/int_storage ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check
Click to expand...
Click to collapse
ramdisk.cpio/init.target.rc:
(SEARCH FOR /system)
on post-fs
mount ext4 /dev/block/mmcblk1p5 /system ro remount barrier=1
Click to expand...
Click to collapse
Just do the same for ramdisk-recovery.cpio. For example:
ramdisk-recovery.cpio/etc/recovery.fstab
/boot emmc /dev/block/mmcblk0p4
/system ext4 /dev/block/mmcblk1p5
/cache ext4 /dev/block/mmcblk1p7
/data ext4 /dev/block/mmcblk1p6 length=-16384
/sdcard ext4 /dev/block/mmcblk0p15
/external_sd auto /dev/block/mmcblk1p1 /dev/block/mmcblk1
Click to expand...
Click to collapse
And replace mmcblk1p5~p7 with p2~p4 then do it all again for 9.2.A.0.295's ramdisk.cpio & ramdisk-recovery.cpio
NOTE: All these fstab and rc files should be rw-r—r-- and owned by root:root. Otherwise the system may fail to boot.
Now repack the ramdisk.cpio, ramdisk-recovery.cpio and then the whole ramdisk.
4. Installing the guest systems
Take notice of the texts in red. Change them to fit your needs.
a. Preparing the guest systemsIf you are installing full stock ROM (FTF format), you can use Flashtool to dump the system image (Flashtool > Tools > Sin Editor, load system.sin from FTF archive and dump data). Then write the image to the sdcard by “dd if=system.ext4 of=/dev/sdb2“ on the computer.
If you are installing ROMs in ZIP format, you need to modify updater-script and replace all (for 9.1.B.1.67 in my example)
/dev/block/mmcblk0p12 or /dev/block/platform/msm_sdcc.1/by-name/System to /dev/block/mmcblk1p5
Click to expand...
Click to collapse
/dev/block/mmcblk0p13 or /dev/block/platform/msm_sdcc.1/by-name/Cache to /dev/block/mmcblk1p7
Click to expand...
Click to collapse
/dev/block/mmcblk0p14 or /dev/block/platform/msm_sdcc.1/by-name/Userdata to /dev/block/mmcblk1p6
Click to expand...
Click to collapse
And
remove /dev/block/mmcblk0p4 or /dev/block/platform/msm_sdcc.1/by-name/Kernel formatting/writing lines
Click to expand...
Click to collapse
Then repack the ROM and push it into phone's internal sdcard.
b. Boot the guest kernel/systemRemember we have zImage and modded ramdisk for each guest system? adb push them to /data partition. The kexec binary is needed as well. Now you can use the kexec binary(check the beginning of this thread) to boot your guest kernel and then recovery.
For example:
I pushed 295 kernel zImage to /data/boot4.3/zImage-stock, modded ramdisk to /data/boot4.3/initrd-stock, and kexec binary to /data/kexec. Now execute as root:
Code:
cd /data
chmod 755 kexec
busybox sync
busybox mount -o remount,ro /system
busybox mount -o remount,ro /cache
busybox mount -o remount,ro /data
busybox sync
./kexec --load-hardboot [COLOR="Red"]./boot4.3/zImage-stock[/COLOR] –initrd=[COLOR="Red"]./boot4.3/initrd-stock[/COLOR] --mem-min=0x85000000 --command-line="`cat /proc/cmdline`"
busybox sync
./kexec -e # phone reboots and guest kernel (295) starts
NOTE: the guest kernel's cmdline may not be exactly the same as the host one. However, it doesn't matter much. 67 and 295 both boot fine using the same cmdline as OmniROM. Since bootloader will append some parameters to the command line, using guest's sec3 without appending these parameters manually is not a good idea.
c. Preparing filesystems and installing ROMs in ZIPAfter the phone reboots, press Vol buttons at purple LED to go into recovery. Now you are in the recovery for your guest system (295).
FORMAT (not wipe) /data and /cache there. For ZIP ROMs you need to format /system as well.
Then install the modded ZIP file if needed. You can also flash SuperSU or anything else to this guest system in the recovery (remember to check if there are wrong block device paths in updater-script).
After finishing the installation of one guest system, reboot and you will go into the host ROM. Execute the commands again and specific the next guest system's zImage and ramdisk to boot into the next guest system. Then do the formatting and flashing things as described above.
5. Boot into guest systems
Once you finish installing all the guest systems, reboot. Then in the host ROM you can execute the commands in Step 4 again to boot into the corresponding guest system. Don't press any key after the reboot. If there's nothing wrong, you will see the bootanimation and then the Android system. Since external sdcards may not be as fast as internal storage, the first boot may take very long time. If you see the bootanimation, just be patient and it will boot up finally.
===========================================================
I know I can't speak English well and it's hard to make myself clear. So if you feel confused, please post your questions here so that everyone who knows the answer will be able to help.
And if you are skilled in Android things, you can choose your own way to achieve the goal:
Partition the sdcard → Mod fstsb and rcs to mount partitions on sdcard to /system etc → Mod the ROM installation script → Boot into guest recovery to format(initialize) data & cache &system and flash ROM → Boot into the guest Android OS
Click to expand...
Click to collapse
This is a little bit complicated. But I do hope this will add more fun to our device
Thanks for your sharing
got it
Although this is labeled for the Xperia TX, after reading through everything, it looks like this works on all devices, you just have to change a few things. Good job putting this together! (Even though I don't have an Xperia TX)
r3pwn said:
Although this is labeled for the Xperia TX, after reading through everything, it looks like this works on all devices, you just have to change a few things. Good job putting this together! (Even though I don't have an Xperia TX)
Click to expand...
Click to collapse
Yeah, it seems that the guide applies to all devices with patched kernels
updateing said:
Yeah, it seems that the guide applies to all devices with patched kernels
Click to expand...
Click to collapse
This guide is nice, full of content, and detailed, but wouldn't it have been easier, though, to just make a MultiROM port?
r3pwn said:
This guide is nice, full of content, and detailed, but wouldn't it have been easier, though, to just make a MultiROM port?
Click to expand...
Click to collapse
I have thought of porting MultiROM, but I'm running a tight schedule...sorry
Whether this Xperia V can also be made from ??
Mircinko96 said:
Whether this Xperia V can also be made from ??
Click to expand...
Click to collapse
It's applicable to Xperia V in theory. But you need a kernel with kexec hardboot patch, which hasn't appeared yet (as far as I have seen). If you know how to compile a kernel, you can try patching the kernel yourself.
.........
do I need linux to unpack kernel?