Apply TcpBufferSize of CarrierConfig from ConnectingState
When creating DataNetwork and triggering SetupDataCall,
NetworkRegistration information and DisplayInfo is already
prepared and updated at most time. So there's very few
chance to update TCP buffer Configuration from CarrierConfig.
Consequently, TCP buffer remains with default config and it's
not enough to support latest high speed radio tech like NR,
and also not proper to support legacy old rat which requires
smaller buffer to keep stable data flow.
DataConfigManager will fall back to read default TCP buffer size
configuration when it fails to read overridden configuration.
So no side effect is expected.
Bug: 261356610
Test: browse internet and made voice call + atest aosp/2405002
Change-Id: I31c19b94029b0d9c82ad87225c0d3d318a93c701
Merged-In: I31c19b94029b0d9c82ad87225c0d3d318a93c701
Signed-off-by: Jiwon Kim <jiwon.ss.kim@samsung.com>
1 file changed
