Database Users

Modded ROM vs. standard ROM keyboard lag difference?

Hi. I have been running a couple of modded ROMs and the htc_ime i install on those ROMs is always laggy and somewhat buggy. Is it the same with standard ROM?
One of the bugs i have noticed is that sometimes, when i press space it just goes nuts and creates a period(dot) and just continues to make spaces for a short period. And this has happened on several ROMs.

It's the HTC_IME, not the ROM. the HTC keyboard is designed to put a period and two spaces when / if you hold the keyboard for too long. I haven't looked at the actual code to see how many milliseconds it is, but that is what is happening. Try to tap the space bar quicker and it should be fine.

Thanks for your reply, but thats not whats happening. I press space fast enough. I am aware of the fact that it puts out a dot if you hold it or tap it twice . It does not explain why it continues to make spaces after it makes the dot. It goes totally bananas

Its a setting.
I have a custom rom but im almost certain that the setting is a standard feature.
Its called "Add a space after dot" or equal and you should find it in the settings for input and text.
Good luck.

dicksisfontes said:
I have a custom rom but im almost certain that the setting is a standard feature.
Its called "Add a space after dot" or equal and you should find it in the settings for input and text.
Good luck.
Click to expand...
Click to collapse
I also know this is considered a feature, and I intentionally have it on. HOWEVER, there is often keyboard lag, where you can quickly tap on a key, and the software does not recognize that it was a quick tap and processes it as if you held it down for a longer period. With the space bar, you get the period + spaces. I frequently get the same effect on other keys, yielding numbers, etc instead what I wanted.
The keyboard lag is *awful* and I consider it one of the bigger usability flaws in the mytouch.

majoraccent said:
I also know this is considered a feature, and I intentionally have it on. HOWEVER, there is often keyboard lag, where you can quickly tap on a key, and the software does not recognize that it was a quick tap and processes it as if you held it down for a longer period. With the space bar, you get the period + spaces. I frequently get the same effect on other keys, yielding numbers, etc instead what I wanted.
The keyboard lag is *awful* and I consider it one of the bigger usability flaws in the mytouch.
Click to expand...
Click to collapse
Yeah i get that exact same thing. It is REALLY annoying the !#¤% out of me

Try using Super D, I get no lag on the key board and its a great 1.6 ROM. Its possible it could be a hardware issue, try going into the dev tools and click pointer location. See whats going on with your touch screen.

phatmanxxl said:
Try using Super D, I get no lag on the key board and its a great 1.6 ROM. Its possible it could be a hardware issue, try going into the dev tools and click pointer location. See whats going on with your touch screen.
Click to expand...
Click to collapse
I am using Super D at the moment . Turning the vibration feedback off helped somewhat, but in landscape mode it is still lagging a lot. Tried pointer location, and the screen seems fine to me

FYI, I switched off the predictive text input option on HTC_IME, which got rid of just about all of the lag. It works very well with haptic feedback now. Unfortunately, there's no spell check or anything, so you may have to pay more attention but it is still preferable I think.
The basic problem seems to be that the mytouch simply doesn't have the processing capability to run close to smoothly with all the advertised features, and we have to selectively disable options to try to get a usable product. It's a shame since android itself is quite nice.
I suppose another solution would be to go into the source for one of the keyboard packages and see if it could be made more efficient, but that may be pointless as soon as better hardware comes out.

[SOLVED; provisionally] New bug with 3.2.. ..'default app not set' road block?

Hi. I'm unsure if this is covered elsewhere. If so, please disregard.
After getting the OTA 3.2 upgrade (unrooted; obviously), I noticed a bug. If I had any applications that weren't set as the default app for a specific piece of functionality, then the option to choose which app to use no longer appears.
For example, prior to 3.2, if I clicked on a bookmark, I was prompted whether to use the default browser or Opera. I didn't set either to use as a default because I may use one or the other depending on the situation at the time since both treat pages differently.
Another example of this shows up when clicking on either the ASUS weather widget or the weather info on Beautiful Widgets. Again, clicking on the forecast for either of these will call up a browser page but since I didn't have a default one selected, the screen dims, but no option to choose a browser appears.
This isn't limited to the browser. I'm getting the same "dim screen, no option to choose" with other programs that had no default option set, such as movies. Prior to 3.2, clicking on an MP4 movie asked me if I wanted to view in the gallery or PowerAMP. Now.. ..nothing. Dim screen. Clicking anywhere or hitting 'back' returns to the screen without the file being played.
It seems any attempt to launch any file or in-app link that points to a link or file that is unassigned results with the same "dim screen" road block.
Anyone else experiencing this? or am I the only lucky one getting this frustrating bug?
Edit: Possible temporary fix...
Quick afterthought. It may be possible with some apps to set "use as default" for a specific file type in the app settings and this may fix this issue for myself and any others. Personally, I don't want to do this. I like being able to choose on the fly and would like this bug fixed. Still, if it's going to be weeks until a fix arrives, I may need to use this workaround (if it is even possible for all my affected associations) so I'm not standing still till a patch comes.
UPDATE:
While I can't be sure this fixed the problem, I undocked the tablet and removed both a 16GB MicroSD (from the unit) and a 16 GB SD (from the dock) and then re-inserted both memory cards and the tablet into the dock. After that, my links called up the association window again. I 'believe' it was reseating the tablet into the dock that corrected the issue, but ejecting and putting the memory cards may have been the answer. Note to self: check results after 'each' step.

Just tested this on mine and no I do not have this issue, I still get all the prompts for what to open stuff in be in links or videos from file managers etc

I just noticed this problem too. Very annoying, reverting to previous firmware...

I got this bug too. I tried the above solution as suggested but no luck. Then i tried another one from one of the threads here. It works!
http://forum.xda-developers.com/showpost.php?p=16100385&postcount=4

Hell, my bookmarks don't even open at all.
There is no pinch-to-zoom either.
Edit: tried the above & it did work how strange. I have auto rotate turned off.

Regarding this bug in the default program selection when trying to run videos or pictures from file managers. As D3StRuCtO posted the link to the "cant play videos in stock players" thread, nego_0 posted a fix for non-dock users and this is verified a working fix. Simply turn your TF 90 degrees to portrait mode and go through the selection process. it works. Go back to landscape mode and everything is good again... Thank you nego_0! If you have a dock like me, just undock the TF and go through the selection process in the file managers and it woked. Redock the TF and everything is good again. It is a weird bug and I never would have found the fix without this forum. Thanks again! Our members ROCK!
*EDIT*
I found other programs that were supposed to bring up the "complete action using" selection that would simply dim the screen and not give you the option to choose are now fixed as well. It didn't seem to be limited to pictures and videos.

Removing the dock and putting it back on seem to have solved the problem. Thanks for the tip!
OK I did some more tests: upon a reboot with the dock on, the problem was back. With the tablet in the "stuck" state, I removed the dock and the selection screen magically appeared.

I had this very same problem. No dock or SD here... Did the portrait - landscape rotation cycle and everything is solved now.
Regards.

This makes for a workaround, and I'm thankful for that, but I think the underlying problem is that while in Landscape mode, the OS won't go through the process of asking for a choice of browser, and you can't make the rotation with the keyboard attached. I went through the removal and rotation, and that was fine until I reattached the keyboard and was back where I started.
I had to remove it a second time, and this time assigned a default browser, then subsequently was able to operate properly with the keyboard back on. This problem is going to confuse the heck out of casual users, and ASUS will need to fix it pronto.

JoTeC said:
Regarding this bug in the default program selection when trying to run videos or pictures from file managers. As D3StRuCtO posted the link to the "cant play videos in stock players" thread, nego_0 posted a fix for non-dock users and this is verified a working fix. Simply turn your TF 90 degrees to portrait mode and go through the selection process. it works. Go back to landscape mode and everything is good again... Thank you nego_0! If you have a dock like me, just undock the TF and go through the selection process in the file managers and it woked. Redock the TF and everything is good again. It is a weird bug and I never would have found the fix without this forum. Thanks again! Our members ROCK!
*EDIT*
I found other programs that were supposed to bring up the "complete action using" selection that would simply dim the screen and not give you the option to choose are now fixed as well. It didn't seem to be limited to pictures and videos.
Click to expand...
Click to collapse
Thanks for the shout out! Im glad i was not the only one who had hit the dim screen default application bug.

nego_0 said:
Thanks for the shout out! Im glad i was not the only one who had hit the dim screen default application bug.
Click to expand...
Click to collapse
Unfortunally this was the first problem I noticed. It happens all over again when you shut the unit off and restart with the dock plugged it. I guess with this official thread maybe someone from Asus will notice it? Not holding my breath. Wonder if full factory datat reset will help. I've found when updating android on my phone tht helps wierd problems but don't want to have to go through all the re-setting up and downloading of my programs.
What a hassel. I guess when they officially begin supporting 3.2 over the phone line I can get them to resolve? Not holding my breath for that either.

I've been thinking about this further and think I might at least be able to point to the culprit (granted, in a 'shoot an arrow into the air' and you're bound to hit something manner).
Recently, ASUS made a change to the way the tablet behaves when docked. Specifically, in the way the auto-rotate functions while docked. Prior to this change, you could view your screen in portrait mode (even if docked) by turning the entire tablet + keyboard 90° or more. After the change, the screen locks at landscape oriented with the tablet in place. Flip it around now and it stays oriented (even upside-down).
With some applications, display boxes are written to start in a specific orientation which will then flip based on the current viewing angle. Since Android was (first and foremost) a phone OS (that uses portrait as it's main orientation), it may start most pieces of functionality such as display of the "choose desired app" dialog box in portrait mode but rotates it based on a call to the current device orientation status. However, I'm wondering if the OS can't reconcile that it is in landscape mode because auto-rotate has been turned off with the change ASUS made when the tablet is docked (making it specifically an auto-rotate issue), or if this change is blocking the dialog in another fashion due to the way ASUS programmed this functionality to communicate with the OS (making this a 'ASUS isn't playing well with Google' issue).
In short, this may be a bug relating to either a "auto-rotate / forced orientation" toggle, or a bug with the ASUS "lock orientation while docked" functionality.
It could also be related to the new "default size / zoom to view" 3.2 functionality mixed with a locked viewing angle.
Thoughts?
Edit: Just did a test. Rebooted the tablet (while docked) and the bug occurred; as expected. I lifted the tablet out of the dock but didn't change the orientation. I just simply lifted it up, then set it back into the dock. When I launched an html link, it now works. I know that some users (without docks) are able to fix this by simply changing orientation after booting. The process of unseating, then reseating may be providing a similar function as changing the orientation does with a dock-less tablet.

Just to say that, as stated by others, as soon as I rebooted the bug came back. I rotated it and the bug disappeared, but I sure hope that Asus solves this on a future OTA.
Regards.

CalvinH said:
Just to say that, as stated by others, as soon as I rebooted the bug came back. I rotated it and the bug disappeared, but I sure hope that Asus solves this on a future OTA.
Regards.
Click to expand...
Click to collapse
It is bit ridculous that the bug comes back aftrer a reboot. I guess with 3.2 we are supposed to reboot?

I'm not 100% sure about this but don't Android apps actually shut down and restart instantly when the orientation is changed?... so doing this restarts the Launcher?
And the same happens when removing and inserting into the dock? launcher restarts...
Try this... reboot in one orientation and test and try the other.. i.e. Boot in Portrait and see if the bug is there then change to landscape to see if that fixed it... then boot in landscape and test..

Possible rotation lag fix

Anyone experiencing this on EI22 ROMs, I suggest getting the Bubble Level app from the Market.
If in that app the bubble level graphic doesn't switch to the "line" version when tilting the device to an edge, you may have the same issue I did.
Tap Calibrate, Reset and then exit the app.
Go to the built-in Android Calibration in the Settings menu (under Display, toward the bottom). Try calibrating then with screen up (opposite of what many did with Froyo, but you can try that too if right side up doesn't work). See if your response of screen rotation gets quicker. It did for me.
The nice thing about this strategy is it doesn't involve anything difficult to do and seems to me a low-risk set of steps.

[TUT] How to Enable Swiftkey on HDX

The Keyboard Settings on HDX is hard coded for the Kindle Fire OS keyboard, but alternative keyboards *can* be loaded or sideloaded into a very confusing menu. This is how you get Swiftkey to work.
The steps should work for other keyboards as well. I've gotten it to work with Fleksy and Google Keyboard. YMMV.
1) Download and install Swiftkey to your HDX through Google Play Store (if you have hacked it onto your device), Amazon App Store, Aptoide or 1Mobile, or even sideload it. However you do it, install it.
2) Once you got it installed, run the Swiftkey app, which is also the installer. Keep going as far as you can until it tries to trigger the settings and so on. It probably will bring up Keyboard Settings, and you'll be utterly lost here.
3) Bring down notification, and go into settings (far right button, usually)
4) Go down to Language & Keyboard and tap it
5) Tap on "Keyboard Language" (should be 3rd one down)
6) Keep scrolling down the languages (and you'll see TONS) until you finally find Swiftkey, make sure it has a checkmark (if not, add it now).
Optional: Also enable any other keyboard you may have loaded. Beware that some keyboards appear here actually as a language. For example, Google Keyboard appears as "English (US)" if you have that installed, though Fleksy appears as itself.
7) Once you have checked all the keyboards you want to enable, scroll back to top
8) Tap "Default language", which is first choice, and you should get a pop-up of all the different keyboards/languages you enabled, and among them should be Swiftkey (or Flesky or whatever keyboard you put a check mark on in step 6) Pick your favorite keyboard now.
9) Hit BACK to go back to "Language & Keyboard" screen
10) Tap "Keyboard Settings" (4th choice?) If you had previously selected Swiftkey, this should bring up Swiftkey Settings, or perhaps the installer if you have not completed the steps like Sign into Google Plus to enable CloudSync. Complete any remaining steps in the installer.
Your new soft keyboard is now active! Enjoy!

