yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Clark789:
The same applies for me. I think the OPO is a nice device and the perspective to use the awesome boeffla-kernel is quite appealing, but i need a sd-slot and i would very much appreciate to change the battery. Besides this i like the idea of having a device working with USB 3.0. So, one day i think i have to move to the SGS5... :)

Regards

Clark
[Galaxy S III Android Development] Mosh Edd:
Thanx for always being this honest, it's the reason I Love Boeffla even more. Thanx for that bro, sorry I never searched. I actually don't also charge mine while off, lol. just out of anxiety coz I heard it works and I always thought it was a bootloader thing to make it work. your kernel is perfect just the way it is.

P.S. I don't use boeffla sound with TW 4.4.2 coz whenever I enable it, my callers complain a lot that there is too much noise from my end. I don't know why maybe some settings but it's not such a big bother. CHEERS. :p
[Galaxy S III Android Development] blue_moon:
its not important for charging when phone is off. but when battery goes to %0 and phone off i plug the charger and phone is opening and after its closing because %0 charge. this takes a long time opening and closing again and again.
[Galaxy S III Android Development] SignetSphere:
Ideally you don't want your phone to reach fully drained state on a daily basis because you're just killing your battery. Most only do that on a monthly basis to re-calibrate the battery's "thinking" so it can provide the longest charge possible. Now the reason it's turning off immediately after you reach 0% is because you haven't let it charge for a while, wait for it to be charged for around 5 mins and turn it on again. It should hold enough charge for to be turned on properly.
[Galaxy S III Android Development] Dabidue:
l8est Update

[MENTION=947981]Lord Boeffla[/MENTION]

Nice update, thanxx for redesign and adding off option on Config V2.1.56. :good: :highfive: :victory:
[Galaxy S III Android Development] D00ky:
As I've said before, problem persists if I switch to TW launcher.

[MENTION=947981]Lord Boeffla[/MENTION]

It seems that also Config app takes longer to open on last two versions. When I click on icon I have to wait for almost 1 second to open. That also never happened before. This strange behaviour started when you send out version with themes. Will try to install older version to check if the problem persists.
[Galaxy S III Android Development] andip71:
You are welcome.

The "longer loading" I can confirm. But it is only a cosmetical effect.

Before, it was opening up a blank screen for 1 second, before the app continued.

Now it does not open this screen up anymore.

This was required for the support of multiple designs, as it would look a bit weird if the app opens hard in holo design and then switches. That is why I open it up with transparent design first, until it is really loaded and active.

So, the app is not a millisecond slower due to that, just the perception is a bit different.

But for the rest of the issues, without a video I cannot say more. Sorry.

Andi
[Galaxy S III Android Development] andip71:
Naaah... if it only were like that ;)

Andi
[Galaxy S III Android Development] metalgearhathaway:
:D

Sent from my GT-I9300
[Galaxy S III Android Development] putti71:
Hi everybody, perhaps you can help me out.

I tried Agni kernel and wanted to come back to boeffla, but that's not working like it's supposed to.

It's booting, but in config app settings will not stick and after a reboot it says that something is wrong.

Before I flashed from Agni to boeffla, I used a kernel cleaning tool (ultimate kernel cleaner).

Now I had to go back to Agni again.

I could also write that in Agni kernel thread, bit don't want to cross post again.

Please help me out.
[Galaxy S III Android Development] andip71:
Clean all content from your /system/etc/init.d folder.

Either by a file manager, or directly in Boeffla-Config Action-Menu.

After that it should work.

When I am not wrong, Agni Kernel uses init.d scripts to configure the kernel. And they conflict if the kernel is not installed anymore.

Andi
[Galaxy S III Android Development] D00ky:
Here are two videos one for TW and one for Nova launcher. In videos I've opened config app first from home screen, than from drawer and than Greenify app from drawer. Hope it helps. I will try to install last working config app to confirm this behaviour only on the latest versions.

Links to videos:

https://www.dropbox.com/s/2g3nfhszv7v3blj/Nova.mp4?dl=0

https://www.dropbox.com/s/095m2bo7bdsogh7/TW.mp4?dl=0
[Galaxy S III Android Development] mayday2:
Is init.d empty? If not, please try to empty it.
[Galaxy S III Android Development] andip71:
Interesting, whatever I try to do here (with both Trebuchet and Apex launcher), I do not have this behaviour.

Now the question goes out to the other Nova users: Can you replicate what is shown in the video?

Last question... is that really kind of a big issue for you? Honestly? ;)

Andi
[Galaxy S III Android Development] D00ky:
Well actually it is a big issue for me. Wen I have a time I will try to install older config app to confirm that issue.

---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------

Andi could you include pre themes version of config app on your download site? There are only last two which if I am not mistaken they are both with themes.
[Galaxy S III Android Development] andip71:
????? May I ask why? It is only cosmetic, not functional. So how can it be a big issue?

Sorry, but I really do not get it.

Have added version 2.1.54 of the app again to the download folder, this version was the last without theme support.

Andi
[Galaxy S III Android Development] putti71:
Okay, I will look at that. Thank you.
[Galaxy S III Android Development] andip71:
Hm, did not answer that so far.

I am not really optimistic about that. Yes, technically I can implement anything. But LMK settings are something that are not "stable" in a way.

They are really different on CM and Samsung roms, etc.

Also there is no "common practise" on how to improve LMK settings.

So I doubt it will make lots of sense to provide profiles for it.

For Samsung, I usually increase all LMK values by 10 MB. For CM and Omnirom, I do not change them at all.

But this is what I believe gives me what I need. I am sure 10 other users would have 10 different opinions.

That makes it really challenging...

Andi
[Galaxy S III Android Development] D00ky:
It is a big issue for me not critical. I really don't like graphical glitches, stutters and other cosmetic related things. That is why I replaced stock launcher with Nova, heck I even rooted because of this to gain access to all parameters that can make UI smooth and free of cosmetic glitches. It is really strange that no other app on my S3 behaves like that and a few of them support themes.
[Galaxy S III Android Development] marenp:
I am on back-to-n00t and with Nova and did the same thing on video and i don't have that behaviour of config app at all. Same thing is with TW.
[Galaxy S III Android Development] dyurno:
Anyone best setting

Hey guyz, anyone have a the best setting backup for galaxy s3 with omega ROM??!.. v.60 :confused:

Thanks
[Galaxy S III Android Development] putti71:
Thank you, that did the job. Glad to be back again:)
[Galaxy S III Android Development] andip71:
Any update of your test with the 2.1.54 version, which did not yet have theme support?

Cheers

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

Is it a good idea to use an app, called ram Manger, in order to set Lmk settings?

And if I use this app to make a swap file (256mb)?

Or would you rather say, stay away from that app?

But I really don't know how to use the Lmk settings.
[Galaxy S III Android Development] D00ky:
I've just tested it and the issue is gone.
[Galaxy S III Android Development] MIKEMON:
Do not use other applications on the configuration !!

Everything can be set in Boeffla config.

It does not work all as it should ..

The application is set for all kernel configuration parameters for use.

There is nothing the best nor the worst, all you have to try

Big thanks to friends Lord Boeffla§ZaneZam for governors and thanks to all the loyal users.
[Galaxy S III Android Development] andip71:
Interesting. Interested in a test version once I am at my pc again? (maybe in 1-2 days)

I would like to try something simple...

Andi
[Galaxy S III Android Development] D00ky:
I am always here to help.
[Galaxy S III Android Development] putti71:
The problem I have is not the config app, it's the Lmk settings, which I am to dumb to set to be a bit more aggressive. When I was on agni Kernel, there was something like Lmk default, medium , aggressive, more aggressive ... Here in Boeffla app, I could do it much more precise, but my lack of know how is the problem.
[Galaxy S III Android Development] vinodr5371@xdaroms.co.in:
How to use MIDNIE Setting in this kernel what is the use of that , i dont about too much about this.HELP

thanks in advance..
[Galaxy S III Android Development] vladakster:
MDNIE settings are not for stock based ROMs. You can use it if you are on CM ones. In that case, you're on wrong forum!
[Galaxy S III Android Development] andip71:
You have a PM with a link to a test version.

Please report back.

Well, as said, I strongly believe there is no universal profile possible for LMK.

I mean, I can reverse engineer the agni profiles and let you know what they mean in terms of LMK values. But not sure if this is a good idea.

Of course you can use the other app you mentioned as well to select some LMK profiles there.

If you found a profile you like, you can even start Boeffla-Config and see what is configured that time. Then you could write down that values for the future and configure it in Boeffla-Config only by deinstalling the app again.

But I do not know what you exactly want to achieve with your LMK settings, whether you want to address a specific issue etc etc, so hard to give you some advices.

Correct. In Samsung roms (and the kernel in this thread is only for Samsung roms), the MDNIE settings can (and SHOULD !!!) be configured in the rom settings under display.

Andi
[Galaxy S III Android Development] MIKEMON:
For all

stick to stable levels, android itself handles these problems.

LMK set to values likely dropped rather than a cause severe problems.

Ram manages the system and accordingly adjusts the operation of the system.

thanks to all
[Galaxy S III Android Development] lsalamun:
[MENTION=947981]Lord Boeffla[/MENTION], thanks for the most awesome kernel for the S3, i doubt i'll see anything like that in the G2 section, wish you the best of luck in the future! :)
[Galaxy S III Android Development] drjat:
[MENTION=947981]Lord Boeffla[/MENTION], you mentioned a few months ago that you might buy S5. Is this still your plan. Asking because I am due for a phone upgrade and want to buy a device which will be supported by you. Regards
[Galaxy S III Android Development] Elemy:
But he bought oneplus one. Look at his kernel website http://www.boeffla-kernel.de/
[Galaxy S III Android Development] corsicanu:
[MENTION=947981]Lord Boeffla[/MENTION] not sure if it's only me but the new version of app (57) FC when trying to change the preset. I'm on qs-3.1. Tried clearing app data, reboots after reboots and still nothing.. The only way to change the presets was to revert to 56. I'll try tomorrow to logcat this issue.. Thanks for all your support for our beloved device!! Cheers!
[Galaxy S III Android Development] andip71:
I do not know the G2 section at all, so I do not know about dev support there.

Hm, but no plans on my side to go for a G2 now.

Currently, I am honestly more than happy with the OnePlus. Finally a phone which does not block any development and allows me to root and modify whatever I want without blowing stupid fuses or increasing flash counters etc.

I do not have strong plans for a S5 due to that, but maybe I get hold of one soon, then I would look at it.

Yeah, finally a bug. Although it surprised me version .56 works and .57 does not.

But yes, if you could manage to get me a logcat, this would certainly help me a lot to see whats buggy in it and fix it.

And what also would help me:

- bc.log from your boeffla-kernel-data folder

- to export the two profiles into .bcprofile files and send it to me

You can send all data to support@boeffla-kernel.de

Thanks

Andi
[Galaxy S III Android Development] andip71:
Update: Thanks for the log files. I already suspect where the bug has been introduced.

(I assume all people having no external sd card in use have this bug now)

Will work on a fix throughout today.

EDIT: User supplied with a test version, awaiting his feedback. If it is ok, I will roll the app out immediately.

Thanks

Andi
[Galaxy S III Android Development] Agaranda:
Hi Andy.

After two years enjoying your excellent kernel I must say goodbye because I've got a Note 4. I'm sure I'm going to miss your kind support and your Boeffla sound.

Thank you very much
[Galaxy S III Android Development] andip71:
Too bad, agaranda.

But that is life, time must move on. Friends come, friends go.

Maybe we see each other again on day on another device.

Cheers and thanks for all the support in the past years

Andi
[Galaxy S III Android Development] viktor92:
Maybe this is a stupid question, but still I can't believe what happened again with another Sandisk microSD. This weekend I was using AD 3.0 with latest boeffla beta 8, and all worked great, but when I tried to make a nandroid of the rom, it was made partially, after that I had problems to write to the card, at the point that it became readonly. Now on KK back to n00t again, no matter I try to format (quick or slow) or erase anything from it, the content remains unaltered. The second time with a sandisk micro sd on different phones. Can be all this caused by corruption on the exFat formated card, and used on CM rom ??
[Galaxy S III Android Development] andip71:
I know the S3 is veeery sensitive on external sd cards. But have never heard about such a story.

I would plug the card into a card reader now, connect it to Windows and see what windows says (corruption or not etc).

No, have not really any other ideas. Never had trouble with my sd cards, and I have sandisks also everywhere...

Andi
[Galaxy S III Android Development] viktor92:
I can erase all I want, format many times, without not a single error, and the phone shows the card capacity all available as it's empty, but I reboot the phone and all the stuff is right there in the card. I can put the card in a card reader, format in low level, anything you want, that the pc will tell you that all it's OK, but you extract and reconnect the card reader... and all is there like written in stone...

The second Sandisk (the first was a 32gb purchased at amazon, used on a Moto Defy) and THE LAST ONE.

Now I will pick up a new kingston 64 gb that I've purchased minutes ago...
[Galaxy S III Android Development] Hidden-Hunter:
hi guys

i sry for quesion

what is FuelGauge *#0228#? and how to use this code ?

tnx
[Galaxy S III Android Development] corsicanu:
Mistyped or did i missed something? :)
[Galaxy S III Android Development] mildavidec:
The same happen to me too with SanDisk 64GB , 2 times and SanDisk always replace the card in warranty.

Looks like it's a know problem that should be fixed now.
[Galaxy S III Android Development] JustArchi:
Had similar issue on my Xperia M.

I ended up totally repartitioning the external sd card.

Best way is the oldschool way. Enter recovery, connect your phone through adb, enter shell, and:

fdisk /dev/block/mmcblk1 (open partitioning on your external sd card)
o (create new empty DOS partition layout)
n (create new partition)
p (primary one)
1 (first number)
enter + enter (accept defaults)
w (save changes and exit)
mkfs.vfat /dev/block/mmcblk1p1 (format first partition to VFAT, also known as FAT32)

I don't trust Windows, neither other magic programs, I trust good old fdisk and mke2fs :).
[Galaxy S III Android Development] metalgearhathaway:
Latest Boeffla Config playing up, zRam keeps turning off, so have deleted Boeffla folder and uninstalled app, rebooted phone installed latest config app again and my profile and will monitor to see if fixed or not and will report back :eek:
[Galaxy S III Android Development] viktor92:
Archi I did it until:

w (save changes and exit)

But can't execute:

mkfs.vfat /dev/block/mmcblk1p1

don't know how :(

I've formated the card from windows and from the phone, and nothing changes...

pd.: the kingston 64gb I've purchased today format only 26gb....
[Galaxy S III Android Development] lucifer76:
I have 1 little problem. I use QS 3.1 and boeffla kernell 6.1 beta7. If i set governor to zzmove and reboot, after reboot is revert to pegasus.

All setting in BoefflaConfig work ok, CPU speed, CPU undervolt, etc,only governor its forget after reboot...
[Galaxy S III Android Development] andip71:
Is this still an issue or is it now sorted?

I have to admit, I did lots of changes to the app internals and cannot guarantee I implemented some bugs.

But I tested zRam here on my side, and it appears to work fine. Settings stick...

Check what kind of init.d scripts you have in /system/etc/init.d.

It is 90% a script (or an app) that changes governor back.

If not, there seems to be a slow rom start. For that, enter some startup delay (e.g. 10 or 15 sek) into Boeffla-Config's settings. This will delay the governor to be applied to a bit later during the start.

Andi
[Galaxy S III Android Development] 99x:
Fat32 can only format 32GB partition
[Galaxy S III Android Development] lucifer76:
Tnx for quick answer. I put 30 sec delay to config, no use, kernel start with pegasus.

In init.d i have 2 files: 85sqlite and 99SuperSuDaemon. I look in this file, nothing about governor.
[Galaxy S III Android Development] metalgearhathaway:
4 restarts and overnight all seems to be fine, so clearing config folder and uninstall have fixed issue. Self solved, I suggest everyone checks their settings are still OK as well and if not to do the same thing.

Sent from my GT-I9300
[Galaxy S III Android Development] viktor92:
Some programs can format FAT32 beyond 32gb, anyway I've tried exFat format (even NTFS) and the size showed it's the same. I have extremely bad luck or it's the best fake kingston I've seen by far...

pd.: the kingston validation page doesn't exist anymore, it was confirmed to me by kingston support... :(

---------- Post added at 06:26 AM ---------- Previous post was at 06:24 AM ----------

Here the program is running perfect as always :D
[Galaxy S III Android Development] River2418:
Updated to 2.1.58 yesterday

Just checked app now and is says zRam status 'disabled'.
[Galaxy S III Android Development] andip71:
... which can be still ok if you have not activated zRam any time before.

It is not standard on the 5.4 kernel.

Andi
[Galaxy S III Android Development] andip71:
Stable releases !!!

Hi all,

finally there is the time to call a good beta a stable version.

And this is what I am doing now for all 3 Samsung kernels:

Version 5.4 stable (for Samsung Android 4.3)

Version 6.1 stable (for Samsung Android 4.4.2 ported roms)

Version 7.1 stable (for Samsung Android 4.4.4 ported roms)

Only change compared to latest betas is the update of the internal su to version 2.40.

Important note: All three kernels are now put on status "

maintenance

".

This means, they will not receive any new features anymore. They will however be maintained in case significant updates to base sources or ramdisks are required. Same goes of course for really significant bugs when they should appear.

And no, it is not the end of Samsung Boeffla-Kernels for the S3. But in my opinion, there is nothing more that I would like to add.

So I call it a final now, as we can expect nothing coming anymore from Samsung side.

Enjoy

Andi
[Galaxy S III Android Development] mkhawx:
Just to confirm.. v5.4 for 4.4.4 also? :/

And is offline charging fixed?

Thats the only bug for me else its the best jernel for me ;)

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

Edit: found stable 7.1.. so no 5.4 :P sorry
[Galaxy S III Android Development] andip71:
Yes, all Samsung kernels are now stable.

And no - offline charging is not fixed on the Port-Kernels. I will not look into that anymore. It never bothered me and I do not see it as a significant issue. The ported roms will never be 100% bug free. So sorry for the bad news, but investing lots of time in something that will never reach a stable status is not really my deal.

Thanks for understanding.

Edit: If I see it done in a way in other kernels, so I can easily cherry-pick, I promise to include it. Just personally I do not want to spend time on it as I do not use a Samsung 4.4.4 port ever myself in a productive way.

Andi
[Galaxy S III Android Development] marenp:
Well, Arter fixed power off charge in his kernel and its working fine...
[Galaxy S III Android Development] andip71:
But not in a way I can just cherry-pick and take over without bigger work.

If it were simple, I had done it already.

Sorry guys, I always said, the kernels for the ports are experimental, less supported, so please accept I will not spend time on something ridiculous (yes, my opinion is hard - just charge with device switched on, I said it hundreds of times :) ) No need to discuss that again however.

Andi
[Galaxy S III Android Development] mkhawx:
Sure ;) offline charging is not so imp for me though. Thanks for the great kernel anyway ;) :D
[Galaxy S III Android Development] SignetSphere:
Oh... the shiny stable builds are now out finally haha :D Thanks for your great work here Andi you're really heaven sent for our beloved aging device :good:

About the offline charging... same here I really don't care about it really. It just bothered me a bit when now that I'm staying on custom roms (Blekota S5 Lite). Other than that the kernels are as stable as ever.
[Galaxy S III Android Development] River2418:
Boeffla-Sound engine V1.6.5

Stable version installed. Thanks for the great work, Andi! :)

Regarding unleashing the power of the Galaxy S3 audio chip, do you need to turn on Boeffla Sound status (in the config app), or is that needed only if you want to change volume, equaliser, mic settings etc?

TIA
[Galaxy S III Android Development] SignetSphere:
You need to turn it on in order to utilize the wolfson chip on the S3. You also need to leave it on in order to edit the settings that the engine can modify.
[Galaxy S III Android Development] River2418:
The wolfson chip will be utilised by the phone for music playback, regardless of kernal or rom.. I realise you need to enable it in the config app if you want to change settings such as EQ. My question was whether by default you get the audio benefits of Boeffla without having to enable in the app.
[Galaxy S III Android Development] andip71:
Nope. If you do not enable it in the app, the sound section behaves 100% like a stock kernel.

This is by design to make sure, there are no side effects and if there are, people can just switch it off.

So, you have to enable it to get the benefits.

Andi
[Galaxy S III Android Development] River2418:
Thanks :good:
[Galaxy S III Android Development] SignetSphere:
Ah yep I meant that too when I posted my reply it's just that i don't think (or notice? lol) that the stock kernel is even utilizing it fully. But since Andi answered you already then I won't push my opinion anymore :D have fun on using Andi's kernel mate :good:
[Galaxy S III Android Development] River2418:
I realised that's what you meant and thanks for your help :cowboy: . Will need to let my ears decide but are any of the 'miscellaneous' settings in Boeffla-Sound recommended to use ?

Will at some point get round to sifting through the 656 pages to find posts discussing audio.. Think I prefer the sound without using Viper4Android but need to try that again at some point..