HELP! PXA clocker killed my TX :/

[Nobitsu]

Help, I tried PXA clocker and everything is blank and I cant reset or hard reset!!

[_Em]

You have to wait for the battery to drain (backlight dies); then wait an extra day, then plug it in to charge. Eventually it'll start back up. You set your CPU or Bus speed higher than your T|X could go (you probably went above 520MHz), and so the reset button won't work (it's on the bus). Other than that, your T|X is fine.

[Nobitsu]

I dont remember what I set it at but I did remember it was below 520 mhz and I pricisely set it for Blazer only.

When it starts back up should I get rid of PXA clocker?

[_Em]

No, I'd use it to start at the defaults and slowly work your way up to 520MHz; when you get a frozen screen, make sure you never set the values above that. A regular frozen screen can be reset with the reset button.

If you continue getting solid lockups randomly below 520MHz, I'd recommend you get Palm to replace your unit (assuming it's still under warranty). There are probably further issues that will rear their heads as time goes by.

[Nobitsu]

Damnit
I just got it working again and then I decided to try underclocking it.
I tried to underclock it to 200 mhz and it died again. :/
I think I shouldn't even bother with it because obviously it doesn't work.

[headcronie]

You might want to try a different program.
http://www.clievideo.com has Lightspeed. :)

[tosbsas]

or even better

www.palmpowerups.com -warspeed

Ruben

[headcronie]

The validity of your statement, remains the the users discretion. ;)

[tosbsas]

??? cause of better?? (:-))

Ruben

[Nobitsu]

I hope it didn't screw up my palm because it's acting weird now. It kept reseting more than normal so I did restored Via NVbackup and I tried to start Netfront but it crashed and more over it tried to connect to the wrong wireless server when I precisely told told it to connect to another but it still connected to the server. :/ and then it netfront and blazer both didn't work so I tried a hard reset and then tried blazer and it worked so then I tried to us NVback up again and it didn't work but it worked before which is quite odd. :/

I think I'll try Warpspeed next. lol

[rbeef]

I'd be interested in an application that would reduce the clock rate when the CPU is idle, similar to powerd on FreeBSD. Here is what it does. Is there something in the Palm world that does this? (Please read the description below to understand what I am talking about.)

The powerd utility monitors the system state and sets various power control
options accordingly. It offers three modes (maximum, minimum, and adaptive)
that can be individually selected while on AC power or batteries.

Maximum mode chooses the highest performance values. Minimum mode
selects the lowest performance values to get the most power savings.
Adaptive mode attempts to strike a balance by degrading performance when
the system appears idle and increasing it when the system is busy. It offers a
good balance between a small performance loss for greatly increased power
savings. The default mode is adaptive.

[dmitrygr]

DynaClock does that. Check it out at palmpowerups.com

[Nobitsu]

I tried Dynaclock and then my palm started to scream. Is that normal? I can seem to get rid of the screaming either. I used the Whineaway software and I tried reset and getting rid of the program. It's screaming pretty loudly too :\

[dmitrygr]

if you delete dynaclock and do a softreset systsem is in exactly the same state it was before dynaclock installation. are you sure you deleted both parts of it?

[Nobitsu]

Yeah, both parts are gone and the screaming now starts to turn off and on it wasn't like that before. I'm going to try a hard reset.

[Nobitsu]

The screaming is still there now but that's normal because whinehack killed it. Stupid scream thing. I wish palm will fix that problem in the next rom update.
Stupid palm crashes on it own. I should have gone for a pocketpc instead because the palmos is terriblyunstable. eg. need 3rd party hacks just for it to be stable which sucks away more of my money :/

[tosbsas]

what do you mean by scream - whine??

Than there, as in your clocking, warpspeed will be very helpfull. The whinehack made my t3 absolutly instable

Ruben

[bh77a]

The Palm TX is a very stable machine. You must be careful in what you install, as with any OS.

[Nobitsu]

tosbsas, my TX whines even without clocking, but with Dynaclock it whine completely and I shouldn't have to get a program called warpspeed just to get rid of whine. :/

bh77a, what programs do you have installed on your TX?

[bh77a]

Nobitsu,

Here is the list of my current setup. There are a few others that I use but don't have installed right now as I was cleaning out some old files from RAM and haven't got the reinstalled yet.
* = RAM
+ = SD

