yashsingh1/xdaforums huggingface dataset:
[Verizon LG G2] minnysota:
What's the early word on M4 vs 3/8? Going for the most stable experience of course. :good:

The only commit I worry about not being on M4 is this:

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

Any thoughts or preferences from those who have flashed M4 or 3/8?
[Verizon LG G2] marleyinoc:
I'll be giving my phone a pretty thorough test at noon and can report back st 3pm ish. My current state is nandroid to M4 to 3/8.

VS980 - CM11 a nightly
[Verizon LG G2] Bwangster12:
Anyone using Philz touch? What's the difference between the Clean to Install A new ROM option of wiping and the wipe all data option?
[Verizon LG G2] iXNyNe:
@ everyone who thinks the m snapshot releases are stable

Please read the link [MENTION=3581726]marleyinoc[/MENTION] posted

Here is is again

http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items

This is VERY important info for ALL nightly flashers!

So let's use caps lock!

M SNAPSHOT RELEASES CAN BE VERY DANGEROUS TO FLASH ON TO OF NIGHTLY BUILDS!

The article offers a proper explanation of how everything really works, but the quick version is the m4 release dated 3/8 is actually more like an older nightly (2/28 for example) frozen to be sure there were no bugs. After 2/28 there were some big changes so if you're using 3/7 nightly and flashing m4 you're DOWNGRADING and this can break your phone because of the changes in the radio code.
[Verizon LG G2] minnysota:
Thanks for the clear explanation.

I guess I'm just looking for the most stable option. I am not on a nightly atm, so going by the blog post explanation and the theory behind M relesses, it sounds like M4 *should* be more stable despite the recent commits not included.

Of course this is assuming you don't downgrade from a later nightly without a full wipe.

With that being said, would you recommend M4 or the 3/8 nightly for stability if comparing apples to apples?
[Verizon LG G2] iXNyNe:
For stability m snapshots usually win over nightly builds. And m4 seems solid so far.

But there's a catch. If you're going to use the m snapshot builds you should probably stick to just using those builds and no nightly builds in between.

And the same if you're using nightly builds don't bother with the snapshot builds (they are older code than the nightly builds anyway).

If you plan on switching between the build types you should always make a nandroid backup before flashing a new build type.

For ease of making nandroid backups I recommend https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup

This app because it does the backup while you're using your phone (so you don't need to do it from recovery).

And always before flashing anything check the thread in case anyone has reported an issue, and if you encounter an issue let others know.
[Verizon LG G2] xI mEzMeRiZe Ix:
Nothing you can do about /system. That's dictated by the original partitioning scheme done by LG.

Sent from my LG G2
[Verizon LG G2] jnasmith:
FYI...no phone errors after updating to M4. Seems solid
[Verizon LG G2] Hosehead:
Is a step back an update? Lol.
[Verizon LG G2] DarthDestroyeis:
Upgraded from M3 to M4 about 12 hrs ago.... so far so good!

Wiped cache and Dalvik for safety, but dirty flashed over the M3 build
[Verizon LG G2] rmd0311:
I dirty flashed and got stuck in a boot loop coming from 3-6 nightly. A clean wipe fixed it. Been running decently since.

Thanks for the explanation before. I will stick to the nightlies from now on.

Makes sense my phone went on bootloop galore.
[Verizon LG G2] deusingmono:
Reiterating what's already been said regarding the roaming issue. It started for me the day the new dialer was introduced and is still present running 3/8. I had been using the PA Google Dialer until that first build without issue. I understand from commit logs the CM Google Dialer is reverse engineered and not necessarily the "Google Dialer".

I think I may try switching back to the PA version today to see if the roaming bug goes away.
[Verizon LG G2] xI mEzMeRiZe Ix:
So has anyone on M3 + PA gapps upgraded to M4 via dirty flash without issues? Just curious if I'm going to need to do a clean or dirty flash when upgrading.

Edit: Flashed just fine for me.

Sent from my LG G2
[Verizon LG G2] datsyuk:
Be sure to let me know. I flashed 3/9 and instantly got the roaming issues yet again.

And can anyone else chime in on this, whenever I flash other ROMs (PA, Omni, etc) the scrolling is very choppy and not smooth. Obviously CM is fine and its the only ROM for me that has smooth scrolling. Does anyone else exp this on other ROMs. Been dying to find out the issue so the devs can fix this on their ROMs.
[Verizon LG G2] marleyinoc:
That's a good way to go. There a few options the CM post suggested and that's one of them.

