GmsCore
GmsCore copied to clipboard
microg
org.lineageos.jelly not using configured http proxy
Affected app Name: Browser Package id: org.lineageos.jelly
Describe the bug Browser not using configured http proxy
To Reproduce Steps to reproduce the behavior:
- Configure wifi network to use proxy
- browse to some website
- observe on http proxy no connection from microG device
Expected behavior Browser app should honor http proxy config
Screenshots If applicable, add screenshots to help explain your problem.
System Android Version: 12 Custom ROM: 19.1
microG
microG Core version: 0.2.24.214816
microG Self-Check results: unchecked: Permission to This app can appear on top of other apps
Additional context logcat & bugreport
The official LineageOS build behaves correctly as expected.
I suggest to report the bug to LineageOS devs: https://gitlab.com/LineageOS/issues/android/-/issues/
I suggest to report the bug to LineageOS devs: https://gitlab.com/LineageOS/issues/android/-/issues/
As I pointed out:
The official LineageOS build behaves correctly as expected.
Sorry, but you said that you went from an "official LineageOS build" to a "Custom ROM". It appears that you effectively changed ROM. Hence I suggested asking the LineageOS devs as they may be doing something differently in their ROM/app that your current ROM does not.
Reference: https://lineage.microg.org/images/bug_reporting.svg https://lineage.microg.org/ https://github.com/lineageos4microg
My guesses, the problem is come from Lineage official upstream code, try to reproduce the problem using official image build. Your issue is system related, and not related to this repo/GMS.
My guesses, the problem is come from Lineage official upstream code, try to reproduce the problem using official image build. Your issue is system related, and not related to this repo/GMS.
Have not been able to reproduce on 19-20220524-NIGHTLY-payton. The logcat and bugreport attached to this case were collected while running lineage-19.1-20220525-microG-payton.zip AND while the Browser app was not honoring the http proxy configuration. To be fair, it does work sometimes, but I was able to capture the logcat & bugreport when it was not.
The official LineageOS build behaves correctly as expected.