yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] sanefirst:
Maybe it's a placebo effect but I can swear that Disabling Touchwiz DVFS in Wanam reduced lags in the UI.

Tried with Wanam 7.2 and Android Revolution HD ROM 40.0

[MENTION=947981]Lord Boeffla[/MENTION]:

Do you have any idea whether the above statement can be true?
[Galaxy S III Android Development] SignetSphere:
Glad to know it's being fixed now Andi :) In the end it was merely a coincidence since you both updated your works at the same time-frame :D
[Galaxy S III Android Development] jj92942000:
Been using it for a few days no issues with this and other custom kernels for v4.3
[Galaxy S III Android Development] nelsonw:
I had a LOT of issues with the SUperSU update. I just intalled your kernel/app to. For a seconds I remembered some of your relatives... LOL Just Kidding. I figured out that wasn't you when all root app were crashing and having issues.

You make a good work...
[Galaxy S III Android Development] ikong7:
thanks!!! coming from who tried it...
[Galaxy S III Android Development] MIKEMON:
4.1.2 § 4.3

I do not see anything special about version 4.3?: Zmatený:

According to me, gold and official stable version 4.1.2 for your country.

4.0 kernel and applications, all beautiful, smooth and without problems, many thanks / Lord Boeffla / for the great work:)
[Galaxy S III Android Development] malachow:
→ [4.3][Boeffla][ALPHA VERSION]

:cool:
[Galaxy S III Android Development] MIKEMON:
Yes, the new test kernel, but in terms of fw.4.3, so no wonder it is not stable??
[Galaxy S III Android Development] pippoaacc:
[MENTION=947981]Lord Boeffla[/MENTION]: excuse me but I'm not sure I understood well: So the new code base of v.5.0 alpha2 IS the Chinese Kernel with new Mali drivers?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] janres155:
You try it, mostly solved problems with CPU lag.
[Galaxy S III Android Development] tezukaryoma:
Anybody here know how to enable crt off effect with 4.3 stock rom?because when on 4.1.2 i was using jkay,inside jkay got option to enable it,now no more jkay for 4.3 so i have totally no idea on how to enable it.
[Galaxy S III Android Development] RtN89:
v.5.0 alpha2 is absolutely perfect on Wanams 4.3.

Everything is so speedy, smooth and snappy.

Am on ZZmove battery yank, Cfq/row.

No crashes, 3 hour screen time with 1/4 brightness slider.
[Galaxy S III Android Development] Svartsyn333:
This kernel works perfect with Nightmare Rom. But there is one thing I don't understand: I have standard bootani with led and sound as long as I stay stock or flash random kernel - except Boeffla. When i flash this kernel my standard Sammy ani disappears, so does the led, and Nightmare Rom custom bootani appears (with Sammy bootup sound). How is that possible? Can this be changed? I want to keep full standard bootani with sound and led. :(
[Galaxy S III Android Development] janres155:
Here: http://xdaforums.com/showthread.php?t=2523433
[Galaxy S III Android Development] strange1712:
5.0a2 + Omega v51(4.3) + music + waze = lock

Hi, I'm testing with omega v51 and Boefflas Kernel 5.0 alpha 2,I know it's alpha, but at least seems like smoother for me...

That lockscreen issue was terrible and I used to get sudden shutdowns (or locks, don't know)... Now I've got issues mainly when using Waze AND music player. Even in 4.1.2 and Boeffla4.0 (I think it was Boeffla sound related, actually) they seemed to have issues, like rendering phone so slow it was unusable, but now it simply randomly locks, last bit of music repeating continuously once and again, and the only thing responding is keeping power button pressed for 10 sec, then charging battery logo appears on screen (I use a car adapter) and I have to keep pressing the power button and resetting about 4 times to achieve getting to "Samsung Galaxy s3 i9300" logo and finally booting the phone.

I thought it was worth reporting it with a little detail.

I liked Kernel 4.0, and now, with this buggy 4.3 (which I plan to keep, btw), I'm using 5.0 alpha as a lifesaver...

I would like to see it get better and eventually stable, keep on!

Ah, and only custom setting : zzmoove
[Galaxy S III Android Development] andip71:
Yes. Alpha1 = code drop for Europe, Alpha2 = Chinese code drop.

It seems, nightmare rom comes with own boot animation. Most kernels cannot handle it.

To get rid of it: Remove file bootanimation.zip in either /system/media or /data/local folder.

Done :)

