What is the correct way to use this to start an application activity with some params ?

Since you use toUri on intent it seems I can't use Parcelable extra since they won't pass this.

I then tried to create intent with a forced action but in the logs it always ends with a no activity found for intent :

E/muzei_MuzeiActivity(1906): android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=movie/759 flg=0x10000000 }

The data is correctly set but not the action :(
The intent is created with new Intent(String action,Uri data) and works without problems in my app.

Very small issue, but I felt in the bug corrected between 0.9 and 1.0 ;)

The wiki link to download jar sends to 0.9 while 1.0 is downloadable on maven and works of course better.

I want to create a settings activity, my activity open above the previous one. How do you replace the previous one like in the 500px extension ?

The wallpaper should be shown as the background for the recent apps menu. When Muzei is used, we can only see a solid black background.

Are any guidelines or examples of the design of the Settings Activity for the plugins?

I'm writing an extension, which pulls the image URLs from a web site. When the URL is formatted incorrectly, Muzei crashes. It should be made more error tolerant. Most of the time this shouldn't be a problem, but if the web site designer changes the site, the code retrieving the image URLs could be bad/incorrect until the extension can be updated.

To duplicate, publish artwork using a URI like "www.example.com".

Here is the stack trace:
03-06 22:48:08.053 20350-5944/? E/AndroidRuntime﹕ FATAL EXCEPTION: IntentService[TaskQueueService]
Process: net.nurik.roman.muzei, PID: 20350
java.lang.NullPointerException
at com.google.android.apps.muzei.util.IOUtil.readFullyWriteToOutputStream(IOUtil.java:210)
at com.google.android.apps.muzei.util.IOUtil.readFullyWriteToFile(IOUtil.java:202)
at com.google.android.apps.muzei.ArtworkCache.maybeDownloadCurrentArtworkSync(ArtworkCache.java:122)
at com.google.android.apps.muzei.TaskQueueService.onHandleIntent(TaskQueueService.java:56)
at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.os.HandlerThread.run(HandlerThread.java:61)

For showing small text like "wikiart.org" or "(C) John Smith"

Hello, I have read a little code about Muzei, very good project to study.

But I have a question while read the sourcecode in SourceState.java, why in setUserCommands() function, need to new a ArrayList, while the variable mUserCommands is already has a ArrayList reference?

Thanks!

I am getting the error when running an example app (based on this example) on my Nexus 4:

cannot instantiate service ... interface ... cannot be instantiated

Searched endless on the line, but could not find a solution, other than the note that an interface cannot be instantiated. But I do not know how to work around it.

More details and code examples here:
http://stackoverflow.com/questions/24070304/android-error-cannot-instantiate-service-interface-cannot-be-instantiated/

I installed the Reddit pics extension and after enabling it I was unable to go back to Featured Art.

If I selected Feature Art, it would show the correct title (Starry Night), but it would still show the picture from the extension. Uninstalling the extension didn't change the wallpaper, and restarting my phone with the extension uninstalled left me with a black wallpaper. I had to clear the data for Muzei to be able to get back to the Featured Art.

Nexus 5, Android 4.4.2

I'll look into this later if you haven't already fixed it.

Do you know why the app is incompatible with both my devices?

Besides dimm and blur saturation would be a nice advanced option. I do not like bright colors on the screen, reducing the saturation would provide that. Sorry, my Java is limited that I can only write an (enhancement) issue and no pull request.

Possibly as easy as overscroll-y:auto instead of visible

Currently the app will load a GIF image, but not set it as a background. Sadly all the other apps for setting GIF's as live wallpapers are not open source. Not to mention they lack muzei's polish!

Thanks

I sometimes find a black section appear briefly in the lower portion of my phones wallpaper, during screen rotations.

This frequently happens after turning the screen back on, and also happens after exiting some apps.

After about a second it fixes itself.

The easiest way to reproduce this I found was as follows:

1. Hold the phone landscape
2. Open the camera app (screen then rotates to landscape)
3. Press the home button (another rotation back to portrait, with a black section in the wallpaper briefly appearing)

It's only a minor thing, but not ideal. I'd like to track down the cause of the delay if possible.

I need to be able to open Muzei's advanced settings within my own settings menu to make it easier to access for my users
!
image

Hello,

Is it possible to add an option to deblur photo when on Lockscreen, then smoothly blur it when the phone is unlocked? Since most people have clean Lockscreens, it would look very well to emphasize the image with full clarity.

Some websites force to give the proper Referer header to fetch high resolution original images. It would be helpful for implementing source extensions for such websites if Artwork class can optionally take a Referer header (or more generally any headers list) to customize.

Thanks!

While integrating Muzei to an app I had this crash, unfortunatly I don't have steps to reproduce. It happend when I was in Muzei app and I was using the next button.

ps: while updating artworks the extension can potentially change the availables custom command (I remove or add commands because we cannot disable/enable them), it is may be related ?
Thanks

E/AndroidRuntime( 8652): java.lang.IndexOutOfBoundsException: Invalid index 3, size is 3
E/AndroidRuntime( 8652):    at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:255)
E/AndroidRuntime( 8652):    at java.util.ArrayList.get(ArrayList.java:308)
E/AndroidRuntime( 8652):    at com.google.android.apps.muzei.api.internal.SourceState.toBundle(SourceState.java:107)
E/AndroidRuntime( 8652):    at com.google.android.apps.muzei.api.MuzeiArtSource.publishCurrentState(MuzeiArtSource.java:696)
E/AndroidRuntime( 8652):    at com.google.android.apps.muzei.api.MuzeiArtSource.publishCurrentState(MuzeiArtSource.java:684)
E/AndroidRuntime( 8652):    at com.google.android.apps.muzei.api.MuzeiArtSource.access$000(MuzeiArtSource.java:190)
E/AndroidRuntime( 8652):    at com.google.android.apps.muzei.api.MuzeiArtSource$1.handleMessage(MuzeiArtSource.java:272)
E/AndroidRuntime( 8652):    at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime( 8652):    at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime( 8652):    at android.app.ActivityThread.main(ActivityThread.java:5017)
E/AndroidRuntime( 8652):    at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime( 8652):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
E/AndroidRuntime( 8652):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)

When setting the wallpaper with the Google Now launcher, I can scroll around the image in order to select the point which will be displayed on the leftmost home screen, which seems to default to the centre of the image.

It would be nice if Muzei had this functionality, at least for the My Photos source. Currently Muzei will always show the leftmost section of the image on the leftmost home screen.

The app "crashed" (black background, had to reactivate it) a couple of times on my Nexus 5, so I decided to have a look at the memory usage from the developer options.
As you can see from the screenshots below, it seems like the app is retaining a lot of memory (almost 90MB), isn't it too much? I didn't had time to do an accurate profiling, but I can do it if you want.
FYI, I'm using it with a static wallpaper from my gallery (so I think you are keeping in memory only 2 images: the original one and the blurred one).

With the stock launcher on a Nexus 5 and only one pane only the far left of the image is visible.

Because the image is likely to be centred on the focal point. It would be nice if the image was centred in the launcher.

(x is the centre)
1 Pane:
[x]

2 Panes:
[ ]x[ ]

3 Panes:
[ ][x][ ]

And so on.

Muzei always downloads wallpapers with any Internet connection - even if this is a non-flatrate, non-stable vor slow connection... If this would be restricted to WLAN , this would be fine :-)

(Mirror: http://i.imgur.com/exolwoT.png)

I think this was an Alarm Managing issue. Yesterday I changed my date to today's date to test a different app. Then today this happened. Ouch. Good thing I was on Wifi!

After a reboot everything went back to normal. Am monitoring the usage now.

Can you add the possibility to Cast pictures using the Chromecast API ?

I'm getting this error with every source, even my own photos. Not sure how to fix this. Tried reinstalling and rebooting, doesn't seem to work

I got this error in my log on the Play Store:

java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:806)
at java.util.HashMap$KeyIterator.next(HashMap.java:833)
at com.google.android.apps.muzei.api.MuzeiArtSource.publishCurrentState(MuzeiArtSource.java:683)
at com.google.android.apps.muzei.api.MuzeiArtSource.access$000(MuzeiArtSource.java:190)
at com.google.android.apps.muzei.api.MuzeiArtSource$1.handleMessage(MuzeiArtSource.java:272)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5102)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)

It happend on this device:

• Android version: Android 4.4
• Device: Moto X (ghost)

It seems that it has something to do with the List object.

Crash stack trace:

E/muzei_GLUtil﹕ Error loading texture (empty texture handle)
    java.lang.Throwable
            at com.google.android.apps.muzei.util.LogUtil.LOGE(LogUtil.java:101)
            at com.google.android.apps.muzei.render.GLUtil.loadTexture(GLUtil.java:95)
            at com.google.android.apps.muzei.render.GLPicture.<init>(GLPicture.java:156)
            at com.google.android.apps.muzei.render.MuzeiBlurRenderer$GLPictureSet.load(MuzeiBlurRenderer.java:335)
            at com.google.android.apps.muzei.render.MuzeiBlurRenderer.setAndConsumeBitmapRegionLoader(MuzeiBlurRenderer.java:256)
            at com.google.android.apps.muzei.render.RenderController$1$1.run(RenderController.java:78)
            at com.google.android.apps.muzei.render.GLTextureView$GLThread.guardedRun(GLTextureView.java:1238)
            at com.google.android.apps.muzei.render.GLTextureView$GLThread.run(GLTextureView.java:1015)
