Test Builds #3

[ghost]

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

[ghost]

Maybe github should use like a page-layout, that would save me a lot of scrolling. I hope you don't mind moving the conversation all the time

[Spookcity]

OK,1.8 I get the boot animation.......Now the keypad...Then it locks up and reboots. If you wish to try to flash this and the try test14 please be careful. I would feel really bad if this destroys anyones phone Download Test15

And @StanNL I don't mind at all

[ghost]

@Spookcity I'm a bit doubtful as to whether or not I should install this.. I think I'm just going to stay on 1.6 and if you manage to get a 1.65 build I'll try it out because I don't want to break my phone... Maybe someone else dares to try this out, but I don't think I will

[Spookcity]

@StanNL I completely understand. I also think that it is very unlikely that this has anything to do with it. I'm building a 1.65 again. Maybe it will boot. If so Ill post it up. If not I just don't know. Hopefully Ill get feedback on XDA. Then I may,if I have time,later today remove all of the revision checks within the CPU files. Maybe this matters. Why,no idea. Then I guess I'll try to figure out how to stop the phone from booting at 1.7.

[Oleggluk]

@Spookcity Test 15. Smoke, hiss, explosion. Knocked out the windows. The cat jumped from the 9th floor. The dog made a big pile ...))) Joke. Not booted. Hangs on the Samsung screensaver. I returned to test 14, no changes, just hangs on the desktop and reboots.

[Spookcity]

@Oleggluk Haha..Whew,you scared me there after only reading the first line! Kinda figured it wouldn't matter,but thanks for risking your phone and trying. At least that's knocked off the list.

Edit: Also strange to me how it hangs on the Samsung logo for you fot test15,but I'm able to get t he bootanimation and even get to my desktop.

Edit II: Again I built 1.65. It boots for me and works for a short time t hen just locks up. I leave it here because others,as we see,may experience different. Download 1.65

I'm off for now. Let me know about the 1.65. I will try to mess with it more and remove the revisions checks a bit later if I have time.

[Oleggluk]

@Spookcity I dont know. You have a military prototype Galaxy S5 Mini)). . I installed test 10 again, also no changes. I installed the test 15 again, the samsung screen saver is not loaded. I think it's easier to stop at 1600, otherwise it takes a long time.

[Spookcity]

@Oleggluk Haha,something I just don't understand. I agree its probably best to just leave it at 1.6 and be done with it,but my brain won't let me lol I must understand how this is possible. Did you try the 1.65 OC I posted above?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

@Spookcity Test 16 also hangs on the desktop.

[Spookcity]

@Oleggluk Thanks. I'm kinda of glad for this as if it worked for you and not me it would have made an already very confusing situation even more confusing. Iv'e lowed the voltage and am building 1.7 again. Although why this would matter I also don't know as its the same on the 1.6,but..

[ghost]

Test 16 also didn't work for me

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

test17 - Reset voltages back to stock values.

[ghost]

@Spookcity I can't download it. Did you delete it?

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Hmm,not intentionally. I think its right,but maybe This Edit: Yep the first was the wrong link errr. Corrected

[ghost]

By the way: The boot.img you uploaded — was that just the stock kernel with a different clock speed, or was it your kernel with another clock speed? Because if it's just the stock kernel with a different clock speed, that would indicate that my phone just cannot handle it.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL It was my kernel.No difference apart from all of the tests on here,just decided to try to rule out it being relateed to anykernel2 Although,that is another thing to try. Given time I will just OC the stock kernel and see. Building one now with all of the revision checks removed.

[Oleggluk]

@Spookcity Test 17 as well as before, no change. freezes on the loading animation.

After the second reboot hovered on the desktop.

[Spookcity]

Thanks @Oleggluk I'm going to build this version without revision checks. Then I will try to just OC the stock kernel. After that...No idea.

[Spookcity]

Test18 -Revision check removed

[ghost]

I'm sorry but this doesn't work either...

[Oleggluk]

@Spookcity Test 18 is no change.

[Spookcity]

Haha,oh my god. My brain is gonna explode. I am building a stock kernel from the device repo (cm-3470) Only OC'ed to 1.7.I'll post it in a few. If this doesn't work I have no idea....If it does I don't really either though haha. No I would have to guess it would be a build flag in my makefile perhaps,but still,that'd be weird. I'll wait and see what this test brings before I start thinking ahead.

[ghost]

Yeah but if it would be a build flag, why would it work for you then? That wouldn't explain it either, but I'll just keep on testing...

[Spookcity]

@StanNL Yep,I completely agree,but I'm at a point now where none of this makes any sense to me,so I just don't know. I also cant get the stock kernel to build with my toolchain and its throwing erors,err

[ghost]

Well, I think we've ran out of ideas. You mentioned something about booting the device at a lower clock speed, right? Maybe that's another possibility

[Oleggluk]

Ahahah, After kernel test18, kernel backup does not help. The phone does not load, the eternal animation of the download.

[ghost]

@Oleggluk That's odd, are you sure you're installing the right one? I always go back to test13 and it worked for me

[Spookcity]

@Oleggluk Wait,your phone works still though right?? Uhgg This should def not have caused this @StanNL Yes,this is the last idea I have, Lower the clock speed on boot. Im just unsure how.

Test19 Stock kernel with stock toolchain. No build flags,all stock except a 1.7 OC Goes without saying,but...It works for me lol

[Oleggluk]

