Jump to content

Survey! Default registry power settings, SD power issues


Guest hardcore

Recommended Posts

Guest hardcore

Hi all!

It appears that there are several power management settings that can be set using the Registry.

Can you guys run this XML input file with RapiConfig:

<wap-provisioningdoc>


   <characteristic type="Registry">


      <characteristic-query type="HKLMSYSTEMCurrentControlSetControlPower" />


   </characteristic>


</wap-provisioningdoc>
Paste the results of RapiConfigOut.xml in this thread. Please also state your ROM version. I am using the Qtek ROM 1.9.14.1. These are my default settings:
<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="Interfaces">


    <parm name="{98C5250D-C29A-4985-AE5F-AFE5367E5006}" value="Power-manageable NDIS miniports"/>


    <parm name="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}" value="Power-manageable display"/>


    <parm name="{A32942B7-920C-486b-B0E6-92A702A99B35}" value="Generic power-manageable devices"/>


    <parm name="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}" value="Power-manageable block devices"/>


 	 </characteristic>


 	 <characteristic type="State">


    <characteristic type="On">


   	 <parm name="Default" value="0"/>


   	 <parm name="Flags" value="65536"/>


    </characteristic>


    <characteristic type="UserIdle">


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


   	 <parm name="Flags" value="0"/>


    </characteristic>


    <characteristic type="SystemIdle">


   	 <characteristic type="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Default" value="2"/>


   	 <parm name="Flags" value="0"/>


    </characteristic>


    <characteristic type="Suspend">


   	 <characteristic type="{98C5250D-C29A-4985-AE5F-AFE5367E5006}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Default" value="3"/>


   	 <parm name="Flags" value="2097152"/>


    </characteristic>


    <characteristic type="Reboot">


   	 <parm name="Default" value="4"/>


   	 <parm name="Flags" value="8388608"/>


    </characteristic>


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


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


 	 </characteristic>


 	 <characteristic type="ActivityTimers">


    <characteristic type="UserActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


    <characteristic type="SystemActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


 	 </characteristic>


 	 <characteristic type="Timeouts">


    <parm name="ACSuspend" value="0"/>


    <parm name="BattSuspend" value="0"/>


    <parm name="BatteryPoll" value="10000"/>


    <parm name="ACUserIdle" value="60"/>


    <parm name="ACSystemIdle" value="300"/>


    <parm name="BattUserIdle" value="60"/>


    <parm name="BattSystemIdle" value="180"/>


 	 </characteristic>


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


 	 <parm name="BattPowerOff" value="0"/>


 	 <parm name="ExtPowerOff" value="0"/>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

I have tried adding entries to the State=UserIdle and State=SystemIdle to shutdown the Block device class and display device classes (I think SD card belongs to this). Hopefully this will save power...

Link to comment
Share on other sites

Guest hardcore

Does nobody want to do this? We could find out the differences between the ROMs, improve battery life and maybe even solve that SD going off issue. (I dont have that issue though.)

Link to comment
Share on other sites

Guest Toyota-F1.com

I don't totally understand what you want me to do :?

My data might be useful because I have found that SD Card does not reduce battery life (search for my thread "Battery Report" - something along those lines), plus I have the original ROM in my SPV3.

Link to comment
Share on other sites

Guest MrMagoo

i have E200 op 2.6.1.3, man 1.11.1.4, ms 4.20.13288.0

