So I got my i9500 and already did some foolery with it.
Fine device, but I hate the raised lip around the screen edge. Something I definitely did not miss on the S3 and something very annoying.
Other than that small design critique:
THE ****ING PHONE ISN'T RUNNING FINAL FIRMWARE!
Basically the CPU is running on the cluster migration driver, meaning it switches all four cores from the LITTLE to the big cluster, as opposed to the core migration driver who does this in an individual core-pair manner.
You can pretty much throw all battery comparisons out of the window: it's completely unfinished and unoptimal.
I already compiled the kernel and flashed it without the cluster migration tidbit, but the phone won't boot. So yea. Current sources also useless.
Cleverly enough: you can't really distinguish between the two drivers apart from one manner: if /sys/devices/system/cpu/cpufreq/iks-cpufreq/max_eagle_count is present, you're running an IKS driver. If it's not, then you're running the sub-optimal IKCS driver.
So yea. We'll see what Samsung does about this, currently the advantages of big.LITTLE are pretty much unused.
Another nail in the coffin on how rushed and unprepared this phone has been.
Fine device, but I hate the raised lip around the screen edge. Something I definitely did not miss on the S3 and something very annoying.
Other than that small design critique:
THE ****ING PHONE ISN'T RUNNING FINAL FIRMWARE!
Basically the CPU is running on the cluster migration driver, meaning it switches all four cores from the LITTLE to the big cluster, as opposed to the core migration driver who does this in an individual core-pair manner.
You can pretty much throw all battery comparisons out of the window: it's completely unfinished and unoptimal.
I already compiled the kernel and flashed it without the cluster migration tidbit, but the phone won't boot. So yea. Current sources also useless.
Cleverly enough: you can't really distinguish between the two drivers apart from one manner: if /sys/devices/system/cpu/cpufreq/iks-cpufreq/max_eagle_count is present, you're running an IKS driver. If it's not, then you're running the sub-optimal IKCS driver.
So yea. We'll see what Samsung does about this, currently the advantages of big.LITTLE are pretty much unused.
Another nail in the coffin on how rushed and unprepared this phone has been.