yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] freeman94:
I did download open gapps arm64 10.0-nano and it show me that there is wrong device architecture with ERROR: 64

then I try the normal ARM verison and it did install.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, we can only use 32bit on this device.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] chertVdetali:
Hi,

yes, it was a PEBCAK. Led by intuition, I didn't expect the device nodes to be in a subdirectory. And hey, with "upgrade" I didn't mean an in-place upgrade., app data and system was wiped.

Thanks for including the ext4 card mounting in the last release, it seems to work now.

Anyway, I had to redo the whole thing since I f*ed up app data while restoring my apps (Titanium no good anymore). So I can report a few bugs now.

Most are probably not originating from your A3 port, just upstream issues with LOS17. Worth reporting directly?

a) when the initial setup is finished, it reproducibly wipes WiFi credentials which were previously entered

b) the first run of the setup wizard is always troublesome, runs into a timeout on "Looking for upgrades"

c) after configuring Google account, data synchronization was not working at all. Made me crazy, no obvios explanation in logcat. A plain reboot solved it, though.

d) LOS own Calendar app is broken. Didn't display data originally, new entries are not possible, looks like being read-only. After installing the Google Calender, sync start to work. But still no entry possible in LOS Calender.

e) Localization behaves weirdly. On the first glance, it works, but then random applications show untranslated strings, for example Gmaps in their address hints.

f) the brightness control by swiping on the status bar is not working properly (I did enable it, of course). When Auto-Brightness is on, it does not react at all. With AB off, brightness jumps like crazy when you swipe it. Seems to be impossible to set it to less than half.

g) Threema messenger doesn't receive updates in Standby. Might be an issue with the new permissions. To be investigated ASAP.

Anyway, apart from those glitches, it seems to be good enough for daily use. Thank you!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I have never seen any of these and have installed OpenGapps many times during testing. Most recently with fresh gapps from a couple of days ago without issue.

I think that is how the calendar app is supposed to work, it is read only.

Anyway these are LineageOS things, not device specific.

That doesn't seem to work at all well, again that is LOS thing and not device specific.

Sounds like an app issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], thanks for the update. Since the start of this unofficial 17.1 for our device, dirty flashing needs to be followed right away by flashing gapps again otherwise, it won't boot.

Except for los Calendar that fc (I use Google Calendar), I don't have the other issues brought out by some users, like automatic brightness that adapts live for me.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You shouldn't need to flash gapps any more. That issue was fixed a couple of releases ago.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
How's that? I faced that issue with your latest update 20200312 just this morning (took me some tries to download the zip from Meganz)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You may need to do a clean flash to fix the addon scripts, not entirely sure. The updates work fine for me though (using latest opengapps).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
OK, I downloaded the latest opengapps and I'll test on next update, thanks.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Ok, these are the screenshots of the logcat. I don't know if it's the correct information, because I don't know how to read the logcat. I wish it is enough to know the problem. Thanks!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You need to start recording a logcat, then simulate/activate the crash, and then send the entire log file to me.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] xrhstaras44:
Very nice rom thank you!Can we ha e ressurection remix android 10?Awesome work
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Hey!! I send you the Logcat with the Android Auto issue! It happened at 16:44 hours, but maybe the problem is in 16:46. I hope its useful. Thanks a lot!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
Hi Dan. Just a question. When the build start to be oficial? For Samsung, the S4 Started today the nightly builds. Thanks for your amazing job, i use your ROM daily since your first upload and its works lovely.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Thanks for the log.

It looks like a permissions issue in either LOS or gapps, the error is:

java.lang.SecurityException: No access to content://lineagesettings/system/force_show_navbar: Neither user 10158 nor current process has android.permission.INTERACT_ACROSS_USERS_FULL.

It happens when it tries to force the navbar on, so you might try enabling the on screen navbar and see if it helps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] omarawais:
Sir please make miui rom for sm a310f
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Somebody already asked for RR. Do you really think he will do MIUI now?! Learn to build and make this ROM by yourself for the A3 (if MIUI source is even available).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] omarawais:
RR

Sir Which Version OF RR ou are making and is it for A310f ????

I used Lineage 17.1

it make my mobile internet speed slow

:)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Seems like you understood my message correctly :laugh:

I can't confirm the issue with the slow internet though. It's pretty sure the fault of your mobile network provider.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Thank you very much, Dan, but I tried to connect Android Auto in my car with the screen navigation bar and the problem continues. Any other idea to try to fix it?? Thanks!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It could be an issue with opengapps. The problem with that permission is that it probably needs the service to be a system app.

