So after going through Paul's guide for rooting my Desire, I did what I've wanted to do since I got the phone, put in the proper wireless settings (802.11x LEAP connection), which I've previously done on my Archos 5IT, which runs Android 1.6 without a problem, turn off wifi, put the device into Airplane mode, pull the file from't device, edit it, then push it back, out of Airplane, wifi on, boom, grand. Now though, I've made one or two edits to the file and when I push it back, it breaks the wifi. It won't turn on, it won't turn off and if I restart, it comes up only as "Unable to start wifi" and does nothing again.
Therefore, question is, is there any way that we can manually input wireless configs without breaking the wifi connector? I also tried "Wifi Helper" from the market (yeah, yeah, I know it says it doesn't work, but I thought I'd try it anyway!) and that didn't work either. Also, any idea why it is breaking, even with simple edits?
I edited mine and didn't break the WiFi, at least I can still connect to a WPA2 AP. I cannot test the LEAP profile (the one I changed) until tomorrow - I'll let you know if the changes work or not.
Thanks EnF70. I kept tinkering with it and used Root Explorer instead, to edit the file directly and it's actually worked and been more stable. I dunno if it was down to editing it with that, or me including "priority=1" and "priority=2" into the config, but it looks to be ok now. I also won't be able to check whether it works properly until tomorrow.
I can confirm that LEAP is working well
me too!
I'm not sure exactly what was causing my wifi manager to start crashing and becoming unstable, but I do know what's now fixed it. I stopped using adb pull and push and instead started using Root Explorer to edit the wpa_supplicant.conf file directly on the device, because there's a possibility that ownership or permissions were being messed up with the pull / push side of things.
so, after that, something that I've noticed is that the wpa_supplicant.conf file doesn't really like you plonking networks into it, willy-nilly (I think), you've gotta give it a bit more structure. anyway, this is now my file, with all the juicy bits taken out, but the config still good,
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="<ssid>"
scan_ssid=1
key_mgmt=IEEE8021X WPA-EAP
auth_alg=OPEN SHARED
eap=LEAP
identity="<leap ID>"
password="<leap Password>"
priority=1
}
network={
ssid="<other ssid>"
psk="<other password>"
priority=2
}
this now has me connecting perfect to the 802.11x LEAP account in work, while also maintaining other networks I have saved from elsewhere.
Related
Hi there,
by browsing a bit on the filesystem of my Hero, I uncovered some files called audio.conf, main.conf and input.conf in the /etc/bluez-directory.
Editing the contents (eg. discoverabletimeout) in it didn't do anything though -.-
I was wondering, if it's possible to get the bluetooth, working on the phone, to get its settings from these files, rather than from somewhere else (wherever that may be -.-)?
Running VillainRom 5.4, btw...
Sorry if I have misread your post, but doesn't Bluetooth work now on 2.1 ROMs?
I managed to transfer a photo to my friends phone last night via Bluetooth. I just went into the Gallery, selected a photo and then chose Bluetooth from the Sharing options. Worked straight away.
I'm using SenseHero 2.1
It DOES work, but you might want to tweak it a little
e.g. disable the timer for discovering the phone, etc...
Come on, there has to be some way...
This little **** won't connect to my handsfree anymore and I think this is related to some settings within these .conf-files...
So, after applying the official 2.1 Update, this little f***** keeps connecting, disconneting, connecting, disconnecting, connecting...
I'll never gonna buy HTC-stuff again... Fed up -.-
hey all anybody out there is able to connect to ad-hoc networks?
its the only thing that keeps me from using android cuz i use my phone as a link to the internet
I tried some stuff posted in other places but it didn't work
thx in advance
So you want to tether the data connection on your phone to your laptop, or the other way around...?
XDAndroid wifi tethering app - that'll allow you to tether your data cxn on your phone to a wifi enabled PC.
If you want the other way around... bleck, not sure.
i don't want to tether my brother uses the computer all the time and im stuck with ad hoc in winmo,
there is a solution all over the internet like this one http://exop.pro/blog/2010/08/15/ad-hoc-support-for-android/
but i don't know if it will support our phones because i don't know how to apply patches
p.s this requires a rooted phone whatever that means
husam666 said:
i don't want to tether my brother uses the computer all the time and im stuck with ad hoc in winmo,
there is a solution all over the internet like this one http://exop.pro/blog/2010/08/15/ad-hoc-support-for-android/
but i don't know if it will support our phones because i don't know how to apply patches
p.s this requires a rooted phone whatever that means
Click to expand...
Click to collapse
XDAndroid is already rooted... Comes that way.
You can try to apply the patch, no clue. Never used it.
So I assume the laptop has a wired internet connection, and it's being shared as an ad hoc connection thru the laptop?
I'd say two choices - try to fiddle with the patch, or just spend $30 and get an actual router
WTF!!!
Definitely go for the router, mate.
You are trying to solve a problem possibly creating a new one, but a hundred times bigger.
tried to mess with my system image by mounting it and replacing the files no luck at all (you will get error when starting wifi);
I should go for a faster internet connection such as wimax that comes with a router
thx for support guys
husam666 or anyone else who got this working,
I saw in another thread you got this working but you didn't say how. I tried to edit my froyo.user.conf but I didn't know what I was doing and it didn't work. Can you tell me how you got it to work? Which file and how to edit froyo.user.conf?
Specifically, I'm running Froyo7 on my Rhodium and trying to connect to an ad-hoc network that is broadcast from another cell phone (a Nokia--so no infrastructure available).
Thanks!
matt300 said:
husam666 or anyone else who got this working,
I saw in another thread you got this working but you didn't say how. I tried to edit my froyo.user.conf but I didn't know what I was doing and it didn't work. Can you tell me how you got it to work? Which file and how to edit froyo.user.conf?
Specifically, I'm running Froyo7 on my Rhodium and trying to connect to an ad-hoc network that is broadcast from my other cell phone.
Thanks!
Click to expand...
Click to collapse
Seems Android doesn't support ad-hoc out of the box, which it seems you already know.
I would much prefer to use a real AP, as opposed to anything adhoc. But that's just me.... What is your other phone? That isn't capable of putting up an actual AP?
lol, just read your sig. If the other phone is the Tytn, I feel your pain.
Actually, I still have the Tytn (still works!), but I'm using a Nokia E71 as my main phone at the moment. Too much of a pain to pop the sim card out when I want to use Android and the Nokia's Joikuspot (equivalent to WMWifi Router) is ad-hoc only.
yeah i got it to work actually, i found drivers somewhere, but sorry dude, it's been a long time and i forgot where
yeah i got it to work actually, i found drivers somewhere, but sorry dude, it's been a long time and i forgot where
Click to expand...
Click to collapse
If you get the time, could you copy the relevant lines out of your froyo.user.conf file?
I've tried two versions of the wpa supplicant I found, wpa_adhoc-signed from http://forum.xda-developers.com/showpost.php?p=7674767 and wpa6_adhoc-signed from another thread.
My guess is I was editing the froyo.user.conf incorrectly.
If there is some way to fix ad-hoc permanently, I wouldn't mind integrating it into the build. If stine is cool with it, it'll get baked into the system image. If he's not... I'll just include it with the bundle .
Let us know if you figure it out.
is it possible (in general) to put it in Infrastructure mode?
AkumaX said:
is it possible (in general) to put it in Infrastructure mode?
Click to expand...
Click to collapse
Not when using WMwifirouter (Windows Mobile) or Joikuspot (Symbian) as the access point. I don't keep my sim card in the Rhodium full time but it's nice to have internet on it when I need it.
Cool, Working!!
OK, I finally got it right. Here's what I did:
Downloaded the wpa_adhoc-signed.zip file from this post: http://forum.xda-developers.com/showpost.php?p=7674767
Copied just the wpa_supplicant file to the root of the sdcard (it's inside of the wpa_adhoc-signed/system/bin folder of that zip file)
Using Notepad++, inserted the following line into the froyo.user.conf file:
mount --bind /sdcard/wpa_supplicant /system/bin/wpa_supplicant see this post: http://forum.xda-developers.com/showpost.php?p=10984380&postcount=1
Here's how the last section of my froyo.user.conf file looks:
# custom shell commands, these commands run last
custom_shells{
chmod 777 /etc/dbus.conf
mount --bind /sdcard/wpa_supplicant /system/bin/wpa_supplicant
#echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
rm -f /sdcard/fsck*.rec
modprobe ipv6
modprobe xt_owner
modprobe ipt_REJECT
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
}
Seems to be running nice and stable with my Nokia E71 providing the internet connection using Joikuspot and secured with WEP. Tried switching back to my home network secured with WPA2 and it still works as well.
matt300 said:
OK, I finally got it right. Here's what I did:
Seems to be running nice and stable with my Nokia E71 providing the internet connection using Joikuspot and secured with WEP. Tried switching back to my home network secured with WPA2 and it still works as well.
Click to expand...
Click to collapse
Cool! Looks like this will have to be shoehorned into the system - so it'll have to be something stine accepts. Thanks!
this is what i added to my config file:
Code:
--bind /sdcard/wpa_supplicant /system/bin/wpa_supplicant
i had the wpa_supplicant file in the root of my sdcard
and yeah, the drivers also fixed WEP
husam666 said:
and yeah, the drivers also fixed WEP
Click to expand...
Click to collapse
Damn! Well I guess we're really going to have to find a way to implement those. Awesome... I wish I would've noticed this last time this thread was popular .
arrrghhh said:
Damn! Well I guess we're really going to have to find a way to implement those. Awesome... I wish I would've noticed this last time this thread was popular .
Click to expand...
Click to collapse
lol, i tried to tell you more than once, in different threads, i guess you were busy
husam666 said:
lol, i tried to tell you more than once, in different threads, i guess you were busy
Click to expand...
Click to collapse
Hum... I guess I vaguely remember the adhoc conversations, but I don't recall the WEP ones. At least I didn't realize that they went hand-in-hand...
We probably did talk about it. I've lost a lot of things in the ether... Oh well, I'll try not to forget it next time we're scrambling to do a release .
First things first:
By reading and following this guide,
you accept *ANY* and *ALL* responsibility
for the possible damage, loss of data and/or other
consequences to your device which may follow.
All the following procedures have been tested on a US Motorola Xoom Wifi only. They *might* (and probably do) work on other devices, including the 3G, Euro, etc., but are not guaranteed to do so.
Now that we're straight, let's get to the point.
Foreword:
Once I had this problem of accessing my brother's MAC filtered access point. I had my notebook MAC added to the access list, whilst my Xoom was left out. Of course, my brother was out and I didn't know the AP credentials. It was then, when the idea of a MAC change came to me.
During my brief "on the spot" research I discovered a file named 'bcm4329.cal' residing at '/system/etc/wifi/'. It has a line, notably 'macaddr=xx:xx:xx:xx:xx:xx'. Changing the contents, however, did not yield any changes to my MAC address. That time, I left the issue unsolved, but later, tinkering with my Huawei U8500, I discovered something that helped solve my Xoom MAC issue.
The solution was quite straightforward, but involved a kernel recompile. So, here I am, offering several kernel modules (drivers) - for the stock 3.2 kernel and for the Tiamat 2.0.0-2.2.0 kernels.
Prerequisites:
a stock 3.2, Tiamat 2.0.0 Katana, Tiamat 2.1.0 Tachi or Tiamat 2.2.0 Odachi running Motorola Xoom Wifi
ClockworkMod Recovery installed (author uses ClockworkMod 3.2.0.0 R4c by solarnz)
Procedure:
The procedure involves changing the appropriate wifi kernel module to a 'patched' one which allows MAC change through the 'bcm4329.cal' file. All this will be done in ClockworkMod Recovery.
1. Download one of the attached files (according to your running kernel version which you will find in Settings -> About tablet -> Kernel version)
2. Place the appropriate file on your SD card
3. Boot into Recovery by rebooting, waiting until the Motorola logo appears, count to 3, press the Volume down button, then the Volume up button
4. Select 'install zip from sdcard'
5. Select 'choose zip from sdcard'
6. Browse to your 'mac_change_mod_xxx.zip' (steps 1 and 2)
7. Select 'Yes - Install mac_change_mod_xxx.zip'
8. After its done it's job, reboot by returning to the main menu and choosing 'reboot system now'
Voila! You now have a Xoom with a custom MAC address. You can change it by editing the 'macaddr=...' line in the '/system/etc/wifi/bcm4329.cal' file. The author uses Root Explorer for this.
NOTE: The kernel module will probably be removed when installing a new kernel, so the procedure should be repeated.
Great work!!
LOL, I love it. I just changed my MAC address to look like an Apple Laptop. Even shows up that way on scanners that resolve the OUI to the manufacture. Now I'm stealthy!
Did I mention I luv it. Maybe tomorrow I will look like a Commodore 64!
is purpose just for personal preference? What would be the benefit of changing it?
One of the possible uses of MAC changing is described in the head of this thread. IMHO it's the most useful one. Other purposes may not be so legit, but the author takes no responsibility ;-)
tdaliviu said:
One of the possible uses of MAC changing is described in the head of this thread. IMHO it's the most useful one. Other purposes may not be so legit, but the author takes no responsibility ;-)
Click to expand...
Click to collapse
Lol I guess I was too dumb to understand what you did in the op, but I will still put this on my sd card just in case I find a use or need it
Purpose for MAC change
Maybe I did explain myself in a little too a technical language The basic idea is that if you have a wireless access point (i.e. a router) that accepts only one of your devices (i.e. your notebook), but does not accept your Xoom, you can try and change the Xoom's MAC address to mimic the notebook. The only thing to remember is that you can not use two devices with the same MAC on a network at once. If you follow that rule, you're golden.
P.S. Ah, and forgot to mention that this update will not work on the 3.2.2 for 4G Xooms.
tdaliviu,
Question for you. Since I applied this update I have noticed that my "WiFi Disconnect Policy" keeps reverting back to "When Screen Turns Off" no matter what I change it to.
I am not saying this patch is the cause, but what do you think are the possibilities? Again, I love the capability, and will live with the issue even it turns out to because of this patch, but I just wanted to check your thoughts on it, or see if you thought it might be something to do with the Tiamat ROM.
Thanks for looking at this.
UPDATE: Well I may have gfinally gotten the disconnect settings to stick. Instead of just changing it, letting it sit and coming back later to find out that it didn't, I changed it to the setting I wanted, then immediatley rebooted. Now it seems to be holding the setting. I will let go for a while and see what it does. Will provide an update either way. Thanks again.
For those wondering what this MOD might be good for, there are multiple things. Some ethical and some not so ethical. For instance, as "tdaliviu" mention, if you are trying to simply get around a MAC address problem, you might need to change it. If you were into hacking/cracking or just sniffing around wireless nets that weren’t yours and you didn't want to be discovered or tracked via your MAC. If you just want anonymity. I like it from this standpoint and that of security.
For instance, assume you are sitting in an Airport with your Xoom WiFi up and running, and someone is scanning the airwaves for likely targets to hack. If they seem your MAC address, they will know you are coming from a Motorola device, and might even be able to tell it is a Xoom. If there are any known security flaws, they automatically know which exploits to use against you to gain access. Just being a Xoom might make you a more attractive target. Who knows. But, if you can change your MAC address so that it appears as belonging to a different kind of system, say a "network device" like a wireless repeater, wireless AP, or some other boring target then not only would the attacker not know what exploits to run, but they would most likely just leave you alone without any further investigation or possible portscans.
And of course if you want real anonymity, you might consider changing the name your Xoom provides to DHCP servers when requesting an IP Address. Right now it uses "android_xxxxxxxxxx" with the x's being some number that is specific to your Xoom. I believe that could be used to track back your identity as well. I found several threads and ideas on how to do this. I used the one at http://forum.xda-developers.com/showthread.php?t=760314.
Anyway, thanks again for the MOD!
Quite a strange issue there, Krpto1973. At a loss to what might be the problem. I myself am running Moray, so will do some testing...
Well like I said, I may have gotten it taken care of. It's been holding steady since I set it and immedialty rebooted. It probably had nothing at all to do with your MOD. If anything changes I will let you know.
Guess I spoke too soon. After it sat idle for quite a couple hours, I came back and found it with "No Internet Connection". Once it fully woke up(just a second or so) it immedialty reconnected but when I checked the WiFi Disconnect Policy settings, it was back at "When Screen Turns Off".
Any thoughts?
Sorry, tested on my side. No such problem... Did you do a wipe when you switched to Tiamat's ROM? Maybe there are some leftovers from Stock? I am almost outruling a module problem since it's compiled from Tiamat's source using Tiamat's config.
Krpto1973 said:
For those wondering what this MOD might be good for, there are multiple things. Some ethical and some not so ethical. For instance, as "tdaliviu" mention, if you are trying to simply get around a MAC address problem, you might need to change it. If you were into hacking/cracking or just sniffing around wireless nets that weren’t yours and you didn't want to be discovered or tracked via your MAC. If you just want anonymity. I like it from this standpoint and that of security.
For instance, assume you are sitting in an Airport with your Xoom WiFi up and running, and someone is scanning the airwaves for likely targets to hack. If they seem your MAC address, they will know you are coming from a Motorola device, and might even be able to tell it is a Xoom. If there are any known security flaws, they automatically know which exploits to use against you to gain access. Just being a Xoom might make you a more attractive target. Who knows. But, if you can change your MAC address so that it appears as belonging to a different kind of system, say a "network device" like a wireless repeater, wireless AP, or some other boring target then not only would the attacker not know what exploits to run, but they would most likely just leave you alone without any further investigation or possible portscans.
And of course if you want real anonymity, you might consider changing the name your Xoom provides to DHCP servers when requesting an IP Address. Right now it uses "android_xxxxxxxxxx" with the x's being some number that is specific to your Xoom. I believe that could be used to track back your identity as well. I found several threads and ideas on how to do this. I used the one at http://forum.xda-developers.com/showthread.php?t=760314.
Anyway, thanks again for the MOD!
Click to expand...
Click to collapse
Fantastically stated there, sir. I wasn't aware of the DHCP request issue. You've successfully made me that much more paranoid.
Hmm this mod doesn't seem to work on 3.2.1 (breaks wifi functionality). Planning on updating by any chance?
Sorry, but I'm on Tiamat's Moray ROM right now, which is based on the 3.2 kernel. I certainly plan on an update when Tiamat releases a ROM based off 3.2.1 (or 3.2.2 for that matter).
If you attach a patch ill add it to the repo and give you bunches of credits
Oh, didn't quite expect such a turn of events One patch coming up...
mac_change_mod patch
Here's the patch. It's quite obvious, though took some time to figure it out. It's against the stock Makefile, but as I understood, there were no changes to the WiFi module from Team Tiamat.
Is it going to make it to a future release of Tiamat ROM/Kernel or will it live only as a patch file in the repo?
Code:
--- /home/liviu/Desktop/Xoom/Makefile 2011-08-03 09:27:45.000000000 +0300
+++ /home/liviu/Desktop/Xoom/stock/drivers/net/wireless/bcm4329/Makefile 2011-08-01 21:27:35.395212384 +0300
@@ -6,7 +6,7 @@
-Wall -Wstrict-prototypes -Werror -DOOB_INTR_ONLY -DCUSTOMER_HW2 \
-DDHD_USE_STATIC_BUF -DMMC_SDIO_ABORT -DDHD_DEBUG_TRAP -DSOFTAP \
-DEMBEDDED_PLATFORM -DARP_OFFLOAD_SUPPORT -DPKT_FILTER_SUPPORT \
- -DGET_CUSTOM_MAC_ENABLE -DSET_RANDOM_MAC_SOFTAP -DCSCAN -DHW_OOB \
+ -DSET_RANDOM_MAC_SOFTAP -DCSCAN -DHW_OOB \
-DKEEP_ALIVE -DPNO_SUPPORT \
-Idrivers/net/wireless/bcm4329 -Idrivers/net/wireless/bcm4329/include
Sweet. Cooking and testing. I don't see why this cant make a release. We gotta play with it a bit, but I like this mod. Goes nice with the BT5 concept too
So, I've been messing around with the source for a couple weeks and finally managed to make a wpa_supplicant based on the 0.8.x code which compiles, loads, and seems to connect to the internet.
Do I know why? Not really. I was working on it mostly just to get back into practice with code and I had some knowledge of the wpa supplicant from messing with the ad hoc and multicast. (Both of which mods are not applied to this supplicant as I wanted to keep it simple until it built correctly.)
Anyhow, the stupid thing finally loads and appears to work. And hopefully it'll be compatible with HashCode's new kernel when that has wifi in it.
If anyone is willing to download and see what does/does not work, I'd appreciate it.
This is totally a testing version, not general use. I honestly don't even know what the 0.8.x version of the wifi supplicant is supposed to do better than the 0.6.x version. But it's a higher version, so it must be better, no?
So, here's the download (Updated 4:30pm 9-Apr-12 CDT).
New version appears to fix encrypted networks, so all unknown on what works/doesn't.
jd
To install:
Download the file. I'm assuming you have ADB running and that you you're in the directory you saved the file to. No I'm not going to help with this part.
adb shell cp -a /system/bin/wpa_supplicant /system/bin/wpa_supplicant_06x
adb push wpa_supplicant /system/bin/wpa_supplicant_08x
adb shell chown root.shell /system/bin/wpa_supplicant_08x
adb shell chmod 755 /system/bin/wpa_supplicant_08x
Now shut off the wifi on the kindle
adb shell cp -a /system/bin/wpa_supplicant_08x /system/bin/wpa_supplicant
Now turn on the wifi.
To revert:
Shut off your wifi
adb shell cp -a /system/bin/wpa_supplicant_06x /system/bin/wpa_supplicant
Turn on wifi, or if it will not, then reboot.
jd
Flashable zip?
Or push with ADB?
:EDIT:
Disregard this post, I posted before he posted directions in post #2.
Extra post just in case
Can i haz packet injection?
Krunk_Kracker said:
Flashable zip?
Or push with ADB?
:EDIT:
Disregard this post, I posted before he posted directions in post #2.
Click to expand...
Click to collapse
LOL, I think I was actually writing post 2 as you posted. Since you got in before the second placeholder
There's no new functions in this that aren't in the stock WPA supplicant. I kinda mashed the ti driver against the 0.8.x supplicant code and then snipped off anything that didn't match. That's why I'm not sure what's not going to work.
From all my looking through the WPA supplicant, I haven't seen anyplace where it interacts at the packet level. I believe that's done driver-side. WPA supplicant seems to manage network names and settings only. I had high hopes of finding how the nic decides to roam originally but not even that seems to be accessible.
Sorry, but if you downloaded prior to this post, please download again. I found a problem with connecting to encrypted networks. (Had been using work guest network for testing previously.)
Fortunately it was a not difficult change and so I uploaded new version to fix that known issue.
Thanks again to anyone testing.
jd
jd,
I was only trying to encourage thought around the idea of getting monitor mode / injection working on this driver, and since I have no clue how to make it work myself, I figured I would get those working on the wifi to have a look how to recompile the drivers (hopefully) lol.
can i use root explorer for this?
@d33dvb No worries, I wasn't offended. Just trying to set the bar on what the new supplicant is capable of. Really, it seems to be basic management of the settings needed to connect to a SSID. So I'm really not sure what was added between 0.6 and 0.8 - it's not like the industry added a WPA3 encryption standard or anything. Googling wpa_supplicant 0.8 accomplishes little, I don't seem to find any change log after 0.7.3. Which is listed as current development version.
Anyhow, I'm hoping it's incremental improvements to network management. I already checked it wasn't a magic bullet fix to our multicast initialization bug so I'll have to reapply that fix when I get that far. At the moment I'm trying to use this as an opportunity to learn to use git so I won't have to keep reapplying these patches by hand each new version from CyanogenMod.
@paranoid_android85 I don't see any reason why you couldn't use root explorer to put the file in place if that's what you're comfortable with. I just wrote the instructions using ADB because that's what I'm comfortable with.
Short alternate instructions, somehow make a copy of your current /system/bin/wpa_supplicant. Shut off wifi, replace the wpa_supplicant file with the one in this thread. Match up the file owner and permissions to the original file. Re-enable wifi.
Since I haven't heard from anyone else, I'll go ahead and post my results.
Been running this on my KF for about 3 days and the only real bug I've found is that the network icon remains grey.
I know I've seen it posted before but do not remember where, but can anyone tell me what the thing is checking to switch from grey to blue?
jdommer said:
Since I haven't heard from anyone else, I'll go ahead and post my results.
Been running this on my KF for about 3 days and the only real bug I've found is that the network icon remains grey.
I know I've seen it posted before but do not remember where, but can anyone tell me what the thing is checking to switch from grey to blue?
Click to expand...
Click to collapse
When it's blue, it means it has contacted Googles servers
Sent from my Amazon Kindle Fire using Tapatalk 2
Krunk_Kracker said:
When it's blue, it means it has contacted Googles servers
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Any idea which servers? I receive gmail notifications, app update notifications, etc. I signed into Google talk. All with a still grey network icon.
I had been hoping to find an error in the logs that would indicate what's not happening, but the logs look clean.
So any additional info anyone has on the process would be helpful.
jdommer said:
Any idea which servers? I receive gmail notifications, app update notifications, etc. I signed into Google talk. All with a still grey network icon.
I had been hoping to find an error in the logs that would indicate what's not happening, but the logs look clean.
So any additional info anyone has on the process would be helpful.
Click to expand...
Click to collapse
IIRC, I believe it is for syncing.
Like Google Books. If you read it on your tablet, it uploads the last page read to the sync servers so when you access it from your phone, it will pick up where you left off.
#wpa_supplicant -v
reloc_library[1318]: 1057 cannot locate 'get_rfc3526_prime_1536'...
CANNOT LINK EXECUTABLE
I'm running cm7 on a passion device...
Wi-Fi works with all existing, configured AP's. It can’t find new ones during scans. I was in a motel all last week and couldn’t detect the local Wi-Fi. I could manually add it and it would work. I don’t know when it started but it was working not too long ago and I haven’t made any major changes to the phone recently. I loaded Wi-Fi scan app and it detects and connects to mine and my neighbor’s AP's so I suspect it’s not the hardware. Settings look good. I disabled AppOps and unfroze anything that might be related. I can't boot to safe mode. I think it's because of exposed. https://forum.xda-developers.com/xposed/tool-samsung-xposed-safe-mode-disabler-t3652781
SM910V, rooted, 5.1.1
Thanks, Geno
I thought I'd bump this. The only thing I did since the original post is to TWRP the phone back to an earlier date before I set it up to my preferences. It worked there but there's to many custom setups to start again from there. The WIFI manager app does what I need and was quick and easy.