Related
(please delete the other thread)
N1 suffers from one simple but debilitating hardware limitations - lack of hardware buttons.
Since trackball clicking is rarely used, it would be nice to assign a different function to it.
The first function coming to mind has to do with the fact that the device is a phone -
make trackball into a "Send" button.
This is what it should do:
1) whenever not in the dialer app, clicking trackball should bring up/start the dialer.
2) when in the dialer app, and a phone number was entered, clicking trackball should dial the number.
3) when there's an incoming call, clicking the trackball should answer the call.
I know some people with arthritis who would kill for such an app.
Thanks.
If such an app. were to be created, how about the case where the foreground process requires the use of the trackball click? Then every time you clicked it, the phone dialer would load.
I also don't personally thing the Android APIs would allow such a global hook (w/o root), but I'm not the best dev. out there so I'll let the more experienced respond to that one.
jayshah said:
If such an app. were to be created, how about the case where the foreground process requires the use of the trackball click? Then every time you clicked it, the phone dialer would load.
Click to expand...
Click to collapse
Well, that's the whole point.
You mean like a game? So far, games might be the only programs where you HAVE to use trackball for functionality.
I think all other programs allow touch screen input in place of the trackball.
Since I never use the trackball for anything, and I've seen a number of comments with the same sentiment (ie "trackball is useless"), I'd gladly trade the entire trackball function (including moving the cursor with the ball) for the ability to have a hardware "send" button.
I'll personally pay 50 dollars to a man/woman who can make this work. Then they can collect the money from thousands of market goers who'd would prefer a useful hardware button over a useless one.
Just a small bump.
why is this in the development section?
/sarcasm
jesus people your right stuff like this should be posted next to / under/ above threads like Cyanogen and Amon_RA
And how would you handle the movement of the ball when it rolls? I find when in recovery, it doesn't take much for the trackball movement to register and overshoot the options I am aiming for if not careful. Obviously a sensitivity setting would be the recourse for such a dilemma but still...or were you thinking that anything beyond buttonOn (false function obviously) is ignored?
Technically you could go as far as to have the tracball pressed trigger the dialer. From there you can scroll to call log, contacts, favourites using the trackball and then scroll down if you so desire.
I do find it odd that the phone has this hardware button and rarely is it actually used.
I think being able to touch the trackball and force the phone out of sleep is a sound expectation for this phone...the fact it isn't there is odd.
just get a sense or blur rom, that fixes everything
PsychoKilla666 said:
just get a sense or blur rom, that fixes everything
Click to expand...
Click to collapse
hahaha...
in other news, plenty of people have no interest in senseUI
One more bump.
Someone should really write this program.
Using the trackball to bring the phone in and out of sleep would drain your battery. That trackball is way to easily pressed (ie in your pocket) to be of any use as that function, but I would love the phone/send function. Would be wonderful as I hate having a phone shortcut on my homescreen.
Would be willing to pay or donate as well.
APrinceAmongMen said:
Using the trackball to bring the phone in and out of sleep would drain your battery. That trackball is way to easily pressed (ie in your pocket) to be of any use as that function, but I would love the phone/send function. Would be wonderful as I hate having a phone shortcut on my homescreen.
Would be willing to pay or donate as well.
Click to expand...
Click to collapse
Thank you. One of very few people who seem to understand this problem.
Anyway, the community's reluctance to implement this feature is a seeming indication of difficulty to do it. Maybe Android OS isn't that flexible; or maybe it's just too new, so people haven't really learned yet how to do things with it.
After all, the Win Mobile OS has been around for ages, and sure enough, as soon my Sprint Touch Pro2 was released, I had an app to rebind all the keys to whatever function I wanted.
Perhaps, in the future, we will see an Android app like the one I want. But, to my greatest disappointment, it may be years...
bump bump bump
I'll bump it one more time.
Any progress with this feature?
Another month has passed...
Has any developer figured out if it'd even be possible to make an app like that?
Thanks.
Maybe I'm just an ignorant fool for having taken several days to figure this out, but I just realized you can move the text-prediction bar so that it's no longer blocking the "send" button on text messages.
Press and hold on any word that pops up, and you can drag it to another location on the screen. Mine is now pinned to the top of the keyboard, and the send button is now available to be pressed even if i don't select an auto-correct word. It does hide the "attach" button, but I rarely use that in SMS anyway.
Thought this might help.
EDIT: Well, I guess I am an ignorant fool. The change isn't permanent.. or at least I haven't found a way to make it permanent. I wonder what person thought it was a good idea to float the text prediction bar at some arbitrary spot that just so happens to block the most important texting button... I'm convinced nobody tests these things... But I digress.
I was excited about this until I did it and then got another text and the box was right back where it started haha
holywhitebread said:
I was excited about this until I did it and then got another text and the box was right back where it started haha
Click to expand...
Click to collapse
Yeah, same here. I edited the original post accordingly. It really astounds me how minor, yet stupid, the text prediction implementation is..
I switched to SwiftKey and never looked back. HTC's IME is nice for a stock KB.. but it's too large (because of extra row for arrow keys) and the prediction text blocking everything above the keyboard.
I wonder if HTC IME MOD is any better in these regards?
Diversion said:
I switched to SwiftKey and never looked back. HTC's IME is nice for a stock KB.. but it's too large (because of extra row for arrow keys) and the prediction text blocking everything above the keyboard.
I wonder if HTC IME MOD is any better in these regards?
Click to expand...
Click to collapse
I, too, am now using Swiftkey. It really has a great feel to it. Most of the time, it records every keypress. However I've experienced extreme lag from time to time, resolved only when i disable the keyboard and reenable it. Ever happen to you?
If your as annoyed with the senseui keyboard as I was I can highly recommend the gingerbread keyboard off the market. It is, unequivocally, fantastic.
I am using the gingerbread keyboard as well. Accidentally found out you can drag the space bar up to get the arrow keys then drag it back down to get rid of them. Handy little feature.
Sent from my ADR6400L using XDA App
Arrow keys are a huge time saver for me... I'll be checking out the Gingerbread keyboard...
Wow, gonna have to pay for this one... Gingerbread Keyboard is awesome
id like to put the word prediction bar transparent or make it desapear but keep the continuous input working on!
Hi Everyone
One of the great (IMO) features of the transformer is that when docked you can just bash away at the keyboard in the springboard to reveal results.
For example if I type "Jones" it would bring up contacts on the right with the name Jones
If I typed Engadget it would search google for that, all of this without me pressing a key
I loved it.
I took the plunge with CM10 and now if I choose to do this it chucks me straight into google now, which I don't mind except for this one problem...
I'm quite a quick typist so when, for example, I type "Engadget" what happens is that the first "E" gets inputted but then the cursor somehow goes to the left of it so I end up with this "ngadgetE"
If i do it slow i get way with it, but im so used to doing it quickly that it's doing my head in the search with the keyboard was one of the things of beauty with this system and or some reason it's just kicking me out each time.
If i've not explained this well enough I apologise, I'm just wondering if anyone else has had a similar problem and if they managed to fix it ?
Thanks guys and girls.
gsusx said:
Hi Everyone
One of the great (IMO) features of the transformer is that when docked you can just bash away at the keyboard in the springboard to reveal results.
For example if I type "Jones" it would bring up contacts on the right with the name Jones
If I typed Engadget it would search google for that, all of this without me pressing a key
I loved it.
I took the plunge with CM10 and now if I choose to do this it chucks me straight into google now, which I don't mind except for this one problem...
I'm quite a quick typist so when, for example, I type "Engadget" what happens is that the first "E" gets inputted but then the cursor somehow goes to the left of it so I end up with this "ngadgetE"
If i do it slow i get way with it, but im so used to doing it quickly that it's doing my head in the search with the keyboard was one of the things of beauty with this system and or some reason it's just kicking me out each time.
If i've not explained this well enough I apologise, I'm just wondering if anyone else has had a similar problem and if they managed to fix it ?
Thanks guys and girls.
Click to expand...
Click to collapse
Would someone else mind trying this as well PLEEEEAAASSSEEEEEE, just want to know if im the only one with the problem
Thanks
can someone please please just try this, it's driving me nuts, ive tried 2 different roms same problem always on the google now search
so if i type bbc
it comes out bcb
(the first b ends up at the end)
anyone else know a fix for this please
gsusx said:
can someone please please just try this, it's driving me nuts, ive tried 2 different roms same problem always on the google now search
so if i type bbc
it comes out bcb
(the first b ends up at the end)
anyone else know a fix for this please
Click to expand...
Click to collapse
I have this same problem... I feel like most people don't use the keyboard because it is so expensive. This is a major cripple of the device, if you ask me. I have been dealing with this for what feels like months, and just started looking for a solution. I am running stock firmware, and I assumed it was because I needed to perform a factory reset. Unfortunately, that had no effect whatsoever. Just caused a lot of wasted time on my part. I am considering CM10, but now I am weary. I also wonder if I would lose out on a bunch of hardware-specific drivers and whatnot. That tends to happen on the custom Android builds off of AOSP.
gsusx said:
Hi Everyone
One of the great (IMO) features of the transformer is that when docked you can just bash away at the keyboard in the springboard to reveal results.
For example if I type "Jones" it would bring up contacts on the right with the name Jones
If I typed Engadget it would search google for that, all of this without me pressing a key
I loved it.
I took the plunge with CM10 and now if I choose to do this it chucks me straight into google now, which I don't mind except for this one problem...
I'm quite a quick typist so when, for example, I type "Engadget" what happens is that the first "E" gets inputted but then the cursor somehow goes to the left of it so I end up with this "ngadgetE"
If i do it slow i get way with it, but im so used to doing it quickly that it's doing my head in the search with the keyboard was one of the things of beauty with this system and or some reason it's just kicking me out each time.
If i've not explained this well enough I apologise, I'm just wondering if anyone else has had a similar problem and if they managed to fix it ?
Thanks guys and girls.
Click to expand...
Click to collapse
Your mind can think faster then your fingers can keep up with. At least on the smaller sized keyboard of the Transformer. It's a symptom of ADHD, One that in fact I enjoy, as it lets me type faster then my coworkers, and I have busted tendons in my left hand.
Actually a lot of what is happening to you is that when you are typing, your fingers "glide" across the keys, and in that you inadvertently perform a differing function causing the curser to return to home. Remember you have 3 things going at once. Your brain typing, your fingers typing, and the keyboard trying to get it all to show up on the screen.
And yes life is REALLY bad when you have a studder. While I can say that 99% of us that have a verbal studder also have a dexterity studder to go along with it. Thank God for backspace.
MasterDecker said:
Your mind can think faster then your fingers can keep up with. At least on the smaller sized keyboard of the Transformer. It's a symptom of ADHD, One that in fact I enjoy, as it lets me type faster then my coworkers, and I have busted tendons in my left hand.
Actually a lot of what is happening to you is that when you are typing, your fingers "glide" across the keys, and in that you inadvertently perform a differing function causing the curser to return to home. Remember you have 3 things going at once. Your brain typing, your fingers typing, and the keyboard trying to get it all to show up on the screen.
And yes life is REALLY bad when you have a studder. While I can say that 99% of us that have a verbal studder also have a dexterity studder to go along with it. Thank God for backspace.
Click to expand...
Click to collapse
FYI, this is simply a bug with Google Now on the Transformer series... It might be that Google wasn't expecting so much lag to exist on a device when they coded it... The system definitely caches/buffers the keyboard input, because every letter pops up on the search--just the first one doesn't get inserted until the system catches up, (the cards load in Google Now.) The first letter isn't ALWAYS at the end--it just depends how long*you type.
I really hate what Google have done to the keyboard in Lollipop. The predictions have been changed for the current word to show suggestions that aren't what you are trying to type, (if you are typing accurately.)
On the face of it, this seems to be a logical decision. In practice though, your eyes have to keep going upto your message to check what you have just typed is correct. You then have to go all the way down to the space bar to get the next word prediction. :silly:
Under the old system, if you were typing accurately, you would just press the middle button without your eyes ever having to go up and find where you are typing. This would then prompt the next word prediction without ever having to look upto the message or down to press the spacebar.
Is there any way to get the Kit Kat keyboard into Lollipop. (Its a deal breaker for me and could influence the Moto X 2014 vs Nexus 6 decision!)
See attached Kit Kat and Lollipop. In the example, I'm trying to type, "The."
I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?
StringerE said:
I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?
Click to expand...
Click to collapse
It is also what I see in Lollipop. Whilst it seems logical, when you are swiping, you only tend to check the word when you have finished a swipe. In KK, this mean't always going to the suggestion bar and confirming which also mean't insert space and then mean't next word please. Your eyes need almost no movement.
In lollipop however, when you have finished the swipe, your eyes have to go all the way upto the text, find where you typed and check it is what you wanted, then go all the way down to the spacebar and press it to ask for the next word suggestion.
It just means you can swipe so much faster on KK than you can on LP as your eyes are having to work alot less. :crying:
For me, the L version seems to be better at determining what I'm trying to swipe without me having to check it. I usually go ahead and swipe out the 2-3 sentences I want in my text/reply/post/whatever and then go back and verify it says what I wanted to say. And I've found it has been more accurate on L than it was on KK. Any incorrect words I see at that point I click on and the suggested replacement is usually what I wanted. If I verified each word as I swiped it would definitely be slower.
In other words, I rarely select the suggested words. I just swipe out what I want to say without looking up and then go back and verify before sending. And it's typically pretty accurate.
Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.
kgry said:
Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.
Click to expand...
Click to collapse
I've had no problems with keyboard lag and I'm using 5 on the Nexus 7 2013, (Which is a much slower device.)
IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.
MrObvious said:
IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.
Click to expand...
Click to collapse
It's good that Google gave you the choice to switch back to the old keyboard look. I just wish Google would give me the option to switch back to the kit kat swipe functionality. I can't buy a nexus 6 until they fix this!
I faced the problem on android 5.0, did they solved on 5.1?
McGyver dei poveri said:
I faced the problem on android 5.0, did they solved on 5.1?
Click to expand...
Click to collapse
The keyboard still sucks in 5.0.2
I don't think 5.1 is out yet?
It's out but not for my note3... Only the LG keyboard is as fast and comfortable as this for me. A part the autocorrection problem, they also removed the option to remove the "change language button" it wastes space for nothing... Bah..
For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers
For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers
Click to expand...
Click to collapse
Exactly the problem I have. If Google don't sort it out in 5.1 I'm staying on kit kat for sure. I get what Google were trying to achieve but they need the option to do both kk and lollipop prediction methods.
Personally I hate it. I have had to type words like "complaint" dozens of times over even though my swiping technique hasn't changed because the software thinks I'm trying to type "composition". Now, mind you, I swipe over to the A and there is no A in "composition".
Any news from android 5.1?
McGyver dei poveri said:
Any news from android 5.1?
Click to expand...
Click to collapse
No change.
Argh!!! That really sucks. Looks like it's staying on kk for me. :crying:
Would be nice if someone could hack the Google keyboard :angel:
Just an update for people having the same issue as me in Lollipop.
On the Play store, there is an app called Jellybean Keyboard 4.3. :highfive:
This app pretty much gets around my issue with the Google Keyboard and has worked fine for the last week I've been testing it with only a few niggles:-
- Emotions requires a separate download.
- When the app updated a few days ago, it forgot what it had previously learned.
I still dont understand why Google Keyboard cant contain a tick box in the settings entitled, "Include typed word in suggestion box in Lollipop." :crying:
Oh dear god. I tried Lollipop once on my N4 - it was awful. Now I plan to switch to 5.1 and see how it is one more time (and check if there is better battery life) but that keyboard abomination still scares me and its sad to know that it still persists...
However I'll try to live with that - at least for one day - cuz I wanna try EuphoriaOS tommorow Maybe I'll try to install Google Keyboard from 4.4.4... Somehow.
Just go for the jellybean keyboard as above. :angel:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.