Database Users

SDCARD Mounting Paradigm - Cyanogenmod7

There are two sdcard mounting paradigms. Currently Cyanogenmod for the tablet is set to use the one that matches phones.
1) Internal SDCARD mounted to /SDCARD, External to /SDCARD2(or equivalent)
Pros
-Internal sdcard is easily accessible
Cons
-External sdcard isn't mounted to computer over usb
2) Internal SDCARD mounted to /EMMC, External to /SDCARD
Pros
-External SDCARD is default and mounted to computer over usb
-Works well for phones with small internal storage sizes
Cons
-Your internal storage is hard to access, not mounted over usb
I took this GIT commit and rolled the changes back for CM7. I then recompiled CM7 to use the option 1 mounting paradigm.
Let me know which you prefer. I personally like option 1 because it doesn't rely on having an external sdcard. Additionally the internal sdcard is not easily removable like the external, so being able to access it over usb is important. If there are reasons for options 2, let me know.
Download:
CM7RC0 with Option 1 Mounting Paradigm(Mounting over USB works): http://www.multiupload.com/NJFGUW04A2
Gapps: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip

Very cool, I was planning to do that myself this weekend. I played with CM7 yesterday for a few minutes but with no SDCard in the "external" slot there were some limits to have useful the OS was....
I'll probably still pull the source down this weekend, but I can flash your ROM tonight and start having a more detailed look at CM7.

Hey Rothnic, nice call, I agree that the CM7 default mounting scheme is both somewhat confusing and somewhat less useful with the G Tablet.
Quick question - you packaged up those performance packs with updated drivers for TNT etc. I know this may be a dumb question, but are these the same drivers currently being used in CM7? Or are they Froyo specific and incompatible with a Gingerbread ROM build because of library dependencies or structural changes?
I'm just trying to figure out if there's some way to speed up 2d graphics stuff in CM7 without waiting for more drivers from NVidia.

rcgabriel said:
Hey Rothnic, nice call, I agree that the CM7 default mounting scheme is both somewhat confusing and somewhat less useful with the G Tablet.
Quick question - you packaged up those performance packs with updated drivers for TNT etc. I know this may be a dumb question, but are these the same drivers currently being used in CM7? Or are they Froyo specific and incompatible with a Gingerbread ROM build because of library dependencies or structural changes?
I'm just trying to figure out if there's some way to speed up 2d graphics stuff in CM7 without waiting for more drivers from NVidia.
Click to expand...
Click to collapse
CM7 uses the Nvidia libraries from TnT 3588. I haven't gotten to merging in the newer "performance pack" ones that TnT doesn't include.
The libraries are Froyo specific, and were for many devices. I believe the CM team has built wrappers so that it can use the froyo specific libraries. I'm not sure on the acceleration issue.

Ok I got 2 questions:
Do we have any clue how does Incredible (for example) works? It has 8gb internal plus External, they both mount on usb.
Doesnt the fact that we can mount the internal storage on the computer, etc etc, can be a reason for the corruption of partitions? (maybe unplugged before unmounting by mistake or stuff like that..). That may have happen to almost everyone, everything starts crashing, FC, etc, all because of the repartitioning. Maybe paradigm 2 its better and correct.
Another quick thing, is it possible to mount internal on /scard and external on /sdcard/sdcard2? That would make both accesible on usb mount no?
Thanks

great work rothnic
I tried to play with cm7 last night but was getting frustrated by this issue. Thanks for doing this!!

+1 for /SDCARD here...
thanks, rothnic

Thanks for the efforts. Oh, option 1until I can get my hands on a 32GB micro SD, but probably still favor /sdcard and /sdcard2 anyhow.
Also, can't wait for hardware acceleration with this Rom, best one so far.

I like option 1 over option 2 for the gTab. What would really be cool is an option 3.
Internal + External = virtual SDCard.

+1 for Option 1.

If it is going to be a 'true' Cyanogen port, it should probably use the default Cyanogen behavior, which is Option 2.

This is meant as a discussion for the merits of each. For my use case option 1 makes sense.
Id like to hear why option 2 makes sense to others. How do you access your 14gb of internal storage?

slaughts said:
If it is going to be a 'true' Cyanogen port, it should probably use the default Cyanogen behavior, which is Option 2.
Click to expand...
Click to collapse
This is handled in the device specific config files so in no way makes it different. Each device has its own specific mounting scheme.