these are not quite default but close enough :)

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="Timeouts">


    <parm name="BattSystemIdle" value="180"/>


    <parm name="BattUserIdle" value="60"/>


    <parm name="ACSystemIdle" value="300"/>


    <parm name="ACUserIdle" value="60"/>


    <parm name="BatteryPoll" value="10000"/>


    <parm name="BattSuspend" value="0"/>


    <parm name="ACSuspend" value="0"/>


 	 </characteristic>


 	 <characteristic type="ActivityTimers">


    <characteristic type="SystemActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


    <characteristic type="UserActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


 	 </characteristic>


 	 <characteristic type="State">


    <characteristic type="Reboot">


   	 <parm name="Flags" value="8388608"/>


   	 <parm name="Default" value="4"/>


    </characteristic>


    <characteristic type="Suspend">


   	 <characteristic type="{98C5250D-C29A-4985-AE5F-AFE5367E5006}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Flags" value="2097152"/>


   	 <parm name="Default" value="3"/>


    </characteristic>


    <characteristic type="SystemIdle">


   	 <characteristic type="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Flags" value="0"/>


   	 <parm name="Default" value="2"/>


    </characteristic>


    <characteristic type="UserIdle">


   	 <parm name="Flags" value="0"/>


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


    </characteristic>


    <characteristic type="On">


   	 <parm name="Flags" value="65536"/>


   	 <parm name="Default" value="0"/>


    </characteristic>


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


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


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


 	 </characteristic>


 	 <characteristic type="Interfaces">


    <parm name="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}" value="Power-manageable block devices"/>


    <parm name="{A32942B7-920C-486b-B0E6-92A702A99B35}" value="Generic power-manageable devices"/>


    <parm name="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}" value="Power-manageable display"/>


    <parm name="{98C5250D-C29A-4985-AE5F-AFE5367E5006}" value="Power-manageable NDIS miniports"/>


 	 </characteristic>


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


 	 <parm name="DisableGwesPowerOff" value="0"/>


 	 <parm name="ExtPowerOff" value="0"/>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

Link to comment
Share on other sites

Guest Vector

OK, I got RapiConfig, i typed "upload battery.xml" (that's what i called the xml file)

But all i got out is:

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKCUControlPanelHome">


 	 <parm name="colorscheme" value="" datatype="string"/>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

What am i doing wrong? :roll:

Link to comment
Share on other sites

Guest MrMagoo
Toyota; check out This thread..

It's rapi config, read the instructions on that page :)

but it hasn't totally worked out for me :?

You have been confused by a thread which uses RapiConfig to configure the home screen.

For this exercise, you need to :

1. Create a folder e.g. c:rapi

2. Put RapiConfig.exe in that folder

3. Create an xml file e.g. power.xml in that folder (c:rapi) and paste the following text into the xml file:

<wap-provisioningdoc> 


   <characteristic type="Registry"> 


      <characteristic-query type="HKLMSYSTEMCurrentControlSetControlPower" /> 


   </characteristic> 


</wap-provisioningdoc>
4. Save the xml file 5. Open a dos prompt and change directory to c:rapi 6. type
RapiConfig /P power.xml

7. Wait for it to finish...

8. open RapiConfigOut.xml to see the results

Link to comment
Share on other sites

Guest Vector

Cheers MrMagoo! :lol:

I'm running the Orange UK rom

operator version : 2.6.1.3

Manufacturer: 1.11.1.4

Microsoft: 4.20.13288.0

My reults:

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="Interfaces">


    <parm name="{98C5250D-C29A-4985-AE5F-AFE5367E5006}" value="Power-manageable NDIS miniports"/>


    <parm name="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}" value="Power-manageable display"/>


    <parm name="{A32942B7-920C-486b-B0E6-92A702A99B35}" value="Generic power-manageable devices"/>


    <parm name="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}" value="Power-manageable block devices"/>


 	 </characteristic>


 	 <characteristic type="State">


    <characteristic type="On">


   	 <parm name="Default" value="0"/>


   	 <parm name="Flags" value="65536"/>


    </characteristic>


    <characteristic type="UserIdle">


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


   	 <parm name="Flags" value="0"/>


    </characteristic>


    <characteristic type="SystemIdle">


   	 <characteristic type="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Default" value="2"/>


   	 <parm name="Flags" value="0"/>


    </characteristic>


    <characteristic type="Suspend">


   	 <characteristic type="{98C5250D-C29A-4985-AE5F-AFE5367E5006}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Default" value="3"/>


   	 <parm name="Flags" value="2097152"/>


    </characteristic>


    <characteristic type="Reboot">


   	 <parm name="Default" value="4"/>


   	 <parm name="Flags" value="8388608"/>


    </characteristic>


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


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


 	 </characteristic>


 	 <characteristic type="ActivityTimers">


    <characteristic type="UserActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


    <characteristic type="SystemActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


 	 </characteristic>


 	 <characteristic type="Timeouts">


    <parm name="ACSuspend" value="0"/>


    <parm name="BattSuspend" value="0"/>


    <parm name="BatteryPoll" value="10000"/>


    <parm name="ACUserIdle" value="60"/>


    <parm name="ACSystemIdle" value="300"/>


    <parm name="BattUserIdle" value="60"/>


    <parm name="BattSystemIdle" value="180"/>


 	 </characteristic>


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


 	 <parm name="BattPowerOff" value="0"/>


 	 <parm name="ExtPowerOff" value="0"/>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

:)

