World

Topics from outside of this forum. Views and opinions represented here may not reflect those of this forum and its members.

A world of content at your fingertips…

Think of this as your global discovery feed. It brings together interesting discussions from across the web and other communities, all in one place.

While you can browse what's trending now, the best way to use this feed is to make it your own. By creating an account, you can follow specific creators and topics to filter out the noise and see only what matters to you.

Ready to dive in? Create an account to start following others, get notified when people reply to you, and save your favorite finds.

Register Login
  • R

    I would like to run the 'community favourite app' awards again later this year but there are a few things that could have been a bit improved.
    One issue was that we didnt have a nice award.

    It would be good to gather something meaningful to provide as a reward to the developers. I was thinking to organise a fund raiser of sorts but I dont know what works best in this type of crowd.

    What types of fund raising has worked in the past?


    read more →
    @RJDan said: @tunnel rush I would like to run the 'community favourite app' awards again later this year but there are a few things that could have been a bit improved. One issue was that we didnt have a nice award. It would be good to gather something meaningful to provide as a reward to the developers. I was thinking to organise a fund raiser of sorts but I dont know what works best in this type of crowd. What types of fund raising has worked in the past? From what I’ve seen over the years, small voluntary donations usually work better than complicated fundraising schemes. People are far more willing to throw in a few dollars when the process is simple and transparent. Even a modest prize pool plus a custom digital badge/trophy can mean a lot to indie developers.
  • T

    Hi everyone I want to start a UB Port to Nokia 6.1, and I have no experience in porting, can anyone help me get started on this project.


    Hi @Thomasb98, There is a documentation: https://docs.ubports.com/en/latest/porting/introduction/ Hope it helps... It seems feasible because this device is supported by lineageos and kernel source code is available: https://wiki.lineageos.org/devices/PL2/ Do you have the version with 4 GB of RAM or the one with 3 GB?
  • T

    UT24.04-1
    There is no USI2.0 support, hence Tiro pen can not be used with UT, unfortunately


    @thomasf Check this topic.
  • T

    It took me a while: Now there is touch sensitivity for the Volla Tablet. It can be used for clicking, mouse movements, even basic handwriting.

    Disclaimer:

    1. This instruction is for the Volla Tablet with Volla Pen Tiro. I have not tested this on any other device.

    2. This fix only works for touch events and is a work-around until MIR support for pen input is fixed. Pressure sensitivity may come with MIR version 2.0 (roadmap this year) or never at all. Whenever there will be true pressure sensitivity the udev rules below have to be reverted / adjusted.

    3. There is a bug in the libertine container (https://forums.ubports.com/topic/12135/input-events-in-right-third-of-screen-in-landscape-mode-are-not-registered-only-in-libertine-container😞 If you want to use landscape orientation (as is normal when using the keyboard) there is no input in the right third of the screen which is annoying. The container works fine in portrait mode. In the above mentioned post you can also get an idea how handwriting looks like with touch input.

    4. We have to write directly to the system partition, so installed libraries or udev rules might be overwritten with any update.

    This instruction is working on ubuntu touch 24.01 stable with update version 437 (March 2026).

    If you can live with the above - here is how to get the pen working. I will give detailed instructions, maybe other hardware / stylus combination may work in similar ways:

    Make the system partition writeable:

    sudo mount -o remount,rw /
    

    Install the following packages:

    sudo apt install evtest
    sudo snap install libinput
    

    find the input device: look for stylus, .... The Tiro Pen uses himax-stylus, make a note of the device identifier, e.g. himax-stylus. If there is no stylus: sorry, your journey ends here.

    sudo snap run libinput.list-devices | grep Device
    # for the Volla Pen Tiro:
    # Device:        himax-stylus
    

    output info regarding your stylus - replace himax-stylus with your pen. Also: it should have a line with Capabilities and Calibration. Note the event number (line starts with Kernel:)

    sudo snap run libinput.list-devices | sed -n '/himax-stylus,+20p'
    # Kernel:     /dev/input/event8
    

    Are events registered? Replace with your event number, quit with Ctrl + c

    sudo snap run libinput.debug-events --device /dev/input/event8   # Touch the screen with the pen
    sudo evtest /dev/input/event8   # Pressure sensitity support? Press lighter and harder with the pen: do ABS_PRESSURE values change? 
    

    If /dev/input/event8 exposes ABS_PRESSURE, and the device is (back) in tablet mode (ID_INPUT_TABLET=1, Capabilities: tablet), then the hardware/kernel side may already be capable of real pen pressure. In the Linux input model, ABS_DISTANCE is hover distance, while ABS_PRESSURE is the pressure axis; BTN_TOOL_PEN/ BTN_TOUCH describe pen presence and contact.

    The output of

    udevadm info -q property -n /dev/input/event8 | grep '^ID_INPUT'   # replace with nur event number
    

    shows which mode the stylus is currently in:

    • ID_INPUT_TABLET=1 (default): the pressure sensitive mode (if the stylus has the capability)
    • ID_INPUT_TOUCHSCREEN=1: touch mode

    ID_INPUT_TABLET=1: The driver actually reports pressure but MIR graphical surface is not reacting to it. No way to fix this. Let's switch to touch sensitivity (ID_INPUT_TOUCHSCREEN) so at least we get some events registered.

    Let's use udev rules to remap the events: create a new rule

    sudo nano /etc/udev/rules.d/99-himax-stylus-as-touch.rules
    

    Redirecting input: Use your own stylus identifier from above, it is necessary to distinct this event from touch (hand) input and mouse events.

    ACTION=="add|change", SUBSYSTEM=="input", KERNEL=="event[0-9]*", ATTRS{name}=="himax-stylus", \
      ENV{ID_INPUT}:="1", ENV{ID_INPUT_TABLET}:="", ENV{ID_INPUT_TOUCHSCREEN}:="1"
    

    Apply the rule: reload udev and retrigger the device

    sudo udevadm control --reload
    sudo udevadm trigger /sys/class/input/event8   # replace with nur event number
    

    Then verify:

    udevadm info -q property -n /dev/input/event8 | grep '^ID_INPUT'
    # it should list ID_INPUT_TOUCHSCREEN=1
    

    you may need to restart the system. if it still says ID_INPUT_TABLET check your input. Test your pen with swiping from top or the left / right screen border.

    To revert the rules: delete / comment the lines in the rules file and reboot.
    If later on you want to test pressure sensitivity you can also switch to tablet mode with

    ACTION=="add|change", SUBSYSTEM=="input", KERNEL=="event[0-9]*", ATTRS{name}=="himax-stylus", \
      ENV{ID_INPUT}:="1", ENV{ID_INPUT_TABLET}:="1", ENV{ID_INPUT_TOUCHSCREEN}:=""
    

    and reload / retrigger:

    sudo udevadm control --reload
    sudo udevadm trigger /sys/class/input/event8   # replace with nur event number
    

    I will write an instruction how to setup xournal++ app for handwriting later in another post.


    Thanks @tusch001 this was very helpful and worked on the stable Focal channel with Snapz0r installed. I would recommend one change: the sed command should read- sudo snap run libinput.list-devices | sed -n '/himax-stylus/,+20p' instead of: sudo snap run libinput.list-devices | sed -n '/himax-stylus,+20p' A few practical questions for you or anyone else: What kind of daily battery life are you seeing for the stylus, over how many hours of use? Do we know if it's compatible with other UT devices? In Libertine, is there a convenient way to anchor the stylus' nib to things like scroll bars? I've been trying to scroll up/down on VS Code but it's quite cumbersome and feels like I have to press it multiple times then do a small flick to get it to scroll by a little bit every time. Kind of much like using my finger (it's just that the nib is so much more small and thus more of a precision instrument compared to anyone's finger!). Unfortunately I need to figure out how to get my Volla Keyboard accessory working again and thus I don't have access to its touchpad and a mouse cursor (I've been using a bluetooth keyboard instead), so this would be a great workaround for the time being if it's possible. On an OS level: Hopefully someone can formally implement this into an OTA upgrade for the tablet on Noble and potentially even a maintenance release on Focal? The code changes look straightforward if they're just about changing the udev rules and such. I have been working on contributing to app development on and off but as a) the tablet is a bit of a daily driver for me and I like to keep it on the stable channel and b) contributing to OS patches is something I'm not really familiar or comfortable with, it would be excellent to see this happen if someone else can help out.
  • sm-xcxS

    Heya, I'm a student who's got plenty time on their hands since my college hasn't started yet. In the meantime I've been actively testing Ubuntu Touch and have noticed how the devices page and other documentations lack updates. I unfortunately don't have a pc right now so I can't contribute in coding and development as of right now but I can offer to help in all kinds of documentation building stuff since I'm quite passionate about writing in general and I really wanna help the community however I can.

    I will do this by keeping myself updated on new developments, talking to community members and ofcourse testing things myself.

    So I'd like to ask, is this a welcomed effort??

    • xcx ❤

    @sm-xcx Hey xcx, how far are we with this project? what is still requirered to finish this project?
  • lduboeufL

    Hi all,
    I'm working on the new contact backend, herited from the work of @mardy .
    Full story here: https://gitlab.com/groups/ubports/development/core/-/epics/19

    Carddav integration is in progress ( Nexcloud and generic cardDav works, teaser here https://m.youtube.com/watch?v=VG6i2LLLML0 ).
    Contact to Birthday calendar done
    Some regressions on address book app fixed ( avatar, import, massive delete etc... )

    For the migration, my idea is to only migrate local default address book,
    Add a carddav integrated feature for working around the issue with custom setup and give contact manual sync first.
    We will still be able to backup the current db with some command lines, and import them via the UI.

    This is the first step before a rework of Address book app and have better sync management ( scheduled sync, etc... )

    Technical:
    The idea is to keep for now Evolution Data Server & co.
    Calendar, Alarms , 3rd party apps ? , Ayatanah Datetime, Bluez relies on it...

    Add a doemon for contact to birthday sync. ( by creating a Birthday calendar and storing birthday there )

    Integration of buteo* and friends for cardDav support.

    Still unknown: BT integration for e.g: Car kit contact list

    I would appreciate your help for making this transition as smooth as possible.

    • Address book app: better online account integration, collections management
    • BlueTooth contact sync ( not working too on Focal apprently )
    • Notifications for sync states ( we have some UI report from indicator transfer )
      ...

    At this time of writing, the "how to test" is not ready. Will edit when easier to install.


    Hello all, It has been decided to postpone the new contact backend to 26.04.x to avoid slowing down the overall roadmap. We will try to move also at that time to the new calendar backend.. 2 major internal changes in a row. I keep you informed.
  • Linus67L

    My personal use of cell phones:

    • Calls + text messages: I want to be reachable at all times
    • I only use the browser, email, messaging apps, cloud services, and other apps when necessary (like a camera)

    Most days, the phone is unused for 90% of the time it’s turned on. So for 90% of my usage, even a Nokia 3210 (with up to 260 hours of battery life) would suffice.

    Task: Given this usage pattern, how can I maximize battery life?

    Workaround:

    Install and open “UT Tweak Tools”
    For all apps: Prevent background suspension = ON

    • Location services = OFF
    • Bluetooth = OFF
    • Wi-Fi = OFF
    • Mobile data = OFF
    • G2 network (optional)

    Then run the script in the terminal:
    ...
    #!/bin/bash
    #Enables power-saving mode on all CPU cores

    for governor in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
    echo "powersave" | sudo tee "$governor" > /dev/null
    done

    echo “Power-saving mode has been enabled for all cores.”
    ...

    New scenario:

    • The phone enters deep sleep mode after a few minutes
    • You remain reachable by phone and text message
    • Set alarms and timers function normally
    • Power consumption drops to an incredible ~22mA (Pixel 3a)

    As a result, in this state, the battery level drops by only about 1–3% over a 10-hour period. (Tested on the Pixel 3a) Theoretically, a full charge lasts more than a week with minimal use. (see pritscreen)

    Advantage: There are hardly any restrictions. You can turn on mobile data or Wi-Fi at any time and use any app with an internet connection. Afterward, turn Wi-Fi and mobile data off again.

    Usage:
    With appropriate usage habits, this can be the default mode. The reduced processor performance is barely noticeable. Only launching apps takes 1–2 seconds longer.

    The cores can be restored to normal performance using this script.
    ...
    #!/bin/bash
    #Enables Schedutil mode (default) on all CPU cores

    for governor in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
    echo "schedutil" | sudo tee "$governor" > /dev/null
    done

    echo “Default mode (schedutil) has been enabled for all cores.”
    ..,

    It would be perfect if a “super power-saving mode” like that could be built into UT.


    read more →
    @Linus67 Thanks very much. Will try it out…
  • UBportsNewsU

    Ubuntu Touch Q&A 191 is live this Saturday 30th May. If you can, please join us at the usual time of 19:00 UTC.
    Before then, if you have any questions on or about Ubuntu Touch and UBports please post them below and we will do our best to answer them in the Q&A.

    Remember that questions on porting to device **** or its status, and questions on bugs, will not be answered.


    @UBportsNews Can you please remind people about the 'community favourite app' awards that will happen toward the end of the year. Toward the end of the year we will run the 'community favourite app awards' where we the community votes on our favourite apps for the year. Keep your eyes on what you use daily, pay attention when an app has some great updates and remember all those new apps. youll want all that info for the nominations and voting later. If you have ideas for fundraising for an award please do offer suggestions. It would be great to have something substantial to give the developers.
  • UBportsNewsU

    Ubuntu Touch Q&A 191

    Ubuntu Touch Q&A 191 is live this Saturday 30th May at 19:00 UTC on https://www.youtube.com/watch?v=hS6sOkNhX1s
    We will cover all the latest news and development, and your questions and answers.

    Questions can be posted live during the show or using this Forum link for priority https://forums.ubports.com/topic/12300/ubuntu-touch-q-a-191-call-for-questions

    Please remember that questions on porting to device **** or its status, or questions on bugs will not be answered.

    UBports@telegram
    #ubports:matrix.org

    #UBports #UbuntuTouch #UBportsQandA #Lomiri #OTA12 #UTnoble #Ubuntu


  • Linus67L

    Is there a simple command to disable mobile data in a script?

    nmcli radio wwan off
    nmcli connection down

    gsettings set com.lomiri.touch.connectivity.cellular data-enabled false
    gsettings set com.lomiri.touch.connectivity.cellular data-active false

    dbus-send ... com.canonical.Unity.Connectivity.SetCellularDataEnabled boolean:false

    /usr/share/ofono/scripts/deactivate-context /ril_0 1 (APN-Kontext entladen)
    /usr/share/ofono/scripts/set-gprs-powered /ril_0 false (GPRS-Modul abschalten)
    /usr/share/ofono/scripts/set-tech-preference /ril_0 gsm (Drosselung auf 2G/GSM)

    Nothing disables mobile data


    @gpatel-fr That´s perfect! Thank you very much for solving this stubborn problem. Now I can put the Pixel 3a into ‘Nokia 3210 mode’ with a single click. Calls and text messages work, and the battery lasts at least three days in this mode. #!/bin/bash # ==================================================================== # NOKIA 3210 MODUS: CPU throttling + All offline services (Pixel 3a) # ==================================================================== if [ "$EUID" -ne 0 ]; then echo "ERROR: Please run the script using: sudo $0" exit 1 fi echo "Enable Nokia 3210 mode..." # 1. Force CPU cores into power-saving mode for governor in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do if [ -f "$governor" ]; then echo "powersave" > "$governor" fi done echo "[✓] CPU throttling enabled." # 2. Turn off Wi-Fi nmcli radio wifi off echo "[✓] Wi-Fi disabled." # 3. Turn off location tracking (GPS) sudo dbus-send --system --type=method_call --print-reply --dest=com.lomiri.location.Service /com/lomiri/location/Service org.freedesktop.DBus.Properties.Set string:com.lomiri.location.Service string:IsOnline variant:boolean:false echo "[✓] Location tracking disabled." # 4. Turn off Bluetooth rfkill block bluetooth echo "[✓] Bluetooth disabled." # 5. Turn off mobile data sudo -u phablet DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/32011/bus" dbus-send --session --type=method_call --print-reply --dest=com.lomiri.connectivity1 /com/lomiri/connectivity1/Private org.freedesktop.DBus.Properties.Set string:com.lomiri.connectivity1.Private string:MobileDataEnabled variant:boolean:false echo "[✓] Mobile data disabled." # 6. Greenline-Service stop at user level XDG_RUNTIME_DIR=/run/user/32011 sudo -u phablet systemctl --user stop greenline.service 2>/dev/null echo "[✓] greenline.service stopped." echo "------------------------------------------------" echo "Success! CPU, wireless modules and GPS are in sleep mode." sleep 3
  • libremaxL

    If you've managed to bypass the access restrictions that prevent ubports-installer from working properly, please share your solution if you can.


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

    Hey all! As you know, a while back I was going through and updating older apps that got left behind on Xenial, when the rest of the community moved to Focal, and then on to Noble. One of those apps was a demo for a game called "CitySim" that never got finished. I spoke with the original author, but they decided that they did not wish to continue this work and gave me permission to fork and carry on, if I so desired.

    Well, I did. Slowly, and perhaps poorly (considering my woeful lack of programming skills), but for the past 6 weeks I've been trying to turn it from a demo of an idea into a playable game. I think I finally have a fairly decent working beta version of the game. The game includes features like:

    • Disasters
    • Traffic management
    • Happiness and population control
    • Scenarios or free play
    • In game assistants
    • Achievement badges
    • And much more!

    There are two known bugs at the moment, and they are:
    - No sound (intentional, as I still need to edit all the sounds) Now has sound, but can't mute yet.
    - Road tiles up-end when destroyed by a disaster (you'd have to see it to understand it) Fixed!

    • Not properly set up for translations (I need to fix that, so others can translate it, currently only displays english)

    But, as is, the game is playable, and I hope, enjoyable. But, I need some beta testers to help me out! In particular, I need to know:

    • Does it run on other phones and desktops?
    • How is the scaling on small/big screens?
    • Are the scenarios beatable?
    • Is it remotely close to something fun?
    • Any bugs or issues running/saving/loading/playing the game?
    • Disasters too often, or too few?
    • General feedback (I can't implement everything, and the goal is to keep it simple and relaxing, but feedback is always welcome)

    You see, mathematically, all of the scenarios are beatable, and badges obtainable. However, I had to adjust several because winning them wasn't "practical" with normal play. The overall goal for the game is a smooth, relaxing, city simulating experience. However, I know some might enjoy something a little more upbeat, so I added a few "tougher" scenarios to the mix.

    Currently only available for Noble.

    armhf
    https://gitlab.com/alaskalinuxuser/citysim-ubuntutouch/-/jobs/14471516899/artifacts/raw/build/arm-linux-gnueabihf/app/city.alaskalinuxuser_0.9_armhf.click?inline=false

    arm64
    https://gitlab.com/alaskalinuxuser/citysim-ubuntutouch/-/jobs/14471516900/artifacts/raw/build/aarch64-linux-gnu/app/city.alaskalinuxuser_0.9_arm64.click?inline=false

    The repository:
    https://gitlab.com/alaskalinuxuser/citysim-ubuntutouch


    @developerbayman Thanks! It is now available on the openstore, so I hope people will enjoy it!
  • V

    Share here your good an bad experiments with bleeding edge .

    Leaving the volte status topic to its purposes.


    read more →
    @egregiousecan There's some bug that causes random bootloop, forcing shutdown by holding all phone buttons simultaneously helps. I was also not able to boot into Ut 24.04 after upgrading from 20.04, I had to reflash the device with Android to do that.
  • Eric HE

    0. Product Authentication

    Verify your Xiaomi phone at official site

    1. Unlock the bootloader

    On Windows

    ℹ The steps below only need to be run once per device. They require a machine running Windows 7 or newer.

    ⚠ Unlocking the bootloader will erase all data on your device!
    Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from Ubuntu Touch once installed.

    See : Complete Guide to Unlocking the Bootloader: Announcement, Troubleshoot and Tips

    Other resources :

    All platforms

    MiUnlockTool developed to retrieve encryptData(token) for Xiaomi devices for unlocking bootloader.
    It is compatible with all platforms.

    2. Check the correct version of MIUI

    Ubuntu Touch for surya / karna is based on Halium 10 and Android 10 Ubuntu Touch rootfs so it requires an Android 10 based MIUI before it can be flashed on your phone. While custom ROMs like LineageOS 17.1 might work, they are untested and not recommended. Instead, use one of the Android 10 based MIUI from below.

    Pay attention to your device name before downloading the MIUI below. Make sure you download the right MIUI version for your device, type is fastboot, and Android version is 10.0!

    Device model Codename Latest Android 10 MIUI version
    POCO X3 NFC surya V12.0.9.0.QJGMIXM
    POCO X3 (India) karna V12.0.10.0.QJGINXM (tested by @mahdi_saad_bd)

    3. Flash MIUI

    On Linux

    1. Make sure a recent version of fastboot is installed
    2. Download your ROM - choose fastboot version
    3. Unzip your ROM
    4. Reboot your phone into fastboot mode (POWER + VOL_DOWN)
    5. Connect your phone to your PC
    6. Flash ROM using flash_all.sh script in your unzipped ROM.
      Depending on your Linux distribution and packages installed, you may or may not need sudo
      ./flash_all.sh
      

    On Windows

    Use Xiaomi Flash Tool — Official Mi Flash Tool.

    ⚠️ Several users have reported that recent versions do not work. The 20181115 version has been successfully tested.

    4. Install Ubuntu Touch

    Install a recent version of fastboot and adb

    It is tested that fastboot version 35 works.

    To display the installed version of fastboot

    fastboot --version
    

    Download / Install UBports Installer

    You can install Ubuntu Touch using the UBports Installer on your computer.
    Make sure your device is unlocked and has the required version of Android installed.

    Installation procedure

    1. Don't plug your phone
    2. Launch the installer on your desktop / laptop
    3. Reboot your phone into fastboot mode (POWER + VOL_DOWN)
    4. Plug your phone with USB
    5. Follow the instruction on screen
      (at first installation Bootstrap and Wipe Userdata checkboxes must be checked)

    Troubleshooting

    🔓 Check that the bootloader is unlocked (see section 1 of this document)
    📱 Verify that you have installed the correct version of MIUI (see section 2 of this document)
    🔧 Make sure a recent version of fastboot is installed

    • If installation fails with Partition not found error, try to update fastboot and adb.
    • If the installer cannot complete the download of the required files, try to use a VPN.
    • If installer stalls at step Adb is scanning for devices, try to check the Wipe Userdata checkbox during first installation.
    • On Windows, if installer stop at Rebooting to fastbootd, try to install the universal adb driver and reboot your computer.
    • Several users report that they have not been able to install Ubuntu Touch from Windows, but that they have been able to do so with Linux.
    • See also "Install Ubuntu Touch - Troubleshooting"

    If you do not find a solution, share your logs on Telegram (see section 5 of this document).
    You will find these logs in this folder:

    • ~/.cache/ubports on Linux
    • %appdata%\ubports on Windows

    5. Get help

    On Telegram

    6. Return to android

    If necessary, to return to android, flash MIUI (see section 3 of this document).


    @bad1080 Unfortunately, nothing is interchangeable with UT. Basically, your phone, running a specific version of Android, has low-level drivers and a partition layout that are very specific to that device. When UT is installed, the partition layout is modified from the original configuration, whilst the low-level drivers are retained. An intermediate layer between these Android drivers and UT is installed (Halium (9 or 10 or 11, etc.), which is also specific to your hardware. Finally, UT is configured to communicate with this Halium layer. Failure to adhere strictly to the prerequisites will, at best, result in a non-functional system; at worst, a phone that is permanently unusable. (My apologies to purists for this oversimplified explanation)
  • mihaelM

    When I change Message sound in the Settings, it is only after a complete restart that this is taking effect. Not even a Lomiri restart makes a difference, it needs a complete reboot.

    Is that only on my Oneplus 10G? - should I move this to my specific device forum?


    read more →
    @mihael yes it's a bug and probably in the push service. I tried to kill the service process (I don't know any other way to restart a service activated by d-bus) and after an initial failure (it seems that when the service is restarted it don't take in account the task that started it), the second time I sent a mail message the notification used the new sound. To be continued.
  • libremaxL

    In some countries (such as Russia, it seems), Internet access restrictions are so severe that using ubports-installer results in a failed installation.
    It would be helpful to have a list of the countries affected.
    (If you've found a workaround, you can share it here:https://forums.ubports.com/topic/12292/workaround-for-internet-access-restrictions-affecting-ubports-installer)

    So if your country is in this situation, please let us know by replying to this message.

    For now, the list includes:

    1. Russia

    @libremax Spain when there's football on the tv (I'm not joking)
  • J

    Radio-alarm

    One of the things I like: waking up to good music. So I made a radio alarm app.

    • It plays an internet stream URL
    • It has customizable volume, fade-in-time and snooze time
    • It shows a notification dialog with snooze option
    • It has fall-back audio if internet connection fails

    It is based on systemd timers and services. For details: see the documentation.

    For the first alarm, you need to type or copy/paste full URLs in the app. Not the nicest UI-design, I know. The ones below may get you going:

    For the fall-back audio you also need a URL (of a local audio file).

    Limitations

    • the app is unconfined, because I have not found confined ways to
    • all alarms are off after reboot
    • the notification dialog disappears after a period of 10 minutes; to switch an alarm off after that time, open the app and tap 'Stop running alarms'
    • you can test station URLs and alarms, but the UI is quit provisional

    Testing

    If you feel like trying it out: please do & comment!


    read more →
    At a suggestion from @sander I implemented the Content Hub to select the local fallback audio file. The API of https://www.radio-browser.info is great, and also already implemented by the Radio app as far as I can tell from a quick glance. So I would rather ask Patrick Fial (does he have an account on this forum?) to add something like a 'copy URL'-button to the station in the favorites-list of his app. Or create a merge request for this myself, of course. @vlad-nirky Classic2 yes! Not waking up too gently though ;-).
  • J

    I have this ContentPeer to provide me with a URL to an audio file. It should not play the selected file.

    ContentPeer {
        id: audioSourceSingle
        contentType: ContentType.Music
        handler: ContentHandler.Source
        selectionType: ContentTransfer.Single
        appId: "filemanager.ubports_filemanager_1.1.4"
    }
    

    This works (although one can select any file, not just audio files).
    But I would rather not have to specify the version number.

    I tried:

    • Not specifying the appId. The code now displays a ContentPeerPicker, with FileManager, Morph and Music. Filemanager works, but Morph shows only downloads so is limited, and Music nicely shows audio files but plays them when selected. That is no good obviously, but I don't know how to fix this.
    • Specify appId: "filemanager". Doesn't work.
    • Specifiy appId: "filemanager.ubports_filemanager". This shows the file manager, but when you select a file, it asks what you want to do with it, and that does not include 'return the URL' :-(.

    Anyone any ideas about how to get rid of the version number but retain functionality? Is there a way to obtain a full appId from a partial one?


  • P

    Hello
    I am not very familiar with this forum so I hope the post is appropriate. Apologies if not.

    I have an old Lenovo tablet with the above features. But on "preparations" is mentioned that kernel 3.15 or above is required.

    Is there any hope?


    @MrT10001 then I guess it's not for me. Thank you all for the clarification.
  • W

    I'm looking to test and be a tester for Ubuntu Touch on the Fairphone 6. I have my unlock code and read to load. If someone could point me in the right direction to work with admins/developers/etc, i would appriciate it. Currently, I still have/using Ubuntu Touch on my Fairphone 4. Works great.


    Buddy, is anyone already working on this device? What’s still missing, and how can I help?