[UNOFFICIAL] LineageOS 18.1 For A310, A510, and A710

[TheRain12]

or i gave up danny, i'm a youtuber and when i shoot videos on roblox, the phone gets hot and the game shuts down (10 minutes after starting the game) so i will switch to Alpha Centauri V3.0 (with a pixel interface) it won't have any heatsink because alpha centauri base is samsung stock romu. Even though it warmed up for about 15 minutes while in stock rom, the games wouldn't close. Even in Oreo LineageOS 15.1 rom, it wouldn't close immediately (your rom)

 

[sbocconi]

Hello,

I have an A510F with LineageOS 17.1, it works fine but the microphone quality became worse with respect to the stock ROM.

I have 2 simple questions:

1) Is this problem common with A510F and LOS 17.1?
2) Is LOS 18.1 going to improve the situation?

Many thanks!

 

[kurtn]

@danwood76 will there be updates for 17.1 or 18.1 ? I have to decide about fixing my broken a3 2016

... And maybe some idea what's stopping auto-focus.

 

[danwood76]

Changes 19-08-2022:

• Synced to latest LineageOS source (including August security patch)

Kind regards,
Danny

 

[danwood76]

@danwood76 will there be updates for 17.1 or 18.1 ? I have to decide about fixing my broken a3 2016

... And maybe some idea what's stopping auto-focus.

I am still updating 18.1 when I get time.

With regards to the af issue. Which camera app are you using?

Kind regards,
Danny

 

[kurtn]

I am still updating 18.1 when I get time.

With regards to the af issue. Which camera app are you using?

Kind regards,
Danny

Thanks. I'm using the camera shipped with your build. Usually rebooting fixed the issue for a few weeks. But now 17.1 microG fork started working after a week lying around powered off.

 

[mrhamed]

Does it possible to release microG build please?

 

[poow]

Is it intended behaviour if I get a Trust notification saying that this build was signed by public keys? (I followed the upgrade steps from official 17.1, but without any Gapps.)

 

[Beta123MAX]

Is it intended behaviour if I get a Trust notification saying that this build was signed by public keys? (I followed the upgrade steps from official 17.1, but without any Gapps.)

Build are signed with public keys.
Don't know what you mean by "intended". But it's, generally spoken, a relevant info and it's right. The signing key warning can be disabled. This is what I did, as I didn't feel the need to get the same info again and again.

 

[mrhamed]

@danwood76
I have a serious issue with this rom: I can't hide magisk from apps (specially my banking app).
It seems the rom has already 'su' (or any kind of) binary and it is impossible to hide with 'magisk hide'.
Does it possible to release not-rooted version?
Does it possible to provide a falshable.zip file to remove stock 'su' (or any kind of) binary?
Could you please help me to find a solution to hide root? (I tested Magisk + LSposed + ApplistHide)

Thank you!

 

[danwood76]

@danwood76
I have a serious issue with this rom: I can't hide magisk from apps (specially my banking app).
It seems the rom has already 'su' (or any kind of) binary and it is impossible to hide with 'magisk hide'.
Does it possible to release not-rooted version?
Does it possible to provide a falshable.zip file to remove stock 'su' (or any kind of) binary?
Could you please help me to find a solution to hide root? (I tested Magisk + LSposed + ApplistHide)

Thank you!

Banking apps use lots of different ways to decide you are "rooted". Unfortunately most simply detect a custom ROM as rooted.

Check the advanced hide options for your banking app and make sure everything option is ticked.

Also reset the app data after hiding everything. You also need to use an old version of magisk before hide was removed.

Good luck.

Kind regards,
Danny

 

[Joanga]

Hi Danny,

The first thing I want to do is to thank you and your team for your efforts in keeping our old mobile phones working.

On the other hand, I tried to install lineage-18.1-20220819-UNOFFICIAL-a7xelte.zip today, developed by you on my Samsung Galaxy A7(2016) SM-A7100 with Snapdragon, and it gave me the error you can see in the attached picture.

I would like to add that I bought this phone from Amazon and I think it comes from Hong Kong.

What could I have done wrong in the installation?

Thank you very much for your answer.

 

[Beta123MAX]

On the other hand, I tried to install lineage-18.1-20220819-UNOFFICIAL-a7xelte.zip today, developed by you on my Samsung Galaxy A7(2016) SM-A7100 with Snapdragon, and it gave me the error you can see in the attached picture.

Only Exynos 7580 based devices are supported.

 

[Joanga]

Hi Betta123,
Thank you for your answer.
Because you are in the world of custom Roms,
Do you know if anyone has developed a custom Rom for my phone?
Thank you very much

 

[Beta123MAX]

Do you know if anyone has developed a custom Rom for my phone?

No SM-A7100 custom Rom thread on xda, sadly.

 

[rik70]

Hello,
many thanks for your great job.

Does it possible to release a 'dev-keys' build?

I'm on a SM-A510F, but a lot of apps does not work with a 'test-keys' signed rom.

 

[kurtn]

Hello,
many thanks for your great job.

Does it possible to release a 'dev-keys' build?

I'm on a SM-A510F, but a lot of apps does not work with a 'test-keys' signed rom.

There is more about it than test keys. There are many device integrity checks out there. But most depend on Google safetynet attestation. Learn how to fake that with magisk.

 

[rik70]

There is more about it than test keys. There are many device integrity checks out there. But most depend on Google safetynet attestation. Learn how to fake that with magisk.

In my country, the first check is "rom signed with public keys".
Can magisk hide that?

I'm using my LOS 17.1 personal build signed with my private keys, and got no warning about security issue while using gov's apps.

ro.system.build.fingerprint=samsung/lineage_a5xelte/a5xelte:10/QQ3A.200805.001/rik09110937:userdebug/dev-keys
ro.system.build.tags=dev-keys
ro.build.display.id=lineage_a5xelte-userdebug 10 QQ3A.200805.001 eng.rik.20220911.094053 dev-keys
ro.build.tags=dev-keys
ro.build.description=lineage_a5xelte-userdebug 10 QQ3A.200805.001 eng.rik.20220911.094053 dev-keys

ro.system.build.tags=dev-keys
ro.build.version.release=10
ro.build.version.security_patch=2022-09-05

The only changes are in '/defaults.prop':
'ro.debuggable=1' to 'ro.debuggable=0'

 

[danwood76]

In my country, the first check is "rom signed with public keys".
Can magisk hide that?

I'm using my LOS 17.1 personal build signed with my private keys, and got no warning about security issue while using gov's apps.

ro.system.build.fingerprint=samsung/lineage_a5xelte/a5xelte:10/QQ3A.200805.001/rik09110937:userdebug/dev-keys
ro.system.build.tags=dev-keys
ro.build.display.id=lineage_a5xelte-userdebug 10 QQ3A.200805.001 eng.rik.20220911.094053 dev-keys
ro.build.tags=dev-keys
ro.build.description=lineage_a5xelte-userdebug 10 QQ3A.200805.001 eng.rik.20220911.094053 dev-keys

ro.system.build.tags=dev-keys
ro.build.version.release=10
ro.build.version.security_patch=2022-09-05

The only changes are in '/defaults.prop':
'ro.debuggable=1' to 'ro.debuggable=0'

Test keys are not inherently insecure, does it actually block you using the apps? I used to do privately signed builds but I didn't in the 18.1 releases.

Old versions of magisk can hide it.

Kind regards,
Danny

 

[rik70]

Test keys are not inherently insecure, does it actually block you using the apps?

Yes, it does.

Phone is marked "insecure" when apps do a check like this:

# ./rootbeerlib/src/main/java/com/scottyab/rootbeer/RootBeer.java,  at line ~74:

    /**
     * Release-Keys and Test-Keys has to do with how the kernel is signed when it is compiled.
     * Test-Keys means it was signed with a custom key generated by a third-party developer.
     * @return true if signed with Test-keys
     */
    public boolean detectTestKeys() {
        String buildTags = android.os.Build.TAGS;

        return buildTags != null && buildTags.contains("test-keys");
    }


#

Source: https://github.com/scottyab/rootbeer