Related
I figure that as long as bugs are being ironed out, this one is worth a try.
As most people have noticed, Rogers networks seem to have SMS timestamping issues that have to do with the network and phone itself. These issues seem to be fixed by replacing the stock Rogers Mms.apk with the stock Google one (since this is what I think HotWeiss did with the HoFo community rom with some help from Nk02). I myself have noticed that the majority of ported Dream roms (such as Cyanogen's mods) also have this issue fixed with no additional tweaking. This leads to two important questions:
1) What makes the two Mms.apk different enough that one suffers from the timestamp issue and the other doesn't? Is is something that can be simply fixed by swapping a few files and resigning, or is it buried deeper in the code?
2) If it is as simple as swapping some files, can we use this knowledge to fix the 4 hour discrepancy that exists in the Hero ports? It seems to be one of the main bugs keeping people from using it.
I myself have been looking into various ways to fix it and have been coming up emptyhanded. Maybe we can use this space to bounce ideas and collaborate to come up with a solution. Please do not use this thread to complain about the timestamp issue. If you have a rom specific problem, post it in that thread. Try to use this space for coming up with ideas on the timestamp issue.
As usual, thanks for all the hard work, and hopefully we can find a solution!
I would really apreciate and suport this issue resolved.
I have a 32b from Vodafone Spain and using portuguese Vodafone but all the sms received are 1h behind.
It's the only thing stoping me from using a Hero rom.
I don't know if it's related, but when I turn on Location options (just wireless, not GPS) it boots my phone's system time back a couple of hours.
Although even when I do that, SMSes still come in stamped with GMT time, so instead of being 4 hours behind, they're six hours behind for that duration.
Is it always four hours? Or is it just GMT? Do people in Vancouver who have this problem have timestamps seven hours behind?
[Edit: System time is okay with location services on now. I'll keep an eye on it. Maybe it's related to the time glitches people were having on Rogers yesterday.]
[Edit the second: Nope. At lunch my time got thrown back by two hours. Fixed itself when I turned off wireless location again.]
I second that too.
I am staying away from all the Hero ROMs because of this issue as well. The only rom that works with no notible bugs is the HoFo ROM, but that's just not HERO. Sure, it's possible to push camera.apk to the Hero ROM, but it's not possible to do the same with the mms.apk file. All that really needs be done is compare the fixed mms.apk file with the Hero one, and find out where it was fixed.
Alright, I did some digging and found a few things. I dunno if this info is useful at all but at least it's a start.
After rooting around in the Android Developers guide, I found there was reference to getTimestampMillis in being used to return the service center timestamp. After dedexing the Hero Mms.odex (no classes.dex in the apk), I could not find any reference to the getTimestampMillis line, but instead found reference to a mTimeStamp in com/android/mms/dom/events/EventImpl.ddx. It also looked like there were references to the local time:
Code:
invoke-static {},java/lang/System/currentTimeMillis ; currentTimeMillis()J
and a reference to another timestamp related thing:
Code:
.method public getTimeStamp()J
.line 67
iget-wide-quick v0,v2,[obj+0x18]
return-wide v0
.end method
So that seems to be what I've found. I'm not saying it means anything, since I know squat about coding in Java, but at least its a start.
This isn't a fix but at least my texts aren't 4 hrs behind anymore. The clock widget shows my city and the current time with the texts stamped correctly.
http://forum.xda-developers.com/showthread.php?t=549291
hope it helps
Well, I dunno if anyone cares anymore, but here is a new update for Rogers Magics direct from HTC that supposedly addresses the original timestamp bug.
http://www.htc.com/ca/SupportDownloadList.aspx?p_id=270&act=sd&cat=2
I have no idea if this does anything for Hero roms. I suppose if there is someone more technical minded, they could extrapolate the fix and apply it to further roms.
Hmm
I have a HTC from Orange (PL) with a hero ROM and me and my half we trade sms's in almost in *realtime.. I'll test right a way again from the Orange website!
If something is going up, I never noticed!!
yes a fix would be nice for us canadians... i use the method origins81 uses but a real fix would be great
Seems to be a ROM update for Rogers on the HTC site. One fix is the timestamp issue.
http://www.htc.com/ca/SupportDownloadList.aspx?p_id=270&act=sd&cat=2
Could this ROM be examined for a fix?
Can anyone put up an alternate link elsewhere, rapidshare or megaupload? I keep getting "Sorry, this software download is not suitable for your device"
Thanks
*No need, you can pick it up from the Rogers website*
So I'm going to ask a dumb question, but does the published HTC source give any insight into fixing the timestamp issues? It's still pretty much the only annoying bug.
So I've been noticing that after a certain amount of use my Hero eventually slows down to the point where typing on the keyboard is frustrating because of the slow response. I did some searching and I came across this online
http://code.google.com/p/android/issues/detail?id=3453
since I'm no where near the level of a dev, I figured I'd put this out there and see if anyone can make heads or tails of it, and possibly create a signed-zip so we can just use the update feature in the recovery screen to flash it to our system.
Seems legit as a fix, and apparently this was something that was a known problem with Android 1.5 that I guess has been fixed with 2.0.
Any Dev help would be hot.
Excellent. Thank you for tracking that down.
The TL;DNR explanation: Location services are causing multiple "heartbeats" on the phone all on top of each other. One guy counted as many as 253 in 5 seconds. This consumes the CPU. I will look at the patch.
Would disabling location services be a temporary fix?
kynetx said:
Would disabling location services be a temporary fix?
Click to expand...
Click to collapse
Yes. We're pretty close to 2.1 though so shouldn't need more then that.
ive seen this problem too but not until recently, it lags the phone and drains the battery amazingly fast.
abcdfv said:
Yes. We're pretty close to 2.1 though so shouldn't need more then that.
Click to expand...
Click to collapse
I'm taking a wait and see approach on the 2.1 progress right now, what's there looks very promising but without the camera, accel., & (for me anyway because I do have alot of apps that i use) a2sd, I'm content with Fresh 1.0, just wanna get help get that issue solved cuz I'm sure I'm not the only one who is experiencing it.
PS: I know I said I have alot of apps, but I know that's not the cause because the same thing happened when I did a wipe and just left things "stock" with Fresh Rom 1.0 for a few days
If they got the accel and wifi tether working, I'd make the jump to 2.1, but I need the accel for work, and the wifi tether for internet.
What app can be used to show the system_server process? I use task manager but it isn't listed. I want to monitor this process.
Also, does anyone know about the patch? How Do you apply it?
1) I can't answer the first question. I just took the advice here and turned all location services off. My phone is back to its snappy self. The only way I'm really impacted by having to do this right now (I'm sure I'll use this phone for more after 2.1) is using google maps. I already kept GPS off when I wasn't using it but having to go into the settings and allow Location Setting before using gmaps is a PITA.
2) I know very little about android and ROM DEV but think the "patch" is programming code, only useful to people who know how to read and write it.
jdlumley said:
What app can be used to show the system_server process? I use task manager but it isn't listed. I want to monitor this process.
Also, does anyone know about the patch? How Do you apply it?
Click to expand...
Click to collapse
RoboTop???
You can use DDMS from the Android SDK toolkit to monitor processes running on the phone. Should be able to pull up a process list from there.
Now, I'm using Locale but not with Location settings for my different profiles. I also have Location settings turned on for use with Google Maps as well as the HTC Flip Clock / Beautiful Widgets Home. Surprisingly, my system_server process is sitting at 0% right now, and the phone has been on for over a day. Both DDMS and running "top -n 1" in the adb shell confirm this. If there's much of a change over the day, I'll be sure to let you know. So, it's possible that HTC found and fixed this issue with their SenseUI CDMA 1.5 build. Unlikely, but possible.
So I was seeing this issue even with the modified services.jar from that thread. Granted I didn't test it very long and it was only maxing out at 1%, but it was enough for me to feel that it wasn't working.
I have since removed HTC's location service. After rebooting it looks as if because the phone couldn't find HTC's service anymore it installed the stock one. Time to see if it makes any difference.
with my BB for example there was an application which rebooted your phone at a custom time that u have set .. is there an application that can be used to do the same with the hero? ... reboot device while u are sleeping.. so it runs nice and quick for u the next day?
flipzmode said:
So I was seeing this issue even with the modified services.jar from that thread. Granted I didn't test it very long and it was only maxing out at 1%, but it was enough for me to feel that it wasn't working.
I have since removed HTC's location service. After rebooting it looks as if because the phone couldn't find HTC's service anymore it installed the stock one. Time to see if it makes any difference.
Click to expand...
Click to collapse
On the Fresh ROM thread I thought you said that it was using 16% previously... and is this an issue that's apparent immediately or is it something that gets worse with time?
Any chance of including the modified services.jar in the next release even if it doesn't immediately appear to make a difference? I mean, if it's not crashing things and is supposed to be an improvement, then why not stick it in there, right?
Just read nearly that entire chain of messages. now somebody (fresh, ima callin you out!) dooo eeeet!
What's the word on progress for this in Fresh ROM? I have found it to be a very significant issue for me (and apparently so has my roommate), as I use location services quite a lot. GMaps being most in particular, but some other apps as well (Aloqa, Sprint Navigation). I'm really glad there's a workaround that doesn't involve a reboot!
I looked at the other link and I have downloaded both the services.jar file and the LocationManagerService.patch. Which one should I apply and do I apply it? I am having problems with this now.
bcellis said:
On the Fresh ROM thread I thought you said that it was using 16% previously... and is this an issue that's apparent immediately or is it something that gets worse with time?
Any chance of including the modified services.jar in the next release even if it doesn't immediately appear to make a difference? I mean, if it's not crashing things and is supposed to be an improvement, then why not stick it in there, right?
Click to expand...
Click to collapse
The bug is that it gets worse over time. I can include it for sure. I believe the reason it's not working is because our hero's code is all stored in services.odex, not services.jar. And I haven't been able to deodex that file yet. But I'll include it regardless because it can't hurt.
scirio said:
Just read nearly that entire chain of messages. now somebody (fresh, ima callin you out!) dooo eeeet!
Click to expand...
Click to collapse
patches11 said:
What's the word on progress for this in Fresh ROM? I have found it to be a very significant issue for me (and apparently so has my roommate), as I use location services quite a lot. GMaps being most in particular, but some other apps as well (Aloqa, Sprint Navigation). I'm really glad there's a workaround that doesn't involve a reboot!
Click to expand...
Click to collapse
I'm working on testing whether disabling HTC's location service will fix our issue. However with the release of the kitchen I was rebooting my phone non-stop. Impossible for me to know if it was working or not.
ElAguila said:
I looked at the other link and I have downloaded both the services.jar file and the LocationManagerService.patch. Which one should I apply and do I apply it? I am having problems with this now.
Click to expand...
Click to collapse
The patch is designed to apply to the source, so that won't help you. The services.jar would replace the one that's already there.
turning off location has been a dramatic difference in speed. its obvious theres something to that. it would get so bad the whole phone would lag
First of all... Happy New Years Everyone!!! I have a Sprint TP2. It's Jan. 1, 2010. My TF3D, however, thinks it's 2016 when receiving text msgs on my SMS stamp dates. I tried messing around w/ some settings on my phone, (doing soft reset, messing w/ TF3D calendar settings, changing WinMo time zone, etc.), but for some reason I keep getting my text msgs showing up as "1/1/16" as the date/time stamp in TF3D on my phone. It is also in the WinMo Threaded SMS, which wouldn't make it a total TF3D issue. When I change the calendar settings in TF3D to that calendar date, it only shows the time and not the physical date since it's a current day in TF3D's judgement.
The reason it shows that 2016 is the year, I believe, is that Jan. 1st on the 2010 and 2016 calendars both start on a Friday. Does anyone know of an existing fix or if there's some way to fix this without hard resetting my phone?
f50ferori said:
First of all... Happy New Years Everyone!!! I have a Sprint TP2. It's Jan. 1, 2010. My TF3D, however, thinks it's 2016 when receiving text msgs on my SMS stamp dates. I tried messing around w/ some settings on my phone, (doing soft reset, messing w/ TF3D calendar settings, changing WinMo time zone, etc.), but for some reason I keep getting my text msgs showing up as "1/1/16" as the date/time stamp in TF3D on my phone. It is also in the WinMo Threaded SMS, which wouldn't make it a total TF3D issue. When I change the calendar settings in TF3D to that calendar date, it only shows the time and not the physical date since it's a current day in TF3D's judgement.
The reason it shows that 2016 is the year, I believe, is that Jan. 1st on the 2010 and 2016 calendars both start on a Friday. Does anyone know of an existing fix or if there's some way to fix this without hard resetting my phone?
Click to expand...
Click to collapse
Verizon here.. same problems all over PPCGeeks. I am running MM Impact rom 12.28.09 2.5 and have the same issue. Maybe a prize for the first person to resolve it???
Thank you. I'm not the only one. I have the EXACT same problem. 2016 SMS timestamp. Tried everything I can think of.
Mines to, the exact same year also... its stupid because this 300 dollar "high tech" phone cant keep time better then my last cheap Razor.
http://www.wmexperts.com/y2016-sms-bug
It seems this is not just affecting a small group of people.
f50ferori said:
First of all... Happy New Years Everyone!!! I have a Sprint TP2. It's Jan. 1, 2010. My TF3D, however, thinks it's 2016 when receiving text msgs on my SMS stamp dates. I tried messing around w/ some settings on my phone, (doing soft reset, messing w/ TF3D calendar settings, changing WinMo time zone, etc.), but for some reason I keep getting my text msgs showing up as "1/1/16" as the date/time stamp in TF3D on my phone. It is also in the WinMo Threaded SMS, which wouldn't make it a total TF3D issue. When I change the calendar settings in TF3D to that calendar date, it only shows the time and not the physical date since it's a current day in TF3D's judgement.
The reason it shows that 2016 is the year, I believe, is that Jan. 1st on the 2010 and 2016 calendars both start on a Friday. Does anyone know of an existing fix or if there's some way to fix this without hard resetting my phone?
Click to expand...
Click to collapse
I dont even think a hard reset will fix this problem. I believe its an issue built into several WM6.5 Rom's
f50ferori said:
The reason it shows that 2016 is the year, I believe, is that Jan. 1st on the 2010 and 2016 calendars both start on a Friday. Does anyone know of an existing fix or if there's some way to fix this without hard resetting my phone?
Click to expand...
Click to collapse
I dont even think a hard reset will fix this problem. I believe its an issue built into several WM6.5 Rom's
Phone: Touch Pro2
Carrier: T-Mobile
Location: Orange County, CA
Rom: EnergyROM "Leo" 28011, Dec 31, Sense 2.5
Have this bug: No
(Some GSM users have reported the bug)
ive got at&t and have no problems
Here's the fix
We just tested this and it works:
http://forum.ppcgeeks.com/showpost.php?p=1454414&postcount=1
Z
ziggy471 said:
We just tested this and it works:
http://forum.ppcgeeks.com/showpost.php?p=1454414&postcount=1
Z
Click to expand...
Click to collapse
Special Thanks To Ziggy!!!
I have to say that this is the quickest response to a sudden issue such as this. Didn't realize it could be solved that easily and within the same day. Nice touch putting this in a .cab format for those who aren't comfortable editing regristy files. Thanks again man.
f50ferori said:
Special Thanks To Ziggy!!!
I have to say that this is the quickest response to a sudden issue such as this. Didn't realize it could be solved that easily and within the same day. Nice touch putting this in a .cab format for those who aren't comfortable editing regristy files. Thanks again man.
Click to expand...
Click to collapse
x2, worked like a charm, may your online-name live in mobile device history ;D
Question about this. I don't have this issue BUT the SMS server on my provider is messed up. If I'm on 3G, it will date all my incoming SMS's one hour behind. If I'm on Edge or GSM, they are the correct time. Will this solve my problem aka use the device's time for the timestamp?
Will this work on GSM devices?
Hey all, while searching for a fix for these, I came across these links. They provide hot-fixes, by HTC. This has not only FIXED the problem of 2016, but also put the MMS/SMS separate thread issue to rest as well (if you are scratching your head, my phone, on top of the 2016 bug, was making separate threads for picture messaging, making it difficult to keep everything organized).
US Cellular Touch Pro 2: http://www.htc.com/us/support/touch-pro2-us-cellular/downloads/
Sprint Touch Pro 2: http://www.htc.com/us/support/touch-pro2-sprint/downloads/
These are the only Touch Pro 2/Tilt 2 Fixes that were available via the HTC website. Verizon and AT&T either are not affected or have not made the fix available, yet.
Hope this Helps you all.
How to fix no bs
forum.(PEE PEE SEE)geeks.com/showpost.php?p=1454414&postcount=1
I know the link has been posted but short version is
If your rom cooked or OEM uses OEMDrivers (chances are is does)
then go to the link posted above
load the following on your phone and reboot when done loading BOTH to save time.
-Ziggy471 USCC Rilphone.cab
-CorrectSMSDate.zip
works for me
if you wanna know how read the post or simple version
first file patches/replaces a dll used when reviving sms to fix the issue rather than work around it like the reg edit "fix" file
second file fixes your screwed up times on the texts already on the device.
have fun hope that helps
earmuffs said:
forum.(PEE PEE SEE)geeks.com/showpost.php?p=1454414&postcount=1
I know the link has been posted but short version is
If your rom cooked or OEM uses OEMDrivers (chances are is does)
then go to the link posted above
load the following on your phone and reboot when done loading BOTH to save time.
-Ziggy471 USCC Rilphone.cab
-CorrectSMSDate.zip
works for me
if you wanna know how read the post or simple version
first file patches/replaces a dll used when reviving sms to fix the issue rather than work around it like the reg edit "fix" file
second file fixes your screwed up times on the texts already on the device.
have fun hope that helps
Click to expand...
Click to collapse
Not sure I follow completely. The links I posted do both fixing whatever files needed fixing AND change the text messages already on the device. This was all on top of the fact that all the threads were together again (both SMS and MMS were in one thread, instead of two or more). AND, to boot, those links were to fixes made by HTC and for the Touch Pro 2 (for Both Sprint and US Cellular Versions). All other versions are work-arounds and third party (not made or authorized by HTC or the phone company), which can lead to extra charges if one were to have to bring it in for repair/replacement and they see non-standard Roms and so on.
Have a nice day.
Sprint direct download:
US Cellular Touch Pro 2: http://www.htc.com/us/support/touch-pro2-us-cellular/downloads/
Sprint Touch Pro 2: http://www.htc.com/us/support/touch-pro2-sprint/downloads/
These are the only Touch Pro 2/Tilt 2 Fixes that were available via the HTC website. Verizon and AT&T either are not affected or have not made the fix available, yet.
Hope this Helps you all.[/QUOTE]
If it helps, I just found the same hotfix directly from Sprint for TP2
http://www.nextel.com/en/software_downloads/pda_smartphone/htc_touch_pro2.shtml
RJ45 said:
Question about this. I don't have this issue BUT the SMS server on my provider is messed up. If I'm on 3G, it will date all my incoming SMS's one hour behind. If I'm on Edge or GSM, they are the correct time. Will this solve my problem aka use the device's time for the timestamp?
Will this work on GSM devices?
Click to expand...
Click to collapse
Can anybody answer this question for me?
I'm looking for the download for the Official Sprint Hotfix for the 2016 timestamp. When Sprint/HTC released the patch, the HTC website and Sprint Website had different versions. My wife and I both have TP2's. I've updated to 6.5 and constantly flashing. I cannot convince my wife to leave the stock 6.1. I left the hotfix undone on hers in hopes of convincing her, but to no avail.
Now she really wants it fixed. HTC and Sprint have removed it from their websites and only have the 6.5 update. I have the one from the HTC website still (not sure how I lost the one from the Sprint website) and it gives invalid version. I have searched here, ppcgeeks and google, but only able to find the ones from the HTC website or non official fixes.
If anyone still has the one from the Sprint site laying around, an upload would be greatly appreciated! Thanks for your time in advance.
***Over the last 2 months, I have been through more issues with T-Mobile then just the issues from the software side. I have spent the majority of that time working with them to try and fix a data connectivity issue I was having. After hard resets, ROM update, and then a site survey, T-Mobile found that the area where I live does NOT have adequate enough coverage to competently supply data coverage to my phone. Notes from the tech said that towers were noted as needed but NO BUDGET was available to deploy a new tower in the area. Because of this, the account rep I spoke to immediately offered a full refund on my unsubsidized HD2 and a refund for all services rendered to-date, including accessories for the phone. As of last night, I left T-Mobile and joined AT&T with a 32gb iPhone in preperation for the upcoming 4G. I'll either trade it in if within 30 days, or give 3GS to wife and get a 4HD on a second line. I have been a Windows Mobile user for YEARS. I still love the HD2 and would never have gotten rid of it, except for the fact I know that AT&T's Edge bands are going away to make room for 3G, and I don't want issues of trying to run HD2 on AT&T's network. I want to stress how much I LOVED the HD2. To me, the phone had a lot of improvement needed, but for what MS and HTC had to work with, it was the best Windows Mobile phone to-date, IMHO. That being said, I have lots of friends with the iPhone, our company exclusively carries it, so I also got a nice discount. I've used one from a distance several times, but never really had one that was mine to really dig into. So far, I am REALLY happy with the phone. I'll jailbreak it and start tweaking it, just like I have my Windows Mobile phones for years, but it's something new for me to play with. =) So, with that being said, I am going to retire from this thread and anybody is more then welcome to take it over. Nibbley15 might be able to do this. I'm still need to get him setup with some software issues he was having, but baby and family haven't left me with a lot of time. Nibbley15, I haven't forgot about you, I just haven't been home to get things configured yet. I'll be in touch soon.
Thanks! ZIMMAY!***
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
I have finished making a CAB. Use at your own risk. I played guine pig and did this myself with no ill effects.
Here are the reg keys that are changed:
Settings from HD2Tweak:
[HKEY_LOCAL_MACHINE\Drivers\TouchPanel]
"PressureThreshold"=dword:000162f2
This is the setting that seems to help the most with being able to click/touch items on screen, especially the corners:[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
Settings from HD2Tweak:
[HKEY_LOCAL_MACHINE\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
"SpeedHigh"=dword:00000000
"SpeedLow"=dword:0000000e
I am still curious what the other settings that Nibbley15 found and how they relate.
***Update 5/21: Added cab to enable Screen options in System Settings to do a screen calibration.
***UPdate 5/22: Reg entry for new CAB is as follows:
[HKEY_LOCAL_MACHINE\\ControlPanel\Pen]
"Hide"=dword:00000000
zim2323 said:
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
Below is what I found to work for me, better then anything I've tried so far. I will be the first to warn you that I have NO IDEA what I'm really doing in relation to TouchResponse, but I do have a good understanding of the registry. The values I've applied may really be nothing more then a happy thought in my head. Though I seem to be able to actually use the close/ok buttons in the upper right part of the screen.
I can make a CAB later, but these are the settings I adjusted my settings to.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
I'd like to see if others could test and post what your experience is. Even better, we may get some help from the chef's to confirm, deny, correct, extrapolate, etc, etc, to find a better fix.
***Edit: Forgot to mention. While the bottom 2 did help, the first FingerThreshold settings seemed to be what made the real difference for being able to competently hit buttons without feeling like I was jackhammering the phone. =)
Thanks!
Click to expand...
Click to collapse
I would have to say that there would be a way to adjust the touchscreen on 2.13 as 2.10 does not have those registries...Well I'll give it a try when I upgrade to 2.13.
Thanks
secano said:
I would have to say that there would be a way to adjust the touchscreen on 2.13 as 2.10 does not have those registries...Well I'll give it a try when I upgrade to 2.13.
Thanks
Click to expand...
Click to collapse
Thanks. Personally I'm running these exact reg and it's working a million times better. But like I said, could be in my head. The only other things I changed sensitivity wise is the scrolling affects that HD2Tweak has. I'll be adding those to whatever I CAB up for a complete fix. I used SKTracker to find out which reg entries changed.
Yes,
Thanks! Please keep the ideas flowing here. Thanks to all that are working this!
I'm posting this reply for folks that are using the 2.13 STOCK ROM and you may want to know the original settings to revert back too or other places to look for you REG peeps to look at.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031 STOCK SETTING
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
STOCK 2.13 version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
STOCK 2.13 version doesn't have this key
Did find these keys:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 20
"FingerThreshold"=dword:31 (0X00001F) <- NOTE:
"NoiseThreshold" = dword: 20
NOTE: if you change the key[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel] to "FingerThreshold"=dword:0
then this value will change to 20, hmmmm.
Other notes: I think that BaseThreshold is where it starts?
I think that the Fingerthreshold here is where it all starts from after learning?
I think that the NoiseThreshold is the amount of "noise" from your fingertouch is allowed before it recognizes before it knows your finger is really touching the screen?
2nd half of post: I'm posting this for folks that may want to know what was in the 2.10.1 STOCK ROM:
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
STOCK 2.10.1 version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
STOCK 2.10.1 version doesn't have this key
Did find these keys:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 0
"FingerThreshold"=dword: 20 (0X000014) <- NOTE: now this is interresting
"NoiseThreshold" = dword: 20
This is what I recommend folks to change their 2.13 Builds to match the 2.10.1 Build for Touch Response.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\TOUCH]
"BaseThreshold" = dword: 0
"FingerThreshold"=dword: 20 (0X000014) <- NOTE: this may change automatically on you from the above change (Setting\TouchPanel)
"NoiseThreshold" = dword: 20
i'm a newbie!!!!
can anyone tell me how cani get to those registry or what kind of program that i need to see the registry? do i need to connect with the computer to see it and change it?
ipsaa said:
i'm a newbie!!!!
can anyone tell me how cani get to those registry or what kind of program that i need to see the registry? do i need to connect with the computer to see it and change it?
Click to expand...
Click to collapse
Hello,
I will try to put this simply, please do not mess with your registry unless you know what you are doing it can crash your phone. When we finally find the fix for this, a cab file will follow shortly. The cab file will do the work for you and you don't have to worry about killing your phone.
If you really really really want to try then please search the threads and there you will find your answers.
Please refer to post #5
zim2323 said:
Ok, I did a lot of playing with the registry this weekend to try and get the same TouchResponse in the new ROM as I had in the old. That has really been my only compaint about the ROM.
Below is what I found to work for me, better then anything I've tried so far. I will be the first to warn you that I have NO IDEA what I'm really doing in relation to TouchResponse, but I do have a good understanding of the registry. The values I've applied may really be nothing more then a happy thought in my head. Though I seem to be able to actually use the close/ok buttons in the upper right part of the screen.
I can make a CAB later, but these are the settings I adjusted my settings to.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
I'd like to see if others could test and post what your experience is. Even better, we may get some help from the chef's to confirm, deny, correct, extrapolate, etc, etc, to find a better fix.
***Edit: Forgot to mention. While the bottom 2 did help, the first FingerThreshold settings seemed to be what made the real difference for being able to competently hit buttons without feeling like I was jackhammering the phone. =)
Thanks!
Click to expand...
Click to collapse
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
mmeyer4663 said:
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
Click to expand...
Click to collapse
I just tweaked the ones that I posted (to a 21903 2.13 BASE build);
I did not add those other 2 registry keys and it is a great improvement;
still testing myself.
Nibbley15 said:
I just tweaked the ones that I posted (to a 21903 2.13 BASE build);
I did not add those other 2 registry keys and it is a great improvement;
still testing myself.
Click to expand...
Click to collapse
Interesting. I do not see the last two entries in my reg.
I guess the difference is, the HTC version for TMO HD2 leaked last week is 21892.
Nibbley15 said:
I'm posting this reply for folks that may be using 6.5.X and not know the original settings to revert back too or other places to look for you REG peeps to look at.
[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031
[HKEY_LOCAL_MACHINE\\Software\OEM\TFLOSettings]
"FingerPressure"=dword:000249F0
6.5.X version doesn't have this key
[HKEY_LOCAL_MACHINE\\Drivers\TouchPanel]
"PressureThreshold"=dword:000162F2
6.5.X version doesn't have this key
Did find this key:
[HKEY_LOCAL_MACHINE\\HARDWARE\CONFIG\]
"FingerThreshold"=dword:31 (0X00001F)
[HKEY_LOCAL_MACHINE\\HARDWARE\SETTING\TOUCHPANEL]
"FingerThreshold"=dword:31 (0X00001F)
some others worth looking at possibly:
[HKEY_LOCAL_MACHINE\\SOFTWARE\HTC\TouchGL]
"DBCLKFingerDistance"=dword:45
"DBCLKFingerInterval"=dword:350
Click to expand...
Click to collapse
THANK YOU for posting this info. I hadn't got back to do that yet.
mmeyer4663 said:
Did you have to add the last two? I am running the release leaked on HTC last week and do not see the last two.
Click to expand...
Click to collapse
Both of those keys/values were there. Although the one thing I had already installed and run was BSBTweaks and HD2Tweaks. Either of those 2 could have created the values. They seem to actually work, but that's kinda why I was posting, to see what others experience was with it.
mmeyer4663 said:
Interesting. I do not see the last two entries in my reg.
I guess the difference is, the HTC version for TMO HD2 leaked last week is 21892.
Click to expand...
Click to collapse
Just to clarify,
I am using a completely stock build of the new TMobile ROM. Based on the information I've read and that has been posted here, it looks like older ROMs may, or may not have those reg keys/settings implemented depending on the ROM timeline.
For those that have had a chance to try these settings, does it seem to improve things?
The numbers I used were just numbers I kept increasing. I have no idea what the max value is or could be.
I'm hoping tomorrow I'll have a chance to post the reset of the reg tweaks I used from HD2Tweaks that would be apart of the entire TouchResponse "package" that I've been working with.
Also, just in case someone wonders, don't ask for permission, TAKE PERMISSION to use this information however you want. You can say you figured it out and incorporate it into "My Awesome ROM". I really don't care. It's about getting things fixed we don't like, and making them better. I could care less who gets credit. I know for a fact that there are chef's and others out there that know a bazillion times more about this stuff then me. I just like know that I helped, if in fact it really does help.
Peace out!
I only had the first value in my registry:
"[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031"
But I did make the change and it absolutely made a huge difference, for the better.
Thank you for this. I just made the first tweak and things are 100% better. That eliminated my one big gripe about the new stock ROM.
xanderdad said:
I only had the first value in my registry:
"[HKEY_LOCAL_MACHINE\\HARDWARE\Setting\TouchPanel]
"FingerThreshold"=dword:00000000
"FingerThreshold"=dword:00000031"
But I did make the change and it absolutely made a huge difference, for the better.
Click to expand...
Click to collapse
So maybe that alone is the fix. I included the other keys because they were apart of the HTC Sense settings in HD2Tweak. Those keys may be more for scrolling issues.
Please put out a cab file for this mod. The lack of responsiveness is killing many here. Thanks.
NickPP said:
Please put out a cab file for this mod. The lack of responsiveness is killing many here. Thanks.
Click to expand...
Click to collapse
Well, before I did that I wanted to know exactly what was "fixing" the problem and what exactly those settings were doing or how it may interact or affect other functions of the phone. So far I have had nothin but positive response to this.
I have a little more testing to do and then I will putting out a CAB with all the fixes I apply that are related to making TouchResponse behave like I would expect it to. Expect something in the next 24 hours. In the mean time, you can always use a registry editor and apply the reg values yourself.
I'm dealing with job and a new baby so my time is short. =)
Hey there. First time I've started a thread in here in a while but these 2 issues have been plaguing me for quite some time... Ever since I've been using Comm5 builds as a matter of fact.
For my first issue - I have a visual glitch in my phone canvas(See screenshot below) that has really started to IRK me.
Facts:
WM Version:
Code:
WM6.5.5 Build 23563
Phone Canvas Build:
Code:
PACKAGE_LEO_TMOUS_Phone_Canvas_Enhancement_2G_4_2_62120113626_0
Device:
Code:
You guessed it.. T-Mobile HD2
I've also attached the phone canvas itself so you can look at the actual files I'm using.
Now for the second issue - When I go to add a new task that has to have a start/due date assigned to it, I can't select a new date. I click on the date box and it auto-fills but doesn't let me actually use the date picker or the WM Calendar Popup box. In essence, I can't actually set dates for my Tasks when I need to add them. This would be much less of an issue if there was a better 3rd party tasks application available but sadly as of right now there isn't one so I really need the WM tasks app fixed.
As I'm sure you might have already guessed from either my signature or the first half of this post, I'm using the 23563 build from Da_G's thread.
Any and all help would be greatly appreciated.
DH
Bumping this. Still have the problems and still seeking an answer.
+1 on not being able to set start / due date for tasks.
the date entry looks like it is selected, and one expects a date picker to popup, but nothing.
Bumping again. Still seeking a fix for the phone canvas and tasks in WM6.5.5 build 23563.
Bumping this again... Please help. The Tasks issue isn't nearly as important as the phone canvas glitch but honestly they're both driving me crazy...
I'm really desperate to get this fixed... I've searched for almost a week now and exhausted all my resources to find what is causing this issue.
Hi there friend,
Try HTC's website for downloads on your phone they have tons of bug fixes available. Some reason they only have the downloads available on the backdoor europe side, but looks like same phone - so at least it can point you in right direction.
h***://***.htc.com/europe/supportdownloadlist.aspx?p_id=297&act=sd&cat=all
PEACEOFWAR said:
Hi there friend,
Try HTC's website for downloads on your phone they have tons of bug fixes available. Some reason they only have the downloads available on the backdoor europe side, but looks like same phone - so at least it can point you in right direction.
h***://***.htc.com/europe/supportdownloadlist.aspx?p_id=297&act=sd&cat=all
Click to expand...
Click to collapse
Thanks for the tip. I just checked that link and unfortunately none of the fixes available on their site are relevant to my issue.
@everyone else - Still seeking a fix.
hi. Finally found a working alternative for the buggy tasks in 6.5.5
http://forum.xda-developers.com/showthread.php?t=591794
works with the built in tasks, so they sync as normal with outlook, and since i am using cookies home tab mod, i can alter the default program to open when i click on a task to be this rather than the built in tasks.
Not ideal, i would have preferred to fix it, (i tried by cooking in an older version of tasks.exe and tasks.dll, but no joy) but better than no start/due time for tasks!
samsamuel said:
hi. Finally found a working alternative for the buggy tasks in 6.5.5
http://forum.xda-developers.com/showthread.php?t=591794
works with the built in tasks, so they sync as normal with outlook, and since i am using cookies home tab mod, i can alter the default program to open when i click on a task to be this rather than the built in tasks.
Not ideal, i would have preferred to fix it, (i tried by cooking in an older version of tasks.exe and tasks.dll, but no joy) but better than no start/due time for tasks!
Click to expand...
Click to collapse
Thanks this does help a little. Makes tasks usable at least.
_______________________________
Still seeking a fix for the phone canvas bug. Have exhausted all resources. REALLY need some help!!