I think this is because of gcc10.2 compiler that I started to use since 3.7 version. Could you try one of default/samsung/proton kernel versions https://cruelkernel.org/release/V3.9-rc1/alt/? They are built with clang. What is the app, btw?@evdenis I've a problem with an app which need access to camera for qr scanning. I've nailed it down to changes that was made in your kernel between version 3.6 to 3.7. This app is working on your kernel up to 3.6, stock kernel, lineage based kernel, all of them with or without magisk. On 3.7 and 3.8 the app don't get access to camera and the phone freezes and reboots.
If you would like to look at it I would gladly provide you with logs. In that case which log do you need for investigate the problem?
The app is bankid, it's for verification during different economic transaction here in Sweden.Hi,
I think this is because of gcc10.2 compiler that I started to use since 3.7 version. Could you try one of default/samsung/proton kernel versions https://cruelkernel.org/release/V3.9-rc1/alt/? They are built with clang. What is the app, btw?
What is this? Camera error? Kernel logs can help. After reboot caused by camera error you need toerror 1
# With adb
$ adb shell su -c "cat /proc/last_kmsg" > kernel.log
# or with termux
$ su
$ cat /proc/last_kmsg > /sdcard/kernel.log
error 1 was in twrp when i tried to flash .zip fileWhat is this? Camera error? Kernel logs can help. After reboot caused by camera error you need to
And send kernel.log file to me.Code:# With adb $ adb shell su -c "cat /proc/last_kmsg" > kernel.log # or with termux $ su $ cat /proc/last_kmsg > /sdcard/kernel.log
This is completely unexpected. What TWRP version do you use?error 1 was in twrp when i tired to flash .zip file
As I mentioned previously, the camera error seems to be because of gcc10.2 compiler (arter97, cruel toolchains).proton, default and samsung img - app can access camera
log attachedThis is completely unexpected. What TWRP version do you use?
As I mentioned previously, the camera error seems to be because of gcc10.2 compiler (arter97, cruel toolchains).
I've just tested it. All installers work, no error 1.Latest official twrp from corsicanu
vbmeta wasn't flashedI've just tested it. All installers work, no error 1.
Did you install multidisabler, flash empty vbmeta?
I have this problem too....Hello, after i flash the img of cruel 3.6 it's all good. but when i restart my phone it goes back to stock kernel. how do i fix this?
There are two possible reasons for this. Either you use combo button during boot. You don't need to hold buttons during boot with this kernel. Either your rom (for example, BeyondRom) forces reboot with kernel from recovery partition. This can be changed in ROM if during installation you choose in aroma non-patched services to install.I have this problem too....
help....pls...
+cifs using the (fantastic) Github action.samba shares using busybox mount, nor is CIFS included in the kernel configuration:# cat /proc/version
Linux version 4.14.113-Cruel-V3.9+ ([email protected]) [...]
# zcat /proc/config.gz | grep -i CIFS # returns nothing
Value requested for CONFIG_CIFS not in final .config
Requested value: CONFIG_CIFS=y
Actual value:
Hi, could you post the github link? This will help me to debug the problem. Thanks!Edit: I can see in the github logs that the +cifs configuration values appear to be overwritten, or are otherwise lost:
Code:Value requested for CONFIG_CIFS not in final .config Requested value: CONFIG_CIFS=y Actual value:
Thanks for getting back. The issue was thatHi, could you post the github link? This will help me to debug the problem. Thanks!
CONFIG_NETWORK_FILESYSTEMS=y needs to be set in cruel+cifs.conf. Let me know if you need anything else.On a side-note, I have to say that working with the code-base and build setup was absolutely fantastic! Thanks.PRs are welcome. Yes, please add it in cruel+cifs.conf Thanks!