yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
I've tested BLE beacon advertising on several devices with lineageOS nougat. Negative. No idea if that is of any relevance for our issue.

https://xdaforums.com/galaxy-s5/uni...-14-0-galaxy-s5-android-t3476433/post83851077
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kamilkala333:
Hi. Well, You do not know why I do not load the firmware? Everything works on stock firmware.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Danny made one:

https://stats.lineageos.org/version/18.0-20201105-UNOFFICIAL-a3xelte
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] neinjet:
FM radio support not enabled?

Hi, I have installed the lineage-17.1-20201101-nightly-a3xelte.... successfully on the refurbished A3 (2016) phone I got for that purpose. Thanks for your work on making it possible to extend the lifespan of this hardware!

I'm wondering if it is expected that the standard FM radio app that I know from Lineage on other phone models seems to be absent. Trying another app gives an "not available on this device" error or so. From the specifications of the phone it very much sounds that it has the FM receiver hardware. Is the support for it simply not configured or activated in the current Lineage builds? Is there hope that it will be present in future builds? (For me the FM radio feature has been one of the reasons why I'm not getting a used or refurbished iphone instead.) Or am I simply missing something that has to be done for activation?

thanks for any hints

sven
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] neinjet:
In the meantime I found a remark in the A5 forum that there is no driver (for the FM hardware I guess). I suppose the two models are similar so that applies here as well. Too bad. If that is indeed the state of affairs, maybe it would be good to make that explicit in the OP of this thread.

thanks

sven
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Ping [MENTION=6707196]danwood76[/MENTION] , Hi [MENTION=8184192]Stricted[/MENTION] .
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Romsuser99:
Battery

Hello everyone, first of all, thank you for the job. My a3 comes back to life. It's been a month now since I installed the rom. There's one point that frustrates me is the drums. It melts like snow in the sun! I just did a test, I lose 10% in 20 minutes of use (web)! It's huge ! On the other hand, when on standby, it consumes nothing (no drop during the night). I tried a lot of parameters but nothing to do ... Has anyone encountered this problem?

Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Still open
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi Kurtn,

I have had a thorough look into this and it appears that the chipset in the A3 only supports 1 BLE advertising slot, which I can only assume is taken by the Android OS (I haven't actually worked out what acquires it, just that something does during boot).

Essentially this is a hardware limitation.

I can only guess that Samsung never used the vendor BLE implementation on the A3 and instead used the legacy method (probably with lots of hacks knowing Samsung). If I switch to using the legacy BLE implementation advertising then works (I can see the tracking beacons on my other devices). Although I can still only emulate a single beacon at a time (I think that's all the legacy implementation allows) so if exposure notifications are enabled then the NRF connect app advertising doesn't work (and vice versa).

I will implement this change upstream.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Hi Danny, I checked with galaxy S5 klte lineage4microG German exposure notification and nRF. I can advertise in nRF only after disabling EN.

Is that different in modern devices?

Kurt
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Well, the A5 supports 5 BLE advertising slots, so it is hardware dependant. On the A5 I can have the EN enabled and add a couple of emulated beacons.

On my S9 I can add multiple beacons with EN turned on.

The klte probably uses the legacy implementation like I am going to switch to on the A3.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
Hello,

i just formatted everything, updated my twrp to 3.4 and flashed the as of now latest lineage-17.1-20201115-nightly-a3xelte-signed

i have more or less the following questions

1) it seems that battery drains a lot faster than previously on Official LineageOS 16.0 that i was using. is that true? how can i go finding what drains my battery faster? i have install a handful of apps that i was also using while on 16.0 for over a year or so and no new fancy apps installed.:(:confused:

2) and something totally weird.....apparently i just take a pic using the stock camera and i cannot locate where (if) they are saved. even if i choose sdcard or phone from settings the pics i take are not in the respctive dcim directories, nor i can find them in albums in gallery. even if after taking pic i try to click on the thumbnail and nothing happens..as if nothing is saved anywhere.:crying::eek:

So based on the above, firstly im wondering if anyone else faces these problems, but i think ill try dirty flashing next nightlies in case those are resolved in any way. But just another quick question,

how do you go about dirt flashing the next nightly ?:confused:

is it wipe cache, flash rom & gapps? i was always doing a clean flash really so what do i loose from my internal storage if i do dirty flashes?

Thanks guys.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Romsuser99:
I have the same issue with the battery drain...

I dont find any solutions. I had read also topics about this problem in other smartphones. Nothing...:(

Is it possible to install lineage os 16.0 ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Battery usage should be better in LineageOS 17.1. you need to do a few full charge/discharge cycles before Android knows your true battery level. So it is best to use it for a week or so and see if it improves.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
ok ill give it a try, thanks.

somehow on lineage 16 though i never quite did that and instantly since installation the battery was really a lot smoother than stock rom lets say. so you know..fingers crossed for this time.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] taz2230:
Hello

I'm sorry to disturb you.

I am blocked.

The A3 2016 phone offered me an update.

I accepted.

The phone has restarted but it gets stuck on the update.

The progress bar is no longer moving.

I no longer have access to TWRP.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
You can always boot into download mode and install twrp with odin/heimdall. Wipe nothing. Just flash lineageOS. Maybe an older version. If you had bitGApps installed, flash it again. It doesn't survive an update.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] taz2230:
Sure enough, I have the wrong version of TWRP.

Did you know I can find the latest version of TWRP and Lineage? (A3xzlte)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
All in 1st post of this thread.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] taz2230:
I succeeded, I was using the wrong TWRP
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] taz2230:
Could you tell me where I can download the latest TWRP version so that I can install the latest Lineage version dated 20/11/2020?

I found the version in "img" format but Odin cannot install it.

7zip transformed it to me in "Tar" format. But INVALID file.

cordially
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Link in OP

https://eu.dl.twrp.me/a3xelte/
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
where are the stock camera's pics stored?

apprarently whenever i take a pic its nowhere stored..hows that?

gallery has no camera albums, pictures dont show up on timeline and also when searching dcim folders etc in both sdcard or internal storage, then pics are nowhere. after each photo i cant even see the pic i just took because pressing on the thumbnail icon after just taken does absolutely nothing.anyone else had this?

is this a know bug or something?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
You selected SD card as storage in camera app. Pictures are stored in Android/data/org.lineageos.snap/files

To be able to see those pictures, you need a different gallery app. Or you select "phone" as storage in camera app.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The SD storage feature is broken and is being removed. Use internal storage.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mehranshabir:
is there any chances of lineage os 18 for this device?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Yes, there's a chance. No clue how well it is working at the moment. But Danny seems to be on it.

https://review.lineageos.org/q/project:LineageOS/android_device_samsung_universal7580-common

https://review.lineageos.org/q/project:LineageOS/android_device_samsung_a3xelte

---------- Post added 29-11-2020 at 00:09 ---------- Previous post was 28-11-2020 at 23:38 ----------

As you've seen there are issues when using the save to SD-card function. My advice: get a speedy SD-card and format it as internal storage. Apps can still be saved on the real internal storage and be reasonable fast(as fast as this phone gets at least) and you still have big storage capacity.

And damn, I just looked up how much Micro-SD cards are at the moment at a huge global online retailer (everyone knows which one.. they like cloud, satellites and rockets, too) here in Germany sells UHS3 Sandisk cards with 64Gb for 9€ and 128GB for 15€. So they are fast enough and huge.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
Hey Dan, since your post i have been doing full charge/discharge cycles but it hasnt been improved at all not even 1%. i dont know what else i could try. i dont know if anyone else is seeing this. on LOS 16, which is where i came from, it was way better. perhaps some other suggestion?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Thank You.

It works as expected.

https://review.lineageos.org/c/LineageOS/android_device_samsung_a3xelte/+/292872

Always yours for testing

Kurt
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Have you installed Greenify? That can help with battery usage.

To work out what's eating your battery you can use better battery stats (available from XDA), it's most likely an app that is the cause.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] charlander:
Is there a way to install apps directly to sd card?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Anyone tried to add WiFi by scanning QR code? My lineage microG fails. Camera picture is bright and sharp. But no recognition.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leo1leo2leo3:
With this LOS 17 my A3 runs extremely smooth, except for one thing: The keyboard. It skips letters while typing at normal (fast) speed.

Same issue present on LOS 16. Never tested on stock.

3rd party keyboard (Gboard) makes no difference.

I've read about similar issues here and there, but have not encountered a solid fix.

Does someone have a clue or can help me in troubleshooting?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
In the past I've put this down to cheap replacement LCDs. Have you had your display replaced at some point?

You could try setting the power saving mode to max performance and see if it makes any difference (it should rule out CPU speed as an issue).

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] leo1leo2leo3:
Thank you for your reply.

The phone is secondhand so I don't know about any screen replacement. But to me this sounds like the most plausible scenario, since for the rest there's no lag or whatsoever.

I've tried boosting the performance but the behavior stays the same. Sometimes the issue disappears but this happens quite randomly.

Since virtually no one else is reporting similar issues, I'll blame it on this individual phone itself and not on the OS.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Suakey:
Hi mates ^^

I installed this Lineage OS on my a310f and it works very fine. I am comming from ExOs Rom and my question is, how to get the same sound quality like on the stock rom or ExOS?

The sound of Lineage OS is quieter than on the stock rom and seems to have fewer bass and more high frequencies. I dont wanna go back to stock or ExOS becouse Lineage OS is too nice.

So please, have someone a fix for this and can help me?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
@danwood76 unbelievable! Samsung shipped updates for our old phone. Is this a chance, to get vendor patch level updated?

Latest Samsung Galaxy A3 2016 firmware

Download the latest Samsung firmware for Galaxy A3 2016 with model code SM-A310F. Check out our free download or super fast premium options.

www.sammobile.com

P.S.: security patch level is only august 2019:(
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I can check it out tomorrow. It might just be a kernel bug fix. Modem version is the same and as you say security patch level is still old.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
So you say the modem version is the same, I see you updated a bluetooth firmware file on LOS 18.1. Is there any reason we need to flash something? Or is the bluetooth firmware update the only updated file for us?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
Okay, I'll try the Nano version and will provide feedback. Where can I find logging information from the boot up in case it fails again? "/proc/last_kmsg"?

Best regards,

thebinf
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, that is the file I would need.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mik128bit:
Always on Display isn't enabled

Hi Dany,

I've installed it yesterday. Everything works fine. But the Always On Display is not enabled in Settings>Display>Lock Screen Display.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Johnpson:
All is fine but There is a one major bug(WiFi hotspot)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
New release just uploaded!

Changes in the 21/01/2020 release:
[INDENT]- WBS BT calling is fixed
- WiFi hotspot fixed
LOS Updates including:
- Ambient display settings now visible
- System profiles
- Dark mode fixes
[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Johnpson:
Dirty flash?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, it is just like an update.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Thanks, danwood76!! You are our hero!! It's gonna be amazing to enjoy android 10 in our phones!!

One question, I have installed your Official Lineage Os 16 ROM. In order to update to Unofficial LOS 17, can I do it with a dirty flash? Or it's impossible, and I have to delete all my data?

Thank you very very much!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Hi!

One bug is that I have to reapply the "Standard" Colour Profile after each reboot. It gets reset to "Dynamic" every time after rebooting the device. Do you have some influence on changing this behaviour?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
With automatic sleep, wakes up spontaneously after a few seconds.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
Hi,

Probably no one is doing that anyway but it turned out that my installation problems (bootloop after OpenGapps installation) were caused by letting TWRP install its app before first boot. Thus, in case anyone encounters similar issues be sure not to install the TWRP app.

Best regards,

thebinf
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Thanks for the update.

I will add a note to the install instructions!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Talking about recoveries and TWRP nagging about its app: Are you considering the LineageOS recovery? I have never seen it, don't know about the features. But using LineageOS Recovery should prevent such issues, shouldn't it?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
LineageOS recovery is working in my current builds and is a support requirement going forwards.

Unfortunately OpenGapps doesn't currently install in it so I am still recommending TWRP for now.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] alexax66:
Thank you for work under LOS17

I found 2 bugs.

1. There are repeated errors in logcat:

01-23 20:06:54.162 2620 2620 D wrapperGPS: wrapperisConnected_RILD
01-23 20:06:54.162 2620 2620 D wrapperGPS: wrapperConnect_RILD
01-23 20:06:54.163 2620 2620 D wrapperGPS: wrapperisConnected_RILD
01-23 20:06:54.163 2620 2620 D gpsd : WakeLock(Release,GPSD)
01-23 20:06:54.164 2620 6215 D [COLOR="Red"]wrapperGPS: onError: error 4[/COLOR]

This errors occurs because gpsd was moved into /system/vendor/bin and libsec-ril.so and libsec-ril-dsds.so contain a hard path /system/bin/gpsd.

I changed it to /vendor/bin/gpsd and replaced those libs with patched libs. Now no those errors

2. I used f2fs for DATA partition long time since los14, but this don't work in los17.1

Bug in fstab.samsungexynos7580:

/dev/block/platform/13540000.dwmmc0/by-name/USERDATA /data f2fs [COLOR="Red"]nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic[/COLOR] wait,check,encryptable=footer

Must be:

/dev/block/platform/13540000.dwmmc0/by-name/USERDATA /data f2fs [COLOR="SeaGreen"]rw,nosuid,nodev,noatime,nodiratime,inline_xattr [/COLOR] wait,check,encryptable=footer

I fixed it and now all works fine.

Best regards!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Thanks for spotting the GPS bug, I hadn't seen that. I will patch them properly in my device trees.

Not sure about the f2fs changes. Can you format that in TWRP?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Is it because of this commit?

https://review.lineageos.org/c/LineageOS/android_device_samsung_universal7580-common/+/256513

I think [MENTION=8184192]Stricted[/MENTION] was simply syncing the ext4 f2fs mount options, which obviously didn't work :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] alexax66:
Yes!

F2FS haven't noauto_da_alloc and journal_async_commit mount options and have inline_xattr <- very important !

See: f2fs.txt
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Toemmel:
The Problem is solved after I changed the Chache-Partition from f2fs to ext3!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] alexax66:
Mounting CAHE in F2FS format have the same bug as DATA in fstab.samsungexynos7580:

/dev/block/platform/13540000.dwmmc0/by-name/CACHE /cache f2fs nosuid,nodev,noatime,[COLOR="Red"]noauto_da_alloc,discard,journal_async_commit[/COLOR],errors=panic wait,check
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There are a few firmware file updates. I will backport to 17.1 once I have fully tested it.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
But no Baseband/Modem/whatever_partition_not_changed_by_LOS changes? So all updates should come with LOS and we dont have to update something else manually via odin?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Klaus Störtebeker:
First of all: 1.000 thanks and more to danwood and everyone else, to deliver such support for my good old a3 2016. I just started using lineage few das ago.

I got one issue whith using the OS 17.1: the wifi direct does not work. The button in the system options is greyed, too. I'm not sure if it ever worked, but Samsung says it is a feature.

What do I overlook?

Greets Klaus
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It should work just fine. Are you running the latest official lineage? It won't work on my unofficial releases (but they are really outdated).

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Klaus Störtebeker:
Hello Danny,

yes, latest official Version from Sunday. Well, could it be a Hardware defect? My proximity sensor is definitively already wrecked.

If i'm the only one with this issue...

Thanks for reply anyway.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] bikepunk:
Hi,

I've just installed lineageos a3xelte 17.1 latest nightly build on a smA310F.

Everything seems to work smothly except...

when replying a call, the screen goes black after 2sec and remains black untill the call is hanged and the power button is pressed.

As the call is going on, I've found no way to turn the sreen on :-'(

that seems to be a proxymity sensor issue,

as a workaround I've tried to turn off the proxymity sensor but didn't find a way in lineageos :-/

I've tried downgrading to lineage-17.1-20201220-nightly-a3xelte-signed.zip but I get the very same symptoms and I don't know how to get older images.

note that I didn't have this issue with the stock ROM I was using untill today.

any idea of workaround is welcome.

Am I the only one to have this black screen during calls issue ?

ready to provide further info if needed
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Klaus Störtebeker:
I've got exactly same issue with proximity sensor. And tried also mocking the sensor with magisk and Edexposed framework. Sensor mocking worked then, but no changes for phone calls, screen stayed black. That's why i thought it must be wrecked. On my further custom it did not work properly too.

I've got also a310f.

Workaround is the power button (can be activated in system settings) to end calls, but the phone needs some seconds before it awakes again.

Maybe i ruined lineage by rooting and installing edexposed, so wifi direct also got damaged. By time (....) i will make a backup and make complete new installations with wiping to check if this helps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] bikepunk:
I fixed it today by removing the tempered glass screen protector \o/

It was disturbing the proximity sensor.

I'm happy since I can have normal calls again.

But still the stock ROM didn't have this issue with the very same screen protector.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The proximity sensor is used by the dialer app to stop your ear from dialing numbers and ending calls. I would expect you had issues on stock if your screen protector was blocking the sensor from working.

I used my A3 with a screen protector just fine for years so maybe try a new one or another brand.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] WE#GO#:
Hi! Everybody I would like to know if you succeed to install the Gapps in LOS 17. Because I followed the official tutorial on LOS Website. It doesn't work. I probably missed something because it talks about sideload or something like that and I don't understand the process. I found sideload on the phone but what I am supposed to do on my pc.

Thanks in advance for your reply. Cheers
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
How did you install lineageOS?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] WE#GO#:
@kurtn thanks for your reply. I've installed LOS 17 with TWRP
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
So now put the GApps file wherever your lineageOS file is. Wipe system and data. And do whatever you did, to install lineageOS. But now do it twice. First with lineageOS. Then with GApps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] WE#GO#:
Thanks, it works now Thanks very much for your help @kurtn