yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] andip71:
And just before someone asks, no - will not add any more tunables to pegasusq.

This is against my "close-to-stock" objective.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] ahac85:
Hi andi please can you check your PM Inbox

Sent from my GT-I9300
[Galaxy S III Android Development] Assa551N:
Boeffla Config Help doesn't describe...
[Galaxy S III Android Development] cerealguy:
http://www.boeffla-kernel.de/index.php/kernel-settings go here , in Tab Cpu...

Inviato dal mio GT-I9300 usando Tapatalk 4
[Galaxy S III Android Development] andip71:
Not true.

It does. See screenshot.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] SuperAce609:
Guys I'm having a problem. My screen sometimes flickers while typing or just when touching it in general. It flickered when I pulled down the status bar and mostly when I type. Sometimes when I turn it on, it shows a blue screen flash then goes to the lock screen.

Does anyone know about this?
[Galaxy S III Android Development] andip71:
The blue flash I have from time to time. Side effect of the 4.7 toolchain (suspected).

But do not have flicker...

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] ahac85:
Hi anybody with knowledge of understanding logcats explain why my device reboots when boeffla 3.1 stable installed, I had logcat recording enabled so the answer is right at the end of the log just before the device rebooted but I dnt understand it.

https://db.tt/NUws7eGm

Sent from my GT-I9300
[Galaxy S III Android Development] SuperAce609:
Do you think it could be an issue with the digitizer? I've never had it before. It's started to happen recently.

Can you tell me more about the toolchain and the flash?
[Galaxy S III Android Development] andip71:
I have that rarely since using 4.7 toolchain.

I cannot tell you more, it is just my observation. And it does not really worry me... It is rare and cosmetic as I have it maybe once a week only.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] SuperAce609:
You have what rarely? The glitch or the blue screen?

So from what you're telling me the blue screen is normal. Okay, that's settled. But what about the random screen flickers?
[Galaxy S III Android Development] tommi.a:
Just an idea: some kind of screen flickering could be caused by (accidentally) configured lcdfreq_enable=1.
[Galaxy S III Android Development] ARCANAAA:
Would also like to hear some opinions on this.. im using it atm and it does feel more responsive eventhough i can be placebo :P

Verstuurd vanaf mijn GT-I9300 met Tapatalk 4
[Galaxy S III Android Development] SuperAce609:
Does that have something to do with touch boost? I checked the build.prop for that line and I can't seem to find it.
[Galaxy S III Android Development] tommi.a:
I meant the (e.g. zzmoove) governor setting.
[Galaxy S III Android Development] SuperAce609:
I'm using zzmove optimal. So switching governors will take the glitching away? I was about to literally take my phone to the repair center asking for a new screen digitizer tomorrow.
[Galaxy S III Android Development] moffa89:
I hate zzmoove only performance is good but lags while playing games and hearing music through power amp since 2 days i use bfq+lulzactiveq and i am happy battery life is good too.
[Galaxy S III Android Development] SuperAce609:
Well, I can't argue because I used to have the same problem before. But even if I switched to Pegasus q it still happened. So to me it was a kernel problem. Now it doesn't happen anymore.

But alright, I'll try switching governors to see if that does it. I love zzmove though :'(
[Galaxy S III Android Development] ZaneZam:
tommi meant the setting lcdfreq_enable=1 if that is the case then the dynamic freq scaling is active which could give u some kind of flickering if lcd freq is switching between 40 and 60 hz mode. but this feature is disabled by default on all profiles so it must be accidentally be activated by something other then the config app. check the tuneable and set it to 0 if it is set to 1 and/or yes simply change the governor becase the dynamic freq scaling is definitely off then ;) btw. i can confirm the blue screen flash from time to time and yes as my lord already stated it seems that this started with using the 4.7 toolchain. but it's no biggie

oh what a hard opinion, sad to hear that! :(

there might be some adjustments to fix that lags at least for the power amp problem, but anyway u already made your decision and thats good 4 u ;)
[Galaxy S III Android Development] SuperAce609:
I really like how you and Andi answer questions. Thank you for your saying on the blue flash. I feel better about it now and not freaked out. Is the toolchain something added by boeffla kernel?

I've checked the boeffla app and for Tuneables, I need the pro version. Does that mean it's off by default? I don't use any other apps to mess with the phone performance. Everything I need is in Boeffla Config. I'll try changing governors to see if the glitching/flickering still happens.
[Galaxy S III Android Development] ZaneZam:
fine glad u did not freak out :) ehm the toolchain is the compiler which makes the kernel image and there are different toolchain versions around,

some time ago my lord (yeah again andi *gg*) decided to use the android stock 4.7 version to compile his kernel because it brings some more performance and also some "code fixes" to the kernel image. since then the blue flash appears some times (really rarely) so the suspect is that toolchain. ;)

and yes u need the pro version for the "tuneable" mode, but u could also use "setcpu" or "android tuner" app to check this, but if u did not use such tools before i doubt that there is lcd_freq active because yes as i said it is off by default in all settings. my thought was that an app accidentally switched that on by saving some test values u maybe had set before :) anyway i hope 4 u it's not a hardware issue! good luck!
[Galaxy S III Android Development] SuperAce609:
I switched back to zzmove optimal and installed set cpu. Here are all the lcd lines. I think it's already set to 0. Am I right?
[Galaxy S III Android Development] ZaneZam:
yes as lcdfreq_enable is set to 0 it's off. btw i think my concentration is getting weak the tuneable is of course

called "lcdfreq_enable"! time to sign off for today :)
[Galaxy S III Android Development] Hbohd:
Just to answer you quickly: yes, you are right, it's disabled :)

For less flickering you should check if your Power Saving mode is turned off. Moreover you might increase your touchboost value (800-1000 may be well performing), set 266/350 as gpu frequencies (it gave me nice smoothness) and set Row as internal I/O scheduler.

However, bear in mind that it might be an app that flickers when you scroll or go through various screens ;)

Zzmoove optimal is really enough for every smooth move :D

*edit*

Hehe, ZZ about half a minute faster ! That's a real helping hand !
[Galaxy S III Android Development] SuperAce609:
Oh no, it's definitely not a performance issue. I have touch boost set to 1600Mhz and no power saving ever on. As for GPU, I have the preset of 266-533. But I'll change the 266 to higher.

I've thought about the possibility of it being an app that makes the screen flicker. But when in the home screen and just simply touching the screen to bring down the status bar, just makes me doubt it. It happens a lot when I'm typing with WhatsApp and sometimes on the XDA app as well. I was thinking it had something to do with the Google Keyboard but the status bar thing made me think otherwise.

I'll try out a different governor and the higher GPU min freq. to see what happens. Thank you all very much for your support. I've had this for a while now and I didn't know what to do.

Edit: All set with new settings. Just changed GPU to 350/350/440/533 and governor to lulzactiveq.
[Galaxy S III Android Development] MinL:
Great Kernel Thanks :good::good:
[Galaxy S III Android Development] puhu:
+1

I have this problem too. I can recording without headphones but when i plug headphones not using microphone and cannot recording with headphones. Im using Omega UBEHM5 JKAY Mod (ported by ZaneZam version) and Boeffla Kernel 3.2beta2

puHu

---------- Post added at 01:37 PM ---------- Previous post was at 01:17 PM ----------

And another problem is as k4bbe said. When i plugged the headphones it makes ringer Off automatically wolumedown ı try many times wolume up and headphones making wolume down again :/

puHu
[Galaxy S III Android Development] moffa89:
The hardest lags are in games and with poweramp its not often and i test a little bit more but i think its when only one core is active i read that 1x 800mhz needs more power than 2x 400 mhz so lulzactiveq is good for me :p
[Galaxy S III Android Development] andip71:
I mean the blue screen, I have rarely.

But I have no glitches.

It could be, yes. But has been ruled out now.

No, not likely. If it started just out of the blue, it is really strange.

But touch boost is not in build.prop, it is a setting in the kernel.

Well, I never tried recording via headphones connected. So, it was never in scope for Boeffla-Sound. Never had the idea to even try that. So, please do not expect a solution for it short-term, I always record via built-in mic and this is just fine.

For the headphones thing plugged in:

If you have privacy mode switched on, please switch it off.

The sound engine does not touch volume levels based on if you plug in a headphone or not. This might be an app (boeffla sound app for instance, or any other that detect headphone activity) or something else. Surely not the kernel, there is not a single line code in to change the rom values (it is even impossible).

