Search results

Yes, but no luck, the crash happens too early https://github.com/tbalden/android_kernel_msm_redfin/blob/9d491f6119975180bf5e9e4d68e7059b55498463/arch/arm64/configs/cleanslate_cfi_defconfig#L5386

It's normal, but I forgot to clarify it in the original post. This changed when Android 12 came and kernel only safety net pass doesn't work now anymore

At the moment I'm stuck with this, I couldn't yet identify which change causes the unbootable state on monolith kernel build. I can't get logs and this makes this really hard to investigate. I'm thinking about how to resolve this yet

There isn't a difference between those two apps in that regard, so it should work. Which vibrations do you tweak? Notifications in pocket or vibration boost?

- Update Android 13 Stable - 3.4.0 - Update- A13 major upgrade - Update to Asus latest 33.0210.0210.210 update's firmware boot image and sources, 5.4.147 - update built-in hosts file adblocking from Steven Black's repo - All Features work, except SafetyNet CTS pass, that's not possible from...

yes, i check time to time if there's a new fix, but it seems Google ended it as they said earlier. No changes since last update

- Update Android 13 - 2.4.5 - Android T stable 13 - Jan update - sources updated to Jan google update - adblock hosts file updated CleanSlate T 2.4.5 Downloads: Magisk with Kernel manager installation If using a kernel manager like Kernel Flasher, EXKM or FKM, here's an anykernel...

- Update - 1.4.4 - Android T stable 13 - Jan updates - update: latest google sources - adblock hosts file updated CleanSlate T 1.4.4 Downloads: Android T images zip (tp1a 2023-01-05) Pixel7/pro (not flashable, contains images) CS 1.4.4...

- Update Android 13 Stable - 2.4.0 - CleanSlate asus sources update -- sources updated to 2060.65 -- Hosts file updated for KAdaway Two types of installation methods provided. - One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM) - One fastboot ZIP for...

To get the log probably this might work: Get to a working state, and without flashing from exkm instead just temp boot the new boot image, which is also uploaded here besides the kernel flasher zip. When that fails to boot and gets rebooted it will boot the working one with magisk and the sys...

Thanks for the report. It seems something goes off with the new upstream and monolith kernel build. Are you able to grab a crash log from /sys/fs/pstore/ maybe with temporarily booting (fastboot boot boot.img) the image instead of flashing ?

Most likely yes, as the dlkm partition, when installed manually like on Kiri, will be resized and then the ak3 flasher will fail when the dlkm partition doesn't fit any more. Stock vendor dlkm size is by default somewhat bigger and manual flashing will resize it.

If you flash all the partitions in the zip, I think you don't need to revert

No, the kernel only can do the volte trick The other thing needs magisk + some settings being done, which so far I couldn't replicate on kernel side only

removing, 3.10.5 - it's not stable unfortunately. Have to investigate further

- Update Android 13 - 2.4.4 - Android T stable 13 - Dec QPR1 update - sources updated to Dec google update - adblock hosts file updated CleanSlate T 2.4.4 Downloads: Magisk with Kernel manager installation If using a kernel manager like Kernel Flasher, EXKM or FKM, here's an anykernel...

- Update - 1.4.3 - Android T stable 13 - Dec qpr1 updates - update: latest google sources - adblock hosts file updated CleanSlate T 1.4.3 Downloads: Android T images zip (tp1a 2022-12-05) Pixel7/pro (not flashable, contains images) CS 1.4.3...

1. sideload ota from ADB 2. go to bootloader and flash vbmeta with Disable verity/verification to make sure verity is still disabled BEFORE booting 3. flash the kernel again

It's welcome, thanks for sharing. The reason to use hosts is the available multiple vetted sources easily for generating and also the relatively small footprint in kernel changes yet possiblity to solely use kernel without magisk dependencies. On some luckier devices even using the kernel side...

This is only happening on p7 non pro with focaltech touchscreen most probably. I can't say I'm sure I found an issue but there's a locking mechanism in the touch driver with which my change might have interfered with. On 7pro this isn't present.

- Update - 1.4.2 - Android T stable 13 - p7 (panther) support fixes - fix: p7(panther) gestures, flashlight notification and wake lag - adblock hosts file updated CleanSlate T 1.4.2 Downloads: Android T images zip (tp1a 2022-11-05) Pixel7/pro (not flashable, contains images) CS 1.4.2...

I'll have a look at this. Seems like I found what could cause this

It's not possible to do that. The reason is mostly security, as if the file were placed on internal memory to interact with the kernel, a malicious app dev could create an app that would set bad ip addresses for hosts to hijack different ones like banking sites and such. But I'll think about...

For android 11: Checked against the asus provided source code and updated with the changes from 2021-12 update which comes with the .82 updates. Here are the images/ ak3 installer zips: Cleanslate 1.2.12 boot image zipped (unzip before fastboot flashing)...

- Update Android 12 Stable - 2.4.1 - Update- October sec level - Update to Asus latest 31.1010.0411.138 update's firmware boot image and sources, 5.4.147 - update built-in hosts file adblocking from Steven Black's repo - All Features work, except SafetyNet CTS pass, that's not possible from...

Latest update 2050.2050.34 is up for zf9. Kernel sources didn't change, so latest cleanslate should work fine with it.

Using kernel flasher , right? Did it patch successfully? If you used manual flashing earlier, probably it failed because that will resize the vendor dlkm partition and then from kernel flasher that partition might not fit and then it might fail to boot with the Kiri modules that remain in dlkm...

I've uploaded 1.4.1 for testing here: https://forum.xda-developers.com/t/kernel-cleanslate-t1-4-0-s2s-adblock-vib-batterysvr-oct-24.4509793/post-87624675 Both all images zip and Kernel flasher AK3 zip are there.

It's going to be an update here, the kernel will need an update.

Thanks, the issue seems to be related to how screen state is being detected, using the touch driver. The pixel 7 can use fts touch driver, which I didn't patch. I'll do so in the next version, and most probably that will fix this and also the touch gestures

In CleanSlate config app, have you in the end tried the Presets (top right corner mode selection)? Then you'll have a list of presets to choose from, where each has "Filtered mode" enabled, to prevent accidental touches on buttons and all

Possibly then the issue is in the lwis io control driver, something is probably not the same as on p7pro. What could help is to have a log after booting and then switching on Flashlight after first unlocking the device after the reboot. You could dump the log from cleanslate companion with the...

I just meant to ask, which apps are having the notifications when you test. It's not a setup thing, but rather how you tested. Yesterday I tested to make sure it works on my side on latest update. Can you try also the following: in flashlight notifications advanced settings switch off Face...

Well, to be honest I only have p7pro cheetah to test it, so I am not sure if it works correctly on p7 (panther). I thought that there's no difference between the two devices' LWIS camera/flash driver. What type of notifications (apps / call...?) do you use to trigger the flash notifications?

In the Preset setting mode (you can cycle to it in the upper right corner of the config page) you can select preconfigurations for S2S/gestures where it gets set to easier to use values and in a "filtered" mode, where the gesture needs to be started from the corner area and the filtering of...

- Update Android TP1A A13 - 3.10.4 - Android T stable - Update to latest update sources November - adblock hosts file updated CleanSlate T 3.10.4 Downloads: Rooted installer zip, new version with updated AnyKernel installer and Magisk tools CleanSlate T 3.10.4...

Strange. Have you updated to the new November OTA and it happens after that?

- Update Android 13 - 2.4.3 - Android T stable 13 - November update - sources updated to November google update - adblock hosts file updated CleanSlate T 2.4.3 Downloads: Magisk with Kernel manager installation If using a kernel manager like Kernel Flasher, EXKM or FKM, here's an...

FYI, google updated kernel sources, but no changes for the November update for Pixel7/7pro, so the current versions are good to go.

No, it's about boosting that further. If I remember correctly, you can set a few lower haptic vibration levels in stock vibration settings luckily.

Cleanslate config app version 3.2.11 needed for new features: Free version download: https://www.androidfilehost.com/?fid=14871746926876820727 This app version should do the trick :)

First question, which version does it show on the Info page in the app? It should be 3.2.x in the Config app, and 3.3.x in the companion app for this device. If you're using the apps from the play store and it's not these versions then you should join the Beta program for both apps to get the...

Hi, I'm not sure what's happening there, but the second zip with the example script does have all the images in a folder named full_img. Sorry for the confusion, the installation guide in the first post isn't reflecting that structure, but it's all in there. The commands to do are: adb...

Thanks a lot for reporting and the provided info! So I had to re-upload a fixed version. The installer didn't contain boot.img correctly, so it was not flashed with the zip. Updated the original post with the new zip. New URL...

Yes, init_boot partition is now separated and easier to keep/flash. So you can flash it, kernel will remain. Yes, the log of flashing would be of interest, I think there might be an issue with the installer script inside it and the log would probably reveal what's happening. Thanks

What would be of interest here is the log that it produced while installing. I suspect that vendor dlkm didn't flash correctly and so modules might have issues with loading

Which way do you flash the kernel? Manually each partition or with the kernel flasher zip? Maybe one of the partitions didn't flash at all? It wouldn't boot if you didn't apply the disable flags.

Hmm, there might be some confusion on the month as Google labeled it's firmware 220804.031 But this kernel is working well with the latest firmware which is that one, and October security level. So wifi also should work with it. It's weird it didn't work for you. What exactly did it show?

- Update Android 12 Stable - 1.4.2 - CleanSlate asus sources update -- sources updated to 2050.29 -- Hosts file for KAdaway Two types of installation methods provided. - One installer ZIP for magisk rooted kernel flasher apps (like Kernel flasher or EXKM) - One fastboot ZIP for solely...

Thanks, I also had the idea if that it doesn't work out, then I'll upload it here, so I just did that here (I'll link it in the original post as well). :) You can now remove your upload. Many thanks for helping out!