yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Hi guys,

sorry for being away for a few days due to my business trip to UK.

Finally the trip was very successful, so I am baaaaahaaaack :)

For me the best rom is still: Samsung odex, then debloat it via TitaniumBackup (thats at least how I do it as you can import/export lists of apps zu freeze or deinstall).

As I generally do not support older beta kernels than the current one, they are not accessible generally. But on special request I can always make them available again on a peer to peer level.

I am still running XXEMG4 stock rom by Samsung. And I always download my firmwares from sammobile.com.

zRam does not use additional battery, at list it is not measurable.

Black crush fix is not implemented in all kernel versions I provide.

It is not in the CM11 kernel with new mali drivers + not in the Omnirom kernel + not in the n8010 kernel.

There is no option to disable/enable it. It is a hard change implemented.

Don't know. Must be some side effect.

However not by the Boeffla-Config app as this app does not run at all when not open (it does not carry a service or anything, you can easily check that in order to believe me).

I think, the rom itself might do it.

And the MDNIE settings are only meant for older CM10.2 roms, as stated in the headline of the app. And this is exactly for this reason, as Samsung firmwares tend to overwrite and reset it.

Because you are on a kernel that does not support GPU changes.

This is for the Samsung 4.3 kernel = 5.0 series. Same goes for newer CM11 kernels.

Yes, true.

And if some kernel dev finds some time to implement GPU settings again, I am happy to cherry pick. However, as I never use it myself, I do not want to put potential many days of work into that now.

But as the new mali drivers are used by CM11 soon (partially it is already), by Omnirom as well... there are good chances someone will implement it in the future. Just for sure not me :)

Andi
[Galaxy S III Android Development] ducky1979:
Hi andi, could you give me a link to the rom you use please pal. I'm interested in flashing a pure 4.1.2 rom and seeing how I go.
[Galaxy S III Android Development] andip71:
Ducky, I always load it directly from Sammobile.com.

Andi

Gesendet von meinem GT-N8010 mit Tapatalk 4
[Galaxy S III Android Development] ducky1979:
so is your bootloader the official JB one and do you flash via odin/mobile odin?

ive never used an official sammy rom so im not sure what to expect or how to go about it.

thanks
[Galaxy S III Android Development] andip71:
My Bootloader is the one that comes with the XXEMG4 rom.

When you flash with PC Odin, your bootloader gets replaced.

But why do you worry about the bootloader at all?

Whatever bootloader I flashed so far, I never faced any issues at all.

Andi
[Galaxy S III Android Development] erto90:
32gb users, from what we got documentated, are not affected by the sd bug.
[Galaxy S III Android Development] saad2687:
But i heard that new bootloader contains the sudden death fix not the kernel ... can some one explain bcz i may be wrong
[Galaxy S III Android Development] andip71:
The microcode patch for the VTU00M device is integrated in the kernel, not the boot loader.

The patch is available and I checked whether it is included in the kernel sources of Update7. It is!

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

All infos about boot loader fixing it are considered to be rumors.

Andi
[Galaxy S III Android Development] erto90:
A thing i found, always about speaker volume

It reset also when you "close" the soundapp using the back button, while is OK closing ( or better, sending in background) ) using the home buttton
[Galaxy S III Android Development] brunodu91:
So Kernel boeffla is update in v7 Like stock ?

Envoyé depuis mon galaxy s3, rom El liberator Lla v7 / 4.1.2 jb , Kernel stock , nova launcher, thème syps Black&color ... via tapatalk 2
[Galaxy S III Android Development] andip71:
Yes. You can state it this way.
[Galaxy S III Android Development] gsw5700:
Away from all the death talk, Boeffla 2.6 is running really well, no problems found. It has definitely got a spring in its step. Back to the death talk, I've had my phone since 1st june and it's got the dodgy emmc. Just copied my ext sd card to my laptop (containing nandroids and TB backups, just gotta bad feeling about this)

Sent via TCP/IP
[Galaxy S III Android Development] brunodu91:
Ok flash is done for me.

So, if this Kernel custom needs to hardware via recovery, it is not really fixed ? Because stock Kernel lla no needs That !.

