yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
There is no lineageOS recovery in official downloads site. Enabling update recovery in developer options upgraded from twrp to LineageOS recovery.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] HasankaSanjana98:
Thanx

Works fine on A310F:o:laugh:​
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
They are built but there is a bug in the website that isn't displaying the links.

If you swap full for recovery in the files path name you get the recovery.

For example todays build is https://mirrorbits.lineageos.org/fu...eage-17.1-20200601-nightly-a3xelte-signed.zip if you go to https://mirrorbits.lineageos.org/recovery/a3xelte/20200601/ you see the recovery image.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
Call forwarding doesn't works

Good morning, with lineage-17.1-2020xxxx-nightly-a3xelte-signed.zip (a310f) call forwarding does not work and blocks the connection with the mobile network and the mobile phone must be restarted. Thank you all for the excellent work, great team!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Wiltoncandido:
Good morning first of all congratulations DANY for your wonderful work, a doubt, screen transmission does not work? I mean screen mirroring, I have a Samsung TV and the phone cannot find the TV. Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Thanks for the official 17.1! Works great!

A small bug (persisting since I used this device with LOS 16) is, that the LiveDisplay settings dont survice reboots. "Dynamic" is just an awful color explosion which has to be switched to standard to look acceptable :D I have to switch this setting to standard again and agin after every reboot as it doesnt get saved and defaults to "Dynamic".

Here the log when setting "Standard":

06-05 20:25:12.272 2380 2996 E BufferQueueProducer: [org.lineageos.lineageparts/org.lineageos.lineageparts.livedisplay.LiveDisplaySettings#1] disconnect: not connected (req=1)
06-05 20:25:12.272 6369 7886 W libEGL : EGLNativeWindowType 0xca29f908 disconnect failed
06-05 20:25:12.272 6369 7886 D OpenGLRenderer: endAllActiveAnimators on 0xc8e6d100 (AlertController$RecycleListView) with handle 0xcbc28840
06-05 20:25:12.276 3464 4663 E InputDispatcher: Window handle Window{83088d5 u0 org.lineageos.lineageparts/org.lineageos.lineageparts.livedisplay.LiveDisplaySettings} has no registered input channel
06-05 20:25:12.280 6369 6369 I LiveDisplay: Setting mode: 1
06-05 20:25:12.294 3464 5064 E InputDispatcher: Window handle Window{83088d5 u0 org.lineageos.lineageparts/org.lineageos.lineageparts.livedisplay.LiveDisplaySettings} has no registered input channel
06-05 20:25:12.450 2380 2380 E display : [PrimaryDisplay] window of layer 2 was not assigned (window_index: -1)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
LiveDisplay is reset on boot by a line in the ramdisk.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] charlander:
Do I need to flash this every after official update or just the official update using lineage recovery without wiping anything? Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Once on official 17.1 you have only thre taps to update:

Download

Install

Ok
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] foxger:
endless Lineageos Bootanimation

Hi,

i have a A3 (2016) with an Exynos7580, TWRP install works fine. But every LineageOS 17.1 or 16.1 (without gapps) ends in a bootloop (endless Lineage Bootanimation). I didnt install TWRP system app, WIPE everything. How can i offer boot debug infos ? adb logcat -d only shows "waiting for device".

I installed a test image from the e foundation (https://images.ecloud.global/dev/a3xeltexx/). an this boots ups...

Perhaps somebody has the same problem? I would like to help with logs, but i only can offer the TWRP Kernel Logs

Attachments:

dmesg.log recovery of TWRP

/proc/last_kmsg
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

You have a failure of your touchkeys (either side of your home button) which is causing the issue (from your last_kmsg)

<3>[ 1.839901] [1: swapper/0: 1] abov-touchkey-ft1804 5-0020: abov_flash_fw checksum fail.(0x0,0x0),(0x74,0x5a) retry:0
<3>[ 1.839920] [1: swapper/0: 1] abov-touchkey-ft1804 5-0020: failed to abov_flash_fw (-1)
<3>[ 1.839940] [1: swapper/0: 1] abov-touchkey-ft1804 5-0020: failed to firmware check (-1)
<6>[ 1.840388] [0: swapper/0: 1] abov-touchkey-ft1804 5-0020: abov_power off
<3>[ 1.894081] [0: swapper/0: 1] abov-touchkey-ft1804 5-0020: abov_tk_probe fail
<4>[ 1.894128] [0: swapper/0: 1] abov-touchkey-ft1804: probe of 5-0020 failed with error -1

Do your touchkeys work in stock?

You should be able to work around the issue by removing the following from the device manifest (it gets stuck waiting for that service which will not run if there is no touchkeys present):

<interface>
<name>IKeyDisabler</name>
<instance>default</instance>
</interface>

With the new hidl interface we use in LineageOS 17 I should be able to remove that section all together from the device manifest. I may try that today.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
This is now fixed upstream (This Commit) and will be in the next build.

Thanks [MENTION=7377908]dariotr[/MENTION] for pointing me towards the issue!

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ginodman:
I can on/off WiFi, Mobile Data, Location, Airplane mode with pull down tiles even when screen is locked and without unlocking it. I think it's not OK from security point.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Some people already reported this. If I remember right, dotOS had a feature like that to prevent users from changing the QS when the device is locked. I don't really get the sense of it. Just take care of your device. Even a recovery like TWRP can be used to bypass the entire lock screen if you know how.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ginodman:
I hope you can't disable lock screen from lineage recovery, because of limited functions and no file browser (but thief can flash TWRP ;) you may say). So only device encryption can help.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Funnily enough LineageOS still requires you to unlock when tapping on the location or adb over network tile, though not when toggling wifi or mobile data (thats kinda half-implemented, maybe its just got forgotten about?)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] foxger:
Hi,

you are great!!!

Thank you very much, pointing out the issue so quick ;)

I will test the new build.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ginodman:
Hi,

Will OTA automatic updates work if I enable device encryption? Does Lineage Recovery support encryption?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
OTA updates work fine, encrypted or not.

Lineage recovery doesn't support device decryption, but it doesn't need to in order to update.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] LoboLeVrai:
SM-310F is a 64 bits device with a 32 bits android installed by Samsung.

Is LineageOS for SM-310F is a 64 bits OS and may run 64 bits app ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
https://wiki.lineageos.org/devices/a3xelte/install#installing-lineageos-from-recovery

Arm. Not arm64
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] chertVdetali:
Hm, not sure what you mean. There is no such folder at https://eu.dl.twrp.me/a3xelte/ and the latest version 3.3.0 is from 2019. I found that I had 3.2.2 installed which might be the reason of my backup/restore problems recently. But still, no update for over a year makes me suspicious.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
That blind?

https://mega.nz/folder/OEIknYIR#AIY-GQ4zeFcG9aUKk2rwrg
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There have been no TWRP releases for a while.

I created my own unofficial builds which fix the issue with backup/restore on LineageOS 17.1, check my first post.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi!! Do you know if the official built fixes the issue with the Android auto crash??

Thanks a lot!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Unfortunately Android Auto is flakey on a lot of LineageOS phones. There were some fixes recently but they didn't seem to change the state of play on the A3/A5.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] charlander:
My mobile bank wont open it says my phone is rooted even if its not. Any help?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Seaarch for safetynet. There are workarounds but real solution is to stay with stock ROM. Preferably iPhone
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
With my banking apps I have to use Magisk hide.

But it is important that from a clean install of the ROM/gapps/Magisk that you install the banking app but don't run it, open Magisk and flag the banking app in Magisk hide and then open the banking app for the first time. Some apps fingerprint your install and then black flag it if they detect root.

Some banking apps also work just with Magisk hide and don't do the blacklisting.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] exzemat:
Sorry,

someone can explain me where I can enable aod like with this rom ? for SMS/watsapp notification.

http://pix.toile-libre.org/?img=1592426893.jpg
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
This phone doesn't have AOD
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] exzemat:
:( sad....

ok, but just for notification ? with LOS 16, background was black and just text in color.

now, with "transparent background" enable, background is black but text is in white popup...

any way to have just text (no white popup) ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] walkercz:
google assistant ambient mode

Hello,

is it possible to run google assistant ambient mode on lineage-17.1-20200516-UNOFFICIAL-signed-a3xelte ??? I cannot see the option to turn on ambient mode :(

https://www.theandroidsoul.com/how-to-enable-google-assistant-ambient-mode/

I want to use the phone as night stand google assistant with photo gallery on locked screen with ambient mode. (I achieve this with z3 compact and lineage OS 17.1 already)

Thank you for help!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Um, about one hour ago I've downloaded and applied an update via system settings' updater, and since then my phones stuck in recovery at 'installing system update', and it's also quite hot even up until now (its been one hour now!).

It's updating from the June 7th (clean install) to the June 21st build.

Updates:

- Upon trying `adb logcat` or `adb shell` I get no output (the device is seen as in adb recovery mode)

- I've now rebooted both into recovery and normally, and the phone boots back to recovery and returns to the same state of 'installing'

- I guess I'll now install (through Odin) TWRP, wipe cache and try booting to system

- did install official TWRP 3.3.0-0, and upon booting it picked up what lineageos' recovery was doing and it went through finishing the update gracefully (as shown in 2 last attached photos).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Sad you instaled magisk. That's a no-go for an official bug report. Do you remember what date of lineageOS recovery you installed? Do you have developer option "update recovery" enabled?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
It was a June 7th build of the recovery; I remember that I've also done the whole clean installation utilising it.

At this moment my 'update recovery' option is disabled, so it must have also been like this before the update I guess
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
So i switched off update recovery and updated from 7th to 21st. No problem. My setup no GApps no magisk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Mine was 'Stock Package' of opengapps alongside with Magisk modules as visible on the screenshots
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Stock GApps is quite heavy. Not recommended.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
I've disabled quite some of its apps after instalation though (google books, games and so on)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That is really strange. I will run some tests on my A5 (A3 is currently waiting a new display).

The OTAs work when I run them with both Magisk and gapps installed.

[MENTION=8031265]kurtn[/MENTION] no issue with Magisk on official reports (most devs use it). Just certain modules screw things up (easily tested with a Magisk uninstall).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fneuf:
Just a quick message to thank the team involve in LOS 17.1. It is quite awesome to see a 2016 phone still alive thanks to your hard work !

To make this more "useful" to the community, so far I only found one issue with 21/06 build : Trebuchet is unable to run.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
You probably installed a GApps package with pixel launcher? That is not compatible.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fneuf:
I installed "open_gapps-arm-10.0-micro-20200625" version, that after verification does effectively come with Pixel Launcher[/URL].

What would be the best way to solve that?

And does that mean that it is not recommended to install anything beyond a nano package of Gapps?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Most installation guides say to use nano or pico. Maybe flashing a smaller package on top will remove the redundant GApps. I prefer clean flash (and no GApps at all)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, you can change your opengapps version by simply flashing a different one.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fneuf:
I second that, it worked! I did it also for a friend I was about to lend a second SM-A310F I have l around.

PS: by the way, can anyone suggest solutions for a clumsy FRP lock
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrvanes:
I have open gapps nano and magisk installed alongside lineage-17.1-20200601-nightly-a3xelte-signed, using twrp recovery. Is it safe to use the embedded upgrade and have "update recovery" in de developer options checked? Do I need to re-apply gapps and magisk afterwards?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
It is safe. No need to re-apply anything. General recommendation: keep your most valuable data at a safe place.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrvanes:
Just for the record: I just succesfully updated to 12 July 2020 without any problem. Thx!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
It became quite silent here... And I think that's because this ROM simply runs flawlessly. No questions to ask :D Thank you!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Well, [GER]Roxxor, not in my case at least :o I've just got into the same issue as some time ago here:

This time I'm updating from Jun 21 to Jul 26 (with Jul 26 LineageOS recovery flashed beforehand) though, and I'll be flashing TWRP in a while for a quick fix :p

EDIT: here's the logcat if anyone's wondering https://pastebin.com/raw/ckwWfZv3 (until 11:18 it was fully booted; there were some GApps crashes so I'll reflash these)

EDIT2: what happened to the ARM stock packages?

[IMG="no arm stock"]https://dl.xda-cdn.com/5/0/6/9/8/6/9/Screenshot_2020-07-28_at_11.26.57.png?key=hffjq9747wFZX9oNME9GTw&ts=1595929135[/IMG]

EDIT3: found the last GApps ARM Stock build (the July 14th one), flashed, and everything seems to be back where it was supposed to.

Having such experiences with LineageOS' recoveries I guess I'll just stay with TWRP for life :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
This happens because opengapps failed to maintain itself across OTA updates, probably a bug in the addon script. People have had the same experience in the past with TWRP and LOS Recovery as it is the fault of your opengapps install. It went away when they fixed issues in the recoveries and OpenGapps, but maybe there are still some broken script installs around.

I would suggest wiping system and then installing the latest ROM, OpenGapps, and Magisk (in that order) to make sure that it is installed correctly and from the latest release.

If that doesn't fix it then a clean install is probably required.

Also you should be downloading the latest stable release of OpenGapps from their website and not directly from sourceforge.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] CBT38:
Hi,

Thks for this ROM !! What is you SOT approx ? I just get 1h30, with 4G...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Yeah, this is what I did and it had me redirected to sourceforge which has there shown me a popup saying the selected package didn't exist
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Doonto:
Hi!

Just flashed the latest lineage-17.1-20200726-nightly-a3xelte-signed.zip and struggle with no SIM-cards detected. Tried SIM-cards from multiple operators and even countries. Tried in different SIM-slots - no result. Ofc, these SIMs work fine in other phones.

Another issue I faced is probably about GAPPS (installed the latest Micro version for ARM, Android 10), but still:

When trying configure the Family link (kid) on this phone - I always get a message "this profile manager is required for google accounts" - google it, and the first result is exactly what I got.

I can manually install the Family link app, make it administrator of the device, but the signing-in tool conflicts with Android, unfortunately...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Hi. I'm no expert, but this happened to me back when I was wandering between variations of modified stock Samsung's images; I think that my EFS/RADIO partitions got fricked and I had either to restore my TWRP backups or reflash the original stock firmware, I don't quite remember so don't take my word for it (again, I'm no expert!)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Update your baseband. You need to be running a recent Nougat modem firmware.

Family link will break your phone (trigger the frp lock), don't use it. It requires you to disable the OEM unlock. Obviously this breaks your ability to use a custom ROM, it used to do it for you :laugh:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Doonto:
Thank you, guys! I suffer from the FRP lock on this blessed phone for more, than a year, and definitely don't want to trigger it again. What I found good about this particular ROM - it doesn't have an option to disable an OEM unlock in the developers options, and even after connecting the google account FRP lock wasn't on.

However, I prefer to do not try)

The baseband (radio, modem) is another thing - I tried about 4 different CP files, found on the Internet without any success. I mean, all the CP files were flashed successfully via Odin, but phone has still no baseband.

I've also seen that Z3X Samsung Tools Pro can restore IMEI and fix this problem, but couldn't find this tool hacked correctly and without viruses.

Why Lineage ROM's baseband doesn't fit to the phone? Haven't seen such a feedback on it before...

I kindly appreciate any links :o
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Ril works just fine but you need to be running the latest modem firmware due to the version of the libraries we use.

If you have messed up your efs partition that will break ril. You need professional tools to repair it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] achkap:
I will try to install a custom rom to this phone and i thought until now that it is simple. Install through Odin TWRP, and then the rom gapps and magisk. But now you made me skeptical, because of the OEM unlock you mentioned. Is there OEM unlock or frp lock that I should watch about? Because I have read a lot and I haven't seen anything
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It is simple. Update to the latest stock version of Nougat first then follow the lineageos wiki.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] HGHJ4:
Hello guys. GPS does not work in the Endomondo app in the background when the screen is off, the track is not recording. When the screen is on, GPS vision works. In the properties of Endomondo there is “battery charge mode” - “do not save power” GPS still does not work when the screen is off in the background.

LineageOS Version

lineage-17.1-20200726-nightly-a3xelte-signed.zip

lineage-17.1-20200726-recovery-a3xelte.img
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like a bug in the app.

There are some fixes for GPS coming in the next build that will speed up GPS lock.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
True. Actually that happens with every GPS-App in the background when screen is off. I actually dont THINK its device specific(but not sure). I somehow linked it to Android 10. But would be nice if somebody has a solution. I guess it's somehow connected to power saving.

Let's see if I can obtain a proper log.

EDIT: Ok, cant find anything specific in the log. Always nicely reporting the location. Unfortunately I cant share the log, as it's full of private information (location, server synchronisation, and "dejavu" (an unifiedNLP plugin) spamming the local WIFIs and location all the time). Impossible to censor adequately.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
Cannot bring LOS 17.1 to my A3 2016

Hello and many thanks to [MENTION=6707196]danwood76[/MENTION] for his great work!

I've got big troubles in bringing the quoted LOS to my Device. Firstly I tried to flash ist with TWRP 3.4. That didn't work, same as with version 3.3. I went back to LOS 16. The installation was completed but the settings failed ("The android setup has been tried repeatedly"). Then I flashed the LOS-recovery but the result when trying to install LOS 17.1 was the same. Now I tried to flash the latest LOS 16 (20200419) but it did't work. It was only possible to install the former LOS 16 which was dated at 20191225, my device doesn't accept any other OS. Since I flashed my former LOS 16 with LOS-recovery, GApps 9.0 was not accepted.

In the Forum I read, that one should install the Stock-firmware "Nougat" to update the baseband. But which one from here should I take?

https://samsungfirmware.net/galaxy-a3-2016-sm-a310f-stock-firmware/

A question besides: is there any possibility whithin LOS-recovery to go back to TWRP? If not, which procedure can be recommended?

P.S. Flashing the inofficial LOS 17.1 to my A3 2015 worked within 5 minutes. But that's really just by the way.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Use this tool to download latest stock. Then you can flash it in odin to update your baseband.

https://xdaforums.com/attachment.ph...rl1u*_ga*YW1wLVBwRVA3NkpSb2ZKOGltbnR3VzR4eXc.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like you screwed up your install.

If you were running LOS 16 happily then you should fine to upgrade to LOS 17 without updating your baseband (you are probably already on the latest).

To upgrade you needed to update to the latest recovery, then flash the latest ROM along with android 10 Gapps and Magisk.

You now need to do a clean install to get you out of it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] HGHJ4:
Hi danwood76. I checked Lineage OS 16.0 for A3 2016. Works in background GPS in Endomondo app in Lineage OS 16.0 - works.