Related
Hi to all, i would like to open a new thread on the following topic: we have seen various opinions about the safety of overclocking. With CPUScaler under Faria's 3.0.0.0 ROM, i can achieve sustained rates at 312 MHz. At the same speed, omapclock would reset my wizard. In my understanding, the TI omap 850 is temperature protected - and therefore any stress due to excessive power dissipation should be intercepted by the internal temperature probe and would result into a system reset. However, it would be interesting to know if anybody was actually able to COOK one processor with overclocking. Any information about it? what is your opinion?
I dont think this omap processor has been actualy been cook but i think that even if you get at a higher speed the system will be too unstable to run, some programs may not work at high speeds because they were not made for that speed power. (if im wrong correct me) the wizzard was made so that the processor would not consume alot of battery power.
what exactly does over clocking do, I think I have the general idea of what it does...... and what do you over clock 2?
overclocking changes the frequency at which your phone's processor works, thereby making it faster. You use batterystatus to overclock. Most of us overclock to 243 or 273,i believe
Your upper limit depends on your particular device. Some can only overclock a few mhz past the stock 201mhz. Some can overclock to 299+.
But it basically allows your device to perform faster at the cost of battery, heat and technically longevity.
Is there any application, such as BatteryStatus that is there for OMAP processors, that can handle the Qualcomm 7201 processor?
1. It would be nice to underclock the phone, in cpu scale mode, so it saves the battery usage, i.e. in idle mode the speed drops to 300-400Mhz giving extra life from battery.
2. Overclocking to 600+Mhz would be nice when using applications such as iGo 8.
Hope you guys got the idea
No
Just use the search feature.
TDO
i am waiting for it too in order to make underclocking and save bbattery
My smug friend just got his N900 up to 800mhz. And i want to get into the competition, is there any way to overclock the X1?
Sorry, the MSM720X chipset is really bad at overclocking, there's the app "nueDynamicClock" which CAN overclock but with huge issues, and small advantage...
noONExda said:
Sorry, the MSM720X chipset is really bad at overclocking, there's the app "nueDynamicClock" which CAN overclock but with huge issues, and small advantage...
Click to expand...
Click to collapse
It's actually called NueOverclockTest, but you are right, it's terribly unstable and will freeze your phone 95% of the time. When it works, however, it's very nice.
No2Chem, the only developer who seems to know how to overclock the Xperia processor, dropped off the face of the earth in September 2009. My theory is that Qualcomm kidnapped him and is forcing him to use an underclocked Palm M505 as torture.
!?!
see this http://forum.xda-developers.com/showthread.php?t=725290
Xperia X1 "overclock"
Ive been investigating the same situation because i would love it if my X1 ran faster to keep up with more modern smartphones out on the mark these days. So heres what ive found out thus far;
- With stock settings, the Xperia X1 cpu (im using MSM7201A 528mhz cpu) is actually underclocked to 384mhz when the battery is being used, and then further underclocked to ~225mhz when the phone idle's for 5000ms.
- However when you apply external power to the phone, the cpu core runs at its full 528mhz speed. I found these power saving techinques employed by HTC or SE or QUALCOMM to be useless, because ive been running my phone at full speed, highest voltage, and the battery life difference is un-noticable.
- Here what you should do to at least make sure your X1 is running at 528mhz (which made WM actually significantly faster) to give yourself a psuedo-overclock;
1. Download "nueDynamicClock-122-v1.3-pack.zip" which i have attached to this post. Extract, copy the contents over to your X1 and run the SETUP file from your PHONE
1b. If you get a security error, you have to install the "EnableRapi.cab" file which i have also attached
2. Once installed, the cpu frequency settings can found it you click on Starty >> Settings >> System. There is a new "processor" icon, and all the settings can be found in there.
The program is very flexible on how you and when you want your processor to run so experiment to find your best needs. I keep my processor set at a constant 528MHZ @ 1.325V and i get the best performance out of that.
Anyways hopes this helps, give some feedback if possible. CHEERS :
I have just try it and it's look to be really faster on battery !!!
I will see for power consumption and stability in some days but the first thing is impressive !
Thanks
have you noticed anything with battery consumption yet? the only changes ive noticed are the obvious, such as running/watching near 720p quality videos on battery power and multitasking the **** out of the phone. overall general performance has definately increased from my experience, and i am glad i found this tool. Couple it with the right rom and you now have one of the fastest windows mobile phones (besides HD2) on the market. YAYAYAY! xperia x1 is still useful!!!
Yes I can confirm now that the battery consumption is not different than before !!! and for the moment, no bug at all!
And the speed of the phone is definitivly better !!!
Very great !
I'm surprise to don't see more reply on this topic, this soft is a must to have !!!! My Xperia will have some nice day more
I'm gonna install it and try it as soon as I wake up tomorrow
I will try this one and see the difference.. thank you for the tip..
Thank you for your tips!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ssingh819 said:
Ive been investigating the same situation because i would love it if my X1 ran faster to keep up with more modern smartphones out on the mark these days. So heres what ive found out thus far;
- With stock settings, the Xperia X1 cpu (im using MSM7201A 528mhz cpu) is actually underclocked to 384mhz when the battery is being used, and then further underclocked to ~225mhz when the phone idle's for 5000ms.
- However when you apply external power to the phone, the cpu core runs at its full 528mhz speed. I found these power saving techinques employed by HTC or SE or QUALCOMM to be useless, because ive been running my phone at full speed, highest voltage, and the battery life difference is un-noticable.
- Here what you should do to at least make sure your X1 is running at 528mhz (which made WM actually significantly faster) to give yourself a psuedo-overclock;
1. Download "nueDynamicClock-122-v1.3-pack.zip" which i have attached to this post. Extract, copy the contents over to your X1 and run the SETUP file from your PHONE
1b. If you get a security error, you have to install the "EnableRapi.cab" file which i have also attached
2. Once installed, the cpu frequency settings can found it you click on Starty >> Settings >> System. There is a new "processor" icon, and all the settings can be found in there.
The program is very flexible on how you and when you want your processor to run so experiment to find your best needs. I keep my processor set at a constant 528MHZ @ 1.325V and i get the best performance out of that.
Anyways hopes this helps, give some feedback if possible. CHEERS :
Click to expand...
Click to collapse
cheers mate works like a charm even when changing panels. everything loads faster even the coreplayer. I have X1i with the R3A rom 528MHZ @ 1.325V
everythings stable also thanks alot!
I'm quite skeptical. I'm pretty sure that the X1 is NOT underclocked when on battery power. If someone shows me before/ after benchmarks, I'll be a believer, but I think this is the placebo effect.
If overclocking works, it will also speed up the boot time, won't it?
I've tried independently on counting startup time. But I don't see different between Max Performance and Default.
Anyway, is it safe if I try it on X2?
mymailx said:
If overclocking works, it will also speed up the boot time, won't it?
I've tried independently on counting startup time. But I don't see different between Max Performance and Default.
Anyway, is it safe if I try it on X2?
Click to expand...
Click to collapse
there is an option in the app which is for starting the app after the boot sequence...that should be the reason why there is no difference in boot time
to all you haters
ok first of all;
1. everyone HAS TO REMEMBER that i first ran this application on a STOCK R3A ROGERS CANADA ROM. what i reported is what i noticed, and the difference between the OS running at 384mhz and 528mhz on battery certainly isnt a "placebo" effect. You might be using a different rom, where the cook changed the cpu frequency settings himself but i certainly dont know. If you dont believe me that is underclocking issue is actually an issue, i suggest you google search the topic and check out how many hits you get.
2. The Xperia X2 is running the exact same MSM7201A 528 mhz cpu soo X2 owners should definately check to see if their cpu's are underclocked.
3. Finally i was just trying to help, i love my X1 and i want people to love their X1's too.
ENJOY EVERYONE lets keep this phone ALIVE
installing it right now...
Its amazing.
successfully overclocked x1
hi,i was able to oc my x1 to 672 mhz using the guide in the htc hd forum.try it out.the phone fell faster than ever.
great work. my phone is deffinately running faster
Moto Z2 Force is a blazing fast smartphone. This out of any doubt.
Fore sure it is the fastest phone I've ever worked on.
On the shelf a lot of phones seem to be fast, BUT when you install over 200 apps on them and you are using 7 home screens full of widgets (ehm...) things become "a bit" different...
Not this time: over 200 apps installed didn't change it's fantastic speed. It's like working on an iPhone.. BUT this *is* doing something too! :laugh:
What's more interesting is that... it can be even faster too!!!
Many smartphones can be sligtly overclocked because of heating and battery life needs that lead manufacturer to lock frequencies to lower values respect of SoC capabilities. BUT usually root isn't enough to have overclock access, since higher frequencies need a modified kernel to be unlocked..
But Moto Z2 Force is not "one of many" smartphones...
Motorola confirmed my first impression I had on my old Griffin (Moto Z): they are making smartphone for "geeks"!
Moto Z2 force is using an 8 core Snapdragon 835 using "big-LITTLE" architecture:
- 4 high performance Kyro 280 cores clocked between 345 and 2361 MHz (big)
- 4 low power Kyro (???) cores clocked between 672 and 1900 MHz (LITTLE)
(frequencies adopted on EU unbranded XT1789-06... on different markets/versions they could differ...)
Obviously, low power cores work most on screen off conditions and during light tasks, while high performance ones enter the game when more performances are required as we have already seen on many similar architectures...
What's particularly interesting is that 2361 MHz is NOT the higher frequency of Kyro 280 and 672 MHz is NOT the lower frequency low power Kyro can work before going to deep sleep condition...
In fact big cores can work up to 2457 MHz (in a single step) and LITTLE ones down to 300 MHz (with 300, 364, 441, 518, 595 MHz intermediate steps available!)
What's is even more interesting is that simply by having root and a (great!) app called Kernel Adiutor - available on Play Store too - we can go to change (temporary or permanently) these values to overclock and/or underclock our system, eventually having better performances and/or better battery lifes...
I'm testing this and results are confirmed (by Kernel Adiutor statistics too...) and interesting: Z2 Force is not a device prone to overheat (like was my old Griffin instead... ) and so it seems to work with no issues at all @2457 MHz with interesting Geekbench 4 results as attached (please note that results are taken with all my 200 apps still installed & working... on lighter conditions they could be quite better too...).
In any case they are better than any Android Device recorded to date in Geekbench 4 charts... expecially for Multi-Core results...!! :highfive:
Underclock LITTLE cores from 672 MHz to lower values could (and I underline could...) improve battery life expecially during screen off conditions, BUT there are considerations to be taken:
- lower frequencies involves more time out of "deep sleep" condition too...
- on many devices adopting very low frequencies often lead to slow (or difficulties in...) "screen back on" operations
BUT there are MANY frequencies to eventually test so... games are open!!!
In any case, Motorola again! :good:
Feedbacks and eventual Geekbench4 / Antutu results on different clock settings are the welcome...
This is with the pantheon Kernel, prior to poking it.
https://browser.geekbench.com/v4/cpu/4880631
I'm doing some little tune up experiments with frequencies and these are some first results:
- lowering lower working frequency of LITTLE cores up to 345 MHz (from 672 MHz) seems to create no issues or delays on powering on screen even using fingerprint sensor...
On the other hand I'm still not so sure of eventual power saving benefits (my Z2 setup is already very good during screen off time with an average consumption of about 1,5%/hr... so eventual differences are minimal)
- I've to doublecheck it (more confirms needed...) but I'm quite sure big cores are clocked at faster frequency (2.45 GHz) during boot up, then (when exactly?) lowered to a max frequency of 2.36 GHz... this seems to me simptom of a very well tuned up system...
Does somebody have voltages/frequencies tables for our phone?
enetec said:
I'm doing some little tune up experiments with frequencies and these are some first results:
- lowering lower working frequency of LITTLE cores up to 345 MHz (from 672 MHz) seems to create no issues or delays on powering on screen even using fingerprint sensor...
On the other hand I'm still not so sure of eventual power saving benefits (my Z2 setup is already very good during screen off time with an average consumption of about 1,5%/hr... so eventual differences are minimal)
- I've to doublecheck it (more confirms needed...) but I'm quite sure big cores are clocked at faster frequency (2.45 GHz) during boot up, then (when exactly?) lowered to a max frequency of 2.36 GHz... this seems to me simptom of a very well tuned up system...
Does somebody have voltages/frequencies tables for our phone?
Click to expand...
Click to collapse
They're in the kernel. I tried to do normal edits to lower and increase, but it did something weird and just parked them at 30mhz after compile...
Edit: https://github.com/Uzephi/kernel_nash/blob/upstream/arch/arm/boot/dts/qcom/msm8998-v2.dtsi
There is the link to the file that controls the frequencies for each bin of our phone
Uzephi said:
They're in the kernel. I tried to do normal edits to lower and increase, but it did something weird and just parked them at 30mhz after compile...
Edit: https://github.com/Uzephi/kernel_nash/blob/upstream/arch/arm/boot/dts/qcom/msm8998-v2.dtsi
There is the link to the file that controls the frequencies for each bin of our phone
Click to expand...
Click to collapse
Very complex!
I will take a deep look at this as soon as I would have a bit of time...
enetec said:
Very complex!
I will take a deep look at this as soon as I would have a bit of time...
Click to expand...
Click to collapse
Essentially, little CPU has one speed bin and frequencies available from 300-1900 and big CPU has 4 speed bins with frequencies from 300-2592. Top end changes depending on your bin. I.E. silicon lottery. Speed bin 0 can step higher than bin 3
Edit: to find speed bin, it's usually in proc/kmesg or proc/last_kmesg. Needs root to read
Uzephi said:
Essentially, little CPU has one speed bin and frequencies available from 300-1900 and big CPU has 4 speed bins with frequencies from 300-2592. Top end changes depending on your bin. I.E. silicon lottery. Speed bin 0 can step higher than bin 3
Click to expand...
Click to collapse
Yes, on my own device max available speed is 2457 MHz... but my doubt is, how a single device (using same software) would choose between different bins?
Anyway is voltage the complexity I was referring to... at first look It seems not using a fixed one for a single frequency as on my old LG G2 but a range... I've to look better at it...
Some first interesting results from tests have been achieved...
I will post a more detailed report in one day or two...
enetec said:
Yes, on my own device max available speed is 2457 MHz... but my doubt is, how a single device (using same software) would choose between different bins?
Anyway is voltage the complexity I was referring to... at first look It seems not using a fixed one for a single frequency as on my old LG G2 but a range... I've to look better at it...
Click to expand...
Click to collapse
It's quite simple. At boot the kernel reads all "devices" on the computer (our case, the phone) and runs checks at low level on the hardware for software revisions, serial numbers, Mac addresses and guess what? The speed bin embedded in the chip. It then runs a cmdline for the system to read the results to access the devices and use the kernel correctly. This is how I manipulated the system to read the bootloader as locked. On my kernel, go to developer options and you will see you can toggle bootloader unlocking. This is because the cmdline tells the system we are still locked.
Uzephi said:
It's quite simple. At boot the kernel reads all "devices" on the computer (our case, the phone) and runs checks at low level on the hardware for software revisions, serial numbers, Mac addresses and guess what? The speed bin embedded in the chip. It then runs a cmdline for the system to read the results to access the devices and use the kernel correctly. This is how I manipulated the system to read the bootloader as locked. On my kernel, go to developer options and you will see you can toggle bootloader unlocking. This is because the cmdline tells the system we are still locked.
Click to expand...
Click to collapse
Nice!
Anyway I saw official documentation of SD835 speaks about 2.45 GHz as max frequency... so other speed bins are for special/overclocked lots probably...
enetec said:
Nice!
Anyway I saw official documentation of SD835 speaks about 2.45 GHz as max frequency... so other speed bins are for special/overclocked lots probably...
Click to expand...
Click to collapse
Cherry-picking a commit by Flar2 on his Pixel 2 kernel that enables the 2.5Ghz on all bins. Hopefully it works.
Uzephi said:
Cherry-picking a commit by Flar2 on his Pixel 2 kernel that enables the 2.5Ghz on all bins. Hopefully it works.
Click to expand...
Click to collapse
Have you found (during you searches...) where is the routine which changes max frequency from 2.45 GHz to 2.36 GHz after boot?
enetec said:
Have you found (during you searches...) where is the routine which changes max frequency from 2.45 GHz to 2.36 GHz after boot?
Click to expand...
Click to collapse
Those are both different bins. Maybe it loads one then the other? In any event all bins will be 2.5 if this works. Building now
Edit: checking my device, I don't go down to 2.36, max on mine is 2.45
Uzephi said:
Those are both different bins. Maybe it loads one then the other? In any event all bins will be 2.5 if this works. Building now
Click to expand...
Click to collapse
Uhm... I'm not so sure this is bin related, since max frequency (2.45 GHz) still remains usable, but no more used after boot (it can be re-enabled by Kernel Adiutor anyway)... this is more a simple setting IMHO...
enetec said:
Uhm... I'm not so sure this is bin related, since max frequency (2.45 GHz) still remains usable, but no more used after boot (it can be re-enabled by Kernel Adiutor anyway)... this is more a simple setting IMHO...
Click to expand...
Click to collapse
That's your bin which is set at boot... My bin gives me 2.45 by default... I am not rooted and haven't made changes. See attached screenshot
Built and works... See screenshot. All I did was change kernel. No other settings done. Next it to try UV
Uzephi said:
That's your bin which is set at boot... My bin gives me 2.45 by default... I am not rooted and haven't made changes. See attached screenshot
Click to expand...
Click to collapse
Nope. Your app reports only min & max available frequencies but not the used ones... In fact, if you look at your screenshot, min frequency is reported to be 300 MHz for all CPUs, BUT if you look at your frequencies at the screenshot moment, they are respectively 672 MHz for LITTLE & 345 MHz for big cores, that are the really used as min frequencies as stock.
If you install Kernel Adiutor all will be clearer for you... it reports all this in better way...
Uzephi said:
Built and works... See screenshot. All I did was change kernel. No other settings done. Next it to try UV
Click to expand...
Click to collapse
It works for sure... because probably new frequencies are still not used... see my previous post.
Try it out then ?
Edit: be sure to flash twrp boot image, then kernel then root. SU and Magisk lose root when flashing our kernels right now and will pull backup kernel from backup boot image
Edit 2: if you also look at my "after" screen, the CPU was pegged at 2.0 and 2.5 respectively due to just booting up and loading assets.