Database Develop

Overclocking XDAIIi

how do I overclock the XDA IIi , I heard there is software Pocket Hack Master 2005. Is it safe to overclock the XDA IIi?

If you try it the turbo mode in the speed settings in the control panel will be unavailable. It'll be the same as standard mode. Also the max clockspeed of the gfx chip/part wil be aft 54 Mhz instead of 108 Mhz which was set by the turbo mode. The latest version does work stable but that's about it. No real speed advantage to be gained because of the above. Perhaps some battery saving but since most of the power goes to the display I don't really see the use of getting a few extra hours of standby time from this while games slow down because of CPU usage polling. For the Alpine IMHO this is just something that is overhyped and not worth the hassle it brings.

I am using xcpuscalar_v2.88 to overclock my i-mate PDA2,the max speed i was able to use is 624 MH and it is very stable and all games and apps are running ok.
You may need to shut it off b4 you use the camera.
Otherwise it is very stable and fast,also saves power as it scales down the cpu to whatever speed your want.

xcpuscalar_v2.88
Thank you

me too, working fine with 624Mhz......unlike previous v2.87 crash with my XDA IIi !

sparcle said:
If you try it the turbo mode in the speed settings in the control panel will be unavailable. It'll be the same as standard mode. Also the max clockspeed of the gfx chip/part wil be aft 54 Mhz instead of 108 Mhz which was set by the turbo mode. The latest version does work stable but that's about it. No real speed advantage to be gained because of the above. Perhaps some battery saving but since most of the power goes to the display I don't really see the use of getting a few extra hours of standby time from this while games slow down because of CPU usage polling. For the Alpine IMHO this is just something that is overhyped and not worth the hassle it brings.
Click to expand...
Click to collapse
I think this is an excellent point.
I use my XDAIIi extensively for business use and was close to junking it - due to all the crashes and freezes I was suffering.
Then... I turned OFF Turbo Mode. I still use it extensively... only it doesn't crash anymore! The only problem I'm getting from time to time is needing to restart the phone via Flight Mode to be able to get a GPRS connection after using ActiveSync.
I own a licence for XCPUScalar, but haven't bothered to reinstall it or try the new version yet. I can't honestly say I've noticed any difference between Standard and Turbo Modes.
Go figure!

last stable frequency is 617 mhz .
Run mode is 247 x 2.5
Bus is 247
Lcd is 61
Memory is 123
Anyone more ?

Yeah...guess I shouldn't listen to things I read. Now my pocket PC has hard resetted.

I use v3.03 and my IIi works well upto 624Mhz. No crashes etc.... However as has been said already, the camera does not work properly with it, but if you downclock the CPU to 108Mhz then it's fine. I rarely use the camera anyway (i have a proper camera instead!!) so it's never a problem.

XCPU scaler 3.03 make my IIi hang, nothing more than that.

It shouldn't be hanging. It's more stable than previous versions i've used. Works great for me. I'd try uninstalling it, then removing any leftover files manually, then reinstall.

Advanced Linux users needed inside.

Hi.
Just a thought i had some time ago; why can't we get a small linux to run in Ram or SD?
Set the CPU to a minimum,
Shut down the HDD when we don't need it,
Share W-Lan when needed,
Share SD when needed,
etc. etc.
If possible, we could have a powerful WM without having Vista eating all the battery in the background.
Any thoughts?
Would it work?
Would we actually be able to run WM and share SD for 2? 4? 6? maybe 10 hours? or more....
Poof thought it would be possible, but unfortunately where he lives they also only have 24 hours a day ;-)
Deadnex proposed to use http://damnsmalllinux.org/ as a base for a project, and to me that look to be a good choice.
But then again, I don't know much about Linux or how to pull this of.
Anybody?
edit:
http://mnm.uib.es/gallir/cpudyn/ could help us?

that what I want to know... in Windows 7 ^^

hmm, good Idea, but how too... ?? maybe a really Unix Expert can porting a small unix to the ARM side, maybe the really better way ;-)

