[KERNEL] [N910C/H] [MM Stable] Perseus-Halaszk-universal5433 [06 May 2016]

Search This thread

UpInTheAir

Account currently disabled
Jan 17, 2011
7,965
15,907
Phuket, Thailand
All cores are 'on', but unused ones go into low power states so it isn't quite the same thing. Cores in WFI & ultimately retention use very little power so aren't a concern. This state is available to all cores in the system so the A53 cores will go in and out of retention while the screen is on similar to how systems will have hotplugged in the past, expect retention is a much faster state to enter and exit so cores can drop into low power far more often. The hard hotplugging the kernel provides is interesting as a toy to play with (for benching A53's for example), but for practical use the retention states are far more effective than actually doing hotplugging while the device is in use.

Yes, I do realise about this, but trying to explain in simple terms in my previous reply. I assume he just really wanted to know if the disabled cores would be in work. Answer = no (retention or "off"). The "offline" cores won't be available from sysfs either, and any power consumption or work is negligible.
 
Last edited:

iba21

Senior Member
Jul 1, 2010
2,829
1,586
Venice
Question: i tryed to disable the virtual swappiness in nand, it's turned on with 20% for default.. but after some time phone starts to be slow and choppy

Does someone test it?

Does 3gb too less for a pure fluid ui? :eek:
 

kadiremrah

Senior Member
Aug 21, 2013
447
605
Nigde
Sorry I understand VM Swappiness value. (130% Stock Value)
You asked about ZSwap Memory Pool I think. This value will set how much % will be used as compressed cache on nand swap. So 0% will not be logical I think. Used @ 10% got no problem but never lower value.

Wish I understand correctly.




Maybe you didn't understand

I was meaning.. with the stock 20% value all is fluid.. if i disable it, so, no swap, after some time phone goes choppy

am i the ony one? does all use the nand swap?
 

iba21

Senior Member
Jul 1, 2010
2,829
1,586
Venice
Sorry I understand VM Swappiness value. (130% Stock Value)
You asked about ZSwap Memory Pool I think. This value will set how much % will be used as compressed cache on nand swap. So 0% will not be logical I think. Used @ 10% got no problem but never lower value.

Wish I understand correctly.

You can chose the ammount of nand memory witch use as swap, the swappiness ( default 130 ) the second one means the kernel preference, higher values = more swap.. linux has 60% as default..

Anyway this is my first phone witch uses swap..

My previus question is..
I tryed to disable swap, but, after a bit i see the phone get lagghy.. so.. do you use the stock values or did you disable the swap?
 
  • Like
Reactions: MichaelShan

UpInTheAir

Account currently disabled
Jan 17, 2011
7,965
15,907
Phuket, Thailand
You can chose the ammount of nand memory witch use as swap, the swappiness ( default 130 ) the second one means the kernel preference, higher values = more swap.. linux has 60% as default..

Anyway this is my first phone witch uses swap..

My previus question is..
I tryed to disable swap, but, after a bit i see the phone get lagghy.. so.. do you use the stock values or did you disable the swap?

If you disable swap. Set swappiness to 0
 

white7561

Senior Member
Sep 27, 2013
2,241
529
Somewhere
My benchmark is about 43 . even i oc to 2.1 on a57 and 1.6 a53 . gpu 600(stock) but still 43.000 hmm. Any after benchmark the max freq for a57 is 1.7 that cauzing to low score. I know u need thermal Throttle . but please increase the temp before it throttle and make it auto to change to the nornal freq if the temp is safe. So i dont need to like go to synapse and click the X button after playing HARDCORE game :( thx :) @kadiremrah
 

kadiremrah

Senior Member
Aug 21, 2013
447
605
Nigde
Room temperature is very important.
Increasing throttle value 5°C will give you only 2 more seconds on high freq.
Main problem is, termal transfer speed of phone body is ~3Watt per second on 25°C room temperature so you can only use thermal capacity of body as a coolant on max load. SoC consumes ~10Watt at max load. So 7Watt energy will heat body and when body get hot SoC will start to throttle. And get it self to 800MHz A57, 1.3GHz A53 and 266MHz GPU state which is near 3Watt SoC power.

So cooler Room temperature will help you,
Over Clock will not help you,
Using Phone UnderClocked will help you best. If you use phone @1.2GHz max A57, @1.3GHz max A53 and 420MHz max GPU this will give you more smooth gaming time. (With these settings SoC will consume 4.5Watt max. and 3Watt average so everything will be on smooth side)

Wish helps,

My benchmark is about 43 . even i oc to 2.1 on a57 and 1.6 a53 . gpu 600(stock) but still 43.000 hmm. Any after benchmark the max freq for a57 is 1.7 that cauzing to low score. I know u need thermal Throttle . but please increase the temp before it throttle and make it auto to change to the nornal freq if the temp is safe. So i dont need to like go to synapse and click the X button after playing HARDCORE game :( thx :) @kadiremrah
 
Last edited:

darkbahamut

Senior Member
Mar 1, 2010
126
48
Overclocking the A57's is probably a performance loss to be honest. It might help in some light burst loads like webpage loading, but for benchmarking it's almost certainly a negative as the SOC will throttle more quickly a snoted above. Perf/watt is lower and given there is a fixed load of work you'll get no performance gains. The biggest performance gains come from heavy undervolting as this increases perf/watt and leads to less throttling, but any overclocking on the A57's is a bad idea.

Personally I would say underclocking doesn't help much. While gaming the device shouldn't be using the high speed states on the A57 as game loads are rarely that sustained on the CPU side. If it's like that in most games then you've misconfigured your kernel settings as b.L shouldn't be allowing that to happen. Underclocking the big cluster will mean you should pay careful consideration to the HMP thresholds set as they will need tweaking with that for optimal usage.
 

white7561

Senior Member
Sep 27, 2013
2,241
529
Somewhere
@kadiremrah what the best hmp up and down scale so it can adjust like when u using like only music or light app. It uses the a53 not the a57 cuz i see like if it on high load it didnt use a57 so much. So. Yea. And after benchmark max freq is scalled down to likr 1.7 but. It didnt go up again after device cools. Any fix or workaround for that ? Thx so much :)
 

