yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] ravenhr:
I have finally flashed CM13. So here are my two cents:

- hissing in headphones is here, but barely noticable (for me, I can't tell for everyone)

- LTE works. Stable.

- WiFi works. Stable.

- BT works, but I don't know for Wear devices, as I have none.

- No random reboots, no BSOD, no flickering, no lags...

Only "problem" I have is a bit faster battery drain than on flashable stock, but it isn't big and it isn't that much of a problem. Oh, yes - i got almost 43000 on AnTuTu - which was IMPOSSIBLE on any previous ROM (stock KK, stock LP, CM12.1, Fulmics, Euphoria 1.1, stock MM). So, I think this is BEST ROM ever for my G3. [MENTION=4574857]finnq[/MENTION] - Thank You.
[G3 Original Android Development] superawesomeme:
Thanks. I've read different reports on different devices where AP either works, works if you disable root or just doesn't work. So thanks for confirming, I know not to waste my time trying it when it launches now. It's a shame but I'd rather go without than use LG Stock.

I've heard it works with AOSP ROMs so I might try XenonHD when AP launches. Who knows though, this one may support it by then.

---------- Post added at 09:21 AM ---------- Previous post was at 09:18 AM ----------

How's your volume in general? On CM mine seems to be about half of what it is on LG Stock, either speaker, headphone or BT.
[G3 Original Android Development] ravenhr:
Volume is fine IMHO.

And about Android Pay - there is Xposed module that helps - Root Cloak. It "cloaks" root for select apps (you can select yours also)... But, you have to install Xposed framework for it.
[G3 Original Android Development] reeep:
With the latest nightly editing COMP1 Switch in mixer_paths.xml is still necessary for (somewhat) clean sound when listening to music.

Can anybody explain what "COMP1 Switch" does and why it affects audio quality so much? I haven't noticed any functionality loss when setting it to 0, so I'll continue to do so, but if CM sets it to 1 even when many people confirm that it fixes their sound it must be important...
[G3 Original Android Development] Windforce0511:
I have 54000 Antutu score on stock...
[G3 Original Android Development] bamiasHELLAS:
Flashed 1-3 this morning on my D855, so far hissing seems to be gone forever! Also battery life seems better, but marginally.

Thanx dev!!!!!
[G3 Original Android Development] takis:
Guys volume isnt fixed fully... Hissing is there but lower... Volume in general is lower imo
[G3 Original Android Development] splitsch:
[MENTION=4574857]finnq[/MENTION]

Today's rom (20160301): the hissing sound has disappeared, but there is still a static noise, much lower, with my k450, with my shure se102 : the sound is ok.
[G3 Original Android Development] agritux:
is anybody using audiofx ? i have never used it but it is exist since the begining of the cm :) if someone using audiofx, please suggest me the best settings for D855 and CM13

i searched about viper4android and saw that it is very popular.

is there any differences?
[G3 Original Android Development] finnq:
Please tell me what headphones you use and when exactly you hear the noise. Which volume? Is there a song with which it is extremely noticeable?

I tried it with the supplied headset and another in ear pair. Can't hear any hissing/noise. The sound isn't as clear as with my sound system but meh it's a smartphone with a crappy headset...

So, first of all, just because CM does it, it doesn't mean that it is always right. :p In this case COMP means compander. Companding is used to decrease the signal-noise ratio.
[G3 Original Android Development] splitsch:
[MENTION=4574857]finnq[/MENTION]

I use SHURE SE102 : http://www.whathifi.com/shure/se102/review

-> No bad sound, no hissing, static, etc : perfect.

I use AKG K 450 : the hissing sound on the left ear was present until today's build.

The static noise is still present in both ear, whatever the volume, and whatever the type of music. The static volume is exactly the same, whatever the sound volume. The static sound is still present, even if I mute the sound in google music app (or any other music app (youtube,...), or even if the button-press should play a sound, outside any app (in the drawer screen, e.g.)).

If I pause the music, the static disappear after about 3 seconds and start over when I press play.

I hope it helps.

What test protocol can I do to help you narrow this bug down ?

Thank you

Splitsch
[G3 Original Android Development] takis:
False alarm with clean flash it seems to be alright...
[G3 Original Android Development] scsgoal31:
I really feel this (http://review.cyanogenmod.org/#/c/134496/) commit missed the mark. I use a 6x6 grid (without the search bar) and the large icons fit perfectly on the screen. Now, my icons are much smaller with a ton of space around them.
[G3 Original Android Development] superawesomeme:
Just installed 20160301 nightly and can't notice the hissing although only tested with my old Apple ear buds from my old iPhone. Not sure about the volume in general now, it's hard to tell, I'll have to open a few videos and play a few songs to test it later.
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] can you implement the awsome work done by [MENTION=4791767]YaDr[/MENTION] regarding the proximity sensor functions in official cm13 so that every g3 user has it? With the mans [MENTION=4791767]YaDr[/MENTION]) permission of course...
[G3 Original Android Development] SpitFireXB360:
[MENTION=4574857]finnq[/MENTION]

Can you please fix audio routing?

With headphones plugged in, the alarm from the alarm clock plays through headphones only not trough speaker...

Thx.
[G3 Original Android Development] finnq:
[MENTION=2970004]SpitFireXB360[/MENTION] Fixed.
[G3 Original Android Development] takis:
Like what i see in cm13 changelog... What about my suggestion mate?
[G3 Original Android Development] finnq:
[MENTION=5883369]takis[/MENTION] I don't know what he did with the proximity sensor. And of course if we merge it we need his consent. Do you have a link to the corresponding commits?
[G3 Original Android Development] takis:
He fixed all the proximity problems the cm has... Phone doesnt wake when proximity is covered and the screen doesnt stay black during calls... I dont know what exact commits he has used but i believe thst you should pm him and ask for his permission as it is a fixable bug thanks.:good:
[G3 Original Android Development] finnq:
We're working on a fix for this too. All fixes we've seen so far were quite ugly.
[G3 Original Android Development] takis:
It works pretty good... Hope we see yours soon ...:fingers-crossed:
[G3 Original Android Development] finnq:
[MENTION=5883369]takis[/MENTION] Yeah, I'll look into his one. It's so crappy that I think there will never be a really clean fix for it :P.
[G3 Original Android Development] takis:
Fromwhat i understand he did the following... Enabled the proximity sensor to check whether its covered or not and if it was the phone could not switch on by power button or by double tap to wake... Regarding the in call black screen issue. He disabled the proximity during the call so that dt2w doesnt actually lock the screen without being able to turn it back on ... I know i didnt fully understood what he did (i am not a dev anyway) and thus i suggest you to contact him.... He is a very good guy and i think he will guide you...:highfive:
[G3 Original Android Development] paulogomesds:
:)

I am using the stock ROM 30b Bumped .. If I install the CM13 above it will have problems with EMMC Bug?
[G3 Original Android Development] :
Well, my fixes aren't the cleanest ones. The second one is quite dirty.

I've solved two problems:

1) double tap to wake stopped working after first wakeup rejection. Fixed by a kernel patch. It's clean enough, and it works. The only things that need changing are declarations - i think it will be better to move them to a header file.

Truly "clean" fix will require implementing a callback mechanism from PowerManager. This way we will avoid free->busy->free->busy transition that happens with the current setup. However, the time required for panel to suspend or wake up is so short, that implementing any kind of callback is just not worth it.

2) Camera wakeup gesture didn't check for proximity sensor readings. This is where things get fugly...

"Fix"

Notice the quotes. This is a -very- dirty fix, that, however, works in all usecases i've tried.

I do intend to refactor this code; however, the idea (Check the proximity after first keypress; use the results in wakeup and camera gesture procedure) will not change - i don't see a cleaner way of doing this.

Edit: oops, broken commit. Pushed updated version, changed link.
[G3 Original Android Development] diverfish:
Pairing with Gear s2 still not working :(
[G3 Original Android Development] Trhanec:
Nightly 20160302 - pairing with Pebble Steel still not working and the bluetooth address is 00:00:00:00:00:00. Last functioning nightly 20160221.
[G3 Original Android Development] agritux:
[MENTION=4574857]finnq[/MENTION] with today's nightly sound level is great! i have no problem with CM13 at all. Thank you very much!
[G3 Original Android Development] ravenhr:
WOW! I never passed 40000 mark on stock! That is incredible score!

I'm happy with 43000 points, but yours is just freakin great (IMHO).
[G3 Original Android Development] reeep:
I managed to record the output of my KSC75 by putting them directly against a decent mic. Compare with COMP1=1 and 0:

http://wikisend.com/download/434456/test-comp1-one.wav

http://wikisend.com/download/603168/test-comp1-zero.wav

Notice the weird background static noise with COMP1=1? It's quite annoying, and even more noticeable with headphones (happens with all headphones I own...).
[G3 Original Android Development] takis:
What build?
[G3 Original Android Development] reeep:
This morning's 20160302. Since a couple of nightlies ago things have improved regarding hissing and low volume, but I still have that weird distortion/noise you can hear in my samples with today's nightly. I didn't touch the headphone or the mic while editing the file or rebooting the phone, so the samples were taken in *exactly* the same conditions, with a difference of one or two minutes. As you can hear, setting "COMP1 Switch" to zero gets rid of the noise.
[G3 Original Android Development] Windforce0511:
Biggest problem for me - screen won't turn on when I finished a call. I heard lock sound in call and after that I have to manual turn it on
[G3 Original Android Development] finnq:
Please give me your build version and a logcat of the pairing attempt.

Check if the file "/data/misc/bluetooth/bdaddr" exists and contains your mac address. If yes please execute the file "/init.qcom.bt.sh" and send the the output.
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] this is fixed with the [MENTION=4791767]YaDr[/MENTION] s solution
[G3 Original Android Development] scsgoal31:
I have a (possibly) similar issue with pairing with my Fitbit wearable.

The Fitbit connects at two different "levels" depending on some things. To simply sync steps/heartbeats/sleeptime/etc., the device utilizes something less than a full-pair (the Fitbit won't show as paired in the Bluetooth settings of the phone). I assume this is done strictly via BLE. If you want to connect the Fitbit so that call/text notifications are shown on the Fitbit, a full pair occurs (now showing in the Bluetooth settings of the phone).

The issue that has existed since CM13 was first built for the G3 is that at the first level (BLE-Only), syncing works great. However, once you choose the options to show notifications on the Fitbit, all syncing breaks and the devices no longer talk to each other.

Let me know if you'd like some logs of the above scenarios?
[G3 Original Android Development] mrjayviper:
Does Bluetooth work? Need it for my earphones. Thanks
[G3 Original Android Development] afilbit:
Having the same issue with sdcard. It doesn't go higher than 20%. I formatted it on my pc and all but always the samething. Anyways getting a great experience with this ROM. Stable enough for daily driving in such a early stage.

Another thing: How can I resize the nav bar? I always resize it in other ROMS but cm doens't have this feature built in and the navbar is just too big. Thanks!
[G3 Original Android Development] hemo87:
Go settings > Search for "Assist & voice input" > tap Assist & voice input > tap Assist & voice input again > tap assist app > select google app > tap settings gear > enable on tap

Should be all working then.
[G3 Original Android Development] :
Wifi cause battery draining, why you know that. My battery drain faster than stock ROM
[G3 Original Android Development] Benny100:
BetterBatteryStats not Working

Wackelock Detector not Working

Root problem of CM13?

Rootchecker status OK!
[G3 Original Android Development] amirhashim:
Same here
[G3 Original Android Development] Mindoy:
Yes. I use mine for spotify
[G3 Original Android Development] raghavsharmaxda:
Yes THIS. thank you so much.I wonder why it wasn't working normally but meh :P

BTW , a small bug which is weird coz I ain't facing any now except that one(major), play store works proper but if I install multiple things or stay on it for long , it FCs.. It's a clean install.
[G3 Original Android Development] briefer:
Terrific ROM! It is flawless so far...

just some localization missing in the setting for Spanish, but so far zero errors.

Thank you and keep the good work!
[G3 Original Android Development] EmptySD:
Same here. At the moment i am using phone without SD card.

Tried to format as internal storrage, as external storage and problem happen all the time. Even if i resized that 15mb partition up to 16gb, phone start to freeze and almost all app's FC.
[G3 Original Android Development] DsTroX:
Seems like 802.1x authentication is not working
[G3 Original Android Development] ravenhr:
I have one problem. In Cell networks, I'm stuck on LTE, but it seems it doesn't get me LTE network, just HSPA...

Guy sits next to me, with his Note 3, my SIM and LTE works flawlessly... Any idea why it acts like that? Anyone with similar problem?

One more thing: *#*#4636#*#* under Phone info gives me several options for preffered net type, but it doesn't make any switch, it is stuck on LTE/GSM auto (PRL).

Almost forgot: this is clean install, everything wiped, then made fresh install. Dirty flash just produced errors (no wonder, though), so I made clean one.
[G3 Original Android Development] Tchiort:
The function which enables us to select preferred networks doesn't work yet, we pointed it out early on.

I, also, am not able to switch to 4G and an stuck to HSPA.
[G3 Original Android Development] ravenhr:
Is the problem just switch, or it doesn't connect to other network type? Eg. if I'm stuck on LTE, should it connect to LTE, or this just shows any selection, without switching to that type?
[G3 Original Android Development] Abaddon:
for now. all MM roms on g3 can't choose/select network type or your preferred one. its default to gsm/wcdma/lte or lte global. i think its ril related. dunno yet. that's why it shows baseband unknown. will be fixed either soon or later. :)
[G3 Original Android Development] SimboXXX:
Haven't read anyone else with this problem but it's happened to me twice now, on last nightly and on another CM13 based rom - the UI crashes when I'm messing about with the Quick Stttings panel, The screen goes black apart from back button and status bar. Phone is still operating but nothing will get the UI to restart, not even a reboot.
[G3 Original Android Development] derekoh:
I had the same issue, but mine was stuck on 2G after dirty flashing from CM12.1. I flashed back to 12.1 which then would boot loop, so I then re-flashed 13 and it now seems to work fine.
[G3 Original Android Development] soblecram:
clean flash, no restore from TiBu, GPS not working at all, Bluetooth forgets connections on reboot.. Other than that , rock solid (until I tried to install a CM12 theme and got SystemUI F/Cs
[G3 Original Android Development] Abaddon:
be wary on installing cm12/12.1 themes. make sure they're updated and made compatible to cm13 or else you'll get systemui fc. if you encounter it again. just delete theme folder in /data/system and delete the app and its contents in /data/app
[G3 Original Android Development] :
[MENTION=2524903]finng[/MENTION] I think you should compile 2 builds: 1 for 3GB RAM version and 2GB RAM version. Because system in 2gb RAM eats over 800Mb its too much. I checked another devices with 2gb RAM run CM rom, system just eats 500mb RAM. Stock G3 have 2 builds too: for d855 16gb and 32gb
[G3 Original Android Development] takis:
Finnq can you just merge it mate?
[G3 Original Android Development] dueiza:
Is EAP SIM work on this build?
[G3 Original Android Development] Windforce0511:
How how how ?!
[G3 Original Android Development] jesus bermudez lara:
Does NFC work?

NFC isnt working for me, it lets me turn it on and off but it doesnt work.
[G3 Original Android Development] c-non:
I think stock color values better than cm13, can someone post stock color values ? Also i love and want to use sharpening stock value(40) with cm13, i tried sharpening mode 3.5 flash via recovery but it didnt work, is there any other way ?
[G3 Original Android Development] takis:
You cant do it yourself you will have to wait for [MENTION=4574857]finnq[/MENTION] to merge the commits
[G3 Original Android Development] Trhanec:
exists but contains address 00:00:00:00:00:00
[G3 Original Android Development] Windforce0511:
Link or something? Thank you
[G3 Original Android Development] S.AMU:
So if we go and set the variable to 60min we would have a really dirty fix, but only have a GPS lost each hour.
[G3 Original Android Development] jeremie57:
No, not a dirty fix. Without A-GPS, I receive the first fix generally in less than 30s. Sometimes, depending of the weather, it can take 2 min.

But, when the device has downloaded the ephemeris from the sattelite, the fix is done in less than 10 s.

With datas activated, The first fix time is less than 10s.

How can I change this value ? :confused:
[G3 Original Android Development] takis:
Just wait for his answer just like i do
[G3 Original Android Development] Loknic4:
Latest nightly 2/3/2016 something is mess with AudioFX. Headphones and speakers are replaced. When I put headphones, effects work but for speakers. :/ wird . Can someone confirm?
[G3 Original Android Development] Trudi:
It happens on any low volume music, for example with Dire Straits song "Private Investigation" with any decent headphones except the very crappy ones that are provided with the phone. I've tested it with my everyday use Bose QC25, it happens also with my monitoring headphones Beyerdynamic DT 770. I've tested with some friends equipment like a Marshall Major or a Sennheiser Momentum, or some low cost Philips SHL3105. I think this happens with any audiophile equipment actually. Bad quality equipment like the original headset provided with the G3 has a too low impedence to be able to hear the hiss.
[G3 Original Android Development] :
Lockscreen not working? Anything happen in the last nightly?
[G3 Original Android Development] youssefkr:
Can you please explain a little more your problem ?
[G3 Original Android Development] lokize:
IR Sensor working? Thanks!
[G3 Original Android Development] :
This is what's happening...
[G3 Original Android Development] NichyXD:
Camera is good as the stock rom?
[G3 Original Android Development] youssefkr:
Yes IR sensor is working.

---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------

No camera on aosp/cm Roms can never reach stock quality, but it's not that bad IMO. No 4k , 1080p60fps, slow motion recording though.
[G3 Original Android Development] lokize:
what app do you use to sensor IR? i use zaza remote and sensor google44 and not working :(
[G3 Original Android Development] youssefkr:
I use smart IR remote anymote.
[G3 Original Android Development] lokize:
led display for IR don't work :(
[G3 Original Android Development] c-non:
No problem with camera app but camera brightness very low with tango app.
[G3 Original Android Development] Meneldur:
I tried NFC yesterday with a tag and worked fine. Using 20160302.

Mnldr/D855/16G/CM13

---------- Post added at 07:12 PM ---------- Previous post was at 07:09 PM ----------

I've been using it with Peel Remote since last year. [emoji4]

Mnldr/D855/16G/CM13
[G3 Original Android Development] GunshinFU:
Overheating until shutdown when using gps... Managed to reproduce using maps for extended time. Does not seem to happen when GPA is turned off. D851 most recent nightly 3/03
[G3 Original Android Development] youssefkr:
When I try to install SuperSU my device run into a bootloop .. What can I do to properly flash it ? Thx
[G3 Original Android Development] Zatta:
Nothing, just use the build-in root manager which can be found under developer settings.

Verstuurd vanaf mijn LG-D855 met Tapatalk
[G3 Original Android Development] Windforce0511:
Which is faster than supersu btw
[G3 Original Android Development] seny92:
Spotify close by itself I don't know if it come from the application or memory leak, when I play SW (Summoners War) and run Spotify, Spotify close faster.

I tried to uninstall/install Spotify again but I got the same problem, I tried listening with bluetooth or cable headphone and got the same result.

13.0-20160302-Nightly-d855
[G3 Original Android Development] easy_ci:
Somebody who can say something about SoT with CM13 atm?

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] rembi94:
Hi, i came back to stock Marshmallow and mobile data is not working. On any other ROM mobile data is not working :C It's only working on CM13 Nightlies. I'm from Poland, using T-mobile card. Any solution?
[G3 Original Android Development] jayce996:
Hello guys,

I went through the thread to find feedback from users who have tested both CM13 & Fulmics ROMs, but i didn't find it clearly.

are there any ways to recover some of the added values of the stock/fulmics rom such as knock-Knock, all photo drivers/enhancements

i'm not looking for the Q-things nor the LG apps.

the battery is not very good from my point of view on the Fulmics ROM, is it much better or equal on the CM13?

one thing that i really love is the UserProfile thing allowing to change the parameters (Wifi, BT, display, sounds, ...) based on some triggers (location, connection, etc) on the CM ROM.

In terms of performance, is there any difference or are they equal? Is Nitro-X supported?

last thing, is it possible to move from Fulmics to CM without having to remove everything or not?

Last question, is this CM nightly build stable enough for an every day usage?
[G3 Original Android Development] agritux:
Anyone know which IR app can learn manually?

i tried many app but can not find anything.
[G3 Original Android Development] diogo.sena:
Just the lg quick remote.