yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] 0nebukadnezar0:
I have the random blackscreen or reboot issue with my G3 under CM12.1, but always after an action:

- start camera

- enable WLAN

- answer a call

etc...

I thought this could be an hardware issue, and the device has been replaced by LG, after I had reinstalled the stock ROM. But with the new device, the same problem again, so it's ROM/Kernel related. I have tried to work with an other kernel, 777 but with no success.

Logcat the device: it was connected 2 days on USB, but the error didn't happen, it looks like, when the G3 is connected on a power source, it's not possible to re-produce the bug.

As I cannot work with a device that randomly stop to work, at least 2 times per day, I decided to move to another ROM, near stock ROM, CloudyROM, now after one week, I had no issue, but of course I miss CM12.1!
[G3 Original Android Development] GieltjE:
Have noticed the same thing, switching to a different kernel doesn't change much. (Maybe a little).

Also with every update the problems appear to get worse, which has been a trend for the past few months.

Due to the devs remaining silent and general lack of CM support I am sincerely tempted to start trying other roms (SlimLP has caught my attention at first glance)
[G3 Original Android Development] takis:
3 main bugs are as expressed below

1) black screens /battery pull to fix

2) proximity keeps the screen off while on call and dt2w doesnt work during that period

3) device cant boot while turned off and plugged

Thanks this. Hoping that someone from cm actually helps
[G3 Original Android Development] soulstaker:
I'll surely miss the camera, but flashed this anyway.

The phone still doesn't feel as snappy as it should be... what kernel do you guys use and what should I use to change its settings on the G3?
[G3 Original Android Development] galmgnt:
Thanks for the response man.

It sucks though.. I'm so used to the asop interface.

Is there any way to get it in cloudy rom?

Will I get the best camera I can get from the g3?
[G3 Original Android Development] p70shooter:
Just use the m9 camera port, job done.
[G3 Original Android Development] Nuuq:
That port was as close to OK as possible. Better than all others. But still, nowhere near stock camera.

I'm sorry to say this, because AOSP is all I want, but, because of camera, I can't have it...
[G3 Original Android Development] galmgnt:
Sucks that I have to choose...

Is there a way to get aosp experience with cloudy rom?

The dialer app for example, it's crucial to me.
[G3 Original Android Development] MisterRio:
Out of desperation, I tried a clean install, but with no luck. Still getting a black screen after calling someone. Still can't hang up myself. Still having to pull The battery. Stil no word from The developers. It's a damn shame, but I think I'll move to another ROM for as long as it takes :(
[G3 Original Android Development] Nuuq:
I was looking for the same thing, but with no luck :(

Live long and prosper.
[G3 Original Android Development] Thanofski:
I'm currently on cloudy...pretty stable and smooth thought I really want to try cm or aosp Rom but what I read here are discouraging me....
[G3 Original Android Development] bubba_66:
Runs silky smooth with no real issues for me. D855 UK. I'm using Camera FV-5 from the play store and it does a good job. I have no random reboots and am using the latest nightly build. I am not using any xposed modules or a modified kernel. CM is giving excellent battery life and is my daily driver.
[G3 Original Android Development] itsbighead:
Could someone try flashing this https://www.androidfilehost.com/?fid=24052804347758535 and seeing if it works on CM12.1 for G3

Its FM Radio pulled from YU Yureka
[G3 Original Android Development] aha360:
Has anyone noticed an annoying 2GB filesize cap on an NTFS-formatted microSD card? I tried to transfer a bunch of files, including the LG stock ROM, which was approximately 2.12GB and it failed to transfer to the microSD card. Is there a workaround or a solution that will allow me, and others if they are suffering from the same problem, to be able to manage files that are over 2GB on a microSD card?

UPDATE: THIS ISSUE HAS NOT BEEN FIXED, EVEN IN THE LATEST NIGHTLIES (20151004 AS OF TIME OF WRITING AND PRESUMABLY IN THE NEWER NIGHTLIES - THIS COMMENT WILL BE EDITED IF/WHEN IT IS FIXED). HOWEVER, THERE IS A CODE REVIEW PAGE AT CYANOGENMOD BELOW WHICH HAS A COMMIT FOR THE 2GB LIMITATION FIX:

http://review.cyanogenmod.org/#q,I1d0dcdfc15ffdcfb884b7c87086ecb10a57c9999,n,zzz
[G3 Original Android Development] -Luigi.:
An stock (LG) based ROM but with AOSP appearence. Thats not impossible, I had a ROM like this on my old Galaxy S2. "Just" need someone to modify every single thing on the appearence and AOSP apps instead of LG's one :P
[G3 Original Android Development] takis:
Just saying my g pad also suffered from black screens on cm12.1 but developers came with unofficial release that had that problem fixed... Dont know if they have common root tho
[G3 Original Android Development] SUNNY-Blue:
Nightlies stopped at 04 OCT?
[G3 Original Android Development] aha360:
That happens sometimes - it can take two to three days before they release another nightly ROM, but most of the time, nightly ROM releases here DO come out on a nightly basis.

In other news, whilst the NTFS bug is still present, I have decided to format my Samsung 64GB EVO microSD SDXC card back to exFAT and it works with CyanogenMod ROM without issues, even when inserting said microSD card directly into the PC - with the card using the NTFS file system, not only I had the 2GB filesize cap to deal with, I also could not get Microsoft Windows 10 to read the card when I inserted it back into the PC directly - now I feel like a dumb bastard for formatting the card using the NTFS file system when in fact it came formatted in exFAT out of the box and CyanogenMod supported exFAT out of the box better than NTFS.

Anyway, with that idiotic issue out of the way, I am going to go on a slightly off-topic tangent here: is there any LG Stock ROM-based custom ROM that works well with exFAT-formatted cards like CloudyG3 if I recall correctly, and has uncapped tethering support like with CyanogenMod/other AOSP-based custom ROMs? I'm asking to just double-check on this as I might move to a stock-based custom ROM if I feel that CloudyG3 or any other stock ROM-based custom ROMs support the two of the many features that made me jump on the CyanogenMod bandwagon in the first place.
[G3 Original Android Development] FanDroid09:
Is there a reason you can't flash it yourself?
[G3 Original Android Development] itsbighead:
Lol i dont have Cyanogenmod installed at this time.
[G3 Original Android Development] Step-han:
Don't flash that modem, this is not a modem for the D855.
[G3 Original Android Development] c0de1:
Problem with updaten to latest nightly build

Hi there,

I'm on CyanogenMod 12.1-20151001-NIGHTLY-D855

I want to install : cm-12.1-20151006-NIGHTLY-D855

I have a problem to update to the latest nightly update.

I download it form the cmupdater app inside the rom when installing i got the message :

Zip is corrupt

Error installing zip file '@/cache/recovery/block.map'

I use TWRP v2.8.6.0
[G3 Original Android Development] diogo.sena:
what exactly do you call "capped tethering" ? i'm currently using stock rom, and share my 3g without problems when needed..

Both stock and Cm12 works perfectly for this.
[G3 Original Android Development] aha360:
Not from my experience as certain network in the UK has a tethering limit of 4GB and with the Stock ROM, the tethering allowance decreases whenever I tether, but with CyanogenMod or any other AOSP-based ROM, the tethering allowance stays the same even though I use around 4GB or slightly more in the 'Internet blackout' situations that I had, so yeah, that's what I meant by 'capped tethering'.
[G3 Original Android Development] diogo.sena:
Look for what apn are configured for your network in stock, and in cm12, maybe they are different..
[G3 Original Android Development] aha360:
Nope - they're the same - I have checked that before and please do yourself a favour and don't give me any obvious suggestions as I will 100% likely tell you that 'I have tried them all', as I have already carried out the suggested solutions and workarounds but to no avail since I first acquired the LG G3 whilst using the Stock ROM out of the box.

Anyway, here's an interesting link to look at:

http://danielpocock.com/android-betrays-tethering-data

I wonder if anyone here has tried this to workaround the tethering limitations on stock ROMs or any other ROMs that have capped tethering/enable tethering provisions! :p

PS: If I have offended you in any way regarding the comment, or comments I have made, then I apologise - I should have said what I have said in a less ham-fisted way but like I have said in the edited comment, what I am trying to say is that you should save yourself the hassle of writing out the obvious suggested workarounds/solutions as I have already tried them out a while back, sans the suggested solution by Daniel Pocock. I will let you folks know if it has worked for me on a stock ROM.
[G3 Original Android Development] Meneldur:
Doesn't SlimLP share CM base?

Mnldr/D855/CM12.1
[G3 Original Android Development] aha360:
Yes it does, although the developer(s) for that particular ROM MIGHT add a few modifications for better functionality - 'MIGHT' being the key word here!
[G3 Original Android Development] FanDroid09:
"MIGHT" add "a few"

Haha have you even ran slim before?

There are DEFINITELY many.
[G3 Original Android Development] aha360:
Yeah I have - once on the Samsung Galaxy S3 (GT-I9300) and on the Huawei Ascend Y300 (U8815) and whilst they have added OS-specific modifications (well, duh - you don't get any points for stating the obvious), the device-specific modifications/enhancements have been minimal at best from my experience when compared to the bog-standard CyanogenMod and PAC ROM, so yeah I was originally referring to the device-specific tweaks, and seeing as most of the AOSP-based custom ROMs are essentially CyanogenMod-based ROMs and thus 99.9% likely use the CyanogenMod device trees/source code, I didn't expect any (and therefore have not seen) significant improvements when jumping from CyanogenMod to PAC ROM or SlimKAT/SlimLP in terms of hardware enhancements - heck, in actual fact, the camera quality and features are 'gimped' on CyanogenMod 12.1 for the LG G3 in comparison to the Stock ROM of the same phone, so you do end up, in some cases, having to deal with fewer features for a particular component - hence me saying "MIGHT add a few modifications", though I WILL admit that I should have been more specific by saying that "the ROM compilers MIGHT add a few device-specific tweaks" - not only that, I was also thinking of jumping onto a stock ROM-based custom ROM for the reason of obviously better-performing hardware-specific features like the camera, provided that I know for sure that I can tether without issues, use Miracast without issues and be able to use exFAT-formatted microSD cards without issues.
[G3 Original Android Development] Meneldur:
That is the key.

I like my installation, my tweaks, my apps and personalization. I'm in the same point as you: CM for G3 is falling short in terms of stability (that pesky black screen, the proximity sensor) and support (no dev seem to read here), but it's a very long jump switching ROMs. And that jump from 100% CM to 99% CM would not be useful, with all the hassle of reinstalling and setting up everything again.

Thanks for your replies.

Mnldr/D855/CM12.1
[G3 Original Android Development] eradicator006:
Head on over to the cyanogenmod forums if you want some more activity. There isn't too much going on there in regards to the g3 but there is more going on there than here.

As for issues; I'm not having any on my d852. No random reboots or anything. I did have an annoying shutdown issue where the phone would never turn off completely but that seems to be OK now. Camera quality seems fine to me. I got my g3 and installed cm12.1 immediately so I never got to experience stock yet. I came from an HTC One m7 with the purple tint problem and cm12.1 on the g3 has a far superior camera to that.
[G3 Original Android Development] GieltjE:
AOSP I believe, with some minor ports from CM, hadn't had any crashes/reboots since migrating. The features may be a bit limited but the reduced memory usage and no more crashes completely make up for that.
[G3 Original Android Development] FanDroid09:
I understand what your saying... the issue here is some of the wording you are using. When people are comparing the "features" of ROMs they generally are referring to the additional tweaks/customizations/utilities that a ROM brings over whatever its based on (whether that be CM or AOSP itself).

You don't need to tell me that the camera quality suffers compared to running a stock based ROM, that is pretty much to be expected on almost any device when moving to an AOSP/CM based ROM. Its the name of the game, really.
[G3 Original Android Development] mo120697:
And again no snapshot for our g3.

I think we have no maintainer?! :0
[G3 Original Android Development] diogo.sena:
what difference does it make? snapshots are nothing more than old nightlies..
[G3 Original Android Development] mo120697:
No I don't mean that this way :)

What I mean is, that the missing snapshots show us that we have no 100% active maintainer. Cause snapshots are builds which are considered nearly stable by the maintainer. And our builds are stable, just audio recording is a big known bug.

So g3 rarely device specific changes (look at cmxlog) and that is a sad fact, because it is a great piece of hardware. And only cm gets full power of the device in case of performance and that stuff (except the camera)
[G3 Original Android Development] Mattycee:
Any update on 4K recording at all? I am waiting for my G3 to arrive so I cannot test it yet so hoping someone can answer me.

Also how is the battery life on this Rom?
[G3 Original Android Development] GTMoraes:
Tiny wakelocks that accumulate and eat up battery along the day. Can't find anything else on BBS rather than "Android". Does it happen with someone else?

Also, the continuous writing (flow, swype, whatever you call it) is broken on the stock keyboard.

Confirm any of those?
[G3 Original Android Development] kroonys3:
Continuous writing has been disabled by cm intentionally for now due to fc issues.
[G3 Original Android Development] maximo12345:
Someone can help me?

The rom works great, but google plus process is always working and keeping cpu at high frequencies... If I open Google plus Photos the process android.media crashes..

On lg stock rom this bug doesn't occur...

Is it a known bug?

Thanks
[G3 Original Android Development] EmptySD:
I think its far more important to fix bugs then to add extra features. Rom still have a lot things to be fixed. Download some rom and test it if is that much important for you to test it.
[G3 Original Android Development] diogo.sena:
no, its just you, try reinstalling google plus, or full wiping
[G3 Original Android Development] maximo12345:
I did it...
[G3 Original Android Development] diogo.sena:
maybe is your gapps? i use this package..

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[G3 Original Android Development] gmbhneo:
I just want to report that my Bluetooth Audio is distorted and if a notification comes in it gets louder and louder.

Calling is impossible since it drops my call immediately after accepting it.

Anything else is working pretty well so keep up the good work! :D
[G3 Original Android Development] rederik79:
Same for me

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Original Android Development] droidbits:
Just some information for those who like their music:

I can confirm that this ROM is working with the FiiO E18 amp/dac.

However, it is only working with Neutron Music Player.

Enjoy!
[G3 Original Android Development] JRAtk94:
Did you dirty install or clean install?

Also, try an FDR to see if that solves your problem.

I was having battery drain too, but I did a clean reflash and it's better now - still not as good as other ROMs, but perfectly adequate.
[G3 Original Android Development] stiggy2012:
I don't have any issues receiving calls, but you can work around the volume issue by turning on AudioFX for all outputs. You can leave the EQ flat so that it doesn't affect the sound.
[G3 Original Android Development] gmbhneo:
Thats what ive already done but it still happens. I tired a lot now and can not get this problem solved or workaround it. (it is happening with every nightly so far)
[G3 Original Android Development] GTMoraes:
Confirm here. You need to turn the volume a notch down, then put it back where it was. It's annoying.

But I had solid 3, 4 hours calls with my long distance girlfriend without a single issue.

Same for short wrong number calls.
[G3 Original Android Development] Macedon2000:
What about proximity ?? Still havet black screen after phonecall
[G3 Original Android Development] weird_iris:
searched the key work gps, all the subject related has bee merged or abandoned,

do you think i restore to stock base rom and then restore cm12 will make it work again? like the touchwiz method for samsung phones

gps is a really big deal to me, i really need it to work properly.

thanks
[G3 Original Android Development] GTMoraes:
Funny.. GPS seems to work fine here

This should have been fixed. There's a fix out (it's a incompatibility caused by the DT2W).
[G3 Original Android Development] weird_iris:
yeap weird, seems area related,

it took ages to lock sat,
[G3 Original Android Development] Awestrike:
For those who have audio issues, you can try the toggle in Developer Options for NU/Awesome player.

Also, if using a music player that has fade in/out effects and audio focus switching, try turning those off, too.

I had to experiment a bit with different setting combinations but I eventually got rid of that increasing loudness issue and managed to install V4A and get it working with PowerAmp.
[G3 Original Android Development] bubba_66:
I updated to 1009 this morning, still smooth and stable. D855, adaway and no other mods.
[G3 Original Android Development] diogo.sena:
Soon we'll be running marshmallow builds, maybe we get a new mantainer :)

And i agree, g3 is great, the only thing that bugs me is the overheating
[G3 Original Android Development] mo120697:
Yeah and overheating is gone with cm for me, almost nearly, but I can't live without clear voice recordings because I use WhatsApp voice memos A lot
[G3 Original Android Development] diogo.sena:
i use so much, that i didn't even knew about that bug :)
[G3 Original Android Development] Meneldur:
Ha! Sane here, didn't know there were problems recording voice.

However, I agree. Our G3s are excellent phones with fair CM implementation. I had two black screens in two days... [emoji17]

Mnldr/D855/CM12.1
[G3 Original Android Development] MalekoUK:
Probably because our maintainer doesn't own a G3.....

---------- Post added at 10:20 AM ---------- Previous post was at 10:14 AM ----------

Side note, people need to stop complaining (not saying u are, just generally) and be grateful we have official nightlies...
[G3 Original Android Development] Noisemaker_:
any release date for android 6.0 nightlies on cm?
[G3 Original Android Development] Meneldur:
I saw many CM13 mentions on official CM changelog for G3. It's near, I think.

Mnldr/D855/CM12.1
[G3 Original Android Development] aha360:
That sounds good - I can't wait for that then. :)
[G3 Original Android Development] ad astra:
hello, does anybody know if this patch http://review.cyanogenmod.org/#/c/111365/, that is now included in the 09/10 nightly, fixes the stagefright2 exploit? or is it something else? thanks
[G3 Original Android Development] Meneldur:
Is it normal that logcat shows many errors and fatal exceptions or is it a sign of illness? CM runs smoothly only with very aggressive LMK values and the black screen issue still appears.

Mnldr/D855/CM12.1
[G3 Original Android Development] DontHate:
ever since installing this rom my phone reboots whenever i try to do anything if its not plugged in.

if its plugged into the charger i can still use it, but running from battery power alone it just boot loops.

if i boot it up while plugged in and then try to unplug it and use it, straight into bootloops again even though its on 100%

ive tried other roms again, same thing. tried calibrate battery app, same thing.

can someone pls guide me?

thank you all.
[G3 Original Android Development] kniffo80:
Had this too a month ago. Ordered a new battery - now everything is working fine again. The same symptoms you described here.
[G3 Original Android Development] Meneldur:
Clearly, phone's problem. You should try the battery solution another member posted about. Since this happens on every ROM you tried, it's likely not CM's fault.

Mnldr/D855/CM12.1
[G3 Original Android Development] DontHate:
Thanks a lot. I was hoping this was the issue. I used to work in a phone service centre, repairing phones. Sometimes when these symptoms occured it was because the battery couldn't supply enough current under the load.

Sometimes I could fix this by cleaning oxidised contacts on the battery.

On a few occasions it was the pins of the phone being bent / broken.

Ordered an extra large 7500mah battery off of ebay a few days ago. Hopefully it will be here soon, but a bit worried as it was cheaper than the standard 3000mah size battery.
[G3 Original Android Development] kniffo80:
I ordered an original battery (3000 mAh) and a large (6000 mAh) - both are running fine with my LG G3. Yes, i heard also about those pins getting oxidised ... but that was not the case when i had those reboots. Anyway, it's fixed by using a new battery ;)
[G3 Original Android Development] Meneldur:
Ten minutes ago the phone got unresponsive, then the screen got black and it went back to life seconds after. There's a flood of these errors on that timeframe on logcat:

10-14 06:12:00.368 E/libsuspend(1046): Error writing to /sys/power/state: Device or resource busy

Nightly 20151012

D855/16

Mnldr/D855/CM12.1
[G3 Original Android Development] Stransky:
Sort of similar problem. Updated to nightly 12102015 and as I normally do, made a nand backup. When i rebooted the screen started with the LG lov

Go and then showed "security Error" and went no further. Tried removing battery and rebooted but same result. In the end I had to put the phone in Download mode and install the stock D85520H stock rom, which i then updated to 20L and rooted.

I had been on CM 12 Official since August and had no problems up to this point. Am going to stay on this stock for the moment and wait and see if CM gets any better on the G3 or CM 13 comes along a d improves the usage on this phone.

Stransky
[G3 Original Android Development] galmgnt:
Hey.

Couple months ago I disables the CM camera app and started using the google's app.

Now I can't seem to enable it, can't press the button.

Did someone encounter this?
[G3 Original Android Development] omer323:
i don't remember how it's called, but the feature of customizing the buttons you get by swiping from the bottom (instead of just Google Now) is gone for me since the last nightly
[G3 Original Android Development] EdgA#1:
Ring targets?

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] Meneldur:
New BSOD, now at 1 every 1-2 days. Becoming unbearable.

Is there any news about this? There's no last_kmsg, almost impossible to track down.

Mnldr/D855/CM12.1
[G3 Original Android Development] two_handed:
I did a clean flash with build 1012 two days ago and did not encounter BSOD. Are you running stock kernel?

Sent from my LG-D855
[G3 Original Android Development] Meneldur:
Nop, using 777's. I tried stock kernel many builds ago and had BSOD. I'll try again, though.

Mnldr/D855/CM12.1
[G3 Original Android Development] cla94:
How i can remove the super su icon please?

Inviato dal mio LG-D855 utilizzando Tapatalk
[G3 Original Android Development] itsbighead:
Use the SuperSU app by Chainfire instead