CPU frequency - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I have installed SETCPU and realized the max CPU frequency is only 1000Mhz.
But I thought the Galaxy Note has got 1.4Ghz. Have I missed something or I have to do something to max the speed?
Thank you

eatout said:
I have installed SETCPU and realized the max CPU frequency is only 1000Mhz.
But I thought the Galaxy Note has got 1.4Ghz. Have I missed something or I have to do something to max the speed?
Thank you
Click to expand...
Click to collapse
Might be your rom limitation.
Provide your rom and kernel details !!

I am using kernel LA4 (rooted stock rom)

to get full 1.4 ghz power and to overclock your device to 1.7 ghz.. u have to use abyss note kernel .. try flashing the kernel.. and ofcourse a good rom..

eatout said:
I have installed SETCPU and realized the max CPU frequency is only 1000Mhz.
Click to expand...
Click to collapse
You realized wrong. Galaxy Note has 1.4ghz definitely. I think you have seen the bold numbers which is shown above the cpu speed slider. That shows the current statistics of the processor. You should see max 1400mhz and 200MHz min in the slider. That is the speed of the cpu.
You can flash latest Abyssnote kernel from http://forum.xda-developers.com/showthread.php?t=1362424
Sent from my GT-N7000 using xda premium

the sliding bar is showing max 1000 only.
If I flash the abyssnote, it is going to wipe the whole phone??
Thanks

eatout said:
the sliding bar is showing max 1000 only.
If I flash the abyssnote, it is going to wipe the whole phone??
Thanks
Click to expand...
Click to collapse
No it wont. After flashing the kernel just wipe cache and dalvik cache and reboot after that. All your data will be safe.
Cheers!!
Hit thanks if it helped!

thanks, what's the difference betwen:
CW Touch Custom Logo
CW Touch Original Logo
RedPill Touch Custom Logo
RedPill Touch Original Logo
And do it do the wipe cache and dalvik cache under CWM?
Thanks

eatout said:
thanks, what's the difference betwen:
CW Touch Custom Logo
CW Touch Original Logo
RedPill Touch Custom Logo
RedPill Touch Original Logo
And do it do the wipe cache and dalvik cache under CWM?
Thanks
Click to expand...
Click to collapse
CW and Redpill are the two kinds of recovery. Works the same only the menu items placement and color coding is different.
Original logo is that you will get the Samsung stock logo while booting up. Custom means you will get the custom made logo of the developer while you boot.
You can go with the Redpill version. It has got the menu quite streamlined.
And you wipe the caches and dalvik in the recovery itself. In CW recovery it will be under Wipe cache partition and Dalvik will be under Advance options.
In Redpill recovery you will find the option of wiping caches under the Wipe Menu.
Hope this helps!!
Hit thanks if you like

it's on 1700 now, and I have read someone mentioned not to set the min too low, what's do you recommend?

Ouch!
Well the kernel would have done the job for you. Not sure why exactly it is showing as 1000 mHz still is it because stock rom...i dont think so. Will have to research it a bit. Will surely get back or see some other member posting something about it.
Just a thought. Adding m screenshot of setcpu. I am on custom rom. ICS Stunner 5.0 and i surely have it max to 1400mHz

thanks for the info.
I am on 1704 now. But what is your recommendation for the min freq? Some posts mentioned the phone will not go to sleep or some function will not work if the freq is too low

eatout said:
thanks for the info.
I am on 1704 now. But what is your recommendation for the min freq? Some posts mentioned the phone will not go to sleep or some function will not work if the freq is too low
Click to expand...
Click to collapse
min freq keep as 200mHz
Hit thanks if you so like
---------- Post added at 11:22 AM ---------- Previous post was at 11:18 AM ----------
abhisahara said:
min freq keep as 200mHz
Hit thanks if you so like
Click to expand...
Click to collapse
And keep the max as 1400. Keeping it 1700 is not worth apart from you want some awesome quadrant scores. It will just eat out your battery amazingly fast. Even at 1400 the phone is fast enough for anything and everything you throw at it !
Cheers! Enjoy your Note!
Hit thanks if it helped!

