Related
i have been on several roms and when i hit about 250apps+ on my internal memory my apps start to not show up in the app drawer but they are still installed then when i restart the launcher my all my apps will show but then again after 10min its the same thing..my apps start to disappear leaving me with about 20 in there? i have been on gingerbread and ics, is this normal for the sgs2?
Sent from my SPH-D710 using Tapatalk
i took sd card out then in twice and phone would not read it until i rebooted my phone now it can see my sd card hence apps are all back as normal. why does my phone kick out the sd card like that?
Sent from my SPH-D710 using Tapatalk
By any chance did you change kernels after loading those apps?
in my case my sd card kept un mounting not diminishing in available capacity. yup i did why? im on calkin el29 3.0 and then to flash the modem i did for just in case. Im going to have a little R&R over at the thread to see if it happens to other people. also does the below link could apply to the sgs2 system as well and work as a fix if needed?
forum.xda-developers.com/showthread.php?t=1863222
forum.xda-developers.com/showthread.php?t=1863222
Sent from my SPH-D710 using Tapatalk
I was killing apps with that task killer and i think that's what happened there is no option to exclude apps?
Sent from my SPH-D710 using Tapatalk
actually i have the issue again and its not the task killer this time. and its the internel storage not the sd card is there a fix
Sent from my SPH-D710 using Tapatalk
Fast Boot option may be the culprit
So, maybe the disappearing apps has nothing to do with storage type (sdcard, internal phone) and task killers?
This is actually a long-standing problem in Android OS, going back at least two years (donkey's years in this technology!)
Something about the interaction of the OS and an sdcard formated for holding apps creates odd behaviours.
Lots of complicated suggestions have been made, including reformatting sdcard, reinstalling ROMs, changing launchers (the one suggested here) and such.
None of these approaches seems really to solve the problem even in most cases.
What seems to be working for me (at least for the last week or so) is the following very simple tweak.
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report anything further on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (especially now that the chosen thread no longer is the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
I've been getting an external storage is low warning after downloading apps on google play. When I go to settings and check my storage space it shows that I'm not even close to being low. Has anyone else been having this problem?
Sent from my SM-N900T using Tapatalk 4
Yes, I have seen it only once. It happened when downloading multiple apps.
Sent from my SM-N900T
Hope it's just a fixable bug and won't cause any problems down the line.
Sent from my SM-N900T using Tapatalk 4
After this notification all my app updates fail to install!
Mexyl33t said:
Yes, I have seen it only once. It happened when downloading multiple apps.
Sent from my SM-N900T
Click to expand...
Click to collapse
I'm seeing the same thing, but not just once. For the past couple of weeks (since mid-October or so) this is happening every time I run Play Store update (which I have set not to occur automatically, but it makes no difference even when I change it back).
More importantly, once external storage reports it is in the range of 1 MB or so, every app thereafter dutifully downloads and then fails to install with error message: "Couldn't install on USB storage or SD card". Both "USB storage" (internal to phone but treated like a USB device) and SD card are multi-GB, and there is plenty of room. Still, no installation! :crying:
As I said, I have never saw this happen before the last couple of weeks.
Based on the limited info thus far on this little thread here, I'm not so sure it is my device or apps at all. Still, I will share what I did prior to finding this thread in the hope that it will help others and perhaps give clues to a skilled dev out there. :fingers-crossed:
At first, I thought it was something about my particular device/setup, which I find is almost always the case. Here are my basic particulars:
Droid Incredible "dinc", rooted, security OFF, with Tiny's mod of CM 10.1 (Jelly Bean 4.2.2), plus Tiny's ext4all patch to expand internal memory space to about 748MB.
My internal memory is getting a bit low despite moving most apps to SD card but it is still respectable:
"settings-->apps-->all" reports 200MB "internal storage" free, while Titanium Backup Pro summary for "internal" reports 249MB free.
(Can't quite figure why there is a difference in the numbers, but in this case it shouldn't matter.)
The only other significant recent additions of apps is that I purchased and installed the full version of "Air Control" game on 29 Sept. and purchased a 1-yr sub for Avast Mobile Security (AMS) on 3 Sept. The problem came about some time later, but Air Control's apparently forced presence in internal storage (see workaround #2 below) and AMS's involvement in scanning every app installation may be contributing factor(s).
As far as I can determine from Avast support resources, AMS scanning cannot be turned off temporarily and would have to be fully uninstalled, which is also not very easy on a rooted phone. So I have thus far left that stone unturned!
Maybe this bug is caused by Google Play Store client app or the Google online system? I followed the troubleshooting steps on the "known issues" Google Play Store page -- click on "Contact Us" to launch the troubleshooter and select "Download Unsuccessful":
Google Play Store support page
1. Clearing Google Play and Download Manager data caches alone made no difference.
2. Doing #1 AND rebooting my device did allow successful "update all" multiple installations.
3. Remounting SD Card was suggested, but I have not tried that option as yet. Maybe it would help?
Prior to tweaking the Play Store app (which may be all that is really needed), I found a couple of other workarounds that at least allow me to update my apps with a minimum of fuss -- no rebooting or labourious individual cache clearing required! Maybe these will help others, too:
1. Installed AVG Cleaner app that makes it easy to clear cache from download history + app caches in one swoop. It seemed to make a difference with some but not all of the smaller apps (<5MB), but no go with larger apps like Twitter and Chrome (>5MB). Not absolutely certain this tweak is really doing anything to help out this situation.
2. Uninstalled the game "Air Control" paid version that stubbornly refuses to be moved to SD Card. Titanium Backup Pro (TBP) says it moves it, but in fact it does not. At least some large chunk of it remains in internal storage. Once I uninstalled Air Control using TBP, I was able to install all updates, BUT ONLY MANUALLY (i.e. one at a time) in Play Store. Auto-updating and "update all" in Play Store continued to fail, whether the low external storage warning appeared or not.
3. I searched the web to see what fixes I could find, and came up with a recommendation for Lucky Patcher (LP), which reportedly can remove all traces of a misbehaving app through its "Troubleshooting" process.
Here is where I found this recommendation (see under "Option 1"):
How-to-fix-insufficient-storage-available-error-on-android-phones
I am now aware that LP is warez and does some pretty nasty things to crack security on apps (definitely not what I want to do -- I pay developers when they ask for it and am happy to support them!). :angel: I just wonder if LP's less nasty function of app cleaning would resolve this current issue. I actually haven't tried using LP yet in any respect.
Better yet, is there some other less potentially destructive app than LP or some other tweak/procedure that will fix this bug/issue?
As I said earlier, I have not taken the step of uninstalling Avast Mobile Security since it is so involved on a rooted Android.
Hoping there is a skilled dev or two out there who can tackle this one, or at least evaluate the workarounds and tweaks listed here. :fingers-crossed:
Autokiller Pro seems to help
Installing AutoKiller Pro (the paid version) and activating all the tweaks seems to end the problem.
I have had one forced reboot since setting up this app's tweaks, but this happens occasionally anyway, so unless it becomes a more common occurrence, I will not blame the app.
I have never recommended a particular app on XDA before, and I absolutely have no financial or other interest in the app or its dev.
It just seems to work, and all the manual workarounds recommended in my previous post are no longer required. I also do not waste time downloading app updates that the system refuses to install.
Try the free version first if you like, but I found that the tweaks that take effect with the Pro version are the key.
Has something to do with Android 4.3. It happens on my Nexus 7 also.
I would guess it is a TRIM bug. Perhaps the storage is not handling trim correctly.
sent from my sm-9005.
So I got this message again after rebooting my device. It's writen in german and says something like:
"We are sorry! The Application LGSystemServer has been closed".
After the error I can't do anything. It's reappearing so fast after clicking "ok", that I can't get into the settings or past the lock screen. Only a factory reset helps.
I'm still running stock android, no changes so far (root etc.). Had this problem with 2-3 GPads Devices before and exchanged them. But the problem still continues, so I think it's an app or settings problem.
After a factory reset I can restart normally for a while. I download my apps and change my settings. Then I don't reboot like for 1-2 weeks and get the problem again.
Before I try rebooting, I make sure I have a backup that I can restore. Had to use it today and restored. And no problem after same apps & settings from the backup. So far, but it will appear again, after a while I think.
Does anyone have a similiar problem or knows what the problem could be
Wolkenstern said:
So I got this message again after rebooting my device. It's writen in german and says something like:
"We are sorry! The Application LGSystemServer has been closed".
Does anyone have a similiar problem or knows what the problem could be
Click to expand...
Click to collapse
I have the same problem on my G-Pad. Wiped cache and dalvik, no help. Full wipe fixes the problem. I used also TWRP for full backup. Restoring the backup brings also the problem back.
Weird problem. Certainly software related.
jaan103 said:
I have the same problem on my G-Pad. Wiped cache and dalvik, no help. Full wipe fixes the problem. I used also TWRP for full backup. Restoring the backup brings also the problem back.
Weird problem. Certainly software related.
Click to expand...
Click to collapse
I have my device since Monday. I deleted some bloatware (after Root), and I had the same problem.
I found the solution in: [HOW-TO] The easiest way to unbrick your LG G Pad 8.3
It took about one hour and the problem has gone.
Good luck!
@Sylvia
Did the problem reappear after the installation? I had the problem a couple of times, appearing days after a factory reset.
Thought it was my Samsung 32GB MicroSD that was causing the problem. Because my sister had the same problem after we inserted the same microsd into her G Pad. In here case a factory reset did it and the probleme never occured again.
Right know I'm testing and writing down, every little change I do. To find the problem trigger. Maybe it is a coincidence, but I also did the "Update Recovery" with the LGMobile Tool yesterday. When the problem appeared, because I read it could help that way. It was still there after rebooting, so I did a factory reset like always. After that I tested after every major change. Did so far 18 Reboots and no problem.
I really hope that the software installed on the G Pad was causing the problem so far. To make sure, I formated the MicroSD card to exfat3 and then back to fat32 under Xubuntu-Live CD with GParted.
Another thought was with the constant writing/reading of my lecture note files every 2 min. of autosave, that are stored on the MicroSD card. And the index search every hour over the 9000 files by DropSync.
I really hope that was the solution.
Interesting coincidence
Interestingly, I have a same problem and same issue. I am using DropSync and LectureNote. Before I receive the same message, I always see a message in LectureNote saying "out of memory" or at least using LectureNote. I think it may be related with LectureNote. I am going to try with autosaving function deactivated.
If it continues, I may remove LectureNote from G Pad and observe how it goes.
Wolkenstern said:
@Sylvia
Did the problem reappear after the installation? I had the problem a couple of times, appearing days after a factory reset.
Thought it was my Samsung 32GB MicroSD that was causing the problem. Because my sister had the same problem after we inserted the same microsd into her G Pad. In here case a factory reset did it and the probleme never occured again.
Right know I'm testing and writing down, every little change I do. To find the problem trigger. Maybe it is a coincidence, but I also did the "Update Recovery" with the LGMobile Tool yesterday. When the problem appeared, because I read it could help that way. It was still there after rebooting, so I did a factory reset like always. After that I tested after every major change. Did so far 18 Reboots and no problem.
I really hope that the software installed on the G Pad was causing the problem so far. To make sure, I formated the MicroSD card to exfat3 and then back to fat32 under Xubuntu-Live CD with GParted.
Another thought was with the constant writing/reading of my lecture note files every 2 min. of autosave, that are stored on the MicroSD card. And the index search every hour over the 9000 files by DropSync.
I really hope that was the solution.
Click to expand...
Click to collapse
@namagile: Coincidence does not imply causality. The problem that you observe might surface by using LectureNotes, but this does not necessarily mean that LectureNotes is causing it.
I received a couple of similar reports, and in one case, the user sent the device logs to me. There were entries in the logs that a system service failed to start another system service, causing this error message that you see; why that tends to happen after LectureNotes usage is not clear. The user admitted that she/he deleted system software after rooting the device, which might be tempting but can lead to problems in case you delete the wrong things.
@acadoid,
I love LectureNote. I don't know/care how it happens, but every time my LG G pad crashed, LectureNote was being used and showed a strange behavior. Now, I deactivated 'auto-saving' and other options coming with a warning message "not to use if RAM is not big". We see how it goes. I hope/believe this may resolve an issue.
One tip for LectureNote. There are so many options available for a user to set -- please simplify and hide some of the options from a ordinary user like myself. It will be less intimidating to new users. Thanks.
acadoid said:
@namagile: Coincidence does not imply causality. The problem that you observe might surface by using LectureNotes, but this does not necessarily mean that LectureNotes is causing it.
I received a couple of similar reports, and in one case, the user sent the device logs to me. There were entries in the logs that a system service failed to start another system service, causing this error message that you see; why that tends to happen after LectureNotes usage is not clear. The user admitted that she/he deleted system software after rooting the device, which might be tempting but can lead to problems in case you delete the wrong things.
Click to expand...
Click to collapse
@namagile: The options are certainly not to intimidate users but to empower them. All options have meaningful default values chosen such that LectureNotes works on essentially all Android devices without touching the settings.
But this is not the topic of this thread.
Wolkenstern said:
So I got this message again after rebooting my device. It's writen in german and says something like:
"We are sorry! The Application LGSystemServer has been closed".
After the error I can't do anything. It's reappearing so fast after clicking "ok", that I can't get into the settings or past the lock screen. Only a factory reset helps.
I'm still running stock android, no changes so far (root etc.). Had this problem with 2-3 GPads Devices before and exchanged them. But the problem still continues, so I think it's an app or settings problem.
After a factory reset I can restart normally for a while. I download my apps and change my settings. Then I don't reboot like for 1-2 weeks and get the problem again.
Before I try rebooting, I make sure I have a backup that I can restore. Had to use it today and restored. And no problem after same apps & settings from the backup. So far, but it will appear again, after a while I think.
Does anyone have a similiar problem or knows what the problem could be
Click to expand...
Click to collapse
I have a 8.3 gpad and have the same problem. Now it recurred for the third time. The problem might be indeed with LectureNotes conflicting somehow with LG software. My device is NOT rooted. For the first two times I had no external SD card, now I have one. I was not using Dropsync earlier either.
I would be happy to do some testing and experimenting.
It would be good to know, if I remove or change some file somewhere, can it bring the device back to life without a factory reset?
I had the problem even before using DropSync. I reinstalled the stock rom using the LG Mobile Tool and then did a factory reset.
No problems so far. Even after installing all apps and configuring them. Then I uploaded about 500 Lecture Notes files using DropSync. Even the next day I did a reboot everything was fine.
I didn't use LectureNotes ones after the new installation. And didn't delete anything that was pre-installed (wallpapers, google apps etc.). (It was said to be a problem conflicting there)
So yesterday I used LectureNotes about 1 1/2 h non stop. Saved about 3-4 times and then closed it. Used DropSync and uploaded the new files to my Dropbox account.
Then didn't use the tablet until the next morning. I tried a normal reboot (using the Power-Off Button (Shut down and reboot), to test and BAM the usuall error message occured again.
Thank god the backup I did before was bug-free and I could flash it back.
So now I'm testing what in LectureNotes could be triggering this error after a reboot is done.
My ideas so far that I will test:
- Automatic Saving Option off
- A few different settings in the app (Triggering back to Default)
- not using DropSync for a while, to test if that was maybe a part of the problem.
- Using a different ROM, maybe the problem is just with the LG Stock rom? (But that will be the very last option I will try)
- Trying to clear cache after using LectureNotes (The Cache is never saved in my backup, so never restored back. Maybe there is sth. saved, that doesn't restart after a reboot.)
What I tested so far:
- The Problem didn't occur 2 times when I used LectureNotes < 1 h.
- The App location doesn't matter for the Problem. Had the App first time on the external SD Card (storage/externalSD/LectureNotes), then on the internal (storage/emulated/0/LectureNotes).
- Tested other apps longer than > 1 and no Problem was there.
If I could anaylse the log file, I gladly would, but I don't know how to. (Read sth. about LogCat?)
@Wolkenstern: There are several apps in Google Play and other app stores (search for `logcat´) that can read the log files. However, a better way is to connect your device via USB to a `normal´ computer and use `adb´, `logcat´ or similar tools to read the logs.
acadoid said:
@Wolkenstern: There are several apps in Google Play and other app stores (search for `logcat´) that can read the log files. However, a better way is to connect your device via USB to a `normal´ computer and use `adb´, `logcat´ or similar tools to read the logs.
Click to expand...
Click to collapse
I installed the catlog app on the tablet, because I can read it in a better ui for now.
I will try to use adb logcat with my computer, when I use LectureNotes at home. (Watched a tutorial)
Step 1: But will it also still continue writing if I reboot the devise? Critical for the error message, that keeps appearing.
Step 2: If I have the log and filter Errors and Terrible Failure, what do I do with them? I don't think I can analyse them, even though I have Java Programming Expierence, but I'm a newbie with programming android apps.
@Wolkenstern: What to look for is difficult to say, even warnings can contain important information in this case.
The advantage of the variant with USB cable is that it continues to display logs during a reboot.
@acadoid: I think I need to combine them. Because I get this little lag with my stylus (GoSmart), when it is connected with the usb.
And then I have broken letters. So I'm running the logcat while using lecture notes and then switching to the adb logcat on my computer, if I'm testing the reboot after.
LectureNote's function crashes LG G pad -- requiring Factory reset!!
Hi, I used Penutimum and Papylus before. Now I moved to LectureNote, but found a serious error. I use LG G pad 8.3, one of latest tablets. Whenever I use the function of 'cut' and 'paste' of my drawing on the note, it says 'Out of momery. Trouble ahead'. And the LG system server is down. I have to do factory reset, reinstalling everything. The tablet is otherwise working well. Acanoid, can you please help on resolving this issue? Otherwise, I wasted my money on this app as it is not usable.
I intentionally tried to confirm that LectureNote's "cut and paste" caused the crash. If this problem does not get resolved, I am going to ask for a full refund. The money is not what matters. I spent my precious tens of hours due to this critical error. I hope Acanoid team can resolve the issue.
@namagile: Which notebook page width and height do you use? Have you enabled `large page cache´ in the app's storage settings?
If you directly see an `out of memory´ message, then disable `large page cache´ in the app's storage settings, and if this option is already disabled, use a smaller notebook page width and height.
So I tested now for about 2 1/2 hours, rebooted and had the problem again.
After looking in the log after the reboot, there is always this error after the "Fatal Exception: Main" -> "03-23 23:09:23.606 E/AndroidRuntime( 1144): java.lang.RuntimeException: Unable to create service com.lge.systemservice.service.CliptrayService: java.lang.NullPointerException"
Then there is a loop etc.
That was just a quick look, I will try to look over the other one before the reboot tomorrow.
I already tried the suggested option
HI, I already tried the small page cache. It did not make any difference. I have not tried the smaller notebook page width and height, but that is a big pain. Every time I create, I have to adjust the page size. In the end, LG G Pad is a new tablet with decent specs with 2 gb ram. I don't understand that even a tablet of this specs cannot handle one app. It means that the app is not built well considering the specs of a tablet.
acadoid said:
@namagile: Which notebook page width and height do you use? Have you enabled `large page cache´ in the app's storage settings?
If you directly see an `out of memory´ message, then disable `large page cache´ in the app's storage settings, and if this option is already disabled, use a smaller notebook page width and height.
Click to expand...
Click to collapse
@Wolkenstern & namagile: The fact that the device has 2GB RAM does not mean much. LectureNotes requests what is called `large heap´ (indicating that it needs more RAM than `normal´ apps), this results usually in an upper limit of 256MB or 512MB, dependent on device. However, there are devices for which the limit is as low as 64MB, which is usually not enough for LectureNotes.
It would constitute a serve security flaw in Android if an app could crash a device. Even if an app starts to allocate memory as crazy, it will not receive any new memory once it hits the upper limit; if it does not cooperate with Android UI, it will get halted after 5 seconds; etc.
I do not own a LG G Pad and hence I cannot investigate this problem myself. The fact that you observe a null pointer exception in a LG system service (com.lge.systemservice.service.CliptrayService) suggest a severe bug in this system service.
One possibility why the problem occurs when using LectureNotes might be that LectureNotes supports Android's clipboard protocol (not many apps do that). However, even if LectureNotes was using Android's clipboard protocol wrongly (which it does not!), it should not result in a device crash, the worst scenario is that LectureNotes crashes.
acadoid said:
I do not own a LG G Pad and hence I cannot investigate this problem myself. The fact that you observe a null pointer exception in a LG system service (com.lge.systemservice.service.CliptrayService) suggest a severe bug in this system service.
One possibility why the problem occurs when using LectureNotes might be that LectureNotes supports Android's clipboard protocol (not many apps do that). However, even if LectureNotes was using Android's clipboard protocol wrongly (which it does not!), it should not result in a device crash, the worst scenario is that LectureNotes crashes.
Click to expand...
Click to collapse
Ok, if that really were the problem, than the only way to solve it, is to wait for an update from LG.
I saw a leak of the .tot file of the official V500 Stock 4.4.2 here on XDA. So maybe Kitkat is on it's way although we possibly have to wait weeks again for it.
Or to Flash another Custom Rom.
I will test a few things, with this new input. Worst Case I have to flash my backup daily, but it takes only 3 min.
The Dreaded "android.process.acore has stopped" Error: Is there a Master List of....
So I got this error withing hours of first turning on my new Galaxy Note last night, and I just figured it was because I disabled an app I shouldn't have. So I reset to factory settings, and everything was fine. Fortunately, I'd saved most of my big media to the SD card.
Today, I got the error again. This time, after wandering the Internet for a while, I was (very haltingly) able to get rid of it by clearing the "Contacts Storage" cache.
Looking online, there are apparently three apps people suggest clearing the cache for to get rid of this error. So, the logical thing to do would be to disable all three apps to prevent the error from ever popping up in the future? The three apps are:
Contacts
Contacts Storage
Downloads
I don't believe I ever make use of any of them, except maybe the Downloads app, depending on how it works. When I download something from Chrome, for example, I always use the ES Downloader w/ ES File Explorer.
So--my question is this: are these three apps safe to disable? And a related question: is there a master list somewhere of the various pre-installed apps Samsung put onto the Note 2014 that are safe to disable? With no app windows active, my note idles with 47% RAM usage which seems excessive to me, and I'd also like to minimize the chance of future errors like the android.process.acore thing.
Of course, I'm also an idiot, so it's entirely possible that the best course of action for me is to just stop talking, stop messing with apps, and just leave everything as-is.
Arsene_Lupin said:
Of course, I'm also an idiot, so it's entirely possible that the best course of action for me is to just stop talking, stop messing with apps, and just leave...
Click to expand...
Click to collapse
Yes, why not? And I will not say that you or someone else here is an idiot but I never understand this cleaning and killing. I mean like you see, your tablet becomes only instable. And there is really no lag of memory. The note has mostly 3GB which is more then most high-end phones have today and enough. And when the note use this memory then be happy because then the resources are perfectly used.
So, why removing stuff when you can't use the free space?
PS. I never got this exception and I use all 3 apps.
My understanding is that the error is caused not by the app per second, but the update process. Like the data gets corrupted somehow.
Anyway, as for why I want to do this, my understanding is that all of these pre-installed programs are constantly running in the background... which means they're consuming battery power. By disabling some , if I can, I hope to maximize battery charge.
I had that error on boot when installed gravitybox xposed module, just ignore it.
I was able to get rid of the error after several resets, but I'd still like to disable some of these background apps to improve battery and free up some ram.
I thought for sure I saw a master list thing here, somewhere, but the thread must have had some weird title or something because I haven't been able to find it again.
Arsene_Lupin said:
I was able to get rid of the error after several resets, but I'd still like to disable some of these background apps to improve battery and free up some ram.
I thought for sure I saw a master list thing here, somewhere, but the thread must have had some weird title or something because I haven't been able to find it again.
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=2514703
Sent from my Nexus 4 using Tapatalk
22sl22 said:
Here you go:
http://forum.xda-developers.com/showthread.php?t=2514703
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
That's not it. It was a list of apps that could be safely disabled via the app manager, no rooting necessary.
i have a problem where after some random event, my phone will crash and reboot and lose/corrupt some or all of its app data (ie settings of applications) and i will have to go and actually uninstall the app, reinstall and set it up again. sometimes it wont even work, for example it happened again and my viper tweaks, settings app, and htc weather settings were lost so i restored backups of the 2 former and it worked but i had to actually go in to each individual page to get the settings to actually update and set, but my htc weather will not save my settings even after a complete removal (even the copy in /system) and reinstall from the play store, any non default setting will not stick.
this has only happened 2 times, this is the first time on my 10 and it happened once before on my old m8 i was using until a few weeks ago, except i actually lost ALL of my app data and had to start from scratch because even trying to restore everything with titanium backup did not fix the errors and crashes. other than that, this has literally never happened to me once in my 8 years of using htc and android in general.
how can i possibly figure out what is going on?
daktah said:
i have a problem where after some random event, my phone will crash and reboot and lose/corrupt some or all of its app data (ie settings of applications) and i will have to go and actually uninstall the app, reinstall and set it up again. sometimes it wont even work, for example it happened again and my viper tweaks, settings app, and htc weather settings were lost so i restored backups of the 2 former and it worked but i had to actually go in to each individual page to get the settings to actually update and set, but my htc weather will not save my settings even after a complete removal (even the copy in /system) and reinstall from the play store, any non default setting will not stick.
this has only happened 2 times, this is the first time on my 10 and it happened once before on my old m8 i was using until a few weeks ago, except i actually lost ALL of my app data and had to start from scratch because even trying to restore everything with titanium backup did not fix the errors and crashes. other than that, this has literally never happened to me once in my 8 years of using htc and android in general.
how can i possibly figure out what is going on?
Click to expand...
Click to collapse
May be a Hardware (corrupted eMMc) Issue.
well after it happened i went right into twrp and made it do a check and repair on /system and /data and neither one came up with any problems. you would think if it were a corruption issue it would come up with bad blocks, even if its on a hardware level.