Port Finishing Touches

[tigerpro]

@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?

[wdehoog]

@tigerpro lets start by logging all output from evtest on the device that responds to the stylus activity.

and for dbus just start dbus-monitor and listen for everything. once on the system and once on the session bus.

(use a pastebin like service)

[dobey]

@tigerpro said in Port Finishing Touches:

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

Don't block getting the build showing up in the installer, on working stylus. It is not a trivial fix, and will require a lot of changes in multiple parts of the system to make work, because these aren't touch events, but drawing tablet events.

[tigerpro]

@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)

[flohack]

@tigerpro Is the WiFi problem due to a module not being loaded, do you know whats missing? How do you get it working?

[tigerpro]

@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]

@tigerpro said in Port Finishing Touches:

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)

I suppose it would help if there were links to bug reports for these issues, specifically to comments on the issues where logs are attached that show these supposed D-Bus errors.

[flohack]

@tigerpro Music issues can also be caused through missing sound configs from Android. Can you check your device tree for mixer_paths.xml, acdbdata directories, and mediacodecs.xml?

[tigerpro]

@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]

@tigerpro Ok try to copy both to /etc (UT container) for the time being and see if this changes things

[flohack]

Also I started this document now: https://pad.ubports.com/p/PortChecklist - feel free to contribute!

BR