I personally never found overclocking these devices with fast, very fast processors like SGN worth it. They are insanely fast, the only thing I can achieve with overclocking is better benchmark scores and worse battery life.
Sent from my GT-N7000 using XDA

I can feel the speed has gone faster.
Usually when I press phone, I need to wait for about a second for the number pad to pop up. But since overclocked, it comes up straight away

Well that's good. But also keep an eye on how fast it drains ur battery!
BOOMED from my BOMBASTIC NOTE

It's used only 2% when idle.

eatout said:
It's used only 2% when idle.
Click to expand...
Click to collapse

Idle usage does not count - your phone does not run in top gear when its idle. Its deep sleep saving battery.

eatout said:
It's used only 2% when idle.
Click to expand...
Click to collapse
Over how long?
I would also recommend: 200MHz min, 1400 Max (as others have said yes it makes for great Quadrant and Antutu benchmark scores but chews battery and adds heat!) If you get a ROM that works well with your phone then the lag will be minimal.
FYI - I used to get 1% power loss overnight (7 hours) on some ROMs. I am still getting 3% on current rom and happy with that because I also get very good responsiveness. HTH.

Related

is undervolting safe and does it save battery? worth it?

and most importantly how is it done?
84 veiws but nor responses? I thought this would be a hot topic seeing as its supposed to do wonders for battery life
Undervolting saves me battery life. And, more importantly, all you have to do is change your kernel - not that difficult.
Sent from my Nexus One using XDA App
do certain roms require certain kernels to function properly or are they independant? any risk bricking your phone?
seeking said:
84 veiws but nor responses? I thought this would be a hot topic seeing as its supposed to do wonders for battery life
Click to expand...
Click to collapse
I wouldn't go lower than 925mV kernels for the Nexus One.
Use a good kernel and a good ROM, and just by doing that, you're got better battery life. Oh, and never, ever, EVER, use a task killer. They're completely pointless.
seeking said:
do certain roms require certain kernels to function properly or are they independant? any risk bricking your phone?
Click to expand...
Click to collapse
Most ROM's have at least the stock kernel built in, but it's usually safe to flash any kernel on any ROM, so long as the OS matches.
Make a backup before you do anything. If you've got a working ROM, back a nandroid backup, then flash to your heart's content. If the phone decides not to boot, just yank the battery and then boot into recovery (hold trackball + power button) and restore your backup.
thanks for the help
are there any recommended kernels for cm6 rc2 right now? I'm looking to get the best battery life I can with out damaging my phone
seeking said:
thanks for the help
are there any recommended kernels for cm6 rc2 right now? I'm looking to get the best battery life I can with out damaging my phone
Click to expand...
Click to collapse
Try the 925mV CFS 1113 Mhz kernel from: http://forum.xda-developers.com/showthread.php?t=693375
If you don't install setcpu it will stay at the stock 998 Mhz, so don't worry about overclocking if you don't want that.

[Q] Any one facing SOD in boype's modded CyanogenMod 7 latest build

