Launcher PRO 5.0.2

Launcher PRO V5.0.2 is now available

Change Log:

- Fixed bugs with localized Windows (RU, DE, NL...etc.)

If you have turned on Check Update option, Launcher PRO will alert you of critical updates, such as this 

Note: Avoid posting support-related questions in the comments section. I don't actively watch comments and don't want to miss anything important. Please send me an email

Important: Apparently, Launcher PRO doesn't handle the link properly. This will be fixed in the next build. Please grab the link from my website for now

Launcher PRO 5.0.1

 Launcher PRO 5.0.1 Build 36 is now available

Launcher PRO V5.0.1 is rewritten from the ground up for Windows 10, 11 64bit only on bare metal machine, meaning, no virtual machines. Supported Versions are 3.35.0, 3.36.0, 3.36.1, 3.36.2, 3.38.2 64bit only, with more to come.

Version 5.0 supports both CAFD versions 1.0 and 2.0. Slowly, but eventually, BMW is moving to online signing all coding data, starting with Coding 2.0 (SP2021), and now Coding 3.0. Signature methods for these CAFD uses RSA 2048 to RSA 4096 and Elliptic curves (ECCP 256 – ECCP 521. These will be very limiting in the future. As of the latest PSdZ data, Launcher PRO V5 supports online signing of known CAFD using authenticated keys and proper coding proof stamp. I'm probably letting off more than I should, but we'll get there eventually.

Launcher PRO V5.0 sports streamlined modern Metro UI. There are 5 selectable themes to choose from. Add as many supported apps as possible and double-click when ready to run.

Launcher PRO V5.0 makes Google Authenticator optional, but is very convenient, so might as well use it. All Time-based One-time Password generator Authenticator, i.e., Microsoft Authenticator, are supported, not just Google Authenticator. More importantly, no more PC activation. Launcher PRO V5.0 is no longer tied to a particular PC. Use anywhere, anytime. It's just like the old dynamic activation, but unlimited.

 

Launcher PRO V5.0 departs from its predecessor in handling KIS database. It's now an Opt-in model where you have to choose which KIS is loaded, as opposed to Opt-out model used in the old version. At least one KIS must be selected

Settings can be temporary or can be applied every time. Either way, you have total control

FAQ:

Q: Can I install on 3 PCs?

A: Yes. There's actually no limit on the number of PCs, so if you have 5 PCs, go ahead and install it on all 5 PCs. The only limitation is that only 2 PCs are active at any given time, so if you move to the 3rd or so PC, you just need to authenticate again.

Q: How long is the license?

A: 3 years is the standard length of the license with no PC limitation

Q: My account says I activated 2 PCs and cannot activate anymore

A: Ignore the website. It was built for V3.0 and I can't update it until V3.0 dies. It will only show the first 2 codes, but really, it is meaningless for V5.0. There is no static or dynamic activation in V5.0

Q: Can I activate more than 1 PC?

A: Err, I just said, there is no static, nor dynamic activation in V5.0 :)

Q: I have a V3.0 license, can I use V5.0?

A: Updates are free, and V5.0 is and upgrade to to V3.0, so yes, you can.

Q: What happens to my V3.0 license?

A: Nothing. It will be as is. If you get a new license now, you will have an extended license. So if you have a year left on the old one, you will end up with 4 years, total.

If you still have active key/s, head out to https://www.fxxtokenmaster.com and grab Launcher PRO V5.0

CAF/NCD 2.0

Starting with V3.34.0, Online signing has been implemented. I did change this to offline/On-premise signing, but I think it's no use to keep reverting to offline signing. I've been working on V3.35(V3.35.1) and V3.36 (V3.36.1, V3.36.2) and have these versions working, but I really do want to support Coding 2.0. This is the future and where we're all going. This means new format of everything and will make everything as we know it today, obsolete. This includes the current mapping technology, and even the NCDF/CAFD Tool.

I've been contemplating releasing an update and retrofit support for Coding 2.0, but my desire to support it and do it right the first time prevailed.

I've checked the latest PSdZdata and we do have a few CAFD 2.0, but seems to be faulty. I can generate NCD 2.0, but I wanted a factory one. So, I'm looking for NCD and CAFD 2.0. These are found in newer G20, G08, i4...etc. If anyone has them, I'd appreciate a couple of samples, better yet, the entire set, including FA.

This is really a big change, so bear with me as we tread this uncharted waters together. I'd be devoting time to this in the following weeks or months even.

Launcher PRO 3.7.0 and Website Update

Launcher PRO 3.7.0 Build 315 is now available.

Change Log

====================

3.7.0 Build 315

- Huge improvement in CAFD processing (BDC, NBT and MGU in the low 2s)

- Better, more accurate CAF mapping and translation

- Significant reduction in memory usage

- Improved 32-bit app performance and stability

- Better handling of low memory condition in 32-bit app

- Fixed: Bug in JNI component that was introduced in V3.2+

- Minor bug fixes

*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store

Note: Please see https://www.fxxtokenmaster.com and blog before upgrading to 3.1+. Launcher PRO now uses Time-based One-time Password for authentication. 

Google Authenticator is required when using dynamic activation and when updating the Launcher.

This is a must-have update. It's more stable all around. 32-bit app has been causing low-memory condition, resulting anywhere from failed mapping to app crash. I put extensive work on this build to significantly reduce memory usage, improve stability and enhanced the performance of the mapping module. The following image shows the timing when opening HU NBT and BDC_BODY CAF.

