yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TheRealSerkus:
Custom Binary Blocked By FRP Lock

I have the same problem here. Everything works until I set up my son's account with familiy link. When I restart it then the device is locked. Any ideas?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
OEM unlock has nothing to do with FRP. FRP is a Google feature, if you remove your Google account from a device you disable FRP.

If you are having issues with FRP then your gapps is at fault. Are you sure FRP engaging on boot isn't a feature of family link?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Today, issues with calls. Other recipients was not hearing my voice immediately or aftet a few seconds. Other calls were ok. It's not all call.

Planning to flash June rom or a new coming soon?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I haven't had any reported of audio issues for months and in the latest update nothing changed on the audio side of things so I doubt rolling back will help.

You can occasionally get issues on cell networks that can cause this, or you might have a dirty/faulty microphone. Best thing is to monitor it and if it happens again send me a logcat.

Was this calls to one particular person? (if so they might have a faulty speaker?)

For a while my wife had a faulty microphone on her iPhone and that was causing similar issues (but the other way round) and was very intermittent, some calls would be completely fine whilst others she would come and go. She blamed my phone of course but it turned out to be her mic :).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
I've recently had an issue as well--after waking up the phone, the touch input did not work at all while everything else did; I could tell that e.g. by the fact that all buttons were working. I had then waited for ~10 mins with no result, so I pulled a force reboot. It happened when I had Strava running and recording an activity, if that changes anything (no worries, Strava had recovered it afterwards :p)

EDIT: It happened today again also with Strava running; this time I waited ~40 mins since noticing the issue--nothing changed. I then quickly pulled the logcat, was about to restart the phone, and you know what? It started working out of nowhere! So I then pulled logcat once again.

The non-working touch input: https://drive.google.com/file/d/1iM8TqxU8bdblWgj3phlVY-5p9ZQwpEtH/view?usp=sharing

And the moment it started to work: https://drive.google.com/file/d/1lW0OAFMRtBQw_Romg7fyXspx-aEwAHLi/view?usp=sharing
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Unfortunately I cant see anything touch related in the logs.

When you say everything else worked were you seeing animations on the screen or was it frozen?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Everything seemed to be working, along with animations; didnt notice any stuttering in these either.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] dan_marcu:
I also had some touchscreen related problems, the touch was not registered, had to press a few times until the phone reacted, and it was on buttons not swipes. I wiped the phone and installed the June build and i no longer have that problem. Also the battery life seems better after 1 day, I'll have to test it for a longer period to be certain.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
When you say touch wasn't working, do you mean the touchscreen or the touch sensitive hardware keys?

I assumed you meant the touchscreen?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Yes I meant the touchscreen; I havent actually checked the touch buttons though (it was stuck at the lock screen, so I wasnt really able to do so anyway).

PS I havent yet rolled back to the June build; I am able to keep on going on the latest one by restarting the phone every ~24 hrs, otherwise it starts to behave as if it had sth like 500 mib of physical RAM installed. And still, even despite me performing those reboots, it doesnt overall feel as snappy as it did before this latest July relase.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Touchscreen input freeze

Hi,

Today I've made a discovery. I had the Strava running and the issue appeared again (Strava run for ~1 h, as in the previous cases). It appears that the issue here is the lockscreen itself--it doesnt respond to any touch input (I've been tapping on it and then the phone had dimmed the screen and locked due to inactivity), but the notifications and clock were updating, so it was not frozen. HOWEVER, when I pushed the volume button and the sound menu had come up, this menu DID respond to touch input AND it prevented the phone from dimming the screen, unlike the lockscreen UI.

My discovery doesnt end there. As soon as I took my USB cable and plugged the phone into my laptop, the lockscreen immediately started to respond to touch input. (it was Windows that I plugged it into, and the phones USB mode was set to 'no data transfer' (i.e. charging only))

PS When the lockscreen was not yet responding to any touchscreen input I was also unable to pull the status bar down.

PPS Since connecting the phone to the computer (and disconnecting as soon as the touch input worked), I can lock the phone with Strava STILL running, and the lockscreen doesnt freeze at all. But I guess, if I had now waited another hour with the screen off and Strava running, the issue would then appear again.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Thanks for the in depth investigation.

Just to check, are you using the stock lock screen?

I will check the lock screen change log.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Yes, I am
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Uploading a new release now.

