[PATCH] Mount storage by UUID / Label

[casino187]

Where do I download v1.0.7 ?  and what are these improvements?

Mount_in_fix_point_and_sdcard_media_rw_1.0.7.rar

[futeko.com]

Where do I download v1.0.7 ?  and what are these improvements?

Mount_in_fix_point_and_sdcard_media_rw_1.0.7.rar

1.0.6 is latest version. OP updated.

I'm not totally sure why 1.0.7 was pulled. pcristi would need to shed some light.

[pcristi]

Where do I download v1.0.7 ?  and what are these improvements?

Mount_in_fix_point_and_sdcard_media_rw_1.0.7.rar

1.0.6 is latest version. OP updated.

I'm not totally sure why 1.0.7 was pulled. pcristi would need to shed some light.

v1.0.6 is latest general more stable over HiSilicon product.

v1.0.5/1.0.6/1.0.7 download from mediafire folder
Mount in fix point and sdcard media_rw
https://www.mediafire.com/?kvlryqpyzcac3

[oxanna]

do you work  in xbmc of egreat A5

[pcristi]

do you work  in xbmc of egreat A5

User reported working on Egreat A5 for v1.0.6.
http://en.egreatworld.com/comunity/index.php?threads/sloved-hard-disk-start-order-in-vidon-xbmc.588/#post-2174

[eccles]

After adding a third external USB drive and screwing up the mount order again, I've finally got around to installing this patch (1.0.6). I remember someone mentioned that mounting by volume name saw the volumes showing as mounted but only one volume showed any content. This also appears to happen to me. I have four drives, one internal and three USB, labelled Media 1, Media 2, Media 3 and Media 4 respectively. Only the internal drive Media 1 shows any content. Did this problem with the previous user ever get resolved?

UUID mounts work fine so I am using this method to map my content. You can rename the mount name from the big string of numbers to whatever you want anyway so once set up it makes little difference.

Incidentally the patch gives the added advantage that the mounts will be correct even if some drives are not turned on.

[eccles]

Further to my last post, I've worked out that when attempting to use the Volume mounts the volume that gets content shown is always the first volume that Android finds and mounts. It might be the internal drive or an external USB drive, whatever Android decides. Any further drives that get found and mounted do not show content by volume name. Content per UUID is recognised. One of my USB drives is a Seagate Hub backup which can act as a hub for two further drives. I attached two portable drives on this and they were recognised by the Q10 as additional volumes. Moreover, with the patch applied both UUIDs were listed in addition to those already attached making a total of SIX identified drives including the internal HDD. I could view the content of every one from within Kodi. The total number of volume names recognised was five, I.e. four of the five attached plus the internal HDD but again only one volume could be read from these mount points.
So, it seems that to accommodate more than four external drives, even if using the volume names work for you, mapping your library to the UUID mounts is the way to go. I got six total UUIDs seen and viewed but I have no idea what the limit is, if any.

[james1961]

you are wrong .
for me, the player after installing the patch, recognizes the hard disk volumes in two different ways :or with its own identifying name, or with its  serial name ( UUID or label ) the problem is another.
every time I turn on the player does not immediately recognize the connected hard disks but  I must  disconnect and the re-connect them  again.
after that the volumes are recognized well with  also the film covers

[eccles]

Nope, not wrong James. I tried what you're suggesting, remounting the USB drives after switch-on. They were reacquired by Android but Kodi still couldn't see their content by volume label, only the label itself. Restarting Kodi had the same outcome. Viewing UUIDs I could see each drive's content. It seems that for some reason not everyone has the same result.
 
But whether or not volume labels work for you, for me at least the use of UUIDs to direct consistent access to content corrects a flaw in the use of Android on the Q10 that is a real pain, and P Cristi deserves a big thanks for writing the patch. An added bonus that I have discovered is that the four device limit can be exceeded by using UUIDs to identify and access external drives. I'd be interested to know what the actual limit is, if any.

Update: 1.07 seems to work for me with volume labels populated correctly. But since UUIDs work ok too I may as well continue using them.

[afss]

Hello Pcristi, please do you know if creating an EJECT app/button for BD-ROM is something possible ?

Currently I have to power down the BD-ROM drive and power back on, as it does not accept pressing the eject  button on the drive (seems to ignore it).

Thanks in advance !!

[Kubrick23]

I have a problem
I tried to execute Mount_in_fix_point_and_sdcard_media_rw_1.0.7.rar

Error:

exit value:126

stdout: null

stderr: tmp-mksh: <stdin>{1}:/sdcard/.RootBrowser/.tmp/RUN_ME.bat: can't execute: Permission denied


How can I solve this problem?

[pcristi]

@Kubrick23
RUN_ME.bat need open on Windows PC not from RootBrowser on Android.

[AVenGER]

Is this patch also working for OFW? Thank you

[giorgiogira]

It didn't work for me. I have Android 10 and HMD 2.1.4 2019-05-31.
Downloaded the patch 1.0.6. Ran it with option 1 Install Standard from prompt dos.
Himedia reboot and then nothing changed.
I don't see any new mounts.
/mnt/media_rw/disk-by-label and /mnt/media_rw/disk-by-uuid this are path you check?

I've done: 
Kodi -> videos -> files -> add videos... -> browse -> root filesystem -> mnt/media_rw and i have only sda1 and sdb1
Am i wrong ?

[eccles]

You appear to have installed the patch correctly so I don't know why it didn't work. Once the patch reboots the box it should be installed. As well as sda1 and sdb1 you should also have disk-by-uuid and disk-by-label. You may have to wait for a minute for the box/patch to pick up the disks after booting.
I have remained on version 2.0.4 so I don't know if the patch still works on 2.1.4. The later firmware versions have all added more bugs than they resolved for me and I can do without Bluray menus.
There is a version 1.07 of the patch which might be worth trying.
BTW I presume you meant android version 7; version 10 isn't available for installation on the Q10.