Hi app drawer bug
Hi app drawer bug
Drawer extremely laggy when scrolling
Using galaxy note 3
]]>« Is it possible to set a custom screen timeout for the lock screen (Previous Post)
(Next Post) I just discover this little tool in the app store. »
D5 Creation
< ![CDATA[
Might be a good idea to mention what Android version your on aswell as which ROM,
Im also using a Note 3 and its not laggy on my phone.
Android 4.4 CM11 Latest Nightly.
]]>
< ![CDATA[
If you make the icons or text transparent it will cause lag. Says so in the option to do so. Check the + box in options
]]>
< ![CDATA[
Hmm… that’s not really what it says.
It says “May affect performance”.
No noticeable hit to performance on my old crappy single core device… so your mileage may vary.
]]>
< ![CDATA[
It did on my stock s4. Was a little mad that it affected it too much cause it looked really cool with my live plasma wallpaper!
]]>
< ![CDATA[
AT&T stock 4.3
]]>
< ![CDATA[
Sorry
]]>
< ![CDATA[
Hmm it never lagged on stock 4.3 for me either, might be worth mentioning that I always disable the system animations in developer settings. I class them as lag and I don’t need them the only animations I like to see are in the launcher. I also usually make my drawer text only but when I do use icons I set the scale to less than 100 usually 80 i dont no if it makes any difference ( I no scaling icons up uses more memory) but I’ve never experienced any lag in this launcher.while your waiting for the dev to reply try setting your draw to text only and see if it still lags oh and turn off decelerate scrolling and put it on disabled. This is how my drawer is right now. See if makes any difference.
]]>
< ![CDATA[
The only time my app drawer lags is if I apply a transparency to the items in it. Otherwise it is smooth as butter. Did some experimenting and turned off my live wallpaper and system animations and also turned off decelerate as suggested by Jay M. The lag still exists if and only if I apply a transparency to all the icons. It also occurs in a scrollable folder if I apply a transparency to the icons in the folder. So when the developer said “‘might’ affect performance”, he knows that certain design preferences of the user may affect performance because of whatever process is used to gather the info from what is behind the icon add the color of the icon and display. The only thing I didn’t try was a black background but what then would be the point of transparency, icons would just seem faint.
]]>
< ![CDATA[
Samuel R, silly question, are you using latest version 9.22? Developer made scrolling smooth as butter with the 9.1 upgrade!
If so, check that you have transparency off. App drawer –》Items –》 + –》Transparency –》255
]]>
< ![CDATA[
I’ve changed the scaling and it’s much better now
It was at to 120
Thanks everyone
]]>
< ![CDATA[
Yeah increasing the scale of icons uses more memory. That’s why when ever I use icons in my drawer I stick to below 100
From the help text.
Keep in mind that enlarging icons will require much more memory, because the number of pixels is the square of the icon dimension.
]]>
< ![CDATA[
Chris Chastain indeed, older CPU and older software doesn’t necessarily mean bad performances.
In this particular case, some “accelerated” drawing operations in use on newer devices are actually MUCH slower that the equivalent software ones, simply because OpenGL (used to draw starting at android 3.x) is designed for 3D, not 2D.
The previous software only implementation was a pure jewel. The addition of hardware acceleration was a necessity. But I am not too sure that everybody likes it.
]]>
< ![CDATA[
So if scaling up increases memory does scaling down from 100 reduce it or doesn’t it make any difference.
]]>
< ![CDATA[
Jay M not always, because sometimes it is linked with a threshold : for instance images are stored as textures in the GPU memory. If for some reason the GPU hasn’t enough memory to store images, then the system will start to constantly swap images from the main memory to the GPU memory, and it will suddenly decrease performances by 10x. I don’t know whether this is specifically the case here, but this is just an example of something that could happen.
]]>
< ![CDATA[
Pierre Hébert, thank you for the replies to my, and Jay M questions. Very informative.
]]>