Today I faced the problem that the CPU-load was permanently higher than normal approx about 5 minutes after booting up. The device didn't get cold and consumed about 16% of the battery in one hour. A wakelock. With the help of "top" I found out, that it has something to do with what's called "vaultkeeperd" and/or "com.samsung.android.kgclient".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While searching a bit around I found an interesting looking folder called LOGS with some files in it: "/data/user/0/com.samsung.android.kgclient/files/LOGS/".
From there I was able to see the following:
2023-06-05 20:37:43 : 16956|17878 : [Alarm] created : PROCESS_CHECK period: 180000 network condition: true
2023-06-05 20:37:44 : 16956|17878 : @setRlcClientData() [-5]Error from VaultKeeper (write/ -106)
2023-06-05 20:37:44 : 16956|17878 : [Alarm] created : RETRY period: 300000 network condition: true
2023-06-05 20:37:44 : 16956|17878 : [Retry Cause] Cannot connect to Cert Server
2023-06-05 20:37:44 : 16956|16956 : updated list: add? true, [com.samsung.android.kgclient.action.STARTMESSAGETOCHECKLOCK]
2023-06-05 20:37:44 : 16956|17878 : updated list: add? false, []
2023-06-05 20:37:44 : 16956|17878 : onHandleIntent action : com.samsung.android.kgclient.action.STARTMESSAGETOCHECKLOCK
2023-06-05 20:37:44 : 16956|17878 : [Alarm] created : PROCESS_CHECK period: 180000 network condition: true
2023-06-05 20:37:44 : 16956|17878 : @setRlcClientData() [-5]Error from VaultKeeper (write/ -106)
2023-06-05 20:37:45 : 16956|17878 : [Alarm] created : RETRY period: 300000 network condition: true
2023-06-05 20:37:45 : 16956|17878 : [Retry Cause] Cannot connect to Cert Server
2023-06-05 20:37:45 : 16956|16956 : updated list: add? true, [com.samsung.android.kgclient.action.STARTMESSAGETOCHECKLOCK]
2023-06-05 20:37:45 : 16956|17878 : updated list: add? false, []
2023-06-05 20:37:45 : 16956|17878 : onHandleIntent action : com.samsung.android.kgclient.action.STARTMESSAGETOCHECKLOCK
Click to expand...
Click to collapse
My first idea was that "AFwall+" might have something to do with it. But in this case it was "AdAway". During the initial setup of AdAway, I obviously carelessly blocked some suspicious looking URLs. Compares to Netguard you can't see what App requested which URL.
At hybrid-analysis.com I saw, that among other URL's some with "*.secb2b.com" are getting contacted. It seems to have something to do with Samsungs MDM solution. After whitelisting this URL the issue was gone.
I never did something with ADB and Android before. Maybe someday my post will help someone with a similar problem. I'm also happy about further tips and tricks to solve such wakelock issues faster.
Regards
Chris
If you're using AFWall+ or another firewall solution please also ensure that you allow network access to "Device Services" (ID: 10079) .
Related
This is an old mod for GingerBread kernel makers I've never mentioned - so it may have been found by now - but I've noticed it may be of use for cf-root (and possibly others) after testing out XXJW4 2.3.6 and cf-root 4.4 JW4, which I'll use in the example.
Dial *#2663#
You'll see "TSP threshold: 40"
Goto cf-root and select Touchscreen Sensitivity. Reboot
TSP threshold now = 35 as it should. Connect power cord or USB. TSP threshold now = 70. Disconnect. TSP threshold now = back to 40 = :-(
Samsung opensource file to edit (my settings):
/drivers/input/touchscreen/qt602240.c
OLD=default - NEW=my custom setting
line 247:
OLD: touchscreen_config.tchthr = 40;
NEW: touchscreen_config.tchthr = 38;
line 249:
OLD: touchscreen_config.tchdi = 2;
NEW: touchscreen_config.tchdi = 1;
line 253:
OLD: touchscreen_config.movhysti = 3;
NEW: touchscreen_config.movhysti = 2;
line 308:
OLD: touchscreen_config.tchthr = 40;
NEW: touchscreen_config.tchthr = 38;
line 310:
OLD: touchscreen_config.movhysti = 3;
NEW: touchscreen_config.movhysti = 2;
And the lines that mess things up when USB is connected/disconnected...
line 2441:
OLD: touchscreen_config.tchthr = 70;
NEW: touchscreen_config.tchthr = 38;
line 2442:
OLD: noise_suppression_config.noisethr = 20;
NEW: noise_suppression_config.noisethr = 30;
line 2445:
OLD: touchscreen_config.tchthr = 40;
NEW: touchscreen_config.tchthr = 38;
Hopefully this is of value to someone.
There is a app called SGS Touchscreen booster..
Faster and same result..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
silitek said:
There is a app called SGS Touchscreen booster..
Faster and same result..
Click to expand...
Click to collapse
No, after connected charger the still values up to 70....
@Ipy, Could u make a cwm package for your mod
cwc289 said:
No, after connected charger the still values up to 70....
@Ipy, Could u make a cwm package for your mod
Click to expand...
Click to collapse
I do have a kernel which I never posted - it's basically a variation of hardcore's SpeedMod kernel, minus a couple of mods, and the addition of the mod I have described above (in case anyone asks about the source code).
Works well with JVU 2.3.6, but NOT JW4 2.3.6
Changing kernels can produce unpredictable results, so at your own risk:
[ROOT] [GUIDE] [CWM] FOR Wing Hero V45 - Wing Hero 40S [ MTK 6572] 100% Working Root
Hello , I am from Vietnam
Here , I will guide you how to root and install CWM RECOVERY
Info My Devices
Hardware : MTK6572
Chip: Media Tek
Model : V45
Build number : SW_T97057Z3_M11_WINGTECH_V009_20141028
Build date UTC : 20141027-134105
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V43, 2014/07/18 11:38
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Oct 27 21:38:09 CST 2014
Click to expand...
Click to collapse
Here are the procedures
1. Download Files Given Below.
2. Install Drivers From " Tools And Drivers.rar "
3.Open SP flash tool and load Scatter "MT6572_Android_scatter.txt"
4.Chose recovery_cwm.img and make tick only on recovery.
5. Click on download
6. Connect phone with "USB Debugging on"
7.Double click on "RUN.bat" from " Tools And Drivers/adb/" (press yes if phone asks for permission)
Flashing will start
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video Demo:
Cách ROOT và Cài CWM WING HERO 40S - WING HERO V45 [MTK6572 - 4.4.2] by Hưng Thịnh
Now For Rooting
1.Put "UPDATE-SuperSU-v1.94.zip" in your sdcard
2.Connect phone with debugging ON
3.Double click on "RUN2.bat" from " Tools And Drivers/adb/"
4.You'll be in recovery mode now "install zip" and choose "UPDATE-SuperSU-v2.46.zip"
5.Your Phone is now rooted reboot enjoy.
6.Hit Thanks.
Download
SP_FLASH TOOL: Download
không được bac ơi
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Axyn kernel
Compatibility :
OneUI3.X Y (GSI A11 y A12)
Features V2:
first kernel to have OC on A51
•OC CPU Big 2.50ghz / Stock 2,31ghz
•OC CPU LITTLE 1.85GHZ / Stock 1.74ghz
•More undervolting on CPU / GPU / DDR / MIF / INT Heat reduction and to make the battery last a little longer
•VM-SWAPPines a 160
•GFS disabled for better performance
•Add ZRAM LRU Ported of the A52
•Schen Reduce latency for better responsiveness
•Add IOSHED:
FIOPS
SIO
ZEN
ANXIETY
Maple is defaul
•Add CPU GOVERNORS
Interactive makes the battery last a little longer
•Introduce KernelSpace baterry saver mode
•PowerSuspend 2.0 adapt exynos 9611
• Updated LZ4 for better understanding and decompression
•Dinámy FSys 1.5
•Wakelock switche
•Boeffla Wakelock Driver v1.1.0
•State notifier
Features V1:
• Android kernel 4.14.130
• Default LZ4 in ZRam
• Fingerprint boost
• Lantecia reduction
• Fsyn on / off
• Fsyn off
• CRC on / off
• Optimize consolé frame buffer
• Maple set As default, better performance and balance with battery
• Undervold CPU / GPU / DDR
• Mali optimized
Instructions:
•Download zip
•Enter TWRP recovery
•Flash zip
•flash rmagisk for root(optional)
•Reboot and enjoy
Credits:
@osm0sis Anykernel
@CliffVale my tester
@ViorelFarcas my tester
@Melanie for helping me
@BlassGO for VolumenUp_to_Recovery
@Yilliee For being a great person and being attentive to the development in A51 and also for reading all my messages where I explained my problems :v hehehe you are a good person
@Adolf24 for me for spending hours dedicating time to the kernel
known issues:
Error when entering twrp from magick, normally I don't use it, but if you want to use twrp use this blassgo file so that you enter twrp with the buttons
VolumeUP_to_Recovery: https://drive.google.com/file/d/1-A1LKND7A69Ufwka5YSiUu3XYHIZtKil/view?usp=drivesdk
Note:
Will there be V3? possibly yes or in the distant future maybe on Oneui 4.x and give it a ping to motivate me to keep adding features and optimizations
Thread closed.
I've attempted to come up with a workaround fix for this, but I am coming up short. I'm familiar with Linux, however Android seems to work a bit different than pure Linux. Here is where I am at this point.
At first, I thought maybe the RFKILL command was soft locking the wifi module. I've attempted to run "rfkill unblock all", however even with root access, the shell doesn't have access to this command. I don't believe this is what is happening at this point.
I am unable to get the dmesg logs or event logs when the WiFi doesn't work due to the fact the application I use to get them doesn't allow local storage. Not sure why. However, I've taken pictures and can simply type what I see.
D WifiClientModeManager: expected stop, not triggering callbacks: newState = 1
E WifiNative: Could not get Iface object for interface null
D WifiActiveModeWarden: ClientMode failed, return to WifiDisabledState
D WifiController: ClientMode unexpected failure: state unknown
D WifiP2pService: Wifi enabled=false, P2P Interface availability=false
D WifiClientModeManager: currentstate: IdleState
D WifiScanRequestProxy: Sending scan available broadcast: false
I WifiScanningService: wifi driver unloaded
I apopt : mBtServiceReceiver onReceive a:android.net.wifi.WIFI_STATE_CHANGED
i apopt: onReceive, Extras: previous_wifi_state = '4', wifi_state = '1',
I zj : state change, state: 1
I WifiScanRequestProxy: Scanning is disabled
D WifiActiveModeWarden: Entering WifiDisabledState
E HalDevMgr: IWifiEventCallback.onFailure 9 ()
D WifiActiveModeWarden: received a message in WifiDisabledState: { when=-4ms what=3 target=com.android.internal.util.StateMachine
D WifiActiveModeWarden: Switching from WifiDisabledState to WifiDisabled
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know this is awful looking but it was the only way I could get the information.
It looks like something might be failing with the WiFi drivers. Is anyone here familiar enough with Android to know if there are ways to change them out. Or is there a command I could run to simply perform a refresh of the drivers? At this point I don't believe it's the hardware since when it works, it works great. It just fails to start sometimes.
Send it back
Check this recent firmware released to solve BT and wifi:
ha3_rk3399_10.0_ota(20220329+蓝牙MCU专用包).zip
Shared with Dropbox
www.dropbox.com
HEY ALL I HOPE YOU ARE FINE HERE !!!
WELCOME TO OUR FORUM FOR LawRun-Kernel For Poco F3 - Alioth
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/* I'm not responsible for any damage on your device, for X or Y reason, also I'm not responsible if you loose your alarm and got fired, anything like that, installing this kernel you renounce to make me responsible of any unwanted behavior of your device */
First-
Introduction
WHY WE BUILD THIS KERNEL --- THE MAIN VALUE OF THIS
we tried to give you the best experience of your phone as the following
in my opinion you will not be satisfied with the phone with the gaming kernel without the battery were last alot of time
in the same side you will have a great performance...
Secondly-
IF YOU HAVE ANY PROBLEM WHILE YOU ARE USING KERNEL JUST TRY TO TEST IT
WITHOUT ANY MODULE, CLEAN FLASH IT & TRY IT Clearly FOR Enough time...
Thirdly-
Kernel Features
- Built with android Clang
- AnyKernel3
- MIUI & Custom rom supported
- Westwood TCP
- I/O schedulers Deadline default
- Separated magisk Profile .zip for enabling profiles on our app
- Optimisations from other kernels
- More and more features check changelogs
Planned Features
IF YOU WANT TO ADD SOME FEATURES OR HAVE ANY PROBLEM YOU CAN CONTACT ME AT Telegram
YOU CAN JOIN OUR TELEGRAM GROUP FOR MORE INFO AND SUPPORT
Fourth-
WHERE IS THE DOWNLOAD LINK
Kernel..: Link
Profiles..: Link
App..: Soon
for more features like app, profiles & performance modules...
Our Telegram Channel... Link
Our Youtube channel... Link
Our Telegram Group... Link
&&
MY DONATION LINK
Our donation: Link
Fifth-
Bugs
-Dont Know :')
Finally-
LawRun App
We are Introducing our New App You can use it For better experience
You can find it in our Website too..
####Installation_guide####
to Get a better experience
- Dirty Flash your rom or boot.img / reboot to recovery
- FLash Magisk ((Recommended))
- Flash Kernel / reboot to recovery
reboot and enjoy
Thanks TO BE HERE AND ALWAYS BE READY TO RUN!!!!!
Source: Link
Version Information
Status: Stable
Created 2023-06-05
Last Updated 2023-06-05
Reserved
Reserved...
does it support Kernel SU ?
ndez said:
does it support Kernel SU ?
Click to expand...
Click to collapse
Nope we will add it as soon as possible