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

Root Overclocking Ally

Very nice job on this kernel.

Velocity V0.1.1
768mh/z
93.7F
Stress test for 582sec, no errors.

Over 768mh/z I get a kernel panic.

EDIT: kernel panic after 20ish minutes on 768 also. 748 seems stable.

Any way to rectify this? Simply just boils down to manufacturing quality control?
 
GRZLA said:
I have flashed the kernel 4 times and have had issues using the browser every time. I of course did all of the obvious stuff like cleared cache and even my history. Everytime I restore the browser works flawlessly. I wish there was a way to give you an error report but it only seems to be effecting me browsing on 3g.
Click to expand...

Can you go into more detail on the issues?
 
Question for those with success at 787 mHz: What have you been setting you min speed to?

Phone has been fine for 18 hours @ 748 mHz. 768 mHz resets the phone once every 15 mins (give/take depending on use). 787 mHz usually locks within 60 sec of setting. I have been using 122 mHz as my min speed throughout...

Velocity V0.1.1
748mh/z
92.2F
Stress test for 368sec, no errors.
 
Im running velocty 0.1.2 beta 11.
i can clock all the way to the top but i get a kernel panic after about 5 minutes.
768 seems stable for me.
Iv been running this for about 8 hrs so far (including night)
 
SuperMerg said:
Question for those with success at 787 mHz: What have you been setting you min speed to?

Phone has been fine for 18 hours @ 748 mHz. 768 mHz resets the phone once every 15 mins (give/take depending on use). 787 mHz usually locks within 60 sec of setting. I have been using 122 mHz as my min speed throughout...

Velocity V0.1.1
748mh/z
92.2F
Stress test for 368sec, no errors.
Click to expand...


