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.

@mariogrip is there a way I can start working on porting my device to it if it's not in the installer?

@DJac sadly this is not the same device, this is for the 8.4" Samsung Galaxy Tab S LTE, why they have it the way they do is very misleading and it really messes with search results for the Galaxy Tab S8

@MrT10001 sorry to dig up an old thread, but if you 2 are still around, I have a S8 Ultra as well that I have started to port, it's very early stages but I'm sure we can collaborate and get Ubuntu Touch running on this device, I also have the Tab S8 and Tab S8+ in case anyone else with those devices happens soon this thread.

@Inali this is what I keep getting after I do a apt update then try to install

root@ubuntu-phablet:/android/vendor/lib64/hw# apt install ofono-binder-plugin-qti
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ofono-binder-plugin-qti
root@ubuntu-phablet:/android/vendor/lib64/hw#

EDIT:

I just figured it out, the package is ofono-binder-plugin-ext-qti Ill test it now

@mariogrip I copied the configs from the FP5 gitlab from about 24 hours ago and that got LTE working, when I tried calling the cell icon didnt show it dropped out of LTE, to install ofono-binder-plugin-qti is there a link or something to install it? Im bit rusty on some of this.

edit: I tried to install with apt as I saw you mention that in another post but it gave me an error saying it couldnt find ofono-binder-plugin-qti

On another note, glad to have ya back, missed ya

@mariogrip I am willing to try it with a port I'm currently working on, however I dont know if the cellular data is working correctly atm.

@m4l490n honestly I haven't had time to even touch the code in a year. There is documentation for making a port, just search for "ubports porting guide" and you will be able to find it. I happily accept any code contributions as long as they don't break the port.

@carlo afaik that command should work, granted my knowledge is mostly LOS 14.1 based porting on a Galaxy Note 4, if that command is not working, double check the documentation your following is for the correct version of your LOS source, as well as your source is complete and not lacking anything.

it is possible to run desktop apps in UT, I know this because I have done it, however the experience was unusable due to the apps not responding to any input/interaction attempts through either touch or KB/M use. it is also pretty involved to setup and will not survibe any OTAs, overall if your looking to run regular linux apps on a handheld device, UT is not going to be the solution you want for that.

@sringgen as stated VoLTE is being worked on for ofono, the other side of the token is that Verizon uses CDMA and afaik CDMA does not currently work correctly, if at all, so there is also that.

@unisuperbox is there anything stopping us from using OTA-16.x system? I understand the thought process behind the idea, however, if we are to switch to a system like this, maybe have it as OTA-x.16 to indicate which OTA it is and the LTS version after that? I feel that would allow easier distinction between the OTAs and not pose a potential issue with the current OTA system as it would work to make it think its a major version change, with the same minor version, just my $0.02

@flohack so if Im understanding correctly, the android side sees /android as /? if that is the case then how would I massage the lxc container to get the blobs to see the efs partition?

@doniks thats actually what made me think to check it, the difference is for my device efs is mounted and I can access it, but its mounted at /android/efs rather than /efs hence me asking if anyone knows if that matters, or how to fix it

so I found myself with about an hour of free time over the past couple days and decided to check into the wifi not re-connecting properly after a reboot, I suspect it is related to efs, I was able to verify it is mounted, but I have a suspicion its not mounted in the correct location, so that leads me to this question, is there a better way to force the correct location rather than putting a bind mount in init? Im not sure what else this will fix, or even if it will fix anything, but its a start since android mounts efs to /efs, and UT is mounting it to /android/efs, I suspect the stuff that is working is not fully working due to that.

Thanks for for your time.

@kyrylo welcome, however I would not advise getting a galaxy note 4 as my port is very incomplete, its missing call audio and has a few other issues I need to address, but I lack the time to do so

@kyrylo on my Galaxy Note 4 I can watch a full length movie from SD in a mp4 format, it takes a few minutes for it to load, but it does play and keeps the sync for about 90% of the video

@mastersezer what do you mean by changing charge?

@squigly as a Volla phone owner, I can say hardware wise, they are close enough to run the same software as GS290, I know this from installing /e/ on my Volla, as far as going the other way and running UT on a GS290, its 100% possible, but as mentioned, the path to do it is not recommended (or the faint of heart), I have probably bricked my Volla more times han most people will trying to install ROMs so I have some good practice in so far