yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] chertVdetali:
Well, a little tale of my update yesterday. There was a regular build announced by LineageOS updater.

Right after the reboot, the phone was stuck in the boot animation. The only way out was hard-reset via buttons or waiting like 10 minutes until it self-restarts. But the problem looked familiar, I rebooted in TWRP and reflashed the OpenGapps via ADB sideload, and it seemed to work again. But not fully, it seemed like some of the OS settings were lost. Means, applications wanted to confirm their access permissions again and also the initial OS setup wizard was started.

What's the problem now? I saw there was strange battery discharge behavior, down to 20% after a few hours without any activity. So I decided to reboot, just to be sure, and recharge. The result now is: the phone is soft-bricked. I get the "Custom binary blocked by FRP" message and it fails to reboot. The only thing which works is the Download mode.

Not sure how to continue now, my last backup of all data is a few weeks old. Would be too bad to reflash it with stock OS again just to get around the issue.

In hindsight, this setup wizard might have caused the problem. I killed it by swiping and it hasn't come back but it might have triggered the FRP somehow.

Also it's questionable whether I should restore my TWRP backup now. If the problem was triggered by a combination of LineageOS update and som setting there, the problem might come back again, right?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
@chertVdetali

No clue about your issue, sorry I cant help.

But I'd like to add my little tale of my update.

I pressed update. It rebooted. Everything worked as usual. The End.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
Thank you Dan, this is a great ROM! It really makes it easier to live with a slow phone like this.

My comments:

1. The proximity sensor turns screen off normally during a call, but does not turn it back on when you move the phone away. You have to press the power button to turn on screen. I do not use a screen protector glass. I think LOS 16 had some similar issues sometimes.

2. Is it possible to have VoLTE working on A3 2016 ever?

3. When i plug my phone to PC to view files, it freezes after a few minutes. I am unable to access it through PC, whatever file transfer were ongoing during the freeze also stop completely and have to be canceled. I have to change my usb setting to charging on my phone so the phone stops the connection with PC and then re enable usb file transfer to get it recognized again. Once the freeze happens, the PC will not be able to access it and you either have to unplug and replug cable or do the switch from usb settings options on the phone i say above. The freeze has not a regular time of appearance. Sometimes its less than a minute until happens, sometimes it happens after 10 minutes.

I have tried different usb cables and different usb gates. Also the same problem existed with the LOS 16 i had previously and my PC has been changed in its OS as well, so i know its not the PC's fault.

Is it possible the file system of the LOS is causing this?

I think i had changed file system to F2FS before i had to installed LOS 16,and i kept it for this LOS too.

What is the recommended file system on a3 2016 running LOS 17?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
1 never had a problem with that. SatStat app from f-droid can show you proximity signal

2 no VoLTE for AOSP based Samsung ROMs

3 I use default file system and use portable SD card for file transfer due to unstable USB connection
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
@danwood76

I see you added FlipFlap support for a3xelte.

I was not aware there is any proper Flipcase for A3 2016? Somebody got a link?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
@danwood76 there is quite some proprietary audio stuff I don't understand. Is anything of that VoLTE related?

https://review.lineageos.org/q/project:LineageOS%252Fandroid_device_samsung_a3xelte+branch:lineage-17.1
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
They are for audio input filtering. Removes echos, background noise, and improves gain in calls and audio recordings.

Volte is still not going to happen.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There were some official flip cases when the phone came out, I haven't been able to find any for sale.

You can get cheap ones on eBay, the one I bought didn't have the magnet to activate flipflap though (it was very cheap). I just added a magnet.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi, Dan, and thanks a lot for your effort to keep our A310f running in 2021.

I have your Unofficial ROM, and I want to ask you two questions -sorry if it's boring for you to answer these kind of questiones-

1.- What's the difference between unofficial and official? I know Official has OTA updates, but I don't know if tehre are significant improvement developments.

2.- How can I update to official in a dirty flash, in order to keep my apps, data and configuration?

3.- When you launch unofficial Lineage 18, it will be possible update to it from official Lineage 17 without full wipe??

Thanks a lot!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

The Official version is actively developed, the unofficial hasn't been updated since last June. There are too many fixes/updates since then to list.

If you want to flash the official version flash this in TWRP first, it will fix all the file checksums to match the official:

20.7 KB file on MEGA

mega.nz

Also update your gapps and TWRP at the same time.

