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%.
I've rebooted the Tab a few times, but in OS Monitor, the "Download" process is running all time time using at least 30% processor!
What's the deal; anyone know? I'm unrooted and running the latest Tw update.
Thanks!
Ended up being MediaServer running. I stopped in in Manage Applications->Running. I stopped it and my CPU went to normal levels. My home screen responses got alot better too.
I vaguely remember this issue on my Samsung Fascinate too.... MediaServer always got hung up on some type of sync'ing.
I'm having the same issue. So what is actually causing this? Any way to disable the mediaserver all together? It seems to keep re-starting itself eventually.
I haven't found a way. It doesn't affect battery life as far as I can see, but it lags my Netflix if its running because its already sapping up 50%+ CPU.
Yeah, I've noticed that the tab gets laggy when it's running, and it speeds up a lot when I kill it in OS Monitor. That's my main reason for wanting it closed. It doesn't seem to affect battery life while the screen is off, but when the screen is on (such as reading an ebook) it absolutely reduces battery life. I just tried freezing it in Titanium Backup but it resulted in all the gapps (such as Gmail) crashing and refusing to open after rebooting.
I also noticed that on some boots, it's DRM Protected Storage Content rather than Download Manager. I just froze that instead and haven't noticed any issues from it yet, but I won't know for sure until rebooting.
I'm having a very similar issue, though it's process.android.media that is causing the problems. I have to manually kill the Media Storage service several times per day. It's quite annoying.
funnelweaver said:
I'm having a very similar issue, though it's process.android.media that is causing the problems. I have to manually kill the Media Storage service several times per day. It's quite annoying.
Click to expand...
Click to collapse
This Media application is what calls the Download Manager service. Killing this app also kills the service that's using alot of CPU processing.
I've noticed that I get a lot of errors in logcat pertaining to the sdcard. They are usually right around the time that a media process starts up, but I have hundreds of them throughout the log:
E/Environment( 1250): getExternalStorageState/mnt/sdcard
E/Environment( 1695): getExternalStorageState/mnt/sdcard
See attached screenshot.
It appears something is wrong with reading the sdcard, and I'm guessing this is maybe causing the media process to hang eating all the cpu?
I am in need of help in dealing with games that keep eating battery life after the game is closed. I have downloaded different kinds of app killers and i do not see them on the list but under battery options i see every game i have played since i had the tablet on. Is there a better option or am i doomed to turning my nook on/off after every game i play?
I am new to all of this and may be off base here. But in all of my mind melting reading here I picked up Nook Tweaks off the market for free and from what I have read maybe some of those settings might help you.
Check this out http://forum.xda-developers.com/showthread.php?t=1104039 Maybe this will help. I am still experimenting and learning.
jsnake said:
I am new to all of this and may be off base here. But in all of my mind melting reading here I picked up Nook Tweaks off the market for free and from what I have read maybe some of those settings might help you.
Check this out http://forum.xda-developers.com/showthread.php?t=1104039 Maybe this will help. I am still experimenting and learning.
Click to expand...
Click to collapse
That's a good program for overclocking and boosting audio, sadly not what i need atm
I was having the same problem. I downloaded an app called 1 click cleaner. after its up and running I simply go into the app and click the cache clear button. after that it will pull up any aps or games that I ran. I can click them one at a time and force stop the app first then if i want I can also clean any cache associated with that app. It stops any apps continuing to run and draining my battery?
Some apps shut down properly if you use the back arrow to quit rather than just pressing the home button. Look for a quit button in those games.
I've had Opera stay running in the background if I didn't back out.
calixt0 said:
I was having the same problem. I downloaded an app called 1 click cleaner. after its up and running I simply go into the app and click the cache clear button. after that it will pull up any aps or games that I ran. I can click them one at a time and force stop the app first then if i want I can also clean any cache associated with that app. It stops any apps continuing to run and draining my battery?
Click to expand...
Click to collapse
I tried this app today and it clears cache but does not bring up anything else even though on the battery use list there are games still running even when i hit the back button to close games. I have had nothing but battery issues ever since i rooted this NC ; / What is even more frustrating is i read on these forums how people are getting 2 days use out of the battery even with moderate use and if i do anything i lose 20-30% of my battery. There must be a way to get this set up right but i feel like only those in the know want to keep their secrets.
From what I've found, the battery usage screen on cm7 is not only applications that are running but also lists apps that have been running but are now closed. If the app doesn't show up in a task killer (I use ES Task Manager) it's not running. Certain games are high demand on the system and will drain the battery more quickly than reading apps (like aldiko) The last tip I have is to turn the screen brightness down. The screen is the biggest battery killer. Also, turn off wifi when you're not using it.
These are what I do and end up getting 2 days of moderate (low gaming high reading) use.
j8048188 said:
From what I've found, the battery usage screen on cm7 is not only applications that are running but also lists apps that have been running but are now closed. If the app doesn't show up in a task killer (I use ES Task Manager) it's not running. Certain games are high demand on the system and will drain the battery more quickly than reading apps (like aldiko) The last tip I have is to turn the screen brightness down. The screen is the biggest battery killer. Also, turn off wifi when you're not using it.
These are what I do and end up getting 2 days of moderate (low gaming high reading) use.
Click to expand...
Click to collapse
i have the screen on 25%ish ever since i got the NC. i do not play alot of games atm and i usually read a little before bed and still i lose about 20% an hour.
Lsjreadingpa said:
i have the screen on 25%ish ever since i got the NC. i do not play alot of games atm and i usually read a little before bed and still i lose about 20% an hour.
Click to expand...
Click to collapse
That sounds awfully high. What Rom and version # are you using? Also, what CPU governor and/or overclock settings? It sounds like something is wrong.
That said, I have had "rogue" apps that keeping restarting and usually just end up removing them because they weren't worth the trouble. Personally, I also use GoLauncher and in the applications menu it has a nifty screen to conveniently show the currently-running apps with a button to close them.
I am running cm7.1 and my governor is on conservative. I do not have it overclocked, its at stock 300/800.
Anyone able to help?
Hi,
Anyone been keeping an eye on hotplugging on the n9005 ?
Mine is still unrooted, so I'm talking 100% vanilla Samsung configuration...
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
At some point, after a few hours of uptime, sometimes only after quite a many (20h+), I just notice that it will never drop below 2 or 4, never had it lock on 3 minimum, so can't comment on that scenario.
Once this happens, it's impossible to get back to single core even on very low load.
Also when leaving the device doing nothing, freq. drops to 300MHz and still 4 cores remain online.
There is obviously an impact on battery drain as well.
Only way to get back to normal is to reboot...
JP.
I've noticed the opposite issue, two cores just going offline forever until I reboot the device.
So that would point to obvious hotplugging issues, except if you ran into thermal throttling, maybe.
Were you running some heavy stuff when this happened ?
JP.
i tested it out of curiosity using the widget in system monitor app.
i have exactly the same issue as SentinelBorg above. the two cores go offline and never come back online until the next restart.
very wierd.
Well for the very least we can conclude hotplugging is flawed in the current firmware ...
As soon as we get a proper recovery (nandroid restore that don't bootloop) I'll start working on an improved kernel, this is just not acceptable for a top notch 700€ pricetagged device
JP.
Send from my Note 3 (n9005)
Latest case ...
Send from my Note 3 (n9005)
Again ...
Send from my Note 3 (n9005)
You're on full stock. Doesn't that mean you have no options regarding CPU government?
nakedtime said:
You're on full stock. Doesn't that mean you have no options regarding CPU government?
Click to expand...
Click to collapse
Correct, so I cannot do anything about this misbehaving, except reboot.
I want to know whether this is something others observe as well.
The thing is, if you're not looking at it, you won't know it's happening, cause who really keeps an eye on online cores all the time ? I do as I do kernel coding and as such also work on governors, which make me look at stuff like that.
If this happens of yours, you'll just have a hotter Note 3 with less lasting battery without knowing why, or worse without knowing battery easily could last longer if that was fixed.
This clearly is a bug in the current firmware, since as you correctly stated, being full stock unrooted, I can't be influencing this in any other way than applying load to the CPU which is clearly not the case as you can see in the screenshots... and it just happens randomly.
Once I start on a Note 3 kernel that will be in the top list of things to take care of.
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
I would have gone with the N9000 if I knew how to develop a kernel. BIG.little sounds like so much fun to dev on.
PS
Have you found any Info about the thermal throttling? I'd love to be able to manipulate the temps for less heat when over clocking.
I was actually not going to get any more Samsung device because of crappy open source support they (in fact don't) give
I ended up going for the note 3 because of the specs and exactly because it was the Qualcom and not the Exynos version and a one time offer I could not refuse, but I will go nowhere Samsung's own super secret Exynos CPUs ever again unless they change their policies, which I doubt.
I just do hope I won't regret my move...
JP.
Sent from my SlimBean 4.3 build 1.8 / Yank555.lu CM10.2 kernel v1.6g-beta4 (Linux 3.0.99) powered Galaxy S3 i9300
exactly the same here, after a reboot everything is back to normal
Sent from my SM-N9005 using Tapatalk 2
Happened again after ~10h uptime while watching a live video stream...
Cores went to a steady 4 online, load was unchanged over a longer period (~45 mins of video stream over WiFi).
This makes little sense, hotplugging is flawed.
JP.
PS: Still stock unrooted.
Send from my Note 3 (n9005)
This is still happening for me, reboot solves it. Running 4.4.2 and thought this should be solved by now.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Stock kitkat XXUENB3, unrooted. I have a similar problem when all of the sudden all cores are stuck online with core 1 and 2 stuck at 1958 mhz and core 0 and 3 scaling normally just not going offline. A reboot fixes the issue untill it happens again randomly. This is my last Android device and I had gs2,gnex,n4 and now n9005.
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
ciprianruse88 said:
I've rooted and when the issue happens, disabling mp decision and enabling it again fixes the issue so this means that hotplug doesn't play well. Maybe a custom kernel will fix this issue.
Click to expand...
Click to collapse
Yes, long time I've open this thread
Indeed, on TW I used to do just that, "pkill -9 mpdecision", which killed the daemon and it respawned and all was back to usual.
I've since then moved to CM11, and this never happened again ever since, so I expect this to be a TW related issue, since mpdecision had the same MD5 signature in CM11 as on my stock 4.3 TW ROM.
And it looks like if the problem still persists on KK TW...
But it's certainly not a kernel related issue, as I've use my own kernel on JB TW, where this happened as well, once I went CM11, I ported my kernel to CM, and as I mentioned, never happened ever since.
Might be TW messing with DVFS (for benchmark cheating and maybe other things...).
Maybe worth trying to use Wanam's Xposed Module and disable ROM DVFS.
JP.
2 cores always online and the other 2 always offline= Dual Core
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
SAVVAS. said:
Ok guys I have experienced the bug with 2 cores being always offline which basically makes your Note 3 a dual core phone many times in the past untill I found what caused this! Even firing up Antutu the cores are still 2 and not 4 online! So yeah at first a reboot was an easy and effective sollution but that was not enough so I devoted 2 days trying to find out what caused this. Guess what? The problem was inside one of Samsung apps, specifically the bloody S-Finder app! I can reproduce the bug 100% whenever I want so I am very sure about it! Also I have tested this on 2 other Note 3s (n9005) and I noticed the same bug , with 4.3 and unfortunately now on 4.4.2!
Steps to reproduce it:1) Fire up S-finder 2) Search any app and launch it or even without launching just only by typing on the search bar the phone enters into dual core mode(!) after few seconds 3)Now this is the critical step, remember now the phone is already having only 2 cores enabled so if you press the home button then you are stuck with the buggy dual core mode!!! So this is how you end up with only 2 out of 4 cores working!
The sollution is of course to reboot the phone but another more faster and specific sollution is to close the S-Finder with only this (correct) way: while you are on the S-finder app close it by simply pressing the back button untill it exits completely and you are out to the menu. Incase you are not in the S-finder app then you must check if the program is shown in the recently used apps(longs pressing the home button) then tap on it to open it and then close it by hitting the back button." Don't close/kill it from the task manager or from the recently used apps, only close it when you are inside of the app and hitting the back button!"
Synopsis All in all, the culprit at least on my case is the S-finder app in which when it is used it somehow forces the phone to get into dual core mode and it stays like this because you forget to properly close it after the search is done. The sollution is simply closing the S-Finder gently/properly by using the back button from the inside of the app and not with any other way.
I don't know if this is truly a bug of Samsung or just a sneaky way to increase/improve the battery life at the expense of performance but I surely know that many people have this issue without even realising it!
I said too many things so that I can give a detailed review on this bug, I hope I have expressed it clearly and not to confuse you!
I think it is a very serious issue and it should be fixed as well as inform people about it!
Click to expand...
Click to collapse
Yes. I've did the exact same thing and cpu was dual core but after I've reset mp decision I couldn't reproduce it anymore. Good catch!
Yank555 said:
I use Android Tuner's online core notifications to keep an eye on this, there are other apps that can to this as well.
Click to expand...
Click to collapse
How did you enable the online core notifications in Android Tuner?
Having Lag & Heat Issues???
Is anyone having lag issue or any heat issues? I guess I have one of the problem notes as mine has extreme lag and heat problems. I have cleared all caches and have also factory reset several times. What's weird is that the lag will come and go, but it's there more often than not. Even scrolling in settings has the jitters.
Any ideas anyone. I might be better off going through the miserable process of exchanging through the mail.
Thanks in advance for any help!
You'll have to boot to safe mode to see if the issue persists. Also, make sure power saving mode isn't on (I've left it on before).
Majin101 said:
You'll have to boot to safe mode to see if the issue persists. Also, make sure power saving mode isn't on (I've left it on before).
Click to expand...
Click to collapse
I'm experiencing the same issues - overheating, slowing down, serious lag. It's simply terrible. I exchanged it and the new one is just as bad and maybe even worse.
[email protected] said:
I'm experiencing the same issues - overheating, slowing down, serious lag. It's simply terrible. I exchanged it and the new one is just as bad and maybe even worse.
Click to expand...
Click to collapse
welcome to samsung
I have none of these problems and i am a heavy user
Sent from my SAMSUNG-SM-N930A using XDA-Developers mobile app
My guess is it has to do with one or multiple of the apps you have installed. There is a 3 step process to fix this issue.
#1 - See if any of the apps you have installed are running rouge. Check, battery usage, RAM usage, and Data Usage to see if you have any bad apps. Uninstall any 3rd party apps that you installed that are running too much. They may just still need updated to be optimized for this new device. Also you can use the "sleep" (doze) feature in battery management to restrict apps that are running TOO much in the background. Also on any apps that are using too much data or RAM check the permissions. If an app does not need access to Data, Media etc to work properly turn off those permissions.
#2 Debloat the device. I like "Package Disabler Pro". Basically if it has Facebook, FB, or ATT in the name you should disable it. Also you can go through an disable any Samsung software you do not use as well. I would be careful about using the "disable all bloatware" button because it is not setup correctly for this new device yet.
#3 Give it some time. It you have a TON of media on a micro EXSD card then it can take a new phone a long time to index and create thumbnails for all of that information. It should speed up i about a day or so once it finishes indexing. this will also effect your battery life till it is completed.
ShrekOpher said:
My guess is it has to do with one or multiple of the apps you have installed. There is a 3 step process to fix this issue.
#1 - See if any of the apps you have installed are running rouge. Check, battery usage, RAM usage, and Data Usage to see if you have any bad apps. Uninstall any 3rd party apps that you installed that are running too much. They may just still need updated to be optimized for this new device. Also you can use the "sleep" (doze) feature in battery management to restrict apps that are running TOO much in the background. Also on any apps that are using too much data or RAM check the permissions. If an app does not need access to Data, Media etc to work properly turn off those permissions.
#2 Debloat the device. I like "Package Disabler Pro". Basically if it has Facebook, FB, or ATT in the name you should disable it. Also you can go through an disable any Samsung software you do not use as well. I would be careful about using the "disable all bloatware" button because it is not setup correctly for this new device yet.
#3 Give it some time. It you have a TON of media on a micro EXSD card then it can take a new phone a long time to index and create thumbnails for all of that information. It should speed up i about a day or so once it finishes indexing. this will also effect your battery life till it is completed.
Click to expand...
Click to collapse
I used the disable all bloatware. Looks to be working fine.
Sent from my SAMSUNG-SM-N930A using Tapatalk
borijess said:
I used the disable all bloatware. Looks to be working fine.
Click to expand...
Click to collapse
Yeah it will break Samsung Pay though... I think it's related to the UIBCVirtualSiftkey app, but have not confirmed that. Also it does not get nearly all of the bloatware. There is a ton of new AT&T junk it does not disable as well as a bunch of new Facebook crap and Samsung crap.
ShrekOpher said:
Yeah it will break Samsung Pay though... I think it's related to the UIBCVirtualSiftkey app, but have not confirmed that. Also it does not get nearly all of the bloatware. There is a ton of new AT&T junk it does not disable as well as a bunch of new Facebook crap and Samsung crap.
Click to expand...
Click to collapse
Can you provide a list?
Sent from my SAMSUNG-SM-N930A using Tapatalk
borijess said:
Can you provide a list?
Click to expand...
Click to collapse
Definitely. It gave me the perfect opportunity to try out the scroll capture. Let me know if you have any questions. This is what I have disabled so far without any issues. Once I get a full completed list I'll probably do a write up about how to clean up the dock ROM. I think I'm about 70% done with the list.
So far I'm getting about 6.5 hrs of SOT and about 28 his of usage.
ShrekOpher said:
Definitely. It gave me the perfect opportunity to try out the scroll capture. Let me know if you have any questions. This is what I have disabled so far without any issues. Once I get a full completed list I'll probably do a write up about how to clean up the dock ROM. I think I'm about 70% done with the list.
So far I'm getting about 6.5 hrs of SOT and about 28 his of usage.
Click to expand...
Click to collapse
What is the file that could mess up Samsung pay? I can always restore disabled apps correct?
Sent from my SAMSUNG-SM-N930A using Tapatalk
borijess said:
What is the file that could mess up Samsung pay? I can always restore disabled apps correct?
Click to expand...
Click to collapse
I am not positive but I think it's the UIBCVirtualSoftkey if the doesn't fix it. Just enable all of the stuff you disabled and reboot. Then only disable what's on my list. I can confirm is working with my setup.
I'm exchanging mine tomorrow and was hoping for better news but from your experience it sounds like I may have to deal with an expensive piece of crap.
ShrekOpher said:
My guess is it has to do with one or multiple of the apps you have installed. There is a 3 step process to fix this issue.
#1 - See if any of the apps you have installed are running rouge. Check, battery usage, RAM usage, and Data Usage to see if you have any bad apps. Uninstall any 3rd party apps that you installed that are running too much. They may just still need updated to be optimized for this new device. Also you can use the "sleep" (doze) feature in battery management to restrict apps that are running TOO much in the background. Also on any apps that are using too much data or RAM check the permissions. If an app does not need access to Data, Media etc to work properly turn off those permissions.
#2 Debloat the device. I like "Package Disabler Pro". Basically if it has Facebook, FB, or ATT in the name you should disable it. Also you can go through an disable any Samsung software you do not use as well. I would be careful about using the "disable all bloatware" button because it is not setup correctly for this new device yet.
#3 Give it some time. It you have a TON of media on a micro EXSD card then it can take a new phone a long time to index and create thumbnails for all of that information. It should speed up i about a day or so once it finishes indexing. this will also effect your battery life till it is completed.
Click to expand...
Click to collapse
I used this app and it's worked wonders.
Sent from my Galaxy Note7 using XDA Labs
This phone lags a lot especially in Chrome and other scrolling apps.. sometimes switching between apps takes lot of time too...I have been using Samsung phones for quite sometime, but unfortunately this is the phone lagging more than any other phone for me..debloated almost 150 apps, still the same..and it gets hot as well when watching videos...none of this happened for me on Note 5...I think Samsung screwed with Note7 software..when they initially released Grace UX software for Note 5, it was very smooth...but the final Note7 software seems to be laggy...the same apps and setup on Note5 doesn't give me these issues....gonna return and try my luck with new one...but good thing is battery life has been very good for me...easily 5hrs SOT whereas on Note5, I used to get only 3.5 hrs
Sent from my SAMSUNG-SM-N930A using Tapatalk
---------- Post added at 11:32 PM ---------- Previous post was at 11:22 PM ----------
chrispyutec said:
Having Lag & Heat Issues???
Is anyone having lag issue or any heat issues? I guess I have one of the problem notes as mine has extreme lag and heat problems. I have cleared all caches and have also factory reset several times. What's weird is that the lag will come and go, but it's there more often than not. Even scrolling in settings has the jitters.
Any ideas anyone. I might be better off going through the miserable process of exchanging through the mail.
Thanks in advance for any help!
Click to expand...
Click to collapse
I am exactly facing this issue..I am a heavy XDA user, so I monitor all the apps on phone and debloated lot (around 150) apps...still the same.. thing is lag doesn't happen all the times..but it starts from no where..but the phone consistently gets hot while moderate usage
Sent from my SAMSUNG-SM-N930A using Tapatalk
When the phone is working properly, bloatware should make no noticeable difference and debloating is unnecessary.
My Note 7 usually responds instantly, with no lag, no matter how heavily I'm using it. That's with nothing disabled or debloated. (I'm using the Google Now launcher but everything else is stock/default, with no esoteric apps or settings.)
However, on three occasions in the week I've had the phone, it's gotten into a mode with serious lag while typing. In this mode, even though the characters I type still show up on the screen instantly, I can type 3 or 4 characters with no sound feedback or vibration feedback; then, there will be 3 or 4 delayed clicks and vibrations in rapid succession.
When this serious-lag mode starts, it continues even if I close all apps and put the phone in Airplane mode. It also makes no difference if I turn on power-saving mode, or even maximum power-saving. The only thing I've found that fixes it (for a while) is rebooting.
The intermittent occurrence of the serious-lag problem shows that it's not a matter of the phone being underpowered or overloaded. There's some specific bug that needs to be fixed.
UPDATE: It just happened for a fourth time. And when the serious-lag mode starts, it's not just typing that has a delay with audio feedback. The feedback delay also occurs when I tap on icons, tap on the Back or Recent-apps soft-buttons, etc. There's a delay of up to a second or two between tapping and hearing the feedback.
On the other hand, compute-intensive tasks--such as playing streaming video--work properly even when the phone is in serious-lag mode. So that's further evidence that there is some specific bug, and not a general problem of being underpowered or overloaded.
Gary02468 said:
When the phone is working properly, bloatware should make no noticeable difference and debloating is unnecessary.
My Note 7 usually responds instantly, with no lag, no matter how heavily I'm using it. That's with nothing disabled or debloated. (I'm using the Google Now launcher but everything else is stock/default, with no esoteric apps or settings.)
However, on three occasions in the week I've had the phone, it's gotten into a mode with serious lag while typing. In this mode, even though the characters I type still show up on the screen instantly, I can type 3 or 4 characters with no sound feedback or vibration feedback; then, there will be 3 or 4 delayed clicks and vibrations in rapid succession.
When this serious-lag mode starts, it continues even if I close all apps and put the phone in Airplane mode. It also makes no difference if I turn on power-saving mode, or even maximum power-saving. The only thing I've found that fixes it (for a while) is rebooting.
The intermittent occurrence of the serious-lag problem shows that it's not a matter of the phone being underpowered or overloaded. There's some specific bug that needs to be fixed.
UPDATE: It just happened for a fourth time. And when the serious-lag mode starts, it's not just typing that has a delay with audio feedback. The feedback delay also occurs when I tap on icons, tap on the Back or Recent-apps soft-buttons, etc. There's a delay of up to a second or two between tapping and hearing the feedback.
On the other hand, compute-intensive tasks--such as playing streaming video--work properly even when the phone is in serious-lag mode. So that's further evidence that there is some specific bug, and not a general problem of being underpowered or overloaded.
Click to expand...
Click to collapse
Curious, do these typing lags occur on the hangouts app?!?! It seems to be the ONLY app on my Note 5 (and all the other phones I've used) that has a VERY NOTICEABLE KEYBOARD LAG, especially with Samsung Stock keyboard. This happens even with other keyboards, but is WORST with samsung keyboard.....
quordandis said:
Curious, do these typing lags occur on the hangouts app?!?! It seems to be the ONLY app on my Note 5 (and all the other phones I've used) that has a VERY NOTICEABLE KEYBOARD LAG, especially with Samsung Stock keyboard. This happens even with other keyboards, but is WORST with samsung keyboard.....
Click to expand...
Click to collapse
No, the problem I'm seeing is unrelated to any app or keyboard. When my phone is in serious-lag mode, the problem occurs across the board. When it's not in lag-mode (which it usually isn't), then there's no lag in any app, including Hangouts.
Gary02468 said:
No, the problem I'm seeing is unrelated to any app or keyboard. When my phone is in serious-lag mode, the problem occurs across the board. When it's not in lag-mode (which it usually isn't), then there's no lag in any app, including Hangouts.
Click to expand...
Click to collapse
Hmmm.....interesting....I use the app os monitor to show which processes are running at high cpu %. Perhaps that can shed some light on your lag issue?
quordandis said:
Hmmm.....interesting....I use the app os monitor to show which processes are running at high cpu %. Perhaps that can shed some light on your lag issue?
Click to expand...
Click to collapse
It happens even with all apps closed, no heat, no battery drain. It's not a side-effect of the phone being bogged down with anything.