futeko.com FORUM
Old Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: futeko.com on November 30, 2016, 02:11:37 PM
-
This topic replaces the original (http://www.futeko.com/newforum/index.php?topic=1398.0 (http://www.futeko.com/newforum/index.php?topic=1398.0)) so opening post can always contain latest version and instructions.
Big thanks to qqq1971 and pcristi. It's all their work.
Compatible with all Android 5.1 and Android 7.0 firmwares.
This patch creates persistent mount locations according to UUID and drive label for attached local storage (internal SATA and USB). This location will stay the same on every boot, eliminating the problem where Q5/Q10 Pro can be inconsistent in where it mounts storage (sda1, sda2, sda3 etc) when multiple USB HDDs are attached.
Mount path:
/mnt/media_rw/disk-by-uuid/<uuid>
/mnt/media_rw/disk-by-label/<label>
/sdcard/media_rw/disk-by-uuid/<uuid>
Restrictions
* Only first 4 mounted disks will be linked
* For disk with multiple partions only first partition will be linked.
* If disks has identical labels only first disk will be linked.
* Wait about 2 min after boot. Master init script has delay before my script will be run.
* Be careful with deleting files from /sdcard/media_rw/ --> can lose your /video/movie/music/picture/etc...
USE AT YOUR OWN RISK!
Version History
v1.0.6 LATEST STABLE VERSION
- bug fix support Android 5.1.1
- preliminary support Android 7.0 f/w
- fix missing ext2, ext3, ext4 partition Android 5.1.1 / 7.0 f/w
v1.0.5
- bug fixed
- add /sdcard/media_rw/cd-rom/srXX
- full support Android 5.1.1 f/w and HMD 2.0.0 Android 7.0
(not more updates, upcoming HMD 2.0.1 f/w will not supported)
v1.0.4
- add DVD/BD-ROM support
- add RUN_ME.bat option not mount/sdcard/media_rw/disk-by-uuid/<uuid>
v1.0.3
- rewrite scripts to support safe hotplug
v1.0.2
- port back to Android 5.1.1
- fix 100 second delay of start running script on first official Android 7.0 f/w
- mount all partition /mnt/media_rw/disk-by-uuid/<uuid>
- mount first partition /mnt/media_rw/disk-by-label/<label> in case of sda5, sdb5,... and not only for sda1,sdb1,...
- additional mount o bind to /sdcard/media_rw/disk-by-uuid/<uuid> --> request for HiMedia DLNA Server
Instructions:
- Download Mount_in_fix_point_and_sdcard_media_rw.rar to Windows PC: Download 1.0.6 here: http://www.mediafire.com/?0u9h678yy61c7h1
- Unzip
- Execute RUN_ME.bat at command prompt
- Insert Q5/Q10 Pro IP address
There is also a beta 1.0.7 version which incorporates derkallevombau's work on page 4 of this thread. Download here: https://www.mediafire.com/?kvlryqpyzcac3
-
Porting my question over here - can this be evolved to bring back the DVD/BD-ROM support functionality we had with android 5 ?
Thank you !
-
Porting my question over here - can this be evolved to bring back the DVD/BD-ROM support functionality we had with android 5 ?
Thank you !
I'm sure with little script correction. But i don't have external rom drive to check it.
General idia is include into list of discs (sd*) list of rom drives - sr* and just mount it like discs. Additionaly check that sr* has UDF fs.
~> sudo blkid | grep sr
root's password:
/dev/sr0: UUID="48CB99C400A2640E" LABEL="BERLIOZ" TYPE="udf"
Box supports udf:
~> adb shell cat /proc/filesystems | grep udf
udf
-
Thank you very much, will give it a try !
-
Porting my question over here - can this be evolved to bring back the DVD/BD-ROM support functionality we had with android 5 ?
Thank you !
I'm sure with little script correction. But i don't have external rom drive to check it.
General idia is include into list of discs (sd*) list of rom drives - sr* and just mount it like discs. Additionaly check that sr* has UDF fs.
~> sudo blkid | grep sr
root's password:
/dev/sr0: UUID="48CB99C400A2640E" LABEL="BERLIOZ" TYPE="udf"
Box supports udf:
~> adb shell cat /proc/filesystems | grep udf
udf
Hi frd
I'm not a coder. can you build that script become Run_me.bat ?
Thanks vm
-
I have not understanding how to solve the problem of mounting discs with the andrioid version 7
the procedure will run throughout the player or you have to use a PC.
how do I communicate HIMEDIA q5 Pro with a PC and use the command prompt ???
-
I have not understanding how to solve the problem of mounting discs with the andrioid version 7
the procedure will run throughout the player or you have to use a PC.
how do I communicate HIMEDIA q5 Pro with a PC and use the command prompt ???
Both the Q5 Pro and a Windows PC need to be on the same network.
You access Command Prompt on the Windows PC, navigate to the directory where the script is located and type 'RUN_ME'.
The script will ask you to input the IP address of the Q5 Pro. You can find this by, on Q5 Pro, going Home - Settings. IP address is shown with the Network icon.
-
Update:
v1.0.5
- bug fixed
- add /sdcard/media_rw/cd-rom/srXX
- full support Android 5.1.1 and HMD 2.0.0 Android 7.0 f/w
(not more updates, upcoming HMD 2.0.1 f/w will not supported)
v1.0.4
- add DVD/BD-ROM support
- add RUN_ME.bat option not mount/sdcard/media_rw/disk-by-uuid/<uuid>
v1.0.3
Big THANKS to qqq1971
- rewrite scripts to support safe hotplug
Download:
http://www.mediafire.com/?0u9h678yy61c7h1
Note: Clean Task can remove all apk from USB device.
-
Excelente! Opening post updated with latest version.
-
Update:
v1.0.4
- add DVD/BD-ROM support
- add RUN_ME.bat option not mount/sdcard/media_rw/disk-by-uuid/<uuid>
v1.0.3
Big THANKS to qqq1971
- rewrite scripts to support safe hotplug
Download:
http://www.mediafire.com/?0u9h678yy61c7h1
Note: Clean Task can remove all apk from USB device.
great, many thanks bro.
-
Update:
v1.0.4
- add DVD/BD-ROM support
- add RUN_ME.bat option not mount/sdcard/media_rw/disk-by-uuid/<uuid>
v1.0.3
Big THANKS to qqq1971
- rewrite scripts to support safe hotplug
Download:
http://www.mediafire.com/?0u9h678yy61c7h1
Note: Clean Task can remove all apk from USB device.
Much appreciated ! you are the best !
-
Excelente! Opening post updated with latest version.
I had test, it work perfect. Now Q10 pro can read Bluray disk over usb port.
Thks all frd.
-
I have not understanding how to solve the problem of mounting discs with the andrioid version 7
the procedure will run throughout the player or you have to use a PC.
how do I communicate HIMEDIA q5 Pro with a PC and use the command prompt ???
Both the Q5 Pro and a Windows PC need to be on the same network.
You access Command Prompt on the Windows PC, navigate to the directory where the script is located and type 'RUN_ME'.
The script will ask you to input the IP address of the Q5 Pro. You can find this by, on Q5 Pro, going Home - Settings. IP address is shown with the Network icon.
I am very angry . I do not have windows pc
but apple mac pc ...... and also the procedure is the same hard for me.
how can I do???? in the next firmware you can perhaps that the discs are read without making the process RUN_ME.bat ????
-
Next official Android 7.0 f/w will support at least UUID mount point --> /mnt/media_rw/<uuid>.
LE: Installing ADB on MAC OS X
http://stackoverflow.com/questions/31374085/installing-adb-on-mac-os-x
source (http://forum.zidoo.tv/index.php?posts/17448)
I am very angry . I do not have windows pc
but apple mac pc ...... and also the procedure is the same hard for me.
how can I do???? in the next firmware you can perhaps that the discs are read without making the process RUN_ME.bat ????
-
Next official Android 7.0 f/w will support at least UUID mount point --> /mnt/media_rw/<uuid>.
I am very angry . I do not have windows pc
but apple mac pc ...... and also the procedure is the same hard for me.
how can I do???? in the next firmware you can perhaps that the discs are read without making the process RUN_ME.bat ????
thank you
-
Next official Android 7.0 f/w will support at least UUID mount point --> /mnt/media_rw/<uuid>.
I am very angry . I do not have windows pc
but apple mac pc ...... and also the procedure is the same hard for me.
how can I do???? in the next firmware you can perhaps that the discs are read without making the process RUN_ME.bat ????
I saw 1.0.5 final ver, but how to create icon/ shortcut of cd/dvd/blr to home screen ?
-
Hello.
With Mount_in_fix_point_and_sdcard_media_rw_1.0.4.1.rar i can see my HDD on Sata on the q10 dlna server with my TV Lg Smartshare . But i can not fast forward or backwards thru the video files, the Tv says "Unsuported function in this file"
With Mount_in_fix_point_and_sdcard_media_rw_1.0.5.rar i can not see my HDD on Sata on the q10 dlna server.
My q10 pro has android version 5.1.1 kernel versoin 3.18.24 build number HMD-1.0.8 2016-10-12.193826
Is there a way to make it work , to fast forward or backwards inside the movie file , or should i wait for a next release or upcoming HMD 2.0.1 f/w ?
-
I can not eject my DVD disk driver when I use q10pro
-
v1.0.6
- bug fix support Android 5.1.1
- preliminary support HMD 2.0.1 Android 7.0 f/w
- fix missing ext2, ext3, ext4 partition Android 5.1.1 / 7.0 f/w
Thanks @HUHA for reporting problem.
-
Before Android 7, I was going inside the File Explorer and the optical drive would show over there (whenever a disk was inside)
I can see the drive is being recognized when I boot my Q5 (same noises as before), but I cannot find it as before.
Please, any thoughts ?
-
Using the patch DVD/BD drives should show at /sdcard/media_rw/cd-rom/
-
Using the patch DVD/BD drives should show at /sdcard/media_rw/cd-rom/
Thanks, let me try to find it.
-
Installed the script. Works partionally for Label in combination with the Internal SATA HDD which shows up as empty. With UUID it works normally. For USB it works with some HDD only.
All HDD where Label does not work are physically accessed continually. Uninstalling the script stopped that undesired disk access.
-
What I am still missing is the translation to Media Center. I really expected the Labels or UUID to replace the pseudo random USBxxx identifications present there now also. Giving meaningful VL's per drive is feasible with 32 positions.
To answer a question Windows stores Volume Labels standard as UTF-16 (not UTF-8 as often presumed) allowing any value including spaces and 32 positions. Looked it up 8)
-
What I am still missing is the translation to Media Center. I really expected the Labels or UUID to replace the pseudo random USBxxx identifications present there now also. Giving meaningful VL's per drive is feasible with 32 positions.
To answer a question Windows stores Volume Labels standard as UTF-16 (not UTF-8 as often presumed) allowing any value including spaces and 32 positions. Looked it up 8)
This will need HiMedia to update Media Center app, which I am sure they'll do when labels/UUID are implemented in next firmware.
-
It works well on Android 5?
-
It works well on Android 5?
Yes. See changelog in OP.
-
Does it work with a usb 3.0 hub connected to the q10 usb 3.0 port and a couple of usb hard disks connected to the hub?
Thanks a lot.
Giacomo
-
Does it work with a usb 3.0 hub connected to the q10 usb 3.0 port and a couple of usb hard disks connected to the hub?
Thanks a lot.
Giacomo
yes it does. Using with 4 units on a single USB3 port.
-
Hello, I still have a problem after running the patch ( I chose standard installation)
My Q10 pro has firmware 1.0.8 2016-10-12.193826 . It has an external usb 3 hard disk (3TB) and an internal sata hard disk 4 TB. Both work correctly and I can access them both with the file explorer and as samba windows share with my windows pc as well.
After the install if I select the disk by uuid folder I see them both and I also see their content, while if I select the disk-by-label I see both labels (volume for the usb one and store4tb for the internal) but the internal hard disk is seen as empty (no folders and no files are displayed).
Thank you very much.
Best regards
Giacomo
-
Hello
disk-by-label --> Need to be on ASCII 437, and all label unique.
If you still not get working send me on private message (http://www.futeko.com/newforum/index.php?action=pm;sa=send;u=72) blkid result.
adb connect <ip player>
adb shell blkid
Hello, I still have a problem after running the patch ( I chose standard installation)
My Q10 pro has firmware 1.0.8 2016-10-12.193826 . It has an external usb 3 hard disk (3TB) and an internal sata hard disk 4 TB. Both work correctly and I can access them both with the file explorer and as samba windows share with my windows pc as well.
After the install if I select the disk by uuid folder I see them both and I also see their content, while if I select the disk-by-label I see both labels (volume for the usb one and store4tb for the internal) but the internal hard disk is seen as empty (no folders and no files are displayed).
Thank you very much.
Best regards
Giacomo
-
Hello, the hard drive is still seen as empty if I browse it by label. I sent you, as you asked me, the result of the blkid adb shell command.
Should I, although the labels are ASCII 437 and unique change the current internal hard disk label (Store4TB). If I do it I should run again the path right?
Thank you very much.
Regards
Giacomo
-
in the new firmware 1.0.9 for Android 5.1, the storage mount patch by UUID / label
It has been inserted ?
-
in the new firmware 1.0.9 for Android 5.1, the storage mount patch by UUID / label
It has been inserted ?
I am pretty sure that this patch is not included in any official firmware.
-
It's not in any firmware yet.
The 2.0.1 beta has an early version of it, but the patch is better. We wait to see what 2.0.1 official will bring.
-
I have 8 HDDs storage attached to the player Himedia Q5 pro with Android 5.1. it work well and open all 8 disk everytime, sometimes loses cover films only.
I want to pass to android 7.
about the patch what means "Only first 4 mounted disks will be linked" ?
......that can be attached only 4 hard disks ,in all ? or 4 hard disk for each host usb port ?
my problem is that I passed to Android 7 and every boot, the 8 hard-disk are not read all . sometimes it opened only 2 , another only 3
So, I have applied the patch but not solve the problem for me.
I tried to mount the all 8 disk using the folder " disk-by UUID" and another time by " disk by label " , but at every boot it not opens the 8 disk all, and always lose the cover and films informations .
I went back to Android 5.1.with much regret, but at least so it opens all disks.
-
I have 8 HDDs storage attached to the player Himedia Q5 pro with Android 5.1. it work well and open all 8 disk everytime, sometimes loses cover films only.
I want to pass to android 7.
about the patch what means "Only first 4 mounted disks will be linked" ?
......that can be attached only 4 hard disks ,in all ? or 4 hard disk for each host usb port ?
my problem is that I passed to Android 7 and every boot, the 8 hard-disk are not read all . sometimes it opened only 2 , another only 3
So, I have applied the patch but not solve the problem for me.
I tried to mount the all 8 disk using the folder " disk-by UUID" and another time by " disk by label " , but at every boot it not opens the 8 disk all, and always lose the cover and films informations .
I went back to Android 5.1.with much regret, but at least so it opens all disks.
At the moment with Android 7 + patch the limit is 4 attached drives.
I expect there to be no limit with the official solution in firmware 2.0.1.
-
please help im a newby im getting really frustrated with drives moving positions ive downloaded the patch and follow instructions but im still having problems I don't know if the patch is not working or im doing something wrong I would love a more detailed guide im sorry guys I love this box apart from this issue please help me ive got a 6tb sata drive and a 2tb usb drive and 256gb usb dongle (to copy files). And on my pc through network calling my 6tb sata sda 2 its calling my 2tb usb drive sda1 also calling my 256gb dongle sda1 I think that's the problem im not sure any help would be much appreciated
-
please help im a newby im getting really frustrated with drives moving positions ive downloaded the patch and follow instructions but im still having problems I don't know if the patch is not working or im doing something wrong I would love a more detailed guide im sorry guys I love this box apart from this issue please help me ive got a 6tb sata drive and a 2tb usb drive and 256gb usb dongle (to copy files). And on my pc through network calling my 6tb sata sda 2 its calling my 2tb usb drive sda1 also calling my 256gb dongle sda1 I think that's the problem im not sure any help would be much appreciated
This patch doesn't change drive name for Samba server (as you see them through PC), only for drives when seen from Q5/Q10 Pro apps.
-
I replaced my HDD in my Q10 Pro with a bigger one.
Its path used to be /mnt/media_rw/sda1
Powered down, put the new HDD in, powered up...
...the path is now /mnt/media_rw/sda2
Why? ???
This screws up all my database files i have with KODI.
How can i change it back to sd1?
-
I replaced my HDD in my Q10 Pro with a bigger one.
Its path used to be /mnt/media_rw/sda1
Powered down, put the new HDD in, powered up...
...the path is now /mnt/media_rw/sda2
Why? ???
This screws up all my database files i have with KODI.
How can i change it back to sd1?
You can't change it manually. That is the problem that this patch addresses. I suggest installing this patch and changing your Kodi database so it points to the drive mounted according to label.
-
I replaced my HDD in my Q10 Pro with a bigger one.
Its path used to be /mnt/media_rw/sda1
Powered down, put the new HDD in, powered up...
...the path is now /mnt/media_rw/sda2
Why? ???
This screws up all my database files i have with KODI.
How can i change it back to sd1?
If you have an SD card, a USB stick inserted then the HDD would probably be seen as sdb1. I use 2 HDDs, an internal one and an external one. I feared that they would probably switch the order they are being detected, but I had zero issues on any firmware (but I only have one partition on any HDD). Unplug everything and make sure you only have the internal HDD connected. Connect anything after it boots. Or you can use this patch to have it mounted in the same folder everytime.
-
I replaced my HDD in my Q10 Pro with a bigger one.
Its path used to be /mnt/media_rw/sda1
Powered down, put the new HDD in, powered up...
...the path is now /mnt/media_rw/sda2
Why? ???
This screws up all my database files i have with KODI.
How can i change it back to sd1?
You can't change it manually. That is the problem that this patch addresses. I suggest installing this patch and changing your Kodi database so it points to the drive mounted according to label.
So i have to install this patch every time i update the firmware from now on?
I'd rather leave it as sd2, if that doesn't change again.
@tmihai20:
The internal HDD is all i have connected.
-
I replaced my HDD in my Q10 Pro with a bigger one.
Its path used to be /mnt/media_rw/sda1
Powered down, put the new HDD in, powered up...
...the path is now /mnt/media_rw/sda2
Why? ???
This screws up all my database files i have with KODI.
How can i change it back to sd1?
You can't change it manually. That is the problem that this patch addresses. I suggest installing this patch and changing your Kodi database so it points to the drive mounted according to label.
So i have to install this patch every time i update the firmware from now on?
I'd rather leave it as sd2, if that doesn't change again.
@tmihai20:
The internal HDD is all i have connected.
Yes, you have to install the patch every time you flash a new release. Does it have several partitions? It is strange that it is seen as sda2 right now.
-
Yes, you have to install the patch every time you flash a new release. Does it have several partitions? It is strange that it is seen as sda2 right now.
Storage mounted by UUID was a part of a 2.0.1 private beta firmware that never made it into 2.0.1 final.
Hopefully HiMedia will add it to future firmware so the patch doesn't have to be reinstalled.
-
@tmihai20:
It's only one partition.
Took old hdd out of Q10 Pro, formatted new hdd in my pc, then booted up Q10 Pro with new hdd inside -> sda2.
I don't get it either, there must be some "file remains" of the old hdd somewhere ???
@futeko.com:
That would be preferable indeed.
Right now there are too many manual patches created by users that could easily just be implemented.
-
Too many manual patches created by users --> Ooo nobody force to use it :(
Check via samba share if only /mnt/media_rw/sda1/Android/data/com.google.android.youtube is there and if yes just remove sda1.
@tmihai20:
It's only one partition.
Took old hdd out of Q10 Pro, formatted new hdd in my pc, then booted up Q10 Pro with new hdd inside -> sda2.
I don't get it either, there must be some "file remains" of the old hdd somewhere ???
@futeko.com:
That would be preferable indeed.
Right now there are too many manual patches created by users that could easily just be implemented.
-
sda2 is the only folder in \\ANDROID_NUMBERSANDSTUFF\share\media_rw.
-
@DancesWithChickens: put in a PC and check if there is another hidden partition. I use dedicated software, not any of the Windows tools as they are known to do things their own way. If you created the partition yourself, then you did something wrong.
-
It worked, but I lost my bigger data. I installed via option 1 and it did not work. Then I installed it via option 2 directly (no uninstall). I can now read my HDD via the media player and via my network. All folders are intact, but my movies and Serie episodes are all gone. An srt file is the only file left on the hdd.
Are my files deleted or can't it be read by my network / media player? Before installing this patch I had no problem with the large files. I could browse through it and open them.
Running android 7 rooted with the newest custom futeko firmware.
-
Using the patch DVD/BD drives should show at /sdcard/media_rw/cd-rom/
I install it and play BD/DVD movie well but can't play data file like mp3, flac recorded on BD-ROM on FW 2.01 but it can play well on FW 1.09, Please advise
-
Probably know Android 7 permission problems, let'a see what will come on new f/w.
Using the patch DVD/BD drives should show at /sdcard/media_rw/cd-rom/
I install it and play BD/DVD movie well but can't play data file like mp3, flac recorded on BD-ROM on FW 2.01 but it can play well on FW 1.09, Please advise
-
First, I wish to thank the creators for this solution.
My HDD also has a hidden partition resulting in the actual partition being recognised as sda2. Parted revealed to me that there is a MSR partition, although I used Acronis Disc Director, no MS tool. ADD doesn't even show the MSR partition it created.
But that shouldn't be an issue, even multiple visible partitions should be mounted correctly, so I took a look at the script and observed that it tried to mount sda1 by the label of sda2, which gave an error, but the already created folder prevented it from mounting sda2 afterwards. Furthermore, it didn't handle labels with blanks correctly because of some path variables without quotes.
So I altered the part that uses ls to retrieve the devices. Now it uses blkid for that, so only partitions with a valid file system are even considered for mounting. I tested it with the internal HDD and some USB sticks, works perfectly for me so far. If anyone is interested, I'm going to attach it, but without any kind of warranty, and hopefully the creators won't be annoyed by me for messing up their work ;)
[attachment deleted by admin]
-
@derkallevombau
Very few people share they improvement, your version is online as v1.0.7.
Thanks.
v1.0.7
- improve / bug fix thanks @derkallevombau
People are welcome to improve and share they modification.
-
You are welcome! I appreciate your work on patches that I can benefit from, so it's a pleasure for me to give something back.
-
Hi,
I have a q10 pro and installed a 1tb HDD.. I have patched my android 7 system with futeko firmware so it can also be seen on upnp server.
It happened to me twice now that ALL my large files (movies & serie episodes) are deleted from the hard disk. The folders and srt files are still intact.
I watch the files using kodi. I went to my HDD using Asus file Manager. And I can really see the files getting deleted while I am doing nothing strange.
Can anyone tell me what is going on and how to prevent? ? I'm getting tired if downloading everything time by time again.
Tha ms!
-
What exactly have you done immediately before you saw your files being deleted?
-
It didn't work for me. I have Android 5. Downloaded the patch. Ran it with option 1 Install Standard. Himedia reboot and then nothing changed. I don't see any new mounts.
Any advice?
-
/mnt/disk-by-label and /mnt/disk-by-uuid this are path you check? Not one create it?
Your USB device are visible on MediaCenter?
It didn't work for me. I have Android 5. Downloaded the patch. Ran it with option 1 Install Standard. Himedia reboot and then nothing changed. I don't see any new mounts.
Any advice?
-
/mnt/disk-by-label and /mnt/disk-by-uuid this are path you check? Not one create it?
Your USB device are visible on MediaCenter?
It didn't work for me. I have Android 5. Downloaded the patch. Ran it with option 1 Install Standard. Himedia reboot and then nothing changed. I don't see any new mounts.
Any advice?
My SATA and USB drives are still visible but under /mnt/sda and /mnt/sdb like before. I don't see anything new. There's no /mnt/disk-by-label when I use File Manager or any other apps.
-
Hi to all,
Sorry, but I don't understand which one I have to choose ....Labels or uuid...I' m having 2 USB Hubs ( because as mentioned only max. 4 HDDs per USB Hub on Q10pro pro....One=With 4 external HDD..Two= With 3 external HDD... Each HUB in the Q10 pro
...Do i have to choose Label or uuid...whats the Difference ??
Regards
-
/mnt/disk-by-label and /mnt/disk-by-uuid this are path you check? Not one create it?
Your USB device are visible on MediaCenter?
It didn't work for me. I have Android 5. Downloaded the patch. Ran it with option 1 Install Standard. Himedia reboot and then nothing changed. I don't see any new mounts.
Any advice?
My SATA and USB drives are still visible but under /mnt/sda and /mnt/sdb like before. I don't see anything new. There's no /mnt/disk-by-label when I use File Manager or any other apps.
Hello. Could anyone give me some advice how to solve this?
All I want is consistent mount points after reboot.
-
Hello. Could anyone give me some advice how to solve this?
All I want is consistent mount points after reboot.
@ pcristi: Tried to use this script for my Egreat A10 but it did not do anything. Loved to see Volume Labels on that one.
You may PM me if you like me to do some testing.
-
For me Mount_in_fix_point_and_sdcard_media_rw_1.0.7 working with HiMedia Q10/Q5Pro and Egreat A10/A5
From EgreatA10
EgreatA10 --> WD 3TB HDD GPT/NTFS
X9S_F --> 8GB FAT32--> 8GB FAT32 USB flash
X9S_N --> 8GB NTFS --> 8GB NTFS USB flash
(http://www.mediafire.com/convkey/d27c/gfiy0mpc8yd4cl7zg.jpg?size_id=5)
(http://www.mediafire.com/convkey/91e1/534oy4xjdhzpqc3zg.jpg?size_id=5)
Please note this will not make application like ES Explorer/Kodi 16.1/etc to use Volume Labels/UUID
(http://www.mediafire.com/convkey/29d4/jwfos5m604k3c25zg.jpg?size_id=4)
-
For me Mount_in_fix_point_and_sdcard_media_rw_1.0.7 working with HiMedia Q10/Q5Pro and Egreat A10/A5
From EgreatA10
EgreatA10 --> WD 3TB HDD GPT/NTFS
X9S_F --> 8GB FAT32--> 8GB FAT32 USB flash
X9S_N --> 8GB NTFS --> 8GB NTFS USB flash
(http://www.mediafire.com/convkey/d27c/gfiy0mpc8yd4cl7zg.jpg?size_id=5)
(http://www.mediafire.com/convkey/91e1/534oy4xjdhzpqc3zg.jpg?size_id=5)
Please note this will not make application like ES Explorer/Kodi 16.1/etc to use Volume Labels/UUID
(http://www.mediafire.com/convkey/29d4/jwfos5m604k3c25zg.jpg?size_id=4)
i have both egreat A5 and himedia Q5pro (with android 5.1 and firmware1.1.0) , but the new patch 1.07 not work for me and not see the disks under mnt/media_rw/disk-by-uuid/<uuid> or label, while it is working perfect the version 1.06.
p.cristi it's possible to test again this version 1.0.7. thank you
-
Android 5.1.1 is /mnt/disk-by-uuid/<uuid>
Android 7 is /mnt/media_rw/disk-by-uuid/<uuid>
Old ver: https://www.mediafire.com/?5op0fk4mj8874
-
Android 5.1.1 is /mnt/disk-by-uuid/<uuid>
Android 7 is /mnt/media_rw/disk-by-uuid/<uuid>
Old ver: https://www.mediafire.com/?5op0fk4mj8874
Maybe my expectation is wrong or just don't get it what to do, but does not work for me.
First what i expect with only an Internal HDD with VL "A10 DVDs" in A10:
- When connecting from my PC with Samba to see under: /Share/ "A10 DVDs" and not /share/sda/sda2
- When using the standard browser (=files with a10) not HDD1 but "A10 DVDs"
Maybe that is already a wrong assumption but this is what Realtek RTD1295DD based players all do.
What i do:
- Unpack the "Mount_in_fix_point_and_sdcard_media_rw_1.0.7.rar" to my PC
- Run the batch and make a connection.
- Select option 2, wait it to reboot.
Look via Samba or the standard browser/poster system for a drive (hopefully indicated with the Volume label now)
-
/Share/ "A10 DVDs" and not /share/sda/sda2 --> this mange by vold, I don't have knowledge how to patch it.
To get little bit closer to your idea open fix_mount.sh with notepad++ and replace /disk-by-label with empty string for 10 time and RUN_ME.bat with option 1 again.
After reboot will be like that.
(http://www.mediafire.com/convkey/22b7/mkt1qc8aa2uxj6jzg.jpg?size_id=4)
Realtek RTD1295DD use UUID for mount, and Zidoo Explorer/ZDMC(fork of SPMC)/Home Theater/etc apps converter to Volume label.
Normal Android Explorer like Es Explorer/Solid Explorer show UUID on my Zidoo X9s.
Samba Server still use sda/sdb/etc and share as Disk_sda1/Disk_sdb1/etc because is power by openWRT, of course can use own samba template to get need things.
if HiMedia/Egreat want to change to Volume label they application like MediaCenter/EgreatTV can do by itself or wait HiSilicon to do they job and provide a binar(source) vold working proper on SDK with UUID.
That scope of this script is only to make easy life for Kodi 16.1 user and HiSilicon DLNA users providing fix source for library.
-
Android 5.1.1 is /mnt/disk-by-uuid/<uuid>
Android 7 is /mnt/media_rw/disk-by-uuid/<uuid>
Old ver: https://www.mediafire.com/?5op0fk4mj8874
thank you pcristi
-
pcristi
can you make a patch for egreat A5 , 1.1.1.9 firmware because the existing patches do not work
-
Hi,
I have a q10 pro and installed a 1tb HDD.. I have patched my android 7 system with futeko firmware so it can also be seen on upnp server.
It happened to me twice now that ALL my large files (movies & serie episodes) are deleted from the hard disk. The folders and srt files are still intact.
I watch the files using kodi. I went to my HDD using Asus file Manager. And I can really see the files getting deleted while I am doing nothing strange.
Can anyone tell me what is going on and how to prevent? ? I'm getting tired if downloading everything time by time again.
Tha ms!
I just experienced the same, it is Asus File Manager that deletes the files! I opened it for the first time after installing the patch, it showed a message on improvements in a new version while I could hear the HDD working, and the message couldn't be closed for several seconds. After that, several folders and subfolders were empty, while the folders itself were still there. Immediately before opening Asus File Manager, I had played some files in these folders to ensure that they had been transferred properly.
So steer clear of Asus File Manager when using this patch! Anyway, would be interesting to know what causes the app to act like this...
-
Just tested v1.0.7 of the patch (1st install option, i. e. only mountpoints in /mnt/media_rw) on my Q10 Pro with the new FW v2.0.3, works flawlessly, in case someone is unsure.
-
I tested patch v1.07, install option 2 on FW2.03 Q10 PRO. It doesn't work but it work well the same on FW 2.01. However, FW2.01 only play Bluray and DVD but can't read data like mp3 (show file but it can't play
-
pcristi
can you make a patch for egreat A5 , 1.1.1.9 firmware because the existing patches do not work
accurate, does not work >:(
-
I didn't read the whole thread but why this patch is not included in latest firmwares?
I reverted back to latest 5.1.1 because 7 was too buggy. Added a USB drive and now Kodi can't find anything. Really really annoying.
-
Where do I download v1.0.7 ? and what are these improvements?
Mount_in_fix_point_and_sdcard_media_rw_1.0.7.rar
-
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.
-
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
-
do you work in xbmc of egreat A5 ???
-
do you work in xbmc of egreat A5 ???
User reported working on Egreat A5 for v1.0.6 (https://www.mediafire.com/?h8jy6u8fi1vtf).
http://en.egreatworld.com/comunity/index.php?threads/sloved-hard-disk-start-order-in-vidon-xbmc.588/#post-2174
-
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.
-
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.
-
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
-
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.
-
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 !!
-
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?
-
@Kubrick23
RUN_ME.bat need open on Windows PC not from RootBrowser on Android.
-
Is this patch also working for OFW? Thank you
-
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 ?
-
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.
-
Thanks for the reply
Yes android 7 and Himedia Q10 PRO.
I also tried version 1.0.7 but with the same result.
I'll try some previous firmware version
-
How do I remove the patch?
-
To state the obvious, run the program and select uninstall.
-
To state the obvious, run the program and select uninstall.
Thanks.
-
My internal Seagate EXOS 12TB shows under FileManager as SATA E but it didn't mount under ES File Explorer. However it is showing under /mtn/media_rw/sdb1? But my USB thumbstick mount as sda1. Any advice.
-
Afraid not. Without the patch, storage device mounting by Android is haphazard unless you connect or turn on the devices in turn.
-
Afraid not. Without the patch, storage device mounting by Android is haphazard unless you connect or turn on the devices in turn.
With or without patch, my Seagate EXOS 12TB is not mount.
-
@pcristi
If the drive is not auto mount by Android, how do I fix it? Any advice? Thanks in advance.
-
If it is showing as sdb1 it is mounted by android. I can only suggest that ES File explorer doesn't like it for some reason. Too large maybe? If it is a new drive you may need to format it in a PC as an NTFS drive before you can use it.
-
If it is showing as sdb1 it is mounted by android. I can only suggest that ES File explorer doesn't like it for some reason. Too large maybe? If it is a new drive you may need to format it in a PC as an NTFS drive before you can use it.
It's not showing sdb1. The device is listed under /mnt/media_rw/
-
If it's listed there it has been mounted as sdb1. I have no idea why the q10 doesn't like it. I won't reply further to this thread because you have started another.
-
So, how does this work when using Linux OS (Linux Mint 19.1)?
I have a 3,5 inch SATA HDD (NTFS formatted) placed inside the Q10. At first it wouldn't show up in the box until I connected a USB 3 cable from the USB 3 slave port (on the left side of the box) to my PC running Linux.
I also have a USB 3 cable connected from the host usb 3 port at the back of the player to my PC. When I connect that however, the HDD disappears again inside the TVbox (under Media Center).
It does show up in my filemanager in Linux however (name/label is Xtreamer, as that was my old mediaplayer which also had a host usb 3 port and when connected to my PC, it would automatically be detected.) when I press on it under Devices in my Linux Filemanager it won't mount.
If I try it through a terminal with: sudo mount /dev/sdd1 (this is what it shows when I hover over it in the filemanager), it states it cannot find it in my fstab
Thing is, in my PC I also have a 2 TB HDD as a data backup disk. When I press that in my filemanager it just gets mounted.
If I try the same in a terminal with: sudo mount /dev/sdb1 (this is what it shows when I hover over it in the filemanager), it also states it cannot find it in my fstab. Which is correct, cuz it doesn't show in my fstab, but it does get mounted when I press on it in my Filemanger under devices.
So how come that HDD gets mounted without an issue, but I can't seem to be able to mount the HDD disk that is directly hooked up through a USB 3 cable to the tvbox' host usb 3 port?
I have identified the UUID of the HDD inside the TVbox and I know it's device sdd1, so how come I am not able to mount it?
-
Does it also work with Q20 Pro?