Page 2 of 9

Re: [hlte][2014/AUG/31][deCAF] Yank555.lu kernel v1.0a

PostPosted: 02 Sep 2014, 10:06
by yank555
Tiny update, as cores 1-3 switched to interactive once they were offlined...

This should fix it, please have an eye on this.

Yank555.lu-hlte-deCAF-light-W03-Slim-v1.0b.zip
(MD5 0a9a759fc48d9f21b1b7b49600f9dc72)
(9.87 MiB) Downloaded 898 times


JP.

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 02 Sep 2014, 20:45
by yank555
Kernel Update

Full version --> Download Link.

Lite version --> Download Link.

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 02 Sep 2014, 22:14
by Shaitan
Whats the difference betwen Full and Lite Version?

Gesendet von meinem SM-N9005 mit Tapatalk

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 02 Sep 2014, 22:50
by yank555
Shaitan wrote:Whats the difference betwen Full and Lite Version?

Gesendet von meinem SM-N9005 mit Tapatalk


As it says in 3rd post under Lite Kernel header ;)

The lite kernel is a full rebase on CM sources, and only added features (like fast charge, touchwake, intelliplug...) but no Linux version upstreaming, nor under the hood changes.


JP.

Sent from my 'proudly eFused' Note 3 (n9005) running W03 deCAF SlimKAT v26 on Yank555.lu deCAF-lite W03 v1.0c kernel.

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 03 Sep 2014, 12:34
by Shaitan
Sorry i dont checked The Op! My Bad!

Gesendet von meinem SM-N9005 mit Tapatalk

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 03 Sep 2014, 23:55
by capnkrunch
For a second there I was thinking "yank is an idiot, CAF is the future." Obviously a mistake on my part. Just got 2 mdss crashes today on temasek 129. Sorry for ever doubting you, I'll flash the light kernel and report back. It sucks how difficult the mdss crash is to predict/reproduce. It would make things so much simpler if there was some very specific thing that triggered it every time.

Re: Vs: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 04 Sep 2014, 01:42
by piats
capnkrunch wrote:For a second there I was thinking "yank is an idiot, CAF is the future." Obviously a mistake on my part. Just got 2 mdss crashes today on temasek 129. Sorry for ever doubting you, I'll flash the light kernel and report back. It sucks how difficult the mdss crash is to predict/reproduce. It would make things so much simpler if there was some very specific thing that triggered it every time.

CAF might be the future but it needs a lot more testing to get stable

Lähetetty minun SM-N9005 laitteesta Tapatalkilla

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 04 Sep 2014, 09:57
by yank555
capnkrunch wrote:For a second there I was thinking "yank is an idiot, CAF is the future." Obviously a mistake on my part. Just got 2 mdss crashes today on temasek 129. Sorry for ever doubting you, I'll flash the light kernel and report back. It sucks how difficult the mdss crash is to predict/reproduce. It would make things so much simpler if there was some very specific thing that triggered it every time.


:D

That is very right, if we were able to systematically reproduce it, it would be a lot easier to pin down the root cause, still likely not easy, though...

In some regards, CAF is the future, but we need to be living in the now, experimental stuff needs to be done, that's the basics of progress, but I just don't understand Cyanogen's urge to throw that into a ROM thousands of users would use on their daily devices (including his so beloved OnePlus One crap).

If it was only in nightlies, fine by me, a nightly is just that, a test thing.

But then it should be nowhere near M builds, and even further away from stables... though those are in fact just specific nightlies, nothing more to it.

That's where this whole thing is wrong imho ;)

JP.

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 04 Sep 2014, 14:37
by capnkrunch
yank555 wrote::D

That is very right, if we were able to systematically reproduce it, it would be a lot easier to pin down the root cause, still likely not easy, though...

In some regards, CAF is the future, but we need to be living in the now, experimental stuff needs to be done, that's the basics of progress, but I just don't understand Cyanogen's urge to throw that into a ROM thousands of users would use on their daily devices (including his so beloved OnePlus One crap).

If it was only in nightlies, fine by me, a nightly is just that, a test thing.

But then it should be nowhere near M builds, and even further away from stables... though those are in fact just specific nightlies, nothing more to it.

That's where this whole thing is wrong imho ;)

JP.


I was wondering if they broke all the snapdragon 800 devices with the CAF stuff, sounds like they did. Also, looks like cm split up the note 3 device trees again (at least the sprint and verizon variants). I didn't see any changes to the kernel make commands so luckily I still get yank555 kernel goodness but I wonder how this affects will03's builds.

Re: [hlte][2014/SEP/02][deCAF] Yank555.lu kernel v1.0c

PostPosted: 04 Sep 2014, 15:23
by yank555
Liekly not affect it at all ...

The split is just radio stuff, the rest looks to be still "unified".

JP.