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

Search This thread

danwood76

Recognized Developer
May 23, 2015
1,400
2,289
Yes, it does.

Phone is marked "insecure" when apps do a check like this:
Code:
# ./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
That is a false positive. I would suggest you install an old version of magisk, I used to have to root my phone to stop my mobile banking from detecting root. 😂

I am not going to start signing builds at this late stage.

Kind regards,
Danny
 

rik70

Member
Nov 20, 2016
7
6
@danwood76

OK, "fake security check" bypassed editing '/default.prop' and '/system/build.prop' via ADB root.

No Magisk needed.

Now I'm able to use/test your rom and report back.

Many thanks to you, other developers and users.

Have a nice day.
 
  • Like
Reactions: maanteel

Beta123MAX

Senior Member
Apr 30, 2018
98
45
That is a false positive. I would suggest you install an old version of magisk, I used to have to root my phone to stop my mobile banking from detecting root. 😂
You said it.
I am not going to start signing builds at this late stage.
Agree, keeping things simple for security updates is the way to go.
Not to mention that most banking and other "security" focused apps are a wonky mess. They're often build against frameworks without caring about compatibly and can break using LOS with every single update. I think, fighting against it on rom side won't actually work.
 
  • Like
Reactions: danwood76

Pierre49976

Member
Jun 20, 2019
31
6
I'm running this ROM on my A3 and it's getting slower and slower. Sometimes it becomes unusable.
What can I do to regain initial speed?
 

funkoot

Member
Nov 6, 2012
49
27
Hi there and thanks for a great rom. I was just wondering of there is a version with Microg already installed?
Cheers,
Dave
 

Benjamin1989

Member
Oct 20, 2020
16
0
Hey Guys I have this ROM on my Galaxy S5 neo.
Everything is working fine except WLAN connection is lost when it's sleeping for some time.
Only restarting the device fixes that issue.
If you use it actively this never occurs.
Is there a solution for this problem?
Edit: I included a log file

Thx for helping me
 

Attachments

  • logs-2022-10-31-07-35-02.zip
    176.8 KB · Views: 4
Last edited:

blumentopf75

Member
Apr 28, 2010
42
15
Lockscreen loop.
I have a a5xelte with this fantastic lineage 18 (RQ3A.211001.001).
Everything worked, until yesterday, when I dropped the phone into water for only a second (applause please).
All thing are still working except of the lockscreen:
When the phone is locked and ich switch it on, it take a little while after the touchkeys are on, the the lockscreen apears for 1/2 sec. then the screen goes to black again. After anothe 1/2 sec the lockscreen apears for 1/2 sec and so on. About 20 or 30 times.
Then the phone reboots to recovery (TRWP). I reboot to system and can unlock sim and phone.
When the phne now locks itself, I have the same lockscreen loop.

It doesnt matter, what kind of lock I use (PIN, wipe, wipe pattern)

When I switch off any locking of the phone (happily I can log in one time after reboot), I can use the phone without any issue.

Could this really be a problem from the water-drop?
It feels a bit, as the lockscreen would chrash and the phone tries to restart it again and again.

Or is there a way to change to anothe lockscreen-app, to find out if the original from lineage chrashes?
And waht is the name of the lockscreen-app. Maybe i should stop and reset it in the settings of the phone.

Thank you.
 
Last edited:

blumentopf75

Member
Apr 28, 2010
42
15
Another idea is, that the fingerprint sensor is damaged because of the water.
I have four fingerprints configured, so maybe the lockscreen asks for the sensor and chrashes because of the damage.
This would eventually declare, why I can unlock on boot, because fingerprint-authentication is nor allowed at this point. So maybe the sensor is not activated on after-boot-login.
I also tried to delete the fingerprints, but this was not possible: when i tap on the bin the listentry becomes gray, but does not disappear. When I reenter the fingerprint-settings all four fingerprints are still in the list.
I also cant record a new fingerprint, because there are only four fingerprints allowed.
Is it possible that the sensor stores the fingerprints in itself, and so deleting from a damaged sensor ist not possible too?
 

tomen94

Senior Member
Oct 31, 2011
57
12
@danwood76

OK, "fake security check" bypassed editing '/default.prop' and '/system/build.prop' via ADB root.

No Magisk needed.

Now I'm able to use/test your rom and report back.

Many thanks to you, other developers and users.

Have a nice day.
Hello,
do you mind sharing us how and what excatly you edited in these files?

thanks!
 

rik70

Member
Nov 20, 2016
7
6
Hello,
do you mind sharing us how and what excatly you edited in these files?

thanks!
Edited parts attached below in `diff` format.

How to:

- in developer options, enable 'USB Debugging' and 'Rooted Debugging', then plug your phone in a pc usb port;
- in a terminal emulator, run 'adb root' and remount the filesystem in read-write mode:
Bash:
adb root
adb shell mount -orw,remount /
- then do:
Bash:
adb pull /default.prop
adb pull /system/build.prop
- in your hard disk you'll see two files: 'default.prop' and 'build.prop'.
Edit them and put back in your rom with:
Bash:
adb push default.prop /
adb push build.prop /system/
- remount the filesystem in read-only mode and reboot your phone:
Bash:
adb shell mount -oro,remount /
adb reboot
 

Attachments

  • rom.diff
    708 bytes · Views: 17
Last edited:
  • Like
Reactions: tomen94

tomen94

Senior Member
Oct 31, 2011
57
12
Edited parts attached below in `diff` format.

How to:

