All,
It seems that the WM6 problems are getting lost in the 36+ pages of the other thread.
I thought it would be appropriate to start a new thread to address the problems and answers that members might be facing.
Here are a couple to start with (most of which are TrueVGA related):
1.) Phone Pad is oversized in VGA mode without using other tools like vjbigphone or others. Smart dialer is off the top of the screen and incomming calls is partially below the edge of the screen on the bottom.
2.) Smart dialer is not consistent in its functionality.
3.) Successive flashes of the 2nd downloadable ROM seem to leave artifactes of older images which seems to create compounded legacy problems.
4.) ICON's don't always show up in VGA mode.
5.) Spb MobileShell doesn't work / Locks up in VGA mode.
6.) OzVGA locks up the device in either mode.
7.) MvrTrueVGA v1.3 works most of the time, but sometimes errors out and refuses to change (QVGA/VGA) modes.
8.) On occasion the integrated caller history doesn't show allow interaction with the contacts, as it should.
This is my list of concerns at the moment, if anyone has resolved these issues or found a way to not have them in the first place, let me know.
Thanks...
v/r
Bob
Related
I find that my Sprint titan is, at times, very unresponsive. Usually it will happen after having not used it for a few hours. After I wake the phone up, I'll notice that most tasks require multiple inputs before sensing the touch. (ie: if I wanna open the start menu I might have to touch it 3-6 times before the phone opens the start menu) It is not just the touch screen; the buttons are just as unresponsive when the issue is present. After a about a minute or two of use while I'm having this issue the phone will become more and more unresponsive, finally I might have to press an item 10-20 times before the phone opens it. At that point I need to reset the phone in order to restore normal functionality.
This used to happen to me using DCD 3.01 and I hoped it would not happen on the newer 3.04 but same issue remains.
Something that is unique to my situation is that I'm in the US navy and currently deployed, thus my titan will never get a signal. Being that I can't find anyone else with this problem it leads me to think that it might be related to never having a cell signal as most people who change their ROM probably are on the network.
Just to let you know, I have had this problem. I think I limited it down to IM+. With just the included applications running, this did not occur.
I've never used IM+
I'd suggest that both of you list ALL apps that you added to the ROM.... That way we can cross reference what you both have in common when the issue happens, and can eliminate OEM's one at a time....
I didn't add anything to the roms. Just donwloaded the rom and flashed it.
I installed Mortplayer and HTC home 2.0 + HTC home customizer 1.0. Those are the only two programs I have on my titan.
Then it could be HTC home. I found what specifically lags me about IM+ is the home screen plugin. Try disabling the HTC home screen plugin.
I'm having this same problem. It started after updating to the new Rev A/GPS Rom from Sprint. I've just recently noticed that when the device becomes unresponsive, the signal strength icon is showing data transfer. The device is acting like it is becoming bogged down while sending or receiving a large amount of data. The last time it became unresponsive, I hit the Com manager button, triggered airplane mode (thereby killing the data connection), and the device instantly became responsive again.
The only thing I have running in the background is Outlook which is checking my Gmail every 15 minutes.
I do have HTC home and Home Customizer on it though. Anyone seeing a pattern here??? I do not use IM.
I ran across Spybot Search & Destroy for WinMo standard and PPC last night. was thinking of installing it and see if it discovers any possible malware. I highly doubt it though since I never surf to unknown websites or open unknown mail.
I should also say that I did make some reg edits for better power management. But they were done with the previous Sprint Rom AND after the new Sprint Rom was installed. Never had a problem when running the previous Sprint Rom.
Anyone else noticing this happening when data seems to be transferring? Anyone try disabling the HTC home and Home Customizer?
HTC Home is a huge memory leak, the worst of any PPC application I've ever run
it dumps tons of useless info to the kernel log which may be the cause
I would suggest rltoday, there are htc home clone themes available
Thanks so much for the info DCD!! Checking out rltoday right now. Possibilities look endless.
I'm bumping this thread because I have the same problem all the time. The issue appeared on No2Chem's ROMs and DCD's roms. I have many programs installed, but it sounds like this occurs even with no programs installed. Did anyone figure out a fix for this?
It is quite annoying to find my phone randomly very unresponsive to any key press (touch screen or hard buttons).
By the way, could it be our radios? I'm using 3.42.30.
Interesting - I've been a user of DCD roms since pre-3.01 on my XV6800 and have never had any problems. After installing 3.3.4, however, I did experience these exact same symptoms. I tried removing applications, today plugins, etc., but the issue persisted. As a last resort, figuring it was just some incompatibility with my configuration and not the rom, I rolled back to 3.2.6 and all has been fine so far.
hi,
leaving aside the dead or blocked pixels, I encountered an issue with my HTC TC WM6.1 touchscreen in the X (close button) area only - I know it still works, because the X flashes when I use the finger or the pen, it activates the phone and it even triggers a vibration response (when activated) but it no longer functions properly, as it doesn't close the programs anymore (don't think that the Close function is disabled, because it doesn't have the OK function either) and the window remains active on the screen.
It happened gradually, but al the neighboring areas assigned to other apps work just fine.
It's true, I spent some time tweaking, but I was carefull when modifying.
Have you experienced something similar? Can it be undone
thank you.
Assuming you got any backup, restore last registry backup(touchscreen keys only)
Hello!
The main bugs I get with my Rose on Uk Orange is the soft key that interacts with the home screen.
Sometimes when I get a message or email it doesn't display on the home screen and when highighting the sms or email panel pressing "inbox" does nothing. Instead I have to hit start and go into messages that way.
A reboot solves this. But it does it a bit to often for it to be ok. Should I reboot my smartphone once every day like a PC?
Also the answer key occasionally plays up. Either it doesn't work when answering a call or when pressing "call" from the contacts list it just takes you straight to the number dial screen. Odd. A reboot does normally solve it but not always.
Can't find any hot fixes on the HTC site. Looks like there isn't a new ROM available for it as yet. What can I do!? I love the Rose but it annoys me a bit!
Thanks in advance.
If I were you I'd make a back-up of the files on your device by syncing it with a PC and then hardreset it by going to: start - desktop tools (or something like that) - clear storage. Might be helpful.
Yesterday I rooted my LG Thrive (part of the Optimus One family) and everything went fine. I was playing around with overclocking and removing bloatware using ROM Toolbox. Eventually however, I realized I wanted to remove some AT&T bloatware apps from initial startup. I was able to disable some through the program, but when doing so the app was freezing and I would just press the zoom button to return and then continue disabling additional apps. In doing so however, I'm certain this messed things up big time. I restarted my phone to see if these disabled apps would still start. The unlock screen came up but the touchscreen was inactive (it wouldn't respond to touch anywhere) as were any of the buttons on the phone (even the power button). I'm guessing I disabled quite an important startup service somehow along the lines. This is the same situtation in safe mode.
I was able to unlock the phone if I receive a text or call, then the touchscreen becomes active and allows me to unlock and use the phone. However, there is no desktop - it's a black screen with taskbar on top. The messaging app works as well as the device receives emails. But aside from the taskbar on the top, there's nothing.
I don't know where to go from here. Do I just try to install cyanogenmod over everything - if so, could someone point me in the right direciton? (I'm running a linux system as my desktop in case someone suggets a program to use for flashing). Or is there a simple fix to this issue I caused?
Thanks everyone!
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
bvz2000 said:
My stock Verizon GS3 waits a while before it makes a call.
I can click on a favorite, dial a number directly, or select someone from my contact list. When I hit dial, the phone does nothing for up to two minutes. It remains completely usable (I can surf the web on 4G, open and close apps, whatever). Just no phoning. Then, after a delay of anywhere from seconds to two minutes, it will suddenly dial the number. From then on, it works the way it should. The next time I try to dial, assuming I have waited a bit, it all happens again. If I try using the phone right away after it has sort of "woken up" to the fact that it should dial numbers, then I can continue to dial new numbers without a delay. Only after it sits a bit does it get stuck again. If I try to hit the "dial" button a number of times (aka, retry dialing because the phone isn't doing what it should) it queues these requests up and once it gets unstuck, it will dial all the numbers one after the other.
This issue also affects two other widgets (and nothing else that I can ascertain). These are the Assistive Light widget and the Negative Colors widget. They behave the exact same as the dialer. I can hit them as many times as I want, and it will simply seem to ignore my button presses. But, after a delay of up to two minutes, suddenly every button press I hit will be queued up and executed all at once (causing the screen to flash negative and positive, and the flash to go on and off a bunch of times).
I am running go launcher and the stock android 4.0.4 on Verizon.
Some specific questions:
1) What should I look for in the logs to indicate that the phone is placing a call (or handling the Assistive Light request)? I have tried to isolate the portion of the logs around when this happens but they are so dense I have no idea if I am even looking in the right area.
2) I occasionally see "VoIPInterfaceManager" referenced in the logs, but as far as I know I am not using VoIP (I had skype installed at one point but then deleted it when this problem started thinking that maybe it was interfering, but to no avail). Is this in any way relevant?
3) I have an extra SD card installed (yanked from my old DroidX). Could that be the issue? I just pulled it out again, but the phone does not always misbehave, just sometimes (say, 75% of the time) and it just happens to be playing nice right now even before I pulled the card so I don't know if it helped or not.
4) Is there anything I can do to start diagnosing this issue (i.e. apps to try to diagnose what is going on, developer modes to put the phone in)? How about anything people can suggest to even start narrowing down what the culprit may be (hardware? downloaded app? os?)
Thanks, and sorry for the long posting. This is making me nuts.
Click to expand...
Click to collapse
So several days have passed, and it appears to still be working. I suspect the sd card was the culprit. No idea why. But I am a happy camper again.