Spookcity_Kernel-N

[Spookcity]

Just a place to share your experiences with the kernel. Let me know about any bugs or problems you experience. Also share any features you may want to see included in future builds. Git repo XDA thread (Although I may create a new one for the Nougat kernel. I'm still unsure of the best route to go) Test builds will be posted here

[Oleggluk]

I'm waiting for the kernel test 7 with new security patches from hennymcc) https://forum.xda-developers.com/showpost.php?p=72437401&postcount=807

[Spookcity]

@Oleggluk Yeah, I've been talking to him about this. His work on our device is to really be commended. Where would we be without him?!I I will try to get these patches in my kernel soon. I hope it is not a big problem to do so.

[ghost]

Now that the Firefox issue has been resolved, we can start looking into the Chrome issue ;) Am I the only one who gets an Aw snap! message when trying to display a website with Chrome? It only happens after flashing this kernel. I'm using LiquidROM at the moment and I have not tried this with other ROMs, although I know someone has had this issue before.

Sent from my Samsung kminilte using FastHub

[Spookcity]

@StanNL Haha,incredible. What's funny is that I don't even use Firefox. I use Chrome dev,but haven't tried to use it due to trying to figured out the problem with FF. Either way,you are correct. There's a problem with all versions of Chrome. A strange new bug. I'll look into it.

Edit: Well,I can confirm that the Chrome issue is only with this kernel. Chrome works fine with only the patch to fix FF,ETC. So it must be a build flag or the toolchain I guess. There's not a whole lot more I've changed that would cause this. I'll try to debug it some tonight. I would really like to hear from anyone who had the fingerprint reboot problems on Lineage though. My tests seemed to indicate it's fixed,but would live to hear from someone else on this.

Edit II: As suspected it is a build flag that breaks chrome now,oddly. Shouldn't be too difficult to figure out. Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Kernel test8 fingerprints work as before, bootloop no. Firmware RR.

[Spookcity]

@Oleggluk Thank you for the feedback!

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Updated the download link for Test8 Chrome is fixed. The strict aliasing flag now breaks Chrome apparently.

[ghost]

@Spookcity Thanks! It works again!

Sent from my Samsung kminilte using FastHub

[Spookcity]

@StanNL Yes,I'm glad as well because the only browser I use is Chrome. I had just been using Firefox for test purposes and hadn't tried Chrome with the latest updates as the last thing I thought was it would be broken :D

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

I can not delete the system applications through the special software for this. I can not even edit build.prop, changes are not saved. Root magic.su, core test8, firmware RR, changed the different regimes of selinux. Is there anyone else who has such problems?

[ghost]

@Oleggluk That issue sure sounds strange. I'd say that the issue lies within the fact that your system directory was not mounted correctly, but I'm not sure

[Spookcity]

@Oleggluk Weird problem indeed. I would have to agree with @StanNL on this. I can't really think of any other reason. I don't think its an SELinux issue. I could be wrong though.

[Spookcity]

Just a little "teaser"

[Oleggluk]

@Spookcity When will we test?)

[Spookcity]

@Oleggluk Not sure yet. I'm going to probably release test9 as v1 on XDA this week if I have the time. Then I may post up a OC build on here for feedback. I have tweaked the voltages,with many thanks to DJSteve for being able to see what he did so not to destroy my phone. I've been using it set at 1.7ghz for almost 2 days now and haven't had a single issue....so far. Or maybe I release an OC build on here for feedback,then release that as v1. Can you tell I'm unsure? haha Stay tuned, maybe I'll build and let the OC kernel be tested.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity I think the version with 1.7ghz is better left as a Test. If everything goes well, you can release V1. I correctly understood, will control voltage? I've been waiting for this feature for so long. Already want to experience)

[Spookcity]

@Oleggluk I tend to agree with that. I've adjusted the voltages to (hopefully) allow the 1.7 OC to be stable. I've yet to implement the allowing of adjusting them though. Soon it will come though (I hope)

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Above we somehow discussed the error "Battery stats service no controller energy info supplied." The conversation was about the power_profiles.xml file. I was looking at the changes in the RR https://github.com/ResurrectionRemix/android_frameworks_base/commit/bf079b8f29c92669b3e677e80ab402b9b9c64453 Is it interconnected? Or is it quite another.

[Spookcity]

@Oleggluk It is possible,but I'll be honest I'm really not sure. I do tend to think this has something to do with the way ROMS implement their power profiles as opposed to being kernel related, but I also could be wrong. This is really just a guess.

Sent from my Samsung SM-G800F using FastHub

[Guntzog]

@Spookcity a flashed your test13 on RR and the battery became surprisingly poor, so damn fast drain, @Oleggluk have experienced something similar?

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@Guntzog Very strange. I don't see why this would be the case. Your battery life should actually improve,at least a little as I've tweaked and patched some things. My battery life is better with it. Either way,I've been working on the kernel a lot and there are many changes since test13. I plan to release it on XDA today or tomorrow hopefully. Then will get a test version up here with some new additions and changes.

[Oleggluk]

@Guntzog My battery is 2.5 years from the date of purchase. Works badly already. It is difficult for me to judge the expenditure of energy. I also always use the core of Spookcity and I do not know how much power is consumed on the original core. I ordered a new battery.

[Guntzog]

@Spookcity waiting for the kernel !

Sent from my Samsung SM-G800F using FastHub

[jimmy999x]

I can not install version 3.0a of your kernel, I know how to correct that, I need to make the boot image a little bigger and re compile liquidark rom, in a few days it will be ready

[Spookcity]

Hmm,interesting. Thanks for the heads up. I've only flashed this version on AOKP and AICP. I'm not sure why this issue though. I had this problem when I tried to use LZ4 compression for the kernel. I'm still looking into that. I think the boot image partition for our device is actually larger than what is in the fstab. I'm not positive though. Let me know the outcome of this though.