[ROM+Kernel][EAS-VOX] VertexOS Carbide v3.6 and RenderZenith Kernel 012 (Blueborne)

[Puddi_Puddin]

Congrats, but BFQ is designed for large multitasking, is great on Desktop, VPS exc exc (my vps use BFQ with latest Liquorix Kernel 4.10)

Android required simple scheduler like Noop or ZEN

Yes and BFQ probably replaces CFQ I'm the near future. This is a more updated one and it performs the same as CFQ on stock settings!

 

[dekefake]

I acknowledge the bluetooth issues. I'll test the fixes and see about releasing the next official early

I am experiencing this kind of Bluetooth issues too, using Carbide 3.0 dirty flashed from previous build. Can't connect my freshly resetted Moto360, as well as my JBL Charge 2+. The speaker connects to my Skylake hackintosh without trouble. If you need some logs, fell free to PM me

 

[Deleted member 2357893]

Yes and BFQ probably replaces CFQ I'm the near future. This is a more updated one and it performs the same as CFQ on stock settings!

BFQ is great on desktop but on Android it's very slowly compared to other solution like NOOP, Deadline and the other "simply scheduler" made for flash storage

 

[joshuous]

BFQ is great on desktop but on Android it's very slowly compared to other solution like NOOP, Deadline and the other "simply scheduler" made for flash storage

There are no regressions with this BFQ. I've done benchmarks in Androbench to test throughout, and I've done app launch test comparisons against CFQ using 24 apps.

I don't think Noop is better. You'll see janks and stutters when there are updates in the background if you use Noop.

 

[ndarkside93]

BFQ is great on desktop but on Android it's very slowly compared to other solution like NOOP, Deadline and the other "simply scheduler" made for flash storage

That would be true in the past. But with the backported code from the mainline 4.11/4.12 it is no longer the case. It's been greatly optimized.

 

[joshuous]

@joshuous a couple of ui bugs.

Bt icon in ststus bar(not qs) doesnt reflect when a headphone is connected

Using Spanish language when i want to turn off. shows your phone will reboot.

Any impact of disabling sdcardfs?

Known bug. Working to fix it.

 

[Konskl]

@joshuous have you found out the reason of the screen not lighting up during incoming calls with the log provided by @Jagdish84 ? I can fetch some more if i get some free time... Also i got some black screens which needed the phone to be restarted by the power button to resolve. Clean flash - haven't tried the sdcardfs disabler by eng.stk yet.

 

[Deleted member 2357893]

The problem is not the ufs memory test, the problem is the test with slower memory like emmc. I prefer test scheduler on old devices like N5, Z3 exc exc

 

[LMcR92]

Congrats, but BFQ is designed for large multitasking, is great on Desktop, VPS exc exc (my vps use BFQ with latest Liquorix Kernel 4.10)

Android required simple scheduler like Noop or ZEN

Yeah I use zen or maple if it is there.

To anyone wanting a layman's breakdown of schedulers, I/O and TCP options here is a great guide. http://androidmodguide.blogspot.co.uk/2014/06/welcome.html?m=1

 

[viveknaudiyal]

Known bug. Working to fix it.

What I instead face is that if i enable Bluetooth battery status from systemui tuner the Bluetooth icon vanishes and if disabled the icon reappear on status bar.
Also can you suggest how to take screenshot as i couldnt find the option anywhere.

 

[joshuous]

What I instead face is that if i enable Bluetooth battery status from systemui tuner the Bluetooth icon vanishes and if disabled the icon reappear on status bar.
Also can you suggest how to take screenshot as i couldnt find the option anywhere.

Screenshot on Android is almost always Power Button + Volume down.

You don't need to take screenshots for me. I mentioned it is a known problem, so you don't need to send me anything. It has been fixed in my test builds already

 

[calvinistmac]

Yeah I use zen or maple if it is there.

To anyone wanting a layman's breakdown of schedulers, I/O and TCP options here is a great guide. http://androidmodguide.blogspot.co.uk/2014/06/welcome.html?m=1

Zen or Maple (not sure about Maple) are not going to be your best options for EAS. Zen was good over on HMP kernels (Boeffla, eng.stk, etc...). The BFQ i/o scheduler in here has been tested by Josh personally (believe me he knows his stuff regarding EAS and kernels) and works really well, plus I've tested it and it gives great performance and the battery life is just as outstanding. Don't go messing with the kernel settings on this rom unless you're absolutely sure you know what you're doing as you can mess things up pretty quick.

Please do a little more research before recommending stuff like this and possibly impacting other users' experience in a negative way.

 

[LMcR92]

Zen or Maple (not sure about Maple) are not going to be your best options for EAS. Zen was good over on HMP kernels (Boeffla, eng.stk, etc...). The BFQ governor in here has been tested by Josh personally (believe me he knows his stuff regarding EAS and kernels) and works really well, plus I've tested it and it gives great performance and the battery life is just as outstanding. Don't go messing with the kernel settings on this rom unless you're absolutely sure you know what you're doing as you can mess things up pretty quick.

Please do a little more research before recommending stuff like this and possibly impacting other users' experience in a negative way.

Wow slap in the face..... I'm not a kid and that "guide" I posted isn't to impact others it's there to give a easy read description to those who don't fully understand the descriptions that can be full of jargon. They don't need to follow the best to worst scale as every phone and user has there setup they like.
Also I'm not undermining any developer or user this is great ROM and a decent kernel that is new to most people and I am enjoying getting a feel for EAS and is the future of android.

 

[Deleted member 2357893]

Zen or Maple (not sure about Maple) are not going to be your best options for EAS. Zen was good over on HMP kernels (Boeffla, eng.stk, etc...). The BFQ governor in here has been tested by Josh personally (believe me he knows his stuff regarding EAS and kernels) and works really well, plus I've tested it and it gives great performance and the battery life is just as outstanding. Don't go messing with the kernel settings on this rom unless you're absolutely sure you know what you're doing as you can mess things up pretty quick.

Please do a little more research before recommending stuff like this and possibly impacting other users' experience in a negative way.

But it's normal for a scheduler to work well with ufs 2.0 memories, the real big problem is with the past memory like emmc.

PS: I reccomended ZEN V2 to Engstk and the others dev

 

[Formhault]

@joshuous and everybody else

Can you please test this for me? It was happening on Vertex 2.2 (clean flashed) and it still happens now on Vertex 3.0 (dirty flashed).

Go to Wi-Fi and manually add a new network.

