Database Users

Auto-Rotate is annoying me.

How can Turn off the autorotate feature? Im Running JFv1.41. I did a search and can only find threads on other phones, I searched under G1, and only learned how to ENABLE it.
Thanks

Dredge said:
How can Turn off the autorotate feature? Im Running JFv1.41. I did a search and can only find threads on other phones, I searched under G1, and only learned how to ENABLE it.
Thanks
Click to expand...
Click to collapse
open the app "droidsans tweak tools" and there's a button to disable auto-rotate.

I don't see that app... What am I missing?
I know im not crazy. Just a n00b

Are you talking about auto-rotate in the browser or for the home screen?
If it's the browser, you can disable it the browser settings. If it's the home screen, you need to search the market for DroidSans Tweak tools and disable it there.
At some point, you must have un-installed DST if your home screen is auto-rotating.

I bet thats what it is. The guy I bought the phone from did a wipe, and all the apps were lost, but the firmware was still on there.

You guys kick ass. Thanks for your patience. Ive had alot of questions since just yesterday and you guys always help within 5 minutes!
It worked like a charm. I love this community!

Dredge said:
You guys kick ass. Thanks for your patience. Ive had alot of questions since just yesterday and you guys always help within 5 minutes!
It worked like a charm. I love this community!
Click to expand...
Click to collapse
i agree...this forum rocks. i'm not very tech savvy, but i was able to root my G1, have apps installed to the SD card, etc, etc...all because of the kick-ass members of XDA.
and before the G1, this community helped me get WM6.1 on my dash.

xda is full of g1 jedis(im not one) they have helped me alot as well..so thanks guys

Is anyone else getting error messages when waking the phone back up? I would occasionally (1 out of 20 times) get an "application 'so-and-so' has stopped responding" and tapping "wait" would continue through the error like nothing else was wrong. As soon as I shut auto-rotate off, those errors went away. It was always a different program, too.

jcostantino said:
Is anyone else getting error messages when waking the phone back up? I would occasionally (1 out of 20 times) get an "application 'so-and-so' has stopped responding" and tapping "wait" would continue through the error like nothing else was wrong. As soon as I shut auto-rotate off, those errors went away. It was always a different program, too.
Click to expand...
Click to collapse
Happens to me every now and then, not as often though, may be once out of 50 times. See what program it is, if it's one from the market then you can remove it ( I would, I don't need anything on my phone that doesn't run correctly or hogs my precious memory). If it's stock... well.. you're SOL, just wait for Android to implement some better way of managing memory.
Good luck

borodin1 said:
Happens to me every now and then, not as often though, may be once out of 50 times. See what program it is, if it's one from the market then you can remove it ( I would, I don't need anything on my phone that doesn't run correctly or hogs my precious memory). If it's stock... well.. you're SOL, just wait for Android to implement some better way of managing memory.
Good luck
Click to expand...
Click to collapse
I've noticed on occasion I also get it with auto-rotate disabled, but not nearly as often. Maybe a couple times so far since I've gotten my replacement last week.
When it would hang, it was pretty much any random process. One time it was Alarm, other times something else, never a particular process. I think it has to do with the phone sleeping and maybe the accelerometer is oriented one way and it wakes up for an event in another position and then hangs - I don't know. It was never really a problem and I don't think the hung processes were wasting battery so I'll just reenable it.

/INIT process Desire HD lag problems...SOLVED ! See post 1

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%.

Battery life in SwiftDroid (may apply to other ROMs too).

Hai,
Since nobody bothered to answer my call to track down what drains the battery I decided to just post my findings and you do with it whatever you like...
In recent couple of months I've been experiencing quite nice battery life, almost a week on standby, which is basically on par with original LG ROM. The trick is simple:
It's happening as long as the Gallery app is NOT running.
I don't know what this piece of software does but when it's loaded to memory it stays in there and ignores attempts to terminate it, doesn't sleep when phone wants to and eats battery in a matter of single day. Unfortunately it seems some other apps use it directly or indirectly, like when Wi-Fi starts and/or by Market for example. Thus my solution is just to force close the Gallery after I finish activities which seem to require it.
I don't know whether root of the problem is with the app itself (like, CM modifications made so it's more cool, at the price) or it's just something else unearthed by certain SwiftDroid's configuration. To anyone who wishes to furher investigate my sincerest good luck. And I'd be grateful if results were published too.

