yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] lawyer_06:
Hi [MENTION=1897326]googy_anas[/MENTION];

I trust your knowledge about kernel developement, so i want to ask you something related with kernel improvements..

There is a Kernel in S4 i9500 section named "Perseus" and has been developed by @AndreiLux .. When i was researching about how to get a good battery life, i saw in a thread some screenshots from that kernel and i saw it has a perfect standby and screen on time statistics.. That kernel is very old and i think it is discontinued and not being supported by its developer for the moment..

(You can find the screenshots that i have mentioned, from here => http://xdaforums.com/showpost.php?p=42078650&postcount=333 )

(You can find Perseus Kernel's main thread from here => http://xdaforums.com/show....php?t=2272602 )

As it can be seen on the mentioned thread, with that kernel it can be reached to "1 day 8 hour 40 min" standby time and "8 hour 15 min" screen on time.. I have never reached to 8 hour screen on time till now.. My record is 6 hours 27 minutes screen on time..

So, i want to ask you if it is possible to work on this Kernel and implement it for S4 i9505 model phones? I know i9500 and i9505 have different processors but i wonder if it is possible to take that kernel's main structure/features or not? If you can implement that kernel to i9505 model phones i think we will have an indispensable Kernel from you.. :) During your Kernel updates maybe this information can be useful for you, so i shared with you.. ;)

(If googy_anas is busy at the moment and if he is not able to write something related to this topic, @!crazy or anyone who has enough knowledge about kernel developement can say something related to this topic. I mentioned [MENTION=4387505]!crazy[/MENTION] especially because i see he is aware of kernel developement..) :)

Thanks in advance..
[Galaxy S 4 i9505 Original Android Development] ricardofago:
Well, I don't know much about kernels but there are lots of factors, for example, the I9500 doesn't have 4G radio or modules, which saves a lot of power. However, 8h SOT is an impressive mark. I haven't followed your links yet but are they on stock battery? It's impressive not only for us, it's impressive for all smartphone users... I'll pray for the best here.

:highfive:
[Galaxy S 4 i9505 Original Android Development] lawyer_06:
As i know it is stock battery, but i am not sure exactly..
[Galaxy S 4 i9505 Original Android Development] !crazy:
Not only that i9500 and i9505 phones are different but every i9505 is different, and same for i9500. That is b/c of the way processor/chips are made. They do a batch of them, every single is different. They target a particular procesor type, but cannot manage silicon so precisely IIRC so the differences can be huge. This is the reason why OC works so well for some people, and for some it doesn't.

They will test the whole batch only to specific, before decided values, and they won't try to check the maximum every peace can achieve (to much resources are needed, and how would they sold this? Instead of 4 different procesor type, they would have 400. Because of similar reason one can buy processors with 3 cores, or five etc.).

Similar happens with batteries etc.

Now consider different usage habits. Some people stay at home whole day, don't have a single account syncing with email, G+, Twitter, and read a text at almost minimum display brightness.

I have 3 accounts active, + two mores which are active only sometimes. Only one is my private account. Besides I sync G+, twitter, weather, Now, have location enabled, don't do a lot of gaming, but I do a lot of multitasking, I use navigation, stream media over Bluetooth in a car, browse a lot Internet, test new stuff etc. My battery on screen time was NEVER 8 hours with PERSEUS kernel. And if you rear a bit you will find people reporting same for this, and every other kernel put there.

---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------

People, just for info. I was always thinking C3 works well with this kernel, and performance governor would do well. Well, I'm running performance for third day today, and I must say I like my phone better now.

Maybe it is not for everyone, but I get around 4 hours on screen time, with original battery, two years old IIRC.

No difference comparing it with other governors, but I always tuned more for performance but not extremely.

So try running performance, but make sure C3 state is working cat /sys/devices/system/cpu/cpu0/cpuidle/state3/usage

If not try enabling it, and disabling it. It is easiest if you have faux clock app, if not you'll find a file in the same folder a a level above of the one I just mentioned.
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
I sincerely appreciate your kind attention.

Andreilux was and is still one of the best devs around and I have been following his work since googymax1 !

Even if i9500 is a different world compared to i9505, I was still having a look at his work frequently but as of now, there's nothing spectacular to expect from trying to port a lot of it to my kernel.

You think I didn't try ? Wrong ! I did a lot of research and experiments (porting, rebasing, even upgrading to 3.17... etc) but you can't know that as I only share with you what's best for me and you ! I don't want to push the users to use highly experimental unstable cutting edge kernel.

About screen on time, it's highly relative to a lot of things, not only kernel (usage, network coverage, rom, settings, apps, push service, active features, revision of phone, age and quality of battery/charger, brightness, revision of screen, even ambient temperature...). So comparing screen on time only without having EXACTLY the same conditions isn't the best thing to do ;)

Envoyé depuis mon GT-I9505
[Galaxy S 4 i9505 Original Android Development] romskii:
It's not the first time I'm reading about people asking for better battery life.

Some don't remember that getting a better battery life is really easy but you'll loose a lot performance and so on.

If you really want a great battery life I can tell you, buy a Nokia 130 for example. Battery life around 6 weeks. Maybe 8 days screen on or more. Try it. I'm happy with my second device
[Galaxy S 4 i9505 Original Android Development] lawyer_06:
Yes, i am a bit aware of what factors effects the screen on time.. :) I have also researched many threads to get a better battery life. And i have a tutorial about "How to get a better battery life?"

(The link of my tutorial => http://xdaforums.com/showthread.php?p=54836915)

But as i mentioned in my previous post, with less wi-fi usage, with minimum screen brightness and with no syncing and with minimum wakelocks my best battery life is "6 hours 27 minutes".. I have never reached 8+ hours SOT despite all my attempts to get more SOT.. :) I am a bit interested with this topic so 8+ hours looks very impressive for me.. And i haven never seen such a SOT on S4 phones except that one untill now.. So i decided to ask this point to you to learn what is the tip in this topic.. :)

Thanks..
[Galaxy S 4 i9505 Original Android Development] AoEKiller:
Why don't you help that guy who's having sound issue instead? Because he's experiencing a problem many of us had since early release. I'm sorry about my comments about o/c. If community prefer u/c device then I understand why your development goes in that direction. The issue I had with your kernel + Viper4Droid was a serious lack of bass compared to other kernel and fauxsound never worked as expected but maybe I guess no one listen music with headphones on their smartphone.

---------- Post added at 07:24 PM ---------- Previous post was at 07:15 PM ----------

Ignoring sound issue as a developer, is ignorance. I would definitely use this kernel but with an older rom. Just saying thank you googy everything works w/o flaws won't make this kernel better.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Wtf is that? Won't make the kernel better? It is not supposed to make the kernel better. It is a guest of thankfulness to the guy who spends his time and hives people great stuff for free! You don't like it? Don't use it! His time is his, and looking at the your issue with sound, you should be the one who should spend your own time in fixing it. You can't? Well that stupid you can't be, and there are lot of different things one could do to help solving the issue. But lazy and not ready to spend hundreds of hours on that.. Probably.

He has also done some things better than other devs, like porting inteliactive.

Also considering sound, I didn't notice any issues with it. I primarily use Bluetooth, and headphones sometimes and I have never noticed a problem.
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
I'm still loving you...

The sound engine is not broken ! To say that is also ignorance. If you take a look at the core of faux sound engine you'll see that it's just like an interface to take control of various sound levels (headphones, mic, poweramp, ....etc).

What's different in my settings is the increased default levels predefined in stweaks.

Fauxapp problems are because I modded some left/right controls to be as one control and use balance control.

I do listen heavily to music on poweramp without any additional mod and I am personally happy (which is my first goal) with the actual sound quality.

PS: no one forces you to thank me BUT I am forced to thank you for helping me learn to know this huge variety of people.

