[APP][18.01.2017] StickMount v3.50 [ROOT]

[jmark13]

My N7 tablet reboots when I unplug the OTG cable after unmounting. I am using Jelly Belly v11 (4.2.1) with Leankernel 5.1.1, as well as stickmount pro 2.1. Any suggestions. I've had this happen on other ROMs as well which I always clean install. Any idea how to fix?

 

[oct_7]

The file structure thing has nothing to do with Stickmount, it's entirely because the version of CWM you have on there is not updated for the file system changes Google made with 4.2. Update your CWM to the latest version (or even better, swap to the latest TWRP), and this will stop happening.

My bad. Thanks for the info.

 

[DANOFDANGER]

My N7 tablet reboots when I unplug the OTG cable after unmounting. I am using Jelly Belly v11 (4.2.1) with Leankernel 5.1.1, as well as stickmount pro 2.1. Any suggestions. I've had this happen on other ROMs as well which I always clean install. Any idea how to fix?

I get this too, cant leave the tab on with something plugged in otherwise it just turns off.

 

[AlexGraves]

My N7 tablet reboots when I unplug the OTG cable after unmounting. I am using Jelly Belly v11 (4.2.1) with Leankernel 5.1.1, as well as stickmount pro 2.1. Any suggestions. I've had this happen on other ROMs as well which I always clean install. Any idea how to fix?

Does it happen on stock 4.2.1 as well?

I am running rooted stock 4.2.1 Android and never experience any of that.

Sent from my Nexus 7

 

[Matchstick]

Is there an easy way to tell of the NTFS and exFAT binaries are being picked up ?

I've copied the ntfs-3g and mount.exfat-fuse files to the root of internal storage on my Nexus 7 but I'm still only getting read-only NTFS support and I'm not sure if that'a because the binaries aren't being picked up by Stickmount or if they just aren't compatible.

 

[Chainfire]

My N7 tablet reboots when I unplug the OTG cable after unmounting. I am using Jelly Belly v11 (4.2.1) with Leankernel 5.1.1, as well as stickmount pro 2.1. Any suggestions. I've had this happen on other ROMs as well which I always clean install. Any idea how to fix?

This doesn't happen on my stock N7. Stuff like this is *usually* the kernel.

 

[DANOFDANGER]

This doesn't happen on my stock N7. Stuff like this is *usually* the kernel.

im on stock, still happens to me.

 

[creeve4]

Galaxy Nexus running Stock Android 4.1.2 with franco.Kernel r300 and Stickmountv2.10.

I have a 64 GB Transcend flash drive formatted as FAT32.

I put a few mp3 files on the drive to test Stickmount. When I connect the drive, Stickmount recognizes it and the "Preparing USB storage" notification appears and runs for about 2 minutes. Then I get a popup notification from Stickmount telling me the drive is mounted, but immediately after I get another popup Stickmount notification telling me the drive is now unmounted and a notification which says "Removed USB storage." I then try manually mounting and unmounting neither of which have any effect.

Also, while the "Preparing USB storage" process is running, if my screen goes off I cannot wake my phone.

Faulty cable? Drive too big (there are only 10 mp3 files totaling ~100 Mb)? Hardware issue? Stickmount issue?

 

[O2Blevel]

My N7 tablet reboots when I unplug the OTG cable after unmounting. I am using Jelly Belly v11 (4.2.1) with Leankernel 5.1.1, as well as stickmount pro 2.1. Any suggestions. I've had this happen on other ROMs as well which I always clean install. Any idea how to fix?

My tablet will freeze and reboot if after dismounting I remove the otg cable + usb stick. This happens to me on the LeanKernel and 4.2, but not with the LeanKernel and 4.1.2. The funny thing is it will freeze and reboot by removing just the otg cable by itself. This also happens with the trinity kernel, but not the stock kernel. I use the stock ROM.

 

[creeve4]

Galaxy Nexus running Stock Android 4.1.2 with franco.Kernel r300 and Stickmountv2.10.

I have a 64 GB Transcend flash drive formatted as FAT32.