Hello xda,
I am posting here as i do not have sufficient rights to post in developer section.
My Q is that is anyone facing problem in boype's modded CyanogenMod 7 latest builds:
cm-7-package-20120916-p970-boype
cm-7-package-20120909-p970-boype
I am facing atleast one SOD per day.
This is not an accusation,just a question.
If anyone could solve the problem.
Even bagr84 is also facing the problem as he said in his reply.
http://forum.xda-developers.com/showthread.php?t=1734312&page=155
Thanks.
e1forall said:
Hello xda,
I am posting here as i do not have sufficient rights to post in developer section.
My Q is that is anyone facing problem in boype's modded CyanogenMod 7 latest builds:
cm-7-package-20120916-p970-boype
cm-7-package-20120909-p970-boype
I am facing atleast one SOD per day.
This is not an accusation,just a question.
If anyone could solve the problem.
Even bagr84 is also facing the problem as he said in his reply.
http://forum.xda-developers.com/showthread.php?t=1734312&page=155
Thanks.
Click to expand...
Click to collapse
Did you do a full wipe before installing the ROMs? Did you restore apps and data with Titanium Backup?
I only had that problem, when I either not did a full wipe, or restored via TB.
N00BY0815 said:
Did you do a full wipe before installing the ROMs? Did you restore apps and data with Titanium Backup?
I only had that problem, when I either not did a full wipe, or restored via TB.
Click to expand...
Click to collapse
Thanks for the quick reply.
I do data reset and dalvik cache reset from CWM before flashing any rom
and
I always do the all apps manual installation process after flashing any rom.
Same problem I faced in both the builds I mentioned.
Before the cm-7-package-20120909-p970-boype build the rom was stable for me.
Never tried tweaking anything else except for the graphic ones.
Thanks
I got SODs with the 20120909 build. They went away after I set the minimum CPU clock to 400MHz (interactivex-governor).
OptiMyst said:
I got SODs with the 20120909 build. They went away after I set the minimum CPU clock to 400MHz (interactivex-governor).
Click to expand...
Click to collapse
Thanks for the reply
Currently i rebeveted back to 20120905 from 20120916...That is i flashed 20120905 back on 20120916
Did wipe/reset, wipe dalvik cache, cache reset.
No SODs so far ...
But facing a new problem.. when I connect my phone to mass storage it restarts.
Any clue?
And on 20120905 the minimum cpu clock is 200MHz default governor and still no sod.
And doesnt setting minimum cpu clock to 400MHz will eat battery?
Any solution for my new problem?
No replies?
No one is facing such problems?
Sorry but what is SOD. New here that's why asking..
Sent from my LG-P970 using Tapatalk 2
vishaldhamnekar said:
Sorry but what is SOD. New here that's why asking..
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
Screen of death. Frozen screen
vishaldhamnekar said:
Sorry but what is SOD. New here that's why asking..
Sent from my LG-P970 using Tapatalk 2
Click to expand...
Click to collapse
Probably a mac user?
On Topic:
I had no problems on interactivex
OptiMyst said:
I got SODs with the 20120909 build. They went away after I set the minimum CPU clock to 400MHz (interactivex-governor).
Click to expand...
Click to collapse
Hey
Thanks man.. it helped...
back to boype's 20120916 build and minimum clock to 400MHz ....
no sods so far... :laugh:
Just a quick notice: I've upgraded to boype's 20120925 build yesterday which contains changes to help against SODs. I've changed minimum clock back to 200 MHz to see if it the new version is better. I had no SOD so far. I'll keep an eye on it.
OptiMyst said:
Just a quick notice: I've upgraded to boype's 20120925 build yesterday which contains changes to help against SODs. I've changed minimum clock back to 200 MHz to see if it the new version is better. I had no SOD so far. I'll keep an eye on it.
Click to expand...
Click to collapse
Hey
I have also upgraded to 20120925 build but have the same settings as before.
Governor - interactivex
min cpu freq - 400 MHz
I'll too change it to 200 and chek.
Thanks.
I had few SoDs after I've updated to the latest build. I've change minimum freq to 400MHz.
I had no SODs, but I had two spontaneous reboots to recovery-mode while in standby. I'm also going back to 400 MHz minimum clock now.
Yeah minimum clock to 400 MHz works fine.... no SOD's so far ... using at this setting since my last reply.
This maybe out of topic but anyone facing USB mass storage problem, the flash drive not shown on the computer screen or instant restart at USB mass connection turned on ...
??
where are you man..don't stay at stoneage.....go to future...
Now trend is CM10....enjoy the jellybean
pvsukumars said:
where are you man..don't stay at stoneage.....go to future...
Now trend is CM10....enjoy the jellybean
Click to expand...
Click to collapse
Any suggestions.....STABLE BUILD I mean for daily use....
Thanks
e1forall said:
Any suggestions.....STABLE BUILD I mean for daily use....
Thanks
Click to expand...
Click to collapse
The M2 build is doing a pretty good job but check it out on your own
Sent from my LG-P970 using xda app-developers app
N00BY0815 said:
The M2 build is doing a pretty good job but check it out on your own
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
Aah yes.. I'll try this thing...
Here's the link
http://get.cm/?device=p970&type=snapshot
e1forall said:
Aah yes.. I'll try this thing...
Here's the link
http://get.cm/?device=p970&type=snapshot
Click to expand...
Click to collapse
i want to use boypes rom
but i have always sods
launcher goes crazy
etc.
which cpu settings no sods no fcs no wakelocks and without problems?
could you tell me?

