bridge OS is already at v3.2x or so.
Sure but my point is that it still feels young to me and it hasn't been around all that long to have earned 3 full releases.
bridge OS is already at v3.2x or so.
brainray - I haven't had any luck getting Photo Booth to cause an issue, but I have been able to replicate a video issue. I have an Envoy Pro EX 2TB portable, bus-powered SSD connected to my MacBook Pro. It dismounts sometimes randomly, and I have been able to get it to dismount three times now when a friend hangs up at the end of a long Face Time call (more than 15 or 20 minutes). I suspect all of these drive dismounts are related to this T2 chip/Bridge OS issue.This crash says that the camera <-> T2 connection seems to have a problem. You can also test the camera by recording the camera signal to Quicktime. My second MacBook only seemed to have this camera flaw, everything else was fine. I sent it back for a refund.
Is it acceptable for a 2000 Euro/Dollar++ computer to have a broken camera on arrival? IMHO not. This seems to be a common problem, that's why I mentioned it.
Mojave 10.14.2 is out..lets see if something is fixed
Yeah, how would they put that. "Fixes a cornucopia of issues with the T2 chip that we kept selling even though we knew it was causing all kinds of problems."I don't see anything in the change log for it, but I probably wouldn't really expect there to be, even if they did fix it. It would be good for people to update and chime in if there is any improvement on this fiasco.
Just got it installed ... appears the T2 firmware was updated to "16P2542" on my machine (2018 13" MBP). Fingers crossed ...
I am on 16P2542 for the T2 chip on 2018 MBP 15" as well.
I just checked my MBP that I special-ordered about three weeks ago, and it has firmware version 16P2088 on the T2 chip. So they were using that firmware when this was built (about two weeks ago).As in you were just updated to it on this new mojave update or thats an older firmware that you have already had?
For Mojave you have to look in system preferences for MacOS Updates. I think they did that to make it more like iOS.I just checked my MBP that I special-ordered about three weeks ago, and it has firmware version 16P2088 on the T2 chip. So they were using that firmware when this was built (about two weeks ago).
On a separate note, for some reason I don't see the new Mojave update in the App Store when I go to Updates. I've tried refreshing it. Maybe they stagger the availability to prevent heavy demand all at once?
Thanks! I did not know they had changed that. Another useless change that somebody could suggest and implement to justify their salary.For Mojave you have to look in system preferences for MacOS Updates. I think they did that to make it more like iOS.
This shows that they are actively working on this at least, if they are/were shipping new models with 10.14.1 but with a later version of T2 firmware. Plus if there are new builds at least every 2 weeks, promising sign for those affected.I just checked my MBP that I special-ordered about three weeks ago, and it has firmware version 16P2088 on the T2 chip. So they were using that firmware when this was built (about two weeks ago).
On a separate note, for some reason I don't see the new Mojave update in the App Store when I go to Updates. I've tried refreshing it. Maybe they stagger the availability to prevent heavy demand all at once?
As in you were just updated to it on this new mojave update or thats an older firmware that you have already had?
Personally I think it makes a lot more sense to update your operating system in ‘System Preferences’ vs the App Store...Thanks! I did not know they had changed that. Another useless change that somebody could suggest and implement to justify their salary.
I believe it updated to 16P2542 today when I went to Mojave 10.14.2
EDIT: Yes I just checked my records, I was on 16P2088 prior to today's update.
Well, so much for this update fixing everything. After updating to Mojave 10.4.2 (and the new T2 firmware), I was able to duplicate a problem I've been having, but with Photo Booth this time. With my Envoy Pro XE external, bus-powered hard drive connected to my 2018 MBP, it spontaneously dismounted (causing the Mac OS warning for not properly ejecting) when I took several photos with Photo Booth.BTW: have you done the Photo Booth test? Open PB, switch to video mode and start recording. Let the computer record like 2 hours. Many of us have crashes/KP within this time. If you have this one, I'd return it without talking to the GB guy.
Right? We'll see...I guess only time will tell if this fixed much. For those that were affected by bridge OS errors and just updated, any status updates throughout the next week or so would be helpful. Fingers crossed.
I just received 2018 15” MBP, 2.6/32g/512gb and got first KP this morning on Mojave at work with no accessories attached. I plan to update to 10.14.2 in the morning.