Test builds #2 - Githubissues

ghost commented 7 years ago

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

ghost commented 7 years ago

@Spookcity I am really curious about what the cause of the issue might be. The only thing left is rule out differences between our devices and then eventually we'll hopefully find the cause...

I'm not using busybox.
I use the userspace governor with min. 1400 MHz and max. 1600 MHz (I know it's kinda overkill and very battery unfriendly, but just let me be me).
I have multicore power saving disabled. This may actually be the cause of the issue. I'll try enabling this and see if it helps
I'm using the cfq I/O scheduler with 512kB read-ahead, though that's not very relevant.

ghost commented 7 years ago

@Spookcity Nope, changing option 3 didn't help and it still freezes at the lock screen. Maybe you know a few possible differences?

Spookcity commented 7 years ago

@StanNL I have been thinking about this all day. I just have no clue. I've not had any problems with any setting, governor,IO scheduler I set. I'm still using RR with the 1.7 OC. The only problem was the reboot yesterday after flashing gapps. It's been smooth since. I've also been messing with the kernel some ( not the OC issue as I'm at a loss) and have flashed the 1.7 OC I would say 10 times today without an issue. No wiping anything either. I really can't begin to understand what the problem could be. I really hope someone else might have some clue because I really don't.

Edit: As far as busybox, I honestly don't know what ROMS come with it these days. I just know that I've used the 1.7 OC on AICP,AOKP,AEX and now RR without issue. Whether they have BB..I don't really know.

Edit II: Sorry just can't stop being bothered by this lol... But I mean what other possible differences could there be? We all have the same revision of the CPU. I have to believe all other HW is the same. Do you guys use encryption in any form? Umm What type file system? I've never changed from ext4 to f2fs. So I guess I'm using ext4. Unless it's just setup to use f2fs. I've never messed with this.

Sent from my Samsung SM-G800F using FastHub

Oleggluk commented 7 years ago

@Spookcity I'm using f2fs. Encryption never used.

ghost commented 7 years ago

@Spookcity Well, I was surprised to find out that I did have BusyBox installed, but I removed it a few days ago (before installing the kernel). It is something that doesn't get removed when you install a new system, so you may have it as well.

Sent from my Samsung SM-G800F using FastHub

ghost commented 7 years ago

@Spookcity I'm using LineageOS, maybe you can try out if that has anything to do with it if you have time for it. I don't have any idea which filesystem I'm using nor how to find out

Sent from my Samsung SM-G800F using FastHub

ghost commented 7 years ago

I just found out that I have ext4. I have an SD card, and though that may sound irrelevant, we could consider it.

Sent from my Samsung SM-G800F using FastHub

Spookcity commented 7 years ago

@StanNL interesting about busybox. I didn't know that. I'll flash Lineage in a few and see what happens for me. I also have a SD card. I agree,it doesn't seem like it could be the cause,but at this point who knows. It has to be some minor thing I would imagine...Assuming our HW is the same,which I think it must be.

Sent from my Samsung SM-G800F using FastHub

ghost commented 7 years ago

@Spookcity I tried booting it without the external (I forgot to mention that in the previous comment) SD card, but it was in vain and it still froze. It's just very very strange. I also tried your kernel on XOSP this afternoon by the way, but it didn't help unfortunately

Sent from my Samsung SM-G800F using FastHub

Oleggluk commented 7 years ago

@Spookcity What version of RR (who is the author)? . In the subject on xda there is a version without Magisk. I have a version of jimmy999x with Magisk installed. Maybe this is the difference.

Spookcity commented 7 years ago

@Oleggluk hmm, I'm not sure. It has magisk installed though,but since I have my kernel running I'm unsure who built it. The build date is Thu June 8

@StanNL It is so strange. I just can't understand it at all. I'm going to flash Lineage, but it seems the way things are going it will probably work for me.

Edit: I also checked the voltages. As I messed with them some, but they are identical on the 1.6 OC. So it has to be strictly related to 1.7. There were no changes made besides that.

Sent from my Samsung SM-G800F using FastHub

Spookcity commented 7 years ago

As suspected, no problems for me. Err,so annoying.. So heres all I can think of..

If I can find the right code to have the phone boot at 1.5 instead of 1.7 that would help,but I've looked into this some without luck,so if anyone has an idea...
Someone can try to grab a kernel log via TWRP without letting the phone reboot back to the system (assuming this is what it does) Other than that I just don't know.

Edit: If anyone is able to grab a log without letting it boot back to system,the command in TWRP is cat(space)/proc/last_kmsg(space)>(space)/sdcard/last_kmsg.txt ( without the space parts) Then the log will be on your internal storage.

Sent from my Samsung SM-G800F using FastHub

Mikahlo commented 7 years ago

Hi there! Just an idea: could you use performance profiles? I'm not sure if this is a LineageOS-only feature. The ROM could than boot with a medium or low profile with max cpu speed set to a lower frequency than 1.7

Guntzog commented 7 years ago

@Spookcity I flashed the kernel over RR clean without gapps, the boot animation turn like for 30 seconds then it freezs, and that it, I have to force close the phone, doesn't even boot for me

Sent from my Samsung SM-G800F using FastHub

Spookcity commented 7 years ago

@Mikahlo I'm honestly not real sure about this. Thanks for the idea though. I think maybe I just need to figure out the proper code to do this. It's fairly simple with snapdragon,but exynos not so much..At least so far.

@Guntzog Thanks a lot for testing. Am I seriously going to be the only one that 1.7 works for?! Its crazy and makes no sense.

Sent from my Samsung SM-G800F using FastHub

ghost commented 7 years ago

@Spookcity I did what you asked... I think. I installed the kernel via TWRP, then I copied the log to my SD card, and then I reinstalled test13. That's what I was supposed to do, right?

I did read the log, though it contained 1.8 million characters. I felt like there was a lot of repetition. Here's what I understood from it: (I attached a screenshot from the part I was talking about, and here is the link to the file itself)

A core dies (I don't really know what that means, but that's just what it said).
Then there's a lot of hexadecimal messages (I think).
Then the cores restart.
And then everything starts over again.

I feel like this is just something that's happening over and over again about every millisecond or so, and that would explain why the log is so long.

Here's an image of the part I was talking about:

ghost commented 7 years ago

@Spookcity Hopefully this will provide you with some useful insights, though it's still very strange that it does work for you.

Some more questions:

Do you have Magisk installed?
Do you use any "enable on boot" options enabled at Kernel Adiutor?

Spookcity commented 7 years ago

@StanNL Thank you very much! I won't be able to look at the full log until I'm at my PC tomorrow,but I think you're very correct that the problem lies with the part of log you posted. Although,off hand I'm not fully sure what it means exactly. Hopefully I'll be able to figure some reason out tomorrow.

I've successfully booted lineage without magisk installed and also with.

Same for the enable at boot options. I kind of just mess around with things,but have had it boot and work successfully with and without apply on boot. Weird stuff. Thanks again for the log!

Sent from my Samsung SM-G800F using FastHub

ghost commented 7 years ago

@Spookcity Well I didn't look at the logs on my PC either, but just on my phone, but take your time

Spookcity commented 7 years ago

@StanNL Yeah, I just had a look on my phone and you're very correct. It's just a giant loop. I'll need to look onto this because its not really clear (to me) what the reason is at first glance. Its still really strange to me that I don't have this problem and everyone else who has tried does.

Sent from my Samsung SM-G800F using FastHub

Mikahlo commented 7 years ago

I have a log too but don't know if I did this right. At least it should be the right kernel (Test10) :D TotallySkilledRepo

Spookcity commented 7 years ago

@Mikahlo Thank you! Your error is very clear. The reason isn't instantly clear to me though. I'll look into this tomorrow. Thanks 93.445692] [3] 2735 Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP ARM [ 93.445860] [3] 2735 CPU: 3 Tainted: G W (3.4.113-Spookcity_Kernel #1) [ 93.446007] [3] 2735 PC is at __irq_svc+0x6c/0x74 [ 93.446090] [3] 2735 LR is at irq_exit+0x6c/0xb8

Sent from my Samsung SM-G800F using FastHub

jimmy999x commented 7 years ago

Compiling aospextended I get this error, any idea how to fix it?

edit 1: I got this compiling paranoid, any ideas?

w3bservice commented 7 years ago

Hello, I would like to thank you for your super work @jimmy999x With your Roms I have problems. The setup assistant breaks down everywhere. I use to flashen always a new sd card and a fullwipe. My data I copy only after the setup of the mobile phone.

I came to the Roms after the Telekom had the update on MM had been rolled out and my mobile phone is always restarted or simply switched off. @Spookcity Your Rom is the first one that does not drain the battery with me

Spookcity commented 7 years ago

@w3bservice I think perhaps your issue with the setup assistant crashing is due to you using a version of GApps that is not supported. I read on SlimROMS site that with an update to their ROM a couple of months ago that you must use a very recent version of GApps otherwise you will experience this problem.

About this strange kernel issue I am sad to say that even with the help of your logs I still cannot determine what is causing this. The logs are very different,which makes it even more confusing. @StanNL just keeps looping it seems and @Mikahlo error is very obvious.Its a kernel oops followed by a kernel panic. The reason however is not clear to me. Usually you can see some clues right before are after,but I fail to see it and I cant read the hex code (which is where a lot of the info is) I grabbed sa kernel log fropm my working phone to compare and didnt see anything super obvious either. The only thing that really stood out to me was this:

mine: Exynos3470 ASV : Use Fusing Speed Group 8
@Mikahlo: Exynos3470 ASV : Use Fusing Speed Group 6 I'm unsure what this is though and a quick search provided me with no real answers. So if anyone can find out it would be amazing! This is simply the most confusing thing I think I have ever experienced. It's a real shame because the 1.7 works very nicely for me and is a rather nice. ** This is literally the only change from the 1.6 version kernel So I just dont know. Im going to try a few more things,which are just a shot in the dark. I'll post a build or two up soon I hope to test. Outside of that I will try to sort out how to have the kernel boot at 1.5 or 1.6. Even though I am sure that switching on 1.7 will still casue issues,but perhaps they will be more obvious. I just don't know

@jimmy999x Those errors are related to recovery. Apparently something has changed in Omni's recovery,errr. I guess I'll have problems with that as well now. I have fixed this before,but don't recall how. I just remember spending too much time figuring it out.

ghost commented 7 years ago

@Spookcity Are you sure you gave us the right link or something? It would be a shame if it turned out that you're using a different version

Spookcity commented 7 years ago

@StanNL Hah,yes that would be incredibly frustrating indeed! Just to make sure of this I actually downloaded test10 from my drive. I'm going to do the same right now and flash just to double check because you're right,how annoying would that be?!

Sent from my Samsung SM-G800F using FastHub

ghost commented 7 years ago

@Spookcity Well it almost has to be something strange like this, because there almost isn't any other explanation... It is very suspicious that it only works for you, the creator of the kernel.

Oleggluk commented 7 years ago

@StanNL It `s Magic :D

ghost commented 7 years ago

@Oleggluk Yeah maybe he's just trying to sabotage our phones...

w3bservice commented 7 years ago

@Spookcity Witch Version of opengapps i must using for this Roms, your Rom aex runs with ther org opengapps. I used the pico

Spookcity commented 7 years ago

@StanNL Double checked,test10 works fine for me. It is incredibly strange and also the most frustrating thing I've dealt with android wise. It just makes no sense. I'm building another test,, If it boots for me Ill post it up here in a few. This is going to drive me insane! ahha

@w3bservice I would just use the newest version from here I always use pico,but this shouldnt matter.

ghost commented 7 years ago

@Spookcity In the end, it's probably going to be something very simple and small that we just didn't notice

ghost commented 7 years ago

We all use the SM-G800F, right?

Spookcity commented 7 years ago

I have the SM-G800F yeah...and these crazy annoying problems always in the end turn out to be something really simple it seems.

ghost commented 7 years ago

Yeah it's either going to be something very simple that we just overlooked, or it's going to be something way too difficult that nobody has every heard of

Spookcity commented 7 years ago

Yep, it doesn't make any sense. I would understand it a little more if the 1.7 was very unstable for me or something,but it runs absolutely fine. OK, tried to build a 1.65 OC,but it doesn't work right. One more thing I can try that may be related to the different :ASV" issue between my log and @Mikahlo

What baseband are you on @StanNL I cant imagine how this would have any effect at all,but at this point... I'm on: G800FXXU1CQB2

ghost commented 7 years ago

I'm on G800FXXU1CQA1.

I don't know if this has anything to do with it, but this part of the log shows things about 100MHz, isn't that a bit strange? I don't know if those are cpu frequencies, but if they are, that may be the problem...

ghost commented 7 years ago

Something that also happened 239 times in that log, is the following: [ 3099.192145] [3] 2516 power_supply sec-fuelgauge: driver failed to report 'online' property: 4294967274

Spookcity commented 7 years ago

I'll be honest,I'm not fully sure whats that is related too. I'm pretty sure not CPU freq though.I just checked my log and its the same.Also the power supply failure is no problem. I'm building another test now. Hopefully it will boot for me and I'll post it here in a few. Although,my expectations are very low at this point.

ghost commented 7 years ago

@Spookcity It's just so strange that it does work for you and not for us... If it wouldn't work for everybody that would've made sense, but this is just strange. You must have installed something that we haven't, right?

ghost commented 7 years ago

All that I can think of that I use is kernel Adiutor, Magisk v12.0 and MagiskSU 8

ghost commented 7 years ago

Without any Magisk modules

Oleggluk commented 7 years ago

@StanNL With the power supply problem still with the CM12, the smartphone does not have a connection to the battery voltage controller. I tried to draw the developers' attention to this, but it's of no interest to anyone.

ghost commented 7 years ago

@Oleggluk Oh well that explains that message then, but that won't cause any problems, right?

Spookcity commented 7 years ago

@StanNL I cant imagine what. I've flashed the kernel directly over ROMS with apps installed that I had been using for days and also completely clean flashed wiping all but external storage and haven't had a problem either way. Also,no Magisk modules here either and the same versions when I install it (or its pre-installed) But the kernel works for me with it installed or not. Also with and without gapps. It just makes no sense at all.

@Oleggluk Intersting about the power supply problem,. Perhaps if this issue ever is sorted I will have a look into that.

Edit: The only possible difference I can think that I have is that I have my extSD formatted in 2 partitions. One fat32,the other ext2,but why this would matter is beyond me.

Hopes are low,but here goes nothing Test14 A bit redundant now,but well,works for me lol

ghost commented 7 years ago

@Spookcity You should realise that some things don't get removed when you wipe the system and data partition, like busybox for example or the "Samsung battery animation" that you saw before it got replaced on some ROMs. There has to be a good explanation for this. Maybe Henny can help us out, since he's very experienced

ghost commented 7 years ago

@Spookcity Or maybe you could post the kernel on XDA, so that more people can try it out and see if you're not the only one

Spookcity commented 7 years ago

@StanNL This is very true and perhaps the issue. I am in contact with henny,but has been really busy lately and I would rather not bother him with this,but at some point I will if I cant sort it cause it will be the death of me haha And yes, I think I will post a build on XDA with a waning because I cant seriously be the only one it works for Did you try the new test build yet?

ghost commented 7 years ago

@Spookcity No I haven't tried it out because I didn't see it. I'll try it right now!

Spookcity / ROMS-G800F

Test builds #2 #18