You would still have the trouble to access the hd, sd, wifi etc. from the ARM side, regardless of which OS you run as I understand :-/

yes, you´re right, that´s a problem of the BIOS if you comparing this issue with a PC :-(

Not very usefull, i tried it with a debian install onto my x86 side tweaked for battery life, as result i got a battery lifetime of 2h 45 minutes with display running all time VERY darkened. 3h 3minutes i readched with a really tweaked vista with auto shutdown nearly all Services disabled and reg tweaked for performance.
So as you dont get all ACPI functions enabled in debian you can't get the goal like a ARM linux shift would.

Neutron83 said:
Not very usefull, i tried it with a debian install onto my x86 side tweaked for battery life, as result i got a battery lifetime of 2h 45 minutes with display running all time VERY darkened. 3h 3minutes i readched with a really tweaked vista with auto shutdown nearly all Services disabled and reg tweaked for performance.
So as you dont get all ACPI functions enabled in debian you can't get the goal like a ARM linux shift would.
Click to expand...
Click to collapse
i reach about 4hours with windows7 but doing nothing at all (msn only)

I don't get it.
If the HD is off, CPU scaled down to...lets say 100Mhz, Linux running in Ram.
How can that use more power than having Vista running?

1. you cant scale it to 100Mhz afaik
2. BIOS / RAM / Grafiks continues to eat POWER
3. Also the grafiks chip isnt able to powerscale afaik
AFAIK
x86 architecture and ARM are very different caused by x86 does mostly running throu cycles and when it catches work it does its work, in the cycles, when theres no work it does HLT (asm signal to hold for some cycles to save power =)
ARM does it in another way it has bits to be set, then its going to power the parts that cycles thru the work when the bit is set.
that causes our 400mhz ARM cpu hold battery power up to 96h and a double that fast cpu x86 only last 4h ?! you see it should be lets say 48h if they where same architecture.

Well, i'm not saying your wrong
But as to my knowledge it is very possible to Scale a processor.
It's being done every day (Over/Under clocking), but i guess it can only be done via Bios?
I did this myself on an Asetek system some years ago, surprisingly how much extra you can get out of a CPU when you have it at -20 Celsius.
Even so, if the HD is off, Linux running in Ram, Screen in power save/or off it should still last a fair bit longer than any Windows version ever would.
But perhaps it's way to much work to get an extra hour or two???

Okay you could possibly get that, but the normal frequency scaling mobile CPU's have, they have a feature (CPU function) to scale the processor while runtime ! i think that wont have the 100Mhz !
you could do it in the bios side (change clocking of the Processor and turn power at all down. but i never would try to rev engeneer the buildin bios from the shift to make manual frequency scaling available ! Cause that would be MUCH work & a chance to brik the device ! also what would i do with a 100MHZ x86 Shift with nearly everything shut down but running let be very optimistic 10h after all tweaking?
i think it would be more interesting in geting linux to the ARM side !
You can have that side nearly 100h online with GSM enabled and partitaly browsing the web writing some stuff !
i recommend the ARM side !
Greets

Neutron83 said:
i recommend the ARM side !
Greets
Click to expand...
Click to collapse
I agree with you on that one, but no matter how you look at it, the ARM side is handicapped.
No Wifi, No External storage, No USB Host
For the above to work we need the x86 side to be running, and I think it will stay that way until somebody figures out a way to solder in a HW brigde

X1 overclock...

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

Post your SetCPU Profiles

748/245
Temp < 50C 245/245 100
Screen Off 245/245 90
Charging/Full 719/245 80
Battery <40% 604/245 70
All ondemand

Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery <100% 768/245
that's listed by priority

Hungry Man said:
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery
Click to expand...
Click to collapse

Screen Off: 245-480
**Stock is 245-245. 160 as a minimum seems to produce a LOT of wait time from when the call is coming in to when the phone lights up. More than 245 seems to whack the battery.
Keep in mind, when you wake up your phone, this Screen Off SetCPU Profile is active for at least a SECOND or two. The problem is that if you have your maximum at 245, you experience BAD lag trying to pull the lock bar down. At 245-480, the maximum is high enough that a) the lock bar pulls down as smoothly as a stock Eris, and b) even if SetCPU takes a couple of seconds to change the profile, at least you're at 480mhz for the first scrolling of the screen left/right (so you don't embarass yourself in front of iphone users). Anything higher than 480mhz is a different voltage. Almost the whole time your phone is 'Screen Off', it will be operating at 245 anyway. So 480 is a good setup for it to jump up when a call comes in (to play the ringtone and show the picture a little faster, and for the lock screen bar to pull down smoothly, and the first second of SenseUI to be smooth enough, until your phone changes the profile to your <100% profile.
Battery <100% 245-806
** Zanfur's take on how this processor clocks up/down its speeds will lend itself to a general wisdom that 768mhz isn't really slower than 806mhz, and that in instances of high variability of clock speed (aka you have some Power Save bias in SetCPU keeping it lower/higher at random, or you're doing very intermittent tasks), the processor rests at 768mhz more quickly, and wastes less time/'effort' changing speeds. Changing to 806 is another 'step' altogether, where 245 to 528 is one 'step', and that to 768 is another 'step'. Going to 806 is absolutely another step yet after that (which means your phone responds a LITTLE slower because it has one more step to 'throttle' up to). BUT, if you're doing a dedicated task, such as running a Linpack benchmark (which is a terrible benchmark anyway) your phone will move faster at 806, or if you're playing a game, or playing a video... generally the processor will stick at one speed (and not have to 'step' up or down), so 806 is faster. I clock friends' phones at 768 to avoid problems, keep it clean, etc etc. Some people put the minimum here at 160mhz, but I feel that this is too low (and another 'step', just like 806 is over 768, 160 is another step down from 245).
Charing (any) 480-806
** I keep the minimum here HIGHER than when the phone is on battery, because I'm less concerned about how much energy it's consuming, and having a minimum of 480 makes the phone very snappy no matter what, from the second you touch it
Overheating > 48C 122-528
** Clock speed here matters a LOT less than just getting your phone out of the heat. This phone doesn't overheat because it's overclocked, it overheats because you run it at an overclocked speed for a long time. MOST overheating instances are from wireless tethering and from broken charging systems (that keep trying to charge the battery and generate a lot of heat). The 'Failsafe' profile here provides a 'notification' option which I HIGHLY recommend.
My ex-gf's Eris actually CAUGHT FIRE, as in it looked like it was a zippo, right above the volume buttons. It used to overheat EVERY NIGHT that it was on the charger, excessively, so hot that you couldn't touch it. For a month or two it did this, actually, and caused no real damage to the phone. Since the night of the Flame (you can actually see the melted plastic and even on the outer case - she has a blue snap shell case on it that is melted as well), the phone has NOT overheated even one time on the charger. (Sorry for the story, it was a waste of time).
The point is that, the first time it happened, her phone System sound was on Silent, and she DIDN'T hear the notification that her phone was overheating. Apparently it doesn't matter (or she's very lucky her phone isn't damaged in terms of its operation!) how much it overheats for some people, but I like to have it warn me it's getting close to 50C. The notification's the important part there (so u can cool your eris), not the clock speed.

@pkopalek I like your settings you posted with a full description of each. I changed my settings to yours and give it a day or so and will report a status update as to performance quality

I've never lagged at 160mhz =p but that could just be my phones/ roms.

Hungry Man said:
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Click to expand...
Click to collapse
my audio skips and it won't wake up when in a call at 160mhz. I keep mine at 245mhz minimum to keep phone working smoothly.

What does the different prioritys mean? Is that like what one its.focused on more?
Sent from my FroShedYo.V5 using XDA App

How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo

sgbenton said:
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
Click to expand...
Click to collapse
When a processor is made at the factory, it will always have flaws in it. The chip is tested to see what frequency it is stable at. So that is the speed that is stamped on the chip and the frequency that it is set at to operate for the consumer and not have any problems. When you overclock a processor, you are bypassing the frequency that the chip as been deemed to be stable at. After that, there is no set speed that your processor can handle, because each one is different according to the flaws it might have.
So in short (what I'm trying to say), the processor in your phone just can't handle those without causing problems. That's why when you overclock it, it's kind of a trial-and-error process to see what speed you can get out of it, but be careful, because too high can cause permanent damage.

Using Interactive governor
Main: 787/710
Temp > 42.1 C: 480/245 Priority: 100
Screen Off: 480/245 Priority: 95
Charging/Full: 480/245 Priority: 90

My own take on the eMMC brickbug.

We all know about the emmc bug that has affected our note 4, as I saw on the "Fix'd" thread someone solved their emmc brick by baking the motherboard, like people did when their PS3s were failing to reball the GPU.
So this means that at least some instances of the bug, if not most, are caused by the emmc being desoldered by the heat of the CPU, which is soldered on the same side of the PCB, right under it (Samsung ePOP technology). As an introduction to my possible "solution" to it I want to say this: I recently bought the Note 4, after I broke something on my Note 3's mobo. A big difference between the two that I observed is that on my N3 i could undervolt about 25-30 mV lower than the stock values and that was it,more and it would reboot, I forgot the pvs bin no. , but it was a either 3 or 4, the good ones. Well, on my N4 after I checked my pvs bin ( pvs10 ), I put the PVS10 voltage table on the phone , and that was -65 mV compared to stock, after that I undervolted -25 mV more and everything is perfect : No deep sleep problems, no audio problems with screen off (While also using V4A), 85K Antutu Score and CPU Throttling Test is showing a very big improvement on the heat dissipation: it now underclocks more easily (2.64-2.45-2.22-2.0 but it mostly stays at 2.45 and from time to time going to 2.22-2.0 for a few seconds), using stock values it was dropping to 1.72 after 2 seconds on the test then going up to 2.0 for a few moments then back to 1.72 and mostly staying there. I want to add here that the Sub-Ghz voltages can be undervolted even more to the values of the pvs15 table without any problems.
So , my "solution", not really a solution but more like future proofing the health of the ePOP package (S805 AP with RAM and EMMC soldered right on top of it) is to :
1. Check your pvs bin.
2. Apply specific voltage table values in KA/Synapse .
3.Undervolt -25 more and test for stability, and if your phone can handle it, undervolt even more, to the maximum possible ( sillicon lottery ).
P.S: If you are more experienced user and have H/W capabillities, you can also add what I did to my Note 3: I opened the phone, removed the pink heatpad it had, and in place of it I put a decent amount of Arctic MX-2, added a very thin aluminium heatsink (from car ECU) , then a blop on the heatsink, one on the CPU and voila! In the cpu throttling app the phone was sustaining 2.57 Ghz for like 2-3 minutes , then underclocking a bit and then back to 2.57 Ghz; idling at around 30 C even hitting 27 C, and when normal using going around 40-42 . Sadly while doing test (i had a few attempts before getting the perfect amount of Paste ) I broke the headphone band, then when replacing that I broke the MIC and Speaker little gold legs on the USB pcb, and then just sold the display and batteries and bought our beloved Note 4, which is a really nice upgrade!
EDIT : h t t p : / / w w w . myfixguide . c o m /manual/samsung-galaxy-note-4-disassembly/ it shows here the said package , they only mention "3GB RAM chip and Qualcomm APQ8084 enclosed chip", but as I read the technology combines RAM and MLC (the internal memory) on the same chip.

Hi bro, do we need custom kernel to do that, just the undervolt thing ?

i'm wondering whether emmc can be upgraded to a faster one, which will then make the phone way snappier?

Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI