I too use that combo.x13thangelx said:SetCPU does work.... I use it with Milestone Overclock and have never had problems out of it.
mine reboots past 1376 (iirc..... its between 1375 and 1380), normally set it to 1350/68 but it can go to 65 before rebooting. I go 2 above whatever the lowest is just to be safe and not stress it too much and im slightly ocd when it comes to number (they have to be even or it bugs the hell out of me) so rounded up one more.nuclearmistake said:I too use that combo.
What speed/vsel do you usually run at?
I usually use 1300/71, but I'm curious where the limit is... I know for sure my phone is unusably slow when I set it to clocks above around 1400
1350 isn't an even number lol. But yeah i'm the same way with overclocking. The number has to look right to me otherwise I drop it or make it faster. I hate funky numbers like 3.97 ghz or 4.31 (My desktop before I sold it hit 4.31 on air cooling but I hated that so I dropped it to 4.24 ghz... I would've done higher but the timings were just too wonky on my 680i board at those speeds)x13thangelx said:im slightly ocd when it comes to number (they have to be even or it bugs the hell out of me) so rounded up one more.
Probably had the voltage too low or speed too high for your phone then. Not all phones can handle the same...tRu3_sKiTz0 said:I was using setcpu and milestone clock using 1350/68 or something. Then I started having major performance issues. So I uninstalled both. Then installed milestone only used the default 1300. Now I am getting much better performance with no noticable battery decrease.