[KERNEL][AOSP/LOS] SINAI-N4 Kernel

[bgoel4132]

what happened @sudokamikaze isn't the new build stable or upto your mark.. ??

 

[d_g_m_2000]

what happened @sudokamikaze isn't the new build stable or upto your mark.. ??

dude, it will be released when it's ready..
why do you wanna flash something that it's not finish and then bomb complaints about performance...
no ask ETA.. read the rules!

 

[bgoel4132]

dude, it will be released when it's ready..
why do you wanna flash something that it's not finish and then bomb complaints about performance...
no ask ETA.. read the rules!

i was just curious unlike you who has second phone for daily use

 

[d_g_m_2000]

i was just curious unlike you who has second phone for daily use

nexus 4 is my daily driver... my other phones is a nokia 105 we have to wait.
hope OP can release soon.

 

[sudokamikaze]

i was just curious unlike you who has second phone for daily use

I'm using my mako still as daily driver
And yeah, I've tired of those drainings too

I had 95 to 79 % overnight
That's why I didn't release it yet

 

[Sam Nakamura]

i was just curious unlike you who has second phone for daily use

Secondary phone or not... it's still impolite and against the xda-developers rules, there's a "no ETA policy" in place for a reason, no matter how much a individual user needs the custom software (ROM, kernel, APP, Mod, etc.) or how many devices the user has, besides that it wouldn't be the first project on XDA I see dying because users keep ignoring basic rules, this can kill motivation, Devs are just humans and it's a hobby here after all, they don't get paid, they owe nobody nothing - what I mean is, be careful with such questions as they can make nice threads go sour & closed and this isn't in our interests, isn't in your interest, not saying that this is what's going to happen, not at all, but patience is a virtue and we all shouldn't forget that...

Sent from my OnePlus 3T using XDA Labs

 

[bgoel4132]

Secondary phone or not... it's still impolite and against the xda-developers rules, there's a "no ETA policy" in place for a reason, no matter how much a individual user needs the custom software (ROM, kernel, APP, Mod, etc.) or how many devices the user has, besides that it wouldn't be the first project on XDA I see dying because users keep ignoring basic rules, this can kill motivation, Devs are just humans and it's a hobby here after all, they don't get paid, they owe nobody nothing - what I mean is, be careful with such questions as they can make nice threads go sour & closed and this isn't in our interests, isn't in your interest, not saying that this is what's going to happen, not at all, but patience is a virtue and we all shouldn't forget that...

Had you just read what i said i never asked for eta first grt that confirmed, before blaming someone atleast you should have confirmed whether the person is guilty or not and about those guidelines i have already read though. It was @d_g_m_2000 who said ETA i was just asking about problem in the new build nothing else.

 

[Sam Nakamura]

Had you just read what i said i never asked for eta first grt that confirmed, before blaming someone atleast you should have confirmed whether the person is guilty or not and about those guidelines i have already read though. It was @d_g_m_2000 who said ETA i was just asking about problem in the new build nothing else.

No bad blood from my side but you're technically pressuring the Dev about his new release by impatiently questioning, which is by it's nature "ETA", when asked to not do it you justify it with "I have no secondary phone like you", without even knowing if that's true besides that it's irrelevant...
Believe me, I read it all but I'm still not out to blame you, I just say you might hurt yourself and other with being impatient, let them do their job, rest assured that progress or test builds will be announced here when the Dev feels like it - now please let us stop the off topic discussion and wait for the actual release, so that we can discuss about what this thred was intended for!

Sent from my OnePlus 3T using XDA Labs

 

[sudokamikaze]

Hey guys
Battery drain fix has worked. I'll implement Spectrum support & cosmetic changes on kernel sources
And, proabably, release in the evening if everything's fine

 

[moriel5]

That sounds great.

Also, to everyone, I'm sorry I did not appear yesterday, I had fallen asleep.

I had to restart the testing a few times at the beginning, since I had to modify /system for several things, however I can say that my 25mV undervolt went without a hitch (the CPU Info overlay really helps with monitoring), however any differences were slight enought to be within the margin of error, so 25mV does not make a percievable difference.

My average temperature at idle was ~32-36°C, and under load, ~46-50°C

As to the issue I had noticed, this is probably a hardware limitation, however 720p at 60 hertz heavily taxes the CPU (overclocking CPU and GPU does not help), causing the phone to overheat (within 10 minutes I was almost at 65°C, with the only thing running being a Gamers Nexus clip running at 720p60hz via NewPipe).
The reason why I haven't seen this in a long time, is simply because I prefer to open clips with either my laptop or desktop.


