yashsingh1/xdaforums huggingface dataset:
[AT&T LG G3] abarax:
Thanks for all of your hard work. Considering that this ROM was launched just over a month ago, it's remarkably smooth, and matured very well. It's already a daily driver on my D850.
[AT&T LG G3] abarax:
There's a build for 12/31 up.
[AT&T LG G3] AndroidUser00110001:
Happy New Years!

First build of the year is now up.
[AT&T LG G3] Enddo:
I've been getting some random full green light screens in the middle of the night. I think it has happened about three or four times so far. It stays there at the green screen until I press volume down(or reboot) or volume up(to go into download mode, I think).

I used the application Syslog to grab a collection of logs the last time it happened. I hope they are helpful to find out what is wrong. I will say that I'm using a custom kernel, however, I have gotten this same green screen issue with the stock kernel as well. I had actually hoped that switching to the 'optimized kernel' that is in the LG forums would have helped, but since it is based on the CM12 kernel, I doubt it makes much of a difference.

Anyway, the logs are attached, I hope you(someone) can make some sense of them
[AT&T LG G3] AndroidUser00110001:
Can't debug a custom kernel problem even if you think the same issue was with stock kernel. It may appear to be the same issue but can be totally different. I purposely ask to report bugs after the issues can be replicated coming from a clean install with no other apps but for GApps to be installed.

Thanks for the logs though, I just changed post #2 for proper bug report info and getting the logs was one of the things I would need.
[AT&T LG G3] abarax:
I just did a clean flash (wiping everything except the internal and external SD cards) of the 01/01 build, and I'm receiving "The Android system has closed" errors immediately following setup. I've downloaded from all three sources, and installed with and without Gapps.
[AT&T LG G3] Kcgiddings3:
Same problem here.
[AT&T LG G3] Enddo:
I definitely understand. I just figured that the logs might be helpful. If they were, then that's cool. If they weren't, then that's ok too. I just felt that I should report it
[AT&T LG G3] AndroidUser00110001:
Need some logs. How to get logs is in post #2 with instructions on how to get them.
[AT&T LG G3] Roseysdaddy:
Getting kernel panics on 0101. Clean flash with nano gapps.

https://docs.google.com/file/d/0B1OeYdLesZgAMmlBdG9BSzhUdFk/edit?usp=docslist_api
[AT&T LG G3] AndroidUser00110001:
what's fitbit and com.amazon.mShop.android doing in logs if it is clean install? You sure you wiped cache and data?

Download ROM again, maybe from different server and install it again. See what happens. If you doing a clean install than make sure you wipe cache and data.
[AT&T LG G3] slapadabass:
Been running 1/1 all day - no issues so far.
[AT&T LG G3] marcoveli:
I have been getting force close and phone not root error in the 1/1 build do you know what might be wrong
[AT&T LG G3] Roseysdaddy:
I always do a full wipe in twrp every time I flash a rom. Fitbit and everything else come from the play store.
[AT&T LG G3] krazyflipj:
Coming from clean install?
[AT&T LG G3] AndroidUser00110001:
Please see if you can replicate issue with no other apps installed besides what comes with ROM and GApps.

If you think I am nuts for asking that then check HERE for the reasons ;)
[AT&T LG G3] AndroidUser00110001:
Root errors you need to go into developer options and change root access to something different and than back to apps or apps and adb.

If you want to report the other issues please follow the steps in post #2 to submit bug report :)
[AT&T LG G3] Roseysdaddy:
That would mean I wouldnt be using this phone for anything 'smart'.
[AT&T LG G3] AndroidUser00110001:
You would be helping diagnose a problem in the best way possible so you can use your 'smart' phone without dumb errors which would be a smart thing to do ;)
[AT&T LG G3] Roseysdaddy:
Every single time I've had a panic I've included the logs here. Is that just been a waste of time?
[AT&T LG G3] Enddo:
I don't think he's obligated to do anything with our logs. We should be(and I am) thankful that he's even donating his time to help out the LG G3 dev community. Even the donations he's received doesn't make him obligated to do anything more than he's already done. Those are a thanks for the work he has already done, not what he will do in the future.

Like with the logs I submitted, if our logs help out then they help out, if not, then no big deal. There's other devs, other ROMs and we are all welcome to use any of them out there. No one is forcing you(or I) to use this custom ROM and we shouldn't expect the dev here to do anything
[AT&T LG G3] Roseysdaddy:
I feel like no one stated nor implied any if the issues you just defended. All solid points and no one is debating them.
[AT&T LG G3] marcoveli:
yes
[AT&T LG G3] AndroidUser00110001:
I would say some of them may have been a waste of time and some have helped with bugs. It all depends on the situation. Honestly, lately I have not looked at logs that have been generated if user did not follow suggested way to submit a bug. If a user cannot take the time out to help diagnose the problem you are about to post about then why should I or anyone else maintaining a ROM take the time to figure out the issue if over half the time the bug being reported is due to something outside of ROM or the device tree.

