yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] nelsonw:
Hi Andi and friends, for a few days I felt my phone really slow. Now I found this source of the slowdown. 3cores are offline. Didn't know what i did or install to shutdown the cores 1-3. How to turn on? Where to look? Thanks!

I'm on imperium 25 with latest beta.

I installed 5.1 stable and I now have all cores up and running... Let's see what happens... Thanks!
[Galaxy S III Android Development] andip71:
Rom? I am not providing roms :)

If you mean the kernel: What governor are you using? zzmoove is included in a beta version with some known issues still.

If reading about this topic and all the options you have makes you having headaches, then I agree, then is better to use stock and be happy.

See my first answer, you are using zzmoove in a beta version which has some known issues.

ZaneZam is working hard on fixing the known stuff.

I am currently testing his RC2 of zzmoove, looking great so far.

Have you rebooted while your charger was plugged in?

You should always plug your charger AFTER you booted your phone only, to make the charge control really taking over control.

I personally do not use it at all, I like the sharp and crispy display of Samsung stock.

See first answer, I am quite sure you are on zzmoove?

Andi
[Galaxy S III Android Development] nelsonw:
no, I was on IntelliActive...
[Galaxy S III Android Development] you_man:
Yes =\
[Galaxy S III Android Development] MIKEMON:
yes, I have some problems with zzmoove, but I expect the new patched version

It's my favorite gov ..

many thanks
[Galaxy S III Android Development] ymy3890:
Ok, i will stay away from Zzmoove until it's fixed..:cool:
[Galaxy S III Android Development] ahac85:
Anybody experiencing boot loops when using pegasus speedmod

Sent from my GT-I9300
[Galaxy S III Android Development] ymy3890:
I am using PegasusQ battery saving and not facing such issue.
[Galaxy S III Android Development] megen:
Imho rebbots usually caused by rom or umundervolting not by governor.

GT-I9300 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy S III Android Development] andip71:
This is true. Although, when the phone is "close to the border", e.g. caused by undervolting, it can make a difference when you change other parameters, even the governor.

Example: Lets assume the phone runs fine on low frequencies but due to heavy undervolting, not on the higher ones. So by choosing a governor that uses more the higher frequencies could lead to reboots sooner than later.

Just an example to make people understand.

Thanks

Andi
[Galaxy S III Android Development] you_man:
Hi, Lord.

Charged all night with 475mA, everything is fine.

Thank you.

Another question. How much is the minimum you can put to mA phone is charging?
[Galaxy S III Android Development] andip71:
Well, basically it is the minimum of the sliders in the config app.

USB I allow down to 0 even (no charging at all, but with some side effects).

Charger goes down to 100.

Andi
[Galaxy S III Android Development] you_man:
That is, you can safely do Charge rate AC - 100mA and the phone will be charged?
[Galaxy S III Android Development] andip71:
It will be super slow, expect something around 15 hours at least.

But slow charging does not add any risk, it is more vice versa. It is supposed to be good for the battery. But nobody really has the time to load that slowly :)

Andi
[Galaxy S III Android Development] you_man:
300mA then it will be optimal for charging at night ~ 8 hours.

Ideally.

Thanks again ;)
[Galaxy S III Android Development] D00ky:
About charging current not sticking after reboot

Yesterday my phone shut down due to empty battery. After connecting charger I turned on the phone and checked Charge info in Boeffla app. It was custom selected current, in my case 500mA (I always charge my phone during the night so I don't need faster charging). If I understand correctly custom charging current shouldn't stick if charger connected during reboot. In my case charger was connected when phone off but after turning it on custom charging current sticks.
[Galaxy S III Android Development] andip71:
Yes, you are right, and I was a bit inprecise last time:

- custom selected current does also stick when you have the charger connected during a reboot

- but the ignore switches will not be active in that case, even when they are switched to on

So, it works half :)

Andi
[Galaxy S III Android Development] andip71:
5.2-beta6

Hi all,

I am currently uploading beta6, which should be the last beta version before I want to release this kernel series as stable.

Version 2.2-beta6

Updated zzmoove governor to version 0.8 RC2 (credits to ZaneZam)

Hint: Do not use multicore powersaving in combination with zzmoove as this is known to cause weird issues!!

Added new zzmoove profile "zzmoove - insane", note this is still in beta (credits to ZaneZam)

Enable USB OTG wired Ethernet support (load Asix module in settings, you need a compatible Asix based USB-Ethernet adapter!!!), dhcp used for ip configuration

