Using the latest update on the playstore(14.0.2).
Using the latest update on the playstore(14.0.2).
Android 4.4
Unclickable apps are no longer selectable even on edit mode.
On edit mode, shifting your phone in landscape or portrait even if auto rotate is off will slide the edit mode 1 cell down. Kinda irritating when you’re trying to edit while lying down.
]]>« Quite some time ago, someone posted a script with which you can execute a root command. (Previous Post)
(Next Post) V14.1b2 beta »
D5 Creation
< ![CDATA[
If this issue is a bug, it has existed since alpha version…
]]>
< ![CDATA[
I can’t reproduce any of these on a 4.4 device (and neither on 6.0). Which phone is it? Do you use any option that would allow me to see the bugs? They don’t seem to appear in a default setup.
]]>
< ![CDATA[
Pierre Hébert How about in a panel?
]]>
< ![CDATA[
Great ! As simple as that…
Unfortunately I just pushed an update so the fix for this one will go in the next update.
]]>
< ![CDATA[
Settings/app drawer/system bars/on/off/search button.
I tinted the status bar so you can see the difference.Status bar doesn’t remain hidden the moment i press search button although it is hidden in app drawer settings.It‘s moving down covering the search bar.Thank you for a perfect launcher
https://lh3.googleusercontent.com/1CAeLl-WpvJQ780hKV83K1YJ-LQES5URvcUQLAn053LazwFooCLHg33-0UWKzfRyPz5AHNHNQw
]]>
< ![CDATA[
Pierre Hébert You’re welcome 😉
]]>
< ![CDATA[
Silviu Daniel Pierre Hébert
the other new bug?
]]>
< ![CDATA[
App drawer.Status bar hidden
drive.google.com – 20161219_142657.mp4 – Google Drive
]]>
< ![CDATA[
Yeah I forgot to mention it’s inside a panel.
No biggie, found a work around, detaching the item from grid makes it selectable.
]]>
< ![CDATA[
Silviu Daniel weird, the status bar is showing when the keyboard is displayed. I don’t know why. It seems it is enforced by the android system. I’ll try to hide it just after the keyboard is hidden, maybe it will induce some flicker.
Regarding the rotation issue and the slide in edit mode, I have no idea of what happens, this is probably a system specific behavior too.
]]>