Develop Bugs

[ROM][24 Feb] IceCreamSandwich Development/Discussion Thread

IceCreamSandwich Development/Discussion Thread
What is this?
Click to expand...
Click to collapse
Hello everyone! This thread is dedicated to Hashcode's and JackpotClavin's work.
This is an Android 4.0.3 ROM not meant for daily use! It is based on CyanogenMod 9.
I will not post any instructions how to flash this to your kindle until it is considered to be ready for daily use. If you know how, feel free to do it.
If you want to join us on IRC:
irc.freenode.net #kindlefire-dev
What works? What doesn't?
Click to expand...
Click to collapse
revxx14 created a Google Spreadsheet to collect known bugs. You can find it right here.
Please take a look at it before reporting any bugs!
A rough list what does not work:
Hardware Video Decoding
Light sensor
There is a SOD bug and no, there is no bluetooth.
Downloads
Click to expand...
Click to collapse
ROM:
2012-02-24 cm9-02-24.zip
ff4e0ea9c27d28b18226e230e2bf2994 by sitic
Changelog:
+init.d support
+fix default.prop
+Test: Apps use now xlarge layout instead of large
More information here
Google Apps:
gapps-ics-20120224-signed.zip
11b5763810edb732379d39b6df9ccbcf
Workarounds / Fixes
Click to expand...
Click to collapse
None needed.
Last words
Click to expand...
Click to collapse
The devs do all of this for free, remember that. Buy them a drink! ♥

it's actually the vold binary found in /system/bin/vold from cm7 ;-) you'll have to change permissions on it once you push it back to /system/bin/ (i just did a 777), then reboot
that's just to have the sdcard properly mount at both /sdcard and /mnt/sdcard. if you wanna do the mass storage you'll have to download the app and do the commands i'm not really a fan of it because unlike other devices, every single filesystem present on our device will mount with the app, so system and data and the sdcard will mount and create like 8 windows on your computer

So the zip file above does the sd card mount with that update or not or is a new update file imminent.

Any hints as to what is or isn't working? At least a vague Idea? Wifi?
Sent from my HTC EVO 3D using xda premium

The zip above was only meant for other devs to see if they could get the sdcard working but now it's working.
Sent from my Galaxy Nexus using XDA App

Wifi works. Video playback (Netflix) and some audio (in Angry Birds) doesn't work. Runs pretty good though.
I'm so excited. Thanks for all your hard work guys.

I've had some random spouts of sound working. sometimes the keyboard will randomly start making those key noises, and it's started working playing angry birds before, but not for long.
---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------
JackpotClavin said:
The zip above was only meant for other devs to see if they could get the sdcard working but now it's working.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
when could you upload a new zip with sd card fix? I'd try a crack at it myself but don't want to mess up anything.
EDIT: nevermind. Seen the new vold file in the op.

Excuse me for being blind, but how do I get to the Trebuchet settings?

JackpotClavin said:
The zip above was only meant for other devs to see if they could get the sdcard working but now it's working.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Could you make a flashable zip where the sd-card is working please?

http://www.multiupload.com/Z5QBY3M80T
Flashable zip with working sd, the launcher from CM9 and the USB mount app. I haven't tested it yet (i am about to flash it). If this isn't allowed then please remove it.
Basically its got vold added to bin, the set_perm line in the updater-zip for it, trebuchet in /system/app and the ICS Usb mounter apk in /system/app.
Enjoy

XperiaPlayer said:
http://www.multiupload.com/Z5QBY3M80T
Flashable zip with working sd, the launcher from CM9 and the USB mount app. I haven't tested it yet (i am about to flash it). If this isn't allowed then please remove it.
Basically its got vold added to bin, the set_perm line in the updater-zip for it, trebuchet in /system/app and the ICS Usb mounter apk in /system/app.
Enjoy
Click to expand...
Click to collapse
Downloading Now as well. Will report back soon
Sent from my Kindle Fire using xda premium

XperiaPlayer said:
http://www.multiupload.com/Z5QBY3M80T
Flashable zip with working sd, the launcher from CM9 and the USB mount app. I haven't tested it yet (i am about to flash it). If this isn't allowed then please remove it.
Basically its got vold added to bin, the set_perm line in the updater-zip for it, trebuchet in /system/app and the ICS Usb mounter apk in /system/app.
Enjoy
Click to expand...
Click to collapse
I should be able to flash this over the other one just wiping /system without any problems, right?

FroyoShark said:
I should be able to flash this over the other one just wiping /system without any problems, right?
Click to expand...
Click to collapse
I flashed this over the last one with no problem. However the USB Mass Storage Tools don't work. I keep getting an error: "You cannot enable UMS without a USB connection."