hmskrecik said:
Hai,
Since nobody bothered to answer my call to track down what drains the battery I decided to just post my findings and you do with it whatever you like...
In recent couple of months I've been experiencing quite nice battery life, almost a week on standby, which is basically on par with original LG ROM. The trick is simple:
It's happening as long as the Gallery app is NOT running.
I don't know what this piece of software does but when it's loaded to memory it stays in there and ignores attempts to terminate it, doesn't sleep when phone wants to and eats battery in a matter of single day. Unfortunately it seems some other apps use it directly or indirectly, like when Wi-Fi starts and/or by Market for example. Thus my solution is just to force close the Gallery after I finish activities which seem to require it.
I don't know whether root of the problem is with the app itself (like, CM modifications made so it's more cool, at the price) or it's just something else unearthed by certain SwiftDroid's configuration. To anyone who wishes to furher investigate my sincerest good luck. And I'd be grateful if results were published too.
Click to expand...
Click to collapse
i deleted this slow sh** from /system/app and installed QuickPic!

hmskrecik said:
almost a week on standby
Click to expand...
Click to collapse
Are you joking? Should i use my phone as a doorstop,or what else?
EDIT: And,an old trick: when an app stays opened,to prevent it to reload again you have to delete his user data (works with Maps and Gmail too)

Eth4n said:
Are you joking? Should i use my phone as a doorstop,or what else?
Click to expand...
Click to collapse
You do with your phone what it damned pleases you. In case you haven't noticed the battery life is most often reported as either standby time or call time. In my typical usage battery lasts no less than two or three days but what 'typical usage' means may mean totally different things to me and to you.
Eth4n said:
EDIT: And,an old trick: when an app stays opened,to prevent it to reload again you have to delete his user data (works with Maps and Gmail too)
Click to expand...
Click to collapse
Hm, even more shotgun approach to what I described. Having user data could be the primary reason for keeping the app installed. But thanks for tip anyway, may come handy one day.

There is gr8 app on xda, better batery state. With this app you can see what aplication keep wake lock, use cpu, gps, etc...

Is it possible to disable auto RAM clearing?

Hi, I know people are usually looking for opposite, but this happened to me yesterday: was playing score oriented game without save option for 3 hours going for personal best, still not dying and it was 2 AM. So I just left it running with pause and screen off. It was working that way whole day for me. But in those long 8 hours of innactivity phone automaticly killed it, started loading like newly launched app. I was so mad I instantly uninstalled game and wanted to smash that phone. I have my hands to clear my ram manually when I really need it, no need for this nobrain automatic cleaning. When I pause app running I want it to stay there unless I decide to kill it, no matter what. Dont care about some lag or battery life. For me only reason to buy expensive phones like this instead of 150€ phones is gaming, portable console (actually phonecalls and SMS are like 3% of my phone usage). On my computer when I leave singleplayer game minimalised its there (even after few days) as I left it. Is there any way to make it possible on android? Smashing clear ram manually 150 times per day is better option for me than this auto clearing bull***t. My phone is rooted, but I am noob in android, have no idea if its even possible to do.
EDIT: Sorry, bad section, didn't notice Q&A, thought this is just offtopic general discussion about anything S7 related. Can you please move it?

The phone shouldn't kill any apps by itself unless...
1. You have some memory clearing apps that do that.
2. Your phone run out of memory. Some ****ty app or game that is poorly written can cause memory leak which continuously taking more and more memory until process being killed when the phone run out of memory.
3. Your phone restarted when you sleep.
Also memory clearing apps are useless on android and can actually slow down your phone a lot.
Sent from my SM-G935F using Tapatalk

Thx for reply, i did not download any memory cleaners but there is some default samsung app for it, must check it for settings. I dont think phone restarted - it might, but it never happened to me on this version of rom during day. Memory leak from some apps or something wrong with this app - that might be the case. Or maybe I screw something in aroma while installing rom where I chose some batery/performance tweeks without description what they actually do.

*Telcontar* said:
...
EDIT: Sorry, bad section, didn't notice Q&A, thought this is just offtopic general discussion about anything S7 related. Can you please move it?
Click to expand...
Click to collapse
Hi,
Done, thread moved in Q&A section.
Friendly advice: next time, use the report button to ask the thread to be moved, any moderator affected to the area you post will handle this. We moderators don't read every threads so if you only write "Can you please move it?", good chance it won't be noticed
Thanks!

