Related
WiFi on campus here uses WPA enterprise auth - good. I was shocked when I saw that the phone seemingly didn't support it. Network didn't even appear in the list, and Add Network only supports WPA Personal / WEP. How Apple of them. But WHY? It's wpa_supplicant behind the scenes.
I've been using campus wifi successfully for a few days now. It seems to integrate well enough - the wifi settings menu doesn't seem to break at all, the enterprise-authed network and status are listed correctly including the 'lock' icon, etc.
These instructions are slightly modified from being specific to the particular university (posted locally too, you see). If you can rub some braincells together, this can be adapted. The parts regarding a certificates file may or may not be needed in your setup, for example.
* Get a root shell
* cd /data/misc/wifi/
* cat wpa_supplicant.conf
* The existing supplicant config is displayed - copy and paste it into a text editor (the beginning bits are important, as are your existing networks)
* Paste in a working wpa_supplicant.conf section for your network at the end
* Fill in username and password in the new section. Replace the path for cacerts.pem with /data/misc/wifi/cacerts.pem
* Save the new config onto the SD card
* Save the cacerts.pem (same site) onto the SD card also
* On the handset: In the settings/storage menu, disable the SD card for USB storage (otherwise, can't access it from the shell)
* rm wpa_supplicant.conf
* cp would be used here normally, but it isn't in the stock image: dd if=/sdcard/wpa_supplicant.conf of=wpa_supplicant.conf
* chmod 666 wpa_supplicant.conf (Warning! Readable/Writable by EVERYONE! Use 664 such that only root can write it if you want, but this will possibly disallow changes by the settings app - if chown was available, ownership would be reverted back to wifi:wifi)
* dd if=/sdcard/cacerts.pem of=cacerts.pem
* chmod 444 cacerts.pem (needs to be readable by wifi user)
* The network should appear in the wifi menu and connect if you enable wifi. Reboot if not maybe?
Problems:
* Permissions are a bit wonky due to lack of chown. The process would be cleaner with busybox installed (possible with root), but this process is written to work on a stock RC29 handset.
* It will almost surely fail following an update. Try not to give up root before the WiFi UI is patched
* Maybe there's a reason that enterprise auth is absent from the settings UI
* WiFi settings page may or may not break. WiFi settings page may or may not undo your changes.
A quick troubleshooting tip: if you've dealt with wpa_supplicant before, note that wpa_cli is available to root. Helpful to diagnose any issues that crop up.
Enjoy.
How Apple of them. But WHY? It's wpa_supplicant behind the scenes
Click to expand...
Click to collapse
I suspect it's because the majority of consumers only access wifi networks secured through psk or mac-address. iirc my university used mac-address too. Not sure if that's changed by now. In any case, I wouldn't hold my breath for official support on the G1. Maybe on some future Android device with enterprise in mind.
Anyway, good tips and good first post. Welcome to the forum
busybox has chown
WPA2
Can I ask a question?
The SSID for your campus wifi is not broadcasted, correct? if this is true, then it won't show up and the only way to get access is to add it manually.
Now when you go to add it manually, did you try to change the type of security before you flipped out the keyboard? Just wondering since WPA2 is clearly seen if you have the keyboard in and if you have it out it looks like WPA2 isn't an option but if you try to move the security box with a swipe up with your finger, WPA2 will be shown. I haven't had a single problem attaching to my home or work network using WPA2 PSK since RC19 and beyond.
Yep, busybox has chown - which makes the whole thing cleaner and safer. My instructions were written originally with no assumptions as to previous modding, incl how to get telnet.
The wifi network here does broadcast, but is filtered out due to "unsupported" security. Add network lists wpa2 personal but not enterprise.
I modified my wpa_supplicant.conf file using your instructions and it worked!
Thanks!
Dave
vSymm said:
How Apple of them. But WHY? It's wpa_supplicant behind the scenes.
Click to expand...
Click to collapse
Because there's a substantial amount of UI work that needs to be done for WPA2-Enterprise compared with the relatively common WPA2-PSK.
My advice? If official support is something you'd like, go write it and submit a patch to the Android devs.
Not working
I can't get this to work. It says "failed to start wifi".
My non-enterprise wifi won't even work now. It connects but apps say network error.
I am trying to connect to my university's wifi that is "Secure 802.1X authentication and EAP-TTLS with PAP inner-authentication (anonymous)"
Can anyone give me an example config for this? It doesn't use a certificate.
Confirm that the permissions were set correctly on wpa_supplicant.conf
I'm sure you can find an example for that particular setup online somewhere.
happyface_0 said:
I can't get this to work. It says "failed to start wifi".
My non-enterprise wifi won't even work now. It connects but apps say network error.
I am trying to connect to my university's wifi that is "Secure 802.1X authentication and EAP-TTLS with PAP inner-authentication (anonymous)"
Can anyone give me an example config for this? It doesn't use a certificate.
Click to expand...
Click to collapse
try this:
adb shell
cd /data/misc/wifi
chown 1010:1010 wpa_supplicant.conf
Worked for me too, but the connection was really unstable. I've added the option bssid to wpa_supplicant.conf to prevent roaming. Now it works really well on my desk, but I haven´t tried the rest of the company.
need help connecting
I'm trying to connect to a campus network, I see the SSID detected (as following), and It tries to connect and aborts by itself.
my wpa_supplicant.conf shows this:
network={
ssid="Techwifi"
scan_ssid=1
key_mgmt=NONE
priority=2
}
hey guys,
will this also work with WPA2 and EAP/TTLS with PAP?
or do you know when this feature will be integrated?
thaks a lot
linulli said:
hey guys,
will this also work with WPA2 and EAP/TTLS with PAP?
or do you know when this feature will be integrated?
thaks a lot
Click to expand...
Click to collapse
Yes, I have it working.
Code:
network={
ssid="ssidname"
scan_ssid=1
key_mgmt=WPA-EAP
eap=TTLS
identity="user"
password="pass"
phase2="auth=PAP"
}
Note: It seems to drain my G1's battery pretty nicely and it starts to get hot after being connected for a bit. Also, my G1 added disabled=1 to the end of this network after the ADP1 v1.1 update, strange.
Thanks happyface_0,
so I will have a few minutes online.
Is there a way to alter your wpa_supplicant settings on an unrooted German G1 , or how can i downgrade and then alter the settings, does anyone know?
I'd love to know that too, i really want to use wifi at work.
Can we do anything to help you help us?
Maybe someone with a US RC33 can look if the WPA 2 Enterprise support finally made it into the gui of the G1 , then our problem would be solved ,
can´t find something on the net which says that WPA 2 Enterprise was part of the Internet .
So please can somebody look up his or her connection settings for wlan and tell us if WPA 2 Enterprise is available now?
Gedomania said:
Maybe someone with a US RC33 can look if the WPA 2 Enterprise support finally made it into the gui of the G1 , then our problem would be solved ,
can´t find something on the net which says that WPA 2 Enterprise was part of the Internet .
So please can somebody look up his or her connection settings for wlan and tell us if WPA 2 Enterprise is available now?
Click to expand...
Click to collapse
Neither WPA-Enterprise nor WPA-2 Enterprise are available yet without actually editing the wpa_supplicant configuration manually, even on RC33.
Hmm thats pretty sad, is it actually possible to write a program which can edit the Wpa_supplicant file so that we can manually insert the settings we need to get WPA 2 Enterprise working , even on phones without root?
Guys, apologies if this has been posted before but couldn't find it.
I've rooted my phone with JF RC9, but for some reason I can't use the wifi tether (one of my main reasons for rooting in the first place). So far as I can tell, I have root (in that I can su in a terminal) and my pc can see the ssid of the phone and connects quite happily but I don't get internet access for some reason - am I missing something really obvious or have others encountered this before?
Hi!
I assume you are using "Wifi Tether for Root Users" ...
If yes please make sure that you are using the lastest Version (0.97.1) which is available here:
http://code.google.com/p/android-wifi-tether/downloads/list
(0.97.1 fixes some cupcake-related issues)
You say that you see that your client is able to connect ... right?
Please check the following:
1) What ip-address do you got from the phone?
(For Windows): Open command-prompt and type "ipconfig"
You should got an ip-address like: 192.168.2.100 (maybe 101, 102, ... at the end).
2) Are you abel to ping the standard-gateway?
type: ping 192.168.2.254
You client must support ad-hoc mode - otherwise it won't work.
Please check and report back.
Man, have I been dense. After spending a couple of weeks, scouring forums, taking the classic I.T. approach of 'turn off, wait, turn on again', I've figured it out...
I'd set up a static i.p. on my pc a long time ago so was still trying to make it through the router...
doh!
Thanks for your reply though harry_m, it was your comment around pinging the i.p. address tat jogged my memory! works like a charm now
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)
I have a rooted Skyrocket. About a year ago I used a QuickSSHd to ssh into my phone from my local wifi network. I haven't used the application in a while and somewhere in that time ATT did some sort of software update that made the windows less Apple-like but not much else. That may or may not have something to do with the fact that if I try to ssh in now the request just times out. I can get a shell through the usb cable using adb (or a terminal program), confirm that I still have root, and see the sshd process with ps | grep dropbear. I also know that something is trying to connect because if I don't launch the sshd and try to ssh in I just get "connection refused" and nmap -p 22 doesn't show anything open but after sshd is running the port shows as "22/tcp filtered SSH" but the ssh request just sits there until it times out. I've tried running dropbear manually through adb, an updated QuickSSHd, and another very nice looking Android application called "DropBear SSH Server" with the same results. I've also tried changing ports. I even make an /etc/shells file because that showed up on some really old how-to document.
When trying to ssh to the Skyrocket from a laptop Wireshark shows the requests going out repeatedly but no replies from the Skyrocket. Shark running on the Skyrocket shows nothing (although other wifi traffic does show up). As a diagnostic I tried sshing from the Skyrocket to my laptop over wifi and wireshark on the laptop shows traffic both ways but they never close the deal. It's as if something is intercepting any incoming ssh traffic on the Skyrocket.
For what it's worth I can ssh from the skyrocket to localhost or its own wifi IP address in an adb shell. It seems like some sort of firewall issue. Any ideas? Do I need a new busybox (whatever that is)? I really don't want to flash any major OS modifications, I just want to be able to ssh in and then start on the real project (trying to talk to an rtl-sdr dongle...)
Thanks!
Dave
c'mon guys, 169 reads and no ideas? Is this something weird with just my phone or are they all this way and everyone's given up?
Ive used developer mode to install my own custom app, however, the session time runs for 50 hours then removes my app, I can if I remember try to go back to dev mode and click extend but is there any way to leave this on permanently so that I can us my app without having to constantly extend the session? TV Software version is 03.01.06, thanks in advance.
Badger
Hey,
old question, but someone may still need this.
This is for LG TVs with WebOS. Luckily, extending Dev Mode it's fairly easy and won't require root (which I preferred).
I spent some hours now trying to identify such a way and thanks to Neur0toxine I found an URL you can call periodically to reset the timer.
First of all, you need your session token. When you have enabled the developer mode, you have the passphrase, generated the ssh keys, etc.
Connect to your TV via ssh using
Code:
ssh -p 9922 -i ~/.ssh/{your_webos_key_file} [email protected]{ip_of_tv} -T
You need to set the port to 9922. -i references the ssh key. -T skips a "PTY allocation request failed on channel 0" error which might be confusing.
Enter the passphrase, when asked.
Now it probably seems that nothing has happened, as you're just in a new line and no location of execution is displayed like we're used to (maybe due to the PTY? dunno), but you can type commands. Try the ls command to check connection if you're not sure.
When connected, get the session token using:
cat /var/luna/preferences/devmode_enabled
From Neur0toxines repo I extracted two URLs.
This will check the time left in dev mode:
https://developer.lge.com/secure/CheckDevModeSession.dev?sessionToken={your_token}
This will reset the dev mode timer:
https://developer.lge.com/secure/ResetDevModeSession.dev?sessionToken={your_token}
So to keep your dev mode active, call the second URL within the 50 hours. I do so periodically using crontab on my raspberry. If you do not have a raspberry or another server, you may find a free online cronjob service for this purpose.
To call the URL every day at 3 AM I got into my raspberry, opened cronjobs using "crontab -e" and added the following line
0 3 * * * /usr/bin/curl --silent https://developer.lge.com/secure/ResetDevModeSession.dev?sessionToken={your_token} &>/dev/null
The first five symbols are minutes, hours, day of month, month, day of week. * = any.
I verified this workflow using my browser, but I just now finished setting everything up. So tomorrow I will see if it all worked automatically using crontab, but in general this should work. Any way to periodically call the URL should (unless there's something else to think of like a change in the token at some point but currently I won't assume that).
Then install the best app: YouTube Extend for WebOS and never see ads, in video sponsors and so on.
YouTube ads you made me do this. Spending all this evening to get this running. It has become unbearable
Another option, if they should ever close the possibility to extend dev mode via this URL, would be installing their CLI to a raspberry and periodically execute the ares-extend command.
Till now I have not found any option to just permanently activate dev mode when connected via SSH for example by disabling the counter or whatever. This would be best for everyone not having a raspberry or else.
But as I'm quite happy with my current solution I have no motivation looking any deeper
Thank you very much! I
can confirm that your solution works. I have set up a cron job on my PiHole and can now enjoy YouTube ad-free without manually resetting the devmode time every day.
Glad to hear that!
works great, thank you. let me know when u find a fix for the screensaver issue on ltt vids
Awesome. It worked for me today very well. Because of an error in domain name resolution i used ip adress instead:
0 3 * * * /usr/bin/curl --insecure https://52.78.120.149/secure/ResetDevModeSession.dev?sessionToken=<your Token> &>/dev/null
Thx.
I configured Github actions with a private repo for this purpose.
When I call Check URL I see 38 hours remaining like in DevApp, so I call Reset URL and after that Check URL again and I get back 59 hours remaining, but I still see 38 hours remaining in DevApp even after killing the app and restarting TV. Does it work then?
So apparently, the timeout in the DevApp won't get updated, but as long as it's updated on LG's backend its ok and dev session won't timeout even if the app shows 00:00:00 time remaining...
ns6000 said:
So apparently, the timeout in the DevApp won't get updated, but as long as it's updated on LG's backend its ok and dev session won't timeout even if the app shows 00:00:00 time remaining...
Click to expand...
Click to collapse
Ok good to hear. Was a bit confused when I realized it's not updated in the DevApp though backend is updated and wanted to dig deeper. So maybe it's a bug in the DevApp after an update because some time ago it reflected the time correctly.
Hello,
I have an old LG TV with WebOS 3.5.5. Is there a way to extend the Developer Mode while the TV is off ?
For example, the Developer Mode is on for 50h, and from time to time I will leave my TV off for more than 2 days. When I' turn it on, the Developer Mode is disabled.
It works by calling "ares-extend-dev" command while the TV is on, it brings up the DeveloperMode app and extends the time, which is fine..
inugoliath91 said:
Hello,
I have an old LG TV with WebOS 3.5.5. Is there a way to extend the Developer Mode while the TV is off ?
For example, the Developer Mode is on for 50h, and from time to time I will leave my TV off for more than 2 days. When I' turn it on, the Developer Mode is disabled.
It works by calling "ares-extend-dev" command while the TV is on, it brings up the DeveloperMode app and extends the time, which is fine..
Click to expand...
Click to collapse
Well, yes. The way described above should work just fine. It calls the web-api on the lge server to extend the the time which seems to be checked by the developer app.
So I was away for like several weeks last year and had my rasperberry cronjob resetting session time each day and it was still active when I came back.
I think when I got my LG tv it also had some WebOS 3.xx Version at the beginning.
schnills said:
Well, yes. The way described above should work just fine. It calls the web-api on the lge server to extend the the time which seems to be checked by the developer app.
So I was away for like several weeks last year and had my rasperberry cronjob resetting session time each day and it was still active when I came back.
I think when I got my LG tv it also had some WebOS 3.xx Version at the beginning.
Click to expand...
Click to collapse
It works perfect! Thank you for your quick response!
schnills said:
Hey,
old question, but someone may still need this.
This is for LG TVs with WebOS. Luckily, extending Dev Mode it's fairly easy and won't require root (which I preferred).
I spent some hours now trying to identify such a way and thanks to Neur0toxine I found an URL you can call periodically to reset the timer.
First of all, you need your session token. When you have enabled the developer mode, you have the passphrase, generated the ssh keys, etc.
Connect to your TV via ssh using
Code:
ssh -p 9922 -i ~/.ssh/{your_webos_key_file} [email protected]{ip_of_tv} -T
You need to set the port to 9922. -i references the ssh key. -T skips a "PTY allocation request failed on channel 0" error which might be confusing.
Enter the passphrase, when asked.
Now it probably seems that nothing has happened, as you're just in a new line and no location of execution is displayed like we're used to (maybe due to the PTY? dunno), but you can type commands. Try the ls command to check connection if you're not sure.
When connected, get the session token using:
cat /var/luna/preferences/devmode_enabled
From Neur0toxines repo I extracted two URLs.
This will check the time left in dev mode:
https://developer.lge.com/secure/CheckDevModeSession.dev?sessionToken={your_token}
This will reset the dev mode timer:
https://developer.lge.com/secure/ResetDevModeSession.dev?sessionToken={your_token}
So to keep your dev mode active, call the second URL within the 50 hours. I do so periodically using crontab on my raspberry. If you do not have a raspberry or another server, you may find a free online cronjob service for this purpose.
To call the URL every day at 3 AM I got into my raspberry, opened cronjobs using "crontab -e" and added the following line
0 3 * * * /usr/bin/curl --silent https://developer.lge.com/secure/ResetDevModeSession.dev?sessionToken={your_token} &>/dev/null
The first five symbols are minutes, hours, day of month, month, day of week. * = any.
I verified this workflow using my browser, but I just now finished setting everything up. So tomorrow I will see if it all worked automatically using crontab, but in general this should work. Any way to periodically call the URL should (unless there's something else to think of like a change in the token at some point but currently I won't assume that).
Then install the best app: YouTube Extend for WebOS and never see ads, in video sponsors and so on.
YouTube ads you made me do this. Spending all this evening to get this running. It has become unbearable
Click to expand...
Click to collapse
Thanks so much for this, crontab works like a charm!
However, after almost i month, the developer mode loses login and asks again for it, thus losing all the app installed. Is there a way to keep the login?
gunther82 said:
Thanks so much for this, crontab works like a charm!
However, after almost i month, the developer mode loses login and asks again for it, thus losing all the app installed. Is there a way to keep the login?
Click to expand...
Click to collapse
Hello,
I would like to bring to your attention that recent changes have been made to the system, and as a result, the developer mode has been extended to 999 hours. I kindly suggest that you attempt to resolve any issues by performing a new login and updating the key. Please note that this recommendation is not a guarantee of resolving the issue, but merely an attempt to determine the cause.
inugoliath91 said:
Hello,
I would like to bring to your attention that recent changes have been made to the system, and as a result, the developer mode has been extended to 999 hours. I kindly suggest that you attempt to resolve any issues by performing a new login and updating the key. Please note that this recommendation is not a guarantee of resolving the issue, but merely an attempt to determine the cause.
Click to expand...
Click to collapse
Yes, I've seen that now the developer mode has been extended to 999, and with the crontab script I reset it every day, but my issue is that after almost a month the developer mode loses the login, and thus all the apps I installed via webos-dev-manager. I have to login again in the developer mode of the TV and then install again the apps, and update the script with the new key.
Is there a way to avoid losing the login?