Search results

Thanks, i already finished internship trial exams 2 weeks ago. Now only need to wait for final test exams on the college... Still preparing for other thinks....

Hard decision to be honest, but beside i want to try to make it work for this 4.9. Since i already failed to bring it up on 2 times, so i won't waste this chance when lead project already success make panel working on 4.9. Clarity will stuck on 3.18 with latest r18, and will continue on 4.9...

4.9 Build still on base focus fix, not getting any customizations. If you want to try that build, look on clarity project channel. You can download latest stable build from there. When it ready to custom i'll create a thread here, or maybe i'll create for updated 4.9 if anyone want it

Well, okay then. Thanks for your suggestion, i'll need to remove this too on next 4.9 :eek:

It'll, but it'll need a time and also. It'll based on 4.9 kernel for the next, i still need a time to stabilize it base, before customized it ;)

If in this cases, so it's better to remove that commit for Simply solution to fix it, however. I'm not currently maintain this kernel anymore. I still can compile it, but i'll leave it out from latest security patch from common stream and untested build included reverted of that commit for MAC...

actually r19 already have it build, but i was dropped it when on testing stage. So far it's good on my test, i couldn't test anymore due focusing on other project for mido. And i don't want to push that build due already not maintain since last april and also, not getting any test of it. So in...

It's from prima (wlan) kernel module, it has this feature to "randomize" your MAC address. I already include this since initial build...

This is actually from HMP ROM boost algorithm, and that error is actually useless and shouldn't make any issue, you just need to remove all ".xml files on vendor/etc/perf and leave it out that .conf file. And you're safe to go

Yes, already quite stable for now

That's absolutely from the thermal engine itself, but, increasing of modem proc mitigation will have other risk with your modem board that may cause some issue there. It's your risk anyway. My kernel have workaround inside the msm-thermal that fix mitigation issue from the kernel when receive...

Random ping issue isn't from the kernel, that may from your thermal engine that mitigate modem when it's too hot

Only notice several SLMK kill of your apps, i think there's something messed up from the slmk that make freeze. But not sure which one

hmmm, did slmk starting weird? last two weeks when i test, that still good. I can't test 3.18 again for temporary :eek:

Currently i'm not including anything on thermal profiles, that maybe come from app that already have a thermal profiles. Use default and never configured that should be fine for daily usage. Sent from my Xiaomi Redmi Note 4 using XDA Labs

Ethereal is closed source...

Flashing kernel without use magisk it'll break safety net, you will need magisk to get rid that issue. Nah, i'm not chinese Sent from my Xiaomi Redmi Note 4 using XDA Labs

Hmm, will search for references then if available... Sent from my Xiaomi Redmi Note 4 using XDA Labs

Hmm, okay, thanks for your report ;). That maybe from simple lmk that i forget to revert for android 9, will fix it on next release :)

Touch driver? For what? Any touchscreen issue :rolleyes:? And beside, where i can get that think. . Sent from my Xiaomi Redmi Note 4 using XDA Labs

It depends, depends how dev tuning that EAS. in theory EAS made to for balance to power-management on kernel, which mean, you still can get great battery balance without tributing so much performance sector. Anyhow, it doesn't always mean to save battery.

Dunno, no reason, give me kernel log when you have that issue, and tell me clearly your reason when you get or trigger that problem. Also, i won't share any kernel if still on that unstable state. It can be from ROM issue too i think...

Issue like what? Sent from my Xiaomi Redmi Note 4 using XDA Labs

Find search option, and search my ID. After that contact me once

Okay good if you want to test it, try to contact me on telegram if you want it. I'll send it when it ready. For battery r18 should a bit drain than r17 due i've include several tweaks to improve performance that have affect to battery. But not really drain so far when i test daily usage. Don't...

Nah, that's not always need it. But that will need if you face any issue after installing any kernel, flash boot.img on your recovery, you should fine that partition option when you want to flash it. Anyway for your issue i just think that may come from panel issue, but i'm not sure. Anyway, if...

You should flash boot.img if you flash from different kernel version, however this think is mandatory to avoid any error that may come from old cache of kernel. To get your current boot.img, you just need to open your current zip of ROM then extract boot.img from there and flash it to your...

Core control should be disabled, on pie version i've disabled it from init script but on Q version. I'm not do it, Android Q on mido have SAR on ROM, which mean i can't plan anything on init. I'll try to find another way to disable it by default. But make enable core control won't make any...

Thanks for your report, report if you've any issue :)

Up to you for reverted, but, flash boot.img before flash any custom kernel is really mandatory to avoid any issue that may come from old kernel cache. I was include commit on github to gain better battery usage on display panel for mido to all display panel, just think if some panel not really...

Will try later with this issue, i'll need tester for pie issue whenever a new build ready. and for USB Fast charge, just use that feature if you need to use it. I was disabled it by default due i'm not always use it :rolleyes:

Dunno, maybe issue on powersave panel, other user told me no problem on pie with derpfest pie. Maybe i'll try to build without that powersave panel, but. Not sure, since i'm not on pie Sent from my Xiaomi Redmi Note 4 using XDA Labs

Android Pie or Q ?

Which FileSystem did you using it? ext4 or f2fs?

Don't know, no reason. I didn't test this on pie, so i can't produce anything why this error may come. Already try force reboot after stuck on MI logo? Stuck on MI logo is normal procedure when flash magisk after kernel, and also. This kernel isn't need to flash magisk again after flash zip...

So some issue happen on pie ROM user, don't know. I may need log from dmesg when issue happen Sent from my Xiaomi Redmi Note 4 using XDA Labs

Which ROM? Try to flash your boot.img again and flash this kernel again, since i don't have any issue on Q based ROM. It may happen due power save panel, but not sure Sent from my Xiaomi Redmi Note 4 using XDA Labs

Try to flash your boot.img from your current ROM again, then install kernel again. If still stuck on MI logo, then try to force reboot your phone. It should boot into your system, i just think this due full pelt implementation. So it have same issue with last syberia ROM for mido Sent from my...

For codm and discord kill when phone i may assume that cause from slmk merged was not optimized "maybe" for android pie. But, for drain. I was play several game like honkai impact, codm and other game with WiFi. Battery usage drain seems still on usually, 16% / hour if you play high graphic...

Nah, tell me which magisk module or modification that already you installed. And is that battery drain happen when you using or not? For that switch tab issue, that may come from simple lmk. Are you on pie or on android Q? I didn't have that issue here on android Q when play codm and discord...

What issue? Smart charging isn't from kernel side, i didn't implemented anything related to charging driver on kernel Sent from my Xiaomi Redmi Note 4 using XDA Labs

Dunno, maybe i'll need to remove powersave panel on that hmp based kernel. Well, try to use clarity and report if you have same issue Sent from my Xiaomi Redmi Note 4 using XDA Labs

Ohh that think, adreno boost and adreno idler :eek:. Sorry i forgot to add that, okay. Noted for next release :silly: Sent from my Xiaomi Redmi Note 4 using XDA Labs

I think i'll add this questions as FAQ if i've free time. 1. EAS Based kernel will work on every ROM, no matter different or same scheduler and it won't make bootloop. 2. For benefit and advantages, EAS Kernel should be use on EAS Based ROM to get advantage from power hal v1.3 (perfmgr). But...

Yes you can Sent from my Xiaomi Redmi Note 4 using XDA Labs

Yes, i'll work for Pie or Q. Just flash with proper android version release ;)

Dunno, can you tell proper reason regarding your issue ? flash procedure, magisk module or etc

Nah, we can't go through that way. Limiting freq speed not always good idea for this cases, if you said EAS work better for different cpu (Clustering) then the answer is yes. But our mido doesn't have any cluster on soc, so EAS here should work for single cluster soc. Anyway, limiting core speed...

Okay ;)

Well, have try ;)