Rom 1.40 camera backlight problem: simple workaround - MDA III, XDA III, PDA2k, 9090 Software Upgrading

Technically, this is not a solution, but you won't have to worry about restoring your favorite backlight settings after using the camera anymore.
First, you need to install a very usefull and very small program called MortRunner on your ppc; you can download the cab here.
Then, unzip the file I've attached to this post (CameraBL.mortrun) and copy it to your ppc. It doesn't matter where you put it.
Then, create a shortcut to this file (you can do that with Resco Explorer, for instance). It will be called CameraBL.lnk; move it to the folder "Windows/Start menu/Programs".
Finally, go to the button settings and assign the camera button to CameraBL instead of Camera.
Now you can use your camera just like you did before, but when you close (not minimize) it, your backlight will be turned down again.
The CameraBL.mortrun file is an extremely simple script for MortRunner; it only contains the following code:
Code:
RunWait \Windows\Camera.exe
SetBacklight 1,1
You can open it in a text editor and adjust the parameters to your own favorite settings; the first is the backlight value when on battery, the second when on external power. They take a number from 1 to 10. I put them both on 1, because I think the Blue Angel's backlight is pretty strong.
Disclaimer: This is a childishly simple workaround, made by a complete dummy. Although it works perfectly for me and I can't imagine anything that could go wrong, I hereby renounce all responsibility for any loss of data etc.!

the even simplier workaround is to take camera.exe from a previous ROM build and copy to your device into \Windows direcotry. I've attached it.

I'd already seen that, I just didn't like the idea of downgrading to a previous version. Upgrading is the way to go, the other direction just doesn't feel right!!
Anyhow, you convinced me to try it, and I must admit the older camera version is just as good. And it doesn't mess with my backlight. Thanks...

Robrecht said:
I'd already seen that, I just didn't like the idea of downgrading to a previous version. Upgrading is the way to go, the other direction just doesn't feel right!!
Anyhow, you convinced me to try it, and I must admit the older camera version is just as good. And it doesn't mess with my backlight. Thanks...
Click to expand...
Click to collapse
yes, upgrading is the way to go... but there is no new feature with new camera.exe, so the old one with no backlight bug is good enuff.

Related

WM6 Phone - Contacts Visible

I have been recently messing about flashing various WM6 ROM's to see which one I might settle on, however I have come across one issue which annoys me so much that I would choose not to go down the WM6 route.
On the phone dialler I now have a bar going across the screen which displays two lines of my contacts. I don't want this. I want the usual phone layout that I have used for the past dozen ROM upgrades.
Is there a way to remove this? I have tried all the settings on the phone but to no avail. Will it dissapear if I re-skin the phone with something from Eten?
What surprises me is that I have not seen anyone else mentioning it on any of the WM6 threads - Does everyone like this new layout?
Vista Dialer
I also found this annoying. I downloaded the following
Jimm98y_vista_dialer.zip
in the development/hacking section. I think it is much better than the old WM5
dialer skin. You can see the screen shots there.
You will probably also need to edit smartskey.ini to allow the dpad to function in the Phone app. With the Underground ROM that was a pain if I remember correctly as it is a system and RO file. I ended up making a cab that created a \Program Files\Smartskeyand copied my smartskey files to that folder. Then stopping smartskey, deleting the shortcut in \Startup and then running Smartskey from the \Program Files folder.
What a PIA! Another reason I went back to the Orwell ROM (after I took the green comm manager with me..)
Tony Simmonds said:
I also found this annoying. I downloaded the following
Jimm98y_vista_dialer.zip
in the development/hacking section. I think it is much better than the old WM5
dialer skin. You can see the screen shots there.
Click to expand...
Click to collapse
Thanks Tony. Just done it and it worked a beaut.

Camera Problems

