yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] mad_ady:
Ok, I think I have two more problems:

1. I managed to pack the boot.img with ramdisk_boeffla, but it won't boot when I flash it. I built it like this:

echo "Compressing ramdisk"
cd "$SRC/ramdisk_boeffla";
find . | cpio -oc | gzip -c -9 > ../../boot.img-ramdisk.cpio.gz
cd "../.."

echo "Build boot.img"
mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.cpio.gz -o "$DST/boot.img"

The resulting file looks ok (about the same size as the one shipped by Lord Boeffla). Do I need to add extra parameters to mkbootimg - things like cmdline?

2. I noticed the modules I get are huge compared to what is shipped with the official release. For example:

Original:

adrianp@frost:~/development/boeffla/boeffla-kernel-2.4/system/lib/modules$ ls -l asix.ko
-rw-r--r-- 1 adrianp adrianp 23040 Oct 22 12:07 asix.ko
adrianp@frost:~/development/boeffla/boeffla-kernel-2.4/system/lib/modules$ file asix.ko
asix.ko: ELF 32-bit LSB relocatable, ARM, EABI5 version 1 (SYSV), BuildID[sha1]=cfc2589691beb9375b0dff09298103622e26eb6e, not stripped

Compiled:

adrianp@frost:~/development/boeffla/zip-base/system/lib/modules$ ls -l asix.ko
-rw-r--r-- 1 adrianp adrianp 222704 Nov 29 10:33 asix.ko
adrianp@frost:~/development/boeffla/zip-base/system/lib/modules$ file asix.ko
asix.ko: ELF 32-bit LSB relocatable, ARM, EABI5 version 1 (SYSV), BuildID[sha1]=c6fe3b952834d081dbfac61d961ab34d6e181218, not stripped

All my modules are about 10 times larger than the originals. I thought it was because they were not stripped, but it isn't so.

I didn't run make modules nor make modules_install. Maybe I'll try that.
[Galaxy S III Android Development] Code124Y:
Hi Andi,

can i know what the smallest value and highest value of hotplag_rq can hold under PegasusQ tunable?

im trying it on something...
[Galaxy S III Android Development] andip71:
I need to check in the code when I am at my pc again, can take a while... Weekend ?
[Galaxy S III Android Development] racky29:
Im using Mahdi Rom 2.9 final

And boeffla 2.4 b8 cm11 ng

But some are saying use the Omnirom boeffla instead

But this cm11 one seems to work just fine

Is there any reason i should use the omnirom version instead

I would of thought if I'm using the wrong one i would see some negative effects

Or it wouldnt boot at all.

Anyone got a positve answer here. It looks like looking through the thread some use cm11 and some omnirom kernels. Im confused
[Galaxy S III Android Development] Der-Knuffi:
I'm leaving boeffla kernel and my S3 off to a S4.

But as I know the people here in the thread really appreciate good kernels (and the best is undoubtably Boeffla kernel!), I just wanted to know if someone of you can give me a hint to a really good S4 kernel for CarbonRom (want to stay with the ROM as it is the best imho).
[Galaxy S III Android Development] ste22032:
Hi Lord Boeffla, what do you recommend to test if the undervolt level is safe for a device? I mean, something that allows you to avoid, or reduce the probability, of freezes, reboots, etc... I know that AnTuTu has a built-in stability test, but maybe a daily use test is better.. What do you think?
[Galaxy S III Android Development] mad_ady:
Good news - I managed to compile and boot my kernel. I was messing up the boot.img file and also the ramdisk. In the end, for future reference here are the steps I took to build a custom kernel (I know I will forget again in 6 months and will have to search again the forum - [MENTION=947981]Lord Boeffla[/MENTION]: Maybe you could add these steps to your FAQ?):

git clone https://github.com/andip71/boeffla-kernel-omnirom-s3.git
cd boeffla-kernel-omnirom-s3
git checkout ng_boeffla
make boeffla_defconfig
#get the USB keyboard patch and apply it
wget https://raw.githubusercontent.com/pelya/android-keyboard-gadget/master/kernel-3.1.patch
patch -p1 < kernel-3.1.patch
#manual steps - fix the Makefile patch
make menuconfig
#change the release string
#apply ZaneZam's patches to fix for correct svn version (by hand): https://github.com/zanezam/boeffla-kernel-cm-s3/commit/20e9c1f878bf7e1a4e05d29b4f9a21bf8d63c22f
make
#Unpack an existing Boeffla-kernel update and put it in zip-base/
#Take the root.bin, copy it to ArchiKitchen and use the kitchen's features to unpack it.
#Copy the unpacked items of the root.bin to kernel/
run prepareZip.sh
#profit

and prepareZip.sh is this script:

#!/bin/bash
DST=zip-base
SRC=boeffla-kernel-omnirom-s3/

echo "Copying kernel zImage"
cp "$SRC/arch/arm/boot/zImage" "kernel/boot.img-zImage"

#echo "Compressing ramdisk"
#cd "$SRC/ramdisk_boeffla";
#find . | cpio -oc | gzip -c -9 > ../../kernel/boot.img-ramdisk.gz
#cd "../../kernel"
cd kernel

echo "Build boot.img"

mkbootimg --kernel boot.img-zImage --ramdisk boot.img-ramdisk.gz --cmdline "`cat boot.img-cmdline`" --base "`cat boot.img-base`" \
--pagesize "`cat boot.img-pagesize`" --kernel_offset "`cat boot.img-kerneloff`" --ramdisk_offset "`cat boot.img-ramdiskoff`" --tags_offset "`cat boot.img-tagsoff`" -o "../$DST/boot.img"
cd ..

echo "Copying modules"
#make modules_install INSTALL_MOD_PATH="$DST/modules"
find "$SRC" -name "*.ko" -exec cp '{}' "$DST/system/lib/modules" ';'

echo "zip the package"
rm -f "Boeffla-Kernel-Custom.zip"
cd "$DST"
zip -r9 ../Boeffla-Kernel-Custom.zip *

Now the kernel boots fine and loads the oversized modules. The USB keyboard/mouse combo I patched in works fine (https://play.google.com/store/apps/details?id=remote.hid.keyboard.client&hl=en).

Now, I wonder how I can trim down the modules - they are still 10 times larger than the ones Lord Boeffla supplies, and I don't know what I did differently than him...
[Galaxy S III Android Development] flither:
I made this guide some time ago, you may try this one. It's little bit complicated, but you should get the overall meaning ;) Worked perfectly for me :good:
[Galaxy S III Android Development] AhmadMarikar:
Can someone help me out? Wanna try Slimkat and I was wondering if I could use this kernel will be compatible on that ROM?
[Galaxy S III Android Development] BFMSAND:
Will boeffla kernel be updated to work with 5.0/CM12 when ist in beta or final build Phase ? I dont want to miss this kernel when i update to 5.0 someday
[Galaxy S III Android Development] XDAMaxe:
:confused: so you want us to make you wake up and take care for your spoonfeeding :p
[Galaxy S III Android Development] Code124Y:
true that boeffla kernel is the best i tested on CM11, hope andi will make 1 for CM12 XD...

Signature:

CM12, by default setting already have such impressive result... i love Google, i love CM, i love AOSP!

Don't post thanks, press/hit thanks will do.

---------- Post added at 11:58 PM ---------- Previous post was at 11:50 PM ----------

actually it's my bad... mahdi ROM should use cm11 kernel instead OMNI kernel. because when I'm on mahdi v2.9 with OMNI kernel, i cant tune correctly the value inside PegasusQ tune setting... i assume that CM kernel will do better for that. (i also had down side on responsiveness after few day usage).

i can't test it now and giving a accurate answer as I'm using Archi CM12... sorry...

Signature:

CM12, by default setting already have such impressive result... i love Google, i love CM, i love AOSP!

Don't post thanks, press/hit thanks will do.
[Galaxy S III Android Development] elhennig:
I am using the omni NG beta8 kernel with Slimkat and it works perfectly well.
[Galaxy S III Android Development] ayoubij:
will overclocking to 1600 kill the phone faster than 1400 or is it safe to use? ( I may still need the phone for atleast 1 more year ) :p
[Galaxy S III Android Development] XDAMaxe:
1600 is in fact no oc cos it does not exceed exynos cpu specs. Therefore you shouldn't expect earlier phone fail imo.

fyi: my phone runs with 1600 for months without any issues (neither increased power consumption nor higher cpu temp)
[Galaxy S III Android Development] andip71:
Yes, meanwhile they are quite different unfortunately. It is not easy anymore to port it. E.g. meanwhile in the 9305 things like Knox have been introduced with all consequences. This is still not even known to the i9300...

Yes, you need to strip debug code out of the modules after compilation.

I am currently on a business trip, so have no access to my stuff. But if you remind me again in 4 days, I can let you know how I strip it down.

It is easy: If cm11 kernel boots up, mahdi uses CM11 as basis. So you should stick to cm11 kernel.

Omnirom kernel will also work, however if you want to have the rom and kernel close together, just keep the cm11 kernel. It will serve you well.

Oh dear, the next one.

But enjoy your new device!!! Maybe we see each other one day again, you never know.

Well, in fact I do not recommend undervolting at all, as it can run fine for 2 days and then all of a sudded you can have a free or reboot which could end you up with data corruption in worst case.

But if you really want to use it, well, play a heavy game. I think this is still one of the best ways to give it a smoke test.

Yes, for Slimkat use latest Omnirom kernel beta. Is working fine.

Once CM team comes up with official CM12 nightlies, then I will jump onto that too.

However I will not develop a kernel for the "niche" roms like nameless and/or others.

Sorry, have not enough time to do all of them. So I will have to focus on official CM12 by CM only.

No, it will not.

Due to thermal throttling of the Exynos SoC, the CPU will throttle down once it would get too hot, in order to protect the CPU.

Andi
[Galaxy S III Android Development] kazuya_kun:
Support for latest SlimKat?

Hey andi :)

Does your kernel supports SlimKat in the newest version? According to your site (on download and stuff) i should use the kernel for OmniRom. Is that correct? However it does not work (the system does not boot up). I am using your latest beta NG kernel and i hope you can help me. Or is there anything else i have to be sure of? I have installed your kernel directly after i installed SlimKat new (without starting it once before, i hope that that is not the problem).

greetings kaz

[MENTION=947981]Lord Boeffla[/MENTION] as always really nice work!

P.S. i used the arter kernel before and changed everything to F2FS. Now i hagve changed back everything (i have formatted everything back to ext4 with the beta recovery from arter), but for some reason, even if i dont install anything just the kernel and the Slim GAPPS it still does not start.... any ideas?

EDIT: Okay nevermind, it was my fault i have formatted my internal file system wrong (instead of FAT32 with ext4 or something like that.) that was the cause of not booting.
[Galaxy S III Android Development] andip71:
Sorry, being on a business trip at the moment, I cannot keep up to date with everything.

What is "slimkat new" exactly? Just a new nightly or something else?

I have stopped using slimkat myself 4 weeks ago for time reasons, so I cannot test myself soon. Hope some others can chime in and tell if they have the same issue or not.

Saying that... I currently cannot say why it does not work for you. We would need to analyze that more deeply.

Andi
[Galaxy S III Android Development] flither:
By latest you mean weekly 8.18? I haven't flashed it since changelog is very short, basically just couple of minor changes. So basically you can flash back to 8.16 - working perfectly with latest NG for me (and all previous versions). And wait for 8.20 :) I would also suggest trying different recovery (TWRP or Philz Touch).
[Galaxy S III Android Development] kazuya_kun:
fixed it already. and no i have used the latest stable SlimKat v8.0 from Android v4.4.4.

greetigns kaz
[Galaxy S III Android Development] flither:
Wow mate, I can assure you 8.16 (and probably 8.18) is great - flash it, no more time to waste. There will be no "stable" 4.4.4 versions anymore, they just polishing the 4.4.4 and moving to 5.0 :)
[Galaxy S III Android Development] kazuya_kun:
but i have one question. When i flash SlimKat it always formats the system partition. I am normally used to a "dirty flash" aka CM11 style xD And i have some apps with settings on the system partition. How can i manage to flash the newest weekly without erasing everything (especially GAPPS) on the system partition? any ideas?

greetings kaz
[Galaxy S III Android Development] flither:
Normally SlimKat is not wiping the system during flashing, I do it manually (in TWRP). Maybe depends on recovery? I'm not so tech savvy ;
[Galaxy S III Android Development] kazuya_kun:
well when i flash it with PhilZ Recovery (it is pretty much CWM (Clock Work Mod)) it shows something like mount and format system and stuff. I am not sure. well i guess after i am finished with configuring my Phone, i will do a full backup and then try to flash the latest weekly. lets see if something gets erased.
[Galaxy S III Android Development] kadopt:
There should be a script to backup gapps during updates. Also I made a custom script to backup apps put on system by myself.
[Galaxy S III Android Development] paour:
I'm using the Touch LED full disable option on the 2.4b7 Omni NG kernel running SlimKat (latest weekly) and it does disable the touch LED, but the setting is reset on boot.

I tried to look for a conflicting option in the Rom settings, but didn't find one. Any idea why the setting doesn't stick?
[Galaxy S III Android Development] andip71:
Not using Slimkat myself, so I cannot search. But I am sure, there must be a setting somewhere in the rom that overwrites it.

Maybe someone else knows straight away...

Andi
[Galaxy S III Android Development] BFMSAND:
Thats the best Thing as i also dont want to use nameless but i want to use cm12 if its time for it (when beta builds, stable builds are available)
[Galaxy S III Android Development] Stevica Smederevac:
You can disable kernel control in Boeffla app and use the one is Slimkat. It has an option built in the rom.
[Galaxy S III Android Development] Der-Knuffi:
What do you mean? My S3 had an heavy impact and is therefore not fully operational anymore. So I thought to shoot a S4 in the bay instead of a S3 ,,,

The prices are not very different.
[Galaxy S III Android Development] andip71:
Do you know by any chance where in the rom you can configure the slimkat internal setting of it?

Because this is where the conflict comes from finally :)

I mean... the next one leaving the S3. Currently, many people leave the S3 and move on to other phones. Which is quite natural after 3 years of course.

Andi
[Galaxy S III Android Development] Stevica Smederevac:
I think it's in display settings,there is settings for led and settings for touch key lights or in advanced display settings where is network,vibration and mdni settings. Not sure but it's there:banghead:
[Galaxy S III Android Development] kazuya_kun:
would you be so kind and attach your script/config? It would be nice to have something like that. I am sure it will come in handy some day.

And [MENTION=947981]Lord Boeffla[/MENTION] dont worry, i will stay on my good old S3. Well as long as it is possible.... until you make a kernel version for the S4/S5 :P That would be great :3

greetings kaz
[Galaxy S III Android Development] Code124Y:
Guess i also might leaving next year, or maybe i will use my S3 as second devices, its good anyways, graphic processor losing in term of old GPU, but come to cpu, Exynos is still better then other like MTK...

will you go for S6?

seem S6 will having new all in house Exynos SoC next year... (may be they will include their own GPU and LTE).

This is what happen from ZERO...

Signature:

do you know what happen if you tune your Kernel+ROM correctly?
[Galaxy S III Android Development] exwan:
Better stay away from exynos if u wanna buy new phone.
[Galaxy S III Android Development] andip71:
I tend to second that.

However, having now a Qualcomm device, it is it's own different world. And I am not yet sure whether this world is so much better.

Andi
[Galaxy S III Android Development] fabfor:
[MENTION=947981]Lord Boeffla[/MENTION]

Which phone and chipset manufacturer would you suggest in terms of opennes in releasing the code and community support.

I'm evaluating a new phone in the range of xperia z2.

Thanks and sorry for the OT
[Galaxy S III Android Development] andip71:
Hard to say...

Until yesterday I had said, a OnePlus as this works officially with CM code.

But after OnePlus and CM announced yesterday they want to stop their relationship, time will show how this continues.

At least OnePlus does not forbid to unlock the bootloader (which is a one liner, so it is specifically simple) and install custom roms and root, you will not lose warranty. I still do like that approach.

Sony is apparently known to be quite open to developers and modding.

But I never had such a device.

Andi
[Galaxy S III Android Development] khanmein:
stay away exynos & mediatek. next hp i will go for snapdragon but currently s3 served me well. i won't spend so much on gadgets.
[Galaxy S III Android Development] scholbert:
Hey Lord Boeffla,

thanks for your comment...

Did some investigation myself and sorted out the differences.

You're right, the Samsung kernel for GT-I9305 seems to have branched from the base and covers some other devices as well.

I realized that Hbohd started some attempts to create AOSP kernel from Samsung KK source back in October.

Maybe i'll drop some comments there, as this is no I9305 thread :angel:

So again, thanks for clearing up and happy hacking!

scholbert
[Galaxy S III Android Development] Code124Y:
nope, i disagree this...

exynos is good but closed source... however the SoC is really good, snapdragon is good because of open source only, i can tell that my S3(current using, international) is much more better in any term (except GPU performance)

vs S4 LTE (snapdragon 600). both 12hours discharge, S3 can handle 4.5hours screen on while S4 only can handle 2.5hours.

But true that AOSP base give a lot benefit vs TW on sammy... smoothness, battery life, responsive and more...

sure 200% no to mediatek...

Signature:

do you know what happen if you tune your Kernel+ROM correctly?
[Galaxy S III Android Development] abhibnl:
Well as a matter of fact, i change my phone every two years. There's no point changing your device every 3-6 months just to be on 'the latest'. S3 served me well for 2 years, an amazing device but closed source ****ed it. That's why i'm buying oneplus one. Latest chipset, affordable, dev support is awesome and moreover due to quallcomm developement scope is really great. I'll keep that device for atleadt 2 years' for sure.

Sent from Galaxy S3 Powered by AD 1.x + Boeffla
[Galaxy S III Android Development] agusdallalba:
But there still are a lot of us that don't talk much in the forums but still use and have no plans at all to replace the i9300. Don't leave us please, the show is not over yet. And now CM12 looks like it's going to rock on the S3, they have a working camera HAL, open source RIL and the hardware compositor is not a stub anymore.
[Galaxy S III Android Development] mad_ady:
Agreed, the S3 is far from being obsolete. It can run anything newer phones run.

Also [MENTION=947981]Lord Boeffla[/MENTION] - friendly reminder - can you show me how to trim down my modules? Also how do you build a ramdisk from your sources? Thanks
[Galaxy S III Android Development] JustArchi:
Sony is doing great job. And all phones shipped with CM are almost guaranteed to be as open as possible.

I'm targeting for Xperia Z4 myself.
[Galaxy S III Android Development] flither:
Exactly yeah. It is a first phone in my history that I want too keep for longer (2y 3m and counting), it's just still one of the best phones ever created imho (also thanks to devs). Millions of people still owning it cannot be wrong :)
[Galaxy S III Android Development] DMD567:
S3 forever i just got mine september and am not ready to change this phone. Its getting popular in jamaica and most of them dont have a xda account long live the S3, if u wanna sell urs go ahead THIS IS NOT THE PLACE TO DOWNGRADE THE S3 ITS TO ENCORAGE ITS DEVELOPMENT U SELL URS SO SHUT UP AND GO TO THE FORUM OF YOUR PHONE AND SUPPORT IT. CAUSE I STILL HAVE MINE AND MILLION OTHERS NO MORE BOUT SELLING LETS BRING UP THE S3 LET PPL BE SORRY THEY SELL THERES :)
[Galaxy S III Android Development] abhibnl:
OT:

Well that's why i chose OnePlus One. Well it was in my budget so i went for it. I wanted towait for first 810 device but it would have been way iutta my budget considering the inflation in India. That's why OPO was the best alternative. Nevertheless, it's a grewt device. Will be keeping s3 too but believe me mate. You, Andi, moster, arter, temasek and namless team, you guys are the reason i survived with this device for 2 years. S3 is still a great mid range device and due to the lesson learned "Never buy Exynos if u love AOSP", i went for qualcomm this time. Thanks guys for your amazing work.

Sent from Galaxy S3 Powered by AD 1.x + Boeffla
[Galaxy S III Android Development] NoxOn3:
Hey there, what kernel version will work better with the latest PacMan 4.4.4 nightlies in case of using xposed framework with it? Cause they seem to handle the xposed framework differently at boot... Same setup, same start Situation (from recovery or regular), different kernel - different behavior... Why?
[Galaxy S III Android Development] VirusPT:
I just know two things:

1. I will only buy a new phone when my S3 dies, because I'm completely satisfied with it.

2. I will never buy a Samsung phone again.

Because if we don't have this amazing community supporting this device and keeping it competitive and updated we would all be stucked with a laggy, buggy and outdated rom.

Because Samsung loves to make the new old in the shortest time possible just to sell and enrich.

There should be some law against it, manufactures should support their devices for longer and mandatory period of time.

Especially expensive devices like this.

I almost forgot to mention that I want to thank you everyone!

[emoji4]

Enviado do meu GT-I9300 através de Tapatalk
[Galaxy S III Android Development] Cosolord:
Hi. Please can you tell me what kernel i have to flash on paranoid android 4.41 ? Cyanogenmod or omnirom based ?

Thank you so much.
[Galaxy S III Android Development] Stevica Smederevac:
Go for Omni Ng
[Galaxy S III Android Development] Cosolord:
Thank you for your help my friend, il will try, but i still have a doubt reading what Andi says on first post :

Thank you, Stevica Smederevac :highfive:
[Galaxy S III Android Development] Stevica Smederevac:
It's the newest one,next generation;) .Don't doubt,just try. Andi would say the same but he is on a vacation or trip,something like that.

Hey,you can wait for his confirmation:thumbup:
[Galaxy S III Android Development] Cosolord:
Ok ;)

Good to hear :good: In bad case, i will flash my rom again ;)

Thanks.
[Galaxy S III Android Development] andip71:
Confirmed.

Andi
[Galaxy S III Android Development] andip71:
Confirmed.
[Galaxy S III Android Development] Cosolord:
Thank you, master ^_^
[Galaxy S III Android Development] karwankar:
Dear lord can i use kernel for Redmi Note 3G ?
[Galaxy S III Android Development] 8vasa8:
Nope. Only for i9300
[Galaxy S III Android Development] andip71:
Stable releases !!!

Hi all,

finally there is the time to call a good beta a stable version.

And this is what I am doing now for all 4 CM/Omnirom kernels:

CM11 Version 2.4 stable

CM11 NG Version 2.4 stable

Omnirom Version 2.4 stable

Omnirom NG Version 2.4 stable

Only change compared to latest betas is the update of the internal su to version 2.40.

Important note: All four kernels are now put on status "

maintenance

".

This means, they will not receive any new features anymore. They will however be maintained in case significant updates to base sources or ramdisks are required. Same goes of course for really significant bugs when they should appear.

And no, it is not the end of CM/Omnirom Boeffla-Kernels for the S3. But in my opinion, there is nothing more that I would like to add to these kernels.

So I call it a final now, until we might see CM12 coming around the corner for the S3 (fingers crossed).

Enjoy

Andi
[Galaxy S III Android Development] simplicio11:
Lord Boeffla thanks a lot! Your kernel and your diligence are awesome! :good: