yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] dr4stic:
Guys, I appreciate your enthusiasm, I really do. But please keep in mind that we need reports from stock, unmodified systems, please. Testing kinda has to happen in a vacuum in order to isolate bugs and fixes, otherwise it just makes things harder for us :)

EDIT: Nevermind, I see you said you uninstalled it. YAY!!!

What device are you on?
[G2 Original Android Development] Mikulic1802:
Lol... D802☺️

And i first uninstalled driver, then app. It should be clean...
[G2 Original Android Development] dr4stic:
I am not sure how Viper works, to be honest. But I wonder if you wouldn't mind wiping just the system partition and installing just the usual CM + Gapps + AudioPatch zip files? If you leave the user data (don't factory reset) in place, you shouldn't lose any data. This will insure you have a full stock CM install. Do a backup before doing anything for good measure.

If you don't mind of course. I don't think it'll change the outcome, but it'll definitely make me feel better about it :)

Thank you, btw. This is very positive feedback!
[G2 Original Android Development] Mikulic1802:
Ok, will do it... That will take some time since i have to re-download everything, will report in an hour or two
[G2 Original Android Development] dr4stic:
Oh, wow... heh, yeah, I don't like removing that stuff from the phone after I flash. Have had too many things crash in my life at really in-opportune times to not have a backup plan ;)

Thanks in advance!
[G2 Original Android Development] mpopovic85:
I installed the patch even though my audio was working fine (I've installed a week ago previous PsychoGame's audio patch). Didn't notice any improvement, but at least sound level and quality seems working just fine. Running 0502 nightly with PsychoGame's beta kernel, no mods. Thanks for your commitment!
[G2 Original Android Development] dr4stic:
I'll ask but I'll be honest with you, I doubt it'll get any traction. If it's behaving the way Stock does, there's usually little effort on the dev's parts to make a change. Ideally a photo should be saved as recorded by the sensor and with proper rotation hints added to the metadata. If the sensor is mounted inverted (it happens on devices depending on the clearances in the chassis and other things) then the image is recorded that way. It's up to the viewer to display it properly according to the rotation hints. Sorry :-/

As for the option being introduced in Snap, I'm not part of the snap team and other than beautification, I'm not sure exactly how much work they're putting into adjusting the behavior.
[G2 Original Android Development] holoyolo01:
OK so I flashed the patch over 5.02 nightly and there is some improvement but still the speaker volume is very low.

You may need to increase the speaker values on the mixer_path...
[G2 Original Android Development] proyatzu:
Doing that may cause speaker damage and/or distorted sound,ahhh if it was that easy :D
[G2 Original Android Development] dr4stic:
do you mean 20160205? (Please use ISO dates to reduce confusion, thanks)

Is it too low in your opinion, or is it too low when compared to stock LG? This is LG values.

I'm also assuming you're using D802? How did you install CM13? Did you come from Stock 5.0 without installing any bootstacks, did you install the LG-Devs or the Hybrid bootstacks? Did you come from stock KitKat and install the bootstacks?

We're trying to narrow down why this varies so much. Thanks.
[G2 Original Android Development] proyatzu:
Dude your goal is to make the audio quality as loud and as clean as stock?
[G2 Original Android Development] dr4stic:
Not expressly, but why not? It's the same hardware, it's using the same firmwares, why shouldn't it sound similar?

Our goal is to clean up the audio variances. The volumes, in theory, shouldn't vary as much as they seem to. In one instance one person with a D802 saw a huge change with the zip while another saw little to no difference. Why is that? No one has a good answer and it's time we did have one.
[G2 Original Android Development] migueldbr:
I'm going to test the zip without editing any files and report back. Sound is a bit subjective in my opinion...but it is indeed to low on stock cm13, and making it louder by editing mixer paths to match the volume level on stock, makes sound distorted. At least on my device. Maybe with this patch we will be able to raise volume without distortion. Will report back when I test it
[G2 Original Android Development] ansontyl96:
i am currently using 0205 build with psychoGame kernel and your audio patch, it seems that the audio does become a bit louder but I really can't tell, it might be 10 to 20% louder I supposed
[G2 Original Android Development] Mikulic1802:
So I clean flashed latest nightly and gapps. And then i tested stock audio player, youtube and one ringtone. Then I rebooted to recovery and flashed audio fix. To be honest, I think that there is no diffrence. I guess that last time there really where some problems with viper4android drivers, because youtube sounded way louder than now. But I found out that using cm equalizer reduced loudness very much, and after disabling it sound is much louder, that is while playing mp3s with stock audio player. But the real problem, for me, is youtube, its really not even close to stock. Thank you guys for your efforts, i am happy to help if you need testing. Good luck
[G2 Original Android Development] migueldbr:
[MENTION=2096805]dr4stic[/MENTION] the sound volume sounds like its the same to me, I see no difference. YouTube is quite low compared to playing a song on the audio player
[G2 Original Android Development] dr4stic:
Refresh my memory... what's your device? how'd you install (bootstack, yes/no, etc)?
[G2 Original Android Development] migueldbr:
****, sorry, completely forgot about that. I have a d802, hybrid bootstack. Normal flash with all the wipes

Edit: scratch that, I dirty flashed the 05.02 over 30.01
[G2 Original Android Development] viper909:
Just wanted to chime in and say that like stayhc, I'm on a VS980 and post-2/04 nightlies are unusable for me due to constant com.android.phone FCs. Tried clean flashing, etc.
[G2 Original Android Development] X0FVZ:
This work for D805?
[G2 Original Android Development] stayhc:
Dr4stic send me his own build with a patch merged that fix it, but i am unable to test if LTE work because where i live signal is really ****, but at least 2g/3g works and no more fc, try to pm dr4stic for the build or i can send you the link if him was unable to answer you.

Enviado desde mi LG-VS980 mediante Tapatalk
[G2 Original Android Development] viper909:
Is it going to be merged in officially? I don't mind waiting if so, but otherwise I'll send him a PM.
[G2 Original Android Development] stayhc:
As I know yes, but not soon because need some testing and confirmation that it works.

Enviado desde mi LG-VS980 mediante Tapatalk
[G2 Original Android Development] johnb380:
Since were messing with mixer paths and such audio things shouldn't we be wiping caches after flashing this zip? I know most other zips that edit audio require this. So I'm asking if it would help or if its needed to hear a difference?

Thanks!
[G2 Original Android Development] dr4stic:
I suppose it couldn't hurt... Honestly I'm not used to editing mixer paths. All this patch does is replace the files, if you normally have to clear cache after editing the paths, then by all means yes, do taht. I'll make a note in the original post. Thank you.
[G2 Original Android Development] johnb380:
D801 with the bootstack from LG devs here on the 20160206 nightly dirty flashed over the last nightly but I wiped system, davlik, and cache booted up played music to check volume and sound. Then booted into recovery flashed the audio zip then wiped cache and davlik again and booted.

Unfortunately tho I don't notice any difference in audio volume or clarity on my device but thank u for taking the time to try and fix this for us. Let me know whatever I can do to help for the d801 guys!
[G2 Original Android Development] dr4stic:
So, ummm.... after a bit of argument over things like responsiveness and bugs and what not, it seems that for you vs980 folk (everyone, really, but starting with you), our devs want you guys to go through the process of logging the problem and then creating bug reports in Jira with the logs of the problem. Sorry about that.

You'll need to do this with a version of the ROM that's failing. You'll need to produce the bug twice while taking two different kinds of logs. And this presumes you have connected your phone and can recognize it when running "adb devices"

I recommend starting from a fresh reboot each time. Once you are ready to produce the log, start the logging command, then generate the error, then press ^C to stop the log.

The first log is a full log.

adb logcat > full.log

The second is a radio specific log

adb logcat -b radio > radio.log

Once you have the two files, please go to the following link and follow the directions to post a bug report on the CyanogenMod Jira:

https://wiki.cyanogenmod.org/w/Doc:_The_JIRA_project_management_system

Please be as articulate and descriptive with the bug as possible. I'm sorry this is such a pain, but it's what they're asking for.

This actually goes for everyone. It's claimed that we never produce proper bug reports, or any bug reports at all. So I encourage you all to start logging your bug reports on the G2 in Jira.

Thank you all.
[G2 Original Android Development] chewdaniel:
[MENTION=2096805]dr4stic[/MENTION] d802 here. flashed your patch with the usual wipe system/cache. doesn't seem to be much noticeable difference in volume.... on droidth's bootstack
[G2 Original Android Development] PsychoGame:
Hello everybody,

This patch should be tested on a variaty of audio cases, not only playback on phone speakers.

You also should test the audio quality of phonecalls, headsets, earphones etc. (as another often heard complaint is low in-call audio volume or very poor audio quality).

Please give these patches a few days of testing, and do not jump to conclusions too soon.

If neccesary I'll take a look at why speaker audio is low on volume later on. First I need to know exactly what improvements stock audio configs make.

Greetings PsychoGame
[G2 Original Android Development] newyorkerboy:
After installing cm-13.0-20160206-NIGHTLY-d802.zip, my WiFi MAC address changed. How is it possible/is it necessary? Can it cause any problem in the future (now WiFi works)?
[G2 Original Android Development] vztmi:
Strange indeed. As written before, I'm not sure about the time required for encryption. It was roughly 30 minutes, not hours. But I didn't follow the progress closely so I'm not 100% sure.

I confirm that I'm using the cm-13.0 kernel. Maybe you'll want to try with nightly 20160102 (even if it's one month old!). At this point, I can't think of anything else.
[G2 Original Android Development] coolhandfluke:
Hi, I have had this issue prior to 15/11/2015 as that's the date I added the rx7 fix to my known issues doc, so it must also be an issue with cm12.1. i didn't upgrade to cm13 till December.

Bootstack, Daniel Stuart's. Device d802 on 20160206 nightly

Patch tested without any noticeable change so far :-

YouTube app

Opera YouTube website

MP3 playback

Ringtone

Alarm

Notification

Thank you for all your hard work
[G2 Original Android Development] chewdaniel:
wait....... WHAT????

http://review.cyanogenmod.org/#/c/131731/
[G2 Original Android Development] OT-Xtreme:
i hope it will be reverted just for CDMA..
[G2 Original Android Development] deimdos:
Hi @dr4stic,

d802 with Daniel Stuart's CAF bootstack, CM13 20160206 clean installed.

I didn't notice any difference in loudiness with YouTube videos.

Cheers
[G2 Original Android Development] mmd1907:
Flashed audio patch with droidth bootstack 02/05 nightly with my d802.

Nothing changed
[G2 Original Android Development] RohanM:
Wondering why LS980 is still not officially supported whereas it is still getting CM 12.1 nightly.
[G2 Original Android Development] Killua96:
http://xdaforums.com/showpost.php?p=65169323&postcount=1192
[G2 Original Android Development] tuncay_93:
I read the FAQ but smth is not clear to me currently running stock D802 with LP update. Do i need to install this bootstack thing and how do i check what BL i am on kk or lp cuz it says check it but how ?
[G2 Original Android Development] niubboxp:
if u are on LP you dont need to flash the bootstack
[G2 Original Android Development] tuncay_93:
Thanks for the quick reply! :good::good:
[G2 Original Android Development] stef.t97:
Hey, is there any way of keeping my dpi changes when I flash a new version? The DPI always resets to default, screwing up my homescreen which means I have to set it back up again.
[G2 Original Android Development] stayhc:
Well, I already got the logs from 2016-02-05 nightly, but I have problem with creating jira issue because in ''Affects Version'' only show me two options, 12.1-YOG7DAO or 12.1-YOG4PAO, which I must select?

Thanks

P.S. Just created the issue with information in description, here is the link https://jira.cyanogenmod.org/browse/CYAN-7390
[G2 Original Android Development] chewdaniel:
here u go :) if u need a different value just change it inside the updater-script

flash it before gapps since they have dpi-specific apks
[G2 Original Android Development] dr4stic:
Thanks, made sure someone payed attention to it :)
[G2 Original Android Development] chewdaniel:
i would sure hope so....... seems illogical to "punish" GSM devices just cos CDMA's having issues with it, given the ratio of GSM:CDMA phones out there
[G2 Original Android Development] dr4stic:
That change goes hand in hand with these:

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

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

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

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

The g2-common device isn't the only device repo that governs us...

The idea is to keep the one in g2-common as generic as possible and bring the GSM specific fix to the gsm specific devices so that both the GSM and CDMA devices get the failed number fix.
[G2 Original Android Development] blastagator:
It seem the fun bluetooth bug from kitkat has made its comeback! Connect, play music, disconnect -> bluetooth stuck on.
[G2 Original Android Development] chewdaniel:
ah ok.... missed out on that.... makes perfect sense then tks :D
[G2 Original Android Development] dr4stic:
Hmmm... I'll play with this later, I'm going out driving for fun and cool weather in Miami! Don't forget to file a Jira bug report. Supposedly we don't do that enough.
[G2 Original Android Development] zexcrazy:
D802 here. Only droidth LP patch flashed before CloudyG2 3.3. No other mods or bootstacks flashed on CM13. Sound i pretty much the same as it was prior to audiofix.
[G2 Original Android Development] blastagator:
Good news (only for a hand full of people I'm guessing). I got encryption working! :) I am still trying to nail down exactly which kernel flag is the culprit, will push changes to CM once I do.
[G2 Original Android Development] laurenjh:
Has anyone noticed increased battery draining with the 20160206 nightly? The one time I didn't make a backup is when I actually have problems. I was like, there haven't been any problems so far, might as well just update without backing up. Worst mistake of my life :')
[G2 Original Android Development] Mikulic1802:
Sorry but i forgot to respond last time you talked about encryption, it's working completely normal for me, i turned it on before few days. D802, i am currently with your latest twrp 3.0.0.0 and yesterdays nightly.
[G2 Original Android Development] blastagator:
Oddly, the nasty flag was taken care of on d802, so d802 encryption should work. Other models had the evil flag :p
[G2 Original Android Development] amkiller:
That's great, thanks. I've successfully upgraded :).

I am sorely missing the lack of knock-knock code unlock, the q-slide calculator and the weather unlock screen. Are alternatives to these available on Cyanogenmod?
[G2 Original Android Development] KpKi:
I'm noticing random WiFi disconnection while using the phone ? My hunch say its from kernel side

D802 / latest nightly
[G2 Original Android Development] Andysuarez:
Hi dr4stic

I have a vs980 and was working well with version 20160203. Today upgrade to the latest version 20160206 and I had the com.android.phone bug, but I found the patch you gave stayhc and everything returned to work well again. LTE is faster than before.

Sorry for my english, im from Colombia.
[G2 Original Android Development] dr4stic:
Actually, I can't get a hold of stayhc, I need to test a different fix to that. Can you please test this: https://www.androidfilehost.com/?fid=24407100847293410 and get back to me quickly? Also, test and make sure LTE works properly, etc...

EDIT: Just got a response back. She is updating her ticket to indicate success. I suspect the 20160208 build tomorrow (or 20160209, whatever it's called)... the next build will have the patch.
[G2 Original Android Development] Andysuarez:
I'm testing the patch now and everything seems fine . lte is better than my last version 20160203.
[G2 Original Android Development] Vrtfrank:
Thanks for clearifying!

Gesendet von meinem SM-G900F mit Tapatalk
[G2 Original Android Development] KpKi:
As for my latest post for WIFI disconnection it seems that when I changed the WiFi settings from 5ghz&2.4ghz to 2.4ghz (my router band freq ) the WiFi doesn't seem to disconnect !!!
[G2 Original Android Development] :
does anybody here has "CyanogenMod System" as one of the top battery drainers?
[G2 Original Android Development] khodos:
I'm loving the rom, and getting very good battery life, but the lack of the features "Skip swipe to unlock" and "Quick unlock" is killing me :(
[G2 Original Android Development] Mohangrmc:
for these kinds of functionality u should try various cm rom derivatives ...
[G2 Original Android Development] floel:
Question about "system profiles"

While for me, everything is working great, I have a quick question:

Why is disabling the lock screen disabled in the system profiles (see attachment)? E.g. I'd love to define that in my WiFi at home, the lockscreen is disabled. On Lollipop I used LLama with SecureSettings, but disabling the lockscreen apparently isn't supported on Marshmallow.

A google search didn't help me. I only found stuff about "swipe to unlock is disabled" because of the device administrator. Clearing the "trusted agents" didn't help.

Except for that, the ROM is great. Very stable, great battery life and no issues at all.
[G2 Original Android Development] edi194:
I've one question. It's possible to add 60FPS camera option? If i know good, it needs Camera HAL editing.
[G2 Original Android Development] dr4stic:
some time ago they tried and it crashed on our setup. I don't know if it was a deficiency in our camera drivers or a deficiency in the devs, but it was definitely attempted.
[G2 Original Android Development] dr4stic:
Need some audio help

I believe it was [MENTION=4363175]migueldbr[/MENTION] that posted that the audio volume/quality is subjective, and he's absolutely right... well, maybe just mostly right. What I need to do is take out the "subjective" part of the comparison.

I've got a few stands, a Rode NT1, an XLR cable, and a firewire interface and I'm in the process of coming up with a testing scenario to try and get a baseline for what people are describing as low audio volume/quality. I intend to do some a/b testing between LG stock and cm-13.0 (and possibly cm-12.1, though I imagine it'll be about the same). It is absolutely going to be a MASSIVE pain. But I'm tired of this crap pissing me off.

What I would like from you all is some scenarios that you believe expose the difference between stock and cm volume levels on the G2. I would also like scenarios that you believe expose the difference in QUALITY of audio between stock and cm on the G2. These could be specific soundcloud tracks, youtube videos, etc. Please indicate a time code that you think illustrates the issue. If it's about sound quality, make sure to additionally include volume levels (like "3 steps down from maximum volume" or something like that).

PLEASE be specific, descriptive, and clear in what you tell me. It's important. PLEASE don't just chime in by telling me that someone else's suggestion is the way to go, I would really like varied ideas and scenarios so I have some choices and can make a decision on the best one. I'll also be looking for some reference audio calibration files on my own.

Also, please send me a copy (pm is fine) of your current mixer_paths.xml

ONLY if you've modified it

. Also if you do that, please indicate to me which device model you have, as well as the storage size on your device.

I likely won't put together this rig until next week but I'd like some suggestions starting now. I'm gonna make this audio bug my mission if it kills me.

...

It likely won't kill me..... but it may make me hate people. :)
[G2 Original Android Development] coolhandfluke:
Hi [MENTION=2096805]dr4stic[/MENTION]

The issue I really notice is ringing volume is so low I miss calls. I discovered the speaker rx7 quick fix while on cm12.1 so I had the problem then. I can't remember if I had it on cm12 or cm11. Because I didn't search for a solution on cm12 probably means low ring volume became noticeable with the introduction of 12.1 I'm on a d802 and will test the earlier mixer_paths.xml if you can post them.

Great job you are doing, many thanks

EDIT After some Googling it looks like volume on the g2 has been an issue since at least kitkat.
[G2 Original Android Development] migueldbr:
my main gripe with sound is not the low volume, but rather the low quality of sound (only the speaker, i am perfectly satisfied with in call sound). It really comes too low from a fresh install of cm13 build, but editing the mixer paths file value of speaker (rx7 value) from 60 to a higher value(i always do 65), makes the sound from the speaker louder but starts to distort on some videos/mp3s(always tested on the max volume step). Compared to stock(from my experience running the same mp3 file) at max volume step, the stock sound coming from the speaker at max level is higher, while not sounding so distorted. So to sum up my experience, on stock, i have louder speaker sound without distorting as much as cm13 sound.

But yeah, it was me who said it was subjective and it really is...some people are fine with a bit of distortion and probably dont even notice it (hell, i have read some posts where people advice to edit the value to 70, which would distort a lot, at least on my phone, because i tried it already). I cant make a comparison with both stock and cm13 because i only have one g2...But even my old nexus 5 that my girlfriend has now (which i considered to have ****ty sound) maxes out quite louder than my g2 when playing a youtube video (without distortion).

The best way to test sound would be on a 320kpbs mp3 on max volume, because on lower quality mp3 it will probably start to distort even on lower volumes?

Im on a d802.

btw as far as i know, on stock lg roms, the value on speaker rx7 on the mixer_paths file (unedited) is also 60 right? If this is correct, then we can already come to the conclusion that there is some problem with the speaker volume because if both stock and cm13 have a value of 60 and stock sounds way higher at max volume than cm13 then there is clearly something wrong. Unless stock rom comes with a higher value of the rx7 speaker in the mixer_paths file
[G2 Original Android Development] berlen:
Hello everybody! I just switched to cm13, I have a couple of questions:

how to flash supersu? if I flash it as I used to do in cm 12.1, I am not able to boot (a message on the lg boot screen states that there is a conflict with secure boot or something).

Also, before flashing cm 13, I tried to update twrp recovery to v3 while on cm12.1, I had bump kk bootstack. But I could not boot in recovery at all, I got a black screen and I ended up hard bricking! How to install last version of twrp?

Thanks
[G2 Original Android Development] stayhc:
Dont flash supersu or get bootloop, use in-build found in developer options

Enviado desde mi LG-VS980 mediante Tapatalk