yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] nazfalas:
Just wanted to report again that this kernel is the best I have ever used for my S3. Recommended this to a friend who was using Temasek's default kernel on Temasek's CM10.2 ROM (I am using latest Carbon nightly) and we both feel like this kernel makes our devices feel like they got a massive upgrade.

Thank you so very much for the time you invest in this!

Buying pro controls was a no brainer.
[Galaxy S III Android Development] Moopow:
Cosign with the above and I am on fusion 4.3.1.r2.2 :thumbup:
[Galaxy S III Android Development] Moopow:
Ok I have noticed something weird... I have set the ac charge rate to 1200ma and it seems to be actually charging slower than the 1100ma that is set as default.... Anybody else experienced this?
[Galaxy S III Android Development] andip71:
Not really weird, it is very well possible.

Reason:

Your charger (let me guess, you are using the crappy stock charger) cannot really provide more than around 1000maA. So in fact, the charging logic recognize the instable power and reduces the charging current down until it gets stable again.

So you can end up, due to that, with charging only with 600 or 700 mA in the end.

Only way to really fix it: Get a charger for a few Dollars or Euros that can supply more charge current in a stable way.

Or (on own risk): Disable the stabilisation logic in Boeffla-Config App and pray your charger will still work.

Andi
[Galaxy S III Android Development] enigma1981:
+1 to that. Me and my partner both bought HTC Sensation chargers and they work perfectly :)

Swyped from my Galaxy SIII using XDA Premium 4
[Galaxy S III Android Development] Moopow:
@ boeffla... Actually before installing your kernel the same charger would normally charge the phone at a faster rate than how it is doing now... I am going to try and get another charger and see if it makes a difference

Also I already have the logic thingy set to off.. See screen shot
[Galaxy S III Android Development] andip71:
Ok, your mistake is:

You have to set these options to "ON", because it says "ingnore unstable power" :)

Andi
[Galaxy S III Android Development] GTMoraes:
Hey Andi, um..

It never behaved like that. First time ever, after I flashed the Beta1. An charge monitoring app shows some useful info. It should, at least, charge at the normal speed, but it even seems to discharge while charging

(ignore the steep graphic, I've been using Bluetooth for Tablet Talk and Wi-Fi AP all day)
[Galaxy S III Android Development] Moopow:
Ohhhhh... I will make the change thanks :)

One more thing I noticed boeffla... I have created a profile and change the governor to zzmoove and governor profile to zzmoove optimal.... Also the scheduler is set to Row for both internal and external... However After rebooting those settings are changed to back to the default.... Others that I have changed in other tabs have remained though...

Is this normal?
[Galaxy S III Android Development] andip71:
Of course not normal :)

Which kernel/app version are you on?

Sometimes it happens other installed apps want to change the scheduler to something else.

Also in CM, make sure in settings you have not configured these standard schedulers to load, as the rom will reset them.

Worst case: Send me a debug info file and I can tell you if the kernel does it wrong or something else.

Andi
[Galaxy S III Android Development] Moopow:
I am on boeffla kernel beta 2a... The app version is boeffla config v2

No I have not made any adjustments on settings to load them

I have never sent a debug file before.. Is it located in your app?
[Galaxy S III Android Development] andip71:
Of course it is, all convenient for you.

Action -> Create debug info file (actually the last item when you scroll down)

Then mail it to me and we will see.

BTW: I meant, check in Rom Settings - Performance - I/O scheduler you did not check the "set on boot" item.

Andi
[Galaxy S III Android Development] Moopow:
Can you provide me with your email address please?
[Galaxy S III Android Development] andip71:
Hehe, no clue. Usually I am not at all very patient.

But yes, maybe I have some good mood.

Putting it in the OP is fine, however... I doubt many people read even the OP.

Anyways, I will put it in for good.

Thanks

Andi
[Galaxy S III Android Development] Gokulbalram:
The Lord loves his devotees, that's why :P

I took this phone over the Moto G2 because of Boeffla and the Dev Community.

All hail Boeffla!
[Galaxy S III Android Development] spark2331995:
i am on archidroid rom latest

and your latest kernel

whenever i exit some resource intensive app (mostly clash of clan) my wallpaper resets to default that came with rom and i will need to either reboot device or restart systemui in order to change wallpaper to my consent.

and this problem i have faced only in zzmoove governer (any profile)

i had these issues before too but i posted in the rom thread and got no solution( it was on archdroid 2.5.3)

i am posting this in kernel thread now as i am sure its not rom related

as i tried on different archidroid version and also on liquidsmooth rom and this doesnt happen in other kernel on same rom and same settings and same environment.

i really like the smoothness and speed and features of this kernel but i need zzmoove too as its the only governer that suits my need after trying several governer

am i the only one with this problem?any solution other than changing kernel or governer?
[Galaxy S III Android Development] andip71:
Quote:

"i am posting this in kernel thread now as i am sure its not rom related"

Very bolt statement. And I add to this another bolt statement:

I am sure it is not kernel related.

The issue is, the S3 is not having enough ram for resource intensive apps and processes. Fullstop. There is not SO much you can do about it.

You can use zRam to virtually increase memory, but it is also more a hack than a good solution.

I would suggest you head over to the configuration threads to get advise from experts on what you can still do.

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

Andi
[Galaxy S III Android Development] spark2331995:
But why this doesnt happen in other kernel? with every settings same.

and why does wallpaper resets and i have to restart the systemui to just set another wallpaper or to come back to my wallpaper (i googled it and found no good answer perhaps anyone here knowing this issue can explain me this, i am very curious to know )?
[Galaxy S III Android Development] nazimster:
Boeffla kernel 3.0 alpha 4 ng is working on Temasek unofficial version 4.5

Best

[emoji517]
[Galaxy S III Android Development] andip71:
Coincidence, luck? Maybe other default settings in other kernels?

Nobody will be able to answer that.

You have the option to play and sort it, or to go back to the other kernel basically.

Or... as I advised, to ask in the thread.

I do not have wallpaper resets btw, so that makes me suspicious anyways about your setup?!?

Andi
[Galaxy S III Android Development] Gokulbalram:
I just installed COC and there's nothing like that. Everything's fine. I'm on CM12 Unofficial Beta 5.
[Galaxy S III Android Development] andip71:
Hi guys,

initially I wanted to release 6 new kernels (cm12, cm11 and Omnirom - all in normal and NG-versions) still today. And the kernels are also ready to ship.

However, I will hold them back for a few hours and release them tomorrow morning (morning CET time) as I will not be close to my PC anymore for the rest of the evening. And I do not have a good feeling releasing it without being able to give some support if there are unexpected issues.

Hope you understand and can wait for another approx. 12 hours :)

Change log is not super big:

CM12 kernel will contain refreshed ramdisk

zzmoove upgraded to version 1.0-beta5 with a few bug fixes - credits to @ZaneZam

Kernel can now be configured to survive CM Rom updates, so no need anymore to flash kernel after a rom upgrade flash (can be activated/deactivated in boeffla config, as always)

Few internal bugfixes

So, stay tuned...

Andi
[Galaxy S III Android Development] fcaronte:
Thanks for adding persistent mode after cm update :) now we only need official cm12 nighty [emoji14]
[Galaxy S III Android Development] andip71:
You were one of the people interested in that, or?

Official nightlies would be nice. Yes.

But so far we have to live with what we have, and that is not bad at all [emoji6]

Andi
[Galaxy S III Android Development] fcaronte:
Yes I'm interested in that :good[emoji106]

And happy of all dev working to make unofficial cm12 possible for our phone and you for your Kernel and support to everyone with fast answer [emoji1]
[Galaxy S III Android Development] PriteshChauhan:
screen turn on lags on incoming call

Hi,

Can any suggest how to improve the waking up of phone screen when an incoming call rings. Right now I am having an issue as whenever someone calls me, my phone rings, vibrates and after a few (4-5) seconds the screen loads. Till then the screen remains black. Any tweaks that can resolve this. I am running CM12 based RR 5.2.8 ROM (on s3) with Boeffla NG A3V4 kernel.

Thx.:good:
[Galaxy S III Android Development] philocritus:
+1.

same happens here. Sometimes I miss the call cause when the screen lights up the caller on the otherside hangs up
[Galaxy S III Android Development] PriteshChauhan:
Is this Kernel Issue or AOSP thing?
[Galaxy S III Android Development] philocritus:
I don't know.
[Galaxy S III Android Development] ziwy:
I have the same issue..

I m on latest nameless with latest boeffla ng
[Galaxy S III Android Development] Stevica Smederevac:
No lag at all,same rom as yours.
[Galaxy S III Android Development] sevenshorseman:
I already noticed that with KK AOSP ROM.
[Galaxy S III Android Development] andip71:
It is a known problem since CM11 already.

Some people minimized the effect by using a "strong" governor like pegasusq and no undervolting/underclocking.

I never had that myself in former times, but I also never use my phone for doing phone calls.

But as you guys are on CM12... note this is all not even having official status, there are not even nightlies. So I guess this is one of the many known issues.

Andi
[Galaxy S III Android Development] fcaronte:
i think is a problem with zram, i have this problem with stock rom too.....to "fix" i activate the aswer by pressing home button, yes, i answer call first to see who is but i'm answer ;) PS for now with lollipop and 400mb zram is not append
[Galaxy S III Android Development] sevenshorseman:
I am on latest RR build with Boeffla Alpha4.

Your hint was great?

Since I activated zram with 400MB it gave a shot to performance that it feels double as fast as without activated zram.
[Galaxy S III Android Development] w0rinal:
Ah, same for me.

I always thought it was a problem with XPrivacy which freezes the screen turned off when the on-demand dialog pops up (to restrict whatever pops up when I receive a call) lol

Using the home button to answer a call might be a solution, thanks :thumbup:

On the other hand zram is disabled on my device so I don't think this causes the screen to stay turned off

BTW is it possible to set the LED blink rate to 0.5?

1 is still too fast for my liking

Sent from my Boeffla powered Slim GT-I9300
[Galaxy S III Android Development] PriteshChauhan:
Can you share your settings on the governor and CPU?

I think mine was lagging due to Zram activated. I already had Zram with 4 devices and 400 mb size.

I reduced to 2 devices and 200 mb size to get rid of the screen light up lag.

thanks
[Galaxy S III Android Development] sevenshorseman:
There is nothing to share, because it is all by default.

Sorry mate.
[Galaxy S III Android Development] PriteshChauhan:
Your suggestion is great. However, I don't want to pick up each and every call that rings so I haven't activated the home button answer option. But yes your clue about zRam helped in a way when i reduced the size and device numbers, i find the screen lights up faster than earlier. I dont know why this happens as it is logically incorrect.

I also tried reset of LMK values.
[Galaxy S III Android Development] philocritus:
maybe 4 devices keeps the 4 processors on the zram task.

that means less available processor time for the screen up task / ringing etc. and therefore the lag on wake up.

Just guessing.
[Galaxy S III Android Development] khanmein:
rom issue. cm11 don't have it.
[Galaxy S III Android Development] exwan:
The easiest way is to edit this line in build prop.

ro.telephony.call_ring.delay.=3000

to another value. I used 1800 and it is working fine.

It is not cm12 bug. As i have call ring delay on almost every rom i tried before. Pa, omni, cm. Saw this solution in omni thread before iinm.
[Galaxy S III Android Development] khanmein:
still delay 4-5 sec. wait to be fix!
[Galaxy S III Android Development] andip71:
And whom would you suppose to fix it? CM team?

I would not count on that, honestly. But lets wait and see.

Andi
[Galaxy S III Android Development] Gokulbalram:
For MultiTaskers: Latest CM12 Unofficial has the Memory Leak fixed. It's awesome.
[Galaxy S III Android Development] andip71:
You mean beta5?

Andi
[Galaxy S III Android Development] Gokulbalram:
Yep. I was playing Minecraft and took a screenshot and even opened WhatsApp and sent the screenshot. (Feels like 2012)
[Galaxy S III Android Development] andip71:
Now preparing 6 kernel updates to ship out in the next hour... stay tuned :)

Andi
[Galaxy S III Android Development] khanmein:
haha camera also can't fix so i don't think cm will fix either.
[Galaxy S III Android Development] Gokulbalram:
I was wondering, does anybody else face the "Can't connect to Camera" error?
[Galaxy S III Android Development] voorhees13:
Staying tuned :good: and downloading ;) Thx Andi.
[Galaxy S III Android Development] andip71:
Kernel updates for CM12, CM11 and Omnirom

Hi Boeffla-Universe !!!

Update time!!!

CM12 kernel is updated to version 3.0-alpha5.

CM11 and Omnirom kernels get updates to version 2.5 stable.

Please do not forget to update Boeffla-Config to version 2.1.62 in order to see all new functionalities... :)

Change logs are as follows:

CM12, CM12 NG:

Version 3.0-alpha5

09.01.2015

Note: You need Boeffla-Config version 2.1.62 to use all new functionalities !!!

"Kernel survive mode" available in settings of Boeffla-Config; this will make Boeffla-Kernel to survive a CM update flash, so you do not need to flash the kernel after a rom update anymore - note you have to activate that first in Boeffla-Config menu->settings->various settings.

New boeffla-config-reset.zip file in version v4 will be put in boeffla-kernel-data folder, to be flashed in recovery when phone does not start anymore due to a configuration problem; also this deactivates the kernel survival setting (needed if kernel is not compatible with rom anymore etc.)

Update zzmoove to version 1.0-beta5 for a bugfix (credits to ZaneZam)

Few internal improvements and optimisations

Ramdisk updated to inofficial CM12 build of 07.01.15 (beta 5)

CM11, CM11 NG, Omnirom, Omnirom NG:

Version 2.5 stable

09.01.2015

"Kernel survive mode" available in settings of Boeffla-Config; this will make Boeffla-Kernel to survive a CM update flash, so you do not need to flash the kernel after a rom update anymore - note you have to activate that first in Boeffla-Config menu->settings->various settings.

New boeffla-config-reset.zip file in version v4 will be put in boeffla-kernel-data folder, to be flashed in recovery when phone does not start anymore due to a configuration problem; also this deactivates the kernel survival setting (needed if kernel is not compatible with rom anymore etc.)

Update zzmoove to version 1.0-beta5 for a bugfix (credits to ZaneZam)

Few internal improvements and optimisations

Expect all kernels up within the next 10 minutes...

Enjoy

Andi
[Galaxy S III Android Development] fonfox:
Dont have this error on temasek v4.5 with boeffla ng. Dont have any error. All fine . Only SMS but i dont need it.

Edit: Thanks for the New App

And thanks for the New kernel alpha 5 [MENTION=220904]andi[/MENTION] its great [emoji2] [emoji106] [emoji106] [emoji106]
[Galaxy S III Android Development] sevenshorseman:
Exact the same here?

---------- Post added at 07:05 PM ---------- Previous post was at 06:59 PM ----------

Edit

After a reboot camera is back?
[Galaxy S III Android Development] Lukijs:
Gratz, you might have ****ty s3 version, also use cm camera fix, if camera ****s up, you wont have to reboot, just launch that app
[Galaxy S III Android Development] viktor92:
I've got the same problem and thought that was the new kernel v2.5, then flashed back v2.4, and doing the same, I've finally got again "camera stopped" and then the infamous "can't connect". Just today I've made a clean flash of AD 3.0.2, then restored the yesterday's AD 3.0 nandroid, and camera didn't failed again...
[Galaxy S III Android Development] andip71:
Camera issues are a big open area since CM11... still unfixed in CM11 for everyone.

So we should not expect CM12 makes it any better.

Sorry to be honest.

Andi
[Galaxy S III Android Development] Virnik0:
I am still thinking if Andi does have crystal ball or not....to answer such questions

---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------

c'mon, it's not your job and you're not helpdesk worker. as far as I understood, it's your time-consuming intensive hobby. there is no reason for you to feel responsible for other people and their self-decided actions. Take break and enjoy your free spare time.
[Galaxy S III Android Development] whatsgood:
Hi [MENTION=947981]Lord Boeffla[/MENTION], thank you for this new release!

According to dhiru it seems that the new lollipop roms for i9300 require a kernel that is based on N7100 to perform even better, as the current kernels exhibit a few graphical glitches. I'm just wondering whether releasing a branch of boeffla kernel based on N7100 is on your agenda.
[Galaxy S III Android Development] andip71:
No, not on my agenda for the next future.

First no time for it, second I don't put any big work in the CM12 kernel as long as there are no official CM12 nightlies.

I stick close to the CM12 kernel branch, everything else is too experimental for me at the moment. And too unofficial.

Andi
[Galaxy S III Android Development] andip71:
However, I could base the kernel for a try on my 7.2 Sammy kernel, which bases in n80xx code. Worth a quick try next week...

Andi
[Galaxy S III Android Development] exwan:
Anyone having problem with camera. Try to uninstall with titanium and then use google camera. I dont have the cant connect to camera bug. Only on cm11. Btw, Ring delay workaround work for me only?
[Galaxy S III Android Development] Gokulbalram:
[MENTION=947981]Lord Boeffla[/MENTION], I'm still baffled by how people say "base on the Note kernel", " base on the n80xx" code. Could you explain it if you get time? Thanks.
[Galaxy S III Android Development] 200:
Slimkat

FWIW, I never had any camera issues since I moved to Slimkat 8 (and now 9). :)
[Galaxy S III Android Development] khanmein:
i faced it everytime when i goin to snap picture but i just reset or reboot fixed the issue. this is cm all time fav bug. ntg u can do about it. i noticed slimkat rom don't show that often but still exist. i stick with cm12 cos now i can snap pic with whatsapp & skype is working. previously cm11 got the bugs haven't fix until now.
[Galaxy S III Android Development] PriteshChauhan:
Thanks will try that suggestion..but from that isn't it a ring delay rather than a screen delay?
[Galaxy S III Android Development] superchandan007:
Hello [MENTION=947981]Lord Boeffla[/MENTION], will alpha 5 work on crDroid latest build???

Sent by Chandan 007 using GT-I9300
[Galaxy S III Android Development] khanmein:
same thing. still got delay even u set 1800 no much difference.
[Galaxy S III Android Development] yusuf_adsas:
Installed temasekCM12 again and using your configs. Working wonderfully. Thanks as always![emoji106]

Sent from my handphone, not yours
[Galaxy S III Android Development] exwan:
Did u check ur build prop after u edit the line? Did it stick?

It is working for me since last 4 month. Everytime i flash a new rom. The delay bug happen. When i edit the line in build prop. Delay is reduce.r

Update

Btw, [MENTION=947981]Lord Boeffla[/MENTION]. Will this patchset be merged in ur kernel? CM has merge them in cm11 branch. The patch fix serious bug on 4210 and 4212 / 4412 chips.
[Galaxy S III Android Development] khanmein:
ya from 3000 change to 1800 & seriously no change. bro, i know how to edit the build prop still delay. i think only u feel faster only.
[Galaxy S III Android Development] j1gga84:
This bug only affects 4210 chipset, i9300 is not affected!

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S III Android Development] exwan:
Really? Lanchon said that it effect both 4210 and 4212 / 4412 chip.

Anyway. All is good if s3 is not affected.

Edit : found the paragraph which he say s3 is not affected. So all is good. Thank you for pointing that out.
[Galaxy S III Android Development] khanmein:
exynos processor very problematic.. take snapdragon no need headache.
[Galaxy S III Android Development] Gokulbalram:
Yep, lack of sources and stuff.
[Galaxy S III Android Development] note2root:
Is there a kernel I can flash for nameless ROM lollipop on my note 2 sgh-i317m?
[Galaxy S III Android Development] andip71:
As I never tried crDroid, I do not know.

But I would assume it should. No guarantees though.

No, as it really fixes only something on the 4210 and 4212 platforms. 4412, which is used in the S3, is not affected.

I am sure there is a custom kernel for this device somewhere. Search through xda and you should find some.

However, Boeffla-Kernel is not available for it.

Well, it is quite simple (explanation is simple, doing not really).

Usually a S3 kernel bases on Samsung code for the device, in case of the S3 it is Samsung update14 code. CM also uses an old version of this code for their basis and move selected patches in over the time.

However, it turned already out a long time ago, you can perfectly build a kernel also from the source repo of another Samsung device. I.e. there was the time when my S3 kernel was based on code of n8020 as it was much newer than the S3 code that time. Samsung bundles all the required drivers into all their repos almost, so you can many time use another repo and build the kernel.

So, what I did for instance on my Samsung kernels 6.2 and 7.2 for Samsung android 4.4.x roms: I merged code of the n8000 (Galaxy Tab 10.1, which has very similar hardware to the s3, just charging chip is different and it does not have a notification led etc.) into my kernel repo for these two kernels, as the n8000 source code got officially updated to kitkat. Subsequently, the kernel ran much better on the ported Samsung kitkat roms.

What I eventually plan to do here is, to also merge the n8000 kitkat code into the NG kernel. So it will not base on Update14 anymore but on real kitkat code. Why not n7100? Because n8000 code is same quality + I have it already almost ready as I provide a n8000 kernel anyways. So it could be a quick action for me. Can be, could be, we will see...

Hope it is more clear to you now.

Andi
[Galaxy S III Android Development] exwan:
It would be great on kitkat and hopefully on lollipop too. [emoji1]
[Galaxy S III Android Development] nosphor:
[MENTION=947981]Lord Boeffla[/MENTION] Any news of getting the googy-max preset for the sound engine ? If i can switch to your kernel anytime soon it would be perfect.

I didn't forget that you have a lot of important things to do, so please don't take this question as a aggression
[Galaxy S III Android Development] konqui15:
Is it only me? If I activate zRam it works but after reboot it is off again.
[Galaxy S III Android Development] yusuf_adsas:
No such issue here.

TemasekCM12 v4.5/Boeffla-3.0-beta5

Maybe you have a script enabled somewhere like in the /etc/init.d ?

Sent from my handphone, not yours
[Galaxy S III Android Development] konqui15:
Ok I use cm11 and 2.6 kernel
[Galaxy S III Android Development] ZjemCiKolege:
Do you have a problem with the graphics glitch? on cm12?