init.d handling changed to omit zipalign scripts (all other scripts still run fine)

Remove debug logging in cpuidle-exynos4

Enjoy

Andi
[Galaxy S III Android Development] you_man:
You can read more about this?

You are my god, thank you.
[Galaxy S III Android Development] andip71:
I will leave the detailed description of it to [MENTION=3279788]ZaneZam[/MENTION], but in short the highlights:

It is a profile for high performance with zzmoove

Hot-Plugging of CPU cores is not that aggressive, which results in better overall performance

But I am sure ZaneZam will add some more info about it, as he created the profile.

Andi
[Galaxy S III Android Development] ZaneZam:
yes exactly andi, hotplugging was changed IN ALL SETTINGS just to be less aggressive in terms of down plugging, up plugging should be now as fast as possible depending of the used settings - we should have performance benefits from that and lesser hotplug overhead. higher/lower battery consumption is unknown as there exists no long term experience atm, (this version is about 12 h old ;) ) "InZane" setting (all settings work in progress!) in particular is atm basically the performance setting with just the new auto fast scaling enabled as preview. this settings makes whole freq scaling "just different" - check it out, im curious how it works for u guys :)
[Galaxy S III Android Development] ymy3890:
Great!

Will flash to confirm high mzh is fixed
[Galaxy S III Android Development] you_man:
I'm confused.

Beta 6 (zz RC2)- all profiles ZZ= lags

Beta 5 (zz RC1)- all profiles ZZ= ideally

:confused:
[Galaxy S III Android Development] marenp:
Just flashed beta 6 and it so far so good :) no lags, no conflicts, no problems at all.

Andi thanks for great work :D
[Galaxy S III Android Development] keneth_c:
Hey dev... Thanks for v5.2 beta 6 :)

--
[Galaxy S III Android Development] Hidden-Hunter:
Thanks [MENTION=947981]Lord Boeffla[/MENTION] [MENTION=3279788]ZaneZam[/MENTION]

New profile in zz is zz-insane ?

and zz-insane use 2cores?

Thanks:good:
[Galaxy S III Android Development] andip71:
I am not aware zzmoove - insane should be using only 2 cores.

It should use all 4 when there is enough load.
[Galaxy S III Android Development] ZaneZam:
really? i had a opposite feeling :) but seriously on every setting?

yeah :confused:
[Galaxy S III Android Development] you_man:
Really, all profiles(.

Back to beta 5 - all perfectly
[Galaxy S III Android Development] Robi959:
Zzmove optimal works great for me. Beta 6
[Galaxy S III Android Development] ZaneZam:
yes and atm its "just" the performance profile with a new featue (auto fast scaling) enabled

no it should not use only 2 cores and i strongly hope it doesn't for u! :)

the 2 core "moderate" setting is coming with final then, i need a bit time to adjust/test all settings ;)
[Galaxy S III Android Development] Hidden-Hunter:
Really Thanks [MENTION=3279788]ZaneZam[/MENTION]

Only using for chat.sms.call.web surffing , Which do you recommend profile ( zzmoove: optimal/yank/extrem yank) ??

Thanks:good::laugh:
[Galaxy S III Android Development] ZaneZam:
i would say still yank battery as this is still the balanced one. ;)
[Galaxy S III Android Development] Hidden-Hunter:
Hi Andi

I can not make you buy the Professional version ( boeffla donate ), because Google Play has banned my country ! :(:crying:

I live in Iran...:D
[Galaxy S III Android Development] andip71:
You can try via www.androidpit.com.

They do not have bans as far as I know.

Andi
[Galaxy S III Android Development] ScratMan38:
[MENTION=947981]Lord Boeffla[/MENTION] : I'd like to update my TWRP recovery, but it is only available as .tar or .img files for the moment. I saw your config app is able to flash .tar.md5 files in it's donation version. Is there any difference between the two extensions ? can I flash .tar file with Boeffla Config v2 ?

Thanks
[Galaxy S III Android Development] andip71:
ScratMan38: Yes, there is a difference.

The tar.md5, which I allow to flash in the config app, includes a checksum to check if the file is downloaded fine. A normal tar does not have that.

That is why, per default, I do not allow flashing pure tar files for safety reasons.

However, you can rename the .tar to .tar.md5. This workaround should be ok to flash the recovery for you anyways. But the risk you flash a corrupted file etc. is then on your side (well, not a biggie, you can always flash over again).

Andi
[Galaxy S III Android Development] keneth_c:
Just flashed a ROM today and flashed Boeffla beta 6... Used zzmoove insane profile and it was a bit laggy... 1 reboot... And froze once at lockscreen after boot up. Had to hard boot the phone then.

Went back to zzmoove battery yank... And 1 sudden reboot after restart.

I've heard PegasusQ is good... But battery on it ain't that good. Feels like battery drain.

Moreover I so love zzmoove... It's hard to make the switch :p

--
[Galaxy S III Android Development] andip71:
keneth_c: Did you start from a clean configuration?

If you change the rom, you should always reset the boeffla config app once in the settings to make sure the configuration is clean.

Never experienced what you had...

Andi
[Galaxy S III Android Development] keneth_c:
Yes my lord :p :)

