Before I explain my observations from my last drive, I have to mention first that I do have an actual SAVVY unit installed (with thumbwheel set at 35MPH). My parts are arriving soon for my other car which will not be equipped with SAVVY unit so I can make a more accurate observation between SAVVY & NO SAVVY. If someone has already made these discoveries on this forum in which I have missed, please let me know. Also, let me know if I have said anything incorrect, and let me know if you have any comments. Here is my current setup which is up to date as of February 2018: - Valentine One [3.8952] - SAVVY (version: S1.0108) - V1 Connection LE (version: L1.0010) - Concealed Display (version: C2.1300) - V1 Connection app (version: 1.51) - V1 Driver (version: 2.0.42) It is safe to say that if there is any app with the V1 unit combination that runs as perfect and smoothly as possible, it would be the V1 Connetion app from Valentine Research and the V1 unit itself. The app is created by VR and the detector is created by VR them self so it has to have the most compatibility with each other; makes perfect sense. This means that the V1C app has the ability to do a serious "push" for configuration straight to the V1's computer system making it "official". Every single time you make a change in your profile, it will automatically push it to the V1. Every single time you fully close (not leaving it in background, really closing the app) and open it back up, it will automatically scan the V1's current configuration to see if it matches any of the profiles on your V1C app. This means that every single time you open up the app for a drive/configuring, it will ALWAYS find an identical match successfully and there is no problem. Now, from my assumption, I though the V1 Driver app is an app that runs alongside with the V1 constantly reading and sending data back and forth telling it to mute or whatever. This basically means that I thought the V1 Driver does not make ANY serious PUSHES to the V1 like the V1C app. However, I don't know exactly how V1 Driver sends data back and forth to the V1 but it is actually tampering with the V1's computer for configuration. Whenever you set the V1 with the V1C app, then it will always startup and find it's identical profile successfully. However, once V1 Driver is even opened at all on main screen or background for an instant (regardless of opening it after background or from being fully closed), the V1C app will no longer find an identical profile match and asks you to select one to push. This will happen every single time EVEN if you close the V1 Driver. A clear evidence of V1 Driver actually altering the configuration can be seen ESPECIALLY for SAVVY settings. Since the SAVVY unit uses the car's OBD2 port for speed detection and the V1 Driver uses GPS to emulate a SAVVY, it doesn't make any sense for the V1 Driver to tap into the SAVVY unit. However, it seems like it really does tamper with either SAVVY or V1 itself. Let's say you never had V1 Driver and only used the V1C app, you can use the thumbwheel speed or override it (let's have both the thumbwheel and override at 35 MPH for this example) with the app's feature by selection your own speed. Open and close the apps as many times as you want to drive, and you will always see the app boot up and display your saved SAVVY settings properly as expected. As soon as V1 Driver opens up for an instant, close it, and then go back to V1C app (open and close both V1C app and V1 Driver in any combination you want, it doesn't matter, I've tried it all). You will see that the V1C will not find an identical profile and if you go to the SAVVY settings on V1C app, the "Current Savvy Setting" will state "0 MPH (overridden)". The only thing you can blame is the V1 Driver, it can't be anything else. We all know the common use of V1C app is to push the main configuration to the V1, close the app, and don't use it for anything else anymore and have V1 Driver or any other app with a lot features take care of the V1 during the drives (we would only go back to V1C app if you wanted to change one of the main configuration). When all toggles for Savvy settings in V1 Driver is turned OFF, it will state "SavvyOffHard Error" in the steering wheel tab of the app. The reason why I observed all of this in the first place is because there's something happening that I couldn't explain during the drive no matter how hard I tried figuring it out at the moment. What happens is that when both my SAVVY thumbwheel (doesn't really matter if it's overridden by the V1C app) and V1 Driver SAVVY is set to 35 MPH, my V1 will alert me full volume for K band signals even at 1-3 strength. I highly believe that the V1's K self-mute logic will BYPASS any SAVVY setting if you have the "No Muting above 3 lights on first-encounter" and/or "Un-Mutes above 5 lights". This is an initial signal of 1 or 2 light too! Now, it really makes sense because even though the displays for V1C app and V1 Driver both say the SAVVY is set at 35 MPH, the V1 literally sees it set at 0 MPH (this is shown in V1C app next to "Current SAVVY Setting"). Even if I did set the SAVVY to 0 MPH, why isn't my V1 and V1 Driver taking care of the muting after at all? It beeps for many seconds without muting. Perhaps the tampered and overridden SAVVY setting bypasses ALL muting features regardless of app or V1 itself. If there was truly a toggle in V1 Driver that literally disables every trace of SAVVY feature (mainly for those who are running SAVVY unit but want the GPS lockout from V1 Driver), then we could get a better understanding if this conflict is true. I will be observing my entire setup on my other car next week; it's exactly the same setup EXCEPT it will not have SAVVY installed but a direct hard-wire straight to the fuse box like the classic method.