yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] i9000usersa:
Thanks so much for that answer. I've experienced some devs feel so self-important that they treat everyone else like they are beneath them, so I appreciate you taking the time to answer my questions in a helpful and polite way. And thanks again for continuing to support this device.
[Galaxy S III Android Development] andip71:
Mh.

I always was like that, users are as important as devs. Nobody can live without the other party.

And I hope time allows me to continue like that, being responsive as good as possible.

Andi
[Galaxy S III Android Development] LuciferIII:
First official LineageOS build was uploaded!

Hope to see support from Andi :o
[Galaxy S III Android Development] andip71:
Yep. Latest kernel is still up-to-date with LineageOS kernel sources.

Currently you can just use it.

Andi
[Galaxy S III Android Development] andip71:
[MENTION=7305969]LuciferIII[/MENTION], all:

Has anyone flashed this version already?

If so, you can confirm internal root is not included anymore? (Lineage will require a root addon script to be flashed, which is afaik not yet available).

As I don't want to use supersu, I would hold off flashing if internal root is not yet an option again.

Thanks

Andi
[Galaxy S III Android Development] LuciferIII:
Thats why i am currently scared to flash the official now.

I would have to flash supersu(a user reported it works),but it may conflict with the later comming root.zip

I would do it for testing but you know the "settings reset after restore from backup" bug.

Hope they fix that bug,its really annoying...

Btw,new thread for i9300 is open,but you probably know that.
[Galaxy S III Android Development] andip71:
Yes, exactly on the same lines I am thinking too.

For the OnePlus3, we have a TWRP version 3.0.4 already (unofficial), which has lots of Nougat fixes in the change log and might finally solve the settings reset after restore issues. To be tested though.

Ok, then I'll wait for the root.zip to arrive first. I am not in a rush :)

Andi
[Galaxy S III Android Development] LuciferIII:
Oh thank god they are doing something about it :highfive: :fingers-crossed:

I just love you developers

I will be patient :)
[Galaxy S III Android Development] LuciferIII:
Yeah,a user confirmed that root is missing
[Galaxy S III Android Development] andip71:
... as expected. Thanks for letting me know.

This means, I will wait for the root zip to arrive first.

Cheers

Andi
[Galaxy S III Android Development] Logan:
LineageOS root is up in site Downloads in extras section
[Galaxy S III Android Development] LuciferIII:
Update process failed...well...
[Galaxy S III Android Development] andip71:
Yep, only on S3. It worked on all my other phones so far.

TWRP error 4...

BUT - I realized although it failed, it was flashed correctly. At least I had root after the failed attempt.

Andi
[Galaxy S III Android Development] LuciferIII:
Ohh yeah!! Thanks!!
[Galaxy S III Android Development] Ghorrim:
I can confirm that. Root works fine after flashing the small lineage-root-zip, regardless of this error 4.
[Galaxy S III Android Development] umbrokhan:
boeffla-kernel-6.0-beta7-Lineage14.1-i9300-anykernel.recovery.zip how is Boeffla Kernel like on Lineage OS ?
[Galaxy S III Android Development] LuciferIII:
It's awesome
[Galaxy S III Android Development] andip71:
Hi all,

update of Boeffla kernel for LineageOS 14.1 is out.

Version 6.0-beta8

31.01.2017

Update: Updated with latest official LineageOS kernel commits as of 30.01.17, 08.00 CET

Change: Improvements in selinux script (could result in better compatibility to certain custom roms)

Change: Update with latest anykernel commits (credits to Osm0sis)

Enjoy

Andi
[Galaxy S III Android Development] Egli.Kasa:
Can i use l speed on latest lineage and boeffla kernel ? If yes , could i see any improvments in term of battery and performnace
[Galaxy S III Android Development] Marchiano88:
Hello! I haven issue. When I hold home button, the recent aps dont apear anymore...i'm the only one who experience this? Can anyone tell me how to fix it? Thanx, cm 13 with boefla kernel
[Galaxy S III Android Development] andip71:
What is this?

You should ask in the rom thread, not a kernel thread. Recent contacts is something not even known to the kernel, it is on a completely different layer.

Andi
[Galaxy S III Android Development] craP_cillA:
you could, but why should someone use a placebo?! ;)
[Galaxy S III Android Development] andip71:
Oh well, if that is something of that "famous mods that makes everything better" stuff, I fully agree.

They are 99% placebo, and I stopped years ago using that crap - sometimes they even have serious side effect. They also cannot do any miracles.

Thanks for sheding light onto it for me.

Andi
[Galaxy S III Android Development] Tech0308:
Latest Beta 8 kernel keeps on showing as incompatible kernel when using boeffla config 2.4.29. I've tried uninstalling and reinstalling as well as restoring previous backups. Clearing cache and dalvik only works temporary as after reboot problem starts again
[Galaxy S III Android Development] LuciferIII:
Yep,Lspeed fuked my wifi on 2 phones...Had to factory reset them...
[Galaxy S III Android Development] andip71:
You have a custom rom, not original LineageOS, or?
[Galaxy S III Android Development] Tech0308:
Yes, I have resurrection remixv5.8.0. After I posted they have released a update but the file is corrupted
[Galaxy S III Android Development] andip71:
Ok, would still be interesting to find out what they have changed to break compatiblity...

I analyzed today why dirty unicorns does not run on the OnePlus 2, and I found some real hard differences to official LineageOS. Differences I cannot bridge at all, also not by workarounds. So DU will never run on OP2 with my kernel.

When you could provide all log files you find in /boeffla-kernel-data, I could check what the issue with RR is...

Thanks

Andi
[Galaxy S III Android Development] craP_cillA:
i'm also using resurrection remix v5.8.0 (18.01. version) and boeffla beta 08 runs without a problem!
[Galaxy S III Android Development] steveengr:
I have boeffla kerner 6 beta 7 . Can i dirty flash beta 8 ? if i dirty flash beta 8 it will keep my settings ?
[Galaxy S III Android Development] LuciferIII:
Yes
[Galaxy S III Android Development] avikjan3:
Help please

how to install a version of the night? when we establish lineage-14.1-20170125-experimental-i9300-signed.zip and she does not want it to finish loading endlessly loads that do can not understand ??? then I want to set the nightly version and can not complete the endless loading

HELP PLEASE
[Galaxy S III Android Development] Jayair:
Hello, does this kernel support MHL connectivity
[Galaxy S III Android Development] Tech0308:
i cleared boeffla-kernel-data and these are the different logs from beta7 and beta8 kernels
[Galaxy S III Android Development] Tech0308:
After ROM update to v5.8.1 beta8 now works
[Galaxy S III Android Development] andip71:
Honestly, I do not understand your questions. What does "a version of the night" mean?

No. Does not, cannot, will never.

Only original Samsung kernels can provide this functionaliy, no CM or Lineage will ever be able to include it, as Samsung made this code proprietary.

Andi
[Galaxy S III Android Development] LuciferIII:
I start to dislike samsung even more.

I heard the camera server crashes on our device cause of something similar.
[Galaxy S III Android Development] avikjan3:
Lord Boeffla

when established lineage-14.1-20170125-experimental-i9300-signed.zip it endlessly loads and again I downloaded UNOFFICIAL version and downloaded all bil perfectly .I want to install NIGHTLY version. how to install do not know :(
[Galaxy S III Android Development] abelenki:
https://xdaforums.com/showpost.php?p=70901915&postcount=433
[Galaxy S III Android Development] avikjan3:
без сделать wiped не могу установить???

---------- Post added at 07:35 PM ---------- Previous post was at 07:35 PM ----------

without making wiped I can not install ???
[Galaxy S III Android Development] Ashraf Iraqian:
if You are using unofficial lineage or CM nightly 14.1 or R.Remix rom you can flash dirty without wiping Your data but you need first to install experimental version and reboot system then go back to twrp recovery and flash nightly version 31/Jan/2017

reboot system

that is all.

and if you come from another rom you need full wipe and just flash nightly version + gapps :)

good luck
[Galaxy S III Android Development] avikjan3:
Thanks for the answer . there now is lineage-14.1-20170129-UNOFFICIAL-i9300 and I want to go official version NIGHTLY. when it sets the experimental version loads indefinitely, there are a circle and everything does not start nothing.

if you can help
[Galaxy S III Android Development] andip71:
I think it is not very efficient to ask that on a kernel thread that has nothing to do with the experimental builds etc?

You should ask that in the rom thread, it is not very likely people here could help.

Andi
[Galaxy S III Android Development] andip71:
Good morning,

maintenance update for LineageOS 14.1 kernel is out.

Version 6.0-beta9

07.02.2017

Note: This kernel runs only correctly on LineageOS weekly of 06.02.2017 or newer.

