1. Home
  2. Devices

Subcategories

  • Subforum for Asus devices

    4 Topics
    31 Posts
    A
    @odo According those who would know, UT has the best battery life of the different mobile linux's on the same device.

  • Subforum for BQ devices

    63 Topics
    469 Posts
    B
    @kaesestulle, Don't you have to activate the developer mode? Have you done it?

  • Subforum for Fairphone devices

    167 Topics
    2k Posts
    L
    @Martin5 said in Mobile data doesn't work: Error activating /ril_0/context1: org.ofono.Error.NotAttached: GPRS is not attached: @lduboeuf Yes, I checked them. They should be web.vodafone.de and they are. For reinstalling UT I got back to Android and installed UT from there. While on Android the mobile data worked just by activating it. Is there anything else to be checked? Should work. Just heard that if IMS is activated on Android, the operator may still use it, and UT does not know how to deal with it.So maybe if you can uncheck it on Android side or in the operator web site.

  • Subforum for Google Nexus and Pixel devices

    417 Topics
    4k Posts
    A
    @Abba Actually Miracast works quite well on the Pixel 3a now. But it is hit or miss if it will work with any particular Smart TV or dongle. If you are looking to buy a dongle, then as mentioned before the Microsoft one is the best bet. Otherwise Sony and Samsung smart TV's also seem to consistently work.

  • Subforum for JingLing devices

    15 Topics
    114 Posts
    M
    Hi @miy Did you manage to revive your Jingpad? If yes, can you please tell what you did?

  • Subforum for Lenovo devices

    86 Topics
    764 Posts
    M
    @Luksus Every one I have tried via fastboot, it boot loops. I haven't used the installer for the 2Gb version.

  • Subforum for LG devices

    10 Topics
    142 Posts
    T
    Hello all, I have been working on porting UT to a LG V60 ThinQ 5G. I have a few issues to work out still, but the key 2 items that I am currently working on are VoLTE (I got the ims service to start with no errors, but still no VoLTE sadly) and the brightness. I have the brightness sysfs path set in the timelm.yaml file, but the brightness slider currently does not do anything. The flashlight toggle (which is also set in that timelm.yaml file) works as expected. I would appreciate any tips or suggestions for things to check. I am also including the line in the timelm.yaml file. DMESG output: [ 0.776921] 0.776921 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap:118] use dynamic brightness supported=0 [ 0.776926] 0.776926 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap blmap_size = 366 [ 0.776930] 0.776930 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap has been successfully parsed. [ 0.776934] 0.776934 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap-ve blmap_size = 366 [ 0.776939] 0.776939 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap-ve has been successfully parsed. [ 0.776943] 0.776943 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap-ex blmap_size = 256 [ 0.776947] 0.776947 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap-ex has been successfully parsed. [ 0.776952] 0.776952 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:73] can't find lge,dynamic-blmap-brighter [ 0.776956] 0.776956 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap-hdr blmap_size = 366 [ 0.776960] 0.776960 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap-hdr has been successfully parsed. [ 0.776965] 0.776965 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap-vr blmap_size = 2 [ 0.776969] 0.776969 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap-vr has been successfully parsed. [ 0.776973] 0.776973 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap-daylight blmap_size = 366 [ 0.776978] 0.776978 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap-daylight has been successfully parsed. [ 0.776982] 0.776982 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:77] lge,blmap-hdr-daylight blmap_size = 366 [ 0.776986] 0.776986 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_blmap_sub:89] lge,blmap-hdr-daylight has been successfully parsed. [ 0.776991] 0.776991 02-19 21:25:43.691] [7: swapper/0: 1] [Display][lge-backlight:lge_dsi_panel_parse_brightness:105] default brightness=158 [ 0.938750] 0.938750 02-19 21:25:43.851] [5: swapper/0: 1] [Display][lge-backlight:lge_brightness_create_sysfs:832] add irc_mode set node fail! [ 0.938889] 0.938889 02-19 21:25:43.851] [5: swapper/0: 1] [Display][lge-backlight:lge_brightness_create_sysfs:835] add irc_status set node fail! [ 7.752447] 7.752447 02-03 03:34:11.531] [6:systemd-backlig: 1589] [Display][lge-backlight:lge_backlight_device_update_status:287] BR:158 BL:558 lge,blmap [ 7.761243] 7.761243 02-03 03:34:11.539] [5:systemd-backlig: 1591] [Display][lge-backlight-ex:lge_backlight_ex_device_update_status:145] brightness=18, bl_lvl=99 -> differed (not allow) timelm.yaml file: BacklightSysfsPath: /sys/class/backlight/panel0-backlight directory listing: root@ubuntu-phablet:/sys/class# tree . ├── backlight │   ├── panel0-backlight -> ../../devices/platform/soc/ae00000.qcom,mdss_mdp/backlight/panel0-backlight │   └── panel0-backlight-ex -> ../../devices/platform/soc/ae00000.qcom,mdss_mdp/backlight/panel0-backlight-ex <snipped> ├── leds │   ├── blue -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d000/leds/blue │   ├── green -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d000/leds/green │   ├── hr_led1 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-03/c440000.qcom,spmi:qcom,pm8150b@3:qcom,leds@d000/leds/hr_led1 │   ├── hr_led2 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-03/c440000.qcom,spmi:qcom,pm8150b@3:qcom,leds@d000/leds/hr_led2 │   ├── led:flash_0 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:flash_0 │   ├── led:flash_1 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:flash_1 │   ├── led:switch_0 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:switch_0 │   ├── led:switch_2 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:switch_2 │   ├── led:switch_3 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:switch_3 │   ├── led:torch_0 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:torch_0 │   ├── led:torch_1 -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d300/leds/led:torch_1 │   └── red -> ../../devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-05/c440000.qcom,spmi:qcom,pm8150l@5:qcom,leds@d000/leds/red <snipped> I would appreciate any help even if it leads me nowhere, I did see that some SM8150 devices had this issue, the V60 is a SM8250 device and I think might suffer from the same issue as the 8150, the issues I read are still marked as open and have no activity for at least months (unless I missed something) Thanks for your time, and sorry for the long read.

  • Subforum for Meizu devices

    27 Topics
    180 Posts
    M
    @ubuntoutou Check here on this thread. Check this out on TWRP. You can use TWRP to access partitions. This can be helpful in data recovery or making a backup. I do fear that you have lost all due to using the installer.

  • Subforum for Oneplus devices

    374 Topics
    4k Posts
    I
    @Kamil Yes, I think this is what i am experiencing. Just tested Nord N100 and Pixel 3A on testufo.com. The 3A holds 60 fps pretty well while the N100 is constantly dropping from the mid 50s to as low as mid 20s.

  • Subforum for PINE64 devices

    67 Topics
    536 Posts
    LakotaubpL
    Not sure calls are working with UT on Pine devices anyway regardless of voLTE being enabled. Need to check on that.

  • Subforum for Samsung devices

    55 Topics
    343 Posts
    Mario.CHM
    Hi @Rondarius, Just tried it out and it works flawlessly. Thank you very much. Best regards Mario

  • Subforum for SHIFT devices

    4 Topics
    13 Posts
    S
    Hi, I am using Ubuntu Touch on Shift6mq. I like to swap between Wifi Data and Mobile Data. The Wifi Data usually gives me a list of Networks and which one is connected. However, turning off Wifi Data, then turning on Mobile Data; then access internet, then turn off Mobile Data; then Power off and Power back on: The Wifi Data is set on, but there is no list of Networks. Access to previously accessed Networks does not work. I have not found a way to reactivate the Wifi Network from this condition. Can anybody help? cheers, Steve D

  • Subforum for Sony devices

    94 Topics
    1k Posts
    D
    @kugiigi said in Feedback: Ridiculously Good Battery Life Since OTA-6: Back in the days with my bq E5, Noble on BQ E5 HD ? Good news !

  • Subforum for Volla devices

    167 Topics
    1k Posts
    AppLeeA
    Hi @jojumaxx said in Running Waydroid fails...: Do you mean this list? I sense that you're not talking about the same list. @arubislander was probably referring to this one: https://devices.ubuntu-touch.io/device/vidofnir/ The "waydroid" feature is shown as: Partial = Working to some extent but with issues Clicking on this link leads to the actual issue. And it's the same as the Quintus. https://gitlab.com/ubports/development/core/packaging/waydroid/-/issues/24 But wait, there's more; this issue is not really one, but instead it's a workaround made by Jami in order to setup waydroid on both devices (Volla X23 and Quintus)... And I hope that this is the answer you were looking for.

  • Subforum for Xiaomi devices

    292 Topics
    2k Posts
    U
    Miatoll has currently working VoLTE on devel channel, only thing you need it to switch channel and upgrade system, it should be working without any change on SIM 1 when enabled LTE (4G) network, not the other SIM 2 slot
Log in to post
Load new posts