yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] Jimmy34742:
Andrei, is the lost audio problem being treated as a separate development bug, or are there too few people reporting it? Starting with alpha3, I frequently lose audio. The workaround has been to reboot until audio returns, and this sometimes takes 2-3 reboots.

But this latest time, I discovered I had no audio when my phone vibrated a phone call, and of course I missed that phone call. Rebooting 4 times still didn't restore audio. I had to flash the latest Adam kernel, and it immediately restored audio. Meanwhile, that's 20-30 minutes lost before I could return the phone call, so the bug has a serious impact. I'm concerned that there aren't many people experiencing such a serious bug so that you're not able to give it specific attention due to to little data.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
From time to time, I get that also... Very randomly...

But get back sound after only one reboot... Please don't forget to turn the sound off before rebooting...

---------- Post added at 07:18 AM ---------- Previous post was at 07:10 AM ----------

I have been closely following your messages regarding this lag...

But really can not have it on my phone...

And my swap settings is as follows...

And one thing I realized while I was tuning my voltages to be able to run @ 1,9GHz, I found out that if you max these settings like mine, you have more ability to UV... On default values been able to less UV... Tough this is OT for now...

I highly suggest you to try without Crossbreeder... As far as I know it is not that stable...
[Galaxy S 4 i9500 Original Android Development] ama3654:
I9500XXUBMG1 changelist=997834 Russia
[Galaxy S 4 i9500 Original Android Development] kirabyte:
I9500XXUBMG1 changelist=1011208 Bangladesh
[Galaxy S 4 i9500 Original Android Development] cmd512:
English may not be your first language, so I'll forgo the fact that you completely missed my point:

1) I did a fresh install of 933xxx changelist ROM.

2) Installed alpha4 kernel only.

3) Used it HEAVILY (push E-mail, opening / closing heavy such as browser / facebook / camera / etc, and the lag WILL appear)

Note that none of the above includes CrossBreeder, which is why I said the lag has nothing to do with it. I'm glad you are not having any lag issues, but several members have already confirmed there IS this system freezing lag after extended use. Again, same setup, v3.4 = no issues.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
may not be my first language but everybody can missread and may not see your "only"... no need to be rude...

what the hell... mess with it, my bad to care for your messages...
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
Both of you guys just chill out, no need to be fpaming in this thread as we all know hardware is slightly different from one phone to another some can OC to a stable 1.9 and sone just cant.... meaning the lag might be a hardware related "again maybe.." so lets wait for Andrie and see he might come up wity a fix for this each device acts in 8ts way so no jeed to be accusing each of useless stuff... wait and we will fix this eventually as you know Andrie still calls this an Alpha build for a reason :)
[Galaxy S 4 i9500 Original Android Development] cmd512:
You chill out, I even acknowledged English may not be his first language, so that may be why he didn't get completely what I was saying. I can't help it if his panties got all up in a knot when I was actually trying to be understanding.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
stop nagging about your hardware than... and answer me, not over somebody else... you arrogant ...
[Galaxy S 4 i9500 Original Android Development] runedrune:
Now now children. Let's all stop fighting.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
ain't no children at an age of 36 and this is the first time i am in a situation like this and get pissed off...

flaming and getting rude over keyboard is so easy for people... tough my intentions was all good and wanted to share my experience...
[Galaxy S 4 i9500 Original Android Development] cmd512:
English may not be your first language, so I'll overlook the fact that I never mentioned anything regarding hardware.

