I am compiling an AIR application from Animate CC (mac version) with runtime embedded. No issues on the mac, but when i transfer the app file to a PC (running windows obviously), the app icon displays as a folder instead, and there is nothing within this folder that I can click on to run the app.
I was under the impression that Adobe AIR is cross platform compatible, so am I doing something wrong when compiling, or do I have to compile on a PC to create a runtime embedded app that will run on Windows?
It's impossible to launch Mac app on Windows. Because embed runtimes are different for Win/Mac. Here you can get some more info https://superuser.com/questions/56739/executable-files-in-mac-os-x-vs-windows.
So you either build 'Mac projector' and run it on Mac or 'Windows projector' to run on Windows (you can change this option in File -> Publish Settings). Tick both options and you'll be able to run it on Win and Mac.
One more option is to build AIR app - but it will require AIR runtime installed.
You're correct that Adobe AIR is cross platform compatible, but publishing from a Mac doesn't give you a Windows-runnable app, nor does publishing from Windows give you a Mac-runnable app.
You'll need to compile on a PC to get a Windows-runnable .exe
I want to use usb wifi adapter in custom android board, so far I was able to build driver for chipset, and android is able to detect the dongle, and even creates wlan0. But I don't how to load firmware as there is one bin file. When I am trying to do netcfg wlan0 up, then I am getting following error Request firmware failed with error 0xfffffffe.
So I need help, that to know how android includes that firmware in build.
Regards,
Yuvi
I found that firmware should be copied at /system/etc/firmware/, reference this link
a simple copy command can be added in build script, to copy firmware before creating image.
The path to wifi firmware in android devices is generally:
\system\etc\firmware\wifi
Some devices have system\etc\wifi or \system\etc\firware\wlan as the wifi firmware path. If you connect through adb and do ls to one of these paths, you should be able to see firmware binary. For Qualcomm wifi, the binary has wcnss string in it.
As for your actual question, the firmware loading is done by the wifi driver. So if you are enable wifi through adb shell or through phone UI, it should load the wifi driver which should load the wifi firmware from the location mentioned above
Ever since I upgraded my Samsung Galaxy S3 to android 4.3 (from 4.1.2) I am unable to use Chrome's remote debugging for android (more details here).
I have the developer options and USB debugging enabled on my phone, and this worked perfectly fine on android 4.1.2.
Now, when I connect my phone to my PC, it simply connects as a media storage device and is not discovered as a USB device by chrome.
I am ruling out any problems with chrome as I could USB debug with a Google Nexus4, also, looking at some other thread (here and elsewhere) it seems to be a problem with Samsung's 4.3 upgrade.
Any pointers to get this working?
My devices stopped working as Chrome de-activated the now depracated ADB plugin as it's built in dev-tools now.
I downloaded the SDK and followed the instructions at Chrome Developers. How ever I found the instructions served by Alphonso out not to be sufficient and I did it this way on Windows 8:
Download Android SDK here ("SDK Tools Only" section) and unzip the content.
Run SDK Manager.exe and install Android SDK platform tools
Open up the Command prompt (simply by pressing the windows button and type in cmd.exe)
Enter the path with ex:
cd c:/downloads/sdk/platform-tools
Open ADB by typing in adb.exe
Run the following command by typing it and pressing enter:
adb devices
Check if you get the prompt on your device, if you still can't see your phone in Inspect Devices run the following commands one by one (excluding the ")
"adb kill-server"
"adb start-server"
"adb devices"
I had major problems and managed to get it working with these steps. If you still have problems, google the guide Remote Debugging on Android with Chrome and check for the part about drivers. I had problems with my Samsung Galaxy Nexus that needed special drivers to be compatiable with ADB.
Update
If you are using Windows 10 and couldn't find the link to download Android SDK; you may skip #1 and #2. All you need is activate "Android Debug Bridge". Go straight to #3 - #7 after download and execute "platform-tools"(https://developer.android.com/studio/releases/platform-tools.html)
Having attempted to follow Valros.nu's answer, i discovered that the sdk download is now bundeled with androind studio, in an 840MB exe installer.
As all you need for this particular program is the adb program, you can get this in a standalone installer from the xda guys:
http://forum.xda-developers.com/showthread.php?t=2317790
Note that you do not need to type adb.exe, simply type adb devices into the command prompt that is launched after install.
Also, i had to unplug and replug in my samsung s4 to get the remote debugging prompt to appear on the phone
After looking around a little longer I came across this. Apparently, there isn't a solution to this issue yet, but there is a workaround - going back to the legacy workflow.
The legacy workflow did work for me, and the only additional thing I had to do was to go to the platform-tools folder from android SDK download, open a command window here and run command "adb devices".
This caused the computer RSA key fingerprint panel to pop on my mobile screen, and after granting permission, the device showed up under Chrome's Inspect page.
Turns out that it was not an issue caused by mobile OS upgrade but by Chrome (I was thrown off by the fact that it worked on my Nexus4 somehow).
In the older versions of Chrome there was't a need to download the 500 odd mb Android SDK, as it supported an ADB plugin. But with latest version of Chrome, I guess, going legacy is the only way to go.
I have Samsung Galaxy S3 and it was not showing in the "Remote devices" tab nor in chrome://inspect.
The device did show in Windows's Device Manager as GT-I9300, though.
What worked for me was:
Plug the mobile phone to the front USB port
On my phone, click the notification about successful connection
Make sure the connection type is Camera (PTP)
On my Windows machine, download installer from https://github.com/koush/UniversalAdbDriver
Run it :)
Open cmd.exe
cd "C:\Program Files (x86)\ClockworkMod\Universal Adb Driver"
adb devices
Open Chrome in both mobile phone and Windows machine
On Windows's machine navigate to chrome://inspect - there, after a while you should see the target phone :)
I'm not sure if it affected the whole flow somehow, but at some point I've installed, and later uninstalled the drivers from Samsung: http://www.samsung.com/us/support/downloads/ > Mobile > Phones > Galaxy S > S III > Unlocked > http://www.samsung.com/us/support/owners/product/galaxy-s-iii-unlocked#downloads
For me the solution was to download the Android SDK and launch adb devices which started the adb daemon.
I know this is an older question, but I thought I would also post my solution:
Update your Chrome on your phone and on your PC.
Even if it says you have the latest driver for your device inside
Device Manager, you may need an alternative. Google latest Samsung drivers and try updating your drivers.
I had success after using ade.exe as explained above, plus using the latest version of Chrome Canary. Apparently your desktop version of Chrome has to be higher than the version running on your Android device.
For me, the menu item Inspect Devices wasn't available (not shown at all). But, simply browsing to chrome://inspect/#devices showed me my device and I was able to use the port forward etc. I have no idea why the menu item is not displayed.
Phone: Android Galaxy S4
OS: Mac OS X
In case it helps anyone I will post what worked for me.
I had to plug my S3 into a direct USB port of my PC for it to prompt me to accept the RSA signature. I had my S3 plugged into a hub before then.
Now the S3 is detected when using both the direct USB port of the PC and via the hub.
NOTE - You may need to also run adb devices from the command line to get your S3 to re-request permission.
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
9283759342847566 unauthorized
...accept signature on phone...
D:\apps\android-sdk-windows\platform-tools>adb devices
List of devices attached
9283759342847566 device
Those who updated their device to Android 4.2 Jelly Bean or higher or
having a 4.2 JB or higher android powered device, will not found the
Developers Options in Settings menu. The Developers Options hide by
default on 4.2 jelly bean and later android versions. Follow the below
steps to Unhide Developers Options.
Go to Settings>>About (On most Android Smartphone and tablet)
OR
Go to Settings>> More/General tab>> About (On Samsung Galaxy S3,
Galaxy S4, Galaxy Note 8.0, Galaxy Tab 3 and other galaxy
Smartphone and tablet having Android 4.2/4.3 Jelly Bean)
OR
Go to Settings>> General>> About (On Samsung Galaxy Note 2,
Galaxy Note 3 and some other Galaxy devices having Android 4.3 Jelly
Bean or 4.4 KitKat)
OR
Go to Settings> About> Software Information> More (On HTC One or
other HTC devices having Android 4.2 Jelly Bean or higher)
2. Now Scroll onto Build Number and tap it 7 times repeatedly. A message will appear saying that u are now a developer.
Just return to the previous menu to see developer option.
Credit to www.androidofficer.com
I'm attempting to run the example project for this Adobe Native Extension 'SongPickerANE' from Flash Builder on Windows onto an iOS device. I've run it successfully on the same device (and iOS Simulator) from Flash Builder on my Mac with AIR SDK 3.4, but it failed to run with 3.4 on Windows, as it couldn't get access to the required iOS SDK (6.1).
So, I've updated my AIR SDK on my windows machine, first to 3.5, and now to the current version 3.9, which seemed to sort out the iOS SDK issues I was having, but both failed to run with the following error:
java.lang.Exception:
Undefined symbols for architecture armv7:
"_objc_setProperty_nonatomic", referenced from:
-[SongPickerHelper setPickedItem:] in libcom.newpixel.air.nativeextensions.SongPicker.a(SongPickerHelper.o)
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
From what I remember of it in the dim, distant past of my iOS development, this is some sort of XCode linking / Build Settings / Phases error? So to fix it, will I have to edit and recompile the ANE, or is there anything I can set in the Flash Builder project which uses the ANE to fix it?
If it requires recompiling the ANE, any tips / advice on where to start would be appreciated, as I've so far managed to avoid having anything to do with them, and I do find them slightly terrifying.
Many thanks in advance.
I've made an AIR app with Flash Builder 4. Works great but I want to run the app without installing it. So..... when I install the app, I copy the files from program files and paste it on a CD and give it to somebody. He runs it on another computer without AIR runtime with as result that it doesn't work.
How can I bypass this? Like some launcher/setup that installs AIR runtime for the client if it aint installed. If it is installed, run the AIR app.
Thanks.
Creating an AIR Badge would be a good option.
The idea is you pass a link to the client, the AIR Badge check if
AIR is installed. If it is, installs your app, otherwise installs AIR
first.
There's a pretty good AIR Badger tutorial on the Adobe Developer Connection site. AIR Badger is an AIR App Grant Skinner wrote to make the setup easier.
Also check out the new AIR Launchpad, which is another AIR app that helps you get started with all sort of AIR related functions, including install badge.
Unfortunately the AIR Badger works online.
You cannot bypass AIR install. Maybe have a third party utility(batch script/etc.) that looks for air related files/.air filetype associations and based on that launches an AIR installer you supply on CD or the app itself.
On osx you have the mdls command that displays information about a file. You could check for kMDItemKind:
mdls -name kMDItemKind /path/to/yourApp.air
If it prints "com.adobe.air.InstallerPackage", then air should be installed, otherwise it will just print "Document".
There should be something similar for windows command prompt that checks registry file type associations.
After you've done that check, install AIR first or just the app, depending on the result.
HTH