yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] olifee:
I also did not test it ;). However, it should be comparable to a desktop machine (taking the slower CPU into account). My NTFS-3G experience for several years has shown it is actually pretty fast, but takes up a lot of CPU time if high fragmentation is present. Nevertheless, I think the throughput (with our devices CPU) will still be much higher than writing to SD-card in most cases.

And yes, although Linus said FUSE-filesystems are just toys, http://www.spinics.net/lists/linux-fsdevel/msg46078.html, they are very fast and stable toys in my experience.

I think we will not see an open-source kernel-module for exFAT / NTFS-3G in the near future. For one, there is the licensing-issue (which will be much more of a problem if it is included in the kernel-sources / can be built against them), and on the other hand, it always took some YEARS time until a new filesystem was reliable enough to warrant an accepted kernel module. After all, btrfs is just becoming widely accepted and stable after 4 years of development (and a shorter time in-kernel). And this is expected to be the next-gen filesystem for linux, and as such the focus of development. With the correct mount-options, it should also be nice to SD-cards ;). Maybe there will be some time to try it when kernel 3.1 (with the 'stable' version) comes to our phones.

So for the next years, the FUSE-solution is the best we can get, and for Android, the most compatible one across kernels and devices (it only needs a kernel-dependent kernel-module in addition to whats cooking here, after all). The perfomance graphs by Tuxera on their site even show that their fuse-exFAT is faster than in-kernel FAT, so I guess we should not worry about performance even with the open-source beta implementation. Maybe battery life could be an issue if CPU-usage spikes when copying large files, that might be worth some testing.

I'm personally not switching to exFAT in the near future, but will watch this thread and might do some experiments in some weeks when I have more time :).

Thanks for the good work, smitna! :)
[Galaxy S II Android Development] z3r0n3:
I have some bad experiences with NTFS-3g on my netbook. Trying to transfer a large number of files from my netbook (running Arch Linux) to my external HDD (that is NTFS) and the transfer was slow and my CPU time are always on 100%. That's why I asked if it was tested, because I don't really know if FUSE is suitable for embedded devices. But yeah, the only way to know is to test, and it's still too early for that ;) .

