Related
I've managed to build a version of wpa_supplicant that has ad-hoc enabled, by forward porting the patch in this thread:
http://forum.xda-developers.com/showthread.php?t=754961
After building and a couple of tests, it works.
To install, you need a rooted Xoom, of course, and just push the file to system/bin/wpa_supplicant.
Because zipfiles don't store permission, you have to make it executable as well.
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
adb shell chmod 755 /system/bin/wpa_supplicant
I also had to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Then reboot, and try it!
It works with my Nokia N8 with JoikuSpot; I can't tether it any other way as the N8 doesn't support the PAN Bluetooth profile, and Android doesn't support DUN.
Don't forget to backup your files, and I am not liable, etc, etc.
The code I used is here:
https://github.com/kelvie/android-wpa_supplicant
Ok heres what happened to me..
I was able to push the first file and when I input the adb shell code it said the device was not connected I am rooted and had no problems rooting or access shell before
So I got a little cocky and thought that the port 5037 that adb communicates with was blocked so I typed adb tcpip 5036 to see if I could get shell access on that port well now when I type adb remount it immediately tells me error: device not found....help!
Got myself stuck without wifi (error)
Thanks for developing such a great app. If i m not wrong i think its working with all 3G carriers.
You can also turn your Motorola Xoom tablets to WiFi hotspot without rooting by enabling setting which are given here http://goo.gl/mgwdn
Also my xoom has been in debug mode and now all of a sudden I noticed that its not entering debug mode when connected there used to a little icon come up and not anymore it acts like nothing yet i can access it on my computer by going my computer and I see Xoom
Ok I got debugging mode back and xoom is plugged in now my problem is when the daemon server starts in adb shell it starts on port 5038
So when I try to copy "adb shell chmod +x /system/bin/wpa_supplicant" it still says device not found and thats if I copy and paste it exactly if I type adb shell it gives me the # Symbol then i put it "chmod +x /system/bin/wpa_supplicant" and it says bad mode
One good thing is I can now type /remount again so what I am doing wrong still stuck without wifi ;\
Ok I've tried everything except reflash my devices I've literally only been able to do step 1 which leaves me with no wifi because i cannot execute the shell commands so please a little help it's been a long night messing with this appreciate your time and I'd love to get this working!
kelvie said:
I've managed to build a version of wpa_supplicant that has ad-hoc enabled, by forward porting the patch in this thread:
http://forum.xda-developers.com/showthread.php?t=754961
After building and a couple of tests, it works.
To install, you need a rooted Xoom, of course, and just push the file to system/bin/wpa_supplicant.
Because zipfiles don't store permission, you have to make it executable as well.
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
adb shell chmod +x /system/bin/wpa_supplicant
I also had to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Then reboot, and try it!
It works with my Nokia N8 with JoikuSpot; I can't tether it any other way as the N8 doesn't support the PAN Bluetooth profile, and Android doesn't support DUN.
Don't forget to backup your files, and I am not liable, etc, etc.
The code I used is here:
https://github.com/kelvie/android-wpa_supplicant
Click to expand...
Click to collapse
Ok...I tried this and got the same "bad mode" error at the
"adb shell chmod +x /system/bin/wpa_supplicant" stage.
So, I instead did "adb shell chmod 700 /system/bin/wpa_supplicant" and that was successful, so I finished the steps listed and can see my cell on my Xoom. I have a Windows Mobile 6.5 cell and my Xoom can NOW see my ad-hoc network. Thanks a lot Kelvie.
If not for the SDCard update from BRD, I think this thread would be getting alot more attention.
Not to be too mistrusting, but I am hesitant about loading this on my Xoom when it is posted by a new user with only one post.
Fusius said:
Ok...I tried this and got the same "bad mode" error at the
"adb shell chmod +x /system/bin/wpa_supplicant" stage.
So, I instead did "adb shell chmod 700 /system/bin/wpa_supplicant" and that was successful, so I finished the steps listed and can see my cell on my Xoom. I have a Windows Mobile 6.5 cell and my Xoom can NOW see my ad-hoc network. Thanks a lot Kelvie.
Click to expand...
Click to collapse
Hey that worked instantly love you!
PengLord said:
If not for the SDCard update from BRD, I think this thread would be getting alot more attention.
Not to be too mistrusting, but I am hesitant about loading this on my Xoom when it is posted by a new user with only one post.
Click to expand...
Click to collapse
I completely understand where you're coming from; but check my github repo, and google for me, I do leave a small internet trail...
I (mostly used to, don't do much anymore but answer the odd email) maintain an open source project (Basket for KDE), and try to participate in open source communities as much as I can.
I just did this to tether my Xoom Wifi to my phone, as I had no other way to get internet on the go.
Nice work. I tried to do this myself last week but ran into trouble just getting wpa_supplicant from the Android git to compile (with or without the changes)
First off, wow man thank you so much. I've been playing with this for a while and I've tried a number of different wpa supplicant files but they failed to initiate a scan of wireless networks. I just tried this one and it works great. I wanted to explain a different way to install it however for the people having ADB issues.
First you want to turn off your wifi. I have used the ADB method a couple of times but I find it easier to use Root explorer. Save the file to your Xoom, Copy it using root explorer, navigate to the system/bin folder and click mount R/W then paste the file into the folder replacing the original (make sure to make a backup!) then long hold on the file and view permissions, check all the boxes in the first two columns and the first 2 in the last column. (chmod 775) You can then restart your wifi and enjoy ad-hoc networks (no reboot needed.)
I've done this a couple of times and it works great. Thanks again.
First off, thanks a ton to the OP for getting this working!
Also, thanks to mr_wrong_0 for the root explorer directions. Not that I'm incapable of using the command prompt, it was just easier to do it this way.
mr_wrong_0 said:
First off, wow man thank you so much. I've been playing with this for a while and I've tried a number of different wpa supplicant files but they failed to initiate a scan of wireless networks. I just tried this one and it works great. I wanted to explain a different way to install it however for the people having ADB issues.
First you want to turn off your wifi. I have used the ADB method a couple of times but I find it easier to use Root explorer. Save the file to your Xoom, Copy it using root explorer, navigate to the system/bin folder and click mount R/W then paste the file into the folder replacing the original (make sure to make a backup!) then long hold on the file and view permissions, check all the boxes in the first two columns and the first 2 in the last column. (chmod 775) You can then restart your wifi and enjoy ad-hoc networks (no reboot needed.)
I've done this a couple of times and it works great. Thanks again.
Click to expand...
Click to collapse
Thanks so much for this! No issues at all. Wifi Xoom is tethered to my HTC Hero now.
Congrats on a killer mod! We are making progress nice and steady.
Installed, works great.
Thank you.
Great, thanks for your hard word.
I do have a question for those how have done this hack. I currently have an old iPhone 3g with tetherme installed and use Bluetooth tethering to give my Xoom (wifi only) internet access. This works great for me.
Is there are speed/battery life advantage to using wifi tethering instead?
Cheers
I don't know for sure. From what I understand wifi is potentially faster than bluetooth, but it can vary from device to device. I have noticed that my Epic seems to stay cooler and use less battery when broadcasting an Ad-hoc network vs broadcasting in infrastructure mode (using wifi tether 3.0.) But I've never been able to get my phone to tether with bluetooth so I don't know about battery life. One advantage of connecting over wifi is file sharing via apps like wifi file explorer. I have used that a lot to transfer files between my Xoom and my phone as well as the computer.
Noob question
Hello all,
Thank you very much for the patch.
I would like to try it out, but before that, I need to make sure of one thing;
If I root my Xoom, will I still be getting future updates from Motorola for the device if there is one? Or once I root it, is it impossible for me to update them from the manufacturer?
Thank you!
Thanks so much to the OP! I've been waiting for a reason to root my wifi Xoom. SDCard access was tempting, but I think this is the thing that pushes me over the edge!!
Thanks!!
Hi all,
having troubles with my Wifi. It needs a minute to connect and doesn't connect when screen is off eventhough settings are to always on.
I started asking in CM7 nightly thread about my problem but it's better to have a new thread for that.
So far I didn't find a solution.
I tried:
- replace tiwlan_drv.ko with new one by deleting old one
- compared wpa_supplicant, tiwlan.ini and other data in that folder without significant outcome
- tried old 2011.11.16-nightly where it still worked
Anyone got an idea what I have to copy from my old nightly where it still worked?
This is what happened:
measel said:
sorry, for bringing this up again, since I'm the only one having this issue but I just collected a few logs. maybe someone has a clue what is going on there:
Code:
2012-02-13-19-35-37_wifion.txt > when turning wifi on it needs more than a minute to connect
2012-02-13-19-37-37_wifiscan.txt > wifi instantly connects after starting 'wifi analyzer' app or open the wifi settings window
2012-02-13-19-45-25_wifiscreenoff.txt > when screen is of, wifi doesn't connect eventhough settings are to "always on"
/edit: ok i just tried to read the logs myself and I think you can't really see any reason for that behaviour... am i right that the possible settings I have to look for are in the 'tiwlan.ini'?
Maybe someone provide me a backup of his/her tiwlan.ini for comparison... (I don't have any idea what I'm doing but that doesn't mean I couldn't try. )
I added my tiwlan.ini as well
/edit: compared to tiwlan.ini: no differences. Must be something else.
Click to expand...
Click to collapse
measel said:
Could you please check your logs if it needs exactly a minute to connect? could be a proof that there is some setting involved.
Click to expand...
Click to collapse
measel said:
I just went back to an older version: 2011-11-16 and the problem was gone.
Thank you.
/edit: Ok might have bin the wrong folder... did it have to be /data/misc/wifi/? Argh it's hard when one knows nothing. :|
/edit2: I'm so sorry: I compared wrong files and folders (system and data). I come back here, when I really found something. *shame on me*
Click to expand...
Click to collapse
[] AL [] said:
I'd just copy the module tiwlan_drv.ko [in /system/lib/module] from that older nightly and replace it on the newer build first.
Don't forget to set its permissions afterwards..
You can do this with RootExplorer or with Terminal (from the app tray) by entering these 5 lines:
Code:
su
cd /system/lib/module
mount -o remount,rw /system/
chmod 644 tiwlan_drv.ko
chown 0.0 tiwlan_drv.ko
and reboot.
Click to expand...
Click to collapse
none of these solutions worked right?
I have wifi problems too. Wifi in CM7 is crap
No wifi problems here... I'm using my personal home wifi network most of the time, but other networks works well too.
Red lense German Vodafone Froyo based
CM7.2 Nightly 02102012
I have this issue if I configure my Router security to WPA. With open I can connect immediately
crakeron said:
none of these solutions worked right?
I have wifi problems too. Wifi in CM7 is crap
Click to expand...
Click to collapse
can't really say that. It's great in 111116-nightly so I just wanna figure out what I have to change to get the speed back!
Motorola Defy CM72120121, german Froyo base
I have this problem, too.
Nobody else?
Would be great if some devs could please look this up.
SOLUTION
Hello all,
first off: delete wpa_supplicant and everything is fine!
I gave up and did a factory reset/wipe data. After that it worked w/o problems.
> Now I will restore all my apps and check if it's still working afterwards. > still working
> restore wifi access points > NOT WORKING ANYMORE!
> with shame I delete wpa_supplicant > WORKS AGAIN!
I'm so ashamed. :/ Should have done that like months ago.
I go back to my backup and try it there. > deleting the wpa_supplicant worked!!!!
My Wifi has a problem with WRT54G Wireless Router, with Froyo Stock ROM and CM7.1 RC1.5-jordan.
WIFI connect, signal is good but connection is very slow.
On notebooks, the connection is faster with this same router.
In another Wireless routers connection is normal from Defy. The problem is only between Defy x Linksys WRT54G.
I have set Defy and Router to work only in G mode, but the problem persist.
With the same configurations the problem don´t occour with another routers from D-link, Cisco or other.
Anyone know how can I solve it?
Tnks.
[I didn't realize there is this HTC Desire specific subforum, so I'm copypasting my question from General Q&A forum].
I've been running Miui happily for over a year on my HTC Desire, just to notice last week that wifi works only right after power-up (not reboot!) and until switched off. After that, it won't start again. I've tried different things, roms, clean installs, just to confirm the same behaviour, regardless of the rom installed. Detailed explanation is available here:
[EDIT: Being a new member, I'm not allowed to post links. So here it is, 'unlinked': http is.gd slash pZ1TDo ]
(includes logs and everything).
Please help, what to do next?
Thanks,
MB
When you have the error, open a terminal and type dmesg.
Please paste the output here.
You can redirect the output by typing "dmesg > /sdcard/file.txt" ( Without quotes )
dqb said:
When you have the error, open a terminal and type dmesg.
Please paste the output here.
You can redirect the output by typing "dmesg > /sdcard/file.txt" ( Without quotes )
Click to expand...
Click to collapse
Hello, thanks for reply.
Here's the output (too big for copypaste here):
http ge.tt (slash) 3nqEYdF/v/0?c
Sorry, still not allowed to paste links.
The bcm4329 module seems ok.
Sometimes when i use the widget to power on/off wifi, it won't connect.
To get wifi working, I go into wifi settings and power on the wifi here.
Could you try like this and tell us if this working ?
dqb said:
The bcm4329 module seems ok.
Sometimes when i use the widget to power on/off wifi, it won't connect.
To get wifi working, I go into wifi settings and power on the wifi here.
Could you try like this and tell us if this working ?
Click to expand...
Click to collapse
I tried all of the combinations - settings/wireless, status bar, specific widgets - nothing works. At least I have consistent behaviour
This is my original post on miui forum (when I thougt it was miui related). It explains what actions I performed while trying to nail the problem. Still no luck.
Code:
Hello,
Recently I've noticed that wifi on my HTC Desire is acting very strangely - it connects just the first time after reboot, every other time I get "Error" message in Wifi settings. Where I can check what actually went wrong?
After looking in the logs, I hope to have more information on this issue, but for now I believe it's hardware related, since the same problem appears even with the fresh install of the latest MIUI or after restoring a backup.
Thanks.
mblenton, Monday at 9:59 PM Edit Report
#1 Reply
Google Adsense
Pele
Admin
Message Count:
278
You can use the MIUI Android Logcat miuiandroid.com / community/link-forums/logcat.82/
Or you could try a fresh download install again : reboot into cwm, factory reset > wipe dalvik > clear cache partition install rom
But try the logcat and also check you router etc and other things that may influence.
Regards
If you require more help speak to ibotpeaches as he is a HTC expert : join the miui irc chat :)
MIUI Android Logcat System
MIUI Android Statistics
...Im all about the end user
Samsung Galaxy S I9000 & I9100 Expert
Black Android Theme Developer Website & Twitter
Pele, Monday at 11:34 PM Report
#2 Like Reply
mblenton
Members
Message Count:
7
Hello Pele,
Thanks for the reply.
I've tried already clean install with wiping everything, even restored an old bkp which for sure is correct, but all without luck. I don't think it's a router thing, since the same problem appears regardless of my location (at home, at work... all the same). I'll join the miui irc chat, good idea, thanks!
Regarding the logcat - the link you sent is just a form for pasting logs - am I seeing it correctly?. Is there some specific miui logcal app? I've installed 'aLogcat' which seems good, but I couldn't find anything on *wifi* or *wpa* which could indicate some sort of error in any of the logs aLogcat is displaying.
Cheers,
mblenton
mblenton, Tuesday at 9:30 AM Edit Report
#3 Reply
Pele
Admin
Message Count:
278
Hi,
Try to restore your back up without wifi settings. Failing that yes come to irc chat for about 12pm GMT+0 and chat with ibotpeaches
Regards
MIUI Android Logcat System
MIUI Android Statistics
...Im all about the end user
Samsung Galaxy S I9000 & I9100 Expert
Black Android Theme Developer Website & Twitter
Pele, Tuesday at 10:31 AM Report
#4 Like Reply
mblenton
Members
Message Count:
7
Hello Pele,
I've tried several combinations of rom/backup flashing, titanium backup restore etc. but the problem persists, even on a clean installation with just one accesspoint defined.
mblenton, Tuesday at 3:09 PM Edit Report
#5 Reply
mblenton
Members
Message Count:
7
Update: I've updated to the newest radio, but the problems are still there.
mblenton, Tuesday at 3:51 PM Edit Report
#6 Reply
iBotPeaches
Admin
Message Count:
569
Yes, you need a logcat to further figure this out.
developer.android.com / guide/developing/tools/logcat.html
Freenode #miuiandroid
iBotPeaches, Tuesday at 6:51 PM Report
#7 Like Reply
mblenton
Members
Message Count:
7
Hello iBotPeaches, thanks for the link, I didn't realize Pele's refering to that logcat. I'll have to set up abd, though.
In the mean time, I've tried the following (plus the actions described earlier):
- Format system and boot partitions (since Wipe Data/Factory Reset doesn't do that) and clean latest miui install
- Clean Cyanogenmod install
Nothing's changed, I still can connect to wifi network the first time after power up, and then all I get is 'Error' msg. Interesting, but reboot doesn't actually help, just power off/power on.
mblenton, Tuesday at 9:04 PM Edit Report
#8 Reply
mblenton
Members
Message Count:
7
Hello again,
I've installed adb and used logcat to generate this file: ge.tt /9UkgUaF/v/0?c
I'm not quite sure what would be interesting for debugging purposes, so I performed the following procedure:
0. Wifi is enabled, but not working; power down the device; start adb logcat - waiting for device -
1. Power on (wifi will be enabled and connected to SSID Hotspot)
2. Open browser, open google (everything works)
3. Close browser, turn off wifi (via status bar, but it doesn't make any difference)
4. Open settings, try to turn on wifi
5. Wifi couldn't be turned on, 'Error' message is displayed
6. Power down the phone
Thanks in advance!
mblenton, Yesterday at 10:36 AM Edit Report
#9 Reply
mblenton
Members
Message Count:
7
Yet another update, not I'm pretty sure this issue is not miui related.
I've installed Gingerbread RUU and performed the power-on/wifi-on--works/wifi-off--won't-start-anymore procedure with the same results. Here are the logs: ge.tt /9sOVXbF/v/0?c
Where I should look for help?
Ok, after you got the error, go in a terminal and type lsmod ( list loaded modules )
If you see the bcm4329 loaded ( wifi module ), go in a terminal and type modprobe -r bcm4329 ( unload module )
Verify with lsmod if the module is unload.
After that, try to activate the wifi in settings/wireless. Twice if the first gives you an error, it should "unload" the first time, and the second time it should load.
I just tested by inducing an error.
Tell us is this work !
Hello again,
I've tried what you suggested, and this is the result:
Issuing lsmod while wireless is OK:
bcm4329 200131 0 - Live 0xbf000000
After turning off wireless, lsmod doesn't display anything.
After trying to turn wireless back on, lsmod also doesn't display anything, regardless of the times I tried to turn wireless on (and getting Error every time is Settings)
modprobe bcm4329 returns
modprobe: 'bcm4329.ko': invalid parameter
insmod bcm4329 or bcm4329.ko says it can't open bcm4329 (.ko)
So, the linux system under the android seems to be working ok.
Hi,
Ok, after power off/on wifi, the driver doesn't load :/
With some tests and by inducing an error, it works on my side
When you have the error, try this as root :
Code:
su
lsmod ( if bcm4329 is loaded then rmmod bcm4329 )
svc wifi enable ( it's to turn on wifi manually, I waited a few seconds, and everything was properly unloaded ! And wifi off.. idk why )
svc wifi enable ( if the first time it didn't work, it worked for me, it might work for you )
svc wifi disable
but I've intentionally caused an error, not you. And i think that svc is the same as widget/settings..
BTW, for insmod you need to give the full path of the module : /system/lib/modules/bcm4329.ko and the fw path, but it will not work like that you need to set/config interface etc.. I'll try to do it manually.
I just looked quickly one of your old logcat because i'm tired and i'm going to sleep, I'll look more in detail this night if we can find the most important thing : what causes this problem.
dqb said:
Hi,
Ok, after power off/on wifi, the driver doesn't load :/
With some tests and by inducing an error, it works on my side
When you have the error, try this as root :
Code:
su
lsmod ( if bcm4329 is loaded then rmmod bcm4329 )
svc wifi enable ( it's to turn on wifi manually, I waited a few seconds, and everything was properly unloaded ! And wifi off.. idk why )
svc wifi enable ( if the first time it didn't work, it worked for me, it might work for you )
svc wifi disable
but I've intentionally caused an error, not you. And i think that svc is the same as widget/settings..
BTW, for insmod you need to give the full path of the module : /system/lib/modules/bcm4329.ko and the fw path, but it will not work like that you need to set/config interface etc.. I'll try to do it manually.
I just looked quickly one of your old logcat because i'm tired and i'm going to sleep, I'll look more in detail this night if we can find the most important thing : what causes this problem.
Click to expand...
Click to collapse
Hello,
Thank you for attepts to help me, unfortunatelly none of your advices haven't succeeded to turn on wifi once it was turned off. I don't know what to do next. I actually keep it turned on all the time, and it works OK. Not quite happy with that
Hi mblenton,
Ok
I just found how to really turn on the wifi manually.
First, in a root terminal run : getprop wifi.interface, I have eth0, if you have another interface, replace the following by yours.
After error, make sure your eth0 interface is down by running in a root terminal "netcfg" you'll not find eth0 interface, or "ifconfig eth0" must return " eth0: No such device " same for "iwconfig eth0".
If eth0 is up, run as root : "ifconfig eth0 down" and retry to turn on wifi as usual.. maybe it will work.
If not, make sure bcm4329 module isn't loaded ( lsmod ), make sure eth0 is down and try this :
Code:
su
modprobe bcm4329 firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin
start wpa_supplicant
dhcpcd -BKL eth0 &
If "modprobe bcm4329 firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin" return you an error, try this :
Code:
insmod /system/lib/modules/bcm4329.ko firmware_path=/system/vendor/firmware/fw_bcm4329_apsta.bin
But it's better to load a module with modprobe.
What the commands do :
1) Be root
2) Is for loading module and firmware properly
3) Start wpa_supplicant as service with right user, and load your wireless config
4) Run dhcpcd on background for getting an ip by dhcp ( which implies not have configured the ip manually )
If the wireless icon is not activated in notification bar, it's normal.
ping -c2 google.com or open a browser and try a google search, it worked for me..
If it work for you, cool, we can make a bash script to get the wifi works temporarily, the time to found the cause of the malfunction !
A guy that I helped had a problem with bluetooth, it was a permission problem.. he found a fix :
Daiksi said:
with rom manager i did fix permission and IT WORKED!!!!!!!!YATTA!!!
Click to expand...
Click to collapse
Try that, it can only do good things !
Hello,
I've tried what you suggested, including permission fixing, and the situation remained the same. I'm surprized there's nothing in the logs, though.
Thank you once more.
OK, several folks have reported Wi-Fi issues with LK8 so I'm making a thread for that.
Please document your problems here so I can help troubleshoot. Logcats are a BIG help when it comes to this.
Thanks!
I have wifi issue on any lk8 rom. I am fine with ljc to lk8 as long as i stay on ljc based rom. When i flash any lk8 rom I get wifi failed to connect or ocasionally it says connected but no traffic. I have tried dirty install on lk8 rom and clean install of lk8 rom several times same result. I go back to ljc and do the chameleon fix and all good.
cajun9924 said:
I have wifi issue on any lk8 rom. I am fine with ljc to lk8 as long as i stay on ljc based rom. When i flash any lk8 rom I get wifi failed to connect or ocasionally it says connected but no traffic. I have tried dirty install on lk8 rom and clean install of lk8 rom several times same result. I go back to ljc and do the chameleon fix and all good.
Click to expand...
Click to collapse
Can you share your Wi-Fi settings?
Don't need the SSID or PW, need to know what security you're running mainly.
I'm on WPA2-PSK and having no issues on LK8.
Most JB builds seem to have problems with WEP, especially if using a second layer security...
I have tried all the different wifi security settings and also no security still nothing. Spent a whole night trouble shooting wifi. Tried changing ip to static still nothing. At times it will show connected but no internet. No problems at all on ljc rom. Other android phone and notebook connect just fine.
cajun9924 said:
I have tried all the different wifi security settings and also no security still nothing. Spent a whole night trouble shooting wifi. Tried changing ip to static still nothing. At times it will show connected but no internet. No problems at all on ljc rom. Other android phone and notebook connect just fine.
Click to expand...
Click to collapse
What settings do the router have set up? (Or do you not have access to it?)
Perhaps the easier way is to do this in ADB from LJC:
Code:
$ su
# cp /data/misc/wifi/wpa_supplicant.conf /sdcard/
This makes a new file in you USB memory called wpa_supplicant.conf - it's the raw wi-fi settings.
Then copy/paste the contents here removing any SSID or PW.
If you can do for LK8 as well then we can probably see if there's a configuration change there.
If you'd rather you can PM this info to me as well.
Last thing to do would be a logcat.
First, turn off Wi-Fi in LK8 and clear the log:
Code:
$ su
# logcat -c
Then turn on wi-fi, let it fail. Let's dump the log now:
Code:
$ su
# logcat -d > /sdcard/logdump.txt
(Doesn't need to be logdump.txt, can be whatever)
Note: You can skip su step if you keep ADB open, only need to do once.
Then .ZIP and attach or put up on pastebin/dropbox/etc and post or send me a link.
Happy to troubleshoot it as much as possible!
Final possible step - wipe the wi-fi information out.
Turn off wifi first before doing this:
Code:
$ su
# rm /data/misc/wifi/wpa_supplicant.conf
...and see if it will pick up and just let you fill in the missing parts.
Hope this helps!
So I recently switched carriers and couldn't get a signal out of the box with my OP5T. After digging around on some blogs I found users who were able to get it working by enabling VoLTE by changing some settings and flashing two files using EfsTools.
The process was basically to install OnePlugLogKit. Dialing #*800# to access the settings, enabling VoLTE there.
And then Dialing #*801# to get into that menu, enabling full port switch and connecting the device to a PC.
Using EfsTools, I flashed two files mcfg_autoselect_by_uim and mcfg_sw.mbn using these commands:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
and
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
Restart the phone and BOOM, the VoLTE icon appears and it connects to the network.
The first time I did this, it worked perfectly and I assumed that the fix was permanent. It was also supposed to transcend any software updates/wipes because I'm flashing something to the modem if I understood correctly.. ?
But then I visited another country and used a different SIM card, when I returned back my signal was gone again. I thought, okay maybe the new SIM card disabled it something, so I reflashed and it worked again.
This time however, it reverted back much more quickly and without any major changes that I could tell. I reflashed again just to see what would happen and the signal came back. Unfortunately the flash does not last long at all anymore. The most recent flash had it working for about 1 day and has now reverted back.
Is there any way I can check some log files to see what is causing it to revert back? I don't know what to do because yesterday I went out for a bit with the signal connected and working, and then just completely random it reverted back and I was left with no signal.
Appreciate any help.