Hi there,
After flashing my TD with panosha's Shine On 1.9, I experience some strange behavior:
When the TD is in standby (i.e. touchscreen off) and there is an incoming call, the display turns on but the touchscreen remains completely unresponsive, i.e. it neither responds to "Answer", "Ignore", etc., nor to "Start" in the upper left corner.
And that is while the device is definitely unlocked (I don't even use the unlock function as I switch to standby as soon as I don't need the phone).
In fact I can answer the call with the hardware button only - in that case the connection establishes, but the screen goes blank.
If the device is not in sleep mode, everything works as it should.
I have tweaked several settings with both Advanced Config and Diamond Tweak, but in my opinion none of the tweakings applied might cause such a behavior.
Thanks for your ideas .
ROM contains:
Answer Key Disabler v0.3.1
Hey, thanks so much!
It wouldn't have occured to me that that is in fact a desired feature of that ROM, therefore I didn't even consider re-reading its thread.
lol i think people need to start reading about the
stuff there putting on there phones.
Related
Hello,
I have got the following issue: with about 1 out of 4 calls, the screen of the diamond freezes on "Dialing..." (after typing a number or calling a known contact).
The call connects correctly, I can speak, hear, but the phone seems crashed and I cannot use the touch screen (it does not turn black automtically as usual either) and can't even end the call (even with hw button).
It started happening after upgrade to ROM
RUU_Diamond_HTC_FRA_1.93.406.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
I've got some Advanced Config tool tweaks as well.
Is that a known bug?
Should I try to upgrade radio? or hard reset and try without registry tweaks?
Thank you in advance.
Z.
I have had my Diamond for about 5 days now. The other day I noticed it will get stuck in a constant weak vibrate. It seems that a vibe event will cause it to start, like the phone doesn't know to stop vibrating.
I call it weak, because while it is doing this, I can go to volume settings, select Vibrate and the much stronger vibrate even occurs. It seems if I shake the phone or move it around a bit the weak vibrating will stop.
Also shaking the phone sometimes causes this weak vibrating to begin.
Sounds like a mechanical issue ? I have installed some apps like GSen & SensorLock. A couple others like Advanced Config and done some of the registry tweaks.
Any suggestions would be greatly appreciated.
Thanks in advance.
mackerman said:
I have had my Diamond for about 5 days now. The other day I noticed it will get stuck in a constant weak vibrate. It seems that a vibe event will cause it to start, like the phone doesn't know to stop vibrating.
I call it weak, because while it is doing this, I can go to volume settings, select Vibrate and the much stronger vibrate even occurs. It seems if I shake the phone or move it around a bit the weak vibrating will stop.
Also shaking the phone sometimes causes this weak vibrating to begin.
Sounds like a mechanical issue ? I have installed some apps like GSen & SensorLock. A couple others like Advanced Config and done some of the registry tweaks.
Any suggestions would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Un install sensor lock and test. i had this issue with an old version ofthat application.
I have uninstalled both GSen (Since it wouldn't rotate SMS for me on Sprint Diamond) and Sensor Lock. The device is still doing this strange vibrate.
I noticed even when I hold the power button and turn it off (soft reboot?) it continues the odd vibrate. The vibrate will however stop when I remove the battery.
Just giving an update. The phone has stopped doing this strange vibrate action. Not sure if it was related to the program un-installation or not. As stated above it continued to do the vibrating action after the program was uninstalled, but definitely less frequently.
I had something very similar the other day. I'm using the swift ROM.
Its never happened before, and i've been using this same rom a for a while now.
ya i have the sprint diamond and mine did that the one time when i took it off the charger. it would vibrate pulses and the phone was like frozen. So i plugged it back in the charger and uninstalled sensorlock and its fine now
mackerman said:
I have uninstalled both GSen (Since it wouldn't rotate SMS for me on Sprint Diamond) and Sensor Lock. The device is still doing this strange vibrate.
I noticed even when I hold the power button and turn it off (soft reboot?) it continues the odd vibrate. The vibrate will however stop when I remove the battery.
Click to expand...
Click to collapse
Somewhat off topic but did you find anything that rotates in SMS on the Sprint Diamond?
Don't blame it on Sensor Lock. I don't have that program installed & mine started vibrating non stop the other day. I couldn't get it to stop & finally did a hard reset. It still continued to vibrate all the way to the point where it got to the green Windows Mobile screen. It stopped, after that & it hasn't happened again since (this was on Saturday). I had done some of the reg tweaks for TF3D performance & nothing else.
sensor lock was the only program i had installed so it was the reason for me. as far as i know only way to rotate SMS with sprint diamond is the long press key
I have also done some of the reg key tweaks on my diamond. It did happen again last night, but before that it's been a few days. I had GSen installed, and it wasn't rotating on SMS, I think I read it wouldn't work with the Sprint Diamond.
What is the long key press method?
Hi,
currently some people are reporting problems with TouchLockPro 2.2.7, which uses the GSENSOR and capacitive sensor for unlocking.
Via this poll I want to achieve the following:
* get insight which percentage experiences problems with TouchLockPro
Hope this is going to work.
Rick.
ZR,
...USING THE STANDARD WINDOWS MOBILE DIALER (NOT HTC) PREVENTS UNLOCKING...
Something else I noticed. Because of ring delays (caller is on the 2nd or 3rd rings when my phone rings the first time), I switched to the default dialer skin. That's the standard WM6.1 phone interface. When I'm on the dialer screen when the phone wakes up (either through a call or me hitting the power button), the touchscreen stays locked (red strip will not go away) and the capacitive unlock does not work (though the buttons do).
There must be some compatibility issue with the standard dialer vs. the HTC dialer. In fact, there are several other compatibility issues with the standard dialer (bluetooth icon is gone, volume control during a call does not work, etc.), so I bet some of these problems are a result of some of us not using default HTC dialer skin.
The only way I can unlock the phone when it is on the dialer screen is by sliding the keyboard or removing the stylus.
Also, now at the end of the day, if I am on the today screen and wake up the phone, it takes about 5 seconds before the capacitive unlock works. Any ideas what could be causing that delay?
I don't remember if I had problems with v2.1 so I did not check the box. I am having problems with 2.2.7 so I posted my problems in the other thread.
well I have had problems with version 2.2.6 - sometimes it didnt lock; when I connected to EDGE display turned off etc. but now version 2.2.7 looks that its working right again
v2.2.4 so far is the one with most responsive capacitive sensor on my Dutty ROM for HTC Diamond.
ZR,
I'm still using TLP 2.1 on my touchpro.
After a few attempts to upgrade to TLP2.2 and higher, which always giving unstable feedbacks, i turn back to the more stable TLP2.1. Afterall, i don't use the features in TLP2.2 with Gsensor support and i don't use light sensor either.
TouchLockPro 2.3
Because of too may problems with TouchLockPro 2.2.7, I posted TouchLockPro 2.3, which should solve the reported problems.
See TouchLockPro XDA thread and zuinigerijder.com
Hope this version is better, as bonus I included some new cool features
When my battery falls below 50% my touchscreen begins to act weird. No matter what I select it chooses whatever option is at the bottom of the screen. I can occasionally get it to work if I reboot the device or open and close the keyboard about 10 times. Once it has been corrected it falls back to the odd behavior within about five minutes. I have established that this doesn't happen if the batter is above 50%, and if I charge the phone up only a few percent then the issue goes away.
The phone currently has Cyanogen 4.2.15.1
I'm stumped as to what could be causing this and was unable to find any similar postings on the forum. If this issue has been addressed in another thread I would greatly appreciate a link to said thread.
Any suggestions would be great. Thanks!
My G1 also has similar problem, the touch screen is totally not functioning, I still finding the cause but it's so annoying. When the touch screen is not working, I can't invoke the "Dialer" function, that means I can't dial. Also, when there's incoming calls, the dialer function can't pop up too. That makes my G1 can't be worked as a phone when touch screen is not working.
Hello. I've had this device for awhile now and it's probably the best phone I've ever had.. except I started to have problems with regards to calls just recently. I actually rooted the device about 2 months ago and am currently using the Rombie mod v2 (JPC), if that helps. Anyway, the problem happens in the middle of a conversation, where the proximity sensor somehow disappears and the speaker mode is activated on its own (or maybe it gets in contact to my skin, I'm not sure, since the screen is supposed to remain blank). After that, the device becomes unresponsive: the touch sensitive menu and back keys don't work, and neither does the screen itself..but the hard key home button works and I could still hear the other caller via loudspeaker. I force a reset and everything goes back to normal (I mean this call issue doesn't happen all the time). I don't have any screen protector to affect the performance of the sensor. Anyone can help me out with this? Thanks!