Brave Browser Windows Arm64
Zee Palmer
Brave now offers a fully native version for ARM64 Windows. When you newly install Brave on your ARM64 device, then you get an even faster browser. Read on to learn more, or skip to the end to find out how to get the new version.
Newer CPU architectures are usually able to run programs with an older architecture. For example, an x64 CPU can run an x86 program. Likewise, ARM64 CPUs can run x64 and x86 programs. But there is a significant performance overhead. In the example of Brave, you could run x64 Brave on an ARM64 computer. But it would be slower than it should be. We therefore spent considerable effort last year to offer an ARM64 version of Brave for Windows.
The second main technical hurdle was caused by an optional and downloadable component of the browser called Widevine. Web sites such as Netflix use this component to protect their content. If you do not have the Widevine component installed, then Netflix (and similar sites) may only serve you low-quality videos, if anything at all.
More and more new Windows computers have ARM64 CPUs. In order for Brave to be as fast as possible, it needs to be optimized for this architecture. We completed this technical work last year. There were some technical challenges on the way, but we were able to overcome them. You can now install ARM64 Brave on Windows 11 by visiting brave.com!
Michael Herrmann is the founder of Omaha Consulting, a software development agency that has been providing services to Brave since 2019. You can find more information about him on his personal website,
One of the first challenges we tackled was to completely rebuild the Create Slideshow workload. In MobileXPRT 2015, the workload uses FFmpeg to convert photos into video. FFmpeg utilizes a C++ executable, and it needs to be compiled differently for different architectures such as x86, x64, arm32, arm64, etc. With each new Android version, the task of maintaining FFmpeg compatibility with numerous architectures and Android versions becomes more complex. MobileXPRT 2015 still works well on most Android devices, but we wanted a more future-proof solution. In MobileXPRT 3, the Create Slideshow workload will use the Android MediaCodec API instead of FFmpeg. This change enables the workload to run successfully on devices that could not complete the workload in MobileXPRT 2015.
We are updating the test content of the following workloads: Apply Photo Effects, Create Photo Collages, Encrypt Personal Content, and Detect Faces to Organize Photos. We will replace items such as photos and videos with more contemporary file resolutions and sizes where applicable.
At over 305,000 runs and counting, WebXPRT is our most popular benchmark app. Device manufacturers, tech journalists, and developers around the world use WebXPRT because test runs are quick and easy, it runs on almost anything with a web browser, and it provides reliable data about how well devices perform when completing real-world tasks.
The XPRTs have been very successful on desktops, notebooks, tablets, and phones. People have run WebXPRT over 295,000 times. It and other benchmarks such as MobileXPRT, HDXPRT, and CrXPRT are important tools globally for evaluating device performance on various consumer and business client platforms.
Recently, both community members and others have asked about the possibility of the XPRTs moving into the datacenter. Folks face challenges in evaluating the performance and suitability to task of such datacenter mainstays as servers, storage, networking infrastructure, clusters, and converged solutions. These challenges include the lack of easy-to-run benchmarks, the complexity and cost of the equipment (multi-tier servers, large amounts of storage, and fast networks) necessary to run tests, and confusion about best testing practices.
Please respond with a confirmation that my issue has been identified as a problem with other (M1) MAC-based end-users and if this issue is currently being worked on and what your timeframe is in getting this resolved.
This issue does pop up on the forums for both Windows and Mac desktop versions. From memory it is generally an intermitent problem. Certainly in my case it is very intermitent and I have been unable to identify which particular images or actions cause a probelm.
Sadly your post lacks so much detail that I am unable to try to see if I always get the issue in your situation. If you really do want feedback from other users then providing more information would help e.g
I've tried to reproduce the problem, but so far with no luck. For me the problem is definitely intermitent so I'm not that surprised. Also note that although I am also using 10.52.8 it's Windows so it may be that this is an area where there are differences between operating systems. Pedrhaps somebody with similar hardware will try, now that you have provided a very detailed description of what you are doing.
Another abnormal image file behavior that I've encountered (just within the Evernote environment) is an inconsistent copy & paste procedure between two different notes (within the same notebook & between notes in different notebooks).
When using the menu-based copy & paste method to duplicate an image file (that clearly appears in preview mode) from one note to another, the image file (when pasted into the receiving note) only appears as a TITLE. Even when accessing the drop-down menu, no matter which option is selected (TITLE or PREVIEW) TITLE is the only outcome or result.
There have been other unexplainable instances where I've successfully pasted image files into notes (appearing in PREVIEW mode) only to have them convert to TITLE mode after leaving notes and returning to them. Then, again, accessing the drop-down menu, and attempting to change to PREVIEW mode, TITLE is the result.
I suppose it is always going back to basics. Does the same happen on the web version? If it is OK there it could be as simple as needing a database refresh on the desktiop version. I recognise all the symptoms you describe as things that have happened ocassionally but for me many of the issues seem to have been resolved and certainly are only intermitent. To refresh the database sign out of your account and choose "Remove my Evernote data from this device". Then sign in again.
I have been using Evernote's desktop application exclusively. I will use Evernote's web app and monitor if this same app behavior is exhibited within that environment. With that option, it's mindful to be aware of which web browser(s) to use and which to avoid. Depending upon the web browser of choice, that has the potential to lead to its own set of unusual or unpredictable application behaviors. The more I use software, the more I have a deep respect for developers who are constantly confronted with issues like mine. Software is a product that is in a constant state of flux due to the environments and hardware it operates within and interacts with. Software developers have a very challenging occupation; one that is unrelenting (in the issues encountered) with each iteration of any given software application.
Because of my software beta-testing experiences, I still look forward to seeing a resolution to this issue and its root cause(s). In most cases, the problems that I've encountered over the years have usually been caused by a basic hardware issue, a software update, etc. thereby quickly resolving an issue that would otherwise be thought of as incapable of being solved.
After just a few hours of using Evernote's web app (accessing it within the Web3-based Brave Browser, which is a Google Chrome-based web browser - Version 1.47.186 Chromium: 109.0.5414.119 (Official Build) (arm64)), I'm encountering the same issues that are present in Evernote's desktop application. In addition, jpg images as small as 200 kb (when they occasionally do appear in PREVIEW mode) take minutes to appear. Overall, I'm encountering the same behaviors.
c80f0f1006