(Seriously, calm down, you're just making yourself look bad now.)

Anyway, back on subject after that short interlude. mw86, you should share your lag findings that you PM'd me about here. Would be good to update the github issues post also.
[Galaxy S 4 i9500 Original Android Development] Xphoid:
still teasing me... but will stop... i said what is need to be said!
[Galaxy S 4 i9500 Original Android Development] might277:
U can use Android system info app to check that
[Galaxy S 4 i9500 Original Android Development] gio_b:
mmmm....audio is to much pamped ,but depends on your taste ,and head phone :i suggest a pair of Klipsch Image X10 Noise-Isolating Earphone ,my actually .

neutron :

my set all =0

surround yes :100/14000/5.5/35.5 ,all =0

tks gio
[Galaxy S 4 i9500 Original Android Development] razer1224:
This is why i left this community :(

They Never Change
[Galaxy S 4 i9500 Original Android Development] droidphile:
Some of us are easily pissed off / offended / disturbed by another user's reply or post. Think of the OP who has to read all these, and still works on hacking for countles hours. I'm sure most of you have no clue how much time he spends on this kernel. Atleast let's be worried that if he should stop this work for any reason, there is no other kernel hacker for this device.
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
finally a reasonable guy in here XD, honestly you said it it the best way ever... we all may get pissed because of small things the only clever move is to release it in no time and no drag the whole nurves over it hehe... anyway they are ok now of course many of us have a different mother language including myself, some of us know the right grammer and other dont but still it doesnt mean we need to disrespect them just because "dey rote dis laik dat" and iam not copying any of your posts its just me so dont burn me :P

hopefully Andrie will be more of understanding in this case we do have two kernel devs for now hopefully more by the end of the month who knows ;)

:good:
[Galaxy S 4 i9500 Original Android Development] Xphoid:
You all guys commented are correct.. Maybe my bad... Sorry for my side...
[Galaxy S 4 i9500 Original Android Development] gio_b:
hi:

in "IO"

i do not have :swap file and the other seting , only read ahead ,internal external...?

tks gio
[Galaxy S 4 i9500 Original Android Development] HassanM:
Has anyone flashed Alpha 5 yet... ????

Plz post your experiences...
[Galaxy S 4 i9500 Original Android Development] zetlaw:
Overclocking A7 to 1500mhz Sounds awsome !!
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
You're been doing nothing but asking other people for their settings, their problems, their experiences all over this thread. You'd be better off if you just either learn to get some initiative to test things out yourself or just stick with a stock ROM and kernel.

Some people might not be able to reach those frequencies.
[Galaxy S 4 i9500 Original Android Development] anasnemer:
if i increase frequency for little cores from 600mhz to 750 MHz

my phone rebooting

is it my s4 not supporting maybe ?
[Galaxy S 4 i9500 Original Android Development] omvir:
Yes.

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] hotheabilly:
My s4 just capable at 650mhz. any higher values is rebooting the devices. 100mhz extra clock from 1200mhz :D
[Galaxy S 4 i9500 Original Android Development] omvir:
If I want to only use my a7 core clocked to 1500, will the following settings work?

CPU max frequency: 600

CPU min frequency: 200

A7 max frequency: 750

Will these settings give what I want?

EDIT: for people not being able to handle anything over 700, adjust the voltages I just noticed the voltages for the little core for frequencies above 600 are very low, lower than their original value for some reason.

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] Alberto96:
My doesn't like a15 and a7 overclock :( Maybe I need to play a bit with voltages. For me only GPU OC is full working.
[Galaxy S 4 i9500 Original Android Development] omvir:
Read my edit above your post!

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] beatsmaster0510:
Thanks for the latest release. I am not able to reach 1500mhz on the little cores. Will it appear on Stweaks or to be configured manually? Thanks.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
CPU max frequency is the policy maximum and has precedence over the "A7 max frequency" configurable. Those settings will not go beyond 600.

They're in STweaks.

I'm able to run 99%tly stable on 1500MHz at 1300/1312mV. Sadly that 1% kicks in every once in a while and crashes the phone. I'm fully stable at 1400MHz. I tried 1600MHz but was never able to reach that even temporarily.

I populated the ASV's for the new frequencies myself, so those voltages are pulled out of my ass and based on my own ASV6 device. You'll have to find optimums yourselves.
[Galaxy S 4 i9500 Original Android Development] skivnit:
As usual great job Andrei. I'm running at max 650 with 1500 MHz on the Lil cores 1300 is the sweet spot under it my device freezes
[Galaxy S 4 i9500 Original Android Development] mw86:
Thanks Andrei I am running the 1500mhz max on A7 and I hope it stays stable but set like on those defaults you made it is working for me so far.

Ill look for the occasional crash.
[Galaxy S 4 i9500 Original Android Development] mrej201:
can flash this to my note or its only s4
[Galaxy S 4 i9500 Original Android Development] skivnit:
You can - 50 from 1400 to 1000 however 1500 should be at 1300 anything below cases instant freeze

Swyped from another galaxy
[Galaxy S 4 i9500 Original Android Development] beatsmaster0510:
I have -50mv UV on all core steps (Big and Little cores) and have problem at all. I can attest that setting the Little core max frequency to 700 and above freezes the phone.
[Galaxy S 4 i9500 Original Android Development] zoule HCo:
The lag time when opening the camera still exist.. I'm using my phone intensively the camera will take some time to load.

anywhere the kernel are good as always. Thanks for the update..
[Galaxy S 4 i9500 Original Android Development] cmd512:
Many thanks Andrei, alpha5 working well. Glad to see zSwap gone, after extensive testing, I'm fairly convinced that was the culprit behind those weird 30+ second freezes / lags that alpha4 introduced.
[Galaxy S 4 i9500 Original Android Development] dazkyl:
I just set the a7 max frequency to 700000 kHz. does this mean my little cpu's are overcooked to 1.4?
[Galaxy S 4 i9500 Original Android Development] Al Gore:
Is it possible to mute external speaker only when the headphones are playing sounds? So when you pause music the speaker is loud again.
[Galaxy S 4 i9500 Original Android Development] xtacy1:
Correct
[Galaxy S 4 i9500 Original Android Development] NOORHASHIM:
Andrei .., No solutions to Fix OverHeating ?
[Galaxy S 4 i9500 Original Android Development] skivnit:
Undervolting should lessen the heat. You have all the tweaks to make the phone run at lower temperature
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
How do you suppose he fixes a hardware issue ? It known these chips heat after extensive usage..... every phone does that it only depends on how muchyou stress it and how powerful the chip is...

Your best solution mate would UV which may extend your usage time before the device heats up again
[Galaxy S 4 i9500 Original Android Development] runedrune:
Nanobots.
[Galaxy S 4 i9500 Original Android Development] jlevy73:
I know the CPU gets throttled, what about the GPU? My device runs perfectly stable @640mhz but when benchmarking using 3DMark or GFX my scores are lower than stock kernel. This would make sense if the GPU get's throttled, if not, it defies logic.
[Galaxy S 4 i9500 Original Android Development] REVERSiN:
Made my day hehe.... have a great weekend!
[Galaxy S 4 i9500 Original Android Development] skivnit:
Great battery life so far I'm @ 70% left with 2h15 min screen on time full brightness
[Galaxy S 4 i9500 Original Android Development] jlevy73:
No camera lag on alpha 5 thus far and the micro-stutters I was getting on alpha 4 are gone.
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Finally fixed OC. Now running 1,7 GHz for A15 Cores (1,7 GHz overvolted a bit 1150000 uV) and 1,4 GHz for A7 (with default voltages). Stability tested with Antutu Stability Tester.

Thanks a lot AndreiLux
[Galaxy S 4 i9500 Original Android Development] dazkyl:
This kernel version 5 is awesome. The battery life is great , device barely heats and i just set my big cpu to 1.8ghz with -50uV (for1800mhz step) and -75uV for all the rest ... and the little cpu to 1.5ghz (stock voltage) and the rest of the little cpu steps with -50uV. Everythign is stable !
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
If you're referring to the way that privacy mode works? Sadly no. I tried to get it to work this way but speaker and headphones have the same audio sources, so I can't differentiate output paths since whenever something is played back out of the speaker, it will also be played on the headphone if they are plugged in. I can only do it the other way round.
[Galaxy S 4 i9500 Original Android Development] yahyoh:
Andrei did u saw this : http://www.linaro.org/linaro-blog/2013/07/10/big-little-software-update/ :D

do u think it will Work on Exynos Octa :)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
No it won't. The only new thing is that they've coined a new term for MP which is now renamed to GTS.

This is pretty much official confirmation that the 5410 won't ever be able to use it, as they specifically note that in the last paragraph, same thing as I've said some time ago. You'll have to wait for 5420 devices to fully use big.LITTLE.
[Galaxy S 4 i9500 Original Android Development] mw86:
Nice article but I think we are still in same boat on this current cpu bsed on this section of text at end of article.

" As has been publicly noted, the current generation of hardware cannot yet take full advantage of the IKS or the GTS designs because the hardware power-saving core switching feature is implemented on a cluster basis rather than on a per-core or a per-pair basis. Even so, the first big.LITTLE implementation produces performance and power consumption on a par with the latest Qualcomm multi-core Snapdragon processor according to reviews from Engadget, PocketNow and others."

---------- Post added at 01:11 PM ---------- Previous post was at 01:08 PM ----------

Andrei, may I ask what the cpu considers a cold state, based on the description of voltage control in Stweaks. Is there a certain target temperature of cpu that triggers the 75mv raise to the shown/set values. Also does it account for battery temp too or just cpu temperature state.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I need to fix that description since it's wrong. The correct one is that everything gets overvolted by 75mV when the temperature is at, or below 20°C.
[Galaxy S 4 i9500 Original Android Development] mw86:
Using userspace governor I stress tested on all benchmarks i put A15 through and used chainfire bench to show weakness. After about two or three runs it destabilize on 1500mhz A7 but seems rock solid on 1400mhz using same volt shown as default. So I'm also staying on 700mhz A7 max.

A user above mentioned a thought of scaling is made harder using increased A7 max to get to A15. The scaling is working same. Using a faster mhz available on A7 does help the need of scaling up but is not hindering it. The touch boost was lowered and by observation it seems to be 400mhz under light load vs stock 600mhz touch boost. I like it this way it is a much more reasonable jump from idle mhz. This does however make the cpu less likely upon touch to cluster migrate to A15 when touch boost was 600mhz it was way to easy especially using stock A7 max to scale up to A15 as the requirement to step to A15 is that it sits for a cycle at A7 max. I like this new setup as it prevents the touch from causing A15 activation from sitting on A7 max and getting a sudden load which runs better now as it must go from 400mhz to A7 max still upon touch to be able to hit A15 on a sudden load while user had finger on screen. The cpu still scales according based on load. I thank Andrei very much for putting so much thought and time into his kernel changes.

If users think A7 is hard to scale to A15 now ypu just need to make it easier to hit your A7 max (up threshold L) or easier to hit up step level b / high frequency zone by carefully lowering those values. As is it should be better on battery then it was.

I'm trying a theory out. Theory being make single thread speeds better but not destroy battery. I set my up threshold L from 60% to 25% so if a single thread gets a 100% load showing as 25% total cpu load, it may improve single thread performance while in A7 cluster. Tapatalk and basic apps are already more responsive but I'm sure it will draw more battery than stock because it makes it a lot easier to scale to A7 max. Whereas it's much harder to scale to A15 by up threshold B etc or up threshold as it's 90% default stock. Meaning many threads need a large load of the 4threads (cores) total.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
That's not how it works. Load is the per-cpu roof load value of all cpus. In a sense, your theory is already how things are done.
[Galaxy S 4 i9500 Original Android Development] mw86:
Thanks for explaining my misconception. I am glad it is that way, thanks again. I reverted to stock of that threshold after testing on it and seeing it far to easy to hit max A7. Your explanation reinforces my use of stock value once again.
[Galaxy S 4 i9500 Original Android Development] croach246:
A word of advice before flashing!

Just flashed alpha5 coming from 3.4 on omega v8 rom, phone would reboot after 10s or so after booting, then would get stuck in a boot loop. Tried refreshing etc. Ended up flashing the rom again then flashing alpha5 (working now).

I believe the voltages I had set on android tuner to apply when booting may have been causing this. So reset voltages to stock, disabled apply on boot then reflected rom.
[Galaxy S 4 i9500 Original Android Development] Hakosuka11:
Same happened to me, but I set to the default values and everything is working fine til now
[Galaxy S 4 i9500 Original Android Development] PROTOCHIP:
Dear AndreiLux,

Flashed alpha5... No camera lag anymore... Thanks a lot...

But i am getting lower gpu scores comparing to alpha4...

Gpu @640 and undervolted a bit... Same value i have used with alpha4...

I also tried with default values but still lower scores...

Observing those;

I see shuttering in Epic Citadel which didnt exist with alpha4 also...

Also Nenamark2 score is lower even the gpu is overclocked...

Antutu has lower gpu scores also..

Has something changed with the gpu overclocking module or it is just me ?

Thanks in advance...

Kind regards.

Sent from my iAmiga
[Galaxy S 4 i9500 Original Android Development] pas2001:
Thanks sir. I try your work with wanam lite 1.6 . After flash the sound ( RINGTONE SYSREM SOUND etc. )has gone . Where can I adjust this. Thanks again sir.
[Galaxy S 4 i9500 Original Android Development] dazkyl:
So by this should i leave the a7 cpu at stock value or is it okay to overCLOCK to 1.5 as i did?
[Galaxy S 4 i9500 Original Android Development] jlevy73:
I'm seeing the exact same thing with the GPU.

