yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Android Development] tenshi_xp:
Not all phones can handle 1.2GHz, and is not related to device model.

A working V for Fred and me is

{1200000, 1198080, 0x0005019C, [B]0x3A, 0xDF[/B], 100, 100},

Yanpol V is

{1200000, 1200000, ARM_MAX_OPP, NOCHG, 0x741, SET_PLL, 0x0004017D, SET_VOLT, 0x0C, [B]0x3F, 0xFF[/B]},

and cocafe V is

{1200000, 1198080, 0x0005019C, [B]0x35, 0x8F[/B], 100, 100},

also i like more 1.15Ghz instead of 1.2Ghz
[Galaxy S III Mini Android Development] grinder777:
You compile this kernel from Android-Andi's sources? Why don't you use the installer of Anykernel as well? It will keep the users ramdisk...

Have fun!
[Galaxy S III Mini Android Development] moonryder:
no he uses the kernel from CM11 source, that´s the reason why camera on slim isn´t working with it.

You can download the modified CroPol kernel for SlimKAT HERE

Have fun!
[Galaxy S III Mini Android Development] 1N4148:
No. I've compiled the kernel from github.com/yanpol199 with the latest LiveOPP code merged from CoCafe. As I first made this kernel for my own testing purposes, a simple install script was enough for me. I will take a look into the installer from Anykernel or Agni, they also patch the ramdisk.
[Galaxy S III Mini Android Development] moonryder:
oh sorry for my lack of knowledge :angel:
[Galaxy S III Mini Android Development] grinder777:
Ah, cropol... Does it support f2fs?
[Galaxy S III Mini Android Development] grinder777:
tenshi_xp updated his kernel

http://www.mediafire.com/download/h3ccmwf67b1ux3x/GT-I8190-KERNEL_2sc.zip

- add LiveOpp updated to 2.0.2 by [MENTION=4832589]cocafe[/MENTION]

Frecuencies from 100Mhz to 1.2Ghz, 200Mhz-1Ghz by default

- Single platform RTC driver by golden-guy

Notes

This is an Aroma-installer provided by tenshi_xp

You can select if your system is ext4 or f2fs to choose the right kernel.

NovaThorSettings will be installed as well.

If you have mount/unmount usb in pc, dissable sounds.
[Galaxy S III Mini Android Development] ChronoMonochrome:
It's not always true. On ace 2, for some strange reason, 0x39 is more stable than 0x3f(!). [MENTION=5840412]ace2nutzer[/MENTION] first user who found it.
[Galaxy S III Mini Android Development] grinder777:
tenshi_xp updatee his kernel

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] grinder777:
tenshi_xp made an update for us :)

Thanks a lot!!!

Kernel in Ofast + JustArchiV3 + Linaro GCC 4.9

Flashable kernel
[Galaxy S III Mini Android Development] Android_Mailson:
Download now!
[Galaxy S III Mini Android Development] ChronoMonochrome:
Can anyone make me a favor? :) Upload please dump of any s3 mini kernel. I mean kernel that stored in /dev/block/mmcblk0p20. For me very interesting Ramdisk part of it :) I want to know if I can make dedicated recovery partition for Galaxy Ace 2. Thanks in advance!

Regards,
[Galaxy S III Mini Android Development] mauam:
How can I do that!!!?
[Galaxy S III Mini Android Development] ChronoMonochrome:
dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img
[Galaxy S III Mini Android Development] mauam:
Ok, is from NF latest kernel (1/11/14).
[Galaxy S III Mini Android Development] ChronoMonochrome:
Thanks, but ramdisk that I extracted from this kernel, is empty(that's my fault, not your). :( Is ramdisk stored somewhere else? :confused: I thought it is in kernel...
[Galaxy S III Mini Android Development] mauam:
Don't know too!!! If you want I cant extract from other kernel, cropol or [MENTION=4198570]tenshi_xp[/MENTION], but I still don't know wich block is!!!
[Galaxy S III Mini Android Development] ChronoMonochrome:
No, it doesn't matter which kernel is extracted. Probably, my script for extracting ramdisk is not compatible with these kernels(my bad, I forgot that's usually compressed with GZIP) - I think I'll find how to extract ramdisk from this.
[Galaxy S III Mini Android Development] tenshi_xp:
My kernel + ramdisc, this tool work for me.
[Galaxy S III Mini Android Development] ChronoMonochrome:
Thanks! That looks very helpful for me :)

UPD. now I can thank you again :) I have not found in this ramdisk any reference to recovery, but I finally understand how to make dedicated recovery partition :) I had to do some changes in my ramdisk, and got it working :)
[Galaxy S III Mini Android Development] grinder777:
Another update from tenshi-xp

Thanx daniel!

Have fun!

Gesendet von meinem GT-I8190 mit Tapatalk
[Galaxy S III Mini Android Development] grinder777:
Updated Novafusion kernel

https://app.box.com/s/9yox0u7p5wekdmbe416l

- Switch to single platform RTC driver - AB500 (clock freeze fix)

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] grinder777:
Tenshi_xp made updated kernel-pack

Flashable kernelinstaller give you have 3 options

1st.- Normal kernel*1

2nd.- Kenel with CPU OC + GPU OC*2

3rd.- Kernel wirh CPU OC + GPU OC + ABBamp Sound*3

*1 For normal users.

*2 For users who like something more powerful without the connect/disconnect USB on pc, deleted 100-300-500-700-900Mhz frequencies for friendly frequency scaling.

*3 For users who like all changes, deleted 100-300-500-700-900Mhz frequencies for friendly frequency scaling. this is the kernel is included in PAC release
[Galaxy S III Mini Android Development] 1N4148:
If anyone likes to test my kernel based on CroPol with some modifications from CoCafe (LiveOPP), feel free to test...

Sources: https://github.com/1N4148/yanpol/tree/cocafe
[Galaxy S III Mini Android Development] mauam:
Before try I want to know which mods you did!!!:)
[Galaxy S III Mini Android Development] 1N4148:
These ones: https://github.com/1N4148/yanpol/commits/master or in short: added zzmoove governor, disabled usecase governor and screen off limiter, added LiveOPP from CoCafe with dynamic voltages based upon device specific avs data.

Don't know if this make OC more stable. I can undervolt my device to 700uV@1200MHz. Either it is a magically device or there's something wrong in the whole LiveOPP logic :confused:
[Galaxy S III Mini Android Development] mauam:
Ok, interesting. So no screen off limits (that's it?) & can you explain me what's zzmoove governor & which is features. I feel lazy today:)
[Galaxy S III Mini Android Development] 1N4148:
The main reason why I've posted here is the new LiveOPP for overclocking :D

Screen off etc. are only minor changes for my personal preferences ;)
[Galaxy S III Mini Android Development] mauam:
But kernel hasn't scoff limits right, I checker sys/kernel & no scroff file. Ok, seems smoother than original cropol. Now, I need to search for zzmoove governor & leran what it is!! Thanks bro. BTW make your own thread (again):laugh:

---------- Post added at 10:38 PM ---------- Previous post was at 10:29 PM ----------

There is more zzmoove versions from the original thread here

ZZMoove Governor v0.1

(post from 18th December 2012, 10:27 PM)

Why that “zzmoove” governor and how it works:

I thought it were pretty cool to have one of my favorite governors back from the old SGS1-days on my actual device, so i decided to take the sources and give that a try on top of boeffla kernel. It worked well so this is now the result of that experiment.

More about the internals:

Basically this is the ported SGS1 version of the well known "smoove" governor from the good old midnight kernel from Michael Weingaertner (mialwe) with a modified CPU hotplug implementation of the ktoonservative governor from ktoonesz. The original implementation from ktoonesz worked well but I observed that on idle most of the time only one cpu was going to sleep. Well that was not enough for me so I made a modification to put the other cpu's also to sleep (except cpu0). That means that this governor uses more often only one cpu on idle and as a consequence of that it needs less energy. Depending on System load and governor settings all 4 cores will be instantly up again if it is needed.

In short:

So what you can expect now from this thingy is a battery-friendly behaving hotplug conservative governor which

