yashsingh1/xdaforums huggingface dataset:
[G2 Original Android Development] ulihh:
Thank you very much! No, it didn't eat my hamster, but it dropped wifi at home on every rekeying this morning. I just had 30 minutes to test before going to work, so it's just 4 rekeyings so far. Now at work. We have multiple access points with the same SSID here and rekeyings on every hour. Let's see. What I tried is letting my d802 sleep when entering the office and waking it up 10 minutes later. It didn't connect to wifi while sleeping. This would be the best feature because it would then reconnect after a drop.

Mind making another test build with changes 140299+140300? I wanted to setup Ubuntu+Android SDK yesterday but my limited disk space on my working machine stopped me from doing so and at home time is the limiting factor.

Regards, Uli
[G2 Original Android Development] dr4stic:
I really hope you're on d802 and I hope this works for you. I don't want to make a habbit of making kernels for people.

You should just be able to flash this from recovery. I tossed the zip file quickly, it should probably work. If it doesn't, then unpack it, extract the boot image and then just flash that from twrp as an image file to the boot partition.

I shouldn't have to tell you to back up your existing boot partition before beginning.

https://www.androidfilehost.com/?w=files&flid=54153
[G2 Original Android Development] ulihh:
Thank you very much for your kernel. I know it's far too early for stable results but today I watched my d802 reconnecting to wifi automatically after a drop!

One drop happened at work, and while I was looking at the logs for some minutes I finally realized that the mobile was online again without any interaction. This is new.

After I came home I have left my d802 in sleep mode again and 30 minutes later I woke it up and it was already connected to my wifi! This is again new!

It seems there are still wifi drops but with automatic reconnects they don't hurt a lot. I will return later with more results. But I really love this test kernel.

Regards, Uli
[G2 Original Android Development] 4Freedom:
same for me:crying:
[G2 Original Android Development] Josh:
Anybody got drop calls? Somedays I've got it on my d802 with clean install on 0412 build with and without xposed . Also on the other builds. Maybe it happens because wi fi lost and also signal? And on two other calls when I've been on lte everything is ok. Any suggestions?
[G2 Original Android Development] Cyanosorro:
Yes, I also have constant call drops, mainly for calls 5 minutes long or more. I'm in release channel, with release 1 and I'm planning on returning to lollipop stock because a phone without good phone support...
[G2 Original Android Development] Borjuelo:
Hi everyone , I´m new in this forum and I came here with the idea that anyone could help my . First of all excuse me for my very bad english xD (im spanish) and cause Im a really "noob´" in this theme.

Well my situation is this : I have a LG G2 D802 , I was in lollipop stock and installed CM 13 , it works pretty well but everytime I update the rom I need to reinstall the Gapps , and my problem is the next : I updated the TWRP from 2.8.7.3 to 3.0.2 after that I can configure the Language and I think that all was working fine(I didnt need to reinstall the GApps) but when I try to enter in the recovery to install a microphone-fix I saw the CMod Recovery menu and not the TWRP recovery menu , so I think that I lost my TWRP recovery . In this situation can anyone say to me what can I do ?Dis I lost TWRP recovery forever? Thanks for your time and really excuse mue for my english level :P
[G2 Original Android Development] jl10101:
Since the latest WiFi commits (20160415) - WiFi dropping seems even worse unfortunately.

Edit: Seems to be settling a bit now. Restoring 50 apps.

Edit 2: Turned on data and left WiFi on before leaving the office. Went for a coffee, unlocked, and already had a notification waiting about the shops open WiFi connect. I locked the device, walked back to work, lay the phone on the table, unlocked 5 minutes later and it had switched from data to my wifi connection all by its lonesome. Very good sign. So far, so good!
[G2 Original Android Development] dr4stic:
What's the word on the kernel I posted a page or so back?
[G2 Original Android Development] jl10101:
Excuse my ignorance, but would this be different to the latest nightly? Or does it have more/newer/untried commits vs the latest nightlies kernel?

Also, thanks for your tenacity on all of this!
[G2 Original Android Development] jeebspawnshop:
Here it is;
[G2 Original Android Development] dr4stic:
Yeah, thanks. I suppose I completely missed that long post that said it would come back later with a longer more definitive post. Oh wait, I didn't.

