Appcelerator, Android Emulator Build Speed Suggestions - android-emulator

So, attempting to figure out if there was a way to use the arguments in the runtime config I ran across my biggest runtime boast yet, calling the Appcelerator build script for the Android Emulator from the command-line, here's what I mean:
<full-path-to-python.exe> <full-path-2-.../android/builder.py> emulator <project-name> <android-sdk> <project-dir> <project-id> <avd-name>
Example:
"C:\Program Files\Appcelerator\Titanium Studio\plugins\com.appcelerator.titanium.python.win32_1.0.0.1331647813\python\python.exe" "C:\Documents and Settings\user\Application Data\Titanium\mobilesdk\win32\2.0.1.GA2\android\builder.py" emulator JavaHomeBug "C:\Program Files\Android\android-sdk" "C:\Documents and Settings\username\My Documents\Titanium Studio Workspace\JavaHomeBug" tld.domain.JavaHomeBug titanium_1_HVGA
Are there any other ways to get the emulator to load faster, including but not limited not executing anything but the app?

This might not be exactly what your looking for but helps a lot with making changes and viewing them in the emulator.
Appcelerator implemented a festDev server. meaning that you can launch an app in the android emulator and leave it open, as you make changes to the code travel back through pages to make the page be reloaded and the new code will be pulled in.
For example going page 1 -> page 2,
then making a change on page 2,
click back button to go to page 1, now when go to page 2 you'll see your changes.
Takes a hige amount of time off waiting for the emulator to load up each time you change 1 or 2 lines

Related

Disable Serial Console on an Android Emulator

I've been learning and working with Flutter for a few weeks now. I used some of the Android Emulators that Android Studio provides and it was doing fine.
But recently, I opened an emulator to run a Flutter project while a memory card was connected with my laptop, and suddenly a notification was shown in the emulator of detecting a SD card and with that another notification was shown saying:
Serial console enabled
Performance is impacted. To disable, check bootloader
The notification is not clickable, and neither it removes even after I deleted all the emulators that I installed using the AVD manager. And as the notification says, it really is impacting the performance of the emulators. Before it showed up, I could see the changes in the app immediately after making changes to the code and saving it, but now, it takes so much time to show the changes even if I use hot reload or hot restart.
Is there any way to get rid of this? How can I disable the Serial console?
Enter engineer mode (*#801#) and disable the option that says serial. Google it how to access engineer mode if the code doesn't work for you.

Can one still install hololens 1st gen emulator?

Hi I was trying to install the hololens 1st gen emulator off of the official website but the download link doesn't work, I am wondering if it just me or is the download link actually broken? I tried with the microsoft archive for the previous releases for the emulators as well but none of the 1st gen ones work
The link: https://learn.microsoft.com/en-us/windows/mixed-reality/develop/install-the-tools?tabs=unity
We have reproduced this issue with some third-party browsers. The actual behavior is the browser pops up a new tab and closes immediately without any download task starts.
For now, it is recommended that you use the Edge browser, after checking it can work fine on this link. Or, the workaround for some third-party browsers is to right-click the emulator download link and select copy address link, then paste it into the address bar.

Why would my side-loaded Windows Store app go no further than the splash screen?

I have a Windows Store App that, of course, runs fine on my dev machine.
After creating the package to side load for testing, I installed it on another (desktop) machine. Using the instructions for side-loading contained on pages 25 and 26 of Brundritt's free ebook "Location Intelligence for Windows Store Apps", my app seems to install just fine, except that the app is not added to the Windows 8.1 start screen at the end, as expected.
Nevertheless, I can find the app via the Search functionality - I type the name, it shows up in the "found" list (with its logo), but when I try to run it, the splash screen simply "flashes" and then the app disappears. It icon is indeed parked on the taskbar, and every time I click it, the splash screen flashes, but that's all.
This is a Windows 8.1 app that contains a Bing Map, SQLite (and sqlite-net), as well as ExifLib.
It does show up in Task Manager's "App History" tab.
How can I rectify this problem, or at least determine what the problem might be?
UPDATE
This may (or may not be) significant: the version of the app I sideloaded was built in debug mode. Do I need to build in release mode for this to work?
Also: After building in release mode (for the first time) on the dev machine, it no longer finds the SQLite data that had formerly existed. Does changing from debug to release change the path to the database or something?
Does this help? http://blogs.msdn.com/b/vcblog/archive/2012/09/28/10354327.aspx It appears that the app needs to be built in release mode to work properly.

What does it look like on the device when you build and run Android yourself?

I just followed the instructions on source.android.com for building Android from source. The build appeared to succeed, and it generated .img files which I fastbooted onto a device.
I started up the device, and got a black screen.
I can "adb shell" into the device and cd around and stuff, but nothing shows on the screen.
Usually, a black screen tells me something is wrong, but it's crossed my mind that maybe this time it's actually right, and the Android version one builds from source is a slim version without any of the bells and whistles, desktop with apps, browser, settings etc like the Android you get when you buy a phone.
My question: What normally shows on the screen when you build and run Android from source?

Workflow for debugging PhoneGap using Safari's Web Inspector

I'm developing a phone gap app and using Safari's Web Inspector to debug it. The tool is very useful but there are a couple workflow inefficiencies that are costing me some time.
Every time I stop my PhoneGap app in xCode the Safari Web Inspector window automatically closes leaving me with the task of re-opening it every time I make a change and re-launch the app.
The only way I'm able to get a full read out in the console is by entering window.location.reload(). Again this adds a step to my work flow everytime I deploy a change in xCode.
Does anyone know how to set it up so that Safari Web Inspector stays open and the console automatically monitors the app?
To solve the reload issue, I add this in my head section when I'm debugging:
<script>
alert('connect your debugger, if you want')
</script>
The alert stops all execution, meaning that I can (manually, ugh) connect my debugger and not miss anything. Execution resumes when I hit okay on the alert window.
I'm having the same issues. I haven't solved them yet, and I'm running out of time, so I'll show you what I've got so far:
Create an ActionScript that opens the web inspector:
https://gist.github.com/amuino/5649177 This works!
Have Xcode launch it! I tried creating a shell script that, in turn, opens the action script, but to no avail. This is what I've got:
How to run a script after Xcode runs codesign on my iPhone app?
Actually I found a way around this issue. It's not super elegant but it works.
At the entry point of my app I added some delay with setTimeout, like this:
setTimeout(function () {
app.init();
}, 10000);
This will give you enough time (10 seconds) to reopen Safari Web Inspector and you will get full console read out.
It saved me a lot of headache.