Database Users

[Q] Forcing screen rotation

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.

setting up Droid 2 for my blind sister

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.

[Q] unresponsive/inaccurate touch issues?

I have persistent issues with the touch screen.. it is unresponsive and inaccurate (I touch one part on the screen.. it "ghost" touch another region instead)... I am getting really annoyed by that... It's due to dirt around the sensors I think (cuz when i clean it, it's better) but I can't prevent dirt from getting on the sensors! Are all ebook touch screens like that?

yeahman45 said:
I have persistent issues with the touch screen.. it is unresponsive and inaccurate (I touch one part on the screen.. it "ghost" touch another region instead)... I am getting really annoyed by that... It's due to dirt around the sensors I think (cuz when i clean it, it's better) but I can't prevent dirt from getting on the sensors! Are all ebook touch screens like that?
Click to expand...
Click to collapse
You are correct, this problem is happening due to buildup of substances (dirt, sand, dust, etc.) around your Nook's screen sensors. If you cannot prevent these substances from getting on your screen, try putting your Nook in a case with a pocket cover. You can carry a microfiber cloth in the pocket to clean the screen when needed.
And yes, all eBook reader touch screens which are eInk act like this.

ИΘΘK¡€ said:
And yes, all eBook reader touch screens which are eInk act like this.
Click to expand...
Click to collapse
Actually most newer e-readers have a capacitive layer for the touch screen instead of the infrared sensors along the edge. I would recommend that anyone experiencing these issues search for and download Renate's app for testing your NST screen, It'll show you exactly what sensor is having problems and allow you to try and correct them.
OB
Sent from my SPH-D710VMUB using Tapatalk 2

OverByter said:
Actually most newer e-readers have a capacitive layer for the touch screen instead of the infrared sensors along the edge. I would recommend that anyone experiencing these issues search for and download Renate's app for testing your NST screen, It'll show you exactly what sensor is having problems and allow you to try and correct them.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
Click to expand...
Click to collapse
Thank you for the FYI!
Would you care to link/attach the app you mentioned? I'd like to try it.
EDIT - Nevermind, after a fair bit of searching I found it. Here's the post with the latest .apk, and here's the post with instructions.

Download Touch.apk in the signature.
Also UsbMode.apk now shows touch coordinates too for a quick check.
It will also work with non-Nook-specific stuff on any Android devices (up to Lollipop).
The screenshot below was with a Nexus 9 using 10 fingers.
The number of points your device can follow may be anywhere from 1 to 10.

Renate NST said:
Download Touch.apk in the signature.
Also UsbMode.apk now shows touch coordinates too for a quick check.
It will also work with non-Nook-specific stuff on any Android devices (up to Lollipop).
The screenshot below was with a Nexus 9 using 10 fingers.
The number of points your device can follow may be anywhere from 1 to 10.
Click to expand...
Click to collapse
Here's a screenshot of what my NTG displays when using 2 fingers - strange that it still displays coord's instead of "2 points" like the Nexus 9 shot you attached does (except with 10, of course).
EDIT - By the way, @Renate NST, don't you think it's probably time to put com.temblast.reader.apk into your signature?

I didn't think there was enough room to show 10 sets of coordinates.
That's why you only see the first two sets.
After that, it only shows the number of touches.
Um, about the Reader, I have to see what the latest version is.
The development has gone off in a direction that probably is not useful for most users.

Renate NST said:
I didn't think there was enough room to show 10 sets of coordinates.
That's why you only see the first two sets.
After that, it only shows the number of touches.
Click to expand...
Click to collapse
Ah. Well, that's definitely logical. Thanks for explaining.
Renate NST said:
Um, about the Reader, I have to see what the latest version is.
The development has gone off in a direction that probably is not useful for most users.
Click to expand...
Click to collapse
You haven't updated your thread on the Reader in a few months. Would you mind PMing me about the newer features that "probably are not useful for most users"? Or, better yet, update your thread about it?

Nook Simple Touch Noob Question

Hi
I have a nook simple touch - 1.2.1 firmware not rooted yet, I only want to use it as an e-reader but the ghosting is awful compared to my wifes kindle of the same generation (non touch).
I've been trying to look around and find out what I can do, is there a way to force it to refresh every page, some searching seems to suggest the issue was better on older firmwares, why B&N didnt include an option like amazon to force refesh every page who knows (that's not enabled on my wifes kindle) - the Kindle is just much easier to read in direct bright sunlight but I'm sure theres some tweaking that can be done to improve it