I really don't get your question since you posted some kernel logs today and I did reply to you. In your post you stated you came from a clean install, I asked you if you are sure because I saw some fitbit, htc lockscreen and some other apps being referenced in the log and then you came back to say that you had some apps installed from play store. I should have also asked if you had any other apps installed but I figured you been in thread long enough to know that it makes it easier for me when no other apps are installed besides what comes with ROM and GApps. Once I saw those references I asked you if you can replicate the problem without any other apps installed besides what comes with ROM and GApps. I have not heard back from you about that issue so I must ask, did I waste my time looking at the logs you posted? You can reference this post.

Did you see how many lines your logs contained? 16,379 should I have wasted my time going through each one after I saw references to outside apps?

Also today some user was posting in the d855 thread about adaway causing a bootloop, user did a clean install XXX amount of times but each time only adaway was being installed and kept bootlooping. So I took some time away from what I really wanted to work (nav bar modifications to submit to CM) on today to investigate since I recall there could be issues in lollipop and certain apps like adaway may not work. As it turned out an hour or so looking into the issue it finally came out that user was changing DPI which was causing the bootloop. If it was mentioned that DPI was changed in the first post about adaway causing bootloops it would have taken me less than a second to tell him not to mess with DPI but I got bad info so an hour was wasted on that, then some more time looking into your 16,379 lines of logs. So I guess it was wasted time since I took the time to look at your logs but you could have not taken the time to try to replicate issue without any other apps installed but yet you try to be a wiseeass asking if you wasted your time for submitting logs.

Please forgive me for wasting your time...

Never got to work on what I wanted to work on because after all that I broke out some sticky to celebrate new year and got sidetracked ;)
[AT&T LG G3] kinjo1023:
^^^epic
[AT&T LG G3] abarax:
That. Was. Awesome.
[AT&T LG G3] shayneflashindaily:
Did you really need to quote that long comment lol its like quoting the OP.

2SHAYNEZ
[AT&T LG G3] abarax:
Not normally, but in this case, yeah. lol
[AT&T LG G3] Roseysdaddy:
I guess I'm just confused. I was under the impression that using this like you would use a phone everyday was the way to test it out, not in some sterile manner. If I install the Rom and lay it down and never use it and there are no kernel panics then what's point? For the sake of argument let's assume that with nothing installed and not in use your rom works great. It's not until I actually try to pretend that its a smart phone that the problems arise.

Cm 12 is the only rom I've ever had a kernel panic on. I flash some different rom almost everyday, and I've always provided you with the resources to focus our what the problem is.

The issue is the rom, or the kernel or whatever. These problems dont happen on other roms, with the same use and and the same crap installed. If you want to try to figure it out, I'll continue to provide you with logs.

Keep up the good work, sorry to hear these kernel panics kept you from doing what you wanted. I can sympathize, I know how that feels.
[AT&T LG G3] cables2590:
Great rom but the only issue that I'm having is my phone won't connect to my moto 360 through the Android wear app... Anybody else seem to have this issue?
[AT&T LG G3] Enddo:
My G3 connects to my 360 just fine. I am running the 12-31 nightly right now
[AT&T LG G3] cables2590:
And u connected it through the Android wear app? Maybe I should flash the rom again... I did do a clean flash and I'm on 01/01 build
[AT&T LG G3] fankuan19:
Be sure to reset the watch, it won't connect if the watch has already been set up
[AT&T LG G3] MikeF0209:
I'm on 1/1 and Moto connects OK.
[AT&T LG G3] Enddo:
Yes, I did. Like the other person says, you might want to do a factory reset on the watch if you think it is paired with another device
[AT&T LG G3] AndroidUser00110001:
That made me chuckle.
[AT&T LG G3] southern87:
Is a 2 January build being uploaded today? I noticed the upload times are in the early morning and one isn't there. Coming from cm11 so don't want to flash yesterday's just yet
[AT&T LG G3] EddyTeddy01:
Its probably a problem with CM but i thought I would bring up that Antutu claims this ROM is 32-bit instead of 64-bit. Probably doesnt impact the performance or anything, but i just wanted to point it out. Great work!
[AT&T LG G3] AndroidUser00110001:
The first step would be to determine if the problem is within the ROM. Best way to replicate the issue is to only have gapps and ROM installed. If the issue can not be replicated then it would be best to test each app independently until the bug is tracked down.