No idea on that, never used waze.

And currently will not continue to dig into the 4.3 topic as long as Samsung does not

- continue the rollout of 4.3 again

- delivers new, fixed kernel sources for 4.3

But thanks for the report. Maybe someone else has some ideas on it?

Andi
[Galaxy S III Android Development] antonigj:
Hi, there is no way to find the link to download kernel 5.0 alpha2 Boeffla Thanks

Enviado desde mi GT-I9300 usando Tapatalk 4
[Galaxy S III Android Development] alirey:
Download from here:

http://boeffla.df-kunde.de/sgs3/boeffla-kernel/Test4.3-alphas/
[Galaxy S III Android Development] vinsbelmar:
I've flashed version 4 stable and these are some issues:

1) System language turns to deutsch in each reboot :shock:

2) stills the issue with my rom: SwiftKey turn off and Samsung keyboard turn on in each reboot.

3) I can't open Boeffla config app. This is the message on screen.

I have Gorgoid v2.6 ROM (4.1.2). My last system info: Kernel Boeffla 3.2. Stable.

Before installing I flashed "ultimate kernel script cleaning".

I'm returns to 3.2., the experience was excellent with it.

Regards
[Galaxy S III Android Development] SignetSphere:
1. Read this: http://xdaforums.com/showpost.php?p=47482940&postcount=8486 it's not that kernel's fault.

2. Same reason with number one. Not kernel related.

3. You're still using the previous version of the config app. 4.0 kernels and up requires the Boeffla-Config V2.

Always read at least 2 pages back because there might be updates that you missed. And also read the OP as everything is stated there.
[Galaxy S III Android Development] kalebdevil:
Hi, great work with this kernel, but I have this problem with alpha 2, no root, any way to fix it? Thanks a lot for your hard work.
[Galaxy S III Android Development] janres155:
Hi! You can flash this through recovery.

Here's the link: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
[Galaxy S III Android Development] vinsbelmar:
I'll do. Thanks
[Galaxy S III Android Development] jj92942000:
Long time Omega user, also using waze and obviously music player. I'm using v5.0alpha2. I'm getting bit better performance by ticking GPU rendering, uping CPU to 1600 despite my use at just 1.5%.

Back to waze, 1st has nothing to do with kernel!!!! Nothing to do with Omega rom!!! But it works for me cuz problems are with app, presume they need to update. Go to manage apps and clear data & cache. Turn on gps 1st then turn on waze. Voila all works. I had initial FC but no more. Didn't have for stock music player if same do same clear data cache but this time reboot to let media scanner do its thing. Again not kernel nor omega's fault blame Sammy
[Galaxy S III Android Development] vinsbelmar:
I've read those articles. finally i Reflashed boeffla v4. And waiting for update of supersu app. With boeffla 4 i've obtain better benchmarks results :D

Enviado desde mi iPad con Tapatalk
[Galaxy S III Android Development] Svartsyn333:
Well orangerot said he didn't implement his own bootani, but it suddenly shows up after flashing your kernel. I don't face this with other kernels.

You mean if I delete the one from Nightmare the standard ani will show up again? Is it because of both available, one in the one and in the other directory? Sorry for stressing you with this but I want to stay on the stock ani and use your kernel. Cause it's the best around by now. :)
[Galaxy S III Android Development] andip71:
I also wait for it :)

Yes, I know it, because I have implemented the logic, hehe.

