Test Builds #3

[ghost]

This is a continuation of #10 and #18 about 'test builds'.

[Spookcity]

@tester-02 Thanks! I'm running test20 and typing from it now. No surprise though. All of these versions have worked for me

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity It just doesn't make any sense... Are you sure you're using a Galaxy S5 mini?

[Spookcity]

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity Just to make sure...

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

Test20 boots and works for me. I didn't threw it on the ground :D Just have to test if the 1.7 ever gets reached.

[Spookcity]

@Mikahlo what? Crazy and more confusing! Please keep me posted

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Mikahlo Really? Wow! Maybe I did something wrong... I'll try installing test 20 again then.

Edit The craziest thing ever just happened... It booted (like it always did), but when it was about to freeze (I think) it started vibrating like crazy!! And then it rebooted again and it froze, like it has done 12 times now today, and has become 'normal' behaviour now. Maybe I just got called without getting a popup or anything

[ghost]

@Mikahlo It didn't work for me, again. It sure is strange that it does work for you.

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

The benchmark needs a while. After that I reboot to see if this kernel boots consistent.

[Spookcity]

@Mikahlo The fact that it boots properly at all leads me to believe even stronger that it does have to do with voltage and ASV fusing. Why there would be differences between our phones is beyond me,but this is looking more and more likely to me.

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

Mkay it's a mess. It boots consistent but reboots randomly. The 1.7 step is not used at all and the settings app seems to hang if you scroll down in the "phone status" section.

[Spookcity]

@Mikahlo Weird,weird,weird. Oh well. I don't have anything else I can think of to try. Maybe I'll think of something,but it seems as if the 1.7 is a lost cause. Thanks again for testing everyone.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

Test 20, hung on the animation. The second time worked fine, even managed to get a message in WhatsApp and read it. Then the screen went off and the phone no longer turns on at all and does not react to charging. It seems burned down completely (

[Mikahlo]

@Oleggluk try holding down vol-, home and the power button for while

[Oleggluk]

He is very hot. I pulled out the battery and put everything in the refrigerator. A little later I'll try to turn it on.

[Spookcity]

@Oleggluk It is def differences in voltage/cpu steps or capabilities of our phones then. I am 90% sure of this at this point. Very strange that it's that way,but I truly believe it is now. Since it has to do (likely) with CPU steps and voltages,I will look at changing the 1.7 voltages if I'm able. Perhaps tomorrow. The 1.7 voltages are the same as the 1.6,but since it appears to be about "stepping" perhaps this could help. I have been using the 1.7 OC for over a week now and have had 1 bizarre thing...A reboot after flashing gapps on RR.

Whoa,I just read apparently something I missed..Your phone is broken? Man, err How the hell is this possible?! The voltages on test 20 are stock. This makes no sense. Uhg,I feel really really bad now,sh%$

There is def some differences in CPU stepping/voltages between our phones. I am positive. I so hope that @Oleggluk phone will work again,man. I think I will not play with the 1.7 any longer. Its a strange issue and I would love to understand why it works so well for me and not others,but not at the risk to anyone's phone.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

I inserted the battery, went twrp successfully, and restored the kernel backup. The phone works fine. Something is already terrible to experiment. Let the smartphone rest.

[Spookcity]

@Oleggluk whew, Amazing news. I am very glad! I agree,the 1.7 tests are done. I'm sure,for some odd reason, that its a difference in CPU stepping and voltages between our phones. Still very strange,but I am content to let it rest at that. I don't want to be the reason why anyone's phone breaks. Its not worth that at all!

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

The most interesting is that I use a custom kernel to save battery power, and not to overclock. I do not really need 1700, it was just interesting). I'd rather wait for a stable version of 1600 with new governors and voltage regulation).

[Mikahlo]

I'm back on the test 5 kernel and suggest to leave the 1.7 behind and concentrate on what's already working to improve things if possible. sayonara

[Oleggluk]

@Mikahlo Test 9 and Test 13 are also stable.

[Spookcity]

