ttab: Set TARGET_NEEDS_NETD_DIRECT_CONNECT_RULE to true
authorKevin F. Haggerty <haggertk@lineageos.org>
Wed, 10 Oct 2018 13:06:28 +0000 (07:06 -0600)
committerJan Altensen <info@stricted.net>
Mon, 25 Feb 2019 11:55:21 +0000 (12:55 +0100)
* Due to "specialness" in our RIL library, ConnectivityService
  doesn't seem to appropriately add the relevant directly-
  connected routes, meaning that IPv4 mobile data is inoperable
  due to lack of a default route. Let's reenable the legacy netd
  behavior to get our connectivity back.

Change-Id: I59f8476ab36db0fb79856f74346e62e0dd4abae0

BoardConfig.mk

index 711717eb2faf095a17c5e57806e3b98e7b9211b5..ac0b465231cd00552be87ee66d7da4b8a48ab266 100644 (file)
@@ -90,6 +90,9 @@ BOARD_HAVE_BLUETOOTH_MTK := true
 BOARD_BLUETOOTH_DOES_NOT_USE_RFKILL := true
 BOARD_BLUETOOTH_BDROID_BUILDCFG_INCLUDE_DIR := $(DEVICE_DIR)/bluetooth
 
+# Network Routing
+TARGET_NEEDS_NETD_DIRECT_CONNECT_RULE := true
+
 # RECOVERY
 TARGET_RECOVERY_FSTAB := $(DEVICE_DIR)/recovery.fstab