yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Thank you Anderi for response and for the information. (Recomendation of 3DMark did help)

Andrei, fantastic, fantastic work!!! With your kernel, undervolting the GPU as well as CPU, and setting the frequency range to 100MHz-1200MHz, as well as using the "Velis Automatic brightness tool" I was able to get almost 80 minutes of screen time till my battery level dropped from 100% to 90%. Simply amazing. I'm gonna leave the phone for the whole day today, and see how much it wille get till the battery level drops to 1-5%. Just to make things straight, I did it only for test purposes, so I barely touched the phone. Just laied down the phone, and left the screen on the whole time on the same screen (battert settings screen).

Ofcourse the fact the screen is left on the dark theme (battery setting) and most pixels are turned off (AMOLED) helps out but still, incredible. Absolutely incredible. 80 minutes for just 10% of the battery. Kinda makes it funny now, remembering those "tests" when people said how snapdragon has so much better battery drainage level.

A side question to anybody. I installed beforehand a lightweight cpu monitor app that displays the cpu frequency in the notification bar, and for like 1.3 hours since I left the phone alone, the cpu frequency showed 100MHz most of the time when I looked at it (some spikes when the phone did synchronization, or new email arrived), but after that point it suddenly went to 800MHz and stayed there. I thought that maybe the cpu monitor got broken and throttled the CPU, but when I installed other app that could show me the cpu frequency, it showed the exactly same thing.

I got lucky though, and by a fluke I found out that the settings app that I left the screen on, being left in the running apps was the culprit. When I removed it with the app manager, the cpu frequency went down immidietly to 0.1 GHz and stayed there.

Any of you know if this is some bug of the 4.2.2 Android, or maybe it's something new and unknown? I'm asking, because with this, to keep the phone idle at that great 100MHz frequency, I will have to hard close the settings app whenever I leave it (kinda pain in the ass).

...

Sorry to repeat myself, but would anybody who does this mind answering my previous question?

4) I see some people underclocking the max frequency of A15 to 1.2 GHz (for example), but overclock the max frequency for A7 to (I see a general rule, as many say 750MHz is unstable) 700MHz from 600MHz. My problem with understanding this, is that underclocking obviously is going to help with the battery drain, but when I see "overclocking" I instantly think (bigger battery drain). How overclocking (in this mix) comes into the overal picture? Is it also (by some way) helping with the battery drain in the long run?
[Galaxy S 4 i9500 Original Android Development] mw86:
This pic is of a post from this thread. As you see you could likely clock a7 to 700mhz and it still should draw less power than a15 800mhz. I hope this answers your question. As well it should help keep you from scaling over 700mhz a7 as easily since scaling is load based and that frequency is stronger it will take a stronger load to scale up than 600mhz a7 would have.

On rare occasion I have had same thing. Example ive used terminal and left it in recents in background and my cpu stayed at 400mhz minimum much like you see upon a screen touch or the 600mhz you see pressing back button or menu for example. This is no glitch. It is related to qos services and is meant to keep a certain performance level minimum when certain stuff is detected like the light load you know of, of the other app you had that did this to you. Just keep closing such apps is all. It's not really a glitch. If you hold your finger to the screen you may notice it doesn't drop below 400mhz. It helps overall keep the fluid feel of the ui by keeping under interactive conditions the minimum mhz above the normal minimum be it 200-500mhz a7 (100-250 half clocks)
[Galaxy S 4 i9500 Original Android Development] Anakha56:
[MENTION=4745870]mw86[/MENTION] thanks for the read. To get a better understanding of what you posted I went and found the start of the conversation over here: http://xdaforums.com/showthread.php?t=2272602&page=148 . Again thanks for the info :).
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Thanks a lot, makes sense.

I also saw Andrei saying, it's not good to try to overclock it even to 750MHz, as it's better for CPU management, to have this one step (750MHz between 700MHz A7 and 800MHz A15) unused.

I guess that's beside the fact it's unstable for more chips to use 750MHz is the reason most guys don't use it.

Yes, I know about the tap frequency, I noticed it too. Also, the background apps is understandable, when some apps need a frequency high enough. By that token, it would be fine here, if the settings screen was taking 800MHz from the get go, but it's stable at 0.1GHz for over an hour, and then suddenly it spikes to 800MHz. I don't think that's normal.

Also, one more piece of information. It happened again, and I noticed it happened only when I took a screenshot(s), with the palm thing. Probably some bug with either a samsung's gesture service, or maybe google.

//Edit

Doesn't happen all the time. In fact it doesn't happen most of the time, I only got it twice. I guess it's some very rare bug. I don't want to spam the thread, so let's ignore it, no big deal, now that I use frequency monitor in statusbar.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
I don't remember ever saying that. Use 750 if it's stable for you.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
@Up

Oh, I applogies Andrei. I was reffering to this response of yours:

To be specific, this part: "Keep in mind that you do _not_ want to have a perfect frequency table and jumps should be there for DVFS's sake."

I guess I misunderstood you (not a hardware/kernel developer myself, rather software one, so my knoledge is very limited here). Again, my appologies and I stand corrected.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
When I saw Andrei officialy announcing he will be doing his kernel strictly for i9500 I knew at that time which version I will be getting, and boy I'm not regretting it one bunch.

I was close to get to Andrei's mark (12 hours screen on time), probably would get there if I used wifi, and left other things, as well as finding why cpustats took so much of battery, but no biggie. This is not a place for childlish competition play. Besides, from what Andrei said, he was using his phone normaly at this point, so that's door closed haha.

Anyways, here's my report using:

- limiting CPU frequency to 100MHz - 1.2GHz

- overclocking the A7's to 0.7GHz

- undervolting all CPU frequencies, the A7's mostly by 100mV, the A15 mostly by 75mV

- undervolting the GPU frequencies

- using Velis Auto Brightness, set to "bright amoled"

- lots of bloatware removed

- not using any samsung "air" functions, or eye functions, except for the palm screenshot efect

- 3g on the whole time, wifi disabled

- auto sync on, dropsync on

- did a little browsing through the phone setting, as well as a few system applications, but aside that the phone was just laying down with the screen on the whole time

Managed to get 10.5 hours of screen on time, with the previous result of 6 hours without the overclocking/undervolting modifications, and without Velis Auto Brightness application, although with using the phone heavily while the screen was on. I think I can get to somewhere between 8 and 9 hours of screen on time with normal usage of the phone now (not just leaving the screen on), if I optimize a few things at this point.

In attachements the screens.

Again, FANTASTIC work Andrei and big thanks for doing all this amazing work..:good:

Sorry guys for a little oftopic of mine in couple last posts, I know Andrei preffer to keep things here strictly technical. I will shut up now ;), and just enjoy this phone with fantastic "tweaks" on it thanks to great kernel.

cheers
[Galaxy S 4 i9500 Original Android Development] vamsi_krishna:
A small suggestion, don't leave your phone display turned on just like that. Over a period of time, AMOLEDs displays will burn in if the display content didn't change.
[Galaxy S 4 i9500 Original Android Development] suadt:
Can someone post best audio settings in Synapse?

Thanks for this kernel.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
One tiny question to those who undervolt for a long time.

I see a lot of variety in tendencies in undervolting. Some people undervolt a lot towards lower frequencies, and go almost to default towards higher frequencies, while others do exact opposite. They almost keep default voltages in lower regions, but apply higher reductions on the high frequencies.

Is it just because the manufacturing of the chips can be so erratic, that one can be better to be treated with the "A treatment", while other better to be treated with "B treatment", or one group is (in theory) wrong, and only the other got it right?

If it's the second, can someone knoledgable, who does undervolting for a long time explain which one is the correct one? Undervolting more towards lower frequencies, or undervolting more towards higher frequencies? Or maybe it's completely relative, depending on the particular chip model?

So far I was under the impression, that at lower frequencies the cpu is very lightly strained, and hence those frequencies can be relatively undervolted a lot more, while at the same time higher frequencies put more strain on the CPU, which means it requires more stable voltage, hence the smallest amount of undervolting should be towards the higher frequencies, but I saw completely reversed chart tables, so here's my question.

Noted. Thanks. It was just for that one purpose, and I wasn't planning in repeating that anyway.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
Have you ever used a Corsair or Intel SSD? :eek:

What you do, under-volt, over-volt, no one should have a problem with that. But as I said before a person who has purchased a S4 has purchased it for it's performance, and it's cool features like 'Air' and 'Gesture', and I agree with you on one section the half or non working for me, the 'Eye' features. Now some people like to think what they are doing is the ultimate and should be followed by others. When you posted that UV'ed that much and the next user said 'why buy a S4', then you both have a point. You did what you like, the person who asked thought you might be weird, but he has point too. As some was (and you too) taking cars into comparison, well I am not a rich person but I own a A4, now would I change my B8 and downgrade to B6? Course not. Same way, why did I or one person purchase the S4? For me it was the Quad Core 1.6 GHz CPU and some of the Air and Gesture features, which you called as ****. And I use them so often, when I am driving the Air call accept, for taking a screenshot the palm swipe and all, if those eye features worked I would have used them so happily. You seem to be a Samsung fanboy, and I don't have a problem with that. I buy a product looking at the product, not the brand, so I will never buy a Samsung SSD, I will never buy a Samsung A.C or even T.V etc etc. Honestly other than my cell phone there is not a single thing in my house which is Samsung! Because the goods I have and when I purchased them, I found the other brands 'better' than Samsung. Now the term 'better' might differ to you, as it varies to each person. But there is a general standard.

So to make it short, that person who questioned you, that was a very valid query, and no offense I agree with him (if I were to use my S4 as a 1.2 GHz unit with lots of trademarked features disabled then there were so many different phones, with way better build quality and aesthetics, and especially with way less price, I simply would have bought any one of them) and then that utterly fouled reply by the OP of this topic was absolutely meaningless, which is called 'uncivilized' in my country. I don't care who he/she is, this is a community, if someone doesn't know the meaning of that please Google it. Everyone has their own opinion, and everyone should respect that.

Period.
[Galaxy S 4 i9500 Original Android Development] Degrated Shadow:
Can u guys stop going off topic? this is original dev section here. if u find discussing this interesting do this in geneal threads please.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Way to totally make a hypocrite of yourself. The whole topic got brought up BECAUSE somebody didn't respect other people's preferences. You argue the same point which I made, yet in the same post you again critique the choice of phone of those who go choose to undervolt and underclock. Who are you to decide this? What makes you certain that any person who bought the S4 did do because only of performance? You're starting your post with an ignorant statement.

Let's get technical; the i9500 was the first and only high end phone with A7 cores, the first phone with PSR, one of the first with new high capacity battery. Up until the G2 it has been one of the best battery performing phones outside of gaming.

You may have your own opinion, you're free to rationalize it however you wish. But what you're doing and what the original user who started the discussion was to dismiss the rationale of the opposing side. And that's disrespectful and a crap move.
[Galaxy S 4 i9500 Original Android Development] jujuburi:
As I have said before, cut your attitude. Every time you respond, either in an offensive way or by using third class language. Who do you think you are? This is a community site, not a potty mouth competition.

[MENTION=4438995]lukair1983[/MENTION]: Did I say you can send your own prioritize stuffs to me via PM? I don't care what you do, what's the sudden interest of everybody that they are trying to make a big deal outta themselves? Spending too much time in virtual life?
[Galaxy S 4 i9500 Original Android Development] hotheabilly:
------------------------

The arguments end here.

------------------------

Sent from my iPotato
[Galaxy S 4 i9500 Original Android Development] Alberto96:
Seems that community agrees with what AndreiLux said ;)

Stop OT now. Dont know why on galaxy s 4 threads moderators have to work so much. This never happened on Galaxy S 1 section....
[Galaxy S 4 i9500 Original Android Development] xHausx:
Please report any off-topic or inflammatory posts instead of replying to them. It makes it very difficult for us to take care of the people who need to be removed when the reactions to them are worse than the original post.

Let's please get back on topic and stay respectful from here on. This is the only warning there will be.
[Galaxy S 4 i9500 Original Android Development] maranello69:
did the new Synapse app changed the extSD scheduler? i get very high writing times when doing a online backup with no other changes

can you guys recommend some settings for a 8GB average SDCard
[Galaxy S 4 i9500 Original Android Development] gp545:
Edge Enhancement control reverts back to default with every reboot. Wiping cache, data, clean install of ROM & Kernel also didn't fix it. Guess, it's a bug or intentionally set up like that for reason may be. Can anyone confirm that?
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Bug, I'm aware of it.
[Galaxy S 4 i9500 Original Android Development] mw86:
Andrei I am very happy with the Synapse interface. Do you have plans to implement safe boot profiles like in the past in case user settings prevent boot? I am aware of the current workaround you posted for adb. I have not had any issues as a result but, I am just curious. While doing tests I crashed and upon boot all was set the same except gpu max mhz. I was setting 600/640 and it was 700. It has only happened while I was testing things so it is really not a problem. This does not happen on subsequent boots or reboots where it has been set. Only on a crash upon next boot possibly and has hindered nothing. I thought what you had in stweaks as a main profile should a failed boot be detected was incredible. Keep up the great work Andrei and don't let the kids discourage you, you put out excellent work it shows and your sub community of the niche 9500 universal 5410 shows it's support. You clearly understand what Android is all about... options. Thank you Andrei for being you.
[Galaxy S 4 i9500 Original Android Development] robertobsc:
Andrei, the way to include new options in Synapse is similar to Stweaks (just change xml + extra text files) or we must code in Java to add make it done?

Enviado de meu GT-I9500 usando o Tapatalk 2
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Wtf? Such a feature never existed.

Anyway I'm planning to do a similar detection mechanism after applying the settings on boot. Like if it's still stable after 5 minutes, it'll set it on next boot too. If it crashes within that time, it won't apply at next boot.

I did some other things for the next version, I want to get rid of kernel-side dependencies before I move onto things I can update via Play Store.

You mean create custom elements for yourself? You can edit /res/synapse/config.json but it's currently being re-generated on each boot. You can create a .patch file and let it run per init.d and patch the config file, that will make your elements persistent. I will do something else to facilitate such a function but that's far far in the future.
[Galaxy S 4 i9500 Original Android Development] mw86:
It must of been fluke lol then because I would crash on a test and next boot sometimes I'd be on main boot profile not the one I had made. I'd then paste the perseus folder back over it and reboot and be back on my settings. So i mean the aspect that if the phone failed to boot on the last settings in Stweaks it booted on the main profile. Based on what you said though i guess that was more of a corrupted file thing, my bad. :) nonetheless looking forward to what ypu have in mind.
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
10pre4 fixes the issue with the edge enhancement.

Synapse also is updated with a written-from-scratch seekbar implementation which adds some new capabilities. This now allows me to totally get rid of those fake A7 frequencies in the app. From now on we're talking in real frequencies.
[Galaxy S 4 i9500 Original Android Development] robertobsc:
Sorry Andrei, I didn't explained why I was asking that.

Me and some other few people helped Gokhan in Siyah with little contributions, our major part of them were changing the xml and text files at initramfs that were configuration files for Stweaks (you know well that) while Gokhan got more time to code instead of making that configurations.

Just guessing that it would be good for you also if you need time to code and good for people that wants to contribute to your kernel.

Enviado de meu GT-I9500 usando o Tapatalk 2
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Fantastic! We're awaiting anxiously. That will allow for the stress testing those "half frequencies".
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
The core aspect of the configuration builder remains ; I designed the draft for the XML template system for ExTweaks later STweaks, Synapse is no different in that regard other than it being JSON based.
[Galaxy S 4 i9500 Original Android Development] HassanM:
Hi friends...

Im on Omega 14.1 w/Perseus 9...

I recently noticed that at times after a boot the sounds in my phone totally go away but after a couple of reboots it comes back...

Can anyone plz shed some light on it...

Thanks in advance...
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
https://github.com/AndreiLux/Perseus-UNIVERSAL5410/issues/5
[Galaxy S 4 i9500 Original Android Development] HassanM:
[MENTION=4167023]AndreiLux[/MENTION]

Thanks alot mate...

Good luck in your upcoming work... Just for info when is Alpha 10 coming out...
[Galaxy S 4 i9500 Original Android Development] silvercat:
Its out long back..check out the link

https://github.com/AndreiLux/Perseus-UNIVERSAL5410/wiki
[Galaxy S 4 i9500 Original Android Development] HassanM:
Thanks mate... Actually I was waiting for the Alpha 10 and not the pre-release .....
[Galaxy S 4 i9500 Original Android Development] cmd512:
Pre-release is working perfectly, no reason not to flash.
[Galaxy S 4 i9500 Original Android Development] matheus_sc:
Using here and perfect.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
Just to also confirm what you guys said, using the pre4 kernel since the day Andrei posted it, no problems for me.

...

Quick question regarding PowerVR SGX544 in the context of underclocking. Does anybody know or found the power consumption of the i9500's GPU?

I found the CPU table that Andrei posted, and I was wondering if there is something similar for the GPU. I did look over the web and xda. Couldn't find anything, but it won't hurt to ask.

Just to give context. From the below listing the benefits of limiting the CPU frequency are obvious, so I was wondering if it's worth considering to limit the GPU (say from 480MHz to 350MHz), because if say PowerVR [MENTION=682170]350[/MENTION]MHz takes 10mW less than [MENTION=302803]480[/MENTION]MHz, then there is just no point for that and waste of time, but I simply don't know because I couldn't find the data. If it's on the other hand something over 100mW then it might be a different story. I could calculate the Watts myself (since we know the default voltage thanks to Andrei's kernel), but I don't know how much Amps are being pushed to the GPU at certain frequencies.

Anybody kind enough to give some help here? (if this knoledge is public to begin with)
[Galaxy S 4 i9500 Original Android Development] AndreiLux:
Not much info about that other than peak load should be around 1.5W for the GPU.
[Galaxy S 4 i9500 Original Android Development] lukair1983:
@Up

Wow, thanks a lot Andrei. Better that than nothing :)

I know it's just approximation, plus there is probably some margin error in those measurments, plus the 266 MHz step and 600 MHz step are in there somewhere, but if someone is interested and want to draw some vague conclusion, this is what I typed down from the video watching at the data:

177 MHz

0.9 V

0.005 W - 0.352 W

350 MHz

0.9V

0.423 W - ? W

480 MHz

0.9 V - 1.0 V

0.628 W - 0.794 W

533 MHz

1.0 V

0.953 W - 1.009 W

640 MHz

1.1 V

1.167 W - 2.??? W

The voltage given to us by Andrei, that is set in stock by Samsung is:

640 MHz	1137.5 mV

600 MHz	1112.5 mV

532 MHz	1087.5 mV

480 MHz	1050 mV

350 MHz	937.5 mV

266 MHz	900 mV

177 MHz	900 mV

There is a difference between the [MENTION=682170]350[/MENTION] MHz and [MENTION=302803]480[/MENTION] MHz, at full load up to 200 mW, so it is something. Not as much as the CPU which at 1.6 GHz speed can take 4 x 1.8 W, but still.

And wow, look that @640 MHz frequency go way up to 2 W. That deffinetly tells a lot :> I guess setting it anywhere between 350 MHz and 533 MHz for someone who is looking at the battery drainage will be good enough.
[Galaxy S 4 i9500 Original Android Development] lch920619x:
Power consumption varies with not only frequency, but also load... so the figures from the video might not be so valid except for the full load ones...
[Galaxy S 4 i9500 Original Android Development] lukair1983:
I'm aware of the fact those aren't completely accurate, that's why I said that if someone wants, he can draw some vague conclusions from it.

Obviously that's not perfect, but like I've said, better this than nothing.
[Galaxy S 4 i9500 Original Android Development] AladdinZ:
Been out of XDA for a while and when I get back I see alpha 10 is there :) but with a slight change which I cant seem to get working, No matter how many times I tried I cant get Synapse to work, it crashes every time I launch it, I have read the last few pages and even tried cache wipes, reboots, re-installed a couple of times as well but doesnt work for me :( Any help will be much appreciated. By the way Im still on Arrow 5 domination theme version. Flashed back to Alpha 9 since STweak support is there :(