HPH NT-V8 RK3368 Marshmallow ROM by mo123

[Shomari]

Don't know, since the manufacturer (Eny Technology, Acemax ?) has released no Marshmallow firmware for Z4 and abandoned it, no one knows the correct settings to build MM firmware for it.
You will have better compatibility using Shomari or cOOLio's firmware for Z4

... the Nagrace firmware runs perfectly fine on the Z4.

http://freaktab.com/forum/tv-player-support/rk3688-devices-aa/nagrace-rk3368/628242-hph-nt-v8-rk3368-marshmallow-rom-by-mo123?p=628424#post628424

I personally have no interest in MM, that's why I don't bother, plus it'll be more to maintain.

[Shomari]

Not one firmware except yours does not have a sound fix in the YouTube. Thank you!

I thought you didn't even have a Z4. Isn't your device different?

The only devices with sound issues (described as stuttering) are R68/i68 devices primarily sold in Eastern Europe. Seven months of threads I haven't seen any audio issues reported except those devices. Not a single report of it occurring with any Z4. Or Ugoos/Nagrace, either.

So I'm not sure a 'Z4 kernel' even if mo123 decides to make it for you, will have anything to do with a 'fix'.

And you said months ago that the audio issues you guys have with your set of devices was 'fixed'.

Told you it wasn't.

