yashsingh1/xdaforums huggingface dataset:
[G3 Original Android Development] prgprg:
I have the same problem but my phone is stuck on LTE instead of 2G. I was on lte in cm12.1 when I clean flashed cm13
[G3 Original Android Development] EthericGhost:
Bro its under Sound/ other sounds/ vibrate on touch
[G3 Original Android Development] rockY.:
I've just installed the latest build on my G3 D855 16GB variant and I have to confirm that for me, everything works perfectly. I haven't encountered any bugs or errors so far. Network, 3G/4G, WIFI, double tap 2 wake, camera, apps... everything works flawlessly. I came from CloudyG3 2.5 ROM so I obviously did a clean install along with Open GApps pico variant. Great work finnq, thanks a lot! I can't wait for future builds.
[G3 Original Android Development] Sorin90:
Camcorder isn't working for me. Known bug?
[G3 Original Android Development] mo120697:
Me too bro
[G3 Original Android Development] spanorg:
Excellent build for the time...

Bug: There is battery drain related to wifi...
[G3 Original Android Development] 0nebukadnezar0:
Hi,

first, big thanks to finnq for his great work!

I have exactly the same issue with a 64GB Samsung SD-Card (EVO white/orange), which works great on CM12.1.

After the wizard is trying to format the card (20%...) a Java error shortly appears, and the wizard stop to work. If you put the card on a PC, 2 partitions are created, one with 16MB FAT32, the second one with the rest of the space but without formatting.

I have tried to format the 2nd one also with FAT32, but it didn't worked. Have also tried with one FAT32 partition, as logical or primary, but also not successful, the message "Corrupted Samsung SD card" always appears again and again... then the Set up your Samsung SD card starts again and again.
[G3 Original Android Development] tallman43:
Working fine for me on D855 have you got the latest build?
[G3 Original Android Development] skrippi:
I don't have any micoSD reader for PC. What else could I do?
[G3 Original Android Development] afilbit:
Don't know if it is a little off topic but which custom kernels work with this ROM?
[G3 Original Android Development] binlalo:
I had the same issue and ended up buying one (2 euros so not a biggie) but maybe someone here knows any other way to solve it.
[G3 Original Android Development] marmo:
I'm getting the same issues, no matter which way you format the sd. It is always stuck on 20% When choosing internal storage.

Also the phone gets laggy when sd card is inserted as external storage. My version is D855 32Gb
[G3 Original Android Development] Ernesto0023:
You´re awesome dude, everything :good:
[G3 Original Android Development] Yonatanl2:
Anybody else experiencing a problem with Privacy guard that it asks for root permissions for every apps after each boot?
[G3 Original Android Development] skrippi:
Which is the best way to update the nightly?

Only wipe cache & dalvik? Or do I have to format system or something?

My order is always: Wipe Cache, Wipe Dalvik, Install CM, Install GApps, Reboot...

Is that good?
[G3 Original Android Development] DeathBoT:
Do you know if I can get this kernel for the VS985? Having the SAME issue but have the verizon version of this phone.
[G3 Original Android Development] Akatoikitos:
No need for any of that...

After downloading from CyanogenMod updates session,just press the install icon and the phone will automatically go to recovery,apply the update and reboot itself!
[G3 Original Android Development] raghavsharmaxda:
Google now on tap

Everything is apprantly working flawlessly. Although I realised eom got suddenly slow after something (backup after Clean install to be specific), over Ll performance is rrLly great :D I hsvebt faced Amy issues. (Yes option to change from LTR to something network doesn't work), but I don't have any problem with that.

But, google now on tap just isn't working. Nothing shows up if I long press home button (latest build 20151130).

Its cleanest install possible. SD card properly formatted to fat32 so no issues there.

Just this.

No rings(if they srenr in marshmallow then okay but still no now on tap). When I go in google> settings> now cards> turn on now on tap , google app force closes. After that it works (google app I mean) but this feature just doesn't.

Thank you for this ROM its almost perfect :')
[G3 Original Android Development] Akatoikitos:
Thats weird..

Now on tap works great here.
[G3 Original Android Development] Slothboy:
Sorry if this should be posted somewhere else, but the interactive CPU governor seems to be f?!%ed on our G3's running CM 12.1/13. Could you maybe look in to this? [MENTION=4574857]finnq[/MENTION]

If that gets fixed then I would definitely switch to CM13, the only reason I havent is because the only CPU governor that seems to not make the G3 laggy is Alucard on Euphoria OS with the 777 kernel.

It's also worth noting that performance is much better in terms of stability on Stock/Stock based ROMs like Cloudy and Fulmics, and they both use the interactive governor, weird huh?
[G3 Original Android Development] GunshinFU:
Randomly my phone overheated and shut down this morning while charging, to my knowledge nothing was running I simply felt it vibrate once which woke me as it turned off, it was blistering hot and would not turn back on for 5 minutes, anyone else having any thermal issues? Maybe 2/18 nightly will not have this issue.
[G3 Original Android Development] papaluigi:
Actually it's not nearly as good as it was on CM12.1. I can't get through the day with a full charge and get like 2.5 - 3 hours SoT. When I try really hard 4 hours and a few minutes are possible but not without a few tricks like disabling mobile data. I love CM13 and it's my daily driver but don't expect a great battery life.
[G3 Original Android Development] dimine:
Only low 5 GHz channels working with current kernel

Hello,

with current nightly 20160218 it is still not possible to see and therefore not possible to connect to 5 GHz channels that use channel numbers above 48, also tried clean flash. With an older kernel, for example 20151221, the higher channels do work.

G3 D855 Modem 21c with 20160218 nightly and 20160218 kernel:

AP using channel 36, can see and connect to it:

switching AP to channel 52, cant see it anymore:

Install older kernel 20151221:

Channel 52 visible and able to connect to:

Just for comparison, Nexus 9 with same nightly version:

Channel 52 visible with current kernel:

Does everybody use low 5 GHz channels or no 5 GHz at all? Cannot believe i am the only one noticing this problem :(
[G3 Original Android Development] dimine:
Sorry, i do not have the problem you describe, my wifi is working fine except for the problem that i can only see and connect to low 5 GHz channels. After toggling airplane mode on and off, my wifi returns as expected.
[G3 Original Android Development] [deXter]:
Thank you - but when you're in the WiFi settings, can you see both 2.4 and 5GHz networks in the same screen, or does it only show one type?
[G3 Original Android Development] dimine:
Yes, i can see both, as long as the 5 GHz ones are on a low channel :rolleyes:
[G3 Original Android Development] [deXter]:
That's really odd - on my D855 21c, I can see and connect to my 5GHz network, channel 149. But of course, it's still subject to the wifi bug I mentioned earlier - if I turn airplane mode on/off, it won't reconnect automatically. Sometimes it won't connect at all, and I need to reboot, or go to settings, switch to 5GHz, and switch back to automatic. But when I'm able to get it working, I can connect to my channel 149 network.
[G3 Original Android Development] GunshinFU:
Random reboots

Phone started randomly rebooting when accessing contacts app, managed to reproduce but not every time by opening contacts and going from favorites to all contacts tab closing and reopening, eventually all contacts vanish the phone slows down then restarts on its own, haven't had this issue until I installed 2/18 update.
[G3 Original Android Development] Ante733:
Hello..does anyone has problem with microphone when speaking during phone call? I installed CM13 and all updates since 10.02 but always the same..the other side can hear me but on moments cant, and she hearing like water in the phone..i hear well all time..anyone? I have lg g3 and CM13 for MM 6.0
[G3 Original Android Development] paulogomesds:
Slimport

The SlimPort adapter is working on this rom?
[G3 Original Android Development] takis:
[MENTION=4574857]finnq[/MENTION] any progress? Stock does not have just checked...
[G3 Original Android Development] dimine:
It seems with current kernel wifi is not "switched" to the selected country, so it does only allow low channels that are allowed all over the world.

Kernel log output after boot with current kernel:

root@d855:/ # dmesg|grep -i crda
[ 0.258817] cfg80211: Calling CRDA to update world regulatory domain

Kernel log output after boot with 20151221 kernel:

root@d855:/ # dmesg|grep -i crda
[ 0.201365 / 01-01 00:00:00.190] cfg80211: Calling CRDA to update world regulatory domain
[ 26.622922 / 02-19 13:35:42.773] cfg80211: Calling CRDA for country: DE
[ 29.782924 / 02-19 13:35:45.933] cfg80211: Calling CRDA to update world regulatory domain
[G3 Original Android Development] mistercheese:
Anyone else have a bug with sending recorded video via whatsapp not working?
[G3 Original Android Development] invisiblek:
^^^ THIS ^^^ is what we should be seeing in

development

forums. Nice work ;)

I had a hunch about this yesterday (don't actually have a 5ghz router to test with but I suspect some of my neighbors are on 5ghz because my victara can see more APs than my g3)

This was my hunch: http://review.cyanogenmod.org/#/c/133438/

Although I'd prefer to be a bit more surgical than just dropping LG's puke on top of our pretty new caf kernel.
[G3 Original Android Development] youssefkr:
Hey guys what are the main bugs with cm13 ? I couldn't find anything in OP
[G3 Original Android Development] Slothboy:
eMMC brick for most users but that might be fixed by updating to latest LG Stock release before installing CM13.
[G3 Original Android Development] JDMpire:
"Bluetooth share has stopped" error messages appearing overlapping each other by the dozens (hundreds... more?!?). Hard to get rid of the message sometimes.

I think it has been fixed in the most recent nightly for some G3 variants. However I still get it occasionally with my d851... YMMV.
[G3 Original Android Development] Sainzgc:
Problem in HDMI slimport still, doesnt work in cm13… tips?
[G3 Original Android Development] youssefkr:
Hey guys can anyone tell me what the emmc bug is ? I flashed cm13 today without any problem .. Is there a chance that my phone will brick ?
[G3 Original Android Development] tomerd78@gmail.com:
WHEN MOVING FROM CM 12.1 TO 13. Any chance getting the emmc bug?
[G3 Original Android Development] dcop7:
Yes. Check this post:
[G3 Original Android Development] youssefkr:
Hey, does emmc bricked devices can easily be unbricked by flashing the latest KDZ image ?
[G3 Original Android Development] archcry:
Just a little update on this, I haven't had the EMMC bug for about a month now, so it does seem to fix the EMMC issue.

Mostly yes, but some people report that their device was bricked to the point in which they could not enter download mode.

So if you want to try and do it please, please, please, please make a backup of you EFS partition, otherwise your IMEI might be gone!

In case you hardbrick your phone follow this tutorial

Otherwise you can simply flash the KDZ which was the case for me.

EDIT:

Following my previous tutorial which covers updating your phone to the latest LG patch might be safer and help you avoid the issue alltogether though.
[G3 Original Android Development] tschmid:
Try search the theory was explained many times.

Gesendet von meinem LG-D855 mit Tapatalk

---------- Post added at 02:47 PM ---------- Previous post was at 02:45 PM ----------

If youve the emmc brick flashing kdz isnt possible cause you havent the download mode. In g3 forum is a thread how to unbrick g3 models

Gesendet von meinem LG-D855 mit Tapatalk

---------- Post added at 02:49 PM ---------- Previous post was at 02:47 PM ----------

Btw backup efs is better but in case you havent is possible with some tuts in inet

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] dimine:
Thanks :)