Envoyé depuis mon galaxy s3, rom El liberator Lla v7 / 4.1.2 jb , Kernel boeffla 2.6.1 , nova launcher, thème syps cyan ... via tapatalk 2
[Galaxy S III Android Development] tsubus:
Quick question for other users on 2.6 alpha1: I have only installed it last night so it might still need a few days to stablize (if this even makes sense), but I've noticed it drains battery quicker compared to my previous kernel (which was not Boeffla, so I am not sure how it compares to 2.4). The same thing happens to a friend of mine which I has installed 2.6 alpha1 last night. This might be due to different usage of the phone compared to my usual standard, I have not had the time to thoroughly test it yet, which is why if someone else is noticing the same behavior.
[Galaxy S III Android Development] andip71:
I do not understand your comment to be honest, but to state again:

Yes, kernel version 2.6 uses Samsung source update7 which includes the sudden death fix. So your device is safe.

Custom recovery (CWM) is a different topic, this is not yet safe until the developers provide a new CWM version. But this is not related to the kernel, Boeffla-kernel does not come with a own recovery.

Does it answer your question/cover your comment?

Andi
[Galaxy S III Android Development] fuxmen:
AM I thinking good. If I doing backup restoring instaling zips from external sd im safe? Even with bad emmc in my phone?? With recovery on not lla kernel?

2.6 Kernel works verry well, one freeze after restoring setcpu now without setcpu everything works like a charm since yesterday.
[Galaxy S III Android Development] andip71:
Comment from me (although I am not a typical user, hehe): First report about that at all. So let's check it for a few more days to be sure.

For me, battery life is even better than with previous (boeffla) kernel versions, same response from existing users so far.

So, lets see.
[Galaxy S III Android Development] andip71:
No, not really. As soon as you enter CWM recovery, the recovery kernel is getting loaded to gain you access to the hardware. And this kernel is not patched.

So you are not safe at all in recovery.

But, just avoid CWM for a day or so. I know people like Phil (Philz recovery) are already working on a new version with a patched internal kernel and plan to release it either still today or tomorrow.
[Galaxy S III Android Development] fuxmen:
With Your kernel and Null ROM i can avoid it for a week. I bought my phone 2 weeks ago. I do everything to make it safe :)
[Galaxy S III Android Development] tsubus:
Yes, I'd also like to use it a few more days before confirming that, for me, it has this effect. It is simple curiosity to see if I'm the only one with this issue (so that I would have to investigate to find the app that is causing it), or if it's a more widespread issue among Boeffla users. So far it seems it's just me, so maybe it's just that I've used the phone more than usual today. I'll report back in a few days in case this pattern keeps up.
[Galaxy S III Android Development] andip71:
Yep. No need to wait for a week. Tomorrow you will see the first fixed CMW recoveries already, I am sure. Then you are fully safe again.
[Galaxy S III Android Development] andip71:
Agreed. Usually I tell people to monitor it for at least 2-3 days, checking also deep sleep rate and if this is too low, to find out with BetterBatteryStats whether an app is causing it.

Andi
[Galaxy S III Android Development] rulala:
i am the same. :p

no battery drain than before.

I confirm it.

my deep sleep rate always could be about 91 - 92% (a night sleep:D)

I don't need to close anything for power-saving.
[Galaxy S III Android Development] brunodu91:
This answer is to answer at mine previously answer ! Lol

Envoyé depuis mon galaxy s3, rom El liberator Lla v7 / 4.1.2 jb , Kernel boeffla 2.6.1 , nova launcher, thème syps cyan ... via tapatalk 2
[Galaxy S III Android Development] Holoshit:
Hi And,

Did you manage to solve the call recording support in your latest kernel?

Thank you.
[Galaxy S III Android Development] ducky1979:
Its not that I worry. I just use an older one due to the flash counter. So you flash stock, then root it, then start to play?

Do you use auto root or another method?

Thanks for the info. Sorry to hijack your thread.

This is last bit of info I need.

Thanks.
[Galaxy S III Android Development] janres155:
Hi! I understand that you want the XXLFB bootloader, which doesnt have the red exclamation during boot.

I highly suggest you flash rom from here: http://xdaforums.com/showthread.php?t=1868004

It doesn't flash bootloader, so you can keep yours. It just flash the system, kernel, and the modem so you are safe with it.

Btw, it has choices for odex or deodex.
[Galaxy S III Android Development] ducky1979:
I currently have flashed XXALEF bootloader and have been on it since Samsung changed it. I was using a 4.3 rom but I've just gone back to 4.1.2 and it's far smoother. But after reading andi used stock I was interested in the process he uses in flashing it and keeping root. But thanks for your help.
[Galaxy S III Android Development] andip71:
Ducky, to answer your question:

I always install stock rom, then flash a custom recovery.

