Galaxy Note 4 Exynos trelte-common
Galaxy Note 4 Exynos5433 AOSP Projects
Brought to you by:
ananjaser1211
Menu
▾
▴
Tree [022138] lineage-17.1 / History
Francescodario Cuzzocrea
arco
Read Me
Releases for Samsung Galaxy Note 4 family
Copyright
- Copyright (C) 2015-2017 Christopher N. Hesse raymanfx@gmail.com
- Copyright (C) 2021 ananjaser1211 (AnanJaser)
License
Apache License 2.0 (Apache-2.0) (Located at LICENSE, read more at tldrlegal.com/license/apache-license-2.0)
Device Guide
Head over to our Wiki Device Guide
Releases Notes
Full Changelog History XDA Developers
Downloads
Downloads are hosted at SourceForge
Threads
LineageOS-17.1 | RessurectionRemix | TWRP Recovery
Universal5433 - BUG Reports Guide
Bug reporting for LineageOS-17.1 | RessurectionRemix
How to write issues
- Select the right template for your issue request
([BUG] for bug, [Request] for requests) - Please explain your issue correctly
- Give as much details as possible.
- Low effort issues most likely will be closed.
- Gather logs!
How to gather logs with LoggingKit
- Clone/Fork the repo or download the kit via Releases
[With booted System] - Intended for Crashes, FCs and other SYSTEM Logs
1) 1. For Windows users: Install Universal ADB drivers or Brand specific ADB drivers if you don't have them
2. For Linux and macOS users: To make the files executable, type in Terminal chmod +x and drag the files
2) On your phone enable USB debugging under Developer options
3) Launch your required log type (to find out which logs you should gather, check Legend)
4) Grant ADB Keys
5) Close your log type
6) Launch the needed log, again
7) After recording log, attach the created file to your GitHub issue post.
Legend
| Log type | Description |
|---|---|
| log-ball | Full buffer logcat. Don't use unless requested |
| log-all | Verbose logcat, messy but records everything |
| log-e | Log for Error filter, only shows crashes |
| log-ril | Log for Modem/SIM and other RIL issues |
| log-kmsg | Log for Kernel msg when the kernel panics |
| log-dmsg | Log for Kernel on an active system |
| log-ActiveDmesg | Looping Log for Kernel on active system |
- Being stuck at
"Waiting For Device"means you either did not auth the adb key or your device does not even have debugging enabled - Extra: You can skip step 3/4 by running
ADB_Keys.batif you previously allowed your computer ADB
