yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andrescm:
Just in case anyone experiences the same, wiping cache and/or dalvik/ART (don't know, I did them both at once) fixed the problem, the phone now charges every time I plug the charger without having to retry.
[Galaxy S III Android Development] tugay12:
Yes, wiping cache/dalvik solved my charging problem and don't know why...
[Galaxy S III Android Development] andrescm:
Did you by chance restore the Boeffla Config app from a backup?. Because I did after installing the ROM. Just discarding possible causes.
[Galaxy S III Android Development] tugay12:
No, I never backed up the Boeffla Config app. After flashing the Boeffla kernel, I always did a clean install.
[Galaxy S III Android Development] andrescm:
Thanks, that rules the app out of the equation :good:

EDIT: Now that I think of it, I did not wipe cache after flashing the kernel, that might be the cause. Will remember to do this next time I do a clean flash :)
[Galaxy S III Android Development] Logan:
Hey andi :)

I am in 13.2.2017 Nightly + beta 9 i am using selinux as permissive but i noticed that the selinux status turns to permissive after the boeffla config settings applied not in boot up is that normal?
[Galaxy S III Android Development] andip71:
The process is as follows:

Kernel starts in strict mode, just like any Android L, M and N stock kernel does.

When Boeffla-Config kicks and to apply the settings, it also checks if you deselected the Selinux check box in Boeffla-Config and if so, it switches it to permissive.

However, there are many apps out that can change the selinux mode, so chance for conflicts are quite high.

Andi
[Galaxy S III Android Development] gtsfreak:
boeffla config app not working on my i9300

running crdroid 7.1 rom

I did everything still no luck :(

I can't even upload the screenshot:confused:
[Galaxy S III Android Development] andip71:
Thanks for letting us know.

But nobody will work on that due to 2 reasons:

- "not working" can mean anything - you have to provide much more information

- crdroid is a custom rom, so yeah... possible it will never work there

Andi
[Galaxy S III Android Development] gtsfreak:
it worked

all I did was a reboot and voila it worked:good:
[Galaxy S III Android Development] LuciferIII:
Shouldn't you at least try to fix it by yourself before you ask here? Rebooting your phone is the first obvious thing you have to try as it fixes a lot of stuff :rolleyes:
[Galaxy S III Android Development] gtsfreak:
my phone freezed and restarted automatically for no reason and automatically the app worked:confused:
[Galaxy S III Android Development] medsalah:
Hello Andi! I want a profile "battery saving", can I content myself with the presets we have in config sitting apk: such battery freindly, battery saving...without any change.

thanks!
[Galaxy S III Android Development] kosmasgr:
Hello guys.

Can someone tell me the default entropy presets ( config app / miscellaneous 2 ) on latest beta 9 cm 14.1 kernel ?
[Galaxy S III Android Development] abelenki:
threshold read - 64

threshold write - 128.

actually, there is RESET button to bring those values back to default.
[Galaxy S III Android Development] kosmasgr:
Thanks :)

Kernel works excellent on latest cr droid , with zmoove / optimal gov
[Galaxy S III Android Development] facethepro:
Hi. I get error while flashing kernel (installation aborted status 6). ROM is crDroid 7.1.1. I had the same problem when i was using ressurrection 6.0.1.
[Galaxy S III Android Development] CygnusHyoga:
Latest twrp?
[Galaxy S III Android Development] facethepro:
I have CWM and i've installed boeffla kernel before (could not on 6.0.1 and 7.1.1)
[Galaxy S III Android Development] fonfox:
Crdroid v2.2 and boefla kernel works fine

Install with twrp3.0.2-2
[Galaxy S III Android Development] andip71:
Yes and no.

You can switch the app to tunables mode (if you have the donation version) and tweak the governor just as you like yourself.

If you found a superb setting which others also tested and confirmed to be fine, I could make it a permanent profile. But this is something I would need to do.

CWM is by far too old.

You need a state of the art recovery to flash a kernel with anykernel method.

Latest TWRP is recommended.

Andi
[Galaxy S III Android Development] dioen:
[MENTION=947981]Lord Boeffla[/MENTION], did you upload beta10 for i9300? On your site there is V10, but download page has only V9 ;)
[Galaxy S III Android Development] andip71:
beta10 should be out soon. I am just testing it and got an unexpected boot loop, so I have not yet uploaded it.

But it looks like my S3 is dying slowly and that was the reason for the boot loop.

As soon as I have confirmed beta10 is fine, I will upload it finally.

Andi
[Galaxy S III Android Development] dioen:
Ok, thank you :)
[Galaxy S III Android Development] andip71:
Good morning,

new update for LineageOS 14.1 Boeffla kernel:

Version 6.0-beta10

21.02.2017

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

Update: Improved compatibility when custom busybox installed

Enjoy

Andi
[Galaxy S III Android Development] baltics:
By 'custom busybox', do refer to the one built into LineageOS?

Will it work with earlier official lineage 14.1 builds too?
[Galaxy S III Android Development] andip71:
No. LineageOS (neither CM from Android M onwards) have a busybox on board.

What they have is a similar thing called toybox. But toybox and busybox do not conflict and can coexist quite nicely without issues.

What I mean is: Some people still use custom busyboxes (like Stericson etc.) on LineageOS, which is quite useless but they do. And for people that do that, compatibility with Boeffla-internal busybox is now improved.

Andi
[Galaxy S III Android Development] baltics:
Andi I was reflecting on the wisdom of the current trend of manufactures of mobile phones., including your current daily driver, the oneplus 3, not to include Ext Storage as an option.

My S3 developed 'screen shake' yesterday. I was pretty sure it was NOT a software issue, but just to make sure this morning I installed and ran two separate virus/malware checkers. No problems there.

Next I downloaded your new Beta 10, which I transferred to my Ext SD and then booted into TWRP. When I selected install TWRP opened my Ext SD card file where I keep Lineage Zips, the screen shake began. I realised it had to be a hardware issue.

I removed the Ext SD, cleaned the contacts and reinstalled it. No more screen shake!

The S3 is useless without an Ext SD, but they are frequently a source of problems.
[Galaxy S III Android Development] andip71:
Yes, sd cards are - of course - subject of mechanical changes and dirty contacts. So they are a cause for errors.

Fortunately modern phones (like the OP3T) come with 128 GB on board, and they can be easily extended by using USB-OTG sticks (I have one which comes with a usb-c connector, so I just plug it in). This is, for me, the ideal solution to storage problems on modern phones.

Andi
[Galaxy S III Android Development] andrescm:
Me too, last year I bought a USB-OTG drive mainly as a gimmick and now I use it everyday.

Beta 10 is working perfectly by the way, thanks for keeping it alive!
[Galaxy S III Android Development] baltics:
Talking of external storage, this is an interesting development. TWRP are developing a new version of their recovery which will enable direct back-up to a PC (and I assume MacBook), using a command line on the computer.

The advantage being that there is no need to make a back-up on the device first.

This development is probably aimed at those reliant on internal storage.

Those using SD cards as external storage may find it easier to just simply connect the external storage to the computer using a card reader.

https://www.xda-developers.com/twrp-v3-1-0-will-bring-support-for-backing-up-directly-to-your-pc/
[Galaxy S III Android Development] andip71:
Very interesting development indeed.

BUT here is the catch: When you ever tried to transfer bigger files via adb, you notice this transfer is incredibly slow. And when I say slow, I really mean slow... by far slower than even mtp connections.

So I could imagine such a backup takes ages.

However, still a good add-on option of course.

Andi
[Galaxy S III Android Development] JimTimmler:
boeffla config v2 says no kernel

Hi there,

I recently flashed lineage-14.1-20170221-nightly-i9300-signed.zip.

Then I flashed boeffla-kernel-6.0-beta10-Lineage14.1-i9300-anykernel.recovery.zip with latest TWRP 3.0.2-2.

But boeffla config v2 always tells me I that a have no compatible kernel installed or that I am using xprivacy.

The latter is not true. And I expected this kernel version to be compatible because it is in its name :)

I never had trouble flashing 13.1 kernels in CM 13.1

What am I doing wrong?
[Galaxy S III Android Development] tugay12:
Perform factory reset > Flash LineageOS ROM > Flash Gapps > Reboot system. Reboot in recovery mode again, flash boeffla kernel zip and reboot. Maybe it works.
[Galaxy S III Android Development] JimTimmler:
Hi,

that is exactly what I did.

And I don't want to do it again, because I just finished customizing everything like I had before with 13.1. :)

Another suggestion?
[Galaxy S III Android Development] tugay12:
Could be kernel zip file corrupted? Did you get any errors during install? Try downloading again and wipe Dalvik ART/Cache then flash kernel from any SD card.
[Galaxy S III Android Development] Logan:
Sorry for out of topic question andi.

Does anyone have latest official cm13 Nightly zip? (latest snapshot bootlooped 5 times in December didn't like it)
[Galaxy S III Android Development] JimTimmler:
No errors during install.

I will try beta 9 or beta 8, maybe they work.
[Galaxy S III Android Development] tugay12:
Beta 8 or 9 may not be compatible with the latest build.
[Galaxy S III Android Development] JimTimmler:
I solved it. Since Marshmallow I always flashed SuperSu after flashing boeffla kernel.

It looks like nowadays you shouldn't do that.
[Galaxy S III Android Development] elsaedy:
please sir...i hope to port this amazing boeffla kernel for note2 n7100.(4.4.4) ..i think i9300 and n7100 have same cheap...thanks
[Galaxy S III Android Development] andip71:
Well.... it is even noted on the homepage you cannot do that anymore in the installation instructions.

You could have saved a lot of time by just reading that.

SuperSu is... **** enough to restore a stock kernel under some circumstances.

Hehe, never ever.

My work on Samsung crap devices is finished for long time now. Read FAQ on www.boeffla.de for more information.

Sorry

Andi
[Galaxy S III Android Development] baltics:
Ouch ....

It may provide developers with headaches, but 5 years on it still has a strong global following amongst the custom ROM community and amongst those who use your kernel.

https://www.droidmen.com/lineage-os-crosses-500000-installs-oneplus-one-popular/
[Galaxy S III Android Development] Bart11666:
Latest beta will be ok with todays weekly or wait for update?

Cheers and thank for support!

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] LuciferIII:
Works fine for me.
[Galaxy S III Android Development] andip71:
No kernel code change in LineageOS repos since 15. Feb 2017 - so latest kernel will run just fine.

Andi
[Galaxy S III Android Development] TEKNOKA:
thank you
[Galaxy S III Android Development] JimTimmler:
doze default

Hi,

I recognized that "doze" is on by default in the kernel. Does it work without breaking the reception of whatsapp messages and so on while it is active?

Just wanna know because I read a lot of bad stuff about doze and the S3.
[Galaxy S III Android Development] andip71:
To correct you:

Doze is on by default in all roms since Android M. And it is not even a kernel but a rom function.

While many people like it, I do not and disable doze always as it indeed delays incoming events for me (this is the reason I put the switch into my app). And I have no negative effect on battery due to Doze being on even.

Andi
[Galaxy S III Android Development] tugay12:
When I open the Boeffla Config App, this problem appears. It only fixing when I flash kernel again. But after some time, appears again. Using latest kernel and config app. Is anyone facing with this problem?
[Galaxy S III Android Development] andip71:
This can have lots of reasons, you need to find out yourself unfortunately.

In short: "something" blocks Boeffla-Config from starting when you boot your phone.

I guess you have done already everything mentioned in the troubleshooting section of installation instructions on www.boeffla.de.

There the most obvious reasons are covered.

Andi
[Galaxy S III Android Development] LuciferIII:
Greenify, any kind of bootmanager,or the build in one from android can block it from startup
[Galaxy S III Android Development] Tech0308:
I once had that problem, i had to restart a dozen times before it wors.
[Galaxy S III Android Development] g104:
[MENTION=947981]Lord Boeffla[/MENTION] literally, after flashed the latest twrp 3.1.0-0, the overview page still showing 3.0.2-2-99af7666-dirty.
[Galaxy S III Android Development] baltics:
Yep
[Galaxy S III Android Development] Logan:
3.1.0-0 Here Try reseting boeffla config data in settings i do reset it every while.
[Galaxy S III Android Development] sunny1234590:
Different S3 has different ASV/PSV level?
[Galaxy S III Android Development] baltics:
Resetting and clearing data and a reboot did fix it. Thanks.
[Galaxy S III Android Development] Logan:
Hey andi

Is it possible to have LMK values that's for more for multitasking, i feel the LMK values presented in Los default kernel and yours are in a way a bit aggressive for example poweramp gets killed in a little while at background but not in cm13.

Thanks
[Galaxy S III Android Development] LuciferIII:
There is a switch that lets you change the values manually,but there are no presets,you will have to find them out by yourself.

Google is a big help
[Galaxy S III Android Development] g104:
never mind not working. literally, i ended clean install since i'm going to flash new boot-loader.
[Galaxy S III Android Development] andip71:
This is very likely.

Ths issue is: TWRP does not provide any version information to the outside world. Which is bad, but it is the truth.

Means: All I can do (and this is what I do) is to parse the log file of TWRP (when there is one) for latest version information. But this can take a while to get refreshed, as it is with log files.

So, this information is a bit "unsharp" after you freshly moved to a new TWRP version.

Sorry, not more I can do apart from removing this display out of my app again.

Or just let's call it "alternative facts" the app displays here sometimes, haha.

Likely, yes. It is the binning level that says something about manufacturing tolerance of the SoC (CPU in easy words), and therefore about the quality.

Just change them as you like. I believe you will find plenty of documentation about LMK values for the S3.

I cannot contribute anymore, not using my S3 anymore for a veeery long time (2 years or more...).

Andi
[Galaxy S III Android Development] renzreyes21:
Lord boeffla, Is there a way to fix this ? My S3 won't run in all cores.. Even when i stress the cpu (full load) its still just 3 cores online.. When i try to online that core using terminal its working.. But then another core will shut down.. (Its like just replacing) I'm using beta 10 stock settings..

I'm sorry I'm lost at words I'm not good in english
[Galaxy S III Android Development] andrescm:
Check your governor settings. The default is pegasusq standard.

When I want to use other apps when listening to music in the background I switch to these settings:

Foreground apps: 24

Visible apps: 33

Secondary servers: 41

Hidden apps: 90

Content providers: 123

Empty apps: 132

Note however that while this configuration is good for keeping your background music player alive, the rest of the phone will suffer for it, being generally slower. There's no perfect configuration sadly, the S3's RAM is a little small for today's applications.

In case you want to return to the default values, these are:

Foreground apps: 72

Visible apps: 90

Secondary servers: 108

Hidden apps: 126

Content providers: 144

Empty apps: 180
[Galaxy S III Android Development] LuciferIII:
Or use the LMK switch to revert the settings ;)
[Galaxy S III Android Development] andrescm:
You are right! :highfive:
[Galaxy S III Android Development] Jack123hello:
I'm just wondering: is there any possible way to install more RAM on S3? ?

I know, this is a silly question ?
[Galaxy S III Android Development] craP_cillA:
yep, super silly! :eek: and to answer that super silly question: nope! ;)
[Galaxy S III Android Development] andrescm:
Enable zram [emoji1]
[Galaxy S III Android Development] andrescm:
Thanks for the explanation and please don't remove it, it's a very nice feature and at least in my case the app showed the correct version right away after updating TWRP.
[Galaxy S III Android Development] andip71:
Usually, in 99% of cases it does straight away show the correct version.

The key is... TWRP needs to not only be installed but also one time "used" for something, so it writes it's version information into the log file (where Boeffla-Config can pick it out).

Andi
[Galaxy S III Android Development] fndpena:
Tema said vibrations would not work with Omnirom kernel... :(

Is that confirmed?
[Galaxy S III Android Development] andip71:
No, with my latest omnirom kernel (which is not yet out) it vibrates...

I currently have problems with root access however :(

No app requiring root is working on V5, I am searching...

Andi
[Galaxy S III Android Development] fndpena:
So, if I flash your Omnirom CM11 2.0-beta1 over V5, root won't work...
[Galaxy S III Android Development] jcvr:
Can confirm it. All working fine. Thanks
[Galaxy S III Android Development] andip71:
You do not have root problem?
[Galaxy S III Android Development] tisazalay:
I've got the omnirom alpha1 you released some time ago, I'll try it when I download temasek's v5 and see what can I come to...

Thanks for your work.

EDIT: Almost.... found the beta1, will try the newest...
[Galaxy S III Android Development] maddes1402:
Just flash latest supersu in recovery, Andi. Root access should be back.

Looking forward to your new Omni kernel!

Regards, Matt

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] leo_nidas:
I have Omni 4.4 (20112013) from XpLoDWilD and supersu working fine with your kernel 3.0.101 - Omnirom 2.0 - beta 1 20131118 :)
[Galaxy S III Android Development] jcvr:
Root working fine with super su 1.72B. Vibration also working.
[Galaxy S III Android Development] andip71:
Reaaally?

I never flashed SuperSu on a CM based rom so far. Typically they come with working root?

:confused:
[Galaxy S III Android Development] ekie84:
Just tested it,i also got no root,vibration working fine

Send from my GT-I9300 using Tapatalk 2 (Temasek CM11 v5 / 3.0.101 Temasek CM11-1224)
[Galaxy S III Android Development] andip71:
I think it is related to SELINUX. I will give it a shot...

Andi
[Galaxy S III Android Development] leo_nidas:
Your default profile loaded

Working Root on super su :)
[Galaxy S III Android Development] cornelha:
SuperSU works with a trick. Flash latest version, open settings, disable root then re enable it. Really odd
[Galaxy S III Android Development] fndpena:
[MENTION=947981]Lord Boeffla[/MENTION]

I wanna update to V5, but not without your kernel :(

So the way to get it working is flashing omnirom version and latest supersu?

Then everything is gonna work?
[Galaxy S III Android Development] maddes1402:
Yes, Cm based Roms have never included supersu because it isn't open source.

But Omni isn't based on Cm and additionally Chainfire is a contributor of Omni. So it would make sense. But tbh I haven't looked more closely in the zip file or source code until now :o.

If you really wanna feel butter on our galaxy S3 for the first time and have the impression that 1 gig of RAM is enough the latest experimental build is a great experience.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] temasek:
Maybe set selinux to permissive?
[Galaxy S III Android Development] leo_nidas:
Yes working Stable :)

Flash rom

Flash gapps PA

Flash supersu

Flash kernel :)
[Galaxy S III Android Development] fndpena:
Supersu before kernel? Is that correct?

Is this the latest supersu?

http://xdaforums.com/showthread.php?t=1538053

About gapps, I'll keep the kk gapps from Tema (less apps than PA version).
[Galaxy S III Android Development] andip71:
Guys, sorry to say - but it is not a real solution.

I did some investigation and foud it:

- switching off SELINUX was good, it fixed some issues with filesystem access

- but... the Ominrom ramfs I use in my Omnirom kernel is not compatible with Temasek

So I am afraid, unless I do two kernel branches for it, it will not gonna work.

Or Tema can try to put the Omni initramfs in.

After I did it, all is running fine.

Was just a quick update, need to go back to work now.

Andi
[Galaxy S III Android Development] tugay12:
[MENTION=947981]Lord Boeffla[/MENTION]

Is any problem occur if I install the Boeffla-Config app as a system application? I think this action will remove the blocks of 3rd party apps.
[Galaxy S III Android Development] andip71:
Yes, the app will warn you during every start it should not be a system app.

System apps have other issues (updating not always working fine), so I do not recommend it.

But of course you can try and share your results. Maybe meanwhile making it a system app is not an issue anymore.

Andi
[Galaxy S III Android Development] stratonz:
i9305 porting

Hello [MENTION=947981]Lord Boeffla[/MENTION],

I've tried to port your kernel to my I9305, from your latest cm-s3 sources. All the versions I've realized, changing something in defconfig file work, but I've always a blackscreen crash or a bootloop when the phone goes in deep sleep mode (or I think so...). I can't realize where is my problem. Could you take a look at my defconfig and at dmesg.log to help me in individuate the error?

View attachment 4075399

View attachment 4075400

View attachment boeffla_defconfig.txt
[Galaxy S III Android Development] LuciferIII:
I9305 and I9300 are not the same,this kernel is ONLY for i9300.
[Galaxy S III Android Development] stratonz:
I know, but a porting is possible and already done. The most of the hardware is the same.
[Galaxy S III Android Development] andip71:
Unfortunately no. The i9305 is not as similar to the i9300 as many think.

And as I stopped developing actively for Samsung phones + I am really busy with my other phones, I cannot work into that.

Sorry

Andi
[Galaxy S III Android Development] tugay12:
Ok, I installed Boeffla-Config as a system app and tested many times. For now, there are no blocks during boot. Maybe there will be problems in the future. I will test it and see myself.
[Galaxy S III Android Development] LuciferIII:
You may already know this,but after a system update the app will be removed (i did that for another program i installed as system app)
[Galaxy S III Android Development] abelenki:
no, the app is not removed after the system update, just a kernel (so you have to flash it again). please do some reality check before posting.
[Galaxy S III Android Development] tugay12:
Yeah, I know. But now I'm making a flashable zip file to quickly install this app as a system application.
[Galaxy S III Android Development] LuciferIII:
Read again,than do a reality check yourself.

You are really annoying,and i reported you twice this weak,this time i hope the xda admins remove you from here.
[Galaxy S III Android Development] craP_cillA:
but he is right! the app won't be removed if you do a (dirty) system update! ;)
[Galaxy S III Android Development] tugay12:
Actually, this app is not a part of system. I think it's not gonna be removed on any dirty flash.
[Galaxy S III Android Development] Logan:
You need to create the app addon ".sh" at System/addon.d/...

(I used to add apps inside gapps.sh pretty easy and works)

Check this: https://xdaforums.com/galaxy-s3/development/cm11-temaseks-unofficial-build-v50-t1797109/post29576699