iPhone Aux Cord for Car, AONISHI [Apple MFi Certified] Lightning to 3.5mm Audio Cable Headphones Jack 13 12 11 XS XR X 8 7 iPad Home Stereo, Speaker, Headphone, DA-006, 3.3 feet

AONISHI Apple MFi Certified Lightning to 3.5mm AUX Stereo Specifications: Apple MFI Certified Chip Color: White Cable Length: 3.3FT / 1M DAC Sound Chip 100 percent Coppery Core Material: TPE + Gold-plated 3.5mm conductor Advantages of AONISHI Lightning to 3.5mm Cable: 1. Apple MFi Certified Ensures completely and securely connect with your Apple devices, 100 percent compatibility to the iOS system without error message. 2. Multi application Easy to connect your Apple Devices to car stereos, home stereos, portable speakers, headphones, Hi-Fi, computers, or anything else with a 3.5mm input jack. 3. Super Sound Sampling rate up to 48kHz, 26bit and filter out noise. Provides a clear with no breaks quality sound. 4. PlugandPlay Just insert the lightning head into your Apple devices and insert the 3.5mm male, like Car Audio, Headphone, Hi-Fi, Computer Stereo, Bluetooth Speaker and so on. 5. LightweightandPortable It is very lightweight, easy to store, not winding, not knotted, can be foldable, easy to carry around, great for home and travel. Perfectly Fits to: iPhone 13 / 13 Mini / 13 Pro / 13 Pro Max iPhone 12 / 12 Mini / 12 Pro / 12 Pro Max iPhone 11 / 11 Pro / 11 Pro Max iPhone X / XR / XS / XS Max iPhone 8 / 8 Plus iPhone 7 / 7 Plus iPhone 6s / 6s Plus iPhone 6 / 6 Plus iPhone 5c / SE 2020 iPad / iPod Support iOS 10.3 and later, including iOS 14. Warm Tips: This Lightning to 3.5mm Stereo Audio cable does NOT support music control and phone calls. This lightning to aux cable needs to directly connect with lightning devices, CANNOT work with an extra lightning adapter. What You Get: 1Aux Cord for iPhone (White) A 36-Month Worry-free warranty and 7/24 Friendly After-sale Service.

ASIN

B09D7NX835

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

6ms·cache hitGET /v2/namespaces/amazon-products/documents/B09D7NX835

How it works

Similar query

22msnearest_to_id → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query asks Layer for nearest neighbors of the stored product vector — queries don't go through the doc cache, so no cache header is set.