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

[marco_wack]

Yes it happens to me when needed to focus on small things like cards, every time I need the auto focus I have to restart the phone, because closing the app didn't worked.
There is any other solution for this?

Sent from my XT1650 using Tapatalk

Sadly no, seems like a kernel issue that @flar2 needs to fix

 

[flar2]

Somehow since I flashed this kernel my camera focus does nothing at all, it just straight up doesn't work. I can only do shots at normal range, even if I tap to focus on close range it won't work

---------- Post added at 04:08 PM ---------- Previous post was at 04:04 PM ----------

Seems like it works for 4 seconds after starting the camera and then stops working until I close the app that's using the camera (eg. WhatsApp Snapchat the camera app, it's the same with all of those) and restart it and then it works again for 4 seconds, so it's definitely not a hardware issue

Yes it happens to me when needed to focus on small things like cards, every time I need the auto focus I have to restart the phone, because closing the app didn't worked.
There is any other solution for this?

Sent from my XT1650 using Tapatalk

I can't reproduce this. My camera focuses and works totally fine.

I'm using NPLS25.86-30-12

 

[marco_wack]

I can't reproduce this. My camera focuses and works totally fine.

I'm using NPLS25.86-30-12

I am on exactly the same stock rom. Is there any way to reflash the camera firmware or something like that? It definitely didn't happen before I used ElementalX and it's a software issue not hardware

 

[flar2]

I am on exactly the same stock rom. Is there any way to reflash the camera firmware or something like that? It definitely didn't happen before I used ElementalX and it's a software issue not hardware

Try wiping cache and Dalvik first. Then make sure you are on the matching firmware and dirty flash the stock ROM.


For these kinds of things, there's nothing I can do. All the camera stuff has to match (firmware + kernel + camera app). I never modify camera drivers, they are too complicated.

 

[lollyjay]

Does this disable force encryption?

 

[flar2]

Does this disable force encryption?

No

 

[ximmox]

Try wiping cache and Dalvik first. Then make sure you are on the matching firmware and dirty flash the stock ROM.


For these kinds of things, there's nothing I can do. All the camera stuff has to match (firmware + kernel + camera app). I never modify camera drivers, they are too complicated.

Same camera issues for me, although I think they don't happen all the time, but most of the time I try to use the camera (stock Motorola app or nCamera HDR+ mod here from the Moto Z Mods forum).

Clearing cache and dalvik didn't fix it, will try reflashing the stock images. Afair this did not happen with the TurboZ Kernel I used previously.

 

[marco_wack]

Same camera issues for me, although I think they don't happen all the time, but most of the time I try to use the camera (stock Motorola app or nCamera HDR+ mod here from the Moto Z Mods forum).

Clearing cache and dalvik didn't fix it, will try reflashing the stock images. Afair this did not happen with the TurboZ Kernel I used previously.

Used TurboZ before too (reflashed stock boot.img before switching to ElementalX) and it didn't happen to me when I was using TurboZ. So definitely something with this kernel. Please report back if flashing the stock images helped you

 

[ximmox]

Please report back if flashing the stock images helped you

Sorry to say, But I could not flash the stock boot.img successfully. There is no stock image of Android 7.0 for the RETEU phones, the suggested RETBR stock zip file with the boot.img therein is not booting on my MotoZ when I flash it (stays at bootlogo saying "bad ID" or something.)

Still, when I restore my Backup with the TurboZ Kernel, there is continuous autofocus without any problems on either camera app. I suppose there is a problem within ElementalX kernel, but I can't say for sure because I'm currently unwilling to reflashing a complete stockimage from RETBR only because there is no proper RETEU image available.

 

[marco_wack]

Sorry to say, But I could not flash the stock boot.img successfully. There is no stock image of Android 7.0 for the RETEU phones, the suggested RETBR stock zip file with the boot.img therein is not booting on my MotoZ when I flash it (stays at bootlogo saying "bad ID" or something.)

Still, when I restore my Backup with the TurboZ Kernel, there is continuous autofocus without any problems on either camera app. I suppose there is a problem within ElementalX kernel, but I can't say for sure because I'm currently unwilling to reflashing a complete stockimage from RETBR only because there is no proper RETEU image available.

Ok but we now it works when going back to TurboZ so it must be inside ElementalX. Hope @flar2 can help. Maybe it helps if we provide some logs when starting the camera app or something like that

 

[flar2]

A version for LineageOS and custom ROMs is now available.

 

[iZak17]

Thank you, SO Much!!!
I will try it right away.

 

[dergu]

A version for LineageOS and custom ROMs is now available.

I installed the kernel, and it seems it is the first for me with working deep sleep mode and double touch to wake and working wlan [emoji1] on LOS Roms (RR 5.8.3) . thank you [emoji1]

Sent from my XT1650-03 using XDA-Developers Legacy app

 

[sno1c]

Will the custom rom version of this kernel work for AOKP?

 

[flar2]

Will the custom rom version of this kernel work for AOKP?

Probably. Back up your boot.img and try it.

 

[swejuggalo]

I might have found a bug in custom rom version. Using Lineage to be exact. I let the battery drop below 15%. I had configured the kernel to auto switch to power save mode with EX kernel manager. Charged it up to around 50% and found the max speed on big cpu still being limited. I'll try to replicate and provide some logs.

I have an idea. Could the manager powersaving mode have a conflict with OS own powersaving mode if that is enabled too?

After some thinking it might just have been throttling. But I did have Lineage own powersaving enabled too. Double is not better [emoji6]

Sent from my XT1650-03 using Tapatalk

 

[iZak17]

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.

 

[swejuggalo]

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

 

[dergu]

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.

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

 

[a442509097]

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".