Related
Hi all,
If this is in the wrong place, i apologise unreservedly. It's really a question about android generally, but it's a question which has arisen specifically due to the behaviour of many of the various android builds available for the HD2, so i figure this is a sensible enough place to put it.
Enough waffle; the question:
Given the screen freezing issues associated with the gsensor/autorotate (i know this is at least relatively widespread as it's mentioned in many of the rom threads, and at least one dedicated thread), is there a setting/widget/app that can be used to force-rotate the screen and lock it in that orientation, if auto-rotate is disabled? For example, if i know i'm about to launch my browser or texting app, i can flip to landscape.
Many thanks all!
_tangent said:
Hi all,
If this is in the wrong place, i apologise unreservedly. It's really a question about android generally, but it's a question which has arisen specifically due to the behaviour of many of the various android builds available for the HD2, so i figure this is a sensible enough place to put it.
Enough waffle; the question:
Given the screen freezing issues associated with the gsensor/autorotate (i know this is at least relatively widespread as it's mentioned in many of the rom threads, and at least one dedicated thread), is there a setting/widget/app that can be used to force-rotate the screen and lock it in that orientation, if auto-rotate is disabled? For example, if i know i'm about to launch my browser or texting app, i can flip to landscape.
Many thanks all!
Click to expand...
Click to collapse
1. That is a very good idea and might fight the freezes caused by autorotation.
2. I want this anyway, because I want to be able to force a specific orientation when lying in bed. With autorotation the screen usually rotates the wrong way...
So any help would be appreciated!
+1 on this ^
Sent from my HTC HD2 Using the XDA App on ANDROID 2.2
MAMeingast said:
1. That is a very good idea and might fight the freezes caused by autorotation.
2. I want this anyway, because I want to be able to force a specific orientation when lying in bed. With autorotation the screen usually rotates the wrong way...
So any help would be appreciated!
Click to expand...
Click to collapse
I have this problem also
I've tried googling for an app of this sort, but so far no joy. Might try and create one myself. Never written something for android before, but software development is my day job, so i'd be willing to give it a crack. Crazy-busy at the moment though, so not sure when i'd get time
how about assigning a longpress-homekey something like rotate by 90° each time it is longpressed?
something like longpress-endkey menu in windows mobile devices.
shouldn't be that much of a problem to write such a program with appinventor?
I have Switch Pro Widget (it's a customizable energy control widget). One of the shortcut buttons enables/disables auto-screen rotation, so that does the trick for me.
My sister lost her vision last year at the age of 24 due to diabetic retinapothy. She is missing be able to text message, facebook, celeb gossip... you know, the important things in life We initially bought the Droid X for her, but It's going back in exchange for the Droid 2, which should be here on 9/9/10.
Problem with the X is the Android Eyes Free Shell and the Talking Dialer make use of either a trackball or a directional pad. The Droid X has neither. It's also difficult to navigate pretty much everything blind without a d-pad. Should of thought of that earlier. Oh well, the exchange process is very easy. The Android Eyes Free team developed the software around the Nexus one i assume, which has a trackball. Personally i think a d-pad is better for a blind person, as you can press down once to go down once. A trackball you might go down 2 or 3 depending on how much you rotate it.
I'm going to be updating this thread with our progress as well as what steps we took along the way. Hopefully this will end up being helpful for someone else in a similar situation. Blind people DO use the internet (even youtube!).
Here are the initial changes I want to make:
Locating Touch Sensitive buttons
I will go to a craft store and find something to put below the 4 touch sensitive buttons on the front of the phone, this way she will be able to find them. Im thinking 4 drops of some puffy glitter glue or something to that effect. Being diabetic she's also lost somesensitivity in her fingers, so something with texture will be needed.
Removing the Lock Screen
Slide to unlock is basically an impossible task for a blind person. The Droid 2 uses the stock vanilla lock screen I believe, does anyone know how to remove it? I could potentially replace it with a "shake to unlock" or whatever, and ideas here are appreciated.
Answering the phone
Again, here slide to answer isn't going to fly. Does anyone know: If you slide the keyboard out while the phone is ringing does it answer the call? Most slider phones I've seen operated like that, I'm hoping the Droid 2 does too. She will also have a bluetooth headset which should make it easy to answer, but if your blind trying to find your bluetooth headset in time to answer the call can be a problem, so i'd like her to be able to answer the phone without a headset as well.
Hanging up the phone
Can you slide the keyboard shut to end a call? What happens if your on a call and you slide the keyboard out and then closed, does that hang up the call? Another solution would be to make it so the power button hangs up the call, surely it can be remapped do that. Or is there an end call button somewhere on the hardware qwerty?
Ok, those are the first major things. Actually dialing a call is no problem once we get past the lock screen issue. She can double tap the home button to launch the voice dialer, or she can use the Android Eyes Free "Talking Dialer" to dial a number with her finger using swipe motions. It's pretty neat actually, give it a try if you haven't already. The Eyes Free Shell and the Moto Voice Command will take care of pretty much everything else.
Thanks in advance for your help!
I can confirm that the Droid 2 does NOT answer when sliding the phone open and does NOT hang up when sliding closed. Just tested this.
Edit: forum.xda-developers.com/showthread.php?t=762101
View that thread and search the app "no lock" in the market. Seems to do what you are looking for in the marketplace. You may also want to contact the developer to see about source code or see if it was a .apk that was removed.
Also in response to the glue idea:
I would test on another device because the screen has to be able to sense your impulse as well because it wont trigger unless it has a touch by a human hand. My guess it it reads the electronic pulse by the skin and that is how it picks it up.
about the unlock screen, I can say is once you do it enough times you know where is on the screen, I usually unlock mine while its not even all the way out of my pocket, also it vibrates when you touch the unlock area and it vibrates again as you pull it to the right...hope this helps
I don't have an Android phone yet, but I've seen a nice replacement for the stock locker, called WidgetLocker. You can modify it a lot (add your own apps, widgets etc.) but the most important thing for you is that you can move the unlock slider down to the bottom of the screen so it would be easier to unlock it.
Of course, the best solution is to remove completely the locker, but I don't know whether it's possible, so I'm just giving you another option
Kamill said:
I don't have an Android phone yet, but I've seen a nice replacement for the stock locker, called WidgetLocker. You can modify it a lot (add your own apps, widgets etc.) but the most important thing for you is that you can move the unlock slider down to the bottom of the screen so it would be easier to unlock it.
Of course, the best solution is to remove completely the locker, but I don't know whether it's possible, so I'm just giving you another option
Click to expand...
Click to collapse
This page has been a big help: http://eyes-free.googlecode.com/svn/trunk/documentation/android_access/basics.html
Above link talked about No Lock, an app on the market that removes the lock screen. Although it turns out she is actually able to unlock the phone blindly, but it usually takes her a few tries. For now we are going with no lock...
Also the Droid 2 has an option in the Accessibility page to enable "use power button to end call" so that has been a big help.
So far the biggest problem with the Droid 2 is the keyboard really sucks for a blind person. The navigation keys are kind of awkwardly placed, and the keys are very flat. I wish I would of known about the LG Ally, as the appears to be the best Android phone for a blind person. Has physical buttons on the front to start/end calls, and the keyboard is WAY better (for a blind person anyways). Unfortunately Verizon only lets you exchange a phone 1 time, and we already bought the Droid X. So looks like I'd have to sell the Droid 2 and buy the LG Ally on eBay. Not sure if we are going to go that route.. might just try and make the best of it with the Droid 2.
I have a LG Ally wits a protective rubber case, invisible shield screen protector, and 2 batteries which I'm not currently using. I'll do a straight up trade for your Droid 2.
Sent from my DROID2 using XDA App
Made my account to reply to this (And because I got my Droid 2 2 days ago). Will be watching this thread. My son is 2 and nearly blind. We are exploring any and all ways to work around it. I'm currently learning braille so I can teach him, and looking into how to make phones and computers more usable for him. Hopefully your sister handles what's happened well and finds ways to keep up her life, goals, and hobbies
Thanks for posting this. Good luck with the project and keep us updated, please!
Need some help here too
Hi there,
This seems to be the only forum that I can find on this subject. I will definitely be checking out the LG Ally but I'm also looking at the Droid 2 Global (which my partner has bought for himself and I have been testing out).
I am a blind person with little vision and I have to find a smart phone that works for me, as I have hit the point where I need to access my work email, work calendar, and browser functions do be more efficient and effective.
The blackberry is out, as it doesn't work for blind people through Verizon.
The IPhone, though just coming out from Verizon, does seem to have a great VoiceOver application which works great for a blind person. However, I'm not sure I'm patient enough to type without a keyboard--though it is possible for a blind person to use it.
Your points about the LG Ally are helpful for me. Does it have an accessibility application like the Droid 2 Global?
In testing out the Droid Two Global, I have enabled the "accessibility application" and checked the read out checkbox in the settings. It has abled me to see most stuff and some of the pieces you put up on the post will help. What I am struggling with is the following:
When I access any part of the browser application, it doesn't read the page of the web site or any of the links. I'm wondering if there are key combinations I am not femiliar with that would make this work or does it do it at all?
Also, the calendar is not reading things to me as well. Any ideas?
In general, is there a button that I can press, that will get it to repete something or to read a screen. I currently am just arrowing back and forth to choose something. I also can hit the OK button when typing a message to read what is in the edit box.
The last issue, though I think it would get much easier as I used it, is that to dial just a phone number seems to take a bit longer. But, I just tried using the voice dialer and it quickly got much easier. lol
I also wonder if the Accessibility application is the only one you are installing. Should I be installing something else to give me more functionality
Sorry for the long-winded questions but I really can't seem to find other assistance on this.
Thanks,
Jeremy Grandstaff
614-519-3026
Hi Jeremy,
I think you will get the best answers to your questions on Google's eyes-free group (I'm not allowed to post outside links on this forum, or I would have given you the URL).
On that list many blind Android phone users report accessibility issues and workarounds, and the list is monitored by Google's Android accessibility developers. Android web accessibility is indeed still very limited, as is text editing support.
Best regards,
Posted my question also to the eyes-free group
Thanks for the reply. I did post my message to the Google eyes-free group, but felt I would get a fuller response here as well.
I'm not sure if it has something to do with SMOLED in general, or if it's particular to the Nexus S, but I'm noticing oddities with the screen. Can't be sure if it's software related, or if it's hardware related.
There are two things. One, it sometimes doesn't register presses, even when an icon is clearly pressed; the orange highlight that surrounds an icon is clearly seen but it doesn't launch the app. It requires a second touch. I'm guessing this is mostly software related, but either way, it's disappointing to see Android like this (or, if hardware related, sad to see SMOLED like this).
The 2nd thing is, the screen seems problematic for the complete opposite reason sometimes. Has anyone ever hovered their fingers over the screen without actually touching it? Sometimes it'll register presses this way. I'm guessing this is hardware related? Either way, I have no doubt this causes unintended screen presses, and might go a long way in explaining typos and frequent errors that occur when typing quickly where your fingers glaze over the screen (like I often see double letter hits, like tthis or thiss - very annoying).
Not sure what the deal is, whether it's software or hardware contributing to these two oddities/problems - or a combination of both. Either way, these two things can make the Google Android experience feel second rate.
Additionally, I think this goes a long way in explaining my frustrations with typing on Android. Missed space bar presses are particularly frequent, resulting in words likethis; while other times, double hits occur, per my example above (like tthis or thiss). Again, it detracts from the overall Android experience and can be frustrating when thumbing out long messages.
The first issue might be related to the Launcher you're using. Are you on stock launcher or did you install something else like ADW or Launcher Pro? If you're on a third party, try it back on stock, or dig into the settings for your 3rd party launcher and see if there are tweaks you can turn on/off that might impact it. I know ADW has a "keep in memory" toggle; stuff like that is what I'd play with.
The other problem is something I've seen several people mention in here. I'm not sure I notice it or not, BUT, I just read this interesting article yesterday, which suggests to me that the screen is ultra-sensitive to touch. The article authors are amazed that they can use the back of their fingernail, or even wear gloves and still register touch on the screen. Other phones aren't so sensitive.
It seems they did something to increase the capacitive touch sensitivity, and perhaps a bit too much. Hopefully it can be software fixed.
The NS is such a lovely device, but it's got it's fair share of quirks, both hardware and software that really mar the experience for many. I love the phone, but am still considering returning it when my 30 days is almost up.
distortedloop said:
The NS is such a lovely device, but it's got it's fair share of quirks, both hardware and software that really mar the experience for many. I love the phone, but am still considering returning it when my 30 days is almost up.
Click to expand...
Click to collapse
I agree.
As for the launcher, I am currently using ADW because there are a slew of glitches and issues with the stock launcher, including the unresponsive issue I wrote about in my OP. ADW Launcher is unquestionably more reliable, smoother, and stable.
It's unfortunate the experience with the Nexus S can be so polarizing: sometimes the screen is not responsive, and other times, too responsive.
And I have to reiterate, the experience typing on this phone (and on Android in general) remains a particular sore spot for me.
distortedloop said:
I'm not sure I notice it or not, BUT, I just read this interesting article yesterday, which suggests to me that the screen is ultra-sensitive to touch. The article authors are amazed that they can use the back of their fingernail, or even wear gloves and still register touch on the screen.
Click to expand...
Click to collapse
No kidding. I don't have to actually touch the screen at all. Just hovering the tip of the finger 0.5mm over the screen is enough. Which is not really a problem, because it's quite difficult to do that.
I have found the same issue with the screen, it is very sensitive to touch. As for the bad selection and typing errors, I think that is more more likely software related, try a different keyboard?
Sent from my Nexus S using XDA App
Corvidd said:
I have found the same issue with the screen, it is very sensitive to touch. As for the bad selection and typing errors, I think that is more more likely software related, try a different keyboard?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I'm currently trialing Swiftkey. It is impressive the few times it works to perfection, but this is usually a rare occurrence. More often than not, I'm still having to type out my words, however, perhaps it's still "learning" how I type. For now, I feel like the experience is actually slower than manually thumbing out messages because you're so busy concentrating on picking the correct predicted word. In some ways, it's counter intuitive to messaging quickly. I have until the end of the month before the trial expires, so we'll see if the experience is improved.
Prior to that, I was using either stock keyboard, or Smart Keyboard Pro. Both have their positive and negative issues, but those two offerings are as good as it can be on Android, it seems. Which is to say, it's disappointing. I have many typing woes. I have to say, the typing experience pales in comparison to typing on iPhone/iPod touch devices. I can type far more confidently and smoothly on an iPhone than I can with any Android device I've used so far. I'm hoping, one day, when Blindtype is implemented, this will change.
I didn't like swiftkey, and don't understand its popularity, having to check the scrolling bar for which word i wanted slowed me down. I agree that the typing accuracy on an iPhone is superior to android devices, there are many things I don't like about the iPhone keyboard but the accuracy is very good.
Have you tried Swype? I believe the beta is now open to all to try, google it, as its not in the market. Failing that, apps like Shapewriter (when it becomes available again) and SlideIT keyboard are other similar options. Or if you want to go all-out weird with text input, try 8pen.
i found the same bugs
and my guess it has to do with the Concave design, that throws off the screen calibration.
on the SGS, the touches are 110% accurate
you just hover your finger on top, and the work
Corvidd said:
I didn't like swiftkey, and don't understand its popularity, having to check the scrolling bar for which word i wanted slowed me down. I agree that the typing accuracy on an iPhone is superior to android devices, there are many things I don't like about the iPhone keyboard but the accuracy is very good.
Click to expand...
Click to collapse
Agreed. However, I'm trying my best to give Swiftkey ample opportunity to grow on me, and as I said, when it actually predicts your words accurately, it's quite intuitive, but this happens rarely. Most of the time it guesses incorrectly and you end up thumbing in almost all the letters to a word anyway. Swiftkey slows me down too and I, ironically, end up taking longer to type out messages. Like you, I'm too busy making sure it's predicting correctly the next words I want to say. In many ways, it's counter-intuitive.
And it's a shame Google didn't set itself apart from Apple's keyboard. They could/should have included custom auto-corrections, etc.
Have you tried Swype? I believe the beta is now open to all to try, google it, as its not in the market. Failing that, apps like Shapewriter (when it becomes available again) and SlideIT keyboard are other similar options. Or if you want to go all-out weird with text input, try 8pen
Click to expand...
Click to collapse
Thanks for the suggestions. Yes, I forgot to mention I have the Swype Beta. Swype is quite fun and often impressive, but like Swiftkey, I find it cumbersome when I'm trying to type 'personal' words like unique names of places, or uncommon lingo and words, etc. Plus, when you start getting into long words, Swype becomes difficult to track. Perhaps I just need more practice, but ultimately found it slower than thumbing it out. I have tried a few other options, like the one where the keys change sizes depending on predictions, and even 8pen (novel, but no thanks), but nothing seems capable of accurately mimicking the iPhone/iPod Touch typing experience. Anyone who has typed extensively on both platforms will know the difference.
I would just like to be able to thumb out messages minus the odd errors and mis-presses/unregistered presses, or the overly sensitive presses. Smart Keyboard Pro remains the best choice, in my opinion, but even that has hiccups and my aforementioned problems. It's probably a combination of software and hardware that is contributing to my typing woes.
Blindtype, please hurry.
I don't have problems with it not registering presses, but it certainly is sensitive. Depending on conditions, you can register a press by hovering your finger 1-2mm off the screen surface. This has rarely bothered me, but if you keep your fingers very close in while you're typing, yeah, I can see it being really problematic.
EDIT: Actually, Android Central posted a short article and video just this morning about how you can use your Nexus S with certain types of gloves on in the winter cold because of this.
zorak950 said:
I don't have problems with it not registering presses, but it certainly is sensitive. Depending on conditions, you can register a press by hovering your finger 1-2mm off the screen surface. This has rarely bothered me, but if you keep your fingers very close in while you're typing, yeah, I can see it being really problematic.
EDIT: Actually, Android Central posted a short article and video just this morning about how you can use your Nexus S with certain types of gloves on in the winter cold because of this.
Click to expand...
Click to collapse
Right, you are. I mention about the hovering finger thing in the OP.
AllGamer said:
i found the same bugs
and my guess it has to do with the Concave design, that throws off the screen calibration.
Click to expand...
Click to collapse
But my understanding is that the actual touch screen itself isn't curved...?
onthecouchagain said:
But my understanding is that the actual touch screen itself isn't curved...?
Click to expand...
Click to collapse
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
zorak950 said:
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
Click to expand...
Click to collapse
Yes, that makes sense.
Not sure if I'm liking what I'm hearing. If the screen is indeed too sensitive and is the cause of my typing woes, I don't suppose there's a way to dial it down via software, is there?
onthecouchagain said:
If the screen is indeed too sensitive and is the cause of my typing woes, I don't suppose there's a way to dial it down via software, is there?
Click to expand...
Click to collapse
I don't know enough about how the technology works to answer that authoritatively. I'm curious too, though.
onthecouchagain said:
The 2nd thing is, the screen seems problematic for the complete opposite reason sometimes. Has anyone ever hovered their fingers over the screen without actually touching it? Sometimes it'll register presses this way. I'm guessing this is hardware related?
Click to expand...
Click to collapse
I've had this happen to me a couple times. I could see how its annoying, but I'm coming from a nexus 1 where you could mash the screen at times and nothing would happen so its nice to have a sensitive screen.
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
distortedloop said:
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
Click to expand...
Click to collapse
I agree. Voice input is very good with the S, much better than it was with the N1.
Smart keyboard pro is also a good one.
distortedloop said:
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
Click to expand...
Click to collapse
Yes, I've attempted to use Voice Actions, especially while driving. Usually it gets what I want to say correct, but unfortunately, it doesn't always get the person I'm trying to send it to correct. In fact, it never does. Same is true for when I'm not driving. So I end up having to cancel the command and type it out anyway.
I bought Better Keyboard long ago. It was one of the first third party keyboards I tried. I found the experience atrocious (at the time, it lacked true multitouch. If you think stock keyboard missed letters... you should try BK!). My understanding is that multitouch is implemented now, so perhaps I'll give it another try.
Edit: Also, Smart Keyboard Pro offers touch points and calibration to help you see where you mistype and to calibrate it to your typing style. These features help, but there's no mistaking that the phone (softward or hardware?) often misfires or misses presses altogether. Problems that appear like tthis or thiss or whenever it misses a space bar press (despite the space bar clearly being highlighted on the keyboard) resulting in words likethis are far too frequent and have nothing to do with pressing accuracy.
zorak950 said:
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
Click to expand...
Click to collapse
exactly... too much empty space in between, that's why the areas around the edge at the bottom are harder to register
When I got my transformer I immediately felt that browsing on it was a little uncomfortable when compared to the control I have on a desktop computer. I've noticed one poorly executed function was the PC equivalent of a "mouseover" or "hover" function. It made opening hover menus in a browser or controlling a flash video player a bit awkward, although still functional.
I've recently stumbled upon on 2010 article on why a Flash developer believes that flash would not work on the iPad, but many of the points that he makes are very valid given the implementation of flash that we have on our transformers.
http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/
I was just wondering if this was something you've all noticed and perhaps if you have your own ideas as to how a mouseover functionality could have been better implemented in android.
Also, I've once tried to bring this up in another topic which ended up getting closed, so let's try to keep that from happening.
Thoughts?
Multitouch. Tap with 2 fingers to "hover".
Sent from my Transformer TF101 using Tapatalk
I think that a double tap would be a good solution for something like bringing up flash player controls without pausing the video.
What about scrubbing the video? For instance, with youtube you can use your mouse and move it (without clicking) along the progress bar while being shown the exact time in the video that you are currently pointing at. This obviously makes rewinding and fast forwarding much easier on a computer. I suppose on a tablet you would double tap and then drag your finger, as per this implementation?
EDIT: Wow, I'm sorry I totally misunderstood. You actually mean't using two fingers as opposed to double tapping with one.
LeoBloom. said:
When I got my transformer I immediately felt that browsing on it was a little uncomfortable when compared to the control I have on a desktop computer.
Click to expand...
Click to collapse
I'll be brutally honest. You've got what I like to call not-used-to-something-that-is-new syndrome.
I'm sure when the personal computer first came out, people were crying left and right that typing on the computer was uncomfortable compared to the typewriter. In fact, if you go back long enough, I'm sure people were whining left and right that the page turning book format was uncomfortable to read compared to the scrolls. Heck, why stop there? I'm sure writing with ink was really awkward and uncomfortable to those who were used to the chisel and hammer.
The fact of the matter is every time a new technology came up, there would undoubtedly be resistance to the change. I have no doubt that there were arguments against Gutenberg's invention (the printing press).
I say the advantages of the tablet far outweighs the disadvantages. And please don't start arguing that the tablet could never replace your pc. No one is making such claim.
That was unnecessary.
The question here is how to make the "hover" functionality more intuitive.
i think a multitouch or swipe gesture would be the best option.
for example with the mousover menus, if u could quickly swipe across said menu to have it show the options.
not sure if its viable but who knows
or even a double tap. tap once to open the menu, tap again to select an entry or go to the main link
The problem is that a multitouch would register as a zoom function, not a hover function.. Computer analyses aren't good enough to tell the difference between two points of contact with relatively stable distance between them vs two points of contact moving away (because it's sensitive right now..?).
im using an external mouse really like it looking forward to ics for no more keyboard lag
i hope at least
also i would like a scrolling in facebook chat and pictures so you can see comments
p.s typing from it right now
I am using Logitech bluetooth keyboard with touchpad [designed for PS3]. For now it's the best solution for me.
o1d8oy said:
I am using Logitech bluetooth keyboard with touchpad [designed for PS3]. For now it's the best solution for me.
Click to expand...
Click to collapse
are you havin keyboard lag?
i mean if like on facebook it doesnt respon as fast a computer
just checkin if the keyboard is problem or honeycomb
All I have to complain about is XKCD in Google Reader (app), and there's probably an app or greasemonkey script for this already.
Sent from my Transformer Prime TF201 using Tapatalk
Flash the KRAKD Rom no more keyboard lag
DESIRE HD using ER3BUS ASUS TRANSFORMER on KRAKD
You will find that as more web developers and designers switch to HTML5 and CSS3 (which the stock android browser already supports btw) it will be much more of an experience like a desktop computer. In fact, hover effects implementing CSS3 currently support mouseovers on our transformer. the hover transitions work pretty dang well actually
Sent from my Transformer TF101 using xda premium
Spidey01 said:
All I have to complain about is XKCD in Google Reader (app), and there's probably an app or greasemonkey script for this already.
Click to expand...
Click to collapse
Yep: https://market.android.com/details?...1bGwsMSwxLDEsIm5ldC5ieXR0ZW4ueGtjZHZpZXdlciJd
Click the title of the item in google reader and it opens in xkcd viewer, and there you can click on the cartoon to get the hover-over.
Yeah its clearly not good, I also frequently miss a keyboard with cursor keys to move around in an input field.
daners85glacier said:
You will find that as more web developers and designers switch to HTML5 and CSS3 (which the stock android browser already supports btw) it will be much more of an experience like a desktop computer. In fact, hover effects implementing CSS3 currently support mouseovers on our transformer. the hover transitions work pretty dang well actually
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
How exactly is the "hover" functionality implemented on the transformer with HTML5 and CSS3, in terms of how the user is able to call on the function?
Yeah, I'm trying to encourage someone who's a developer on a web software I use quite often to add the clickhover property to the default theme instead of pure hover. Not only does that enhance browsing on tablets, but it also supports a11y.
yes, mouse-over or the lack of it is a real pain in the ***. I use Opera Mobile and browsing websites that use mouse-over navigation without the dock is really annoying.
is there a fix/workaround/touch-combination to get the mouse-over effect working?
The problem is that a multitouch would register as a zoom function, not a hover function.. Computer analyses aren't good enough to tell the difference between two points of contact with relatively stable distance between them vs two points of contact moving away (because it's sensitive right now..?).
Click to expand...
Click to collapse
This is false. There's nothing magical going on here, a touch UI is only as good as how it's programmed.
Two points of contact with stable distance CAN be discerned from two points moving away. For example a naive method to do this would be to store the last N number of touched coordinates per some time slice in the form of a recency list and then perform some minor arithmetic operations on them to determine the delta and make a reasonable assumption as to whether movement is occurring. It might be harder to discern movements where the quantity is similar to each other but where one quantity is essentially zero movement and the other is any movement, this is not so difficult to do.
d3l1 said:
yes, mouse-over or the lack of it is a real pain in the ***. I use Opera Mobile and browsing websites that use mouse-over navigation without the dock is really annoying.
is there a fix/workaround/touch-combination to get the mouse-over effect working?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21270831&postcount=30
refer to point number 3
Hi...new to this forum, so advanced thanks to all the tips, allowing me to give my encore new life.
Running CM10.1.2, stable build. Downloaded a stylus writing app (Papyrus), since I thought I could use my Nook to take notes at work. Issue here is that the stylus I bought works fine on my friend's Ipad, but I can't write worth a damn on my screen.
I have read a lot of threads on capacitive styli, and have some on order, but I also started looking at screen calibration and the sensitivity of the screen as well (this really could just be a hardware problem).
Question...I'm looking for the RTFM on shell commands to see if there is any way to improve the sensitivity, as well as calibration (I know there's an app on Play, but I don't need an app, do I?). Seems as if I can't find any info on either, and it's been a long time since I've worked on Linux. Only got one hit on "calibrate", talking about adb commands, and renaming the
Are there any settings to help this out? I booted into TWRP, and there doesn't seem to be anything in there, and there's a bunch of settings in "developer options", but I have to start googling those, to see if any fit the bill.
If anyone can point me in the right direction, I would be extremely grateful. Perhaps this belongs in the developers forum?
TIA...Eric
There is the nook screen recalibrate app but on my nook a stylus had never worked well. Just the hardware they used.
Sent from my ADR6410LVW using xda app-developers app
Thanks for the reply...I'll look into that app, but I have a funny feeling it's the hardware as well.
Funny thing is when I use my finger, the writing comes out better than when using the stylus. More capacitance in my finger, I suppose :laugh: