yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] brunodu91:
Someone have a cm rom with googy max kernel? What are you set for good battery and performance?

Thx
[Galaxy S 4 i9505 Original Android Development] MehStrongBadMeh:
I also lost IR functionality in Smart IR Remote (a.k.a. Anymote) on the Danvdh Google Play Edition while using GE 1.2.1 kernel. I have reverted back to the GE 1.2.0 kernel for the time being where IR works properly. It is easy enough to stick to one older version for this problem, but I hope future updates return the IR to its 1.2.0 and lower functionality.

Also, thanks for your work on this kernel, googy.
[Galaxy S 4 i9505 Original Android Development] edzamber:
[MENTION=1897326]googy_anas[/MENTION],

Hi googy, just for information, Alucard made a CM12 version ;)

http://xdaforums.com/showthread.php?p=56943308
[Galaxy S 4 i9505 Original Android Development] brunodu91:
[MENTION=4507636]edzamber[/MENTION]

Cool but useless on kit Kat? !
[Galaxy S 4 i9505 Original Android Development] edzamber:
Yep, but Googy-Max3 is for CM11 too so it will be great that CM12 runs with Googy-Max3 Kernel (the Best for me !).

Kissss ma poule :)
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
I'd prefer to wait until cm12 reaches a good level of stability...

Envoyé depuis mon GT-I9505
[Galaxy S 4 i9505 Original Android Development] edzamber:
It's all in your honour ! :)
[Galaxy S 4 i9505 Original Android Development] Giga37:
Use the Google ROM Edition and then come try this kernel and I'm liking the results, I did not spend half the battery is still far behaves very well.

Intelliactive working perfectly :D

I saw here that Zzmove will be implemented, this soon this implementation? : D

Congratulations for the work done and continued :D

|| Enviado através do meu S4 @ GT-i9505 Google Edition ||
[Galaxy S 4 i9505 Original Android Development] s1l3nt:
Just noticed ir blaster is not working for me on 1.2.1 using smart ir remote. Worked perfectly on 1.2.0

Sent from my Google Edition S4
[Galaxy S 4 i9505 Original Android Development] viper531986:
I can use kernel 1.2.1 with multirom? Thanks.
[Galaxy S 4 i9505 Original Android Development] Mystique:
[MENTION=769869]viper531986[/MENTION]

Is that a TW or CM based ROM?

Whatever your answer, use that version of GMX, currently 1.2.1.

(1.2.2 in the works..)
[Galaxy S 4 i9505 Original Android Development] viper531986:
Its tw rom the kernel is for primary rom.
[Galaxy S 4 i9505 Original Android Development] marcondi:
Reboot with S4 Echoe Rom v.27

Hi,

i have some reboot with my rom... one a day and after the upgrade of my apk with google play.

Solutions?

thank for your job :D

Roberto
[Galaxy S 4 i9505 Original Android Development] Gamer-king:
Why do you think this issue is kernel related?
[Galaxy S 4 i9505 Original Android Development] mattiadj:
Googy please can u try to improve zram performance??
[Galaxy S 4 i9505 Original Android Development] Solace50:
use 1.1.9 its stable.
[Galaxy S 4 i9505 Original Android Development] bluflight:
And latest 1.2.1 is stable, your reboot is not kernel releated sure.

I'm trying intelliactive and feeling is very good. I noted a performance similar to nightmare, but more battery friendly. Really good [emoji106]

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] mekoa8:
Can you share your settings for TW Kernel 1.2.1?
[Galaxy S 4 i9505 Original Android Development] bluflight:
- governor intelliactive (usually i use nightmare, but i'm testing this and i found it similar to nightmare with performance, but more battery friendly)

- scheduler fiops

- untick android logger, zram

- tick (activate) special tweaks under misc tab

Reboot phone

Edit: i not like to play with uv, all stock values
[Galaxy S 4 i9505 Original Android Development] Gamer-king:
Every time I selected intelliactive as governor my battery drains pretty fast. Even after a reboot. Any idea why?
[Galaxy S 4 i9505 Original Android Development] bluflight:
Never had reboot, i think is something rom releated. Check maybe xposed modules if you use for example.

Try to download again kernel, copy to phone and reflash

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] dyval:
which kernel governor is best on performance? thanks
[Galaxy S 4 i9505 Original Android Development] !crazy:
People reporting great battery on inteliactive either had pretty terrible setup before, or something other than just governor has changed, like some services settled down or whatever and improved battery. Inteliactive is per default more tuned for performance I would say. That is what I anyway prefer, but I still always edit default governor settings. No chip is same, everyone has a different usage habits, and even governor developers are not omniscient in that regard, and they also experiment and try to guess what could be the best default setting.

In other words, one, especially the one who plays with custom kernels, tuning etc, should learn to tweak governor parameters, and to understand what which variable represent/does, and it's effect on the CPU.

IMO all reports about incredible performance achievements allegedly caused by governor change and similar are mostly placebo.

If you want to play a bit with inteliactive, try increasing timer rate to 30k - 50k, or even more. 100k was standard value for governors like on demand, today people play with 10k. Ali card for example was using /or uses 65 k or similar. That is a rate at which governor evaluates the scaling and load of the processor, and decides what to do in the next steps.

You could also lower high speed frequency to lower value than highest frequency and than play with above high speed delay values. For a while highest frequency was used as a default value for high frequency of interactive also, but not any more. IMO one should try getting something out of above high speed delay, when we already have it. If you want governor to scale fast above high speed, up to the maximum frequency, than lower the above high speed. You can also play with lowering target load and go high speed. That would normally improve performance, but this CPU has a much better implemented C3 power saving state, comparing it to older devices, and now rave to idle starts making sense, maybe, and in theory that can improve battery time too (because the sooner the job is done, the sooner can cpu switch to C3 or even turn it self completely off.).

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

I withdraw my statement that inteliactive us not great for battery, I cannot know, and claim that. It is just my opinion, or better said, what my intuition and my experience tell me... But that experience is just related to my device, and my usage.
[Galaxy S 4 i9505 Original Android Development] Mystique:
Agreed.

Many people do find intelliactive better.

I never wanted to try nightmare because it did not sound battery friendly..

Choice and options.. Thank you Android.

Great points by the way.

Have you seen the H3 governor?

What is the equation if usage that makes sense for certain users.

That is what I am trying to figure out..

But it us impossible to solve an equation with more than one unknown.

Thank you for your post; even more.. Thank you for your addendum.
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
Most of all, thank you both for your valuable contributions. You don't talk much but when you do, it's just like a surgical strike ;)

Envoyé depuis mon GT-I9505
[Galaxy S 4 i9505 Original Android Development] Mystique:
What version of the kernel?

TW, GE, CM..

In recent versions googy changed the voltage to be accurate for each users device.

This major revision would change how your device consumes power.

If you are interested, toss me a PM.
[Galaxy S 4 i9505 Original Android Development] vt0r:
Personally, I think the default value of 20k is fine. The only setting I changed was hispeed_freq to 1566000, as it feels smoother during scrolling and other touch events than when I previously had it set to 1242000.

I've also dropped the max GPU freq down to 320 MHz, but I'm not a mobile gamer, so I have no idea how others would feel about the small down step.

With the above settings, intelliactive seems to give me somewhat similar battery drain to nightmare, even with the fact that nightmare is far more aggressive on scaling down.

It's a phenomenon I'll probably never be able to explain, but since intelliactive gives a smoother experience with touch events, I'll probably stick with it over nightmare, even if it costs me some screen on time.
[Galaxy S 4 i9505 Original Android Development] genuino80:
Infrared sensor not working after kernel update

Hello all,

I'm using version 1.2.1 GE and I'm having problems with the infrared sensor, it does not work. I restored version 1.1.9 GE and the infrared sensor has resumed operation.

I'm using Google editon 4.4.4 by Danvdh.

Do you also have the same problem with this latest kernel?
[Galaxy S 4 i9505 Original Android Development] !crazy:
So you have only changed that? Than you had 2 phase frequency set higher than high level frequency. Doesn't make sense IMO.

Edit. Regarding responsiveness, I presume that nightmare has much higher timer rate (so it takes longer to evaluate and scale up). One can compensate with lowering go high speed like parameters. Regarding scaling down, it is probably not so much governor related, but depends more on parameters. Min sample time and sampling down factor at inteliactive. So if you want more aggressive scaling down, just change that from 80k to say 40.
[Galaxy S 4 i9505 Original Android Development] vt0r:
The default two_phase_freq setting is 1350 MHz for all cores, and I only bumped that down (to 1026 MHz) when the hispeed_freq was set to 1242 MHz, but now that the hispeed_freq is set to 1566 MHz, yes, I have left the two_phase_freq setting at the default 1350 MHz.

Sorry for not clarifying that before.
[Galaxy S 4 i9505 Original Android Development] babbione15:
Me too on GE.
[Galaxy S 4 i9505 Original Android Development] Gamer-king:
I'm using the TW version. My default governor is nightmare. Even with the changes applied in recent versions I have nearly the same battery life. I always had the drain with intelliactive governor even on other Kernels.
[Galaxy S 4 i9505 Original Android Development] Mystique:
Screen brightness level?
[Galaxy S 4 i9505 Original Android Development] Netuser:
Why disabling zram ?
[Galaxy S 4 i9505 Original Android Development] Gamer-king:
I'm using lux to control screen brightness.
[Galaxy S 4 i9505 Original Android Development] !crazy:
The question would be why enabling it at all, on system with 2 GB of RAM?

Im not saying it is useless, or that ZRAM has to be off, but it depends on the way one is using its device, and one has to know precisely what to expect from it. It won't improve performance magically just like that, or at all, or it will even make things slower.

IMO most of users do not need it. And users who could benefit from it, may not succeed in doing so, because of the system configuration. For example, low memory kill, OOM or whatever jumps in and removes apps from the memory before they are swapped out, or with aggressive vm.swappiness value pages will be swapped out even if there is no need for that, so instead to enjoy the speed of RAM, and using the full potential of device, one forces it to compress things unnecessary (that takes time), even those which cannot be compressed or at very small percentage, than to emulate a swap partition and to do everything people were running from.

Only case that comes to my mind now, where ZRAM could be useful us if one uses multitasking A LOT. And here one has to tinker and think about ZRAM, and system (all things which interact with ZRAM) configuration in order to see some real benefit from it.

That being said, I'm glad we have the opportunity to use it ☺, I'm using it sometimes, and I'm thankful to our kernel dev for it.
[Galaxy S 4 i9505 Original Android Development] Netuser:
Thanks [MENTION=4387505]!crazy[/MENTION] for this useful info :)

I have another question. On my secured lock screen when I awake my screen and want to enter PIN it is very lagy and take a some time to register what digit I pressed. Is there any setting that allow me to have smooth lag free pin unlock ?

For now I am using intelliactive governer

Thanks
[Galaxy S 4 i9505 Original Android Development] !crazy:
Try changing scheduler. Try cfq, bfq, noon, but others too. Do you have external sdcard? Such lag could be caused by IO operations, and having a slow sdcard can just make things worse. The first two schedulers I mentioned do not provide so great throughout, but should help with such issues. Noop is the simplest of all, and in general good option for non rotating storage, so you could try that also, but others are worth trying too.

You could also try removing sdcard just to check if that helps.
[Galaxy S 4 i9505 Original Android Development] Netuser:
Thanks will try all these options to see what works betters.

I do have external SD card it is class 10 extreme.
[Galaxy S 4 i9505 Original Android Development] MatteoB92:
For I/O operations, I suggest him FIOPS or ROW, and than ZEN, I've ordered them for best performance
[Galaxy S 4 i9505 Original Android Development] !crazy:
The question is what are 'performance'. It is not always important to achieve the highest possible throughput. Read a bit about bfq, cfq (there is a reason Google uses cfq, is there?) and you'll understand what I'm talking about. You should also consider his issue as relevant parameter. How would ROW help if blocking happens while writing stuff to slow external sdcard? It will only make the situation worse.

That being said, it is still possible that one of governors you mentioned will work best for him, and that's why I have suggested him to try all, and see if any of those will make his problem less serious.
[Galaxy S 4 i9505 Original Android Development] MatteoB92:
I can agree in part with you, but if I choose an UHS probably I'll have an external microSD faster than internal memory
[Galaxy S 4 i9505 Original Android Development] gerardo87:
Released new toolchain ?
[Galaxy S 4 i9505 Original Android Development] Mystique:
(android@gpe) (gcc version 4.9.3 20141031 (prerelease) (crosstool-NG linaro-1.13.1+bzr2709 - Linaro GCC 2014.11 - Cortex-A15) ) SMP PREEMPT

This one?
[Galaxy S 4 i9505 Original Android Development] Solace50:
1.2.1 still suffers the same stability issues as 1.2.0 1.1.9 is unaffected unless voltage control was never operational in that build.

the crashes on boot are not standard RR's due to some minor issue, they are related to improper voltage settings of which nothing has changed between 1.1.9 and 1.2.1 settings wise and the former was running months + stable.
[Galaxy S 4 i9505 Original Android Development] mjnmd54:
i seem to be getting battery drain with the latest TW version. guys what do you suggest a version that has better battery life and settings please.
[Galaxy S 4 i9505 Original Android Development] ricardofago:
Voltage control works fine for me on v1.2.1 (-75mV for all frequencies) and my stock voltages are detected fine (check the *.ggy files in /data/.googymax3/) according to my PVS. On v1.2.0 voltage control was actually messed up (something related to GPU, I think, discussed a few pages ago). Voltage control on v1.1.9 also works fine but is based on default voltages.
[Galaxy S 4 i9505 Original Android Development] Mystique:
Solace50

If you boot up whatever version you feel worked the best. Do that and capture what the UV was that you felt was stable for you.

Then bit into the new one and match the numbers..

Your goal is to end up in the same place but you are starting off somewhere else..
[Galaxy S 4 i9505 Original Android Development] VelosCohagen:
For me on Imperium ROM v14, tw version 1.2.1 runs without issues. :)

Gesendet von meinem GT-I9505 mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] Solace50:
amongst every revision using ktoonz kernel and fauxes + many others never have i ever needed to adjust my undervoltage for any given reason changing between revisions. the initial settings are "stable" and been benched properly. nothing has changed other then the kernel revision with the new "delta" change which i would have to assume has some issues with applying the correct voltage based off default delta values being inaccurate somewhere. the only other way such crashes would be occuring is something like the memory timings in the ram were tweaked causing simular hardware failure. its not about where i want to start and end, its a fact that the current revision contains an issue of which i cannot provide a log for and is related to the recent change around the voltage.
[Galaxy S 4 i9505 Original Android Development] ricardofago:
The reason why you didn't need to adjust them between revisions is because the revisions used the same voltage computation system. From v1.1.9 to 1.2.1, [MENTION=1897326]googy_anas[/MENTION] changed the voltage management, so you need to work out your settings. You don't need to change your voltages, you need to adjust your parameters to reach the same voltages as before. If you don't want to do that either stick to v1.1.9 or take it easier on undervolting.

Are you sure you computed the proper deltas to reach your previously stable settings? On v1.1.9, undervolting was computed using predefined default voltages (I don't remember them but you can check it on STweaks while on v1.1.9), now, on v1.2.1, STweaks asks your device for its default voltages and writes them into the *.ggy files (one for CPU and one for GPU). Then, when you enable undervolting, it applies the selected delta over the respective entry on the *.ggy file and update the voltage with the result.

So, basicaly, you have to find out what is the difference of your chosen voltages at v1.1.9 and the voltages that v1.2.1 detects for your device. This is your stable delta. I can assure you undervolting works properly on v1.2.1, I have heavy deltas on both CPU and GPU.

P.S: Do you have a backup of your profile or do you know what voltages were stable for you at v1.1.9? If so, please post the contents of /data/.googymax3/vdd_levels.ggy and /data/.googymax3/GPU_mV_table.ggy and we can check the deltas for you.
[Galaxy S 4 i9505 Original Android Development] gjergji1:
I have a sound problem on the latest version.

There sound is "screeching", expecially on ringtones..

if I change kernel it all goes away.. Omega 38.1

Any fix?

Also anyone notice that with the latest fauxsound 3.5 there is no difference when changing profiles in fauxsound app?
[Galaxy S 4 i9505 Original Android Development] Mystique:
[MENTION=4176798]Solace50[/MENTION]

119 and below were based on the values Googy had in his device.

120 and newer bases on your device values. (My 9505G has different value than my wife's AT&T device both are different than Googy 119 values)

So I apply a -50 to my phone and a few -25 and some -12.5 on my wife's device.

We have now ended up where UV was stable for us in 119.

YMMV

I sat on an adb shell console looking at sysfs to figure mine out..

---------- Post added at 03:50 PM ---------- Previous post was at 03:47 PM ----------

@gjergji1

What flavor and what ROM?

Have you changed the volumes in stweaks?

Does it happen with headphones? Or only the device speaker?
[Galaxy S 4 i9505 Original Android Development] Chaitanyapatel8880:
Hi googy... Are you to support GS5 any time?....... GOD I MISS YOUR KERNEL.....
[Galaxy S 4 i9505 Original Android Development] AoEKiller:
Seriously I'm using v4android for almsot 18 months and this kernel break sound since v1.0. When the op said he would stop development, I didn't care really much because he always denied the fact that his kernel break sound. In september, I didn't understand why nightmare gouvernor was patched because it is so outdated, and this kernel dropped O/C for a device which is 2 years old. Seriously I don't understand why someone would use this, because if your device is rooted, I guess you want to run your device at 2.3 Ghz especially when you can actually remplace your battery. This kernel is a stock kernel with sound library messed up but nobody seem to care until Lolipop get realeased, this kernel and Alcuard are the only option you have but personally I would stick with rom before september 1st and wait until Lolipop.
[Galaxy S 4 i9505 Original Android Development] radz_:
No issues for sounds here.

When you say the sounds is breaking you mean the phone speaker or headphone?

If your using V4A and tweak for loud sound for speaker of course the phone speaker will break because it cant take the loud volume anymore, remember its just a small speaker at the back of your phone...

Im using V4A too and no issues for me eversince! If its breaking for you off course you can adjust the volume in stweaks!

The speaker default volume in stweaks is 45 i always set it 40 for speaker so i can add tweaks in V4A...

If its breaking you can always adjust bro..

Dont just say Sound library is messed up specially when you are the only one or 2 having this issues..
[Galaxy S 4 i9505 Original Android Development] Mystique:
[MENTION=5775877]AoEKiller[/MENTION]

Is v4android Viper or something else?

Are you looking to fix a problem, or something else?
[Galaxy S 4 i9505 Original Android Development] ricardofago:
V4A always worked out of the box for most of us with this kernel, and I didn't even change the audio options on STweaks, so you should watch out your words before saying rude things, specially to a developer that is delivering you personal work for free. It becomes incredibly hard to help you when you don't even detail your settings. Patchs happen because bugs happen and there is no software development without bugs. OC was dropped as a community choice because it is tricky for a device like ours with many different binnings and PVSs, causing many people like you (who don't do their homework) to come to development threads and blindly blame developers for such experimental and empirical problems that have been explained many times. 75% of the users dropped OC (and I can assure you most of use don't even miss it, my device is actually UC) because they found out way better reasons to use this kernel. This is not a stock kernel, and it is updated regularly, not because the developer needs to care, but because he has chosen to.

As you said, this a 2 years old phone that is still alive mostly because of people like [MENTION=1897326]googy_anas[/MENTION], but most people are not able to perform miracles. If you need more, I'm sure you'll find a more suitable device. However, look out for your choice, angry users have reported that devices like the DynaTAC haven't been receiving much attention from developers nowadays.
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
Oh thank you. I love you too ...

Envoyé depuis mon GT-I9505
[Galaxy S 4 i9505 Original Android Development] davtse:
Another user who blames his ignorance on the developer. At least get your facts right before mud-slinging. Otherwise you just look plain stupid.