I have a Vivobook Pro 16x which has a mediatek 7961 wifi chip and I just installed Nixos on it. Everything works except the Wifi. The wifi works occasionally, but not always.
I updated the kernel to the latest version by setting boot.kernelPackages = pkgs.linuxPackages_latest;, as I read that was needed for the mediatek 7961 chip to work.
I’ve also tried setting networking.networkmanager.wifi.backend = "iwd", which seems to work slightly better, but only for a few seconds.
So my wifi works for a bit, few seconds, and then nothing loads.
Are there any other settings I can try out?
Sadly I was unable to fix it through software. Luckily it was easy to replace the wifi chip. So I did that, now using an AX200 chip, which works flawlessly with the default settings in NixOS.
Related
This is happening intermittently, but frequently iOS devices are connecting to my MacBook Pro (mid-2014) and then quickly disconnecting. Without any clear error or log to indicate why.
Where should I look for event logs that may help indicate what the underlying error is? I've tried to look through console logs for system events but I haven't seen anything that jumps out.
I've gone through many of the recommended solutions for Xcode not recognizing iOS devices:
Clean Project
Delete DerivedData folder
Restart Xcode
Restart the Mac
Restart the iPhone
Reset device permissions to re-trigger the "Trust Computer" prompt
Deleted iOS DeviceSupport folder
Alternated USB ports
Kill USB process
Deleted and re-installed the latest version of iTunes
Swapped out 4 different lightning cables
Tried 5+ different iOS devices with various versions of the OS
Went back to Xcode 8.2.1 to see if it was an issue with 8.3.1
Corporate IT reset my SMC this morning. I put in a request to have them disable Sentinel Agent to see if that's a factor, but it's not the clear culprit since other developers are still able to connect.
Very rarely, the connection will hold and I can use the device just fine. I have yet to determine what combination of astrological events leads to that case though.
Had the same issue and tried 10+ of the things you listed as well. Even tried uninstalling a few things that could have been interfering. As soon as I switched USB ports it worked and stayed connected. Turned out to be lint/dust in the USB port. A little duster in the port and it works like a charm. Sometimes the answer is so simple.
This is a disappointing solution, but IT reimaged my machine and the device connection has been stable ever since.
So if all else fails for you, start over.
Update:
This ultimately was narrowed down to an issue with Mobile Labs Device Bridge. Removing their launch daemons and restarting the system is the much simpler solve!
I am currently running a robotic's project using an Hokuyo (URG-04LX-UG01 - http://www.hokuyo-aut.jp/02sensor/07scanner/urg_04lx_ug01.html). This one is plugged to my computer using USB. Although it creates the port "/dev/ttyACM0" when I plug it, I can't connect to it using the associated library (serial connection error). Until here, nothing's strange, bugs or misprogramming happens but here is my problem :
When I plug the hokuyo to an USB HUB, which is also plugged to my computer, I can connect to it and everything works perfectly.
My laptop is a samsung 900x3c running Linux Mint 15.
Do you know what an USB HUB changes in the USB communication ?
Is there a link with my laptop ? (I used to face the same problem using an ARM-Based embedded computer)
Is it possible to fix the issue without using any hardware solution ?
If it's not, is there anything more compact than an USB HUB which could fix it ?
Thanks !
Is your USB-HUB powered from external power adapter? URG-04LX-UG01 seems to consume 2,5W/5V=0,5A. This is limit for USB. Laptop USB ports are not so powerful and if device consumes a little bit more than max, then they just cut the power.
Update
The device is USB 2.0 Full Speed. I've seen USB controller, that had problems with USB 1.0 or USB 2.0 devices. Hub presents itself as USB 2.0 High Speed and handles USB 2.0 Full Speed transparently for the Laptops USB controller. Do you have another Laptop/PC to check this?
I'm kind of late on my feedback for that issue, but better late then never so :
I've been able to determine that the whole issue came from my USB cable. Somehow there was an electrical issue in that cable and the computer-or the hokuyo- was not able to properly communicate through it. I think that the USB HUB was somehow able to correct theses electrical issues.
Anyway, problem solved !
I'm trying to figure out why my BTLE TI CC2540 keyfob is working with my iPad 3 but not with the iOS Simulator equipped with a new GBU521 IOGEAR adapter on Mountain Lion.
I've been able to successfully connect the iOS 5 Simulator Bluetooth in the general settings (it says on, now) to my BT adapter, and to be considered as 'powered on' in my proof of concept app. I'm using a GBU521 IOGEAR adapter, which only worked after upgrading to Mountain Lion (tried Lion with some hack modifying some .kext files-- don't do that. Upgrading to Mountain Lion was impossible until I reverted that .kext). I then ran the Apple suggested nvram setting, rebooted, and it was able to recognize the BT adapter.
I'm able to communicate with my iPad 3 successfully (registering the button pushes, accelerometer, etc), but when I try to run it on the simulator, it just doesn't discover the device. It's telling me the BT state is CBCentralManagerStatePoweredOn, but then when I tell it to discover peripherals, it comes up with nothing.
How can I establish Bluetooth LE communication between the iOS Simulator and an LE-enabled iOS device?
(modified from my answer in other iOS Simulator Bluetooth thread here: Bluetooth Dongle and iOS Simulator)
Throw away the IOGEAR and pick up a Cirago BTA8000.
I'm not sure why you were able to turn Bluetooth on in the iOS Simulator (possibly related to your kext editing, which I tried too), but I suspect it's not actually on. I bought the IOGEAR you mention, in addition to the Cirago BTA8000, and the MediaLink 4.0 adapter. Turns out that anything based on the Broadcom chip won't work despite my MacBook having the exact same one built in, which means the MediaLink and IOGEAR don't work. My Cirago shipment just arrived this morning, and the Bluetooth slider in the iOS Simulator flicks to "ON" in less than a second.
If you want to experiment, I'd love to hear if other non-Broadcom chips work too.
Does your keyfob didn't came with a dongle? I'm planning to buy one :S
Update: I've just found this(But probably you have arleady seen this, it explains why you are using a separate adapter): http://developer.apple.com/library/ios/#technotes/tn2295/_index.html
Also the reviews on amazon of your adapter doesn't look very good. have you tried it with antoher device? http://www.amazon.com/IOGEAR-Bluetooth-Micro-Adapter-GBU521/dp/B007GFX0PY/ref=sr_1_1?ie=UTF8&qid=1344560021&sr=8-1&keywords=GBU521+IOGEAR
I'm developing a mobile app using Flash Builder 4.6/AIR. I've been able to debug on the device (an iPhone 4s) just fine until now. I connect my iPhone to my mac with the USB corad, and debug.
All of a sudden I'm getting a black screen for close to a minute. Then I see the "Enter ip address or hostname" dialog. If I enter the ip address of my machine it doesn't matter. The window goes away for about 15 seconds, then comes back. Meanwhile, Flash Builder on my mac times out. The only way I can actually see the program running is if I hit 'Cancel' on that dialog. The app then launches, but I cannot set any breakpoints, cannot debug.
Everything I've found on the internet around this issue mentions it in reference to AIR for android -- not iOs. But I'm seeing it with iOs.
Anyone know what's going on here?
Thanks.
To make it easier for future readers, the official answer to this issue;
With the current (official) version of the AIR SKD (3.2) USB debugging is not supported on iOS devices. This is going to change with the future 3.3 release which (amongst others) adds USB debugging support:
"USB debugging for AIR iOS
This new feature allows the iOS developer to connect to the desktop via USB while debugging their mobile applications instead of relying on network connectivity."
With version 3.2, iOS debugging works over the local network, so both devices (the machine the debugger runs on and the iOS device) have to be in the same network so that they can communicate with each other.
See also the reply to What is the address of my Flash debugger?, it really helped me to resolve similar issue. Using 'ios-debug' mode was the way to go.
If you still have this problem using Android with the device connected to same wifi, try checking firewall rules. In my case FlashDevelop was blocked and I didn't suspected because of updates worked perfectly.
Do iPad in the simulator and the Macbook share a same network? I have connect a wifi then VPN on my Macbook and everything works just fine on the outside Safari. But when I open the iPad simulator and it seems on that inside Safari the VPN is not set up yet cuz I cant access to my specified website. (But internet still works. I guess it is the wifi)
Not sure if I make it clear. I wonder how can I solve this problem. Thanks for helping!
Generally the iOS Simulator runs with the same IP and actually in the same process space as other applications on your Mac.