yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] mikailmohammed:
No it is constantly using 1.6ghz and not anything lower. I have monitored it today so far and it has been normal. I installed back the stable kernel 4.0. I was on the 4.1 beta.

---------- Post added at 07:50 PM ---------- Previous post was at 07:46 PM ----------

So far today has been normal like before. I flashed back the stable kernel.

---------- Post added at 07:53 PM ---------- Previous post was at 07:50 PM ----------

So far for today. I am busy at work so didn't use my phone as much plus I flashed back the rom and kernel from scratch last night.
[Galaxy S III Android Development] Saenic:
Another problem with the Kernel:

I'm using 4.0 on UltimaRom 15.1 (JB 4.1.2).

adb remount works but when I try to install an app with adb install I get a an error

D:\Projekte\construction\target>adb install construction.apk
1326 KB/s (44821 bytes in 0.033s)
pkg: /data/local/tmp/construction.apk
Failure [INSTALL_FAILED_INVALID_APK]

With Siyah Kernel it works, so I think its Kernel related :/
[Galaxy S III Android Development] jj92942000:
Siyah kernel is discontinued. Was taken over by googy-max. Not sure why causing problems on Boeffla.
[Galaxy S III Android Development] Saenic:
Siyah is just my example for a "good old stable" kernel. It has all features that I need.

I'm starting with Android App development again and therefore I need a kernel, that has all the adb features.
[Galaxy S III Android Development] GUZGUN:
First of all i have v4 and omega rom v50.1. I noticed something strange the last 2 weeks. From 100%-35% the there is no any specific battery drain. After 35% the battery runs out very quick. In 8 hours without doing almost anything the battery goes from 35% to 20%. Strange, eh?
[Galaxy S III Android Development] alerems:
Same do mine. After ~30% battery becomes crazy and then after ~5% it comes back to normal. I have 20h of working phone till 30%, then i had 1 hour and 5%.
[Galaxy S III Android Development] andip71:
Yes known problem with 4.0.

Why dont you step up to 4.1-beta1, where this problem has been fixed? :)

It was always for me, after 30% downwards it went quicker than before. Already was the same with my Galaxy S1.

But as I have not changed anything in the code regarding this behaviour, nor any charging/voltages curves, I can confirm this has nothing to do with the kernel.

Andi
[Galaxy S III Android Development] RCT1:
When I used 4.3 I've experimented all the kernels, and some of them uses that script, like yank...

init.d folder - where can I find it?

Thanks for all your help!
[Galaxy S III Android Development] andip71:
init.d is under /system/etc.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] mikailmohammed:
Soooo... throughout the day my phone was fine. Flashed 4.1 beta and it decided to go nuts on battery again. Seems bluetooth test and media server scanning were going crazy on battery. I flashed back 4.0 stable and same thing continues. I wiped cashe and dalvik cashe and it seems to have lowered the cpu usage. Will observe more.
[Galaxy S III Android Development] jhonyrod:
Autoroot not working

The autoroot function isn't working, I've restarted many times now, with and without the mentioned "autoroot" file with no success. Also, the logs indicate that the binary is "copied successfully" yet there's no hint of it acutally doing something. Is this a known bug? What can I do to get around/fix this?
[Galaxy S III Android Development] andip71:
Autoroot should work. All you need afterwards is installing supersu app from play store and you should be done.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] jhonyrod:
First of all, thanks for the quick reply.

I retried, now uninstalling supersu then rebooting and reinstall, again, with and without the autoroot file to no avail... I guess I'll try a full wipe, I'm being hesitant because it really is a drag.

PS: I forgot to mention that I'm using the 5.1 beta version of your kernel.
[Galaxy S III Android Development] andip71:
Hehe, was just about to ask.

On 5.1 this has for sure not yet been extensively tested.

Before you wipe, can you check if you have a file called "su" in /system/xbin folder?

If so, all should be ok.

If not, it is a bug which I potentially can fix. Please let me know, almost nobody roots this way, so it is possible this is probably an uncovered bug.

