Obsolete
Status Update
No update yet.
Comments
dn...@google.com
dn...@google.com
Please provide following information which will help us to investigate this further,
* What is the desired behavior of the feature? (Be specific!)
* If relevant, why are current approaches or workarounds insufficient?
* If relevant, what new use cases will this feature will enable?
* What is the desired behavior of the feature? (Be specific!)
* If relevant, why are current approaches or workarounds insufficient?
* If relevant, what new use cases will this feature will enable?
mm...@commonsware.com
Desired behavior: When the active display feature activates, currently, the only things shown are the time and any pending notification icons. Desired behavior is including the battery percentage somewhere on the active display as well - whether that is in line with the notification icons, or next to the digital clock, or somewhere else on the screen that is easily noticed by the user. Additionally, it may also be desirable for the contents of the active display to be user-customizable - rather than simply deciding if it is on or off, which are the current options. This would apply both to the active display that shows when the user raises their device (under "Moves") and the ambient display that shows when a user receives a new notification.
Sufficiency of current workaround: there are currently no workarounds for this. User must turn on the display to check the current battery percentage.
New use cases: Adding the battery percentage to the active display will allow users to quickly check their battery level without fully turning on the display.
Sufficiency of current workaround: there are currently no workarounds for this. User must turn on the display to check the current battery percentage.
New use cases: Adding the battery percentage to the active display will allow users to quickly check their battery level without fully turning on the display.
Description
* What device are you using? (for example, Pixel XL)
PPP1.180208.014 (Pixel)
PPP1.180208.011 4624533 dev-keys (emulator)
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Run the "Activity Mill" app from the attached project.
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Framework
* What was the expected result?
Either the app to work or for messages to appear in LogCat indicating the nature of the problem
* What was the actual result?
Absolutely nothing. The process is terminated with no obvious logging messages to explain what is going on.
If you remove the android:appComponentFactory="com.commonsware.android.activitymill.ActivityMill" attribute from the <application> element in the manifest, the app runs. But, the point behind this sample is to demonstrate AppComponentFactory.
* Relevant logcat output.
All we see is the standard launching message:
03-09 12:59:55.778 1683-2468/system_process I/ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.commonsware.android.activitymill/.MainActivity} from uid 2000
Nothing related to this process seems to appear after that. No UI is presented.