yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] EtherBoo:
Interesting thing about chargers.

I've never had good charging on anything other than the stock charger and cable. I know it makes NO sense whatsoever, but if I use another charger/cable, it has never charged at a reasonable speed (I'm referring to even KitKat days). I've found 2 car chargers that charge decently - 1 is a dual port 2.0 amp charger than I bought 3 of - and they all broke the exact same way. The other is a dial port 2.4 amp charger that works just as good as the AC charger. I've only used an extra LG cable I have from an insurance replacement I did.

It sucks because I bought some 10 foot cables and I can't use them because of how slowly the phone charges- it won't charge fully overnight it's so slow. What also gets me is Battery Monitor Widget with this phone will only show me 30 mA when charging, even if it's AC or USB plugged. I haven't been able to figure it out.

Otherwise, I'm running the 3/4 build with only a couple of very minor bugs that are so sporadic it's not a big deal. Battery life hasn't been this good in a long time - I can last a whole day again with heavy usage. I use BT without issue as well. GPS, Proximity, and Light sensors appear out of wack, but I had that on XDADB's KK ROM I used to generate a new sns.reg file. GPS wouldn't show a lock with GPS test, but it would find my location. Also, I'm traveling on business now and my GPS NEVER finds me out here (I'm in Maine right now), but it finds me fine at home. Prox sensor works, but it's wonky. It's actually much better on the ROM than it was on XDADBs, but still not perfect. Light sensor - well I just stopped using auto-brightness. Prox, GPS, and Light used to work perfectly, but I got a screen replacement and that seems to have thrown them off. Not sure if they weren't connected properly or what.

Anyway, enjoy your time off JPC. Best of luck in school and thanks for all your hard work. I know 3/4 is "alpha" but it's my daily driver now. Ridiculously stable for an alpha. Hell, I would think it's a snapshot it's so good.
[Verizon LG G2] crispy1:
On 3/4 still and recently lost Gmail notifications. All others work. Not sure if it is something I did. Any clues? I have to go into gmail and swipe down for new email to show up.

Did all the normal sync troubleshooting, sync on/off, clear data, reboots, etc.

A bit frustrating but not major. Any tips would be appreciated!!

--C.
[Verizon LG G2] Zaphod-Beeblebrox:
Just for the record, I've had virtually no trouble with your 39a. I suspect there are many like me who are enjoying the fruits of your labor with no issues, and just aren't vocal about it. Those with issues are going to be more vocal (not to be jerks, but just discussing how to fix it). I think that can sometimes lead to an incorrect assessment of how 'buggy' something is. If you only hear from the 1% who are having issues, and not the 99% who are trouble-free, it gives the wrong impression.

Anyway, I hope those with reboots figure it out. Meanwhile, I'm enjoying a re-boot free ROM from [MENTION=3727492]JackpotClavin[/MENTION]. Thanks!
[Verizon LG G2] :
Good luck man, hope everything works out with school.

Just curious, since you got the new sources booting. Did you have to change/revert anything in the CM sources to get it working? Or was everything in the kernel/device/vendor blobs? I'm looking at trying to rebuild another rom off of what you've done here, for features.

Thanks again man!
[Verizon LG G2] JackpotClavin:
My cm-12.0 sources will work, you'll need to cherry-pick this https://github.com/CyanogenMod/andr...mmit/ceb0707e139a146679d4bdd17be47451a577793d

into hardware/qcom/media/msm8974 or else your mediaserver will continuously crash and you won't have audio, camera, video playback, etc.

My last test build for cm-12.1 had pretty much everything working except for wifi, but that might have been due to making a dirty build (didn't wipe the out directory before building as I just wanted updated java packages), but wifi worked on the previous build

Just for the record: I'm not taking a leave because of people reporting bugs or anything, I'm just going on a vacation to focus on school (I did the same thing last year with CM11)
[Verizon LG G2] drlenny:
No prob boss! you've been awesome, we'll keep the thread warm for ya!
[Verizon LG G2] :
Thanks man, there's always one cherry-pick somewhere that's needed ;)

I don't think anyone thought anything like that... If they did, they just haven't been around long enough to realize people take breaks for school at fairly predictable times.
[Verizon LG G2] chiefwigms:
Flashed last night and no reboots for me... I did have two issues:

1) Alarms don't sound - my alarm volume is turned all the way up (priority is set to ALL)... it doesn't even vibrate (just wakes the screen) - was late to work today :)

2) Pandora isn't working - just acts like its playing and continually skips... this happened a bunch of times before

any thing I can change without having a new build to fix these?

n/m - the actual phone doesn't work either - can't answer calls, and the phone lags when trying to make them.
[Verizon LG G2] bbender716:
Posted in crDroid thread:

What I did that fixed GPS and rotation:

Use the 39a bootstack in the stickied thread NOT any other older versions or other 39a bootstack floating around or combination of other stacks modems etc.

Just download the one that's there now and forget anything else out there.
[Verizon LG G2] toebee76:
I know it doesn't help you much but Pandora and alarms are working fine for me. Surprisingly stable here.
[Verizon LG G2] chiefwigms:
I actually did a full wipe again, and reload - looks like it works fine this time (haven't fully tested it)... one thing I did last time was allow google play to restore the apps - this time I selected "new device", and manually reloaded all my apps (no backup) - that could be it.
[Verizon LG G2] :
Did you have viper installed previously? If so, did you wipe data?

With sound issues it's tricky, the new sources use slightly different sound drivers than the old sources did it seems. So any number of things... Old files, residual settings, etc could have caused issues.
[Verizon LG G2] KBizzle:
Flashed 39a bootstack

Wiped System, cache, and dalvik

Flashed XDABBEB's stock 39a, signed in to Google, opened up maps to get GPS lock. While maps still up and GPS still locked, I immediately powered down and booted to recovery.

Wiped System, cache, and dalvik.

Flashed rom

Flashed PA gapps mini modular 03/07

Flashed SuperSU 2.46. Probably unnecessary but I always do.

Boot into rom.

Been running for 3 days. No soft reboots. That's no **** either. GPS works just fine. Only thing I haven't tested was BT.
[Verizon LG G2] Lawlrus:
[MENTION=3727492]JackpotClavin[/MENTION]

Don't think you're getting enough positive feedback about this source but I'm using the new CrDroid build on your 5.0 frankenkernel, and everything is running great.

I can't try GPS because its always been busted on my phone but no soft reboots others are reporting, battery life is stupid good, and as with all your builds its smooth as butter.

Figured I'd have rotation issues per usual, so I flashed the 39a bootstack, micromods debloated 39a and had it rotate a few times, clean flashed it and its all gravy.

After a few more days on this ROM I'm going to go ahead and try your cm build, but I'm expecting the same flawlessness.

Beautiful work man. I'm not going to miss much about Verizon come november, but I will miss you, xdabbeb, amit sen, and quite a few non-dev people.

You are giving us what every other device wishes they had. They are still stuck flashing half busted assed 4.2 based 5.0 ROMs.

Many, many thanks.
[Verizon LG G2] jacob019:
Following up on my soft reboot issue. I'm using the phone with T-Mobile, so the CDMA side of things is unused. I suspect this may have something to do with the reboots. I tried the older version, and it works okay except no GPS lock and the CM12 theming is incomplete. After trying a few other roms on just about all the other basebands I came back to the lastest version of this one. Installed properly, but it still reliably soft reboots a few seconds after boot up.

I discovered a workaround to prevent the soft reboots:

1. After boot up quickly enable airplane mode. This stops the soft reboots. It took me a several tries to get past the setup menu and get to the air plane mode setting before reboot.

2. Open dialer, enter *#*#4636#*#*, Phone information, Set preferred network type to LTE/WCDMA

3. Turn off airplane mode

Oddly it can survive an immediate reboot after I do this, even though the network type setting reverts. If I wait a while and reboot, then the soft reboot problem recurrs, so I'll just do this every time I boot. I'm not sure if this is directly fixing it, or it's just a side effect of manipulating the settings. Either way, I'm happy that I can use this awesome rom.

Later I will try to adjust the build.prop to permanently set the network type.
[Verizon LG G2] :
Can someone who's getting the reboots try this build?

It's the same as JPC's I just stopped using the GPS in his tree and let it use the normal qcom one. It seemed to work fine on my phone, except that it's still not showing as having a lock in GPS test apps (even though it does). Also seeing some GCM crashes. I suspect that maybe there's an API mismatch or something.

I did notice that this one was a bit snappier for me on the first boot, so that might be indicative that it's running better.

http://d-h.st/QmO5
[Verizon LG G2] koftheworld:
Did you update cm source on your build?
[Verizon LG G2] :
Don't get too 'thanky' too quick ;) Not even sure if it improves anything for anybody yet.

Yeah it was synced as of yesterday. Left it building today.
[Verizon LG G2] steveo17:
would love to try this, but i'm stuck having to clean flash every build now for some reason. super f'ing annoying. only have this problem since 39A.

might kdz cause its just unbearable
[Verizon LG G2] :
Why do you have to clean flash each time?

Also, when you do KDZ (what KDZ are you using for 39a anyway?) you should get uatoprime's partition backup script. It's possible something's just getting corrupted.
[Verizon LG G2] steveo17:
no idea honestly. my phone wont boot after flashing a new rom unless i dirty flash.

i'm not sure what kdz i was going to do

whats this backup script you're referring to
[Verizon LG G2] :
It's the one here: http://xdaforums.com/showthread.php?t=2451390

Though, it can be REALLY bad if you try to restore something that you shouldn't. I've used the sns backup a couple times now. I notice that going from 39A based roms back to 12B based roms, that partition becomes changed and breaks things like rotation.... Not really sure why. I asked Blastagator to include that partition for backup in his next TWRP build though, so that should make it easier to restore with the right rom.

The only reason it shouldn't boot is:

1. You're not reflashing the correct bootstack to match the rom.

2. You're not doing a factory reset (wipe data,cache,dalvik) after new flashes. (Clean flash, I assumed you meant KDZ-ing each time)

Mostly #2 will make you hang at the LG screen.
[Verizon LG G2] steveo17:
well i know i'm on the right bootstack

the phone gets stuck at the boot animation though not the lg logo
[Verizon LG G2] koftheworld:
I will thank anyone I want lol. Seriously though thank you for looking at this. Personally, I went back to stock 39a after my softboot issues and have been too lazy to come back. I think I'm just waiting for 5.1 and volte. I know I'm sad. [MENTION=5559940]Lawlrus[/MENTION] will be disappointed in me.
[Verizon LG G2] Lawlrus:
I work retail. Takes a lot more than that to disappoint me lol.

You'll come back when you're ready, if at all. Use whatever works for you.
[Verizon LG G2] koftheworld:
I worked retail for awhile, so I completely understand.

I've been on this rom about 90% of the time since the original cm11 release. I love it, but strangely have been okay on stock right now (with a ton of disabled programs, root, etc.).
[Verizon LG G2] jacob019:
.

I tried it. On first boot I was getting only 3G data. I went to settings, mobile networks, preferred network type and changed it to LTE--the radio switches to LTE and BAM, soft reboot. I conclude that in my case GPS is not responsible for the soft reboots. I believe it is related to the modem itself. When I first boot up on stock rom there is no data. After a short while a message pops up that a sim has been detected and it's switching to global mode, then I get data. Perhaps the baseband is expecting some sort of mode switch before connecting to a GSM only network. I reinstalled JPC's rom, got the same reboots, used the workaround I wrote about previously, and now it's working again.
[Verizon LG G2] Xyriin:
Charging Issues

For those experiencing charging issues have you tried a dedicated charging cable?

Something like http://www.amazon.com/gp/product/B009W34X1I/ can't be used for data transfer but it ensures your phone can charge at the maximum rate. Please note that you probably want to have a wall charger that can handle the current draw. Personally I recommend just getting 2.1 A rated chargers and never having to worry about it again.

I purchased dedicated cables and some quality dual port chargers (ex. http://www.amazon.com/gp/product/B00BEJSRDI/ ) ages ago and they work perfect for everything. The same setup for your car can work wonders as well.
[Verizon LG G2] :
So same as before then.

You may want to kdz/tot flash though to be honest. So far you were the only person I'd seen with a reliable soft boot related to data. The others were random, without data issues.

Might be something else going on with your setup.

You might also be the only person using the VS980 with T-Mobile as well, which could be causing different issues.
[Verizon LG G2] fixxxer0:
yes i have 3 such similar chargers, and all of them are charging other devices just fine at the full rate. but when you plug in the phone with this software, no good - back to 500mah charge rate.

its easily verified that the rate is ~500max because if the phone is next to dead it takes about 6 hours to fully charge it (3000mah battery).
[Verizon LG G2] ddzado:
Any idea how to get tap and pay working?
[Verizon LG G2] da_reeseboy:
I think you'll have to go back to an older build on the 26/27a modem bootstacks
[Verizon LG G2] Xyriin:
What about the cable? The charger is less important than the cable since the actual charger has nothing to do with the actual charging rate, only the device and cable. Not saying it isn't the phone but the issue could be due to the device maintaining some of the cable for data use. The specialized cable essentially forces everything into charge only mode.
[Verizon LG G2] fixxxer0:
yes the cable as well.

i have cables that do not exceed ~500 as well, and those are typically the older thinner gauge wire ones.

again you are missing the point that the charger and cable is outputting the rated current on other devices, just not with this phone. while it previously worked fine on this phone, that to me is the smoking gun that it is something software related.

also to rule out any crazy software drain that would be counteracting the battery charged I shut the phone off and calculated how much charge I get in one hour. only charged 20% from 50%, which on a 3000mah battery is about 600mah. Give or take the percentage point and other non linear variables
[Verizon LG G2] soapinmouth:
Check your alarm and see what ringtone it is using, default is none when I first installed.
[Verizon LG G2] da_reeseboy:
Before today I've had no issues. But this morning I had 4 soft reboots (not complaining by any means). Every one of them was while I was on the road driving. I then switched my GPS from high accuracy to off, then to device only. I didn't get another soft reboot (yet) since then.

I'm on the 3-21 build. Anyone else with soft reboots try switching to device only?
[Verizon LG G2] jacob019:
I'm trying to edit ro.telephony.default_network in build.prop, but the changes just don't work. I also tried editing settings.db with an sqlite editor, but it always reverts to 10. I've done a ton of searching and tried everything but I just can't manage to chnage the default network. Any suggestions?
[Verizon LG G2] ddzado:
So I'm stuck trying to flash back to a pre-39A version of this ROM.

Steps

1. Installed 26A

2. wiped data/system/cache/dalvik

3. Flash the March 4th build.

The error seems to be with loki vs bumped.

"assert failed: run_program("/system/bin/loki.sh")==0

E: Error executing updater binary in zip '/sdcard/Download/cm-12-20150304-vs980.zip'

Error flashing zip '/sdcard/Download/cm-12-20150304-vs980.zip' "

Any idea?

[edit] added loki assert error.

[update] There is no loki.sh at that location... anyone got some loki I can adb on?
[Verizon LG G2] Lawlrus:
[MENTION=4965249]ddzado[/MENTION]

You need to flash the 12 bootloader zip with the 26a bootstack.
[Verizon LG G2] ddzado:
I finally figured that out. So I just flashed 12b bootstack. Could I just flash 26a over that and accomplish the same?

[update] nvm... I'll just flash the bootloader.
[Verizon LG G2] Lawlrus:
You can flash the 12b bootstack or you can do what I do, and keep the 26a bootstack. You do that by flashing it with the 12bootloader. That will keep your 26a radio and stuff.

Until these 5.0 kernel based builds, that's what I did. Then you can rotate with modems from 26a to 12b for the different types of kernel bases.

Doubt I'll be leaving these bases though because its running fantastic for me on crdroid. Battery life is stupid.
[Verizon LG G2] ddzado:
So I went back to pre-39A land. I tried getting v4a installed (lolliviper) and it fcs like crazy.

1. Wtf? This was working before.

2. Is there a simpler way to get it to stop besides flashing the CM build again?
[Verizon LG G2] :
You could look at the instal script in the zip and manually undo whatever it did. However, I'm sure it deleted files, so it'll be hard to undo without the originals.

Probably easier to simply reflash the rom.

*edit*

On another note, I found some additional commits it looks like for hardware/qcom/gps on googlesource as well as CAF. I linked CAF because it's easier to read for me than googlesource. I'm thinking that merging some of these commits might help with the selected GPS issues (possible soft boots, no lock being shown in apps) as some of the commits are affecting the GPS location apis.

When I get home later today I'll try to merge some of these in and see what happens. Unless someone else can weigh in to say I'm barking up the wrong tree. Basically, I'm kinda figuring that since GPS works fine when built straight off of AOSP with LG's sources (the way the 39A stock images are supposed to be built per the LG source), it's gotta be something between googlesource commits and CM commits. Kinda leading me down this rabbit hole right now.
[Verizon LG G2] Xyriin:
I completely understand your point. However, your previous post indicated that you had this issue earlier ( "Had this on the last version of crdroid as well") which means it isn't a new problem with this particular ROM. It doesn't seem to be occurring for everyone either which makes the 'smoking gun' something specific to your device. It's either a hardware problem or a combination of software you've tossed on your phone.

I'm trying to help you troubleshoot and point you in the right (or at least not wrong) direction but you seem stuck on this particular ROM being the issue even when you've experienced it on another ROM.
[Verizon LG G2] :
I feel like there's a bit wrong here.

As far as I recall, no rom besides stock on this phone has ever charged at over ~600ma while powered off. Not sure why that's a surprise or an issue. If I'm not mistaken, for a while AOSP roms wouldn't even charge if the phone was off... Has nothing to do with this specific ROM. It's a hardware/kernel/driver limitation that hasn't been worked out yet... I also don't believe anyone's really concered enough to bother trying to fix issues with charging while the phone's powered off. It's a smartphone, who really powers it off?

How are you calculating this 20%-50%? Based on the value it shows on the screen? This isn't a percentage coming straight off the battery or anything, it's a value that's being calculated by the phone. And can be pretty inaccurate. Don't get me wrong, it's not a bad estimate, but they don't put high-end power meters into these things... Why would they, if the phone dies because you thought you had 10% battery left but you really only had 1% it sucks... but is it really worth the cost involved with better sensors? Not really. This also plays into why your phone will sometimes report 100% battery for like 30-45 minutes then finally start dropping. It's not really a linear representation.

If you're trying to get the phone to charge at full speed, you could attempt to charge the phone with the phone on, while running a battery/charging app that actually shows you the current draw from the sensor. There's a few of them, I've used in the past because I didn't trust that my phone was charging at full speed either back on KK roms. It would fluctate a bit, but that's not really surprising.

If you're *really* that concerned about it, you could always use a multimeter with a rigged together extension cord to find your exact draw. But really, why bother?
[Verizon LG G2] fixxxer0:
Lol the bottom line is my phone used to charge from almost dead to full in about two hours. Now it's about 6. The calculation I did in an hour is obviously not perfect, but it's very close.

I'm not talking about a few minute difference here. I'm talking 3x longer. This happened immediately after an update, it was not a gradually wearing out of the battery or anything.

And yes it started around the 3/4 update when I switched bootstacks. Anyway, I have some time this weekend and will go back to stock kitkat and test it.
[Verizon LG G2] koftheworld:
This is exactly my situation. I've gone from certain short charge times to much longer. Also, the phone no longer keeps up when I use navigation in the car. I've used the exact same cords and chargers as well as not changing other conditions such as phone position in the car. This is an issue with 39a.
[Verizon LG G2] :
So just a quick update.

I don't think it's just typos/missing commits like I previously did.

After looking at the source for hammerhead (pretty similar to us) they have a bunch of qmux stuff that seems to be needed. We have it on our stock builds as well. I'm guessing that with the newer modems this is needed now.

I'm syncing the aosp sources now, so that I can see what stock did to get everything working and try to reverse engineer it from there.
[Verizon LG G2] jacob019:
Thanks for the update. Really glad to know that development continues. You will be a hero to us all if you can solve the stability issues.
[Verizon LG G2] darker_slayer:
While I agree that the battery percentage indicator in software isn't a perfect way to predict this, at least for a rough estimate your math is off

20% -> 50% is a 30% increase in an hour

30% of 3000mAh is 900mAh

Within a timespan of an hour indicates your charging at 0.9A (on the phone) with a 10% loss on the charger could be 1A at the charger. Not sure how much loss a charger has. Car chargers are DC DC? Wall probably has at least 5 or 10% like most AC-DC conversions
[Verizon LG G2] fixxxer0:
I wasn't that clear in my original post. It was 50 to 70=20
[Verizon LG G2] darker_slayer:
Oh, well nvm ;) Reading was never my strong suit
[Verizon LG G2] fixxxer0:
Okay so I flashed a stock KK 4.2.2 12B (rooted) and my charging works at full speed again!

Getting 1600mah with the screen on and its clearly much charing faster! finally! but again the light sensor, prox and rotate arent working, but gps is fine. my phone is so finicky lol. going to try going back to a 39A stock and see if everything comes back magically.

of course in my brute force rebooting into recovery, i somehow managed to damage the volume rocker buttons and now they stick. so this will be another adventure in hardware repair.