Hi, looking at my task manager, gwes.exe seems to take up 35000+kb. There is also an x icon next to it in the task manager. I'm thinking it's responsible for the bit of lag I am experiencing. Is there a fix to this?
hi,
what Rom/build/com are you running on you phone?
35 Mb gwes does not seems to be too much.
i used to be about that when working in Com 2 and now mine is much bigger on com3 (23152).
anyway, for an HD2 35 Mb should not be creating lags
gwes renders all the controls like buttons and scroll bars. do you have a high definition skin or something non-standard going on in that area?
Im not on winmo so cant compare with yours, sorry.
Do not worry because of the red (x). It's really the default icon of this file.
thanks for the replies, I was worried because it was abnormally big compared to the other processes. I think it was another app that was causing the lag, I uninstalled it and hd2 runs smoothly now. This morning gwes was at 40MB, but it's not laggy. I have tmous original energy rom installed, com3 I believe--I guess with that build, plus filling up 30 quick links with an analog clock (second hand enabled) provides reasonable excuse for 40mb?
Ok, i have found similar requests on Desire and G2 forums - and have read lots about task killers (on ours and everywhere!!).
So, i see the un/educated opinions on the need to kill apps for performance etc, quite frankly - I don't use a task killer, i have system panel lite just to check on things with from time to time, but kill it when i've finished with it (lol)
What i do find however is that when some apps are pushed to background/sleep by clicking back to exit on 2.1 they can have a fair background usage - today for me it was dolphin and a dictionary app (both responsible for 1-2% use (with bat down to 80% - so they account for 5/10%)
I like to have my core/most used apps easily accessible so for the most part, I appreciate the way android deals with active/inactive apps, But.. For the few apps that i do like/want to use occasionally i would prefer to be able to kill them upon exit
So, on 2.2 roms (definitely Z's, probably others) you can enable this feature/setting. Is it possible to port this ability to 2.1???
Thanks for your time L:
ok, no early takers!! - please pm me if you have any info/suggestions please
Hi all, I have the latest 20110601 aosp cm7 installed on my LG optimus V. I installed autokiller memory optimizer and set it to moderate. I didn't like the app so I hit default. But the default numbers aren't exactly what the numbers were, so what is the numbers that the aosp cm7 put on there? I just need the numbers for the three blanks Hidden app, Content provider, and Empty app.
If another user of this ROM could download this app and tell me the numbers, I would be very thankful.
AutoKiller Memory Optimizer only applies the settings on boot, so as long as you uninstall it, or uncheck apply settings on boot, the default values will not be changed.
Usually it's fine to keep the default task killer settings, especially since O1 has 400MB usable RAM...
why not install every script and app that can be found to get a hell machine?
1.) memory is very optimized through kernel - if you dont know about that, read some posts.
2.) speed is very optimized through the kernel - if you dont know about that, read some posts.
3.) do you know about lowmemorykiller and task priorities? if you dont know abouth that, read some posts.
btw:
where can i download AOSP CM7? do you know something about android versions?
if not, read some posts.
Im running Themer on my Moto X (stock) and sometimes it takes several attempts for a touch to register to open a given module. (Favorites, camers, etc.)
Sometimes it works ok, but sometimes the screen seems unresponsive to touch. I had it show touches in dev options but even 'direct hits' don't register and open whatever the icon is supposed to open. This seems to occur across themes. I do have widgets locked.
Am I missing something here or is this normal?
flyingj said:
Im running Themer on my Moto X (stock) and sometimes it takes several attempts for a touch to register to open a given module. (Favorites, camers, etc.)
Sometimes it works ok, but sometimes the screen seems unresponsive to touch. I had it show touches in dev options but even 'direct hits' don't register and open whatever the icon is supposed to open. This seems to occur across themes. I do have widgets locked.
Am I missing something here or is this normal?
Click to expand...
Click to collapse
Hi,
Try uninstalling Themer - delete the /sdcard/MyColorScreen/ folder (removing the Exported folder within it if you saved any themes) - then reinstall Themer.
Let us know if that helps!
I have the same problem, both before and after doing what is suggested above. The pretty themes with really small or really close selections are the worst at it.
Thank you for responding, I'll give that a try. Though it is possible that with some themes with small target zones may contribute to the issue.
Thank you!
ThemerSupport said:
Hi,
Try uninstalling Themer - delete the /sdcard/MyColorScreen/ folder (removing the Exported folder within it if you saved any themes) - then reinstall Themer.
Let us know if that helps!
Click to expand...
Click to collapse
RED ZMAN said:
I have the same problem, both before and after doing what is suggested above. The pretty themes with really small or really close selections are the worst at it.
Click to expand...
Click to collapse
Could you give us an example? We could try increasing these areas for selection.
Shades of green and coordinate are two perfect examples. I'm using a rooted Nexus 5 running droid Kang. Beautiful themes, but even with the screen showing presses I can be pressing right on something and it doesn't pick it up.
RED ZMAN said:
Shades of green and coordinate are two perfect examples. I'm using a rooted Nexus 5 running droid Kang. Beautiful themes, but even with the screen showing presses I can be pressing right on something and it doesn't pick it up.
Click to expand...
Click to collapse
Thanks for the heads up, will speak to the developers and see what they can do.
I experience the same problem on my Note II running PA.
Is there an official place to request features
Same thing, doesn't seem dependent on theme (happens across all themes I've tried), T-Mo Galaxy Note 3 running stock 4.4.2 (unrooted)
It's hit & miss, sometimes everything works, sometimes it takes 2 or 3 presses before it registers. Seems to be memory related because it generally only happens when returning to the home screen after leaving another app that uses a significant portion of RAM, though I do not have actual evidence of this.
ingenious247 said:
Same thing, doesn't seem dependent on theme (happens across all themes I've tried), T-Mo Galaxy Note 3 running stock 4.4.2 (unrooted)
It's hit & miss, sometimes everything works, sometimes it takes 2 or 3 presses before it registers. Seems to be memory related because it generally only happens when returning to the home screen after leaving another app that uses a significant portion of RAM, though I do not have actual evidence of this.
Click to expand...
Click to collapse
The developers are still looking into reducing RAM usage, hopefully this will be resolved soon.
ThemerSupport said:
The developers are still looking into reducing RAM usage, hopefully this will be resolved soon.
Click to expand...
Click to collapse
I believe this will solve the non-registering touches.
I don't think it's grid/sensitivity related, I really think it's the RAM issue.
ingenious247 said:
I believe this will solve the non-registering touches.
I don't think it's grid/sensitivity related, I really think it's the RAM issue.
Click to expand...
Click to collapse
On my device it appears to be related to adding the dock feature or persistent search box. Adding either appears to cause the problem and then removing them causes the problem to be alleviated. I ran up my RAM usage to near 90% without any problems (without the dock or search).
Another bug I would love to see fixed is Themer retaining the dock and search features when applying a new theme. It is annoying having to reconfigure the options and add everything back to the dock each time.
Edit:
I'm going to add my feature requests/changes here since I can't find a specific thread for it.
App drawer:
Horizontal or vertical scroll options perhaps with a paginated option for both
Allow Themer icon to be swapped for the play store icon
Allow for the removal of the tabs at the top entirely
Launcher screens:
Allow custom smart categories and/or folders to be used by widgets (maybe the news icon could open a folder or category I've created to show all my news apps instead of launching the themer news app only)
Allow reordering of home screens (perhaps even allow adding multiple themes at one time next to each other)
Retain custom added home screen folders and icons when changing themes
Give end user access to icons used by the theme so when customizing an icon I can use one built into my theme (I like the dialer in my dock but I would love to use my theme's dialer icon instead of the default android one)
As mentioned above:
Retain dock and persistent search options between themes but also allow themes to better resize when those options are selected (some themes get cut off slightly or the aspect ratio gets out of whack)
Hopefully that doesn't sound too demanding. I'm just trying to help make an awesome concept better
Wetzel402 said:
On my device it appears to be related to adding the dock feature or persistent search box. Adding either appears to cause the problem and then removing them causes the problem to be alleviated. I ran up my RAM usage to near 90% without any problems (without the dock or search).
Another bug I would love to see fixed is Themer retaining the dock and search features when applying a new theme. It is annoying having to reconfigure the options and add everything back to the dock each time.
Click to expand...
Click to collapse
Agreed (Bold), I would like the notification bar auto-hide to stay selected when I change themes. However, because each theme requires a different configuration to work/look properly, this might not be ideal.
For me, the problem only happens when the launcher is trying to "catch up". This indicates a memory issue IMO. Anytime the launcher is fully loaded and I'm on the main home screen(s), I do not experience any issues registering touch.
Perhaps that is the problem then. I don't use Themer as a daily driver just yet because there are a few thing I need sorted out first. The touch issue in this thread being one of them. Folder/custom smart categories, mentioned in my edit above, are another.
This also happens when I use the gesture system(Swiping up/down). Personally this is the least fluid launcher I have ever used, sad seeing that its my favorite.
I know themer is still beta but this problem has been happening for a long time now.
On the gestures, I agree there is definitely an issue.
When attempting to do the "two fingers down" or "two fingers up", it generally triggers the "pinch in" gesture. This is the only launcher I have experienced this problem with. It's not make-or-break as I know it's beta, but accurate gestures are very important to me with the way I use my phone.
I expect these will get fine tuned before they transition out of beta
I'll have to rescind my former statement(s). I did more testing
There are definitely issues with touch not registering on some themes. As I tried more and more themes, I started to see it more and more. And it's bad. 2-3 times minimum to get the touches to register, especially on the Tron looking theme (I forget it's name). There are many more themes with this issue as well, and it appears over time the more cache/data stored in the MyColorScreen folder, the less responsive the launcher becomes. It got to the point of being unusable until I uninstalled, deleted the folder and reinstalled.
This, coupled with the intense RAM usage and pretty aggressive battery drain (10-12% daily, minimum) and I have to hold off on using Themer for now.
I'm not against sacrificing one or two minor things, but to sacrifice device response + RAM + Battery is too much just to use Themer. I will wait and watch and as improvements are made I will reinstall and retry.
ingenious247 said:
I'll have to rescind my former statement(s). I did more testing
There are definitely issues with touch not registering on some themes. As I tried more and more themes, I started to see it more and more. And it's bad. 2-3 times minimum to get the touches to register, especially on the Tron looking theme (I forget it's name). There are many more themes with this issue as well, and it appears over time the more cache/data stored in the MyColorScreen folder, the less responsive the launcher becomes. It got to the point of being unusable until I uninstalled, deleted the folder and reinstalled.
This, coupled with the intense RAM usage and pretty aggressive battery drain (10-12% daily, minimum) and I have to hold off on using Themer for now.
I'm not against sacrificing one or two minor things, but to sacrifice device response + RAM + Battery is too much just to use Themer. I will wait and watch and as improvements are made I will reinstall and retry.
Click to expand...
Click to collapse
Hi,
Could you possibly provide us with some more details? What device/Android version/ROM are you using?
Also, which themes are doing this?
T-Mobile Galaxy Note 3, running stock 4.4.2, unrooted. For Theme specifics, I will have to reinstall and test for a few days. I will get back to you.