yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] kilapanga:
Well I have to try it again...[emoji38]

LG D802 CM13
[G2 Original Android Development] cb951303:
I have used LG Flash Tool 2014 to install D802 30d stock firmware. It booted successfully. Then I've installed kingroot to root the device and then I've used autorec to install TWRP 2.7.0.0. Then I used TWRP to install TWRP 3.0.0.4. Rebooted to the new recovery. Everything went smoothly. Afterwards I did a factory reset and installed the CM13 latest nightly zip. To my surprise it only took like 40 seconds but didn't give any errors. I rebooted and now it gets stuck after the LG logo. Just black screen. Any ideas what am I doing wrong?

Thanks

Edit: Install log attached. And it's more like 20 seconds not 40 seconds.
[G2 Original Android Development] mal13:
Look and try: Bootstack d802-caf
[G2 Original Android Development] TheHaso:
Use TWRP v2.8.7.3 and be sure to use right GApps. Custom bootstacks is NOT recommended.
[G2 Original Android Development] cb951303:
I don't use GApps.

I have the stock 5.0.2 bootstack.

Just tried TWRP 2.8.7.3 and the result was the same. Any other ideas except a custom bootstack :D ?

EDIT: Tried CM 12.1 and that one works ok.
[G2 Original Android Development] TheHaso:
If CM12.1 works, this shows that you bootstacks are already modified.

So, KDZ to LP, root, TWRP, and directly flash CM13.
[G2 Original Android Development] murok9042:
Update to the newest TWRP version!

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Original Android Development] machinehead121:
Works fine mate, I just did a conference call the other day. Try again

?
[G2 Original Android Development] dr4stic:
If I had to guess, I would say that kingroot does something odd and changes the bootloader. I tried researching it but can't find exactly what it does.

When I root my d800, I use the LG Lollipop One Click Root. The tool is a bit of a pain to use sometimes, but it gets the job done for me. In theory the rooting utility should just stick an SU binary on the system. Then it's up to you to install the SuperSU app.

I'm assuming you install the autorec app from the play store: https://play.google.com/store/apps/details?id=b007.autorec2 ... This is what you want to install the recovery.

Using those two I've never had an issue. If you start from the latest lollipop for your device, you should not at all need any bootstacks. Please don't use bootstacks.
[G2 Original Android Development] Boopie11:
I have microstutters while begining to scroll in some apps

Whst settings to use in stock kernel?

Enviado desde mi LG-D802 mediante Tapatalk
[G2 Original Android Development] cb951303:
I'm also against hybrid bootstack.

You might be right though. I don't know how kingroot works. When I KDZed to LP 30d, no other root tool worked. I tried One Click and ioroot. Only kingroot was successfull.

I've just also noticed that my device is identified as d802tr not d802. Maybe it has a different bootstack? Anyway, I'm now on 12.1 happily. I think I will wait a little more for 13 (until the wi-fi issue is solved)

PS: I've also used another autorec (the one mentinoned on cyanogen wiki) because the one on your link didn't see my device as d802. Now that I think about it, it's probably because my device is a d802tr :D. Hardware wise they are the same but those apps probably check some strings and don't know about d802tr.

Thanks

---------- Post added at 07:33 AM ---------- Previous post was at 07:29 AM ----------

That's first thing I tried.
[G2 Original Android Development] dongerado:
Hello!

For those who have problems with whatsapp voice message (low quality Mic) try to chance following (to false) in build.prop:

ro.qc.sdk.audio.fluencetype=false

This worked great for me!
[G2 Original Android Development] khaytsus:
Well, no, it is not. It was an Android behavior change in AOSP which does more connectivity testing and invalidates a wifi connection if the testing fails. The testing is apparently too strict or such.. And should be able to disable it.

It's not a CM issue, although I'm surprised CM hasn't fixed it. Google seems to be sitting on it.
[G2 Original Android Development] dnsp:
Time to say goodbye to CyanogenMod. This wifi bug is just unacceptable and the devs seem to just don't care. Back to stock based roms, slower but at least I can receive my notifications all the time, anywhere.
[G2 Original Android Development] GalaxyGusta:
Anybody else have this issue that you can't peek at notifications in the lockscreen? You can only swipe to unlock
[G2 Original Android Development] sachilleas:
I have mentioned it some posts earlier. I don't know what happened. It was all good before.

I can't even change songs in Spotify. I also can't use toggles from notification panel.
[G2 Original Android Development] Tech_Savvy:
[MENTION=2096805]dr4stic[/MENTION] i don't want to bother you...i read op but cudn't quite figure out which bootstack to use for for d800 ? shjould i use kitkat or lollipop? thanks
[G2 Original Android Development] dr4stic:
No, he's right... I've had many in-call mishaps. Sometimes they happen, sometimes they don't. I wish I could get the devs to care. Call switching is a crap shoot for me. Call holding too. The most recent set of logs I sent in were because dialing 3 digit numbers (611, for example) is consistently buggy for me, and so I could produce consistent logs for it.
[G2 Original Android Development] dr4stic:
If you've gone back to the regular d802 and that works for you, and you downloaded the last nightly for 12.1 from CM's download servers, you should consider running a newer one. If you look at the CM-12.1 thread (the one Shelnutt started), towards the end I posted a recent build of official CM-12.1.

http://xdaforums.com/showpost.php?p=66071230&postcount=1458

The build is basically official CM-12.1, but I ran it a few weeks ago, so it has the March android security patches. It's certainly newer than the mid-november build and some people in the thread indicated that it even corrected a few bugs they had with the last official nightly. It was also modified to have a special build of CM-13's current (as of that build) version of Snap. Make sure your Gapps isn't replacing it if you decide to use my build.

As for the cm-13.0 release for you.... there may actually be some checks happening on the hardware itself that are keeping the build from coming up on d802tr. The devs did tighten checks with cm-13.0. I'm sorry about that.
[G2 Original Android Development] dr4stic:
You are bothering me, mostly because you didn't read the OP, or more importantly the FAQ. Try again (hint, if you read the FAQ, you'll know the answer).
[G2 Original Android Development] ulihh:
To me it seems that last patches to the wifi environment with the 20160406 nightly have made a step in the right direction. My wifi seems more stable today, I didn't have a single drop related to rekeying so far (since flashing this morning). Have to wait and check it tomorrow morning though.

Regards, Uli
[G2 Original Android Development] dr4stic:
I wonder if that's related to these changes from last night's build:

eap-sim: Unbreak the standard non-proxied flow for multi-challenge requests

eap: Don't force reassociation when getting the identity and handshakes are in progress

If it is, I would encourage people to test at least the 20160406 nightly for a few days and report back on their wifi issues. It'd be nice to cross this one off a list. Thanks.
[G2 Original Android Development] Tech_Savvy:
Darn i missed it... I thought i read ur faq... Mustve. Missed it bc i did read it... Sorry...:) oh well thanks anyways, got what i came for;) thanks for ur work:)
[G2 Original Android Development] JMailuhu:
For some reason i don't experience the wifibug anymore... I've been paying attention today, and while my screen were off, i have received whatsapp and email.. My wifi was running constantly for at least 8h, and i haven't missed any connectivity related stuff like messaging, gapps updates or whatever. I used to have a drop the first couple of times after a fresh install, but i've been running this (snapshot) for a few weeks now and i haven't got any drop ever since... I wonder why? Maybe i needs time to settle down, i don't know..
[G2 Original Android Development] ulihh:
So far no drops :D it's definitely much better than before. I had one drop today with

NetlinkSocketObserver: NeighborEvent{elapsedMs=39125485, 172.16.1.1, [3431C441393E], RTM_DELNEIGH, NUD_NOARP}

when I switched off my workaround wifi router, so this drop was intentionally. Now I count 20 rekeyings in my home wifi without a rekeying drop and that's rather unusual. Looks promising! :good:
[G2 Original Android Development] Kael710:
The PWM frequency of LED charging notification is somewhat set low and when you wave with the phone in the dark, you can actualy see red and green stripes of light... Not a bug really, more like a feature :D
[G2 Original Android Development] jeebspawnshop:
If this is indeed a fix for the wifi rekeying issue, this might be the greatest moment of 2016 for me thus far...!
[G2 Original Android Development] chewdaniel:
wifi seems good so far....... but now a new and annoying lockscreen bug lol
[G2 Original Android Development] dr4stic:
I swear... it's like as soon as the WiFi bug seems like it might be fixed, people find a WHOLE NEW BUG to complain about ;)
[G2 Original Android Development] chrismin13:
Hey there. I've got an idea.

Would it be possible to fix the Slowly Charging bug by modifying the Language Pack? I don't see it solved any other way any time soon so let's just change how it's displayed both for fast and slow charging to just "Charging.".

---------- Post added at 06:48 AM ---------- Previous post was at 06:27 AM ----------

Sorry for replying to such an old post but the solution would be to set GPU to 320mhz instead of 200 for the lowest. This has been mentioned before. Search next time around.
[G2 Original Android Development] TnK8iD:
Sad for you, but i never noticed a wifi's bug on my device using the builds from the last month.

Enjoy your lollipop notification in the right time ;)

---------- Post added at 08:33 AM ---------- Previous post was at 08:28 AM ----------

let's imagine a new bug together :D
[G2 Original Android Development] ulihh:
It's not completely solved because I had one NUD_FAILED at 5:30am in the logcat last night, but it looks much better than before.

Regards, Uli
[G2 Original Android Development] cb951303:
Hey thanks for the newer 12.1. I'll flash it as soon as possible. Do I need to do a factory reset or can I just install it and keep my things?

For 13.0 where can I bring it up? A bug tracker maybe? Maybe it's as simple as just adding a "d802tr" somewhere...
[G2 Original Android Development] szabyka95:
could i get any performance drop/any disadvantage if i have hybrid bootstack ?? currently my phone is running cm 13 + hybrid bootstack
[G2 Original Android Development] dr4stic:
Sure thing... I remember being bothered that we got CM-13.0 at a time when 12.1 was really getting stable, knowing that it would absolutely kill our 12.1 nightlies... and then with 13.0 not being as stable as 12.1. Anyway, for my family I don't load up 13.0 on the G2's they have and I had been wanting to run a recent build of 12.1 since forever :)

You should just be able to install it over an existing installation without any problem. However if you only recently set up 12.1 on your phone and you don't mind, I'd suggest doing a full wipe of your phone (including wiping system partition) and doing a fresh install with my build.

I'll have to do a little research and bug a dev. We may have to do a bit of inspection on your phone to grab some version numbers. There are strings embedded in your firmware with fairly extensive version numbers on it. However I'm not sure how that works because it should only stop the installation, not fail to boot. My knowledge of the version number usage is that it's used during the installation phase to stop installation on incompatible firmwares.

This may actually be far worse and more involved than just figuring out some version strings, and it may be that we aren't able to add support for your device... and you should be prepared to expect that. Also, you'd need to be able to test repeated installation attempts, and it may be that you won't care to do that. If we go down this road, it may be a significant amount of work, and that's just assuming I can grab a dev's attention.
[G2 Original Android Development] mrsoftball77:
Hi there,

I have an issue with my bluetooth. Listening to music works perfectly fine. But everytime I coonect the phone to my car bluetooth and try to place a call the phone immediately hangs and restarts after a while by itself. Placing a call after the restart works just fine, a 2nd call afterwards again doesn't.

I am on 20160406 nightly but had this problem since I first put CM13 on my phone (around 20160328 nightly).

Has anyone else experienced this behaviour?

Gesendet von meinem TF300T mit Tapatalk
[G2 Original Android Development] carlosbmc:
Hello

I have installed some nightly versions. All it's ok... But never working automatic brightness.

Somebody could tell me if it is working correctly?

Thankyou.

Enviado desde mi LG-D802 mediante Tapatalk
[G2 Original Android Development] dnsp:
Your D802 must be a special edition because we all are having wifi disconnecting in deep sleep and when changing access points or wifi networks.
[G2 Original Android Development] PhantomBeam:
I'm on CM13 20160317 SNAPSHOT, and i've never experienced issues with the wifi dropping. I'd say this rom is perfect (for me anyway :) )
[G2 Original Android Development] RinCEWinG:
I am in the same snapshot and I can say that this rom is very fast and smooth room! It is amazing how multitask works!

Anyway, it has little bugs for me:

- Whatsap voice record - There is a fix mod

- Multimedia Speaker Volume too low for me - I know that there is a mod, but I installed it and random reboots happens.

- Weak telephone signal (I think that I have a bad bootstack or baseband...or something like that, cause I had been flashing loads of roms before CM 13...)
[G2 Original Android Development] andreas_h92:
hello guys,

i installed cm12.1 SNAPSHOTa couple of months ago but i returned to stock because i had issues with noise-cancellation.

When i was recording videos there was a lot of noise, but in stock roms it was clear.

Does this bug exits in cm13 snapshot as well?? Please report, i don't wanna install it and uninstall it..

thanks in advance!
[G2 Original Android Development] cb951303:
I'm now successfully on your build. Thanks again.

For 13.0, I'm willing to test things out. I have my full TWRP backup so it's not such a hassle to switch between roms. I've also taken a look to the github codes. If a developer can point me to right direction I can even change/build/try myself. Right now I have no idea where to look for those string/version checks.

One thing I'm sure of though is the hardware is identical otherwise 12.1 for d802 wouldn't work as well. So I'm hopeful 13 will work if we can eliminate the verison check (ofcourse it might be some other unrelated issue but I'm betting on this one :D)
[G2 Original Android Development] johnb380:
Should be editable in the updater script right?
[G2 Original Android Development] rafa10pj:
If I flash the d802 version on my d805 coming from stock Lollipop (KDZ) will I need to flash a d805 baseband? I can't seem to find the answer in the thread.
[G2 Original Android Development] dan3840:
Here the wifi does not disconnect just to turn off the screen but all the time, impossible to use, not to play vaingrlory because of dc and this occurs not only in my router but in any router then it sure has some bug related to wi-fi
[G2 Original Android Development] PhantomBeam:
There is no noise cancellation when you record in CM13.
[G2 Original Android Development] errikosd:
Does anyone have any idea where in the CM source are the network operator names set? It's very annoying to have the whole company name displayed. It occupies 3 rows in the data toggle tile. I get "Cosmote - Mobile Telecommunications S.A." instead of "GR COSMOTE". Stock ROMS display the latter.

I know it's a RIL related thing, as my current workaround is editing libril-qc-qmi1.so with a hex editor and replace the aforementioned string.
[G2 Original Android Development] andreas_h92:
is this normal?
[G2 Original Android Development] esaslead:
CM13 Stuck on Boot Logo

Hello everyone,

Before posting here, I've gone through a lot of searching/reading for a possible solution but none helped, so I'm asking for a solution to my specific problem. Please read carefully as this is most probably not a duplicate question.

I've tried almost every tutorial on installing CM13 on my G2 d802, including the recommended steps mentioned in this thread's FAQ. Tried with / without bootstacks, on stock KK or LP, different versions of TWRP, CM 12.1, CM 13, with / without different GApps packages, everything.

I've even bricked it so hard one time with no accessible interfaces whatsoever (including the low-level HS-USB interface) which i turned it back to life by shorting some capacitors on the motherboard!

The process goes fine with no errors until I boot into CM 13 for the first time. It always stucks on the CM boot logo.

I've started to think that my device has a specific problem/fault. But I'm not giving up yet.

Here are my answers to some common questions you might initially ask:

Can you boot into recovery mode? Yes

Can you boot into DL mode? Yes

Can you connect via 'adb' while on boot logo? No

Can you connect via serial port while on boot logo? No

What version of CM are you trying to flash? Tried official CM13 Snapshot, a few CM13 Nightlies and CM12.1 Snapshot so far.

Have you tried any other unofficial CM/other ROMs? No, only those mentioned above.

What is your device vendor? Online IMEI check shows TAIWAN-D802. I've tried the stock ROM for this too.

Have you tried installing WITHOUT a GApps package? Yes

Have you tried flashing <bootstack_name_here> bootstack? Yes, I did

Have you tried the process WITHOUT flashing a bootstack? Yes

Did you wipe cache, dalvik, system partitions? Yes

Did you do a KDZ flash to begin with? Yes, I've tried many different stock ROMS including KK and LP ones. Most recently: europe open D80230D

Have you updated TWRP? Yes, I've tried many versions

Have you tried any other custom recoveries? Also CM recovery, but no luck.

How did you flash initial TWRP? d802 AutoRec for LP (from Play Store) along with a few other methods.

Have you tried to remove/rename /system/media/bootanimation.zip file? Yes

So, I've tried many possible combinations so far. Now I am looking for a way to debug the boot process.

I know about 'dmesg' and '/proc/kmsg' logs but since I can't connect to the device on boot state, I can't read those messages.

When I boot into recovery, these logs are overwritten.

My questions are;

Is there some way that I can persist those 'dmesg' messages to some file in the boot process?

Is there a way to enable 'adb' early in the boot sequence?

Maybe some other way I can figure out what's going on?

I have MTP, adb and serial connections in recovery mode.

Thanks
[G2 Original Android Development] sioncan:
I have an issue, firstly you say that :"The required bootloader (aboot) for CM13 on the LG G2 is the KitKat (KK) bootloader. CM13 will fail to install otherwise."

But then you say that the best way to flash this rom is to start from LP Stock.

I have a LP Stock based rom, and i can't figure out if i have to install the kk bootloader or i'm fine :/

Thanks!
[G2 Original Android Development] ulihh:
The wifi patches in 20160406-nightly have changed my wifi drops in the following ways:

At home the drops happen less often, but still directly after a rekeying. In the logcat NetlinkSocketObserver says RTM_NEWNEIGH, NUD_FAILED, and wpa_supplicant says reason=3 locally_generated=1

At work the drops happen as often as before, but they are NOT related to rekeying anymore. In the logcat NetlinkSocketObserver says RTM_DELNEIGH, NUD_NOARP, and wpa_supplicant says reason=0

It looks like we (i.e. android) have 2 different errors.

Regards, Uli
[G2 Original Android Development] TnK8iD:
yes I'm the lucky one :D
[G2 Original Android Development] Owoc21:
If you have LP stock, you don't need to install KK bootloader. Root-->flash TWRP (ex. play store installer)-->full wipe (if you have bootstack, rom and gaaps on your flash drive)-->flash hybrid bootstack-->flash CM13-->flash gaaps-->reboot
[G2 Original Android Development] MB525:
In fact on my D802 i could do without flashing _any_ stack at all after coming from stock LP.

Flashing stacks always led to loss of hardware button combinations into recovery.
[G2 Original Android Development] timanels:
Lock Screen Notifications

I am using 20160408 nightly and using PIN lock for security. When I press a notification twice and the PIN entry comes up, the shortcuts are still there and interfere with the code entry.

I had a problem immediately after 20160402 with the PIN entry being overlapped by the lockscreen shortcuts (left and right corner) for all situations and now (20160408) it has improved but still remains this specific issue.

Is this also true for anyone else?

Thank you.
[G2 Original Android Development] dr4stic:
When you use autorec on a stock LP rooted firmware, it installs a hacked KK bootloader. Essentially the LP bootstack uses a modified KK bootloader. The KK bootstack uses a JB loki-compatible bootloader. There is no workaround for the LP bootloader itself.
[G2 Original Android Development] airon11:
I have the same exact problem with pattern unlock...i did not had this with 28 March release...i updated today to 8th April build and it is usable but definitely a bug..
[G2 Original Android Development] aaronDroid80:
This is a bug that is related to the new live lock screen stuff. It looks like the devs are aware that it's not perfect yet and are working on it. It is a bit frustrating to have to unlock your phone for things you shouldn't have to...

...but it's not the end of the world. It'll be fixed soon enough.

Sent from my gooey, toasty LG-D800
[G2 Original Android Development] dr4stic:
Alright, it's been a few days and I'd like a report. The WiFi bug. I've heard almost no complaints since the 20160406 nightly. I'll chalk up the single complaint I really saw (with no reported nightly date) to some other bug.

Is the WiFi (disconnect during sleep) issue squashed now?

Please report, thanks.
[G2 Original Android Development] ulihh:
Sadly not, for details see my post #2703
[G2 Original Android Development] belgianrebel:
Its better but not totally gone
[G2 Original Android Development] edi194:
I'm just wondering, that camera can't be done like in this OPO rom? OPO uses Sony Exmor lens (but other version) and both of them have 13mpx cam. I'm not dev, just asking :E
[G2 Original Android Development] machinehead121:
With that being said my D802 must be a special one too as I never had any WiFi drop issue till now not even in doze, and I'm still on snapshot ??

---------- Post added at 04:16 PM ---------- Previous post was at 04:12 PM ----------

As far as my D802 is concerned I never had WiFi drop issue and also about that call switching/holding bug, I didnt experience that either and I make regular conference calls so I'm saying from my own usage.

I'm keeping myself to snapshot and it has been a very stable enough build for my D802.

Thanks & regards.