RK3368 04/2017 True Octacore Firmware

[brickmojoccatz]

Thanks everyone to contributing on making our RK3368 usuable again keep up the good job everyone.

[Shomari]

Guest here's a full Z4 port in two variations. One is the true octacore kind: http://ge.tt/9MIlMgj2

The second is the overclocked kind but with the power menu fix, all cores running at 1608 but with separate clusters: http://ge.tt/7GKnMgj2

You won't lose any data flashing the images in the archives provided. For each variation flash both the kernel and resource in the archive.

These files are targeted for the Z4, all your components will function correctly. Please let me know if there's any screen artifacts, someone on 4PDA once said there was screen banding on their device with the earlier (power menu fix) build. I've altered the frame buffer and uboot configurations and may need to revisit them if any additional reports of that come in.

Also please let me know the results of your Mele mic test. (I think it was you that mentioned it)

These will also work for devices with AP6330 wireless chips.

Link to full update (since I haven't updated OP it keeps getting buried)

https://mega.nz/#!bNwFDBjS!4mfrgm8C6...q2X8Wy1h2u3YC0

AP6330 support in quoted links above. Images in archive are intended for use with full firmware. You can mix and match with other firmware if you'd like, but stability and performance are not guaranteed, and I can't/won't debug issues arising from mixing and matching with other firmwares. The combinations would be endless, and the issues and environments too difficult to reproduce. It's time intensive enough to debug issues within my own very familiar builds at times. I'm sure you understand..

Just now updated the power menu fix archive in quoted text to further optimize the vcore. I tested with the stock power supply, and it actually didn't shut down, and it was actually pretty stable, I'm surprised.

So if you absolutely need the power menu functions for when you turn the screen on your TV box off and put it in your pocket, go ahead and refresh your box with the images linked in the quoted text.

[Shomari]

Thanks everyone to contributing on making our RK3368 usuable again keep up the good job everyone.

You have extra hardware in your device, don't you? Display clock, etc. I haven't forgotten about your box. Soon as I get a chance I'll update your files and post a link.

[gefattern]

Just chill out bro...

Hi dincis1 ,

i never was angry or in StressMode , i only wanted to say that without us

he never could do that !!! more not .

wish u a nice Easter

Greetings

gefattern

[cOOLio]

Ahhh come on gefattern. Do you wanna start a world war 3 right out of nothing? Saddle down, make yourself comfortable and have a cup of tee. That was just a joke. Silly has also the meaning of giggly, ignorant, unwise.

So I meant, why they don‘t see the potential of Shomaris work for all of us RK3368 users. Not the Ugoos users in person, all those RK3368 freaks here at Freaktab. And meaning of freaks is also meant in a positive way. Because in the end, we are all freaks, but from the dark-side of the moon. Where you can get all those shit, the others are still dreaming off.

And Ugoos has still one of the best software for these TV boxes. Rich in features, stability, etc. I would be a fool, if I would ignore that fact. And by the way, when it comes to Android and its source code. It‘s still Open Source. So there is no hiding. Saying that’s my code you are not allow to use it on your own. Everybody could use my ROM, Shomaris ROM, everybody's ROM and start using and porting it to his own needs. And I didn’t sell Ugoos excellent work as my own work. I always give credit.

Ahhh, I have to stop. That was to much Off topic. Wasted time for all of us. If not, I start to get crazy inside of the membrane. BTW don’t you know I’m loco?


OK back to topic …

I will right down some instructions on how to test Shomaris and later also my builds in easy but and efficient way. Tools, good practices and so on. So everybody could join the test. Even if they had no clue about coding and all that freaking shit, the most Android users do not care. So we can unleash the real potential of our box, all together.

So let's focus on that. Everything else is silly = giggly, ignorant, unwise.

[cOOLio]

Shomari I was wrong with the AnTuTu version. I've did my test also with 6.3.3. But I mixed up the version number. Because the 3D part is V6.1. Will edit my test results.

And BTW I found already a way to crash my build within 2 minutes. Always. With both of your OC & T8C builds. And for me it looks like it has nothing to do with the over clocking. Because it happens also when all cores are set to 1200 GHz. More to come ....

[brickmojoccatz]

Shomari Yes the display clock and remote control i know you are a man of your word, appreciate it thanks again.

[dkholm56]

I'll post something for you in a couple days as soon as I get a little time. I have some ideas.

kool. thanks much

[cOOLio]

Instructions on how to test Shomaris OC & T8C builds in a efficient way.


First of all we need some tools, everybody could get for free at the Google Play store.

But before I will start with the list. In case you already know, or have found a better comparable free app we can use for our tests. Feel free to let me know and I will update the list. THX


[ CPU Stress Test ]

• Stress CPU

As the name of this app already says. This beast will stress all cores to the limit (100% CPU load). It’s capable to run in back round. And we are still able to do things on the box, during the 100% CPU load. And BTW right now this beat crashes my ROM within 2 minutes (max).



[ CPU Temperature Measurement ]

• ????

Until now I didn’t find any tool to show the real CPU temperature. So please help to find a tool that didn’t show values like 2-3 °C / 35-37 °F, or fake values that do never match compared with checking the temperature with your hand. THX



[ CPU, GPU (3D) Performance Test ]

• AnTuTu 6.3.3
• AnTuTu 3D 6.1
• Bonsai Benchmark
• FPS Meter (To see the FPS in real game conditions. Like Fraps for PC)

Ok here in nothing much to say, These are synthetic Benchmark tools, to compare our result. It is also important to see your results. Especial to check if there is any huge range of quality hardware build for these boxes. Slower, faster or all nearly at the same speed.



[ Video Benchmark ]

• AnTuTu Video Tester 3.0

Ok this is not really needed for a OC & T8C test. But it is always good to know which audio/video codes played well on our builds. And maybe we will see also that some videos, who do not play smoothly, will play smoothly in future.




[ Kernel Tool ]

And now the most important tool for our tests. I call it The Swiss Army Knife when it comes to the Kernel and CPU and all its features and potential. Within your hands, easy to handle, as you never have been seen before!? Ha ha ha, I’m not joking. But it sounds a bit funny. Like a reseller of the app. But as I said before, all apps are for free @ Google Play store. And If you like this app and you want to use it also in future. Please be so kind and say thanks to the developer and buy this additional cheap app [ROOT] Kernel Auditor Don. This will also deactivate the advertisement within the Kernel Auditor (root) app. BTW this app will work on any rooted mobile, tablet or ATV.

• Kernel Auditor (Root)

This tool has so many features! But right now will concentrate only to its CPU features. Because there you can change the CPU Cluster min/max frequency and the Governor on the fly. And you can even disable each CPU individually. So perfect for our needs.








My own first test results

ROM: cOOLio V3.0 GSE beta1 (not released)
ResourcePack: Shamori Z4 OC & T8C V??? (latest one at this time)

This is what I have tested so far. Yesterday I watched one movie in FULL HD without any issues. Then I started to play Beach Buggy racing. I’m one of the old N64 Mario Cart Fans. So I love this Android forge. But after 30 minutes of playing, without any issue, the box restarted. The surface of the Box felt also a bit hot, but not that much. But when I tried to powered it on again. it turns off immediately. Then I pushed the power button a bit longer and it went on again. And all was fine until I found Stress CPU. I first started Stress CPU, pushed once the home button. So it keeps on stressing the CPU with 100% CPU load, while running in background. Then I started Kernel Auditor to check the CPU Information. Boom and after 2 min. it crashes again. But right I could restart the box without pressing the power button for a longer period. Then I repeated the test, but I changed the frequency of the Big CPU clusters max 1,5Ghz. Same issue. So I did the test again, and again. While I reduced each time the max value of the BIG cluster to 1.2Ghz. Then I did the same test with the T8C build. Same result. So I stopped my test. Because I saw that this crash has nothing to do with overheating. It must be something else. Maybe my beta ROM? Maybe the DDR or I/O, setting? I don’t know. The first case my ROM, could be easily cross tested, while doing the same test with Shomaris latest build. For DDR & I/O settings we need a new Resource file. Or we can change its vales on or own. But I would prefer to have only one source to test new Resource builds > Shomari.



@Shomari
One final but in my point of view important fact!
Your starting thread is totally outdated and let’s say not well structured. All new build must be searched by the users. New testers must first read so many unneeded post to find the right build for there box. And by much luck, they will download the wrong version to test. And the test results will be useless for us and this fact is frustrating for the users. Maybe it’s right now the right time, to spend some time, to clean up all those things. Giving this whole project a structure, that could be even understand by the most uninformed users. So they can easily find what they need. To test the right version for there box. And maybe a change log would be nice. Because, as more infos we all get, as more brains could start using them, to enhance the testing and so on. And I would stop posting download files in new posts. Just add them to the starting thread and post just a link in case of updates.

Just my 2 cents




Happy Eastern to all of you.

Cheerio cOOLio

[Shomari]

Shomari I was wrong with the AnTuTu version. I've did my test also with 6.3.3. But I mixed up the version number. Because the 3D part is V6.1. Will edit my test results.

And BTW I found already a way to crash my build within 2 minutes. Always. With both of your OC & T8C builds. And for me it looks like it has nothing to do with the over clocking. Because it happens also when all cores are set to 1200 GHz. More to come ....

Power supply, power supply, power supply.

Alot of this has already been covered in the seven months I've been doing public releases. The changes in my dtb and boot, if you're using that, too, are much more comprehensive than just cpu. Additionally, as explained before, changes in boot have code dependencies with dtb, kernel, and system. Your firmware is not a proper port in that sense because it uses major elements of ugoos firmware. It's important to understand this will create unknown and possibly undesirable results.

Intentional crashes should only be done in a debugging environment (with debugging tools, logs, etc.) Crashing for the sake of crashing is fruitless. You should have logs, carefully monitor your components and determine what is the cause and adjust for a fix.

When I first started the cpu hack project, I had nasty segfaults almost instantly, resulting in crashed programs, hung systems, and beyond that some kernel panics. I covered all that.

And - power supply, power supply, power supply. If you want surefire stability as far as abrupt shutdowns go, change from the stock power supply. I've been overclocking RK since the RK3066. We've always understood with more performance comes more demand on current. You need higher amperage. There's a reason I don't release builds clocked at 1752, though I have them; ease of use for the user, and power demands. This too has been covered before.

[Shomari]

The OP is definitely outdated. But, after seven months issuing releases monthly, along with specific device ports here and there, and other maintenance, combined with dwindling user feedback, I've grown into some bad habits.

That, as well as the fact that demands in my daily life shift leaving me with not much time some days, and more during others.

In the end what happens is I end up at least pushing the updates, so that the work is at least out, but I do it in a way that's least time intensive for me. Not always the most user friendly way, but at least it's out there.

Tremendous amounts of time go into this project. If I were simply doing, let's say, Z4 firmware and not concerned with broader compatibility, and if I were not concerned with keeping a monthly update schedule as well, that would cut 50% of the time spent, at least.

I'll organize things soon. As to organization, please do make sure when you post results of your tests, that if it's using your firmware, please be clear as to not confuse users into thinking it's a full firmware update of mine, for example.

Because I suspect many users are going to get confused about results coming from the ugoos based firmware you use in your build.

I only say that because I've been very meticulous in building and debugging my firmware in order to understand the likely range of results and performance, but I have no idea of the general results and performance of the ugoos system, especially when combined with choice elements of my firmware. That's unknown territory, as opposed to my firmware which has been evolved over 7 months at this point.

I hope I explained some things in a way that everyone can understand.

EDT: as for temperature sensing, you'll never get it with using by dtb (resource) or boot, for that matter. That's gone, thrown to the wolves with RK's throttling mechanism, as RK's temperature sensing in RK3368 is tied into its throttling and had to go as a consequence.

Again, you've showed up a bit late in the process, and so you've missed alot of these things that have already been covered.

[dkholm56]

The OP is definitely outdated. But, after seven months issuing releases monthly, along with specific device ports here and there, and other maintenance, combined with dwindling user feedback, I've grown into some bad habits.

That, as well as the fact that demands in my daily life shift leaving me with not much time some days, and more during others.

In the end what happens is I end up at least pushing the updates, so that the work is at least out, but I do it in a way that's least time intensive for me. Not always the most user friendly way, but at least it's out there.

Tremendous amounts of time go into this project. If I were simply doing, let's say, Z4 firmware and not concerned with broader compatibility, and if I were not concerned with keeping a monthly update schedule as well, that would cut 50% of the time spent, at least.

I'll organize things soon. As to organization, please do make sure when you post results of your tests, that if it's using your firmware, please be clear as to not confuse users into thinking it's a full firmware update of mine, for example.

Because I suspect many users are going to get confused about results coming from the ugoos based firmware you use in your build.

I only say that because I've been very meticulous in building and debugging my firmware in order to understand the likely range of results and performance, but I have no idea of the general results and performance of the ugoos system, especially when combined with choice elements of my firmware. That's unknown territory, as opposed to my firmware which has been evolved over 7 months at this point.

I hope I explained some things in a way that everyone can understand.

EDT: as for temperature sensing, you'll never get it with using by dtb (resource) or boot, for that matter. That's gone, thrown to the wolves with RK's throttling mechanism, as RK's temperature sensing in RK3368 is tied into its throttling and had to go as a consequence.

Again, you've showed up a bit late in the process, and so you've missed alot of these things that have already been covered.

Just want to say a quick thanks for all your hard work Shomari. I'm sure you spend a considerable amount of personal time creating some really great roms for people who otherwise would have almost useless devices (me included). Thanks for all you do.
dk

[gefattern]

Ahhh come on gefattern. Do you wanna start a world war 3 right out of nothing? Saddle down, make yourself comfortable and have a cup of tee. That was just a joke. Silly has also the meaning of giggly, ignorant, unwise.

So I meant, why they don‘t see the potential of Shomaris work for all of us RK3368 users. Not the Ugoos users in person, all those RK3368 freaks here at Freaktab. And meaning of freaks is also meant in a positive way. Because in the end, we are all freaks, but from the dark-side of the moon. Where you can get all those shit, the others are still dreaming off.

And Ugoos has still one of the best software for these TV boxes. Rich in features, stability, etc. I would be a fool, if I would ignore that fact. And by the way, when it comes to Android and its source code. It‘s still Open Source. So there is no hiding. Saying that’s my code you are not allow to use it on your own. Everybody could use my ROM, Shomaris ROM, everybody's ROM and start using and porting it to his own needs. And I didn’t sell Ugoos excellent work as my own work. I always give credit.

Ahhh, I have to stop. That was to much Off topic. Wasted time for all of us. If not, I start to get crazy inside of the membrane. BTW don’t you know I’m loco?


OK back to topic …

I will right down some instructions on how to test Shomaris and later also my builds in easy but and efficient way. Tools, good practices and so on. So everybody could join the test. Even if they had no clue about coding and all that freaking shit, the most Android users do not care. So we can unleash the real potential of our box, all together.

So let's focus on that. Everything else is silly = giggly, ignorant, unwise.

Hi cOOLio ,

first i dont want to make a WW3 from it , but i am German and my understanding of English is not like one of a US Man or UK Man .

Here "silly" means funny but crazy too and i am not crazy , i am poor not more . (payed only 80€ for my UT4 on Ali)

I know the Ugoos Company is a little bit strange with there own Customers , i felt it on my own , they do not even answer here if

Users have Questions , i tried to help with better translations but they did not even used it on there last Rom .

Hours of work for nothing .

I know u give credits and that Android is Open Source . Why only Shomaris work of course he makes good work but Mo you and others

make good work too and what about the "Mic fixT8C"??? i wrote somewhere here , now Mics work on RK3368 FW ???


thats all

nice Day

gefattern

[Shomari]

gefattern most microphones work fine on this firmware. They have for a couple months.

Only slight difference (but still significant) is I do this as a volunteer.

I don't work for any brand or manufacturer, and I don't work for compensation from 'fully loaded' box sellers or any company.

[Shomari]

Latest updates: (reposting for visibility)

http://freaktab.com/forum/tv-player-support/rk3688-devices-aa/628558-rk3368-04-2017-true-octacore-firmware?p=641321#post641321