ngoquang2708 / android_device_samsung_vivalto3gvn

Device tree for Samsung Galaxy V SM-G313HZ
7 stars 8 forks source link

cm-12.1: Audio FX has no effect #14

Closed ngoquang2708 closed 8 years ago

ngoquang2708 commented 8 years ago

NuPlayer again.

ngoquang2708 commented 8 years ago

Everything will be working normally when switch to AwesomePlayer in DevSettings.

diepquynh commented 8 years ago

Did your phone freezes when pressing volume buttons?

diepquynh commented 8 years ago

Not exactly freezes, but Trebuchet freezes, and after a couple of minutes, it soft-reboot

ngoquang2708 commented 8 years ago

It is working normally.

diepquynh commented 8 years ago

After turning to AwesomePlayer?

ngoquang2708 commented 8 years ago

Both NP and AP.

ngoquang2708 commented 8 years ago

Any logcat?

diepquynh commented 8 years ago

I can't get it now, but it shows that "service media.audio_flinger died" then soft-reboot Pressing volume buttons makes Trebuchet freezes. Audio settings in Settings does the same thing, can't change audio volume

diepquynh commented 8 years ago

Btw, can i try your build?

ngoquang2708 commented 8 years ago

I am building it currently with major bug fix with libatchannel which fix audio routing to ext speaker when incall. you can try my old build cm-12.1-20160226-UNOFFICIAL-vivalto3gvn.zip

ngoquang2708 commented 8 years ago

About crashing mediaserver, I didn't remember exactly, when change it user to root instead of media in init.rc, crashing is gone. Our audio HAL require more privilege than standard one.

ngoquang2708 commented 8 years ago

May be system user should be enough but I haven't tried it.

diepquynh commented 8 years ago

We need that on CM12.1. Stock APM in CM11 makes UI audio very quiet, but media or ringtone works fine

ngoquang2708 commented 8 years ago

OK, I remember it now. I removed nvram ccci groups plus set user to root and mediaserver audio service stop crashing.

ngoquang2708 commented 8 years ago

I don't know why but audio in cm12 is perfectly, not very loud like in cm11, no audio blobs here.

ngoquang2708 commented 8 years ago

@koquantam I remembered that your cm12.1 build has both sim work, right?

diepquynh commented 8 years ago

Only calls, SMS. Mobile data works only for one SIM

ngoquang2708 commented 8 years ago

But you could see 2 network signals?

diepquynh commented 8 years ago

Yes and 2 exclamation marks on both SIMs, which means no mobile data for almost all of the time. If enabling mobile while in dual-SIM mode, that chosen SIM RIL would crash

ngoquang2708 commented 8 years ago

@koquantam Oh god, at least dual-SIM work for you, never work for me. When I enable dsds, both network signal is gone but 1st SIM is usable. Could you try to flash my new build to see if dsds work (please re-enable it from build.prop).

@Y300-0100 If you cannot wait, try this.

Here is it: cm-12.1-20160228-UNOFFICIAL-vivalto3gvn.zip

diepquynh commented 8 years ago

@ngoquang2708 vivalto3gvn build cannot work on kanas, as they had different hardware

ngoquang2708 commented 8 years ago

I though he had galaxy v.

diepquynh commented 8 years ago

He has mentioned that he was working for G355HN, Galaxy Core 2 with NFC

diepquynh commented 8 years ago

Did you integrated libmemoryheapion?

ngoquang2708 commented 8 years ago

Not yet. Using LD_PRELOAD is just a hack, much like we are hacking libbinder right now. If we can make camera codes to work, then we can use libmemoryheapion without LD_PRELOAD hacking and libbinder hacking too.

diepquynh commented 8 years ago

Bro, not just camera relies on ION. Anything on HW needs ION too, so just make it temporary hack instead. People want a lollipop build instead of a bugless build

ngoquang2708 commented 8 years ago

Of course, when camera source codes work, we can change hwc source code or any other source code to use libmemoryheapion!

ngoquang2708 commented 8 years ago

And the current hack on libbinder is working, bro!

diepquynh commented 8 years ago

Yes, it's working Dual-SIM seems broken. Could you try removing RIL CFLAGS? More weird is: SIM1 can call, but SIM2 can't. Starting to have some headaches

ngoquang2708 commented 8 years ago

You said Dual-SIM is broken, so SIM2 supported to not work?!?!?

diepquynh commented 8 years ago

"supposed" , not "supported" dude Yes, i've some typos :D

ngoquang2708 commented 8 years ago

Yes, my grammar it not good. Thanks for pointing it out any way :D