HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
LineageOS
charter
OPEN SOURCE2019–2025
LineageOS / charter

charter

Discover this repository through its Hacker News conversations.

Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
218GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2019-06-30 10:41:06 UTC to 2025-02-08 16:08:51 UTC.

0122019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

3 sources
c0l0·Feb 8, 2025
XDG_CACHE_HOME, as mentioned by numerous other posters, is a good remedy to deal with this kind of cached-artifacts-sprawl - but it does need a will to cooperate and care from the original software developer in the first place, which ain't a given. So does another standard that I've come to appreciate in all software that supports it: CACHEDIR.TAG (https://github.com/LineageOS/charter/blob/main/device-suppor...) - I'm just here to spread the word! ;)
In The practical (Unix) problems with .cache and its friends
h4waii·Oct 7, 2019
This is likely because LineageOS has adopted a Charter, which includes fairly rigorous Device Support Requirements [0] before a device can get Official status. Maintainers and device maintenance have more stringent requirements also. I think this is a step in the right direction. As for old builds being removed, this is completely asinine. and their rationale really doesn't hold any water. You can likely find an archived version for your device, or continue building from source, 14.1 still gets Android Security Bulletin patches, for the time being. 0. https://github.com/LineageOS/charter/blob/master/device-supp...
In The privacy trade-offs of cheap Android smartphones
commoner·Jun 30, 2019
Camera quality depends on both the camera firmware blob and the camera app. On high-end Android phones, the camera app usually makes use of proprietary features on the firmware blob and performs post-processing (such as HDR and bokeh). Other Galaxy S7 (herolte) users seem to have the same problems as you on LineageOS, but it's hard to tell exactly what causes them: https://www.reddit.com/r/LineageOS/comments/8awrcz/herolte_g... Also, the Galaxy S7 is no longer officially supported by LineageOS, since there are currently no active device maintainers: https://wiki.lineageos.org/devices/herolte/ It's difficult to diagnose issues with unofficial builds of LineageOS, because they most likely don't meet the LineageOS device support requirements: https://github.com/LineageOS/charter/blob/master/device-supp... Google Camera's post-processing has
Read the rest
been well-received, and the app has been ported to many non-Google devices, including the Galaxy S7. I'm not sure how well the S7 ports work (especially if your S7 has an Exynos SoC) but XDA Developers has a couple of active threads here: https://forum.xda-developers.com/galaxy-s7/themes Using one of the ports might improve your camera situation. No guarantees, but it doesn't hurt to try. I recommended the first-generation Pixel and Pixel XL because they are the only phones that are currently supported by both LineageOS and the latest version of the official (non-ported) Google Camera app. For people who aren't particular about camera features and quality, the Camera app that comes with LineageOS or any third-party camera app would be adequate, and you can use these with any supported device.
In Freeing My Phone from Google

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.