I am new to WinCE.
I am trying to build an WinCE 6.0 Image using platform builder.
So I went Like this .
Visual Studio 2005 >> Platform Builder >> OS Design
Avilable BSP : CEPC X86
Custom Device
Actice sync and Cab File Insaller and
Finished.
Build >> Build OSDesign .
Make Runtime image .
In Device's I choose "Windows CE device " and in Device option
Kernal Service Map >> Device Emulator
Debugger >> KdStub
Now After building and creating image when I click Attach devive , it comes up and shows me
a Black screen. Not sure what mistake I am doing .
Packages I Installed :
Visual Studio 2005
Visual Studio 2005 Service Pack 1
Visual Studio 2005 Service Pack 1 Update for Windows Vista (if
applicable)
Windows Embedded CE 6.0 Platform Builder
Windows Embedded CE 6.0 SP1 (required if PB 6.0 Tools have been
installed)
Windows Embedded CE 6.0 R2
Windows Embedded CE 6.0 R3
Windows Embedded CE 6.0 Cumulative Product Update Rollup Package
(through 12/31/2010)
Windows Embedded CE 6.0 Monthly update August
I think you haven't selected properly the BSP, currently I am using WinCE 7.0, but from what I remember you should select a BSP called: Device Emulator: ARMV4 - something similar should be for a x86 - CEPC design. For example on WinCE 7.0 you have a BSP called VCEPC - Virtual CEPC that can be loaded in Virtual PC. The reason is that you have different drivers, different bootloader, etc.
I have a similar problem that is not solved yet but searching a documentation around you can check if the KITL option in the project properties is ENABLED.
If it is then please try disabling it, rebuild the project and make new run-time image.
I hope this helps you.
My problem is listed here: Black screen after booting WinCE 6.0
Since solving the same problem I agree with Patrik. In my case it was the KITL Option. After I disabled this option, my composed image continued booting. This MS article helped me out of the problem:
http://msdn.microsoft.com/en-us/library/aa289160(v=vs.71).aspx#grfvsdtroubleshooting
Section "Emulator generated by Platform Builder boots with black screen"
Short:
1. Start Platform Builder with your composed Platform
2. Select "Platform" on the menu bar.
3. Now click subitem "Settings"
4. Select the "Build Options" tab
5. Uncheck "Enable KITL (no IMGNOKITL=1)"
Related
I've upgraded to the M1 chip 2020 Macbook Air from a 7th gen. Intel chip pc. Overall, I'm very happy and content with it but when it comes to Android Studio performance, which I use quite often, it is very disappointing I'm sorry to say. When will an Apple Silicon compatible version be available? Are any of you guys have any clue?
I had the exact problem and the solution was as follows:
Open Android Studio, go to Help -> Edit Custom VM Options and add the following lines:
-Dsun.java2d.opengl=true
-Dsun.java2d.opengl.fbobject=false
Restart the IDE and wait for the files to sync. Done, IDE running smooth again.
Starting from Android Studio Artic Fox version, they not only changed versioning number style (replaced number system with Year-styling Version names), but also introduced Android Studio for M1/Apple Silicon (arm arch 64bits).
To check if you'r using right Android Studio for your M1, click on 'About Android Studio' and check the runtime, it should show as aarch64 (ie. Arm architecture 64bits). If not, mostly you might be having x86_64 if you installed regular Mac's Android Studio.
To switch to M1's Android Studio,
first exit already installed Android Studio, if it's open.
Go to Finder and under 'Applications', rename 'Android Studio' to preferably 'Android Studio_x86_64'.
Go to Android Studio downloads page (https://developer.android.com/studio#downloads), and download the one tagged as 'Mac (64-bit, ARM)' and unzip and move to 'Applications'.
Click to open 'Android Studio' from the Finder/Applications. You may drag and add it as a Dock shortcut option.
Good thing is that there is no extra installation required and the existing project, (at least for me), opened without any issues.
Android-SDK based and Flutter projects should be good right after switch, NDK not yet there.
AS is now faster again as you are using it as intended on Apple M1's chipset. !
Now Android Studio Bumblebee (2021.1.1) is available in Stable Channel. If your version is older than Bumblebee, download it for more performance.
I find out that the link shown by default is for intel architectures.
Automatic update performed by android studio also downloads the intel version even if this download occurs on a Mac with an ARM architecture (M1) .
You should navigate to the download options and choose ARM architecture manually.
You can download version 2021.1.1.22 Bumblebee for MAC ARM (M1) here (Link updated on Mar 7 2022 )
Check Android Studio Arctic Fox (2020.3.1) Beta 3 (have apple silicon support)
https://developer.android.com/studio/archive
use Intellij CE the latest version released on April 6th has native support for m1 and its very fast and intuitive, i've been using it and it's not very different from android studio
Edit: September 21
Download m1 native supported Android studio through https://developer.android.com/studio/archive
Download Mac (Apple silicon)
All the above did not work and my emulator was completely unusable but in my case the following fixed my issues:
Android studio Preferences > Tools > Emulator
Make sure 'Launch in a tool window' is checked
'Wipe Data' on emulator and then relaunch
Having the emulator launch as a separate window caused a huge slowdown but this fixed it immediately
Extended control settings/options are missing in this update? like sending sms, gps settings unable to find the settings any help appreciated.
To see the additional options you need to run the Emulator in a separate window (process).
To do so go to File...Settings... and then choose the following.
You'll need to uncheck the Launch in a tool window option.
After you do that and restart Android Studio and start your emulator, it will run in a separate window and you'll see the options you want on the ellipse menu item on the side of the emulator.
Here's my Android Studio version info:
Android Studio 4.1
Build #AI-201.8743.12.41.6858069, built on September 23, 2020 Runtime
version: 1.8.0_242-release-1644-b3-6222593 amd64 VM: OpenJDK 64-Bit
Server VM by JetBrains s.r.o
Linux 5.4.0-52-generic
Current Desktop: ubuntu:GNOME
Edit: September 2021
Now, since Android Studio Arctic Fox (2020.3.1) you can enable that in settings:
And you have it there:
Old answer
TL;DR
Currently, you can't use
Why
Base on documentation:
https://developer.android.com/studio/run/emulator#limitations
Limitations
Currently, you can't use the emulator's extended controls when it's running in a tool window. If your development workflow depends heavily on the extended controls, continue to use the Android Emulator as a standalone application. In addition, certain virtual devices—such as Android TV and foldable devices—can't be run in Android Studio because they have specialized UI requirements or important functions in the extended controls.
After hours of struggling, I finally started my emulator using terminal-command and I was able to see the extended controls. Followed this answer, https://stackoverflow.com/a/45201495/6869086
It seems only the VS 2013 Remote tools for ARM works on Windows 8.1.
Does this mean that Visual Studio 2012 is obsolete now for WinRT development?
Update on 25 Nov 2013:
Just saw Moche's answer and was about to post the update. Yes VSE2012 on Win8.0 can now remote debug on Surface2 / Win8.1 using VS2012 Update 4 which was released over the weekend.
Also it is required to download the Remote Tools for Arm that are part of the Update 4:
http://www.microsoft.com/en-au/download/details.aspx?id=39305
Click the 'details drill down' to get the 'Remote Tools' Download
To get remote debugging running, you need to right-click on the project file in Solution Explorer and select debugging under the Configuration tab - then you will notice a field with 'machine name'... complete the machine name of the Surface 2 and select Authentication 'Yes' - Ensure both the Visual Studio Computer and Surface 2 are on the Same Workgroup in Control Panel, System, Advanced System Settings, Computer Name Tab. These brief instruction assume you will be using Windows Private lan authentication. If you want to use your live account for authentication simply google how to Remote Debug Visual Studio 2012 with Windows Live Authentication..
When you run the remote tools installation for the first time on the Surface 2 tablet, you will be prompted by a wizard which sets up the necessary exceptions for the Windows firewall on the tablet.
Actually I succeeded to do the debugging on 8.1 using VS2012. I've installed the latest update 4 of the Debugging Tools. Then I went in Windows Explorer to Program Files->MS Visual Studio 11->Common 7->IDE->Remote Debugger>arm and ran msvsmon from there. That's it - I was able to connect to it from my Windows 8 machine running VS 2012.
Yes, it's indeed obsolete.
For windows 8.1 RT development, set up a separate 8.1 machine with VS 2013.
Update
As of Visual Studio 2012 Update 4, remote debugging to 8.1 seems to be available.
The Answer above that 'Its obsolete' pertaining to VS 2012 and debugging on Win 8.1 is (entirely) not correct - the correct phrase would be that Debugging on Win 8.1 client from a Visual Studio 2012 machine is not supported at time of Win 8.1 preview - Hopefully VS 2012 update will soon allow it to connect to Visual Studio 2013 remote debugger tools to allow Windows 8 development to continue between Windows 8 and Windows 8.1..
As Per:
http://weblogs.asp.net/lduveau/archive/2013/07/10/visual-studio-2012-2013-and-windows-8-1-apps-clarifications.aspx
Quoting:
Visual Studio 2012 (running on either Windows 8 or Windows 8.1) continues to support creating and working with Windows Store apps for Windows 8. It does not support creating or working with Windows Store apps for Windows 8.1. Apps targeting Windows 8 continue to work on Windows 8.1, they just can’t take advantage of all of the new Windows 8.1 functionality and performance improvements.
When I read the Answer above I got my knickers in a real twist and then I thankfully found this (and now have hope my shiny Surface 2 isn't a desk weight for developing) -->
quoting off:
http://social.msdn.microsoft.com/Forums/en-US/3e5bd281-4dde-418b-a9fe-078815523fe1/win-81-surface-remote-debugger
For debugging applications on Windows 8.1 Preview RT devices you need to use VS2013 Professional, Premium, or Ultimate Preview with the Remote Tools for VS2013 Preview.
We are aware that VS2012 is not compatible with Windows 8.1 Preview, and we are working to address this with the next update to VS2012.
Thanks,
Dave Lubash
Visual Studio Team
#Carl L - After further digging.. It seems both our answers are sort of right.. To support Win 8.1 currently, you need Win 8.1 and Visual Studio 2013 installed - I tried Installing Visual Studio 2013 Express on my Windows 8 PC and NO DICE..
I guess the only clarification I am adding is that developers can continue using Windows 8 with Visual Studio 2012 to create apps that run on Windows 8 (only) and will also be available in the Apps Store and run compatibly on Windows 8.1 (but not use all the latest 8.1 optimized features). I am only taking this based on MS forum posts.. The information from Microsoft doesn't properly address this point in its documentation at:
http://www.microsoft.com/visualstudio/eng/products/compatibility-2013
Its also worth pointing out that Visual Studio 2013 Express (free version) is not able to produce Windows 8 Apps - ONLY Windows 8.1 apps (so that part of your answer is correct currently). So in a sense it is unsafe to say Visual Studio 2012 is obsolete as it is currently required to support creation of Windows 8.0 apps.. Unless you don't mind ditching App updates for your existing user-base who may not have yet made the jump to 8.1 (not a sound development model and I am very surprised MS is making fragmentation on its own new platforms for developers currently).
At the moment I am a bit miffed that I am forced to upgrade to Windows 8.1 and VS 2013 in order to debug on my Surface 2 (RT) tablet and in that case would not be able to debug Windows 8.0 apps on my Surface 2 (RT) using VS 2012 until MS hopefully updates VS 2012 and/or the VS 2012 remote debugger tools.
Hope that clarifies a bit - seems you were mostly right which is a real shame if Microsoft is serious about attracting developers to its newest OS and having its free development tools rival that of Android OS and iOS..
It appears that it's no longer possible to debug using VS2012 tools on a Surface RT running 8.1 (see Debugging Surface RT 8.1 from Visual Studio 2012).
So, how can I uninstall it, because it still has icons on the start menu, and items under program files. The digital signature is no longer recognized, so it's not possible to uninstall via the control panel.
Just remove the program files folder of Visual Studio 11.
Then go to your registry keys in HKLM => Software => Microsoft and remove the Remote Debugger entry.
Now you can do a fresh install of the VS2013 remote debugger tools and next time you'll restart the old icon seems to be removed from the all apps screen.
Good luck :)
Yeah good luck with that, we will all need it... As is mentioned in a few places on the web, Win 8.1 and Visual Studio 2013 can develop apps ONLY for Windows 8.1, while Windows 8.0 and Visual Studio 2012 can develop apps ONLY for Windows 8.0... You can install both side-by-side on the same machine (VS 2012 and VS 2013) though.
But what really gets me is that my new surface 2 is now a paperweight because I can no longer debug on it as I don't wish to abandon Windows 8.0 development ATM. I hope Microsoft addresses this as it could become a serious fragmentation issue and keep developers away in droves.
I've already built windows ce 6.0 and run it in windows ce emulator.
but I want to run this without visual studio 2005.
I found emulator for windows ce 5.0, but I couldn't find emulator for windows ce 6.0.
somebody help me, thanks.
So you're saying you have created a CE image that does boot up in the Device Emulator? If that's the case, then you probably just need to install the stand-alone Device Emulator v3 bits (and your image) on the target PC.