UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • libremaxL

      Where does Ubuntu Touch come from? And why clarify it?

      Watching Ignoring Scheduled Pinned Locked Moved General
      12
      0 Votes
      12 Posts
      336 Views
      O
      Viability: hmmm, at the moment: No voice calls (no VoLTE) on Pixel 3A (which WAS a primary supported phone for UT), on UT in USA (which is the third largest phone market by country, or 4th largest by region, after Europe). [alternative: VOIP - NOT available in openstore for most recent version UT] That is pretty NON-Viable, if you want a phone you can make calls on. Is that the fault of the UT teams ? I would say NO, it is the fault of the much larger system cancelling 2G, 3G, (USA & Australia , etc, now, and changing worldwide, with plans in place over 10 years ago) and the fact that the drivers for the radio chips and most others are closed source or Android or whatever. Who would be the ones to fix it ? UT dev teams, if at all. Or, what about WiFi calling ? Not functional. Is that the fault of UT devs, or other main stream code (from the larger base) being unavailable ? OR some phone brands / models NOT supporting required radio bands in some countries. NOT Viable. I think PC's are a better analogy than cars, since we are mostly talking software here, not hardware. if using cars analogy, could mention how air bag manufacturers caused a huge recall problem for a variety of car manufacturers. Q: So, where did UT come from ? A: 1) a gigantic base of hardware and software: major players who recently CANCELLED (in some countries, and in process in others) the fundamental ability of UT to make phone calls, through changes to the larger hardware and software system. A: 2) a few dedicated, volunteer developers who are doing their best to modify code for specific devices to overcome above obstacles.
    • B

      Ubuntu Update on FP3+ und FP4

      Watching Ignoring Scheduled Pinned Locked Moved German / Deutsch
      3
      0 Votes
      3 Posts
      121 Views
      K
      @Bubu Auf welchem Softwarestand bist du denn jetzt und wo möchtest du hin?
    • N

      Xiaomi Redmi Note 7 (Lavender) Ubuntu 24.04.1 Status

      Watching Ignoring Scheduled Pinned Locked Moved Xiaomi Redmi Note 7
      3
      0 Votes
      3 Posts
      233 Views
      Vlad NirkyV
      @nparafe Hello. Thank you for sharing your experience. Regarding the noise during calls, which Android ROM was installed on the phone before installing UT?
    • N

      Problem installing snap

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Support
      14
      0 Votes
      14 Posts
      772 Views
      CaedemC
      @fredldotme noted, if a bit late
    • CaedemC

      Adding a feature list for Focal/Noble for the Redmi Note 7 (Lavender) (help wanted)

      Watching Ignoring Scheduled Pinned Locked Moved Xiaomi Redmi Note 7
      20
      1 Votes
      20 Posts
      2k Views
      CaedemC
      @qusay Thank you that is very helpful!
    • bhdouglassB

      OpenStore Stats for 2025

      Watching Ignoring Scheduled Pinned Locked Moved General
      5
      11 Votes
      5 Posts
      833 Views
      CaedemC
      This btw is also why I'm not so happy on the "dump xenial" train, there are more xenial devices than both focal and noble combined Funny seeing 47 focal amd64 downloads lol Maintaining 53 apps... That blows my mind
    • E

      How can I troubleshoot broken SMS?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Support
      29
      1 Votes
      29 Posts
      1k Views
      E
      @gpatel-fr Yeah, I noticed that about the logs too. The phone "thinks" I sent a text, and then it "thinks" I sent another text, but in the middle the phone does "not think" that I tried sending a photo message. Which I did. There's actually three message attempts in that timeframe. The photo message send(MMS) just might as well have never happened at all. It's completely missing, my human activity is not there logged in that moment. So the text messaging app itself probably would have sent the photo over to my carrier but it just never knew I attempted to send the photo from the OS to begin with? I don't know for now but I'm going to have to do the hard reset and wipe it all and start over. For now I need this working. I haven't gotten any text messages in over a week now and and I know how to get it working again. It just is what it is. I need to think about how I will add this to the bug report.
    • pparentP

      XWayland: Menu windows resized full screen and crash?

      Watching Ignoring Scheduled Pinned Locked Moved OS
      12
      0 Votes
      12 Posts
      775 Views
      G
      I did not try your method yet, however I debugged the problem in my method. It's something (I guess Lomiri itself) that is sending a signal when the window is paused while switching. It is killing xev. The fix is to use TweakUT to keep the terminal awake, then my method works whatever the launch mode (direct > or with starting a new task &>) So I could repro the problem you have seen. No discrepancy here. I have looked a bit at Firefox and Chrome under vanilla Linux (Kubuntu 24.04) and xev reports something very different than under UT. That is, no strange events, basically the system reports the menu being created and mapped and that's all. I have also 'packaged' a recent version of Firefox freshly downloaded from the editor's site, that is, I did env GDK_DPI_SCALE=2 MOZ_ENABLE_WAYLAND=0 DISABLE_WAYLAND=1 ./firefox and the menus in the top bar display (if no scaling were done, I'd guess that the menu would display if by a stroke of luck I could hit the minuscule screen area) So my guess is that's not a clever packaging trick, that's something that Firefox is doing differently than Chrome. I searched for a Chrome Linux arm64 build but it seems that Google has insufficient resources to generate arm64 Linux builds (it's not a joke, it's exactly what is said by a Google employee in the Chrome issue tracker). I'd say that as under UT Chrome and Firefox are hitting XWayland that is hitting Mir, the problem could be all the way down to Mir. The version of Mir in current 24.04 UT is woefully outdated. When it will be updated, the way forward will be to switch to Wayland anyway and drop XWayland.
    • 4

      Synchronize appointments with caldav and radicale

      Watching Ignoring Scheduled Pinned Locked Moved Support
      2
      0 Votes
      2 Posts
      393 Views
      U
      I'm suffering the same. I have a radicale server and the calendars fail to syncronize with ubports 24.04 stable and fairphone 5. No problems with nextcloud accounts
    • libremaxL

      FOSDEM'26: FOSS on Mobile

      Watching Ignoring Scheduled Pinned Locked Moved General
      4
      3 Votes
      4 Posts
      275 Views
      libremaxL
      It's beginning now.
    • L

      Black screen issue

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Porting
      1
      0 Votes
      1 Posts
      140 Views
      No one has replied