Root [Virgin Mobile] VaeVictus Kernel VOLTAGE ERROR

[mudflap2020]

Well from what I've seen the moment I hit 1.5 ghz maybe 1.6 my phone started bugging out I switched between conservative and on demand. By the way I am also running version 0.1.1 of JerryScript because I don't want that link2sdcard stuff. Could this be a contributing factor?

Omg, (THE GRAPHICS ARE HORRIBLE)wait the responsiveness is 60 fps ohhh nevermind lol ftw

 

[Chiral]

Well from what I've seen the moment I hit 1.5 ghz maybe 1.6 my phone started bugging out I switched between conservative and on demand. By the way I am also running version 0.1.1 of JerryScript because I don't want that link2sdcard stuff. Could this be a contributing factor?

When processors are built, there is a bit of variability with each chip. After being built, each one is tested and they are sorted based on what they can handle and given ghz ratings. I would assume theyre all built to be 1.5s, but on the lower end of the bell curve you do get some duds. Conversely, there are probably a few "lucky chips" that could safely go higher than 1.8.

Thus, the Victory is probably built with mostly the 1.5 rated chips then capped down to 1.2, but the ones that failed QC @ 1.5 and passed @ 1.2 are probably tossed into the production run because fudge it, they run at 1.2. Sounds like yours might be one of these. If thats the case, OCing will require higher voltage, more heat, and really just isn't a good idea.

 

[insanelycool]

When processors are built, there is a bit of variability with each chip. After being built, each one is tested and they are sorted based on what they can handle and given ghz ratings. I would assume theyre all built to be 1.5s, but on the lower end of the bell curve you do get some duds. Conversely, there are probably a few "lucky chips" that could safely go higher than 1.8.

Thus, the Victory is probably built with mostly the 1.5 rated chips then capped down to 1.2, but the ones that failed QC @ 1.5 and passed @ 1.2 are probably tossed into the production run because fudge it, they run at 1.2. Sounds like yours might be one of these. If thats the case, OCing will require higher voltage, more heat, and really just isn't a good idea.

Chances are no matter how much voltage you throw at it, it just wont be stable. Thats what happens when you hit the limit of how well the circuits came out on that particular chip. Even if you watercool or phase cool a processor, it can still only go as far as the chip itself can handle.

On the bright side though, the performace gain is relatively minimal from overclocking past 1.5ghz, and most of the gains you are getting on the rom is optimized and efficient code.

 

[JerryScript]

Chances are no matter how much voltage you throw at it, it just wont be stable. Thats what happens when you hit the limit of how well the circuits came out on that particular chip. Even if you watercool or phase cool a processor, it can still only go as far as the chip itself can handle.

On the bright side though, the performace gain is relatively minimal from overclocking past 1.5ghz, and most of the gains you are getting on the rom is optimized and efficient code.

Oh yeah?

Just bragging, I agree with you!

 

[comps]

i will beat

 

[mudflap2020]

Oh please shazam my phone and itll kick both yall a$$at 2.5 ghz with 100fps graphics at 1080p and gpu @ 1000mhz lolz

 

[rbheromax]

XD U are really trying to blow your phone up lol

 

[insanelycool]

Oh yeah?

Just bragging, I agree with you!

You got a good phone... I was just about to post that my antutu crashes on the CPU test if I go past 1728mhz 9on performance gov for consistant testing conditions)... so both 1836mhz and 1782mhz crash the antutu at 1%... The phone seems fine running at those speeds though as I was running ondemand with max of 1836mhz and hadn't experienced any crashes in over a week... I have overclocked enough to know that its probably my chip though. Just can't do consistant math maintaining those speeds... what a shame.

Edit: I also remember from overclocking my PC that one core can usually overclock better than another... in this case I can get the test to run if I put core 0 lower and max out core 1...