PS2: when you want to help improve the kernel, why didn't you give proper informations about your rom, kernel version, mod version, various sound levels, stweaks settings, apps giving problem, apps tried, .... instead of stating that the kernel is useless, the dev is ignorant, you didn't care about the dev leaving and that you don't understand why all those (stupid?) people like it (without necessarily thanking me) ???

Envoyé depuis mon GT-I9505
[Galaxy S 4 i9505 Original Android Development] !crazy:
Yes, some batteries are better and have greater capacity, even if they are sold under the same model as the weaker ones. Than again repeat the store about mpu, which can be more battery friendly, than radio/baseband, WiFi signals. You don't notice that, but not every setup is same, and in some places in your house you get more noice, other people can have in general better device at their homes, together with Better everything we mentioned, including Wireless card.

Some people even buy new bigger battery and report SOT without mentioning it.

So, nothing to do with Perseus kernel. Same stories are to be found in almost all kernel related threads.
[Galaxy S 4 i9505 Original Android Development] dclarkg:
Someone ran out of meds haha. Why don't you do your homework and learn how to develop your own awesome private perfect kernel and stop bugging the dev? You don't even know how to do a problem report haha.
[Galaxy S 4 i9505 Original Android Development] lawyer_06:
Yes, i understand you and i respect and trust your knowledge.. But could you able to look at the screenshots of the battery statistics that i have mentioned? (From here => http://xdaforums.com/showpost.php?p=42078650&postcount=333 ) The screenshot has been shared by AndreiLux himself, not by any other one.. And in screenshots (in first picture) there is an interesting situation as i noticed. According to the first graphic and from the infos at the bottom, we can see that wi-fi is always on and sometimes when the "

screen is on but the phone doesn't seem awake

".. How can this case be? How can a phone not be awake when the screen is on? I didn't understand this point..

Besides this, as i mentioned before, what i have done i couldn't go beyond 6+ hours screen on time.. But the statistics we are talking about has 8 hours 15 minutes screen on time, so the the difference between our SOT is near 2 hours. And if we think that some members just get max 2-3 hours SOT, is this difference not so huge? So, can this difference be explained

just

with the points you have stated (or should it be something more)? And i want to give a note; my battery is not even one years old..

Thanks..

Kind regards..
[Galaxy S 4 i9505 Original Android Development] AoEKiller:
Googy I have much respect for you than you think, when I said your kernel was useless it just because all your effort will be obsolete in maybe 2 months because we may have an updated to 5.0 faster than we think. But don't thank me because atm you develop for only a small group of people, those who didn't know that all you really need is a spare battery. Under volting a device bring instability but if this is what community decided then good luck for future development. I'm out.
[Galaxy S 4 i9505 Original Android Development] !crazy:
All this claims like UV, or OC cause instability are so general, silly and pointless, despite being <b>true</b>.

So what if they bring instability?

First it is NOT ducking true that the both mentioned have to cause instability! It depends on how much, and on hardware, can it handle. From your point of view you see UV, but the chip has its own specs, not the written one, but the real one. Chip producers do not have time to do extensive tests for every peace they produce. They just check if it satisfies the ones they though it probably will, and that's it.

But WE tinkers, geeks, people who like to try stuff and experiment do.

Further it is not dangerous. If I am going to get 3 minutes more battery in two days because I UV for 70 mV so be it. But some people will be able to UV much more! So it is not only about me.

You are not forced to do that? Giving an option to people is great, while doing that what he likes, what for he has time, what he can.

People say the same for OC, or they could. Instead of buy a new battery, but a new device! Just like that, b/c I say so.

I am thankful to people who make OC of grouper possible, b/c instead of having device which runs on 1.3 GHz CPU, < 400 MHz GPU I have device which runs 1.7 GHz / 660 stable as steam loc. And I know only one other person (not in person, but on xda) who has grouper able to run 1.7 on GHz. This what I have now thanks to these people, and what I had before doing OC are two different devices. This is not about UV but same logic applies. If you think OC offers more, well not to people who don't need/use this performance. Besides let the man do what makes him happy. Your talk about few users who use his kernel even if it is true, means nothing. Currently his kernel is probably the most popular, custom one for this device. So no matter what he does it will not make more people buy S4.
[Galaxy S 4 i9505 Original Android Development] davtse:
Wow. Such a beautiful display of respect. If only you made sense.

How much does it cost to buy a new battery? How much does it cost to flash a kernel?

Don't like flashing kernels? What are you doing on XDA then? Isn't this community all about experimenting with our devices and making them perform better? No?

As always I tell everyone to beware of the new poster who has contributed nothing but criticized so much. Beware the troll.
[Galaxy S 4 i9505 Original Android Development] ricardofago:
Jesus, what the hell is wrong with you? We offered you help but you don't even deserve it. You've been whining all day for a sound problem you brought to yourself, you've been rude to one of the most respected members of this development community, you've been imposing your needs when actually a hundred people voted to drop OC but you still haven't done the only thing you should have: providing useful details about your problem and your setup.

We may have Lollipop tomorrow and it will still be worth it. This kernel has been ruling for a long time and it is a joy to be part of it and its community. The Galaxy S4 will be dead soon. Were Samsung efforts useless? They surely disagree. Do you dare to know what we need? Sorry, but I don't need a spare battery at all. I don't need a few more MHz on my phone. I don't need a quantum computer. Please go sit in the corner and take a new look at life before life leaves you behind.

Sorry [MENTION=1897326]googy_anas[/MENTION] and the others for this post, you are truly polite and I know this is the kind of post you'd disapprove but I felt like this should be said. Maybe this guy just wants the attention, I don't know, I can't even understand what goes through his head. Anyway, enough of this for me, I don't wanna taint this thread any further. As a telecommunications engineer, it's a huge satisfaction to share this forum with most of you. Thanks guys. Let's move on to meaningul people and meaningful things. Tomorrow I'll start my tests with intelliactive, for now I was comparing mpdecision and autohotplug on darkness but I didn't notice much difference (even though I had the impression that autohotplug is slightly lighter, but couldn't get any conclusive numbers or technical research to verify it). Anyone wants to share personal thoughts about it?
[Galaxy S 4 i9505 Original Android Development] Chaitanyapatel8880:
[MENTION=5775877]AoEKiller[/MENTION] your name really suits you... "killer". I am following his kernel since s3 and I had these problems in kernels but they are easy to solve by your self if you do some tweaking with kernel settings and v4a settings. But let me guess... All you like is to complain rather than solving the problem.
[Galaxy S 4 i9505 Original Android Development] !crazy:
[MENTION=3137143]ricardofago[/MENTION] how do you enable auto hotplug on this kernel?
[Galaxy S 4 i9505 Original Android Development] ricardofago:
I don't recall the exact option but next to the CPU settings on STweaks you can set the hotplug mechanism (a choice between show-p1984's mpdecision and Thalamus' autohotplug). mpdecision is the defult but I've been trying to evaluate it, as nowadays we have smarter governors doing what mpdecision may be doing as well. I couldn't find details about them but it seems that mpdecision is more stateful. I've been inclined to autohotplug but I still have to test it under heavy usage.
[Galaxy S 4 i9505 Original Android Development] !crazy:
I presume that could be an option for TW kernel, but I see no such option in Googy STweaks with CM version of the kernel.
[Galaxy S 4 i9505 Original Android Development] Mystique:
I believe this is the setting?
[Galaxy S 4 i9505 Original Android Development] ricardofago:
Well, it is here on GE v1.2.1. Not sure about CM, haven't been able to use it since CM reworked the base code on October and 2G got unrecognized for my carrier.

Bingo! Damn, faster than me while I was trying to find a host to my screenshot. The option has been around for a while though, no idea why it's myssing on CM.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Thanks both, but I don't have the option. Possible reasons are, I am on 1.20 and for now, until there is a good reason I will stay on it, because an option googy introduced in 1.20, and removed in 1.21 (something like ARCH POWER, or similar) works well for me, and my battery definitely feels but better (in hundred percent sure it didn't got worse, and 80% sure it is better, but haven't done any real tests.),

and second thing that comes to my mind is that I use CM...
[Galaxy S 4 i9505 Original Android Development] gjergji1:
Just to be clear, rom version Omega 38.1, and Omega 39.

No modifications in the kernel.

I do not use Viper sound.
[Galaxy S 4 i9505 Original Android Development] Mystique:
[MENTION=1293833]richardo[/MENTION]fAgo

I find hot plug to be very performance based at the expense of battery life.

Many people find longevity in msm mpdec and nightmare for maximum longevity.

I find that intelliactive with msm mpdec gives better longevity when you are interacting with your device.. web, text, yt, and others whereas waze and other constantly adapting applications seem to not spike and fall over and over like other governors..

I ignorantly am looking for something for which I have no answer..

If you need 1.2Ghz what is more effective: 4 cores at 384 or 1 core @1.2 or 2@702..

And all those variables and their respective variances in between..

:)

That is why kernel tuning is so difficult thing..

If we all agreed on what we were looking for we could have that answer and have far fewer posts to read and comment on..

My 0.02
[Galaxy S 4 i9505 Original Android Development] dr.wtf:
if you choose between the first two then 1 core @1.2. you cant parallelize certain tasks. on those your higher clocked single-core would perform better while parallel tasks can be handled equally effective by a scheduler.
[Galaxy S 4 i9505 Original Android Development] !crazy:
I have noticed some wireless related processes (like dhd_dpc, dhd_rfx...) topping tasks lists, like top, or whatever, and my wireless connection is not that great despite me having not that bad Asus Wireless access point, which usually didn't have issues with covering my apartment...

If I choose only 5 GHz it works better, but that is not always option. For example a few hours ago, when I was out in a shopping center, I had to use mobile network what is not a big deal, but I would like to save battery of course by using Wireless.

Anyone noticed any issues (like weak signal, throughput, problems with establishing connection or anything.) with this kernel, or with 1.20 version?

---------- Post added at 11:48 PM ---------- Previous post was at 11:11 PM ----------

Sorry, forget top, processes were among the active b/c some photos and videos were uploading to Photos / G+.

But the rest of my issue with wireless networking (connecting, doesn't work, slow.) remain...
[Galaxy S 4 i9505 Original Android Development] DaReDeViL:
Oh maaan, I nearly had a heart attack!

I didn't touch/change wifi since ages. Is your modem up-to-date?

Envoyé depuis mon GT-I9505
[Galaxy S 4 i9505 Original Android Development] DasXardas:
CPU and GPU OC?

When the CPU and GPU overclock/underclock will be enabled? :) and XXUGNJ8 is the latest. Or not? :)
[Galaxy S 4 i9505 Original Android Development] davtse:
Been through this many times before. Overclock will not be enabled.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Yes it is. Asus still maintains RT N56U. Last patched firmware was released about a week ago. But that again who knows, it can be indeed a bug in the firmware. I'm not sure how much could something like this be caused by noice and interference with other access points, and there are a lot of them here. The reception and network got better after I switched to 5 GHz only mode. But now when I'm out, I forgot about that, and than I wonder how only my device is not able to connect to public hot spots in shopping center etc ☺(b/c it only scans for 5 GHz, and there are no such public networks around).
[Galaxy S 4 i9505 Original Android Development] lawyer_06:
Hi @!crazy;

Thanks for the informations you are sharing with community.. In the topic we were talking about, i asked a question in my last previous post, but i think you didn't recognize that question.. :) (The link of that post => http://xdaforums.com/showpost.php?p=57095620&postcount=2539) So i am asking it again, because i really want to learn its answer. And i think lots of members on this forum want to learn its answer. If you inform us about this topic i will be glad.. :) The question was:

How can a phone's screen be on, but that phone doesn't be awake?

Thanks in advance..