host you could use google drive or whatever is allowed in your country

what doesnt someone simply host a repo for all the images IN russia and fork the installer??

@projectmoon yes people in those situations should obtain their images another way like the gitlab or whever they keep their specific image ,....its gotta all be manual

@Vlad-Nirky im not sure what you mean you need to downgrade to the appropriate android version for your device then get the ubuntu touch install files extract it and you gonna hold on my phone volume and up then it will enter fast boot mode then your gonna flash the same files usually the same name as the partion something like this fastboot flash boot boot.img && fastboot flash recovery recovery.img && fastboot flash system system.img && fastboot flash userdata userdata.img .......if you dont know about adb or fastboot you will need to look those up first and have a tiny bit of comfortability in a terminal ...but its pretty easy

obtain your image and fastboot flash the image manually or per your device guidelines for manual flash

this is sweet

@projectmoon exactly i dont mind confinement anymore as i used complain because i didnt understand now i do and i see ALOT of missing api thats why i made "workspace" --->still needs lots of testing but i have to say im not happy having to make a workaround solution ....as it kinda breaks the whole design point ..

take this guys really cool app https://forums.ubports.com/topic/12261/for-testing-radio-alarm-for-ubuntu-touch .....dude had to make a unconfined app for a alarm clock .....let that sink in for a minute with the security implication of app confinement .....the security is great but i think the execution needs for work ....also am i not understanding?? ....like i know content hub needs more completion ...so is this a task for content hub that just never came to be so im disgruntled not knowing thats where the doorway to capability lives?? or supposed to live?? but was never implemented??? maybe i need to learn more about the original history of design direction for UT

simple question really ...do we really need app confinement?? ...like i get it security purpose and the original idea and all ...but like everyone including myself is making unconfined apps because xyz does not work ....and this is actually a really big list of xyz ...so i guess i just dont understand why we are still trying for this thing that is very much in the way ...app confinement? ....im not even complaining its just a genuine question what is the future plans for this?? or is there any?? ....feels like limbo to me

i know this is old but i think its cool when it does that lol ...shows me its paying attention ....3 years+ in the making

so im reading and my AI : I would not use a chroot for this in a normal confined Click app.

A real chroot() needs privilege/CAP_SYS_CHROOT, and even inside a chroot the process would still be under the same Ubuntu Touch AppArmor confinement. So it would not really solve the app-store/confined-app problem; it would mostly move the path problem somewhere harder to debug.

For EFL/pEFL the better confined solution is to make the Click package look like the EFL install prefix at runtime:

1. build/install EFL and pEFL into the Click package, for example under usr/
2. ship the needed usr/share/elementary, usr/share/efreet, locale files, Perl module files, and .so files with the app
3. start the app through a wrapper script that redirects EFL, XDG, Perl, and HOME paths into the app’s own confined directories

Example launcher idea:

#!/bin/sh
set -eu

APP_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"
APP_ID="hellopefl.maxperl"

APP_HOME="/home/phablet/.local/share/${APP_ID}"
APP_CACHE="/home/phablet/.cache/${APP_ID}"
APP_CONFIG="/home/phablet/.config/${APP_ID}"

mkdir -p "$APP_HOME" "$APP_CACHE" "$APP_CONFIG"
mkdir -p "$APP_HOME/.cache/efreet"
mkdir -p "$APP_HOME/.elementary/config"

export HOME="$APP_HOME"
export XDG_DATA_HOME="$APP_HOME/.local/share"
export XDG_CACHE_HOME="$APP_CACHE"
export XDG_CONFIG_HOME="$APP_CONFIG"
export XDG_DATA_DIRS="$APP_DIR/usr/share:/usr/local/share:/usr/share"

export ELM_PREFIX="$APP_DIR/usr"
export ELM_BIN_DIR="$APP_DIR/usr/bin"
export ELM_LIB_DIR="$APP_DIR/usr/lib/aarch64-linux-gnu"
export ELM_DATA_DIR="$APP_DIR/usr/share/elementary"
export ELM_LOCALE_DIR="$APP_DIR/usr/share/locale"