Coz I flashed stocked Sammy ROM (NA7) first... And then flashed ARHD v50 next. And then Boeffla kernel beta 6.

Still having battery drain... But maybe I should wait for a day or 2 till ROM settles maybe?

--
[Galaxy S III Android Development] andip71:
Yes. Give it one full charching cycle at least.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] Saenic:
Hey, its me again with my bugging about root rights for adb to make stuff like "adb remount" work.

In adb shell I can do "su" (and granting permission with Superuser app) and then "mount -o remount,rw /system" but it does not work from commandline with "adb shell mount -o remount,rw /system" or directly with "adb remount".

So would this be possible to add? :]
[Galaxy S III Android Development] MIKEMON:
Lord Boeffla § ZaneZam

really great work, kernel and zzmoove gov., is close to the final

Application config, amazing
[Galaxy S III Android Development] khalid0099:
Insane is it battery save or performance or middle :confused:
[Galaxy S III Android Development] andip71:
I had that in at the very beginning. But it broke adb for other things like app debugging etc.

So, if you know a fully compatible, patched adbd, then yes - no problem.

I was not able to find one which did not break anything, so I decided the adb remount can be sacrificed for the moment.

Performance, mainly.

Andi
[Galaxy S III Android Development] ZaneZam:
it's insane no one knows it yet, not even me! :eek:

well seriously the base of this setting is the well known performance setting BUT the scaling uses the new auto fast scaling mode

which means it scales up/down fast has hell so maybe there is no impact on battery or it even saves more then other

settings i dont't know. it was a experiment of mine in one of the latest 0.8 betas which gave me surprising results

but i have absolute no long term experience with it.. so WE have to learn and see what happens by using it :)
[Galaxy S III Android Development] MIKEMON:
practical tests, the best show you'll use

but even so, great job
[Galaxy S III Android Development] psyntific:
Thanks for the kernel Andi.... The only issue I've got is that real racing 3 keeps force closing on all of your kernels even on the stable 5.1... I've tried both beta5 and 6... Still the same result.. Tried different governers n different gpu frequency sets... No luck... Can you please take a look at this
[Galaxy S III Android Development] andip71:
Sorry to be very honest with you.. Gaming is something I am not really interested. I never installed a game and never will. See also OP.

But maybe others have hints, I know people are doing gaming as well with my kernel...

Andi

Gesendet von meinem GT-N8000 mit Tapatalk
[Galaxy S III Android Development] Ubimo:
Just flashed 5.2-beta6 and testing zzmoves insane profile.

1600 MHz max

AFTR + LPA

multicore powersaving disabled

-100mV undervolt

row

row

BEST result in quadrant benchmark so far! (7006 points overall) :victory: (I know Lord B does not like/appreciate benchmark results)

The phone is very responsive and fast, no lags. Well done!

Now I'm looking at the battery consumption very closely and report back after 24h. (daily usage testing)

Edit:

I cannot record videos but this may not be kernel related. Says "recording failed". Investigating...

Edit2:

Lord B: I feel like Evel Knievel - may/will you provide overclocking up to 1704 MHz?
[Galaxy S III Android Development] ahac85:
I also experiencing this I dnt undervolt at all. Using stock mk6

Edit2. Noticed using perfmon cpu still gets locked. Using zzmove optimal beta 6

Sent from my GT-I9300
[Galaxy S III Android Development] jj92942000:
On Omega v56 with v5.2b6 it's awesome. Tried zzmove insane and it's just like its name!! Loving it but for normal day to day will be back to battery yank. Thx Andi great job and ZaneZam too
[Galaxy S III Android Development] ZaneZam:
Oh now I have to ask stuck on which freq and when exactly? during normal operating or right after suspend?
[Galaxy S III Android Development] glockaki:
the new beta is very good.had some freezes after installing.but now everythung is fine.thanks

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] ahac85:
Ok sorry my explanation was wrong it is stuck on one cpu, the freq scales up and down from ranges 200 to1400. But other cores do not fire up. I rebooted my phone aĺl was fine then shortly phone became laggy, I checked perfmon and only 1 core was running

