JooJooBee666

Already started that by the time you replied as I had a feeling it had to be something with that with all the changes from last night. Forced another sync just in case, rebuilt and installed, now it hangs on the linage boot animation, adb not connecting at this point either. Grrr...

I did a repo sync --force-sync before building today. In my roomservice.xml: <project name="tdm/android_device_fxtec_pro1" path="device/fxtec/pro1" remote="github" /> <project name="tdm/proprietary_vendor_fxtec" path="vendor/fxtec" remote="github" /> <project name="tdm/android_kernel_fxtec_msm8998" path="kernel/fxtec/msm8998" remote="github" /> Maybe it's possible that the rebuild didn't clean old framework_manifest.xml out and deleting the system and vendor folder in out before rebuilding again would resolve?

@tdm Synced, rebuilt and installed again. However, after the first sleep/screen off it would not come back on. After another reboot, I'm now stuck at "Phone is starting....". I've attached a logcat from the second boot. I'm currently reinstalling the build from yesterday for now....or so I thought. Apparently, I cannot downgrade as Lineage Recovery sees it has an older timestamp and wont let me. I'm going to manually flash the system and vendor images from bootloader now. Update: that's not working either, I can't get a good looking vendor.img extracted from the payload.bin. Revert

Figures. Resyncing and rebuilding. Update: Confirmed. Looks like the only commit i didn't have was the "Switch to standard livedisplay implementation" in the device tree.

@tdm built and installed. I'll let you know if I see anything amiss and get some avc logs over.

Yeah, that's what I was originally asking, sorry I wasn't very clear on that. But I believe I have it figured out. 🙂

[[device/fxtec/pro1/lineage_pro1.mk]]: "vendor/fxtec/pro1/pro1-vendor.mk" does not exist. I'm going to update my roomservice to move the vendor three to that location. It's currently pointing to vendor/idealte/pro1/ Ahh, I see. New vendor repo.

@tdmAre you finished rebasing? If so, do I need to update my roomservice? Right now, it's completely broken for me.

@tdm Are you going to push the changes to the repos any time soon? I'd like to test here but build my own.

New issue filed on GitHub with attached log. The following line seems suspect: 03-13 13:26:09.895 2843 2843 I FingerprintController: fp wakelock: TIMEOUT!! Obviously the full log may be more helpful. Let me know if you need more.

Ok, thanks. I'll start digging around.

@tdm Just an update on the fingerprint changes: It's mostly not working for me since the most recent changes last week. I cannot figure out what the pattern is as to when ot works or doesn't, but usually nothing happens at all; no vibrate, no notification...just nothing. I find I have to use the screen unlock pattern 70% of the time. Were you aware of these issues and seeing the same thing or should I start gathering some logs files?

@tdm I've done that on mine. All the apps I normally have an issue with are working with this fix as well. I'll let you know if it holds. I didn't even notice that there was a second audio_policy_configuration.xml in that folder there. Definitely confusing.

Ahh, interesting. Well to answer your question: Disable Magisk hide and reboot. Connect to adb via adb shell Elevate to root mount -o rw,remount /vendor exit out of ADB and get back to prompt, then run adb root ADB pull the files to the pc, edit them and adb push them back Reboot device. Sidenote: I believe this will break the signature so make sure you disable ABV. Someone correct me if I'm wrong, please.

@tdm Finally had some success with the audio. Since the problem appears only when deep buffering is being used, disabling it from the audio config policy seems to resolve it. Here's the changes: diff --git a/audio/audio_output_policy.conf b/audio/audio_output_policy.conf index 4719b66..eb932be 100644 --- a/audio/audio_output_policy.conf +++ b/audio/audio_output_policy.conf @@ -26,7 +26,7 @@ outputs { app_type 69943 } deep_buffer { - flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER + flags AUDIO_OUTPUT_FLAG_NONE formats AUDIO_FORMAT_PCM_16_BIT sampling_rates 48000 bit_w

Oh, and I found another hack to temporarily fix the audio...receive a text message. Or send one to yourself and QUICKLY go back in to the app with the problem. No need for a plug now. 🙂 Clearly this has nothing to do with power. I see this in the logs: audio_hw_primary: start_output_stream: enter: stream(0xe6d71000)usecase(1: low-latency-playback) devices(0x2) and other various things surrounding this. Where as when I start apps that have the issue, I don't see this. So this leads me to think it is indeed related to buffering. Though my attempts to adjust different buffer settin

I'd say fixing this stupid crackling/echo audio problem...still no joy here trying to resolve. If you want to reproduce, there are certain apps that ALWAYS do it. For example - Fishdom. But my experience so far is that most games do this. Even RetroArch emulator.

Started working again for me later in the day. The fingerprint reader stopped working at all for a short while but shortly after I noticed that I tried it again and it was working once more along with the vibrate.

I was just able to successfully install OpenGapps today. Been a couple of weeks since I last tried so something obviously changed to fix this issue. Let's see if I have less crashes now.

For me it just fails. I haven't been successful installing but there was no disaster after failing. I just installed MindTheGapps after the failures and all was well (as well as it has been for GApps, the play services periodically crash on me).

I would be one of those. If I don't reinstall GApps, I just get not stop errors from the apps crashing.

That's up to you. Just make sure you activate the correct one afterward. GApps does need reflashed and you may also have to uninstall then reinstall some of the Google apps.

@tdm vibrator seems to work for calls and other stuff but I notice it no longer virbrates when reading the fingerprint (successful or not).

@tdm Thanks for the update. Building now. 😎

I tried a few things today, but no luck. HOWEVER, I did find something interesting and it also explains why I thought it was fixed. If there is crackling audio, simply plug in or unplug the usb, then it stops until the app shutdowns or phone goes to sleep again. I'm not sure whether or not it because another sound is being played when that occurs or if something else is somehow being triggered. I grabbed some adb logs of it occurring but haven't narrowed it down to anything yet.