Windows Mobile @ TechParaiso

We will be Unavailable on 6th & 7th March!!

Mr. Makk — Tue, 02 Mar 2010 11:26:39 +0000

Hello friends,

This is to inform you all that our main website, www.techparaiso.com will be unavailable on 6th & 7th of March as we are updating the core of our website.

It is to note that the Sub Sections – Winmo.Techparaiso.com and Art.Techparaiso.com will remain open throughout. We are only reconstructing our main site. Kindly cooperate and be ready for a new up-liftment of all the data present on our servers.

Winmo GPS Weather Radar

viggo vin — Tue, 23 Feb 2010 23:27:04 +0000

GPS Weather Radar retrieves and displays weather radar for current GPS location or using cell towers.

- Retrieves and displays weather radar for current GPS location or using cell towers
- Ability to manually enter location (for those who do not have GPS)
- Click anywhere on the map to move to that location
- Different views and zoom levels
- Animated radar loop
- Integrates with Titanium Weather 4.2 Plug-in

You will need NetCF 3.5 to use this application properly.

Enjoy !

to Download, Click Here

How to Port a ROM of Different Resolution on Windows Phone OS

Mr. Makk — Sat, 20 Feb 2010 11:43:57 +0000

If you want to get the latest and greatest Windows Mobile version, then follow these steps! They should work for WM6.5, WM6.1, etc. Should work for other phones, too. This guide covers how to port a ROM that has a different resolution than your phone. This is an article posted by Ace10134 @ XDA Developers. To Understand more about the Basics, you can read out following Articles:

Here are the most probable setups that you have:

If you have an official .NBH ROM (custom ROM might work) that is a newer version, then go to Option I
If you have the kitchen of your ROM that you want ported, then you can locate the SYS and XIP folders inside it, and go to Option II
If you only have the SYS and XIP folders, then go to Option II.

Option I