uses a frequency lookup table for faster upscaling (so called "smooth scaling") So this is more a energy-safer than a performer.

Tuneables/Defaults:

Sampling Rate (default=2) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/sampling_rate

Sampling Down Factor (default=4) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/sampling_down_factor

Up Threshold (default=70) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold

Up Threshold Hotplug (default=68) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/up_threshold_hotplug

Down Threshold (default=52) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold

Down Threshold Hotplug (default=55) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/down_threshold_hotplug

Ignore Nice Load (default=0) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/ignore_nice_load

Freqency Step (default=5) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/freq_step

Smooth Up (default=75) tuneable: /sys/devices/system/cpu/cpufreq/zzmoove/smooth_up
[Galaxy S III Mini Android Development] 1N4148:
We're on 1.0 beta 2 ;)

http://xdaforums.com/galaxy-s3/development/info-cpu-governor-zzmoove-t2326544
[Galaxy S III Mini Android Development] albertusac:
What do you mean? New governor?
[Galaxy S III Mini Android Development] mauam:
Yeah! ZZmoove governor. I'm using it with sioplus 200-1200 & feels great:cool:

---------- Post added at 05:10 PM ---------- Previous post was at 04:43 PM ----------

No one freaking reboot at 1200, testing it since yesterday, games, sms, calls, wifi, etc:cool:
[Galaxy S III Mini Android Development] exwan:
Zzmoove + yank batery extreme is the best combo in my s3. Happy to see the governer ported here in s3 mini.
[Galaxy S III Mini Android Development] grinder777:
Tenshi_xp updated his kernel:

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] Balino:
We are on the right way!!! My device handled 1.2 GHz for 10 minutes... I couldn't even set it with other kernels! But Still not usable for me at this clock speed. Thank you for the update.
[Galaxy S III Mini Android Development] ChronoMonochrome:
Have anyone tried following settings?

IDX | CLK | PLL | VDD | VBB
0 | 199680 | 0x0005011a | 600000uV 0x00 | 0xbd
1 | 299520 | 0x00050127 | 600000uV 0x00 | 0xbd
2 | 399360 | 0x00050134 | 600000uV 0x00 | 0xbd
3 | 499200 | 0x00050141 | 600000uV 0x00 | 0xbd
4 | 599040 | 0x0005014e | 600000uV 0x00 | 0xbd
5 | 698880 | 0x0005015b | 600000uV 0x00 | 0xbd
6 | 798720 | 0x00050168 | 600000uV 0x00 | 0xbd
7 | 898560 | 0x00050175 | 600000uV 0x00 | 0xbd
8 | 998400 | 0x00050182 | 600000uV 0x00 | 0xbd
9 | 1098240 | 0x0005018f | 600000uV 0x00 | 0xcd
10 | 1198080 | 0x0005019c | 600000uV 0x00 | 0xff

Instead of vbbx=0xbd set VBB_50_OPP from your avs file.

( from https://github.com/ace2nutzer/Samsung_STE_Kernel/commit/ae4cd9dd16fb92a744f7d2b39e1664762bd48713 )
[Galaxy S III Mini Android Development] brooker88:
I'm using tenshis ROM and governor keeps reverting back to on demand, anyone else have this problem? I can't change it
[Galaxy S III Mini Android Development] grinder777:
Did you check at Pac-Performance settings to apply after boot?

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] Roji:
It is working true mate.. Really amazing battery life at 1.2Ghz.. Kudos [MENTION=4996458]1N4148[/MENTION] ..
[Galaxy S III Mini Android Development] Balino:
I couldn't figure out how to undervolt your kernel yet... No data in step_file... How can I do?
[Galaxy S III Mini Android Development] 1N4148:
Which step file? My kernel only uses 11 steps (0-10).
[Galaxy S III Mini Android Development] Balino:
Every step_file is empty... Maybe due to the dinamic voltages you introduced?
[Galaxy S III Mini Android Development] 1N4148:
Hm, not on mine. I'll have to look into.
[Galaxy S III Mini Android Development] Balino:
Sorry dude, my bad... I was looking at the last four which are unused... Thank you :)
[Galaxy S III Mini Android Development] Balino:
Anyway where can I find the GPU voltage? To undervolt it..
[Galaxy S III Mini Android Development] 1N4148:
You cannot, there's no sysctl interface for changing gpu voltages on the fly at the moment. Therefore I tweaked it in the sources for my own device.
[Galaxy S III Mini Android Development] Balino:
Ah ok .. Thank you for replies :)
[Galaxy S III Mini Android Development] 1N4148:
You can test my personal kernel if it fits your needs :) cpu uc'd a bit, gpu at 320/640 with uv at [MENTION=2539186]320[/MENTION]
[Galaxy S III Mini Android Development] Balino:
Where can I find it :)
[Galaxy S III Mini Android Development] mauam:
Here you go:)
[Galaxy S III Mini Android Development] Balino:
I'm already using it so :)
[Galaxy S III Mini Android Development] 1N4148:
gpu can be already uv'd/ov'd with

echo "[idx] vape=[vape]" > /sys/kernel/mali/mali_dvfs_config

and with

cat /sys/kernel/mali/mali_dvfs_config

you can see the freq table and the Vape in hex
[Galaxy S III Mini Android Development] Balino:
Great news :)
[Galaxy S III Mini Android Development] 1N4148:
Stay tuned, doesn't run 'til now :confused:

In the meanwhile, you can do the same like I did (I've hardcoded it into my personal daily driver kernel):

echo "3 vape=0x20" >/sys/kernel/mali/mali_dvfs_config
echo "17 vape=0x30" >/sys/kernel/mali/mali_dvfs_config
echo "idx=3" >/sys/kernel/mali/mali_boost_low
echo "idx=17" >/sys/kernel/mali/mali_boost_high

So you get a 320 step for low/normal untilization and a 640 for high utilization
[Galaxy S III Mini Android Development] Balino:
All my voltages are set to 60000 and it seems to run just fine O.o at 1,2ghz too... Is it possible???
[Galaxy S III Mini Android Development] 1N4148:
Yes, I discovered phenomenon this two weeks ago. I don't believe the core is really running at this voltage but I cannot check. Even the regulator debug output says the same. And only with the raised bias voltages it cannot be explained. I assume there's another mechanism kicking in.
[Galaxy S III Mini Android Development] 1N4148:
A new kernel is in the oven for baking ;) Reworked the gpu code a little bit, now we've more than 2 steps so the gpu freq can also scale like we know from cpu.

Possible gpu clocks:

idx freq rawfreq clkpll Vape
0 128000 128000 0x01030114 1050000 0x1c
1 192000 192000 0x0103011e 1100000 0x20
2 256000 256000 0x01030128 1100000 0x20
3 320000 320000 0x01030132 1200000 0x28
4 384000 384000 0x0103013c 1200000 0x28
5 448000 448000 0x01030146 1250000 0x2c
6 512000 512000 0x01030150 1250000 0x2c
7 576000 576000 0x0103015a 1300000 0x30
8 640000 640000 0x01030164 1300000 0x30
9 704000 704000 0x0103016e 1362500 0x35

Kernel boots up with min@128 & max@384

To change the min & max frequencies type into shell:

Min. frequency

echo [frequency] > /sys/kernel/mali/mali_boost_low

Max. frequency

echo [frequency] > /sys/kernel/mali/mali_boost_high

Feedback please, especially for graphics ;)
[Galaxy S III Mini Android Development] Balino:
Downloading :)
[Galaxy S III Mini Android Development] 1N4148:
New builds...

2 new builds available. The first one is the same like announced with the new gpu scaling driver, the second one is a build with the old wifi driver before JB2 update from Samsung. Only for people who have problems with wifi connected but no data. Maybe if I find the time I'll modify the installer so you can choose between new & old wifi drivers.

Enjoy & feedback please
[Galaxy S III Mini Android Development] grinder777:
Thanks a lot for your nice work!

I put it all together here

http://xdaforums.com/showthread.php?p=54024791

please PM if you like something to be changed or added.

Have fun!
[Galaxy S III Mini Android Development] grinder777:
Running well here, great to see you also have ZRam enabled! Great job!!!

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] 1N4148:
Even if I enable zram on my device, it won't swap anything out. Maybe I've tuned my LMK too much :D

Currently trying to get lz4 for zram/zcache running
[Galaxy S III Mini Android Development] grinder777:
If I just type 'free' at terminal it shows 148Mb swap...

I did not enable nothing, same as at tenshi-xp's kernels :)

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] 1N4148:
Yup, I've forgot my /data/local/userinit.sh. There I disable zram for me as I don't see any benefit ;) But even with zram on, my device won't swap much :)
[Galaxy S III Mini Android Development] grinder777:
Could you post the line to disable ZRam? Just in case someone want to...

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] 1N4148:
My /data/local/userinit.sh

#!/system/bin/sh

# Disable zRam
swapoff /dev/block/zram0;

# Set scheduler
busybox echo "zen" > /sys/block/mmcblk0/queue/scheduler;
busybox echo "zen" > /sys/block/mmcblk1/queue/scheduler;

# Tweak read ahead values
busybox echo "256" > /sys/block/mmcblk0/queue/read_ahead_kb;
busybox echo "512" > /sys/block/mmcblk1/queue/read_ahead_kb;

# switch governor
busybox echo "zzmoove" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor;
busybox echo "7" > /sys/devices/system/cpu/cpufreq/zzmoove/profile_number;

# Tweak gpu frequencies
busybox echo "256000" > /sys/kernel/mali/mali_boost_low;
busybox echo "512000" > /sys/kernel/mali/mali_boost_high;

# Disable BLN
busybox echo "0" > /sys/class/misc/backlightnotification/enabled;

# Set deepest sleep state to 4
busybox echo "4" > /d/cpuidle/deepest_state;
[Galaxy S III Mini Android Development] 1N4148:
New version is up

Now with stats for GPU frequency in /sys/kernel/mali/mali_stats

For everyone who likes to see how often his GPU was at which frequency. Stats shown as: Frequency, Count, % of total time.

OPP50 is half of lowest clock if GPU is active but idle.

Wifi driver selection in installer isn't completed, yet. For now it will always install current Wifi driver.
[Galaxy S III Mini Android Development] Sn0wdune:
Hey [MENTION=4996458]1N4148[/MENTION]!

Any news on if ever 1.2GHz will ever work on my device? :p

The post you made about being "rockstable" a few weeks ago, I saw the values had changed in that file and my values were totally different from that.

It's a long shot and I don't mean to come across as being cheeky but do you think you could provide a build for the people who are having problems with applying 1.2GHz please?

I know this question may of been somewhat answered in the past but with the amazing knowledge that you possess (;)), I'm sure you can be successful! :p

Again, If I come across as cheeky or even selfish, Sorry! ;)
[Galaxy S III Mini Android Development] 1N4148:
There's nothing I can do in the kernel for you. The only thing you can do is to try different values for Vbb at arm_step10 (should be the 1.2GHz step if I remember correctly). Your defaults for Vbbx are 0x0b, so in theory it should run at 1.2 with Vbbx = 0xbf, but it depends on the chip. Not all can run at 1.2
[Galaxy S III Mini Android Development] 1N4148:
Introducing LiveOPP 3.0 beta

A new build has left my builder box...

Based upon the latest LiveOPP from CoCafe I've reworked the automatic calibration a little bit. Based on the AVS data of your device, Varm & Vbb is recalculated. At lower frequencies Varm is lowered, at 1100/1200 Vbb is raised by 100mV (or only 50mV if already near max). Maybe this improves to ability to overclock a little bit more for some devices. [MENTION=5069880]Sn0wdune[/MENTION]: Your milage may vary.

Feel free to test & report

The next change is in my head: Automatic voltage calculation for GPU
[Galaxy S III Mini Android Development] grinder777:
Sorry, this one is not working for me. It boots up, but after one minute it will reboot the device... :-/

I just went back to 29th release and it seems - while booting (fast) - the system switched back to dalvik..? ...was on ART before...
[Galaxy S III Mini Android Development] meduza:
[MENTION=4996458]1N4148[/MENTION],

