I personally enjoy using my new Fire HD 10 , but I don't want it tied down to an Amazon account. At first startup, I was able to bypass registration by skipping the WiFi connections. However, after that, when a system update happens, it asks me to re-register, and this time it skips past the WiFi question, because I already had it registered by that point.
The first option to get past it was to move away from my WiFi access point. However, I found another way to do this.
If you've already turned on USB debugging on your device, you can connect it to a PC, and, with the "adb" tool, run:
adb shell "am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher"
This will cause the launcher to start, where you can then access the WiFi settings. From here you can "Forget" the connected network, restart, then "Add Network Connection", "Cancel", then the "Skip Registration" will appear.
It's a bit of a pain. Does anyone have a better solution?
groboclown said:
I personally enjoy using my new Fire HD 10 , but I don't want it tied down to an Amazon account. At first startup, I was able to bypass registration by skipping the WiFi connections. However, after that, when a system update happens, it asks me to re-register, and this time it skips past the WiFi question, because I already had it registered by that point.
The first option to get past it was to move away from my WiFi access point. However, I found another way to do this.
If you've already turned on USB debugging on your device, you can connect it to a PC, and, with the "adb" tool, run:
adb shell "am start -n com.amazon.firelauncher/com.amazon.firelauncher.Launcher"
This will cause the launcher to start, where you can then access the WiFi settings. From here you can "Forget" the connected network, restart, then "Add Network Connection", "Cancel", then the "Skip Registration" will appear.
It's a bit of a pain. Does anyone have a better solution?
Click to expand...
Click to collapse
Try to disable unwanted Amazon system updates by executing adb shell pm disable-user com.amazon.device.software.ota and adb shell pm disable-user com.amazon.device.software.ota.override
Related
I don't post much (obviously, and keeping me from putting this in Dev forum or posting external links :| ) but I do work a lot on the sides and figured out how to get a Verizon non-smartphone to act as a 3g dongle for the Acer A500. This is a copy of my tutorial originally posted on TegraOwners.
First off my setup;
Acer Iconia A500; Running Thor v14.2 ROM (Possible to work on other ROMs/kernels that support 3g dongles)
Build.prop mod installed from -snipped because of limit, will edit when able-
Phone; LG EnV2 Verizon prepaid.
Solution should work for any tether enabled verizon phone, POSSIBLY Verizon Dongles, and other brands of phones besides LG.
This guide assumes you either have, or know how to flash Thor's rom, and other flashable zips. I will not provide ADB instructions, but if someone would like to send me instructables how; I will add them into this post.
From a 'fresh' or unmodified version of Thor's ROM (I used v14.2, follow the build.prop install instructions in the link above. (Link removed because of limitations on posting)
Then using root explorer (or equivalent root browser) remount /system rewritable and open the build.prop file in a text editor.
Comment out ro.carrier=wifi-only and uncomment the rest of the block. It should match the following when done;
#ro.carrier=wifi-only
picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true
Save the file and check permissions; they should still be rw-r--r-- and reboot the tablet.
This enables the 3g menus, and using the previous build.prop, lets your A500 read as an A500 instead of an EPAD.
Note: You DO NOT need to set an APN, Verizon, being a CDMA network, does not use APNs. The 'login' information is in the phone itself. It just needs the commands to initiate a data connection.
Now is where it got tricky to figure out; If you open a terminal emulator as root (type su at the prompt) and type ppp-start.sh you will get a couple of lines with this error;
pppd: In file /system/etc/ppp/peers/3g: unrecognized option '/dev/ttyUSB2'
or similar.
In the terminal prompt, type dmesg | grep tty it will return several lines, I noticed I had a device on ttyUSB0 not ttyUSB2.
On study, some modems make several ports for control, monitoring, etc. mostly data connections are on ttyUSB2, which is my guess why it was default.
I figured out by editing the ppp config file that ttyUSB0 wouldn't error, but wouldn't start either. I looked back at the grep and noticed something else that matched and I had seen before in my studies; ttyAMC0
So using the same method as editing build.prop, edit /system/etc/ppp/peers/3g it should read as follows;
ttyACM0
921600
crtscts
defaultroute
modem
noauth
noipdefault
persist
updetach
usepeerdns
connect 'chat "" AT OK ATD#777 CONNECT'
Note the ttyUSB2 being changed to ttyACM0, apparently the data serial for the phone, and atd number being changed to #777, Verizon's 3g number. (Speculation that you could increase the 921600 for higher USB bus speed, but I've not tested this).
Save the file and confirm the permissions are; r-xr-xr-x
Open terminal emulator with root permissions and again try ppp-start.sh
This time after it says pppd, after about 5 or so seconds, it should list your IP and other information confirming the connection. You should see TX and RX packet info on the phone screen. If so, congrats you are now connected via 3g with the phone.
To turn off the connection, use the command ppp-stop.sh I suggest making a couple script manager widgets to 'shortcut' these.
Note; If the screen turns off, the phone will disconnect and you will have to unplug the phone, restart the ril daemon, plug the phone back in, and run ppp-start.sh again.
You can install the ril-daemon_restarter.apk to easily restart ril, or in terminal emulator; stop ril-daemon then start ril-daemon
(Had to remove link for limitation, google for now, will add in when I can. suspected credit goes to dmatusek76 on XDA.)
Things that I've tested;
Browser works despite saying 'no connection' at the start.
Market can browse apps, but not download them.
GMail seems to receive, but not send emails.
Netflix works.
Edit: OpenVPN works.
Google Maps/Navigation works (downgrade to stock, latest update FCs)
Best part; The Portable Wireless Hotspot option in Settings > Wireless & Networks > Tethering & Portable Hotspot menu works to create a 3g Wi-Fi hotspot.
All connections through the hotspot are NOT BLOCKED; i.e. using my android to connect to the tablet, I was able to browse apps, download them, send emails, etc.
My theory on the reason the tablet won't; Some apps (like Google Voice and AndroIRC), check for an internet connection BEFORE TRYING, and if it isn't 'available' it just gives you a warning and stops without actually TRYING. Other apps just try to access the internet without checking for a connection first (Like Netflix), and they work.
This theory is backed up by the Browser first checking for a connection (hence the 'no connection available' popup), but then loading as it continues to try anyway after the check.
Using the wireless hotspot, the phone sees it as a full connection, so nothing stops during the 'network check'.
I hope this information might be useful in getting other devices, phones, dongles, etc. working with this masterful tablet.
Please let me know if it works and if you use other equipment.
Credits;
Thor for his awesome rom that supports USB 3g in the first place
pimpmaneaton for the build.prop
So, the touchscreen on my Nexus 4 broke this weekend. I have a new device coming in, but in the meantime I need to be able to access the device to use a few different apps and send/receive some SMS messages from it.
I found a guide on reddit (Apparently I'm not allowed to post links, but it'll be the first result if you google "How I managed to use my Android device with a broken touch screen")
It's not exactly simple, but it should work.
Unfortunately, I discovered that in order to use ADB shell commands, a pop-up window should appear on the phone to allow/disallow USB debugging. (USB debugging is enabled already, but there appears to be an additional 'authentication' step)
Unfortunately, I can't use the phone's touchscreen, so I can't unlock it or tap the notification that will allow me to authenticate the phone.
Is there a way I can get around that authentication step?
The device is unlocked and rooted.
Back story: I've always rooted in the past, but purely for entertainment / backup purposes. Now however, I actually NEED root for my phone to function as I believe it should due to a "glitch" in the system. Please reference the thread that I started in the google help forums here (sorry can't post outside links):
I'm a new Project Fi customer with a Nexus 6P. The phone is fantastic, but I'm having a problem making calls while at home. The Project Fi CSR that I chatted with was not very helpful and was only able to tell me what I already knew.
The problem is that one of my neighbors has a Sprint "home cell tower" device (I believe it's an Airave but no way to know for sure) that my phone connects to when I attempt to place a call. When I hit send, I hear 3 beeps followed by an automated message "We are unable to complete your call at this time, please try again later; Message 12: Switch 2195"
Currently, my only option if I want to make a call is to turn on "airplane mode" and then turn wi-fi back on so that it reconnects to my home wi-fi and then place the call. Obviously this is not ideal as it's not really practical to turn airplane mode off and on when I come and go from my house.
Is there another option that I am missing. It seems almost too obvious that there should be a "prefer wi-fi calling when available" toggle somewhere, but I don't believe there is.
Any ideas / suggestions?
Click to expand...
Click to collapse
and which I proceeded to find a solution for as detailed here (sorry can't post outside links):
I've found a better solution (or at least a more convenient one) to this problem. This solution is also workable for people who feel that wi-fi calling would be more reliable in specific places than their cellular connection for making phone calls. The only caveat: you need to root your phone for Tasker and System Settings to function as required for these tasks. I have used the apps Tasker and Secure Settings to set up a rule for my phone that will automatically turn off the cellular radios and leave wi-fi on when I'm at home. When my phone connects to my home wi-fi as identified by the SSID of my home wireless router, Tasker initiates the Task to turn the cell radios off thus forcing all incoming and outgoing calls be routed over wi-fi. When my wi-fi connection is lost (when I leave home), Tasker initiates another task to turn the cellular radios back on. This has been working flawlessly for about 3 weeks on my phone, and requires absolutely no user input after the initial setup. I highly recommend this solution as it is far more convenient than having to use separate dialer apps when at home and away.
Click to expand...
Click to collapse
Long story short, I need to use Tasker and Secure Settings to manipulate airplane mode based on my location as determined by the wifi SSID to which my phone is connected. I ALSO would like to be able to use Android Pay. Unfortunately, Android Pay doesn't work unless I remove SU from the /su/xbin_bind folder, and if I do that, then Secure Settings doesn't work.
I attempted to use tasker to automate the renaming of the SU file when the Android Pay app is started and then rename the file back to SU after Android Pay closes, but the results only work sometimes... it's flaky at best and I don't know why. Sometimes Android Pay works, sometimes not, other times Secure Settings Works, and sometimes not.
Does anyone have any suggestions for me? Is there going to be an update to Secure Settings so it will work with systemless root without having the create the symlinks? Is there a way to use Tasker to turn off the cell radios only without the need for the Secure Settings app? (I'm a relative novice with Tasker)
Thanks,
Adam
Oops! Posted in wrong section. Mods, please move.
mntnbkr said:
Does anyone have any suggestions for me? Is there going to be an update to Secure Settings so it will work with systemless root without having the create the symlinks? Is there a way to use Tasker to turn off the cell radios only without the need for the Secure Settings app? (I'm a relative novice with Tasker)
Thanks,
Adam
Click to expand...
Click to collapse
Don't bet on a Secure Settings update. It seems a dead project.
You can do it without secure settings, as you're rooted (as per this post)
In tasker, instead, set your task to perform Code -> Run shell -> Command: "settings put global airplane_mode_on 1; ; am broadcast -a android.intent.action.AIRPLANE_MODE --ez state true" -> Check Use Root checkbox, for going into airplane, change 1 to 0 and true to false to disable and return to normal operation.
rgawenda said:
Don't bet on a Secure Settings update. It seems a dead project.
You can do it without secure settings, as you're rooted (as per this post)
In tasker, instead, set your task to perform Code -> Run shell -> Command: "settings put global airplane_mode_on 1; ; am broadcast -a android.intent.action.AIRPLANE_MODE --ez state true" -> Check Use Root checkbox, for going into airplane, change 1 to 0 and true to false to disable and return to normal operation.
Click to expand...
Click to collapse
Thanks for the reply and info! I'm not terribly proficient with Tasker, but I'm going to give your suggestion a shot. If it works, that would be great!:good:
Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Code:
adb shell content insert --uri content://settings/system --bind name:s:tether_dun_required --bind value:i:0
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.
lafinjack said:
Hi there, before now some people were having issues with the hotspot workarounds, where they could enable the hotspot but attached devices received no actual internet. I didn't do any polling but it seemed to be mostly a Sprint phenomenon, as after doing the magic hotspot trick most other people had no issues.
I just tested it, and the new root will get you functioning hotspot on Sprint, and possibly for other people too who were having the same problem. I ran the following code while the hotspot happened to be off, and after turning it back on I was able to get internet through it on other devices. If you try this with the hotspot already enabled please report back so we know if it needs to be either particular setting. Use a normal command line where you have adb.exe and run this command while the phone is on and no further action should be needed once you turn on the hotspot.
Just having root itself has not enabled the normal hotspot switch locations, like in the notification drawer or in the tethering settings, and I still had to use the network refresh trick to get them to work. This may need another command to insert/change the correct protection setting, or something else entirely.
I also went back to the APN settings through the shortcut maker and received the same error I had before, about this user not being able to access them.
On a related note, I saw some people mention that their hotspot would automagically turn off after 10-20 minutes, so I'll post this now and keep an eye on whether it does so here, as I never watched before.
Click to expand...
Click to collapse
This didn't work for me. Any other ideas. Says hotspot service not provided? I can't even switch it on?
An easier command to type that does the same thing is:
Code:
adb shell settings put global tether_dun_required 0
I have Eonon GA7151W headunit - Android 6.0
Suddenly my wifi says "Connected" but 'No Internet' .... it doesn't matter whether I tether to my phone or use my home wifi, for some reason the wifi says 'No internet'.
I tried a few things and ended up resorting to a factory reset ... unfortunately it's still not working after the factory reset! Exactly the same symptoms ...
Any ideas?
hogiela said:
I have Eonon GA7151W headunit - Android 6.0
Suddenly my wifi says "Connected" but 'No Internet' .... it doesn't matter whether I tether to my phone or use my home wifi, for some reason the wifi says 'No internet'.
I tried a few things and ended up resorting to a factory reset ... unfortunately it's still not working after the factory reset! Exactly the same symptoms ...
Any ideas?
Click to expand...
Click to collapse
I have the same issue that has me stumped. any luck fixing it?
Did anyone find a solution for this? Same thing is happening to me. I don't use the internet much on my head unit but I need it. It seems this is a widespread issue.
I'm having the same problem with my radio and after Google'ing I found that you need to run this command to fix it. I don't have root on my radio yet, which is why I'm not sure if this will work.
Code:
su
settings put global captive_portal_server google.com
"Each time your Android device connects to a Wi-Fi network, the system performs a Captive Portal Check. Android aims to ensure that your device has not only received an IP address from the access point, but can actually reach targets on the Internet. This is necessary, for example, for the detection of portal pages of WLAN hotspots (e.g. in hotels). Android sends a request to the address "connectivitycheck.gstatic.com" for verification. If the request is successful or is answered with HTTP Response Code 204, the Internet is accessible. With this request, the system transmits information about the IP address of the connection, the time of Internet access and which browser is currently used to Google.If you block this request to Google via AFWall+ or anywhere else in your network, a small cross will appear on the Wi-Fi icon in the Android menu bar. Depending on the Android version, a message will also appear that no Internet is available. However, privacy-conscious users in particular do not want to send a "ping" to Google every time they go online. There is now a solution that works on rooted and non-rooted devices."
Here's a method that may work without root. Only problem is it seems to be for German devices. Also my device is Android 6.
Android Nougat (7.x)
Connects the device to your computer via USB cable and activates ADB for the process. You then place the following commands via a terminal on the computer:
adb shell 'settings put global captive_portal_http_url "http://captiveportal.kuketz.de"'
adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de"'
Android Oreo (8.x) | Pie (9.x)
Connects the device to your computer via USB cable and activates ADB for the process. You then place the following commands via a terminal on the computer:
adb shell 'settings put global captive_portal_http_url "http://captiveportal.kuketz.de"'
adb shell 'settings put global captive_portal_https_url "https://captiveportal.kuketz.de"'
adb shell 'settings put global captive_portal_fallback_url "http://captiveportal.kuketz.de"'
adb shell 'settings put global captive_portal_other_fallback_urls "http://captiveportal.kuketz.de"'
You can check whether the URLs have been adjusted as desired with the following command:
adb shell 'settings get global captive_portal_https_url'
I think I've broken it down to one command that needs to be run at terminal or adb.
Code:
settings put global captive_portal_detection_enabled 0
Again, I don't have root yet on my device and spent the whole day trying to root it, but you guys can try it out for yourselves. You can use this command to see if you disabled it.
Code:
settings get global captive_portal_detection_enabled
Don't know if all of you solved this issue or swapped unit... But the same happened to me this week after a crash that made me reboot the unit.
Since then, no internet at all, besides the wifi was running like supposed to.
Also tried the factory default, a pain for nothing.
This is how I fixed the issue:
Go to date time of the unit on settings, change it to manual, get it right and adjust the time fuse to the correct one for you, then, switch off then on the wifi and should be running like a charm.
I'm my case, the internet came back in most of apps, but in google store don't, needed to reboot the unit. (I have the by eonon and the code to my radio it's 126, so I can reboot it going to eonon settings)
Rpscavaleiro said:
Don't know if all of you solved this issue or swapped unit... But the same happened to me this week after a crash that made me reboot the unit.
Since then, no internet at all, besides the wifi was running like supposed to.
Also tried the factory default, a pain for nothing.
This is how I fixed the issue:
Go to date time of the unit on settings, change it to manual, get it right and adjust the time fuse to the correct one for you, then, switch off then on the wifi and should be running like a charm.
I'm my case, the internet came back in most of apps, but in google store don't, needed to reboot the unit. (I have the by eonon and the code to my radio it's 126, so I can reboot it going to eonon settings)
Click to expand...
Click to collapse
I'm gonna try this. Would be silly that messing with the clock fixes it. I haven't been able to do anything about it since I need to root the stereo to run those commands.
I truly rocomemd you to do it!
I won't lie that first I get it running, I came to this post and when I saw you guys answer, I was already thinking in take the stereo off, but my mazda 6 it's a pain to get it off, because I have to unscrew the dash.
After some dig, found that solution for issues with access with hotspots.
I also didn't believe that the proceed would work but... the important thing is that my Eonon came back to internet life!
Let me know if also worked with you.