I've actually done this several times using the swiftkey apk from my phone extracted from a titanium backup. Every time I have tried it though the nav bar on the bottom (portrait mode) or right(landscape) has covered part of the keyboard making it unusable. I may have missed it in one of the other threads but what needs to be done to fix this? Having a working swiftkey would be great as the stock keyboard is really slow on long press combos like numbers and sometimes doesn't even recognize the first one.

Indeed it's a bit annoying... The best I've been able to achieve is to set the keyboard size to the largest one and also select the extended keyboard option so that most keys are on top of the space bar... But still we need a fix on this one and I think the problem is on swiftkey 's side not recognizing the fireos bar...

Swiftkey has an undock setting. I activated that and just moved the whole keyboard up the screen further. Works fine for me.
Rich

dorpmuller said:
Swiftkey has an undock setting. I activated that and just moved the whole keyboard up the screen further. Works fine for me.
Rich
Click to expand...
Click to collapse
Where is this option located? I can't seem to find it.
*edit* Nvm, found it, haven't used Swiftkey in ages so forgot where the swiftkey icon was. For those unfamiliar with swiftkey, it's the second one from the bottom left. You can use this video as reference:
http://www.youtube.com/watch?v=eVeoy51IkME

glimmer00 said:
I've actually done this several times using the swiftkey apk from my phone extracted from a titanium backup. Every time I have tried it though the nav bar on the bottom (portrait mode) or right(landscape) has covered part of the keyboard making it unusable. I may have missed it in one of the other threads but what needs to be done to fix this? Having a working swiftkey would be great as the stock keyboard is really slow on long press combos like numbers and sometimes doesn't even recognize the first one.
Click to expand...
Click to collapse
Undock is your only option. It's easy in landscape, but almost impossible in portrait mode. You'll have to guess where's the swiftkey button and from there, undock.
I was about to suggest "arrow keys" but I realized Swiftkey hides the arrow key option on the tablets (WHY!?!?!?!)

kschang said:
Undock is your only option. It's easy in landscape, but almost impossible in portrait mode. You'll have to guess where's the swiftkey button and from there, undock.
I was about to suggest "arrow keys" but I realized Swiftkey hides the arrow key option on the tablets (WHY!?!?!?!)
Click to expand...
Click to collapse
Indeed I also thought of activating the arrow keys just to see it's not an option on tablets...
I don't like the undocking option as sometimes the undocked keyboard appears on top of the text field you're trying to type in, effectively blocking your view of the typed text...

Thanks for this post! I had really missed the language recognition ability of SwiftKey.
I haven't had any of the above problems due to the nav-bar covering the keyboard. Unless I update this post, you can assume I'm one happy guy
I installed Swiftkey from the 1Mobile appstore on a non-rooted device (Thor 7 inch, Kindle OS 4.5.5). There were 6 versions of Swiftkey available to install. The only version that worked for me was "Swiftkey Tablet Free," Version 4.2.1.202.

[HELP] Problem with multi touch nexus 4 lollipop 5.1.1

Good evening, can you help me? Every time I go to use the multi touch on some touch to the game, it still works, just can not use the multi touch simultaneously, For example when I try to walk and jump in a game, the character jumps, but stop the run, in photos I can use the multi touch quietly, does anyone know how to fix this?Another problem is that when I go into the play store, type a name of any app and if it appears a direct link to google play store simply crash. I'm using lollipop 5.1.1 please help me

GhostMk said:
Good evening, can you help me? Every time I go to use the multi touch on some touch to the game, it still works, just can not use the multi touch simultaneously, For example when I try to walk and jump in a game, the character jumps, but stop the run, in photos I can use the multi touch quietly, does anyone know how to fix this?Another problem is that when I go into the play store, type a name of any app and if it appears a direct link to google play store simply crash. I'm using lollipop 5.1.1 please help me
Click to expand...
Click to collapse
Is this a new problem on your phone?
Maybe a factory reset would help?

After replacement screen i believe, the problem of when I use the multi-touch and when I drop a finger both sort out, if I push a button and push each other and hold works, but if I let go of the buttons the two "disconnect" for example : if I run and shoot in a game, if I walk and pressing the shoot, he will ride and shoot normally, but if I try to get going and pressing 1 for 1 second to shoot, ride the will "lose the contact"

I've started to get a similar issue. I have developed a 'dead zone' in the top 3rd immediately above the centre of the screen. When scrolling the phone is registering a press on the screen and selecting links/icons instead of scrolling past them. Sometimes the phone goes loopy registering continuous presses along this line not allowing any other screen presses to be registered. I have enabled 'show pointer touches' in developer mode which shows the screen registering touches that I have not performed. Pressing the power button and then squeezing the sides of the phone resolves this temporally leaving me with the 'dead zone'.
Am I right in thinking that a replacement screen is needed?