Andi
[Galaxy S III Android Development] danierakes:
someone pls share ur own best setting in performance and battery save too...sharing is caring...I would love to try

galaxy s3

galaxy mega 6.3

galaxy grand duos
[Galaxy S III Android Development] MIKEMON:
For me, the best gov.Zzmoove / optimal and perf / absolutely reliable

Batteries and Power super, no uv

Scheduler int.row and ext.zen

zram 4, set to 800 megabytes, swapines 80

CPU tweaks / AFTR § LPA / multicore powersave enabled

system all smooth and stable
[Galaxy S III Android Development] yosef019:
boeffla if i have ext2intrnal mod shelduer is how play here?

int is int ext is ext / or / int is ext ext is int

row shelduer make lil buggy my microsd card thats maits storage
[Galaxy S III Android Development] andip71:
Only the mount points are changed by this mode.

The schedulers are still the same for the two storage types.

So I would still suggest you use ROW for internal storage and cfq or bfq (or zen?) for external.

I am currently using zen for both, but I do not use this mod myself.

Andi
[Galaxy S III Android Development] MIKEMON:
@ Lord Boeffla

Yes, but there is a big difference between planners / CFQ, BFQ and Zen /

row is great for internal
[Galaxy S III Android Development] janres155:
Thread seems to be too quiet today. :)
[Galaxy S III Android Development] andip71:
Yeah, sorry... today and tomorrow you would need to do the show :)

Reason: I am / was working on a complete overhaul of both kernel and Config App for the future.

In future, all root issues will be gone as the whole concept will be different.

Too early for the 3.2 series, but could come with 3.3 series - together with a separate V2 app.

And this massive coding kept me completely busy today on top of my professional work.

:)

Andi
[Galaxy S III Android Development] tommi.a:
I regard your work on the kernels and app professional as well!
[Galaxy S III Android Development] FlemishDroid:
I use an app called Galaxy Charging Current Pro and when my phone is on charger it looks like:

Maximum: 1000

Current: 1098 (or 1198 if I set 1200 in Boeffla-config)

Avg: 1000

So Current is higher then Maximum.

But when I try Adam kernel with this app it looks like:

Maximum: 1100

Current: 1098 (or whatever I set in STweaks)

Avg: 1100

With Adam kernel and stweaks you can change "DCP and mains ac input current" also... does it matter or is it only an option so that maximum looks the same as current value?

Verstuurd van mijn GT-I9300
[Galaxy S III Android Development] andip71:
Hi Flemish,

all I can say is: Whatever these apps show, it is "something", but only some interpolated rubbish.

Reason is: The S3 has no circuit/device that can in fact measure the charging current.

All these apps do is checking for the battery voltage and the tendency, and trying to interpolate something. Maybe some apps try to read some settings from some kernel interfaces, to display (or pretend to display) something more useful.

The only real test is: Is charging quicker with 1300 on a good charger than with 1000 or not :)

Sorry for the honest answer

Andi
[Galaxy S III Android Development] FlemishDroid:
Last night I plug in my phone and 5 hours later I unplug my phone from charger and it was 76 % normally it's always 100 % after a night so I tried this app and it was showing max 200 and current 198 so the app was correct this time. :p That's the only time I use this app when I think something is wrong with the charger... Thx for the info.

Verstuurd van mijn GT-I9300
[Galaxy S III Android Development] andip71:
Then try to enable "ignore instable power"... it might help.

(on your own risk)

Andi
[Galaxy S III Android Development] MIKEMON:
If you fix, the problem with unroot

phone after, flash is not binary SU / SU PRO, § triangle away /

It will be the absolute best message
[Galaxy S III Android Development] 7wajahat7:
Well, I had the same issues with the original samsung charger, because the original samsung charger that comes with S3 is CR*P! I replaced it with a 2A travel adapter charger and things worked out. But you may try what Andi says, Enable "Ignore unstable power" But i wont be responsible if it burns your house down. Do it at your own risk.
[Galaxy S III Android Development] TSO of Stormwind:
As i said in my first post, i just wanted to hear your opinion or some others experts opinion. I did not make any kind of request nor i will (even if i used the verb "want" i was being rethoric). this kernel is your creature, you decide how it will grow. (Obviusly duh)