When it boots you need to do the following:
Check set as default then select:
Trebuchet
com.cyanogeonmod.trebuchet
If the USB mounter comes up just press the back button at the bottom.
ENjoy

How exactly do you set permissions to 777? God I sound like a noob. Lol

I also get the error as well, going to see what it is now. (usb mounter ums)
---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------
If you use my zip you dont need to set the permissions. However if you are doing it on the device (the way described in first post):
adb shell (or terminal emulator)
chmod 777 /system/bin/vold
---------- Post added at 08:21 PM ---------- Previous post was at 08:17 PM ----------
The SD card seems to work if you type this into adb shell:
echo "/dev/block/mmcblk0" > /sys/devices/platform/usb_mass_storage/lun0/file
It then pops up on my screen as Removable Device (F, however windows asks me to format it....

gannon5197 said:
How exactly do you set permissions to 777? God I sound like a noob. Lol
Click to expand...
Click to collapse
If you use adb: adb shell chmod 777 /system/bin/vold
If you use Root Explorer, check all nine boxes.

Thanks!!!
Just wanted to reiterate that XDA is the greatest forum ever!! Thanks to all of the guys working on this, you are incredible!!!

A official alpha would be nice it's abit confusing as who is in charge on this rom seems live everyone is having a dabble here and there for a fully working rom.Good work though guys.

XperiaPlayer said:
http://www.multiupload.com/Z5QBY3M80T
Flashable zip with working sd, the launcher from CM9 and the USB mount app. I haven't tested it yet (i am about to flash it). If this isn't allowed then please remove it.
Basically its got vold added to bin, the set_perm line in the updater-zip for it, trebuchet in /system/app and the ICS Usb mounter apk in /system/app.
Enjoy
Click to expand...
Click to collapse
I will add this to the OP when I get home later!
Sent from my Nexus S using XDA App

swap internal and external SD cards

I made this post over in the HellyBean thread as one user was asking about it, and I decided I would post it in an easier to find place.
Basically it is a shell script that you can toss into /data/loca/userinit.d (if your ROM supports userinit.d, otherwise throw it in /system/etc/init.d) that will swap your internal and external SD cards.
Using this script is at your own risk. Any bricks, fires, alien invasions, etc are not my fault... well, unless they are. I have run this script on my phone and it seems to do as I claim it does.
This script has ONLY been tested on a SGH-T989D phone running the ROM Hellybean on Android 4.3. Based on my memory, I believe this should work on 4.2.2 ROMs as well and should not be dependant on one specific ROM. If you wish to make sure it will work with your ROM, run the following command from the shell/terminal:
mount | grep sdcard
if you see /dev/block/vold/179:97 and /dev/block/vold/179:28 and tempfs as your 3 SD cards, you are good to go. If you get any different values, this script will NOT work for you unless you modify it to match your values. I STRONGLY recommend you check your mount points before running the script as mounting an incorrect partition to your SD card (internal or external) can do unexpected things. If you unintentionally mount your recovery or boot, you could easily corrupt these. I accept no responsibility if anything goes wrong. Make sure you do all of this as root as well where applicable.
STEPS:
1) backup your internal and external SD cards
2) take a nandroid (never hurts to do a nandroid before making a startup script)
3) download the zip file and extract the swapsd.sh file (NOTE: this is NOT a flashable zip. do NOT attempt to flash this from recovery. If you do, you do so at your own risk)
4) copy the script to your phone (however you wish to do that is up to you)
OPTIONAL STEPS
5) copy the script to /data/local
6) run the script
7) verify that your internal and external SD cards are swapped
END OF OPTIONAL STEPS
8) do one of the following:
8A) copy the script to /data/loca/userinit.d
8B) copy the script to /system/etc/init.d (NOTE: you will need to mount /system as RW)
9) change the permissions on the file to 755 (or rwxr-xr-x)
10) reboot and your SD cards will be swapped.
I strongly recommend doing the optional steps as if they fail for any reason, then you do NOT want to run this as a boot script.
Below is the script if you are curious what it is actually doing:
#/sys/xbin/bash
while [ `mount | grep -c sdcard` -lt 3]
do
sleep 10
done
umount /storage/sdcard0/.android_secure
umount /storage/sdcard0
umount /storage/sdcard1
mount /dev/block/vold/179:97 /storage/sdcard0
mount /dev/block/vold/179:28 /storage/sdcard1
mount -t tmpfs -o ro,seclabel,size=0k,mode=000 tmpfs /storage/sdcard0/.android_secure

man how do this does it work really want it kinda lost on how to do it

