It isn't clear what they mean when they say pick up where you left off. If I am in the middle of a random game, and I pick up another device of mine with the same app installed...I can start from right there?
Here is an article that sounds like where Android is heading (scroll down a bit to the device backup section).
Edit: I cannot post links...so Google search this for the Android Police article -> "[APK Teardown] Google Play Services 6.1 Contains Proximity Unlock, Device-2-Device Account Transfer, New Authorization Techniques, And So Much More"
Right now I know Google already has something similar, but devs have to implement it themselves. We know how well that goes (look at Immersive Mode...not even Google has done this with many apps....including Chrome who could really use it). I know there is one FF that uses this functionality, but it is purely up to devs. I am HOPING that Google allows brute forcing it into Google Drive. I have so much Google Drive space availible I would be happy to donate space for true backups of my device.
So, has no one looked into this? This could be a huge change to Android, or a small one.
Surely someone on this forum dedicated to Android developers would have some idea about what the details are.
Related
Does anyone know if google is going to be allowing api access to their cloud music service? I love the idea of syncing my music between my desktop and phone via the cloud, but I'm not a huge fan of their music player. I wasn't able to go to google i/o this year, so I didn't get a whole lot of 'insider' info. Has anyone heard anything about this? My gut feeling is that they're going to make it a google-only type thing to make people want to use their music app, but my hope is that it'll end up as a system feature.
Currently, the music app syncs with the cloud. Ideally, I'd like android as a system(accounts and sync) to sync the music from the cloud to a folder or something so I can use my own or any other number of awesome music apps, most notably federico's ubermusic(zune style).
If I get time this week I'm going to dig through the new music player and see if I can pull out any code that would make use of a new api or something, but like I said, my gut is telling me that this is coded to their app only.
Thoughts, ideas, and info greatly appreciated!
Mods: I thought this would get better coverage here, but feel free to move it if you think it's miscategorized.
Do anyone have any info about this?
I doubt google are giving away hundreds of thousands of GB of storage so people can use their service as a handy way to sync their tunes.
I'm not a fan of the Google Music player either, but hopefully it'll be updated to something more user friendly. A google image slide show, while playing an artist or band would be cool.
would be nice to see music on my phone automatically sent to the cloud too though. Rather than just pulling down whats already up there.
This app will take all music that have been marked as "available offline" and make it available in any of your players. Bamf eh?
market.android.com/details?id=com.t3hh4xx0r.gmusicsniper
... ... ...
Did you find solution?
i'd like to see a way to work with google music, not for phones but for a windows media center plugin.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
I'm currently working on an unofficial api: github.com/simon-weber/Unofficial-Google-Music-API
I really hope they release it. I've been waiting patiently. I just want it to work hand in hand with MIUI
Unofficial Google Music API
There is an "unofficial" google music api for python out... Just added MP3 upload capability, so hopefully we won't all be stuck using Google's horrible "music manager" to upload....
Check it out at github.com/simon-weber/Unofficial-Google-Music-API
This thread is probably long dead, but I just stumbled on it through a Google search for 'google music api'.
There are several news stories that went live 3 days ago, saying that there is an unofficial gMusic api which is nearing completion. This means that devs will soon be able to make 3rd party apps which can integrate gMusic libraries and functions. It's not an official release, so it might be buggy at times, but at least it's coming!
Unofficial Google Music API
http://readthedocs.org/docs/unofficial-google-music-api/en/latest/#
From the site:
The Unofficial Google Music Api
The api itself is hosted at GitHub: https://github.com/simon-weber/Unofficial-Google-Music-API.
gmusicapi enables interaction with Google Music. This includes both web-client and Music Manager features.
This api is not supported nor endorsed by Google, and could break at any time.
Respect Google in your use of the API. Use common sense: protocol compliance, reasonable load, etc.
Click to expand...
Click to collapse
maybe either through API level, or by querying market info
Reason: i want to check on GB before I upgrade to ICS, which apps will not work.
don't know if relevant but it is for SGS II
Thx in advance
repost from here as nobody could really answer my question
can't believe I'm the only one with that issue
maybe an idea for a dev? would be willing to pay for that ;-)
I don't see why this can't be done:
-http://stackoverflow.com/questions/2695746/how-to-get-a-list-of-installed-android-applications-and-pick-one-to-run
-http://developer.android.com/reference/android/content/pm/PackageManager.html
-http://developer.android.com/reference/android/content/Context.html#getApplicationInfo()
I haven't thought through the problem just yet, but its seems to be doable. If you don't find an app soon, I will start working on a script that does it and, if successful, a proper, free software app. I am hoping the available methods won't require something as stupid as launching each app fully. But again, I haven't thought it through. Thanks for the idea btw.
EDIT:
Made a little more effort
https://groups.google.com/forum/?hl=en&fromgroups#!topic/android-developers/dXLACRIizKc
I will work on something this weekend and get back with y'all.
EDIT 2:
So it looks like I would need maxSdkVersion which I don't find in the API. Furthermore, it is strongly suggested that one not use maxSdkVersion when building an app so that doesn't sound all that useful. I have received another, much more complicated suggestion that may do what I want, but I will have to look hard at it. Looks like I'm going nowhere in my effort. Always open to suggestions. More to come later this weekend.
I'm not the sharpest tool in the shed, but I thought this was mostly a straightforward task using the API's exposure to AndroidManifest.xml. As per my previously posted link to an Android Developers discussion on the topic, my approach is dead in the water as far as I can see. I did try to find an answer though to the best of my limited ability. If anyone has or ever solves this problem (I consider it a problem) I would hope they find the this thread.
Thanks for the learning experience. I give up.
Most older apps will work fine on ICS, its pretty backwards compatible. If the app uses legacy menus the button will appear in the old lower left hand corner location instead of the upper right hand corner like apps written for ICS.
i'm no dev so bear with me if i write stupid stuff
one likely but not very promising sounding way might be to use android:targetSdkVersion as "As Android evolves with each new version, some behaviors and even appearances might change. However, if the API level of the platform is higher than the version declared by your app's targetSdkVersion, the system may enable compatibility behaviors to ensure that your app continues to work the way you expect. You can disable such compatibility behaviors by specifying targetSdkVersion to match the API level of the platform on which it's running. For example, setting this value to "11" or higher allows the system to apply a new default theme (Holo) to your app when running on Android 3.0 or higher and also disables screen compatibility mode when running on larger screens (because support for API level 11 implicitly supports larger screens)."
question though is how many apps actually use this?
However after having read this re android:maxSdkVersion "Warning: Declaring this attribute is not recommended. First, there is no need to set the attribute as means of blocking deployment of your application onto new versions of the Android platform as they are released. By design, new versions of the platform are fully backward-compatible. Your application should work properly on new versions, provided it uses only standard APIs and follows development best practices. Second, note that in some cases, declaring the attribute can result in your application being removed from users' devices after a system update to a higher API Level. Most devices on which your application is likely to be installed will receive periodic system updates over the air, so you should consider their effect on your application before setting this attribute." (taking from here) i now don't know how important my op is, but then why do all app devs release new versions "fixing things" for ICS?
One pretty significant example which actually currently will prevent my phone from getting ICS for now is that the subsonic app in the current version produces stuttering when playing audio while downloading (problem description here).
Isn't there any way to instead of searching the phone searching google play/android market instead?
Randi said:
maybe either through API level, or by querying market info
Reason: i want to check on GB before I upgrade to ICS, which apps will not work.
don't know if relevant but it is for SGS II
Thx in advance
repost from here as nobody could really answer my question
Click to expand...
Click to collapse
Here's a list of some working games/apps for ICS
Theoretically an Android app (or a combo of say App Engine and Android) could find your installed apps, seacrh Play for said apps and then scrape the page for relevant information. Doesn't sound to hard, but I didn't think about too hard either. Perhaps I will check out what useful info is on Play and how feasible scraping its markup will be. I will get back at y'all if I do.
So i did a quick Google search, however, i didn't find anything answering my question.
So when we think about android we (at least the ones who knows their thing) we know it is related to google. However, so far i know that Android is open source, correct me if i'm wrong, but that means that anyone CAN "cook" their own rom of android. (As soon in the numerous threads in android development). So far so good.
A while back i recall reading Google forbidding Cyanogenmod of including their multi-window feature (the one that allows you to surf the web and watch a youtube video simultaneously as seen in Samsung devices(Note 1/2 probably S4 and S3(?)). Anyways, my guess is they came to terms where they can agree or did Samsung ignore what google had to say? So to make a long story short, what are google's rights when it comes to android?
Can google, for instance, if it doesn't like what a manufacturer is adding to their phone be it a feature or a skin say that they only want manufacturers to stick to the AOSP look and if they do add their own skin they will be taken to court? Can they do this?
Just curious to understand how things are running here. I wanna know the rights google has and if it could have went to court with samsung because of using the multi window feature.
I think that you are asking a good question, to which I have no answer, but would be interested in following this.
Personally, I would like to see an Android ROM devoid of Google.
____________________
Sent from my HD2 JB-CM10 with XDA Premium
shadehh said:
So i did a quick Google search, however, i didn't find anything answering my question.
So when we think about android we (at least the ones who knows their thing) we know it is related to google. However, so far i know that Android is open source, correct me if i'm wrong, but that means that anyone CAN "cook" their own rom of android. (As soon in the numerous threads in android development). So far so good.
A while back i recall reading Google forbidding Cyanogenmod of including their multi-window feature (the one that allows you to surf the web and watch a youtube video simultaneously as seen in Samsung devices(Note 1/2 probably S4 and S3(?)). Anyways, my guess is they came to terms where they can agree or did Samsung ignore what google had to say? So to make a long story short, what are google's rights when it comes to android?
Can google, for instance, if it doesn't like what a manufacturer is adding to their phone be it a feature or a skin say that they only want manufacturers to stick to the AOSP look and if they do add their own skin they will be taken to court? Can they do this?
Just curious to understand how things are running here. I wanna know the rights google has and if it could have went to court with samsung because of using the multi window feature.
Click to expand...
Click to collapse
My understanding is while 'Android' or rather the AOSP is completely open source and free to use as you like, there are parts that Google have restrictive licensing over, or example the 'Gapp' (gmail, google+, play store etc). Manufacturers then also hold rights over the parts they add into Android (skins, other apps etc.).
Google has no control over manufacturers sticking Android on a device and that manufacture changing Android in anyway (hence the many many random Chinese devices), however Google can prevent a manufacturer from having a license to include the play store etc if they are unhappy with whats being done.
Google didn't forbid the CM team from including it, they said they would restrict access to the Play Store for devices running CM. The Play services is the only thing Google has power over, since that's their proprietary service. They cannot prevent someone from making a device that runs Android, since that's open source.
And I so believe Samsung's method is different, because apps require some changes before you can run then in multi windows, so you can't just run any app (officially, that is).
Lesicnik1 said:
Google didn't forbid the CM team from including it, they said they would restrict access to the Play Store for devices running CM. The Play services is the only thing Google has power over, since that's their proprietary service. They cannot prevent someone from making a device that runs Android, since that's open source.
And I so believe Samsung's method is different, because apps require some changes before you can run then in multi windows, so you can't just run any app (officially, that is).
Click to expand...
Click to collapse
I see. Doesn't that in theory mean that Samsung could just take their sgs 3, remove all google services and smack their own play store onto it or am i missing something here?
shadehh said:
I see. Doesn't that in theory mean that Samsung could just take their sgs 3, remove all google services and smack their own play store onto it or am i missing something here?
Click to expand...
Click to collapse
Oh they could. But then it would be blocked from other Google projects as well.
Wayne Tech S-III
Was just wondering what peoples thoughts were on using the Android Licensing copy protection in their apps? Do you use it and do you spend a lot of time on it or have any creative ways to help enforce it?
As we all know any kind of drm will always be cracked but I just wanted to know if people found it worthwhile to have..
I'm using In-app-billing, because I found that even licensed apps can be copied.
And yes, all apps can be cracked eventually, but most of the publishers of cracked apps remove them if you ask to. So that's what I'm gonna do!
Sent from my Nexus 4 running Android 4.2 JB
I don't like license checks that force you to be online, but I do like to have 'something' in place...
Recently I started working with some OEMs in India who wanted to pre-load my apps on their devices. Very exciting obviously, but I didn't know if I could trust them as I'd never heard of them.
So what I did was get the app to load a web page on one of my servers off the screen (9000%x...) so that it couldn't be seen. The page it linked to was empty, but if I wanted to I could modify the code to include a redirect that would send it to another page. Then in my 'onPageOverride' event I just said if URL = 'stopapp.htm' then do whatever it was I wanted to do.
What I actually have it do in that event is to fill the entire screen with that web page. The user then can't interact with the app underneath, but they get a message that I can create at the time saying 'This app has been illegally distributed' or whatever else I want to say. I can even forward them on to the download page if I want this way.
This works well too because if the user isn't online, the page just doesn't load and nothing happens. But if I want to stop offline use as well I can save a file in File.DirInternal and have the app check for that. 'SwitchOff.txt'. They get caught once, then they can't use the app.
Obviously this doesn't work quite like a license check, but what you *could* do with it is to have the app pop up with a message to people using an old version that's not updated. That's probably downloaded off of some file sharing site, so you could then just keep pestering them to 'update' and send them to the Play Store to do so. You can also check how many of the users on that version of your app are legitimate by looking at your Play Developer Console.
One thing to note is that the redirect URLs you use will need to be different in every version of your app that you release.
Hope this helps someone! I wish I'd done it sooner, one of my apps is all over the web grrrr...
pretty much the same as what I'm doing atm except I just ping a server in the background and display a popup if the result meets certain conditions.. I don't disable the app either as I can't be 100% certain it's pirated, instead I display a "scary" popup saying if they're using a pirated copy this is illegal etc.. your average user won't know how the popup was generated so it should be enough to make them think "someone" is onto them and go the proper route.. With the added bonus a genuine user can just press ok and carry on using the app
Sent from my Nexus 4 using Tapatalk 4
Currently, none of my apps use licensing.
For one of my paid apps, about 5% of the downloads are from non-Google Play sources, meaning, I'm not seeing any revenue from those 5%.
There is an Android API, that allows developers to see which platform their app was downloaded from. So, I've been thinking about adding that hidden feature to my apps and maybe do something fun with it. But, haven't got around to it yet. My thinking has been that if somebody downloaded a pirated copy of my app, then they probably weren't going to pay for it in the first place. And, hopefully, they will tell their friends about it and maybe one of them will actually purchase it through Google Play.
I already have all my licensing code in place and commented out. Since my app is pretty new I want to see how it does before adding licensing. Since the app is free and income is from IAP its not too bad. I'd only turn on licensing in the next release if I see a pressing need for it.
Currently, none of my apps use licensing.
So I've come to discover that, if you enable Google Location Service on my Samsung Galaxy S7 Edge (and I assume *all* other Android devices, but rebuttals to this are kind of the point of the post), all Google accounts logged into the device will be able to locate, and "remote control" the device via Find My Device app on any other device/desktop/etc. that can login via the Google account. And the only way to prevent this is to remove the Google account from the phone. There is no proper fine-grained control.
This means if you login a child's Google account to your device (say phone), to allow them to resume a game from the last save point in Google Games, they can then go back to their device, and locate your device/phone at any time, remote control it to say a ring for a prank, or worse, perhaps wipe the device.
I've google around, and haven't really found a post that describes this or comments on how problematic this can be... am I overreacting here? Isn't this really problematic and something that should be fixed in future Android releases?
da4an1qu1 said:
I've google around, and haven't really found a post that describes this or comments on how problematic this can be... am I overreacting here? Isn't this really problematic and something that should be fixed in future Android releases?
Click to expand...
Click to collapse
And of course, I am not suggesting that this community has anything to do with the Android baseline development. But I guess from the point of view of what customisations could go in, this might be of interest.