I prefer option 1, because it does not depend on having the external inserted.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk

danielsjam said:
I prefer option 1, because it does not depend on having the external inserted.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Click to expand...
Click to collapse
This has to be the most compelling reason on why it should be mounted as sdcard and sdcard2.

thebadfrog said:
This has to be the most compelling reason on why it should be mounted as sdcard and sdcard2.
Click to expand...
Click to collapse
I agree. I prefer internal being SDCARD.

A vote for Option 1. As a temporary solution, I go into the Terminal Emulator and type
Code:
su
mount /emmc/ /sdcard/
and it works
gksmith said:
I like option 1 over option 2 for the gTab. What would really be cool is an option 3.
Internal + External = virtual SDCard.
Click to expand...
Click to collapse
You mean.............just like Windows Phone 7?

It depends on the read/write speed of the sdcard. But since the internal sdcard is shared with other system partitions it makes sense for the external sdcard to be mounted at /sdcard, especially if you have media on it. Processes that read/write to /sdcard (like Gallery) can't mean anything good for performance. What we should have is both the sd and emmc to have /data, /system, and /sdcard mdraid partitions created and mounted/initialized for a nice perf increase. I wonder if its possible with android. It certainly is supported in the kernel with the right config. I should check to see if there are arm binaries for mdadm. Then i could create a test partition to measure performance.
Oh and CIFS is what i use to xfer files. There are plenty of ways to access partitions without mounting them as a drive. I think that usually leads to trouble. There is even file expert which lets you create smb shares... there prob solved, map network drive.

Blades said:
It depends on the read/write speed of the sdcard. But since the internal sdcard is shared with other system partitions it makes sense for the external sdcard to be mounted at /sdcard, especially if you have media on it. Processes that read/write to /sdcard (like Gallery) can't mean anything good for performance. What we should have is both the sd and emmc to have /data, /system, and /sdcard mdraid partitions created and mounted/initialized for a nice perf increase. I wonder if its possible with android. It certainly is supported in the kernel with the right config. I should check to see if there are arm binaries for mdadm. Then i could create a test partition to measure performance.
Click to expand...
Click to collapse
How would you handle people who do not have an external sdcard?

One more for option 1.

default USB Mass storage issue

Hi
for the last few hours I am trying to resolve the issue that I only today found out and after lots of testing, reflashing different roms I realized that this is a general issue and not related only to me or the rom I am using. So far tried only CM7 roms and NexusHD 3.0.
First it only happens if you have second partition on your sdcard. If you have only one fat32 partition everything works OK.
To see the issue try next:
-Enable USB Mass storage via default mount option in notification area. (issue is not present with 3rd party mount apps)
-On your computer open some folder on your SD card and remember its content
-Turn off USB Mass storage
-copy any file to that folder via any file manager app ib your phone
-Turn on USB Mass Storage and again open that folder to check for the new file (second mount lasts much longer then the first)
-File is not visible via USB mount until next phone reboot.
I have tried so far:
-HyperDroid 3 and Hyperdroid GBX v12
-Typhoon 3.6.4
-NexusHD 3.0 and 3.1a
-UltimateDroid 3.3
(all cLK)
Tried to use vold files from several other roms (MIUI and sense rom) but the issue is always there.
Also tried disabling USB debugging, changing USB ports, even PC's.
After some testing I realized that it only occurs if there is extra partition on sd. I tried ReiserFS and ext4 format, no difference. Only when I deleted all the partitions, created one and reformat it to fat32 mount was working fine.
I am currently using AdamG's a2sd modified by Seader for Hyperdroid, but while trying this on NexusHD I used Darktremor 2.7.5.2 and the issue is there.
Workaround for this is to use alternative apps for mounting. I am using Multi Mount SD-Card Lite.....
I have several people so far confirming this, on HyperDroid and Typhoon. All have partitions for a2sd.
I am not sure when this started happening. I will try tommorow some older roms but until then any information about this is helpfull. Please post if you have the issue and what rom you are on.
This is a log while mounting the USB for the second time. I see lots of vold, mount lines.
http://pastebin.com/XKUqpU56
update:
The cause of this issue is definitely a2sd. After I installed fresh rom (hyperdroid) with a2sd script removed from init.d folder USB mount doesn't have this issue.
So something is happening during mount or unmount process with active a2sd which breaks the ability of USB mount to update its file index which is sent to the computer.
This is happening with both Darktremor (tried 2.7.5.2 and 2.7.5.3. beta4) and AdamG's a2sd scripts.
update2:
this is another logcat
while mounting, checking Camera folder on a computer, unmounting, takes a picture, mounting again(this mount takes about 3 times longer then the first) and then checking the Camera folder again.
http://pastebin.com/HtqXzVx4
update3:
I found a way to stop this issue from happening. I have modified one line in vold.fstab file that is located in /system/etc
from
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
to
dev_mount sdcard /mnt/sdcard 1 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
As soon as I change 1 to auto again and reboot issue is back.
This way only the first partition (fat32) is mounted and the issue is gone. I dont know if this change can cause any other issues, but so far only thing I noticed that is different is that when you turn USB Mass storage on while connecting the phone to a linux computer it only mounts first partition and no sdext one. For me this is not important, but as I said I am not sure if this change could have an impact on stability to any part of the system or phone functionality.
So to summ up:
- there is an issue of phone doesnt updating file index after first mount and you can't see any new files on your PC that are created in the meanwhile until phone reboot (for example new pictures taken with Camera)
-this only happens if you have extra partition on sdcard (for a2sd) and installed a2sd script (so far tried only Darktremors and AdamG's, but I guess that they all basically are doing the same thing). If you remove one of this elements the issue is gone
-after changing line in /system/etc/vold.fstab
"dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1 "..........from auto to 1
so the system will mount first and not automaticaly the first available partition, the issue is gone but someone with more knowledge then me could say what kind of issues this change might produce.
(Some time ago while applying this change in hyperdroid release at that time lots of people had issues with getting an corrupt SD card error. Not sure why it happened because it worked fine on my phone)

I have that issue also and i'm using NDT MIUI...now have to use the eMAgldr 1.13 USB Mount Storage to move or copy the file.

I have just installed Ultimate Droid 3.3 to check this issue and it is also there. UD is a 2.3.3 rom with tytung r9 kernel. So the issue is not so new
I need to test even older roms to find out if this ever worked right.
Is there anyone with some old rom installed on it? Nand or SD.

clyder said:
tytung r9 kernel.
Click to expand...
Click to collapse
Yup just try updating your kernel to be able to support ext2-4 partitions
its a big mistake that almost everybody does...

Dakargr said:
Yup just try updating your kernel to be able to support ext2-4 partitions
its a big mistake that almost everybody does...
Click to expand...
Click to collapse
You havent read my post. There is no problem with functionality of sdext partition. But the presense of sdext partitions is one of the conditions for this issue.
I am using Hyperdroid with kernel that is based on tytung r12. After I realized the issue I thought that it is related to that rom and after that with my sd card or something 3rd from my side. But that is not the case.
I have tried about 5 different roms, vold files from 5 more and the issue is always there. Issue is present only where there is a second partion on SD card.
Oldest rom I tried is UD 3.3. I havent found much older cLK roms to test, and now dont have time to convert older roms to test. I will do so later. I want to see if this thing ever worked right and in what point it stopped.
Also you havent mentioned if you tested the issue or not.

I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.

tytung said:
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
Click to expand...
Click to collapse
Thanx for replying. I havent tried with ext3. Only reiserFs and ext4 and the behavior was the same. Only when I removed the ext partition it was gone.
The issue is like phone is sending the same directory listing to a computer in both first and all other mounts until reboot.
One also good way to test is by taking photos from a camera. Look at the DCIM/Camera folder with USB mass storage. Turn storage off. Take another picture. Use Mass storage again and the new pic wont be visible through USB mass storage on your computer.
So far I tried only on windows and not linux. Maybe the behavior is different. I will make more tests later.
At one point I thought that my windows system made that issue, so I tried to change USB ports, also tried hooking phone to another computer and the new files wasn't present.
Also it came to me that a2sd can cause this, but on your rom I tried Darktremor a2sd, while on others it was AdamG's one. Issue was exactly the same.
I havent tried any sense rom, because I would need to reflash different partition layout and was too lazy to do that yesterday.
Point of this thread was to check other people experiences with this to try to realize if this is all general HD2 issue, or perhaps only on AOSP roms. So far not much reports
Can any of your older kernel (<r9) work with newer roms(2.3.4+). I dont care about wifi, phone or anything. It is enough if I can just boot the phone to test this.

update:
I just tried USB mount in Ubuntu and the behavior is the same. Also since I can see ext partition when do a USB mount in linux I realized that the same issues goes with files on ext. New files are not visible to the computer until phone reboot.

clyder said:
Thanx for replying. I havent tried with ext3. Only reiserFs and ext4 and the behavior was the same. Only when I removed the ext partition it was gone.
The issue is like phone is sending the same directory listing to a computer in both first and all other mounts until reboot.
One also good way to test is by taking photos from a camera. Look at the DCIM/Camera folder with USB mass storage. Turn storage off. Take another picture. Use Mass storage again and the new pic wont be visible through USB mass storage on your computer.
So far I tried only on windows and not linux. Maybe the behavior is different. I will make more tests later.
At one point I thought that my windows system made that issue, so I tried to change USB ports, also tried hooking phone to another computer and the new files wasn't present.
Also it came to me that a2sd can cause this, but on your rom I tried Darktremor a2sd, while on others it was AdamG's one. Issue was exactly the same.
I havent tried any sense rom, because I would need to reflash different partition layout and was too lazy to do that yesterday.
Point of this thread was to check other people experiences with this to try to realize if this is all general HD2 issue, or perhaps only on AOSP roms. So far not much reports
Can any of your older kernel (<r9) work with newer roms(2.3.4+). I dont care about wifi, phone or anything. It is enough if I can just boot the phone to test this.
Click to expand...
Click to collapse
This problem appears only after dismounting SD storage you don't remove the cable from the phone.
It is normal before mounting it again to disconnect the USB cable!

Denkov said:
This problem appears only after dismounting SD storage you don't remove the cable from the phone.
It is normal before mounting it again to disconnect the USB cable!
Click to expand...
Click to collapse
This is not the case here. I tried disconnecting my phone, also tried connecting it to another PC and again I can't see any new files until phone reboot.
Have you actualy tested this or just guessing? Do you have ext partition on your SD card? What rom are you using?

clyder said:
This is not the case here. I tried disconnecting my phone, also tried connecting it to another PC and again I can't see any new files until phone reboot.
Have you actualy tested this or just guessing? Do you have ext partition on your SD card? What rom are you using?
Click to expand...
Click to collapse
I have second partition ext3.
I mount SD card, check screen shot folder, unmounted the card, remove the cable, take a screenshot, mount it again and the new image was there.
When I try to do same thing second time it did't work! Maybe you are right - there is issue with th SD card mount and I think the card is not dismounted properly!

tytung said:
I think I don't have any USB Mass storage issue.
My SD card has FAT32 and Ext3 partitions but I don't use Apps2SD. (i.e. Ext3 partition is empty.)
I will try your steps when I go home. (I didn't bring my mini USB cable in hand.)
I rarely copy files using file manager apps.
If you can use USB Mass Storage, it seems there's no reason to use file manager apps.
Click to expand...
Click to collapse
I have tried it.
Mount -> check the content of a folder in the SD card.
Unmount -> Copy a file to that folder using ES File Explorer. (Second testing is Root Explorer. Has the same result.)
Mount -> new file is there.
Win7 x64
NexusHD2-Gingerbread V3.1a NAND

tytung said:
I have tried it.
Mount -> check the content of a folder in the SD card.
Unmount -> Copy a file to that folder using ES File Explorer. (Second testing is Root Explorer. Has the same result.)
Mount -> new file is there.
Win7 x64
NexusHD2-Gingerbread V3.1a NAND
Click to expand...
Click to collapse
You said before that you dont have a2sd installed. Did you tested this without a2sd also? Maybe that is the key. All my tests so far included the presence of some kind of a2sd script.
Also I am on cLK, and two other guys that confirmed it are also on cLK. I dont know about denkov.
I will do more tests later but the issue is definitely related to ext. Because of some incompatibility of a2sd scripts with some part of android system or for some other reason.

I have just tried the combination of NexusHD 3.1a/cLK/AdamG's a2sd script/ext4
issue remains here

clyder said:
You said before that you dont have a2sd installed. Did you tested this without a2sd also? Maybe that is the key. All my tests so far included the presence of some kind of a2sd script.
Also I am on cLK, and two other guys that confirmed it are also on cLK. I dont know about denkov.
I will do more tests later but the issue is definitely related to ext. Because of some incompatibility of a2sd scripts with some part of android system or for some other reason.
Click to expand...
Click to collapse
I am on MAGLDR.
And I don't use any a2sd as I said before.
So my testing is without a2sd.
I think a2sd scripts may be the suspect.

tytung said:
I am on MAGLDR.
And I don't use any a2sd as I said before.
So my testing is without a2sd.
I think a2sd scripts may be the suspect.
Click to expand...
Click to collapse
They are definitely the cause. I have tried both Darktremor's and AdamG's script.
All of the people who confirmed this to me was using a2sd.
edit:
Just did a fresh install of hyperdroid with a2sd script removed from init.d and usb mount issue is gone.
So something is happening while mounting or remounting USB with active a2sd script which breaks the file list updating when mounting it the second time.

I have found a way to stop the issue from happening. Updated first post....if anyone is actually reading this thread...
clyder said:
update3:
I found a way to stop this issue from happening. I have modified one line in vold.fstab file that is located in /system/etc
from
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
to
dev_mount sdcard /mnt/sdcard 1 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
As soon as I change 1 to auto again and reboot issue is back.
This way only the first partition (fat32) is mounted and the issue is gone. I dont know if this change can cause any other issues, but so far only thing I noticed that is different is that when you turn USB Mass storage on while connecting the phone to a linux computer it only mounts first partition and no sdext one. For me this is not important, but as I said I am not sure if this change could have an impact on stability to any part of the system or phone functionality.
So to summ up:
- there is an issue of phone doesnt updating file index after first mount and you can't see any new files on your PC that are created in the meanwhile until phone reboot (for example new pictures taken with Camera)
-this only happens if you have extra partition on sdcard (for a2sd) and installed a2sd script (so far tried only Darktremors and AdamG's, but I guess that they all basically are doing the same thing). If you remove one of this elements the issue is gone
-after changing line in /system/etc/vold.fstab
"dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1 "..........from auto to 1
so the system will mount first and not automaticaly the first available partition, the issue is gone but someone with more knowledge then me could say what kind of issues this change might produce.
Click to expand...
Click to collapse

Good job! I will try!

[Q] Noob question about Multi-Rom on Nexus 7

One little question about the Tool "Multirom":
My internal storage is nearly full because of many Gameloft Games like Nova with big .obb files. After installing a custom Rom on a external storage like a 64gb usb stick, do the Apps/Games of the 2nd Rom will be stored on the external device or on the Nexus 7 internal storage?
Unfortunately tools like "Directory Bind" don't work for me because of Android 4.21...

I think they will store in external storage.
Sent from my Nexus 7 using Tapatalk 2

Sadegh is right. They stay on the external.
Sent from my Nexus 7 using xda premium

rebel1699 said:
Sadegh is right. They stay on the external.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks^^.
Little problem after installation: Multirom doesn't see the rom (paranoid android) on my USB drive.Always the message "No Roms in this location".USB is formatted in NTFS and the paranoid.zip is in the root directory

~VipeR~ said:
Thanks^^.
Little problem after installation: Multirom doesn't see the rom (paranoid android) on my USB drive.Always the message "No Roms in this location".USB is formatted in NTFS and the paranoid.zip is in the root directory
Click to expand...
Click to collapse
Try FAT32.

Mac of York said:
Try FAT32.
Click to expand...
Click to collapse
Well Fat32 is much better,now i can boot many roms but I cant install the paranoid-android rom.Always the same error:
create system.img
create data..
create cache
...
...
unable to open paranoid.zip
Whats wrong?
Maybe a kernel problem because I selected "use the same kernel for both roms"?

Ok I found the problem.In my opinion MultiROM is not fully compatible with NTFS...None of my roms work on NTFS.Always stuck on create data.img...
FAT32 works but the 4gb cap is a little bit annoying.Any idea?

The thread says NTFS is compatible... so it should be. You could also try making it extX.

Well ext3 is compatible too but I cant write anything on my USB Stick with this partition format...I use "Ext2fsd" but I cant mount the partition as read & write...only as read only.
I think NTFS is the best for me but I cant get it working ...Can I move the rom which I created under Ext3 to the NTFS partition?

Maybe exFat?

Have you checked the paranoid zip isn't corrupted? (md5 check or redownload)
I've not tried usb storage but paranoid is certainly working for me in multirom on internal storage
Sent from my Nexus 7 using Tapatalk HD

[Q] sdcard read only from PC

This was a bit unexpected. Lollipop is supposed to make using SDCARD (in this case there is NO sdcard) more sensible.
However now I can't copy any files to Nexus in MTP mode. I can do that in P2P mode but only to the picture folders. Any suggestions on that? Selinux setting?
And, yes, I did try making a new folder but no joy. I also noticed I can't see app-specific folders such as titaniumbackup.

Barleyman said:
This was a bit unexpected. Lollipop is supposed to make using SDCARD (in this case there is NO sdcard) more sensible.
However now I can't copy any files to Nexus in MTP mode. I can do that in P2P mode but only to the picture folders. Any suggestions on that? Selinux setting?
And, yes, I did try making a new folder but no joy. I also noticed I can't see app-specific folders such as titaniumbackup.
Click to expand...
Click to collapse
I just upgraded my N10 to Lollipop yesterday. I'm rooted, have SELinux Mode Changer (set to permissive mode) and have USB OTG Helper [root]https://play.google.com/store/apps/details?id=net.shajul.usbotg&hl=en installed. That gives me full unfettered RW access to my OTG SDCard reader. USB OTG Helper expands the number of SDCard file formats that Android supports. I have mine formatted to ext4 to remove the 2GB file limit but thats just my requirement. I used ES File Explorer to access the SDCard and move/copy files, although I'm sure many other file managers would have worked.
I hope that info helps.

It's not an actual SDCARD but the internal emulated sdcard which is being difficult.

Barleyman said:
It's not an actual SDCARD but the internal emulated sdcard which is being difficult.
Click to expand...
Click to collapse
I am in the same boat. I want to restore some apps I backed up in 4.4.4 and lollipop won't read the backup folders in the root directory. I can see and access them via pc, but not through Android. I tried using Titanium & MyBack Up Pro w/ SU access. No dice. Like you, I also tried moving the folders to my Desktop and back. Renaming, creating new folders, etc..., doesn't help.
I can't work around the issue. My current thinking is that we are dealing with a security feature. It seems like all my 4.4.4 folders with user info in them are walled off.
Grrrrr

Native OTG USB Storage on Nexus Player?

Has anyone been able to get Native OTG USB Storage working on the Nexus Player? By this I mean actual mods to the system not by using third party apps. I know CM12.1 has the mount/mount USB Storage and move app to USB Storage options but neither of these actually work yet. Are there any other devices that has this functional that can be cherry picked from for a quick patch to CM12.1 to enable this function? As most of you are aware the Nexus Player is pretty limited with storage so allowing us to use USB Flash drives over OTG to store apps and their data would be very helpful.

Try the latest nightly

lafester said:
Try the latest nightly
Click to expand...
Click to collapse
Yeah it mounts the drives now but it's still broken and doesn't let you transfer apps to it but dhacker29 is looking into it to fix it.

I've tried to get this working, I can get external storage mounted manually but so far had no luck getting it mounted on boot. My first issue was that after rooting, there was no space left on the /system partition, so busybox failed to install properly. After deleting the korean and japanese IMEs I was able to get busybox installed.
I have an otg hub, with a microSD slot, the card gets recognized by the system as /dev/block/sda and I can mount the partition using busybox mount, but trying to mount it from /etc/install-recovery.sh or /etc/install-recovery-2.sh doesn't work, so I'm not sure if by then the mount point is available.
I know this can be fixed using some other tool (like rom toolbox pro) but I'd love to get this working without them, so if anyone has been able to get it working, please help!

FaberfoX said:
I've tried to get this working, I can get external storage mounted manually but so far had no luck getting it mounted on boot. My first issue was that after rooting, there was no space left on the /system partition, so busybox failed to install properly. After deleting the korean and japanese IMEs I was able to get busybox installed.
I have an otg hub, with a microSD slot, the card gets recognized by the system as /dev/block/sda and I can mount the partition using busybox mount, but trying to mount it from /etc/install-recovery.sh or /etc/install-recovery-2.sh doesn't work, so I'm not sure if by then the mount point is available.
I know this can be fixed using some other tool (like rom toolbox pro) but I'd love to get this working without them, so if anyone has been able to get it working, please help!
Click to expand...
Click to collapse
USB Mounting and moving Apps to USB Storage works in the latest build of CM12.1 Edit: I also found a great app Link2sd to move the data and obb folders too.

Where exactly do I find the options in CM12.1? In the leanback settings or the regular settings accessible via the App Drawer?