yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Ok, it has no hot plugging in as I can see here:

https://github.com/gustavoss/androi...aster/drivers/cpufreq/cpufreq_intellidemand.c

No, the intelli-plug by faux is a generic hotplugging driver, so the governor itself does not need to take care anymore of that.

I have no plans to put this in my kernels I am afraid, as this is against my "close-to-stock" objective.

Sorry

Andi
[Galaxy S III Android Development] fcaronte:
thank's for explain
[Galaxy S III Android Development] andip71:
Thanks for understanding my reluctance.

If this driver could work without touching other stock governors, I would consider it to just make non-plugging governors working in the s3.

But I also would need to change pegasusq, lulzactiveq... and so on. And then it is too far away from stock for me.

Cheers

Andi
[Galaxy S III Android Development] andip71:
CM12 kernel - new versions !!

Hi all,

please find an update for the CM12 kernels (NG and non-NG, but non-NG not recommended anymore).

Both have the same change log.

Version 3.0-alpha8

28.01.2015

Changed toolchain to CM12 standard toolchain gcc 4.8

Internal kernel busybox updated to version 1.23.1 (compiled from sources by myself to fit all Boeffla-Kernel needs)

Internal su updated to version 2.45

Enjoy

Andi
[Galaxy S III Android Development] thearc77:
Flashed and the first boot took long time to detect battery gauge, telephony and Wifi but after 1 or 2 min all is working.

Edit: only was a observation for future post and really thank you. My f... gov is a mess and i can't get a card for international money trade and i want give you some beers because this great project. Ty so so so so much.
[Galaxy S III Android Development] andip71:
No worries! I appreciate your comments and appreciation alot. They are equally important to donations.

Cheers

Andi
[Galaxy S III Android Development] Gokulbalram:
I was wondering if I could donate in any way other than credit cards. I don't have a credit card :P

Anyway, thanks for the update. All hail Boeffla!
[Galaxy S III Android Development] andip71:
Other ways are:

- paypal

- international bank transfer

- bitcoin

- google play store vouchers

- cash

Select one if you feel you should support me :)

Andi
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], in the OP you stated "Triangle Away supported". Does this imply for CM too or will I have to go back to stock and then try triangle away?
[Galaxy S III Android Development] andip71:
I think the patch is still in.

You can try.

However I am not 100% sure anymore. I did not use it anymore for a long time.

Andi
[Galaxy S III Android Development] Gokulbalram:
1. I'm not sure how Paypal works.

2. Not sure about that either

3. Heard of it, not sure what it even is

4. We don't have gift vouchers here in India :/

5. I'd happily do that, but I guess I live a 1000 miles from you.

The reason my options are so limited is because I'm 16. I'll dig into this though :)

---------- Post added at 08:26 PM ---------- Previous post was at 08:19 PM ----------

Just tried it, doesn't work.

Anyway, I added Profile shortcuts to my Homescreen, but when I activate them, I get the message "Profile does not exist".
[Galaxy S III Android Development] andip71:
Triangle Away does not work with all bootloader versions anymore. So if you have a quite recent one, then this is over. Sad, but true.

Also Triangleaway was really supposed to work on Samsung stock initially. So yes, it was a try.

For the shortcuts: Sure they still exist in your profiles?

I would delete them and recreate from the app.

Andi
[Galaxy S III Android Development] Gokulbalram:
Yes. I even made the shortcuts again, but later on the same message came.
[Galaxy S III Android Development] andip71:
If you can replicate it, send me a bc.log file and then I will see if I can find something.

Andi
[Galaxy S III Android Development] Gokulbalram:
Woah, that was a lightning fast reply :eek:
[Galaxy S III Android Development] Code124Y:
erm... andi, what internal su to do u provide?

i mean what the purpose u put su in ur kernel?

Sent from my GT-I9300
[Galaxy S III Android Development] glockaki:
the new cm12 ng kernel on weekly 2 cm12 from archie and moster 2 is blazing fast!wow!im speechless!gonna monitor the battery cinsuption for a couple of days and report.the new toolchain seems to work better.
[Galaxy S III Android Development] andip71:
Simple. if you install the kernel on an unrooted rom, start the boeffla-config app, it asks you if you want to root during next phone start. And for this it uses the su coming with the kernel.

Then just install supersu app from play store as well and you are fully rooted.

Very handy with Samsung roms which are not that easy to root.

Apart from this autoroot functionality, it is not used at all.

Andi
[Galaxy S III Android Development] Buckycasuals:
Definitely not related to kernel. As one of the existing top devs for our device, I will like your few cents in this problem via recovery.

Hello [MENTION=947981]Lord Boeffla[/MENTION]. I don't want to cluster the thread with questions.

Can you explain to me what are these?

"Detected filesystem ext4 for /dev/block/mmcblk0p9

". ". ". ". ". ". mmcblk0p12

". ". ". ". ". ". mmcblk0p9

I got these detected by TWRP and CWM recovery while flashing the a current cm12 build. Though the build flashed and booted succesfully. Just curious what are those thing detected.

I'm thinking it might reason of frequent freezes on my device when I run cm11 and cm12 respectively.
[Galaxy S III Android Development] andip71:
Simple... one is the system partition, one the data (user) partition.

Basically it is what gets mounted under /system and /data.

And of course, this is why it is ext4.

Here the full partition table of the i9300:

dev: size erasesize name

mmcblk0p1: 000400000 000000000 "bota0"

mmcblk0p2: 000400000 000000000 "bota1"

mmcblk0p3: 001400000 000000000 "efs"

mmcblk0p4: 000800000 000000000 "param"

mmcblk0p5: 000800000 000000000 "boot"

mmcblk0p6: 000800000 000000000 "recovery"

mmcblk0p7: 002000000 000000000 "radio"

mmcblk0p8: 040000000 000000000 "cache"

mmcblk0p9: 060000000 000000000 "system"

mmcblk0p10: 023000000 000000000 "hidden"

mmcblk0p11: 000800000 000000000 "ota"

mmcblk0p12: 2e2000000 000000000 "userdata"

Andi
[Galaxy S III Android Development] Buckycasuals:
Thanks alot for your input. Do you know anything I can do to resolve that from being detected? I have been running cm11 since its onset and I have never seen such thing while flashing any ROM both cm11 and cm12 respectively.

Would using ODIN to go back to stock fix such detection? I presume its the reason of frequent freezes on my device running temasek cm11 v162.1 recently.
[Galaxy S III Android Development] andip71:
Well, all I can recommend if your partition table is somehow "messed up", is to find a Samsung stock firmware with a pit file (which created the partition scheme again from scratch when flashed wit PC odin).

But not easy to find a 3-part firmware with PIT for the S3 I think. On the S1, this was standard, so I was quite used to it.

Surprisingly different for the S3.

I am sure I saw such an "old" firmware in some other forum, maybe even android-hilfe.de

Andi
[Galaxy S III Android Development] sajju73:
There is pit file on this thread

http://xdaforums.com/showthread.php?t=2762594
[Galaxy S III Android Development] whatsgood:
Bro, I got the same message when flashing cm12 weekly 2 on latest arter CWM recovery but my phone seems fine. It is also the first time I've seen the message as well.

I don't think my partitions are messed up either, I only repartitioned my S3 a few weeks ago.
[Galaxy S III Android Development] szotaa:
Dear Lord Boeffla,

I'm wondering if there is any performance improvement in your cm12 ng kernel over cm 11 ng kernel. I wasn't using your kernel for a quite long time, now I came back to it on cm 12 and I'm impressed with 3d and ui rendering performance. Since I find cm12 in too early stage of development to use it as a daily driver and I'm forced to go back to cm 11 I'm asking you if I will find any performance diff on cm11 compared to cm12. Of course I'm asking about kernel-wise difference since I'm aware that I will lose hardware composer. Did you make any performance changes?

Thanks in advance for your answer and I hope my bad English is not an obstacle to you.

Best regards, szotaa.
[Galaxy S III Android Development] flither:
I had exactly the same messages when flashing Weekly 2, no problems with the phone at all. I think CM12 team changed something in the flasher, it doesn't say it's an error, it's just kind of information :)
[Galaxy S III Android Development] Gokulbalram:
http://hastebin.com/ihanacawav.coffee

Here you go.
[Galaxy S III Android Development] andip71:
Hm, think I need to put some more debug logging into the app to find out your specific issue.

Currently I do not log which profiles exists and which one should get applied. But for your case I should put that into the log.

I will come back to you once I did it. But as I am going on business trips soon, it can take a while unfortunately.

Till then: Does your profile has any weird characters in the Name? Quotation marks, hyphens etc.? Or only characters and numbers?

Andi
[Galaxy S III Android Development] Gokulbalram:
I have three profiles namely:

Normal

Battery

Power!

These three worked fine once I made shortcuts for them (even 'Power!'). Not sure what happened later on. They do have descriptions too.
[Galaxy S III Android Development] XDAMaxe:
Latest stock rom (german dbt) with pit (as part of a 3-part package) you can find here

and btw: it works perfect if you follow the op (inevitable :p)
[Galaxy S III Android Development] Scorpionea:
Hi there [MENTION=947981]Lord Boeffla[/MENTION]

I have installed your latest kernel on blissPop by team bliss v 1.9 rom

Kernel runs great but when I install config app latest version I can't access setting or three dot menu in upper right corner as shown in screenshot,is it been moved or what? Thx
[Galaxy S III Android Development] Oiram_37:
No problems here with latest Resurrection.
[Galaxy S III Android Development] andip71:
New kernel versions CM11/Omnirom !!!

Hi all,

now also updates to the stable kernel releases for CM11 (NG and non-NG) and Omnirom (NG and non-NG).

All now in version 2.6 stable with the same change log.

Version 2.6 stable

29.01.2015

Changed toolchain to gcc 4.8

Implemented new Boeffla-Sound equalizer profile "Googy-Max"

Internal kernel busybox updated to version 1.23.1 (compiled from sources by myself to fit all Boeffla-Kernel needs)

Internal su updated to version 2.45

Enjoy

Andi
[Galaxy S III Android Development] andip71:
Must be a glitch with latest Bliss Rom.

I have the three dots on CM12 inofficial by JustArchi.

What happens when you open the app and then press the menu touch key instead?

Andi
[Galaxy S III Android Development] Scorpionea:
yep that did the trick,i can access setting now ;)

thanks for the help
[Galaxy S III Android Development] andip71:
Ok, then Bliss rom developers disabled this type of menu.

There is an option in the rom that tells the app which style to use.

The question is only... did they do by intention or error? Because these three dots are now missing for all apps, just for info.

I would ask them if I were you.

Andi
[Galaxy S III Android Development] Scorpionea:
I don't know abouth that,installed today rom and is great,will link your post to main dev in bliss thread

also i haven't found issue with other apps that have 3 dot menu,they show just fine only boeffla app have this issue so far..but yea i agree it could be rom issue
[Galaxy S III Android Development] andip71:
Interesting, I would have bet the three dots miss in some other apps too.

Anyways, you have a way. And in other roms it works also with the three dots.

Let's see.

Andi
[Galaxy S III Android Development] cookiepuppy:
Hello lord boeffla,

First let me thank you for your great work with kernel, it amazes me how do i keep coming back using your kernel no matter what rom i use at the moment, and its like that because of your work, its the best kernel i used, in every aspect, for my device it made a miracle with sound battery and performance.

Thanks man for doing this work.

I have a question:

Most of the time except the sound and maybe governor and scheduler i never change anything. So in all other settings like Zram andbLMK im quite a noob

Which are the best settings in your opinion regarding LMK values and battery friendly governor and Zram values on LP rom. I use Cm12 weekly2 by moster and justarchi.

Do you have any suggestions or any idea what can work, since im not a gamer just web reading and music most of time

Thanks in advance
[Galaxy S III Android Development] Buckycasuals:
Many thanks to the toolchain upgrade for cm11 and OmNI. I'm going to grab it now and flash it over L-Droid 4.4.4. My days with cm12 has come to an end ... "There always a reason why CM discontinued support for i9300" which highlights unavailability of RAM.

Lest I forget, I did the repartition as you suggested. Is there any way I can see that the partition tables are corrected and in order? Thanks for your help. You have been a blessing to this community.
[Galaxy S III Android Development] Buckycasuals:
[MENTION=947981]Lord Boeffla[/MENTION] I just flashed the latest OMNI NG kernel 2.6 on L-Droid 4.4.4 (slim based rom). Phone booted successfully then my device becomes very slow. Next my device freezed, I had to remove the battery and power on again.

Then I got this message for the first time using your kernel for more than 2years. It reads "Caution: Kernel settings were not properly loaded (maybe a soft or hot reboot?),,please reboot to fix this issue!!!
[Galaxy S III Android Development] andip71:
I am not aware of an easy way to check the partitioning. I mean, sure thing you can issue a mount command in terminal, but it just shows the mounted volumes as such, not the partition scheme. Think you have to just "trust" all is fine again.

Well, I tested on Omnirom and there it was running just fine (as all know, I am not testing on any custom roms).

Did you then reboot, as the app told you in the notification? Would be interested if after next reboot the message was back to normal or not.

But if the message does not go away, something is wrong. Then I suspect init.d files blocking a correct kernel start, which can also cause the sort of issues you described.

Fortunately, if you keep on getting this message, we will find out in boeffla-kernel.log file what is going wrong.

First, I suggest you to visit this thread and ask your questions again there:

http://xdaforums.com/galaxy-s3/general/unofficial-boeffla-kernel-app-profile-t2621308

There are the real hardcore experts with lots of experience tweaking my kernel.

For CM12 I would keep the stock LMK values that come automatically, and if you do not do heavy multitasking I would even keep zRam switched off.

If you want to try it (to extend your memory), I would go for a total size of 600 MB and this on 4 devices. But this is my personal opinion.

Andi
[Galaxy S III Android Development] Buckycasuals:
After playing around with the kernel to avoid freezes, i have decided to revert back to stock. I keep getting the dreaded black screen even after tweaking the kernel trying to improve performance. I mean i have never had such problem with your kernel.

Here's the boeffla .log in dropbox

https://www.dropbox.com/sh/l2pjmi7253u99mk/AAAki8eMS_94p3y4f98ug02Ra?dl=0
[Galaxy S III Android Development] andip71:
Have you tried a negative testing by going back to previous kernel version 2.5?

Just curious.

Andi
[Galaxy S III Android Development] cookiepuppy:
Thank you
[Galaxy S III Android Development] Buckycasuals:
Just did as you suggested, I went back to 2.5 with a clean install as usual. Everything works as intended. Noticeably faster and responsive than 2.6. No freezes or lock up atm
[Galaxy S III Android Development] andip71:
Then the s3 is a diva again.

Others report this new version to be snappier. But that is normal. New release = 100 different opinions.

Your phone obviously doesn't like the new toolchain used.

Or it was a bad flash etc.

I would do a nandroid backup and then flash 2.6 again.

If still bad, you will need to stick to 2.5 for the future.

Andi
[Galaxy S III Android Development] Lukijs:
alpha 8 is awesome, went to sleep with 36% with poweramp playing and sleep timer set after 2h, woke up after 7h, still 36% : D
[Galaxy S III Android Development] glockaki:
for the first time after 2 years using the kernel i have a problem.i updated cm12 weekly 2.1 by moster2 and now evertime i reboot the phone my governor changes from peagusq to zmoove and the scheduler from boefla battery saving to standar.all the other settings stay as i set them up.i reflashed the kernel but the problem still there.
[Galaxy S III Android Development] andip71:
There are two possible reasons for that:

a) you enabled to overwrite scheduler and governor in the "performance" settings of the rom. You can find it under settings->performance under processor and I/O scheduler. Make sure, the switch "set on boot" is not active in both sections.

b) the rom boots very slow, so it one time sets the scheduler/governor again after the kernel did it. You can put additional "startup delay" into boeffla-config to delay the kernel configuration being applied. Try 10 or 15 seconds, if required you can go higher.

Andi
[Galaxy S III Android Development] andip71:
Yep, I switched off the battery fuelgauge functions.

Hehe, no... kidding.

Andi
[Galaxy S III Android Development] glockaki:
yep!i had enabled the "set on boot" option.now everything is back to normal again!thanks Andi.by the way i must tell you again that the new toolchain is great!!!the battery life is getting better and better!:D:D:D:D:D:D:D
[Galaxy S III Android Development] seroesh:
which kernel is best for CM12 Unofficial Temasek.. CM12 NG or CM12?
[Galaxy S III Android Development] ayoubij:
NG
[Galaxy S III Android Development] andip71:
Always NG in the CM12 world.

I consider even dropping the non-NG version completely as everything runs better with CM12 on NG (graphical glitches gone etc.)

Andi
[Galaxy S III Android Development] ayoubij:
Btw sometimes i have graphical glitches using snapchat even with NG kernel. It happens for a second sometimes when playing a video in snapchat a weird green screen shows for a second or two and then the normal screen comes again
[Galaxy S III Android Development] andip71:
Yes, known issue. Also when you open amazon.com or amazon.de in Chrome and jump into a product, the display gets messed up.

But also the same with stock kernel.

Who knows if this will ever be solved in near future. We will see.

Andi
[Galaxy S III Android Development] sanguinesaintly:
5.6-samsung-slim-19300

I'm guessing that this kernel has nothing to do with SlimKat and that the Omni version is still the recommended one. I wasn't sure what the slim referred to.

By the way - great work - been using your kernels for months now and I'm a very happy bunny.
[Galaxy S III Android Development] andip71:
Where did you see this kernel?

But no, when there is no text "Boeffla-Kernel" in it, it's not coming from my factory.

Andi
[Galaxy S III Android Development] andip71:
CM12 Kernel update

Hi all,

minor maintenance update for the CM12 alpha kernel, which now climbs to version 3.0-alpha9. Still NG and normal kernel version is available, NG version is highly recommended.

Basically I updated the CM12 ramdisk of inofficial cm12 weekly 2.1 (the one of weekly 2.0 was skipped by me due to some issues). And on some request, added a new equalizer profile called "Flat".

So, small update, but recommended for all users using inofficial CM12 weekly 2.1 by JustArchi/Moster.

Version 3.0-alpha9

30.01.2015

Implemented new equalizer profile "Flat", which resets the equalizer in Boeffla-Sound to neutral settings

Ramdisk updated to inofficial CM12 build of 29.01.15

Enjoy

Andi
[Galaxy S III Android Development] sanguinesaintly:
It was in your tweet

https://twitter.com/andip71/status/560829402502955008/photo/1

---------- Post added at 12:03 PM ---------- Previous post was at 12:02 PM ----------

By "hardly recommended" do you mean "HIGHLY recommended" ?
[Galaxy S III Android Development] andip71:
Oh, the slim kernel is something I always build for my own usage only. It is not officially released and nothing else than a downstripped standard kernel. Just forget about it :)

And yes.. HIGHLY instead of hardly. This is when one does 10 things in parallel at the same time. Thanks for spotting!

Andi
[Galaxy S III Android Development] ScratMan38:
[MENTION=947981]Lord Boeffla[/MENTION], in the S5 forum, ktoonsez developped a CM12 kernel for the SM-G900F beginning of January using Samsung sources and blobs, and it was working perfectly.

But he decided to stop using Samsung sources, as it would take too much time to debug in case of big changelog in codeaurora project, this is his post :

http://xdaforums.com/showpost.php?p=58461523&postcount=2895

What do you think about that ? as far as I understand, it is much better to use stock Samsung kernel sources to make sure the performance and stability of the hardware is optimized

Is there a way to ease the porting of samsung kernel sources to CM12 ?

Thanks
[Galaxy S III Android Development] andip71:
Hm, but this is exactly what my NG kernel is about???? :)

The normal CM12 kernel uses sources of official CM12 kernel git repo.

My NG CM12 kernel uses latest Samsung sources for n7100.

So, I have already done that almost more than half a year ago when I introduced NG kernels for CM11 and Omnirom...

Andi
[Galaxy S III Android Development] ScratMan38:
I know this, and I'm using your NG kernel for my girlfriend's i9300.

I asked for your feeling about the difficulties it generates to port samung kernel sources to CM kernel. I would like to convince Ktoonsez to continue developping his own "new generation" kernel for the S5 with samsung kernel sources.

And, IMHO, this task should be easier with S5 because the S5 has official Lollipop support from Samsung, so it already have an official LP kernel ; while you had to use sources from different devices to port it to i9300.
[Galaxy S III Android Development] andip71:
Well, "convincing" him would be a hard job in my opinion.

Here in the S3 world it is quite easy... to have the CM12 roms around with HWC to run with acceptable graphics display, the newer Samsung based sources are a must.

For the S5, I do not know about potential benefits in sacrificing the CM kernel code base and using Samsung only.

The only point is always: If you use Samsung instead of CM, you can be sure no new bugs have been introduced by CM kernel devs (which is still the rumor in the S3 area, mainly their upstream from 3.0.31 to 3.0.64 is said to be faulty).

Just my thoughts on it.

Andi
[Galaxy S III Android Development] ICavalera:
Hi there.

I'm a using slimkat 9.0 (4.4.4) stable.

Witch kernel should I install?
[Galaxy S III Android Development] andip71:
Latest Omnirom NG stable, with is version 2.6.

Andi
[Galaxy S III Android Development] ayoubij:
Hey thanks for the reply. Is it a known rom issue or kernel based issue? It didnt use to happen in cm11 at all. Only when i updated to cm12. Thanks
[Galaxy S III Android Development] andip71:
Neither nor... or better... both together.

For a perfect graphical experience rom and kernel have to go hand-in hand in terms of drivers, blobs etc. There might be also special requirements by CM12 graphic interfaces to be implemented in the lower layers.

So in the end I think, both rom and kernel need to be changed to overcome this. It is for sure not isolated to either rom or kernel.

Honestly, I only have the kernel view of these things, so I cannot add more constructive thoughts here.

And as CM dropped support for the S3 with CM12 (at least it appears so), I have not big hope this will ever get 100% fixed. But, happy to be wrong with that opinion one day.

Andi
[Galaxy S III Android Development] ayoubij:
Well hope that maybe you, if you are free, to check it out and maybe try to fix it if you can (A) :D