I compiled a kernel with your change, but it had no effect. I am not sure if this file is used at all, see kernel config explanation:

config CFG80211_INTERNAL_REGDB
bool "use statically compiled regulatory rules database" if EXPERT
default n
depends on CFG80211
---help---
This option generates an internal data structure representing
the wireless regulatory rules described in net/wireless/db.txt
and includes code to query that database. This is an alternative
to using CRDA for defining regulatory rules for the kernel.

For details see:

http://wireless.kernel.org/en/developers/Regulatory

Most distributions have a CRDA package. So if unsure, say N.

And this option is not set, it was not set in the old kernel too, so that cant be the source of the problem.

This seems to be a good read about it, it suggests adding something like COUTRY=DE to wpa_supplicant.conf, but that did not work, too.

If i get it right, there is a new version of the wireless driver in the current kernel named bcmdhd_g3? Maybe the problem is somewhere with this driver. You can find stuff about regulatory domains in this driver file: android_kernel_lge_g3/drivers/net/wireless/bcmdhd_g3/src/wl/sys/wl_cfg80211.c

I temporarily fixed my problem by editing this file: android_kernel_lge_g3/net/wireless/reg.c

At line 131 the world_regdom gets defined and most of the 5 GHz channels are missing there. It seems, it wont get overwritten with country specific settings in the current rom.

I replaced it with parameters suitable for germany and recompiled the kernel, now i can see and connect to all 5 GHz channels again.

/* We keep a static world regulatory domain in case of the absence of CRDA */
static const struct ieee80211_regdomain world_regdom = {
.n_reg_rules = 4,
.alpha2 = "00",
.reg_rules = {
/* IEEE 802.11b/g, channels 1..11 */
REG_RULE(2412-10, 2462+10, 40, 6, 20, 0),
/* IEEE 802.11b/g, channels 12..13. No HT40
* channel fits here. */
REG_RULE(2467-10, 2472+10, 20, 6, 20, 0),
/* IEEE 802.11a, channel 36..64 */
REG_RULE(5180-10, 5320+10, 80, 6, 23, 0),
/* IEEE 802.11a, channel 100..140 */
REG_RULE(5500-10, 5700+10, 80, 6, 30, 0),
}
};
[G3 Original Android Development] Slothboy:
When you say latest LG release, is that 30B? Or 21C?

Because my phone came with Lollipop and I never had the eMMC problem (But went to Fulmics just to be safe when word started spreading about it)

I have the 21C modem currently with TWRP 3.0, in theory I should be fine right?
[G3 Original Android Development] archcry:
I mean this version:

Android Version: 5.0

Baseband Version: MPSS.DE.2.0.1.c1.13.2-00002-m8974AAAAANPZM-1

Kernel Version: 3.4.0

Build Number: LRX21R.A1445306351

Software Version: V21a-EUR-XX

So yeah you should be fine I guess.
[G3 Original Android Development] finnq:
The bcmdhd_g3 driver isn't used in the international d855 variant as it is only for broadcom devices. Our variant uses the qc wcnss platform. The associated driver is called prima and located at drivers/staging/prima.

Another thing: In tomorrows nightly the bluetooth mac address should show up correctly. Please report if it works :).
[G3 Original Android Development] youssefkr:
Hey guys, I really really want to try cm13 but I can't afford to lose my second phone this month.. I mean what are the chances that my phone will hard brick because of the emmc bug ? thanks. D855 16Go user
[G3 Original Android Development] FooFighter312:
Please read through this thread because many people have already asked the same question (and it was already answered). Basically, if you're upgrading from CM12.1 then you have a pretty good chance of getting the emmc bug. If you upgrade to stock Marshmallow and then flash CM13 you probably won't get it.

I was on CM12.1, then on stock Marshmallow, then on CM13 and nothing bad happened.

But do have in mind that whatever you do you're the one responsible. If you don't want to brick your phone the safest thing to do is not mess with it at all.
[G3 Original Android Development] youssefkr:
I already read through the thread but haven't found my answer.. Anyway thanks for your reply
[G3 Original Android Development] c-non:
Hello devs. gpu governor changing cause power off problem, when i change gpu governor to simple_ondemand device power off, not opening since i remove and set battery than power on button.
[G3 Original Android Development] DutchPlayer29:
Whatssup guys! Love the CM13 rom, flashed from stock to CM13, from 13 to 12.1 and now back to CM13 cause some function work better in the latest CM13 version.

I've searched this topic but what do we know about the audio jack problems and the annoying noise when listing to music, problem doesn't exists when using Bluetooth headphones.
[G3 Original Android Development] bamiasHELLAS:
Hi, I noticed using cpu-z that when screen on and do nothing the GPU is stuck at 330mhz. If I like move the notification bar down it goes to 200mhz. Is this normal???
[G3 Original Android Development] c-non:
I think msm_adreno_tz very bad governor and lagging(i dont know but it can be about driver), this discussed in a lot of other device thread , i want to change governor for try another something but power off with other governors has bug, gpu heating because of gpu governor and thermal engine throttling cpu than lagging and performance degradation incredible with gaming.
[G3 Original Android Development] takis:
Do you mean the is a bug when governor isnt interactive?
[G3 Original Android Development] c-non:
I mean gpu governor not cpu, default gpu governor msm_adreno_tz and it is very bad ,also if you want to change to simple_ondemand device power off.

Also the main problem thermal engine, it is throttling cpu to 1728 mhz on 50 celcius, with normal usage cpu jump 50 celcius generally, if you gaming cpu can down 1100 mhz by thermal engine and performce get down.
[G3 Original Android Development] Teemoo:
Using 21/02/16

IR blaster is usable without using LG framework or something like that, I've tested it with the application TV KILL, it is on f-droid.

org.twinone.irremote also works. I've got the apk from a shady website, but it works. Could anyone download the apk from google play store and share with me?
[G3 Original Android Development] Akatoikitos:
I use Peel Universal Remote TV Guide from Playstore and is working great!
[G3 Original Android Development] GunshinFU:
I am also having thermal issues when gaming and charging, also noticed if you leave a game running in the background but are not playing it the GPU still remains under massive load until throttling/power off or you close the program completely, not sure if the thermal problem when charging is related but I do not have this problem with stock ROM.
[G3 Original Android Development] archcry:
Just install the stock android ROM from LG and patch it up to build version LRX21R.A1445306351.

