Related
Hello all
I just rooted my NC last night and I'm having two issues.
First, my NC reboots when I dont use it for a few minutes. It seems like any time I let it idle for more than 1-2 minutes it reboots itself. So far I've seen this happen in the wireless screen multiple times, but I'll be testing it on other screens today as well.
Second, I cant seem to stay connected to my home wifi network. When I rooted it last night it wouldnt connect at first, but I just toggled wifi on/off and it connected. Now I cant seem to access the internet at all. I can see and connect to my network, but the status hangs at "Connected, but no internet." I use a N router on WPA/WPA2 PSK.
I did run into a few weird things when rooting the device, which may or may not be related. The instructions on nookdevs say once you have the SD card in the device and it's then connected to your PC it should boot from the SD card with the screen off, then reboot on its own into the new boot animation. Mine never did this, (left it for about 20 minutes and the screen remained black) so I unplugged it and booted it up myself. It booted with the new animation and loaded into android and I was able to get the marketplace working. At this point the network started doing some really strange things, (dropping connection mid-stream on youtube, failing to load new tabs in market) so I did the 8 failed reboots reset and wiped the device to factory settings. From here I re-rooted it using the same steps with the same outcome. The device did not auto-boot but the root seems to have taken OK, but I have no network access just like before.
I was able to get it working for long enough to open up the market and download angry birds and a few other apps late last night, but I've been trying reboots and toggling wi-fi all day today and it still cannot connect.
Also, I am very new to Android and I can't seem to add shortcuts to applications to my home screen. How do I edit this?
I've been having issues with restarts as well. I think it has something to do with Soft Keys.
I am brand new to Android starting last night, but have been a Pre Homebrewer since July
I do use soft keys. I am unsure if that is causing the problem or not
I am going to go test the wifi issues on some public wifi hotspots today. Will report once I do
swapdotavi said:
Hello all
I just rooted my NC last night and I'm having two issues.
First, my NC reboots when I dont use it for a few minutes. It seems like any time I let it idle for more than 1-2 minutes it reboots itself. So far I've seen this happen in the wireless screen multiple times, but I'll be testing it on other screens today as well.
Second, I cant seem to stay connected to my home wifi network. When I rooted it last night it wouldnt connect at first, but I just toggled wifi on/off and it connected. Now I cant seem to access the internet at all. I can see and connect to my network, but the status hangs at "Connected, but no internet." I use a N router on WPA/WPA2 PSK.
I did run into a few weird things when rooting the device, which may or may not be related. The instructions on nookdevs say once you have the SD card in the device and it's then connected to your PC it should boot from the SD card with the screen off, then reboot on its own into the new boot animation. Mine never did this, (left it for about 20 minutes and the screen remained black) so I unplugged it and booted it up myself. It booted with the new animation and loaded into android and I was able to get the marketplace working. At this point the network started doing some really strange things, (dropping connection mid-stream on youtube, failing to load new tabs in market) so I did the 8 failed reboots reset and wiped the device to factory settings. From here I re-rooted it using the same steps with the same outcome. The device did not auto-boot but the root seems to have taken OK, but I have no network access just like before.
I was able to get it working for long enough to open up the market and download angry birds and a few other apps late last night, but I've been trying reboots and toggling wi-fi all day today and it still cannot connect.
Click to expand...
Click to collapse
Reboots: http://forum.xda-developers.com/showthread.php?t=880785
No problems using or reconnecting to wifi here. No other problems.
And I doubt this reboot problem is related to softkeys, but I'm not going to uninstall it to find out. The problem has been (greatly) reduced by changing the scaling governor from conservative to ondemand, per the thread above.
Ah perfect thank you. I will read that thread fully once I get home.
I just tested the NC's wifi at a Starbucks and had no issues at all. Everything connected on the first try and I had 0 disconnections during 15 min of testing in multiple apps. I have to assume it is specific to my network, but I am not sure what the issue would be. I already have a 360 and a laptop using that network with no problems, and even my iPhone can use it when I tell it to.
Has anyone had similar network woes? I use a DIR 615
I found on other topics / forums that people generally has problem with N routers. I've got Linksys WRVS4400n and it randomly hangs when Nook is on (it just drops everything and there's no network connectivity on any devices @ home). When I have turned off N (I left only b/g) everything seems to work normally again. I did not dump traffic that Nook generates, but N-on configuration was a problem..
I hope that will help somehow.
Thanks very much. I've updated to newer firmware and that seems to be helping. If my issue persists I'll disable N and report my findings.
My wife and I gifted each other with nook colors for christmas, so I have 2 to compare side by side.
I'll be returning mine, as it has definite wifi issues. It can connect sometimes, and I was able to get registered after a couple tries and get a couple books downloaded, but more often than not I can't connect at all and the browser rarely works.
My wife's works fine and connects without any problems at all every time.
Both connecting to the same wireless network just an old 802.11G belkin access point that I've been using for a couple years.
Well, I hate to admit it, but my wifi issues were of my own making, and they're now fixed.
I used to keep my wireless network separate and on a different subnet. Once we got playon for the wii, which connects wirelessly I had to move my wireless network to the same subnet as my desktop PC which was running the playon server.
Long story short, at some point in the past for some reason I hard coded my desktop IP address, but left that address in the DHCP scope for that subnet. My nook color happened to get that IP address, so the root cause was an IP conflict.
I deleted the lease and removed that address from the scope and then reconnected the nook to the wireless network, and now it works great.
Neither the nook nor my desktop reported the IP address conflict.
khaytsus said:
Reboots:
And I doubt this reboot problem is related to softkeys, but I'm not going to uninstall it to find out. The problem has been (greatly) reduced by changing the scaling governor from conservative to ondemand, per the thread above.
Click to expand...
Click to collapse
Can you explain what scaling governor is and how to change it? My NC reboots every so often and I'd like to give this a whirl.
eyecrispy said:
Can you explain what scaling governor is and how to change it? My NC reboots every so often and I'd like to give this a whirl.
Click to expand...
Click to collapse
The frequency scaling governor is the cpu control setting that configures a cpu with built in throttling capability to one of the power options available. In linux this is usually configured as a kernel option and can be set to ondemand, conservative, userspace, powersave or performance. In Win systems it is a configurable item in the power profile settings. Ondemand will keep the cpu throttled at the lowend until the system begins working and then it will speed up to the higher end. Userspace is usually required for apps that control the cpu like some taskbar widgets you would find in Gnome or another desktop environment. Powersave would be always run slow to conserve power. Performance would throttle the cpu at its highest level. Etc.
I'm experiencing both of these issues on my 1.0.1 nook. I downloaded spare parts and set the wifi sleep policy to never and nothing happened, I just changed my router from mixed to B-G mixed, we'll see if that helps. That being said, I also downloaded CPU Tuner and changed everything to on demand and am still experiencing reboots. Hope this info is useful for someone!
Yea, SetCPU set to ondemand has not solved my reboot issue, either. It just rebooted on me again about 10 min ago right after i put the device down. I don't seem to have the wifi dropping issue, though.
CPU Tuner has done nothing but make my wifi stop during sleep. I have all the profiles at leave unchanged or enabled. All file transfers stop during sleep now. The random reboots were a smaller issue before. I think I will undo all the changes I've made.
Just so everyone is up to speed with where I landed on these issues.
Wifi:
It was a problem with my DIR 615. A very knowledgeable poster was kind enough to offer a potential solution, which I never tested as I ended up getting a new router anyway. If you are experiancing issues and dropping N helped, you may want to read that thread and talk to aludal.
Reboots:
Still occurring, but very rarely. I see one every day or two. It was worse before I installed Set CPU and set it to "on demand." For a full list of the settings I am using in Set CPU please see the OP in this thread. It's towards the end of the OP.
Hope this helps.
I also have DIR615 and Slingplayer continually crashes my router's wifi internet connection but it works fine using my phone's wifi hotspot. Thanks for the info.
Only thing to reliably do is shut off wifi when the screen goes off.
This issue will be addressed by B&N with their 1.1 update rumored to release this month. Only 20 days possible left...
I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I booted into the bootloader, then used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery ).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
organophosphate said:
Allowing The WiFi Setup Step To Be Skipped (Dangerous):
...
9. YOUR TABLET WILL FAIL TO BOOT IF YOU SKIP THIS STEP: adb shell chmod 755 /system/build.prop
...
Click to expand...
Click to collapse
Shouldn't this be 644?
Also, in case anyone wants to know, you can bypass activation after connecting to a WiFi network - you do not need to tie the tablet to your Google account.
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
cwoggon said:
Shouldn't this be 644?
Click to expand...
Click to collapse
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
nextelbuddy said:
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
Click to expand...
Click to collapse
Well, in my opinion, less is more
organophosphate said:
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
IIRC, this would have been helpful to a gentleman who was looking to bypass WiFi activation awhile back. I applaud little workarounds such as this... you never know when this information might be useful.
cwoggon said:
Well, in my opinion, less is more
Click to expand...
Click to collapse
True.
I was dissatisfied with the original approach because of the risk of causing boot failure, so I refactored the implementation to avoid the problem altogether. The updated procedure should be cleaner & more efficient.
organophosphate said:
It appears that 644 will work as well. Allowing group/other "write" permissions seems to be the cause of the boot failure. Regardless, suffice it to say that the outcome of a standard "adb push" of the file results in incorrect permissions, at least on my configuration (ie. 666, which is Wrong).
I can't believe that this kind of sentiment seems common on XDA, of all places. Seriously? Your flawed reasoning can trivially be applied to wanting to load a custom ROM (your device isn't getting system updates from Google after that) or choosing not to activate the device with a Google account (you miss out on all the Google features). Repeat after me: this is my device; I don't have to justify anything I may want to do with it.
Besides, preventing setup from proceeding without a WiFi connection certainly is a flaw, as others have amply demonstrated. I'm just irked that it requires so much effort/specialized tools to bypass. And no, "It doesn't matter if you're in Afghanistan/at work with no WiFi/only have access to paid WiFi networks. Just go to a McDonald's: your device is worth less than a flaming sack of canine excrement without WiFi and who doesn't have eleventy billion open WiFi networks around in 2012, herp derp!" is not an acceptable workaround (or even constructive advice).
Click to expand...
Click to collapse
ehh i still have to disagree with you there. this isn't the same as wanting to install a custom ROM.
installing custom ROMS and Kernels have true benefits whch are optimization and customization that stock does not offer aka more choice.
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice. as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
I know that many custom roms and kernels give me the ability to inccrease speed and add more options in the operating system that i am looking for hence i will choose to flash a new rom and kernel.
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Im not trying to be argumenative just to do it, im trying to determin your real actual justificaton for wanting this besieds "
its my device let me do what i want" because at no point did i say nor did anyone else say they wanted to flash new roms and kernels because it was their device and they wanted to do what they want, they did it because those options benefitted them in a way that the stock experience did not.
Just because someone is on XDA does not man they are here ot hack their device to pieces. there are many reasons people come to XDA..
talk and interact with others that have a love for media devices
ask questions about their devices
learn from others on how to modify their devices
completely change their devices
just to name a few.
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
nextelbuddy said:
bypassing wifi on a brand new device just because it's your device an you want that freedom does not have the same benefit and doesnt give oy more choice.
Click to expand...
Click to collapse
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
nextelbuddy said:
as i asked before, what could you do with your tablet if you were allowed to bypass wifi on a brand new device?
Click to expand...
Click to collapse
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
nextelbuddy said:
there is nothing i can or want to do with a tablet that allowed me to bypass the wifi setup.. at least not that I can think of.
Click to expand...
Click to collapse
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
nextelbuddy said:
Just because someone is on XDA does not man they are here ot hack their device to pieces.
Click to expand...
Click to collapse
Then this procedure is obviously not for them. That's perfectly okay.
nextelbuddy said:
it does not mean that all of us want the ability to change devices out of the box just because its ours necessarily.
Click to expand...
Click to collapse
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
organophosphate said:
Ipso facto, yes it does: it gives you the choice to skip the WiFi configuration during the initial setup. Whether this is a useful option for you is a decision you make for yourself, but now you have a choice about it whereas you had none before.
That's not salient to this thread, but I suppose you can read your previous post for some possible uses that you suggested.
Then this procedure is obviously not for you. There's no need for the existence of the procedure to be justified, because no one is forcing you to perform this modification.
Then this procedure is obviously not for them. That's perfectly okay.
Sensing a pattern? This procedure is obviously not for you, but others do want this ability. The existence of this procedure in no way infringes upon your ability to use the device just as Google intended.
I still don't get the reaction from this contingent of the XDA community. Honestly, I expected most people to shrug and realize that this workaround might only be useful in certain esoteric cases. Instead, it seems like a vocal group of users must own stock in WiFi router companies, given their insistence that the only valid use of a Nexus tablet is with WiFi connected (haha).
Click to expand...
Click to collapse
Im only one person. I can appreciate your work into finding a valid work around and am in no way attempting to take that from you and im sure there will be many that will be happy and thankful with your hard work. Dont take what I said as any sense that this is how the community feels please.
keep on with your work!
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
nextelbuddy said:
Reasons for wanting to do this other than just saying "because its mine and I want the choice" ?
the device is useless with out wifi. what purpose does the device serve if you dont connect to a wifi point?
Lets say you follow the above steps you laid out and now you are able to boot into the device with out a wifi AP and google account. what now? ok you can load some movies and sideload some APKs you download off the web.
your device isnt being updated now, and almost seems forgive me for saying this... "bratty" i dont want to have to do this its my choice etc.
Click to expand...
Click to collapse
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
lex1020 said:
I am on a military base with in room wifi. The wifi redirects me to the browser which makes me agree to their terms. Since it is initial setup I can't use the browser and since I can't skip I can't use the tablet until later when I get leave and can go to somewhere with free wifi. There's your reason.
Click to expand...
Click to collapse
That's a good reason!
Absolutely agree that you should be able to skip that step. AND no valid reason needed. Unless Google can show a valid reason for not letting you skip that step. I'm sure most of us have watched the Google, (and Facebook) 'net' close in around us. When I started on Android I thought it was so cool how it was all tied to Google and was cross device. Now I'm like: Google would you just get out of my way, I'll be more than happy to click on 'you' when I need something from you.
The latest insult is that annoying "Keep Shopping" prompt in the Play store. Clicking Back, and Keep Shopping does the exact same thing. I shouldn't have to do either. Since I used to be dropped back to the same place anyway.
While the initialization does require a Wi-Fi connection it does not require an Internet connection. I was able to connect to my printer Wi-Fi network and let the waiting bar run for 2-3 minutes then the initialization would continue to completion.
I didn't like this Google forced initial setup either but at least no information was broadcast this way. The Nexus 7 is very useful even when not connected to the Internet.
Chicken and egg
organophosphate said:
I just got my Nexus 7 this evening and was incensed to find out that I could not skip the WiFi network selection phase of setup. This really irked me because I chose this device specifically because it was open/hackable/etc. Instead, I found that immediately after I picked up the device I was being forced to do something I didn't want to do right then. Naturally, this forcing mechanism was supposedly "for my own good".
I searched around and found others asking the same questions only to receive mockery. Therefore, I wanted to post instructions for those who may really want to skip WiFi setup for whatever reason. It's your device; don't feel like you have to justify what you want to do with it or how.
It will become apparent that this was done out of the principle of the matter. This isn't for people who want to get their device up and running quickly or who aren't familiar with adb, custom recoveries, shell commands, etc. Casual users (or anyone who isn't familiar with what each step does without asking questions) should probably avail themselves of the workarounds posted in some of the other threads on this subject.
Preliminary Tasks:
1. Download the ADB drivers for the Nexus 7 from the ASUS support site & install them.
2. Unlock the bootloader using your favorite method (I used "fastboot oem unlock") and let it nuke your tablet.
3. Obtain & load ClockworkMod Recovery using your favorite method (I used "fastboot flash recovery </path/to/clockworkmod.img>).
4. Reboot into recovery.
5. Mount /system via CWM.
If you're in the intended audience you probably can tell where this is going. You have two choices at this juncture: you can edit the build.prop file to allow you to skip WiFi setup step or you can edit the same file to just disable the setup wizard entirely. Both ways work. So, here's the Choose Your Own Adventure stage...
Disabling The Setup Wizard Entirely:
6. Launch adb shell
7. echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
8. Exit shell and issue an adb reboot.
9. Watch your tablet launch directly to the home screen.
10. Manually configure your settings without the "help" of the Setup Wizard and go on your merry way.
11. There is no step 11. Stop reading now.
Allowing The WiFi Setup Step To Be Skipped:
6. adb shell sed -i 's/ro.setupwizard.wifi_required=true/ro.setupwizard.wifi_required=false/g' /system/build.prop
(Thanks to steevp for this idea)7. Issue an adb reboot.
8. Your tablet will launch into the initial setup wizard, but the WiFi page will have a "Skip" button.
9. The developers really didn't anticipate this scenario, so after you skip WiFi selection it will display "Connecting to WiFi" even though there's no connection. This will take a minute or two before it times out and setup continues to the next step.
10. Proceed with the rest of setup however you like.
Naturally, two minutes after I finished getting the tablet booted to the home screen I enabled WiFi and connected to my home network. However, I did this when *I* wanted to do so rather than when Google's devs thought I should; therefore, I am of the opinion that this exercise was worth the effort.
(If your tablet fails to boot after either one of these build.prop file edit approaches, just hold down power + volume down until it reboots. Go into recovery/adb/etc and start debugging what went wrong. This is a particularly fun condition, because you can't adb logcat the issue because you haven't enabled USB debugging because you've haven't setup the device yet. Don't take this the wrong way, but don't bother asking me for help if you can't figure out how to extricate yourself. I mean, how much more dissuasion/warnings/disclaimers do you want?)
ETA:
Disabling the SetupWizard by simply renaming the apk has deleterious side effects, so I refactored the approach. Among other problems, the home button doesn't work if you just rename the apk--likely because it is disabled to prevent users from escaping the setup wizard/WiFi selection screen. Disabling the setup wizard via build.prop doesn't exhibit this issue. Addditionally, I updated the WiFi skipping instructions to be safer and more efficient.
Click to expand...
Click to collapse
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
violincello said:
There seems a "chicken and egg" problem with the above instructions? To unlock the boot loader, you seem to need "USB debugging mode" enabled (for example, see how-unlock-nexus-7-bootloader at androidcentral), but since you can't reach the Nexus 7 options menu without getting through the wifi setup, you can't do that? What am I missing?
Click to expand...
Click to collapse
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That's exactly what I did. I was sitting in a parking lot after purchasing my N7 and didn't have a hotspot nearby. I wanted to play with my tab for a few before heading home so I just fired up WiFi Tether on my Rezound.
Sent from my Nexus 7 using xda app-developers app
chiggy2212 said:
We can just create a hotspot with our phone..this method is more easier than the method mentioned.and it doesn't require an active internet connection..just WiFi connectivity .
Click to expand...
Click to collapse
Absolutely. As I mentioned in the OP, this isn't the fastest solution. Hell, you can probably tell I don't even recommend it for common scenarios.
That said, the approach *does* work. Before I started this I searched and was unable find any other way to accomplish the specific goal of skipping/disabling WiFi connection during initial setup. Therefore, when I was finally able to get it working I wanted to document it for the community.
dr.m0x said:
You can boot into the bootloader by holding volume down + power while the tablet is off. Then fastboot oem unlock. Job done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I tweaked the OP to indicate this more clearly.
Simply
Andie00 said:
Thanks for the effort. I just got my N7 and was also surprised I couldn't skip the wifi setup.
Click to expand...
Click to collapse
When it happened to me, i just restarted it. It then booted to the homescreen.
My WiFi has issues opening new connections, like checking my email can take anything from a normal 1 second to just sit there and spin for 30 seconds.
This gets worse if I ask the email client to check all three accounts at the same time.
Opening say facebook through a bookmark on the start screen, can either load instantly, or just show a white screen until I force close Chrome and retry.
I never get an actual timeout error, but it'll keep loading some items between 10 seconds, to just never connecting.
When I do a speed check, there's no issue, I get the same 12 Mbps as the wired computer, assuming it'll actually start downloading.
On the play store there's broken downloads though, it'll download at max speed instantly, but then hang in the middle until I force stop the play store (or reboot).
If I let it sit long enough, it might resume but often with corrupt downloads as a result.
I've had this problem for a while now, and I've tried connecting to various other networks with completely different configurations and it's pretty much consistent.
Disabling WiFi and using the LTE network instead, it doesn't display this behaviour at all, so it has to be something with the WiFi.
Has anyone else had this? I can't find anything useful through the search or google, they all suggest I do this and that on my router, but the other devices work fine.
Tested with the HTC M7, an old Motorola Razr, even the now ancient Moto XT720 has no issues.
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
eyeoncomputers said:
If you are in the stock Lollipop 5.0, then you should check your logcat (or use CatLog app in PlayStore if you are rooted).
There are many many WifiStateMachine errors that are logged each second.... I made a thread about it:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-pure-edition-stock-5-0-major-t3002124
I reverted back to 4.4.4 and had no more of those errors.
Click to expand...
Click to collapse
I checked your thread, and I had a bug like that on 4.4.4 actually.
Where it would work fine, go to sleep then not wake up again.
For me, it was a game from humble bundle that triggered this, "The Deer God"
There was another game on play that did the same, but I can't remember the name of that one.
After I emailed the devs of Deer God, they oddly found the bug immediately and their new version didn't have this problem.
I didn't even send them a log file or anything.. Which was weird.
So far this never happened after upgrading to Lollipop though.
My WiFi problems disappeared at work, but remained at home.
Thinking it was the router, I borrowed a WiFi repeater but the problem still occurred.
Even when I used the repeater as a hotspot with cable.
I was about to give up, and just use my 4G all the time..
But I installed DD-WRT, and lo and behold, WiFi works flawlessly?!
It's not like I'm using a cheap rubbish router, it's the Netgear Nighthawk for crying out loud..
You'd think the software for it would be well coded considering how long they've been doing these devices...
Hello everybody,
I have a wifi connection drop issue with my Amazon Fire tablet - running CM12.1 (Unofficial Ford) - Build 30th May 2016 - however, the issue persists since I first replaced the FireOS with CM12.1 (a December 2015 build) using SuperTool.
As long as the fire does not fall into sleep mode, everything's fine with the wifi connection. However, I'd like to use the tablet as a Streaming device for Services like Spotify or Amazon Prime Music via BlueTooth to my HiFi-System. After a certain time (time duration varies), the wifi connection drops in the power savings mode and therefore, the music stops playing of course. If I unlock the screen at this point, the wifi connection re-establishes and the music resumes playing. I already checked, if the energy savings options are configured in that way, that the wifi connection is up all time.
I've done a lot of investigation (with my limited knowledge about the system), however I was not able to find the root cause of this issue
Not sure, if this is important, but I have a AVM Fritzbox 7490 as Wifi Access Point.
A few days ago, I did a clean install of CM12.1 (Build 30th May) using FlashFire and even after the clean install, the issue re-appers. :crying:
I would really appreciate, if someone can point me in the right direction, how to fix this issue or even where to look at.
If this is a known issue, please bear with me, however the search function in this forum presents an error message, if I search in the CM12.1 Main thread for the Fire tablet, saying:
"Sorry, we encountered an error processing your request. Please go back and retry or wait a minute.
The Administrators have been notified of this error"
Thanks and Cheers from Germany
Puempel
I've been trying to figure out what is causing this strange behavior on my phone but i guess i'm not alone.
The issues:
delayed notification on WiFi/mobile net (i know there is a thread to that, and i know this has been poising every android release for certain phones)
Tidal (Soundcloud, and probably any other music streaming app) connection drop after around 3-4 mins of locking the phone ( seems like mobile data/wifi is disconnecting after a certain minutes when phone locks, causing Tidal to show connection error message and stops streaming music)
Messenger call issue: calling on mobile data/WiFi, if the phone locks, same behavior happens but instantly ( as soon as phone locks, messenger call disconnects, but as soon as i unlock it connects again)
All of these apps have unrestricted battery usage, allowed background data. I think this is a systematic issue around connection dropping when the phone locks. Maybe this is also the cause for notification delay. I'm new to the S21 ultra but not to android, never experienced these issues with any other android phones (not even with my S8) Anyway, if someone has an idea on this i would appreciate it.
Edit: I'm on unrooted, fully stock os (G998BXXU4CVC4), OneUI 4.1, march security patch
What OS version?
blackhawk said:
What OS version?
Click to expand...
Click to collapse
Latest Oneui 4.1 with march sec patch. G998BXXU4CVC4
redhunter22 said:
Latest Oneui 4.1 with march sec patch. G998BXXU4CVC4
Click to expand...
Click to collapse
You can try:
Clearing the system cache.
Factory reset, if so do not use SmartSwitch
Or a full nuke rollback to 11.
blackhawk said:
You can try:
Clearing the system cache.
Factory reset, if so do not use SmartSwitch
Or a full nuke rollback to 11.
Click to expand...
Click to collapse
There is no way to go back to 11 because bootloader is newer that it was on 11.
Maybe the fact that I'm always connected to VPN (Mullvad VPN) has something to do with it? (Mullvad app also unrestricted)
redhunter22 said:
Maybe the fact that I'm always connected to VPN (Mullvad VPN) has something to do with it? (Mullvad app also unrestricted)
Click to expand...
Click to collapse
Highly likely. Try going without it for a while.
Update for those of you with the same kind of issues: I'm now pretty sure the cause is the VPN. Mullvad is using wireguard, I reached out to them and they recommended to change the MTU 1300 from the default. So far so good with this value, notifications arrive instantly and no connection drops.