I have this problem with the camera on the herald.
Once I press the camera button, it does nothing, but the screen and dpad lights up. That's it. The program doesn't even open.
After that, I tried to open it through the programs folder and still nothing happens...
Does anyone have the cab file for the latest camera build for herald or a fix to this problem. It's been bothering me for so long.
Also, once I am able to obtain the fix or cab file, I will have completed a new rom for the herald AND wing that will publish ASAP.
Any help would be appreciated! =]
umchriswho said:
I have this problem with the camera on the herald.
Once I press the camera button, it does nothing, but the screen and dpad lights up. That's it. The program doesn't even open.
After that, I tried to open it through the programs folder and still nothing happens...
Does anyone have the cab file for the latest camera build for herald or a fix to this problem. It's been bothering me for so long.
Also, once I am able to obtain the fix or cab file, I will have completed a new rom for the herald AND wing that will publish ASAP.
Any help would be appreciated! =]
Click to expand...
Click to collapse
All I can tell you, I already said in the PM. I've done this before, twice now that I think about it. Once I just started the ROM from scratch, the second time... umm.... I don't remember how, but I fixed it. It was a small dumb little file, too... send me a copy of the ROM, RGU's and all and I'll see what could be missing. Or download my ROM and try to match the OEMAPP folders between them and see what files you're missing.
ivanmmj said:
All I can tell you, I already said in the PM. I've done this before, twice now that I think about it. Once I just started the ROM from scratch, the second time... umm.... I don't remember how, but I fixed it. It was a small dumb little file, too... send me a copy of the ROM, RGU's and all and I'll see what could be missing. Or download my ROM and try to match the OEMAPP folders between them and see what files you're missing.
Click to expand...
Click to collapse
That's exactly what i did, i used your rom to compare with mine and everything is basically the same...
I also started from scratch again and it still won't work. I'm starting to believe that it may be a program that i have added to the rom.
Did you check ALL the OEM folders? Or just the OEMAPPS? What have you added if you don't mind revealing it to the world.
ivanmmj said:
Did you check ALL the OEM folders? Or just the OEMAPPS? What have you added if you don't mind revealing it to the world.
Click to expand...
Click to collapse
yes i checked all folders, but it's complicated.
do you still want me to send you my .nbh file so you can take a look?
I'm not home right now, but go ahead. Make sure you leave the RGUs intact, though. It might be something in the registry as well.
I glanced over it quickly and found the following files missing from your ROM that were in my ROM. I didn't look TOO hard so I may have missed a few things.
OEM_Lang_0409
DRM0409.dll
OEMAPPS
Arail.amf
ding.amr
taskserstart.exe
transport.exe
different camera file sizes
CannedText_0409.bin
ding.amr
Engine.Dll
FlashLiteDll.dll
getMMSCtxMenuInfo.dll
getMMSCtxMenuInfo.dll.0409.mui
HTCDrmAPI.dll
HTCFlashLiteDll.dll
HTCFSrc.dll
HTCICON.dll
ImageDLL.dll
impie.dll
internal.config
mm1lib.dll
all the mms files including the provxml
mxip_tmus_ppc_cert.provxml
phcanOverbmp.dll
svgplayback.dll
system.config
taskserStart.exe
transport.exe
VerInfou.dll
OemDrivers
PLAYSND.dll
StartupAnimationEngine.dll
TIInit_3_4_27.bts
I know I gotta finish cleaning my ROM... but I'm so focused on getting that flashing limiter taken off...
all right, i have the camera working now because i download the camera build for the hermes, but since it's not the same, everything is distorted and out of place. all i need to do is fix that up and i think i should be able to release this rom.
Where did you find the camera build? I am having the same problem. I have tried two different ROMs, but I think it may be related to JasJam Vs. Hermes. I have the JasJam and the camera app doesn't even pretend to start.
it's all right!!! i got everything fixed! i'm pretty much going to release it now and hope all turns out well!
@ prostar. you need the reg files for the camera. the reason why it wasn't working for me was because i didn't have them. I was able to do it by breaking down any herald ROM and extracting the specific reg files for the camera and BOOM! it worked like a charm...took me a while to figure it out. if you would like, pm me and i'll see what i can do to help you

if i want to add a"third party" keyboard to Cyanogen's build?

