I need someone that hasn't flashed with a STOCK T-Mobile ROM to post the values from the following reg entries:
HKLM\Software\OEM\TFLOSettings\FingerPressure=?
KHLM\Drivers\TouchPanel\PressureThreshold=?
I have used HD2Tweak and set mine on maximum, which has helped very little if any. The values I currently have are:
FingerPressure=DWORD:7530
PressureThreshold=DWORD:5182
I don't know if these are the only settings that affect screen sensitivity, but those are the only settings that I see anybody making changes to.
Everything else about the new ROM I love. I really do hope this is just a test ROM and a newer "official" ROM will come next week.
Thanks!
Ok, well I don't know how much this will end up helping, but I looked them both up on my original stock Tmo ROM.
For the first one, there was no "finger pressure" entry under TFLOSettings (first screenshot below).
For the second one, there wasn't even a "TouchPanel" key under drivers (2nd screenshot). There was a "display" key, but no values under there that looked at all like what you're looking for.
Now, having said all that, I'm kinda suprised that any pressure-related settings
a) showed up in the new ROM, and
b) would have any bearing on the response of the capacitive screen on the HD2...I was under the impression that these types of displays don't/can't register pressure at all, only the electrical disruption caused by your skin.
oops, never mind
Related
Alright Peeps, ok, firstly i bought a Charmer (MDA Compact 2 / WM5) it was pink and i decided to change the housing/shell. I opted for the O2 XDA NEO Case as i liked the black, smooth sides, chrome earpiece & Buttons. I know your all thinking why, but i've tried it and every part fits perfectly apart from the button arrangement, I was just wondering if i bought a O2 XDA NEO Keypad which has the exact same connection type as the MDA Compact 2 just the extra 2 buttons, could this work out of the box and recognise all buttons or at least the usual 4 buttons work correctly?, or is there, or could one be made, an application that the buttons could be assigned? please any help would be appreciated, as i love modding my charmer from the wise information within XDA-DEV, your the only site i'd look to for honest answers.
Cheers Bren.
just an opinion, don't go spending money because of it
but from my experience doing similar things with htc smartphones, I reckon it should work, but i doubt it will recognise the extra buttons...
maybe with a cooked ROM?...i don't know.
triplejay said:
just an opinion, don't go spending money because of it
but from my experience doing similar things with htc smartphones, I reckon it should work, but i doubt it will recognise the extra buttons...
maybe with a cooked ROM?...i don't know.
Click to expand...
Click to collapse
could there not be some registry tweaks? like adding the buttons manually and moving the others?
i have a button remapping software, but this may be more useless than usefull, i think (it'll probably just move the buttons around) i've bought the shell already and fitted it all buttons work and are in correct place, just the keypad... I'll buy the keypad and fit it coming up to christmas, i'll let you all know the outcome, so if there is any charmers that wish to charm with a prophet/XDA NEO case to the full, i will have the answer.
Any ROM Chefs or Registry Raiders? Help would be appreciated here...
or just shine a little light on the subject.
I think the person who might be able to shed some light is vlodeck, he is a very knowledgeable guy, and he ported gullum's ROM from prophet to charmer
http://forum.xda-developers.com/showpost.php?p=1446686&postcount=1
as a mod, he will probably see this thread anyway, and his time is valuable etc etc, so I am definitely not advocating pestering him
....so wait a while but in case it gets missed, FYI in his sig there is a link to PM "if you need help"
*edit, I have no new information right now so I'm not gonna bump this thread but I have to say...
just saw your other thread, and the one word answer;
rtfwplsthx
made me spit coffee all over my monitor as I LOL'd
(translation - read the f***ing wiki please, thanks.)
I understood it, as I've probably spent too much time reading forums like this one recently
Hi guys
I finally read this thread Yes, I do check up the Charmer forums from time to time.
Ok, as to the question. I don't really do the cooking stuff at this time. Basically because I'm not a windows user anymore but there are registry values for soft keys and buttons. I won't tell you were it exactly is right now, but it's there. And taking myself a little in the past I recall some major problems with setting up the keys in WM6 for charmer, you remember it right? Those calendar and contacts buttons were assigned to Start Menu and OK keys, which were unconfigurable, in the registry at least. So my call is, those buttons you want to make work are hardly worth the potential time spent to actually get them working
Hi, the buttons you had trouble with kinda goes with what i want, like you said the bottom two buttons (calendar/contacts) were start menu and ok, as the keypad for the o2 xda neo has start menu and ok as standard bottom two, so that doesn't need changing (that sound like a bonus to me ) the top two will probably get recognised as the answer/endcall buttons (which is not that bad come to think of it, if buttons cannot be configured). its just the two silver answer/endcall present on the xda neo keyboard which probably wont get recognised, and if not, would there be a way in the registry to ADD them, so it would be a little different than altering settings already there? sort of copying all registry settings for one button and adding it alongside another button setting with some configuration.
Thanks Guys...
Well the Buttons worked straight away, charmer to prophet (lookalike)... all the 6 buttons were recognized instead of 4, and all in the right places. thanks anyway.
Right, I've had the HD2 (well two of them now actually) for over three weeks so this isn't just a case of my 'not being used to the device yet'. I'm very used to it, so, moving swiftly along...
When typing on the super-sensitive keyboard, you know the one, where nearly every word needs editing due to errors......when I hit the delete button, all sorts of anomolies regularly occur. Typing is a real chore on this device. I get all sorts of characters appearing when I press delete, it is a real lottery and takes several attempts to actually delete anything. I have experienced this problem on both HD2s I've had, so this is definintely not a faulty unit. I am assuming that they're all like this?
Have you try with bsb tweaks and option decrease sensitivity of screen?
Your not alone pal - i install a cab - from this post http://forum.xda-developers.com/showthread.php?t=604831
and it seemed to have help some
Its version 3
unque1 said:
Your not alone pal - i install a cab - from this post http://forum.xda-developers.com/showthread.php?t=604831
and it seemed to have help some
Its version 3
Click to expand...
Click to collapse
I installed the first version of that cab on my previous HD2 and found that sometimes buttons would not register and the whole screen would freeze momentarily etc. Also, the clincher, was that the screen was less sensitive in all apps, not just the SMS one. For instance, when sliding to unlock the handset it would take several attempts etc, this I could not live with. Is v3 any different?
Hi - if you read the link its not to do with removing the sensitivity as i didnt want that either it do do with alignment - I really cant explain it better then the dude himself. but if you holla at him im sure he will give you a better understanding of whats changed
I love this phone but this crashing its doing my head in. Ive heard so many people have this issue but no ones knows how to fix it. What happens is...
You recieve a txt you press the on button you swipe the unlock and it just sits there doing nothing. You have to pull the battery out and its a tad annoying when you have to take the case off to get to the battery cover.
I think its the HTC sense causing this as ive taken it off and im using spb mobile shell 3.5 and its working ok
Any help would be very grateful.
Cheers
Baker0
Can't say fixed completely, but it's much better after performance tweak
I can't say that my TMOUSA HD2 never crashes anymore, but I get much better performance with very few crashes after implementing the following registry tweak which comes from the 3rd sticky link on the HD2 General page. Also, even with the tweak, SMS performance is not fluid:
*Leo Hints, Tips and Registry....
37. Boost Performance:
Navigate to: HKEY_LOCAL_MACHINE\System\StorageManager\FATFS
Change - CacheSize to 4096. Works for some and not for others though.
I have not flashed my ROM and do not plan to do so for some time because I don't want to get off of the stock ROM until I see a few more bugs worked out.
Please let me know if this registry change improves the crashing behavior because I might increase the CacheSize another 1 MB to see if the performance improves.
HTH
PS: I meant to also mention that my phone was doing the exact same thing as yours. I went back to TMO and they said it should probably be replaced but they didn't have any in stock and they didn't know when they were getting anymore in. After reviewing many of the posts from new purchasers (including yours), I think the new phone will have the same problem and the only way to fix it will be for the MFG to post a hotfix. So rather than losing the few apps and customizations I have already made, I'll just struggle along until a hotfix comes out.
So, I did some tooling around and found that the battery is veritably the same in terms of efficiency from TMO ROM 2.10 to 2.13 save for one thing...it drains like a mother when using my wifi network.
I went through most of the day with normal use, a few less phone calls as I was in meetings, but more uploads to Facebook as I was at one of my kid's functions and snapping shots and trying to upload on nary a bar and I still had 20% left at the end of the evening.
The major difference was that I hardly tuned into my wifi network at all.
I seem to recall a registry tweak that enabled use of an "N" network very effectively that I employed first go around. I am not even sure that I found it on this forum, but I would be much obliged if someone could turn me on to it again.
I believe that, at default, the HD2 is not set to run "N" speeds though again...that might be rumor. I do know that I tweaked the registry within the first week to address this though and cannot remember what I did!
It's in BSB Tweaks, right at the bottom...
The cab below might be the one you're remembering.
It's from the following list of tweaks, etc (which is in the sticky at the top of this forum section): http://forum.xda-developers.com/showthread.php?t=584415
don't you have to have a n enabled router to utilize?
I appreciate the posts, but I found one of the lines that I needed to change (I prefer to do things manually) and it is denying me access!:
HKLM/Comm/BCMSDDHD1/PARMS
11nModeDisable Change the Value from 1 to 0
It won't let me change the value with this ROM.
It is telling me that it won't let me access this!
What the hell?
No one knows why this string would be protected now or how to unprotect it?
hi all,
Sorry for my bad english...
During scroll or when i play in game or when i watch a video, i have the "breaks" of crappy, this is very very irritating for me ! I don't understand why everyone ignores this.
The only thing I find on the web is this: forum.xda-developers.com/showthread.php?t=500499
After search in keys reg, i found this:
Code:
[HKEY_LOCAL_MACHINE\\Drivers\Display\Settings\ILCDC]
"VisibleDisplayHeight"=dword:000001E0
"VisibleDisplayWidth"=dword:00000320
"DataEnInvertSignal"=dword:00000000
"VsyncInvertSignal"=dword:00000000
"HsyncInvertSignal"=dword:00000000
"VsyncFrontPorchLns"=dword:0000001B
"VsyncBackPorchLns"=dword:00000014
"VsyncPulseWidthLns"=dword:00000002
"HsyncSkewDclk"=dword:00000000
"HsyncFrontPorchDclk"=dword:00000051
"HsyncBackPorchDclk"=dword:00000051
"HsyncPulseWidthDclk"=dword:0000003C
"ID"="4.3in WVGA Optrex"
[HKEY_LOCAL_MACHINE\\Drivers\Display\Settings\ILCDCgordon]
"VisibleDisplayHeight"=dword:00000280
"VisibleDisplayWidth"=dword:000001E0
"DataEnInvertSignal"=dword:00000000
"VsyncInvertSignal"=dword:00000000
"HsyncInvertSignal"=dword:00000000
"VsyncFrontPorchLns"=dword:00000002
"VsyncBackPorchLns"=dword:00000002
"VsyncPulseWidthLns"=dword:00000002
"HsyncSkewDclk"=dword:00000000
"HsyncFrontPorchDclk"=dword:00000021
"HsyncBackPorchDclk"=dword:00000090
"HsyncPulseWidthDclk"=dword:0000003C
"ID"="VGA Sharp Gordon"
You know exactely where i can activate the vsync ?
Thx
Well, no answers ...
Yet you are all concerned! This didn't embarrasses you not?
To illustrate the problem, see:
- en.wikipedia.org/wiki/Screen_tearing
- youtube.com/watch?v=O8_fbUfVRZg
- youtube.com/watch?v=L0ZhDGTVm4M
lo said:
Well, no answers ...
Yet you are all concerned! This didn't embarrasses you not?
To illustrate the problem, see:
- en.wikipedia.org/wiki/Screen_tearing
- youtube.com/watch?v=O8_fbUfVRZg
- youtube.com/watch?v=L0ZhDGTVm4M
Click to expand...
Click to collapse
I saw this too,but it happens only when I slide open the phone in some apps.
I have same problem in my x2,and can't find any way to solve it ,I search vsync in registry,change 0 to 1,but it also ''screen tearing''
ps,x1 seem not has this problem...
What can we do to solve this?
Sorry to my bad english.
Warning: I have placed only the non-HTC tweaks here and HAVE NOT TESTED THEM YET. Any changes you apply or programs you use will be at your own risk!
I would have tested this already if I could but I will only be able to after a few days when I get my new X2 (again). I just wanted to give possible solutions besides turning on Vsync.
-------------------------------------------------------------------------------
Activating VSync only will not solve your problem because screen tearing is usually caused by a combination of bad video and file access configuration.
To answer your request here is what I found for the VSync registry location (please confirm this):
[HKEY_LOCAL_MACHINE\Drivers\Display\LCDC]
"Vsync"=dword:1
And here is a list of possible tweaks for the X2:
Original post by g.lewarne is: forum.xda-developers.com/showthread.php?t=629388.
Change:
HKLM/System/GDI/GLYPHCACHE To: 524288 (change both keys in there)
This allows for much smoother font rendering, especially when scrolling
Change:
HKLM/System/StorageManager/Filters/fsreplxfilt/ReplStoreCacheSize To: 131072
This creates a filesystem 128k sector cache filter, improves data throughput from ROM to RAM (probably) and does seem to improve indexing response and file browsing.
EDIT: file explorer just loaded my “Windows” directory in half a second with this enabled , and the screen does not tear when scrolling the list either any more
Change:
HKLM/Drivers/Display/VMMaxHeapSize To: 33554432
This changes the VideoMemory max heap from 16k to 32k
Change:
HKLM/Drivers/Display/Settings/SMI2 AllocSizeMB To: 32
Change:
HKLM/System/GDI/Drivers/Bpp To: 24
Now this IS interesting. I dont know if its just me, but were HTC holding out on us display wise? Changing the BitsPerPixel (colourdepth) from 16 to 24bit, for some reason, whether the display is actually capable of true colour or not, not only MAKES THE SCREEN LOOK BETTER but its also FASTER
Click to expand...
Click to collapse
Finally a tool for boosting graphics:
forum.xda-developers.com/showthread.php?t=509704
Can somebody test the above a provide a feedback thru all the points Xareth suggested us?
I'm not able to do this my X2 is not available for a a month or so.
Who is coming up with these crappy settings? Most of them are NONEXISTENT in my X2!!! And many of the rest are already much higher!
This is not a HTC phone and has no such hardware and NOT most of those HTC specific windows registry settings a HTC phone has.
Please post only registry settings and changes of such, which are existing in the X2.
Thank you!
I agree.
I think all that Xareth says, comes from the HD2... But I tried to add the non-existent keys => nothing !
And i have already tried GfxBoost, NeoS2007 and SpeedBooster, this hasn't solved the problem.
I think that without hardspl, nobody knows anything do
What happens when you try to help and warn in CAPITALS that you have not tested it.
Thank you all for your replies to my post above.
First of all, really sorry to have disappeared but I have entered a new job and have been busy as heck to reach a stable setup.
Even though the testing of the reg keys failed, I am happy that it at least has gotten us closer to finding a solution since we found out they did not work
What next? Well, what else! Gotta try to find other ways. This time I can test since I have my X2 and am using it regularly.
@lo: don't give up, don't assume it's the end! I am now checking if it has to do with the SD card access (delayed reading).
@michaelthemage: I know you are frustrated and want a working answer at once, but:
1. this is a community forum not a support centre so don't assume I or anyone else is making up any crappy settings. We're just trying to find the right answers.
2. and yes, I can make mistakes just like you or anyone else. For example you did not read my first line saying I did not test the settings since I did not have a device to test with! Demanding much?
3. I don't think we can limit things to X2 only registry settings because first of all, it's not out there in the open to know which settings are only for X2! I removed the obvious HTC reg keys and went on from there. I think that is the next best thing to finding an answer, instead of hitting a dead end. I ask you to also try to find an answer or at least post something more constructive.
4. Sony previously worked with HTC (HTC was making the components for previous Sony devices) and therefore it is logical there may be some HTC keys which are applicable. I will tell you right now many fixes that work for HTC work for the X2! Have you ever wondered why? Of course I may be wrong too but I'm trying to find out if I am!
5. Let's go on to hardware. Many smartphone manufacturers are only integrators. Even HTC buys its parts from another company in China. So don't tell me it does not have similar hardware to HTC until you have opened both companys' phones and confirmed (which I have btw, the opening not the confirming). It's like saying LG Laptops do not have LCD screens like Samsung Laptops when Samsung manufactures the LCDs for LG.
Get a life!
Dude, I don't have the time nor inclination to answer this crap in several paragraphs. Still these reg settings are crap and somebody posting this crap is responsible if any noob applies them and screws up their phones. That is the crap! That's it!