yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] DUBS73P:
Hi sorry where can I find a link to download v5 alpha of boeffla? Thanks
[Galaxy S III Android Development] winworld00:
wooh! i love my phone again, its like brand new! thank you andi for such a great hardwork
[Galaxy S III Android Development] SignetSphere:
Why don't you read and search the thread before posting such request? :rolleyes:

Oh wait... is the "FIRST 4.3 KERNEL ALPHA" on the recently thanked post not clear to you?
[Galaxy S III Android Development] GrimPivo:
Whoa, not bad!

Can you share your kernel settings?

Did you overclock CPU/GPU (I think I know the answer, but...)?
[Galaxy S III Android Development] acasmc:
CPU1.6GHz, GPU600Mhz

Governor Pegasusq

Governor profile - Pegasusq speedmod

Internal memory scheduler - cfq

Readahead buffer - 2048

That's it.
[Galaxy S III Android Development] andip71:
While I still do not get exactly where the issue is with the timing... yes, Boeffla since day one waits with init.d script execution until the rom booted up to a certain point (this is for boeffla sound compatibility) by checking if the acore process is running.

But this never changed, it was always like that.

I am pretty sure, it is a busybox thing again. Let's see.

Will release beta1 in the next few hours...

Andi
[Galaxy S III Android Development] andip71:
5.0-beta1 (for JB 4.3)

Good morning all,

finally, version 5.0 of Boeffla-Kernel for Android 4.3 based Samsung Roms is available as a first beta version:

Version 5.0-beta1

Change log (vs. 4.0 stable)

Initial version based on Samsung 4.3 sources (XXUGMJ9)

All features of 4.0 Boeffla-Kernel are contained, with the following exceptions:

GPU frequencies/voltages are not available (due to changed mali drivers, I will wait until they get more stable and performant with next source drops)

"Sharpness tweak" not available (due to completely changed MDNIE implementation)

CPU frequency based LCD frequency (due to new mali drivers, was anyway only for tweaking experts)

Please note, I will suspend further development on this kernel branch until Samsung

continues to rollout 4.3 again with bugfixes

provides a new kernel source base with bugfixes

But until then - enjoy the kernel as good as possible :)

You can grab it now officially from the kernel homepage: www.boeffla-kernel.de

Thanks

Andi
[Galaxy S III Android Development] jj92942000:
Good morning Lord, tried to download beta and nothing happens, tried phone & PC?
[Galaxy S III Android Development] tzpm:
flash the v5.0 beta1 on android 4.3，there is no signal of my phone，how to solve it.thanks
[Galaxy S III Android Development] alirey:
Hi Lord,

Installed 5 beta. Everything works fine.

Thanks allot
[Galaxy S III Android Development] andip71:
Hi, honestly.. I do not quite understand.

What do you mean by "tried to download" and nothing happens

You tried to get it from the homepage?

Mobile or WIFI?

Please guys, you need to be more precise.

But ultimately, I do not know. I have signal, and almost all others (I guess) as well...

Andi
[Galaxy S III Android Development] tzpm:
solved!Right now, in front of the time I use the ROM with this kernel had no signal（cannot call，also without mobile）, then I flash other rom and this kernel can be used perfectly，your kernel is excellent，will not delay when light the screen.Thank you very much!
[Galaxy S III Android Development] hwjrmrm:
what's your modem?

such as my ZCBMK2 modem with boeffla kernel would lost signal and unkow baseband
[Galaxy S III Android Development] jj92942000:
Duh I went to 5.0 stable instead of test. Thx

---------- Post added at 10:54 AM ---------- Previous post was at 10:44 AM ----------

On 5.0b1 all is well. Don't feel any difference between this and alpha 2. Thx all good
[Galaxy S III Android Development] andip71:
That is already good news.

Basically beta1 is nothing else that a "cleaned" and proper version of alpha1.

Thanks

