yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] superawesomeme:
As far as I know, knock code and most of the features unique to LG Stock/Fulmics are not portable due to requiring the LG Framework which is only available on stock based ROMs.

I've used both extensively over the past couple of months and I think it's safe to say I'm sticking with CM now.

Fulmics is really good and adds a lot to LG Stock but there are too many niggles for me that are part of stock and therefore part of Fulmics.

UX

CM is bright, clean and modern. The built-in apps look good together, work well together and work well with most third party apps. You can use custom themes and icon packs system wide regardless of your launcher. The circle battery icon is great, I know it's not the significant but to me I really like it.

LG/Fulmics is dull, boxy and a bit dated. It tries hard to have a material look but falls short and resembles a JellyBean/Lollipop hybrid. Icon packs can only be applied to the launcher and the default icons are seriously ugly. The status bar and nav bar also have giant icons that look ridiculous and uncomfortable.

Gmail

Small niggle here is that LG/Fulmics doesn't natively support Exchange accounts with gmail forcing you to use a different app or download the exchange services apk separately if you want to access an exchange account from Gmail.

Notification panel

I guess this is very much a personal preference but I prefer the way CM lays out the toggles in the quick settings area compared to LG/Fulmics and their slide along method.

Live Display

I don't recall seeing this on LG/Fulmics, I may have just overlooked it, but live display is great. It adjusts the screen temperature throughout the day to make reading easier, reduce eye strain and help you sleep. I love it.

Update cycle

CM 13 is already on Android 6.0.1 whereas LG/Fulmics is only on Android 6.0 this may not sound like a big deal but when you think about major exploits or updates then they should get patched or applied faster with CM than stock.

A few plus points for LG/Fulmics because it does have some over CM...

Camera

Hands down the LG camera app is streets ahead of anything you can install on CM because it uses proprietary drivers to make the most out of the camera's features such as laser autofocus, 4K video and slo-mo recording. These aren't available on CM.

Stability

Whilst I haven't had any major issues with CM, it is still considered 'unstable' and hasn't been designed specifically for the device. LG/Fulmics has been designed and tested for this specific device so you would expect it to work more smoothly, but personally I've seen just as many issues if not more.

Q-Memo

A handy tool but not going to lose sleep over not having it.

Game Optimisation

A new setting on LG/Fulmics allows you to manage your power expenditure while playing games. You won't find it on CM.
[G3 Original Android Development] BigsyBiggins:
I'm having bluetooth issues and I get the same out from both.
[G3 Original Android Development] finnq:
This sounds like you guys have a corrupted misc partition. Please execute the following in a root shell and send me the resulting file via private message: "dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/msic.img".

[MENTION=655230]jeremie[/MENTION]

Thank you for your quality report. I'll try to reproduce it. However I'm quite busy at the moment.

[MENTION=4791767]YaDr[/MENTION] [MENTION=5883369]takis[/MENTION]

"free->busy->free->busy" That's what we wanted to avoid. We came up with something that would only work during a phone call. Because as you say, currently no one has time to implement a really clean solution, you can upload it to Gerrit, I'll merge it then.
[G3 Original Android Development] takis:
So if yadr uploades it to gerrit we will have it fixed?
[G3 Original Android Development] finnq:
[MENTION=5883369]takis[/MENTION] It will fix the deadlock of d2w in some situations.

Additionally many people have huge problems with the proximity sensor, as it responds correctly with the NEAR state but stays there forever. That's the reason that the screen remains black during phone calls. This will be fixed in tomorrows nightly too. This is a problem that again should occur only for those who do not come from a recent Stock ROM.
[G3 Original Android Development] takis:
What about the #prevent accidential wake up# option?

---------- Post added at 12:54 PM ---------- Previous post was at 12:27 PM ----------

Btw the commit that willbe used in tomorrows nightly will be from yadr or yours?
[G3 Original Android Development] youssefkr:
Hey guys, it seems like I cannot cast my phone screen to my TV.. Is there a workaround ? D855
[G3 Original Android Development] BigsyBiggins:
Thanks finnq, I've sent you the image. I think it stopped working upgrading to 28th build do you think it's worth flashing stock MM kdz and installing newest cm nightly?
[G3 Original Android Development] Windforce0511:
What about in apps rotation lagg? Why it occur? It will be fixed?
[G3 Original Android Development] :
1) I'll submit necessary config changes to Gerrit a little bit later.
[G3 Original Android Development] mispp:
Avoiding emmc brick bug is said to be solved ba flashing LP or MM kdz and only afterwards installing CM.

