yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] jt12345:
NFC

[MENTION=6880495]HardStyl3r[/MENTION] I've just clean installed lineage-15.1-20190424-nightly-d855 and it's working beautifully - thank you.

I have noticed, however, that NFC isn't working at all. I found the following comment you made in a post on 4th December 2018:

I presume that means that the D855 does *not* have "full NFC HAL support". Do you know whether this is likely to change?

Many thanks, Jaime

Update: I've just found this. I've included a link to this issue, because (apparently) the S5 has the same NFC chip as the D855 (an NXP PN547) and that issue is now closed as resolved.
[G3 Android Development] Juraj_v:
On my D855 NFC works flawlessly from the software point of view. The only issue I have is that my back cover has many mounting spots broken off and doesn't quiet make contact with NFC antenna, which is part of the back cover, so I have to hold it in place wile using NFC.
[G3 Android Development] jt12345:
[MENTION=9828438]Juraj_v[/MENTION] Thank you letting me know. I am going to have to dig a bit deeper with this - I'll update this thread when I have more info. Thank again, J
[G3 Android Development] jt12345:
[MENTION=9828438]Juraj_v[/MENTION] Ok, I've tried again, but I can't get any sign of life out of the NFC subsystem on my phone. On my wife's LG G5, I can use "NFC Reader" (se.anyro.nfc_reader) to scan my NFC Metro (TFL Oyster) card and her phone successfully "sees" the card. I've tried the same setup on my G3 (d885) but it doesn't see the card. I've also tried using Android Beam between the 2 phones, and they can't see each other.

Stuck to the inside the back cover I can see what appears to be an antenna/aerial which terminates at 2 copper contact pads. These seem to align with 2 of the 4 copper spring terminals near the top left corner of the battery. I assume that the other 2 spring terminals stay unconnected - does this appear to be the same as your hardware? I've also just seen this youtube video about G3 back covers, NFC antennas and reading problems. My back cover (for my D855) appears to be identical to the back cover that the guy in the video says is for his D851 - my back cover does not appear to be the same as the cover that the guy in the video describes as the "D855 European model back cover". I've also just checked ebay, and *most* of the UK/European D855 back cover advertised have 4 contact pins. I'm starting to think that the (second-hand) phone that I bought does not have the correct back-cover/NFC antenna!

Does anyone else have any positive or negative results trying to use NFC? What's your phone model, and does your NFC antenna have 2 or 4 contact pads? Any success or failure stories would be a great help. Thanks!
[G3 Android Development] Juraj_v:
As I said all things you mention work. I regularly use Google Pay for mobile payments, I've tried android beam - succesful, I've tried to scan some of my NFC cards with "NFC reader" app, all working.

I have the version with 4 contact pads. As mentioned in the YT video you posted, those extra pads should be for wireless charging (not sure if mine works since i don't use it). I've tried covering the two bottom pads with a piece of electrical tape and again NFC reader succesfuly read my card for public transport, so i wouldn't think that those missing pads are the problem, but who knows...

I don't know if it might be a problem or not but first version i've installed was 15.1 from 10th of March, then i've regulary updated to current version (1st of may).
[G3 Android Development] Danilo_94:
Bluetooth callings are disturbed, any solution? D855, last lineage 15
[G3 Android Development] jt12345:
Thank you for trying to help.

I originally thought that the only thing stuck inside the back cover was an antenna. Both an ebay advert (#283438284674) for that "part" and the end of the explanation given by that guy in the youtube video make me think that there is also a chip encased with the antenna. I think we (both myself and the guy in the video) have the same problem, but our problems are "going in different directions":

He has a D851: his 4-pad/D855 cover doesn't scan but his 2-pad/D851 cover does, whereas...

I have a D855: my 2-pad/D851(?) cover doesn't scan, but hopefully a 4-pad/D855 cover will!

That's the only way that I can explain why the guy in the video couldn't scan tags while using the D855 cover. I'll buy a 4-pad/D855 cover and let you know the result. For the time being, I'm hopeful!
[G3 Android Development] Ph3ar.:
The extra two unused pads on the G3 is for wireless charging . The G3 comes standard with a back only having two contacts for NFC . You can buy a replacement back with 4 contacts but all that's going to give you is the ability to charge the phone by placing it on a wireless charger . The AT&T model uses a different charging protocol for charging than the other variants so make sure you get the right one for your phone . A back with 4 contacts for a sprint phone for example will fit your att but will not charge it and vice versa , a back for the att will not charge the sprint phone . The extra two contacts have nothing to do with NFC .
[G3 Android Development] oile:
Clean flashed latest lineage os 15.1, first bug encountered:

Kernel is limiting charging current to 500/600 mA causing the battery to be charged in 3 hours.

Anyone else experiencing this?

It seems a very good Rom anyway so thank to the maintener
[G3 Android Development] Ph3ar.:
Not on the LS990 Sprint variant . Charges nice and fast for me .State what variant your using .
[G3 Android Development] Metin59:
Getting error

My phone D855

Rom lineage-15.1-20190501-nightly-d855-signed.zip

com.qualcomm.shutdownlistener stopped

and no sim card :/

Is there a solution?
[G3 Android Development] Rob...:
which android did you have before that? Android version! it could be the modem, radio firmware.

what is your baseband?
[G3 Android Development] Metin59:
cloudy g3 2.5 I used

had no problems
[G3 Android Development] Rob...:
it is only a guess, try to update radio firmware. 21C should be the right one.

https://xdaforums.com/lg-g3/general/radio-modem-lg-g3-t3110376
[G3 Android Development] oile:
D855 16gb no brand
[G3 Android Development] Metin59:
thanks man worked :)

sim card came
[G3 Android Development] oddcow:
I've noticed mine does seem slower to charge compared to stock marshmallow, but I'm not sure about the actual current/time. D850 AT&T here.

Also, does anyone know if it's possible to increase the vibration strength? I use it mainly for alarms/timers and it seems significantly weaker than the stock marshmallow.
[G3 Android Development] jt12345:
NFC problem solved!

The (4-contact) D855 cover arrived today, and it works perfectly!

I think you might be referring to USA models. I'm pretty certain the "International" ("European"?) model, the D855, comes as standard with a 4-contact cover.

My phone isn't an AT&T D850 - it's the "International" ("European"?) model, the D855. (Incidentally, I don't care about QI Wireless charging - I just want "working" NFC.)

I agree that the extra 2 contacts have nothing *electrical* to do with NFC, but I now believe that the number of contacts might be *indicative* of which G3 models the back cover is "NFC-compatible" with. The "experimental observations" are:

From the youtube video: D851 (T-Mobile G3): D851 cover (2-contact) compatible, D855 cover (4-contact) incompatible

From my experience: D855 (Int/Euro G3): D855 cover (4-contact) compatible, D851? cover (2-contact) incompatible

If I look at the observations and "ignore" the model numbers for the covers, these observations become:

From the youtube video: D851 (T-Mobile G3): 2-contact cover compatible, 4-contact cover incompatible

From my experience: D855 (Int/Euro G3): 4-contact cover compatible, 2-contact cover incompatible

Please bear with me here - my last days as an experimental physicist were at least 30 years ago!
[G3 Android Development] cracker12:
Is there any gcam port that works on lineage 15 or 16?
[G3 Android Development] HardStyl3r:
It's still distorted on d851, f400, g3ds and ls990. There is no known fix yet.

The NFC support is present on the software side. You need to check your back cover.
[G3 Android Development] samcoinc:
How do you do this? I don't have the screen resolution menu option in the display settings.

I am also running 16 - came from a samsung s5 (same proccessor) and the samsung ran smoother with 16.

thanks
[G3 Android Development] entaled:
My D851 and all the back covers I have are 4-contact and support both NFC and Qi wireless charging. Some models like the D850 use PMA instead of Qi so some back covers are not compatible with others.
[G3 Android Development] jt12345:
Done and fixed!

Brilliant ROM, BTW - thank you! :good:
[G3 Android Development] sergialess:
I'm probably wrong but I think GCam requires Camera2 API (HAL3) which is not implemented in our G3's (and never will be).
[G3 Android Development] jt12345:
No GPS fix

I'm running 15.1 20190424 and I've just discovered that I can't get a GPS fix. Before I reflash stock ("No! Don't do it!") or start taking this thing apart, could anyone running 15.1 20190424 or later please tell me whether or not you can get a GPS fix? Thank you!
[G3 Android Development] downloads_bg:
My phone often restarts when I turn 4G on, or open Google Maps (every time), or launch app when 4G is on.

It restarts and then battery drops drastically. And it restarts until I have to take the battery off.
[G3 Android Development] DrFlaisch:
GPS didn't work for me at all on LOS 15.1. If I used Google Maps and I somehow got a GPS Signal after a while, Maps wasn't able to relocate my position while I was moving. Ist got stuck this way permanently.

I recently did a hardware fix and flashed LOS 16.0 and now GPS and Maps run just fine.

This symptomatic sounds like my D855 which restarted all the time and after a while got more and more often stuck in a bootloop. In my case this was caused by a very common issue: The soldering connection of the chipset (especially CPU and Flash memory) and the phones mainboard gets lose by time. I could fix it by using a hair dryer and blowing hot air onto two chips of the mainboard. Obviously one needs to disassemble the device for this procedure. My LG is running fine now for 3 days without any problems except losing network signal from time to time which I can't explain yet. But maybe one of you guys can?

To solve the solder issue just punch "d855 solder" into Youtube search. There are a few guides how to fix it.
[G3 Android Development] ParsaMrrelax:
is there anything i should do when coming from stock android 6.0?
[G3 Android Development] MaverickNextDoor:
Your battery may be the culprit. I bought a replacement battery and had it randomly rebooting my device in a bootloop. Original battery has no such issues.
[G3 Android Development] samcoinc:
Found a solution that worked for me

https://xdaforums.com/showpost.php?p=63387158&postcount=150

Thanks

Sam
[G3 Android Development] jt12345:
(No) GPS on 15.1?

So I guess that means that the fix could *either* have been the "hardware fix" *or* the move from 15.1 to 16.0.

Does *anyone* have GPS working on 15.1?
[G3 Android Development] DrFlaisch:
Yes, you're right, I can't really say what brought the GPS to work, if it was the heating of the chipset or moving from 15.1 to 16.0. But since my girlfriend noticed the same GPS issue on her D855 which ran 15.1 and the problems were gone when she moved to 16.0, I think it might be a software related thing. I did the hair dryer fix because of constant crashes and bootlooping caused by LGs poor solder connections and that worked for me :)
[G3 Android Development] xxStingrayxx:
Hidden SSID WiFI

Hi, I have a plea

I use D855 for a lot of years. I using it from cyanogenmod 11 to lineage OS 15.1, and is it still good phone. But in the work or home is hidden WiFi, and after every official 15.1 update a must flash custom kernel as xtd, because with a stock I can´t connect. Please Can you fix it in official builts?

Thank you
[G3 Android Development] astrod:
GPS works very well on my D851 with 15.1.
[G3 Android Development] jt12345:
Ok, so it might be a software bug that is present in 15.1 but not in 16.0.

Ah, now that is interesting. Could you please tell me the build date/filename for your ROM? (Settings/System/"About phone"/"LineageOS version") Thank you!

Is there

anyone

else out there who is still running 15.1? Does your ("internal") GPS work? If your GPS does work, what's your ROM's build-date and phone model (D850/D851/D855/etc)?

:)
[G3 Android Development] L1p1c1:
on d855 i can confirm that is sworking very well. if nobody is saying that is working very well on d855 that dosent mean im right..

the same way for your vwesion
[G3 Android Development] astrod:
I'm on the D851 nightly from 20190429. Not sure if it matters but I have gapps installed and use SatStat which has always been helpful on many different phones for helping to acquire GPS position. I should note that when I set GPS to 'device only' it is a lot slower to acquire accurate position.

---------- Post added at 04:57 AM ---------- Previous post was at 04:54 AM ----------

What are people doing to maximize battery performance on 15.1? I'd like to use my D851 as my daily driver but the battery will simply not last more than a few hours with regular use. I'm even using a new battery that I recently got on ebay. Thanks for any pointers!
[G3 Android Development] jt12345:
(Thank you for the GPS info - I'll reply to it in a separate post) Re your battery usage "problem", my D855 on 15.1-20190424 will run a whole day on one battery.

A few things to mention:

linux's "cpu frequency scaling" is a big factor in power consumption, so I use (open source) "CPU Stats" with the settings set to show "cpu frequency" and the "update interval" set to 1 second to make sure that the cpu frequency scaling driver is working correctly and that there aren't any processes holding the frequency high. If I close my browser and wait a couple of seconds, then I can see that the cpu frequency has dropped to "0.3" (GHz). An alternative approach to monitoring the "cpu frequency scaling" is to install termux and then (from the command prompt) type:

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

On my phone, this shows:

300000 3887483

422400 89645

652800 271377

729600 28858

883200 84094

960000 12944

1036800 104156

1190400 118135

1267200 48360

1497600 376759

1574400 233766

1728000 14171

1958400 840

2265600 20560

2457600 166651

The first column is the frequency and the second column is the time at that frequency, so you can see here that my phone has spent 71% of the time (=3887483/(sum of all the times) =3887483/5457799) at its slowest frequency, 0.3GHz (300000KHz) so this tells me that cpu frequency scaling is working correctly. If you think that your cpu frequency scaling is working correctly, then I'd suggest checking that your battery is OK. Over the past ten years I have bought dozens of phone batteries from ebay, but only 1 of them was genuine. That means that the stated capacity (written on the label) means absolutely nothing. I bought one of these ZB206 battery capacity measuring devices from ebay and I use it to check the *real* capacity of all my rechargeable batteries (phone batteries, 18650s, NiMH, etc). The ZB206 tells me that my three batteries (for my G3) have *real* capacities of:

Batt1: 2657mAh/3000mAh = 89%

Batt2: 2353mAh/3000mAh = 78%

Batt3: 2719mAh/3000mAh = 91%

(All three batteries have stated label capacities of 3000mAh) Guess which of my three batteries was a "new" battery bought from ebay! :laugh: Ha ha!

Hope this helps, J

---------- Post added at 09:10 AM ---------- Previous post was at 08:34 AM ----------

[MENTION=7652221]L1p1c1[/MENTION] Could you please tell me what your "Location mode" is? You can find this by going to "Settings", then "Security & privacy", then "Location" and it is then the 2nd entry down. Mine says:

"Mode: Device only" - this means use *only* the GPS chip to find the phone's location

The other possibilities are:

"Mode: High accuracy" (this is no good to me as I am trying to test *only* the GPS chip)

"Mode: Battery saving" (this is no good to me either, as this mode does not use the GPS chip)

What "Location mode" is your phone using? Thank you. :)
[G3 Android Development] Ph3ar.:
APN

[MENTION=6880495]HardStyl3r[/MENTION] , Is there any chance an apn menu could be added to Lineage 16 so I can edit the apn for for my carrier which is Tello for the LS990 ? I could edit it in 15.1 and get LTE . This morning I went from Lineage 15.1 to 16 via a clean flash . I'm unable to get any data 3G or LTE and can't find an apn menu anywhere . If I could get my apn's setting incorporated into the build or have the ability to edit apn's I could make this work . Tello is just an MVNO like Ting , Twigby etc . Sure hope we can get this into Pie like it is in Oreo . Thanks .
[G3 Android Development] Ute60:
Found this. Tello apn fix zip. Worked on my tablet. Havent tried it on a phone yet.

https://www.imfiles.com/topic/tello-apn-fix-lineageos-14-15-15-1-and-16/
[G3 Android Development] HardStyl3r:
Hmm, strange. I don't know what's wrong.

[MENTION=2709988]jt12345[/MENTION] do other sensors work?
[G3 Android Development] L1p1c1:
[MENTION=7652221]L1p1c1[/MENTION] Could you please tell me what your "Location mode" is? You can find this by going to "Settings", then "Security & privacy", then "Location" and it is then the 2nd entry down. Mine says:

"Mode: Device only" - this means use *only* the GPS chip to find the phone's location

The other possibilities are:

"Mode: High accuracy" (this is no good to me as I am trying to test *only* the GPS chip)

"Mode: Battery saving" (this is no good to me either, as this mode does not use the GPS chip)

What "Location mode" is your phone using? Thank you. :)[/QUOTE]

sorry bro, i moved on lineage 16, on lineage 15.1 only one time i had a problem and was resolved at next update, on battery saving and device only never worked, not even when i buyed the phone new /stock rom

on lineage 16 location worked on all version besides the last one , april update, its not working, no lock on location.

L.E: sorry, forgot to allow location from gogle play services, when im not using maps or other service that i need location i turn it off from there.
[G3 Android Development] HardStyl3r:
The battery in my G3 turned out to be a balloon, so I am not quite sure whether should I charge it or not. My phone doesn't work with stock batteries anymore and only the Greencell replacements are working and they're currently out of my range. So, the May update will be built, but only the LineageOS 16.0 on d855 will be tested, and not by me. If it turns out something's broken in the new release, please report it and if it's really bad, you may switch back.

Sorry to let you down.
[G3 Android Development] Ph3ar.:
Thanks , this worked and 3g, LTE working now .
[G3 Android Development] santaIwantMi8SeForXmas:
G3 D855 32gb - april version clean install [MENTION=6880495]HardStyl3r[/MENTION] after phone call (definitely after missed one) sound profile automatically changes from vibration to sound enabled one, could you please look up into that? And i think that even after i change back to vibration, it reverts to sound on profile if i dont clean the missed call notification.

And from other things - I noticed that wifi speed drops heavy after some time and i have to reboot phone to make it work fast again (on really stable WIFI from like 4MB/s to 150 kbps)
[G3 Android Development] UmutKaynar:
May update When?
[G3 Android Development] marcdw:
#1. ETAs are a no-no.

#2. Look up/back a few posts and you'll see a note from the dev that may answer your question.

Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
[G3 Android Development] TheFieryBreeze:
I'm on 15.1 microG build

I tried device only with OsmAnd~ and it didn't work

Explains why i could never get an accurate fix when I was in Germany, since my carrier didn't give me any mobile network connection, only crappy appproximates, like being deep in the nearby sea hahaha

Very problematic, happy to know it works in 16.0, going to eagerly wait for the official release!
[G3 Android Development] walter79:
ATA 24.12.2042

Don t ask for ata.
[G3 Android Development] UmutKaynar:
How was the April update
[G3 Android Development] UmutKaynar:
Sory bro translate is dead :silly:
[G3 Android Development] qwertyu123:
Question for g3 users

Does Google Duo calls between Android (g3 in this case) and Apple IPhone work on lineage 16 on the LG G3?

In case of LG G2 there is no problem on Iphone side (video and audio works) but on G2 side only audio works, and the image is stuck in blackscreen with a loading circle.

It looks g2 has AVC decoder problems, and I would like to know if you have the same situation on lg G3.

Thanks !
[G3 Android Development] HardStyl3r:
Hey, May update is finally here!

Sorry for the late update, I have much less time for development than I used to, so future updates might also come late.

Also, there is new issue tracker, which is a must-go-to when you are reporting an issue. This really helps organizing the issues.

XDA threads will remain a more community-aimed thing.
[G3 Android Development] Shred00:
Should provide a link to where it is.
[G3 Android Development] Zirila:
GPS fix problems

I've got problems with GPS. I use the latest microg lineageos 15.1 on this d855 phone and I'm struggling hard with GPS issues.

First thing is that it takes ages to get a GPS lock. The other thing is, when I use a navigation app, the GPS position is always a bit off and it constantly loses a GPS lock, therefor recalculating routes indefinitely.

I use device-only-gps. If I'm outside under clear sky it takes about 10-15min to get a GPS lock if i'm lucky. And it loses the lock constantly while navigating.

I've already tried various fixes and things:

- I opened the phone and cleaned the gps contact pins, also bend them a bit to make a better contact possible. the hardware is working, I see satelites and it's locking them, it just takes ages.

- I also tried high accuracy gps,

- I reset AGPS data

- I edited /system/etc/gps.conf

..... edited working NTP servers and

......edited new XTRA-SERVER's (the izatcloud xtra3grc.bin)

......edited CAPABILITIES=0x31 (from 0x33 which should fix the reset of the lock all the time, but didn't)

- I activated all the UnifiedNlp gps settings.

- I tried different GPS and Navi apps and support-apps.

nothing really helped fixing the issues. I'm out of ideas.

Is anybody else having these issues with LG G3 and lineageOS? I remember it used to work a bit more reliable in previous ROMs (original and aosp).
[G3 Android Development] marcdw:
Should check the OP. That's where the link is.

Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
[G3 Android Development] newbuss:
I just started having this problem too on one of my 2 D852s. I tried all Pie ROMs, XTD kernal, and even tried Fulmics. Tried with stock camera, Google camera legacy, Open Camera and Footej camera.

Anyone else having this issue?

Thanks!!
[G3 Android Development] cracker12:
Hi, since dev is the same for almost all what is the most sable and battery friendly pie rom? Opinion are welcome
[G3 Android Development] qwertyu123:
Anyone with a g3 can make the test?
[G3 Android Development] mksahin:
I haven't been using my G3 actively any more and I haven't tried all available ROMs extensively. But from my brief testing of all these ROMs, Pixel Experience seems the most stable and fluid. Probably because it has fewest customization options and Google apps are already integrated (no need to flash Gapps separately). Pixel experience also seems to boot up fastest. In terms of battery friendliness, I have no idea. But, I guess they would be similar.

I would love to hear other opinions as well.
[G3 Android Development] HardStyl3r:
what about Pie?