There is no wifi on gederom or any CM9 rom.I turn on and off wifi and still it doesn't work. I have an Intellinet router.
Thanks for any replies.
You should probably try changing your router's channel. I've heard that channel 13 is bad news ... and I think that was for a cm9 rom. Anyway, it's definitely worth a shot.
Are you wiping cache/dalvik before flashing new roms? If you're going from one developers rom to another developer, you should do a factory reset, then wipe, then install rom. If all you're doing to flashing roms from the same developer, then a cache/dalvik wipe is all you need to do. Hope that helps!
Wipe that kindle clean. Are you using fios? I've heard of a few people having issues with them.
I notice I can't see one particular Linksys wireless router at one of my job sites, but since we have two wireless routers it doesn't really affect me. No idea why...but maybe there is something someone else knows that can help understand the issue?
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Daniel120201 said:
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Click to expand...
Click to collapse
Try changing from dhcp to static.
Daniel120201 said:
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Click to expand...
Click to collapse
Can you go someplace where there is another router? Like I said, I notice there is one particular flavor of Linksys router that my Fire can't see on this ROM, yet at home I have a different model Linksys and there is no problem. Check it out on another router to see if it's just some weird compatibility issue.
Daniel120201 said:
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Click to expand...
Click to collapse
Check the router and see if QOS is enabled. If so try turning it off.
I don't have any other routers in my house. With static I still get the same result.
Any way thanks for all the replies.
Sent from my Kindle Fire using Tapatalk
IF FOR SOME REASON WIFI DOESN'T WORK ON THE FIRST BOOTUP DO THE FOLLOWING:
This is what hashcode say's
Enter Terminal Emulator
Type: su
Type: fix-mac.sh
Exit Terminal Emulator
Reboot
Daniel120201 said:
I don't have any other routers in my house. With static I still get the same result.
Any way thanks for all the replies.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Daniel120201 said:
I don't have any other routers in my house. With static I still get the same result.
Click to expand...
Click to collapse
Is there a reason you can't go to a coffee shop, library, or any number of other hotspots with your Fire? I mean if you have a medical issue that keeps you bedridden, I understand, but if not, there are usually routers everywhere you can try connecting to.
Please try connecting to your wifi and then pastebin the output from the following and PM me the links:
Adb shell "dmesg" > dmesg.txt
Adb logcat > logcat.txt
Thanks
Sent from my DROID4 using Tapatalk 2
The fix-mac.sh fix still doesn't work and I found something with build.prop and settings.db and with some locale things while I was with channel 11 and still it didn't work.
Thanks for the replies.
Daniel120201: I looked at your pastebin logs and here are some notes:
The key lines in your logs are:
logcat: 7551.D/wpa_supplicant( 1040): EAPOL: Supplicant port status: Unauthorized
dmesg: 3949.<7>[ 538.654174] wlan0: disassociated from 00:0e:e8:d5:c5:d1 (Reason: 15)
When I looked up "Reason 15" as a disassociation error, I find:
Reason code 15: 4-Way Handshake timeout.
When I looked up how 4-Way Handshake works:
http://en.wikipedia.org/wiki/IEEE_802.11i-2004
On that page it references CCMP protocol for WPA2 and IPSEC:
http://en.wikipedia.org/wiki/CCMP
And on that page it mentions this:
CCMP is an enhanced data cryptographic encapsulation mechanism designed for data confidentiality and based upon the Counter Mode with CBC-MAC (CCM) of the AES standard
I double-checked the kernel config and low and behold:
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
I think this can be solved via a kernel config change. Later today, I will create a new kernel only .zip file with this change and I'd like for you to test it.
This also may solve IPSEC issues as well.
Here is a link to the new kernel w/ CCMP support added [Kernel #12 06/08]:
http://bit.ly/KPbDVm
md5sum: e7476ff785b2dfbdb062e1cc036c14ac
Thanks for the kernel Hashcode.It's Works.
You're quite welcome. I think there were a few others who were in the same boat.
Updated kernel Still same problem for me
Hashcode said:
You're quite welcome. I think there were a few others who were in the same boat.
Click to expand...
Click to collapse
I am still experiencing this error after kernel update. Too bad this is a very good rom otherwise.:crying:
Related
Hi folks,
Since last thursday I've got a problem with my WiFi on my wildfire. Every time I turn on the WiFi (via not. bar or settings) the little box is ticked but it does not scan or anything. A couple of seconds later I get the message that the WiFi process in the settings app is not responding together with the option to kill the process. Is my WiFi broken now? Or is there a fix?
Thanks in advance
P.S. I'm using CM7 7.1.0
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
It doesn't work. When I boot after applying the update after the bootanimation there's just a black screen. It hangs. I pulled the bat and tried it again but the same...
Usually this can be solved by wiping the dalvik cache, have you tried that?
henkdv said:
Usually this can be solved by wiping the dalvik cache, have you tried that?
Click to expand...
Click to collapse
I managed to update CM7 to 7.1.0.1, but Wi-Fi is still not working! It just hangs after switch-on. And the weirdest thing of all is that it just happened, I dind't change anything or install any new apps...
Try reflashing the radio?
3xeno said:
Try reflashing the radio?
Click to expand...
Click to collapse
Reflashed the radio, still no progress It just wont find any wifi networks and after leaving the settings app the WiFi is turned off automatically (or the app hangs and the same happens) Any other suggestions?
By the way, WiFi-Tethering does work. Still confused about this weird problem :S
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
henkdv said:
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
Click to expand...
Click to collapse
Could you explain these steps? I'm not so familiar with terminal inputs and especially IP adresses. Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now). Isn't this a software problem?
tobitronics said:
Could you explain these steps?
Click to expand...
Click to collapse
Sure, here's the html formatted manual page. A relevant excerpt:
ip link set - change device attributes
dev DEVICE
DEVICE specifies network device to operate on. When configuring
SR-IOV Virtual Fuction (VF) devices, this keyword should specify
the associated Physical Function (PF) device.
up and down
change the state of the device to UP or DOWN.
Click to expand...
Click to collapse
When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.
tobitronics said:
Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now).
Click to expand...
Click to collapse
The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler.
tobitronics said:
Isn't this a software problem?
Click to expand...
Click to collapse
I see no reason to believe the contrary.
henkdv said:
Sure, here's the html formatted manual page. A relevant excerpt:When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler. I see no reason to believe the contrary.
Click to expand...
Click to collapse
I've tried your steps. When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'. It also says something about a loop? When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'. I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused . I hope this problem can be solved....
tobitronics said:
When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'.
Click to expand...
Click to collapse
This is the RFC2863 state of the interface which is seldom relevant, the actual link state is between < and >.
tobitronics said:
It also says something about a loop?
Click to expand...
Click to collapse
That would be the loopback device. It is always present and its parameters are the same across nearly all Linux kernels, one might be funny and try to change the mtu, queueing discipline or address but it's pointless to do so.
tobitronics said:
When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'.
Click to expand...
Click to collapse
According to the documentation, DORMANT means
Interface is L1 up, but waiting for an external event, f.e. for a protocol to establish. (802.1X)
Click to expand...
Click to collapse
This could indicate a problem with wpa_supplicant rather then the radio firmware. Try to connect to an open AP such as the ones at the local Bakker Bart, NS station, McDonalds or T-Mobile shop.
tobitronics said:
I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused .
Click to expand...
Click to collapse
It is the actual source code to "Wi-Fi settings" where you normally see the list of networks.
Thanks for your explanation. So what should I do/try now? I was thinking about reinstalling the settings.apk and settingsprovider.apk ....
Sent from my HTC Wildfire using XDA App
Like I said, try an open 802.11a/b/g access point.
henkdv said:
Like I said, try an open 802.11a/b/g access point.
Click to expand...
Click to collapse
I tried that at the McDonald's and it didn't want to search for available networks, so I couldn't connect
Go to settings > Wireless & Networks. Disable this option
Mobile network
Use phone for data connection when Wi-Fi is unavailable
It should change to
Mobile network
Connect to the Internet
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Takudenatsu said:
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
IT WORKSSS!!!! Thank you all for your help. That such a small little text file could cause such a large annoying problem. I hope it won't happen again...
Sent from my HTC Wildfire using XDA App
could you write how?
Under phone settings I keep getting ping ipaddr - fail, ping hostname - pass, HTTP client - pass. I still have internet and all seems to be working fine. I had a random MMS not send which led me to check my settings. Not sure why it keeps saying unreachable. The thing I've recently done was flash miui. I wiped then went back to mmuzzy's 4.2.2 ROM, I have the newest radio available. Anyone else experience this?
Unreachable could be your wifi router causing the problem. Try reboot the Router and see if it corrects itself.
Even if it occurs while I'm on mobile data?
dancingtortoise said:
Even if it occurs while I'm on mobile data?
Click to expand...
Click to collapse
I am having the same issue.
Ping IpAddr: Fail IP addr not reachable
Ping Hostname(www.google.com): Fail: Host unreachable
HTTP client testass
Data seems to be working otherwise.
any one can solve this??
Hi,
This is my first post, on this great forum, so I'm posting as a "noob"...
So my problem :
- I installed the LegacyXperia 20130908 CM10.1 release. It was working almost OK
- But because of the high wifi drain, I gave the lated DarkKernel a try (http://forum.xda-developers.com/showthread.php?t=2451839)
It seems to perform very good BUT I just noticed something really weird : I have access to the internet through my wifi LAN, I can ping my gateway BUT nothing else works on the local LAN :
ping fails :
[email protected]:/ $ ping -c 1 192.168.1.13
PING 192.168.1.13 (192.168.1.13) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=1 Destination Host Unreachable
The arp table seems incomplete :
1|[email protected]:/ $ arp -a
d810.home (192.168.1.13) at <incomplete> on wlan0
livebox.home (192.168.1.1) at 00:1f:95:26:25:4d [ether] on wlan0
The routes seem ok, the ip neighbours are not :
[email protected]:/ $ ip route show
default via 192.168.1.1 dev wlan0
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.10
192.168.1.1 dev wlan0 scope link
[email protected]:/ $ ip neighbor show
192.168.1.13 dev wlan0 FAILED
192.168.1.1 dev wlan0 lladdr 00:1f:95:26:25:4d STALE
AH, on more weird thing, the kernel arp table has lots of zeroes for the unreachable devices MAC adresses (yes, I have 192.168.1.13 and 1.15 are up and running) :
[email protected]:/ $ cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.1 0x1 0x2 00:1f:95:26:25:4d * wlan0
192.168.1.15 0x1 0x0 00:00:00:00:00:00 * wlan0
And I can't seem to be able to communicate with the local LAN only with the android phone...
I have static IPs in my DSL router, I can't set the arp tables manually.
I *think* this was all working with the default ROM kernel, but before I attempt to revert back to that kernel to check (I backed up the modules, but yet another noob thing, I'm not sure putting back the tar into /lib/modules will be enough...) :
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Since it's my first post (only 9 remaining now !), I can't post in dev section...
Thanks && regards
Did you flash the DarkModules?
Hi,
Yes i did flash them in cwm...
fschaer said:
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Click to expand...
Click to collapse
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155
Someguyfromhell said:
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155
Click to expand...
Click to collapse
Hi,
Thanks for the reminder.
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
and it appeared after i flashed this new kernel which seems better for the battery.
I think this is a kernel/wifi modules issue, not a rom one.
Or a noob error, but then i hope some of you can help me understand my error
As i said, wifi is somehow working since i'm replying just now using it...
It's just that apart from the dhcp/gateway, my device seems unable to learn any mac address with this kernel.
I haven't tried a tcpdump for now, and i wanted to test ipv6 but my 'great' dsl/wifi box does not support v6 - yes, that still exists...
Regards
fschaer said:
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
Click to expand...
Click to collapse
He is also developing the kernel together with his team, which is given within the .zip file.
Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers
fschaer said:
Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers
Click to expand...
Click to collapse
Which DNS server are you using? Did you change anything else by WiFi?
The captcha is only for limited amount of posts, then it will disappear.
I did not change any dns setting, but i saw local names in the terminal, so i must be using my dhcp/box dns.
You remind me i unchecked the wifi optomizations with the new kernel: i read this was causing arp issues on nexus devices...
Lets try to re-enable that... appart from this, i changed nothing after i flashed this kernel.
Except I tried 1.8ghz (it worked well), but this disappeared sincei restored the official rom krtnel
Thats really all i changed since i tried the new kernel yesterday evening
Can you believe this...
- Restoring the wifi optimisations did not help
- rebooting the DSL box helped. For 5 minutes.
I was able to ping a computer on the network, but not to go to the dsl box webserver. and I lost internet.
- subsequent dsl box reboots did not solve anything : no internet, no webserver, no connexion even on the wired PCs , powerd them on or off, nothing.
- *unplugging* everything + dsl box reboot => did restore internet+wifi on the arc
- replugging the PCs did not break
- and I can now see/ping the LAN with the arc s
Only remains, now, the dlink switch I have downtstairs that is the only stuff that remained plugged all time (theres a device on it, but it's off)..... It must have switched to a "netkill" state somehow. Funny, isn't it ?
let's now start wireshark, reinstall the new kernel, and see if there is any difference... and lastly reboot/replug the dlink switch
the come back for the (arp) ping of death ?
Regards
Last experiments:
- fired wireshark, to capture any network suspicious paquets
- reflashed the new kernel+modules
- retried ping / local LAN
Still working.
I rebooted my last network device (dlink switch), repluggued it : everything is still working.
conclusion : I don't understand :laugh:
Cheers
Hi,
I have read almost everything that this forum gave me and some solution from the rest of the internet and STILL my wifi mac address is still stcuk at 02:00:00:00:00:00
Wifi won't turn on and it won't display available wifi
I can't remember exactly what caused it but i'll try to share my recollection
I vaguely remember that i was able to connect to the wifi before trying to fix it. Can't recall what really happened
I fixed the random rebooting nexus 5x by using unblod fix
I think i tried rooting it and succeeded with a twrp recovery
I vaguely remember flashing a zip custom rom with wrong version and brought it into a soft brick. Cant find the file anymore.
I reflashed it with flash all batch file from stock firmware
the phone is bootlooping
Fixed it again using unblod exe using the stock firmware's boot.img
Wifi wont turn on
mac address is 02:00:00:00:00:00
Tried on android 6.0, 7.0, 7.1.2, 8.0 and 8.1.0
Other solutions tried:
Nil Mac app. Seems to work app wise but mac is still stuck at 02:00:00:00:00:00 on settings. Wifi wont turn on
Manually edited, placed *.bin file in /persist, and /etc/firmware/wlan/qca_cld/
WIfi mac changer apps from appstore (they dont work)
Some root apps that mess with the phone's setting (cant find anything that seems to deal with wifi mac address)
p.s.
I also tried bricking the phone using TWRP wipe and checking all the wipe locations to eliminate remnants from previous mods
I cant seem to do anything. Still stuck at 02:00:00:00:00:00
Any more suggestions on where to look?
Or is android not getting the real mac address and revert to 02:00:00:00:00:00 and wont let wifi turn on during flash all script?
Thanks in advance.
Recent Android hides the MAC address to prevent tracking. 02:xx:xx:xx:xx:xx means a site-local MAC address.
Try using "ip link" and looking for the wlan0 entry. eg.
Code:
22: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 3000
link/ether 2c:59:8a:xx:xx:xx brd ff:ff:ff:ff:ff:ff
nowster said:
Recent Android hides the MAC address to prevent tracking. 02:xx:xx:xx:xx:xx means a site-local MAC address.
Try using "ip link" and looking for the wlan0 entry. eg.
Code:
22: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 3000
link/ether 2c:59:8a:xx:xx:xx brd ff:ff:ff:ff:ff:ff
Click to expand...
Click to collapse
HI,
thanks for the reply. I already did that and i got a mac address that is not 02:00:00...
then i tried to change it using if config just to see if it changes using the command.
I got an error saying wlan0 not found (not exact words)
Is there a different MAC address in Settings -> System -> About phone -> Status ?
nowster said:
Is there a different MAC address in Settings -> System -> About phone -> Status ?
Click to expand...
Click to collapse
No, it is 02:00:00:00:00:00.
arviverona said:
No, it is 02:00:00:00:00:00.
Click to expand...
Click to collapse
Did this ever get fixed? I'm facing the same issue. However, the steps I did was trying to spoof a MacAddress using Busybox and a terminal emulator.
Just using that would not allow me to connect to wifi, but wifi was turned on. Then I read to change the wlan.bin file in the persists folder.
After I changed that file and did a reboot wifi would not turn on.
I tried:
1. factory reset
2.Changing the wlan.bin back to what it was
3.Sideload android 8.0
4.Flash OEM back to factory
Nothing seems to work. Settings->about->status MacAddress says "unavailable", but
wifi -> preferences -> advance shows MacAddress 02:00:00:00:00:00
Any help would be great,
-realkewl
Try AMC, its the only MAC Address Changer app I could find that worked on my 5x. That was without a screwed up MAC address to begin with, but It might work for you.
I downloaded it from the play store, but now its not there. Here's the apk from my phone:
https://sqerk.com/pythonlimited.amc.apk
Looks like AMC was forked from nMAC :
https://forum.xda-developers.com/android/software-hacking/app-nmac-nil-mac-changer-t3391283
sqerk said:
Try AMC, its the only MAC Address Changer app I could find that worked on my 5x. That was without a screwed up MAC address to begin with, but It might work for you.
I downloaded it from the play store, but now its not there. Here's the apk from my phone:
https://sqerk.com/pythonlimited.amc.apk
Looks like AMC was forked from nMAC :
https://forum.xda-developers.com/android/software-hacking/app-nmac-nil-mac-changer-t3391283
Click to expand...
Click to collapse
Thanks, but I figured it out. I was trying to flash with the same version 8.0...and for whatever reason that did not work, so I tried a costume ROM and it brought back my MAC address, so then I flash again to android 8.1 and my MAC address problems are fixed. Not sure why flashing with the same version did not fix it.
Thanks,
realkewl
realkewl said:
Thanks, but I figured it out. I was trying to flash with the same version 8.0...and for whatever reason that did not work, so I tried a costume ROM and it brought back my MAC address, so then I flash again to android 8.1 and my MAC address problems are fixed. Not sure why flashing with the same version did not fix it.
Thanks,
realkewl
Click to expand...
Click to collapse
What Custom ROM did you use friend? I have the same exact issue with my Nexus 5. Maybe finding your previously installed Custom ROM, I can fix the issue too. I saw a lot of threads says that installing Custom ROMs or downgrading then upgrading OS using OTA updates given from their Android System fixed the issue. MAC address is important and controls everything that has to do with wireless connections in your device. Maybe this can help be fix my issue too. I am almost convinced to buy a brand new smartphone. It's almost my limit here... If this doesn't bother you, please, can you tell me what is the ROM you used?
Background: oneplus 5t with lineageos 16
Can detect WiFi signals but wouldn’t connect to my own WiFi but mobile hotspot & other people’s WiFi
what was on my screen after i entered the password:
connecting...
saved...
connecting...
saved...
after a while
Disabled
My other devices have no problem with WiFi connection
Super weird, isn't it? does anybody have any idea how to fix this?
Trials and errors:
1. Changed WiFi frequency: 2.4GHz & 5.0GHz
didn’t work
2. Changed WiFi name & password on both frequencies multiple times, i even made my wifi public with no password(2.4GHz & 5.0GHz), still my oneplus won't connect
didn’t work
3. Reset network settings on oneplus
didn’t work
4. Rebooted my router and phone
didn’t work
Maybe try a clean install. Backup then wipe : system, data, cache, dalvik. Then reflash. Titanium backup app is recommended.
sasali said:
Background: oneplus 5t with lineageos 16.........
Click to expand...
Click to collapse
I don't have this device myself but, you may want to see if you can locate/obtain some support and guidance within the following Official LineageOS 16.0 thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3843026
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Is *your* wifi SSID hidden? If so, forget the connection on Lineage 16.
Re-add it:
When you add it back, *before* you enter the password and hit save, hit Advanced and make sure "Hidden network" is ticked.