yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
Thank you very much! I've already tried to perform a clean install three or four times. Both with TWRP and LOS-recovery (latest versions). That didn't work. But I didn't try to install Magisk. Now I've got LOS-recovery on my phone. Can I use it again or should I return to TWRP? And if so, what is the easiest way to achieve this? (as I can see there is no possibility to flash an img-file within LOS-recovery). On the other Hand, is it recommendable to try it again this way? Am I blind? What thing am I not able to see? Thank you for your help!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
To perform a clean install you need to wipe data, cache, and system. Sounds like you are not wiping data or cache. Which is causing you install issues.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] klasie:
I've already done it before this way without success. Since I've got a working LOS 16 on my device I performed an adb-sideload and succeded!

There is only a little beauty mistake: handsfree doesn't work. But that was the same on version 16.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Well, this in fact seems to be happening in every GPS app, here's a case study of mine:

- I've been riding my bike for an hour, and Strava had detected movement only throughout half of that time

[IMG="ride summary"]https://dl.xda-cdn.com/5/0/7/5/5/8/7/Screenshot_20200807-202304.jpg?key=4xEgTNFg3YTX_f4mI-YXiA&ts=1596826639[/IMG]

- here's some detail as to what was being reported between the 2 points in time that I'd checked my phone

[IMG="ride path"]https://dl.xda-cdn.com/5/0/7/5/5/8/5/Screenshot_20200807-202453_Strava.png?key=dGDj2OMUgckKkidnH43rOQ&ts=1596826632[/IMG]

I wouldn't ride through a church, would I? :cool:

This issue exists since I'd updated from the Jun (yes, June) 21 to Jul 26 build, therefore it's not just Android 10 specific as a whole.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I have background GPS issues on my Stock S9 running Android 10. My wife and I use an app to track each others location (she has an iPhone and likes the "find my friend" feature), it sometimes says I'm in the middle of the sea when she goes to find out where I am :D

A quick search online and quite a few people are having GPS issues on Android 10:

https://support.strava.com/hc/en-us...-GPS-data-since-updating-Android-on-Oneplus-6

I will take my A3 out when I next go for a ride, the next official build will have quicker GPS lock so this may improve things anyway.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
[MENTION=7472360]witampanstwa_[/MENTION] new official update built last night. Are you able to update and retest?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Oh yeah, will do today or tomorrow evening
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
First test done, and the fix seems to have worked!

[IMG="strava"]https://dl.xda-cdn.com/5/0/7/6/6/7/3/Screenshot_20200809-201800.jpg?key=C5BljwYjS5Lp91ufiOJFUw&ts=1596998286[/IMG]

I've gone straight ahead for a clean flash as to fix my earlier mentioned lineage recovery problems though
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
Good afrernoon. A litle bug i found is that "OK Google" doesn' t work anymore. A few build ago worked. Now the microfone symbol doesn't apear anymore in the status bar. Any solutions? Thank's for any reply.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi, Dan!

Finally, I fixed the Android Auto issue!! I had your unofficial Lineage installed in my phone with OpenGapps, and I re-installed it in a dirty flash -only wipe data and cache- but I installed BitGapps. And it worked!! It must be a problem with Gapps, not with Lineage.

I hope you find it interesting.

Best regards!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That is interesting, I will have to test that out tomorrow.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] munstey7:
Just installed this ROM on my a3, it's great! The phone is so much more usuable now and it runs so fluidly. I haven't encountered any issues so far either
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mehranshabir:
magisk Problem

magisk modules not working in this rom when i instal any magisk module it shows module installation completed without any error but after reboot no module shows in magisk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like you have a bad Magisk install. Make sure you are running the latest Magisk version.

Some modules are not compatible with Android 10 though. You are best asking on the Magisk forums.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Ommahhabi:
Miui

Sir please make miui rom for Samsung a310f
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No chance of me doing it
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Hello guys,

My child I using this A3 and faces a small annoyance.

When stock camera is configured to store pictures on SD, they don't appear in the Gallery. They are effectively on the SD card (Android/sub/sub/... /) directory.

Any other facing the same this?

Any suggestions to correct this behavior?

Thanks for your feedback.

Tim
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi Tim,

This is due to this issue:

https://gitlab.com/LineageOS/issues/android/-/issues/443

In Pie google introduced scoped storage. This effectively means that apps can't access the SD card anymore when targeting the Android 10 API.

In addition to this there appears to be a bug in the media scanner which stops it from scanning the Snap image directory.

As a workaround I believe that OpenCamera still allows you to store to the DCIM folder on the SDCard but this will likely be broken when we go to Android 11.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] :
Hey Dan, i remember i raised this issue a good while ago and i'm afraid i have to report it still persists - i am completely unable to make an emergency call to 112 in Finland, with this ROM on the A3 2016. It simply says "number is unavailable" and cuts off. Is there any way you could look into this? Last time i asked our emergency services if we had a number we could call to test the functionality on custom ROMs, but they said no, test calls of any kind are not allowed. There's pretty much nothing i can do about this on my end.

I tried making the call at least three times. Strangely enough, also my personal OnePlus 5T cut off the phone call, until i rebooted the phone. Then i got through. But only the A3 reports that number is unavailable, immediately after dialing it.

The phones have SIM cards from different operators, so i think that rules that out. This is a fairly scary bug/problem/whatever, i can't imagine having to wait rebooting my phone in a more urgent distress than calling the medics on a hobo in a ditch...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I do remember you reporting that issue.

I have done a bit of searching and it looks like installing Google dialer can cause issues like this. What Gapps version do you have installed (if any?)?

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] :
That's the thing, i only have stock Lineage on the A3, and nothing else. No root, no gapps/microg, no dialer replacement apps. I remember i had the unofficial version of your ROM back when i first reported this, now it's the official version. Clean flashed.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Thx,

Would you suggest extending disk space with an SD instead of external space? Pictures in internal memory is a long term issue, freeing space, etc.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
SD cards are much slower than internal flash and are more prone to failure, so I always use the SD as an external drive (photos are not the only thing stored on there). Lots of people use it as adopted storage without issue though.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] munstey7:
Nah I wouldn't use extended storage. File transfer speeds get destroyed, and I find it better to just use the sd card as a separate storage device where to put pictures and data, while all apps only go on internal for best speed
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
That was my way to go, but not being able to store camera is going to reduce interest.

But you're right, speed is a good argument.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
I've got a speedy 64GB microSD card and use it as extended storage with encryption. The phones performance is absolutely adequate in my opinion, though I did not compare it. Most Apps are stored in the internal storage and the apps userdata is stored on the extended storage. In my opinion the loading times are mostly affected by the low RAM kicking apps, which have to be reloaded. But those are loaded from internal storage. The small amount of user data is irrelevant in my opinion. There are most probably bigger differences for apps like OsmAnd, as there are huge files which have to be loaded. But this data is so big, it either way has to be stored on an external SD card.

Also I have to say that I dont use GApps, which also preserves more performance, as there are less services running and FOSS Apps are mostly more lean, having less external libraries and bloat.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] guillaumesalagnac:
accelerometer not working ?

(newbie here) I just installed LineageOS 17.1 on my A310F, and so far everything seems to be working great, apart from the accelerometer. It's quite annoying because I get no auto screen rotation.

Is it a known problem at all ? any idea what steps should I follow to investigate and/or workaround the issue ?

btw, in case it matters: to install the OS I followed the instructions from the lineage wiki ( devices/a3xelte )
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
F-droid.org SatStat app can show accelerometer signals. Screen rotation can be enabled for apps and homescreen separately
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] guillaumesalagnac:
thanks for the info about screen rotation. however my point is that my accelerometer produces no data ! I installed "SatStap", here is a screenshot:

[IMG="SatStat screenshot"]https://i.imgur.com/9gtWi7Z.png[/IMG]

---------- Post added at 02:49 PM ---------- Previous post was at 02:19 PM ----------

also, as per pinned message on page 1:

logcat: controlc.com / a81039a0

dmesg: controlc.com / 4eaf520f

/data/tombstones is an empty directory

last_kmsg is over 2MB so I had to cut it into pieces: 1: 19eb05b1, 2: 7369cf71, 3: 5d94d9be and 4: 31e8a5aa

(sorry I can't post clickable links as this is a new account)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
[MENTION=6707196]danwood76[/MENTION]: Just want to say thank you for maintaining this old device!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] reg000:
A310F stuttering

I just installed LineageOS 17.1 on my A310F and GAPPS. Now the device is lagging. Video, audio and scrolling stutters unfrequently.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Probably an issue with gapps. Which version have you used?

I think there are some issues in the very latest release.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] reg000:
This one "open_gapps-arm-10.0-nano-20200926"

Just scrolling the settings menu

https://pastebin.com/0BXw3JLB