And from this recovery I flash Chainfires supersu zip, which you can download from his thread, to root my phone.

Andi
[Galaxy S III Android Development] janres155:
No problem mate. I just thought you are afraid on flashing ROMs with bootloader, because you know, samsung is full of suprises when giving new updates. Therefore, I recommend you to just use CWM flashable ROMs just to be safe and to get rid of the red exclamation mark during boot. :P
[Galaxy S III Android Development] andip71:
This is correct Janres155.

Just to complete on this topic: Even every bootloader can be downgraded again to any previous version.

It is not very easy as the bootloaders, at least when trying it, are reluctant to be downgraded again.

But there is a way using dd commands on terminal or adb to achieve it always. Have done that many times myself already.

Andi
[Galaxy S III Android Development] andip71:
4.1-beta2 / 5.1-beta2

Hi all,

the Samsung kernels got a new update today:

Version 4.1-beta2 (Android 4.1.2)

+

Version 5.1-beta2 (Android 4.3)

03.12.2013

Charge level information added (you need Boeffla-Config V2 app 2.1 or higher for it), this shows you the detected charger + the negotiated charge rate between kernel and charger

Bit more relaxed timing during kernel initialisation

Some minor bugfixes

Enjoy

Andi
[Galaxy S III Android Development] MIKEMON:
big thanks to my friend for a good job

---------- Post added at 07:19 PM ---------- Previous post was at 06:28 PM ----------

Andi, display charging, usb charger 475 mA

It is good for me
[Galaxy S III Android Development] shivasrage:
Hi Andi,

This is the first time that I have to report a problem with Boeffla-Config app V2 2.1

I cannot download Kernel 5.1 beta 2 via the app...tried with WIFi and mobile.... no chance.

When the select-text shows up and you tip test it fc´es....and no dowanload.

Have wiped caches and rebooted allready ....also tried to reinstall app

But same again..

greets
[Galaxy S III Android Development] andip71:
Ok, possible. I did not try myself as I currently have no device on 4.3.

Will look into that in the next few days.

So far, please download from the homepage and flash manually.

EDIT: Found it I guess. My FTP client did not upload the files correctly. Please try again.

Thanks

Andi
[Galaxy S III Android Development] axetilen:
I just checked it and it is still 4.1 beta 1. Please fix it

thanks you so much :)
[Galaxy S III Android Development] butus73:
An hour or two ago I've downloaded and flashed 4.1 beta2 without any problem via the latest Boeffla-Config V2 :)
[Galaxy S III Android Development] ssteidte:
Successfully updated to 5.1-beta2 from the app. Thanks for your great work!
[Galaxy S III Android Development] andip71:
4.1-beta3 / 5.1-beta3

Hi all,

new beta is out for you.

Version 4.1-beta3 / Version 5.1-beta3

04.12.2013

Correction to the charge level information interface (cover for periodical reset of soft regulation loop)

Enjoy

Andi
[Galaxy S III Android Development] nelsonw:
I have this. I couldnt find an update on Play Store....
[Galaxy S III Android Development] andip71:
Somehow root is not working anymore for the Boeffla-Config App.

Had that yesterday with another user. Hi tried everything and in the end, reinstalling the kernel was the only way to fix it for him.

Andi
[Galaxy S III Android Development] JMS74:
I can't seem to find that information on the updated config v2 app. Where does it show?

Enviado do meu Nexus 7 através de Tapatalk
[Galaxy S III Android Development] gabebcn:
I had this problem but tried for the second time and root access was granted.

Enviado desde mi GT-I9300 mediante Tapatalk
[Galaxy S III Android Development] andip71:
It is here, see screenshot.

Andi
[Galaxy S III Android Development] MIKEMON:
Version 4.1 beta3 is again a perfect job.

Charging indication is amazingly
[Galaxy S III Android Development] Clark789:
Hi Lord,

will the new app show the real charging rate or just a category? I.e. will it show only 500mAh, when it's connected to USB and 900mAh for the charger or will it show (nearly) the exact mAh-value of each charging source?

Thx for the new kernel and for the new app. Again great work!

Regards

Clark
[Galaxy S III Android Development] mattiadj:
Hello to all guys. How are u lord? I'm back since I have the gs3 of my girlfriend for some days to flash 4.3 rom. But I have a problem with this kernel and also with the yank one. The kernel is successfully flashed and reported In information but... The settings are not stored after a reboot! Also the yank init.kernel.sh is completely empty!! With this kernel and config app is the same! How is possible? Anyone can help me? I'm on latest 5 test for 4.3 of course and rom is omega 51.

Thanks!

From universe with my gs4 snapdragon powered!
[Galaxy S III Android Development] JustArchi:
First rule, full wipe.

Second rule, full wipe including your internal storage.

Third rule, change rom.
[Galaxy S III Android Development] mattiadj:
Made full wipe including internal of course.

Why I have to change omega??

I think the problem is recovery related... I'm using twrp... Since Philz recovery has a problem mounting 64gb fat32 sdcard

From universe with my gs4 snapdragon powered!
[Galaxy S III Android Development] JustArchi:
How recovery could be related to the kernel? It either flashed something properly, or not. If not, it's not working at all, if it did, it's fully working. Kernel is boot.img image, there's no way in flashing it "partially". Unless you interrupted this 0.5 sec process.

You should change the rom to learn if your problem is rom-related. If you won't then you never find out if it is. You should NOT decide to poke Andi before making yoru best to solve your problem, eventually gather as much info as possible. I'm not blaming Andi's kernel even if a problem is really caused by the kernel... :D.
[Galaxy S III Android Development] mattiadj:
I'm only asking if someone had this problem too... I'm know how Andy is a wonderful Dev so I know that your kernel is a sort of must have... Infact is the first kernel I have flashed. I know also about the not correlation between recovery and kernel... So I have thought about a bad flash as you. This is the first time I have this problem.

Tomorrow I will test with more stock rom like wanamlite and report.

In your opinion which rom I should try? Which one do you have?

From universe with my gs4 snapdragon powered!
[Galaxy S III Android Development] JustArchi:
The one from my signature ;). Running perfectly with Andi's kernel.
[Galaxy S III Android Development] nelsonw:
Hi Lord, it's possible to backport the new video drivers to 4.1.2?
[Galaxy S III Android Development] mattiadj:
Sorry can't see it. Tapatalk rule. Can u tell me?

From universe with my gs4 snapdragon powered!
[Galaxy S III Android Development] JustArchi:
ArchiDroid, 2.3 actually. Powered by boeffla-omni kernel :).
[Galaxy S III Android Development] vicfirth_23:
Hi everyone, is the Boeffla Setting not available in the latest version for 4.3? I cant find it... :what:
[Galaxy S III Android Development] dyval:
Just download it from the Google Play Store.
[Galaxy S III Android Development] gkhushal:
Guys. What's the best settings for zram without lags...!!
[Galaxy S III Android Development] dyval:
IMHO it is best not to activate ZRAM. Much smoother.
[Galaxy S III Android Development] janres155:
But if he insist in using Zram, I recommend a 200mb or 300mb and swappiness set to 30. Low swappiness avoids the system to use Zram too much and this can prevent filling up Zram fast, which cause lags.
[Galaxy S III Android Development] andip71:
Ok, this is a very valid question and I have hopefully a good answer:

The rate showing in the app is NOT the actual charge rate as this would mean, we need a circuit in the S3 that can measure it. The S3 has no sensor to measure that.

But what it is:

Based on the detected charger type (AC charger, USB, dock, wireless etc.) the kernel tries to load with the charging rate you configured in Boeffla-Config for the type.

If you did not activate the ignore unstable power function, the charging logic then checks if the desired charging current is delivered and stable.

a) If yes, all is good and you will see your configured charging rate in the app - in fact, the device will load with it.

b) If no, the so called "soft regulation loop" will kick in and reduce charge current in steps of 100 mA down until the current is detected to be stable again. Then another 100 mA safety margin will be deducted (if you have not set the ignore safety margin switch to on). This new, negotiated charging rate will be reflected in the app.

Just to let you know the whole negotiation bit is done every around 40 seconds again.

So in short: Although we cannot measure the actual charge rate, the rate shown is the one negotiated between kernel and charger and should be pretty accurate.

It will show you for instance if your USB port cannot deliver the current you have configured, and so on. So I think it is quite exciting information to have, especially when you face slow-charging occurances. There is no more why and how, just open the app and see.

Thanks, I am pretty fine. Hope you as well.

Without log files I cannot answer your question. Send me a debug info file and I will tell you.

Probably yes, as we devs have done it for CM11 as well.

I did not try it so far as it would not help you a lot without the rom supporting it as well.

Boeffla-Setting app is discontinued for around half a year meanwhile, it was in the series 1 and 2 kernels only.

Now you need to load Boeffla-Config V2 from play store or AndroidPIT.

I agree, honestly.