Link to comment
Share on other sites

Guest hardcore

Hi all,

First of all sorry for being too cryptic in the original request. My bad. :lol:

Here is what I am trying to do, or get info on. This is info on the Registry settings that affect the Power Management in MS Smartphone 2003.

http://msdn.microsoft.com/library/default....tatemapping.asp

Basically I wanted to get a sample of what power management settings the different vendors put on their ROMs. Its interesting to note that there has not been too much deviation from MS's recommendations.

MrMagoo - thanks again for helping out and being so useful :) Out of curiousity, can I ask how does your BLManualSD utility turn on/off the SD card? Which function and what device is the SD slot?

Next I might be digging around the Registry settings for the Drivers and seeing what we might be able to hack out of it.

Link to comment
Share on other sites

Guest MrMagoo

hardcore,

BLmanualSD turns off the card by calling DeactivateDevice() and back on using ActivateDevice() and it looks for a device called DSK1: - although this should probably do something much more clever to find it - i suppose it could end up as DSK2: or anything else really - but it sort of works :)

Link to comment
Share on other sites

Guest hardcore

Hi all,

I'm not sure if I am just imagining things, but I think I have gotten better battery life out of the phone by adding the following registry keys:

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="State">


    <characteristic type="SystemIdle">


   	 <parm name="DSK1:" value="4" datatype="integer" />


   	 <parm name="HSD1:" value="4" datatype="integer" />


   	 <parm name="SDC1:" value="4" datatype="integer" />


    </characteristic>


 	 </characteristic>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

Basically what this does, is to request the Power Manager to put the following devices into the lowest power mode, when the phone goes into the "SystemIdle" state:

DSK1: - SD memory device

HSD1: - SD card host controller

SDC1: - SD card bus controller

It seems to have similar effect to manually turning on/off the SD card using MrMagoo's BLManualSD tool. Except this is automatic.

I'm using the latest QTek ROM. If you like you, why not give it a try eh? U must reboot the phone for it to take effect.

Link to comment
Share on other sites

Guest Toyota-F1.com
Hi all,

I'm not sure if I am just imagining things, but I think I have gotten better battery life out of the phone by adding the following registry keys:

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="State">


    <characteristic type="SystemIdle">


   	 <parm name="DSK1:" value="4" datatype="integer" />


   	 <parm name="HSD1:" value="4" datatype="integer" />


   	 <parm name="SDC1:" value="4" datatype="integer" />


    </characteristic>


 	 </characteristic>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

Basically what this does, is to request the Power Manager to put the following devices into the lowest power mode, when the phone goes into the "SystemIdle" state:

DSK1:     - SD memory device

HSD1:     - SD card host controller

SDC1:     - SD card bus controller

It seems to have similar effect to manually turning on/off the SD card using MrMagoo's BLManualSD tool. Except this is automatic.

I'm using the latest QTek ROM. If you like you, why not give it a try eh? U must reboot the phone for it to take effect.

This sounds pretty big if it saves battery life. Why not do some testing on it? Check out my thread which contains the word "battery life" in the title and it's in this forum (HTC Voyager).

Let us know how it goes... :D

Link to comment
Share on other sites

Guest d6d8

Hi, I have the darn SD bug on my O2 Xphone (running on the 02 rom).

Operator: 1.10.18.3

Manufacturer: 1.11.18.23

Microsoft: 4.20.13349.0

Language:1.11.18.23

Filesystem:: 4.20.13349.0

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="Interfaces">


    <parm name="{98C5250D-C29A-4985-AE5F-AFE5367E5006}" value="Power-manageable NDIS miniports"/>


    <parm name="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}" value="Power-manageable display"/>


    <parm name="{A32942B7-920C-486b-B0E6-92A702A99B35}" value="Generic power-manageable devices"/>


    <parm name="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}" value="Power-manageable block devices"/>


 	 </characteristic>


 	 <characteristic type="State">


    <characteristic type="On">


   	 <parm name="Default" value="0"/>


   	 <parm name="Flags" value="65536"/>


    </characteristic>


    <characteristic type="UserIdle">


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


   	 <parm name="Flags" value="0"/>


    </characteristic>


    <characteristic type="SystemIdle">


   	 <characteristic type="{EB91C7C9-8BF6-4a2d-9AB8-69724EED97D1}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Default" value="2"/>


   	 <parm name="Flags" value="0"/>


    </characteristic>


    <characteristic type="Suspend">


   	 <characteristic type="{98C5250D-C29A-4985-AE5F-AFE5367E5006}">


      <parm name="Default" value="4"/>


   	 </characteristic>


   	 <parm name="Default" value="3"/>


   	 <parm name="Flags" value="2097152"/>


    </characteristic>


    <characteristic type="Reboot">


   	 <parm name="Default" value="4"/>


   	 <parm name="Flags" value="8388608"/>


    </characteristic>


 	 </characteristic>


 	 <characteristic type="ActivityTimers">


    <characteristic type="UserActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


    <characteristic type="SystemActivity">


   	 <parm name="Timeout" value="10"/>


    </characteristic>


 	 </characteristic>


 	 <characteristic type="Timeouts">


    <parm name="ACSuspend" value="0"/>


    <parm name="BattSuspend" value="0"/>


    <parm name="BatteryPoll" value="10000"/>


    <parm name="ACUserIdle" value="60"/>


    <parm name="ACSystemIdle" value="300"/>


    <parm name="BattUserIdle" value="60"/>


    <parm name="BattSystemIdle" value="180"/>


 	 </characteristic>


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


 	 <parm name="BattPowerOff" value="0"/>


 	 <parm name="ExtPowerOff" value="0"/>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

Could such minor registry settings for power management cause the bug?

Link to comment
Share on other sites

Hi all,

I'm not sure if I am just imagining things, but I think I have gotten better battery life out of the phone by adding the following registry keys:

<wap-provisioningdoc>


	<characteristic type="Registry">


  <characteristic type="HKLMSYSTEMCurrentControlSetControlPower">


 	 <characteristic type="State">


    <characteristic type="SystemIdle">


   	 <parm name="DSK1:" value="4" datatype="integer" />


   	 <parm name="HSD1:" value="4" datatype="integer" />


   	 <parm name="SDC1:" value="4" datatype="integer" />


    </characteristic>


 	 </characteristic>


  </characteristic>


	</characteristic>


</wap-provisioningdoc>

Basically what this does, is to request the Power Manager to put the following devices into the lowest power mode, when the phone goes into the "SystemIdle" state:

DSK1:    - SD memory device

HSD1:    - SD card host controller

SDC1:    - SD card bus controller

It seems to have similar effect to manually turning on/off the SD card using MrMagoo's BLManualSD tool. Except this is automatic.

I'm using the latest QTek ROM. If you like you, why not give it a try eh? U must reboot the phone for it to take effect.

Does resuming using the phone powers up the SD device again?

Link to comment
Share on other sites

Guest hardcore

Hi, sure it does power up the card again. Actually, as far as I can tell, the card device does not "disappear" like when using MrMagoo's BLManualSD. But I'm quite sure that the card itself went into a "sleep" mode - how? This is my observation:

1. Play music using Media Player. While an MP3 is playing half-way, pause it.

2. Leave the phone alone to let it go into the systemidle mode.

3. Press a button to activate the phone again, go back to Media Player... and Media Player starts from the Playlist screen again. This is what happens after u eject/insert the SD card. So my guess is that the SD card was indeed "powered down" in some sense.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.