Related
Hi @all,
in the last weeks with my HTC touch dual, i discovered a worse loss of performance during 1-2 days - resulting in the need of a softreset. Unlike some of you i won't accept a daily softreset as a "must" for a WM device.
Looking into the processes with SKTools, i notice a constantly raising CPU load of the process "shell32.exe", which may need 40% CPU load or more just in idle state, making the phone really laggy. I've read about this somewhere in the web and some forums, but i did not feel everybody is suffering from this issue.
So what about it? As a SMS flat user i'll write many SMS per day with my wife - and this seems to be the crux of the matter. Playing an hour with my phone, opening and closing apps, entering dates and contacts - and shell32.exe is still at 0% in idle mode. Writing and receiving 40-50 SMS and i'm at 20% or more.
I just want to set up an discussion about that ... maybe some of you will have the same problem. And maybe some of the clever guys here will have an idea how to fix this ... the problem still exists in WM6.0 and unfortunately still in 6.1
Any discussion / ideas appreciated ...
İ have the exact same problem and was googling about it finding your comment... when i first boot my device cpu usage is %0 when idle and after sending/receiving around 50-60 sms , it increases up to %25 when idle by shell32.exe . I wonder what's it got to do with cpu ...
"Nice" to read someone else with this problem. It seems, that most people make a restart every day or does not write much SMS.
In holiday, my HTC ran 2 weeks without restart and problems ... but abroad you have to pay for SMS and there were only 5-10 of them. But with a flat ...
It seems that Microsoft still did not noticed these problems ...
I actually do restart everyday my htc prophet as it does reduce battery life having cpu at 20-30%
I guess we can solve this problem by comparing software we use and find what could be the problem. Because ,as there is not a lot people suffering from this, it might be a software issue.
well i heard that shell32.exe was also for today plug-ins , i have only bat.status as today plugin. May be i should disable it and try again... Actually i am abit lazy
You can spend this time to other things ... ... i made all these tries. A "naked" Touch Dual with no plugins makes the same - it's an issue of the operating system and/or the SMS app, which is a part of it.
well then these pdas are just not for sms-lovers Or shall we beg for a fix from microsoft ...
I'm experiencing the same problem. And i'm not a heavy user of SMS.
I think it happens even when not a single SMS have benn sent or received.
It seems to happen since I have flashed a 6.1 ROM.
I remark this because my battery is discharging more than usual.
I have the same problem on my new Palm Treo Pro, even without sms sending. Cpu usage is not that high though, but sometimes the battery is almost empty at the end of the day without doing anything special.
Monitoring power consumptions with BatteryStatus (now HomeScreen++) has a best case of 45mA (still almost double of my P3600) and more often than wanted around 150mA-250mA, with moderate backlight and idle state.
If I remember correctly, the P3600 had a similar issue and that was linked to the radio, it was solved by a newer radio rom. But that my be coincidence or just a total different thing too.
I'm having the same problem with my treo 800w. If i reset my phone to begin the day, about halfway through the day wihtout using the phone at all I will notice the battery dropping rediculously fast. Looking at the processes reveals that shell32.exe is using 20% cpu constantly. After a reset, shell32.exe hovers at 0-2%
I am positive this is what is causing my battery to die so fast.
Hi
I've got a similar problem with my FSC Pocket Loox N560.
I got a RAM extension which additionally needs an upgrade to WM6.1 (at least that's what i got).
When i reset the Loox, everything is fine.
But as soon as the device is switched off to suspend mode and then on again, shell32.exe takes up between 30 and 70% of CPU power. And there is another process, filesys.exe, which uses another 20 to 30%. So in the worst case, the CPU is at about full load and - of course - the processor mode is constantly at turbo mode. The system's reaction is pretty poor then. One can see the sector-colored-circle-thing appearing every 2 seconds on today screen and some other applications.
Haven't found a reason for this. I would be quite happy for now if i only needed to reset the device once per day, but in fact i have to reset it everytime i switch it on.
Does anybody know a reason for this yet?
Greetings, Martin
sipple said:
Hi
I've got a similar problem with my FSC Pocket Loox N560.
I got a RAM extension which additionally needs an upgrade to WM6.1 (at least that's what i got).
When i reset the Loox, everything is fine.
But as soon as the device is switched off to suspend mode and then on again, shell32.exe takes up between 30 and 70% of CPU power. And there is another process, filesys.exe, which uses another 20 to 30%. So in the worst case, the CPU is at about full load and - of course - the processor mode is constantly at turbo mode. The system's reaction is pretty poor then. One can see the sector-colored-circle-thing appearing every 2 seconds on today screen and some other applications.
Haven't found a reason for this. I would be quite happy for now if i only needed to reset the device once per day, but in fact i have to reset it everytime i switch it on.
Does anybody know a reason for this yet?
Greetings, Martin
Click to expand...
Click to collapse
I have the exact problem on same device (FSC LOOX n560). Upraded it to WM6.1 about two weeks ago. Everything was running ok until yesterday, when I installed and then uninstalled latest version of Pocket Informant from WebIS and MyMobiler remote desktop (which I uninstalled right after this problem started, because I thought it is, what's causing it).
My guess is that it has to do with some filesystem errors on storage card (after all it's FAT system, which fragments it's data). I'll try to format my storage card later today, to see if it helps
EDIT: Okay, it seems it was caused by misbehaviour of SPB Pocket Plus v4 program. I uninstalled it and turned my PDA on and off several times and shell32.exe process was still on 0-1%
EDIT2: Well, I made a hard reset and installed everything again, including SPB PP and everything is running ok
Jupiman said:
EDIT: Okay, it seems it was caused by misbehaviour of SPB Pocket Plus v4 program. I uninstalled it and turned my PDA on and off several times and shell32.exe process was still on 0-1%
EDIT2: Well, I made a hard reset and installed everything again, including SPB PP and everything is running ok
Click to expand...
Click to collapse
It was any particular installation order?
1.SPB Pocket Plus v4
2.other software
yep, I installed SPB PP as a first application, then the rest
hey every1
even i am havin d same prob on my htc diamond..but on a minor scale.. I have installed few softwares recently and have noticed dat shell32.exe is taking arnd 0.37 % continously..but i compltly remember that b4 installing and even in all the roms(i have tried many roms) it used to be only at 0% in idle state.. but this is continously taking abt 0-1% which is also affecting me as i wud like to know the reason.so have anyone found the reason and a way to resolve widout a hard reset. bcoz i know once i hard reset its gonaa be normal. but i install many softwares and putting them back is a pain...
hi guys. I have the same problem when I use the usb cable to connect as a masive disk and I finish using or not "extract securely" in my PC.
sorry my english!!
I have this problem too!
when my phone is turning on: shell32.exe=> Ram usage about 2MB, CPU usage 0% or 1%!
after receive several sms, shell32.exe=> Ram usage about 10MB , CPU usage about 40% to 60%!!
I installed "BestTaskMan" and found shell32.exe in processes list, i select it and in menu button i click "Windows list"..
in "Windows list", I found a invisible windows with "Clock Window" name!!
i checked it, each time I receive sms, a "Clock Window" was added tu "Windows list"!!
I think, its the main problem!
My Questions: whats "Clock Window"?
why is it invisble?
why will greate a "Clock Window" when I receive a new sms?!!
How to close it?!
As I suspected early on the issues boil down to corruption within the User Data or Cache partitions, less often on the system partition due to an unexpected shutdown of the device. Shut on these devices need to follow the proper shutdown routine as any linux environment. Following this best practice will ensure that all data is written out to its corresponding file system by flushing all cache, unmounting the file system, etc..
Here are the culprits of why we see so frequent random Force Closes, Market Resetting, etc. ultimately resulting in an unclean shutdown, corrupting some data.
1. The button we use is also a forced off button. Typically if you hold it down too long you are powering off the device.
2. Some times when in sleep mode you see the Viewsonic logo upon starting - that means that the system shutdown (most likely crashed).
3. If your running Vegan your hitting the reboot.. I dont know for sure but I suspect this is NOT performing a clean shutdown... (I dont have a copy of the source)
Anyway... wanted to pass this on... as last night my data partition became corrupt after using the Reboot function on the Poweroff menu of Vega 5.1..
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
roebeet said:
My internal memory has to be repartitioned every few weeks - I'm certain that something is corrupting it over time. I had massive FC's just a week or so back where the SD partition re-do was the only fix.
I suspect that this happens in stock, as well - the problem of course is that there is no fix for a stock user, other than a return / exchange.
Click to expand...
Click to collapse
I have been on stock since I got the device just moving to the newer versions when they come as OTAs and have never ever had to mess with my partition, so I don't THINK the issue is in the stock software. In fact, the only problems I've ever encountered were when I used the enhancement pack, in which case my screen started to become unresponsive and the calibration.ini I was told to try did not work. Since then I went back to 3389 and the device has been perfect ever since.
I could be wrong though and just very, very lucky....here's to hoping. Another thing to consider is maybe the memory is going bonkers for some reason. I've had flash memory that lasted forever and I've had flash memory that has gone wacky over a period of 6 months....even a wipe by the utility designed to do it doesn't fix it properly. I don't know how CWM wipes or partitions the memory, I do know there's supposed to be a special way to do it.
If it's not faulty memory off the bat, then that leaves something in the 'extras' being put into these ROMs. Maybe some of the newer tegra drivers or some coding to make the ROMs faster - I'm just saying, can't leave any stone unturned.
Has anyone that has stayed loyal to stock encountered these issues? We have to ask that question I think. Then we ask how many of the people playing with ROMs are seeing the issues, this would include people that have used CWM to partition and mess with their mounts initially.
I can say I've never seen data disappear from my internal memory or my SD and I can also say I've never seen multiple FCs except after putting in the enh. pack (keep in mind I got my tab on Dec 20something, so I had 3053 and then 3389 soon after).
The first sign of anything being 'corrupted' on it's own at stock and I'll be sending mine back. As an owner of Android since Android's been around, I've never had my G1 or MT4G (or any smartphone before it) become corrupted due to not being shutdown or reboot properly and while this is a tablet I think the fundamentals should be the same. Pampering 'faulty' memory is a risk. You can wipe and re-do all you want, but if it's faulty it's going to stay that way.
Ive done that but I guess you can say unfortunately I have had only clean shutdowns since then... The last corruption I had I formatted my data and cache partitions before I ran logcat.... Of course thought of that afterward....
Generally if any has FCs, etc. etc. run a logcat and post it here... we will be able to confirm this...
We could change the way the partitions are created and add a sync which will further reduce chances BUT will take a performance hit...
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I reviewed the out of the box framework source on the google GIT and technically if a reboot command is given a clean shutdown is performed via the framework... but the widget on the shutdown screen I suspect is not calling the method properly or is not being called at all... All speculation at this point... But for sure there is corruption occurring..
Since the last corruption I switch over to pershoots kernel... Even though his kernel seems to be a little slower he seems to have included the latest drivers which other items relate to data integrity (im reading into the release notes).
NEO: The first thing I did when I got my device install CW, Vegan... Updated Kernels also... Never had an issue until the first time (yes about a day ago) I used the reboot feature of Vegan. That corrupted my user data. I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
But again.. between the wrongly placed power switch, the unprovoked reboots (ie viewsonic screen showing when trying to wake up the device) and the reboot button possibly not performing a proper shutdown will sure increase the chances in a wider distribution of users. So it may not be a CW issue and just some poor design.
When I have time today I will verify if the reboot function performs a clean shutdown... if anyone has the time please post the logcat... Im going to be running around today and will try to get to it..
watson540 said:
shouldnt need source code to debug a dirty shutdown..Cant you just run an adb logcat? maybe run the shutdown command in a terminal on the device and pipe the output into a text file for later viewing
Click to expand...
Click to collapse
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
Click to expand...
Click to collapse
AFAIK they're running yaffs ATM. Next move is to ext4...
Read some articles about this several weeks ago, apparently many apps do not properly flush file caches. One of the articles was a Google developer post about file corruption along with their API method which did a cache flush prior to a close, then a bit later was the Google indication that they were planning to move to ext4 FS to further help alleviate the problem.
stanglx said:
I am very surprised though as the EXT3 filesystem is very resilient to dirty shutdowns (more than EXT4)...
I suspect if you have not been performing clean shutdown then you are just lucky. Linux, like any other OS, even with Journaling if you do not perform a clean shutdown you will surely encounter SOME corruption. Typically the corruption is re-mediated by the the file systems integrity controls. You dont even know it happened... 1 in 1000 the integrity controls can not overcome the significant loss of data and thus results in crashes, etc. Some times the corruption happens in areas where are lightly used thus why you would get a Market Reset... that data is easily replaceable on the fly. Core components that require subsystem to run are not replaceable and thus why I had to reformtat. What upsets me is that this failsafe is not working properly most likely as its far too frequent.... I too suspect it has something to do with CW.
Click to expand...
Click to collapse
That's my point. How many times since we've had our Android and smart phones have we had situations where they are turned off or rebooted without the proper procedures? Power drains till they die, they drop and reboot, we clog them up with stuff or some app drives them nuts and they reboot or shut off....Yet you rarely if ever hear about a phone's data being 'corrupted' with stock software. Sure it may happen with official OTAs etc, but never just off-the-bat like what's happening with the G-Tab. But it's not happening to everyone either so I'm just looking to see if there's a pattern.
Even since the G1 and newer phones, you don't really hear about or see file corruption issues on stock software with these phones. It's when users start going to ROMs that you hear of issues cropping up. That's not to say it doesn't happen at all at stock, I just think we're seeing it in a more concentrated fashion here because of all the formatting, re-partitioning, etc. At first you hear, 4GB is a great partition size, then you hear there are problems so move to 2048, then you hear 256MB swap, then no swap since Android doesn't use it. Then dataloop for speed, then no dataloop because of critical issues. Rules and instructions change almost on a daily basis. I think it's more than these poor flash drives can take I find sometimes it's good to keep it simple.
I owned a Vibrant for a while...decided it was a PoS when at stock I was seeing bad lag (because of Sam's terrible FS). People said...do the speedhack, it'll be fast!, but what was the caveat? Having to reboot the phone almost weekly, sometimes several times a week, and people were seeing what? Data corruption. That's not for me. Give me something that is lag free (doesn't have to be a bullet train, just don't skip on video or audio and make sure my live wallpaper and drawer animation is fluid and I'm happy!). Point being....keeping it simple may help to alleviate some of the issues. If people are seeing these problems with stock, then you're absolutely right and it would be a point of contention that the failsafe isn't working right.
Otherwise it seems the stock OS on these things are able to self correct in most situations and it may just be some of the many tweaked features in these ROMs doing something it shouldn't - or, I may just be very lucky indeed.
I'm still dying to get the OTA - I haven't seen one since 3899 yet.
I've looked around, but can't really find much information about this. When viewing logcat logs(via an app called aLogcat), every 5 to 10 seconds, i get the three errors listed below:
08-24 17:32:14.605 E/TrafficStats( 2906): Tx(pdpbr0) 72
08-24 17:32:14.608 E/TrafficStats( 2906): Rx(pdpbr0) 100
08-24 17:32:14.608 E/TrafficStats( 2906): dpram_stat: pending UL 0 (@4926) pending DL 0 (@5360)
For what it's worth, pid 2906 in the log above points to: com.android.phone
I am currently running on Humble 1.51, with CWM from 08-17(Orange, with restore capability). However, i've noticed this on previous versions of humble/cwm as well. I just did a factory EE4 install via Odin with .pit file, then installed an old humble (1.33) with the same results. I've tried removing the SD card completely, and it still pops up.
If I look at the network usage in Spare Parts, I see that 'Dialer' is always at the top. It sounds like it may be related, as there was a similar discussion in this thread.
Does anyone have ANY idea why the constant "E/TrafficStats" messages might be happening? If not, any idea what I can do to get more information on what is causing it?
I to noticed this and am very curious as to what it is?
I'm not sure what is causing it, unless it is some sort of hardware defect? It makes me feel better that it isn't just me though
Sent from my SCH-I510 using XDA Premium App
it's mainly debugging stuff from what i can tell, and it isn't breaking anything, just annoying when looking through logcats.
The thing is that not everybody gets those messages though. I've seen other charge users' logcats, and they aren't in there, at least not nearly as often. I've noticed that it does seem to be greatly diminished when the phone hasn't recently been used, but not consistently. For example, last night it ran from 11:30 to 2:30 without a single message. Then, it started occurring every 2 to 5 minutes. When the phone is being used though, it is consistently every 5 seconds.
The only way i've found to prevent it is to turn on airplane mode, then restart, as the numbers after pdpbr0 or pdpbr1 are like some sort of counter(they never go down, only up). Obviously, that isn't ideal.
If you have logcat look at the radio buffer instead, you will see messages that coincide in frequency with the trafficstats for "[GsmMultiDCT]NetPollStartTimer: posting again for netStatPollPeriod", with the same UID as the trafficstats.
imnuts, do you know of any tools/apps for me to investigate this further than just looking logs?
You could start decompiling framework .jar files and searching through the resulting smali output for TrafficStats to see what is creating the lines and potentially how to stop them.
Tricks to Make Your Android Smartphone Run Faster
Is Your Android Smartphone isn’t as Fast as it Should be: Here’s 10 steps on how to fix it.
In this fast generation, no one wants a slow phone every one want way to Make Android Phone Run Faster. When you first get your Android smartphone, it seems to work very well, things are fast and fluid responsive. But few months down the line, things started slowing down, many of us now have to settle for one as the hardware grows older, storage space run out, the number of bugs add up and reason for the problem is almost too simple to be true: your Android smartphone does not have the same settings, space and apps it had a when you first got it.
Most Android smartphones are prone to slowing down over time. However, this issue is not unique to Android. Device running iOS also encounter the same problem. The good news is that you don’t have to accept a slow Android smartphone their are way to make Android phone run faster.
Below are tricks and hacks we believe are efficient and effective to make Android phone run faster if you are experiencing a slowdown with your Android smartphone.
You haven’t got enough space
If you want your Android smartphone to run fast, then you’ve to do away with some stuff and junk files eating up space. Delete some apps, text messages, music and videos.
The Version of your OS met be out of date
One of the reason why you may experience slow down with your device is not because it’s old but because the running version of OS is outdated. If your smartphone supports the newest version of OS, updating should make things run faster.
You haven’t turned off your phone for a while
If your phone as being active and on for days without turning it off there are every possibility that this may effect to smooth running of the phone. Turning off your smartphone for a while is good. This will clear up things and shutdown some apps running at the background.
You’ve have too many apps
Too many apps mean too many apps eating up space that will enable your phone run properly. If you are pushing your phone memory to the limit, it’ll slow down. Try uninstalling some app or delete them completely.
You’ve got too many apps running
If you’ve too many apps open and running, there is high chance that your phone will slow down. Tap the minimize button and close all the apps by swiping it to the right side. That should free up some capacity.
You haven’t cleared your cookies for some time
Remember not clearing up your cookies for a long time takes up a lot of space. Clearing them up and staring over again should help make your Android phone run smoothly and faster.
Wipe Cache Partition
The cache partition on your phone contains temporary files which is different from your phone’s actual app data so it’s a good idea to get rid of the cache file every once in a while. Doing this will not only have your smartphone run faster but will also free up some storage. To clear up the cache files, you’ll have to enter your phone recovery mode. Once you’re there, find and select the ‘wipe cache partition’ option and just reboot.
Overclock your Android device
If you’re not satisfied with the overall performance of your smartphone, you can also overclock it. Many manufacturers maintain a low clock speed in order to minimize heat and extend your phone’s battery life. If you have a rooted device or are willing to root it, you can overclock it using an app like SetCPU. It’s not a straightforward process so be sure to follow proper guidelines and proceed with caution.
Too many app trying to access your location
Turn off your location to free up your C.P.U. to do that go-to Setting>Location and swipe the Turn on/off left to turn your device location off.
Do a factory reset
Sometimes, there are just too many things to take care of on your phone that you should just do a factory reset. It’s easier than cleaning up your device and getting rid of all the junk on your phone. By doing a factory reset on your Android phone you will wipe out all files, settings and data on your phone so make sure you’ve done a proper back up of all your files, app, data and settings before embarking on doing a factory reset.
The list above doesn’t necessary fixed up the problem. However, if after carrying out all of the steps and you still experience same problem, if your phone is still within warranty take it back.
Have you experience the same problem with your phone? How did you solve it? Share your experience and how you solve it via the comment box below.
My Laptop is quiet old. The first time I installed Windows 10 on it it was fine, but now it takes at least 90 seconds to shut down and 90 seconds to boot up again. Restarting takes even a longer time, almost 4 minutes. I've tried disabling fast startup, turning High performance on, updating windows, debloating, Tron script, changing settings, virtual memory, startup. It still has a slow boot time, not only that, my clicks aren't as responsive as before. I can't do hardware upgrades because my parents will not pay money, and I don't know if it can be upgraded. Please help. If I try to install a new operating system every file that I have vanishes for some reason, I've tried it before. Should I install my additional antivirus? That's the only thing I haven't done in the solutions list of carbon copied YouTube tutorials. Can anyone help me? I'm quiet desperate this slow Laptop is sucking me out of my sanity, and the hardware requirements match Windows 10.
All OSes have it so that after a long time of use, updates and installing new applications over and over again, they just slow down.
For starters, try a few different online antivirus programs to help clean up your laptop, if they find anything.
If it's an SSD problem, though, do a diagnostic, preferably with your SSD manufacturer's dedicated program.
prash001 said:
My Laptop is quiet old. The first time I installed Windows 10 on it it was fine, but now it takes at least 90 seconds to shut down and 90 seconds to boot up again. Restarting takes even a longer time, almost 4 minutes. I've tried disabling fast startup, turning High performance on, updating windows, debloating, Tron script, changing settings, virtual memory, startup. It still has a slow boot time, not only that, my clicks aren't as responsive as before. I can't do hardware upgrades because my parents will not pay money, and I don't know if it can be upgraded. Please help. If I try to install a new operating system every file that I have vanishes for some reason, I've tried it before. Should I install my additional antivirus? That's the only thing I haven't done in the solutions list of carbon copied YouTube tutorials. Can anyone help me? I'm quiet desperate this slow Laptop is sucking me out of my sanity, and the hardware requirements match Windows 10.
Click to expand...
Click to collapse
use ssd , my laptop only take 3 seconds