Closed ghost closed 4 years ago
@StanNL Thank you! Again,my hopes are not high.I lowered the DVFS which I believe is related to power management. Who knows
@Spookcity It still froze on my home screen...
It may be related to the fact that I have my charger plugged in, who knows... I'll just let it boot without one
@Spookcity Test 14, the smartphone started and rebooted again and hung on the animation and again rebooted, again booted for a few seconds 30 and again hung.
Errr,Oh my god. What the hell could it be?!! I usually have my charger in too,so probably not it,but again at this point...I'm going to post on XDA and see if I am the only one this works for.Crazy!
@Spookcity Are you sure the only difference between test13 and test10 is the frequency?
Yep,I have checked and checked. Even checking commits made after to make sure something wasn't included from the 1.7 OC that shouldn't have been. I have found no other changes.
I posted test14 on my kernel thread on XDA. Lets see if others are willing to try and what the outcome is. This is seriously making my brain hurt lol
So I guess I'll wait and see if others will test and what the outcome is. It seems at this point it's only going to work for me,which for the life of me I don't understand. After that I will look into trying to get it to boot at 1.5 or 1.6...even though this would still cause issues at 1.7 for others I would think,and also not really answer anything.
@StanNL are you still on Lineage? Let me make a boot.img instead of using anykenel if you're willing to try. Again,no clue why this would matter,but I'm trying to eliminate things.
Boot.img fot Lineage only! LOS boot
@Spookcity Yes I'm still using LineageOS
@Spookcity You used the kernel from 1800 and it was not stable, but maybe this somehow affected the performance of the processor? Is there a version with 1800? I'm ready to check.
@StanNL If your willing to try t o flash the boot.img above I'd be greatful. Just obviously make sure you check boot and NOT recovery.
@Oleggluk No,but I can build one. Give me a few. I had the same experience with 1.8 as you guys are describing with 1.7
@Spookcity I'll wait for version 1800. I'll try later. You have to walk with a dog)
@Spookcity The boot.img didn't work either. It's not that 1.6 GHz isn't enough, but it's just strange that it does work for you and not for us, I guess there is a hardware difference after all
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...
Wait, I got a bit confused there. I thought it said GHz, but it was MHz... now it makes a lot more sense all of the sudden...
@Oleggluk Building now....and I do have to walk my dog..How do you know that?! I'm a bit scared haha I'm going to assume it translated wrong and you mean that you have to walk the dog,but wow,that's a bit creepy lol
@StanNL I agree,but only a 100mhz OC is not much and the 1.7 is a much more noticeable step up from 1.5. It is beyond strange. I seriously cant stop thinking about it lol. I mean WTF?
@Spookcity Yeah it's a ridiculous issue, but it probably has to do with hardware differences. Maybe 1.65 GHz would work?
@StanNL I couldn't get 1.65 to boot for me.Perhaps I did something wrong or maybe its just not a usable variable. I will try again the 1.65 and see. The HW difference is the only thing that makes any sense,yet it also doesn't to me. I mean you and I are even from the same country! Why would there be a HW difference?! I just don't know.
@Spookcity But did you already live here when you purchased the phone? I didn't buy the phone in the Netherlands by the way, I ordered it at a Belgian company who gets their phones from Hungary
@StanNL Yes,I bought my phone here in the Netherlands. Hmm,Ok I mean I guess you getting your phone from a Belgium company that gets them from Hungary could explain a little,but still. It seems very weird to me.
It's very strange... Most of the time 50 MHz steps do work. I've seen some computers with 2.15 GHz or similar clock speeds
I thought so too. Perhaps I just messed something up. I'm building a 1.8 now. I will flash and see what happens. I think I expect to experience the issue you have with 1.7. I'm a bit hesitant to post it up though as if 1.7 doesn't work for you guys what is 1.8 going to do to your phone. I changed no voltages are anything though for the 1.8,but still. And I also highly doubt me flashing a 1.8 before has anything to do with it,but one more time..at this point...
Could we please continue the discussion at #20, because issues with more than 100 comments are a bit long, aren't they?
Вы просто молодцы,блин кто т сказал про 2000 Ггц ,это что то невероятное,прошу не бросайте свои разработки,если получится то это ж что то из фантастики для старого мини
@Igor9393 2000 GHz would probably be a world record, which would be nice for our "old" device :) 2000 MHz would be a little high as well, since 1.7 GHz doesn't even work for everybody except Rick.
Sent from my Samsung SM-G800F using FastHub
@StanNL Yeah,there was never any chance of reaching 2000. 1800 MHz was something that was probably unlikely as well,but since it does boot for me and allows me to get to my desktop before it locks up there was a chance that adjusting some things might have helped. But since no one else can seem to get 1700 to work (grrr) I'm not going to mess with anything higher.
Sent from my Samsung SM-G800F using FastHub
Согласен,я был бы очень рад если вы spoockity доработали версию на 1700 Ггц
@Igor9393 I have indeed done this and am personally running a 1.7 build. However this does not work for anyone on here but me for some very strange reason,but don't get me started on that Grrr lol
Also as one last attempt to try to figure this out I cloned DJSteves 1.7 OC repo as he messed around with a few other things. This would not boot for me though. Probably due to being based on the lollipop sources.
Sent from my Samsung SM-G800F using FastHub
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