- ROM Apps (Docs To Go, etc)
- Agendus Pro 11.03*
- PenPenCol+
- SuperNote+
- Due Yesterday+
- CardTXT+
- Database (Mobisystems)*
- IdeaPad+
- OfficeSuite (MobiSystems)*
- PalmPDF+
- Progect+
- SmartListToGo 2.603+ (paying $30 for the upgrade won't happen, since I am a Mac user and only get the prc file :))
- AvantGo+
- Agile Messenger+
- FTP Server+
- Plucker+
- SharkDownload+
- SharkLinks+
- SmbMate+
- AeroPlayer+
- Artelope+
- EarthComber+
- epDraw+
- IconMgr+
- Paint (Mobisystems)*
- TCPMP+
- TealPaint 6+
- Bejeweled 2+
- Casino+
- Chess Tiger+
- Hold Em+
- Monopoly+
- Resco Sudoku+
- Scrabble+
- Solitaire (Gamebox)+
- Space Trader+
- Sudoku+
- Trivial Pursuit+
- Unicheater+
- Vexed+
- Warfare Incorporated+
- iziBasic*
- Plua (1/2)+
- Piaf/PP+
- ViziBasic*
- BatteryGraph*
- ChangeName*
- DataVizTech+
- dbScan+
- Resco Explorer*
- MakeSpot+
- Resco Backup*
- Hi-Launcher*
- myKbd*
- PalmRevolt*
- TextComplete+
- Wireless Keyboard+
- ZLManager*
- ZLauncher*
-

Other apps that I use but haven't got around to re-installing since spring cleaning
- YAHM w/ FontSmoother
- TealScript
- TextPlus
- MobileWrite
- CardReader
- pToolSet

Right now, my TX is very stable, with one exception. Agendus Pro will crash when selecting a contact category while PalmRevolt is enabled. This is an Agendus bug and it has been reported in the Iambic forums to also occur when using SkinUI or FontSmoother.

I do not use TealScript/MobileWrite at the same time. Only one can be installed to RAM. Same with TextPlus and TextComplete.

You are correct that you shouldn't have to buy a program to get rid of the screen whine. It would be nice if the problem didn't exist, but that just isn't the case (unfortunately). My TX whines just a bit, my TE and my CLIE TJ27 do not whine at all.

- Just a side note, YES I am a registered user of all of the shareware apps listed above plus about 25 more that I have outgrown the need for on my TX. ChangeName is simply used to set the HotSync name so that I never have to hot sync in the first place.

[tosbsas]

tosbsas, my TX whines even without clocking, but with Dynaclock it whine completely and I shouldn't have to get a program called warpspeed just to get rid of whine. :/

Complain with palm (:-(( Warpspeed is just the most effective way of killing the whine (:-)) (At least I know)

Ruben

[Nobitsu]

Wow, thanks for your replies. Is agile messenger as good as Verichat? I use Veichat and I find it a litle bit buggy. But it can send files and has alot of function except multichat. I guess I'm just fustrated because Sony Clies were really stable but now they dont sell them any more. heck I would prefer a VZ90 over the TX if the VZ was in english. I cant deal ith the new NVFS system. I really just want an OS that I can install any software and it'll work.

[bh77a]

I am not sure in comparing Agile Messenger to Verichat. Never used Verichat.

NVFS is a good/bad thing. Many programs that one expects to work on it will not, or not in combination with other programs. Palms without NVFS may be more capable of handling tons of hacks, etc. but the NVFS Palms can be extremely stable if one is careful.

[Nobitsu]

I dont see whats the point to having the new NVFS system anyways.
It just makes things unstable and make people sick of dealing with it.
The only advantages is having not lost data after the power is out, which isn't a big deal because the TX has a great battery life and it could be improved, and that doesn't counter the headaches caused by the mind boggle headaches it cause.
Now I understand why palm's became so unpopular in the last few years.

[rbeef]

I've had no problems with my new TX. NVFS has caused no problems and the only app I have that doesn't work on the TX is an app called Backup, which flips the archive/backup bit for files in memory, forcing them to be backed up next hotsync.

My TX has been much more stable than either of the T|E's I have which do not have NVFS.

The reason Palms became unpopular over the last few years is:

1. The Blackberry. It has access to email that you can only dream of having with a Palm device.

2. Smart cell phones are much more capable. Most people want to communcate. Calendars, to do lists, notpads and the like are secondary.

3. Windows mobile devices are quite capable these days. They do have innovations that Palm has just begun address over the last few years, e.g. writing in other than a graffiti area. Another thing that the Windows mobile devices do is recognise actual writing, they don't rely on a writing protocol such as Graffiti.

What Palm has in its favour is that it runs apps that have been developed for it. Some if not many of those apps have not been ported to the Windows mobile platform and probably never will be. Unfortunately most people don't care about those apps, e.g. I use two food database apps specifically designed for the PalmOS platform. Apps is where it's at.

[FerdFerd]

It's amusing to see complaints about stability from users who do things that the system isn't designed to do, such as over/under clocking! Don't get me wrong - I'm almost as interested as the next person in fiddling with my TX. It's something of a hobby. But I don't blame Palm for the crashes that result when I do something it isn't supposed to do. If I remember the start of this tread, a Palm died because it was overclocked too much. Then once it recovered from that, it died again because it was underclocked too much.

It's true that I don't use clocking programs, but my TX is absolutely stable. I do use things like UnCache and OffFlush and FontSmoother (hack) and mySkin without incident. I bet I could do the same with clocking programs if I wanted to and didn't insist the unit go faster than it can or slower than it can. But I don't blame Palm when something happens while I'm doing this.

[Nobitsu]

I have issues even if I dont underclock/overclock my TX.
One time it hard reset on me by itself which was totally weird.
Secondly it doesn't work that well with pocket tunes in the background it usually get stuck or crash in netfront or blazer and I have the latest version of pocket tunes.
I'll just quickly give you guys a list of what programs I have on it.

- autodimmer 1.01
- AudioGateway 1.06.657
- blue files v.1.07
- checkers v.3.1
- clock wireless v.1.01
- DlxSudoku
- Filez v.1.0
- Flash Players v.5.89
- MSDICT 7
- Clean installer 1.72
- mySkin 2.33
- palm revolt 0.946b
- off flush
- Filez 6.8.3
- rescoExplorer V2.42.4
- Card Reader 1.04
- Picsel Proviewer 1.0.29
- TCMP V0.72RC1
- pocket tunes bundle V3.1.6
- MyDiary V5.0
- Netfront 3.1
- Opera Mini 2.0.4509
- Wifile LT
- Warfare inc. v1.2
- Whine hack v.1.1
- UDMH v5.3
- softick bluetooth commander 1.01.188
- VFS-FTP v 1.3.3F
- Snapermail v 2.1

[bh77a]

Autodimmer might be problematic as it is a somewhat old (but good in its day) program.

Resco Explorer is on something like version 2.71 (just letting you know).

There are several hacks in your lists (even if they aren't managed via YAHM or the likes). I would try disabling some of them and reinstating each one at a time to see the combination that causes the issues with PT and Blazer.

[Dick Tracy]

I agree with FerdFerd. Just because other people like to play with clocking (whether they understand the risks or not) doesn'tran that I have or want to. Doing mighty fine without, thanks.

Take a look at the app compatibility list at palmfocus.com before you install anything.

[Nobitsu]

Okay, I'll try something new. lol

[rbeef]

It's amusing to see complaints about stability from users who do things that the system isn't designed to do, such as over/under clocking! Don't get me wrong - I'm almost as interested as the next person in fiddling with my TX. It's something of a hobby. But I don't blame Palm for the crashes that result when I do something it isn't supposed to do. If I remember the start of this tread, a Palm died because it was overclocked too much. Then once it recovered from that, it died again because it was underclocked too much.

It's true that I don't use clocking programs, but my TX is absolutely stable. I do use things like UnCache and OffFlush and FontSmoother (hack) and mySkin without incident. I bet I could do the same with clocking programs if I wanted to and didn't insist the unit go faster than it can or slower than it can. But I don't blame Palm when something happens while I'm doing this.
I totally agree. Overclocking anything will increase the amount of heat it produces thus reducing its life expectancy by an order of magintude. By overclocking you can expect to replace your Palm a lot sooner than you expected.

[dmitrygr]

palm processor produces no heat. increasing it by an order of magnitude is still....(drum roll) ....none.

the only heating parts in a TX are: battery, wifi, bt, scren backlight.

[_Em]

Remember that the PXA chips were originally designed to run at 624 MHz. Palm underclocks them to 312 MHz for the TX mostly for battery savings (although the rest of the hardware is also designed to match that clock speed, which accounts for some TXes locking up at speeds above 520 MHz). These are the same chips used in the LifeDrive which... wait for it... runs at 416 MHz. If you clocked the chip above 624 MHz, you might start getting a bit of heat off the chip, but then the bus speed in these devices can't handle speeds higher than 624 MHz anyway, so the issue is academic for the most part (except in the case of people like Dmitry who can run such devices at 800MHz+ before they die).

[chef]

You have to wait for the battery to drain (backlight dies); then wait an extra day, then plug it in to charge. Eventually it'll start back up. You set your CPU or Bus speed higher than your T|X could go (you probably went above 520MHz), and so the reset button won't work (it's on the bus). Other than that, your T|X is fine.

That PXA Clocker should be called PXA Crapper. I have the same problem as the poster and wasn't so lucky. That software is junk. I guess you get what you pay for. I used it for about 6 hours before it froze up and kept resetting. Never did get it to work properly. The docs are junk. No explanation for much of anything.

Lots of people, and I mean tons, have similar stories about their T5s, TXs etc...most have some sort of permenant damage, if they work at all. The best I heard was orange lines in the screen for ever.

I knew I should never have OCd the palm. USE AT YOUR OWN PERIL.

[_Em]

Just for clarification: the software isn't junk -- it just doesn't protect you or hold your hand. It gives you COMPLETE control of your hardware, and doesn't care if you try to make your hardware do something that will cause it to go up in a puff of smoke.

That being said, it's highly unlikely that fiddling around with the standard settings will permanently harm your device, and any of the advanced settings should only be messed with if you are sure you understand what you are doing. It wouldn't hurt to have the spec sheets for the components your messing with handy, so you don't go outside the tolerance ranges.

If you want something that is better at holding your hand, but still allows you to change clockspeeds, use WarpSpeed. There aren't much in the way of docs for that either though. Generally, it's assumed that if you're overclocking hardware, you are aware that you are NOT running your hardware as it was originally designed to be run.

Maybe there should be a large disclaimer that shows up the first time you run these things so people don't just go "ooh! magical fasterness!" and proceed to lock up their device.

[Nobitsu]

Its okay now.
I found out that Lightspeed is the way to go. :)
Thanks so much

[DoctorBri]

Remember that the PXA chips were originally designed to run at 624 MHz. Palm underclocks them to 312 MHz for the TX mostly for battery savings (although the rest of the hardware is also designed to match that clock speed

Didn't know it was that simple! I have been eyeing a TX for a while, but didn't like the 312 mHz. Knowing this, I'll probably get one, though. Anyways, I know this is OT, but would someone be willing to explain how this all works on a palm? Obviously it involves more than just overclocking the cpu. Just curious. Thanks.

[_Em]

In simple terms (there's more there, but this is all you really need to know), the Palm TX has 3 clock chips: one for the CPU, one for the data bus, and one on the WiFi controller. Everything but WiFi gets its timing signals from the data bus -- but of course, different bits of hardware require different thresholds of accuracy. The data bus controls communication between all the different pieces of hardware on the Palm -- namely, the universal connector pins, the SD Card controller, the Bluetooth controller, the IrDA controller, the screen, the hard buttons, the reset button, the touchscreen, the internal storage, the internal ROM, the memory heap, and the CPU. The CPU uses the bus' clock speed, but needs more accuracy, and so its internal clock breaks up the signals sent by the bus into smaller chunks, so it can process multiple instructions per bus cycle. The WiFi controller acts like a seperate device with its own data buffer, and streams data to the bus as the bus indicates it has space available.

As a result, slowing down the clock speed on the CPU decreases the number of calculations per second, but slowing down the bus speed slows down all hardware communication as well.

[DoctorBri]

Thanks _Em. So... theoretically, if one were to overclock the data bus (if that's even possible) would that alleviate the freeze problem when overclocking the CPU too much?

[nowshining]

Damnit
I just got it working again and then I decided to try underclocking it.
I tried to underclock it to 200 mhz and it died again. :/
I think I shouldn't even bother with it because obviously it doesn't work.

how exactly did you get it working again?