yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ikador:
YES. Device is hot-Andi
[Galaxy S III Android Development] kadopt:
Your device can get hot for a number of reasons : cpu load, gpu load, low network signal, incorrect voltage settings for cpu and/or gpu, etc... Try a different governor, see if anything is keeping your device from deepsleeping, undervolt a little(like 25 or 50 mV on the cpu), etc.

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] ikador:
Yes

I did not touch any of the settings on the default mode. Course I did not install the kernel config and I just flash the kernel
[Galaxy S III Android Development] FlemishDroid:
I can only advice to install the config v2 app...

Verstuurd vanaf mijn GT-I9300 met Tapatalk
[Galaxy S III Android Development] sayaksark:
Hello andi,

Im on archidroid rom, there are two strange problems...

The touch wake option is automatically switching off after reboot... And the sound panel is also completely switched off....Can you show me some light
[Galaxy S III Android Development] JustArchi:
Second option is connected with DSP manager, and is ROM fault.

First option may be connected with advanced settings.
[Galaxy S III Android Development] metalgearhathaway:
Hi [MENTION=947981]Lord Boeffla[/MENTION]

I puchased the donate version and wanted to alter the value for "freq_limit_sleep", but it is not in the tunable section, has it gone or is it gov specific, i.e. not available to pegasusq?
[Galaxy S III Android Development] janres155:
I think pegasusq has no parameter "freq_limit_sleep" or maybe it is named differently.

As far as I remember, zzmoove has this parameter.

Janres
[Galaxy S III Android Development] Avalun:
Hi, You have serveral Modems for the S3 on your page. I use your 2.2 Kernel with the latest SlimKat, which do you recommend, I should install?

At the Moment I have: i9300XXDLIB but I encounter a increased battery drain after a call, till the next reboot.
[Galaxy S III Android Development] ZaneZam:
it's a zzmoove only feature ;)
[Galaxy S III Android Development] andip71:
Dlib is a good modem for cm.

But this is not a problem of the modem, it is a known issue with cm based, older roms.

There are fixes provided I heard.

Sorry for only short message, I am still in holidays.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] striked0wn:
Btw andi.. Which modem you are using with cm/slimkat or on stock rom in berlin.. ^^..?!.. And with which provider..:)

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] DirkStorck:
For this "battery drain after a call" there exists a fix. Look at this thread [V5][FIX][CM][OMNI][ALL AOSP]Bug Fix : After call battery drain in AOSP is fixed
[Galaxy S III Android Development] Avalun:
cool, very nice for the fix, thanks very much :)
[Galaxy S III Android Development] andip71:
Xxdlib, Congstar T-D1.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] mad_ady:
I also noticed touch wake off after reboot. I am on 2.2
[Galaxy S III Android Development] RuralGalaxy:
I use omnirom, and use boeffla sound, unistalling dspmanager works great, without problems.

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] sayaksark:
Archi and andi are right

I followed archi and turn on the touch awake option in settings-advance-display.

Now touch awake is working fine
[Galaxy S III Android Development] metalgearhathaway:
If anyone can help me understand the mechanics I will be very pleased!

I wanted to resolve the occasional blip in A2DP bluetooth streaming, so I switched from Pegasusq to zzmoove so I could alter the freq_limit_sleep value as per the FAQ. I have found setting the value to 800mhz resolves the issue.

But, I like to know why, so my questions are:

1) Whats the deal with pegasusq? Does its equivalent sleep value cause the issue?

2) I see some other entries, which to me would potentially control the issue as well without requiring alteration to the freq_limit_sleep, however it could just be that these would be either pointless and/or counterproductive for the remainder of screen off sleep time, but unless I ask I will never rest, if it is a case that I should just experiment as no-one else has then I will happily go into test geek mode:

a) Freq-step-sleep value, increasing this value closer to wake values may assist?

b) smooth_up_sleep & up_threshold_sleep, they both look like contenders to assist the issue.

I am only in to my second month of S3 ownership, so I don't want to test old scenario's if it has already been performed, just finding my way at the moment, I hope someone can educate me :)
[Galaxy S III Android Development] Kord:
I have such a great battery life than even before! I'm using latest CM NIGHLTY and Boeffla 2.2 stable (CM Version).

- 2 hours Music

- 2 hours 39 minutes Display

- WiFi enabled all the time

- 50% battery left

If somebody want, I can provide my settings :)

Thanks Lord for great work! Have a good trip!
[Galaxy S III Android Development] ZaneZam:
well maybe i can :)

honestly i think i'ts a combination of multible things that causes this issues not only the governor one factor is coming from the pretty strictly powersave settings i've made back in the days for my personal usage (yeah i was a power save junkie *g*) not having in mind that zzmoove ever will spread like it did and might make problems with such a scenario as i rarely used bluethooth equipment at that point. but that changed from that moment on i bought a bluetooth car hands-free equipment ;) nevertheless i'm still happy with these settings as for me (with my equipment) and (hopefully! *g*) most of you out there there are no problems with it. so they stayed as they were. well meanwhile they changed a bit, though but that depends on the used setting.

now to your questions:

1.) as far as i know there are no such sleep values in pegasusq and i honestly never did a sleep monitoring with it so i can't say whats the deal :o

2.) yes u are right the combination off all the sleep settings are giving u the good sleep results. you can take a look especially at the new early_demand_sleep tuneables! i added this function in recent versions to try to react the problem without having to rise any of the usual sleep values. so you can maybe have both, fix the issue and having good sleep results when not using the phone at screen off. ;)

a) yes

b) also yes, as said it's a combination of all settings u can influence it with every sleep tuneable. the question is how much it counts if u adjust only one. in addition there are the hotplug_sleep and disable_hotplug_sleep tuneables with it u can control the hotplug behaving at sleep. also something u can try to play with.

so i would suggest to lower the value in the new early_demand_sleep_threshold (early_demand_sleep should be 1 for enabling it)

and see if it helps, it makes the scaling behaving faster at sleep. if not try to lower up_threshold_sleep and smooth_up_sleep and/or increase the freq step value to the analog awake value and or set fast_scaling to 4 or disable hotplugging (all cores online) at sleep or enable for example 2 cores by giving hotplug_sleep = 2 and and and :)

multiple possibilities beside of rising freq_limit_sleep to 800mhz which btw. would have not that big impact on battery so u can just use

that if it fixes your problem! :D

hope u find your setting!

cheers

ZZ
[Galaxy S III Android Development] metalgearhathaway:
Wow, thank you for exactley the answer I was looking for! Very reassuring :)

The 800mhz setting does cure the issue and yes with no negative battery impact it appears, although my test was limited to an hours time frame, so a full busy day on the road will confirm a) fixed and b) battery analysis.

However, I will play with those other tunable sleep elements, I am intruiged to see how the different approaches will fare, damn my annoying brain for being so curious on the matter, but it is good fun finding out.

:good:
[Galaxy S III Android Development] boyheadkick:
maybe you can share your bcprofile in the profile sharing thread :p
[Galaxy S III Android Development] mad_ady:
I'm using slimkat, but I found the same option and now I'm playing with it. Thanks!
[Galaxy S III Android Development] ayoubij:
Does the kernel change the screen timeout on the lock screen? I know the normal behavior is to have a different and shorter screen off timeout at the lock screen than the normal timeout while using the phone. Guess it's a kernel issue since i asked many people using the same rom and don't have this issue. I'm on carbon rom latest nightly.
[Galaxy S III Android Development] andip71:
All roms based on Omnirom have that... Slimkat, Archi, Fusion etc...

No. It does not and it even cannot.

Lockscreen is something handled by the rom, not the kernel.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] metalgearhathaway:
It was short lived, the freq_step_sleep value improves the a2dp issue, but does not cure it.

Experimenting, but tried Intelliactive first as I had not used that one on this device before, that seemed to be much more improved, so I will test on that a little and monitor my results.
[Galaxy S III Android Development] ginzo:
Yes please share, thank you a lot!

Inviato dal mio GT-I9300 utilizzando Tapatalk
[Galaxy S III Android Development] metalgearhathaway:
Interactive governor solves all a2dp issues for me with no need for tuning :) streaming audio over 3g with deezer perfectly!

Interactive also benchmarks as well as zzmoove and pegasusq, so it seems like a winner if it survives my battery test!

Was looking forward to geeking it with the tunables, but seems pointless now.

Sent from my GT-I9300
[Galaxy S III Android Development] iceman0826:
e210s boeffla

can i flash this to my e210s (s3 korean version)? or does it need to be ported?
[Galaxy S III Android Development] Kyle07:
I assume you mean "Intelliactive"? I must agree though. Great governor! Audio glitches are gone and it is super fast and smooth. A bit heavy on battery but worth it in my opinion.
[Galaxy S III Android Development] kadopt:
This is for international model only (GT-I9300).

