Develop Bugs

Combining internal and external sdcards as one storage unit? Android LVM?

Basically what im getting at is would it be possible to combine both storage units to where the os can mount them as one? In traditional Linux I would use LVM2.

Anybody? You think something like this would've been done already but I haven't found any directions on Google just a project page.

dude, desktop computers require an entire card in order to do this kind of stuff, it's called raid, and android isn't programmed to support it
Sent from my SPH-L900 using xda app-developers app

That is incorrect. Try looking into what an LVM actually is before attempting to answer. RAID is something completely different.
Edit: not trying to be a **** but your post had a condescending tone to it.

schnowdapowda is correct, LVM would be able to do this just fine if Android supported it, but as far as I can tell the Android system doesn't have the kernel modules or systems in place sadly. Otherwise it'd be no problem making a physical volume from the two SD partitions, then a volume group and logical volumes.
One down side is you would run into system overhead while the slower SD card is keeping LVM from writing to faster on-board "SD card" partition space.
I just run the following at boot time, and it swaps the internal and external cards... Note this is with the Perseus kernel.
Code:
busybox mount -o remount,rw /
busybox mount -t exfat -o umask=0000 /dev/block/vold/179:49 /mnt/sdcard
if busybox mount | busybox grep vold/179:49; then
busybox mount -o bind /data/media /mnt/extSdCard
fi
I saw this on a website and it works perfectly, just need to verify your dev/block/vold/NNN:NN mount point and make this change after the SDCard is initialized.

aramova said:
schnowdapowda is correct, LVM would be able to do this just fine if Android supported it, but as far as I can tell the Android system doesn't have the kernel modules or systems in place sadly. Otherwise it'd be no problem making a physical volume from the two SD partitions, then a volume group and logical volumes.
One down side is you would run into system overhead while the slower SD card is keeping LVM from writing to faster on-board "SD card" partition space.
I just run the following at boot time, and it swaps the internal and external cards... Note this is with the Perseus kernel.
Code:
busybox mount -o remount,rw /
busybox mount -t exfat -o umask=0000 /dev/block/vold/179:49 /mnt/sdcard
if busybox mount | busybox grep vold/179:49; then
busybox mount -o bind /data/media /mnt/extSdCard
fi
I saw this on a website and it works perfectly, just need to verify your dev/block/vold/NNN:NN mount point and make this change after the SDCard is initialized.
Click to expand...
Click to collapse
How well does this work for you? And do you do this at every boot or only when you want to swap? Also when running apps after you swap the two and all of your other apps are already installed on internal then you swap the two, can you still just open the app drawer click and run? Or do they no longer run after the switch.
Also after the switch how does that all work when going into recovery and wiping directory's/folders etc and flashing ROM's what will it wipe since the directories are switched?

What is the benefit of swapping?
Sent from my SPH-L900 using xda app-developers app

Tw1sted247 said:
How well does this work for you? And do you do this at every boot or only when you want to swap? Also when running apps after you swap the two and all of your other apps are already installed on internal then you swap the two, can you still just open the app drawer click and run? Or do they no longer run after the switch.
Also after the switch how does that all work when going into recovery and wiping directory's/folders etc and flashing ROM's what will it wipe since the directories are switched?
Click to expand...
Click to collapse
Sorry i had forgotten about this thread. This shouldn't effect app storage. Only SD storage and the mock SD storage partition on your internal memory. I believe it might screw up any apps you have installed on your external unless there is some mechanism that changes where the system thinks they're installed. And this wouldn't effect recovery as you cant run that script till startup.
Devi0124 said:
What is the benefit of swapping?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Being able to save stuff automatically to your external without in app configuration.
Anyway.. this isn't what I'm really looking for. As far as I'd be concerned.. the system overhead wouldn't be an issue as I would gladly take a slowdown in read and writes to my storage for the convenience of having it accesible like that. I guess its just a matter of some genius dev compiling LVM into their kernel.

Devi0124 said:
What is the benefit of swapping?
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
More space
Sent from my SPH-L900 using xda app-developers app

[How-to] Using an ext4 formated SD card.

