[KERNEL] [Oct 2] ElementalX Z 3.02 (Stock 8.0.0)

[iZak17]

I am on RR also. DoubleTap2wake works.
I have no overclocking.
Have you disabled inactivitydisplay ?

I may have any setting that´s not allowing to DoubleTap2wake to works.

I will check inactivity display.

Thanks for your reply.

 

[flar2]

I have installed on my XT1650-03 with Resurrection ROM (Jun 14 build).

Everything is working perfect, except for the wake gestures (DoubleTap2wake). I turn it on with Kernel Adiutor app, but it doesn't work. After a reboot, It disables automatically.

Overclock is running fine. No overheats, glitches or battery dranings.

Try EX Kernel Manager if you want to take full advantage of this kernel. Kernel Adiutor doesn't have proper settings for a lot of things.

With EX manager the io scheduler only get changed on external storage (according to Kernel Auditor, but I think it's a mistake and it's really the internal and not SD card). Could it be a bug somewhere?

Min cpu frequency (big cluster) shows as unavailable.

Cpu temp does not show at dashboard at first unless you go in and press ok and arrow button at the cpu temperature page. The temperature page is at first completely empty.

Sent from my XT1650-03 using Tapatalk

sdcard is on the data partition, which is the partition that EXKM has i/o settings for.

 

[swejuggalo]

Try EX Kernel Manager if you want to take full advantage of this kernel. Kernel Adiutor doesn't have proper settings for a lot of things.



sdcard is on the data partition, which is the partition that EXKM has i/o settings for.

After the cpu frequency showed a strange value I decided to compare with what Kernel Auditor showed. Made me wonder why I had a not available value on the frequency in Ex Kernel Manager. Maybe it is that way for a reason. No need to fix stuff if it works as intended [emoji6]

Sent from my XT1650-03 using Tapatalk

 

[ximmox]

Same problem camera can't focus, "XT1650-03_GRIFFIN_TELUS_7.0_NPL25.86-30_cid50_subsidy-TELUS_regulatory-DEFAULT_CFC.xml"

"TurboZ" is ok, but i don't like overclocked, because will "flower screen".

I have the suspicion, that the camera bug appears for people that previously used TurboZ? Perhaps there are any remains left, that interfere with ElementalX?

Due to the bug I am back to using TurboZ for now, but I'd like to switch to ElementalX.

 

[flar2]

There nothing I can do about this camera bug. I don't modify the camera drivers at all, and I can't reproduce the problem. My camera works flawlessly.

 

[ximmox]

There nothing I can do about this camera bug. I don't modify the camera drivers at all, and I can't reproduce the problem. My camera works flawlessly.

I know, I really think it has to do with the modules TurboZ pushed while flashing. Or does anyone here have the camera bug (autofocus not working 3 to 4 seconds after opening any camera app) with this kernel, who never had any other kernel than stock before?

I would simply flash back to clean stock, but I'm still hesitant because there is no proper RETEU image for Android 7 and while everyone says to flash the RETBR image instead... Well, I find that to be kinda hacky.

 

[marco_wack]

I know, I really think it has to do with the modules TurboZ pushed while flashing. Or does anyone here have the camera bug (autofocus not working 3 to 4 seconds after opening any camera app) with this kernel, who never had any other kernel than stock before?

I would simply flash back to clean stock, but I'm still hesitant because there is no proper RETEU image for Android 7 and while everyone says to flash the RETBR image instead... Well, I find that to be kinda hacky.

That said I flashed the stock retbr image and then back to ElementalX and the bug stayed, so even going back to stock didn't help

 

[ximmox]

That said I flashed the stock retbr image and then back to ElementalX and the bug stayed, so even going back to stock didn't help

Same for me, flashed stock image this evening, focus works on stock kernel, focus stops working after a few seconds when flashing ElementalX afterwards. So there seems to be a connection to the kernel, maybe it's some setting to save power or something instead of directly camera related stuff.

 

[swejuggalo]

I can't see a problem here. But I'm on Lineage and tried Snap and Open Camera.

Sent from my XT1650-03 using Tapatalk

 

[flar2]

That said I flashed the stock retbr image and then back to ElementalX and the bug stayed, so even going back to stock didn't help

Same for me, flashed stock image this evening, focus works on stock kernel, focus stops working after a few seconds when flashing ElementalX afterwards. So there seems to be a connection to the kernel, maybe it's some setting to save power or something instead of directly camera related stuff.

Maybe firmware? I'm going to try one more thing first. I think there could be a problem with my dt.img.

 

[flar2]

Update!!!


Stock ROM
ElementalX-Z-1.01



Changes:
-optimize for size
-fix installer

 

[ximmox]

Maybe firmware? I'm going to try one more thing first. I think there could be a problem with my dt.img.

Thanks for looking into the possibility. Any more input that could help? Which logs might be useful if any? I'll be glad to help.

And: Is the "one more thing" already in 1.01, maybe the reverted commit?

Edit: awesome, it's already fixed in 1.01! Autofocus works all the time, stock Moto Camera as well as the HDR+ mod of nCamera (here in the Moto Z Themes & Apps section, highly recommended!).

Thank you very much @flar2!

 

[marco_wack]

I am gonna flash 1.01 later and report back if the issue is fixed

 

[flar2]

Thanks for looking into the possibility. Any more input that could help? Which logs might be useful if any? I'll be glad to help.

And: Is the "one more thing" already in 1.01, maybe the reverted commit?

Edit: awesome, it's already fixed in 1.01! Autofocus works all the time, stock Moto Camera as well as the HDR+ mod of nCamera (here in the Moto Z Themes & Apps section, highly recommended!).

Thank you very much @flar2!

The dt image was okay, I built with different complier options ( -Os instead of -O2)

 

[iZak17]

Try EX Kernel Manager if you want to take full advantage of this kernel. Kernel Adiutor doesn't have proper settings for a lot of things.

I've just installed EX Kernel Manager. You were right, it is a lot better than Kernel Adiutor. DoubleTab2wake working perfectly

Congratulations for your work!

 

[marco_wack]

I've just installed EX Kernel Manager. You were right, it is a lot better than Kernel Adiutor. DoubleTab2wake working perfectly

Congratulations for your work!

How big is battery drain with dt2w?

 

[flar2]

How big is battery drain with dt2w?

No drain.

There are only a couple phones where gestures cause drain. It's a myth.


Sweep up to wake is much better than doubletap to wake. Double tap to wake is prone to accidental wakeups, interferes with phone calls and is not as reliable. Sweep2wake works much better.

 

[swejuggalo]

Just tried a day with the wakelocks in the EX Kernel Manager as blocked. Pretty nice change. I did some searching for explanations on all the wakelocks and some stuff is not that very easy to find. I haven't seen any downsides with my specific use yet.
Some other settings is not that very clear and easy to understand either. Some stuff users might want to change for certain reasons but if they know the pros and cons they might reconsider.

I haven't found any info about the settings and what they do. Do they exist somewhere? Think some users would be happy with some explanations

Around 1% drain per hour according to EX kernel manager is pretty nice.

Sent from my XT1650-03 using Tapatalk

 

[flar2]

Just tried a day with the wakelocks in the EX Kernel Manager as blocked. Pretty nice change. I did some searching for explanations on all the wakelocks and some stuff is not that very easy to find. I haven't seen any downsides with my specific use yet.
Some other settings is not that very clear and easy to understand either. Some stuff users might want to change for certain reasons but if they know the pros and cons they might reconsider.

I haven't found any info about the settings and what they do. Do they exist somewhere? Think some users would be happy with some explanations

Around 1% drain per hour according to EX kernel manager is pretty nice.

Sent from my XT1650-03 using Tapatalk

Someday I want to write a guide, just haven't had time.

 

[swejuggalo]

Someday I want to write a guide, just haven't had time.

Ah. Great

Take your time. I've seen some solutions that have plenty of info within the app itself, but it can make it rather ugly. Maybe a manual/guide link that simply opens a browser may be the best solution.

Personally I'm most interested in the wakelock explanations and what the audio setting really do. I probably haven't googled enough yet.

Sent from my XT1650-03 using Tapatalk