I will not be releasing any unofficial packages for 18.1 as I have not got enough free time to manage it. The 18.1 patch set is almost complete though so it might be a release day device.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Thanks a lot for all the information!!

So, I have an issue with VOIP videocalls... There is a huge noise, and the other persona can't hear me. Is there any solution to fix it??

Thanks!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The latest official build has some audio filters applied to the mic input which should help/fix that issue.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
Voice input key is not working. I installed with pico Gapps. Is there something i can install to make voice input working?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
What do you mean by "voice input key"?

Do you mean Google assistant? You need a bigger gapps package than Pico. Check the OpenGapps website for what is included in each package.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
I mean when you try to write in the keyboard with voice input. They key gets pressed but nothing happens.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Peam03:
Hey Guys, my friend has this Phone and is still on the Stock Rom. His Phone is lagging badly, his RAM Hits about 1.5gb all the time and even the easiest Animations lag like hell.

So i wanted to ask: is los17 any better? Are the 1,5 GB of RAM really enough to run A10? Is it smooth and reliable?

Which Gapps should i Install to achieve a smooth Performance, Pico or nano? Is the Phone still running smooth with nano Gapps?

Thanks in advanced! Greetings!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
This rom is good without GApps. If you need performance and GApps, you can as-well stay with stock ROM. Installing a custom ROM includes a complete wipe. Instead you can as well do a factory reset to speed up the phone. And disable all unnecessary apps.

P.S.: I have no experience with GApps
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Peam03:
So you mean its gonna perform Bad with Gapps? Okay, then i will stay with Stock (if thats faster than los17 with Gapps)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It runs perfectly fine with gapps installed. It is much faster and smoother than stock. I always advise Pico gapps as it has a lot less of the Google bloatware.

However if your friend is using a lot of RAM intensive apps then it won't help much.

The Samsung bloatware does add quite a bit to RAM usage, you might just try disabling all the Samsung junk first, deleting unnecessary apps, etc.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi!! I have updated the firmware via OTA with the last update launched yesterday and my phone is on a bootloop. How can I fix it??

Thanks!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Bad GApps? Bad magisk Modules?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Reinstall gapps.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Flominator:
hey, Ive took a look at los 18.1 a3xelte unofficial, must say looks very promising, bugs in my build

where:

- gpu overlays not working

-brightness kind a broken

looking forward too see amazing los 18.1 official :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Try the latest build from february. I included a patch from @danwood76 that fixes it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mehranshabir:
Bro Where did you get los 18.1 a3xelte unofficial file, can you share with me?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
I updated to the latest OTA 21 Feb update, with TWRP. It rebooted to TWRP ,was flashing , suddenly screen turns off, reboots and now is stuck at Samsung Galaxy A3 logo.

I recently had an SD card, which i converted to internal storage.

Do you think,that has anything to do with it?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
The latest release i had before i updated, was lineage-17.1-20210207-nightly-a3xelte-signed.zip . Which was installed through OTA update normally without issued with TWRP. That was before i had reconfigured SD card as internal storage, it was as portable SD.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
Ok, i fixed myself because i could not wait for answer.

Here is what i did:

1.Downloaded the previous nightly signed build , plus latest Open pico Gapps and magisk to a USB OTG

2.Turn off A3 ( VOL down + Power for 8 secs)

3.Quickly enter the recovery combination to enter TWRP

4.Wipe Dalvik, Cache, System

5.Install as usual ROM+Gapps+Magisk from USB

6.Rebooted normally

Everything looks ok so far. So it seems an issue with the OTA.

I also have to mention i was using F2FS at my Cache partition. I wiped and formatted to EXT4 before i installed the ROM. All the rest of my partitions use EXT4 with exception of SD card of course.

When i first booted again, i got a notification saying SD card missing ( i have an adopted SD card like i told you earlier), which went away after about 30 secs. Is this normal?

Checking storage it seems all available space is there (80 GB).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
@Hornelen SD going away is not normal. But with adopted storage, all kind of bugs are to expect, because aosp reference device Google pixel has no SD card.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Suakey:
Yes mate, upload broken builds. Love it <3
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Works perfectly fine here on my A3 since LOS is official on it. Rarely app-specific issues appeared, the ROM was always stable as itself with adopted storage.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Suakey:
Thanks good Sir.

If someone had problems too updating to latest build then follow this tutorial. Is used the

lineage-17.1-20210207

build and it works now.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
Ι used the lineage-17.1-20210214 release. It might work with the latest release as well, if flashed liked i said above.

We do not know what the issue yet is, if it is the release itself, or an issue with OTA.

Or even Gapps perhaps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Try to wipe system and then install latest ROM, gapps, (and Magisk if used) in that order. Occasionally gapps fails to reinstall correctly when using TWRP.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] KilluaGaming:
Hey bro I really appreciate your work. I just wanna ask you on how to fix the network issue. The simcard is detected but no signal. Thank you!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It depends what's causing it.

Does you sim work in stock?

What baseband version are you running (you can check in phone info)?

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] KilluaGaming:
Hey bro it's my fault I tought it have no signal because of the cross mark in signal.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
@danwood76

I just want to say thank you for all the development! I am now switching to the Oneplus 3 for 65€ :D (Main reason: Upgrade from 1,5 ->6GB RAM). 1,5Gb RAM was just not enough sometimes and very painful to use when e.g Web Browsing. The A3 was a perfect companion all thanks to you!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] truitedeluxe:
Hello guys,

I just migrated my phone from stock ROM to last LOS 17.1 builded for a3xelte.

Everything works fine, but I have GPS issues. It's simple : I have no signal, no matter what app I tried.

GPS Data APP shows me almost no sat and 0 Fixed while my wife's phone (same model, but still stock ROM), show many sat and many fixed.

My phone : Model SM-A310F, Android 10, lineage_a3xelte-userdebug 10 QQ3A.200805.001 b21b9934f2 :

Her phone : Model SM-A310F, Android 7.0, NRD90M.A310FXXS5CTJ2, Kernel 3.10.61-13952378 :

Everything worked well on my phone before migration, so I guess it's not HW related.

I read many threads and many posts on here, but couldn't find any solution.

Last thing I tried was to overwrite /system/etc/gps.conf with stock ROM version and reboot phone, but it didn't fix the problem.

Any ideas ?

/system/etc/gps.conf (got it from Stock ROM)

NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://gllto1.glpals.com/4day/v3/latest/lto2.dat
XTRA_SERVER_2=http://gllto2.glpals.com/4day/v3/latest/lto2.dat
SUPL_HOST=supl.google.com
SUPL_PORT=7275

Some logs :

Spoiler content hidden.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I have just done a clean install on my test device and got a 3D lock to 6m in around 45 seconds.

How long did you leave it for after opening the app?

The first lock can take up to a minute to achieve but after that should be near instant when reopening.

Also I would advise against copying any files from stock, stock is a very old android version and so files from there may not be compatible with LineageOS. The GPS config is a prime example, you can correct your changes it by simply reflashing LineageOS.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] truitedeluxe:
Hi,

Thank you for your advice. I restored a TWRP backup that I made before making any changes. So I'm back with a clean LOS now.

I tried leaving the app open for 15 minutes and didn't get any 3D lock.

Sattelites keeps appearing and disappearing without ever lasting.

I did a try with GPSTest APP and collect some new logs while it was searching.

I found these could be relevant :

NmeaUtils: Couldn't parse geoid altitude from NMEA: $GPGGA,133548.18,,,,,0,00,999.9,,M,,M,,*67

04-01 15:35:51.909 4899 7076 W FirebaseInstanceId: Failed to find package android.content.pm.PackageManager$NameNotFoundException: com.google.android.gms
04-01 15:35:51.911 4899 7077 W FirebaseInstanceId: Failed to find package android.content.pm.PackageManager$NameNotFoundException: com.google.android.gms
04-01 15:35:51.912 4899 7077 E FirebaseInstanceId: Google Play services missing or without correct permission.

Does Open GApps needed to make GPS works properly ?

The thing is, I'd like to avoid having any google layer on my phone.

Thanks for your help.

Regards,

Truite

Full log here :

Spoiler content hidden.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Has karmakar taken device maintainance?

https://review.lineageos.org/c/LineageOS/lineage_wiki/+/307403
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
He is the a7 maintainer, just getting excited. Not quite ready yet.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] awawi:
Hai, Dani

I have problem with this rom in my A3 2016 with gapps, without magisk.

Some application from play store says my device is rooted, so I can't use that application. any solution?

thank you.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
This is no A3 problem. This is the safetynet feature from GApps. Safetynet can be cheated with magisk, but breaks again, when Google changes detection.

I strictly avoid apps with that "root" detection.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Install Magisk and use hide for those Apps. Ironically my banking apps only work with Magisk installed 😜
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Explaining the joke will kill a unicorn. Nevertheless: The worst thing you can do for device safety is rooting with magisk. And exactly that is needed to get safetynet attestation for running banking apps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Alicee3:
Hey Danny, can I have the 8-core boot.img for this ROM? (Cuz my phone is stable even with 8 core enabled + full-throttled. Also, I don't know how to modify kernels so the last thing I can do is asking you for help :X)

Thanks for reading!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

No. I have never produced a kernel like that as I do not support overclocking.

The official kernel is fast and stable. There is no point in overclocking such a low power device.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Bastaxic:
Hey there, I am trying to install this custom ROM to my A3 2016, but the home button of my phone is broken.

I can use ADB to enter download mode and then use Heimdall to flash TRWP, but I can't figure out a way on how to reboot into recovery immediately afterwards. ADB does not detect the device while in download mode, and only after rebooting (volume down + power) once the Samsung logo starts blinking I can use it to enter recovery.

However, this seems to be too late, TRWP seems to have been overwritten already, and I seem to enter the stock recovery environment. Any ideas (besides fixing the home button)?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] eu7tFeTyT7vfPy:
Hello, very new user here. Can banking apps be used on this? It's the only issue I could see occurring when flashing LOS to my device, as I don't intend on using any other "popular" apps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Out there is a fantastillion different banking apps. Some of them work, some refuse to work because they detect a modified system. Some can be cheated by magisk to run despite
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
If you have adb and root you could flash TWRP directly to the recovery partition using DD and then reboot to recovery. If you don't have root then the only way is fixing your home button.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Magisk hide always works for my various banking apps. Just be sure to enable magisk hide on the banking app before you run it for the first time (may require a clean install).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi, Dan!! One question, are you thinking about launching a LOS 18.1 version for our A310f devices in the future??

Thanks a lot for all your work!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
https://review.lineageos.org/c/LineageOS/hudson/+/307404
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
clean installed lineage-17.1-20210704-nightly-a3xelte-signed and i have to say things are much better batterywise than around a year's old nightly i had been using so far. it had become very slow after about 1 year use so i gave a go at something fresh and i have to say all is good :)

thanks danwood :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lohtse:
Anyone else not able to use ANT+ devices with their a310f??? ant+ service just crash.. is there a fix?

I know I could use them with stock....
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No idea. I don't have any ant+ devices. Are you able to produce a logcat of the crash?

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] setecastronomy:
Hi,

is there a way to optimize application memory usage in LOS17.1?

I have been using A310f with your OS for years, currently only for regular messaging and navigation and similar tasks. While being mostly happy with it, in the last couple of months the performance of certain activities is at rock bottom. Very much visible during application switching. For example: open Firefox with a dozen of tabs, switch to a newsreader (already sluggish), reopen the launcher, starts Google Maps. Result: you wait, and wait, and wait, almost 10s while the app finished rendering first screen, then you want to enter an address into the text field, and the keyboard gets stuck for another 5s until it becomes ready, and then it repeatedly gets stuck while you are typing.

I know this kind of symptoms from my older phones, those are signs of memory exhaustion. And checking "top -s6" in terminal confirms it - we are by a few hundred MiB in Swap right after fresh startup + opening gmaps. Started route calculation in map -> boom, almost 500mb in Swap, only 56mb free in Mem. And it's not like there a single significant memory eater in the task list, the extra fat is spread among dozens of tasks.

Can we do something about this mess or is it time to buy a new phone? I remember tricks like "memory compression" and "buffer compression", could this be applied here?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
In your case i would replace firefox with bromite and disable Google app.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Which gapps are you running?

The A3 should have plenty of ram for the usage you describe.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pjaap:
I can confirm this behavior. Since I have the Corona Tracing App Germany, Signal and Firefox on my A3 the RAM is full right after boot. I checked "top" over ADB and confirmed that the device is swapping a lot. I already disabled a lot of Apps (I'm using microG), and force-close most things but the system performance is very slow. I think 1,5 GB RAM is not that much. I think I will switch to a 3 GB device. Although I will really miss the form factor of the A3 :(

BTW: Is there any news about the 18.1 release? The gerrit commit is now open for months and nothing happens ...