yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Ok, so the family link app is modifying the FRP partition directly via google play services and enabling the "OEMLock".

The only way you can get round this is by wiping the FRP partition before each boot, however this is not ideal and could never make it into an official release (you would also be defeating the point of the family link).

My only suggestion would be to use one of the alternatives available. Essentially family link is not compatible with LineageOS on our devices, if you need family link then use stock.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] heilbron:
Thank you very much for looking into this! You saved me quite some time and efforts, since I was almost into buying some more A3's for my other kids!

I would also assume, that LineageOS and Familiy Link are incompatible with any Samsung with Factory Reset protection (FRP)?!

So it would be probably good advice to check in the other LineageOS Samsung forums first, before buying a Samsung phone with FRP....
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rolujas:
Instale todo normal, pero en el ultimo paso a la hora de hacer reboot se queda en el logo de la room :(

help
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
English, please. And re-download open GApps. They had problems last week.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It sounds like the galaxy S5 (klte, not the s5neo) doesn't have the OEM lock so it won't get triggered with family link. I think anything S6 and later has the OEM lock (so you are probably looking at phones before 2015).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You need to follow the install instructions.

Wipe data, system, cache and then install. It sounds like you didn't wipe the data partition.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rolujas:
Todo muy lindo y bien. Pero el teclado no se puede usar. Probé usando otros teclados pero lo mismo, muy lento, 0 fluidez. Alguna solución ? Seria una pena dejar de usarlo solamente por el teclado :(
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Please reply in English, Google translate if you have to.

On first boot if you installed stock gapps the phone can go nuts for a while as it is optimising the apps (and stock gapps installs a lot of stuff). Please wait for a few hours, it should start working correctly.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sekil:
Hi.

I'm rewrite and fix libexynoscamera, camera.universal7580, libhwjpeg - can build and use from opensources.

camera.universal7580 - working good

libhwjpeg - working good

libexynoscamera - have some bugs (freezes when using bar scan apps, when using snap..) - need time to fix this.

some info about snap freezes in -

https://github.com/Exynos7580/andro...los-14.1/libcamera/34xx/hal1/ExynosCamera.cpp

if remove string

m_autoFocusContinousQ.pushProcessQ(&frameCnt);

or delete comments with "skip count ifelse" - snap not freezing when starting.

i'm think - this related to continous mode of focus - need rewrite and add some locks, unlocks..

If interesting - all changes in 7580 git.

i'm change phone and stop working on this... thank
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rolujas:
A day has passed.

The keyboard is still slow! :bueno:

I used google translate ja :dedos cruzados:

Any other solution?!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Interesting that you got the camera hal building and working.

The libexynoscamera freezes are caused by the multi threaded architecture of the Samsung driver. I worked around this with my wrapper.

Basically the camera hal calls one or two of the callbacks and at the same time the camera framework calls for example cancelAutoFocus. cancelAutoFocus waits for those callbacks to complete before it exits but the AOSP camera framework is not processing the callbacks so you get a deadlock. In my wrapper I pass the callbacks off to a worker thread which stops this issue, I might be able to fix it properly if I can build the HAL.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sekil:
Ok.. if you have time - maybe you fix all problems. If need help or other - you can pm me.. (i'm spend many time to understand how fix for our soc - many related to config header)

p.s. i'm try run hal3 but not working - need research...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ginone:
FM Radio

Hello,

It is possible to make the FM Radio usable ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Please try reinstalling. Make sure you wipe data, system, cache and then reinstall. Try using just the Pico gapps and see if it improves things.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
[MENTION=6707196]danwood76[/MENTION]

Why did you remove the equalizer? I used it on Oneplus 2 for my bluetooth headphones and need it also on the A3 to achieve proper sound.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
I was sad about it, also. But now I'm glad to have moved to viper magisk module. It works with much higher reliability.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
The integrated Equalizer worked perfectly fine for my usecase (at least on oneplus 2; not sure if there's a functional issue on a3xelte). I don't use magisk and I just use free (as in freedom) software. Especially software that is deeply integrated into the system and not sandboxed. I don't think it should be dependent on the device maintainer which apps are supposed to be included. LineageOS should have its standard set of tools provided with the ROM. If apps are to be excluded, that should be a decision of the complete team.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Unfortunately audio FX has issues on our devices.

Audio FX relies on proprietary blobs for audio processing anyway so there is no real difference to using viper in that regard (you would have used blobs on your op2 without realising). Also Magisk is open source.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
I knew about magisk being open source (I still prefer not having a root solution, but only using it when really needed over adb), but not that audiofx is also using blobs :/ Thanks for the info. (Ultimately I would like to get a Librem 5 or a Pinephone to evade proprietary components as much as possible).

A question about battery: I use my phone without GAPPS(also no microG, only UnifiedNLP for NetworkLocation), so I do not have GCS which certainly gives me a penalty in battery endurance. In flight mode there's almost no loss, so the ROM should be fine. But my results are horrendous, I get barely a day of battery with almost not using the phone. If I use the phone a bit more I can forget to get a day of battery life. I already optimized the apps use as much as I could to preserve battery.

How well is your battery doing? Maybe I should replace my battery?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I do not use my A3 as my main phone any more, when I did I was getting 3-4 days out of a charge with my usage (a coupe of short calls a day and quite a few WhatsApp messages).

When I used it without Gapps it was even longer, but I didn't have WhatsApp installed (or any of my other apps for that matter).

Since I stopped using it I removed the battery and replaced it, my old battery was swollen and about to die after ~3 years usage so it might be worth replacing yours. Just be careful when buying a replacement as there are lots on the market without the NFC antenna (it took me a few attempts to get a new battery with the NFC antenna).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
I bought my phone in 2016 and 2 months ago I've had the battery replaced. Before the replacement I was unable to get even a day (!) of normal usage (it's usually been sth like 10 hrs). Now it can handle nearly 2 days of the same intensity use, what clearly states the battery was quite dead.

As a sidenote, I use Gapps in pair with Messenger, Magisk and Viper4AndroidFX; I have not been applying any special optimisations either.

I've attached some screens of my current usage stats (I've charged the phone up a bit when I got back home, hence the small spike going up).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
[MENTION=6707196]danwood76[/MENTION]

I see that you are also doing some work on LOS 17. Are your testing builds booting/functional? Major bugs still there? Just asking because I ordered new backplates and a battery. I'm going to continue using this phone and it would be nice to know if LOS 17 is a realistic expectation.

Thanks for all the efforts!

EDIT: This is obviously not a ETA question. Just asking for the state of things at this very moment.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
LOS 17 in its current state runs fine on the A3, but LOS17 isn't ready yet.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], I have just installed mokee 9.0 for a3xelte and it's working fine for me so far, very smooth and reactive.

Well, of course, it needs a little more testing to get a full idea of the quality of this rom.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
MK90 is android pie ... And off topic here.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Sorry
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
By the way, I discovered a bug: In Display Settings the "Dynamic" color profile is too vibrant for me, so I changed it to "Standard". After every reboot the setting gets reverted to "Dynamic", and I have to reset it to "Standard". Basically an annoyance. Im happy I do not have more to complain about. Splendid ROM!

Edit: Well never mind for me. I hate Samsung again. I tried to replace the battery. ( https://de.ifixit.com/Anleitung/Samsung+Galaxy+A3+2016+Akku+austauschen/91779 ) Everything worked fine (got the backplate off without a single scratch, even though I ordered one if it goes wrong) up to step 9. I just wasn't able to get in between the battery and the the rest of the assembly. Was fiddling around carefully to get a good angle for 20 minutes. One second my wrist slipped, caught the micro usb port and broke the daughter-board, so USB-Data and the menu button are not functional anymore. Now I actually have a broken (destroyed by my sister) replacement device which I could get the daughter-board from. But in order to replace this I have to remove the display from the rest of the assembly because the buttons are wrapped around and fixed to the daughter-board. Now I don't have the right tape anymore to reattach the display assembly. I'm fed up with this.

There are 3 factors making this repair unnecessarily hard:

1. You cant replace the battery from step 6. The frame is just slightly too small for the battery to fit trough.

2. The battery is stuck upon with a extremely tight strip.

3. There is not a single even tiny gap just to get a tool properly between the battery and assembly to remove those from another.

Sorry, just had to release some steam. Going to calm down a bit and then I'm trying to detach the screen install the new daughter-board (wrap around those stupid buttons), reattach and see if I can get things to work. I'm honestly pessimistic. Otherwise that means: New phone.

EDIT2: Aaand. I got a cheap used A3 2016 in Mint condition. Back in the game :D

EDIT3: Now that I needed to unlock a new device I saw that there's a new security update by samsung, which you already set as vendor patch level. I downloaded This update, but it failed at flashing "hidden.img" in Odin. I flashed all other partitions without issues. Is "hidden.img" needed? Which partitions are necessary to be updated? Is this somehow possible via TWRP? Thanks!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
[MENTION=6707196]danwood76[/MENTION]

As you updated the vendor patch level to 08.2019( https://review.lineageos.org/c/LineageOS/android_device_samsung_a3xelte/+/264440 ), I think it would be good if you could address how to correctly upgrade to this patch level? As I described it was problematic for me to flash the new firmware via odin. But the patch level only is true if all partitions are updated. Are also the binary blobs updated from the mentioned update?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You do not need to do anything apart from update via OTA, the vendor patch level relates to the security patch level of the ROM I pulled the latest blobs and kernel patches from.

The latest A3 vendor update consisted of a couple of trustlets and an updated camera firmware.

The only other thing that you could update is the modem/baseband, we were on version 4 (9th character of your baseband version) for a very long time on the A3 (since start of 2018) and now it looks like there is a version 5 for certain regions/carriers. The vendor implementation (libril) is the same for the newer baseband so there is no need to update, LineageOS should run just fine with a Nougat version (3+).

If you really want to update the baseband you can extract just the modem firmware from the latest flash file (obtained with samfirm software) and then flash it in Odin, I'm sure there are loads of guides around on how to do just that. There are also ways of doing it via TWRP.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
Does someone else have problem with the built in calendar? It does not notify me.No sound,no wake up screen.I used 2-3 third party calendars and only one worked as it should.Is there a way for the default samsung splanner to be installed and work on this phone?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I never had any issues when I ran it as my daily and I have tested just now and not had issues. Do you have "do not disturb" enabled? Have you actually enabled the alarm for your calendar events?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
When I navigate to sound>advanced>do not disturb there is a button at the end "activate now".So I believe it is not activated.However when the screen is on,there is a pop up window and sound.When screen is off/locked there is a pop up window which is silent and the screen doesnt wake up.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Hi [MENTION=6707196]danwood76[/MENTION]

Got a hint from a S5 neo user: Facebook lite shows a blue bar where a navigation bar could be. Same in our A3
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That is clearly a bug in the Facebook app. Complain to them, no other apps have that issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
I tried everything I could think of but nothing.I reset the phone and now all are OK.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
[MENTION=6707196]danwood76[/MENTION]: Just wanted to say: Thank you for supporting this old device. Merry Christmas and a happy New year!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Subagoy:
Pixel launcher always not working. Tell me how to fix it
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
OpenGapps of nano or smaller is supported on lineageos. It is possible to make larger versions work but you need some hacks.

You are better off sticking to nano gapps
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
Bootloop with TWRP 3.3.0-0

Hi forum, as one can see i've got a bootloop with TWRP 3.3.0-0 and LOS 16.0 a3xelte (20191225). Has anyone got an idea how to fix it with as little effort as possible? Which entry in the terminal is required? Thank you very much!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Wipe system, flash rom and new downloads of all addons you had before.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
Now i've done what you suggested. The restart activity is displayed at the screen and after a while TWRP appears again.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Then install less: only rom (and GApps if used before. Make sure it's fresh and the right flavour)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
Meanwhile i've made a fresh new install. With the associated backups it is not heavy work at all. But now i do not intend to change to TWRP unless it is necessary. Before, i tried to check the updates in data/data/... , now i wonder whether the updates will work otherwise. LOS 16 is the first official Custom one i've installed and therefore i've got to learn very much from now. And i like it! :o
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] niltu:
Hi [MENTION=6707196]danwood76[/MENTION],

thanks for the effort that you put for this ROM, it works perfectly fine except one thing... the video quality on social media (Instagram,Twitter) is really bad :( I don't know if I'm the only one who is faceing this problem. Can you please fix it?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
This has been reported to me before but I was unable to reproduce it.

Have you got a good internet connection? These services will lower video quality for poor quality/ low bandwidth connections.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] niltu:
Yes, I have no problem with the connection. Also this issue didn't exist on stock ROM. So I guess it has something to do with Lineage OS.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You have to remember that stock is Nougat. There are lots of new features in Oreo/Pie. Some of which help with data usage.

Like I said, I tested Instagram that a previous user commented had the same issue and it worked perfectly (I watched hd videos without issue). We use the stock video codecs from the A3, so I think it must be a connection thing.

Are you able to produce logs of it for me to debug? Run Matlog (available in the playstore) and then reproduce your issue. Once done upload the logs to Google drive and send me a link via pm. I might be able to see something that could pinpoint the issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
Good evening to all.I have to say that using for some time now this rom made both the phone and my day better! It feels so smooth and stable that it changed my mind of throwing it away.However the last days I am taking it to my job and I am using a (corded) headset.The problem is that when someone calls me,the calling tune does not ring on the speeker but only on the headset.That is really annoying because I do not have the phone always on me so I miiss calls.Is there setting,a trick,a mod,an app or magisk module that can change that? thanks.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
You can enable "also vibrate for calls"
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
I thought of that but many times I have to be in the warehouse or next office,so I do not want to carry it everywhere on me.The same applies in the car.I do not want to be"connected" with it all the time,just when I have to answer.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Looks like a job for mi band 2 and gadgetbridge.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
Or someone find a way to mod it with the to enable it and if someone wants to disable it then just mute the sounds. This was enabled in android 6 and 7... I think.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ochurlaud:
Notifications issue

Hi, I use lineage everyday on my A3 and it works really smooth. I have 2 issues that are always present:

- notifications: I use Firefox, when I download something, the notification doesn't disappear when it's finished and I have to kill the application to clean the notifications. It's the same with the stock music app of lineage, after playing a song, I have to kill it to remove the notifications.

- music app: when the music Playlist is over, I have to kill the app to play another song.

Thx again for your work!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
Hello. I'm using this ROM for a longo time and it's wonderfull, but today i found a litle bug on the default messenger app. When o try to start a new SMS with the + button, the app crashes and close. I'm using the latest nightly build. Any solutions? Thanks.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Long press app icon tap info tap storage delete cache and app data.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
Thank you for your ideia but continue to crash.:(
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
cannot answer incoming calls while already using the phone

Firstly i want to thank all guys who help maintaining the system. Great work! Now i've got a little problem as described in the title. While being busy with my phone it is not possible to answer incoming calls. The corresponding icon is out of order. Has anyone had the same issue and could already solve it?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] niltu:
I recommend you to use Google Message.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
O did a clean install and then it works ok.?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ochurlaud:
Any idea about my issue? It could be worse but I would love to fix it..
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Nobody else experiences your issues. Have you tried a clean install?

Maybe a mod you are using is causing your issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ochurlaud:
I don't use any mod. Ok I wanted to be sure that if it was only me or something known.

I should try the clean install then. I hoped not to have to do it :S

Thank you!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kipphebel3:
My SM-A310F ordeal :)

Finally installed LOS 16 on this device. It took all day, because I am stupid and forgot to check that OEM Unlock was on. It was not so after entering Google creds and rebooting, the unit was bricked by "FRP Lock"

This is what I did to get around the problem: Flash, stock FW, but... What FW??

There is no specific FW for Finland so I took a German one (A310FXXS5CSF3_A310FVFG5CSF3_A310FXXS5CSF3_HOME). Problem was that Odin barfed on the infamous hidden.img file. Solution:

Extract all files in the TAR archive, remove hidden.img and create a new tar, using a recent version of 7-Zip (19.00 x64)

Then create a checksum on that file:

BIN\md5sum -t A310FXXS5CSF3_A310FVFG5CSF3_A310FXXS5CSF3_HOME.tar 1>>A310FXXS5CSF3_A310FVFG5CSF3_A310FXXS5CSF3_HOME.tar

BIN\mv A310FXXS5CSF3_A310FVFG5CSF3_A310FXXS5CSF3_HOME.tar A310FXXS5CSF3_A310FVFG5CSF3_A310FXXS5CSF3_HOME.tar.md5

(Stole that from tar-tool 3.10.7)

Then flash, using ODIN

Then go into recovery and do a factory reset and clear cache. If you fail to do this, the phone will boot forever, as opposed to 10 minutes

Phone was now stock and sim was working (had issues with that the first time as modem.bin had gone AWOL)

Time to TWRP!

Odin 3.14, install twrp-3.3.0-0-a3xelte.img.tar, no reboot

Power off by vol down+power and then fast as a weasel volup+center+power

You are now in TWRP

Wipe

install Lineage (lineage-16.0-20200208-nightly-a3xelte-signed.zip), Gapps nano (open_gapps-arm-9.0-nano-20200208.zip)

Wipe cache/dalvik (check both, do not install)

Reboot, do not install TWRP app (19:07)

Phone ready at 19:10

My biggest issues, apart from forgetting OEM unlock had to do with finding the correct image. There are lots of them floating around and you need one with the same version or later. The other issue was hidden.img and the fast that an older version of 7-zip created an archive that Odin would not accept.

Hope this helps someone!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
I once had the same issue and I got around by first flashing this: A310F_MODIFIED_COMBINATION_FOR_BIT3_FIRMWARE.rar, then the latest firmware available then.

Lately, I've lost imei on that same device and the only solution was to flash the version of firmware that comes with a superior number, in this case number 5 as this firmware (the German one, the same you used): A310FXXS5CSF3