[Q] Battery jumping

So i flashed Apocalypse ROM after i heard it was better in terms of battery life for custom roms and from my experience it is even with my 3g on constantly.
however, my battery level jumps from 100 to around 60 very fast, around 20 mins? before it stabilises and decharges at steady rates even if i charge it fully over night
battery calibration did not help
help anyone?
ok, i had the same thing on stock rom and on apocalypse AND on both cm10 and cm9, pretty much with every ROM i tried :/
i've tried calibrating/delating battery stats and nothing helps.
ntanggg said:
So i flashed Apocalypse ROM after i heard it was better in terms of battery life for custom roms and from my experience it is even with my 3g on constantly.
however, my battery level jumps from 100 to around 60 very fast, around 20 mins? before it stabilises and decharges at steady rates even if i charge it fully over night
battery calibration did not help
help anyone?
Click to expand...
Click to collapse
Try with the firekernel 22.07.2012 version.
also you can install better batery stats: http://forum.xda-developers.com/showthread.php?t=1179809
to see what's eating your battery,
and you did the proper wipes after install the room?
what governor are you using? min and max freq?
Matias.s said:
Try with the firekernel 22.07.2012 version.
also you can install better batery stats: http://forum.xda-developers.com/showthread.php?t=1179809
to see what's eating your battery,
and you did the proper wipes after install the room?
what governor are you using? min and max freq?
Click to expand...
Click to collapse
wiped battery stats n everything
using smartassv2 480 max 245 min
Qbsti said:
ok, i had the same thing on stock rom and on apocalypse AND on both cm10 and cm9, pretty much with every ROM i tried :/
i've tried calibrating/delating battery stats and nothing helps.
Click to expand...
Click to collapse
My phone is doing the same ****
Thread moved to Q & A section, kindly post in the relevant section next time.
ntanggg said:
wiped battery stats n everything
using smartassv2 480 max 245 min
Click to expand...
Click to collapse
i mean the proper wipes after install the rom, try this:
wipe data,
format sistem and cache,
-install the latest apocallipse and the 22.07 firekernel non official and non oc version.
don't wipe your battery stats, after install set up your lenguage, etc
and turn off your phone, charge off until 100%.
use it a few hours, and tell me how's your battery life,
Matias.s said:
i mean the proper wipes after install the rom, try this:
wipe data,
format sistem and cache,
-install the latest apocallipse and the 22.07 firekernel non official and non oc version.
don't wipe your battery stats, after install set up your lenguage, etc
and turn off your phone, charge off until 100%.
use it a few hours, and tell me how's your battery life,
Click to expand...
Click to collapse
i did this when i first flashed apocalypse , im just gonna see how it is for a few days

[Q] Desire C reboots after installing custom ROM