Just rename both of them to bootanimation.bak, so you will see and can always go back again.

Andi
[Galaxy S III Android Development] Svartsyn333:
Ok, will try. Thanks for the quick reply!
[Galaxy S III Android Development] andip71:
to 1) SuperSu problem of version 1.69. Known and Chainfire will provide a fixed version

to 2) Same with me, it is a rom failure, it is with all kernels.

to 3) Are you using anything that block the app in terms of rights?

Things like xposed framework and apps like xprivacy?

If you have a 4.0 based kernel and the Boeffla-Config App V2, there is no reason for this.

Also check for proper root access.

Andi
[Galaxy S III Android Development] Milerpa:
Point 2 from above known issue with SwiftKey not sticking it's a problem with app not kernel or rom. Thought I'd clear that up.
[Galaxy S III Android Development] GUZGUN:
You are absolutely right for SuperSU 1.65. I installed it and all are great again. Thanks Andi for your great work and the time you spend for us.
[Galaxy S III Android Development] Saenic:
I just wanted to write about this but the search gave me your post... thanks for the research... *goes to blame Chainfire* :D
[Galaxy S III Android Development] Unuce:
Can you attach bigger format, i can't see anything on this. :)

Sent from my GT-I9300 using Xparent Blue Tapatalk 2
[Galaxy S III Android Development] reS28raM:
I had that in the past, both with SwiftKey and Swipe+Dragon, as a quick fix I used the app Disable Service to disable Samsung's keyboard service. That solved until they fixed, at least for me.

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] vinsbelmar:
Hi! Thanks for response to my post. Understood. [MENTION=5146570]SignetSphere[/MENTION] explain me the reasons. Solution for 3 issue report for me was install Boeffla-Config App v2.

Now i've reflashed Boeffla kernel v.4 and installed boeffla app v2 and its all OK.

Now waiting for SuperSU and Swiftkey ETA's for fix both issues.

Thanks for your work!

Hi! [MENTION=4794809]GUZGUN[/MENTION], Where download v.1.65? I search old releases to download at SuperSU threat but it isn't
[Galaxy S III Android Development] andip71:
I also uploaded onto my kernel homepage:

http://boeffla.df-kunde.de/sgs3/other/SuperSu_1.65/

Until Chainfire released a fixed version.

Andi
[Galaxy S III Android Development] andip71:
No. Because it is normal, nobody is perfect.

Chainfires work it typically masterpieces. So - no reason to blame anyone.

Especially as this topic gets more and more complext with growing number of devices and Android versions...

It happens from time to time, thats life.

Andi
[Galaxy S III Android Development] Pusheka:
https://db.tt/wlv0xb2J
[Galaxy S III Android Development] Unuce:
Thanks matee:)
[Galaxy S III Android Development] strange1712:
Hi, I think it's Kernel related in the way that Waze completely looping my phone didn't happened with 4.3 stock kernel, as somewhat mentioned, the problems with stock were long lag in lockscreen and sudden deaths (none-app related, most of them occured when in my pocket) of the phone (or locks, don't know, the phone was hot and screen off), besides common issue with wifi and worst gps fix. With Boeffla, I have no more sudden deaths, and lockscreen never takes more than 1.5 seconds to show, still got Wifi unstability and sometimes gps goes to travel who-knows-where, so I know (and by reading about it everywhere) these two are not THIS kernel related (It's Sammy's fault). The only drawback I find in Boeffla relative to stock now is the locks + sound loop which at halfway (working excellent before) occurs, and by the way triggered by some action by myself, namely pressing the menu button.

By the way, in 4.0 I have a similar issue with waze, as sometimes it rendered smartphone extremely slow, rendering it useless, but the music kept playing pristine, with boeffla Sound enabled. If I stopped the music (With a lot of patience waiting 1 minute for de drop-down menu to show and another minute for it to respond to the "pause" button to work), things got back to normal (somewhat, read next sentence). If I turned Boeffla Sound off, the lags were less frequent but still happened. With Stock kernel it simply didn't happened. What happened were "glitches" in the playback. A lot.

I don't OC, as it caused sudden shutdowns in my phone, even at 1500. Using 4.0 and Omega v50.1. With 5.0 and Omega 51 haven't tried, but phone works smooth enough for me (in everything else not related with the Issues mentioned before).

My guess is Waze is messing with sound server and sound optimizations, so waze is guilty about these issues, but the way the phone "reacts" to this issue is kernel related. With 4.3 AND Boeffla 5.0 this has gone to a new dimension in my phone.

I know about sammy being the ultimate responsible for all of this, just wanted to report that maybe some optimizations result in a more severe drawback, even if overall it makes system performance better.

Greetings!
[Galaxy S III Android Development] nelsonw:
Hi there! Good News! I'm using Imperium 20.1 ROM and 5b2 kernel and games don't lag that much. A little hiccups here and there but i'm pretty happy. You Should try!

Nelson
[Galaxy S III Android Development] andip71:
Quick question?

Have you tried with boeffla sound set to off? To check your sound server suspicion?

I would think it could be related to memory. Do you use zram?

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] jj92942000:
Strange I never had issues with Omega + Boeffla + sound + waze before nor now, it all works. Encountered a few app FC I attribute to restoring app data with TB once clear data it all works, then and now. Maybe a fresh install with full wipe and internal sdcard wipe this time don't restore apps install from play store and test.
[Galaxy S III Android Development] Unuce:
Can someone tell me all settings in boeffla conf app, for balance between battery and performance but little more on performance?

:confused::)

Sent from my GT-I9300 using Xparent Blue Tapatalk 2
[Galaxy S III Android Development] khalid0099:
Boeffla kernel v5 stopped working on wanamlite 4.3 :confused:
[Galaxy S III Android Development] Gorgtech:
zzmoove opt. @ 1,6 Ghz, row/row, 1024/1024 ;)
[Galaxy S III Android Development] andip71:
Should not be? There are no newer sources, so it must work (in theory).

Or Wamanlite 4.3 has included tweaks which are required in the kernel?

Such things like custom frameworks or so? (please not)

Andi
[Galaxy S III Android Development] Unuce:
Thanks mate, can you tell me about lmk settings, and gpu, and udervolt or overvolt for cpu and gpu?

And what to choise here:idle mode and multicore powersave?

System tweaks, zram, touch boost?

Sent from my GT-I9300 using Xparent Blue Tapatalk 2
[Galaxy S III Android Development] Saenic:
I was just beeing sarcastic ;)
[Galaxy S III Android Development] GUZGUN:
Suddenly Boeffla config v2 stopped working. I press to open it and nothing happens. It just shows me only the first of the first page and nothing else. I uninstall it, install it again and nothing... After restart i have a notification that my profile is enabled but i can't open config.
[Galaxy S III Android Development] dkionline:
Which base do u use?
[Galaxy S III Android Development] janres155:
Be wary that undervolting cpu/gpu can cause system instabilities and unexpected force reboots, so it is highly suggested that you decide for yourself on what undervolt values you will use and the decision to undervolt your phone. As what Andi always mention "Undervolting = No support".

To help you, you could add 10 for every stock values in LMK settings. On the other hand, you could try AFTR + LPA for CPU idle and Aggressive for Multicore powersave.

For zram, you try first with no zram then decide if you need it.
[Galaxy S III Android Development] JustArchi:
For mine ASV2 (which is pretty bad in terms of uV) I suspected problems at high undervolting, so light undevolting is pretty safe while medium is "max".

