yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] BackDaws:
Last 2 nightlys my wifi is dropping, it shows wifi still connected but no internet.
[G2 Original Android Development] MrSqueaky4000:
Has the "slow charging" bug been fixed ? Because I am no longer seeing "slow charging" on the lock screenscreen in build 203 but I am using the same chargers as before

:D
[G2 Original Android Development] KpKi:
Delete
[G2 Original Android Development] MrSqueaky4000:
What build and or viper version are you using ?

PS. Make sure their plugged in all the way
[G2 Original Android Development] KpKi:
No V4A ... build 3/2 D802 ... I deleted the post because I'm not grasping the issue if it's from my side or the ROM's
[G2 Original Android Development] Vrtfrank:
Flash Dolby Atmos 6.5. Flash deep buffer remover. Activate volume leveler.
[G2 Original Android Development] johnb380:
Do u happen to have a link friend?

Actually I found it but does it work with Viper4A or is it use one or the other? Anyone know if they play well together?

Thanks in advance.

Update: I guess they do play well together but I really don't see that big of a difference after flashing both zips and tuning it. Maybe it just works as an Eq like viper cuz the volume is same level to me!
[G2 Original Android Development] dr4stic:
Just an FYI for your cocktail... one of the next patches working it's way through the system gets rid of the deep buffer configuration and switches to low latency.
[G2 Original Android Development] coolhandfluke:
For a temporary fix you can increase the RX7 digital volume in the speaker section of the /etc/mixer_paths.XML file. I've set mine to 65 (default is 60) on a d802. Start at 61 and work up slowly, test all volumes at highest levels, notification, ring, media, alarms are ok before going higher. Beware as taking this too high can damage your speaker. Reboot phone to apply the new setting.

<path name="speaker">

<ctl name="SLIM RX1 MUX" value="AIF1_PB" />

<ctl name="SLIM_0_RX Channels" value="One" />

<ctl name="RX7 MIX1 INP1" value="RX1" />

<ctl name="RX7 Digital Volume" value="65" />

<ctl name="SPK DRV Volume" value="7" />

<ctl name="SPK DAC Switch" value="1" />

<ctl name="RX7 HPF cut off" value="MIN_3DB_150Hz" />

</path>

Daniel Stuart was working on this but I believe its been held up as the issue may be model specific i.e. my d802 has it but not d800
[G2 Original Android Development] saturax555:
Read the OP not an issue, just a display :

Slowly charging" displayed. This is cosmetic. Charges at the same speed as CM-12.1, check Settings -> Battery to see true charge mode.
[G2 Original Android Development] crazyguns:
I tried setting it to 65 on my d802, 30/1 nightly with dr4stic's patches, the volume seemed to increase ever so slightly, but still no where close to the loudness it was before... I'm tempted to increase it to 85 or 90!
[G2 Original Android Development] OT-Xtreme:
don't go over 70, speakers can go boom..
[G2 Original Android Development] chewdaniel:
yup. 70 is good enough. also worth noting alarm previews are having lower volume than actual alarm
[G2 Original Android Development] xtract1:
still doesent work.

and i'm on the 0402 nightly now
[G2 Original Android Development] sapsa:
Is there some recommanded way to update?

I see update in 'CyanogenMode Updates'

I click on it to download

And I would like to flash it and gapps also (which i have package also (do i need to use the newest or the one I used on first install?))

Do I wipe anything ? Do I flash both zip in query in TWRP ?

Or do I update via Update option and then flash gapps ?

Edit: after hiting update it didnt not need new gapps
[G2 Original Android Development] seanp25:
If you're coming from a previous CM13 nightly, there should be no need to flash gapps every time (Google Apps will just update as normal through Play Store).

No need to wipe either.

I use this app CyanDelta: https://play.google.com/store/apps/details?id=com.cyandelta&hl=en

Just point it to a full nightly zip on your phone, and then it just downloads small delta files (30MB a day or so) and flashes for you also. No need to do anything manually in TWRP.
[G2 Original Android Development] coolhandfluke:
If your ring tone is an mp3 etc then that may be the problem, best to test with the CM defaults. Higher than 70 may damage your speaker
[G2 Original Android Development] MrSqueaky4000:
I understand that it is cosmetic and has nothing do with actual charge speed, I was just wondering if it was fixed because it now says "charging" on the lock screen instead of slowly charging
[G2 Original Android Development] akaloith:
snapdragon camera panorama is low resolution

google camera panorama is OUT OF FOCUS, all panoramas come blured :(

there is no way to shoot a decent panorama :(
[G2 Original Android Development] chewdaniel:
it depends i guess.... i'm still getting Charging Slowly...
[G2 Original Android Development] KpKi:
Noticed a weird thing , while using HW decoder on streaming apps/browsers while seeking through a video it doesn't seek to the position and play , it keeps fast forwarding the video ..why is this happening ?

D802 ...build : 3 Feb

To test use MX player and stream a video.
[G2 Original Android Development] OT-Xtreme:
in mx try to untick "fast seeking" in settings > player
[G2 Original Android Development] crazyguns:
I was actually just playing a youtube clip and a podcast via podcast addict.. Even on full media volume it sounded really low.. would flashing v4a or something make that better perhaps?
[G2 Original Android Development] edi194:
Hi everyone:) I want to share with you my custom build of CM13 with patch for network switcher with recent changes (from 03/02). Maybe more builds'll come ;)

D802

Changes in comparsion with official nightly:

- working network switcher

- DPI changed to 420

I know, that actual patch for switcher is not good enough, but it's WORKING, that's why i've builded this:)
[G2 Original Android Development] BackDaws:
Anyone else having really **** wifi? I have to keep turning it off and back on to get it working.
[G2 Original Android Development] blastagator:
I guess possibly worth adding to the doesn't work list: encryption. Although this probably isn't a surprise given I don't think any custom ROMs on our phone seem to support it. I tried it last night just to see and had the standard hang at 0%.

Did a lot of searching for any rom that may have had it fixed, to pose possible solutions, but had no such luck. If anyone can point me to a working non-stock rom, that would probably be a good starting point for me to look at.
[G2 Original Android Development] ramabg:
Can you share the source with us so we can merge your change into CM mainline and include you as CM contributor ? Nice work brother.
[G2 Original Android Development] Kaejin:
Anyone knows how to change nav bar height?
[G2 Original Android Development] Treboeth:
You can only do it by installing Xposed and a module lie Gravitybox.
[G2 Original Android Development] Vrtfrank:
Could you please explain a little bit further? Does it mean that deep buffer remover is not any longer necessary or will it break atmos? Do you have a hint where i can get a little more info about the way Android audio works?
[G2 Original Android Development] dr4stic:
http://review.cyanogenmod.org/#/c/130868/

There's no longer a deep buffer to remove. If you wanna install the stuff, go for it, but changes in the audio subsystem are in the works. Nothing major, please don't get all your hopes up, but there are changes... so if you like your setup the way it works now, stop updating for a little while.
[G2 Original Android Development] dr4stic:
In other news...

We're getting some long overdue attention that I'm rather grateful for.

As of 20160205 build, we will have network type selection fix!

http://review.cyanogenmod.org/#/c/129322/

On top of that, it looks like our RIL is getting more attention and may get better support than it had before. I'm not sure what that'll look like, but I doubt it'll mean better reception. It'll most likely mean MM will do a much better job of understanding what our radio is doing.

You'll also notice there is a barrage of audio patches in the works. At the moment it's all basically redoing the same patches that "fixed" the seek bug of a few days ago. The original fix was more of a mistake that effectively disabled audio offloading, so the patch was reverted and proper disabling was put in place.

At the moment our offloading is broken and the devs quite a lot smarter than me are working to get that working again.

I gotta say it is so awesome we have so much attention lately. If you haven't done so already, you should consider donating to CM.
[G2 Original Android Development] OT-Xtreme:
great news hope g2 will continue to get the attention and fixes
[G2 Original Android Development] ramabg:
Does this ROM use Fast Dormancy ? My carrier does not support this and It is draining my battery. Secret menu in stock LG G2 ROM is no longer working in this ROM so I cannot check nor disable It. Google doesn't give good answer too. Anyone here know how to disable It in CM 13 ? Thank you
[G2 Original Android Development] vztmi:
Just for the record, encryption works for me. I updated from cm-12.1 to cm-13.0 with nightly 20160102. I successfully encrypted it a few hours later. I started encryption and it was OK about 15-30 minutes later. I don't know how long it took because I didn't watch my phone during encryption. I have a d802 model. (Not sure it makes any difference with respect to encryption, but I use only f-droid. No gapps.)

I have been a very happy cm-13.0 user since then. The recent progress are amazing. Thanks A LOT to all people involved.
[G2 Original Android Development] coolcfan:
I tried to use thread search but it returned no result.. so, anyone knows if the WiFi Tethering works on this ROM, and how does GPS perform? I'm currently on a pretty old version of CM12 unofficial and everything works fine except Tethering. Other device can connect but stuck with "getting IP". I'm considering updating because of that.

Thanks in advance!

--

BTW regarding the camera issue mentioned in the second post, can I just install the pico or nano package of Open GApps to avoid it (since they shouldn't include the Nexus camera)?
[G2 Original Android Development] johnb380:
Yes you can that's what most of us do!
[G2 Original Android Development] coolcfan:
Thank you! Could you also take a look at WiFi tethering?
[G2 Original Android Development] dr4stic:
I am pretty sure I've tethered with my phone on 12.1. Once it stabilized I loved that release... I just tried tethering my tab to my phone and that worked... so I'd say you're good to go.

If you have 12.1 installed, you probably have the required bootstack already, so just take a full twrp backup and do a fresh 13.0 install and check it out. If you don't like it, roll back. Hell, you should probably at the very least wipe 12.1, update to the latest snapshot (I think it was a few days ago) and reinstall that. You'll probably like it better than what you're using now... Just make full backups of your existing system first :)

Oh, and update your recovery to the one recommended in the FAQ

Definitely valid. Really if you just stick a gapps-config.txt file in the same directory as your gapps package with the following line in it:

CameraGoogle

you'll be fine with any of the packages. In the default exclude mode, that'll keep the google cam from being installed, therefore OpenGapps won't uninstall the stock camera.
[G2 Original Android Development] Th4nat0s:
Hi people i have a bug for cm 13 and also cm 12.1, The audio of the notifications he go random . it is very annoying.

There is a solution?

Thanks all.

PS sorry for me little english

Inviato dal mio LG-D802 utilizzando Tapatalk
[G2 Original Android Development] d1rX:
Thanks man. Will try since playing with mixer paths, there isnt much improvement
[G2 Original Android Development] sachilleas:
[MENTION=4781875]d1rX[/MENTION]: check this dr4stic's post before flashing anything. In the 5/2/2016 nightly seems something that has changed about low latency.
[G2 Original Android Development] Jan Philipp:
There are no more bugsfixes listed (d802) for the next Nightly. Does this mean we'll get the first CM 13 Snapshot tomorrow? :fingers-crossed:
[G2 Original Android Development] d1rX:
yea, yea, i'm on an old nightly anyway ;)
[G2 Original Android Development] GyGu:
There are still problems with the sound (I'm in 02/05), to send a voice message for whatsapp gets noisy
[G2 Original Android Development] wzedlare:
Thanks for the builds.Do you think you will support ls980 and vs980 variants? I have been using ls980 and want to use official cm13
[G2 Original Android Development] PsychoGame:
Hello everybody,

Everybody is noticing the stabilizing of CM-13.0 for our G2 as well as the other devices.

In the past CM-Team has hinted they were hoping to push out fist Release Snapshots around end Januari beginning Februari.

Taking into account the state CM-13.0 is at the moment I'm guessing first snapshot will be coming somewhere this month.

I'm not official member of inner circle on CM-Team so it's purely speculation but I think it's a pretty strong conclusion.

To [MENTION=6810779]wzedlare[/MENTION],

If I remember correct CM already pushes out builds for VS980: http://download.cyanogenmod.org/?device=vs980

I don't know if CM-Team will ever support LS980 for CM-13.0 but I can always check why they chose not to support CM-13 for LS980.

Now back to development talk:

Today I've put the commits from my "CM Beta Kernel" in waiting line to be merged.

If you encountered any problems/noticed any regressions or just want to give positive feedback, head over to my kernel thread and leave your comment/review.

When reactions are positive or I have no reactions at all I'll interpret it as everything OK so I'll push through the respective commits.

So if you want your voice to be heard please leave a message.

Greetings PsychoGame (A.k.a. Jan Jasper de Kroon)
[G2 Original Android Development] alexx_kidd:
So,do we still flash your kernel with the latest nightly build?There are kernel stuff that are not on the official yet,right?
[G2 Original Android Development] PsychoGame:
Hello [MENTION=6176962]alexx_kidd[/MENTION]

The commits which are in testing phase in my beta kernel indeed haven't been merged yet.

I haven't really received much feedback on it yet while the kernel has been downloaded approximately 80 times (all variants)

Of course I run the kernel also on the phone myself, so if I don't receive any feedback I'll merge the commits based on my experience with it.

This doesn't mean it'll always work nicely as there are so much kernel commits it's nearly impossible to test every aspect myself.

Greetings PsychoGame
[G2 Original Android Development] alexx_kidd:
I'm running your kernel and haven't experienced any problems at all, in fact it is a very fast and battery efficient one
[G2 Original Android Development] Hbohd:
[MENTION=4647521]PsychoGame[/MENTION] and other,

could you try to call 2-3 different people (phones) and ask them/check whether they hear THEIR voice as a light echo after saying sth?

To be honest, I'm not using pure CM, however yesterday I updated CM's device trees and my friend told me that they can hear slight eho of their voice. On the other hand, other friend couldn't notice same.

I know this might be a coincidence or some other source's fault, however worth to try and not taking too much time :) thank you all !

Wysłane z mojego LG-D802 przy użyciu Tapatalka
[G2 Original Android Development] sachilleas:
Thats a very good question. Is there a dial code for CM?
[G2 Original Android Development] edennem:
Same for me. My workaround: shoot single pictures and stitch them together with the free app "bimostitch" (set the maximum size in its settings to 100MP)
[G2 Original Android Development] PsychoGame:
To everybody,

I've been cooking up a new beta release of the stock kernel (05/02/2015).

This time it's mainly graphics related patches and some basic android related patches.

The kernel on my phone is running perfectly so should be safe to apply to your nightly.

Please test the new kernel build and try out if all the stuff you usually do with your phone still works as expected.

When you encounter something which you think is broken take logs on your device using Syslog (my preference) and upload it somewhere or PM me.

Please take the time to write a review in the corresponding thread about your experience with the kernel after a 1 to 2 days of normal use.

For download links head over to: http://xdaforums.com/lg-g2/orig-development/kernel-stock-cm13-0-kernel-unmerged-caf-t3291282
[G2 Original Android Development] niubboxp:
[MENTION=2096805]dr4stic[/MENTION] could you pls address the otg inside the file manager? In cm12.1 worked thank you
[G2 Original Android Development] RXG9:
I have a D801 with a custom recovery TWRP and Cloudy G3 2.2 (Kitkat) it was previously on Cloudy G3 3.3 (Lollipop) but I reverted back to Cloudy G3 2.2 (Kitkat) after a week of Lollipop.

I'm not sure which bootloader i'm on. how can I find out? Also when am I supposed to flash the bootstack, after flashing the gapps? Or before flashing the rom? Also which bootstack should I flash the 5.0.2 Bootstack with Jellybean (Loki) bootloader or 5.0.2 Bootstack with KitKat (Bump) bootloader ?

Here's the problem I'm having I tried clean flashing CM13 12/7/15 nightly, flashed opengapps pico 12/8/15. After flashing I restart my phone and the phone says Android apps updating, 1 out of 96 apps. so it finishes loading all the 96 apps, then after that it says "android system starting" (or something along the lines of that). After that my phone doesn't start, it's stuck there. I left my phone for 30+minutes at that screen "android system starting" but nothing happens.
[G2 Original Android Development] SashaVeliki:
Forced turn off. Wait pressed on power off about 20 sec. Than try again. If won't start try entry in recovery and wipe cache and dalwik cache. Than reboot. I have same problem with BlissPop.

CM 13 stuck on boot for me too.
[G2 Original Android Development] ukguy115:
Anyone getting Bluetooth share stopped errors?
[G2 Original Android Development] rdeleonp:
Just to understand, it stays in LTE mode, but it does negotiate 3G/2G?

Or is no negotiation possible?
[G2 Original Android Development] dr4stic:
Honestly I don't know for sure, but I imagine it does. The problem is the OS speaking to the radio to force it to 2G or 3G. When the radio is left to it's own devices, it should negotiate properly on it's own.
[G2 Original Android Development] chewdaniel:
it does.... depending on coverage...... the sucky part comes when LTE has no internet but 3G does and you can't do anything about it lol.. or get a 3G-only SIM. haha
[G2 Original Android Development] RXG9:
I just tried that but what happens now is that I'm stuck on the CM logo icon at startup.
[G2 Original Android Development] bigiuly:
The rom it's very good, but wifi disconnects often.
[G2 Original Android Development] SashaVeliki:
[MENTION=5229863]RXG9[/MENTION]

Try these steps:

Install stock lp rom. Root and install Twrp which is suggested in topic. Wipe all except internal storage. Install rom, and wipe cache, dalvik and factory. Reboot system.
[G2 Original Android Development] AsM0DeUz:
I do [emoji20]

---------- Post added at 09:02 AM ---------- Previous post was at 08:57 AM ----------

In cm 12.1 there was a way to put the phone silent for a defined period of 15 minutes, 1h up to 8h. But I can't find the same option here.. Is there a way to enable that?

Regards
[G2 Original Android Development] sunekosuri:
Nobody knows why but google removed it in AOSP 6.0 It is back in 6.0.1 AOSP version so you should hold up for CM to merge new AOSP sources.
[G2 Original Android Development] Christof-:
I am only connected to 2G. It doesn't matter if 3G is available or not. Settings says still LTE. So iam a little bit slow these days ;)
[G2 Original Android Development] bosbode:
Yep
[G2 Original Android Development] Ginel:
is there any custom kernel for this rom?
[G2 Original Android Development] Oto_Shan:
Very stable, nice work :). I searched LG Quick remote for CM13 is it work?
[G2 Original Android Development] bravho:
Looks like there's a big update?
[G2 Original Android Development] Paddy2014:
I've dirty flashed 20151209 over the previous nightly.

All seems good except Bluetooth. I'm getting '...Bluetooth Share has stopped' errors. A reboot fixes it temporarily.
[G2 Original Android Development] ukguy115:
Same here.
[G2 Original Android Development] SashaVeliki:
Please, how to install cyanogen recovery? It's not zip. Can't throw curent TWRP.
[G2 Original Android Development] dr4stic:
No. You're never getting otg again.
[G2 Original Android Development] OT-Xtreme:
because?...
[G2 Original Android Development] dr4stic:
I've had this issue forever (since at least 12.1) on my mother's phone and mine. Both of them d800's. I don't think the echo cancellation is as good as stock, but then I never used stock (been on CM for the life of my phone). It's one of my greatest pet peeves with the phone.

I will say that it becomes noticeable with partial obstruction of some or all of the microphones (the d800 has 3, all other models have 2). If they tell you that they hear an echo, try shifting the way you hold the device. Also, the phone case can have quite a bit to do with the echo as well. In my mom's case it's terrible. With me it's a rare occasional thing.
[G2 Original Android Development] crazyguns:
Read the first few posts guys.. It's been addressed already. If you cannot see your question on the first page or in search, asking it is reasonable.. But if you just ignore everything and keep asking questions, you're just being ignorant.. If you're having a different issue it'll be better if you provide a lot more information than a one line question..

OTG works absolutely fine with the default document browser (pressing Explore on the notification as seen in my attached screenshot) and in Solid Explorer via the /mnt/media_rw/XXXX-XXXX/ folder. From the faqs on page 1;

Is OTG working? I can't see my attached device!

The OTG, to my knowledge (and personal experience), works. If you get a notification when you attach your OTG peripheral to your device, then OTG is working.

The PROBLEM is that Marshmallow (Android 6.0) does things differently with attached storage. Locations are all different from the way they were on previous versions of Android (Lollipop and earlier) and mount points are now auto-generated. Your chosen file manager must have been updated to work with the new 6.0 scheme. Not all of them have been.

For example, I just attached an OTG sdcard reader with an SD card inserted, and the storage was mounted at /mnt/media_rw/7E7B-0812
[G2 Original Android Development] OT-Xtreme:
congratulations for speech of a tool, dont treat people like their noobs, cause im far from it. otg has barely been discussed and not deeply. no one want to use the default file manager/explorer of cm. so essentially yes "it doesn't work"