This fixes the SSWAP issues and so low memory issues should be solved (hopefully [MENTION=7472360]witampanstwa_[/MENTION] this was the cause of your issue).

Changes in the 19/07/19 release:
[INDENT]Fixed SSWAP
Synced with latest LOS sources[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
And disable of HWC?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
No, I can post another build with it disabled of required?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
If it's more stable, yes. :)

If it's not linked, then it's not needed
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
[MENTION=6707196]danwood76[/MENTION] , one issue is now fixed for real! :D I've just got running Spotify, Youtube, Chrome, Excel, Google Caclulator, Google Phone, Gmail, Google Calendar, Adobe Actobat, Google Docs and Google Drive, all simultaneously. And as a bonus, I've also had Spotify playing music during all this with no issues at all.

I've also been checking 2 times each time whether all the apps were still open, as I couldn't believe it, so my results are legit!

The phone gave up when I launched Samsung Internet (it loaded a bit complex site, what might have been the reason why)--but nonetheless, only a few of those background apps got closed (actually only the calcuulator, adobe acrobat, and nothing more!).

I'm speechless now.

I haven't checked yet if the lockscreen sill freezes.

---------- Post added at 09:08 PM ---------- Previous post was at 08:39 PM ----------

[MENTION=3330244]TimMayle[/MENTION] , I am pretty convinced that all the "unresponsiveness" we've recently experienced was not indeed caused by the buggy HWC, but rather by the malfunctioning ram management. Right now I do feel that the phone has also sped up -- to me, it feels like it is more responsive than its been on the latest June build. The animations still suffer a little from the HWC, but again, I think it is still better than turning it off, as -- in theory -- thanks to it we should gain some battery life and performance.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
Good evening, I'm sorry I keep freezing on the screensaver even with the new version (20190719)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I have created a couple of flashable zips that enable and disable HWC for people to test with.

The enable script (Exynos7580_HWCEnable.zip) also adds a new build.prop option that [MENTION=8184192]Stricted[/MENTION] found that should speed up some animtations (seems to help a lot on the A5) so I would be grateful if some people could test that out too.

Both can be found here:

https://mega.nz/#F!aEgXhAoQ!R4rhV9lKhr7xwdgntgVdOQ
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
I've flashed the Exynos7580_HWCEnable.zip and it looks like all animations are now as smooth as they were on the build with HWC disabled (I've tested recent apps switcher, Youtube and app open/close animations).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Flashed last rom and enabled HWC. My wife will quickly let me know :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] aggellos2001:
Hey there. I've been using this ROM for 2+ months and it's great no problems. The only thing that I've encountered and I wanted to report it here so maybe it gets fixed if possible is that although the NFC is working, it's very inconsistent. What I mean is that when turning it on it may take few minutes to open or even hours. Sometimes it will open after a restart of the phone and so on. Apart from this issue everything else is working as intended. Thank you.

(Although the latest build seems to be better for now)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
NFC usually takes around 10 seconds to switch on.

It you use it a lot then just leave it on. In testing I didn't see any real difference between having NFC on or off in terms of battery use.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] aggellos2001:
I see. I am used to disable it when not needed that's why probably.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Maybe, it depends on when [MENTION=7377908]dariotr[/MENTION] synced from my trees. HWC will also be patchy on DotOS as we have only just fixed the remaining issues we were having.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Hey,

Im here to complain about lock screen again. I've attached pictures dwscribing what is wrong with it--it does not show the 'lock screen message' and the weather--as well as how it should look like.

PS The blank space between the clock and the date does not smallen if the 'lock screen message' is set to none.

PPS I've just realised that my weather provider's api key is still 'pending verification'... But it doesnt explain why the lock screen message isnt showing though
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Complain away, I will simply ignore your post.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Just tested and it works just fine on my main A3 (running latest release).

Maybe it is something to do with your weather provider. I don't think it is supported in Pie.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] aggellos2001:
By the way yesterday I updated to the latest build (I was 2 versions behind) and I now experience the same problem like some to other people said. When trying to unlock the phone sometimes it doesn't register my input and only reacts to the back button. Like I can't do anything. I have to wait a few seconds or minutes and then it may work. This happens randomly and it's very annoying because you cannot access the phone. Very weird.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I have just uploaded a new release.

[MENTION=8184192]Stricted[/MENTION] and I managed to fix the remaining major issues we had in our HWC implementation.

This release is very smooth with fully working HWC!

Changes in the 23/07/19 release:
[INDENT]Fixed remaining HWC issues (we now build with no hacks to upstream LOS)
Added buildprop to skip waiting for buffer fences to signal (thanks [MENTION=8184192]Stricted[/MENTION] and @Ivan_Meler)
Build new HIDL lights HAL
[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Try my latest release. I have a feeling that issue was caused by either RAM issues or HWC.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jpm92:
Hello Dan! My father has been telling me to "do that thing you do with old phones to make them usable again" for a while and I think now it's time to install this ROM on his phone.

I've never used custom ROMs on Samsung phones, but I guess unlocking the fastboot should be similar to other ones. Apart from that TWRP is official so no problem with flashing the wrong version right?

Thanks a lot for your work! It looks like you made an awesome job!

Any chances of going official? ?

Regards,

J.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I just had a quick search and this is a fairly good guide:

https://www.androidinfotech.com/root-samsung-galaxy-a3-2016-sm-a310f-m-n0-y-nougat/

Just get all the files you need from my original post as I don't know the quality of the links to TWRP and Magisk in that guide.

Version 3.13.1 of Odin worked well last time I did this:

https://www.androidinfotech.com/download-odin-all-versions/

One thing to note, about half way down that guide it says 'PC. Also, navigate to “options” and tick the Auto Reboot.', make sure auto reboot is not ticked as the stock firmware will overwrite TWRP when it first boots (very annoying when you forget this). Once flashing of TWRP is complete you need to reboot yourself, I usually hold all the buttons and then release the volume down once the screen goes black and you should end up in TWRP.

Once you have TWRP installed you can then flash my ROM after erasing the various partitions.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] aggellos2001:
Tried the latest release with full reset and still happens. :/
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
What do you mean by full reset?

Can you produce a logcat of it misbehaving? Without logs I can't possibly help.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] aggellos2001:
By full reset, I mean full wipe of system, cache, data everything and then re-install the ROM.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Odd, I cannot replicate that with either of my test phones.

Can you post a full logcat from boot?

And a dump of /proc/last_kmsg might help as well.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mobb_Deep73:
Best upgrade experience ever (really not recommended):

> Running your Lineage 15.1, thought: need to install the latest security patches

> Googled the thread, didn't pay attention, dirty flashed this Lineage 16

> Booted, other UI, huh? Google services keeps crashing, Gmail / playstore didn't work anymore

> Flashed Lineage 15.1 back, didn't booted, flashed this Lineage 16 again

> Realized I made a mistake, downloaded OpenGapps for Lineage 16, flashed it

> Playstore works again, reinstalled Gmail

> All seems fine now

* Did wipe cache / dalvik cache after every flash

Thanks for keeping this device up-to-date!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
:silly:

You went through quite a bad upgrade experience :o

Glad it went fine at the end.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Glad you got it sorted in the end. Yes you need to update gapps when upgrading. If you get any issues/instability with gapps you can always wipe just the system partition and then reinstall ROM + OpenGapps + Magisk (in that order) and it will keep your data.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Does anybody else experience weird screen behavior with latest release or is it just my phone? When battery is bellow 40% i bearly can use phone. Then i put it on charger and wola, it works again.

Edit. It seems to be random so it not always happen under 40% battery.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Not on mine.

Just strange issues with mic after 2-3mn calls
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
I also had the screen lock, I disabled HWC on version 20190723 (Exynos7580_HWCDisable.zip)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Does it solved your issue?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
it seems so ... now it is more than thirty-six hours that it works
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Can you produce a logcat of the issue? I think [MENTION=7377908]dariotr[/MENTION] had a similar issue with his A3.

Does it occur when the device is overheating?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
I noticed: when it got stuck it was always overheated, there can certainly be a connection
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
I can try to logcat it. Lets hope its happening again. I dont be sure about overheating becouse here is bit hot weather :p

In addition, when screen is locked menu and back buttons haptic feedback is on. Small wibrate come if i touch either.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Oh. It sounds like you somehow have AOD enabled. It is not supported on our device.

Are you using pixel launcher from stock gapps? The "pixel stuff" Magisk module enables AOD. A few pages back someone modified the module to remove the AOD addition as it is not required.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
I use Trebuchet launcher. Only module whom i use is youtube vanced.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Have you installed any other modifications? The symptoms you describe are exactly like when I enabled AOD in testing, our kernel driver doesn't support it so you get strange behaviour.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
No, i dont have any mods or anything like that. I can not come up with anything which enable AOD. Is there any way to check if it is enabled?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Hi,

If anyone wondered where did the blank space on the lock screen come from, its because of the magisk module Ive attached a screenshot of.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Which log you need? I tried to make it with SysLog APP and it makes many different log types.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
I face the exact same brightness problem as well; it is still there on the latest build
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You just need to keep adjusting the brightness. It will learn what you choose and eventually you will stop having to adjust it.

On my A3 I never had to adjust the brightness after a week or so of use, it always picked the right level for me.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Matlog produces good output, just install it and then open it and let it run in the background. Do a couple of sleep tests and then save the output (including dmesg) and upload it here or PM it to me.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Is it just my setup? Every reboot, the Colour profile jumps to dynamic! I really prefer "Standard". Latest ROM without GApps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Hello guys,

I experienced issues with roaming lastly. I went abroad and tried to change mobile network from automatic to manual, but it kept switching back to auto.

It provided me a choice of operators, but kept failing (maybe for other reasons).

I left it so, but we had to reboot the phone to connect back to native network.

We also experienced an irresponsive touch screen. I could power the screen, but somehow, was not reactive to any touch interaction.

It was also impossible to force power it off with a long press.

I had the feeling that plugging it to power source could change it state. And it did. Plugged power and it brought back touch screen :)

Any other experienced this or could try?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
I can confirm the issue with the lock screen. The buttons still work. Sometimes it is possible to reboot from the menu but I usually have to tap several times before it reboots. I'm on the latest build and also tried to enable/disable hardware acceleration to no avail. Plugging the phone into the charger also helps in my case.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
When it next happens can you plug it into your charger, reboot your phone and then dump and send me the /proc/last_kmsg file? (you need root)

Without that kind of log it is impossible for me to debug as I haven't experienced that issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
I'm not rooted since this interferes with Google Pay. I want to give it another try to disable Face Unlock and inactivity display first.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Google Pay worked fine for me with Magisk installed. :)

You can dump the file from within TWRP by copying the file in file manager to your externalsd.

You managed to get face unlock working? I thought it wasn't supported on 32 bit arm?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
I found it too annoying that Google every now and then worked around the methods Magisk used to hide itself with Google Pay suddenly not working as a consequence. Face Unlock has been working without an issue for most of the time. I simply installed it as part of OpenGApps. I'll try the TWRP method once the problem occurs again. I didn't have had the issue yet again but outside temperatures also dropped a bit.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
Some problems here, when making a call: Flashlight starts when calling and can't be turned oft, because the screen does not turn on, when taking the phone from my ear. I have to wait, until my conversation partner finishes the call. Anybody else has similar problems? I did a clean falsh, no other problems occurred. No Gapps installed, no mods.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
Hey man, this is very interesting to read.

I have the same problem since I installed LinOS 15.1.

See here: https://xdaforums.com/showthread.php?p=79879790

I went back to stock and now I'm on dotOS 3.1. But since I installed a custom ROM the first time, the proximity sensor isn't working anymore.

Did you go back to stock? and if yes: how is the function of the proximity sensor?

Gesendet von meinem Mi 9 SE mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
No, i didn't go back to stock, but may be, i will try. Thanks! Anyway, the rom is very good, thanks [MENTION=6707196]danwood76[/MENTION]!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The thing with the proximity sensor from your logs is that it appears to be communicating with the chip correctly but it is always reading back the maximum value. This would point to hardware issues like, a cracked screen, poor quality screen protector, scratched screen protector, something behind the glass (have you had a battery/display replacement?), or simply a faulty sensor.

You can see if the sensor is enabled by shining another phones camera at it when it is on, open the sensor page in something like AIDA64 and open the camera on the second phone, you should see a purple dot flickering next to the earpiece if it is on.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
[MENTION=6707196]danwood76[/MENTION]: Thank you!

Sensor is working as descripted.

But the Sensor reading stays [MENTION=8690982]255[/MENTION]. So maybe a brocken/bad glass. [emoji24][emoji24][emoji24]

Gesendet von meinem Mi 9 SE mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The sensor is made of a transmitter and receiver. You can see the transmitter is working but the receiver may be broken or bad glass. Is the display lifted up or scratched around that area?