I'm even applying light undervolting in all my ArchiDroid presets. Why? Because manufacturers always add safe margin to make sure nothing bad happens. So by light uV you're in fact returning to factory desired value.
[Galaxy S III Android Development] janres155:
Yes, Ligh undervolt is the safest but we never know. Just to be safe and to be informed because a lot of people undervolt too much then get support here that their devices are having instabilities. So from what I know undervolt cpu/gpu = no support from Andi.
[Galaxy S III Android Development] strange1712:
In 5.0 I've not tested it with Boeffla Sound on. In 4.0, Boeffla Sound being off, these delays were pretty much less often. And now you mention, the setting I didn't change in 4.0 was zram, I kept it on as I actually found the phone to keep responsive in a long term, because just after booting it used to be ok, and with time it started to be more sloppy even after killing all the tasks, and this seemed to be fixed by zram. So this might be related to zram.

Unfortunately right now I'm not reverting to 4.1.2, I'll be trying to live with the 4.3 issues. Thanks anyway, this kernel Is awesome!
[Galaxy S III Android Development] janres155:
Hi [MENTION=947981]Lord Boeffla[/MENTION]

I want to ask if there is a way to execute init.d during rebooting, before the screen turns off? To be exact, I want to execute a script before the rebooting (screen turn off) process.
[Galaxy S III Android Development] GUZGUN:
Omega v50.1 + boeffla v4 stable + boeffla config v2.
[Galaxy S III Android Development] khalid0099:
It's working fine after restart. Thanks :thumbup:
[Galaxy S III Android Development] GUZGUN:
i restored an old backup i had and now it's ok.
[Galaxy S III Android Development] andip71:
This is typically a symptom when there is an issue with root access.

When you have that, go into SuperSu, remove Boeffla-Config V2 from here.

Then start Boeffla Config again and let SuperSu grant access again.

Or you use frameworks/apps that prevent proper access.

Or... reboot. Sometimes that is the magic :)

zRam is not always good, unfortunately.

It is just a kind of workaround to overcome the memory limitations. But it never ever can replace real physical memory.

Unfortunately, no.

Kernel does not even know when the rom (which is one level higher) is in which bootup step during startup.

And although the kernel knows when the display is on or off, it does not fit the startup sequence.

What I could, however, implement in theory is a kind of "early init.d" support. Which executes special scripts first thing of the initialisation instead of waiting for the rom to initialize.

Question is however, what do you want to achieve? What would you do in the script?

Andi
[Galaxy S III Android Development] MIKEMON:
I went back to 4.1.2 MG4 for me and everything is beautifully smooth and stable.

As long as Samsung does not issue really stable version 4.3 will remain so for older

Kernel 4.0 stable is super busy
[Galaxy S III Android Development] abhibnl:
Reverted back to old SU, bit still language is changing bro after every reboot. Wanam's rom 4.1.2....
[Galaxy S III Android Development] andip71:
Then most probably you only reverted back to old SuperSu App, but not for the binaries.

But you could try the new supersu beta version already:

http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip

According to Chainfires comments, it should be fixed now:

https://plus.google.com/+Chainfire/posts/e7N7ucmhu2X

Cheers

Andi
[Galaxy S III Android Development] mrstatler:
Works without any problems : omega50.1 and boeffla kernel 4.0

Jacek SGS3
[Galaxy S III Android Development] GrimPivo:
Try to set language inside SuperSU app settings, than reboot again.
[Galaxy S III Android Development] ilovehc:
Hi there, awesome kernel!

Where can i find some pre-configured profiles? In particular i need the battery life one.

Thanks in advance!
[Galaxy S III Android Development] andip71:
In config app, go to menu, then presets.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] danierakes:
Absolutely working.....
[Galaxy S III Android Development] JustArchi:
Hey Andi.

Did you change anything regarding init.d support?

For some reason my backend on ArchiDroid 1.X is called after initital load, not during it. It should loop at least ~10+ times, while it loops 0 (com.android proccess already started)

It's core component for me, on other kernels it work fine (including AD 2.X and Boeffla Kernel for CM11).
[Galaxy S III Android Development] andip71:
Archi, exactly the same handling as in cm kernels.

