It happens that I have installed a Kernel OC, KangarooX to be more specific, everything works fine except the front camera of the Google Cam that freezes.
Oh yes, me too! But with PureCaf instead. It's strange because in the telegram group I seems to be the only person with this problem, and actually it never happen to me with previous version of the same kernel. I test kinda everything except a clean flash. The only thing I know for sure this is a hdr+ problem, if I turn it off cam work normally, and (at least for me) if I switch to front cam with hdr off and only then I turn it back on it will work fine. It's a really strange and unusual problem.
Some question, if you don't mind:
which firmware are you using?
which rom are you using?
do you use microG?
do you use some xposed modules? If yes, did you install the yahfa or the sandhook version, and which modules have you installed?
which magisk modules are you using, if any?
is your phone encrypted?
I flashed the latest firmware and I'm using the latest los from srfarias (and his latest purecaf too), I use microG, I installed Xposed YAHFA version and using xposed edge and xprivacylua, I'm using nanodroid and quickswitch magisk modules, my phone is encrypted.
Raven.95 said:
It happens that I have installed a Kernel OC, KangarooX to be more specific, everything works fine except the front camera of the Google Cam that freezes.
Click to expand...
Click to collapse
Shadow 00 said:
Oh yes, me too! But with PureCaf instead. It's strange because in the telegram group I seems to be the only person with this problem, and actually it never happen to me with previous version of the same kernel. I test kinda everything except a clean flash. The only thing I know for sure this is a hdr+ problem, if I turn it off cam work normally, and (at least for me) if I switch to front cam with hdr off and only then I turn it back on it will work fine. It's a really strange and unusual problem.
Some question, if you don't mind:
which firmware are you using?
which rom are you using?
do you use microG?
do you use some xposed modules? If yes, did you install the yahfa or the sandhook version, and which modules have you installed?
which magisk modules are you using, if any?
is your phone encrypted?
I flashed the latest firmware and I'm using the latest los from srfarias (and his latest purecaf too), I use microG, I installed Xposed YAHFA version and using xposed edge and xprivacylua, I'm using nanodroid and quickswitch magisk modules, my phone is encrypted.
Click to expand...
Click to collapse
I had the same problem and I solved it by flashing latest Illusion kernel 5.8
--> https://github.com/akhilnarang/whyred/releases
EdoNINJA93 said:
I had the same problem and I solved it by flashing latest Illusion kernel 5.8
--> https://github.com/akhilnarang/whyred/releases
Click to expand...
Click to collapse
Yep, extended kernel do the job too, thanks. So it's really a kernel problem...
Related
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
I could not get the V4A module to install under Magisk 12; however, it works just fine with Magisk 13.
This is the version that I used: https://www.androidfilehost.com/?fid=745425885120735287
Magisk Uninstaller (should not be needed, but if you want it) is here: https://www.androidfilehost.com/?fid=745425885120735289
NOTE: You are, I believe using the @tdhite kernel, which is based in Magisk 12. Not sure what the impact of installing Magisk 13 will be.
The kernel is fine with Magisk v13 (beta, to be sure is all that is released there). Magisk v13 beta still has problems, so beware. The SkyHigh kernel and module are v13 compatible as much as v12, just so you know. The reason v12 is packaged in is v12 is the only stable Magisk version at this point.
The bigger issue is Magisk v13 beta working stably and reliably, but if you are willing to debug its failures, it's ok. There should be no need to uninstall to upgrade if you want to play. Reloading the kernel flash will cleanly load up v12 if all goes badly.
Sent from my iPad using Tapatalk
@koop1955 Thank you for that information! I will bookmark those so I can get back to them once v13 is reliable and stable enough for my kernel
@tdhite Thanks bud as Well! I think I will just stay where I am until the kernel and v13 play nicely. Just got this thing as perfect as I can for now, well other than ram use creeping up, but that's only every now and then, and for another topic. I *might* get my nandroid current and play a little if I get bored and want to tinker. I guess I can safely assume then the reason Liveboot stops working with the V4A module installed is because of Magisk v12...?
Thank you to both of you guys for the help and advice. At least now I know it's not some dumb issue with my device lol.
Chuck
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
koop1955 said:
@digitalchaos1980 and @tdhite, I have had a good experience with one particular version of Magisk 13, which is why I added it to my AFH. Other and newer versions...not so much. To be expected with a work in progress.
At some point, Magisk 13 will be final and we can move forward.
Click to expand...
Click to collapse
No doubt! Version 13 gives me something to look forward to for sure
Chuck
digitalchaos1980 said:
Hi y'all, first off I have the G920P, just recently upgraded to Nougat QC7 stock ROM, modified and running the SkyHigh kernel v5.01 with Magisk v12. Everything runs pretty smooth, even got Liveboot working successfully (there's a reason I mention Liveboot.) Now I decided to try to get Viper4Android to work. Of course, installing the standard apk fails when it comes to installing the driver. So I tried the V4A Magisk module and it installed fine, however on reboot, my Liveboot no longer works and when opening the V4A app it asks to install the driver, I hit yes and it says it successfully installed and to please reboot. I reboot and of course Liveboot still doesn't show, but otherwise it boots fine. Once I re-open the V4A app it is asking me to install the driver yet again, and the whole system at times seems a bit unstable until I disable the V4A module in Magisk Manager. Does anyone have any ideas, or has anyone gotten this to successfully work? If so I'd love a suggestion lol. I really would like to keep my Liveboot working, but I'd kinda like to get Viper working too. Thanks in advance for any help, suggestions, ideas, etc.
Chuck
Click to expand...
Click to collapse
if you kindly Tell me the process how did you end up using Live boot in magisk , It would be very helpful . I have tried various method but failed
Saafir said:
Place a copy of audio effects.conf in vendor/etc. Should get you working. Be sure to set permissions as well.
Click to expand...
Click to collapse
Just to be sure, folks realize there is full equalizer support in my SkyHigh kernel and the bands are all adjustable, even per channel if desired, in Synapse, right? Just noting in case that's all you need, because it is a no-CPU-load way of getting it done.
Sent from my iPad using Tapatalk
I just installed magisk and it is working fine in f2fs file system.
This will cause any problem?
Wonder Wicked Witch said:
I just installed magisk and it is working fine in f2fs file system.
This will cause any problem?
Click to expand...
Click to collapse
Interesting, I have some questions. What rom, kernel and twrp version? Does SafetyNet pass? And do magisk modules work?
razr96 said:
Interesting, I have some questions. What rom, kernel and twrp version? Does SafetyNet pass? And do magisk modules work?
Click to expand...
Click to collapse
Right Now I'm using Resurrection remix 5.8.5 kernal 3.18.31 twrp 3.1.1.1
It works in any custom rom, it is mostly useful for lineage os and los based rom because in los you cannot root easily, Magisk with ext4 filesystem is required. I'm not sure with the modules, super user works, safety net pass failed. If you just want root access you can give a try....
It works fine when you have a different kernel. A dev. on here reported that the only reason it doesn't work is because of how Lenovo implemented F2FS in the kernel.
No problem, everything works fine except that Safety net won't pass.
I've read that Dolby Atmos crashes on March security patched ROMs and even I faced on RR OS. I'm back on LOS, but I'm afraid to flash this module. Will it crash or there's updated module?
EpicPrashant said:
I've read that Dolby Atmos crashes on March security patched ROMs and even I faced on RR OS. I'm back on LOS, but I'm afraid to flash this module. Will it crash or there's updated module?
Click to expand...
Click to collapse
?? works fine Dolby Atmos standard version on march update stock rom
For RR i don't test
laugeek57 said:
?? works fine Dolby Atmos standard version on march update stock rom
For RR i don't test
Click to expand...
Click to collapse
Didn't worked for me on march update
Tried with latest magisk 16.0 and even tried with 15.3
Have common modules installed such as ARstickers one, camera2api and eis enabler, google lens , selinux enabler v1.2
AlwaysWin said:
Didn't worked for me on march update
Tried with latest magisk 16.0 and even tried with 15.3
Have common modules installed such as ARstickers one, camera2api and eis enabler, google lens , selinux enabler v1.2
Click to expand...
Click to collapse
What version standard or unity?
laugeek57 said:
What version standard or unity?
Click to expand...
Click to collapse
Standard.
AlwaysWin said:
Standard.
Click to expand...
Click to collapse
This : https://androidfilehost.com/?fid=746010030569955178
I can assure you that this version works perfectly on rom stock I installed it a good dozen times before switching to Pixel Experience rom ...
If you have permissive selinux v1.2 to install correctly I do not see what can disturb the proper functioning ...
laugeek57 said:
This : https://androidfilehost.com/?fid=746010030569955178
I can assure you that this version works perfectly on rom stock I installed it a good dozen times before switching to Pixel Experience rom ...
If you have permissive selinux v1.2 to install correctly I do not see what can disturb the proper functioning ...
Click to expand...
Click to collapse
It is flashed successfully in twrp (3.2.1) and can be seen in the app drawer but when I open it, it keeps stopping even though the other apps like google camera is also working so probably selinux is fine, but I've faced issues with selinux before too and that time i had to restart my phone 3-4 times to fix the issue.
Any solutions?
AlwaysWin said:
It is flashed successfully in twrp (3.2.1) and can be seen in the app drawer but when I open it, it keeps stopping even though the other apps like google camera is also working so probably selinux is fine, but I've faced issues with selinux before too and that time i had to restart my phone 3-4 times to fix the issue.
Any solutions?
Click to expand...
Click to collapse
My advice would be that you make a clean installation of your rom and install only permissive selinux v1.2 magisk before of course and flash DA standard version ...:good:
[Kernel][Oreo/Nougat] StockPatched
Work's on Nougat and JUI
Fetature:
- Oreo support
- Cpuqiet
- Working magisk
- IR Work on device where IR not work on JUI
- GPU overclocked to 625 mHz
Download (Install only on JUI, LOS)
https://drive.google.com/file/d/1RkugRW3i-64sZnkNW7Jb5pz_2aNQh9QN/view
Donate:
1529yLvkmQHqhtgcDkYyZ7VgYxHnUyxefj
BitCoin
nice one there dude.
when we all beleive these isnt a light at the end of the tunnel for this phone, you make one. thanks for the kernel, i was able to boot dotos base on oreo on cool1 with your kernel.
I will make Los 15.1 as soon as possible
that's nice.
i wait for Oreo LOS.
SimbyOS said:
I will make Los 15.1 as soon as possible
Click to expand...
Click to collapse
Thank you
I installed this on los 14.1 but if you flash kernel then magisk, get ramdisk error (wifi,Bluetooth, etc), so flash magisk first then kernel and all working
cmiiw
A stable Miui 10 with everything working like stock cam,IR could be worth giving a shot as a daily driver..
JUI 8.0
Is this kernel working on JUI 8.0?
Hi,
Thanks for the work.
Do your other ROMs already have this kernel?Or should I flash this again?
cool1 and also Dotos?
Fixes IR Blaster, Disables WiFi
Hi. I tried installing this on JUI hoping it would fix IR issues. It did, but now my WiFi is not working. Any work around for this?
Btw, thanks for this.
Installed this on JUI Mod Cool Play 6. Fixed my Magisk but Wifi and Wifi Tethering is broken.
@SimbyOS Please tell me how to fix the broken wifi issue with this kernel...The kernel working seamlessly on machmotofan coolplay6 firmware for cool1...IR blaster and auto-brightness working fine.. if the wifi works I can use the jui as daily driver..Help! Please!
vulturext said:
Installed this on JUI Mod Cool Play 6. Fixed my Magisk but Wifi and Wifi Tethering is broken.
Click to expand...
Click to collapse
Hey dude have u found the fix for IR for cool play 6 rom...i think coolplay 6 jui roms are best if we get to work the ir..
Friends we can finally use dual camera in any custom rom.
Install using Magisk.
If it does not work at the first attempt it is recommended to return to the stock rom and then install the custom rom.
That way everything will work without problem.
Venezolano desde Argentina.
Hmmm... Portrait mode on rear camera not working... It fc app.. Aosip
Works
I am on RR
adag1 said:
Hmmm... Portrait mode on rear camera not working... It fc app.. Aosip
Click to expand...
Click to collapse
Work on PE and EvolutionX
Portrait mode no work in RR
Force Close
leechgid said:
Portrait mode no work in RR
Force Close
Click to expand...
Click to collapse
Strange. I am on the latest build, with DragonHeart Kernel. All seems to work fine.
Portrait mode no work in Bootleggers 4.2
Force Close
Does this cam crashes frequently? I know cameras have been always the most difficult part o custom roms, I am still on stock only for the camera, other roms I tried (with a mi a1, to be honest) crashed when I need to take a quick picture... Also tried the GCam, it has better quality but it was worse at the end, it broke the whatsapp camera taking green pictures and random crashes were common. I would really like to install RR or any other rom, but the camera is dragging me back.
I wish there would be a debloated stock rom (no GAPS and the few xiaomi extras) just for keeping the camera working normally, but noone has done it (and I am far for been able to )
DARKEASC said:
Does this cam crashes frequently? I know cameras have been always the most difficult part o custom roms, I am still on stock only for the camera, other roms I tried (with a mi a1, to be honest) crashed when I need to take a quick picture... Also tried the GCam, it has better quality but it was worse at the end, it broke the whatsapp camera taking green pictures and random crashes were common. I would really like to install RR or any other rom, but the camera is dragging me back.
I wish there would be a debloated stock rom (no GAPS and the few xiaomi extras) just for keeping the camera working normally, but noone has done it (and I am far for been able to )
Click to expand...
Click to collapse
I get green tinted photos when I zoom in this camera app. Otherwise, I encounter no crashes or other problems.
Fix for the color bug:
Set the HDR mode to "live".
Portrait Mode is absent on AOSiP ROM
Portrait mode does not work on back camera.
Front camera has color bug. But, if hdr turn on or in portrait mode it works fine.
On superior OS
I got bootloop after flash this module in magisk 19.4 on (AEX) AOSP Extended v6.7 Is working only on LineageOS based roms?
lars00 said:
I got bootloop after flash this module in magisk 19.4 on (AEX) AOSP Extended v6.7 Is working only on LineageOS based roms?
Click to expand...
Click to collapse
Miui camera works with almost every custom rom : Superior , crdroid , POSP , RR (I've tested on them )
Portrait mode crashing with back camera is fixable , you'll need some file explorer with root permissions . The problem is with vendor mismatch , and you'll need to make some changes , here is the walkthrough:
How to solve vendor mismatch bug:
Find string ro.vendor.build.fingerprint in the file /vendor/build.prop, copy the value from it and replace this value to ro.build.fingerprint in the file /system/build.prop ,reboot and portrait mode has to be working , it works for me all the time
Unfortunately I don't know where is the problem. After install this module and restart device, then stuck on AEX boot animation. After uninstall module in Magisk Mnanager 4 Recovery boots again normally For me also not working MI A2 camera port in generic Magisk modules, respectively not all functions, no live image filters, crashing etc. Can't it cause the custom Vendor of AEX rom?
Base lineageos.snap camera and GCam 6.2.030 works fine. I use both of them, it is not the conflict in there?
Thank you for your tips...
lars00 said:
Unfortunately I don't know where is the problem. After install this module and restart device, then stuck on AEX boot animation. After uninstall module in Magisk Mnanager 4 Recovery boots again normally For me also not working MI A2 camera port in generic Magisk modules, respectively not all functions, no live image filters, crashing etc. Can't it cause the custom Vendor of AEX rom?
Base lineageos.snap camera and GCam 6.2.030 works fine. I use both of them, it is not the conflict in there?
Thank you for your tips...
Click to expand...
Click to collapse
Try using this magisk module:
https://drive.google.com/file/d/1po2DDLUifIEJe_zMJvpVXuWch8jffZzw/view?usp=drivesdk
This is stock Daisy camera ,uninstall miui camera from magisk ,then install this zip,reboot and try again
nikoman1987 said:
Try using this magisk module:
.......
This is stock Daisy camera ,uninstall miui camera from magisk ,then install this zip,reboot and try again
Click to expand...
Click to collapse
This link doesn't contain any magisk zip module, this is nova launcher backup file(?). I'm using Lawnchair on Aex.
I have all Magisk modules unistalled before flash MiuiCamera.zip of course, but stuck on AEX screen persist.
I have tried more versions of miui camera, but no satisfying success.
nikoman1987 said:
Try using this magisk module:
https://drive.google.com/file/d/1aSX4odE5fAqtl4ImEwRrDxdkWuABbX_J/view?usp=drivesdk
This is stock Daisy camera ,uninstall miui camera from magisk ,then install this zip,reboot and try again
Click to expand...
Click to collapse
wrong link bro
lars00 said:
This link doesn't contain any magisk zip module, this is nova launcher backup file(?). I'm using Lawnchair on Aex.
I have all Magisk modules unistalled before flash MiuiCamera.zip of course, but stuck on AEX screen persist.
I have tried more versions of miui camera, but no satisfying success.
Click to expand...
Click to collapse
Sorry , copied the wrong link , the link is fixed now
can this work on 10 GSI maybe? i would rather not bootloop