I never said use your phone daily with no apps. Just have no other apps installed when you are trying to replicate the issue.

Software debugging sucks for users and the people trying to fix the issues, especially when the issue cannot be replicated.

Can you make the kernel panic happen or is it just random?
[AT&T LG G3] AndroidUser00110001:
No I gave the build system a day or two off...
[AT&T LG G3] southern87:
I did 2 installs of 1/1 build and get the Android close box. First install I did install the aosp lg remote so I redid the install with just the rom and gapps. I was not near a computer and wasn't able to get logs. Will do it tonight again for the logs.

I wiped cache, Dalvik, system, and data flashed the rom then gapps.
[AT&T LG G3] BB6H22LUDE:
Our device is a32 bit
[AT&T LG G3] southern87:
Oh here is my logs for build 1/1. I followed the OP steps on installing coming from non cm12 rom.

So Wiped dalvik, cache, and data. I flashed 3 times total today. Running the stock kernel. I get a android system has stopped box. If something pops up I can click on it if i am fast enough. I can pulldown the notifications and go to settings and change whatever I please. When i got to the home launcher i get the system error. Eventually I get a black homescreen with nothing. no scrolling left or right. I press the home button and I get the error. I click ok, it goes away.

CM 12 1/1 build and GAPPS from 12/25(Latest that I know of) were only things flashed.

LIKE OMG FIX IT.....you know.

Here is a link to a folder with all the logs for this rom i shall produce. There is a kmsg, dmesg, and 2 logcats(first is after boot, and 2nd is after I get the message to semi stop)

Link to the LOGS!!!!!P.S THE ROOSTER IS CROWING
[AT&T LG G3] EddyTeddy01:
But should tge operating system be 64-bit anyway?
[AT&T LG G3] kinjo1023:
64 bit os won't work on a 32 bit phone.
[AT&T LG G3] jake.corey.jacobs:
You need tochill there buddy. Demanding things isnt the way it works around these parts. It will be fixed when whats causing it is figured out and then figured out how to fix it.
[AT&T LG G3] southern87:
Someone didn't since the sarcasm. It's OK..... And I am chill
[AT&T LG G3] jevan24:
*sense...anyways I flash this zip https://www.dropbox.com/s/itah3appo9omisn/GNL5-0V2.zip?dl=0 and go through the setup I am able to pull down the notification tray then go to settings and change the launcher to gnl. Then I'm able to use this build. This can be done even with the error showing constantly.
[AT&T LG G3] SmokeyTech1:
I was one of the first to flash this rom back when it came out, im amazed how greatly its matured, i flashed the 1/1/15 rom, and was very impressed, BUT i couldnt get VPN to work, so i had to go back to stock, hopefully it gets fixed and ill be back on it! Keep up the good work
[AT&T LG G3] TonyStark R.I.P.:
Why... oh why can't all these folks play nice.

Please end the ETA references here... ahora!

Please bring the snipe melee to a steel cage:silly:

And please respect one another.
[AT&T LG G3] AndroidUser00110001:
New builds up...just not on goo.im
[AT&T LG G3] southern87:
Running 1/4. No system fore close error. So far running smoothly.

What was changed to fix anything?
[AT&T LG G3] EddyTeddy01:
That, my friend, is why he posts a changelog of every change made (found in post 1 if you didnt know).
[AT&T LG G3] southern87:
I get that but there was a lot of base cm12 changes too yesterday. The g3 specific was audio changes in the kernel, surely that couldn't been the issue. So I was curious of something in the cm12 base got screwed.
[AT&T LG G3] wedgess:
This ^^. Thread cleaned of yesterdays carry on. Please report and move on in future instead of going OT in a development thread, thanks!

Thread cleaned
[AT&T LG G3] HaruSoul:
Running 20150101, everything is running smoothly for the most part. Only real issue I'm having is that any link I click on I get a force close "Unfortunately, Android System has stopped" I just got the phone and this is the first flash I've done. Will post a logcat if needed, not sure if the issue is known.
[AT&T LG G3] AndroidUser00110001:
Try a newer build...
[AT&T LG G3] southern87:
1/5 is running smooth. The camera quality angers me. Waiting for the banned guy camera to work properly for 4k video. I messed with the media profiles and it helped some or my brain thinks that lol
[AT&T LG G3] Ozark_8125:
Probably that...:p

