Today I turned on my phone's wireless and I noticed it turned off quickly. I thought it was odd so I turned it on again...same thing occurred. The third time I went into settings > wireless and network > wi-fi settings and enabled the wi-fi card from there. It shows it's scanning and then displays "unable to scan networks" along with turning off the wireless card. What the crap?!
I've rebooted the phone a couple of times - still nothing. I'm going to try removing the battery for 10-15 mins and try it again but I don't imagine that's going to fix anything. A quick google search has shown only a couple other people with a captivate are having this problem as well. I have to imagine there are more out there? Anyone have a clue. I'm really trying to avoid flashing back to stock.
Thanks in advance.
Did you go through the process of enabling Non-Market apps directly on the phone (editing settings.db) ?
If so, did you follow the chmod/chown commands?
max_warheads said:
Did you go through the process of enabling Non-Market apps directly on the phone (editing settings.db) ?
If so, did you follow the chmod/chown commands?
Click to expand...
Click to collapse
How would that affect WiFi??
If the system does not have proper write access to the file, and then a program says to the settings provider "turn on wifi", but the provider is not able to save that setting, it will later turn around and say "yeah... thats not supposed to be on." Which happens to coincide with an approximately 10 second window.
max_warheads said:
Did you go through the process of enabling Non-Market apps directly on the phone (editing settings.db) ?
If so, did you follow the chmod/chown commands?
Click to expand...
Click to collapse
Thanks for your help. However I did not edit settings.db. I've only rooted the phone. Haven't done any other manual edits to the system.
The only relevant thing I can think of that might be useful information is yesterday morning I installed wi-fi analyzer from the market on my phone. I'm 99% sure that my wi-fi was working after I installed it but then later in the day the problem started. Last night I un-installed wi-fi analyzer just to be safe.
Could this program have made some edits to Android that is causing the problem?
I found a similar problem in a google code forum from 2008. Individuals were using a G1 and had the same problem. They mentioned that it appears as if the wi-fi driver would load but then wouldn't be able to recognize the wireless card.
Hopefully some useful information to someone. Thanks again guys for taking a look.
sola fide said:
I found a similar problem in a google code forum from 2008. Individuals were using a G1 and had the same problem. They mentioned that it appears as if the wi-fi driver would load but then wouldn't be able to recognize the wireless card.
Hopefully some useful information to someone. Thanks again guys for taking a look.
Click to expand...
Click to collapse
Ran into the same issue, my issue was solved by fixing permissions as mentioned in the previous reply. How did you root your phone?
div3rg3nt said:
Ran into the same issue, my issue was solved by fixing permissions as mentioned in the previous reply. How did you root your phone?
Click to expand...
Click to collapse
Rooted the phone by using the update.zip file from the "Pimp My Captivate" thread.
How could I edit the permissions for the file to see if this remedy's the problem? I already have Terminal Emulator on my phone but I'm brand new to linux commands.
open Terminal Emulator and follow along
Code:
$ su
# cd /dbdata/databases/com.android.providers.settings/
# ls -l settings.db
You should see :
Code:
-rw-rw---- system system <snip> settings.db
max_warheads said:
open Terminal Emulator and follow along
Code:
$ su
# cd /dbdata/databases/com.android.providers.settings/
# ls -l settings.db
You should see :
Code:
-rw-rw---- system system <snip> settings.db
Click to expand...
Click to collapse
Ran the code you gave and it returned what you wrote above:
Code:
-rw-rw---- system system <snip> settings.db
I take it this means that settings.db is already set as writeable which means it's not my problem?
Yuppers... :/
Thanks for trying max.
What about the wireless config file? If this was messed up could it cause it the wireless card to act up like this? Could I simply delete this file and android would recreate it when I turned on the wireless card? Along with - where is it on the captivate?
Just a thought, my knowledge in this field is pretty low.
bumping this thread
Update: A factory reset fixed the problem. However when I restored from a Titanium backup the wireless immediately stopped working. Obviously there is something in the software/files that are corrupt causing this problem.
Anyone have any ideas of which file to attack?
BUMP
I am having this problem too. It is very annoying and I don't want to reflash the rom again. Has anyone else had this problem (and fixed it)?
americanbordercollie said:
BUMP
I am having this problem too. It is very annoying and I don't want to reflash the rom again. Has anyone else had this problem (and fixed it)?
Click to expand...
Click to collapse
ABC: Is there anything you installed before the problem happened that you think might be causing it? I'm guessing since you said "again" that this is the 2nd time or more you'll be flashing your phone if we don't find a fix.
I had to flash it with Odin because my phone bricked two weeks ago trying to enable non-market apps. I don't want to go through that process again.
I didn't install anything except the WiFinder app. It stopped working after a coworker asked me to turn on my wifi to test an app he got for his phone that turns it into a WiFi hotspot through its 3G data connection. The test was unsuccessful anyway, but that is irrelevant.
I had the problem of wifi not being able to scan for devices after 10 sec. This problem was only on my wifi at work.
I set the IP address, IP mack, gateway address and DNS servers statically and saved the config. This got me connected to the wifi at work. You could try this.
Just changed permissions on settings.db and now wifi seems to be working flawlessly without a need for static config.
americanbordercollie said:
I had to flash it with Odin because my phone bricked two weeks ago trying to enable non-market apps. I don't want to go through that process again.
I didn't install anything except the WiFinder app. It stopped working after a coworker asked me to turn on my wifi to test an app he got for his phone that turns it into a WiFi hotspot through its 3G data connection. The test was unsuccessful anyway, but that is irrelevant.
Click to expand...
Click to collapse
I'm curious if WiFinder altered a file that is causing the problem. Mine came just 30 minutes after installing Wifi Analyzer. Just hunch since both programs use the wireless card.
santblue said:
I had the problem of wifi not being able to scan for devices after 10 sec. This problem was only on my wifi at work.
I set the IP address, IP mack, gateway address and DNS servers statically and saved the config. This got me connected to the wifi at work. You could try this.
Just changed permissions on settings.db and now wifi seems to be working flawlessly without a need for static config.
Click to expand...
Click to collapse
It sounds like the same problem I had but I wasn't able to connect anywhere - At either one of my offices or at home. I tried to add in manual settings in the Android menu but it still didn't help.
I'll try messing with the settings.db file if this happens again and report back. I'm crossing my fingers that I never have this problem again but you never know. Hopefully we can get a couple of known working solutions posted on here since it sounds like there are plenty of people out there having this problem.
I have been trying to spoof my mac address on my phone. I am a pen tester so please don't lecture me on the ethics behind this because I know. It is very simple to do on linux, so I thought it would be possible on Android.
I installed busybox and terminal emulator and ran the su command. So far, i can run 'busybox ip link set eth0 address XX:XX:XX:XX:XX:XX' 'busybox ip link set eth0 broadcast XX:XX:XX:XX:XX:XX'. Everytime I do this, it changes the mac address, but breaks the wifi functionality. The only way to fix the wifi was to disable, then re-enable it, but that resets the wifi. I was wondering if we could colaborate on this and maybe get somewhere.
I have also seen this somewhere, but am not sure if it will work.
ip link set address NEWMAC dev eth0
Sorry for digging out this old thread, but I was trying the same and failing in the same way as you were.
The only difference is, I do not change the broadcast address, because imo this should remain on "all FF" (please tell me, why the broadcast should be set to the new MAC).
If I change it and fire up 'ip link show eth0', it shows the changed MAC.
The settings menu still shows the real MAC.
As in your case, the WiFi-connection (naturally) terminates (the router (access point) cannot know about the change). If I try to reconnect to the router, I get the error that my password is wrong. When checking the router's log, I see an entry about a failed connection attempt from the changed MAC address.
The only explanation I have is that the WPA2 encryption somehow incorporates the actual "real" MAC address so the encryption fails and as a consequence the connection is refused.
So-far, I haven't tried it without encryption.
Another question would be, what exactly is executed, when you activate WIFI on the phone? Which script?
I know that the network device (in my case "eth0") is created at this point.
If WIFI is down, no such device exists.
I would suspect some script that creates the interface, activates it and starts a demon that handles the connection stuff.
Maybe it would help to inject the spoof code after the interface was created, but before it is activated? So-far, I couldn't identify the correct script/command. Does anyone know?
Knowing the command that creates the network interfaces would also help when searching for the script.
Hi Folks
[UPDATE]This is not the only way of getting Dongle's working on the N7, If widgets are your thing and you don't feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android and members have reported success using it. See this thread [Nexus7 UMTS-Stick extern working] in the general section for the initial find.
[UPDATE]This mod has seen success on ZTE Dongles ( Thanks To NexusPhreak ) See the supported devices list in the second post for a list of the latest tested devices
[UPDATE]It turns out this mod is good for CDMA Dongles as well as GSM - It needs a slight tweak. See this post [ Post #76 ] for details ( Thanks to mailbinoy )[UPDATE]
IMPORTANT: THIS IS A WIP AND NOT READY FOR PRIME TIME - IF YOU HAVE NEVER USED FASTBOOT, ADB, DON'T UNDERSTAND THE FIRST THING ABOUT NETWORKING OR HAVE NEVER SEEN A BASH PROMPT THEN THIS IS PROBABLY NOT FOR YOU
TROUBLESHOOTING: IF YOU ARE HAVING PROBLEMS PLEASE READ THE TROUBLESHOOTING SECTION IN THE SECOND POST - THE MORE INFORMATION YOU CAN PROVIDE THE BETTER AS THIS HELPS GET TO THE ROOT OF THE PROBLEM - THIS INCLUDES MODEL NUMBER OF THE DONGLE, LOGCAT LOGS AND DMESG OUTPUT.
DOUBLY IMPORTANT: PLEASE READ THE FIRST AND SECOND POST TO GET AN UNDERSTANDING OF WHAT WORK HAS BEEN DONE AND HOW THIS FUNCTIONALITY IS IMPLEMENTED
Okay I've seen a lot a thread asking whether using 3G Dongles ( Huawei in particular ) is possible with the nexus 7........ The Answer........ "Of course it is!!!11!! it's Android/Linux Kernel, If we can dream it we can code it! "
I've been working on getting the full connectivity going but so far I've managed to bring up a raw ppp connection which is good for all things google (play, web browsing, gmail ) as the google apps still aren't playing fair with the connectivity manager and they just scoot around that and use web sockets instead!
Normally to enable this functionality we need to compile the usb_wwan.ko and option.ko as kernel module, much to my surprise google/asus have built these in already so we can just usb_modeswitch into modem mode and init our ppp connection. Winner! :good:
STAGE 1 PPP Connections
My test modems where Huawei E173s-1 and E1752Cu and the build I used is my own AOSP 4.1.1 with a kernel version of 3.1.10-g52027f9
Steps to 3G Fun
1. Do a full back up
2. Flash this boot.img through fastboot
3. Download This file ( nexus7-3g.7z ) See post 2 for link
4. unzip the file and adb push to correct directories
5. Turn off Wifi
6. Plug in Dongle
7. Restart
8. In Terminal Emulator of similar run
Code:
su
/system/etc/init_pppd_gprs
If all has worked then your dongle should now be connected!
Detailed Explanation ( Or Why The Hell Am I Doing This? ):
Why The New Boot.img?
The boot image adds service called hotplugd and service called switch_ms_to_3g which handles the usb_modeswitching
The code for hotplugd is here ( github ). if you don't want to flash the new boot image you can always run usb_modeswitch manually pointing to the config file and specifying your vendor id and product id if you do not wish to run hotplugd
Why turn Wifi Off?
We turn wifi off first because otherwise the ppp connection doesn't get assigned properly if wifi is turned off after the event.
Why The Restart?
On My USB OTG cable at least it doesn't seem to get power if I plug it in after power up YMMV.
STAGE 2 - FULL CONNECTIVITY
Obviously the Stage 1 is good. But It's not Great and we can do better. Using a similiar Wifi Only Device as my frame of reference, ( the Motorola Xoom Wifi ) to bring full connectivity ( i.e Mobile Networks Option in the settings and The Signal Icon in the Menu Bar) to the device required modification of the framework-res to allow mobile networks, you can either modify the existing one on the device or if building from source you can modify the config.xml found in the device overlay in the aosp ( device/asus/grouper/overlay/frameworks/base/core/res/res/values/config.xml )
something along the lines of
Code:
<resources>
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,0,-1,true"</item>
<item>"mobile,0,0,1,-1,true"</item>
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,5,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<item>"ethernet,9,9,9,-1,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,-1,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"wifi_p2p,13,1,0,-1,true"</item>
</string-array>
<string-array translatable="false" name="radioAttributes">
<item>"9,1"</item>
<item>"1,1"</item>
<item>"0,1"</item>
<item>"7,1"</item>
</string-array>
</resources>
NOTE: I've not really took the time to fully understand these settings and I've basically Kang'd them from another overlay.
As such they maybe suboptimal. Any further tweaks Improvements or general insight is more than welcome.
This seems to build okay and gives me the above mentioned features,I also set the build.prop default network to
GSM:
Code:
ro.telephony.default_network=3
CDMA:
Code:
ro.telephony.default_network=4
NOTE: Full CDMA Support require more than just this. There are a number of other build properties which affected and I'm currently working out which are the best ones to use.
and added the following files
Code:
/system/bin/rild
/system/lib/libhuaweigeneric-ril.so
/system/etc/permissions/android.hardware.telephony.gsm.xml
/system/etc/permissions/android.hardware.telephony.cdma.xml
I would expect this work and give me full connectivity on the device however it seems to "bork" when trying to load the vendor specific ril , I suspect I may be missing a permission or something similar
PROBLEMS - TROUBLE SHOOTING
If you're having problems, first I would Install busybox which will give you lsusb, this will tell you if your modem is actually recognized.
You can also run netcfg which will tell you if the network interface name ppp1 has been created and is up, then grab dmesg and a logcat, so something like this on adb will give you a good idea of what's going on.
Code:
adb shell netcfg
adb shell lsusb
adb shell dmesg
adb logcat -b main -b system -b events -b radio
* Note if you are running logcat through terminal emulator please run it with superuser permissions
Code:
su -c "logcat -b main -b system -b events -b radio"
Happy Hacking People and Good Luck!
References:
DerArtem Original Work with Huawei Dongles on the Toshiba Folio 100
usb_modeswitch official website
3g-modem.wetpaint.com A great source of information regarding 3G Dongles
Android Device Porting Walkthrough - Android Builder Summit 2012 ( An excellent presentation on device porting )
Hi Folks.
[DISCLAIMER]YOU KNOW THE DRILL.... RESPONSIBILITY FOR DAMAGE, INCURRED COST THROUGH EXCESSIVE DATA USAGE ETC IS NOTHING TO DO WITH ME.[DISCLAIMER]
VITAL : THIS IS STILL A WIP - THERE IS A GOOD CHANCE THAT I'VE DONE SOMETHING WRONG, COPIED A FILE TO THE WRONG DIRECTORY OR SIMPLY MISSED SOMETHING OUT, PLEASE THINK ABOUT WHAT YOU ARE DOING BEFORE BLINDLY FOLLOWING THE INSTRUCTIONS OF SOME MANIAC ON THE INTERNET :laugh:
Right on with the fun!
I haven't had much time to look at this as it wasn't top of my list, However the good news is I now have full 3g connectivity on the nexus 7 using Huawei 3G Dongles. :victory:
The issue turned out to be incorrect permissions on the /dev/ttyUSB* devices nodes which are created by the Huawei Modems, this was fixed by adding the following line to uevent.grouper.rc in the boot.img,
Code:
/dev/ttyUSB* 0660 root radio
simple when you know how!
I've attached a zip file which contains the files needed to enable this. It is a manual installation at present although I plan to make this flashable through recovery at some point but would really like to leave any other modification you may have made in tact. I.e TabletUI etc
The Changes where made to the Stock Factory Image JRO03D with Kernel 3.1.10-g52027f9
I've included the stock Mms app and enabled both voice and sms capability in the framework-res.apk. I left out the Phone.apk as you can only make silent calls because of the lack of Audio Rooting ( A possible future project perhaps ). I also changed the Data Usage to monitor the connection used by the dongle which allows you to impose data limits on your bandwidth ( see screenshots ).
Upon applying this update you should have mobile networks available in "settings/more networks" and the signal strength icon should appear in your status bar
Download the file here ( hotfile )
Please follow the readme in the archive for installation instructions and take note of the notes!
In addition to the steps in the readme, It's worth making sure that everything that needs to be executable still is.
Code:
adb shell chmod 6755 /system/bin/pppd
adb shell chmod 755 /system/xbin/chat
adb shell chmod 755 /system/bin/usb_modeswitch
adb shell chmod 755 /system/bin/rild
adb shell chmod 755 /system/bin/hotplugd
adb shell chmod 755 /system/etc/ppp/init_pppd_gprs
adb shell chmod 755 /system/etc/ppp/ip-up-gprs
adb shell chmod 755 /system/etc/ppp/ip-down-gprs
SUPPORTED DEVICES
The theoretical list of supported devices come from those Huawei devices which are supported by the GSM Modem driver in 3.1.10 kernel.
my testing was on a E1752Cu, E173s-1 and the E1750
Confirmed Devices
Huawei
E1750
E1752Cu
E173s-1
E173-u2 ( Thanks to m3ritum ) Video
E367 ( Thanks to mynamesriz )
E3131s-2 GSM/HSPA+ ( Thanks to radkor )
EC156 CDMA with a couple of tweaks see this post [ Post #76 ] ( Thanks to mailbinoy )
E160E (Thanks to Dragon0501 )
ZTE
MF190J**
MF190**
MF636**
MF626**
** Thanks To NexusPhreak
TROUBLESHOOTING
There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprop
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
* Note if you are running logcat through terminal emulator please run it with superuser permissions
Code:
su -c "logcat -b main -b system -b events -b radio"
RESERVED
All sounds very cool, nice one.
looks very promising, do you know if there are any CDMA dongles for 4G phones on Verizon?
Is there a better explanation of how this works ? Would we have to have a data plan to use this or is it just picking up 3g?
Sent from my Nexus 7 using Tapatalk 2
azoller1 said:
looks very promising, do you know if there are any CDMA dongles for 4G phones on Verizon?
Click to expand...
Click to collapse
Not a clue, I'm not in the US and don't really have an understanding of the US celluar network. I'm unsure whether this implementation of the ril library ( the part that talks to android ) can handle CDMA as I've only got GSM dongles to test with.
emarietta said:
Is there a better explanation of how this works ? Would we have to have a data plan to use this or is it just picking up 3g?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hi
This is using Huawei 3G Dongles ( sometime called mobile broadband ) which were quite popular in the UK and Europe, Something along the lines of this ( linked picked at random ) they normally come with their own sim card, and by extension a data plan, generally on a pay-and-go basis.They are effectively a fast "dialup modem" ( by UK Standards anyway )
The modems are generally carrier branded / locked and are restricted to data and sms only. However the carrier restriction can be removed and voice support can be added via firmware updates if the hardware allows.
My carrier ( 3-UK ), picked this up as tethering when I used my Phone SimCard for testing and as such It is not a method around tethering restrictions your operator may have in place.
I hope the helps shed some light on the topic.
cool idea, ill just use my 4g tether though
Great work mate!!! Just one question:
I will be getting my Nexus 7 in a couple of days and I already own a HP TouchPad running CM9. I want to know can I tether my dongle's internet on my nexus 7 with the HP Touchpad via Wifi or bluetooth?
lovleshgarg said:
Great work mate!!! Just one question:
I will be getting my Nexus 7 in a couple of days and I already own a HP TouchPad running CM9. I want to know can I tether my dongle's internet on my nexus 7 with the HP Touchpad via Wifi or bluetooth?
Click to expand...
Click to collapse
That's a dam fine question . The word FrankenConnection instantly sprung to mind :laugh: I haven't got the tablet in front of me at the moment and off the top of my head I'd say probably not by default.
However, It wouldn't be too difficult to enable on a technical level, it's all about your ip routing tables, they are probably numerous apps on play to do it, although personally i've a little no success with then. Cyanogenmod has it built into to the rom, at least on CM9 on my Sensation and that works a treat. I will have a proper look as It could be crazy enough to work!. :good:
had a go but no luck
using a Huawei E353 dongle with a variation of a 3 sim. has its own APN and a static IP, left over from a work project.
flashed the new boot, copied the new system and made the permissions mod. the various apps show up
under about tablet it shows baseband as unknown and if i try to add an APN it goes through the motions but doesnt add it to the list.
I've attached the logs, i'm no developer but i can follow instructions if any one can suggest any thing. there is every possibility i've messed up in the install so feel free to suggest dumb stuff that i should have known in the first place.
It could just be that the dongle isn't supported in which case we can chalk up a zte MF112 as been a duffer as well (had one kicking about so gave it a go)
laz2336 said:
using a Huawei E353 dongle with a variation of a 3 sim. has its own APN and a static IP, left over from a work project.
flashed the new boot, copied the new system and made the permissions mod. the various apps show up
under about tablet it shows baseband as unknown and if i try to add an APN it goes through the motions but doesnt add it to the list.
I've attached the logs, i'm no developer but i can follow instructions if any one can suggest any thing. there is every possibility i've messed up in the install so feel free to suggest dumb stuff that i should have known in the first place.
It could just be that the dongle isn't supported in which case we can chalk up a zte MF112 as been a duffer as well (had one kicking about so gave it a go)
Click to expand...
Click to collapse
Hi There,
Thanks for trying...... The Logcat proved useful. As many a woman has said to me, "It's not you it's me" :laugh: ..... You need to make the rest of the added files in /system/bin executable.
Code:
adb shell chmod 755 /system/bin/usb_modeswitch
adb shell chmod 755 /system/bin/rild
this line in the logcat explains it all
Code:
E/logwrapper( 842): executing /system/bin/usb_modeswitch failed: Permission denied
Good Luck and thanks for the detailed info...
It Lives!!!
I can see mobile networks, signal strength and all that good stuff. just need to figure out the APN details now for this cranky sim
top job trevd
laz2336 said:
I can see mobile networks, signal strength and all that good stuff. just need to figure out the APN details now for this cranky sim
top job trevd
Click to expand...
Click to collapse
It should pull the apn off the sim automatically.... the Radio Interface Layer may need a bit more tweaking, If you want to post more logcats, I wouldn't mind a cheeky look because that's how I get my kicks
Don't forget to turn your Wifi Off...... And sometimes turning data roaming on helps. especially with t-mobile/orange in the UK
happy to run logs for you. i will say though that this is no run of the mill sim, it sits on top of 3 as a carrier but has its own 3rd party APN, login details and a statip IP address when it is connected. it does pick the apn from the sim and show the default 3 apn settings, i just need to tweak them a bit.
I'll find a hub and get some logs with modem hooked up.
update
wow these logs get big quickly. this one has the modem been removed, reconnected, negotiating with the network and trying to log in. I've removed apn,usernames and passwords and replaced them with <APN> <username> <password>. I can give you the APN name over pm if it helps but for security reasons i can't give out the login details, bit too company specific.
laz2336 said:
happy to run logs for you. i will say though that this is no run of the mill sim, it sits on top of 3 as a carrier but has its own 3rd party APN, login details and a statip IP address when it is connected. it does pick the apn from the sim and show the default 3 apn settings, i just need to tweak them a bit.
I'll find a hub and get some logs with modem hooked up.
Click to expand...
Click to collapse
A Bit like GiffGaff!, Cyanogenmod Rom maintain a hugh list, I think he must have got every carrier in the world, Check it out here ( apns-conf.xml on github )
trevd said:
A Bit like GiffGaff!, Cyanogenmod Rom maintain a hugh list, I think he must have got every carrier in the world, Check it out here ( apns-conf.xml on github )
Click to expand...
Click to collapse
just had a quick search, he aint got mine
bit more of an update, hooked up the ZTE MF112 in the office this morning it seen and sees the network. This dongle is unlocked so i've given it a go with my own vodafone sim from my phone. copied the apn settings across from the phone (just the standard vodafone 'internet' APN), it goes through the the motions of trying to connect but never gets there. I'll fire up the logging a bit later and get you a bit more data.
on a side note so far both these dongles have been able to be connected while the device is turned on and been picked up automaticaly.
I think it may be more permissions
laz2336 said:
bit more of an update, hooked up the ZTE MF112 in the office this morning it seen and sees the network. This dongle is unlocked so i've given it a go with my own vodafone sim from my phone. copied the apn settings across from the phone (just the standard vodafone 'internet' APN), it goes through the the motions of trying to connect but never gets there. I'll fire up the logging a bit later and get you a bit more data.
on a side note so far both these dongles have been able to be connected while the device is turned on and been picked up automaticaly.
Click to expand...
Click to collapse
Hi I had a little sleep on it, it's probably more persmission issues *facepalm*
Code:
adb shell chmod 755 /system/etc/ppp/init_pppd_gprs
adb shell chmod 755 /system/etc/ppp/ip-up-gprs
adb shell chmod 755 /system/etc/ppp/ip-down-gprs
As a test You can try running
Code:
adb shell /system/etc/ppp/init_pppd_gprs
which should start a native connection ( the modem will connect but android won't know about it ), although you can use the built in browser and Gapps ( play , gmail ,youtube etc ) as they don't use androids connectivity service to check for connections
no logs yet but heres the update so far.
set the permissions on those three files and had another go. no difference. do all the files that get put in the ppp directory need to be executable?
trying to start the connection with init_pppd_gprs doesn't manage to connect with either dongle, though the E353 does seem to get further. it moves on to a new line in terminal emulator with out returning any thing. with the MF112 it gets quite vocal about not been able to find the usb device despite it showing as been registered on the network under system properties.
sadly can't put the voda sim in the E353 as the bloddy thing is locked.(did try, though it pulls the APN details it won't see the voda network)
when I connect to a captive wifi, I want to use the connection as is (maybe I want to login without telling google - since the builtin authenticator uses their gstatic domain, or maybe I want to probe the network as it is being redirected, or maybe I just want firefox to manage my password to the portal, etc)
but after I select "use wifi as is" on the android webview builtin auth screen, android starts to route all and every traffic to my 3g/4g data connection instead, until I disable and re-enable wifi.
it will only ever redirect traffic to wifi after it successfully got the correct 204 from gstatic.com
is there anyway to work around this?
I am on android6, but I think I has always been like that.
gcbxda said:
when I connect to a captive wifi, I want to use the connection as is (maybe I want to login without telling google - since the builtin authenticator uses their gstatic domain, or maybe I want to probe the network as it is being redirected, or maybe I just want firefox to manage my password to the portal, etc)
but after I select "use wifi as is" on the android webview builtin auth screen, android starts to route all and every traffic to my 3g/4g data connection instead, until I disable and re-enable wifi.
it will only ever redirect traffic to wifi after it successfully got the correct 204 from gstatic.com
is there anyway to work around this?
I am on android6, but I think I has always been like that.
Click to expand...
Click to collapse
Do you have any kind of Linux ide? Have you tried making a tunnel?
Or is that what your looking for. I'm not 100% sure what your looking for. If your trying to skip Hotspot authentication? Or anything like that Then a tunnel would work fine.
Sorry I can't be of much else help
If your phone is rooted or has a custom ROM (Which would obviously indicate that the phone is rooted), there is a solution that you can try using a terminal (Or ADB shell).
Issue the command: "settings put global captive_portal_detection_enabled 0" That should prevent captive portal detection and gstatic confirmation. This should work, I haven't tried it personally though.
Additionally, you can setup a captive server.
Issue the command: "settings put global captive_portal_server g.cn"
Restart your phone, and you should have access to the pages.
Basically, connecting as is, requires you to reach a site that does not require 204 confirmation and afterward other sites should be accessible. Let me know if this helps.
Josh Ross said:
If your phone is rooted or has a custom ROM (Which would obviously indicate that the phone is rooted), there is a solution that you can try using a terminal (Or ADB shell).
Issue the command: "settings put global captive_portal_detection_enabled 0" That should prevent captive portal detection and gstatic confirmation. This should work, I haven't tried it personally though.
Additionally, you can setup a captive server.
Issue the command: "settings put global captive_portal_server g.cn"
Restart your phone, and you should have access to the pages.
Basically, connecting as is, requires you to reach a site that does not require 204 confirmation and afterward other sites should be accessible. Let me know if this helps.
Click to expand...
Click to collapse
no root on the phone (damn blackberry priv) and no control of the portal.
this is so infuriating. This is trivial, banal even, on any device i control. Feel like a kid on training wheels every time i touch my phone.
I am debating whether or not to post this here, on Howard Forums or on CDMA Gurus, but I'll post it here as this forum seems the most popular and has a great SEO so hopefully someone googling how to do this will see this thread and find it helpful.
This summer I picked up a used Verizon Samsung SCH-LC11 hotspot. It is surprisingly small and lightweight but heavy and feels high quality.
I was surprised to see the built in web interface didn't have a software update button, nor any options to change APN settings and so on. I searched Google and couldn't find ANYTHING initially on how to do this, but found that there was a software update which mine didn't have that gave it the ability to choose LTE only, 3G CDMA only, and so on, which I thought would be nice to have. After a lot of digging, I finally found out how to do this.
First you'll need to install the latest Samsung USB drivers from here https://developer.samsung.com/mobile/android-usb-driver.html
Once that is done, you'll need to download the Samsung firmware update utility for this hotspot which can be found here
Verizon: https://www.samsung.com/us/support/downloads/?model=N0020110&modelCode=SCH-LC11ZKAVZW
US Cellular: https://www.samsung.com/us/support/downloads/?model=N0020124&modelCode=SCH-LC11ZKAUSC
Download the one listed as "PATCH,OTHERS" and run it, and follow the instructions, once that's done you should now be on the latest firmware!
This next one is something that initially was reported as impossible, changing the APN settings. There is nowhere in the web menu to do this and when you plug this device into your computer nothing happens.
After months of searching though, I finally found a thread on CDMA Gurus related to flashing and doing more involved things with this hotspot, and this showed how to enable debugging mode!
To do so you'll need to power your hotspot on and connect to it's wifi network, and then head to the admin page at http://192.168.1.1/ and login with the wifi password found on the sticker underneath the battery cover. If your sticker is missing the password is the last 8 digits of your IMEI, ignoring the last digit of the IMEI. For example if your IMEI is 123456789123456 your password is 78912345.
Once you're logged into the admin page go to http://192.168.1.1/selectusbmode.html and enable USB debug mode and click Save. Then go into "Configuration" and "Diagnostics" and click restart and connect the hotspot to your computer via USB. You should hear the device connect sound.
Now you'll need to use a program called AT Command Tester available at https://m2msupport.net/m2msupport/download-at-command-tester/ as we will set the new APN of your choice using AT commands, and this program let's you do that all through a simple, easy to use GUI.
You will need the latest version of Java installed on your computer as AT Command Tester requires Java to run, you can obtain the latest Java here https://www.java.com/download/ie_manual.jsp
Once you have the latest version of Java installed and have downloaded and installed AT Command Tester, open up your start menu and launch AT Command Tester, if this doesn't work navigate to C:\Program Files (x86)\AT Command Tester and run "atc.bat"
You should see AT Command Tester open, and now you'll need to establish a connection to the Samsung hotspot. Click on "Find Ports" and wait, now you should see 3 COM ports available from the dropdown selection list, in my case it was COM16, COM17 and COM18 and the one I needed to use was COM16, however yours may vary and you may need to try each one until you establish a connection, I'd recommend trying the lowest numbered one in the list. Once you have selected the proper COM port click "Connect" and in the log in the right you should see it detect the hotspot and list Qualcomm as the device type.
Now you can follow the instructions here for setting up the APN https://m2msupport.net/m2msupport/how-to-setup-access-point-network-apn-in-cellular-modules/ and once you have set the proper APN you can restart your hotspot and you should have everything working!
If you for some reason need to change other settings, you can use DFS Qualcomm Tool to do so. This device will also be detectable via QPST and CDMA Workshop too.