Regarding the camera, I'm starting to observe lag especially after CPU intensive activities. After playing a game for about 20 minutes went to turn on the camera on it took about 10 seconds to load. I could reproduce that pretty consistently so I'm thinking this is a FW issue although I haven't tested stock kernel under the same conditions.
[Galaxy S 4 i9500 Original Android Development] zoule HCo:
I've experience the same with intesive activities. The camera start to lag. It will take time to open it.. normally between 5 to 10 second on the first run..

I've tried this on stock kernel.. the lag doesn't exist.. not so sure what it cause. Could be some thing on kernel..

I love this kernel especially on battery and sound tweak.. better than other kernel..
[Galaxy S 4 i9500 Original Android Development] mw86:
If your not getting random crashes or reboots such as comeing back to fphone and realizing the screen it is on it must have rebooted than I wouldn't worry and I would use the 1.5ghz a7. Im using 1.4ghz only because that is what has proven by testing to be stable for my cpu.

---------- Post added at 02:34 PM ---------- Previous post was at 02:26 PM ----------

The majority of users are actually reporting the camera lag to be fixed. Zcache was removed for now to help this. Please see github to report issues, find fixes and help. Here is the one for the camera lag that has been fixed in latest build. https://github.com/AndreiLux/Perseus-UNIVERSAL5410/issues/10

Please see change log.

Perseus alpha5 (11/07):

A7 core overclocking up to 1500MHz. Configurable only via STweaks or /sys/devices/system/cpu/cpufreq/iks-cpufreq/CA7_max_freq.

Adjusted touch booster and other QoS locks to lower frequencies.

Disabled ZSwap until further notice due to random crashes and suspected battery drain.

If using mods or ram scripts or anything of the same capacity it is important to debug and see if these were the cause of issues too. I believe you guys just updates to latest and are reporting this.

CMD and Protochip as well as me have not had the lag anymore so maybe it has to do with the rom or firmware update one is on. I hope the lag for you guys is easily sorted out. Cpu speeds can effect opening apps dramatically so if been modified try defaults. Also running out of ram available will dramatically cause stutters and lags try to lower amount of apps that stay in background when they are uneeded.
[Galaxy S 4 i9500 Original Android Development] jlevy73:
Thanks mw86, but i've tried all the suggestions you have stated previously to no avail. I use no mods, hacks, init scripts and have updated to the latest MG1 FW. Plenty of RAM available. I can reproduce it at will, 15 minutes of buggy blitz or some intensive gaming or browsing and the camera will lag 5-10 seconds on opening. Running on stock kernel I do not get any lag. I'll open or re-open this on Andrei's github.

Everything is running mint with this update, just this one issue.
[Galaxy S 4 i9500 Original Android Development] oblivion186:
hey just wanna ask

if i install this kernel without touching the stweaks( not gonna undervolt or mess with the sound setting) will the battery life improve or will it be the same as stock kernel?
[Galaxy S 4 i9500 Original Android Development] omvir:
If you're not going to touch it after flashing the kernel, you should just stick to the stock kernel. :)

Sent from my GT-I9500
[Galaxy S 4 i9500 Original Android Development] I_M_I_2:
I have not touched the stweaks at all, n the battery life for me is amazing. Plus the phone doesnt heat up half as much as the stock. Amazing kernel this is.
[Galaxy S 4 i9500 Original Android Development] Nghtmare:
Im using 1.4Ghz in the little cores and its super solid, also 1.7Ghz in the A15s and its great. I cant find a proper voltage for 1.8, maybe its because max ive tried its 1225mv. Here are my voltages for both chips.
[Galaxy S 4 i9500 Original Android Development] zetlaw:
soulja30589 = something is very weird. i have the Same device I9500 with Perseus Alpha 5.

but my Default voltages are different than yours. i repeat the DEFAULT voltages not the ones you set.
[Galaxy S 4 i9500 Original Android Development] Nghtmare:
Because none of the ones im using are stock voltages :P maybe 1.9 and 2.0Ghz on big cores but because I dont care about them. The rest I did them myself, Im just sharing to see other ppls set ups since from what ive seen I uv the chip a lot more than most people I saw. I just need some tips on 1.8Ghz since I forgot what stock voltage was.