yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] JDROIDS:
This worked for me! I was having the same issue and I followed these instructions except I left out the MNC. I changed one of the current Verizon APNs which was already selected. Still works after reboot!

Thank you for the fix [MENTION=4375253]juancp[/MENTION]! Thanks for the perfect ROM [MENTION=3727492]JackpotClavin[/MENTION]!
[Verizon LG G2] stelthy77:
Just upgraded from your last "M" build of CM11. So far so good. MMS seems to be working fine without any changes, using Evolve SMS. I did have issues with CM11 and MMS that was resolved with Evolve SMS, and that seems to have carried forward to this build of CM12.

Bluetooth streaming was good. Performance was a little chunky at first, but is fine after another reboot.

I'll post again after a few days, as to performance and Battery Life. With CM11 for some reason I always have battery life issues, with less than 2 hours of SOT, unless I do a clean install, then i get 4+ for a few days and then back again to 2 hours, with Android OS, Google Services, and Android System being the largest Battery users.
[Verizon LG G2] steveo17:
Anyone having proximity sensor issues when on a call?
[Verizon LG G2] JackpotClavin:
New build from earlier this morning. It has a few radio-related patches that I hope will fix MMS for those who have had issues with it. Also synced up with the latest sources

Can somebody comment on if the new build has fixed their MMS woes? If not, try reverting your APN/whatnot changes to the default if you changed it to try to get MMS working (I just want to make sure a change made isn't conflicting with the changed config settings of the new build, just spitballing to try to fix MMS...)

I'll add that bootanimation patch for the next build (probably over the weekend)
[Verizon LG G2] keever25:
Really liking the ROM. Only question, even though I toggle off the vibrate on touch option under sounds, the soft keys still vibrate on the navigation bar. Does anyone know how to turn this off? Thanks
[Verizon LG G2] sp44:
I also get this. I also can't get smart unlock (face) to work.
[Verizon LG G2] markcyst:
I'm on 26a running the last jpc cm11 nightly. I tried flashing the alpha build, with gapps (and without). Just going into a bootloop (waited an hour). Tried multiple times, no luck dirty flashing. Anyone else manage a dirty flash?

Or am I missing something
[Verizon LG G2] heleos:
Why on earth would you dirty flash an LP build over a KK build?
[Verizon LG G2] stelthy77:
I did and it worked fine. I am also on 26a.

---------- Post added at 07:40 AM ---------- Previous post was at 07:34 AM ----------

Because jackpot told us we could:

3. You have to be on a KitKat modem and bootstack with a 12B aboot, if you are current running my CM11, you don't have to change anything, just flash and reboot like you would any other ROM in this thread (don't forget you'll need Lollipop Gapps)
[Verizon LG G2] heleos:
Well don't I feel like a ****! Sorry about that. Next step would be to clean flash if the dirty didn't work
[Verizon LG G2] JackpotClavin:
Which gapps did you use?
[Verizon LG G2] zzandrewst:
Is any one having problems with titanium backup? Mine says it can't detect root... Ran a root checker and it says I have root. Any ideas? I have uninstalled and reinstalled multiple times and tried on the last build and the current build of the ROM. Love the ROM, thanks for the hard work!
[Verizon LG G2] pinecone:
Did you go to Developer Options - Root Access and change those settings? That's what I had to do.
[Verizon LG G2] zzandrewst:
That did it, figured it was something simple. Thanks!
[Verizon LG G2] KnappyRoot:
Installed latest build and MMS was not working out of the gate. After changing the APN settings detailed a few pages back, it seems to be working (using Google Messenger at the moment, will be switching to Textra soon).

My buttons also vibrate after I have unchecked (re-checked and un-checked again) the vibrate on touch option. Is there another option somewhere I am forgetting about? Touch sounds are also unchecked.
[Verizon LG G2] jesssiii:
What bootanimation patch?

VZW LG G2

---------- Post added at 05:40 ---------- Previous post was at 05:34 ----------

I didn't uncheck the vibrate, but rather turned it way down under, I think, the volume. It's one of the sliders. I like just a little vibration, but if you turn it all the way down it won't vibrate. It's linked with the system sounds.

VZW LG G2
[Verizon LG G2] markcyst:
Used regular cm12 gapps. I can try another

---------- Post added at 10:46 AM ---------- Previous post was at 10:44 AM ----------

I haven't clean flashed since I had my original moto droid unless it's 100% necessary (it never really is)

Not going to start now :)
[Verizon LG G2] bouchigo:
What, you don't know about it??? ;)

Patch/Thread link: http://xdaforums.com/android/software/arm-arm64-android-5-0-lollipop-t3032247
[Verizon LG G2] mmoogle:
If you read the linked CM and AOSP Gerrit pages you'll find that there isn't really a problem. AOSP already rejected the patch and it looks like CM is headed that way too.
[Verizon LG G2] bouchigo:
I' ve been building my own cm variant for months now, and haven't had a single bootloop; I'll just let them hash it out as it's really a non-issue for me. We'll see what they come up with/discover in the end.
[Verizon LG G2] soapinmouth:
I haven't tried the new build yet, but I've had no issue with the last as far as as mms, I just sent three in a row and it was pretty quick to send too. What upgrade path did everyone come from that is having issues? What baseband? I just came from the other cm12 flashing the 26a baseband than this rom.
[Verizon LG G2] keever25:
I also noticed you can turn the vibration down with a slider under sounds, but this also turns down ALL vibration, including for incoming notifications. i can't seem to find a way to turn the navigation soft key haptic feedback off without turning down the "system" vibration. I belieev it should be the check box previously mentioned, so this may be a minor bug to address. Thanks.
[Verizon LG G2] jesssiii:
No, didn't. I always flash a google bootanimation with every rom. Does this mean I wouldn't have to worry?

VZW LG G2
[Verizon LG G2] markcyst:
Tried regular cm12 gapps, and just tried PA's gapps. Still stuck in booting. I'll keep trying
[Verizon LG G2] bouchigo:
They are two separate things. What you're flashing is the actual boot animation, the patch is the binary file that controls how the boot animation is displayed, whether sound is allowed, etc.

Like I said, I haven't personally experienced any bootloops during boot, but I also don't use cm's stock bootanimation.
[Verizon LG G2] patrickneville:
24a and latest build

should I update. to 26a or 27a, and if so, how should I do that? last time I flashed a radio I ran into lots of issues
[Verizon LG G2] xttapolatakettle:
I, too, am skeptical about flashing random basebands and bootstacks. (Chalk it up to OCD.) Personally, every so often, I like to do a clean install:

1) Make sure important data is backed up and synced.

2) Revert to stock via KDZ method (latest 27A KDZ can be found here).

3) Ensure GPS LOCK and AUTOROTATE work.

4) Stump Root via brute force method.

4) I like Freedom One Click Tools for recovery. A lot of people recommend AutoRec, but I've had softbrick bootloop problems with AutoRec in the past.

4a) For TWRP 2.8.5.0, replace the recovery.lok in Freedom One Click Tools with this one.

5) Install JPC's latest goodness from recovery. (Also GApps)
[Verizon LG G2] markcyst:
Should I upgrade my TWRP before trying to dirty flash the alpha? I'm on 2.8.0.1
[Verizon LG G2] soapinmouth:
I have this weird issue with both cm12 roms with bluetooth audio in my mazda, music always starts on connect, which is fine, but when I pause the music I cant hear audio from any app not just music. Also trying to navigate while a song is playing tends to make audio all funky. Doesn't happen to me on stock
[Verizon LG G2] stelthy77:
That is my version, and I dirty flashed OK.

Here are the steps I followed:

Download JPC's Alpha build, check MD5.

Download CM12 Gapps

Reboot to recovery

Backup phone using TWRP

Install JPC Build

Install Gapps

Wipe Dalvik and Cache.

Reboot to system

Wait 30 minutes for it to boot and upgrade. (I don't know if it took 30 minutes, but it took a while.)

Phone was not quite right, slow and chunky, so I rebooted again and it was much better after that.
[Verizon LG G2] zman0125:
Can I dirty flash jpc if coming from the official cm11 12b?
[Verizon LG G2] JRJ442:
Doubtful. You'd have to flash the 26A baseband first. Doing that, then dirty flashing this over an older Android version might cause a security boot error. Personally I'd just do a full wipe, flash the baseband then this ROM and Gapps. You could always try dirty flashing and see, but make sure you know how to get into recovery manually to clean flash everything in case issues arise
[Verizon LG G2] zman0125:
By manually getting into recovery do you mean by holding the power and volume buttons? Also If issues arise could i restore my 12b backup as is or would I have to flash the 12b boot stack?
[Verizon LG G2] da_reeseboy:
I've noticed that my ringtone seems to play at a faster than normal speed. I initially had a custom ringtone so I thought that was it and switched to a stock one, but that one is doing it too. Is this happening to anyone else?
[Verizon LG G2] zman0125:
By manually getting into recovery do you mean by holding the power and volume buttons? Also If issues arise could i restore my 12b backup as is or would I have to flash the 12b boot stack before restoring?
[Verizon LG G2] JRJ442:
Yes by holding the buttons. I'm not sure about the restore to get out of it. Could work, maybe not. Both times I've been in a security boot error I've just done full wipes and a reflash to get out of it.
[Verizon LG G2] zman0125:
Alright so I had to do a full wipe (rather than a dirty flash)...

Everything is working well except I cannot get a GPS lock. Sorry if this has been covered previously but any tricks to getting this working?
[Verizon LG G2] JRJ442:
Flash a stock based ROM, like xdabbeb's. Boot up, sign in. Download maps. Open it and ensure you get a good GPS lock. Go back into recovery, clean flash this ROM and Gapps again. Restoring this ROM may work after xdabbeb's, but way back when with Mahdi I had to do another clean flash.
[Verizon LG G2] z0mghii:
Is it me or is touch on vibrate broken? I can't get the back/home/recents buttons to stop vibrating on touch.
[Verizon LG G2] jesssiii:
I never turn it off, but turning it down to 30% worked for me. So I'd assume you could use that vibration intensity setting to turn it to, say 1, or maybe even zero would work.

VZW LG G2
[Verizon LG G2] z0mghii:
Problem with that is I want it to vibrate on call and texts.
[Verizon LG G2] finger11:
Did you go from Mahdi to this ROM? I'm still running Mahdi and having some issues like boot loop when it overheats (GPS+plugged in to my car) and I've been stalking this thread for awhile as my next daily driver and good to see the kinks being worked out.

If you did go from Mahdi to this ROM do we basically have to go through all the Steps in the instructions on the first post? Thanks man.
[Verizon LG G2] jesssiii:
From Mahdi, just clean flash this rom.

VZW LG G2
[Verizon LG G2] finger11:
Seriously?? I'm stoked. I figured I'd have to follow this at the very least:

Note: if you are already on 24A, 25A, 25B, or 26A, root it, and proceed to step 5

But if not, I'm gonna give this a go on Sunday. Thanks!
[Verizon LG G2] JRJ442:
Like [MENTION=2861395]jesssiii[/MENTION] said, just a clean flash and you'll be fine. In my post I was talking about when we were running JB kernel based ROMs like around January 2014. Jumping to KK based, the sensors had trouble working back then. So you'll be good with just a clean flash.
[Verizon LG G2] finger11:
Awesome. Yea I remember having to flash the stock ROM to get the GPS lock then put Mahdi back on.
[Verizon LG G2] keever25:
Yes, it seems to a small bug. I also tried CR Droid rom based on these sources, and it does not have this problem, so it should be an easy fix. By the way, this ROM in this thread is an AWESOME ROM. Love it.
[Verizon LG G2] jesssiii:
I don't have this issue, I turned off vibrate on touch under sound / other sounds and it no longer vibrates touching the soft keys but still vibrates with calls and notifications. Am I not understanding what you're trying to say?

VZW LG G2
[Verizon LG G2] z0mghii:
I have that setting turned off and my phone will vibrate when i hit the back/home/recents button but nothing else. I didn't have this problem on the 15th build, maybe I could try reflashing but it seems like there's another person having the same problem as me?
[Verizon LG G2] markcyst:
Is anyone able to get the 17th alpha build to boot?
[Verizon LG G2] heleos:
I'm on it. I actually haven't seen anyone not able to boot it. Are you sure your on a kk modem?
[Verizon LG G2] markcyst:
I'm running the alpha from the 15th. I didn't try the initial alpha posted. But for whatever reason, the 17th build just will not boot.
[Verizon LG G2] HueyT:
Check MD5 as it may be bad download? 17th alpha is perfect for me (and sounds like most people) :good:
[Verizon LG G2] markcyst:
Yup, MD5 is good. Tried downloading from a few other computers just in case. No big deal. The 2-15 alpha got me over to lollipop on a dirty flash so I won't complain :)
[Verizon LG G2] koftheworld:
Don't you think the dirty flash between os versions might be the issue lol?
[Verizon LG G2] Lawlrus:
Preposterous!
[Verizon LG G2] jesssiii:
17th? My about phone says 15th... And it was the second release. There's another one? How'd I miss it? Where?

VZW LG G2
[Verizon LG G2] da_reeseboy:
He updated the link -

http://xdaforums.com/showthread.php?p=58847326
[Verizon LG G2] markcyst:
How do you think stock phones get upgraded over the air? Why would JPC explicitly say a dirty flash was fine in the alpha post?

Unless there is something like when we came from the official CM to JPCs, you don't need to clean flash.

How do you explain the fact I did successfully dirty flash between os versions? How would you explain the fact I haven't clean flashed since 2010 (unless it was actually required)?

---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------

JPC is adding the updates to the alpha post, not the first post yet.

Goto first page, click on the alpha build link.

---------- Post added at 09:47 AM ---------- Previous post was at 09:35 AM ----------

This directly from a cyanogen developer.

"Ricardo Cerqueira

2 years agoEditedPublic

For f$%k's sake... We intentionally left placebo operations out of the CM OTA updater, and explicitly wrote one click upgrade. So now we get:

1 - people complaining about having to reboot twice in order to run those same placebo operations because the updater doesn't

2 - "Improved" replacement apps that "installs AND does placebos, all in one".

FML, I don't think even the mythbusters could overcome the "conventional wisdom" when it comes to Android.

People can do whatever they want with their devices, but it does piss me off to see people write things to the effect of "I'm running an old version because I don't want to lose my data to do another upgrade" after being mistakenly convinced that it's a requirement."

If you want to waste time clean flashing when you don't have to, fine. But please don't try mocking those of us who follow facts and reality, not placebo OCDs ;)

When you keep spreading the myth of clean flashing, triple wiping, cache clearing, startup apps, etc.. You are hurting the community. When people don't want to lose data, and you ignorantly tell them clean flashing is required, you convince people not to upgrade, and eventually, not to even bother with custom roms on their next phone. Which in turn will give our wonderful developers, like JPC, less of an audience or whatever the reason is why he does this for us :) . You also cause Cyanogenmod to lose donation money, and less ad revenue for sites like XDA

Unless their is something that will prevent a dirty flash, it is never necessary or helpful to wipe before flashing. Stop spreading lies that hurt our community
[Verizon LG G2] jesssiii:
Thanks guys! What's weird is I remember reading his post about the update. If I have time on my break at work I'll have something to do now.

VZW LG G2
[Verizon LG G2] koftheworld:
You didn't read what he said. He said he got to lollipop from a different os version. JPCs cm12 is only for Loki-based kk basebands, so therefore can be an issue for those dirty flashing from a different rom not from the same base. Dirty flashing is not a definite no, but considering the flashing situation on our phone it is certainly something to consider before switching between different roms. There is no ignorance there, just practicality.

Also, consider the state of the questions these developers get. Most of the people who have major issues are those that either dirty flash or restore apps with titanium (or similar).

Honestly, people should pause more and flash less. If they do end up flashing, maybe they should take a step back and consider their phone situation before asking why their phone won't work (not saying this individual did that).

Fyi jpc said dirty flashing between his cm12 builds was fine, but he couldn't 100% endorse going between another rom and this with a dirty flash. This is not a normal cm12 rom with a normal cm12 update cycle.

Stock phones getting otas is a gigantic pain for oems. If you read the comments for people who take them, they don't always go as planned. Many end up doing a factory reset afterwards because of these issues.

In conclusion, let's just keep flashing recommendations with the actual developers rather than cluttering up their threads with nonsense.
[Verizon LG G2] markcyst:
I'm doing just that, you do NOT need to wipe before flashing unless directly stated by the developer. JPC has stated multiple times in this thread you do NOT need to wipe before flashing to upgrade his rom. Cyanogen even added in an Updater into CM that took the upgrading out of our hands completely to simplify the process even more, and people still kept the myth alive.

Going from one Android version to another does NOT require wiping. Every now and then a bug or piece of code will not do well with a dirty flash, and the rom developer will almost always warn us about it.

JPC said no wipe was required, and it wasn't.

The clean flashing myth came up around the same time that custom ROMs really started taking off on the Moto Droid, along the myth of triple wiping and running apps causing android to slow down. For some reason, even after developers explicitly stating the opposite, people refuse to listen to them.
[Verizon LG G2] Lawlrus:
I've never had issues with a clean flash, can't say that about some dirty flashes, so how is that hurting the community? "Unless their is something that will prevent a dirty flash" right there you stated you can have issues.

