Fisker Ocean key fob problems

Filed May 17, 2026 · Driver assistance · NY

FORMAL DEFECT AND SAFETY HAZARD COMPLAINT TO: the federal safety agency Office of Defects Investigation (ODI) 1200 New Jersey Avenue SE, West Building Washington, DC 20590 DATE: May 17, 2026 SUBJECT: Urgent Request for Recall Investigation: Systemic Cloud-Dependency, Hypervisor Power Management Failures, QNX Boot-Looping/Blackouts, Unix Epoch Clock Drifting, High-Voltage Contactor Thermal/Fire Hazards, and Core Low-Voltage Module Malfunctions via Telematics Disconnection in the Fisker Ocean Fleet 1. Executive Summary This petition requests an immediate, systemic safety defect investigation into the software architecture, operating system stability, power management, and network subsystems of the Fisker Ocean vehicle fleet (Model Years 2023–2024). Following the liquidation bankruptcy of Fisker Inc. and its affiliates—under Case No.XXX (XXX) in the U.S. Bankruptcy Court for the District of Delaware, overseen by Judge [XXX] —the vehicle's intellectual property, cloud infrastructure, and over-the-air (OTA) software management assets were assumed by a commercial entity, American Lease, and its vehicle management arm (OV Loop/Ocean Loop). Due to the subsequent imposition of a predatory $499/year subscription paywall, thousands of retail owners have been cut off from cloud connectivity. While a missing cloud connection in a standard passenger car traditionally results in a benign loss of convenience features, in the Fisker Ocean's "software-defined" architecture, it triggers a severe, un-throttled software failure loop. This architectural defect forces safety-critical operating systems into permanent boot loops, pins CPU utilization, drops the system clock into a broken chronological state, and drives an aggressive parasitic drain on the 12V battery system. This directly leads to cascade control module failures, key fob inoperability, and accelerated mechanical degradation of high-voltage components, introducing an acute INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION AC

Filed Aug 6, 2025 · Brakes · CA

In May of 2025 we received this email. We have written them 10 times with recall info and also in need of service. We have never received a response. We would love to get the car looked at and fixed, but no one has been able to help us. Our first 6 months with the vehicle, the key Fob stopped working multiple times and I had to get someone to pick up my kids, as I was stranded. As for the brakes, they shoot us forward every now and again when pressed. It is very scary. Dear Ocean Owners: Enrollment for repair as well as reimbursement for published the federal safety agency ( [XXX] ) recalls on the model year 2023 Fisker Ocean is now open until August 31st 2025. If your vehicle is in need of recall related work performed please email [XXX] and include your vehicle identification number, full name address and phone number. You will be contacted and scheduled for required repairs. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Apr 6, 2025 · Brakes, Electrical · CA

There are many incidents to report. 1. No Braking consistency and sometimes a jerk forward on braking, many incidents about 10. Also loss of regen braking at times. 2. Software safety features do not work and constant warning it does not work. Mostly lane assist, automatic parking collision warning. One time reversing camera shows room with digital assist lines which did not protect or warn car of swiping another car. Only slight damage to my vehicle. 3. Driver door handle water leakage causing door to not open with NFC chip and is constantly very warm on the handle as if there is electrical current always on. 4. I had to buy a new KEY FOB as old one has failed. 5. Rear passenger door reading light will come on for no reason. Some adjustment needed. 6. Broken air vents. Poor quality plastic apparently. I did tell manufacturer when i received car and they offered to fix but unfortunately at time I had no time to come in for repair before they went bankrupt and closed shop. Regardless they used poor plastic and a fix needs a better quality plastic i found out in research with other owners. 7. Inherent Production quality of parts problem many owners are discovering with help of owner organization to find remedy.

Filed Mar 26, 2025 · Driver assistance · FL

More bugs and problems after partial OTA to version 2.2.2 than before. Constant alarms and warnings that ADAS is not functioning. Driver alert monitor stopped the car in the middle of the road because it said I was not paying attention. The biggest problem is the car no longer detects the key FOB inside the car. New battery and I can unlock the car from 100+ft away. But once in the car I'm forced to hold it to the NFC. One time I started the car, jumped out to grab something from inside the house, left my key there, then drove off. With no key in the car I was able to dive about 3 miles to the store. Somehow I was able to put it back into D and get home without it shutting down and asking to hold the FOB to the NFC again. The other safety related issue is the small driver screen will not dim. No matter where I have the brightness setting manually set or on auto the screen is always at 100% At night it is very bright and is not at all pleasant to drive with. I have started putting a piece of thin masking tape over it to dim at night. I can still see mostly see things that pop up.

Filed Mar 10, 2025 · OH

The Over-The-Air (OTA) team pushed updates out to my car without warning...without any kind of notification. I was extremely upset as many cars from other owners got bricked. Luckily mine didn't get bricked but the full 2.2 updates did NOT get pushed. They picked and chose which modules they felt needed updated. So my car says it is at 2.2.2. I drove from Cleveland to Columbus to get my extra Key Fob and NFC cards programmed and was told (and I verified) that my PKC version was only version 09. This is so old that they were unable to even attempt to pair by fob/cards as it could brick the car. This is so disappointing and directly related to the OTA team not pushing the full 2.2 update which is supposed to address the recalls. This makes me very uncomfortable and upset not knowing if all the software recalls were completely addressed. The fact is...2.2 is supposed to address the federal safety agency software recalls so that is what we should get. This is the certified version. Pushing partial updates out should not be acceptable.

