yashsingh1/xdaforums huggingface dataset:
[HTC Vox] tobbbie:
That is strange - the system should go off when the battery is below a certain voltage. You can observe the voltage e.g. with celetask or other tools. The recommended cut-off voltage is 3.5 -3.6 Volts - below that a LiIon rechargable battery should not be discharged as the number of possible charge-discharge cycles will decrease.

There are two system of charging in the devices:

- onboard loader (or HW only): when the device is off - only light indicators

- controlled/influenced by OS: when the device is on

They can be rather independent of each other, but both of them should stop discharge at 3.6 V and stop charge at 4.2 V. I don't know which chip cares for the charging, but for sure also some adjustments over time is possible in this scope.

The interpretation of the voltage over time in %-capacity is much depending on the vendor, but for the HTC (e.g. Tornado) my experience is that it is quite ok. Obviously the adjustment should deliver that 0% equals the cut-off voltage. If you are patient (and curious) you could evaluate the V-% relation for your device.

Your full discharge may have re-adjusted it - retry and see if that still happens.

For LiIon batteries it is NOT recommended to have many full discharge cycles - they can happily take full charge all time without memory effect. This will prolong battery life.
[HTC Vox] Pikranus:
Thank you guys,

I discharged my Vox to see if it would happen again, but it turned off at 1%. And I think the percentage had decreased a bit slower than last time.
[Touch Cruise 2 General] koilos:
Can you help me?

I have tried " Duttys Disable Sleep in Call " but it doesn't work.

I have also tried to modify:

HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL

EnableFastDormantDisplayDuringCall=0

and:

HKEY_CURRENT_USER\ControlPanel\Phone

Sleep=0

nothing to be done: it keeps on not working!

do you have some suggestion?

I apologize me for mine bad English and I in advance thank you
[Touch Cruise 2 General] Dair:
Hello, personally I didn't try to solve this as I do like the behavior as it is. But this topic was discussed here in Jade (same chipset and TF2D) forums and here is some tip too.

