版面

  • The Meta category: Organizational or general discussion.

    1k 主題
    10k 貼文
    KenedaK
    https://forums.ubports.com/topic/1405/please-use-general-category-for-what-it-is Kind of the answer to your question.
  • Discuss news updates from Ubuntu Touch and its related projects

    1k 主題
    5k 貼文
    messayistoM
    @uxes I actually overlookd the link to the thread
  • Discuss and solve problems with other users

    4k 主題
    29k 貼文
    O
    @Ehartwork Due to lack of time, I asked Google. So, hopefully someone here will correct any errors: Answer was: VoLTE & WiFi calling share some underlying code. But VoLTE code more on modem & WiFi calling in OS. Also, Halium 11, or newer . Better support with that (11) for WiFi Calling. (Nord N10 only on halium10). I suggested (different thread) that WiFi Calling get added to all device pages, to make the distinction that VoLTE works on some devices, but WiFi calling does NOT, at present, on most UT devices. This would help prospective UT users decide on device. Google also said that some developers said FP5 WiFi calling works sometimes, and this was due to different -newer- modem & firmware than most other phones. I bought Nord N10 months ago, under same bad assumption: VoLTE (YES) & WiFi calling (NO) work. Wasted huge money & time. Had to buy active cell signal booster. (more $ than I paid for the phone). BTW: No native RCS. (Just in case you expected that feature). Not listed, as far as I could tell, on devices pages.
  • Community section for all languages other than English

    18 主題
    90 貼文
    DJacD
    Pour la ROM d'origine : https://xiaomistockrom.com/xiaomi-redmi-note-7 Je n'ai pas le détail, mais je suppose qu'il faut utiliser "fastboot" pour l'installer. (Plus facile avec un PC linux : sinon, tu auras également besoin des drivers windows pour ton téléphone : https://xiaomi.eu/community/threads/installing-xiaomi-drivers-for-pc.73382/). Mais si vous aviez auparavant installé LineageOS, ce n'est sans doute pas un problème ?
  • 2k 主題
    20k 貼文
    H
    This tablet has no digitizer - it's a hardware limitation. So only touch input is supported, no active stylus will be recognized as such. You can still use it a soft-tip passive stylus for convenience, but it's essentially the same as using your fingers.
  • Discussions on development of Ubuntu Touch

    540 主題
    6k 貼文
    G
    @pparent said: it is an OS sepcific feature to decide how you are going to display the captive portal. now you have seen the reaction to your MR Quote from Gitlab: I have a deep interest in captive portal as a feature being also available to other distros (such as pmOS or Mobian)
  • Discuss the user experience or design of Ubuntu Touch or its apps

    168 主題
    2k 貼文
    I
    @sixwheeledbeast said: To me this seems like something that should be included into a toggle on the Battery pull-down menu itself, much like most modern devices have a "low power mode". How feasible would a toggle option to disable all these power hungry features and set the radio to the most energy efficient available in your location. Then toggling back would restore what you had previous. It seems like something the OS should provide and not additional apps. Something like this is already implemented in the OS. It is called "Flight mode" Humour aside, I don't know if it is really worth implementing switch for turning off all but 2G when it can be done in two or three clicks. But if you want to contribute to Ubuntu Touch this way, you can take a look at how it is implemented in lomiri-system-settings repository.
  • Creating Ubuntu Touch apps

    801 主題
    8k 貼文
    H
    Work wishes us to be familiar with the capabilities of AI, so I figured I'd let Opus 4.6 have a go at it. It did fix the immediate issue and here is the result: https://haagch.frickel.club/files/ubtouch_gps_fix/ gps-fix.tar.xz contains a build of the fixed library for current 24.04.1-2 and the scripts to install it, and restore the original version. For installing this system wide fix the root partition needs to be made writeable, then the library replaced, then it can be made readonly again. This worked here, but will need to be applied after every OS update until it is fixed upstream. Note that it's much better to reproduce a patched library yourself rather than installing a prebuilt one from a random stranger like me. The patch fix-gps-singleton-instance.patch it came up with is this: diff --git a/qt/position/core_geo_position_info_source.cpp b/qt/position/core_geo_position_info_source.cpp index 62e5cfd..a4eeb53 100644 --- a/qt/position/core_geo_position_info_source.cpp +++ b/qt/position/core_geo_position_info_source.cpp @@ -389,7 +389,25 @@ void core::GeoPositionInfoSource::Private::handleVelocityUpdate(const cll::Updat void core::GeoPositionInfoSource::Private::createLocationServiceSession() { - instance = std::make_shared<Instance>(); + // Keep the Instance alive as a process-wide singleton. The dbus-cpp + // asio executor uses a global static boost::asio::io_context + // (see dbus-cpp executor.cpp make_executor()). When an Instance is + // destroyed, its Executor::stop() calls io_context::stop() on that + // global object. Because the io_context is shared, this permanently + // poisons it: any subsequent io_context::run() returns immediately, + // so a new Instance's worker thread exits at once and all blocking + // D-Bus calls (transact_method / invoke_method_synchronously) hang + // forever waiting for a reply that will never be dispatched. + // + // QtWebEngine's LocationProviderQt destroys and recreates its + // QGeoPositionInfoSource on every geolocation request cycle, which + // triggers Instance destruction → io_context::stop(). On the next + // cycle a new Instance is created but its worker is dead-on-arrival. + // + // Fix: use a persistent static shared_ptr so the Instance (and its + // worker thread / D-Bus connection) lives for the entire process. + static std::shared_ptr<Instance> s_instance = std::make_shared<Instance>(); + instance = s_instance; try { session = instance->getService()->create_session_for_criteria(cll::Criteria{}); and the AGENTS.md and final_report.md files should contain enough info to reproduce this build via qemu and proot. As usual with AI generated fixes, I don't claim that this is the correct way to fix this, nor that there are no issues with this like leaks. So don't go around and demand someone merge this immediately. I just figured I'd post this because it'll make my own smartphone slightly more useful for navigation right now.
  • Porting Ubuntu Touch to new devices

    502 主題
    4k 貼文
    S
    @faveoled https://github.com/LineageOS/android_kernel_samsung_sm6115 is it kernel one?
  • Lomiri, the operating environment for everywhere

    77 主題
    636 貼文
    arubislanderA
    @developerbayman This thread is not about touch or gestures in Lomiri. It is about gestures on the virtual trackpad that the device becomes when it is connected to a screen wirelessly via Miracast.
  • Discussion on translating Ubuntu Touch and its core apps

    61 主題
    335 貼文
    lduboeufL
    said: Hello, With the next calendar-app release coming, a bunch of new strings are waiting to be translated, thanks for looking into it: https://hosted.weblate.org/projects/lomiri/lomiri-calendar-app/ Lionel oops forgot to mention the forum post about it: ( arf can't paste the link here), look into category OS->Call for testing: calendar-app)
  • A place to discuss ideas for promoting Ubuntu Touch

    57 主題
    731 貼文
    O
    @Moem yeah ... that is why I replied to MarcelloTogg - to see if cups WORKED for them, or they WANTED cups to work for them.
  • Other Projects

    Projects which are started by a group within the UBports community

    71 主題
    429 貼文
    arubislanderA
    @lsitongia I had missed the part where you said you were testing PR packages on the device.
  • For things that just don't fit in the other categories.

    899 主題
    5k 貼文
    MoemM
    @tahirmehmood Best of luck, I hope it helps!