I do not use GAPPs, in case anyone is asking, and I keep my running apps to a minimum (including disabling autostarts).
I utilize lightweight apps, such as Lightning Browser and MiXplorer, and I prefer WiFi over cellular (even though I have a 20GB plan (no more "unlimited" in my country since a few months ago (it used to be 20GB at normal speeds, and then unlimited at 2G speeds)), to the point that cellular is disabled most of the time (I don't have to be online all the time).


Next, I'll go back to stock voltages, update the kernel, and install the newer modded Kernel Adiutor, just to have a baseline, and then I shall undervolt by 50mV and test that.

---------- Post added at 08:46 PM ---------- Previous post was at 08:33 PM ----------

For some odd reasone, XDA Labs won't allow me to edit my post, so this is a seperate post.

Update: I'll wait for the for the kernel's new version's release, before commencing with the 50mV undervolt.

Update 2: XDA Labs seems to be drawing more system resources than it should, which is making the CPU stay between 44-48°C, even at idle (at least it does not usually go past 48°C, and the few times it had, it did not go beyond 50°C, except for once (today), since ambient temperatures were higher today, 30°C at the time I had started typing this post (and it was mid-to-late evening back then).

 

[sudokamikaze]

Just check that out!
It's almost working!

 

[sudokamikaze]

Here there is! Long-waited update!

Changelog as always:
Cleaned sources, removed unneeded commits
Battery idle drain fix(I hope that would work)
Spectrum support
Upstream changes from aosp 3.10 repos
Minor fixes
Also all wakelocks has been disabled
If you having some problems with them you can freely re-enable them back in KA
AutoSMP as default hotplug

Infromation about spectrum. Read that, please

You will have problem with switching governors if you using KA-Mod + Spectrum
Use only one of these app, do not combine them. I have already reported that problem in frap's thread

And there's an explanation: KA(Kernel-Adiutor) Changes permissions on governor's sysfs entries and spectrum can't change governos without changing permissions before. I'm not sure if this problem would appear on official KA or on other kernel tweak apps

There's possible workaround:
Disable 'Apply On boot' in CPU section and do not touch options that related to CPU frequencies & governor



Here's describe of which profile
Balanced:
Will be default state, rock solid options which I use every day

Performance:
That profile overclocks GPU, setup ASMP hotplug in best way to provide best performance
And changes governor to hellsactive
Disables FSYNC to provide best performance & ArchPower

Battery:
Smartmax governor, Lower max frequency
Decreases GPU freq to 120 MHz & Descreases RQ affinity to 1
ASMP tweaks as well

Gaming:
Default(400Mhz) GPU freq
Screenoff freq will be 91800
ASMP Hotplug tweaks to provide smoothness
And disables Arch_power

If you don't like these options or you think that you know better - Let me hear your suggestions and *may be* they would get merged

 

[bgoel4132]

Here there is! Long-waited update!

Changelog as always:
Cleaned sources, removed unneeded commits
Battery idle drain fix(I hope that would work)
Spectrum support
Upstream changes from aosp 3.10 repos
Minor fixes
Also all wakelocks has been disabled
If you having some problems with them you can freely re-enable them back in KA

Infromation about spectrum. Read that, please

You will have problem with switching governors if you using KA-Mod + Spectrum
Use only one of these app, do not combine them. I have already reported that problem in frap's thread

And there's an explanation: KA(Kernel-Adiutor) Changes permissions on governor's sysfs entries and spectrum can't change governos without changing permissions before. I'm not sure if this problem would appear on official KA or on other kernel tweak apps

Here's describe of which profile
Balanced:
Will be default state, rock solid options which I use every day

Performance:
That profile overclocks GPU, setup ASMP hotplug in best way to provide best performance
And changes governor to hellsactive
Disables FSYNC to provide best performance & ArchPower

Battery:
Smartmax governor, Lower max frequency
Decreases GPU freq to 120 MHz & Descreases RQ affinity to 1
ASMP tweaks as well

Gaming:
Default(400Mhz) GPU freq
Screenoff freq will be 91800
ASMP Hotplug tweaks to provide smoothness
And disables Arch_power

Thats fantastic @sudokamikaze, i am installing the kernel and will report you back by tomorrow.

 

[sudokamikaze]

Thats fantastic @sudokamikaze, i am installing the kernel and will report you back by tomorrow.

I will be waiting for your results

I hope fixes will work

 

[bgoel4132]

is your new build updated for unlegacy also

 

[sudokamikaze]

is your new build updated for unlegacy also

Of course

As I can see they didn't release new build which contains my binder changes(they won't work without kernel patch) yet

And yes, build is updated, when they release update I'll immediately re-upload kernel which will support that

 

[sudokamikaze]

is your new build updated for unlegacy also

Also, I have updated links, you should re-download new build
I set ASMP as default hotplug

 

[bgoel4132]

Also, I have updated links, you should re-download new build
I set ASMP as default hotplug

Presently using aosp build with fake Nexus with spectrum set as balanced and it's been going great so far hope battery stats be great too
:fingers-crossed::fingers-crossed:
Are the links updated again for aosp also.

 

[Sam Nakamura]

Are there any changes made (i.e to /system) that makes dirty flashing the ROM necessary or is fine to just flash the updated kernel? What's your recommendation?

Thanks for this update, looks very promising! :highfive:

Edit: Is there a kernel version for lineageOS 15.1? According to the OP it's (still) for Nougat only, are we meant to use this for Oreo as well? Is the description just not yet updated?

Sent from my Nexus 4 using XDA Labs

 

[sudokamikaze]

Are the links updated again for aosp also.

I always update all links