Is there a way to test memory? Lots of weird issues!

I'm not sure if it's my device or an OS update or what. For whatever reason, apps just don't seem to be able to stay running in the background on my OP5. Doesn't matter what kind of app it is, but whenever I to switch to it using the recent's list or pressing the icon, they almost always seem to start up as if they haven't been opened yet. It seems to be getting worse as time goes by. I'm running the lastest OS version and have also factory reset my phone as well as removed a bunch of unused apps and photos.
The thing is my first device didn't have this problem. But I had a hardware issue and my phone was replaced. But about the same time I got my replacement phone, I also had a major OS upgrade occur. So I'm not sure if my replacement device has some sort of defect, or it's just a normal thing that happens now.
Also, on top of apps always starting up from scratch every single time no matter how long it's been since I just used them; now I'm finding apps disappearing from my recently used list! WTF is going on???
I have all optimizations disabled as much as I can, I've deleted a ton of apps and photos to make sure I'm not running out of memory. Yet this phone is still acting very weirdly.
I've searched and used some "memory testers" that I've found in the Play store and they say everything is fine. But I'm not confident they are actually testing the memory or system properly.
Help please!!

ned4spd8874 said:
I'm not sure if it's my device or an OS update or what. For whatever reason, apps just don't seem to be able to stay running in the background on my OP5. Doesn't matter what kind of app it is, but whenever I to switch to it using the recent's list or pressing the icon, they almost always seem to start up as if they haven't been opened yet. It seems to be getting worse as time goes by. I'm running the lastest OS version and have also factory reset my phone as well as removed a bunch of unused apps and photos.
The thing is my first device didn't have this problem. But I had a hardware issue and my phone was replaced. But about the same time I got my replacement phone, I also had a major OS upgrade occur. So I'm not sure if my replacement device has some sort of defect, or it's just a normal thing that happens now.
Also, on top of apps always starting up from scratch every single time no matter how long it's been since I just used them; now I'm finding apps disappearing from my recently used list! WTF is going on???
I have all optimizations disabled as much as I can, I've deleted a ton of apps and photos to make sure I'm not running out of memory. Yet this phone is still acting very weirdly.
I've searched and used some "memory testers" that I've found in the Play store and they say everything is fine. But I'm not confident they are actually testing the memory or system properly.
Help please!!
Click to expand...
Click to collapse
Please read ahead several posts from here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post78727896

strongst said:
Please read ahead several posts from here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post78727896
Click to expand...
Click to collapse
But I have been having these issues for the better part of a year, well before I got the Pie update. Granted, Pie has made it much worse, but it's been going on for a very long time now. And it seems to be getting much worse as time goes by.

ned4spd8874 said:
I'm not sure if it's my device or an OS update or what. For whatever reason, apps just don't seem to be able to stay running in the background on my OP5. Doesn't matter what kind of app it is, but whenever I to switch to it using the recent's list or pressing the icon, they almost always seem to start up as if they haven't been opened yet. It seems to be getting worse as time goes by. I'm running the lastest OS version and have also factory reset my phone as well as removed a bunch of unused apps and photos.
The thing is my first device didn't have this problem. But I had a hardware issue and my phone was replaced. But about the same time I got my replacement phone, I also had a major OS upgrade occur. So I'm not sure if my replacement device has some sort of defect, or it's just a normal thing that happens now.
Also, on top of apps always starting up from scratch every single time no matter how long it's been since I just used them; now I'm finding apps disappearing from my recently used list! WTF is going on???
I have all optimizations disabled as much as I can, I've deleted a ton of apps and photos to make sure I'm not running out of memory. Yet this phone is still acting very weirdly.
I've searched and used some "memory testers" that I've found in the Play store and they say everything is fine. But I'm not confident they are actually testing the memory or system properly.
Help please!!
Click to expand...
Click to collapse
There is no solution for this. Maybe you can try a custom kernel. Apps killed in background is a normal thing for OnePlus.
https://dontkillmyapp.com
You can see this article

This is beyond acceptable now. Apps are being closed while I have them open and are using them! It's different apps, different types of apps, random times, nothing to connect them. Is there anything at all that I can do?