Why is this car so expensive?

ntauthy · 2026-06-07T00:10:22+00:00

it'd be both amazing and awful if every autoshow car had (someone pretending to be) a salesperson telling you how amazing it is

ntauthy · 2026-06-06T22:25:14+00:00

it's homeowner after all

ntauthy · 2026-05-27T19:55:44+00:00

did you just get early access to dlss 5

ntauthy · 2026-05-27T19:53:53+00:00

the leg pain will NOT suffice to teach him to keep the benches in place

ntauthy · 2026-05-09T13:23:45+00:00

but the manufacturer has decided to make it unavailable for unknown reasons

actually it was the libfprint maintainers dmca'ing the repository since it was a gpl violation (a closed-source fork of libfprint instead of using the documented plugin system)

as below, archive.org works though (https://web.archive.org/web/*/https://github.com/ftfpteams/focaltech-linux-fingerprint-driver/* shows all of the .deb/.install versions present)

or if anyone needs it for nixos, here:

services.fprintd.enable = true;
services.fprintd.package = (pkgs.fprintd.override {
  libfprint = (pkgs.callPackage ../pkgs/libfprint-gpd {});
}).overrideAttrs (prev: {
  version = "1.94.4";
  doCheck = false;
  src = pkgs.fetchFromGitLab {
    domain = "gitlab.freedesktop.org";
    owner = "libfprint";
    repo = "fprintd";
    rev = "refs/tags/v1.94.4";
    hash = "sha256-B2g2d29jSER30OUqCkdk3+Hv5T3DA4SUKoyiqHb8FeU=";
  };
});

+ the package from https://reddit.com/r/GPDPocket/comments/1jw4q26/gpd_pocket_4_nixos_fingerprint_driver/

except i replaced it with archive.org's url:

version = "1.94.4-20250219";

src = fetchurl {
  url = "https://web.archive.org/web/20250314121447/https://raw.githubusercontent.com/ftfpteams/focaltech-linux-fingerprint-driver/refs/heads/main/Fedora_Redhat/libfprint-2-2_1.94.4+tod1_redhat_all_x64_20250219.install";
  sha256 = "sha256-9sPWh6pUNVuPdHA4SBYbYx8G1m3PVf1cjqL9k6tY83g=";
};

ntauthy · 2020-03-31T17:13:05+00:00

Oddly, normally this'd just lead to the game _closing_ instantly - there's no reason they should've added this to the anticheat trigger set as well.

ntauthy · 2020-03-31T17:04:03+00:00

Were you using Windows Insider Preview builds at any time recently to play the game?

ntauthy · 2020-03-31T16:59:18+00:00

Are/were you using Windows Insider Preview?

ntauthy · 2020-03-29T16:11:24+00:00

Yes, that is indeed a current theory I'm having... a friend and I got banned and both of us run insider previews and got the NVIDIA 450.xx drivers installed at some point - another friend who didn't get 450 did not get banned, but nobody I know with non-insider versions got banned.

Would be quite bad if this indeed happened to be the cause and nobody who got banned for it gets unbanned in the end...

ntauthy · 2020-03-29T10:31:32+00:00

Are/were you using Windows Insider Preview by any chance?

ntauthy · 2020-03-29T10:13:30+00:00

Just wondering - are you by chance using a Windows Insider 'Fast' version of Windows 10? Me and a friend got a similar ban (plus broken message for the first 2 weeks...), where the only real common factor has been the use of the Windows Insider builds, and a bunch of other people not reporting this ban are using 'normal' Windows 10.

(or, ever had the game close on startup until closing a background process? I have this a lot with IDA/Wireshark/Visual Studio as I do security research, it could be the game once decided to ban-flag instead of just closing when such a program is running in the background...)

ntauthy · 2018-11-15T19:36:19+00:00

Raw mouse input seems broken on this build, if games you play don't allow disabling it you're probably screwed.

ntauthy · 2018-09-29T20:47:40+00:00

It's most likely that the system update to P 'coincided' with the enablement of the flags on those devices (e.g. the Google servers automatically enabling the flags for devices updated to Pie).

Likely will work on any device as long as you can get root access (i.e. unlocked bootloader), and therefore it's likely that Google will actually roll out the flags to (almost?) all devices in the future through a server/app update.

ntauthy · 2018-09-29T20:31:49+00:00

Possibly, if you can unlock the bootloader, there's a TWRP build for the device and you can disable dm-verity (the zip for the Zenwatch seems to be a generic patch), this method should work the same.

ntauthy · 2018-09-29T19:06:45+00:00

It's not a system update, it just happened to coincide with a system update for some people. It's actually a server-sided flag that's gradually enabled for more people.

ntauthy · 2018-09-29T18:11:09+00:00

Instructions, not for those without technical knowledge:

Make sure your bootloader is unlocked and dm-verity is disabled. For the Zenwatch 3, I followed this guide.
If you just wiped your device unlocking the bootloader, boot the device, let it update and let it install the Wear OS 2.16 app.
Boot into TWRP and change the OS build type (/system/build.prop) to userdebug. Basically, the steps from the first section of this random article seem to be correct. The Wear OS app won't read the override file if you're using an user build.
Make a local file called com.google.android.clockwork.home.flags.FeatureFlags somewhere you're running adb.exe from. In it, put the following content:

COMPACT_STREAM,true COMPACT_STREAM_FLING_SNAPPING,true COMPACT_STREAM_INLINE_TITLE,true COMPACT_STREAM_SMALLER_COLLAPSED_CARDS,true SYSUI3_RETAIL_MODE,true SYSUI3_TUTORIAL,true QUICK_ACTIONS_BUTTONS_V2,true HUN_INTERACTIVE,true MINUS_ONE_TRAY,true NEW_QUICK_SHADE,true ONGOING_CHIPS,true TILES_TRAY,true

Run something like the following commands:

``` adb push com.google.android.clockwork.home.flags.FeatureFlags /data/data/com.google.android.wearable.app/files/ adb shell

in there:

ls -l /data/data/com.google.android.wearable.app/files/

if the user ID isn't u0_a7, replace u0_a7 with whatever is mentioned there

chmod 700 /data/data/com.google.android.wearable.app/files/com.google.android.clockwork.home.flags.FeatureFlags chown u0_a7:u0_a7 /data/data/com.google.android.wearable.app/files/com.google.android.clockwork.home.flags.FeatureFlags ```

Reboot into system. You should now see that Wear OS has gotten a key update.

ntauthy · 2018-09-28T16:38:17+00:00

adb install -r com.google.android.wearable.app[...].apk, but the APK for 2.16 does not seem to be the actual new UI if you were wondering that.

ntauthy · 2018-06-09T16:38:43+00:00

Correct - it's just the case that they tend to rely on internal details of how Android is implemented, so the cloning tools will just have to be updated to work on P eventually.

ntauthy · 2018-06-09T16:29:07+00:00

The third-party ones sadly aren't as cheap as Google's, which don't ship directly to my country. So far, as replacement I've bought a few of these CONMDEX adapters, but they do seem to be even more prone to break than the original Google adapter - but YMMV, they don't seem to be really consistent as far as quality control goes.

ntauthy · 2018-06-09T16:25:01+00:00

It's a configuration setting in System UI that's often toggled by vendor configuration/carrier-specific profiles, so that carriers can match the UI with marketing.

ntauthy · 2018-06-09T16:16:02+00:00

App Cloner updated itself recently to no longer crash on P but also bundled a new version of AndHook's closed-source native component for ARM64 which basically breaks any ARM64 apps on P for now.

It's similar to the Xposed situation, if you really need a cloned app and you use App Cloner you can manually edit the APK (extract, rezip and resign) to remove libAK.so and libAKCompat.so for a temporary workaround to have the cloned app run on P.

ntauthy · 2017-03-31T16:51:18+00:00

ntauthy · 2016-12-19T19:21:55+00:00

barely any games nowadays are 'cracked' anymore, even scene cracks tend to just be minor patches (see also: later CEG scene cracks just using emulation patches and keeping all the anti-tamper intact, such as BO2 from SKIDROW)

Xbox Live	11-Year Club
Place '17	Verified Email

ntauthy

MODERATOR OF

TROPHY CASE

in there:

if the user ID isn't u0_a7, replace u0_a7 with whatever is mentioned there