The answers below cover only facts verifiable in the current release.
None. Sleepy is an independent open-source Android project with its own repository and maintainer. The two are compatible at the data-format level only: Sleepy can import JSON and share-text exported by WakeUp, and can export WakeUp-compatible JSON.
It is free under the GPL-3.0 license. There are no ads, subscriptions, in-app purchases or paid tiers. The public APK is downloaded from GitHub Releases.
No account, email, phone number or student ID is required. After opening the app you can build a schedule manually or import an existing one.
Schedules and settings are stored on the device. The project integrates no analytics or crash-reporting SDKs such as Firebase Analytics, Crashlytics, Sentry, Bugsnag, AppCenter or Bugly, and does not require a cloud login. Academic-affairs import visits the school site, holiday refresh downloads public date data, and version checks and downloads access GitHub or the project mirror; viewing and editing schedules work offline.
The project is maintained by Lingion. Bugs, new-school adaptations and feature requests go to GitHub Issues; discussion goes to Discussions. When reporting academic-affairs problems, never attach accounts, passwords, verification codes, cookies, tokens or personal schedules.
Minimum Android 8.0 (API 26); target / compile SDK is 37. The release application id is com.lingion.sleepy, debug builds use com.lingion.sleepy.debug; their data is isolated.
The build version derives from Git tags; with no usable tag it falls back to release notes. Your installed version is shown under "About" in the app; public releases are authoritative on the GitHub Releases page.
Release builds provide separately:
arm64-v8a: most modern phonesarmeabi-v7a: 32-bit ARM devicesx86_64: common Android emulatorsuniversal: contains all ABIs above; pick it when the architecture is unknownThe native app in this repository targets Android. There is a separate online trial; it does not imply the web and native Android feature sets are identical. Native platform support follows the project's published artifacts.
First search the full name or alias on the school-picking page, or enter the academic-affairs URL to try identification. If that still fails, open an Issue with the school adaptation template, providing the school's academic-affairs address, failing page and steps. Never submit login credentials or unredacted personal data. The current school list is in docs/schools-list.md; the list and protocols evolve with each adaptation.
The app opens the school's login page in an on-device WebView, the user enters credentials there, and returned schedule pages or API data are parsed. Sleepy does not write academic-affairs credentials into the schedule database. Failure-triage material must also be redacted per the project's adaptation guide.
The current parser supports:
【来自WakeUp课程表】)sleepy-v1 formatThe parser detects the format from content; users never pick an internal protocol name first. Legacy WakeUp data formats remain compatible.
Sleepy's native plain-text exchange format, carrying a chk integrity field used to verify content on import and export. It is not a replacement requirement for the old WakeUp format: existing WakeUp JSON, share text and ICS still import.
Schedules export as WakeUp-compatible JSON, WakeUp share text, ICS and sleepy-v1. On Android 10+ JSON/ICS are written to Download/Sleepy/; on Android 8–9 the app cache plus FileProvider sharing is used, and share text and sleepy-v1 go through the system share sheet. Timetables export as JSON or sleepy-v1. ICS files can be handed to the system calendar, Google Calendar or any iCalendar app.
Yes. On the export page pick a writable calendar on the device and a date range, preview, then confirm; calendar read/write permission is requested only at this step. Rescheduled classes and calendar reminders apply. The experimental first-period alarm depends on calendar app and account support.
"General settings → Data migration" exports a .sleepybackup containing schedules, timetables, preferences and widget configuration. Restore offers merge or overwrite: merge keeps local schedules and appends, but same-name preference keys take the backup's values; overwrite replaces only the schedule and settings modules present in the package, keeping local values for preference files absent from it. A single schedule's JSON/ICS is not a full backup.
The school-picker location button requests foreground location on demand; enabling reminders requests notification permission, with pages offering exact-alarm, battery-optimization and do-not-disturb access entries; writing the system calendar requests calendar read/write; in-app update installation requires unknown-source install permission. Ordinary offline schedule viewing asks for none of these optional permissions.
Yes. Each schedule is stored independently, with its own semester start date, maximum week count and period timetable.
No data is deleted just because the interface shows one layer. The conflict layout keeps overlapping courses; tapping a covered area shows the others; manually adding a conflicting course displays weekday, period, weeks and the conflicting course details.
The most recent schedule-data change; redo restores what was just undone. Switching the current schedule is not a data change and never counts as a course-edit record.
Yes. Timetables support per-period manual entry and derivation from the first period's start, per-class duration, period count and inter-class break template. Different schedules can bind different timetables.
There are five widget families now:
They ship fixed-size variants per launcher; resources currently hold 13 widget configuration XMLs. Rendering uses synchronous RemoteViews + Canvas.
Older versions used Glance's asynchronous SessionWorker, which some ColorOS launchers froze. Since v1.0.29 the main render path is synchronous RemoteViews + Canvas. If a widget still misses refreshes, check launcher permissions, battery limits and notification permission, and refresh the widget manually first.
Theme colors come from the app's theme settings; course colors use a stable golden-angle HSL distribution. After the app theme changes, the app broadcasts widget updates; if the launcher still shows old content, remove and re-add the widget, or check system limits on background and launcher components.
Pre-class reminders accept 1 to 999 minutes, not just a few fixed options. Today summary, tomorrow summary and pre-class reminders are configured separately under "Mine → Reminders".
Holidays and reschedule mappings are managed in general settings; each schedule stores its own reschedules. The reminders page configures date rules independently, and class-time auto do-not-disturb with resume-on-end can be enabled after granting system DND access. Fluid Cloud is experimental; its display depends on system and vendor support.
No. Reminders are scheduled on the device with AlarmManager, offering exact and inexact paths within what the Android version allows; after reboot or app update BootReceiver restores the schedule.
With the app's master reminder switch off, no new reminders are scheduled. Android notification permission remains controlled by system settings; if notifications are intercepted by the system or vendor battery policy, restore the permission in system settings.
"Mine → Appearance & theme" supports following the system, light and dark modes. Android 12+ can use Material You wallpaper-based dynamic color; devices without dynamic color use preset theme colors.
Yes. Custom themes can be created and edited: primary, secondary, tertiary accent and surface tint. Editing and saving the custom theme in use re-applies colors immediately — no need to tap another theme card first and tap back.
The selection indicator uses a fixed-size slot; selected and unselected states keep the same card layout size, with the selected state expressed through color hierarchy and a check mark.
JDK 17 is required. Linux / macOS:
git clone https://github.com/lingion/sleepy.git
cd sleepy
./gradlew assembleDebugOn Windows use gradlew.bat assembleDebug. The debug APK lands in app/build/outputs/apk/debug/; ABI-split builds generate one file per ABI.
./gradlew testDebugUnitTestTest sources are under app/src/test/, covering parsers, schedule data, conflict layout, week calculation, widget logic, theme contracts and import/export modules. Never put real local accounts, academic-affairs sessions or personal schedules into fixtures.
Read CONTRIBUTING.md and the matching project SOP first, then submit one well-scoped change. New school adaptations must add protocol evidence, redacted fixtures and tests. Use the project-convention author email lingion@hrbeu.edu.cn, and commits carry no Claude attribution trailer.