I made a thread specifically to find a fix for your devices, despite not even owning it. Very few users wth the actual device even bothered to participate. Yet here you are begging for a shot in the dark. (that's not even related to the Z4, that you keep mentioning, let alone Nagrace).

And remember, while you said the sound was by luck fixed on your device with mo's 1.1, a whole bunch of users on 4PDA said it wasn't.

[Jura46]

I'm not asking you.

[Andro_James]

Dear Shomari,

Please accept my apologies for the previous post, I believe this guy didn’t mean any offense. I’m an R68 user and can confirm that audio issues were really fixed in mo123 firmware, both L and MM based. Also, I can’t agree that R68/i68 are the only devices with sound stutter. I know that for example, CSA90 and CSA91 users faced the same problems. I think that that was also an issue even for Nagrace because otherwise mo123 wouldn’t have fixed it. He mentioned in his changelog “fixed stuttering” so it means that the problem was there until he fixed it. I ordered my R68 in China so I think that the problem exists for the users from around the globe, not just Eastern Europe.


You made a thread to find a fix but unfortunately closed it in a few days. I believe not all users are technically savvy enough to run tests and send you the logs. Also, as you know, many users buy these devices for their kids, just like me and it is sometimes very difficult to make them stop watching cartoons for several hours while I’m running the tests. Another reason is just being busy almost all the time, work, etc. I would have definitely liked to take part in testing, but had no possibility to send the results immediately. But I still think that if we could get your firmware with fixed stuttering, that would be really great. But for now I’m happy with 1.3 MM firmware which works perfect on my R68 except for the IR remote and I’m ok with that.


As for the 4pda users, many of them are just newbies and got lost in various firmwares, others can’t set it up to work with their WIFI module and thus give it up, etc. As for me I reported several times on that forum, that the sound issues are fixed and many other users confirmed that. Actually, I was the first who pointed to mo123 firmware for Russian speaking community and suggested everyone to install it as the best option among many other roms available.

[Shomari]

Andro_James the audio thread was open and is still open, though. And you're right, I remember jura himself begging me in my dm's for assistance with the stuttering on csa91 and other things. How quickly people turn; btw that post is nothing, if you're on 4PDA then you've probably seen the things they've said over there, without provocation. It's something else, really.

And there was never a 'fix' identified per se, let alone a targeted solution based on specific component/device logs.

As I said then, if a fix was true and actual, it would carry from version to version. It did not, as it didn't ever really exist.

What occurred was a happenstance result of certain users having certain devices reporting better audio with a specific version. I said then that it appeared to be mere luck, and not appropriately identified and thus not likely to stick or carry over to subsequent versions.

That's exactly what's happened. Later versions have the 'audio stutter'; an actual fix would mean the issue doesn't persist. Fixes are robust, they don't come and go. Jura himself said the problem came back, as did others.

Bottom line, my effort was always to be part of the solution, that's why I made the thread to look for a solution despite never once experiencing the audio stutter until I artificially induced it after a user at 4PDA sent me a video clip for me to see what it's like, since it's difficult to describe it otherwise.

As to work and being busy, I'm just the same as everyone else. I put my time into this to help users (that audio fix thread is just one example) with things that have nothing to do with my devices at all. Purely 100% volunteer. Sometimes a desirable outcome requires user participation, I don't think that's too much to ask at all.

[Andro_James]

Again, please accept my apologies for those guys, I’m more than sure that many people are grateful to you for your work and willingness to help. Now understand your point, if we are talking about a fix that could be carried from version to version, then, yes, such a solution has never been found. However, I’m still sure that it was not just a happenstance but a real fix implemented somewhere deeply in the firmware so that no one can still identify it and retrieve for the use on other versions. The reason why the problem came back is very simple: some users don’t understand that mo123 firmware has a bit different structure and thus can’t be used with other kernel/resource extracted from other roms. So they just installed their kernel and resources on top of mo’s firmware and the issue came back. They did it in an attempt to make their wifi and ir remote work but couldn’t understand that that was the main reason for resumed stuttering.

Again thank you so much for all your efforts and readiness to spend your personal time. I just wanted to say that if people can’t respond fast, it doesn’t mean that they are not interested. I believe that the issue with r68 is somewhere in video cache which was eliminated by some dev tweaks. For example, in one of the latest changelogs Mo123 mentioned that he fixed audio issues with higher disk usage. I’m pretty sure that he knows what's going on and how it needs to be rectified.

[bangprovn]

Again, please accept my apologies for those guys, I’m more than sure that many people are grateful to you for your work and willingness to help. Now understand your point, if we are talking about a fix that could be carried from version to version, then, yes, such a solution has never been found. However, I’m still sure that it was not just a happenstance but a real fix implemented somewhere deeply in the firmware so that no one can still identify it and retrieve for the use on other versions. The reason why the problem came back is very simple: some users don’t understand that mo123 firmware has a bit different structure and thus can’t be used with other kernel/resource extracted from other roms. So they just installed their kernel and resources on top of mo’s firmware and the issue came back. They did it in an attempt to make their wifi and ir remote work but couldn’t understand that that was the main reason for resumed stuttering.

Again thank you so much for all your efforts and readiness to spend your personal time. I just wanted to say that if people can’t respond fast, it doesn’t mean that they are not interested. I believe that the issue with r68 is somewhere in video cache which was eliminated by some dev tweaks. For example, in one of the latest changelogs Mo123 mentioned that he fixed audio issues with higher disk usage. I’m pretty sure that he knows what's going on and how it needs to be rectified.

Yes, I confirmed the audio stuttering with high disk usage is fixed in his kernel. I've tried his kernel on my box and it worked just fine, the problem is that the hardware on my box is not running properly with his kernel. I've pmed mo123 for this fix but he doesn't answer me yet. Hopefully this fix will release and I can fix this on my box

[Shomari]

bangprovn you still haven't said what device you have. I don't think mo123 has a fix and he's keeping it secret. I think, as I've been trying to explain, that if it's kernel related - which is as of yet undetermined - it's a fix for some devices but kind of by luck. That happens. I especially consider this to be the case as his fixes , as always, are for Nagrace devices, specifically. That the devices suffering from audio stutter other than Nagrace ended up fixed seems purely coincidental.

Remember, I don't have that issue, or the other related symptom of dropouts as seen with Wasser firmware. Only a subset of devices have this problem, based on that I guess you have a I68/R68, or to a lesser degree possibly a csa91... yes?

[Shomari]

Andro_James I'm not so sure mo123 has the 'fix' and is keeping it proprietary (or secret) to prevent its use. If it's kernel related, that doesn't need to be done, as the kernel sources are not public and thus any related methods are already obfuscated in the binaries.

As I've said before, I'm neither promoting or discouraging the decompilation of the Nagrace firmware, but it's trivial to take the Nagrace kernels with the supposed fix and use them with my or any other firmware.

Any dtb (resource image) from my firmware, with the exception of the ones in archives specifically marked 'Z4', can be used with mo123's kernels.

Jura already did that and posted it on 4PDA, it's trivial to do so.

It's undetermined whether the 'fix' is in the kernel or in some shared object. We've all seen the audio thread, I was the top poster, still am, and I don't even have the devices that are affected, and mine has never been affected. I never required immediate responses, simply responses. Users made the choice to decline to participate.

It's not unique to my threads. I've seen requests from mo123 for tests go completely without response on several occasions. It's an unfortunate thing that hinders progression.

[bangprovn]

bangprovn you still haven't said what device you have. I don't think mo123 has a fix and he's keeping it secret. I think, as I've been trying to explain, that if it's kernel related - which is as of yet undetermined - it's a fix for some devices but kind of by luck. That happens. I especially consider this to be the case as his fixes , as always, are for Nagrace devices, specifically. That the devices suffering from audio stutter other than Nagrace ended up fixed seems purely coincidental.

Remember, I don't have that issue, or the other related symptom of dropouts as seen with Wasser firmware. Only a subset of devices have this problem, based on that I guess you have a I68/R68, or to a lesser degree possibly a csa91... yes?

Based on what I encounter, yes, it's related to disk usage. I noticed everytime I play some video while downloading something (I download to internal storage and playing video in my drive), it caused audio stutter, I've tried many things like updating the player lib but no use. And I'm very sure the fix is in kernel as when I flashed mo's kernel and reproduce the audio stutter, it's not there any more.

[Shomari]

bangprovn nice!

[mo123]

Based on what I encounter, yes, it's related to disk usage. I noticed everytime I play some video while downloading something (I download to internal storage and playing video in my drive), it caused audio stutter, I've tried many things like updating the player lib but no use. And I'm very sure the fix is in kernel as when I flashed mo's kernel and reproduce the audio stutter, it's not there any more.

To reduce stuttering, you can do this
1, Root your device
2,Install this app

https://play.google.com/store/apps/details?id=com.devasque.fmount

3,Remount Youtube's cache folder to external storage(sd-card)
Youtube's cache folder is here:
/storage/emulated/0/Android/data/com.google.android.youtube/cache/exo

For Kodi use an advancedsettings.xml file to cache to RAM instead of disk.

You can ask the manufacturer of your tv box to provide the latest SDK, firmware that may help you, since the Geekbox code is very old.

[Shomari]

You can ask the manufacturer of your tv box to provide the latest SDK, firmware that may help you, since the Geekbox code is very old.

... positively ancient.

The only sources I have of recent are from 01/17, aside from some patches.

[Sabinus]

Hello and congratulations for the good work.
I have a Beelink I68 clone (Andoer)
I have installed your Rom and works fine, even passthrough 5.1
The problem is the WiFi that doesn't work, doesn't start.
With other custom roms always worked replacing /etc/firmware/nvram_AP6335.txt with nvram_AP6330 but this time the fix didn't work.
Can you confirm the wifi chip of the HPH is AP_6335? Or is it different? Can you provide a fix or at least a hint

[segagr]

Dear sir. Your firmware is great, but on some TVs the Philips screen periodically changes to green/pink. Could you fix it?