Related
Can someone please tell me how -- or point me to an existing thread that will provide instructions for how -- to get AT&T's Tilt 2 to use wi-fi?
My situation is that I'm new to the Tilt 2, and I'd like to be able to access wi-fi -- rather than the slower than molasses 3G network -- when I'm within range.
My network is wired with a WAP, and it uses static IP addressing. I have no problem accessing the network with my (old) 8525 and my (newer) iPhone or my PDA or my laptop (all configured by me) to use my network to access the Internet and email.
My network is pretty tight (I think, or hope) in that it requires a specific IP address that matches a specific MAC address to gain access.
I've configured my router & WAP to accept a specific IP address for the Tilt 2, as well as the Tilt 2's MAC. I've checked & rechecked too many times to count to make sure I didn't make any typos. I've assigned the IP address on the Tilt 2 by going to Settings > Connections > Wi-Fi > Wireless Networks > Network Adapeter, and I set the Boradcom 8-2.11 DHD Newwork Adapter (is that the right one?) to use the specific IP addy I've assigned.
However, while the wi-fi icon indicates it's connected, I'm unable to use either browser on the Tilt 2 to access the Internet -- all I get are error messages.
I have honestly tried to read here for tips, and while I've read that I need to disable the AT&T proxy, the threads I found were a little (or a lot!) over my head.
I would sincerely appreciate any guidance.
TIA,
Saundra
Please, Need Help with Wi-Fi Settings
Surely I'm not the only one having problems getting the settings right so my AT&T Tilt 2 can connect to a home network, am I?
Honestly, I'm not a moron, but I can't figure it out, and the AT&T store was no help today, either. I recall that I had a similar problem with my 8525, so I went back & looked at my notes from 2008-- the problem was the MEdia Net proxy settings. On the 8525, it was a simple matter to uncheck the "This network uses a proxy server to connect to the Internet" box.
On the Tilt 2, however, I can't see where to give that a try because all I see is a message that says, "This connection is pre-configured. It cannot be modified."
Am I looking in the wrong place, or what? Or is that unlikely to be a problem on the Tilt 2?
I will greatly greatly appreciate any suggestions to try!
TIA
My first question is, are your WiFi router and the wifil on the TP2/Tilt the same? If the router is g and phone is N, they won't communicate.
That's a good question, and one I'd not thought of. My WAP supports B, G, & N & is operating in B/G/N mixed mode-- I don't know what the Tilt 2 is, but I'd think one of the three would cover it, yes?
Try going to this thread and downloading the files in post #13. Run the remove hidden proxy cab and see if that works, that will remove the hidden AT&T proxy server setting that often can't be disabled otherwise. The Tilt2 supports 802.11 b/g, so a router in mixed mode should have no trouble with that. You might try playing around with the network adapters again; I'd personally take another stab at the DHD adapter you tried earlier, since that is the one used on wlan connections. Also, you should probably make sure that the box which says: "My network card connects to:" is set to The Internet, and not work (this setting can be found on the Network Adapters tab of the Wi-Fi applet.
And while a bit off topic, you might want to consider adding additional security on your router (such as WPA2 encryption) if MAC filtering and static IP addresses are your only security; it's quite easy to grab both using free tools like aircrack-ng.
I want to thank you for your suggestions, but I'm not having any luck so far.
Scratch that -- things seem to be working . . . kind of. All I did was keep redoing the same things over & over, and suddenly, things are working.
I'm starting to think, though, that there's something wrong with this particular phone. Seriously -- I did nothing different tonight to get wi-fi working . . . encouraged by your comments, I just kept doing the same things over & over & over that I did last night.
Last night, running the removeHiddenProxy4CWS cab (it's in the Tools folder) resulted in not being able to connect to the Internet via 3G or wi-fi. Tonight, the results are different: I'm able to connect to the Internet via both after having run for the umteenth time the removeHiddenProxy4CWS file.
Further, while I've read many comments that the Internet is really slow on the Tilt 2, I'm thinking mine is abnormally slow & seems to hang up even via wi-fi. Now, I'll admit that perhaps my expectations are different coming back from an iPhone, but I charged up my old 8525, turned off the phone on the Tilt 2 to make sure I was connecting via wi-fi, and we are talking agonizingly slow on the Tilt 2 -- I was able to browse to six different Web pages on the 8525 in the time it took the Tilt 2 to partially bring up the first page (I used the same starting page on both). And, I say "partially" because it seemed to hang up at only partially displaying the Web site until I eventually hit the little circle in the bottom right of the screen. It does that on lots of pages -- is that the way things usually work on the Tilt 2?
Also, after my last soft reset just before things started working, I got a memory error message after I turned on wi-fi & when I hit the Internet button -- I should have written it down, but it said something about being out of memory on line 2. Any suggestions about that?
If the above are normal experiences for the Tilt 2, then I'll start learning about the tweaks to improve speed & such. If not, then I guess I need to try to exchange this phone. <sigh>
I also really appreciate your a bit off topic comment because I'm a security freak but not sure I understand much! My WAP uses WEP 64-bit encryption in addition to the MAC filtering & static IP addresses, and my wired router has a firewall -- does that sound sufficient. None of my neighbors can "see" my network, and it can't be seen from the nearest public road -- does that sound relatively secure?
Most of your Tilt2 problems could be fixed by flashing a custom ROM. If the phone is a business phone (as in it belongs to your company) or you otherwise can't void the warranty, a custom ROM sounds about right. It will improve the device's speed on all fronts, and will also have more available memory on bootup (mine had 25% less RAM in use on startup with a custom ROM). On my Tilt2, using a custom ROM with the latest Manila 2.5 build, things are still quite snappy, and pages load quickly on 3G and EDGE. If you'd like to know how to put a custom ROM on your device, this link will tell you everything you need to know. If you decide to put a custom ROM on your device, keep in mind you'll lose all the data on your device if you don't back it up.
As for the wireless security: WEP is extremely insecure. It has been proven insecure for many years, and has been replaced with the WPA (okay but obsolete now) and WPA2 (best current router security) protocols. Cracking WPA/WPA2 is much more difficult, as it requires a password cracking program and a wordlist to crack downloaded traffic obtained from the network, which can take days of cracking, sometimes ending in failure regardless. Unlike WPA/WPA2, WEP is much more vulnerable to many different attacks, from programs like aircrack-ng, which are free and readily available. If you don't believe me, check out this video of WEP being cracked on a test router, with the Backtrack 4 Beta security Linux distro, in as little as 2 minutes. MAC addresses and IP addresses can also be grabbed with many readily available tools, and the MAC can then be spoofed quite easily with free programs. And even a hidden SSID can be grabbed with a program like Kismet, which scans all wireless network traffic in an area (regardless of the network it's on) and can grab the hidden router's SSID during the handshaking process (when a client computer connects to the router). If you're absolutely positive that your network can't be detected from any public road (as in, there's no signal whatsoever), you're probably okay and can probably sleep safe at night. But, unless you have old equipment/software which doesn't support WPA2 or WPA, I'd recommend upgrading to the latest WPA2 security (if you're really concerned about security/privacy).
I really appreciate your help!
The Tilt 2 is a week old -- it was a birthday present. Am I correctly understanding that I could flash a custom ROM & then flash back the original if I don't want to void the warranty?
If so, playing with different ROMs would be something I'd be interested in doing . . . I just don't want to void the warranty in case there is something wrong with the phone. I had lunch with a friend with an AT&T stock Fuse (I think) Thursday, and we were playing with each other's phones. I can't say that I noticed her Internet was any faster (I wasn't really paying attention), but she was quite surprised that both IE & Opera failed to display a complete page until the screen was touched. On my end with her Fuse, Web pages opened completely with no fuss.
So, the whole "hang" thing makes me very nervous, particularly with the "out of memory" error message with nothing other than Contacts on the phone yet -- I've not even bothered to configure email (my lifeline). I was hoping the Web interface (I have IMAP) would work OK since that was one of my big beefs with the iPhone -- the onscreen keyboard just didn't work for me. But, with The Tilt 2 taking over 60 seconds to even get to my web-based Inbox, the Tilt 2 is gonna be a problem unless I can get that resolved. Hence my concern about not voiding the warranty.
You are correct: I do have older equipment that only supports WEP. My PDA & my old 8525. If I can get the Tilt 2 working well enough for me, I can rotate the older stuff out and go with stronger wireless security. I know my neighbors can't "see" my network, but I've never tested from the street behind my house since the closest neighbor behind can't see the network. However, due to the configuration of my neighborhood, I'd best check that street. <gulp>
Thanks again -- I really appreciate the help.
sslund said:
The Tilt 2 is a week old -- it was a birthday present. Am I correctly understanding that I could flash a custom ROM & then flash back the original if I don't want to void the warranty?
If so, playing with different ROMs would be something I'd be interested in doing . . . I just don't want to void the warranty in case there is something wrong with the phone. I had lunch with a friend with an AT&T stock Fuse (I think) Thursday, and we were playing with each other's phones. I can't say that I noticed her Internet was any faster (I wasn't really paying attention), but she was quite surprised that both IE & Opera failed to display a complete page until the screen was touched. On my end with her Fuse, Web pages opened completely with no fuss.
So, the whole "hang" thing makes me very nervous, particularly with the "out of memory" error message with nothing other than Contacts on the phone yet -- I've not even bothered to configure email (my lifeline). I was hoping the Web interface (I have IMAP) would work OK since that was one of my big beefs with the iPhone -- the onscreen keyboard just didn't work for me. But, with The Tilt 2 taking over 60 seconds to even get to my web-based Inbox, the Tilt 2 is gonna be a problem unless I can get that resolved. Hence my concern about not voiding the warranty.
-snip-
Thanks again -- I really appreciate the help.
Click to expand...
Click to collapse
Sure, I'm glad I can help. Well, you're partially correct about the whole ROM thing. The deal is, your warranty is only voided if they know you put a custom ROM on it. If they don't find out (ie, you restore the ROM and SPL to their stock counterparts) you're good to go. However, you do technically void the warranty because you put a third party ROM. However, you can take it from me when I say it's almost 100% safe when you follow instructions and it's completely worth it. You get more features and stability with less bloat while using an unofficial ROM. Keep in mind that if the USB port goes bad, you can't restore the device to stock configuration, and you'll have to pay full price for repairs (unless you dispute the warranty violation in court, and try to prove that there's no way an unauthorized ROM broke the USB port). Otherwise, a custom/cooked ROM is completely worth it, and will greatly improve your whole experience over the stock ROM.
After trying out several ROMs I have noticed that my wi-fi randomly disconnects, but only for (Non-HTC/Sense) ROMs.
I'm running OpenDesire at the moment, which I really like, but the arbitrary disconnetion of wi-fi is driving me crazy.
As far as I can tell, it has done this with the other Non-Sense ROMs I have tried as well, and I have no idea why.
Wi-fi does switch on, but (part of) the problem _seems_ to be that the phone has trouble actually getting an IP; other than that, and why it does this, I have no idea.
The settings (in *#*#4636#*#* test mode) are basically the same as they are for, say, the official HTC Sense OTA or Pinky, for which wi-fi seems to work perfectly.
Although, to be honest, I'm not entirely sure what I'm looking at/for...
Anyone have any ideas?
Any help would be much appreciated
It's not having an issue with getting an IP, it's having an issue with authentication.
The first thing I noticed with these roms is they do not re-prompt to enter a password again if you have mis-typed it at all. This leads to wpa_supplicant client to effectively force a connection and get a refusal in quick succession. The wpa_supplicant client on the phone then disables the connection until you step in and either choose to reconnect or edit the password manually.
The issue we are having is related to this;
After being connected to WiFi for a fair period of time, it re-authenticates with the base station/router as it's supposed to do.
From memory, the re-auth happens every 60 minutes and most decent routers are able to change this.
At this point, the client (phone) tries to re-auth and fails (for whatever reason). Instead of prompting for a password (as it should do). It tries 3 times in total and stops.
After the last failed attempt, it disables the connection that it failed to connect to and jumps back to mobile data (if available).
So. Yes, there is a major issue with the wpa_supplicant in non-sense roms. Could we get the devs to investigate this, as it's really getting to be a major pain in the arse!
I see... Thanks for the clarification. Nicely explained.
So, short of jumping ship to Sense, there's really not much I can do then, other than wait for someone more skilled than me to come up with a solution?
No workaround, third party app, router setting or anything?
Unknown at this moment in time.
I'm investigating this in my own limited knowledge of Android and Linux systems, so far I've not come up with anything solid.
As far as settings you can change on your router, it all depends on your router and it's firmware.
I've got three different routers here:
A) Trendnet TEW-435BRM v4.00.07 : No way to change Key Renewal length
B) Linksys WRT160Nv2 v2.0.03 : Able to change Key Renewal length
C) MZK-MF150 v1.00.16 : Able to change Key Renewal length
Check your router, try increasing the length and have a play around. It's not a fix, the issue is either in the AOSP kernels or the wpa_supplicant module.
My NetGear WNR2000 does not seem to have any (easy) way of configuring Key Renewal Length, but I'll have a look around. Else, I guess I'll just have to bite the bullet and go with Sense for a while...
At least now I know it's not just me. That's always comforting.
Thanks for the help acolwill!
No problems at all.
I have been trying to locate an app that will automatically restart the WiFi if a disconnection takes place, however, I've yet to find one :|
Anyone out there know of one?
eham, there's an app on the market called "WiFi Auto ReEnabler"
Give it a try, as it may well be the answer you've been looking for!
Sounds very promising indeed. Will get right on that.
Tried an app called Wifi Fixer, but that was a bust. Actually somehow managed to make things worse (for me, anyway).
Thanks for the tip. I'll be back with an update...
Ok, so "WiFiReEnabler" does actually do just that; re-associate with the network everytime the screen wakes. Unfortunately, what it doesn't do is stay resident.
It will let itself get killed by the system very easily, so I still have had a few times where I had to manually deactivate and activate wifi because WiFiReEnabler didn't have my back.
If the developer could make this a helper app/system service, this seems like it could be a decent workaround though.
I did however find an app called "Fix My WiFi" (£0.99 in Market) that seems to take care of the problem nicely, and quietly, so far (about 16 hours and counting, fingers crossed).
It also has some options to set different levels of aggressiveness, and notifications, which I like.
I also found a free app called "Wifi Reassociate" that seems to address the same issue. Haven't gotten around to trying it yet, as Fix My Wifi still seems to be doing its job.
Still, a tip for anyone with the same problem.
With that (hopefully) outta the way, I'm off to celebrate the anniversary of my birth.
Be well, friends.
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
TLDR: Unlocked LG G2 was on Sprint, now on VIVA in Kuwait, Max WiFi users when running hotspot is 1 - I want to increase it to more.
Long version:
Hello! I am a military service member deployed to Kuwait. I have a Sprint LG G2 which is rooted and running the latest UltraPop ROM. Before I left the US, my phone was activated on the Sprint network and when I would use my WiFi hotspot, I had the ability to connect up to 10 users or something. When I got to Kuwait, I had to have my phone SIM unlocked for International use to make it work with the SIM cards provided by the carrier here (it's called VIVA). My phone was not on the Sprint network when I needed to unlock so when I did the UICC unlock it did an OTA over WiFi and then I was able to use my phone on their carrier. This is all well and good.
The problem is, I want to connect my laptop, my tablet and a few other items to my hot spot - thus the appeal of the hot spot, right? LOL. Anyway, several advanced options like the radio channel, frequency, etc. have now disappeared and in addition, the most important one - the amount of users able to connect to the hotspot, went from allowing 10 to 1. I am not sure why, except maybe something to do with the OTA update when I did the UICC unlock.
I did some reading and found this article: http://forum.xda-developers.com/showthread.php?t=2718682
Quickly I tried it and restarted my phone. No change. Then I noticed there was another hack for phones that had been activated on the Sprint network, which as I explained above, believe applies to me. This article has a more complicated procedure: http://forum.xda-developers.com/showthread.php?t=2675280
I am afraid to try this method and screw things up. I suppose I could boot in TWRP and do a NANDROID back up before I try it but I am wondering if anyone thinks it will hose the only working Internet I have right now in Kuwait.
Any help is appreciated. Also, if anyone knows how to get the WiFi hotspot to allow devices to connect while running a VPN at the same time please enlighten me!
Thanks!!!
Sincerely, Lost & Confused...
OK, so I am going to resurrect my own thread here. I spent some time on and off dealing with the 1 client max for the hot spot in my Sprint LG G2. Lots of frustration. Anyway, digging deeper based on a tip another friend of mine gave, I discovered something that I thought would have helped, but no cigar.
Anyway, a variable called max_num_sta in the file /data/misc/wifi/wpa_supplicant/hostapd.conf allows the access point to have only one client. The hostapd application on Android performs almost identical to an average Linux distro, so I figured by modifying this variable I would be able to allow more than 1 client to connect to my hotspot. However, even when changing the file manually, as soon as the hot spot is enabled thru the stock interface, only 1 client is able to connect and looking at the file again shows the value of the variable has been reset.
Next step on the list, was to run the hostapd manually from an Android terminal (something like hostapd -e/data/misc/wifi/entropy.bin -BK /data/misc/wifi/hostapd.conf). The command works at the hot spot functions, but again somehow resets to 1 freaking client again!
I would really like to be able to use my G2 to connect more than one device at a time to my hot spot while I am stuck in Kuwait. It is my only source of Internet. Anyway. Is there a way to disable the stock Wi-Fi Hot Spot interface using Titanium Back-up? Remove the APK? Modify the system? Something? I'd really like to figure this out. Any info or suggestion appreciated...
Disclosure: I own nothing hereI am not an expert romolgist. Just a guy that hates when buttons don't do anything.
Without a working US csc folder in the Rom it's all pretty much temporary.
Since support in current threads is non existent I'll do my best to show what I've done to get data and texting. It's still a bandaid for a weak design but it's enough to get things working for a couple hours.
Results will vary and this will be updated multiple times in the next week. I'm forgetting some details.
List of apps used.
SetEdit pro - helps remove bloated junk that's greyed out.
Radio Switcher - needs to be turned to cdma-auto and lte-cdma every time signal is lost
Region changer - gets the phone labeled as US but it's incomplete. More on that later
Root essentials - easiest way to get can and build prop in one place
Partitions backup - backup-/restore efs and radio
Aurora settings - adds necessary settings that rom builders left out
APNs backup - obvious reasons
Phone info+ - get into prl enable all LTE frequencies/ disable gsm band
They're pretty much necessary for every n7 port listed today.
Step one:
Backup efs/radio/apn from WORKING rom like MOAR or stock
Download with ADM. Speed was not a priority with these ports including downloads
Pick a Rom that you like the pictures of because words don't mean anything at this point. A 928p Rom doesn't mean it will work on a 928p so don't be afraid to experiment. Had better results from 930 and R4 Roms and kernels.
Hopefully you'll see the activation screen. If not you're gonna have a bad time.
Speaking of kernels use sky but uncheck the prop and other junk box on last setup page. These ports need extra junk just to stay running. I'll post a link to another kernel I like as well as some newer clones.
Step 2
Delete everything. Seriously. Data/system/whatever
Pull your flash drive after install or it tries to write there as well.
These things seem to write anywhere they want and old data has effected startup or install times.
Flash what you liked and hope for the best.
Pick whatever country is your favorite. Means nothing to US Sprint customers
Install as a 920.
Don't take the 928 option.
Install the note5 camera
Install whatever audio driver they added. Stock hasn't worked for me
If you don't see a restart at the Samsung splash screen or blue light stays on after restart it's a bad file. You want to see a jogging pace with the dimming of the logo. Anything less than that and it's going to crash sooner than later. For US Sprint customers it's usually at the connection check.
Step 3
Be patient. These are as temperamental as the builders and require constant maintenance to avoid memory leaks and signal loss. When you read claims about battery life it's because it's missing basic functions necessary to run reliably on us Sprint towers.
Step 4
Hopefully it's showing signal. If not the only workaround is injecting a US csc to the Rom itself as well as 90% of someone else's build props and csc files. I'll show what were used once the owner gives permission.
Restore apn/efs/radio
Root explorer systen/csc/sales_code mount as rw and edit to say XAS
Change region to US
Restart
From there I'll use radio switcher and connect to cdma-auto and wait for signal. Once signal is established and you see your phone number switch it to cdma/LTE auto and restart. Verify the settings stuck. If they didn't try playing with different connections. This sometimes works. Also needed for signal loss and probably every restart.
Once data is working try editing csc until it matches a good Rom.
*added xposed that works with lam7.3
https://mega.nz/#!tdF0FKjR Aurora apk
Reserved for download links
Here's what I like. Results will vary
https://mega.nz/#!oUVxSSKb Lamlazy 7.3
https://mega.nz/#!0EFCGAob duelbootgraceux kernel
https://mega.nz/#!tBNBXCgY hidden menu
https://mega.nz/#!wM0V2LyT some beta crap that gets good LTE but needs dialers or it it comes unglued
https://mega.nz/#F!oA9Q0QyS More links including 925 and 920 combo files
Reserved for cat pictures
Got synapse to load this morning. Day and night difference after cleanup and adjustments to little cores. Loaded a MOAR profile for shiggles and both roms freeze. Knew results would probably go that way but it's fun to try and break these things instead of the usual self destruct.
Testing with this phone might be done. Charging port is pretty lose and I don't want it fixed. If anyone can add to this please do I'll keep the links alive.