@Oleggluk Hehe,yes. Well I appreciate you testing and I'm very very glad your phone is OK. I will only work on the 1.6 version (and just keep a 1.7 branch updated for personal use) I have already added many new governors,IO shed,TCP congestions. I have also moved a particular CPU function to be inline with newer kernel versions 3.8 etc) This is important for getting certain CPU governors to work properly on our 3.4 kernel. I've also added alucard hotplug. Which was a bit of a hassle, but seems to work relatively well. Either way,I'll try to get a (1.6) test build with some new stuff up on here real soon.

Sent from my Samsung SM-G800F using FastHub

[jimmy999x]

someone help me?

[Spookcity]

@jimmy999x Hmm.interesting error. I have to assume you have this line in the BoardConfig.mk: "BOARD_RECOVERYIMAGE_PARTITION_SIZE := 12582912" If so for some reason it is not being used I don't think. I'm unsure what would be causing this,sorry.

[w3bservice]

@jimmy999x Es sieht so aus als wenn im makefile ein Aufruf steht und er Werte aus erwartet die nicht übrsetzt worden sind. Schau Dir mal die audio_hw.c an.

Solche Probleme hatte ich immer wenn ich mir den Seamonkey aus anderen repos über setzt habe. Meist ist es eine Abhängigkeit bzw unterschiedliche Lib-versionen.

[w3bservice]

@Spookcity Kernel MM and your AEX 4.2 running good Thx

[Spookcity]

@w3bservice Interesting. I guess you mean the build in the XDA thread? I'm surprised this works for a 7.x based ROM honestly as a lot has changed for our kernel. Either way,glad it works. I'd recommended test 13 though for nougat. Only because, while having less features at this point. It is tweaked more already than the MM version

Sent from my Samsung SM-G800F using FastHub

[w3bservice]

@Spookcity My mobile runs with AEX and Test9 and the mobile phone of my wife with CM13 and MM. There I was with the Fnger leg write faster than the thoughts, sorry. Hear is a old man at work :XD

[w3bservice]

@Spookcity A bit of confusion keeps the hirsutes on the go

[Spookcity]

@w3bservice Haha,believe me I know the feeling :D

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Today we will experiment?))

[Spookcity]

@Oleggluk Hah,nope :D Yesterday was enough. I'd think for you as well! Ya wanna test out 2000 MHZ?! Hehe I'm not home now,but I plan to release test 13 as version 1 on XDA tomorrow or Tuesday. After that, hopefully late next week I will post a build up on here for test with some of the new features.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity I've been thinking about 1.7GHz and I was wondering if you've already tried making a Marshmallow kernel with 1.7 GHz. I don't know if you still have the necessary files to do it, but it may be worth trying.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Interesting idea. I do have everything I need. I actually just built a MM kernel this morning to put on the XDA thread.. I will build a 1.7 version tomorrow if you'd like to give it a test. There has been many kernel changes since MM. So who knows @Oleggluk is not allowed to test though :D hah

Sent from my Samsung SM-G800F using FastHub

[ghost]

I now know why the CPU frequencies didn't do what I wanted: Whenever you turn the screen off, the CPU either goes into deep sleep or it uses 800 MHz. Interesting behaviour...

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL This makes sense. Nougat handles sleep and CPU idling differently then previous versions I believe. Plus I have applied a good deal (15+) patches for CPU idle and CPU scheduling for tweaking/problem solving. Plus doze. So the combo of these I'm sure is the reason.

Edit: I've added and have messed around some with alucard hotplug. I've never really used any hotplug governors,but you can choose minimum cores always online,max cores online and cores online with the screen off. It seems to be a nice battery saver. I plan to try to add more hotplug governors if able. It was more difficult to add than a "regular" governor,but hopefully I'll work it out.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

I'm here reading all the nonsense on the Internet and that's what I thought. Everyone knows that on our smartphone there was a regular FM radio on firmware 4.4.2, it was necessary to install apk. But then on 5.1.1 it stopped working. I read on the Internet that "mobile devices have a universal chip for Wi-Fi, Bluetooth and FM, but the company at the program level blocked the possibility of listening to radio stations." So, what is the probability for us to unlock FM? More from the Internet: "Previously, cellular operators AT & T, Sprint, Blu and T-Mobile in the US agreed to activate the FM chip in mobile devices, Sprint has already enabled the function on contract Android-smartphones, and AT & T, Blu and T-Mobile are ready to do this in any time." So this is possible in principle.

