![]() |
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
Quote:
|
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
Quote:
I am not right and not wrong ... this is my personal opinion , when it comes to overclocking I've always avoided extra systems related to power management due to instability . I know you are asking me to see if I know what I am talking about . Maybe I am totally wrong , but with my personal experience in overclocking I can say MY N9 and MY N900 consume less power with SR off and a lower voltage at a overclocked cpu speed (I am not sure about the others , that's why I highlighted "MY"). I just can not see how a system could reduce power consumption when it needs a lot more power to work . :rolleyes: |
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
Quote:
|
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
Quote:
|
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
VDD1 is the CPU and GPU because they're on the same chip (MPU), VDD2 is the "l3 bus" that the MPU uses to read and write to main memory, flash storage, USB, the display, the camera, and everything else.
The bus is used more at higher MPU frequencies, but since we didn't touch the clock speed of it, increasing the voltage shouldn't be required. |
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
I experience many reboots in PR 1.3 overclocked to 1150, especially when I use the phone, but not only (sometimes I just see it rebooting while it is on the desk with low-power screen displayed). In PR 1.2 I overclocked to 1200 and I don't remember of any reboot. Is it only due to my device, or did something change whith how voltage is managed? Am I the only one to experience a stability loss with the N9 and the last version of Opptimizer?
|
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
Quote:
It sounds to me like your values aren't working and are destabilizing your N9. Overclocking is always do-at-your-own-risk, but here is my set_up: I am running version 1.2.5 with the 1.5.4 kernel module version. I have custom voltage activated and Smart Reflex activated. Frequency (MHz) is 1375. Voltage is 1375000. I have run well over 36000 test iterations at these levels without a single reboot! And I have been operating at this level for months. Good luck with whatever you decide to do! |
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
Yes of course I understand that overclocking is do-at-your-own-risk, no problem with that.
But the fact is that I did not change anything between my configuration for PR 1.2 and my configuration for PR 1.3, except updating Opptimizer to the correct version. I have Smartreflex VDD1 and VDD2 activated, and no custom voltage. I run 1.2.7 version with kernel 1.5.4. In PR 1.2 I was running at 1150 or 1200 MHz, and successfully passed the iterations step at 1300 (but decided not to use it). Now, in PR 1.3 with the updated Opptimizer, even 1250 makes the N9 to reboot during the iterations, and 1150 is highly unstable. I don't know if it comes from my device or other stuff I may have screwed up in config files (or by installing stuff like Faster N9), or if somebody else experiences the same issues since the update. Hence the question! :) |
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
I've been running opptimiser UI 1.2.7 since Creamy posted it here and haven't had any issues at all.
With regards to the SmartReflex switches this is what I've found with my N9: SR1 disabled SR2 enabled Custom Voltage 1.30V Maximum stable frequency: 1140MHz SR1 disabled SR2 disabled Custom Voltage 1.30V Happily purrs along at a frequency of 1250MHz. No reboots. Supposedly ramping up the MPU_CLOCK (VDD1 domain) should be uneffected by SR2, which controls VDD2 domain. Yet I can gain an extra 100MHz when I disable SR2, just as Dragoss mentioned. |
Re: overclocking kernel modules + UI for PR1.3 [ko v1.5.4] [ui v1.2.6]
I was hoping it's Dragoss's device since that makes no sense. Thanks for letting us know, though.
|
| All times are GMT. The time now is 14:34. |
vBulletin® Version 3.8.8