How do I run script on schedule, for example daily at 4 o'clock?
You can try Tasker.
amplatfus said:
You can try Tasker.
Click to expand...
Click to collapse
I want to do it via magisk module tho thx for the answer
There was a cron module, but it hasnt been actively developed in years, so ymmv...
GitHub - liangsai12/crontab: Magisk crontabs
Magisk crontabs. Contribute to liangsai12/crontab development by creating an account on GitHub.
github.com
if you try this, you may want to edit the timezone line in /common/service.sh
export TZ=Asia/Shanghai
an alternative may be this, but also, not developed in years:
crond | F-Droid - Free and Open Source Android App Repository
Schedules scripts
f-droid.org
Related
I have to know a couple of things about xposed.
is this a open source or not?
what kind of risk can you get from using this especially concerning privacy.
I would imagine wrt privacy.... It could compromise everything as modules have access to just about everything. Most popular modules are open source, and the source for the framework itself is posted on github and linked to from the read only thread.
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
scryan said:
I would imagine wrt privacy.... It could compromise everything as modules have access to just about everything. Most popular modules are open source, and the source for the framework itself is posted on github and linked to from the read only thread.
Click to expand...
Click to collapse
so in theory it's safe just as long as you use open source modules.
and framework isn't doesn't have security risk because it's open source
Syncing accounts issue
After installing Adaway for YouTube and Bootmanager if I try to sync my Google account or any account, it will not sync. Is this a known issue or am I missing something?
Just because it's open source it doesn't mean it's safe, it means you can audit it's source code. It doesn't mean you won't have vulnerabilities that can be exploited just because "someone will read it's source code". Even libraries that are used across all internet have problems, like http://www.openssh.com/security.html.
Somewhat related, that's why I'm asking here http://forum.xda-developers.com/xposed/jars-xposedinstaller-t3300963 about the nature of some jars, some zips and such in the source code.
Hello everyone!
I created a fork of the Magisk Module Template to facilitate the development of Magisk modules!
The current changes are:
Install app in /data/app
Scheduled changes:
Installation in /system if Magisk is not detected
Installation in /system if the module developer sets it up
AROMA included with easy configuration
Module installation in module (in common/module)
If the module developer enables a specific option, the template identifies the cpu architecture and installs the specific files (put by the developer in common/arc/<name-architecture>)
If the module developer enables a specific option, the template identifies the phone model (ro.product.device) and installs the specific files (put by the developer in <common/phone/phone-model>)
The Complete guide with technical explanation is available here: https://github.com/PurifyOS/magisk-module-template/blob/master/README.md
Repo for clone template: https://github.com/PurifyOS/magisk-module-template
reserved
reserved
Reserved
Reserved
I was just looking through your repo on GitHub and suddenly there's this thread. Looks really interesting. Gonna be interesting to follow... :good:
Didgeridoohan said:
I was just looking through your repo on GitHub and suddenly there's this thread. Looks really interesting. Gonna be interesting to follow... :good:
Click to expand...
Click to collapse
Thanks
Have any plan to make a Xposed SDK25 ARM64 Magisk Systemless for AEX or AOSP please ? waiting for it
洛城天使 said:
Have any plan to make a Xposed SDK25 ARM64 Magisk Systemless for AEX or AOSP please ? waiting for it
Click to expand...
Click to collapse
For aosp xposed work
CottonmouthOS
A security and privacy focused mobile operating system based on CopperheadOS that is MicroG friendly.
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
This ROM is based on the great CopperheadOS ROM with signature spoofing enabled to allow MicroG framework. There will be changes to make the signature spoofing spoof ONLY the Google service signatures and ONLY usable/allowable by MicroG services ONLY. The new name CottonmouthOS is a way to distinguish from CopperheadOS builds, because of the signature spoofing patches.
Prerequisites coming from other ROMs :-
Have latest March factory image installed.
Instructions :-
Download the CottonmouthOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Features of CopperheadOS ROM
Note :-
CottonmouthOS is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team
Mar-V-in for MicroG
razorloves for inspiration
References :-
Copperhead homepage
Documentation
Instructions used to build
Sources
MicroG patch
If anyone wants to reupload to a better file hosting site please do.
OLD OP
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
- Mirror 1
- Mirror 2
- Mirror 3
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
Does copperhead have the pixel navbar animation?
File not yet uploaded
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
+1
ChongoDroid said:
File not yet uploaded
Click to expand...
Click to collapse
That is strange. Will reupload.
EDIT: Done see OP
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
ChongoDroid said:
I've always wondered something, since COS charges money for phone flashing and the only way to get it yourself is to compile it yourself and flash. Once you flash your self compiled build, do you have to build the updates or does the built in updater work?
Click to expand...
Click to collapse
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
jahrule said:
I didn't see the updater, and even if it was there the keys would not match so you would not be able to update.
Ideally, we would put this on a build server and release the full install and OTA every time there was an update so we would get the updates within a few hours of official. A few changes could be made to either change the updater (if it is there, which I did not see it) or use lineageOS one and modify it to point to the release server.
Click to expand...
Click to collapse
Yeah CopperheadOS uses the stock recovery iirc. They do it like this to use verified boot iirc. I personally loved COS on my Nexus 5 and missed it on my pixel.
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Thank you for building this, I tried and failed miserably. Will flash it today :good:
Fdroid Keys and BuildSystem
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
KShion619 said:
how likely are weekly builds for this rom? also did you find a workaround for the F-Droid extension? I tried manually removing it and disabling it via twrp, but it seems to restore itself or simply refuse to delete, showing as deleted from within twrp
Click to expand...
Click to collapse
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
smilingtux said:
Thanks for building.
Please add your keys to the fdroid whitelist.
Could you write/post about your build system?(Like a Howto)?
Click to expand...
Click to collapse
Please see the build instructions in the op that I posted.
Ideally, I would like to make another rom that has the restricted sigspoof added so we could have an option for microg
jahrule said:
The fdroid extension needs the keys as I pointed out in the 2nd or 3rd post notes. Regular builds would require a build server but a build server costs money. So, will try to update when I can.
Click to expand...
Click to collapse
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
KShion619 said:
Meant like a user-doable way until the keys updated, I'm fine with the full screen dialog for now
Click to expand...
Click to collapse
The keys are compiled in so, no.
jahrule said:
Please see the build instructions in the op that I posted.
Click to expand...
Click to collapse
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
smilingtux said:
I have seen and read it before
I setup an build host based on copperheads documentation, I read about the java whitelisting of my keys for fdroid, but the build process itself fails from time to time.
So my question was more about, how did you manage to setup a reliable environment for building. What OS did you use, installed dependencies etc.
Click to expand...
Click to collapse
You seem to ask for a docker.
Twitter Emojis is BACK!!
Since the original author of the Magisk module for the Twitter Emoji, doesn't maintain it anymore, i decided to maintain it myself.
So here come Twemoji-Remastered!
A Twitter Emoji module maintained for Magisk!
You can view the source of this Magisk module right there
Reserved #1
Here you can find all of the previous and latest version of Twemoji-Remastered in the Release section of my GitHub repo
Reserved #2
Why is this module still Twemoji 13.1, as Twitter has released 14.0?
I'm aware of Twemoji being on release 14, but the upstream didn't updated the package yet, and the script to do it from source is atm very very broken, and i don't have time to fix it atm.
Also they still haven't "officially" updated the emoji to the 14th version yet.
Also atm i don't think it urgent to do it since it just emojis.
Edit: now it is
(Do NOT use this one with the latest magisk) Twemoji-Remastered-14.0.2 is out!!
You can also download it from the GitHub repo
Twemoji-Remastered-14.0.2 is out (again) !!
I've cleaned up the module and it now only compatible with Magisk v20.4+ and above.
You can also download it from the GitHub repo
Just FYI, I've been maintaining the Twemoji module for years on my GitHub at CrystalCommunication/Twemoji-systemless. I hadn't bothered to post it anywhere because I only started maintaining it for my personal phone, but other GitHub users started using the package I maintain, so I started offering automatic updates as well.
CrystalCommunication said:
Just FYI, I've been maintaining the Twemoji module for years on my GitHub at CrystalCommunication/Twemoji-systemless. I hadn't bothered to post it anywhere because I only started maintaining it for my personal phone, but other GitHub users started using the package I maintain, so I started offering automatic updates as well.
Click to expand...
Click to collapse
Cool i guess, well i continued to maintain the orginal twemoji module that was on XDA
hi everyone i would like to ask the developers if they can create a magisk module to take screenshots in protected apps.
do not recommend smali patcher because it sends the smartphone in bootloop I have already tested several times.
you need a module that only allows you to take screenshots in protected apps, only this function.
andrea0807 said:
hi everyone i would like to ask the developers if they can create a magisk module to take screenshots in protected apps.
do not recommend smali patcher because it sends the smartphone in bootloop I have already tested several times.
you need a module that only allows you to take screenshots in protected apps, only this function.
Click to expand...
Click to collapse
you can easily do this with LSPosed framework (which works as a Magisk module) and Disable FLAG SECURE module
Releases · LSPosed/LSPosed
LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.
github.com
Releases · Xposed-Modules-Repo/com.varuns2002.disable_flag_secure
Disable-FLAG_SECURE. Contribute to Xposed-Modules-Repo/com.varuns2002.disable_flag_secure development by creating an account on GitHub.
github.com
First install LSPosed and reboot, then install apk, enable in LSPosed manager for your protected apps and reboot again. Works perfectly fine for me on Android 12