Alxa

I am still thrilled that they release updates which seem not even tested against bugs regarding core functionalities. Share-to-EN is such a fundamental functionality no way you do not recognize this bug if you do real world testing. Well I noticed the bug instantly on all my Androids, althoug being just a customer! Wow this is even worse with BS than with the former EN devs. Nothing to be seen of the announced quality over quantity the last six months 😔

That would be good. But I think they don't dare to cut off service for all those legacy only users yet. Look at the Android client. In 2023/01 around 30% of Android devices were running on Android OS versions <10 - given Google stats are correct. The new client never got access to these OS versions and probably never will (due to the resource hungry web framework they now use instead of the formerly native code). Ending legacy support could exclude a significant part of the (mobile only?) user base. But only EN could tell, they have the stats...

Exactly, thank you @eric99 for explaining my unfortunate literal translation of the german localized GUI of Evernote. If was considering using EN tasks even for my daily random tasks (which go the one standard note). But if this note does not get any history when tasks are edited this seems risky. I don't think, this is the intended behaviour.

Quick update on this: I did some tests over several days. adding, editing or deleting tasks within a note does not trigger note versioning . My note did not get any versions since initial creation of the note. Clearly a bug . I will not use tasks anymore if there is no versioning on this 😕

Maybe adding / changing tasks only in a note does not trigger the versioning process - which would be a bug. I will do some testing if I can reproduce this. Without versioning of task edits we definitely could not rely on tasks in EN.

On EN Win 10.58.3 displaying times for old and new notes (created on latest clients) for me vary between nice 1-2 seconds to 65 (!) seconds turning EN into an anti-productivity tool. Would be nice if @Federico Simionatocould post an update on this here. Thanks.

@ShankPossible As Evernote 10 is no native Android app but wrapped in the react framework in consumes ridiculous lot of ressource given the output you get from it. Having much RAM and a fast processor will certainly help to get EN on Android to a more usable performance (but never comparable no native apps). I noticed this with my devices. Jumping from a 4 GB RAM to 8 GB RAM device speeded things up by factor 4 or 5 I think for me. 12 GB RAM sounds like overkill 😉 But please, don't buy a new device if Evernote is the only pain you have on Android. Consider watching for native apps instead, this could be more sustainable.

I can confirm this bug with EN 10.51.1 as well. Adding to home screen results always in an instant crash of the app. Wow, for me they added 3 bugs (add image to note not corresponding, adding note to homescreen crashing, opening notes at the end of the note) with the last program update and did not resolve any of the long-term existing. I had hoped Bending Spoons would really invest in the core stability and reliability as CEO announced. But until now I cannot see anything of that. 😔 (Started a ticket as well)

Another RTE feedback on tasks: adding a task on EN for Android often ends up with multiple duplicate notes altough even edited on that one and only device. The dups then contain an empty task. Looks like a race condition bug which effects my slower devices... Something that even without RTE is not allowed to happen still happens with RTE. Still no robust user experience 😞

I checked this on my two Android devices and can confirm. The bug occurs on RTE-created notes as well. Submitted a ticket as well.

@Federico SimionatoI read the supplemental terms and it does not make clear, if my note content is sent to an external service for AI processing or not. Does the AI engine run on Evernote's servers, under Evernote's control or is it some (which) external service? In your posting it sounds like you sent information abroad. Without certainty I will likely not use AI features at all.

I disagree.The widget should not give the feedback "Saving note to General" as showed in the screen shot above. It should either give an error message or deny any input before instead. Saying it is saving without doing so is explicitly a bug. The fact, that the widget knows the notebook "General" although EN being logged out, seems there has to be a glitch in the interaction. Thanks to @Schmoranz for bringing it up to support. 👍🏼

Can confirm EN 10.51 for Android fixed the playback problem. 👍🏼

Update: I got a reply on my ticket by Hector C. (technical support specialist). He confirmed the - for over 2 years - ongoing image rendering bug. "The issue itself has been complicated to resolve but our developers continue to work on improvements, albeit, more slowly than we have hoped for." Wow, we are just speaking about displaying images consistently... Let's see if the announced quality over quantity approach of Bending Spoons really kicks in the next months.

Thank you @Scott T.. Does this mean, that the Android client will eventually get push sync for the widgets (updates of tasks / reminders in the background without client running)? The whole concept of Android home screen widgets and tasks/reminders makes no sense without that at the moment. Would love do see this finally working.

As the posting is gone. Could you please make transparent which point of code of conduct was broken. Thank you.

You can easily do a full backup export - one ENEX per notebook - with the legacy windows client. First log of so you see the login-window Then press CTRL+SHIFT+E and select the account to export. Evernote than creates a folder on the desktop and exports ALL notebooks into one ENEX per notebook. One keyboard shortcut + one click = Very convenient. Only downside: tasks are not included in the export.

There is another thread with the similar problem: I've seen the issue on my machine, too. During the last 2-3 days. But at the moment it is working again for me. Maybe there is something around with the new syncing method that affects account temporarily...

Addition: I now get the bug on all Android devices a lot, even on offline notebooks. Evernote on Android still stays an app you cannot rely on. It is so frustrating.

EN Android 10.50.3, still no bug fix. Seeing this even on new hardware with a lot of RAM and CPU every once in a while. Some day the images are shown, the other day not. And so on. It is definitely not a ressource issue but a programming bug nobody cares in development. Bending Spoons: Concentrating on AI stuff while not even being able to simply show my images? It must be a joke. Pay more for an app lagging essential bug fixing? No. (Started once more ticket:# 3682046 - Image cannot be rendered properly)

Exactly widgets do not update in background yet.

Noticed this as well, even on older Androids it is quite reasonable fast in sync now, whilst the clients are running. Hopefully they eventually add background sync finally to mobile to always have my offline notebooks and widgets fresh and up to date on all devices 🙏🏻

I still see the image rendering bug on mobile (Android) and when moving images between notes on desktop. It stays a pita. No way to even pay more now for this basic bugs not being resolved.

Hey, everyone can replace a battery on Android, too and we do this 😁. On my Android devices the one and only app which is that much resource hungry is EN10. If you use a native Android note taking app as OneNote, UpNote, or the gold old EN8.13.3 there is likely only little performance difference between a 4 year old device and a new one, I do not bother about it. Everything feels fresh. Using EN10 on react framework on Android you cannot use the app on the old device because it does not offer the excessive resources the react framework demands to work out something simple as displaying text and pictures. 😞 It is a problem a lot of react "apps" show on (my) older devices. I really hope Bending Spoons will dive more into this misery.