[KERNEL][AOSP/TW][27 Dec] War Kernel r3 // colder than ever

[GeeckoDev]

I just got something absolutely HUGE today.

I have always been puzzled why the OLED panel on our Note was limited to 57 Hz while 99% of the phones rocking a LCD panel are running at 60 Hz. I think it may be a reason why games are performing so poorly on our phone, because most games assume that the phone belongs to the 99% and does not feature an exotic refresh rate.

Well, it's over. It is possible to overclock the OLED panel. That's something I've never seen in any other kernel, but I bet I will be in a very near future

The only thing that needs to be changed is the .freq field in the s6e8aa0 (panel reference) struct in arch/arm/mach-exynos/mach-u1.c. The default is set to 57, but this can be cranked up to 62 Hz. Anything higher than that results in a weird mess on the screen when booting because the panel can't keep up. In logcat, gralloc should be reporting the new refresh rate.

At 62 Hz, you get 16.1 ms of latency compared to 17.5 ms by default. When the phone doesn't drop a frame, it feels smoother, and it is also noticeably more responsive. I would recommend sticking to 60 Hz though.

Right now I'm running a Touchwiz ROM (shame on me, right?), so I only tested it with a TW kernel. Once I get back home, I'll cook something for you, AOSP users

Edit: test build for Touchwiz two posts below.

 

[themanssx]

Maybe post the tw kernel as well...

 

[GeeckoDev]

Maybe post the tw kernel as well...

Alrighty.

This a TW kernel based on c.o.h.'s HelloWorld 1.2.8 sources with the OLED panel refresh rate set to 62 Hz. Download here. Flash it at your own risk using Heimdall.

Notes:
* Modules are not included which means you won't get Wi-Fi.
* THIS WON'T WORK ON ANYTHING AOSP BASED LIKE CM OR OMNI. Touchwiz only.

 

[panamera2011]

I just got something absolutely HUGE today.

I have always been puzzled why the OLED panel on our Note was limited to 57 Hz while 99% of the phones rocking a LCD panel are running at 60 Hz. I think it may be a reason why games are performing so poorly on our phone, because most games assume that the phone belongs to the 99% and does not feature an exotic refresh rate.

Well, no more. It is possible to overclock the OLED panel. That's something I've never seen in any other kernel, but I bet I will be in a very near future

The only thing that needs to be changed is the .freq field in the s6e8aa0 (panel reference) struct in arch/arm/mach-exynos/mach-u1.c. The default is set to 57, but this can be cranked up to 62 Hz. Anything higher than that results in a weird mess on the screen when booting because the panel can't keep up. In logcat, gralloc should be reporting the new refresh rate.

At 62 Hz, you get 16.1 ms of latency compared to 17.5 ms by default. When the phone doesn't drop a frame, it feels smoother, and it is also noticeably more responsive. I would recommend sticking to 60 Hz though.

Right now I'm running a Touchwiz ROM (shame on me, right?), so I only tested it with a TW kernel. Once I get back home, I'll cook something for you, AOSP users

Edit: test build for Touchwiz two posts below.

Great news thanks! :good:

 

[GeeckoDev]

I applied the modifications to Raw Kernel r6, pulled the latest changes from Omni at the same time.

Here's the result: raw_kernel_60hz_test.zip. For Omni-based KitKat ROMs only.

I consider 60hz as a safe default, because that's what is used for 99% of Android devices. Nexus devices in particular. It lowers touch response time by 1ms.

It is not tested, but should work flawlessly, so please report. Raw Kernel r7 will basically be the same with the first GPU step cranked up to 160MHz unless I find a good reason to not do it.

Edit: nope, doesn't work, see below

Edit2: NOPE, it does work, but you'll have to turn off and on the screen after the device is fully booted. also broken recovery :/

 

[XxPixX]

I applied the modifications to Raw Kernel r6, pulled the latest changes from Omni at the same time.

Here's the result: raw_kernel_60hz_test.zip. For Omni-based KitKat ROMs only.

I consider 60hz as a safe default, because that's what is used for 99% of Android devices. Nexus devices in particular. It lowers touch response time by 1ms.

It is not tested, but should work flawlessly, so please report. Raw Kernel r7 will basically be the same with the first GPU step cranked up to 160MHz unless I find a good reason to not do it.

Hi, just downloaded it and tested and I can confirm it doesn't work:
Upon boot up It starts flashing very violently (after 0.5s of showing a perfect picture of the samsung galaxy note logo) and then shows a screen which is gradually getting brighter. The phone didn't boot up and I believe it stopped getting brighter at one point. What's also interesting is that it seems to be brighter at the top half of the screen and there seem to be lines.

Sorry about the picture quality, had to use my laptop :/

ROM: CarbonROM (a nightly from about 2 weeks ago), based of Omni

EDIT: After leaving it for 5min or longer on a white, grainy screen (with different colours and scan lines) the phone showed a perfect picture 0.o. However com.android.phone keeps crashing so I can't test any further (I think it's caused by some updated RIL drivers or something that Omni merged recently).

 

[pSyCh¤_O_O]

Hi, just downloaded it and tested and I can confirm it doesn't work:
Upon boot up It starts flashing very violently (after 0.5s of showing a perfect picture of the samsung galaxy note logo) and then shows a screen which is gradually getting brighter. The phone didn't boot up and I believe it stopped getting brighter at one point. What's also interesting is that it seems to be brighter at the top half of the screen and there seem to be lines.