Sent from my GT-I9300
[Galaxy S III Android Development] ymy3890:
no more high CPU usage

Installed Boeffla Kernel beta 5.2 Beta6 yesterday and using Zzmoove battery extreame.. so far no appearance of sudden high frequency issue reported that before, maybe due to no such issue my phone felt smooth,,, need to test with full charge and play some games to confirm.

So far no reboot, freeze or lagging issue as report by others. Welldone Andi and ZZ...:good:
[Galaxy S III Android Development] ymy3890:
Beta 5 with zzmoove my CPU stay at 1.4 mhz after using awhile. Eaten my battery so much. Need to restart system to solve the problem
[Galaxy S III Android Development] andip71:
beta5... or did you mean beta6?

Andi
[Galaxy S III Android Development] PIRATA!:
How can I really understand if Boeffla config is/isn't working correctly without reading a log??

I'm still on Beta4 as I had to work a lot and hadn't time for my cell phone..

I feel good with it, but better battery would not be bad.

I was just looking to this new Beta6 description, and noticed that you say to keep "Multicore Powersaving" off with zzmove governors...why??

Did I missed something about Beta5?

What does it cause to use multicore powersaving with zzmove? I'm not noticing nothing bad...or at least I can't see it.

For now, have you noticed something about performance/battery?

Specially for battery...have your noticed to be better then other zzmove or what?

Thank you all.
[Galaxy S III Android Development] syedkamal92:
im using intelliactive from beta5 released and now beta6.. great performance..no lag at all than zzmove.. thanks lord
[Galaxy S III Android Development] JustArchi:
The best power saving governor will be always the one, which uses lower/lowest frequencies longer, and in addition to that - less cores.

The *best* powersave is exactly with 200 MHz @ 1 core active, which zzmoove likes to apply in idle load (:good:).

The most smooth governor will be the one, which can adapt frequencies fast enough. However the "fast" definition is also important because the faster the governor, the more battery drain in idle (cpu load).

Zzmoove is great solution mostly because it gives you smooth experience with less battery drain than other governors (such as intelliactive), due to the fact that it immediately brings idle load when it's possible. The most powersaving governor will be probably pegasusq with tweaked settings (such as boeffla power saving preset).

Just for reference:

1. Archi.bcprofile uses zzmoove optimal

2. Archi_Performance uses intelliactive

3. Archi_UltraPowerSave uses pegasusq boeffla power saving

These are, of course, my profiles (shared in proper linked thread), and they're based on my knowledge what *is* the best option for performance, battery, and mostly important - balance between both. This is why I like zzmoove, because it gives smoothness when required, and it gives power saving when not.

Thanks to [MENTION=3279788]ZaneZam[/MENTION] and [MENTION=947981]Lord Boeffla[/MENTION]
[Galaxy S III Android Development] andip71:
Just quick, I am uploading a maintenance release right now:

Version 5.2-beta6a

11.03.2014

Back to proven and stable Google gcc 4.7 stock toolchain (have some doubts on gcc 4.8)

Andi
[Galaxy S III Android Development] gieffe22:
today i can't test it because i'm on a short trip out of town...so i have to use a "safe" phone(and beta6 for me work perfectly)... on next days i try it...for now i have to wait other members opinions!!!
[Galaxy S III Android Development] andip71:
No issue, there is nothing spectacular in beta6a. As I said, just a maintenance update for those that have weird issues which they cannot explain.

Andi
[Galaxy S III Android Development] andip71:
So, already some users that had strange effects with beta6 reported, with beta6a all is fine again.

Lession learned: Google stock 4.7 toolchain seems to be more stable than 4.8 (at least for kernel compilation)

Thanks

Andi
[Galaxy S III Android Development] JustArchi:
Andi, take a look here. This was the only needed commit I had to add in order to compile stock kernel with GCC 4.8 (it compiled fine, but didn't boot / had weird errors).

It may help if you didn't have that already, otherwise I don't know :). Cheers!
[Galaxy S III Android Development] andip71:
Thanks Archi, that was also the commit I was using as well.

And it did compile well and works fine for many users. But not for all it seems.

