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

Root Instability in velocity when oced

d3310n

Android Enthusiast
Am i the only one who cets a crash and has to pull battery when using the camera or any camera related app? Im oced at 748mhz when i go back to 600mhz i can use the camera.
 
for me at 748 my keyboard acts funny.
typing a "c" opens messaging app (sms) when composing an emial.
729 is stable.
 
for me at 748 my keyboard acts funny.
typing a "c" opens messaging app (sms) when composing an emial.
729 is stable.


You fix that by going to settings and turning it off. So you can stay at 748
 
My camera was actually doing just that last night....if I clicked the camera button, it would freeze and reboot, but if i went into the app drawer and selected camera it was fine.
 
Yeah, using the camera button while overclocked causes my phone to reboot, though like socobandit said, if I open the camera a different way it's fine.

@Valkerie, I don't think it has to do with the overclocking itself(yes, I know the ocing is related obviously) because I didn't have this issue before FroYo, I think it's a bug that's causing the problem vs the action of ocing itself. You get what i'm saying?
 
turning what off.

when I am typing an emial or entering a password with a "c" the 'messagng' app starts

id love to clock higher.

if you go to settings then under applications it says quick launch... go through and clear them. i think you have to long press and then clear it... doesnt matter if you are OC or not just clear these and you will be set...

hope ive helped...
 
if you go to settings then under applications it says quick launch... go through and clear them. i think you have to long press and then clear it... doesnt matter if you are OC or not just clear these and you will be set...

hope ive helped...
ok
I did that. ill try reclocking when I am sure that the new dalvik to cache is working perfectly.
 
ok
I did that. ill try reclocking when I am sure that the new dalvik to cache is working perfectly.

Moving files around isn't going to make your CPU any more clockable than before. Everyones phone has a limit and nothing can change that.
 
Moving files around isn't going to make your CPU any more clockable than before. Everyone's phone has a limit and nothing can change that.

no no no .
I meant I don't want to try 2 new things at once. it messes up testing.
if I get a force close I won't know if it's the overclock or the moved dalvik cache. so I won't know the best way to fix it.
 
Back
Top Bottom