What resources are required to run Flash on Android? - android

I have HTC T-Mobile device having Android OS 1.6, Eclair platform. I doubt if Flash Adobe Air can run on that. Because that is the only supported on 2.1 and 2.2. Please confirm.
Also can i upgrade my device's OS to Froyo by downloading the OS from android.source.com?
I have downloaded SDK 2.1 and 2.2 on my machine. Can i develop and run flash games on the AVD/emulator?
Please comment and reply precisely to the aforementioned questions. Thank you

The implementation of Flash from Adobe won't work on anything prior to 2.2. That is more to do with Adobe targeting that version rather than flash being something that Android 1.5/1.6 intrinsically cannot do.
There have been flash players on Android before, I understand that HTC used to bundle flash capability with the HTC Hero.
You can certainly download 2.2 from source and build it for your device but you must have two things prior to doing that:
root access to your device
proprietary drivers for your device that will work with that android build
If you have a G1, then you are in luck because the cyanogen mod can be installed on a G1 plus they will be porting 2.2 to it (along with the Nexus One and a few others)

Related

Android Device Connectivity in Adobe Flash Pro CS6 Win7 x64

I'm using a Samsung Galaxy S3 running Android 4.3. I've installed the latest Samsung Kies as well as the Android SDK. I'm able to run the Android SDK in Eclipse and properly compile/run/debug applications via Eclipse, but I cannot seem to get it working with Adobe Flash CS6 - it compiles the SWF and hangs on the "Publishing..." progress bar.
AIR 3.2 for Android Settings are correct, and when I compile the SWF to an APK file and then move the file over to the phone via File Manager I am able to install and run applications successfully. I can't, however, publish directly to the phone or debug on the device over USB.
I've definitely done my research and have been through all the normal stuff like USB debugging and all that. Everything works great in Eclipse with the Android SDK - just not in Adobe Flash Pro CS6. I've read in this thread that others simply have not been able to do it either with Samsung devices running Android 4.2.2+ Can anyone shed some definitive light on this issue?
UPDATE: I got it to work! I had to copy the adb.exe file from the Android SDK to the one being used by Adobe Flash Pro CS6. I'm working on turning my experience into a blog post with pictures and step-by-step instructions and I will elaborate on every step of the process. Stay tuned...

Testing Android Apps on a 4.0.3 device with 2.2 and 4.1 sdks installed

So I've been playing around with the Virtual Devices for a while working on a few Android Apps. I have the 2.2 and 4.1 SDKs installed on the computer like is suggested by the developers website (this incorporates most of the phones around today).
Recently I purchased an Android phone, the HTC One XL running Android 4.0.3, and in trying to run my apps through it, the system is not finding the device.
I fiddled around a bit searching for the device but it says that it is searching for 4.1 devices in the Android Device chooser.
The phone is in debugging mode, and as far as I can tell, the most up to date driver is installed.
So, is there a way to tell Eclipse to look for devices with lower OS's or should I uninstall the 4.1 kit and put on the 4.0.3? Or is there a better option?

apk fails to run on some devices

I have a quick question. I have built an app in Corona SDK (Version 2012.878). My app works fine on my Galaxy S. But it fails to install on HTC Wildfire S.
Is it because of CPU? Are there some other reasons? Is there a way to know, on which devices app will fail to install?
Thank you
The HTC Wildfire has an ARMv6 processor. You need a device with ARMv7 or later for Corona apps to install. There is a very old version of Corona SDK that supports ARMv6, but it's not supported anymore and I don't think it's that easy to get your hands on either.

Downgrade Samsung Galaxy Tab from Android v3.1 to v2.3.3 Gingerbread

I am new developer of Android's tablet, if I buy a Samsung Galaxy Tab 10.1-inch with Android 3.1 installed, can I downgrade it back to version 2.3.3 Gingerbread??
Since I want to test my apps running on v2.3.3
Any possible problems for doing this?
This may be possible, if you can find a ROM built for the 10.1 Tab which is running 2.3.3
I would advise you check out XDA-Developers and see what ROMs that have available. You will need to wipe your device though, so backup any data you may have on it. Also, you will need to Root your device, which will be explain on the XDA forums.

Which android devices support the ADK / open accessory

Is there a list anywhere of which Android devices (phones, tablets) support the ADK / accessory mode? From what I have read, I known that the Nexus One, Nexus S and Xoom do support it. Are there any other devices (custom ROMs included) that also support it? I have an ADK and can't get it working with my phone, I am basically looking for the cheapest phone that I can use with ADK.
** UPDATE ** I found this list of tablets that work with the ADK
The offical Android 2.3.4 is based on the kernel 2.6.35, ADK need kernel 2.6.35. Some Android 2.3.4+ do not support adk because the kernel is not 2.6.35+. I used to copy the adk need jar into my milestone (Android 2.3.5, kernel 2.6.32, cm7), and install the DemoKit.apk but it doesn't work.
The phone I know ADK works: Nexus One, Nexus S, HTC Desire(need to do something to make it work)
I think if the phone have kernel 2.6.35+ and android 2.3.4+ it will support ADK too, but I can't find a 2.6.35+ kernel for my Milestone.
When I was digging around in the CyanogenMod 7.1 kernel sources for my Galaxy S2 I found that the USB accessory driver missing from kernel 2.6.35.7 (I think the kernel .config flag is CONFIG_USB_ANDROID_ACCESSORY).
From what I've found by a lot of searching and forum digging was that the accessory driver was implemented in Honeycomb (3.x) but backported to Gingerbread (2.3), and should be available from kernel 2.6.35.15. I made a few unsuccessful attempts to compile my own kernel, with the plan to cherry pick the driver but for some reason I was not able to make the phone boot with my custom kernel.
I am now running an early experimental CyanogenMod 9 ICS (4.0.3) build on my SGS2 and it is possible to have the phone talk with my Arduino board. I made the phone able to toggle an LED on the board so I guess it is time to start working on my plans for world domination.
In theory, any device running Android 2.3.4+ or 3.1+ should be compatible with the ADK (as long as they have a USB port). I don't think any manufacturers remove the ADK from their builds (I don't see why they would), but it's not impossible either.
So, you either update your phone to 2.3.4 (if it's possible), buy a phone that runs 2.3.4+ (the minor version is important -- 2.3.3 does not have the ADK) or buy a tablet that runs 3.1+.
If you're going to buy a phone, I recommend a Google-branded phone, such as the Nexus S.
Known good: Nexus S (not 4G) running ICS 4.0.4.
ICS 4.0.3 is known not to work. Don't know anything about 2.3.x.

Categories

Resources