You are on Option I because you now have a .NBH ROM file. Now, you need to download NBH Tool v 1.1, and extract it to your Desktop (or elsewhere).
Run the nbhtool.exe that you just extracted. You will see dutty’s nbh tool window pop up. Make sure that you are on the NBH to NB tab at the top. Then click Decompile NBH file.
You should see a file explorer now. Navigate to the location of your NBH ROM file (that you said you already had), and double click it to open it.
Now a new file explorer window pops up. Navigate to a location of your choice, where you would like to place the extracted NBH. I would create a folder on your desktop called EXTRACTED, and then select that as the location to dump the extracted files. Once you selected your folder, click OK.
Let it work.
Once it finishes, it will say, "Done! Wrote …." Click OK.
You can now close out of dutty’s nbh tool.
Navigate to the folder that you picked in step 5. I told you to extract it to your Desktop in a folder called EXTRACTED. In that folder, you will hopefully find a file called, "Windows.nb", among others. Delete any other files in that folder, except the Windows.nb file.
Now, you need to download Bepe’s TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open the imgfs tools folder. Then open up the folder from step 8 (I told you to call it EXTRACTED, and place it on Desktop). Set the two folders up side-by-side.
In your imgfs tools folder, you should have these files/folders: bin, Dump_200.bat, and Dump_800.bat. We will be using the Dump_800.bat file. Now switch to that EXTRACTED folder, and drag and drop the "Windows.nb" file from the EXTRACTED folder onto the Dump_800.bat file. Yes, you place it right on the file.
A command prompt (black window) will pop up. Let it work. Yes, it seems like it’s not doing anything at the beginning. Just let it work! Wow, it does take a while for it to complete. But let it go! Finally! The commands stop moving, and at the bottom, it says, "Press any key to continue . . ." Press Enter.
The command prompt closes. Now, notice that in your EXTRACTED folder, there is a second file, called "Windows.nb.payload".
Return to the TOOLSET folder, go to the root of it, and then open the dump xip folder. There are two files/folders in this folder: bin and dumpxip.bat. We will be using dumpxip.bat.
From your EXTRACTED folder, drag and drop the "Windows.nb.payload" file onto the dumpxip.bat file, just like last time.
Another command prompt opens. This one goes faster. Once finished, it says, "Press any key to continue . . .". Press Enter.
Back in your EXTRACTED folder, you should find two new folders: IMGFS and XIP. Open your XIP folder.
You should have a folder that looks like an XIP folder. But first, we have to do the following steps.
Have your TOOLSET folder next to your new XIP folder from the last step. Make sure that you are in the root of your TOOLSET folder, and in the root of your XIP folder (EXTRACTED\XIP). Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Drag them one-by-one, and wait till it appears that it’s finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your kitchen’s XIP folder (for user’s of Holly’s Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen’s old XIP folder. You will then end up with the same folders in both your kitchen’s old XIP, and your EXTRACTED\XIP. In your kitchen’s old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new EXTRACTED\XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen’s old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen’s XIP folder. Go into your LangDB folder (in your kitchen’s XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen’s XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Go back to your EXTRACTED folder, and then open the IMGFS folder. You should hopefully have a folder called SYS there, if it ported properly.
Now, that SYS folder is in a different resolution than your current phone is. You have two options: If you are porting a build that is fairly similar to your last ROM’s build, then you can use your SYS’s old resolution folders. The other option is, if you are porting a very different build (like from 6.1 to 6.5), then you need native resolution folders. You have to search and find them yourself. Once you have them, follow below.
Go into your kitchen’s SYS folder (or your downloaded resolution folder, if you chose option 2 from the previous step). Resolution folders have the following tags on the names "…_DPI_96" or "…_DPI_96_RESH_240_RESV_320".
If you are choosing option 1 (keeping your old resolution folders), then, in your old SYS folder, delete EVERY folder, EXCEPT the resolution folders (previous step) and the .VM folder. If you chose option 2, then delete the entire contents of your kitchen’s old SYS folder, except the .VM folder, and then paste your resolution folders that you downloaded into your kitchen’s SYS folder.
Now, no matter which option you chose, you should have a SYS folder in your kitchen that only contains a .VM folder and resolution folders.
Return to that old EXTRACTED folder from a while ago. Open the IMGFS folder within it. Find the SYS folders there, and then select all of the folders except the resolution folders and the .VM folder. Copy the selected folders, and then paste them into your old kitchen’s SYS folder.
You’ve just ported your SYS folder! Hopefully, all goes well. Cook and flash your ROM like normal.

Option II

So, you are here because you either have a newer kitchen’s files that you want ported, or you have just the SYS and XIP folders of the new ROM you want ported.
First, you need to download Bepe’s TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open your new XIP folder (from the kitchen or just from the folder) and keep that window open next to the TOOLSET folder.
Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Yes, drag and drop the .DSM files onto the packagebuilder.exe file. Drag them one-by-one, and wait till it appears that it’s finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your old kitchen’s XIP folder (for user’s of Holly’s Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen’s old XIP folder. You will then end up with the same folders in both your kitchen’s old XIP, and your new XIP folder. In your kitchen’s old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen’s old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen’s XIP folder. Go into your LangDB folder (in your kitchen’s XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen’s XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Now, that new SYS folder that you have is in a different resolution than your current phone is. You have two options: If you are porting a build that is fairly similar to your last ROM’s build, then you can use your SYS’s old resolution folders. The other option is, if you are porting a very different build (like from 6.1 to 6.5), then you need native resolution folders. You have to search and find them yourself. Once you have them, follow below.
Go into your kitchen’s SYS folder (or your downloaded resolution folder, if you chose option 2 from the previous step). Resolution folders have the following tags on the names "…_DPI_96" or "…_DPI_96_RESH_240_RESV_320".
If you are choosing option 1 (keeping your old resolution folders), then, in your old SYS folder, delete EVERY folder, EXCEPT the resolution folders (previous step) and the .VM folder. If you chose option 2, then delete the entire contents of your kitchen’s old SYS folder, except the .VM folder, and then paste your resolution folders that you downloaded into your kitchen’s SYS folder.
Now, no matter which option you chose, you should have a SYS folder in your kitchen that only contains a .VM folder and resolution folders.
Return to your new SYS folder (the different resolution one). Select all of the folders except the resolution folders and the .VM folder. Copy the selected folders, and then paste them into your old kitchen’s SYS folder.
You’ve just ported your SYS folder! Hopefully, all goes well. Cook and flash your ROM like normal.

You can read the original article HERE

How to Port a ROM of Same Resolution on Windows Phone OS

Mr. Makk — Sat, 20 Feb 2010 11:09:00 +0000

If you want to get the latest and greatest Windows Mobile version, then follow these steps! They should work for WM6.5.x, WM6.5, etc. Should work for other phones, too. This guide covers how to port a ROM that has the same resolution as your phone. This is an article posted by Ace10134 @ XDA Developers. To Understand more about the Basics, you can read out following Articles:

Here are the most probable setups that you have:

If you have an official .NBH ROM (custom ROM might work) that is a newer version, then go to Option I
If you have the kitchen of your ROM that you want ported, then you can locate the SYS and XIP folders inside it, and go to Option II
If you only have the SYS and XIP folders, then go to Option II.

Option I

You are on Option I because you now have a .NBH ROM file. Now, you need to download NBH Tool v 1.1, and extract it to your Desktop (or elsewhere).
Run the nbhtool.exe that you just extracted. You will see dutty’s nbh tool window pop up. Make sure that you are on the NBH to NB tab at the top. Then click Decompile NBH file.
You should see a file explorer now. Navigate to the location of your NBH ROM file (that you said you already had), and double click it to open it.
Now a new file explorer window pops up. Navigate to a location of your choice, where you would like to place the extracted NBH. I would create a folder on your desktop called EXTRACTED, and then select that as the location to dump the extracted files. Once you selected your folder, click OK.
Let it work.
Once it finishes, it will say, "Done! Wrote …." Click OK.
You can now close out of dutty’s nbh tool.
Navigate to the folder that you picked in step 5. I told you to extract it to your Desktop in a folder called EXTRACTED. In that folder, you will hopefully find a file called, "Windows.nb", among others. Delete any other files in that folder, except the Windows.nb file.
Now, you need to download Bepe’s TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open the imgfs tools folder. Then open up the folder from step 8 (I told you to call it EXTRACTED, and place it on Desktop). Set the two folders up side-by-side.
In your imgfs tools folder, you should have these files/folders: bin, Dump_200.bat, and Dump_800.bat. We will be using the Dump_800.bat file. Now switch to that EXTRACTED folder, and drag and drop the "Windows.nb" file from the EXTRACTED folder onto the Dump_800.bat file. Yes, you place it right on the file.
A command prompt (black window) will pop up. Let it work. Yes, it seems like it’s not doing anything at the beginning. Just let it work! Wow, it does take a while for it to complete. But let it go! Finally! The commands stop moving, and at the bottom, it says, "Press any key to continue . . ." Press Enter.
The command prompt closes. Now, notice that in your EXTRACTED folder, there is a second file, called "Windows.nb.payload".
Return to the TOOLSET folder, go to the root of it, and then open the dump xip folder. There are two files/folders in this folder: bin and dumpxip.bat. We will be using dumpxip.bat.
From your EXTRACTED folder, drag and drop the "Windows.nb.payload" file onto the dumpxip.bat file, just like last time.
Another command prompt opens. This one goes faster. Once finished, it says, "Press any key to continue . . .". Press Enter.
Back in your EXTRACTED folder, you should find two new folders: IMGFS and XIP. Open your XIP folder.
You should have a folder that looks like an XIP folder. But first, we have to do the following steps.
Have your TOOLSET folder next to your new XIP folder from the last step. Make sure that you are in the root of your TOOLSET folder, and in the root of your XIP folder (EXTRACTED\XIP). Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Drag them one-by-one, and wait till it appears that it’s finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your kitchen’s XIP folder (for user’s of Holly’s Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen’s old XIP folder. You will then end up with the same folders in both your kitchen’s old XIP, and your EXTRACTED\XIP. In your kitchen’s old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new EXTRACTED\XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen’s old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen’s XIP folder. Go into your LangDB folder (in your kitchen’s XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen’s XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Go back to your EXTRACTED folder, and then open the IMGFS folder. You should hopefully have a folder called SYS there, if it ported properly. Go to your kitchen’s folders (for Holly’s Kitchen, C:\HollysKitchen\Working_Folder\), and delete your SYS folder. Then copy and paste your SYS folder from EXTRACTED\IMGFS to your kitchen’s folder, where your old SYS folder used to be.
Cook your ROM like normal, and you’ll be running a new version of Windows Mobile!!

Option II

So, you are here because you either have a newer kitchen’s files that you want ported, or you have just the SYS and XIP folders of the new ROM you want ported.
First, you need to download Bepe’s TOOLSET, HERE. Extract that to somewhere, like your Desktop.
Open the TOOLSET folder from your Desktop (or elsewhere). You should find three files/folders there: dump xip, imgfs tools, and packagebuilder.exe.
Open your new XIP folder (from the kitchen or just from the folder) and keep that window open next to the TOOLSET folder.
Scroll down to the bottom of the XIP folder. Notice the .DSM files. They are the important ones. You will drag each .DSM file onto the packagebuilder.exe file from the TOOLSET folder. Yes, drag and drop the .DSM files onto the packagebuilder.exe file. Drag them one-by-one, and wait till it appears that it’s finished until doing the next. Once finished, your XIP folder should consist of folders only.
Your folders in the XIP will be: LangDB, MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE.
Go to your old kitchen’s XIP folder (for user’s of Holly’s Kitchen, that would be found in C:\HollysKitchen\Working_Folder\ROM\XIP). Repeat the same proccess on the .DSM files, from two steps above, but with your kitchen’s old XIP folder. You will then end up with the same folders in both your kitchen’s old XIP, and your new XIP folder. In your kitchen’s old XIP, remove all of the folders, except the OEMXIPKernel folder. Then, go to your new XIP folder, and select all of the folders, except the OEMXIPKernel folder. Copy and paste those into your kitchen’s old XIP folder.
Now, you have to remove all of the folders, so that you just have files in your kitchen’s XIP folder. Go into your LangDB folder (in your kitchen’s XIP), select all the files/folders, and cut them (Ctrl-X). Then go back to your kitchen’s XIP root folder, and paste the files there (Ctrl-V). Do the same procedure with the MSXIPKernel, MSXIPKernelLTK, OEMXIPKernel, and WinCENLS_WWE folders. You are now done with your XIP!
Now go to your kitchen’s old SYS folder. Select all of the files/folders within it, except the .VM folder, and then delete them.
Go to your new SYS folder and select all of the files except the .VM folder. Copy them (Ctrl-C), and then paste them into your kitchen’s old SYS folder (Ctrl-V).
Now you should be done porting the ROM! Go ahead and cook your ROM, and hope it works!

The original Post is HERE

Windows Phone 7 Series Specs and comparison to previous versions

Mr. Makk — Tue, 16 Feb 2010 17:10:21 +0000

With new specs and information coming out every other moment, it can be easily believed the hype and hoopla around the new OS from Microsoft.

Its a whole new Core from Microsoft and they are ready to set the standards to be matched by others. Its a do or die attempt from them as they are pretty late in the competition and pretty behind for now from the likes for iPhone and recent Android. A lot of expectations are from Windows Phone 7 Series and how the series unfolded into its different components and how well Microsoft distinct among them.

Windows Phone 7 Series on HTC HD2

Mr. Makk — Tue, 16 Feb 2010 15:26:19 +0000

Not even a day since the Windows Phone 7 Series was announced at the MWC 2010, the most probably prospect to get the upgrade, HTC HD2 is already showing the new OS running on it. If sources are to be believed at winmo.nl then an HD2 Rom is already out running the new OS on HTC HD2. As can be seen in the picture on right, it doesn’t really look a fake.

Here is what was the user had to say:

Multilingual
What immediately struck by the first boot: multilingualism!
Windows Phone 7 Series expresses a nice Dutch word as you start the screen (with the tiles / hubs) can see.
Or something of that multilingualism "children" build is a good question, because it is quite possible that the final version with different language versions will work, just as is the case.
Hubs
These hubs are great and resemble the shortcuts on the home screen of HTC Sense.
You can find contacts, applications, shortcuts to websites, widgets and place shortcuts to files.
The pictures hub takes the space of two standard hubs consuming and leave a slideshow with nice effects.
TomTom Navigator?
Very strange but true: the ROM contains a TomTom Navigator (see the shortcut on HD2). It is version 7.916.9189 and touching the icon will launch that TomTom Navigator just that you’re used to.
So ehh …. TomTom is already working in the context of developing a package for Windows 7 Series Phone?
Fast!
Windows 7 Phone Series is FAST!
So fast that it seems the Snapdragon processor of the HD2 but at half speed runs under Windows Mobile 6.5.
SMS problem
Good news: Windows 7 Phone Series on the HTC HD2 not affected by the super-annoying SMS problem.
Zune does not
This ROM works unfortunately none of the Zune multimedia features (all error messages, etc.).

This review might be true in terms of the fact that Windows Phone 7 Series is not ready as yet and it shows. How it develops is to be seen in coming weeks before MIX 2010. We all know the raw Windows Mobile 6.5 that was presented to us in the starting and how much it has changed and developed by the confused Microsoft who is dying to do something new and still not loose its dignity.

Windows Phone 7 Series Revealed!!

Mr. Makk — Mon, 15 Feb 2010 18:33:57 +0000

Here it comes. The next generation of Windows Mobile or Windows Phone OS. Here comes the Windows Phone 7 Series. What al we get in the series is yet to be figured out but what we were shown at the Mobile World Congress is a sure shocker and a revelation. The current UI seems ages old to the upcoming new UI. It Zune interface extension as can be seen from the Pictures and Videos. The Official Website has been launched Windows Phone 7 Series for you to have a look at it.

What was focused at the MWC was:

The new user experience
Integration with social networks like Facebook
Internet Explorer
Photos, videos, and music
E-mail and texting
GPS and maps
Search integration
Hardware standards

Overview:

Its now focusing on sets of tiles which represent links to applications or contacts. It’s a completely contextual experience which can be customized both by users and carriers, and allows people to "promote" items higher up in the list.

If you have a Zune HD, you know what this is like. Lots of bold text on the device, lists with text cut off on the sides of the phone, and additional screens to the left and right driven by arrows pointing you in either direction. For the most part this works, though in instances like email, it feels like there’s a bit of wasted space. Everything else is super stripped down — the calendar app looks like vector line art (and weirdly one of our favorite parts of the phone), the browser seems to be using the bare minimum to show its content (which isn’t necessarily a bad thing), and the phone application is essentially monochromatic.

The OS seemed simple and minimalistic with stripped down basic applications. Not the camera, of the Dialer was showcased as yet and every other detail was left for the MIX10 conference as being repeated by the Officials.

Bug Fixed: HTC Album showing Duplicate Images in Camera Shots View

Mr. Makk — Sat, 13 Feb 2010 18:42:49 +0000

Many of us on HTC Windows Mobile Devices have noticed that when we open the HTC Album, and view the pictures in Camera Shots Mode, it shows the Image with its duplicates. As seen in the screenshot, this is a very annoying issue as Camera Shot mode is set to as default even in HTC Sense UI’s Weather Background folder. And if we delete one image of the two, the other one gets deleted automatically. This shows that its just a copy impression of the original image. I searched for a solution but found no result so the best solution was extensive tests just to check what was going wrong. What i noticed was that in my one of my registry tweaks was causing the problem:

Problem:

[HKEY_LOCAL_MACHINE\Software\HTC\HTCAlbum]
"VideoSaveFolder_0409"="\\Storage Card\\DCIM\\100MEDIA"

Reason:

My Theory – As per my understanding, the Camera Shots mode has to show both Images and Videos, so it’ll show the default folder where Camera Images are saved and where Camera Videos are saved. Now by default it has been set that these two locations are same unless forcefully guided to some other folder location. Now my registry above made the HTC Sense, sense that the location of Saved Images and saved Videos is different. Do HTC Album now shows both the folders separated though they are actually same and thus showing the images and videos twice. This being a very logical and fruitful theory, i believe that somehow others aswel are making such mistake and getting this Bug/Error.

XDA – Some user Morenoshark @ XDA Developers have a different reason to it:

Well, the "double picture" problem happens when you change the Manila language. I change from English (0409) to Brazilian Portuguese (0416) and the problem began. I solve it changing 3 registry entries:
HKLM/Software/HTC/HTCAlbum/VideoSaveFolder_xxxx
HKLM/Software/Camera/Image/GpsSaveFolder_xxxx
HKLM/Software/Camera/Image/SaveFolder_xxxx
Change xxxx to your language code, soft reset, and voilá!

Solution:

If your saved Images and saved camera Videos have a same location folder you need not add such registry or change to their location.
Lawrence74 @ XDA Developers has a different solution to it:

1. Delete the "HKLM \ Software \ HTC \ HTCAlbum" under the "VideoSaveFolder_0409" String.
2. Create a new String "VideoSaveFolder_xxxx" as a value add to "My Pictures".
3. Soft-reset.

Now Enable Wifi From Manilla Launcher

viggo vin — Thu, 11 Feb 2010 22:13:18 +0000

Now, no need to enable Wifi from Comm Manager. A small program that lets you toggle your WiFi on/off with one touch.

No more going into the Comm Manager. You can also add it to your Manilla launcher like in the screen shot.

Click to Get

New HTC HD2 LEO Rom Launched!!

Mr. Makk — Wed, 10 Feb 2010 13:22:56 +0000

The Ahen Rom Series now finally moves to the Mammoth Windows Mobile Beast, the HTC HD2. Head over to the Roms Section for more information on a Fully Features first Release of this Rom.