---------- Post added at 11:23 PM ---------- Previous post was at 11:07 PM ----------

It is not gapps. After reinstall without gapps the stuttering persists.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] drisdian:
Anyone have link to sm-310f/ds version custom rom? Pls
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There is no "stuttering" on anyone elses A3. Are you installing any mods/hacks at the same time?

There are a lot of "performance" mods that actually decimate performance.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
LineageOS official should run fine on your device (previous testers confirmed this).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] drisdian:
I got error 7 on twrp
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Which version of TWRP?

You need to be running 3.4
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sienleun:
I want to use android 10 in my A3 2016(a310f).

But its my first time.

Also can i use Samsung One UI 2.5 in the Lineage OS 17.1?

Please anybody help me
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
No, you can't use most of the Samsung apps, because they depend on OS components not included in lineageOS.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sienleun:
Thanks,

Well,can i use Samsung apps other custom ROMs?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
I think, what you are searching for is no aosp based custom ROM, but a port like that:

https://xdaforums.com/samsung-a-series/development/rom-centaurus-ii-t3931395

It's a Samsung firmware from another device tricked to boot on a3 2016. I don't think, there is any android 10.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sienleun:
Thanks for your answer;

I just want use android 9 or 10 in my phone but same time i want use samsung UI.

So,I dont want use stock android design.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] drisdian:
On attachment capturing the error
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Encrypted?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Then your only choice is a new phone.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jurko217:
This is not true for my a3xelte

[/COLOR]

Hi, i want to tell you, my phone working like a charm! I am using for 2 weeks now RR 5.8.5 (nougat) with magisk, without Gapps (apkpure), enabled Greenify and there is native enabled 8 cores in kernel so i want to share my experience.

Battery in idle 0 percent per 17 hours, 30 min SOT (if i am in job), so if am not using phone, battery backup is for more than 3 days!

More using with data, bluetooth, some games, playing music, battery lasts more than 1 day, which is very good for 4 years old battery.

No lags, restarts or stuttering (especialy in games) and i have tested more roms from android 6 to 10 and i havent found faster rom than this and no overheating!

I think from my experience with enabled 8 cores in A3 2016 - is only question of optimization in custom ROM.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi.

The 8 core hack doesnt work on every phone. I have one phone where it appears to be fine and the other is buggy as hell. Samsung disable the second cluster for a reason and this is usually because it is broken.

Obviously you have been lucky.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kamilkala333:
Hi. Such a problem, this firmware hangs on the logo and does not load further. And only Lineage OS. Version 16 and 17.1. I tried to change a ton of recovery, but it's no use. Put only the firmware, then the firmware and gaps. In recovery, it sews the firmware normally, but does not move the launch after the logo. The phone doesn't even heat up. Samsung galaxy A3 16. I don't know what to do.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lohtse:
Am I able to dirty flash this over your 16.1 lineage OS???
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Official or unofficial?

First update TWRP to v3.4.

If you are running an unofficial build you will need to update to the latest release and then flash the migration zip and you should be able to upgrade to the official 17.1 release with a dirty flash.

Got an official build just flash the latest 17.1 release.

Always make a backup incase it goes wrong.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dorpm:
message deleted.. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You need to be running the latest stock nougat version for your region before installing LineageOS.

YOu also need the latest official TWRP or LineageOS recovery.

Then follow all of the instructions on the official Wiki.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kamilkala333:
If it were that simple, I wouldn't be talking about it. What I didn't do. I switched from the official one. Not start. I don't know why it doesn't start.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
After a failed boot extract this file using TWRP:

/proc/last_kmsg

Then upload it somewhere and send me the link and I will be able to see what is going on.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kamilkala333:
Thanks. Do so.

---------- Post added at 10:12 AM ---------- Previous post was at 09:41 AM ----------

That's it.

https://drive.google.com/file/d/1i0NqtrHdKNdtZuu0qHUETdGIF53feK_c/view?usp=sharing
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Huh. I just want to report that the automatic LineageOS update system worked for me this time since my numerous problems I'd encountered and described in this thread here. The only thing I've changed in my configuration is that I use my samsung 128 gb sd card (the yellow one) as the internal storage, so this might've been it(?) Anyway, thanks for help in the troubleshooting as well as maintaining the firmware :eek:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Thanks for that.

It looks like an issue with your touchkeys (back/recents buttons next to home button). Do they work in stock?

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kamilkala333:
They're fine. They work as they should.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Sorry to bother, though I've yet found another recovery-related problem (lol) After I'd successfully updated from the Oct 4th to the Oct 11th build (and fully booted afterwards), I decided to power off the device and boot it into recovery mode. And guess what happened--it started installing the system update once again! I don't think it's ever going to get as good as TWRP was :P
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
:) Weird. I've not had sent issues with OTA on lineage recovery.

The latest TWRP should be ok for OTAs. But backup restore still doesn't work AFAIK (my build of TWRP 3.4 does work).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Weird. Yesterday I wake up and see this

[IMG="screen showing aod on"]https://dl.xda-cdn.com/5/1/1/7/8/0/7/IMG_20201016_085537.jpg?key=m_AMyaMjLkv4Hxh4B66hfw&ts=1602937348[/IMG]

as if my ambient display had temporarily switched into AOD. I remember this happening on earlier builds, too.

PS You can see the proximity sensor going mad at the time, don't know if that's default behaviour for AOD itself
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], dt2w doesn't work. Any suggestions?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It's not supported and never has been on my builds.

You can have it wake via a hand wave using the proximity sensor.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
That's precisely because of broken proximity sensor that I'm looking for alternatives. Maybe kernel-side?

Thanks anyway and regards,
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Buttons are a good way to wake the phone up. Actually one less press than dt2w ;)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Pierre49976:
[MENTION=7472360]witampanstwa_[/MENTION] and others: how do you enable ambient display?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
You can do it through a Magisk module. Though the problem is that I did not do this! It gets activated by itself (though rarely)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Largephonehater:
A while ago I bought a used A3 2016 because of the official lineage OS ROM. It runs fine except for the keyboard typing. When I type fast it often misses letters I have pressed. Basically it causes me to type really slow ruining the experience. I'm curious if other are / were experiencing this and if there are any solutions? I really love having a smaller phone, I hate that all smartphones are now so big you can't put them in your pockets without causing lots of discomfort.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Keyboard is just an app. You can replace it with whatever you like. Even exotic ones like typewise.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Largephonehater:
I thought I had tried this before, but will do so again. Also found this old thread, but when I try the "solution" at the bottom nothing happens. I know it's a really old thread, but the symptoms are quite the same.

https://xdaforums.com/samsung-a-series/help/galaxy-a3-2016-nougat-kwyboard-issues-t3656581
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
how to backup

anyone has a good

reliable

method to back up and succesfully restore the current running rom [lineage official 16.0] in case something screws up??

i wanna try upgrading to latest 17.1 image.

cheers
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
TWRP Backup
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Hi [MENTION=6707196]danwood76[/MENTION] , Hi [MENTION=8184192]Stricted[/MENTION],

Just testded the Bluetooth low energy beacon advertising on SM-A310F stock Rom. You know, it is essential for Apple/Google contact tracing. I tested with the app

https://github.com/NordicSemiconductor/Android-nRF-Connect/releases/tag/v4.24.3

On Stock rom, I can easily advertise LE beacons. On Lineageos 17.1 (no GApps) I get the error message "advertising failed to start (error 2)". I can run Corona-Warn-App without error message, but if I check with nRF or BeaconScope, I see there is no contact tracing beacon sent from my A3 (2016).

How can I contribute to fix this bug?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I expect you need Gapps for contact tracing as it uses their APIs.

I am fairly certain I emulated BLE beacons on my A510F which uses the same BT stack.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Thanks for the reply.

Yes, I need GApps or microG to provide contact tracing APIs. But this bug report is not about contact tracing. Its about Bluetooth LE. How can I make my A310F make sending BLE beacons?

Fresh installed LineageOS. (Setupwizard now offers to restore a backup). Still not able to advertise BLE beacons.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

My A510F advertises BLE beacons without issue, and my local track and trace app (UK NHS) also works with the beacons showing up on my S9.

The A5 has a different bluetooth chip so I will reflash my A3 and see if I can reproduce it there.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I can confirm the issue affects the A3 but not the A5.

The error is "no free advertiser instance" indicating that it is not possible for it to act as a BLE advertiser.

This must be related to the chipset not supporting this function as the same BT stack works on the A5.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Thanks for testing. As soon I've seen this, I installed stock ROM. There I successfully advertised BLE. Is the issue related to using identical BT stack for different BT chip?

Best regards

Kurt
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It's possible that the API didn't exist in Nougat so it uses a raw packet API instead. But the I'm not sure.

Can you capture some logs from stock enabling and disabling the beacon a few times?

Regards,

Danny