[ROM] [ZTE Z7MAX] [Android 6.0] CM 13.0 unofficial

[PaoloW8]

Everything working much better in your new sources, thank you. After 3 months(since i used the OPO kernel sources for bluetooth) i got stuttering on bt playback again. It was an isolated incident and everything worked fine after a reboot, for more than 2 hours of playback(if i had to count, it happened once in a total of 30 hours of music playback). A took a look at the logcat while playing, and got an error about qcmediaplayer(music played fine, it just presented the error while changing tracks), and i remember that you commented it out in your rel v14 sources. Could it have some relevance to the issue?

I also use the OPO kernel bluetooth driver since relV13 but the bluetooth issue has never been solved, sometime it works sometime not (just as with Nubia kernel bluetooth driver)

[pchatzop]

I know, but sure we can agree that the opo driver and hci_qcomm_init blob got things much more stable. My question was more about qcmediaplayer, because i saw that error in logcat. It seems like the mediaprocess want to access it but we got it removed, so throws an error.

[PaoloW8]

I know, but sure we can agree that the opo driver and hci_qcomm_init blob got things much more stable. My question was more about qcmediaplayer, because i saw that error in logcat. It seems like the mediaprocess want to access it but we got it removed, so throws an error.

it is irrelevant

around on the internet I found to add this line to build.prop as possible fix:

ro.bluetooth.request.master=true

you have already tried ?

[pchatzop]

No way to test right now, but any possible fix is welcome . Problem is that the bug is so rare now, i could think it is fixed but and could still be there sometimes. Think that i used a2dp for 3-4 hours a week, and it happened 1st time yesterday for me since september 9th. Qcmediaplayer is truly irrelevant with bluetooth, error shows up even in normal music playing. Could you explain to me what it means? Still trying to learn about this proprietary qcmediaplayer process .

[PaoloW8]

No way to test right now, but any possible fix is welcome . Problem is that the bug is so rare now, i could think it is fixed but and could still be there sometimes. Think that i used a2dp for 3-4 hours a week, and it happened 1st time yesterday for me since september 9th. Qcmediaplayer is truly irrelevant with bluetooth, error shows up even in normal music playing. Could you explain to me what it means? Still trying to learn about this proprietary qcmediaplayer process .

I don't know exactly what qcmediaplayer is (maybe QualComm mediaplayer) but I saw that in cm14.1 has been completely removed from the source code and that in many cm13.0 device tree was removed months ago so is no longer needed

now I'm doing some test with the build.prop line added

[pchatzop]

Thought so as well, and i see that in the past lots of people have that showed up that error in their logcats when they could not play online videos with sound. Maybe Cyanogen replaced this proprietary service with the CMAudioService i saw since september. Maybe it has to do with redirecting audio streams to the hexagon dsp so they could be decoded, and the CM devs found a non-proprietary way to do this.

Hope the a2dp test goes well!

[PaoloW8]

Hope the a2dp test goes well!

no...same issue

[Caikki]

Hi paolo, thank you very much for keeping the development!! Can't wait for the Theme Engine on CM14! BTW, can you help me encrypt this device? Already used resize2fs for the free space for the crypto footer but still says "No master key, so not ext4enc" and "Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata" and "Not a valid ext4 superblock", help plz I can't leave home without cryptfs here

[PaoloW8]

Hi paolo, thank you very much for keeping the development!! Can't wait for the Theme Engine on CM14! BTW, can you help me encrypt this device? Already used resize2fs for the free space for the crypto footer but still says "No master key, so not ext4enc" and "Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata" and "Not a valid ext4 superblock", help plz I can't leave home without cryptfs here

I really never tried to encrypt the device and I don't know how it works.
I'll probably have make some changes to make it work on cm13 and cm14
I'm looking info on internet

[pchatzop]

I already added every needed crypto driver in my kernel fork for crypto from OPO kernel, it was required to get f2fs support. It could be an fstab issue, i will take a look. Sorry Caikki that i couldn't respond in xda, but i was busy trying to port cm to nx506j(only audio left to fix, damn tfa9890 audio amp) , and looking at the bluetooth issue.

Speaking of which, i replaced bin/btnvtool with the one from bacon blobs, and i am spending the last hour and a half trying to cause the a2dp bug(i have the phone connected to my computer via a2dp). No luck yet. I disconnected the computer side, the phone side, with wifi open, with data, no dice. The damn thing keeps working correctly. Logcat does not show anything abnormal. Link takes a while to close(about 10 secs) if i forcefully close bluetooth on the computer side, but shuts down correctly and music pauses on phone side. Maybe its worth a shot, try it yourself paolo, since i wasnt getting the bluetooth bug a lot to begin with(maybe my devices play well with the buggy driver ). Just replace the btnvtool blob with the one from bacon.