yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
where can i find the userdebug version? Willing to help you find the cause...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
All LineageOS builds are userdebug, I can't remember the exact error but you can trigger an mtp crash by copying a file with an apostrophe in the name. It should give an error that it cannot transfer the file but instead it locks up.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
Freeze regardless of the file name. I can copy the same file multiple times, 3-5 times, then freeze.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
Checked on A510, same problem...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Is this copying to internal storage or SD?

Do you have many files on there? Windows scans drives for files which swamps mtp, usually it recovers if you wait (same behaviour as stock).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Gekkon76:
copying to internal storage. copying and deleting the same file multiple times...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] funkoot:
Is there a guide for installing microg with signature spoofing on this ROM? I have tried using a few guides online but none have worked.

Thanks,

Dave
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I think you can install microg with a magisk module.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
What

What phone are we talking about? For some there are builds with baked in signature spoofing. You can always use magisk and LSPosed and whew-inc fakegapps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] funkoot:
Cheers Danny. I have installed microg via magisk but can't enable signature spoofing.

Best,

Dave
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] funkoot:
Hi Kurtn. Sorry but I forgot to mention that it's a Galaxy A3 2016 (a3xelte). I have already tried LSposed and Whew-inc fakegapps as you suggested in an earlier post (using latest Magisk) on this thread but couldn't enable signature spoofing. Do you have a step by step guide.

Any help is much appreciated.

Regards,

David
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Do you see the LSPosed app? Is zygisk enabled in magisk settings? Is fakegapps visible in LSPosed? How do you check signature spoofing?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] funkoot:
Cheers Kurtn, all working now. It was my fault. I was using the Riru version of LSPosed which was incompatible with Magisk 26.1. I'll definately do more research next time.

Thanks for your help, as always :)

David
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
Hi, all!

Got the latest unofficial LOS 18.1 on my a5xelte. Tried to build it myself. I extracted proprietary blobs from the phone and after running breakfast I got this:

hardware/samsung_slsi/exynos7580/exynos7580.mk:28: error: _nic.PRODUCTS.[[device/samsung/a5xelte/lineage_a5xelte.mk]]: "vendor/samsung/universal7580-common/universal7580-common-vendor.mk" does not exist.

I tried building 17.1 and 18.1 branches, tried extracting blobs from the device and from the .zip (block-based OTA) and the result was the same. I was following LOS wiki to the letter.

Then I tried adding TheMuppets repo to .repo/local_manifests/roomservice.xml. Progress, breakfast worked. Then brunch gave me this:

ninja failed with: exit status 1
#### failed to build some targets (48 seconds) ####

I synced the repos yet again and this time I tried extracting blobs from the phone while keeping TheMuppets repo in the roomservice.xml. Ninja failed, again.

Any ideas?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, you need to the universal7580-common blobs as well. Muppets repo is the easiest way.

There is no easy way to add that into the wiki so it was never done.

You may need to clobber your build and restart once you have the Muppets synced correctly.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
I added this to .repo/local_manifests/roomservice.xml:

<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" />

I thought it would pull both a5xelte-specific blobs as well as 7580-common blobs, or am I wrong?

So, you're saying I should add both TheMuppets repo and extract blobs from the phone already running LOS and do the same thing over and over until it finally succeeds?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Just sync the Muppets, don't extract the blobs because that can break the makefiles if it fails.

Post the actual build failure with the Muppets, your error doesn't actually show any meaningful info.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
I attached both LOS 17.1 and 18.1 brunch results.

Edit: for whatever, I don't see my .txt files uploaded. Could I send them to you in a message?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] chris@xda:
My shopping list so far for the SM-A510F:

twrp-3.7.0_9-0-a5xelte

a5xelte ROM (latest)

open_gapps-arm-11.0-pico-20220215.zip (32bit)

I'm not sure how to install TWRP on the SM-A510F. Can someone who knows confirm, please?

Enabling Developer Options by tapping the built and then allow USB debugging and OEM unlock. That's it, right?

For Windows I'd flash with ODIN in the AP slot with Option "Auto reboot" unchecked.

If ODIN reports PASS after flashing, I reboot to recovery with POWER + HOME + VOL DOWN until screen goes blank. While staying on POWER + HOME button, change to VOL UP and TWRP recovery should appear.

EDIT: I had to use TWRP 3.6
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] tuthanika:
hope u support A7 2016 SM-A7100 snapdragon version

Code : A7100 a7xltechn a7xltezh (TGY)

