Why, using numeric tast, when i write a sms, very often, the bar space doesn't work. The text, infact, if i write quickly, is whithout spaces. Afhter touching the bar space, i can't touch immediatly the next letter, i have to wait almost one second.
Is it normal?
Thank You..
I had problems with keypad when composing text too. Sometimes the back space won't work. Sometimes, spacebar behaves out of order. And other frustrating weird stuffs.
I found a few ways to temporarily set it to work properly. To avoid the time-consuming soft reset. The solutions i came up with are not consistent. Sometimes you have to try more than one of the methods, or in combinations.
1. Close down some apps. Generally, i observed that if your remaining RAM falls below 80Mb, the chances of misbehaving keypad rises. Though not consistent. Just higher risk to go out of order. Use BattClock to monitor remaining RAM, and Task Manager to close down apps.
2. Go to Text Input settings, and remove garbage words from User Dictionary. They tend to pile up real quick. Most mistyped words are sucked in, and interpreted as user's custom words. The programming of this User Dictionary really suck. I clean it up daily.
3. Shutting down, and re-running HTC Messaging can sometimes help. Really weird.
4. Install and use CleanRAM.
These are temporary solutions. It doesn't work all the time. But do work most of the time. Reducing the frequency of your trips to the soft reset planet drastically.
We'll just have to live with it for now. Until someone at HTC decided to actually read our complaints for once and do something about it.
Maybe by the next decade.
Related
I have the tmobile TP2 for two days and I have two major issues.
1. I can't scroll smoothly for the life of me. Flicking in the all people menu goes way far and slow scrolling seems impossible without turning into a tap. Same thing in the slide bar and pretty much any situation that involves gestures.The touch screen response seems exagerated/extremely sensitive for most of the time and other times lags or requires several taps. I calibrated the screen but don't see much improvement. Does anybody else have the same problem / is it the hardware or just a matter of learning curve on a very "touchy" screen?
Is there a way to adjust the scrolling speed and the screen sensitivity?
2. going online is extremely frustrating. most links in webpages don't work in either IE or Opera, not to mention excruciatingly slow load (I bounce between edge & 3g) and several attempts to open a website (screen turns white and freezes)
Is there a way to obtain a half decent web browsing experience without being tech savvy?
I really want to like this phone but it's becoming too frustrating/time consuming to accomplish some of these presumably simple tasks like the ones mentioned above.
thanks in advance for your response
1. You're probably just used to using a capacitive touch screen like on the iPhone. When flick-scrolling on a resistive screen, you have to apply pressure. Don't apply so much that you are pushing down on the screen, but you shouldn't be brushing the screen with your fingers. That is probably what's causing the accidental taps you experience.
2. Don't know about anyone else, but here are my own tips to make my browsing experience extremely satisfying.
-disable java script and plugins. Most sites don't need them to work and this makes your pages load faster. Only turn them on when you absolutely need them.
-use your fingernails to hit links. Hit them once firmly and trust that the browser picked it up (it often does). Zoom in to small links to hit those.
-don't use IE
What sites don't work for you?
thanks for the reply. Example of site that doesn't work: realtor.com I cannot enter search data at all (i.e. zip code).
I tried your suggestion about scrolling but I am not able to scroll slow (i.e from one contact to the next or second next). someone who owns a tilt mentioned that there is a way to tweak the scrolling/screen sensitivity. Do you know how?
Thanks again
ohyeahar said:
1.-use your fingernails to hit links. Hit them once firmly and trust that the browser picked it up (it often does). Zoom in to small links to hit those.
Click to expand...
Click to collapse
...That's where I've been going wrong, patience not being one of my many virtues
Song list
I'm having a similar problem: I like to listen to Arionradio.com, but I cannot get the browser to show what song is being play either on the main site or when I use the Arion Radio Player; I can hear the song fine but does not list whats playing. Is there a way to fix this?
Thank you for taking the time to reply!
Have you tried the SkyFire browser yet. it is a Full java enabled browser. I just went to realtor.com and did a search for my zip code. It worked and looks just like it does on the computer.
I was wondering if anyone else has seen any of these 2 issues with their tilt 2. One of them is a problem, the other may just be normal.
1. Text messaging - Text messaging, as i've learned to deal with on all the winmo phones i've owned is sluggish. But this particular problem I haven't seen before. The problem is when I close out a text message and the screen goes back to the inbox. The screen freezes for a few seconds (sometimes longer than others) before I can do anything else. It's really annoying. I have attached screenshots of this. I know it's frozen because the top of the screen has not redrawn, as you can see in the screenshot.
2. It seems that there must be a memory leak somewhere as my memory usage keeps increasing, yet no programs are open or running. I have attached a screen shot of the task manager as well. As you can see it's at 86% and nothing is open.
If you have experienced this and know of a way to fix either of these, please share. By the way, i'm using a stock ROM. Thanks everyone for your help.
Normally the stock ROM´s are full of crappy apps installed by the cell providers.
Normally I reflash inmediately to a cooked ROM from the great Chefs we have here at XDA!
Those ROM¨s nomrally perform better, of course it affects the apps installed by you at the end
Has anybody experienced the text messaging issue in any of the cooked ROMS?
maybe
imeraz said:
Has anybody experienced the text messaging issue in any of the cooked ROMS?
Click to expand...
Click to collapse
i have an at&t branded tp2 and i am running an older leo from ngrz28 (thanks by the way) and yes i stay between 59% lowest i've ever seen and 84% with nothing open. i is probably cuz the good cooks from xda shoved an elephant of a rom (really made for snapdragon prosseser with twice the speed) into the tp2 (minus all the bloatware and other crud). oh well do a lot of reading and try a few different roms to find the right one for you. good luck bro.
Thanks for the replies!
Well, it looks like I may have found a solution to both of my problems. I figured out how to get rid of the text messaging issue...for the most part. I figured out that if I leave text messaging running, once all my conversations are opened once, the lag isn't there when I close out a conversation. This lag happened to me constantly because I have my phone set to close programs completely when I tap the "X" (as opposed to minimizing...I do it so I don't end up with 10 different programs running and crashing my phone). I figured out that if I just minimize text messaging and never close it out, the lag isn't there. Must be a caching thing or something with the sms conversations.
As far as the memory issue goes I gave spb mobile shell a shot and installed the trial version. So far my memory usage has stayed at about 69%. Looks like tf3d is a memory hog.
Anyways, thanks for the replies and hopefully this information helps someone.
imeraz said:
Thanks for the replies!
Well, it looks like I may have found a solution to both of my problems. I figured out how to get rid of the text messaging issue...for the most part. I figured out that if I leave text messaging running, once all my conversations are opened once, the lag isn't there when I close out a conversation. This lag happened to me constantly because I have my phone set to close programs completely when I tap the "X" (as opposed to minimizing...I do it so I don't end up with 10 different programs running and crashing my phone). I figured out that if I just minimize text messaging and never close it out, the lag isn't there. Must be a caching thing or something with the sms conversations.
As far as the memory issue goes I gave spb mobile shell a shot and installed the trial version. So far my memory usage has stayed at about 69%. Looks like tf3d is a memory hog.
Anyways, thanks for the replies and hopefully this information helps someone.
Click to expand...
Click to collapse
Memory usage / leaks depend a lot on your ROM built
I found out the same for SMS. However opening / closing a contact in the contact list takes even longer than the SMS issue and for this I havent found any solution yet
Try disabling XT9 and all the other Xt9 and predictive word settings.
This worked for me when Landscape mode and typing emails..
I've found myself back here on the forums after getting frustrated with the official Windows updates.
There's a really big glitch I've encountered that changes the volume from Normal to Vibrate or vice versa.
It took me years to finally realize why my phone was switching profiles without me changing it.
Whenever I start a new text message and type the letter 'A' too fast as the first letter of the message it changes to Normal/Vibrate. If I slowly start typing the message, the glitch is avoided.
Has anyone else encountered this bizarre problem? I'm still trying to figure out how this could even be possible! Any suggestions from the gurus?
This problem exists on ALL Roms I believe ... I have always had it.
Here is the explanation, as I see it:
The Texting program, in all honesty, sucks. Windows decided to create the TextBox before loading up the history of messages, which meant there was a huge lag. FURTHER: They didn't do these actions on separate threads, which means the lag would occur on one thread.
Now think of it this way: While a program can have different 'threads' to run on, the keyboard, while an input to the program, will get its own thread because it is a system device. So the Keyboard gets its own thread, therefore its own buffer.
What goes on, in the second it takes to load the text message history is this:
1) TextBox appears and is activated to user [and Keyboard]
2) History load starts on same thread as TextBox
3) User types "A"
4) "A" is sent to the foreground window, which is the TextBox
5) The TextBox takes a while to respond, to process the message, therefore the system assumes the key was held down for X seconds.
6) Realizing this is the Hard-coded "change-profile" shortcut, the system then sends a message to the Profile 'manager' (if one exists, but in theory let us say it does) to switch profiles.
7) The TextBox stops lagging since the history is loaded, and it registers that the 'A' key was lifted.
The whole issue has to do with timing and buffers ... all pretty stupid errors on Microsoft's part.
I had wanted to start making a replacement, but alas, I have no time
One day....maybe one day
Brilliant Cyclone! Thanks for the simplified/understandable response.
I didn't realize the quick button to switch profiles is the 'A' button. That's much more understandable.
I just updated my phone to 3v0, but then downdated to 1.22.531.6 because it 3v0 was too buggy.
It cleared all my text messages and I haven't had the A-glitch yet. I'm guessing clearing the text history is the only way to avoid the glitch.
I'm surprised I haven't heard other people talking about this problem. I Googled it, but couldn't find anything.
Very interesting...although, these kind of problems are expected when dealing with Microsoft.
I just had a thought...
How easy would it be to change the "Hard-coded "change-profile" shortcut" to a letter that is never used? Like 'Q'. Or completely remove the change-profile shortcut.
You guys are way over my head when it comes to working with the fundamentals of phones(the registry?) like this. I'd like to learn more, but I must also say....One day....maybe one day!
I don't honestly believe it is possible..."hard coded' means that they programmed it straight into the OS.
Now realize, this is only my theory, I can be 100% incorrect..
The OS can't have any changes made to it? I thought this was possible through something like "regedit" on PC's. Changes to the registry aren't changes to the OS?
zemaoner said:
The OS can't have any changes made to it? I thought this was possible through something like "regedit" on PC's. Changes to the registry aren't changes to the OS?
Click to expand...
Click to collapse
Things in the Registry aren't 'hardcoded' ... when I say 'hardcoded' I mean that when Microsoft employees was in their IDEs developing, they typed in a few lines of code dealing with the A-Key, and then compiled it. We cannot change that, especially since it is part of the ROM.
When I use email, calendar or anything else that requires text, the spellcheck kicks in and, with my DHD, the alternatives proffered jump around. They jump from below to above the text box and back again several times before coming to rest where they should be below the text. That really slows things down and is driving me up the wall.
I've tried changing settings but nothing seems to cure it. If I was better at typing, I'd turn off spellcheck but my typing is utter rubbish so I really do need it.
I'm wondering if this is another app interfering with the normal operation. If so, what sort of app could do that. I don't have any replacement keyboards, spellcheckers or similar installed.
Any ideas?
Thanks.
B
So I'm sure everyone has experienced performance issues when typing stuff on their keyboards. I use Swiftkey 3 and for a long time I thought it was simply performance issues with the keyboard itself, but after testing the stock Samsung keyboard, I get the same performance issues. Basically there is delays while I type, and I've linked it mostly to when the phone is doing some system-intensive task such as using the radios to send a text or receive a text.
The best way to test it is by opening up your SMS app, type up a quick text and send it. While the text is sending (usually takes a few seconds in most cases) start typing another text and you will see a significant drop in performance from your keyboard, and really everything else.
Is there a reason for this? Does it have anything to do with Android's process prioritization? Most importantly, can this be fixed?