I put a few mp3 files on the drive to test Stickmount. When I connect the drive, Stickmount recognizes it and the "Preparing USB storage" notification appears and runs for about 2 minutes. Then I get a popup notification from Stickmount telling me the drive is mounted, but immediately after I get another popup Stickmount notification telling me the drive is now unmounted and a notification which says "Removed USB storage." I then try manually mounting and unmounting neither of which have any effect.

Also, while the "Preparing USB storage" process is running, if my screen goes off I cannot wake my phone.

Faulty cable? Drive too big (there are only 10 mp3 files totaling ~100 Mb)? Hardware issue? Stickmount issue?

Formatted the drive as ext2. Now Stickmount mounts it, but nothing is displayed on the drive. I triggered a media rescan, still nothing. Just an empty sdcard/usbStorage/sda1 folder.

The light on the USB drive turns on and blinks (indicating that it is being accessed).
I have the PRO version and have selected automatic media scanning and to kill processes that may be using the drive
My Nexus is rooted and running SuperSU.

UPDATE:
I was able to get the USB drive working after creating two ~32GB partitions on the drive. I guess 64GB is too much?

 

[jmark13]

This doesn't happen on my stock N7. Stuff like this is *usually* the kernel.

Chainfire, I am happy to report that after flashing the Franco Kernel, thus removing LeanKernel, I can now unmount and remove the OTG cable with no reboot. The kernel is most likely the culprit. Thanks for the awesome app!

 

[tobbbie]

Automount used to work on Xperia Ray (sirkay - xKernel) no more

I use the external sticks only rarely but older versions of stickmount have well auto-mounted all my USB sticks.

Now I noticed that still stickmount is fired up (toast message) but it does not find a drive then. Manually starting stickmount and then pushing "Mount" will always work. Also if there is another mount-helper, so you have to choose which one to pick until you made a default selection, then selecting stickmount will also work with automount.

So it seems pretty clear that the initialization of the USB device may take some more time than stickmount is spending by default.
As older versions worked - can I get access to those? Or could you add a delay option before starting to search a drive on the USB?

BTW: Many of my simple card-readers (which look like a USB-stick) will not be hooked on USB correctly as they draw too much power from the line - at least they announce that to the device - and so they are not hooked right and subsequent program access (like from stickmount) do not succeed. You can check for the powerclass easily on your PC with Nir Sofer's USB DevView. For my device those with 100mA work, but 500mA do no more. This is sad, as the smallest good microSD reader I have from SanDisk (MobileMate Micro) claims 500mA and it fails

 

[tobbbie]

utf8 support - this way it works for me

I noticed that all mounted sticks are not correctly supporting extended characters like German Umlauts (äöü). I can either have them on the device correct (read/write) or if the stick is on the PC (read/write). Cross-wise read/write never works right - neither side can read the encoding of the other

Obvious way-out: tick the utf-8 box in stickmount - but that did not change anything.

Cross-check: does it work right for my sdcard (also FAT32) in the device and if written from card-reader externally: YES it does!
So what is the magic that allows a vfat mount of the sdcard in the device work right, while the same device does not mount the usb-stick correctly?

I studied the mounts on the device and noticed that the sdcard is mounted like this:

/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

