Text Selection not working on Galaxy S5, nor on Galaxy S5 Active

[GoogleCodeExporter]

I am using Android KitKat 4.4.2 with A Samsung Galaxy S5 Active.  This problem 
is also occuring on the standard Galaxy S5.

Using Talkback 3.5.2, when focused within an edit field, it is impossible to 
select text unless using a hardware bluetooth keyboard.

1.  Locate a text box which you may enter data into.

2.  Double tap the text box to move focus to it, and open your on screen 
keyboard of choice.

3.  Open the Local Context Menu, and select cursor control followed by Select 
all.

4.  Notice that the text in the edit box is not all selected.

3.1.  Instead of moving to select all in the Local Contewxt Menu, move to 
Cursor control, then to Start selection.

5.  Change your granularity to characters, words, lines, etc.

6.  Swype through the screen with one finger, and notice that nothing happens.  
Talkback says nothing, and no text is selected.  Be sure to disable Select 
mode, and return to default granularity when finnished testing.

Note:  all of the above methods work perfectly on all devices I've tested with 
the exception of the Galaxy S5, and the Galaxy S5 Active.  I have tried using 
different software keyboards such as the google keyboard, Flexy, Samsung's 
default native keyboard, Swype+Dragon Dictate from Nuance, etc.  All of them 
produce the same results.

It's worth mentioning that I used to be able to long press the text box, and 
then could move to the top of the screen with explore by touch, and locate 
items like select all, copy, cut, paste, undo, etc.  Now, when long pressing, 
this no longer works either.  I started noticing the long pressing not working 
effective today, 9/23/2014 at 23:20GMT.  I have tested this both with the 
public beta as well as with the official 3.5.2 release.  Both have the same ill 
effect.

Original issue reported on code.google.com by clgillan...@gmail.com on 23 Sep 2014 at 11:28

[GoogleCodeExporter]

I also use the Samsung Galaxy S5 Active, and I also see the exact same results. 
As the poster indicates, the only way to get around this issue is to use a 
bluetooth keyboard, and who wants to lug that around with them on the go?

Original comment by ben.j.bl...@gmail.com on 23 Sep 2014 at 11:37

[GoogleCodeExporter]

Hi.  I understand totally that you can use a bluetooth keyboard, but again, 
as comment #1 states, not everyone's going to own one, nor have access to 
one.  Further, though this might be a temporary work around, this is still 
definitely a bug which needs to be addressed by the Eyes-Free development 
group.

Thanks.

Chris.

Original comment by clgillan...@gmail.com on 23 Sep 2014 at 11:49