[Galaxy A3, A5, A7, A8, A9 Original Android Develop] impasta:
A short review.

This really does work on SM-A710Y/DS, Awesome! No show stopping problems, here.

I've been using this for about half a month right now. I'd say, this is the best build I used ever since.

Everything from the cell radio, video playback at 720p 60fps, camera, to the sensors and such are working as expected.

But, I do have a couple of nitpicks:

Miracast doesn't work so no screen casting or WFD. Google seem to have removed the support in AOSP.

Volume steps is at 15 (I'd liked it better at 25 or 30)

If you ever change this, please also change the high volume warning too. They seem to be independent values.

When using unprovisioned/deactivated SIM card on SIM2 slot and a valid/provisioned sim on SIM1 slot,

The system will only see 1 SIM even though the SIM2 is recognized in the RIL level.

Cannot export contacts to SIM card.

MTP does not work with ADB.

WiFi MAC address randomization is missing :(

Reader's discretion is advised when reading the text below.

This were my short review gets a bit technical.

I'm sorry if the resulting tone becomes too overbearing. I'm not a developer/programmer anyways.

Also, I'm not trying to be arrogant in anyway but instead I'm thankful for the people who made this LOS build possible (and free).

With that out of the way, I have some minor problems:

Using Samsung's original charger causes the phone to heat up and the current can shoot more than 2 Amps.

This does not happen when NOT using a fast charging adapter or when the battery is above 70%.

However, this can be adjusted in two ways, both requiring to change the device-tree files

The charger limits the current automatically when the battery is about 41 degrees Celsius.

The current it limits to is in the device tree (under the swelling_high_temp_current value).

This is, IIRC, at 1.4 Amps

Although it is more risky, you could also change the current tables: fast_charging_current and input_current_limit

I didn't try this out since the last thing I want this Christmas is to have a broken battery.

Change when the charger limits the current(using the swelling_high_temp_block and swelling_high_temp_recov)

I used this approach along with (a).

I made it so to limit the current to 0.8 Amps upon reaching 38 C and restart fast charging when the battery cools down to 35 C.

When I was trying to charge the phone while it is off, I get this confusing battery animation.

As always, I cannot tell how much of the battery has charged or if it is fast charging or not.

I also find it difficult to reboot from this mode (or it's just the power button acting up.)

I miss the LPM binary from Samsung which I believe is not possible to include since its a proprietary blob.

But, if it's not the case then it is quite possible to include this to the Lineage OS 17.1 build. It needs:

Find a way to remove or to effectively disable the default 'charger' binary.

BOARD_CHARGER_NO_UI can disable the battery animation.

Create a init script to launch the lpm binary on charger mode

Import the lpm and its dependencies (libmaet.so and libsxqk_skia.so), and the *.spi file from /system/media.

Write the appropriate sepolicy for the lpm binary.

The sound is comparably softer than the stock rom.

This could be because Samsung uses their soundalive technology (or library) to do some dynamic loudness enhancement.

Okay, to a possible workaround without soundalive.

I haven't tried any of these since I usually use headset and I'm quite contented.

A pair of good headset will make a difference. Teehee :)

Use some audio mod (viper4android or something)

Play around with the amplifier library.

Find a way to tweak some parameter that you can see when you run 'tinymix' in the root shell.

Usually, the audio HAL sets these parameters automatically.

You could try to play with these parameters when playing some thing to see:

which parameters affect the perceived loudness

how much value you can change before the sound becomes distorted

Has anyone tested connecting through a WiFi 5 network (the one with 5GHz)?

This device supports this but the overlay files said that it does not.

config_wifi_dual_band_support is set to false.

I haven't tested this out yet, if setting this to either false or true makes a difference in supporting 5GHz.

The code seems to show that this flag is not being used at all.

For some reason, when the powersaving mode has been enabled and disabled, the maximum cpu clocks stays at 900MHz.

When switching to Power Save, /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq is set to 900Mhz

Then switching to Balanced, /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq is still at 900Mhz

Finally, when switching to Performance, /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq is now restored back to 1.6Ghz