[Galaxy S 4 i9500 Original Android Development] mw86:
I see. So by disabling twdvfsapp is it normal in Antutu for it to hit throttle 1400 but then drop to A7 max suddenly while at 100% load during the cpu test. Im trying to get Antutu to run way it seemed to on alpha 0.1

I enabled boost mode and deleted dvfsapp but it seems to hit the max mhz now but go way below 1.4ghz when it nears throttle condition. Setting my min mhz up from stock it would jump to what id set the min to randomly after the throttle started this only started after removing twdvfsapp. Yes its a shame we cant see temp at 100-200ms refresh though i believe the throttle may refresh lower?

Do you know why 1.6ghz would hit through whole antutu run if i stayed cool enough in alpha 0.1 but requires modding twdvfs to hit above 1.4 in alpha 1 and up? Do you think for just Antutu with twdvfsapp on alpha 1 is reporting thermal issue when not and its working correctly on alpha 0.1? I know cool tool refresh is a half a second which in cpu cycles is an eternity but for 3-4 seconds i was under throttle with twdvfsapp and it started runs at 1.4ghz. I am not versed in this new setup vs what phone i came from and I like to understand a lot of the way the mechanisms work and maintain system stability and workload efficiency. Im guessing this strange occurrence between alpha 0.1 and 1 is all related to Twdvfsapp.

Ill keep looking on Google for twdvfs it comes up to some links to your perseus kernel for GS3 and in links about removable apps from android. I came from a qualcomm chipset hoping to get a better experience on Samsungs Exynos. So far I feel I made a good decision as this has been one smooth phone. You have already made this phone better. I hope to learn more about this as we go.

I noticed the handling more of where temps bring stability to mhz and perhaps you can further refine the stock throttle mechanism to drop as needed and raise back as temps allow as this throttle seems very jump is it 1400/1200/1000/800/600 as temps get worse. It would be great to see 1500/1400/1300/1200/1100/1000/900/800/600 and an active attempt to raise back up as it seems it can lock on 800 or some other specific mhz and i must lower max below it apply and set my max again. This is under stress but it can be much smoother on ongoing sustained loads. The refresh rate on throttle if lowered more so its faster may catch 1800/1900mhz fast enough to make it more stable. I have surprising stability as i play with those clocks but would be better if under extreme stress it stuck to 1700 or less. Sort of turbo boost running high mhz when lighter threaded usage and full load all threads closer to the 1.6/1.7 range. I don't know from reading your thread on this chip if anything i mentioned can be manipulated to be more efficient long term you know not so up down and lock down on the throttle setup so the chip doesn't quite drop very low unless temps were obviously critical. I was sitting at 70c on some of the states of throttle for long periods like 10seconds or until load dropped altogether but at low mhz. Strangely antutu didn't handle the same with throttle on alpha 0.1 it just kept chugging at 1400mhz and wouldn't drop unless it hit throttle again and can't quite emulate the same on Alpha 1. Yet stranger thing is quadrant seems to handle proper on both alpha 0.1 and 1. I have a lot wrong I know please enlighten me. I was used to horrible qualcomm throttle and then a better replacement a nexus type throttle which was just throttle start temp, poll rate, throttle stop temp and throttle start mhz. It would drop to target mhz if at throttle start temp checked every poll rate period that passed and would raise back up next poll rate one frequency step if temp was same or under throttle stop and the throttle down after the target mhz was only one frequency step down per poll rate that was at or over throttle start temp.

Is any of the throttle target frequencies up or down tied to any on demand tunables?

I hope this is okay questions. Thanks for your answer above too Andrei.

**and i just realized fully what you mean on antutu hits throttle with dvfsapp enabled and doesn't have minimum mhz set which means 1.4ghz will stay max until exit app or workload that it would drop again to idle mhz lower than 1.4ghz. Like i told the user above that having min at 1.3ghz or less may be important if we are hitting throttle temp for a workload.