yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] MrSqueaky4000:
How would i go about installing these patches to the ROM . Do i need to use linux to install it into the ROM before flashing or is there a way to flash it to the ROM directly ? sorry im a real noob when it comes to this. :)
[G2 Original Android Development] niubboxp:
i'm using it on cm 12.1, downloaded here

snapdragon camera
[G2 Original Android Development] OT-Xtreme:
can anyone test SlimPort functionality for me please, and also miracast/mirroring/dlna/upnp/ various wifi casting. tnx
[G2 Original Android Development] holoyolo01:
There is a way to keep the mixer_path file settings after flashing the updates? I need to make changes every time...
[G2 Original Android Development] zexcrazy:
Hi guys. I have noticed strange readings i battery stats. It says that wifi is on and that it consumes most of the battery juice. Which is imposible because it is off. It was on for about an hour. After that i've turned it off, but it keeps showing in battery usage like it is on. Plus i get almost 5 hours screen on time. So is it just bad reading or what? Does anyone else has a same issue?

Otherwise, great rom. Keep up the good work.
[G2 Original Android Development] mrvlhs:
Similar issue, although with Wifi on. I've been reading about it, some people say it's just a reading mistake bug but it doesn't affect the battery, I've been monitoring the battery with GSM monitor and it doesn't show drain from Wifi even though I think it's been draining a bit while standing by, more than it should. I've also tried some fixes like reseting the network settings and turning on/off location but the issue seems to come back.
[G2 Original Android Development] zexcrazy:
I'll see if it repeats after restart. Just testing screen on time. And i'm wery pleased :)
[G2 Original Android Development] razielarcanum:
Just a knee-jerk thought on the black screen issue: JDI? It's been a good couple of years since I last flashed a ROM onto my d802 (32GB from Hong Kong) and I've had black lines down the screen ever since (I was aware of the issue in advance but unfortunately the post that warned about it didn't provide a link to whatever alternative was that was safe for JDI screens, so I rocked on anyway because I think I'm invincible). The lines started appearing after "washing" effects spread over the LG logo on boot failures (the same time these black screens occur -- the black screen is definitely backlit).

I've just been going through your process for CM13 (from an ancient custom 4.x ROM) and the bumped lg-devs version gave me the black screen. I'd've tried the loki one but wanted to minimise the number of times I did it so tried Daniel Stuart's and it worked first time.

I know little to nothing about how this stuff works anymore (and I barely scratched the surface back in the Desire days) but I'm aware that I'm part of a subset of people that experienced a weird issue due to a seemingly irrelevant hardware difference.

The experience has also reminded me that much as I love the often-mocked button configuration on the G2 (and still get a kick out of people freaking out when they're on my phone and the screen times out), it's definitely not suited to recovery-reboot button combination presses. :)

Thanks for the detailed instructions and your participation anyway; looking forward to playing with it now.
[G2 Original Android Development] coco43:
Hello,

Great rom, I love it. Very fast and works nicely.

The only problem I have is that in MX player I had to choose Hardware+ mode to seek videos, so now it's cool. But in a application I use (D8, french tv channel), I can't seek streamed video, because then I have no sound and video is jerky.

I flashed mixerpaths.zip but it didn't fix the problem.

Any idea, or we just have to wait?

PS : in YouTube app there's no problem, but in my ISP streaming videos app I have the same problem.

Thanks.
[G2 Original Android Development] dr4stic:
The funny thing about your suggestion... I was thinking along the same lines just earlier today :)

I was gonna put up a poll but I want to make sure I have a reliable way to find out what pannel is installed. There's a simple app, but I'm not sure if it works reliably just yet so I'm waiting.

These phones were manufactured with one of two panels: the LGD panel (very common) and the JDI panel (not common). Most roms and recoveries default to one or the other, usually the LGD one because it's more common. The rom or recovery zip files would detect the panel type during flashing and alter the boot line accordingly. The KK bootloader solved this issue by moving the panel initialization into the bootloader, so from CM-12.1 onwards, the lg developers removed the panel setting code from the zip files.

I wonder if what's happening is that the process for installing the updated bootstacks and recoveries and what not is causing something to forget how to deal with the panel on the JDI devices. It might not necessarily be that daniel stuart's bootstack is better, it might just be the order in which things get installed that makes it appear that way...

I'm still thinking this through and trying to find a reliable way to determine the panel type. Also, getting enough people to pay attention here and actually report back meaningful information is akin to herding cats.

If anyone who had issues with the bootstacks is paying attention to this, could you please install this tool, run it, and report back which panel you have (and be descriptive, sometimes these 1 word responses leave me wondering what people are talking about). Thanks!
[G2 Original Android Development] wackou:
I install the application and its displaying : lgd/lgit
[G2 Original Android Development] dr4stic:
And you had issues after installing the lg-devs bootstacks with the screen going black?
[G2 Original Android Development] wackou:
Correct.

With bootstack-d802-LP_30d-Bump-signed and CM12.1, I can boot.

But with CM13, I got black screen, need to install hybrid bootstacks
[G2 Original Android Development] dr4stic:
Well, there goes that theory... that's the same panel I have. Thanks :)
[G2 Original Android Development] Vishal7790:
How to install custome rom into micromax a068,

i allready try flash rom bt isn't suceess.

what is the simple method to do this?
[G2 Original Android Development] AsM0DeUz:
Since the beginning of cm13 on lg g2 my device reboots from time to time during the day but every morning when I wake up the device has rebooted.

Does your device also reboot every days?
[G2 Original Android Development] dr4stic:
I've had my phone run a number of days without reboot. Otherwise I do tend to reboot on purpose because I do quite a bit of testing.

If you haven't factory reset your phone since you started using CM-13 and you have indeed been using it since about when it came out (or more than a month and a half), you should very strongly consider resetting your phone and setting it up from scratch. There's a good chance that'll clear up your issues and probably make your device feel faster as well. Do a full backup before you start in case you want to revert.
[G2 Original Android Development] saarxee:
Why the sound is very low in CM?

in stock the sound is very good
[G2 Original Android Development] Dade98:
sorry ... which modem you have flashed?
[G2 Original Android Development] mujka:
I did like he said i fladhed 30b modem just Google zg85 30b modem
[G2 Original Android Development] norbigazda98:
It seems there are three ways to use kernels for this ROM. Which one is recommended?

-Lambda

-CM13 kernel from PsychoGame

-original kernel in the ROM

Thanks for the answer :)
[G2 Original Android Development] chewdaniel:
try it out yourself and see which one suits you best

---------- Post added at 09:57 PM ---------- Previous post was at 09:56 PM ----------

