yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] fixxxer0:
still no adaptive brightness or swipe

Tried the new 3/21 and still no adaptive brightness or swipe typing.

Def have to clean flash. Dirty =fc like crazy

Maybe my light sensor isn't working? I haven't heard anyone else complain about brightness sensors

Screen proximity in call also doesn't work... Maybe related to the light sensor. I tried to check sensor tester app and it doesn't detect anything.

Also while GPS works in navigation apps, GPS test says no fix, even though it gives an accuracy which means a lock
[Verizon LG G2] doublej713:
http://forum.cyanogenmod.org/topic/103962-no-gesture-typing-in-aosp-keyboard/. Try this for the gesture typing. Worked for me.
[Verizon LG G2] jesssiii:
BaNkS gapps moved to 5.1, which causes FC on 5.0 roms. Make sure your gapps are for the correct Android version.

VZW LG G2
[Verizon LG G2] ddzado:
I've flashed the CM12 Gapps. I'll just have to keep those around and flash after updates for now.

I've also notice the Lollipop V4a is having issues. Anyone noticed or found a fix?
[Verizon LG G2] cazafka:
I've been using cm12 20141212 gapps. Gapps was fc'ing with the latest rom release as well.

This time I went back to recovery and flashed gapps without wiping system and all appears to be fine now.

When i get home tomorrow I'll try comparing changes to system before and after flashing rom update.
[Verizon LG G2] jesssiii:
I couldn't get it to work even using the SELinux changer set permissive. It FC at boot. I had flashed the LoliViper test zip. That was on the last version of this rom. It's probably kernel related?

VZW LG G2
[Verizon LG G2] :
[MENTION=3727492]JackpotClavin[/MENTION],

Sorry to bother you, but I'm attempting to build from your kernel source. However, it's not building the DTB's for me. I know your release boot.img had them... any idea why it might not be building them?

I see that you removed the config value for it in the defconfig in a commit about cyanogenmod's devtree tool but not really sure what that is.
[Verizon LG G2] JackpotClavin:
Look in my github on g2-common. Under in the custom mkbootimg I had to change the directory path to the dt files for the new kernel source

Sorry I can't link it I'm on my phone
[Verizon LG G2] rockcipher:
Just had another bluetooth softreboot, and I have PM'd you my logs. It only seems to happen when I am connected to media and headset. I am running a clean flash of the 3/21 build.
[Verizon LG G2] :
Thanks for the info. I figured it out for fixing the build script that I'm using.

Apparently I need to do

./scripts/dtc/dtc -I dts -O dtb -o out/g2/msm8974-g2-vzw.dtb arch/arm/boot/dts/lge/msm8974-g2/msm8974-g2-vzw/msm8974-g2-vzw.dts
./scripts/dtc/dtc -I dts -O dtb -o out/g2/msm8974-v2-2-g2-vzw.dtb arch/arm/boot/dts/lge/msm8974-g2/msm8974-g2-vzw/msm8974-v2-2-g2-vzw.dts
./scripts/dtc/dtc -I dts -O dtb -o out/g2/msm8974-v2-g2-vzw.dtb arch/arm/boot/dts/lge/msm8974-g2/msm8974-g2-vzw/msm8974-v2-g2-vzw.dts

now to manually make the .dtb files so that I can use dtbtool to create the dt.img. I was also getting "failed to scan" errors from dtbtool until I installed dtc with apt-get install device-tree-compiler. I guess the script in the folder also needs it installed on the system.

At least now I have it making a bootable zip :)

Thanks for everything you do man.

---------- Post added at 08:23 AM ---------- Previous post was at 07:35 AM ----------

PA gapps from the 17th works fine, so does the cm gapps.

Banks gapps dated. I think the 15th or newer will fc.
[Verizon LG G2] jesssiii:
3-5-15 is the last BaNkS gapps that work.

VZW LG G2
[Verizon LG G2] abdel12345:
Im getting constant reboots on setup with no way of even getting into phone, I tried with a gapps package and without and same results. I read through a couple pages and saw others getting reboots too but i didn't see anyone saying they couldn't even get through the setup. I reviewed the directions and im pretty sure everything was right.

I originally cam from stock 39a. I used a guide to install twrp that would downgrade the aboot to 28a from kitkat (which the directions say either kitkat or jellybean is needed) and get a bumped twrp installed. After that i backed up my stock rom, wiped system, data, cache, and dalvik and installed the rom.

The first time I tried with the 3/15 pa gapps the second time i tried without and same results both times. Im going to try one more time and see what happens just in case i forgot something. Am I supposed to flash an older modem? (i saw its based off 39a now and that it should work on 39a radio so thats probably not it though).
[Verizon LG G2] Zaphod-Beeblebrox:
I assume we are talking about clean flashes? CM install script preserves gapps when present. Has done this for quite a while I thought. "dirty" flashes shouldn't require gapps flash, right?

---------- Post added at 09:07 AM ---------- Previous post was at 08:56 AM ----------

Hrmm. I just dirty flash 3/21 this way and got FC's ... re-flashing now with gapps-ll-20141109. I know its an older gapps set, but you know those things auto-update, right?

And the flashing of System/Gapps stopped my FC's.
[Verizon LG G2] 4rsenal:
I'm getting force closes whenever I attempt to get into the contacts app.. Anybody else?
[Verizon LG G2] jesssiii:
You using a theme? If so, try with stock.

VZW LG G2
[Verizon LG G2] zzandrewst:
If updating from the 3-04 build, would it be best to wipe data before stock flash, 3-21 flash, or both?
[Verizon LG G2] noll5326:
Since CM12/Lollipop I've had to flash gapps each time or I get constant FCs on boot; with CM11 I never did. It wouldn't be so annoying if I didn't lose all my widgets and folders on the Google Now Launcher in the process. Would be awesome if it preserved everything like CM11 did.
[Verizon LG G2] steveo17:
A random reboot when trying to paired with my car

https://www.dropbox.com/s/spao5x052ozjxu5/2015-03-22_00.41.zip?dl=0

https://www.dropbox.com/s/avvp58evtbryvs5/tombstones logs.zip?dl=0
[Verizon LG G2] Napa7m:
This worked perfectly.

Thanks
[Verizon LG G2] smb209:
Had a random soft reboot followed by a hard reboot. Captured a log after the hard reboot. Running the 3/21 build.

https://www.dropbox.com/s/l1hew2w25hndfcb/1426855425509.txt?dl=0
[Verizon LG G2] JackpotClavin:
You guys don't need to send me anymore logs, (but thanks!)

I have all the logs I need, unfortunately I still don't know what the exact cause is or how to replicate
[Verizon LG G2] jesssiii:
Yeah, I was listening to music on Bluetooth yesterday while browsing but had no issues.

VZW LG G2
[Verizon LG G2] koftheworld:
[MENTION=3727492]JackpotClavin[/MENTION] I would never pretend to be a developer, but maybe you should return to previous source for your builds until these issues are resolved or 5.1 is merged into cm and you have another host of issues to deal with. Your rom was rock solid prior to your lollipop source migration, and you've done an amazing job with the resources available.
[Verizon LG G2] :
I'm pretty sure JackpotCalvin is one of the handful of people who work the issues out for the new sources to eventually be merged/used by CM.

So, that kinda seems counterproductive.
[Verizon LG G2] Napa7m:
For what it's worth, I tested bluetooth on both of my cars and it worked fine. Haven't had one crash/reboot on this ROM.

However, adaptive brightness doesn't work, volume is very low, and the battery drains pretty damn fast - so ill be sticking to the LG based ROM for now.
[Verizon LG G2] koftheworld:
He's the only one doing anything with cm for the vs980 and not even officially. We still have no official maintainer. He is extremely skillful and can work out these issues in time, but right now he can't even replicate the issues on his own phone. Personally a stable release trumps one with soft reboots and no clear advantage over the other.
[Verizon LG G2] stelthy77:
If you want or need (like me) a stable release, run the 3/4 build.
[Verizon LG G2] crispy1:
Link?

---------- Post added at 11:08 PM ---------- Previous post was at 11:03 PM ----------

Still on 3/4 and it has been running awesome. Love it. Not brave enough to flash the new one yet.

One issue I am having and I'm seeking a resolution. Just recently my phone stopped deep sleeping. Wakelock shows Google services. I've rebooted, wiped dalvic/cache. Reflashed (dirty) 3/4. No dice.

Anybody know how best to diagnose and fix?
[Verizon LG G2] koftheworld:
This problem can be solved by installing DisableService from the play store and then enabling SystemUpdateService under Google Services Framework. You'll have to do this after every reboot.

Here's a link about it: http://xdaforums.com/google-nexus-5/general/script-google-play-services-battery-t3059585
[Verizon LG G2] JackpotClavin:
I still think the soft reboot issue is a problem with GPS rather than Bluetooth. If somebody can rename /system/lib/hw/gps.default.so to .bak and reboot and get me a log of this reboot with this GPS library disabled, that would be great. (Steveo tried this and didn't experience a reboot while his GPS library was disabled) that could be dumb luck or it could the root cause

I'm switching over to source-built GPS libraries for future builds and for CM12.1 so that *might* resolve the issue, but I'm afraid to promise anything. 12.1 is still a way's away at this point.
[Verizon LG G2] jesssiii:
For some of us there are no issues. I've not had any and [MENTION=3727492]JackpotClavin[/MENTION] isn't if he can't reproduce it. Since we're all on vs980 39A, is there any other differences we could find between ones with and without issues? I leave Bluetooth and Wi-Fi always on but not always connected. But I don't use GPS, I leave it set to battery saving. Is it worth comparing?

VZW LG G2

---------- Post added at 16:36 ---------- Previous post was at 16:10 ----------

http://downloads.blissroms.com/Gapps/5.0/

VZW LG G2

---------- Post added at 16:39 ---------- Previous post was at 16:36 ----------

I should turn on high accuracy first, right? I'll get the log, but haven't had any reboots.

VZW LG G2
[Verizon LG G2] HueyT:
Definitely GPS causing soft reboots and nothing else
[Verizon LG G2] jesssiii:
[MENTION=3727492]JackpotClavin[/MENTION], sent you a PM with log link.

VZW LG G2
[Verizon LG G2] crispy1:
Got it installed and testing now.

Thank you!

Edit: Works as advertised!
[Verizon LG G2] fixxxer0:
I'm also still having slow charging... Had this on the last version of crdroid as well.

Are other ppl really not having any of these issues?
[Verizon LG G2] Nafon:
For anyone to believe you have charging issues, you're going to have to prove it. First of all, go to a rom where you aren't having issues and screenshot the amperage you are getting and the current temperature of the phone. Then repeat the process on this ROM with the same charger.

If the phone is hot, it won't charge at full speed. Just tested this today. After backing up system and data and then restoring a different backup and rebuilding art cache, my phone was very warm and only charged up to 600mA. I put it in the freezer for a few minutes, plugged it back in, and was charging at 1600mA. Most of the people complaining about slow charging seem to all be using GPS navigation which usually heats up your phone.
[Verizon LG G2] fixxxer0:
Gladly.

Going to monitor with batt mon widget from 3c. so far im at 88% charge, while typing this and I'm getting 260ma @ 90deg F battery temp.

This is on my 1.6a charger with a cable that worked just fine two weeks ago. I know in the past I have used other monitors and registerd around 1400ma with the screen off
[Verizon LG G2] bbender716:
Easy surefire way for me to soft boot: clean flash, cm gapps, let all apps update, switch to high accuracy GPS, open maps, soft reboot every time maps is opened. Logs to come.
[Verizon LG G2] da_reeseboy:
I am unable to replicate that personally, so hopefully pulling a logcat while you open maps will provide JPC with some insight on what's happening. I did however notice when I check my GPS status in GPS test I get great accuracy but no locks ironically...
[Verizon LG G2] koftheworld:
i've had these issues even on stock 39a. as jpc stated, it might just be a product of the types of cables and chargers we are using. even so, i know that the phone is charging slower in between 39a (and 39a-based roms) and prior versions.
[Verizon LG G2] cazafka:
No soft reboots for me, I leave location set to high accuracy and use Google maps daily.
[Verizon LG G2] hardball 45:
I had never experienced this before. Dirty flashed the 3/21 update and it appeared as if gapps were not present...lots of Google FCs and no way to interface. Wiped and clean flashed rom and gapps and all working again.
[Verizon LG G2] JackpotClavin:
To people who have had soft reboots: were you ever on the stock 39A right before installing this ROM?
[Verizon LG G2] da_reeseboy:
No soft reboots here, I went to micromods extreme 1.0 (39a based) for sensors before this rom.

Edit: I guess it would be good to note that I've done this to 2 phones. One was dirty flashed and one was clean. It made no difference - neither have soft reboots, but neither get a "lock" on GPS either (see above screenshot in my previous post). GPS does work fine though for navigation.
[Verizon LG G2] techbeck:
So, flash this first....and test everything....

http://xdaforums.com/verizon-g2/development/vs98039a-stock-fw-t3051560

Then the ROM in this thread?
[Verizon LG G2] zman0125:
I am experiencing soft reboots and was on the stock rom by xdabbeb before your 39A build.
[Verizon LG G2] steveo17:
i was on micromod's stock based rom for sensors before coming to this
[Verizon LG G2] JackpotClavin:
Can you send me your sensor config file under /sns/reg/sns.reg?
[Verizon LG G2] steveo17:
doesn't look like i have that directory. where exactly would it be? i've seen it before, just can't recall where it is on my phone now
[Verizon LG G2] fixxxer0:
I get the same, but i have no issues with my GPS in apps (navigation/maps/weather, ect) or soft reboots
[Verizon LG G2] joedajoester:
I came directly from micromods 39a and I haven't had a soft reboot yet. Could be because I haven't used location that much and haven't touched Bluetooth. Overall this rom is fantasic, thanks for all your hard work JC
[Verizon LG G2] da_reeseboy:
Yep, same here. GPS works great, it just never sees a lock.
[Verizon LG G2] :
How can you be sure that GPS is working for navigation? Are you setting location to 'device only' before trying to navigate?

If not, then you could simply be navigating based off of tower triangulation... not GPS.

Navigation is pretty much the worst way to test whether or not GPS works on a phone.
[Verizon LG G2] da_reeseboy:
Working fine. GPS test is what I normally use. I only switched to navigation to see if it would accurately follow and direct me, not hop from spot to spot.
[Verizon LG G2] :
This may seem dumb, but could you try this app?

Since it's able to provide you with the NMEA strings, I believe it interacts with the GPS reciever a little more directly as I doubt that Google Location Services provide this to the apps. The other GPS app might be taking info from Google Location Services.

I'm curious if that app will show you a fix or not. If you could also click on the NMEA button it should scroll the NMEA mesages. They'll look like gibberish if you're unfamiliar with NMEA... But they should be strings starting with like 2 characters, then a bunch of numbers seperated by commas (yes there can be multiple subsequent commas without numbers), then an asterik followed by 1 or 2 digits which are a checksum. As the data scrolls, it should be pretty obvious if there is data corruption as you would see strings of characters that *really* don't belong with the general theme.

I imagine they'll be there. But if the NMEA test app shows a fix but the other doesn't, it's possible that Google Location services is just refusing to recognize that there's a GPS fix.
[Verizon LG G2] da_reeseboy:
Does anything show up in that that I shouldn't post here?
[Verizon LG G2] :
Satellite positions and info. I suppose given the info, someone could potentially deduce your location from it. So maybe, maybe not?

Suppose it depends how paranoid you are. It won't include anything like IMEI's or such for people to clone your phone or anything like that.

Mostly, I'm just curious if the first screen shows "fixed" on the bottom line and if the NMEA page looks right-ish.
[Verizon LG G2] da_reeseboy:
Okay, Ya I'm not worried about that. If someone wanted to find me, there are lots of easier ways.
[Verizon LG G2] :
Yeah, that all looks fine. That app also shows you as having a GPS fix. So there's that.

Unless they've added things into the API with 5.x that I'm not aware of... The API only provides a little bit of data for apps to grab. I imagine this is how the GPS test app is getting the info... without a fix.

The NMEA app has to hook into the GPS reciever driver somehow bypassing the API in order to get the NMEA data. The reciever definitely thinks it's locked on, here's a great explanation of the way the fix string works. Which is clearly there on your device. If it's not too much hassle, you could compare using that guide to where you actually are and your approximate height above sea level and see if it's at least close. Maybe it's so far off that GLS is rejecting it.

I'm speculating of course on the lower level interaction. But this is the only thing that makes sense to me.

I guess the thing that JPC would have to figure out though is why this would be the case... Or at least why Google Location Services is being dumb like that... But the hardware and driver *have* to be working.
[Verizon LG G2] da_reeseboy:
Thanks for the app by the way. I'll have to use that one in the future.
[Verizon LG G2] :
[MENTION=3727492]JackpotClavin[/MENTION],

Just wanted to tag you here. Over the last few posts it seems like the GPS hardware and driver are working correctly, but the Google Location Services aren't reporting the fix correctly.

I'm not really sure how this information gets fed to the service to come back out of the API... But it seems like perhaps the issue lies in that interaction. That could also explain some of the soft reboots if the Location Service is panicing.

Hopefully this helps some.
[Verizon LG G2] fixxxer0:
Yes its on device only.

I use it everyday trust me, anything other than actual GPS lock is unusable for navigation while driving.

Also I've been logging the charging current from my 3 chargers (all 1.2A plus) and none of them ever go above 500ma. No matter the temp. All of these chargers previously charged at or around their rated rate on earlier versions of the ROM (lolipop included).
[Verizon LG G2] natemup:
Hate to change the topic, but since Tkruzze just announced a hiatus and Banks is no longer compatible, what updated gapps source should I have bookmarked?
[Verizon LG G2] rockcipher:
I flashed a rooted stock 39A just before this ROM. Here is my sns.reg https://docs.google.com/file/d/0Bx0LedahvDLCOG1kMmtOWWNKYUE/edit?usp=docslist_api
[Verizon LG G2] ddzado:
I'm not getting the soft reboots, but I am also not seeing a fix on GPS. Before making the jump to 39A, GPS was fantastic for me.
[Verizon LG G2] met152:
I just installed the 3/21 [MENTION=3727492]JackpotClavin[/MENTION] firmware yesterday. I was previously on a JackpotClavin 4.4.4 build (KTU84Q) from October 2014 (Yes, it's been that long since I updated my ROM).

Here were my steps (some screw-ups along the way)

1. Backup in TWRP

2. Flash xdabbeb 39A bootstack from the resources thread

3. Wipe dalvik and data

4. Installed xdabbeb 39A stock lollipop flashable (xdabbeb 39A flashable

5. Booted ROM, added Google account, tested sensors, phone call ability, GPS lock ability.

6. Backup stock 39A including EFS

7. Wipe dalvik and data

8. Install JC 3/21 Lollipop build

9. Booted (forgot to install Gapps)

10. Downloaded and flashed 3/17 gapps (before reading about the force close issues)

11. Rebooted, worked through the force closes and got banks_gapps-L-3-5-15.zip downloaded.

12. Wiped dalvik, cache, data, system, and re-flashed 3/21 39A JC build + 3/5 banks Gapps.

I've experienced a few soft reboots and what I perceive as slow charging.

2 Reboots occurred prior to pairing any bluetooth devices. One was while opening titanium backup, the phone briefly (<3 sec) was unresponsive and then soft rebooted. I actually forget what I was doing when the 2nd occured.

2 reboots happened this morning, one after pairing to my car and while listening to music and one while disabling SystemUpdateService using the DiableService app.

No issues with GPS.

I'm happy to provide any logs or files to help with future builds.
[Verizon LG G2] RichSPK:
Maybe I've missed it, but has anyone compared charging rates on USB versus Qi charging? I'm beginning to think my phone charges faster with Qi since going to 39A-based ROMs.
[Verizon LG G2] koftheworld:
Exactly. I think it's just 39a itself. I am tempted to buy an oem charger just to see, but that's ridiculous.
[Verizon LG G2] :
They very likely made the battery thermal throttling more aggressive tbh.
[Verizon LG G2] jacob019:
coming from xdabbeb 39A, getting soft reboots on first boot, before I even touched it.
[Verizon LG G2] abdel12345:
That's how it was for me too. I couldn't even get past the Wi-Fi login screen on the setup.
[Verizon LG G2] fixxxer0:
I think it's just some kind of fallback to the default USB max of 500ma
[Verizon LG G2] :
Yeah, that's what the failsafes do. They're setup in the device tree's overlays usually. You tell it what temperatures to throttle at and to what values. It's entirely possible that they're just overly aggressive... or not present which would cause it to use the default values from CM's sources... which are probably VERY conservative just in case whatever device is built from it doesn't set them that the phone doesn't melt.
[Verizon LG G2] JackpotClavin:
Sorry about the bugs and inconveniences in the recent builds since upgrading to the 39A base.

I'm gonna take a few weeks off for a vacation from Android to focus on school, but will be back before you know it :)

If you wish to go to an older build from the pre-39A requirement, you are probably (I haven't done it but I'm sure you will) gonna have to go back to a KitKat modem and then install one of the older builds
[Verizon LG G2] TheUnladenSwallow:
Go ahead and get some rest man! I was waiting things out on stock 39a while the stuff got worked out anyway lol.