Then use the guide I previously posted in order to root and flash recovery.

When you're done with that flash CM13 and Gapps.

If you do it like this your chances on getting the EMMC bug are nearly 0% as far as I tested (I havent had emmc issues for 1 month while it would usually occur within hours)

I hope this is the answer you're looking for, it will not get more specific then this for the moment.

Edit:

Guide

~ Archcry
[G3 Original Android Development] essentially_mia:
You flashed TWRP straight from their website, or do you have a "special" bumped version?
[G3 Original Android Development] android bunny:
can i flash this rom from stock kitkat ?
[G3 Original Android Development] podkilla:
afaik this is not recommended. flash MM kdz first then CM13.
[G3 Original Android Development] takis:
Yss the other governors seem to be broken
[G3 Original Android Development] djdeeles:
on stock rom broken too...
[G3 Original Android Development] takis:
Testing now if thats the problem... Staying with interactive for some time...
[G3 Original Android Development] HAPPYFATHER:
Good work, it worked for my LG G3 D855 perfectly. Will there be any builds for my another G3 D858HK with Marshmallow?
[G3 Original Android Development] takis:
Sound problems i am still facing

1) constant hissing when using headphones

2) volume is much LOWer than stock

3) in call volume cant be changed at all (this only happens sometimes)
[G3 Original Android Development] finnq:
[MENTION=5883369]takis[/MENTION] No more caller echo?
[G3 Original Android Development] takis:
Fingers crossed but there is no issue on 21 build... Hope you dont brake it hehe... The sound needs major improvment tho...
[G3 Original Android Development] finnq:
If it works then the new calibration blob fixed it. That'd be nice.
[G3 Original Android Development] takis:
When was this implemented? Btw do you have a plan on the sound/volume bugs :confused:?
[G3 Original Android Development] tschmid:
You can flash it from twrp side or with flashify (download inside flashify)

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Original Android Development] stupink:
Bluetooth has forgotten a device (but seemingly left it hidden?)

I've tried to search, i'm sure I've seen someone else post similar but can't find it.

Essentially after flashing last nights build, my LG G-Watch wasn't connected, so I went to Bluetooth on phone, and more settings, oddly its now neither listed as a paired device(other things are still), nor is it showing as a "nearby" device... I had this with a motorolla earpiece some months back, but it didn't really bother me and it randomly popped back up.. my watch is 100% switched on and ready to pair etc..(and likewise cannot find a new device nearby, as its already paired to the phone, but not connected)

Is there a way to force-Clear all Bluetooth devices and start from scratch? or any other ideas what could be causing this? If I do it the watch end it factory resets the watch, which isn't ideal.
[G3 Original Android Development] dimine:
Thanks, i have compiled some kernels to test and searched orginal LG G3 30A sources for clues and differences to our kernel. In original kernel the kernel option "CONFIG_CFG80211_INTERNAL_REGDB=y" is set. In our kernel it is unset. I compiled it myself with this option set and it works, it is using the db.txt then that invisiblek stated above. Please do not merge the new db.txt from http://review.cyanogenmod.org/#/c/133438/, at least the settings for "DE" are worse than they were before. Official wireless-regdb seems to be linked here.

Original kernel also has the option CFG80211_ALLOW_RECONNECT set (ours has not), maybe it has something to do with the wifi drop problem some people have:

config CFG80211_ALLOW_RECONNECT
bool "Allow reconnect while already connected"
depends on CFG80211
default n
help
cfg80211 stack doesn't allow to connect if you are already
connected. This option allows to make a connection in this case.

Select this option ONLY for wlan drivers that are specifically
built for such purposes.

For me wifi seems to keep connected in deep sleep.

BT address showed up correctly(?) with current (20160222) and last nightly ...
[G3 Original Android Development] essentially_mia:
Do you have any partitions as f2fs? Couldn't reformat them to said file system after installing twrp 3..
[G3 Original Android Development] superawesomeme:
I've noticed this too but thought it was just me.
[G3 Original Android Development] eradicator006:
No problems here with TWRP 3 and f2fs. I use f2fs on my cache and data partitions.
[G3 Original Android Development] Ante733:
I have these too..the other side cant hear me well if i am 3 cm far from mic..
[G3 Original Android Development] bamiasHELLAS:
At least I don't have that issue anymore build 22-2 stock kernel, stock everything