In NetBeans 8.1 Profiler API was heavily re-designed and became too Java SE specific. As the result Profiler support for Oracle Java ME SDK is broken. We found a partial "dirty" workaround, but it is not really good.

What is wrong:
Now starting of Profiler always opens ProfilerWindow that belongs to selected project with features that belong to Java SE only and which cannot be disabled or hidden. E.g., for Java ME
 - there is no Methods/Threads/Objects/Telemetry/Locks features, there is only one sampling static (not live) CPU profiler feature that belongs to a project
 - Profiling Points has no sense (both in the ProfilerWindow and in the main Profile menu)
 - Multiple modes are not applicable
 - Two special Java ME profiler features (Network Monitor and Memory Monitor) belongs to a devices where the project is run, but not to a project itself (so ProfilerWindow has no sense for them).

So, what is required to resolve this issue:
1. Provide an ability to start profiler without showing ProfilerWindow (both from main Profile menu and project popup menu). I.e., see ProjectSensitivePerformer.perform method:

    @Override
    public void perform(final Project project) {
        RequestProcessor.getDefault().post(new Runnable() {
            public void run() {
                ProfilerSession session = null;
        
                Lookup projectLookup = project.getLookup();
                if (attach) {
                    Lookup context = new ProxyLookup(projectLookup, Lookups.fixed(project));
                    session = ProfilerSession.forContext(context);
                } else {
                    ActionProvider ap = projectLookup.lookup(ActionProvider.class);
                    if (ap != null) {
                        ProfilerLauncher.Command _command = new ProfilerLauncher.Command(command);
                        Lookup context = new ProxyLookup(projectLookup, Lookups.fixed(project, _command));
                        session = ProfilerSession.forContext(context);
                    }
                }

                if (session != null) {
                    session.setAttach(attach);
                    session.open();
                }
            }
        });
    }

    Instead of this code that opens sessions and eventually ProfilerWindow we need just invoking action provider, e.g. in the following way:

    @Override
    public void perform(final Project project) {
        RequestProcessor.getDefault().post(new Runnable() {
            public void run() {
                final Lookup projectLookup = project.getLookup();
                final ActionProvider ap = projectLookup.lookup(ActionProvider.class);

                if (ap != null) {
                    SwingUtilities.invokeLater(new Runnable() {
                        @Override
                        public void run() {
                            ap.invokeAction(command, new ProxyLookup(projectLookup,
                                    Lookups.fixed(project, new ProfilerLauncher.Command(command))));
                        }
                    });
                }
            }
        });
    }

    What kind of code should be invoked can be determined using some new option from ProjectProfilingSupportProvider

2. Provide an ability to exclude a project from "New Profiling Point" dialog (man menu Profile>Insert Profiling Point...), e.g. basing on some new option from ProjectProfilingSupportProvider