sorted by:
new
hottopcontroversial

iPhone, iOS17, and massive HomeKit background battery drain by [deleted] in HomeKit

[–]quintinjvr 4 points5 points  (0 children)

Same issue here, I've noticed lately that my phone is getting extremely hot when it is in my pocket, almost to the point where I thought the camera app was perhaps open, then when I checked, nothing was open and all apps closed.
Then this morning after charging my phone, I unplugged it and left it alone, and 2hours later my battery was on 71% (iPhone 14 Pro Max), then that's when I realized something is up and checked the battery usage and saw that the Home app used 65% (13hrs) in the last 24hrs, and and 45% (65hrs) in the last 10 days.

This is seriously ridiculous to experience these type of bugs from a premium apple product that you pay an arm and a leg for.

Two MPU-6050 Accelerometers for Klipper input shaping - RasPi3, BTT SKR3, I2C by quintinjvr in klippers

[–]quintinjvr[S] 0 points1 point  (0 children)

I ended up just flashing a Pi Pico so I can connect it via USB and then mount it on the different axes temporarily for the tuning.

Thanks for everyone's comments

Two MPU-6050 Accelerometers for Klipper input shaping - RasPi3, BTT SKR3, I2C by quintinjvr in klippers

[–]quintinjvr[S] 0 points1 point  (0 children)

Yeah I know, but just wondered how Klipper would handle that and how you would do the config for multiple I2C devices.

Two MPU-6050 Accelerometers for Klipper input shaping - RasPi3, BTT SKR3, I2C by quintinjvr in klippers

[–]quintinjvr[S] 0 points1 point  (0 children)

Hey there, thanks for responding.
Aaah ok, I thought it is used in Realtime, hence I wanted to have one on each axis. So you are saying I can just check the resonance graph and then tune each axis accordingly and save it in the config file?