Andi
[Galaxy S III Android Development] NM666:
Hey!

It seems to be I can't take the logcat through ADB because of this kernel. Logcat on devices (CatLog application) works good. Same ROM with stock kernel sends logcat to ADB regularly.

Can I enable logcat from Boeffla Config? I didn't see any working option for that.
[Galaxy S III Android Development] andip71:
You can enable logcat in the Misc panel in Boeffla-Config, it is called "Android Logger".

But if it works with logcat app and not with adb, it is most likely due to the insecure adbd I use to enable insecure kernel functionality.

Potentially this breaks logcat.

If so, I will change this with 4.1 release of the kernel though.

Andi
[Galaxy S III Android Development] NM666:
Yepp, I toggle this settings but it didn't work with ADB :( .

I use version 5.0.
[Galaxy S III Android Development] andip71:
Aaaaah, you are using version 5. I see.

Would you like me to compile a test kernel for you, so you can check if it works when I remove the insecure adbd?

If so, let me know and I quickly build one for you.

Andi
[Galaxy S III Android Development] andip71:
Hi all,

have not yet checked myself (as I was sleeping till now), but I read now through all posts in different forums and the statement is as follows:

Update7, according to a kernel dev friend (who checked my repo still during the night) does contain the SOD fix already.

So it looks, 2.6 kernel version is already safe.

I will check myself later to confirm. But as this friend is a trustful resource, I am sure he is right.

So - enjoy the 2.6 kernel for now :)

Andi
[Galaxy S III Android Development] andip71:
Sudden Death fix confirmed !!!

Hi again and good morning!!!

I now checked myself whether the both patches to fix the "sudden death" issue

1) mmc: Soft-patch MoviNAND VTU00M (16GB) eMMC failure

2) mmc: Disregard pending irqs in sdio

are included in the latest sources update7, which were used to build kernel version 2.6.

And the answer is: Yes, they are in !!!

This means, kernel version 2.6-alpha1, which I released yesterday afternoon already fixed the sudden death issue (and the Exynos exploit of course as well).

So, you can relax and I would recommend all Boeffla-Kernel users to urgently update to 2.6-alpha1 !!!

Andi
[Galaxy S III Android Development] buster041284:
nice work pal
[Galaxy S III Android Development] Ninolina:
Well, that's great...:) But in that post it says:

"Expect an urgency kernel update within the

hour. I also advise other developers who

already are using other source bases not to

use update 7, it is outdated and older than

other sources. I extracted the fixes and will

be in my Github within the same hour."

Doesn't that mean that update7 doesn't have fix in it? Please, don't get me wrong, I am not a developer or similar, I just noticed that and I ask. Thanks for great work...:)
[Galaxy S III Android Development] andip71:
Ninolina:

It might be, Update7 is in some aspects older than other kernel codes for other devices. Could be, yes. But this is not what counts in this case.

The SOD fix is in. I checked the update7 codes against the fix patches myself this morning and I can confirm they are in.

So following my objective "Close to stock", I will stick with update7 source base as it is released for the i9300 and has both SoD and Exynos exploit fixed (and runs great by the way).

So, all is good with it.

Andi
[Galaxy S III Android Development] gsw5700:
Remember to keep usage of recovery/download mode to a minimum until these are also patched with the fixes. recovery mode will write to memory without the fix so there is a chance it may screw the phone. The kernel fix only protects the phone whilst the kernel is running (or so I understand)

Sent via TCP/IP
[Galaxy S III Android Development] andip71:
Very true!

The good thing is... normally, around 99,9% of the time the phone should run normally and not in recovery. Isn't it?

But you are right, this is the last remaining flaw and let's hope new custom recoveries are released quickly.

Andi
[Galaxy S III Android Development] AndreiLux:
Way to smooth-talk about Yank on Android-Hilfe while there he was suspecting I pulled that patch out of my ass ;)

