yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
/sys/devices/system/cpu/cpufreq/iks-cpufreq/CA15_min_freq has always been there.

I benchmarked things at the time and a 800MHz A15 is still slightly bit faster than an A7 at 1500. I actually wanted to reduce the A15's min to 700MHz for a while. Keep in mind that you do _not_ want to have a perfect frequency table and jumps should be there for DVFS's sake.
[Galaxy S 4 i9500 Original Android Development] mw86:
I benched similar and found also that 800mhz a15 has seemingly double memory performance and slightly faster cpu power vs 750mhz a7. Passmark and Chainfire bench seem to be indicative of this performance difference on passmark memory performance and Chainfire java score seem to equally drop on a7 750mhz vs a15 800mhz.

Andrei, if you had enabled 700mhz A15 would there have been a way to get it to scale to that the way this is setup now. It is a very interesting concept to add another lower step to a15 :) 800mhz on that power draw chart seemed to be close to efficient but still double an a7 600mhz in power draw.
[Galaxy S 4 i9500 Original Android Development] bobdoblo:
What would be the difference or drawbacks if TwDVFS.apk was deleted?

I always delete it and notice no ill effects, if anything my battery life seems better and benchmarks are slightly better :confused:

NeatROM Mods

+

Battery Guide/Remove Apps
[Galaxy S 4 i9500 Original Android Development] mw86:
Maybe I just had a weird setup but I get better benches with it left as is. If i remove it I get random drops to 600mhz or lower under full loads. I saw this in not just benches. Restoring apps for example in Titanium backup showed the same behavior.
[Galaxy S 4 i9500 Original Android Development] dibartolodroid:
hello #andreilux… It does a stupid and inappropriate is question perhaps but exist a flashable zip to regulate the CPU for optimal performances in term of speed of the telephone? Thank you.

Envoyé depuis mon GT-I9500 avec Tapatalk
[Galaxy S 4 i9500 Original Android Development] bryanfuryin22:
Hi andreilux... just a simple question. I don't see you active on github for almost a month. Can we expect a new kernel by month end with the changes u mentioned earlier. Just wanted to know no intention to piss u off or bother u. Cheers
[Galaxy S 4 i9500 Original Android Development] bobdoblo:
What has happened to the audio on this kernel?

Everything else is great but i cannot use it because of the audio.

Anyway of returning it to normal?

I noticed in STweaks the volume sliders were at different levels to Adam kernel too.

NeatROM S2 Mods

+

Battery Guide
[Galaxy S 4 i9500 Original Android Development] mw86:
Use Stweaks app in app drawer. Should be there after kernel install.

we can expect a new kernel never. Expecting gets us users nowhere. We can graciously look forward to any progress Andrei makes on his kernel. His posts indicate an alpha 10 coming but he clearly noted it may be a few weeks. He noted clear plans to change the whole interface we adjust kernel options with because Stweaks has failed to fully cover well enough everything Andrei intends.

I am not being a spokesman for Andrei, I'm just noting what I read.

If you want stock like audio turn of speaker tuning in Stweaks audio section and add some volume if thats what seems missing. There's nothing wrong on the audio but if you don't like the tuning turn it off.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Absolutely wrong. If one disables that Speaker Tuning thingy, then the audio won't be like stock, it'd be exactly opposite. Anyone can test this by playing a same file on both stock and this kernel.
[Galaxy S 4 i9500 Original Android Development] bobdoblo:
I'm talking about headphones not speaker.

The audio quality sounds much worse than Stock and Adam kernels.

NeatROM S2 Mods

+

Battery Guide
[Galaxy S 4 i9500 Original Android Development] mw86:
Guys look at Andrei's post I am quoting. Speaker tuning checked is an option based on the tuning Andrei did with microphone and frequency analysis. Saying it is not is just giving Andrei less credit for his hard work. Having pretuned speaker tuning not checked is actually stock Samsung sound.

From github change log

" Sound control (part five):

New tuning for the speaker:

New frequencies are:

Band 1: 160Hz cutoff, +12dB gain

Band 2: 500Hz center, 1050Hz bandwidth, -9dB gain

Band 3: 2800Hz center, 2200Hz bandwidth, 4dB gain