But licensing is really a issue? I know that Linux have module to read a NTFS partition (but not write, this is why we have NTFS-3g) and there was some work for a read-only module for exFAT too (sadly, it didn't get much attention).

Anyway, I'm not switching for exFAT too anyway and I don't know how they aprove exFAT as the default filesystem on SDXC cards, but it's important anyway and will be critical somewhere in the future to have support to this filesystem.
[Galaxy S II Android Development] dildano:
First of all, thanks for your work on this. I was shocked to discover that my SGS2 wouldn't support any filesystems that support large files on external sdcards. I was able to get your solution working in the sense that I could format an sdcard with exfat, mount it, write to it, and unmount it. Awesome! I am having one serious problem though: After editing the vold.fstab and rebooting, I get constant FCs after trying to install any APKs. It doesn't matter if I have my external_sd mounted or not. And these are not apps that are trying to install to the sdcard. Any ideas?

I've got the AT&T version of the SGS2 (i777), but I'm running Siyah's latest kernel. The FCs just say it's the media process.
[Galaxy S II Android Development] smitna:
Sorry for my later answer!

This should be nevertheless a problem with the app2sd service and I have no solution for this. My thread here is only a howto, nothing for the "daily to use"...

I also don't know why there is no other selectable alternative file system for "us users" to use for the external card by default and not FAT32.

The media service depends on the vold daemon to my knowledge. So I cannot recomment this for the default external sdcard, because of the media service scans. If you want to store larger files (e.g. video files), you should better split your sdcard in one FAT32 partition and an additional ext2/3/4 partition. On this partition there is no 4 GB limit. The "media scanner" will not scan the files (videos etc.) on the partition, but you can choose the videos from your favorite player with the file chooser.

Hope this helps you a little bit.
[Galaxy S II Android Development] dildano:
Thanks for the response. I was actually trying out multiple partitions over the weekend to no avail. Granted, I was trying a combination of FAT32 and NTFS. It would actually work for a while until the NTFS partition would appear to get corrupted. I thought about ext2, but my understanding is that Samsung somehow disabled ext* support for external SD cards. Is that not the case? Anyway, I'm surprised that more folks haven't caught onto your work here because storing large files seems to be a fairly common issue for SGS2 users.
[Galaxy S II Android Development] smitna:
I am using an ext3 partition with deactivated journalling and noatime option on the sdcard since months without problems. Of course I have also a FAT32 partition on the card to stay compatible with vold and media scanner. With a start script it is mounted after every phone restart.
[Galaxy S II Android Development] dildano:
OK, I must have misunderstood. So is it just that vold will not allow us to automatically mount ext* partitions? I'll try it with a script as soon as I can get some time. Thanks.
[Galaxy S II Android Development] shadowofdarkness:
I would like to try this, for use connecting my camera which has a exfat formatted sdxc card in it via OTG. But have a couple questions since I can't test at this moment.

1: Do the binaries work on a ICS build (Siyah Kernel) or do they need updated?

2: Do I have to make any vold.fstab changes to prevent FS damage when using a OTG cable or is that just external sd?

3: If I have to make the changes will other devices (not memory) work normal without manual interaction?
[Galaxy S II Android Development] smitna:
Hello, I am still on GB, but I guess it should work on ICS too.

If ICS (or better the vold daemon) has not changed its behavior you have to modify vold.fstab to prevent damages. To do this, you have to disable automounting the exfat OTG device (commenting out the part for OTG and reboot). The other partitions (internal and external memory should work like before). Then mount your camera card manually. But be very careful with your data/pictures!
[Galaxy S II Android Development] WhiteTrap:
Hello, I'm working on an HTC Mazaa with Windows Phone and inside a partition I've found several times the EXFAT header, so I'm trying to mount it, but looks like it's EXFAT 2.0, while your implementation covers only 1.0.

Do you know if it's somehow possible to mount EXFAT 2.0? On Windows, on Linux, modifying your tool, whatever!

Here's the header:

012f7400 eb 76 90 45 58 46 41 54 20 20 20 00 00 00 00 00 |.v.EXFAT .....|
012f7410 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
012f7440 00 00 00 00 00 00 00 00 00 1b 00 00 00 00 00 00 |................|
012f7450 20 00 00 00 36 00 00 00 8c 00 00 00 74 1a 00 00 | ...6.......t...|
012f7460 02 00 00 00 94 01 eb 07 00 02 10 00 09 00 02 80 |................|
012f7470 ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
012f7480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
012f75f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
012f7600 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
012f77f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
012f7800

Thanks!
[Galaxy S II Android Development] smitna:
I don't think that I can give you a good answer, sorry. It's not my tool, it's the exFAT driver from http://code.google.com/p/exfat/, the latest is fuse-exfat-0.9.7.tar.gz and I don't see any notes for a "version 2" in the ChangeLog. Are you really sure about the version? If there is a version 2, I guess it's more than only a change to the header.

I recommend you to post the question in the mailing list https://groups.google.com/group/exfat?hl=en. It is rumored that exFAT works natively on the new S3, but I don't know if this will be true and I have strong doubts that Samsung will release the sources of the driver.
[Galaxy S II Android Development] WhiteTrap:
It's fuse-exfat itself that says the version is 2.0. I'll try on the ML, but looks like there are big differences. If I make fuse-exfat ignore the fact that it's 2.0 it says that there are 2 FAT, which I think non-banal modifications to the implementation.

Thanks!
[Galaxy S II Android Development] WhiteTrap:
Seems that exFAT 2.0 is (or is very similar to) TexFAT.
[Galaxy S II Android Development] shadowofdarkness:
I just wanted to say thanks I just tested this and the binaries works great on ICS 4.0.3 (LPG) using Siyah Kernel.

I plugged in my Panasonic Lumix TS2 digital camera with a 64GB sdxc card and was able to mount it fine on my S II with a OTG cable.
[Galaxy S II Android Development] smitna:
Fine and thanks for sharing your experience! It's good to hear that the driver is useful for you.
[Galaxy S II Android Development] omar300:
I have galaxy s3 and the 64 gb exfat formatted card works on the stock rom of it.

But when i switch to custom rom which are not based on galaxy s3 own stock rom the card stops working.

No other rom beside galaxy s3's own come with exfat driver. so i was wondering if i use this in custom rom as for now its Cyanogenmod 10, would this mod of yours work?

please let me know.

thanks.
[Galaxy S II Android Development] smitna:
Theoretical the driver and tools should work with any ROM, because there are no explicit ROM-dependencies, only kernel related stuff (if any). But the modifications for the vold daemon are necessarily if you want to use an exFAT formatted INTERNAL card.
[Galaxy S II Android Development] svs57:
Do anybody know how compile fuse-exfat-1.0.0 (http://code.google.com/p/exfat/downloads/)?

I don't see configure file in sources:

~/fuse-exfat-1.0.0/libexfat$ ls

byteorder.h cluster.c exfatfs.h exfat.h io.c log.c lookup.c mount.c node.c time.c utf.c utils.c version.h
[Galaxy S II Android Development] shardul_seth:
Here is the latest version 1.0.1 (at the time of posting) of fuse-exfat and exfat-utils for android arm phones.. Thanks to the OP for the detailed instructions.

Please read the first and second posts of this thread before downloading! By downloading, you agree that you are responsible for any data loss/damage or legal issues.

Download
[Galaxy S II Android Development] svs57:
I need your help.

I used "mount.exfat-fuse" with custom kernels which don't support exFAT (SGS3)

I just create script in /etc/init.d/ that mount ext. SD

mount.exfat-fuse -o uid=1023,gid=1023 /dev/block/mmcblk1p1 /storage/extSdCard

This works fine. Android recognize ext SD.

But with latest yank555 3.1h kernel I have problem.

Ext. SD mounted while boot. But android show me message that ext SD is empty.

I login to phone via adb shell.

Ext SD is mounted. I see content of card. But android told that card is empty.

Do you have any ideas why it's happen?

I downgraded yank555 kernel to 3.1g. Everything works. Android show me ext SD.

PS

I found that with latset yank555 when android tell me empty ext. card

Settings - Storage - Prepare ext SD

Then card is appeared.

Will be nice do the same in init.d script

But I don't know how...
[Galaxy S II Android Development] shardul_seth:
Just use

mount.exfat-fuse -o rw,umask=0 /dev/block/mmcblk1p1 /storage/extSdCard

Should work..
[Galaxy S II Android Development] svs57:
It works. But Android doesn't see card.

PS

Found where was the problem.

Script /etc/init.kernel.sh includes in first lines wait while Android is UP.

I put mount ext SD before this waits.

Now it works :)
[Galaxy S II Android Development] HMkX2:
Thanks to everyone in this thread for the compiling - that's slightly beyond my area of expertise. But I was able to refine it for the Galaxy S3 running a CM10.1 nightly - works perfectly!

@smitna - I wasn't able to locate the problem within vold, unfortunately. But I did locate the cause of the problem exactly: 3 4-byte segments in the header -- not just the one you noticed at the top. I've written it up in the post here:

[HOWTO][exFAT][CM10.1] Working 64GB ext sdcard with fuse-exfat (1.0.1) + FIX broken
[Galaxy S II Android Development] svs57:
I use exfat_arm_binaries_v101.zip on SGS3 with Android Revolution HD 22.1 based on XXEMR2 and Yank555 3.2 kernel.

Everything works fine. Never have this problem.

Can you tell me which version of exFAT fuse do you use? What ROM do you use?

PS

/system/etc/vold.fstab doesn't modified

## Vold 2.0 Generic fstab

## - San Mehat (san@android.com)

##

#######################

## Regular device mount

##

## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>

## label - Label for the volume

## mount_point - Where the volume will be mounted

## part - Partition # (1 based), or 'auto' for first usable partition.

## <sysfs_path> - List of sysfs paths to source devices

######################

#storage_struct = series, "/storage/sdcard/extStorages"

#storage_struct = parallel

{

supported_exfat = yes

}

dev_mount sdcard /storage/extSdCard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
[Galaxy S II Android Development] Phil3759:
Here's my trial to port exfat/fuse 1.0.1/2.9.2 to bionic as static binary:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/3faf6270b7cc261925aab6e1ad9237426675ad10

libdl functions I added are defined from what Android NDK/CM-10.1 has. So, it shouldn't break anything

Missing pthread calls could probably be deleted, but I went with that alternative as it was already used on a previous port (stackoverflow topic and a github commit from old 2.8.7 fuse)

At the end, it shouldn't matter since twrp uses the bionic libc and that implementation doesn't have these pthread functions

So, I feel it is a good port.

You get an exfat-fuse of about 190kb stripped which is great to fit in recovery partition

Now, the issue:

There are some hard coded /bin/prog functions inside fuse

There is also that /usr/bin entry in mount.c

The resulting binary fails to find /bin/mount on which it relies. This is obvious since we have it in /sbin. TWRP seems to symlink things there

I tried symlinking /bin to /sbin, but it then fails with a busy device message. Maybe it is because I am using Samsung ko modules too. But the static non bionic binary does work perfectly!

Here's the binary I got for your testing

http://www.mediafire.com/download/mmgp5le6bpc5f7n/exfat-fuse.zip

If someone can have a look and an advice on how to fix the path issues, it will be appreciated.

Please do not leech only. If you fix it, do share the source and commit to the github or here

Meanwhile, I am also working on it, but have very little time sadly
[Galaxy S II Android Development] Lurker0:
I've created a project to build exFAT and NTFS drivers using Android NDK toolchain (any supported OS), which is more easy than Linux and CodeSourcery:

http://xdaforums.com/android/development/exfat-ntfs-fuse-drivers-easy-build-t3126413

There are ready to use binaries built from the latest sources for ARM and x86.

I post here because this is the most referred place for exFAT for Android.
[Android Themes] Swind3r:
Hi all,

I love the interface Sense 3.5 but the software sms is quite limited.

I decided to install Gosms Pro. Is there a theme similar to Sense?

I hope you can help me.
[Android Themes] Swind3r:
Nobody ???

Okay...........
[Android Themes] flamepanther:
I'm looking for the same thing right now, but so far all I've found is this thread.
[Android Themes] twizt3d:
also looking for a go sms -sense theme, even a 3.0 or older would be cool, theres a go launcher sense 4 theme which is pretty cool, trying to find some matching themes for go sms and go contacts myself, anyone know of anything? I found the go widgets sense 3.0 themes. but these do not theme the 2 additional apps, just widgets.
[Kindle Fire Themes and Apps] esoh:
I'm looking for a unified email app that I can also use with Exchange/Activesync and Yahoo boxes. From what I can tell, KF mail app doesn't include Activesync support (yet, or ever?). I use Touchdown on my Nexus S 4G but frankly, I don't want to pay another $20 plus I'm looking for a unified inbox.

I also have a Nexus S 4G and the mail app can do this (although I don't love it because it has some major restrictions, mainly no warning before delete). Does anyone know if I could take the apk from the Nexus and install onto Fire? Has anyone done this?
[Kindle Fire Themes and Apps] EABonney:
You can try to side load the apk, it won't break anything, worse case is it won't work.

Why can't you just use the license from your Nexus for Touchdown on your Kindle? Just curious.

-Eric
[Kindle Fire Themes and Apps] esoh:
I could, but my preference is to have one inbox for Exchange and Yahoo. TD only does Exchange/ActiveSync accounts.

On the license moving, I guess I need to read up more on the licensing policies. I thought you could only use licenses on one device/machine.
[Kindle Fire Themes and Apps] BriDroid-74:
Check out Enhanced Email. Its on the Amazon and Aneroid markets and is only $9.99. I like it a lot. Its based on the stock aneroid mail app, so it catches a lot of heat? The support from the dev is awesome though!
[Kindle Fire Themes and Apps] esoh:
Thanks. That is one option I'm looking at, although I was hoping for a free option which is why I was considering the Google Mail (not Gmail) apk. I won't be doing that much emailing on the KF, which is why I'm shying against spending any money at all. I'm glad you like it though, that's a + I suppose.
[Kindle Fire Themes and Apps] EABonney:
Just fyi...I read in the reviews of Touchdown that someone else bought a tablet and put it on there and they where allowed to use the same license for their phone and the tablet. So you might want to look into that.

-Eric
[Kindle Fire Themes and Apps] andTab:
Solution here:

http://xdaforums.com/showthread.php?t=1376386
[T-Mobile LG G2x] roadtrip72:
Does the T-Mobile G2x come with the Carrier IQ rootkit installed? If so, I'd like to block it. I'm running a rooted Android 2.2.2 (I like the camera) and don't want to do anything that would prevent me from possibly upgrading to ICS should it become available. So where do the stock rom users stand?

-roadtrip72-
[T-Mobile LG G2x] adampdx:
I would also like some more information on this. I'm running CM7, but what of the other stockish ROMs? Is this something that is removed by the devs?
[T-Mobile LG G2x] player911:
Well they did have LogMeIn apps installed in the stock roms, but didn't have actual launcher icons for them... kinda scary.

CM7 based roms won't have anything like this installed as they are built from the ground up. Stock-based roms, which I don't think so, still could. Would be nice to get a real answer.
[T-Mobile LG G2x] da-pharoah:
Ok so I have been researching this for the G2x and not really found much positive test results. I'm currently running 2.3.3 stock everything and I downloaded the apk from here: http://xdaforums.com/showpost.php?p=17612559&postcount=110

From my results the main apk for ciq was not found and nothing ran nor was logged. So I guess no, the g2x stock doesnt have ciq installed. Anyone else confirm this?
[T-Mobile LG G2x] fabricatedhero:
Well you can always check and or get rid of the Carrier IQ thing that tracks your information.

You need a rooted phone to do so and then go here to download the app because it is not on the android market.

http://xdaforums.com/show...&postcount=110

*Note: do a backup of your phone before you do this just incase. I haven't checked if its on our phones just yet but more than likely it probably is

**Update: Having trouble with the app on my g2x with stock rom/faux froyo kernel.05. It keeps giving an "Error copying Busybox" so the App won't update to the pro version that you need. Waiting for Dev response
[T-Mobile LG G2x] lotherius:
Does not look to me like CiQ is on the 2.3.4 Rom, but it is possible it may be on the 2.3.3 Rom... Most concerned about LMIRescue.apk and LMIRescueSecurity.apk ... both of those are troubleshooting apps for T-Mobile which in the past has been suggested stands for "LogMeIn"... sounds a lot like ciq or similar. These files were not included in the 2.3.4 Tracfone leak. I have not, however, actually checked a running 2.3.3 with the tools TrevE offered. I did check my copy of the 2.3.4 and it did not find the CiQ service or binary. That is not to say it may not be obfuscated in such a way that TrevE's tool isn't aware of yet though.

However, one thing to note is that a couple of the app usage logs it pulls up I am pretty sure are NOT related to CiQ, and have been around in almost every build of Android since the beginning - specifically the log that tells how much time you've spent in each app. What is IMPORTANT is, is there an app on the phone that's sending the data. That, I can't say for sure.
[T-Mobile LG G2x] freakboy13:
I saw that article on CNN and was like effing great. After I rooted my phone and saw that logmein crap I froze that right away, lol. Somehow didn't sit with me. Android is great, but let me tell you do NOT trust Google and what they do. I am convinced there's something underlying and sinister about them.

Google=Android

Cell phone=giving up your privacy

I'm going to freeze that lmi crap thing now as well.

I garuantee the g2x has the ciq but its probably hidden or it IS somehow related to logmein. 1984 wasnt a story it was a prophecy. Scary indeed.

And I'm on stock froyo and rooted.

meh...
[T-Mobile LG G2x] jboxer:
No CIQ in 2.3.4 but it collects usage stats and periodically sends them to Google. Not sure how to stop that behavior. Also, many of the apps in the Android market use Google's SDK to collect their own usage stats and the apps send them to the devs. They say it is to improve their apps. That is why most apps have permission for network data, even though the app doesn't require network data to work.
[T-Mobile LG G2x] lotherius:
Isn't there an opt out for Google analytics during the setup wizard that everyone skips when you first set up the phone after a wipe?
[T-Mobile LG G2x] r0zj0k3r:
just

Its A work around. But I install Lbe and droidwall or prdroid. With pdroid and Droidwall you can lock down pretty much all services (need root). Lbe is OK but not nearly as good as pdroid. This of course would be ideal for your random Apps that abuse internet use or private data
[HTC Sensation XL] orb3000:
In the meantime we have a dedicated sub section please all your questions must go in this thread, those one found in other sections will be closed.

Thanks for your help
[HTC Sensation XL] zameer022:
hi, RUU 1.05.708.6 for sensation XL is Available
[HTC Sensation XL] jammysunny:
Whats new on it?
[HTC Sensation XL] zameer022:
sorry , i mean to say is i am looking for that, any help pls
[HTC Sensation XL] Loushi:
rooted the phone..

recovery.img flashed..

boot.img flashed..

reboot into recovery..

wipe data/factory reset..

and then flashed RCmix3D v.12

just as requested....

and i got stuck in the first boot page (white HTC page) :(

wipe data/factory reset again..

fastboot > factory reset..

and im still there

any help?
[HTC Sensation XL] jeandujardin01:
you have to flash the Chinese ROM 1st -> boot it -> wipe -> then flash RCmix3D
[HTC Sensation XL] Loushi:
ill flash it and see what will happen

regards,

---------- Post added at 09:26 AM ---------- Previous post was at 08:50 AM ----------

sorry for bothering,,,

fastboot boot c:\runnymede_ax918_111511_101713\file.img <<-- is this the right command to flash the rom?