yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] raph920:
Hello guys, I tried to install last nightly (20/05) today and I'm pretty sure my G3 is now bricked :( Got an error message at the LG logo screen showing "Secure Boot Error".

I know they are here somewhere but I can't find any instruction as how to repair my phone, can anyone help ?
[G3 Original Android Development] RMarques:
Just flash a Kernel, ie: aCC v1.5...and hit the thanks button!
[G3 Original Android Development] raph920:
Well I don't know what went wrong especially since I already tried to install acc v1.5 right after flashing the latest nightly, but what you just said worked... thanks !
[G3 Original Android Development] RMarques:
I flash new nightlies daily.

Just flash all these files in that very same order, with 2 Dalvik&Cache wipes between each flash. I never got a single error/bootloop doing so!

...you can ignore the Marvel boot animation if you don't feel like having it!
[G3 Original Android Development] frankforpresident:
Is acc v1.5 mandatory? What for use has it? I only flash cm and opengapps..
[G3 Original Android Development] raph920:
I don't think it's mandatory in any way, but I tried to flash it in the wrong order so I had to flash it again.
[G3 Original Android Development] RMarques:
Nothing is mandatory, since we can do whatever we want to, but there is always a correct way of doing things...flashing isn't different!

ACC is a custom and tuneable Kernel designed for AOSP ROMs. Flashing it in last place prevents any unexpected boot sector errors.
[G3 Original Android Development] Charismatic_Batman:
Dialing doesn't work

when trying to dial somebody (dial by number/contacts) the marshmallow icon appears (like when booting) and then the it shows the lock screen. I cannot dial anybody and probably nobody can dial me.
[G3 Original Android Development] youssefkr:
Just a remark : battery life has taken a huge hit since the last nighties. Now I can't squeeze even 3 hours of SOT..

And performance also has decreased ( I don't usually do geekbench tests but I tried it just to see if the performance really decreased and the multi core score went down from 3010 to 2500 ..)

I hope things get sorted out in the next builds.

Cheers to the dev ?
[G3 Original Android Development] :
Is anyone experiencing a black wallpaper on lockscreen? Mine is doing that, but when I unlock the phone, my wallpaper is normal
[G3 Original Android Development] Meneldur:
You are experiencing a reboot.

Check if you are using CM diaper and *not* Google Dialer. Update to latest nightly, too.

Mnldr/D855/16G/CM13
[G3 Original Android Development] Jhonnythereaper:
Can anyone tell me if it's OK to flash this ROM coming from cm12?

*Update*

I flashed, wiped dalvik/cache and perfect

To recapitulate

Coming from stock android 6.0

Flashed cm 12+ installed gapps

Wiped dalvik/cache

After a couple of months I decided to jump to cm 13

Started by flashing cm 13+ gapps aroma zips(excluding dialer and dialframework)

Wiped dalvik/cache twice for good measure.

Let it reboot and alas! Everything working like a charm

With the expected few bugs that is. +1 cm team
[G3 Original Android Development] Windforce0511:
Yes
[G3 Original Android Development] Zatta:
Not necessarily.. You have to make sure you have been on stock android 5.0 or you might experience the emmc brick bug

Taptalked u see .. əəs n pəʞlɐʇdɐʇ
[G3 Original Android Development] Jhonnythereaper:
I installed cm12 from stock 6.0. Does it have to be 5.0?
[G3 Original Android Development] jeremie57:
In this case, it should be good !

It can be 5 or 6.
[G3 Original Android Development] TomBayley1:
After a CM13 update I did a few months ago my G3 would only occasionally get network but mostly it said no SIM detected and was rebooting multiple times a day randomly.

I tried flashing different modems, roms, and back to stock. Nothing worked.

It was under warranty so I reverted to stock and sent it off to get repaired. When I got it back they said they replaced the phone, because I assume it couldn't be repaired.

Now I want to go back to CM but I dont really want to risk the flashing modems again with CM13 since it was a network related problem I had.

So I was thinking of going to CM12.1.

Is it safe to go to CM13 and flash 21c? or CM12.1?

From what I've read I need to go back to L using kdz, flash 21c if I want to use CM13, than flash CM12.1/13 with GApps

At the moment i'm on Android 6.0 with 30c

Thankyou
[G3 Original Android Development] bamiasHELLAS:
If you have stock 6.0 or 5.0 from what I understand it is safe to go straight to cm13. But before flashing cm13 and gapps flash first the 21c modem.

I was in stock 5.0, I have never had any issue
[G3 Original Android Development] TomBayley1:
Ok thanks, and I just use the latest TWRP version to flash it (TWRP 3)?

Just because I read on another forum for a different phone that using a certain twrp version worked to flash a new modem but some others didn't.
[G3 Original Android Development] bamiasHELLAS:
I don't think that that is an issue
[G3 Original Android Development] reepje123:
You are the first one I see who has the same issue I'm having since I needed to flash the 21C modem to update CM13.

I tried updating nightlys regularly and redownloading/reflashing the 21C modem in case it was a bad download/flash.

I came from 30B and my signal is dropping every day. The only way to get a signal again is rebooting until it asks for a PIN code.

So the only way to fix it is replacing my G3? :crying:

I guess I will give stock rom a try, because I bought my phone abroad and it would be a huge effort to get it replaced there.
[G3 Original Android Development] TomBayley1:
I have no idea what caused it either. I was on Stock KK, then L then went to CM12.1 int mid 2015 then clean flashed CM13 in december and I dont think I had 21c then.

It was all fine until march when I updated to a newer nightly between March 10th and 15th I think. That was when it everything started happening.

I tried updating to newer nightlies for half a month and still got the same issue apart from on these nightlies it said I should flash 21c.

Do you get signal like 20-50% of the time? and the rest of the time it says no SIM/network. And I when my G3 randomly rebooted, almost every time I had no SIM straight after it turned back on.

It would even freeze then reboot while it was booting sometimes.

It would reboot when I received a call as well sometimes.

I tried everything I knew of like different modems, APN, new SIM card, different ROMs, Stock L and M but it was the same every time on everything.

When I flashed a new ROM though, sometimes everything would seem like it was working fine for up to 1-2 days, then all the problems start happening.

Is all of this the same for you?

I rang LG and they didn't say much about the issue but it sounded like the person I spoke to never heard anything like it before. I went back to stock 6.0 and sent it off and all they said to me was it wasn't repaired so it got replaced.

It would be good to know what caused it, so I went into detail, if anyone has any idea.
[G3 Original Android Development] reepje123:
Before CM13 I did a clean 30B flash, because I had some problems and it was the only way to get my G3 working again, but nothing modem related.

It all began around the time that you needed to flash the 21C modem to update CM13. I didn't flash any modems before.

For me it's like this: Turn phone on (assuming it asks for PIN), use it normally and after some time my signal is gone. Sometimes it's gone in the morning, sometimes at midday, but definitely till the evening.

I turn my phone off every day when I go to sleep and the last couple of weeks it never asked for a PIN when I turned it back on in the morning, so I always had to reboot at least once before it worked.

I don't have problems with random reboots or freezes.

My next step for now is to try the latest stock ROM and hope for the best.
[G3 Original Android Development] TomBayley1:
Good luck! :)
[G3 Original Android Development] RMarques:
Is anyone having issues, on all nightlies since like a week ago, with local Skype cam image getting heavily darkened several times during web cam Skype calls?
[G3 Original Android Development] joaonds:
Please:

Actually, my rom is Fulmics 5.2 (android 6).

To flash this CM13, i need modem RADIO_D855_21C before flash this rom ?

My model is D855 (Brazil).
[G3 Original Android Development] agritux:
You need Lolipop modem. Any V21 can be ok. Because MM modems not working with bumped Lolipop bootloader.
[G3 Original Android Development] Wishmesh:
Answering my own question. I don't know if that is caused by fact that I tried to remove AOSP keyboard with TB... (unsuccessful)... but suddenly Play store offered to update AOSP keyboard with Google keyboard.

Now I have Google Keyboard version 5.0.25.122319759-armeabi-v7a (Updated on May 16, 2016) ;)
[G3 Original Android Development] raph920:
Just tried to install the newest nightly without flashing aCC v1.5 at the end and I faced the same issue as before (Secure boot error). Flashing aCC solves this but is there any way to not have to flash it ? Does CM13 come with a custom kernel I could stick with ?
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] another cm based rom dev i know found a fix for the navbar and also has a handy amount of navbar additions... if he approves can you suggest the commits to the official builds?

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

Guys what are your opinions on the new browser?
[G3 Original Android Development] RMarques:
I'm rolling with chrome beta.
[G3 Original Android Development] FooFighter312:
I'm using Google Dialer and experiencing no problems at all
[G3 Original Android Development] ThePurpleK:
If you're getting that error, the image needs to be bumped.
[G3 Original Android Development] raph920:
The image is bumped so I don't think this is the issue. Plus if I flash it after installing the newest nightly the secure boot error stops.

I think I'll just try again to install the nightly without the kernel and see if the error occurs, maybe I did something wrong last time :)

Edit:

I must have done something wrong because I just tried to update to the latest nightly without flashing aCC kernel and it worked. Thanks anyway :)
[G3 Original Android Development] ad astra:
Hey guys/gals, it's been a while since I don't join the nightly's train. In fact I still roll with CM 12.1.

I know about the eMMC bug, do I need to flash an original LG rom with their tools, to avoid it? Or can I just flash a stock 6.0 ROM with twrp?

Note: I am pretty certain that my last LG stock android version was KitKat (4.4.2). I'm not 100% sure if I need to flash a Lolipop before I go with Marshmallow. Could you also confirm that?

Does anyone have a handy guide to do this?

Thanks a lot!
[G3 Original Android Development] MisterRio:
Is it possible to enter this device test?

http://forum.cyanogenmod.com/topic/81988-black-screen-during-call-jfltexx/

Code 3845#*855# doesn't work
[G3 Original Android Development] ravenhr:
Thanks, I'll keep that in mind for next instalation (in a few days, I'm tired of constant switching :))
[G3 Original Android Development] Tchiort:
Quote:

Originally Posted by CatalinBRB

For your LTE to work you need to keep only one apn(the one that works with your carrier), delete the others, it makes a conflict between them. After you delete do a reboot and it should work

This is unfortunately not that easy - although it may work for you. There are options which are not available yet in that ROM and that is problematic. I can't make 4G work on my phone with only one APN added.

We have to be patient, the ROM is brand new.
[G3 Original Android Development] Step-han:
[MENTION=4574857]finnq[/MENTION]

On CM12.1 with stock kernel on idle state, it uses 1 core @ 300mhz. On CM13.0 it uses idle 2 cores @ 300 mhz. Its always in dualcore mode. Why it that changed? Better performance?
[G3 Original Android Development] munkiii:
USB-OTG Problem

When i plug in a USB device using an OTG adaptor, my device appears as a notification where i can "Explore" the OTG storage

This allows me to view the OTG storage and to copy from the OTG to my phone/card memory, but i can't seem to copy from my phone/card memory to the USB-OTG storage.

I also can't find in ES File explorer where this OTG storage is mounted.

Can anybody help?
[G3 Original Android Development] radek007:
LTE working when install Opera Max
[G3 Original Android Development] ianthemojo:
Is this ROM stable enough to be used as a daily driver? As of 20151203 release.
[G3 Original Android Development] Akatoikitos:
More than enough...
[G3 Original Android Development] omer323:
after a clean install, CM13 is much more stable for me than latest 12.1.

i had lot's of random reboots, black screens...

since the first day of 13 - had NONE.
[G3 Original Android Development] MattiasKarlberg:
I cannot download files using Chrome, any ideas?
[G3 Original Android Development] Akatoikitos:
Did you tried clearing cache/data of chrome?
[G3 Original Android Development] MattiasKarlberg:
I am really sorry... I should have tried that first... Sometimes I am a bit sad about being born with this brain of mine... [emoji6]

It works now, thank you kindly!
[G3 Original Android Development] drolgnir:
I was thinking about starting a CM13 thread for the D852, unless the bugs between the devices are the same?
[G3 Original Android Development] stevo3337:
Quality ROM, super smooth and great battery life. Only issue is with video recording but installed cameraMX from play store and now all good. Thank you Devs :)
[G3 Original Android Development] Darkapolo:
The phone became very hot when it is charging and listening radio via WiFi (with screen turned off).

Enviado desde mi LG-D855 mediante Tapatalk
[G3 Original Android Development] haris182:
great rom so far

gps is so fast in locking

but, I can't select 3G or 2G on mobile network settings :(

currently on 2015-12-03 build
[G3 Original Android Development] kjwaugh:
Please do

We need a CM 13 for D852 thread - thank you for stepping up.
[G3 Original Android Development] boss4eto:
I have search thread but without result, so can you tell me, is there way to root it, I am very pleased with ROM so far, later I will share bugs and issues I found. Thank you.
[G3 Original Android Development] shivaagarwal1:
Goto developer settings and enable root access to apps and adb.
[G3 Original Android Development] Fade2:
But how to hide that root mark in status bar?

Odesláno z mého LG-D855 pomocí Tapatalk
[G3 Original Android Development] aha360:
Ideally, flash any Lollipop/Marshmallow LG stock ROM using any of the openly available tools on here and you should be safe, and like I said, for safety's sake, you need to go from Lollipop to Marshmallow and NOT jump straight to Marshmallow first, especially on a stock ROM.
[G3 Original Android Development] ThePurpleK:
You need to flash an original ROM with their tools. I jumped to 30B (stock MM) directly and I'm fine, but I wiped everything. Idea is that it makes no difference whether you go from stock KK to MM or via LP because the tools overwrite the partitions of the phone entirely.
[G3 Original Android Development] Meneldur:
Feels good, quick, no rendering problems, minimal. The only thing missing with Chrome is Google sync with desktop Chromes.

Mnldr/D855/16G/CM13
[G3 Original Android Development] Omar-Avelar:
eMMC Corruption (a.k.a ext4 corruption)

Hey [MENTION=4574857]finnq[/MENTION] -- I would like to understand better the eMMC bug that people keep mentioning. Does it manifest to people as a device not booting? And it is 'fixed' by re-partitioning with the LG flash tool?

With some experimentation here I have found that currently the userdata partition (which holds /data and the internal sd) become corrupted after a lot of 'reboot' cycles on the device I am using (D855 on my case) using CM13. Users can check if they have some mild-corrupted partitions by going into /data/lost+found and seeing a bunch of 'recovered' files.

After some investigation it seems like the " journal_async_commit" option we are using in the mounts look really suspicious.

Just googling " journal_async_commit" points to links saying about EXT4 data corruption... it is seen in the LWM website from 2012 (that I don't see as resolved) and I am wondering if the Kernel versions we and other people are using could be vulnerable and hence why we eventually get corrupted filesystems and call it 'eMMC bug'...

EDIT: I will be running the phone myself with that "journal_async_commit" mount option removed, but so far I have done reboot tests of 30-40 cycles without hitting the bug now -- I am attaching to this post a flashable script in case anyone else who experienced the corrupted partitions bug wants to give it a try. :fingers-crossed:

UPDATE: There's a tiny chance that TWRP 3.0 can also induce the error too if mounting the cache and data partitions, so better patch that too with the second zip. Since TWRP 3.0 is using the fstab based on CM's.
[G3 Original Android Development] Simone98RC:
Hi guys,

I appeal to CM developers:

1) Why 60 FPS recording is not implemented yet? It would be much simple (3rd-party apps like Open Camera support it).

2) What prevent you to make laser AF working? Proprietary driver under AOSP is buggy, there are license troubles... ?

Thanks in advance
[G3 Original Android Development] ThePurpleK:
The eMMC bug shouldn't be related to the filesystem, especially since users who used f2fs also experienced the bug. The eMMC bug is rather something to do with flashing CM13 over a stock KitKat ROM. We aren't sure what exactly happens, but having a stock KitKat ROM as a base breaks things. It's solved by flashing stock LP/MM then CM13.
[G3 Original Android Development] Omar-Avelar:
I don't think there's enough data out there to say that F2FS is having the 'corruption' or not. However I can give more data into why I strongly believe the problem lies here and why this is not a coincidence. Strangely everyone reported that the issue started to appear during December 2015 (and that's also seen from your forum posts on this issue).

https://github.com/CyanogenMod/android_device_lge_d855/blob/cm-12.0/rootdir/etc/fstab.g3

vs

https://github.com/CyanogenMod/android_device_lge_d855/blob/cm-13.0/rootdir/etc/fstab.g3

What a coincidence that between CM12 and CM13 journal_async_commit was added.

https://github.com/CyanogenMod/android_device_lge_d855/commits/cm-13.0/rootdir/etc/fstab.g3

And specifically, that this mount option was added the first week of December as seen on the GitHub log...

[IMG="Don't think this is a coincidence"]http://i.imgur.com/yln6XtL.png[/IMG]

I personally would suggest people use the *.zip I posted above that removes journal_async_commit. And [MENTION=4574857]finnq[/MENTION], let me know your thoughts on this. I also don't believe that journal_async_commit provides much benefit and just believe that you inhered this change from invisiblek, I strongly believe this mount option should be removed to prevent ext4 corruption.
[G3 Original Android Development] ravenhr:
Nightly 20160528 - I have lost LTE...
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] man commits for the navbar ��

https://github.com/XOSP-Project/and...mmit/c30bdf1a0aa15e8461cdbf678ee132023c8d6781

https://github.com/XOSP-Project/and...mmit/cdc8be872bcb3917ea871ba17995007245d1313a

They will fox navbar size on landscape
[G3 Original Android Development] jeremie57:
I have not this issue !
[G3 Original Android Development] Wishmesh:
The same nightly build.

I have lost External SD card during night. It showed error, that SD card needs to be formatted... rebooted... and no more SD card.

My PC still recognizes SD card and all the data... it seems that broken nightly build or something...
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] commits do not fix the issue ignore them
[G3 Original Android Development] mabs67:
Where would I find those settings?

My phone charges fast after a fresh reboot, but somehow forgets about it after a day or so.
[G3 Original Android Development] ravenhr:
Why NOBODY answers, no new posts? Is there some problem with this thread????
[G3 Original Android Development] iambig:
Everything works fine, the only (small) issue I can recognise is the poor SOT.

Personally I use the phone on the car often (every day for at least 1 hour) Ok google works, bluetooth works, GPS works. At home WiFi is great, GSM-LTE switch goes pretty well, photo is absolutely good with snapcamera (just for an example my photos on https://www.instagram.com/gintronic4/ ), audio quality with Spotify is good (I'm using good mid quality sony in ear/on ear), google keyboard works good (from playstore, not stock rom).

I'm Just happy about the phone.
[G3 Original Android Development] kuzaro:
Since aprox. 1 week I have enormous issues:

Battery drain

Random reboot
[G3 Original Android Development] eradicator006:
Are you using f2fs on cache and data? If so, that's the cause of your random reboots. I had that issue recently. I get the same thing on exodus when using f2fs. The f2fs kernel driver is crashing for some reason.
[G3 Original Android Development] Tyler123456:
ROM is great for me besides slightly less SOT, battery percentage in status bar is oddly position too close to the time, and damnit STILL audio is poor! Hiss is still present, fluctuation in sound when changing volume is still happening also. I don't understand how sound issues haven't been fixed considering its one of the main parts of any phone. Also a new problem with sound, when a song automatically changes to the next in the list, for some reason audioFX stops working, have to force close music and reopen to get the equalizer running again. Doesn't ever happen if I mentally change the song though. Keep up the good work
[G3 Original Android Development] ravenhr:
My current problems are:

- no LTE whatsoever

- random cell connection droppings and sometimes it needs reboot to register on network. Not just data, whole cell connection, which renders me unavailable to callers.

SOT is OK, I guess, and I don't have any other problem with ROM. I don't know about hissing as I didn't use headphones in a while now...
[G3 Original Android Development] Tyler123456:
Have you tried going in settings and checking if access point is correct? For me after some random updates the APN changes and I have to either change it to my network (EE) or manually add it if my network has magically deleted
[G3 Original Android Development] ravenhr:
Been there, done that several times (first though, I think I have reset it 6-7 times) - still no LTE.

When I enter *#*#4636#*#* under Phone information, network type is HSPA - on same place I had LTE without problem few days ago. Exactly same place - same chair in my living room on same place...

Preferred network type is set to LTE/GSM auro (PRL), but it doesn't recognize network as LTE...
[G3 Original Android Development] Samueldw:
Noticed that too :(
[G3 Original Android Development] RMarques:
I've been using and dirty flashing nightlies for a bit more than a month but since around 04242016, my cellphone battery sometimes don't charge at all. I'm using the original AC charger, it shows the animation where you can see it's supposed to be charging but battery percentage never goes up!

It's random, although, it's been happening more and more lately. A reboot usually does fix it!

Anyone else?
[G3 Original Android Development] raph920:
Are you using aCC kernel ? I read several posts on their thread mentionning this issue occuring at completely random times. Apparently it is an an identified bug and the workaround is to remove the battery once to stop it from happening until you flash the kernel again.
[G3 Original Android Development] RMarques:
Yes I'm using it indeed! Thanks man!