Considering Android is based on Linux, albeit with an ancient kernel, does it support XFS file system? I'm guessing it formats the microSD card as any of the extended file systems (2, 3 or 4) but if it does support XFS, I'd prefer to format it as that FS.
Xfs on android (ported for sdcard)
Update: I've attached clockworkmod with support for xfs(or any other file system the kernel supports) all i did is put my kernel and modify /etc/recovery.fstab ). just untar it ,go to bootloader menu and do fastboot flash recovery...
forum.xda-developers.com
I saw that topic but it's 10 years old. I was hoping for more recent answers.
Why ? For what purpose exactly ? If you want better performance use an A2 microsd card. If you want a better filesystem try exfat , the xfs you can try to format it on Linux and see if the Android will work with it, however I don't recommend that, could introduce risk.
Check out ssdfs if you are into dev stuff however without GPT-5 I can't foresee much interesting happening in filesystems and storage handling due to complexity.
Network_Pro said:
Why ? For what purpose exactly ? If you want better performance use an A2 microsd card. If you want a better filesystem try exfat , the xfs you can try to format it on Linux and see if the Android will work with it, however I don't recommend that, could introduce risk.
Check out ssdfs if you are into dev stuff however without GPT-5 I can't foresee much interesting happening in filesystems and storage handling due to complexity.
Click to expand...
Click to collapse
For faster uploading of files. Ever since I formatted my storages to XFS they move/copy files between each other with the maximum speed their manufacturer says they can do. When they were ext4, copying 50 GB from one device to another was like on Windows - start fast then drop to a ridiculously slow speed, like 20 MB/sec, for instance. And I'm getting the same slow performance RN with the microSD card formatted by Android 12. I wanna upload 400 GB to the SD card but with the current file system I'll never have the 150 MB/sec the card's manufacturer says it can reach for writing. Which means I'll be uploading these 400 GB a whole year. I barely managed to upload my music which is 85 GB and it took me 3 hours to do that.
IDK how to format the microSD card on Linux. I don't even know if that's possible, bc GParted doesn't detect the phone as a device at all - even when it's mounted.
Ah here we are again trying to overcome corporations limitations they imposed on us by their retardation.
Well well well. Whos decision was it to Not use XFS in the first place? Give me a name... Someone from Google who was responsible for Android? Someone from the Phone Device manufacturer? The sd association for not informing developers about a correct filesystem? The makers of ext4 probably sponsored by Redhat ?
They are all GUILTY if you ask me. GUILTY !!!
They should give us our money back for all their crappy products !!!
We should start a class action law suit against all of them, for all of their bull**** limitations, separately for their retardation, and separately for their LIES in their advertising.
How do you know XFS is faster if you can not format the sdcard on Linux?
To format a sdcard on Linux - you connect Only the sdcard. After it's formatted - insert the sdcard in the phone and see if the phone can work with it, or not.
1.)SD cards are usually formatted with exfat.
2.)You will have to build your own kernel with explicit XFS support to enable XFS support.
Now I don't remember, but you can multipartition SD card
Keep the first partition as exfat, the second partition as XFS or ext4 or btrfs.
and loop mount it in a directory.
It's a convoluted process and not sure if it is worth the hassle.
Related
This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device).
Mountpoint is:
/mnt/sdcard/usb<disk-number>-disk0
Known issues:
- NTFS volumes are mounted read-only, this has been explicitly added to the vold to prevent data loss or filesystem corruption until we know that the patch is stable.
Tested on FolioMod v1.3c
Installation:
copy zip file to your sdcard, rename to update.zip and flash using recovery.
vold-update-0.2.zip - this is the patch for vold containing ntfs support
vold-rollback.zip - rollback to default FolioMod 1.3 vold
source-0.2.zip - source code for updated vold
v0.1
- Initial release
- Ntfs support, multiple disks working
v0.1.1
- make sure that the mount point directory exists, create if necessary
v0.2
- multiple partitions are working
- fixed asec handling as discussed
- mount point directories are removed, when unmounting disk (if empty)
I know vold also handles sdcard + multiple usb stick is that part still included?
and the strange vold.fstab with wildcards? otherwise it will be hard to use for a toshiba rom, i think.
Yes this should all be still included, until now I had no issues with my sdcard.
What the patch does is try to mount everythin with FAT like before, if that fails, it tries NTFS.
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Still need to figure out how to use this, hope to get a new disk on Monday, so I can test that.
weeds2000 said:
The vold.fstab is still included, only change is what partitions should be mounted, this was 'all' before and has been changed to 'auto' (as the 'all' seems to be a toshiba addition)
Click to expand...
Click to collapse
Could that also help recognizing some strange formatted SD cards? E.g. I have a digicam (Panasonic) that modifies the FAT32 somehow that the folio tells me the card is defective (but still works perfectly fine in Windows or the Digicam)?
I doubt it, as nothing has changed for sdcard.
But as this vold is compiled with additional debug output you may as well trry to use it. Maybe the output will give some more information on what is going wrong.
But I guess this is because your cam actually uses the "secure" part in your Secure Digital Memory Card. See http://en.wikipedia.org/wiki/Secure_Digital#DRM_features for more info on that.
Very interesting! Thank you !!
Tested with FolioTNT 4.0a and 2 usb sticks (16 and 8 gigs) and working perfectly on both
Great job
Is write supported already or is only for read?
Can large files be read?!?! (i mean no laggy?)
Thanks
Great job, thank you very much Mr. Weeds!
OK partition support is somehow working now, but not really a solution I like to release.
Looks like vold was not intended to handle that.
The main reason for this post is, that the handling of /mnt/asec and /mnt/asec_secure is somewhat bad (again vold was not intended to even handle multiple external storage devices at the same time)
Just to make sure anyone know what that is: Apps2SD stores the packages in that folder.
At the moment vold will create (and mount) an asec container for every storage device attached to the folio. So if I insall an app (or move it manually) with SDCard inserted it will use the asec dir of the SDCard. If I install an app without SDCard it will use the asset directory of the internal storage.
The problem is it seems I cannot change on the fly between those two directories. If I unmount SDCard /mnt/asec does not contain the package if put there. So I need to take out the SDCard and reboot the device.
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
The one thing I can think of is creating a selection setting within the settings app where I can select which device should be mounted as primary SDCard.
If that is switched the systrem may copy contens from asec to the new device.
So the layout of /mnt may look like that
/mnt/sdcard (linked to /sdcard) - the primary sdcard device as selected by the user (defaults to internal storage)
/mnt/sdcard2 - well, the other one (either internal or sdcard depending on what the first device is)
/mnt/usb-storage/usb<disk-number>-disk<partition-number> - hdd's mounted over USB
Just waiting for anyone to come up wither other/better ideas...
weeds2000 said:
Fixing this behaviour would be quite simple. The question rather is where to put it?
Internal storage or SDCard?
The same question goes for what should be the default SDCard (i.e. the one mounted under /sdcard, the one where apps download their resources). Internal Storage or external SDCard.
Just waiting for anyone to come up wither other/better ideas...
Click to expand...
Click to collapse
proper behaviour would be internal storage for apps.. as its not nice that the apps you install disappear if you remove the sdcard or usbsticks.
i noticed this problem early on..but no one mentioned it as a problem.
do you see why the .android_secure mountpoint does not happen?
i think somehow this relate to the problem of downloading paid apps.
If this is OK for everyone, then this would be a much simpler approach, so /sdcard and /mnt/sdcard always point to internal storage.
If someone needs more storage (i.e. for downloaded resources) we may simply create a tool wich does some linking (e.g. link /sdcard/gameloft to /sdcard2/gameloft)
The mount point for asec_secure exists as well, 2 times with the same issues as asec. I don't know if this is related to paid apps. According to the logs I get a 403 response from the google servers.
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
weeds2000 said:
Is there any specific reason, why SDCard is put under /sdcard/sdvcard-disk0?
I'd like to move that to /mnt/sdcard where usb-storage will go as well.
Using that approach it might be unessesary to unmount the external storage when a USB-connection is made.
Click to expand...
Click to collapse
normally its a good reason.. the Toshiba filemanager looks at a location where all users got access..
no regular user would look into a /mnt/sdcard2 unless the toshiba pointed to the location.
so /mnt/sdcard offers both internal storage + sdcard + usbstick here which i think works well and all users easily find it as its within the sdcard default location.
i dont think that logic should change..
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
weeds2000 said:
updated to 0.2 write support is still disabled.
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
do you consider this ok to be included in a new update?
I of course let you approve if its ok for regular use..
denver-tempor said:
From weeds2000:
"This patch allows mounting of NTFS volumes through vold (i.e the disk is automatically mounted when pluged into the device)...."
------------------
This patch was tested by me on FolioMod v1.3c.
It readed well one HD NTFS, and recognized all of SD cards that were not recognized before.
Many thanks.
Click to expand...
Click to collapse
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Nemo0815 said:
You have NTFS formatted SD Cards? Or FAT cards which weren't recognized before?
Click to expand...
Click to collapse
I have some SD cards (several trades and capacities) FAT formatted that weren't recognised before applying this patch. Now, they are.
Also, I tested a 2.5 USB HD, NTFS, and it was readed without problems.
weeds2000 said:
As I always used NTFS-3G I cannot tell if the driver implementation is reliable and complete. However I think it is, as my knowledge from incomplete write support is 3 or 4 years old...
Click to expand...
Click to collapse
OK, so I was wrong, this is from the kernel documentation on NTFS Write support.
This enables the partial, but safe, write support in the NTFS driver.
The only supported operation is overwriting existing files, without
changing the file length. No file or directory creation, deletion or
renaming is possible. Note only non-resident files can be written to
so you may find that some very small files (<500 bytes or so) cannot
be written to.
While we cannot guarantee that it will not damage any data, we have
so far not received a single report where the driver would have
damaged someones data so we assume it is perfectly safe to use.
Click to expand...
Click to collapse
So it looks like ntfs-3g is the way to go, this will take some time however.
@dexter
I played around with various disks today, watched a movie, etc... Seems like everything is OK, so I would consider 0.2 be a candidate for regular use.
I will include this in the next update..
You seem to have many downloads, but not really any complaints
that should tell us something.
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Pinging this thread for IMPORTANCE
I very much hate FAT32, yet am forced to keep using it in my external SD card on phone in the same way. I would love to see all devs add full ROM support for reformatting and mounting external SD cards with full suite of OS supported file systems. How is it OS supports EXT4 yet I am still bound to FAT32 on SD card !!!!????
This is very important to me, and should be to you all too. we need file system journaling and large file support!
Wouldn't hurt to build in advanced visual presentation for formatting/converting any partition on phone from/to all supported types with ability to setup swap partitions. I know I ask for a lot.
------Running--------
SPH-D710, Starburst ROM v2.0, EK02 modem, custom startup screen/sounds
---------------------
cpgeek said:
I have a Samsung galaxy tab 7" currently running the latest version of the overcome rom (but i'm not married to it if others here have better recommendations), and for whatever reason, whenever i try to format my newly purchased 32gb sd card that i've placed inside, it wants to format it in fat32, which is one of the worst filesystems for data integrity ever devised (no journaling or data protection features of any kind). I have attempted to use my fat32 formatted sd card for a few ebooks that i've got, but when i move them from one folder to another, and then reboot, I get a lost+found directory full of corrupt, errant data and an empty folder where i attempted to move my stuff... this is, of course, unacceptable.
first off, why is fat32 used for the sd card in the first place when the system clearly uses rfs by default (upgraded to ext4 by my overcome installation), and anyone who is technologically inclined knows the pretty extreme limitations of fat32 (4gb single file data limit, no file protection mechanisms)?
and secondly, how do I fix this problem? the tab doesn't seem to accept my sd card when i format it in ext4 using my ubuntu desktop and an sd card reader, nor does gingerbread seem to have any advanced mount controls at all (including strangely the lack of mount support for cifs/smb, which i think is crazy as well but probably well out of the scope of this particular post).
tldr: external storage support on gingerbread is archaic and broken, how do i fix it for regular use?
Click to expand...
Click to collapse
Hi. I Used gparted to format my sdcard to ext3. I booted from a usb stick and my 8gb sdcard was connected via a PSP with a MSDUO to Microsd adapter. When i inserted it into my Tmobile G2X the phone didnt recognize the sdcard. Does anyone have any ideas whats wrong?
You cant use your sd for mass storage with it formated in ext. The only time ext is used on your sd card is if you are using apps2sd and even then just a small portion of the card is ext and the rest is fat32.
Crap. Thank you. I looked around, but didnt find aything about THIS.Thank you.
is there anyway to add support for ntfs to the OS or kernel. As i have heard the kernel doesnt support ntfs, but Linux can read the file system. So my question is what has to be done to accomplish this.
m_malyszko said:
is there anyway to add support for ntfs to the OS or kernel. As i have heard the kernel doesnt support ntfs, but Linux can read the file system. So my question is what has to be done to accomplish this.
Click to expand...
Click to collapse
I'm not saying it's impossible, but it might not be worth it. I'm sure others have thought about this before, but it still hasn't been done, so I'm guessing there's a good reason for that.
Fat32 is native to android and it's probably going to stay that way. You should be good unless you have files bigger than 4gb each that you want on your sd card
well i actually wanna be able to download huge files, 8GB, at my work place. And we can only have phones at work, and they dont even know that were using their wifi or that we have cell phones.
So, I've got a new SanDisk 64gb Class 10 micro SD and want to use it for app and data storage, as well as for nandroid recoveries.
Unfortunately, the stock format - exFAT - is not recognized by many apps or by any of our custom recoveries.
Now, you've got two virtually bulletproof options to reformat that disk to FAT32 ... you choose your poison.
**************** HARDCORE *******************
I call this the "Use your teeth to open that bottle of beer" method ...
1. Place the card in your PC's card reader and determine the drive designation (i.e., G:\, H:\, etc.)
2. Download the program Fat32Format to your PC from here: http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm. The download link is actually situated about mid-page.
3. Unzip the downloaded file with 7Zip (which you can get here: http://www.7-zip.org/)
4. Navigate to the folder with the unzipped fat32format.exe file; while holding down the [Shift] key, right click on the folder.
5. A menu should popup. Scroll down and click on <Open Command Window Here>.
6. You are now in virtual DOS (.. don't be scared ..)
7. Enter the following command sequence> fat32format h: (or whatever drive designates the location of your SD card)
8. You will be prompted to confirm a wipe and format of your SD card. Type "y" and hit enter.
9. In approximately 5 seconds, your SD card will be FAT32 formatted.
10. Remember to follow whatever procedure you normally would before removing a drive from USB.
***************** EASY PEASY ******************
This, on the other hand, is the "my hands are as soft as a baby's bottom" method ... (thanks to lynkdead)
1. Place the card in your PC's card reader and determine the drive designation (i.e., G:\, H:\, etc.)
2. Download the fat32format utility in GUI version from here: http://www.ridgecrop.demon.co.uk/guiformat.exe. Click on the picture to retrieve the file.
3. Launch the guiformat.exe.
4. Choose the drive that corresponds to your SD card.
5. Choose the size of the SD Card you are formatting.
5. Check the Quick Format box.
6. Press Start.
And voila !!!
Enjoy your new SD card !!!
Pj
Phoenix, AZ
p.s. Needless to say, this process will erase all data on the card. Also, you will no longer be able to transfer files larger than 4gb to the card.
http://www.ridgecrop.demon.co.uk/guiformat.exe
If you use the GUI version from the same website it's WAY easier.
Just launch the .exe, choose the drive that corresponds to your SD card, make sure Quick Format is checked, and press start.
I thought I'd give people to a chance to explore Command Prompts as sort of a baby step to ADB or Terminal Emulator.
The GUI method works just as well. :good:
Thanks for the heads-up ... I edited the OP to reflect both options.
Pj
Phoenix, AZ
Sorry, I don't download and run any unknown/noncorporate apps, for the fear of them being trojans. Do you have any other methods?
Can one not format a mounted sdcard to fat32 on their pc by using "right click/properties/tools/format" or something? Does Microsoft not provide an official tool to format an sd card?
The functionality is built into Windows, through the command prompt. It is, however, excruciatingly slow.
Fat32formatter is open source and has proven to be the only reliable method of formatting large drives without spending any money.
Let us know if you find a good alternative ...
Pj
Phoenix, AZ
pdinphx said:
The functionality is built into Windows, through the command prompt. It is, however, excruciatingly slow.
Fat32formatter is open source and has proven to be the only reliable method of formatting large drives without spending any money.
Let us know if you find a good alternative ...
Pj
Phoenix, AZ
Click to expand...
Click to collapse
So, basically - use command prompt on windows7? "format X: /FS:FAT32", where "X:" is the sdcard drive name.
Right? (just reading "format /?" in windows)
That should work, though others have reported trying the native Windows format command and later running into trouble with a damaged disc prompt when the card was inserted into the phone.
Pj
Phoenix AZ
nabbed said:
Sorry, I don't download and run any unknown/noncorporate apps, for the fear of them being trojans. Do you have any other methods?
Can one not format a mounted sdcard to fat32 on their pc by using "right click/properties/tools/format" or something? Does Microsoft not provide an official tool to format an sd card?
Click to expand...
Click to collapse
If you don't trust it you can always upload the files to VirtusTotal, run them against your own virus scanners, or just rely on the handful of people here who have run the program without issue.
In Windows if you try to simply right-click format it doesn't give the FAT32 option, only exFAT. You can try it through the command line, and it appears to work, though once you actually try to use it CWM throws a fit. Other tools that I've tried also don't work (likely because they simply do exFAT even though they say FAT32, since the difference usually doesn't matter).
This tool works, I've had zero issues, and it hasn't tripped any of the virus scanners I've run against it.
I don't have a 64g card yet, but only my old 16 for more. Why not have the s3 format your card. I did that with my 16g and its a fat32.
Sent from my SPH-L710 using xda app-developers app
... NEVER use fat32 with anything above 32 GB.... there is a reason for this it is designed for a max of 32GB you need to use the phone to format it. it will become a newer ext partition.
Either format it in the phone fully booted into Android, or download EaseUS Partition Master (free) & format it as a Primary Drive FAT32 file system. Either way will work.
Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 Pro, the SGS3 is on my hip...
drksilenc said:
... NEVER use fat32 with anything above 32 GB.... there is a reason for this it is designed for a max of 32GB you need to use the phone to format it. it will become a newer ext partition.
Click to expand...
Click to collapse
How u r so wrong. You wont be able to use asop cm9 or cm10 when released. unless the 64gb card is in fat32 format. the only disadvantage I see is the 4GB file limit.
why wouldnt cm9 be able to use ext4 thats what the 4.0 version of android was built on and why the partitions can scale.
drksilenc said:
why wouldnt cm9 be able to use ext4 thats what the 4.0 version of android was built on and why the partitions can scale.
Click to expand...
Click to collapse
It's not a matter of a specific ROM being able to read it, it's a matter of external storage not being recognized by your recovery(only sees fat & fat32 at /mnt/sdcard), and the OS cannot see external storage formatted as ext2/3/4, only FAT, FAT32, & exFAT.
not my best explanation ever
Sent from my SPH-L710 using Tapatalk 2
carhauler1969 said:
It's not a matter of a specific ROM being able to read it, it's a matter of external storage not being recognized by your recovery(only sees fat & fat32 at /mnt/sdcard), and the OS cannot see external storage formatted as ext2/3/4, only FAT, FAT32, & exFAT.
not my best explanation ever
Click to expand...
Click to collapse
You sure about that last bit? I was going to reformat my 64GB extSD as ext4 (when I got around to it), since Microsoft's exFAT is patent FAIL, and it's the only other fs the phone supports that'll handle files larger than 4GB. No good reason why it shouldn't be supported on stock touchwiz or on CM10||AOKP
drksilenc said:
... NEVER use fat32 with anything above 32 GB.... there is a reason for this it is designed for a max of 32GB you need to use the phone to format it. it will become a newer ext partition.
Click to expand...
Click to collapse
As I noted above, none of our custom recoveries recognize the exFAT format, which means that you cannot boot, backup or flash from that giant 64gb card. Many users have reported the same problem with their favorite apps ...
No one has reported issues with a FAT32 64gb card , so I don't think this is an issue.
Either way, it is your choice ...
PJ
Phoenix AZ
zmore said:
You sure about that last bit? I was going to reformat my 64GB extSD as ext4 (when I got around to it), since Microsoft's exFAT is patent FAIL, and it's the only other fs the phone supports that'll handle files larger than 4GB. No good reason why it shouldn't be supported on stock touchwiz or on CM10||AOKP
Click to expand...
Click to collapse
Try it and report back ...
PJ
Phoenix AZ
This convinced me to go FAT32: http://www.epiccm.org/2012/06/why-not-exfat.html
I suspect the phone respects your card's native format. My 64gb SanDisk remained exFAT formatted even after running it through the phone. Thus, the need to format it with my computer. If your experience is different, please let us know.
PJ
Phoenix AZ
pdinphx said:
This convinced me to go FAT32: http://www.epiccm.org/2012/06/why-not-exfat.html
I suspect the phone respects your card's native format. My 64gb SanDisk remained exFAT formatted even after running it through the phone. Thus, the need to format it with my computer. If your experience is different, please let us know.
PJ
Phoenix AZ
Click to expand...
Click to collapse
This is what I wanted to be certain on cards >32gb. I know Team Epic posted points on how to avoid exFAT, but only for 32gb that you can run thru the phone.
nabbed said:
Sorry, I don't download and run any unknown/noncorporate apps, for the fear of them being trojans. Do you have any other methods?
Can one not format a mounted sdcard to fat32 on their pc by using "right click/properties/tools/format" or something? Does Microsoft not provide an official tool to format an sd card?
Click to expand...
Click to collapse
I can confirm download is not a Trojan. I did the second option and it worked perfect took 5 seconds.
I just noticed that SD cards formatted in NTFS via USB work on the Shield tab (Lollipop). So, would it also work in the SD card 1 (slot)?
You need to mount the sdcard in ntfs mannually with third app.
Sent fro SomeFon
No. It also works in the SD slot.
What device? He he.
Sent fro SomeFon
Shield.
I am searching an android device installed upon ntfs, due to several hardware concerns that ext2/3/4 causes in emmc or ssd disks, i experienced bootloop, only because an ext2 error on my sdext2 partition, i took out the sdcard, and the phone booted normally.
Ext any kind, i believe exfat is brother of ext, Nevermore i pretend use.
After i learned that kingston taiwan's original notebooks ssd disks, are usinf ntfs, and i still never seen any notebook with standard linux installed, think with me: may be why?
Hm.
Now, i modded the link2sd scripts to start sdext2 in a ntfs partition, 2Giga is the minimum for good ntfs usage, and what i am experiencing, is not comparable with any device that i had, is crazyly fast, stable, and no errors.
Sent fro SomeFon
See this:
Ntfs breaks cached ads.jar in various apps.
Anyone heard somewhere , the gogle will change the adwares method?
Ha, may it because why?
See the pictures:
Youtube, running on sdext2-ntfs
And the File explorer showing the youtube cache folder,
The ntfs security, detected remote code in cache.
Called by ads.jar 1 & 2
The ntfs security, stopped these jars, and renamed to .fusehidden... that you see on the picture.
So?
What more the damn ext1/2/3/4 Done for away desteoying devices via malicious cached dexes and jars codes?
Sent from SomeFon