[KERNEL] [G800F/M/Y] Spookcity_Kernel-N (For all 7.x custom ROMS)

[elhennig]

Glad to hear all is working well. Westwood will be the default TCP congestion from the next build on. It was suppose to be on this build, but I forgot.

Edit:
Oleggluk has pointed out to me that alucard and ondemandplus do not work as they should. You can use them and they cause no issues, but they don't scale the CPU frequencies like they should. I recommend not using these until hopefully I can fix them. Alucard hotplug works properly though.

OK, I was just cautious now and tried to minimize the changes I did to the default config. Anyway with this I will try to activate alucard hotplug and see what happens

 

[Friedensfurz]

@spookcity138 I'm on your Kernel 4.0 1500mhz and I experience random reboots (about one per day). I think this has to do with voltage control as it only happens when my screen is off? Any ideas?

 

[spookcity138]

@spookcity138 I'm on your Kernel 4.0 1500mhz and I experience random reboots (about one per day). I think this has to do with voltage control as it only happens when my screen is off? Any ideas?

Hmm,interesting. Well,that's certainly no good. What CPU governor are you using? I really cant think of any specific reason why this would be happening. My only guess would be perhaps the CPU governor and/or the voltages you've selected for the lower CPU frequencies because when the screen is off the CPU should scale down.

 

[Cisencjusz]

hey, can you add suport for usb tethering in this kernel? it's working fine on stock kernel in every rom, but if i install this one (4.0) i have a lot of weird ip configuration errors, i tried to fix it for like 6h, but i couldn't do it, flashing again rom (stock kernel) was the only solution

 

[Knoose]

@spookcity138 I'm on your Kernel 4.0 1500mhz and I experience random reboots (about one per day). I think this has to do with voltage control as it only happens when my screen is off? Any ideas?

I am experiencing the same, but more than once a day. Battery drain also seems to be higher. This started with version 4, while using the same governor, zzmoove ybat. I do not know much about voltages but will play with them a bit, see if it will help

 

[spookcity138]

hey, can you add suport for usb tethering in this kernel? it's working fine on stock kernel in every rom, but if i install this one (4.0) i have a lot of weird ip configuration errors, i tried to fix it for like 6h, but i couldn't do it, flashing again rom (stock kernel) was the only solution

Hmm, I will look into this,but it may be difficult for me to track down. If USB tethering is available in the stock kernels then I don't really know. I certainly did not remove this feature. I will see what I can do though.

I am experiencing the same, but more than once a day. Battery drain also seems to be higher. This started with version 4, while using the same governor, zzmoove ybat. I do not know much about voltages but will play with them a bit, see if it will help

Are you using the 1.5 kernel or the overclocked one? I didn't tweak zzmoove,so it must be something else. Right now I'm just curious what version of the kernel you're using. Setting unstable voltages can certainly give these results. Have you messed with these already or no?

 

[Knoose]

Are you using the 1.5 kernel or the overclocked one? I didn't tweak zzmoove,so it must be something else. Right now I'm just curious what version of the kernel you're using. Setting unstable voltages can certainly give these results. Have you messed with these already or no?

I am using the 1.6 kernel, but it worked well for me on previous versions. I have not yet tweaked any voltages, i have just disabled the 200 mhz and 1600 mhz in kernel adiutor. Maybe this helps

 

[spookcity138]

I am using the 1.6 kernel, but it worked well for me on previous versions. I have not yet tweaked any voltages, i have just disabled the 200 mhz and 1600 mhz in kernel adiutor. Maybe this helps

Yeap,def helps. Let's me know that you've done nothing that should cause this. Before I start spending time looking into this, I plan to release a test build on my github hopefully this weekend. While I've done nothing that would specifically fix this issue. Perhaps by chance something new/different in this build may solve it hopefully. If not we will try to hunt down the cause. I'll post on here when I've released the next test build.

Sent from my SM-G800F using Tapatalk

 

[Knoose]

Yeap,def helps. Let's me know that you've done nothing that should cause this. Before I start spending time looking into this, I plan to release a test build on my github hopefully this weekend. While I've done nothing that would specifically fix this issue. Perhaps by chance something new/different in this build may solve it hopefully. If not we will try to hunt down the cause. I'll post on here when I've released the next test build.

Sent from my SM-G800F using Tapatalk

No rush I can work around this and it is a minor issue to me. You always provide us with good quality roms and kernels, I won't complain if something does not work for me once in a while. If you give me a heads up on your test build I will flash and see if it helps.

 

[Friedensfurz]

Hmm,interesting. Well,that's certainly no good. What CPU governor are you using? I really cant think of any specific reason why this would be happening. My only guess would be perhaps the CPU governor and/or the voltages you've selected for the lower CPU frequencies because when the screen is off the CPU should scale down.

