I use: VScode, Idea, iTerm2 (with x86 brew), Logic (and lots of plugins), FCPX, Live (x86, and lots of plugins), Slack, Reeder, MS Office, Spotify, Chrome and other stuff. MBP M1 16GB.
What I do get, is some bluetooth issues (e.g. affecting the mouse cursor. If you start the bluetooth deadmon it fixes itself for a day or so.
Nope. My AirPods have regular issues and my Magic Mouse regularly disconnects.
I hoped my next M1 would solve it. Guess not.
EDIT: Perhaps the parent means Helvum, which ldd says links to libgtk-4.so.1 => /usr/lib/libgtk-4.so.1. However, I can't figure out how to open a popover (https://python-gtk-3-tutorial.readthedocs.io/en/latest/popov...) in the app; all I can do is drag to create or break connections.
I haven't tested EasyEffects. With that in mind, PipeWire is buggy AF for the time being, and I've been working over the past week to clean things up (fixed a few bugs in plasmashell and pipewire so far, but I'm still learning and there's a great deal of bugs I haven't diagnosed and explained to the maintainers, it will probably take weeks longer for me to work through everything, and I'd very much prefer the program was written to handle race conditions and edge cases properly, instead of leaving users to discover bugs and trace the root cause through the labyrinthine IPC-heavy event-driven codebase after the fact).
An advantage of C is that it comes with a stable ABI, where Rust is unstable and C++ is a subject of conflict (though you can achieve a stable ABI by restricting your external API to C functions, and if you want cross-shared-object virtual calls like Pipewire, you might have to write the same pile of macros as PipeWire, which you were trying to save yourself from). The downsides are memory and type unsafety (surprisingly the only crash I've seen so far is a null pointer dereference, and I haven't hit any obvious memory or type errors), and a complete absence of "vocabulary" or templated types (they've created their own slotmap-like ID allocator but without a generation count resulting in ever-present "logical use-after-frees" in library and application code, and an intrusive linked list which they use even when hashmaps might provide somewhat faster iteration and asymptotically faster search).
The saving grace is that it can at any time be switched over to be built with a C++ compiler, and then start to be modernized incrementally.
It would be cool (not necessarily useful, probably not a good use of time) to rewrite it in Rust while keeping the dependency count in the single digits. It would be helpful to contributors to add architectural documentation.
I finally gave up on using an XPS15 with Ubuntu because I could not get over the fact it cannot do high quality bi-direction bluetooth audio.
Edit: Looks like it does offer some improvments over pulseaudio: https://www.redpill-linpro.com/techblog/2021/05/31/better-bl....
Throw hardware at the software problem, because software absolutely cannot be trusted not to foul this up. Not Windows, not linux, not pipewire, not pulse, none of it. Evidently not mac either, though I've personally never had trouble with bluetooth on mac. Bluetooth is 23 years old and its flagship application is still completely broken across huge swaths of the client/server compatibility matrix.
But actually, since switching the AV sync is off using my Bluetooth earphones, at least in Firefox.
Curiously, I can fix it with latency adjustment in pavucontrol, but it only has an affect when the 'advanced' drop down is revealed in that tab of the menu. Close it, and it's off again. Open, and the value has persisted, and it works again. Haven't really dug into that because I've been hoping the (presumably) underlying Pipewire issue will be fixed.
Pulse is still broken a year later, pipewire is fixed.
So it goes.
That is not to say Pipewire could not also be a problem, but I haven't encountered such complaints about it.
I think you're right about this. I have a pair of JBL headphones and it will just randomly become completely garbled during a video conference under Windows.
I have to disable/re-enable Bluetooth to "fix" it. It's a mess.
The bug isn't that bad if all you use bluetooth headphones for is YouTube, video chat, and music but it makes Anki language learning decks with audio almost unusable.
I'm more familiar with BLE, which is better, but even that has a completely weird "characteristics" protocol that you have to use. Want to send a big blob of data? You have to manually cut it up into 20 byte chunks to send it over "notifications".
It's like they looked at the OSI model and thought "ah yes this looks right! we'll implement all the layers!"
Doesn't really make sense for a new CPU/GPU to fix the problem, what you want is for Apple to stick in their own networking cards.
See my other comment in this thread about how i solved "windowserver".
Bluetooth issue was a hw proximity issue for me. My CalDigit hub was mounted right below my Macbook. I noticed when I moved my MacBook's location (still connected to hub), the bluetooth issue when away.
It's worth a try if you have a powered accessory near your macbook and haven't tried this already, but...
I do still get the issue once in a while, but I can now at least just turn the keyboard/touchpad off/on and it goes back to normal whereas before, it happened all the time.
Once in a while I still have to Shift+Option+"bluetooth menu icon" and reset bluetooth module.
I know these are just work arounds, but at least it allows me to get back to work and only have to deal with it weekly instead of not being able to use bluetooth at all.
Edit: just upgraded to 12.0.1 and noticed Shift+Option+"bluetooth menu icon" to reset bluetooth module is gone!?
Only issue I've seen with it is some bluetooth flakiness sometimes the way you mentioned. Other than that, it's been a rock solid device and the only reason I haven't upgraded to one of the new MBPs despite really wanting one...is because so far I haven't been able to justify it yet considering how rock solid the M1 has been!
My guess is faulty hardware. I've had plenty of those on the 2018 MBP (keyboard getting stuck, bulging battery and dead zones on touchbar). Waiting to see if the QC is better with new M1 Pros before buying.
Otherwise I have been very happy with the laptop.
That sounds like a big bug and a very possible cause.
Can you elaborate on this? I think i was hitting this as well. Specifically when I scroll or type, it "halts" for a split second every other second. Originally I thought it was a video card failing or something but after a long time I finally traced it to Bluetooth. Since then I have been using wired connection on my keyboard and mouse.
What do you mean by "If you start the bluetooth deadmon"
I've heard this happens when you have some USB-C hubs attached, which I do. Not sure what the connection is -- but I think my Anker hub does causes this.
>What do you mean by "If you start the bluetooth deadmon"
Sorry, I meant: "if you restart the bluetooth daemon", e.g. "sudo pkill bluetoothd".
a little unclear if you don't have a hub, or do have an Anker hub, but try moving the Anker hub far away from your Macbook and see if you still have the bluetooth issue. You need a USB cable (depending on what's the hub is you might need a 3.1 Gen2) long enough.
For me it was a hardware proximity issue. Powered external devices interfering with the Mac's bluetooth.
I'd wager most people on this thread do not actually own an m1 Mac.
My experience (and that of others I know that have them) has been nothing but stellar.
https://www.theatlantic.com/family/archive/2021/11/group-nar...
Most recently, the Thunderbolt 3 issues were responsible for countless hours of lost time rebooting my laptop last year, and I’m not alone: https://rachelbythebay.com/w/2020/10/03/repro/
The weirdest part was that this occurred with only Apple products connected to my laptop. I couldn’t even blame it on 3rd-party products. It also worked perfectly fine before and after the range of affected MacOS versions. There were many reports of the same issue all over the internet, so I know I wasn’t alone.
Then one day Apple finally fixed the bug and everything was back to normal. But all those months of constant reboots and crashed and failed workarounds left a mark on my overall experience.
So while the Mac experience is generally good, it’s still far from perfect. Weirdly, I’ve had far fewer problems with my Windows system in recent years.
My Mac used to expose the same kind of problems, that's why I switched to Linux on non Apple laptops years ago.
My feeling was that the quality of the OS went down constantly and apparently it's not coming back with newer releases.
Its not like Apple doesn't release faulty hardware and software. Butterfly keyboard is a good example of faulty hardware and OSX Lion crashed all the time on the Macbook pros with discrete GPUs till Apple patched it.
I have absolutely no doubt that this person is having bad memory leaks (though their narrative about SoC memory or other elements seem unlikely to play any part whatsoever). Software has faults, and something in their environment or stack is causing problems. I have an M1 Mac and used every beta of Monterey, and now the release, and have had zero problems. Like nothing at all. I use XCode, IntelliJ, Chrome, Safari, Excel, Logic Pro among others all day long, heavily. Loads of other people seem to be having no problem with their systems. Eh.
If something has literally millions of users, saying "{X} happens" will invariably draw out someone with a similar anecdote, but that doesn't mean it happens to everyone, or even a significant minority. Some unique combination of factors is yielding a poor user experience, and hopefully there is a resolution, but it just doesn't seem likely that it's widespread.
Why do I see so many pro-Apple posts then? And even posts directly pointing to an Apple ad.
Because such generalizations are just encodings of personal likes/dislikes in the form of general claims, they lead to lame discussion.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...