Update: I've since made a flashable zip that automatically creates a modified sdcard1 binary and extracts an init.d script to handle it all. Will make a thread in a more general location as this could be used on many TouchWiz devices. Link.
Hello everyone,
The mailman brought me a new 64GB microSD card this morning, and I wanted to try formatting it in ext4 instead of exFAT. Both for the heck of it and in case I wanted to give AOSP ROMs a try down the road.
The usual caveats apply.
Required:
init.d support
a mounting script
a mounting updater-script for custom recoveries.
You can get init.d support with the stock kernel on many devices by having the run-parts command launch from a custom install-recovery.sh script. See the following thread for files and a how-to:
[MOD]Term-init & Zip-init: Enable Init.d for Any Phones w/o Need of Custom Kernels!!!
SD card removal:
Should you need to remove the card it can be unmounted and safely removed from the storage settings as usual. Mounting it again requires either a reboot or manually executing the mount command and then activating the card in the storage settings.
Mounting script:
Make sure you have proper line endings, file name (e.g. 95mountsdext4) and permissions set.
Code:
#!/system/bin/sh
# Mount SD Card Ext4 Script
mount -rw -t ext4 /dev/block/mmcblk1p1 /storage/extSdCard
Mounting in CWM/TWRP:
The other piece in this is the attached zip file, which simply runs the appropriate mount command for Clockworkmod Recovery. Unmount as usual. This way you can also store nandroid backups and other update zips on the external as well.
Technical considerations:
The mounting occurs early enough during the boot process that the media scanner and MTP services have no issues with this.
There may be are some permissions related glitches to look out for, but it hasn't been an issue for me so far. (One possible fix would be a recursive chmod/chown added to the mounting script.)
Update: The camera app saves the photos properly to the SD card, but leaves them with improper permissions which prevent subsequent viewing or editing again until you chmod the files. To be continued...
If your init.d support comes from the install-recovery.sh trick, CWM will prompt to delete the script before reboot. Don't.
If the mounting script doesn't run for some reason, or you try to activate the card before having mounted it manually, the phone will give an error and ask if you want to format the card. Don't.
Enjoy,
Darkshado

I have been looking for a way to do this for a long time for numerous reasons (symlinks, >4GB file size, linux-only environment, etc.). I'll be giving this a try very soon.
Thanks for sharing!
EDIT: Just wanted to add that I think it's ridiculous Android doesn't support this natively.

The permissions issues are frustrating. I can take photos and store them on the card, but the umask for JB has been set as 077, in other words, rwx------ permissions, and ownership by the application's user.
I tried different arguments for the mount command to try and force permissions and ownership one way or another with no luck so far. Ironically, an NTFS formatted card might work better in this respect.
A similar mod had been made on the Nexus S and one of the posters resorted to an apk that regularly ran chmod -R 0777 on new files, I tried using it but it just hung there and did nothing on the Note II.
Another possibility would be using FUSE, although I'm not sure how to go about doing this yet.
Also, I pondered the possibility of using UDF instead of ext4, it is a standardized format and just about every major OS out there supports it too...

Any updates? Is it working already or...?

Despite all the good of Android, Google/carriers, whoever, not including ext2/3/4 support natively is just a slap in the face. Good to see someone working to right a wrong that subjugating software has done.

You should NOT be doing this. The Android hardware requirements clearly state that all shared storage directories must be case insensitive and must not have permissions. FAT32 is the only supported filesystem which meets these requirements. Mounting an EXT filesystem directly will break applications.
The newer versions of Android come with an "sdcard" utility which uses a FUSE driver to wrap a native EXT filesystem and exposes a pseudo filesystem which is case insensitive and is without permissions. You should mount the EXT SD card at a different location (/dev/fuse) and use the "sdcard" utility to emulate it at /storage/whatever. You can see the command line syntax of the "sdcard" utility in the source code.
CM10.1 does this automatically. https://github.com/CyanogenMod/android_system_core/tree/cm-10.1/sdcard

KurianOfBorg said:
You should NOT be doing this. The Android hardware requirements clearly state that all shared storage directories must be case insensitive and must not have permissions. FAT32 is the only supported filesystem which meets these requirements. Mounting an EXT filesystem directly will break applications.
The newer versions of Android come with an "sdcard" utility which uses a FUSE driver to wrap a native EXT filesystem and exposes a pseudo filesystem which is case insensitive and is without permissions. You should mount the EXT SD card at a different location (/dev/fuse) and use the "sdcard" utility to emulate it at /storage/whatever. You can see the command line syntax of the "sdcard" utility in the source code.
CM10.1 does this automatically. https://github.com/CyanogenMod/android_system_core/tree/cm-10.1/sdcard
Click to expand...
Click to collapse
Again, Android not natively supporting ext4 is a slap in the face. Usability over technical merit disgusts me.

