JooJooBee666

@tdm here's more filtered log errors when audio is crackling E ACDB-LOADER: Error: ACDB get asm topology returned = -8 E ACDB-LOADER: Error: ACDB_CMD_GET_AUDPROC_COMMON_TABLE_SIZE Returned = -19 E ACDB-LOADER: Error: ACDB audproc returned = -19 E qcbassboost: [vendor/qcom/proprietary/mm-audio-noship/audio-effects/safx/android-adapter/qcbassboost/qcbassboost.c:536] Assertion fail: pConfig->inputCfg.format == AUDIO_FORMAT_PCM_16_BIT Same error I saw before...but they're back. I'll try to find some time to play around with the buffers today and let you know if I find anything.

Spoke too soon....somehow it came back later in the day and even back after a reboot. How was it gone earlier?

@tdm fyi, the a2dp commit also fixed the crackling audio problem. Makes sense as one of the things I noted when the issues was occurring was an error stating "AUDIO_FORMAT_PCM_16_BIT" was an invalid format. Bad-ass.😎

Working well here. Thanks again.👌

@tdm awesome.😎

Ok, thanks. 👍 FYI, I dont care about it either. Never listen to radio anywhere, anytime, any longer.

@tdm Just curious about this, but how are you building successfully from your device tree repo with the FMRadio package enabled? I have to remove it to allow the build to complete.

Ahh, ok. I was thinking most of it was being handled in the kernel. Thanks for clarifying.

@tdm Just a thought on fixing the unwanted finger print read issues. I think most of the issues are due to accidental quick brushes with the sensor. Would it be possible to add a delay so that when it senses a touch, it doesn't send a read to the OS unless the touch remains active for a certain period of time, say 500ms?

@Polaris If the LED's in that app don't work, it also has an option to use the camera flash. Maybe overkill but maybe a better option for you than nothing if it works?

I use this app. It sends audible alerts. The notification LED is useless to me. I never look at my phone unless I need it for something so an audible notification works best for me. NEVER used the LED in all my years. It does allow control of the LED as well but I've never tried it.

@tdm My top issues are: 1. Fingerprint 2. Dead Zone 3. TWRP (would LOVE some userdata backup as right now I feel like I'm going all cowboy)

Good to hear. FYI, no issues with audio yet. Been using it for 7 hours so far. I've never had it stay up that long without issues using the LOS built vendor image.

This is a known issue. See this for some work arounds.

Hmm, ok. I didn't dig in to what the property does. Just comparing the build.prop (and the libs) from the stock vendor image but I guess that doesn't mean FxTec left some unneeded cruft in there. Anyhow, I'm going to test out an updated vendor image today. I'll let you know how it goes.👍

@tdm Sure. Looks like it was just one line: persist.vendor.bt.a2dp_offload_cap=sbc-aptx-aptxhd-aac

@tdm The items I was just referring to were a line or 2 in the build.prop file. Also, looking at the file comparison, I noted a few additional audio libraries in the lib64 that are not present in the latest update to the vendor files (libaudioalso.so, libaoa.so and libaudio_log_utils.so). I'm guessing those are not necessary? Anyhow, I'll compile an updated vendor.img tomorrow with the changes you pushed and see how it goes.

@tdm Thanks. I noticed some missing libs as well but none seemed connected to audio (I don't know what they do exactly) so I didn't bother with those. I also noticed some of the missing a2dp items as well but don't use BlueTooth so didn't bother. I can test today if you push to the repos soon but I gotta have everything working again in the next 5 hours as I have to be out and about this evening.

@tdm Still haven't found anything. Tried swapping a bunch of different values from the props on the older vendor image to the newer one and some of the blobs (most are identical as you noted). But due to the length of time it takes to see if the changes helped (a few hours typically before the $**T hits the fan) I finally gave up for now. I instead mounted the older vendor img, fixed the fstab for the userdata encryption, added in the new lights HAL, keyboard layouts and framework overlay, flashed that and confirmed everything is happy again so I can reliably use my device for a few days.

@tdm fair enough. I'll let you know if I find anything of interest.😎

@tdm ok, thanks. I'm really not sure what to do with the backtrace here as there is so little information. I can't use addr2line to trace it back to anything as it abruptly ends on <unknown>. The only thing I was planning on attempting was just replacing all the audio libraries from the last known working vendor.img I have and seeing if that helped, unless you can confirm these have NOT changed since McCreary's manually created vendor imgs?

TDM, I flashed a new ROM (self built) from your repos today to test latest vendor blobs. I figured I'd give them a go. Audio services are still a train-wreck. Randomly stops working, then reboots. During this time, you don't know its not working but any phone calls, texts and alarms are missed. Same as before. This is a show-stopper. However, I can no longer use the older images from McCreary as they cause Lineage to not boot (stuck on boot animation). Anything I can do to get it booting with the older vendor images again? I already ensured AVB was disabled. Also, I cannot down grade

I've been working on an app to restore the backlight functionality on LineageOS builds (It will NOT work on stock). It's called KB Backlight Manager. It runs as a foreground service to monitor the system for the slider events and turns the backlight on or off depending on it's state. It also includes a QuickSettings tile so you can easily turn it on or off from there and an option to disable the backlight completely as well as an option to enable/disable the QuickSetting tile. You can get the latest builds over on the Github page for it here: https://github.com/JooJooBee666/KB_Backlight

I'd definitely prefer not to have it as well. I don't care about bling one bit. I just want functionality. Curved screens reduce that as well as making it impossible to protect 100%. Maybe the next model won't have this? Either way, it's a compromise that I'm willing to live with for a nice QWERTY once again (with headphone jack).