Yes GrapheneOS only supports pixel devices, as these are the only phones that have a high enough security standard.
Yes GrapheneOS only supports pixel devices, as these are the only phones that have a high enough security standard.
People should stop using .tar.gz or .zip
They both are not horribly bad, but .tar.zst is just the best option we have, as zstandard is pareto optimal
https://insanity.industries/post/pareto-optimal-compression/
I use arch btw
GrapheneOS is the best android custom ROM by far. It is more secure, it gets updated very often and security patches land on my phone faster than I hear about them. It is way more performant than the default ROM that ships with Pixel Phones, my battery lasts for days if I don’t use the phone.
At first I was very sceptical, as I want to be sure I can rely on my phone. But it is super stable, way better than the Samsung ROM I had before.
) Plesse close that parentheses
Ooh I found it a bit confusing as I collapse comments very often, and it looked similar to it
Such an iconic video
https://www.vandelaydesign.com/green-websites/
Those are green websites /s
I just pay the qobuz subscription and use this inofficial script which can download the high res flac files from qobuz. (You can also buy music on qobuz and you get the flac file without drm or so as a download, compared to other services which don’t give you the file itself)
And then I use jellyfin to host my music library. Jellyfin has many music player apps which you can use.
https://github.com/vitiko98/qobuz-dl
https://jellyfin.org/downloads/clients/all
But most of the time I’m just streaming through qobuz directly.
Some relevant links to get you started:
https://github.com/shroudedcode/apk-mitm
https://github.com/emanuele-f/PCAPdroid
https://docs.mitmproxy.org/stable/howto-install-system-trusted-ca-android/
Edit:
also very helpful tool is https://frida.re/
And a little tutorial I’ve found to get you started with the android emulator: https://dev.to/ptisserand/mitmproxy-and-android-emulator-206b
Note, that you can only get root on the images that don’t include google play store.
It’s really not that hard, after you’ve done it once. The first time will include some head scratching and learning about some android gotchas. But after that it will be easy.
Even happened in the comments here
Is there a reason to use this instead of the builtin functionality?
Sure, but I really like to look at this when I’m deciding on wether an open source project is worth to use, if you can see that the author is relatively active.
If you have a variable called exit
you’ve overwritten the function in that scope, and won’t be able to execute it.
e.g.
>>> exit=1
>>> exit()
Traceback (most recent call last):
File "", line 1, in
TypeError: 'int' object is not callable
>>>
This is the code (Github link):
class Quitter(object):
def __init__(self, name, eof):
self.name = name
self.eof = eof
def __repr__(self):
return 'Use %s() or %s to exit' % (self.name, self.eof)
def __call__(self, code=None):
# Shells like IDLE catch the SystemExit, but listen when their
# stdin wrapper is closed.
try:
sys.stdin.close()
except:
pass
raise SystemExit(code)
What happens is that the python repl calls __repr__
automatically on each variable/statement that you type into the repl (except assignments e.g. x = 1
).
But this basically only happens in the repl. So “executing” only exit
wouldn’t work in a python script as it is not calling __repr__
automatically, so better you learn how to do it right than using just exit
in your python scripts and scratching your head why it works in the repl but not in your code.
You didn’t specify the calendar used 🤓, so I’ll go to the year 1401 in the hijri calendar (1980 in the gregorian calendar)
Currently it’s a mix of: (with link to all streaming platforms)
Yes phones need to have at least these requirements to fullfill GrapheneOS standards:
https://grapheneos.org/faq#future-devices