Found solution to get manual brightness working on windows 10 firmwares on our 1020 devices
Change registry with interop tools or what ever.
Select this provider this device, then registry browser, HKEY_LOCAL_MACHINE/ SOFTWARE/ Microsoft/ Autobrightness/ABSManualBrightness.
Change "Registry Value Type" to "Multi String".
Then Registry Value Data to
1
2
3
Save and restart device and smile :victory:
Thanks for info.
These settings i have now 1020 and brightness settings works great.
Numbers in () is original and without is modified.
HKLM\Software\Microsoft\AutoBrightness
- ABSAutoMaxBrightness (3) 6
- ABSManualBrightness (3) 1 3 6 (the variable here is multistring)
- ABSMonitorControl (1) 1
https://msdn.microsoft.com/en-us/library/windows/hardware/mt168406(v=vs.85).aspx
HKLM\Software\Microsoft\Shell\OEM\Brightness
-LowBrightness (1) 1
-MediumBrightness (2) 3
-Hightbrightness (3) 6
https://msdn.microsoft.com/en-us/library/windows/hardware/mt147021(v=vs.85).aspx
HKLM\Software\OEM\AutoBrightness
- ABSPercentIntensityMapping 2 3 4 (the variable here is multistring)
- ABSRangeMilliLuxMapping 1 2 MAX (the variable here is multistring)
- DimBrightness 1
- Transitiondelay 0
Supel low light u get when change settings manually low and then autobrightness on.
Normal light, manually normal and then autobrigtness on.
is it normal that i can't change registry type? I use interop tools on lumia 925
found interop tools L release
Yes
If you cant change the registry, you need to go into interop tools app
-interop unlock
And turn on restore NDTKSvc then restart the phone and edit the registry
Related
where can i dim the backlight? i'm searching for the backlight settings, but haven't found anything.
any reg tweak?
thx very much.
do u need to check some key register.....
i guess not. did some research, seems you can't set the backlight in any way.
poor, but true.
under power settings there is 'backlight off' and 'display off'.
i set the backlight off to quick (15secs) but display off to 2 minutes. The display is quite readable indoors with the backlight off (I suspect it is on a little - so the description in settings is not accurate).
Hopefully a firmware update will bring proper brightness control. Although I rememer my C500 and C550 not having it as well.
rgds
Im not sure if the hardware supports multiple levels for backlight.
I tried an app to test.(only tested on vda2 wm 5.0)
the only thing that happens is off or on.
but it works on ppc version!(didnt try on real ppc , but the emulator does switch light conditions! nothing happens on sp emulator)
no, unfortunately it's not supported.
big, big disadvantage!
Verify this Keyreg....and update on your SP.
HKEY_CURRENT_USER\Control Panel\Backlight\
- AcTimeout = 60
- AutoSensor = 1
- BatteryBacklight = 40
- BatteryTimeout = 15
- m_ACTimeout = 0
- m_BatteryTimeout = 0
Byeee
Sky_Lab
While poking around 20954, and comparing it to the stock fuze build 19971 or whatever it is, I noticed that at some point in the 20xxx series there were several registry keys added pertaining to In-Call recording, tried fiddling with them a bit but don't see anything specific kicking in.. maybe someone else wants to tinker!
Code:
[HKEY_LOCAL_MACHINE\System\AudioRecording]
"Enabled"=dword:1
[HKEY_CURRENT_USER\Software\Microsoft\Voice]
"AllowInCallRecording"=dword:1
"EnableCallRecordMenuItem"=dword:1
I might be wrong on the HKLM\HKCU parts, try adding them to both.. no idea where the menu option is supposed to show up either, but i'd assume the dialer since it's cprog.exe that checks for these
Also, there are new keys in the 20xxx series pertaining to Gestures, which are now supported by WinMo itself, mimicing some of the features available in HTC's TouchFlo (and probably performing better, too, )
Code:
[HKEY_CURRENT_USER\ControlPanel\Gestures\Touch]
"Disabled"=dword:0 ; 0 for disabled, allows multi-select, 1 for enabled, doesn't work so hot with multi-select
"ScrollFriction" ; unknown default value or units
"ScrollInterval" ; unknown default value or units
"Multiplier" ; unknown default value or units
"Length" ; unknown default value or units
"Multiplier" ; unknown default value or units
"Tolerance" ; unknown default value or units
"Timeout" ; unknown default value or units
[HKEY_LOCAL_MACHINE\SYSTEM\GWE\TouchFilter]
"FastestTapTime" ; unknown default value or unit of measure, guess=units in ms
"MaxTapSpan" ; unknown default value or unit of measure, guess=units in pixels
"MaxTouchFilterDelay" ; unknown default value or unit of measure, guess=units in ms
More new stuff:
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\GDI\GLYPHCACHE]
"Limit0"=dword:12000 ; unknown, "limit" key controls font cache, limit0 may be a secondary font cache or..?
[HKEY_LOCAL_MACHINE\ControlPanel\Power]
"DynamicChargeicon"=dword:1 ; set to 0 for normal "plugged in" icon when on ac/usb power, set to 1 for blinking battery icon to indicate charging
[HKEY_CURRENT_USER\ControlPanel\Phone]
"EnableTextResponse"=dword:1 ; unknown
"DisableGSMNetworkSelection"=dword:0 ; unknown, but you can guess from its name
[HKEY_LOCAL_MACHINE\Software\Microsoft\SIClnt]
"ShowAllSIPopups"=dword:1 ; imagine this has something to do with SI/SL messages from provider, see http://msdn.microsoft.com/en-us/library/ms890494.aspx
"HideMediumSIPopups"=dword:0 ; see above
[HKEY_LOCAL_MACHINE\System\Inbox\Settings]
"ShowReplySMSSK1"=dword:1 ; unknown
"MsgClassMenuOrder" ; unknown default or units of mesaure
[HKEY_LOCAL_MACHINE\System\Inbox\Settings\OEM]
"CustomEventHandler" ; unknown
[HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Settings]
"ReminderAllDay"=dword:1 ; unknown
[HKEY_LOCAL_MACHINE\System\Inbox\AutoConfiguration]
"DefaultDestinationNetworkGUID" ; unknown, probably directs sms/mms/email to use a specific connection (i.e. wap.cingular vs. ims.cingular vs. isp.cingular) - value is most likely a string that matches the connection GUID
[HKEY_CURRENT_USER\Software\Microsoft\Inbox]
"DisableAutoSSL"=dword:0 ; unknown
[HKEY_LOCAL_MACHINE\Software\Microsoft\Pim\Contacts]
"SIMNewContact" ; unknown
[HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms]
"TcpRttVarAdjustment" ; unknown, probably a dynamic RTT prediction
"TcpSmoothRttAdjustment" ; see above, probably toggle dword 0/1
If a value doesn't work, try swapping HKCU for HKLM and vice versa, I jotted these down as I was going along looking for other things, and left that part off
New sound category:
Code:
[HKEY_CURRENT_USER\ControlPanel\Sounds\CallStart]
IE Mobile 6:
Code:
[HKEY_LOCAL_MACHINE\Security\Internet Explorer]
"MSHTML"=dword:0 ; 0 for old IE, 1 for IE Mobile 6
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Settings]
"Always Use My Font Size"=dword:1 ; overrides absolute font sizes on webpages, uses menu setting for font sizes
Prototype UI? Removes the start button and x button..
Code:
[HKEY_LOCAL_MACHINE\Adaptation]
"PROTOTYPE"=dword:1
yah ive seen that "record call" option in monx's roms..doesnt work but has a start and a stop option in the pop up righ softkey menu while in the dialer..
Does he get the record call option from the same registry edits or another method?
not sure..ill pm him or you can if you want
bump for IE 6 Mobile toggle
bump for prototype UI
Bump for a useful IE Mobile 6 key that makes xda-devs alot easier to read on ie mobile 6:
Code:
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Settings]
"Always Use My Font Size"=dword:1 ; overrides absolute font sizes on webpages, uses menu setting for font sizes
[HKEY_LOCAL_MACHINE\Adaptation]
"PROTOTYPE"=dword:1
this was not present for me in 20954, and doesn't do anything when added.... I tried in HKCU too...
Search for string "PROTOTYPE" type unicode in \SYS\Shell\shell32.exe\S000
If you don't have it, you must have a different version of 20954 than me? Works here (note it needs a soft reset)
in Comm Manager, turning 3G Icon "OFF" will activate GPRS only.. whereas turning it "ON" will make it to Auto.. can u pls advise me how to make it 3G only instead of Auto when turning it "ON"?
coz i want to 'force' my device to use 3G only in my area.thx
comm manager is written by htc, not microsoft, and thus is outside the scope of this thread.
I just got the Sprint TP2 and I don't want to use a different rom yet. Is there any settings I could turn off or turn on to make this phone more tolerable? It's just so slow.
GripR said:
I just got the Sprint TP2 and I don't want to use a different rom yet. Is there any settings I could turn off or turn on to make this phone more tolerable? It's just so slow.
Click to expand...
Click to collapse
Get a registry editor and just make a couple registry edits as follows.
HKLM\System\Storagemanager\Fatfs
change "Cachesize" to 32768
HKLM\SYSTEM\GDI\GLYPHCACHE
Set both limit settings to 32768
HKLM\Software\OEM\TFLOSettings
create dword key "SpeedHigh" set value to 5
create dword key "SpeedLow" set value to 14
(Do not add the quotes, and its case sensitive)
HKLM\SYSTEM\StorageManager\Filters\fsreplxfilt
Set “ReplStoreCacheSize” to 8192
HKLM\Drivers\BuiltIn
Set "battery" to 30000
Another good one to increase your In call Volume
HKCU\control panel\sound categories\\in call
set "initial volume" to 4
That should help ya out a lil, But just so you know, stock roms run like crap outta the box, cuz carriers wanna put all that junk you don't need in the rom.
Im starting this thread for anyone having the same issue as me where by adding the property ro.config.media_vol_steps to /system/etc/prop.default and assigning their prefered steps value, ie '= 30', results in multiple volume ranges devisable by 15.
Apparently this affects the HTC UI sense as well.
For example if I assign the value 37 to the above property (I do get 37 steps) but when I test by playing something on spotify and increase volume using the buttons I get -
step 0 = mute
step 15 = max volume
step16 = mute
step 30 = max volume
step 31 = mute
step 37 = volume 6
Anything below 15 works as expected.
The same happens if you've rooted with Magisk and do it via prop editor or any other editor.
Iv been trying to find a solution for this for months with no success hence up the creek with no paddle.
I have coding abilities but for me X86 assembly is easier than than understanding the various tool chains / libraries / compilers required to debug an Android device.
Id like to at least know where in the architecture I should be focusing on.
Is it vendor or system related?
A persistant setting?
Is the setting pre compiled so would need custom ROM ie a library file (.so) where other devices simply allow to change the property?
I beleive it must be solvable just hoped I could get at least a hyperthetical view of the problem from someone more familiar with the sourcery of Android!
You can get fine volume control from the GUI (swipe down) how can this be mapped to Volume_key_up / volume_key_down ?
Thanks.
You need to be on 60Hz refresh rate before applying these steps
Step 1 : Install "SetEdit" app from play store
Step 2 : Select 120Hz refresh rate option (Settings > Display > Refresh Rate)
Step 3 : Open "SetEdit" app and open "System Table" from drop down menu
Step 4 : We need to change these values
Select "min_refresh_rate" > Edit Value > 90 > Save Changes
Select "peak_refresh_rate" > Edit Value > 90 > Save Changes
Select "user_refresh_rate" > Edit Value > 90 > Save Changes
Step 5 : Restart Device
Step 6 : Disable system app "Battery and performance" (com.miui.powerkeeper)
Step 7 : Go to (Settings > Apps > Manage apps > Battery and performance) and clear all app data.
Step 8 : Go to Developer Options and Enable Show refresh rate
Step 9 : Its Done, no need to restart your device
I have tested this on MIUI by xiaomi.eu 13.0.9 SJUMIXM and it worked without any issues
In step 4, only the third one is necessary and you don't to do step 5 and beyond.
After changing the value, just open the recents and it'll automatically go 90.
JuanTamqd21 said:
In step 4, only the third one is necessary and you don't to do step 5 and beyond.
After changing the value, just open the recents and it'll automatically go 90.
Click to expand...
Click to collapse
I just tested what you said, Try to open youtube... It will go back to 60Hz
Usama-CW said:
I just tested what you said, Try to open youtube... It will go back to 60Hz
Click to expand...
Click to collapse
didn't experienced that on stock 13.0.4