I just want to know why the API 17 had been specifically chosen between other ones.
That must have a reason.
Related
Hello all,
I'm currently trying to develop an Android app as part of my final year of university (I would have posted this is development but I'm too new ) and I'm using my Dell Streak as the main testing device as, lets be honest, it rocks and I'm too poor to get another device. I'm running DJ_Steves Streakdroid 1.9.1 custom rom as the Android platform.
The app itself requires the usage of some sort of mapping API, and I would prefer to use the Google maps API as it has all the features I require and with it being built into a significant number of Android devices it would reach the widest range of devices whilst retaining the necessary simplicity due to being built into the SDK and ADT plugin. However when attempting to run a basic app prototype that displays a map centred on the last recorded GPS location, I run into a classDefNotFoundError every time I try to run it, indicating that the API does not exist on the device. This leads me on to a selection of questions I'd like to ask if anyone knows the answers to:
Do any of the Streakdroid versions have the maps API?
Do any other custom roms have the maps API?
Is the maps API included in the stock Froyo release?
I was wondering about updates if it turns out that LG won't give them any more.
The V60 is supposed to have project mainline, and so there are, I think, 23 modules that can be updated directly by google (Oh, joy!)
But I'm not sure they are, or how to check when they were, or enable updating.
Looking in /system/apex I see apex modules, all dates Dec 31, 2008. Not very helpful. Would updates go here?
Has anyone seen mainline modules updates for the V60?
So, i try to write my first App for my Puma Smartwatch. (If i get it right, it's a derivative of a Fossil Gen4)
First thing, i try to understand Wear OS Versioning, what API level it supports, to select a corresponding emulator.
In the Watch settings i see
Wear OS 2.27
Systemversion H MR1
Patch level 1.Jan.21
Build PXDE.201206.004.A1
Click to expand...
Click to collapse
Wear OS 2.27 does not (yet) exist yet according to wikipedia.
Is it a sub-version of 2.2? The date and H MR1 points to it...
Anyways, the final question is, which API levels are supported by which WearOS versions?
They dropped Android 7.1.1 Nougat (API 25) support a couple of months ago. Wear OS app on the watch has been impossible to update since then, even by installing from ADB. Most of the other apps still update from GP, on the other hand.
So I learned that there is something called Camera2 API, which as far as I understand, allows third party apps to take full advantage of camera on your android phone.
There are 4 levels, the higher the level, the more features and more support you have.
Sadly, Xperia Z2 has no support for Camera2 API, when I install Camera2 API Probe App, it tells me that Hardware support level is "Legacy" which means no support for Camera2 API.
I was wondering, is this set in stone or can it be changed ?
Maybe by rooting or something, not sure.
Hence why I am asking here, do you know ?
So seems like Xperia Z2 simply has no Camera2 Api support and that's the end of that.
That's OK, next time when I go out to buy a new phone I will look for one that has this
As well as unlocked bootloader and sim.
Cheers
Now am on Android 12 but want to fake a certain app that am Android 10 to use some feature because it doesn't provide that feature above 10 so is there any way to fake my Android version to specific app?