yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
Well, as I said... it works for many here.

And my app does not influence LED colour at all, I do not see that as a kernel level task honestly, that's why I am that reluctant.

Maybe the alternate mode helps, as mentioned by another user.

There is no charge current sensor in the S3, so all the widgets show you is... "something". Something interpolated based on battery voltage changes and expected battery capacity. In other words, it is mostly crap.

What you see in Boeffla-Config however is the value, the charging logic negotiated with the charger. So this is the rate that will be really used (demanded). If this goes down to 400, be sure it does charge very slow.

Then you should buy a better charger, or replace your cable. Or - on own risk - switch off the stable charge power detection so the charging logic will not scale down anymore.

If I do understand correctly, you did not activate the profile.

The right way to load my profile is:

a) Download the andi1.bcprofile file from the other thread

b) Store it into the existing folder /boeffla-kernel-data

c) Go into Boeffla-Config app and tap on the profile name

in brackets on the top

d) At the bottom left corner, click the load button and select

the andi1.bcprofile to import

e) The profile will show up in the list

f) Now, TAP on the profile to apply and activate it

From now on, it should always load the setting of this profile.

The currently active profile is shown in the brackets at the top again + if you enter profile maintenance again it is coloured blue.

Andi
[Galaxy S III Android Development] PIRATA!:
Thank you so much for your replying!

What happens if I reach 300 of zRam? What problem will I have??

Is there a way to prevent the saturation of zRam?

Maybe dividing it into different devices (mine is set to 1 at the moment) could help??

About PegasusQ and zzmoove...I'm on the zzmoove+AFTR-LPA combination now, and I like it.

As you say that theoretically PegasusQ battery modded as you explained could be better then zzmoove combined with AFTR-LPA, I think I would in case try that. I just have to understand if trying it would be best thing to do, or just keep my actual zzmoove+AFTR-LPA as I have set now.

About the other stuff....

For Fast Dormancy.....is it correct to disable it in any case on each network I hook (like now that I'm in roaming) or not?

For Wi-Fi that consumes too much battery......I use a lot of Wi-Fi as my home is some kind of bunker!! Without Wi-Fi I couldn't write now on TapaTalk!!!.

Is there a way to lower battery drawning??

Should I change modem flashing a new one with related CIFS??
[Galaxy S III Android Development] Clark789:
Excuse me for my stupidity, but what is meant by "alternate mode"?

Kind regards

Clark
[Galaxy S III Android Development] andip71:
Uuuh, many questions:

When you fill up the zRam, the normal process of unloading not-used apps out of memory will kick in again. Just if you would not have any zRam or physical ram left. Standard Android procedure.

Splitting zRam into multiple devices does not help preventing it being filled, it just in rare cases helps to balance the CPU load across the zRam devices better, especially for gaming purpose. So I generally recommend to set it to 4 anyways.

zzmoove and ATFR-LPA is definitely a good choice. This is what I was using for more than half a year.

Just out of curiousity I started using pegasusq with my Boeffla moderate profile two days ago again, to compare.

As for WIFI: The typical hacks to reduce Wifi power usage as much as possible are already contained in the kernel (blocking multicast packets, reducing wakelock times etc.). So the only way to reduce WIFI power consumption further is to not use WIFI :) No, seriously, I would not know how to make it better. Maybe if you have bad WIFI reception, putting a hardware repeater in somewhere could help as the phone does not need to send with high power then....

And just to fight against a wide spread rumor again:

Modem has nothing to do with WIFI at all.

WIFI drivers are 100% in the kernel.

Modem is only taking care of Mobile data connections (GSM, Edge, 3g, H...).

There is no stupidity :)

But I did not say that, it came from another user.

I can only guess this is a setting in Lightflow...

Andi
[Galaxy S III Android Development] Clark789:
Can you please tell me, what is meant with "alternative mode"? I tried Light Manager, Light flow and other, but none of them works well on my boeffla-strengthend phone... :(

Regards

Clark
[Galaxy S III Android Development] jj92942000:
B14 and Omega v54 working as good as ever
[Galaxy S III Android Development] andip71:
Thanks for all the feedback.

Smells like this can become the stable 5.1 soon :)

Fingers crossed.

Andi
[Galaxy S III Android Development] boyheadkick:
Huh, that's weird...i tried zzmoove with aftr+lpa last night and i lost 10% battery..