That said, I feel like the nightlies has some new stuff that I'd like to use. So after boot looping, restoring a fairly old nandroid, flashing m4 ... I then flashed 3/8.

Had a soft reboot this morning but just played ingress 3 hours while letting a new player tether to me and had no issues at all. I've mostly been in an LTE area (with probably some drops to 3G) and didn't have any issues.

VS980 - CM11 a nightly

---------- Post added at 10:06 PM ---------- Previous post was at 09:45 PM ----------

I'm not have problems with my dialer but don't really know which one I'm using. In apps it says com.android.dialer version 4.4.2-50ab2241fb

VS980 - CM11 a nightly
[Verizon LG G2] ppeklak:
my only issues are no MMS in hangouts (when i try to put an APN in it just disappears) and my sound search for google is broken.
[Verizon LG G2] deusingmono:
I reflashed the PA Google Dialer on 3/8 and started getting the dreaded com.android.phone error that others have reported. I tried reverting to a 3/6 backup that I had and the issue persisted. I then wiped system, cache and dalvik, flashed 3/9 and it was peachy until I flashed PA Google Dialer again.

The issue wound up being with the PA TeleServices.apk that is in their Google Dialer zip. When I swapped it out with the CM TeleServices I was able to interchange between the reverse engineered CM Google Dialer and the PA Google Dialer without getting that error anymore.

Now, on 3/9 I am not getting the same symptoms as before with the roaming bug. Before it would do it even when I had WiFi enabled, it would cause Chrome to crash and other weird behavior. I am not getting that anymore even when I intentionally sit in places in the house with no service. If I turn WiFi off in these areas I will get a data roaming message, but have no problem picking the network back up when I move to a better spot. This is with either dialer.

I will update if I come up with anything new.

---------- Post added at 05:54 PM ---------- Previous post was at 05:44 PM ----------

Correction, picking a signal back up may have been a fluke. I cannot seem to get it back once lost without toggling airplane while using either dialer.
[Verizon LG G2] annoyingduck:
Can someone explain what exactly cm's open source Google dialer is? I see no difference at all. Has it been pulled?

-VZW LG G2 VS980
[Verizon LG G2] ddzado:
I feel like I've seen it smaller in other nightlies. There's got to be a way to repartition.
[Verizon LG G2] koftheworld:
Btw I switched from preferred network global to lte and haven't gotten the roaming notification since.that was this morning and I'm on the 3/6 build.
[Verizon LG G2] minnysota:
Can anyone on M4 comment on in-call volume/distortion?

The only reason I'm considering one of the nightly builds is this commit:

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

Otherwise I think M4 would be better for me, especially if the latest nightlies still have mms and roaming bugs.

Any input would be much appreciated!
[Verizon LG G2] datsyuk:
That commit won't be in M4, but I tested and it did help sound out. Haven't run anything past 3/1 lately because of all the bugs so I really can't remember how loud it was but def took away distortion.
[Verizon LG G2] minnysota:
Thanks for the quick response. Is the distortion only when using speaker? What about normal in-call performance?
[Verizon LG G2] datsyuk:
Yeah definitely when using the speaker you'll hear some distortion, not during phone calls I believe, I never notice any.
[Verizon LG G2] minnysota:
Cool I think I can live with that as long as only speaker is affected. It sounds like M4 is more stable minus that one commit.
[Verizon LG G2] Viper76269:
For me, the last stable nightly release was the 3/1 nightly, and even that has screen wake during a phone call and reboots. but after 3/1, i experienced a lot of android process errors, roaming issues, and APN issues. Waiting to hear that those are fixed before i update again.
[Verizon LG G2] Bwangster12:
It only seems to be with my wireless charger... but ANYTHING after M3... and I'm using M4 now... when I put my phone on my wireless charger it doesn't start charging right away. After about 30 seconds it starts.

Then, in the morning, I take it off the charger and go about my day. I'll watch a video, listen to music, but it stays on 100% for an abnormal amount of time. After about an hour and a half of moderate to heavy usage, I notice my phone screen doesn't turn on. Presumably it froze. I hold power to restart it and when it comes back on, it's at like 81%.
[Verizon LG G2] ddzado:
M4 has also been pretty stable for me. I'm getting great battery life so far. I haven't tried the speaker yet on this build, but I've heard the distortion. I think it might just be a line in the mixer config.

Has anyone flashed from M4 to the latest nightly? Any issues? I know that M4 is code that's like a week and a half old.

I've never been so cautious for nightly builds before, Galaxy Nexus never had a major annoying issue. I just remember one time not being able to send MMS, but that was more of a verizon issue. I'm pretty sure it's because LG isn't anywhere near AOSP on stock and they haven't release the verizon kitkat source.
[Verizon LG G2] datsyuk:
Before I rolled back to 3/1 I flashed the latest nightly over M4 and had no issues aside from the roaming bug which is an issue regardless of a dirty or clean flash. I'm assuming once that is fixed a dirty flash over M4 to the latest nightly will be fine.
[Verizon LG G2] just4747:
Mmmkay so I flashed the first nightly after M4 and now when I try to send MMS pic messages, via stock Messaging app, it fails saying no APN set and there are no APN settings in the mobile networks menu. So flashing back to M4 I guess....
[Verizon LG G2] :
Cannot send MMS on M4 snapshot, no APN setting showing up even after failed MMS in Hangouts. Any idea on how to fix this?
[Verizon LG G2] minnysota:
Having the weirdest issue on M4..

After a clean flash, Google Now was working just fine.

Then about an hour later, I check again, and when I try to refresh and load new cards it says "not available."

Anyone else have this issue or know of a fix? I read this Android Police article that may explain why:

http://www.androidpolice.com/2013/11/14/bug-watch-google-now-broken-for-some-nexus-5-users-problem-may-spread-to-other-devices/
[Verizon LG G2] BigToach:
I am also looking to fix this. Anyone have any ideas?
[Verizon LG G2] soapinmouth:
After yesterday's nightly I seem to have gone back to multiple sods a day after having none on the previous :/
[Verizon LG G2] Nandrew:
Hi guys. Just manually setup a new access point name. Use MMSC: http://mms.vtext.com/servlets/mms

I set my port to 80 and left all the over values alone or blank. Remember to save the new APN. Then back out and select it. Boom, there's your MMS fix.
[Verizon LG G2] dragonboydbboy:
Yes, also just did that and it seems to fix the signal a bit.

I also turned roaming on, so I wouldn't get the notification anyways...

But the bug also made it so that every time I would lose signal for a sec, (which seems the be the underlying problem) apps would struggle. Hangouts crash, chrome, google now launcher redraws, etc.
[Verizon LG G2] polaric:
Does everybody have this roaming bug or is it just some?
[Verizon LG G2] flyinj54:
Same thing here. Went back to 2-28 old reliable.
[Verizon LG G2] datsyuk:
http://review.cyanogenmod.org/#/c/60803/

Good news?
[Verizon LG G2] shadowkid8391:
If you are having APN problems try uninstalling hangouts and reinstalling if you dont have an update for it. I was having the same problem yesterday but it works today and there is no setting for APNs now.
[Verizon LG G2] Nandrew:
Wu-tang
[Verizon LG G2] techbeck:
Past several builds i get random reboots, system locks, and issues where the notifications will not work. Annoying and this is coming from a complete wipe. Did a fresh on today of the lates milestone and the damn thing already locked twice and rebooted once.

---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------

Have a link to 2-28? I dont have it anyore. I am guessing this is a pretty stable build? I dont try every release so I may have skipped over that one.
[Verizon LG G2] :
I can't get the APN settings to show up, even after failed MMS. Im using latest PA Gapps.
[Verizon LG G2] markcyst:
You can also use the installed Voice Dialer app, when it opens, say "OPEN APNs"
[Verizon LG G2] Nandrew:
I have no idea why. There are many apps in the play store that can access the settings too. I think the new cm commits on the Verizon eri should fix this funky business.
[Verizon LG G2] soulz:
Putting the LG G2 back in the drawer, and taking out the trusty LG F6 :silly:
[Verizon LG G2] minnysota:
Anyone else getting absurd battery life on M4?

Granted 7 of the 9+ hours I was sleeping with the phone on wifi, but either something is messed up with my calibration or this is by far the best battery performance I've ever had on any device. Hoping it's the latter.
[Verizon LG G2] Hosehead:
I have seen this with CM and PA recent versions. Wireless charging is borked. It causes crashes and reboots. The charge light stays on for several minutes after being taken off the charger. I have resorted back to using a regular charger (yuck) instead of my two Tylt chargers.

This is another VS980 specific issue, obviously. I wish there is something that could be done for this device to cure this problem as well as may Isis usable.
[Verizon LG G2] ddzado:
I've been getting great battery life as well. No complaints here. 1/31 build was also like this. Usually if you manage the location seeking apps, you'll get great life.