[ghost]

@Oleggluk If our phone's hardware is capable of receiving FM radio broadcasts, which is what you just claimed, it should indeed be possible. The only problem is the fact that installing an FM-radio.apk isn't enough. There's a lot more to it than just that, but I think @Spookcity is capable of doing it, given that Samsung provides the necessary means. The FM radio also needs the appropriate libraries that often are device-specific and sometimes also (Android) version-specific. However, you also said that our device was able to use FM radio with Android KitKat. If that's true, the libraries should be available for our device and we might be able to implement them into either Spookcity's kernel or as a separate flashable zip for our device. The problem is just the fact that a lot has changed since Android 4.4.2 and it is quite likely that the old libraries won't work anymore, but maybe there's a chance that we are able to modify them to work with Android N.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@Oleggluk Hmm,very interesting. I honestly have no idea if this is possible or not. It seems like it should be,but I could be very wrong. It's something I can look into at some point. It is interesting how it was blocked or what-not. I wonder why exactly.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity They probably just felt like it wasn't worth the maintenance. Using FM radio would be cool though

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Yeah, I think you're probably right. I can't really think of another reason.

I also very much agree with your post about implementing FM radio. I don't know exactly how it is implemented, but like you said, if it was available on KK,the needed libraries should be available.

Edit: It may simply be enough to get the libs,have them flash/install along with my kernel and build the appropriate kernel module for it. As also mentioned by @StanNL though a lot has changed since KK, so fixing may be needed which becomes more difficult obviously.

Sent from my Samsung SM-G800F using FastHub

[w3bservice]

@Spookcity An FM radio would be class. Germany is about to ban the sale of new equipment. And when you look at what goes on here, everything fits into the paternalism of the citizens. I head back to the time of the GDR, just worse. Internet, restrict freedom of expression. I already knew that. But here no one does what. And now there is only digital radio. Nice, but it can be controlled who gets a license and sends system-conform. Orson Wells 1984 or V like Vandetta.

[Spookcity]

@w3bservice I didn't know that about Germany. Interesting stuff. I will only say that 1984 is one of my favorite books of all time and V for Vendetta one of my favorite movies.

I am home earlier than expected. Therefor I am going to try to build the MM kernel OC'ed to 1.7

Here's the MM kernel OC'ed to 1.7. I have flashed this on Lineage 14.1 and it does indeed boot. I had an "android is starting" message on boot and it took a little bit for my sim and WiFi to be detected,but it works. EDIT: there are def issues though with some apps. Either way,this is just to test the 1.7 OC,so not a big deal.

[ghost]

@Spookcity I tried using it on LineageOS 14.1 and it didn't work, but I'll try it with CM13. EDIT: It did survive longer though. It actually lasted for about a minute, and then it froze again. EDIT 2: Maybe that means I can get a system log now. EDIT 3: My old CM13 file seems to be corrupt, I'll try using it with XOSP 6.2 (based on Marshmallow)

[Spookcity]

@StanNL Thanks a lot for trying. Strange it didn't work for you on LOS 14.1. I'm typing from it now. Although there are issues.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity XOSP gave me an error that there is no system volume, so therefore it cannot mount it, which is odd, but that doesn't mean it won't boot, right? EDIT: It booted anyway. That was a strange error. I haven't installed the kernel yet so we'll have to wait for now.

[Spookcity]

@StanNL I have no idea honestly. Its weird that your having these problems. I can't really explain this.

Sent from my Samsung SM-G800F using FastHub

[ghost]

Yeah that was one of the strangest errors I've ever seen, but it's probably an XOSP bug.

[Spookcity]

@StanNL Haha, the your vs. you're is one of my pet peeves so I understand :D

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity Would you like me to get a Marshmallow log or a Nougat log? (or no log at all)