System_server draining battery - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

I noticed my battery was draining pretty quickly. I started looking and android system was the culprit. I drilled down further and system_server was using a lot of cpu time. Is this something I can adjust?
Sent from my SM-N910A using Tapatalk

I feel like that process could be a multiple of things and not just one simple thing you can tune or turn off. Have you tried using an app like wakelock detector(root) or cpu spy to try and narrow down the issue to perhaps a certain app causing the issue? Try out greenify to hibernate certain apps if you find them.
Otherwise I found this in another this in another post if that doesn't help you out that you could try...but I'd take and find the culprit first and foremost:
"Developer options > Background process limit > At most 4 processes"

I have wakelock detector installed. I will put cpu spy on.
After digging deeper in wakelock detector I found 2 apps with over 400 wakelocks each. The next closest was only 70. Facebook and Facebook messenger. They have been greenified till I decide whether i am going to uninstall then
Sent from my SM-N910A using Tapatalk

Any way to dig into System_Server?
Good day folks. I've also noticed System_Server severely draining the battery on my Galaxy S5 (2-3% per hour, when it's normally .75%/hour). In the past few weeks, the top Kernel Wakelocks and "Process" wake time (reported by BBS) have been System_Server, Time_Daemon (which I can't find ANY info about), and WakelockManagerTimeout (likewise - no useful info, literally only SIX results on Google). I've also seen "IPC_###_Event0" every now and then, where ### is a Process ID. When I check the PID via Terminal (Cat /proc/*PID*/cmdline) the PID ends up belonging to "System_Server".
To make a Windows comparison, it looks like System_Server is "RunDLL32" or "SVCHost", wherein, numerous processes can "hook" into "System_Server" and are thus disguised behind that process name. Is there anyway to dig deeper into "System_Server" to find the ACTUAL process/service that is causing all these wakelocks? I've also tried GSam Battery Monitor (thanks to - this post) and WLD (Wake Lock Detector) but the most granular any of them get is just "System_Server". As far as I can tell, this did not start as of newly installed software, but it could certainly be due to an update to an existing program. Whatever the cause, though, I need to find out, because a dead phone is useless
Merry Christmas, Happy Holidays

SolidSnakex128 said:
Good day folks. I've also noticed System_Server severely draining the battery on my Galaxy S5 (2-3% per hour, when it's normally .75%/hour). In the past few weeks, the top Kernel Wakelocks and "Process" wake time (reported by BBS) have been System_Server, Time_Daemon (which I can't find ANY info about), and WakelockManagerTimeout (likewise - no useful info, literally only SIX results on Google). I've also seen "IPC_###_Event0" every now and then, where ### is a Process ID. When I check the PID via Terminal (Cat /proc/*PID*/cmdline) the PID ends up belonging to "System_Server".
To make a Windows comparison, it looks like System_Server is "RunDLL32" or "SVCHost", wherein, numerous processes can "hook" into "System_Server" and are thus disguised behind that process name. Is there anyway to dig deeper into "System_Server" to find the ACTUAL process/service that is causing all these wakelocks? I've also tried GSam Battery Monitor (thanks to - this post) and WLD (Wake Lock Detector) but the most granular any of them get is just "System_Server". As far as I can tell, this did not start as of newly installed software, but it could certainly be due to an update to an existing program. Whatever the cause, though, I need to find out, because a dead phone is useless
Merry Christmas, Happy Holidays
Click to expand...
Click to collapse
Hi, i now it is a long time ago but i have the same problem with cm13 now. You find the culprit?
greets

bauita said:
Hi, i now it is a long time ago but i have the same problem with cm13 now. You find the culprit?
greets
Click to expand...
Click to collapse
Good day Bauita - Unfortunately, I didn't find the culprit programmatically. What I noticed, though, was that the drain only occurred while I was at the office, and I also noticed that my phone was frequently bouncing between the actual cell network and a network extender (identified by this: http://forums.androidcentral.com/verizon-samsung-galaxy-s4/307371-little-house-icon.html). I checked around and discovered that our IT department had been testing an extender and left it running accidentally - once they turned it off, my phone stuck with the regular Verizon network and it's been fine since.
So... in your case, you may need to discover a way to look inside System_Server, unfortunately. Good luck and please post back if you do (my apologies for not coming back when I figured it out on my end).

I'm sorry for bumping a ~2 year old topic, but from my googling, this one is the only one that has come closest to nailing this system_server problem. Everywhere you look, people are having the same issues (at least on the surface) but we're all scratching our heads with no apparent way to glean any additional information.
My phone (HTC One M8) has been driving me up the wall with this issue. A few things that I've noticed or think may contribute:
- I live in an area of poor-to-no signal (although my phone performs just as poorly in conditions with good signal)
- I have a terrible Netgear router at home that has this manufacturing defect where the signal is exceptionally weak (but again, the problem persists elsewhere)
- The problem displays on and off, but if my phone has been on for more than a couple of days, it shows up more frequently.
- If I'm in a car (riding as passenger of course), I believe I've noticed my phone lagging more often if I leave the WiFi on and allow it to try and connect to open hotspots as they fly by.
The problem for me specifically shows as heavy lagging in display and input. Even pressing the power button, the screen may not turn off until whatever extremely important thing this is has finished. Interestingly, using my phone right now and listening to music, I've noticed that the music somehow keeps playing despite the lag, as if it's given priority even over input?
But I'd like to look at the internals a little deeper here. According to Systempanel, system_server is the lowest-level process running in the Android VM. My hope is that would make this easier to debug, however as it was pointed out earlier, the exact problem could still really be anything. I'll try to study up more on debugging and see if I can maybe crack this, and even make an app/library to aid other frustrated users.

Related

CM-5.0.5/6: "akmd" alwasy takes up to 3% cpu

guys, I found out that the G-sensor daemon "akmd" alwasy takes up to 3% cpu on my N1 with CM-5.0.5/6.
I compared with stock ERE-27 rom, in which "akmd" in that takes less than 1%.
While during standby, it take no CPU usage.
Does it matter? I mean, would that kill our battery?
Actually I first found that out when I was using CM-5.0.5. One day I put my fully charged N1 beside my pillow and after 7-hr sleep, only 86% power left..
Maybe it has something to do with the 360 degree launcher2.
I personally don't use that feature. I'm gonna take a look at my usage.
I just noticed this as well while tinkering.
Gimpeh said:
I just noticed this as well while tinkering.
Click to expand...
Click to collapse
I realize I'm bumping an older thread now but I still feel this might be relevant.
Running top at any point will still show "/system/bin/akmd" which is the system daemon for the compass.
In my case, it almost always resides underneath "system_server". I've tweeted it at Cyanogen once but got no response to my question.
So, after doing some digging, I pulled down the SDK and fired up the "Dalvik Debug Monitor" here's what I saw (See attached: android-troubleshooting2.jpg)
Edit: i42.tinypic.com/m953rq.jpg
Not that it needed reiterating but the AK8973 is the 3-axis compass chip and something calling it or (the driver itself) is throwing an error almost precisely every 10 seconds. Now, I belive this has only been happening since the upgrade to CM5.0.6-N1 (Although I am now on CM5.0.7-Test1) either way whatever bug there is, still remains.
Edit: i40.tinypic.com/21liauh.jpg
Googling for that error: "Compass driver encountered fatal error2" pulls up a single page in the CyanogenMod Forums and two error logs on PasteBin.
Bump!!-Bumb!!
Thanks for the bump! Being a lurker has it's definite disadvantages.
prophetjinn said:
Maybe it has something to do with the 360 degree launcher2.
I personally don't use that feature. I'm gonna take a look at my usage.
Click to expand...
Click to collapse
In my testing, the use of 360ยบ rotation nor the setting of "Launcher Rotation" changed whether akmd was consuming resources.
Full size image link: i40.tinypic.com/dxh0yu.jpg
Just as GaryD had posted here:
forum.cyanogenmod.com/index.php?/topic/3129-ak8973-compass-driver-encountered-fatal-error2
after a reboot the errors disappear for a while. I don't know the pattern to which they reappear (e.g. due to a buffer overflow or some other reason.)
confirmed...
I think this issue is with newer kernels. I saw it on various versions of CM before switching to enom's TheOfficial rom. Doesn't exist on unmodified versions of enom's rom, but I just loaded several of the newer 2.6.33.x kernels and all show akmd using 1% cpu while the phone is sleeping.
Additionally, power drain while sleeping with these kernels is between 5 and 7 milliamps, while with the stock rom (and enom's stock kernel) it is between 3 and 5 milliamps.
If anyone wonders how I am getting these numbers, I am using OSMonitor (from the market). I sort the processes, reversed, by CPU%. To get the power drain, I look at the dmesg log and filter for the "batt" tag.
I may post this as a new topic for the kernel devs to review if it gets no attention here...
bubbahump said:
I think this issue is with newer kernels. I saw it on various versions of CM before switching to enom's TheOfficial rom. Doesn't exist on unmodified versions of enom's rom, but I just loaded several of the newer 2.5.33.x kernels and all show akmd using 1% cpu while the phone is sleeping.
Additionally, power drain while sleeping with these kernels is between 5 and 7 milliamps, while with the stock rom (and enom's stock kernel) it is between 3 and 5 milliamps.
If anyone wonders how I am getting these numbers, I am using OSMonitor (from the market). I sort the processes, reversed, by CPU%. To get the power drain, I look at the dmesg log and filter for the "batt" tag.
I may post this as a new topic for the kernel devs to review if it gets no attention here...
Click to expand...
Click to collapse
Since I haven't run any other roms I was hesitant to drag anyone else's ROMs into the discussion. I've seen it with InsectrRaven and the Pershoot but they're obviously all pulling from CM's commits on Github. I realize they're not large amounts of cycles but any usage that can be minimized is something. Right? Maybe I'm just a minimalist at heart.
Much appreciated on the bump and the bump towards the devs.
Another confirm here.
I'm on CM5.0.7-test2 with pershoot 2.6.33.4 kernel. Mine was steady at 6% CPU though.
Confirmed..
E/AK8973 ( 101): Compass driver encountered fatal error2 is thrown in every 10 seconds.
CM-5.0.7.1-N1
Kernel 2.6.33.4-cyanogenmod
this TOTALLY makes sense to me. used the stock ROM for last 3 months and had great battery life. after using cyanogen 5.0.7 the last 4 days, battery life is much worse than the stock ROM for me. also different is in cyanogen this "akmd" always shows up in my battery usage, but this never appears in the stock ROM. i'd make a solid bet that this is a cause of the poor battery life on current cyanogenmod, especially if this thing is hitting every 10 seconds with some fatal error. wonder if it can be easily fixed?
I have an EVO, unrooted, no OTA update, fully stock but used the 'top' app to notice the compass /system/bin/akmd consistently using resources.
Disabling auto orientation has fixed it, and done miraculous things for my battery life (battery graphs can have flat lines!), but I want my auto-rotate back. Is this a case of the accelerometer writing out a bad settings file, or it's a bug or what?
I'm still seeing this issue in the latest cyan r c 2 nightly. I'm confused why the compass would be used for the screen orientation. As far as I know, we are talking about 2 different sensors. The phone has a compass sensor, which is akmd, and also has an accelerometer sensor, which is used for auto screen rotation. The compass I thought is only used in things like maps street view and Google sky map.
Regardless, is there any solution to get akmd to stop running all the time? What process is calling this to even run all the time exactly?
I have the exact same problem (though akmd often takes up 80% here) on Hero with CM6 nightly build Aug 19th. I hope I can simply delete the file somehow.
dvfk said:
I have the exact same problem (though akmd often takes up 80% here) on Hero with CM6 nightly build Aug 19th. I hope I can simply delete the file somehow.
Click to expand...
Click to collapse
was same for me.. i had disabled auto-rotating in "settings->display" and in cyganamod settings.. AND in launcher pro.. (i always lay down on the side and the phone flips and i dont like it).. i did this 2 days ago.. and phone been laggy as **** since then. akmd have had 70-99% cpu all the time.. so i turned it all back on again. and now akmd takes 1% wake and 0% sleeping.. so wierdo.. shud be the other way around!
any updates on this?
having the issue as well, can't get rid of it.
please someone let me know.

ok so i could use some help... please...

alright it is with great pain that i am writing this, but i really need some help here. for months i've read the forums, searched for answers, asked little individual questions, IMed with people directly for help... and i'm still having trouble.
i rooted my T-Mobile G1 all the way back when cupcake first came out. everything was great. life was grand. everything ruled. i was a happy android fanboy, talking friends into switching to android, talking crap about iphones... the works... but slowly things started getting slower and slower and slower...
the obvious thing was to wipe and reflash. i was constantly just updating to newer cyanogen roms at that point without wiping. so i wiped to the newest cyanogen at the time (can't remember at this point, but just picture it was like a couple months after cupcake). so things were good again for a little bit, but then it started slowing down again, getting FC's, etc. so a friend recommended i switch to superD... i did, and again, everything was great for a while. i consistently upgraded superD roms (sometimes wiping in between sometimes not). eventually i got to the point where i was on the most recent superD release. it lasted about a day before things started slowing down. examples include when i hit home to exit an application and go to the home screen, the whole screen would either turn black or just show my wallpaper for a good 5 seconds before my home screen would appear, or opening the browser would take like 10 seconds. lots of slow down.
so with the help of a friend i decided to completely wipe and reformat/repartition my sd card. i bought titanium backup but i didn't even bother with it, i said to myself, look, you barely use any of the stuff you have right now, how about just start fresh and reinstall things as you need them manually. so i formatted, repartitioned (using amon Ra's recovery, using the menu option that helps you do it automatically). i made sure i had the most recent radio and spl (this was just a couple months ago), and reflashed the most recent superD (i think its 1.11 if i remember correctly)... again, maybe one day of good performance before everything slowed down. this was also about the time when my battery life started becoming an issue. i'm not exaggerating when i say i couldn't make it home without breaking under 20% battery by the end of the day... and i really don't use my phone THAT much. i'd say i'm a little above average on my usage. i'll get into my widgets and apps in a second, but i really don't use that much stuff...
SO... continuing my story (thanks for sticking with me if you're still reading...). when cyanogens 2.1 for the g1 rom came out (5.0.8d/s) i decided it was time for a change. i reformatted AGAIN, repartioned AGAIN, and flashed 5.0.8. basically, i've got the same story going on. slowdowns, poor battery life, etc.
so here i am with my cyanogen 5.0.8 flashed g1. let me tell you about apps and widgets and stuff. right now i have a regular wallpaper (not live), 14 icons between my 5 screens and just the google search and power management widgets. i used to have calwidget, the genie widget (both news and weather), and the setcpu widgets too, but i decided to take them off to see if it would help with performance. zero help. apps that i either know for sure are always running or i think may have some impact are twidroyd, newsrob, craigsnotif (craigslist notifier), and dealdroid. i don't think any other apps are running and/or do automatic updates for content and stuff like that.
i also use cachemate (purchased) regularly to clear my caches. apps2sd is enabled.
i'm not sure what other information you'd need to help me out, but just let me know and i'll try to give you more details.
right now, i've got slow down like almost all the time. things are constantly pausing, slowing down. i feel like i'm back on my t-mobile mda with winmo5 haha. and forget about it with the battery. i left the house with 90% battery this morning. i went to the gym. went home. picked up lunch. came to work. its been like 4 hours. i currently have 19% battery. all i've done is make 2 phone calls, about a dozen text messages and i've sent 2 tweets (about my battery problem haha). i also used google maps once to look up a number. my wifi and gps is off.
so there we go. really guys, please please please. help me out if you can. any help would be appreciated. i'm so sick of this. and i'm stuck in contract until july 2011. so i'm not getting a new phone any time soon. i gotta figure this thing out.
i really appreciate your help.
thanks.
Dave
OH... and PS... forgot to mention that I just got a new battery this week thinking maybe the battery was just getting old and bad. obviously, no such luck.
I had the same issues till I flashed a SuperD, then everything was fine. I just recently flashed the Froyo from Cyanogen and its like it fixed everything and I'm on a brand new device (knock on wood)!
How old is your G1? Do we know if there are issues with the first run out of the factory? Is that even an issue?
i got the g1 last july. so it was already out for a while at that point. it was new from a store though. i suppose there could be something actually wrong with the phone itself, but i don't know. i was thinking of trying the cyanogen froyo but because its not a stable release yet i figured it would be just this bad or worse...
I promise cm5.0.8 has wonderful battery life when no custom apps are installed and not on any network..
so the question is what is your phone doing, and ought it be doing what it is doing.
There are some nice built in tools for this
Applications->running services
And
Applications -> manage applications (check out the filter in the menu from that screen)
You may be surprised by the apps the think they need to constantly have a service running for some painful trivial job the android API has better interfaces for.. if in addition to that you don't need the app uninstall it.
Otherwise experiment with comp cache and lock launcher in memory.
another example, as i was reading this i was on the phone and i just finished the call and hung up, and i was previously in text messages, it took 12 seconds for my text messages to come up. thats just insane...
as for running services:
- GTalkService <--- I use GTalk all the time
- GenieRefresh Service (Restarting) <--- weird considering I disabled this widget, although I'd LIKE to have it back
- Maps FriendsAppWidgetUpdater (Restarting) <--- never used this in my life
- NewsRob UnreadWidgetProvidor (Restarting) <--- never used the widget before (as a matter of fact, you have to pay to use the widget and i have the free version... weird)
-Twidroyd Background Service <--- understandable, I use this constantly
- AKNotepad Snaptic Update (Restarting) <---- umm... I use this all the time but I don't know why a notepad program would need an updater service running... interesting...
- Swype <---- gotta have that
- CM Updater (Restarting) <--- Don't really think that needs to be on all the time. Can easily manually refresh that...
So that's it. I didn't realize this was included now. Very cool. On older roms I had to use task managers which don't seem to really work. I'm going to stop everything except twidroyd, gtalk and swype right now and see how that does... at the bottom it says Avail: 3.2MB+0.00B in 0 ... Other: 55MB in 4 ... While typing that the Maps FriendsAppWidget just popped back up... I'm gonna see if theres a setting...
In the meantime, does any of this give you any ideas? thank you so much for the advice. Also what does (Restarting) mean?
ezterry said:
Otherwise experiment with comp cache and lock launcher in memory.
Click to expand...
Click to collapse
oh and i have compcache not checked and launcher in memory IS checked... i just tried turning on the compcache option... lets see how that goes...
ok so...
now that i know about those things that were running, i stopped all the ones i don't need, and also went into the apps to see if there was any options for turning off automatic updates, background syncing, etc etc for those things... i'm gonna charge my phone while getting ready to go out and then we'll see how it goes throughout the evening. lets see if i make it home with more than 20% battery left (i'll be gone for like 5 hours). if so then we're on to something here still i find it weird that i can't have a few widgets loaded. but whatever, i'll take a smoothly running phone that lasts all day and i just have to click on icons to get to stuff any day... thanks for the help, i'll let you know how its going tomorrow.
the next day
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
so back to square one... any ideas guys?
thanks so much for any help you can give me. i really really appreciate it.
polarbearmc said:
ok so i tried the compcache and keep launcher in memory options last night, messing with both settings. i found that every possible combination became very unstable other than the one i already had (which was compcache off and launcher in memory on). after trying to shut excessive running services like i mentioned yesterday, and also restarting the phone and then shutting them again, i got NO difference in performance OR battery life...
Click to expand...
Click to collapse
Um... The compcache instability scares me a bit
Compcache has had issues (maybe still does) where the first time you enable it the phone crashes.. but then works fine with Compcache on reboot. Otherwise it really ought no make the phone unstable. (it may or may not speed things up depending on how memory is being used.. usually however it allows 12MB of memory that is rarely used to be compressed, allowing a little more active memory to be utilized) You may want to look into wiping dalvik-cache both on the internal memory and SD card:
Enter console and run (this will restart the phone)
Code:
rm -rf /data/dalvik-cache/*
rm -rf /cache/dalvik-cache/*
rm -rf /sd-ext/dalvik-cache/*
reboot
if you get an error about no files found thats not an issue; but other errors may indicate a problem.
This may help system stability (with or without compcache) .. but won't do anything about the battery life (nor speed unless something was seriously wrong)
-------------------
Unfortunately you will either need to erase all your apps and just run stock CM5 [maybe slowly restore your apps you really need] -- OR -- be very patient and debug whatever application(s) are causing issues on your phone (and maybe complain to the dev for failing to read/understand google's documentation on how to write android applications.. not that some of the google apps haven't quite figured that out until recently)
Thus again the main question is what is running on your phone.. The places I mentioned before allow you to see the services (most of which usually restart if you run the related application again) but not strictly all the details to look for.
Example 1 An widget service is likely holding onto memory starving timer services (those not listed) and swapping out other services (phone/launcher making everything feel slow) At the same time the widget is not very active usually and may not connect to the internet at all; thus may not reduce battery life.
Example 2 An IM client on the other hand may requires a service to keep TCP/IP connections alive, and if not coded properly may be very persistent and cause a slow continual stream of data from your phone requiring a large amount of power to keep the phone on 2G/Edge.
Example 3 A Task killer an kill tasks that re-spawn, or kill a task in use if it doesn't know better causing things to behave in strange ways.. so can killing services/applications from the setting screens btw.. but at least that is a one off by user decision not a automatic operation in the background. Tasks when re-spawned may require more data from the internet thus more power to 2G/Edge
User: Then the one that causes me the most problems: A user that keeps the phone in his/her pocket rather than surfing the web, checking XDA, or continuously checking the battery level is using the device less thus will have longer battery life. (careful to not fall into this trap)
Other Ideas:
SetCPU: set the sleep CPU low in profiles (sleep for me is 245/160)[/*]
Verify End action: Settings->End Button Behavior->Go to sleep[/*]
Set longer periods between polls in applications that poll the net (example twitter every 10 or 20mins.. not 5)[/*]
Larger net transfers on wifi if available (example tell newsrob to sync on wifi only) wifi drains the battery faster than idle, but is much cheaper if larger amounts of data are involved.[/*]
As you can see many things will impact the system. You will need to find the ones eating your battery
Another helpful screen for debugging this may be Settings->Spare Parts->Battery History and Settings->Spare Parts->Usage Statistics
I get between 4h and 12h batter life under semi-normal conditions. 4h = surfing 3g + tappatalk + games.. 12h check email/tweat if i get one.. otherwise stays in my pocket. I've seen my test phone hang out for days on a 2g network without data. (so you can always set your apn type to mms if you just need it to be a phone for many hours.. mms keeps mms support btw)
Ebuddy (and most other MSN/AIM/ect chat clients is frequently one of the biggest problems on my phone.. so if I need more battery those are the first to go.. and whomever it is can poke me on gtalk/txt/or wait
Good luck in your search.. Took me a while to make cm5 work as long as cm4.. most of it was mis-behaving apps that I either know to shut off when I need longer battery life.. or have found replacements for.. or avoid widget functionality if the widget was misconfigured. (

[Q] Samsung Galaxy i9000 freezes on standby

I have had my phone for about 2 weeks now, and this has been an issue since about day 1. I will set my phone aside while doing other things. When I want to use it I pick it up and press the power button to activate the screen. It seems that about 20% of the time the phone is non-responsive. I can't even receive calls/texts/email while it is in this state. I end up pressing the power button for 10 seconds or pulling the battery to get it to reboot. Everything seems to work fine.
I have heard that this could be a result of a reception issue, and that an update would be released in September to solve this issue. Is this information correct? Has the update already been released? I believe I am running the most current version, 2.1 update 1
Is there a software fix? Do I have a defective unit that needs to be sent in for repair? Is there a setting I need to look at? Any assistance would be appreciated.
you are describing the typical scenario of too many background services and apps running taking up too much resources thus making the phone non reponsive
install Auto Run Killer http://forum.xda-developers.com/showpost.php?p=8123924&postcount=40
then tick all the apps to disable reboot your phone
then you can choose which apps you really want to let lose for it to run in the background
It's also entirely possible it's faulty though
I don't think it is a matter of apps running because there are no active apps running when I am not using my phone.
I guess I am looking for an answer that tells me that this is an known issue with this model and I wiould be better off with a different product, or if I will be safe to get it replaced/repaired.
Ideally I would love to hear it is only a matter of a software patch or something similar.
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Well that was a pretty useless post. The only idea my mind is set on is to get my hands on a dependabel phone, preferably the one I have. You suggested too many apps running, fine, but unless they run automatically on reboot and/or the 'active applications' window that runs by default is inacurate, there aren't too many resources being used and nothing running.
you'll be surprised what runs under the hood
you can run this and find out
http://forum.xda-developers.com/showpost.php?p=8156087&postcount=58
Android System Info
another good thing to disable is the Media Scan
AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Don't be so quick to assume your suggestion was correct either, AllGamer:
http://forum.xda-developers.com/showthread.php?t=775017
Thus far nothing in that thread has suggested taxing the system too far. In fact, hardly installing anything at all from a fresh factory reset still has this problem and no one yet has really worked out why aside Samsung saying the hardware is damaged. I was on the phone to them today, same thing said.
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
AllGamer said:
i read that before and the signal theory doesn't hold truth
if that is the case, every time i go to the toilet, or to the stairs in my office building (way deep in the building) you have Zero reception at all, yet I've never experience the freeze on black screen issue.
same goes with walmart, it's true, most walmart warehouse like buildings have extremely poor cell phone reception inside.
assuming that signal is the cause issue is true, then installing this app will prevent that
http://forum.xda-developers.com/showpost.php?p=8172580&postcount=59
Mobile Signal Widget
I'll highly recommend this app for anyone experiencing the issue and are under the impression the signal issue is the cause of the frozen black screen
Click to expand...
Click to collapse
I see no truth in the signal claim I've said why in the other thread. But this is the point, it is an issue a few of us are having from all over the place but as of yet there is absolutely no distinguishable pattern. As I say, a completely fresh phone with official firmware and no installs also has the problems. It's a very frustrating situation because no one can conclusively point to software or hardware yet. Samsung keep saying the same thing, send it in, send it in..
it's true the only way to diagnose those will require to be hands on, and run tests to pin point exactly what is causing that.
Eclair doesn't have the option to auto upgrade, so that's definitely not it
Lag is likely, but what, or which stock apps can cause so much lag?
signal even when the phone is having a hard time switching and scanning for a new signal it shouln't keep the phone unresponsive for such a long period of time unless it's lagging
my Old Treo did that, anytime it lost signal and regained signal there was a minor pause, or a looooooong pause if the phone was lagging
if this is the same case with the SGS we just need to figure out which App is running in the background that is dragging the entire system down.
it could be the internal SD which might have become defective, thus locking up the phone, similar to those people that can't get past the boot screen
i can't think of any other plausible causes at the moment.
Well, I can tell you: having experienced the problem a number of times, it is almost certainly not the lag scenario you have described - this is a proper lock-up. My guess (since it does appear to have some correlation to cell switching, or other signal-related issue) is a bug in the baseband drivers, or something similar, resulting in a panic. I might see if there's any way to get a dump out of this thing to prove it, but at the moment it's just a guess, so I'm not going to tell you that's the definitely the reason, or that you're stupid if you don't agree, even though I'm more qualified to do so, since I've actually experienced the problem.
AllGamer said:
go get an iphone
there is no point helping some one that have their mind already set on their own ideas already
Click to expand...
Click to collapse
Android is designed to not need auto task killers. It is purely a myth that they are needed whatsoever. This is linux we're talking about here, not windows.... It's possible he has a single app installed causing the issue, but the ideal fix would be to figure it out one app at a time and get rid of the faulty app.

Bionic Unexpected Rebooting

[Q]
Out of the blue my Bionic just started rebooting. 8-10 time per day, who knows how may time at night. I am using the stock ROM. I am looking for a stable ROM that I can use to fix the problem. I also have the problem of disapearing apps that I move to the ext card.
Feedback on possible cures will be welcomed.
I just experienced my first unexpected reboot. It was after plugging in my USB to my computer.
This seems like the sort of thing that would have a 50% chance of being related to your hardware, and a 50% chance of an unstable app screwing something up. The stock software is at least stable enough that it's not very likely to be the cause of your issues, and flashing another ROM (which will have the same kernel) won't help if it is a hardware issue.
A factory reset followed by staggered reinstallation of apps (one or two at a time, to see if one in particular might be causing issues) would be my first step for a problem as extreme as random reboots. The next step is through warranty channels. I might even do that first- I don't think I could put up with a phone that rebooted on me.
And the cure for disappearing apps is to not use media area for storage. The phone dedicates 4gb for apps, that should be more than enough until they patch a fix.
i may have to add that my phone was completely stable until i purchased and installed the extended battery then i started to experience reboots and a few locks here and there.
i did a few factory reset on the stock but the phone was still acting up with the new battery.
i then decided to root and run roms and to be frank no locks and or reboots running the same battery that seemed to be causing the problems based on that being the only change to my phone before the reboot and locks.
i am not saying that there is something there with the stock as there would be more reports on this but rooting and going back to stock is a single click now making it a fast process to trouble shoot the software.
i am experiencing a bad or short life with the extended so in my case it could have been the battery screwing up the reads on the software (guess) but the first 3 charge from full to dead just about 3 days after that same extended only last one day.
in general it seemed that my issue could have been a bad battery and wiping data and playing with roms may had help but in the end i will be calling verizon for a battery replacement as i doubt that in two weeks the battery charge for an extended could only last 1 day of medium use.
sorry long response and by no means i'm i encouraging to root and rom just speaking out of my experience.
Hi - first post here. After 4 Thunderbolts - Verizon sent me a Bionic. Much better however, after rooting with 43v3r and de-bloating with The Black Hat App - I'm having random reboots. Initially, the reboots were several times per day increasing in frequency to several times an hour. Y u c k - My Thunderbolt could do that too.
So in troubleshooting:
1 - I've reverted to stock build - no add'l apps: No reboots in 48 hours. So - I doubt it's hardware.
2- After reverting - I then rooted w/43v3R, then debloated - just using stock apps - no reboots in 24 hours. So, I really doubt it's debloating or rooting
3 - After adding a few apps - Stitcher, Enhanced email, SVOX w/voice, Beautiful Widgets (w/clock selected) - I get a reboot.
4 - Remove everything but stitcher. No reboots - 24 hours.
5 - Add Enhanced Email yesterday
Today, I had a reboot.
6 - So culprit 'looks' like Enhanced Email OR perhaps a switching problem between 3/4g (The Thunderbolt - Stitcher used to drop connection in this particular location so, there IS an issue w/3G-4G.
Questions:
1 - If it's not a 3g/4g issue; could it be related to where Enhanced email or Stitcher chooses to install itself?
2 - Is there a log somewhere where I could find 'boot' times and any issues relating to reboots? Like a 'minidump' in Windows...
thanks
I, too, have started having unexpected reboots. I can't pinpoint it exactly, but I have also recently isntalled Enhanced Email (trial version).
Reboot Logger
Hey Google is our friend - don't know why I didn't look before but I found this in Android Market.
"Reboot Logger" by Watanabe,Masayuki.
Just installed it - will report back after Thanksgiving (in the U.S. - Thursday)...
(I would post a link but I'm a noob here - and, now I know why I hate myself.)
Looks like promising -
Have yall installed any themes or different battery icons, or anything like that to yours? Mine is 43v3R rooted with the liberty romv2. I was changing a cpl of the icons and experienced a reboot just out of the blue. I got rid of the icons I changed and stayed with the icons that came with the liberty rom and have no issues at all. I do not have enhanced mail on mine.
most bionics will turn off and wont turn back on till you do a battery pull. Its a known issue, all you have to do is google it and it turns up. From what ive read putting the battery on performance mode and putting on detect in pocket will help. Personally it doesnt help, i had the issue with the stock battery so purchased a extended thinking it was the battery, but after doing research i found out it isnt. They say the new OTA should fix it
icons - reboot logger
Thanks - haven't changed any icons BUT I am using HTC Thunderbolt wallpaper. I had a Thunderbolt that had a reboot problem until the OTA before Gingerbread - Verizon offered me the Bionic when I called about my Thunderbolt issues (I had three replacements - all with the same issues).
I will try different wallpaper -
Reboot logger works well but doesn't offer a clue as to what is causing the reboots. Mine has rebooted 2-3 times per day since I installed Reboot Logger(RL).
3 times a day is tolerable but, I would like to get to the bottom of what's causing it.
What IS helpful with RL is that it does show that the reboots are not occuring in any obvious time sequence.
They may be related to push emails coming in from my Exchange server. Not sure - I'll post more as I learn more. Hopefully the upcoming OTA will fix - though my experience with HTC's OTAs does not give me a lot of hope.
Update - Last night, I uninstalled Stitcher - Stitcher frequently throws errors requiring a FORCE CLOSE. I also have kept Blueooth off.
No reboots in 24 hours -
Will reinstall Stitcher in the morning (I need it at the gym)...
Update tomorrow/Monday
Turned Bluetooth ON - no reboots in 36 hours so, It looks like Stitcher may be the culprit - I wonder if Stitcher has issue with the internal/external SD storage scheme.
As I noted previously, Stitcher reports 'force closes' frequently - especially when it's not even active (when I have not loaded it or used it).
(No sooner than I posted this - my phone rebooted. And again, and again will switch off BT - I'm in my office so, there's could be an issue with 3g/4g switching or other interference...)
Have you tried setting the phone to run strictly 3g? I have had no issues at all with mine jumping back and forth between 3g/4g.. I leave mine on 3g to keep it from trying to search for a 4g signal. I never turn bluetooth on, nor do I ever really use the compass. hmmmm... Can you tell me everything you have done to the phone. Apps you have installed, what ROM you using, if you have .886/.893 etc? I'm willing to see how close we are as for as how our phone's are setup and help as much as I can. I have not had a single issue with mine other then that one reboot after changing the battery icon.
After nearly two weeks of monitoring restarts - it appears that the problem is more related to where I am. At my home, restarts are rare and related to Stitcher.
At work in Beverly Hills, CA; restarts occur frequently. I assume it has something to do with 3g/4G switchover/crossover or interference.
I had lots of problems with the Thunderbolt dropping data connections in 90210. I could not use the hotspot. On the Bionic, the hotspot functions really well. I've used it up north near Fresno in 3G only land, here in BH and at home where I have decent 4G coverage.
When I remove Stitcher, the reboot problem disappears. Sometimes when I 'wake' the phone, there is a dialog apologizing for Stitcher having 'force closed' even if I haven't used it for days. Market reviews indicate anecdotally that Stitcher has a problem with force closes. This behavior must also be at the root of some of the reboots.
I've also set all programs not to update automatically - this may have reduced the reboots as well. On average, I'm getting 2-3 reboots per day. More than I would like but, tolerable.

Some possible problems and concerns about my new Note 5

Hello there,
I recently got a Note 5 and I am coming from a iphone 5s. This is my first android device ever and I am trying to get used to it. Thus, I noticed a few things that bothered me a little bit. When I scroll down faster than usual in apps like facebook, shaman, play store, whatsapp emoji menu etc. I get a laggy/jittery behaviour. Some people mentioned browsing as well but I think samsung browser seems decent, I feel no lag after it completely loads the page. I dont wanna believe that this device cant handle even Facebook app, maybe its a network related problem (I am sitting on a 10-25mb internet depending on where I am). I feel an extremely small stutter when I switch between menus for the first time in simple apps like dialer. I just pop it, for example when I first go to contacts and favourites, it kinda stutters for an extremely short time. I am aware such concerns might sound stupid but I am really not sure how it is supposed to be. Next, I am getting about 5-6 hours of SOT battery life. Location is on (wifi and cellular), android device manager is off, NFC off, wifi is always on where I dont have to use mobile data. I noticed that android system is draining the highest amount just after Screen. Usage was mostly Whatsapp, some facebook, phone settings (since I am trying to figure out stuff), a little bit of gaming and twitch. Brightness is auto and at about %30. I also got a geekbench score of Single Core: 1450ish and Multi Core: 4500ish.
Finally, I wonder if these concerns are expected and possible to solve. I did some reading but unfortunately never had chance to come across to a clarifying explanations to all these things. I thank you in advance for your time taken and effort reading this.
Xulkin1337 said:
Hello there,
I recently got a Note 5 and I am coming from a iphone 5s. This is my first android device ever and I am trying to get used to it. Thus, I noticed a few things that bothered me a little bit. When I scroll down faster than usual in apps like facebook, shaman, play store, whatsapp emoji menu etc. I get a laggy/jittery behaviour. Some people mentioned browsing as well but I think samsung browser seems decent, I feel no lag after it completely loads the page. I dont wanna believe that this device cant handle even Facebook app, maybe its a network related problem (I am sitting on a 10-25mb internet depending on where I am). I feel an extremely small stutter when I switch between menus for the first time in simple apps like dialer. I just pop it, for example when I first go to contacts and favourites, it kinda stutters for an extremely short time. I am aware such concerns might sound stupid but I am really not sure how it is supposed to be. Next, I am getting about 5-6 hours of SOT battery life. Location is on (wifi and cellular), android device manager is off, NFC off, wifi is always on where I dont have to use mobile data. I noticed that android system is draining the highest amount just after Screen. Usage was mostly Whatsapp, some facebook, phone settings (since I am trying to figure out stuff), a little bit of gaming and twitch. Brightness is auto and at about %30. I also got a geekbench score of Single Core: 1450ish and Multi Core: 4500ish.
Finally, I wonder if these concerns are expected and possible to solve. I did some reading but unfortunately never had chance to come across to a clarifying explanations to all these things. I thank you in advance for your time taken and effort reading this.
Click to expand...
Click to collapse
Being an ios and android user, what i can say is android can never(as of now) be as smooth as IOS. This is the truth as android is made to support all the variety of devices, however android users get more customisability more useful free apps and more control over the device they own. 5-6 hours of SOT is considered not bad, it really depends on personal usage i think it is acceptable, i guess the ability to see what your phone is using may be a good or bad thing. For what you know maybe on IOS the system actually drains as much or even more than android just that we are unable to view. hahaha :highfive: cheers not looking for flammers just my two cents.
Thanks for the input =) Hopefully this will be solved with a software update later. Still some confirmation/consultancy will be much appreciated, cheers

Categories

Resources