change 706-16-01Yes. I am talking about lane keeping camera. IPMA module is from this car, but it was tried in other f150, programmed and now returned back to this f150. Now I cannot do PMI or configuration via fdrs
| 0049 | 0000 | 006D |
Sponsored
change 706-16-01Yes. I am talking about lane keeping camera. IPMA module is from this car, but it was tried in other f150, programmed and now returned back to this f150. Now I cannot do PMI or configuration via fdrs
| 0049 | 0000 | 006D |
?Lots of reports that in dark mode the APIM is more stable with Bluetooth and cameras.
I know, it sounds crazy.
Send me your VINCan anyone help me with this error? I was able to do several other GWM updates during the day yesterday. TIA
![]()
1FTFW1ED5MFB06652Send me your VIN
That's exactly what I did. I bought a cheap used Windows laptop from a colleague of mine just for FDRS and FORscan.A little off topic - If I was to buy a small cheap windows (10 or 11) based pc/tablet to run just FDRS, Forscan ect. - Any ideas? Thinking of keeping all my truck info stored on it as well. Would need a couple of USB ports, WIFI and SSD drive.
I have our laptop installed in the office, with all cords tucked away. Also, it has not been used on battery power that much and the battery doesn't last long.
please update the post w/ phone model so we can see if similar issues popup with that phone. I believe the latest iphone is having issues with the phone as key.Looking for ideas on this issue or see if anyone else is experiencing this. I did an APIM update via FDRS on Oct 6 up to version 23167 Rev 926. Ever since then my Android Auto will connect and load. In about 5 seconds it will drop out and display the image below. 60% of the time it will re-connect in 10 seconds. The rest if the time it won't work unless I manually connect it from the phone screen. I have done an APIM reset, removed the phone from by vehicle, cleared out the app data and cache from Android Auto on my phone. Same result.
Feb 2021 build. 501 Lariat
i have the same phone and year of truck - I seemed to get intermittent period where my wireless Android Auto would not connect, and seemed to be worse if my family used the truck before me (using Apple CarPlay). Things got a bit better by doing the following:Looking for ideas on this issue or see if anyone else is experiencing this. I did an APIM update via FDRS on Oct 6 up to version 23167 Rev 926. Ever since then my Android Auto will connect and load. In about 5 seconds it will drop out and display the image below. 60% of the time it will re-connect in 10 seconds. The rest if the time it won't work unless I manually connect it from the phone screen. I have done an APIM reset, removed the phone from by vehicle, cleared out the app data and cache from Android Auto on my phone. Same result.
Phone is a Pixel 5, Android 13.
Feb 2021 build. 501 Lariat
Very cheap laptop will do the job.A little off topic - If I was to buy a small cheap windows (10 or 11) based pc/tablet to run just FDRS, Forscan ect. - Any ideas? Thinking of keeping all my truck info stored on it as well. Would need a couple of USB ports, WIFI and SSD drive.
I have our laptop installed in the office, with all cords tucked away. Also, it has not been used on battery power that much and the battery doesn't last long.
I was thinking 8 GB ram, 125/256 GB SSD and Windows 10 or 11. Has to have 2 or 3 USB ports and WiFi. Figured that would work just nicely.Very cheap laptop will do the job.
First thing I did when I bought it was reinstall Windows 11 from scratch off USB drive. It finds the baked in hardware license key and it's off and installing quick without OEM bloatware. Then add FDRS and Forscan.
Go off the relatively low FDRS requirements plus a little extra. It doesn't need an amazing spec laptop.
I went with 8GB of RAM and 128GB HD even though first post in thread says 4GB. It's a useful little laptop for forum browsing and basic things.