took a wrong turn somewhere, perhaps?
[G2 Original Android Development] Dade98:
Certainly the original kernel of this ROM is the best kernel for this ROM
[G2 Original Android Development] alexx_kidd:
I'm missing Google search bar on recent apps panel on latest build. Anyone else?
[G2 Original Android Development] MrSqueaky4000:
On nightly 129 the search bar is working fine in recent apps for me on D801 with hybrid bootstack and open gapps full
[G2 Original Android Development] alexx_kidd:
Not for me, no. Although it might be an issue with gapps. Opengapps, latest build 29/1 here
[G2 Original Android Development] MrSqueaky4000:
I will try with different gapps to see if there is a change .
[G2 Original Android Development] chewdaniel:
did u disable it?
[G2 Original Android Development] alexx_kidd:
disabled,re-enabled,re-disabled..nothing.there can only be one thing going on.either the latest build has this setting broken (highly unlikely considering no one else has this issue),either it is an opengapps issue,either restoring apps with TB backup (but NO google apps) screwed something up (which would be strange cause I always do this and never had any issues.So I think it is a 29/1 opengapps issue.

OR it could be xposed bug,never had any issues with it though either.I only have amplify and gravity box MM installed
[G2 Original Android Development] MrSqueaky4000:
Must be something on your end, because the bar works fine in 29/1 opengapps (full, mini, micro) for me at least by doing factory reset, install cm13 129 nightly, install gapps, and then enabling search bar in display and lights.

D801

hybrid bootstack

twrp v2.8.6.1
[G2 Original Android Development] jl10101:
Anyone know what happened to the "prevent accidental wake-up" option by any chance?
[G2 Original Android Development] ukguy115:
Been gone for some time. You can use xposed to get it back.
[G2 Original Android Development] OT-Xtreme:
what module..
[G2 Original Android Development] alexx_kidd:
Do you know any way to add Ambient display back in settings? Xposed module doesn't work. Aicp marshmallow has managed to implement it though, so it is possible.

Also - any news on the music bug?
[G2 Original Android Development] ukguy115:
Gravity box, may have ambient display option to.
[G2 Original Android Development] dr4stic:
You don't have to constantly update your GAPPS. I often go months before updating my gapps, and that's only because it's usually when I've decided to do a full device re-install.

I'm assuming you are using the Google Now Launcher. This has nothing to do with CM and as you've noted, since no one else has the issue, it's likely a "you" situation. It's likely the application caches and/or data have become corrupt. My suggestion would be to go into Settings -> Apps, find both "Google Now Launcher" and "Google App". For each one go into it's Storage section and clear cache and/or data. If that doesn't work, maybe try wiping cache and dalvik-cache from recovery and letting it rebuild it all.

I don't believe this device ever had ambient display. I think I remember you asking about preventing accidental wakeup once, and I doubt that's coming back. As for the music bug, I don't know, but I'm doing my best to guilt people into paying attention to the problem.
[G2 Original Android Development] alexx_kidd:
No, it wasn't me. As for the audio bug, it really is a drive-me-nuts problem for audiophiles. Let's hope someone will fix it.
[G2 Original Android Development] AssassinGEO:
Alright, you guys probably know that CM12.1 audio issue when notification comes and there is a half second skip in sound. I remember CM13 had this problem too. Is it fixed or is it still there?
[G2 Original Android Development] alexx_kidd:
Did it ,with no luck.I'm going to clean install it again and see what happens
[G2 Original Android Development] alexx_kidd:
Ok, I finally figured it out. It has to do with xposed and gravitybox. Rom and opengapps are ok. Sorry for wasting anyone's time. Should have search it first a bit before posting about it.
[G2 Original Android Development] mrvlhs:
Trying to use Smule Sing and the microphone quality and volume is terrible. Just to try to give some attention to this issue as well.
[G2 Original Android Development] razielarcanum:
Cool cool. Unfortunately at the moment I've got myself into a bootloop and absolutely no hardware key methods are booting me into anything other than a perpetual CM logo, so I can't report back until I figure out whether I'm bricked or not :rolleyes:

I can tell you that the tool I used at the time told me it was JDI, which I was surprised to learn. In fact I think a part of me assumed it might have been mistaken, until the lines started showing up on the screen...

[update]: It's not bricked. Phones are resilient little buggers. If I don't tear out my own eyes while I deal with the stock LG software I'll double-check the screen type with your app once I'm back on CM13.
[G2 Original Android Development] dr4stic:
Actually, if you could check it on stock, I'd appreciate that :) And then check it on cm-13... I'm curious to hear if the values are the same.

It should still be JDI (that wouldn't have changed).
[G2 Original Android Development] razielarcanum:
Already back up and running with CM13 unfortunately! I've taken a look at the app though and I'm 99.9% sure that's the one I used originally, on rooted stock. I remember laughing at the "YES AND I HATE THEM" button.

At the time (stock) it definitely told me JDI when I told it I had no lines, and I've blamed myself ever since for not waiting for a suitable kernel to show up when all of the appropriate warnings were provided to me in advance.

On CM13 however, what it tells me seems entirely contingent on what I tell it. If I tell it I have white lines (they're actually black lines except for when it's booting) it tells me it's JDI; if I tell it otherwise it claims LGD/LGIT. There are a few posts in the thread indicating that it may only work on stock; to me on CM13 it resembles an if/else statement disguised as a screen detector :)
[G2 Original Android Development] dr4stic:
That's the OTHER thing I was afraid of. I need to find a reliable way to find that information from CM-13, otherwise there won't be an easy way to determine if it's why some people have trouble with the bootstacks.
[G2 Original Android Development] razielarcanum:
I switched my /system and /cache to f2fs and haven't had any problems that I can see so far (the bootloops I mentioned earlier were of my own doing and I believe unrelated; similarly I can confirm that the lg-devs bootstack still failed for me with ext4 partitions). On the 25/01 nightly at the moment. Will update if I run into anything.

---------- Post added at 05:37 AM ---------- Previous post was at 05:34 AM ----------

Just get them to use the kernel I used and see if their screen gets permanently damaged. :p

I'll dig around a bit.

---------- Post added at 05:50 AM ---------- Previous post was at 05:37 AM ----------

Well now I don't know. I was aware that my permanent issue was a hardware one most likely down to overheating, and that there had been reports of it happening to people on stock; but it seems that the black lines/white lines issues may have been less related than I thought. I just had the luck to run into them at the same time.

Everything else I've seen says to check /proc/cmdline, which I assume tells you no more than what the kernel expects you to have. Could be that all the app's doing is parsing that and spitting out one or the other.

Might just be worth throwing it to lg-devs?
[G2 Original Android Development] dr4stic:
Special build... please test

Hi folks, I have a treat for you...

I've run a very special

ONE-TIME BUILD

: this means I will NOT under any circumstances succumb to requests for updates just because you wanna "keep up to date." I DO NOT PHYSICALLY HAVE THE CAPACITY FOR PITY. I do however have a huge capacity for ridiculing and sarcasm. Also, these things are big, take a long time to build, take a long time to upload, and eat up my bandwidth caps.

I ran a build with the following patches/fixes:

Network type selection fix (http://review.cyanogenmod.org/#/c/129322/)

Audio offloading disabled, music seeking fix (http://review.cyanogenmod.org/#/c/130656/)

Added some extra cellular radio family types (modification based on this)

Switched some graphic settings (http://review.cyanogenmod.org/#/c/130662/)

Get it here: https://www.androidfilehost.com/?w=files&flid=48803

PLEASE MAKE A FULL BACKUP BEFORE YOU APPLY ANY OF MY BUILDS.

This has all the same patches as the 20160130 official nightly (no newer). This can be flashed over a recent cm-13.0 nightly. I've uploaded builds for d800 (because that's what I have) and for the d802 (because that's what most of you have), and d801 (cuz someone asked nice). I did run a build for d803 but I won't upload it unless someone specifically asks.

What should I know about this?

The network selection type has some weird effects for me that go away after a reboot, and may be specific to the speedtest app. After switching back to LTE, it looks like the app loses some of the network settings (but the rest of the internet connected apps work, so... weird right?).

Audio offloading is disabled. This means audio processing happens on the CPU instead of being offloaded to low-power processing (duh). This also means that the CPU will be more active than it was before, especially when the screen is off. This in turn means more battery usage than before. But ultimately, it should mean you can seek audio and what not. I'd actually appreciate it if the heavy music listeners that wanted this patch could report back on the difference in perceived battery life.

The final two patches shouldn't be of any consequence. The radio access family thing just adds a bunch of connection modes, and the video thing should just be a little more efficient than before but hardly noticeable. I just wanna make sure your phones aren't any less stable than before.

Why am I doing this?

Well, I wanna test the bottom two patches listed above. I realized the only way to get people to actually run them for a while would be to give them something they want (the top two patches listed above). So I put them together and am hoping for plenty of exposure.
[G2 Original Android Development] proyatzu:
Heavy music listener here :)

Will install as soon as i go home, then i will report
[G2 Original Android Development] posy:
installed yesterday with hybrid bootstack, it works with my standard application and also spirit2 fm open for AOSP works fine (no RDS for me at moment)

I have just one relevant bug with chrome, see the pictures and sometime also with standard browser.

about LTE, you can set the 2g/3g mode in the profile setting but seems to have no effect

Is there any way to have a camera app like the standard lg?

thanks to all
[G2 Original Android Development] carpon:
am i the only one have noticed that the sound is too low? how can we solve that
[G2 Original Android Development] chobot1976:
Change the speaker volume in mixer_paths.xml

send from my LG D802 via Tapatalk
[G2 Original Android Development] carpon:
Explain please :D
[G2 Original Android Development] chobot1976:
Edit mixer_paths.xml in system/etc and find <path name="speaker"> and change line Rx7 digital volume 60 to 68 save and reboot...

send from my LG D802 via Tapatalk
[G2 Original Android Development] dr4stic:
For #2, describe not persistent? Do you get disconnections after plugging in? Or do you mean the setting doesn't stick?

For the most part both of these seem like CyanogenMod problems and not just G2 problems. I'm trying to limit the listed bugs to just the ones for our implementation of CM on the G2. And both of the ones you mentioned are firmly in the general software category.

But thank you. I do appreciate it. :)

I think people are forgetting that CM13 is extremely early yet. When the G2 finally got added to the nightlies for 12 and 12.1, the features were pretty well cemented in place. Yet, somehow the stars aligned and we got into the early approvals for CM13 and things are quite less finished than they were with the lollipop branches.

I think most people are better served by sticking with the 12.1 snapshot or latest nightly, at least until 13 is more stable and feature complete (at this rate, I'm guessing mid to late january). At the end 12.1 was pretty damn stable for me. Hopefully someone saved the last nightlies before they disappeared.

Thanks again!
[G2 Original Android Development] seanp25:
Thanks this was useful. Do you know what should be changed to boost mic volume during Whatsapp or Hangouts calls?

Many people complaining of low volume when I ring them.
[G2 Original Android Development] bravho:
Install bootstack and reboot recovery. After that you flash CM13 and GApps.
[G2 Original Android Development] chobot1976:
For boost mic I don't know...

send from my LG D802 via Tapatalk
[G2 Original Android Development] wq0913562:
Could someone please explain that in more detail? It sounds somewhat paradox.

And what if LTE covarage is not available? Will the phone still switch to 3G or 2G respectively in that case?

Regards
[G2 Original Android Development] physiecho:
Thanks bro i ll try this
[G2 Original Android Development] ghost141:
Love it all,,, but i really dont get it.

Everytime i set up all my account, restore all my apss, and reboots.

I will get an INFINITE CM Boot Animation.

And please, don't ask me to change the bootloader, cuz i tried it all.

LOKIFIED? BUMPED? or what?

Anyone got the same issue here? Solution?
[G2 Original Android Development] chewdaniel:
thanks :D just pointing out some in case you missed it and wanna put it in the OP. I've been using CM13 since the early unofficial build and it's good enough for me so those are just minor annoyances.

MTP not persistent being that the setting doesn't stick, even tho the corresponding option is selected in DevOpts. Could be an isolated issue since on my friend's 1+1 it works everytime in that Internal Storage shows up every time he connects to PC.

1. When the opposite party ends the call an Invalid Number will popup and you have to tap OK... or when the call drops.... any situation that the call is ended that you did not press endcall yourself.

2. When you set it to LTE it will automatically connect to an LTE network and will fallback to 3G/2G in the case of a higher band service isn't available. However some of us might want to disable LTE from time to time when the LTE signal is strong and connected to it, but the internet doesn't work and we force it to 3G where it usually does. As of now we cannot choose 3G/2G and we're stuck with LTE

---------- Post added at 01:57 AM ---------- Previous post was at 01:56 AM ----------

try restoring WITHOUT data...........

do u have supersu or xposed? try without those too
[G2 Original Android Development] dr4stic:
Ahhh. I see, yeah. I'm gonna chock that up to CM13. I originally started playing with CM13 on hammerhead (my Nexus 5), which in theory should be as fully supported as they come. And hammerhead had the same issue for me.

Something else I've generally noticed with nightlies... because they're in such flux, especially early on in the development like we are now, the settings often get corrupted. The devs will play with settings and storage options and things aren't cleaned up in the interim because.... well, they're nightlies. Nightlies are testbeds, and sometimes the tests go wrong. And sometimes when they go wrong, they corrupt the settings database :)

I'm sure they'll figure out why it is or isn't working for some and not all. Until then I'm sitting patiently and manually changing to MTP whenever I connect to my computer.