@domubpkm can you give me the log from the logviewer app?
also dmesg | grep DENIED and dmesg | grep uwolf

@AmauryDBZ as in still not showing chrome?

try running: gsettings get com.lomiri.Shell usage-mode
I'm thinking you're device has an edge case which makes the is_usage_mode_staged() make a false negative, this command is what's responsible for toggling the custom UI (after all you don't need it with a screen/keyboard connected).
essentially this is the code for deciding if its using stages or window mode:

if usage_mode == r"'Staged'" or usage_mode == None: # check if staged, fallback if nothing was outputed to most likely.
    return True
return False # if check fails then its not Staged

point is I'm suspecting the output is not 'Staged' in text (including the ' ')

@AmauryDBZ url about:support , there should be a big button named clear startup cache.

@domubpkm indeed, I am currently trying to up the security by trying to make app confinement work if nothing else it will make it clear to the user what exactly am I accessing because I will still need some special permissions but this will become much more secure.

you can test the experimental confinement here, this has the same functionality as v0.10.30

@domubpkm the goal was bring it to usable state before the switch to Noble
it is as close as possible more optimization while possible is unlikely to happen, at most I will fix bugs until I make a proper Beta version for Noble.

in Noble i can use ubports-qa to install the needed MR's to get wayland working so i can actually get the browser to be usable as I don't consider it usable right now on low-spec phones like my own phone.

@AmauryDBZ theres a new update, just in case try to upgrade to it if you haven't already.

if that doesn't work please try going here: about:support and clear startup cache.

@domubpkm try to reinstall v0.10.30 i patched it it should work now.

@domubpkm yeah idk how or why you use a virtual framebuffer that means no hardware acceleration in most cases,
try running the command

cat /sys/class/graphics/*/modes
fbset -s

if this gives you a list of resolutions tell me, I'll implement reading this as a fallback.

also not related but because you use a virtual framebuffer you could potentially hack together a way to have nightlight.

@domubpkm can you search around a bit and see if you can find these:

phablet@ubuntu-phablet:~$ ls /sys/class/drm
card0  card0-DSI-1  renderD128  sde-crtc-0  version

I need access to card0 so i can see resolution size of the screen.
its probably somewhere in a different directory, if you can find it I would appreciate it if not I'll figure out another solution.

ls /sys/*/*/*/modes

check this out, if its simply renamed then this should return something.

@domubpkm okay can you run this in shell:

cat /sys/class/drm/*/modes | awk -F 'x' '{print $2}' | sort -nu | tail -n 1

also just this in general so i can see if theres different syntax here

cat /sys/class/drm/*/modes 

@domubpkm please try version 0.10.30

@domubpkm what does this say:

cat /sys/class/drm/card0-DSI-1/modes

@domubpkm provide me the crash log, preferably on github.
i don't own you're device i can't tell you why it doesn't launch.

@AmauryDBZ can you log the full startup by running librewolf.sh and piping the output to a log file?
something like this:

cd /opt/click.ubuntu.com/uwolf.chromiumos-guy/current
./librewolf.sh >> ~/uwolf.log

if you run that it should put a log file on the home directory.
what you provided does not provide the context for why the userchrome does not load.
i will check out the syntax error in the javascript file though.
EDIT:
no idea whats wrong with the javascript, no syntax errors are found for me.
its an actual setting and i set it, no idea why it thinks it doesn't exists.

@AmauryDBZ Hi, developer of uWolf here, on a side note the UI is not modified (in the screenshot) for mobile so this has to be either v0.2.3 which doesn't make any sense or its not loading.
if you could provide me the startup log of the app I would be grateful.

for the spotify problem, disable the extensions first uBlock-Origin and Decentraleyes( which is a tracker blocker).
not to mention LibreWolf by default stops cookies which breaks some sites so you can try to change the security settings and add spotify to the exception rules.

@domubpkm the next step is to wait for Noble, i have somethings i can fix right now
bit i rather just do one big bug sweep session when switching to wayland.

as soon as the transition to noble happens i can automatically make the phone install the subsurface patch (until it goes to upstream) and then i can run wayland which means a host of bugs will be gone but i already know some stuff breaks (and my workarounds for the xwayland bugs) so i will probably need to do a refactor of the entire app so i might as well do everything in one big concentrated push.

edit:
other then that?, really only cleaning up the UI mostly.
i can't really do anything else, though i am toying with the idea of making another startup script to mimic webapp-container so webapps can use this (they'll need to be unconfined)
also finding a way to make uWolf the default browser, after the switch to wayland it should be a lot more usable so it stands to reason people will want to be able to make it open links.

@haagch im currently working on the nix-manager project + in between somethings, so it will take me a while to test.

1. LibreWolf is secure by default like that and i will not change it, maybe a call out that this is an extremely hardened version of firefox.
2. location is not something i can fix, this is something for librewolf devs/ ut devs to work on.
3. UI bugs relating to clipboard are due to xwayland and will be "fixed" by running under wayland when subsurface support is introduced.

@johndoe we are working on a plugin to lomiri system settings like Libertine plugin.

I already have most things implemented in backend, mostly lack some generation control over nix/home-manager left other then that mainly implementing the main UI, I have a design ready just need to implement it.

@domubpkm also kinda not related but genus level move, I moved the settings menu (3dot button) to the bottom left where the tabbar starts, this frees just enough space to make the XUI work with almost no other modifications.

@domubpkm
I'd estimate the total time spent to be around 110-120 hours.

Here's a breakdown of how it was spent:

• The first 5 hours were completed a couple of months ago building version 0.1.0, which involved creating a setup script for running LibreWolf with no modifications, @Fuseteam helped a lot with this considering his experience with uFirefox.
• The remaining work was done over the course of 2.5 weeks, with daily work sessions averaging around 7 hours, and some days going up to 12 hours.
• To avoid burnout, I took a few days off, roughly every 3 days, which helped to maintain productivity.
• It's worth noting that a significant amount of time was spent exploring and testing different ideas, many of which were eventually scrapped, which made the work more time-consuming, especially in the beginning.