Some observations I have made in a few weeks with the minix neo x5 mini and the problems people including myself have had with wifi. I am hoping this may help others, what I have found is trial and error and some conclusions based on guess work as to why my results are what they are. Its long winded but if your having wifi issues, you might want to read it.
I started out with one router, a netgear wnr2500 flashed to dd-wrt sp2. Not much of a router for todays standards but all I had lying around after a recent move. Not to imply the wifi on the mini is flawed,,, though it is not hard to find people having issues, google it. In fact many of the rk 3066 mini tv sticks have similar issues for people no matter the brand. Either I missed the related posts googling repeatedly on the subject or I may have actually stumbled across something.
No matter what channel I used, I would eventually get buffer issues when watching streaming content such as xbmc, netflix and so on. I tried editing the buffer size in xbmc, seemed to help, slightly. Heres what seems now to be a recipe that works for me, all the time, it might buffer for 2 seconds out of 24 hours of viewing.
I will ad to this I bought a tplink wdr4300 to trouble shoot the issues I was having. I will also talk about how I think that router is not good hardware, although cheap with lots features. Bottom line the shiny new tplink actually made things worse as far as my buffer issues went with the mini.
I wanted two routers in the house on the same network, I have terrible coverage issues. to much metal in the house. so I hooked the netgear running dd-wrt as an ap to the tplink wdr4300 running its stock firmware. that part all works great. both running g/n mixed mode and both different channels to avoid collisions. also only the primary router is providing dhcp and so on just as described in the dd-wrt wiki. OK enough of that.
I found that the dd-wrt router was having issues but much less then the shiny new tplink. after tinkering with different channels on the dd-wrt router and tweaking settings I figured out this. In the advanced wireless settings in dd-wrt there is a setting called bt coexistence. bt standing for Bluetooth. I figured might as well enable it, my phone has bluetooth, and I wasn’t so sure the cheapo wireless keyboard and mouse I was using on the mini was not as well. That little setting made all the difference in the world, that and trying different channels until I found one not being used by other people, for me that was channel 2. I have nearly 0 buffer issues now. I can even stream full 1080p with no issues. prior to those two key changes I was having issues daily. wifi completely crashing when it was bad. not now, not at all.
I don’t know if the results I am having is related to the netgear using a broadcom chipset or not, heres where I will reflect on the tplink being not so good. on the dd-wrt ap router, connected via ethernet cable to the tplink, download speed tests are consistently 15 to 20 percent faster via wifi then when connected to the tplink via wifi doing the same tests. The tplink uses atheros chipset which on the consumer level I have never been fond of. Either they got a crappy driver in the stock firmware or there is a leak somewhere. the tplink coverage isn’t anything to brag on either. I am flashing it to dd-wrt as well, because the stock firmware doesn’t have the blue tooth coexistence feature. I will also lose some coverage flashing the tplink to dd-wrt but without the blue tooth coexistence feature, it will not run the mini properly.
I took it a step further, I sold a second mini to a buddy. I told him what I had run into. sure enough, he also had issues with a linksys wrt54g. That’s old and with stock firmware doesn’t handle a load well. I have had several myself and flashed every one to dd-wrt sp2. I flashed his for him,,,, guess what, same exact results, smooth sailing for him.
I started reading the system messages on the mini when I was having all the wifi trouble, it always was proceeded by java errors in the logs. Doesn’t android use java in 4.1.1 and 4.2.2 to run bluetooth? if so it would all make sense of the results I had.
short end of it, if your router supports blue tooth coexistence and your having wifi issues with your tv stick, try enabling that feature.
Turns out the atheros chipset may or may not have bt devel in it, seems a bit unclear on google. The drivers i am guessing arent open to open source developers, just a guess. As a result the bt coexistance option isnt in dd-wrt. Back when linux was first trying to have a working driver for older atherus chipsets, backward engeneering was the open way, seems that hasnt changed.i used a nightly tet version of dd-wrt. As nice as dd-wrt is, this unit still runs like a schol bus with a moped engine as far as the wifi goes. I bought the tplunk because i was frustrated with the wifi issues i was having amd only looked into the reviews of it for 15 or so minutes. Turns out there is a epron regulating its tx power.there are some patches to get past this that have mixed results and several bricked units. Not that i couldnt jtag it but i am giving it a rest for now, i dont see any great success storys related.
The bt settings related to the minix mini, i stand by that, never more stable, runs flawlessly.
Side note for me at least, i dont run ms os's unless forced, i will aviod any routers containing atheros chipsets in any device as a result, untill the workings are better understood. I remember the old atheros 5k drivers back in the days of mandrake power pack edition, this router reminds me of that time.
All this is just my opinion, nothing more, not without countless hours of time spent though.
If i only ran ms, i wouldnt feel the way i do, it is what it is.
Hopefully someone else is a dd-wrt fan running a rk3066 tv stick and the router is broadcom based.
Related
I gotta know if anyone else is having the same problems connecting to wifi as I am. Whenever I try to connect to my wireless network with any of my devices, it's sporadic. Sometimes it'll connect right away. Most of the time, it takes two or three minutes (!) and sometimes it'll puke on itself and say it doesn't see the network.
In the latter two cases, I can delete the profile for the network and power-cycle the device and it'll connect to the network almost immediately. As you might guess, this is an annoying process to go through.
It never really bothered me until my wife got an iPhone and it connected immediately to the network and does so EVERY TIME SHE USES IT!
Can anyone help me out? Why do these devices take so darn long to connect?
This is the second router I've used (first was a Linksys, currently I'm using a Trendnet), the Raphael (Fuze) and Tornado (SDA) are running their stock ROMs. The Wizard (MDA), I've gone a little flash-happy on, but I've encountered the same problem with all ROMs I've tried.
I'll admit I haven't checked what channels neighboring wifi networks are using (I'm pretty sure I'm the only one on my channel), but when I first got my Tornado and Wizard, mine was the only network (visible) and I was still having problems. And regardless, is the wifi radio in the iPhone that much better than my HTC devices?
(Just a side note, I have three wireless laptops that are all able to connect to the router without a hitch, adding to my belief that my network is on its own channel.)
Just wanted to update everyone that, last night, I checked the wireless networks I could see from my house and none share the same channel as mine, however I didn't take overlap into consideration. The lack of response to this thread would suggest to me I'm the only one encountering this type of problem, so I'll do some experimenting in an area with no other wireless activity and see if connecting is still slow.
O.K. I tested the Wizard and Raphael with a router in an area with no other wireless activity and discovered the following:
If the devices are set for DHCP, it takes a long time to connect. However, they did connect and remain connected without any problems.
If the devices have static IP addresses, they connect immediately and remain connected without any problems.
Conclusion:
The DHCP discovery on these devices takes too darn long to acquire addresses. That, and the slightest bit of EM noise can cause them to crap out. Since I don't have problems with other wireless devices (laptops, iPhone), I'm left with the assumption that either the radio is poor quality (unlikely) or the driver needs some serious fixing (most likely).
When and if the noble developers of this board get linux up and running on the Raphael, I'll be more than happy to test it out.
Since this thread was self-answering and would seem to be of little value, please feel free to delete it, moderators.
I finally tossed my old wifi router and got a shiny "new" Linksys E2000 and have it set up pretty much as stock. B/G/N, a few ports open, WPA2 Personal security, etc. Nothing special except that, of course, the Focus won't connect to it. I had to ask a neighbor if I could use his wifi so it would stop whining about email. How many more months until this "phone" can do something useful? Tell you what, how about if I mail a piece of it to Microsoft every month they don't have an update for it and attached to each mangled piece I attach a note that reads "You"? Think they'd get the point then instead of combing their hair around it? I'd just sell it on ebay except what do you get for a Focus these days? $30 if you throw in the sim card? Still might be worth not having to look at the thing every day, tho. Never again, Microsoft. WP7 is as dead a WM....well, no, I can connect my Fuze to the damn wifi.
Linksys routers, especially the new E series, are notoriously buggy. My Focus connects to two of my 11n routers just fine (one TrendNet, one NetGear). So, it looks like it is the problem with your shiny new router.
I concur. I've connected my Focus to dozens of hotspots without issue.
On the other hand, I've had problems and complaints about 100% of Linksys routers that are owned by clients (granted, they call me when they have problems) and two Linksys routers that I managed myself.
I would never recommend Linksys, and will never own another. I have and will recommend the Samsung Focus, however, and will own another Windows Phone.
(For the record, I own a Buffalo router running http://www.dd-wrt.com)
Ever since Cisco takes over Linksys, its Linksys brand getting worse and worse. Not only the initial release firmwares are always buggy, Cisco also deliberately remove features that are common on other brands of consumer routers so that it does not eat into its Cisco commerical grade router business. Most common compliants I read is that WOL packets do not work on Linksys routers and switches after a device entering sleep for a while.
I have a Linksys E2000 and mine works great. I was loyal to the D-Link brand, but their recent routers have had too much trouble. I was resetting my router at least once a week.
I will admit, it seems to be hit or miss with any brand of router. Just go to Newegg.com and you'll see hundreds of reviews both positive and negative for any brand router. Why can't they just make something that works?
foxbat121 said:
Linksys routers, especially the new E series, are notoriously buggy. My Focus connects to two of my 11n routers just fine (one TrendNet, one NetGear). So, it looks like it is the problem with your shiny new router.
Click to expand...
Click to collapse
I kind of doubt that. Every other device I own works just fine. Bridges, iPhone, iPad, Galaxy Tab, 3 laptops, 2 netbooks, other people's equipment....everything that anyone has tried to connect does so and very quickly. Just like at work where there are literally dozens and dozens of devices connected and what won't connect? Why the Focus, of course! Actually, the E2000 is an excellent router and it gets very good reviews nor have I ever had a problem with a Linksys in a whole lot of years of using them. No, I tend to think the Focus is the junk here.
I am sorry my friend but it is not the Focus phone in "general" You must have a faulty device and should take it back to the store to return it or get fixed. There are so few complaints about Focus devices connecting to routers. I have never had a single problem and I have connected to dozens of routers all of different brands and models.
I would definitely take the focus back to the store, if you bought it from an ATT store, at least I hope you did and didnt get it from some other source as you are probably screwed.
I have been so pleased with my Focus, granted all of the setbacks with updates and short comings.
OP:
I have found people with issues connecting their Android & iOS devices to this router as well. The Android post I read suggested using WPA2 (AES) on the router. A iOS person suggested taking wireless settings off auto and actually selecting a channel such as 11 as well as selecting B & G or G & N instead of auto to fix connection issues.
My personal experience with Cisco Linksys routers in the past has been mixed mode can be flaky. When I set the router to G only or N only (use only if all your devices support N) everything runs smoothly.
yup it must be the router, back home my Focus failed to lock onto my Linksys WAG200 gateway if my Laptop was already connected to it. So I had to turn off the wifi on my laptop and let Focus connect to it first and then let my Laptop also connect. Strange
Set your router to g only
Sent from my SGH-i917 using Board Express
My wifi drops on a consistent basis. I toggle wifi off and right back on, and it kicks back in. This is with stock acer and reflexxx. Stock kernel and one of ezterry's(sp). With both dhcp and static set.
I'd blame it on my router, but at any given moment there are about 6 other devices pulling off my Wifi, and none have anywhere near a similar issue.
Why does my acer's wifi hate me?
Anthony820 said:
My wifi drops on a consistent basis. I toggle wifi off and right back on, and it kicks back in. This is with stock acer and reflexxx. Stock kernel and one of ezterry's(sp). With both dhcp and static set.
I'd blame it on my router, but at any given moment there are about 6 other devices pulling off my Wifi, and none have anywhere near a similar issue.
Why does my acer's wifi hate me?
Click to expand...
Click to collapse
RE-FLEXxx and FLEXREAPER got a dhcp patch in them , so it should prevent that problem you have.
You say you got it with stock ICS also and that doesn't got the dhcp patch so if you ask me it is a router problem. Did you try with only one device connected to your router and not 6.
civato said:
RE-FLEXxx and FLEXREAPER got a dhcp patch in them , so it should prevent that problem you have.
You say you got it with stock ICS also and that doesn't got the dhcp patch so if you ask me it is a router problem. Did you try with only one device connected to your router and not 6.
Click to expand...
Click to collapse
I've considered it's my router. Unfortunately, my cable modem also serves as my wireless router -- provider requires it for 50mbps connections. I've lost my power cord for my old router, and purchasing a new one just to test a theory just doesn't sit well with me. And, unfortunately, things like my HTPC require nearly constant internet.
If no one else has this issue, and you, who seem to be somewhat of a god of acer development, think that it's my router or specific to my individual tablet, then c'est la vie. I shall trust your judgement knowing that there's not much I can do - software wise - to fix things.
Anthony820 said:
I've considered it's my router. Unfortunately, my cable modem also serves as my wireless router -- provider requires it for 50mbps connections. I've lost my power cord for my old router, and purchasing a new one just to test a theory just doesn't sit well with me. And, unfortunately, things like my HTPC require nearly constant internet.
If no one else has this issue, and you, who seem to be somewhat of a god of acer development, think that it's my router or specific to my individual tablet, then c'est la vie. I shall trust your judgement knowing that there's not much I can do - software wise - to fix things.
Click to expand...
Click to collapse
If it happened on stock ICS only then I would understand due the dhcp bug.
But my rooms and ezterrys from got the dhcp patch build in to prevent the problem you are having, so on the software side there are no more options when you use ezterrys near stock from or one of mine.
I never have wifi problems and I constantly stream HD movies to my Sony blue ray player in the same time my tablet is connected and so is my phone.
In a rare situation maybe once a moth a need to restart my router and it is also a cable router to my pc with wifi host access for my friends if they pop in. So it is very busy all the time.
This issue has been posted several times. I have searched most threads but didnt get right answer. I have a Samsung Galaxy S2 and Google nexus 7. I could connect both at home and at work to wifi and then to network. But for the last 1 week I am unable to connect to internet at home. There isnt such problem with laptop and Ipad at home. I had this problem with my galaxy s2 in the past, when it was only android device at home. I didnt give much attention at that time as it used to sort itself on its own. I mean to say though the network connectivity behaviour is erratic it didnt bother me much as I have other devices to use to connect to internet. I am posting this now to highlight this problem with android and some great soul will sort this out forever. I dont think it is a problem with router as this happened to several people with different brands of routers. As suggested by somebody, I have tried the Wifi fixer app, with no success. My galaxy S2 is not modified, but nexus 7 is rooted.
I had the same problem. I fixed it by setting my router to only do B/G instead of B/G/N. This means I can only get max 54kps, but so what. I was only getting a bit better than that before.
Hope this helps!
Sent from my HTC One S using xda app-developers app
sripos said:
I dont think it is a problem with router as this happened to several people with different brands of routers.
Click to expand...
Click to collapse
It takes two to Tango.
I had the symptom you describe on a 3 year old Android phone, while with the same router, no problem with Macs, Windows PCs, and iPod Touch devices. The Android phone could associate and authenticate ("connect") to the router, but it would never get an IP address via DHCP.
What was the solution? I updated (flashed) new firmware to the router.
Interop problems happen all the time with WiFi gear; it's unfortunate but true. I mention the above example because the symptoms seemed to point to the Android device as being the "trouble", and yet the fix involved changing software on the router side of things. And that's entirely the point - when bugs occur, they occur between TWO software stacks. Router firmware can have "latent" bugs that require client devices to deviate just a little bit before they occur, and the same thing is also true with the software stack on the Android device.
In general, you have more knobs to fiddle with on the router than you will have on the Android phone/tablet, and the more variable the behavior of the router is, the more likely bug expression between the two software/hardware stacks becomes. So - as with the suggestion of the above respondent - if you want to experiment, try turning off non-essential features on the router such as multiband, proprietary channel bonding or "turbo" modes, beacon suppression, etc. Simplify things and see if the problem disappears.
good luck
thank you
steve1326 said:
I had the same problem. I fixed it by setting my router to only do B/G instead of B/G/N. This means I can only get max 54kps, but so what. I was only getting a bit better than that before.
Hope this helps!
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thank you, I will try this.
With 4.2.2 I had no issues with wifi and can still go back to that version and have no issues, but with version 4.3 and 4.4 I have had and still have the following problem.
I have a list of known wifi connection points as well as available access points. Everything appears as it should, but the wifi will not automatically connect to any wifi (protected or unprotected/known or previously unknown) without first turning the wifi off and back on. Additionally, this only works if the persistent background wifi option is toggled off. If I do toggle the wifi on and off and connect to an available access point everything is fine so long as I remain in range and stay connected. If I go out of range and lose the connection, when I next reenter the range and the access point shows up on the list it will not connect unless wifi is cycled on and off. This happens every single day at work and home, although there is a workaround, it is quite annoying to have to cycle the wifi off and on. The networks will show as available and if I click on them and try to force it to connect, it still won't work unless I cycle on and off.
I have seen prior threads with this issue on 4.3 and there was a topic in the official Google issues page and was frankly hoping desperately that 4.4 would fix it, but alas, it has not. I know it is not the device itself since reverting back to 4.2.2 solves the problem.
Does anyone know of a permanent fix to this wifi issue that doesn't involve reverting to an older version of android or some kludged together solution?
Ya.. I have also been facing this problem since i have installed KitKat 4.4 on my i9300
Are you stock? Maybe try another ROM? I had the exact same problem, but my problem was my wifi AP.
1- My router was setup for a/b/g/n, I set it to only what I really had using the Wifi AP, which was g/n
2- I had a weird cable modem to router to Wifi AP setup. The router was handing out IPs, not the Wifi AP. I removed the router and only let the Wifi AP give IP addresses (DHCP). It seemed like the "further hops" away that the DHCP addresses were, the more issues i had with my Android connection.
No other devices on my network had these issues, but doing the above made a world of difference.
All that made my connections lightening quick, no issues at all since then.
odd Wifi behaviour
I got a refurbished delivered N10 last evening, came with 4.2.2, played with it a little, did a network benchmark test (FTP off a LAN NAS) and was getting comparable peformance to my other fastest system (a Thinkpad Ubuntu laptop). It seemed stable but I only used it for like an hour as 4.2.2. I was getting FTP of max 4MB/s over a N-router.
I then let it OTA to 4.3 and then played with it for some hours. Issue I found was the Wifi would work and then have "authentication problem" I had to turn Wifi off then on to make it connect to router. I've had that issue with other devices at times. I was thinking of staying on 4.3 to allow 4.4 to have another bugfix (its not been long out on N10) but I had a key issue for me (PPP Widget didn't work) so I did a stock 4.4. flash upgrade.
On 4.4. the Wifi speed is still fast, but periodically it just stops working, a glitch.
One key thing that stands out is the N10 is connecting at much higher Mbit speeds than any other of my devices, it is showing 130Mbits vs say 20-65Mbits on other devices. I'm wondering if my N10 is "too good" for my router an old low-spec refurbished model (Cisco E1200 v2, which I flashed to latest DD-WRT) ?
I'm not so far disappointed with network performance, just network stability, but I can't tell for sure if its the N10's fault or my router's fault. I'll play with settings a while til I find something stable.
When I first got my N10 I had a lot of trouble with wifi connection. Mostly authentication issues, or it would authenticate but not have internet access. It was frustrating, and Google's support was clueless.
I then tried using wireless tether from my N4 and it worked as it should. The issue ended up being the Arris router that Time Warner uses. I bought a Linksys router and have had 0 issues since. So if you're using an Arris router, or it shares the same chipset, that might be the issue.
The router is the Arris DG860.
Ichiban Rei said:
When I first got my N10 I had a lot of trouble with wifi connection. Mostly authentication issues, or it would authenticate but not have internet access. It was frustrating, and Google's support was clueless.
I then tried using wireless tether from my N4 and it worked as it should. The issue ended up being the Arris router that Time Warner uses. I bought a Linksys router and have had 0 issues since. So if you're using an Arris router, or it shares the same chipset, that might be the issue.
The router is the Arris DG860.
Click to expand...
Click to collapse
Good anecdote.
Well in our house, the proliferation of gadgets has changed progressively to a large number, I make it 14 devices from an initial 2 devices 5 years ago. I count 4 wired and my 4 devices, my son's 2 and my daughter's 3 and my wife's 1. They all compete for router bandwidth, Wifi spectrum, router CPU / cache.
What I might do with this high-performance (capability and demand N10) is segment my network using an old G router I hard fix to non-overlapping channels from N-router, and connect the low-spec devices to the G and high-spec to the N. That will involve no $ and naturally reduce congestion. I run a NAS and download media to it and then stream to gadgets off NAS so I'm Wifi-limited often more than Internet-limited, and even tweaking I get 2MB-4MByte (16Mbit~32Mbit) off a NAS is making my typical LAN speed the same as the Internet bandwidth I buy (16Mbit).
My NEtbook (EEE 1015PN) if it ever felt a Wifi hiccup it would lock-out that frequency and so not see the router til I powered off netbook and remove battery.
I do wonder if some of the N10 Wifi complaints are really just generic or bad combinations with router or "straw that broke the camel's back".
I'm having wifi issues with my N10 as well. I had a few wifi issues at work, but not at home while using 4.3. Now with 4.4 I'm having serious wifi connection issues both at work and at home. In fact my N5 running 4.4.1 is having issues connecting to wifi both at work and at home. Not as often as my N10, but it still happens. I'm running stock on both and have no problem connecting to either network with my laptop.
I've installed wifi fixer, but so far it doesn't seem to be helping much. Does anyone have any suggestions on what might be done to fix this that doesn't involve rooting either device?
I'm now running 4.4.2, and I'm experiencing better wifi connectivity, but it still drops out more than it did on version 4.3. Is anyone else having this issue?
Sent from my Nexus 10 using Tapatalk 4
droidfan77 said:
I'm now running 4.4.2, and I'm experiencing better wifi connectivity, but it still drops out more than it did on version 4.3. Is anyone else having this issue?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
I'm in the same boat, more drops in 4.4.2 than on 4.3 and I'm running stock
same here...waiting for a fix
experiment with the router
metzner said:
same here...waiting for a fix
Click to expand...
Click to collapse
Some of your problems might be just coincidence, something changed in your area around the same time as you upgraded. Some of these are just the wrinkles of firmware of device vs firmware of router, some combinations work bad and isn't really "fault" of Android in that you can't test every combination. You could wait for a fix from Android... or just try to avoid the wrinkle by changing settings on the router. A common thing is to move the router from auto to fixed channel and fix to 20mhz narrow. Go the place you mostly are with the N10 and use a Wifi analyser to find the least-congested channel and then set the router to that. What that does is reduce channel-hopping and gives less opportunity for firmware issues on both router and the Android device.
I also had a problem with my N7 when I moved house. The answer was to flash DD-WRT on my router and the problems went away.
So either wait+complain or go look at your router now.
Right now I have DD-WRT on an old refurbished Cisco E1200 and I set it to channel 3 with 20mhz and I got very good Wifi performance. With the stock Cisco firmware I was getting Android Wifi drops and poor performance. Yes, that's partly Android's fault but I fixed it myself quicker flashing firmware on the router.
I also took opportunity in DD-WRT to setup IPTABLES for a transparent proxy so all the devices in my LAN now share a large harddrive as http cache so e.g. any downloads from Play store for say my N4.... is cached to my N10 so I only ever download anything once.
If you have issues still with the N10, then what I find solves a lot of problem is do a stock flash of 4.4.2, on setup untick all the backup+restore from Google, then manually install and configure yourself to make it "vanilla". That often fixes accumulated wrinkles unique to your history of your device and places to more mainstream with less likely of having a unique problem. I do that on all my Android devices now (N4, N7, N10).
Similar wifi problems here
I've had similar issues with my N10.
I will have fast internet speeds (30+ Mbps) and it will just freeze. I'll be watching youtube and it will start buffering. Doing a speed test on my phone shows the speeds as normal. It makes no difference whether connected to 2.4 GHz or 5 GHz wifi.
I just resolved my WiFi issue this past weekend. Connectivity is rock solid
Here is what I did I.
Purchased my own cable modem/router. New router had updated firmware. time warner cable modem did not.
Change beacon interval from 100 to 20 on router and repeater.
Made sure router was on a less congested channel.
All is rock solid
YMMV
bflatmajor said:
I just resolved my WiFi issue this past weekend. Connectivity is rock solid
Here is what I did I.
Purchased my own cable modem/router. New router had updated firmware. time warner cable modem did not.
Change beacon interval from 100 to 20 on router and repeater.
Made sure router was on a less congested channel.
All is rock solid
YMMV
Click to expand...
Click to collapse
Great! Often just tweaking settings can do wonders. I flashed DD-WRT on mine and it solved a lot of issues on an old low-spec router.
Hey Guys,
I posted this in General section but saw this so I will add this info:
I just want to share what and why I did it. First off I did not have problems with my wifi on 4.2.2 with the Nexus10. the second that I went to Slim Kat and Vanir 4.4.2 I had weak wifi signal at work and at home when my nexus 7 slim kat and my galaxy note 2 Vanir did not. I noticed that RAM was also weird on the nexus 10. Even though it showed 2gb of ram on the specs it was only showing 1099 on 4.4.2 when I show that I have 1647 ram available with 4.2.2.
Concerning the OS using Ram. Google said that they would make Kit Kat more RAM friendly but I was using 535mb of RAM for 4.4.2 and right now I am showing only 357.3 mb for 4.2.2. I am using the same apps launchers and screen savers
I just flashed back to 4.2.2 this morning so I will update later, I do see an improvement in the wifi though.
I just want to say that I love Slim Kat and that is why I am on the 4.2.2 I just think Google somehow hosed up the wifi on the Nexus 10.
B][/B] Ok so I am at work and have went back and forth between 4.4.2 and 4.2.2. the 4.4.2 connects and disconnects back and forth. When it does connect to router but it says poor connection and it is only 24mbps. "It drops way more than connected" I am 45 ft from router in an open environment.
The 4.2.2 Slim Kat has a fair connection with 78 Mbps and has not dropped once. So I don't know what the difference is with Kit Kat compared to Jelly Bean but for my nexus 10 my wifi is great now with Jelly Bean. I wish I could figure out why and fix but I do not know programming.
I also installed on both 4.4.2 and 4.2.2 a app called WiFi Connection Fixer *Root* by ZEXTR. It did not help 4.4.2 but it did help with 4.2.2. this app helps connect to poor connections or when Android says avoided poor connection.
I don't know why the Nexus 10 is having issues with wifi with KitKat but I wish I could fix it. So I will be on 4.2.2 until a new version comes out and I will test it to see if it fixed it.
update; I have used 4.2.2 all day with the wifi connection fixer and I have not dropped wifi once and the download speed is fast. It is much faster than what 4.4.2 was, at least on my tablet.
Joe
Nexus 10 4.4.3 WiFi Bottleneck Problem
Hello there everyone,
I just wanted to confirm that I personally found a fix on my end for my Nexus 10 WiFi bandwidth problem that was definitely evident for many people that upgraded from 4.4.2. First off, I'm totally stock. I will most likely root & ROM this thing in this near future. I was having a bottleneck on my Nexus 10 around ~2 mbps when I tested using the speedtest.net application (may not be the best measurement application but it works). I ended up fixing the problem by changing my router settings in the WiFi section of my browser based software to N/G Mixed instead of just Mixed (which allows 802.11a/b as well as 802.11g/n to run on the router's WiFi signal). I use DD-WRT on my router as well so that may have played a factor in it but I did NOT see an increase in bandwidth until making the N/G Mixed change in the settings. I found this suggestion earlier in the thread and wanted to give it some credit. Thanks everyone!