Related
I'd like to know if anyone is having the same lag problems as I am getting from time to time..
The lag happens for no reason and comes at different times while doing different things.
I downloaded Watchtower from the Android Market to monitor what was happening. When the phone is running fast the /INIT process is showing as 0%..as soon as the lag starts to happen I check Watchtower again and the /INIT process is at anywhere from 70% to 100% CPU usage.
I dont use an app killer but I donwloaded one to try and see if it would correct the problem, it doesn't. The only way to solve the lag is to Restart the phone, then its fine for the rest of the day, sometimes two days but it always comes back.
I sold my SGS because of the lag issue and now it seems I have it with the DHD..
I did google this and I found that it maybe something to do with android itself..looks like /INIT is an android process..
If you notice your DHD lagging then download Watchtower and I'd bet you will see the /INIT process killing your phone..
------------------------------------------------------------------------------------------------------------------------------------
EDIT - A fix has been found to stop the /Init process lagging the phone.
On your phone go to..
Menu/settings/applications/development/now turn on Usb debugging..
This seems to keep the / init process at 0% CPU usage, it also works when the /INIT problem starts, turning USB debugging on will make the /INIT process drop back to 0%, very nice to see.
Ive contacted the Dev to find out if he can tell us why this method has fixed the problem.
Still need an update from Htc but at least we can use our phones again..
There doesn't seem to be any negative effects from turning this option on, the only thing to note is turning it off to connect to your pc could bring the /init process back and lag your phone. You can download Android Manager from the market for free which will allow you to transfer data from your pc using Wi-Fi, using this app you can keep the USB Debugging on.
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 2 - It looks like you can connect to the pc via USB cable with the debugging turned on without problems, the only difference is that it will try and install additional drivers...because of the debugging mode..
Im using windows 7 and the ABD driver wont install...you need to download Htc Sync on your pc which downloads the ABD driver !!
We should also watch the battery as this may actually increase battery life...
-------------------------------------------------------------------------------------------------------------------------------------
EDIT 3 - Not one single person has come back to me and said that the /INIT problem has returned after this fix...lets hope it stays that way.. 10/11/10
---------------------------------------------------------------------------------------------------------------------------------------------------
EDIT 4 - A lot of people including myself have found that this fix improves their battery life quite a bit.
-----------------------------------------------------------------------------
Last EDIT before thread is locked just for reference and to help people !!!
For people that have the com.htc.bgp process that loads the CPU it stays at 80-90% all the time, and i have autosync on, if you stop auto sync the process goes out....
So here is the final fix in the link below (post 7)
http://forum.xda-developers.com/showthread.php?t=659325
Thank you to everyone in this thread for there efforts...amazing response.
Thanks to all the XDA Community...Including the Devs and Mods
Thread Closed
nednapalm said:
I'm getting the problem.
No apps installed except the flash and maps update, oh and OS Monitor.
Have turned off "Fast Boot" and removed battery to reset, ok for now. Very scared to start installing more apps, nearly unusable when it is lagging
Click to expand...
Click to collapse
I also tried the "turn off fast boot and it was ok for 2 days, it came back this morning though..It is very worrying and yes, the phone is unusable until it is Restarted..Thanks for the reply.
sanju007 said:
LAG WHAT?
I hope not, the samsung galaxy s have lag issus and its very bad and i sold de sgs
And now the DHD gets also lag problems ?
Ik hope not, then i will not buy this phone
Maybe an good task killer wil help ?
More people have lag issus ?
Can you make a video ?
Click to expand...
Click to collapse
An app killer doesn't solve the problem and Im unsure how many people are having this problem, to my understanding its not many...that's why I started this thread to try and find out.
I wouldn't worry yet...
I will make a video when it happens again...it may take a few days to come back....but it always does...a video added to this thread would be most useful...just have to wait till it rears its ugly head again.
So it seems that /init is a core process regarding the initialisation of the Android system and userspace hence the fact it cannot be killed using OSMonitor. It is always the first process that runs on Linux systems after boot and acts as a parent process which itself initialises then processes needed to get the OS going.
Here is a description of the Android Init Process from elinux,
'init'
A key component of the Android bootup sequence is the program 'init', which is a specialized program for initializing elements of the Android system. Unlike other Linux systems (embedded or otherwise), Android uses its own initialization program. (Linux desktop systems have historically used some combination of /etc/inittab and sysV init levels - e.g. /etc/rc.d/init.d with symlinks in /etc/rc.d/rc.[2345]). Some embedded Linux systems use simplified forms of these -- such as the init program included in busybox, which processes a limited form of /etc/inittab, or a direct invocation of a shell script or small program to do fixed initialization steps.
The init program processes two files, executing the commands it finds in them, called 'init.rc' and 'init.<machine_name>.rc', where <machine_name> is the name of the hardware that Android is running on. (Usually, this is a code word. The name of the HTC1 hardware for the ADP1 is 'trout', and the name of the emulator is 'goldfish'.
the 'init.rc' file is intended to provide the generic initialization instructions, while the 'init.<machine_name>.rc' file is intended to provide the machine-specific initialization instructions.
The Bug
The /init bug has presented itself on numerous handsets including the HTC Desire, Nexus One and Droid X models. It seems to be specific to Android 2.2 and reports the same symptoms on all handsets. Primarily this is due the 99% CPU usage causing system slowdown and left unchecked, high battery usage. It is not specific to HTC Sense ROMs as it also presents itself on stock releases. The only solution so far is a reboot. Hard Reboots and altering system settings seem to have no effect on the reproduction of this bug.
I can only speculate to what is causing the issue and hopefully a Dev can shed some more light.
Logically it seems as though a 'rogue' process is triggering /init to resume its primary function in regards to checking filesystems and attempting to spawn other system process. Due to some form of miscommunication between the processes in question, /init continues to perform these post boot tasks in a constant loop.
Think of it like this, if you try perform tasks straight after boot, the phone is unresponsive while the SD is mounted/checked and all other processes are fired up. The /init process is responsible for these tasks. If it were to loop, you would experience the symptoms we are having.
I found this on Wikipedia:
After /init has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen:- processes it started to end or die, a power failure signal[clarification needed], or a request via /sbin/telinit to further change the runlevel.
So our trigger should hopefully be narrowed down to these three events.
Regarding what I posted before, the connection between sync and the bug has proven itself to be a false one.
I've also noticed that sometimes the bug can be present, however there is little impact on the responsiveness of the OS. It can seem as though everything is ok yet the CPU load can be extremely high, resulting in poor battery performance.
Anyway, hopefully more people can contribute to this thread so we can build up a better picture of what is going on. I will also try and grab a Logcat and ask anyone else near their PC when it happens to do the same.
There is a thread here which has users complaining of the same problems, yet no solutions are presented. Hopefully we can make a bit more noise and get some definitive answers.
Regards.
Hey guys some great feedback here, as with my link on starting this thread the /INIT is an android 2.2 process, auto sync on/off doesn't solve the problem neither does a hard reset, taking the battery out ect...
The guy in the link says his method worked for him, can't say the same for myself, I have a feeling his problem will be back...but if it did fix it for him then thats great, just cant say the same for me
http://forum.xda-developers.com/show...3&postcount=42
I have gone 5 days without the problem coming back and then Oh no its back, sometimes it happens twice a day, all the above doesn't fix this problem im afraid from what I have experience anyway.
The /INIT process is only 132k, something so small causes the phone to be basically unusable....very frustrating.
The 1.32.405.6 update also doesn't solve this problem, I updated yesterday and 10 min later I had the dreaded /INIT problem...
The so called "turn off fast boot doesn't fix the problem either, I have had the /INIT lag problem with it switched on and off...
What I find to be the most strangest thing is that if this is indeed an android process which it most likely is then why doesn't every DHD phone have this lag from time to time???.....why only certain phones??..
I haven't had the problem since yesterday (around 12 midday), when it occurs again I will be posting a video as requested...
The mystery continues.......There is NO solution as yet that fixes this problem.
Thanks to Lynxboy, your posts give some good information.
I wonder if this has any relevance to the problem from a linux based PC..
It seems that /INIT uses the same Process ID - 1 (found from using watchtower)
http://www.yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html
BigMango said:
You purchased it from ebay, but did you buy it from a shop or from an individual (second hand)?
If you got it from an ebay shop they should give you a receipt. If it was from an individual, he should give you his original receipt (that's when the warranty started).
Anyway, the phone has a 2 years warranty, so you are covered for the next 2 years minus 1 or 2 weeks. And the paypal transaction is a valid payment receipt (it can be verified directly with paypal); so even without the receipt from the first owner HTC should cover you since the phone can't be 2 years old.
Get in touch with HTC directly, they should replace it. But the tricky part is that the problem must happen when they check it out, for this reason I would also make a video of the problem the next time it happens and send it to them by email so they can keep it on file with your RMA.
Click to expand...
Click to collapse
Thanks for the advice, Im going to contact the seller, he had it on upgrade and shipped it to me the following day..he seemed a nice guy so It should be ok...Now its just a matter of waiting for MR INIT to show up haha....wonder if he wears a hoodie LOL
bimmerfox said:
I'm not wrong because I see it with my own eyes. Even my DHD had the same problems as described. After the update no more /INIT at 90% and it keeps running smooth now.
Try to keep your patience before quoting a person who is willing to help others.
Click to expand...
Click to collapse
What?? Why do you think I made this thread...to help myself and others...as we do at XDA....the update doesn't fix the problem....just because yours hasn't lagged since the update doesn't mean its fixed....I've gone 5 days with no lag and it came back...like yours probably will.
Ridiculous....
EDIT- You can't post a statement that the problem as been fixed when numerous people have done the update and still experienced the /INIT problem...how can it be fixed??...and since the update only came out yesterday you have no way of knowing this for sure... its way to early to say that.. Try reading through posts in the forum and gather some information next time.... the update was for the youtube fix, we're not even sure that HTC were aware of the problem at the time.
Hi guys,
Just finished work and have caught up with the thread since I last posted and wanted to clarify a few things. I would also ask any new readers to find my previous post which covers much of the nature of the /init process.
The problem is solely software based. The hardware is NOT at fault!
The /init process is the parent process of Android/Linux, hence the PID 1 in OS Monitor. Imagine it as the ignition system in your car. You need to turn the ignition to fire up the other systems and that technically is the role /init takes.
It is not a rogue process in itself. It cannot be killed or closed via a task manager.
The latest update was not a fix nor does it resolve the issue.
The bug IS a Froyo bug and affects numerous devices not just the DHD although it is not present in all Froyo ROMs.
It is possible the memory management is to blame however I have run many Froyo based ROMs from FRF55 and not experienced it before; they all use the same memory management.
The three triggers for /init to awaken after its boot tasks are completed are specified in my previous post. These are the most likely causes for our issue and are in my mind triggered by some rogue process interactions.
A logcat will only really be useful if it captures the event taking place. A logcat taken when the /init process has started will report back specifically that.
Just because you haven't experienced the bug in 2days doesn't mean you are bug free, nor is there a bad batch of phones as this would indicate a hardware issue.
Continuing this thought, it is possible if you are on a branded operator ROM you may be bug free.
The /init bug is extremely annoying.
Regards.
Yes off topic...
Im asking the mod to still keep this a sticky but to lock the thread as there is really nothing left to discuss and its just here for people that are still having the /init problem as a reference...
EDIT - Thread being locked soon so....
Agian thanks to all xda community !!
Is this stickie needed anymore? Has this been corrected by any software update?
I've had this problem since the day I got the phone (December 2010) and got it again today. Once I see the obvious lag of everything, I just restart.
If it can help...
I have noticed this phenomenon the first time just after installing 2 things in my DHD :
- creating the HTCSense account (and keeping it synchronized one a day)
- installing the HTC plugin for Picasa Web Albums in the Album application.
Maybe coïncidence, maybe not.
I have disabled all HTC Sense stuff I can see. It always happens when performing some action, like opening a new app. It seems to occur so randomly, it happened again the day after my last post, but has been fine since then.
Problems with calendar after removing cache and program data.
I had major problems with com.htc.bgp using up to about 90% of my processor from time to time. When I searched the forums I found this thread.
I tried what is stated in the top post and went ahead and cleared the calendar data and the gmaill data. This is all fine, I don't seem to get any more warnings about com.htc.bgp reaching the 90% mark. One slight problem that occured though is that now when I'm syncing my calendar back to what it was, it either does not search or does not find all the other calendars that I have. The list is just totally empty. Strange as it is, It does find and sync with the default [email protected] Gmail's working fine and syncing properly though.
Since I rely on the calendar I really need this to be fixed as soon as possible.
I don't want to put words in your mouths, but I figured I might need to factory reset the phone. No biggie, but a time consumer, since I need to recustomize everything again (not rooted, not titanium).
Are there any ways of luring the calendar back on track. Jumpstarting it without a factory reset?
Thanks in advance.
Henrik
So apparently all it needed was a full night of syncing, because now it works again.
It seems though that I got rid of the annoying com.HTC.bgp that drained my processor.
Thanks to the thread
Sent from my Desire HD using XDA App
Have not experienced this since the 2.3.3 upgrade, problem solved!
I'm having this problem on my Defy after installing SetVsel, setting any values, after time the cpu stuck at 100. Watchdog lite didn't show nothing but 100%, not any process higher than 50 even. I turned on in the watchdog to show system processes and ther it showed that:
init
Linux process
Had most the time the highest percent used
I googled and found this topic. The
Menu/settings/applications/development/now turn on Usb debugging.
Click to expand...
Click to collapse
solution solved my problem. The proc isn't anymroe stuck at 100%.
Hi Folks:
Is anyone else having this problem?
New Info as of 16 July. Sound Still Skipping
Unfortunately, I'm still having sound file skips when the tablet is off.
I did some more Google research on this, and I found several instances with regard to phones having sound problems with skipping and popping sounds while playing. Nearly all of those seemed to be related to either headphone issues or the Bluetooth xceiver.
I originally though this problem was specific to Overdrive Media console, but it has also turned up in the Music app. I also installed a couple of other music/sound apps to see if it may be app specific, but all of them had the same consistent behavior of the sound file...pausing at random intervals....and then continuing after a few seconds when the screen...was turned off. The skips DO NOT happen when the screen is on.
Going through Erica Rene's thoughts I went into the Running Applications Manager and turned off several services I wasn't using, including Neo Player, 3d Gallery, Skype, and even Music. I initially thought that worked, but I was wrong. Same behavior.
This morning I did a factory reset. No change in behavior.
Since I just started using the tablet for audio books and podcasts I honestly don't know if this problem was there in 3.0. When I did the factory reset I thought the tablet might go back to 3.0, but I was wrong. I am still on build Acer_A500_4.010.08_COM_GEN2 after the factory reset.
There seems to be nothing wrong with my hardware that I can see. These skips happen with the headphones in or out. The only thing that triggers it is turning off the screen.
Insofar as software is concerned, I've not done anything more except rooting the tablet (which survived the factory reset process, which did surprise me! ). Beyond putting in another ROM - which, unless I can get some specific thoughts that it will fix the problem, given my experience level I'm a bit leery of doing - I can't see how software would fix it now.
Is anyone else seeing this???
Thanks!!!!
=============================
I've searched Google and here on XDA for this and not found anything, so I'm hoping that someone can say something.
When I play a sound file on my A500, and then turn it off, the sound continuing to play is a very iffy thing. This works on my Nexus One phone, so I assumed it would work here. On my phone I start a sound file running (music, podcast, audio from an audio book or Google reader) and then I turn the phone "off" to conserve the battery, of course. The sound continues to play.
When I do the same thing on the A500 it is very rare that the sound continues to play. Sometimes it will stop as soon as I turn the tablet off, sometimes it will continue for several seconds and then stop, sometimes it will continue for several seconds and then pause for a couple of seconds and continue in this loop for the life of the file.
I originally thought that this was a specific issue with the audio books in the Overdrive Media Console program, but I've now encountered it with Google Reader and playing things through either Music or Rockplayer Lite.
Has anyone seen this yourself, or does anyone have any thoughts? Details on the tablet are below:
OS: AndroidOS 3.1
Build: Acer_A500_4.010.08_COM_GEN2
Rooted
Could be some of the apps not playing fair.
Do you have a task killer or any add on management app.they can cause this
Also in settings sounds.there is a check button to control this.
Also do not hit the back button on the apt this will kill it
I had Google music going off when I would hot the power buttonbtobturn off display and it was ina task killer ibaccidently installed something I had on USB drive for my cell.it had a setting to close all apps on display off or sleep.
Erica:
Thank you for your reply. Oddly enough, something along those lines may be it.
I've not modified my tablet much beyond rooting it. I've not uninstalled applications and don't have a custom ROM.
You mentioned that something might not be playing fair. I have no add on management application, nor any task killer I'm aware of. The Applications area of Settings has been doing what I need in that department fine for me. So I went in and looked at what services were running, and specifically turned off the services and programs I know I was not using: Skype, NemoPlayer, PhotoBrowser, Acer Sync. I then tried a sound file, turned off the tablet and it did continue to play steadily.
Now I guess I just have to figure out which program is the culprit, but it seems evident that one of them is.
Along those lines, perhaps you can answer something else for me: Those programs I mentioned above basically started running services on bootup. How do I stop that? I don't use NemoPlayer, for example, and so have no reason to have any service from it starting. I took a look at the Settings->Applications area and don't seem to see anything there that indicates what gets started upon bootup.
Thanks!
-----
Doc Kinne
I use titanium backup. It has a option to not only backup. But can freeze apps.Im not sure but you might need to have root for this feature.there are other apps on market to freeze them maybe someone can help by telling the app they use.just do not remove any apps Acer put on your tab.
You can get root easky look in Dev area
Put some new information in teh original post.
My sound also cuts out when tablet goes to lock mode. I thought it was certain apps. Removed everything as far as widgets anything running in backround on home screen but I still have the same issue its random. Tried a clean wipe/install basic apps root explorer and still had it happen. I thought it might be a audio codec problem. In Honeycomb 3.0 I was able to play AVIs with AC3 in mobo and nemo player now I cant in 3.1.
HC 3.1
Acer 4.010.02 Gen1
i have the probleme too with the sound when it goes to sleep when i stream webradio !
Just a thought, along similar lines when my screen is off sound will cut out after about 15 to 20 mins. I think for you as others have said you have something else that is causing the problem. For me I think it's just a system timer. Don't know how to fix it.
i have experienced a similar thing with some Roms I've tried and with them it was the built in overclocker that was the culprit. I had to change the profile in the overclocker to enable the playback while the screen was off. Same goes for overclocking apps such as setcpu.
I'm experiencing a skip with my email notification. I recorded a short notice (similar to you got mail) & it does a 5 second pause 1/2 way through. Didn't do it prior to 3.1
So I am really angry at Android now, with all the issues and difficulties it is getting me through. Although visually and practically I still prefer it to iOS, there are some really annoying issues with it, that concern battery life/stability.
So there are apps that prevent your phone from sleeping, either leaves speaker on, or other BS. I have to close them every time I stop using the phone, to avoid a really stupid issue I had today. I recharged the phone 100% in the morning, later that day I went to check e-mails, sent a couple sms etc. and then I played this game called Pou, I left it running, the screen was off, but I didn't close it. Ended up with empty battery in 3 Hours.
This is ****ing ridiculous, what kind of smartphone is that, if it can't understand that I'm not playing games when the screen is off.
Is there at least a faster way to close all open apps, other than swiping from left to right 20 times every time you stop using the phone?!?!
What apps are causing the issue?
You're blaming the OS for the behavior of an app made by a bad developer. The vast majority of applications will not do that. iOS avoids that by limiting the cases in which an app is allowed to run in the background. You can argue that it's a superior solution for the end user, but it limits the ability for an app to actually do anything in the background.
Many custom ROMs build in a "kill all" button in the recent apps view. It's really not necessary though. You've identified an application that has this issue, so just make sure to kill that one app when you're done with it. Again, most applications won't have that problem.
raptir said:
You're blaming the OS for the behavior of an app made by a bad developer. The vast majority of applications will not do that. iOS avoids that by limiting the cases in which an app is allowed to run in the background. You can argue that it's a superior solution for the end user, but it limits the ability for an app to actually do anything in the background.
Many custom ROMs build in a "kill all" button in the recent apps view. It's really not necessary though. You've identified an application that has this issue, so just make sure to kill that one app when you're done with it. Again, most applications won't have that problem.
Click to expand...
Click to collapse
+1. I had just read a lot of silly things and ur comment relaxed me a bit. Blame a PHONE because some apps keep the phone awake... this is crazy, people should have a bit of experience before posting in this forum with so much arrogance.
This might help...
https://www.youtube.com/watch?v=JmvCpR45LKA
Sent from my Nexus 4 using Tapatalk 4
badboy47 said:
This might help...
https://www.youtube.com/watch?v=JmvCpR45LKA
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
That helped me so many times till I understood it....
The place to go, to get a definitive understanding of wakelocks is here:
http://forum.xda-developers.com/showthread.php?t=1179809&highlight=betterbatterystats
This is the thread for BetterBatteryStats, which is really all you need to troubleshoot why your device doesn't sleep enough.
Also, look at Greenify, which hibernates the apps you tell it to, a pretty unique trick.
http://forum.xda-developers.com/showthread.php?t=2155737&highlight=greenify
And as a last suggestion (frowned on by the purists at the betterbatterystats thread, but I find it really useful) use DS Battery Saver Pro, which will switch off wifi and reconnect every 10 minutes, amongst other tricks.
http://forum.xda-developers.com/showthread.php?t=2030696&highlight=ds+battery+saver
As an aside, I hear that iOS7 has impressed its user base with all sorts of hidden options which stop the phone resting, so maybe it's just a question of complexity . The good news is that, especially with the knowledge that is shared in betterbatterystats, it won't take you long to troubleshoot what your problems are, and the other 2 apps which will resolve your issues are pretty straightforward to use.
There are free versions I recall in the first post of these threads, I use the Pro version of DS Battery Saver since I prefer to configure my own profile.
Thank you everyone for replies.
I have not rooted the phone, so Greenify is no option for me, not really up to going through all rooting and ROM installing process in order to maybe succeed in solving the issue.
Specifically talking apps that leave speaker ON (It keeps hissing) and keeps phone awake, if you do not close them are following : Asphalt 8, Need For Speed Most Wanted.
The thing is I am not sure who to blame really, yes there are many apps that work normally and don't cause these issues, but then again why is the keeping the phone awake allowed in the first place, downloaded apps that would need to work that way should need special permissions. I understand there might be apps that want to keep ON/playing something after you have quit them, but if that's the case, then user should be able to deny certain permissions to prevent this from happening. The OS is complex enough, why not give even more options then or just this one at least.
Not sure how other people manage with this problem, I can't find anyone mentioning anything about Asphalt 8 and Android having this problem, people just deal with that they have battery draining to 0% in 5 hours? I know many people with smartphones 75% barely ever closes any programs from multitasker, most of them are iPhone users though. But how do they manage to live with their phone if they have this. I did manage to find people complaining about Pou draining battery, solution was to just uninstall the app, ridiculous.
I can't be the only one having these issues.
Well, the Android "style guide" has the back button as the exit function, so instead of leaving it running in the background, you may want to try backing all the way out.
It's been about a year since I played Asphalt (6 I think it was), but I vaguely remember it had an exit button which explicitly closed down the app.
Could be worth trying that. All the same, install the free xda edition of BetterBatteryStats (in the first post I think) and then look at the partial wakelocks, you'll quickly see what is stopping the phone sleeping.
paul c said:
Well, the Android "style guide" has the back button as the exit function, so instead of leaving it running in the background, you may want to try backing all the way out.
It's been about a year since I played Asphalt (6 I think it was), but I vaguely remember it had an exit button which explicitly closed down the app.
Could be worth trying that. All the same, install the free xda edition of BetterBatteryStats (in the first post I think) and then look at the partial wakelocks, you'll quickly see what is stopping the phone sleeping.
Click to expand...
Click to collapse
It really is like that, this fixes a small part of this issue! If you exit the game using the back button, the application closes the resource, but leaves it available at the multi task panel.
But, when I had iPhone, I could play the game, lock the screen, go home, for example, and continue where I left off, no battery drainage or anything. Only when you fill up the RAM memory it stops least recent processes.
Often it is very annoying to tap multiple times the back button (Sometimes even on screen you have to press quit multiple times (Quit current game & quit menu)) until you get to exit the application. And you can't continue where you left off, if you do that.
What the most bothers me about this is if I suddenly have something urgent and I don't turn off the application, my phone could drain a heavy amount of battery percentage till I remember to close them or check something on the phone/continue where I left off.
raptir said:
You're blaming the OS for the behavior of an app made by a bad developer. The vast majority of applications will not do that. iOS avoids that by limiting the cases in which an app is allowed to run in the background. You can argue that it's a superior solution for the end user, but it limits the ability for an app to actually do anything in the background.
Many custom ROMs build in a "kill all" button in the recent apps view. It's really not necessary though. You've identified an application that has this issue, so just make sure to kill that one app when you're done with it. Again, most applications won't have that problem.
Click to expand...
Click to collapse
luiseteyo said:
+1. I had just read a lot of silly things and ur comment relaxed me a bit. Blame a PHONE because some apps keep the phone awake... this is crazy, people should have a bit of experience before posting in this forum with so much arrogance.
Click to expand...
Click to collapse
Guys, this isn't the only issue with the OS. I had bad battery drainage from Wi-Fi & mobile network location setting also. I have various Google app problems, also with drainage, freezing and lag with Google Chrome, Google+ keeping phone awake. I would consider that as a property of Android OS, because the software was already installed when I got the phone. Chrome is the default and only internet browser in the beginning and it should work properly.
So I am not sure who to blame, maybe the developers can't find a workaround from the problem, because the OS is not behaving correctly, and I don't think that it's inappropriate to blame also the OS, since even the default apps and settings have problems same as some apps do.
I have used Chrome daily since it was first released for Android and have never had any real issues with it. Occasionally it will give me a problem where I need to restart the app but that's probably about once a week. Google+ should only keep the phone awake if you have it set to upload your photos automatically, and even then there's a setting to force it to only do the uploads when on the charger.
I think the key issue is that you're used to an OS that does not involve any thought from the user. I'm not saying that's a bad thing, but it's a distinctly different approach from Android. Apps are allowed to run when the phone is asleep because that can provide additional functionality. I'm sure you wouldn't complain if Pandora was playing music and thus running when the phone was asleep. And that would hit your battery hard. iOS only allows applications to run under very specific conditions, thus limiting what they can do but making sure you don't end up with any "runaway" applications. Android puts the responsibility on the developer to make their app handle battery life well and on the user to make sure they're using decent applications.
Things like the mobile network and WiFi location are used by Google Now to provide location-based data. If you would rather have the improved battery life, turn Google Now off. Some of us would rather have the functionality, but you have the option to disable it.
Keep in mind also that the Nexus 4 just doesn't get as good battery life as the iPhone 4 or newer.
raptir said:
I have used Chrome daily since it was first released for Android and have never had any real issues with it. Occasionally it will give me a problem where I need to restart the app but that's probably about once a week. Google+ should only keep the phone awake if you have it set to upload your photos automatically, and even then there's a setting to force it to only do the uploads when on the charger.
I think the key issue is that you're used to an OS that does not involve any thought from the user. I'm not saying that's a bad thing, but it's a distinctly different approach from Android. Apps are allowed to run when the phone is asleep because that can provide additional functionality. I'm sure you wouldn't complain if Pandora was playing music and thus running when the phone was asleep. And that would hit your battery hard. iOS only allows applications to run under very specific conditions, thus limiting what they can do but making sure you don't end up with any "runaway" applications. Android puts the responsibility on the developer to make their app handle battery life well and on the user to make sure they're using decent applications.
Things like the mobile network and WiFi location are used by Google Now to provide location-based data. If you would rather have the improved battery life, turn Google Now off. Some of us would rather have the functionality, but you have the option to disable it.
Keep in mind also that the Nexus 4 just doesn't get as good battery life as the iPhone 4 or newer.
Click to expand...
Click to collapse
I have never had a OS that I am fully satisfied with, that is normal, but I am always very aware for issues, always scanning for issues, I really hate that about myself, I am a perfectionist, I will not calm down until I get everything just the way I think it should be... So that makes up very difficult relations with any software I use, too bad for me.
Android apps do have more functionality, more freedom than iOS, and I very much appreciate that. BUT if that functionality results in 90% to 0% in 3 hours, when you forget to turn off 1 app after using it... please, I feel like it's a duty to take care of my smartphone, close app after you are done or the phone will die, and you will be left without a phone for the entire day.
I don't like that instability when you can make 1 thing wrong and it all goes to pieces, not when there are people using other phones with almost the same functionality and no problems like that.
No matter who I have to blame this on, I have this issue and it is because of Android & because of the developer of the app.
It's very sad, I really want Android to be more stable with this
Yukicore said:
It's very sad, I really want Android to be more stable with this
Click to expand...
Click to collapse
There are hundred millions of Android users, we don't all gets wakelocks. I don't have this problem and my phone is stable. Once you are using Android, you are no longer special and pampered in a walled garden like iOS users.
If you have battery drain due to Google services, see here: http://forum.xda-developers.com/showthread.php?t=2385843
I suggest doing a factory reset and not install crap apps like anything by Gameloft, just play them on Apple devices. If you gets a wakelock, make a shortcut on your desktop to Apps and check on what apps are running in the background, one of the app in the list could be the issue.
I know you don't want to root, but I suggest do it anyway and install Greenify, hibernate any apps you don't want autostarting when you boot up the phone. Watch out for apps that both runs in the background and ask for too many permissions. I know there is an app that limit the maximum app that can run in the background, but I don't know the name, you can set it in the phone's Developer mode, but it doesn't persist on reboot.
Maybe the difference is like moving from an automatic car (iOS) to a manual (Android).
At least before "multitasking" arrived to iOS, an app no longer in the foreground was effectively exited. Android's memory management is much more complex than that, and apps are kept in memory until a new app requires the RAM being held by a previous one.
There is a clear advantage to this since apps "reopen" instantly, but if you're not careful there could be continued drain from apps still open but not in the foreground.
Incidentally - I don't follow Apple closely - iOS7 has been slated by users for the scenario you describe, I believe!
Google's apps offer all sorts of wonderful location-based features, for which the phone inevitably needs to know its location. Coarse location (via triangulation of radio towers) is not a problem, but "fine" requires the GPS to be used, and that does drain the battery.
So you need to consider whether you want all that location based stuff from Google.
Wifi is also a big drain, and that is why I get my phone to switch on every 10 minutes via DS Battery Saver. The upside is that the phone sleeps regularly, but the downside is that Whatsapp messages etc don't arrive immediately.
As you can see, Android offers you the ability to choose to be uber-connected/always on, or to have a better battery consumption. Since each individual is different, you can choose what is important to you.
I just had that drain second time happening. I don't remember how I left that stupid game, but I ended up with 2% battery and phone turned off.
I think I exited using the back button. What the hell.
Pou is known to kill your battery.
http://forums.androidcentral.com/google-nexus-4/253092-media-server-draining-my-battery.html
http://answers.yahoo.com/question/index?qid=20130606043957AA9Tq7N
Since it's a virtual pet game the developer probably did not code it to close when you hit the Back button, so you need to kill it through Recent Apps. Or just uninstall it.
raptir said:
Pou is known to kill your battery.
http://forums.androidcentral.com/google-nexus-4/253092-media-server-draining-my-battery.html
http://answers.yahoo.com/question/index?qid=20130606043957AA9Tq7N
Since it's a virtual pet game the developer probably did not code it to close when you hit the Back button, so you need to kill it through Recent Apps. Or just uninstall it.
Click to expand...
Click to collapse
This is bad... Now it is developers fault, but why on earth should Android OS allow this kind of behavior on any app... This is not a simple background service, this was running fully when the screen was off. 2-4 hours is the screen on time averagely I get, 3.5 hours without screen on, it's damn fast draining.
Yukicore said:
This is bad... Now it is developers fault, but why on earth should Android OS allow this kind of behavior on any app... This is not a simple background service, this was running fully when the screen was off. 2-4 hours is the screen on time averagely I get, 3.5 hours without screen on, it's damn fast draining.
Click to expand...
Click to collapse
We've already been through this. You're fine with your phone's music player running in the background when the screen is off, right? It's the exact same behavior, just that Pou uses more resources and has no reason to be running. Apple puts heavy restrictions on what an app can do in the background (playing music being one of the only exceptions). Google leaves it up to the developer and user to manage it.
If you think that is a problem with the OS, I really recommend you go back to the iPhone. Not being mean or anything, but you clearly either do not understand the differences in philosophy between the two operating systems or you understand it and prefer the iOS way.
raptir said:
We've already been through this. You're fine with your phone's music player running in the background when the screen is off, right? It's the exact same behavior, just that Pou uses more resources and has no reason to be running. Apple puts heavy restrictions on what an app can do in the background (playing music being one of the only exceptions). Google leaves it up to the developer and user to manage it.
If you think that is a problem with the OS, I really recommend you go back to the iPhone. Not being mean or anything, but you clearly either do not understand the differences in philosophy between the two operating systems or you understand it and prefer the iOS way.
Click to expand...
Click to collapse
You said that user and developer can manage resources of apps, how can a user manage them? Can I fix this specific problem myself somehow?
I've had my Verizon Galaxy Note 3 since 10/13-10/14, pretty close to when it was released at Verizon. I've loved it, loved its tons of features, since I got it, and have had many people jealous. (I upgraded from a Galaxy Nexus, a heck of a reliable phone, when I realized that the Nexus 5 would also not go to Verizon.) In the past 6 weeks, i've encountered some curious behavior that i'm stumped and frustrated by. Overall, I love the phone.
Notes: I have searched and searched and searched for help, via Google and via XDA / AndroidCentral / other sites. My phone is un-rooted (never rooted), and has not been factory reset, dropped, submerged in liquids, or in any way mishandled. My phone uses the stock launcher and aside from some games, does not have a ton of apps installed.
However (Stated verbosely but with detail):
1) On two separate occasions, my Alarm has crashed. I used my Galaxy Nexus for nearly 2 years without ever having it fail to wake me (with many roms in between); I used my Droid X for nearly a year prior without ever having it fail to wake me, and before that my Blackberry Storm 2 for nearly a year without it failing. I'm not used to my phone failing me as an alarm.
In both cases, last Thursday (11/21) and today (11/25), I woke up to my phone acting as though the Alarm was still going off. (The notification bar indicated I should either Snooze / Dismiss the Alarm). I woke up about an hour after it should have went off, and there is absolutely zero possibility that I slept through the alarm going off that long. When I unlocked my phone, in both cases, it indicated the Alarm app had crashed.
I was using Timely on my Galaxy Nexus for the last few months of it as my daily driver, and then for the first few weeks on this phone. I immediately assumed it was the culprit, and went back to Alarm Clock Plus (the app I had used for nearly the entire time on my Nexus). This morning, Alarm Clock Plus crashed (with the 'Wait / Report / Close' options), and i'm now more confident that Timely was not the culprit.
In both cases, with both apps and on both days, after I clear the error, I had a similar experience.
- On Thursday, I pressed the power button to turn off the screen, and when I pulled the phone out of my pocket about 20 minutes later, it was completely powered off. However, I could not power it back on by pressing the button, and had to perform a battery pull to turn it back on.
- Today, I had pressed the button to perform a restart, and only tapped it instead of pressing + hold. Same thing happened: it turned off the screen but also somehow powered it entirely down, and required a battery pull to start it again.
- After Thursday's debacle, I have rebooted my phone multiple times, so it's definitely not because of an uptime related issue.
The only thing I can think of for the above scenario, is that I did have it work (the alarm) without any issues for a few weeks, and both issues (and some other random crashing of Google Plus, etc) have been following the update that was released by Verizon.
2) This is an issue i've experienced for the entire life of the phone, and is flummoxing me and extremely frustrating. I loved using the Droid X and then Nexus as my music player (both via headphones and definitely in the car via the Aux on my older stereo). On my Nexus I experimented with different Equalizers, including ones from Google Play (I liked 'Equalizer' quite a bit actually), and then I tried out and enjoyed Beats (or whatever it is now called, NexusLouder or whatever), to great enjoyment. Music sounded awesome.
On my Note, I expected at least a marginally similar level of audio (to that of the Nexus without Equalizer), until I rooted (which I have not done yet). I am facing (like others have sporadically reported) and issue where it appears that my Audio or Equalizer or something is turning off or turning on between songs. I'll plug it in to my car stereo, slap it in the window mount thing, and let it ride. It plays one track (sometimes two) without issue. Then, it will play a song either really quietly or really loudly. (I don't mean the volume has changed; it has not and I have verified this). The solution i've found is to go back (or forth) a track and then return to the same track, which has resolved this 100% of the time .... until a few tracks later. /rinserepeatrage
- I have tried this with the same Equalizer app, a few other Equalizer apps, and even without a Google Play Equalizer app (using only the built in one).
- On my Nexus and now my Note, i'm using Google Music, and use the pre-downloaded/cached songs.
- I have tried clearing the data / cache for Google Music and uninstalling / reinstalling it, to no effect.
- The only interesting thing i've noticed is that after the Verizon Note update (I believe), the audio appears to only get softer, rather than getting ear splittingly louder.
- Additionally, this seems to occur much more frequently when the screen is off.
Today I am going to the Verizon store and they will likely tell me they have to perform a Factory Reset (which is why I haven't already done one) before they'll give me another one, in the case that it is a hardware issue. I will very carefully be monitoring and see if this corrects / resolves either issue. I also intend to NOT install the update if I have any say (I don't know how not-rooted phones work with updates, i.e. if it is required or prompts for update, etc) If any of you have any ideas, solutions or suggestions, i'd be very open to them. I love this phone, but I absolutely hate that these two very important functions are not working consistently.
Well, i've been to Verizon and as expected, they heard my issue and thought that a factory reset might be the solution.
Their logic, which is not terribly shaky, was: the recent update (or even the factory pre-load of the OS) could have config or factory fragments / blahblahblah that a clear of the data / cache / etc could resolve. This made sense to me.
After the reset, we tried to recreate the Google Music bug in the office, no such luck, all looked good on the home front. I tried a few more songs on the way home, still not able to recreate the issue. I got home, all my stock apps updated, then I went through and installed apps, blah blah blah. I also cached the songs for an album so I could continue to confirm my confidence in this as being resolved.
I then went for a drive not too long ago, and the issue occurred again. I also noticed (though it may have existed prior to the factory reset) a new issue / symptom. When I scrub, like clockwork, the issue shows up. Song plays perfectly, I scrub (even only a few seconds forward), equalizer is gone and the music is much quieter. I have no clue what to think now. I will be hesitantly trying to recreate the alarm clock bug over the next few days. I also may try the old 'uninstall apps until I can't recreate' method too, for at least the Music bug.
If any of you all have thoughts, that would be extremely appreciated. Else, i'll keep reporting info as I get it, maybe this will help someone else.
Mine crashed Saturday. Woke up to the force close message.
Sent from my SM-N900V using xda app-developers app
kickenwing13 said:
Mine crashed Saturday. Woke up to the force close message.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Sorry to hear that! I know i've seen other reports on the interwebs saying similar things, but did not see any threads with discussions about theories or investigation, beyond the 'me too' I see often (which is entirely fine, and unfortunate for those who also have this issue!). Having the volume helps a ton, but i'm surprised I didn't see more analytical or critical thinking / discussion happening in the many threads, and figured i'd just get the ball rolling and hope this helps others (even if it's just mostly me putting findings down).
That said, I have more information to offer.
1) Alarm - Day 1, following the Factory Reset yesterday, it started without issue (not unexpected). I expect that the issue (if it does) will re-appear sometime around Friday - Saturday.
- Other than installing some apps (as mentioned previously) mostly things like Netflix and some games, I have not installed anything that (from what I can see) should interfere with an Alarm app
- I am presently using Alarm Clock Plus (the second of two apps I encountered the issue in); this is for consistency, and also because the app worked without issue for over a year prior to this
- I have not 'Turned off' any apps, though previously (prior to the Factory Reset) I had turned off some apps mentioned in other XDA threads as not required by the system to run (mostly Verizon and Samsung apps)
- I am not and have not rooted this phone at any time; this is 100% stock Android at this point (well, as Stock as a Samsung phone gets)
- After speaking with a few friends, they have confirmed that: this issue has occurred with the stock Alarm Clock app and another 3rd party app (one I have not tried yet) as well; but one friend has not experienced any Alarm issues at all (though he may just not be aware of them, so i'm taking his account with a grain of salt)
2) Music - To add to my previous notes about the issue around the equalizer ..
- I am able to (as indicated previously) re-create the issue on-demand by scrubbing
- I can re-create the issue relatively reliably by hitting 'Pause / Play', and I didn't see a difference (in ability to reproduce) whether it was from the lock screen or in the app that I hit 'Pause / Play'
- It does appear that (with inconsistent results) I experience the Equalizer turning off / on by itself, if I keep listening to songs the issue seems to reverse. (i.e. Song 1 is fine, Song 2 - Equalizer turns off, Song 3 or Song 4 - Equalizer turns back on) I encountered this just a bit before this post, and sure enough, after hitting 'Pause / Play' I was able to verify that the Equalizer had turned back on.
- I am now 100% positive it is the Equalizer being horked by the phone / OS / something. This is based on replication of the issue (where it sounds like it gets soft) being the exact same sound as when the Equalizer is just turned entirely off.
A few things to test today / next few days:
Alarm issue:
-None at this time; keep observing
Music issue:
- Google Play Equalizer app (see if issue occurs still outside of the stock Equalizer)
- Try non-Cached music to see if this is a factor (including 'Pause / Play'; song scrubbing; etc)
- Try an alternative to Google Music (this is not a practical solution to me, but would provide comparison data)
Last note:
- After completing the Factory Reset and hearing my story yesterday, the Verizon rep did inform me that I could bring the phone back, if the issue keeps happening, and exchange it for a refurb. I'd rather avoid this if possible, as I feel like i'm not as confident it is a hardware issue as before, but this is an option (and may be an option for others wishing to try this path). Obviously, I hadn't rooted, so the Manufacturer's Warranty was available, so YMMV.
verziehenone said:
Sorry to hear that! I know i've seen other reports on the interwebs saying similar things, but did not see any threads with discussions about theories or investigation, beyond the 'me too' I see often (which is entirely fine, and unfortunate for those who also have this issue!). Having the volume helps a ton, but i'm surprised I didn't see more analytical or critical thinking / discussion happening in the many threads, and figured i'd just get the ball rolling and hope this helps others (even if it's just mostly me putting findings down).
That said, I have more information to offer.
1) Alarm - Day 1, following the Factory Reset yesterday, it started without issue (not unexpected). I expect that the issue (if it does) will re-appear sometime around Friday - Saturday.
- Other than installing some apps (as mentioned previously) mostly things like Netflix and some games, I have not installed anything that (from what I can see) should interfere with an Alarm app
- I am presently using Alarm Clock Plus (the second of two apps I encountered the issue in); this is for consistency, and also because the app worked without issue for over a year prior to this
- I have not 'Turned off' any apps, though previously (prior to the Factory Reset) I had turned off some apps mentioned in other XDA threads as not required by the system to run (mostly Verizon and Samsung apps)
- I am not and have not rooted this phone at any time; this is 100% stock Android at this point (well, as Stock as a Samsung phone gets)
- After speaking with a few friends, they have confirmed that: this issue has occurred with the stock Alarm Clock app and another 3rd party app (one I have not tried yet) as well; but one friend has not experienced any Alarm issues at all (though he may just not be aware of them, so i'm taking his account with a grain of salt)
2) Music - To add to my previous notes about the issue around the equalizer ..
- I am able to (as indicated previously) re-create the issue on-demand by scrubbing
- I can re-create the issue relatively reliably by hitting 'Pause / Play', and I didn't see a difference (in ability to reproduce) whether it was from the lock screen or in the app that I hit 'Pause / Play'
- It does appear that (with inconsistent results) I experience the Equalizer turning off / on by itself, if I keep listening to songs the issue seems to reverse. (i.e. Song 1 is fine, Song 2 - Equalizer turns off, Song 3 or Song 4 - Equalizer turns back on) I encountered this just a bit before this post, and sure enough, after hitting 'Pause / Play' I was able to verify that the Equalizer had turned back on.
- I am now 100% positive it is the Equalizer being horked by the phone / OS / something. This is based on replication of the issue (where it sounds like it gets soft) being the exact same sound as when the Equalizer is just turned entirely off.
A few things to test today / next few days:
Alarm issue:
-None at this time; keep observing
Music issue:
- Google Play Equalizer app (see if issue occurs still outside of the stock Equalizer)
- Try non-Cached music to see if this is a factor (including 'Pause / Play'; song scrubbing; etc)
- Try an alternative to Google Music (this is not a practical solution to me, but would provide comparison data)
Last note:
- After completing the Factory Reset and hearing my story yesterday, the Verizon rep did inform me that I could bring the phone back, if the issue keeps happening, and exchange it for a refurb. I'd rather avoid this if possible, as I feel like i'm not as confident it is a hardware issue as before, but this is an option (and may be an option for others wishing to try this path). Obviously, I hadn't rooted, so the Manufacturer's Warranty was available, so YMMV.
Click to expand...
Click to collapse
My stock alarm crashed yesterday. Woke up to a completely black phone. Only the pulldown would get out of the crashed alarm app. Quite unfortunate. 100% stock, unrooted.
Botond said:
My stock alarm crashed yesterday. Woke up to a completely black phone. Only the pulldown would get out of the crashed alarm app. Quite unfortunate. 100% stock, unrooted.
Click to expand...
Click to collapse
Sorry to hear that
On a similar note, if anyone can re-produce the Music issue i've mentioned, that would help me confirm i'm not crazy or alone in my issue.
Of note:
Music:
- I have attempted to recreate the issue in Pandora, but was unsuccessful. The audio remained unchanged when I did a Pause / Play (I was unable to scrub, unsure if that's a Premium feature or just not a thing with Pandora). I will not be able to try a local song with another music app until I am home this evening.
- I was able to recreate the issues (scrubbing, between track loss of equalizer, pause/play) with the Google Play equalizer app 'Equalizer' reliably.
- I was able to recreate the issues (scrubbing, between track loss of equalizer, pause/play) using both Cached music and Streaming, with stock and 3rd party equalizer
After searching for awhile for an already open bug report, I have opened up a bug report on the AOSP site, in case you are interested, for the Music issue: 62864 is the defect number; I am unable to link it since i'm still not yet a real boy.
I will hold off on creating one for the Alarm issue until I am able to recreate it post-Factory Reset.
This will likely be the last update until post-Thanksgiving, and will hopefully bring a measure of consistency (if the Alarm error returns) or confidence (if it doesn't) to the information I have.
Music:
- I was able to recreate the issue with scrubbing and 'pause/play' with a song located directly on the phone (not downloaded/cached via Google Music)
Other notes:
- I've seen other sites with similar sounding issues for different phones, such as the Galaxy S4, well before the Note 3 came out
- This is noted as being a bug with the equalizer, but not specific to the .api or .dll or whatever Android calls reusable things (as this is an issue with not just the stock equalizer, which points to some system dealie rather than the specific equalizer)
- I have not yet tested another app such as PowerAmp or similar, but suggested workarounds on the GS4 issue thread (on AndroidCentral) indicate disabling the equalizer altogether (not a great workaround) or using another app (not confirmed as a workaround; by me or the thread)
- One other forum suggests it is due to a bug in the OS with the equalizer not having a persistent icon in the notification bar, and suggests using another app (the 'Equalizer' app from Google Play is suggested) to resolve; this thread was started in May of 2013, but does point to it turning off during playback, not in between songs
- Still another person does report the issue I have experienced, with the issue displaying when the screen is off during the change from one track to another; this person also indicates WinAmp did not resolve this issue (implying that: A) local tracks are not the fix, and B) that another player is not)
Alarm:
- Day 2 after Factory Reset, the alarm went off again without issue
- I have had difficulty with finding many other threads or information; if you are reading this and have experienced this, it would be helpful for information to note that you have had it, and if you have the MJ7 update (or whatever) that too would help
- I might end up doing a bit of 'set an alarm for 5 minutes' testing and see if I can recreate the issue with any reliability
Learning is fun! Happy Thanksgiving and/or Hanukkah everyone!
verziehenone said:
Alarm:
- Day 2 after Factory Reset, the alarm went off again without issue
- I have had difficulty with finding many other threads or information; if you are reading this and have experienced this, it would be helpful for information to note that you have had it, and if you have the MJ7 update (or whatever) that too would help
- I might end up doing a bit of 'set an alarm for 5 minutes' testing and see if I can recreate the issue with any reliability
Learning is fun! Happy Thanksgiving and/or Hanukkah everyone!
Click to expand...
Click to collapse
My alarm crashed a couple times with my unrooted Note 3. After I rooted, no more problems with Alarm or anything else crashing.
My advice??
Root & load SafeStrap 3.65 HAppY Thanks Giving
Are you using any battery-saving apps? That could create issues like this, especially if the app messes with wakelocks.
I am rooted with the stock MI9, and alarm crashed one morning. Apparently there is a bug, root or no root. All I had to was restarting the phone and it worked after that, but it may crash anytime, I'm afraid.
Sent from my SM-N900V using xda app-developers app
Update (12/2):
So, after a Thanksgiving break and more time for more research...
Alarm:
- Since the Factory Reset, I have not had the alarm fail
- From Thursday Morning to Sunday Morning, I did manually / individually set an alarm for each day; unknown if this is a factor
- I do not use any power saving anythings (I don't even use the built in Note power saving mode)
Music:
- Audible (the Amazon Audiobook App) did not display this behavior
- I have not had a chance to try to uninstall until I cannot recreate this
Related to above?
- Once more I set the phone down (this time after using it very liberally for the past few days, and then on an 8 hour drive home yesterday) on a coffee table, not hard or anything, and it would not turn on
- Weirdly enough, although the power button, home key (or whatever the physical key in the middle of the phone is called) would not turn the screen on, but when I pulled the stylus out (on a whim), the screen turned on but was not responsive
- Battery pull resolved this, but I never saw any errors / errored apps / etc
- I am more firmly believing that at least this part is related to a hardware issue and will be going to Verizon tonight for my Manufacturer's Refurb or whatever
Notes:
- I am not using any crazy apps, mostly games and such, all straight from Google Play and none are those obviously suspect apps (like the many strip poker, etc, that are very shady)
- Although I have a decent volume of apps (probably about 40 or so from Google Play, not including the Verizon pre-loaded), I have fantastic battery life still
- I do not have any power saving anything turned on, on the phone, and do not use auto-dim, or anything like that
- Since the factory reset, I have not 'turned off' any apps
- I do have a Sandisk Ultra 32GB microSD card, this could be a factor
- I have a Model: SM-N900V UD (in case the Refurb is a different model)
That's all for this update, will keep updating as I have more information to share. (Still assuming that at least someone is finding this helpful, if not, i'll keep playing quietly in the corner)
More updates -
Alarm:
- The Alarm functioned without issue once more this morning (this time the result of a recurrent alarm, and not a manually set alarm)
- I am beginning to suspect that after the latest OTA, it gummed up something and just required a Factory Reset to un-gum
- The alternative is that the issue with the unresponsive screen is related, but the times I experienced the Alarm issues were accompanied with an error indicating the Alarm app had crashed
Music:
I played around with a few settings and did some app-investigation and learned stuff.
- I DO have 'All Access', though i'm unsure how that would impact the equalizer
- Surround vs. Stereo does not make a difference, issue is still present
- Adapt Sound On does not make a difference
- Adapt Sound 'Turned Off' does not make a difference
- Having the S Pen out does not make a difference
- I went through and wrote out every single app installed on my phone, Google, Samsung, Verizon, Play, etc ... and found a total of 356 apps. The breakdown was: 326 Pre-Loaded/Verizon, and 30 that I installed. I have uninstalled all but about 5 apps (Alarm Clock Pro, Business Calendar, Facebook, Outlook.com, A Better Camera, and Safe In Cloud) and the issue is still present
- I cleared the Cache / Data and 'reverted' Google Music to the pre-installed/factory installed version: v5.1.1107K.753159 and after this was completed, the issue was NOT re-creatable (at least the 'scrubbing' part)
- I re-installed the most current Play version: v5.2.1301L.891271 and the issue was NOT re-creatable (at least the 'scrubbing' part)
- My working theory is ... well, no, I don't really have any idea now; I thought the version could be an issue, but that doesn't appear true. After the Factory Reset, the version would have been reset as well, but the issue returned, so maybe it takes time?
Note:
Due to the other mentioned issue (where I set my phone down and it randomly is unresponsive) I will be receiving my Manufacturer's Refurb on Wednesday-ish (depending on whether or not FedEx tries to deliver when i'm at work or not). The hope is threefold: 1) that this resolves the issue with the random unresponsiveness, 2) this resolves the issue with Google Music, and 3) this resolves the issue with Alarms. This would confirm a hardware related issue as being the source of all three, but if either of the other issues return, this means one of two things: 1) the issues are software related, or 2) the statistically unlikely but possible situation where I received two bad units.
To any readers: I've asked before, but figure i'll ask again.
1) Have any of you experienced the issue with Google Music's equalizer shutting off when scrubbing, in between tracks, or similar?
2) Have any of you experienced the issue with the Alarm not going off, AFTER receiving the latest OTA?
3) If you have experienced either of the above issues, have you performed a Factory Reset after the OTA?
Update: 12/5
Alarm:
- No issues since the Factory Reset still
- Really starting to think the Factory Reset was the key
Music:
- Still all kinds of things going on; tried another reset to 'stock' Google Music but issue came back
- More research seems to find this issue with other 4.3 phones like the Galaxy S4, etc
Notes:
I have now received my Manufacturer's Refurb. I'm about to go through the process of the switchover, but I wanted to note something I found interesting. On the sticker behind the battery, (where the IMEI and all that business is), I noticed one difference between the one I bought in the store and the refurb.
Model is unchanged, so is SKU and FCC ID. Right below 'Made in China' and above 'IMEI' I see a number. On the one I bought was '13.09', but the refurb is '13.10'.
Does anyone else have any other numbers? Is that a revision or something like that? Just wondering if that could mean another run of the hardware or something. Or if it's nothing of course, whatever.
I'll update again once I have more info from the refurb. /crossingfingers
I have the same problem. I have had my Note 3 for a week, and yesterday a third party alarm crashed (Sundroid). Then today, the stock alarm app crashed. Do you use a widget for your alarm? I do. This is stock, unrooted, very few apps. Is there more information I can give to you?
Alexander_Q said:
I have the same problem. I have had my Note 3 for a week, and yesterday a third party alarm crashed (Sundroid). Then today, the stock alarm app crashed. Do you use a widget for your alarm? I do. This is stock, unrooted, very few apps. Is there more information I can give to you?
Click to expand...
Click to collapse
Good questions I do not use a widget, and with regard to the Alarm, I think the one big question is: Have you received the MJ7 OTA? (If you go into About Phone and look at Build Number, the last 3 characters tell you if you have the latest OTA). If you do, I would suggest a Factory Reset, which is painful but appeared to resolve the issue for me.
Updates: (12/6)
I have received my Manufacturer's Refurb and have completed the process of switching over (including a Factory Reset after the OTA update). I am still curious what the 13.10 means on the sticker with the IMEI (since my previous phone at 13.09).
Alarm:
- The alarm worked without issue on Day 1 with new device
- All signs right now point to: If you have Alarm issues, and have received the MJ7 OTA, perform a Factory Reset; seems to resolve it
Music:
- On the Manufacturer's Refurb I was able to quickly confirm the presence of the bug
- This is looking more and more like an issue with either 4.3 or some Samsung software issue
- I would suggest submitting a bug report to Google and also posting a review on the Google Music software, see if we can get Google to look into it
Thoughts:
- Is there a Google Music .apk for 4.4? Does it require Root to side-load if so?
- I wonder if anyone with a Nexus 5 (or other device with 4.4) can recreate the issue
I didn't read thru everything here, but I use Alarm Clock Plus (the paid version) and it has never crashed once on me.
I bought my N3 the day they where released and used it everyday on first the stock ROM & now Beans ROM..
I am on the updated mj7 firmware etc.etc.
jmorton10 said:
I didn't read thru everything here, but I use Alarm Clock Plus (the paid version) and it has never crashed once on me.
I bought my N3 the day they where released and used it everyday on first the stock ROM & now Beans ROM..
I am on the updated mj7 firmware etc.etc.
Click to expand...
Click to collapse
How long ago did you root it? I'm assuming you performed a factory reset or a cache/data clear (or similar) as part of the rooting process, so i'm leaning towards that being the reason it has been stable. That said, if my theory holds that it is related to the MJ7 firmware and needing to be cleared out or whatever, that also means that it likely wouldn't be affecting everyone.
Are you able to replicate the issue with equalizer? I hadn't thought to ask if Rooted users experience it too.
verziehenone said:
How long ago did you root it? I'm assuming you performed a factory reset or a cache/data clear (or similar) as part of the rooting process, so i'm leaning towards that being the reason it has been stable. That said, if my theory holds that it is related to the MJ7 firmware and needing to be cleared out or whatever, that also means that it likely wouldn't be affecting everyone.
Are you able to replicate the issue with equalizer? I hadn't thought to ask if Rooted users experience it too.
Click to expand...
Click to collapse
When the mj7 tar was released, I did an odin flash of that to reset everything in my stock ROM slot.
I still had beans ROM in slot one with safestrap and it didn't affect that.
I have had no music problems whatever, but I use WinAMP with the viper sound mods. I have 800 gigs of music on my 64 gig card that I play thru headphones or hdmi out in my truck.
jmorton10 said:
When the mj7 tar was released, I did an odin flash of that to reset everything in my stock ROM slot.
I still had beans ROM in slot one with safestrap and it didn't affect that.
I have had no music problems whatever, but I use WinAMP with the viper sound mods. I have 800 gigs of music on my 64 gig card that I play thru headphones or hdmi out in my truck.
Click to expand...
Click to collapse
That helps
Unfortunately, i've already heard that a good way to resolve this issue is to install the Viper sound mods, but was hoping to prove whether or not Rooting / Rom-ing it (without Viper) made a difference.
Of note -
Music:
- I turned off the equalizer entirely, figuring i'd just deal with it with a more flat sound, and after playing 2-3 songs, the music got really loud; after doing a pause/play, it went back to normal. I verified (before pause/play) that the equalizer was still off
- I am still unsure why my friend couldn't recreate this, as if it is a software issue, any Note 3 should be able to recreate it
Hi everyone. So I've scoured the web high and low for some help on this topic, and so far I've gotten some scattered information, but not a lot of concrete solutions.
I'm having bad idle battery drain problems on my un-rooted, stock Verizon N9000V (MJE). Using BetterBatteryStats I've singled out bam_dmux_wakelock as the culprit. From what I've been able to find online, I guess this is a kernel level wakelock caused by something accessing cellular (not-wifi) data when the phone is asleep. I've pulled my hair out individually un-installing apps one at a time to see if I can pinpoint the culprit. I've also factory reset the phone and started from scratch, adding my apps one at a time, but due to the intermittent nature of this wakelock (it is not always present) I've had a whole bunch of false positives, thinking I'm safe only to have it pop up again the next day.
At it's worst, this wakelock is keeping my phone out of deep sleep around 50-75% of total battery time.
I do know that a thread exists on this topic over on the GSIII board, and I'm not trying to duplicate threads. I'm really just wondering whether any Note 3 users have experienced this patricular wakelock, and maybe what you've done to combat it on this particular phone. I've already tried some of the things others have suggested from other phones (disable Google+, disable Hangouts etc.) I'm really at my wit's end.
Thanks for your time and I appreciate any input.
This is also what is causing my rooted Note 3 to not go to deep sleep.
From previous xda threads, it looks like it is also present on the S3, maybe other phones too.
example:
http://forum.xda-developers.com/showthread.php?t=1811365
Maybe the solution is to just turn off Mobile Data when you are not using internet.