Also Googy removed 4.8 toolchain again. So, maybe some more code needs to be changed to make it work with 4.8 more reliable.

But 4.7 is not worse as such, it is a proven rock-stable toolchain. So I feel better with it for now.

Andi
[Galaxy S III Android Development] adzz37:
sorry for this very noob question.. im new on galaxy s3.

i just want to know if this kernel will work on neatrom 6.5 xxugna7 4.3.1 jellybean rom? or only for 4.1.2 roms...

this kernel looks so good nd promising... thank you..
[Galaxy S III Android Development] andip71:
The 5.2-beta series should work fine for your Neatrom version.

Andi
[Galaxy S III Android Development] marenp:
Flashed beta6a and put zzmoove governor and optimal profile :) lets see how it will behave :)
[Galaxy S III Android Development] andip71:
Jepp, tell us after a day or so, please.

Andi
[Galaxy S III Android Development] JustArchi:
What are those "weird issues" exactly?

I'm compiling stock omni kernel every time I compile ArchiDroid, currently with GCC 4.8 (ROM with Linaro 4.8), I can see if I (or my users) can reproduce any of that.
[Galaxy S III Android Development] Ubimo:
Reporting back after 20h on:

5.2-beta6 and zzmoves insane profile

1600 MHz max

AFTR + LPA

multicore powersaving disabled

-100mV undervolt

row

row

Battery drained from 100% to 65%

Conclusion: Very fast and snappy profile but on the cost of power consumption.
[Galaxy S III Android Development] ahac85:
Beta 6a working absolutely fine :)

Sent from my GT-I9300
[Galaxy S III Android Development] andip71:
There are plenty of reports for weird effects I got from users since beta6.

Automatic reboots directly after start, freezes, hot reboots, frequency stuck issues... all users reporting that now reported the issues are gone with beta6a.

So.... not sophisticated and scientific, but a clear pointer as the only change is now recompilation with 4.7 toolchain instead of 4.8.

Andi
[Galaxy S III Android Development] viktor92:
I was on beta6 until a few hours (beta6 linaro now) and the kernel was as stable as always, not a single issue...
[Galaxy S III Android Development] keneth_c:
Same here. Switched to beta6a... So far so good.

I feel like my battery is draining but I'm not for sure. I'm a n00b with kernel settings so all I've done is... Using zzmoove governor and profile battery yank.

However as mentioned yesterday... I just updated my ROM... So gonna give it another battery cycle to check.

--
[Galaxy S III Android Development] andip71:
Keneth_c: It is almost never the kernel being the root cause for high battery consumption.

Install BetterBatteryStats app from XDA to check your deep sleep rate and especially the partial wakelocks. This will enable you to find out what exactly keeps your phone awake...

Andi
[Galaxy S III Android Development] PIRATA!:
What about "Multicore Powersaving" with zzmove? Still issues?
[Galaxy S III Android Development] keneth_c:
I have batterystats already...

At least I know where to look now... Thanks!

--
[Galaxy S III Android Development] psyntific:
Lord Boeffla thanks for 6a.. The game works fine now... Awesome kernel... Luv the app too... Thanks again mate
[Galaxy S III Android Development] MIKEMON:
no problem with beta6, I will compare with 6a

I'll see you tomorrow, thanks
[Galaxy S III Android Development] treyy:
Ok. Mh. I dont know if it works with the stock kernel.but it works with syiah,galaxsih and i mean with yours to until the new beta

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] mclaudio:
Is there a interface program for set up options? Regards
[Galaxy S III Android Development] treyy:
U can use apps like voltage control or setcpu for some. Or u use a config File. for more information look at the first post.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Android Development] saintsinner25:
Lol good story dude :) amazing kernal too i got. 1h of on screen time and i was playing jetpack joyride all this while and 81% is still left! Awesome :D

Sent From My GT-i9300 ;)
[Galaxy S III Android Development] tommyrumbler:
much love to this kernel.simplicity meets solid performance. codec and this kernel are an unbeatable combo for me.
[Galaxy S III Android Development] saintsinner25:
Now the only thing missing for me is boeffla-sound with a customizeable UI :) no disrespect or eta or anything just giving a +1 to your idea ;)

Sent From My GT-i9300 ;)
[Galaxy S III Android Development] romwhacked:
Flashed on stock odex DLJ1 and everything is fine so far hope it continues..Thanx andi for keeping this so simple the .conf thing is really great
[Galaxy S III Android Development] Pusheka:
?

Beta3