yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] florianh78:
Bluetooth crash issue: Steps to reproduce below

Thanks [MENTION=10210919]CV8R[/MENTION] and [MENTION=6880495]HardStyl3r[/MENTION] for looking into this. Now I'm back with detailed steps on how to reproduce the "Bluetooth app crashing" issue. I don't know enough about the architecture, but to me it looks as if some Bluetooth related bits may be stored in a wrong place, thus get deleted upon wiping, and won't be recreated afterwards, leading to a crash.

Please find below a description of what I've done since my last post on this topic and how I could reproduce the issue:

Ordered a used D855 phone in good shape, it came with the latest official LG Marshmallow ROM

:good: Did intensive testing of the hardware, in particular Bluetooth tested thoroughly with several devices, all worked fine

Rooted and flashed TWRP (latest by Hardstyler) and CleanROM 3.2 according to https://xdaforums.com/lg-g3/general/guide-how-to-root-v30n-twrp-install-t3889628

:good: all worked fine, Bluetooth tested thoroughly

Flashed LineageOS 20191106 incl. SuperSU and OpenGApps Pico

:good: all worked fine, Bluetooth tested thoroughly

Encrypted phone using the functionality LineageOS offers

:good: all worked fine, Bluetooth tested thoroughly

Reset the phone via TWRP by wiping Cache, Dalvik, and Data

:eek: Bluetooth app crashes immediately upon initial boot

Reset the phone via TWRP by wiping Cache, Dalvik, Data, and Internal Storage

:eek: Same behaviour, i.e. still crashes

I didn't continue further, so I'm available for executing any further steps in order to help fixing this issue.

Kind regards

Florian
[G3 Android Development] mbr2019:
My D855 runs LOS 16 fine. I just tried LOS 17 on my D855. I shows "Bluetooth keeps stopping" messages every few seconds after a plain install (not even gapps installed) even if I disable bluetooth.
[G3 Android Development] HardStyl3r:
I'd like some logs, so I can investigate the issue more. Thank you for the work done.
[G3 Android Development] florianh78:
Logs

OK, I've wiped also System, and flashed LOS, SuperSU, and OpenGApps again, and the error persists.

Here are the Logs: https://www.holeczek.de/d855-blueto...bluetooth-issue-logcat-after-initial-boot.log

If I can help with anything else, just tell me.
[G3 Android Development] HardStyl3r:
Issue found, should be fixed in next release. Thank you!
[G3 Android Development] mbr2019:
Bluetooth crash on LOS 17

I've captured a logcat showing the bluetooth problem on LOS 17: https:// pastebin.com / QHanq4D4

Regards,

mbr2019

---------- Post added at 02:20 AM ---------- Previous post was at 01:51 AM ----------

Digging deeper shows /data/misc/bluetooth/bdaddr missing and running /system/vendor/bin/hwaddrs results in a SEGV.

strace is here: https:// pastebin.com / aU1xntt8
[G3 Android Development] florianh78:
Oh, great, thanks! I've just tested it with 20191107 and 20191108, not sure what's going on though.

On my current productive device, the update to 20191107 fixed the issue (using the LineageOS Updater). On my second device, neither 20191107 nor 20191108 were fixing the issue - both I've flashed via TWRP after a complete wipe.

Any idea?
[G3 Android Development] florianh78:
[MENTION=6880495]HardStyl3r[/MENTION] Still happening also with LineageOS 16 2019-11-13 on my completely emtpy D855 3 GB device, new logs here: https://www.holeczek.de/d855-blueto...ssue-logcat-after-initial-boot_2019-11-13.log
[G3 Android Development] HardStyl3r:
[MENTION=9679169]florianh78[/MENTION]

The Bluetooth will be fixed in the next release of 17.0. I am working on it, but having some problems.
[G3 Android Development] florianh78:
OK, just to prevent from misunderstandings: My reports are related to 16.0, and the ones of [MENTION=10284495]mbr2019[/MENTION] are related to 17.0.
[G3 Android Development] florianh78:
Hi HardStyl3r,

I've just updated my D855 to lineage-17.0-20191028-UNOFFICIAL-d855 and experience the issue of after entering the correct password of the encrypted data partition, a message appears (in my case in German) saying something like "error in encryption", "The password entered is correct, but data is corrupted. In order to continue, you need to reset the device to the factory settings".

Kind regards

Florian

---------- Post added at 04:39 PM ---------- Previous post was at 04:21 PM ----------

[MENTION=6880495]HardStyl3r[/MENTION]

Adding some more LOS 17.0 observances:

Two D855 (one with LOS 16.0, one with LOS 17.0), seem to connect but then immediately disconnect again. No idea though if that is normal - I just thought that one could directly transfer files like that, never been doing that before though.

Connecting to and using some Bluetooth speaker (Rokono B10) is working with both, however, compared to LOS 16.0, the feature "HD Audio" seems to be missing in LOS 17.0.
[G3 Android Development] HardStyl3r:
Encryption will fail on 17.0.
[G3 Android Development] eric93se:
Latest LOS16 build 11/15 fixes the crazy cpu usage and heat generated. I don't know when that issue began because I had been using XTD kernel. I still have to use kernel Aduitor to tame the cpu more. Wish we had more tweaks in this kernel especially better thermal throttle control.
[G3 Android Development] xytkhi:
ho all: What is the best kernel for my d855 phone that can save battery and radius cpu heat?

- also Bluetooth crash problem,, what to do to fix it pls ?
[G3 Android Development] Daniel MH:
First of all, I'd like to thank HardStyl3r for his hard work. The LG G3 community should be really grateful.

I've been using LineageOS 16 official in my LG G3 since it came out and I haven't experienced any issues... at least until last week.

I was using the latest build with TWRP, GApps and Magisk installed, everything was working properly. When I was updating the apps via Play Store, my phone suddenly rebooted and entered bootloop, with no reason.

I've tried doing a clean installation multiple times, even wiping internal storage. LineageOS 16, 17 and Pixel Experience 9.0 don't boot at all.

I've also tried installing some stock ROMs and the result was... unexpected. The phone boots normally with Lollipop and Marshmallow versions, but Wi-Fi can't be activated. Everything else seems to work.

I haven't found a way to make LineageOS 16 boot again and I don't know what else to do. Any ideas? Help would be really appreciated.
[G3 Android Development] waratwoeld:
they look like symptoms of hardware failure
[G3 Android Development] eric93se:
You could try to KDZ back to stock but sounds like hardware failure.
[G3 Android Development] moriel5:
Has anyone else seen this odd bug with LOS16 and LOS16-based ROMs that the ROM just restarts and bootloops, with no apparant reason, and the only (temporary) solution is to reinstall the ROM?

My friend's MI A2 Lite has had this happen to it on both LOS16 and ResurrectionRemix7.0.2 (multiple times), and I had thought that it may have something to do with one of the partitions having gotten corrupted, however it has now happened to me multiple times on my LG G3 (D855) (I haven't moved to it yet from my Nexus 4, not enough time, and my G3 is the guinea pig, before my parents' G3s are prepared).

Repairing and formatting the partitions do not resolve the issue, only reinstalling the ROM, and even that is only a temporary workaround.

Additionally, for some odd reason there are issues with the LOS root addon (partially working on LOS16, not working at all on LOS16-based ROMs).

I'm pretty much at a loss at what to do, since as awesome as Magisk is, it's not really what I need (I need to be able to directly modify the /system partition).
[G3 Android Development] florianh78:
Hi, I've seen this once with a Samsung Galaxy Note 10.1, and the reason was that the flash memory (eMMC) was broken. These components wear out, so in case there's heavy I/O on the phone (e.g. because of using it like a USB stick), there's a probability of running into that issue sooner.
[G3 Android Development] HardStyl3r:
This sounds like a hardware failure.
[G3 Android Development] moriel5:
That makes sense, however my friend's Mi A2 Lite is brand new, and this issue does not occour on stock.

Again, that would make sense, however there are no issues whatsoever on stock, nor LOS 14.1 (don't have the last LOS 15 to check there), so I'm pretty sure that the hardware is fine, plus it is refurbished by LG themeselves.
[G3 Android Development] florianh78:
Oh OK, then it would probably be good to provide some logs as described in one of the first posts of this thread.
[G3 Android Development] moriel5:
Thanks, I hadn't yet posted logs because I first wanted to know if anyone else had also encountered this issue, however I'll do so when I'll have time (I was at home earlier, which is why I had a bit more time for this).

As for my friend's Mi A2 Lite, that will have to wait until I meet him again, towards the end of next week.
[G3 Android Development] evotech:
Can confirm this bluetooth error on a clean install of lineage-16.0-20191123
[G3 Android Development] HardStyl3r:
For those who had any issues (Bluetooth, dualsim etc), please try latest LineageOS 17.0 builds. Now is the time to report issues.
[G3 Android Development] waratwoeld:
Beta yeah!, Great my friend, installing, testing and uploading logs-

thanks!!
[G3 Android Development] Šəmûʼēl:
LG D856 (dualsim) - wifi, bluetooth are normal.

But both SIMs are absent in system at all. There are no icons of signal level, looks like sims are not inserted.

Logs are attached
[G3 Android Development] HardStyl3r:
Please check if you have "persist.radio.multisim.config=dsda" in build.prop and which model is reported in Settings.
[G3 Android Development] Šəmûʼēl:
Build.prop is correct

Model in system menu: g3ds
[G3 Android Development] waratwoeld:
D855

The state testing the latest compilation of Lineage OS 17 has greatly improved in many aspects.

- The Radio application is already working and it works well

- Temperature and battery go very well, as in official Lineage 16

- The camera error when opening it was black and when taking the first photo it returned to normal with the camera display, solved.

- Native SMS, working.

- Notifications very well,

- Bluetooth running

mistakes i found

- Battery and icon percentage cannot be modified yet

- When changing the clock style in settings / screen / styles and wallpapers, two clocks appear I don't know if it's normal, better leave it in default.

- Record the screen, freeze the phone

- Format for recording the call appears in the call application, but the option of recording call when calling is not displayed.

- Automatic brightness always appears at more than 50% in dark places

- Native keyboard, does not allow gestural writing

camera does not save in SD

--------------------------------------------------------------------------------------------------

update 03/12

I found these mistakes

- sometimes when charging in off mode, the charging battery icon freezes and the screen stays on

- Randomly shutting down the device, it has happened to me a few times since installation, three times to be exact between 100% load and 89%

--------------------------------------------------------------------------------------------------

installation

lineage-17.0-20191122-UNOFFICIAL-d855

BiTGApps-arm-10.0.0-v0.5-SW_signed.zip

Magisk-v20.0

Thank you for this great job, I hope my contribution serves
[G3 Android Development] sylveon cheung:
i flashed g3 d858hk with g3ds ver zip ,the system boots up ! but the sim card wont read , and imei lost ,any way to get back my imei and simcard work ?
[G3 Android Development] eric93se:
Where did Dialer.apk go in LOS17? Anyone know?
[G3 Android Development] Onyxsolo:
For me the LOS 17.0 build for LS990 models reboots almost immediately and goes back into recovery after loading the OS. I'm far from pro when it comes to android/linux but 15.1 and 16.0 have loaded fine for me. Currently I still prefer 15.1 because of app support and stability(BT call speaker quality sucks though).

I did wipe partitions and tried clearing the dalvik/cache after installing the "lineage-17.0-20191124-UNOFFICIAL-ls990.zip" build with no success.
[G3 Android Development] L1p1c1:
im using latest build with BiTGApps-arm-10.0.0-v0.5-SW_signed.zip (the beta ones says im using android 6.0.1) and magisk 20.1

For D855 i add to the list:

-unblocking the phone using pattern takes 30 seconds, need to use it like 3-4 times after turning on the phone or restarting

-gps not finding satelites, not working, tested with 3 different aps

-default phone app cant be disabled anymnore like in lineage 16 if you install another 3rd phone app (both will register calls )

-same as previous lineage versions, bug with battery still persists, battery goes from 100 % to 80 in 2-3 minutes, after that drains normal.

-captions not working

-activating new android 10 gestures blocking the phone using home button dosent work anymore. i dont think is suposed to work, only works in 2 buttons gesture

-shows wrong SOT, used phone for 1 hours, shows 2:10 , after i have more than 2:10 the SOT changes

-when you wanna change notification sound via sounds app dosent change, dosent oppen (i think is because of the permissions , but then again is a bug because dosen ask to give permission to read data)

-for people who got scared because they lost trust , its there but its better and its called permissions manager and blocks by default all permissions, in pie you needed to turn off permissions for every app in phone, took me like 20 minutes to do that

-photos from camera are saved on memory card on wrong location (android>data>>org.lineageos.snap)
[G3 Android Development] fOxunO:
Try on off location
[G3 Android Development] L1p1c1:
dosent work , you find this as a soluton on internet, change between high accuracy, only gps , then restart phone

tried fixing modules from magisk, same thing
[G3 Android Development] vibraniumdroid:
Turns off on boot

On the LS990 here.

Clean flashed the rom with gapps and magisk and it just powers off when booted
[G3 Android Development] vibraniumdroid:
Anyone have the same problem?
[G3 Android Development] L1p1c1:
at me random reboots while changing luminuosity and then bootloops, dirty flashing dosent resolve the problem, needs new install
[G3 Android Development] walter79:
LOS 16: (d855)

5 GHz wifi is unstable, random disconnect

("Allow wireless channels with 160-MHz channel bandwidth" is enabled)

Edit: It seems 160 Mhz channel bandwidth seems to be the problem.

no Problems with 2.4 GHz only network

log:

[ 932.587577] 622,932587577;rmnet0: no IPv6 routers present
[ 953.670333] 623,953670333;[09:29:46.335957] [000000044C16AA6D] [wific] wlan: [E :HDD] wlan_hdd_get_frame_logs: Frame Logging not init!
[ 953.689946] 624,953689946;wlan: [10968:E :CTL] Error returned WDI_ProcessInitScanRspi:0 BMPS0
[ 956.482609] 625,956482609;[09:29:49.148201] [000000044F4E90ED] [wpa_s] wlan: [E :HDD] wlan_hdd_cfg80211_set_ie Set UNKNOWN IE 3B
[ 956.483185] 626,956483185;[09:29:49.148821] [000000044F4EBF35] [wpa_s] wlan: [E :HDD] wlan_hdd_get_frame_logs: Frame Logging not init!
[ 956.559712] 627,956559712;[09:29:49.225342] [000000044F652A53] [MC_Th] wlan: [E :PE ] limProcessAssocRspFrame: 472: Filling tdls prohibited in session entry
[ 956.615538] 628,956615538;wlan: connected to
[ 956.671586] 629,956671586;wlan(36) Standalone
[ 956.672455] 630,956672455;[rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
[ 956.683699] 631,956683699;[rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
[ 956.683699] 632,956683699;[09:29:49.349350] [000000044F897EC2] [wpa_s] wlan: [E :HDD] __wlan_hdd_cfg80211_firmware_roaming: 5200: attr bss id failed
[ 956.779797] 633,956779797;[rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
[ 957.554379] 3634,957554379;[rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
[ 957.554382] 3635,957554382;init: processing action (sys.sysctl.tcp_def_init_rwnd=*) from (/init.rc:724)
[ 957.568918] 636,957568918;[09:29:50.234558] [00000004508CD569] [MC_Th] wlan: [E :PE ] limProcessAddBaInd: 5719: BA setup for staId = 3, TID: 0, SSN: 20
[ 957.705009] 637,957705009;[rmnet0] error: rmnet_ioct called for unsupported cmd[35585]
[G3 Android Development] hourwatch:
In last lineage 16 version GPS is not working for me. It just doesn't find my position.

Edit: Maybe related to this: gitlab.com/LineageOS/issues/android/issues/895
[G3 Android Development] Ph3ar.:
What variant are you using ? On the LS990 sprint version I'm getting a lock in 2-3 seconds with great accuracy with it raining and overcast here today using the latest Dec 20 build . In fact every build so far has worked perfect for me on GPS . I also use the SPH-L720 in that link you posted and again that device also works perfect so maybe it's specific to your variant .
[G3 Android Development] HardStyl3r:
new builds are up

note: this is just a refresh, no issues have been addressed yet
[G3 Android Development] hourwatch:
Ia m using D855. I have achieved to connect GPS waiting for signal around 10 minutes. But that's too much to use it in a diary basis, so is still a problem.
[G3 Android Development] Šəmûʼēl:
I found for g3ds that sim1 started working on (in previous build 20191124 sims not found at all).

sim2 is invisible

Logs were attached
[G3 Android Development] watoan:
[MENTION=6880495]HardStyl3r[/MENTION]

I got a LG G3 (HK version), it is a Dual SIMs international unlocked version but its model number is D858, from here I can see only the ROM for D855, may I know will the latest version LOS16 is working normally for it?

Tried to search in thread but not much related result.

Thanks.
[G3 Android Development] eric93se:
Normal for the very first fix of a fresh install. After that it should be faster, so try again.
[G3 Android Development] hourwatch:
I have tried again and the same: 7-10 minues to connect. And when it connects it only finds a few GPS satellites.

I have tried to install the Magisk Module for GPS fix, which says improves the GPS.conf, and I have installed GPS locker, but nothing. I attach the GPS Locker results. It only uses 4/22 with 33m of accuracy, when trying the same spot with my Moto G 2014 uses 12/23 and has 7m of accuracy.

Maybe is related to trying to read /etc/gps_debug.conf instead of /etc/gps.conf like the bug link I posted, I don't know, but it takes to much to reach GPS signal, and when it achieves it is very poor.

On the other hand, I have tried to improved it installing UnifiedNlp (no GAPPS) and MozillaNlpBackend, but it says that the system did not bind the UnifiedNlp service. Someone knows hot to solve it?
[G3 Android Development] Scepterus:
I keep losing my sim. I'm on the latest 16 build, and it comes and goes. Does not look like a hardware problem because sometimes reboot alone fixes this.

Are there any logs i can attach that will help figure this out?
[G3 Android Development] HardStyl3r:
Custom ROMs nowadays do not support GLONASS and some of the GPS features on legacy platforms, so we're left with 4/22 fix and we can do nothing with it.

The g3ds variant is for you, but it's only unofficially supported with no guaranteed stability yet.
[G3 Android Development] torbherr:
My G3 d855 with 17.0 finds satellites within a couple of minutes (probably at about one minute), which is still too slow. Once the satellites are found navigation works fine for me.

Generally I am happy running lineagesos 17.0.

The GPS satellite finding issue is the only significant issue for me.

The 17.0 runs smoothly for me.
[G3 Android Development] ferdossi:
Hi,

What about Widevine ? I don't know which security level I had before on the Stock ROM but with this one, DRM Info gives an unknow security level so it is not possible to play Netflix videos.

Is there any workaround?
[G3 Android Development] 7wells:
A Happy New Year to everybody! :)

Now I have successfully downgraded my LG G3 D855 (16 MB) from MM to KK, rooted it and installed latest LOS 16.0 with OpenGApps and Magisk. The phone seems to run very smoothly, so thank you very much @HardStyl3r and other involved people who make it possible that this older but very decent phone is still supported with security patches etc.

I have some topics with questions:

1.

Is there a way to wake the phone by triple instead of double tap? Would this need (also) another kernel? If yes, which one? Would we need permissive for another kernel? And before this becomes too OT here: What would be needed (if anything) on LOS' side?

2.

In OpenGApps, I have not excluded one of the launchers, and it turned out that both the Pixel and the Trebuchet launchers are available. However, the Pixel launcher is stopped immediately when invoked, so I have to set the Trebuchet launcher (which works fine). Do I have to pay special attention regarding the launcher when I set the OpenGApss settings? (I used the aroma version with the GUI) I am sorry if this, too, is maybe too OT here in this thread.

3.

I set the system language to German; however, Chrome is in English. Not that I care much about it, but I am curious why. Other apps appear in the system language, i.e. in German.

Thanks for your hints!
[G3 Android Development] HardStyl3r:
I don't know.

1. There is a way to do this, but it's not supported anywhere and definitely not in this kernel.

2. You can always delete it, I guess it's something on their side but it didn't happen to me when I installed 16.0.

3. I have no idea.
[G3 Android Development] 7wells:
Thank you. Yes, I now simply removed both the Google Now and the Pixel launchers, which leaves only the Trebuchet launcher that is fine for me.
[G3 Android Development] 7wells:
I also observed that the LOS 16.0 (built 20200103) snap camera app stores photos to:

/storage/xxxx-xxxx/Android/data/org.lineageos.snap/files/

However, it should store photos there (if an external SD card is selected):

/storage/xxxx-xxxx/[B]DCIM/Camera[/B]/

@HardStyl3r

If this is correct, would you mind correcting this? Thank you so much! :)

As an intermediate solution, would adding a softlink via local terminal cause any unwanted adverse reactions?

PS:

If there was a way to omit the "IMG" prefix in the filenames of the photos taken by the LOS snap camera app, I would appreciate it very much. If the effort to change this, is not worth the benefit for most of the users (or not liked by most of them), could this be accomplished by a manual tweak on my side? Some hints would be great. Thanks again.
[G3 Android Development] 7wells:
With LOS 16.0, the LG G3 D855 is not charged wirelessly.

I tested 2 chargers, none works with the G3 but both charge my S7 and both charged my G3 on stock.

Can somebody confirm this?
[G3 Android Development] :
Hi

I'm using LG G3 D855 as well. I've seen you posted in other ROM threads as well. So I guess you're not really sure about what ROM to use. I've not used this ROM, I've tried many other ROM's. May I point you to another interesting ROM from the same maintainer: AOSP Extended. I'm using it now without any problems. For the first time i didn't need to reflash for a long time. And pictures are saved where it should be saved. But there still is the "IMG" prefix. I don't know how to make it save with a different name. And you can flash it with OpenGAPPS or MicroG without problems. You should try it. I think you won't regret.
[G3 Android Development] 7wells:
Hi and thanks for your post and recommendation. I will look into it. :)

Indeed I am looking for a ROM with a "compromise" between up-to-date security patches and working stock camera. But I will follow up on that in the right thread before I get OT here. ;)
[G3 Android Development] HardStyl3r:
This is a known issue and I can't do anything unless LineageOS decides to fix it. The issue lies in the Snap application and its implementation, the hardware is fine.

CleanROM may be the thing you're looking for. The latest stock with good stuff.
[G3 Android Development] 7wells:
Thank you so much!
[G3 Android Development] Андрей711:
Hi guys there is a problem with ls 990.

on los 16 with twrp 3.3.1, a blue screen appears when connected to a computer.

If you use another firmware (stock) with twrp 3.3.1, this is not observed.

Maybe someone came across? How to overcome this problem?

sorry for my bad english