I have to say I am surprised by your description of your NST. I've been paying close attention to mine today while reading and I may be losing my vision but I can't see the ghosting you are describing. I've always felt the native Reader and its default settings worked really well. In some other apps there may be issues with ghosting, but not in the reader.
I'm running FW 1.21 also and while I have rooted and altered my device a lot, to my knowledge I haven't done anything to the functioning of the Reader app. Are you sure you don't have some kind of hardware issue?

nmyshkin said:
I have to say I am surprised by your description of your NST. I've been paying close attention to mine today while reading and I may be losing my vision but I can't see the ghosting you are describing. I've always felt the native Reader and its default settings worked really well. In some other apps there may be issues with ghosting, but not in the reader.
I'm running FW 1.21 also and while I have rooted and altered my device a lot, to my knowledge I haven't done anything to the functioning of the Reader app. Are you sure you don't have some kind of hardware issue?
Click to expand...
Click to collapse
It could be a hardware issue but it's well out of warranty, I do notice the ghosting on the kindle too so maybe im just susceptable to spotting it and having it irritate me, just wondered if there are any tweaks to control thow often it refreshes as its ok once it refreshes the screen

damianiw said:
It could be a hardware issue but it's well out of warranty, I do notice the ghosting on the kindle too so maybe im just susceptable to spotting it and having it irritate me, just wondered if there are any tweaks to control thow often it refreshes as its ok once it refreshes the screen
Click to expand...
Click to collapse
OK, so look here at what Renate suggests.

nmyshkin said:
OK, so look here at what Renate suggests.
Click to expand...
Click to collapse
Seemed to be very complex, so I went for root and under there is the option for how many pages before full refresh
also installed cool reader for good measure and very happy - problem solved

damianiw said:
Seemed to be very complex, so I went for root and under there is the option for how many pages before full refresh
also installed cool reader for good measure and very happy - problem solved
Click to expand...
Click to collapse
Excellent! Your rooting method must be different from mine but now we're both happy

Good job, @nmyshkin!

Thanks everyone, my main concern was rooting would stop it behaving like an e reader but relaunch I a great launcher and the default options for home and library mean I have best of both and importantly control over the refresh as my nook does appear to ghost far more than a friends on comparison, for the £29 paid over a year ago the nook is awesome

Comparing my nook to a friends the contrast looks really different so maybe this unit wasnt calibrated right - i'm now looking for a contrast adjuster to see if that solves me needing to fully refresh the screen so much as that will be using more battery

[Q] Laggy screen response/sensitivity on T280

Is there any way to increase the screen sensitivity on the T280? I've only found one mention of the issue after thoroughly searching Google, with no suggested fix.
I'm comfortable with modifying system files such as build.prop and such, I just have no idea where to start!
The issue:
This screen is really slow to pick up touches, especially from a stylus.
When swiping (eg for pattern unlock) contact is often broken.
Even using my finger, when selecting text it's difficult to move just one letter at a time.
In handwriting/drawing apps, resulting text is extremely angular and jagged.
Here's what I've tried:
Changed "mouse sensitivity" in the settings (minor improvement)
Used 2 different screen calibration apps (minor improvement)
Installed debloated ROM (only one available; no improvement)
Removed some unnecessary system apps (will be removing more to free up space....)
Disabled settings that affect device speed such as animations
Several different stylus types (the most expensive work worst )
So, is anyone else finding this an issue? Is there a fix I don't know about? Is/are there a kernel tweak or something that will speed up screen response time?
I bought this tablet in part so I could use it for handwriting input using a stylus on a larger screen than my teeny S5. Unfortunately, the screen response is far too inconsistent and ...well, slow than I'd expected.

PushyPhoenix said:
Is there any way to increase the screen sensitivity on the T280? I've only found one mention of the issue after thoroughly searching Google, with no suggested fix.
I'm comfortable with modifying system files such as build.prop and such, I just have no idea where to start!
The issue:
This screen is really slow to pick up touches, especially from a stylus.
When swiping (eg for pattern unlock) contact is often broken.
Even using my finger, when selecting text it's difficult to move just one letter at a time.
In handwriting/drawing apps, resulting text is extremely angular and jagged.
Here's what I've tried:
Changed "mouse sensitivity" in the settings (minor improvement)
Used 2 different screen calibration apps (minor improvement)
Installed debloated ROM (only one available; no improvement)
Removed some unnecessary system apps (will be removing more to free up space....)
Disabled settings that affect device speed such as animations
Several different stylus types (the most expensive work worst )
So, is anyone else finding this an issue? Is there a fix I don't know about? Is/are there a kernel tweak or something that will speed up screen response time?
I bought this tablet in part so I could use it for handwriting input using a stylus on a larger screen than my teeny S5. Unfortunately, the screen response is far too inconsistent and ...well, slow than I'd expected.
Click to expand...
Click to collapse
Unfortunately the drivers or the touchscreen hardware itself for the T280/T285 is not that good. I have a drawing app that I created myself and the touch event update rate is so slow it creates jagged lines. Best case is that it is a driver issue and we can fix it in the kernel, worst case the hardware just sucks and it is what it is. On my OMNIRom 6.0.1 SM-T285 device touch response is actually ok, it is the update rate and precision of the touch which is a problem.

