yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] ZaneZam:
yeah that blue flash happens sometimes also to me and as far as i can remember also to andi ;)

normally it's happening

very

rar but i have that minimum once on every stock rom since ages. maybe a kind of samsung bug (like the ugly "high brigthness bug" after waking up the phone) maybe it's related to the kernel and or it's settings (early suspend delay?). but with such a low appearance count and no error log (as usual with graphic glitches *g*) andi cannot really catch that and look into that "problem".

beside of that it is completely negligible :)
[Galaxy S III Android Development] lsalamun:
Oh, so it's normal pheew, you mentioned early suspend delay, it's set to 100ms, what is it exactly doing?
[Galaxy S III Android Development] flither:
[MENTION=220904]andi[/MENTION], I know it's have been discussed already, but would you consider adding 1.8GHz overclock option in your kernel? It could be an unlockable option in settings with big red exclamation mark and 2 or 3 confirmation pop-ups or something?

The reason I'm asking is some of the phones have higher ASV levels (mine is 8), and can be heavily undervolted and overclocked to 1.8. For example my phone is undervolted to -150mV on most of freqencies, with 1.6GHz step at just 1200mV (stable as rock).

I can understand that you could be worried about people with lower ASV/IQ, and not let them fry their phones, but could you consider it? :good:

I don't want to switch to another kernel because only yours is PERFEC for me, and with extreme OC could be even PERFECT ;)
[Galaxy S III Android Development] ZaneZam:
it delays the time between pressing the power button and suspend mode (screen off), that's mostly needed for screen off animations to give them more time to show.
[Galaxy S III Android Development] lsalamun:
Who needs animations anyway:)

Thx for clearification zz.
[Galaxy S III Android Development] andip71:
Yes, it is normal.

I even had it with stock kernel some times, just very very rarely.

My suspicion is also, it has to do with the toolchain we use.

I recall it was rare when using still Google 4.4.3 toolchain and started to be more prominent with 4.7.

However, no need to worry about it.

You can search on xda for "blue flicker" and you will get tons of hits, so it is a widely known topic.

No, I will not, sorry.

The thing is: I want to stay as close to stock -> I do not want to introduce additional frequency steps.

So adding 1800 would mean I have to sacrifice one of the existing steps.

Also, I tried it and my phone never ran stable with 1800, nor the phones of some testers. I consider this as too much of risk.

When you remember, 2 years ago I said I will never provide anything higher than 1400 stock standard. Then after reading some specs I decided to support 1600 as Exynos is supposed to be able to take it.

1700 was just a try, and surprisingly it worked stable for me. So I decided to keep it as also all my testers had zero problems with it.

But 1800 is not going to come. There it will start with people (incl. me) not having stable phone anymore, and this is something which is contradicting my objectives finally.

Thanks for understanding

Andi
[Galaxy S III Android Development] flither:
thanks [MENTION=220904]andi[/MENTION] for quick response.

Well, I will have to live with it but not even thinking about changing kernel :) Keep up the great work!!!
[Galaxy S III Android Development] SteStanich:
[MENTION=947981]Lord Boeffla[/MENTION] 1st of all thanks for keeping up such a great work, I love it!

2nd.. on aosp (omni kernel) I've never faced an issue, I'm running it right now and it's just perfect but have had an issue with sammy kernel on Neat stock:

I've noticed that on sammy based rom, your kernel uses around 100 mb more than neat's stock one, bringing ram up to aroud 700 mb and giving sometimes a few lags. I've flashed both stable and betas always with same result. After wiping cache and dalvik, ram gets lower but increases quite soon after rebooting. is it part of the game or it's just my issue?

thanks again

:thumbup:
[Galaxy S III Android Development] 0sAND1s:
It's OK now

Thanks keneth_c. I flashed the kernel using the latest Boeffla Config v2 and now it seems stable. Until now, I used Mobile Odin, and I didn't have issues. What can cause the diffrence?

Also, Antutu benchmark score is the best until now, over 20.000. I attach a snapshot.

Thanks!
[Galaxy S III Android Development] andip71:
Mh, I do not know Neatrom kernel, so hard for me to seriously comment.

My kernel is close to stock = it uses the LMK settings of the stock kernel. However, you can try to play around in Boeffla-Config App with it. For instance I personally always increase all LMK values by +10 MB. This is for me perfect.

Apart from that, as said, I do not know what Neatrom kernel is different from stock really.

Andi
[Galaxy S III Android Development] andip71:
Good good.

I would not be mad if you changed the kernel, honestly.

I am very well aware, my personal objectives for my kernel are not in line with views, opinions and requirements of other users.

That is normal, that's what we call life :)

Cheers

Andi
[Galaxy S III Android Development] SteStanich:
thanks mate, I'll give a try with what you suggested, will report back asap.
[Galaxy S III Android Development] flither:
haha, tried couple of most popular and came back to yours, so I'm staying in Boeffla castle.

BTW i didn't know that adding this extra freqs will sacrifice some of lower ones, learning all life :)
[Galaxy S III Android Development] andip71:
No no... it IS possible to implement additional frequency steps, then you do not have to sacrifice other frequencies.

But I am not a friend of this, due to my close-to-stock thinking, so I do not want to do that.

Andi
[Galaxy S III Android Development] keneth_c:
:D

Glad to know it worked out for you...

Not sure what causes the difference...

but thats a little trick I learnt from [MENTION=947981]Lord Boeffla[/MENTION]

When in doubt.... use Boeffla app to flash the kernel :)
[Galaxy S III Android Development] andip71:
Never say never :)

Thanks to a hint by psndna88, there is one more beta for the Android 4.4.x kernel only:

Version 6.0-beta4

23.06.2014

zRam and swap working now again (thanks to psndna88)

Enjoy

Andi
[Galaxy S III Android Development] lopiop:
[MENTION=947981]Lord Boeffla[/MENTION] graphical glitches fixed?

---------- Post added at 05:32 PM ---------- Previous post was at 05:26 PM ----------

also how do you guys get 20 k plus on antutu, i only get 17k on antutu
[Galaxy S III Android Development] andip71:
Lol... Is anything mentioned on graphics in the change log? ☺

And no, I still have not seen tge "graphical glitches". Maybe because I am not gaming. Nothing I can replicate, nothing I will change.

Andi

Sent from mobile
[Galaxy S III Android Development] AssassinGEO:
Go ahead and uninstall any benchmark app. Numbers won't give you anything.
[Galaxy S III Android Development] Ubimo:
Go ahead and uninstall your tachometer. Mp/h or Km/h won't give you anything.
[Galaxy S III Android Development] Blackstard:
ur position is so wrong...

S3 ➰
[Galaxy S III Android Development] xKyrex:
22081 on NeatRom 7.6 + Boeffla 5.2

Thank you for this awesome kernel.
[Galaxy S III Android Development] andip71:
Good morning,

new Boeffla-Config app version 2.1.43 available (you will get a notification when you open your app).

I would strongly recommend to update as it removes the false alarms of a few virus scanners (that did not like Stericson's Roottools framework 2.6) finally.

Change log

Added Polish translation (credits to Tocco)

Replaced Stericson roottools by own lightweight root implementation (50kb size reduction, no false virus scanner alarms anymore)

Andi
[Galaxy S III Android Development] Choristav:
More like e-penis-o-meter.

6.0 beta 4 is a blight!
[Galaxy S III Android Development] keneth_c:
No notification on opening the app (v2.1.39)... I guess I will need to do it manually.

Hmmm....

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.4 (official nightly) powered by Boeffla kernel via Tapatalk
[Galaxy S III Android Development] andip71:
On which app version are you now? You need at least to be on 2.1.40 to receive the update notification.

Andi
[Galaxy S III Android Development] keneth_c:
Ok makes sense. I'm on v2.1.39.

Realized I didn't mention the version and edited my previous comment... But you were very prompt with ur reply :D

--

Sent from my Samsung S3 (GT-i9300) on OmniROM 4.4.4 (official nightly) powered by Boeffla kernel via Tapatalk
[Galaxy S III Android Development] SaschaKH:
A lot ppl have OCed so I can undestand that. Well I have not OCed and get around 19k.

BTW benchmarks don't really say much, I start the same benchmark two times and sometimes have differences of more than 300 points. I more or less use the benchmark only to see if it runs without fc or reboot. OK with Boeffla kernels you don't have that problem at all.
[Galaxy S III Android Development] eatsleep:
Its not the games who get the glitches but the launcher sometimes (while transition effect, you'll see shuttering).

In chrome, try to swipe away the the tab in the front slowly. You'll see gains and other stuff.

One a piece of my notification Centre broke (the one you swipe down from the top) :D and stayed broken for some days ( a small pice near carier label. I could see things behind it :) )

Viewing a video on Facebook is shuttery slmost everytime

These are purely random..... sometimes I get them, the next time I don't!
[Galaxy S III Android Development] xKyrex:
Lord Boeffla, are you able to tell why the Equalizer doesnt work on NeatRom?

Thanks
[Galaxy S III Android Development] andip71:
Well, does it not work?

I never used Neatrom as I never use a Sammy based custom rom.

So I can only suspect... maybe another app conflicting? Something like DSP Manager etc?

But hard to say from remote.

Andi
[Galaxy S III Android Development] xKyrex:
The sound effects tab on settings > sound doesn't exist. Can it be that?

And I dont have any other app that changes the sound.
[Galaxy S III Android Development] andip71:
We are getting closer - where exactly do you expect the equalizer to show up?

If you are talking about Boeffla-Sound Equalizer, you need to use the Boeffla-Config V2 app from my homepage.

Is this where you are looking for it?

Andi
[Galaxy S III Android Development] xKyrex:
Yes, I'm talking about Boeffla-Sound equalizer. I have the app, I updated it a while ago when I saw you saying that there was a new version.
[Galaxy S III Android Development] andip71:
Can you please send a screenshot? I have doubts.

Thanks

Andi
[Galaxy S III Android Development] xKyrex:
There you go
[Galaxy S III Android Development] andip71:
Ok, all good.

You have selected a Equalizer Profile (Archis audiophile), which has predefined values and locks the equalizer band sliders to be modified.

Set it back to "none" and you will be able to move the sliders again.

Andi
[Galaxy S III Android Development] xKyrex:
Still wont work. Even if change them, or change the preset to any other with predefined values, the sound wont change
[Galaxy S III Android Development] andip71:
Well, then I have to give up from my side. Then something is blocking something.

I never used Neatrom, as I said. On stock it works fine. But I also know of many other Netrom users that do not have any issues.

So... maybe they can comment here.

Andi
[Galaxy S III Android Development] xKyrex:
Well, thanks anyway.

I wanted to use it because it worked on an KK Archi port ROM and I really liked it.
[Galaxy S III Android Development] 99x:
When set to none, do the equalizer adjustment bars go bright blue or stay 'greyed' out?

They should go bright blue, meaning you can adjust them.

Edit: You could also try cleaning kernel settings and reflashing the kernel
[Galaxy S III Android Development] xKyrex:
They go bright blue and I can adjust them.

Where do I clean kernel settings? Because I already tried reflashing.
[Galaxy S III Android Development] andip71:
Either in the boeffla config app, settings, reset settings...

or you flash the reset zip file you find in /boeffla-kernel-data in recovery...

or you delete folder /data/.boeffla completely and reboot

Andi
[Galaxy S III Android Development] xKyrex:
Still nothing, I guess it's a Rom problem. I've tried changing MusicFX.apk to see if the tab on settings > sound apear but with no results.

Thanks for the help anyway.
[Galaxy S III Android Development] MIKEMON:
I did this, the problem on custom rom

are added audio mods or scripts

You need to check the system rom and should be removed or remain at the core rom
[Galaxy S III Android Development] glockaki:
uninstall music fx.its useless.i do it everytime i flash a rom.and i use dsp manager on a sammy based rom with no conflicts with boeflla sound.

Στάλθηκε από το GT-I9300 μου χρησιμοποιώντας Tapatalk
[Galaxy S III Android Development] lsalamun:
so [MENTION=1141513]archi[/MENTION] to conclude, pegasusq is better in terms of battery?
[Galaxy S III Android Development] JustArchi:
To conclude we're talking about micro constant battery drains here, nothing you should worry about unless you're a trying-to-be-professional developer like me, analyzing everything what I'm using.
[Galaxy S III Android Development] 4hunter:
Omg how to change language back to English, I prefer it in that lang, in polish all options sounds stupid...

Wysłane z mojego GT-I9300 przy użyciu Tapatalka
[Galaxy S III Android Development] ZaneZam:
Maybe with the app setting "force English language" :)

Gesendet von meinem GT-N5110 mit Tapatalk
[Galaxy S III Android Development] lsalamun:
Ok, i'm just informing myself:)
[Galaxy S III Android Development] JustArchi:
If you want that stats for geeks then yes, ZZmoove has higher "frequency", sampling rate. It samples more often, and that's why it's snappy - because it has more samples to base from. On the other hand, pegasusq has less samples, so it makes it's decision based on that.

Sampling is important because the more samples you're collecting. the higher potential battery drain will be. This hits mostly deep sleep and "constant" battery drain, as when it comes to higher CPU frequencies or gaming, it doesn't even matter.

Ideal governor with no sampling at all is powersave, userspace and performance. These three work on static fixed frequency. Hence, if governor could limit it's sampling while in deep sleep to a bare minimum (let's say once per 0.1 second), it would drastically improve battery life in deep sleep. However, I'm not sure if that's even possible, probably I'd need to have fun with my own governor (ArchiQ, anyone?), and I have already too many projects started :D.
[Galaxy S III Android Development] viktor92:
Maybe what I will say it's a nonsense, but isn't possible to change the governor's behavior to that of powersave when the CPU is in deep sleep state, and return to high sampling when exits from it ?
[Galaxy S III Android Development] andip71:
Exactly. You can force English language in the app settings.

Andi

Sent from mobile
[Galaxy S III Android Development] putti71:
With which app do you listen to music? Because I had the same issue when using poweramp. But there you have to go to settings-audio-....-direct volume control and untick it.
[Galaxy S III Android Development] xKyrex:
I use stock app from Samsung
[Galaxy S III Android Development] ZaneZam:
sampling rate is adjustable and not fixed as u know archi *gg*, and it's even semi-dynamic when setting sampling rate idle for awake :) beside of so many other things especially for suspend. sometimes i think even too much as people getting confused - me inclusive if i do not play with the settings for some time and forget how they work exactly, but my docu helps fortunately - think i'm getting old *ggg*). as mentioned we could play around with sampling rate sleep multiplier (maximum value is x4 atm.) which for example increases sampling rate (again the sampling rate is just a delay time between 2 cycles and not the cycle rate itself) by the given factor but as said too much of restriction at suspend leads most likely to sod's. i think at suspend we are already on the highest (stable) level and we could really run in problems by making more "strictly" settings, but as also said we could try it and actually i allready made some preparations for that because i didn't lost my curiosity yet *g*

beside of all that i think zzmoove does a very good jop in terms of battery saving at suspend (yes even with the sound issues which are not coming alone from the governor as often stated these days!!), what i would like to see is a bit more saving (without loosing speed) when using the phone, actually :)

and just one last word about the sampling rate as you are so much focussed archi *g*: it's important yes but by far not the only reason why zzmoove (or any other governor) behaves as it behaves. :)

no not really nonsense and something i had already in mind when starting making zzmoove i wanted max bat saving when not using the phone and therefore it kind of has this functionality already by "soft locking" the freq at suspend, adjustable with "freq_limit_sleep" ;)

i think we should stop here now (sry andi, again *g*) but we can discuss this further and share our ideas in the ZZMoove thread :good:
[Galaxy S III Android Development] lsalamun:
Thanks for your precise clearification [MENTION=5161352]JustArchi[/MENTION] !
[Galaxy S III Android Development] Lightysnake:
Hi,

i've installed beta 2 and beta 3 on my s3 with bulldog74ts's Galaxy S5 Mini and i have wifi problem.

at every reboot i need to apply a fix for wifi (the fix is set the correct cid)

At first i was thinking that was a bug releated to the rom but with the original kernel i haven't issues.

Any ideas? I love this kernel is smooth and with great battery life
[Galaxy S III Android Development] SaschaKH:
If you have problems you could install 5.2 stable or maybe the latest beta (5.3beta 6), if your on 4.3. If you use the ArchiPort there is a 6.0beta4.

Gesendet von meinem TPC-9000 mit Tapatalk
[Galaxy S III Android Development] hwjrmrm:
Dear Boeffla,could you tell me which is the best stock Sammy 4.3 now or which 4.3 are you using?thanks
[Galaxy S III Android Development] SaschaKH:
I would guess his own Frankenstein version of the official Samsung ROM: http://boeffla.df-kunde.de/firmware/

Gesendet von meinem TPC-9000 mit Tapatalk
[Galaxy S III Android Development] Lightysnake:
I'm on Galaxy S5 Mini 4.4.2 i will try 6.0 beta 4 hope it fix the problem :)
[Galaxy S III Android Development] andip71:
As Sascha said already, I am personally using Samsung stock odex firmware which I debloat after installation.

If it is the best? Maybe not for everyone, but for me it is my preference.

Andi
[Galaxy S III Android Development] Hidden-Hunter:
Hi Andi

Thnaks for kernel but i sold my device and now i have a note 3 device-

I miss you very much :D:good::highfive::victory:
[Galaxy S III Android Development] andip71:
All,

I will be travelling to my home city tomorrow and will return back home Monday night.

So I will not be much active here for the next 4 days.

Have fun anyways

Andi
[Galaxy S III Android Development] MIKEMON:
Andi, enjoy

everything is fine and your support is always at hand

thanks for all
[Galaxy S III Android Development] eatsleep:
deleted
[Galaxy S III Android Development] painball:
Hello everyone.

I haven't found any related topic so I will post here since it it evolved from previous one (older subject - 4.1 kernel)