02-12 09:50:39.196  27554-27977/? E/AndroidRuntime﹕ FATAL EXCEPTION: GLThread 1133
    Process: net.nurik.roman.muzei, PID: 27554
    java.lang.RuntimeException: Error loading texture (empty texture handle).
            at com.google.android.apps.muzei.render.GLUtil.loadTexture(GLUtil.java:97)
            at com.google.android.apps.muzei.render.GLPicture.<init>(GLPicture.java:156)
            at com.google.android.apps.muzei.render.MuzeiBlurRenderer$GLPictureSet.load(MuzeiBlurRenderer.java:335)
            at com.google.android.apps.muzei.render.MuzeiBlurRenderer.setAndConsumeBitmapRegionLoader(MuzeiBlurRenderer.java:256)
            at com.google.android.apps.muzei.render.RenderController$1$1.run(RenderController.java:78)
            at com.google.android.apps.muzei.render.GLTextureView$GLThread.guardedRun(GLTextureView.java:1238)
            at com.google.android.apps.muzei.render.GLTextureView$GLThread.run(GLTextureView.java:1015)

Happened on Nexus 4, Android 4.4.2, CM11m3. Built from source (no modifications) on master head.

per http://api.muzei.co/reference/com/google/android/apps/muzei/api/MuzeiArtSource.html, the settingsActivity of a MuzeiArtSource must be exported. This is not important for the Muzei app itself (since it's accessing its own Activity), but for 3rd parties utilizing Muzei extensions this prevents changing the settings of this plugin.

I saw while developping my plugin for Muzei.
I used the fallowing image : https://dl.dropboxusercontent.com/u/43794636/original.jpg
When it is blurred it's good, but when I double tap, the image gets stretch and weird.

I get the same behavior when I'm in the app and not on the launcher.

I confess that the ratio of the image is not perfect for a wallpaper...

I'm running the app on a Nexus 5 running Android version 4.4.2. Below is the list of issues I've encountered, as well as the steps to reproduce:

Blur/Dim settings not working

• After installing (or clearing app data)
• I go through the first launch steps: activate, then view "Settings...", adjust settings, "Set wallpaper"
• Tap the Muzei icon from my launcher
• Browse to dots > customize > advanced settings
• Adjust the sliders and nothing happens. No changes are applied when I click the checkmark.

Additional "Choose Source" options overriding my selected option

• Again, this is after a first run of the app
• Launch app and "choose source"
• Set to My Photos or 3rd party extension (ex: Muzei - Reddit)
• The source will change initially but I can never change it back to Featured Art. If it does change back the image appears missing (shows black).

My only work around for the above has been to force quite, clear data, then restart the app.

I'm loving the app though, great work!

The application crashes when I select a custom source.

Exception when starting activity net.nurik.roman.muzei/com.google.android.apps.muzei.MuzeiActivity
android.os.DeadObjectException
    at android.os.BinderProxy.transact(Native Method)
    at android.app.ApplicationThreadProxy.scheduleLaunchActivity(ApplicationThreadNative.java:750)
    at com.android.server.am.ActivityStackSupervisor.realStartActivityLocked(ActivityStackSupervisor.java:967)
    at com.android.server.am.ActivityStackSupervisor.startSpecificActivityLocked(ActivityStackSupervisor.java:1063)
    at com.android.server.am.ActivityStack.resumeTopActivityLocked(ActivityStack.java:1622)
    at com.android.server.am.ActivityStack.resumeTopActivityLocked(ActivityStack.java:1247)
    at com.android.server.am.ActivityStack.startPausingLocked(ActivityStack.java:805)
    at com.android.server.am.ActivityStack.finishActivityLocked(ActivityStack.java:2455)
    at com.android.server.am.ActivityStack.finishTopRunningActivityLocked(ActivityStack.java:2329)
    at com.android.server.am.ActivityStackSupervisor.finishTopRunningActivityLocked(ActivityStackSupervisor.java:2035)
    at com.android.server.am.ActivityManagerService.handleAppCrashLocked(ActivityManagerService.java:9543)
    at com.android.server.am.ActivityManagerService.makeAppCrashingLocked(ActivityManagerService.java:9436)
    at com.android.server.am.ActivityManagerService.crashApplication(ActivityManagerService.java:10081)
    at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:9632)
    at com.android.server.am.NativeCrashListener$NativeCrashReporter.run(NativeCrashListener.java:86)

On my Samsung Galaxy Note 2014 edition the app freezes completely, when I drag the blur slider all the way to the left. Leaving it around 5-10 pixels to the right works, but the last bit causes it to freeze.
I can't re-enter the app until I manually clear the app data.
The Dim slider works fine

What's up with the dominance of late 19th and early 20th century works in this app? Is this a restriction of some API that you're using? It seems 95% of these paintings are from a period between 1870 and 1920. Occasionally there are some from earlier (e.g. I think there was a Bosch painting recently), but it's a rarity.

There is a way to use use local images already downloaded?
the imageUri method supports only web Uri.

Since most of the wallpapers are wider than a single screen, would it be possible to add an option to automatically pan the wallpaper left and right when navigating through the home screens?

First, I have to say that the issue may come from my implementation.
I'm getting a lot of crash with this stacktrace:

java.util.ConcurrentModificationException
       at java.util.HashMap$HashIterator.nextEntry(HashMap.java:806)
       at java.util.HashMap$KeyIterator.next(HashMap.java:833)
       at com.google.android.apps.muzei.api.MuzeiArtSource.publishCurrentState(MuzeiArtSource.java:683)
       at com.google.android.apps.muzei.api.MuzeiArtSource.access$000(MuzeiArtSource.java:190)
       at com.google.android.apps.muzei.api.MuzeiArtSource$1.handleMessage(MuzeiArtSource.java:272)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:136)
       at android.app.ActivityThread.main(ActivityThread.java:5017)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)

I first thought I call too often setUserCommands method, but I realised that I also had this crash in a version in which I never called it.

Does some other extension developers get this crash?
Did you manage to fix it on your side or does it need a fix in the API?

People with only 2 page on their home screen see only the left part of the image but often the most interesting part is the center of the image. To illustrate, in green the image, in black the home screen's pages and in red the part of the image that won't be visible.

see http://www.reddit.com/r/Android/comments/2enp7r/the_studio_ghibli_muzei_extension_is_the_reason/ck19eji

Could be an option.

Thanks

Hi, I was wondering if it would be possible to have an 'Automated Source Select' option, to cycle through sources?

Reason being that there are a number of sources that would be cool to have as the sources concurrently (e.g. 500px + APOD + NatGeo), but at the moment we can only select one at a time.

Essentially it would an automated version of going into the Muzei settings, selecting a different source, pressing the tick/accept button, and then pressing the 'Set Wallpaper' button.

The way I see it working is that you configure the installed sources as you want them, then enable an 'Automated Source Select' option (under advanced options), which would have the following sub options:

Sources: checklist to select which of the installed sources you want to cycle through (maybe this option isn't necessary, just uninstall sources you don't want)
Select type: select the sources randomly or sequentially
Select frequency: how often to select the sources (minutes or hours etc)

I imagine the pseudo workflow would be something like:

• load Automated Source Select options
• get the source:
  • get array/list of (selected) sources
  • if only 1 source
    • set source = sourceList[0]
  • else
    • if select type == "random"
      • generate random number within array limits
      • set source = sourceList[randNum]
    • if select type == "sequential" / as the default select type
      //would need some playing around with keeping track of the previous source here
      • source = sourceList[previous source + 1] //or wrap around list if at ulimit of array
  • return source
• set the source as the returned source // From a quick look I think its SourceManager.selectSource(source);
• schedule the next update

Muzei with APOD plugin consumed all my mobile data in just few days. 👎 Needed to uninstall it until the issue is resolved. Also in relation I think (but this is subjective) that recent few days (after installing Muzei) the battery was drained faster. Galaxy Note II, stock Android 4.3.

I'd like to request the addition of a widget that displays the wallpaper from Muzei. I use the Aviate launcher and I'd love to use Muzei with it, but the only way Aviate supports backgrounds is with widgets or direct references to image files.

Many times I absentmindedly close the new wallpaper notification, then later decide I want to know more about the featured piece. Is there a place to identify the current wallpaper when the notification is not present? If not, perhaps it could be added to the settings menu.

BTW, this is one of my favorite Android apps. Thanks for making it!

Muzei is utilizing a much higher CPU than expected on the Nexus 9. This also seems to be causing unusual heating of the device near the CPU.

http://i.imgur.com/alu2GHJ.png

http://i.imgur.com/ft972lq.png

As soon as muzei is disabled, the device begins to cool down. Any ideas?

I got this Stacktrace appearing in my Google Play Developer console quite often. I'm downloading Images via URL from a webserver (using most recent Muzei API). Any ideas?

Stacktrace:
java.lang.IndexOutOfBoundsException: Invalid index 1, size is 0
at java.util.ArrayList.throwIndexOutOfBoundsException(ArrayList.java:255)
at java.util.ArrayList.get(ArrayList.java:308)
at com.google.android.apps.muzei.api.internal.SourceState.toBundle(SourceState.java:107)
at com.google.android.apps.muzei.api.MuzeiArtSource.publishCurrentState(MuzeiArtSource.java:696)
at com.google.android.apps.muzei.api.MuzeiArtSource.publishCurrentState(MuzeiArtSource.java:684)
at com.google.android.apps.muzei.api.MuzeiArtSource.access$000(MuzeiArtSource.java:190)
at com.google.android.apps.muzei.api.MuzeiArtSource$1.handleMessage(MuzeiArtSource.java:272)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5118)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:794)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:610)
at dalvik.system.NativeStart.main(Native Method)

As one of the few motion effects that is interesting in motion yet not distracting at rest, I think that a parallax effect would be a perfect final addition to this wallpaper. Would this be feasible? Desirable?

I would like to request the ability to rotate wallpapers as I have a number of landscape images I would like to use.

Thanks

I use folders a lot and see this happen. It's momentary disruption of de-blurring, before the opened app takes over the screen.

The app switcher is broken in the current release of Muzei. Normally, the app switcher is overlaid over a darkened version of the background image. When Muzei is activated, the background simply appears black. Additionally, the animation that transitions from the current view to the app switcher disappears when Muzei is activated.

With Muzei installed Display settings crash on a Lenovo B6000 running 4.2.2.

I'm not sure whether Muzei or Lenovo is at fault here (I'm guessing the latter), but I figured it was worth posting here anyway.

I hope the logs below are of some use.

04-05 13:14:14.383  12702-12702/? E/AndroidRuntime﹕ FATAL EXCEPTION: main
    android.content.res.Resources$NotFoundException: String resource ID #0x0
            at android.content.res.Resources.getText(Resources.java:750)
            at android.content.res.Resources.getString(Resources.java:834)
            at com.android.settings.DisplaySettings.parseString(DisplaySettings.java:663)
            at com.android.settings.DisplaySettings.onResume(DisplaySettings.java:539)
            at android.app.Fragment.performResume(Fragment.java:1738)
            at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:919)
            at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1057)
            at android.app.BackStackRecord.run(BackStackRecord.java:694)
            at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1435)
            at android.app.FragmentManagerImpl$1.run(FragmentManager.java:441)
            at android.os.Handler.handleCallback(Handler.java:725)
            at android.os.Handler.dispatchMessage(Handler.java:92)
            at android.os.Looper.loop(Looper.java:153)
            at android.app.ActivityThread.main(ActivityThread.java:5299)
            at java.lang.reflect.Method.invokeNative(Native Method)
            at java.lang.reflect.Method.invoke(Method.java:511)
            at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
            at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:608)
            at dalvik.system.NativeStart.main(Native Method)

Wikimedia Commons is repository of free licensed images which is mainly used by Wikipedia, would be nice someone looking for an addon idea for muzei (or in the app itself) develop a Wikimedia Commons addon as a source.
Some may helpful info about Wikimedia Commons:

• Almost all images and files on Wikimedia Commons are hierarchical categorized and here are some categories that really worth to see, featured pictures of Wikimedia Commons, paintings by painter category which every category of it has several images
• MediaWiki (the software powered Wikipedia, Wikimedia Commons and ...) has a Special:Random/File page that everytime visited it will raise new page. There is also a random category Special:Random/Category.
• MediaWiki has a lot good API to let its contents be accessed. API:Random
• This is category tree viewer from Category:CommonsRoot which is parent of all categories on Wikimedia Commons. Would be nice if the extension would provide that category viewer first then let user would select the category. that would be most prefect Wikimedia Commons integration that would be possible.

Only tricky part of it IMO would be finding count of images on a category then choosing a random one. Also on some categories or when using Special:Random/File there is a need to filter pictures from other media. So for now using Special:Random/File (or its API) or just surfing the 200 first may would be best.

Anyway this was my idea to build an addon for muzei. I don't feel I have time for that for now and I know this bug tracker is not for addon idea but I raised my idea here so in case someone would pick the idea, would be nice. If you fill this idea is not good or after a while no one picked it, please feel free WON'TFIX it. Thank you