Related
Hi all,
I'm not sure what its called, but you know the context menus that come up basically whenever you hold your pointer over something for a while? It annoys me with the size they are in wm6.5. I love the speed of wm6.5 (tried both xplode's r7 (about to install 7.1...) and swampy's rls) but it really annoys me that they've made everything so big. Seems to take twice as long to do simple things now because now you have to scroll down menus to find what you're looking for. Is there anyway to bring this back to the good old "classic" sizes? I can't seem to find an option anywhere... and I realise loading a skinning app is just going to slow the OS down making the whole upgrade to 6.5 kinda pointless.
Also, does anyone know a way to speed up the actual time taken to register a tap and hold command? So that we don't have to spend as long to bring up the context menus?
Thanks in advance~
-kdp
that's a lot of questions. let me start with saying that i can not guarantee you, that the reg tweaks work. i found them for different devices and checked both my devices and didn't have the reg keys in there. so i don't knoiw if it helps you. Maybe, if i find out more, i'll post it later:
1. The size of the context and softkey menus:
a. the easiest way to influence the size and look of those menus would be, installing another theme. not just the color will change, but also the entire looks, so if you have a .tsk theme, copy it to the device and activate it, you will see it changed.
b. regitry tweak:
HKLM\System\GWE\Menu\Popfnt\
there should be two dword values that you can change to whatever you like.
ht=height is default set to 1000
wt=width is default set to 700
2. a skinning app is gonna slow down the os
- true, with wm6.5 there is really no need for anything else to make the graphics any nicer
3. tap and hold time:
HKCU\ControlPanel\Desktop\MenuShowDelay
right-click, select properties, and enter a value from zero to 999 milliseconds
if that value, does not exist, create it (string value)
if those values didn't work, you should try out advanced config, which can be downloaded here: http://www.pocketpc.ch/news/42529-freeware-advanced-config-3-0-a.html
there you have more than 200 tweaks for the os and don't need to search the registry for any values.
first off, a big thank you for the speediness of your reply.
i tried out the other tsk files i have... but unfortunately i don't have any older ones from wm5/6, only the newer 6.5 ones. they didn't seem to make much difference in size of anything... only the actual colour/font schemes. if you have any older tsk files that you wouldn't mind uploading, that'd be much appreciated as something to try.
the softkeys aren't so much an issue - i've got wisbar to disable them (yes yes, i know wisbar is a skinning app... but i prefer a nice cascading start menu to something i need to fumble through to find stuff any day) - its more the context menus that are annoying me.
the registry edit is interesting. changing the height and width actually also changes the zoom on the font size... i'm not sure how this is being calculated, but the font is clearly getting smaller the smaller you set the dimensions. it seems like its taking a predefined box with the text designed to take up a predefined percentage of it and then letting you put in the dimensions of the box... basically so that no matter what numbers you plug in, you'll always have the rather annoying amount of space being wasted between items in the context menus. though all that said and done, 750 for height and 350 for width are far more workable than the previous settings. more than legible too imo~
the tap and hold time tweak worked wonderfully
thanks again~
Tap and Hold time delay Setting
I found your post ref to Tap and Hold delays. I tried this Tap and Hold setting you said worked on your phone (see below) I tried it as shown below on a HTC wm 6.5 HTC pure(diamond2), and did not see a change, were you able to shorten the delay? Is that done with a String? or Dword?
3. tap and hold time:
HKCU\ControlPanel\Desktop\MenuShowDelay
right-click, select properties, and enter a value from zero to 999 milliseconds
if that value, does not exist, create it (string value).
I have spent hours searching the registry for a solution
it was a dword iirc... tbh, this hasn't been so much of an issue for me with the newer releases so i haven't bothered so much.
koi_desi_pagal said:
first off, a big thank you for the speediness of your reply.
i tried out the other tsk files i have... but unfortunately i don't have any older ones from wm5/6, only the newer 6.5 ones. they didn't seem to make much difference in size of anything... only the actual colour/font schemes. if you have any older tsk files that you wouldn't mind uploading, that'd be much appreciated as something to try.
the softkeys aren't so much an issue - i've got wisbar to disable them (yes yes, i know wisbar is a skinning app... but i prefer a nice cascading start menu to something i need to fumble through to find stuff any day) - its more the context menus that are annoying me.
the registry edit is interesting. changing the height and width actually also changes the zoom on the font size... i'm not sure how this is being calculated, but the font is clearly getting smaller the smaller you set the dimensions. it seems like its taking a predefined box with the text designed to take up a predefined percentage of it and then letting you put in the dimensions of the box... basically so that no matter what numbers you plug in, you'll always have the rather annoying amount of space being wasted between items in the context menus. though all that said and done, 750 for height and 350 for width are far more workable than the previous settings. more than legible too imo~
the tap and hold time tweak worked wonderfully
thanks again~
Click to expand...
Click to collapse
If you still need themes for wm6.1, try http://www.wm6themes.com/
I use one from that site on my BA, but since i don't have wm6.5 installed right now, i can't tell you whether it'll help in your situation or not.
I was just viewing various system registry... and came across some keys that I've never before noticed in the past.
They really aren't too outlandish, but I'm wondering if folks are interested in "testing" what exactly these registry edits "do" in terms of whether or NOT they are enhancements or NOT much of anything.
DO NOT ATTEMPT TO MAKE ALTERATIONS TO THE SYSTEM REGISTRY IF YOU ARE NOT FAMILIAR WITH ADVANCED WINDOWS MOBILE CAPABILITIES!
Now, having said all of that... here are a few of those interesting "tweaks" I've come across:
1.) HKEY_CURRENT_USER\ControlPanel\Keybd: WM7KeybdLayout - "0"
By default this registry value is ZERO... perhaps if "enabled" by using "1" as the replacement value, something "cool" may happen.
2.) HKEY_CURRENT_USER\ControlPanel\Gestures\Touch: Disabled - "0"
By default this registry value is ZERO... and I'm not entirely sure what this COULD allow your system to do, but it may be "cool" also.
3.) HKEY_CURRENT_USER\Performance: Available RAM on boot - "327274496"
By default this registry value is LIST ABOVE, and perhaps editing this value, and making it larger could allow for a more "hasty" booting process.
4.) HKEY_CURRENT_USER\Software\HTC\WebSnapShot: Enabled - "0"
By default this registry value is ZERO... but I'm wondering if this will allow for some kind of built-in screen shot function to "snap" thumbnail images of your online browsing history. Assumed value to "enable" it, should be "1".
5.) HKEY_CURRENT_USER\Software\Microsoft\Shell: AnalogClock - "0"
By default this registry value is ZERO... so I figure changing this value to "1" might "create" some kind of analog clock on for Manila.
6.) HKEY_CURRENT_USER\Software\Microsoft\Shell: HasKeyboard - "0"
By default this registry value is ZERO... and to be quite honest, this seems pretty obvious that it will "allow" or display the keyboard somewhere on the "shell" of your device. Assumed value to "enable" it, should be "1".
7.) HKEY_CURRENT_USER\ControlPanel\BackLight
This ENTIRE key has some pretty interesting settings that can be adjusted for advanced or unseen backlight settings.
8.) HKEY_CURRENT_USER\ControlPanel\AllLEDMgr
Here is the key in which you can adjust the LED settings such as interval.
9.) HKEY_LOCAL_MACHINE\Audio\SoftwareMixer: SampleRate - "268435456"
The default value is listed above, but my query involves whether or not tampering with this could resolve the "audio delay" for some users.
10.) HKEY_LOCAL_MACHINE\ControlPanel\Power
Here is the key in which you can adjust the values to be labeled for battery power settings. HIGH, MEDIUM, and LOW. The percentage before the system provides a warning can be changed.
11.) HKEY_LOCAL_MACHINE\Drivers\Display
Here is the key in which you will find a majority of your advanced display settings for your device.
12.) HKEY_LOCAL_MACHINE\Software\Qualcomm\DSM
Here is the key in which I believe you might find another possible solution for the audio delay, considering one of the string values is "250" as a file queue setting.
13.) HKEY_LOCAL_MACHINE\Software\OEM\USBtoPC
Here is the key in which you'll find the way to REMOVE or otherwise disable the "popup" window that appears whenever you connect your device via USB to a desktop PC.
14.) HKEY_LOCAL_MACHINE\Software\OEM\MASD
THIS KEY, THIS KEY RIGHT HERE FOLKS... this is VERY important for those of you who are trying to figure out what "official" version number of specific services is currently installed on your device.
15.) HKEY_LOCAL_MACHINE\Software\Microsoft\ActiveSync\OEM Links\T-Mobile Help - "0"
Enabling this key by changing the value to "1" should provide for a direct system link to the T-Mobile support network for the HD2. This is very similar to the Microsoft error reporting services.
16.) HKEY_LOCAL_MACHINE\Software\Microsoft\Calendar: ShowLunarCalendar - "0"
By enabling this, you should be able to have the Lunar Calendar displayed within the HTC system calendar... among other things. Assumed value to "activate" this should be "1".
17.) HKEY_LOCAL_MACHINE\Software\Microsoft\CHome
Here is where you'll find a laundry list of options to make changes to the original WM6.5, "Titanium".
18.) HKEY_LOCAL_MACHINE\Software\Microsoft\Pictures\ImageSendSize
Here is where you'll find 3 sub-keys that contain resolution values that can be altered in order to provide a "bigger picture" for MMS or uploads.
19.) HKEY_LOCAL_MACHINE\Software\HTC\Camera\Image
This key will open up a list of options that will allow you to change various settings for image capture and resizing.
20.) HKEY_LOCAL_MACHINE\Software\HTC\PhoneCanvas
In this key you'll find options that will allow you to make changes to the picture size for contacts.
21.) HKEY_LOCAL_MACHINE\Software\HTC\PHONE
Here are more device settings for in-call and beyond.
ENJOY!
Oh, and don't hesitate to leave a bit of feedback. Thanks.
I am patiently waiting for you to try these and update the post.
I sure as heck don't plan to "play" with my registry
As soon as the store calls to tell me that mine is *FINALLY* in, I'll be happy to test some of those out. As long as you back up your registry before you do anything (and aren't afraid of a Hard Reset as a last resort), there shouldn't be any issue trying these...any of the changes you make can be reversed that way.
Snarksneeze said:
I am patiently waiting for you to try these and update the post.
I sure as heck don't plan to "play" with my registry
Click to expand...
Click to collapse
sirphunkee said:
As soon as the store calls to tell me that mine is *FINALLY* in, I'll be happy to test some of those out. As long as you back up your registry before you do anything (and aren't afraid of a Hard Reset as a last resort), there shouldn't be any issue trying these...any of the changes you make can be reversed that way.
Click to expand...
Click to collapse
Agreed fellas. This stuff seems interesting. I haven't played with these listed items just yet. I was so exhausted last night while skimming through tons and tons of registry keys... that I may have gotten a little desperate to post this rather than test each one.
Some are just useful tips, but others I have not before seen on the EURO model of the HD2. For instance, the WM7 keyboard... that's rather curious, huh?
5 - puts tiny analog clock where digi clock is by battery
6 - for phones with hardware keyboards
14 - can change that to fake any system info you like
18 - doesnt necessarily work. best way ive yet to find to fix the small mms size on some networks is the mms userprofile tweak that reports it as a diamond, and the mms useragent as a nokian95. (I can tfind the link, sorry)
3.) HKEY_CURRENT_USER\Performance: Available RAM on boot - "327274496"
By default this registry value is LIST ABOVE, and perhaps editing this value, and making it larger could allow for a more "hasty" booting process.
When I looked I had a lower value, "281640960". I increased it to "327274496" startup seems a bit faster, not much. I'm gonna try increasing it later. On another note, slide to unlock seems to be faster. Of course this could all be in my head.
chrys9989 said:
3.) HKEY_CURRENT_USER\Performance: Available RAM on boot - "327274496"
By default this registry value is LIST ABOVE, and perhaps editing this value, and making it larger could allow for a more "hasty" booting process.
When I looked I had a lower value, "281640960". I increased it to "327274496" startup seems a bit faster, not much. I'm gonna try increasing it later. On another note, slide to unlock seems to be faster. Of course this could all be in my head.
Click to expand...
Click to collapse
This looks suspiciously like overclocking to me. If it is, I doubt that the S2U being faster is in your head...
Are you sure that "on boot" only means during the bootup process and not the original RAM available before the processes kick in?
Snarksneeze said:
This looks suspiciously like overclocking to me. If it is, I doubt that the S2U being faster is in your head...
Are you sure that "on boot" only means during the bootup process and not the original RAM available before the processes kick in?
Click to expand...
Click to collapse
What's weird though is that the value keeps changing, on every boot it's a different value. On the last boot, it was 280760320.
chrys9989 said:
What's weird though is that the value keeps changing, on every boot it's a different value. On the last boot, it was 280760320.
Click to expand...
Click to collapse
Then it just about has to be a record and not reference value. Shoulda known it wouldn't be that easy
samsamuel said:
5 - puts tiny analog clock where digi clock is by battery
6 - for phones with hardware keyboards
14 - can change that to fake any system info you like
18 - doesnt necessarily work. best way ive yet to find to fix the small mms size on some networks is the mms userprofile tweak that reports it as a diamond, and the mms useragent as a nokian95. (I can tfind the link, sorry)
Click to expand...
Click to collapse
chrys9989 said:
What's weird though is that the value keeps changing, on every boot it's a different value. On the last boot, it was 280760320.
Click to expand...
Click to collapse
Thanks for the reports.
And yeah, I noticed that as well... yet my value is always relatively in the same demographic in terms of "high" or "low".
But yes, it is some "lowbrow" version of overclocking, but as far as I know... it only pertains to the RAM available during and shortly thereafter a booting process is complete. It's like tweaking the allocated resources that "HTC Sense" used each time it booted up.
Awesome find. looking forward to what will be unconvered
I have a few friends skimming the registry keys day n' night as well... it's just very, very exhausting to read thousands of lines of coding.
I doubt I'll be updating the OP with tons of additions, but I'll certainly add to it, should something reasonably decent come to my attention.
I would like to add something that also seems interesting
HKLM/System/Autoupdate: 0 <-- I wonder what 1 does.. I just set to 1, will update as i hopefully receive updates
PS: I'm not sure if its this that caused this, but my phone just locks on slide to unlock.. As soon as i try unlocking the screen turns off.
Reignzone said:
I have a few friends skimming the registry keys day n' night as well... it's just very, very exhausting to read thousands of lines of coding.
I doubt I'll be updating the OP with tons of additions, but I'll certainly add to it, should something reasonably decent come to my attention.
Click to expand...
Click to collapse
Bump.
Anyone found any interesting tidbits as of yet?
Is it possible? I've pulled build.prop like 3 times pushed back after changing it to 200 and it does not save after a reboot. Am I doing something wrong?
i supose, you need to change the DPI, of the rom.
but not sure.
I just tried it to this build ->[mccm SE v2.0/2.5 (09.10.2010)] what I did is copied the build.prop from a different build and edited the lcd density to 200 and then I added this to the startup text ->"rel_path=Android lcd_res=200 gps_zone=us" and it worked although it does look like when I did that it doesn't actually set it to 200 but rather 180 a little experimenting with it and you should be able to get it right.
I have better keyboard pro but I am running hyperdroid which has the density set at 167, making the keyboard smaller.
Is there any way that I can make the better keyboard bigger?
Im not sure, as i havent tried that rom, but if you have spare parts installed, try turning off compatibility mode, reboot and see if it works. or you can always edit your build.prop lcd density.
snyper2k2 said:
I have better keyboard pro but I am running hyperdroid which has the density set at 167, making the keyboard smaller.
Is there any way that I can make the better keyboard bigger?
Click to expand...
Click to collapse
There's an app in the market called LCD density changer, you could try that..
I would personally like to know this too. I would like to have low density with a normal size keyboard. I have tried turning off compatibility mode.
ive done a little testing myself now, running hyperdroid and same key board. i couldnt get it to work right til i un-installed it after turning compat mode off and restarting. so maybe it will work for you this way,,, un-install it, turn compat mode off and resart, best to turn off phone then back on really. after re-start, re-install and see if it is full screen. good luck!
Same issue here. Interesting problem -- the HyperDroid rom with CM7 on my HD2 *came* with a 167 density setting (tiny fonts) but a large keyboard (sized as if density were 240). I wanted to change the size a bit and set the density to 200, and then the keyboard got *smaller*. Now they are correlated and I can't get back to the way it was originally. Love to hear if anyone has this figured out. There must be a separate setting somewhere for the keyboard size.
How to adjust your DPI without root, I believe the current DPI is around 300 I could be wrong.
To adjust the DPI follow the steps below, THIS DOES NOT REQUIRE ROOT.
Open settings and scroll all the way down to About
Open Software Information
Tap the build number quickly a couple times till it says "You're now a developer"
Head back into the main settings page and open the new Developer Options
Enable USB debugging
Install ADB on your computer (there are plenty of tutorials out there if you don't know how)
Start ADB and check if you see your device by typing
Code:
adb devices
If you see your phone go ahead and type
Code:
adb shell wm density 250
Reboot your phone to apply the effects system wide.
250 is the DPI set which I think looks the best for me. Adjust how you like it
NOTE: IT WILL LOOK WEIRD AT FIRST, REBOOT YOUR PHONE!
This is a great method. Use it often. Couple more commands:
Code:
adb shell wm density reset (set to default)
adb shell wm size 1080x1920 (emulate whatever resolution)
adb shell wm size reset (set to default)
What Screen Resolution have you chosen?
Chinaphonearena said:
This is a great method. Use it often. Couple more commands:
Code:
adm shell wm density reset (set to default)
adm shell wm size 1080x1920 (emulate whatever resolution)
adm shell wm size reset (set to default)
Click to expand...
Click to collapse
I noticed in the pics from your review consisted of smaller icons. I am assuming you changed the DPI to 250. I would like to know if you have tinkered with your screen resolution as well. If yes can you show us some screenshots? Does that have any other benefits like battery performance and processing speed?
sanjeevopeth said:
I noticed in the pics from your review consisted of smaller icons. I am assuming you changed the DPI to 250. I would like to know if you have tinkered with your screen resolution as well. If yes can you show us some screenshots? Does that have any other benefits like battery performance and processing speed?
Click to expand...
Click to collapse
Yes, you're correct the dpi was changed. There's no performance gain I see. I do this so I can fit more on the screen at once within apps, while browsing etc... For me this is half the value of an HD device - you can shrink stuff down to fit 2x as much, but tiny text still remains comfortably legible.
This can also be done within terminal emulator. For me, not successful unless entering su.
nice way to adjust animations on your phone..its now fast without the animation by the way i need help i accidentally touch the Logger Buffer Sizes....its under settings..developer options...scroll down you will see. logger buffer sizes...now there are number to choose from..64k..256k...1m...4m...16m.... now would like to ask if what is your default value in your phone"? want to do default...whats the diffence it do when you change those settings 64...256...etc....tnx
pato2015 said:
nice way to adjust animations on your phone..its now fast without the animation by the way i need help i accidentally touch the Logger Buffer Sizes....its under settings..developer options...scroll down you will see. logger buffer sizes...now there are number to choose from..64k..256k...1m...4m...16m.... now would like to ask if what is your default value in your phone"? want to do default...whats the diffence it do when you change those settings 64...256...etc....tnx
Click to expand...
Click to collapse
Mine is 256k. That should be how much data is held in the logs.
thanks...got it...it just goes to default by itself when closing developer option......
This is pretty cool, is there an adb command to readout the density what ever it's currently set at?
I ended up at 390, it gives a nice 5x5 grid.
Thanx, work fine! A little notice: Asus Powermanagment end in force closed when you change the DPI. Went back to orig. 480 and it works, when you need it
And next big issue Swift key doenst work with changed DPI. When changed i saw only a few very!! big letters. Keyboard not useable.
Thanks OP!
The issue with swiftkey is well known and documented, just search Google for it (XDA says I don't have enough posts to post links yet). It looks like there's a fix, but it requires root. I switch to the Google keyboard and it works fine with modified DPI.
FYI, density setting of 460 is the lowest (stock is 480) that will keep the widget width taking up the whole screen for wide widgets. Makes everything a little sharper than stock, which was needed.
The hardware keys below the screen also stop working when the screen resolution is changed.
tasar said:
Thanx, work fine! A little notice: Asus Powermanagment end in force closed when you change the DPI. Went back to orig. 480 and it works, when you need it
And next big issue Swift key doenst work with changed DPI. When changed i saw only a few very!! big letters. Keyboard not useable.
Click to expand...
Click to collapse
ZenMotion touch gestures config also crashes.
As for swiftkey, you could probably use xposed appsettings to adjust its dpi/dp settings.
ziddey said:
As for swiftkey, you could probably use xposed appsettings to adjust its dpi/dp settings.
Click to expand...
Click to collapse
I have test it with AppSettings at first but no luck or i do something wrong. I have set DPI to 480 all other at default but same as before.
tasar said:
I have test it with AppSettings at first but no luck or i do something wrong. I have set DPI to 480 all other at default but same as before.
Click to expand...
Click to collapse
Try a different DPI. 480 is extreme and some apps simply won't work properly at such a high setting.
After doing this, how to revert to the original one???
dineshdotcom2000 said:
After doing this, how to revert to the original one???
Click to expand...
Click to collapse
adb shell wm density reset
Chinaphonearena said:
Try a different DPI. 480 is extreme and some apps simply won't work properly at such a high setting.
Click to expand...
Click to collapse
480 is original dpi
tasar said:
480 is original dpi
Click to expand...
Click to collapse
Tasar, I stand corrected. 480 it is.
Application settigs
Anyone having problems with some applications after using this mod? I am having issues with viber(photos sent wont open properly- always zoomed in and i cannot see the entire photo and no option to be zoomed out) and instagram as well. Hope anyone can help me with this. Thanks
Photo Studio pro the same problem, see only a quarter of the pic, cant zoom it to full. App settings doenst help