yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
NovaThor Settings v1.6 is Up !!!

And new kernel build due to the right permissions for NT-APP !!

Changelog:

20150807:

Mali: Changed Freqs order to make it compatible with NT-APP v1.6

Updated permissions for NovaThor Settings v1.6

Use it only with NT-APP v1.6 or later !!!

Clean Build

NovaThor Settings v1.6

Removed TCP Control

Charger: add missing currency Steps and use 700mA as default

Replaced buggy cycle charging with "Charger OFF"

Removed EOC

Removed Deep sleep states

Removed LPA

Removed buggy 2tap2wake + sweep2wake

Removed non working Min Brightness Control

LCD Type Detection

Removed Fsync Control

Added LCD Freq Control

Reworked MaliAutoBoost

Fully working GPU OC (Fail Safe)

Removed Mali L2 Max reads + pre_allocated_memory_size

Removed Sched_mc_powersaving Control

Removed use_spi_crc

Removed Read ahead kb

Removed Torch (burning led)

Re-implemented BLN Blink Control

Completely reworked CPU/GPU UV/OV Control (more stable)

CPU OV/UV: +-50mV (200-1000Mhz)

GPU UV: -300mV (500-680Mhz)

Languages Support: EN, DE, IT

Cleaned Sources

Clean Build

Use it only with ace2nutzer kernel version "20150807" or later !!!

Older Changelogs:

https://docs.google.com/document/d/1IoeWy3yipGGFvkl1WrMsOFpDVkBlPUeVmFV9l7ROrqQ/edit?pli=1

Download Kernel:

http://xda.mister-freeze.eu/XDA-fil...e2nutzer.kernel.4.4.x_20150807_codina.p.l.zip

Download NovaThor Settings v1.6:

NovaThorSettings_v1.6.zip - 497.51 KB

Notes:

Highly recommended to delete first the old NT-APP .. and reboot one time the Phone.. so that the data folder (with old settings) will be automatically wiped !!! - And do also wipe cache + dalvik cache ;)

Pls test and report.. if u'll find any issues with the App !!

Reports about how much u can UV are appreciated :)

Notes #2:

Pls no questions about: what is the best Values blah blah, best Values are already Kernel Defaults.. and those "defaults" are also stored in the new NT-APP ! (marked as Standard, Default etc..).
[Galaxy Ace II Android Development] manthes:
This patch can be used for every rom?
[Galaxy Ace II Android Development] ace2nutzer:
I think yes, but may it can broke other things like: camera, yt, and maybe even live video at all
[Galaxy Ace II Android Development] DetroX:
My codina is stable undervolted to -50 cpu (up to -75 on chrono) and -50 gpu. ;)

I have a small bug on every 4.4.x rom and every kernel. Every app to monitoring GSM/3G singal ex Netmonitor can't show signal stronger than -89dBm (on stock JB up to -50dBm). Pls fix it :( or maybe i can fix that ? :confused:
[Galaxy Ace II Android Development] ace2nutzer:
No idea about Signal.

About UV: pls don't compare it with other kernels, as for example this kernel is around -50mV already by default undervolted.. (Compared with chrono, but even not on every freq.step same). .. So if u can uv here stable -50mV for CPU then u have an real UV up to -112.5mV ! (Depend on the voltages from the AVS file)

And GPU is not uv by default.. That's why U can uv up to -300mV.

And GPU UV depends on which max freq u want to use...

If u'll use so let say 500mhz instead of max. 680mhz, then u can UV much more.

There is ability to UV it up to -300mV.

Btw: what about latest kernel and the finally updated nt-app ??

It is working good ??

One more thing: can somebody with WS2401 LCD, check and report if nt-app will show u the correct model? Then we know that it's working properly ;)
[Galaxy Ace II Android Development] Bito21:
[MENTION=5840412]ace2nutzer[/MENTION], my nt-app detecctss the correct lcd.

I have the ws2401 and changed the freq to 49.92 and no problems. until now,

so far undervolt -50mV on CPU seems stable.

testing UV on GPU and report.

by the way, my android OS consumes a large percentage of battery, any advice?
[Galaxy Ace II Android Development] DetroX:
My too i.imgur.com/9k37igG.png
[Galaxy Ace II Android Development] xtomashpl:
New version supports f2fs?
[Galaxy Ace II Android Development] ace2nutzer:
Check u guys with BetterBatteryStats ... but probably it's Google Play Services ... so u've to disable wakelock.

Nope and i don't plan it :)
[Galaxy Ace II Android Development] xtomashpl:
All partitions must be formatted ext4?
[Galaxy Ace II Android Development] ace2nutzer:
yes...

if u don't want to wipe data:

make cwm backup (with actually f2fs kernel)

then switch to ext4 in mounts and storages

format data, system and cache as ext4

reboot recovery

switch again to ext4

now advanced restore and choose -data

reboot to recovery

switch again to ext4

make cwm backup (now the backup is in ext4 format ;) )

and flash latest kernel

reboot to recovery

flash latest CM11

flash again latest kernel

reboot recovery

now advanced restore and choose:

-data

wipe cache

wipe dalvik cache

reboot recovery and if want:

install latest gapps
[Galaxy Ace II Android Development] PolishVodka:
His kernel for others system, unfortunately I cannot test every, only checked if stock JB working. Philz Recovery, P support.

https://drive.google.com/file/d/0B7hlS8uionOjblZsRzYtNkdQWEk/view?usp=docslist_api

Stock JB, 4.2 Roms, 4.3 Roms, 5.X Roms in aroma installer.

PS. OTG isn't working any way on this kernel. For me S6D screen is overclocked too much and even when I chenged frequency to stock, still was visible something what's I didn't like when scrooling up&down.
[Galaxy Ace II Android Development] ace2nutzer:
Strange @ OTG ... but it's already activated in kernel .. also on stock JB Kernel it's fully activated ...

I'm quite sure OTG is 100% OK for U8500:

for CONFIG_AB8500_USB:

Enable this to support the USB OTG transceiver in AB8500 chip. │

│ This transceiver supports high and full speed devices plus, │

│ in host mode, low speed.

@ S6D .. hmm weird.. on which System is the problem ?? Here on CM11 it's okk....

btw: did u used the script what i've send to u ?
[Galaxy Ace II Android Development] PolishVodka:
On stock JB, but I know this effect perfectly from my old and damages WS LCD. This is something like too much frequency for this screen driver.

But even when I go back to 307... stock freq from lcd_clk interface, scrooling wasn't smooth. I don't know how this look on CM11 because I don't use already any KK.

And about which script you asking? I only included device_tunables because any JB support performance profiles and I didn't find anything else in your ramdisk.

[MENTION=309187]edit[/MENTION]: Doesn't matter, I was now see board-codina-mcde ....

Sorry but this doesn't make sense to do anything in S6D, you're over clocked screen freq + changed to lowest values .video_mode.hbp | video_mode.hfp in the same time.

For me this killing smoothness in my case.

I know, WS screen is crappy (from stock JB, but on GB it was even ok as i remember) and need lowest values of this video_modes (and this was nice find from you) but after this you shouldn't over clock refresh rate.
[Galaxy Ace II Android Development] ace2nutzer:
okay, i've never adapt this kernel for all android versions .. both screens are working perfectly here on CM11 ... nobody is complaining.. just working great ;)

yes device_tunables .. because there is settings for some things like LMK .... and more important for latest NT-APP .. to make it fully working and stable.

Yes that's right, on WS2401 changing both tunables wasn't good idea .. i did this just "approx" as i already didn't have this screen anymore...

but after some time i test the smoothness correctly on my mothers ace2 with WS LCD .. and i saw it wasn't perfectly smooth ... also i saw some (small) tearings on scrolling.. no matter if vertical or horizontal.. that's why i reverted video modes and use again 57Mhz.. still the best option.

But here for S6D i've also tried every thing and the best combo is 36Mhz + tuned video.modes... try to find better values :D

But anyway, here on S6D with CM11.. there is no problem with tearings, and scrolling is smooth... and vertical AND Horizontal 2D games are running perfectly ... in some combos only vertical 2D games are smooth, but horizontal not ... and so on ... believe me, i've spend a lot of hours to find best values... i only like the perfect way :p

btw: Chrono did a patch for reboot issue when charger is present + one new feature (but my idea :D) is to turn the BLN ON when battery has 100% and when unplugging the cable ----> BLN OFF ... (next version, will also have this..)

Usually i'm using this feature all the time with TASKER ... but on offline charging that wasn't working of course.. so i asked Chrono and he did immediately an patch .. btw: that Dev. is really fast in programming :good:
[Galaxy Ace II Android Development] PolishVodka:
ace2nutzer

I don't play with any games, so I don't care about, I believe in your rights. For me the best test for smoothness, where I didn't see any tearing, frame droping (vertical) is in opera mini. Long sites in one column view (but the same I'm feeling in interface of system, some existed lags, if any, coming for me just from ROM, surfaceflingers etc. None of Rom's is perfect).

And as I'm talking, the best values for S6D are just stock values, this screen DOESN'T NEED ANY IMPROVEMENT'S.

I'm pretty understand that you didn't care about other Roms and supporting only yours CM11, but even on this system, feelings should be better on stock values (for S6D users, WS screen really need this lowest video.modes, but not highest LCD clk).

In board-codina-mcde we have definitions of LCD clk rate for both drivers (PRCMU_DPI_CLK_SHARP_FREQ | PRCMU_DPI_CLK_SMD_FREQ), but (correct me if I'm wrong) anywhere here is used SHARP_FREQ, so always is used SMD_FREQ. This is bad for S6D.

Your and Chrono's kernel has mcde_clk freq interface of course, but for me this function isn't working the same like defined values in board-codina-mcde.

When I was have WS screen, and was defected with this black screen bug, only solution to fix it when waking up devices was highest refresh rate defined in board-codina-mcde, in mcde_clk interface bug still was present (the same freq).

You're are talking peoples doesn't complain about smoothness, but even when LCD freq was increased for long time (from 4992 to 6240) to fix tearing on WS displays, and this was twice more than stock S6D (which was terrible for this screen, some time ago I was on kernel with that freq) not so many users posted about problems, only about black screen bug...

And yesterday after using stock JB (I know, you care only for CM) with this kernel, I got first time on new screen problem of display after rotating screen (was gray).
[Galaxy Ace II Android Development] ace2nutzer:
I'm sorry, but here on CM11 it needs some adjustments .. be sure that i don't touch anything if it's already 100% OK. :)

sorry, i've really check those things very very carefully.... actually kernel defaults for both screens are just 100% OK..

There is only one leftover little bug, i'll explain here below .....

I still don't know what u mean .. u maybe are mixing up my kernel with chronos one ... .. here on my kernel every LCD works with his programmed freq on kernel.. but 100% sure not one freq for both LCD's .. also LCD detection is correct.. and that beginns already with executing Bootloader :)

So can u make more details, or better just show me the "bug" in my Repo ?? - Thanks ;)

Yep :) Now i got it ! .. u mean surely this:

https://github.com/ace2nutzer/Samsung_STE_Kernel/blob/3.0.101/drivers/video/mcde/mcde_hw.c#L1182

There is defined an stardard LCD freq.. this freq. is for both LCDs defined .. but during booting up.. the used freq is the board-codina-mcde .. one.

And after this, is used the one what the user want to have .. (in the sysfs) ... BUT when turning the screen OFF the LCD freq will be "rebased" to the default one.... and after waking up the screen.. it'll set again the freq from the userspace .... OF course this is senseless more or less ... i didn't programmed that "mistake" i don't know who did this.. cocafe or Chrono ... (not important) but anyway later it was "fixed" by chrono ... in his kernel ... and i didn't merge this "fix" because i was just too lazy .. and just because it didn't cause any problems so far :D

https://github.com/ace2nutzer/Samsung_STE_Kernel/blob/3.0.101/drivers/video/mcde/mcde_hw.c#L1377

Yeah old thing .. and like u know by yourself this famous BS Bug is nothing else than an hardware bug .. not software.

With which LCD freq xxxx for S6D ??? u told me u changed it later in NT-APP or so ... :)
[Galaxy Ace II Android Development] PolishVodka:
No problem. But I know what I see on stock JB, I'm not using your CM, I'm must believe you.

You don't have anymore WS, so you cannot be 100% sure, you only thinking that because someone told you this. From my experience when I was on WS, lowest video.modes + 60+ LCD freq = tearing visible on whites backgrounds. Lowest video.mode + stock 4992 = nice smoothness everywhere, some frame dropped because of ROM surfaceflinger, but this mix was the best what's I was seeing on this screen (maybe excluded Gingerbread).

No, we not talking here about Chrono's kernel.

I'm mean that's:

# define PRCMU_DPI_CLK_SHARP_FREQ

36305454 /* Stock: 30720000 */

42

# define PRCMU_DPI_CLK_SMD_FREQ 57051428 /*

Stock: 49920000 */

and function

static struct mcde_port port0 = {

79

.type = MCDE_PORTTYPE_DPI,

80

.pixel_format = MCDE_PORTPIXFMT_DPI_24BPP,

81

.ifc = 0,

82

.link = 0,

83

/* sync from output formatter */

84

.sync_src = MCDE_SYNCSRC_OFF,

85

.update_auto_trig = true,

86

.phy = {

87

.dpi = {

88

.tv_mode = false,

89

.clock_div = 2,

90

.polarity =

91

DPI_ACT_LOW_VSYNC |

92

DPI_ACT_LOW_HSYNC |

93

/* DPI_ACT_LOW_DATA_ENABLE | */

94

DPI_ACT_ON_FALLING_EDGE,

95

.lcd_freq = PRCMU_DPI_CLK_SMD_FREQ

96

},

....

So, as I know in this stage is used only frequency for WS driver (2x stock S6D) for both screens and is changed in later state to this from mcde_clk interface for both drivers different now.

But in my case this "later" makes the difference.

When we didn't have this mcde_clk interface, for both drivers was used always freq from WS.

Stock from you.
[Galaxy Ace II Android Development] ChronoMonochrome:
Right now I don't remember whether it was my idea, or I has found it in CoCore kernel. This trick was needed to ensure there are no screen tearings which happens if you just LCDCLK freq to 49.92 MHz in board-mcde-codina.c. I don't know how it works on your kernel, but for me without using that trick was same as if lcdclk freq just set 49.92 MHz(so you face tearings everywhere). Of course, I'm not quite satisfied with the way it works now, because I'm not sure how it works and why it should be different from simple freq change in board-mcde-codina.c, but somehow it works. This also seem to be causing "grey screen" bug on stock JB, but to be honest, even I don't care about JB. On most ROMs it seem to work properly(maybe only with exception of some 4.3.x, which has had tearings in the past).

But in indeed, lcdclk freq is being set to PRCMU_DPI_CLK_SHARP_FREQ here https://github.com/ChronoMonochrome.../arch/arm/mach-ux500/board-codina-mcde.c#L436 . Only later it's overriden again by lcdclk code.
[Galaxy Ace II Android Development] ace2nutzer:
Yeah, i also don't say that it'll or it should work great on Stock JB .... so i also believe u .. 100%.

btw: are u seriously using Stock JB ? Or it's just for testing purposes ?? xD

If so, why u don't simply fork my kernel to your GitHub Account and then change all LCD Things like u want for Stock JB .. and then only merge (if u want) latest commits ? ;)

(u probably again speaking for Stock JB ?) I can only speak for CM11 here...

Nope, my mother still have an ace2 with WS ...(CM11 + always my latest kernel) and i've see some small tearings with tuned vide_modes + 499 ... and yes, u're right... tuned video_modes + 57Mhz is not smooth ... but after reverting to stock video_modes + 57Mhz = smooth and no tearings at all :)

Btw.: it makes really no sense to use tuned video_modes and stock freq for WS .. because it drains same power like 57Mhz and of course it also reduces stability .. it's like overclocking .. so it's not 100% for free ;)

OMG :D Nope, Nope and Nope ;)

U still believing that there is a messed up with LCD type identification .. forget this very quickly .. it's working perfectly !

I can tell u one user with S6D + blackscreen bug ... i believe it was [MENTION=4365971]manthes[/MENTION] .. i've building an kernel for him with everything @ 30,7Mhz for BOTH LCD Drivers .. because i had also thought maybe on his phone LCD detection is wrong because of hardware failure .. bug no luck .. still blackscreen .. even on cwm ! ;)

U probably also don't know that on Stock GB there is NO S6D Driver... the S6D LCD WORKS with WS2401 Driver ! BUT that doesn't mean it works with WS2401 Freq ! ;) weird ?? Check on my repo .. there is also stock GB and JB Sources ... without any changes of course.

If u still can't believe that, install stock GB ROM with stock kernel.. and check with ADB .. /sys/devices/pri_lcd_ ... u'll see ws2401 with your s6d ;)

But this is not all, .. enter in this folder and check some files like: /lcd/panel/lcd_type + panel_id .. in one of both files u'll see: SHARP (s6d) :highfive:

and later on JB it was splitted.. but LCD freq was never changed.. only the driver ... and the driver for S6D .. and also here on this kernel.. is based on WS2401... see:

/*
* S6D27A1 LCD DPI panel driver.
*
* Author: Gareth Phillips <gareth.phillips@samsung.com>
*
* Derived from drivers/video/mcde/display-ws2401_dpi.c
*

@ LCD probs after rotation .. yes.. this is possible on s6d .. because it's pushed to the max... tuned video_modes + OC'ed freq .. here on CM11 works fine .. but i know i can't OC more .. then i also will having problems ... in this case just reduce the freq on NT-APP.

[MENTION=5695278]ChronoMonochrome[/MENTION]

u're using for 499 for WS + tuned vide_modes from 8/8 @ 1/1 .. if'll see problems like colored tears on the side, right, left or what ever .. this is coming due to the changed vide_modes.. but as i already said, it's not best solution for at least on CM11 here ...

anyway i'll make simple test if the s6d screen uses really first the WS freq ... and then changed to s6d freq ....
[Galaxy Ace II Android Development] ChronoMonochrome:
No, I had nothing like that. Only apps/games where I have tearings with stock WS2401 freq is flappy birds(and probably other similaries). But if you say that changed video mode interefes with higher than stock freq, then it would be really handy to allow change video mode on the fly. I has found some stuff in CoCore which allow us to do it, and also found why it didn't work for me when I tried make similar interfaces.
[Galaxy Ace II Android Development] ace2nutzer:
yes, it makes probably sense.. but i'm warning u ... :D that can drive u and other users really creazy.

it's a game between LCD freq and video_modes ... that means every video_mode value has another effect with every LCD freq !

So that way there are many config scenarios possible :)

If u want to make interface, allow for the both values u did changed @ "1" .. for WS between 1 - 8 .. and for S6D: 1 - 63

Now a little explanations what those values do, according what i know:

lower values = like increasing lcd freq, more power consumption.

higher values = like decreasing lcd freq, lesser power consumption.

On lowest Value.. so let say 1 - 5.. u can't OC stable @ xxMhz like without stock video_mode. (so max. stable LCD freq, is then lesser)

Now why u shouldn't allow bigger Values than stock:

first of all: nothing can happen... but increasing such values more than stock, will only cause an wrong playback of the LCD .., everything will working slower.. slower runtime and so on.... it's like the "pitch" on the turntables (yes i've such things xD)
[Galaxy Ace II Android Development] PolishVodka:
Thanks Chrono and ace2nutzer, now I understand how this work.

Edit: Will be more clear for me if someone explain, why changing SMD freq in board-codina-mcde.c was causing screen flickering on SHARP display in older kernels?
[Galaxy Ace II Android Development] ChronoMonochrome:
That's odd.. Honestly, I understand it no more than the trick I described before. But fact is, S6D default freq is 30.72MHz, some users confirmed it here after they opened lcdclk sysfs file. Yes, I also noticed that "later" lcdclk freq change through lcdclk interface is different from "direct" change in board-mcde-codina. Maybe this was a reason for using trick above.
[Galaxy Ace II Android Development] manthes:
'Ok i don't undestand what you are telling i admit it :o:p

I will say a few things just if it helps you. I have blackscreen ONLY with cwm even with clean install. The most interesting thing is with temporary cwm. With oldest builds is ok but with CWM 6.0.5.x i have blackscreen even i install it from stock recovery or TWRP. BUT if i install CWM 6.0.5.x from philz recovery i DON"T have blackscreen.

I am saying it if it helps you to understand a little more how it works

.......................................

And something else. I can't say that changing lcd frequency i see any visible difference except of course if it goes to 60 MHZ
[Galaxy Ace II Android Development] ace2nutzer:
thx for your investigations ...

that sounds like u've problems with the NAND-flash or at least with the 2 kernel partitions ...

I know this problem after repartitioning the kernel partitions .. it never worked right, only solution was to flash 3-part stock ROM.. then it was ok ..

but i think u already tried this ?
[Galaxy Ace II Android Development] manthes:
Yes. The problem happened from the first time that i used custom rom with cwm and i mean with cm 10.1 with stock kernel. And i have installed again the Russian gb.

Just mentioning it because as i see my lcd is unique ?
[Galaxy Ace II Android Development] ace2nutzer:
New Builds are Up !!

Changelog:

20150810:

MaliAutoBoost: added more steps

MaliAutoBoost: allow to OC up to 700Mhz instead max. 680Mhz

Fix: shutdown the Phone correctly if a charger is attached instead to reboot to system again- thx @ Chrono

Use it only with NT-APP v1.6.1 or later !!!

Clean Build

NovaThor Settings v1.6.1

MaliAutoBoost: Stability Fix, reworked freq. tables.

MaliAutoBoost: added more steps

GPU: allow max. UV (no limit) (up to -325mV) (450-700Mhz)

CPU: allow max. UV (no limit) (up to -250mV) (200-1000Mhz)

CPU OV: up to +50mV = approx Hardware defaults

GPU: OC up to 700Mhz

LCD Freq Control: optimized "default" option (no reboot required anymore)

Clean Build

Use it only with ace2nutzer kernel version "20150810" or later !!!

Download Kernel:

http://xda.mister-freeze.eu/XDA-fil...e2nutzer.kernel.4.4.x_20150810_codina.p.l.zip

Download NovaThor Settings v1.6.1:

NovaThorSettings_v1.6.1.zip - 497.47 KB
[Galaxy Ace II Android Development] Bito21:
Testing..

[MENTION=5840412]ace2nutzer[/MENTION], so far 0 problems,

CPU undervolt -87.5mV.

cannot undervolt more, otherwise the phone reboots.
[Galaxy Ace II Android Development] greeceeeee:
Is it possible to explain me or give me something to read about voltage settings on cpu and gpu?