yashsingh1/xdaforums huggingface dataset:
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
Well,

My first thought was, that some parameters ( like offset parameters and other magic numbers ) were overwritten by installing a custom rom.

Because I did not alter the HW of the phone it is a strange coincidence...

Meanwhile I studied the datasheet of the tmd3700 sensor and found out that there have to be parameters send to the sensor.

Just for my understanding : are those Parameters part of the kernel? and are not touched by installing a custom ROM?

[MENTION=6707196]danwood76[/MENTION]: Do you know where I can gain access to tmd3700 to play around with the mentioned parameters?

I found this article on xda: https://xdaforums.com/galaxy-s4/i9506-develop/how-to-proximity-sensor-fix-cm-based-rom-t2997610

Is this also valid for a310f?

Gesendet von meinem Mi 9 SE mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Good thought.

This is the TMD3700 source file in the kernel:

https://gitlab.com/Exynos7580/andro...0/blob/lineage-16.0/drivers/sensors/tmd37xx.c

It looks like it might load its calibration values from "/efs/FactoryApp/prox_cal", what is the contents of that file on your phone?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
OK that EFS file is binary.

However you can view and set that file through a sysfs node located here:

/sys/class/sensors/proximity_sensor/prox_cal

Can you tell me the output from this command:

cat /sys/class/sensors/proximity_sensor/prox_cal

You can initiate a sensor calibration with this command:

echo 1 > /sys/class/sensors/proximity_sensor/prox_cal

Or reset it with this:

echo 0 > /sys/class/sensors/proximity_sensor/prox_cal

These commands need to be executed from a shell, ADB on a PC is easiest or you could copy/paste them into the internal Android terminal. (you need root).

-- edit --

I forgot to say that to test the values of the prox sensor from the sysfs nodes it needs to be enabled by running something like the sensors page on aida64, you should be able to see the raw values and how this changes when you move your hand closer by running this command:

cat /sys/class/sensors/proximity_sensor/raw_data
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
I shared more logs for you. I hope those help.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Looking through your logs it looks like your phone is never entering the doze state, have you disabled any system services from running?

I also notice you run Titanium Backup, have you restored a backup of any system services? (that can really mess things up)

Can you install better battery stats and see if it can work out what is stopping sleep?

My only other advice would be to try a clean install (don't restore your backups) and see if the problem persists on a clean install.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
Thanks for your support on prox sensor. Unfortunately I'm on an urgent business trip.. So no chance to get my hands on the phone of my wife. I'll try on the weekend.

So long...

And Keep up the good work [emoji106]

Gesendet von meinem Mi 9 SE mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
hello there, iam using currently Lineage OS 15.1 from 16.05.2019 and very frustrated because the short battery lifetime. I must reload the handy twice on a day. I have brightness allready very low, and only facebook messanger and whatsapp on it...on stock rom the battery can handle 2 days of use without charging it. So my question is: is this lineageOS 16 release it better in battery consumption as lineage os15.1?

or should i use stockrom for best battery lifetime?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It sounds like your phone is not entering sleep. You should get better than stock battery life.

Install "better battery stats" (available on XDA) to work out what is keeping your phone awake.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
OK. i have now upgrade to the lastest LineageOS 16 release, and install also the better battery stats app...

over night, the battery drained 1,5%/h. But no programm shown,but many wakelock alarms with job.delay (over 180 over night) and ~92% deep sleep... hmm i spend more time to find out whats going on here
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I used to see around 1% an hour on standby so you are not far off.

Can upload screenshots from better battery stats? The most important statistic is how much deep sleep you get.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Hi. I didnt restore any system services and didnt disable any system services.

I will make clean install today and see if that helps me out.

Thanks for your time!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

I was testing out the "hand wave" to wake gesture just now (as an A5 user is reporting issues) and realised that it keeps all the sensors enabled when that setting is on (not just the proximity sensor). So you get the haptic feedback when hitting the cap touch buttons. Is this a setting you had enabled? Might explain reported the behaviour.

I will look into this.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sreekmtl:
My phone is vibrating when I touch the screen( when phone is locked ) Using the latest build. Is there any way to solve this issue .pls help
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Did you read the post above?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sreekmtl:
No, but now I turned off touch feedback in settings and this problem is no long. Does a fresh install solve this issue? Or I have to wait for next updation. During phone call also, the touch is working even if screen is off and it automatically turn speaker on or mute mic etc.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
can i send you a logfile?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
You are better of investigating the battery usage yourself with a tool like "better battery stats". If you are unsure how to read the info just run it for a day and then upload screenshots of the various information panes in the app.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
hmm i have here a logfile from over night:

http://s000.tinyupload.com/index.php?file_id=10011182141103982808
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
Okay, I did some Magic with adb and checked the numbers... Honestly: I'm Frustrated!

1. I got the following results for prox_cal:

cat /sys/class/sensors/proximity_sensor/prox_cal: 0,100,70

2. Neither Reseting nor Restarting the calibration process changes the values given in [1.]

3. Reading the raw_data:

cat /sys/class/sensors/proximity_sensor/raw_data: 255

, always. AIDA running or not.

So far the numbers. But they are odd or I miss something:

Assuming that the function "proximity_get_adc()" returns the value for [3.] I Don't understand the reading of 255.

The ADC outputs just one

byte

and "proximity_get_adc()" returns "ADC - "taos->pdata->prox_rawdata_trim" (which is 170).

Strange... at least for me.

Do you know where the logging data of the macro/function SENSOR_INFO(), SENSOR_ERR() goes?

I would love to get more details/Info of whats going on inside that phone. ;)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
The initial configuration/calibration is set in the device tree within the kernel (https://gitlab.com/Exynos7580/andro...4/boot/dts/exynos7580-a3xelte_eur_open_00.dts).

If you are getting 255 as raw values I would guess that there is dust/fluff in the sensor or it is faulty. I will double check the original dts from the kernel to ensure we have the correct values.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
I'm sorry and please don't get me wrong. But 255d / 0xffh because of dust?

254 would be OK for me ;)

Gesendet von meinem Mi 9 SE mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Hand wave setting is turned off. I need to check my battery stats if i can find something from there.

I didnt made clean install yet becouse lack of time. Maybe at next week but ill try to debug first.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Just uploaded a new release

Chnages in the 11/08/19 release:

More HWC improvements (thanks [MENTION=8184192]Stricted[/MENTION])

Added volume keys as a wakeup source (now visible in button settings)

August security patches​

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
one question: comes LineageOS with its own kernel, or can i flash a alternative kernel?

i think, i have bad modded kernel on my phone, so iam searching now for a better/stock kernel...but which should i use?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Has anyone else the effect that after dirty flash you get one hour lineage boot logo? Than boot into twrp? Or is it just me due to the flashed unifiedNLP? Wipe system and caches + flashing worked for me.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

This ROM has an optimised kernel, I do not know of any alternative kernel based on these sources so I would advise against using any other custom kernel with this ROM.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Shumafuk:
Thanks for this ROM. It works finally perfect and it is suitable for everyday use.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Hi. I didnt find anything with batterystats so i made clean install but that didnt help me out from AOD-symptoms. Menu&back buttons still make phone vibrate.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
i have heavily issues with mirophone on calls...when i call another person and speak with him - after ~1min my microphone is not working anymore (call-partner cant hear me, but i can hear him).

This is allmost everyone when i established a call...

is this a known issue?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Brummbude:
Not at all. Mic is perfectly fine never had issues with that.

Gesendet von meinem Mi 9 SE mit Tapatalk
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Hi [MENTION=6707196]danwood76[/MENTION],

Have you seen? There are monthly security updates running in stock firmware: https://www.sammobile.com/samsung/galaxy-a3-/firmware/SM-A310F/

Vendor patch level of your highly appreciated rom is February 1st. Do yo think yo can update blobs? Do you recommend to update baseband as well?

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

Although they publish updates the vendor security patch doesn't always get updated, most of the security changes they make are either software stack or kernel fixes that we already have included in our kernel.

The vendor security patch level is not really that important, the last update I checked (June) had no blob differences to what we use, I didn't actually check their reported patch level but I assume it was unchanged.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Thanks, Danny. I've seen reports about some really ugly bugs in proprietary Qualcomm code. So that's not the case with enoxys?

Did you also check for baseband updates? Any recommendations? I have A310FXXU4CRF1
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Don't worry, we have our fair share of nasty bugs on exynos devices :D. A prime example is the camera HAL, the wrapper I had to write to work around their bugs is rather large (but it works reliably).

The current state of the blobs is very good (no real issues), so I am reluctant to update them just because of a new Samsung release.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
I do have this issue too. Seems not for everybody.

Recently, some friend try to call me and it went to voice mail without any notice. No clue if linked or not. Got SMS of missed call. Strange.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
It looks like the screen is on even when im calling with my phone. Screen goes black when i put phone on my ear but all buttons is still activated. If my cheek touch screen it pressing buttons while call.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mr Curious:
I have inserted 32gb sd card but it shows 64 gb after i format it into internal sd card . It doesnt do anything but still is this normal
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
Same here with my Problem...Screen goes black when proximity Sensor detect my ear/head, but all touch Inputs still works and was not blocked...so Touch Inputs still possible when Screen Is black...Can you fix it?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Bug vanished with august update.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Is it a good quality SD card? There are a lot of cheap cards on the market that are not really the capacity they say they are. There are apps on the playstore that will verify an SD cards actual size, it's worth checking before you loose data.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mr Curious:
Its Samsung SD card class 10 ,if you format it as portable storage it shows 32 and if you format it as internal it comes to 64gb I have used other phones .it works normal.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] TimMayle:
Could it be possible that 64Gb is now simply your total internal storage?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Interesting. I will test this later.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Stricted:
its a general AOSP/Lineage bug

there was a patch merged a few days ago which should fix it, see https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/252493
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] exzemat:
Same problem here, with latest build.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

Debugging this issue I have found an issue with the A3 sensors labels in our SELinux policy. This would explain why the touchscreen is not getting disabled when the proximity sensor is covered and why you are still getting vibrations on the touchkeys when the display is off.

I am creating a new build now which I will upload later.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I just uploaded a new release, this should solve disabling the touchscreen during a call and other strange sensor behaviour we have been seeing.

I also pulled in the latest LOS changes which should solve the incorrect reporting of SD size issue.

Changes in the 16/08/19 release:
[INDENT]Fixed sensor SELinux policy
LOS updates[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
seems to be working fine, thank you :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I wonder if this issue was due to your ear muting the call because the touchscreen wasn't being disabled?

Can you report if the latest version fixes this call issue?

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] M249:
yes, error fixed in lastest version.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
Hi there,

Right now I'm on the 20190811 build (going to flash the lastest one in a second) and I still encounter the no-deep-sleep problem.

I've attached the BetterBatteryStats screenshots -- since unplugging I had not touched the phone for at least 2 hours, and I'd killed all the apps opened in the recent apps switcher just before leaving it idle.

PS I've just had the battery replaced and I want to fix this asap not to ruin this one now :|
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
I think this update fixed all my problems! Great work again, thank you Danny.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
I have just flashed the latest build and found out that the GPS barely works now. It seems like it returns the correct location to an app requesting such, but only once. It just doesn't update it afterwards. I've attached screenshots.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
[MENTION=8184192]Stricted[/MENTION] discovered an SELinux issue stopping GPS functioning correctly. I will upload a fixed build tomorrow.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Nothing obvious in those screenshots, however I suspect that if you click on the com.android.google.gms in the sensors pane that you will see that the significant motion sensor causing wakeups. 1.8/min could be enough to prevent deep sleep. Installing Greenify might help the issue (if you haven't got it already).

I did see something like this a long time ago on my test phone and I came to the conclusion that it was a corrupt Gapps installation.

When you update do you flash the latest OpenGapps as well? Because you don't need to and I think that might have caused my issues (gapps update from the play store so there is no need to load a fresh opengapps each time).

My only other suggestion would be to try a clean flash and see if that solves the issue, that fixed it on my test phone.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
I just uploaded a new update that fixes the GPS issue in the previous release.

Changes in the 18/08/19 release:
[INDENT]Fixed GPS SEPolicy (thanks @stricted)
[/INDENT]

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] witampanstwa_:
3 builds ago (since the 20190816) I did a clean install; I had then dirty flashed the 2 following ones without flashing gapps again. I will now clean install the latest one though and let you know how it goes aftwrwards

---------- Post added at 09:30 AM ---------- Previous post was at 08:44 AM ----------

I've also found the android's magnifier widget to be out of sync with the actual selected text by 1 character. I;ve just recorded this phenomenon: https://youtu.be/okjMxtk8qWU .
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Fa1Tra:
secure protocols problem?

Meanwhile, I thank Danny very much for his fantastic work! Thanks also to [MENTION=8184192]Stricted[/MENTION]! From version 20190811 on my a310f two apps no longer work (home banking and weople app) because they can no longer reach their servers (I believe with https or with other secure protocols). In your opinion, is it due to apps that do not comply with the security patches of August 1st or does LOS have a problem? Does anyone else have similar problems?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Hi,

So it finally happened, the hard work that [MENTION=8184192]Stricted[/MENTION] and I have put in has meant we are finally going official:

https://wiki.lineageos.org/devices/a3xelte

Official builds will start tonight and should be available tomorrow, you will not be able to dirty flash the official builds until you have flashed a migration zip that I need to create so please wait a couple of days for me to test the update path. You can always do a clean flash if you want to switch to the official branch sooner.

Best regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
[MENTION=6707196]danwood76[/MENTION] and [MENTION=8184192]Stricted[/MENTION]: Congratulations and thank you very much!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] thebinf:
I'm facing similar issues with the phone not entering deep sleep and nothing apparent from BBS. I clean flashed after HWC was introduced but I always flashed OpenGapps with the new builds. Please let me know if a new clean flash solved your issue.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Congratulations. And the microG fork has been built aswell:

https://download.lineage.microg.org/a3xelte/
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] fenekatomico:
Thank you very much!! Such a great new!! It will be a huge improvement for all of us!

So, I have two questions (sorry, I'm nerd about lineage)

1. What are the main differences between official and unofficial?

2. What are the differences between "dirty" and "clean" flash? What is better in this case?

Thanks a lot, guys!!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
There is not much difference. With the official builds you get faster security patches and ota updates.

A "dirty" flash means without wiping data/system before the update.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
To update to official from my relases:

Download the migration zip attached to this post.

Download the latest nightly: https://download.lineageos.org/a3xelte

Flash the migration zip and the official nightly in the same zip queue in TWRP.

Reboot, enjoy.

Regards,

Danny
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
Migration zip is working well! [MENTION=6707196]danwood76[/MENTION]: Time to update first post and the header :)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mobb_Deep73:
Just migrated successful.

First flash the migration zip, then the nightly build :).

Thanks again!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
That's great!

Unfortunately I've just had surgery on my right hand and can't really do much in terms of editing or coding at the moment :D
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] lawliet80:
Well, multiple fap might hurt your wrist XD
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] WSuijker:
Just did a dirty flash, first the migration.zip and than the latest nightly. Everything works fine! Thanks Danwood!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Somebod y:
Geht well soon!
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] Mobb_Deep73:
How is the wifi hotspot working for you guys? It looks like mine isn't working anymore.

I do get an IP address

I see my /etc/resolv.conf is adjusted

I can ping the nameserver

But it won't resolve any names
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] silokki:
Congratz for getting this ROM to official Lineage lines! I made dirty flash to latest with migrate patch and this works just as it should.

I got great battery performance and system stability with this ROM. Its nice to continue using this device.

Thank you Danny for great work!

---------- Post added at 11:25 AM ---------- Previous post was at 11:19 AM ----------

I can confirm this problem. I tried to connect my hotspot with galaxy x cover 4 and i cant browse at all. I think this is some kind of nameresolving problem cos i get IP.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
It looks like there have been some tethering changes recently in LOS, if I feel up to it I will have a go at fixing it later.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] yeye.phone:
Hello,

Thanks for lineageos for our A3. But why this is UNOFFICIAL release ? You update frequently it, it isn't possible to be official ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
Our device trees have just been accepted official. ;) Read a few posts back.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] yeye.phone:
So OTA update will work ?
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
OTA works, as soon as you have a NIGHTLY installed.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] danwood76:
[MENTION=2535901]Mobb_Deep73[/MENTION] and [MENTION=5394604]silokki[/MENTION] WiFi tethering should be fixed in the next OTA. ;)
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] yeye.phone:
Thnaks !

I found nightly on official site : https://download.lineageos.org/a3xelte

Must i do a clean install or can i do an simply flash update twrp with wipe cache & dalvik ?

Best regards
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Read 15 posts above. There is a migration ZIP.
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] yeye.phone:
Oh !! thanks... i 'm lazy boy....
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] sstassin:
Hi everybody

Does anyone have the same problem than me ??

Using the download link on the first post... i am redirected to the A5 roms ??
[Galaxy A3, A5, A7, A8, A9 Original Android Develop] kurtn:
Latest official links to a3xelte