Test builds #2

[ghost]

This is a continuation of the test builds topic (#10), since it was getting way too long.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

Check connection). I agree with the phone a lot of flipping a lot of posts. What the technology has come to, it translates words)

Отправлено с моего Samsung SM-G800F с помощью FastHub

[jimmy999x]

I have compiled many roms, now I do not know what to do, the majority of roms, they give me problems at the moment of applying the patches

[Oleggluk]

@jimmy999x When there is nothing to do, you can always update RR )). Still it is possible to try to build new twrp 3.1.1

Отправлено с моего Samsung SM-G800F с помощью FastHub

[Spookcity]

@Oleggluk I am pretty sure that ayke has built TWRP 3.1.1. There were issues in general with TWRP that I think he has fixed,mostly. I think I remember him saying that the difference was very little and he wouldn't be releasing the new version until all of the bugs were worked out.

[jimmy999x]

@Spookcity I would like to learn to compile custom kernels, would you give me some good tutorial?

[Spookcity]

@jimmy999x Sure thing. I would personally start with just trying to compile the "stock" kernel without making any changes. I'll post a few links as well. The main steps are

1. Clone the kernel source
2. cd into that directory
3. In terminal: export ARCH=arm export CROSS_COMPILE= "path to toolchain" /bin/arm-eabi-
4. make kminilte_00_defconfig
5. make nconfig (or gconfig or menuconfig. They are the same just different interfaces) This is where you can make your settings. When done esc and save.
6. make -j4 or -j8 or -j16 to build

You can use the default toolchain which is found in all of the ROM sources directories in "/prebuilts/gcc/linux-x86/arm/arm-eabi-....or you can download a sabermod,linaro,uber prebuilt and use that. You can also download one of my toolchain builds which are optimized for our device (a7) from my Android toolchains repo

As far as adding features and stuff. I really just look through xda and browse other kernels and look for interesting/useful things to add. Then work out how to add them. CPU governors and IO shedulers are not very difficult (most of them) Its just a matter of finding the source files and adding them. Then fixing them a bit to build with our device. I'll gladly try to help out if you need anything. Heres a few helpful links: XDA XDA GCC build flags can be used to add to the makefile to optimize the kernel. Archidroid XDA Great stuff fabout optimizations. Good luck!

[Guntzog]

@Oleggluk I agree, updating RR would be good

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Spookcity_Kernel-test10 - 1.7ghz OC

OK,I am leaving this here for whoever may see this to test and let me know their findings. I have been using it for days with no issues,but your experience may differ. I am not going to announce this on XDA as I really just need a few people to test and let me know. No changes beside the OC and I adjusted some voltages to work with it. It is set to automatically use the 1.7ghz frequency. I want to change this and have it set at 1.5 so the person can decide wether they wish to use 1.6 and 1.7 themselves,but Ive yet to figure out how to do this. In time. Feedback please. Thanks! Download 1.7 OC

[Oleggluk]

@Spookcity Test10, firmware RR. I could not check. Phone freezes tightly. Does not react to anything.

[ghost]

@Oleggluk Yeah and it really overheats to 55-65 °C

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Weird. I have had no issues at all. The temps are nearly identical as with 1.5 for me as well. How is it that 3 ppl with the same phone have such drastically different experiences? What ROMS are you guys on? I've used the 1.7 OC for days on AOKP and AICP without a single issue. Edit: My CPU temp is steady at 35-38. Has not exceeded 50 and I've been checking for that.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Clean installation of the firmware RR and the kernel test10. The phone does not boot, it hangs on the download animation.

[Spookcity]

@Oleggluk What revision of the processor do you guys have?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity The complexity of translation. What does revision of the processor mean? And where to look?

[ghost]

@Spookcity I'm a bit puzzled by this as well. Don't we all have the same Exynos 3470?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity

[Spookcity]

@StanNL Yes,same processor,but there are at least 3 revisions. From terminal cat /proc/cpuinfo On the first line you'll see "rev #" @Oleggluk. Try the command line I posted. This doesn't show revision... For some reason

Stupid autocorrect. I corrected the terminal command

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity What kind of command you need to enter, I do not understand.

[Spookcity]

@Oleggluk Yeah,sorry. Autocorrect messed it up. Enter cat /proc/cpuinfo

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity

[Spookcity]

@Oleggluk leave a space between cat and /proc. So "cat(space) /proc/cpuinfo'

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

[Spookcity]

Thanks @Oleggluk This however confuses me more. You have rev 3,same as me,so I have no idea why it works without a problem for me and doesn't even boot for you. I'll flash RR and try.

Edit: And it becomes even more confusing.

No problems with RR for me either,so I don't get it at all.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity It is very strange. But the problem is not just me. Familiar with the forum, wrote to me that he has the same problem, the phone does not boot with the test10 kernel on the RR

[Spookcity]

@Oleggluk yeah, I just don't know what the reason for this might be. It is the most confusing thing to me and I'm not sure how or even if I can fix this as it works perfectly for me on every ROM that I've tried. So I just assumed that if it works for me others should experience at least similar. If you had rev 2 of the processor then I would kind of get it,but you don't,so I'm at a complete loss.

Edit: I have time now so I'm going to try ta few things. If you wouldn't mind @Oleggluk testing them for me. I will post a link up in this post shortly. I will flash first though just to make sure it works for me and doesn't destroy my phone. Just going to build a few with slightly different tweaks to see if any will work for people. I have tested them all.All work fine for me.

Download test11 Download test12 Sent from my Samsung SM-G800F using FastHub

