yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 1needhelp:
Hi, I've got A310F, I could install it okay along with GAPPS, but when trying to login with google account to configure/complete setup, it doesn't seems to be going through properly. Right after I typed my email address, it seems to be hanging on "checking info" and it has been on this for the past 15 mins or so. is there a problem with A310F? I've installed the latest variant. 16.0-20190408-unofficial-signed

please help. Thanks

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

after kept going at it (repeating endless times), I finally got through. I found that the connection to internet via wifi keeps dropping. It's not that it lost wifi connectivity, but after sometime it says "no internet". I had to stop and start wifi to get it going again.

is this a known bug?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The "checking info" thing is a bug of open gapps. You can skip it by going back or touching each corner of the screen in a certain combination. Mind the gapps doesn't suffer from this issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 1needhelp:
Thanks for that. I'll give mindthegapp ago, but do I need to install magisk for it to work? I don't know enough about it, but I'm guessing it does supersu plus more.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Magisk is used for root, and it is also required so that you can use some banking apps that use root detection (often they don't like custom ROMs).

You will need to do a clean install if coming from open gapps.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 1needhelp:
I just tried mind the gapps and it's doing the same thing. The WiFi is connected but kept saying no Internet.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 1needhelp:
I've wiped, system, cache, dalvik and data, and still getting the same issue with wifi. rather annoying, not sure why this is happening.

---------- Post added at 11:56 AM ---------- Previous post was at 11:46 AM ----------

do i need to install particular version of mindthegapps? i installed the version from 3/2/2019.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
Is the device you are trying to flash and your wifi router familiar from earlier?

Do you have access to the settings of your Wifi router?

I'm thinking this may be a WEP/WPA/WPA2 (+AES/TKIP) issue. The router knows the phone from earlier but reads different connection info from the same device.

I remember this being a problem with the PS4 (PS3?). Every now and then I had to switch between the different standards because the router didn't like the way the playstation was communicating after an update.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 1needhelp:
thanks Jofan, I think you hit the spot there.

it's weird though.

I'm using tenda wifi (mesh wifi).

their app is quite basic, so I cannot actually see where it kept the record of MAC addresses.

But the weird thing is, that when I created a second SSID, it worked straight away.

what I noticed right after your comment, is that the phone kept saying that I need to "sign in" before I can get out to the internet.

Now, I'm UK and using BT as ISP. Before I purchased Tenda Mesh WIFI, i used to be getting this "sign in" since BT router was also acting as the WAP.

But since I used Tenda, I never had that issue, that's why I never thought it is potential culprit.

anyway, I can continue setting this phone up, but whenever I put it back to my original SSID, I am still getting this issue. I'll see if I can find the MAC in BT router.

I will clear ARP on my cisco switch as well.

If you have any other ideas of where to look for this, then that'd be much appreciated.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like a 'Have you tried turning it off and on again?' moment :D.

At home I have a BT HH 5 and have no issues with WiFi and at work we have a BT business hub and that also works very well with my A3.

The words "Mesh WiFi Network" always fill me with dread, it is not a good solution to wireless signal issues.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
I think my phone wont charge right. Some days i got 44% after over night charge and another day it might be 78%. I even made test with different cables and chargers.

And some times my phone makes weird reboots. I think alarms makes them happen. Yesterday when i woke up at morning my phone alarmed and after i dismiss alarm, phone rebooted.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Is this with the latest release?

Can you get a logcat of this failed charging?

Also check that the USB port on the phone is clean, sometimes dust can cause issues with charging
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Im running latest release but...

I bought new charger and it works like charm so i just have foulty chargers.

Some random reboots still appears. Today i listened music from soundcloud and when song changed to another, whole phone rebooted. I try to give logcat from that. I need to check my log first.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Is the random reboot a full reboot or just a UI crash? (If you see the Galaxy A3 logo then it is a full reboot).

If you are getting a full reboot then can you dump the /proc/last_kmsg file (you need root to access it)? A logcat wont reveal anything after a full reboot.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] menca93:
This morning the phone was 54% charged, at 11.30 the phone turned off completely (0% battery), the phone has never been used in that time frame.

Second problem:

When I get to 15% of the battery the phone becomes very laggy and changes application by itself
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Sounds like either an app started going nuts this morning or something, most users are reporting better battery on LOS 16 compared to 15.1.

Below 15% might be the automatic battery saver kicking in, this usually just leaves you in a reduced power state (disables animations, etc), this can be configured in the battery settings.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Its all time full reboot when its related to alarm or "soundcloud" in my case.

I took logs today with SysLog from F-doid every time that happened. SRY i need to put them somewhere, i cant upload them right here..
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The /proc/last_kmsg is the only file that will help in case of a full reboot. Upload it to google drive or something
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Thanks for the PM with your logs.

Looking at the logs you are still running the previous release (07-04-2019) which suffered from a reboot bug that I fixed in the latest release (08-04-2019). Please update to the latest release and your reboot issue will be solved.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hameez21:
Stability

Can any1 ensure how stable is this as a daily driver
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I use this as my daily driver and it is very stable. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
I have used it since the first release, end of March, and not experienced any crashes, freezes, restarts etc. No problems with audio or video. Highly recommended.

You need to be aware of charging problems though. Sometimes it doesn't charge the battery even though the cord is connected and the battery charging icon is visible. Seeing the battery percentage on the home screen is usually a good indication that your phone is charging (or just turn the phone off and connect your charger).

Try it out! I recommend it!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hieuvo:
It's really stable and really good but i'm getting 4h of screen on time instead of 5h when i was on 15.1, it's not a big deal since the phone charge fast
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] 1needhelp:
it is stable for me too. One issue I have though which is not really related to the stability of the ROM as such.

But I've install this ROM for my daughter, I then installed google family link parental control. this for some reason has switch FRP lock back on.

Is there a way of removing or disabling it within Lineage OS? there's an option within Samsung ROM to enable the "OEM unlock", hoping lineage OS has the same ability. Thanks
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
[MENTION=6707196]danwood76[/MENTION] I don't know what I did wrong but I always end up with error 7 even though I followed the OP installation guide to the letter (same with dotOS)

Edit: nevemind, managed to do the install by installing first the dotOS-O-v2.5-a3xelte-UNOFFICIAL-20190323 then after full reboot, flashing dotOS-P-v3.0-a3xelte-OFFICIAL-20190410-1339 as an update and open gapps 9.0 in the same queue.

I'll stay for some days on the unrooted configuration and see how it turns out but after 1/2 hour or so, I can already say that the rom is amazing - quite nice feature the Equalizer!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I have fixed this issue in my current kernel code and this fix will be in the next release in a few days.

It looks like it was a bug that affected the stock firmware too, if you do not plug the phone in for more than 20 hours you get the charging issue as it miscalculates the time it has been charging for and the safety timer kicks in.

-- edit --

Also to work around this issue if you notice it is not charging you just need to unplug it and plug it back in as this should clear the timer issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You need to be running the latest version of TWRP. From your log you are running 3.0.2.1 which is very old and doesn't really support Oreo.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] mohand06:
Thanks for the reply but this happened on twrp-3.3.0-0 that I flashed afterwards. Anyway, as I said, after prior flashing of the last oreo build, then doing the wipe, the new build installed fine.

Unfortunately, there's still that bug of the screen going black when making a call and struggling to end or cancel it by tapping on unresponsive home button (it was there also on 8.0 builds).

And I also noticed that the stock browser is really laggy. Cheers.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
The black screen "bug" sounds like a broken proximity sensor. Mabe only some dirt on it. You can select in settings to end a call with power button.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The issue in your TWRP log was caused by the incorrect version. If you still get error 7 in the latest TWRP please send me another log.

The black screen issue you describe has nor been reported by anyone else. It does sound like a faulty sensor or a dirty/bad screen protector.

Stock browser seems fine to me, we loose a little performance due to not having hwc yet.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
Yes Sir! I am aware of the problem and I am aware of a solution. Thank you most kindly for the ongoing struggle with the ROM (and us in the forum :eek: :highfive: :silly: )!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
[MENTION=6707196]danwood76[/MENTION] did you think about updating binary blobs? There are stock roms with February security patch level.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I am currently testing the updated blobs, they will be in the next release if I find no issues. ;)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] s3korn:
Hi Danwood,

I have this charging bug also in your 15.1 build. Will u update the 15.1 kernel too?

Best regards,

S3korn
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, it is already backported to the Oreo kernel tree.

There will be a new release when the security patches land.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hameez21:
I am currently running the stock rom that came with the phone and i have noticed that sometimes my phone does not charge overnight.

It may be bcoz of this issue
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It probably is. The same workaround should work with unplugging it and plugging it back in.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] tomtomgo91:
Can i update from your Lineage OS 15 without wiping the Phone? Thanks for the great work!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hameez21:
Hey,

I was just wondering why did you disable hwc isn't it quite favorable for performance and battery while watching videos and playing games?

and if it does not cause any issue how can I enable it?

or there is no performance or battery gain with this enabled?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Users have reported that it works, when I did it it did work but my gapps got corrupted and I ended up with random force closes. It might be because I was previously encrypted though, not sure and I didn't think it was worth investigating.

It is safest to do a clean install and it is actually quite quick (if you have fast broadband).

What I do is make a google backup, backup WhatsApp (or any other app that doesn't support google backup). In TWRP I also backup cache, data, system just in case.

Then do a clean install (wipe cache, data, system, (backup and format internal storage if encrypted). Then install as normal.

With HWC enabled we get random black screens and redraw failures. I am going to debug it but I am very busy at the moment.

With HWC enabled you gain a little in 2D performance (phone feels smoother when redrawing lots of 2D overlays) and probably a small amount of battery. It really isn't a major issue, it is just listed in the bugs (you probably wouldn't notice if I hadn't said anything ;))

Regards,

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

Uploading a new release now (17/05/19).

Changes since last build:

kernel: fixed non charging issue if USB is not plugged in for 20+ hours

NFC: default to slower but more reliable firmware loading mechanism

system: optimised the vfs_cache_pressure which improves FS performance and fixes most MTP issues

ramdisk: fixed lots more permissions and selinux denials

vendor: Added missing magnetomoter configuration file

vendor: Updated blobs to February security patch

Android May security update

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
[MENTION=6707196]danwood76[/MENTION] you still build oreo and pie. Are they equal in terms of security and performance?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hameez21:
Hey danny,

Just wanted to know i can update the rom just by flashing the new one from twrp right no need to wipe anything or lose any app data?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
That's the way i do it as long as i stay with the same Android verion.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Yes, just install this in TWRP to update. You won't loose data. :)

The Oreo builds are probably more reliable/stable as they are a much older code base, I ran this for months without any real issues.

The state of Pie is very good, I am currently having occasional issues with the phone not dropping to deep sleep which I am debugging, I think it is WiFi related.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lawliet80:
Now that you mentionned it, there must be something that causes the battery to lower faster (is it english? XD).

There are days where i got low battery quite fast, and sometimes not. :confused:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I am working on it :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The current deep sleep issue seems to start when you disable WiFI (usually the second time you disable it).

I have found that enabling WiFi, rebooting the phone, and then never disabling it results in good deep sleep behaviour. You can also disable WiFi, reboot, and then use the phone without WiFi enabled for a similar good deep sleep behaviour.

The system appears to start repeatedly scanning for WiFi networks and not allowing the device to enter deep sleep.

I am working to find out the root cause of this issue but I have a above work around for now.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Would that mean that the issue comes when we change thw state of wifi? Maybe something not properly configured while shutting down the interface
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Specifically it is when the system_server process shuts down the interface. It seems to go into a PNO scan loop which triggers a few wakeups every couple of minutes and prevents the device from entering deep sleep (PNO is disabled in the overlay and only seems to activate when the interface is taken down). So my thoughts are that there is a bug or incompatibility between our driver and the latest HAL. I will find it soon enough :).
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
For me the issue also occurs when leaving a wifi. My workaround so far besides rebooting the phone when the issue occured is to automatically disable wifi via a systems profile once the connection dropped. Thereby I could typically avoid the problem while having to manually reenable wifi when necessary.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Uploading a new release now which should fix the WiFi deep sleep issue.

Full change list:

manifest: downrev android.hardware.wifi to 1.1 to fix deep sleep

ramdisk: fix a typo in the WiFi init script

system.prop: remove incorrect assignment of 'wifi.direct.interface'

kernel: Add in the UID field to xt.NETFILTER​

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
This doesn't seem to have solved the sleep issue entirely.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
You're still making progress! Thanks!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
+1 .. 1UP .. True true! I second that!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I think I have a solution now. Just doing some final testing today. :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
I'm using the 17 may build.

I'm seeing the camera crashing after first use.

At first attempt it works just fine. All the settings and modes works.

After exiting the camera, using home or back button, the next time I want to use the camera the interface is frozen; nothing reacts to me pressing the icons (no picture, no way of entering the gallery from camera, no mode selection, no settings, just frozen). Any pictures taken during "first attempt" are still in the gallery and visible in camera/gallery app so no loss of data.

I have tried

--using using home and back button to exit the app.

--starting the camera app in portrait and landscape.

--change storage to SD card/internal.

--forcequit the app.

...there is no difference in outcome. The UI is just frozen and a restart of the phone is needed to take pictures.

All the best!

EDIT: I just realized there is a 21 may build. Sorry. I will update and check back when I get the chance.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I cannot reproduce this issue. The Camera HAL sucks unfortunately and does crash occasionally, there isn't a lot I can do about it.

Rebooting the phone is the easiest way to recover the camera hal, sometimes restarting the cameraserver whilst running can recover it (run 'killall cameraserver' from a root terminal).

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
I did something: :victory:

- I changed the contrast from 6 to 4 and back to 6 again.

- I switched from front camera to back camera a few times

The camera has been working for the last 80 90 minutes.

I haven't changed anything else or been using the phone during this time so I assume something connected with what I did 'fixed it'. Just a small hickup :)

All the best!! :highfive:

EDIT: Camera still works at 1840 CET! :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Uploading a new release now, sleep issues with WiFi now seem solved.

I'm actually getting really good battery with this latest build :).

Can people please test this build and report back if they have any WiFi or sleep issues .

Full change list:

overlay: enabled WiFi background scanning

manifest: reverted previous downrev of android.hardware.wifi​

Regards,

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

Is there a way to get a working radio FM app (no net streaming) like the one in the stock ROM?

Spirit FM2 or a stock ROM apk for example

thanks in advance
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
Just updated to 23 may build (and camera still works! Woh!)

I will keep you posted

All the best! :highfive:

---------- Post added at 07:13 PM ---------- Previous post was at 07:05 PM ----------

As much as I would love one I don't think there is much chance for it at the moment.

From the 15.1-thread:

Seems to be a bit of a hassle :(
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Hornelen:
Good ROM.

-Sounds app not working,when i click on a sound,its shows loading symbol,then nothing happens.If i end app and start again it shows exclamation symbol (!) next to the sound track.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Works fine for me.

Did you block the permission for sounds to access your storage by any chance?

Can be checked in Settings->Apps->Sounds (You need to click the show system apps from the top right drop down)

My only other thoughts are, bad gapps install or a bad backup restore.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Hello guys,

Finally took time to flash my phone.

TWRP 3.2.3-0 from 1st post.

After flashing rom+Gapps(pico-arm-v9)+Magisk system starts, got the LOS animation, but then it reboots into Recovery/TWRP.

Wondering what I did miss:confused:

Edit:

Tried flashing only ROM and it boot properly.

I then rebooted in Recovery and reflashed Gapps and it worked. Strange.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] exzemat:
Hello,

Sorry for the Newbie question :

Is it possible to extract and use the camera.apk (stock rom) made by Samsung ? To fix the hal issue bacause of closed source
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That won't work, the Samsung apps need Samsung libs.

I have a new fix to my camera wrapper that is working well for the built in camera (Snap), I have also tested open camera and that seems stable too. Just google camera is still buggy but I think that is a bug in the open gapps google camera package.

I will upload a new build later including my new fix.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Uploading a new release now (27/05/19).

This should fix any camera crashes (lost focus, hard lockups, etc), I have been thoroughly testing my new fixes and haven't crashed it yet.

Google camera (from open gapps) is still buggy but in debugging it I think it is the app doing strange things rather than a specific hal issue, it is known to cause issues on other phones so i would still avoid using it, best results are with the built in camera app Snap.

Changes in the 27/05/2019 release:
[INDENT]camera: improved camera wrapper to fix camera crashes (still avoid google camera)
LOS updates[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] jofan:
[regarding build 20190523]

I have noticed (three times so far) that the phone rejects the charging process when having reached 100%. The lightning symbol is still visible in the battery icon but there is no "charging/charged" notification and the phone shows battery percentage declining. Good old unplug/plug-in technique does the trick and the phone "accepts" the charger with no further quirks (I had my eyes on it for the next eight or ten hours).

...camera still works though :victory: