



I wonder if the iPhone 17 pro/max front clip will work in place of the 16 pro/max front clip for the OtterBox defender pro cases. Since the 17 series have the camera control protection and otterbox wont revise it for the 16 series it really makes me wonder. Looking at the two they seem to have the same contact clip points. Can anyone test it?
So about 2 weeks ago I water damaged my 16PM. No big deal just send it into apple for a AppleCare claim and get a fresh new phone. I request the service, pay the repair fee for a whole unit replacement. Now just wait for a recovery kit to send the damaged device off. I've been stuck here for nearly 2 weeks now. I spoke with a senior advisor today and they told me that my configuration was out of stock. So what do I do? They told me I have to wait for my configuration to be restocked and that there is no known time it will be available again. So I've paid for an AppleCare replacement but actually indefinitely lost my phone. Has anyone else had this experience? What am I supposed to do now? To be a trillion dollar company you'd think they would have at least one device in stock that was last years top of the line model.. especially for someone who pays for their premium service.
I’m looking into a long-term project to run a GM HMI 2.5 system (2016-2018 Silverado/Sierra generation) standalone in my 2010 GMT900 Silverado.
I know this is NOT a simple swap and that the newer K2XX infotainment architecture is very different from GMT900, but I’ve seen proof-of-concept standalone HMIs running outside the original vehicle environment, so I’m trying to understand what’s actually required to make one functional beyond just powering it on.
My goal would be to retain as many OEM-style functions as possible:
- audio output through the factory or aftermarket amp/speakers
- vehicle speed data
- engine temp/coolant data
- steering wheel controls
- reverse camera
- potentially door/chime/status data later on
From what I understand so far:
- HMI 2.5 depends on both the HMI module and A11 radio module
- VIN/theft lock and SPS programming are major hurdles
- CAN traffic spoofing/emulation may be required
- some modules communicate over MOST bus depending on configuration
What I’m mainly trying to figure out:
I’m not expecting plug-and-play. I’m more interested in the reverse engineering side of it and building a modern OEM-style infotainment retrofit into a GMT900 platform.
Any info, forum threads, DBC files, CAN logs, or module dependency knowledge would be appreciated.
I’m looking into a long-term project to run a GM HMI 2.5 system (2016-2018 Silverado/Sierra generation) standalone in my 2010 GMT900 Silverado.
I know this is NOT a simple swap and that the newer K2XX infotainment architecture is very different from GMT900, but I’ve seen proof-of-concept standalone HMIs running outside the original vehicle environment, so I’m trying to understand what’s actually required to make one functional beyond just powering it on.
My goal would be to retain as many OEM-style functions as possible like:
- audio output through the factory or aftermarket amp/speakers
- vehicle speed data
- engine temp/coolant data
- steering wheel controls
- reverse camera
- potentially door/chime/status data later on
From what I understand so far:
- HMI 2.5 depends on both the HMI module and A11 radio module
- VIN/theft lock and SPS programming are major hurdles
- CAN traffic spoofing/emulation may be required
- some modules communicate over MOST bus depending on configuration
What I’m mainly trying to figure out:
I’m not expecting plug-and-play. I’m more interested in the reverse engineering side of it and building a modern OEM-style infotainment retrofit into a GMT900 platform.
Any info, forum threads, DBC files, CAN logs, or module dependency knowledge would be appreciated.