[OFFICIAL] [NIGHTLIES] LineageOS 17.1

esjarc

Member
Apr 7, 2020
8
11
0
@jeferson1979 No, plugging the charger in does not help with booting, it still continues bootlooping.

I managed to get it booting once by connecting the charger, but I was unable to reproduce this behavior. The single successful boot with the charger may have actually been pure coincidence.

But I just noticed that there is a certain chance that it boots up fine the very first time after enabling Secure Startup. But all (?) subsequent reboots seem to result in a bootloop.


EDIT: After continued testing today, I could no longer verify the issue without Open GApps installed, so I guess this might be related somehow to Google apps? I've updated the bug report accordingly.
 
Last edited:
  • Like
Reactions: jeferson1979

ywlke

Member
Jul 24, 2013
5
0
0
I noticed the other day that the DTMF tones with preprogrammed numbers (i.e. saved in a contact with pauses) are way too long and not getting interpreted correctly by the other end. Googling around suggests there is a system setting dtmf_tone_type that can be changed (https://forum.xda-developers.com/galaxy-s3-att/decrease-length-touch-tone-dialer-t2810483) which is often exposed in the Dialer app (https://help.ting.com/hc/en-us/articles/115005081167-Changing-the-DTMF-Tone-of-your-Android-Device) but I can't find the setting, or how to change it on Android 10 which no longer uses a SQLite database for system settings storage. Any thoughts?
 

MauricioJorge

Member
May 11, 2019
9
0
0
You need to install app.debug.apk attached few posts later, then, allow additional setup
the system is working perfectly so far with no bug found, with the exception of the magisk that I couldn't make work
the 4g signal is perfect for the first time in years of testing with lineageOs
what should i do to solve the problem with magisk?
where do I find Patch boot.img?
 

ttocs99

Senior Member
Jan 26, 2011
1,911
290
113
middlesbrough
how do i do this? have any tutorial? where do i download?
If you have this ROM installed. Open the zip file and extract the boot.img and put it somewhere on your phone or as card. Install magisk manager and click install magisk, from the list click patch boot.img and let magisk do its work. Once completed pull the newly patched boot.img of device and flash it via fast boot as fastboot flash boot boot.img. reboot phone and check magisk manager and it should say that it is installed.
 
  • Like
Reactions: MauricioJorge

MauricioJorge

Member
May 11, 2019
9
0
0
If you have this ROM installed. Open the zip file and extract the boot.img and put it somewhere on your phone or as card. Install magisk manager and click install magisk, from the list click patch boot.img and let magisk do its work. Once completed pull the newly patched boot.img of device and flash it via fast boot as fastboot flash boot boot.img. reboot phone and check magisk manager and it should say that it is installed.
I will test thanks ?

---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------

tested it and it's working perfectly thanks ????
 

TomOehser

New member
Jan 12, 2018
4
1
0
Seems that "hey google" is still broken. It's a known bug, right?

In 16/pie, the "ok google" capability broke - I saw, I think, that it was a known issue and that there was disagreement (between lineage/magisk maybe?) about who was doing the "the wrong thing".

I'm disappointed to see this still broken? Is anyone else irked, are there any workarounds, is there any view-forwards to a resolution?

-Thanks....
 

jeferson1979

Recognized Developer
Jan 15, 2018
292
447
83
41
Taió
sourceforge.net
In 16/pie, the "ok google" capability broke - I saw, I think, that it was a known issue and that there was disagreement (between lineage/magisk maybe?) about who was doing the "the wrong thing".

I'm disappointed to see this still broken? Is anyone else irked, are there any workarounds, is there any view-forwards to a resolution?

-Thanks....
Workarounds are not the right way, you can help to fix providing log ;)