So I thought this would be helpful because I spent so much time searching and was not able to find an answer. I will post it here to help others who thought their Note 3 was DOA.
Symptoms:
> Upon installation of an app (seemingly random, until several factory resets later I realized it was the same apps for me) it is greyed out and shows sd card symbol
> Trying to launch app would seize up the device and just black screen and force close
> Regardless of factory reset and uninstalling/reinstalling apps, they suffered same issues (other apps were fine)
> Would periodically see the following message:
"Prevention Information. An application has been forced to stop for an unauthorised attempt to access system on your device. It may be safe to delete an application obtained from an unauthorised route. Check now?"
*NOTE: all apps that I was having issues with were via Playstore, not a side loaded one.
Solution:
> After some research and going on a hunch, I finally fixed it by doing the following:
Factory Data Reset
Unchecked 'Verify Apps' option under Settings > General > Security
Dragging KNOX Shortcut to Disable option in app drawer (click and hold icon in app drawer and "Disable" appears on top)
Cleared Data on LookOut Security and re-entered logins
Removed those problematic apps and then reinstalled them
After reinstalling the very same apps giving me issues this whole time, they are now working perfectly. Please note I tried everything under the sun including 2 factory resets and reinstalling/installing from Wifi/Data and nothing worked. It was not a simple parse error or a simple install to sd versus install to device issue. It would happen by default and was not being corrected by any other method than this above. This is what worked for me and it finally solved my issue. I've been seeing a lot of buggy stuff with this Note 3 versus my Note 2 and I feel it's some of this extra crap that Samsung put in the Note 3. I know KNOX is supposed to be great for security, but it will mean nothing if it makes my device lose simple functionality of some apps.
If this helped anyone, feel free to thanks.
Cheers,
So quick update, the issue returned. I think I narrowed it down to a bad sdcard. I didn't think that would attribute to the app issues because I never explicitly installed to sdcard. But it seems at some point the phone tried to store the apps in question on the sd card automatically and that's when they failed. Anyone know if there is an auto apps to sd process on note 3?
Sent from my SM-N900T using Tapatalk
I noticed my Sam's Club app was an icon of a grayed out SD card also.
Sent from my SM-N900T using Tapatalk
So far after removing my bad sdcard last night I haven't had the strange issue anymore. Actually a lot of the weird things that was happening have seem to subside. *Crosses fingers* hopefully this was my issue the whole time.
Sent from my SM-N900T using Tapatalk
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.
Hi, has anyone come across this issue since the update to Pie? If I log on to any banking app, I get "Fingerprint change detected" and I then have to enter my password for that app. Tried a factory reset, same. After a factory reset, fingerprint works ok for a few hours then the problem returns. I've used Odin to downgrade to Oreo, problem no longer exists! I love Pie but this fingerprint issue is a nightmare because I use Lastpass, which also tells me my fingerprint changed and I need to enter my master password.
Yep, happened with my banking app and my credit card app
Lasts longer than a few hours though, currently had it working for a couple weeks without it bugging out
*Detection* said:
Yep, happened with my banking app and my credit card app
Lasts longer than a few hours though, currently had it working for a couple weeks without it bugging out
Click to expand...
Click to collapse
Thanks for confirming it's an issue and not just my phone. Very annoying.
houstie said:
Thanks for confirming it's an issue and not just my phone. Very annoying.
Click to expand...
Click to collapse
Yea I started wondering if someone knew my PIN and was adding their own fingerprint to my phone, but tested each print and they were all still set to my own
I could be wrong but I don't believe it's a bug. When I flashed Pie initially I did a clean setup and of course had to register my fingerprint on the phone. From there I continued setting up apps and set them to login using fingerprint. Later I added a second fingerprint to unlock my phone and those apps reverted back to password unlock because of the addition. Once you log in using the password you should be able to go into the app settings and turn on fingerprint login again.
m1batt1 said:
I could be wrong but I don't believe it's a bug. When I flashed Pie initially I did a clean setup and of course had to register my fingerprint on the phone. From there I continued setting up apps and set them to login using fingerprint. Later I added a second fingerprint to unlock my phone and those apps reverted back to password unlock because of the addition. Once you log in using the password you should be able to go into the app settings and turn on fingerprint login again.
Click to expand...
Click to collapse
Yea the bug is when you have not added any more fingerprints, and it says you have
Any fix for this.?
This is a huge bug / issue for me.
Any 3rd party app that uses fingerprint detects a change even though I have not made any changes.
I have even factory reset my device and it was working fine for about 2 days then today it started happening again.