Filed Mar 6, 2025 · CA

I recently encountered a series of issues with my Fisker Ocean One (FOO) following a partial software upgrade at A1 Autobody in Fremont, CA. The service center performed an incomplete software update, leaving several modules pending for over-the-air (OTA) updates to reach version 2.2.​ [XXX] Software Version Discrepancies Initially, my vehicle's dashboard displayed the previous 2.1 version, indicating the absence of the critical T-REX upgrade. Unexpectedly, the dashboard later showed version 2.2 (1/3) without any notification from Fisker regarding this partial update. This lack of communication left me uncertain about the status and completeness of the software installation.​ Fisker App Connectivity Issues Concurrently, the Fisker App ceased functioning correctly, consistently showing my car as "offline." This issue prevents me from remotely unlocking my vehicle, a significant concern given the frequent unreliability of the key fob. This problem has been reported by other Fisker owners as well. ​ reddit.com [XXX] [XXX] [XXX] Safety and Reliability Concerns The inability to access my vehicle remotely poses safety risks, especially if the key fob fails. Additionally, the incomplete software update may affect other vehicle functionalities, potentially compromising overall safety and performance.​ Steps Taken and Recommendations I have attempted to resolve the app connectivity issue by reinstalling the Fisker App and re-pairing my device, but these efforts have been unsuccessful. I am seeking assistance to restore the app's functionality and complete the software upgrade to version 2.2 to ensure all systems operate as intended.​ I urge Fisker to improve communication regarding software updates and provide timely support to address these issues, ensuring a safe and reliable experience for all owners. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

Filed Mar 3, 2025 · Brakes, Electrical · TX

I have not received the 2.2 software update. The software delivered to my vehicle is 2.2.2, which has been communicated as an incomplete remedy of 2.2 that has not been homologated. Also, none of the hardware recalls have been addressed on my vehicle. My only local service provider does not accept any recall related work due to customers not receiving reimbursement. I do not have any available options to have my vehicle fully serviced. In addition to open recalls, I have a magnitude of issues with my vehicle, including but not limited to broken door handles, broken NFC reader, broken key fob, broken rubber trim, intermittent ADAS, intermittent reverse camera operation, and missing software features.

Filed Feb 26, 2025 · Driver assistance · WI

There were three times that after I had the car in park and tried to get out that I was unable to open the driver door to exit. The driver door out side handle did not automatically pop out to allow me to exit. I tried locking and unlocking the door internally and also tried with the car on and in park. On one occasion the window was stuck closed, probably because of icing. I ended up crawling over to the passenger side to get out. On the other occasions the door handle was popped out but I had to open the window and open the door using the outside handle. Frequently, the driver door handle won't go back in until after I have been driving for a few minutes. This seems to be the only handle with the issue of "sticking" either popped in or popped out. Occasionally when I lock it using the key fob, all the handles go in except the driver side. When I give it a little push from the outside it will go back in. At 2600 miles the NFC reader in the door handle stopped working. It is my understanding that the door handle recall was already performed on this vehicle. It is my belief that the vehicle is not better off after the recall. And that the $100 being offered to perform a door handle recall is far below the real world cost of such a service. Not to mention most techs can't get in and out of the door without leaving some damage to the panels or clips. I believe the recall on this vehicle for the door handles should not be considered completed. Or it should be reopened. There is also no emergency release strap anywhere in the vehicle for a door or window. Similar to the trunk manual pull from the inside. Please help us get this fixed. The ADAS warnings and chimes blinking lights etc are distracting as they are mainly warning for things we don't have working. Also the drivers screen flashes red to blue when changing fram accel to decel. Very distracting at night. Thank you.

Filed Feb 23, 2025 · Brakes, Electrical · AZ

Prior to a recall-mandated update of the vehicle's operating system, I received numerous (daily) ADAS warning lights and sounds. Regen braking often (2-3 times per week) jerked the car abruptly. Additionally, the ADAS lane-keeping process was jerky. The vehicle was evaluated by an over-the-air (OTA) team and determined to be ready for an OTA update, which occurred from 11/11/ to 11/12/2024. This update was managed by an OTA team that was mandated and funded by these the federal safety agency recalls: 24V865000 (Regen Braking OTA-2.2), 24V405000 (Warning Lights OTA-2.1), and 24V404000 (MCU/VCU Loss of Power OTA-2.1). The OTA update only partially loaded, with the vehicle was at OS 2.2 (2/3) and inoperable for 2 months, from 11/12/2024 through 01/12/2025. I made numerous attempts for support during this time, with communication via the Fisker Owners Association but no information from the OTA team. After I replaced the 12V battery, two recharges, and a remote tech support, the vehicle's electrical system was again available to receive an additional OTA update yet not operable. With limited notice, the vehicle received some of the missing components of OS 2.2 on 01/23/2025, at which point the vehicle was operational again. Though at this time the key fob only connects as an NFC device, with the potential risk of the key losing security connections while driving (and thus turning off, mid-drive). This has not occurred but a technician has noted this risk and I now "velcro" the key to the NFC port while driving. I have yet to receive two additional recall repairs: 24V499000 (Water pump), 24V466000 (Door Handles). I have an appointment with a former Fisker technician who has stated that I will need to pay him directly for the service time for replacing the water pump, and then seek reimbursement from the managers of the mandatory recall.

Filed Feb 21, 2025 · Driver assistance · CA

Key fob is not working and Range reduction from 360 to 200