Thanks.
Thanks.
Install Magisk canary and Magisk build props to hide.Hi everybody,
first of all thank you for best ROM! Everything runs smoothly and nice.
But I'm trying to solve an issue with SafetyNet because checking it in Magisk Manager gives
"SafetyNet API Error
basicIntegrity -
ctsProfile -
evalType N/A".
Checking the status in app SafetyNet Checker gives:
"Basic Integrity Success
CTS Profile Match Failed
Response Signature Verification Success"
I really don't know which way should I go to resolve that issue. I was trying doing step by step
https://xdaforums.com/t/working-mag...s-17-1-22-on-pie.3929950/page-9#post-79643248
installing SafetyNet Fix gives bootloop
https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
Now I have no clue to do it. Could somebody help?
I will be grateful for any help.
Thnak you Aga.bogdan for your help.
In props selectThnak you Aga.bogdan for your help.
I have installed Magisk Canary Manager first, again flashed Magisk.zip on twrp. Next I've install Magiel Prop Module and enabled Magisk Hide. I've used Hide for Google Play Services and Google Pay (fresh install). Ten opened Termux, props and used signature for Samsung S9 android 10 because there was no 11. Now I've got this means "incorrect certificate". View attachment 5304775
Google Pay does note work of course. Am I doing something wrong?
Same hereHi there, I'm using this ROM for some weeks now. I just figured out two bugs, one is very disturbing the usage of the phone. I use an SD card of 128GB formatted with exFAT. When connecting with USB and enabling the file transfer the phone immediately reboots.
Thanks but what I meant was if the phone is rebooting without SD card inserted as well.@geronimoge Yes, the card works in a standard card reader. Even when booting the phone into TWRP 3.5.2_9 I can access the card via USB.
I've tested this. It is also rebooting without an SD card.Thanks but what I meant was if the phone is rebooting without SD card inserted as well.
Thanks, so the problem of rebooting isn't related to SD cards.
I used the NikGapps-core-arm64-11. No errors since the last update.With latest build I get " app won't run without Google Play services, which are not supported by your device" when I try to run an app that uses Google Maps. Though I have Google Apps installed with MindTheGapps-11.0. Anyone else experienced this?
Thanks for the answer. Indeed with NikGapps it's working fineI used the NikGapps-core-arm64-11. No errors since the last update.
In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.Don't mean to be a jerk, simply stating my choices. The person who made this unoffical rom has been online several days this past week and has given us zero communication on future updates.
I'll be heading to arrow os soon.
Don't mean to be a jerk, just do what u want... silentlyDon't mean to be a jerk, simply stating my choices. The person who made this unoffical rom has been online several days this past week and has given us zero communication on future updates.
I'll be heading to arrow os soon.
Hi,would you mind specifying exactly what you did to build this? I am using the lineage for microg docker based build and it currently succesfully builds 17.1. I would like to build 18.1 with OTA and sign it myself and provide the OTA like you do.
There are fragments of info across this thread, it would be great if you or anyone else can put them together.
Thanks!
mkdir -p ~/bin
mkdir -p ~/android/build
mkdir -p ~/android/build/src
mkdir -p ~/android/build/ccache
mkdir -p ~/android/build/keys
mkdir -p ~/android/build/logs
mkdir -p ~/android/build/zips
mkdir -p ~/android/build/manifests
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
“if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi”
cd ~/android/build/src
git config --global user.email "you@example.com"
git config --global user.name "Your Name"
source ~/.profile
repo init -u https://github.com/LineageOS/android.git -b lineage-18.1
repo sync
PRODUCT_PROPERTY_OVERRIDES += \
lineage.updater.uri=https://raw.githubusercontent.com/<Your_username>/OTA/lineage-18.1/starlte.json
...
<project name="synt4x93/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" revision="lineage-18.1" />
...
repo sync
subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/emailAddress=android@android.com'
cd ~/android/build/src
for x in releasekey platform shared media networkstack testkey; do \
./development/tools/make_key ~/android/build/keys/$x "$subject"; \
done
make a copy of the “keys” directory and keep it safe.
docker pull lineageos4microg/docker-lineage-cicd
docker pull pakaoraki/docker-lineage-cicd
docker run \
-e "BRANCH_NAME=lineage-18.1" \
-e "DEVICE_LIST=starlte" \
-e "INCLUDE_PROPRIETARY=false" \
-e "SIGN_BUILDS=true" \
-v "~/android/build/src:/srv/src" \
-v "~/android/build/zips:/srv/zips" \
-v "~/android/build/logs:/srv/logs" \
-v "~/android/build/ccache:/srv/ccache" \
-v "~/android/build/keys:/srv/keys" \
-v "~/android/build/manifests:/srv/local_manifests" \
pakaoraki/docker-lineage-cicd
{
"response": [
{
"datetime": 1627204505,
"filename": "lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
"id": "39b85208c5c30edfafd983673a703d60",
"romtype": "UNOFFICIAL",
"size": 608774193,
"url": "https://github.com/<username>/OTA/releases/download/<tag>/lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
"version": "18.1"
}
]
}
I will do my own build anyway if there is no official support so I'm happy to share it. No need to tips but thanks@ElPakoTech
Thanks for your work!
I will test the build and give you feedback.
Nice , if we have a maintained LOS with current security patches.
Have you a paypal adress, that i can buy you a beer?
Regards
dreas
To check for security update version of Lineage 18.1 before building your own: https://github.com/LineageOS/android_build/blob/lineage-18.1/core/version_defaults.mk#L2435th July security update ready on this build if you are compiling your own.
How to check when its available besides going thru the make process and checking
~/android/build/core/version_defaults.mk
once complete for the security update date ?
Also checking the
//source.android.com/security/bulletin
for the monthly date and
https://lineageos.org/blog/
changelog
isnt helpful. How to know what patch is ready to build before I go thru the whole process ???
Need to keep the device patched to the latest at all times to be able to use as a daily for work
In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.Don't mean to be a jerk, simply stating my choices. The person who made this unoffical rom has been online several days this past week and has given us zero communication on future updates.
I'll be heading to arrow os soon.