Did it work on Los 16?

I can't debug the issue as I don't have an Android auto head unit. I might buy one off eBay, my wife's car could do with an upgrade :)

--edit--

There is a bug report with some people having similar issues:

https://github.com/opengapps/opengapps/issues/742
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Thanks! I used Android Auto in your unofficial LOS 16, and it worked fine, but I used MindTheGapps, no Gapps. Maybe there is the problem.

I hope it will be a MindTheGapps version to use in LOS 17, and I can taste it.

Thanks a lot!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I found an Android auto emulator for Linux (openauto) which I can simulate the crash on. It works fine with my stock S9 but I get the exact crash you reported on my A510F running Los 17.

I will add it to my list of issues to look at, I am really busy right now so I probably won't get a chance to dig into it any time soon.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Ok, we will wait, and thanks a lot, Dan!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Honey7t:
This rom is best for SM-A310f

Good Work

Best of luck for the future
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

New release just uploaded.

We have now switched to the new BSP, some users on the J7 have reported better UI fluidity with this change. Hopefully we will see the same on our devices.

I have now also added a fodler to my mega drive with the latest LineageOS recovery images (flashable in both TWRP and LOS recovery), I would recommend the LOS recovery as the are issues with TWRP breaking updates that some users have reported.

Flashable recoveries can be downloaded here:

https://mega.nz/folder/OEIknYIR#AIY-GQ4zeFcG9aUKk2rwrg

Changes in the 12/04/2020 release:
[INDENT]- Disable rounded corner animations (thanks @dariotr)
- Cleanup overlays (thanks @dariotr)
- Switched to new BSP to solve licensing issues (thanks @stricted)
- Synced to latest LOS (including April security patch)
- Uploaded LineageOS recovery
[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pluescho:
Error in latest release

Device isn't booting after installing latest release.

Tried with both twrp and your los recovery. Long boot loop will end up in rebooting.

Be careful.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
Hi all, same behavior here... will try to make a clean install of the latest build....

Los recovery... first time i have heard about that tools on our SM A310, i've flashed it... but don't know how to use it.

If someone can give me a tutorial link... it will help . TY

I confirm that doing a clean install, with TWRP is working... if it can help
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pluescho:
You can't install twrp anymore from los recovery. Older release can be installed after failed signature check warning.

Nevertheless device won't boot and is useless by now....

---------- Post added at 10:44 PM ---------- Previous post was at 10:04 PM ----------

Full swipe is required to go :(
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Your issue is probably caused by the TWRP SAR bug I mentioned in my post.

The way to fix is to wipe system partition and cache and then flash ROM + Gapps (+ Magisk).

Stick with Los recovery and you won't see that bug in future updates.

I tested both recovery installers and they work just fine for me. If the signature verification fails just click install anyway. I may have just uploaded the unsigned version accidentally.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
For me all work well. I did a clean install after flash Los recovery.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], I was happy with your latest build but I'm nevertheless pleased to take this update.

After installing the los recovery as you avised, I don't see the option to make a backup of the fresh system. Which means that if I try some mods and if anything goes wrong, I'd have to go back through the whole process of flashing. Nevermind, just asking.

FYI, the installation of the update went smoothly and the system runs fine so far, thanks and best regards.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Thank you for updating and for releasing the LOS recovery!

An issue concerning LOS recovery: At least on A3 decryption does not work, so /data access is not possible. Does LOS recovery even support decryption? Or is it not correctly setup for A3?

My device is encrypted and I use the SD-card as internal storage. On TWRP everything is recognized correctly.

Output:

E:[libfs_mgr]Failed to mount /data: Invalid argument
E: emulated failed to mount /dev/block/platform/13540000.dwmmc0/by-name/USERDATA on /mnt/staging/emulated: Invalid argument
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, LOS doesn't support decryption (or nandroid style backup [MENTION=6990309]mohand06[/MENTION]).

I guess I will have a look at why TWRP fails to update correctly today.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Hi [MENTION=6707196]danwood76[/MENTION], thanks for confirming that we can't do a nandroid backup on Los recovery. How to revert to twrp? Flashing image in Los recovery?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I created a flashable zip for TWRP in the recoveries folder. You can ADB sideload, use a USB stick and an OTA cable, or even a space micro SD care if you cannot access your internal storage/SD.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Is this TWRP already patched for the updates? Or just as an easy possibility for reverting?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It is just official TWRP.

I haven't even started to look in to the TWRP issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] laachir123:
I hava samsung a310f with latest firmware .when i flash lineage in twrp it only reboots to lineage logo for aboit 20 min and then reboot to twrp

i tried all kind of wiping but no luck

help plz

when i tried with los recovery i got this error after autoreboot to recovey

E:Failed to bind mount /mnt/staging/emulated/0/media/0 to /storage/emulated/0: No such file or directory
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dariotr:
Are your touchkeys working on other ROMs?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] laachir123:
yes with the stock rom everything is working fine
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like you didn't format data before trying to install.

When first installing you need to wipe System and Cache and format data/

You will loose all of your internal storage data so make sure you backup.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] laachir123:
I did a full wipe

system data cache dalvik cache internal ...

before installing
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Trebuchet crash

Hi everyone,

I've just flashed system + gapps + magisk (all latest and in one run; after formatting system and cache partition) and it all resulted in Trebuchet crashing right after boot.

I've dumped the log (since boot) -- at 19:50:17 I pressed the home button (which resulted in Trebuchet crashing yet again) https://gist.githubusercontent.com/...ce6f7ac99467/Trebuchet%20crash%20since%20boot

PS I've now tried to restore my complete backup and got stuck at bootloop (why?) so I've just done a clean flash.

PPS All this was actually worth it as the pixel launcher finally works :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Looks like you had corrupted gapps install in that log. Lots of GMS crashes.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] laachir123:
here the logs and

Thanks for your help

last_kmsg:

https://drive.google.com/file/d/1KGh_KkIOVYlnnWOAQifG85ROvjxlLhXi/view?usp=drivesdk

dmesg.log:

https://drive.google.com/file/d/1Rn0KHMPwLHUf2lUgl5WszSiXxZpvwWT1/view?usp=drivesdk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] apokit:
Does viber works with this rom?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] chertVdetali:
Nope, I have used CM/LOS calender for years, the editor was quite good.

Why am I actually here: a quick report from the installation of the April build last week. So, installed this over the March build. And on restart, it was stuck in the boot animation for about 5 minutes. And then restarted into Recovery. Tried rebooting a couple of times, same game. So I attempted to restore the TWRP backup made before. And nope, the same thing happened again, this time no longer self-rebooting and stuck for about 10 minutes. This was the moment when I started panicking, and had to look up the key combo to reset the phone forcibly for the first time in years. So, rebooted, tried to restore an even older backup, from begin of March, and same result. The restore was not dirty, TWRP did wipe partitions according to the logs on each restore. And the last straw was a wild guess, so I restored the latest backup, then wiped /system, reinstalled your April image, downloaded latest OpenGapps and immediately side-loaded them. And rebooted, without installing Magisk. And then it suddenly worked. On the next recovery run, installed latest Magisk, and that also worked.

And now I am wondering what the heck was going on and why the restore of a good state didn't work. Maybe some bug in Gapps which has persisted since February could explain it, OTOH the restore runs did also restore the caches, so why was it failing then? Really confusing.

Regarding my previous (audio) problems with the ROM, it got partly better, but not fully. Now echo cancellation with speaker works "mostly" with messenger apps, sometimes still failing. The microphone volume on analogue headset is between weak and very bad. But not so for GSM calls, there it's just normal, and BT headsets are also fine.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Los calandar is AOSP and Google removed even more features. There is talk of switching to a 3rd party app.

TWRP updates and backups are broken, which you have discovered. Updates work just fine with lineageos recovery but there is no backup function.

To fix a broken update, wipe system and cache and then install ROM Gapps and Magisk.

I do have a working build of TWRP with a hack to fix restoring backups but I haven't had time to properly test it.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mehranshabir:
Updates

why it's not update regularly.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
Because there is no right to, you did not pay for updates, did't you?. And because it is running very good, thank you, danwood76 for your work on this old device!

PS: Why don't you ask this to Samsung?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It is stable so once a month should be good enough for now. I am extremely busy with other things at the moment.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrvanes:
Well, in that case I have a question. I'm running 16.0 and was waiting for an "official" release so I can flash dirty? Is there an upgrade path to this ROM without formatting data or by restoring recovery data backup?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sure.

In the downloads folder there is a migration zip. Flash that, ROM, latest OpenGapps, latest Magisk.

Make a backup first just in case something goes wrong.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrvanes:
Thank you very much! All went well and my A3 is now proudly humming 17.1, will make a small donation later today! :)

What about 17.1 updates? Only the rom, or do I need to reflash OpenGapps and Magisk again? I'm not quite sure what gets replaced under the hood on a single rom install?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Usually you just flash the update. There have been issues with TWRP not running the add-on scripts correctly and breaking gapps/Magisk causing a bootloop, but you can recover from that issue quite easily.

Before I release the next update I intend to fully test the updates and TWRP and possibly release a custom version of necessary.

You can also install the lineage recovery (link in first post) where the updates always succeed but it doesn't offer some of the extra twrp features like backup.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] [GER]Roxxor:
Is there actually still an issue blocking the official 17.1 release? LOS Recovery generally works, as far as I can see everything else works and is stable. I'm actually quite happy we are still on LOS 16 official, as a very important App for me doesn't work with all features on Android 10 (https://github.com/PeterCxy/Shelter). But still just interested what still remains to be resolved.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I don't think so. I have been extremely busy lately. I might ask [MENTION=8184192]Stricted[/MENTION] if he has any objections and then push the devices to official.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrvanes:
This may have been raised before but I can't seem to be able to store photo's on SD using the built-in camera app, is that a result of Android being more strict on where apps can write on SD i.e. in a folder named after their application id? Is that even true for the built-in camera?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
In Q the is even more app isolation. Someone needs to write a storage access framework based driver, then we could write to dcim again.

If you store internal it is fine.

Not sure why the media scanner doesn't allow the images to be scanned in the app folder. It's on my list of things to debug. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

New update just uploaded.

Notable changes/fixes:

- USB sounds now work when you plug/unplug a cable

- Ringtone no longer plays through speaker when a headset is connected

- Probably lots more :)

My tests with my new TWRP build show that updates appear to work fine as well as backup restore.

Full changelog:

Changes in the LineageOS 13/05/2020 release:
[INDENT]- Fixed ringtone routing when headset is plugged in (thanks @stricted)
- Synced to latest LOS (including May security patch)
[/INDENT]Changes in the LineageOS Recovery 13/05/2020 release:
[INDENT]- Synced to latest source
- Added my signing keys to the zip verification function
[/INDENT]Changes in the twrp-a3xelte-3.3.1-0-danwood76 release:
[INDENT]- Synced to latest TWRP 8.1 source
- Added selinux labelling to system_root to fix broken backup restore
[/INDENT]

Kind regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
Hello Danny, there's maybe a problem with this update. Did a dirty flash and trebuchet freezes in black screen, did a clean install with recent nano opengapps and start in boot loop. Did a clean install of the 12/04 update with the most recent opengapps nano and then aply this update and have no sound. I made a new clean install of the 12/04 build with most recent opengapps nano and woks fine. Another thing, in your mega, the latest build is 13/05 and no 15/05. Thank's
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mrvanes:
Where do I find your "new TWRP"? The links in the topic starter seem to point to the official TWRP page?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It's in the "flashable recoveries" folder.

Regards,

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

It works just fine on my test phone. Not sure what is going on.

When you say "no sound" is that through speaker/headset/Bluetooth? More information is required in a real bug report along with logcat/kernel log.

Regards,

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

Install:

First: twrp-a3xelte-3.3.1-0-danwood76-signed.zip = okay

Second: lineage-17.1-20200513-UNOFFICIAL-signed-a3xelte.zip = okay

Clean install (just LOS, no gapps)

Boot = okay

LOS =

- Black screen (5ms wallpaper), black screen.

- i can press the 'power button' and see the shutdown menu.

But thats it :( The screen is on, but i cant see anyting.

Kind regards from germany
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pluescho:
Flashed new LOS recovery, than new release 13/05. Results in boot loop. Flashing back to 12/04 doen't help. :(
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I will test it out again in the morning.

Regards,

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

Quick update that fixes the boot crash issue.

Changes in the LineageOS 16/05/2020 release:
[INDENT]-Fixed mediaserver shim to solve boot crash introduced by last update
- Synced to latest LOS[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] pluescho:
Thanks a lot. Did a full wipe, flashed 16/05 with your latest los recovery and latest nano gapps. looking good!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] a32016fan:
lineage-17.1-20200516-UNOFFICIAL-signed-a3xelte.zip

Awesome.

Boot okay, no blackscreen anymore.

thanks. kind regards