Categories

  • The Meta category: Organizational or general discussion.

    1k Topics
    10k Posts
    L
    @jam1388 said in Working VoLTE reports, share your experience: been hearing news about shutdown of 4g on t-mobile starting next month and only certain 4g devices will work ... I just hope this phone continues to work after the phase out of 4g how much speed do we need LOL!! hello @jam1388 ! I totally agree with you! I just got my NORD n10 5g to work today and in the device verification via T-Mobile webpage, sadly, I think it said this won't work with the satellites. Hope we can get a couple of good years out of it nonetheless. big THANK YOU for sharing your detailed experience in the OnePlus Nord N10 5g thread. I was inspired to attempt it after seeing you and others succeed!! I really, truly want to express my sincere GRATITUDE to everyone in this wonderful forum and project in general. The developers, product mgrs, maintainers, support, forum members ... you are all HEROS to me! Let's keep it alive.

  • Discuss news updates from Ubuntu Touch and its related projects

    1k Topics
    5k Posts
    UBportsNewsU
    Today is Ubuntu Touch Q&A Day Ubuntu Touch Q&A181 is today at 19:00 UTC please join us on YouTube: https://www.youtube.com/watch?v=mKmWQ14BKlY Questions can still be posted here https://forums.ubports.com/topic/11828/ubuntu-touch-q-a-181-call-for-questions for priority or live in the show. UBports@telegram #ubports:matrix.org #UBports #UbuntuTouch #UBportsQandA #Lomiri #OTA11 #Ubuntu #UTnoble #MobileLinux

  • Discuss and solve problems with other users

    4k Topics
    28k Posts
    U
    With the new update 3.5.0 the bug of nonsense voice routing commands has been fixed.Thank you for the geat app!

  • Community section for all languages other than English

    9 Topics
    29 Posts
    yumi83Y
    Eine kurze Anleitung, wie man das Xperia X mit Ubuntu Touch bringt. Dieses Tutorial wurde geschrieben bevor das Xperia X im Ubuntu Touch Installer erschienen ist. Sobald das der Fall ist, sollte dieser Weg bevorzugt werden. Schritt 1: Alle Daten auf dem Gerät sichern. Das betrifft übrigens auch eine Partition mit DRM-keys. Sollte Dir Ubuntu Touch nicht gefallen und du willst zurück auf Android und da noch Netflix-Serien schauen, solltest du einen Blick hier drauf werfen: https://together.jolla.com/question/168711/xperia-x-backup-ta-partition-before-unlocking- bootloader/ Schritt 2: Das richtige Android installieren! Das Gerät muss auf Android 8 sein! Bei Android 7 oder älter funktioniert diese Installationsmethode nicht. Um das Gerät zu upgraden unter Einstellungen->System->Software Updates so lange upgraden bis Android 8 erreicht wurde. Das kann ein paar Stunden dauern. Alternativ gibt es das Sony-Flash-Tool welches dummerweise nur auf Windows funktioniert. Ihr könnt es hier herunterladen: https://developer.sony.com/develop/open-devices/get-started/flash-tool Dieses Tutorial-Video von Sony zeigt wie das ganze funktioniert: https://www.youtube.com/watch? time_continue=115&v=ieYxHKb-eMg Schritt 3: Nun muss der Bootloader entsperrt werden. 3.1) Gehe dafür zuerst in die Telefon-App und gib dort ein: ##7378423##. Unter Service info > Configuration > Rooting Status sollte Yes stehen. Sonst kommen wir hier wohl nicht weiter ... Aktiviere nun die Entwickleroptionen indem du in der Einstellungs-App unter "System" auf "Build Number" 10 mal hintereinander schnell drauf tippst. Anschließend gehst du eine Ebene zurück und in die Entwickleroptionen und aktivierst den "OEM Unlock"-Schalter und den "Adb debugging"- Schalter. 3.2) Nun brauchen wir die IMEI deines Gerätes. Diese Nummer ist für jedes Gerät einzigartig und findest du in den Einstellungen unter "System" und "Status". Mit der IMEI kannst du Deinen Unlock-Key erhalten auf dieser Website: https://developer.sony.com/develop/open-devices/get- started/unlock-bootloader/ 3.3) Jetzt gehen wir in den Fastboot-Modus! Ich gehe mal davon aus, dass du einen PC mit Ubuntu hast. Erst einmal brauchst du fastboot. Öffne das Terminal und gib ein: sudo apt install fastboot adb Sobald das installiert ist schließt Du dein Xperia X an den PC an und gehst in den Fastboot Modus mit dem Befehl: adb reboot bootloader Auf dem Xperia X erscheint noch ein Dialog, ob Du deinem eigenen PC vertrauen willst. Falls dem nicht so ist, das Problem mithilfe dieser Url bitte beheben: https://www.selbstbewusstsein-staerken.net/ Auf dem Xperia X sollte nun die Status-LED blau leuchten. Jetzt kannst du den Bootloader entsperren mit dem Befehl: fastboot oem unlock 0xHIERDEINENUNLOCKCODEHIN Also falls dein Unlock-Code z.B. 1234 ist: fastboot oem unlock 0x1234 Wenn jetzt kein Fehler angezeigt wird, können wir weitermachen. Schritt 4: Zusätzliche Binaries installieren. Wir müssen nun hier eine Datei herunterladen, die wir vor Ubuntu Touch flashen müssen: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ Sobald wir diese haben, flashen wir sie (wir sind noch im Fastboot-Modus. Der Modus mit der blauen LED!) mit: fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img Schritt 5: Ubuntu Touch installieren (endlich)! Ab hier kann man mit dem ubports-Installer weitermachen! Oder: Lade dir das Flash-Tool herunter und installiere es: https://ci.ubports.com/job/goget-ubuntu-touch/job/bionic/5/artifact/ubuntu-device- flash_0.35+ubports+0~20181221200828.5~1.gbpd7daaa_amd64.deb Anschließend kannst du aus Fastboot heraus Ubuntu Touch installieren: fastboot erase cache fastboot erase userdata fastboot erase system ubuntu-device-flash touch --device=suzu --channel=16.04/arm64/hybris/stable --bootstrap Wenn alles durchläuft aber das Gerät nicht booten möchtet, dann hast du wohl eine zu alte Android Version. Also ab zurück zu Schritt 2. Wenn noch nicht mal das Recovery erscheint, dann hast du wohl nicht genug gewiped. https://together.jolla.com/question/168711/xperia-x-backup-ta-partition-before-unlocking- bootloader/

  • 2k Topics
    19k Posts
    W
    @oldbutndy In Ubuntu Touch, all "About This Device" tells me is "OneplusN10". Looking up IMEI didn't yield anything specific about model #. My best guess after some reading on XDA: BE2025=Metro(USA?) BE2026=North America, non-network BE2028=TMobile(USA?) BE2029=Global except stupid North American market? Anyway, mine does NOT have a dual SIM, and I never saw Metro or T-Mobile on boot, so I presume it's BE2026. Happy to check further if you know how. But sounds like BE2026 (if you can get your hands on it) or non-eBay purchase is the way to go? Thanks for the info about them asking for sales receipts, BTW.. I'm considering buying a replacement N10 for my poor broken old one, now that VoLTE seems to be coming along. 3G is slowly being sunset up here in Canada too. I've been trying to get a Redmi Note 9 Pro working, but can't get bootloader unlocked, and network coverage isn't great anyway.

  • Discussions on development of Ubuntu Touch

    531 Topics
    6k Posts
    R
    A related project to look at: https://blog.mariofragnito.it/en-gb/posts/pitv-my-fire-tv-stick-clone/

  • 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

    779 Topics
    8k Posts
    developerbaymanD
    @Voorstad so truly im developing a new meshtastic protocol called “meshnet” it utilizes exoandabke lane bonding like lornawan but meshtastic bonded ideally up to 12 lanes allowing up to 2 mbps while range still effects speed will have greater distance .....its a thing but also eventually i too will be making a UT app while it will be meshnet ...meshnet is also backwards compatible with regular meshtastic so this will be included as well ....i have two dev boards coming this month then im gonna buy alot of radios

  • Porting Ubuntu Touch to new devices

    488 Topics
    4k Posts
    L
    Trả lời: Build Ubuntu Touch error : Halium initrd Failed to boot I fixed this problem . sorrry, is my mistake comand method : ./prepare-fake-ota.sh out/device_gta7litewifi_usrmerge.tar.xz ota ./system-image-from-ota.sh ota/ubuntu_command images adb push images/rootfs /data/ubuntu.img and next its success to run kernel but cant mount my rootfs (i see it at dmesg log) i think i need more time to make this tablet work correct with ubuntu touch here ís log in dmesg : [ 12.541550] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 12.649706] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 12.649734] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 12.757704] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 12.757732] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 12.865462] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 12.865490] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 12.973712] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 12.973739] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.081820] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.081848] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.189704] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.189732] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.280059] -(4)[0:swapper/4]mtk_charger_alarm_timer_func: not suspend, wake up charger [ 13.280594] -(4)[321:charger_thread]mt635x_auxadc_read_raw: 10 callbacks suppressed [ 13.376047] (4)[321:charger_thread]mt6370_pmu_chg_get_property:chg_stat = 2 [ 13.405702] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.405730] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.513578] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.513606] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.595980] (4)[321:charger_thread]mt6370_pmu_charger mt6370_pmu_charger: mt6370_dump_register: ICHG = 500mA, AICR = 500mA, MIVR = 4600mV, IEOC = 150mA, CV = 4400mV [ 13.596001] (4)[321:charger_thread]mt6370_pmu_charger mt6370_pmu_charger: mt6370_dump_register: VSYS = 4355mV, VBAT = 4330mV, IBAT = 0mA, IBUS = 300mA, VBUS = 4900mV [ 13.596011] (4)[321:charger_thread]mt6370_pmu_charger mt6370_pmu_charger: mt6370_dump_register: CHG_EN = 1, CHG_STATUS = done, CHG_STAT = 0x80 [ 13.596021] (4)[321:charger_thread]mt6370_pmu_charger mt6370_pmu_charger: mt6370_dump_register: CHG_CTRL1 = 0x10, CHG_CTRL2 = 0x1B [ 13.596084] (4)[321:charger_thread]charger_routine_thread zhi end , 0 [ 13.621702] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.621730] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.729417] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.729443] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.837613] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.837640] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 13.945537] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 13.945564] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.053710] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 14.053738] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.161509] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 14.161536] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.269740] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 14.269771] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.377799] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 14.377827] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.485704] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 14.485731] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.557524] (2)[133:kworker/2:1][sensorHub] sensorType = 0, action = 8 [ 14.557681] (6)[7:kworker/u16:0][SCP] scp_ipi_send: SCP A not ready [ 14.557700] (6)[7:kworker/u16:0][sensorHub] scp_ipi_send fail [ 14.557911] (2)[133:kworker/2:1][sensorHub] scp_sensorHub_req_send fail! [ 14.593509] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 14.593536] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 14.701610] (6)[279:teegris rpmb]TZDEV ERR tzdev_teec_connect(60): Failed to connect to root_task socket after 20 retries [ 14.701633] (6)[279:teegris rpmb]TZDEV ERR TEEC_InitializeContext(208): Failed to connect to root task, context = 0000000000000000 ret = -111 [ 15.229710] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.229738] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.325696] (4)[14:tz_kthread_hear]TZDEV: heartbeat smc for reschedule [ 15.337692] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.337720] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.445555] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.445583] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.553729] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.553756] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.661419] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.661445] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.769705] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.769733] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.877735] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.877763] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 15.985392] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 15.985426] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 [ 16.097383] (6)[279:teegris rpmb]TZDEV ERR tz_iwio_alloc_iw_channel(175): IW buffer registration failed, error=-111 [ 16.097410] (6)[279:teegris rpmb]TZDEV ERR tz_iwsock_connect(619): Failed to connect socket root_task, error=-111 and i found some folder create in /data : $ adb shell gta7litewifi:/data # ls android-data cache lost+found media system-data ubuntu.img user-data gta7litewifi:/data # ls system-data etc nix opt root var gta7litewifi:/data # ls user-data/phablet Documents Downloads Music Pictures Videos gta7litewifi:/data # are you have any idea?

  • Lomiri, the operating environment for everywhere

    75 Topics
    624 Posts
    A
    I also struggled getting into a development ready state due to the readme inconsistencies. An unfortunate barrier to entry. That said, it looks like this would bring Clickable deps up to date for Noble (once merged): https://gitlab.com/ubports/development/core/lomiri/-/merge_requests/254

  • 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

    67 Topics
    397 Posts
    I
    @uxes That is a great program, but I heard that ATL relies on GTK. Which is not integrated into UT. And besides, list of supported apps is limited compared to Waydroid.

  • For things that just don't fit in the other categories.

    872 Topics
    5k Posts
    O
    @Moem said ... most of us have full lives and don't read the forums every day. Me too, usually. I just focused to try to get something working, due to 30 day ebay seller return policy. Failed interaction with Oneplus support ate up 12 days of that.