yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] jagabongo:
when i try to use TomTom Navigator...

it hungs at: Waiting for GPS Signal, so i think there is noch signal at all..

which radio version should i try ??
[Touch Diamond, MDA Compact IV General] band27:
Currently I'm back with 1.09.25.23 but all the Security Unlocked radio's had this symptom of not displaying the signal but it was there.
[Touch Diamond, MDA Compact IV General] nexxexium:
First time use of an app using gps takes a long time to get a gps fix.

It can take up to 20 min.

And make sure you're outside AAAHAHAHAHA
[Touch Diamond, MDA Compact IV General] steveianson:
Try running quick GPS
[Touch Diamond, MDA Compact IV General] jagabongo:
this solves my problem!
[Touch Diamond, MDA Compact IV General] band27:
Excellent.....glad to hear! :)
[Non-Touchscreen Windows Mobile Other] timepassman:
Hi,

Although it is possible to get any htc any carrier unlocked for $20 over net (input being model and imei), has anyone attempted to figure out the algorithm?
[Non-Touchscreen Windows Mobile Other] UnkzDomain:
This would be cool to find out...
[Networking] Moony1987:
Argh!

I've never really posted a rant, but here's one.

Symbian is streets ahead of WinMo when it comes to network management.

With Symbian if you open an app that wants to access the Internet you get a prompt asking what available connection you want to use. If for some reason while using that app you lose the connection, you get prompted again.

WinMo doesn't ask. It uses whatever network is available going from Wifi down.

This is a problem for some (Okay, not all. I'm sure people with unlimited data plans, and those who don't want to be prompted like this way). Symbian let you configure programs to automatically connect to a network. It gave you a choice. Again, WinMo doesn't.

My own example -

I'm with Telstra, in Australia. We don't get unlimited data. I have a 150MB Plan.

With my previous N95 I could start up Internet Radio, chose WiFi for my connection, and listen to it while I was in bed knowing that if I fall asleep, and the WiFi drops out, the program will stop. It won't switch over to HSDPA and cost me a fortune.

Now my Touch HD. It sleeps automatically after 30 minutes. I've just found out that when it does that, I lose WiFi.

Last night when I went to bed I started up Kinoma, and was listening to a shoutcast stream over WiFi. The phone went to sleep and with the wifi connection lost, the phone went to HSDPA.

12 Hours of streaming has put me 560MB over my 150MB limit. That's $270 extra I'm going to need to pay.

Oh well. Lesson learned.

I don't understand though how Windows Mobile can be so far ahead of Symbian in almost every area, yet lacking by a huge amount when it comes to Network Management.

FWIW - I've now set all programs that want to use the Internet to now use my "Work Connection" so they will only use WiFi but

a) What a useless workaround. If for some reason I do want to use HSDPA data I then have to go through the hassle of changing it back

and

b) How hard is it to have the option there to "Always Ask"

Seriously!?

Phew. I'm done.
[Networking] scote:
you have my sympathy, my last smart phone was symbian UIQ. that had internet profiles and priorities etc. WinMo is sadly deficient in that area.

There are a few issues raised here.

First off wifi turning off when the phone (and you!) goes to sleep. I think there is a setting to prevent that, have a look at this thread:

http://xdaforums.com/showthread.php?t=488623

also i have seen mentioned an app called no_data which prevents GPRS connections, might be usefull, though I have no experience of it.
[Networking] thenext1:
I have to agree on this, but on a slightly different subject: the

EVIL

windows mobile connection manager.

It is completely useless, being in the middle way between iPhone style (connect with any network and don't bother the user), and Symbian style (bother the user and let him choose the network every time). That is, it requires the users to dig into tricky and labyrinthic settings and always fails to do the right thing.

Thx to connection manager, I cannot use the BT PAN connection I spent long nights trying to get it work on my Motorola Q9, when the phone is not in airplane mode, because the CM will unilaterally think the PAN is useless and use H$DPA (or GPR$) instead.
[Networking] hidden_hunter:
Good old fashion Telstra reeming plays a part as well.
[Networking] Jackuuuuu:
OUCH on the $270!!!

OMFG!@#$%^&*()_+|

I share you frastration until I found this No Data application which I install first in every flash, it just disables any Data connection!

If you need it let me know :)
[Networking] Moony1987:
Thanks for the sympathy.

