Database Develop

[DEV-only][WIP] ALSA BCM21553 Audio libs built from source - BroadcomCM

I've created this thread to join developers into the final audio fix for android 2.3.7. Although the prupose of this thread is to fix Audio on Android 4.0.4 we first need audio drivers source.
On all our based Android 2.3.7 ROMs we fixed audio using some AOSP Alcatel .so files (to remove Samsung lib dependency) and some Samsung .so libraries too, this is the whole list:
# Samsung audio libs
acoustics.default.so
alsa.default.so
libaudiopolicy.so
# Alcatel audio libs
libaudio.so
libaudioflinger.so
libaudioeffect_jni.so
libmediaplayerservice.so
Click to expand...
Click to collapse
Our device uses ALSA audio system, which is also used on stock ROM. This is related to software more than hardware, although we are not planning at the momnt to "change" this audio way. To activate ALSA audio some changes need to be done on kernel, that samsung provide to us on their kernel sources. Mostly we need to enable ALSA on device .config file:
Code:
CONFIG_BRCM_SOUND_ALSA=y
CONFIG_BRCM_SOUND_ATHENA_ALSA=y
That's not an issue as prebuilt alsa libs work, so new libs should work too. Ramdisk needs some edit too, as ALSA audio system is stored on dev/snd, and this is well defined too on our ramdisk, ueventd.rc
Code:
/dev/snd/* 0660 system audio
We realised after that that actually CyanogenMod 7.2 Sources include ALSA lib sources, what we didn't know if those sources could work with our devices. This sources build the following libs, as releated to its Android.mk files:
We can found inside hardware/sound_alsa the following sources to build
libaudio
libaudioflinguer
hw/alsa.default
hw/acoustics.default
On external/alsa-lib we can found the sources of anoher lib
libasound
And apart from that, some other audio libs such as libaudiopolicy are built inside framework/base repository, but they doesn't make any conflict. Other libs are included on Android source files.
To enable the build of those libs, using ALSA software instead af "Android default (not sure about that)". I've enabled on Boardconfig.mk the following configs:
Code:
# Audio
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_ALSA_AUDIO := true
BOARD_PREBUILT_LIBAUDIO := false # even not writted.
BUILD_WITH_ALSA_UTILS := true
This configs enable the building of those libs on their Android.mk files.
Also, I've added on device_cooperve.mk the following lines to build those hw modules releated to audio:
Code:
# Audio
PRODUCT_PACKAGES += \
alsa.default \
acoustics.default
After the build finished, and fixed some errors, AUDIO WAS WORKING, but not as expected. There were issues on Audio Routing:
Headphones are detected through system, but audio is not reproduced on headphones (speakers does)
When you make a call, sometimes you can't and phone freezes, or when you hangout the call, phone freezes.
Everything else apart from that seems to be working, even microphone, although this bugs are pretty weird, I took a look to logcat.
Code:
[COLOR="Gray"]D/AndroidRuntime( 1419): CheckJNI is OFF
I/ ( 1420): ServiceManager: 0xad50[/COLOR]
[COLOR="Red"]E/ALSALib ( 1420): external/alsa-lib/src/control/control.c:882:(snd_ctl_open_noupdate) Invalid CTL AndroidOut[/COLOR]
W/AudioHardwareALSA( 1420): Unable to attach mixer to device AndroidOut: No such file or directory
[COLOR="Red"]E/ALSALib ( 1420): external/alsa-lib/src/control/control.c:882:(snd_ctl_open_noupdate) Invalid CTL AndroidIn[/COLOR]
W/AudioHardwareALSA( 1420): Unable to attach mixer to device AndroidIn: No such file or directory
D/AudioHardwareALSA( 1420): openOutputStream called for devices: 0x00000002
D/ALSAModule( 1420): open called for devices 00000002 in mode 0...
I/ALSAModule( 1420): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/AudioHardwareALSA( 1420): buffer size (bytes) to AF = 16384
D/AudioFlinger( 1420): setParameters(): io 1, keyvalue routing=2, tid 1593, calling tid 1420
I/AudioFlinger( 1420): AudioFlinger's thread 0x1d978 ready to run
D/ALSAModule( 1420): route called for devices 00000002 in mode 0...
I managed to fix those errors (E/) by moddifying asound.conf, found on system/etc, adding this lines on the top and deleting old ones:
Code:
ctl.AndroidOut {
type hw
card 0 # Can replace with drivers name from /proc/asound/cards
}
ctl.AndroidIn {
type hw
card 0
}
Now logcat shows this at the moment
Code:
[COLOR="Gray"]D/AndroidRuntime( 1425): CheckJNI is OFF
I/ ( 1426): ServiceManager: 0xad50[/COLOR]
D/AudioHardwareALSA( 1426): openOutputStream called for devices: 0x00000002
D/ALSAModule( 1426): open called for devices 00000002 in mode 0...
I/ALSAModule( 1426): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_normal
I/AudioHardwareALSA( 1426): buffer size (bytes) to AF = 16384
D/AudioFlinger( 1426): setParameters(): io 1, keyvalue routing=2, tid 1604, calling tid 1426
I/AudioFlinger( 1426): AudioFlinger's thread 0x1d960 ready to run
D/ALSAModule( 1426): route called for devices 00000002 in mode 0...
Actually that's the actual logcat, using headphones, and sound goes through speakers:
Code:
D/dalvikvm( 1926): GC_EXTERNAL_ALLOC freed 324K, 49% free 3317K/6471K, external 571K/579K, paused 58ms
V/HeadsetObserver( 1607): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=2, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=1335, ACTION=change, SWITCH_NAME=h2w}
W/Vold ( 1415): Ignoring unknown switch 'h2w'
V/HeadsetObserver( 1607): Intent.ACTION_HEADSET_PLUG: state: 1 name: h2w mic: 0
I/HeadsetService( 1907): Headset plugged: true
I/Effect-DRC( 2115): Compression factor set to: 1.000000
I/Effect-BassBoost( 2115): New strength: 0
D/SurfaceFlinger( 1607): Layer[1c62e0] [2] non-RGB565 reloads
I/Effect-Equalizer( 2115): Setting band 2 to 0
I/Effect-Equalizer( 2115): Setting band 2 to 1
I/Effect-Equalizer( 2115): Setting band 2 to 2
I/Effect-Equalizer( 2115): Setting band 2 to 3
I/Effect-Equalizer( 2115): Setting band 2 to 4
I/Effect-Equalizer( 2115): Setting loudness correction reference to 100.000000 dB
D/AudioFlinger( 2115): setParameters(): io 1, keyvalue routing=8, tid 2117, calling tid 2115
D/ALSAModule( 2115): route called for devices 00000008 in mode 0...
D/ALSAModule( 2115): open called for devices 00000008 in mode 0...
I/ALSAModule( 2115): Initialized ALSA PLAYBACK device AndroidPlayback
D/dalvikvm( 1926): GC_EXTERNAL_ALLOC freed 323K, 49% free 3327K/6471K, external 571K/579K, paused 44ms
We must take a look if that is kernel relevant or not, as we really need this libs to work, to then start working on CyanogenMod 9.1 / Android 4.0.4 audio. Any suggestions are welcomed, although if they are from newbie or developer, don't want this thread to be spammed as others

Why this is helpfull ?
Currently we based it upon cm7.2 GB
this is because our device uses to run GB as stock.
When we figure the sources out and figure out what is part 1 or such we can adapt and try to port to CM9 so in that we can have new libs aswell.
(W.I.P Post;P )

to me

Sorry for intrusion Biel and spacecaker But can i have the output of cat /proc/asound/cards ???

4dead said:
Sorry for intrusion Biel and spacecaker But can i have the output of cat /proc/asound/cards ???
Click to expand...
Click to collapse
Sure, here it is:
Code:
# cat /proc/asound/cards
0 [ALSA ]: Broadcom - Broadcom ALSA
Broadcom ALSA PCM 0

I can help
bieltv.3 said:
Sure, here it is:
Code:
# cat /proc/asound/cards
0 [ALSA ]: Broadcom - Broadcom ALSA
Broadcom ALSA PCM 0
Click to expand...
Click to collapse
give me any link - any guide i got linux want to help i will do my best

at myaser
for this
there are no guides.
Sent from my S500 using xda app-developers app

SpaceCaker said:
at myaser
for this
there are no guides.
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
I will try using my mind
Sorry for non-useful comments

u need tiny alsa not alsa sources to work with bcm21553 modules , Android 4.0.4 introduced tiny alsa replacing alsa

percy_g2 said:
u need tiny alsa not alsa sources to work with bcm21553 modules , Android 4.0.4 introduced tiny alsa replacing alsa
Click to expand...
Click to collapse
We are fixing on 2.3.7 at the moment. Tinyalsa gives support for msm8960 chips as I can see on their sources, so we should start from 2.3.7.
Enviado desde mi C5303 mediante Tapatalk

The sound will work after 3 months?
The sound will work after 3 months?

bieltv.3 said:
We are fixing on 2.3.7 at the moment. Tinyalsa gives support for msm8960 chips as I can see on their sources, so we should start from 2.3.7.
Enviado desde mi C5303 mediante Tapatalk
Click to expand...
Click to collapse
What about CyanMobile eXperience Biel ??
Are you will starting the build ??

@bieltv.3
Look At ur inbox

jeko99 said:
The sound will work after 3 months?
Click to expand...
Click to collapse
Maybe... Be patient bro, it's so hard to fixing audio issue

jeko99 said:
The sound will work after 3 months?
Click to expand...
Click to collapse
No ETA's, please.
Can't you see that this thread is a Dev thread? No discussion here, please.
Enviado de meu XT1032 usando Tapatalk

I think you should really take a look on the stock asound.conf

4dead said:
I think you should really take a look on the stock asound.conf
Click to expand...
Click to collapse
We are using stock asound.conf
Enviado desde mi C5303 mediante Tapatalk

Are the drivers initialized in the kernel?
check here ---> http://seasonofcode.com/posts/using-alsa-audio-drivers-in-android.html
and here ----> http://code.paulk.fr/article3/tinyalsa-audio

faZevoLv said:
Are the drivers initialized in the kernel?
check here ---> http://seasonofcode.com/posts/using-alsa-audio-drivers-in-android.html
and here ----> http://code.paulk.fr/article3/tinyalsa-audio
Click to expand...
Click to collapse
Biel already said in the op that he added /dev/snd in the Ramdisk and i dont think our device use tinyalsa because With Alsa Drivers biel got sound working.

No Way To Use Audio files from other devices
Not booting at all
BroadcomCM Team \o/
Good luck It seems to be hard

[FIX] Voice messages

First of all, thank user @Bobgle for the fix. He killed the fish with that, so big kudos.
I just had to add a little line of code to the /system/etc/media_profiles.xml. I know it's not your rom which has the problem, I'll tell the other developer how to fix it as well. I first found out that it was a common problem through your NOPE Kernel FAQ, though, so it's definitely worth adding.
This is the line of code:
Code:
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
Has to go right between these two and should look like this:
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="8000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
<AudioEncoderCap name="amrnb" enabled="true"
minBitRate="5525" maxBitRate="12200"
minSampleRate="8000" maxSampleRate="8000"
minChannels="1" maxChannels="1" />
Once you've done that it's working. I also replaced this line in the media_codecs.xml:
Code:
<MediaCodec name="AACEncoder" type="audio/mp4a-latm" />
with:
Code:
<MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm" />
I'm not sure if that was necessary. Anyway, it's working.
Click to expand...
Click to collapse
I've put his message in the spoiler. I'll put it simply below, hopefully correctly.
-Open /system/etc/media_profiles.xml
-Find
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="8000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
-After that line of code squeeze in this:
Code:
<AudioEncoderCap name="aac" enabled="true"
minBitRate="8000" maxBitRate="96000"
minSampleRate="8000" maxSampleRate="48000"
minChannels="1" maxChannels="1" />
-Save and close
-Open: media_codecs.xml (Same folder.)
-Find:
Code:
<MediaCodec name="AACEncoder" type="audio/mp4a-latm" />
-Replace the line with:
Code:
<MediaCodec name="OMX.google.aac.encoder" type="audio/mp4a-latm" />
-Save, close reboot.
Post results, and stuff and hopefully he will be able to answer stuff. The issue was in the ROM itself apparently, so it should work for any CM10 based such.
Edit: Of course, since this is not thoroughly tested, make sure you do a backup before you edit anything.

Not helped.
Desire C,MiniCMv7,NOPE Kernel

Dark_AssassinUA said:
Not helped.
Desire C,MiniCMv7,NOPE Kernel
Click to expand...
Click to collapse
I'm using the CyanogenMod10 (Build #3 by cute_prince) so I guess that MiniCM uses different encoders and decoders. I'll take a look at it, the fix should be similar.
Edit: Okay, it seems to be completely the same. The encoder should be included and working, are you sure you've edited all the things you have to edit? I was just messing around so I don't know what exactly I've changed, it could be that I've forgotten something, I'll upload my files. I've taken these directly from my phone where voice messages are working flawlessly with WhatsApp and Facebook.
To test if your aac encoder is now working, you could try downloading a recorder which supports the filetype. I used Easy Voice Recorder. Make sure to select AAC.
The problem with voice messages was simply that most apps use aac files, most cm roms did have the codec, but it simply wasn't registered in the files.
Edit2: If it still doesn't work after pushing my files in the correct directory (/system/etc/) try clearing all the caches (dalvik cache, too). If it isn't working after you did that, I would guess that this fix only works for cute_prince's rom.

Bobgle said:
I'm using the CyanogenMod10 (Build #3 by cute_prince) so I guess that MiniCM uses different encoders and decoders. I'll take a look at it, the fix should be similar.
Edit: Okay, it seems to be completely the same. The encoder should be included and working, are you sure you've edited all the things you have to edit? I was just messing around so I don't know what exactly I've changed, it could be that I've forgotten something, I'll upload my files. I've taken these directly from my phone where voice messages are working flawlessly with WhatsApp and Facebook.
To test if your aac encoder is now working, you could try downloading a recorder which supports the filetype. I used Easy Voice Recorder. Make sure to select AAC.
The problem with voice messages was simply that most apps use aac files, most cm roms did have the codec, but it simply wasn't registered in the files.
Edit2: If it still doesn't work after pushing my files in the correct directory (/system/etc/) try clearing all the caches (dalvik cache, too). If it isn't working after you did that, I would guess that this fix only works for cute_prince's rom.
Click to expand...
Click to collapse
Wow,it`s working!
Huge thanks from Ukraine!
From newbies(like me) made flashable zip

Dark_AssassinUA said:
Wow,it`s working!
Huge thanks from Ukraine!
From newbies(like me) made flashable zip
Click to expand...
Click to collapse
Glad I could help.

wwooowwwww .....thnxx bro...really it worked....i always had to switch back to sense bcoz of voice message problem in watsapp n other such apps...u saved my life...

[Guide] AC3 sound for stock player & others

How to add support for AC3 audio format​
Guide (need root):
1. Put the file media_codecs.xml in the folder system/etc
2. Put the files libsac3d.so & libsomxac3d.so in the folder system/lib
3. Set permissions to all 3 files: 0644 (owner: root/root)
4. Reboot
Thanks to: Pako777
Download:
View attachment AC3_Tab_S.rar

what is it ? ^^

androidrouen said:
what is it ? ^^
Click to expand...
Click to collapse
Stock player can not play the AC3 audio format (the video can be seen but there is no audio). With this trick the problem disappears..

Nice.

A word of caution
Set the permissions of all 3 files (and not only the last 2... ) to 0644, otherwise you end up with the software video mode...

Niice more reason for me to root this beauty..
Sent from my SM-T705 using Tapatalk

works great thanks

A few days ago I configured a Tab S 10.5 for a relative. They will not root so I installed the free version of MX Player and its ARM7 codec package. This gave me AC3 support without rooting and the loss of the warranty. I also configured MX Player to use HW+ acceleration for all playback.
If the tablet was mine I would have rooted within 10 minutes of confirming that all the hardware works, so I'm only mentioning this alternative for non-root users that want to play AC3 content. I personally bought MX Player Pro as the app is the best video player for Android as far as I'm concerned.
P.S. Thanks for this valuable post.
Sent from my Nexus 10 using XDA Premium HD app

3DSammy said:
I installed the free version of MX Player and its ARM7 codec package. This gave me AC3 support without rooting and the loss of the warranty.
Click to expand...
Click to collapse
Thanks.

Thank you very much.
Any reason why would samsung remove this libs when they are present in older note 3 phones ?

leojab said:
Thank you very much.
Any reason why would samsung remove this libs when they are present in older note 3 phones ?
Click to expand...
Click to collapse
Save money on licensing it for these series of tablets?

Is there a way to also get DTS?

Could anyone guide on how to play Ultra HD videos?
I am not able to play them either through MX with all custom codecs installed and not even through the built in video player with the additional libraries.

no sound on AVCHD.mts (has ac3 from Sony DSC-HX
MX Player with S/W or H/W+ Decoder plays it with Sound (not the H/W Decoder). I installed the files and corrected the permisssion, but still no sound with the preinstalled Video app. it says "no Audio ... not supported Audio codec"
here is the format info:
Code:
Vollständiger Name : \PRIVATE\AVCHD\BDMV\STREAM\00401.MTS
Format : BDAV
Format/Info : Blu-ray Video
Dateigröße : 89,1 MiB
Dauer : 28s 253ms
Modus der Gesamtbitrate : variabel
Gesamte Bitrate : 26,4 Mbps
maximale Gesamtbitrate : 28,0 Mbps
Audio
ID : 4352 (0x1100)
Menü-ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Format_Settings_ModeExtension : CM (complete main)
Format-Einstellungen für Endianess : Big
Codec-ID : 129
Dauer : 28s 320ms
Bitraten-Modus : konstant
Bitrate : 256 Kbps
Kanäle : 2 Kanäle
Kanal-Positionen : Front: L R
Samplingrate : 48,0 KHz
BitDepth/String : 16 bits
Stream-Größe : 885 KiB (1%)
Video
ID : 4113 (0x1011)
Menü-ID : 1 (0x1)
Format : AVC
Format/Info : Advanced Video Codec
Format-Profil : [email protected]
Format-Einstellungen für CABAC : Ja
Format-Einstellungen für ReFrames : 2 frames
Format_Settings_GOP : M=1, N=12
Codec-ID : 27
Dauer : 28s 320ms
Bitraten-Modus : variabel
Bitrate : 25,1 Mbps
maximale Bitrate : 26,0 Mbps
Breite : 1 920 Pixel
Höhe : 1 080 Pixel
Bildseitenverhältnis : 16:9
Bildwiederholungsrate : 50,000 FPS
ColorSpace : YUV
ChromaSubsampling : 4:2:0
BitDepth/String : 8 bits
Scantyp : progressiv
Bits/(Pixel*Frame) : 0.242
Stream-Größe : 84,8 MiB (95%)
Text
ID : 4608 (0x1200)
Menü-ID : 1 (0x1)
Format : PGS
Codec-ID : 144
Dauer : 27s 775ms
I also looked at the differences in the .XML:
Code:
<MediaCodec name="OMX.google.vpx.decoder" type="video/x-vnd.on2.vp8" />
instaed of
<MediaCodec name="OMX.google.vp8.decoder" type="video/x-vnd.on2.vp8" />
<MediaCodec name="OMX.google.vp9.decoder" type="video/x-vnd.on2.vp9" />
additional
Code:
<MediaCodec name="OMX.SEC.hevc.sw.dec" type="video/hevc" >
<Quirk name="decoder-ignores-streamcorrupt-error" />
</MediaCodec>
<MediaCodec name="OMX.Exynos.mpeg4.enc" type="video/mp4v-es" >
<Quirk name="requires-allocate-on-input-ports" />
<Quirk name="requires-allocate-on-output-ports" />
<Quirk name="video-controller-check-enable" />
</MediaCodec>
<MediaCodec name="OMX.Exynos.h263.enc" type="video/3gpp" >
<Quirk name="requires-allocate-on-input-ports" />
<Quirk name="requires-allocate-on-output-ports" />
<Quirk name="video-controller-check-enable" />
</MediaCodec>
<MediaCodec name="OMX.Exynos.avc.enc" type="video/avc" >
<Quirk name="requires-allocate-on-input-ports" />
<Quirk name="requires-allocate-on-output-ports" />
<Quirk name="video-controller-check-enable" />
</MediaCodec>

TheGoD said:
Is there a way to also get DTS?
Click to expand...
Click to collapse
MX Player allows you to install custom decoders. There is an XDA forum that publishes the DTS decoder file which you can add to MX Player. No root is required but sometimes when MX Player is updated you'll have to wait until the DTS decoder is also updated. That's not a big deal just something you'll need to I aware of. This is a licensing issue and a work around. A long time ago MX Player included DTS support with the player install.
Sent from my Nexus 10 using XDA Premium HD app

Thanks, I know about that. Would prefer to get a solution for the stock player though too.

TheGoD said:
Thanks, I know about that. Would prefer to get a solution for the stock player though too.
Click to expand...
Click to collapse
Could one of you please upload a media file (Video would be best) with AC3 that works for him ... so I can test

Why do you guys try XBMC?
Sent from my Galaxy Note 2

needs testing
Could one of you please upload a media file (Video would be best) with AC3 that works for him ... so I can test

I dont think its a good idea just to take the media_codecs.xml from here, as it has more changes than just AC3. I'd suggest to just add those lines to your original media_codecs.xml
Code:
<MediaCodec name="OMX.SEC.ac3.dec" type="audio/ac3" >
<Quirk name="needs-flush-before-disable" />
<Quirk name="decoder-ignores-streamcorrupt-error" />
</MediaCodec>
I m still not having AC-3 sound on my AVCHD.mts video files. Stock video player says unknown audio codec.

Enable Noise Cancellation in Temasek

Flash the provided zip it will enable noise cancellation in temasek
And edit the build prop like this
persist.audio.fluence.audiorec=true
persist.audio.fluence.speaker=true
All thanks to kumajya

Nirbhay2 said:
Flash the provided zip it will enable noise cancellation in temasek
And edit the build prop like this
persist.audio.fluence.audiorec=true
persist.audio.fluence.speaker=true
All thanks to kumajya
Click to expand...
Click to collapse
There is no persist.audio.fluence.audiorec. Only persist.audio.fluence.voicerec. Should I add it to build.prop?

This should do it
actually you need add following 4 lines for Qualcomm fluence in build.prop
ro.qc.sdk.audio.fluencetype=fluence persist.audio.fluence.voicecall=true persist.audio.fluence.voicerec=false persist.audio.fluence.speaker=true
fluencetype can be "none" "fluence" or "fluencepro"
also this should work in all custom ROMs since it is a feature of snapdragon 410

[WIP!][KERNEL] Razer Phone 2 Kernel (+exfat module, TWRP device tree, and more!)

Hi all!
What is this?
This is my mostly-working Razer Phone 2 Kernel and TWRP device tree!
I've been reading threads where people are having issues compiling the Razer-provided source for the RP2 and figured I should post what I have so others can use it to help achieve a fully working source-built kernel.
I'm also including a set of scripts to repack a Magisk-patched boot.img so you can iterate on building a new kernel rapidly, and am including a prebuilt magisk-patched boot.img with the custom kernel so we can QA other features while focusing on the known-broken things.
Also also, I'm including an exfat kernel module (not built into kernel for now) so that can be tested too!
Click to expand...
Click to collapse
Why is this mostly-working?
I've tested many features on this kernel and so far the only feature *not* working is the microphone. (Audio recording, haven't tested in-call audio)
This kernel is a mashup of Razer's source and a few other OSS repos from CAF - specifically the TFA98XX driver, and the audio-kernel repositories, so there's a bit of integration left to do to get all the audio features working.
I also had to edit the defconfig to get the DTB to build, and have to build with some special flags to use the prebuilt DTB compiler (dtc) since the one included in the source isn't capable of compiling the FIH DTBs inside the Razer-provided source (correct me if I'm doing something wrong here, but this was how I ended up getting it to work).
The kernel parameter skip_initramfs has also been renamed to skip__initramfs to break the silly bootloader skipping the ramdisk (and thereby breaking Magisk). This means you don't need to run Magisk's binary patch to rename that kernel argument to make Magisk or TWRP work.
Keep in mind, though, that this means if you use this kernel with a 100% stock ramdisk, you'll only ever get recovery since new Android ramdisks only contain recovery! (Thanks Dees_Troy for the refresher course!)
If you're familiar with the new audio-kernel CAF stuff, please let me know! I could use your assistance getting the microphone working.
It seems like the microphone isn't working because of some mismatches between the in-kernel msm audio drivers and the Razer customized drivers in the vendor partition.
I get errors like
Code:
[31269.485217] send_afe_cal_type cal_block not found!!
in dmesg when attempting to record audio. This seems isolated to the q6afe drivers in the kernel (specifically here: https://github.com/thecubed/android_kernel_razer_sdm845/blob/master/techpack/audio/dsp/q6afe.c#L1593 ) not playing nice with the prebuilt snd_soc_sdm845 kernel module.
Click to expand...
Click to collapse
Where do I get this?
See here for the TWRP device tree (and detailed instructions on how to set up your build tree): https://github.com/thecubed/android_device_razer_cheryl2
See here for just the kernel source: https://github.com/thecubed/android_kernel_razer_sdm845
See here for a kernel-less boot.img skeleton that you can drop your newly minted kernel into and repack with mkbootimg: http://downloads.codefi.re/thecubed/aura2/kernel/magisk_custom_kernel_skel.tar.gz
See here for a prebuilt boot.img with this custom kernel which includes Magisk: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk_custom_9.img
See here for an exfat module you can insmod from a booted phone with custom kernel to try mounting exfat SD cards: http://downloads.codefi.re/thecubed/aura2/kernel/exfat_module.tar.gz
See here for a stock Magisk-patched boot.img for when you're done playing with this: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk.img
Click to expand...
Click to collapse
How do I use this?
First off, this isn't for the average user. This kernel is *under development* and is not fully working yet. This means don't try this kernel on your mom's phone, your neighbor's phone, or any device that you aren't comfortable developing for.
Secondly, to test this, you'll need to be oem unlocked. There's plenty of guides to do this, but be aware that it erases all data on your phone when doing so. You could try using adb backup first, but I didn't have much success with that.
I'd suggest looking at the first link in the Where do I get this section and reading the README for the device tree as it'll have the most detailed instructions.
The gist is you'll need to download a minimal OmniROM manifest, add some lines to a file in .repo/local_manifests/cheryl2.xml, and run mka kernel to get a kernel image.
After that, you'll want to use mkbootimg to build a bootable magisk-patched boot.img, which you'll flash to your device with fastboot flash boot_X path/to/boot.img (where X is the active boot partition).
Once you've got the Image.gz-dtb file from your $OUT/obj/KERNEL_OBJ/arch/arm64/boot/Image.gz-dtb you'll want to repack it into a magisk-patched boot.img
Repacking the boot.img can be done with this command:
Code:
mkbootimg \
--kernel Image.gz-dtb \
--ramdisk boot_magisk.img-ramdisk.gz \
--cmdline 'console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0xA84000 androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 service_locator.enable=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a600000.dwc3 buildvariant=user' \
--base 0x00000000 \
--pagesize 4096 \
--kernel_offset 0x00008000 \
--ramdisk_offset 0x01000000 \
--second_offset 0x00f00000 \
--tags_offset 0x00000100 \
--os_version 8.1.0 \
--os_patch_level 2018-10 \
-o ../boot_magisk_custom.img
Click to expand...
Click to collapse
FAQ
Does this have TWRP?
No. This does not have TWRP. The device tree is for TWRP eventually, and to make compiling the kernel easier (since Android kernels don't like compiling outside of Android's makefile system anymore)​
Does this have Magisk?
Yes! It's "pre-patched" too, as long as you're using my prebuilt one above.​
Do I need the custom kernel to use the exfat module?
Yes. This is because the Razer stock kernel has module signing forced. I don't have Razer's kernel module signing key so I can't compile kernel modules for the stock kernel. My kernel has module signing set to allow mismatched signatures, so both the Razer modules in /vendor/lib/modules (required for sound) and my exfat module can coexist.​
Why is exfat not compiled into the kernel?
Laziness, primarily. Actually, in this case I just didn't want to add extra variables to testing the kernel. If adding exfat into the kernel directly causes other issues it could potentially derail my quest to get this kernel up to par with the stock kernel.​
Why did other kernels not boot?
Most likely due to incompatible audio-kernel revisions, or dtb issues. I'm not sure, but getting this kernel to compile required a bit more hacking than it should have.​
Are you working on TWRP for Razer Phone 2?
Yep. Look for another post once the kernel is good to go. I aim to get encryption support working too, unless Dees_Troy beats me to it ​
Is audio still not working?
I'll update the post to remove the WIP tag and the section about audio as soon as it's working.​
Is anything else not working?
Feel free to download and test to let me know what else isn't working and I'll add it to the OP.​
Click to expand...
Click to collapse
Acknowledgements
Special thanks to Rashed97 and Dees_Troy for all their help.
Click to expand...
Click to collapse
y u quote OP?

Thanks for your work! Looking forward for a stable version. Wanna help but RP2 is currently my only working phone..

u sir,deserve a beer,thanks for working rp2 and not to forget other devs who help u along the way,we will wait patiently,cheers!!!!

Thank you.

Interesting discovery just now, seems that the stock kernel gives the same 'error' in dmesg when recording audio (but obviously audio recording still works).
Code:
[ 1365.950315] send_afe_cal_type cal_block not found!!
This could mean that Razer doesn't have a calibration profile for the microphone anyway (interesting, wonder if there's an opportunity to improve recording quality here?) and that I'm barking up the wrong tree re: calibration mismatches.
I've also confirmed that I get the same 'ASoC: no backend DAIs enabled for [backend name here]' messages in the stock kernel when brute force trying all PCM inputs with:
Code:
for f in `seq 1 80`; do tinycap /sdcard/wavs/device-$f.wav -D 0 -d $f -r 48000; done
It's also (very) possible that I don't understand how tinycap works.
I dumped the list of PCM inputs/outputs with:
Code:
for f in `ls -d /proc/asound/sdm845tavilsndc/** | grep pcm`; do echo "$f : `grep 'id' $f/info`"; done
and
Code:
cat /proc/asound/pcm
on both kernels (stock and custom) and they seem to match.
I'm thinking I should figure out how to record sound outside of android (from adb only) from stock kernel, and use that same test to try in the custom kernel. If I can find a test like that, I should be able to determine if I need to rename one of my DAI links to match whatever's baked into the XML files in /vendor/etc .
Any ideas?

Are you using the audio.a2dp.default.so driver?

Warrior1988: A2DP isn't in play here, and I'm using the stock /system and /vendor partitions, so any razer-customized tweaks are still present.
Currently, I've been working on figuring out the codec mappings to make sure that when audio is being recorded in the custom kernel that all the appropriate routing is set to enable audio from the tfa98xx chip (NXP amplifier, apparently supports digital microphones too?) or the wcd934x codec.
I'm not sure where the microphones are physically connected internally, so I'm working backwards from what gets enabled/disabled when recording audio in the stock kernel.
So far I have observed a few things (pardon my potentially incorrect terminology, the whole linux ASOC sound layer is new to me):
1. Audio in the stock and custom kernels is being captured by the mixer device called "SDM845 Media1", and it is capturing from SLIMBUS_0_TX input.
Code:
[Recording]
aura:/sys/module # cat /sys/kernel/debug/asoc/sdm845-tavil-snd-card/SDM845\ Media1/state
[SDM845 Media1 - Playback]
State: new
Backends:
No active DSP links
[SDM845 Media1 - Capture]
State: start
Hardware Params: Format = S16_LE, Channels = 1, Rate = 16000
Backends:
- SLIMBUS_0_TX
State: start
Hardware Params: Format = S16_LE, Channels = 1, Rate = 48000
2. You can also see when recording and not recording that in both kernels the SLIMBUS_0_TX input is wired correctly to the right mixer:
Code:
[Not recording]
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/platform:soc:qcom,msm-pcm-routing/dapm/SLIMBUS_0_TX
SLIMBUS_0_TX: Off in 2 out 0 - R0(0x0) mask 0x1
stream Slimbus Capture inactive
out "static" "SLIM0_UL_HL"
in "static" "Slimbus Capture"
in "static" "BE_IN"
[Recording]
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/platform:soc:qcom,msm-pcm-routing/dapm/SLIMBUS_0_TX
SLIMBUS_0_TX: On in 2 out 1 - R0(0x0) mask 0x1
stream Slimbus Capture inactive
out "static" "SLIM0_UL_HL"
out "SLIM_0_TX" "MultiMedia1 Mixer"
in "static" "Slimbus Capture"
in "static" "BE_IN"
Now that I've observed those things, I need to do a bit more research on how audio can get enabled/disabled on each of the chips that touch it.
For instance, in the custom kernel, I noticed that during recording sounds the DMIC* lines on the second tfa98xx aren't enabled. I haven't checked in the stock kernel yet - but if the tfa98xx chip is providing mic bias, it's possible that everything is wired right for input but since the mic bias isn't on, the mic isn't powered and thus we get no sound.
(Updated side note, why is Razer Phone 2 is using two TFA9888 chips? The tfa98xx.cnt firmware references TFA9892 which is mono only, too. I need to see a disassembly to figure out what chips it's actually using...)
Code:
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/codec:tfa98xx.4-0034/dapm/DMIC*
DMIC1: Off in 1 out 0
out "static" "AIF OUT"
DMIC2: Off in 1 out 0
out "static" "AIF OUT"
DMIC3: Off in 1 out 0
out "static" "AIF OUT"
DMIC4: Off in 1 out 0
out "static" "AIF OUT"
aura:/sys # cat ./kernel/debug/asoc/sdm845-tavil-snd-card/codec:tfa98xx.4-0035/dapm/DMIC*
DMIC1: Off in 1 out 0
out "static" "AIF OUT"
in "static" "MIC BIAS1"
DMIC2: Off in 1 out 0
out "static" "AIF OUT"
DMIC3: Off in 1 out 0
out "static" "AIF OUT"
in "static" "MIC BIAS3"
DMIC4: Off in 1 out 0
out "static" "AIF OUT"
Update: just noticed that this path doesn't exist on stock kernel. So the TFA driver I have doesn't match the one Razer is using. Interesting!
Also, I'm not sure why SLIMBUS_2 playback/capture aren't shown as 'dynamic DAI' linked (the '(*)' means it's a dynamic DAI)... Probably not important though.
Code:
aura:/proc/asound # cat pcm
00-00: MultiMedia1 (*) : : playback 1 : capture 1
00-01: MultiMedia2 (*) : : playback 1 : capture 1
00-02: VoiceMMode1 (*) : : playback 1 : capture 1
00-03: VoIP (*) : : playback 1 : capture 1
00-04: MultiMedia3 (*) : : playback 1
00-05: SLIMBUS_0 Hostless (*) : : playback 1 : capture 1
00-06: AFE-PROXY RX msm-stub-rx-6 : : playback 1
00-07: AFE-PROXY TX msm-stub-tx-7 : : capture 1
00-09: AUXPCM Hostless (*) : : playback 1 : capture 1
00-10: SLIMBUS_1 Hostless (*) : : playback 1 : capture 1
00-11: SLIMBUS_3 Hostless (*) : : playback 1 : capture 1
00-12: SLIMBUS_4 Hostless (*) : : playback 1 : capture 1
00-13: MultiMedia5 (*) : : playback 1 : capture 1
00-14: Listen 1 Audio Service (*) : : capture 1
00-16: MultiMedia10 (*) : : playback 1 : capture 1
00-17: MM_NOIRQ (*) : : playback 1 : capture 1
00-18: HDMI_RX_HOSTLESS (*) : : playback 1
00-19: VoiceMMode2 (*) : : playback 1 : capture 1
00-20: Listen 2 Audio Service (*) : : capture 1
00-21: Listen 3 Audio Service (*) : : capture 1
00-22: Listen 4 Audio Service (*) : : capture 1
00-23: Listen 5 Audio Service (*) : : capture 1
00-24: Listen 6 Audio Service (*) : : capture 1
00-25: Listen 7 Audio Service (*) : : capture 1
00-26: Listen 8 Audio Service (*) : : capture 1
00-27: MultiMedia9 (*) : : playback 1 : capture 1
00-33: MM_NOIRQ_2 (*) : : playback 1 : capture 1
00-34: SLIMBUS8_HOSTLESS Capture (*) : : capture 1
00-35: Slimbus4 Capture tavil_vifeedback-35 : : capture 1
00-36: SLIMBUS_2 Hostless Playback tavil_rx2-36 : : playback 1
00-37: SLIMBUS_2 Hostless Capture tavil_tx2-37 : : capture 1
00-38: MultiMedia6 (*) : : playback 1 : capture 1
00-39: USB Audio Hostless (*) : : playback 1 : capture 1
00-80: QUAT_MI2S_RX Hostless (*) : : playback 1
Meanwhile, we've reached out to Razer to see if they'll bless us with the full and complete kernel source this time

I doubt it. They won't even answer simple questions as to an estimate of when we're getting Pie

blackknightavalon said:
I doubt it. They won't even answer simple questions as to an estimate of when we're getting Pie
Click to expand...
Click to collapse
>simple question
>eta
pick one

Any progress on this kernel? I'm really curious now that we have pie.

No progress as of yet, I've been busy with work recently and Razer hasn't dropped source for the new kernel version (still 4.9 but a different patch level).
I'm hopeful that Razer will drop the complete source for Pie's kernel and I can backport that to the Oreo kernel for those who want to keep the old OS.
I haven't updated my RP2 to Pie yet so I can test out any changes once the source for the new kernel is out. I'll be sure to post here when I have any updates

Audio-kernel source is out! https://s3.amazonaws.com/cheryl-factory-images/audio-kernel-aura-2009.tar.gz
I'll be rebuilding my kernel very soon and testing.

https://s3.amazonaws.com/cheryl-factory-images/

Warrior1988 said:
https://s3.amazonaws.com/cheryl-factory-images/
Click to expand...
Click to collapse
Yup, I'm building it right now!

Yup, it works! I have fully working audio and microphone now. Seems like there's a bunch of DAI changes and some offset changes to calibration stuff that FIH added (ugh).
Please hold while I get the commit up on my Github, and I'll get a build with exfat going here in just a minute after.
Plan is:
- Github updates (readme changes, etc) UPDATE: done
- Upload this current build I just tested for anyone that wants it
- Add exfat module to kernel and rebuild / test UPDATE: exfat support works, BUT I need to recompile vold to support exfat. I can mount the SD card just fine, but Android doesn't understand that it's mounted because vold isn't tracking it
Also, <3 u razer, thanks
I'm bummed to hear about the layoffs, and I really appreciate whomever uploaded the source even after that. Hopefully Razer's phone team will grow again and get to make us a Razer Phone 3 at some point in the future.

For anyone that's still running 8.1 and wants to try my custom kernel (no, no exfat support yet until I get vold fixed), here's a link: http://downloads.codefi.re/thecubed/aura2/kernel/boot_magisk_custom_10.img
Github has been updated as well.
I'll be sure to update the OP tomorrow when it's not 2AM.
EDIT: Fixed link, 2AM is not kind to my typing skills

Awesome work! Very excited to try it out tomorrow.
Also sad to see your post about their layoffs. Pretty fun phone with much potential for future.
I think some of the reviews are pretty harsh given the penchant of Pixel / Samsung / Apple worship out there.
Anyway, thanks so much for this.

thecubed said:
For anyone that's still running 8.1 and wants to try my custom kernel (no, no exfat support yet until I get vold fixed), here's a link: http://downloads.codefi.re/thecubed/aura2/boot_magisk_custom_10.img
Github has been updated as well.
I'll be sure to update the OP tomorrow when it's not 2AM.
Click to expand...
Click to collapse
Thank you for this!
It's showing up "Not found" on the download link though.

jal3223 said:
Thank you for this!
It's showing up "Not found" on the download link though.
Click to expand...
Click to collapse
Fixed the link in my previous post - sorry about that!
I'll be updating the OP tonight too when I get home from work.

Looking good! Is the sound as good as stock (or maybe better, considering the low volume crackling we get)?
Hoping to give this a shot soon, as soon as I figure out rooting on 9.0. I saw a thread about it, but nobody answered my question there, and light digging through threads didn't turn up an answer, so trying this kernel will have to wait a bit. Makes me miss the HTC root days, when finding out about root was a simple yes or no situation... lol.