I tried this patch on the Galaxy Note 4, works very well, even with flash, video however doesnt play back but I believe that is a mediahub or contenthub issue. I wanted to ask if there was a plan to get this merged into the halium repos or do we have to merge this patch intou our specific device repos? if we have to merge it to our device, what would be the best way to do so?

@Flohack my device has this:

https://github.com/tyg3rpro/android_device_samsung_trlte-common/blob/cm-14.1/audio/mixer_paths.xml

https://github.com/tyg3rpro/android_device_samsung_trlte-common/blob/cm-14.1/configs/media_codecs.xml

I dont seem to have acdbdata in my repo

@Flohack the wifi connects fine once the device is booted, and it reconnects when it scans and finds the wifi it was connected to before reboot, but as soon as I reboot, it doesnt reconnect. For my port I dont think I need any extra modules but I dont know if thats how other ports have gone. I honestly think a good chunk of my issues might be D-Bus related

Edit:
My port does have wpa_supplicant working and what not, if a device is having an issue with wifi connecting or enabling, I would think that be a good place to check

@dobey i understand that, and thats not a blocker, sorry if that wasnt clear, the recovery not working correctly is the major blocker atm, I tried adding the repos from Alfreds github, but it doesnt work for me, after that I have to find a scriptable way to install it (heimdall doesnt work for me and fastboot is not an option)

Edit:
I feel like this is focusing primarily on my port which is not what I was hoping to accomplish, I was hoping to have some solutions for the misc. Issues facing most of the near completed ports like in call audio not working or apps not working correctly (no sound/unable to queue files in music app)

@wdehoog the events that arent being handled by unity/mir are all stylus/wacom related events (i.e. I pull stylus out, tap icon on the screen, put stylus back) dmesg will show the events for the given example, but nothing happens GUI side. I havent saved any full logs from dmesg yet but I will get some when I have a chance, did you have anything in particular you wanted me to get?

So my Galaxy Note 4 port has come a long way with help from other community members, I can confidently say it would be ready for a daily device if I didn't have these last little bits that, while aren't important to UT use, are annoyances that I know I've seen a solution for before but can no longer find. I have managed to get everything but the sensors and the stylus to work on my device, the sensors show up with "test_sensors" and the stylus works with libinput but mir or unity do not handle those events yet, I tried to look into the code for mir, but it goes over my head honestly as I am not a coder. I know Marius has briefly talked about sensorfw for sensors coming down the pipeline (which I'd love to test and give feedback) but for now, I accept that both those things are beyond my capabilities so I will just have to wait till I can get there or till the code gets there on its own. I have yet to get a working recovery with my source, and to be honest, I haven't really played with it in a while. Now for the annoyances I know I've seen a solution for (whether it was for ubports 5.1 or another version), the list overall I think is manageable, but here it goes:

WiFi doesnt re-connect after a reboot

BT sometimes crashes device

Camera loads the viewfinder, sometimes takes a picture or two, and ultimately crashes the whole device

On CDMA networks (Sprint and Verizon) I have to downgrade ofono to get a cellular signal (not UT's fault as most of the world has moved on from CDMA and EVdO)

Charge indicator only works if device is plugged in to charger on boot

Audio works for everything that isn't Youtube, or sound from a app that stores sounds locally (D-Bus error)

I started this post in hopes of being able to have a centralized location for all the ports facing these issues, and possibly have a healthy discussion about things like D-Bus errors and how to fix them as there is not much info for D-Bus in regards to Ubuntu Touch. I know dbus-monitor works (how I found out I have a D-Bus error with localized audio vs audio from the web)

I also welcome constructive criticism as long as it remains respectful and family friendly.

I do apologize to mods if this is in wrong spot or anything of the like.

I look forward to the healthy discussion and hopefully solutions to some of the lesser known issues

@rinigus I am always willing to help, when it comes to app development Im best classified as a noob, I can compile code though. I am willing to help implement features if theres someone that can help/guide me through the process.

Hello rinigus, first and foremost, thank you for porting a great app to Ubuntu Touch, I was just curious if there's any plans to add an option of trucks/lorries to the navigation options (like car, bus, train, ...) I have been driving a truck/lorry (not sure what you call them, they are trucks to me) for work and pure maps has worked out well, but there are a few routes its wanted me to go that I can't take the truck on. I would also like to take this moment to ask if you need volunteers for testing, I have Pure Maps working on my Galaxy Note 4 port of Ubuntu Touch and would love to help out, I lack knowledge on app programming though

@mh4it with CDMA the network wont work out of the box on UT, in order to get CDMA working (Sprint/Verizon) service you have to change ofono on the running system, then modify APNs, and even after all that there is no guarantee they will be able to send/receive SMS/MMS messages, my advice would be to set the device up as a mini tablet with no cellular service to allow experience of UT, and a GSM service if they wanna try it

Is there any progress with sensorfw, and if not are there any plans to implement sensors that dont use the sensors.qcom but something else, like for example sensorhub?