• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread
By:
Advanced…
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,457
Austin, TX
Gamesoul Master said:
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.
Click to expand...
Click to collapse

Sound seems to have the same issues as stock - slight popping sounds on audio playback, and loud popping sound recorded at start of any audio recordings, but I have a strong feeling these have everything to do with the tfa98xx code razer modified.
I suspect Razer isn't muting the inputs/outputs of the chip while it's being brought out of sleep/reset when audio isn't playing.

I should be able to merge in the latest tfa98xx code from CAF with the few necessary tweaks to fix the popping.

I'm not sure if this is fixed on 9.0 or not, since I'm not running 9.0 yet (I will when src is released).

Also, off topic, but to answer your question rooting 9.0 seems to be fairly straightforward - if you're already rooted on 8.1 you can just take the OTA before rebooting use magisk manager to "install to inactive slot" and it'll patch the freshly installed 9.0 partitions.
If you're not already rooted, you should be able to just flash someone's pre-rooted boot.img and be good to go. I won't get into detail in that here since I'm sure others have a better guide than I do.
 
  • Like
Reactions: Gamesoul Master and jal3223
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,457
Austin, TX
Quick status update: Android 9.0 source is out, I'm going to switch my build targets (and update my phone) to 9.0 and start working through the exfat changes for 9.0 (no sense doing it twice when everyone's going to end up on 9.0 anyway).
TWRP works on 8.1 with full decryption support thanks to Dees-Troy, but we're holding off releasing it until we test on 9.0 since we don't want to support multiple kernel versions for TWRP downloads (i.e. you'd need a twrp download for people still on 8.1, and one for people on 9.0, and then have to fix bugs for both).

I'll let y'all all know when I've got more info later this weekend most likely.
 
  • Like
Reactions: CalebQ42, BoezeGott, Craftingmod and 5 others
J

jal3223

Senior Member
Mar 14, 2009
1,470
376
Google Pixel XL
Samsung Galaxy S8+
thecubed said:
Quick status update: Android 9.0 source is out, I'm going to switch my build targets (and update my phone) to 9.0 and start working through the exfat changes for 9.0 (no sense doing it twice when everyone's going to end up on 9.0 anyway).
TWRP works on 8.1 with full decryption support thanks to Dees-Troy, but we're holding off releasing it until we test on 9.0 since we don't want to support multiple kernel versions for TWRP downloads (i.e. you'd need a twrp download for people still on 8.1, and one for people on 9.0, and then have to fix bugs for both).

I'll let y'all all know when I've got more info later this weekend most likely.
Click to expand...
Click to collapse


Amazing news! Thank you so much. Also, I hope exfat can be sorted out. It blows my mind that it doesn't support it already.
 
Rox598

Rox598

Senior Member
Sep 7, 2011
1,771
436
Northern Ireland
thecubed said:
Quick status update: Android 9.0 source is out, I'm going to switch my build targets (and update my phone) to 9.0 and start working through the exfat changes for 9.0 (no sense doing it twice when everyone's going to end up on 9.0 anyway).
TWRP works on 8.1 with full decryption support thanks to Dees-Troy, but we're holding off releasing it until we test on 9.0 since we don't want to support multiple kernel versions for TWRP downloads (i.e. you'd need a twrp download for people still on 8.1, and one for people on 9.0, and then have to fix bugs for both).

I'll let y'all all know when I've got more info later this weekend most likely.
Click to expand...
Click to collapse

Awesome work guys!
 
B

blackknightavalon

Senior Member
Feb 1, 2009
3,218
530
Somewhere in NYC
thecubed said:
Quick status update: Android 9.0 source is out, I'm going to switch my build targets (and update my phone) to 9.0 and start working through the exfat changes for 9.0 (no sense doing it twice when everyone's going to end up on 9.0 anyway).
TWRP works on 8.1 with full decryption support thanks to Dees-Troy, but we're holding off releasing it until we test on 9.0 since we don't want to support multiple kernel versions for TWRP downloads (i.e. you'd need a twrp download for people still on 8.1, and one for people on 9.0, and then have to fix bugs for both).

I'll let y'all all know when I've got more info later this weekend most likely.
Click to expand...
Click to collapse

I would honestly have no problems with a separate download for each Android build. It takes maybe 2 seconds to flash recovery
 
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,457
Austin, TX
Status update: I'm working on getting everything building for 9.0, however while preparing my build trees I realized that audio-kernel source for 3110 isn't out, only 3040. I've posted in the other thread ( https://forum.xda-developers.com/showpost.php?p=79171840&postcount=24 ) to see if Razer can upload the MR1 3110 sources when they're not busy.

My goal is to have a android-9.0-3110-MR1 branch in my Github once the source is available and a exfat kernel (using sdfat) shortly after. Then I'll start working on vold support for exfat.
We're still QA'ing TWRP, and I'll let you know when I have a status update there.
 
  • Like
Reactions: CurtisMJ, lixindiyi, jal3223 and 6 others
Warrior1988

Warrior1988

Senior Member
Jun 28, 2015
332
262
33
thecubed said:
Status update: I'm working on getting everything building for 9.0, however while preparing my build trees I realized that audio-kernel source for 3110 isn't out, only 3040. I've posted in the other thread ( https://forum.xda-developers.com/showpost.php?p=79171840&postcount=24 ) to see if Razer can upload the MR1 3110 sources when they're not busy.

My goal is to have a android-9.0-3110-MR1 branch in my Github once the source is available and a exfat kernel (using sdfat) shortly after. Then I'll start working on vold support for exfat.
We're still QA'ing TWRP, and I'll let you know when I have a status update there.
Click to expand...
Click to collapse

Looks to me it's all the same.

https://developer.razer.com/razer-phone-dev-tools/kernel-source-code/?_ga=2.184187238.1995365126.1553112791-598559331.1548458885?_ga=2.184187238.1995365126.1553112791-598559331.1548458885

Razer Global Kernels

Version Release Date
9.0 MR1 – Kernel Source March 2019
9.0 MR0 – Kernel Source February 2019
9.0 MR0 and MR1 - Audio Kernel February 2019
9.0 MR0 and MR1 - Wifi Source
Click to expand...
Click to collapse
 
  • Like
Reactions: jal3223
CurtisMJ

CurtisMJ

Senior Member
May 23, 2013
633
533
I managed to compile with the techpack they have up now and indeed everything audio related does work. Also the linaro toolchain seems to cause memory corruption. I have no idea lol
 
  • Like
Reactions: Warrior1988
thecubed

thecubed

Inactive Recognized Developer
Aug 19, 2008
1,046
10,457
Austin, TX
CurtisMJ said:
I've also tried to start upstreaming the kernel if you're interested. https://github.com/CurtisMJ/cheryl2_custom_kernel
Audio and WiFi immediately stop working citing mismatch of symbol in the log so modules need to be replaced on the vendor partition. I need to figure out how to compile that WiFi module...
Click to expand...
Click to collapse

You shouldn't have to replace those modules as long as you're compiling the kernel using the techpack. I'd recommend double checking that the techpack is being included by the defconfig properly.
 
  • Like
Reactions: CurtisMJ and RKBD
CurtisMJ

CurtisMJ

Senior Member
May 23, 2013
633
533
Could be. I'm using the same defconfig as I did for an older build and sound worked though. I'll double check. I'm thinking maybe its the kernel headers used by the techpack, could result in slight differences in the final module with bad enough luck? I'll see.

Edit: maybe I'll just compile them in the kernel. Android kernels didn't use modules the last time I did this :p
Edit2: OK I googled it. The exact message I get is something like:
cd_dsp_glink: disagrees about version of symbol dev_warn
And apparently this is due to a kernel data structure changing, and the solution is to recompile the modules :( So stock modules may not be compatible with an upstreamed kernel.
https://unix.stackexchange.com/questions/125624/unable-to-load-module-disagrees-about-version-of-symbol-module-layout
Edit3: Theres apparently a config to disable version checks. Imma try it
 
Last edited:
  • Like
Reactions: Warrior1988 and RKBD
Warrior1988

Warrior1988

Senior Member
Jun 28, 2015
332
262
33
CurtisMJ said:
Could be. I'm using the same defconfig as I did for an older build and sound worked though. I'll double check. I'm thinking maybe its the kernel headers used by the techpack, could result in slight differences in the final module with bad enough luck? I'll see.

Edit: maybe I'll just compile them in the kernel. Android kernels didn't use modules the last time I did this :p
Edit2: OK I googled it. The exact message I get is something like:
cd_dsp_glink: disagrees about version of symbol dev_warn
And apparently this is due to a kernel data structure changing, and the solution is to recompile the modules :( So stock modules may not be compatible with an upstreamed kernel.
https://unix.stackexchange.com/questions/125624/unable-to-load-module-disagrees-about-version-of-symbol-module-layout
Edit3: Theres apparently a config to disable version checks. Imma try it
Click to expand...
Click to collapse

Good luck are you working on custom Kernel or TWRP?
 
CurtisMJ

CurtisMJ

Senior Member
May 23, 2013
633
533
Warrior1988 said:
Good luck are you working on custom Kernel or TWRP?
Click to expand...
Click to collapse
Custom kernel. So far I've figured out trying to modify the vendor partition is an absolute nightmare. I might just have a jerry-rigged magiskinit in the ramdisk to bind mount something from the ramdisk over it before they're modprobed, but we definitely need new modules. Disabling symbol checking just makes it go crazy
Edit: got something to work...I think. I'll try again later...
 
Last edited:
You must log in or register to reply here.

Similar threads

arter97
[r14] arter97 kernel for Razer Phone 2
Replies
542
Views
81K
E
edison
H
22/7/19 TWRP Stock ROM Pie MR1 (No Bloatware) for Razer Phone 2
Replies
28
Views
10K
G
Gamesoul Master
mikeioannina
[ROM][11][OFFICIAL] LineageOS 18.1 for Razer Phone 2
Replies
309
Views
25K
P650SE
P650SE
Alcatraz323
[ROM][UNOFFICIAL][11] EvolutionX 5.9.2 for Razer Phone 2
Replies
15
Views
896
V
vladis444
Warrior1988
[ROM][Pie] MR1 and MR2 Stock Deodexed
Replies
94
Views
21K
jonchance_84
jonchance_84

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 10
    thecubed
    thecubed
    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?
    View
    9
    thecubed
    thecubed
    Status update: I'm working on getting everything building for 9.0, however while preparing my build trees I realized that audio-kernel source for 3110 isn't out, only 3040. I've posted in the other thread ( https://forum.xda-developers.com/showpost.php?p=79171840&postcount=24 ) to see if Razer can upload the MR1 3110 sources when they're not busy.

    My goal is to have a android-9.0-3110-MR1 branch in my Github once the source is available and a exfat kernel (using sdfat) shortly after. Then I'll start working on vold support for exfat.
    We're still QA'ing TWRP, and I'll let you know when I have a status update there.
    View
    8
    thecubed
    thecubed
    Quick status update: Android 9.0 source is out, I'm going to switch my build targets (and update my phone) to 9.0 and start working through the exfat changes for 9.0 (no sense doing it twice when everyone's going to end up on 9.0 anyway).
    TWRP works on 8.1 with full decryption support thanks to Dees-Troy, but we're holding off releasing it until we test on 9.0 since we don't want to support multiple kernel versions for TWRP downloads (i.e. you'd need a twrp download for people still on 8.1, and one for people on 9.0, and then have to fix bugs for both).

    I'll let y'all all know when I've got more info later this weekend most likely.
    View
    3
    thecubed
    thecubed
    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 ;)
    View
    3
    thecubed
    thecubed
    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.
    View

New posts