CoreShift
رفتن به کانال در Telegram
Developer-facing tooling only. Not intended for casual or personal use. Assumes you understand shell behavior, Android service boundaries, and the side effects of touching ART, app-ops, system properties, and device_config. Group chat - @diky_IC
نمایش بیشترکشور مشخص نشده استفناوری و برنامهها47 146
699
مشترکین
+324 ساعت
+47 روز
+1430 روز
آرشیو پست ها
696
CoreShift Watchdog
What CoreShift Watchdog Is
Central runtime enforcement daemon for the CoreShift framework Continuously monitors system and application process state Identifies non-foreground, non-whitelisted workloads based on runtime behavior Applies dynamic restriction and correction actions at the process and thread level Protects critical system services and foreground workloads from interference Prevents runaway background execution, excessive wakeups, and resource abuse Designed to run persistently and self-stabilize system performance over time Functions as the last-line safeguard ensuring CoreShift policies remain effective even under abnormal conditionsChangelog
Utilize dumpsys usagestats prevent false kill and compitable with manager to add a pkg whitelist Add a ram threshold so app below 150mb ram usage get spared
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManagerSupport Us Here
SociabuzzDownload Here
CoreShift Frameworks
696
CoreShift Manager
What CoreShift Manager Is
Central orchestration and control module for the CoreShift framework Provides unified CLI tools to configure runtime behavior and module policies Manages application classification lists (doze, game, watchdog) with pattern-based control Applies aggressive power and restriction actions through predefined operational modes Controls lifecycle of CoreShift modules, including start, stop, and status inspection Acts as the single administrative interface for coordinating and supervising all CoreShift componentsChangelog (@koneko_dev)
Introduced WebUI (@koneko_dev) as an additional interface for CoreShift Manager WebUI (@koneko_dev) operates as a frontend layer only; core behavior and CLI remain unchanged Maintains full compatibility with existing CoreShift modules and managers
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift FrameworksCredits
• @ChatGPT • @Koneko_dev
696
CoreShift UClamp (ROOT)
What CoreShift Uclamp is
CoreShift UClamp is a systemless CPU utilization clamp solution that combines: a custom Powerhint.json overlay, a custom taskprofile.json overlay, and a runtime uclamp enforcement layer. All three work together.What CoreShift Uclamp Does
CoreShift UClamp directly defines how much CPU time each execution class is allowed to consume, instead of relying on frequency scaling alone. The tweaks operate on scheduler utilization clamps (uclamp), which control task placement and boost eligibility.
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch
CoreShift FrameworksCredits
• @ChatGPT • @reljawa • @EmanuelCN0 • @Java_nih_deks
696
CoreShift Latency
What CoreShift Latency Is
Thread-level latency controller for the CoreShift framework Foreground-driven latency scheduler Continuously tracks the active foreground application Applies task-profiles only to latency-critical threads main and RenderThread Uses explicit CPU scheduling and cpuset assignment at the TID level Minimizes input-to-frame delay and render jitter Preserves normal background behavior without aggressive global restriction Designed for interaction responsiveness and frame-time consistencyChangelog
In-memory caching to pid for less redundant apply Added fallback foreground Migrate to C and include daemos detection to ensure compatibility and efficiency Better foreground detection latency
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManagerSupport Us Here
SociabuzzDownload Here
CoreShift FrameworksCredits
• @ChatGPT • @reljawa •@AduhaiWelewele
696
CoreShift GameShell Sched
What CoreShift GameShell Sched Is
Foreground-driven scheduler and task-profile controller for the CoreShift framework Automatically reacts to the active foreground app Applies explicit CPU scheduling and cpuset profiles to the active game only Enforces background restriction for non-foreground processes Designed for latency stability and sustained frame pacing This is not a booster toggle. It is a continuous, state-aware scheduler controller.
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift FrameworksCredits
• @ChatGPT • @reljawa • @AduhaiWelewele
696
CoreShift GameShell
What CoreShift GameShell Is
On-demand foreground-aware performance mode for the CoreShift framework Activated automatically when a listed game enters foreground Applies aggressive, explicit performance tuning only during gameplay Restores balanced system behavior when leaving games Designed for sustained gaming sessions, not background automation This is not a passive optimizer. It is a state-driven, foreground-controlled performance shell.
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift FrameworksCredits
• @ChatGPT • @dcx400
696
CoreShift CacheCleaner
What Coreshift CacheCleaner Is
On-demand cache and process purge action for the CoreShift framework Executed only when the action button is pressed Performs an aggressive, explicit cleanup pass Designed for manual recovery scenarios, not background automation This is not a passive or adaptive module. It is a user-triggered maintenance action.
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift FrameworksCredits
• @ChatGPT • @dcx400
696
CoreShift Preload
What CoreShift Preload Is
Predictive execution and warm-up module for the CoreShift framework Reduces perceived app launch latency by preparing runtime state before interaction Triggers only on meaningful state transitions (foreground / home), not continuous polling Executes bounded, concurrency-limited preload tasks to avoid cache and memory thrash Tracks execution history to prevent redundant or repeated work Operates entirely in user space with no kernel hooks or permanent background residency Designed to complement memory compaction rather than compete with it Prioritizes responsiveness without increasing steady-state resource usageChangelog
Migrated all performance-critical logic to native C. Unified control flow under a single native execution path. Reduced shell invocation surface
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManagerSupport Us Here
SociabuzzDownload Here
CoreShift Frameworks
696
CoreShift Compaction
What CoreShift Compaction Is
Centralized memory pressure control module for the CoreShift framework Actively reclaims RAM by forcing kernel and ActivityManager compaction paths Operates dynamically across foreground, background, and cached processes Uses system-level compaction on newer Android versions and per-process fallback on older releases Reduces fragmentation and swap pressure without killing applications Designed for sustained performance stability rather than burst optimization Runs autonomously with minimal wakeups and bounded execution cost Integrates cleanly with other CoreShift modules without overlapping policies
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManagerSupport Us Here
SociabuzzDownload Here
CoreShift FrameworksCredits
• @ChatGPT • @dcx400
696
CoreShift Runtime
What CoreShift Runtime Is
Active execution layer of the CoreShift framework Applies system properties, runtime policies, and tuning states Disables debug, tracing, and profiling overhead dynamically Enforces doze, standby, and background restrictions per app Coordinates cleanup, compaction, and idle maintenance tasks Initializes once after boot and maintains a clean runtime state
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift FrameworksCredits
• @ChatGPT • @Kzuyoo • @Hoyoslave
696
CoreShift Manager
What CoreShift Manager Is
Central orchestration and control module for the CoreShift framework Provides unified CLI tools to configure runtime behavior and module policies Manages application classification lists (doze, game, watchdog) with pattern-based control Applies aggressive power and restriction actions through predefined operational modes Controls lifecycle of CoreShift modules, including start, stop, and status inspection Acts as the single administrative interface for coordinating and supervising all CoreShift components
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift FrameworksCredits
• @ChatGPT • @Koneko_dev
696
CoreShift Frameworks
What CoreShift Is
A unified optimization framework built from multiple components that manage system behavior, enforce performance rules, and provide tools for deeper control. Included Modules • CoreShift Manager • CoreShift Runtime • CoreShift Preloader • CoreShift Compaction • CoreShift Latency • CoreShift UClamp (ROOT) • CoreShift GameShell • CoreShift GameShellSched
Full usage guide here & hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift Essential Coreshift Game CoreShift Control Coreshift QoLCredits
• @ChatGPT • @Koneko • @Hoyo • @Brains • @dcx • @rowjik • @puji • @Zexshia • @reljawa • @bleble
696
CoreShift Compaction
Startup gating Waits for full system boot completion. Waits until SystemUI is running to avoid early-boot interference. Displays a toast to confirm the service is active. API-aware compaction strategy On Android 14+ (API ≥ 34): Uses cmd activity compact system to trigger framework-managed system-wide memory compaction. On older Android versions: Enumerates all installed packages with UIDs. Applies both some and full compaction per app to maximize reclaim. This ensures compatibility and correct behavior across Android releases. Initial compaction Runs a full compaction cycle once after startup. Allows the system to stabilize before entering the monitoring loop. Screen-state monitoring loop Polls screen state periodically using cmd deviceidle get screen. Maintains counters to detect consecutive screen-off or screen-on states, avoiding false triggers. Idle enforcement logic If the screen is detected off twice consecutively: Forces device idle using cmd deviceidle force-idle. Marks idle as forced to prevent repeated calls. Immediately runs a compaction cycle. Sleeps for a long interval to avoid unnecessary churn. If the screen is detected on twice consecutively: Releases forced idle using cmd deviceidle unforce. Returns control to normal Android power management. Periodic maintenance While the screen remains off: Performs scheduled compaction at long intervals to reclaim memory steadily. While the screen is on: Sleeps lightly and avoids compaction to prevent foreground performance impact. Stability guarantees Idle forcing is stateful and reversible. No compaction is spammed. No interaction with foreground apps. No dependency on heuristics like memory pressure or thread count. Net effect Reduces memory fragmentation over time. Improves idle-time memory reclaim efficiency. Preserves foreground responsiveness. Works silently in the background with predictable, bounded behavior. CoreShift Compaction acts as a low-frequency, idle-aware memory maintenance daemon, complementing Android’s own memory management without fighting it.
696
CoreShift Watchdog
Startup gating Waits until Android finishes booting and SystemUI is alive. Starts only after the system is fully usable. Whitelist handling Uses a persistent whitelist file. Whitelisted packages are never touched. Whitelist is the only protection for system apps. Continuous scan loop (every 30 seconds) Enumerates all currently running processes. Skips: itself, empty or malformed entries, whitelisted packages, packages killed recently (cooldown enforced). Decision model System apps (UID < 10000): Standby bucket is ignored. If running and not whitelisted, they are eligible for termination. Third-party apps (UID ≥ 10000): Queries numeric standby bucket. Only killed if bucket > 20 (FREQUENT, RARE, RESTRICTED). ACTIVE (10) and WORKING_SET (20) are never touched. Action Eligible packages are terminated via cmd activity kill. Kill time is recorded per package. Fixed-string state updates prevent regex errors and corruption. Stability controls Cooldown prevents rapid re-kills and restart storms. No thread counting, no heuristics, no guessing. Deterministic decisions based on app state and policy. Net effect Aggressively cleans unused background apps. Enforces strict control over non-essential system services. Preserves foreground apps, recently used apps, and protected components. Maintains long-term system responsiveness and resource headroom.
696
CoreShift GameSet TaskProfile Scheduler
Boot-safe execution with continuous runtime monitoring Foreground-aware scheduling using ActivityManager stack inspection Game-only promotion via curated gamelist (no global boosting) Automatic background demotion for dozelist applications Thread-correct enforcement using settaskprofile (TID-based, not PID-based) CPUSET and SCHED aggregate profile orchestration aligned with task_profiles.json TOP_APP profiles applied exclusively to active foreground games Immediate demotion of games upon foreground loss to preserve scheduler fairness Background applications constrained using BACKGROUND profiles for power efficiency PID de-duplication to prevent redundant scheduler reapplication Periodic reevaluation to track process restarts and thread respawns Thermal-aware boosting gated by battery temperature to avoid boost–throttle oscillation No killing, freezing, force-stopping, or app suspension Scheduler-only behavior: no wakelock, sensor, GPU, or thermal HAL interference Screen-off friendly: no foreground promotion when no resumed activity exists Silent execution without logspam or persistent state files Designed to stabilize frame pacing, reduce scheduler noise, and improve sustained gaming performance while maintaining system responsivenessCredit
@AduhaiWelewele @reljawa
696
Changelog - CoreShift UClamp Scheduler (ROOT)
Boot-completion gated using sys.boot_completed and SystemUI readiness to ensure deterministic startup Cgroup-aware uclamp tuning via /dev/cpuctl with safe existence checks Class-based CPU utilization control: Background / system-background constrained for power efficiency Foreground balanced for responsiveness Top-app aggressively boosted for UI and gameplay RT and critical daemons capped to prevent starvation Process-level enforcement using uclampset with thread-wide application (-a) Dynamic top-app detection via ActivityManager stack inspection Periodic reevaluation to follow app focus changes without relying on static assignments No killing, freezing, or task suspension; scheduler-only behavior Screen-off friendly: foreground boost naturally collapses when no resumed activity exists Silent execution with error suppression to avoid logspam Designed to reduce scheduler noise, stabilize frame pacing, and improve sustained responsiveness without increasing thermal load
696
Changelog - CoreShift Compaction
Boot-completion gating using sys.boot_completed and SystemUI readiness for deterministic startup Android-version-aware behavior: Android 14+: uses cmd activity compact system Android 13 and below: per-package compaction via am compact (some/full) Screen-idle-driven execution using cmd deviceidle get screen to avoid foreground interference Two-step idle confirmation (screen off twice with delay) before triggering compaction Periodic execution with cooldown interval to prevent excessive reclaim pressure Full-package enumeration with UID awareness on legacy versions for correctness Silent execution with error suppression to avoid logspam and crashes No forced killing or stopping of apps; memory-only compaction Designed to reduce RAM fragmentation and background pressure Improves sustained responsiveness and multitasking stability Safe to run continuously after boot with minimal overhead State-independent operation (no persistent flags, no cumulative drift) Consistent behavior across reboots and long uptimes
696
Changelog - CoreShift GameShell
Added boot-completion gating (sys.boot_completed) and SystemUI readiness check for deterministic behavior Dynamic refresh-rate switching using detected device max FPS Automatic foreground app detection with per-state switching (Game / Normal) Game Mode: high refresh rate, reduced animations, ADPF enabled, aggressive frame pacing, thermal override disabled Normal Mode: 60 Hz fallback, balanced animations, ADPF disabled, thermal control restored Renderer alignment (SkiaVK / SkiaGL) without forced overrides MediaTek-specific guards for display/game PQ handling Memory-factor tuning per mode (Game: higher responsiveness, Normal: balanced) Background interference reduction during gameplay State-change guarded application to prevent redundant reapplication Improved stability and consistency across reboots
696
CoreShift Frameworks
What CoreShift Is
A unified optimization framework built from multiple components that manage system behavior, enforce performance rules, and provide tools for deeper control. Included Modules • CoreShift Manager • CoreShift Runtime • CoreShift Watchdog • CoreShift Preloader • CoreShift Compaction • CoreShift UClamp (ROOT) • CoreShift GameShell • CoreShift GameShellSched
Full usage guide hereSupported Managers
• Root: Magisk / KernelSU / APatch • Non-root: AxManager
CoreShift Essential Coreshift QoLCredits
• @ChatGPT • @HoyoSlave • @dcx400 • @Koneko_dev • @Brains82 • @pujipungkas • @AduhaiWelewele • @reljawa • @Zexshia
اکنون در دسترس! پژوهش تلگرام ۲۰۲۵ — مهمترین بینشهای سال 
