I thought for sure this would have been asked; yet after searching for an hour, I've found nothing.
With the new Google Maps 5.0 out, allowing compass-rotation (showing the map based on your current heading) I wondered if there is a new API available to take advantage of these features?
I updated maps in the SDK but don't see anything new. How would one go about exposing these new v5-specific features in their own app?
Thank you in advance,
RKM
And why do you think you can use features from another apps in your own app?
And why do you think you can use features from another apps in your own app?
Click to expand...
Click to collapse
I'm sorry if my post came across as if I expect to use features from other apps in my own app. That was not my intention. My intention was simply to ask a very simple question, that is..
Google, owning the Android OS, offers the API for "Maps". This API currently supplies the ability to render maps. Prior to v5, the rendering looked identical to what Google exposed to developers.
Google has updated their turnkey Maps app. As a result, the rendering (and the very foundation, now that it consumes vector data rather than tiles alone) has changed.
My *question* was simply whether this is passed along to the developer in some way, or whether the developer is limited to using the older tile-only infrastructure that also lacks auto-orientation.
If the answer is that the developer is limited, I'm fine with the answer. I certainly didn't mean to suggest that I should be allowed to cannibalize features from other's app, but merely was referring to what appeared to be a fundamental change in their Maps app, that I wondered whether it might pass along in their API, being that LBS/Maps is pivotal in the Android as a mobile development platform.
Ahh, sorry, now I know what did you mean
Google Maps doesn't use Maps API - these things are totally unrelated with each other. So answer is: no, you can't use vector maps in Maps API. Maybe someday Google will update Maps API as well.
Ah, okay. Although it's not the answer I was hoping for, at least I can put an end to my quest!
Thank you!
Related
desperate for it. makes me want android just for this app. is there one for WinMo? or anyone trying to port it?
and is this app dependent on Andoird hardware, like specific hardware to function?
Could not find sofar Google sky maps for windows. For sure is not a hardware thing.........
Think that google wants to keep some apps exclusive for Android to make this OS more attractive vs windows......
It's a matter of time till it is available to us guys.
You could try this application.
http://forum.xda-developers.com/showthread.php?t=666966
Nice catch..... Looks like google sky......
I have a question that is purely out of curiosity. I'm not a developer, nor do I have any desire to become one... at this time.
In the process of answering questions for my father about his new Android phone, I came across the Android Developers website. Being the infinity curious person that I am, I started to browse through it and came across something that I was particularly curious about, the "Forward-Locked Application" market filter. It states that an application in the market can be set to not be visible to developer devices and unreleased devices. What I'm curious about is why would a developer not want their app to not be visible to said devices? Wouldn't it be to their advantage to allow their app to be visible, installed, and possibly tested if the owner of the developer phone or new unreleased phone so chose to do, after all, this is potentially new hardware that the app developer may not have support for in their app. Now not being a developer myself, I'm sure there are valid reasons for the filter and I am just curious as to what they may be.
Because you haven't tested your app on a new OS build, and want ensure compatibility before offering it for sale. Other reason is that the new OS build either obsoletes, duplicates, or just plain breaks your app. An example would be the updates to the calendar API's in Android 2.2. Every calendar widget in the market that tied into the built-in calendar app ceased to function because the way it interacted with outside apps had changed.
So the lock is not in reference to developer or unreleased hardware, it pertains to developer or unreleased software or OS?
They would check build/version number in the build.prop or whatever they use... It's just like how FroYo builds couldn't see protected apps while it was in pre-release.
garfnodie said:
So the lock is not in reference to developer or unreleased hardware, it pertains to developer or unreleased software or OS?
Click to expand...
Click to collapse
yes this is correct. The developer phones have different software that allow native root access and this would be defined in the build.prop . That would also allow people to rip applications and pirate them.
That switch is mainly a quality assurance/anti-piracy measure.
ATnTdude said:
Because you haven't tested your app on a new OS build, and want ensure compatibility before offering it for sale. Other reason is that the new OS build either obsoletes, duplicates, or just plain breaks your app. An example would be the updates to the calendar API's in Android 2.2. Every calendar widget in the market that tied into the built-in calendar app ceased to function because the way it interacted with outside apps had changed.
Click to expand...
Click to collapse
Actually, those apps that broke, broke because they were using private APIs. As explained, if you stick to public APIs your app should not break when updating OS iterations because ALL APIs are frozen as soon as a release is cut.
Here's another question then, are app's allowed to do automatic bug reporting back to a developer with out the user consent, or even with the users consent. It seems to me that say Google is testing Android 3.0, and one of their in house testers decides to install your app, but your app does not support 3.0 for whatever reason, if there is automatic bug reporting, you could be made aware of a potential incompatibility with a new API and have time to fix it long before the new OS is ever released. This all could never happen though if you have the market filter set.
garfnodie said:
Here's another question then, are app's allowed to do automatic bug reporting back to a developer with out the user consent, or even with the users consent. It seems to me that say Google is testing Android 3.0, and one of their in house testers decides to install your app, but your app does not support 3.0 for whatever reason, if there is automatic bug reporting, you could be made aware of a potential incompatibility with a new API and have time to fix it long before the new OS is ever released. This all could never happen though if you have the market filter set.
Click to expand...
Click to collapse
bug reporting is going to be a new feature of 3.0. I dont think many if any apps have their own built in bug reporting. Also it really is on the developers side if their app doesnt work with new OS revisions. They should program their apps in such a way that they wont have to make drastic changes for updates. Google also give plenty of time for developers to make fixes before the first iterations of the new update goes out (almost 1 month in the case of froyo)
however some developers just dont care (e.g Co-Pilot)
I just two apps called ANT Radio Service and ANT+ Plugins. I did not installed them. How can they are on my phone? And why are these are system apps?
Can I delete them, and if I can, how do I make it?
I use 4.3 MI8 Android Sytem on my Galaxy S4
Lewis0214 said:
I just two apps called ANT Radio Service and ANT+ Plugins. I did not installed them. How can they are on my phone? And why are these are system apps?
Can I delete them, and if I can, how do I make it?
I use 4.3 MI8 Android Sytem on my Galaxy S4
Click to expand...
Click to collapse
Copying my post from somewhere else:
Sony and Samsung bundle these services on all of their latest devices.
To my understanding these services are just the equivalent of the Bluetooth stack which allows apps to use Bluetooth on your phone, but for ANT+. Instead of being built deeper down at the system level (where you wouldn't find it in your apps list), it's been distributed on the Play Store to make bug fixes and new feature updates much faster than waiting for new firmware updates. Also it allows users to add ANT support to devices which already do not have it through USB.
Google already does this with their Google Play Services which they bundle into the Google Play "app" so they can bypass carriers and not wait for phones to be firmware updated (if they ever are). In this case it's just more highly visible then if it was hidden deeper.
If you delete them, it's the equivalent of deleting Bluetooth support, but for ANT+ devices instead.
You can find more information about it on their website.
As to removing it, you need root access, but if their are no apps using them then they don't consume any discernable power anyway
OneCanuck said:
Copying my post from somewhere else:
Sony and Samsung bundle these services on all of their latest devices.
To my understanding these services are just the equivalent of the Bluetooth stack which allows apps to use Bluetooth on your phone, but for ANT+. Instead of being built deeper down at the system level (where you wouldn't find it in your apps list), it's been distributed on the Play Store to make bug fixes and new feature updates much faster than waiting for new firmware updates. Also it allows users to add ANT support to devices which already do not have it through USB.
Google already does this with their Google Play Services which they bundle into the Google Play "app" so they can bypass carriers and not wait for phones to be firmware updated (if they ever are). In this case it's just more highly visible then if it was hidden deeper.
If you delete them, it's the equivalent of deleting Bluetooth support, but for ANT+ devices instead.
You can find more information about it on their website.
As to removing it, you need root access, but if their are no apps using them then they don't consume any discernable power anyway
Click to expand...
Click to collapse
Good to know thanks for the info.:good:
Ant and Ant+ are for pairing with fitness devices like pedometers, heart rate monitors, and other such fitness monitors and tools. If you do not use these type of devices...simply disable the app...its just another way samsung is trying to appease all of their users and entice others to use their products. A very useful app if you are into staying fit.
NO!!!,DONT USE THEM,THEY WILL TURN YOU INTO ANT(lol,jk,just feeding the trolls[emoji23] [emoji23] ) but anyways @geusseppe is right:
geusseppe said:
Ant and Ant+ are for pairing with fitness devices like pedometers, heart rate monitors, and other such fitness monitors and tools. If you do not use these type of devices...simply disable the app...its just another way samsung is trying to appease all of their users and entice others to use their products. A very useful app if you are into staying fit.
Click to expand...
Click to collapse
Sent from my GT-I9505 using Tapatalk
yahya wessam said:
NO!!!,DONT USE THEM,THEY WILL TURN YOU INTO ANT(lol,jk,just feeding the trolls[emoji23] [emoji23] ) but anyways @geusseppe is right:
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
geusseppe said:
Ant and Ant+ are for pairing with fitness devices like pedometers, heart rate monitors, and other such fitness monitors and tools. If you do not use these type of devices...simply disable the app...its just another way samsung is trying to appease all of their users and entice others to use their products. A very useful app if you are into staying fit.
Click to expand...
Click to collapse
Not exactly, this is not entirely correct. It's more then just "pairing fitness devices". Please read OneCanuck's first reply for a better understanding on what it is. Thank you.
Just watched a video where apparently this so called "ANT" app is just a spy infiltrated in your phone. If installed, by remote access, camera/microphone can be activated even with the phone shut off.
Link, or it doesn't exist.
Where did you find this video? And, what Proves they have knowledge & truth on the subject. Just cuz its on the web dosent mean its true or real. Theres a LOT of sh*theads out there puttíng out Bad Information, some unwitingly, some are deviant jerks. Either way, the one who accepts this bad info is exploited & his/her problems are ábout to begin. Be suspicious my friend, trust nothing, verify everything.
@?Everything: Replying to a thread that's been dead for two years now. Why?
@Strephon Alkhalikoi, things stay on the internet for longer than 2 years and search engines find them.
If you want siloed forum threads, automatically lock them after 6 months of inactivity. But there's value in having all information and interaction in one place.
To ?Everything's point, notkbna never provided proof, and readers from the future will now have both warnings and be able to decide on their own.
To make my own contribution to the actual topic, ANT+ really isn't much more than "pairing fitness devices". Sure it can be used in things like remote controls and geocaching, but it's just a protocol for monitoring sensor data.
Let'sDev said:
@Strephon Alkhalikoi, things stay on the internet for longer than 2 years and search engines find them.
If you want siloed forum threads, automatically lock them after 6 months of inactivity. But there's value in having all information and interaction in one place.
Click to expand...
Click to collapse
And here you are, wasting time on a thread that ended three years ago. Neither you nor "Everything" bothered to look at the date of the last post, which means the only purpose of you two posting at all is to inflate your post counts. The only reason I knew this thread was resurrected from the dead is XDA Labs bringing it to the top of my Participated Threads window.
You're wasting both your time and mine by resurrecting this thread. The people who participated in it are unlikely to respond, and anything you may want to add is probably out of date.
Just like this thread.
Hi all,
If you've read the text that USED to exist here before, scratch that. Big Thanks to @Sunius1 for clarifying what I thought was a win. Due to this, I DID find something interesting in regards to the ExtensibilityApp class (Windows.Phone.System.LockscreenExtensibility.ExtensibilityApp). I happened to also find a hidden capability "ID_CAP_SHELL_DEVICE_LOCK_UI_API" (Seems to be a locked CAP because it only works on Emulator. I get a deployment error on my if I try including this capability). I suspected that these two worked together, but I wanted to make sure of this.
Before we get started, read through the documentation from this site: http://msdn.microsoft.com/en-us/lib...lockscreenextensibility.extensibilityapp.aspx.
We have the following methods:
BeginUnlock
EndUnlock
GetLockPinpadHeight
IsLockScreenApplicationRegistered
IsSystemOverlayApplicationRegistered
RaiseToastNotifications
RegisterLockScreenApplication
RegisterSystemOverlayApplication
UnregisterLockScreenApplication
UnregisterSystemOverlayApplication
EDIT: After the release of the Live Lock Screen app, my speculations about the ID_SHELL_CAP_DEVICE_UI_API capability and the ExtensibilityApp object were correct. Thanks to @jessenic for finding out a good bit of info on this with me.
It seems that in order to get this working, we have to add an Extension to the WMAppManifest.xml
<Extension ExtensionName="LockScreen_Application" ConsumerID="XXXXX" TaskID="_default" ExtraFile="Extensions\\LockAppExtension.xml" />
In the LockAppExtension.xml:
<?xml version="1.0"?>
<x:Extension xmlns:x="urn:LockApp">
<AppID>AppNameForLockScreen</AppID>
</x:Extension>
As usual, Microsoft doesn't really give us much in terms of documentation.. Probably because it isn't meant to be used by the normal developer Confirmed: For now we have to actually ask for permission in order to use the cap. As to whether we'll get that granted? Who knows....
All of these methods have no parameters at all, but I can almost guarantee this has to do with having an application that can control the lock screen.
This thread will be for efforts in breaking this open and seeing whether we can create lockscreen applications..
Homebrew Lockscreen Apps:
Lockscreen App by @-W_O_L_F-
There are actually two Windows.winmd files in Windows Phone SDK, one for Silverlight 8.1 apps and one for Jupiter 8.1 phone apps (located in C:\Program Files (x86)\Windows Phone Silverlight Kits\8.1\ and C:\Program Files (x86)\Windows Phone Kits\8.1\). There's only one the phone. And some APIs support only one app type (it's phone limitation it seems: faking .winmd file results in Platform::InvalidOperationException, saying you cannot use that API from this app type). That explains why the one on the phone has more APIs available than either of for single app type.
As for LockscreenExtensibility - it's documented, just not available for Jupiter apps:
http://msdn.microsoft.com/en-us/lib...ows.phone.system.lockscreenextensibility.aspx
Sunius1 said:
There are actually two Windows.winmd files in Windows Phone SDK, one for Silverlight 8.1 apps and one for Jupiter 8.1 phone apps (located in C:\Program Files (x86)\Windows Phone Silverlight Kits\8.1\ and C:\Program Files (x86)\Windows Phone Kits\8.1\). There's only one the phone. And some APIs support only one app type (it's phone limitation it seems: faking .winmd file results in Platform::InvalidOperationException, saying you cannot use that API from this app type). That explains why the one on the phone has more APIs available than either of for single app type.
As for LockscreenExtensibility - it's documented, just not available for Jupiter apps:
http://msdn.microsoft.com/en-us/lib...ows.phone.system.lockscreenextensibility.aspx
Click to expand...
Click to collapse
Well that is very good to know! Thanks for the clarification. The best part is that I was actually able to compile without receiving an error (somehow).
I found something that may be of use in order to get the LockscreenExtensibility working (I just tried on a Silverlight 8.1 app and got access denied).
<Capability Name= "ID_CAP_SHELL_DEVICE_LOCK_UI_API"/> <----. Can't be used OOTB
EDIT: I just tested this in the Emulator and it really IS the capability that the LockscreenExtensibility needs in order for it to work.
snickler said:
I found something that may be of use in order to get the LockscreenExtensibility working (I just tried on a Silverlight 8.1 app and got access denied).
<Capability Name= "ID_CAP_SHELL_DEVICE_LOCK_UI_API"/> <----. Can't be used OOTB
EDIT: I just tested this in the Emulator and it really IS the capability that the LockscreenExtensibility needs in order for it to work.
Click to expand...
Click to collapse
I assume this is the thing Rudy Hyun used to create the lockscreen app at Build?
TheInterframe said:
I assume this is the thing Rudy Hyun used to create the lockscreen app at Build?
Click to expand...
Click to collapse
I speculate that this is what he's using. I bet there's more going on that we have yet to figure out. It also could be that the base class EXISTS, but the full implementation isn't available yet. Who knows.
snickler said:
I speculate that this is what he's using. I bet there's more going on that we have yet to figure out. It also could be that the base class EXISTS, but the full implementation isn't available yet. Who knows.
Click to expand...
Click to collapse
Ah, Yes that makes sense. I wonder if there are any other "half-baked" API's in the SDK?
Edit: I Know it sounds stupid but honestly I think we should have a thread dedicated to finding odd API's (Just found one: Windows.Phone.System.SystemProtection, nothing terribly useful though)
TheInterframe said:
Ah, Yes that makes sense. I wonder if there are any other "half-baked" API's in the SDK?
Edit: I Know it sounds stupid but honestly I think we should have a thread dedicated to finding odd API's (Just found one: Windows.Phone.System.SystemProtection, nothing terribly useful though)
Click to expand...
Click to collapse
there are also some hidden APIs in the current SDK for 3D Touch-enabled Apps!
From WP Central:
Some of the features include APIs for gestures, side interactions and even heat maps.
Crazy stuff.
Believe it or not, some of these APIs for developers are in the current SDK, they're just not visible. What this mean though is developers will have access to this 3D Touch technology for their apps. It also means that Microsoft will have a small batch of third-party apps supporting this 3D Touch technology on launch day.
Click to expand...
Click to collapse
source: http://www.wpcentral.com/microsofts-next-flagship-windows-phone-november-3d-touch
Yea, even though those 3D touch APIs may be available, they're not particularly useful, as they require special hardware to work.
Sunius1 said:
Yea, even though those 3D touch APIs may be available, they're not particularly useful, as they require special hardware to work.
Click to expand...
Click to collapse
That is true. Sort of of a side question though, has anyone made a OEM account and looked over the API documentation there? There maybe some useful things we could learn about WP and maybe further a jailbreak for all WP devices....
TheInterframe said:
That is true. Sort of of a side question though, has anyone made a OEM account and looked over the API documentation there? There maybe some useful things we could learn about WP and maybe further a jailbreak for all WP devices....
Click to expand...
Click to collapse
API isn't much useful as long as you cant really use most of functions due to policies.
ultrashot said:
API isn't much useful as long as you cant really use most of functions due to policies.
Click to expand...
Click to collapse
Ah, Yes that makes sense....
http://www.wpcentral.com/joe-belfiore-announces-new-updates-sheds-details-lock-screen-app
Sounds like there will be a dev preview update to enable lockscreen functionality quite soon. Joe also mentioned keeping the lock screen in memory. So 512 MB devices won't get the functionality soon....
Good stuff. Another question: can apps show the action center? Because I want code an app to show notifications on lockscreen. Thanks
Marocco2 said:
Good stuff. Another question: can apps show the action center? Because I want code an app to show notifications on lockscreen. Thanks
Click to expand...
Click to collapse
something to force the volume/music control on the lock screen to automatically open would be really useful as well
Updated first post with some more data since the Live Lockscreen App debuted yesterday. There's more I didn't get into, but I want others to dig in and find out
I suppose we can only speculate how it works at this point, but if I had to guess, it goes like this:
1. You have 2 projects in your LockScreenApp solution, one for the application to register the lockscreen, and the second one for the actual lock screen application.
2. The former would use ExtensibilityApp APIs to register the the second one, coupled with the manifests so it's all "valid".
3. The second application is just a another app that is able to process input and draw whatever it wants on the screen. That would explain why there's a delay at it starting when you press lock screen button while the phone is sleeping (probably it's a time for .NET to startup? Direct3D app should be able to start much faster).
Although this is only speculation, I think this makes sense, because that's how background tasks work on Windows, at least. I wonder though, why Microsoft is not releasing the APIs to be used in public - are they afraid somebody will make a lockscreen application that will drain the battery fast or something?
Sunius1 said:
I suppose we can only speculate how it works at this point, but if I had to guess, it goes like this:
1. You have 2 projects in your LockScreenApp solution, one for the application to register the lockscreen, and the second one for the actual lock screen application.
2. The former would use ExtensibilityApp APIs to register the the second one, coupled with the manifests so it's all "valid".
3. The second application is just a another app that is able to process input and draw whatever it wants on the screen. That would explain why there's a delay at it starting when you press lock screen button while the phone is sleeping (probably it's a time for .NET to startup? Direct3D app should be able to start much faster).
Although this is only speculation, I think this makes sense, because that's how background tasks work on Windows, at least. I wonder though, why Microsoft is not releasing the APIs to be used in public - are they afraid somebody will make a lockscreen application that will drain the battery fast or something?
Click to expand...
Click to collapse
I don't think its that but most likely the fact that the API is un-optimized, some of the facts you stated (i.e. Slow start up, documentation is lacking) etc... The fact the OS needs to be updated to show a section telling the user what lock screen app has taken over (since the setting page doesn't now)
Edit: Remember what Joe said about keeping the lockscreen in memory and 512MB devices might not be supported for that reason? Yeah seems like they aren't doing that since you can see the resume time for the lo screen is wayyy to much
Sunius1 said:
I suppose we can only speculate how it works at this point, but if I had to guess, it goes like this:
1. You have 2 projects in your LockScreenApp solution, one for the application to register the lockscreen, and the second one for the actual lock screen application.
2. The former would use ExtensibilityApp APIs to register the the second one, coupled with the manifests so it's all "valid".
3. The second application is just a another app that is able to process input and draw whatever it wants on the screen. That would explain why there's a delay at it starting when you press lock screen button while the phone is sleeping (probably it's a time for .NET to startup? Direct3D app should be able to start much faster).
Although this is only speculation, I think this makes sense, because that's how background tasks work on Windows, at least. I wonder though, why Microsoft is not releasing the APIs to be used in public - are they afraid somebody will make a lockscreen application that will drain the battery fast or something?
Click to expand...
Click to collapse
You are correct. Two projects: One is the settings page, which is the main entrypoint of the app when it's opened from the start menu and the second one is the actual lockscreen app.
The settings page uses the ExtensibilityApp APIs to register the second one as a lock screen application. That second application is another 8.1 Silverlight app that uses a LockScreen_Bridge WinRT component that has native access to read what is shown on the lockscreen from the WP Settings item.
It then uses some storyboards to make it do different things as you're swiping up and down on the LayoutRoot grid. It does use a timer so that's where that little lag comes from.
The only background stuff it's doing is latching on to system events ("Start button being touched for example").
I can see where MS would be protective of this. They DID say that they would be releasing a public version of the API at some point. I'm hoping it's not one of the situations that leaves it public only when they've approved you to be able to use it.
It does suck that it's restricted to 8.1 Silverlight though. I could see some Music Apps wanting to take advantage of the lockscreen like this.
snickler said:
You are correct. Two projects: One is the settings page, which is the main entrypoint of the app when it's opened from the start menu and the second one is the actual lockscreen app.
The settings page uses the ExtensibilityApp APIs to register the second one as a lock screen application. That second application is another 8.1 Silverlight app that uses a LockScreen_Bridge WinRT component that has native access to read what is shown on the lockscreen from the WP Settings item.
It then uses some storyboards to make it do different things as you're swiping up and down on the LayoutRoot grid. It does use a timer so that's where that little lag comes from.
The only background stuff it's doing is latching on to system events ("Start button being touched for example").
I can see where MS would be protective of this. They DID say that they would be releasing a public version of the API at some point. I'm hoping it's not one of the situations that leaves it public only when they've approved you to be able to use it.
It does suck that it's restricted to 8.1 Silverlight though. I could see some Music Apps wanting to take advantage of the lockscreen like this.
Click to expand...
Click to collapse
Quite interesting...!
The API in itself is quite powerful, custom lockscreens with weather animations are possible! http://wmpoweruser.com/wp8-1-live-l...amazing-lock-screen-weather-animations-video/
Hey guys,
I want to explain you how you can integrate different services like Facebook, Dropbox or Slack into your application.
Why is this important?
In the kind of ever evolving market place that we are now in, it is more important than ever that your application can rapidly add new features. You don't have to invent the wheel again, there are thousands of great software solutions out there. All you have to do is to leverage those software and integrate them into your application. By doing so you can provide your users a more pleasant user experience and make your application stand out from others.
What is the problem?
Integrating different services also means to deal with all the different APIs since all the services are using their own API which are very often complex and you will need a lot of time to become familiar with all of them. This means you lose time which you could spent on focusing on your core application.
How to solve this issue?
A very simple solution is to use the CloudRail SDK. CloudRail is a completely free developer tool which allows you to combine all the different APIs including all the features you want to only one universal java or android API in only a few steps. By making the process of adding any new integration quick, simple, and easy, you can start ignoring all of the busy work and get on with making simply great applications.
I would love it if you did check it out and let me know any feedback, good or bad!