I've got an issue. Mistakely I didn't made a backup of Boeffla Config V1 app. I'm using 4.1.2 firmware on my S3 LTE (i9305) and ported kernel works only with old Boeffla Config and only available one at boeffla home site is Boeffla Config v2. After flashing kernel, installed kernel app says that it's outdated and need an update. But nowhere to be found since it's gone from Google Play and home site. Anybody got it in own resources? Last BC v1 app was working fine. I updated it from google play ages ago but lost this backup.

Regards
[Galaxy S III Android Development] andip71:
Go on http://boeffla.df-kunde.de/bc/.

And there move into the version1-obsolete directory, here you will find the latest version 1 Boeffla-Config app.

Andi
[Galaxy S III Android Development] painball:
Fehler 403 :)
[Galaxy S III Android Development] andip71:
Try again :)
[Galaxy S III Android Development] MIKEMON:
functional link

but why do not you release V2, which has more options
[Galaxy S III Android Development] MIKEMON:
super result

after debloadet your rom using zzmoove Governor

I have 12 hours in standby mode, only 1% per hour of battery

great, I'm very happy.
[Galaxy S III Android Development] malachow:
Attention please! :cool:

I'd like to show you guys what the power of Boeffla with ArchiDroid literally means.

Are you ready? Get to spoiler! :D

Yep, 25% battery equals 2:22 SOT with WiFi&sync on all of the time. And yes, stock battery.

What's the secret? I always remember temasek's words long long time ago:

Make your phone behave.

Simple. :)

Cheers to all!
[Galaxy S III Android Development] xKarlo:
Is that archidroid 2.x? Are you using 5.3 beta 6? Damnnn I can only get 5 hrs screen on time from 100% to 0% with archidroid. Im using ArchiDroid 1.7.16

How old is your battery? Mine is 1 and 1/2 y/o

---------- Post added at 05:23 AM ---------- Previous post was at 05:20 AM ----------

Is that archidroid 2.x? Are you using 5.3 beta 6? Damnnn I can only get 5 hrs screen on time from 100% to 0% with archidroid. Im using ArchiDroid 1.7.16

How old is your battery? Mine is 1 and 1/2 y/o
[Galaxy S III Android Development] malachow:
1.7.16.

Yeah, there is also second secret - after 1.5 year of using phone I replaced battery with new one about month ago. I'd recommand this to all of you, phone behaves as if he ressurected. :)
[Galaxy S III Android Development] Android -_- hacking:
Hm... Awesome results ... so what's your config like ? just purely stock config?

Id love to get those results im a power user and i browse the net with my s3 a lot.. but 5 hours + of sot for me is just not possible.... No way ...

Would be glad if you shared your config...
[Galaxy S III Android Development] malachow:
The best one. :cool:
[Galaxy S III Android Development] Android -_- hacking:
Thank you kind sir.. ;) i hope ill get those results too!
[Galaxy S III Android Development] AssassinGEO:
Guys,I couldn't find it anywhere. Anyone can explain me how the size of zRam works?

Faq didn't help either. I just turned zRam on back again but set it to 800 mb and situation didn't change,still 2 apps max running if I start multitasking hard. I remember it was fine with 300 mb thought he phone lagged quite badly. Less mb - more apps?
[Galaxy S III Android Development] lsalamun:
[MENTION=5264108]malachow[/MENTION] , slight OT, but, do you get any overheating with latest 1.7.16 archi and 5.3 beta 6 boeffla kernel?

I got mine upto 56C when playing heavy games and 48-50C while just social networking.

This never happened on any other ROMs, they were around 48 on heavy load and 38-42C web browsing, social etc.

I don't use OC/UV, just classy zzmoove moderate.

I think it's something in the latest AD, with 1.7.15 everything is fine. I did full wipe also, i was using 5.3 beta 6 with stock ND5 and no overheating, and, Im not the only one who complains, maybe [MENTION=5161352]JustArchi[/MENTION] has the right answer.
[Galaxy S III Android Development] malachow:
No heating. At all. :good:
[Galaxy S III Android Development] lsalamun:
Awkward, could you tell me your temps please?

For me, Idle is ok ~40C, but loaded phase is worying me a bit...
[Galaxy S III Android Development] tmac31:
yes you are right my phone is heating with archi 1.7.16 and boeffla beta 6 too. using s3 for 2 years and its 1st time i see thermal throttling on s3 with only browsing over 3g. cpu was stuck on 800 mhz and phone kept laging.
[Galaxy S III Android Development] lsalamun:
I don't get any lags, but temperature is worrying me, Idle is ok, it can drop to 35C even, but 55-58C gaming and 52C browsing, awkward, and i don't use OC.