Did I say that you can never dirty flash? Nope, I cracked a joke about people that posy issues on a dirty flash, just like I do about people that post issues on custom kernels

We all know, well should, that dirty flashing can cause issues. Some devs require a clean flash before posting a bug report. Some devs also ask you to wipe cache and dalvek before rebooting, seems more kernel devs than ROM, but regardless they are out there.

Sure some people back up SMS or whatever else as data, but really? To assume that the vast majority of people that dirty flash are not just being lazy with restoring their 150 whatshangoutmyfacespace apps? I don't believe that.

Then again that's my opinion, more over so is this wall of text you typed up. Less you have more source then one cm maintainer talking about the ota updater which also has zero relevance to the whole reason we are having this discussion, that is less jackpotclavin baked in an ota updater to go from cm11 to cm12 and I'm missing it.

If he says it's fine to dirty flash, that's good enough for me. But unless you have a lot of issues with cleanflashing, I don't believe that its a bad rule of thumb to point people in that direction. I see posts all the time with as active as I am of people having issues with dirty flashing. Not to say that's the only reason they are having it.

You seem to be doing a whole lot of assuming, well that or you're taking a shot at me for pent up aggressions towards others who have "pissed you off with they ignorant tales of myths"

"You convince people not to upgrade and eventually, not to run custom ROMs on their next phone, and eventually start the apocalyptic downfall of android as we kno......" Whatever dude, if you think this then you read too many Dan brown books.

If data was that important I would learn how to back it up to my PC and transfer it back versus refusing to ever flash another ROM.

Anyways. That's about all I have to say about it, and you can take it for what its worth, I honestly don't care lol.

I just wanted to give my views on it since you lumped me in with three other posts, and made a lot of assumptions based on one word, and look, I didn't even have to personally insult you, even though that's exactly what you TRIED to do with me.
[Verizon LG G2] Lawlrus:
Oh hell I forgot the best part. Courtesy of [MENTION=5037435]REV3NT3CH[/MENTION]
[Verizon LG G2] markcyst:
I'm sorry if you think I was insulting you, I did not intend to.

I don't need to provide proof, as I am not the one trying to disprove the word of the developers. Those who argue with the people who design this OS, or release customs roms are the ones who need to provide proof.

Clean flashing is only necessary if the developer has stated it. If you want to try and disprove that, then provide the evidence.

I followed his words in flashing from his CM11 to CM12 builds. I did not need to clean flash. I was simply having trouble with the LATEST alpha build, not the one from the 15th.

How does it hurt the community?

Because the vast majority of android users do not want to lose data every time they update. I know you don't mind, I know others don't mind. But the developers have done a wonderful job on keeping the upgrading process as simple and trouble free as possible.

JPC dedicates time to us by giving us finished builds ready to flash without issues. By keeping the myth of clean flashing alive, you (not specifically you) are telling people to ignore what he says and wipe before flashing. Thus, people not into losing data will be turned off from staying active in this awesome community.

Android is just like any other OS out there, from Windows to iOS to Linux to Unix, you don't need to wipe your data to upgrade the OS. UNLESS, specifically told to by the dev. There is no magic that happens when clean flashing vs dirty flashing.

It just drives me nuts to see millions of posts by people who have no idea how programming works, let alone Android Code, tell people they have to follow some bizarre ritual of wiping, flashing, clearing, cache'ing, killing apps, etc.

By the way, I like you, you are helpful. I'm not singling you out, you just got caught in the crossfire due to my horrible aim.
[Verizon LG G2] da_reeseboy:
[MENTION=5559940]Lawlrus[/MENTION] and [MENTION=2339888]markcyst[/MENTION] -

Please stop. The thread is getting cluttered with unnecessary posts. If a dirty flash didn't work, it is recommended to backup and then try a clean flash. It is entirely possible that something on the current setup is not compatible with lollipop. Doing a clean flash will verify if it is the rom or current phone setup.
[Verizon LG G2] Lawlrus:
I stopped over an hour ago. Thanks though
[Verizon LG G2] markcyst:
Those of us who have successfully dirty flashed from CM11 to CM12 have proven there that there is in fact, nothing in the KitKat builds, that is not compatible with the Lollipop build, like you are suggesting.

Trying to correct misconceptions about how to upgrade this ROM is not cluttering the thread with useless information.