BTW: I always root by flashing the supersup zip Chainfire provides in his XDA thread in CWM. Done.
[Galaxy S III Android Development] D00ky:
Probably it has something to do with the rom. I am on the latest 4.1.2 Samsung rom, odexed with the latest Boeffla kernel. At least for the last three months it always happens that after battery hits 40-30% wakelocks becomes more frequent as you can see from my screenshots. That phenomena usually goes away after battery gets to 20-15%. I always suspected samy's rom. I recently removed some bloatware (system) apps which I don't use. We'll see how it goes from now on.

One more observation about that. I always thought that this drainage has something to do with the UV that I use but apparently it happens also with stock voltages.
[Galaxy S III Android Development] Garreth88:
Use BetterBatteryStats to check out which app are wakelocking.
[Galaxy S III Android Development] jhonyrod:
There's the su binary in that folder, but I think it's faulty in some way because Supersu doesn't recognize it...

I tried running it from the terminal emulator and the only thing that happened was that the prompt changed from [username]@[machine] to 1|[username]@[machine], which I've never seen before.

I don't have a custom recovery yet, I usually like to flash it via Mobile ODIN since I don't like tripping the flash counter. I'll try and find a signed package.

Out of curiosity, is the su binary for the autoroot somewhere else in the file system and then copied at boot or is it in the ramdisk (or somewhere else)?

Thanks again, and like to say that you are very attentive
[Galaxy S III Android Development] andip71:
The su binary getting copied can also be found in /res/misc. You could try to copy it from there, but without root would not work to copy it :cool:

At least you could check if file sizes are correct and permission is ok (only in /system/xbin)
[Galaxy S III Android Development] D00ky:
Don't worry. I used it and I know what is going on. It is not app's fault only regular system wakelocks that get more frequent when battery is between 30% and 15%. Wouldn't it be weird if some user apps would go crazy only when battery percentage is on that interval and that over 4 days sample?
[Galaxy S III Android Development] andip71:
As weird as when the kernel should put more wakelocks in when battery is lower.

Would be weird as well.

Anyways, it behaves like stock kernel as I did not change anything.

Andi
[Galaxy S III Android Development] sooperbad:
Hello everyone..

I tried searching thread but couldnt located how the encounter the problem for the Lag in Lockscreen.. It takes 4-5secs to unlock the screen after pushing the button.. I am on Android Revolution HD v40.. using latest kernel v5b2

Please someone tell me what to do?

I am sorry if this has already been asked.

And great job Boeffla.. great work.. :)
[Galaxy S III Android Development] andip71:
Honestly: Go back to a 4.1.2 firmware and enjoy the almost bug-free experience (this is what I did)

Samsung stopped the rollout of 4.3 to the S3 for good reasons. You will never completely fix that as long as Samsung did not fix it in the rom base.

Sorry for bad news, but it is the truth. You cannot fix this issue, just try to mask it as good as possible.

Andi
[Galaxy S III Android Development] sooperbad:
thanks for the quick response.. :)

I will surely do that with your kernel..

Please tell me by going back to 4.1.2 firmware you mean stock firmware?
[Galaxy S III Android Development] andip71:
Any Samsung based 4.1.2 firmware. Either being full Samsung stock or a Samsung based custom rom.

I am on Samsung stock only, but this is my personal preference.

Andi
[Galaxy S III Android Development] MIKEMON:
Yes, I confirm this, I had a custom rom, but I'm back to stock 4.1.2 MG4

ODEX stock rom runs beautifully smoothly without problems
[Galaxy S III Android Development] sooperbad:
I think custom rom with all the bloatware removed would be a better option?

dont you think?

Its because I don't know what apps are safe to remove if I flash a custom stock ROM
[Galaxy S III Android Development] musvi:
after hours of trying miserably failed to download the kernel from the specified page of op

page stuck at.... :(

View attachment 2420706
[Galaxy S III Android Development] NapsTer.VicTor:
Can you tell me where can i find older versions of the kernel?? Like 4.0 beta 1,2,or 3..as this recent one eats my battery, the phone is gettin very hot.. And it's winter.. And it has a lot of lag.. I tried everything.. Reset from app from cwm reintall beta/stable.. All profiles, and nothing..
[Galaxy S III Android Development] MIKEMON:
Test Wanam 7.2 s boeffla 5.1 beta1, bloatware delet securely using rom cleaner script

I'm on stock 4.1.2 ODEX without bloatware

each must choose himself

---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------

I have stored in the cloud / box / I do not know if I will download?

https://app.box.com/s/udfvgynhxi8nobtw787q

https://app.box.com/s/klov6jcdjqbzu9a06x4e

https://app.box.com/s/frx1s1t4ujpemyo3zswh

https://app.box.com/s/klov6jcdjqbzu9a06x4e
[Galaxy S III Android Development] D00ky:
Maybe I expressed myself in the wrong way.:o

I suspected some system apps or maybe even sammy's rom. I didn't want to put a blame on the Boeffla kernel as it did just the opposite. Boeffla kernel reduced wakelocks on my S3. I just started observing this behaviour when I was on stock rom+Boeffla kernel, haven't tested stock setup. On stock setup there is whole allot of other wakelocks that I just couldn't find this behaviour:) I should mention that my culprits are: sammy rom itself, some sammy's rom system apps or my UV regime. I already crossed out UV as I proved it happens also with stock voltages. Now I am testing with some system apps removed. If this makes no progress than it is sammy's rom itself and the case is closed for me as I can't do anything more.

Again sorry if it sounded like I pointed to the Boeffla kernel as the culprit. Andi thanks again for this wonderful kernel and I just can't wait for stable 4.3 from sammy so you could do your magic there. Till than I am staying on 4.1.2 as it is as perfect as it can be.
[Galaxy S III Android Development] Sleehond:
Boefla 5.0 kernal flashed here on ARHD 40 ROM. But now my camera doesn't work.

Anyone a solution?
[Galaxy S III Android Development] schlex2010:
Can not download 5.0 stable from the website. There is no link. Please help!
[Galaxy S III Android Development] MIKEMON:
http://xdaforums.com/showthread.php?t=1717610

Around error fw.camery
[Galaxy S III Android Development] Sleehond:
I don't understand this link and posts? Thats not a solution to make my camera work!?
[Galaxy S III Android Development] MIKEMON:
No, just read the update fw.for camera

You need to look here on the forum
[Galaxy S III Android Development] SuperAce609:
Does LMK kill apps once in a while or is it continuous? Like a permanent effect
[Galaxy S III Android Development] axetilen:
I dont really understand the question. It always monitors the amount of free ram and wil be activated only when amount of free ram reaches a specific values -> all apps which belong to a specific category will be killed according to their priorities (OOM ADJ)

most "downloaded" apps (like facebook main app and web browsers) belong to the last category (empty apps) which is usually set at ADJ = 15 or 9 or 7 (highest priority to be killed first, second, third repectively). If I set that category at 128mb, when the amount of free ram <128mb => these apps will be killed FIRST. if free ram >128mb, LMK will stop

if empty apps are kill but free ram is still <128mb, probably there are some apps which belong to the second category = content providers (adj = 7 / 9), which has a different OOM LMK value as you set. I set this at 96mb (facebook background services or instant messaging apps usually belong to this)

=> if free ram <96mb => both empty app and content provider categories will be activated => both app belong to these will be killed

p/s: this is my finding that I find it is true in my device. I dont read anywhere so there could be something wrong => correct me please :)

I think these are the optimal values to avoid lags. I repeat, keep ur free ram >100mb and u will never get lag. u can increase the content provider to 100mb and empty app to 128mb

yes, apps will be easily killed with this setting but we dont have lag. u can use swap (may degrade ur sdcard or internal flash) or zram (safe) to compensate that more apps will be kept in ram but it costs some cpu to keep this working (especially zram). However, maybe some apps when they are running would drain your battery like google maps and viber :)
[Galaxy S III Android Development] SuperAce609:
I really love your throughout explanations. Thank you so much once more. But see, this is what I set my LMK values to:

So far it's been working wonders. The animation stutter I thought was a general S3 problem is gone. Turns out it's a lack of ram. Animations play beautifully at x1 without any problems. And there's enough free ram to keep the phone flowing and everything working neatly. Sure, it might seem a bit aggressive. But hey, it works.
[Galaxy S III Android Development] axetilen:
it is good for ur phone cuz u have a big battery and high cpu speed :)

it doesnt need to be that much aggressive. u can try 130 and 110. its good also