astonmartin214 said:
man how do this does it work really want it kinda lost on how to do it
Click to expand...
Click to collapse
Pretty easy... copy the files in the attached zip to /data/local/userinit.d if your kernel supports it...otherwise out it at /system/etc/init.d
I would first try running it from anywhere to verify works for though
Sent from my SM-T310 using xda app-developers app

bmg002 said:
Pretty easy... copy the files in the attached zip to /data/local/userinit.d if your kernel supports it...otherwise out it at /system/etc/init.d
I would first try running it from anywhere to verify works for though
Sent from my SM-T310 using xda app-developers app
Click to expand...
Click to collapse
don't get it still lost wish U could make a video of it

astonmartin214 said:
don't get it still lost wish U could make a video of it
Click to expand...
Click to collapse
I'll see what I can do... won't be very exciting as it is all command prompt crap...
Want me to write a pc app for it?
I'll need to look up the rules for distributing adb...
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

astonmartin214 said:
don't get it still lost wish U could make a video of it
Click to expand...
Click to collapse
What part are you stuck at?

can't find the data/local or the file

astonmartin214 said:
can't find the data/local or the file
Click to expand...
Click to collapse
es file explorer then hit the second button on top to get to device, the folder is under there....might have to hit it twice
Your probably overthinking it, I looked it over and the longest process is making a backup...
what rom r u using?
ill walk u step by step if need be....

minlo said:
es file explorer then hit the second button on top to get to device, the folder is under there....might have to hit it twice
Your probably overthinking it, I looked it over and the longest process is making a backup...
what rom r u using?
ill walk u step by step if need be....
Click to expand...
Click to collapse
I'm running carbon ROM & I use es file

astonmartin214 said:
I'm running carbon ROM & I use es file
Click to expand...
Click to collapse
Did you find device with steps given?
keep in mind the carbon i bleave you running it kkat n mod steps are 4.3 based, not sure if it matters but wanted to that out....

minlo said:
Did you find device with steps given?
Click to expand...
Click to collapse
yes I did

go to data then local
reply back
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
place unzipped scrpt file there
Run script file
I hope you already made ur backups as stated by op
---------- Post added at 09:04 PM ---------- Previous post was at 08:52 PM ----------
astonmartin214 said:
yes I did
Click to expand...
Click to collapse
still with me?
the optional steps are to verify compatibility i bleave

minlo said:
go to data then local
reply back
---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------
place unzipped scrpt file there
Run script file
I hope you already made ur backups as stated by op
---------- Post added at 09:04 PM ---------- Previous post was at 08:52 PM ----------
still with me?
the optional steps are to verify compatibility i bleave
Click to expand...
Click to collapse
don't really care about backups

astonmartin214 said:
don't really care about backups
Click to expand...
Click to collapse
yeah i keep my first backup and ddriver backup
but if something happens LOL u were warned!
Did u run the script?

what's next

astonmartin214 said:
what's next
Click to expand...
Click to collapse
did they swap? i cant see the screenies good on my phone
one way to tell i bleave is settings, storage
if so we are on step 8 to make it permanant....
I dont have 8a but i have 8b on jedi rom....
hit settings in es file exp, go to root explorer, pick mount system rw
place script in location stated on 8b....
reply back

astonmartin214 said:
what's next
Click to expand...
Click to collapse
The screenshots you attached do not really show much. The root folder contents should not change, but /storage/sdcard0 and /storage/sdcard1 should change contents.
What should happen after running the script (if it was successful, I found with later builds of HellyBean I needed to do a lazy unmount and to use busybox to unmount it) is /storage/sdcard0 and /storage/sdcard1 should swap contents. So sdcard0 is normally your INTERNAL memory and sdcard1 is normally your EXTERNAL memory, so running the command should swap them.
I have not tested it on kitkat, but I believe it should work. I know that later jellybean builds used vold devices instead of mmcblk devices, but I don't think that kitkat would have removed the mmcblk device.
If you like, I can update the script to use busybox and a lazy unmount? I know to remount /data you need to use a lazy unmount as it is in use.

bmg002 said:
The screenshots you attached do not really show much. The root folder contents should not change, but /storage/sdcard0 and /storage/sdcard1 should change contents.
What should happen after running the script (if it was successful, I found with later builds of HellyBean I needed to do a lazy unmount and to use busybox to unmount it) is /storage/sdcard0 and /storage/sdcard1 should swap contents. So sdcard0 is normally your INTERNAL memory and sdcard1 is normally your EXTERNAL memory, so running the command should swap them.
I have not tested it on kitkat, but I believe it should work. I know that later jellybean builds used vold devices instead of mmcblk devices, but I don't think that kitkat would have removed the mmcblk device.
If you like, I can update the script to use busybox and a lazy unmount? I know to remount /data you need to use a lazy unmount as it is in use.
Click to expand...
Click to collapse
I think we lost him LOL
2nd time this week tried helping some noobs and they dissappear...

