yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] bacon4bfast:
Is anyone else's double tap to wake not working? Support was there in cm12.1. Just want to make sure I'm not the only one. :rolleyes: :rolleyes: Otherwise everything else works great for me! Camera disconnects from time to time but this build is so new that kinks are expected.

Thank you for your hard work guys!
[Verizon LG G3] dcooterfrog:
I was on this morning's nightly 1/12 and was having screen brightness issues.

it was way too dim even at mix even with adaptive turned off.

i rebooted and it was normal for a while then got dim again.

then new camera appeared ot work. but maybe not.
[Verizon LG G3] lucifergil:
Hi,

Does GLONASS works for anyone on the VS985? My phone sees the satellites but cannot fix on them. I have the same issue on my VS980 with the same nightly.

Thanks,
[Verizon LG G3] notdeadyet01:
Anyone else not able to flash any of the nightlies? I keep getting "Error executing updater binary in zip"
[Verizon LG G3] johnd12:
If you get that error, you need to update the bootstack to 35b. Flash the zip before you flash the nightly.
[Verizon LG G3] cpttrsn:
I got my first taste of this today. I woke slightly before the alarm was due to go off and the phone would not turn on. I do not know if the alarm would have gone off or not. I had to pull the battery to get things going again.

I had a similar issue later in the day while the phone was on charge and I was on a very long phone call. The screen and the power button would not respond after the call ended. Had to pull the battery again.

Again, this was my first issue of this type. The only thing that I can remember doing different is that I set my "power menu" to include screenshot yesterday. I turned that off after the second battery pull of the day and have not seen the issue again. That cannot be related though, right?

---------- Post added at 07:24 PM ---------- Previous post was at 07:22 PM ----------

Thanks for the information. That worked for me as well.
[Verizon LG G3] ncjones28:
It is definitely not something with that setting (from what I've experienced). I haven't experienced it since I updated 2 days ago so I'm hoping it's a thing of the past. It always seems to happen when the phone is charging but I've been running a backup alarm since.
[Verizon LG G3] NedDasty:
I updated yesterday; happened to me today. Fortunately I had set a backup alarm, as I knew of this issue. I woke up to a force-close of the system process though, so it was slightly different, but the problem is still that CM13 is not reliable enough to serve as an alarm clock.
[Verizon LG G3] x86cpu:
This seems to be relevant: http://xdaforums.com/showpost.php?p=64786672&postcount=2903 Is there a special request to get the thermanager removed? Is that even possible? All the power offs/issues/battery pulls, might be related to that.
[Verizon LG G3] ncjones28:
I agree, but the problem isn't just because of the alarm clock app or the alarm would just not go off. There seems to be a problem with charging (at least with my experience). When the phone is charging it will just randomly soft brick itself due to some process. I noticed that constantly when charging in earlier builds the phone would stop charging for a couple seconds then resume (you can notice this if you have wake on charging on). There would be the # symbol showing that something was using root access. So there seems to be some sort of process when charging that soft bricks the phone. I haven't had any recent soft bricks while not charging though I haven't had any since updating 2 days ago as well. This is just what ive seen. There seems to be something running that causes the soft brick.
[Verizon LG G3] x86cpu:
Thanks [MENTION=2385005]invisiblek[/MENTION] http://review.cyanogenmod.org/#/c/126528/
[Verizon LG G3] dragonboydbboy:
On 01/14 still having cm system major battery drain
[Verizon LG G3] ticholas:
I can safely say that, at least in my case, it does not matter if my phone is plugged in or in my pocket, I still get random Black SODs and have to pull the batt. Happens about every other day.
[Verizon LG G3] jimc5423:
I had the same problem. I tried 1/6 and 1/8.
[Verizon LG G3] dragonboydbboy:
I actually had one of those today with 01/14...
[Verizon LG G3] ChiefIlliniwek5:
I've been experiencing them on just about every build going back to cm12.1
[Verizon LG G3] ticholas:
Same here

Bout ready to go back to euphoria..

Can anyone else confirm mic issues/hard time being heard on any of the recent builds?? On 01.10 getting a lot of "what did you say" "can barely hear you"
[Verizon LG G3] johnd12:
Anyone else have camera problems? After dirty flashing from q/10 to 1/14 I now have connection and media server problems that make it impossible to take pictures
[Verizon LG G3] davidliu85:
When this happens, you can hold down the power button + volume down for about 10 seconds to reboot the phone instead of pulling the battery.
[Verizon LG G3] sentry_mode_activated:
Bluetooth issues

Is anyone else experiencing bluetooth connectivity issues? For some reason I can no longer connect to my smart watch since the past few builds. Shows up in bluetooth settings but never connects. What's weird is that it connects to my car just fine still.
[Verizon LG G3] jacksheadache:
Battery life issues persist within 01/15 build. Everything else has been very solid thus far.
[Verizon LG G3] AKDMA:
Is anyone having issues with Root Explorer force closing?
[Verizon LG G3] RedWingsFanEd:
I did until I installed Busybox I have to install it every update.
[Verizon LG G3] dragonboydbboy:
Strange thing: dirty flashing for some time, never had the sod people have talked about.

Clean flashed 01/15, had my first one just now...
[Verizon LG G3] fenrisswolf:
I can confirm that behavior. MY Jawbone up24 hasn't been able to pair with my phone from the 1/10 upgrade upwards. It gets detected just fine, and the up24 itself can pair with other devices, just not with my phone. My phone can still pair with BT headphones and with my car, so it must be something about wearables...

---------- Post added at 08:01 PM ---------- Previous post was at 07:10 PM ----------

Follow-up: Downgraded to 1/7 update, and my Up24 band pairs up properly again. Definitely a bummer that something got borked with bluetooth on the upgrades sometime between 1/7 and 1/10, and that it hasn't been patched yet....
[Verizon LG G3] MaddMaxx636:
Will you please remove the thermel control crap from the ROM and let the kernel control the thermal? Its making my phone heat up and its messing up and with custom kernels!
[Verizon LG G3] dragonboydbboy:
I believe that was reverted in 01/14

http://review.cyanogenmod.org/#/c/126528/
[Verizon LG G3] MaddMaxx636:
Oh one other thing! What about this one? https://github.com/CyanogenMod/andr...mmit/9c0da61b6f7a7b74800a0147751abaf4229f429d

Why was this done? Isnt this apart of thermal controls and or something that heats up the device?
[Verizon LG G3] AKDMA:
My phone rebooted during some app updates today and is now stuck in a bootloop, even after wiping cache/dalvik. Going to do a clean install of the latest version.
[Verizon LG G3] AKDMA:
I keep getting the " connection to 10.0.100.17:9312 failed (errno=111, msg=Connection refused) " when searching for this, so forgive my asking - how do I fix the titanium being unable to write to external SD with this ROM?
[Verizon LG G3] RedWingsFanEd:
I believe you have to go into TB settings/preferences and go to backup folder location. Then navigate in that setting to the root of your SD card and select it. After you give it permissions you can select TIBU or whatever. That worked for me.
[Verizon LG G3] AKDMA:
This happened again on 1/15, installed cleanly. It occurred during a multi app update over 4G. Phone bootloops and will not recover until I reflash clean - dirty flashing does not fix it, nor does wiping cache. Going to have to jump ship, unfortunately.
[Verizon LG G3] dragonboydbboy:
Do you still? I thought there was a mini busybox included in a recent in nightly? It's worked for all my root needs thus far... Haven't tried root explorer though
[Verizon LG G3] NegativeOne:
Has anyone figured this one out? Is it officially recorded on the bug tracker? It seems extremely widespread
[Verizon LG G3] RedWingsFanEd:
Everything else was working fine with out reinstalling the full busybox. Root Explorer seems to be the only one so far that doesn't run without it.
[Verizon LG G3] johnd12:
Anyone else having problems with broken video recording (on snap camera and all other camera apps) since 1/10 nightly?
[Verizon LG G3] dragonboydbboy:
01/15 both snap and Google camera work.

777 kernel
[Verizon LG G3] konoha457:
Bluetooth connection problems

I'm also having trouble connecting my fitness wearable (fitbit) ever since the 1/10 nightly. Although I was still able to connect and sync via bluetooth with my pebble. From the changelog, it would appear there was a change to the bluetooth package from merging the "improve AVRCP metadata string" to the "b9398e5 Merge branch 'LA.BF.1.1.3_rb1.7' of git://codeaurora.org/platform/packages/apps/Bluetooth". So far the issue still hasn't been fixed on the current nightly, and the only fix was to downgrade to 1/8 or earlier.
[Verizon LG G3] dragonboydbboy:
I've noticed that on a clean flash, when setting up, the cm setup overrides the Google setup that allows me to choose a restore from a cloud backup (thus restoring my apps and sometimes home screens)

Rather annoying and defeats the purpose of having a Google backup...
[Verizon LG G3] aaronc222:
My Charge HR works fine on 1/18 nightly. Was on 1/13 before that without issue as well.

Both times it was a clean wipe with Open GApps Stock download.
[Verizon LG G3] konoha457:
I tried dirty flashing the 1/19 nightly and still couldn't connect to my fitbit flex. Also my bluetooth headphones and pebble couldn't connect either. Will try to do a clean flash soon to see if anything will change.

*UPDATE* 1/20/16

Just dirty flashed the 1/20 nightly, now both bluetooth devices work again!
[Verizon LG G3] dragonboydbboy:
I am having the extremely annoying issue of Google calendar not syncing events that are added from my phone (they disappear immediately when added from phone, but work normally when added via my tablet or web)

This started today with 01/19 nightly, as far as I noticed...

Normal fixes aren't working (re-adding Google account, forcing sync, etc)

Using the latest version of the app
[Verizon LG G3] R2D2-AKU2:
My quick tiles disappeared. Or I can't swipe down from the right corner (which is enabled in settings). Anyone else have this?
[Verizon LG G3] bschmidy10:
Any way to flash gapps on a dirty rom without force closes galore?
[Verizon LG G3] keetrock:
Same here...new update seemed to have borked it
[Verizon LG G3] dragonboydbboy:
I had that briefly upon boot (all quick tiles were gone) but they repopulated when I did long press on settings gear to readd. Swipe from right corner works too
[Verizon LG G3] keetrock:
Has anyone else had WiFi issues since the last update? Mine seems to not want to connect or it takes forever to connect when it decided to.
[Verizon LG G3] R2D2-AKU2:
That worked. Thanks!
[Verizon LG G3] jacksheadache:
System profile icon on the quick tiles seems to randomly disable. System profiles still function through the settings menu.

Edit: This issue persist on the 01/20 build.
[Verizon LG G3] dcooterfrog:
yup same here.
[Verizon LG G3] dragonboydbboy:
Could somebody test their Google calendar for me? Just try adding an event (if you're on the 01/19 nightly) and let me know if it stays
[Verizon LG G3] Opsdri:
Mu cm13 calendar works fine when adding an event. 1/20 build.
[Verizon LG G3] dragonboydbboy:
Thanks.

But are you using the cm13 calendar or the Google calendar?
[Verizon LG G3] keetrock:
I just added an event using Google calendar and it stayed...I'm on the most recent 1/20 build
[Verizon LG G3] dragonboydbboy:
Hmmmm odd.

How is Google calendar installed? As a system app? Do you also have the cm13 calendar? And what gapps are you using?

---------- Post added at 09:03 PM ---------- Previous post was at 08:53 PM ----------

Never mind, seem to have fixed my issue like this:

Simply flashed the latest Google calendar apk from apk mirror (even though the open gapps I was using had the same version installed already)

Very strange indeed...
[Verizon LG G3] MORANDCHI:
Was looking into Flashing this ROM. I flashed Broken 4.1 MM ROM, but it was shutting down and getting hot. Does this ROM work as a good Daily Driver? Are there any major issues?

I Flashed back to SD 5.1.1. But Like the MM roms

When Flashing this ROM, Do you Flash the CM 13 ROM, Bootstack 35B then Gapps?

thanks

Chris
[Verizon LG G3] shindiggity:
Bootstack, Rom and gapps.
[Verizon LG G3] TheLoonyRebel:
Anyone else on the 1/20 build not seeing the 5ghz band on their WiFi router?
[Verizon LG G3] R2D2-AKU2:
This week all my issues are gone. I'm back on stock kernel and everything works (everything I use, anyway). No more overheating, charging issues, etc. Definitely a daily driver now.
[Verizon LG G3] bschmidy10:
Lots of WiFi issues on 1/20 here, no 5ghz and usually doesn't appear to be transmitting data properly, if at all.
[Verizon LG G3] dcooterfrog:
daily driver. yes. once the charging issues and heat issues were solved.

I am not having wifi issues.

I might be having smartlock issues. sometimes it seem lik i need to enter my password when it should stay unlocked, but i am not even sure.
[Verizon LG G3] dragonboydbboy:
I'm having no noticeable WiFi problems and can see my 5ghz just fine. 01/20
[Verizon LG G3] jacksheadache:
Continue to have issues with system profiles on the quick tiles within the 01/21 build.
[Verizon LG G3] lucifergil:
I'm having problems with 5Ghz wifi on 1/20 as well.
[Verizon LG G3] TheLoonyRebel:
I did notice a few Wifi changes that happened on the 1/20 build that might explain the issue with 5Ghz not working for some of us. I can confirm on my Asus router that 5Ghz is turned on and my Sero 7 Pro is connecting to it so my router is working fine on that end of things.
[Verizon LG G3] keetrock:
Same issues here with WiFi, but if you go into your advanced WiFi settings and select 5ghz only, it will show up...then if you select Automatic, you will still be connected to the 5ghz band.
[Verizon LG G3] jacksheadache:
Repeatedly crashing after boot on 01/22 build. "Unfortunately, the process com.android.phone has stopped"
[Verizon LG G3] a65lopez:
No black screens? That's why I left candy and went back to SD
[Verizon LG G3] psycho_asylum:
Same here. The SIM card icon is grayed out. Unfortunately, I'm not in a position to grab a log, need to flash back to previous.
[Verizon LG G3] dcooterfrog:
Same process .... phone... stopped
[Verizon LG G3] keetrock:
Same problem here...had to go back to the 1/21 build
[Verizon LG G3] bschmidy10:
I'm on 1/20 and am not receiving texts , sending is fine
[Verizon LG G3] Opsdri:
Same error. I dont have any backup of the previous build so i just flashed it manually withoup wiping data. hoping that there will be no error.
[Verizon LG G3] JMooney5115:
Hi. I just flashed the latest nightly after flashing the 35b boot stack, and then flashed micro GAPPs. When the phone boots up I get a phone apk force close dialog constantly before I get to step 3 of the step.

This was a clean flash with wiping cache before rebooting. I also tried not flashing GAPPs and the same thing happened.

TLDR; phone apk force closes constantly during setup. The phone is unusable.
[Verizon LG G3] keetrock:
If you look at the last few posts, the current 1/22 build is giving an error...just a piece of advice, check previous messages before you flash anything...it will save you a world of heartache.
[Verizon LG G3] cpttrsn:
1/22 is having issues. Try the 1/21 and you should be fine.
[Verizon LG G3] Opsdri:
Tried flashing 1/21 over 1/22 without wiping the data. No errors as of the moment. For those having trouble with 1/22 without 1/21 back up, just flash back to 1/21 but downgrade usually needed a data wipe so do at your own risk.
[Verizon LG G3] dcooterfrog:
1/23

I couldn't even get past encryption before android.phone has stopped

Also I never have had to wipe when doing a down grade of a nightly. This is good because my data partition is encrypted and twrp won't mount it.
[Verizon LG G3] stinson317:
Me too ended up having to wipe and go back to 12/28 nightly to find a version that didnt produce error. Anybody know whats going on or what to do to fix?
[Verizon LG G3] R2D2-AKU2:
1/23 borked my phone. Same phone crashing thing as 1/22, but this time when I flashed 1/21 overtop it failed to boot. Had to clean flash.

By the way, I was not able to recover my settings from Google account, so be prepared to set everything up from scratch. Or make a backup in twrp before attempting to flash any newer nighties until this thing gets resolved.
[Verizon LG G3] MaddMaxx636:
Im having the same damn issue! Please fix this with a hotfix or something!
[Verizon LG G3] Opsdri:
1/21 is the latest version that doen not have android.process error.
[Verizon LG G3] dragonboydbboy:
Yes I've noticed that the CM account overrides the Google account restore... So annoying
[Verizon LG G3] dewhashish:
anyone get Android Pay working?
[Verizon LG G3] PDR447:
Anyone know how to tell the devs that the issue is likely this:

http://review.cyanogenmod.org/#/c/129256/

that's the only phone related change I can see.
[Verizon LG G3] Sparty73:
I agree that this commit is likely the source of our consternation.

I'm sure [MENTION=2385005]invisiblek[/MENTION] has other things going on in life that he's paying attention to this weekend. I'm sure he'll revert, as least for the VS985, once he sees the thread.
[Verizon LG G3] r.Huzar:
Yeah, I hope that someone will figure out the phone thing as I have had to roll back to a backup over the previous 3 installs due to the phone crashes.
[Verizon LG G3] Opsdri:
Has anyone tried the 1/24 build?
[Verizon LG G3] PDR447:
From reading the chabgelog it doesn't look like it was fixed for 24.

If anyone knows what file that RIL change compiles into we can just grab it with a root explorer and move it to a new build manually after flashing.
[Verizon LG G3] dragonboydbboy:
There is a telephony change in 01/24, but it doesn't seem like it would fix the problem

http://review.cyanogenmod.org/#/c/129557/
[Verizon LG G3] Sparty73:
I've tried 1.24. It's not fixed.

They're on it, though: http://review.cyanogenmod.org/#/c/129601/
[Verizon LG G3] Jamez007Bond:
Has anyone had issue with CM Recovery not allowing an adb sideload?

I ask because just before updating to cm23 I had toggled in the dev settings to use the CM Recovery, rather than continue using TWRP as I had been. Upon rebooting the device I got the android.process error as some of you have and I figured no problem, I'll just revert back to the last build that was working. No go. All that happens is I'm stuck at the CM logo boot screen no matter what build of CM I try. I've left it on this screen for several hours in the hope it would work through whatever was going on.

Then I try to gain access to adb sideload via CM Recovery and it will not allow me to sideload anything from my Win 7 computer, or my Linux computer. I've tried various angles from the adb approach to gain access but nothing successful yet.

It appears that my problem could be stemming from the CM Recovery, but I can't replace it with TWRP no matter what I've tried.

From the device while in CM Recovery, adb sideload appears to work for a minute or so because I can get a reply back from a Linux command where the device replies "sideload". Any further attempts of communicating via adb fail as if it wasn't connected. I can gain a brief connection again by restarting the adb sideload option from within CM Recovery AND restarting adb from the linux command prompt, making my first command to sideload a new CM.zip file. After about 5 seconds it appears to timeout and return me back to a prompt without any progress indicator appearing to show the transfer.

Oh, and one more thing, CM Recovery will not recognize my external sd card so I can't just copy a file over to the card and put it back into the device in an attempt to transfer a file.

At this point I'm thinking I'm out of options and will need to use the LG Flash Tool to start over at a big square 1.

Does anyone have any other Ideas to try? I've poured over so many forums in search for answers but I'm coming up short. I generally take pride in not asking for help because usually the answers are just a search away, that is if you do your due diligence. A big thanks if any of you have any further guidance. I know we have a lot of very knowledgable people here with lots of experience.
[Verizon LG G3] Sonic_44:
To be honest, just try flashing TWRP 2.8.7.0. That will give you the best results. It's recommended by all the users as it was more made for the device. CM recovery has been a little cumbersome for everyone. But that does allow ADB access and also to connect as storage in case you wiped your whole phone (which I've done...)
[Verizon LG G3] psycho_asylum:
The change was reverted after midnight on 1/24. It should be in the 1/25 build.

edit: the revert was abandoned but the change that will fix the issue is here: http://review.cyanogenmod.org/#/c/129652/ I don't think it will be in the 1/25 build.
[Verizon LG G3] Sparty73:
Missed the 1.25 build, but the commit is now merged. Next build...

I'm actually holding out until it drops. Don't want to start fresh, and didn't make a nand. Could Titanium, but that takes time.
[Verizon LG G3] psycho_asylum:
Same here. It's difficult to operate with out a phone, I don't have a backup phone. I tried flashing back to 1/21 but it won't boot. It just sits at the CM logo. I had it on the charger last night and gave it a few hours to try to boot and it was off when I woke up with 0% battery.
[Verizon LG G3] TrueYears:
using the 1/21 build because from what Ive read, the recent ones have major problems. So far 1/21 seems stable .. enough, I am using it to scan for books, bluetooth works but not the camera
[Verizon LG G3] lucifergil:
I reverted to 1/19 and all wifi issues went away.
[Verizon LG G3] below100hz:
I'm running the 1/21 build and just realized that I can't make calls from the phone app? if i try to dial from recents or even manually dial it does nothing. I can make calls to contacts if i go through the contacts app. I see people have had issues with the phone app force closing. Anyone having the same issue? sorry if it has already come up, I searched but didn't see this issue specifically.
[Verizon LG G3] kuhl_man:
On 1/19, how do you get the quick tiles to show up?
[Verizon LG G3] dragonboydbboy:
Use Google camera as the default, snap has issues from within other apps I've noticed (but does fine on its own)

---------- Post added at 04:42 AM ---------- Previous post was at 04:10 AM ----------

I believe there is a bug, try updating to 01/21

If you mean how to actually add and edit, long press on the setting gear from notifications drop down
[Verizon LG G3] Opsdri:
Im using 1/21 as well but i dont have this kind of issue. Try to dirty flash it again and clear cache and dalvik and look if it fixes the problem. If not, i recommend a clean flash
[Verizon LG G3] R2D2-AKU2:
No problems here with 1/21 for calling from recents. I'm not sure if I've dialed a number directly or not, but I haven't had any issues with the phone.
[Verizon LG G3] stinson317:
1/26 flashed (dirty). So far so good.
[Verizon LG G3] R2D2-AKU2:
Yes it's good. I made s backup first just in case, but it's all good.
[Verizon LG G3] Sparty73:
I'm glad I held out over the weekend for 1.26. Clean flashing everything would have been a gigantic pain.
[Verizon LG G3] r.Huzar:
Dirty flashed 1/26 and so far so good. Phone issues seem to be resolved.
[Verizon LG G3] Jamez007Bond:
Sheesh... I'm still pounding away at this and don't seem to be gaining much ground on even getting and adb connection with the device. I WILL PREVAIL! haha
[Verizon LG G3] FynxSyndct:
Cr@ps!!! just flashed 1.25 this morning to fix a SD card issue from before and update my phone w/o looking here. no phone until sideload tonight. :(