I didn't mess with Kernel Adiutor at all, I just used it to take a look at the used frequencies. Are the standart options not stable yet? @Knoose also seems to have this problem. Anyway - thank you very much for your efforts in this kernel and all the other content you provide to our S5 Mini. There is no hurry on my side at all so take your time

 

[Knoose]

I reverted back to v3 and reset adiutor, all seems fine now. V4 still gives me problems.

 

[spookcity138]

I didn't mess with Kernel Adiutor at all, I just used it to take a look at the used frequencies. Are the standart options not stable yet? @Knoose also seems to have this problem. Anyway - thank you very much for your efforts in this kernel and all the other content you provide to our S5 Mini. There is no hurry on my side at all so take your time

The standard options should indeed be stable. It's as strange thing as I have had no issues at all. I know a few others who have not as well,but obviously some do. You are not alone in this. I really don't know why. I have some logs provided to me that I am going to have a look at when I have sometime. Hopefully this will give me some insight.

I reverted back to v3 and reset adiutor, all seems fine now. V4 still gives me problems.

Weird,as above it seems that some have issues and others do not which makes it more difficult to figure out. Again,maybe the log will show me something interesting.

 

[spookcity138]

Released a test build of the kernel. For those having issues (and anyone else) will you give it a try. Maybe by some great luck it will solve some things.
https://github.com/Spookcity/ROMS-G800F/issues/22#issuecomment-322771019

Sent from my SM-G800F using Tapatalk

 

[Knoose]

I just installed your test build. I will let you know how it goes!

 

[Friedensfurz]

Okay, I tested your Kernel 4.0a 1500mhz version but sadly it restarts my phone when I lock it and it also lights up my cpu, all 4 cores at 1500mhz and a temperature of 65°C So I switched back to stock RR kernel. Let me know it you need logs etc @spookcity138

 

[spookcity138]

Okay, I tested your Kernel 4.0a 1500mhz version but sadly it restarts my phone when I lock it and it also lights up my cpu, all 4 cores at 1500mhz and a temperature of 65°C So I switched back to stock RR kernel. Let me know it you need logs etc @spookcity138

Thanks for the feedback. I can't explain why you're having these issues though. I know Oleggluk is also running RR and has reported no such issues to me. There should be no reason for these things to happen that I can think. Did you wipe dalvik/art cache and the cache partition after flashing? Do you have kernel adiutor or similar set to apply settings on boot? If so try to disable all of that before flashing the test build. I will gladly look over your logs if you are able to grab them. I'm not sure it will help me much,but perhaps.

 

[Friedensfurz]

Thanks for the feedback. I can't explain why you're having these issues though. I know Oleggluk is also running RR and has reported no such issues to me. There should be no reason for these things to happen that I can think. Did you wipe dalvik/art cache and the cache partition after flashing? Do you have kernel adiutor or similar set to apply settings on boot? If so try to disable all of that before flashing the test build. I will gladly look over your logs if you are able to grab them. I'm not sure it will help me much,but perhaps.

Thanks for the answer, I wiped system, dalvik and cache, flashed RR, Magisk 13.3 and finally your kernel build. Maybe it helps if I uninstall Kernel Adiutor, but I can't try because I'm on the move at the moment

 

[Knoose]

Tried the 4a oc kernel for one day now, all seems fine except that it hangs when i turn off the phone. I need to manually remove the battery to turn it off. But hey, no more reboots! :victory:

 

[spookcity138]

Thanks for the answer, I wiped system, dalvik and cache, flashed RR, Magisk 13.3 and finally your kernel build. Maybe it helps if I uninstall Kernel Adiutor, but I can't try because I'm on the move at the moment

You shouldn't need to uninstall kernel adiutor. I have come to realize that what is stable to some is not for others. I know part of this is due to how the user uses their phone (apps etc) but there is something else to it that I'm currently unsure of. It's all very strange to me. I see no reason why you should be having these issues.

Tried the 4a oc kernel for one day now, all seems fine except that it hangs when i turn off the phone. I need to manually remove the battery to turn it off. But hey, no more reboots! :victory:

Again,as above another strange issue that I can't reproduce. Interestingly,I do now have random reboots. Just to show how very strange things are. I was assuming that you would as well (and others) but apparently not..or not as often as me. I've had a few a day. I think this may be due to a HZ issue that I implemented,but again not everyone has this issue. It's like the whole 1.7 overclock issue that was on my GitHub a month or so ago..It's all just very confusing. I will continue to investigate.

 

[Evos11]

Can somebody use magisk hide with this kernel?