Sent from my SGS3 with Temasek 's CM11, Boeffla kernel & Tapatalk Pro!
[Galaxy S III Android Development] Choristav:
This kernel should appear here

http://xdaforums.com/galaxy-s3/#kernels
[Galaxy S III Android Development] Kord:
Thanks, as boyheadkick said, posted here ;) -> http://xdaforums.com/showpost.php?p=51529786&postcount=457
[Galaxy S III Android Development] dastaudi:
Status bar disappears and re-appears accidentially

hello!

my status bar in cm11 archidroid is either fixed and locked or it disappears and reappears when I swipe over it.

this happens accidentially - i have not found out yet which configuration setting influences it.

can anybody help?

thank you, yours, david
[Galaxy S III Android Development] metalgearhathaway:
Lol yes I meant intelliactive, battery is hit a little, i'm going to monitor tomorrow as well before continuing tests with some tweaks to the gov.

Either way it's sure nice having the glitches gone!

Sent from my GT-I9300
[Galaxy S III Android Development] Kord:
Hey!

It's Android 4.4 feature, when you open fullscreen app, you can swipe from top to show status bar ;)

This feature is also in older Samsung ROM's (4.0, 4.1.2, 4.3)

Regards :good:
[Galaxy S III Android Development] _Negan_:
It's called "immersive mode" or "extended desktop" you should have a toggle to enable disable it. BTW this is boeffla kernel thread...
[Galaxy S III Android Development] metalgearhathaway:
I have made the following adjustments, to stop the governor from spiking up to 1.4ghz at a drop of a hat, I have lowered it to 1ghz instead after monitoring the effect incremental drops made until I found a limit that satisfied the music app I use (hispeed_freq - 1000000).

I had a quick roll through underclocking, with the result of -25mV off cpu, I could tell -50mV was having slight issues and I lowered my gpu by -50mV on the first two steps. I am hoping to see if those tiny savings offset the slight intelliactive hit, but of course my eye will be on reliability of those values and I'll test days on and off underclocking to contrast and report back.

Intelliactive is a very impressive governor anyway, its very snappy and menu scrolling feels happier with it also. Seems like an unsung winner maybe, the next 48 hours will shed some light!
[Galaxy S III Android Development] ayoubij:
Bro what is ur ASV number? Seems very low if im not mistaken
[Galaxy S III Android Development] metalgearhathaway:
ASV? You'll have let me know what that is dude

EDIT - I now know what ASV is, but do not know how to find out what mine is, any help appreciated, interested to know!
[Galaxy S III Android Development] ayoubij:
Boeffla config app main screen has ASV level.

There is a thread with much more details about it, but it basically means all asv devices with same number has very close values that work.
[Galaxy S III Android Development] boyheadkick:
ASV level as explained by Andi

http://xdaforums.com/showpost.php?p=49688552&postcount=6
[Galaxy S III Android Development] SuperAce609:
Two full days of heavy use. 3G always on (don't even care for Wi-Fi anymore xD) and i have my phone literally maxed out on performance. The battery lasts 2-4 days. Depending on your usage. For me, now it's only 2 days because i got used to it and I'm constantly on my phone. The normal stock battery wouldn't last 6hrs with my type of usage xD
[Galaxy S III Android Development] enigma1981:
Awesome stuff! Wish I could get that capacity without making the phone the size of a small house lol

Would be great to have that sort of on-time! Like old school Nokia battery life isn't it lol

Swyped from my Galaxy SIII using XDA Premium 4
[Galaxy S III Android Development] zeli9:
Well, in fairness those Nokias didn't have the screen size of a small house :laugh:
[Galaxy S III Android Development] SuperAce609:
It doesn't get big. It just gets as big as putting a normal TPU case on it. Definitely easier to hold as well. It's all pros and no cons for me.
[Galaxy S III Android Development] drew071:
Have u flashed this kernel and it's nuts working or are u checking before flashing?

Drew
[Galaxy S III Android Development] GTMoraes:
Boeffla, I'm having some very bad RAM issues.

Idk if that's related to your Kernel or the ROM (PAC-man AIO), but I'm not getting anything more than 10MB free RAM, idle.

It translates to inviable multitasking and browser fighting with keyboard for RAM space

My battery is also going to hell due to apps restarting. They were supposed to stay in memory -- like WhatsApp, Facebook, etc -- but Android keeps killing them

A quick look at "current" apps on Settings, there are always one or two apps "Restarting" -- probably they've been killed and are trying to restart.

Right now, that's my status:

- Facebook, 39MB used (probably listening for push notifications)

- Messenger, 22MB used, restarting (ditto)

- WhatsApp - 17MB used (ditto)

- Settings - 84mb (?)

- Equalizer - 0,00b, restarting

- Google Services - 25MB used (?)

- Metro Notifications - 9MB used (fancy notification app)

- Swiftkey - 19mb (keyboard)

RAM: 827mb used, 6,6mb free

If I try to open Apollo and do something else, anything else rather than just going back to the launcher or locking the screen, it closes.

I've tried enabling zRam, but I think it just made it worse.

Is that a ROM or Kernel problem?
[Galaxy S III Android Development] andip71:
Hard to say. But I would say - if kernel, than many more would have reported this issue. Incl. me, I would have the same issues then.

But I do not have.

However, I am using slim rom or CM nightly only when it comes to 10.2.

From both I know, they are pretty clean.

Generally it is normal if ram is very low, this is how Android works.

But if your user experience is bad, something seems to be wrong still.

Andi
[Galaxy S III Android Development] amppen:
Thanks for the chainfire perfmon tip, just bought it and it's awesome. With that tool I saw that your governor is the only one behaving like I'm trying to make it by tuning the tuneables.

Pegasusq and lulzactiveq are using cpu0 and cpu3 almost all the time in normal light use, even though I'm trying to get single core on light tasks. Your governor is sticking with the cpu0 only like intended, yet rapidly jumping to full quad when necessary.

Mad props :good:

Tapatalked
[Galaxy S III Android Development] GTMoraes:
I see. Thanks for the fast reply.

I'll try updating everything to see if it's some memory leak. If that doesn't solve it, I'll try Slim ROM
[Galaxy S III Android Development] nicesoni_ash:
I am on boeffla right now so yes I tested. I tested with superbeam app with Samsung tab which has stock firmware but the app got stuck at enabling wifi direct. I have mailed and posted in app developer's thread too about this (with no reply yet) , so I just wanted to make sure this kernel support wifi direct. If you use wifi direct, can you explain if I am doing anything wrong?

_____________

Sent from my GT-I9300 powered by Temasek Rom & Kernel

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S III Android Development] STAticKY:
The last word of the new feature in settings is wrong

TP.
[Galaxy S III Android Development] andip71:
... which is, Staticky?
[Galaxy S III Android Development] STAticKY:
Shouldn't it say kernel

TP.

---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------

Sorry. My bad. I red your post wrong :S

TP.
[Galaxy S III Android Development] andip71:
No, it should say recovery.

I got the request of some users, after flashing a recovery, they do not want the phone to do a normal restart (as it is currently) but directly jump into the newly flashed recovery.

And this can be achieved now and configured in the settings...

Andi
[Galaxy S III Android Development] fanistic:
i just sold my sgs3 to buy the new note 3 and am wondering if i would ever get ANdi to make a custom kernel just like the beoffla for the note 3.

used this kernel all through my use of the s3 it was an awesome and perfect kernel.

ANdi pleaseeeeeeee
[Galaxy S III Android Development] zeli9:
Yes, I can confirm this, - zzmoove governor with yank battery profile works absolutely great! Strangely enough I cannot get the same behavior on yank's own kernel, where all cores (sometimes 3, but not less than that) are staying online. I know it's not the place to discuss other kernels, but I though this is related since yank's profiles are used both by temasek and andi, so perhaps yank can shed some light here, perhaps it's a different implementation or I just don't understand how it's supposed to work.. and sorry if this has been explained before. My understanding from earlier discussions was that the idea behind zzmove is in the "race to idle" argument i.e. minimum CPU use on idle and "rapidly jumping to full quad when necessary" which is exactly what I see on boeffla kernel.
[Galaxy S III Android Development] GTMoraes:
What's new on Beta6?
[Galaxy S III Android Development] andip71:
Hm, what is wrong with the search function?

http://xdaforums.com/showpost.php?p=46047194&postcount=250

Or go in Boeffla-Config app when you are on a previous version and select "change log" from the menu...

Andi
[Galaxy S III Android Development] andip71:
1.0-beta7

Hi all,

new beta for you all (just a small update, for both CM10.1 and CM10.2 version):

1.0-beta7

Change log

Upstream to 3.0.98 Linux kernel from 01.10.13

Adjustments on voltage ranges of max77686 regulator (required for GPU undervolting)

Enjoy

Andi
[Galaxy S III Android Development] metalgearhathaway:
Cheers, I am level 2 apparently, so not great, but fine really
[Galaxy S III Android Development] Unicorn9x:
my asv level is 4 :fingers-crossed::fingers-crossed: hohoho
[Galaxy S III Android Development] aliw32619:
My ASV level is 7 , is that something good or bad?
[Galaxy S III Android Development] cheese458:
I got a 6? Good?
[Galaxy S III Android Development] metalgearhathaway:
4-7 rating is awesome, 1-2 is not so great, but only from the perspective over voltage savings and potentially overclocking ability.

I am happily -25mv on cpu and clocked in at 1.6ghz :)
[Galaxy S III Android Development] granadier:
I have asv level 3. Is it good enough??? I get 7 hours hard using the phone til it get around 16% batery live
[Galaxy S III Android Development] cink40:
No it is garbage, throw it away :D
[Galaxy S III Android Development] JustArchi:
ASV level is a number of "chip quality". Higher number indicates more potential in OC and uV, however you're forgetting the fact that the device you're using right now is not the same as it was in the first day - chip quality slowly decreases and even if you have high ASV level, due to using the device it may behave worse than other devices with lower ASV level.

Don't threat it as the only factor in OC and uV. You can base on it, but every device is different, even with the same ASV level. For example I have 2 and I'm running great on -50mV.
[Galaxy S III Android Development] Nic2215:
Glad to hear that I'm 2 and great on - 50 too :thumbup::thumbup:;)
[Galaxy S III Android Development] mortoss:
I have ASV 2 and run on -100mV [MENTION=1516530]150[/MENTION]0MHz stable :)
[Galaxy S III Android Development] SuperAce609:
Why do you guys undervolt? It has no effect on battery at all
[Galaxy S III Android Development] josipborac:
It does..
[Galaxy S III Android Development] SuperAce609:
Placebo effect yeah.

Might as well leave your phone off of you really wanna save battery. Lol
[Galaxy S III Android Development] you_man:
1) Minimal heat processor.

2) The smaller the processor consumes energy, the better for the battery (small savings).
[Galaxy S III Android Development] josipborac:
It works for me.. Never could reach 8h SoT before UV.
[Galaxy S III Android Development] JustArchi:
1 core @ 200 MHz uses 900 mV. When we undervolt it by 50 mV, it uses only 850, which gives us 5.(5)% of battery saved on CPU duing deep sleep. Same goes for higher frequencies, but the amount decreases, down to minimum of 3,57% saved battery on CPU in comparision with no uV.

So if you say that it has no effect on battery at all, I disagree with you. CPU uses from 3.57 up to 5,5% less battery. With -100 mV you can double this values and get even 11% savings in best scenario, of course only on CPU. Screen uses much more resources than CPU istelf, so the total amount of saved battery is no more than ~1-3% with normal behaviour of using your phone during the day. This may give about 10-20 minutes SoT more.
[Galaxy S III Android Development] Jackos:
Undervolting helps with battery life, because the CPU uses less current. It's not a placebo at all.
[Galaxy S III Android Development] aliw32619:
[MENTION=5161352]JustArchi[/MENTION] i changed my mainboard after i got Sudden Death Syndrom
[Galaxy S III Android Development] ayoubij:
Im on asv 02 as well but i can under volt cpu 100mv and gpu 75mv

Have you tried it :D
[Galaxy S III Android Development] SuperAce609:
Lmaooo daaamn archiiii alright man you winnn xDDDD hahaha I'll believe you bro.

I've decided to join in the UV wagon as well. Set CPU to -100 and GPU to -100. I only see you guys tweaking the cpu. Why not gpu as well? I'm asv level 4.
[Galaxy S III Android Development] RuralGalaxy:
I got ASV 7, and always use cpu-100 and gpu-50, but some times I used more uv with both, cpu max -125 :D

PD: Not with this kernel ;)

Enviado desde mi Samsung Galaxy S3.
[Galaxy S III Android Development] BrhoomHD:
which kernal do I need to use for pac rom 4.4.2 omni or cm ?
[Galaxy S III Android Development] aliw32619:
I'm on PAC rom and I'm using the stable version 2.2 of Boeffla
[Galaxy S III Android Development] jiprudy:
Hi aliw,

Just want to ask this kernel not suitable for galaxy i9300 with sudden death chip ?
[Galaxy S III Android Development] Moster2:
You wont find a kernel that is not suitable. They are all patched.
[Galaxy S III Android Development] aliw32619:
All kernels released the SDS fix