ELAD098 said:

>adb wait-for-device root
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
restarting adbd as root

platform-tools>adb wait-for-device remount
remount succeeded

powershell -ExecutionPolicy Bypass -File .\push.ps1 -use_remount
adb server is out of date. killing...
* daemon started successfully *

and is stuck

Click to expand...

Try right click push-OP6T-devices.ps1 (with ih8sn.conf see attached files) and choose run with PowerShell (for Windows : https://aka.ms/powershell-release?tag=stable). It worked for me (safetynet passes and OTA updates work).

EDIT (06/06): After the first reboot, do not forget to clear storage of Google, Google Play service and Google Play Store apps ... and then restart your device ... in order to get Play Protect certification.

Hellera said:

First of all I wish to thanks for this good work. I have only one issue with lineage... boot time takes to long, about one minute. It bother me with wake up phone from power of state (missed clock alarm). I wonder, maybe another kernel will work better?! If yes, Can somebody recomand me another working kernel, please?! Thank you.

Lineage's offline alarm implementation is not working: all it does is boot the phone at the scheduled time, but it is too late for the alarm. And this happens to all their android versions.

The app (clock) must be modified to start the phone 2 minutes earlier so that alarm could work. I have done it in my rom. I even posted my committ there, but it was disregarded... .

optimumpro said:

Lineage's offline alarm implementation is not working: all it does is boot the phone at the scheduled time, but it is too late for the alarm. And this happens to all their android versions.

The app (clock) must be modified to start the phone 2 minutes earlier so that alarm could work. I have done it in my rom. I even posted my committ there, but it was disregarded... .

Thank @optimumpro you for the reply, I knew that, but I thought maybe another kernel will solve this.

Hellera said:

First of all I wish to thanks for this good work. I have only one issue with lineage... boot time takes to long, about one minute. It bother me with wake up phone from power of state (missed clock alarm). I wonder, maybe another kernel will work better?! If yes, Can somebody recomand me another working kernel, please?! Thank you.

Currently, it's set to boot the phone one minute before the actual alarm. On my fajita, it takes only 30 seconds to reach the lockscreen, and as such, PowerOffAlarm works as intended. What exactly do you have installed on your phone that causes it to take longer than one minute to boot?

Hellera said:

Thank @optimumpro you for the reply, I knew that, but I thought maybe another kernel will solve this.

Well. There was another commit on Lineage gerrit doing the same in kernel, but they declined that too... .

Hellera said:

First of all I wish to thanks for this good work. I have only one issue with lineage... boot time takes to long, about one minute. It bother me with wake up phone from power of state (missed clock alarm). I wonder, maybe another kernel will work better?! If yes, Can somebody recomand me another working kernel, please?! Thank you.

It takes about 20 seconds for my fajita to boot, so you must have something that slows down boot on your phone.

syntesys said:

Hi all! Have someone problems with Google Sync? I'm not receiving emails or syncronizing calendar with last build.

I had the same problem with the lineage calendar app. Fixed it by installing google calendar. Now the lineage calendar syncs for some reason, but when I uninstall google calendar, it stops syncing again...
Maybe it has something to do with the Gapps package used, I used MindTheGapps...

Edit I just dirty flashed the newest MindTheGapps package over the existing one and now calendar sync works

Eric_Lev said:

Try right click push-OP6T-devices.ps1 (with ih8sn.conf see attached files) and choose run with PowerShell (for Windows : https://aka.ms/powershell-release?tag=stable). It worked for me (safetynet passes and OTA updates work).

EDIT (06/06): After the first reboot, do not forget to clear storage of Google, Google Play service and Google Play Store apps ... and then restart your device ... in order to get Play Protect certification.

Hello please how I can run this script in Linux?

kodopraha said:

Hello please how I can run this script in Linux?

Release latest · luk1337/ih8sn

Commits c5fb698: Override non-configurable properties on boot_completed_stage (Oto Šťáva) #20

github.com

Dashboard - LOS-Legacy®

Deine Android Community

forum.los-legacy.de

lineage-19.1-20220610-sing.spoofing-fajita.zip​

Master_TC said:

On step 3 i get the message, that the command "sh push.sh" is unknown.
Can you explain the steps to me in more detail?

---
Safetynet fix with ih8sn:

OK i have found a more detailed installation instruction for all with windows:
(https://github.com/luk1337/ih8sn/issues/9#issuecomment-1027987082)

* enable usb debugging and rooted debugging in the developer options
* reboot phone
* extract the ih8sn.zip and put the files in your adb folder
* execute the following commands in your adb folder:
adb wait-for-device root
adb wait-for-device remount
adb wait-for-device push 60-ih8sn.sh /system/addon.d/
adb wait-for-device push ih8sn /system/bin/
adb wait-for-device push ih8sn.rc /system/etc/init/
adb wait-for-device push ih8sn.conf /system/etc/
*reboot phone

Click to expand...

Completed the above and am now able to register cards on Google Pay and register phone with my company (intune) hurray!

But google pay indicates that the cards are not setup for NFC payements and in "contactless setup" it says the phone does not meet security requirements...

UPDATE: This started working when I checked the next day (I had rebooted several times, before posting the above).

EdwinMoq said:

It takes about 20 seconds for my fajita to boot, so you must have something that slows down boot on your phone.

I just installed again lineage, after setting up the system, without any app installed (only magisk app) it took about 45-50 seconds to enter the system...