Thank you so much for the quick reply, and for understanding what I mean.
jedld said:
On my OMNIRom 6.0.1 SM-T285 device touch response is actually ok, it is the update rate and precision of the touch which is a problem.
Click to expand...
Click to collapse
Congrats on getting most of the bugs out of that ROM! It was SO disappointing to read the "fine print" on your OMNIRom and discover I couldn't use it, as it looks pretty sleek, but you're helping others immensely with your work.
jedld said:
Unfortunately the drivers or the touchscreen hardware itself for the T280/T285 is not that good. I have a drawing app that I created myself and the touch event update rate is so slow it creates jagged lines. Best case is that it is a driver issue and we can fix it in the kernel, worst case the hardware just sucks and it is what it is.
Click to expand...
Click to collapse
Hooray for drivers being a possibility! There's something can be done about that!!
Do you find that the lines aren't quite as jagged running OMNIRom as with stock?
How would someone find out whether it's the hardware or the drivers?
Are the differences between 280/85 so extreme that I can't try anything on my own?
Is there anywhere I can "sign up" for testing any new tweaks or ROMs or kernels?
(Update on the issue: I ran the "screen calibration" test again and it says it's taken another 10ms off the response time. Not sure if I'm imagining it but it feels as if it's actually faster...)
I was also thinking, would the DPI have anything to do with the jagged appearance? Between this tablet and the 2 others I was looking at (both Galaxy - previous 7-inch and 9-inch) those had much better DPI ...or am I thinking of resolution? Those aren't the same thing, are they? In any case, it's worth checking into whether fiddling with the DPI might do any damage.

Do you find that the lines aren't quite as jagged running OMNIRom as with stock?
Click to expand...
Click to collapse
I think it is just as bad
How would someone find out whether it's the hardware or the drivers?
Click to expand...
Click to collapse
We will need someone to tinker with the kernel sources to found out. For the SM-T280 someone is working on making the kernel sources work. Unfortunately, though annoying it isn't really on the top of my list right now.
Are the differences between 280/85 so extreme that I can't try anything on my own?
Click to expand...
Click to collapse
Devs working on the devices are actually surprised that there are more differences as expected for two devices that share the same family name.
Is there anywhere I can "sign up" for testing any new tweaks or ROMs or kernels?
Click to expand...
Click to collapse
I just go through xda for my testing.
I was also thinking, would the DPI have anything to do with the jagged appearance? Between this tablet and the 2 others I was looking at (both Galaxy - previous 7-inch and 9-inch) those had much better DPI ...or am I thinking of resolution? Those aren't the same thing, are they? In any case, it's worth checking into whether fiddling with the DPI might do any damage.
Click to expand...
Click to collapse
Based on the software codepath, DPI shouldn't really affect touch performance.

I wound up returning it and picking up the 7" Galaxy Tab E Lite (SM-113), which seems to suit my needs much better. While it's much more limited in some ways - no custom ROMs, limited to KK4.4.4, same small internal storage issue - the screen response is WAY better and I can get around the annoyances (largely - no, SOLELY - due to all the things this forum has taught me over the years. :highfive:
jedld said:
Based on the software codepath, DPI shouldn't really affect touch performance.
Click to expand...
Click to collapse
You were right. But it was fun to play around with! And I learned a few things in doing so.
We will need someone to tinker with the kernel sources to found out. For the SM-T280 someone is working on making the kernel sources work.
Click to expand...
Click to collapse
I sure hope that someone figures this out soon because it's a pretty sweet little tablet, otherwise, and I can't be the only one for whom this is a deal-breaker.
Unfortunately, though annoying it isn't really on the top of my list right now.
Click to expand...
Click to collapse
I totally appreciate that your time is valuable, and thank you immensely for taking the time to respond.

Similar issue
Hi,
Was wondering if anyone with these issues also experienced this: While the tablet is on, when watching something for instance, if the touch screen isn't used for a bit (say over 30 seconds) when I first press it it doesn't respond at all, to get it to wake up I have to press quite firmly, usually several times, before it starts working. Once it does respond I can use a much lighter touch so it doesn't seem like a screen protector or overall sensitivity problem, it's as if the screen goes into some kind of sleep mode becoming much less sensitive.
Anyone know about this/how to fix it?
Much love,
Tom