Network name - put in whatever (doesn't matter).
Security - choose 802.1x EAP.
EAP method - choose PEAP.
Phase-2 authentication - MSCHAPV2.
CA certificate - Use system certificates / Do not validate (doesn't matter)
Domain, Identity, Password - put in whatever you want.

The "Domain" field only becomes available if you select "Use system certificates" for CA certificate. Doesn't really matter, as the output is the same : force close. On Marshmallow, this didn't happen.

Is this related to the Wi-Fi bug that's been making headlines (enable/disable Airplane Mode in order for the Wi-Fi menu to function properly & refresh the SSID list)?

 

[calvinistmac]

Wow slap in the face..... I'm not a kid and that "guide" I posted isn't to impact others it's there to give a easy read description to those who don't fully understand the descriptions that can be full of jargon. They don't need to follow the best to worst scale as every phone and user has there setup they like.
Also I'm not undermining any developer or user this is great ROM and a decent kernel that is new to most people and I am enjoying getting a feel for EAS and is the future of android.

I never said you were a kid. I wasn't talking about the guide either as I've looked at that guide for reference. I was talking about telling people to use Zen or Maple on this ROM. These i/o schedulers are not good for this ROM and can cause issues. It's best to stick with what the ROM defaults with as EAS is a completely different bird than your standard run of the mill kernels (HMP).

Now, again I ask, please do some research before posting i/o scheduler recommendations for an EAS rom so you don't mess up people's experience. I'm not trying to give you a hard time, but you can't just haul off and recommend something that it looks like you know nothing about.

---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------

But it's normal for a scheduler to work well with ufs 2.0 memories, the real big problem is with the past memory like emmc.

PS: I reccomended ZEN V2 to Engstk and the others dev

Yes but EAS is a totally different bird that these particular i/o schedulers aren't suited for. More research needs to be done before a recommendation is made for this ROM. As I told the other gentleman, don't recommend these i/o schedulers without doing some research first. Stick with what the ROM comes with.

 

[cba1986]

@joshuous just to inform that the wifi bug is still there..
Other than that. Great ROM. The ui performance is top notch and the battery is very good so far.

 

[ManuBBXX]

Right here we go.
EAS is a completely different breed compared to the conventional HMP system, where it serves an entirely different purpose of achieving the optimal balance between performance and efficiency, with the latter taking the top spot. EAS achieves that via cleverer tasks placement by which the system determines which is the more efficient cluster for the task to be processed, as well as categorising the different tasks into cgroups (top-app, foreground and background, in order from highest priority to lowest priority) by which each cgroup receives its sliver of the available firepower (cpuset). EAS also offers the capability of inflating the perceived load, that's determined by the load trackers, of the task in any of the cgroups via its schedtune.boost setting, and whether the task should be processed by all the cpu cores available or only by the cluster the task has been placed on via its schedtune.prefer_idle setting. One of the key features of EAS is lifting almost all the processing from the governor to the CPU scheduler (no it is not the I/O scheduler, something different) and letting it take much much more control, leaving the CPU governor to only do the frequency determination part, which unsurprisingly relies heavily on data supplied by the scheduler. With all that said, it is easily deduced that EAS is not all about governors and governor settings and the like, rather a much cleverer solution that serves the purpose of seeking the best balance between performance and efficiency, and to ensure the CPU is not overdoing a task or the CPU governor is overshooting, draining a lot of power as a consequence of that. EAS is about ensuring you get the smoothest UI possible while retaining as much power as possible. However, that does not mean that EAS is lame poor when it comes to performance. Sometimes, if not in most cases, this cleverer tasks placement makes tasks get processed faster. Conserving battery does not necessarily mean crushing performance. This explains that app launches are on-par with HMP if not ahead of it sometimes.

Now on to your question. After going through that brief explanation of EAS, i think your question is actually invalid, since it is not an apple-to-apple comparison anymore. EAS seeks for the optimal balance between performance and efficiency. Should there be a commit to improve performance while not being at the expense of efficiency, EAS should have that stuffed in, whereas HMP is prioritising performance higher than efficiency by design. What Burnout does is taking HMP and making it even more performance oriented, hence it is very unlikely to face micro lags with it. However, HMP still misses the cleverer tasks placement, which can show its canines if you have so much processes going in the background, where in that area EAS takes the lead quite noticeably.

Conclusion: You should try and see what suits you more. But something i can safely say is, EAS is more than satisfactory when it comes to performance from the perspective of a man after the best performance, and with the battery gains you yield with EAS, it can go better.

Hope i helped and clear the confusion. Looking forward to your feedback on your EAS experience.
-TDK

Thanks a lot for this explanation chief !!
I loved you burnut profiles, but I believe I love too much that newx EAS features !
Not sure about battery life yet, since I use it since yesterday, but the ROM feels smoother( except in games, where I have micro stutters, joshuous says it could be caused by sdcardfs module commit, but I didn't catch how desactivating it.. )
But the entire ROM has a feel of more smooth, faster ! Even with a perf oriented profile like burnout_pr4 with Ex kernel

I think render kernel is great, but vertexOS too !!
And if I'm not wrong, it's in early developement, and will maybe better in the future. Maybe it IS the future of kernels..
How do you feel it ?

Anyway, thanks a lot for your feedback and experience sharing !

 

[pantmunu]

@joshuous what do u think of this app ? Looks simple and clean.

https://www.xda-developers.com/xda-...m-is-an-open-source-kernel-manager-for-users/

 

[Formhault]

The problem is not the ufs memory test, the problem is the test with slower memory like emmc. I prefer test scheduler on old devices like N5, Z3 exc exc

But it's normal for a scheduler to work well with ufs 2.0 memories, the real big problem is with the past memory like emmc.

PS: I reccomended ZEN V2 to Engstk and the others dev

The OnePlus 3 and 3T have UFS 2.0, not older eMMC memory, soooooooooo...