---------- Post added at 09:02 AM ---------- Previous post was at 09:01 AM ----------

I just flashed the latest nightly on top of M4. So far, everything is just great!

Also... it's really nice to change the pixel density in build.prop.

Set ro.sf.lcd_density=420

Default is 480.
[Verizon LG G2] minnysota:
Awesome. Definitely no complaints here!

I would try the latest nightly, but it's tough to mess with zero SODs, lockups, etc. and amazing battery life. :good:
[Verizon LG G2] polaric:
Could someone breif me on the bug everyone is talking about with roaming? Ive been away for awhile so I haven't been watching the forum for a week or two. I seem to remember that Cm 10.2 had a similar issue

Sent from my LG G2
[Verizon LG G2] datsyuk:
Phone will show your roaming after a short amount of use from my experience. Air plane or rebooting may only fix it for a couple minutes. If you don't have roaming enabled either like me then you have no data. So I rolled back to 3/1
[Verizon LG G2] :
I'm on M4 clean install from stock and I've had 3-4 SOD's since two days ago. Are you using M4 as well?
[Verizon LG G2] minnysota:
Yes I also went from stock to M4 and have had zero SODs.

The only minor issue I had was a freeze-up in Hangouts. It worked itself out, though, and there was no force close or reboot.
[Verizon LG G2] :
What did you wipe when you installed M4? I'm trying to figure out what's causing my SOD's.. I am also stock kernel on M4, no customizations yet.
[Verizon LG G2] julesism:
I flashed M4 on Sunday and have had zero SOD's. *knocks on wood* Even after phone calls yesterday the phone did not SOD. That's when I recall causing SODs for me in the past. Battery life seems ok. I wiped data/cahce/dalvik and formatted system prior to flash. Only MODs I have added are the volume distortion zip and LG Camera F40 zip. I'm using 20140105 KK gapps from goo.im.
[Verizon LG G2] minnysota:
I used TWRP and did a factory reset (the recommended step). I did that a few times even though it's just placebo. :eek:

I'm also running the stock kernel with no mods. Maybe try flashing again if you haven't already?

Could you provide a link to the volume distortion zip? Is it just this CM commit from 3/4 to fix speaker issues?

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

That's quite literally the only problem I have experienced with M4, so it would be great to fix it (without adding more issues).
[Verizon LG G2] dawgwood3:
Are you guys on M4 also having problems with data handoffs? For example, when I turn off Wifi instead of going to LTE I always drop to 3G instead. I have to toggle airplane mode to get LTE back.

Is there a work around for this issue?
[Verizon LG G2] julesism:
minnysota, here's the volume fix I flashed:

http://xdaforums.com/showthread.php?t=2652831

I honestly have not used my speaker much to see if it helped any.

*EDIT* looks like this is the same one committed on 3/4 :)

dawgwood3, I have not noticed any data handoff issues. I'm able to keep a good LTE connection at work and on the road. I only connect to WIFI at home. I'll see what happens tonight when I get home and let you know if I notice anything wonky.
[Verizon LG G2] viper909:
Before anyone asks, the roaming issue is still present on the 3/11 nightly (the one with the Verizon ERI patch).

EDIT: In case anyone wants more information about the problem: the phone flips between signal and no signal + loss of connectivity/roaming warning every 5-10 seconds, when the signal drops out apps tend to hang or crash, and the preferred network type flips back to LTE (if it had been changed). The other thing I noticed was that mobile plan throws a "SIM not installed" error.
[Verizon LG G2] Bwangster12:
It was working on M3 and a nightly or two after I think, but since then it's been messed up.
[Verizon LG G2] xI mEzMeRiZe Ix:
For me, after going into an area with very poor to no signal, my phone would tell me it was roaming and wouldn't reconnect to the right network until rebooting or toggling airplane mode. M4 does not have this bug.
[Verizon LG G2] datsyuk:
Was just making a backup and was going to flash and I read this. Ugh was really hoping that was going to fix it haha.
[Verizon LG G2] dragonboydbboy:
For me it is similar to viper909,

When I'm an area with poor signal, the phone will struggle to maintain a connection, cycling between 0 signal and 1-2 bars, sometimes completely dropping service entirely and regaining, dropping again, regaining, etc. Which causes the problems with apps. I'm usually on Wi-Fi when this happens, at my house.

I have a signal booster upstairs, so there is no reason it should have no connection

---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------

Dirty I'm guessing?

I also think that it has to do with the new cm dialer...

If only I could install uber dialer like I used to :(

---------- Post added at 09:36 PM ---------- Previous post was at 09:35 PM ----------

P.s. does the cm dialer look unchanged to anybody? I don't have the reverse lookup settings that should be present with the open source google dialer...
[Verizon LG G2] El Ha$on:
Are you using a custom kernel??

Sent from my KitKat powered device!!!
[Verizon LG G2] viper909:
I dirty-flashed this time, but with the last couple nightlies I've tried clean flashing as well. No matter what I do, the instant the phone finishes booting the signal problems start.

I noticed that as well, it looked the same as it always has, and didn't appear to have any lookup capabilities.
[Verizon LG G2] minnysota:
Nope just stock CM kernel that comes with M4.

Here's an update on battery life as the day has gone on. Came down to earth a little bit, but I have also been off wifi and in a weak(er) coverage area. Still pretty phenomenal.
[Verizon LG G2] Hosehead:
What settings do you have on your Mobile Network Settings page?
[Verizon LG G2] El Ha$on:
I agree. I'm going to have to try stock then. I've been on furnace and while battery life has been OK its not where you are. Granted I may not get the same as you even with similar settings but it is worth a shot.

Sent from my KitKat powered device!!!
[Verizon LG G2] polaric:
So the roaming issue isn't present on M4?

Sent from my LG G2
[Verizon LG G2] minnysota:
Yeah I would give it a shot. I've heard multiple reports of good/great battery life on M4 with the stock kernel.

Although you are right—every phone is different so YMMV. Let me know how it turns out!

---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------

Not in my experience.

Also I work in a poor coverage area, so it seems I would have encountered it by now had in been present.
[Verizon LG G2] dragonboydbboy:
Switching my settings>more>mobile networks and choosing "preferred network type" to LTE and checking the box for data roaming has made a big difference for me. No problems since I switched from "global" to "LTE" I'm gonna try and unchecked data roaming but leave it on LTE, let yalls know how it goes later.

Running one of the newer nightlies

---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------

OK, already got a data roaming notification after turning off data roaming. But no continual service drop and reconnect since switching to LTE...

Aaaaaand I am also still getting the service dropping...
[Verizon LG G2] juancp:
I'm on the 3/6 nightly and getting INSANE battery life.

Clean flash from stock.
[Verizon LG G2] polaric:
I dirty flashed from 2/12 to M4, very stable.

Sent from my LG G2
[Verizon LG G2] viper909:
Data: enabled

Data roaming: disabled (enabling it doesn't help)

Preferred network type: LTE

System select: automatic
[Verizon LG G2] viper909:
Just flashed M4. No roaming/signal bug, but interactive governor is still broken (since the 2/9 nightly). It was fine initially, but after 10 minutes or so became unusable.
[Verizon LG G2] beddachedda:
Does anyone else get wifi drops like all the time? I need to reconnect to wifi probably once every 5 minutes if I want to keep a stable connection. Have been on dirty flashes since like 1/09, so maybe it's just time for a clean flash?
[Verizon LG G2] datsyuk:
Very possible because mine has been rock solid man.
[Verizon LG G2] jeston:
So what was the main reason for them removing the eri.xml file? If there's no real reason, I'm definitely putting it back on from a previous build. I hate seeing "Preferred System"
[Verizon LG G2] viper909:
I've noticed that large downloads frequently fail (the longer it is, the more likely), and I think it's because my wifi is cutting out. There's no indication of this though (wifi shows as connected the whole time, websites load fine), so I think it may be due to interference rather than something ROM-related.
[Verizon LG G2] datsyuk:
Is that what that commit did?
[Verizon LG G2] BigToach:
This worked for me, Thanks so much!
[Verizon LG G2] stelthy77:
I am seeing this also.
[Verizon LG G2] :
I finally got the APN section to show up in Hangouts and I added the APN for Verizon and still cannot send MMS or receive. I am on the latest nightly, but clean flashed from stock to M4.

I also tried the Open APN's from the voice dialer and it got me the system APN settings, where it's blank. I tried adding the APN there, but no luck, it disappears after I click save.
[Verizon LG G2] Hosehead:
Have you tried changing Preferred network type to Global?
[Verizon LG G2] beermedean:
What GAPPS should I look for? Link?
[Verizon LG G2] tattooz305:
Been running 4.2.2 since I got my phone but thinking about checking out 4.4. Do you still flash the LGapps? Can I use any of the LG apps with this?