Ive been noticing a problem with the Kaiser recognizing (or not recognizing) quick consecutive same key presses.
This happens on the keyboard as well as on the dpad.
ie... If im typing a word such as "ull" or "pass", if im typing at full speed the device wont recogize the 2nd consecutive letter.
Or if im pushing the dpad quickly up or down (not holding it down, but consecutive presses), it will also skip over some of my presses.
Has anyone else noticed this problem on their Kaiser's?
Thanks.
Yes I am having this problem and have to type slowly to get it to work reliably
there is a setting for key refresh rate and speed in the settings menu set them to as fast as they go also clear your stored words. I don't have this issue and type all day long!
How do you clear stored words?
For button settings, u have "Delay before 1st repeat" set to "Short", and "Repeat rate" set to "Fast"?
Thanks.
austinsnyc said:
there is a setting for key refresh rate and speed in the settings menu set them to as fast as they go also clear your stored words. I don't have this issue and type all day long!
Click to expand...
Click to collapse
Maybe you're not typing as fast as me
The only repeat settings I can find are under "Buttons" and that's just for the Up/Down control.
I don't see how clearing any stored words will help and if it does there's obviously something wrong with the software.
Have I missed something???
You can get it to show you suggested words based on the first x number of letters that you type. I never use this and found it was slowing my text input a helluva lot! Don't know why it's so slow on my TyTN II!!! On my XDA Mini which (supposedly) ran at half the speed the TyTN II does, I never suffered with slow-down.
This is only one of a few speed gripes I have with my lovely new Kaiser
Related
Hi everybody, my first message here
few days ago i got my new Qtek 2020i... but i have some problems with it..
1) sometimes (expecially when activly using) I hear single flicks(sounding very likly elecric discharges) from device...(even when sound is off)... last time i noticed that it sounded at the moment I quit program and memory it used was released... but sometimes it flics just when standing in cradle.... does anyone have same noisy sounds? or it's damaged device, and I should replace it?
2) I can't close dialing screen... I installed spb plus plugin which makes programs really close when you press X button.. it works, but it refuses to close dialing screen - when i press top rignt corner shortly - it blinks with phone screens I just used(exacly them - if I pressed on "quick call" button, then returned and clicked on history of calls and returned again - it will fastly show that 4 screens in that order) and returns to dialing screen again.... I can exit it only by holding top right corner button for 3 sec's or start button... but it still holds "phone" task in memory(spb plus shows it.... but there is now such task until I use phone for the first time after soft reset) - and if I use phone again - the number of screens I'll see on exit will increase and increase untill I make soft reset.... Of course I can always exit by long pressing the button... but it's annoying, and maybe there is another solution?... is that my software problem? or it's windows bug?
ps thanks for nice forum, I already found a lot of usefull info here =)
Hi
I don't know if anyone has experienced this or has a fix for it.
I picked up my Tytn II last week and I must say it's a cracking piece of kit. I seem to be experiencing a problem though.
If I say for example make a voice call and then hang up. I find that the word "phone" replaces the start menu in the top left hand corner of the screen. This wont default back to start and effectively makes the whole top row of icons inoperable. Ie battery status volume control etc. I have found this problem when using other apps, ie calendar, so it's not specific to just making voice calls.
The only way to get the top row of icons working again is to do a soft reset
All icons not on the top row seem to work ok (apart from keylock)
Any ideas ??
Massiv
Dont soft reset... just hit the power button to go into standby, then hit it again and the device will work again.
Hey presto it worked. Thanks for that. It's a bit annoying having to do that though.
Massiv
Its not a fix... its just a workaround.
When you end calls. Try first pressing the end call button, then the ok button.
I find this rather annoying, but don't know how to adjust it.
When making a call, sometimes you have to press through prompts like, 1, 2 , 3 etc. But after listening to the prompts, I find the phone screen to be OFF. I know that it's a power saving feature. However, it's quite annoying when to have press other keys to continue. I have to press the power button to get the screen to come back on.
Secondly, when connected to a call, the dialpad goes to the status screen by default. I have to change to keypad as well.
So here are my questions:
1) Anyway to change the amount of time before the screen blanks out while in a call?
2) Any other way to turn on the screen quickly without have to push the power button (which is difficult to push BTW)?
3) Any way to make the dialpad go to the numbers by default after a call is connected?
Thanks for any inputs!
Using WM6.1 ROM by Duty
anubus12 said:
I find this rather annoying, but don't know how to adjust it.
When making a call, sometimes you have to press through prompts like, 1, 2 , 3 etc. But after listening to the prompts, I find the phone screen to be OFF. I know that it's a power saving feature. However, it's quite annoying when to have press other keys to continue. I have to press the power button to get the screen to come back on.
Secondly, when connected to a call, the dialpad goes to the status screen by default. I have to change to keypad as well.
So here are my questions:
1) Anyway to change the amount of time before the screen blanks out while in a call?
2) Any other way to turn on the screen quickly without have to push the power button (which is difficult to push BTW)?
3) Any way to make the dialpad go to the numbers by default after a call is connected?
Thanks for any inputs!
Using WM6.1 ROM by Duty
Click to expand...
Click to collapse
KaiserTweak should solve some of your problems, if you have installed it.
http://forum.xda-developers.com/showthread.php?t=333898
tkalli said:
KaiserTweak should solve some of your problems, if you have installed it.
http://forum.xda-developers.com/showthread.php?t=333898
Click to expand...
Click to collapse
that utility doesn't change any of those settings.
anubus12 said:
that utility doesn't change any of those settings.
Click to expand...
Click to collapse
isnt that was the fast sleep and the sleep function in KT does??
Speaking of dialpads,
Do any of you guys having problems with inaccurate digit presses? I mean, I try to press 2, and 0 gets pressed instead, or other adjacent and non-adjacent numbers. Quite annoying really. Anyone experienced the same?
I bought a Touch Diamond recently.
But I can't resolve a problem with the fast dormont display during call function.
I tried to modify the setting in the following path:
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall
I change the DWORD Data from 1 to 0.
But after a soft reset, I still have the problem that screen turns off quickly during calls.
It bothers me when I need to use the keypad during a call
to enter ext. number or to follow a vocal operation.
Does any one have the solution here?
Thanks a lot.
Craig Shih
My problem is now solved. Any one who needs the solution can go to post#19 and post#29.
But it needs more tests and feedbacks because I don't know how it works for other roms.
No body in the diamond forum knows how to solve this problem.
Maybe this is a very very difficult problem to solve.
No one knows how to sovle it until now.
Hope a real master comes to help us.
diamond bugs
yes it's really sad to have a expensive mobile without a support even the htc don't have a solution what kind of support we had ??? lucky us we had a website like XDA developer to help us tnx to the dude who put up all the tweaks and update....try to flash the euro rom it will solve the prob.blank screen during call...
as soon as phone call is received, just press on joystick centre button shortly. Display will not go off then. Simple enough.
if before you'll make the call ypu'll take out the stylus, it won't go off, and it will automatically start a note.this setting is in phone option last tab...
remember: it goes to sleep the moment you hold it against your ear (or your hand or anything in the front).
if you set the registry right it will stay on as long as you don't hold anything against the front.
pskint said:
automatically start a note.this setting is in phone option last tab...
Click to expand...
Click to collapse
that's an additional and necessary side effect since he only needs the display to stay on so he can use the keypad without pressing extra buttons.
SecureGSM said:
as soon as phone call is received, just press on joystick centre button shortly. Display will not go off then. Simple enough.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried this method and then the call will be on hold immediately
until I press the central button again.
But it surely keep the screen on during calls though I have to press the central button twice.
pskint said:
if before you'll make the call ypu'll take out the stylus, it won't go off, and it will automatically start a note.this setting is in phone option last tab...
Click to expand...
Click to collapse
Thank you for your suggestion.
It's a good functionality for diamond users.
But sometimes I want to use the keypad during calls rather than to make a note with stylus.
For example when we call for some credit card toll free service,
we might have to key in ext. numbers or ID numbers or card numbers etc.
pietrucci said:
remember: it goes to sleep the moment you hold it against your ear (or your hand or anything in the front).
if you set the registry right it will stay on as long as you don't hold anything against the front.
Click to expand...
Click to collapse
Could you explain the registry for us?
Err... personal view..
If there is a solution.. it would be great.. but just in case, there isn't :
I have gotten used to it.
now if it is to enter extension numbers or whatever.. I just start off by pushing the center dial once. The key pad is there.. I get on with entering the ext. number or the Account numbers..
Same call - next time I have to enter other details, hit the center thing again.. and the key pad is there..
It's not that much of a hassle.
Of course a solution would be great, but even if there isn't, one does get used to it, in time.
why do you want it to stay on.
i noticed that when it stays on during a call, my ear is opening programs.
which i really do not want.
if you need to use the phone during a conversation just press the on button.
L o r d R a j said:
Err... personal view..
If there is a solution.. it would be great.. but just in case, there isn't :
I have gotten used to it.
now if it is to enter extension numbers or whatever.. I just start off by pushing the center dial once. The key pad is there.. I get on with entering the ext. number or the Account numbers..
Same call - next time I have to enter other details, hit the center thing again.. and the key pad is there..
It's not that much of a hassle.
Of course a solution would be great, but even if there isn't, one does get used to it, in time.
Click to expand...
Click to collapse
You are right, it 's not a big deal.
Maybe it's only my preference with mobile phone or somebody else's.
But if we can choose which way to go, that would be better.
i think there is a slotion please try
got this one now and it looks like problem solve for me
Originally Posted by minkol
I suggest this too:
HKCU\ControlPanel\Backlight\LightSensorPollingEnab le to 0 (default 1)
During call the light sensor can also switch the backlight off. This setting will that disable.
This registry setting will disable your screen from turning off when making a call:
HKLM\ControlPanel\Backlight\LightSensorPollingEnable set to 0
It disables the lightsensor so it doesn't react when you're putting the phone next to your ear.
It worked for me, so I hope it will work for you as well.
motin said:
got this one now and it looks like problem solve for me
Originally Posted by minkol
I suggest this too:
HKCU\ControlPanel\Backlight\LightSensorPollingEnab le to 0 (default 1)
During call the light sensor can also switch the backlight off. This setting will that disable.
Click to expand...
Click to collapse
Thank you.
I 'll try it right away and see how it works.
motin said:
got this one now and it looks like problem solve for me
Originally Posted by minkol
I suggest this too:
HKCU\ControlPanel\Backlight\LightSensorPollingEnab le to 0 (default 1)
During call the light sensor can also switch the backlight off. This setting will that disable.
Click to expand...
Click to collapse
Hello. That registry entry solved that problem, but still after a few seconds the light turns off, even if I set it to turn off after 5 minutes in the Power settings. Is there any registry "tweak" to increase the backlight duration during a phone call?
craig_shih said:
Could you explain the registry for us?
Click to expand...
Click to collapse
Yes I can. Look at this post, point 8: http://forum.xda-developers.com/showpost.php?p=2278799&postcount=1
This regkey is also mentioned a few times in this thread.
See also point 17 of that post.
Done.
This is what I did
HKLM\Drivers\BuiltIn\RIL\BatteryTimeoutInCall set to 0
HKLM\Drivers\BuiltIn\RIL\BatterySuspendTimeoutInCall to 0
HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall to 0
HKCU\ControlPanel\Phone Sleep to 0
HKCU\ControlPanel\Backlight\LightSensorPollingEnable to 0
That done..
Restart the phone (I waited for a minute or so)
Backlight remains on now.
Then, just for the hell of it.. went back into the registry and set back the default values for:
lightsensorpollingenable
Phone sleep
Fast dormant
Checked again.. still works.
If one or two people could confirm that this works, we could finally put a SOLVED thing to this nonsense and get it over with.
Hi, I am having an odd sporadic issue when texting, typing with the hardware keyboard. Occationally when I start to type and reach a word with the letter 'a' in it, pressing the 'a' key on the hardware keyboard selects all the text. I have to either back out of the text message and go back in (most of the time this works), or reboot the phone (rarely have had to do this lately, but initally when the problem started, this was the only way to fix it). Is there a setting somewhere that is causing this? Am I accidently hitting a key or key combination? Its pretty annoying, but thankfully doesnt happen that often. My wife has the exact same phone and setup, and has the problem as well.
Background info:
Droid 4, Stock rooted ICS
Using GoSMS, GoLauncher.
I've tried every "select" combination I can think of on my D4 to try to reproduce what you are seeing, to see if it's a stuck key or something. The closest I can find is Shift-UpArrow. This will select lines. If your text is less than a single line, this has the effect of selecting everything. Have you ever notice if it happens on multi-line texts? if so, does it select the entire thing, or only a single line? or parts of lines?
I know this isn't much help. But maybe this is a step in "a" direction? lol.
inspector_Gadget said:
I've tried every "select" combination I can think of on my D4 to try to reproduce what you are seeing, to see if it's a stuck key or something. The closest I can find is Shift-UpArrow. This will select lines. If your text is less than a single line, this has the effect of selecting everything. Have you ever notice if it happens on multi-line texts? if so, does it select the entire thing, or only a single line? or parts of lines?
I know this isn't much help. But maybe this is a step in "a" direction? lol.
Click to expand...
Click to collapse
Hehe, it definitely is a step. I cannot remember if it selects the whole thing on multi-line texts or not. I will check the next time it acts up. I can definitely say that I am not accidently hitting shift and up arrow, its for sure just pressing the 'a' key as part of a text message. The frustrating thing is that it does it randomly, and if I'm typing and I hit the a and it selects the whole thing and I dont notice, it of course replaces the entire selected text with whatever letter I type after the a.
Thanks for the help. I have seen this exact problem a few other places (google search), and there have been some replies, but none that have identified the problem, or offered a solution. I am hoping that we can get to the bottom of it. Keep the ideas and suggestions coming!
CTRL-A on most OS is a select all. I wonder if there is a "CTRL" key that can be accessed somehow? and if so, is it stuck, or getting stuck somehow?
inspector_Gadget said:
CTRL-A on most OS is a select all. I wonder if there is a "CTRL" key that can be accessed somehow? and if so, is it stuck, or getting stuck somehow?
Click to expand...
Click to collapse
I had not thought of the control-a possibility. It definitely is getting stuck, if that is the case, cause it doesnt stop after one keypress, I have to back out and go back into the sms again before it stops.
popssracer said:
I had not thought of the control-a possibility. It definitely is getting stuck, if that is the case, cause it doesnt stop after one keypress, I have to back out and go back into the sms again before it stops.
Click to expand...
Click to collapse
The CTRL key, as far as I'm aware, is the touch sensitive "menu" button. Is it possible that it's being "pressed" constantly?
Cheers,
Steve.
StevePritchard said:
The CTRL key, as far as I'm aware, is the touch sensitive "menu" button. Is it possible that it's being "pressed" constantly?
Cheers,
Steve.
Click to expand...
Click to collapse
Ah-HA! Ok, when I turn the phone to the side, if I 'accidently' bump the menu button, the menu comes up (the menu for gosms settings when you're in a text message) and, when i hit back to make it go away, and it does, and I start typing... VIOLA! I reproduce the problem. You nailed it sir. Thanks very much. Now that I know what its doing, is there a way to turn it off, or should I just be careful not to hit the menu button when I go into a text message?
Thanks again!
Popss
Edit: I did notice that hitting the menu button again does not make it go away... any suggestions there?
Mine started doing odd things like this as well as "y" launched YouTube "s" Google search ect..... I just FDR and that was the end...
Sent from my DROID4 using xda app-developers app