- in developer options, enable 'USB Debugging' and 'Rooted Debugging', then plug your phone in a pc usb port;
- in a terminal emulator, run 'adb root' and remount the filesystem in read-write mode:
Bash:
adb root
adb shell mount -orw,remount /
- then do:
Bash:
adb pull /default.prop
adb pull /system/build.prop
- in your hard disk you'll see two files: 'default.prop' and 'build.prop'.
Edit them and put back in your rom with:
Bash:
adb push default.prop /
adb push build.prop /system/
- remount the filesystem in read-only mode and reboot your phone:
Bash:
adb shell mount -oro,remount /
adb reboot
exemplary! Thank you @rik70
 

mrhamed

Senior Member
Apr 19, 2014
455
43
I have A310 device and install this ROM, thank you!
But on calling, the other people can hear our call because of the loudspeaker.
@danwood76
As I know I have to edit mixer_paths_0.xml, could help me find related values to DECREASE calling speaker?

Also, can I INCREASE music sound?

1668167651729.png
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    2okPze5.png


    Introduction

    LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    This is a combined thread for the A series Exynos7580 based devices.

    What works
    Everything
    What doesn't work
    IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.

    Any issues will be ignored if you do not provide:
    a) Logcat
    b) /proc/last_kmsg
    c) LineageOS bug report
    d) dmesg

    Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications

    Installation

    • Install the latest TWRP for your device
    • Make a full backup (just in case something goes wrong)
    • Do a full wipe (Cache, Data, System)
    • If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
    • Flash the latest LineageOS 18.1
    • Opengapps
    • (Magisk if required)
    • Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
    Upgrade from official 17.1
    • Make a full backup
    • Flash in this order:
    • LineageOS-18.1
    • OpenGapps 11
    • (Magisk if required)
    • And then this migration zip available HERE
    Downloads
    Latest unofficial releases HERE
    OpenGapps HERE
    TWRP is available HERE
    Magisk is available HERE

    Thanks
    @Stricted
    @dariotr
    @Androbots
    The LineageOS team
    All the testers on the Discord group (https://discord.gg/8fp9cr7)
    And all others who have contributed to the Exynos projects past and present

    If you like my work consider buying me a coffee:


    Source Code: https://github.com/LineageOS

    Device trees:
    https://github.com/LineageOS/android_device_samsung_a3xelte
    https://github.com/LineageOS/android_device_samsung_a5xelte
    https://github.com/LineageOS/android_device_samsung_a7xelte
    https://github.com/LineageOS/android_device_samsung_universal7580-common

    Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580

    ROM OS Version: Android 11
    Based On: LineageOS

    Version Information
    Status:
    Stable

    Created 2020-08-20
    Last Updated 2022-06-15
    12
    Hi,

    Update time!

    Changes 20-01-2022 (all devices):
    • Synced to latest source (incl January security patch)
    • Enable WiFi display
    • Switch to GNSS HIDL service (improves GPS stability, thanks @retiredtab @impasta)
    • Fixed power profile switching (restores correct CPU speed when going back to balanced mode)
    Changes 20-01-2022 (A510F/A710F):
    • Enable fastcharge hal (allows disabling fastcharge)
    Kind regards,
    Danny
    10
    Hi,

    New update uploaded.

    Changes 15-03-2022:
    • Synced to latest LineageOS source (including march security patch)
    Kind regards,
    Danny
    9
    Changelog:

    Changes 18-01-2023:
    • Synced to latest LineageOS source (including January security patch)
    • Included patches missed in last build
    Changes 19-08-2022:
    • Synced to latest LineageOS source (including August security patch)
    Changes 15-06-2022:
    • Synced to latest LineageOS source (including June security patch)
    • ZRAM now mounted with discard option (thanks @JPCastillo2000 for the link)
    Changes 26-04-2022:
    • Synced to latest LineageOS source (including April security patch)

    Changes 15-03-2022:
    • Synced to latest LineageOS source (including march security patch)
    Changes 20-01-2022 (all devices):
    • Synced to latest source (January security patch)
    • Enable WiFi display
    • Switch to GNSS HIDL service (improves GPS stability, thanks @retiredtab @impasta)
    • Fixed power profile switching (restores correct CPU speed when going back to balanced mode)
    Changes 20-01-2022 (A510F/A710F):
    • Enable fastcharge hal (allows disabling fastcharge)
    Changes 19-10-2021:
    • Synced to latest Lineageos (October security patch)
    Changes 25-09-2021:
    • Fixed SDFat bug that caused reboots when accessing sd card (thanks to Ícaro Albuquerque for testing)
    Changes 21-09-2021:
    • Resysnced source (includes updated webview)
    • Fixed Wi-Fi hotspot (broken in last build)
    • Added slow/fast charging detection (indicates on lock screen)
    Changes 16-09-2021:
    • Synced LineageOS sources (includes September security patch and AOSP WFD)
    • Fixed WiFi direct
    • Added further ZRAM improvements (thanks @alexax66)
    Changes 28-08-2021:
    • Updated ZRAM implementation from Linux 4.1.52
    • Switched to LZ4 ZRAM compression (should be faster and better)

    Changes 24-08-2021:
    • Synced latest LineageOS sources (includes new lineageos charger animation)
    • Cleaned up device overlays
    • Fixed tethering overlays
    • Disabled BPF offload for tethering (as we dont support it)
    • Added a7xelte to thread
    9
    Just uploaded a new update.

    Main changes 21-09-2021:
    • Resysnced source (includes updated webview)
    • Fixed Wi-Fi hotspot (broken in last build)
    • Added slow/fast charging detection (indicates on lock screen)
    Kind regards,
    Danny