Hi there,
is there a solution to make it possible that a microSD-card formatted in ext4 is able to be mounted in CM9?
This one I found for the Galaxy tab here.
I don't use any window systems and I'm not happy to have to format the extSD-card in FAT32 or exFAT.
Regards
Koeti
No one, who has a solution?
Gesendet von meinem GT-I9300 mit Tapatalk 2
There is such a feature, but you have to proceed with EXTREME caution.
You must also have taken a backup of you sd cards' contents.
Firstly, go and flash the Franco Kernel
On his secong post, you can see the instructions required:
franciscofranco said:
Wi-Fi Power Management toggle:
How to activate the special sdwatcher binary:
This binary is special *buzzwords incoming* and will get rid of the fuse mounting and get rid of the /data/media symlink which causes excessive Media Scanning load - basically just mounts the internal sdcard as ext4. Battery life gets a nice boost using this binary. Instructions on how to use it at the second post. All credits go to Greg White, I did nothing but testing it for him.
To activate use ADB or Terminal Emulator:
mount -o rw,remount /system
cp /system/bin/sdcard /system/bin/sdcard.bak
rm /system/bin/sdcard
cp /sbin/sdcard /system/bin/sdcard
chmod 0777 /system/bin/sdcard
reboot
Don't mess with this if you don't know what you're doing.
Click to expand...
Click to collapse
I, however, did this manually using RootExplorer:
Code:
1) Navigate to "/system/bin/" using a root enabled explorer app. Enable read and write access.
2) Rename the "sdcard" file found in that directory to "sdcard.bak" (so you know have a backup).
3) Navigate to "/sbin/". There will be an "sdcard" file there.
4) Copy the "sdcard" file to "system/bin/".
5) Change the permissions to "rwxr-xr-x".
6) Reboot the system.
My guess is that you can flash any kernel you want after this procedure. I have tried Siyah and it's working fine so far. Your mileage will vary.
If you find the camera saying things like "Unable to write to external storage" or whatever, you have to creat a "DCIM" folder in the root of your external sd card manually. It will then be alright (you have to change the storage device back to external in camera options).
Make a note that this is an extremely advanced procedure that I myself am in the process of fully vetting!
Cheers!
Erahgon said:
Firstly, go and flash the Franco Kernel
Click to expand...
Click to collapse
Thanks for your answer, but franco writes: 'This kernel is for Samsung roms only. No plans to make it work with AOSP or CM9'. So unfortunalety it's only runs on stock roms.
Hi, any news on how to get this to work on other kernels?
Thanks
Phk said:
Hi, any news on how to get this to work on other kernels?
Thanks
Click to expand...
Click to collapse
Also, on the mid-step of this, the file "/sbin/sdcard" does not exist...
Related
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
pavitar said:
I have tried a lot of custom Roms. I'm on Neat ROM Lite now. Not sure which ROM changed my file access permission settings to cause this problem but I'm not able to delete any files from my external memory card. I was able to delete when I was on stock rom. The other problem is for a few apps I get an error message which says can't install on usb/sd card. I have posted this in another thread
some time back but got no response. Some one please point me in the right direction.
This is what my file permission looks like.
PS: I am able to delete when my fone is connected to PC via USB. So I don't think it has anything to do with a faulty sd card.
Click to expand...
Click to collapse
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
ricky310711 said:
file permissions are 775, try changing them to 777(all boxes ticked)
for future refference he is my support thread Ricky310711 AllInOne Support Thread
Click to expand...
Click to collapse
Can you please tell me, how to apply a file permission? I tried checking the box which is not checked in the snapshot shared, but that too gives an error.Says "Operation failed"
pavitar said:
Can you please tell me, how to apply a file permission?
Click to expand...
Click to collapse
download mobile terminal from playstore
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
pavitar said:
Hey I know its been quite sometime now.but as ur advice I downloaded mobile terminal and now have to run the following command everytime I boot my fone:
mount -o rw,remount -t/yaffs2 /storage/extSdCard
Otherwise i do not get rw access to my external sd.Istn't there a permanent solution to this? Also I fail to understand what changed my permissions and why does this persist across all the new roms I flash?
Sent from my GT-I9100 using xda app-developers app
Wanamlite ->Slim Bean 4.2.2 ->NeatRom Lite -> wanamlite
Click to expand...
Click to collapse
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
iamareebjamal said:
Create a blank file and type that command in it. Now save it and rename it to 95mountsd with no extension
Now, if you have init.d support, place it in /system/etc/init.d and reboot
Command will run on every boot itself
Click to expand...
Click to collapse
pavitar said:
Thank you, it worked. Now could please have a look at my other issue, in this post I'd be really thankful.
Can you please tell me what could be the reason for my default rw settings to change, coz I remember when I had stock os I never had to do all this.
Click to expand...
Click to collapse
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
iamareebjamal said:
Sorry, i'm not good at hardware stuff
Maybe the ROMs aren't mounting that special kind of partition your sdcard is having
FAT32 format works universally
yaffs2 may not
I'm not sure
Click to expand...
Click to collapse
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
pavitar said:
Hey I have switched back to stock rom and I've rooted it by flashing philz kernel. Now I don't see init.d in my /system/etc , where do I place this 95mountsd in this case?
Click to expand...
Click to collapse
Try this
https://play.google.com/store/apps/...&utm_medium=organic&utm_term=universal+init.d
Hello, Noob here so only allowed to post to 'General' forum.
I have a Nabi-2 tablet that I recently flashed the stock 2.1.27 ROM.
Then used WiFi to do the OTA to version 2.3.11.
And got TWRP installed (Jelly Bean v2.6.3) and rooted the device.
Trying to get Need For Speed installed without chewing up all the
internal memory. And also trying to learn some basics about mounting,
symbolic links, etc on the Android.
NFS gets installed at:
/storage/sdcard0/Android/data/com.ea.games.nfs13_na
I'd like to install it on the external card at:
/storage/sdcard1/links/Android/data/com.ea.games.nfs13_na
I made a folder named 'init.d' and placed it:
/system/etc/init.d/
Then placed my script 'foo' into init.d.
foo contents:
Code:
#!/system/bin/sh
mount -o bind /storage/sdcard0/Android/data/com.ea.games.nfs13_na /storage/sdcard1/links/Android/data/com.ea.games.nfs13_na
Then I moved all the contents from the subfolder in sdcard0 to
the respective folder in sdcard1.
And made sure the permissions were set to rwx for all folders and
the script.
Should this approach work? I did something wrong but thought I should
ask the experts if this is even a valid approach.
I'm sure there are other ways to accomplish this but like I said, my
objective is to also learn.
I also also run into this problem with my kid's nabis. Especially with NFS!
So I put up a post here to give it some more visibility (maybe):
http://forum.xda-developers.com/showthread.php?t=2592694
Looking at your mount command - looks like you reversed the args.
Try this with the suggestions in my post.
Code:
mount -o bind /storage/sdcard1/links/Android/data/com.ea.games.nfs13_na /sdcard/Android/data/com.ea.games.nfs13_na
Hope it helps.
skippyV said:
I also also run into this problem with my kid's nabis. Especially with NFS!
So I put up a post here to give it some more visibility (maybe):
http://forum.xda-developers.com/showthread.php?t=2592694
Looking at your mount command - looks like you reversed the args.
Try this with the suggestions in my post.
Code:
mount -o bind /storage/sdcard1/links/Android/data/com.ea.games.nfs13_na /sdcard/Android/data/com.ea.games.nfs13_na
Hope it helps.
Click to expand...
Click to collapse
Just got it working using your pointers. Thanks so much! :good:
That Init.d program is awesome!
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
I installed [ROM] [4.4.2] CyanogenMod 11.0 from here
everything runs fine,but i cant write files to the internal storage.
For instance if i start the gallery app it tells me "No internal storage available",another app tells me it "cant write to the cache folder" because the sd is full,mounted,or write locked.Root explorer sees all the files but cant delete,move or copy/paste anything.
Apps that save/download files like podkicker or reddit act normal when trying to save the file but after the download starts the notification disapears and the file is simply not downloaded.Apps that stream content work fine,like youtube,or the stream feature of podkicker.
I have over 2gb free space so its not that,and if i plug into my pc i can move and delete files no problem.I like the rom and like i said everything else seems to work fine.
Thanks in advanced for any help.
EDIT:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
lalalalas said:
I'm having the same problem, with both CM11 and 10.2.0 on Verizon LG G2. Could it be a permissions problem?
Click to expand...
Click to collapse
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
leadtk said:
Its weird because i can write to the root directory but not any folders in it.Root explorer and es file manager say that its read only but neither will let me switch to read/write.
I made a logcat from boot[at least i think i made it rite,never had to do one before]
But i cant post the link because i dont have 10 posts just add this rpqjxGhG to pastebin
This all also happens with external sdcards as well it turns out,i just tried to make a new file with the built in file manager on the external sd and it said it requires elevated permissions,
root explorer just says file creation failed.
I also get constant "unfortunately,Trebuchet has stopped" messages when doing any thing.
I have also tried terminal emulator for kicks.
I gave it su then tried
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system]
didnt change a thing
then i tried
adb remount
this said error: device not found
Im pretty sure its not my tablet as i can can go back to stock/stock root and write files perfectly fine,ive also re-downloaded the rom twice just to make sure it wasnt bad,and ive probably flashed it around 20 time by now all with the same result.
I hope someone can figure something out.
Click to expand...
Click to collapse
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Quallenauge said:
When installing the CM11 firmware, did your format/reset your "android+storage" in "format device" recovery menu?
Storage files should be /mnt/sdcard/ (internal storage) and /mnt/media_rw/sdcard1/ (extern sdcard).
I'm able to create files in both directories as well on the file explorer.
If you want to "unlock" the root ( / ) partition you have to use this one inside the shell:
Code:
mount -o remount,rw /
but this don't have some effects to the mounted storage files.
Click to expand...
Click to collapse
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
leadtk said:
I was updating by putting the firmware file on the the device then rebooting and flashing the zimage and initramfs,
The reason being if i reset the "android+storage" dosnt that mean the firmware is deleted?
adb dose not see the tablet when its in recovery,it does see it when its on[am i doing something wrong there?],so i cant push the files,and if i export the data partition in windows a pop up and says it needs to be formatted before it can be used.so how am suppose to get the file to the device if i format everything?
Click to expand...
Click to collapse
From the guide, install using adb. http://forum.xda-developers.com/showthread.php?t=1871912
Originally Posted by surdu_petru
Installation : Now should be work on all devices Gen9 !!!
...connect USB cable to PC and ( you need to use a Rom with root access ) :
> adb shell
# stop
# rm -rf data/*
# mkdir data/local
# mkdir data/media
# exit
> adb push archos.ext4 /local/ ( need to wait about ~150 seconds ) !
> at the same time do : adb reboot & press and keep volume down ; in SDE -> DEM-> Remove Android Kernel ( if exist ) -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.gz -> OK -> wait to reboot !
Click to expand...
Click to collapse
If you are a Linux user. http://forum.xda-developers.com/showpost.php?p=48731942&postcount=1
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
leadtk said:
YAY i got it,
thanks stevemp and Quallenauge,a couple of the things needed to be a bit different though like the "# rm -rf data/*",and the push location line,heres what i did
Plug in the tablet with usb debugging enabled
run cmd and get adb going
type
adb shell
stop
rm -r data/*
mkdir data/local
mkdir data/media
exit
then push the rom file with [adb path]/adb push [rom path] /mnt/storage
when the push finished type adb reboot hold the volume down button and press enter
once rebooted into sde go to dev menu remove android kernel if necessary then choose flash kernel and initramfs
copy the files over
reboot
Everything seems to be working now i can read write files all day.
THANKS AGAIN!!
Click to expand...
Click to collapse
I do not know what i am doing wrong but when i type adb shell ..all i get is BUSYBOX v1.7.2 (2012-10-19 CEST) built in shell (ash) Enter help for a list of built in commands ...
I did have ics blue v04 rom on my tablet that i was trying to go from to 4.4.2 ..
I did this before and had the write problem . any help you can give would be appreciated
I was Just reading about a Triple Swap (Ram) trick on XDA, It Uses Cache and Data and System partition as Swap Space.
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!
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.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So the Help I need is: To get our device supported for this is are the following things:
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 Me 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")
Please, sent above info to Me via PM!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
The Two Files I will send to the developer, Then We can pray that He gets to Work on it..
HJain13 said:
I was Just reading about a Triple Swap (Ram) trick on XDA, It Uses Cache and Data and System partition as Swap Space.
Idea
So the Help I need is: To get our device supported for this is are the following things:
The Two Files I will send to the developer, Then We can pray that He gets to Work on it..
Click to expand...
Click to collapse
U can just skip ur second step by not checking the device
Hmm..... BUT
T3snake said:
U can just skip ur second step by not checking the device
Click to expand...
Click to collapse
Hmm.. but It would be nice if We could use Aroma.. easier to choose amount of swaps and where etc...
HJain13 said:
Hmm.. but It would be nice if We could use Aroma.. easier to choose amount of swaps and where etc...
Click to expand...
Click to collapse
It will be aroma allright...
I meant ur second step (getprop 1) isn't mandatory
Anyway info u need is in build.prop
Sent from my SM-T211 using Tapatalk
DISCLAIMER:
I AM NOT RESPONSIBLE FOR YOUR DEVICE OR ANYTHING THAT MIGHT OCCUR WHILE USING THIS TUTORIAL. TRY AT YOUR OWN RISK!
Credits:
[mbm] for teaching me this dd terminal method.
As we all know, for what ever reason, Samsung decided to release the Tab 3 model tablets with 1 GB of ram. I believe this system needs more ram but unfortunately we cannot upgrade the hardware. What we can do is create virtual memory or a "Swap file" that acts like ram to help our Tab 3's out with multitasking and other memory hogging tasks. Below are the steps to:
1. Create a swap file.
2. Create a script file to run at boot from your /system/etc/init.d directory.
3. Create a android system with 1GB of RAM and 1GB of swap file virtual memory.
*Remember whatever device you are using must have a rom with init.d support and be rooted.
STEP 1: TERMINAL COMMANDS PT.1
Download terminal emulator from the play store if you don't already have it.
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Open terminal emulator and execute these commands in order:
1. "su"
2. "cd /system"
3. "mount -o rw,remount /system"
4. "dd if=/dev/zero of=swapfile bs=1m count=600" (be patient, this step takes about a minute)
5. "mkswap swapfile"
6. "chmod 755 swapfile"
STEP 2: INIT.D SWAP FILE TEXT CREATION
Now to create a script to execute at boot every time you boot your phone. I used the app QuickEdit from the play store.
https://play.google.com/store/apps/details?id=com.rhmsoft.edit
Now open that up and put the text below in the file:
"mount -o rw,remount /system
swapon /system/swapfile"
Now save that to your sdcard (/sdcard) as "swap" (remember do not save with the .txt)
STEP 3: TERMINAL COMMANDS PT.2
Now go back into terminal and execute these commands:
1. mv /sdcard/swap /system/etc/init.d
2. chmod 755 /system/etc/init.d/swap
I kept my previous terminal session open but if you closed it for what ever reason you might have to execute "su" and then "mount -o rw,remount /system" before the two commands in step 3.
STEP 4:
Reboot and win. :laugh::good::laugh:
To verify that the process has worked, after reboot, bring up terminal emulator and type "free -m". You should see that swap has more than 600M! This will stick after reboot. If for whatever reason you want to get rid of your swap file just delete the "swapfile" file and the "swap" script. Enjoy!
I'm getting "swap file needs to be a least 40kb" after I "mkswap swapfile"
EDIT:I tied it again now and it seemed to work, for some odd reason
Sent from my SM-N910T using Tapatalk
My swap file reads "399" .... it's not more than 600m. What did I do wrong?
vin_001 said:
My swap file reads "399" .... it's not more than 600m. What did I do wrong?
Click to expand...
Click to collapse
Never mind! I found the solution... when typing "1m" into the command line, the m must be capitalized, "M". If anyone else has this issue, this is where u went wrong! Now I have "999" instead of "399"!
AWSOME. It brought some more life into my lagging P5210 running latest cm13 from Nelson. Cool
Thanks, I can finally use chrome on my tab 3
Is it same to wipe the system partition? , bcuz i want to clean install
Sent from my SM-G7102 using Tapatalk
Devel0per95 said:
Is it same to wipe the system partition? , bcuz i want to clean install
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean, but when you wipe your system folder, you need to make swapfile again.
@ "4." it says: "Read-only file system"
What did I do wrong?
I'm on 13.0-20161121-UNOFFICIAL-santos10wifi
Thanks!
Gesendet von meinem SM-G925F mit Tapatalk
DerLeoLeo said:
@ "4." it says: "Read-only file system"
What did I do wrong?
I'm on 13.0-20161121-UNOFFICIAL-santos10wifi
Thanks!
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
You didn't do number 3 right. That mounts the system read/write
Sent from my SM-N920V using Tapatalk
Thanks! Will try again...
Gesendet von meinem SM-G925F mit Tapatalk
Hi I have still the message...
Any clue?
Thanks a lot
My device is really more usuable with this trick
Added with niels CM custom ROM it is fantastic
Envoyé de mon GT-P5210 en utilisant Tapatalk
I've got to the last step and couldn't move the file as the /system partition is 100% used.
I also notice that the created /system/swap file is only 589M ...
So I guess I could try to use a smaller swap file or clear some /system/** memory? Anyone know the best way to do that? or what i can delete etc?
thanks.
spankycarbowski said:
I've got to the last step and couldn't move the file as the /system partition is 100% used.
I also notice that the created /system/swap file is only 589M ...
So I guess I could try to use a smaller swap file or clear some /system/** memory? Anyone know the best way to do that? or what i can delete etc?
thanks.
Click to expand...
Click to collapse
The last step is where you went wrong, since swap uses space on your system partition. Free up space and redo everything again. You should see 999 ( or more than 600) if you succeeded.
vin_001 said:
The last step is where you went wrong, since swap uses space on your system partition. Free up space and redo everything again. You should see 999 ( or more than 600) if you succeeded.
Click to expand...
Click to collapse
Yes right, I guess I am really asking - what is the best way to clean up the system partition - as i have no idea what i can delete?
spankycarbowski said:
Yes right, I guess I am really asking - what is the best way to clean up the system partition - as i have no idea what i can delete?
Click to expand...
Click to collapse
To free up space in the system partition, try deleting unecessary system apps and bloatware, (I'm guessing you are on stock touchwiz, but it doesn't matter otherwise). You can also find a deodexed rom that you would like. Deodexed roms use less space in your system partition. The last option is to get a download of your rom on a PC and boot into TWRP (3.0.2-0 preferred) and do an advanced wipe as well as your internal storage. Backup everything if needed, then reflash.
Hope any of these helped!
vin_001 said:
To free up space in the system partition, try deleting unecessary system apps and bloatware, (I'm guessing you are on stock touchwiz, but it doesn't matter otherwise). You can also find a deodexed rom that you would like. Deodexed roms use less space in your system partition. The last option is to get a download of your rom on a PC and boot into TWRP (3.0.2-0 preferred) and do an advanced wipe as well as your internal storage. Backup everything if needed, then reflash.
Hope any of these helped!
Click to expand...
Click to collapse
Ahhh. I followed the instructions and installed cm13.0 from nels83 ( https://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-13-0-t3342017 )
I guess doing this step:
"Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data"
doesn't actually wipe the system partition clean?
spankycarbowski said:
Ahhh. I followed the instructions and installed cm13.0 from nels83 ( https://forum.xda-developers.com/galaxy-tab-3/development-10/rom-cyanogenmod-13-0-t3342017 )
I guess doing this step:
"Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data"
doesn't actually wipe the system partition clean?
Click to expand...
Click to collapse
Ya, that doesn't wipe the tablet clean, wiping all of that and 'internal storage' does the trick. Glad I could help!
I agree with everyone here. This made a big responsiveness change in the tablet. Thank you!