muqali said:
Again, Android not natively supporting ext4 is a slap in the face. Usability over technical merit disgusts me.
Click to expand...
Click to collapse
It does support EXT4! Officially. All Google ROMs and AOSP can mount EXT4 partitions as /storage/*. The correct way to mount it is to use the command "sdcard" not "mount". I'm pretty sure any AOSP ROM will automatically mount an EXT4 SD card using the "sdcard" command just like Cyanogenmod does.

Thanks for the info. I'll look into this soon-ish, once my exams are over.
Sent from my SGH-T889V using xda app-developers app

KurianOfBorg said:
It does support EXT4! Officially. All Google ROMs and AOSP can mount EXT4 partitions as /storage/*. The correct way to mount it is to use the command "sdcard" not "mount". I'm pretty sure any AOSP ROM will automatically mount an EXT4 SD card using the "sdcard" command just like Cyanogenmod does.
Click to expand...
Click to collapse
It's still a second class citizen to a xFATx filesystem.

muqali said:
It's still a second class citizen to a xFATx filesystem.
Click to expand...
Click to collapse
No it's fully supported by AOSP exactly the same as FAT on AOSP and exFAT/NTFS on Samsung ROMs. It's the manufacturer's fault for REMOVING support from their ROM. When you insert an EXT SD card on AOSP, it gets mounted at /storage/* just like any other SD card.

In my N7100 with CM 10.1, ext4 has stopped working for my 32gb SDCard on 05-01-2013 nightly, even after reformatting, going back to stock, then reinstalling CM 10.1. I also noticed that my ext4 formatted 8GB SdCard still works, however, so I am not sure if it's a storage size issue in my case (32gb vs 8gb). I am trying a hybrid of 8mb fat32 / 28.*gb ext4 to see if that will work.
KurianOfBorg said:
No it's fully supported by AOSP exactly the same as FAT on AOSP and exFAT/NTFS on Samsung ROMs. It's the manufacturer's fault for REMOVING support from their ROM. When you insert an EXT SD card on AOSP, it gets mounted at /storage/* just like any other SD card.
Click to expand...
Click to collapse

clearday said:
In my N7100 with CM 10.1, ext4 has stopped working for my 32gb SDCard on 05-01-2013 nightly, even after reformatting, going back to stock, then reinstalling CM 10.1. I also noticed that my ext4 formatted 8GB SdCard still works, however, so I am not sure if it's a storage size issue in my case (32gb vs 8gb). I am trying a hybrid of 8mb fat32 / 28.*gb ext4 to see if that will work.
Click to expand...
Click to collapse
Is it formatted properly as ext4? Using mke2fs or (tune2fs to convert to ext4). All ROMs only mount the first partition on the SD card regardless of the file system. Sometime after mounting USB Mass Storage an the SD card doesn't remount properly so you need to reboot the device. You'll most probably want to use MTP with ext4 anyway.

KurianOfBorg said:
Is it formatted properly as ext4? Using mke2fs or (tune2fs to convert to ext4). All ROMs only mount the first partition on the SD card regardless of the file system. Sometime after mounting USB Mass Storage an the SD card doesn't remount properly so you need to reboot the device. You'll most probably want to use MTP with ext4 anyway.
Click to expand...
Click to collapse
Finally fixed the problem by running this command in ROM Toolbox Lite:
"find /storage/sdcard1/ -print0 | xargs -0 chown root:media_rw"
http://forum.xda-developers.com/showthread.php?p=38182488#post38182488

clearday said:
Finally fixed the problem by running this command in ROM Toolbox Lite:
"find /storage/sdcard1/ -print0 | xargs -0 chown root:media_rw"
http://forum.xda-developers.com/showthread.php?p=38182488#post38182488
Click to expand...
Click to collapse
Then it's not mounted properly! Your ext4 SD card has directly been mounted at /storage/* instead of through the FUSE driver. You should NOT be able to see permissions when it's mounted at /storage/*. The physical partition should be mounted at /dev/fuse. Reboot the device and check again whether permissions are visible at /storage/*.

KurianOfBorg said:
Then it's not mounted properly! Your ext4 SD card has directly been mounted at /storage/* instead of through the FUSE driver. You should NOT be able to see permissions when it's mounted at /storage/*. The physical partition should be mounted at /dev/fuse. Reboot the device and check again whether permissions are visible at /storage/*.
Click to expand...
Click to collapse
It's still visible at storage
How do I fix it?

clearday said:
It's still visible at storage
How do I fix it?
Click to expand...
Click to collapse
It should show up at /storege/* but that should be the FUSE driver's mount point with permissions stripped away. The real ext4 partition will be at /dev/fuse.

Any further progress?
I want to use symlinks and ext4 on my note 2 also.

On aosp roms just use the sdcard binary with an initd script.
Gesendet von meinem GT-N7105 mit Tapatalk 2

DerTeufel1980 said:
On aosp roms just use the sdcard binary with an initd script.
Click to expand...
Click to collapse
I'm trying to do this on Tweaked. There is an sdcard binary, however, it appears to be modified by Samsung as it's hardcoded to mount to /storage/sdcard0 and overrides the internal sdcard mount when I use it. It doesn't take a destination parameter like the AOSP/CM version does.
If anyone has an AOSP/CM build environment, could I trouble you for a statically linked version of the sdcard binary? I downloaded CM10.2-nightly, but it's dynamically linked and, of course, doesn't work on the stock based ROMs.
EDIT
It might still be nice, but I figured out a way around it. I hex edited the sdcard binary from the Note2 to use /storage/sdcard1. Then in the mount script, bind mounted it over to /storage/extSdCard. I've rebooted a few times and it seems to be working fine. I am copying data to it over MTP right now. I've attached a zip of the files I'm using.
NOTE: THIS IS NOT A FLASHABLE ZIP.
I might make one later, but this kind of needs to be a manual process anyway.
put the sdcard1 file in /system/xbin
chmod 755 /system/xbin/sdcard1
put the script file in /etc/init.d
set permissions/ownership on it
Now, if you have an ext4 formatted SD, and it's not mounted, you should be able to run the script and have it mount it, run the sdcard1 binary on it, and bind mount it over to the normal extSdCard spot. It will happen at boot if you got it all right.
There are probably improvements that can be made, my shell scripting is a bit rusty. Hopefully this will get people interested in it again, now that the permissions issues are resolved.

Help fixing Droid Inc's emmc after NTFS format?

Guess what guys, I thought it would be a smart idea to format my Dincs internal storage to NTFS...I needed to transfer a big file and didn't have anything on it so it seemed like a good idea. Yes I didn't have a flash drive. Anyway, it didn't turn out good. I'm not really worried about being able to use it again (I have a 32gb sd card) but I don't like broken things. I'd like to fix it, I've already done some homework but have got no results. I am currently running this for anyone interested. http://forum.xda-developers.com/showthread.php?t=2143575 Any ideas on how to get it to work again? Even my computer won't read it -___-

AdrianCO said:
Guess what guys, I thought it would be a smart idea to format my Dincs internal storage to NTFS...I needed to transfer a big file and didn't have anything on it so it seemed like a good idea. Yes I didn't have a flash drive. Anyway, it didn't turn out good. I'm not really worried about being able to use it again (I have a 32gb sd card) but I don't like broken things. I'd like to fix it, I've already done some homework but have got no results. I am currently running this for anyone interested. http://forum.xda-developers.com/showthread.php?t=2143575 Any ideas on how to get it to work again? Even my computer won't read it -___-
Click to expand...
Click to collapse
Format the internal SD with recovery?
Sent from my Galaxy Nexus using xda app-developers app

Do you have adb setup and working on your pc?
You need to be in recovery and then open an adb shell. Run the folowing hitting enter after each line.
Code:
parted /dev/block/mmcblk0p3
print
You will see a line starting with "Disk /dev/block/mmcblk0p3: ...MB"
What ever that size says at the end use in the following line.
Code:
mkpartfs fat32 0 ...MB

cmlusco said:
Do you have adb setup and working on your pc?
You need to be in recovery and then open an adb shell. Run the folowing hitting enter after each line.
Code:
parted /dev/block/mmcblk0p3
print
You will see a line starting with "Disk /dev/block/mmcblk0p3: ...MB"
What ever that size says at the end use in the following line.
Code:
mkpartfs fat32 0 ...MB
Click to expand...
Click to collapse
Sorry for the extremely late reply, I've been without internet for the longest time now. Anyways, as much I would've liked to fix it, I've upgraded my device. Thanks a lot for your comment though!:laugh:

[d2tmo][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Now: one common recovery for all: d2lte
The below specific variants are no more updated, use d2lte common variant
SGH-T999 (d2tmo)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Reporting issues:
1- Keep in mind I do not own the device: be precise in your description providing step by step details and screen log output
2- Provide a log: Advanced / Report Error, then attach the philz_recovery.log here
exfat is enabled: report if working or not
Let me know about any issue so that we can debug it + LOGS

Downloading now, will flash in a second or two and report back.

mt3g said:
Downloading now, will flash in a second or two and report back.
Click to expand...
Click to collapse
Will be waiting for first feedbacks, first bugs, or a first perfect (would be rare, even if I am getting a bit used now to Qualcomm devices)

Flashes fine and looks great.
The time is off by 7 hours for me looked in settings for creating a time zone slot, with no success. The screenshot feature is dope but didn't work, gave me tears and not visible screens. Will flash a kernel in a second to test that much out. Will flash a ROM and create a backup later to test more thorough. The screen is what I got from swipe to left for screenshot in recovery.
EDIT: Kernel falshed fine. so all in all no real issues to report as it works as a recovery should, all but testing nandroid and restoring.
T-Mobile SGS III

mt3g said:
Flashes fine and looks great.
The time is off by 7 hours for me looked in settings for creating a time zone slot, with no success. The screenshot feature is dope but didn't work, gave me tears and not visible screens. Will flash a kernel in a second to test that much out. Will flash a ROM and create a backup later to test more thorough. The screen is what I got from swipe to left for screenshot in recovery.
EDIT: Kernel falshed fine. so all in all no real issues to report as it works as a recovery should, all but testing nandroid and restoring.
T-Mobile SGS III
Click to expand...
Click to collapse
Thank you for the positiv eearly report
fb2png for screenshots doesn't support most new boards. Hopefully it will be fixed later
Time is GMT by default. Time zone can be set under GUI settings, it should work. If not, provide a log

Phil3759 said:
Thank you for the positiv eearly report
fb2png for screenshots doesn't support most new boards. Hopefully it will be fixed later
Time is GMT by default. Time zone can be set under GUI settings, it should work. If not, provide a log
Click to expand...
Click to collapse
It sure was and time is correct now, I like the brightness settings also, lots of goodies in there. I'll report back later tonight if no one else does on nandroid and such.

ill try it out im using twrp recovery so itll be fun to try something new lol
omg! its touch enabled
and i like the color at first the layout is a win for me so far and ui is to
great job
clock is working changed to my time zone with daylight savings time fine
omg just found out i can you my home back and menu in it
im having fun playing with it im easy to entertain lol give me a break
ok new favorite recovery lol im hooked lol

I do not expect any issue with nandroid backups as it was largely debugged now on other devices
However:
- Mount USB storage works?
- exfat is ok?
- A last important point: when you boot into recovery, /system is mounted or unmounted? To see this, go into Mounts and Storage menu after you booted in recovery. /system should show (mount) and not (unmount)
I ask this to tune things if needed as this is completely repacked around stock ramdisk and kernel to enable exfat mainly

My stuff is fat32 so I can't help there... system is not mounted it shows mount/ system

Just booting into it and scrolling through some of the options was a treat within itself. Don't have much more to say (that hasn't been said already) but I'm glad we're able to have such a refined recovery. I'll let you know if I bump into any issues, as I tend to not stay in recovery mode for too long (when I actually have something to flash, etc. I'll test more). Thanks!
Sent from my SGH-T999 using Tapatalk 4 Beta

Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
I was able to install it perfectly with Odin with the only difference from your installation instructions being that the phone rebooted into normal mode, so I just entered recovery mode via Rom Toolbox.
I am unable to access an external 64GB SDXC formatted as exFat. I tried to mount /external_sd and /sd-ext and neither one worked. I don't know if this is relevant but the normal mount point for the external SD card on the Galaxy S3 is /mnt/extSdCard.
The aroma file manager doesn't see the external card either.
Everything else seems to be working though I haven't tried to do a backup or a restore.
Thanks for your help...

Love the UI! Very easy to navigate. Everything seems to be running smoothly so far. Installed a few AOSP and TW ROMs successfully. Kernels I've tested are BMS, KT747, and LK. All were successful as well.
EDIT: Backup and restore options seem to work just fine. No issues with Mounts or storage I'm on a fat32 card so I can't test exfat unfortunately. Will let you know if anything comes up within the next day or 2.
Thank you very much for sharing this. It is pretty dope.

Thank you all
Will wait a bit more for reports about exfat
Some 64Gb cards always caused issues on some phones, mainly if they were not formatted as they should (primary partition and default block size)
Sent from my GT-I9100 using Tapatalk 2

I tried flashing the zip file but install keeps aborting?
Sent from my SAMSUNG-SGH-I747 using xda premium

Phil3759 said:
Thank you all
Will wait a bit more for reports about exfat
Some 64Gb cards always caused issues on some phones, mainly if they were not formatted as they should (primary partition and default block size)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
When I had problems with the early exfat drivers from Samsung, I reformatted the card as Fat32 and ran with that for some time. After installing an update from Samsung/T-Mobile where the exFat issues were fixed I used the following procedure to convert the card to exFat:
1. Copied all data from the card to a PC via a card reader.
2. Deleted all partitions from the card using a partition manager on the pc
3. Installed the card into the phone and let the phone partition and reformat the card.
4. Copied all data from the PC back to the card via a card reader.
5. Re-installed the card into the phone.
It has been several months since I converted the card back to exFat and I have had no problems with app on the phone accessing the card. This include Nandroid Manager, Online Nandroid and Titanium Backup as well as all of the normal Android utilities.
The partition information is:
Partition Type: Primary
Psttition Type Id: 0x0C
File System: exFAT
Serial #: 0
First Physical Sector: 2048 (Cyl: 0, Hd:32, Sect: 33)
Last Physical Sector 124735487 (Cyl: 7764, Hd: 108, Sect: 24)
Total Physical Sectors: 124733440 (60905.0MB)
Physical Geometry: 7764 Cyls, 255 Hds, 64 Sects.
That's the best that I could do on short notice. I am trying to find a utility that will give me more information under Windows 7.
Thanks again and again...
Mike
P.S. If I can help with some testing or programming, please let me know. I'm fighting learning java but I am pretty good with C/C++ and assembler.

ChitownWingMan said:
When I had problems with the early exfat drivers from Samsung, I reformatted the card as Fat32 and ran with that for some time. After installing an update from Samsung/T-Mobile where the exFat issues were fixed I used the following procedure to convert the card to exFat:
1. Copied all data from the card to a PC via a card reader.
2. Deleted all partitions from the card using a partition manager on the pc
3. Installed the card into the phone and let the phone partition and reformat the card.
4. Copied all data from the PC back to the card via a card reader.
5. Re-installed the card into the phone.
It has been several months since I converted the card back to exFat and I have had no problems with app on the phone accessing the card. This include Nandroid Manager, Online Nandroid and Titanium Backup as well as all of the normal Android utilities.
The partition information is:
Partition Type: Primary
Psttition Type Id: 0x0C
File System: exFAT
Serial #: 0
First Physical Sector: 2048 (Cyl: 0, Hd:32, Sect: 33)
Last Physical Sector 124735487 (Cyl: 7764, Hd: 108, Sect: 24)
Total Physical Sectors: 124733440 (60905.0MB)
Physical Geometry: 7764 Cyls, 255 Hds, 64 Sects.
That's the best that I could do on short notice. I am trying to find a utility that will give me more information under Windows 7.
Thanks again and again...
Mike
P.S. If I can help with some testing or programming, please let me know. I'm fighting learning java but I am pretty good with C/C++ and assembler.
Click to expand...
Click to collapse
Sadly, without a recovery log or even better a dmsg log, I cannot help a lot
exfat drivers are from /system/lib, so the ones used by your ROM. They are not bundled with the recovery as that causes issues for some
can you try this in adb shell:
Code:
mount -t extfat /external_sd
Give the error message if it fails
If it fails, try this
Code:
mount /system
insmod -f -v /system/lib/modules/exfat_core.ko
insmod -f -v /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
Give output of these command lines if they do fail

Phil3759 said:
Sadly, without a recovery log or even better a dmsg log, I cannot help a lot
exfat drivers are from /system/lib, so the ones used by your ROM. They are not bundled with the recovery as that causes issues for some
can you try this in adb shell:
Code:
mount -t extfat /external_sd
Give the error message if it fails
If it fails, try this
Code:
mount /system
insmod -f -v /system/lib/modules/exfat_core.ko
insmod -f -v /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
Give output of these command lines if they do fail
Click to expand...
Click to collapse
Manual mount:
~ # mount -t extfat /external_sd
mount -t extfat /external_sd
mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument
The mount was successful after the insmod commands. I was also able to cd to /external_sd and do an "ls -l".
Can I modify a script to include the insmod's or do you have to do it?
Thanks again...

ChitownWingMan said:
Manual mount:
~ # mount -t extfat /external_sd
mount -t extfat /external_sd
mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument
The mount was successful after the insmod commands. I was also able to cd to /external_sd and do an "ls -l".
Can I modify a script to include the insmod's or do you have to do it?
Thanks again...
Click to expand...
Click to collapse
Ok, we're on the way to fix it
Can you try this now, in adb shell, after a recovery reboot please
Code:
mount /system
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
That way I can limit the potential causes. It is same as above without insmod options in command

Phil3759 said:
Ok, we're on the way to fix it
Can you try this now, in adb shell, after a recovery reboot please
Code:
mount /system
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd
That way I can limit the potential causes
Click to expand...
Click to collapse
Before I tried what you asked I rebooted into recovery. In other words, I ran the adb shell commands while the phone was in your recovery program. Is that what you mean?

[Q&A] [KERNEL][V510GPE]SleekAI.

Q&A for [KERNEL][V510GPE]SleekAI.
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Hi sleekmason, i am going to sell my palman and so i need to get back to stock. I know izs not necessary because the OTAs can be flashed with TWRP but the new owner is not that nerdy as he needs to be.
Can you tell me the steps to revert anything in the right order? I followed all the steps in the OT and have backups etc....
btw...you did a great job with the kernel for v510

flashed the latest kernel (v4) this morning, switched to the wheatley governor .. no anomalies, too soon to tell. I'll give you an update when I have it - thanks for your work on this.

zenrev said:
flashed the latest kernel (v4) this morning, switched to the wheatley governor .. no anomalies, too soon to tell. I'll give you an update when I have it - thanks for your work on this.
Click to expand...
Click to collapse
Was Wheately the default? It should have been. Let me know! I'm still going to add a few things.

Is there any special way to format to try to test the new exfat support? That's what has kept me from using this kernel for the longest time.
I just flashed the latest kernel, erased the SD card within the regular Storage Settings, but the card still fails to mount successfully. I will try to pop the card out and reformat via Windows in the morning to see if that has any impact.

siopaor said:
Is there any special way to format to try to test the new exfat support? That's what has kept me from using this kernel for the longest time.
I just flashed the latest kernel, erased the SD card within the regular Storage Settings, but the card still fails to mount successfully. I will try to pop the card out and reformat via Windows in the morning to see if that has any impact.
Click to expand...
Click to collapse
Why would it keep you from using my kernel? until now, there were no changes to the extension types the sdcards can use, meaning there was NO difference regarding exfat support between the stock kernel and the sleekai kernel.
The device itself will not format the card to exfat. Please let me know if your exfat formatted card works. Not having exfat myself, I am relying on you people to tell me!

sleekmason said:
Why would it keep you from using my kernel? until now, there were no changes to the extension types the sdcards can use, meaning there was NO difference regarding exfat support between the stock kernel and the sleekai kernel.
The device itself will not format the card to exfat. Please let me know if your exfat formatted card works. Not having exfat myself, I am relying on you people to tell me!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50572410&postcount=23
There was something in the old versions that conflicted with exfat formatted cards. I honestly couldn't say what the difference was, but the stock kernel worked fine. It's been a long time since I tried this kernel, but when I did everything else worked great. I just travel a lot for work so I'm always putting movies on the SD card >4GB, so fat32 wasn't an option for me. I'm on lollipop now and it's generally a little more sluggish than KK, so that's what peaked my interest in giving this kernel another shot.
I tried a quick format in Windows, but that did not make a different. I'm still unable to mount the card on the tablet. I'm trying a full format now, but that'll take a while since it's a 64GB card.
Appreciate the help.

siopaor said:
http://forum.xda-developers.com/showpost.php?p=50572410&postcount=23
There was something in the old versions that conflicted with exfat formatted cards. I honestly couldn't say what the difference was, but the stock kernel worked fine. It's been a long time since I tried this kernel, but when I did everything else worked great. I just travel a lot for work so I'm always putting movies on the SD card >4GB, so fat32 wasn't an option for me. I'm on lollipop now and it's generally a little more sluggish than KK, so that's what peaked my interest in giving this kernel another shot.
I tried a quick format in Windows, but that did not make a different. I'm still unable to mount the card on the tablet. I'm trying a full format now, but that'll take a while since it's a 64GB card.
Appreciate the help.
Click to expand...
Click to collapse
I will try to get to a Windows box and format in exfat to test and compile another kernel. Check back in a few days to see if it is resolved.

sleekmason said:
I will try to get to a Windows box and format in exfat to test and compile another kernel. Check back in a few days to see if it is resolved.
Click to expand...
Click to collapse
I certainly appreciate the effort. I did try a full format from Windows, but that didn't have any impact. It's a 64GB G.Skill card, FYI. If there is anything else I can try that might help troubleshoot the issue, let me know.

siopaor said:
I certainly appreciate the effort. I did try a full format from Windows, but that didn't have any impact. It's a 64GB G.Skill card, FYI. If there is anything else I can try that might help troubleshoot the issue, let me know.
Click to expand...
Click to collapse
Okay, updated both versions again. There was a module issue that I cant believe has nobody caught before now. .. including me!
Please let me know if this is working now, and whether you are using kitkat or lollipop.

sleekmason said:
Okay, updated both versions again. There was a module issue that I cant believe has nobody caught before now. .. including me!
Please let me know if this is working now, and whether you are using kitkat or lollipop.
Click to expand...
Click to collapse
No luck, I'm afraid. I'm using lollipop.
The curious thing that I noticed is that I can see the SD card in TWRP. I can also mount it and access it over USB via MTP. When I boot the tablet it then disappears and can't be seen in Android or over USB/MTP. I don't know if that means anything, just an additional observation.

siopaor said:
No luck, I'm afraid. I'm using lollipop.
The curious thing that I noticed is that I can see the SD card in TWRP. I can also mount it and access it over USB via MTP. When I boot the tablet it then disappears and can't be seen in Android or over USB/MTP. I don't know if that means anything, just an additional observation.
Click to expand...
Click to collapse
It does. I don't know anything about how twrp works though. Sounds like a mount issue. If one of the other developers knows what's happening, I would appreciate the insight.

siopaor said:
No luck, I'm afraid. I'm using lollipop.
The curious thing that I noticed is that I can see the SD card in TWRP. I can also mount it and access it over USB via MTP. When I boot the tablet it then disappears and can't be seen in Android or over USB/MTP. I don't know if that means anything, just an additional observation.
Click to expand...
Click to collapse
Okay, there may be something notice for exfat after all. There is a tuxera exfat module that should be available as texfat.ko in /system/lib/module, but it is not being made(compiled) and I dont know why....
But! Here may be a solution after all. I was missing a command in the init.palman.rc for the exfat I Compiled into the kernel from Mako sources.
I still need to get a card formatted exfat when I get a chance. You could try from a terminal emulator using my kernel that should have exfat support with these commands
as root. So first do:
Code:
su
To get root access, then:
Code:
insmod /system/lib/modules/exfat_fs.ko
Code:
insmod /system/lib/modules/exfat_core.ko
to activate the modules. It is worth a try anyway.
You can get a terminal emulator app from the playstore
This would be my next step. If it works, I will put them directly into the rc file

sleekmason said:
Okay, there may be something notice for exfat after all. There is a tuxera exfat module that should be available as texfat.ko in /system/lib/module, but it is not being made(compiled) and I dont know why....
But! Here may be a solution after all. I was missing a command in the init.palman.rc for the exfat I Compiled into the kernel from Mako sources.
I still need to get a card formatted exfat when I get a chance. You could try from a terminal emulator using my kernel that should have exfat support with these commands
as root. So first do:
Code:
su
To get root access, then:
Code:
insmod /system/lib/modules/exfat_fs.ko
Code:
insmod /system/lib/modules/exfat_core.ko
to activate the modules. It is worth a try anyway.
You can get a terminal emulator app from the playstore
This would be my next step. If it works, I will put them directly into the rc file
Click to expand...
Click to collapse
I gave that a shot, but got an error on the first one. I copy/pasted with Pushbullet what you suggested. Here is the output from the terminal:
Code:
[email protected]:/ $ su
[email protected]:/ # insmod /system/lib/modules/exfat_fs.ko
insmod: init_module '/system/lib/modules/exfat_fs.ko' failed (No such file or directory)
255|[email protected]:/ # insmod /system/lib/modules/exfat_core.ko
[email protected]:/ #
I checked that directory, and it looks like the file exists, so I'm not sure what happened. The second command seemed to work fine (no positive or negative response).
EDIT: I just repeated the commands and the first one seemed to work fine now. Maybe the second one just needs to be run first? Now it gives me a message saying the File Already Exists when I re-execute. I haven't noticed anything different. I tried restarting the tablet to see if I noticed a difference, but nothing yet.

siopaor said:
I gave that a shot, but got an error on the first one. I copy/pasted with Pushbullet what you suggested. Here is the output from the terminal:
Code:
[email protected]:/ $ su
[email protected]:/ # insmod /system/lib/modules/exfat_fs.ko
insmod: init_module '/system/lib/modules/exfat_fs.ko' failed (No such file or directory)
255|[email protected]:/ # insmod /system/lib/modules/exfat_core.ko
[email protected]:/ #
I checked that directory, and it looks like the file exists, so I'm not sure what happened. The second command seemed to work fine (no positive or negative response).
EDIT: I just repeated the commands and the first one seemed to work fine now. Maybe the second one just needs to be run first? Now it gives me a message saying the File Already Exists when I re-execute. I haven't noticed anything different. I tried restarting the tablet to see if I noticed a difference, but nothing yet.
Click to expand...
Click to collapse
restarting won't help as you have to run the commands after the tablet has already started. But yes please try again running the second command first and then see if you can see any files, or mount, etc.

sleekmason said:
restarting won't help as you have to run the commands after the tablet has already started. But yes please try again running the second command first and then see if you can see any files, or mount, etc.
Click to expand...
Click to collapse
I restarted to try a clean attempt, ran the exfat_core.ko command followed by exfat_fs.ko and they appeared to go through smooth. Unfortunately, I can't get the SD card mounted still. I tried reformatting the card again and no luck. I created a 30GB partition, formatted in FAT32 and the card mounted without issue. I reformatted the partition back to exfat, but am unable to get it to mount.
Note, I'm still using the Lollipop5.0 version of the kernel, not the latest 5.2, just to clarify.
I appreciate the help and sorry I can't offer more troubleshooting help.

siopaor said:
I restarted to try a clean attempt, ran the exfat_core.ko command followed by exfat_fs.ko and they appeared to go through smooth. Unfortunately, I can't get the SD card mounted still. I tried reformatting the card again and no luck. I created a 30GB partition, formatted in FAT32 and the card mounted without issue. I reformatted the partition back to exfat, but am unable to get it to mount.
Note, I'm still using the Lollipop5.0 version of the kernel, not the latest 5.2, just to clarify.
I appreciate the help and sorry I can't offer more troubleshooting help.
Click to expand...
Click to collapse
that's okay, at least you tried. The original stock kernel has exFAT support through what I believe to be a proprietary driver that was installed during the making of the device and device tree. And in the kernel source that I download to compile a new kernel, it is not there. If I could just find that driver we would be in business. I dont know why it is missing, and maybe I just am not seeing things clearly and it is there somewhere. Ill keep looking.

@siopaor
I think we have a winner! Please give the below kernel LollipopSleekai5.7 a shot
I am very hopeful. I wound up scrapping the exfat code I found in another developers github and went straight to the source. You shouldn't need to insmod or do anything else as I wrote it into the init.palman.rc. Please let me know! Best Regards,

sleekmason said:
@siopaor
I think we have a winner! Please give the below kernel LollipopSleekai5.7 a shot
I am very hopeful. I wound up scrapping the exfat code I found in another developers github and went straight to the source. You shouldn't need to insmod or do anything else as I wrote it into the init.palman.rc. Please let me know! Best Regards,
Click to expand...
Click to collapse
I think you're right. So far, so good. I reformatted back and forth between FAT32 and exfat, copied an 8GB video file to the SD and was able to access and play it without issue. All I did was flash this new version of the kernel and everything worked just fine.
Thanks for the time you spent tracking down the solution for this, very much appreciate it.

Absolutely awesome!!!! I will be making an updated version with fsync enabled by default and other optimizations. So the next kernel out, maybe tonight, you may want to switch out with. Or, you can just keep using this one. It is most definitely good to go. KitKat version coming as well