Link fw original: https://samfw.com/firmware/SM-A7100
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
None in https://stats.lineageos.org/
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] tuthanika:
it's just a version use snapdragon as an alternative to exynos.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
They are not compatible
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] badms:
Hello. im trying to connect dualshock 4 via bluetooth in a A5 2016 without success, is there a way to connect it via bluetooth in this ROM ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] shaskhin1365:
hii ... sometimes i check my phone and it has no registered network , and i have to restart to phone to fix that..does anyone has the same problem?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lamandopaijo:
for dual sim the second sim is not allowed, but the imei number of the second sim is detected

sm-a310f
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
I finally managed to build LOS 18.1 for my a5xelte. So far, so good. However, I tried to sign my build and got the file named lineage_a5xelte-ota-en.eindroid.zip, but when I installed it, Trust still notified me it's using public keys. LOS wiki is a bit confusing on what referrs to which version of LOS. Could somebody here give instructions how to sign LOS 18.1 builds?

EDIT:

After I run:

croot
sign_target_files_apks -o -d ~/.android-certs \
$OUT/obj/PACKAGING/target_files_intermediates/*-target_files-*.zip \
signed-target_files.zip

I get:

2023-07-17 21:42:40 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read VENDOR/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read PRODUCT/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read ODM/etc/build.prop
2023-07-17 21:42:40 - common.py - WARNING : Failed to read ODM/build.prop
done.

EDIT 2:

Turns out I got a build named signed-ota_update.zip in ~/android/lineage. I flashed it in TWRP without wiping my previous self-build, unsigned install. Everything works ok and Trust is no longer notifying me about using public keys. So, I guess that's it.

I think LOS wiki article Signing Builds should explain the location and name of the signed build under section Generating the install package. It's not intuitive for newbies and it took me days of searching the web to find out about it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

New version with updated security patches just uploaded:

Changes 15-07-2023:

Synced to latest LineageOS source (including July security patch)

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] badms:
this build supports dualshock 4 via bluetooth connection? last build i tried didn't have support
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I have no idea.

What errors do you get when you try to pair?

The kernel might be too old (native ds4 support is quite recent).

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] badms:
I've tried every LOS from 17 to 19, the BT recognizes the DS4 in the BT devices as Wirelles Controller, but when i try to connect it never connects, no error, it just timeout. However it connects via OTG. I heard something about kernel outdated. Is there a way to update the kernel with a kernel that has the ds4 driver?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Updating the complete kernel is nearly impossible. Backporting individual features is still hard work but someone with more time than our Danny could maybe do it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There will probably be errors in the logcat or kmesg.

Try to pair it and then dump a crash log from the developer settings and send it to me (upload to Google drive and pm a link is easiest).

I might be able to help.

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
Hi, is this rom good for my SM-A510F? Is the IMS service problem annoying as an alert? Excuse my english
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
That's for you. No VoLTE is a problem if your network provider doesn't supports neither 2G nor 3G calls.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
So the 4g data connection is not working?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
4G works for mobile data. Not for calls or sms on any Samsung with lineageOS or similar.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Double post
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
How long can the first power up take after flashing?if i try to install only the os without the gapps it turns on right away. instead if I put the gapps loads to infinity. Maybe I'm wrong to download the gapps. What are the right ones for this system? the arms or ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Read OP
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
? OP. Sorry
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
OOriginal post. Just checked: no info. Better read wiki.lineageOS.org it's arm android 11. maybe those

Redirecting…
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
What model of gapps should i install? which one is cheaper? i had downloaded the arm stock but it loaded for more than 2 hours with no results
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Never ever install openGApps stock. Use nano or pico. Better use mindthegappps
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
Please help me. If I try to install the gapps you said it gives me error 1 and won't let me install them. opensgapps doesn't work
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
I couldn't start the rom with the gapps you indicated. I was successful with nikgapps but as soon as I restart the phone it gives me the frp lock. how can i fix which gapps are working? the minds don't even go
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
Hi I have a problem in practice if I install the lineage 17.1 the phone works with the mini gapps but it doesn't let me use the Google family link app (because I have to give the phone to my daughter and I need to use it) if instead I try to flash the 18.1 with all the gapps I've tried the phone works even the app I need but as soon as I reboot it goes into custom binary frp. How can I solve this? Please help me
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] vxqwxik:
You downloaded the version for ARM, but you need for ARM64.

The file has the name MindThegaps-11.0-Arm64-20220217_100228.zip

But on the version of the TWRP for the A310F(a3xelte), MindTheGapps will also not work, so you will need to take these steps in terminal:

unzip -d MindTheGapps-11.0.0-arm64-20220217_100228 MindTheGapps-11.0.0-arm64-20220217_100228.zip
sed 's#SYSTEM_BLOCK=$(find_block "system")#SYSTEM_BLOCK=/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM#g' -i MindTheGapps-11.0.0-arm64-20220217_100228/META-INF/com/google/android/update-binary
(cd MindTheGapps-11.0.0-arm64-20220217_100228 && zip -u ../MindTheGapps-11.0.0-arm64-20220217_100228.zip META-INF/com/google/android/update-binary)

Now you can install.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Yes, it is. No annoying alerts related to IMS service.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] solidus69:
I had to remove it and put the stock because it gives me frp problems even if I had removed the account and used the app to bypass
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rik70:
Removed on stock rom before flushing?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] elijun:
I have the exact same problem of FRP lock on my A5 2016 with Lineage OS + Family Link child account. I've tried different approach but with no success :

LineageOS 17.1 + OpenGApp ARM 10 -> KO

LineageOS 17.1 + OpenGApp ARM64 10 -> KO

LineageOS 18.1 (from this thread) + MindTheGapps ARM64 (zip updated as mentioned by @vxqwxik before) -> KO

Everytime it works like a charm during install, I always make a full wipe of data/system/cache ...etc during flash.

But in the end, it fails on the first reboot with this error message : Custom binary blocked by FRP Lock

Note : LineageOS works perfectly fine with a normal google account. This problem occurs only when your try to activate a child account with family link on the phone....

After that the only solution is to get back to a stock firmware on android 7. (And the Family Link Child account works fine with it, but it's so f*** old .... )
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] vxqwxik:
Hi. A similar problem is described here(click), and apparently lies in the "Family Link" itself. The GAPPS installation on a device with an unlocked OEM does not lead to lock.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] abduullah:
where is the link
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
In 1st post

38.06 GB folder on MEGA

82 files and 6 subfolders

mega.nz
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jpmhh:
Hi

this is not for the Galaxy A3 2017 (SM-A320FL). Am I right?

I can't find an actual Lineage version for my phone. Al posts

refer only to sm310.

I've installed Lineage 17 long ago. But it works not very good. Kamera is freezing sometimes and needs a reboot. Linage Updater is also not working. It loads an updates but then fails to install it.

Thank you
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
About a couple of months after I started using my own signed builds, my SM-A510F started having display problems, but only while in OS, but not in TWRP or ODIN. It would go black for long periods of time, and when I press power or home button it would just flicker once real fast and stay black. It would still respond to the touch, I could see it using scrcpy to mirror the screen on laptop. Sometimes the display would start working again, and then go black again.

I thought my builds were the problem since it happened only in OS, so I tried your unofficial build, the same happens. I used ODIN to flash the 4 files for stock ROM, still the same problem.

Anything else I could try? It looks like a software issue since it doesn't happen in ODIN or TWRP.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
Probably too late but I could prevent FRP lock in Lineage OS 18.1 in combination with FamilyLink on the A3 2016 by flashing a file Danwood once posted here https://xdaforums.com/t/official-a3xelte-sm-a310f-lineage-os-17-1-for-a3-2016.4036121/post-86732369

- thebinf
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
When I try to repo init, I get a warning:

warning: Changing --git-lfs settings will only affect new project checkouts.
Existing projects will require manual updates.

When I try repo sync, I get a lot of errors like this one:

error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 7763 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output
error: Cannot fetch LineageOS/android_packages_apps_Seedvault from https://github.com/LineageOS/android_packages_apps_Seedvault

This particular error is just one example, I can't fetch anything. Google says I need a stable internet connection, which I tried in 3 different apartments with an ethernet cable.

Per instructions on LOS wiki build page, I tried repo sync j -1. Still have the same issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Polarbear83:
Does build for a7xelte support signature spoofing?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Yes, i think so.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrhamed:
Hi, I have Samsung A3 device.

The in-call-volume is very loud. I couldn't manage to decrease it with some changes I've made in the mixer_path_0.xml file.

Could you help me please. I attached the device's mixer_path file too.

Thank you!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
Hi all,

I am a noob looking for help with the istallation of Lineage @ a Samsung Galaxy A3 (2016) aka SM-310F aka a3xelte. (Or maybe a hint, why it doesn't start.)

My parents in law had two of these devices and were unable to install recent apps. They wanted to get new mobiles but I wanted to give Lineage a try.

After one night (aprox. 8 hours), I succeeded on one device. It works like a charm now and made me very proud! :cool: But the 2nd one does not. 😞

What confuses me even more: I thought they were identical - disregarding the colour ;o)

The phone went through the same steps as did the phone's "twin" -which is working now- except the fact that the 2nd one is not working... I softbricked it and had to take it home, to dig deeper...

Here is what I did:

I managed to flash (unofficial) Lineage 18.1 ...

(https://mega.nz/folder/OJ4GEAhC#Uw6CQgD57KD0pxZKwI6GfQ/file/CIBmlbiT)

coming from danwood76 (great work, thx a lot!):

https://xdaforums.com/t/unofficial-lineageos-18-1-for-a310-a510-and-a710.4321901/

with TWRP 3.7. flashed via Odin 3.14.4 (Heimdall was recommended in the Lineagewiki

https://wiki.lineageos.org/devices/a3xelte/install/#preparing-for-installation but it didn't work; I ran zadig2.4 but it showed a fail: the driver already existed.)

...resulting in an endless (I waited over an hour) starting-lineage-sign (that bowed green line with a bubble from right to left).

As I assumed that the problem might come from the recovery, I tried different TWRP-versions afterwards: started with twrp-3.7.0_9-0-a3xelte, switched to older versions (twrp-3.4.0-0-a3xelte followed by twrp-3.2.1-0-a3xelte). Same outcome. (I always wiped cache, system and data before I went into adb-mode and adb-sideloaded the lineage.zip. That process always succeeded but lineage never properly started after the reboot)

Then I tried (unofficial)LineageOS 17.1 (https://xdaforums.com/t/official-a3xelte-sm-a310f-lineage-os-17-1-for-a3-2016.4036121/) with all the above TWRPs. (same result)

Then i switched to Lineage recovery for 17.1 and adb-sideloaded (unofficial)lineageOS17.1 -> same result.

(I couldn't find the official LOS17.1, there seems to be a deadlink) [edit: I just found the archive, but didn't try it yet.]

All the time the phone could and can boot into recovery and download-mode.

As I am running out of ideas, I signed up here for the very first time. Does anybody has any suggestions for me? I'd appreciate it a lot!

Hopefully I didn't miss any relevant info? Ah: neither Gapps nor microG or anything similar, aurora-store suffices my needs.

Thanks in advance for your time and knowledge! All ideas are welcome.

Bo

PS: yesterday I did a factory reset and tried Lineage 16.0. Didn't work neither.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
I would start from scratch. Let odin install the recommended Samsung firmware.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
thanks for the hint! 🙏 I'll go for it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
🤔 what did I miss?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
Hmm, I tried my best:

at https://firmwarefile.com/samsung-sm-a310f there were three different versions, I tried them all - but all failed. More suggestions?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
sry to have bothered you, I found and read https://xdaforums.com/t/tutorial-ho...ts-functions-explained-noob-friendly.4540331/

then I downloaded the correct version for my csc at https://samfw.com/firmware/SM-A310F and am flashing it now.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
It worked out: I am back at stock ROM.

I'll call it a day for now. And will try to flash Lineage tomorrow. Thanks again for the advice.

Do you have any Idea what might have gone wrong at my 1st attempt to flash Lineage? (So I hopefully don't have to repeat my mistake...)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lineage for a3xelte:
Hmm, no success. :(

At Android 7 I enabled USB-Debugging, flashed TWRP 3.4, rebooted into recovery to wipe data, started adb sideload and loaded the unofficial Lineage18.1. After the reboot I am back at where I was in the 1st place: Lineage does not start, showing nothing but it's starting-logo.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
Hi!

Is there any point in building new LOS 18.1 builds since the last security patch was in February 2024?

Is there any way to update the default webview without building the entire ROM? Could I compile the apk and sideload to update?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
There are security patches in review.lineageOS.org they just don't get merged. So you have to cherry-pick before building.

I usually don't update default webview, but make system accept mulch webview - no idea how to get that on A310 . But if you build, just include that.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Eindroid_a5xelte:
How do I cherry-pick stuff?

I tried replacing webview.apk in /system/product/app/webview with Mulch webview using ADB, just like I used to do it with Bromite, but it didn't work with Mulch.

Then I tried adding Mulch signature to config_webview_packages.xml, but that didn't work either.

Patches/Common/config_webview_packages.xml · dc853bfdaecc73a273de252cf555c9a3b6a38864 · DivestOS Mobile / DivestOS-Build · GitLab

Everything needed to build DivestOS, a more private and more secure aftermarket mobile operating system. https://divestos.org/index.php?page=build

gitlab.com