search

ungoogled-software / ungoogled-chromium-android

Android build for ungoogled-chromium
GNU General Public License v3.0
495 stars 42 forks source link

How to remove red lines at the edge of screen when i entered Settings? #24

Closed Me0wzz closed 4 years ago

Me0wzz commented 4 years ago

How can i disable this red lines? I thought that i can disable it at Accessibility but, I cannot find the setting that disables red lines.

Anyway, Thanks for a good project :D

Screenshot_20200728-153203_Ungoogled Chromium Extensions.jpg

Me0wzz commented 4 years ago

Device: Samsung Galaxy Note 8 Android Version: 9 Pie ARM64 Chromium Version: Monochrome 84.0.4147.89

wchen342 commented 4 years ago

Duplicate of #53@Gitea. To put it simple, it's the strict mode check enabled by Chormium internally. It is just a warning and has no harm. Can you check whether the same happens to unmodified Chromium of the same version? If it also happens then please file an issue upsteam.

Me0wzz commented 4 years ago

Yes, Strict mode was disabled. Also, Original Chromium is same as this too. I think Chromium internally automarically enables Strict mode in app

wchen342 commented 4 years ago

Yes, they have a lot of places that uses strict mode check in their codes. It is not really feasible for me to remove all of them, so the only ways are basically either asking Chromium dev to disable this or just ignore them since they are harmless.

wchen342 commented 4 years ago

Isn't the canary version way past v84? I think it is supposed to be a nightly version. Also I didn't build a debug version, is_debug is set to false so that shouldn't be the problem.

wchen342 commented 4 years ago

If the problem occurs on v84 and disappears on v86 then probably they fixed it during v85~v86? Maybe should wait a little longer to see whether in next version the problem will solve itself.

wchen342 commented 4 years ago

See update at https://git.droidware.info/wchen342/ungoogled-chromium-android/issues/53#issuecomment-447. I'd like to hear opinions.

wchen342 commented 4 years ago

Should be fixed by 1812d02.