Test Builds #5

[Spookcity]

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

[Spookcity]

Spookcity_Kernel-N - 3.0+voltage_control

IMPORTANT- More than ever do a FULL backup before flashing this version. Read on and I will explain why.

This is the same as version 3.0. The only difference is the added voltage control. The maximum possible voltage is 1500mV. The minimum is 600mV. I have found 1475mV and 650mV to be the highest and lowest I am able to use and have my phone stay stable. Your voltages may vary. You will certainly experience lockups/freezing issues if you select unstable voltages. This will require you pulling the battery. This is not a problem with the kernel. I HIGHLY suggest slowly moving the voltages up or down (+/-25) Letting it "settle in" for a few minutes and then adjusting more.On to why I recommend a backup..

I have had my phone freeze/lockup multiple times due to me experimenting with voltages. This is to be expected. However,I once had this happen,so I pulled my battery,it booted fine,but some settings had been reset. This has been talked about and is also no big deal. When I went into settings to restore some things I noticed a few very strange things.

1. My home button stopped working
2. I clicked on developer options and nothing was there except a message saying "this user cannot access this" or similar.

I reinstalled my ROM and all was good again,but I should have tried to boot into recovery and do a few other things before I just re flashed the ROM to see if they worked. A wipe of dalvik and cache or just dirty flashing the ROM may have solved this,but I don't know. Either way,be aware of this. I can not explain why this happened as its very strange and it only happened once. Download v3.0+voltage_control v3.0+voltage_control-1500mhz (Untested)

[Oleggluk]

@Spookcity RR works great. Thank you!

Ahaha)) this dangerous thing. Three times already rebooted and once completely stopped). I like))

[Spookcity]

@Oleggluk Great! I'm glad to hear that. Please keep me updated on your findings. Do expect lockups/freezes if you select unstable voltages though. Hopefully nothing more than that. I've had my share,but have been running the same voltages now for 2 days and so far so good. The CPU governor you choose also seems to play a fairly big part in the stability of certain voltages.

Edit: Hah,yes this can definitely happen. I've needed to pull my battery many times just playing around with the voltages,but all but that one time I mentioned in the other post all was good after a reboot. There is certainly no reason anything horrible should happen. Just freezes and such. But as we also know..My phone is apparently different hah

Edit II: I've been running alucard along with alucard hotplug for 2 days now with these voltages ( really just trying to test out the max/min values) 1475 1400 1325 1250 1100 1050 950 900 850 800 775 725 700 650 650

These same voltages were unstable with zzmoove. Expect your CPU temp to rise as you raise the voltages though obviously. I've seen mine rise a fair bit with those settings.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity I'm using the standard interactive now. Once 8 already had a reboot)), but I continue to look for the optimal values.

[Spookcity]

@Oleggluk Yeah,that's the key,just finding the values that are stable and close enough to what you're looking for. It took me awhile of messing around and many reboots/freezes to find these as well. I should also mention that I don't play any graphic intensive games. Otherwise I'd highly recommend not over-volting as much as I have done. The CPU temps would get too high.

Good luck finding the optimal voltage values.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity I'm not afraid of overheating, on the contrary I put the smallest possible values to conserve battery power. I can not understand how hotplug works. I installed the minimum number of kernels online 3 (1 core immediately turned off), the maximum I set to 4. I understand that if there is a heavy load, then the fourth core will turn on? I included games, heavy applications, the processor runs on 3 cores with a frequency of 1600, but the 4 core never turns on.

[Spookcity]

@Oleggluk Yeah,then overheating shouldn't be an issue. I'll be honest I am also somewhat confused by alucard hotplug. It's the first I've ever messed with hotplug governors though,but its behavior is somewhat strange to me. I'm going to try to add a few more hotplug governors in the near future. Perhaps some behave a bit differently.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Hmm. Interesting. In the developer parameters there is an item "show information about the processor". So, Indications kernel adiutor and the readings on the screen are very different. To whom to trust more?

[Spookcity]

@Oleggluk That is interesting. Are you able to post a screenshot of what that says?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

For example, if the Kernel Adiutor shows a stable frequency of 900, then the system indicator remains at 200. they show completely different information.
I removed the screenshot so did not interfere

[Spookcity]

@Oleggluk Ahh,OK. That's is what you're talking about. I for some reason was thinking it was something specific to RR. I will try this as well and see if I can tell what's happening.

Edit: OK, after just a quick look at this I think its due to different refresh rates. I believe kernel adiutor just refreshes at a different time,so I think they are both accurate,but my guess is that the developer options overlay refreshes faster. I'll investigate further though.

Ok,Well maybe not. It is interesting.

Edit: OK,after messing around and staring at things for awhile my only guess is that it does have to do with refresh rates. I believe they are both accurate ,but one is late reporting,so it is very confusing to compare.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity I thought about the fact that the update time is different. But if you watch longer, you can see that the values are really different.

[jimmy999x]

I have a great doubt, I love xosp, it seems to me one of the best roms for the device, but I have a problem, it has a battery drain, I installed the kernel 3.0 of @Spookcity, to change the cpu governors it is necessary to check the "apply on Boot "? Or do I simply choose the options and close the application? (I speak of Kernel Adiutor)

[Spookcity]

@Oleggluk It's a strange thing and its difficult to compare. Especially if 1 is off by say 2+ seconds. Then the values are going to look very different. I don't know for sure though. I was using pegasusq governor and I kinda could see similarities. I mean it didn't look totally different, but yeah this is just a guess as I really don't know. I will look more into it though as it is interesting.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@jimmy999x Yes,if you want to keep the particular governor after rebooting ( without manually changing it) then click apply on boot. The governor you select is activated once you select it though. Just that it'll be reset after rebooting if you don't tick that.

@Oleggluk I just compared kernel adiutor and 3c Toolbox's CPU frequencies. They are different as well. I don't know what else it'd be besides refresh rates at this point.

Sent from my Samsung SM-G800F using FastHub

[jimmy999x]

What configuration do you recommend? What I most want is to improve the battery life

[Mikahlo]

@jimmy999x I read in the xosp telegram group that xosp doesn't get an android o version, so probably this project gets discontinued. @Spookcity I'm joining the test team going for undervolting and overall battery lifetime.

[jimmy999x]

@Mikahlo I know, I read it on your g +, a real shame, but I'll use xosp to the end or find some rom compatible with am3d (even though I think I'm about to find the cause of the incompatibility) I am beginning to believe that the problem of incompatibility with am3d is due to our device tree, because on my tablet, all roms are compatible with am3d zirene, in summary, crdroid is compatible for the lg pad (tablet) but not with The s5 mini (smartphone)

[Spookcity]

@jimmy999x As far as configuration.. Hmm alucard seems to be good for this. Alucard hotplug as well. Just be sure,as in the warning about my kernel to set the delay time in kernel adiutor to at least 10 seconds because certain governors don't play nice with the hotplug governor and will cause a reboot once applied. I came across a real nice article on CPU governors that I plan to add to my kernel thread on XDA. Let me see if I can find it. I'll post it here.
CPU governors

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

@Spookcity So far the kernel works as expected. No random reboots or other strange behaviour. The governors and the voltages seem to apply correctly. Well done!

[jimmy999x]

Any idea how to compile moke rom? Already includes AndroidProducts.mk in the kminilte folder

[Spookcity]

@Mikahlo Great! Very glad to hear that and thanks a lot for the feedback. Its really appreciated!

@jimmy999x Hmm, I don't really remember doing anything specific when I built it. If theres already an AndroidProducts.mk,then all I can think is that there must be somewhere in Mokee's vendor folder where you have to add our device. I'm really not too sure.

[jimmy999x]