halaszk88

Senior Member
Oct 20, 2011
284
1,592
Abony
5.1.1 Test kernel here!

Please upgrade your ROM busybox from Playstore because most of custom ROM not compatible with new lollipop busybox. Before you dont upgrade your busybox please do not start synapse, it is crashing your profile. (This making to synapse working and any other script from my kernel.)

The kernel is fully autoroot 5.1.1 ROMs!

PM me to bugreports! :)
 
Last edited by a moderator:

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    - FIRST READ -
    ** THIS CAN BRICK YOUR DEVICE **
    ** ONLY FOR SM-N910C/H MARSHMALLOW**
    IF YOU NEVER FLASH AND SET A KERNEL BE AWARE
    IF YOU ARE NOT HAPPY WITH THIS KERNEL FLASH OTHER CUSTOM KERNELS
    (GoogyMaxN4 or Wanam or Ultimate)

    I asked for permission to announce this kernel and All credits goes to @halaszk88

    DONATE to halaszk88
    (Every Coffee you send, will help him to work overnights :) )


    Github Source:
    2016.05.06 - All Sources are up to date V2.2MM Version


    Kernel Download:

    Thanks;
    Credits,and big thanks to:

    -halaszk88
    -AndreiLux
    -UpInTheAir
    -Faux123
    -Yank555.lu
    -Friedrich420
    -Dorimanx
    -Alucard24
    -Flar2
    -Myfluxi
    -Savoca
    -TwistedUmbrella
    -and to many many others!
    19
    Kernel V1.1 Update:

    • wireless: dhd: Enable standby ARP and multicast packet filters
    • security: SELinux: revert Samsung hard enforcing
    • cpufreq: Remember last policy min/max on cluster restart
    • HMP: Added HMP_LITTLE_PACKING control from sysfs
    • HMP: sched: Clean up hmp_up_threshold checks
    • HMP: fix out-of-range CPU possible
    • HMP: Do not fork-boost tasks coming from PIDs <= 2
    • HMP: Make idle balance behaviour normal when HMP: HMP_LITTLE_PACKING is disabled
    • ARM: Mali-T760: disabled min/max lock sysfs
    • Various sched/mm/writeback/workqueue fixes
    • gpio: sysfs: fix memory leak in gpiod_export_link
    • gpio: sysfs: fix memory leak in gpiod_sysfs_set_active_low
    • ARM: DMA: ensure that old section mappings are flushed from the TLB
    • cpufreq: interactive: merge interactive governor from new G920F source
    • input_booster: ported from SM-G920F
    • cypress-touchkey: Added input-booster event (from S6)
    • misc: Input booster: Allow configurable levels
    • Exynos-Thermal: Smoothen throttling levels
    • CPUFREQ: EGL: increase booting freq to 1.7GHz
    • ARM: enable UNALIGNED_ACCESS

    Synapse:

    • Added HMP packing mode control for Advanced TAB ( Auto mode will be able to use automatic when you are in POWER_SAVE_MOD in TW ROM, if disabled POWER_SAVE_MOD hmp_little_packing auto disabled so kernel use normal packing (more performance)

    Download at my github: Perseus-halaszk-universal5433
    19
    Kernel V1.3 Update:

    Kernel:

    • Merged N910CXXU1BNL8 sourcecode from OSRC release.
    • Drivers: battery: fully reverted stupid fast_charging driver and make Universal5433 Max77843 charge control (original version thx to Andreilux)
    • Mach-Exynos: added exynos-interface for control min/max online SOC core control
    • Varios fixes for workqueue/procfs/mm/iosched/ext4/sched/irq
    • I think the WIFI touchlag has gone away
    • I made Device Tree image file generating script, now we can use a compiled dt.img from our dts source code.

    Synapse:

    • I added a new TAB to Synapse: HMP: under this TAB we can controlling HMP UP/DOWN migrating thresholds
    • New charge-control interface under Battery TAB: support and fully controlled the normal and the adaptive-fastcharging, USB, and various MHL charging current.

    Download at my github: Perseus-halaszk-universal5433
    13
    Bugs - Screen Shots

    -BUGS-
    WiFi must be always ON to prevent MicroLags, TouchLag, UI Lag (Discussed on AndreiLux issue tracker)

    -My Personel Settings-
    https://youtu.be/W1if5mkhY1Q

    My personel settings are like this. UnderVolt settings will not be compitable with yours. Every SoC has it's own UV capability so try and find yours.

    -Power Advantage Calculation for My SoC -
    Exynos5433_T760.png


    As per AndreiLux's measurment:
    "A57 are about 1.87 more efficient in performance per Mhz and 4.23 times less efficient in perf/W outside of voltage droop."

    -Benchmark ScreenShots-
    13
    Kernel V1.4 Update for N910C/H/U:

    Kernel:


    • Merged N910CXXU1BOE3 Sourcedrop
    • Updated Linux mainstream to 3.10.82
    • Varios fixes for writeback/fs/cpufreq/kernel-scheduler/Wifi-driver/ARM-platforms/mm/kthread_work/smp
    • Drivers: GPU: optimize min/max threshold in dvfs table
    • Exynos5433-common DTS: merge input_booster and IPA config from exynos7420-zero-common
    • Dynamic CPU Hotplug: ported exynos-interface from Universal5410 to control min/max online core control
    • Drivers: sensorhub: reduce wakelock time
    • Drivers: GPU: less dvfs polling time
    • Added fully support for SM-N910U device, now we have a barebone kernel for (C/H/U)
    • Kernel now fully compiled from DTS device tree source

    Synapse:

    • Added Exynos Core control
    • Various ramfs tweaks

    Download at my github: Perseus-halaszk-universal5433