Lollipop and AES WiFi Fail - ONE Q&A, Help & Troubleshooting

Apologies if this has been noted elsewhere. The search didn't bring it up.
Since upgrading my OPO to CM12, I have noted that after deep sleeping, my phone wakes with a "Wifi Authentication Error," without fail. Apparently, Lollipop has a coding problem, wherein it won't reconnect to AES, but apparently is ok in reconnecting to routers with TKIP encryption. Unfortunately for me, TKIP disables WPS, and I have several devices that use WPS to connect to my network (Printers), so I need AES.
Looking at the following page, it seems I am not alone, and that a lot of people have the same issue.
I will state right now, that I am definitely not attacking the CM devs, as this looks thoroughly like a Google coding issue.
If you are having the same issue, then please check out this link, and click on the star in the top left corner. Google still looks on this as a minor issue, when it isn't.
https://code.google.com/p/android/issues/detail?id=78702&

Related

Samsung - VPN Issues

As a new XDA user involved with development, but unable to post in the development boards because of minimum post restrictions, I am going to drop some general information here (getting my post count up). This is also an attempt to see how many people are frustrated with the VPN connectivity on Samsung Platforms and desire a kernel fix.
Behavior:
An inability to connect to a VPN concentrator, or a seemingly successful connection with a failure to pass traffic across the tunnel. You can observe the behavior by connecting to your VPN, having the interface report a successful connection, but when you attempt to access resources on the other side of the tunnel you will not be able to reach them. When you view the status of the VPN connection, you will see that no packets were encrypted and passed along the tunnel.
Cause:
While I cant rule out a configuration error in every case, I can in mine. Samsung was/is creating kernels for GB and ICS with a slimmed down version of ipsec-tools/racoon. Without getting to technical, this is the module responsible for negotiating the multiple phases necessary for a fully functional VPN tunnel. Because it is slimmed down, IPsec-Tools lacks its usual level of configuration necessary to support a wider range of VPN encryption types.
Solution:
Sorry, for all of you vanilla/non rooted users (really, who is that here anyway?) there is no fix. For everyone else, we need a kernel (the version depends on your rom) with a full version of IPSec-Tools baked in.
Let me know what you people think, the more responses the better my chances of getting this put together. Feel free to also give me a tl:dr
PS: I already tried and failed at compiling this myself, if anyone knows of any good places to start learning a bit more about kernel compiling please drop it here or PM me.
Thanks, I thought the problem was in my router. I am using a Linksys router with DD-WRT on it, and thought the problem was on that end.
Hawkeye9723 said:
Thanks, I thought the problem was in my router. I am using a Linksys router with DD-WRT on it, and thought the problem was on that end.
Click to expand...
Click to collapse
Could be, what version of android are you on? Were you experiencing the behavior above, successful connect and no packets transmitted? Usually dd-wrt wants you to setup the vpn as SSL IPsec (RSA Certificate). I have not yet given tried that implementation but have been attempting IPsec + xAuth PSK (3des encryption).
I have in the past configured dd-wrt to work successfully using the "VPN (the easy way)" on the dd-wrt site (sorry, I'm not allowed to post hyperlinks yet).
It would be great if we could get VPN running like it should. Would make my life a ton easier for work, I wouldn't need to carry around my laptop just to diagnose a tiny problem.
~PsyCl0ne
PsyCl0ne said:
It would be great if we could get VPN running like it should. Would make my life a ton easier for work, I wouldn't need to carry around my laptop just to diagnose a tiny problem.
~PsyCl0ne
Click to expand...
Click to collapse
As an IT professional, that's my motivation as well. Been following all of the leaks and releases, no fix yet. Looks like we'll have to take matters into our own hands.
I haven't tried in on ICS yet. I was running the stock GB. It would connect, bu could not access anything on my home network. I also could not access anything on the internet. Trying to access the router config page would just timeout. I had dd-wrt set up using PPTP.
Yeah, could be the same issue.
Don't mean to patronizing, if I am I apologize...
Did you try setting the advanced options? See attached image.
Leave the DNS settings alone. Try adding the forwarding route ie. If your router address is 192.168.1.1, put 192.168.1.0/24 in that field (192.0.0.0/8 or 192.168.0.0/16 should work too).
Sent from my SAMSUNG-SGH-I727 using xda premium
this issue exists on most samsung phones, from GB to ICS - not sure about JB.
ipsec is broken

Wifi disconnected periodically

Hi guys this is my first post in HOX forum, I just got mine 1 week ago.
So the main problem I have so far is that my HOX gets disconnected from wifi at home periodically. It just suddenly drops and then reconnects by itself. Does anyone experience the same? If not I'm considering exchange a new one.
Thanks guys!
zihaoyu said:
Hi guys this is my first post in HOX forum, I just got mine 1 week ago.
So the main problem I have so far is that my HOX gets disconnected from wifi at home periodically. It just suddenly drops and then reconnects by itself. Does anyone experience the same? If not I'm considering exchange a new one.
Thanks guys!
Click to expand...
Click to collapse
I do.. but my router's a POS without an external antennae. so I can't give good answer on that.
Mine does, frequently. I've seen posts regarding the problem, and maybe even a fix. But it doesn't bother me enough to risk breaking something else in the process.
Sent from my HTC One X using XDA Premium HD. In between Force Clo...
zihaoyu said:
Hi guys this is my first post in HOX forum, I just got mine 1 week ago.
So the main problem I have so far is that my HOX gets disconnected from wifi at home periodically. It just suddenly drops and then reconnects by itself. Does anyone experience the same? If not I'm considering exchange a new one.
Thanks guys!
Click to expand...
Click to collapse
I upgraded to the beastmode kernel and this started happening to me too.
Running the normal CleanROM 4.5 Rom fixed the problem for me.
Last night I took a logcat of when this disconnect happens... But I dont really know how to debug it.
I have the same issue, with an additional problem. When WiFi disconnects I lose mobile data too. Toggling airplane mode brings back mobile data. WiFi may or may not connect for a little bit afterwards.
Sent from my One X using xda app-developers app
Why don't you all post up what bands your running on and what you have set on your router. We can map it out a little better
18th.abn said:
Why don't you all post up what bands your running on and what you have set on your router. We can map it out a little better
Click to expand...
Click to collapse
Good idea 18th.abn. I'll start.
With BeastMode Kernel v3 I have this problem. However I don't have the problem with the stock CleanROM 4.5 kernel. I will test CleanROM V with CleanKernel tonight and see if the problem is still there.
I did get a logcat while the disconnect happened... I took a couple and will have to remember which one was which... I don't really know how to read a logcat file though. Anyone good with linux? Does that help at all?
Problem happens with 2 separate routers. I'm a BAMF so I have 2 routers on my home network, 1 to service each band, and only that band.
Router 1:
Name: Linksys WRT320N
Firmware: DD-WRT v24-sp2 (04/16/10) mega
(SVN revision 14289)
Band: 5Ghz N-only, 40Mhz channel width, control channel lower, wireless channel auto.
Security: WPA2-PSK (Personal), AES
Router 2:
Name: Netgear WGR614v10
Firmware: Stock
Band: 2.4Ghz G-only, channel 11, "up to 54mbps mode"
Security: WPA2-PSK, AES
EDIT: added logcats.
Okay, so I suck at this and have forgotten which one is which. I believe it was my latest one that shows the disconnect (logcat 3). I can make another soon enough.
Logcat1
Logcat2
Logcat2
Do you have the same issue on both routers?
In logcat3, it looks like it connects for just a little bit, then once disconnected, it attempts but can't get fully connected again....it was a quick glance but is that the case?
---------- Post added at 04:24 PM ---------- Previous post was at 04:07 PM ----------
I believe your issue is right here...could be wrong but
W/wpa_supplicant( 7594): [EAP-MSG] EAP [email protected]: eap_methods not available
I/wpa_supplicant( 7594): [SeamLess] This is already connected so rejected to 00:23:69:eb:98:6a
I/wpa_supplicant( 7594): [SeamLess] flag_disconnect is reset i.e., Seamless is give it up
Here is the why its not working, its looking for sim authentification-
To run an EAP-SIM/AKA authentication you will need a client as wpa_supplicant which has access to a (U)SIM. The WLAN access point on the network has to support EAP (which is often transcribed as WPA(2)-RADIUS or WPA(2)-ENTERPRISE). The WLAN AP has to have access to a RADIUS server who handles the authentication and session key generation. The RADIUS server in a productive environment needs for EAP-SIM/AKA access to the home location register (HLR) of the MNO where the (U)SIMs are registered. For testing a file with precreated values for authentication is sufficient.
I think your security is possibly on Wpa2-EAP, Which would explain the eap-sim call, and I doubt you have a RADIUS server giving out session keys to authenticate....double check your security settings
To add. Here's a good little write up in optimum router settings with your wireless n. I see a few things in your setup that could be killing or seriously slowing your wireless connections...
http://www.smallnetbuilder.com/wireless/wireless-basics/30664-5-ways-to-fix-slow-80211n-speed
I would DEF. drop to 20mhz from 40mhz, that alone might fix your problem. I had big problems with tabs and phones connecting at 40mhz. 20 should help a lot and don't select auto, keep at 20.
Wireless channel, u have set on lower channels, lower channels are usually busier, there's an app, wifi analyzer, it will show you the least busy channels and then choose A channel, don't let it bounce around and choose for you.
Dd-wrt has an infinite amount of twee king/tuning options, as you already know but is extremely easy to make a great connection a worthless one all the same...
Try just switching to 20mhz and nothing else at first......it just might be the root issue for you also
Thanks, I'll try that out and report back.
---------- Post added at 12:19 PM ---------- Previous post was at 11:34 AM ----------
18th.abn said:
Do you have the same issue on both routers?
In logcat3, it looks like it connects for just a little bit, then once disconnected, it attempts but can't get fully connected again....it was a quick glance but is that the case?
Click to expand...
Click to collapse
My problem is that WiFi was fine for a while, then would disconnect, and then reconnect a second or two later. However, I did take a look at that guide you posted (I really like smallnetbuilder) and made some changes to my setup that they (and you) suggested. I'm still in the process of testing it.
18th.abn said:
---------- Post added at 04:24 PM ---------- Previous post was at 04:07 PM ----------
I believe your issue is right here...could be wrong but
W/wpa_supplicant( 7594): [EAP-MSG] EAP [email protected]: eap_methods not available
I/wpa_supplicant( 7594): [SeamLess] This is already connected so rejected to 00:23:69:eb:98:6a
I/wpa_supplicant( 7594): [SeamLess] flag_disconnect is reset i.e., Seamless is give it up
Here is the why its not working, its looking for sim authentification-
To run an EAP-SIM/AKA authentication you will need a client as wpa_supplicant which has access to a (U)SIM. The WLAN access point on the network has to support EAP (which is often transcribed as WPA(2)-RADIUS or WPA(2)-ENTERPRISE). The WLAN AP has to have access to a RADIUS server who handles the authentication and session key generation. The RADIUS server in a productive environment needs for EAP-SIM/AKA access to the home location register (HLR) of the MNO where the (U)SIMs are registered. For testing a file with precreated values for authentication is sufficient.
I think your security is possibly on Wpa2-EAP, Which would explain the eap-sim call, and I doubt you have a RADIUS server giving out session keys to authenticate....double check your security settings
Click to expand...
Click to collapse
My security was (and still is) set as WPA2 Personal with "AES" as the WPA algorithm. This is correct for my home network, is it not? At least that's what I set in the "wireless security" tab of dd-wrt under wireless. I see that there is something under "advanced settings" called "authentication type" which has a radio button for "auto" and "shared key". Right now it's on auto. Think I should change it to "shared key"?
"Authentication Type:
You may choose from Auto or Shared Key. Shared key authentication is more secure, but all devices on your network must also support Shared Key authentication."
18th.abn said:
To add. Here's a good little write up in optimum router settings with your wireless n. I see a few things in your setup that could be killing or seriously slowing your wireless connections...
http://www.smallnetbuilder.com/wireless/wireless-basics/30664-5-ways-to-fix-slow-80211n-speed
I would DEF. drop to 20mhz from 40mhz, that alone might fix your problem. I had big problems with tabs and phones connecting at 40mhz. 20 should help a lot and don't select auto, keep at 20.
Wireless channel, u have set on lower channels, lower channels are usually busier, there's an app, wifi analyzer, it will show you the least busy channels and then choose A channel, don't let it bounce around and choose for you.
Dd-wrt has an infinite amount of twee king/tuning options, as you already know but is extremely easy to make a great connection a worthless one all the same...
Try just switching to 20mhz and nothing else at first......it just might be the root issue for you also
Click to expand...
Click to collapse
I just made some changes based on the guide you posted. I also made sure to drop the channel width down to 20mhz (I didn't know that made so much of an impact. Kudos for that piece of advice. I chose to use channel 36, 5.180Ghz, based on my testing with wifi analyzer. No one else in the neighborhood has a 5Ghz router (Apparently).
I'll see what tonight's testing yields.
Awesome, hope it helps! As far as the disconnecting, catalog shows it searching for aes-sim authentification and I don't know why. Its connected, then disconnects because already connected....*LIGHT BULB* Make sure WiFi settings on device is set to 5ghz and not auto.....that may be why its giving a already connected in catlog
18th.abn said:
Awesome, hope it helps! As far as the disconnecting, catalog shows it searching for aes-sim authentification and I don't know why. Its connected, then disconnects because already connected....*LIGHT BULB* Make sure WiFi settings on device is set to 5ghz and not auto.....that may be why its giving a already connected in catlog
Click to expand...
Click to collapse
Are you saying the WiFi settings on my phone? I won't be able to set it to 5ghz only as I connect to various 2.4ghz networks throughout the day.
I haven't seen the error again yet *knock on wood*
Maybe you fixed it.
Awesome, I bet it was the 40mhz that was doing it glad u got it!
I spoke too soon. I was browsing XDA on my phone, clicked a new page and it disconnected for a second and reconnected immediately.
New logcat. I saved this one only a few seconds after it reconnected. It should say something about WiFi at the very bottom of the logcat file. Do these things even help you guys?
Logcat #4
Check my thread!
[HowTo][INFO] Wifi Drop Caused by "Sign-in to WiFi Network" Notification [KitKat BUG]
http://forum.xda-developers.com/and.../howto-wifi-drop-caused-sign-to-wifi-t2862509
M_J_Nazari said:
Check my thread!
[HowTo][INFO] Wifi Drop Caused by "Sign-in to WiFi Network" Notification [KitKat BUG]
http://forum.xda-developers.com/and.../howto-wifi-drop-caused-sign-to-wifi-t2862509
Click to expand...
Click to collapse
This thread is from 2 years ago... In the future, try not to dig up old threads, especially to promote your own (and irrelevant) thread
I don't care about the date of threads, i just care about the solution and help others! you just do your job, every forum has a admin moderator, and you are not one of them! so do your job.
Best regards
M_J_Nazari said:
I don't care about the date of threads, i just care about the solution and help others! you just do your job, every forum has a admin moderator, and you are not one of them! so do your job.
Best regards
Click to expand...
Click to collapse
You're solving an issue that doesn't really pertain to the original bug. If anything, start a new thread in general here, but don't bring back this thread because of its lack of relevance.
The issue deals with the WiFi on 4.2.2 (not kitkat) dropping out and coming back in. It's an issue that's based on the kernel we had. Your solution is based on timing out. It's not the same bug.
And just for the record, I'm a user. Just like you are. So what would my job exactly be? Yes, I just started to develop too, but don't accuse me of not caring about helping others. I've been helping out for a long while now. I don't believe we really have "jobs" on this forum because none of us are obligated do anything. It's a bunch of people following etiquette and helping each other.

[Q] Won't reconnect manual network without SSID broadcast?

So the S3 has known WiFi issues, but mine seems to have none of the issues I've read about thus far. It does have one irritating thing that has been driving me crazy for the longest time. If I ever move outside of the range of my network, reboot, or etc such that the WiFi has to be reestablished, it will decide that my network is "out of range" even though the signal is well within an acceptable minimum (it's a tad bit weak, but, once established it holds extremely steady pretty much no matter what I'm doing.) If I remove and re-add the network settings it works perfectly, again with a stable signal and perfect speeds until the next time I move out of range or reboot.
For now I've reenabled SSID broadcast, but I really liked the idea of having it off as it's a ridiculously simple yet strikingly effective security mechanism (I like the "security through obscurity" methods when I can -- especially since I'm having to use the old WEP encryption protocol to support some older devices, though I'm just about ready just to give up on them at this point. Even the best hacker in the world couldn't get into my network if (s)he never actually made any attempt to do so in the first place.) With SSID enabled, it has no troubles picking up my network every time, it just won't automatically pick it up without it.
Is this just an issue with the software itself or something? Anything that can be fixed from the user side, or is it something that can only be fixed by an update to the OS or related software itself? (But then with 4.1 coming soon supposedly I'm kind of hoping that if it is an issue with the software that would fix it. Still, that's a while away at least and this is assuming their plans aren't messed up with this whole lawsuit business causing them so many problems right now.)
If you have SSID broadcast disabled, how do you expect your phone to recognize the network? I can see how it would work if you enable SSID, connect to your network then disable it again, but it's not going magically reconnect with SSID disabled, its not logical seeing your SSID is what makes it possible for your phone to find your network.
Sent from my SCH-I535 using xda app-developers app
Wep sucks ofcourse but how about just setting up a mac addy auth to give another layer of security and enable ur ssid
Sent from my SCH-I535
I do use MAC address filtering if that's what you mean. While it might stop a script kiddie, I don't have a huge amount of confidence in it. MAC address spoofing is so pitifully easy than with computer equipment at least you usually are even presented with a configuration option that lets you specifically change the MAC address to anything you want. I'm definitely sticking with it because, well, there's absolutely no reason not to, but I actually have less confidence in MAC address filtering to stop anyone than disabled SSID broadcasting because anyone actually actively trying to break in should pretty much immediately bypass that particular mechanism right off.
Shibby87 said:
If you have SSID broadcast disabled, how do you expect your phone to recognize the network? I can see how it would work if you enable SSID, connect to your network then disable it again, but it's not going magically reconnect with SSID disabled, its not logical seeing your SSID is what makes it possible for your phone to find your network.
Click to expand...
Click to collapse
ALL other devices are smart enough to search for a manually configured network if they actually know the SSID to search for. My Roku, my Android 2.2 "Internet Tablet" (basically a PDA) by Archos, my Nintendo DS (this is the main thing holding me back at WEP, and as ancient and pitiful as its networking is, even IT can connect on its own without making me manually recreate the settings every time!) and my EeePC running Windows XP without any software to manage the WiFi settings except the built-in Windows thing.
Nazo said:
So the S3 has known WiFi issues, but mine seems to have none of the issues I've read about thus far. It does have one irritating thing that has been driving me crazy for the longest time. If I ever move outside of the range of my network, reboot, or etc such that the WiFi has to be reestablished, it will decide that my network is "out of range" even though the signal is well within an acceptable minimum (it's a tad bit weak, but, once established it holds extremely steady pretty much no matter what I'm doing.) If I remove and re-add the network settings it works perfectly, again with a stable signal and perfect speeds until the next time I move out of range or reboot.
For now I've reenabled SSID broadcast, but I really liked the idea of having it off as it's a ridiculously simple yet strikingly effective security mechanism (I like the "security through obscurity" methods when I can -- especially since I'm having to use the old WEP encryption protocol to support some older devices, though I'm just about ready just to give up on them at this point. Even the best hacker in the world couldn't get into my network if (s)he never actually made any attempt to do so in the first place.) With SSID enabled, it has no troubles picking up my network every time, it just won't automatically pick it up without it.
Is this just an issue with the software itself or something? Anything that can be fixed from the user side, or is it something that can only be fixed by an update to the OS or related software itself? (But then with 4.1 coming soon supposedly I'm kind of hoping that if it is an issue with the software that would fix it. Still, that's a while away at least and this is assuming their plans aren't messed up with this whole lawsuit business causing them so many problems right now.)
Click to expand...
Click to collapse
hidden ssid enabler will solve this problem. it works great for me. follow the directions in comments of play store though.
You know, I do believe that did actually solve the problem. I guess more testing is needed, but in my initial test it seems to have worked just fine with the SSID broadcast set to hidden again (I even rebooted the router and phone both just to be sure the settings fully took.)
It still strikes me as being a bit dumb that my ancient Nintendo DS that can't even handle WPA can handle a non-broadcast SSID and my previous Android PDA could as well, yet this Android phone couldn't out of the box...

Lollipop Wifi Connectivity Check Feature

Hi,
first of all, my apologies if i am posting this in the wrong section, i read the sticky but i consider this more a discussion rather than a request for help.
Most of you probably know the little exclamation point next to the wifi symbol in the status bar that you get since Lollipop when the network does not offer Internet connectivity.
I tried to locate the feature in the AOSP codebase but was not apt enough to come up with anything relevant, though i did log the network while disabling/enabling wifi to see what it does, and apparently it sends out a couple of DNS queries. I have yet to check it more thoroughly with Wireshark.
So in theory, from a privacy point of view, Google could trace your account/model/network anytime you connect etc.
I am quite interested in how it works exactly, and if i, for instance, could hard code my own server's address into it.
I have read some things that relate this connectivity check to a setting "global captive_portal" (or similar), but was unable to reproduce on Lollipop.
It is also quite strange that apparently no one discussed this before (from a privacy point of view).
So i would be happy to hear what you people have to say about it.
Ciao

Wi-fi issue (and how to solve it!)

Received today (finally! :silly my XT1650-03 Dual SIM in white/gold flavour and... only few seconds after turning it on... the first issue!
And not a minor one, a bad issue... weird that nobody have reported it before!
Turned on, boot, chose language, selected a wifi and... error during verifying connection: no Internet!
Obviously, my wifi had a good Internet connection up & running...
Tried again. Nope. Tried my old phone in hot spot mode (ever worked fine with every piece of hardware...), connected... same error!
Major problem was that on this phone the verifying step can't be bypassed (ignore is gray out...), so I was on a no way loop.
After A LOT of tries, at last it decided to bypass and go after BUT all my wifi connection still were marked as "Connection without internet" and no navigation available.
I've tested three known good wireless connections, all open, all same result.
Tried to configure them as static IP, inserted good data (it's my work, I KNOW what to insert...), same result.
The phone was connected, was pingable, has good IP, Gateway, DNS but... No internet.
My old phone and my pc, in wifi on the same network, was laughing at new arrived while surfing the Web. ..
After some Google searching (and a LOT of stupid "solutions"...) I found the good one... :fingers-crossed:
It's needed to enable Developer options and, inside, enable an option called "Use old/Lollipop DHCP client".
After that we *have to* delete the memorized wifi connections and recreate them. After that they work fine!
Weird thing is that, when I set manually the connection parameters, there shouldn't be anymore a DHCP protocol to be used...!!!
BUT probably, since it seems to need connections to be deleted before begin to work fine on them, even with manual (correct!) parameters it continues to mark them as "No internet" for some strange reason...
I think this is an issue related to Marshmallow more than Moto Z itself, BUT anyway it is a bad bug and I can't understand @google what they have "invented" this time to have such an absurd behaviour on a simple (and old) protocol as DHCP!
Obviously, connection parameters before and after the setting were exactly the same (same IP, same gateway, same DNSs), BUT with old DHCP enabled they are now of Moto Z taste...
Nobody had faced this issue before?
I didn't have this, probably just you. Haven't heard of anyone else either, so i can assume it might be your Router/WiFi AP that is old/outdated and uses redundant/old protocols (try updating the Routers Firmware, see if that helps). If that isn't the case, then i don't know (maybe someone else also has/had this problem, don't ask me).
yanniclord said:
I didn't have this, probably just you. Haven't heard of anyone else either, so i can assume it might be your Router/WiFi AP that is old/outdated and uses redundant/old protocols (try updating the Routers Firmware, see if that helps). If that isn't the case, then i don't know (maybe someone else also has/had this problem, don't ask me).
Click to expand...
Click to collapse
I have to repeat myself... It's my work... I know what I'm talking about...
Up to date, four tested, three not working vs. one working with new protocol enabled. All working with old one.
DHCP is a old, simple & efficient protocol, there is no need to mess up it...!
WiFi compatibility *must* be best as possible (think about public hotspots, airport, etc... I Travel a lot and I need it!) and not limited in any way by absurd changes in well working protocols...!
When I'll be @hong Kong airport and my Moto Z eventually refused to connected WiFi, what should I do? Ask them to "upgrade router firmware"?
If you Google "marshmallow dhcp client issues" it's full of thread of people having this issue...
What they have invented is still a mistery instead...
I don't have this problem too.
I have the phone from august. It is an UK model, single sim. I have done factory reset more than 5 times and never had that problem. It is your phone with this problem.
SteveHG said:
I don't have this problem too.
Click to expand...
Click to collapse
You'll have...
Great post. I have that problem to with wifi, cannot establish connection. Your guidance is perfect solution.
I guess is more to Marshmallow problem (software) rather than hardware issue.
izamd said:
Great post. I have that problem to with wifi, cannot establish connection. Your guidance is perfect solution.
I guess is more to Marshmallow problem (software) rather than hardware issue.
Click to expand...
Click to collapse
Yes, BUT... I've found MM ROMs on other devices where this doesn't happen...
Be careful that on Nougat this option is no more available...

Categories

Resources