if i want to add a"third party" keyboard to Cyanogen's build
how to accomplish that?
and if i want to make it the default keyboard
how to do that..?
thanks in advance
Roy
if this "third party" keyboard is an app like better keyboard or something similar, i would assume just install it or put into your update.zip package and flash it. it should appear under settings-locale and text and just check it on and uncheck any other keyboards like with the htc_ime. unless you are talking about something else then in theory this should work.
thanks for the comment
yes it is an App file.. so i just need to add it to system/app in the update?
and how i can make it the default keyboard so right after a fresh install it would appear and ready to use with specific config that i set?
thanks again
Barina said:
thanks for the comment
yes it is an App file.. so i just need to add it to system/app in the update?
and how i can make it the default keyboard so right after a fresh install it would appear and ready to use with specific config that i set?
thanks again
Click to expand...
Click to collapse
I don't think you can. All roms use android kbt as default (don't quote me on this but I believe so)and it's more trouble then it's worth to make something else default before install. It would be easier to go into settings->locale and text the first time you use it and just make it default (i.e. uncheck all other VKs). Once you do that, your vk will pop up everytime you touch fill-able field. Hope that helps.
OK, I'm curious about the other keyboard. The hardware keyboard. I have a German G1, and have actually become quite fond of QWERTZ even though I mostly only speak English. I've gotten used to reaching down for y and up for z. Also, There are keys like the euro symbol that I actually use a lot living in Deutschland. Not to mention that all the little symbols are laid out completely differently than QWERTY, so looking at the keys just makes life that much tougher. Anyways, I want to change QWERTZ to be my default keyboard, other than having to type in a long string of commands each time or use gscript. I would like it to be so that it works in recovery, and doesn't get lost each time I change builds. Is this possible?
hmmm, I would say yes...I wouldn't be able to tell you how though. I downloaded Russian keyboard from the market and it has the ability to change mapping of hardware KBT and change languages on it. So obviously there is a way. I believe devs name is Game Warrior (could be one word). It's on the market... contact him-he may be able to point you in the right direction.
Also... did you try switching locales in Settings->Locale and Text menu? That could do the trick (not sure what would you choose though as I'm not familiar what country uses QWERTz set-up).
Good luck, I hope you figure it out... sorry I had it easy.. I just dl'd my vk from the market
I DID have it working when I first got my phone. Everything was just dandy with JF1.51 as well. I decided to install the latest DizzyJACHero, and had to update my recovery image, SPL and Radio. Somewhere in there, it borked things up. I tried going back to another SPL and recovery, but only ended up in bootloops when I did that. I redid everything, but I'm stuck with QWERTY unless I do some terminal stuff each time I change roms. And with all the nice new ones (I LOVE Rosie, but she's a resource/battery hog) it's becoming more frequent that I change roms. Eh, I guess I'm just stuck having to terminal my way out of it, like usual with computers.
SPL, Radio and/or Recovery image have nothing to do with the way your keyboard behaves... hmmmm
Here... talk to DudeOfLife in the developement forum (pm him or something). His rom at some point had every language and every layout included.. he should know about this. As an alternative... you can make a script of what you put in terminal and have G1 run it on start-up to change mapping for you. Rogro82 is the king of scripts fyi.
Good luck
all u need to do is istall the new keyboard as an update. thats if it come in an update.zip format. otherwise, just install the .apk file and you should be good to go. best of luck!
shelay said:
all u need to do is istall the new keyboard as an update. thats if it come in an update.zip format. otherwise, just install the .apk file and you should be good to go. best of luck!
Click to expand...
Click to collapse
He is not talking about virtual keyboard... he is talking about hardware.
borodin1 said:
I don't think you can. All roms use android kbt as default (don't quote me on this but I believe so)and it's more trouble then it's worth to make something else default before install. It would be easier to go into settings->locale and text the first time you use it and just make it default (i.e. uncheck all other VKs). Once you do that, your vk will pop up everytime you touch fill-able field. Hope that helps.
Click to expand...
Click to collapse
thanks a lot
Well, I actually feel kinda smart for once. I just opened up a build which had the QWERTZ files in it. I deleted everything else except that folder (and the ones inline above it) and those files. Renamed them to the v3 files. I also added in all the ringers/notifications/alarms that I wanted from other builds in the right locations as well. I now can unzip any build I want to check out, copy the system folder I created over, and it fixes all my keyboard issues, plus ensures I'm never left with just one ringtone/alarm again. Just rezip and resign, then I can flash it right over. Just verified it all worked before posting. If anyone else wants that, I recommend trying it. My next question will be, can I JUST use these files, make a new update.zip that I will flash over any existing rom. If so, I'll just make one and post it up. Well, I guess I may as well try that now. I'm not doing much else tonight.
So, quick answer, NO. It didn't work like I hoped.
Long answer, If I understood more about the update script, I may have been able to get it to work. I noticed it was formatting the System folder when it went to install, pretty much screwing EVERYthing up. Maybe if someone knows how to make the script only replace the files instead of completely wiping the system folder, I may have something others can use. As it stands, it's really useful for me, and pretty much noone else.
ghrayfahx said:
So, quick answer, NO. It didn't work like I hoped.
Long answer, If I understood more about the update script, I may have been able to get it to work. I noticed it was formatting the System folder when it went to install, pretty much screwing EVERYthing up. Maybe if someone knows how to make the script only replace the files instead of completely wiping the system folder, I may have something others can use. As it stands, it's really useful for me, and pretty much noone else.
Click to expand...
Click to collapse
1. Can't you put your commands (that you type in the terminal) into your userinit.sh and it will run on every start up? Not a pro about this but I think it's one way of doing it.
2. There's a guy in the development forum who will build a custom rom for you. He made a post, you should see it on first or second page. Drop him a line. He may just show the way how to do it or he may just build you a rom. Don't worry, we'll figure it out one way or another
Cool, sounds good. I was looking at the script, and it's pretty straight forward. I COULD possibly figure it out if I wanted, but I wouldn't want to put other people's phones at the risk of me being an idiot. Heh. I'll check with the other guy. Thanks

Blackstone device emulator

Hello all,
i have searched quite a bit for an emulator which mimics the Blackstone on your PC.
I am new to Rom cooking (1 day to be precise) and dont want to risk bricking my own so i wondered if there was something of an emulator which i can use to test Roms.
thanks in advance,
- Mega
same is my case...
No idea if this will do what you want, I'm not entirely too sure how this works.
Windows CE 5.0 Device Emulator
http://www.microsoft.com/downloadS/...12-ca31-4be9-a3bf-b9bf4f64ce72&displaylang=en
WM 6.5 Emulator is here:
http://www.microsoft.com/downloads/...1d-97a8-4f80-bc6a-ae010e085a6e&displayLang=en
But I've no idea how to run a blackstone's ROM on MS's emulator.
I'm trying to do same thing that you want do.
Was checking about it a year ago.
Got no answers
Seems its not possible at the moment.
I created an emulator (at least in looks, I don't think you can do a hardware emulator) for my Touch Pro and used it in Visual Studio 2005 Pro when I played with development.
Basically you have three images:
1. A skin (the chasis of the phone, I found a high res image and sized it properly in Photoshop).
2. A layer of what the skin looks like with all buttons pressed (make the Talk button look like it lights up or something).
3. A mask layer with different colors identifying the buttons (Green = Talk, Red = End, etc.).
In an XML file, you'll define the hex codes for the colors and assign an action. For example, if you used green for the Talk button on the mask image, you would enter something like "00FF00 = Talk", so when the Talk button is pressed in the emulator, the "pressed button image" shows the Talk button being "pressed", and the mask image tells the emulator to bring up the dialer, since green (00FF00) = Talk in this case. I've got VS 2008 Pro now (I tinker, not really much of a developer), so I'm not sure how you do it in the standalone emulator. I'd imagine it's a similar process.
-EDIT- I just read your post again, and I'm not sure how you would change the ROM that the emulator reads, since it reads the MS issued ROM when it boots. Maybe have to compile it as a .BIN file, once again, not sure on that.
visual studio includes one (might be useful if you are considering some developing down the line)
Yea, sorry if I made that unclear to Meganut and the others who were asking, VS includes the emulator in the development environment, so all I had to do was make the Touch Pro skin. I'll work on a Blackstone skin and post the files so you guys can hopefully use it as well in the standalone emulator...I just ordered a T8285 today, so I may want to start playing again, so my gain is your gain. I'll try to get it done tomorrow at work.
WOO HOO...I'M GETTING A TOUCH HD!!
GSXR750K2 said:
Yea, sorry if I made that unclear to Meganut and the others who were asking, VS includes the emulator in the development environment, so all I had to do was make the Touch Pro skin. I'll work on a Blackstone skin and post the files so you guys can hopefully use it as well in the standalone emulator...I just ordered a T8285 today, so I may want to start playing again, so my gain is your gain. I'll try to get it done tomorrow at work.
WOO HOO...I'M GETTING A TOUCH HD!!
Click to expand...
Click to collapse
An HD skin for my emulator would be awesome!
Sorry it took so long. Here is the emulator skin for the Touch HD. You can examine the XML file and PNG images to get a feel for what I was saying in my previous post. I've named the files so that you can drop them in and overwrite the default 800x480 emulator in the 6.1.4 SDK Refresh (the default looks pretty pathetic anyway). If you are insistent on keeping it, just rename the files. Reason for doing it this way is I hate screwing with making a new emulator, and if I want to change images (6, 6.1.4, 6.5), I can just move these four files around I have the same skin using a different ROM.
--EDIT--
I corrected the Home button and uploaded the changes below (I changed the mask file also to make it about four times smaller than it was), but for some reason the "Back" button will not respond, although I've tried multiple masks and hex codes to make at least do something. I'll continue to dig in to the Back button issue, I won't have much time this weekend though.
-EDIT-
Scratch what I said here if you already tried it. Like I said previously, I use VS2008 which comes ready to run, so I'm not sure what is needed to get this to work in the standalone emulator. Maybe some of the guys using the emulator can shed some light?
As some might have mentioned above, to make the MS emulator (or any for that matter) run a different ROM is impossible at the moment.
dwizzy130
dwizzy made a good point, the ROM images used in the Emulator and Visual Studio are as Microsoft created them before any vendor touches them. You can "install" things on the emulator and it will retain everything after soft-resetting, just as a physical device will, but chefs won't be able to create their ROMs in a file useable by the Device Emulator. Maybe some of the brilliant people on here can see if they can tear the BIN file apart...
GSXR750K2 said:
Sorry it took so long. Here is the emulator skin for the Touch HD. You can examine the XML file and PNG images to get a feel for what I was saying in my previous post. I've named the files so that you can drop them in and overwrite the default 800x480 emulator in the 6.1.4 SDK Refresh (the default looks pretty pathetic anyway). If you are insistent on keeping it, just rename the files. Reason for doing it this way is I hate screwing with making a new emulator, and if I want to change images (6, 6.1.4, 6.5), I can just move these four files around I have the same skin using a different ROM.
--EDIT--
Just found that the "Home" and "Back" buttons aren't working, I left them off of the XML definitions. I'll leave the "rough draft" version up here for now so you guys can get a feel for it. Depending on whether you've installed Visual Studio or the Standalone Emulator, you'll have different paths to put these files, so make a note of where you install it.
Click to expand...
Click to collapse
Thanks for that. I created my own, but yours look far better
Just one thing: if one would like to revert to the original skin for whatever reason, it might be better to rename the files to e.g. Blackstone.xml etc.
Any chance to get the home and back buttons working? I'll check if i can find out on my own, but seems you're more experienced with that.
Thanks, glad you like it. I'll check on the Home and Back buttons today.
GSXR750K2 said:
Thanks, glad you like it. I'll check on the Home and Back buttons today.
Click to expand...
Click to collapse
That would be great, thanks a lot.
Meanwhile, i found the buttons, but would be great if you could check/confirm. I did check the back button with AEbutton and it gave me the same code on both physical device and emulator. Not sure about the home though.
<button
toolTip="Home"
onClick="0x3B"
mappingColor="0xE6E6E6"
/>
<button
toolTip="Back"
onClick="0x5C"
mappingColor="0xFFFF4B"
/>
The updated skin has been uploaded (it is at the bottom of page 1).
6Fg8, I had to use 0x3E for the "Home" button (which is the same as End), the 0x3B works as the Left Soft Key. I've made several attempts to get the back button to do something...anything, no matter what mask I use or hex command I assign to it, it just sits there. Since you have some experience with the emulator files, feel free to go in and play with the XML/PNG files and see if you can get it to respond and if you figure out what is going on with it, let me know...my weekend is sort of tied up, so I may not have much time to dig into it over the next couple of days. -EDIT- Maybe you can give me some pointer in this aspect, I've found it doesn't seem to matter if I use "onClick" or "onPressAndHold" if I only assign one hex command to it, as no other advanced menu options are assigned. Have you found that it makes a difference?
GSXR750K2 said:
The updated skin has been uploaded (it is at the bottom of page 1).
6Fg8, I had to use 0x3E for the "Home" button (which is the same as End), the 0x3B works as the Left Soft Key. I've made several attempts to get the back button to do something...anything, no matter what mask I use or hex command I assign to it, it just sits there. Since you have some experience with the emulator files, feel free to go in and play with the XML/PNG files and see if you can get it to respond and if you figure out what is going on with it, let me know...my weekend is sort of tied up, so I may not have much time to dig into it over the next couple of days. -EDIT- Maybe you can give me some pointer in this aspect, I've found it doesn't seem to matter if I use "onClick" or "onPressAndHold" if I only assign one hex command to it, as no other advanced menu options are assigned. Have you found that it makes a difference?
Click to expand...
Click to collapse
Thanks for the skin update.
I tested the back button with AEbutton, see here. This is a great piece of software and lets you redefine keys including custom keys, and you can see what code is sent (at least for the custom keys added). Just installed it on emulator, added a user defined key for the back button and an action ("show actions menu"), and presto - works. Compared with the real device the keycode is identical, so i assume the definition is fine. Unfortunately, the home button cant be captured on the PDA for comparison.
The difference between onClick and onPressAndHold is only when the event is fired. onClick fires on button release, onPressAndHold fires on button press and repeats sending codes. So if the software which receives the key doesnt care, there is no difference.
work great, thanks for this and the updated version!
GSXR750K2 said:
The updated skin has been uploaded (it is at the bottom of page 1).
6Fg8, I had to use 0x3E for the "Home" button (which is the same as End), the 0x3B works as the Left Soft Key. I've made several attempts to get the back button to do something...anything, no matter what mask I use or hex command I assign to it, it just sits there. Since you have some experience with the emulator files, feel free to go in and play with the XML/PNG files and see if you can get it to respond and if you figure out what is going on with it, let me know...my weekend is sort of tied up, so I may not have much time to dig into it over the next couple of days. -EDIT- Maybe you can give me some pointer in this aspect, I've found it doesn't seem to matter if I use "onClick" or "onPressAndHold" if I only assign one hex command to it, as no other advanced menu options are assigned. Have you found that it makes a difference?
Click to expand...
Click to collapse
How to use skin in designer window?
thanks for the skin it looks great. I am new to Visual Studio and so wondered if you could help with two problems I have relating to using the HD skin.
firstly, I get to see it in the emulator but it is larger than my screen and it will not scroll up. can this be overcome?
Second, how do I get to use the skin in the Designer Window so I can see what the screen will be like when placing objects on it?
I've tried many ways but to no avail so hope you can help me.
Thanks
Gary

Any way to skip device setup stage after a rom flash?

Ive ended up with stupid issue here, basically I replaced my digitizer with a cheap ebay one and made a mess of it, so now my touchscreen doesnt work. Ive been ok with that until today I flashed the rom to unlock the phone and the first screen pops up with "Please tap the screen to set up your device" or something similar. Thats something I cant physically do so if anyone knows a way around that I would LOVE to hear it
Cheers.
Not yet
People will recommend using tools such as mymobiler and such, that enable you to connect to your device over the PC using activesync.
It does work, for the first tap only. The screen alignment after that is where you are boned, I find myself in the same situation.
Try researching for registry keys that can be modified, as programs like Soti's Pocketpro will allow you to modify registry keys. I'll post if I find anything similar.
search for and read about "welcome.not". the idea is to create a blank file named "welcome.not" on your storage card so the phone chooses to skip the screen alignment wizard on first boot up.
The "solution" may be:
Try flashing one of Witschey's ROMs, because he does not include neither screen alignment nor apps setup in the ROM, so that you'll access the device after flashing, no need to soft-reset nor anything.
The question is, what are you going to do if you can't touch the screen ?
Well, i can do a few things that I need with it. Use it as a phone for a start
I get a free upgrade soon so Ill go with the hero or an iphone but until then I will need a phone and an mp3 player. You can still kind of use google maps even for GPS its just tricky. I did manage my way around London with it lol.
Thanks for the tips anyway guys, Ive tried deleting the welcome file already today but the device kind of locks after that in that you cant really see any icons, even tried 2 roms with it. I will give that Witschey ROM a go though that sounds like it could be the answer to this.
welcome.not
Welcome.not file worked for me, but I did not put in on a SD card, just in the root of the device after MS does activesync.
My computer<device<double click<paste
Took the battery out, turned it on, presto.
Thanks for that!!
No need to reflash, was cool.
Well I tried a Witschey ROM and its working great! Thank you afn961 for that one. It runs very fast indeed as well compared to the stock T-mobile WM6 I had on there. Only issue I have now is that I cant access some menus without the touchscreen, worst one being the running programs menu so stuff just stays open. Cant win em all though.
quite a few cooked ROMs these days are built so that the screen alignment wizard is skipped and it won't show up unless you invoke it explicitly.
i suggested the "welcome.not" approach because it is known to work in terms of skipping the screen alignment wizard and i thought you wanted to stick to the ROM you had because it was to your liking, else i'd have suggested one of the ROMs mentioned in the first paragraph.
finally, you CAN manage running applications using one of the many third party task switchers. i will suggest "showcase" or "taskfacade". the idea is to map your PTT button to invoke the task switcher. not sure if the following will work properly but you can set the default htc task manager to close applications (instead of minimizing them) when you press OK. so you can press OK to exit the foreground application or you can invoke the third party task manager to SWITCH to another application. that way, you get multitasking AND the ability to close the applications you don't need.
check it out and let us know how it goes, good luck!

Categories

Resources