When I built paranoid, I got these errors, is there any way to correct them or skip that process of creating the kernel and using of the @Spookcity

[Oleggluk]

Ooh, paranoid, I want to try it for a long time.

[Spookcity]

@jimmy999x I'm not real sure. You can try to comment out these lines in the boardconfig.mk with a #

Kernel

TARGET_KERNEL_CONFIG := kminilte_00_defconfig TARGET_KERNEL_SOURCE := kernel/samsung/kminilte Then add:

ifeq ($(TARGET_PREBUILT_KERNEL),) LOCAL_KERNEL := device/samsung/kminilte/zImage else LOCAL_KERNEL := $(TARGET_PREBUILT_KERNEL) endif

PRODUCT_COPY_FILES := \ $(LOCAL_KERNEL):kernel

This will require you building the kernel separately before the ROM build and then pasting the zImage in the folder listed above (device/samsung/kminilte). I'm unsure if it will work or not. Hope so!

Edit: Just thinking, if you don't want to build the kernel and want to use mine just open up the zip file of my kernel and extract the zImage. You could use that.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

Someone can explain to me in Russian)), that he means. Https://forum.xda-developers.com/showpost.php?p=73191400&postcount=1241 One of the links has a paragraph with the words "klte-common: fingerprint: fix missing sensor_init () (android_device_samsung_klte-common)". Does this concern our apparatus?

[Spookcity]

@Oleggluk Interesting find. I'm honestly not sure off hand and this is for the S5,but we use bits from the S5. Plus I do think our fingerprint stuff is similar. Certainly the file that has been patched ( fingerprint.c) I think are the same...or at least similar enough that we could try this patch.

Edit: Sorry not in Russian :D

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Ahaha)). Not in Russian, but it's pretty clear. If this somehow helps improve the performance of the fingerprint scanner, I would like you to pay attention to it when there is free time.

Explain in Russian, it's an expression. Means that I did not understand)), even if we communicate in one language. It is necessary to explain in an easier way. Ahah).

[Spookcity]

@Oleggluk hehe,OK understood. I will look into this some when I have a little time and try to see exactly what this fixes and if it applies to our device.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Thank you. With a new core, with a new RR, with a new battery for $ 10 with aliexpress)), 2 days of life and 6-8 hours of screen and more than 20 hours of Wi-fi. Why do I need a new smartphone, when this is good).

[Spookcity]

@Oleggluk Very nice! I agree. I am very happy with my phone. I'm in no hurry to get a new one. I'm able to do all I need with it. I think I'll be looking into a replacement battery soon. Mine is OK,but its getting old.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity I also thought that my battery is still normal. I constantly use the widget in the status bar, voltage and load of the processor. But on the old battery the voltage is not logical, on a new battery it can be understood. I'm not at all sure that I bought the original battery, I bought for $ 10, we have official services asking for $ 40. But I'm happy, my device has not kept so much for the past few years.

[Spookcity]

@Oleggluk This could very well be the case with mine as well. Good to know. I will not be buying an official battery either. They ask too much for them IMO. I will also probably just get one from AliExpress...or similar.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Be careful. A lot of deception. And never look at 3200/5200 of the same form, ahah, it's such a hoax. Samsung could not, and Uncle Liao could)).

[Spookcity]

@Oleggluk Hah,yeah I will certainly be careful. On another note... I just read your post on XDA in the LOS 14.1 thread to the guy who keeps posting over and over about his sim card. Made me laugh. It's funny, but also very true,something must not be right with him.

Sent from my Samsung SM-G800F using FastHub

[HaxXorHardy]

@Spookcity i have this simcard bug too. I use an older version.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Explain it in Russian)) But I think they just troll.

[Oleggluk]

@HaxXorHardy You installed the official firmware 6.0.1, launched it. Installed TWRP, installed custom firmware? And you do not see a sim card? I do not believe!

[Spookcity]

@Oleggluk agreed,I think he must be trolling..or is indeed mentally ill!

@HaxXorHardy You need to do as @Oleggluk has said then you should not have this problem

Sent from my Samsung SM-G800F using FastHub

[HaxXorHardy]

@Oleggluk no i have done a dirty flash while it was released after this i had to rollback to the old version. What is the best tool to backup personal settings apps and data?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@HaxXorHardy For me, the best Titanium Backup. But I do not answer for anything and do not bear any responsibility. You can restore the data. It depends on what firmware was previously used. Photos and videos, you need to transfer separately. Contacts can also be saved separately as standard in the vcf format. All in your hands.

[Spookcity]

Spookcity_Kernel-N - Test v3.0a

Alright,so I've spent most of my limited free time lately messing with the kernel and its really getting to where I want it to be. It is very stable for me and I notice real improvements over the stock kernel,performance wise and battery wise. Granted, I am running a version with more additions/tweaks,but you cant' get everything at once :D

Changes:

• DriveDroid support (add sysfs entry for cdrom to LUNs)
• Implemented zen-tune v4.5 (I don't think I've fully implemented it properly yet though. Still looking into this)
• Full CIFS support (modules will be pushed with kernel install)
• Introduce new flag WQ_POWER_EFFICIENT for power oriented workqueues ( This will allow for power saving if enabled in Kernel Adiutor etc.)
• Added Fsync on/off
• CPU voltage control (still)
• Added ROW I/O sheduler
• Added BFQ-v7r8 I/O scheduler for 3.4 kernel
• Added Blu_active CPU governor

Other things of note

• block: disabled add_random

• tweaked build flags

• many other workqueue related patches

• tcp: tweaked for speed

• CONFIG_HZ=300 (from original 100. I may lower it back though. I'm unsure. Still testing this)

• fs/proc/array.c: make safe access to group_leader

• disabled debugfs

• 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_v3.0a Download Spookcity_Kernel-N_v3.0a-1500mhz (untested)

[Oleggluk]

Only I lost the switches in the virtual memory item?

[Spookcity]

@Oleggluk Weird. I assume you mean in kernel adiutor. I still have them. No issues here. I use kernel adiutor-mod,but I also checked with the regular kernel adiutor and all good there too.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

Strange, maybe I dreamed). But below there were more settings.

[Spookcity]

@Oleggluk haha,I don't know. This is the same as I have. I guess I didn't really pay attention,so I'm not sure if its changed. I'm not real sure why it would,but who knows. I'll install an older version of the kernel later and have a look.

Edit: I will say after looking at your screenshot.. The swappiness value of 100 is way too high IMO. This is a common setting. I'm looking for a way to set this much lower with my kernel install. I have mine set to 0.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

I built a 1500mhz version of test 3.0a. Download is in the main comment above.

[Oleggluk]

Installed the core of test 3.0a on RR Tonight I used the BetterBatteryStats program to make a BBS dump. When I showed it on the forum, that's what they said to me: "Oleggluk, you have an expense of 0.1% per hour, at this expense, even the meaning of the dump is not to be studied, just a little bit and the phone will start charging itself." . :D Hahaha

[Spookcity]

@Oleggluk Haha, brilliant! That new battery is certainly paying off. I really do notice very nice improvements using my kernel. Even with my rather old battery. I have really good battery life. I also notice a nice performance boost. Which is good. Means I'm not spending all of this time on nothing :D

Edit: Even with my Marshmallow kernel I really only added governors and I/O schedulers. No real tweaks or patches at all. Now I have learned a lot more about android kernel things :)

Sent from my Samsung SM-G800F using FastHub

[tester-02]

I'm on lineage-14.1-20170726 build from Panzerknakker. For me 3.0a produces random reboots, where the 1500MHz is working fine! Thanks for the second version. But all the other versions since your build v0.9 with 1600 MHz produced the reboots.