minlo said:
I think we lost him LOL
2nd time this week tried helping some noobs and they dissappear...
Click to expand...
Click to collapse
Lol or he figured it out... I hope that is the case
Sent from my SM-T310 using xda app-developers app

need help with "mount system RW"

hi
i am using aokp 28/9/2013 previous version was 20/8.
Now when i try to use metamorph to change the softkeys, it gives the error "/system could not be mounted as RW". Can someone help me what this is and how to fix this? it worked on my previous rom
btw, its given permission by superuser so thats not the problem. And i also went to recovery > mounts and storage > and tapped mount /system
Sry, dont know much about this stuff so can someone help me?
Thanks
EDIT: also tried this app. still doesnt work
https://play.google.com/store/apps/details?id=com.beansoft.mount_system&hl=en

bump..... anyone??

rollerdyke44 said:
bump..... anyone??
Click to expand...
Click to collapse
try from pc
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
or in terminal emulator
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system

samersh72 said:
try from pc
Code:
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
or in terminal emulator
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
tried from pc.... didnt work
What exactly is the error supposed to mean btw?
edit: used root explorer to change permissions of /system to all. still didnt work :/

rollerdyke44 said:
tried from pc.... didnt work
What exactly is the error supposed to mean btw?
edit: used root explorer to change permissions of /system to all. still didnt work :/
Click to expand...
Click to collapse
Why not just click the "remount r/w" button in Root Explorer (navigate to /system, then click it)? From my experience, whenever another app can't mount /system by itself, Root Explorer always helps it outta trouble.
Sent from Google Nexus 4 @ CM10.2

nop
that also didnt work

rollerdyke44 said:
nop
that also didnt work
Click to expand...
Click to collapse
If Root Explorer doesn't remount, there's a good chance you aren't properly rooted. You can verify this by 1) flashing the latest SuperSU zip or 2) flash another ROM and see if things work.
Sent from Google Nexus 4 @ CM10.2

thanks for reply
I CAN mount/remount system as r/w and then r/o using root explorer and i also get a notificatioin that superuser granted to root explorer. But Metamorph still doesnt work. It worked on my previous version as said in 1st post so dont know what the problem is.
i guess its a app specific problem then?

rollerdyke44 said:
i guess its a app specific problem then?
Click to expand...
Click to collapse
Did the update change OS, by that I mean 4.2.2 to 4.3? Perhaps metamorph doesn't work properly with 4.3. Have you tried uninstalling it and reinstalling the app?
If all you are doing is changing softkey images, I am pretty sure AOKP has options to do that within the ROM

metamorph has not been updated lately and therefore has not been made compatible with 4.3+ hence why you receive the /system rw error . if you check busybox and run the script or manually thru terminal you can verify if /system is RW or not.

rollerdyke44 said:
thanks for reply
I CAN mount/remount system as r/w and then r/o using root explorer and i also get a notificatioin that superuser granted to root explorer. But Metamorph still doesnt work. It worked on my previous version as said in 1st post so dont know what the problem is.
i guess its a app specific problem then?
Click to expand...
Click to collapse
I have the same freaking problem with adblock app.....
Can change it in root explorer but still got the error flashed new superuser ap but didnt work
Sent from my Galaxy Nexus using xda app-developers app

kjax said:
metamorph has not been updated lately and therefore has not been made compatible with 4.3+ hence why you receive the /system rw error . if you check busybox and run the script or manually thru terminal you can verify if /system is RW or not.
Click to expand...
Click to collapse
Yeah it might be an app issue then. Thanks
demon2112 said:
I have the same freaking problem with adblock app.....
Can change it in root explorer but still got the error flashed new superuser ap but didnt work
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You also use aokp??

Nooe on cataclysm
Sent from my GT-I9300 using xda app-developers app

Have you got the solution ...??

Saskai1 said:
Have you got the solution ...??
Click to expand...
Click to collapse
Assuming you have a similar problem, how exactly is it going? This thread is a bit 'outdated' now because OP had trouble with an app intended for earlier Android versions. Apparently he was trying to use Stericson's Metamorph on a wrong Android version, thus it wasn't able to mount system R/W...
Sent from my Motorola XT1563 using XDA Labs

Mount samba share

I am trying to download to my samba share through xbmctorrent plugin but i get an error that it cannot download to unmounted share.
is there any way of mounting the sambashare in the ftv system so it will see it as an internal folder or something ?

I am also looking to do the same thing for retroarch. The 8GB internal storge aint big enough for all the roms

quacka said:
I am also looking to do the same thing for retroarch. The 8GB internal storge aint big enough for all the roms
Click to expand...
Click to collapse
Did you root your fire tv? Did you see drive in xbmc? If not then you have to root it then mound hdd. Follow following guide.
http://forum.xda-developers.com/showthread.php?t=2783805

rooted
gujju said:
Did you root your fire tv? Did you see drive in xbmc? If not then you have to root it then mound hdd. Follow following guide.
http://forum.xda-developers.com/showthread.php?t=2783805
Click to expand...
Click to collapse
yes i have rooted it and yes i see it in xbmc. the problem is with xbmctorrent plugin that cannot download to an unmounted share drive.

gujju said:
Did you root your fire tv? Did you see drive in xbmc? If not then you have to root it then mound hdd. Follow following guide.
http://forum.xda-developers.com/showthread.php?t=2783805
Click to expand...
Click to collapse
Think this is missing the point, the issue is attempting to mount network shares as native paths, not within another app. The link provided only discusses USB drives, not network.

Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.

hmagoo said:
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
Click to expand...
Click to collapse
Thanks hmagoo, that worked for me finally.
I think I was trying it via SSH hence never got it to work.
How do I make the share remain after a power cycle?

hmagoo said:
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
Click to expand...
Click to collapse
Please make a guide
If using this code using ADB allows us to mount network drives a little more elaboration needs to be done..

Vylle said:
Please make a guide
If using this code using ADB allows us to mount network drives a little more elaboration needs to be done..
Click to expand...
Click to collapse
I only tried using samba shares because I wanted to launch MXPlayer as an external player to play xvid files through xbmc, but I found it was easier to just disable libstagefright and mediacodec in xbmc settings and the xvid files play smoothly.
if you used an app like Script Manager you should be able to run a script upon boot-up that makes the directory and mounts the share.

hmagoo said:
I only tried using samba shares because I wanted to launch MXPlayer as an external player to play xvid files through xbmc, but I found it was easier to just disable libstagefright and mediacodec in xbmc settings and the xvid files play smoothly.
if you used an app like Script Manager you should be able to run a script upon boot-up that makes the directory and mounts the share.
Click to expand...
Click to collapse
I have installed tasker. I set the command to run on boot as Shell Script but it doesn't seem to work. it seem only to work when running via adb shell for me. No idea what I am doing wrong

I have to apply the script after every reboot also. Has anyone found a way to keep it after boot?

hmagoo said:
Code:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
the mount command has to look like that, in order for it to be seen by apps I had to mount to /mnt/obb/nas (make the nas directory)
that may not be your solution but it should help, I have seen people say they can set up a mounting app to use those parameters.
FYI, if you are going to try the mount out from the command line you need to be in adb shell, not an ssh session.
you can find answers like this in search as well.
Click to expand...
Click to collapse
dont want to get too off topic but what if you are using NFS. since that doesnt require a username and password what would the command look like?

mejdam said:
dont want to get too off topic but what if you are using NFS. since that doesnt require a username and password what would the command look like?
Click to expand...
Click to collapse
same sort of thing
mount /mnt/obb/nas 192.168.1.23:/path/to/share

adionita said:
I have to apply the script after every reboot also. Has anyone found a way to keep it after boot?
Click to expand...
Click to collapse
Sorry to bump this old thread but I'm also in the need of this,
Have you figured out a way of auto remounting the share???

[HOW-TO]Full USB OTG on Media Players in Marshmallow

It's my first relevant post in here so please be benevolent and friendly to me .
Hello everyone,
After long hours of roaming around on the internet, Moto forums, PowerAMP forums (you wouldn't believe how many people posted this problem in there), huge exchange of emails and debugs to the Nexus Media Importer dev, and checking out many many topics here on XDA, I finally came across the only way to use an USB-OTG pendrive as a music library, and having Android detect it (through the Media Service) and build the music library for other media apps to use.
tl dr; Problem: You wanted loads of music without wasting precious internal memory. You tried using an USB pen but no mp3 apps were able to find the files, nor stickmount, nor whatever.
This is so far the only way to do this on android Marshmallow.​
Believe me, I've tried almost everything one can do, including using the Nexus Media Importer, Stickmount, OTG Helper, etc (spoiler alert, none of these worked).
Why is this happening, you ask? Well, Google changed things on Android 6.x.x so much regarding filesystems and USB support that full read/write on USB OTG with other apps no longer works, although I've never tested on previous versions of Android. But I finally managed to find a way to do it, and here I intend to share it with you guys.
Requirements - Rooted phone and permissive SELinux (what is that and how do I do it? don't worry, it's easy and I'll explain a bit later)
1st step - Verify that your phone is capable of using USB-OTG. If it is not, check on play store for other apps that supposedly can enable USB Host support on your phone, although I've never tried them because I never needed, so I can't say anything. My phone is a Moto X 2014 and it comes with OTG support embedded.
2nd step - Format your pendrive as NTFS. This is very important because...
If you use your pendrive as Fat32, Android will mount it to a folder in /data/media_rw/blablabla with GID and UID 1023 (media_rw), which most apps don't have permissions to access, thus they won't be able to find your pendrive and build a music library. Why? Well, glad you asked...
...Since Fat32 doesn't support the linux permissions system, Android mounts the pendrive with the FUSE fs wrapper, which cloaks a permission system hard-coded into some file in the Android system that I wasn't able to tell how could I modify it in order to set the pen permissions as 777 root root.
You can do so by plugging your pen on a Windows PC and right clicking -> Format. Remember to backup your data, otherwise you will lose everything. Your pen will still be able to be used on Windows pcs and Macs. You could also use other fileformats...
... like EXT4 or f2fs or exFAT or whatever, but do it at your own risk. I have no idea if those would work, despite them being able to use the linux permission system.
3rd step - Install the wonderful app Paragon HFS and NTFS mounter from appstore or whatever. They say it isn't compatible with marshmallow but it is, the only issue is that it can't mount a pendrive automatically but it's very easy to do it manually. In the settings menu, you can set SELinux as permissive. Since I'm not an android dev, only an ambicious amateur, I can't really explain what it does or what happens when you do that. So far, neither me or my phone died because of that, so.
Oh by the way, whenever you insert the pen , Android will say it's corrupted and ask you to format it. DO NOT DO IT! That happens because Android doesn't natively support NTFS (hence using an external app to solve that). Oh, and since we're talking about that, there is a way for Android to natively support NTFS...
..., just search it up on XDA. Beware that it's outdated and it won't work on Marshmallow either, unless you edit the copymodulecrc script, but that goes beyond my knowledge. For now, stick to the plan.
4th step - You need to choose the folder which you want to mount the pen to, which will be a folder in the root Android folder (I chose /pen so that I wouldn't forget)
You are now probably thinking, "That's insane! You need to edit init.rc in order to do that!" Well, you're kinda right, but there is a workaround for that. Why do I do this? Well...
... if you mount the pen in another random folder such as /storage/emulated/0/pen it won't work because all the folders underlying that one have certain permission issues that don't let other media apps be able to search for music files.
So here I'll show you two ways of accomplishing this.
4.1 Editing init.rc - This is very complex and NOT RECOMMENDED unless you're very comfortable with messing with boot files. PLEASE DO NOT DO THIS if you aren't sure of what you're doing, don't tell me I didn't warn you.
So in order to do this, well, I won't explain it to you. Search it up on the internet, it's very complex and too big for me to post here. But in the end what you want to do is edit the init.rc file, adding two lines:
"mkdir /pen" and "chmod 777 /pen".
4.2 Creating a script that runs on boot - This is the one method I recommend since it's harmless, but you have to install yet another app, that allows you to run scripts at boot. I used script manager. Then create a script that mounts the / folder as rw, creates the folder /pen, chmods it to 777. I used the following:
#!/system/bin/sh
su -c mount -o rw,remount /proc /
su -c mkdir /pen
su -c chmod 777 /pen
I tried other mount -o commands with rootfs instead of /proc but they didn't work. I don't know the difference but I hope it's harmless. Anyways, let's move on.
Run the script to see if it works, and to create the folder. Use a rooted file explorer to verify if the folder was created.
5th step - Reboot your phone if you had to set SELinux as permissive, and type on the Terminal "su -c getenforce" to confirm that your SELinux is permissive.
VERY IMPORTANT - On the Paragon app, open settings and disable FS access rights, otherwise it's the same as mounting a Fat32 pendrive - not what we want.
On the Paragon app, choose the folder we created before as the folder to mount the pen to, and mount the pendrive. If you followed all the previous steps correctly, the app won't have any issues mounting the pen.
6th step - Find a way to enforce Android building a media library with the new files in the USB OTG pendrive. There are many ways to do this and I recomment the one I used, but I will tell you other ways.
I used the app jetAudio which is a media player that can also forceably build a media library. On jetAudio settings menu, press "Rebuild media library" and point to the /pen folder. It will start reading all the files and Android now detects your pendrive as a media library.
Another way would be to use an app called FolderMount, and creat a symlink from the /pen to another folder in your emulated SD storage (you know, the only folder you have access to if you're not rooted), and wait for some time until hopefully Android detects your new music. If you don't want to use FolderMount, do a symlink with another method (like the ln command)
EDIT - Another cool way I found elsewhere on StackExchange is to run this command (through a script or whatever):
am broadcast -a android.intent.action.MEDIA_MOUNTED -n com.android.providers.media/.MediaScannerReceiver (-d file:///pen)
which forces Android to run a media scan. The part on parenthesis is optional, you can use it to choose the folder in which Android runs the media scan.
Hurray! Congrats for reaching this part of the post. If you did everything correctly, all media apps will finally be able to find the files. I posted some screenies to orientate you.
Feel free to ask anything and I will try to answer or explain. Remember that I'm no Android dev so my knowledge is limited. Feel free to thank me, if you want too.

reserved post

Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...

AndDiSa said:
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
Click to expand...
Click to collapse
It's not as straight-forward as you're saying.
Most media player apps that weren't updated to support Android 6's native USB OTG support will not be able to read a pen's contents. This topic that I made is aimed to circumvent the issue by mounting the pen in a different way. That bug you mentioned is not something I want to solve, and even if a new kernel solved the issue that I'm talking about, most manufacturers wouldn't update their devices...

Ok, you may be right with apps which are not yet updated to support Marshmallow, I didn't check that.

gaferreira13 said:
It's not as straight-forward as you're saying.
Most media player apps that weren't updated to support Android 6's native USB OTG support will not be able to read a pen's contents. This topic that I made is aimed to circumvent the issue by mounting the pen in a different way. That bug you mentioned is not something I want to solve, and even if a new kernel solved the issue that I'm talking about, most manufacturers wouldn't update their devices...
Click to expand...
Click to collapse
Oh, and maybe now that I think of it, this could solve the problem, since mounting/unmounting is done with the Paragon app instead of Android. Give it a shot

AndDiSa said:
Why so compilcated? USB-OTG is supported on the fly by Android 6.0 / Marshmallow, but unfortunately most of the N7-kernels have a bug which lead to reboot on unmounting the OTG-Device. Nevertheless the next version of Android 6 AOSP on Grouper should have it fixed this issue ...
Click to expand...
Click to collapse
Using native otg function, you can only copy files between phone and otg dive. To open a file e.g. To install apk from otg, you have to first copy it to phone's storage. On many media player, video can only be played sequentially (seek bar doesn't work).

Stuck at step 4.2, folder is not created

kashinath said:
View attachment 3746340Stuck at step 4.2, folder is not created
Click to expand...
Click to collapse
Hey, is there any way for you to determine the path of your root folder? Maybe using ES File Explorer. For some phones, the root folder isn't pointed to /.
EDIT - If you can't do that, try replacing the first of those commands with the following:
su -c mount -o rw,remount,rw /system

I'm also getting the same issue as kashinath, won't let me create pen. I've also tried pointing the mounter to a directory in /storage/emulated/0/pen but it seems to just crash and restart the app.
EDIT:
Okay so I've solved the problem completely differently. The otg storage is found in /mnt/media_rw, so I used the app "FolderMount [ROOT]" to point the folder "pen" (in the internal storage) to the /mnt/media_rw/*random string* folder. I then used the app "media.Re.Scan:" to force the media scanner to scan that folder as it didn't seem to want to do it. Now all apps seem to be working.
What tipped me off about this was this post: http://forum.xda-developers.com/nexus-6/help/marshmallow-usb-otg-mounting-media-t3230588
It seems you have to turn the folder mount on/off every time you plug/unplug the USB drive otherwise it won't play the files.
Thanks for the detailed instructions nonetheless.

Viridis said:
I'm also getting the same issue as kashinath, won't let me create pen. I've also tried pointing the mounter to a directory in /storage/emulated/0/pen but it seems to just crash and restart the app.
EDIT:
Okay so I've solved the problem completely differently. The otg storage is found in /mnt/media_rw, so I used the app "FolderMount [ROOT]" to point the folder "pen" (in the internal storage) to the /mnt/media_rw/*random string* folder. I then used the app "media.Re.Scan:" to force the media scanner to scan that folder as it didn't seem to want to do it. Now all apps seem to be working.
What tipped me off about this was this post: http://forum.xda-developers.com/nexus-6/help/marshmallow-usb-otg-mounting-media-t3230588
It seems you have to turn the folder mount on/off every time you plug/unplug the USB drive otherwise it won't play the files.
Thanks for the detailed instructions nonetheless.
Click to expand...
Click to collapse
Yeah forget mounting anything in the /storage/emulated/0...
According to the post you linked in your comment, "6.0 mounts to /mnt/media_rw/ but I can't seem to get any media players to see it. I tried creating a symbolic link in /storage/emulated, but I get an error with root explorer about symbolic links not being supported" which is exactly what happened to me
If you don't like the folder mount alternative you can always do a bind command (but i'm not sure how it works), search it up and see if you get any results.
Is your pen in Fat32 though?
There is a workaround for the pen thing... If you use Total Commander and want to edit any files in /, it asks you to run a command that mounts the / folder. Try to see what command it is and replicate it into the script, then the rest might work.

Thank you so much !! It worked on my XT1033 falcon dual sim - MM6.0 identity crisis 1.3a . I can finally restore all my nandroid backups.
Just to correct shouldn't the last command in the script be
su -c chmod 777 /pen
instead of
su -c chmod /pen 777

4k5blr said:
Just to correct shouldn't the last command in the script be
su -c chmod 777 /pen
instead of
su -c chmod /pen 777
Click to expand...
Click to collapse
No, thank you
And, damn you're right, lol I'll correct it ASAP, thanks a lot for pointing it out

I'm a complete newbie at this, in fact I rooted my device just to do this
Anyways I'm getting the same issue kashinath is getting and tried the other command you recommended (su -c mount -o rw,remount,rw /system ) wich also didn't work
In that reply you also said that the root folder is different between devices so, if I determine the path to my root folder, where exactly in the script do I have to put it? (Again I'm a newbie)

Arcane35 said:
I'm a complete newbie at this, in fact I rooted my device just to do this
Anyways I'm getting the same issue kashinath is getting and tried the other command you recommended (su -c mount -o rw,remount,rw /system ) wich also didn't work
In that reply you also said that the root folder is different between devices so, if I determine the path to my root folder, where exactly in the script do I have to put it? (Again I'm a newbie)
Click to expand...
Click to collapse
For my phone the Root folder's path is "/" so I'll put 2 arrows where the path to root is in the command:
" su -c mount -o rw,remount /proc --> / <-- "
So imagine your root path is /root
The command would look like this: " su -c mount -o rw,remount /proc /root " (without "" of course)
If you still can't find the path to your root folder, try searching on the internet "root folder for xxxxx phone"
Hope it helps

gaferreira13 said:
For my phone the Root folder's path is "/" so I'll put 2 arrows where the path to root is in the command:
" su -c mount -o rw,remount /proc --> / <-- "
So imagine your root path is /root
The command would look like this: " su -c mount -o rw,remount /proc /root " (without "" of course)
If you still can't find the path to your root folder, try searching on the internet "root folder for xxxxx phone"
Hope it helps
Click to expand...
Click to collapse
Turns out my phone's root folder is also / , and I'm still getting the same error (mount: '/' not in /proc/mounts)
Maybe its because I have Nougat :/
EDIT: So I think I managed to kinda work around that, I change the command to " su -c mount -o rw,remount / " and it ended up making the pen folder and no errors came out. So I then proceeded to open Paragon, disabled FS access rights, ensured that SELinux was permissive (it is) and change the mount point to the /pen folder, I finally proceeded to manually mount the thing BUT even tough that in my notifications says that I mounted it, on the app it still says that my Flash Drive is still not mounted (even tough it detects it and know that it is an NTFS file system). Basically whenever I try to mount my Flash Drive it wont work even tough the app detects it.

Arcane35 said:
Turns out my phone's root folder is also / , and I'm still getting the same error (mount: '/' not in /proc/mounts)
Maybe its because I have Nougat :/
Click to expand...
Click to collapse
Ooooh. Remember the topic is called "Full USB OTG on Media Players in Marshmallow"
I can't help you then, sorry. The only thing I can tell you is to open the /proc/mounts file as text on the top there should be a command that tells android to mount the root folder as rootfs I believe.
Maybe that could help.

Arcane35 said:
EDIT: So I think I managed to kinda work around that, I change the command to " su -c mount -o rw,remount / " and it ended up making the pen folder and no errors came out. So I then proceeded to open Paragon, disabled FS access rights, ensured that SELinux was permissive (it is) and change the mount point to the /pen folder, I finally proceeded to manually mount the thing BUT even tough that in my notifications says that I mounted it, on the app it still says that my Flash Drive is still not mounted (even tough it detects it and know that it is an NTFS file system). Basically whenever I try to mount my Flash Drive it wont work even tough the app detects it.
Click to expand...
Click to collapse
Try to open the /pen folder, try to see in the properties of /pen if the permissions are set to 777.

gaferreira13 said:
Try to open the /pen folder, try to see in the properties of /pen if the permissions are set to 777.
Click to expand...
Click to collapse
It is set as 0777, so yes (if the 0 is not supposed to be there)

Arcane35 said:
It is set as 0777, so yes (if the 0 is not supposed to be there)
Click to expand...
Click to collapse
Hmm... If you can open the folder fine and maybe create a file in there or something then I can't help you any further. The paragon app doesn't let you do much regarding troubleshooting.
Try using the methods that other people did like using Foldermount or something like that.