yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] robcore:
This is a test build I think some of you brave souls might enjoy. When I'm working on each release, I make my own "Next" versions of the previous release, then "proto" versions of the next release. The process usually means flashing around 5-10 kernels for each stage of testing. This is pretty much MarkTen with additional hacks to further stabilize hbm/panel, improved color quality, better battery life and performance due to some more scheduling updates. The screen looks so bloody good I couldn't pass this up.

machinex-MarkTenNext2.zip:

https://drive.google.com/file/d/0B5Wyhwt8r31ZcnVia0pDZFVZTjg/view?usp=drivesdk
[Galaxy S 4 i9505 Android Development] eilex17:
Please you can share a backup for kernel settings??
[Galaxy S 4 i9505 Android Development] devsnor:
I didn't change all that much but sure, catch.

//edit

Will do when I get back home, for some reason my attachment doesnt go through.
[Galaxy S 4 i9505 Android Development] Superperry96:
I'm running alberom 9.0 with imperium kernel (i9505), I want to know if I can flash directly this kernel removing my current stweaks before doing it or should I do a complete wipe of the telephone (I prefer doing a complete wipe than the simple factory reset/clear dalvik, cache, etc.).

Also, I want to know especially for someone who tried it if it's more/less stable than/stable like imperium and if it's performance or usage experience is ok or faster/more battery friendly than imperium.

If my questions are a bit "nooby" (is this the right term?), pardon I'm still new to custom roms and adjusting kernel for better gaming/multitasking performance.

I'm thinking of trying this kernel but I want to be convinced or have a clearer idea before doing so.
[Galaxy S 4 i9505 Android Development] Helloziro:
Please best gaming features... ( sorry my english... )
[Galaxy S 4 i9505 Android Development] robcore:
For coming from imperium, I have the instructions in the OP : )

As far as stability goes, I actually recommend the "next" version I posted a couple posts back.

When it comes to comparisons between different developers work (your Imperium questions), XDA forbids this type of conversation. Even if XDA didn't, I would rather we not out of respect for Slim, who is a great developer and person.

Read my posts in this thread, and you should find your answers regarding stability and installation, including how to switch between Imperium and machinex.
[Galaxy S 4 i9505 Android Development] robcore:
Electroactive and Elementalx governors. For everything else, just like every other linux kernel : )
[Galaxy S 4 i9505 Android Development] Superperry96:
Thanks for your answer and sorry for these maybe rude questions, I also respect anyone's effort, in primis the one's I'm trying right now for giving my phone a new life.

Anyway I'll give it a shot and see the benefits.
[Galaxy S 4 i9505 Android Development] Andycar:
Hey, I also came from Imperium, and with enough of respect to both developers I must say that I wasn't disappointed... at least[emoji6] [emoji6]

BTW, maybe you don't really need to do the full wipe, but if feel like, of course you can.

Отправлено с моего GT-I9505 через Tapatalk
[Galaxy S 4 i9505 Android Development] Tristan1302:
Really good work, fast, no big lag and good stability ;)

Just a question, did you will add CPU / GPU OC support on your kernel ?

Thanks :fingers-crossed:
[Galaxy S 4 i9505 Android Development] sonickles9:
nope (not yet)

not sure if he is willing to though, our CPUs are powerful enough tbh

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] Superperry96:
Can I adjust screen brightness in this kernel?

If yes how to do it and also I'm trying it right now and see the differences.

Edit: I noticed there is HBM but I'm not a fan of high brightness.
[Galaxy S 4 i9505 Android Development] robcore:
[MENTION=6173323]Tristan1302[/MENTION] [MENTION=6018519]sonickles9[/MENTION]

GPU OC: 99% no. I've tried a variety of higher clock speeds for this gpu and all of them have resulted in unstable or inconsistent graphics behaviour. However, this is most likely due to corresponding bandwidth/bus values that need to be modified in order to be compatible with higher kgsl speeds. Some of these modifications could be downright dangerous, so unless I can work something out down the road, this isn't going to happen. Another factor will be whether I can establish a working cpu hardlimit to act as a failsafe. All of these are my requirements for gpu OC, so there is a chance in the future but don't hold your breath.

CPU oc: With the working cpu hardlimit I now have in place, cpu oc is on my list of potential features, so long as I can implement it in a way that actually provides a stable performance boost. The versions I've tried so far haven't really shown an impressive increase in value vs battery life, but I will probably come up with something. If I do, note that two extra steps, 1998 and 2106 are probably the highest I will go.

Whether or not our cpu can handle it is even up for debate, as one could argue that our board and cpu (snapdragon 600 and krait 300, respectively) are overclocked versions of the s4 pro and its krait 300, in which case our clock speeds could represent the higher range of what our device can take. Others have suggested our cpu's are intermediary enough between krait 300-400 to be able to support a little boost. So all in all, this subject isn't definitive enough to be able to claim absolute stability with oc, but I will give it a shot when I get to it. Like anything else, I'll only release it if I'm happy with it.
[Galaxy S 4 i9505 Android Development] robcore:
HBM is purely optional of course. Beyond that, you can adjust it with the tw controls like usual. Though I think there is a framework file that you can adjust min brightness levels in somewhere (Framework-res if memory serves me correctly), so if you find that and make your min "1" instead of "10," I've lowered the corresponding values in the kernel driver to go as low as "1" instead of "10."

We should control our min and max brightness, not samsung.
[Galaxy S 4 i9505 Android Development] robcore:
For now, you can try electroactive and elementalx for performance gains, as they both hook into the gpu to provide a graphics boost.
[Galaxy S 4 i9505 Android Development] robcore:
So I just investigated (some more) the potential causes behind this bug where 1) phone is put into airplane mode, 2) phone goes to sleep 3) wake up the phone and the modem doesn't turn back on until you reboot.

The old code sucks, I'm gonna force the modem to reboot for one. Also, I fixed an issue where aborted suspends were still causing driver interrupt counters to increment. More to come. Let's see if we can take this experiment to the next level.
[Galaxy S 4 i9505 Android Development] sonickles9:
sweet :)

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] robcore:
It's so frustrating! And like the very definition of a random reboot lol.
[Galaxy S 4 i9505 Android Development] Superperry96:
I tried your new update and I want to point out some little bugs I noticed:

-It seems my wifi and lte are not displaying correctly thier incoming/outcoming transmission (even if it's working it still a noticable bug that bothers me a little bit).

-After a reboot it doesn't always save my configuration.

This kernel has potential but it need to squish some bugs.

Anyway it's a solid kernel with good performance and I would like to modify screen brightness without manually doing it.
[Galaxy S 4 i9505 Android Development] robcore:
Radio: not sure what to tell you yet.

Synapse: saves mine every time, did you update busybox on rails to 1.24 through the app?

Brightness: I don't know what you mean...?

Also please provide logs when giving bug reports.
[Galaxy S 4 i9505 Android Development] robcore:
Oh I had to reduce some word count! Which rom are you on?

Anything with "fps" is either snake-oil or just plain buggy. If you have max_events_per_second I wouldn't set it above 90, and remove the line pm.dyn.sampling.rate if you have it. Beyond that I can't say either way because I threw away build prop tweaks other than knox stuff, etc ages ago.
[Galaxy S 4 i9505 Android Development] Corduroysack:
i'm on Super Wizcyan v3. i've removed anything with fps in it and totally deleted the max_events line. luckily i backed up build.prop before changes

what about persist.sys.NV_FPSLIMIT=60
[Galaxy S 4 i9505 Android Development] VITMAD:
WIFI

Sorry about that but WiFi don't work:crying::crying:. Can anybody help me

Thanks in advance
[Galaxy S 4 i9505 Android Development] Superperry96:
I installed busybox so I don't know if that is the issue. Anyway about configuration, I noticed it saves my configuration but I have to open synapse every time in order to have benefits again because when I open it after reboot it shows the same warning as the first time I open it.

If you can implement brightness adjustment it would be good but maybe it's not probably adjustable. Also brightness is a little bit higher with this kernel when it is minimum, thats why I want to modify screen brightness.

About radio: I noticed the voice data usage in settings disappeared, because I remembered there was a voice in the settings and also I reverted my kernel to see myself the differences, maybe I should update modem+non-hlos, I'll test it later.

So far these are my problems and concern.
[Galaxy S 4 i9505 Android Development] parser:
Trying to understand smth here; HBM mode is not supposed to stick when I active it right?

When I shut the screen off it disables itself because it drains battery and screen life etc.

Did I get it right?
[Galaxy S 4 i9505 Android Development] robcore:
Brightness controls will be updated in the future, I'm only 25% through the panel project.

Data: I think i see what you mean, the little arrows don't show anything. I think I know the culprit and will have a look.

Synapse: make sure you have apply on boot ticked in the app's settings, and wait for a while after boot to see if they are applied. A toast should pop up. My settings stick perfectly...do you have busybox on rails from the play store?
[Galaxy S 4 i9505 Android Development] robcore:
Oh I think his issue is overall brightness gain. For hbm, it actually will stick until you turn it back off!
[Galaxy S 4 i9505 Android Development] parser:
Well when I turn hbm on it stays on until I shut the screen off. When I turn the screen on, the screen is hbm off. What can be the problem?
[Galaxy S 4 i9505 Android Development] robcore:
Dunno, stays on for me!
[Galaxy S 4 i9505 Android Development] Superperry96:
I installed busybox on playstore, started and installed it. I'll try it later or maybe for your next update.

Also I want to know why the voice data usage disappeared from settings and I appreciated the fact that you guessed my problem.

If it's possible, I would appreciate if the screen brightness is lower for your next update because I'm not fond of the kernel's default brightness because more brightness = more battery consume. Also keep your good work, I'm looking forward to this kernel because I like it and it's performance is really good.
[Galaxy S 4 i9505 Android Development] robcore:
I can't tell you why a setting would disappear from your settings, and don't think it's kernel related...

Again, you keep saying you installed busybox from playstore, but unless it's "busybox on rails," as shown in the photo below, it's the wrong one.

As far as brightness goes, I've had no other complaints, and I chose these settings because I like them. I'm not going to change it because of one person's preference, and battery life issues are mitigated in various other ways. Given your specific tastes, I encourage you to learn to build a kernel with the settings you like, that's what I did...

Finally, here is a video of my phone right at boot, you'll see the synapse settings being applied properly. There is nothing to fix for my next update because it's not broken... [youtube]jjJMN-erE3A[/youtube]
[Galaxy S 4 i9505 Android Development] lfpeacemaker:
sorry for ask, but you can port this kernel for 9515l?
[Galaxy S 4 i9505 Android Development] Superperry96:
I probably installed the wrong one, because sometimes it showed me "synapse boot canceled".

For brightness, okay i'm sorry for being pretentious, I'm only not used to that brightness.

Maybe I'll also try to learn how to modify kernel but I'm afraid it won't be an easy task for me.

Again I'm really sorry and thanks for all your replies.

Btw this is the busybox I installed and I want to be sure if it's the correct one:
[Galaxy S 4 i9505 Android Development] robcore:
I'll work on some more brightness customization soon, don't worry.

As far as busybox goes, you are using the wrong one and that's why Synapse isn't working. That's why I've repeatedly told you "busybox on rails," both in the OP and my replies to your questions. HERE>>>>>>>>>> https://play.google.com/store/apps/details?id=me.timos.busyboxonrails&hl=en

Make sure to update to their latest binary in the app, or your synapse issues will continue to persist.
[Galaxy S 4 i9505 Android Development] robcore:
I'm sorry but without having the device to test with, it just isn't possible for me. If you guys have any devs who own the device, they are free to. It will be difficult though because I've hacked a lot of customization in strictly for the 8064 board, and yours is an 8930.
[Galaxy S 4 i9505 Android Development] sonickles9:
Hey robcore, suddenly I got RR's after boot with markten

it would happen every boot, and got fixed once I reflashed the kernel (synapse?)

synapse settings:

cpu

-underclock to 1350mhz both in hardlimit and frequency

-elementalx governor

-C3 sleep

cpu volt

--50000mv(HOWEVER, reverting to stock voltages would cause the same problem)

thermal

-65°/75° respectively

gpu

-simple governor

-ramp threshold at 3000

sound

-headphone -10 (heck it's too high lol)

battery

-1000ma for usb

-1200ma for WC

the rest is stock settings...

and here are the logs

http://cloud.tapatalk.com/s/57e7225c29fe0/dmesg-2016-09-24.21.14.55.txt

http://cloud.tapatalk.com/s/57e722d7a6ef3/last_kmsg-2016-09-24.21.14.56.txt

http://cloud.tapatalk.com/s/57e72320b2390/logcat-2016-09-24.21.14.54.txt

Enviado de meu GT-I9505 usando Tapatalk
[Galaxy S 4 i9505 Android Development] robcore:
Everyone pay attention: THIS is bug report.
[Galaxy S 4 i9505 Android Development] robcore:
[MENTION=6018519]sonickles9[/MENTION]

Please tell me that was MarkTen and not the beta i posted? (MarkTenNext)

Either way, there are so many improvements in code , execution, and Synapse for MarkEleven that I'm not even worried. Thanks to your bug report, I have removed sleep state checkboxes in Synapse but left the time in each state for reference. Disabling wfi(wait-for-interupt) basically disables the machine's ability to recognize messages from all the different hardware components. Essentially, it blocks things like Bluetooth and the cpu telling each other "hey, time to wake up!" Or "hey, i need more power!"

Lol I knew it was shortsighted to allow user control of the sleep states, I was just excited that my fancy scripting worked....there is nothing more satisfying than learning how to convert a number in microseconds to day hour and minute using "awk."

I think I'll release MarkEleven tonight, till then, turn c0 (wfi) back on! Also try the "next" version of MarkTen I posted a few posts back. It includes the fix for partial suspend's counter decrement bug in the drivers (modem is biggest example).
[Galaxy S 4 i9505 Android Development] Andycar:
hey [MENTION=4763308]robcore[/MENTION], speaking about two other power states checkboxes in Synapse (besides deepsleep and WFI) - I tried enabling them, but CPU always stays zero time at them... So I really dunno if we can control these power state, and what for? :):)

Thanks for the MarkTenNext2 - I think I can see some image quality improvement on display! -However, might be just a placebo effect.... :)

Anyways, working good. :)
[Galaxy S 4 i9505 Android Development] robcore:
Yeah i added the power states section in synapse when considering trying them all, but my research into the board convinced me that retention and spc are still useless. And it looked neat :P

The color is definitely NOT placebo. It's control in synapse might be though!
[Galaxy S 4 i9505 Android Development] robcore:
Here is a little MarkEleven demo. I cleaned up synapse by consolidating sections, moving some functions into their appropriate sections, and removing some functions that don't need tweaking.

[youtube]IqASM8UTiiw[/youtube]
[Galaxy S 4 i9505 Android Development] Superperry96:
I didn't expect such a fast update (I installed 11 and now there is 12 lol).

The data usage voice returned with 11, I kinda expected it so nice job.

Also I didn't noticed bugs on 11 and performances are okay as usual.

I'll try 12 to see if there are bugs.

P.S. Sorry if I used the term 11 or 12, it's only for fast typing and also thanks for citing me in the 11 update, I saw it :P
[Galaxy S 4 i9505 Android Development] Andycar:
LOL! I downloaded Mark11 in the morning, and was going to flash and test it tonight.

Fortunately, I checked this thread again for some reason - and boom! - here comes the next version :)

So, gonna skip the 11 and test the 12th! )
[Galaxy S 4 i9505 Android Development] devsnor:
Hello again, MarkTwelve is awesome, very snappy and stable, I have not gotten a single RR yet since MarkTen. Good job! I do have some observations though. There is something wrong with the simple GPU governor, even if I set it to more performance oriented values it gives me terrible ui lags and battery drain. Even when I go back to ondemand the lag and the drain stays until i reboot.

BTW, can you by any chance release the OC version along side the regular release, for testing? I don't know how much extra work it would be for you to do that, im guessing not much since all the tools are already in the kernel, anyway.. If you think that is a good idea and not too much of a hassle for you atm, I'll happily be a tester of the OC version. Thanks!

//edit

A very good read on interactive and ondemand governors, the guy seems to know what hes talking about, my question to you is what do you know that he doesnt, concerning your default gov of choice in your kernel. He also touches the subjects i have already asked about, the deadline scheduler, im very curious what your thoughts are. Thanks in advance. ; ) http://xdaforums.com/showthread.php?t=2649820
[Galaxy S 4 i9505 Android Development] robcore:
[youtube]uDXGyYHWKYo[/youtube]

Simple Gov can't be the only factor, what other settings are you using?

Regarding OC, if it becomes a stable option, it will be included in the kernel. No two separate releases will be required because hardlimit is in place and is working as it should.

As far as the default gov goes, I'm leaving it at samsung's stock for compatibility purposes, and because everything can set on boot. My personal gov of choice is hellsactive, but I'd rather make bootup as close to stock as possible given how much is already changed. In my opinion, the default gov should be performance for booting, then switch to ondemand in init sequences, but some s4's can't handle the performance gov due to age/damage/binning etc.
[Galaxy S 4 i9505 Android Development] Belgas14:
robcore now that you already a stable kernel try to put as side project your own ROm, you're probably the only guy that can port 5.1 or 6.0 for our device, another thing, you should try to our s4 group, some people are testing your kernel there and we are having some nerdy discussions there. Thank you againc
[Galaxy S 4 i9505 Android Development] robcore:
Ha ha I really appreciate your confidence in me, thank you : )

Porting a newer android version is definitely food for thought. If I ever were to, i would start with 5.1 because I'm sure I could get a decent base from our google edition device to start with. That said, I haven't been in the rom building game for years, so I dunno if I'd be much use. I'll throw out a "never say never" but I don't want to get your hopes up ;)

For now, it looks like darknesss is doing something neat with his arctic ux project that has piqued my curiousity.

I am always interested in joining a geeky discussion group! Lol my number one development complaint is that I can never get enough geek talk! I love it! I hate whatsapp though, is there a telegram one?
[Galaxy S 4 i9505 Android Development] robcore:
Fyi don't worry about how you write the numbers, I am in no way sensitive about it. Tomato to-mah-to and all that jazz.

Technically, given that the naming scheme I'm using is based on iron man's suit numbers, I should be using Roman numerals. But I started out spelling the numbers out and kinda liked how it worked out, so now I just keep the naming scheme for consistency (though it gets annoying for file sorting.)

People! Check out how crisp the audio is on the latest update!!!!!
[Galaxy S 4 i9505 Android Development] parser:
Dude thanks so much for your work! after all this time, you are reviving this phone again with crazy abilities lol :)

some posts ago I ask smth about HBM not sticking. Follow up question; should the auto brightness be shut down? when I use like that HBM sticks without problem.
[Galaxy S 4 i9505 Android Development] robcore:
You're welcome my friend :) yes HBM works perfectly but only in manual mode. Autobrightness must be off to use it.

The reason is that samsung/Qualcomm (mostly samsung in this case) hooked the hbm trigger into the auto brightness code and then proceeded to conditionally over ride it. So I disabled the override.

If I knew the register bases well enough, and became more familiar with mipi protocols, I could rewrite the part of the api to make hbm and hbm auto separate features like on newer boards, but for now having it working for manual mode is an achievement in itself!
[Galaxy S 4 i9505 Android Development] Superperry96:
Your kernel is very stable, I'm using this with WizCyan rom.

I'm amazed of the performances. Great job.
[Galaxy S 4 i9505 Android Development] robcore:
Ever had stable with OC? ; )
[Galaxy S 4 i9505 Android Development] devsnor:
mom please!
[Galaxy S 4 i9505 Android Development] Andycar:
to [MENTION=4763308]robcore[/MENTION]

My S4 is operating nicely with your kernel and my own odex I9505XXUPPI1 ROM debloated base!

I've never been pleased more with the device! I still want to keep it for daily use, despite I have other newer Samsung smartphones.

I want some xda members advice. My i9505 is 2 years and 10 months since its manufacture date... I wanna try UnderVolting for even better battery life.

Should I go with UV or is it a bad idea? Thanks!

On a side note: On the last machinex I noticed some delay after home before wakeup, despite the Wake Up Kick freq is 1890 Hz by default. Is it only me?
[Galaxy S 4 i9505 Android Development] devsnor:
I have that too although its much less severe since I maxed the wakeup kick. However my issue may be related to using the sview cover (the one with a window).

My experience with undervolting is that it doesnt do much in terms of battery life but it does make the phone a bit cooler. The drawbacks outwighted that for me however. Its nearly impossible to find which frequency is causing trouble as I noticed that the stability at say -. 50mv at full charge doesnt mean its going to be stable at 30% charge. Also, sometimes it wouldn't simply reboot when unstable but cause some random freezes, performance losses and force closes. Not worth it imo.
[Galaxy S 4 i9505 Android Development] Andycar:
Thanks for your opinion, [MENTION=7737372]devsnor[/MENTION]

Отправлено с моего GT-I9505 через Tapatalk