Anyway the u7 are just slightly above u6 ones with the fixes which are new and then everything else being outdated such as WiFi, governor and a bunch of other stuff compared to the N80x0 sources. The patches I extracted are the only new things out of it.
[Galaxy S III Android Development] andip71:
Yeah, and that is fine. My objective is not (and never was) to be always on latest versions for everything. For that we have other kernels, so people can decide :)
[Galaxy S III Android Development] Ninolina:
Thank you for fast and great answer..:) I am more peaceful now...:) Thanks again..:)
[Galaxy S III Android Development] AndreiLux:
You already were running the N8000 sources here with zero issues, so it doesn't make much sense to me. I'm just saying, because things like the governor changes will have noticeable battery life improvements/degradations.
[Galaxy S III Android Development] andip71:
Fair points. If users report any (negative) differences, I can potentially change my mind again.

However, so far the reports on update7 are extremely positive.

So, time will show and users will tell :)

Thanks

Andi
[Galaxy S III Android Development] bcs2112:
boeffla-kernel.conf

Hi,

i'm using V2.4 with boeffla-kernel.conf - the only things, that sould i switch back to default are the undervolting setting? ... just to make sure :)

--

Regards,

bcs
[Galaxy S III Android Development] andip71:
bcs2112: In theory you are right. Only GPU undervolting is the thing I have not (yet) built in.

But: No need for you to change it back in the config file. The setting will magically disappear when you flash the 2.6 kernel. As it is useless for the time being.

So in a nutshell: Just flash, thats all :)
[Galaxy S III Android Development] rulala:
hi , andiP

I had found the important key point- Sound app problem..

I test it several times and make sure it .

supersu cause this problem. Because this always happen on every boot.

I uninstall supersu and install superuser . now I don't have any problem.

If I uninstall superuser and install supersu back and reboot . Problem is Back.

in other words , superuser is safe .

can you help me to report it to Simone201 ? thank you very much.:o

ps:

speaker volume will be return to 57 after you reboot.

others setting will not. only speaker volume. I mean Sound app .

another interesting thing is "Set on boot" ... I make some settings and values and reboot.

But I can't see the difference between Set on boot ON or Set on boot NON .....