Before that, i was using pegasusq boeffla battery saving with after+lpa and i would only lose 1-2% overnight...

I had changed governors based on the posts of [MENTION=4301380]axetilen[/MENTION] regarding the behavior of zzmoove and pegasusq wherein which of them shuts down the second core quicker which in turn activates the battery saving feature of after+lpa..

Which is why i now understand why a lot of people say that the S3 is such a diva in that it behaves very differently with different users

Edit: i am not in any way disputing anything that axetilen says in his posts...these are just my own observations

Edit2: also i've noticed in my Cooltool monitoring that pegasusq boeffla battery governor most of the time uses only core0, and in times that it uses cores 1 and 2 it only does so in such a brief moment and immediately shuts them down...which leads me to believe that the pegasusq boeffla battery saving governor is just as ideal as zzmoove to be paired with after+lpa...

I haven't tried the other pegasusq variants with after+lpa though, just boeffla battery saving

Tapatalked from my OmegaDroid i9300
[Galaxy S III Android Development] SignetSphere:
When the 5.1 stable comes out I gotta say goodbye to my 4.1.2 memories :silly:

Anyway, thank you Andi for being the ever patient dev I know here on xda :D Good luck on your upcoming releases! :good:
[Galaxy S III Android Development] Ubimo:
5.1-beta14 on Omega v54 working great!
[Galaxy S III Android Development] maxniper:
Testing the kernel from yesterday and for me is really stable. Really like it.
[Galaxy S III Android Development] axetilen:
if it lost 10% last night, it could be because of some other reasons, not kernel related

if your battery is currently <30%, it could happen like that. Wrong battery stat reading => should wipe batterystat.bin (battery calibrate) once if that file is old, then you dont need to do it anymore. I recommend you to wipe this file after flashing new rom especially when you update rom from the old to the new version (without wiping). You dont need to do it if you already do a fullwipe

try to monitor battery % when the battery is at least 70%, most correct I think

the other reason maybe something was working not correctly that caused wakelocks

sometimes, it is due to syncloop. it happens to me sometimes. whatsapp used to cause 10 minutes of wakelock to me during night, but only twice, then it has never happened again

try to set CPU frenquency 1st and then change the gorvenor => finally do a reboot to make sure everything is working probably

sometimes the old governor still does something that may affect the new governor

long ago, when I changed from boeffla battery to zzmoove, only cpu0 could work, the other were blocked => did a reboot and it was fixed

create a shortcut of greenify on your homescreen, press it right before you turn the screen off

wipe cache + dalvik cache to make sure everything is clean. Sometimes, wipe these makes phone more stable, smoother and probably fixes some force-closed bugs

I usually lose 1-3% during night. if battery level is too low, it can be a lot, 10% maybe more although there is only 1-2 minutes of wakelock in 8-10 hours as usual

---------- Post added at 11:19 AM ---------- Previous post was at 11:11 AM ----------

wifi issue, if you just use wifi at home, try to set static IP, no need time for obtaining IP address => faster and cause less wakelocks

reboot your wifi modem to make it fresh :P

running in a very long time may cause some weird problems to wifi modem

about 300mb of zram

if it is saturated => 350mb + 300 = 650mb => plus foreground apps => may reach 800mb of physical ram

we have 832mb of physical ram. 832 - 800 = 32mb free ram :silly:

=> very laggy and probably causes launcher redraw

setting swappiness to 60% and increase LMK to 112 and 100 could prevent saturation

I did this and I set zram to 60% => it is usually used ~ 64mb, free 36mb. rarely higher

pegasusQ, I dont have anymore idea. I still keep my opinion that, zzmoove is the best governor for daily usage and also deepsleep. pegasusQ is good for gaming, you can set pegasusQ (anything) before you play games. pegasusQ is probably slower than zzmoove because as we already knew, pegasus just jumps to the frequency that is enough for running the apps (maybe less than enough => a bit laggy). zmoove tends to peak to the highest frequency => smooth and then it turns off unused cores
[Galaxy S III Android Development] jimdem:
I can also confirm that beta 14 is perfect. Running Archidroid 1.7.6 ;)

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] khalid0099:
Using andi2 profile its perfect :D
[Galaxy S III Android Development] boyheadkick:
How do i wipe this batterystat.bin file?

when you say battery calibrate, do you mean use the phone till 1% then charge to 100% untouched?

Tapatalked from my OmegaDroid i9300
[Galaxy S III Android Development] axetilen:
no just wipe the file and reboot

you can download battery calibration on playstore and it will do it for you, and then uninstall it

or you can delete it from the folder /data/data/batterystats.bin if Im not mistaken
[Galaxy S III Android Development] D00ky:
Andi probably you haven't seen my post as you've been away when I posted it. You have any idea why this would happen?

Edit: It is happening also with the latest beta14
[Galaxy S III Android Development] Robi959:
Using beta 14 no problems for me. Boeffla you can mak stable edition because is realy stable with no problems ! :D
[Galaxy S III Android Development] andip71:
I have not overlooked it, but I tried to replicate the issue on my side and was not able to. Whatever I tried.

So I decided to keep quiet for now and see if others report the same.

Andi
[Galaxy S III Android Development] D00ky:
Any chance to be bad flash of the rom? I've already flashed few times the kernel so this is ruled out.
[Galaxy S III Android Development] andip71:
I dont think so.

I think it is more a combination of several things that come together in an unlucky mix at your side.

Maybe it is the combination of configured other settings with apps in the background etc. etc.

Really hard to say without seeing anything and not being able to replicate.

Andi
[Galaxy S III Android Development] cyberlord86:
I have experienced the same issue. Have not found the solution tho. Even on fresh installs on ROMs with default frandom on. Solution? I stopped using zzmoove. More than that, zzmoove performance gives me Android OS battery drain bug, on 4.3. One more reason not to use it. Downside? Zzmoove performance gives me the most smoothness on my device. :)

Since I am not battery junkie, now I'm using PegasusQ stock. Cfq. No bugs, no lags. No stupid drains. Can't get more then 3.5h screen time. But for lag free I am willing to pay the price. :)
[Galaxy S III Android Development] janres155:
I have better battery with the google toolchain. I had drains with the linaro one. I dont know, I just had bad results with beta13.

Sent from my GT-I9300
[Galaxy S III Android Development] ZaneZam:
<advertisement on>

exactly axetilen, nice and right explaination but u maybe have to "update" your opinon when u finally use v0.8 of zzmoove governor :) because you can use it then for playing games too without loosing unnecessarily more bat or heating up your phone because of the fast scaling behaving! i fortunately managed to calm down the beast in that direction! now it even behaves (in fact it just looks like so) similar to pegasusq but freq jumps are not that striktly like they are in pegasusq. some kind of middle thing between pq and zz in terms of scaling. so you can expect no lags but better bat and less heat during gaming. all that of course depending on the current setup ;)

<advertisement off>
[Galaxy S III Android Development] andip71:
Well, personally I did not have higher battery drain, but many other reasons made me returning back to Google standard toolchain.

So, we should be happy with beta14 now. It is intended to become 5.1 stable.

Andi
[Galaxy S III Android Development] ZaneZam:
eh sorry but as the name "zzmoove

performance

" implies it gives u

performance

and that is in fact

not

a

drain bug

, it's more a

performance feature

and performance needs energy :)
[Galaxy S III Android Development] cyberlord86:
It's not a bug, it's a feature. :P Even tho you are creator of this particular governor, I have to say that situation like that I described in my previous post, did not occour in 4.1.2 ROMs. :)

Android OS drain while sleep. :)

Damn, but it is smooth. :D
[Galaxy S III Android Development] andip71:
Honestly, also that is not a bug of zzmoove, nor a feature.

It is simply the fact: Sammy 4.3 roms are very young and far away from maturity of their latest 4.1.x roms.

I am pretty sure, with new rom versions, new kernel source code drops by Sammy, this will all get better again and again over the time. As it was with 4.1.x.

The question is only, if we will still see that or move on already soon.

Andi
[Galaxy S III Android Development] JustClass00:
I have big problem I do what do your says.but still have problem I load your Andi and restart phone then open configv2app and all settings change this is screenshot.and when retry active your Andi load and work fine retry restart change settings please add default profile enabler on your config app

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Android Development] andip71:
Ok, then there is only one option left:

You have an init.d script blocking the startup sequence.

Send me a kernel log file from your /boeffla-kernel-data folder. Or easier: Create a debug info file in boeffla-config and mail it to me.

support@boeffla-kernel.de

Then I will tell you what is wrong and how to fix it :)

Andi
[Galaxy S III Android Development] syedkamal92:
Using official 4.3 ml2 removed alots of bloatwares, greenify playstore, and using battery doctor..boeffla kernel beta 14 and using andi's profile
[Galaxy S III Android Development] JustClass00:
Okey I send mail and all log files and debug .

And this is my battery status :) I use stock mk6 remove bloatware and Andi profile

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Android Development] andip71:
Hi,

I just answered you by email as well: It is a broken init.d script (or let's call it "non-optimized") which you apparently need to make your phone working with a corrupted EFS.

I provided an improved version of the script to Zuluman a while ago, he provides it on XDA in the following post:

http://xdaforums.com/showpost.php?p=49188350&postcount=1637

If you flash this, all will be fine again. :good:

Andi
[Galaxy S III Android Development] JustClass00:
Thanks Lord boeffla you are the king !!!

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Android Development] jimsiv:
Hi Andi,

Once again great job with beta 14 which I think you should name it stable. I don't have any battery drain even if I switch between governors...I tried them all today and it is just perfect. Thanks for your great work!

Sent from my GT-I9300
[Galaxy S III Android Development] borjaag:
Boeffla 5.2 and Zzmoove 0.8? :p

It couldn't be better! :D
[Galaxy S III Android Development] andip71:
Yes, that is the roadmap.

Now let's hope beta14 is rock stable over the next 2 days, then I make it stable on Monday next week.

And then 5.2-beta1 with zzmoove 0.8, yeeeaaaayh.

Andi
[Galaxy S III Android Development] JustClass00:
Boeffla solved my problem it is the script problem cause i use zuluman old init script and not a kernel problem :) thanks LORD BOEFFLA

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Android Development] andip71:
You were welcome :)

The debug info file function is super powerful to analyze problems efficiently, I think I should advertise it more...

Cheers

Andi
[Galaxy S III Android Development] PIRATA!:
I'll try to slit stream on 4 devices leaving it at 300 like stock.

About PegasusQ you're trying...is it the battery version or just classic??

Let us know your results eh!!!!!!!! ;)

About Wi-Fi I'll try to see what I can do.

About modem, the Fast Dormancy thing I mentioned before could help? I mean disabling it for both my networks (main & roaming).

So you say that PegasusQ battery indeed shuts all cpus fast?? Did you modded it to do so??

You talk about core 0, 1 & 2...but core 4??

How can I set static IP on my device??

Ok for the other things! ;)

This is only needed if config is not loaded correctly, right?
[Galaxy S III Android Development] andip71:
Ok, give it a try if you really need zRam. I do not have it activated, I really do not need it.

No, I am not trying the standard pegasusq, I am trying the one with my "boeffla moderate" profile. I used that last time on 4.1.x, so I think I want to see how it works with 4.3 now.

I never had an issue with Dormancy, but many people say it helps in their networks. So why not just giving it a try...

Andi
[Galaxy S III Android Development] Mr. Despair:
Used so far the zzmoove governor and tried the different battery saving options, also with changing schedulers.

But after all this discussions here I tried the PegasusQ with Boeffla Battery config (plus AFTR+LPA and Aggresive power saving). Although I had in mind that this governor isn't optimised for efficient multicore usage. But with that in combination with Zen scheduler I have the best battery life and performance. Don't know exactly how Lord Boeffla tamed the PegasusQ, but it works very great. :D
[Galaxy S III Android Development] boyheadkick:
didnt mod it at all, it's just what i see on Cooltool

core4 seldom kicks in..that's the nature of pegasusq, i guess, in that it uses cores 0 and 1 more than 2 and 3..
[Galaxy S III Android Development] k6?:
Perfectly stable kernel for me. Great work Andi..

:cool:
[Galaxy S III Android Development] chaoxe:
Guys, I was wondering if anyone is using this kernel with Paranoid Android 3.99RC2? Want to test it out after loving it while using UltimaROM.

Thanks in advance for any replies.
[Galaxy S III Android Development] boyheadkick:
no one has used this kernel for PA, PA wont load :D

there's a CM version of this kernel though, that would be compatible with PA
[Galaxy S III Android Development] chaoxe:
Deleted. Answer was common sense.
[Galaxy S III Android Development] zhuoxian:
Good job Andy,Is there need to remove init.d folder? I am on omega 54?

from my I9300 omega 54 tapatalk
[Galaxy S III Android Development] axetilen:
open wifi setting -> long hold your home wifi access point -> advanced -> set your ip, subnet mask, default gateway,...
[Galaxy S III Android Development] JustArchi:
[MENTION=3279788]ZaneZam[/MENTION] sent me a beta kernel with new brand new beta of zzmoove, which in fact handles constant load VERY well even with default values. I don't want to spoil much, but I'll definitely reconsider using zzmoove in all of my boeffla profiles when it's released.

It's getting even better ;).

As for now, power saving pegasusq gives me the best results, both for gaming and normal usage. Zzmoove can give you even more than that, but will perform worse in the games (battery life). However with new zzmoove beta, it's no longer true and I'm looking forward to make some advanced tests when I find some time between my finals...:)
[Galaxy S III Android Development] zhuoxian:
Andi

I created shortcut ,switched to other profile, nothing changed when I go back to see in the boeffla config

from my I9300 omega 54 tapatalk
[Galaxy S III Android Development] syedkamal92:
thanks andi for the great kernel !!!!
[Galaxy S III Android Development] Hidden-Hunter:
hi Friends

Best profile for maximum battery use and save max battery in deep sleep??

tnx_:fingers-crossed:
[Galaxy S III Android Development] PIRATA!:
Thank you.

So you are testing PegasusQ only activating the Boeffla moderate profile...

Well, let us know the results;)

Cooltool..mmm.....I'm better take a try in it! ;)

But the fact is still strange as it should not be so quick...

And I'll end up with static IP only with that access point?? Seems interesting.....
[Galaxy S III Android Development] ymy3890:
your configuration can share?

Mind sharing your configuration?
[Galaxy S III Android Development] jj92942000:
There's a new Boeffla config thread just for that search and check it out. Oh hell here it is

http://xdaforums.com/showthread.php?t=2621308
[Galaxy S III Android Development] sassinapoli:
Andi i installed an apk.

Reboot phone and apk was not installed on my phone.

I have delete zipalig file in system/etc/init.d? (In this folder i have two files named zipalign...eliminate both?)

Confirm?

Thxx

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] andip71:
As already told, I uploaded it in the other thread that has been posted already.

Confirmed, remove both. Zipalign scripts do under some circumstances cause trouble. I really ha**e these scripts.

Andi
[Galaxy S III Android Development] MIKEMON:
It is better to delete the folder init.d or keep?
[Galaxy S III Android Development] zalaros:
When using boeffla kernel on Samsung 4.3 stock rom, does power saving option of the rom do anything? Does it affect the battery life?
[Galaxy S III Android Development] PIRATA!:
Just disable it. It is worst using it.
[Galaxy S III Android Development] zalaros:
Thanks for the reply. I have another problem now, in camera i get the "camera failed" warning. Could this be a kernel issue?
[Galaxy S III Android Development] k4bbe:
Flashing another kernel, rebooting, start camera and then reflashing Boeffla usually fixes this for me. Tends to happen after a rom flash... Not sure why :cool:
[Galaxy S III Android Development] zalaros:
Could you give me a link please? I'm far away from my pc and doing this from my s3 is difficult. I would be extremely grateful if you could do that. Thank you in advance.

Edit: I mean a link from the "other" kernel that you use.
[Galaxy S III Android Development] boyheadkick:
try clearing data of your camera app first before doing any flashing..flashing something else should be your last resort, be it rom, kernel or mod
[Galaxy S III Android Development] k4bbe:
I'm using the phone too... So that's no excuse really :cool:

Don't really want to post a link to another kernel thread... That's not cool.

Just go grab one from the original development thread.

I doubt clearing data will work as it never does for me, but by all means give it a go :cool:

Remember to flash boeffla back once the camera is back online ;)

Let us know how you get on.
[Galaxy S III Android Development] zalaros:
Nope your trick didn't solve the problem. I get the same warning. I don't know what else to try.... Thanks anyway :thumbup:
[Galaxy S III Android Development] janres155:
Hi Andi

I think you should include or mention the unofficial thread of boeffla profiles at the OP.

This is to prevent forumers to ask the same questions about what settings to use.

This way, they can have ideas where to start..

Regards,

Janres
[Galaxy S III Android Development] kunal1540:
Flash a stock kernel open camera then flash boeffla with your settings...