I need to develop an app including feature to add widget on lock screen.
I tried that on 3 devices so far -
1) Samsung Galaxy s4 (KitKat 4.4) - It worked well, if the lock is swipe screen lock,
but doesn't work in case of pattern lock. Even in case of swipe lock, I am unable to add it on main lock screen, instead it appears on second or third screen, navigated from the main lock screen to its right.
2) Samsung Galaxy Grand (JB 4.2.2) - same behaviour as above.
3) LG ls970 (JB 4.1) - It doesn't seem to provide lock screen widget feature at all.
So, what must I do in case I need that to be worked in most of the devices.
What may be the issue by the way - Is it version specific issue or the brand specific or both.
Please let me know the solutions.
Thanks
Lock screen Widgets is not provided by "default" in "older" versions of Android.
Speaking of older - ALL DEVICES THAT ARE >= Android 4.2 SUPPORT lock screen widgets.
OLDER devices < Android 4.2 does NOT SUPPORT this feature. That's the problem
You can get more information on this topic here: Lock screen Widgets
And btw, make sure just to read more on the Google's provided information about Android. It supports search too!
Basics of Android by Google
Related
I'm writing an android application and i need to detect what version of Samsung Experience the device is running to do a special check. Galaxy S8 with android 7.0 allows the navigation bar to be on the left. And from my understanding only android 7.1 allows that. My application apply margins based on android version and I need to check if the version is 7 and we are running Samsung Experience 8.1.
Here you can find an example of About phone.
Another posibility is detect the position of the navigation bar on the screen (right or left). I could not find a way to do it.
thanks in advance.
I tried reading with Build.MODEL, Build.TAGS, Build.MANUFACTURER.
Take a look at Checking external app version name in android
I don't have a Samsung Galaxy S8 available at the moment, but I think you can check the version of packages com.sec.android.app.launcher or com.samsung.android.mobileservice.
I could not find a good solution for the question. Some of them say using flags you can achieve it. But I think it is too old and it will not work for Lolipop.
I have a project on my University Last Semester and I am hard working on that, I have implemented all of the other features but failed for this.
There are no lock screen APIs for Lollipop - the only APIs for displaying things on the lock screen for Lollipop and higher devices is through notifications.
This link lists the supported Android devices that can cast their screen over a Chromecast dongle onto a bigger display. Why aren't other devices like Moto X or E present on the list (both on version 4.4.4 as per the requirement) ? I observed that the "Cast screen" option appears under Settings -> Display on these devices. But it doesnt work.
Are there any hardware requirements for any device to support screen casting?
Thanks in advance!
The Cast Screen feature is currently just in beta. Only a few select devices - like the Nexus 5 - are supported at this time, but this list will be expanded later on. Maybe at some point all Android devices will be supported.
Its all fake no need any hardware. Cast screen works by some system software module which might be missing. some devices gets updated with including cast screen function.
We are evaluating Delphi XE5 specifically to see how easy it is to develop mobile apps. We have developed a simple Android app that scrolls through a TClientDataset using a DBNavigator. The application comprises a few input fields, labels and slider controls (TSwitch).
Everything works ok and sliders (animations) are responsive, except on a Google Nexus 10 (Android 4.3) where everything happens in slow motion. It is like the app is still running in emulator mode. (A sliding button takes over 2 seconds to move from left to right!)
We have successfully tested the app on a Samsung Galaxy S3 (Android 4.1.2) and a HTC One (4.2.2) and the UI is as responsive as one would expect.
Update.
We asked the question at Code Rage 8 and they are referring it to the R&D Department. Will update when or if we get an answer.
I see mention of the screen resolution in comments. Has it actually been determined that it is the screen resolution that is the issue here?
Can you go into the developer options on the Nexus and try anything there that forces GPU usage or whatever might potentially help things along graphics-wise?
And is there anything clue-like in logcat? Run monitor.bat in the Android SDK tools directory or, if the path to it has spaces in, then that won't work so run ddms.bat instead from the same location (DDMS doesn't abort due to spaces in the path).
It would be good to get more evidence on the problem, rather than (educated) guesswork.
If it turns out to be screen size, well that will be interesting for Embo.
I am currently expanding the use of the action bar in one of my applications by looking at and implementing the action mode ability via ActionBarSherlock 4.0.1 and the support Library .
I have achieved this by implementing the 'ActionMode.Callback' on a class as par the ActionBarSherlock example (ActionModes.java). As par the example, I am starting the action mode by using 'startActionMode(new ModeCallback());' and finishing it with 'actionMode.finish();'. The only difference I have is that I am doing all this in a SherlockFragment and not SherlockActivity.
Currently the functionality works just fine, however, as the following images will show, I am getting graphical issues with the ActionBar tabs when they are on a separate row with some android versions and not others.
Android 2.1 - Issue
Portrait - bad:
Landscape - ok
Android 2.2 - No Issue
Portrait - ok
Landscape - ok
Android 2.3.3 - Issue
Portrait - bad
Landscape - ok
Android 4.0 - No Issue
Portrait - ok
Landscape - ok
Apologies for the obvious image adjustment but I have had to cover up some IP. As can be seen from the screen shots of ones with issues and ones without, the tab row is getting 'whited out' when going into the action mode.
The screen shots for Android 2.2, 2.3.3 and 4.0 have been taken from the emulator with 2.1 being taken from my own phone. I can therefore rule out emulator issues. The problem also is present on a phone running Android 2.3.5.
I have also run the application in BlueStack for Windows. Incase you have not heard about it go to http://bluestacks.com/. In essence it allows the running of Android apps in a Windows Environment (Yep, a fancy emulator!). On this the issue is not present.
Any help will be appreciated as the fact it is happening on some versions and not others completely baffles me.