I restored today's backup, the phone does not load, eternal animation. I restored a two-day kernel backup, the phone does not boot, eternal animation. I asked Test13, the phone does not load, the eternal animation)). Now I'll try to flash the stock boot.img from the firmware.

[Spookcity]

@Oleggluk Oh my god man. I so hope that works. I'm very sorry. I feel really bad. There was certainly nothing in test18 that should have caused this.

[Oleggluk]

Stock boot.img also did not help. Eternal animation. I'm going to flash the smartphone. Spookcity, do not worry. I volunteered to test myself. And I will continue))

[Spookcity]

@Oleggluk I know,but I still feel really bad. I'm only trying to help people and improve the phone a little. I definitely didn't want to cause this :( I really hope that will work. I'm very unsure why that kernel would have caused this. I made no big changes. DJSteve also removed the revision check from his kernel. I doubled checked just to make sure it would be OK.

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

Test19 didn't boot for me. The boot animation got stuck. The log I made is useless. So we all have the same phone even the revision is the same. But what's different?

[ghost]

@Mikahlo I'm not sure, but @Spookcity mentioned something about the fact that he has Fusing Speed Group 8, while you have Group 6, but I have no idea what that means, how to change it, and even if it's possible to change it or if it's just a hardware difference

[ghost]

I don't have much time today (nor the upcoming two weeks, why am I even doing this at the moment?) but here are the only 295 about those groups (just in case you don't know how Google's syntax works): https://www.google.nl/search?q=%22fusing+speed+group%22

[Spookcity]

@StanNL Yeah, I'm going to look into what fusing speed is exactly. I did some searching yesterday,but found no useful info. So the stock kernel 1.7 OC still doesn't work for anyone here but me It has to be a HW difference then,no? But what and why? So frustrating. @Oleggluk What's the situation with your phone?

Sent from my Samsung SM-G800F using FastHub

[Oleggluk]

Installed the firmware, without deleting data, does not work, eternal animation. That's bad. Found a full backup five days ago. I did all the wipe and restored the backup. The phone started. I did not lose much., But it's long minutes for me, I've had 5 cigarettes). For today, enough experiments))

[Spookcity]

@Oleggluk Oh man, I'm so glad it's working at least. Again,I'm very sorry that you lost stuff and had to go through this. Whew,I'm just glad its not broken. Yet another confusing thing that makes no sense to me though. No idea what caused that for you.

Edit: This issue that @Oleggluk had also seems to indicate a possible hardware difference. Again,but why I wonder.

Edit II: @StanNL Those search result are pretty much what I was looking at yesterday. I'll look a little deeper, but didn't see anything very helpful. At the end of the day I may just have to assume that I have a super S5 mini and contribute all of this to that... Only so I can stop thinking about it and sleep tonight lol

Sent from my Samsung SM-G800F using FastHub

[Mikahlo]

Found this > link. So the voltages needed for some cpu steps are different depending on the asv group I guess.

[Spookcity]

@Mikahlo Great job! This makes a lot of sense actually. If your voltage steps are different then mine, it would explain a lot. Although I still don't get why they are different. I was thinking,I believe when I posted the test version with the stock voltages that I actually forgot to change them in a file. I will try to do that later or tomorrow and post up test 6318 lol Otherwise I'll look more into that link,but now knowing its voltage related explains a little. Interesting: ”ASV group gets fussed on SoCs during process of mass production.”

Sent from my Samsung SM-G800F using FastHub

[ghost]

That sure is a nice find. Hopefully it'll help because I was completely clueless

[ghost]

My CPU cores seem to have their own will. No matter which minimal and maximal frequencies I choose, it always slowly goes back to 800 MHz, which is strange. Am I using the wrong governor? I'm using userspace at the moment

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

@StanNL perhaps,I have actually removed userspace from my newer builds. I can place it back though if you prefer. I have never used it and am a bit unsure of how it behaves. If your frequency stays at 800 MHZ even with say zzmoove then something is not right for sure.

Edit: I am building my last build for today..and very possibly regarding this issue (unless I can sort out how to have it boot lower than the max) This will be for SURE the stock voltages. After that I give up and have to assume,for the sake of my sanity,that it has to do with the set fusing speed. Although this will always be strange to me.

[ghost]

@Spookcity Well userspace is known for allowing the user to set their own clock speeds, so I thought that would be the best choice. I'll try zzmove

Sent from my Samsung SM-G800F using FastHub

[ghost]

Even with the performance governor, it still goes to 800 (though it should always stay at the max frequency then). In that case I'll use zzmoove indeed, though it keeps disabling certain cores.

Sent from my Samsung SM-G800F using FastHub

[Spookcity]

Download Test20 - Stock voltages That's all I got for today. My hopes are low and if it doesnt work then I'll just keep the 1.7 for myself and share the 1.6 only. Thanks everyone for testing!

@StanNL very strange.My frequencies stay at 1000 on userspace and full on performance.I am using the 1.7 build though,so perhaps this is why. I'm unsure

[ghost]

@Spookcity I have to disappoint you, because test20 still does not work for me :(

[Spookcity]

@StanNL Hah,not surprised. I just don't know. It's a shame because the 1.7 does run nice,well for me. Oh well. I'll still try to look into the boot CPU frequency. Other then that,1.6 it is I guess. This will always be a big mystery to me.

Sent from my Samsung SM-G800F using FastHub

[ghost]

@Spookcity It definitely is. Maybe henny has some time today, since he just posted something on XDA

[tester-02]

Sadly a bootloop for me with test20. it doesn't even get to the homescreen. I'll try to get a log.