4k video isn't working yet, but as far as the camera picture quality goes, it's pretty good. I was worried because I read someone else's post about poor photo quality also, so I took a test shot with a stock rom and then the same shot with this rom and compared the two on my 27" 4k monitor. There wasn't much difference. That's as far as the quality goes. Features are a different story. I use the Snap camera app and it gives you some of the features back (especially save to extSD).
[AT&T LG G3] southern87:
The media profiles xml for cm12 has the 4k profile actually. Quality is about the same. LG still was better to me. Changing some of the settings helped a little though.
[AT&T LG G3] SupaAvenger79:
New DPI

Great news everyone... Well at least I think it is. Looks like the next nightly is going to look much better.

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

560 DPI (About time)
[AT&T LG G3] greg4869:
Coming from stock, I thought 640 was an ok dpi..sure things looked bigger but they look "right" I started out with this ROM changing dpi to 560 and there was a lot of talk of what it should be at, and AU can attest this was quite the subject matter for some time. I've since left mine at 640 and came accustom to this but would love to see 560 by default.
[AT&T LG G3] KeeperOfThePizza:
Even though this is irrelevant if Google Now supported 5x5 it might look better at 640 because it looks fine on the stock rom. [emoji1]
[AT&T LG G3] krazyflipj:
Looking at Gerrit, 560 will be new default (Code was merged) Should see changes in next build
[AT&T LG G3] AndroidUser00110001:
Yes it was and CM12 is now official. Should see builds going up on their server soon.

Hopefully the build I am making now and about to upload is the last one for me :)
[AT&T LG G3] AndroidUser00110001:
CM 12 Going Official

http://review.cyanogenmod.org/#/c/84091/
[AT&T LG G3] Enddo:
Does this mean nightly builds for the 7th and onward will be posted on CM's official site? Or is this more of a preparation stage?
[AT&T LG G3] AndroidUser00110001:
We may see it tomorrow HERE

It's all based on mostly the same source I have been testing with. After it goes official I have a few more commits to push.
[AT&T LG G3] Enddo:
The first CM12 Nightly was released for the LG G3. . .but it's for the Verizon variant - http://download.cyanogenmod.org/?device=vs985
[AT&T LG G3] KeeperOfThePizza:
Should imminent for all then.
[AT&T LG G3] AndroidUser00110001:
There are experimental builds with today's date in the experimental folder. It is straight 100% CM source with a new camera commit.
[AT&T LG G3] Enddo:
I've got my fingers crossed :fingers-crossed:
[AT&T LG G3] AndroidUser00110001:
There was a huge bug in the latest updates, be happy it is not "official" yet. Being worked on and tomorrow or day after we should have official builds.
[AT&T LG G3] AndroidUser00110001:
PS. Lets put a freeze on reporting bugs until this goes official...

Doing a code freeze on my side until CM starts building CM12. Some fixes may not make it into CM just yet so lets wait and see...
[AT&T LG G3] KeeperOfThePizza:
Sounds fantastic. [emoji1] [emoji4]
[AT&T LG G3] southern87:
So the experimental one shouldn't be flashed?

I do like the new dpi change.
[AT&T LG G3] abarax:
I wonder if it's the issues some have reported on rebuilding the media profile .xml file to clean up the camera to bring it closer in line to the stock camera. I read that it's causing bootloops when you flash clean or dirty.
[AT&T LG G3] AndroidUser00110001:
Nope was a radio issue but it is moving forward now.
[AT&T LG G3] Enddo:
That's good to hear. I was close to flashing that earlier today lol
[AT&T LG G3] marcoveli:
is any of you having clock force close when you're trying to set up an alarm
[AT&T LG G3] abarax:
Gotcha.
[AT&T LG G3] AndroidUser00110001:
Oops wrong thread
[AT&T LG G3] krazyflipj:
No
[AT&T LG G3] mischief4l:
I was having a major battery drain issue, even when the phone was off. I thought it was a kernal issue. Maybe that Radio big had a hand in it
[AT&T LG G3] marcoveli:
even wen i try to start fresh with the rom it still do it...what gapp you use?
[AT&T LG G3] AndroidUser00110001:
And we are officially official :)

http://review.cyanogenmod.org/#/c/84091/
[AT&T LG G3] marcoveli:
awesome dude.....hope to see that build tomorrow
[AT&T LG G3] DeathStolas:
Awesome and congratulations!
[AT&T LG G3] Enddo:
Way to go, man! Congrats :highfive:
[AT&T LG G3] PsychoChild:
Got the kernal panic today on 0104 build also seems like I lost root also :(
[AT&T LG G3] valdesr11:
Congratulations Android user, you deserve it. The ROM is great.

Is there any other kernel available that is compatible with this rom for overclocking?
[AT&T LG G3] AndroidUser00110001:
We official but first build failed but CM is building for now on.

Please read post #2 about submitting bugs and try to follow that :)

Thanks!
[AT&T LG G3] AndroidUser00110001:
Not sure...
[AT&T LG G3] EddyTeddy01:
Well now that cm12 is official for us, what will this thread be used for?

Also, will we be getting OTA updates from CM now?

Lastly, congrats AndroidUser! You are the best!

One more thing, I only see cm11 downloads on the CM website. Is there somewhere else I should be looking for night lies or are they still cooking up a download?
[AT&T LG G3] southern87:
Official nightly! Heck yeah brother. Thanks for maintaining a kick wing rom android user.
[AT&T LG G3] kirky2k2:
So with this ROM now being official, does that mean it's the most daily driver friendly lollipop ROM available for D850? Everything is working such as messaging app, mms, mem cards, wifi, NFC bluetooth, keyboard animations etc etc etc?
[AT&T LG G3] mcortese81:
Only CM11?

Is the CM12 somewhere else now that it is official? Link in first post is only CM11...
[AT&T LG G3] valdesr11:
CM's first 12 upload was a fail - They are working on a working build now and will be uploading it asap.
[AT&T LG G3] mcortese81:
Sounds good, thanks!
[AT&T LG G3] Enddo:
It wont happen until tonight(in 12 hours or so) when the rest of the CM12 nightlies are build, right? Or am I missing something?
[AT&T LG G3] KeeperOfThePizza:
You're right. I believe they release at/before midnight.
[AT&T LG G3] AndroidUser00110001:
http://jenkins.cyanogenmod.com/

You can see what is being built.

I am uploading today's "unofficial" build to the FTP servers I have been using for all of you flash addicts.

It's on AndroidFileHost now

https://www.androidfilehost.com/user/?w=settings-dev-files&flid=22972
[AT&T LG G3] valdesr11:
Its asking me for a log in.
[AT&T LG G3] AndroidUser00110001:
https://www.androidfilehost.com/?w=files&flid=22972

Basketbuild - HERE

Goo.im - HERE
[AT&T LG G3] valdesr11:
Thanks. By any chance do you have a changelog for your builds available?

The one on your OP is still emtpy.
[AT&T LG G3] AndroidUser00110001:
The CM changelog shows all changes to CM, the G3 Specific shows all changes to the G3. My github is down while I prepare for the official ROMs and you can see the changes also at the CM review code site.
[AT&T LG G3] Enddo:
Again, thank you for all of the work you have done for the development of the LG G3. I can only imagine that you are excited to let CM take over the builds but I do hope that you know how much we appreciate the work that you have done.
[AT&T LG G3] BB6H22LUDE:
+1
[AT&T LG G3] Ozark_8125:
Rrrrrooowwwrrrr!!
[AT&T LG G3] AndroidUser00110001:
CM will take over the nightly builds, saves me some time late at night or early in the morning. I will still be making experimental builds but I doubt daily to have users help test out what features might be added. I will also be working on the remaining bugs.
[AT&T LG G3] tmack4life:
Great work android quick question whoops are you impressed enough with the g3 that you would get g4 when it comes out off topic sorry
[AT&T LG G3] shekinahsmoke:
bro. "phrasing"
[AT&T LG G3] AndroidUser00110001:
G Flex 2 ;)

-----------

On a side note...with the incall audio bug when a notification arrives and incall audio getting dropped. Can I get some help testing. Some notifications cut the audio while some others do not. I believe CM Messaging app cuts out the incall audio if you get a text message but hangouts does not cut off audio. Can some of you try different notifications to see what breaks incall audio? CM may put a stop to the official builds until we get this resolved.

So I would use cell phone to call house phone or another cell then send yourself a bunch of different notifications to see what breaks incall audio. To get audio back when incall just switch to external speaker while in call and then back to ear speaker.

Also, if you have a different device running CM12 can you see if you can reproduce the issue on a different device.

Thanks!
[AT&T LG G3] krazyflipj:
Ok so the way I tested was that I called my bank and used my wife's phone to send various messages. Zero issues with in call audio! Scenarios below:

-Received text with cm messaging as default sms

-Received text with Hangouts as default sms

-Received Hangouts message

-Received text with Google Messaging app as default

-Received Facebook Messenger notification

*EDIT* found a way to recreate in call audio bug. Make a call and turn off screen via proximity sensor. When you receive a notification, hit power button. You will hear phone unlocking sound and it will cut off

*EDIT2* As long as you have a notification, hitting the power button during a phone call will cut audio

*EDIT3* workaround is to turn off screen locking sounds.