Did you test the kernel? Do you have some thoughts? Exposure is key, you realize that, right? My WiFi is fine and I honestly couldn't care less about this issue. I don't need you to respond for other people here unless you live near them or something and are going out to check on them.
[G2 Original Android Development] DoubleDeuce22:
Delete
[G2 Original Android Development] qwertyu123:
The changes that are expected to improve or solve the wifi drops are still not merged, so it is completelly normal that there is no wifi improvement with todays build.
[G2 Original Android Development] jl10101:
Are you sure?

https://www.cmxlog.com/13/d802

I did follow up on my post with edits, so I'm not sure what you are calling out as normal?

Personally, I have seen a huge difference. Previously, I have flashed CM13, had 2 drops within 5 minutes, and restored a stock backup. I have been running the build the whole day without a problem. I am monitoring it though.
[G2 Original Android Development] qwertyu123:
As far as I know this is the change that will solve the wifi problems.

http://review.cyanogenmod.org/#/c/140300/
[G2 Original Android Development] jl10101:
Thanks for digging that up - I have seen this one. But whatever has been merged on the 20160415 nightly has made the difference for me. Perhaps it's not 100% and I haven't noticed, but I have been (sadly) obsessive about this bug and have been satisfied for the whole of today :)

Whatever is going on - I am sure it is in the right direction!
[G2 Original Android Development] ulihh:
Can you please tell if the patches from http://xdaforums.com/showpost.php?p=66350114&postcount=2788 were also applied to the test kernel (2 posts later)? I'm especially interested in the wifi background scanning patch, because I'm currently trying to find the differences between those two and atm it seems the auto-reconnections have started with #2788.

Are here other people also testing the kernels/builds? Please do so, and please report your results. We don't get the bugs fixed if we don't care.

Regards, Uli
[G2 Original Android Development] dr4stic:
They are patches to two separate components. The first is a rom set of patches (not in the kernel), the other is kernel specific. Combine the build with the kernel and you have all the patches I used put together.
[G2 Original Android Development] ulihh:
Thank you! Now I can confirm what I already suspected. The reconnections came with your test build in post 2788. It's not the kernel. The reconnections start with a line in logcat I never saw before:

WifiStateMachine: Fail to set up pno, want true now false

There's a difference with your test kernel (post 2790). wpa_supplicant reports reason=7 when wifi drops. reason=7 is just as senseless as the other reasons :D But the logging seems more reliable because now I can see what happens at a wifi drop at my work - it's not wpa rekeying but wpa negotiation (some lines including "WPA: Key negotiation completed" in logcat). These lines never appeared before. I can't tell if the better logging is kernel or testbuild related, sorry. I wonder why negotiations happen on an existing connection, but my wifi knowledge is limited. At least now we know the wifi drops are connected to rekeyings AND negotiatons.

The changes 140299 and 140300 don't break anythink as far as I can tell, so i strongly vote for them. But the wifi background scanning is more important because with background scanning we can turn on mobile data permanently - some minutes after a drop the wifi returns - finally! For a lot of people this would appear just as if the wifi bugs are completely gone. logcat still shows them.

Regarding the number of drops I haven't noticed any difference with any build and kernel so far. I couldn't test the new nightly because hunting the bugs is really a time-consuming task... sometimes I have drops every 10 minutes, sometimes it takes 8 hours for a single drop. Oh my god.

Regards, Uli
[G2 Original Android Development] jeebspawnshop:
If anyone wants to know what the reasons for disconnects are, check here: http://www.aboutcher.co.uk/2012/07/linux-wifi-deauthenticated-reason-codes/

For [MENTION=5726616]ulihh[/MENTION] it's reason 7 = Class 3 frame received from nonassociated STA

*shrug*
[G2 Original Android Development] ulihh:
Yeah thanks I already saw that and "*shrugged* also :good:
[G2 Original Android Development] dr4stic:
Ok... so based on your feedback, I +1'd the two patches we tested (I hope they'll get pushed soon enough). I also pushed through the wifi background scanning setting, that should come out in the next nightly (2016-04-16).

Based on the error type you're getting, it makes sense that the logs would be more stable with the background scanning turned on. The PNO is about network location and doesn't seem relevant. If you're on networks that want special authentication, it might be what's crashing your connection. I'm gonna go and look for options and settings that have to do with that.

I saw some settings for wifi firmware debugging, I may enable that and run a special build, but I'd need your help in running them and returning useful feedback. The most annoying part of all this is trying to get someone to actually test things. And since I don't have this issue, I can't test it myself. Remember, I'm flying blind.

The HTC One M7 and Samsung Galaxy S4 use the same wifi chipset (BCM4335), so I'm gonna compare some settings there.... see if anything is out of place.
[G2 Original Android Development] aaronDroid80:
Damn! 2 builds in one day. I'm glad the lock screen stuff appears to be fixed. Good stuff.

Sent from my gooey, toasty LG-D800
[G2 Original Android Development] Treboeth:
Does anyone know how to get the lg weather widget working on this. It's the only thing of lg's that I miss.
[G2 Original Android Development] dnsp:
Can't wait to test the next build.

"Enable wifi background scanning"

http://review.cyanogenmod.org/#/c/140795/
[G2 Original Android Development] Bisclavret:
Going through the tiles to check if LiveDisplay was put back again, I scrolled down to (+) something and BOOM it crashed. Was able to repeat it again and again. Nothing to say bad about the ROM this is something minor imo, but something to be checked.

[IMG="System UI crash bug"]http://i.imgur.com/r1gZZUl.jpg[/IMG]
[G2 Original Android Development] GalaxyGusta:
Guys I just clean flashed to the snapshot version and I'm still having the problem where when I was to view my full call history just when I click on the bottom to see in the phone app the phone app crashes...

Is there a solution for that? I really really need a full call log
[G2 Original Android Development] dr4stic:
If you did a clean flash, you shouldn't have a call log yet, unless you're restoring it.

Honestly, I don't see the issue, and I'm guessing it's because one of your databases within the dialer is borked. My call history goes back to some time in february.

I'd suggest doing a full backup from TWRP. Then, use some app to backup the call history. My preference would be the XML version from Titanium Backup (you only get XML's from the pro version), or MyBackup Pro. Then do a clean flash (factory reset + flash), or just do a factory reset... and set your phone back up from scratch. Then restore the xml based text backup.

HOPEFULLY that will get you past whatever binary gremlin is crashing your call log. I can't guarentee that would work, this is all just a guess... but that's my best guess. Good luck.
[G2 Original Android Development] GalaxyGusta:
I didn't restore it this time I just made a phone call to have something in there then clicked the bottom and it's crashing..

Is there anything I can provide to you so maybe you'll be able to see what's causing that?

Edit:ok listen I just figured it out...

I'm from Israel and therefore I use Hebrew on my device

When using my device in Hebrew it crashes.. When switching to English it doesn't
[G2 Original Android Development] ALIEN-3-:
Hi to all.

I just record a call with my daughter ,but i cant find the file. Where is the folder?
[G2 Original Android Development] ulihh:
I didn't say PNO is in any way part of the bug, it's just the line that I never saw before that now appears at the beginning of a reconnection... oh wait, it appears twice. 1st time when the wifi drops, 2nd exactly 5 minutes later when the reconnection starts. I've grepped through almost 14 days of logs. It never appeared before. Interesting to see, the reconnections always start at the same timing distance to the drop, 5 minutes later.

That's ok for me, I hope I can help. Send me whatever you think is worth testing and ask the right questions ;) I don't mind flashing experimental versions.

Regards, Uli
[G2 Original Android Development] Rasgola:
How to upgrade to most recent nightly build.

Hi,

I am flashed my LG G2 to CM13 feb24 build. After flashed I lost my root access. Please let me know what is most stable nightly build and please let me know the steps how to upgrade to recent builds. Or does OTA works seamlessly.
[G2 Original Android Development] chobot1976:
Settings about phone few tap on numbers of (sestavení I don't know in English) and enabled root access...

Edit: settings developer options root access
[G2 Original Android Development] murok9042:
Try the Snapshot version. You can use it as a daily driver for the G2

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Original Android Development] ulihh:
[MENTION=2096805]dr4stic[/MENTION], I just read the notes in change 140300. As I noted somewhat earlier I also have a multi hotspot environment at work. I had a drop there with your test kernel and that change applied. That's where wpa_supplicant spit out his reason=7 directly after key negotiation completed.
[G2 Original Android Development] dr4stic:
Yeah, from the reading I've been doing, I'm starting to think you may just be screwed. Some of the reading led me to this link (and then the link following it, that I found in the first link I post here):

http://serverfault.com/questions/614851/wifi-deauthentication-issue

https://en.wikipedia.org/wiki/Rogue_access_point

Based on the reading above and the little I was able to find online, and your description.... It sounds like your phone was sent a frame (class 3, which is supposed to be for authenticated things, i.e... real expected traffic). Your phone realized it wasn't even associated to the AP that sent it and so dropped the connection.

Given that you mentioned you're in a multi-AP environment, and reading the first link, I'm guessing that one of two things is happening to you.

Your work environment (hotspot network) is set up poorly, or is set up with poor equipment. The first link details this issues and in the comments, the OP mentioned that the problem was solved when they went from a multi apple airport solution to a cisco managed solution.

Your work environment is not terribly secure and someone has set up a Rogue AP. And this rogue AP is being used to attack other devices on your network.

If you're looking at a deauthentication attack, there may not be much recourse:

http://security.stackexchange.com/questions/57776/de-auth-attack-reason-codes-and-possible-reaction

https://en.wikipedia.org/wiki/Wi-Fi_deauthentication_attack

And that sucks... There's something called PMF (protected management frames) and I'm gonna see if it's enabled by default for us, and if I can enable it by default for us. That would at least require encryption on deauthentication requests. However, I suspect it may already be enabled.

The other issue is that this may not be something that can be repaired in the software driver. The software driver largely acts as an interface to the proprietary firmware... a firmware, mind you, that hasn't been updated by broadcom in a few years. There's only so much fixing that can be done from the software driver and it may be that if this is a problem with a reaction in the firmware, you may be screwed.. basically... forever.

I'm gonna PM you off list to talk about a few things and figure out some next steps.
[G2 Original Android Development] peanutsz:
newest nightly doesnt saves videos.....
[G2 Original Android Development] dongerado:
You mean from camera app? No problem here in nightly 1704.
[G2 Original Android Development] Josh:
When I try edit tiles and add system crashed on 0417 build
[G2 Original Android Development] josezito:
Hello guys. I upgraded to the new rom but i forgot to trigger the developer program, and the installation is broken becouse gapps

Now, have no access to the recovery.

Its possible doing this whit command buttons?

Thanks
[G2 Original Android Development] ulihh:
I carry a second android device with me. It's a LG P700 with the latest mahdi rom (android 4.4.4) on it. Yeah, it's a really slow phone, but it runs ok and is a good comparison in some situations. At my work I can't see wifi drops on this device. Shouldn't I? We have cisco hotspots. Let's look at my G2 logcat:

04-14 14:50:13.421 1371 1371 I wpa_supplicant: wlan0: Associated with 70:10:5c:f3:2d:f8
04-14 14:50:15.501 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
04-14 14:50:15.519 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13 -> NAK
04-14 14:50:15.532 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25
04-14 14:50:15.533 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected
04-14 14:50:15.637 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=1 subject='/DC=group/DC=xxxxxxxxxx/DC=xxxxxxxx/CN=xxxxxxx' hash=cbd2f85d53bdb8b63bb5dde02c35b4702b20fc4f845f326ee37c0be06b0974b6
04-14 14:50:15.652 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-PEER-CERT depth=0 subject='/C=DE/O=XXXX/CN=xxxxxxxxxx/emailAddress=xxx@yyy.com' hash=897c3c73ee938574b1b71094d80e80ce7c28f4edd3283501d2ced842879d3efd
04-14 14:50:15.760 1371 1371 I wpa_supplicant: EAP-MSCHAPV2: Authentication succeeded
04-14 14:50:15.779 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
04-14 14:50:15.859 1371 1371 I wpa_supplicant: wlan0: WPA: Key negotiation completed with 70:10:5c:f3:2d:f8 [PTK=CCMP GTK=CCMP]
04-14 14:50:15.859 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-CONNECTED - Connection to 70:10:5c:f3:2d:f8 completed [id=1 id_str=]
04-14 14:50:15.864 821 1096 D IpReachabilityMonitor: probing ip=10.173.0.1%23
04-14 14:50:21.236 245 874 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UID' not found
04-14 14:50:21.548 1371 1371 I wpa_supplicant: wlan0: Associated with 70:10:5c:f3:2d:f7
04-14 14:50:21.683 1371 1371 I wpa_supplicant: wlan0: CTRL-EVENT-DISCONNECTED bssid=70:10:5c:f3:2d:f7 reason=7
04-14 14:50:21.683 1371 1371 I wpa_supplicant: p2p0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD

Some personal details are covered with xxx. Looks like it was associated with the right hotspot before, but why changes the mac address from 70:10:5c:f3:2d:f7 to ...:f8? I saw several changes in mac addresses this way (+1 on the 6th digit) before and they don't seem to do anything. Just irritating.

Anyway, I talk to our network team in the next days and ask them if they have all the mac addresses in their equipment database or we have a rogue ap.

Regards, Uli
[G2 Original Android Development] Alex93917:
I confirm that... ?
[G2 Original Android Development] Josh:
Last days I've got problems with connection on LTE network on my d802,only has 3g connection. Any suggestions to fix it or I must change sim card? I'm on clean 0317 snapshot.Thanks
[G2 Original Android Development] raffux3:
BUG Nightly 17: advanced messages settings crash
[G2 Original Android Development] jl10101:
WiFi Update

Just dropping in to say that on nightly 20160417 WiFi seems to be stable now. I haven't had a single drop at home like I used to. I have 5 APs running throughout the house and had the phone sleeping, streaming, rebooting, receiving push emails etc.

I will keep monitoring but so far so good. Hello daily driver!
[G2 Original Android Development] ulihh:
How did you check it? Did you also look at the logcat? It's probably the background scanning that reconnects your wifi.

Regards, Uli
[G2 Original Android Development] jl10101:
When I was having disconnects and drops, it would be reflected in the battery stats. Also, after letting the phone enter deep sleep, I would send Whatsapps, emails etc to it (with data off) and received nothing until waking the device. I haven't had a problem running those (what I like to call "real world / usage") "tests" today with 20160417.

Here is my battery stats screenshot. Ignore the two drops for WiFi as I was flashing / had WiFi disabled purposefully. It's not a logcat, but its real use and it's working for me when, in the past, it didn't.
[G2 Original Android Development] Lycidias:
I have continious reboots after i enter my sim Pin after first boot. I Come from lollipop Stock kdz. Beanstalk Rom is just working fine. Any ideas?
[G2 Original Android Development] ulihh:
Read the OP and don't reboot before flashing gapps.
[G2 Original Android Development] Lycidias:
I red the OP and flashed open gapps just after the Rom..
[G2 Original Android Development] ulihh:
Which G2 variant? Have you tried taking out the sim?
[G2 Original Android Development] dr4stic:
We'll need to test further off the forum... your problems are probably protocol issues and unlikely what most other people were seeing. When two MAC addresses are that close to each other, it's usually because they're on the same device. One mac address is for the wireless interface, the other for a LAN side interface (which is typically seen as originating control packets). I don't think you're necessarily under attack. I think we need to figure out how to debug you properly. But I don't believe your issues are like the wifi issues that others are having.
[G2 Original Android Development] ulihh:
I have just learned that these MAC addresses are representations of virtualized BSSIDs and they are for the 2,4 and 5GHz access points - one address for each radio. See https://supportforums.cisco.com/discussion/11790496/understanding-wireless-mac-address. At my work the mac addresses seem to be n and n+1 though. Next I will check if I can reduce the wifi drops when turning off one radio - i tried that already 2 months ago but the logs weren't as good as now.

Regards, Uli
[G2 Original Android Development] julijannikolic:
Hi guys, I have problem with my G2 and cynogenmod 13. I am using latest montly release and I have problem that my dialer is sometimes making dialed or received numbers shorter. I have disabled connected line indetefication because it was even worse when this was on.

For example, in this screenshot +381642152 is missing last 3 digits, and missing last 3 digits is constant for all corrupted numbers...
[G2 Original Android Development] jak-jak:
i want to upgrade my G2 and G3 with new ROM,i do not know what should i do,is there any one to help me?i wana know what requirement is needed and so on.plz send me private msg if you can help me,

thanks
[G2 Original Android Development] Josh:
Everything you got on xda,just search it no one can do for you! Google knows everything! First you must know model of G2 and G3 ...good luck