Sorry about the picture quality, had to use my laptop :/

ROM: CarbonROM (a nightly from about 2 weeks ago), based of Omni

EDIT: After leaving it for 5min or longer on a white, grainy screen (with different colours and scan lines) the phone showed a perfect picture 0.o. However com.android.phone keeps crashing so I can't test any further (I think it's caused by some updated RIL drivers or something that Omni merged recently).

Same here on slimkat...

Anyone have a european stockrom.tar to get me out of here...its 4 am...last two and a hours or more searching and flashing boot image with odin. Triying to get me back online but nothing seems to work and im tired..its late...please point me to the right link and please dont tell me its samfirmware .com lol
TIA

 

[XxPixX]

Same here on slimkat...

Anyone have a european stockrom.tar to get me out of here...its 4 am...last two and a hours or more searching and flashing boot image with odin. Triying to get me back online but nothing seems to work and im tired..its late...please point me to the right link and please dont tell me its samfirmware .com lol
TIA

GB ok with you?
http://forum.xda-developers.com/galaxy-note/help/official-2-3-6-links-t2829045

 

[pSyCh¤_O_O]

Thanks mate..as long as i can get myself out of here without digging through google again fo another hour...and no ICS brickbug lol

Thanks again

 

[XxPixX]

Thanks mate..as long as i can get myself out of here without digging through google again fo another hour...and no ICS brickbug lol

Thanks again

No problem, I'm not sure how to fix mine xD
Can't see anything in recovery (but it is there, just the screen is distorted)
Download mode isn't distorted but odin isn't detecting my phone
After booting up the connection to my laptop keeps resetting
Can't do a lot on my phone because com.android.phone keeps crashing (I have up to 1 tap on the screen between each crash so I can't really do anything there)

 

[NoteboyTech]

Alrighty.

This a TW kernel based on c.o.h.'s HelloWorld 1.2.8 sources with the OLED panel refresh rate set to 62 Hz. Download here. Flash it at your own risk using Heimdall.

Notes:
* Modules are not included which means you won't get Wi-Fi.
* THIS WON'T WORK ON ANYTHING AOSP BASED LIKE CM OR OMNI. Touchwiz only.

Haven't used heimdall so is their any other way to flash it? Please?

Sent from my GT-N7000 using XDA Premium 4 mobile app

 

[User_99]

Odin?

 

[GeeckoDev]

Odin?

Odin will do the job just fine.

 

[GeeckoDev]

Hi, just downloaded it and tested and I can confirm it doesn't work:
Upon boot up It starts flashing very violently (after 0.5s of showing a perfect picture of the samsung galaxy note logo) and then shows a screen which is gradually getting brighter. The phone didn't boot up and I believe it stopped getting brighter at one point. What's also interesting is that it seems to be brighter at the top half of the screen and there seem to be lines.

Sorry about the picture quality, had to use my laptop :/

ROM: CarbonROM (a nightly from about 2 weeks ago), based of Omni

EDIT: After leaving it for 5min or longer on a white, grainy screen (with different colours and scan lines) the phone showed a perfect picture 0.o. However com.android.phone keeps crashing so I can't test any further (I think it's caused by some updated RIL drivers or something that Omni merged recently).

Can you provide me your logcat output with and without this kernel?

The only explanation I have right now is because of broken HWC, but that can be fixed. What refresh rate gralloc is reporting?

 

[GeeckoDev]

I built 57hz, 59hz, 60hz and 62hz versions. The first one should be working (57hz being the default). Please report

Get them here.

If you can't access the recovery anymore, recover by flashing boot.img from an older Raw Kernel zip archive using ODIN or Heimdall.

Edit: I also found this bug report which seems to impact our gralloc code. This needs to be fixed in CM and Omni.

Edit: bug fix submitted to Omni https://gerrit.omnirom.org/#/c/10124/

 

[pSyCh¤_O_O]

Can i just flash boot.img with ODIN without converting it to tar with 7-zip ?

Damn computer at work is so crap it wont recognize device so i cant recover phone till i get home..

Should i test 57hz version once im back and running or its basically stock anyway?

Thanks in avance guys

 

[GeeckoDev]

Can i just flash boot.img with ODIN without converting it to tar with 7-zip ?

Damn computer at work is so crap it wont recognize device so i cant recover phone till i get home..

Should i test 57hz version once im back and running or its basically stock anyway?

Thanks in avance guys

Oh that's right. You can do this, or use Heimdall Suite on Windows.

On linux i'm using "sudo heimdall flash --KERNEL boot.img" in command line.

Please test everything and report back

 

[XxPixX]

Please test everything and report back

57Hz: Works
59Hz: Works
63Hz: Exactly the same effect as with 60Hz

I'm afraid I can't do a logcat whilst booting (I never could).

 

[NoteboyTech]

So 60hz kernel is perfect and balanced?

Sent from my GT-N7000 using XDA Premium 4 mobile app

 

[pSyCh¤_O_O]

Ive tried with seversl Odin versions to flash boot.img.tar
Ive also tried with Heimdall but it only lets me select PIT files.

And now ive just given up with linux...It says:ERROR : Failed to send data! Releasing device interface...Re-attaching kernel driver. Where should i put boot.img so it can grab it?

I want to avoid flashing stock...
Never mind to late...lol