Hi
I recently tried to use a custom ROM and ended up trying almost all custom ROMs available for HTC Desire C. The problem is that whatever custom ROM I install my mobile reboots automatically while working on it. Sometimes during calls, sometimes during accessing Internet and also while accessing the menu items. What am I doing wrong or what should I do???
Your phone is not able to handle the cpu frequency. Flash a kernel with a lower frequency. Try 767MHz.
Or just use SetCPU or NoFrillsCPU app and lower the max frequency.
Frequency change did not work either
aashay960 said:
Your phone is not able to handle the cpu frequency. Flash a kernel with a lower frequency. Try 767MHz.
Or just use SetCPU or NoFrillsCPU app and lower the max frequency.
Click to expand...
Click to collapse
HI
Thank you for the reply... I tried changing the frequencies, but still it reboots
sathee12 said:
HI
Thank you for the reply... I tried changing the frequencies, but still it reboots
Click to expand...
Click to collapse
OK, first run the phone at 600 max, if it doesn't reboot in a day or two, increase it one step. Do this until it finally reboots.. Then you will know your phone's capacity.
And if it reboots at 600, then the problem might be something else.. And please tell me what rom and kernel you are currently using..
aashay960 said:
OK, first run the phone at 600 max, if it doesn't reboot in a day or two, increase it one step. Do this until it finally reboots.. Then you will know your phone's capacity.
And if it reboots at 600, then the problem might be something else.. And please tell me what rom and kernel you are currently using..
Click to expand...
Click to collapse
lguix rom supports which kernel and also for sonyxperia rom supports which kernel plss help me
Click on the second link in my signature. If the rom is present under 'Jellybean 4.1.2', then use either NOPE or Prometheus cm10. If it is present under sense, then use prometheus sense kernel.

[GT-i9195][cm11] - [ROM](Feb.2016)&[kernel](ECOACTIVE & ECOPLUG)(OC/UV)(20151210)

[GT-i9195][cm11] - [ROM](Feb.2016)&[kernel](ECOACTIVE & ECOPLUG)(OC/UV)(20151210)
This is a GT-I9195 CM11 kernel highly optimized to best possible performance and energy efficiency.
It may work on Slim (confirmed), AICP (confirmed) and Carbon Rom (confirmed) as well.
It will not work on any Samsung Stock based ROM.
- built from latest avalable CM sources
- CPU OC: 1998 Mhz (light: 1782 MHz) (default and max.)
- reworked freq- tables (unique 108 MHz-steps) for fast scaling
- CPU UV: -50mv (light: -25mv) (default, adjustable)
- GPU OC: freq steps changed to 192-400-608 MHz (light: 192-400-554 MHz)
- L2 OC/UV for extra performance (stock setting is a bottleneck, especially with OC)
- improved bus scaling
- RAM UV
- adjusted msm_thermal to prevent too much thermal throttling under heavy load
- added new "ECOACTIVE" governor and set as default
- added new "ECOPLUG" hotplug driver and set as default
- added FIOPS IO Scheduler and set as default
- added some more commonly used IO schedulers
- added fast random (and enabled via init.d)
- built with official gcc 4.8 with -O3 flags
"ECOACTIVE" is the ultimate governor for lag free performance and good battery life at the same time. It's based on interactive governor. It has a special input gain including the menu, home and back buttons. Separate input gain, fullspeed and eco/screen off phases minimize the use of high frequencys whithout slowing down the device noticably. The upscaling is more agressive during the input phase (default 1s). In the following fullspeed phase (default 10s, set to 0 for unlimited) full performance is allowed. The third phase is configured for battery saving usage while reading, watching videos, music listening or when the screen is off. This ensures maximum responsiveness and best gamig experience along with best possible battery life when reading, listening to music etc.
"ECOPLUG" is an alternative hotplug driver based on AutoSMP. It works much snappier on our device than the stock msm-mpdecision. On default setting second core is down when screen is off.
Everything is fully "pretweaked".
Flash from recovery, enyoy... no need to adjust anything via init.d or app.
Dont flash this kernel if you don't know how to fix problems after flashing !
Make a backup before flashing this kernel !
The hardware parameters are adapted near to the limits of my phone. This means this kernel will not work if your devices hardware cannot handle the OC/UV.
If you are lucky you run the fastest kernel available for your phone
If your phone doesn't run with the "lombartz kernel" you may try the "lombartz light kernel" with less agressive OC/UV.
My latest pure CM11 ROM build (Feb. 2016):
https://drive.google.com/open?id=0B-1RyGtdRvCwWEVfc0ZhTTRzdXc
If you use Xposed framework you need to flash XposedFix after ROM.
regards,
lombartz
...updated.
this kernel is amazing but i have a problem when i connect the smartphone at bluetooth radio. In this case my smartphone freeze and always reboot.
sorry for my english
Hi, thanks for yor feedback Have you already checked if you have the same problem with the last official CM11 kernel from 20150105 ?
regards,
lombartz
edit: tested with my laptop as bluetooth- speaker with no problems. My actual Version is heavily tweaked at the Moment but nothing changed with audio or bluetooth.
Anyone else with bluetooth- playback issues out there ?
edit: found a possible reason for the problem. hope it's fixed in new version (see OP)
Thank you for this. Any chance to include f2fs into the kernel?
bongster said:
Thank you for this. Any chance to include f2fs into the kernel?
Click to expand...
Click to collapse
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.
regards,
lombartz
lombartz said:
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.
regards,
lombartz
Click to expand...
Click to collapse
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
bongster said:
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
Click to expand...
Click to collapse
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.
If this one boots your phone doesn't like my OC/UV settings...
lombartz said:
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.
If this one boots your phone doesn't like my OC/UV settings...
Click to expand...
Click to collapse
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?
I never tried it...
bongster said:
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?
I never tried it...
Click to expand...
Click to collapse
Yes.
lombartz said:
Yes.
Click to expand...
Click to collapse
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
20150212 working nice with latest Carbon 4.4.4
can you please add option to underclock min CPU to 162/270 MHz?
spixy said:
20150212 working nice with latest Carbon 4.4.4
can you please add option to underclock min CPU to 162/270 MHz?
Click to expand...
Click to collapse
This is a technically useless placebo feature and doesn' t save any energy.
The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.
br,
lombartz
bongster said:
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
Click to expand...
Click to collapse
Hmm, the reason is the fstab.qcom, /cache and /data is expexted to be ext4.
Can be changed but I dont know how to allow both fs at the moment.
lombartz said:
This is a technically useless placebo feature and doesn' t save any energy.
The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.
br,
lombartz
Click to expand...
Click to collapse
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you
but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)
But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
spixy said:
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you
but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)
But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
Click to expand...
Click to collapse
I suppose you mean 50 mV ? The lower UV limit is reached at about 384 MHz anyway.
Youre right with hfpll. Only at 384 MHz the CPU runs with pll8.
If you undervolt @ 384 manually as much as possible you will find that you cannot go noticeably lower if you clock down further.
At the Moment I am testing other tweaks that should be more effective an give some extra performance.
bongster said:
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
Click to expand...
Click to collapse
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.
If it boots you are a tester for all the new changes ...
This Version will not run with ext4 /cache and /data partitions.
lombartz said:
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.
If it boots you are a tester for all the new changes ...
This Version will not run with ext4 /cache and /data partitions.
Click to expand...
Click to collapse
Thank you very much!
After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.
Update:
I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
bongster said:
Thank you very much!
After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.
Update:
I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
Click to expand...
Click to collapse
I am sorry. Should not publish something I did not test myself...
What OC Values did you use with f4ction ?
lombartz said:
I am sorry. Should not publish something I did not test myself...
What OC Values did you use with f4ction ?
Click to expand...
Click to collapse
No problem. I'm aware of the issues that can happen.
Normally I use f4ction as it is with 50uv. For the test I oc'ed to 1998mhz.

Categories

Resources