I have searched high and low, all the while people telling me that, "no it is impossible to completely surpress the navigation/combo bar on an ICS tablet without rooting it.. and then i find there is an app on the market called Surelock that does exactly this.. Unfortunately i am building a launcher app myself so i can't use their launcher app, but the big question is HOW do they do it? anyone?
Whatever SureLock is doing is exploiting some security hole. Someday, I will take the time to find out what they are doing and will work to get the hole fixed.
Related
the main question I'm asking is:
Does Google prevent ANR dialogs to show up on the customer side when my app is released?
Do manufacturers disable ANR dialogs at some point on the customers side (I think I remember Huawei / Honor was doing something like that)
If not, is there a way to prevent ANR dialogs on the customer side (production app)?
Does anyone know what happens with Android Automotive? Is it possible to show ANRs there?
Thanks a lot for your feedback,
really appreciate your feedback and help!
answering officially for question: starting Android P system won't show ANR dialog, well, by default. There are some options in Developer options for bringing crash/ANR dialogs back and you never know when some Manufacturer turn these on by default (I very doubt for common devices/smartphones, but some "special case" units or "modded" OS versions, which Android Automotive kind-of is, are possible to have such flag turned on)
I have a custom rooted android tablet working on Android M version. We built a kiosk application and next step is removing navigation bar completely, while our application is working. Also, when administrator close our application, navigation bar should appear again.
Before asking this question, I researched on Internet and find a lot of people have this problem. However, answers to theirs question were generally, making application to work in full-screen mode or in immersive full-screen mode.
These answers didn't help me at all, because user still can fling on screen and navigation bar would show again. These solutions are probably the best that can be done with an unrooted device, but in my case I need a better solution and my device is rooted.
Also, I saw this answer link, but after using this command my desktop went black, and couldn't reboot android system again. Happily I have recovery USB so my device is working again. :)
I found another answer link, and like others, didn't help me because I need to reboot system after adding line of code (qemu.hw.mainkeys = 1). Also, solution that I looking for is fully dynamical and done by code.
I am really convinced that this isn't mission impossible, because we had old tablet (also rooted) with button in back, which can hide and show navigation bar without rebooting it.
Any help is appreciated.
I can't help you with your problem, but provide a little more information.
The company im working for is using devices in kiosk mode, but we have custom android devices from a hardware producer, which provides a custom HAL interface. We can set the kiosk mode via that interface.
My guess is it cant be done easily, if it was easy, we would have not gone that way. Hope it helps.
Ok, on the surface I thought this would be fairly easy to do but it's proving challenging for me. All I would like to do is programmatically start the default Android launcher and bring up the apps selection screen. By "apps selection screen" I mean the screen with all the devices applications that is often built into Android, often it can be seen by hitting an "apps" button on a device, the icon associated with the button is often a series of rectangles... I don't actually know what this activity/app is called... so I hope I am articulating this properly.
I know how to start the launcher, the intent I am using looks like this:
Intent().setComponent(new ComponentName("com.android.launcher", "com.android.launcher.Launcher"))
This can be used to start the launcher, however I don't know how to bring up the apps screen. I have looked at the logs using logcat and find that I see nothing to indicate an activity/package/application name when I press the apps button on my device(s). Would anyone be able to shed any light on this for me?
I've been Googling this for quite awhile and haven't found anything I can use, this admittedly could be because I don't know the name of the functionality I am trying to trigger, but for the life of me I can't find that either! . If anyone could point me in the right direction I would really appreciate it. Thanks much.
I know how to start the launcher, the intent I am using looks like this:
There is no guarantee that com.android.launcher exists on any Android device, let alone that it is "the default Android launcher" for the user's configuration.
Would anyone be able to shed any light on this for me?
There are dozens, perhaps hundreds, of launcher implementations that come preinstalled on devices. There are hundreds, perhaps thousands, of launcher implementations that users can download from places like the Play Store. None are required to provide any means for a third-party app to directly drive to "the apps screen". Heck, some will not even have an "apps screen".
You can see the source code to com.android.launcher here. This particular launcher is ancient, and there is no separate activity for the "apps screen", let alone one that is exported for third-party use. The same holds true for com.android.launcher2.
My question is similar to this one. I'm running Android 4.4 on my device, and want to add additional options to the quick settings. I noticed that turning on/off the Alarm Clock shows/hides a tile in the quick settings, like this:
The biggest difference in the two questions is I want to know what it would take to make it work, either having the device rooted, or flashing a custom app at install or what. I've been trying to browse the source code here, but so far I haven't seen anything that stands out to me.
Sorry about the picture size, I don't know if there's an option to scale them down...
Android N introduced Quick Settings API which allow application to add status icon in quick settings. Please check Android N preview document to learn more.
I'm pretty sure you need to be rooted. I have not come across anything that will let you add tiles under completely stock android. Depending on your phone, you might be able to root it without voiding the warranty explicitly, however it will be tricky. After which you can look at installing something xposed framework and then different xposed modules (I suggest gravity box as it lets you add most options to the quick settings). But again, it's all at your own risk for voiding your warranty or soft-bricking your phone. Good luck!
My company makes industrial manufacturing products and we ship Android tablets with an app to control a manufacturing process. Ideally this should be the only app the user sees, and we've been able to do this on handheld devices running Gingerbread but on Honeycomb and Ice Cream Sandwich the system bar prevents this.
My understanding is that on Jelly Bean there is more programmatic control over the appearance of the System Bar but I'm unclear on the details. I read http://developer.android.com/about/versions/android-4.1.html but it still wasn't clear to me whether there was any way to actually hide the system bar under programmatic control.
We're too small a company to make our own ROM (I'm the only Android developer) so we're trying to work with the stock version of the OS.
Thanks in advance.
it still wasn't clear to me whether there was any way to actually hide the system bar under programmatic control
Not permanently. The JB options to remove the system bar on a tablet only do so temporarily -- any user input will cause the bar to reappear. Hence, it is unsuitable for your scenario.
We're too small a company to make our own ROM
If you don't mind my asking, did you hunt for a consultant or firm to do this and not find anyone (or anyone suitable)? Or did you not pursue that angle? A custom ROM, or at least a root-change-unroot process, would be the right solution for your problem. I can certainly see where hiring a full-time ROM slinger might be overkill, but one hopes that there are ways of outsourcing that work.