Yes and yes to your questions. Thanks.
1 Like
Thanks. We are just testing a version that seems to have the issue resolved. We will be pushing to all users soon in the next release. Thanks for your patience.
5 Likes
I have the latest version of the iOS app. I experienced the freezing issue a couple of times yesterday, 30th December. It seems to happen particularly with long texts. I think the one I was using was 23 pages in Lingq. It happens when you click a word to form a Lingq or to re-read a yellow Lingq. Sometimes I have to wait a very long time. Sometimes it totally stops, though maybe if I waited two or three minutes it might eventually work again. The only solution is to close down Lingq and restart the app. Then it’s fine again. I switch the audio off, empty the audio cache, etc. Doesn’t make any difference. Happy to help in any way I can (screenshots, etc.).
3 Likes
Same here with videos.
Thanks @sfoxall and @LeifGoodwin , the issue is that it isn’t possible to recreate easily. At any rate, our latest version seems to be working well for me and not having this issue. It’s currently under review by the App Store so should be available soon.
3 Likes
I thought someone said elsewhere that to have translations available like on the web, we have to use the web browser, that the full experience is not currently supported on the app.
So I’m confused here.
1 Like
I’m not sure where you heard that but the mobile app experience on Android and iOS is excellent and probably gets more use than the web version, especially from power users. The mobile web experience is definitely sub par and not very well supported on our end. It is simply too difficult to achieve the desired functionality on a small touchscreen on the mobile web. If you haven’t already done so, you should switch to the mobile apps on your phone or tablet and only use the web app on your desktop.
2 Likes
Only thing I can think of is he could be talking about “Show Translation” in page view, which does not exist in the Android app. As a result, you have to go to sentence view to get a translation, and those translations often don’t line up with the text.
I’m finding the points counting pretty flaky in the web version … roughly once a week I get an email saying I lost my streak, when according to the web interface I’ve met my daily goal. The updates on the daily goal often jump around from say 20 to 50 to 80 without me doing anything that I know of.
If I could turn off the streak counting I would. It’s just annoying and worse it’s inaccurate.
1 Like
Yes, it is true that that feature doesn’t exist on the mobile apps. It just isn’t possible to show the translation under the text like we can do on the web. However, most lessons translations should line up. If not, please share the URLs so we can get those fixed. Also, in sentence view, if the translation is poor or inaccurate, you can tap the refresh translation button to generate a new translation for the sentence.
1 Like
As long as you complete your goal on Web, it should be maintaining your streak properly. You may want to check that the emails that you’re getting are all for the same language. It’s possible to have different goals set for different languages and to have streaks active in one language while getting a streak reminder for a different language. We’re not aware of any issues with the streak goals changing automatically.
1 Like
Lol. I only read the title but the answer is “Yes”
I’ve been using it for some years.
4 Likes
There seems to have been a major automatic update in the app. I didn’t have to reinstall anything. I’m delighted to report that so far it’s looking very good. No slowing down at all. Early days maybe, but congrats and thanks.
2 Likes
Something happened to Chinese word splitting in the last day or two. Instead of being just randomly wrong as it’s been for a while, suddenly, particles, prepositions, etc. are consistently being attached to words around them, creating a huge number of phrases that should not be phrases.
Here is an example lesson: https://www.lingq.com/en/learn/zh/web/reader/36109033
In this lesson, you can see many examples where 的 should be a separate word but is attached to preceding words resulting in a huge number of nonsense phrases like 漂亮的, 非常的, 很长的, and 看到的 that result in hundreds of nonsense new and unknown LingQs.
This is more than a little frustrating.
Here is what I want to do, and maybe some helpful person can give me pointers: I want to turn on a 30 or 40 minute audio that I uploaded to linq, and go out running or walking.
When I don’t understand, I want to look at the screen to see a translation of what I just heard.
I have not figured out how to make the app display scroll along with the audio it is playing, and I have not figured out how to make it show the translation.
I’m pretty sure I do not want to use sentence mode–wouldn’t that require hitting “go to next sentence” nearly constantly, and having the audio stop all the time, every time it finishes a sentence?
2 Likes
There is a karaoke mode, where the text scrolls with the audio, but you cannot see the translation in that mode afaik.
The only way I see you can accomplish what you are looking for is to create a translation of the text and then create a subtitle files with the timestamps according to the audio (this should be doable with AI). You could use that + the audio to create a lesson where the audio is in your target language, but the text is the translation, and use that in karaoke mode.
1 Like
Yes, all software has bugs. No, not all software has as many bugs as LingQ.
I’ve been using personal computers since the Apple II and programming professionally since the Macintosh. I’ve never used any commercial or open source software as buggy as LingQ.
Because of this I use the bare minimum of LingQ functionality. I import text files, then read/listen through them in Sentence Mode. That’s all.
Trying to do anything more complicated in LingQ has always been more trouble than it’s worth.
The codebase needs to be rewritten from the ground up, but we know that’s never going to happen, so this is the way LingQ has been, is currently, and always will be.
2 Likes
It’s also working really well for me too. I won’t congratulate the team as IMO such severe bugs in basic functionality should never appear. The pop up dictionary dialogs are still more trouble than they are worth, a traditional dictionary is quicker and better.
You’re right about basic functionality, but at least they responded by taking on board the complaints and doing the necessary work. There’s nothing out there that does what Lingq does, so it’s important to me that they fix things.
The next battle will be about the bugs in the lesson import function. There are workarounds but they’re annoying.
Meanwhile, have you tried the AI audio transcription function in the browser version? Astonishing!
1 Like
I haven’t. I have no idea what that is.