My biggest problem with NoData is that I actually want to be able to use HSDPA when I am not near a WiFi network, I don't want data off permanently!

Why can't there be an app that lets you chose which connection everytime. That's what is annoying me most!
[Networking] Jackuuuuu:
When you need it just switch it back on. Less than few clicks :)
[Networking] purec0de:
Hi,

i have just posted regarding this issue on another thread.

I remember reading a review for the Touch HD and one reviewer mentioned a 'simple thord party app that allows one button switching from wifi to 3g(HSDPA)'. rather disappointingly the reviewer does not mention what this app is called!!!!!

actually the issue i have is slighlty different, if i set the network setting to use wifi , when i turn wifi off i have the phone simply will not connect to anything until is go back through.

START>SETTINGS>CONNECTIONS>CONNECTIONS>ADVANCED>SELECT NETWORKS> either MY Work Network or Orang Internet.

phew what a pain in the preverbials.

Microsoft - i really hope you sort this in winMo 6.5

Anybody else - how about a simple app, if i switch wifi on and a network is found, set the above to my work network.

if not found then either set it to Orange Internet (or whoeever) (for those of us with unlimited data) or as the thread leader suggests just bloody ask whether it is ok to go back to 3G/HSDPA.

but can we please stop the:

START>SETTINGS>CONNECTIONS>CONNECTIONS>ADVANCED>SELECT NETWORKS>MY Work Network

or

START>SETTINGS>CONNECTIONS>CONNECTIONS>ADVANCED>SELECT NETWORKS>"carrier internet connection"

7 clicks of frustration that i struggle to do without a stylus
[Networking] Moony1987:
I've since installed and been using NoData. While not a perfect solution, it does make it easier to turn my data connections on and off without going through the settings menus.

It will do until Microsoft decides to catch up with the rest of the field with regards to network management.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] sugui:
hi... how can i directly store files in storage files coming from bluetooth device, is there a way w/o installing any applications? pls help me..
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] muckelmaus:
The Search-button is a 'Powerful Medicine'

Hi, there 3 good lucking answers to your question in other forum threads, I think.They look good, at least:

Try 'bluetooth storage card' on the search function on the upper right corner of this side.

I hope, it works for you, sounds good. I prefer to change files via bluetooth-ftp and the bluetooth explorer and store it directly, wherever I want.
[8525, TyTN, MDA Vario II, JasJam General] eirfan:
Hi there,

I purchased a used SPV M3100 and it comes with Windows TAI edition, which is quite annoying to me, I want its original rom or 6.1 on this device for this I download different rom's from orange website and some others but no one is working for me please if anyone can help me to find original or 6.1 rom for this device...
[Windows Mobile] hilaireg:
Consolidating .RGU Files to BOOT.RGU

The boot hive contains system settings that are applied only during boot. The boot hive is read out of ROM and used to start drivers and file systems needed to reach the system hive file. Once the system hive is mounted, the boot hive is discarded. Changes made to the registry during the boot process are copied into the system hive once it is available. The boot hive in ROM remains unchanged.

The boot.hv registry hive, which contains the contents of all .RGU files in the XIP, provides the initial basic registry hive that is referenced during the loading of the kernel and any necessary drivers to mount the root file system. Once the file system is mounted the default.hv and user.hv registry hives are mounted and used. Most chefs add/remove/change entries from the BOOT.RGU file during their cooking process – you'll eventually do the same.

For the purposes of this guide, we will consolidate the contents of all .RGU files found in the Dump_XIP folder into the BOOT.RGU file. Consolidating the contents of the .RGU files found in the Dump_XIP folder to the BOOT.RGU file ensures that all necessary registry entries will be added during the ROM compilation activities.

Tools Required

The following tools are required to edit .RGU files.

Unicode Text Editor

Procedure

The following procedure will consolidate all of the .RGU files found in the Dump_XIP folder into the BOOT.RGU file.

Navigate to C:\XDA\MY_KITCHEN\Temp\Dump_XIP\ folder.

Launch a text editor and open the BOOT.RGU file.