But when I used zRam I configured it to 4 devices, 600 MB in total and the predefined swappiness of 80. Worked fine for me, however I do not use it really as I do not have such memory-intensive apps.

Andi
[Galaxy S III Android Development] sanefirst:
Andi, I am facing an issue with this.

When I connect my phone via USB and set to 600mA it's working OK. The app shows 600mA all the time.

But when I connect to wall charger, then I get 900mA in the beginning (my setting is 1100mA) and after a couple of seconds the app shows "AC Charger 300mA". I don't know what's wrong as I use genuine Samsung GS3 AC charger.
[Galaxy S III Android Development] andip71:
Hi,

all is well.

The genuine S3 charger is known to be a piece of crap. It is known to be the culprit for slow loading many users report. And you are one amongst them apparently.

The charger in fact does not supply the power required, so the charging rate goes down to 300 mA in your case after some time.

By the way: This is not implemented by me, it is the same in each and every kernel incl. stock. The only thing I did is: I make it now easily visible (you could see it always in the kernel log, but now it is more convenient).

You have two options:

- buy a better charger for around 10 Dollars (I did as well, it loads with 1100 mA in my case)

- switch the ignore functions on, so the S3 does not try to reduce the charge current anymore. but do on own risk as it might damage your charger

Have you never wondered why your S3 charges slowly? With 300 mA it takes ages?!?

Andi
[Galaxy S III Android Development] sanefirst:
Ah yes, I always thought that charging time for GS3 was a disaster. However, I bought this phone two months ago so I was convinced that that's the way it is...

Thanks! I'll try with my Galaxy Tab 2 2000mA charger. Should be safe to use (as there is a safe automatic regulation), right?
[Galaxy S III Android Development] andip71:
It is perfectly safe. I also use the charger of my HP Touch Pad.

Let us know which charging rate you achieve. Put it on 1100 mA for instance, plug it in and see.

If it stays at 1100 mA, you will see how quick charging can go :)

Andi
[Galaxy S III Android Development] janres155:
i put mine on 1200mA and I'm using Nokia's E52 Charger, but I only got 500mA. Any tips?
[Galaxy S III Android Development] andip71:
1) change charging cable (if not fix mounted to charger)

2) change charger

3) Switch on the "ignore instable power" function in boeffla-config (on own risk)

Option 2 is most recommended.

Andi
[Galaxy S III Android Development] SuperAce609:
Don't say that. One thing is not knowing how to use it and another is knowing it doesn't work.
[Galaxy S III Android Development] janres155:
I agree with you. One must know how to experiment to fully achieve the best performance and battery lifetime. :)
[Galaxy S III Android Development] D00ky:
Samsung resumes Android 4.3 update roll out fo S3

James May: "Good news."

Jeremy Clarkson: :confused:

James May:"Samsung resumes Android 4.3 update roll out for S3"

Sorry for spam, but I just had to post this. Waiting for others to spam as I am shure that there will be plenty of them :laugh:
[Galaxy S III Android Development] SuperAce609:
Hey Andi i have a couple of questions. I've started using my phone for music (completely replaced my iPod, big ups for boeffla sound) and I've noticed that there are 1-2 cores active and another one with Zz on it. Does that mean it's sleeping or active or what? First time i see it. It can be like (1600Mhz, 1600Mhz, Zz). Is that the core responsible for playing music?
[Galaxy S III Android Development] andip71:
SuperAce: Well, this is all very normal.

Yes, CPU cores are required when you play music. Someone (in our case the CPU) needs to decode the compressed data of the music (mp3, ogg, whatever) and convert it into something that can be fed to the audio hub.

But typically I would assume 1 CPU core should be enough. So I am pretty sure on pegasusq - boeffla moderate only 1 core would run and music would still play fine.

Where do you see zZ? I think you are looking into an app and this zZ means the core is switched offline.

Andi
[Galaxy S III Android Development] jj92942000:
Xmas comes early Sammy resumes Int. Update see kink. Check sammobile soon for download links.

http://www.sammobile.com/2013/12/05...-3-update-roll-out-for-galaxy-s-iii-gt-i9300/
[Galaxy S III Android Development] nelsonw:
Already posted on the same page. Please read before double post.
[Galaxy S III Android Development] SuperAce609:
Here. There's only one core active when listening to music. This time i was doing something else in the background. But the zz is always there. (300Mhz, Zz)
[Galaxy S III Android Development] jj92942000:
Sry mate long day scanned and missed yours.