I like your kernel a lot - thank you! Unfortunately BT is not working correct when using the kernel with android-andi`s SLIM ROM :( It`s the same with cropol. Do you think, something could be done about this inconvenience...?

m.
[Galaxy S III Mini Android Development] 1N4148:
Some more details? Max. cpu freq? Can you send me the output from /sys/kernel/liveopp?
[Galaxy S III Mini Android Development] grinder777:
Sorry, don't have much details...

I just set max-freq to 1100 and governor to zzmove at previous kernel. But I don't know if this values where overtaken by flashing the new build. Anything else were default.

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] 1N4148:
I need the output from /sys/kernel/liveopp/arm_summary and /sys/kernel/liveopp/prcmu_avs
[Galaxy S III Mini Android Development] grinder777:
This files are not present...
[Galaxy S III Mini Android Development] 1N4148:
They must be there for sure!
[Galaxy S III Mini Android Development] grinder777:
Nope... I'm back at 29th build..?

'

Gesendet von meinem GT-I8190 mit Tapatalk 2
[Galaxy S III Mini Android Development] 1N4148:
They are only there in the newest version. Can you send me /d/prcmu/avs instead? But I also need the output from the newer version, maybe the recalculated voltages doesn't match.
[Galaxy S III Mini Android Development] 1N4148:
1N4148 Kernel

Moved to a own thread: http://xdaforums.com/galaxy-s3-mini/orig-development/1n4148-kernel-i8190-cpu-oc-gpu-oc-t2959201
[Galaxy S III Mini Android Development] dat7476:
excellent work, not been using long but seems stable and no 1ghz bug so im happy.
[Galaxy S III Mini Android Development] grinder777:
Here I've extracted Lollipop-kernels for you:

Android-Andis-LP-kernel 2015-07-23

Aroma-installer,

works fine with Novafusion-ROMs

and

Novafusion-LP-kernel 2015-07-23

to switch back

Have fun!
[Galaxy S III Mini Android Development] aymelis:
Kernel damaged hardware

Guys, I thought I would share my experience with NF-kernel 20141101.

I acquired a S3 mini but discovered it did not recognize any of my SD cards. Tried many things on the card itself (chkdsk, FAT, FAT32, exFAT, ...). Nothing worked despite the card being recognized by my laptop and my S4. I know there are some phone/SD card ncompatibilities. But this is usually related to high capacity or high speed cards. Mine is only 2GB.

I then tried many ROMs : various stock versions, then custom ones. I ended up with the excellent DmodV6 (XXANF3) and started to try many kernels, stock and custom. I ended up with this NF-kernel 20141101.

OK I did not spend much time reading the associated thread about issues, etc... All installed ok, but when I restarted the phone I was very surprised to discover an unknown screen in red letters:

(sorry if blur). Then I took the battery off to start reflashing with Odin. When connecting the

USB cable to the PC I got a scary "USB power surge" alert from Windows... And Odin did not recognize the phone anymore. I had to try several USB ports, the 4th one accepted to install the drivers and got Odin connected, which allowed me to flash the latest stock ROM back.

BUT at each reboot I now get this screen:

I believe a short cut or something occured due to installing this kernel. Any idea which damage could generate such a splash screen ?

So, if you plan to install it (without the associated Carbon ROM 4.4.4) be aware of a potential hardware damage to your phone...

regards

Edit: could fix this crappy boot screen thanks to mauam here.
[Galaxy S III Mini Android Development] PRO.B:
make sure you know exactly what you are doing!

[IMG="10/10"]http://a136.idata.over-blog.com/0/13/56/66/Photos-22/images-copie-65.jpg[/IMG]
[Galaxy S III Mini Android Development] ZRK_NanDRD:
Hi guys, I've flashed omni-5.1.1-20151103-golden-HOMEMADE.zip on my S3 mini & as expected the fm radio was gone. I then installed the Spirit fm 2.apk hoping the Radio would work but,when I opened the Radio it said something like *Try getting a kernel that supports radio api*

Should I flash this custom kernel-CM_20150723.zip golden mentioned above or must I flash the Jb 4.1.3 stock kernel to get the radio working with the 5.1.1 omni rom?