I use a live wallpaper that should react to double taps.
Posted by: pierrot | on December 18, 2014
I use a live wallpaper that should react to double taps. But it seems that the event doesn’t propagate to the live wallpaper from LL. What could went wrong? (It worked at some point in recent past, I’m not sure when did it broke. Btw the LWP is Muzei.)
]]>
Posted in | 32 Comments »
Tags:
« Please explain me what is Panel ? And how can I use it ? (Previous Post)
(Next Post) V10.6b2 »
D5 Creation
< ![CDATA[
It was never implemented đ It requires some simple hooks, but the item which is on the TODO list since a while never managed to get out of this list…
]]>
< ![CDATA[
almost nobody asked for it. i havent seen any requests
]]>
< ![CDATA[
Indeed, very few requests about this, but this is nevertheless quite a handy feature.
I must admit that I stopped to use a LWP and almost forgot about this.
]]>
< ![CDATA[
Interesting… Then this means that the culprit is Muzei itself. As I wrote it worked not so long ago. Both LL and Muzei was updated recently, but the double tap works in other Launchers. That’s why I thought it’s LL.
]]>
< ![CDATA[
Do you mean that double tap on a LWP ever worked with LL ?
]]>
< ![CDATA[
wait llx had a recent update? when was this
]]>
< ![CDATA[
Pierre HĂ©bert Most definitely! I could double tap in Muzei since I started to use it. And I don’t use other launchers. (I have a few installed for debugging – like now – and for a few additional functions.)
Since single tap and touch movement propagation works even now, I guess Muzei used an alternative way to detect double taps, which probably was removed in the last update. There is really no other explanation.
]]>
< ![CDATA[
Interesting. I always thought that the link between the two apps had to be explicitly done. I wonder how a LWP could receive such events without the help of the app wich originally receives them, unless the Android system makes some bridge between them.
Did you receive an Android system update that could help to explain this change in behavior ?
]]>
< ![CDATA[
Curtis Sylvester Jr. yes, 10.6b1 yesterday, but only if you are on the beta channel.
]]>
< ![CDATA[
Pierre HĂ©bert you mean that even single touches shouldn’t work? No, no update, I’m on 4.4.4 with a first gen Moto G, stock ROM. There was no update recently. (I didn’t yet receive 5.0)
]]>
< ![CDATA[
Nothing at all should work đ The launcher receives touch events in this window and is not supposed to give them to any other apps. Even if no action is configured in the launcher, events are processed, so in theory no other window (and app) should receive them. Maybe the Android window manager is nevertheless detecting that a LWP is in use and visible, and then does some sort of event duplication. I am not experienced enough with this to tell for sure, just a supposition.
]]>
< ![CDATA[
That would explain that almost nobody complains about not working wallpaper commands, lol đ
]]>
< ![CDATA[
10.6b1?? you mean to tell me i was removed from beta again??? according to you i should have gotten the update
]]>
< ![CDATA[
Yes probably, usually it takes only a few hours
]]>
< ![CDATA[
ok so how do i get back in again? i forgot
]]>
< ![CDATA[
Have a look at the pinned post, instructions can be found here
]]>
< ![CDATA[
ok found it thanks. i was right, it kicked me out
]]>
< ![CDATA[
Pierre HĂ©bert Try this for an example: lwp https://play.google.com/store/apps/details?id=fixedpointcode.fleya It doesn’t even do anything unless it receives touch events.
]]>
< ![CDATA[
Funny (and not only the wallpaper itself) !
]]>
< ![CDATA[
Events are transmitted even when you touch an icon or the menu by the way, so it really means that Android makes the bridge somewhere.
]]>
< ![CDATA[
i think its just the wallpaper. i have one that should respond to touch but doesnt. but it works on any other launcher. the best would be that a wallpaper mimicking (if thats how you spell it) a touch. ill run a test with some of mine
]]>
< ![CDATA[
ok there is one wallpaper that does react to touch (to simulate scrolling – when selected). it DOES work with llx. another is my famous MULTIPICTURE LIVE WALLPAPER Pierre HĂ©bertâ should remember this as my very first post involved it. but it works too. some wallpapers do and some dont
]]>
< ![CDATA[
Yes, but scrolling is a different thing because it does involves other mechanisms
]]>
< ![CDATA[
but tapping the screen doesnt work. this is not the first case for this issue. the 1st case is buried so it would take 5 criminal investigative agencies to find it but someone else had trouble awhile back and ended up ditching the wallpaper app. still brings me to conclude that not all wallpapers will react well with llx
]]>
< ![CDATA[
Without any doubt.
]]>
< ![CDATA[
It kicked me out aswell Curtis, I was sat waiting for the beta like a goon checking Gplay all the tym basically waiting for something that wasn’t happening :/ I have it now though
]]>
< ![CDATA[
i fell asleep waiting for it jay
]]>
< ![CDATA[
I had to re-up for the beta also.
]]>
< ![CDATA[
Pierre HĂ©bert I’d like to show my support for better support of LWPs. I don’t have a problem yet, but I suspect there will be some in the near future:
I use a LWP named Kustom Live Wallpaper, which is now out of beta and gathering popularity. One of the most anticipated features is reacting to touch input!
If you haven’t heqrd of KLWP, tjen think Zooper with animations and per second changes. It also looks a lot simpler to use than Zooper, UCCW and the others before it (maybe it’s just my experiance now vs then). It’s amazing what can be done with Kustom, so hoping that I can srill use these two awesome apps together!
]]>
< ![CDATA[
Taavo Allikâ could you share the link for the wallpaper please?
]]>
< ![CDATA[
Curtis Sylvester Jr.â
Hopefully i got the full link (on my phone Chrome wants to hide it for some reason):
https://play.google.com/store/apps/details?id=org.kustom.wallpaper
And also here’s a link to the G+ gallery community if anybody wants to see what’s possible with Kustom:
http://goo.gl/bZnEzr
]]>
< ![CDATA[
i just checked.. figures. my device is incompatible
]]>