March, 2014
now browsing by month
Lock Screen keeps disabling.
This happens to me a few times each day, and I now know how to replicate it:-
If I am in an app (app having current focus) and the screen times out or I lock it, and then a notification appears, the lock screen fails to display. From this point onwards the lock screen no longer works unless I reload LLX (selecting the llx icon from the app drawer does it) , or manually navigate to the lock screen page.
Any ideas ?
]]>A few months ago I asked whether it was possible if u could restrict the desktop items from entering the…
Bug with item hierarchy 9.9.14.
Add Panel
Edit panel layout
Items…
Hierarchy…
Item menu
Crash.
]]>I am a noob to LLx and must say it is awesome!
I do have a question that I can’t seem to find here on this community. I see there are notifications for gmail, but I don’t see a way to get notifications from Exchange/ActiveSync. Is this possible using LLx or with scripting in some way?
Thanks!
]]>Hello Pierre Hébert
I was wanting to ask some battery drain questions for various elements. I can’t find the answers online.
1.
How does scale of icons affect battery? Larger drains more battery, but does smaller drain less? There is still the option to zoom, so does scale only matter based on current display – based on zoom?
2.
How much more drain is on an object of it is stretched to fit a screen width and height? Even if the scaling is still 1:1? So the icon is still small, but the size is much larger.
3.
Widgets drain battery based on update interval and size. Does it matter how many elements are inside of a widget if only one element is being updated and the rest are aesthetics? How much more battery does a widget consume based on its size?
4.
How much more battery does it take to place items in a folder instead of on the desktop? Is there a way to keep widgets from updating if they are inside of an unopened folder? Like the way pop up widget or action launcher works to conserve battery? How about all of those questions for panels too?
5.
I know that extra homescreens take up more battery, but llx isn’t like other launchers in that respect. How much more battery drain is there per screen width in use? How much more battery is it for a second or third desktop entirely? Do extra desktops consume full battery if they are not being used? Do widgets on extra desktops update even if not swiped to those desktops?
6.
What are the biggest scripting battery drains? Does an event such as the wheel circling desktop on position event cause heavy drain? Events such as that which are constantly activated by script.
7.
Referring to the landscape of the desktop, does a larger amount of rows and columns on each page consume more battery?
8.
If i want to use a transparent icon over my other icons, what is the best way to create it? Is it best to make a shortcut and strip it, an app and strip it, or a folder and strip it?
9.
Is it faster to use the llx all apps shortcut or the app in the drawer?
10.
Do shortcuts from some apps use less memory? Are they faster? Is it better to use those or launch the app directly?
11.
Cache from llx and other apps can build up. There are cleaners for that, but I’ve heard they are rather unnecessary. However, i notice an increase in performance in llx after cleaning all of my cache. Why is that?
12.
What are some of the biggest reduceable or avoidable battery drains in llx?
Thank you for reading. I can’t seem to find definitive answers online to these questions.
As always, you’re the best Pierre Hébert
Jacob
]]>So, I had to say that to thank Pierre.
I finally build my first own desktop. And with all of LLx functionalities, I couldn’t believe it, but I got rid of UCCW, Zooper, WidgetLocker and tasker…
Well truth is I am not using a lot of widget on screen. And the few I use (calendar, weather and music are fine with apps build in widget). Yet, this is still the first time I’ve build an advanced desktop without needing widget apps to design notification or pop-up/scrollable widgets.
I was quite impressed with how much scripting brought to LLx so I had to congratulate Pierre Hébert
]]>