• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] [KERNEL] VaeVictus Kernel - Overclocked to 1.8Ghz [Updated 8-8-13]

I went back to the 1.5 victorius kernel Jerry built with linaro.

Battery is much better, -NO- battery heat, even while charging. Vaevictus benched ~700 pts higher locked at 1.8 on performance, but regardless of governor battery was worse and instead of hanging around ~80F the battery was regularly 85-95F.

The 1.5 kernel behaves exactly as stock & redspot, only without ANY UI lag. the 1.8 just doesnt feel "solid" in comparison.

I feel the 1.5 kernel deserves more attention than it has been getting.
 
Chiral said:
I went back to the 1.5 victorius kernel Jerry built with linaro.

Battery is much better, -NO- battery heat, even while charging. Vaevictus benched ~700 pts higher locked at 1.8 on performance, but regardless of governor battery was worse and instead of hanging around ~80F the battery was regularly 85-95F.

The 1.5 kernel behaves exactly as stock & redspot, only without ANY UI lag. the 1.8 just doesnt feel "solid" in comparison.

I feel the 1.5 kernel deserves more attention than it has been getting.
Click to expand...
No doubt it is a very stable kernel, and everyone would be fine using it. I will be sure to edit the VaeVictus and Victorious OPs to include downloads to it.

However, the goal here is to get a stable set of frequencies and voltages to achieve the best performance/battery life possible. Please be patient as we (and be we I mean mainly rbheromax, I'm just a compile monkey on the OCing) get things ironed out.

If you don't have the desire to test, I understand, and still appreciate the bug reports. ;)
 
Oh, I'll gladly test whatever you can come up with. I went back to confirm the differences.

Already downloaded the fixed freqs Vae kernel, I'll let you know what happens after I flash it.
 
I flashed the fixed freqs kernel yesterday and ran some benchmarks and stress tests. For some reason antutu doesn't seem to always work for the benchmark (i didn't try it on the previous kernel as I just downloaded antutu today, sorry!). I will often get booted back to the homescreen after starting the test. I still managed to try it enough times that it eventually worked. Didn't seem to matter what gov, but did seem to make a difference if I clocked down to 1.5ghz.

The stress test seemed fine on antutu, but I did manage to get the battery to overheat (I left it on the charger and got the overheating battery message during one of the stress tests while on the badass gov. the test completed though.) The first time I ran stress test on badass the phone rebooted. It's def getting hot on 1.8ghz if you push it! lol :)

Edit: I should have some free time later this week to do some extensive testing and post screenies. But so far my highest antutu score was 11873 running the msm-dcvs gov. with max range 384-1.8ghz
 
insanelycool said:
I flashed the fixed freqs kernel yesterday and ran some benchmarks and stress tests. For some reason antutu doesn't seem to always work for the benchmark (i didn't try it on the previous kernel as I just downloaded antutu today, sorry!). I will often get booted back to the homescreen after starting the test. I still managed to try it enough times that it eventually worked. Didn't seem to matter what gov, but did seem to make a difference if I clocked down to 1.5ghz.

The stress test seemed fine on antutu, but I did manage to get the battery to overheat (I left it on the charger and got the overheating battery message during one of the stress tests while on the badass gov. the test completed though.) The first time I ran stress test on badass the phone rebooted. It's def getting hot on 1.8ghz if you push it! lol :)

Edit: I should have some free time later this week to do some extensive testing and post screenies. But so far my highest antutu score was 11873 running the msm-dcvs gov. with max range 384-1.8ghz
Click to expand...

Its good it rebooted, if we can just find that freq it revooted it I may need to raise or lower voltage, random reboots are a kernel devs best friend when finding voltages :)
 
I have what I hope isn't a stupid question. In stead of a voltage issue, could the discoloration possibly be caused by the CPU? In the thread over at XDA, it explains that our processor is a processor that has errors. Each processor will give different results at higher speeds. Could the CPU on that phone not like higher, overclocked speeds. Just curious. You guys have a way better understanding of this than me and I wondered about this because it's only been reported by 1 user.

Thanks :D
 
buzzcon said:
I have what I hope isn't a stupid question. In stead of a voltage issue, could the discoloration possibly be caused by the CPU? In the thread over at XDA, it explains that our processor is a processor that has errors. Each processor will give different results at higher speeds. Could the CPU on that phone not like higher, overclocked speeds. Just curious. You guys have a way better understanding of this than me and I wondered about this because it's only been reported by 1 user.

Thanks :D
Click to expand...
What they are talking about will vary from phone to phone. Each processor has different capabilities. Batches of processors are "rated" at a certain frequencey, but each processor in that batch is in fact capable of higher speeds, some only a notch or two higher, others many notches higher. I could go on about the why's (physical defects during manufacture, insurance of good performance at underclocked values, added heat dissipation, etc), but the simple fact is each chip is unique and can be overclocked to a different degree than others. Some of us will be stable pushing our phones above 2.1ghz, others will not be stable much above 1.5ghz, it's the luck of the draw.
 
cause i think my phone dont crash or anything bad ever, seams as with any the errors you see, i dont..:/ is it cause my cpu is just lucky with min defects?
i just flashed the voltage fixand now mobile id keeps hanging/crashing on its own, repairing permissions hoping that solves it
new kernel is borked jerry. breaks twrp reboot from rom manger, breaks mobile id.

so how can i repair mobile id? now it wont run..
 
I was thinking that, but really, remove the app if its fc'ing like that, or change its perm to ---,---,--- and be done with it.
 
Also, related to the stability / how many ghz can my phone handle... it will not only vary depending on luck of the chip, but also will vary based on conditions like how cold or hot it is at the time.

I often overclock my systems based on the season, if I don't want to run my heater in the winter my pc can overclock higher, but if I run the heater then I can't actually overclock as high in the winter as I can in the summer if I leave my AC blazing the whole time. It's all relative. In an ideal situation you just watercool, or phase cool, but that isn't realistic with a phone.
The phone is more susceptible to crashing when it's in a hot room or car, in your pocket, or in sunlight. If you want true 100% stability, you bring those factors into your testing so that you have a realistic assesment of the overclock in the conditions under which you actually use the phone. You probably won't be encoding video on your phone or anything, so a "stress test" program will probably push your phone harder than anything you will realistically do... then again, some games *might* push the phone pretty hard. You just have to take all these factors into account. There is no one size fits all *maximum stable* overclock. We all have to figure that out for ourselves if we are going for max.
 
comps said:
remove what? mobile id? no. should find a fix, or its no good kernel in my book.
Click to expand...

Not the kernel.. I tried running it.. Did you try to restore mobileid from titanium backup?

When you get into flashing custom roms and kernels there's no guarantees, especially when in testing phase. But it sounds more like an issue on your phone.
 
comps said:
huh? rom manger bad to use for only to get into recovery?
Click to expand...
I said for fixing permissions, I do not know how ROM Manager performs this function, and I do not care to investigate (past history, lots of hours helping people fix their phones via remote-desktop after borking with ROM Manager, and no help from the dev when requested, lots of late-nite lost sleeping hours!).
 
You must log in or register to reply here.
Back
Top Bottom