Re: New RCA Galileo, my thoughts


Jeremy <icu8it2@...>
 

Hehe, actually, no. I'll hop over and take a look in sounds though to see what I find. Do you possibly mean some place where the talkback navigation sounds might be listed and what they are set to indicate? that would be majorly awesomeness if so. lol
Tc.

On 4/27/2017 5:59 PM, Rajmund wrote:
Hi,
HMM, my android clicks when it accepts the double tap. Weird if yours doesn't. Have you tried looking in sounds/notifications? JUST a random guess, for whatever it's worth.



Sent from a Braille Sense

----- Original Message -----
From: Jeremy <icu8it2@gmail.com>
To: main@TechTalk.groups.io
Date: Thursday, April 27, 2017 11:52 pm
Subject: Re: [TechTalk] New RCA Galileo, my thoughts


I didn't really pay attention to whether this was the 2016 or 2017 version of the tablet, but I'm going to assume it's the later one. I'm thinking that there shouldn't be any real differences between the two, yours and mine, but there very well might be. As Carlos also mentioned later in the thread, it might also be just that something is messed up with it being cheaper hardware and I drew the wrong straw. lol

I don't recall if it was ever mentioned, but is this audex free? An ability to have a sound specific to when you perform a double tap could certainly be helpful in trying to figure out if it was actually working.
Thanks.
Take care.


On 4/27/2017 6:57 AM, Josh Kennedy wrote:

unless the touch screen is made a bit different than mine? I don't know. But I can tell you that I can double tap just fine on my RCA tablet. Using audex helps because I get a sound and stuff when I double tap and do gestures and stuff. the audex accessibility redefined app, that is what i use.



On 4/26/2017 11:24 PM, Jeremy wrote:

So, I had an opportunity to test a double tap without tb running and go figure, it worked perfectly, every single time. I made sure to test different speeds of tapping, different amounts of force and the double tap was flawless. I then had my wife remove the updates to tb that had been added when I updated it and then we went back through the tutorial again. Even inside the tutorial, in the part where it has you demonstrate a double tap, it wasn't working as consistently as it had before we started it back up, but we were able to complete the tutorial. Once we'd gotten back on the home screen, we noticed some major inconsistencies again with getting them to register. She was able to get it working pretty well using one finger and then not at all with another one. I had issues no matter what finger I tried, but I noticed that I could tap it with the fat part right below my knuckle and get it about every 5 or 6 times. I even re-updated tb, thinking that perhaps some part of some mechanism that tb uses to intercept the gestures was wigging out, but it still hasn't changed. We are still able to completely turn it off and have them work correctly, so at this point, I'm completely boggled.

The last thing I thought of, which I've yet to try is doing a complete factory reset of the device. This seems really stupid to me, as I just received it this morning, but I honestly don't have any ideas beyond that or any ideas of where else to go with it. As much as I'd really love to get back into android, hopefully figure out if a higher end phone is going to work for me, I'm thinking that perhaps this wasn't the best way to go about it. rofllmao
Take care. :)


On 4/26/2017 6:36 PM, jeremy wrote:

Unfortunately, as much as I'd like it to, I highly doubt that practicing a double tap beyond what I've already tried is going to automagically cause it to start registering them differently. My apologies if I didn't mention it before, but I'm not exactly new to using a touchscreen. I've been using different touchscreen devices every since I purchased the IPhone4, had an S3 with both ICS and then rooted to use jellybean with cm10 for a short time, back to the IPhone5, IPads and now to the IPhone6 plus which I've had since it's release.

My issue really wasn't from a lack of knowledge of the gestures used for android, as they are for the most part equivalent to those used in IOS, it was more so my confusion why most gestures were working decent enough to use and that one was not. Now that I've played with it even more, had an opportunity to tap it lightly, hard, tap it slow and fast and yet see no difference, I really don't have any clues.

This isn't the first time I've herd of this type of thing on an android device, but it's the first time I've actually seen it with one I've played with. As you say, if you have detached the keyboard and you're finding that the double tap gesture is registering as it should, then perhaps it's something out of my control to fix or re-configure, such as some weirdness in the display.

I've also tried to visit the preferences area of tb and enable the one tap activation gesture, to see if it'd work as a workaround, but it still doesn't perform a click on an element with raising your finger and tapping once as it should. It does seem to make the double tap work a little better, but it's still not consistent.

As I said before, I think I need to figure out a way to test the difference between it registering a single tap and a double tap and do it without tb running. It'd be my thinking that that'd be the best way to determine if it's something specific to the accessibility framework, so tb or EBT or something outside of it like the hardware.

Lastly, I also noticed an option in the settings for tb that indicated that you could change the sensitivity for it registering taps. I may be slightly off it the exact wording, but either way, I also tried to adjust that to see if it'd change and it didn't.
Take care.


On 4/26/2017 4:48 PM, Josh Kennedy wrote:

I detached my tablet and was using it for a bit tonight, and had no issues with the double taps and stuff. just practice with it, you'll get the hang of it.

Sent with AquaMail for Android
http://www.aqua-mail.com
On April 26, 2017 17:45:15 "Gene" <gsasner@ripco.com> wrote:
I don't use such devices but I would suggest experimenting with the time between taps. Changing the interval may affect performance. You indicated that keeping a finger on the icon improves performance. This may be, in effect, interfering with how the device gauges the time between taps and may be improving performance for that reason.
Gene
----- Original Message -----

From: Josh Kennedy
Sent: Wednesday, April 26, 2017 4:25 PM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] New RCA Galileo, my thoughts


two useful commands are control alt r for recent screens, and control alt n
for notification screen. to review the screen press alt plus up down left
or right arrow keys. to activate an item hit alt enter. to long press, hit
alt shift enter.


Sent with AquaMail for Android
http://www.aqua-mail.com


On April 26, 2017 5:19:30 PM "Carolyn Arnold" <4carolyna@windstream.net> wrote:

Thank you for that information. Could you send me any tablet specific key
commands to:

4carolyna@windstream.net

Thanks.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of
Josh Kennedy
Sent: Wednesday, April 26, 2017 4:13 PM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] New RCA Galileo, my thoughts

if you use the keyboard, the escape key is back, and home is f1 and
settings is f3.


On 4/26/2017 4:09 PM, Jeremy wrote:
Hey all,
First let me just say that I do not intend what so ever to start any
arguments as to what platforms might be better, but my experiences so
far with this new tablet haven't been good at all. It was my hopes
that perhaps updating tb might fix some of the issues I'm seeing so
far, but it hasn't done much for being able to navigate around this
thing.

Beyond that, I'm hoping that perhaps something is faulty in the
hardware, but either way, here is what I'm having issues with, so
perhaps someone with more experience can help.

As soon as I got the tablet this morning, I followed the instructions
here for starting tb. I'm familiar with using this two-finger gesture,
as I'd used it before on other devices, but I unfortunately wasn't
able to get it to work right away. I ended up locking and unlocking
the screen, as was mentioned here previously, using one finger to
flick up and then using the two-finger gesture again. After a little
bit tb came up talking and took me to the tutorial thing as I'd expected.

It was here that I started having a lot of problems. First, the double
tap gesture seems to be very difficult to register. From what I can
tell so far, the other gestures such as flicking aren't as bad, but no
matter how slow or fast I try to double tap, it always seems to
register it as me just touching the item once. I noticed that it's a
little more reliable if I keep one finger on the item I want to
activate and then use another finger to double tap, but this isn't
always consistent either.

Another real gripe was actually making it through the setup process.
One area specifically that I got stuck in was the one where you can
select your wireless AP you wish to connect to. I'm not quite certain
if it was the flick gesture screwing up, an issue with that part of
the interface, or whatever, but I ended up in an area where the name
of an AP here close to me was being repeated over and over and over.
As soon as I'd use the arrow keys on the keyboard or a flick right
gesture to try to jump to the name of my AP, I would get the sound
from tb that something else had been refocused and it would jump back
to somewhere else on the screen. Once I'd made it to the name of my
AP, I tried to quickly use the double tap to activate it, but once
again, it failed. I ended up having to use a mixture of the arrow
keys, enter key, touching the screen to find stuff that I couldn't
focus on with the keyboard and the flick gestures to make it through.

Once I'd made it through setting up the tablet, I was able to go into
the apps icon on the bottom and locate the play store icon. Through
using explore by touch, flicking and the keyboard, I was able to
locate the search button and do a search for talkback. I'd also been
somewhat familiar with this process from older devices, so I already
knew what to expect as to installing/updating it. Once I'd updated it,
I noticed that the navigation sounds had changed, but I'm still having
major issues with actually moving around through the UI. This is where
I'm hoping that maybe something is jacked up with the screen, as to
why it's hard to register a double tap, but if not, I'm not quite sure
I'd call this usable at all. I'll also note that in the little I've
been able to play with higher end devices, such as the s7, I didn't
seem to have issues with gestures like this.

For anyone else who might be thinking of purchasing this, please keep
in mind that it doesn't seem to have dedicated hardware buttons for
back and home. For those familiar with some of the phones that
actually have a home button you can feel, this makes it quite easy to
re orientate yourself back to the home screen if you're stuck or
whatever. While the tablet does have buttons going along the very
bottom of the screen, back, overview, home, volume down and volume up,
it appears to be necessary to use the double tap gesture to activate
these, so that means it's stupidly hard to get them to work.

I then decided to locate the settings app and see if there were any
preferences I might could change to help, which leads me to my final
problem. I checked through everything I could find, accessibility,
checked the TTS, looked at the TTS's speech rate, whent back a bit and
turned down the brightness on the screen, pressed back on the keyboard
to go back into the main settings again and poof, I completely lost
speech. It didn't appear that tb had crashed, as I still had the
navigation sounds that tb used when I used flick or the keyboard to
move, but the speech from the default google TTS that comes loaded was
completely gone. I tried to lock and unlock the screen which didn't
work, so I ended up holding down the power button for like 30 seconds
and everything was shut down. Luckily for me, when the device came
back up, I had speech again. I've thought about purchasing another
TTS, as one reason I tried it was for being able to use eloquence, but
I'm honestly a little worried with what I see so far from what I
assume is crappy hardware.

I'd really hoped that the 80 bucks I put into purchasing this little
beasty would be enough to give me an idea if a higher end device such
as a phone would be something I'd like changing to, but so far as I
can tell, I'm not pleased at all.
It was here that I was hoping that perhaps it's just me, something
screwy with the hardware that could be fixed, or that perhaps someone
else had ideas on stuff I could try.
Hope everyone is well.
Take care.


















Join main@TechTalk.groups.io to automatically receive all group messages.