export LD_LIBRARY_PATH="$APP_DIR/usr/lib/aarch64-linux-gnu:$APP_DIR/lib/aarch64-linux-gnu:${LD_LIBRARY_PATH:-}"
export PERL5LIB="$APP_DIR/usr/lib/aarch64-linux-gnu/perl5:$APP_DIR/usr/share/perl5:${PERL5LIB:-}"

exec "$APP_DIR/usr/bin/hellopefl" "$@"

The important bit is that /usr/share/elementary should become $APP_DIR/usr/share/elementary inside the Click package, and EFL should be told about that prefix with the ELM_* variables instead of trying to read/write the real device /usr or /home/phablet.

For Clickable, the rough shape would be:

builder: cmake
framework: ubuntu-touch-24.04-1.x

dependencies_host:
  - perl
  - make
  - pkg-config

dependencies_target:
  - libefl-all-dev

libraries:
  pEFL:
    builder: custom
    src_dir: libs/pEFL
    build:
      - cd "$SRC_DIR" && perl Makefile.PL INSTALL_BASE="$INSTALL_DIR/usr"
      - cd "$SRC_DIR" && make
      - cd "$SRC_DIR" && make install

install_data:
  "${PEFL_LIB_INSTALL_DIR}/usr": "usr"

install_root_data:
  - run-pefl.sh

install_lib:
  - "libefl.so*"
  - "libelementary.so*"
  - "libeina.so*"
  - "libevas.so*"
  - "libecore*.so*"
  - "libedje.so*"
  - "libefreet.so*"

That example will need the exact library list adjusted after running ldd on the final binary/module, but the direction is: bundle the runtime prefix, then point EFL and Perl at the bundled prefix.

read_path/write_path can help for specific paths, but I would treat that as a last resort. A confined app should work from its own packaged resources and its own .config, .cache, and .local/share directories.

A helper app/broker such as Workspace could be useful during development for copying logs, staging files, checking AppArmor denials, or preparing the bundle, but I would not make the final pEFL app depend on an unconfined/root broker just to launch. That would be useful for side-loaded developer/admin workflows, not the clean confined Click solution.

i think the last thing im gonna drop is "game native" im trying to port the latest version to UT as well so we can play our steam games ....after that i think ill start at the beginning and start refining everything starting with python deploy ....then openstore ....hopefully i gain some feedback by then so i can get all the bugs ....my problem is time ....i get something running i swipe around a little ....i dont have a use or need at the moment so im like "seems to work" then see something shiny over there and go do that .....if i get game native to work well people will prob want to starst porting UT to much higher end devices ....i dont think my phone has the power .....but i wanna play helldivers 2 on my phone someday

**super alpha im sure bugs

@oldbutndy iv updated this and should actually work now please let me know next ut office im like 70% there

@oldbutndy i have not because i dont own a printer ....so your my guy if you dont mind .....as of writing this i have to build and test some so im gonna try to post something ....also in workspace i discovered mad flaws so i need to do some repairs before i think itll actually work ....as of right now i dont think workspace really works also for that im gonna really need the broader experience from the community ...some of the features i added in i cant even test printing for example ....i do have a 3d printer though

@oldbutndy honestly i think its this ....and honestly your the the most interested person so far i think?? ...i was hoping as i was cranking all these app out people would test and report back all those things for all the apps so i could focus on fixing the list of broken things ...this isnt the case it seems so i have to basically do everything so its taking a bit ....im not mad or anything i just was expecting a slightly different scenario ...thats prob my bad for having pre-expectations

heads up i forgot to re-enable some of the build chains during debugging so this is broken till i post the update

you need to go to settings and set your usb to tethering ....there is your internet connection it should just work when you plug it in and connect ...if im understanding you correctly?

@oldbutndy

@oldbutndy yes there is a UT version in progress