yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] internetjlmb:
Hi I was on stock MM rom and recently tried cm13 05-02 nightly everything works OK but I'm having problems with charging is really really slow, I tried nebula kernel, 06-02 nightly, and 21c modem, nothing seems to solve the problem, I did a clean install by the way, I hope someone can help me with an idea of what could be happening
[G3 Original Android Development] tooomins:
Try changing usb cable. For me usually this is the main problem.
[G3 Original Android Development] internetjlmb:
Already tried that, same result
[G3 Original Android Development] Meneldur:
Rapid charging working nicely right now, 20160205 with stock kernel and original USB adapter + cable.

Mnldr/D855/16G/CM13
[G3 Original Android Development] sloseph:
I just wanted to drop I and say I'm running 01/02/16 nightly and it's been running like a dream for since I flashed on Monday, I've had no random shut downs, no freezing and no camera problems

My only slight gripe is Netflix doesn't work but that's really not an issue I care that much about

So huge thanks to everyone who worked to get this rom where it is, you've done amazing work
[G3 Original Android Development] ThePurpleK:
Netflix has been working as of recent updates, including the current build. However, you have the issue of loud earphone hissing.
[G3 Original Android Development] ThePurpleK:
Have you tried a clean flash? Tried reverting back to latest stock MM ROM and going back to CM13 (assuming your last stock ROM was pre-MM)? Charging is fine for me.
[G3 Original Android Development] sloseph:
Is the Earphone hissing a constant thing or just on netflix?
[G3 Original Android Development] ThePurpleK:
In general. It occurs every time (lasting many seconds) when audio is meant to play, including just touch sounds.
[G3 Original Android Development] StuckinMemphis:
Just thought I would share my experience although it's not likely to help anyone.

I'm on the International D855 in Australia.

Last firmware update via LG Flash Tool - D85520t_00.kdz LG hasn't updated my IMEI to marshmallow

I waited to flash CM13 with all the scare about emmc. Then I saw the post on here that it is believed if you have flashed .kdz to latest you may not suffer the emmc problem. So I jumped in as CM12 was really starting to have increased random reboots.

I did a completely clean flash of the 1-30 nightly and have dirty flashed every nightly since then.

I can't say that I can find a single problem, not a single BSOD or random reboot. I use headphone jack to listen to podcast in my car (no bluetooth in car) no hissing ever. WiFi, LTE, Bluetooth and everything is working perfectly.

I don't use Netflix. I can't say if that works for me or not.

This is absolutely fine for daily driver.
[G3 Original Android Development] JDMpire:
Can you tell me what problems there has been with the EMMC. I have a D851 but that's shouldn't really make a difference. I've been flashing these CM nightly for a while with no issues (no flash issues that is).

Also what happened to the battery life? One of the Nightlies from about a week ago got the most Amazing battery life. It more then doubled! I couldn't believe it. Then it seemed to go back to its normal poor life...Aside from the upgrade I did nothing else on the device that would have contributed to such a drastic change in battery consumption.
[G3 Original Android Development] StuckinMemphis:
I can't speak personally about emmc. I have not experienced the issue. If you read back through this thread you will find it documented rather well. It sounds pretty scary. I am just not knowledgeable enough on the issue. All I know is it scared me away from flashing CM13 for a while.
[G3 Original Android Development] dimine:
On which channel? One of 36 - 48? Or a higher one?
[G3 Original Android Development] ThePurpleK:
WiFi Channel Analyzer shows that 44 and 48 are available to me.
[G3 Original Android Development] kulenski:
Q: eMMC bug possible workaround

Can I ask all you guys that took the approach to flash the Latest KDZ before flashing CM13. I read all the posts since archcry's post and I did the same thing and I can say that I haven't experienced any shutdowns since.

My question to you guys is, which "LATEST" KDZ did you flashed: V20+ (LP) or V30 (MM). I did flashed the latest available for my IMEI, which was d855(21A) LP. I'm trying to figure do I need to flash the 30B (MM) to avoid it or anything after stock KITKAT will do the work.
[G3 Original Android Development] superawesomeme:
I flashed the D855 MM from here that was shared after the release in Poland. (30/12/15 I think)

I then flashed CM13 in early to mid Jan. My last clean install was using nightly 20160121.

My experience has been almost flawless except for:

• No BLE support (FIXED 20160121)

• Camera crashes (FIXED last week)

• No FM radio (FIXED 20160204)

• No support for Android Pay - this isn't available in my country yet but I also understand that CM isn't supported at all, even if you live in the states.

A few niggles that probably will never be addressed:

• LED does not disable during Do Not Disturb mode.

• CM Theme Engine requires you to clear your launcher data after changing icon pack.

• Gallery is piss poor. You can't move photos between albums/folders.

That's it really. It's a much shorter list than the issues I've had with LG Stock and it's ugly design, bloatware and restrictions.
[G3 Original Android Development] RL77LUC:
It makes a difference. D855 seems to be the only one who has the eMMC issue, because our kernel is different (again, if I'm correct, I don't look at other variants changelog). The new CM13 kernel for d855 has a bug who crashes randomly eMMC and requires you to open the phone to put the SoC on debug mode. It seems to be fixed when you flash MM KDZ before CM13.

I think there's an option to disable LED when you're on Do not disturb mode. You should check in settings.

Btw, I flashed MM KDZ, then installed TWRP via KingRoot/AutorecMM, then updated it to 3.0.0.0 and installed CM13 yesterday, so far everything is fine, no eMMC issue at all, camera is working again (it wasn't with dirty flash).
[G3 Original Android Development] ThePurpleK:
You need the latest MM one.
[G3 Original Android Development] kulenski:
Thank you, I'll try it and get back after a couple of days to report. Just for information (if it is helpful) I've been using Cm13 flashed on top of KDZ 21A and didn't have any issues for 3 days.
[G3 Original Android Development] StuckinMemphis:
Now I'm confused. Do I need to flash the 30b kdz from Poland or is it okay to run 20t? I came to CM13 from 20t. Been running nightlies for a week with no issues. My phone is International D855 in Australia.
[G3 Original Android Development] ThePurpleK:
Isn't v20 KitKat? If the hypothesis that running on old firmware leads to the EMMC bug is true, then you might run into the EMMC bug. The recommendation is to flash the latest possible stock ROM, which should be MM. As for the KDZ you need to flash, I'm not sure since you aren't in Europe.
[G3 Original Android Development] youssefkr:
Hey guys, I just got my hands on an LG G3, I was wandering if I flash this rom , or any other rom for that matter, will it be easy to restore to stock ? Thx
[G3 Original Android Development] RL77LUC:
He could flash Europe file in Australia phone without issue. D855 is D855, it's the same device.

Yes it is, you only need to go to download mode if you want to go back to pure stock, which is very easy.
[G3 Original Android Development] kulenski:
V20[X] and V21[X] are all Lollipop. KitKat is V10[X]. I'll stick with my latest official Lollipop (21A) so we can see. If the bug occurs again we'll know for sure :)
[G3 Original Android Development] dimine:
Well, that backs my findings that low channels 36, 40, 44 and 48 work, but higher channels do not work with current kernel. If you could select a higher channel on your access point/router (not all devices support this) and try to connect afterwards, i assume it wont work anymore.
[G3 Original Android Development] vBurak:
Hey, I installed on my G3 D855 yesterday CM13 20160206 after a full wipe. It really works good and no crashes or freezes! But there is a problem with the mobile connection for me.

I'm in Germany with Vodafone as provider and using LTE. The mobile connection completely falls down for several seconds. It works for now but after some minutes it is going away again.

Any suggestions what I can do? Can I someone tell me how to get some logs to analyze the cause? I had stock MM on it before and did a full wipe.

Thanks!
[G3 Original Android Development] iambig:
With TWRP 3.0.0 is possible to navigate microsd formatted like internal storage.

Just flash the new recovery and try. So cmupdater is returned to be completly fuctional another time.
[G3 Original Android Development] takis:
The same issue here only on 4g tho
[G3 Original Android Development] superawesomeme:
4G is LTE
[G3 Original Android Development] takis:
Yeah false tho there haha
[G3 Original Android Development] TwinHeadedEagle:
Is Youtube hd resolutions freezing problem fixed?
[G3 Original Android Development] ThePurpleK:
Yup. Fine for me.
[G3 Original Android Development] superawesomeme:
Yes. No problems at all with YouTube.
[G3 Original Android Development] mainicia:
that's weird, I can't update 20160206.

It's said "update script error", I'll try 20160207 tonight and check again.
[G3 Original Android Development] SourPower:
Love the ROM thanks a lot
[G3 Original Android Development] Samueldw:
Is it possible to record calls (both sides) in this rom?
[G3 Original Android Development] jeremie57:
I have not found the possibility...

Now that things seem calmer about the kernel, I wonder if the GPS fix problems that we are facing since Lollipop have a chance to be solved by the Cyanogenmod team or if we need to wait for Google team.

Namely: if I turn off the datas and I turn on the GPS (high precision mode or device only mode), the GPS fix is good, but I lose it every 5 minutes for about twenty seconds.

If I let the datas activated, the situation is better and if I put the phone in airplane mode, the GPS works great ! :eek:

I had this issue with stock rom under Lollipop, CM12, CM12.1 and now with CM13...

I had absolutely no problem under kitkat (stock rom) and it seems that all models are affected: https://code.google.com/p/android/issues/detail?id=81140
[G3 Original Android Development] S.AMU:
Is someone getting viper4a to work?
[G3 Original Android Development] wjazdbitu:
I cannot access Contacts: "You have disabled a required permission" (today's build). I granted all, turned it off and on few times. Anybody?
[G3 Original Android Development] Akatoikitos:
Last build and camera works great!
[G3 Original Android Development] flausatu:
No problem at all with today build...thank u for this one.
[G3 Original Android Development] Sorin90:
Finaly a great mantainer for CM ! Thank you. :)
[G3 Original Android Development] wojtek007pl:
Viper4android works, you just have to wait a little bit more time while its installing drivers(I had to wait around 30 seconds).
[G3 Original Android Development] TwinHeadedEagle:
What gapps to install? With open gapps getting Setup Wizard has stopped :mad::mad::mad:
[G3 Original Android Development] EthericGhost:
Which version are you using? I used Nano without issues.
[G3 Original Android Development] skrippi:
Formatting SD to use it as internal storage

Hey guys,

I just wanted to try the new feature of Android 6 "formatting the SD Card for using it as internal storage".

But it doesn't work...

When I choose "Format SD as internal storage" it instantly shows me the progress bar of 20% and says "do not eject SD until finished...bla bla" but it never finishes.

The window only dissappears after a few minutes and that's it. After that the SD card also dissappears from the system and any file browser until I format it in recovery again.

Whats wrong? Any solutions?

Regards, skrippi :)
[G3 Original Android Development] Tchiort:
We are talking about that earlier in this thread.

Format your card in Fat32 and it should work.
[G3 Original Android Development] skrippi:
Ah sorry missed it. But thanks a lot!

You mean formatting it in fat32 @ PC and after that in my phone?
[G3 Original Android Development] Tchiort:
Yeap!
[G3 Original Android Development] vassagout:
did you change the selinux mode to permissive?
[G3 Original Android Development] Step-han:
Contacts works for me, even with dirty flash 20151130 over 20151129. On 20151129 its worked too for me.

On 20151130 taking pictures, filming (720p & 1080p) and facebook are working correctly.
[G3 Original Android Development] pradeepjoshua:
How to disable vibrate on touching navbar buttons
[G3 Original Android Development] :
I think battery in CM ROM drain faster than stock. Am I right?
[G3 Original Android Development] wojtek007pl:
Yup
[G3 Original Android Development] MattiasKarlberg:
I love the rom, so fast!! However I have a small issue with whatsapp... Sometimes messages does not reach the destination and I sometimes get messages like 30 minutes after they were sent. Anybody have any ideas?
[G3 Original Android Development] derekoh:
Just installed the latest CM13 nightly and mostly it's fantastic - thanks finnq!

I'm experiencing most of the same issues as others. The key one for me is that my phone is stuck on 2G and I can't select either 3G or LTE. Fortunately, WiFi is working fine, so I'll make do for now.

Interestingly, I use Tasker to turn on/off LTE/3G when I'm connected to WiFi by setting Mobile Data to 3G Preferred. When I try this on CM13 I get the error "Mobile Data 2G/3G isn't available on this device."
[G3 Original Android Development] vassagout:
thanks. My problem is /system/su.d/vyper50.sh (for enable media server without changing selinux to permissive) doesn't work as on cm 12.1.
[G3 Original Android Development] omer323:
how is it seems calmer if emmc is still present? =\
[G3 Original Android Development] jeremie57:
Yes but the team made a wonderful job since beginning of january.

A lot of issues have been solved and it's better every day !
[G3 Original Android Development] dimine:
I had the same problem, i fixed it by setting the option to Never (in german: Nie). Sounds strange, but now my wifi keeps connected in sleep mode. Maybe ist only an error in the german translation but maybe its a general bug, have you tried that already?

Sorry, that must have been something else that kept my wifi alive, today it is disconnecting in sleep mode again ...
[G3 Original Android Development] ravenhr:
Does LTE works? Not only selection, but also the connection?

My provider works on 1800 MHz, not usual 900, and on CM12.1 and this I could never get LTE.
[G3 Original Android Development] SourPower:
Weird thing I woke up this morning and my phone was stuck after restarting, it was optimizing apps but didn't load. Afterwards I kept getting stuck when my privacy guard would pop up to ask if I wanted to give permissions for some things like locations,recording sounds, access to contacts etc. Anytime it popped up to confirm the permissions it froze
[G3 Original Android Development] Meneldur:
Works here in Argentina, at least for me.

Mnldr/D855/16G/CM13
[G3 Original Android Development] ravenhr:
I don't care is it in Argentina, Mexico, Croatia, Mars or Venus, as long as it works! Thanks!
[G3 Original Android Development] iambig:
I'm using LTE in Italy with 800-1800-2600, the carrier is Vodafone.
[G3 Original Android Development] ThePurpleK:
The hypothesis is that if you restore to latest stock MM and flash CM13, you will not experience the EMMC bug. Three days in, I've experienced no EMMC issue.
[G3 Original Android Development] aha360:
Or even the latest Lollipop release, as I have done - in fact (thank God), I haven't had the eMMC bug since I had received the replacement handset (LG G3), though in this case, it came shipped with Android 5.0 out of the box.
[G3 Original Android Development] ThePurpleK:
Re. MEGA SD card selection bug, MEGA staff have replied to my email to state that developers are working on it!
[G3 Original Android Development] Cytovan:
Hey guys !

Testing the ROM (20160206 build) on my D855/16g since last night.

I have not tested everything but I have to admit, that ROM is smooth ! Great job !

However, I encountered two problems : some YouTube videos simply won't start and a message will show up saying "Connection to the server lost", and no matter how many times I restart the video, the same message shows up; and some will play properly (not mentioning the hissing in the background sometimes)

The other issue is that I can't access my phone's storage on my computer. Internal and SD storage won't show up, sayin "This file is empty". I'm on Win 10 btw

Voilà ! Hope it'll be fixed soon ! Bye !
[G3 Original Android Development] takis:
Great!
[G3 Original Android Development] ThePurpleK:
File handling is fine for me. I have the same setup as you. Check the storage option - does changing between MTP and PTP work? Check the cable - does it support data transfer and work on transferring other devices' data? Check your drivers - have you tried the plug and play drivers and then nstalled official ones?
[G3 Original Android Development] Cytovan:
Aaaaand you just solved my problem !

You were right, I was on "charge only" mod instead of "file transfering" mod :p

Thank you kind sir ! :good:
[G3 Original Android Development] ctnkyx:
Is good thank you

LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
[G3 Original Android Development] spanorg:
Do you all have lag on launcher? I do by the way...(nebulah kernel).
[G3 Original Android Development] jeremie57:
Everything works great for me with the launcher...

I use Nova
[G3 Original Android Development] spanorg:
Which kernel do you use?
[G3 Original Android Development] jeremie57:
I use CM kernel.
[G3 Original Android Development] spanorg:
Maybe this is the reason of the lag. However, I don't want to use CM kernel in case of emmc bug.
[G3 Original Android Development] RL77LUC:
CM kernel is snappier with default settings.

I you flash MM KDZ before re-flashing TWRP and CM13 nightlies you should be fine with CM kernel.

I'm currently running it without that eMMC bug, just like pretty much anyone else who have done this. But this requires a bit of work and time (not that much) and there's still a risk (but, well, that's nightlies, and custom rom, there's always a risk).

If you don't want to bother you can also change Nebula settings (especially governor/thermal control).
[G3 Original Android Development] writely:
Yes, same with me. Lags in Launcher with Nebulah.

But Nebulah as for me has almost no hissing sound in headphones.
[G3 Original Android Development] agritux:
i dont have any emmc problem with stock cm kernel

what is emmc bug?

and i have no lag with launcher. i am using nova launcher.
[G3 Original Android Development] podkilla:
I had the emmc bug right after Christmas after flashing the 25/12 build.

I had to unbrick the phone and shorten the pins as explained in this thread a couple of times.

I flashed the stock ROM and after that went back to the working 22/12 build, which is running my phone ATM.

Is it save for me to update to the recent builds now?
[G3 Original Android Development] jeremie57:
I experienced the same issue a few days later.

I have installed the last stock rom available (Lollipop) with Flashtool, root the phone, reinstalled TWRP and I waited on CM13 build from 22/12 until middle of january.

Now, I flash every day new builds with no issue...
[G3 Original Android Development] RL77LUC:
If the stock rom was MM, it should be safe, but there's no way to be sure. However, all reports has been good until now, so you should be fine.

You should flash MM. It's the MM bootloader which is supposed to fix that issue.
[G3 Original Android Development] jeremie57:
I read that after reinstalled everything ...

No risk, no fun ...

We will say that I serve as a guinea pig :D
[G3 Original Android Development] RL77LUC:
It's not an exact science ^^.

Some people never had eMMC bug without flashing MM rom first (including myself).
[G3 Original Android Development] takis:
Guysis the hissing sound fixed?
[G3 Original Android Development] spanorg:
Just to share my experience...

I flashed latest nighlty without having flashed pure stock mm and all works perfectly.Really good built !!!

Question:

LTE is working perfectly but I have no data symbols (3G-4G etc). Any clues?
[G3 Original Android Development] Trudi:
No, sound hiss not fixed yet. But a bit reduced with Nebula or 777 kernel.

For people who have lag in their launcher, I had it too. Solved after a clean flash.
[G3 Original Android Development] podkilla:
well I don't think it was MM stock. Iirc it was android 4.4. can you tell me where I can get a mm stockrom?
[G3 Original Android Development] eradicator006:
If you use autorec for MM to install TWRP, it replaces the bootloader with probably a KK version. I don't think the bootloader is part of the emmc problem. It could have something to do with the partition layout that the MM kdz uses.
[G3 Original Android Development] C.Fava:
For what i read in this thread, i think that the issue with eMMC happened with people that they last firmware was kitkat, i think lollipop it's fine, i have flash cm a lot of time and no eMMC bug (my phome came with lollipop).

I think everyone reading this thread should post his situation, to see if the premise is rigth.
[G3 Original Android Development] RL77LUC:
It's on the KDZ repository for G3. Use search to get it.

Really ? Where is that from ? I've no idea of how AutoRecMM works, but the idea mentioned before was bootloader-related.

I don't think it's a partition layout issue. Partition layout issue wouldn't cause random crash, especially considering that flashing old CM13 kernel seems to prevent eMMC bug.

Could be. But just to be sure I would advise to flash MM, I think, since CM13 is MM.
[G3 Original Android Development] StuckinMemphis:
D855 - Flashed 20t.kdz Lollipop with LG Flash tool. Ran Autorec to get TWRP. Been flashing nightlies since January 30 with no issues at all.
[G3 Original Android Development] finnq:
It's true, the app reverts the following partitions back to older versions: aboot, sbl1, rpm, tz, dbi, (laf, modem, boot, recovery). I'm still looking for the cause of the problem.
[G3 Original Android Development] RL77LUC:
Well, that's weird. And I guess it reverts it to KK version ? Because Lollipop seems to "prevent" the issue too according to previous reports.
[G3 Original Android Development] C.Fava:
Any version of Autorec flash Kitkat bootloader because lollipop and MM bootloader could not be Bump.
[G3 Original Android Development] Slothboy:
Put it this way, I'm on 21C and my phone came with Lollipop out of the box (Not sure what baseband version unfortunately) And I had been on CM13 for a good 2-4 weeks before switching to Fulmics when people were pointing out the eMMC bug.

Just want to confirm, the solution thus far is to update to LG's latest ROM, root, flash TWRP, then CM13 and it'll be okay?
[G3 Original Android Development] Tyler123456:
I had the emmc bug at Christmas time, couldn't be bothered with shorting pins and was half a month till warranty would run out so I sent the phone to lg for repair. They swapped out the whole motherboard for a new one. I flashed KK KDZ as I previously had it already downloaded and hadnt read here about MM theory, and KK is easy to root/twrp, went to cm13 and been going 3 weeks with no issues except horrible audio hissing/screeching noise. Just changed to 777 just in case and to slightly fix audio( also if 777/nebula doesn't fix hissing, make a phone call, unplug and replug headphones then press play again and it should work better)
[G3 Original Android Development] RL77LUC:
That's what I thought.

Well, that's weird...

It should be ok. So far it works, but we don't know why or how, so we can't predict what will happen.
[G3 Original Android Development] StuckinMemphis:
Is there a requirement to flash TWRP by another means than AUTOREC?
[G3 Original Android Development] RL77LUC:
No, AFAIK, everyone here is using AutoRec to flash TWRP on MM Stock Rom (and there's no reason to change that, because it works fine).