yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
What do you mean by ghost touch?

Is it caused by the screen protector?

The touchscreen driver is in the kernel and is the same as stock so I'm not sure what can be done. Unless it has a sensitivity setting I don't know about, I will check later on.

Kind regards,

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

On the A710FD, the volume up and down keys do not work properly, you have to try several times to increase or decrease the volume.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like a hardware issue to me. The A5 is almost identical and the volume keys work fine on my test device.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mihancad:
There is no problem in lineageos 17.1 version, so I informed, but I will check again and inform accurately
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
You can enable in developer settings to show the touch events. I get around 10 touches per second spread all over the screen. Stops the moment i plug in charger.

No protector.

Thanks for taking your time.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Are you able to reproduce the issue and then reboot and dump the /proc/last_kmsg file and send it to me?

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TheRain12:
or i gave up danny, i'm a youtuber and when i shoot videos on roblox, the phone gets hot and the game shuts down (10 minutes after starting the game) so i will switch to Alpha Centauri V3.0 (with a pixel interface) it won't have any heatsink because alpha centauri base is samsung stock romu. Even though it warmed up for about 15 minutes while in stock rom, the games wouldn't close. Even in Oreo LineageOS 15.1 rom, it wouldn't close immediately (your rom)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sbocconi:
Hello,

I have an A510F with LineageOS 17.1, it works fine but the microphone quality became worse with respect to the stock ROM.

I have 2 simple questions:

1) Is this problem common with A510F and LOS 17.1?

2) Is LOS 18.1 going to improve the situation?

Many thanks!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
@danwood76 will there be updates for 17.1 or 18.1 ? I have to decide about fixing my broken a3 2016

... And maybe some idea what's stopping auto-focus.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Changes 19-08-2022:

Synced to latest LineageOS source (including August security patch)

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I am still updating 18.1 when I get time.

With regards to the af issue. Which camera app are you using?

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Thanks. I'm using the camera shipped with your build. Usually rebooting fixed the issue for a few weeks. But now 17.1 microG fork started working after a week lying around powered off.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
Does it possible to release microG build please?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] poow:
Is it intended behaviour if I get a Trust notification saying that this build was signed by public keys? (I followed the upgrade steps from official 17.1, but without any Gapps.)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Beta123MAX:
Build are signed with public keys.

Don't know what you mean by "intended". But it's, generally spoken, a relevant info and it's right. The signing key warning can be disabled. This is what I did, as I didn't feel the need to get the same info again and again.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
@danwood76

I have a serious issue with this rom: I can't hide magisk from apps (specially my banking app).

It seems the rom has already 'su' (or any kind of) binary and it is impossible to hide with 'magisk hide'.

Does it possible to release not-rooted version?

Does it possible to provide a falshable.zip file to remove stock 'su' (or any kind of) binary?

Could you please help me to find a solution to hide root? (I tested Magisk + LSposed + ApplistHide)

Thank you!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Banking apps use lots of different ways to decide you are "rooted". Unfortunately most simply detect a custom ROM as rooted.

Check the advanced hide options for your banking app and make sure everything option is ticked.

Also reset the app data after hiding everything. You also need to use an old version of magisk before hide was removed.

Good luck.

Kind regards,

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

The first thing I want to do is to thank you and your team for your efforts in keeping our old mobile phones working.

On the other hand, I tried to install lineage-18.1-20220819-UNOFFICIAL-a7xelte.zip today, developed by you on my Samsung Galaxy A7(2016) SM-A7100 with Snapdragon, and it gave me the error you can see in the attached picture.

I would like to add that I bought this phone from Amazon and I think it comes from Hong Kong.

What could I have done wrong in the installation?

Thank you very much for your answer.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Beta123MAX:
Only Exynos 7580 based devices are supported.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Joanga:
Hi Betta123,

Thank you for your answer.

Because you are in the world of custom Roms,

Do you know if anyone has developed a custom Rom for my phone?

Thank you very much
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Beta123MAX:
No SM-A7100 custom Rom thread on xda, sadly.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Hello,

many thanks for your great job.

Does it possible to release a 'dev-keys' build?

I'm on a SM-A510F, but a lot of apps does not work with a 'test-keys' signed rom.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
There is more about it than test keys. There are many device integrity checks out there. But most depend on Google safetynet attestation. Learn how to fake that with magisk.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
In my country, the first check is "rom signed with public keys".

Can magisk hide that?