Band 4: 7600Hz center, 4500Hz bandwidth, -10dB gain

Band 5: 20000Hz cutoff, 0 dB gain

Speaker tuning now applies a -3.5dB offset on the digital volume of

the DAC as to compensate equalizer added volume and have

generally equal volume to the default settings"

https://github.com/AndreiLux/Perseus-UNIVERSAL5410/wiki/Changelog

See Alpha 3.4 changes

Andrei even made the tuning adjustable you just echo what you would prefer instead to the wolfson control speaker eq gain file locations.

So stock is pretuned unchecked.

---------- Post added at 11:32 AM ---------- Previous post was at 11:23 AM ----------

The stock headphone gain was lowered to a more reasonable - 8db as when audio controls were first added to the kernel, Andrei and user's found it too loud for most headphones and caused distortion, so you could try the headphone gain at - 0db for a more original volume range. As for the "poor headphone quality of sound" you are far off my friend. I get better audio on here than my all about audio Ipod... Seriously check your rom, check your headphones or buy new ones. Don't blame Andrei's amazing Perseus kernel for your issues. If your rom has audio build prop removing them likely will fix it for you being that the kernel is no way the issue.

Example audio af resampler rate line in a build prop should be 3 not 255 which causes distortion and crackling. Check your setup. You can see you got your answer from Andrei, there's nothing wrong on any of our ends. I don't go to my rom dev and say my cpu wont run the right mhz I go to the source. Source here is unique to your setup alone.
[Galaxy S 4 i9500 Original Android Development] gio_b:
Hi,where i can change 255 to 3 ? Other suggestion for in ear audio?

Tks giovanni
[Galaxy S 4 i9500 Original Android Development] bobdoblo:
Well, i use Arrow ROM v.7.1 with PowerAmp + V4A and SoundMAGIC E10 IEMs.

It sounds brilliant on stock & Adam kernels but not this one.

But somehow its my set up?

Theres only one thing i changed so that by the power of deduction must be the issue.

NeatROM S2 Mods

+

Battery Guide
[Galaxy S 4 i9500 Original Android Development] mw86:
This is only if you have the lines in your build prop. If you don't this is not the issue your experiencing.

These lines:

af.resampler.quality=255

persist.af.resampler.quality=255

Are sometimes put into roms.

They should be like this which according to plenty of guide online is what the value should be for clear audio resampling. The other value resamples too much and adds cpu usage to audio playback while making audio lower in volume and little distorted.

af.resampler.quality=3

persist.af.resampler.quality=3
[Galaxy S 4 i9500 Original Android Development] gio_b:
O.K:directory ?

P.S: but from 255 to 3 what exactly what we change S.V:P ?

tks gio
[Galaxy S 4 i9500 Original Android Development] mw86:
Can't speak for soundmagic or poweramp but as for even stock viper v4a makes audio more shallow at defaults. Turning off all gains in viper to stock and removing the - db off the gain area will help but overall it is actually making it have too many filters. Seriously why would you need power amp, viper audio another one, Sound magic?

Having none of those and just the kernel, you would have clearer audio. None of us, that are not using your apps have these issues. Check your setup.

I've tried viper multiple times same thing you describe happens to me.

If the kernel is no good to you return to Adam kernel or stock. Unmodified this kernel audio is clear and normal.
[Galaxy S 4 i9500 Original Android Development] mw86:
/system/build.prop

Navigate there with a root explorer and edit with a text editor. Make sure permission of that file stay as they were before modified and reboot after change.

Rom toolbox makes it easy to edit these type of things.

See a post here for example where this line caused distortion for an android user. http://xdaforums.com/showpost.php?p=31509114&postcount=341

It's not bad in all setups but my sound was normal again after using that set to 3 and apparently at that link they just removed it. To fix it. I had an article that explained the possible values for this line but have misplaced it and after looking for last two hours have found that link for now instead.

If you like I can edit it for you if you upload and send your bp to me via PM where this conversation should continue if it is in your interest.

There is no guarantee that line or related ones are utilized in your current rom. It has only been a suggestion of the possibilities.

Basic guide on editing build prop here. You can check on it yourself if you would like as well. http://xdaforums.com/showthread.php?p=39622520

If you grab an app to edit build prop there is a free version of it if you need as well which works fine.

[MENTION=4613872]bobdoblo[/MENTION] please check my first link above in this post. The user had sound issues and they use poweramp as well (used power amp in past for short time it was seemingly a good app) and his issue solved removing the audio line from the users build prop. Have you tried that before?
[Galaxy S 4 i9500 Original Android Development] jujuburi:
I really dislike bragging but

this is NOT true

. As I said multiple times before, stock isn't pre-tuned unchecked, I am not sure if it's pre-tuned checked either, but I am fully sure that disabling pre-tune provides a sound which I have never heard before! As I said, just play any file which has little surrounding details, voices especially (it was the Battlefield 4 game-play for me, just skip to 2:25 and play till 2:35, just ten seconds are enough to tell the difference!), play it on stock, then play it on this kernel with pre-tuned disabled, even a non perfect eared person will notice the difference.

And those who are wondering why would one use Viper and PowerAMP, well I literally don't know what to say, but all I know that it's impossible for me to digest 'anything' after the PowerAMP and Viper combo, along with my adorable XB90.
[Galaxy S 4 i9500 Original Android Development] mw86:
Leaving pretuned speaker eq checked it uses Andrei's custom tuning.

If you were to put the following in an initd it would set pretuned eq to gain values which are default if you left pretuned checked. If you toggle it though you would have to echo the values again.

#!/system/bin/sh

echo "0" > /sys/class/misc/wolfson_control/eq_sp_gain_1

echo "0" > /sys/class/misc/wolfson_control/eq_sp_gain_2

echo "0" > /sys/class/misc/wolfson_control/eq_sp_gain_3

echo "0" > /sys/class/misc/wolfson_control/eq_sp_gain_4

echo "0" > /sys/class/misc/wolfson_control/eq_sp_gain_5

I am not sure on vs a stock gs4 kernel if unchecked pretuned speaker eq matches. But I do know this would put pretuned speaker eq back to a stock sound other than the audio gain offset that was put in to cover for the dynamic sound Andrei's pretuned produces.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Could you please elaborate the underlined part a little bit more? If I toggle what? The separate band gains or the speaker dB? Cause I never touch anything other than speaker amp in S Tweaks.

[MENTION=4613872]bobdoblo[/MENTION]: I just listened to a song on both stock and this kernel for three straight times now, nah, don't find any difference, at all mate.
[Galaxy S 4 i9500 Original Android Development] mw86:
If you toggle "Enable Speaker Tuning" which enables the loud speaker to use a copy of the eq implemented for the headphone with seperate config files for each band like the headphone. They are all in that wolfson_control folder you see in the code posted before.

If you apply the initd or echo those values for the speaker eq manually and you toggle that enable speaker tuning off and on you will need to reboot or use terminal and echo those to 0 again. But if you make that into an initd script at each boot the loud speaker would use stock eq instead of the one Andrei carefully made for us. You can also change the values after echo in that script and use your own gain values but you can easily make sound better or worse. But all of them set to 0 is stock.

But that speaker eq doesn't effect the headphone eq and are fully separated. The headphone eq adjustment is exposed in Stweaks as well as headphone gain. The loud speaker however has gain in stweaks but the eq is not exposed in Stweaks the locations in the code i listed above are the values the loud speaker uses for sound. If you check enable speaker tuning it uses the values Andrei set I linked the changelog on github which he made and goes in depth showing and explaining what was adjusted.

The headphone eq has a toggle in Stweaks to enable the eq values exposed in stweaks for headphone.

The headphone section other than default gain value of the headphone eq if it hasn't even been configured it should have stock normal sound as a stock kernel as Andrei I don't see has changed any defaults of the headphone section but simply exposed the options available with the Wolfson Dac. I think stock is a hair higher on the default gain for headphone volume. I hope helps.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Stock ALSA defaults to 56dB during playback, default driver is 64dB, and I'm adjusting it to be exactly like stock on ST defaults. There is no volume difference.

Furthermore I don't even touch the headphone audio beyond that, and Adam uses the exact same audio modifications which I wrote.
[Galaxy S 4 i9500 Original Android Development] mw86:
Thanks Andrei, that's even better news.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
[MENTION=4745870]mw86[/MENTION]: Okay, so let me get this straight, if I don't change/toggle the speaker tuning option then I won't have to redo that script you mentioned? I mean if I change the speaker amp that won't affect that file, right?

