Related
Please remember to make a backup image of your phone before experimenting.
============ WARNING!! =============
The highest setting is VERY loud (as I found out) and could potentially rip apart the speaker on your phone!
Exercise extreme caution when using this. You risk permanent damage to your phone and your ears.β
2013-Jan-20
-----------------
Thanks xda-developers members "skvalex" who wrote ALSAMixer and "chdlock" who is helping me figure out
how ALSA is mapping the audio chipset, we can now temporarily adjust the Digital Volume on the Nexus 4.
Unfortunately, the selected volume doesn't "stick" because the audio driver re-writes it every time it re-opens an audio stream.
A stream is usually opened when a music track begins to play so then the digital volume will reset back to default.
We need a kernel developer to modify the audio driver so it opens an audio stream using a user-selected Volume level.
***
If you don't mind setting the volume frequently or just want to try this out here's what you need:
1) Get ALSAMixer from the Play Store. It was updated recently and you need the latest version.
Please consider a donation to the author.
2) You can re-program the audio chipset by editing fields in ALSAMixer. Here is a list of what we can control so far.
Headphones volume:
Left: RX1 Digital Volume (numid=27)
Right: RX2 Digital Volume (numid=28)
Speaker volume:
RX3 Digital volume (numid=29)
Camcorder volume:
DEC6 Volume (numid=39)
Microphone volume:
DEC7 Volume (numid=40)
-----------------------------------------------
old OPs
-----------------------------------------------
2013-Jan-15
----------------
The creator of ALSAMixer updated it to correctly install for Nexus4. (Uninstall removes the app but the ALSA libraries remain on the phone.)
https://play.google.com/store/apps/details?id=com.skvalex.alsamixer&hl=en
Thank you so much!
--------
http://forum.xda-developers.com/attachment.php?attachmentid=1653124&d=1358438577
This is a piped output of "alsa_amixer -c 0 contents" from a stock Nexus 4 (4.2.1)
2013-Jan-13
-----------------
Is anyone successfully running ALSA on their Nexus 4?
If you do please share instructions to do so.
I am on stock 4.2.1(rooted/busybox) and I ran the AlsaMixer from
the Play Store but it doesn't seem to complete the installation.
http://forum.xda-developers.com/sho...ited Edition Kitβ
ββ
| aokp,minco,pa,rasbean |
Shameless promotion
Sent from my Nexus 4
Next you're going to tell me that you want systemd and PulseAudio on your device too, right?
I wiped to stock,
I installed AOKP-jb-mr1-build1,
then Nocturnal 1.4 LE for AOKP
and the ALSAMixer still doesn't work. It installs but I get the same blank screen with no settings.
What am I doing wrong?
I'm not sure what that app is, I just meant that some of the audio mods in the kit ROM referred to ALSA audio libs.
As you can tell I'm not the expert, sorry if that's not what you were referring too
Sent from my Nexus 4
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
-Mindroid- said:
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
Click to expand...
Click to collapse
I have only a Nexus 7, and the SoC is different from the Nexus 4, but look for alsa_amixer (installed by AlsaMixer) from within a console and execute
"alsa_amixer -c X contents" (without the quotes)
where X is one of the card numbers shown in your /proc/asound directory (e.g. card0 [X=0], card1 [X=1], etc). In my case, X=1 is the actual card where (a lot of) values can be set. One of those values is called "ADC Boost Gain"(I guess a programmable analog gain?).
I established a call with CSipSimple and successfully raised that parameter by 24dB in mid-call by executing "alsa_amixer -c 1 cset numid=20 2" [the default value was 0 and each step increases the level by 12dB]
You can query individual parameters by executing alsa_amixer -c X cget numid=Y
YMMV with the Nexus 4. Good luck!
Thank you! This looks really promising.
I only have "card0" aka [apq8064tablasnd].
When trying to execute "alsa_mixer -c 0 contents" I get an error stating that I'm missing
library "libasound.so". Any ideas what could be wrong?
I'm not sure whether libasound.so came with the AlsaMixer app. If it did you may need to copy the library into a system library path, e.g. /system/lib. If not, I could send you the library that I have. I actually forgot whether I found the library somewhere online or whether I cross-compiled it myself...
Sent from my Nexus 7 using xda app-developers app
ALSA on Nexus 4 sound capabilities
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
If I understand correctly the app is just an installer that puts the ALSA libraries on your system.
If you are not using them it probably doesn't matter if they are there or not. You can contact the app creator about it.
-Mindroid- said:
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
Click to expand...
Click to collapse
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
Restore your back up
Sent from my Nexus 4 using xda premium
alsa_amixer c- 0 contents
chdloc said:
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
Click to expand...
Click to collapse
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
-Mindroid- said:
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
Click to expand...
Click to collapse
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
chdloc said:
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
Click to expand...
Click to collapse
It's a long shot but if you are in the New York tri-state area I wouldn't mind meeting up and letting you mess around with the Nexus4.
The invitation is open to anyone with ALSA experience. I would love to learn more about it first-hand.
As far as I can tell:
- ALSAMixer installs the ALSA libraries and displays the control set. I tried modifying a value with it and it didn't work.
It's a matter of wrong syntax I think, I will contact the app creator about it.
- Terminal Emulator works. I was able to change the value of "AUX_PGA_LEFT Volume" with the following command:
alsa_amixer cset numid=54 39
I'm not sure what this one does yet but I will investigate later today.
- unfortunately, during a phone call "proc/asound/card0/pcm0p/sub0/status" (playback) as well as
"proc/asound/card0/pcm0c/sub0/status" (capture) report "closed". Earlier I tried recording a voice call from an app
and trying to prepare an audio stream with MediaRecorder.AudioSource.VOICE_CALL throws an exception.
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
-Mindroid- said:
[...]
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
Click to expand...
Click to collapse
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
chdloc said:
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Click to expand...
Click to collapse
Great find! This seems to be exactly what we need.
Most intriguing there are also facilities for Voice Call and FM Radio audio streams. Those are not currently working on
the Nexus4 at the moment and this might shed some light on a possible solution.
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
I confirmed with 'cget' that I am indeed setting values with 'cset'.
chdloc said:
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
Click to expand...
Click to collapse
It seems that DEC7 controls to the MICROPHONE stream and DEC6 the CAMCORDER.
I will focus my attention on these.
chdloc said:
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
Click to expand...
Click to collapse
I was wondering about that myself. There is very bad low frequency noise on video recordings so I will
definetly look into this.
-Mindroid- said:
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Click to expand...
Click to collapse
Actually, the nomenclature is quite common, TX, i.e. transmit [to the network] denotes the signal to be transmitted (taken from from microphone)
while RX is the receive signal [from the network] to be played back through a loudspeaker.
-Mindroid- said:
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
Click to expand...
Click to collapse
No, you will have to issue the command only once. Without having looked at the underlying code I tend to think that the first number denotes the type, i.e. integer vs string, and the second number the actual value.
Another interesting observation is that the SoC of the Nexus 4 seems to support SRS TruMedia via an effects mixer, which reportedly has potential to improve audio considerably (http://www.srstechnologies.com/content.aspx?id=1269 , I believe).
Hi all, [I did a forum search using volume galaxy note 3; volume mod galaxy note 3 and didn't find anything related to my post below]
I have quite a bit of a head scratcher here and I'm not sure which way to go to resolve it....
I have an AT&T Galaxy Note 3 that is rooted running stock MJ5 firmware. When playing music using the speaker and built-in music app (or when setting up the sounds to use for ringtone, notifications, etc.), the volume output is decent respective to it's factory output level. However when I'm playing music via PowerAmp or JetAudio Plus - the volume output is not at the same level as it is with the built-in music app. I've made sure that AGC is off in JetAudio, de-selected the Limit option in PowerAmp, and checked and unchecked the Direct Volume Control option within the advanced audio settings in PowerAmp. In spite of all that I have checked - the volume output is not the same and it's driving me crazy. Here are all of the things that I've done so far (in no particular order) to see if I can 'fix' the problem:
1) Factory Reset my phone (from within the OS itself)
2) I've tried using the Volume Boosting Mods found in this forum post to see if that would correct anything.
3) Performed a FULL firmware restore (courtesy of this post) to see if I mucked something up along the way. (I kind of messed up my haptic feedback which was the catalyst for the restore. The volume restore was along for the ride at that point )
None of the above seems to work (EVEN with the firmware restore). Please note that with the firmware restore - I tested it out BEFORE loading my applications (except for JetAudio and PowerAmp). What makes the built-in music application different than apps such as PowerAmp, JetAudio, etc. that it accesses a different volume stream (say digital vs. analog)? (I know that last question was kind of confusing, but think of it as being analogous to Line Out vs. the 3.5mm headphone port for external sound output )
I know that the file used for modifying volume output levels is located in system/etc/snd_soc_msm (the file snd_soc_msm_Taiko_CDP is what's used to make the mods) but is there a specific line or lines contained within that file that control analog volume output for the built-in speaker?
I'm not sure how the PowerAmp or JetAudio app is configured to access volume output streams (if that makes any sense) but there seems to be something different because the volume output drops pretty badly when using either of these apps vs. the stock music player.
Has anyone else noticed this oddity (and found a way to fix it) or am I the odd man out here ?
Any help would be appreciated.
Silly question: Did you try disabling Adapt Sound?
ShadowLea said:
Silly question: Did you try disabling Adapt Sound?
Click to expand...
Click to collapse
I don't recall having Adapt Sound enabled (I did see it but don't remember having any checkboxes ticked....). I'll reply back once I downgrade my phone back to JB (I was forced to take an OTA update to kitkat and I need root access).
rob.allen78 said:
I don't recall having Adapt Sound enabled (I did see it but don't remember having any checkboxes ticked....). I'll reply back once I downgrade my phone back to JB (I was forced to take an OTA update to kitkat and I need root access).
Click to expand...
Click to collapse
So after going through a full factory reset (via ODIN), I can confirm that I'm not using Adapt Sound and have also ensured that I am not using any equalizers to enhance the sound in either application.
You cant compare PA or JA to the stock audio because those 2 apps using different drivers than a stock 1
rob.allen78 said:
I don't recall having Adapt Sound enabled (I did see it but don't remember having any checkboxes ticked....). I'll reply back once I downgrade my phone back to JB (I was forced to take an OTA update to kitkat and I need root access).
Click to expand...
Click to collapse
meawww said:
You cant compare PA or JA to the stock audio because those 2 apps using different drivers than a stock 1
Click to expand...
Click to collapse
Thanks for the info (The driver usage may be what the difference is respective to audio output.)
I wasn't really trying to compare the apps per se as more of a process of finding out if I have a unique hardware issue in which I would need to send my phone back to AT&T/Samsung for a warranty exchange.
There are a lot of users with uneven speakers, some have even exchanged their phones and still had the same problem with their second device. So I don't see the point in exchanging mine atm.
Using power amp I fixed my issue by panning my sound a little more to my bottom speaker, however this only works when listening to music.
Since the fix for music was so simple, is there anyone that can make a mod to change the phones speaker balance for the whole system?
I tried viper4android which has channel pan, but that setting is not available for phone speakers. Is there any other solution?
jamespat93 said:
There are a lot of users with uneven speakers, some have even exchanged their phones and still had the same problem with their second device. So I don't see the point in exchanging mine atm.
Using power amp I fixed my issue by panning my sound a little more to my bottom speaker, however this only works when listening to music.
Since the fix for music was so simple, is there anyone that can make a mod to change the phones speaker balance for the whole system?
I tried viper4android which has channel pan, but that setting is not available for phone speakers. Is there any other solution?
Click to expand...
Click to collapse
I do not have a 6P, but I still follow especially audio-related posts with interest.
One solution (root required!) would be to first play around with the audio mixer while playing music (or other audio material). First, go here and download the tinymix_lollipop.tar.gz file from the second post. This is the user-space mixer interface that at least on my Nexus 5 also works on Marshmallow. Copy the binary (tinymix) from that archive to, for instance, /system/bin and make executable (permission 755). Once installed, go to a root shell on your phone and execute
Code:
tinymix "Left Speaker Gain" X
and/or
Code:
tinymix "Right Speaker Gain" Y
where X and Y seem to be 20 by default. Carefully (!) change X and Y independently of each other until you find a satisfactory balance. I'd suggest you go one "tick" at a time and initially lower the gain instead of increasing it. Without having looked at the device-specific kernel, I don't know what the range of this mixer control is, but you can find out by issuing
Code:
tinymix "Left Speaker Gain"
Note X and Y that sound good to you and hard-code them, I believe, in the "speaker-gain-default" section of your /system/etc/mixer_paths.xml file and reboot.
chdloc said:
I do not have a 6P, but I still follow especially audio-related posts with interest.
One solution (root required!) would be to first play around with the audio mixer while playing music (or other audio material). First, go here and download the tinymix_lollipop.tar.gz file from the second post. This is the user-space mixer interface that at least on my Nexus 5 also works on Marshmallow. Copy the binary (tinymix) from that archive to, for instance, /system/bin and make executable (permission 755). Once installed, go to a root shell on your phone and execute
Code:
tinymix "Left Speaker Gain" X
and/or
Code:
tinymix "Right Speaker Gain" Y
where X and Y seem to be 20 by default. Carefully (!) change X and Y independently of each other until you find a satisfactory balance. I'd suggest you go one "tick" at a time and initially lower the gain instead of increasing it. Without having looked at the device-specific kernel, I don't know what the range of this mixer control is, but you can find out by issuing
Code:
tinymix "Left Speaker Gain"
Note X and Y that sound good to you and hard-code them, I believe, in the "speaker-gain-default" section of your /system/etc/mixer_paths.xml file and reboot.
Click to expand...
Click to collapse
Thank you so much! this is extremely helpful and seems like it will be a great solution. I'm trying to go through the steps now but just need a little help.
I download tinymix_lollipop.tar.gz, extracted the tinymix file and copied it to system/bin. Then I changed its permissions to 755 to make it executable like you said. Next I tried to use terminal emulator and typed 'tinymix "Left Speaker Gain" 1' just to test it. However it just gives me the error message 'failed to open mixer'. I'm rooted and made the file executable so I'm not sure why it didn't work?
jamespat93 said:
Thank you so much! this is extremely helpful and seems like it will be a great solution. I'm trying to go through the steps now but just need a little help.
I download tinymix_lollipop.tar.gz, extracted the tinymix file and copied it to system/bin. Then I changed its permissions to 755 to make it executable like you said. Next I tried to use terminal emulator and typed 'tinymix "Left Speaker Gain" 1' just to test it. However it just gives me the error message 'failed to open mixer'. I'm rooted and made the file executable so I'm not sure why it didn't work?
Click to expand...
Click to collapse
Before executing tinymix you need to make sure that this particular shell session has been granted root privileges. You need to type
Code:
su
in your terminal emulator to accomplish that. The prompt should switch to #
chdloc said:
Before executing tinymix you need to make sure that this particular shell session has been granted root privileges. You need to type
Code:
su
in your terminal emulator to accomplish that. The prompt should switch to #
Click to expand...
Click to collapse
Yeah its working perfectly now thanks! Just going to play with it a bit till I find settings I'm happy with but this is exactly what I was looking for!
The range is 0-31 so does that mean its safe to put the gain anywhere between those numbers?
jamespat93 said:
The range is 0-31 so does that mean its safe to put the gain anywhere between those numbers?
Click to expand...
Click to collapse
Who knows? I'm guessing things will start to audibly distort at gains higher than 20, maybe even to the point of physical damage at the top end.
Wow guess I'll be leaving it below 20 then, but seriously thanks again!
jamespat93 said:
Yeah its working perfectly now thanks! Just going to play with it a bit till I find settings I'm happy with but this is exactly what I was looking for!
The range is 0-31 so does that mean its safe to put the gain anywhere between those numbers?
Click to expand...
Click to collapse
What values did you end up using? And just to confirm....the top speaker is left?? because my top speaker is way louder than my bottom...so should I increase the bottom "1" or decrease the top speaker "-1". Also I'm assuming you can do a negative gain right?
bsg411 said:
What values did you end up using? And just to confirm....the top speaker is left?? because my top speaker is way louder than my bottom...so should I increase the bottom "1" or decrease the top speaker "-1". Also I'm assuming you can do a negative gain right?
Click to expand...
Click to collapse
Yeah top speaker gain is for the left speaker. The gain is '20' at default and it changes to whatever number you change it to. So to reduce it just change it to any number below 20. I changed my left speaker gain to 16.
Also elemental kernel now has left and right speaker gain controls too.
jamespat93 said:
There are a lot of users with uneven speakers, some have even exchanged their phones and still had the same problem with their second device. So I don't see the point in exchanging mine atm.
Using power amp I fixed my issue by panning my sound a little more to my bottom speaker, however this only works when listening to music.
Since the fix for music was so simple, is there anyone that can make a mod to change the phones speaker balance for the whole system?
I tried viper4android which has channel pan, but that setting is not available for phone speakers. Is there any other solution?
Click to expand...
Click to collapse
How did you install Viper4android and get channel pan? I installed using this http://forum.xda-developers.com/nex...er4android-t3250579/post65464645#post65464645
and the setting seems to be missing!
Dear folks,
I used to search this and other forums for an easy solution to increase the volume level of my Galaxy S5 (G900F) in both directions, to mic something and for listening. I do not care of speakers (to destroy them) or my ears (they are already in bad status since the DISCO-Beats in early 90ties), smile, but I hate to anoy my friends with to low volume messages (even when I am at home with no background sounds). In the car it is even worse. My phone is rooted. Android 8.1.0 Extend Version AospExtended-5.4-unofficial, 2018-April-05, G900FXXU1CPC9, with Kernel 3.4.113-lineageos-g808bf80, Build-Number OPM2.171019.029, Moderate
I have downloaded and testet micgain26higher.zip, micgain26normal.zip, Mic_Gain_Mod_v11.9.zip, and s5_Volume_Boost_Version_vX...zip
None of it works.
I even extracted / copied the three files from container to /etc, with no positive result.
I tried to increase the numbers within mixer_paths.xml by hand, no improvements.
Please give me a solution (preferable a ready made mixer_paths.xml to copy/paste).
Thanks.
I think there is no solution - mine is loud for me, but my mic level is poor. I expect nobody is good enough to help you here.
Copy the mixer_paths.xml that i have attached to "/vendor/etc" and change permissions to "rw- r- r-". (ps : i think it is not necessary to change permissions anymore but just in case you can try)
For me it works on recording audio
The guy in this thread.....
http://forum.xda-developers.com/showthread.php?t=3202087
Knows a *lot* about adjusting the xml file to make adjustments to various volume level parameters. He was able to give me a lot of help when I needed it. Why not ask in that thread.
Sent from my SM-G900F
Since I installed Android 10 on my phone I have been experiencing problems related to audio, when I use the speakers for anything it is just to low to listen to, sometimes when someone call me I often can't hear the ringtone. However the microphone is OK, its quality for recording human voice (specially) is amazing and everyone listens to me loud and clear.
Possible solutions?
Well, I did some research and find out that Android Q doesn't have a to3g file, some websites may tell you go to
Code:
/device/etc/sound/to3g
and open it using any text editor, but you won't find it in our Galaxy-A20. I tried to find it in /vendor partition and /system partition but no success.
There were two more interesting files in /vendor partition, mixer_paths.xml and mixer_gains.xml, I tried changing their values and comparing them with the original ones that comes with vendor.img.lz4 from stock ROM, also there was no difference between them.
The question is, does anyone know how to solve this problem? If so, please help us and I'll mention the comment here. Thanks.
This problem also happens in Pie versions of Android, as you can see here in the bugs' section
https://www.android-hilfe.de/forum/...iziell-pie-lineageos-16-0-andyvan.928318.html
Alright, part of the problem can be solved by installing Agrim's custom kernel. This can be found here
the same problem here. There's no solution?