Does this also work for regular OTA stock updates to LP and then installing CM?
[G3 Original Android Development] Loknic4:
When i play video from gallery, after that gallery frozen and then can't open any photo or video. Is this bug CM 13 or only me have this problem. I try another ROM based on Cyanogen and result it's the same. :(

Sorry I am Sad now :(
[G3 Original Android Development] :
[MENTION=4574857]finnq[/MENTION]

Pushed kernel fix. For g3-common you can use this commit: http://review.cyanogenmod.org/#/c/131442/
[G3 Original Android Development] jayce996:
I've made the move and don't regret it so far. Thanks for the advice.

Last little thing: is there a way to have the Google search bar reduced to just the Google icon on the portrait mode as it is on the landscape mode with the Google launcher? Or even getting rid of it?
[G3 Original Android Development] Aruvianzz:
2016-04-03 nightly working fine on D855. No bug occured. Gonna use it as my daily driver. Thanks dev! ??
[G3 Original Android Development] GunshinFU:
Any chance you will readd the option for pictures and video to be saved directly to the SD card without a 3rd party app through the camera app? Or is it already there and I'm retarded ?
[G3 Original Android Development] finnq:
This will take a few more days. Works fine on d855 but I need confirmations for vs985 too.

Will be added as soon as I have the vs985 confirmations.

Of course from YaDr, he fixed it that way :).

Chromecast? Errors? Logcat please.

It should be there. Open Snap, swipe to the right and choose "Storage location".
[G3 Original Android Development] B3hr4d:
Firstly much appreciate the effort you put into this

On to the Q: in android 5.1 there was an option for blocking the notifications on lock screen and Its not available anymore . It was really handy. Just curious, Is it removed by Google or is it cyanogen related?
[G3 Original Android Development] finnq:
[MENTION=6932667]B3hr4d[/MENTION] Thanks, Settings - Notifications - When device is locked - Don't show notifications at all
[G3 Original Android Development] GunshinFU:
Negative I have no such option to change the location in which the "camera" app saves video or pictures it only gives me options for help and feedback, advanced which only gives me manual ****ter options, and the option to save the location in which the photo was taken.
[G3 Original Android Development] B3hr4d:
See, this is not what im talking about. earlier by long tapping on any notification and entering info menu you could block apps from showing up on lock screen singularly. The one you just mentioned blocks all the apps completely.

Tnx for the quick reply anyway
[G3 Original Android Development] itsBasti:
Simply hold down on a emty place on your homescreen. Over the widgets button there are 3 tiny circle. Hold them down and push it upwards.
[G3 Original Android Development] pprashank:
It's very annoying.. Every time I use earphone it's hissiiiiing...
[G3 Original Android Development] finnq:
I think you're using the Google camera and not CyanogenMods Snap Camera. Google cam doesn't have such an option.

This option is still available. Long press on the notification, click on the information icon and enable "Block all". You can enter this menu also from Settings - Apps - [App] - Notifications.
[G3 Original Android Development] takis:
What do you mean by the models vs985 confirmation?

And pls [MENTION=4574857]finnq[/MENTION] can you quote me when you add the prevent accidental wake up option?
[G3 Original Android Development] youssefkr:
How is the battery life ?
[G3 Original Android Development] Windforce0511:
Excellent!
[G3 Original Android Development] Windforce0511:
After using Youtube app for about 20 minutes, I'm starting to see big blue artifacts on display. What can be a problem? I'm on latest build, clean flash, but I am seeing this for a long time.
[G3 Original Android Development] Meneldur:
Is the phone hot?

Mnldr/D855/16G/CM13
[G3 Original Android Development] Windforce0511:
Nope, maybe a little like always. Same thing with my old white G3. Now I'm using black-gold G3 and the problem is still there.
[G3 Original Android Development] BigsyBiggins:
Can anyone who is running the very latest cm13 nightly do me a favour? Can you go to:

Settings > about phone > status > bluetooth address

Does it have a real mac address there? I have tried a few times now, even flashing back to stock MM (where I do have a real address) then back to latest cm13 but the address gets set to 00:00:00:00:00:00. Seems odd that its only me getting this.
[G3 Original Android Development] Windforce0511:
Bluetooth address: Unavailable.

I'm on latest clean flashed build. Good luck. :)
[G3 Original Android Development] BigsyBiggins:
I think you need your bluetooth switched on. Thanks :)
[G3 Original Android Development] iambig:
I have a normal address and it works flawlessy.

Am I the only one with problem with autoconnection of Wi-Fi?

I can connect but before I have to switch off-on.
[G3 Original Android Development] StuckinMemphis:
D855 on 0305 Nightly. I get a legitimate MAC address.
[G3 Original Android Development] :
You probably tried to OTA after you rooted your phone, then followed Autoprime's ota recovery guide. First version of it included wiping misc partition clean... It contained wifi/bt macs, region code, etc... And latest CM versions try to read mac from misc, not from the chip itself...
[G3 Original Android Development] BigsyBiggins:
Cheers guys, hopefully finnq can get to the bottom of it.

---------- Post added at 10:32 AM ---------- Previous post was at 10:29 AM ----------

Interesting, I've never had any ota recovery thing. But my phone was bricked by the emmc bug and this had its entire storage blatted.

Is there any way to recover or create a new misc partition?
[G3 Original Android Development] youssefkr:
Hey guys, I want to update to the latest nightly, my device is already running cm13. Is it OK to dirty flash without gapps ?
[G3 Original Android Development] agritux:
camera fc on 05.03.2016 nightly / clean install

---------- Post added at 02:20 PM ---------- Previous post was at 01:41 PM ----------

is your camera ok?
[G3 Original Android Development] Trhanec:
Same problem, last "functional" nigthly 20160221 - show address 00:00:00:00:5a:ad
[G3 Original Android Development] BigsyBiggins:
Thanks for that, hopefully finnq can fix it, I sent him a dump of my misc partition but not heard back yet.

I don't suppose you have 20160221 nightly that you could upload to mega or something? Or anyone for that matter?. I'd be very grateful to get my bluetooth back working and cm repo only has latest builds.

Thanks.
[G3 Original Android Development] Windforce0511:
Yes.

---------- Post added at 03:04 PM ---------- Previous post was at 03:04 PM ----------

It is switched on.
[G3 Original Android Development] :
Not entirely. The bytes that CM reads can be written to it though.
[G3 Original Android Development] MorsGames:
For some reason themes don't work on the notification drawer anymore. Is there any fix for that?
[G3 Original Android Development] finnq:
You both have the same problem. You somehow have an incomplete misc partition. However I can't tell how that happened. If you know your mac addresses you can send them to me together with a current image of your misc partition. Then I'll give you instructions for recovery.
[G3 Original Android Development] agritux:
i reflashed again camera still gives FC md5 is correct and making clean install
[G3 Original Android Development] BigsyBiggins:
I would appreciate that, you should already have a link to my misc partition via pm. Will send mac.

Thanks
[G3 Original Android Development] jagjot2704:
Cm 13 05-03-2016 nightly

I have been using this built and the only problem I have from it is that it gets warm during normal tasks like texting or web browsing. I have clean flashed it on my Lg d855. So can someone help me with this issue? If anyone of you are aware of some other built which doesn't get heated up then please let me know.
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] will it include the option to prevent accidental wakeup?
[G3 Original Android Development] :
Look three lines up... it will....
[G3 Original Android Development] vassagout:
Hi guys, I have a question: I'm using n&n rom. Is based on MM 30b. As you already know, I had to root my device and installed twrp in order to install the rom. Do you think is safe to install cyanogenmod from twrp? Or is mandatory to install stock MM from kdz first?
[G3 Original Android Development] Tyler123456:
Wi-Fi is almost constantly disconnecting and reconnecting, any fix for this? Also audio hiss is still present but reduced compared to how it was, yet still worse than stock LG.
[G3 Original Android Development] takis:
Just couldnt figure out if it will just incloud the patches for the incall bug or introduce the prevent accidental wake option. Thanks anyway
[G3 Original Android Development] agritux:
i found the reason. i decided to use opengapps. it cause camera fc. now returned to slim gapps and everything is ok now.
[G3 Original Android Development] reeep:
Same all zeros Bluetooth address as others have reported. Never had any brick problem with the phone... came with KitKat, upgraded to Lollipop via OTA, downgraded to KitKat to bump and install CM. I had stock MM for a while before going back to CM, but never changed bootloaders since going back to KK.
[G3 Original Android Development] metalgearhathaway:
I wonder what is causing the Bluetooth issue for some people, Mac address is there for me on D855. I'm on a clean install with stock kernel on yesterday's build, no problems with anything else either! :)
[G3 Original Android Development] agritux:
My mac adress is there too. I have no problem with bluetooth. I am on clean install and stock kernel too. :good:
[G3 Original Android Development] reeep:
Since http://review.cyanogenmod.org/#/c/121143/ and according to getmac.c the bt mac address is read from the misc partition (offset 0x4000) but my misc partition has nothing there:

0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0000040 6572 6f63 6576 7972 2d0a 772d 7069 5f65 <-- ascii: "recovery.--wipe_data"
0000050 6164 6174 0000 0000 0000 0000 0000 0000
0000060 0000 0000 0000 0000 0000 0000 0000 0000
*
0000800 5342 2050 6f46 6572 6576 0072 0000 0000 <-- ascii again: "BSP Forever"
0000810 0000 0000 0000 0000 0000 0000 0000 0000
*
0001000 0006 0000 0000 0000 0000 0000 0000 0000 <-- ??
0001010 0000 0000 0000 0000 0000 0000 0000 0000
*
00017e0 0000 0000 0000 0000 0006 0000 71f7 0f88 <-- ?????
00017f0 0006 0000 71f7 0f88 0006 0000 71f7 0f88 <-- ?????
0001800 0000 0000 0000 0000 0000 0000 0000 0000
*
0006800 xxxx xxxx xxxx xxxx xxxx xxxx xxxx xxxx <-- and here is my imei
0006810 0000 0000 0000 0000 0000 0000 0000 0000
*
0007000 474c 3844 3535 5441 302d 2d30 3356 6230 <-- ascii: LGD855AT-00-V30b-EUR-XX-DEC-17-2015-16G+0
0007010 452d 5255 582d 2d58 4544 2d43 3731 322d
0007020 3130 2d35 3631 2b47 0030 0000 0000 0000
0007030 0000 0000 0000 0000 0000 0000 0000 0000
*
0007800 474c 3844 3535 5441 302d 2d30 3356 6230 <-- ascii: LGD855AT-00-V30b-GLOBAL-COM-DEC-17-2015-16G+0
0007810 472d 4f4c 4142 2d4c 4f43 2d4d 4544 2d43
0007820 3731 322d 3130 2d35 3631 2b47 0030 0000
0007830 0000 0000 0000 0000 0000 0000 0000 0000
*
000bfe0 0000 0000 0000 0000 0006 0000 71f7 0f88 <-- same thing as 0x17e0?????
000bff0 0006 0000 71f7 0f88 0006 0000 71f7 0f88
000c000 0000 0000 0000 0000 0000 0000 0000 0000
*
some more ascii in 0xF800 (phone serial number?) and then binary data

It seems the wifi mac should also be in offset 0x3000 according to getmac.c. I suppose CM is getting the wifi mac from elsewhere because I also have zeroes there but I have a correct mac in settings/status.

(edit) I've tried grepping the misc partition dump for the wifi mac address that appears in settings/status, in case it had moved somewhere else in marshmallow and the bt mac address could be found close to it, and found nothing similar...

(I haven't OTA'd while rooted or anything similar. I've never wiped my misc partition. I still have nothing in 0x3000 or 0x4000...)

(edit2) I installed marshmallow stock 30b and took a look at the wifi and bt macs. The wifi mac is the same as in CM (00:90:4c:xx:xx:xx). The bt mac is 22:22:f3:xx:xx:xx (not zeroes). I don't know where stock gets the macs from.
[G3 Original Android Development] Windforce0511:
I haven't problems with Open Gapps
[G3 Original Android Development] agritux:
i installed arm & 6.0 & nano version. am i wrong?

Edit: there is a log txt file and debug archive file in my sdcard. Mybe something gone wrong.

Is the nano package includes Google Camera? Maybe it is releated with Google Camera.

I think Slim Zero package has no camera on it.
[G3 Original Android Development] Trudi:
4 hours. 6 with Nebula Kernel.

Use modem 21C instead of 30B.

I had lots of problems with Slim Gapps. Now I use Open Gapps and no problem anymore. Camera is only in stock package if I remember well.
[G3 Original Android Development] takis:
Wanna say a huge thanks to [MENTION=4574857]finnq[/MENTION] and his team for creating cm13! Cm12.1 was garbage for our device but ever since he showed up we have been getting some serious support and critical updates/changes! One of them was the new kernel that removed the bsod issue!:good::highfive:
[G3 Original Android Development] Tyler123456:
[MENTION=1459357]Trudi[/MENTION] I am on modem 21C and still got the issue, that's what's mind boggling me
[G3 Original Android Development] podkilla:
I encrypted my device recently. Is it possible to decrypt it again somehow?

Settings / Security / Encrypt Phone does nothing.
[G3 Original Android Development] fmehdi:
Greaat work [MENTION=4574857]finnq[/MENTION] can you add kcal support on kernel pleaaaz
[G3 Original Android Development] c-non:
I think screen resolution not 2k with cm13, everybody can see difference about screen color and sharpness with stock vs cm13.
[G3 Original Android Development] takis:
Sharpening.... Its lg trick for stock
[G3 Original Android Development] c-non:
It is about only text sharpening ?
[G3 Original Android Development] okanb3:
I got google play services battery drain. Freshly flashed Open Gapps Mini 6.0 arm version with latest nigtly. Google Play Services just keeping awake my phone constantly. Anyone got idea?
[G3 Original Android Development] Windforce0511:
If you want sharpness like stock rom, download apk called "Whetstone" and you will find what you want. ;)
[G3 Original Android Development] vassagout:
Guys, has anybody flashed CM13 coming from a custom marshmallow rom?
[G3 Original Android Development] Meneldur:
Install BBS and check which alarm is causing the wakeup. Then see if you can control it or use Amplify to get rid of it.

Mnldr/D855/16G/CM13
[G3 Original Android Development] okanb3:
I already installed BBS and using it. There is no partial wakelock over there. There is one unusual thing in alarms, Google GSM GCM alarm 49/h (About 200-300 times depends on time). When i look at the detailed alarms, most of this caused by HeartBeat_Alarm. As far as i know HearBeat is relevant to Push Notifications. But i only use Whatsapp and Instagram and Greenified them. I cant understand why this is happens.

I hear Amplify too much but i dont want to use Xposed because of stability issiues.

So everyone in there has this bug and solved by Amplify? If its not, i would like to know why this happens. After that maybe we can solve.
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] and [MENTION=4791767]YaDr[/MENTION] Excelent job guys!
[G3 Original Android Development] Loknic4:
No one have this problem? :(
[G3 Original Android Development] agritux:
yes nano package doesnt contain camera. i tried 3 times. wiped all and made clean install. am i wrong? i downloaded arm&android6 package.

i am using slimgapps since it started to release. i have never have any problem with its zero package. interesting.
[G3 Original Android Development] two_handed:
Are you sure you really encrypted it? Encryption did not work since cm12 nightlies (at least for me)

And I guess thats why "encrypt phone" did nothing because encryption does not work yet.

Sent from my LG-D855
[G3 Original Android Development] ravenhr:
My two cents (again):

I'm on 20160303 nightly.

Hissing - on stock earphones, on some Sony earphones - GONE.

On a nightly before, there were some freezes. So far on this nightly, with 5 days and 14 hours uptime - NONE.

Bluetooth works fine. I never had any problem with it.

LTE is stable, WiFi also.

On previous nightly I had higher battery drain. This nightly - I unplug G3 at 6.30 and by the time I go to bed (usually around midnight) I have more than 40% left. IF I don't play. So much, much better.

In short, this is now my daily driver, it fits ALL my needs. [MENTION=4574857]finnq[/MENTION], thank You for this ROM and all the effort put into solving issues.
[G3 Original Android Development] augusto.med:
I was still on Dec 18th build due to those hard bricks that people had with late december builds. This weekend I decided to update. Yesterday phone started rebooting randomly. Today after some of those reboots it wouldn't boot anymore. Downloaded Fulmics (tired of CM13 problems), booted into TWRP, did a factory reset, bang. My filesystem is completely screwed. MTP mounts but cannot transfer anything (not even read the files that do show up there), adb sideload fails, my external SD card is not read/mounted by TWRP. I'm totally lost. Since I had not transfered the zip yet, I don't have any way to flash another ROM. Can anybody point me in the right direction?
[G3 Original Android Development] jeremie57:
You have to flash a kdz file as already explained before...
[G3 Original Android Development] agritux:
cm-13.0-20160309-NIGHTLY released with a huge changelog with our device releated fixes :) Thanks devs thanks [MENTION=4574857]finnq[/MENTION]

http://www.cmxlog.com/13/d855/
[G3 Original Android Development] splitsch:
[MENTION=4574857]finnq[/MENTION]

Last knightly : hissing sound is gone on AKG K450.

Thanks !

Splitsch
[G3 Original Android Development] reeep:
Answering myself, I decided to hexedit the misc partition and put the wifi and bt macs seen by LG 30B stock in 0x3000 and 0x4000 by hand. Now I have the same bluetooth mac in CM and in LG stock.

But I still think something other than PEBKAC is removing the macs, since I never did anything like dd'ing misc from /dev/zero or had the emmc bug.
[G3 Original Android Development] takis:
So true he nailed it...
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] to poins on one image...

1) glad to see we got android r016 as well

2) the navbar isnt shown correctly on landscape...
[G3 Original Android Development] mainicia:
I can't boot up with 30B radio.

anyone got same problem?