been running for close to 24 hours, no restart, on performance. min set to 245, but this really makes no difference as its been running at the full 787 for the entire time. I even left it running some pretty cpu intensive games all night, and its still going strong. Love my phone : ) Sorry to those who got poor die quality : (
 
oh yeah, and I switched back to stock ROM. Im getting some amazing mflops for this phone with it, much better than with velocity for some reason. Quality of the build?
 
drellisdee said:
Can you go into more detail on the issues?
Click to expand...

After I flashed the kernel I was able to play a multiplayer game over 3g but could not use my browser.I even tested out seesmic and was able to update tweets but my browser was the only thing lacking. It was always halfway load on the statusbar and just stall. I attempted to let a page load for 10 minutes with no results.
 
drellisdee said:
No that wont work. Why dont you just restore nandroid. Else reflash rom. No one else has repoerted connection issues.
Click to expand...


I dont have a nandroid backup and oddly enough the problems just went away. maybe i just didnt have a sufficient enough cell signal or there was something wrong with the wifi, i have no idea but i was at school.. when i got home it was working fine and has been now ever since.
 
GRZLA said:
After I flashed the kernel I was able to play a multiplayer game over 3g but could not use my browser.I even tested out seesmic and was able to update tweets but my browser was the only thing lacking. It was always halfway load on the statusbar and just stall. I attempted to let a page load for 10 minutes with no results.
Click to expand...

Try running a lower clock speed and toggle airplane mode off/on.
 
drellisdee said:
Try running a lower clock speed and toggle airplane mode off/on.
Click to expand...

I scaled it all the way down to 600 and on each step cycled airplane mode for 2 minutes, and still had the connectivity issue. I had to restore to even post this.
 
Anyone else having serious problems with the 50% bug after installing this kernel. I seem to be getting it more than usual
 
Nope. I overclocked at 729mhz 11am witha a full battery yesterday and my phone lasted until 8-9ishpm. Thats with IRC running in the background, using Skyfire, sync on, full brightness, and whatever apps were running in the background.
 
Jace417 said:
Velocity V0.1.1
748mh/z
91.4F
Stress test for 643sec, no errors.


Will try a test at 768 and report back later.
Click to expand...

Decided to run the stress test at max first... results are as follows:

Velocity V0.1.1
787mh/z
87.8F
Stress test for 370sec, no errors.

--

It's actually running cooler at 787 than it did at 748. Granted the stress test at 748 lasted almost 11 minutes; while the test at 787 lasted for only 6 minutes. Still results look promising... more to come!

--

Results at 768:

Velocity V0.1.1
768mh/z
87.8F
Stress test for 563sec, no errors.

--

At 768mh/z, temperatures matched the 87.8 put up by 787. Will test all three speeds (748, 768, and 787) for 30 minutes per, later this evening. I will, of course, let you know how that goes.
 
I must have got a good one or the fact I work in a room that is at a constant 60 f. I've been up for an hour on 787.

Velocity 0.1.1
787 mhz
80.1 f (batt temp)
Stress Test for 262 seconds no errors

Also when I installed the OC rom, it reset my velocity back to stock, is that normal?
 
turbine said:
I must have got a good one or the fact I work in a room that is at a constant 60 f. I've been up for an hour on 787.

Velocity 0.1.1
787 mhz
80.1 f (batt temp)
Stress Test for 262 seconds no errors

Also when I installed the OC rom, it reset my velocity back to stock, is that normal?
Click to expand...

no, thats not normal.

i only got kernel panic running 3 apps in background and skyfire active after 20 minutes, set on performance with processor max at 787 and min set to 600.
 
badandy2021 said:
no, thats not normal.

i only got kernel panic running 3 apps in background and skyfire active after 20 minutes, set on performance with processor max at 787 and min set to 600.
Click to expand...


Try setting it to On-Demand, I remember Dres saying he only has OnDemand implemented
 
turbine said:
Also when I installed the OC rom, it reset my velocity back to stock, is that normal?
Click to expand...

Did you clear your caches with the recovery before flashing? This kernel is packaged in a zip thats setup to be an update, it only moves/changes a few files on your FS, it is not necessary to wipe caches or data before applying.

I flashed it fine and quick with no impact to my configuration, should have worked the same for you.
 
badandy2021 said:
no, thats not normal.

i only got kernel panic running 3 apps in background and skyfire active after 20 minutes, set on performance with processor max at 787 and min set to 600.
Click to expand...
ahhhh, just got my first kernel panic, i ran the music player, navigation, and started browsing javascript heavy sites with the 787/600 performance option.

Doh, yeah i wiped out of habit. I have a backup that I made minutes before, I'll go restore then not wipe.
 
savoxis said:
Try setting it to On-Demand, I remember Dres saying he only has OnDemand implemented
Click to expand...


i know what it SHOULD be set at ;)

i just wanted to keep pushing it to see how much the cpu could handle. im going to keep backing it down a little at a time until i can find the max this one is capable of running.

*edit* yeah ill just put it back to 787/320 on demand, no sense in frying a good cpu.
 
Jace417 said:
At 768mh/z, temperatures matched the 87.8 put up by 787. Will test all three speeds (748, 768, and 787) for 30 minutes per, later this evening. I will, of course, let you know how that goes.
Click to expand...

Unless someone specifically requests it... I think I'm going to forego on the half hour 748 and 768 mhz tests for now. The 787 variant went rather smoothly, so I'm going to actually put the stress test aside for now, and put it throw some actual usage.

For those keeping score at home... the 30 minute test at 787 look remarkably like the 6 minute version:

Velocity V0.1.1
787mh/z
87.8F
Stress test for 1800sec, no errors.
 
Ok, I reflashed (thanks savoxis) and I'm going to just leave it with the 787/122 on demand setting and see if it stays stable through a normal day of usage.
 
Ok... 20 minutes of Home Run Battle 3D at 787/245 was all my little phone could handle. As the ball was sailing out of the park, I experienced lock-up and restart.

Next step is to let the battery cool-down and see how long I can play at 768/245 before it cries.
 
I think running graphic applications will be our Achilles Heel, our little ARM is already overworked trying to render 3d applications.
 
You must log in or register to reply here.
Back
Top Bottom