yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] baldybill:
Not asking for an ETA, just a ballpark. Do we have any idea if we'll get a stable CM13 and if so what month?
[Verizon LG G3] dcooterfrog:
sounds like an eta :)

did you mean snapshot. I dont think there are any cm13 snapshots yet. this seems pretty damn stable to me.
[Verizon LG G3] techhexium:
Hi, has anyone had issue with TitanumBackup and their external SD cards if they have one? My TiBu settings are stored in my external SD but aren't loaded anymore. In CM 13 compared to 12.1, the sdcard folder is a random eight alphanumeric string instead of I assume "/storage/sdcard1". Also I can locate my backup folder but TiBu says it cannot write to the folder, so I can't make new backups there. But I checked /system/etc/permissions/platform.xml and the right permissions seem to be there. Is there anything I can do that could resolve this, like rename the folder to sdcard1 or run the SD card fix? I'm using 12.1 atm and it's a while to switch back and forth between roms.
[Verizon LG G3] RedWingsFanEd:
If you go into TB settings and go to backup folder location and select the root of the SD. After you select it and close TB you can go back in and select the folder you want to use.
[Verizon LG G3] dcooterfrog:
this thread is getting awfully quiet. the change logs are getting smaller.

are most people going to 46a?
[Verizon LG G3] baldybill:
dcooterfrog, which nightly do you find the most stable so far?

and what is 46a?
[Verizon LG G3] someguyatx:
Yeah but 46A is still a little glitchy so I was thinking of flashing the latest nightly. Are there still wifi issues when switching from 2.4/5Ghz?
[Verizon LG G3] techhexium:
I tried that, here's the specific problem I am facing. The folder you see is the SD root. Root is enabled, otherwise I wouldn't be at this point
[Verizon LG G3] RedWingsFanEd:
Post #484 was where I got this trick and it worked for me. He has another suggestion in the post you may want to try.
[Verizon LG G3] Chris_Patterson:
That worked for me as well.
[Verizon LG G3] Nnyan:
You do know what ETA means right? ESTIMATED is the key word, althought you could subsitiue Ballpark and call it a BTA.

Asking for and ETA (even if you say you are not and call it a ballpark) is still still asking for an ETA. Just saying.
[Verizon LG G3] baldybill:
While that may be true, the rest of the question has nothing to do with an ETA or BTA.

Do we have any idea

IF

we'll get a stable CM13?
[Verizon LG G3] techhexium:
Thank you sir, I'll try it when I get the chance but it seems like I'm not the only person who had this issue and it would take care of it
[Verizon LG G3] someguyatx:
I flashed the 0302 nightly and its definitely a solid daily driver for me and much smoother than 46A. After setting everything up I rebooted and charged to 100% then pulled off charger at midnight and it was still at 100% at 7AM when I woke up. edit: after a while my 5Ghz networks disappeared until I rebooted, for now I guess am just not connecting to 2.4Ghz at home or work.

What are you guys using to replace visual voicemail? I forgot all about the jibberish texts from Verizon
[Verizon LG G3] Nnyan:
Unfortunately that's not an option for me since a number of the networks I connect to are only 2.4Ghz. But I was successful by going into advanced wifi settings and changing the band setting from "Auto" to whichever band you want to connect to.''

/sigh and I guess that answers my question to see if this is still happening in the latest builds.
[Verizon LG G3] dcooterfrog:
Clear your voicemail manually then use Google Voice
[Verizon LG G3] j36047:
Delete
[Verizon LG G3] Reznor7:
Speakerphone volume is much better on 3/3, but my mic cuts out upon enabling it, so the other person can't hear me.
[Verizon LG G3] NatesLaw:
I 2nd this. Also, I clean-flashed 3/3 today (coming off 2/16 build) and don't seem to have any Lockscreen options avail in Settings.

Otherwise, seems wonderfully stable. Thanks to the devs!
[Verizon LG G3] someguyatx:
No lock screen settings in 0302 either, haven't tried speakerphone.
[Verizon LG G3] R2D2-AKU2:
This is not a new issue. I've had this issue randomly for all of cm13 and 12.1.
[Verizon LG G3] PhonePhapperBYAAAHH:
I think once Google Play Services is totally tamed in terms of battery consumption (don't know if that's a problem with Doze or what. Seems that it's not able to be optimized.) and the mic is fixed on speaker calls, CM13 for this phone should be all the way good to go. My proximity sensor is still busted too when I hold the phone to my ear for over 30 seconds or so. The screen stays off. Anybody else getting this one? I think if i clean flash, it should be resolved (haven't clean flashed since last month, waiting on snapshot release). Overall, best MM ROM yet.
[Verizon LG G3] ForevermanRGPC:
you can simply create a folder on the external sdcard,using the following folder-structure: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/If you already have existing backups, move them with a file-explorer from their current place to: /storage/extSdCard/Android/data/com.keramidas.TitaniumBackup/ Lastly, go to the preferences of TitaniumBackup, choose “Backup folder location” and choose the above specified folder.

Finish.
[Verizon LG G3] ToF_Itachi:
So updated to the latest nightly and now my Lg Infinim won't play audio through them after getting paired. It even shows (no media) and then when I try to watch a video or listen to music it plays through my phone. I'm assuming its my headsets right?
[Verizon LG G3] CaptainElwood:
No I think its CM, Im on the 3/4 nightly and have only intermittent BT. I was able to connect to my car stereo once, but not since, and have not been able to connect to my MS Band 2 watch.

I had recently come from 46a stock and figured this was just an ongoing bug with CM, are there past nightlies that did not have BT issues?
[Verizon LG G3] ToF_Itachi:
I just downgraded my nightly and the issue still isn't even fixed so I have no clue what happened to it.

Edit: I downgraded as far down as 2/08 and it works perfectly fine again.
[Verizon LG G3] someguyatx:
My Bluetooth has been working perfectly on 0302 with my car. Aside from speakerphone not working and the wifi sometimes not showing all networks it's a solid build. Hope the speaker phone thing is fixed soon.
[Verizon LG G3] R2D2-AKU2:
2 things broken in today's nightly (3/9):

Adaptive brightness doesn't work. When its on, the brightness slider does nothing. Turn off adaptive brightness and the slider works.

Notifications follow lockscreen rules even when unlocked. If you set lockscreen notification rules to hide sensitive content, the content remains hidden after the phone is unlocked. The only way to show content is to change the lockscreen rule to show all. Probably has something to do with this: http://review.cyanogenmod.org/#/c/134754/
[Verizon LG G3] someguyatx:
Yes I can confirm adaptive brightness is broken in 03/09, mine does the same thing as R2D2-AKU2

also speakerphone is still not working, rolling back to my 0302 backup
[Verizon LG G3] rohitece06:
Adaptive brightness is broken for me too but speakerphone works for me although I think volume is quite low for the speakerphone.
[Verizon LG G3] MaddMaxx636:
I am just wondering. Has anyone been having really bad battery life lately? Like with Android OS or GPS (Google Play Services) eating up battery? Also with the latest nightly adaptive brightness is broken for me too like other people have stated. When it's on the brightness is set in middle and the slider doesn't work but the slider works perfectly when it turn adaptive brightness off.
[Verizon LG G3] R2D2-AKU2:
I had bad battery life today, but otherwise it's not been too bad.
[Verizon LG G3] R2D2-AKU2:
I clean flashed back to 3/5 and the adaptive brightness bug survived clean flashing. I wiped everything (system, data, cache, dalvik) twice.
[Verizon LG G3] R2D2-AKU2:
WTF am I doing wrong? I clean flashed a second time, this time to 3/4, and this adaptive brightness bug still survived! How can this possibly happen? What am I failing to wipe? Is there some setting located on the sd card that breaks this?
[Verizon LG G3] Obaterista93:
I'm experiencing the same weirdness as you guys. I was running 3/2, decided to check out the AOSP rom that was posted. After clean flashing that, I did a full wipe and then restored my backup from 3/2 and now I'm having adaptive brightness issues too. Something is persisting after a full wipe from the newer builds that is affecting it.
[Verizon LG G3] Chevelle1768:
The only way I could fix mine was to flash back to 3/5 build (without wiping) and copy /data/misc/sensors/sns.reg to /sns/cal/sns.reg overwriting the file. Then rebooting.
[Verizon LG G3] R2D2-AKU2:
That's great news. Unfortunately, apparently because I clean flashed, /data/misc/sensors/sns.reg doesn't exist for me. Any chance you could share the file?
[Verizon LG G3] Chevelle1768:
Could restore if you have a backup or I have attached mine.

THE ATTACHED FILE IS COMPRESSED!
[Verizon LG G3] R2D2-AKU2:
I screwed up big time. First, for some stupid, dumb, incredibly retarded reason I thought you simply renamed your file with .zip at the end. So, obviously when I replaced it, it was corrupted and to top off the stupidity, I did not make a backup of the original file. Now it won't boot no matter what I try. I have tried replacing the file with the unzipped (real) sns.reg, clean flashing, adding it in via twrp, dirty flashing, clean flashing, dirty flashing over clean flashing, using 3/5, 3/9, 3/10. Nothing works. It goes to a black screen after the LG logo splash.

Also, on a clean flash, this file doesn't exist. It seems to be meant to be made during boot, but it won't boot without it. Some older version must have contained it. The oldest one on the download page is 3/3, other than a 12.1 snapshot.

I finally got it to boot by restoring a year old stock deodexed nandroid. Thank God it wasn't corrupt or something. I'm stuck. I've tried everything I can think of as well as losing a bunch of hours at work trying to fix this. Any ideas?
[Verizon LG G3] Chevelle1768:
Selinux issue?

Here are mine:

root@vs985:/ # ls -lZ /sns
total 24
drw-r--r-- 2 system system u:object_r:sensors_persist_file:s0 4096 2016-03-09 09:33 cal
drwx------ 2 root root u:object_r:sensors_persist_file:s0 4096 1969-12-31 19:00 lost+found
drwxrwxr-x 2 system system u:object_r:sensors_persist_file:s0 4096 1969-12-31 19:00 touch
root@vs985:/ # ls -lZ /sns/cal
total 32
-rw------- 1 root root u:object_r:sensors_persist_file:s0 0 1970-01-02 19:23 calb
-rwx------ 1 root root u:object_r:sensors_persist_file:s0 15360 2016-03-10 13:29 sns.reg
root@vs985:/ # ls -lZ /data/misc/sensors/
total 40
drw------- 2 sensors sensors u:object_r:sensors_data_file:s0 4096 1970-03-10 19:16 debug
-rwx------ 1 root root u:object_r:sensors_data_file:s0 15360 2016-02-28 09:36 sns.reg
root@vs985:/ #
[Verizon LG G3] R2D2-AKU2:
Thanks for getting back. I'm sorry, but unless you give me a tutorial, I'm not going to be able to tell you one way or the other. I'm working from a very basic level.

Also, one other thing I tried was installing the last 12.1 snapshot. It booted, went through the dalvik upgrade thing and then the same black screen.
[Verizon LG G3] IaKnightHawke:
I tried to post a message for help on the CM 13 forum to get help with a question about the advanced calling features setting related to Voice Over LTE. Does CM 13 have this setting yet, if so where? I am experiencing alot of dropped calls and Vzw tech support said that I do not have true 4g lte call ability with out this setting enabled and alot of dropped calls as result. I was active on the CM 13 forum but recently found I was unsubscribed from it for some reason. I therefore can't post anything there for a while again. Sorry to reach out to you but I saw that you are in Minnesota where I lived previously, I thought you could help me out on this. TIA, Gary Specs: LG G3 VS985 variant handset, 777 Kernel, CM 13 nightlies, last update on 3/3/16

Edit, I was trying to reach [MENTION=2385005]invisiblek[/MENTION] with this message as I could not post it to the forum, I thought . If anyone can help please. I am out of options here.
[Verizon LG G3] CaptainElwood:
Did you...

1. full wipe of everything but external sd (make sure your backups are on ext sd card)

2. flash 35b

3. flash version of CM from your last working backup

4. boot phone and immidiately go back to recovery

5. wipe, and restore the last backup you had?

I dont know whats going on but that seems like it would have to work
[Verizon LG G3] R2D2-AKU2:
1. No, I did not wipe interval storage. Many wipes of everything else. However, internal storage got wiped when I uprooted to 10b using the kdz method.

2. Yes. I was on 35b. I flashed it again to be sure.

3. Yes. The oldest I had was 3/3.

4. I think so. I'm not exactly sure what you mean. It won' wouldn't boot, but yes. I started the phone, get to the LG splash screen, then force reboot into recovery. Many times.

5. My backups are corrupted. Error 1 I think? Only a year old backup of stock deodexed worked. I think that had something to do with twrp. I upgraded to 3.0 so hopefully that won't be an issue inn the future.

So basically, even after urooting to 10b, which is a full wipe, then rooting and installing twrp 3.0, 35b bootstack, cm13 3/5 and open gapps nano, I continued to have the same issue. Immediately after the LG splash screen it goes black and that is all I get. Unbelievable. Currently I'm running skydragon. Stock roms seem to work fine but I hate it. It's slow and bloated. I can't believe people can put up with all these "enhancements" to the user experience that the manufacturers put on. Even stripped of the bloat ware it's slow and clunky as hell. I need it for work today but I'm going to keep trying to get cm or another aosp rom on over the weekend.

I've been running cyanogenmod since cm6 on my htc hero. I'm no Linux guru. Far, far from it. But I've had my share if situations like this and it never deterred me before. This is the first time I haven't been able to solve the problem, though.

---------- Post added at 05:57 AM ---------- Previous post was at 05:51 AM ----------

By the way, on skydragon (stock), there is an automatic brightness setting that seems to work so it's not like the actual sensor is broken.

Edit - after playing with automatic brightness inn daylight, it appears that it's borked after all. Does not respond to baseline settings. Seems to be 100% brightness all the time.
[Verizon LG G3] CaptainElwood:
Well there is always the option of using a KDZ/TOT back to 10b right? I still think that if you went 10b, got TWRP, flashed 35b, you would be able to restore a backup from a ROM made on 35b. Ive just never heard of something like this persisting through wipes and reflashing the bootstack.
[Verizon LG G3] R2D2-AKU2:
Its crazy but true. I did kdz 10b twice. I don't have a 35b nandroid, backup so I installed fresh 35b/cm13/opengapps and had the same issue. Then I did the kdz 10b again and then put skydragon on. The phone crashes randomly and every single time i attempt to make or receive a call. Its unstable and unusable. I also tried to put cm12.1 on after all that and it installed all the way through the "upgrading/optimizing apps" thing and as soon as it said starting apps it died.

I think I'm going to have to do a warranty exchange or upgrade my phone. I'm researching new phones now but there's nothing I really like from verizon.
[Verizon LG G3] dcooterfrog:
get a g2 on ebay I just picked one up on ebay as a backup.
[Verizon LG G3] PhonePhapperBYAAAHH:
Pretty sure this is due to the proximity sensor being totally non-functioning on the latest builds. You can tell when you make a call and the screen won't turn off when you put the phone to your face. Anybody else?

Edit: it is really weird for it to survive over a clean flash and downgrade, though. Seems that only restoring an old backup will fix it.
[Verizon LG G3] R2D2-AKU2:
I'm giving up. Phone is on 10b, ready to go back to verizon. It spontaneously reboots when I attempt to make a call or use the camera, and randomly reboots constantly. Something is completely borked. Thanks for all the suggestions, but its time to move on. I need a phone for work. Getting a new phone today.
[Verizon LG G3] PhonePhapperBYAAAHH:
Any physical trauma to your phone? I've been in a situation where my old device was GPS and camera borked across all builds and TOTs/KDZs, but it was because of internal hardware problems. Is it really even possible to mess up a hardware component (ie. Sensor, camera, etc.) so bad one time in your program that its fried across all reimaging? I'll have to test some old backups today. All this started for you from flashing 3/9???

---------- Post added at 05:01 PM ---------- Previous post was at 04:11 PM ----------

Yep. I restored back to 12.1 latest snapshot and the light/proximity sensor is completely botched from flashing any CM13 build 3/9 and forward.
[Verizon LG G3] gteknet:
OK I went thru the forum looking to see if any fix to the adaptive proximity sensor problem but can't see one, if this if been workout or any way to fix this. Unable to read my phone is been getting a pain.
[Verizon LG G3] j36047:
Yes...I fixed it by using the file that Chevelle 1768 provided.

Downloaded the sns.reg.zip using my PC

Moved it to my phone

Unzipped it using ES File Explorer

Renamed the /sns/cal/sns.reg to sns.reg.orig (for a backup)

Copied the unzipped sns.reg from Chevelle1768 to the /sns/cal/ directory

Rebooted

And now it's working on 3/4 build.
[Verizon LG G3] Chevelle1768:
I thought I tried it on a newer build and it didn't work. I will have to try again. That is why I flashed back to the 3/5 build.
[Verizon LG G3] j36047:
Shoot, sorry...I'm on 3/4 build! My bad...been flashing backups and old nightlies like mad all day trying to fix this. Updating my other post...
[Verizon LG G3] Nuke420:
This worked on my 3/5 NAND backup of CM 13. I'm wondering if it would work on the latest builds? Have you tried anything newer with this fix since you've posted this?

Thanks,

-n4-
[Verizon LG G3] j36047:
Haven't tried any newer ones. Had my fill of borked phones for the day & am winding down. Give it a whirl and let us know maybe.
[Verizon LG G3] R2D2-AKU2:
Yes and no. I did not dunk it or drop it. No, sir, far worse than that. When Chevelle1768 graciously offered his sns.reg file, I must have been daydreaming or something because I did NOT unzip it - I just deleted the .zip from the file name and plopped it in. For some insane reason, I was thinking that it was not actually a zip file, but just renamed so it could be uploaded. That was pretty dumb. But I was ready for an upgrade anyway, so I picked up a moto x at verizon (officially cm supported). Its a little smaller than the g3 and I like that. But yeah, I think that mistake qualifies as trauma. Completely borked the phone so badly that even kdz unrooted to 10b it would reboot everytime i made a call, started the camera and random reboots for no apparent reason. Probably other driver related triggers to rebooting too, but I didn't play with it much after that.
[Verizon LG G3] PhonePhapperBYAAAHH:
WTF though? You would think that wiping system and flashing a fresh build would overwrite everything. Especially useful in these cases where hardware is dependent on files in there. Sorry that happened to you like that, man. I'm starting to believe CM12 nightlies broke something where my GPS and camera wouldnt work across reimaging on my past G3 (this is my second one I'm typing from now). I guess I've turned to a whole new perspective on nightlies, no matter how stable they're getting, and becoming one of those scary stable/snapshot only people.
[Verizon LG G3] R2D2-AKU2:
I've heard, but thankfully never experienced in all the years I've been doing this (until now), that you can brick your phone beyond repair with software, but I always thought that was only for boot level stuff (wrong bootloader, radio, etc). I guess borking the driver is pretty low level.

Once on the g3 a cm13 nightly broke something and I had the no Sim card error. That survived through a nandroid restore of a 12.1 image and a restore of a stock deodex image (no kdz unroot). That took me a day and a half to sort out. After all that and a new phone (I got cm13 on my new moto x without too much trouble), I'm thinking I'll stay away from the nightlies for a while. It's running smooth as silk at the moment. I don't really want to upset the apple cart. And this is coming from a guy that flashes every single nightly religiously. I don't know how long that can last. It's kind of a habit at this point, like smoking.
[Verizon LG G3] PhonePhapperBYAAAHH:
I can confirm that this works. There must be something that changed in the later builds that corrupted this file. After a little testing, I can also verify that /sns/cal/ does not get wiped or changed at all across clean wipes of /system or any other wiping options or restores (its at the root, so it makes since to me now that wiping /system wouldn't remove these directories and then them be rewritten by a new image). These files at the root are obviously essential for hardware components to function properly and are probably not messed with much by system images/ROMs. Learned something new today about how Android works in that sense.

Edit: be sure to set perms for the sns.reg file to just owner rwx after you move it to that directory.
[Verizon LG G3] gteknet:
OK I will give a try TY

---------- Post added at 10:18 AM ---------- Previous post was at 10:15 AM ----------

TY

---------- Post added at 11:11 AM ---------- Previous post was at 10:18 AM ----------

there is not a sns.reg in /data/misc/sensors/
[Verizon LG G3] PhonePhapperBYAAAHH:
Download the file Chevelle provided on page 92 I think. Be sure to read the posts surrounding this. We've lost a device to this issue already.
[Verizon LG G3] gteknet:
Thanks Works but after reinstalling 3/13 goes back to brightness failure.
[Verizon LG G3] PhonePhapperBYAAAHH:
If you still have the device, do you think it will work again if you move Chavelle's file with adb to that directory or with TWRP file manager? Could derping that file have caused some sort of chain corruption? I will provide the needed files if an expert can tell us (or google it) which directories could have been affected.

Edit again: forgot you 10b'd and turned it in.
[Verizon LG G3] j36047:
Did you try replacing the file once again after the upgrade to 3/13?
[Verizon LG G3] gteknet:
Yes
[Verizon LG G3] j36047:
Thanks for the confirmation. No point downloading any more nightlies for me till this gets sorted out. Anyone know if this bug has been reported so it gets worked?
[Verizon LG G3] P013onEr:
Fixed Auto brightness in 3/13 build and sensor works well

Just delete /etc/sensors/sensor_*.conf except sensor_def_common.conf

then reboot.
[Verizon LG G3] Reznor7:
This worked perfectly for me. Thanks!
[Verizon LG G3] dcooterfrog:
0n 3/13 speaker phone is still not working. proximity sensor working again
[Verizon LG G3] Chris_Patterson:
Worked for me. Thanks for the post!
[Verizon LG G3] gteknet:
how you get to this here if /system/etc/sensors ?
[Verizon LG G3] CaptainElwood:
You could always try this. I accidentally borked my phone going from jasmine9.1 to CM and not flashing the updated 35b bootstack. That is a lengthy process but it got my phone back from what I really thought was a hard brick.
[Verizon LG G3] amirfida:
just go to cm file manager on the bottom right there is a settings icon click on it go to general settings then scroll down and change the access mode to root access mode and then go back to file manager from the top change the directory to / and then go in folder called etc and then in folder called sensors delete every file except sensor_def_common.conf and then reboot and sensors should work fine then. :)