I have the Corsair Vengeance 2000 headset and i would like to use it with my SGS3 running Temasek's unofficial CM10 rom.
I tried using a OTG-cable and plugged in the the USB adapter that comes with the headset but no sound seems to go through.
When i connect the USB and turn on the headset, i am able to control the volume with the wheel on the side of the headset but i can't play sound.
I ticked on "use usb dock audio" in advanced settings but still, no sound.
What can i do to get sound through?
What am i doing wrong?
I am willing to change ROM or Kernel to get this to work, if possible.
I have a friend who got a g930 to work on his sgs3.
Thanks in advance.
If you are using custom kernel than there is an option ENABLE OR DISABLE PRIVACY MOD in sound section of kernel settings that might be the problem...
I'm afraid i have no idea what you are talking about.
I checked in setting>sound and there was no such option.
Am i looking the wrong place?
Sorry for being a noob
Chaitanyapatel8880 said:
If you are using custom kernel than there is an option ENABLE OR DISABLE PRIVACY MOD in sound section of kernel settings that might be the problem...
Click to expand...
Click to collapse
You're talking about boeffla kernel which is not compatible with CyanogenMods.
wtfhaxxor said:
I'm afraid i have no idea what you are talking about.
I checked in setting>sound and there was no such option.
Am i looking the wrong place?
Sorry for being a noob
Click to expand...
Click to collapse
better ask on the official cyanogen discussion threads:
10.1: http://forum.xda-developers.com/showthread.php?t=2035141
10.2: http://forum.xda-developers.com/showthread.php?t=2382573
SignetSphere said:
You're talking about boeffla kernel which is not compatible with CyanogenMods.
Click to expand...
Click to collapse
I'm using the boeffla kernel currently. Should i change kernel?
Edit: I am using Temasek's unofficial CM10.1 who suggested using this boeffla kernel in his thread.
wtfhaxxor said:
I'm using the boeffla kernel currently. Should i change kernel?
Click to expand...
Click to collapse
Then there's your problem. Like I said boeffla kernel is NOT compatible with cyanogemod so yes you better change it. You're quite lucky your device isn't bootlooping.
"Note: This kernel is only for Samsung based Jelly Bean (Android 4.1.x) roms!!! Do not install it on CM or AOSP based roms!!!
Also do NOT install it on any Samsung 4.2.x based Roms!!! You will just get a boot loop!!!"
quote from AndiP's boeffla kernel thread.
oraends sang
SignetSphere said:
Then there's your problem. Like I said boeffla kernel is NOT compatible with cyanogemod so yes you better change it. You're quite lucky your device isn't bootlooping.
"Note: This kernel is only for Samsung based Jelly Bean (Android 4.1.x) roms!!! Do not install it on CM or AOSP based roms!!!
Also do NOT install it on any Samsung 4.2.x based Roms!!! You will just get a boot loop!!!"
quote from AndiP's boeffla kernel thread.
Click to expand...
Click to collapse
What would you suggest i install? I am very new to the whole android "rom's and kernels" part of technology.
wtfhaxxor said:
What would you suggest i install? I am very new to the whole android "rom's and kernels" part of technology.
Click to expand...
Click to collapse
Upon browsing temasek's thread I see that he is indeed using a boeffla kernel but from what I can understand there is he's modifying it for it to be compatible so he made minor adjustments. I just don't know if he is still using boeffla kernel 2.x or the 3.x branch. You can however use the default kernel provided in the OP of temasek's thread and see if that can fix your problem.
http://forum.xda-developers.com/showthread.php?t=1797109
EDIT:
Your still on 10.1 when temasek's rom is already on 10.2
Download links for the 10.1 kernel are still available on the thread of temasek.
no you do not have the boeffla kernel installed (which is for stock sammy) but you have temasek kernel with boeffla sound (it's an important difference ) so the kernel is just fine for cm10.2
I think it is not possible to use a wireless headset (which is not based on bluetooth) on android, because there are no compatible drivers. I had a similiar idea: i tried to connect my external usb sound card with usb otg. on cm10.1 i was able to hear sound through it, but I was never able to switch on the optical out of the soundcard because the driver was missing. Now on cm10.2 I am even not able to hear any music with it. maybe just for a test you could try a cm10.1 based rom, because there I personally had the best results with music through otg
Edit: sorry i saw your post to late (I am really to slow in writing )
Edit2: @ OP: which rom does your friend with the g930 use?
Edit3: last one: I think the option with privacy mode is in the boeffla sound config app (sorry I cannot check it, because I do not use this kernel anymore)
Darkened_Sky said:
no you do not have the boeffla kernel installed (which is for stock sammy) but you have temasek kernel with boeffla sound (it's an important difference ) so the kernel is just fine for cm10.2
I think it is not possible to use a wireless headset (which is not based on bluetooth) on android, because there are no compatible drivers. I had a similiar idea: i tried to connect my external usb sound card with usb otg. on cm10.1 i was able to hear sound through it, but I was never able to switch on the optical out of the soundcard because the driver was missing. Now on cm10.2 I am even not able to hear any music with it. maybe just for a test you could try a cm10.1 based rom, because there I personally had the best results with music through otg
Edit: sorry i saw your post to late (I am really to slow in writing )
Edit2: @ OP: which rom does your friend with the g930 use?
Click to expand...
Click to collapse
I see... so it's a cm rom with boeffla sound. I though the OP uses the boeffla kernel itself. I had no idea since i haven't used any cyanogenmod based rom yet :laugh:
Darkened_Sky said:
no you do not have the boeffla kernel installed (which is for stock sammy) but you have temasek kernel with boeffla sound (it's an important difference ) so the kernel is just fine for cm10.2
I think it is not possible to use a wireless headset (which is not based on bluetooth) on android, because there are no compatible drivers. I had a similiar idea: i tried to connect my external usb sound card with usb otg. on cm10.1 i was able to hear sound through it, but I was never able to switch on the optical out of the soundcard because the driver was missing. Now on cm10.2 I am even not able to hear any music with it. maybe just for a test you could try a cm10.1 based rom, because there I personally had the best results with music through otg
Edit2: @ OP: which rom does your friend with the g930 use?
Edit3: last one: I think the option with privacy mode is in the boeffla sound config app (sorry I cannot check it, because I do not use this kernel anymore)
Click to expand...
Click to collapse
I am using cm10.1
I have tried using an external usb sound card and that worked just fine.
I am not sure what ROM he is using. And i also have no means of finding out.
I tried the privacy mode and it does nothing. I don't think it recognizes the headset because it is not plugged in the minijack
wtfhaxxor said:
I am using cm10.1
I have tried using an external usb sound card and that worked just fine.
I am not sure what ROM he is using. And i also have no means of finding out.
I tried the privacy mode and it does nothing. I don't think it recognizes the headset because it is not plugged in the minijack
Click to expand...
Click to collapse
Yes. As far as i know privacy mode on boeffla sound only supports headsets being plugged through the headphone jack.
bump
Has anyone ever had any success with this kind of thing?
As i stated earlier i am willing to switch roms or kernel to make this work.
Related
Since CM11 changed to CAF, here's a zip to be able to use AOSP kernels again. There's really only one note to adhere - You MUST use the kernel ramdisk from CM's kernel as there is stuff in there that is needed, so if you just flash a AOSP kernel that is built as a boot.img, IT MAY NOT BOOT. Special Note - For Franco's kernel(and others maybe) all you need is to do is use the CM(or mod his) init.d to get it working properly, using the full CM ramdisk may cause the phone not to sleep(high Android OS usage in battery stats)
Now for those that want to know the specifics, these 10 libs are what control it
Code:
hw/gralloc.default.so
hw/gralloc.msm8974.so
hw/hwcomposer.msm8974.so
hw/memtrack.msm8974.so
libexternal.so
libmemalloc.so
libmemtrack.so
liboverlay.so
libqdutils.so
libqservice.so
This is neat. Haven't tried CM11 yet, but when I do, this will be good.
Sent from my Nexus 5 using Tapatalk
So for a CAF based rom my best bet for running a third party kernel would be to let the rom boot with its ramdisk, flash this fix (Thank you by the way.)
Let that boot,
Then while in recovery flash the custom kernel?
Would it do any justice to unzip the Decaf build, replace the boot.img with a third party kernel boot.img and just flash that in recovery?
Sent from my Nexus 5 using Tapatalk 2
melbourne408 said:
So for a CAF based rom my best bet for running a third party kernel would be to let the rom boot with its ramdisk, flash this fix (Thank you by the way.)
Let that boot,
Then while in recovery flash the custom kernel?
Would it do any justice to unzip the Decaf build, replace the boot.img with a third party kernel boot.img and just flash that in recovery?
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Well it's not going to boot with 3rd party kernel so you flash the non CAF zip immediately after flashing the nightly. Then flash the custom kernel. Then reboot.
Sent from my Nexus 5 using Tapatalk
Was able to flash elemental kernel on latest cm nightly with this. Works great
Tikerz said:
Well it's not going to boot with 3rd party kernel so you flash the zip immediately after flashing the kernel. Then boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Fasho.
Fiddle time tonight!
Sent from my Nexus 5 using Tapatalk 2
melbourne408 said:
Fasho.
Fiddle time tonight!
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
You like to fiddle , your mom told you to stop.
Sent from my Nexus 5 using Tapatalk
unforgivenmercy said:
You like to fiddle , your mom told you to stop.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hahaha you got me.
Saw I, Frankenstein with the family.
Haven't felt my heart race in years. Really enjoyed it. Screw ripened potatoes.
Sent from my Nexus 5 using Tapatalk 2
anyone try with Franco yet?
dmo580 said:
anyone try with Franco yet?
Click to expand...
Click to collapse
Yes, it works. Flash CM11, flash non CAF zip, then last flash the custom kernel. You'll have to do this for each nightly until CM breaks it again.
Sent from my Nexus 5 using Tapatalk
Can someone point me to the source, where was changed to CAF? Thanks.
Tikerz said:
Yes, it works. Flash CM11, flash non CAF zip, then last flash the custom kernel. You'll have to do this for each nightly until CM breaks it again.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is volume control an issue though? I believe certain apps like Play Music or whatever fail to allow volume to be properly controlled with Franco. I will test now and report back.
Edit: Volume control works but then you lose custom color settings
Any tried this on latest nightly 29/7??
dmo580 said:
Is volume control an issue though? I believe certain apps like Play Music or whatever fail to allow volume to be properly controlled with Franco. I will test now and report back.
Edit: Volume control works but then you lose custom color settings
Click to expand...
Click to collapse
Is this why all my music and alarms were at max volume at all times before?
rockingondrums said:
Is this why all my music and alarms were at max volume at all times before?
Click to expand...
Click to collapse
Are you on Franco? Starting Nightly ~0118 or so, the conflict started due to the audio commits and as a result the volume control for media started spiraling out of control on Franco kernel. I'm not sure about alarms because I already use 6/7 volume which is pretty loud, so 7/7 probably wouldn't be noticeable unless I did a heads up comparison.
But basically, while this non-CAF patch allows you to gain control of the volume back, a lot of Franco kernel features will be broken. Basically CM and Franco commits are in conflict right now, so unless Franco decides to support CM's latest moves or someone cherry picks commits for Franco kernel, it's gonna be hard to get the best of both worlds.
dmo580 said:
Are you on Franco? Starting Nightly ~0118 or so, the conflict started due to the audio commits and as a result the volume control for media started spiraling out of control on Franco kernel. I'm not sure about alarms because I already use 6/7 volume which is pretty loud, so 7/7 probably wouldn't be noticeable unless I did a heads up comparison.
But basically, while this non-CAF patch allows you to gain control of the volume back, a lot of Franco kernel features will be broken. Basically CM and Franco commits are in conflict right now, so unless Franco decides to support CM's latest moves or someone cherry picks commits for Franco kernel, it's gonna be hard to get the best of both worlds.
Click to expand...
Click to collapse
Yeah, I was. I've got an itch to switch (again) anyway. I'm the opposite of you; I always have media at max, but my alarm fades in. It took me a few rude awakenings to figure out why.
rockingondrums said:
Yeah, I was. I've got an itch to switch (again) anyway. I'm the opposite of you; I always have media at max, but my alarm fades in. It took me a few rude awakenings to figure out why.
Click to expand...
Click to collapse
I personally just want color control. To me, features are more important so CM comes first unless there's a very similar AOSP-ROM that offers some key features I need. So I'll try to run CM and just ditch Franco if necessary Thank goodness the colors on the N5 aren't as bad as the stock N4. I just powered on my N4 and almost barfed.
dmo580 said:
I personally just want color control. To me, features are more important so CM comes first unless there's a very similar AOSP-ROM that offers some key features I need. So I'll try to run CM and just ditch Franco if necessary Thank goodness the colors on the N5 aren't as bad as the stock N4. I just powered on my N4 and almost barfed.
Click to expand...
Click to collapse
I just want to get rid of mp decision. BTW, I used this patch with Trinity's latest beta on cm nightly and audio in the alarm stream broke again, as well as torch.
One thing you can't do is just can't flash whatever kernel you want when it's built as a boot.img onto a ROM like CM, as the ramdisk for CM & AOSP are different, so you will have issues. To get them to work, decompile it, see if the kernel has specific kernel related changes in the ramdisk, decompile a CM kernel and pull the CM ramdisk, mod the ramdisk with the changes of the kernel that you want and rebuild the boot.img with the CM modded ramdisk with the kernel zImage of the kernel you want, that's basically what I do for Franco's kernel that's in my thread, it's Franco's kernel with a CM ramdisk that was modified to include all the changes he usually does.
I haven't really get the point. So if i want to use CM based rom and wanted to use AOSP kernel (non caf) i need to flash the CAF kernel and then flash the non caf zip?
Confused here
Sent from my Nexus 5 using Tapatalk
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
SaiyanGoku said:
I'm on Paranoid Android 4.0 beta 6 and would like to change to CM11. But CM11 official kernel doesn't have HDR because it uses the gproj kernel.
Can someone help me extract kernel from PA 4.0 beta 6 or post a flashable zip of kernel used in the PA rom or any HDR enabled kernel which can also support cm11?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
adfurgerson said:
http://forum.xda-developers.com/showpost.php?p=51935339&postcount=506
Click to expand...
Click to collapse
I'd suggest using the kernel you want since the beggining. Just Open up both files using winrar and delete boot.img from the GEE DU and replace it with the boot.img from the GEEB build that you like much.
Click to expand...
Click to collapse
so, does replacing the boot.img will do the job?
SaiyanGoku said:
so, does replacing the boot.img will do the job?
Click to expand...
Click to collapse
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
adfurgerson said:
It will most likely come down to whether the video drivers match or not. I think the boot.IMG contains kernal, ramdisk and zimage. They must work together is why you would swap whole boot.IMG. Maybe @jimbo77 or someone else will chime in to either confirm or let us know I am completely wrong.
Click to expand...
Click to collapse
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
jimbo77 said:
This is not going to work. We are talking about two different source codes here. The OP wants a Gproj based kernel to work with CM11 however his base (PA Beta 6) is no longer being based in Gproj sources but AOSP (or GEE for the matter) and thus making the swap incompatible with both ROMS.
I'm sorry but as you (OP) stated HDR does not work on CM becuase is based off old LG Sources (Gproj) whilest the newest ROMS or the ones being developed right now are based from newer AOSP (GEE) sources. I will not recommend doing the swap because you will have a phone that does not boot or if it boots the colors of the screen will look all funky and not al functions of the phone will work properly.
Click to expand...
Click to collapse
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
As stated earlier in the thread, No.
If you want to have HDR photos, you need to use a rom that's built on Mako/GEEB sources (like Vanir or PA or Carbon or Beanstalk or DU or 90% of the other roms on this forum.
CAF-based roms, including CM and Mokee use a completely different set of source code, so No, You Can Not add HDR to CM11 kernel.
If you want to learn about device development, sure, it might be possible. But just trying to Winzip Wizard everything into place is not going to accomplish Anything that you want it to.
SaiyanGoku said:
Ok, so i won't make the swap, I tried mounting the boot.img using ultraiso but it says "invalid or unknown image format". Even 7zip was unable to unpack it. So how do I extract kernel from it (or is it possible to add HDR to CM11 kernel)?
Click to expand...
Click to collapse
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
jimbo77 said:
Do you know something about C and kernel coding?
You will need to learn code and add it to current cm11 source for you to be able to build a kernel with HDR
Sent from my LG-gee using Tapatalk
Click to expand...
Click to collapse
i learned C and C++ when i was in school. and about kernel coding, nothing yet.
i think i'm better using CM11 directly if ever wanted to switch from PA instead of nuking my phone experimenting on non-compatible kernels.
(i don't use HDR that often as post processing takes time and there isn't that much of a difference in image quality)
I want to triple boot my Galaxy S3 with the following:
A modded stock ROM
MIUI
AOKP or CM (Which is more customizable? I'll choose that.)
How on earth do I do it?
BTW calling not working well in MIUI
I don't think you can do that at least not on i9300
At most dual boot
Press thanx if i helped you in anyway...
yoyololo said:
I want to triple boot my Galaxy S3 with the following:
A modded stock ROM
MIUI
AOKP or CM (Which is more customizable? I'll choose that.)
How on earth do I do it?
BTW calling not working well in MIUI
Click to expand...
Click to collapse
in the past there was announced triple boot for devil kernel, but it has been quite a long time since then, and there hasn't been an update for some time now as well. but it was also announced that development continues again in nfuture so maybe your wish come true
(but i am not sure if miui is even supported there)
IMO it will be quite annoying to always switch between 3 roms. atm it is even annoying for me to switch between 2 roms.
@yoyololo
I wouldn't recommend dual-booting for most people, and triple-booting will just be a nightmare. There is a risk of permanently damaging your phone if done incorrectly.
RazorMC said:
@yoyololo
I wouldn't recommend dual-booting for most people, and triple-booting will just be a nightmare. There is a risk of permanently damaging your phone if done incorrectly.
Click to expand...
Click to collapse
So My final decision is Stock + AOKP
Possible?
So I saw this kernal called "SiyahKernel" that lets you dual-boot... How do I use it?
yoyololo said:
So I saw this kernal called "SiyahKernel" that lets you dual-boot... How do I use it?
Click to expand...
Click to collapse
Not siyah.Googy max would be necessary if you want to use the latest roms.
Try following instructions on the thread or better watch some videos for that on youtube
Press thanx if i helped you in anyway...
kunal1540 said:
Not siyah.Googy max would be necessary if you want to use the latest roms.
Try following instructions on the thread or better watch some videos for that on youtube
Press thanx if i helped you in anyway...
Click to expand...
Click to collapse
I've used this "Googy2-max"/"Googy-max2" (I forgot the name). I want to use SiyahMod for quadboot (Stock, AOKP, CM, PA, I know I can just use PAC, but it WON'T WORK) but it's not compatible. I tried...
yoyololo said:
So My final decision is Stock + AOKP
Possible?
Click to expand...
Click to collapse
Like @kunal1540 said, use GoogyMax kernel.
This will work for stock and aokp, but check which versions are supported. It is not possible to just use any version of the ROM directly. You need to check which ones will work from kernel's instructions.
RazorMC said:
Like @kunal1540 said, use GoogyMax kernel.
This will work for stock and aokp, but check which versions are supported. It is not possible to just use any version of the ROM directly. You need to check which ones will work from kernel's instructions.
Click to expand...
Click to collapse
Done it
Nice
Hi All,
I've got my S2 (i9100) Dual Booting, between KitKat and Lollipop.... and whilst the KitKat is just fine, the guide said Lollipop will boot with Apolo Kernel.
Well so far I've downloaded 2x Lollipop kernels from Apolo, and neither of them boot it up....
So, are there any other Kernels out there that are for Android 5.x (Lollipop) please, and if so, where...??
Thanks, Lister
Lister Of Smeg said:
Hi All,
I've got my S2 (i9100) Dual Booting, between KitKat and Lollipop.... and whilst the KitKat is just fine, the guide said Lollipop will boot with Apolo Kernel.
Well so far I've downloaded 2x Lollipop kernels from Apolo, and neither of them boot it up....
So, are there any other Kernels out there that are for Android 5.x (Lollipop) please, and if so, where...??
Thanks, Lister
Click to expand...
Click to collapse
Only apolo kernel currently support lollipop. Gustavo kernel will start supporting lollipop soon (I think).
Make sure you download the proper version of Apolo kernel, which is 8.0 beta3 for CM12, otherwise it won't work. Try Apolo-8.0_Beta3_Regular-TWRP.zip and try running the kernel cleaning script before installing Apolo.
Hi @gsstudios,
Thank you for your reply, I look forward to any updates regarding this kernel... As there is only is only one out there at the moment, as you've also mentioned. Are you involved in this Gustavo kernel??
Also, may I pick your brains over something that I posted here, as I saw your reply on a similar nature here....
(sorry, work has crept in... so I'll update this post a bit later with current situation)
Many thanks, Lister
gsstudios said:
Only apolo kernel currently support lollipop. Gustavo kernel will start supporting lollipop soon (I think).
Click to expand...
Click to collapse
Hi @acydwarp,
Yeah i followed the Apolo thread, and selected the (branch 8) link, however it took me to like about 6x different files.... So I tried the one i thought was the most normal one... ie: Regular.
Apolo-8.0_Beta3_Regular-TWRP.zip and this is the one I am having problems with. After flashing this, it won't boot Lollipop for me. I've also tried the LITE version too, and that't not worked either.
What's this "Cleaning script" all about, how do I find it, and what does it do...? I've seen reference to it mentioned in other threads too, is it the same as RomNuker2 or something similar to that....??
Thanks, Lister
acydwarp said:
Make sure you download the proper version of Apolo kernel, which is 8.0 beta3 for CM12, otherwise it won't work. Try Apolo-8.0_Beta3_Regular-TWRP.zip and try running the kernel cleaning script before installing Apolo.
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi @acydwarp,
Yeah i followed the Apolo thread, and selected the (branch 8) link, however it took me to like about 6x different files.... So I tried the one i thought was the most normal one... ie: Regular.
Apolo-8.0_Beta3_Regular-TWRP.zip and this is the one I am having problems with. After flashing this, it won't boot Lollipop for me. I've also tried the LITE version too, and that't not worked either.
What's this "Cleaning script" all about, how do I find it, and what does it do...? I've seen reference to it mentioned in other threads too, is it the same as RomNuker2 or something similar to that....??
Thanks, Lister
Click to expand...
Click to collapse
You mean kernel cleaning script by hawker? It deletes left over files from kernels and deletes the current kernel to prevent issues from occurring. You can find the kernel cleaning script by using google or you can go to the Gustavo kernel thread and there will be a link that will take you to download the script. Cheers.
What cm12 beta build are you on? The latest builds are experimental and the builds before that are buggy too. This could have stopped compatibility with apolo kernel. Also, Omni 5.0 for our device is facing serious problems with this kernel. Avoid it until this problem is fixed!
Hi,
For quite sometime now I have been using Samsung ROMs like MD4, QS-KK, etc
Recently I tried switching to lollipop ROMs - temasek and others. However, what I noticed is that the sound volume for ringtone, notifications, and alarm is quite low; not only temasek but others as well
Can you please help me understand how it can be raised? I had tried the latest Viper4Android but in vain.. If there is any other mod, I am using Dolby on MD4, then I will be very happy to try that
Thanks
If it is not a hardware malfunction or dirt in the speaker than you could try to install custom kernel, ie. Boeffla and rise master volume via Boeffla config app.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
srv.abhishek said:
Hi,
For quite sometime now I have been using Samsung ROMs like MD4, QS-KK, etc
Recently I tried switching to lollipop ROMs - temasek and others. However, what I noticed is that the sound volume for ringtone, notifications, and alarm is quite low; not only temasek but others as well
Can you please help me understand how it can be raised? I had tried the latest Viper4Android but in vain.. If there is any other mod, I am using Dolby on MD4, then I will be very happy to try that
Thanks
Click to expand...
Click to collapse
You will have it on all Lollipop CM based rom's.Install V4A or Boeffla Sound App and try it
Sent from my BlissPop 3.2 ✌
KeTuRr74 said:
You will have it on all Lollipop CM based rom's.Install V4A or Boeffla Sound App and try it
Sent from my BlissPop 3.2 ✌
Click to expand...
Click to collapse
Thanks. Have you tried V4A? I tried it on cm 12.1 by justArchi yesterday but every time I open the app, it asks for driver installation irrespective of the fact that drivers were already installed last time.. also xTra loud doesn't seem to be effective. .
Sent from my GT-I9300 using XDA Free mobile app
srv.abhishek said:
Thanks. Have you tried V4A? I tried it on cm 12.1 by justArchi yesterday but every time I open the app, it asks for driver installation irrespective of the fact that drivers were already installed last time.. also xTra loud doesn't seem to be effective. .
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
You need to set the SELinux to "Permissive" and installs the drivers of V4A and it will work
Sent from my BlissPop 3.2 ✌
You can also modify the levels in /system/etc/sound/m0