Categories

  • The Meta category: Organizational or general discussion.

    1k Topics
    10k Posts
    bhdouglassB
    @danfro nope! Apparently it should have been -2 instead of -1. I've updated it in the original post.
  • Discuss news updates from Ubuntu Touch and its related projects

    1k Topics
    5k Posts
    UBportsNewsU
    Ubuntu Touch Q&A 182 Ubuntu Touch Q&A 182 is live this Saturday 24th January at 19:00 UTC on our YouTube channel: https://www.youtube.com/watch?v=k1j8DHT5MwI 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/11879/ubuntu-touch-q-a-182-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 #OTA11 #UTnoble #Ubuntu
  • Discuss and solve problems with other users

    4k Topics
    28k Posts
    G
    @domubpkm said in Working hours - Agenda: Still strange not being able to set the minutes. if the code is storing begin work in an integers variables called businessHourStart and businessHourEnd, there is no way that you will be able to register minutes since there is no variable called businessMinuteStart... Some code refactoring (and UI) would be needed for that.
  • Community section for all languages other than English

    9 Topics
    39 Posts
    CiberSheepC
    Let's see
  • 2k Topics
    20k Posts
    J
    @MrT10001 Thanks for that reminder I have had issues with Ubports install from certain ports in the past, I'll try a different one. Just hope that charging works without a working OS since it's now saying the battery is too low
  • Discussions on development of Ubuntu Touch

    530 Topics
    6k Posts
    K
    @garsbenjoe This has been reported. Mouse scrolling has improved in Noble but it's still not perfect. Scrolling speed is normal in webapps/browsers but scrolling only works on the first tab/webbiew you scroll, others won't work. It may also stop working on that tab for some unknown event/trigger.
  • Discuss the user experience or design of Ubuntu Touch or its apps

    164 Topics
    2k Posts
    G
    @mirroronthewall Yes, this is surprisingly useful, as it means you don't always have to whip out a hardware keyboard, which defeats the point of the small form factor of a phone. Missing support for modifier keys is a big issue when using GUI apps in Libertine, as touch-to-mouse conversion often doesn't behave as it should and can get you 'stuck', so a fallback to keyboard shortcuts is just as necessary there as it may be useful in general: actually, your idea of creating macros for anything seems to solve many problems (including mine) at once, so congrats - now we just need to figure out how! The closest I've found is Ambot Installer: Hacks and Mods, although I need to set up a persistent amd64 QEMU instance on my arm64 laptop before I can allow myself to experiment with it freely (it's the only way I got the installer working). Other tools may be available but I have not been able to surface them yet, I will update this thread as I learn more about the issue and potential solutions. [UPDATE] Here is a list of interesting posts related to this problem, which may be a good starting point for building a bridge towards the solution: These are previous conversations on the repos which appear to have been abbandoned: https://github.com/ubports/keyboard-component/issues/96 gitlab.com/ubports/apps/terminal-app/-/issues/78 https://gitlab.com/ubports/development/core/lomiri-keyboard/-/issues/96 Instead, here are some useful links related to Malakiboard, which should be a good foundation to build macro functionality on: https://github.com/kugiigi/jerk-click https://github.com/kugiigi/jerk-installer https://github.com/kugiigi/jerk-packages
  • Creating Ubuntu Touch apps

    782 Topics
    8k Posts
    G
    @PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer): certain types of D-Bus requested are blocked by AA (such as AuthorizePush I have actually taken a look at the ubtd code and as I understand it AuthorizePush is a method defined by ubtd for obex. Looking at the Ubuntu touch bluez code with some dismay, it seems that this method is defined quite officially to allow the obex daemon to send data to a client, squarely fitting your use case, so why is there no apparmor policy for that ? As a wild guess, it looks like an oversight by Canonical that was forwarded by Ubuntu Touch - or even an oversight by Debian, forwarded by Canonical, forwarded by Ubuntu Touch. Maybe a bluetooth policy should exist. Or maybe it already exists ? looking at usr.sbin.cupsd in my Kubuntu 24.04 installation, I see a string 'network bluetooth'. Maybe adding that to your apparmor profile could strike gold ? Absolutely wild guess of course
  • Porting Ubuntu Touch to new devices

    492 Topics
    4k Posts
    F
    @a20sporter can we take a look at your deviceinfo file?
  • Lomiri, the operating environment for everywhere

    76 Topics
    627 Posts
    K
    @uwahl I understand your concern but that is sadly not related to my post I'm talking about the virtual touchpad when connected to an external display.
  • Discussion on translating Ubuntu Touch and its core apps

    59 Topics
    329 Posts
    B
    @Vlad-Nirky Thank you. Done.
  • A place to discuss ideas for promoting Ubuntu Touch

    56 Topics
    716 Posts
    LakotaubpL
    @Jules We are aware of this and we are having a good look at it.
  • Other Projects

    Projects which are started by a group within the UBports community

    69 Topics
    400 Posts
    G
    @MrT10001 I don't quite remember what the installer did when I flashed my phone (happy memories... not ) but from browsing v2/checkDownloads.ts I'd say that the installer is saving stuff in a sub-directory called 'download' from the current directory when it was launched.
  • For things that just don't fit in the other categories.

    879 Topics
    5k Posts
    peat_psuwitP
    @klh said in My Ubuntu Touch devices participated in Thailand nationwide cell broadcast test: @peat_psuwit do you have a spec for the Thai EBS? Looks like they require a working SIM card? I have no idea where to look for that. I tried searching on web for it, but nothing that look like it. The only thing I can go by is Android's config file. I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification. In theory we should only need the table from 9.4.1.2.2 of 3GPP TS 23.041. Hmm interesting. That spec does indeed list all topics I've seen on my Android phone. I think I've seen a different spec cited earlier that doesn't include some of them. (For reference, I've seen the following topics: 4370, 4371, 4372, 4384, 4396) Still, it doesn't seem to provide a grouping of topics for settings (or maybe I miss something). And it would also be useful to have a database for notification heading (e.g. in US the title for 4370 should be "Presidential alert", but that obviously won't fly for Thailand). Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not. We don't already? According to the same table, 4370 is not supposed to be settable by the user and always subscribed (I'm kind of extending the 3GPP definition of MMI here) so this shouldn't be a question - since afaik it's not required to be implemented at modem level, we should check what ofono reports and subscribe to the missing ones. It's not supposed to be settable, but this doesn't seem to be enforced by oFono. Currently our settings pane doesn't subscribe to this topic, but apparently Fairphone 5 subscribes to this topic anyway. Still, I reckon that we should be on the safe side and always add 4370 to the list of subscribed topics. Also, currently there's no boot-time component which will subscribe to mandatory topics automatically (and on some region e.g. Thailand this doesn't seem to be limited to 4370 only; see the linked Android config). The settings pane is the only component which sets the topics. This is problematic because oFono don't have a set of initial topics (besides a small number of built-in ones from ETWS).