Keep up the great work!
[Galaxy S III Android Development] blue_moon:
Even though zram is enabled i cant change zram devices number and disc size?
[Galaxy S III Android Development] mildavidec:
ZRAM should be disabled to change device numbers and disc size. Than you can enable again
[Galaxy S III Android Development] yosef019:
camera some time freeze if i use row for ext sd so i try zen
[Galaxy S III Android Development] rulala:
hi , Andip

I am sorry to ask you not about boeffla kernel question.

Because I am Curious What exynos note 3 use which audio chip.

Can we check ourself by looking /sys/class/sound/card0/device ?

for our s3-i9300, i see WM8994 A1F1 folder.

But S3 use WM1811 audio chip .

I also see Midas_WM1811 BT and Midas_WM1811 Voice folder.

So. do you know the way how to make sure which audio chip?

someone say ：

seems no wolfson in exynos n900...

it seems to use the yamaha ymu831

http://xdaforums.com/showpost.php?p=46039293&postcount=42

how do you think? Big thanks.:o
[Galaxy S III Android Development] Ha_Ha Shoes:
Using the most recent stable version of Boeffla I get network problems. I have tried three different kernels and it is definitely Boeffla causing the problems. I flashed the most recent beta and network is fine. I am using Omega v49.
[Galaxy S III Android Development] andip71:
Mhhhh, it is surprising to me.

Because Samsung signed a contract with Wolfson a while ago, forcing them to put WM audio hubs in. Maybe the Note3 design was already done before that. But looks like Yamaha, yes.

Good I find the Note3 anyways too big for me, so never planned to go for it.

So, you have network problems with latest beta or not?

Also, which network - mobile data or wifi?

If it is wifi, then yes... can be, based on what your network configuration / router is.

I put some patches in to reduce the wifi wake locks, but for a very small number of people this causes wifi problems in rare cases.

It is a fact, I can only choice how many people I try to make happy, and the ones benefiting from the wake lock reductions are more.

Yes, this will be history then. The app will not need any root rights anymore during startup.

Just when you use the app itself to configure, root rights are still used, but this is standard.

Yeah, and it is running already quite nicely on my side. Will work on fine tuning now.

Andi
[Galaxy S III Android Development] andip71:
App

Quick one, I just pushed a new app to Playstore and AndroiPIT.

V1.4.5

* More relaxed timing during app start

* MDNIE internal handling improved

* Internal json enhancements

* New option in settings to define reboot mode when flashing recovery

Cheers

Andi
[Galaxy S III Android Development] pistoke:
This is a quite small issue, but could you Andi change uptime so it shows hundreds of hours not only tens? I have uptime 116h and app shows 16h.
[Galaxy S III Android Development] andip71:
Oh dear... what an uptime :)

Can you pls do me a favour and post me the output of file

/proc/uptime

here? So I can use it for a test?

Many thanks

Andi
[Galaxy S III Android Development] andip71:
3.2-beta3

Hi guys,

next beta, I plan this to be the last beta before 3.2 stable:

3.2-beta3

Change log (vs. last 3.1 stable)

Yank zzmoove battery profiles updated with latest changes from Yank kernel 4.6f

Loggers (both kernel and Android) are enabled by default, switch them off in Boeffla-Config again if you wish

Insecure kernel (adb has root rights), this enables commands like "adb remount" etc.

Added Zen scheduler

Added system fs to display asv level in Boeffla-Config app

Upstream to 3.0.98 Linux kernel from 01.10.13

"Turbo zRam": zRam is now spread across 4 devices per standard

exFat completely moved to opensource exFat (Samsung OSRC)

Fixed a bug with the ignore instable charge power switch not being sticky

Configuration file way of configuring the kernel finally completely removed, you have to use Boeffla-Config app now

Archiving of kernels when using load&flash fixed

Internal cleanup

Happy testing

Andi
[Galaxy S III Android Development] Gorgtech:
Awesome as usual :D:good:
[Galaxy S III Android Development] Achraf AOUAD:
My lord one quick note im on latest app version 1.4.5 and beta 3

you said that the loggers are enabled but i checked and they aren't ! Is it just me ?

Plus what does the ext4 tweaks do ? For a normal us3r not a gamer

Thanks for the amazing kernel !!

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Android Development] andip71:
Hi, well... the loggers are on when you have a fresh setup. As you used the app already and saved your profile with the loggers off, they - of course - stay off.

