and here in lies the problem or at least one of them when you deal with open source, or a platform that allows for more freedom to change phones. there are times that CF just can't make a change to get around a manufactures software like htc's software. I don't know as I am not a programmer, however this makes sence to me. yes, I think CF should be doing more than they are doing, for example, talkback works with the market much better than MA does, or spiels does, however, the author of spiel at least has said they might work on a fix for it. cf should have already done this, it is doable. if it wasn't then how did talkback do it? my point is this, people that want to blame CF for everything, and think that is is 100% CF's fault are so wrong it isn't even close to funny. CF has done what they can, and think about it this way, MA is much cheaper than MS was.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of dan greene Sent: Friday, November 11, 2011 5:56 AM To: [email protected]; 'Mobile Accessibility Android Users List' Subject: RE: [MA] Answering A Call While I'm willing to give some blame to Android for being open-source, I am also willing to point a bit at CF as well. Open-source goes both ways. Sure, the providers can modify parts of the operating system for their own ends. So, conceivably, could CF, perhaps producing a usable replacement to that fabulously annoying HTC Sense window. As for updates, I'm sure they will be loudly proclaimed on this list. Along those lines, anyone actually tried to perform any upgrade that appears in the Android Notifications Screen? I've seen things in there, but again, trackpad swipes up, down, ... sometimes work, sometimes not. Don't get me wrong, in principle I have come to really like the touch interface, ever since my early days with MSP 1.x. All I ask is that the interface consistently work, and if it doesn't, a bit of response from the software developers as to reasons why. Cheers DG > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Dusty Tague > Sent: Thursday, November 10, 2011 10:06 PM > To: Nick Zammarelli > Cc: Mobile Accessibility Android Users List > Subject: Re: [MA] Answering A Call > > No one is covering up for code factory, since many phones still work, > the problem isn't with code factory, it is with Google allowing > fragmentation. Set a standard and Code Factory will either meet it or > go away. Frankly, I see MA as the best of the alternatives, windows > phone 7, inaccessible, iPhone, strictly swipe. Blackberry and > Symbian, on their way out. Do I wish code factory was more on top of > things yes, should they be more responsive to their customers, yes. > If I replace my version of the Android operating system with ice cream > sandwich and it works out of the box on all native apps and feels > smooth and easy to use, unless code factory wows me, I will walk away > and not look back. > actually you most likely will be notified of a release as someone will > post it here. In addition, you will get a notification that updates > are available. Keep the faith. swiping and tapping isn't that bad. > > On 11/10/2011 7:36 PM, Nick Zammarelli wrote: > > I'm sorry, but we need to stop covering for Code Factory on these > > issues. Last summer, we thought it was just an issue with > HTC phones, > > but we now know that it goes much deeper. I have an LG enlighten, > > which I love, but I cannot answer or reject calls using the volume > > keys. Dan is right, why should we have to swipe to answer a > call when > > the phone is locked but have to find the answer button when > the phone > > is in use. It was easy for Code Factory to lay blame with just one > > manufacturer, but clearly this is not the case, and now we all know > > that. Hopefully, a new version of Mobile Accessibility is > coming soon > > that addresses all these issues. Of course, even if this is > so, we'll > > never know this, because Code Factory never tells us anything.On > > 11/10/2011 2:36 PM, Dusty Tague wrote: > >> It is not just code factory at fault, it is android for allowing > >> fragmentation to occur making this a problem. I think I > can honestly > >> say that for some the simplicity and continuity makes the > iPhone a > >> better purchase. The reason I said generally is that the > >> manufacturers aren't always consistent in labeling buttons and > >> placing them in the same location, but I have found that there are > >> few exceptions to this and differ according to the > particular app. > >> That is the problem with a one size fits all approach on a > fragmented > >> platform. It is a shame that t-mobile doesn't offer the > iPhone. You > >> could try the sidekick 4g, or the lg my touch q, check the > keyboard > >> first to make sure, and see if that would be a better phone. > >> > >> > >> > >> > >> On 11/10/2011 12:22 PM, dan greene wrote: > >>> That may be true, but on the MyTouch 4G Slide, with MA running, > >>> sometimes the trackpad works for arrowing down and to the > side, and > >>> sometimes it does not. > >>> And, now forgive me if this sounds argumentative, it > should not take > >>> me 3 or more gestures to hang up the phone. > >>> And, again being argumentative, why should there be one procedure > >>> for answering/disconnecting the phone when it's waking up, and > >>> another when the phone is awake as the call comes in? > >>> And, finally, if the phone is still against my ear when I try to > >>> hang up, it's usually displaying a different screen than > if I move > >>> it away from my ear--something CF seems to forget to > tell users in > >>> its, so-called, manual. > >>> I laughed out loud when I read your sentence that contained the > >>> words "generally works". > >>> Generally works???? I just spent over $300 for a phone, and CF > >>> wants over another $100 for this software. Seems to me > that things > >>> should be a bit better than "generally works". > >>> And CF should support its users better, instead of canned > responses > >>> to their problem reports. > >>> I certainly mean no disrespect to you, I thank you for > responding, > >>> but I've spent almost a week trying to help my wife learn > this new > >>> phone, and the inconsistency of operations, and the > absolute lack of > >>> support from CF, is unbelievable. > >>> Cheers > >>> Dan G > >>> > >>> > >>> > -------------------------------------------------------------- > ---------- > >>> > >>> *From:* [email protected] > >>> [mailto:[email protected]] *On > Behalf Of *Dusty > >>> Tague > >>> *Sent:* Thursday, November 10, 2011 11:03 AM > >>> *To:* Mobile Accessibility Android Users List > >>> *Cc:* Steve Cook > >>> *Subject:* Re: [MA] Answering A Call > >>> > >>> Dan, if you can answer a call in system screens, you > can hang up, > >>> either arrow down once and to the right once and you > should be on > >>> the correct button. Another approach, also when > using system call > >>> screens is to tap the screen to the right of where you tap to > >>> answer, not on the right side of the screen but more > to the left > >>> side of middle. > >>> Both these approaches generally work on most phones > regardless > >>> of manufacture as long as they have physical > navigation controls. > >>> > >>> On 11/10/2011 9:05 AM, Steve Cook wrote: > >>>> Thanks for this information Dan. > >>>> > >>>> Steve Cook > >>>> Assistive Technology Consultant > >>>> SC Commission for the Blind > >>>> 1430 Confederate Avenue > >>>> Columbia, SC 29201 > >>>> Office: (803) 898-8788 > >>>> Fax: (803) 898-8882 > >>>> E-Mail:[email protected] > >>>> > >>>> -----Original Message----- > >>>> From:[email protected] > >>>> [mailto:[email protected]] On Behalf > >>>> [email protected] > >>>> Sent: Thursday, November 10, 2011 10:14 AM > >>>> To: Mobile Accessibility Android Users List > >>>> Subject: Re: [MA] Answering A Call > >>>> > >>>> Hi Steve, > >>>> > >>>> I have similar problems with the My Touch 4G Slide. > >>>> When your phone is awake as a call comes in, there > doesn't seem > >>>> to be any way to answer the call using MA. > >>>> the swipe up doesn't work, just increases the ringer volume, > >>>> and, like you, the volume keys just silence the ringer. > >>>> I haven't tried answering one call, while on another--the > >>>> manual says just a swipe up will answer, I tend to > doubt that now. > >>>> You can try using the system call screen, (it's > selected by a > >>>> checkbox in the MA settings/advanced dialog box) but I > found that > >>>> option even worse. > >>>> With that screen enabled, I can answer the call, but I can't > >>>> hang them up. > >>>> > >>>> It's just another annoyance to add to the list of > things that > >>>> aren't right with the MA application-- at least on the > My Touch 4G > >>>> Slide. > >>>> > >>>> Cheers > >>>> Dan G > >>>> > >>>>> -----Original Message----- > >>>>> From: Steve Cook [mailto:[email protected]] > >>>>> Sent: Thursday, November 10, 2011 07:37 AM > >>>>> To: 'Mobile Accessibility Android Users List' > >>>>> Subject: [MA] Answering A Call > >>>>> > >>>>> Hi All, > >>>>> > >>>>> I can make a phone call with my Android HTC EVO > using MA. My > >>>>> question How do you answer a call when receding one? I > have the > >>>>> using volume buttons checked to answer and hang up the > call. When > >>>>> pressing either of these keys, it just silences the > phone. Also, > >>>>> when the phone is in the lock position, I can answer > the call by > >>>>> just moving my finger up the screen. My problem comes > when I am > >>>>> within MA and receive the call that I can't figure out how to > >>>>> answer the phone. Thanks in advance for your help and > I hope this > >>>>> is clear. > >>>>> > >>>>> Steve Cook > >>>>> > >>>>> October is National Employment Disability Awareness Month. > >>>>> > >>>> _______________________________________________ > >>>> ma_mailing mailing list > >>>> [email protected] > >>>> > >>>> > http://list.codefactory.cat/mailman/listinfo/codefactory.cat.m > a_mailing > >>>> > >>>> > >>>> October is National Employment Disability Awareness Month. > >>>> > >>>> > >>>> _______________________________________________ > >>>> ma_mailing mailing list > >>>> [email protected] > >>>> > >>>> > http://list.codefactory.cat/mailman/listinfo/codefactory.cat.m > a_mailing > >>>> > >>> > >> > >> > >> _______________________________________________ > >> ma_mailing mailing list > >> [email protected] > >> > http://list.codefactory.cat/mailman/listinfo/codefactory.cat.m > a_mailing > > > > > _______________________________________________ > ma_mailing mailing list > [email protected] > http://list.codefactory.cat/mailman/listinfo/codefactory.cat.m > a_mailing > _______________________________________________ ma_mailing mailing list [email protected] http://list.codefactory.cat/mailman/listinfo/codefactory.cat.ma_mailing _______________________________________________ ma_mailing mailing list [email protected] http://list.codefactory.cat/mailman/listinfo/codefactory.cat.ma_mailing