It looks like there is no confirmed solution for our devices yet though. (I know I didn't help too much this way.)
[Touch Cruise 2 General] torrentonly:
koilos: Why do you want to do that? I think, that disabling screen while calling is quite good feature, because I don't want to perform some operations with my ear :). And if you want to do some operations, you can always short press power button to enable it.

Anyway, there are some interesting options, you can play with on your own risk, like

HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL -> BatteryTimeoutInCall (default: 5)

HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL -> BatteryTimeoutSuspendInCall (default: 5)

I didn't look at that, because I didn't have time now. Number should be time in seconds (my device's display goes black 5 seconds after call connects). Maybe it will need restart after change. Maybe it will do something else.
[Touch Cruise 2 General] koilos:
I have tried to modify the keys that you have recommended me ( planned value 60 ) , the display keeps on going off after 5 seconds.

I have obviously effected the soft reset.

Thanks however for the kind answer, if I had to find the solution it will be' my care to post it
[Touch Cruise 2 General] iampong:
:)check out ' Auto adjust backlight' back light will not sleep when make a call
[Windows Mobile] hilaireg:
Extracting the RUU_SIGNED.NBH Contents

An .NBH is a signed group of modules or packages; they are typically comprised of .NB files. An .NBH can contain any combination of .NB files. An .NB file is a block of code that can be a Radio ROM, Operating System packages (XIP and IMGFS), Startup Splash Screen (or SPL).

The file we will be working with is the OS.NB file; it contains the ULDR, XIP, and IMGFS (OEM, SYS). To extract the contents of an .NBH file, we initiate the Ervius NBH/NB/PAYLOAD Dumper tool from within the Generic Visual Kitchen.

Upon completion, the following files will have been extracted: OS.nb, OS.nb.payload. Additionally, the Ervius NBH/NB/PAYLOAD Dumper tool creates a DUMP folder that contains all the files required.

Tools Required:

The following Ervius Visual Kitchen tool will be used for the RUU_SIGNED.NBH extraction activities.

Dump NBH/NB/PAYLOAD

Procedure

The following procedure initiates the ROM extraction activity via the Ervius NBH/NB/PAYLOAD Dumper tool built into the Generic Visual Kitchen. The extraction process can take a significant amount of time to complete.

Copy the RUU_SIGNED.NBH file to the C:\XDA\My_Visual_Kitchen\BaseROM\ folder.

Navigate to the C:\XDA\My_Visual_Kitchen\ folder.

Launch ErviusKitchen.exe.

At the multiple warning messages, click OK.

Warnings that may appear include:

Folder Not Found

Could Not Find A Part Of The Path

You Need To Specify … First

Click the Dump NBH/NB/PAYLOAD button.

Navigate to the C:\XDA\MY_VISUAL_KITCHEN\BaseROM\ folder.

Select the RUU_signed.nbh file and then click Open.

At the All Done... Nbh/nb/payload Dumped and ''Kitchen'' created Successfull!!! message, close the Ervius Visual Kitchen application.

Navigate to the C:\XDA\MY_VISUAL_KITCHEN\DUMP\ folder.

Move the sub-folders (and content) to the C:\XDA\MY_VISUAL_KITCHEN\ folder.

At the Confirm Folder Replace message, click Yes To All.

At the Confirm File Move message, click Yes To All.

Tip

The C:\XDA\MY_VISUAL_KITCHEN\BaseROM\Dump\ folder should be empty at this point – and can be removed.
[Windows Mobile] hilaireg:
Reducing the .PAYLOAD File

At this point, the Ervius NBH/NB/PAYLOAD Dumper tool has removed the contents of the IMGFS (OEM, SYS) from the .PAYLOAD file in preparation for changes to the ULDR and XIP. Removing the IMGFS (OEM, SYS) contents from the .PAYLOAD file reduces the size of the .PAYLOAD file making it easier to work with.

The Ervius NBH/NB/PAYLOAD Dumper tool has placed a copy of the reduced .PAYLOAD file in the C:\XDA\My_Visual_Kitchen\ROM\Raphael\ folder.

Tip

Advanced .PAYLOAD file operations can be performed using the XIPPORTEREX & ROM tool.

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. 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.

At this point, the Ervius NBH/NB/PAYLOAD Dumper tool has extracted the contents of the XIP.BIN and placed a copy of the file in the C:\XDA\My_Visual_Kitchen\ROM\Raphael\ folder.

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

Tip

Advanced XIP.BIN file operations can be performed using the XIPPORTEREX & ROM tool.

You can change the ROM Date/Version using the XIPPORTEREX & ROM tool.

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:
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_VISUAL_KITCHEN\ROM\Raphael\20764\OEMXipKernel\ 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:
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 kitchen_build_rom.bat to set the Paging Pool size (initially set to 6MB) to a new size of 8MB.

Tools Required

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

Unicode Text Editor

Procedure

The following procedure will change the kitchen_build_rom.bat to set the Paging Pool size during ROM compilation.

Launch a text editor.

Navigate to the C:\XDA\MY_VISUAL_KITCHEN\Tools\ folder and open the kitchen_build_rom.bat file.

In the Find (Search) box, type:

implantxip

Add the following implantxip command line option:

-PP 8

Select the Save option in your text editor.

Select the Exit option in your text editor.

Tip

Spaces are usually required between command line options; the command line option should only appear once.

You can add output logging to file by adding the following command instructions to the end of a command line:

| ..\tools\mtee /+ ..\%LOG_FILE%

Newer versions of Ervius Visual Kitchen provide built-in logging and an Option button to set the Paging Pool size.
[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.

Unicode Text Editor

Procedure

The following procedure will change the kitchen_build_rom.bat disable the internal certificate store verification.

Launch a text editor.

Navigate to the C:\XDA\MY_VISUAL_KITCHEN\Tools\ folder and open the kitchen_build_rom.bat file.

In the Find (Search) box, type:

implantxip

Add the following implantxip command line option:

-NoCert

Select the Save option in your text editor.

Select the Exit option in your text editor.

Tip

Spaces are usually required between command line options; the command line option should only appear once.

You can add output logging to file by adding the following command instructions to the end of a command line:

| ..\tools\mtee /+ ..\%LOG_FILE%

Newer versions of Ervius Visual Kitchen provide built-in logging and an Option button to disable the Certificate Store verification.
[Windows Mobile] hilaireg:
Reducing the Update Loader (ULDR) Partition

The boot loader can accommodate multiple execute-in-place (XIP) regions where individual modules can be updated after the initial operating system image file has been written to the device – the ULDR is an example of this use. The Update Loader (ULDR) provides Flash-Over-The-Air (FOTA) capabilities permitting your carrier to issue changes such as Hotfixes over the cellular network – generally, most carriers avoid this practice.

As this is generally undesirable in a cooked ROM, since we are making modifications that a carrier Hotfix might roll back, we will reduce the partition. This will cause the device to report insufficient ULDR space to the carrier FOTA request … and the freed up space becomes available for our uses.

For the purposes of this guide, we are going to apply a change to the kitchen_build_rom.bat to reduce the ULDR – effectively providing approximately 3 MB of space.

Tools Required

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

Unicode Text Editor

Procedure

The following procedure will change the kitchen_build_rom.bat disable the internal certificate store verification.

Launch a text editor.

Navigate to the C:\XDA\MY_VISUAL_KITCHEN\Tools\ folder and open the kitchen_build_rom.bat file.

In the Find (Search) box, type:

implantxip

Add the following implantxip command line option:

-uldr

Select the Save option in your text editor.

Select the Exit option in your text editor.

Tip

Spaces are usually required between command line options; the command line option should only appear once.

You can add output logging to file by adding the following command instructions to the end of a command line:

| ..\tools\mtee /+ ..\%LOG_FILE%

Newer versions of Ervius Visual Kitchen provide built-in logging and an Option button to enable or disable ULDR reduction.
[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_VISUAL_KITCHEN\OEM\Raphael\0409\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
[Windows Mobile] hilaireg:
Changing the Unsigned Themes 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. If a signed theme file does not have a matching root certificate in the Software Publisher Certificate (SPC) store, the file is unsigned and is therefore not executed. To allow execution of unsigned Theme files, we need to change the default security policy settings that pertain to Theme files.

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

ID 4103: Unsigned CABS Policy = 16

* 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_VISUAL_KITCHEN\OEM\Raphael\0409\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="4103" value="16" />

...​

</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

Customizing the User Interface of Windows Mobile Powered Devices

http://msdn.microsoft.com/en-us/library/bb416487.aspx
[Windows Mobile] hilaireg:
Compiling the New RUU_SIGNED.NBH File

Brief Review

At this point, we have increased the Data Cache size, ensured that the implantxip command unlocks the Paging Pool and sets an initial size 8MB, disables Certificate checking, and reduces the ULDR. We changed the Unsigned .CAB policy, changed the Theme policy, and changed the Remote API (RAPI) policy.

This guide did not go into details about adding, changing, or removing ROM packages to/from the OEM and SYS folders. Additionally, the guide did not cover the steps required to port an XIP from a different ROM version or device – you'll eventually want to learn how to do these types of activities.

Compiling the ROM

We now need to assemble all of these changes into a new RUU_SIGNED.NBH file – this process if often referred to as ROM compilation. We are going to initiate the Create ROM tool from within the Generic Visual Kitchen to perform this process – there are newer versions of the Ervius Visual Kitchen available.

Tools Required

The following Ervius Visual Kitchen feature will be used for the RUU_SIGNED.NBH file creation activities.

Create ROM

Procedure

The following procedure initiates the ROM creation activity via a script that is included in the Generic Visual Kitchen. The creation process can take a significant amount of time to complete and requires user interaction at various stages.

Navigate to the C:\XDA\MY_VISUAL_KITCHEN\ folder.

Launch erviuskitchen.exe.

Click on the Device drop-down box and select Raphael from the list.

In the ROM Ver box, change the value: 5.05.405.1

Click the Create ROM button, the command window will begin to display processing information after a few minutes.

Wait for the All Done message to appear in the Bottom Status window.

Exit the Ervius Visual Kitchen application.

Copy the RaphaelWrapper.exe file from the C:\XDA\MY_VISUAL_KITCHEN\Tools\ folder to the C:\XDA\MY_VISUAL_KITCHEN\RELEASE_Raphael\ folder.

Tip

Processing information may take a few minutes before it appears in the Command window; this is a result of logging activity being spooled to logging files for troubleshooting purposes.

If the compilation is successful, the last three (4) lines in the Status window of the Ervius Visual Kitchen will display: ROM Builded successfull!!! Reenabling all skipped packages. All packages Reenabled. All done!!!

References

Visual multilang/multidevice/multibuild kitchen for last bepe rom-tools!!!

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