Test Builds #6

[Spookcity]

A continuation of #10, #18, #19, #20 and #21

[Spookcity]

Spookcity_Kernel-N - Test v4.0a

Changes:

• Removed ROW I/O scheduler ( until I can hopefully fix it)
• Added I/O scheduler switcher by sultanxda (changes the I/O scheduler for a specified request queue to Noop when the screen turns off in order to improve power consumption while the screen is off
• Added PIE net scheduler
• Added support for USB keyboards ( You need This app to use it.
• Properly enabled faux123's powersuspend v2.5
• Added dynamic fsync
• Added optimization flags for the GPU
• Enabled AIO
• Fixed alucard governor (hopefully)
• Fixed ondemandplus governor (hopefully)
• Fixed bluactive governor (hopefully)
• Added intelliactive governor (by faux123)
• Added intelliplug hotplug driver (by faux123)
• Added thunderplug hotplug driver (by varun.chitre15)
• Added Dynamic management of dirty page writebacks (allows to have two different intervals for dirty page writebacks and to dynamically manage them when the system has been resumed (it's active) or when has been suspended - Not adjustable via garaks kernel adiutor app)

Other things of note

• lib/int_sqrt.c: optimize square root algorithm

• af_unix: speedup /proc/net/unix

• wireless - bcmdhd - reduce scan dwell time to reduce power usage

• bcmdhd reduce wakelocks

• readahead: make context readahead more conservative

• block/partitions: optimize memory allocation in check_partition()

• power: make sync on suspend optional

• block: bfq-iosched: tuning for SSD (thanks to anarkia1976)

• Please give feedback Here and NOT in the XDA thread for test builds. Otherwise it will be come very confusing. Thanks!

Download Spookcity_Kernel-N_v4.0a
Download Spookcity_Kernel-N_v4.0a-1500mhz (untested)

[HaxXorHardy]

hi @Spookcity
i installed Beanstalk rom(newest)
then spookcit-kernel-4.0a
then gapps nano
then superSU
one after one with TWRP
Fresh install and it reboots after 3 mins of use.
is this correct sequence?
idk what is the fault :(

now i tried a fresh install:
First beanstalk rom
then the kernel.
it is still the same problem

here is the log from the second try.
log.txt
log1.txt

[Spookcity]

@HaxXorHardy Hmm,interesting. I'll try to have a look at the log when I'm home if I have some time. I've just been rather busy. The sequence your flashing sounds fine. I can only offer a quick suggestion right now,and that's to try and eliminate the cause one by one. So,only flash the ROM. See how it goes. Then maybe flash gapps and so on. You may be able to at least figure out the cause like that.

Sent from my Samsung SM-G800F using FastHub

[HaxXorHardy]

It is after flashing the kernel. But idk what the reason is. I use the newest twrp and only flashed Rom and kernel like the logs in my first comment they are only Rom and kernel.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@HaxXorHardy Just had a quick look at your logs. Sorry I was busy yesterday..but is/was your device encrypted? I only ask because this is the only thing that really stood out to me in the logs
"Cryptfs : Cannot remove dm-crypt device"

[HaxXorHardy]

@Spookcity Yes it was encripted but i flashed the Stock rom cause i got a realy strange error:

after press "reset Phone" it loads twrp and trys to delete data cache etc(default settings)
the only posibility was odin mode cause twrp was not able to mount the partitions.

Do you think that is maybe the fault and how can i fix it?

[Spookcity]

@HaxXorHardy I do think it has something to do with it yes. If it is fully due to that I'm unsure.
I'm trying to think of a solution that you haven't already tried and don't really know off the top of my head. I'll have to give it some thought. Perhaps someone else has an idea?

Sent from my Samsung SM-G800F using FastHub

[HaxXorHardy]

@Spookcity i dont know how this works, but maybe repartitioning vor deleting this thingy is an Option? I have not tryed any solution, cause I never had any problems wit this. Hmm maybe encript end decript again?

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@HaxXorHardy I will be honest,I really am very unsure and don't want to give you bad advice. It's a strange issue. Hopefully someone else has some clue because I really don't. If not,maybe post the issue on XDA? Maybe someone there can help. I've never messed with encryption on a phone in any way, so yeah I'm not very qualified to answer this.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Hey can anyone test the intelliactive CPU governor for awhile? I was getting random reboots with the last test version of my kernel. I had not messed with voltages or much else. I have since switch CPU governors and its yet to happen. Just curious if anyone can confirm this. Thanks!

[Mikahlo]

@Spookcity I did just that, see my repo for logs with intelliactive. Do you need a dmesg or modem log? I had the random reboot once with zzmove and profile 4 also. The logs are kind of useless I guess. Isn't there a way to get a more precise log of what happened when the os crashed?

[Spookcity]

@Mikahlo Thank you very much! I will have a look hopefully tomorrow. I've just been lacking time recently to look into this further. I've also grabbed a log from my reboot with intelliactive. Again,kernel panic. No surprise. It might have to do with me changing the HZ to 300 from 100...or a suspend thing. Intelliactive def seems to be the cause though. I've not had a single reboot until using it.

As far as better logs. I'm really not sure honestly. I've applied some patches to make the kernel log easier to interpret, but I'm really not sure. I know if I was able to interpret the stack dump it'd be a lot easier,but I need to learn this. I'm still really new to Android stuff really. Most of my knowledge is just carry over from my love of Linux...and I've obviously learned some android,but still,long way to go. Thanks again for the logs.

Edit:
@Mikahlo Had sometime to look over your logs. The logcat showed nothing that really stood out to me.
Your kernel log again shows a kernel panic. Hopefully I will have some time this week to try to figure out how to properly interpret the backtrace. Then I will know the exact cause. From my understanding though it is related to a timer problem.

Sent from my Samsung SM-G800F using FastHub

[jimmy999x]

Good evening everyone, I have not been around for a long time, I have been busy, I have a big question, I have seen that bliss rom and lineageos already started working with version 8.0, when they think that it is ready for our device? I speak of the source code, I am anxious to test android 8.0

[Spookcity]

@jimmy999x Yeah,I noticed this as well. I had a look at SlimROMS 8.0 manifest and at this point they are only pulling the AOSP repo's. Same with Lineage. They are pulling some of their own,but they are all 14.1. So until this changes I see no point in even attempting a build....which I believe is going to be full of problems for our device sadly :(

[jimmy999x]

why? Some incompatibilities?

[Spookcity]

@jimmy999x Well,with every new release there are changes that will nearly certainly require at least some changes to the device trees. From what I've read about Android O there are some rather significant changes. This could be a challenge. Tobias aka hennymcc is the one who has fixed and created the majority of the fixes and patches for the trees. It's not an easy thing to do and requires lots of debugging.

The only real way to go about it if you don't know any programming is to just build. Get an error. Try to fix it and so on. Could be very time consuming.

Sent from my Samsung SM-G800F using FastHub

[jimmy999x]

Unfortunately not being programmed in android, but if I can collaborate with a server so that they can perform their tests and others, it has good compilation times and also internet connection

[Spookcity]

@jimmy999x Thanks,that is certainly appreciated and could be useful. I'm not sure. For myself I am still in the very beginnings of learning java and cpp,so it would probably be very difficult..or at least exceptionally time consuming for me to do it. Hopefully hennymcc has plans to work on it at some point. I'm not sure,but I would also understand if he doesn't as it is really time consuming.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Spookcity_Kernel-N - Test v4.0b

This is attempt number one to try to solve some of these random reboots that some,myself included,are experiencing with the last build. Apologies for taking so long to try and get this resolved. I've just been very busy.Hopefully this will have some effect as I'm not too sure what step 2 will be at this point. I guess looking into suspend related things.

Changes

• Reverted a few HZ related commits

Download
Spookcity_Kernel-N_v4.0b
Spookcity_Kernel-N_v4.0b-1500mhz

[hard-sat]

RR-N-v5.8.4-20170813-kminilte-Unofficial
Spookcity_Kernel-N_v4.0b-1500mhz (v3.0a, v4.0a, v4.0b)
kerneladiutor-update-Quark.44.BHB27-Mod or Kernel+Adiutor+v0.9.71.1P(239)
new frequency, it is impossible to change tension of frequencies ((
v3.0 have no new frequency

I thank

[Spookcity]

@hard-sat Hmm, I have no clue why this would be. No one else has reported this to me and I have no issues. I have used a few different versions of kernel adiutor as well. I'm not sure what to say. I will try the 1500MHZ version and see. I have not tested these. Perhaps I messed something up.

Edit:
Also,that bizarre frequency seems to be "normal" I'm not sure why,but I have had that a time or two as well. Something I'll look into also.

[hard-sat]

and v.3 perfectly works!
something is badly changed in the version of century v.3a and, as a result, the subsequent versions.
I thank

[Spookcity]

@hard-sat You are right. It's only the 1500MHZ version,but changing voltages indeed does not work with version 4.0b..Probably the last few versions as well. I obviously messed something up. I will try to fix it when I have some time.

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

@Spookcity No random reboots with Spookcity_Kernel-N - Test v4.0b. I guess you reverted the correct commits. I didn't mess with kernel-adiutor at all. So I was using the default settings. The battery lifetime is great like the previous versions. I will try other governors the next days and hope for the best :)

[Spookcity]

@Mikahlo Great news and many thanks for the feedback! Hopefully this will be behind me now so I can release a stable v5.0 on XDA and work on other test builds to release on here.

Sent from my Samsung SM-G800F using FastHub

[hard-sat]

Spookcity, THANKS for Spookcity_Kernel-N_v5.0-1500, everything perfectly works and tension changes))
and it is possible to make FM-radio also? worked on the Android 4... ))
I thank))

[Spookcity]

@hard-sat Glad to hear the voltage control is indeed fixed. As far as FM radio. A month or more ago I tried very hard to figure this out. I even downloaded the KK kernel sources to try to build the module.I tried a few different radio apps,but none would work. I have to say I think FM radio for our device is a lost cause.

Sent from my Samsung SM-G800F using FastHub

[hard-sat]

it is a pity, I thank))

[Spookcity]

@hard-sat I agree,it would be nice. I'm just not real sure what else I can try. Perhaps if I have some free time I will revisit it. Maybe I can think of another idea.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity There is nothing useful for Exynos processors to markup memory.
The only phrase with a mention is this:
"Users of smartphones based on Exynos processors are less fortunate - they will have to develop a kernel with already re-allocated memory."
And I also looked in Titanium Backup, that in the system section 2.11gb and freely only 1.37gb. Internal memory + media 12.7gb. We have nothing to increase). In general, stupid is an idea.

[Spookcity]

@Oleggluk Haha.ok. Thanks for the info though. It was an interesting idea...I suppose for other phones. It's something I had not thought of before.

[Oleggluk]

@Spookcity One fat minus in AEX is. I just can not install ViperFx. Swears at not working / not suitable BusyBox. I installed different versions of BusyBox in different sections and different ways. I installed ViperFx in many ways, from the usual apk to installing exclusive archives through twrp. Does not want to install / run the driver ((. Is this a common AEX problem or only an optimized version?

[Spookcity]

@Oleggluk Interesting. I always use viper as well,but haven't installed it recently as I've been jumping from ROM to ROM. I'm sure I've installed it on AEX before and I don't see why it would be an issue... On the "normal" version or the optimized version. I will try to install it later and see if I can figure out what the problem might be..Oh,you do mean Viper4Android right? Or is this something else?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Yes, I'm talking about Viper4Android)
I've never had problems with it on other firmware before.
I will wait for results.

[Spookcity]

@Oleggluk OK,thanks. That would indeed be an issue for me as well cause I use it too. Will report back later today with my findings.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@Oleggluk OK,I had some time.. You are correct it will not install saying a busybox error. I thought that I may have messed something up with my optimized version of AEX,so I tried the standard version. Same error. I am really unsure what the deal is. I also tried a few different versions of busybox without success. There is also a Magisk module for viper,but I kept getting a "process error" when trying to download and install. I know that I installed it on AEX before,but more than likely an older release. There has to be some fix as this would be a deal breaker for me. I will try to figure it out whenever I have some time.

[Oleggluk]

@Spookcity Ok. I will know that this is not only my problem. I already broke my head with this. I hope this can be fixed.

[Spookcity]

@Oleggluk

OK, I got it working. I forgot,I always use A.R.I.S.E.
This will install V4A and the driver. The thread is kinda a mess and its not the easiest to install as you need an arise.prop so it knows what to install. Plus there are many versions. I only ever install the core and viper. I'm not sure of another way right now. If you want to install it and can't figure it out I'll post my prop and such later when I'm home.

Edit:
I should also mention that Viper does not process unless you set FX compatible mode to compatible in V4A settings.It's always been this way for me with ARISE. Not sure why,but it doesn't seem to effect anything.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity There, the devil himself will break his leg. I need help). Wow! 300MB. I did not understand, are these modules for Magisk? I refused the Magisk modules, because after the activation of any module, the ability to edit the system and programs working with the system is limited.

[Spookcity]

@Oleggluk I think there is a magisk module,but I don't use that. I think the 300mb is for a full install. Could be wrong though,but there are many possible things to install. I install core,viper and viper profiles only. It really is a nice sound mod,just a bit confusing. To make it even more exciting I you need to dirty flash your ROM again. Then flash ARISE. I will post my arise.prop along with the version I installed. Give me a few.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@Oleggluk Ok,download This file and place it in the root of your internal storage. This will only install the core and V4A and V4A profiles. I installed the latest build from Here "ARISE+Magnum+Opus+20170918+Stock+Edition.zip" The zip can go anywhere on your phone,but it will look for the arise.prop in your internal storage. Then you will need to dirty flash your ROM then you can flash ARISE and all should be good. Just remember to set the FX mode to compatible.

The arise.prop basically just tells the installer what to installer. You can obviously open it up and have a look and edit things if you want more. I used to install a few more things as well,but couldnt remember what as its been awhile,so I just went mininal.

[Oleggluk]

@Spookcity God, how is it all difficult, I already got a headache)). Thank you! without you I would never understand.

[Spookcity]

@Oleggluk Hah,you're most welcome. The thing with ARISE is that the XDA thread is more confusing than anything. It is really not layed out very well at all and then people keep posting different versions on every page. Its a mess. Let me know if you need more help. I am glad to try.

[Oleggluk]

@Spookcity Oh yeah! working! everything is super! and profiles are interesting. Generally elegant! Thank you!!!

[Spookcity]

@Oleggluk Great! Glad to hear. I've used ARISE for awhile now..off and on and really like it. Always glad
when I'm able to help out as well

[Oleggluk]

@Spookcity In the theme of Los14.1 there was today an assembly with some patch: "Build contains latest wpa_supplicant patches." What is this patch? Too I want))

[Spookcity]

@Oleggluk Hmm,I haven't read anything about this. I'm unsure what that's all about. I'll have to do a bit of research. I would have to assume its a security patch as I think the main purpose of the wpa_supplicant is to control keys and other things related to the WiFi driver.
What else the patch would be for I've no idea.

Sent from my Samsung SM-G800F using FastHub

[vonico]

Hey @Spookcity
I just saw there is a new Oreo branch in AEX's github. Do you think you will have time this week to look into it and possibly build a test ROM? I'm excited to see this ROM being updated :)

[Spookcity]

@vonico I hope so. It is in my plans to try to build this week or over the weekend. Not sure how easy or hard it may be. I will post it here first,so stay tuned!

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

At AEKS-4.6_UBERTC8.X-DTC5.0, one thing annoys me. For security purposes, the "install" button is not active in this firmware when there is a filter on top of the screen or any information is displayed on top of all windows. I rebuilt PackageInstaller.apk and disabled this protection. I did it for myself, but it's still possible for somebody else to interfere. Download and replace PackageInstaller.apk https://yadi.sk/d/0CnumF-23NqSsz by the system / priv-app / PackageInstaller (Set File Permission (644) "Г")
Just in case, save the original file.

[Spookcity]

@Oleggluk That's fantastic! Thank you! I will give this a go.

Update:
It works great. Good job and thanks again @Oleggluk

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

Someone uses a fingerprint. I found this module "Fingerprint Scanner Booster" for magisk. It increases the priority of the fingerprint process in the system. Hah, maybe it's a coincidence, but for the whole day I did not have any problems with the fingerprint, it works great. I would like to have someone else try it, especially if someone has trouble working on a fingerprint. To see if it really works or not.
@Spookcity If this module really helps in the work of a fingerprint, is it possible to add it not as a module, but at the system level in the new firmware builds? There it is written what code it uses.
https://forum.xda-developers.com/apps/magisk/module-fingerprint-scanner-booster-t3688637

[Spookcity]

@Oleggluk That's a nice find! I don't use the fingerprint scanner so I can't really test...or at least I wouldn't notice a difference if I did.
After just a quick glance at the link you posted about the module it seems as if this could be implemented in the kernel. I'll have to read through that a bit more though.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

I've update my kernel on XDA to v6.0 (same as 5.1) Hopefully over the next few weeks I have the time to look into adding ZRAM,possibly implementing the fingerprint boost that @Oleggluk has found,along with other that ideas I have.

Also,lets continue this over Here