Hi there,
after looking for some OC programs for my PDA i found this PHM software.
so i have decided to check its ability to make the changes to my Asus My Pal A639/GPS.
i have noticed there is another post here about the Asus A696 which is pretty much the same PDA,
which is having the same problems i am experiencing.

currently the software in trial mode.
as it is i am facing a problem with my Asus My Pal A639, which has Intel PXA-270.
when ever im trying to test other speeds than the ones from OEM, even lower speeds,
as 104,221,332,416 the screen disappears and only solution is restarting the PDA.

after disabling the OEM AUTO speed, and fixing to 416 (highest speed), i do manage to
test all range of speeds. although i can test its range of given speeds, every test i take in the end
results in the PDA gets hung over, and i have to restart.

one thing i have noticed while playing whit all the definitions was:
only one speed get away with the test :
CPU:104 , BUS:104 , RAM:52 , LCD:52
after setting this speed with PHM, the PDA slows down to 104, and wont be able
to go up until i remove it from auto run and reseting. another thing i have noticed, while it is on PHM 104
i have some blinking lines every now and then all over the screen,
which doesnt appear when working on the OEM 104 (low speed),
and another thing i have noticed that the WIFI slows down also, which doesnt happen in
OEM 104 (low speed) also.

my guess is the program doesnt have correct speed configuration with ASUS products having PXA-270.
or that Asus has made some other hardware settings for the PXA-270 products of their MFG, which may cause the PDA to respond unexpectedly on other speed managers.
i get to that conclusion since any speed setting will result in complete system slow down, unstable work, blips or blinks on the screen, other unstable hardware as GPS or BT, and even worse than that repeated
hangups and resets.

maybe the problem is because its in trial mode ?
or maybe is there a way to make the program get every parameter fixed on speed i want ?
because at the moment i have to make a selection from typical set of available pre defined speeds.
what can u recommend as a solution to make it work ?

thanks in advance to all responders.

baracuda - 30 July 2008 07:07 AM

Hi there,
after looking for some OC programs for my PDA i found this PHM software.
so i have decided to check its ability to make the changes to my Asus My Pal A639/GPS.
i have noticed there is another post here about the Asus A696 which is pretty much the same PDA,
which is having the same problems i am experiencing.

currently the software in trial mode.
as it is i am facing a problem with my Asus My Pal A639, which has Intel PXA-270.
when ever im trying to test other speeds than the ones from OEM, even lower speeds,
as 104,221,332,416 the screen disappears and only solution is restarting the PDA.

after disabling the OEM AUTO speed, and fixing to 416 (highest speed), i do manage to
test all range of speeds. although i can test its range of given speeds, every test i take in the end
results in the PDA gets hung over, and i have to restart.

one thing i have noticed while playing whit all the definitions was:
only one speed get away with the test :
CPU:104 , BUS:104 , RAM:52 , LCD:52
after setting this speed with PHM, the PDA slows down to 104, and wont be able
to go up until i remove it from auto run and reseting. another thing i have noticed, while it is on PHM 104
i have some blinking lines every now and then all over the screen,
which doesnt appear when working on the OEM 104 (low speed),
and another thing i have noticed that the WIFI slows down also, which doesnt happen in
OEM 104 (low speed) also.

my guess is the program doesnt have correct speed configuration with ASUS products having PXA-270.
or that Asus has made some other hardware settings for the PXA-270 products of their MFG, which may cause the PDA to respond unexpectedly on other speed managers.
i get to that conclusion since any speed setting will result in complete system slow down, unstable work, blips or blinks on the screen, other unstable hardware as GPS or BT, and even worse than that repeated
hangups and resets.

maybe the problem is because its in trial mode ?
or maybe is there a way to make the program get every parameter fixed on speed i want ?
because at the moment i have to make a selection from typical set of available pre defined speeds.
what can u recommend as a solution to make it work ?

thanks in advance to all responders.

Hi baracuda,
Welcome to the forums!

When you say you are testing a range of speeds does that mean you are running tests on all speeds that are available in the Speed configuration module list? That list is quite generic and I would recommend testing a single speed at a time instead of batch testing them all. You are probably hitting an unstable speed that is hanging up your device.

Try the 624MHz, 520Mhz, 416Mhz, 211Mhz and the 104Mhz - these are pretty standard and should work on your device. Please post the results here and I will try to give you further instructions on how to proceed.

I have more or less the same problems with my IPAQ 614c, and its ARM920T pxa270 processor. I got PHM from IPAQchoice.com, and its version 4.33.051.

When doing the speed config I get green lights for ever cpu setting from 624 down to 221. 208 doesnt seem to work but 104 does. When trying the higher settings - 728, 663 - the device freezes. After soft reset their indicators are still grey though, no red lights. Also No speed above the native 520 works when I try to set speed, even though they passed the test. Again the device just freezes and has to be soft reset.

With 553 it doesnt freeze, but the screen gets really wobbly and flickers. This also happens with some of the lower settings, but not all.

For me it also seems that only 208-104-104 settings work at all, though not all of those.

Ive tried disabling the built-in scalers but no difference at all.

Also, I cant remove favourites once theyre set. But after a PHM induced freeze and a soft reset all favourites disappear.

Its not a huge problem, since I can go as low as 312 which gets me more battery life, but I must say the program (or maybe version) feels buggy and I would sure like to have more versatitility..