While the mount of USB Stick is done like this:
/dev/block/sda1 on /mnt/sdcard/usbStorage/sda1 type vfat (rw,nosuid,nodev,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

Checking a changed mount with a test like:
mount -t vfat -o utf8 /dev/block/sda1 /mnt/sdcard/usbStorage

delivers a mount like:
/dev/block/sda1 on /mnt/sdcard/usbStick type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

and finally correct special characters also for cross-wise read/write (as expected).

When searching for the "usual treatment" of the character set problem it seemed that it is advised to change the iocharset parameter, however this only works if the kernel supports it. It seems that mine does not but still the onboard tools permit to get the correct encoding via the "-o utf8" parameter.

Now my kind request is: Could you possibly include this "-o utf8" as another option (or even default) when mounting a FAT partition?

 

[NoSubstitute]

What's missing to have working Write access on NTFS?

Is there an easy way to tell of the NTFS and exFAT binaries are being picked up ?

I've copied the ntfs-3g and mount.exfat-fuse files to the root of internal storage on my Nexus 7 but I'm still only getting read-only NTFS support and I'm not sure if that'a because the binaries aren't being picked up by Stickmount or if they just aren't compatible.

Yet another N7 with read-only support. Bricked 0.55 kernel with stock rooted ROM.

 

[Chainfire]

Here's another test version, please let me know if this fixes some issues for you.

NTFS read-only
I have adjusted the mount order, that if ntfs-3g is present (which can mount r/w), it has higher priority than kernel based ntfs mount (which is r/o). To those having this problem, your kernel probably supports ntfs mounting and due to this ntfs-3g had been ignored. Let me know if this fixed the problem for you. (you still need ntfs-3g for this to work)

UTF-8
I've made some changes to the mount code and testing order during mount with UTF-8 enabled (which is now enabled by default). It seems to work for me with various German and Chinese characters. Let me know if this fixed the problem for you.

Mount delay
As there might be a timing issue between USB connection, StickMount launch/mount, and kernel device detection, I've added the mount delay option (1000ms by default). This is the amount of time StickMount will wait after being notified of a new device being connected before attempting to find and mount partitions. Let me know if this fixed missing mounts/partitions for you (and if so, which ms value you had to use)

This is a test version that may soon be removed and should be replaced by a Play release. Do not redistribute/post elsewhere.

Please comment in this thread, not on Twitter or whatever.

 

[AlexGraves]

Reverting back to ver. 2.10...
2.11 test version didn't improve anything because I'm not using any special characters in my daily use, but it presented a new (small) problem.
Whenever it mounts or unmounts, it triggers an error message for my SwiftKey3 keyboard. It causes Swiftkey to unable to load its language module.

Sent from my Nex7

 

[shaarky]

StickMount-v2.11-test-1.apk working fine (Czech characters with UT8 showing up correctly, with previous version it wasn't) ! Thanks

 

[tobbbie]

For me things are partly ok now:

• setting a delay has no impact, the toast comes immediately when connecting the stick and it finds nothing. I noticed that the delay entered is happening only when you push "mount" in the panel, but not when auto-started!
• Mounting is done with utf8, but not by default as written. You have to set the relevant entry in the menu - not sure if the kernel remark is still valid here- Thanks!

Not sure why AlexGraves has a problem with his mounts. Does the USB mounted device later refer to a file located on the mounted device itself? Or is the delayed mount (which is not delayed for me) the problem there? For the former case, just deactivate the UTF8, for the latter set delay to 0.

---------- Post added at 05:54 PM ---------- Previous post was at 05:47 PM ----------

Another remark for the delay: maybe it is better to start finding partitions immediately but if none found, then to loop in an interval of e.g. 500ms (or shorter for the impatient) for "max amount" (to be specified) to find them after the stick is ready. This delivers fastest response for any stick and does not force you to wait for the slowest

 

[sergialess]

Not working for me...

Hi,

As the USB-OTG function worked well in my old S2, it never won't on my Galaxy Nexus .
I can figure out that the cable is faulty, but the same cable works fine in my other tel.

Whenever I put the pendrive (16GB, Fat32), Stickmount gets crazy with the sequence: "searching... mounts 0... searching... mounts 0", and the led of the pendrive is always flashing.

With Android 4.2.1, the USB-OTG function is suppossedly supported natively. Not at least for me...

Thanks anyway for your effort.

 

[kar10s]

Hi,

(I think) I found a minor bug (both in v2.10 and v2.11) - when I connect several USB drives using USB HUB, all the usb are connected properly (as sda1, sdb1...), but there is also created one empty directory sda - there probably is a short delay after inserting second USB and before creating the sda directory (on one try I noticed that it was not here at first, but appeared after few seconds) - there also happens some name changing to sdb and back when the USB devices are disconnected and reconnected.

And one more thing (this one I was not able to replicate on neither version, but it happened to me vith v2.11) - somehow (probably because of the "rapid" usb stick switching) the StickMount stopped mounting the USB sticks. When I stopped the APP, deleted its cache and data, it started working again, but then sudenly my tablet rebooted, but I already experienced this kind of behavior (I mean the rebooting) when I disconnect the USB that was being used, so it probably has nothing to do with StickMount (I experienced this on v1.0 (or what was it) on Stock 4.1.2, now I have Stock 4.2.1)

Otherwise, the app is working perfectly. Thank you for your hard work!