Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cellular: Disable cellular.clear-on-connect by default #11469

Merged
merged 1 commit into from
Sep 19, 2019

Conversation

AriParkkila
Copy link

Description

Disable cellular.clear-on-connect configuration by default. It was a bit too bold assumption that it ca be always enabled, as it seems that clearing of PDP contexts may cause different kind of connectivity problems depending on a network environment confguration, such as auto-reconnect to network, create initial network context, SIM pin query disabled/enabled.

This change disables just automatic clearing, while CellularDevice::clear() API is still available for applications as previously.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

Release Notes

The release notes of PR #11414 are not anymore valid, as there is no change in functionality.

@ciarmcom
Copy link
Member

@AriParkkila, thank you for your changes.
@ARMmbed/mbed-os-wan @ARMmbed/mbed-os-maintainers please review.

@ciarmcom ciarmcom requested review from a team September 12, 2019 09:00
@0xc0170
Copy link
Contributor

0xc0170 commented Sep 12, 2019

If we are changing the config, this even might be a fix but breaking, isn't it ? Thus the next minor version.

Wait, I've noticed release notes just now. all good, 5.15

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 18, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Sep 18, 2019

Test run: SUCCESS

Summary: 11 of 11 test jobs passed
Build number : 1
Build artifacts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants