yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] marn3us:
Try to .kdz back to stock via LGUP, this usually solves any problem :)
[G4 Android Development] jahmezis45:
Im going on vacation tomorrow and I have no phone SMH how is it this has only happened to a few people and no one else. I don't believe this was a few isolated incidents as the cm downloader said I shouldn't update to new version because of the low ratings the rom received but I updated anyway. No word from the developers for a fix either.
[G4 Android Development] mattgoldey:
I will probably try this, I just don't have ready access to a Windows PC.
[G4 Android Development] benchmade707:
Same thing here, 9/28 update rendered my phone unable to boot past "loading apps." I tried wiping, Nandroid, full format, 3 different ROMs, Exodus, Resurrection, and the stock T-Mobile that is linked to in the original CM13 post here. The stock T-Mobile is the only one that almost works, though it's having all sorts of weird issues. It does boot and mostly works, at least.

Exodus booted, but gave a totally black screen, the only function was the power menu, which seemed to work fine.

So full kdz stock is going to be my only option? I'm tempted to just stay stock after this, it's the 2nd time I've lost everything on the phone due to CM.
[G4 Android Development] benchmade707:
I just realized that the stock h811 MM image linked to in post 1 IS the factory KDZ image. It says in the kdz thread that there is no benefit over using TWRP (the method I used) vs LGUP. I'm having all sorts of problems, camera and "call" crash all the time, messaging acts funny, no function from either spotify or audible, my main used apps.

Is there anything that LGUP will do that flashing the LG-H81120i-Flashable.COMPLETE.zip won't do? I still have an unlocked bootloader and TWRP, so it's not TOTALLY stock.
[G4 Android Development] benchmade707:
Correction, even with the LG-H81120i-Flashable.COMPLETE.zip ROM it is nearly unusable. I get maybe 10 minutes of partial function every hour, the rest of the time the screen is non-responsive. I can wake it with a doubletap, but not enter the code to unlock. It'll kind of work for a while, then stop responding and appear to lock itself after a few minutes. This issue with nonresponsiveness only began after about 5-6 hours of the flash, it may have began after I set the phone to vibrate.

Going to try an LGUP revert to stock when I get home, but I'm becoming less optimistic, beginning to think my phone may go in the trash thanks to CM.
[G4 Android Development] xrad:
If in doubt I would always prefer LGUP over some Zip just because LGUP the official procedure from LG. Nobody knows what black magic it applies to get things straight again on the phone.
[G4 Android Development] knzor:
[MENTION=3208754]codeworkx[/MENTION] and/or [MENTION=5776465]genesixxbf3[/MENTION]

Recent V20h firmware from LG fixed quadrooter vulnerabilities, I've completely reset my h815 device (full wipe + flashed firmware from lg bridge) and tested with this tool.

I've then flashed CM13 20160928 nightly + pico apps, tested again and CVE-2016-2504 vulnerability was still present. Is this normal behavior due to kernel being overwritten by CM's one?
[G4 Android Development] genesixxbf3:
Vulnerability are from kernel + rom

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[G4 Android Development] codeworkx:
I've merged a ton of security patches a few minutes ago.
[G4 Android Development] Yotachambers:
Well I just screwed up and am stuck on the 'preparing to start... Starting apps...' screen on CM. I booted into it just fine after recieving the phone earlier today, but the method I used to boot Twrp was to ignore the failure and run 'fastboot boot twrp.img'. Everything went fine until I used advanced reboot to see if Twrp somehow patched my recovery somehow (it didnt) and I got the dead android triangle. I pulled the battery and rebooted into CM and have been stuck ever since. Button combination isn't working to get back into bootloader mode and I can't establish a connection with ADB. Anyone know anything I could do to get back to bootloader mode??
[G4 Android Development] mattgoldey:
I just tried flashing the same thing you did. Same results you had. Something in that CM nightly ****ed our phones. Hard. I ended up buying a Moto G4. Gonna stay stock for a while, I think. It's pretty vanilla anyway.

---------- Post added at 01:25 PM ---------- Previous post was at 01:23 PM ----------

Welcome to the club. Your phone is likely ****ed. I've wiped completely and repeatedly. I've installed 3 different ROMs. It still gets stuck at "starting apps" on most of them. On the factory ROM, it does at least boot once, but after that it's unusuable. I ended up buying a Moto G4 a couple days ago.
[G4 Android Development] Yotachambers:
Im not sure we're experiencing the same issue. I can't get connected to adb or any other method to get back to twrp, so I can't even try flashing something else or restoring the backup I made. CM booted just fine the first time and ran smoothly with no issues. For some reason after trying to reboot into recovery and failing because twrp isn't installed, I can't get it to boot again. I literally just bought the phone because I wanted something with CM and a zerolemon battery, it's more of an extra phone for me as I'm using the HTC 10 Daily, but it's frustrating to have killed it on the first day of tinkering..
[G4 Android Development] mattgoldey:
You said stuck on the 'preparing to start... Starting apps...' screen which sounds exactly like the issue I and others are having. Once or twice I've been able to boot a ROM of some kind, but once it's up, it's completely unstable and unresponsive. Apps crash or just don't respond. That's where I am now. I flashed the factory ROM, it booted, but it's completely unusuable.
[G4 Android Development] xrad:
You can put the phone into downloader mode and then use LGUP to get back to a sane state:

Pull battery to force turn off -> Put battery back in -> hold volume up -> connect to PC via USB cable
[G4 Android Development] Yotachambers:
Hay! I got it to work. I'm a newbie, I apologize. Everything's working now, just had to do a reset in Stock recovery and it booted. I was under the impression that would wipe system and I wouldn't have any firmware installed but that's my lack of knowledge showing..
[G4 Android Development] knzor:
Awesome news.

Are those related to known exploits (I mean referring to specific CVS?)

Thank you for your work.
[G4 Android Development] benchmade707:
I did the LGUP kdz update last night and finally got it to work, though it acted really screwy until I finished with it's 2 OTA updates. Seemed to have normal function there, decided to try and root, then flash TWRP again through Flashify, then flashed Exodus ROM.

Took forever to boot up, made me pretty nervous, but it does seem to be fine now. What an ordeal.
[G4 Android Development] mis2417:
tested latest nightly (1002) with pico opengapps and xposed with checkpoint and it's all good now.
[G4 Android Development] knzor:
Confirmed.

Thank you [MENTION=3208754]codeworkx[/MENTION]
[G4 Android Development] noidman123:
Could anyone point me in the right direction to getting exfat support on a cm/aosp rom? I tried flashing llama/superxe but this official cm13 still asks me to format my 128 gb card which i'm not willing nor able to do lol
[G4 Android Development] Loulou-13:
Hi !

How is the baterry life on the last build ?

SnapCamera with lastest updates are as well as the stock lg app ? Or aosp rom still have bad quality ? ...
[G4 Android Development] codeworkx:
Should have exfat support by default. No need to flash another kernel.
[G4 Android Development] zenitraM:
Already reported but still not fixed, see my workaround here:

http://xdaforums.com/showpost.php?p=68625029&postcount=4751

It's been working so far since then, though I'm still on a nightly from 3-4 weeks ago.
[G4 Android Development] kessaras:
i saw the same error around the G4 forum again and again. Someone said that its related to the supersu. When you 1st flash rom gapps etc, boot, encrypt, do your staff there what you wanna do and later install supersu last. its not rom related, its in most of the roms for G4
[G4 Android Development] agueijo:
Excelent! with the boot.img the camera autofocus closely works well!

Many thanks!
[G4 Android Development] zenitraM:
This is a different issue, on stock roms encryption doesn't get enabled / does not boot after being enabled if you have rooted before enableing it.

The problem on CM is that the (HW?) keymaster does not properly recognize the screen unlock key once encryption is enabled and the device has booted.
[G4 Android Development] iNaruX:
hello,

does it support quickcharge 2.0? No notification displayed, so I wanted to ask...
[G4 Android Development] baggerbodo:
Hi.

I testet CM14 preview nightly on my G4. Everything works fine (except some CM settings) and no more or less lags than CM13 or stock Android.

It´s my daily driver now, no probs and battery is ok.

I made a little video. Check this out.

https://www.youtube.com/watch?v=aapX5u_XvBk&feature=youtu.be

EDIT: The nightlys can you find HERE
[G4 Android Development] bozlaci93:
How to install? Full wipe? My currently rom cm13
[G4 Android Development] genesixxbf3:
What did i say some page earlier ?
[G4 Android Development] rednax:
CM14 won't connect to my business wifi PEAP.. The connect button stays greyed out..
[G4 Android Development] genesixxbf3:
i said no talk on cm14 here ffs
[G4 Android Development] rednax:
lol, my bad... but fixed now
[G4 Android Development] mbar:
Yes, the LED blinks when QC 2.0 is used.
[G4 Android Development] a tiny ant:
So if I may ask, how close to stable is the latest nightly? I want to know if it's decently stable for use as daily driver.
[G4 Android Development] Loulou-13:
Nobody for an answer ?
[G4 Android Development] genesixxbf3:
use search bar
[G4 Android Development] iNaruX:
So THATS why it was blinking, I thought it had an issue or something like that. Thank you for clearing it up :)
[G4 Android Development] t.kijas:
Battery life is probably same or slightly better in basic usage, it depends how much apps u have and how many of them wakes up frequently. +1

Baterry consumption when playing games etc. is higher than with stock and phone is warmer. -1

Snap camera is ok but without DNG (RAW) support (doh!).

Other cameras with API2 (and raw) have huge problems with CM13 in lg g4, they do not run/they run but black screen appear/they run but freezes oftenly. All of them work smooth on stock. :(
[G4 Android Development] Astur_Torque:
Is 5/10/2016 stable?
[G4 Android Development] mymeatb18:
2/10 is stable for me
[G4 Android Development] brossovitch:
04102016 is quite stable for me on h811.

It's so far doing better than ever with little bugs.

Battery life is very good, with auto sync off I'm seeing consistently 4-4.5hrs average SOT.

Around 3hrs SOT while using Google Fit or Pokemon Go (in high accuracy GPS). Device only GPS works wonderfully even for navigation.

And to this day, this is the Only ROM that has working video recording after taking the H81120o firmware update.

Thanks for this amazing ROM!

Eagerly awaiting CM14!????
[G4 Android Development] Astur_Torque:
Thanks so much

What about camera?

I think it's not as good as stock, but is it very noticeable?
[G4 Android Development] CraigHardy:
It's never going to be like stock camera so either learn to deal with it or stay/ go back to stock, simple
[G4 Android Development] kessaras:
use jishnu's camera mods. personally i use htc 10 camera and its working great. i can't give link cause of rules, but search in google and find him in google+
[G4 Android Development] thewild:
It's excellent.

Why don't you just give it a try. It's as simple as doing an nandroid backup before installing CM and restoring it if you don't like it.
[G4 Android Development] macart:
hmm... mine says quick charging, but the led is not blinking... what does that mean? I use original charger that came with my phone.
[G4 Android Development] mbar:
Original LG's charger is not QC 2.0 enabled.

I use QC 2.0 charger from Samsung.
[G4 Android Development] Astur_Torque:
I Tried it few months ago, but the camera was very unstable, sometimes it never shot or app crashed.. I will try it again
[G4 Android Development] macart:
what the hell? why would they not put one in? it costs insignificantly more...

why does it say "charging rapidly" then? my old note 2 on CM said "charging slowly"... I was wondering if the LG charger was QC or not but when I noticed the different message I assumed it was...
[G4 Android Development] mbar:
LG's charger is QC 1.0, but not QC 2.0.
[G4 Android Development] macart:
thanks for clarifying it, I actually attempted to look that up, it nowhere says anything about if it is QC or not, not on charger, not on instruction, not on LG product information page. there is no QC logo on it, and you can not take it apart without braking it too.
[G4 Android Development] xrad:
Please clearify. Any camera app using API2 works just fine for me (h815).
[G4 Android Development] mymeatb18:
The only issue I find is after a few reboots cell signal stops turning on.

Anyone else having this issue? H811

Edit: just turned off the phone completely then turned back on and had no issue.
[G4 Android Development] a tiny ant:
What exactly is the reason stock rom needs to be installed before flashing CM? Is it the bootloader part that needs to be there? I thought CM was mostly AOSP.

Would it also work from the Imperium rom for example since it's stock based?
[G4 Android Development] Loulou-13:
Thank to all for battery and camera feedbacks...it's nice :good: ;)
[G4 Android Development] codeworkx:
bootloader, modem, firmware...
[G4 Android Development] Koile:
to the developers:

Out of curiosity I updated my h815 (we really should have separate threads for the two devices when CM14 is out ;)) to latest nightly. As I expected: Camera did not work ootb (but torch is shown in quick-settings). But with the modded boot.img posted a few pages before, the latest nightly works just fine (except for missing torch in quick-settings). So the problem with the laser-af seems to be a problem in the boot.img.

Thought it could be a matter of interest for you.
[G4 Android Development] xrad:
There is no thread for cm14 because it just doesn't exist officially. Whatever builds you find out there - they're known to be buggy. Use them if you must, but don't spam the forum with pointless bug reports. I know you're well meaning but this doesn't help at all.
[G4 Android Development] Koile:
oh no, big misunderstanding! I was talking about the latest CM 13-Nightly! So with latest CM 13-Nightly and boot.img laser-af is working, but no torch is shown in quick-settings (tbh: I prefer being able taking photos over having a tiny flashlight).

What I meant, was that when CM 14 finally comes out, there should be separate threads for h815 & h811!
[G4 Android Development] CraigHardy:
Seperate threads will be given when the dev(s) think it's at a point for public use
[G4 Android Development] Koile:
yeah... I know... what I meant was not, that I demand a separate CM14-thread by now. I know, that it is still work in progress and not yet to be released.

I just thought out loud, that it would be a good idea, that when CM 14 for the LG G4 is officially announced and gets an own thread, it would be a good idea, if there were two separate threads for CM 14 itself: CM 14 for H811 and CM 14 for H815.

I realize quite often that in this thread people with different devices (H811 vs. H815) don't realize, that they got different devices and different CM-versions (e.g. when talking about bugs regarding only one model-type).
[G4 Android Development] CrunchMilk:
Side note to the need to install the stock rom before flashing cm. I did try out the unoffical cm14 builds from genesix. I did a full wipe before installing (including system).

When I reverted back to cm13 I also did a full wipe. I don't really know why it suddenly works, but it does.
[G4 Android Development] yasiro500:
Yes I have this issue as well on my h811 running the 10-05 build

---------- Post added at 01:34 PM ---------- Previous post was at 01:31 PM ----------

There's something wrong with AudioFX. For the past 2 days, even when its on, I don't hear any difference, it basically works when it wants to. Not fixed even when I update. Any suggestions, I cant deal with no audofx, because I'm all bout that bass ?
[G4 Android Development] t.kijas:
Hi, ProShot crashes frequently, very frequently on slower shutter speeds, like 5secs and more.

Open Camera freezes on slower shutter speeds

FV-5 Camera shows only black screen

Manual Camera crashes with black screen

A-Z Camera do not save pictures frequently.

All of them are able to produce DNG (RAW).
[G4 Android Development] xrad:
I doubt this is all the fault of this ROM. The may certainly be some issues with certain combinations of settings, but I'm willing to bet that an instantaneous black screen is an issue in the app. In the case of Manual Camera it wouldn't even surprise me (so save stronger words.)

You can try Snap HDR and Footej, both work fine for me. Snap HDR has a very active dev, but the apps complexity seems to bring some stability issues. Not CMs fault though.
[G4 Android Development] t.kijas:
Yeah, well almost all of them worked on stock so... There is something wrong on way app->cm->camera.

Footej is nice but slow and max shutter time is one sec. That's not an option.

Snap camera HDR - Black screen after start.
[G4 Android Development] the-erazer:
They also work on actual aosp based roms like Exodus.

Gesendet von meinem LG-H815 mit Tapatalk
[G4 Android Development] xrad:
Er. No. Xposed? Custom kernel?
[G4 Android Development] epv:
I flashed the oct 6 daily over the may 16 daily i'd been running since may, which was working fine.

During boot, logcat spews:

10-06 12:51:09.342 461 578 E AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
10-06 12:51:09.342 461 578 V AudioDaemon: bool android::AudioDaemon::getStateFDs(std::__1::vector<std::__1::pair<int, int> >&): 0 sound cards detected
10-06 12:51:09.343 461 578 E AudioDaemon: Sleeping for 100 ms
10-06 12:51:09.443 461 578 D AudioDaemon: Opening sound card state : /proc/asound/card---/state
10-06 12:51:09.443 461 578 E AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
10-06 12:51:09.443 461 578 V AudioDaemon: bool android::AudioDaemon::getStateFDs(std::__1::vector<std::__1::pair<int, int> >&): 0 sound cards detected
10-06 12:51:09.443 461 578 E AudioDaemon: Sleeping for 100 ms
10-06 12:51:09.543 461 578 D AudioDaemon: Opening sound card state : /proc/asound/card---/state
10-06 12:51:09.543 461 578 E AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
10-06 12:51:09.543 461 578 V AudioDaemon: bool android::AudioDaemon::getStateFDs(std::__1::vector<std::__1::pair<int, int> >&): 0 sound cards detected
10-06 12:51:09.544 461 578 E AudioDaemon: Sleeping for 100 ms
10-06 12:51:09.644 461 578 D AudioDaemon: Opening sound card state : /proc/asound/card---/state
10-06 12:51:09.644 461 578 E AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
10-06 12:51:09.644 461 578 V AudioDaemon: bool android::AudioDaemon::getStateFDs(std::__1::vector<std::__1::pair<int, int> >&): 0 sound cards detected
10-06 12:51:09.644 461 578 E AudioDaemon: Sleeping for 100 ms

Then I reflashed back to the twrp backup made immediately before this, and it now does the same thing on boot. Then I reflashed 100% stock 20i from http://xdaforums.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227 and it still does that on boot. Then did factory reset and flashed the oct 6 daily again, still the same thing is happening. Phone app and anything else sound related do not work.

Any ideas? Is there a table of what boot image / modem /etc goes with which system?

There are in fact no probed soundcards in /proc/asound - so i'm guessing i have a wrong or missing kernel module installed or the wrong kernel entirely (Linux localhost 3.10.84-g0097f69 #1 SMP PREEMPT Wed Oct 5 22:58:36 PDT 2016 aarch64)
[G4 Android Development] t.kijas:
Er. No Xposed, no custom kernel. :)

---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------

BEWARE guys, do not attempt to install SuperSU, I just did it on my CM13 (latest nightly with latest TWRP) and for few hours I totally bricked my device, without possibility to enter recovery mode, download mode/fastboot mode without ability to be seen by fastboot. Dead. EDIT: LG G4 is full of surprises... recovery mode worked when phone was connected by USB to computer. The world is CRAZY.

I would not risk SuperSU again.
[G4 Android Development] yasiro500:
Can someone help me out I have this reallyyyy annoying issue and its pissing me off. Ever since flashing this ROM, I've been getting WiFi dropped, tried updating and its still there. H811, was running 9/24 and updated to 10/05 and the problem is still there, in fact, it's getting worse and worse. Please help me someone
[G4 Android Development] xrad:
Yeah, I never get why people bother with SuperSU in the first place. Probably it's just too popular while CM's perfectly capable built-in root is just too little known.
[G4 Android Development] t.kijas:
Yup, it's because it's popular and I used it years ago ony ma samsung devices :) And some apps informs (like titanium) that built-in root may not be enough.

OK, I purged system to install camera apps again and report.... so.... no, it is the same. Front camera works, though.
[G4 Android Development] oxidax:
Nope. I took your approach and got myself a S7 edge. My G4 bricked after that CM 13 update and even reverting to stock didn't make it work again.
[G4 Android Development] epv:
I have a Tmobile H811 which I've completely wiped and reinstalled stock 20i from kdz using LGUP.

It can't detect any sound devices, and /proc/asound/cards is empty. Camera also doesn't work.

Is there anywhere else state is preserved that could cause this? As I understand it, the kdz install should have overwritten bootloader, modem, system, and everything. What else is there?

Something happened when I updated to the 10/6 nightly.
[G4 Android Development] theslam08:
H811 'Starting Apps' & No Sound issue

It should be posted somewhere for us H811 users:

20o is REQUIRED now for fully working non-stock roms.

I had the exact same issue as everyone else. Was on 20i FW running stock for months at a time with everything working fine, then decided to 'try' a new build of CM14. Ran pretty good, but few little bugs + had no sound and no camera had me going back to a 6.0 ROM. Decided to try the latest CM13 & RR, but got stuck on the 'Starting Apps' for both...

Decided to just go back to a stock 20i ROM and what do you know, camera crashing instantly on welcome screen & no sound. I started to bug out so I went reading and it seems others were having similar issues and could be related to us H811 users still being on 20i and some having success upgrading to 20o from 20i.

I did the update myself and all ROMs (CM13, RR, DU, Stock) work with camera/sound now. I'm guessing the newly incorporated code to get the camera working was FOR the 20o firmware so not having that caused sound/cam to break...the very very odd part is that the 20i stock ROMs got affected too after flashing these ROMs with 20o code...weird

That is exactly what I did (H811 ONLY - research more if needed):

-Flashed xTreme 3.3 (flashed nothing else)

-Loaded up LG Bridge, found phone + 20o update no problem

-Let it update using LG Bridge

-Once done, it boots up into non-rooted updated xTreme

-Have to fastboot boot recovery

-Flash recovery

-Enjoy all ROMs working as they should now :)
[G4 Android Development] epv:
Oh **** man, you have saved me so much frustration. Thank you! I either really suck at googling stuff or it's very hard to figure that out from reading the threads. I'm going to put a note on my other thread about it as well.

And yeah, I just used LGUP to install 20o and it's all fine now.