“iPhone 16 pro”

Hello, I switched to public version of iOS 26 few days ago, not because Im curios about new design and new look, the only and main reason was just to see if you fixed the most annoying problem that iPhone ever had, and yet you still did not fix it, which is sad, actually very sad! Since iOS 18 was released and iPhon 16 versions were released iOS on these phone was working worse then android phone that costs 200€ And its all caused because you tried to make some kind of intelligent refresh rate which makes no sense at all. You have 120hz panel and its not used in iOS at all, only when gaming and screen recording.Very sad. That kind of uselss intelligence is making phone very laggy and jittery in most of scrolling scenarios, 3rd party apps and apple apps as well. Im begging you, can you just let people choose to have it on auto or locked 120hz or locked 60hz, because using your lastest flagship is totally offending compared to how much it costs and how much

I installed iOS 18.4 on Friday evening, all worked well during Saturday and Sunday, Monday morning the Phone rebooted and appeared to have installed an Update, I didn´t notice, I was about to answer a WhatsApp and the TestFlight beta didn´t start up, a renew of the App was not possible due to TestFlight not being available. So I thought a reboot would help, but I did a reset, since then BOOT LOOP. I brought in recovery mode, updated with the 18.4 ipsw, no change - BOOT LOOP

Hello Developers, I am working on an app where I need to capture 48MP high-resolution photos using the ultra-wide camera of the iPhone 16 Pro while an AR session is running. The goal is to take these photos without interrupting or impacting the AR session, which uses the main wide-angle camera. Despite extensive testing and various approaches, we have been unable to achieve the desired functionality. What We Have Tried So Far 1. Using AVCaptureMultiCamSession: • We attempted to leverage AVCaptureMultiCamSession to simultaneously use the wide-angle camera for ARKit and the ultra-wide camera for photo capture. • However, this approach resulted in resource conflicts, with errors such as Cannot Record (OSStatus error -16409) and dropped frames. Additionally, the ultra-wide camera feed would frequently freeze or stop. 2. Dedicated AVCaptureSession for the Ultra-Wide Camera: • We separated the ultra-wide camera into its own AVCaptureSession while letting ARKit exclusively use the wide-angle camera

Hello, I am developing with the Nearby Interaction framework using third-party UWB accessories (Murata SR040/SR150). I observed a difference between U1-based and U2-based iPhones: iPhone 12 Pro (U1 chip) NINearbyObject.direction returns valid 3D vector (x, y, z). Distance and direction both work as expected. iPhone 15 Pro and iPhone 16 Pro (U2 chip) NINearbyObject.direction is always nil. Only distance is returned (around 0.35–0.40 m in my test). Effectively behaves as distance-only mode. Environment: Hardware: iPhone 12 Pro, iPhone 15 Pro iOS version: 18.5 Accessory: Murata UWB SR040 / SR150 App: Using NINearbyAccessoryConfiguration with BLE-based discovery Info.plist includes NSNearbyInteractionUsageDescription Camera assistance was tested both ON and OFF Expectation: I expected the U2 chip to behave consistently with U1, i.e. provide direction vectors when possible. Instead, on iPhone 15 Pro

Today I opened the camera using the camera button and noticed that when I tried to zoom in the slider button was not responding. Not sure if it’s related to iOS 26 beta which I have installed. Forced restarted the phone and the phone case is not covering the button. Thank you in advance for your help.