AT193
Well-known member
- First Name
- Aaron
- Joined
- Jul 1, 2022
- Threads
- 3
- Messages
- 52
- Reaction score
- 93
- Location
- New Jersey
- Vehicles
- 2022 F-150 Lightning - Lariat SR - Antimatter Blue
- Thread starter
- #1
I know the LVB and associated issues have been brought up a lot on the forum. I just wanted to throw in some weirdness that I'm experiencing as well. Starting about three days ago I noticed that the FordPass app would often not be able to remote start, lock, unlock, or at all control the truck. It was also missing a lot of driving records and wouldn't update the location, unless I manually got into the truck and turned it on. Then I was away from the truck for 24 hours and it went into "Deep Sleep Mode" and threw a big red warning in the app. When I got back I noticed it not lightning up on approach, and the easy unlock by sliding hand behind the handle was not working. FOB still worked to unlock. When I got in the truck nothing happened on the screens like it usually does and I had to start the truck in order for it to even know I was there.
Based on my reading online this all seemed related to the LVB, so I called the dealer and brought it in. They tested the 12v battery thoroughly and said that it came back fine. I am the first F150L that they are servicing in any way, so they are doing some more research on their own and getting back to me.
Does anyone else have insight into this? If the LVB is coming back okay, maybe the truck just thinks it's low for some reason? None of this was happening before the last 3.3.1 update, so maybe it's related to that?
Based on my reading online this all seemed related to the LVB, so I called the dealer and brought it in. They tested the 12v battery thoroughly and said that it came back fine. I am the first F150L that they are servicing in any way, so they are doing some more research on their own and getting back to me.
Does anyone else have insight into this? If the LVB is coming back okay, maybe the truck just thinks it's low for some reason? None of this was happening before the last 3.3.1 update, so maybe it's related to that?
Sponsored