yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
I always disable AudioFX first thing, then install this time around only James dsp as equalizer using a good ViPER-DDCs for better sound experience both in volume (gain) and quality - AudioFX prevents jdsp from working. I have used a lot ViPER4AndroidFX as installable apk (pittvandewitt's v2.7) or flashable zip either with Magisk or Lineage root and have no issue with your builds or official nightly.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Can you recommend a simple installation method for james dsp? Ideally without magisk?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Jdsp in an all-root solution according to developer.

You can install james dsp using the zip in twrp which needs the use of volume buttons for the selection of the driver quality or opt for manual installation.

The latter procedure needs (for those like me who aren't put off by some manipulations on this tiny device):

1) extracting the content of the zip where you get 2 other zips in Custom folder, bp.tar.xz and ff.tar.xz which hold the Bit Perfect and the recommended Full featured apps and libs for your choice

2) extracting and placing the 2 libs in /system/lib (libjamesDSPImpulseTol.so) and /system/lib/soundfx (libjamesdsp.so), and the privapp-permissions-james.dsp.xml in /system/etc/permissions not forgetting to give 0644 permissions to these items.

3) install the extracted JamesDSPManager.apk if it shows in it's purple dsp icon - in nougat, a JamesDSP-Manager folder will be created in /system/priv-app, in Oreo+ the app normally works installed in data.

[ entries will be added to /etc/audio_effects.conf and /vendor/etc/audio_effects.conf (or audio_effects.xml for oreo+, I'm still on stock nougat):

in libraries section library name: jdsp path: /system/lib/soundfx/libjamesdsp.so

in effects section effect name: jamesdsp library jdsp uuid f27317f4-c984-4de6-9a90-545759495bf2 ]

4) Uninstall audiofx as it prevents jdsp from working

5) Enjoy!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
I have started playing around with MatLog (please let me know if you would advice me to use another LogCat reader) to view what's going on in the background so there may or may not be a lot of questions in the coming days (sorry!).

I have noticed three things-

AlarmManagerService is really keen on getting the timezone right. During the last 90 mins it has updated the kernel timezone 14 times. Is that really necessary?

Line 3362: 09-12 07:27:02.231 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 3375: 09-12 07:29:34.085 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5367: 09-12 08:48:14.196 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5512: 09-12 08:53:26.120 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5723: 09-12 09:00:33.645 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5725: 09-12 09:00:38.375 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5738: 09-12 09:00:59.200 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5770: 09-12 09:02:04.193 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5783: 09-12 09:02:36.481 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5787: 09-12 09:02:54.054 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5795: 09-12 09:03:21.299 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5799: 09-12 09:03:33.732 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5844: 09-12 09:04:58.598 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

Line 5860: 09-12 09:05:57.112 D/AlarmManagerService(2557): Kernel timezone updated to -120 minutes west of GMT

For the last two hours WifiHAL has "Failed to register debug response; result = -95" 106 times. I don't know if that is unusual or strange in anyway. It's just something that got my attention.

437 instances since yesterday of "wificond(2429): Failed to get NL80211_ATTR_EXT_FEATURES". I don't know what that means.

There is a logcat if anyone is interested.

Curious George over and out
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Ignore all of the WiFi stuff, that is normal. I've not seen the timezone messages before but they are just a message, not an error.

Logcat spews out loads of info, not really useful for your average user. If you are looking for reasons why you might get unusual battery consumption then I recommend better battery stats (available on XDA).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
Thank you for clarification. I'm fine with the battery usage but interested in why my phone shows [BetterBatteryStats> Graphs> Wakelock] as almost completely blue and at the same time showing "Awake" in single digit number.

Also I'm mighty happy about my phone FINALLY starting to take an interest in how bright I want my screen to be! :highfive:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rabbit0083:
Is anybody using this Rom with the Google Familiy Link app? It runs fine even with family link (for my son), but as soon as I restart after adding his restricted account to the phone, FRP gets triggered and I have to reinstall Stock ROM to get access to the phone again. Any hints/ideas?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] heilbron:
I had this problem on my Galaxy A3 2016, too. I then reinstalled a stock ROM. If you want to do this, too, dont forget to set the "OEM unlock" before reinstalling LineageOS from scratch.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rabbit0083:
Yes, that's clear. But somehow the restricted google account along with the family link app triggers the frp-lock again. If I don't install the family link app, it works, but then I can't use the restricted google account.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I think the FRP lock on reset is by design with the family link app. However it should work fine just logging in with your google account, no need to reinstall stock.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rabbit0083:
Yes, it's definitely related to the family linsk app. But it already blocks the bootloader, so the only way out is to enter download mode (as TWRP is unreachable) and flash stock rom.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Oh, maybe the family link app is incompatible with custom ROMs. I will install it and have a play later in the week.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] afterglow:
can i flash another nightly on top or do i have to do a full flash and start from scratch?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You can download a nightly manually and update by flashing over the top or you can automate this by updating OTA from Settings -> System -> Advanced -> Updater
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] ono123:
i run the official build for about two weeks, it was good and run smoothly for use as my daily phone, but compared to the stock nougat the media sound was little bit lower. i had installed magisk, is there any suggestion to make the audio louder?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Magisk module Viper4Android
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Kobrika11:
Help

witch opengapps is better?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It really depends what Google features you want.

It is usually best to stick to the Pico gapps as you can install most other things from the play store if you need them.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
Good morning.I just flashed the latest build and when booting it takes me to twrp menu.I reboot to system and still takes me there.What can I do?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Wipe system before flash
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
I did it.Then I re-wiped all and installed just the rom and no gapps.After that it booted OK.So the problem were the gapps.Which gapps version should I download,arm or arm64? I downloaded arm64 and I got an error flashing them.By the way,if I first flash rom and later flash the gapps,should I clear anything?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] s3korn:
you have to use arm just pico...
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
After trying different gapps packages,a little earlier (and after my stomach joined my mouth) I discovered what you already said! Thanks !
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You need to flash your gapps at the same time as you install the ROM the first time or you will get issues.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
Although I didn't,for the present time, it doesnt look to have any issues.I used google play and gmail and they seem OK.What problems should I pay attention for?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
Well,I have these questions.

1.I have a problem saving photos from open camera to sd.It shows no thumbnail (just a gray image) but when I choose to edit (eg pictsart) it shows OK.

2.I want to root it.Is magisk device depended or it is universal? All I have to do is download latest and flash the zip in recovery? Does it reset any setting or something else? Should I be careful with something on this device before doing it?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
1. I don't care about open camera, it is not my app

2. Just flash Magisk it is not device specific but stick with 19.3 for now as I have heard reports of issues with the new beta release (19.4).

--edit--

I forgot to say, with a badly flashed gapps you will see lots of crashing of various things. If you get no crashing you sound be ok.

----

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jokeris:
First of all ...thanks the beautiful rom.The phone is at last...awaken from deep sleep!!!

1.It seems like there is no card access of the app (open camera or a better camera) so I thought it might has to do something with accessibility or some settings.

3.Thanks for the info/help

3.I do not have any crashes.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] diogogomes11:
What's the neste camera app for Thais ROM? The one which retrieves better camera quality results? Any way to install recent Google camera apps?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
LineageOS stock camera is good enough for me.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brutale1090!:
Hi guys, I have the 3.3.0.0 version of TWRP, I converted cache, data and system to F2FS, then I installed the last nightly.

The issue I-m facing is Error 64 when trying to flash 64 bit open gapps.

I tried to use the 3.2.1.0 version of TWRP, still 64 error

I tried to reboot into recovery, still 64 error

I can only install the 32 bit version, no ARM 64.

What can I do?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Read https://wiki.lineageos.org/devices/a3xelte/install

GApps version has to match ROM version, which is ARM 32 bit. What can you do? Try to find or build a 64 bit ROM?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brutale1090!:
Did't believe it were 32 bit... I strongly believed the opposite.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You need 32-bit gapps.

Samsung had a 64-bit CPU with 32-bit userspace with the Exynos7580 devices (as is shown on the device wiki (https://wiki.lineageos.org/devices/a3xelte)).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 4nndee:
Hi

First, thanks a lot for this great ROM. I'm using it for a long time now and I was very happy, even with the unofficial builds. But since the official nightly builds are available, I have some problems to set up the phone.

I've always used a patch (tingle, nanodroid) to activate the signature spoofing feature. After the patch process, I copied the microg gmscore and the f-droid privileged extension app to "/sstem/priv-app" and after a reboot, everything was working fine. With the official nightly builds, the phone bootloops when I copy one of the apps to the "system/priv-app" folder. Any ideas why this happens, was something changed I'm not aware of?

I use TWRP 3.3.0.0 and the latest nanodroid patcher.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
There is one major change you are not aware of: there is a lineageOS microG fork for official devices:

https://download.lineage.microg.org/a3xelte/

No need to patch and move to system.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 4nndee:
I am aware of this and I tried it (sorry, I should have mentioned that in my initial post). If I use the LineageOS for microG everything works fine except the GCM registration. The microG self check shows that everything is fine, but non of my apps is able to register to the push service. I had this issue with the unofficial releases when using nanodroid patcher and nanodroid microG, too. And that was the reason why I always used the method with copying the microG service core to "system/priv-app" because that was the only way I could make it work properly.

So maybe it is better to ask two questions:

- Why is the method with copying the apps to the "system/priv-app" folder not working any more?

- Why is the GCM service in the Lineage for microG ROM or in the "normal" ROM with nanodroid patcher + microG not working even if microG tells me everything is fine?

An answer to at least one of them would be very helpful ;)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Answer 1: i think there changed something in boot process, regarding permissions of system apps.

Answer 2: you know the correct sequence? Enable device registration / enable GCM / threedotmenu disable confirm new apps / install app / trigger a cloud message

Oops 2 is OT here. Please continue in https://xdaforums.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 4nndee:
Answer 1: Thank you, now I know at least in which direction I need to focus my research.

Answer 2: I was not aware that there was a sequence, but I always did it that way. Activating the functions from "top to down" and after that installing my apps seem to be logical to me. But somehow this is not working for me at the moment. What I noticed with the build in microG ROM is, that it asks me for less permissions when I open microG for the first time. I'm not sure if this is because it is already integrated into the system or if this is a problem?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brutale1090!:
Hi guys, 2 questions:

- i believe charging speed is lower than stock, confirmed or just a feeling?

- does anybody know any kernel here around? I looked but found nothing

Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Charging speed should be the same.

It comes with an already optimised kernel.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sekil:
Hwc working? Dumpsys SurfaceFlinger ?

What about new exynos sources from TO21Consortium ? I'm run new display.so - but i'm think - no differents..
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
HWC works great on our official builds, [MENTION=8184192]Stricted[/MENTION] and I put a lot of hard work into making that happen.

The "TO21Consortium" source would need a lot of work to make it build correctly, it is also Nougat source so needs lots of patches to make it work on pie, on top of that it is for the later 7570 device and there is quite a bit of difference between the two.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sekil:
i'm make this working (display, hwc and all related hwc sources from to21consortium) - need some small edits in surfaceflinger. Send me Dumpsys SurfaceFlinger please.

---------- Post added at 05:20 PM ---------- Previous post was at 04:23 PM ----------

h/w composer state:
h/w composer present and enabled
Hardware Composer state (version 01050000):
mDebugForceFakeVSync=0
Display[0] configurations (* current):
* 0: 720x1280, xdpi=309.966003, ydpi=309.638000, refresh=16949152, colorMode=-22
numHwLayers=4, flags=00000000
type | handle | hint | flag | tr | blnd | format | source crop (l,t,r,b) | frame | name
-----------+----------+------+------+----+------+-------------+--------------------------------+------------------------+------
HWC | f6c98d20 | 0000 | 0020 | 00 | 0100 | RGBx_8888 | 0.0, 0.0, 720.0, 1280.0 | 0, 0, 720, 1280 | com.android.systemui.ImageWallpaper
HWC | f7064220 | 0000 | 0000 | 00 | 0105 | RGBA_8888 | 0.0, 0.0, 720.0, 1280.0 | 0, 0, 720, 1280 | com.cyanogenmod.trebuchet/com.android.launcher3.Launcher
HWC | f6c98500 | 0000 | 0000 | 00 | 0105 | RGBA_8888 | 0.0, 0.0, 720.0, 48.0 | 0, 0, 720, 48 | StatusBar
FB TARGET | f7063320 | 0000 | 0000 | 00 | 0105 | RGBA_8888 | 0.0, 0.0, 720.0, 1280.0 | 0, 0, 720, 1280 | HWC_FRAMEBUFFER_TARGET

hdmi_enabled=0
Primary device's config information
type | handle | color | blend | pa | format | position | size | intMPP | extMPP
----------+--------------|----------+-------+----+---------------+---------------+----------------------------------
OVERLAY | f6c98d20 | - | 0 | ff | RGBX8888 | [ 0, 0] | [ 720, 1280] | [ -, -] | [ -, -]
OVERLAY | f7064220 | - | 1 | ff | RGBA8888 | [ 0, 0] | [ 720, 1280] | [ -, -] | [ -, -]
OVERLAY | f6c98500 | - | 1 | ff | RGBA8888 | [ 0, 0] | [ 720, 48] | [ -, -] | [ -, -]

Primary device's layer information
type | CheckOverlayFlag | CheckMPPFlag | Comp | mWinIndex | mDmaType | mIntMPP | mExtMPP
------------+------------------+--------------+------+-----------+----------+-----------+----------
HWC | 0x 0 | 0x 0 | N | 0 | 0 | [ -, -] | [ -, -]
HWC | 0x 0 | 0x 0 | N | 1 | 1 | [ -, -] | [ -, -]
HWC | 0x 0 | 0x 0 | N | 2 | 6 | [ -, -] | [ -, -]
FB TARGET | 0x 0 | 0x 0 | N | 4 | -1 | [ -, -] | [ -, -]

This dump from my cm14.1 with sources from TO21 - what we need :

h/w composer present and enabled

And all layers - with HWC flag - this mean that hwc working - if GLES - hwc not working..
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
HWC is working just fine for us, no need to edit surfaceflinger. But we do not use the to21 sources.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sekil:
Send me logs from "dumpsys SurfaceFlinger"
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No, if you want logs you can download the ROM and do it yourself.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Dear Danny,

There is a gap in device installation wiki: after heimdall flash twrp --no-reboot the device stays powered. Next step is with device powered off.

My solution was to power off from download mode by pressing power and vol+ and vol- for 10 seconds.

Finally the adb reboot says "error: no device/emulators found". Tapping reboot in twrp says someting like " no OS installd" boot into lineageOS works nevertheless.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Well it is important to not reboot after flashing TWRP as the stock firmware overwrites the recovery when it starts up, that is why it stays on. But it does look like there is a missing instruction and it could be added to the device Wiki heimdall template (all other Samsung devices look to be affected too).

I will look into adding it.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 4nndee:
Just to let everybody know, I found a solution to my problem. It turns out that there is a generall issue with the registration to the cloud messaging service on some devices with Lineage 16 ROMs. It is not a problem of certain appps, in fact the cloud messaging service does not register at all.

The solution is quite simple, just open the phone app and dail

*#*#2432546#*#*

to reister manual. I foud this solution in a thread on github, related to this problem.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Didgeridoohan:
Hello everybody. Hope you're having a good friday.

Did some cleaning in an attempt to keep the thread free of drama. Let's try keep it that way...

Thank you for your attention.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sekil:
Bugs:

1. Kernel not compiling with -Werror flag

2. /system/bin/cs dont have proper selinux configs - not runing

3. use stock mcDriverDaemon and libs libMcClient libMcRegistry - compiled not working - many errors - maybe fix later.

4. hwc cant working with video overlays - use this - working good on lineage 16

https://github.com/Exynos7580/androi.../libvppdisplay
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] natheux:
Big thanks to all devs which are working on this rom, just installed on my brother's Galaxy A3. It runs smoothly ! :D

I hope the battery will last longer than stock rom.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mobb_Deep73:
My battery lasted only one day. This week I disabled the developer options. Now I have 3 days! Note: I almost don't use the phone.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
Good morning. I notice a litle bug on the mobile data Control. I define max data 7 GB and warning 6.9 GB, but the phone didn't warn me and didn't stop mobile data wen I reach de 7 GB. Did it happen to someone else? I use latest LOS Oficial build and it runs excelent except this litle bug. Thank you for the good work.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Yes. Download stopped at limit, but can be resumed. Look like a bad feature. Not a bug. MicroG versoin 0923
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Carlosrody:
But on my case, that won't happen. I don't have the warning and mobile conection is always on, even after i pass the limite i define.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rabbit0083:
Did you have the opportunity to take a look at this issue?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I've just tested this and can confirm that this is caused by the family link app disabling the "OEM unlock" toggle.

You can see why Google do this, if your child can install a custom ROM the family link protection is pointless.

We hide this feature intentionally in lineageos because it screws your install if you toggle it off. I will have a dig and see if I can force it on. (Just have to unbrick my test phone first :D )
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] rabbit0083:
Thanls for your effort. It's clear that a custom rom gets you the chance to avoid the "protection"-stuff, but It's a pitty that it prevents you from using Lineage. On a Galaxy S5 it doesn't cause any trouble (but I think the S5 doesn't have FRP).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Looking on the lineageos wiki the S5 doesn't mention the OEM unlock, so you might be right.

We may still be able to fool it. Really we shouldn't allow a setting which bricks the phone.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
Nobody needs family link, there are better (and open source) apps, if you want to set up a phone for a child
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] heilbron:
Samsung FRP and Family Link

After installing Family Link on my child's A3 with LineagoOS, the Factory Reset Protection (FRP) lock was also tripped off.

Reinstalled stock ROM yesterday and set "OEM unlock" (just before reading this. Thx!)

Just to be sure: Now, are both of you ([MENTION=80510119]rabbit0083[/MENTION], [MENTION=6707196]danwood76[/MENTION]) saying that - after installing LineageOS - the FRP would go off again, even when having done a "OEM unlock" before?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Only if you install the family link child's app and then reboot. I am trying to work out what's going on.