If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I've got the subject from aliexpress. It had no sound at all in any mode. Flashed Shomari's ROM, got the sound... but any command from TV or receiver RC make the ROM freeze.
Downloaded ROM from cloudnetgo.com and I became a happy QBOX user at last. Sound works and TV RC doesn't affect the device.
FYI. Tried a few videoplayers, the only one plays x265 perfectly - MXPlayer.
Thanks a million to Shomari for a heap of useful info!
This one can get ugly before it's all over, and leaves me very disappointed I've done business with them and recommended their products. Still hoping for a good resolution to the issue but it can go any direction at this point.
What the app do you use for monitoring video info?
I've got the subject from aliexpress. It had no sound at all in any mode. Flashed Shomari's ROM, got the sound... but any command from TV or receiver RC make the ROM freeze.
Downloaded ROM from cloudnetgo.com and I became a happy QBOX user at last. Sound works and TV RC doesn't affect the device.
FYI. Tried a few videoplayers, the only one plays x265 perfectly - MXPlayer.
Thanks a million to Shomari for a heap of useful info!
Wow! I had NO idea these remotes were going to be such trouble. And, I didn't even expect most people use them except to turn the box off and on (sleep and resume rather).
I thin it's the kernel, and bad for you, the cloudnetgo kernels clock the DDR lower than all the others for some reason. These boxes are powerful enough that it doesn't make a huge difference but I kind of notice.
As there are likely subtle (and perhaps not so subtle) differences between boxes, sharing the same PCB, and to help Shomari, and readers / other users, could people making requests and reporting problems, can you please:
1. Clearly state which box they have, i.e. make and model
2. Identify which ROM they are using
3. The nature of the problem: box, connection, function or wishlist etc.
Yeah! That's it.
As for XBMC...
My Bluetimes QBOX pro cannot play some HEVC file, it stops after some time. If I move the slider further it plays again for a while. At the same time MX Player works without any freezes or lags.
About kernels: maybe it seems to me that cloudnetgo ROM is a bit laggy though Antutu shows the same 35000-36000 like it was on stock.
Yeah! That's it.
As for XBMC...
My Bluetimes QBOX pro cannot play some HEVC file, it stops after some time. If I move the slider further it plays again for a while. At the same time MX Player works without any freezes or lags.
About kernels: maybe it seems to me that cloudnetgo ROM is a bit laggy though Antutu shows the same 35000-36000 like it was on stock.
Hardware accelerated playback of HEVC in XBMC is currently only possible with the non-compliant XBMC fork I post about here in the forums in the RK3288 section.
The Cloudnetgo ROMs have the DDR clocked lower than my custom ROM and other stock ROMs. That's why it feels slower.
You should try my custom ROM and see how it works for you.
That is your whtest.sh:
#!/system/bin/sh
mount -o rw,remount -t ext3 /dev/block/mtdblock8 /system
#sleep 2
echo "*******************************"
echo "wh do begin"
echo "*******************************"
rm system/app/*.nm
And this one is cloudnetgo:
#!/system/bin/sh
mount -o rw,remount -t ext4 /dev/block/platform/ff0f0000.rksdmmc/by-name/system /system
#sleep 2
echo "*******************************"
echo "wh do begin"
echo "*******************************"
#rm system/app/*.nm
And if I unpack your system.img it writes "EXT3 found", while with cloudnetgo's file "Ext4 found".
P.S. Am I right that the most important your changes are in the build.prop?
That is your whtest.sh:
#!/system/bin/sh
mount -o rw,remount -t ext3 /dev/block/mtdblock8 /system
#sleep 2
echo "*******************************"
echo "wh do begin"
echo "*******************************"
rm system/app/*.nm
And this one is cloudnetgo:
#!/system/bin/sh
mount -o rw,remount -t ext4 /dev/block/platform/ff0f0000.rksdmmc/by-name/system /system
#sleep 2
echo "*******************************"
echo "wh do begin"
echo "*******************************"
#rm system/app/*.nm
And if I unpack your system.img it writes "EXT3 found", while with cloudnetgo's file "Ext4 found".
That is not the proper way to determine the information you are looking for.
Another way to tell what things are mounted as is open a terminal emulator and type
su
mount
It will list everything and how it is mounted.
That whtest.sh is a left over and does not even need to be there! I usually remove it from init.rc
Bob
"Pzebacz im, bo nie wiedzą, co czynią"
"Прости им, они не ведают, что творят"
"Perdona loro perché non sanno quello che fanno"
"Vergib ihnen, denn sie wissen nicht, was sie tun"
"Vergeef hen want ze weten niet wat ze doen"
"Pardonne-leur car ils ne savent pas ce qu'ils font"
"Perdónalos porque no saben que lo que hacen"
"Oprosti im, jer ne znaju što čine"
"Forgive them as they know not what they do"
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment