I know about offsetChange function, but it doesn't work on such devices as Galaxy S4. I think it happens because of TouchWiz wrapper. So I need to find out another way to determine count of home screens.
Any help will be appreciated!
Android has main screen like desktop.
Android has a home screen. Whether it is "like desktop" or not depends upon the device and user.
There are several home screens, you can switch between them
It is unclear what you mean by this.
You might mean "an Android device can have multiple applications installed that each offer to be a home screen, and the user can choose which of those applications to use". In that case, creating an Intent for ACTION_MAIN and CATEGORY_HOME, then passing that to queryIntentActivities() on PackageManager, should give you the list of possible home screen implementations.
You might mean "all Android home screens offer some sort of swiping option to move to different portions of space". Some home screens offer this, and there is no standard way to find out. There is no requirement that a home screen offer the capability of swiping this way, let alone a requirement to supply an API for third-party apps to find out details about them.
Related
I am developing an android application and I'm trying to implement a button which initiates a screen mirror to a selected device.
I want it to be as straigth forward as possible, but the best i've been able to do is have it open the cast settings on the Settings app, which isn't a proper solution. It would be ideal to start screen mirroring with a single click.
Problem is i've tried using Googles Cast SDK but that only allows me to build custom HTML cast receivers, which isn't what I want, I just need a screen mirror from the android device to a screen/TV.
Is there any Android module/API that would allow me to do this with a single click, even if I have to use a Chromecast/Miracast device connected to the screen?
No, sorry, this is not an option AFAIK.
At least part of this is privacy/security. You seem to want to be able to start screen mirroring purely from app code ("I'm trying to implement a button", "allow me to do this with a single click"). Your button is the "single click", and so you really want to be able to do this without user involvement at all (since there is nothing forcing that button to exist). Showing the contents of the screen on another screen that might be visible to lots of people is the sort of thing that users need to approve, which is why additional clicks will be required.
In addition, there may be more than one target for screen mirroring within range, and the user needs to be able to choose which one to use, if any.
Combine all that with limited support for wireless displays across the various Android device manufacturers, and there really isn't anything here for what you want.
I want to make a widget but it should be uninstallable or undeletable from home screen (if possible) like "google search" widget on nexus & moto phones. I searched it already but didn't find anything related to this. Is it really impossible to built such widgets?
Is it really impossible to built such widgets?
Yes. The decision of what widgets to allow users to add and remove is up to the home screen implementation, not you. So, for example, if on "nexus & moto phones" you install a third-party home screen, the Google search widget may or may not be available at all, let alone non-removable.
If you want to force people to have certain things on their home screen, write a home screen, then use heavy weaponry to force people to use that home screen. Note that the use of heavy weaponry may be illegal in some jurisdictions.
I need to know the number of virtual screens of the desktop but I don't know where I can find this information.
I think I need to access to the launcher but I don't know how.
This is not possible. Not all home screen applications have "virtual screen of the desktop". Applications should neither know nor care what the home screen looks or behaves like.
I need a screen control (possibly but not mandatory an app widget) that will seat
on Android's homescreen and will always be visible to the user - even when he scrolls the homescreen to the next page.
Please help me if any body have done this before.
I think the only way you will be able to do this is if you implement your own Launcher.
The functionality that you're looking for, being able to place a static widget on every screen of the launcher regardless of how many screens they have, isn't currently available in Android, nor any of the launcher apps out there (Go launcher, ADW, Launcher pro etc) nor any of the versions of Android which have been rewritten by the phone manufacturers (HTC's Sense, Samsungs Touch Wiz etc)
It's a big job to write a Launcher yourself, but the stock Android Launcher code is available to play about with from https://android.googlesource.com.
I am looking for a way for when someone installs my application it goes in their "all applications menu". Then, after they run the app and go into the setup, when they click save on their options, it will create a shortcut on the home screen (not the all applications menu). Also, is it possible to have this shortcut not do the same thing as the other app? meaning that if I wanted to change the settings I could click on the app in the all applications menu and if I click on the app in the home screen it does something else.
First off, there's lots of different home screen implementations on Android. The stock Android one, Samsung, HTC and Motorola all have their own variants, then third party ones like Launcher Pro. All use different stores as to what to keep on the home screen, may provide different profiles for the home screen (home, work, etc).
Second, the home screen is prime real estate. And it is also the user's real estate. If there was programmatic access to the home screen, what happened to the Windows quick launch, desktop, favorites menu (in older versions of IE), and older pin area of the start menu (the very top of it in Win 95/98).
To quote Raymond Chen "I bet somebody got a really nice bonus for that feature". So, in short, even if it was possible, please don't. As awesome as you think your program is, the user might not think the same.