But which one did you use?

4 or 5 series?

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
5.0 alpha2.

I'm trying to find what may cause that, will keep you informed.
[Galaxy S III Android Development] andip71:
Ok. Will release 5.0 beta1 tomorrow.

Maybe that fixes your issue already.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] JustArchi:
Tested on Googy Max 2.0.5, Yank's 4.0+ and Stock with init.d, all fine. This time it's not false alert :p.

Looking forward to beta1, will keep you informed. The fact is that init.d is executed after initial bootup, so something must slow it before it's executed, like a script with while ! pgrep com.android or something like that, you know better.

Googy-Max

Sun Nov 17 21:20:51 GMT 2013

Linux localhost 3.0.101-Googy-Max2-2.0.5 #50 SMP PREEMPT Sun Nov 17 12:19:47 WET 2013 armv7l GNU/Linux

INFO: ArchiDroid_RunOnce executed!

INFO: I'm a child!

INFO: boot-dmesg NOT detected, turning off logcat banner

INFO: Not forcing Install mode if Update mode found

INFO: Install mode detected, I'm either after full wipe or forced to think so. Turning on ADMANY and DBUPDATE

INFO: I found 2 folders which need merging (data)

INFO: RunOnce Semaphore started

INFO: I'm merging com.near.boefflasound, called by ADMANY

WARNING: We're on Sammy's 4.3, which doesn't care about security, falling back to dirty chmod permissions!

chmod: /data/data/com.near.boefflasound/lib: No such file or directory

INFO: It looks like everything ended successfully on com.near.boefflasound

INFO: 1 to go

INFO: I'm merging ds.cpuoverlay, called by ADMANY

WARNING: We're on Sammy's 4.3, which doesn't care about security, falling back to dirty chmod permissions!

chmod: /data/data/ds.cpuoverlay/lib: No such file or directory

INFO: It looks like everything ended successfully on ds.cpuoverlay

INFO: 0 to go

INFO: Android created settings.db for me, how cute! Performing DBUPDATE

INFO: Applying Samsung-specific DBUPDATE

INFO: Finished DBUPDATE

INFO: I looped 42 times and didn't have to exit from infinite loop, that's nice (RunOnce Semaphore)

INFO: Calling Post-Installation functions (if any)

INFO: Could not detect RunOnce in init.d after cleanup, that's good

INFO: Reboot required, I'm rebooting the device right now

INFO: ArchiDroid RunOnce finished

Sun Nov 17 21:22:23 GMT 2013

Boeffla

Sun Nov 17 22:17:14 CET 2013

Linux localhost 3.0.101 #1 SMP PREEMPT Wed Nov 13 18:53:11 CET 2013 armv7l GNU/Linux

INFO: ArchiDroid_RunOnce executed!

INFO: I'm a child!

INFO: boot-dmesg NOT detected, turning off logcat banner

INFO: Not forcing Install mode if Update mode found

INFO: Install mode detected, I'm either after full wipe or forced to think so. Turning on ADMANY and DBUPDATE

INFO: I found 1 folders which need merging (data)

INFO: RunOnce Semaphore started

INFO: I looped 0 times and didn't have to exit from infinite loop, that's nice (RunOnce Semaphore)

INFO: Calling Post-Installation functions (if any)

INFO: Could not detect RunOnce in init.d after cleanup, that's good

INFO: Reboot required, I'm rebooting the device right now

INFO: ArchiDroid RunOnce finished

Sun Nov 17 22:17:18 CET 2013

Notice start and end time.

If you need testing ground, 1.X-EXPERIMENTAL awaits. Log is in /data/media/0/ArchiDroid/RunOnce.log.
[Galaxy S III Android Development] paintball23456:
why u no 4.3? this is the best kernel for cm or 4.1 ever! bring to 4.3!
[Galaxy S III Android Development] acasmc:
Flashed on CM11, all good. Thank you for your work.