Develop Bugs

WIFI Router does NOT work with full root

Hey everyone. between my brothers and I, we have five Evo's. two of us are running full roots and nand unlocks, the other three are using unrevoked. those that unrevoked can use the wifi router without issue, but for my brother and myself, using the wifi router results in the app crashing and having to force close.
has anyone seen anything similar? can anyone offer me some solution?
and btw, this is my third rom. they all have the same results(full wipe, data and davik cache clear each time)

Delete wi fi tether from the phone and re-download it. This has worked for me everytime i change roms =)
Hope it helps.

Do you mean the wireless tether app? I am running my own rom but it seems that it worked for me when I was using fresh. But that is the only other rom I have tried. Have you tried re-installing the tether app?

I'm not sure i can remove the base wifi tether app. it's always cooked into the rom. and i have tried reinstalling the app. i've gone from the original version, to the newer version and finally the beta version with no luck

I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now

Hmmmmmm. I am sure someone else can offer better advice, but does the super user app come up to ask for permission or it fc's before that?

topdawgn8 said:
I was having this issue for awhile. I'm not sure exactly what fixed it, but my work around was:
1. Re-install from the market place (Do not launch)
2. Reboot
3. Install this version http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q=NexusOne
(Don't lanch)
4. Reboot
5. Should work now
Click to expand...
Click to collapse
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests

I am not sure if your signature is correct but have you tried flashing the newest radio? I am not sure if that would fix it or not. And the same thing happens to the other phone? Puzzling indeed. I'm sure someone will drop in and tell you how to fix it soon. Worst case, start over. Even though I know you said you tried various roms, maybe you are accidentally skipping a step, I do that sometimes

SilverStone641 said:
okay, i did exactly as you said. now the app will start, but as soon as i click on the wifi symbol, it thinks for a second and says "Unable to start tethering. Please try again!"
Edit: and on first run, it asked me for super user permissions. i click grant and checked the box to allow future requests
Click to expand...
Click to collapse
Ok, go back through the same process and try this one instead of what was in step 3.
http://code.google.com/p/android-wi...me=wireless_tether_2_0_2.apk&can=2&q=NexusOne
If that doesn't work, I've got nothing else. The first one was the beta you probably tried earlier. This is the stable one; however, I never tried it with this one. I always got it working using the 2_0_5 version.

Also, for ****s and giggles, have you tried updating you profile and prl?
- you didn't flash the wireless n patch over a 1.47 base Rom correct? Can you connect to a WiFi router or is it just the tether app?

elegantai said:
Also, for ****s and giggles, have you tried updating you profile and prl?
Click to expand...
Click to collapse
uh....what?? you got me there! i thought i knew what those were, but it escapes me now.
the only thing i can think of is that the rooting process screwed up somehow. but for it to screw up in the same way for two separate phones is odd, but it's the only thing that has remained constant since the very beginning.

Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this

elegantai said:
Menu - settings - system updates. The profile and prl won't mess with root or anything but its something I have heard to do in this case. Don't know if it will help.
Also did you see the note about the wifi n patch on the other page? I added it after I posted... like this
Click to expand...
Click to collapse
done. same results. "Unable to start tethering. Please try again!"

Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.

elegantai said:
Well crapola. I think I'm outta ideas man. if you didn't patch the wireless n over a 1.47 Rom then I have no clue what it could be. maybe Sprint is spying on you and has your phones on lock down! but if you can't find the answer just try starting fresh. it might be a pain but who knows what little quirk could have gotten messed up.
Click to expand...
Click to collapse
i do have the wireless N enabled, but i do not have the new 1.47 yet. i'm waiting on OMJ to release an update

Wifi Error

I have the EVO 4g and I was able to put it into S-off....Once i did that i was getting wifi error when i tried to use the wifi. I'm stumped and have looked everywhere and have not gotten any clear answers. I have tried to install a rom (using digital karma now) but to no avail. Please help me out :laugh:

Try upgrading radios

death-by-soap said:
Try upgrading radios
Click to expand...
Click to collapse
that did not work =\

Could try reflashing the kernel and wiping cache and dalvik cache in recovery.
You tried switching your router off and on again?

note that some kernels need to have data and/or system mounted first in recovery before flashing the kernel otherwise wifi breaks. Just a thought.
also, you did sanity check your network by conforming that other devices still connect fine?
Sent from my PC36100 using xda app-developers app

Robobob1221 said:
Could try reflashing the kernel and wiping cache and dalvik cache in recovery.
You tried switching your router off and on again?
Click to expand...
Click to collapse
well i didn't do the router because its not even scanning for a router at all. This is a fairly new phone so it was never dropped (just some info).

NxNW said:
note that some kernels need to have data and/or system mounted first in recovery before flashing the kernel otherwise wifi breaks. Just a thought.
also, you did sanity check your network by conforming that other devices still connect fine?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
yeah the network is fine. I have another EVO that i use for wifi purposes, but the usb port broken. I have been charging my battery on one phone and using wifi on the other. It was fine while it lasted but now its a bit old. I want to flash one of these phones to pageplus and i prefer the one that the wifi works on.

Ok...let me search my memory banks to see if I can help. I have had this problem about 2 or 3 times, and I searched DILIGENTLY for an answer. After countless, and I mean countless pages, I found a solution. (Not saying you didn't search right...but it took me a while, and I had to change the words of my search about 20 times.)
You need a file explorer with root access. There are many good ones, and I use ES File Explorer. Not saying it's the best, not saying it's the worst, not saying anything except that it's the one I use. Period.
Anyway, you must access the root of your phone, and go to these folders.
System-->Etc-->Wifi.
In the Wifi folder, either rename the supplicant file to be safe, or delete it. I renamed mine the first time around to be safe, but I can confirm that deleting doesn't hurt anything. Restart your phone, and it will rebuild the file when the phone reboots. No need to wipe cached or anything. And fixing permissions doesn't work for this.
Try it, and let me know.
P.S.: I would give credit to the person who originally posted this solution, but I don't remember, since the answer was not on XDA, and I found it in a forum for a random Samsung phone.
______________________________
HTC Evo 4g

aarsyl said:
Ok...let me search my memory banks to see if I can help. I have had this problem about 2 or 3 times, and I searched DILIGENTLY for an answer. After countless, and I mean countless pages, I found a solution. (Not saying you didn't search right...but it took me a while, and I had to change the words of my search about 20 times.)
You need a file explorer with root access. There are many good ones, and I use ES File Explorer. Not saying it's the best, not saying it's the worst, not saying anything except that it's the one I use. Period.
Anyway, you must access the root of your phone, and go to these folders.
System-->Etc-->Wifi.
In the Wifi folder, either rename the supplicant file to be safe, or delete it. I renamed mine the first time around to be safe, but I can confirm that deleting doesn't hurt anything. Restart your phone, and it will rebuild the file when the phone reboots. No need to wipe cached or anything. And fixing permissions doesn't work for this.
Try it, and let me know.
P.S.: I would give credit to the person who originally posted this solution, but I don't remember, since the answer was not on XDA, and I found it in a forum for a random Samsung phone.
______________________________
HTC Evo 4g
Click to expand...
Click to collapse
nope did not work...I eeven tried taken wifi files out of my working evo to this one and still did not work

Do a Full Wipe of everything. Then Flash a Stock Rooted Rom. See if that corrects the issue. You may also want to check out THIS thread. Also the one HERE.

Hmmmm...I tried my best. I hope you find a solution soon.
But the way, does it simply say error, or does it behave strange, like turn off and on for a while, then give you the error message?
______________________________
HTC Evo 4g

aarsyl said:
Hmmmm...I tried my best. I hope you find a solution soon.
But the way, does it simply say error, or does it behave strange, like turn off and on for a while, then give you the error message?
______________________________
HTC Evo 4g
Click to expand...
Click to collapse
it say error

Since nothing else has seemed to work you could try this..http://forum.xda-developers.com/showthread.php?t=1982149 ..you have to be running an ics or jb rom for the app to work though. Just throwing it out there.

[Q] after cyanogen install - root may be lost, fix?

On my galaxy s3 1747 i get the above message. When i select yes the phone reboots to stock firmware.
Is there a way to fix this?

skiiermike said:
On my galaxy s3 1747 i get the above message. When i select yes the phone reboots to stock firmware.
Is there a way to fix this?
Click to expand...
Click to collapse
Do you have KNOX on the phone? That might be causing it

mole62 said:
Do you have KNOX on the phone? That might be causing it
Click to expand...
Click to collapse
I do and thanks for the response.
Since trying the install a few times I have now lost root access. Now when I try to transfer files to my phone through USB so I can root it again it always times out.
Other than the above the phone is working.
What should I do?

I just tried a different usb cable and it worked. Phone is now rooted. I'll uninstall knox and try it again.

skiiermike said:
I do and thanks for the response.
Since trying the install a few times I have now lost root access. Now when I try to transfer files to my phone through USB so I can root it again it always times out.
Other than the above the phone is working.
What should I do?
Click to expand...
Click to collapse
When I rooted my S3 i9300 I had similar problems with timing out, I tried one desktop PC and a laptop, with no luck. I finally dug out an old netbook which worked - so I guess it would be worth trying a different PC if you can?
This is a link to disabling KNOX - my phone doesn't have it so I've not tried it myself http://www.androidpit.com/how-to-uninstall-knox
Hope that helps!
edit: Or a different cable lol

mole62 said:
When I rooted my S3 i9300 I had similar problems with timing out, I tried one desktop PC and a laptop, with no luck. I finally dug out an old netbook which worked - so I guess it would be worth trying a different PC if you can?
This is a link to disabling KNOX - my phone doesn't have it so I've not tried it myself http://www.androidpit.com/how-to-uninstall-knox
Hope that helps!
edit: Or a different cable lol
Click to expand...
Click to collapse
I have completely removed knox.
I am still getting the root may be possibly lost message. I select yes to fix root and I still get my original firmware.
There has to be someone who knows how to fix this?

skiiermike said:
I have completely removed knox.
I am still getting the root may be possibly lost message. I select yes to fix root and I still get my original firmware.
There has to be someone who knows how to fix this?
Click to expand...
Click to collapse
Are you talking about in the recovery? if yes ignore it and choose no or get a better recovery like philz where it doesn't pester you about it.
Also this is in the wrong phone forum, this is the international version. Ill get a mod to shift it for you.
also its the i747 not 1747.

If You Used The TMobile Root Method...

2 things... Would anyone mind verifying that once you use the tmobile root, you can no longer boot into recovery?
I tried to factory reset and the recovery will not boot.. Just flashes the android icon every few seconds.
The only way to boot back into the phone is to put it into download mode and re run the tmobile root. It will restart and all will be good.
Now, if it is not just my phone that no longer has a working stock recovery, does anyone know a way to factory reset without a working recovery? I'm guessing it's not possible. Kies does not work with the Sprint Note 4 yet. They updated it today and you can backup the n4 but not factory reset.
Finally, can anyone that used the Galaxy Tools app to get WiFi tethering to work, check to see if your private mode will turn on? I do not have xposed installed and the wifi tether fix in the galaxy tools app seems to be the only thing I can think of that would have broke Private Mode.
Thanks!

Same thing happened to me. I had to get another note 4. There is no way until samsung releases the firmware dump. Sprint even called best buy samsungs care center to see if they have the reflash files and they don't even have it. Odin wipe the data and bring it into sprint so they can give you another one.

Mine boots just fine to the recovery and tecovery works just fine.
I know when i first downloaded thw CF auto for n910t and used the oding in that package my process failed and phone showed to monitors on screen
So i took battery off and download mode again and used a different odin i allready had same version and did the process again and worked and everything is fine.

Androidwarrior said:
Same thing happened to me. I had to get another note 4. There is no way until samsung releases the firmware dump. Sprint even called best buy samsungs care center to see if they have the reflash files and they don't even have it. Odin wipe the data and bring it into sprint so they can give you another one.
Click to expand...
Click to collapse
It is not that big a deal. I can wait for a custom recovery and then go from there. I wanted to factory reset so that I could get private mode back, but I will just use it as is until there is another alternative.
Others are saying that their recoveries are working fine. I guess you and I are the lucky ones
Thanks Androidwarrior.

CJPRICO said:
Mine boots just fine to the recovery and tecovery works just fine.
I know when i first downloaded thw CF auto for n910t and used the oding in that package my process failed and phone showed to monitors on screen
So i took battery off and download mode again and used a different odin i allready had same version and did the process again and worked and everything is fine.
Click to expand...
Click to collapse
What version of Odin did you use? Thanks

I just auto-rooted with N910T, and tried to install Wifi Tether (and TrevE variant) and neither worked. I don't think it started the tether correctly, it was unable to open the log for write, so I don't have a log. I am pretty sure the root was successful (at least partially). I used the root checker app and it said I was good and within the terminal emulator I was able to switch users to root.
I also unsuccessfully tried X Tether. It started up, and showed up on my computer, but I wasn't able to connect to it, and after a while it invariably told me that I needed to upgrade my service.

loonytunes said:
What version of Odin did you use? Thanks
Click to expand...
Click to collapse
3.07 but a normal odin (with all options available) not modified (that it wont let you chose anything but pda) like the one it came with the cf auto
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
hpmaxim said:
I just auto-rooted with N910T, and tried to install Wifi Tether (and TrevE variant) and neither worked. I don't think it started the tether correctly, it was unable to open the log for write, so I don't have a log. I am pretty sure the root was successful (at least partially). I used the root checker app and it said I was good and within the terminal emulator I was able to switch users to root.
I also unsuccessfully tried X Tether. It started up, and showed up on my computer, but I wasn't able to connect to it, and after a while it invariably told me that I needed to upgrade my service.
Click to expand...
Click to collapse
Have you tried Galaxytools from playstore it worked just fine on mine for hotspot

Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).

hpmaxim said:
Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).
Click to expand...
Click to collapse
Even before root. They were doing that system update everytime y restart. But u can freeze samsung DM service if it bother you

hpmaxim said:
Just loaded it... It seems like I am getting a "System Updating" every time I reboot now, not sure if it was doing it before that though. After some playing with it, I think it is now working. I hit the "Enable Native Hotspot" and it rebooted and then it worked for a while, I tried it again, and it seems more reliable now. I'm still not convinced its completely reliable. I tried a speedtest on my laptop while tethering and I got about 8Mbps down, but only about 300kbps up. The upload seemed very goofy, like it was sending a lot of data and then pausing, and then sending a lot of data. Interestingly it was on 3G initially and getting about 1.5Mbps and the same thing up (and then when I rebooted it, I got LTE and the higher download speeds).
Click to expand...
Click to collapse
Can you check to see if using galaxy tools to enable tether kills your private mode? Since using the galaxy tools app, whenever I click on private mode it fails saying "Private mode failed to start, try again."

loonytunes said:
Can you check to see if using galaxy tools to enable tether kills your private mode? Since using the galaxy tools app, whenever I click on private mode it fails saying "Private mode failed to start, try again."
Click to expand...
Click to collapse
My private mode is gone but id assume its because of xposed but can't be for sure.

sml2004 said:
My private mode is gone but id assume its because of xposed but can't be for sure.
Click to expand...
Click to collapse
I'm not sure how to use it since this is the first time I've heard of it, but it appears to be there. S Health seems to have been killed somewhere along he way there. No more pedometer, UV sensor, SPO2, or heart rate....

Did some googling and found this. http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
I'm going to try it and see if it works on ours.
Update: Uninstalled Xposed and S Health started working again. Going to back up and try the buildprop edit in a bit.

Shadeoblac said:
Did some googling and found this. http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
I'm going to try it and see if it works on ours.
Update: Uninstalled Xposed and S Health started working again. Going to back up and try the buildprop edit in a bit.
Click to expand...
Click to collapse
In Xposed install "Wanam Xposed", open Wanam, go to Security Hacks, and click "Disable Secure Storage" and S Health will work fine.
Sent from my SM-N910P using Tapatalk

hpmaxim said:
I'm not sure how to use it since this is the first time I've heard of it, but it appears to be there. S Health seems to have been killed somewhere along he way there. No more pedometer, UV sensor, SPO2, or heart rate....
Click to expand...
Click to collapse
pdaddy said:
In Xposed install "Wanam Xposed", open Wanam, go to Security Hacks, and click "Disable Secure Storage" and S Health will work fine.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
That sounds way simpler.
Thanks!......
So I tried that and it didn't work.....hmmmm

Shadeoblac said:
That sounds way simpler.
Thanks!......
So I tried that and it didn't work.....hmmmm
Click to expand...
Click to collapse
Yep, me too... Didn't make a difference.

hpmaxim said:
Yep, me too... Didn't make a difference.
Click to expand...
Click to collapse
Going to try that buildprop edit. I'll report back as soon as I'm done.
Update: The buildprop edit from http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
worked. Xposed and S Health working now.

Shadeoblac said:
Going to try that buildprop edit. I'll report back as soon as I'm done.
Update: The buildprop edit from http://www.andromods.com/fix-troubleshoot/fix-xposed-framework-shealth-problem-galaxy-s5.html
worked. Xposed and S Health working now.
Click to expand...
Click to collapse
I had the same problem with S Health, but there is an xposed module that will fix the issue for you. Just search in the download section of xposed.

hpmaxim said:
Yep, me too... Didn't make a difference.
Click to expand...
Click to collapse
allaidback said:
I had the same problem with S Health, but there is an xposed module that will fix the issue for you. Just search in the download section of xposed.
Click to expand...
Click to collapse
I'll check it out, but it's working fine now. Now if I could only remember how to get the SD back to normal again.

TWRP should be out today so we can root via an actual Sprint method if you guys wanted to wait a little longer. I believe you can even root via CF now.
Sent from my SM-N910P using Tapatalk

[FIRMWARE] [STOCK] Pre-rooted, optimized, stock firmware for HD 10 Suez [APRIL 2019]

Pre-Rooted, Optimized, Stock ROM
This thread contains stock firmware for the Fire HD 10 SUEZ, which has been pre-rooted and optimized. Please see the respective section for your FireOS version. Later FireOS versions ARE supported, but I am going to need a few days. Downgrading from a newer version of FireOS is NOT recommended and can potentially damage your device. This ROM has NOT been 'de-bloated'. By installing this ROM, you do so at your own risk. Results may not always be the same.
****THIS GUIDE REQUIRES AN UNLOCKED DEVICE WITH TWRP.****
Features:
- Zipaligned - All system and framework apks have been zipaligned.
- Deodexed - The whole system has been successfully deodexed. Among many things, this makes uninstalling system apps easier and greatly lowers the risk of a bootloop, though not promised. It also saves a little bit of space in the system when uninstalling system apps.
- No OTA - Never worry about an accidental Over The Air Update. Both APKs have been removed. You can sign into your network the very first boot.
- Pre-rooted. - Magisk, by XDA member and developer @topjohnwu, is stepping up to the plate this time. The ROM is pre-rooted with the latest stable version 18.1. SuperSU cannot be flashed on this tablet. Doing so will result in an endless display of the beautiful orange fire logo. It is possible to manually root the ROM with SuperSU, but I will need to do a lot of testing. If you prefer SuperSU, this ROM is not for you and you will have to root using one of the several guides available in this forum.
- Busybox - Contains the latest busybox by XDA member and developer @osm0sis.
If it were not for the tool, SuperR's Kitchen, this ROM, and hopefully others, wouldn't be possible. I have trouble linking his username here, but if someone can direct superR to this thread so he can see the endless thanks I give to him for creating this amazing tool.
These ROMS do NOT contain any of my tricks or hacks. They're simply pre rooted ROMS in case you need to return back to stock FireOS. No apps have been removed except the above mentioned and none have been added, except the above mentioned.
Downloads:
- For HD 10 SUEZ on 5.6.1.0: 5.6.1.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip
- For HD 10 SUEZ on 5.6.2.0: 5.6.2.0_Fire_HD_10_optimized_pre_rooted_stock_rom-signed.zip
Installation:
1. Download the ROM then plug your tablet into the PC and place the zip on your internal storage.
2. BACKUP ALL VALUABLE DATA. YOU WILL BE ERASING THE SYSTEM AND DATA. Reboot to TWRP (recovery), tap wipe and select dalvik, cache, system and data ONLY and swipe to confirm. When finished tap the home button, reboot then recovery.
3. When back in recovery, tap install and select the ROM then swipe to confirm. When done, reboot and enjoy.

Reservation
Sent from my MotoG3 using XDA Labs

Is there any benefit to flashing this if I'm already rooted? I mean, "optimized" sounds nice, but my data.... lol

Anyone try this yet?
EDIT: Flashed and got a black screen at first, spooped me for a few seconds there, then showed the Amazon and (now currently) Fire logos. And now we wait for it to do its optimization.

To be clear: your instructions don't have any prerequisites of already being rooted or modded in any other way? So a person could do these steps on an unmodified HD 10 2017 Suez that is running 5.6.1.0?

phanguy said:
To be clear: your instructions don't have any prerequisites of already being rooted or modded in any other way? So a person could do these steps on an unmodified HD 10 2017 Suez that is running 5.6.1.0?
Click to expand...
Click to collapse
I would think you would need to have TWRP installed, at least. The instructions do call for that.
Also, it appears to be working without at hitch. I'm inputting my WiFi password as I type this.
EDIT: I kept getting a DHCP error when connecting to my home hotspot, so I'm using my phone's hotspot instead. WiFi icon has an exclamation mark next to it, but internet seems to be working fine.
EDIT 2: Spoke too soon. Don't have internet. No matter what I do. Can't seem to connect properly. Every network I try just keeps saying "Obtaining IP address," never connects. Eventually throws the error, "IP Configuration Failure, IP configuration failed due to DHCP error."
EDIT 3: Phone hotspot is working, for now. Guess I'll stick with that until the router is fixed.

GuyInDogSuit said:
I would think you would need to have TWRP installed, at least. The instructions do call for that.
Also, it appears to be working without at hitch. I'm inputting my WiFi password as I type this.
EDIT: I kept getting a DHCP error when connecting to my home hotspot, so I'm using my phone's hotspot instead. WiFi icon has an exclamation mark next to it, but internet seems to be working fine.
EDIT 2: Spoke too soon. Don't have internet. No matter what I do. Can't seem to connect properly. Every network I try just keeps saying "Obtaining IP address," never connects. Eventually throws the error, "IP Configuration Failure, IP configuration failed due to DHCP error."
EDIT 3: Phone hotspot is working, for now. Guess I'll stick with that until the router is fixed.
Click to expand...
Click to collapse
This is on a 2.4.ghz band that you are trying to connect to I'm assuming?
Edit: @DragonFire1024 thank you so much for your continued and dedicated work with these tablets! Can't wait to see what you can do when you really get down on making a ROM for this beast.

tylerhole said:
This is on a 2.4.ghz band that you are trying to connect to I'm assuming?
Click to expand...
Click to collapse
It most likely is. The router's SUPPOSED to output 5GHz as well, but someone f*cked it up and now it only does 2.4.

GuyInDogSuit said:
It most likely is. The router's SUPPOSED to output 5GHz as well, but someone f*cked it up and now it only does 2.4.
Click to expand...
Click to collapse
Do you know/are you able to find out what the channel width is set at? If it's set at 40 instead of 20 that could be why the phone hot spot works and the router doesn't.

tylerhole said:
Do you know/are you able to find out what the channel width is set at? If it's set at 40 instead of 20 that could be why the phone hot spot works and the router doesn't.
Click to expand...
Click to collapse
Could be. I'll check and try the other setting. It's worked before this ROM, so I dunno if that's the cause...
EDIT: Nope, that wasn't it. Where's the f*cking WPS option on this tablet?! Thanks, Amazon!

GuyInDogSuit said:
Could be. I'll check and try the other setting. It's worked before this ROM, so I dunno if that's the cause...
Click to expand...
Click to collapse
Very well could not be then, was just the first thing that popped into my head.
Sent from my SM-G9650/DS running stang5litre Pie ROM

tylerhole said:
Very well could not be then, was just the first thing that popped into my head.
Click to expand...
Click to collapse
Nothing works so far. I need to fix this damn router or replace it. I'm tired of AT&T and their sh*tty hardware and even sh*ttier service.

I'm having the same WiFi issue. Just gets stuck on obtaining IP address.
Sent from my SM-G9650/DS running stang5litre Pie ROM
---------- Post added at 10:14 PM ---------- Previous post was at 10:07 PM ----------
It appears that the tablet is not liking DHCP. If you configure a static IP address it connects fine and internet works.
Sent from my SM-G9650/DS running stang5litre Pie ROM

GuyInDogSuit said:
It most likely is. The router's SUPPOSED to output 5GHz as well, but someone f*cked it up and now it only does 2.4.
Click to expand...
Click to collapse
I wonder...perhaps installing my framework and settings APK will fix this. Looks like I have a lot of tests tomorrow.
Sent from my MotoG3 using XDA Labs

Wonder why it works (sometimes) with my phone hotspot? I'll try the static IP. That actually had crossed my mind, @tylerhole, but i didn't have time to try it before work.

DragonFire1024 said:
I wonder...perhaps installing my framework and settings APK will fix this. Looks like I have a lot of tests tomorrow.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
In the "optimizing" you did for this ROM did any of it have to do with wifi?
Sent from my SM-G9650/DS running stang5litre Pie ROM

DragonFire1024 said:
I wonder...perhaps installing my framework and settings APK will fix this. Looks like I have a lot of tests tomorrow.
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
if you're referring to what you have in this thread then it didn't work for me. i removed everything but the boot animation, framework stuff, and the settings apk. still getting wifi issue though.

Took a chance and tried this coming from the original 5.1.1 Fire OS (what I thought was 5.1.1, but now im not sure what version I had, read on)
Did the wipe as instructed and everything looked good during the flash but on reboot it looks like the 5.1.1 persisted somehow.
EDIT. getprop ro.build.version.release reports 5.1.1 but the system updates reports 5.6.1.0. I had blocked system updates just to make sure that was disabled but in doing so you cant get the version from the settings. So I'm good, except for the WIFI not working.
Miles

phanguy said:
if you're referring to what you have in this thread then it didn't work for me. i removed everything but the boot animation, framework stuff, and the settings apk. still getting wifi issue though.
Click to expand...
Click to collapse
Ok I do know the kernel source contains the wifi drivers. I'm not at home to look, but I'm willing to bet $150 that the needed wifi firmware is not in the system partition. This is the last hurdle I believe and I think everything to this point are intentional blockades. If one can hunt down the system wifi drivers it shouldn't be an issue to include them in another build.
Sent from my MotoG3 using XDA Labs

beachmiles said:
Took a chance and tried this coming from the original 5.1.1 Fire OS (what I thought was 5.1.1, but now im not sure what version I had, read on)
Did the wipe as instructed and everything looked good during the flash but on reboot it looks like the 5.1.1 persisted somehow.
EDIT. getprop ro.build.version.release reports 5.1.1 but the system updates reports 5.6.1.0. I had blocked system updates just to make sure that was disabled but in doing so you cant get the version from the settings. So I'm good!! Thanks.
Miles
Click to expand...
Click to collapse
5.1.1 is the Android version not FireOS version which is 5.6.1.0.
Sent from my MotoG3 using XDA Labs