@Moem thought there is a way… heard of recovery mode but somehow couldn't get to it. and installed via odin/fastboot, not installer…

generally there is one main browser on UT (morph) and few clones of it over on openstore but all of them are still basically morph and everything you can't do with morph you can't do there too (for example lacking webCrypto apis, gyroscope apis, FS api, extensions and so on… and additionally sites very oftenly block these browsers as outdated).

i know it's possible to install manually firefox/firefox-esr via apt and even tried that but surely it doesn't work properly (keyboard - maliit - doesn't even open there like in any other gtk, apt-installed apps, copy/paste with bluetooth keyboard neither so navigation only by manually typing addresses, additionally bad/non-mobile sizing of buttons, enough high ram usage to crash phone after longer time of being open, etc…)
chrome/ium isn't even in apt repos.

will it be ever possible to run a "normal" browser on mobile ubuntu somewhen or is it just my weird dream and i'll be stuck in "modded safari" forever?

generally i have muted audio over whole system (including slider set to 0 and silent mode).
recently i'm testing browsers and some desktop-like ones (so far firefox click package) are able to turn on sound when they want (eg. a website wants to play audio) regardless of OS settings and themselves put up system audio to 100% .
is it possible to block such behavior on like lower level than just sliding toggle in settings which doesn't work in this case?

@naz.R ok

@libremax tried to test/install manually. best i got was this:

generally there is one main browser on UT (morph) and few clones of it over on openstore but all of them are still basically morph and everything you can't do with morph you can't do there too (for example lacking webCrypto apis, gyroscope apis, FS api, extensions and so on… and additionally sites very oftenly block these browsers as outdated).

i know it's possible to install manually firefox/firefox-esr via apt and even tried that but surely it doesn't work properly (keyboard - maliit - doesn't even open there like in any other gtk, apt-installed apps, copy/paste with bluetooth keyboard neither so navigation only by manually typing addresses, additionally bad/non-mobile sizing of buttons, enough high ram usage to crash phone after longer time of being open, etc…)
chrome/ium isn't even in apt repos.

will it be ever possible to run a "normal" browser on mobile ubuntu somewhen or is it just my weird dream and i'll be stuck in "modded safari" forever?

@MrT10001 thanks. forgot about twrp possibility

@MrT10001 i don't have twrp. only odin. if ubuntu itself haven't installed any recovery then idk if such thing exists

@Moem thought there is a way… heard of recovery mode but somehow couldn't get to it. and installed via odin/fastboot, not installer…

i am a web and game dev, sometimes i really lack some features in default browser (like gyro access, webcrypto apis, etc…).
so yesterday been testing out browsers to install (epiphany/gnome browser, konqueror, falkon, qutebrowser, links2, firefox, etc…) almost installed/tested min browser but phone broke before. ofc chrome/chromium isn't available in repos so couldn't. in between when deinstalling one of browsers (already forgot which one) it alo deinstalled (or otherwise disabled) system virtual keyboard input. and some time later got a huge lag requiring reboot.
my phone from start haven't had proper usb drivers (best i got is percentage of battery) and no data connection this way.
so like right now my phone is unusable cause of login screen requiring keyboard which doesn't exist now. can't connect bluetooth keyboard (the one i have) over on login screen, usb as i said broken, ssh doesn't work on login screen (security). right now from OS best i can do is emergency call… and flashlight from statusbar i keeped on login screen.
phone is samsung m33 (custom build) with ubuntu 20.04 .
any ideas to unbrick except of reflashing OS back via odin and losing all data?
haven't made any backups before testing