|
Build 57
Chuck Dean
Build 57
I have removed, and reinstalled FlickType on my iPhone 8, hoping to rid myself of the memory warning pop up. Unfortunately, it has returned just as bad as before. I noticed George also has this problem and also has an iPhone 8. Considering most of us are running the latest software, I doubt the iPhone model would be the culprit, but I am not a computer nerd, so I guess anything is possible. Here is a new glitch. When I went to mail this post, the FlickType custom keyboard came up, but was only a black screen for about thirty seconds, and I couldn't do anything with it. Finally I could switch to the iOS keyboard. Then I came back to the App to include this quirk. Chuck
|
|
|
|
Re: Build 57, no click sounds on my iPad mini.
Chuck Dean
I totally agree with you. The memory warning is unacceptable. I’m wondering if it’s only showing up on iPhone eights? I don’t know if anybody else is reporting that.
toggle quoted messageShow quoted text
Chuck
On May 6, 2018, at 3:32 PM, George Cham <George.cham@hotmail.com> wrote:
|
|
|
|
Re: Build 57, no click sounds on my iPad mini.
Alex Hiironen <l000b2a@...>
I had the same issue with dictionary importing. Did the same thing (exported/reinstalled Ft from Testflight). The first time I tried importing dictionary, I didn't have Ft running. It crashed hard on that attempt. I consequentially opened it then switched back to mail and tried to import it again and it was successful that time.
toggle quoted messageShow quoted text
As others have stated, I'm also experiencing the "beginning of document" msg when I switch to the Flicktype keyboard in any app, even with text already in the edit field. Sounds like the keyboard uses a buffer and once it's dismissed it drops the text in the field? As usual, thx for all the hard work. Alex
On May 6, 2018, at 6:32 PM, George Cham <George.cham@hotmail.com> wrote:
|
|
|
|
Re: Build 57
Chuck Dean
Hi Michael, I find the need to revert back to the iOS keyboard to insert capital letters, new line breaks, and emoji which are not presently available in the custom keyboard. But I can see, in the near future, I may not need to switch.
toggle quoted messageShow quoted text
Chuck
On May 6, 2018, at 3:03 PM, Michael Maslo <michaelmaslo04@gmail.com> wrote:
|
|
|
|
Re: Build 57, no click sounds on my iPad mini.
George Cham <George.cham@...>
Hi chuck, I removed FlickType and installed it from testflight. I went to import dictionary, from the iOS mail app. Flicktype froze, and crashed. I then launched it again, imported dictionary, I got a message saying, all 32 entries imported. As I type this reply, I got the memory warning. I think that before this build goes into the AppStore, the issue of the memory warning needs to be addressed. Because you fan not expect the user to keep restarting there device
Kind regards, George Cham ‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’ Numbers 6:24-26 Get Outlook<https://aka.ms/qtex0l> for iOS ________________________________ From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com> Sent: Monday, May 7, 2018 8:12:55 AM To: alpha@flicktype.groups.io Subject: Re: [FlickType-alpha] Build 57, no click sounds on my iPad mini. Hi George, I removed FlickType after exporting my dictionary, and installed it using test flight. It is better, but as I tried to reply to this email, I got the memory warning enough times that I had to restart my iPhone. Its working better now. I am also using an iPhone eight running iOS eleven point three point one. Chuck On May 6, 2018, at 3:02 PM, George Cham <George.cham@hotmail.com> wrote:
|
|
|
|
Re: Build 57, no click sounds on my iPad mini.
Chuck Dean
Hi George, I removed FlickType after exporting my dictionary, and installed it using test flight. It is better, but as I tried to reply to this email, I got the memory warning enough times that I had to restart my iPhone. Its working better now. I am also using an iPhone eight running iOS eleven point three point one.
toggle quoted messageShow quoted text
Chuck
On May 6, 2018, at 3:02 PM, George Cham <George.cham@hotmail.com> wrote:
|
|
|
|
Re: Build 57
Michael Maslo
No I have had no loss of text. However I rarely switch keyboards. I usually stick with flick type for it offers everything I need. When I do switch I lose nothing though.
toggle quoted messageShow quoted text
Sincerely,, mike
|
|
|
|
Re: Build 57, no click sounds on my iPad mini.
George Cham <George.cham@...>
Hi costa I'm still getting memory warning on I phone8 with build57
Kind regards, George Cham ‘May the Lord bless you and protect you. May the Lord smile on you and be gracious to you. May the Lord show you his favor and give you his peace.’ Numbers 6:24-26 Get Outlook<https://aka.ms/qtex0l> for iOS ________________________________ From: alpha@flicktype.groups.io <alpha@flicktype.groups.io> on behalf of Chuck Dean <cadean329@gmail.com> Sent: Monday, May 7, 2018 7:58:37 AM To: Alpha Subject: [FlickType-alpha] Build 57, no click sounds on my iPad mini. Hi Kosta, I am trying the custom keyboard on my I pad mini two. Everything works great except I get no click sounds. I have the settings at new marimba and the volume at forty percent. No big deal, but thought I would mention it. I can type very fast with the mini, as I am using both hands and eight fingers. A little clumsy at first, but I am getting better all the time! Chuck (mobile) Pleez x cuze enny tie ping or spelin airors.
|
|
|
|
Build 57, no click sounds on my iPad mini.
Chuck Dean
Hi Kosta, I am trying the custom keyboard on my I pad mini two. Everything works great except I get no click sounds. I have the settings at new marimba and the volume at forty percent. No big deal, but thought I would mention it. I can type very fast with the mini, as I am using both hands and eight fingers. A little clumsy at first, but I am getting better all the time!
Chuck (mobile) Pleez x cuze enny tie ping or spelin airors.
|
|
|
|
Build 57, rocking back-and-forth between keyboards.
Chuck Dean
Hello everyone, first I want to say I removed FlickType and then installed it with test flight, and it is working much better. I have been typing a lot with no memory warning pop up. I have been trying to go between the keyboards, which has been working fine. The previous text has been typed on the custom keyboard, now I'll go to the iOS keyboard.
This is being dictated on the iOS keyboard. It has inserted it exactly where I left off with the FlickType keyboard. Now I will go back, and see what happens. This is back to FlickType. If I cursor back it only goes back to the point where I cane back to FlickType, it says beginning of document, but all the text is actually still there. The easiest way to verify this is to go to the iOS keyboard. Chuck
|
|
|
|
Build 57, reinstall
Chuck Dean
Hi Kosta, I was getting frustrated with the memory warning pop up, so I exported my dictionary, removed FlickType, installed it from test flight, and imported the dictionary. It is running better and I have yet to see the memory warning pop up. I am noticing FlickType is taking a long time to load; perhaps this will clear up as I use it. Will keep our fingers crossed.
Chuck
|
|
|
|
Re: Build 57
Chanelle Allen
Hello,
As with others in this group, I did not receive a message from TestFlight but updated anyway. Did Kosta send an introductory message? On my phone, build 57 performs as expected. Personally, I find the cursor sounds for navigating between words and sentences to be unnecessary. More testing on my part will determine whether or not the sound is distracting, but I don't think it will be. I still prefer the typing experience offered by the FlickType app. As others have said, the predictive engine in the FlickType app is slightly better than the engine used in the keyboard. For me, the FlickType app has two advantages over the keyboard--no lag and customizable tap volume. I know that Kosta continues to address typing latency in each new build. It seems that there is less lag upon beginning a new typing session regardless of the app being used. After a couple of sentences or switching back to the FlickType keyboard from another app or the iOS keyboard, the latency increases. Again, I need to do more extensive testing to verify my statement and do not write frequent email, texts, or social media posts. My phone has not given a low memory warning or deleted the last line of text. Will it eventually be possible to customize the tap sound volume for the FlickType keyboard? The tap sound (type of sound) specified in settings does carry over to the keyboard. I had not read the fine print to realize that nothing was stated about volume. The only way to change volume is to set sound effects mode to unduckable. The volume of the taps is so loud for me when using the keyboard that I am able to use the custom keyboard for only a short period of time. Everyone has such widely varying needs, and the sound may be just fine for most people. I am sound sensitive and experience frequent headaches. As a result, my VoiceOver sounds, raised pitch when typing, and keyboard clicks are turned off. The FlickType app tap sounds set to 20% do not bother me at all. Finally, last week, my problem with hearing space when flicking down went away once I discovered that my cursor was not at the end of the document. Even though the "space" bug has been fixed, I have made it a habit to use the two and three finger flicks to ensure that I am at the end of a document before typing. Chanelle
|
|
|
|
Re: Build 57
Benny Barber
Yes, the loss is only in the custom keyboard.
toggle quoted messageShow quoted text
On May 6, 2018, at 1:32 PM, David Nason <dnason@gmail.com> wrote:
|
|
|
|
Re: Build 57
Santiago
I also noticed this. Not to mention, it seems to be more sluggish on my iPhone X than my SE.
toggle quoted messageShow quoted text
On May 6, 2018, at 11:03 AM, Chuck Dean <cadean329@gmail.com> wrote:
|
|
|
|
Re: Build 57
David Nason
I am kind of seeing this problem of losing sentences too. However it is only when the FlickType keyboard is on screen that this is the case. If I go back to the main email screen, with the standard iOS keyboard on screen, or no keyboard at all, then the full content of what I had typed is still there.
toggle quoted messageShow quoted text
Dave
On 6 May 2018, at 19:25, Benny Barber <rebelben@bellsouth.net> wrote:
|
|
|
|
Re: Build 57
Paul Sutton
hi all, I just thought I would say that I have also noticed that the prediction Engine is a lot more difficult to please when compared with the main app. However as yet i have had none of the memory issues that others have experienced, Paul.
|
|
|
|
Re: Build 57
Benny Barber
Michael,
toggle quoted messageShow quoted text
Have you had any problem losing text in the custom keyboard when you toggle between the custom keyboard and the iOS keyboard? I have been losing everything except the last sentence in the custom keyboard. Thanks. Benny
On May 6, 2018, at 1:06 PM, Michael Maslo <michaelmaslo04@gmail.com> wrote:
|
|
|
|
Re: Build 57
Benny Barber
I have not had any issues with the memory problem, but then again I have nut typed that much. I have had the problem of losing text except for the last line.
toggle quoted messageShow quoted text
On May 6, 2018, at 12:49 PM, Chuck Dean <cadean329@gmail.com> wrote:
|
|
|
|
Re: Build 57
Chuck Dean
Hi mike, what iPhone are you using, and what iOS are you running?
toggle quoted messageShow quoted text
Chuck
On May 6, 2018, at 11:06 AM, Michael Maslo <michaelmaslo04@gmail.com> wrote:
|
|
|
|
Re: Build 57
Michael Maslo
I have had no issues what so ever with the custom keyboard. No memory issues no nothing. My custom keyboard has been working so awesome.
toggle quoted messageShow quoted text
Sincerely,, mike
|
|
|