[10][KERNEL][06.12.2019] Kirisakura-Q 10.1.0 [3.18.140]

[WhiteEVO]

Ah I gotcha, I don't do much besides a rom, kernel and v4a+Dolby nowadays, which could also lend to the fact that my phone is much more stable than my previous phones haha

Same here, I don't modify the kernel at all, running PN.

 

[Amritttt]

i am currently on PA 7.2 (aospa) and battery life was terrible after flashing kirisakura nonoc kernel battery life has really improved governor is set to sched.

 

[kkeith]

Same here, I don't modify the kernel at all, running PN.

I only modified
zram to 2048kb
swappiness to 40
Zram to lz4
Dirty ratio to 40
Dirty background ratio to 10
Overcommit to 35
I/O scheduler to maple
Read ahead to 2048kb
And of course turned on the audio high performance mode and sdcardfs

I've had it like this ever since I first downloaded kirisakura way back at the beginning and never had a problem, thing runs buttery smooth, no lag anywhere no scrolling issues and no random reboots, and to top it off my battery life is as good as it ever was. I guess I do a touch more than just install as is. And tbh after installing harmony I don't think I'll OC this phone again, I didn't notice a difference in fluidity going back to non-oc.

Edit: I think a couple of those settings I just recently stole from another post somewhere around here when I updated to harmony

Sent from my Pixel XL using Tapatalk

 

[WhiteEVO]

I only modified
zram to 2048kb
swappiness to 40
Zram to lz4
Dirty ratio to 40
Dirty background ratio to 10
Overcommit to 35
I/O scheduler to maple
Read ahead to 2048kb
And of course turned on the audio high performance mode and sdcardfs

I've had it like this ever since I first downloaded kirisakura way back at the beginning and never had a problem, thing runs buttery smooth, no lag anywhere no scrolling issues and no random reboots, and to top it off my battery life is as good as it ever was. I guess I do a touch more than just install as is. And tbh after installing harmony I don't think I'll OC this phone again, I didn't notice a difference in fluidity going back to non-oc.

Edit: I think a couple of those settings I just recently stole from another post somewhere around here when I updated to harmony

How do you turn on audio high performance?

 

[kkeith]

How do you turn on audio high performance?

Under misc in ex kernel manager

Sent from my Pixel XL using Tapatalk

 

[bobbarker2]

I feel like I typed this already but it didn't post...

Anywho, had one random reboot to boot animation, tried to cat the log but it was empty.. on latest PN.

I think the reason we're saying a lot of variance instability is due to ROM interactions. I'm still on June images + 1.40 was unusable for me then Harmony fixed it and then now a hiccup or two with the latest Harmony.

I can also confirm though that auto brightness does not work anymore with the latest PN build and this kernel. That seems Io have been broken since 1.36.

---------- Post added at 05:00 AM ---------- Previous post was at 04:52 AM ----------

I only modified
zram to 2048kb
swappiness to 40
Zram to lz4
Dirty ratio to 40
Dirty background ratio to 10
Overcommit to 35
I/O scheduler to maple
Read ahead to 2048kb
And of course turned on the audio high performance mode and sdcardfs

Uh.. I don't think the word only belongs in there haha. You're modifying some key values that dictate the kernels and memory management's behavior

And not to be a critic but your settings don't make a whole lot of sense. What is 2 megabytes of compressed Ram going to do? You might as well just turn it off and save the CPU Cycles. And you're skewing the kernel to page more while decreasing overcommit. It's self defeating.

 

[kkeith]

Typoed on that, supposed to be mb, was at work, I mostly just try out settings that I see other people post and test them out and see if they help. As I was writing it it sure send to get long haha, used to only have swappiness at 40 and zram at 2048mb, sdcardfs and 2048 readahead.
Do you have some suggestions that would be better to try for the dirty ratios, swappiness and overcommit? I will say I did notice a difference when I changed the over commit and dirty ratios to those I found.

I initially meant I don't see much with my phone nowadays, not specifically the kernel... But with lack of attention and a quick minute to reply to a post I didn't pay attention to my last post that he responded to as well haha
Sent from my Pixel XL using Tapatalk

 

[bobbarker2]

Typoed on that, supposed to be mb, was at work, I mostly just try out settings that I see other people post and test them out and see if they help. As I was writing it it sure send to get long haha, used to only have swappiness at 40 and zram at 2048mb, sdcardfs and 2048 readahead.
Do you have some suggestions that would be better to try for the dirty ratios, swappiness and overcommit? I will say I did notice a difference when I changed the over commit and dirty ratios to those I found.

I initially meant I don't see much with my phone nowadays, not specifically the kernel... But with lack of attention and a quick minute to reply to a post I didn't pay attention to my last post that he responded to as well haha
Sent from my Pixel XL using Tapatalk

gotcha. id suggest going back to stock settings for swappiness and dirty ratios. For Android (and the core of Linux) unused RAM is wasted RAM. Its a very different paradigm than Windows. You want the kernel to do as little paging as possible and keep most used/relevant data resident in memory. I almost never have activities destroyed, even coming back to some apps a day later.

And I dont think you are using 2gb allocated for ZRAM.. thats 1/2 the total RAM of the device. 512mb is stock and a good value based on 4GB of RAM. If you had 1/2 your ram compressed, you would see some major negative side-effects.

 

[kkeith]

gotcha. id suggest going back to stock settings for swappiness and dirty ratios. For Android (and the core of Linux) unused RAM is wasted RAM. Its a very different paradigm than Windows. You want the kernel to do as little paging as possible and keep most used/relevant data resident in memory. I almost never have activities destroyed, even coming back to some apps a day later.

And I dont think you are using 2gb allocated for ZRAM.. thats 1/2 the total RAM of the device. 512mb is stock and a good value based on 4GB of RAM. If you had 1/2 your ram compressed, you would see some major negative side-effects.

Ok I set them back to defaults, I do have 2048mb allocated to my zram and have had it that way for a very long time now with no issues, I'll set it down to 512mb and try that, I do remember picking 2048mbs based on some reading I'd done, but wouldn't be the first nor last time I had found misinformation on the internet haha

Edit: I guess clicking the button to the right of the options in ex kernel and rebooting doesn't set them back to defaults, does anyone have the default settings for the dirty ratio, dirty background ratio, and over commit ratios by chance?

Sent from my Pixel XL using Tapatalk

 

[bobbarker2]

Ok I set them back to defaults, I do have 2048mb allocated to my zram and have had it that way for a very long time now with no issues, I'll set it down to 512mb and try that, I do remember picking 2048mbs based on some reading I'd done, but wouldn't be the first nor last time I had found misinformation on the internet haha

Edit: I guess clicking the button to the right of the options in ex kernel and rebooting doesn't set them back to defaults, does anyone have the default settings for the dirty ratio, dirty background ratio, and over commit ratios by chance?

Sent from my Pixel XL using Tapatalk

Clear data on ex kernel manager and reboot. Should get you back to stock. If not just reflash, just make sure ex km has its data cleared.

@Freak07 I had another weird reboot to boot animation again and like last time the ramdump was empty. However, I was able to play around with Franco's kernel and got it to do the same thing so it isn't any issue specific to your kernel.. or its a merge that you both took. But much greater likelihood of some weirdness going on with PN back in June and kernels being updated for July. Will be flashing factory image clean and your latest kernel to give an accurate test. This isn't really a bug report since I have no data to submit, but more of a "eh - everything's probably alright kernel side".
I wonder if Beans is going to skip a July build and just do August since there's only a bit over a week left in the month..

 

[kkeith]

gotcha. id suggest going back to stock settings for swappiness and dirty ratios. For Android (and the core of Linux) unused RAM is wasted RAM. Its a very different paradigm than Windows. You want the kernel to do as little paging as possible and keep most used/relevant data resident in memory. I almost never have activities destroyed, even coming back to some apps a day later.

And I dont think you are using 2gb allocated for ZRAM.. thats 1/2 the total RAM of the device. 512mb is stock and a good value based on 4GB of RAM. If you had 1/2 your ram compressed, you would see some major negative side-effects.

Well after a couple days of using the default settings I will say the phone is actually a little quicker, battery life has certainly improved, however the slight choppiness when scrolling every once in a while had also come back. Not a big issue or anything, definitely worth the added battery life haha. Just thought I'd give you an update and let you know you were right [emoji6]

Sent from my Pixel XL using Tapatalk

 

[bobbarker2]

Well after a couple days of using the default settings I will say the phone is actually a little quicker, battery life has certainly improved, however the slight choppiness when scrolling every once in a while had also come back. Not a big issue or anything, definitely worth the added battery life haha. Just thought I'd give you an update and let you know you were right [emoji6]

Sent from my Pixel XL using Tapatalk

Glad my advice helped.

 

[Freak07]

Update

Harmony is now upstreamed to 3.18.63


Download is here: https://www.androidfilehost.com/?fid=673368273298974775

 

[Freak07]

OP is updated and heavily simplified.
New kernel is Kirisakura-Harmony upstreamed to 3.18.63

 

[liam_davenport]

Thanks for all your work bro :good:

 

[mazubo]

Are there any issues with flashing this kernel over stock room with another developers kernel?

Edit: flashed over another developers kernel as instructed in OP and all is well, thank you !

On another note; can someone explain the different io schedulers? I appreciate the choices, but don't know which one to choose!

 

[mazubo]

Just tried watching a YouTube video. No audio is playing.. I previously played a bit with mic gain in Sound settings using ex manager, however I reset them to default. I now get fizzing, pooping sounds even while doing other things besides watching YouTube videos.. what can I try to do to fix this?

 

[Freak07]

Just tried watching a YouTube video. No audio is playing.. I previously played a bit with mic gain in Sound settings using ex manager, however I reset them to default. I now get fizzing, pooping sounds even while doing other things besides watching YouTube videos.. what can I try to do to fix this?

Which kernel are you on? The new harmony?

I just watched a youtube video. Sound is playing fine for me.

 

[veetoe]

I haven't been able to get harmony to work. Im on the july purenexus build now, same issues on june. I've tried .61 and .63. I get some really weird issues, screen not waking, or takes like 20 seconds to wake. I also noticed that the camera was only showing a black screen. Sometimes it seems like android won't load all the way upon boot and then it will reboot straight to the bouncing dots and never boot from there, hard reset required. I've let it sit for well over 10 minutes too like previously mentioned, and it doesnt get any better. I use liveboot and when i flash harmony it shows a bunch of weird errors in the log during boot that don't show up on 0.17.
I've tried numerous times and the ONLY time harmony seemed to operate normally was after first flashing the july purenexus build, coming from the stock purenexus kernel. Screen would wake fine and right away. So I rebooted to twrp to flash the schedtune900 zip and when it booted back into the system it had the same previous symptoms, screen not waking etc.
I even flashed a twrp backup of JUST before i flashed harmony when it worked, and I couldn't get it to work again even after the backup restore.
I would love to get this to work properly, any ideas? Thanks

 

[Freak07]

I haven't been able to get harmony to work. Im on the july purenexus build now, same issues on june. I've tried .61 and .63. I get some really weird issues, screen not waking, or takes like 20 seconds to wake. I also noticed that the camera was only showing a black screen. Sometimes it seems like android won't load all the way upon boot and then it will reboot straight to the bouncing dots and never boot from there, hard reset required. I've let it sit for well over 10 minutes too like previously mentioned, and it doesnt get any better. I use liveboot and when i flash harmony it shows a bunch of weird errors in the log during boot that don't show up on 0.17.
I've tried numerous times and the ONLY time harmony seemed to operate normally was after first flashing the july purenexus build, coming from the stock purenexus kernel. Screen would wake fine and right away. So I rebooted to twrp to flash the schedtune900 zip and when it booted back into the system it had the same previous symptoms, screen not waking etc.
I even flashed a twrp backup of JUST before i flashed harmony when it worked, and I couldn't get it to work again even after the backup restore.
I would love to get this to work properly, any ideas? Thanks

Don’t flash the schedtunezip. The power Hal changed probably in the new builds and is not compatible. :good:

It isn’t recommended to flash the schedtunezip with the new EAS machinery.