[Guntzog]

@Spookcity in 5hours after work, I will test and see if I'll get the same bootloop or else, I'll keep u informed

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity I have revision 3 as well. test11 didn't work for me but I'll try test12

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Thanks for testing. Test12 probably won't work either. There's only a small change,but who knows. I guess I'll just stick to using the OC personally and not include it on the kernel cause I have no idea how its possible to be very stable for me,yet not even boot for others. I've no clue how to fix this.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity 12 didn't work either indeed. It's strange that it does work for you. I'm using LineageOS

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Thank you. It is incredibly strange to me. Like I can't even wrap my head around how that's possible. It not only works for me,but it works well. I haven't had a single crash or weird issue in nearly a week of use... On 3 different ROMS. No extreme CPU temps either. I'm at a complete loss.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@ @Spookcity Test 11 and 12 also does not work. Which TWRP do you use? I'm using 3.1.0. Perhaps there is some difference.

[Spookcity]

@Oleggluk I'm also using 3.1.0. Could it be related to SELinux? Is that possible? Are you guys flashing over an enforcing kernel? Maybe I'll compile an enforcing version and see..if you're willing to test. None of this makes sense to me.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Dirty installation of salinux in the permissive. Clean installation, I do not remember which option. I'm ready to test any changes.

[Spookcity]

@Oleggluk Yeah probably not SELinux related. Thats' a bit of a long shot really. I'm going to compile an enforcing kernel and I'll compile one with 1.6 OC. Thanks for testing. I'll put links in this post. If neither of those work I don't know what else to do unless someone smarter than me can tell me how its even possible to work for me and not others,cause I have no clue what the deal is.

[tester-02]

@Spookcity Test10, -11 and -12 all won't boot for me, too. It makes no difference if I delete catch/delvik or do the dirty flash. I was on your test9 kernel and use LineageOS 14.1. The SELinux is set to permissive and I have the same terminal output like @Oleggluk.

[Spookcity]

@tester-02 Thank you for testing. Any idea as to how this is possible or what could cause this? I am really at a loss. It makes no sense to me.

[ghost]

It does boot by the way. It just wouldn't respond to any form of input on test 10 and on 11 and 12 it would just reboot after it had booted, though it wasn't a bootloop either

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Thanks for clarifying @StanNL Here's a 1.6 OC version. I tried to compile an enforcing kernel,but it still showed as permissive for some reason in RR.I need to look into that. Download test13 - 1.6 OC

[Oleggluk]

Test13 works!

[Spookcity]

@Oleggluk great! but someone needs to explain to me how this is possible. I am so confused right now. 1.7 works fine for me.

[Oleggluk]

@Spookcity I saw on your screen a new governor alucard. But I did not find it in Test13

[Spookcity]

@Oleggluk Yes,I've actually been working on the kernel a fair bit over the last week. I've added many new CPU governors,IO schedulers, TCP congestions and a few patches. None of this is included in this build yet. I was wanting a test of the OC without these things first..and good thing as 1.7 apparently doesn't work for many it seems. If you'll test out the 1.6 version for me and let me know if you have issues. I will create an XDA thread over the weekend of an official release and soon after I'll build with the added governors etc for test on here. I would still love to understand how 1.7 doesn't seem to work for others.

Edit: I've also overclocked the GPU to 600mhz,but the way things are working this will only work for me :D Test versions for all of this coming hopefully next week. I've been running it all, stable as can be.

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Ahahah. I ran the test10 kernel after test13 and it works! It took 2 reboots. Installed 1700, rebooted the smartphone and the smartphone booted and hung on the desktop

Eh, does not work anymore. Reboot does not help. Loads well, but hangs tightly on the desktop. But once it worked. Miracles are somehow.

[Spookcity]

@Oleggluk Hmm,so even more confusing haha. So very strange. I just can't imagine what the cause would be. Like I've said 1700 works just fine for me. I've even got 1800 to boot,but it doesn't last long

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Oleggluk Yeah but that issue was the exact same that I experienced on builds 10-12. Test 13 does work!

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Thanks for testing and the feedback guys! I guess I'll just keep it at 1600 and perhaps create a separate 1700 git branch ( cause I'm gonna be using that) and when I create an XDA thread link both builds with a large disclaimer about the 1700 build. I can't be the only one who this works for though. My brain hurts from trying to think about why this would be :D

Edit: OK,something interesting. I generally don't install gapps as I use f-droid and other combinations for this. I flashed gapps. The phone booted,but was very "laggy" then rebooted. First reboot I've had. Gapps has also cause my CPU temps to raise. Although I'm still not experiencing the non booting issue. It is bizarre.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity Yeah that's exactly the issue I had. I'll try to flash the kernel without GApps!

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL keep me posted. Things seem to be OK for me now though with gapps. No more lagging and no more reboots. I've rebooted a few times without issue. Gapps does seem to increase the CPU temp though. Although this has stabilized for me as well since initially flashing.

Edit: I find it highly unlikely that it is gapps related as I've been steady using my phone with gapps installed and the 1.7 OC for a bit now without any issues, aside from the reboot and lag directly after flashing gapps. So on to another reason I suppose.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity Yeah when I installed LineageOS without GApps, it went the same as before: It booted, but after a while it rebooted, and then after a while it froze again and rebooted, etc. It's very strange

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL Thanks again for testing. It is very strange. I'm really out of ideas as far as anything else to try,or what the cause could be. So if anyone who sees this has any idea about what could cause such a bizarre thing please do let me know.

Sent from my Samsung SM-G800F using FastHub