[Tilt, TyTN II, MDA Vario III General] ASCIIker:
jumpspl is needed ONLY AND ONLY to CHANGE your HardSPL...it is also needed to put on the HardSPL in the first place. it may not be a very intuitive read and certainly requires some effort on the reader's part but if you read it all carefully, your concepts will become rock solid and all further steps and conclusions will flow logically...the pieces will fall into place.

its a good idea to keep all installables on your micro sd card. BUT, you should install ONLY the stuff you TRULY need. also remember to clear up browser caches and temporary files that are dropped on the device internal memory from time to time. skyfire, opera, minimo...thats THREE browsers in addition to the builtin IE...i just stick to the latest official beta of opera 9.7 in addition to the latest IE built in to my winmo6.5 ROM. my point is, windows mobile (pre 6.x, 6.0, 6.1, and 6.5) is somewhat delicate and sensitive in terms of the specific versions of applications you install. i've had my kaiser (my FIRST winmo device) for just over a year...i still use pretty much the same applications as i did the first couple of months, i've abandoned some in favor of better ones, and nearly all of them are newer versions that i am certain are compatible with the winmo build(s) i am using at any given time. your stock ROM is quite an OLD build and quite a few corrections and improvements have been made to the OS, so much so that the build number is now in the 21xxx range (compared to your 6.0 build of 18125) and still going further (a bunch of new bugs and issues are inevitable as the OS moves forward). my point is, perhaps you have accumulated some newer installables that don't quite play well with your old OS build 18125.

thats odd...once again, kaisertweak and advanced config have both progressed to newer versions...if you have an old installable, try a new installable. if you are already trying the new installable, try the old one from the era that your build belongs to.

i'm not saying you should try att's newer official winmo6.1 ROM but some people have reported great improvements, but your milage may vary. i, on the other hand, SWEAR by "cooked" ROMs and there are some particular cooked ROMs that will impress the $H1T out of you :D

i never used TCPMP and i quickly moved on to coreplayer, even when i was on winmo6.0. so far, the BEST video performance i have gotten was with the following configuration:

1. Sakajati's HyperDragon IV Rhodium ROM (April 10th, 2009)

2. chainfire's gfxboost v1.1

3. coreplayer 1.3.2 build 6909

4. coreplayer configured to DISABLE QTV mode, and video mode set to DirectDraw @ medium quality

on a side note, the ROM mentioned in item 1 above is STELLAR if you're looking for a good cooked winmo6.1 ROM.

make sure your wifi is set for "Best Performance" as opposed to the default "Best Battery". you might want to look into changing your radio ROM as well, making sure to match the radio version with your winmo MAJOR version. that is, some radios are made ONLY for winmo6.0, others ONLY for winmo6.1 and winmo6.5. same concept applies to the particular HardSPL version you use. finally, quite a few senior members and cooks here claim that wifi is the ONLY radio that is NOT AFFECTED by your radio version but my experience has been different.

also, you need to understand how windows mobile "picks" an available connection and uses it. if your data connection is set up and enabled, it will almost always be picked and forced to connect, even if your wifi is already connected. you'll have to read up some more about the concept but here is what i do. i have my data connection DISABLED all the time. i force windows mobile to always pick "My Work Network" (which is usually the wifi). note that windows will NEVER force the wifi to connect and won't be able to connect the data connection because i have disabled it. this way, i have TOTAL control over how it "dials out". so when i am in a wifi area, i connect my wifi manually and when i am not in a wifi area, i enable my data connection and i let windows dial out onto Edge/GPRS, etc.

errr i think the zoom level is controllable in the camera ONLY in non-3-megapixel mode. that is, if your camera's picture taking mode is set to 3MP, you will NOT get any zoom control. set it to anything lower and you should get zoom control. you must have inadvertantly set the resolution to below 3MP and 3 months ago, either you or the hard reset must have caused it to revert to 3MP, hence your inability to zoom in picture mode.

i said it before and i'll say it again and i don't mean to sound harsh but windows mobile is powerful...and with great power comes great responsibility...the user HAS TO BE AWARE of what he/she is doing and what is going on in the device to be able to tweak it and customize it and to get it to do EXACTLY what is desired.