if u set it too high, apps will always be killed and it takes time to reload the app from the beginning => costs more battery and time
[Galaxy S III Android Development] SuperAce609:
Like you said, big battery. At this point all I want is performance with less heat xD. And either way, loading from the beginning isn't a problem with so much free ram and the processor with enough space to do whatever it literally wants. Really can't tell any difference. As for GPU, it's clocked at 350/350/440/533. No heat, no lag, no nothing.

But hey, those are the settings that work for me. Just love poking and messing around with different combinations.
[Galaxy S III Android Development] Clark789:
Hey Ace,

as far as i can see, the raising of the LMK works for you, because you enabled your zRam. But how will it work, when you disable the zRam? Will the rainsing of the LMK make any difference? Did you ever try?

Regards

Clark
[Galaxy S III Android Development] schlex2010:
Do you have an odexed stock rom? If yes, do you have a link? And for sure you use your kernel on 4.1.2 Stock, right?
[Galaxy S III Android Development] SuperAce609:
No idea at all. zram doesn't cause any problems so i don't bother turning it off. It only does good in my case. But either way, i do suspect the LMK has something to do with the free ram i have. Even with zram enabled, i don't remember having this much free before.

Zz - optimal (used yanks battery before but it's really bad for gaming) at 1.6Ghz with the GPU settings i posted above and the settings in the picture and you'll be completely all set. So far it looks like a new rom to me. Try it and you'll see. No heating problems or anything negative.

Edit: I'd like to add something. When you're tweaking your kernel settings, you have to keep in mind what type of result you want. Whether it's performance, battery or anything in between. I've never used other people's settings before. I've taken ideas, yes as you can see from previous posts on this thread. But never literally. I've read that Andi adds +10 to all LMK values. The axetilen sets empty apps and the other setting a little higher. I took those ideas and went a little further. To some, my settings might look too extreme. But like i said, you need to have a certain mindset when tweaking. Mine is pure performance and no battery consideration. Samsung roms save extreme battery compared to CM even in the highest settings. And with 7000mAh to play with, you can already guess.

Well, that's my bit. Enjoy some new ideas guys.
[Galaxy S III Android Development] mikailmohammed:
Guys what can cause android os to use up battery??

---------- Post added at 01:39 PM ---------- Previous post was at 12:50 PM ----------

Wayy to much battery drain than normal.
[Galaxy S III Android Development] axetilen:
yes, raise everything +10 and the last 2 values to 96 (or 100) and 128mb, respectively if you dont wanna use zram

it will be very good. Im currently using these and Im really happy with it :good: . this LMK can be used with zram also and provide a good combination

the amount of free ram usually around 130-160mb so lag almost never occurs
[Galaxy S III Android Development] ICavalera:
Just see that resolved... Some guys far now in the litegx topic. It seems by removing the external sd, turn on the phone... Stay a while, turn off and put the sd again on it.

Seems that trick resolved. Many users did I the same... All with the same results.

Not a bad idea to try it.

Sent from my GT-I9300 using TugaPower ROM
[Galaxy S III Android Development] MIKEMON:
anything you read here

http://xdaforums.com/showthread.php?t=2194644
[Galaxy S III Android Development] ICavalera:
http://xdaforums.com/showthread.php?p=47968208

Sent from my GT-I9300 using TugaPower ROM
[Galaxy S III Android Development] schlex2010:
Back from ARHD 40 to 4.1.2 with 4.0 boeffla kernel.

THAT is smooth and battery life is brilliant.

Thanks for this advice AndiP !!!!
[Galaxy S III Android Development] MIKEMON:
According to me, the right choice until repaired by sammy
[Galaxy S III Android Development] schlex2010:
Is zram only with 100 MB possible? And I think zram is using a lot if battery, or?
[Galaxy S III Android Development] MIKEMON:
Yes, zram is useful when a lot of applications, but rather less swapiness 50-60

This will help the system.

I do not know 100 megabytes, 400 megabytes use, but it is not necessary to use it.

Boeffla kernel is still very smooth and stable
[Galaxy S III Android Development] schlex2010:
Ahhh.... first have to set size of zram and after that activate it.

I do not use it but it works :)

Now search the best battery settings ;)
[Galaxy S III Android Development] vicfirth_23:
hi everyone...I cant find the download...
[Galaxy S III Android Development] ahac85:
Hi just got my phone back today after 2 months from samsung, last I remember is 3.1 kernel which ran great on my s3. Now sammy have replaced it with new s3 since they first one died of emmc bug.