I'm using my LOS 17.1 personal build signed with my private keys, and got no warning about security issue while using gov's apps.

ro.system.build.fingerprint=samsung/lineage_a5xelte/a5xelte:10/QQ3A.200805.001/rik09110937:userdebug/dev-keys
ro.system.build.tags=dev-keys
ro.build.display.id=lineage_a5xelte-userdebug 10 QQ3A.200805.001 eng.rik.20220911.094053 dev-keys
ro.build.tags=dev-keys
ro.build.description=lineage_a5xelte-userdebug 10 QQ3A.200805.001 eng.rik.20220911.094053 dev-keys

ro.system.build.tags=dev-keys
ro.build.version.release=10
ro.build.version.security_patch=2022-09-05

The only changes are in '/defaults.prop':

'ro.debuggable=1' to 'ro.debuggable=0'
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Test keys are not inherently insecure, does it actually block you using the apps? I used to do privately signed builds but I didn't in the 18.1 releases.

Old versions of magisk can hide it.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Yes, it does.

Phone is marked "insecure" when apps do a check like this:

# ./rootbeerlib/src/main/java/com/scottyab/rootbeer/RootBeer.java, at line ~74:

/**
* Release-Keys and Test-Keys has to do with how the kernel is signed when it is compiled.
* Test-Keys means it was signed with a custom key generated by a third-party developer.
* @return true if signed with Test-keys
*/
public boolean detectTestKeys() {
String buildTags = android.os.Build.TAGS;

return buildTags != null && buildTags.contains("test-keys");
}

#

Source: https://github.com/scottyab/rootbeer
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That is a false positive. I would suggest you install an old version of magisk, I used to have to root my phone to stop my mobile banking from detecting root. 😂

I am not going to start signing builds at this late stage.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Yes, I know that it's a 'fake security check' 😅

But banking apps and so on....

OK!

What Magisk version you suggest?

Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
@danwood76

OK, "fake security check" bypassed editing '/default.prop' and '/system/build.prop' via ADB root.

No Magisk needed.

Now I'm able to use/test your rom and report back.

Many thanks to you, other developers and users.

Have a nice day.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Beta123MAX:
You said it.

Agree, keeping things simple for security updates is the way to go.

Not to mention that most banking and other "security" focused apps are a wonky mess. They're often build against frameworks without caring about compatibly and can break using LOS with every single update. I think, fighting against it on rom side won't actually work.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] _sui:
Thank you very much for this Rom and keeping my good old A5 alive. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] doubleviai:
Hello.

The update cannot be done via OTA update ? (It doesn't work for me).

The good way to get it is to reflash from recovery (but with risk of loss of data?)?

Thanks a lot
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No OTAs in my unofficial builds.

Just flash the update in TWRP (that is all the OTA would do anyway).

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Pierre49976:
I'm running this ROM on my A3 and it's getting slower and slower. Sometimes it becomes unusable.

What can I do to regain initial speed?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You are probably running low on ram, remove any unused apps.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] funkoot:
Hi there and thanks for a great rom. I was just wondering of there is a version with Microg already installed?

Cheers,

Dave
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Lineage.microg.org only has some old 17.1 versions
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] funkoot:
I know. I'm currently running the official lineage 17.1 15/4/2022 microg rom but would like to upgrade to 18.1 with microg.

Thanks

Dave
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Benjamin1989:
Hey Guys I have this ROM on my Galaxy S5 neo.

Everything is working fine except WLAN connection is lost when it's sleeping for some time.

Only restarting the device fixes that issue.

If you use it actively this never occurs.

Is there a solution for this problem?

Edit: I included a log file

Thx for helping me
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Vincent144:
Is it okay for the chinese A5108 variant?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] blumentopf75:
Lockscreen loop.

I have a a5xelte with this fantastic lineage 18 (RQ3A.211001.001).

Everything worked, until yesterday, when I dropped the phone into water for only a second (applause please).

All thing are still working except of the lockscreen:

When the phone is locked and ich switch it on, it take a little while after the touchkeys are on, the the lockscreen apears for 1/2 sec. then the screen goes to black again. After anothe 1/2 sec the lockscreen apears for 1/2 sec and so on. About 20 or 30 times.

Then the phone reboots to recovery (TRWP). I reboot to system and can unlock sim and phone.

When the phne now locks itself, I have the same lockscreen loop.

It doesnt matter, what kind of lock I use (PIN, wipe, wipe pattern)

When I switch off any locking of the phone (happily I can log in one time after reboot), I can use the phone without any issue.

Could this really be a problem from the water-drop?

It feels a bit, as the lockscreen would chrash and the phone tries to restart it again and again.

Or is there a way to change to anothe lockscreen-app, to find out if the original from lineage chrashes?

And waht is the name of the lockscreen-app. Maybe i should stop and reset it in the settings of the phone.

Thank you.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] blumentopf75:
Another idea is, that the fingerprint sensor is damaged because of the water.

I have four fingerprints configured, so maybe the lockscreen asks for the sensor and chrashes because of the damage.

This would eventually declare, why I can unlock on boot, because fingerprint-authentication is nor allowed at this point. So maybe the sensor is not activated on after-boot-login.

I also tried to delete the fingerprints, but this was not possible: when i tap on the bin the listentry becomes gray, but does not disappear. When I reenter the fingerprint-settings all four fingerprints are still in the list.

I also cant record a new fingerprint, because there are only four fingerprints allowed.

Is it possible that the sensor stores the fingerprints in itself, and so deleting from a damaged sensor ist not possible too?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] tomen94:
Hello,

do you mind sharing us how and what excatly you edited in these files?

thanks!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Edited parts attached below in `diff` format.

How to:

- in developer options, enable 'USB Debugging' and 'Rooted Debugging', then plug your phone in a pc usb port;

- in a terminal emulator, run 'adb root' and remount the filesystem in read-write mode:

adb root
adb shell mount -orw,remount /

- then do:

adb pull /default.prop
adb pull /system/build.prop

- in your hard disk you'll see two files: 'default.prop' and 'build.prop'.

Edit them and put back in your rom with:

adb push default.prop /
adb push build.prop /system/

- remount the filesystem in read-only mode and reboot your phone:

adb shell mount -oro,remount /
adb reboot
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] tomen94:
exemplary! Thank you @rik70
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
I have A310 device and install this ROM, thank you!

But on calling, the other people can hear our call because of the loudspeaker.

@danwood76

As I know I have to edit mixer_paths_0.xml, could help me find related values to DECREASE calling speaker?

Also, can I INCREASE music sound?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Just turn the volume down during a call. You get that effect with all phones if it is too loud.

To get louder music buy a speaker, the default volumes are as loud as stock. Any louder and you will get distortion and damage the phones speaker.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
I tried "volume down during a call" but it's loud and other people can hear our call.

Could you help me to edit mixer_paths_0.xml file please?!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Why are you using loud speaker mode of you don't want everyone to hear your conversation?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
No! I don't use speaker-mode during a call.

During a call in my device the lower volume is loud by my opinion.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] hedgehog37:
I have exactly the same behaviour after cloning my system to another A5. I doubt it's the damage from the water. I saw some people on the Internet with the same problem. Couldn't find a solution though. Now I am using it without a screenlock.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] blumentopf75:
Hello, and thank you.

The problem still persists. Nothing helped (put the phone in rice or put it on a radiator). So I think, the semsor is finally broken.

I so I switched off all locking features.

I also want to know, what will happen, if I reset the phone.

- Best case: it "forgets" that there are 4 fingerprints saved (in the sensor?) and doesn't ask for the sensor on lockscreen, because there are no fingerprints which it has to scan. So ich could lock the phone with pattern or PIN

- Worse case: reset of the fingerprint sensor fails and so I cant reset or I'm locked in a boot loop.

Changing the sensor is very complicated (I would have one from a screen broken phone), because one has to detach the screen. backcover and frame is not enough. So I will leave it unlocked. Its not worth it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Some slowdown and/or 'short hangs' while browsing Google Account.

Logcat attached.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 8y73:
Can someone please extract and post the APK of the keyboard from this LineageOS-version?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] RANSKY21:
STUCK IN LOGO
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] RANSKY21:
whats gapps ? micro or nano ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Pico 😁
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] maanteel:
I used to flash opengaaps nano - to have pico + including extra functionality which is not available from playstore. see https://github.com/opengapps/opengapps/wiki/Nano-Package

It's up to you. Micro has google things I don't use.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi and Happy New Year.

I have just uploaded a new build with the latest security patch.

Changes 10-01-2023:

Synced to latest LineageOS source (including January security patch)

Kind regards,

Danny

-- edit --

I have had to pull these builds as they are missing a few patches, new builds will be uploaded later
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Build date January 10 ? So the builds already have seen a week of heavy testing?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I've been running on my A5 which I have been lightly using. J7 testers have been using it for a week.

I have just spotted an issue with these builds which I am pulling and rebuilding now (missing some patches as they expired on gerrit and my auto script didn't pull them in, oops).

Regards,

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

I have just uploaded a new build.

Changes 18-01-2023:

Synced to latest LineageOS source (including January security patch)

Included patches missed in last build

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
This still holds for a3 2016 ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, gcam requires 64-bit and some extra sensors.

There are old versions of gcam that do work but they have less features than snap.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
No. You can use magisk and LSPosed and fakegapps
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Polarbear83:
Thanks for the information x3
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
How I can enable the signature spoofing? (magisk & microG-module installed)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Use LSPosed and fakeGApps from whew-inc
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] red_fork:
Does anybody have problems with localization accuracy after last update? Sometimes it take ages to acquire GPS signal. Also GPS signal is lost very often.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Dahita:
Thanks a million for this thread, much appreciate everyone's efforts
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hi, Dan. Sorry about the question, I can figure you're tired of it, but... Are you thinking on launching LineageOS 19 for this device??

Thanks a lot for all your great job.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
W

Why not 20?

https://xdaforums.com/t/unofficial-lineageos-20-0-android-13-for-a310-a510-and-a710-alpha.4524891/
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
I tried the LineageOS 19 from that developer and it was full of bugs, unfortunately. One of the most important was the microphone crash during calls... It was not usable as dalily driver...

have you tested that LineageOS 20??
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
I use 20.0 on 3.x kernel only for playing around. Daily driver quality is 17.1/18.1on 3.x or 19/20 on 4.x (other phones)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
Lineage 17.1 and 18.1 have a problem with the stability of the USB connection to the home computer and to the car computer (Android Auto), intermittent disconnection... USB file transfer... even a clean system. SM-A310F
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mtek89:
I switched to this ROM after using the above linked LOS 20 as a daily driver for a few months.

This downgrade is already a huge QOL improvement, and I'm happy I switched back.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] X-Ray 7:
I just signed up to say thank you, Dan! ❤️

Thank you for keeping my 8-year-old Galaxy S5 Neo up to date in such a way that buying a new phone still seems unnecessary to me after all these years! It's almost incredible! 🙂

I recently tried several other unofficial LineageOS releases, 17.1 as well as 18.1, but they were all slow as hell and had very frequent extreme lags (like: phone completely unresponsive for a minute or longer). With your version, everything is running smoothly, and I haven't run into any errors so far. I'm so happy!

That's why I went to Dan's donation page and donated a few Pounds, and I kindly ask anyone who uses his releases to do the same!

Show this man some love ❤️

and send him your money! 💵
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I have just uploaded a new build.

Changes 09-04-2023:

Synced to latest LineageOS source (including March security patch)

Kind regards,

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

Thank you for the support and nice words.

Hope your phone continues to live on!

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
That no one has problems with USB "File Transfer"? Android Auto?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Check your usb lead and that you have a clean port.

Mtp file transfer has always been a bit rubbish on Android. Even on stock.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
stock SM-A310F_SER_A310FXXS5CTJ1 everything works fine. Tried different computers and different cables. LineageOS 17.1 and LineageOS 18.1 - the connection freezes. freezes not immediately, after some time, after several copied and deleted files.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It's not perfect. Invalid characters can crash the connection. I did some debugging on it a long time ago, the error handling basically crashes the kernel driver and doesn't report it to the OS gracefully. I don't use mtp on my stock s9 because it sucks.

I might take another look at it, bit I am seriously lacking in free time at the moment.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] JMek:
Hello everyone. I wanted to ask if only to me happens that if i install opengapps-arm-11-pico it tells me "incompatible android rom" with error code: 20?

Tried every gapps for version 11 arm and even arm64 in the doubt. Nothing changes.

Also the latest Magisk (26 and 26.1) causes me Bootloops. So i guess i'll stick with the older one that works for me, which is Magisk v23.

But im curious to know, if others have these problems or it is just me. :)

#EDIT#

After many retries, it actually installed me the opengapps-arm-11 successfully.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kirbyz09:
Hi! I would like to support the project. I found this in a forum https://archive.org/details/lineageos171-20220217 It is a compilation of lineage versions, there is one of A5XELTE LINEAGE lineage-17.1-20220214-nightly-a5xelte-signed.zip ,which fixes some errors such as SD card reading at the start of the device and saving photos to the SD card, I hope it helps. (my english is not good, use google translate) (>~<)