yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG G3] thelgog:
Alright i have some more finding as to my issue and some mythbusting

1. its not my headphones because with the same audio settings it ( convolver + spectrum extension ) runs like it did on fulmics and stock. beautiful

2. its not just it being to loud in general because when you disable it all and as long as any bass boost isnt enabled then you can make it go super loud to the point where it sounds like speakers so its not just it being loud. Since it also only occurs on roms you've built ( not calling you out ) may be an issue with the CM build itself?

3. I havent had any of BT crashs so thats good but it is on a BT headset ( jaybirds x2 to be exact) and running regular apple earpods thru aux with the settings sounds normal

so my guess is it may just be the current CM build or whatever and i also switched to acc kernal ( for fast charge and not the 1000 MA this kernal has ) and so switching kernals doesnt solve it either
[T-Mobile LG G3] shariq3598:
Wifi drops issue

For developers and others: Regarding to wifi drops (disconnects and reconnect on its own) i've found something helpful,i dont know you have seen it before or not. Google this: "Bug id 196035" might be helpful. :)
[T-Mobile LG G3] SirElim:
Well that was fun... Tried to update my RR d851 to the new 30d modem, that didn't go well. At first it was stuck on boot. I pulled the battery and then it booted with no baseband found in settings, and said no sim found. WiFi worked. Then I flashed the bootloader, that made it permanently get stuck while booting.... Tried a bunch of different modems and bootloaders after that to get back in.... Didn't work. Did a restore boot and modem from a recent nandroid and tada! Thank God.... Lol. So is RR compatible with the new 30D modem?
[T-Mobile LG G3] McNoob:
Running 30d modem and bootlaoder with RR here, no problems. Did you follow the instructions from Autoprime s thread ?
[T-Mobile LG G3] gunner05:
So these BT share issues are from latest build? I'm running the April update and no BT issues here... now worried to update this latest build (even tho it fixes nebula swipe2sleep) - any thoughts?
[T-Mobile LG G3] SirElim:
What instructions? I didn't want to install stock mm just the modem / bootloader I guess. I didn't see any specific instructions regarding that though I saw others flashed the bootloader and modem over for other roms and it worked fine. Not so much for me. Odd. Anything particular you're supposed to do to achieve this with RR?
[T-Mobile LG G3] marcdw:
I installed the stock ROM via TWRP method. Even got it to work as primary using Nebula 12.5-MM kernel. Lost my internal storage as a result. I eventually got rid of the ROM.

Anyway, so now I'm on 30D modem. My primary PAC ROM LP and secondary Validus MM work with 30D modem. But for some reason Resurrection Remix and Dirty Unicorns will not run. Stuck at the LG logo. Not sure why. In RR's case I reflashed (dirty) the ROM and gapps but it still won't run. Looks like I'll have to start from scratch. Didn't want to do that in DU's case 'cause I had it the way I liked it.

I did backup my EFS and modem. Might restore that first. I was on 10R and still chugging along.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] marcdw:
YES! I'm back into RR. It took a little doing though.

I restored my EFS and modem backed up in TWRP. However, in PAC LP (my primary) I had no data or APNs.

So I restored from stock KitKat which is supposed to be 10R. No go. Same thing.

Tried again from SkyDragon KK but now phone would shut off.

Flashed a 10R zip I have but failed again. Phone shuts off.

Flashed another called Baseband-10R or something from (the once great) Cloudyfa.

BOOYAH! Data and the APNs were back.

Rebooted and was so happy to see the Resurrection Remix boot animation. Data and APNs are a-ok here.

I am a bit confused though. I compiled a list of basebands for the D851 a few months ago. I've never had or flashed anything beyond 10R. My baseband was the same as the 20 series (20B, 20G, etc.). What I have now is 10M according to my list. That's what I used to tell people I was running anyway before I noticed a change one day.

Screenshot below shows the baseband. Can anyone confirm if that's 10m or 10r?

Spoiler content hidden.

LG G3 D851, Resurrection Remix-M ROM, Tapatalk 4.9.5
[T-Mobile LG G3] SirElim:
I believe that is 10m and its the one I'm on too. I had to go back to it when 30D would let my phone boot with RR.

I read on the D855 the mm modem only works on the original stock rom. Though I saw someone (d851) using exodus and cm13 flash the modem / bootloader and they were fine. (another cm13 guy ended with bootlooping issue were seeing here) odd results...
[T-Mobile LG G3] SirElim:
K figured I'd try it again (because why not...) not quite sure why the heck it worked this time? I flashed the 30D modem wiped cache /dalvik cache, flashed the bootloader wiped cache /dalvik cache and it worked this time! Took a bit to boot the first time, it setup all my apps during the first boot again but now I'm on the 30D modem. Maybe it was because I didnt flash the bootloader with the modem the initial time and then it was too late later... Anyway, all set now. Can confirm it does work with RR.
[T-Mobile LG G3] navey:
Is anybody else still experiencing random freeze and then black screen of death? (battery pull)? I have been getting these consistently for the past few builds but I don't see anyone else talking about it.
[T-Mobile LG G3] sleepfaster:
I had those symptoms, but it was due to some issues with the proximity sensor. Once I set it not to blank the screen based on the proximity sensor, it cleared up.
[T-Mobile LG G3] gunner05:
So i just want the nebula fix where swipe2sleep is disabled by default. my BT is working fine now and don't want that to change. Why am i reading all these complaints about BT and screen issues, is this from latest build only?
[T-Mobile LG G3] pj1000:
+1
[T-Mobile LG G3] marcdw:
I posted how to deal with the Nebula thing if you're not on the latest build. Might be a few pages back.

Sorry, it's almost ten pages back. Here's the post. Try it out and see if it works for you.

http://xdaforums.com/showthread.php?p=66796743

[MENTION=438893]pj1000[/MENTION], those +1s are annoying. Save those for Google+ and just use the Thanks button when you agree or like a post.

[I'm being a putz today, heh heh]

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] pj1000:
Marc - life is too short...try to get annoyed so easily. Regarding swipe2sleep, it's not a problem on RR a few versions back. Everything on that version works fine so I'm happily sticking with that. one for the time being..
[T-Mobile LG G3] marcdw:
[MENTION=1014934]SirElim[/MENTION], I did as you did with 30D but it didn't work out. Same as before. Two ROMs run, RR is stuck at LG logo, while DU shuts down phone.

Now I'm on 20G and all is fine. Staying put.

LG G3 D851, Resurrection Remix-M ROM, Tapatalk 4.9.5
[T-Mobile LG G3] SirElim:
Yeah I'm not quite sure why it didn't work the first time for me and did the second. I figured it was the order or wiping cache In between.

Regarding the random black screens, I was experiencing that at least once or twice a day. Thanks to fubaring my phone trying to update to 30D modem I restored a backup modem bootloader, kernel that included tootsie-pop 3.4.0 kernel to get my phone booting / working again. I don't want to jinx myself here but so far I haven't had one black screen issue on tootsie pop so far!
[T-Mobile LG G3] navey:
So you think the black screens are a result of the kernel? I'm experiencing them at least 2-3 times daily
[T-Mobile LG G3] McNoob:
New one for me: whenever o try to change a ringtone or alarm sound, I get " the process android.process.media has closed. And settings fc. This is on 0516 build, which I dirty flashed over 0509
[T-Mobile LG G3] SirElim:
Honestly don't know if the kernel is the issue or not? Others in this thread are stating they disable the proximity sensor and it fixed the black screen for them. Since I had to restore the system (including the kernel) , modem and bootloader for an older RR version rom and then updated to 30D bootloader and modem I haven't had one black screen, but it's only been a day or two so far. (though I usually get a black screen 1-2 times a day so...) it could be completely unrelated. I'll keep testing this for a few more days and report back. Maybe if it is stable I'll take a nandroid and do a little testing. Wipe everything, install the most recent RR, test and see what happens then play with kernels.

This is what I'm running right now with 30D bootloader and modem.
[T-Mobile LG G3] nytebird:
Not sure if this will solve your problem, but if click on Codefire Directory in autoprimes'thread, you'll find the files for the modem and bootloader
[T-Mobile LG G3] McNoob:
So I clean flashed 0516 build and that solved my ringtone access problem. Just leaves me wondering what went wrong, since I clean flashed 0509, and the only apparent change in 0516 was the swipe2sleep removal... Oh well. Clean flash is your friend :)
[T-Mobile LG G3] :
New update. 5.6.9.!
[T-Mobile LG G3] thelgog:
Back at it again in 5.6.9 with the Bluetooth problems
[T-Mobile LG G3] uberboyd:
So your still having the bluetooth share error in latest build?
[T-Mobile LG G3] xlxcrossing:
Bluetooth share has stopped logcat
[T-Mobile LG G3] :
Don't give up hope yet on bluetooth not working. I just need to find the right combo of fixes to get this all working. I need to see if I can find a bluetooth headset or try connecting to my computer through bluetooth and see if I get the same issues as you guys. Unless something is messed up with CM'S bluethooth code. Im 99% sure I can figure this out.

Update: Good news, I get the bluetooht share fc when my g3 tries to connect to my crappy Imac. So I should be able to do some test builds locally and see what happens.

Update2: I looked back at some of the cm commits, and I found one dealing with bluetooth on may 4. So Im going to try a build before may 4 and after may 4 and see if that could be the bt issue.

Update3: I reverted the bt and nfc commit in todays build Im uploading. I was able to connect to my imac bluetooth and send a find from my imac to the phone zia bluetooth. I had no issues with bluetooth share fc.
[T-Mobile LG G3] McNoob:
Happy dance!
[T-Mobile LG G3] :
Ok new release it out. Has updates from cm today, and I reverted the NFC and BT commits. I tested the BT with computer to phone. I don't have a bt headset so I couldn't test that or connecting to a BT radio. Let me know if it works or not. Thanks guys.
[T-Mobile LG G3] McNoob:
First off, thanks! 9JY710657U552704C Have a beer on me!

I dirty flashed 0524 and 0524 GApps over 0516. Still get the BT share stop when I turn on BT and let the phone go to sleep.

BT eventually restarts, and I let it connect to my car radio before it goes back to sleep again - no BT share close, connection seems solid.

When I turn off the car radio, with the phone display off, I get the BT share msg when I wake up the phone.

Catlog attached.

On another matter altogether - wold you consider baking Viper4Audio into the ROM again? I 've been flashing this ViperAudiophile.zip in TWRP after each flash, but it's very kludgey, and never takes on the first or sometimes even the second try
[T-Mobile LG G3] :
Thanks for the donation. I'll go to my friendly starbucks so I can fuel up and keep on coding. :p

You might have to clean flash. That's what I did on my phone. I still haven't recieved any BT errors at all. Ill keep bt on, let my phone fall asleep and see if I have any other issuues. Of course I was only connecting to my imac though. With headsets and radios could be another issue.

Yea, I could probably try and figure out how to get viper4android back in a few days.
[T-Mobile LG G3] :
Also I might be updating some of the blobs to 30b. Ill just need to make sure that it can be done without having to install the 30b modem or bootloader.
[T-Mobile LG G3] uberboyd:
So I clean flashed latest, I connected pebble and a bt jabra and have no errors yet, I'll keep you posted I have 7 bt devices I connect to regularly so I'll find out what happens.
[T-Mobile LG G3] :
Awesome. :) Thank you very much.
[T-Mobile LG G3] McNoob:
FWIW, I've only recently updated modem and boot to MM level, was running 20e modem and boot and was installing V4A using the same method (and with the same frustration).

Ya know, this latest build may be a positive step for me after all. I get the BT share stop, but do not continually get it as before...hmm, I'll try a clean flash and factory reset the BT in my car stereo.
[T-Mobile LG G3] :
Yea, the previous build I was getting Bluetooth share FCs myself. This new build I haven't had any issues. Well, connecting to a computer through Bluetooth anyways.
[T-Mobile LG G3] uberboyd:
Bluetooth Share

Well I'm on day two and have connected to all seven of my bluetooth devices and have not had a issue so far. I am using d851 using cricket sim I clean flashed all good so far, its nice to have a solid ROM to turn to the stock mm rom was sort of lacking in Battery department.

Keep up the good work.
[T-Mobile LG G3] wallaces:
Unfortunately, after a clean install, I've had a couple of the BT closes, but only a couple! Very nice! I've since installed catlog so will catch one if it happens again.

Thanks! Much more stable for sure
[T-Mobile LG G3] :
Awesome. I was worried cause nobody has said anything. I still have a little bit more tweaking to do on some other things.
[T-Mobile LG G3] :
Sounds like things are getting better. For sure a good sign then.
[T-Mobile LG G3] jrome123:
I'm on 5-17 fresh installation I never had a Bluetooth problem and I have my LG Urbane hooked to it
[T-Mobile LG G3] thelgog:
the issue im having with bluetooth headsets isnt really with it connecting but rather the sound itself on the latest DU it works fine with viper but when using it on your 2 roms you maintain (bliss and rr ) i get heavy glitching sounds and 2 vol steps when only turning convolver on with hi-fi on ( when theres bass the mids and highs gets lowered down so low and bass gets muddy then returns to normal as soon as a bass hits like its the auditory protection kinda like so ) stock kernal acc and that one nebula was based on xposed or no xposed all same
[T-Mobile LG G3] uberboyd:
Well unfortunately I had my first by share error I had my Pebble connected but no other bt devices that's when I got the error "by share" I have never produced a log at file but if you spoon feed me I'll attempt to replicate the error.
[T-Mobile LG G3] :
Have you tried using viper on bliss and rr?
[T-Mobile LG G3] wallaces:
Had another BT closed happen. Here's a logcat:

https://drive.google.com/file/d/0B20MDIvynfy4WUIyNzR0YVVHQjQ/view?usp=drivesdk

Thank you!
[T-Mobile LG G3] :
I could try a couple things, but I've read that mm causes a lot of Bluetooth issues. It could even be an issue with cms Bluetooth app causing all these issues. Which is why aosp+caf roms might not be having Bluetooth issues. They actually use aosp Bluetooth app.
[T-Mobile LG G3] wallaces:
Here's another logcat right after another "Bluetooth share has stopped"

https://drive.google.com/file/d/0B20MDIvynfy4YjZUSTF2LVhoY0k/view?usp=drivesdk

Thank you so much for all your work on this!
[T-Mobile LG G3] Malezar:
FWIW my BT has only crashed once and it connects to two separate devices when I drive.
[T-Mobile LG G3] wallaces:
Just to make sure, I have gone back to recovery, manually cleared dalvik/art,data,system, did factory reset, cleared cache again then reinstalled RR. It's updating now so we'll see if it's any better.

I had tried installing a full on AOSP ROM but it had the Bluetooth share closed issue as well so there may be no hope for me with MM. :(

Might be forced to go back to LP. That would stink...lol

At least it's doing it less now, so may not be too bad.
[T-Mobile LG G3] wallaces:
Here's another

https://drive.google.com/file/d/0B20MDIvynfy4Z19NOV9nUXBkalE/view?usp=drivesdk
[T-Mobile LG G3] Malezar:
[MENTION=1634082]wallaces[/MENTION]

What BT devices are you connecting to?
[T-Mobile LG G3] thewalkingdude:
Yes I gave it a try last night. Wonderful ROM (as always) but the Bluetooth just kept crashing when I would try to connect. Oh well. Thanks for your work mate.
[T-Mobile LG G3] wallaces:
Hi melezar, I use a Blueant Q2 headset and sometimes connect to my Pioneer car stereo.
[T-Mobile LG G3] wallaces:
Oops, that was my old headset! It's actually a Plantronics Edge headset.
[T-Mobile LG G3] uberboyd:
I sometimes get the bt share error and its not really an issue it works most of the time. I do awake to find my phone stuck on the resurrection boot screen every morning when I wake up, I don't know what would cause that any one else having that issue?
[T-Mobile LG G3] thewalkingdude:
New feature. Ultimate doze mode. :) Joking sir, only joking.
[T-Mobile LG G3] uberboyd:
I did notice the doze setting will disabling that resolve the issue? Setting my phone as alarm clock has been problematic, I appreciate the humor made my evening watching "Scott's Creek" on amazon isn't cutting the mustard. :0)

---------- Post added at 08:48 PM ---------- Previous post was at 08:47 PM ----------

Schitt'z Creek damn spell check
[T-Mobile LG G3] centipedes:
Because this runs nebula then yes it is almost certainly a result of the kernel. Nearly every ROM I have tried with nebula has given me the black screen of death. I would recommend simply avoiding nebula entirely. The dev is a great guy but black screens multiple times a day are not acceptable.
[T-Mobile LG G3] :
I'm not sure if anybody had this problem but for some reason I started getting random reboots ever since I updated this ROM. It's every time I decide to load up chrome and load up webpages, it happens to lag at times and then at times it freezes then reboots the phone. Never had this problem before I updated my ROM. I only dirty flashed the May 24th build & the Open Gapps to the latest possible and wiped the caches/Dalvik. Any help or suggestions would be greatly appreciated. Thanks!

I have provided a logcat in case that helps.
[T-Mobile LG G3] thewalkingdude:
Thats funny because Nebula is all use. More people have had success with it than not. Have you pulled a log to see what causes your crash with said kernel? I'm not saying you haven't had problems with it, I believe you have but you shouldn't tell people to avoid something just because you have problems.
[T-Mobile LG G3] centipedes:
All I know is nebula causes my phone to become unusable and other kernels do not. Whether that's because I lost the silicon lottery or for some other reason: I don't know. Every other kernel functions properly and never, not even once, has resulted in a black screen. Nebula gives them to me once every hour.

Of course I'm going to tell people not to use something when I have narrowed it down to a single factor present across all tests. In all of the ROMs I've used on all versions of Android I've used, nebula is the only thing that consistently gives me black screens and other issues. I thought it was the result of competing battery policies so I disabled those, but it made no difference.

Nebula also gives worse problems depending on the governor/hotplugs (for example: Wheatley will BSOD the phone within minutes even though all hotplugs are off. Same with zzmoove. Slim governor takes a little longer but also BSODs eventually) and the phone runs hotter even when underclocked. Also thermal options have never stuck on nebula whereas they have on other kernels.

Yes, I clean flash every time.

If you use it and it works for you and others: good for you, but it's entirely possible that nebula is the cause of your problems and should be one of the first things to check if you're having issues.
[T-Mobile LG G3] :
Actually, both crisis and rr roms are running my Tootsie-pop kernel which is a slightly modded cm kernel.
[T-Mobile LG G3] :
The newer releases aren't using Nebula kernel anymore and need to be flashed separately if you want it. You also might want to do a clean flash with a more updated gapps.
[T-Mobile LG G3] :
Thank you so much for the information. I will do either of them to see if it resolves the issue.
[T-Mobile LG G3] xlxcrossing:
2 questions...first is the long press power on screen off for flashlight tweak still available because it stopped working for me and I can't find the setting. Second is do you have any plans to incorporate the screen color mod to tootsie pop. I really like the performance of this kernel but I can't stand the washed out colors without the screen mod. Cheers
[T-Mobile LG G3] :
New update! Mostly cm fixes.
[T-Mobile LG G3] :
Not sure about the first one. The rom devs change stuff all the time. I might be able to add that to the kernel. Im trying to keep the kernel pretty basic, without a lot of mods, but I might be able to add that in.
[T-Mobile LG G3] :
The d851 is close to my heart and will always have the best stuff. A lot of you guys have donated to me on the d851 and I feel I kind of owe you guys more hard work. Even though I actually use shamu (n6) as my daily driver, the g3 was my first development phone. Another thing though is I can test everything on the g3 except data and bluetooth. And one more thing. I'm going to try and see if I can get slimrom build for the d851.
[T-Mobile LG G3] centipedes:
Been testing June 8th release for awhile now and everything seems to be working perfectly. GPS, Data, Wifi, etc. The only thing I haven't tested yet is Bluetooth but I will do that once xposed is done installing. Goes without saying but installing Google Dialer requires you to manually set the default phone app or you'll reboot every time you make or receive a call.

The only thing I'm left wanting for is the always-on option button on the navbar. Can't seem to find the setting for it if there is one.

Edit: PC cannot find phone when searching for Bluetooth devices. I don't own any other Bluetooth peripherals, so it may work for other purposes.

Oh and the camera is pretty awful.
[T-Mobile LG G3] uberboyd:
No Bluetooth detect of devices here too
[T-Mobile LG G3] nola mike:
Also can't get BT working on the new build. Tested with multiple devices. Had to go back to the last version, which worked after a dirty flash.
[T-Mobile LG G3] jrome123:
Yes me too no Bluetooth on new-build 6/8 no Bluetooth
[T-Mobile LG G3] :
Looks like cm changed some Bluetooth stuff. Let me update the repos.
[T-Mobile LG G3] :
New release. Let me know if bluetooth works again.
[T-Mobile LG G3] pj1000:
Dirty flashed new version. Bluetooth working again for me. Thanks aclegg.
[T-Mobile LG G3] davexhero:
On 6/12 release, still getting Bluetooth FC's, albeit less often than before. Mainly using a Moto 360 watch. Clean install also. Everything else is great though!
[T-Mobile LG G3] jrome123:
Bluetooth work good 6-12 dirty Flash no force close on bluetooth anything seems to be working day 2
[T-Mobile LG G3] gunner05:
Nice looks like BT is working again on this rom? anyone else seeing bt share issues or all fixed?
[T-Mobile LG G3] thewalkingdude:
Not since he updated. It fixed my Bluetooth problems.
[T-Mobile LG G3] jrome123:
Me

---------- Post added at 05:10 AM ---------- Previous post was at 05:10 AM ----------

Me too
[T-Mobile LG G3] masong397:
Is there call recording? And if so how do I enable it?
[T-Mobile LG G3] magf1882:
Question???

20160616 a new version but the download page appears the same as the 20160612 ... will they mistook !!! sorry for my English:confused:
[T-Mobile LG G3] marcdw:
You are correct. I get 0612 also even though there are two newer builds. No doubt it will be fixed soon.

LG G3 D851, XOSP ROM, Tapatalk 4.9.5
[T-Mobile LG G3] :
It's fixed. Sorry guys.
[T-Mobile LG G3] rodsayd:
Hey I'm really greatful for the work you do for us, without you D851 development would probable be dead, so thanks! And one thing, is it possible to build a ParanoidAndroid ROM for our G3? I always loved that ROM and they're back at it it seems :) Anyway is just a question dont take it bad...

Thanks again for all the job.
[T-Mobile LG G3] :
New update!
[T-Mobile LG G3] cliff385:
Where is the new update download