[OFFICIAL][a7xelte][SM-A710F]Lineage OS 17.1 for A7 2016

[White18]

Same question, will this work on A700FD or could you please port it?

 

[Floehelis]

Having display on/off issues with the latest update. In the previous one the screen was glitching when on idle or when connected to usb. On this one, the screen glitches when trying to turn the screen on. Also happens during calls when it triggers the proximity sensor. Pressing the power button multiple times does no effect but then on its own mind it decides to turn on, on a random press.

 

[Androbots]

Anyone tried this on A7 A700FD (2015)?
Do you suppose worth a shot to try?

Same question, will this work on A700FD or could you please port it?

I am pretty sure you can't just flash this on another device no matter how similar the devices are. We even have checks within the flashable script that will stop you from doing that. Why don't you two reference the device trees we have for a*xelte and figure something out?

Could anyone please help me with modem flashable tar files, am currently on A710FXXU2CRK1, need to upgrade coz my signal is weak since i flashed a custom ROM on it.
Thanks in advance

Check Samfw.com

Having display on/off issues with the latest update. In the previous one the screen was glitching when on idle or when connected to usb. On this one, the screen glitches when trying to turn the screen on. Also happens during calls when it triggers the proximity sensor. Pressing the power button multiple times does no effect but then on its own mind it decides to turn on, on a random press.

I think I have noticed this, but I am not sure what causes mostly because it happens next to never on my side.

 

[impasta]

Thanks for your great job experience is buttery smooth but I faced two problems
1-device charges much faster than the stock rom and that causes it to heat up (used accubattery to monitor charging speeds 800-1300 mAh on average in stock. And 2300 on average in LOS17.1) is there any way to make it a bit slower to preserve the battery from the heat?
2-sound volumes tend to be lower than the stock rom
If these 2 problems were solved, hands down it's the best rom ever

Hello,

For the charging problem (problem #1), you can try to disable fast charging. I read about this at some Gerrit review.


You could do this using adb in root mode (enable "Rooted debugging" in Developer options, first).
Start by running the line below then re-plug the phone charger. That's all.
This resets after a reboot.

echo 1 > /sys/class/sec/switch/afc_disable

I don't know what afc stands for (adaptive fast charging, I suppose?) but with this disabled, the maximum current it can draw is about 1.7 Amps (at least in A710Y/DS). On the other hand if enabled, I can observe the phone drawing 2.5 to 2.6 Amps max.

In my experience, this phone's fast charging (even the normal charging) is problematic. It causes the phone to heat up past 40 degrees centigrade and helps its battery to swell faster. I think I need a heatsink for this.

 

[Floehelis]

I've also noticed the flicker starts happening when bringing the brightness slider down to below 20%. I don't know if it's the A7 alone or if other phones also have this, at around 20% brightness the screen switches to a limited color range profile. Could it be this is causing a problem? But that said the flicker still happens when on full-range colours as well. In any case, when I first installed the rom in early december this issue wasn't there, it started happening around after the early january updates.

 

[Androbots]

I've also noticed the flicker starts happening when bringing the brightness slider down to below 20%. I don't know if it's the A7 alone or if other phones also have this, at around 20% brightness the screen switches to a limited color range profile. Could it be this is causing a problem? But that said the flicker still happens when on full-range colours as well. In any case, when I first installed the rom in early december this issue wasn't there, it started happening around after the early january updates.

Sounds really like a hardware problem cuz what you are describing is something I've had even on stock and Samsung Service Center suggested me to get my device's screen replaced for $150 which I obviously didn't xD

 

[greenberet33]

Why don't you two reference the device trees we have for a*xelte and figure something out?

Not sure how to start with this. Could you point me out to something?

 

[Androbots]

Not sure how to start with this. Could you point me out to something?

GitHub - LineageOS/android_device_samsung_a7xelte

Contribute to LineageOS/android_device_samsung_a7xelte development by creating an account on GitHub.

github.com

GitHub - LineageOS/android_device_samsung_a5xelte

Contribute to LineageOS/android_device_samsung_a5xelte development by creating an account on GitHub.

github.com

 

[Floehelis]

I reverted back to stock. The problem is still there. So, that essentially rules Lineage out of the question. But the problem is only there for very low brightness, and when trying to bring the phone out of sleep. While the phone is on and the brightness is sufficient, everything is working fine, both in Lineage, and Samsung's default OS.
But, since this is a circumstantial glitch, I'd like to believe it's a software error and not hardware. And it looks like the issue isn't the ROM itself since it persists on a clean samsung OS install.
I'm fairly new to this so I'll look around for what other data still persists. Maybe that'll provide some answers. Eventually.

 

[[email protected]]

I can flash LineageOS 17.1 for my phone variant A7108 exynos?

 

[Asutosh01]

Can you please make the screen turn off instantly whenever power button is pressed. Because a lot of Galaxy A7 2016 including mine comes with faulty amoled displays which flickers at low brightness. In this is version when the power button is pressed the screen gradually lowers its brightness before going in to sleep mode and the screen flickers for 2-3 seconds. When power button is pressed again to wake up the phone it flickers again sometimes wakes up after 4-5 attempts. Please make this is to wake up and sleep the phone whenever power button is pressed instantly without gradually lowering or increasing brightness

SOLVED: Screen flickering at low brightness - samsung galaxy a5 2016

The LCD screen flex cable is worn out and not well connected with the motherboard. This may cause by overheating, moisture or dropping damage. - samsung galaxy a5 2016

www.ifixit.com

 

[Asutosh01]

I reverted back to stock. The problem is still there. So, that essentially rules Lineage out of the question. But the problem is only there for very low brightness, and when trying to bring the phone out of sleep. While the phone is on and the brightness is sufficient, everything is working fine, both in Lineage, and Samsung's default OS.
But, since this is a circumstantial glitch, I'd like to believe it's a software error and not hardware. And it looks like the issue isn't the ROM itself since it persists on a clean samsung OS install.
I'm fairly new to this so I'll look around for what other data still persists. Maybe that'll provide some answers. Eventually.

Turn off transition animation scale window animation scale and duration scale . Then use pwm app. Thank me later

I reverted back to stock. The problem is still there. So, that essentially rules Lineage out of the question. But the problem is only there for very low brightness, and when trying to bring the phone out of sleep. While the phone is on and the brightness is sufficient, everything is working fine, both in Lineage, and Samsung's default OS.
But, since this is a circumstantial glitch, I'd like to believe it's a software error and not hardware. And it looks like the issue isn't the ROM itself since it persists on a clean samsung OS install.
I'm fairly new to this so I'll look around for what other data still persists. Maybe that'll provide some answers. Eventually.

 

[Asutosh01]

I reverted back to stock. The problem is still there. So, that essentially rules Lineage out of the question. But the problem is only there for very low brightness, and when trying to bring the phone out of sleep. While the phone is on and the brightness is sufficient, everything is working fine, both in Lineage, and Samsung's default OS.
But, since this is a circumstantial glitch, I'd like to believe it's a software error and not hardware. And it looks like the issue isn't the ROM itself since it persists on a clean samsung OS install.
I'm fairly new to this so I'll look around for what other data still persists. Maybe that'll provide some answers. Eventually.

Use pwm app

 

[impasta]

Hello. I'm curious about 2 things.
Will there be a LineageOS 18.* build for this device?

Has someone experienced random system crashes specially when the GPS is used (e.g. LiveDisplay is set to Automatic and location is on; Google tries to access your GPS even if location is off)?
I can provide a stack trace and a symbolized stack trace if that will help the developers.

 

[Androbots]

Hello. I'm curious about 2 things.
Will there be a LineageOS 18.* build for this device?

Has someone experienced random system crashes specially when the GPS is used (e.g. LiveDisplay is set to Automatic and location is on; Google tries to access your GPS even if location is off)?
I can provide a stack trace and a symbolized stack trace if that will help the developers.

Yep. We have already made a lot of progress over the months and things are pretty stable now. We plan on releasing after we level out some more inconsistencies. Here are some screenshots though to keep you chugging along

About GPS, I am blind without a logcat. Googling how to get a logcat should help you get one from your device.

 

[impasta]

Yep. We have already made a lot of progress over the months and things are pretty stable now. We plan on releasing after we level out some more inconsistencies. Here are some screenshots though to keep you chugging along

About GPS, I am blind without a logcat. Googling how to get a logcat should help you get one from your device.

Wow, nice! Thank you so much for all these efforts. Eagerly looking forward for that one.

Though about the vendor security patch level, isn't there a more recent Android 7.0 stock rom build from the end of 2020? Any thoughts of upgrading the vendor blobs from that build?

As for the GPS one, I'll try to get a proper logcat when that issue pops out again (since I ignored it for the last 2 months). I do not know yet what exactly triggers the issue or how to reproduce it, so it seems to pop out in random times. Additionally, the only logs I have saved is just this:

01-23 16:54:18.986  7247  7247 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-23 16:54:18.987  7247  7247 F DEBUG   : LineageOS Version: '17.1-20201217-UNOFFICIAL-a7xelte'
01-23 16:54:18.987  7247  7247 F DEBUG   : Build fingerprint: 'samsung/a7xeltedo/a7xelte:6.0.1/MMB29K/A710YZTU1BQK2:user/release-keys'
01-23 16:54:18.987  7247  7247 F DEBUG   : Revision: '0'
01-23 16:54:18.987  7247  7247 F DEBUG   : ABI: 'arm'
01-23 16:54:19.071  7247  7247 F DEBUG   : Timestamp: 2021-01-23 16:54:18+0800
01-23 16:54:19.072  7247  7247 F DEBUG   : pid: 2699, tid: 3083, name: Thread-5  >>> system_server <<<
01-23 16:54:19.072  7247  7247 F DEBUG   : uid: 1000
01-23 16:54:19.072  7247  7247 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x69007f
01-23 16:54:19.072  7247  7247 F DEBUG   :     r0  00000009  r1  00000011  r2  00430000  r3  f33ab084
01-23 16:54:19.072  7247  7247 F DEBUG   :     r4  c2800b64  r5  c0c81970  r6  0069006f  r7  f50fa260
01-23 16:54:19.072  7247  7247 F DEBUG   :     r8  c29bd44b  r9  c29bd216  r10 c2800af0  r11 c29c0010
01-23 16:54:19.072  7247  7247 F DEBUG   :     ip  00000000  sp  c2800ac8  lr  ce65c4cf  pc  c29d6baa
01-23 16:54:19.249  7247  7247 F DEBUG   :
01-23 16:54:19.249  7247  7247 F DEBUG   : backtrace:
01-23 16:54:19.249  7247  7247 F DEBUG   :       #00 pc 00056baa  /system/lib/[email protected] (android::hardware::gnss::V1_0::BsAGnssRilCallback::requestSetIdCb(unsigned int)+450) (BuildId: 30ee8b14270ae2b3ae675a7f9b4de136)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #01 pc 0000d8dd  /system/vendor/lib/hw/[email protected] (android::hardware::gnss::V1_0::implementation::AGnssRil::requestSetId(unsigned int)+32) (BuildId: aaeb0bd94f81a67e9a33098d9df7a9ab)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #02 pc 0001817d  /system/lib/hw/gps.universal7580.so (broadcom::GpsiClient::marshal_agps_ril_request_setid(broadcom::IpcIncomingMessage&)+160) (BuildId: c154e477d5e0986066dee33ae6b1f776)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #03 pc 0001f6f5  /system/lib/hw/gps.universal7580.so (broadcom::IpcPipeTransportBase::OnSelect(int, bool, bool, bool, void*)+280) (BuildId: c154e477d5e0986066dee33ae6b1f776)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #04 pc 0001f7ad  /system/lib/hw/gps.universal7580.so (non-virtual thunk to broadcom::IpcPipeTransportBase::OnSelect(int, bool, bool, bool, void*)+12) (BuildId: c154e477d5e0986066dee33ae6b1f776)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #05 pc 0001fd33  /system/lib/hw/gps.universal7580.so (broadcom::SelectManager::ProcessEvent(broadcom::ISelectHandler&, int, bool, bool, bool, void*)+26) (BuildId: c154e477d5e0986066dee33ae6b1f776)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #06 pc 0001fc91  /system/lib/hw/gps.universal7580.so (broadcom::SelectManager::PerformOneWaitAndProcess()+424) (BuildId: c154e477d5e0986066dee33ae6b1f776)
01-23 16:54:19.250  7247  7247 F DEBUG   :       #07 pc 0001653b  /system/lib/hw/gps.universal7580.so (broadcom::ipc_thread_proc(void*)+30) (BuildId: c154e477d5e0986066dee33ae6b1f776)
01-23 16:54:19.251  7247  7247 F DEBUG   :       #08 pc 0000d019  /system/vendor/lib/hw/[email protected] (threadFunc(void*)+6) (BuildId: aaeb0bd94f81a67e9a33098d9df7a9ab)
01-23 16:54:19.251  7247  7247 F DEBUG   :       #09 pc 000a6b83  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+20) (BuildId: be2954ec495707bc280c21e0cf2919f2)
01-23 16:54:19.251  7247  7247 F DEBUG   :       #10 pc 00060723  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: be2954ec495707bc280c21e0cf2919f2)

 

[wektorizm7]

Introduction

LineageOS 17.1 is a free, community built, aftermarket firmware distribution of Android 10.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.

What works

Calls, SMS, Mobile Data​

Camera​

NFC​

WiFi​

Bluetooth​

Torch​

Sensors​

GPS​

HWC​

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.​

You tell me!​

​

Known Issues

If you are running the latest update and are not able to enroll a fingerprint you may need to clear the fingerprint data using this zip (flashable in TWRP): https://mega.nz/#!6YZV2QTY!hOYYwrbkTPfThUIJUffOEQWMosdCxeqy_7JdGpYp3AA​

​

There are still quite a few features that are not yet completed for LineageOS 17.1, these are not bugs this is a beta release.
Any hardware related issues will be ignored if you do not provide:
a) Logcat
b) proc/last_kmsg
c) data/tombstones
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 (Available Here)​

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​

Download the latest LOS build and transfer it to your phone​

Install LOS​

If you are installing GApps do it at the same time (preferably in the same install queue)​

And finally boot, the first boot can take several minutes as it optimizes all the apps​

Do NOT install the TWRP app when prompted, this will cause a bootloop​

​

Downloads

Latest Official releases HERE​

OpenGapps HERE(ARM, 10, nano)​

TWRP is available​

Magisk is available​

​

Thanks

@Stricted​

@l-0-w​

@danwood76​

@sekil​

@alexax66​

@macs18max (BT call audio fix)​

@Borduni​

All the testers on the Discord group (https://discord.gg/8fp9cr7)​

And all others who have contributed to the Exynos projects past and present.​

​

XDA:DevDB Information
Lineage OS 17.1 for A7 2016, ROM for the Samsung Galaxy A Series

Contributors
Androbots, danwood76, Stricted
Source Code: https://github.com/LineageOS

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

ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Stock.
Based On: AOSP

Version Information
Status: Stable
Update frequency: Every week (Nightlies)
Current Stable Version: 17.1
Current Beta Version: 18.0

2020-04-24

Hi, first of all thank you for your super work but after throwing the rom I can no longer call anyone, IMEI problem I guess what can I do?

 

[Ariskwn]

Hi, kudos to the Dev for the ROM. Working nice and smooth. Anyhow does anyone having issues with formatting the SD card as internal storage? In my case, it failed during formatting (stuck at 40 percent and then it force close), is it a bug on this release? Thanks

 

[retiredtab]

F DEBUG : #00 pc 00056baa  /system/lib/[email protected] (android::hardware::gnss::V1_0::BsAGnssRilCallback::requestSetIdCb(unsigned int)+450) (BuildId: 30ee8b14270ae2b3ae675a7f9b4de136)
F DEBUG : #01 pc 0000d8dd  /system/vendor/lib/hw/[email protected] (android::hardware::gnss::V1_0::implementation::AGnssRil::requestSetId(unsigned int)+32) (BuildId: aaeb0bd94f81a67e9a33098d9df7a9ab)
F DEBUG : #02 pc 0001817d  /system/lib/hw/gps.universal7580.so (broadcom::GpsiClient::marshal_agps_ril_request_setid(broadcom::IpcIncomingMessage&)+160) (BuildId: c154e477d5e0986066dee33ae6b1f776)

@Androbots and @impasta

Was the above ever solved? We are running into the exact same error messages when gnss crashes on the exynos5433 platforum (Samsung Tab S2 and Galaxy Note 4). We get the same marshal_agps_ril_request_setid and AGnssRil::requestSetId and AGnssRilCallback::requestSetIdCb.

Both exynos7580 and exynos5433 use the same BCM4752 gps chipset.

We have tried lots of things to fix it over the last week and now trying to switch manifest.xml from gnss passthrough to hwbinder. I cannot recreate the gnss crash at all and it seems random when it crashes so I have to wait for my testers to report it, but usually it crashes with 24 hours.

 

[retiredtab]

We have tried lots of things to fix it over the last week and now trying to switch manifest.xml from gnss passthrough to hwbinder. I cannot recreate the gnss crash at all and it seems random when it crashes so I have to wait for my testers to report it, but usually it crashes with 24 hours.

Just to update. Switching to hwbinder let's my 3 testers have > 100+ hours uptime now. Details at

https://github.com/universal5433/android_device_samsung_gts2-common/pull/4

It may help you guys out?