Launch a text editor and open the next .RGU file that appears in the C:\XDA\MY_KITCHEN\Temp\Dump_XIP\ folder.

Select and copy all of the file contents.

Switch to the BOOT.RGU file and paste the content to end of this file.

Repeat steps

3

to

5

until the content of each .RGU file has been appended to the BOOT.RGU file.

Save the expanded copy of the BOOT.RGU file in the C:\XDA\MY_KITCHEN\ROM\XIP\ folder.

Tip

Make a backup copy of the BOOT.RGU file before editing; delete the backup file when done.

Observe the line formatting and spacing in the BOOT.RGU file and make certain to have an empty line as the last line of the file.

Comment lines, which usually begin with a semi-colon [;], can be omitted.

Registry removal lines usually begin with a minus [-] after the open square bracket.

References

Windows Mobile

http://msdn.microsoft.com/en-us/library/ms885472.aspx
[Windows Mobile] hilaireg:
Increasing the Data Cache

File caching improves performance and also improves power management; when an application accesses physical storage, the storage device uses much more power. The less often physical storage is accessed, the longer storage devices spend in a low-power state.

By increasing the DataCacheSize registry value, you effectively improve the performance of applications that are file system intensive such as database and mapping applications – which results in lower physical storage access requirements. Drastically increasing the DataCacheSize however, may have adverse effects and slow the device down as a result of longer auto-compaction processing.

For the purposes of this guide, we are going to increase the current DataCacheSize value from 4MB to 8MB.

Tools Required

The following tools are required to adjust the DataCacheSize value.

Unicode Text Editor

Hexadecimal Calculator

Procedure

The following procedure will change the current DataCacheSize value of 4MB to 8MB.

Navigate to the C:\XDA\MY_KITCHEN\ROM\XIP\ folder.

Launch a text editor and open the BOOT.RGU file.

Search for the following registry key entry:

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FLASHDRV\FATFS]

Locate the following registry value underneath the key:

"DataCacheSize"=dword:00000800 ;2048 sectors(2048*2048=4MB)

Change the registry value to the following:

"DataCacheSize"=dword:00001000 ;4096 sectors(4096*2048=8MB)

Save the BOOT.RGU file.

Exit the text editor.

Tip

Make a backup copy of the BOOT.RGU file before editing; delete the backup file when done.
[Windows Mobile] hilaireg:
Reducing the .PAYLOAD File

At this point, we need to remove the contents of the IMGFS (OEM, SYS) from the .PAYLOAD file in preparation for our changes to the ULDR and XIP. Removing the IMGFS (OEM, SYS) contents from the .PAYLOAD file will reduce the size of the .PAYLOAD file making it easier to work with.

To reduce the .PAYLOAD file, we essentially need to cook a new version of the .PAYLOAD file with an empty IMGFS partition – one which only contains the .VM and .ROM folder contents. For the purposes of this guide, we will use the Ervius Payload Reducer script to perform this process.

Tools Required

The following tools are required for the .PAYLOAD file reduction activities.

ImgfsFromNb

ImgfsFromDump

ImgfsToNb

Procedure

The following procedure initiates the .PAYLOAD file reduction activity via a script that is included in the Generic Simple Kitchen. The reduced os.nb.payload file will be required when we update the XIP.BIN file.

Copy the ReducePayload folder (and contents) from the C:\XDA\MY_KITCHEN\Tools\ folder to the C:\XDA\MY_KITCHEN\Temp\ folder.

Copy the OS.NB.PAYLOAD file from the C:\XDA\MY_KITCHEN\Temp\ folder to the C:\XDA\MY_KITCHEN\Temp\ReducePayload\ folder.

Navigate to the C:\XDA\MY_KITCHEN\Temp\ReducePayload\ folder.

Launch reduce_payload.bat.

At the OS.NB.PAYLOAD Successfully Reduced. Press Any Key To Continue ... message, press ENTER.

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676
[Windows Mobile] hilaireg:
Extracting the XIP.BIN Contents

The Execute-in-place (XIP) region is an area where an application can execute code directly from ROM rather than loading it from RAM. Before we can proceed to make changes such as unlocking the Page Pool and disabling Certificate checking, we need to extract the contents of the XIP.BIN file.

