Don't know if this is any use, but I saw this on Android Police and thought I'd post it:
http://www.droid-life.com/2011/01/27/download-honeycomb-sdk-android-3-0-system-dump/
Has anyone been able to port the gmail app fetured in honeycomb?
This is from the "preview" version of the SDK, not even the full SDK that will be released (SDK = Software Developers Kit).
There is no Gmail app or other "Google Apps" included with the SDK's.....I've only seen Maps included.
SDK's are for people to build apps
Source (AOSP) is for people to build the OS
Google Apps are proprietary and aren't available in either the SDK's or source (AOSP).
Related
Hey All,
Not sure if us as the community can email google or someone to push for the release of the honeycomb 3.0. I don't have the right info as to who to email or who to contact but i am sure if enough people will get together and do this we will see honeycomb in no time.
Honeycomb SDK is already released for a few tablets and i would like to see it for our viewsonic Gtab. (so lets speak for it guys)
Let me know if someone has the contact info to contact the correct team this way i can send out the email from my side. I know viewsonic will just tell me that they are waiting for google to release it so i am guessing that our main contact is google but the question is who..
cd112 said:
Hey All,
Honeycomb SDK is already released for a few tablets and i would like to see it for our viewsonic Gtab. (so lets speak for it guys)
Click to expand...
Click to collapse
The "Honeycomb SDK" is just the Software Developers Kit for Honeycomb. It's not for any particular tablet. What has happened is that they include an emulator to run on your PC or Linux box so you can test the apps you build with the SDK to make sure they are working. Some have taken this emulator and hacked it to run on devices that are similar enough to the CPU architecture emulated in the emulator. Definitely not something I'd want to base building an OS off of.......
Google isn't going to release the source code (what you want...not just and SDK) to AOSP (Android Open Source Project) until they feel it is ready.
AOSP and SDK are two different things.
AOSP is the source code that devs use to compile ROMs. This will be helpful.
SDK's are used by app devs to build apps and is already fully available.
Someone needs to post the honeycreams image....
Do you think it is still worth it to develop apps for phones that still have android 1.x? There are some apis that is not available on 1.x and my apps need those APIs. Should I just expect them update their android to 2.x?
Develop Android Apps on Android
with AIDE - the Android Java IDE
AIDE is an integrated development
environment (IDE) for developing real
Android Apps directly on Android
devices. AIDE supports the full edit-
compile-run cycle: write code with the
feature rich editor offering advanced
features like code completion, real-
time error checking, refactoring and
smart code navigation, and run your
App with a single click.
AIDE will turn your Android tablet with
keyboard into a real development box.
We use the Transformer Prime
running Ice Cream Sandwich to code
with AIDE. AIDE will turn your Android
Phone into a small development
computer to browse and touch your
code on the go.
AIDE is fully compatible with Eclipse
projects. You can just copy the
sourcecode to your device and open
the Eclipse project in AIDE to start
coding. Alternatively you can keep
your sourcecode on your Dropbox -
AIDE integrates with Dropbox and
allows to easily download from your
Dropbox and sync back your changes.
DOWNLOAD LINK:-
https://play.google.com/store/apps/details?id=com.aide.ui
I have many times found devices or ROMs that have malware installed as system apps. This thread is intended to define a recurring problem and discuss and determine solutions.
Background:
In many cases malware apps can simply and directly be removed with root privileges. A complication, however, arises when the app to be removed is: a rather important app, necessary to run or boot the operating system, or an app of its kind is necessary to run or boot the operating system. Only removing such apps may resolve the malware problem, but creates other major problems such as an inability to meaningfully operate the Android environment or an inability to boot the Android operating system. A few typical examples of such apps are the Settings app and the Package Installer app.
Wherefore, to perform a proper repair, a malware app must instead be patched to remove the malware or replaced with another clean and compatible app.
For basic Android apps, such as the Settings app and Package Installer app, that are malware infected, I would think that the best course of action would be to replace the infected app with a clean AOSP version or clean OEM version. Using the OEM version of the app would only be acceptable if the app were available and the OEM is believed to not have or be the source of the malware.
The Problem Being Considered:
For a malware infected system app to be replaced with a clean AOSP version, my impression of the most obvious option that would be most likely to work would be to build Android from source against the target device and for the same architecture and Android version as the malware-infected system, and then donate its apps as replacements for the malware-infected apps and replace the malware-infected apps. Unfortunately, while the method should be effective, it comes with considerable costs. The sizes of the various Android source codes are quite large and it can take a rather long time to acquire and process it. It is worth considering other options.
Questions to Resolve Problem or Are Related to Problem:
Instead of building Android from source against the target device and for the same architecture and Android version as the malware-infected, AOSP-based system to use as a source for donating replacement apps:
Should it be sufficient to use apps from a pre-built AOSP or AOSP-based build of Android, such as LineageOS, with the same Android version and architecture as the build of Android of the infected device?
Should it be sufficient to use apps from a pre-built AOSP or AOSP-based build of Android for a different device, but with the same Android version and architecture as the infected device? Is the matching of the SoC or processors of the donating Android build and the target Android build important for donation app compatibility purposes?
Is it acceptable to use a build of Android of a different minor version to acquire an app for donation to the malware-infected app build? (For example, malware-infected build may be of Android version 7.0, but other, clean Android build may be of Android 7.1.2)
Can just single Android system app be compiled? If so, would it still require acquiring the source code for the entire Android version?
Are there any generic, pre-built offerings of Android that may be used to acquire the replacement apps for donation to the malware-infected Android build? If so, where?
Any other recommendations or things I may not have thought of?
i have the apk file for an old app that is no longer on the play store. it's for gingerbread but i want to edit it so that it will run on android 11. is this possible and if so how hard would it be to do
Android applications are generally forward-compatible with new versions of the Android platform.
Because almost all changes to the framework API are additive, an Android application developed using any given version of the API (as specified by its API Level) is forward-compatible with later versions of the Android platform and higher API levels. The application should be able to run on all later versions of the Android platform, except in isolated cases where the application uses a part of the API that is later removed for some reason.
In an app's withcoming file named AndroidManifest.xml it's declared what Android API that the application is going to use.
Example:
Code:
<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="15" />
So you have to edit this file accordingly.
jwoegerbauer said:
Android applications are generally forward-compatible with new versions of the Android platform.
Because almost all changes to the framework API are additive, an Android application developed using any given version of the API (as specified by its API Level) is forward-compatible with later versions of the Android platform and higher API levels. The application should be able to run on all later versions of the Android platform, except in isolated cases where the application uses a part of the API that is later removed for some reason.
In an app's withcoming file named AndroidManifest.xml it's declared what Android API that the application is going to use.
Example:
Code:
<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="15" />
So you have to edit this file accordingly.
Click to expand...
Click to collapse
ok so the app brisksaber should work on android 11? i can't get it to work at all, won't even open but it does install