Like the new graphic, I'd like to call this the Concept 4 Edition. Like the Concept 4, the Launcher is just leaner, meaner and faster all around.

To fully appreciate the improvements, use the 64-bit versions. It's just way so much better. When using 32-bit versions, expect the Launcher to fallback to slower method most of the time due to memory constraint. It's no slouch at all, but it's nowhere near the performance it can achieve when using 64-bit versions.

Website Update

My web host has been doing changes to their infrastructure, causing unintended side-effect on my app. I noticed a couple of days ago that validation has been failing, and upon further investigation, found that my web host did drastic settings changes which caused a critical function of my web app to fail. I scrambled to find a solution and worked around this changes, since they won't acquiesce to reverting the changes. Anyway, I'm glad to announce that I rewrote the affected portion of my website, so login/validation is working again. 

If you have been experiencing problems recently when trying to login/activate, please try again and let me know if the issue persist.

**Don't use the comment section to ask where to get it and stop posting your email addresses

FXXTokenMaster.com is UP

My Web host is DOWN for 3 days now. 

All customers are not privy to what is happening and we're being kept in the dark. Sorry for the inconvenience and I appreciate your patience. I'm hoping to get my site back up and running, sooner than later.

My site is now up, at least for the moment. My host drop the ball big time and all files were replaced with a very old version. I just can't wait any longer and blasted the entire site with files that I know are working.
I'll have to check what else has changed and act accordingly, so, it may go down from time to time.
I apologize for any inconvenience.

Launcher PRO 3.6.0

Launcher PRO 3.6.0 Build 288 is now available.

Change Log
====================

3.6.0 Build 288
- Added: Support for 3.34 64bit Only
- Improved PSdZ Handling and Translation
- Minor bug fixes

*Requires Google Authenticator mobile app. Download from Apple App Store or Google Play Store

Note: Please see https://www.fxxtokenmaster.com and blog before upgrading to 3.1+. Launcher PRO now uses Time-based One-time Password for authentication. 

Google Authenticator is required when using dynamic activation and when updating the Launcher.

V3.34 is really interesting, but appears to be an indication of how things are, going forward. The easier way to deal with it would have been to provide an alternate REST API for signing and encrypting NCD, but I don't believe in encrypting user's data.  It's my NCD, I'd like to not be locked out of it, so I chose the harder way. NCD files remain not encrypted. Properly signed, but not encrypted.

It appears to be well-coded and stable. I like this version a lot.


**Don't use the comment section to ask where to get it and stop posting your email addresses

X3!!!

I've been playing with a friend's G01 XDrive these couple of days, (well, it's been more than a week, but who's counting?). No serious coding yet, just taking a look-see at what can be done with it.

G01 is really nice. It's small enough to replace a sedan, but not big enough to compete with a family SUV. I like it, so much so, that it gave me enough motivation to go and shop around, and shop around I did. I've looked and test drove a couple of G20s. I like the G20, so much technology squeezed into that little car. However, I'm still more impressed with the G01, even with its older technology. I know it will have the Live Cockpit Pro and ID7 in the coming builds, so G01 will have all the same bells and whistles that the G20 has.

Did I say I like the G01? YES, I like it. I like it so much that a new G01 will be coming home with me soon :(  Just deciding between BSM, Alpine White, Mineral White. Leaning towards BSM, like my F30. I wish I can turn off XDrive. I mean, in my suburban settings, I hardly have the need for it but I want it, in case I need it.

I can hear a voice screaming inside my head: "Ahhhh, noooooo, wait for a couple of months and you'll have all the good stuff the G20 has!!!!!". F*ck my EQ,  I wanna drive it NOW!!! Giving up the i3 for it. I think I'm OK with that trade. That thing depreciates like crazy, though.

I detailed my F30 last weekend, to help me contain my excitement. She still runs like a champ, and she aged gracefully. After getting in a G20 though, it does feel really old.


And you know what else it motivated me to do? Dusted off NCD/CAFD Tool. The tool is so outdated that I see a lot of inaccuracies, and the "What-If"s functions are really crawling. Of course, the format of NCD and CAF files have changed a little bit too, and so are the rules for functions.

I just want to quickly bring it back to life, so I plugged in the components from Launcher PRO. It has so much dependencies on it, but it gave me the benefit of quickly analyzing the G-series stuff. So far, so good. I can see some minor issue with mapping though, but that's just given, the way we do things.

I can't wait to fully analyze the CAFs on this G01. Hopefully, I can enable and test some stuff soon, in preparation for my own car.

My friend has been asking what we can possibly change with his car, but hasn't asked for it back. I might keep it for another week or so. NO! I WILL keep it for another week or so  😂


UPDATE: 09/07/2019
There seem to be a lot of potential, but I just don't have enough time to test them. So far, here's what I did to this X3:

• Speed Limit Info (SLI) - Note: FSC is required. I opted for the Euro Style SLI, the while circle with red outline. This is what I have on my i3, but the new US default is just silly, with the word "Speed Limit" on top of the value in a white rounded rectangle. That's just plain silly. It's nice how the HUD turns red, and the dial have a red trailing line when you go over the limit.
• Auto Start/Stop Memory - I wonder why this isn't the default yet
• Tailgate/Lid Angle/Height Settings
• Tire Temperature - Default only shows pressure
• Auto Park Assist On
• Cross Traffic Alert - haven't tested yet.

By the way, I'm getting a BSM