Shud I install 3.2 or 4.0 or go 5 series kernel? Which runs better, theres too many posts to go thru to find out, any recommendations?

Sent from my GT-I9300
[Galaxy S III Android Development] SuperAce609:
Install the latest 4.0 version. The 5.0 series are for 4.3 Samsung roms which are currently buggy and development for them has been halted.
[Galaxy S III Android Development] vicfirth_23:
there are two options in the download link the current test and stable one...but when I click the stable...it does not download...should I choose the current test ? ?
[Galaxy S III Android Development] GUZGUN:
choose the current test version. It works very good.
[Galaxy S III Android Development] janres155:
Hi! You can try turning off the Scanning always available option by WIFI, and I think this is the culprit for Android OS.

You can find the option in Settings>Wifi>Advanced>Scanning always available.
[Galaxy S III Android Development] DF5JT:
Black Crush Fix

I Have seen quite a number of references for the "Black Crush Fix", but so far I have been unable to find any configuration option that addresses this feature.

I would at least like to see what effect this configuration has on my phone, so can someone please show me how to en/disable this particular option? I am running Omni-nightly and the corresponding latest Boeffla beta kernel with BoefflaConfig.

Thanks for your help in advance.
[Galaxy S III Android Development] SuperAce609:
Wrong boeffla thread xD
[Galaxy S III Android Development] DJ's life:
Why when I choose a preset whenever I disconnect the charger from the terminal app boeffla config resets eg mDNIe?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] MIKEMON:
It is important to save the profile settings
[Galaxy S III Android Development] erwinhayamz:
Back to most stable stock JB 4.1.2 with Boeffla kernel 4.1 beta1 is just amazing. Trying all the governors, my daily driver goes to pegasusq-boeffla moderate : smooth, stability & great battery life. Great thanks!
[Galaxy S III Android Development] DJ's life:
How can save profile?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] MIKEMON:
http://www.boeffla-kernel.de/index.php/boeffla-config-help

Everything described here

citer:

3. Profile maintenance page

You enter the profile maintenance page by clicking on the profile name in the actionbar (top right). In this page you have the following options:

Klicking a profile loads the profiles settings and defines this profile as the "active" profile from that time onwards

Create a new, "empty" (= default kernel settings) profile via the "New..:" button in the left bottom corner

Context menu when you long-press a profile in the list:

Copy a profile with all its settings into a new profile

Change description of a profile

Reset all settings of a profile (back to default kernel settings)

Create a shortcut to the profile on your homescreen, that allows to switch between settings without launching the Boeffla-Config app

Delete a profile

A profile always consists of a profile name and a profile description, both fields can be freely populated by you.

Please note, the profile called "Default" can never be deleted to ensure, there is always at least one profile left in the list.

By creating a shortcut to a profile on your homescreen you can load the profiles settings and make the profile the active profile by an easy klick on the icon.
[Galaxy S III Android Development] jj92942000:
FYI mates greek site confirms Samsung resumes v4.3 for S3 after being temporarily pulled. This also confirms an article I read in Canada. So we should see v4.3 issues behind us soon, hopefully by end of week.
[Galaxy S III Android Development] DJ's life:
Escuse me why i can't change the profile Gpu in boeffla config?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] SuperAce609:
How can you not? Take a screenshot
[Galaxy S III Android Development] DJ's life:
[

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] SuperAce609:
Oh you're using the 5.0 kernel. Right? I don't remember but Andi said something about GPU not being configureable in a version of the kernel. Which version are you using?
[Galaxy S III Android Development] jun_ng_1208:
If you're using the 5.0 version on a JB 4.3 ROM, then the GPU is not configurable yet :good:
[Galaxy S III Android Development] DJ's life:
I using the version 5.0 beta 2...but i think not configurable.... True?

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] vespa.truccata:
Great work as always, I really love your work and I've been always using your kernel! I'm using v5 beta1 for 4.3 and even if I get excellent battery life and no FC's, I believe my phone gets somehow in a very deep sleep. I receive whatsapp msgs and notifications with a big delay. Is it kernel related, anyone has same problem?