For oder LineageOS versions, use beta8 kernel version.

Update: Updated with latest official LineageOS kernel commits as of 06.02.17, 08.00 CET

Enjoy

Andi
[Galaxy S III Android Development] abelenki:
it's written LineageOS/CM14.1 - Test:	6.0-beta9 for Samsung Galaxy S3 (i9300) on download page, but it's not here:

http://kernel.boeffla.de/sgs3/boeffla-kernel-cm/cm14.0_download/Test/
[Galaxy S III Android Development] andip71:
Jupp. I forgot to upload. ?

Will do that soon...

Hahaha.

Andi
[Galaxy S III Android Development] ZaneZam:
glad that i'm not the only one who does this from time to time :)
[Galaxy S III Android Development] andip71:
Oh yes, this is a result of doing too many things in parallel.

I am not good in multitasking [emoji1]

BTW: Uploaded meanwhile.

Andi
[Galaxy S III Android Development] abelenki:
boeffla-kernel-6.0-beta9-Lineage14.1-i9300-anykernel.recovery.zip is up.

much appreciated, Lord Boeffla!
[Galaxy S III Android Development] Egli.Kasa:
Thats deffenitly a bug with backkeys light even on boeffla app turned off when i touch the screen , they turn on
[Galaxy S III Android Development] andip71:
Nope, bullsh**t.

As written in ZaneZams thread already, I am able to achieve all combinations with some configuration.

Assumption: Latest Lineage weekly of 06.02.2017 and latest Boeffla-Kernel beta 9.

LineageOS team changed touchkey handling with latest weekly, so you need this combination!

1) touchkey lights work for touchkey touches and screen touches

- LED controlled by kernel = off

- Touch LED when touch screen = on

2) touchkey lights work for touchkey touches but not screen touches

- LED controlled by kernel = on

- Touch LED when touch screen = off

3) No touchkey lights

- LED full disable = on

Always put screen off for a few seconds after changing these settings to become active !

So what else do you want?

Andi
[Galaxy S III Android Development] i9000usersa:
I was having trouble with this last night as well after I flashed the latest weekly before I flashed the latest beta kernel so I had to completely disable the lights. This morning I flashed the latest kernel, saw your post and decided to try again. And now it seems to be working properly. I don't know if it was just disabling and re-enabling that did it or the latest kernel.
[Galaxy S III Android Development] andip71:
It is the last test kernel.

For latest LinageOS weekly, you HAVE TO use latest beta.

If you scroll up to the change log, I meanwhile put an extra notice in.

LineageOS introduced new features -> they changed the kernel code -> only beta9 has this changed code in.

So this time, Rom and kernel must be in sync. This does not happen frequently, but this time it is a hard requirement as their code change is not backward compatible and breaks either old or new rom.

Andi
[Galaxy S III Android Development] LuciferIII:
I flashed beta8 on newest weekly :laugh: and it worked :D?

But later i flashed to beta9 :svetius:
[Galaxy S III Android Development] i9000usersa:
Thanks.

On an unrelated note, and if it is too off topic please feel free to just say so, do you know anything about fast dormancy? I asked in the official Lineage thread but that thread has since gone on for a couple more pages with no one responding.

I had some battery drain so I installed BBS and found secril_fd-interface to be the most frequent kernel wakelock when I was not around wifi, which had kept my phone awake for 2 of 9 hours, and my phone was in deep sleep for only one percent of the time. I googled around and found that it was probably related to fast dormancy, but the solutions, which were toggling fast dormancy, are old and can't be applied on the latest Lineage OS.

I wanted to try to turn fast dormancy off to see if that helps but I couldn't find an easy way to toggle it. Do you know anything about fast dormancy?
[Galaxy S III Android Development] andip71:
Yeah, beta8 would also generally work on latest LineageOS, but the touchkey lights would behave mad.

Andi
[Galaxy S III Android Development] andip71:
I heard about it many times a few years ago when I still used my S3.

But I never experimented with it, as I never faced this drain (I guess it depends on a combination of modem firmware and your network provider).

So I was in the lucky situation I did not have to take care of that.

Sorry

Andi
[Galaxy S III Android Development] Egli.Kasa:
Dont know whats yhe prob buy even with the combo andi suggested cant seem to turn off the lights , every time i touch the screen they turn on. I am on latest lineage and latest boeffla
[Galaxy S III Android Development] andip71:
Don't know.

Working fine here.

