Samsung Finally Releases MK2 Firmware for SM-900 (Hopefully fixes battery Issues)

I assume I can Odin flash MK2 over MJ7 without issues? Is the Indian MK2 pretty bloat free?

So hows it going so far?

Sent from Note 3 (The beauty & beast)

stanley08 said:

Yes you can, tho I reflashed flashed MJ7 with Full Wipe and did OTA. If you have stock, go ahead. It's still Samsung. Same amount of bloat.

Click to expand...

Click to collapse

If I don't wipe, I'll still be rooted, correct?

Do you think it's worth the trouble to flash K2 over J7?

stanley08 said:

Here mate!

MODEM_N900XXUCMK1 - https://mega.co.nz/#!3MURDbKD!QCpnEGUGjSb-awjLqY-Zwlkp1mJyuWdkxClTS8Bjg9w


NOTE: It is for N900 Exynos and NOT N9005 Snapdragon

Click to expand...

Click to collapse

Thank you

Im checking on doing the upgrade to this new firmware, but where the smoky mountains do I find my Product Code??? I know this is a dumb question, but its totally eluding me...

>>Product Code: XSE<< Im looking for this...

iba21 said:

Desktop?

Click to expand...

Click to collapse

you can't even use separate processors with different clock speeds, let alone different architectures.

In the case of BIG.little, you have an out of order execution deep pipeline with an in order execution shallow pipeline.

You could check out the mediatek mt6592. It uses homogeneous multiprocessing. you may need to use all 8 cores in multiprocessor mode though.

nakedtime said:

you can't even use separate processors with different clock speeds, let alone different architectures.

In the case of BIG.little, you have an out of order execution deep pipeline with an in order execution shallow pipeline.

You could check out the mediatek mt6592. It uses homogeneous multiprocessing. you may need to use all 8 cores in multiprocessor mode though.

Click to expand...

Click to collapse

Big little has an internal CCI cache witch connect the 2 different arch.. that's why an in order can run in the same chip than an out of order

Hmp (GTS) is a rewriting of kernel scheduler witch has to do more job

1) understand the arch of the single core, so, it has to "name" the core
2) chose when and where send the task

That's hmp

Bug.little is absolutely working in exy 5420 SoC, it only.needs a controller

More details?

Bug little uses C states as like pc cpus, those are automatically.. when linux scheduler chose to turn off one core, it will not send a task in that core, and, it auto goes offline by powergating tecnology

Actual big.little logic is called IKS (in kernel switching)
when linux dvfs goes over a frequency (650mhz for 5420) iks module moves scheduling tasks from A7 to A15..

simply.. iks has less code than hmp (gts) since it only do one "cluster switching"

You have to know with iks frequency from 250 to 650 are of cortexA7 (kernel freq is an half of real cluster freq.. so.. 650 mhz is in real 1.3ghz on A7)
From 700 to 1.9ghz there is used the A15 cluster..

Linux scheduling is the normal scheduling, so, it only move the tasks to preserve a too high ramp up of freq, so, it doesen't chose to move all tasks to 1 core to let the chip to shut down the other 3

Bug.little is a new arch logic witch is compatible only with cortexA7 and cortexA15 with CCI cache interface..

Sure.. cortexA53 and A57 too.. the 64bit version of A7 and A15