it seems the same .
[Galaxy S III Android Development] fuxmen:
Big thanks for kernel just now checked and I have VTU00M rev 0xf1 chip :( :( soo no recovery for me until new arrive.

With Your kernel I can sleep well now.
[Galaxy S III Android Development] andip71:
Thanks rulala, this matches a report from another user having similar issues.

We will contact Simone on that, absolutely.

Andi
[Galaxy S III Android Development] Yank555:
I wasn't suspecting "you pulled that patch out of your ass", that would have been either magic (but we're talking about magic numbers :D) or inside knowledge coming from Samsung, and I don't think they would share stuff like that ;)

Just that, as I said there and on here on xda, I checked against a Repo that I had just created that didn't contain the Update 7 sourcedrop yet and at the time of day (or rather night) I really didn't have the will to check which potential compatible device that patch could have been pulled from by looking up if any other new source drop had been made.

Anyway, all is fine, most will include it in their kernel anyway (hopefully, and we will see for recoveries...).

Though, I'm still now waiting to see if it really does avoid the SDS for good, and only time will tell, that's my point of view.

JP.
[Galaxy S III Android Development] traitor123:
Nomination for Recognized Developer

Hey AndiP,

I personally feel you are qualified enough. You should nominate yourself or ask another higher authority in forum to make you a recognized developer. Request is to be sent to Senior Moderators Only. HERE is a list, see in the end under "Senior Moderators". Ask any one of them help you to change your membership status. You must provide your ID, a brief history of what you have done, if accepted, they'll make you a recognized developer. :)

Regards
[Galaxy S III Android Development] bcs2112:
\off

sorry for offtopic - i guess this revision no somehow SDS related. In which topic could i read more (how can i check the rev.no, etc.)?

\on

thank you,

bcs
[Galaxy S III Android Development] NM666:
OK, I'm ready to try test version.
[Galaxy S III Android Development] JenLOI:
Able to flash 5.0 into older version 4.1.2?
[Galaxy S III Android Development] artyfarty:
no!!!

5 --> 4.3

4 --> 4.1.2
[Galaxy S III Android Development] janres155:
[MENTION=947981]Lord Boeffla[/MENTION]

So this means that the alpha2 (chinese sources) will not become beta, and you will continue beta with GMJ9 sources for 5.0?

Btw, I already solved my script issue. Thanks!
[Galaxy S III Android Development] andip71:
You have PM.

Honestly, I never tried.

And I would never recommend that, as 4.0 has more features than 5.0 and the kernel source by Samsung for 4.1.2 kernels (as in 4.0) is BY FAR more stable.

Thanks

Andi
[Galaxy S III Android Development] andip71:
You have 100 points.

Most users reported the version with original (and not China) sources was better, at least on our European firmware.

So I decided to drop the other version for the time being.

But I will anyway suspend further development, as announced, until Samsung releases better sources.

Andi
[Galaxy S III Android Development] janres155:
Well, that's good news Andi. :)

On the other hand, I want to ask how init.d is executed in your kernel? Is it during on boot or after the ROM completely booted?
[Galaxy S III Android Development] andip71:
It is as follows:

- kernel initialisation waits until first Android rom processes can be seen (checking for the android acore process)

- then another 5 seconds wait time

- then the settings from the Boeffla-Config App are getting applied

- another 3 seconds wait time

- init.d gets processed, one script after the other

Hope this is what you were looking for.

Andi
[Galaxy S III Android Development] janres155:
Now I understand. So it means that this method is before applying the boeffla settings.

while ! /sbin/busybox pgrep com.android.process.acore ; do

sleep 1

done
[Galaxy S III Android Development] abihakim:
Im on chinese kernel atm. Will try to give a shot later.
[Galaxy S III Android Development] andip71:
Yes, exactly.

This is required to make the settings of Boeffla-Config and other init.d scripts stick + not break Boeffla-Sound due to too early initialisation.

Otherwise, firmware overwrites settings like schedulers again during start.

Do so, should not work worse than the one you are used to.

Andi
[Galaxy S III Android Development] NM666:
Oh yes, it's working now!
[Galaxy S III Android Development] andip71:
Ok, thanks!

I think it is more important to have normal adb based functions working than having insecure adb.

So I will remove insecure kernel for Samsung based kernels again with next beta versions.

It is always causing all kind of different issues anyway, so was close to do that already anyways.

Andi
[Galaxy S III Android Development] DirkStorck:
Hi. I have update your kernel to version 5.0-beta1.

I have a problem with getting log act over adb. I have enabled it in settings but if I write

adb logcat nothing happens.

If I write adb devices I see my device.

Any help please :)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] PedroMedeiros:
Hi [MENTION=220904]andi[/MENTION]P. I am back to your boeffla kernel. I am seeing that zram settings can't be applied. Is it working?
[Galaxy S III Android Development] andip71:
Confirmed bug, will be fixed with next beta.

Which version do you use?

At least on version 5.0 I can confirm this bug as well.

Andi
[Galaxy S III Android Development] PedroMedeiros:
I am using 5.0 beta1 ;)

When I run: /res/bc/bccontroller.sh apply_zram 1 4 I get input/output errors.
[Galaxy S III Android Development] jj92942000:
It works, make sure it's turned off then adjust zram then turn it on
[Galaxy S III Android Development] JustArchi:
Andi, it still doesn't work.

It looks like init.d is executed after initial bootup, it didn't work this way in previous releases, including Boeffla 4.0 and Boeffla 2.0 for CM. This is the first time when I face this issue.

In all other kernels init.d is executed right after kernel load, during initital bootup, in your kernel init.d is executed after initial bootup, which breaks my core backend during it's job during initital bootup.

Could you take a look? You can use any init.d script, for example the one which reboots your device. In all kernels it will reboot your device right after sgs3 logo, because init.d is executed during inittial bootup. In your kernel it will reboot the device slightly after load, including showing pin pattern etc.
[Galaxy S III Android Development] nelsonw:
Here too...
[Galaxy S III Android Development] andip71:
Archi,

it is the same in all my kernels, always has been!!!

Also in Boeffla 4.0 for Samsung, and 2.0 for CM based... you can look at the boeffla-init.sh yourself if you want to see.

There must be something else...

But I am happy to give it a try and move the init.d stuff forward. Maybe it helps.

First I need to release 5.0-beta2 to fix two bugs now. Then I can do a test version for you.

Andi
[Galaxy S III Android Development] JustArchi:
Then for some reason your pgrep doesn't work on CM, while it does on Sammy's one, because on CM init.d is called instantly.

I see that you have bootanimation support in your script, Yank recently deleted it because Samsung already placed it in ramdisk afaik. Maybe that's the reason?

https://github.com/JustArchi/ArchiDroid/commit/aa7f33a91f170de9b4958b6a0e4ccbfbd2226fa0
[Galaxy S III Android Development] acasmc:
anyone tested v5.0 with CM11?
[Galaxy S III Android Development] andip71:
No, and not needed, it will brick it.

For CM, I have specific kernels in the other thread. Link in the OP.

Andi
[Galaxy S III Android Development] Achraf AOUAD:
why would you do that ?

it's already mentioned in the OP that its not gonna work so why bother unless you want to put your phone into bootloop
[Galaxy S III Android Development] acasmc:
my bad. just realized i'm in wrong topic :D
[Galaxy S III Android Development] andip71:
Yes, known issue in beta1.

Will be fixed in beta2, due for today.

Andi
[Galaxy S III Android Development] nelsonw:
But I'm on Beta1 and works...
[Galaxy S III Android Development] Eleve11:
Will Boeffla 5 beta 1 fix the wake up bug in 4.3 as it does in the Yank/LiteGX kernel? :confused:
[Galaxy S III Android Development] 7wajahat7:
[MENTION=947981]Lord Boeffla[/MENTION] Apart from stablility, do you think there is a difference b/w 4.1.2 and 4.3 kernel in terms of battery timing? which kernel is more battery friendly? Or they are both the same?
[Galaxy S III Android Development] andip71:
Archi, built a test version for you.

Please look at your PM.

Andi
[Galaxy S III Android Development] sergini:
Same problem here, with yank my phone lags a lot when it wakes up from deep sleep.

I'll try boeffla to see if this happens as well, hope not!
[Galaxy S III Android Development] andip71:
Well, do not expect any wonders here. I have not put specifically something in.

Just zRam handling is different.

But - wait for beta2 please, it fixes 2 bugs.

Andi
[Galaxy S III Android Development] sergini:
I'll follow your advice, yank kernel os great in terms of battery, but this wake up problem is kinda annoying.

I'll be jumping between yours and yank's kernel, you both do amazing kernels!

Thanks
[Galaxy S III Android Development] winworld00:
yes mate
[Galaxy S III Android Development] gkhushal:
I always get lag on this kernel. On default settings... Don't know why..?? :(
[Galaxy S III Android Development] andip71:
Nobody can tell you. If you not - at least - let us know which kernel version you are talking about.

Usual suspect for lags: Disable zRam and try again.

Andi
[Galaxy S III Android Development] andip71:
5.0-beta2

Hi all,

to fix the recent reported bugs, a new beta kernel for the 4.3 Samsung firmware is already on the way:

Version 5.0-beta2

Fixed issues with zRam not being sticky

Fixed issues with logcat cannot be read over adb (and potential Eclipse debugging errors)

Moved init.d handling to an earlier point in the kernel startup sequence

"Beautified" the kernel logging

Homepage or load&flash :)

Enjoy

Andi
[Galaxy S III Android Development] gkhushal:
Started laging since 3.0 version .n even on 4.0 everything default(no zram) .. Except boeffla sound

Tried tons of time reinstalling, clearing cache n even with factory reset .... :(
[Galaxy S III Android Development] andip71:
Then have no idea.

Seems your phone and Boeffla do not like each other.

Never have lags at all, and many users also not as well.

Andi
[Galaxy S III Android Development] Clark789:
Hi!

One question for the experienced here: is there any real advantage for the time being for changing from Android 4.1.2 to 4.3?

There are lots of comments in this thread, that complain about annoying bugs in the new rom. Even The Lord does it himself... ;) And so i'm really keen on trying the new kernel, but installing the new, lagging and buggy ROM seems to be a high price... :)

So, i'm inclined to wait for a proper ROM. What do you think? Will there be a better DBT-ROM with less bugs?

Regards

Clark
[Galaxy S III Android Development] JustArchi:
For me, latest experimental ArchiDroid 1.X + Boeffla kernel is as close to perfect stock rom as possible.

But that's me.
[Galaxy S III Android Development] Gorgtech:
Gorgoid + Boeffla is close to Stock JB 4.1.2 too with good battery life.

http://www.gsmarena.com/samsung_suspends_the_android_43_update_for_galaxy_s_iii-news-7207.php

If this is true, many people will have to go back to JB 4.1.2 if Samsung still continues to at least offer JB 4.1.2 updates ;)
[Galaxy S III Android Development] rulala:
[MENTION=947981]Lord Boeffla[/MENTION]

I alaways use this script for myself.

I know we can use Config app to set zram .

But beta2 will read it as 1 device 150mb...

swapoff /dev/block/zram0;

swapoff /dev/block/zram1;

swapoff /dev/block/zram2;

swapoff /dev/block/zram3;

echo 1 > /sys/block/zram0/reset;

echo 157286400 > /sys/block/zram0/disksize;

mkswap /dev/block/zram0;

echo 1 > /sys/block/zram1/reset;

echo 157286400 > /sys/block/zram1/disksize;

mkswap /dev/block/zram1;

echo 1 > /sys/block/zram2/reset;

echo 157286400 > /sys/block/zram2/disksize;

mkswap /dev/block/zram2;

echo 1 > /sys/block/zram3/reset;

echo 157286400 > /sys/block/zram3/disksize;

mkswap /dev/block/zram3;

swapon -p 2 /dev/block/zram0;

swapon -p 2 /dev/block/zram1;

swapon -p 2 /dev/block/zram2;

swapon -p 2 /dev/block/zram3;

----

alpha1 .alpha2 . beta1 is read the script correctly.

I really hope it can be fixed. please:o
[Galaxy S III Android Development] MrAlez:
Chinesse sources

[MENTION=947981]Lord Boeffla[/MENTION], do you think it is possiblke to realease a boeffla kernel with Chinesse sources for 4.3, because some people like me, cant install custom kernels on 4.3 because we use patched modems to get signal, if you could that would be awsome.

BTW,here is what im talkking, http://xdaforums.com/showpost.php?p=47584571&postcount=1212, thanks man and for me this is the best custom kernel ever. i used it with cm and 4.1.2 easy to tweak and super stable! thanks in advance
[Galaxy S III Android Development] andip71:
Now we have already first instance of init.d move. Argh.

Boeffla-Config settings now take precedence over settings done in init.d scripts before.

Now I have the choice... either breaking Archis script, or yours.

Humpf, I need to sleep over that.

Andi
[Galaxy S III Android Development] eyegor:
Hey guys, I'm using this kernel with 4.1.2 atm. I'd like to upgrade to 4.3 but keep all my data and settings (as if upgrading through official OTA). Can someone suggest the proper way for doing so?