Setup the switches as I explained above, maybe that helps.

But with latest Laos and latest Boeffla, I never had this mentioned problem.

BTW - this is not the first time they changed backlight handling in the past years. They already did it in the past and when I saw they change it again, I was almost about to kill them :)

Also in the past it took a while before everything was in sync again with roms (custom roms), so I expect some noise over the next days still. Hehe.

Andi
[Galaxy S III Android Development] i9000usersa:
Thanks for the earlier response about fast dormancy. Back on topic, the touch key lights are not working properly again. I thought it was, but now even with the toggles set to not light up with the touching the screen, they still light up. They are constantly on as I type this post.

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

Weird, I finished typing that post, left the thread and they stopped doing that.
[Galaxy S III Android Development] i9000usersa:
I've figured out how to reproduce this touchkey lights issue. If I leave the screen on for about five seconds, every touch of the screen afterwards will activate the touch key lights. They stop lighting up after I actually use one of the touch keys. Until I leave the screen for a few seconds again. Then the screen will activate the lights again. That is why when I left the thread earlier, I pressed the back button and it stopped doing that. I hope that makes sense. I have never taken logs but if you think that will be helpful, please point me to a helpful tutorial on how to take logs and I will learn and post them, as long as I can do it directly from my phone without plugging into my PC.
[Galaxy S III Android Development] andip71:
Can you please let me know how you configured the three switches in Boeffla-Config?

Can you please let me know step by step what to do to replicate this?

Logs would not help, the touchkey light driver does not log anything.

Then I will see whether I will have to change something or not. Usually the kernel is not in development anymore, so I might just remove the whole feature instead.

But so far I have found no way to reproduce an issue. So please tell me step by step what to do.

Andi
[Galaxy S III Android Development] Logan:
To get keys work as default (not activated in touching the screen like touchwiz).

Pick the needed illuminate time i prefer 1 second, then disable backlight keys in LOS settings and change kernel options like attached in screenshot.

It's been always like this even in cm13/cm12.
[Galaxy S III Android Development] Egli.Kasa:
Worked :D
[Galaxy S III Android Development] i9000usersa:
Okay. In the ROM settings I have setting>buttons>backlight = enabled for 5 seconds. In boeffla config I have touch led full disable = off; controlled by kernel = on; when touch screen = off.

To reproduce, leave the screen on without touching it for 5 seconds. Then start using the touch screen and the touch key lights will come on every time you touch the screen. To get them to stop coming on when touching the screen, use one of the touch buttons and then touch the screen within 5 seconds. Every time you touch the screen after that the lights will not come on. Unless you leave it alone for 5 seconds again, then the lights will come on every time you touch the screen again.

I hope that is clear, and hopefully you can use that information to debug this.
[Galaxy S III Android Development] Logan:
Try the solution i posted 3 posts above.
[Galaxy S III Android Development] andip71:
Yes, can reproduce now. But will take a bit of time until I can check and debug this.

What you can do as a workaround so far:

Go into settings, buttons, backlight and switch backlight off there. Then it behaves exactly as you want it.

Andi
[Galaxy S III Android Development] i9000usersa:
Thanks, it worked.

Thanks, I hope you can figure it out.
[Galaxy S III Android Development] andip71:
Well, bad news.

I just restored my previous LineageOS version with the older kernel.

And the behaviour was exactly the same there.

So no new bug has been introduced as such, and as the kernel is end-of-life and not actively developed anymore, I will not touch this. Sorry.

When you disable touchkey led in the rom settings, everything is as you like it. And this was exactly the same in previous versions.

Thanks for understanding

Andi
[Galaxy S III Android Development] andip71:
Yes, you are fully right. That was always the case, I just verified myself as well.

Thanks for spotting the solution.

Andi
[Galaxy S III Android Development] i9000usersa:
Thanks. I wonder why I didn't have the issue before, and I didn't change the settings. I thought there were also a couple of other people saying that this was different. It doesn't matter, because we know how to workaround it. Thanks for looking into it.
[Galaxy S III Android Development] andip71:
I thought so too initially, and I even restored my previous 1 week old setup with older rom and kernel.

And the result was - exactly the same behaviour.

But yes, the solution is simple and clear. So no need to beat a dead horse to death now :)

Andi
[Galaxy S III Android Development] Logan:
It's been like this from long time ago(cm12+) wondering thought it's normal thing as i used the logic to turn off backlight keys in settings as not controlled by system and then toggle it in boeffla config.

Before someone report about boeffla audio too

If Boeffla sound is enabled at Vol 52 earphones (any value doesn't matter) with headset connected if do you turn boeffla sound off the volume jumps to 57 which is default when do you enable the boeffa sound.

it doesn't return to phone's default value until do you unplug the headset then play any sound through internal speaker after this reconnect the headset.

I use boeffla sound as default at vol 52 from a year so not an issue for me.

Thanks :)
[Galaxy S III Android Development] hellcat50:
I can't say this enough but It's really great to see that you (and all the other active Galaxy S3 developers) keep the Galaxy S3 alive. Although Samsung isn't a developer-friendly company we see how far we've come with this phone! Long live the Galaxy S3!
[Galaxy S III Android Development] andrescm:
I don't know if anyone else is experiencing this but I'll post it in case anyone has a clue: I'm using LOS14.1 nightly 02-06 with Boeffla 6.0-beta9. Sometimes when I plug the charger the phone won't start charging. Unplugging and plugging again one or two times resolves the issue. So I thought it was a problem with my cell phone's USB port or the USB cable. However I've done a test 3 times now and always with the same result:

1. Plug the charger (if the phone starts charging right away, test can't be done. Try later).

2. Wait for several minutes, the phone won't start charging. Led is off, Boeffla Config says "no charger", etc.

3. Without moving the phone reboot into recovery (I have TWRP).

4. TWRP shows *I am* charging.

5. Reboot to system again, the phone charges and the led stays on.

As I installed Boeffla kernel right after installing LOS I can't tell if this is because of this kernel or if it comes with the ROM. But since this kernel does mess with the charging part I think it's worth to mention here. Has anyone else experienced this?
[Galaxy S III Android Development] andip71:
Mess? Well.. mess is kinda negative.

It does not mess with the charging part, it "controls" it a bit more.

And to answer your question: No, I have never seen that on one of my two S3 devices in the past 4.5 years.

Andi
[Galaxy S III Android Development] andrescm:
I'm sorry, my apologies, english is not my natural language and I used the wrong word. I meant that your kernel controls the charging port.
[Galaxy S III Android Development] andip71:
:)

Sounds indeed much better.

Andi
[Galaxy S III Android Development] Ashraf Iraqian:
Hi Mr.Andi

Thank You very much for this amazing job

but what about the battery led problem in last version of LAOS 2017/02/06

when i put my phone to charge my battery led working like a flashlight and it is paining my eyes!

now i am turned it off but how to fix it please.

another issue about the battery drain it is drain too much and more than past!

Regards :)
[Galaxy S III Android Development] andip71:
Hi,

you are in a kernel thread, not a rom developers thread.

So all I can say is:

Switch off the battery LED then completely in rom settings. This is for instance the first thing I always do. And wait for the next rom update, maybe this is changed again by then.

Battery drain - nothing is changed in the kernel versions for ages regarding battery drain. Battery drain also does not come from kernel as you can read on www.boeffla.de in FAQ but by userland processes, syncs, rom.

Sorry, but your issues are some I cannot help you with, those need to be addressed with the LineageOS devs.

Just to also say that again: I am not using my S3 anymore for more than 2 years, also the kernel is just maintained. So I cannot talk about real life experiences myself anymore for a long time.

Andi
[Galaxy S III Android Development] Ashraf Iraqian:
Thank You for reply :)
[Galaxy S III Android Development] tugay12:
Deleted
[Galaxy S III Android Development] Agonyy:
Can I report a bug here please?

Im using LoS 02/06 with the beta9 of your kernel. Basically, the function "Touch LED when touch screen" under the section "Touch key LED settings" (Display+LED Tab) doesn't work properly (I have this function off for the reason below):

When I lock the screen and unlock it, the key LED are off when I touch the screen, so this is good (because I want them to light up only when I touch them, not the screen. This is the reason that I mention before). But, if I touch them and then use the touch screen, they ALWAYS light up, so I think that this is a little bug(?). Hopefully you can fix this (if it's a kernel bug). Thank you for keep this phone alive!
[Galaxy S III Android Development] i9000usersa:
This has already been discussed pretty extensively in the last few pages. You have to change the ROM settings to disable the button backlights, then tick the option in the kernel config to control led. If you do this it will work the way you want. Andi has said because it works this way he is not going to try to fix it.
[Galaxy S III Android Development] Agonyy:
Thank you very much! :)