Hi,
I've just bought my new O2 XDA IQ. (Tornado). I thought I'd try and deploy an application to it but I'm getting the following error:
Error 1 The device security configuration disallowed the connection. Ensure that you have the appropriate certificates on your device for development. Review your SDK documentation for proper security settings for connecting to this device. Device Connectivity Component.
Has anyone got any ideas for what I need to do?
Sorry for replying to own topic.
I found this link:
http://blogs.conchango.com/stuartpreston/archive/2005/11/10/2376.aspx
Just what I needed. Hope this helps if anyone else has the same problem.
Actually, it will be a good idea to use device emulator rather than your real device to debug your app. Unless you want your phone really mess up.
On the other hand, if your app use some device specific features, than you should pray every time before deploying.
That's my experience.
Hey
I'm taking on a new project and I have a few questions that are explained below, This is my first post here been a long reading member but never had any questions until now, so if this is in the wrong section, I'm sorry.
The project is basically converting a netbook into a tablet, being that the netbook lacks sufficient power to run Windows 7, but runs Android x86 really well. The only problem I have is that I need a touchscreen and I've decided to pick up a touchscreen kit, which on the fidohub website, its called the 10.2" Solderless touchscreen kit however they don't support Android and only provide drivers for Win7, OSX and Linux.
So what I'm asking you guys is how do i get past this problem and get myself an Android compatible screen.
Any help with this project will be a great help!
Thank you,
Rohan.
Maybe find the src and rewrite it?
And what would that require? Any guide available?
Try the linux drivers. Android is based on the linux kernel so it should work. If not youll have to mod the drivers up yourself
Sent from my Desire HD using Tapatalk
spam
This is exactly what I am just about to start! By the looks of it I am a few months behind you!
I have been searching around and have found little info... did you have and luck with the linux drivers or did you try them? would be great to hear how you got on?
many thanks to all,
Sam
Tablet Drivers
In the search all forums box in the upper right corner type in "tablet drivers" There is a list of options that maybe you can put to use.
adlakeche said:
In the search all forums box in the upper right corner type in "tablet drivers" There is a list of options that maybe you can put to use.
Click to expand...
Click to collapse
I am doing something very similar, I am basically using a MK802 unit in the car. The car already had a VGA USB touchscreen from my PC install. I connected my 4-wire touchscreen to it and nothing. Funny thing is, I connected a different screen from another manufacturer and it worked, with the exception that up and down were inverted. But the brand in the car is the one that doesnt work. I know that when I use this device in Windows, it uses drivers from the touchkit.com website. This side also have Linux drivers, but unsure what to look at. I have no experience with root, or anything Android as far as code and stuff. The have drivers for 32bit or 64bit. The have it for Linux, Red Hat, Fedora Core, SuSE, Debian, Ubuntu, Yellow Dog, Mandrake. All of which is alien to me. Is there a driver that will work closest to Android?
There's already a great thread where people are reporting what USB/Bluetooth items will and won't work on the Surface RT.
According to Pluggable, a manufacturer of USB peripherals, the problem lies much deeper: Windows RT doesn't support any USB device requiring a driver, and support may never come. It says:
"Windows RT does not have a Device Driver Development Kit and does not support or allow the installation of drivers. There is currently no Windows Update for Windows RT from which to match and download newly approved drivers for new device types from 3rd parties."
In short, the only devices which will work are devices which have traditionally had in-box support in Windows and never require a 3rd party driver to be installed: USB hubs, USB Mass Storage (USB hard drives and flash drives), USB Audio (headsets and mics), some USB printers, most USB video (webcams), USB HID (keyboards and mice), and a few other special cases.
I knew RT drivers would be a problem; this article implies that the drivers may never be coming at all.
AndyRathbone said:
There's already a great thread where people are reporting what USB/Bluetooth items will and won't work on the Surface RT.
According to Pluggable, a manufacturer of USB peripherals, the problem lies much deeper: Windows RT doesn't support any USB device requiring a driver, and support may never come. It says:
"Windows RT does not have a Device Driver Development Kit and does not support or allow the installation of drivers. There is currently no Windows Update for Windows RT from which to match and download newly approved drivers for new device types from 3rd parties."
In short, the only devices which will work are devices which have traditionally had in-box support in Windows and never require a 3rd party driver to be installed: USB hubs, USB Mass Storage (USB hard drives and flash drives), USB Audio (headsets and mics), some USB printers, most USB video (webcams), USB HID (keyboards and mice), and a few other special cases.
I knew RT drivers would be a problem; this article implies that the drivers may never be coming at all.
Click to expand...
Click to collapse
i think they just have to submit drivers to microsoft to have them work, my canon 5d mk 3 worked out of the box and i've had to install drivers for all my dslr's in windows before
When you plug in an unsupported device, does it at least attempt to search windows update for a driver? Or are all supported drivers included in the device?
Sent from my Galaxy Nexus using Tapatalk 2
Skitals said:
When you plug in an unsupported device, does it at least attempt to search windows update for a driver? Or are all supported drivers included in the device?
Click to expand...
Click to collapse
That's a good question. To control things, I turned on Airplane Mode. Then I plugged in an Easy Transfer Cable.
Surface RT recognized the cable, and USB Transfer Device appeared in Device Manager, but with the yellow exclamation point.
I turned off Airplane Mode, opened the Device Manager's Properties window for the USB Transfer Device, and told it to search automatically for updated driver software.
After visiting Windows Update, it gave me this message: "Windows was unable to find driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
I'm thinking Windows RT only accepts USB items that the OS natively recognizes: cameras, external storage devices, mice/keyboards, and a few other things. It won't accept anything requiring a third-party driver because Microsoft doesn't want to introduce that as a possible security hole.
I would be surprised if MS would not provide a driver development kit.
WinRT is basically a recompiled version of Win8 for the ARM. So in theory I would be able to take my C/C++ coded driver and run it through an ARM compiler to produce the correct dll.
Just made a quick look around, and I see the essential dll's required to implement a proper windows system driver. So it should work...
draftQ said:
I would be surprised if MS would not provide a driver development kit.
WinRT is basically a recompiled version of Win8 for the ARM. So in theory I would be able to take my C/C++ coded driver and run it through an ARM compiler to produce the correct dll.
Just made a quick look around, and I see the essential dll's required to implement a proper windows system driver. So it should work...
Click to expand...
Click to collapse
Just like you should be able to take your C/C++ desktop app and run it through the ARM compiler and it should work (like Office RT), but it doesn't. MS has it locked down tight. They are going the completely closed ecosystem route... like Apple (iOS).
Its a shame, because it otherwise has the potential of full blown windows 8. No reason we shouldn't have recompiled ARM versions of VLC and other open source desktop apps, but MS is keeping developers in the metro sandbox.
Sent from my Galaxy Nexus using Tapatalk 2
This was incorrect
AndyRathbone said:
There's already a great thread where people are reporting what USB/Bluetooth items will and won't work on the Surface RT.
According to Pluggable, a manufacturer of USB peripherals, the problem lies much deeper: Windows RT doesn't support any USB device requiring a driver, and support may never come. It says:
"Windows RT does not have a Device Driver Development Kit and does not support or allow the installation of drivers. There is currently no Windows Update for Windows RT from which to match and download newly approved drivers for new device types from 3rd parties."
In short, the only devices which will work are devices which have traditionally had in-box support in Windows and never require a 3rd party driver to be installed: USB hubs, USB Mass Storage (USB hard drives and flash drives), USB Audio (headsets and mics), some USB printers, most USB video (webcams), USB HID (keyboards and mice), and a few other special cases.
I knew RT drivers would be a problem; this article implies that the drivers may never be coming at all.
Click to expand...
Click to collapse
Hi gang-
I work for Plugable, not trying to advertise, but just want to share some news.
Then information we're quoted in above turned out to be wrong.
We've updated the post referenced above,
[Update: 11/16/2012] We had previously incorrectly written that device drivers aren’t installable on Windows RT. That’s not right.
Click to expand...
Click to collapse
We've also added a follow up where we explain how to install a driver on a Windows RT device. Here's the new post.
We're very sorry about providing the misleading information, but we'll be working hard towards being open about news and developments.
I'm game to explain how we arrived at the bad findings if anyone's interested: essentially just that Windows Update hadn't found any drivers, and we'd not been able to find any drivers posted at http://catalog.update.microsoft.com, nor other important resources for development and distribution.
dharmapunk said:
Hi gang-
I work for Plugable, not trying to advertise, but just want to share some news.
Then information we're quoted in above turned out to be wrong.
We've updated the post referenced above,
We've also added a follow up where we explain how to install a driver on a Windows RT device. Here's the new post.
We're very sorry about providing the misleading information, but we'll be working hard towards being open about news and developments.
I'm game to explain how we arrived at the bad findings if anyone's interested: essentially just that Windows Update hadn't found any drivers, and we'd not been able to find any drivers posted at http://catalog.update.microsoft.com, nor other important resources for development and distribution.
Click to expand...
Click to collapse
Any ETA (possibility?) of RT drivers for your USB video adapters? Oh, and just bought that Ethernet adapter, thanks for letting us know!
Actually, it does work. You just have to sign the apps with the Microsoft code integrity key. This may give the impression that you can't do it at all, but that's not actually true.
Obviously, this isn't possible for a third-party developer to apply such a signature directly, and MS is generally not fond of signing third-party code. It happens on occasion, though. Consider the Flash Player in IE10 for RT; that's Adobe code, but it's signed with the MS key. Downloading suitably signed EXEs and running them works just fine; for example, the remote debugging server for Windows RT is distributed by MS exactly like any other downloadable EXE, and it works.
In fact, if you somehow manage to put your device in Testsigning mode (which exists in RT and also in x86 versions of Windows, and allows using any trusted signature instead of only the MS signature), you can install your own signing certificate and then run your own compiled and signed desktop apps. Unfortunately, testsigning mode is a bootloader option, and the bootloader for all currently released Windows RT devices prohibits its use (although development devices were found to support it).
@dharmapunk: Any chance this driver is going to show up in Windows Update soon? Since you've obviously already gotten the MS signature, hopefully it will be literally plug-and-play soon...
GoodDayToDie said:
@dharmapunk: Any chance this driver is going to show up in Windows Update soon? Since you've obviously already gotten the MS signature, hopefully it will be literally plug-and-play soon...
Click to expand...
Click to collapse
@GoodDayToDie Sorry, I'm not entirely sure on this- since it's an ASIX developed driver the info I have here is second hand. We anticipated this would be baked into RT's RTM, however for some unknown reason it wasn't.
Sorry I can't be more help here, I'm still looking for ANY WinRT drivers over on catalog.update.microsoft.com.
---------- Post added at 06:05 AM ---------- Previous post was at 06:00 AM ----------
addictivepixels said:
Any ETA (possibility?) of RT drivers for your USB video adapters? Oh, and just bought that Ethernet adapter, thanks for letting us know!
Click to expand...
Click to collapse
Sorry @addictivepixels, I've not heard any news that DisplayLink is close to releasing, or even working on, a WinRT usb graphics driver. I anticipate that will stay only x86/x64 for quite some time. Wish I had better news...
The saga continues...
Hi again-
The saga continues. We’ve been asked to take down the WinRT driver for our ASIX-based USB Ethernet adapter. Seems like it wasn’t supposed to have been released after all, so we’re taking the driver off our website soon- before month's end.
We’ll still be selling the adapter. We’ll still be supporting customers. We’re even keeping the installation instructions that we wrote up on our website.
I hope that this issue can be resolved soon. I want more devices to plug into Surface too!
Since I'm a noob I can't post a link to our new post, however the one the OP listed now has an update notice with a link to further details.
dharmapunk said:
Hi again-
The saga continues. We’ve been asked to take down the WinRT driver for our ASIX-based USB Ethernet adapter. Seems like it wasn’t supposed to have been released after all, so we’re taking the driver off our website soon- before month's end.
We’ll still be selling the adapter. We’ll still be supporting customers. We’re even keeping the installation instructions that we wrote up on our website.
I hope that this issue can be resolved soon. I want more devices to plug into Surface too!
Since I'm a noob I can't post a link to our new post, however the one the OP listed now has an update notice with a link to further details.
Click to expand...
Click to collapse
Is there any chance that we could get the source to said driver? I'd like to poke around it to see if it has any vulnerabilities that'd allow a kernel-mode exploit.
I understand if you can't/don't want to post it.
netham45 said:
Is there any chance that we could get the source to said driver? I'd like to poke around it to see if it has any vulnerabilities that'd allow a kernel-mode exploit.
I understand if you can't/don't want to post it.
Click to expand...
Click to collapse
@netham Other than the driver package in the link in the original post, we haven nothing else to offer. Since I knew our blog post with the driver download was quoted in the original post in this thread, we wanted to warn any customers who might have purchased our USB2-E100 that the driver will be going away soon due to a takedown request.
To be clear, our concern is making certain any customers who purchased the USB2-E100 for use on Windows RT have a chance to download the driver before we take it down.
I'd post the link to our new blog post with details if I could, trying again: http://plugable.com/2012/12/11/windows-rt-surface-usb-ethernet-takedown
The RT driver situation has been odd to say the least - still trying to figure it all out. I've been able to yank some drivers out of my Windows 8 Pro box and manually install them onto the Surface. Outcomes:
I was able to get my Smart Card Reader half functional this way, although there is no current affordance for installing the necessary minidriver that allows the .NET card to fully interoperate with the Surface.
I had the same minidriver issue with my DisplayLink UV+.
I was also able to get my Lumia 900 to mount , but can't get the file system to read past the top level.
More research required...
That is... *very* interesting. Those must be .NET user-mode drivers, because the Surface RT uses the ARM instruction set and is completely incapable of running the typical written-in-C/C++-and-compiled-for-x86/x64 drivers used on "normal" Windows.
Alternatively, the driver may contain a firmware blob that is loaded into the microcontroller of the hardware even though the actual Windows driver code (which would be x86) wouldn't work. The firmware blob won't be x86, it'll be whatever instruction set the device's microcontroller executes.
Don't ever buy Windows RT again, it's a dead end operating system.
well, at a very low price,it's a good device. Kids like them for games and music. Youtube etc . play well on it . Not totally useless but I would of never paid the full price for it.
hello,
i bought the easycap viewer android application,
and installed it on my devices
The easycap viewer needs an easycap frame grabber , connected via usb to the device and connected to a camera (via bnc or s-video or rca connector)
the devices i have are these:
- Acer iconia tab a500 (tegra 2 , android 4.03)
- Created N7 (china phablet, mt6592, android 4.4.2)
- Xiaomi m2s (qualcomm snapdragon, miui v5)
The application does work flawlessly with the Xiaomi m2s,
instead:
on the Acer, when i start the app, the screen become black, and the app is not responding
on the Created N7,, the appl starts , but when i connect the camera, i cannot see the video coming from the camera
I dont understand why on these devices the app does not work,
and need help to understand what is the cause of the problem.
The app includes an option to send log report to the developer
(autodroid), i sent it, but autodroid told me to try with a powered hub, but this did not help...now they are working on other project, so they told me they cannot help
Could you please help me to find the cause of the problems?
By the way, on the Acer i cannot send the report, because the appl is not responding:
so i enabled the logcat, and i was able to see in it that the appl is hanging when it tries to load the streaming library...
Could yoy help me?
I can send you all the data you need to debug the appl..
or, if not possible to fix it, could you suggest me an alternative frame grabber application/usb dongle that can work with my devices?
Thank you!!
Lodovico
Hi,
Thanks for using XDA Assist Not all apps are universally compatible So apps support only certain set of devices whose Specifications match with application and hence for your devices its not supporting
Thank you
I know that sometime, with some simple fix to an application, it can work for a broader range of devices...
Or, sometimes, the issue can be solved with an upgrade to the os of the device ... (for example, i could try to upgrade my Acer A500 to the 4.4 Omnirom and see what happens...)
Perhaps the developer has stopped working on this application, but with some simple fix it could work also with my devices
Are you sure that this is not the case?
By the way, i faced a problem like this with an other application, the IrDroid, (available for free on the Play Store)
It didn't work with my Sony tv, but then i was able to find the sources (it was open source), debug them ( i installed the SDK on my pc), do a simple fix, compile them, and get an IrDroid app that now works also with my Sony tv , flawlessly...
The easycap is not open source, but i found some russian language forums, where there is an active thread about the easycap application,and applications like it (example... carcam) ...perhaps there some program sources are available...
Any suggestion?
Thanks!
Thread Closed .
Good evening,
After weeks of troubleshooting and searching I ended up here hoping to find a specialist who can help me out.
This is a very special case,
I got an intel FT410 Tablet PC from ebay.
I repaired the charging controller circuit and now it works. The thing is, this tablet does actually not even exist. It has never been sold anywhere. What I got here is an original intel engineering example especially manufactured for development. It has 6 different modems in it, 2 sim trays, 2 usb ports (usb c and usb a mini) and a debugging connector at the back. It's equipped with an intel atom cpu and 2gb ram.
I can enter a special intel bios with more settings you've ever seen in a bios before I can even set the threshold voltage of the battery.
Beside the intel bios i can boot into a fastboot mode like menu. from there i have the option to enter fastboot mode, recovery mode, crash mode and normal boot of course. Recovery mode leads to a black screen as there's no recovery image flashed. no rom flashed as well this thing is empty. I managed to detect it with adb using the common adb driver package. But the adb shell in this tablet is very limited I can not even do a sideload. I can only pull I can't push. I can enter fastbood mode or crash mode which appears to be the same in windows device manager at least. It detects an "Cherry Trail FFD" device. But i can't find any drivers. When I go back into this menu I can adb it. It also shows an "Cherry Trail FFD" device under usb devices in devman. But the fastboot device won't work as I can not find any drivers for it. I tried many, i tried the intel usb driver package. nothing.
I'm losing hope in getting this thing flashed somehow but you are my last chance here otherwise i'll just salvage the flash chips, screen and the battery. But maybe someone has had the same tablet which seems to be unlikely as Google literally knows nothing at all about this tablet 0 informations.
here are some photos attached:
Hello! It sounds like you have a very unique device on your hands. Unfortunately, since it is a development unit and not a consumer device, finding resources and support for it may be difficult.
Based on what you've described, it seems like you may need to find and install the appropriate drivers for the "Cherry Trail FFD" device in order to use fastboot. You mentioned that you have tried many drivers already, but have you tried contacting Intel support directly? They may be able to provide you with the necessary drivers or offer other assistance.
Additionally, you may want to try posting on forums or discussion boards focused on development or hacking of Intel-based devices. You may find other individuals who have experience with similar devices or who can offer guidance on how to proceed.
Good luck with your device!
Joe L. Thompson's said:
Hello! It sounds like you have a very unique device on your hands. Unfortunately, since it is a development unit and not a consumer device, finding resources and support for it may be difficult.
Based on what you've described, it seems like you may need to find and install the appropriate drivers for the "Cherry Trail FFD" device in order to use fastboot. You mentioned that you have tried many drivers already, but have you tried contacting Intel support directly? They may be able to provide you with the necessary drivers or offer other assistance.
Additionally, you may want to try posting on forums or discussion boards focused on development or hacking of Intel-based devices. You may find other individuals who have experience with similar devices or who can offer guidance on how to proceed.
Good luck with your device!
Click to expand...
Click to collapse
I'm not sure if that's a good idea contacting intel. i'm not even sure if this is legal as it says it's intel property and a top secret. And yeah I actually thought xda would be the best place for that topic.