wince wec7 usb debug android - MTCB Android Head Units Q&A

Hello, do you have the option to add a feature to the registry of windows to allow android debug usb?
I have a lg oem based navigator based on wec7 and wanted to use carbit mirrolink. Only when launching carbit can not debug the phone. thank you

Related

How to Debug PPC 2003 with eMbedded Visual C++ 3.0

Hi,
I use eMbedded Visual C++ 3.0 and develop a application for Pocket PC 2002.
Now I want to debug my applikation on an iPAQ with Pocket PC 2003.
But eMbedded Visual C++ 3.0 has a problem while connecting to that device: "The Platform Manager Server failed".
What must I do to be able to debug PPC 2003?
Thanks for all solutions !!!
Have a nice day!
Franz
use evc4++
Hi,
thanks for your reply.
Is the migration from evc 3.0 to 4.0 smooth or painfull ?
don't know yet.
there are issues with having both compilers installed, I think in some cases
you have to reinstall evc3 to get it to work again.
I use eVC+3
I have no problems with eVC+3
I installed PPC2003SDK
and since this time I can debug for PPC2003 devices too, and connect via PlatformManager too.
btw: I have VS#NET installed in this same partition. Dont know if it changes anything.

anyone have eMbedded visual basic software,please

i need the software to run some program if anyone can send that or any links to download thanks
Hi,
The SDK for Pocket PC is actually available for free at Microsoft!
You just have to search a little for it: use "Pocket PC SDK 2002" as keywords at www.microsoft.com, or try this direct link:
http://www.microsoft.com/downloads/...4a-bd94-4167-b817-2b2e548b2e92&DisplayLang=en
The SDK for Pocket PC 2003 only includes VC++ 4.0, but the SDK for Pocket PC 2002 contains both VCC++ 3.0 and Visual Basic CE 3.0.
For VB Apps to run, you need to install the VBRUN-Runtime library on the PDA.
Be aware that embedded VB has some severe drawbacks, compared to VB6:
- you don't have the DoEvent command, so no "multitasking"
- you don't have VAR() and VAL()
- you don't have many of the controls
- it is VERY slow
More info's about it:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbceide/htm/evbstart.asp
Cheers,
vma
VBRuntime.cab
VBRuntime.cab
Note that it is better to write your apps in Visual C++ rather than VB, as VB will not be supported on future devices...
eMbedded Visual Basic can run on WM 2003, just use the following link to download the runtime library from the following link:
http://msdn.microsoft.com/mobility/windowsmobile/downloads/evb_eula.aspx
This will allow any applications written using eVB 3 to run on your device!

MissingMethodException on PPC2003 C# program

I have been working with VC# 2005 and the WM5.0 and 6.0 SDKs. However, recently I decided to try to run my programs on a PPC2003 device, since nothing in my code should prevent me from doing so..
However, I seem to have run into some problem that might be beyond my understanding of how the different versions of WinCE relate. My programs run on a WiMo 6.1 device with no problems. When I simply tried to run the software built with the 5.0 SDK on a PPC2k3, I got a MissingMethodException for a function that was in a C# dll that was in the project directory. I thought that it may have to do with some fancy new 5.0 functionality so I created a ppc2k3 project, but the problem did not go away. I was able to get rid of it by just including the files from the dll in the main project (which I would prefer not to do). This brought me to an even sillier exception: "Could not load type 'System.Collections.Generic.LinkedList' 1' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=...'"
The device has CF2.0 installed and as far as I know, Linked Lists should be supported without any issues. Does anyone know what I might be doing wrong?
A WinMo 2003 device by default only has .NET CF 1.0 or 1.1 (WM2003SE) installed on it by default. Unless it has the .NET 2.0 framework installed on it, that could be the problem.
To find the version(s) on .NET CF installed run \Windows\CGACUTIL.EXE It may be a hidden file on your device. Depends on the OEM.
Check whether the method you are calling exists in .NET CF 1.1
It may not, exist or have a different overloaded type, check the parameters. If you modify your app to use the methods/properties only available in CF 1.0/1.1, it should work.
Thank you for your reply! I did install CF2 (and I think it gets automatically deployed if it's not installed anyway). The version I get from cgacutil is [2.0.6129.0, 1.0.3111.0].
This does seem to be something other than a compact framework issue though, since I got a similar error while trying to use a function from a dll that I built from source. Are there some build flags or anything that should be set on a PPC2K3 application that are unnecessary on later versions?
Not that I am aware of.
The versions installed on your device are 2.0 and 1.0, the third number is the build version.
You have to use some debug code in your app to get to the bottom of it.
Have a look at:-
http://msdn.microsoft.com/enus/library/system.missingmethodexception.aspx

[Q] Native code problem in WP7

I try to call native dll from WP7 SDK but it say that dll must build with windows phone SDK which disable unsafe code.
How can I make my native dll and use it into windoes phone 7 app ?

Bada USB-OTG

please bada usb-otg driver write stune or fw install pleaseeeeeeeeeeeee
device support
bada usb-otg not supporting pleaseeeeeee write driver
or bada 2.0 support pleeaseeeeeeeeeeeeeeeeee
it need driver support ..I had diy a cable ,and it doesn't work
BADA, API would need to be built into it
BADA is just a platform which any OS can ride on like Linux, Unix etc it isnt the OS itself.
So even if for example you put in a Linux OS that supports USB OTG on top of BADA, if BADA doesnt have the API to support USB OTG then USB OTG will still not
work.
Samsung has to bake a USB OTG API into BADA itself to allow it and is not dependent on the third party developers but samsungs bada developer team.
This means working on the bada source code itself.
>> BADA is just a platform which any OS can ride on like Linux, Unix etc it isnt the OS itself.
It's exactly the other way round: Bada is the OS, Linux, BSD & Co. is the *kernel*. In real-life (read: Wave devices), BSD is used.

Categories

Resources