From notebookcheck,

Microsoft's answer to the Apple MacBook Pro, the Surface Laptop Ultra, comes with the novel Nvidia RTX Spark line of processors and an oddball display choice. Not that the Mini-LED panel of the Microsoft Surface Laptop Ultra isn't bright and beautiful, as tested in our review, but it comes with issues like screen flicker, ghosting, lack of local dimming, or slow response times, and most of these can't be fixed with software.

https://www.notebookcheck.net/Microsoft-fixes-Surface-Laptop-Ultra-screen-flicker-and-boot-times.1434395.0.html

Hi everyone,

I recently unboxed a brand new, sealed Surface Go 3 that had been sitting unused in its original box for a few years. Unsurprisingly, it was completely dead out of the box and wouldn't turn on or take a charge via the charger.

Since the battery has 0 cycles and is practically brand new, I opened the tablet to see if I could recover it. I manually brought the cells back to nominal voltage, but the Surface Go 3 still refuses to recognize the battery or power on.

Attached is a close-up photo of the battery's BMS board. My current theory is that the modern smart BMS registered a Permanent Failure (PF) hard safety lock due to prolonged deep discharge, shutting down the MOSFETs and blocking communication with the motherboard.

Before I give up and order a third-party replacement battery, I wanted to ask if there is any known trick, software reset, or manual procedure to signal this specific BMS to clear the lock. Has anyone successfully revived a hard-locked BMS on a Surface device without a full IC reprogramming setup like a TI EV2400 or NLBA tool? It’s really frustrating seeing a 0-cycle original battery go to waste over a firmware lock, so any insights would be greatly appreciated.

Hey all, I just encountered this weird issue. I'm charging my SP11 with a 65w usb c charger for the first time. Immediately after plugging it in, the entire OS slowed to a halt and the keyboard mouse works on and off- the haptics will stop working, most inputs are delayed or missed. Makes getting any sort of work done impossible.

Unplugging the charger immediately fixes the issue. Plugging it back in reproduces it.

Has anyone encountered this before? Any idea why this is happening? Thanks.

I'm an IT student planning to use this device for school projects and development work, mainly with:

• Arduino IDE
• Android Studio
• Antigravity
• Visual Studio Code
• Git

Aside from programming and IT-related tasks, is this device good for everyday use as well? I'm also wondering if it's still worth buying considering I'll continue using it after graduation. Do you think it can stay reliable and capable for at least 2+ years?

What are the biggest pros and cons of this device? I'd appreciate any insights since I need to make a decision ASAP. Thanks!

My first surface pro has been a great experience. Lucked up and got a like new pro 5 16gb for only $100.

I’m the developer. I built this because OneNote on Windows always made me stop writing to go and find a tool,

For Surface pen users in particular:

• hold the side button and the pens, colours and undo open in a ring around the nib
• pressure ink, palm rejection, and shapes that snap neat when you hold still
• mark up lecture slides and PDFs while it records the lecture
• search finds your handwriting

It’s in the Microsoft Store, it’s free during the beta, and you don’t need an account. I’d really like to hear how it feels on different Surface models, and bug reports are very welcome.

deltella.com

a few months ago i made varan, pale moon for windows rt. to give it a working javascript jit i ported spidermonkey's arm backend to thumb-2, and that's where i learned the hard rule of rt 8.x: it only runs thumb-2 code. plain arm (a32) code just dies there, while the same code runs fine on the windows 10 build 15035 that boots on these tablets.

then i wanted a real modern browser on them, so i started venetium: chromium 150 ported to arm32 for the surface rt and surface 2. it worked on 15035, but not on rt 8.x, for the same reason: v8, chrome's javascript engine, makes and emit a32 code, and even its built-in code is a32. so not even a jitless build could start there.

so i did for v8 what i did for varan: ported v8's arm32 jit to thumb-2, every tier (sparkplug, maglev, turbofan, liftoff, wasm), and filled the windows 8 api gaps inside the browser itself. now venetium 1.3 runs on my surface rt

with windows rt 8.1, with the jit on and the sandbox on (limited btw).

two builds, installer or portable:

- **arm32**: windows 10 build 15035

- **arm32-thumb2**: windows rt 8.0 / 8.1 (needs a jailbroken rt; tested on 8.1, not on 8.0 yet)

download: https://github.com/hamed7ir/venetium/releases/tag/v1.3

the v8 port: https://github.com/hamed7ir/v8-thumb2-rt

varan: https://github.com/hamed7ir/varan

if you still have a surface on rt 8.0, i'd love to hear if it runs.

Laptop will charge for like 30 seconds after connecting the mag charger than stop charging until I unplug the charger and plug it back in where it will do the same thing, what’s wrong with it?

Hey all,

I've got a Surface Laptop 4 15" that's gone completely dead on me.

For a while it was randomly shutting down on me, and a couple of times it wouldn't charge for a couple hours/ 1 day, then it would just start working again like nothing happened. Now it won't charge or turn on at all. Nothing happens on the Surface Connect charger, and USB-C doesn't do anything either.

I'm comfortable opening laptops and have already opened this one to take out my SSD, so I'm happy to take it apart. What I really want is to diagnose the problem properly before I spend money on parts, rather than guessing and buying a new Surface Connect port or battery for nothing.

Right now I'm leaning towards the battery, mainly because of the random shutdowns, and because USB-C not working either makes me think the port alone isn't the problem.

My main question: how do I check if the battery is actually working when I can't turn the laptop on?

Thanks in advance, any tips or horror stories welcome. I'd rather hear them before I start poking around inside.

If you're on SP11 or 12 and you have a Thunderbolt dock with 10GBE using Aquantia (AQCxxx) chips, Marvell has now created drivers. Tested good on my OWC dock which uses AQC107.

Go to Marvell driver download page: https://www.marvell.com/support/downloads.html# and follow: (You need to select AQC113 to make the driver show up. Not guaranteed to work on all Aquantia chips, but mine although being 107 still works with this driver)

The drivers are super new, built on Oct. 12th and released on Oct. 17th