It is possible to use the XIP.BIN contents from a newer version of a ROM from a different device or a newer operating system. This is typically done by chefs who are looking for the most recent versions of system files from a specific device or version of an operating system – you'll eventually do the same.

For the purposes of this guide, we will be using the same version of the system files.

Tools Required

The following tools are required for the XIP.BIN file extraction activities.

XIPPort

Procedure

The following procedure will extract the contents of the XIP.BIN file. The extracted contents of XIP.BIN file will be required when we unlock the page pool and disable certificate checking.

1. Copy the XIPPort folder (and contents) from the C:\XDA\MY_KITCHEN\Tools\ folder to the C:\XDA\MY_KITCHEN\Temp\ folder.

2. Copy the XIP.BIN file from the C:\XDA\MY_KITCHEN\Temp\ folder to the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder.

3. Navigate to the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder.

4. Launch XIPPORT.EXE.

5. Click the Dump XIP.BIN button.

6. Exit XIPPORT.EXE.

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676

XIP Porting Guide

http://xdaforums.com/showthread.php?t=379598
[Windows Mobile] hilaireg:
Unlocking the Paging Pool

The Paging Pool serves as a limit on the amount of memory that can be consumed by pageable data. It includes an algorithm for choosing the order in which to remove pageable data from memory. Pool behaviour is typically determined by the OEM – Microsoft sets a default value for the paging pool, but the OEM can change that value. Applications do not have the ability to set the behaviour for their own executables or memory-mapped files.

For the purposes of this guide, we are going to apply a change to the kernel binary file which will permit us to change the Paging Pool size (initially set to 6MB) to other sizes using the PagePool Changer tool.

Tools Required

The following tools are required for the Paging Pool unlock activities.

Hexadecimal Editor

Procedure

The following procedure will change the kernel binary file to permit adjustments to the Paging Pool size via the PagePool Changer tool.

Navigate to the C:\XDA\MY_KITCHEN\Tools\xvi32\ folder.

Launch XVI32.EXE.

Select File, Open.

Navigate to C:\XDA\MY_KITCHEN\Temp\XIPPort\OUT\MODULES\nk.exe\ folder.

Select the S000 binary file.

Select Search, Find.

In the Hex String box, type:

03 15 A0 03 02 15 A0 13

Click OK.

Change the following 4 bytes after the 03 15 A0 03 02 15 A0 13 string;

FROM: 00 10 82 E5

TO: 00 00 A0 E1

Select File, Save.

Select File, Exit.

Tip

Make a backup copy of the S000 file before editing; delete the backup file when done.
[Windows Mobile] hilaireg:
Disabling Certificate Checking

During the startup process of your device, the operating system verifies that each system file against an internal certificate store to ensure that each file is signed with a trusted certificate; if the system file is not signed, the file is ignored.

To allow execution of non-signed system files, we need to disable the internal certificate store verification. Once disabled, the operating system will trust all code installed regardless of its signature. This provides more control over the code that gets installed on the device – you no longer need to load and manually sign additional certificates such as those from the sdkcerts.cab into the device root certificate store.

For the purposes of this guide, we are going to apply a change to the kernel binary file which will disable the internal certificate store verification.

Tools Required

The following tools are required to disable the internal certificate store verification.

AutoPatcher01

Procedure

The following procedure will disable the internal certificate store verification.

Navigate to the C:\XDA\MY_KITCHEN\cmonex_AutoPatcher\ folder.

Launch AUTOPATCHER01.EXE.

Click the Cert Patch button.

Select All File (*.*) from the Files Of Type list.

Navigate to C:\XDA\MY_KITCHEN\TempXIPPort\OUT\MODULES\nk.exe\ folder.

Select the S000 binary file.

At the Successfully Patched... message, click OK.

Exit AUTOPATCHER01.EXE.

Tip

Make a backup copy of the S000 file before editing; delete the backup file when done.

References

[RES] RILPHONE.DLL And "How To" With A Radio

http://xdaforums.com/showthread.php?t=481026

Kernel Overview

http://msdn.microsoft.com/en-us/library/aa909237.aspx
[Windows Mobile] hilaireg:
Updating the XIP.BIN Contents

The Execute-in-place (XIP) region is an area where an application can execute code directly from ROM rather than loading it from RAM. Now that we have unlocked the Page Pool and disabled Certificate checking, we need to assemble the extracted XIP.BIN contents back into a XIP.BIN file that includes our changes.

It is possible to use the XIP.BIN contents from a newer version of a ROM from a different device or a newer operating system. This is typically done by chefs who are looking for the most recent versions of system files from a specific device or version of an operating system – you'll eventually do the same.

For the purposes of this guide, we will be using the same version of the system files.

Tools Required

The following tools are required for the XIP_OUT.BIN file creation activities.

XIPPort

Procedure

The following procedure will compile the contents of the XIP.BIN file. To eliminate some confusion, the new .BIN file will be called XIP_OUT.BIN – the XIPPort tool creates the new .BIN file and renames it to XIP_OUT.BIN.

Navigate to the C:\XDA\MY_KITCHEN\Temp\XIPPort\ folder.

Launch XIPPORT.EXE.

Click the Build XIP_OUT.BIN button.

Exit XIPPORT.EXE.

References

[TUT] Manual Full XIP Porting (& MANY MORE TUTORIALS)

http://xdaforums.com/showthread.php?t=438676

XIP Porting Guide

http://xdaforums.com/showthread.php?t=379598
[Windows Mobile] hilaireg:
Changing the Unsigned CAB Policies

Security policies are used for configuring security settings that are then enforced with the help of security roles and certificates. They provide the flexibility to control the level of security on the device. The policies are defined globally and enforced locally in their respective components. The security policy is set during boot by executing a .provxml configuration file. This provisioning file is in ROM and contains the default setting specified by the OEM. The provisioning document is an Extensible Markup Language (XML) file that is assigns security settings to the device.

Typically, the mxipupdate_oemoperators_100.provxml file contains the default security policies that will be applied to the device. To allow execution of unsigned .CAB files, we need to change the default security policy settings that pertain to .CAB files.

For the purposes of this guide, we will add or change the following unsigned policy setting ID’s:

ID 4101: Unsigned CABS Policy = 8

ID 4102: Unsigned Applications Policy = 1

ID 4122: Unsigned Prompt Policy = 1

* IMPORTANT *

Policy settings may appear in other files. You may wish to perform a search through .TXT, .RGU, and other .PROVXML files using the keywords such as: security, policies, policy.

Tools Required

The following tools are required to edit .PROVXML files.

UTF-8 Text Editor

Procedure

The following procedure will add/change the unsigned policy settings to permit the installation of unsigned .CAB files.

Navigate to the C:\XDA\MY_KITCHEN\OEM\OperatorPkg\ folder.

Verify that the mxipupdate_oemoperators_100.provxml is not set as Read Only.

Launch your UTF-8 Text Editor.

Use the Search feature to find the following section:

<!--337.01_SecurityPolicy-->

Ensure that the following lines are present in the section:

<!--337.01_SecurityPolicy-->

<characteristic type="SecurityPolicy">

...

<parm name="4101" value="8" />

<parm name="4102" value="1" />

<parm name="4122" value="1" />

...​

</characteristic>

Save the changes to the mxipupdate_oemoperators_100.provxml; ensure that the file is saved in UTF-8 format.

Exit your UTF-8 Text Editor.

Verify that the mxipupdate_oemoperators_100.provxml is set to Read Only.

Tip

Make a backup copy of the mxipupdate_oemoperators_100.provxml file before editing; delete the backup file when done.

Observe the line formatting and spacing in the mxipupdate_oemoperators_100.provxml file.

When saving the file, select the Save As menu option and put quotes ["] around the file name so as to avoid additional file extensions.

References

Security Policy Settings for Windows 6.x Mobile-Based Devices

http://msdn.microsoft.com/en-us/library/bb416355.aspx

Security Policy Settings for Windows 5.x Mobile-Based Devices

http://msdn.microsoft.com/en-us/library/ms889564.aspx

What Do The SmartPhone Policy ID's Mean

http://www.xs4all.nl/~itsme/projects/xda/smartphone-policies.html