And how do I create that init.d file, which path? I mean there must be one already under etc afaik. Should I modify that one or create a new one? If it's the latter then will I have to provide a new name for it? I mean two files with same name will be merged anyway right?

Sorry for asking these, but I'm a basic user, and I like that :p
[Galaxy S 4 i9500 Original Android Development] mw86:
Okay, so let me get this straight, if I don't change/toggle the speaker tuning option then I won't have to redo that script you mentioned?

Yes, but it's not that you would need to redo the script it's that you would need to rerun script ie reboot for it to launch for you again.

I made the file for you. This will save you time. https://db.tt/ZSbVjMCQ

Just place into initd. Unless there is a script there named audio this will launch seperate from any other initd script in there. Goodluck.

Your welcome to after 20 secs after boot to check here: /sys/class/misc/wolfson_control/eq_sp_gain_1 at the 5 files with eq_sp in their name there to have 0 set in them. ES File explorer is a easy to useroot explorer to do that and has its own text editor to read the file in it.

Available on play store free here.

https://play.google.com/store/apps/details?id=com.estrongs.android.pop
[Galaxy S 4 i9500 Original Android Development] jujuburi:
[MENTION=4745870]mw86[/MENTION]: Okay, so I pasted your text file under init.d folder. Just see the screenshot if I have done it right. Need to change the permission to same like the other two files there right?
[Galaxy S 4 i9500 Original Android Development] mw86:
You did it right. I usually set all initd to permission showing rwxrwxrwx for each of those. But yeah atleast match the permissions for it with the files next to it.

*#*#*#*#*#!

Edit: that won't work. Delete the .txt off it buddy so it just says audio or that script won't launch. That happens often from Dropbox it makes it a text file. Just delete the .txt off of the end of it.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Hope everything is all right now? I'm gonna check now what difference it made. Thanks for your help once again.
[Galaxy S 4 i9500 Original Android Development] mw86:
That should be perfect and you are very welcome.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
[MENTION=4745870]mw86[/MENTION]: It works mate, it just works. Now I can hear smooth, non distorted audio on this kernel. What was terribly distorted at +3, isn't even near at +6 now! What a relief!

Thank you.

[MENTION=4613872]bobdoblo[/MENTION]: Try that script dude, it should work.
[Galaxy S 4 i9500 Original Android Development] mw86:
This only effects the loudspeaker so if the headphones were the issue for Bobdoblo this will not effect it, but there isn't anything for headphones that differs when set to defaults in stweaks in this kernel as Andrei was gracious to take his precious time to correct one of my statements on all this. So stock headphone settings in stweaks on this kernel is same as stock kernels.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Yeah sure, it was the loudspeaker issue which was driving me crazy. As I said before, before Andrei's comment, I didn't find any difference in audio output via headphone with this kernel and stock. bobdoblo must have some setting problem.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
First of all, a big thank you to Andrei for all his work, that we can all use thanks to him.

I can admit upfront without any tortures that I am no specialist in this, so if my questions are very basic, I appologise.

Before I ask my questions, my background: rooted i9500, stock 4.2.2 android, with lots of bloatware(including some services) frozen by me. Latest perseus kernel.

I have 2 things that I wanted to ask. First, I noticed that on some phone restarts break the sound, meaning there is no sound at all. When I plug in a headphones I don't see a notification that I do on other occasions, and there are no sounds whatsoever. Sometimes it takes just 1 restart to bring the sound back, sometimes it takes couple. Is it a known bug, with some known solution?

Second question is for anybody (including Andrei ofcourse) who knows something about the current settings. The problem is as foolowing:

When I charge the phone with USB cable (connected to usb 2.0, as some say 3.0 gives more current, didn't try that) the current that the phone receives is 500 mA. When I use however the newest wall charger from Samsung, it has the outgoing current of 2.0 A. All is great, until I don't get in the middle the mhl 2.0 adapter from Samsung. As one person in a thread theorized and I checked, when the phone gets connected to mhl adapter, it treats it as a usb port, even though it might get 2 A current from the wall charger. Consequently, the phone pulls of only 500 mA from the mhl adapter.

The problem with it, is that the phone when used with mhl adapter is on high strain, usually running something which is cpu intensive, and also the screen is on. So even with "charging" the battery is being drained because the incoming current is too small. If it was 2000 mA, like with a normal connection to wall outlet, it would be charging (slowly, but still).

I just checked the sTweaks, and there are lots of options in the battery tab. Is there any setting that I could use, that would help me? What I'm looking to achieve is basicly, for the phone to drain the full 2000 mA from the mhl adapter, when it's connected to it, instead of just 500 mA.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
[MENTION=4438995]lukair1983[/MENTION]: Regarding your first query, yes, it's a known problem and afaik it happened with stock kernel too. Some say that it has been solved with the latest kernel sources, some say don't. I personally am using Perseus for more than a week now, and I never faced the problem. Before that I was on Adam, for about two weeks, never happened with it either. So basically I haven't faced that issue, yet.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
@Up

Thanks a lot jujuburi for taking the time. I appriciate it.

I noticed that for some people this problem is persistant, for others it happened only once or so. It is a safe bet, the fact I forgot to factory reset after I did an android stock update might be the cause here. But since, the 4.3 seems getting close I will wait with further investigating, since the flashing the newest android might fix it.
[Galaxy S 4 i9500 Original Android Development] djigane:
Hello. I am posting this both in this thread and in Arrow thread, cause I don't know if the issue is linked to the kernel or the rom:

Encountered random reboots while using headset connected to Car Aux (for listening music) and bluetooth earpiece connected to device (for making and receiving calls).

The reboot occurs most of the time just after a call, as it cut off music from headset.

Precision : this happens even with Viper4Audio un installed.

Does anyone face that issue?

Regards,
[Galaxy S 4 i9500 Original Android Development] bobdoblo:
Its not the kernel mate, it happens on Adam too.

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] djigane:
It's not V4A either, as I've faced the issue without V4A installed... Weird...
[Galaxy S 4 i9500 Original Android Development] djigane:
Hello, all

[MENTION=4167023]AndreiLux[/MENTION], I've tried to reproduce the conditions when phone reboots while headphone output connected to Car Aux (for listening music) and Bluetooth connected to Bluetooth earpiece.

The reboot occurred again, just after a call, without Viper4Android installed...

My configuration : Latest Arrow Rom + Perseus Kernel + and latest Wanam Xposed.

Before making the call, I've recorder all logs with catlog. So attached please find the log, if you kindly investigated.

Note : posted this in Arrow Thread too, because I really want to understand why these reboots happen...
[Galaxy S 4 i9500 Original Android Development] Caspersky83:
Maybe your problem is not related to the kernel. I also had random reboot on lockscreen when I tried to unlock device after the phone was in hibernation for a long time. I tried Perseus & Adam kernels. Then I just made a full wipe and reinstall ROM. Problem is resolved.
[Galaxy S 4 i9500 Original Android Development] Aijazji:
Perseus alpha10 Up :) Downloading....
[Galaxy S 4 i9500 Original Android Development] fierce_brake:
awesome ! perfect excuse to flash another ROM !
[Galaxy S 4 i9500 Original Android Development] HannibaL_kk:
Great job AndreiLux! Any plans for synapse and play store?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
It's up already. I'll try to deliver updates which don't involve changes in kernel via that. I wrote the basic requirements for it on the Wiki: https://github.com/AndreiLux/Synapse/wiki .

I'm also planning to do some expanded features in the future and particularly one I want to expose in a "premium" version (Don't blame me, you guys have been cheap lately).
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Andrei, any help with the problem us, mhl users have? Here is my explanation again:
[Galaxy S 4 i9500 Original Android Development] NBruderman:
When I install the kernel synapse take the control over Stweaks? because i noticed that the kernel still install stweaks, even after uninstalling and reflashing? who do i configure the settings now?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
MHL currents are hard-coded but can go up to 1500mA depending on MHL adapter. I didn't expose those for configuration yet since I'm not sure if it would be wise for the adapter.

STweaks is dead, gone, dust. If you uninstall it it should remain so.
[Galaxy S 4 i9500 Original Android Development] Grarak:
The kernel doesn't install STweaks anymore