Just if you would freshly install kernel and app, you would see they are then on (former they were off as standard).

And ext4... may I please request you to look it up in the documentation.

- kernel homepage, or

- help menu in Boeffla-Config app, or

- link in the OP of this thread

Everything is explained in details there.

Thanks

Andi
[Galaxy S III Android Development] ahac85:
will leaving the loggers ON result in any additonal battery loss??
[Galaxy S III Android Development] andip71:
Well, not very significantly at least. Maybe a little.

And this was the reason why since version 1 of Boeffla-Kernel, loggers were switched off by default.

But it also causes issues, in CM mainly, but also with a few apps around

So I decided to keep then on = standard. And everyone can still switch it off again in the Config App.

Andi
[Galaxy S III Android Development] danierakes:
My Lord Is it good to switch on loggers for stock rom?what is ur opinion..

galaxy s3

galaxy mega 6.3

galaxy grand duos
[Galaxy S III Android Development] andip71:
I have them switched off on Sammy stock roms, unless I find something is misbehaving - then I switch them on to be able to analyse the log files.

Andi
[Galaxy S III Android Development] Ha_Ha Shoes:
The problem is with my phone network. If I use the most recent stable release of Boeffla my phone comes up with network errors. It says EE network cannot connect. Emergency calls only. If I use Boeffla beta no problems.
[Galaxy S III Android Development] andip71:
Okay. Latest betas have a newer initramfs. This could explain it probably.

But if you are on one of the latest betas, it is anyways appreciated a lot by me :)

Andi
[Galaxy S III Android Development] Stevemann:
3.2 b3

Just tried the new 3.2 b3 - and for me it's way smoother and less laggy than v3.1 (using the same settings - except for the zRam devices now set at 2 from a stuck 1).

Great kernel Andi!
[Galaxy S III Android Development] andip71:
Yes, this is the purpose of ongoing development. I also think 3.2 b3 has the potential to become stable.

It HAS to. I have 4.0-alpha1 already prepared and want to get it out at least to some pre-testers.

Cheers

Andi
[Galaxy S III Android Development] SuperAce609:
http://xdaforums.com/showthread.php?p=34879375

I read that because i was curious about how zram worked. But i still don't understand. If there's only 1gb ram, how can we add 600MB out of literally nowhere? I know it's allocated in the normal ram but how? How does the compression make it practically disappear resulting in more space? Does it compress them to 1MB or what?

Sorry for all the questions but I'm a guy that likes to think outside of the box. Instead of ticking a box in settings, i like knowing how it does it and how everything happens.

Can anyone help with this please?

Btw: the yank battery profile is badass.
[Galaxy S III Android Development] Gorgtech:
zRAM is similar to a compression utility; the data in your RAM is compressed and needs less space which makes you feel like you have more physical RAM available ;) You can hold more apps in your RAM while they´re compressed. The only downside, you´ll have a greater battery consumption since the CPU needs some extra power to pack und unpack the data. You may also experience some lags.

I don´t use zRAM since I have lots of free RAM available :good:
[Galaxy S III Android Development] SuperAce609:
The battery consumption and the lag haven't been present ever since i started using it. All pros and no cons for me.

But how is it that we set the zram size? Is the size what determines the max total size of compressed apps? How much do they get compressed? I've seen kernels with up to 1200MB zram though. Wouldn't something that high also fill up the normal ram as well?
[Galaxy S III Android Development] andip71:
Average compression rate is around 30-35% average based on my experience.

So even if you create a 1200 MB zRam device, it would only consume around 400 MB real memory.

Andi
[Galaxy S III Android Development] andip71:
-- deleted --

(what is wrong today? this is already my 2nd double post today)
[Galaxy S III Android Development] MIKEMON:
3.2beta3

excellent work, I hope the problem will disappear with unroot

Applications also a big thanks to my friend:): Prsty kříženy:
[Galaxy S III Android Development] pistoke:
It's a plain file just added doc to name so I it's attachable.

View attachment 2297545
[Galaxy S III Android Development] andip71:
Misacek, just to be very precise:

The app (the user interface) still needs root. This is required to change settings on-the-fly in the sys file system. There is no way round.

However - when you reboot the phone, the app does not need root anymore. The startup process will be completed fully without root. And this avoids many issues from the past.

Andi