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.
Hello everybody,
got this mobile a few months ago, latest Android officially available release, only thing I did was rooting and adding some software, I use it as a second device mostly to check email and online services, I use my other smartphone as a phone and for calendars, phonebook and notes.
I noticed that the device all of a sudden restarts without me doing anything, my son (who uses Android since longer than me but who doesn't really know much about it...) said it could be the heat (it's always in the shade) or too many options on (wi-fi in primis) but I checked and there are just a few apps running (mail, phone, phonebook, sometimes Instagram), what can I check to find how does it restart without any notice or action from me?
Thank you
soory
I had an issue where my Note 2 would randomly reboot, I also had an issue where my power button was dodgy.
What it ended up being was the ribbon for the power button, got this replaced, and this fixed my dodgy power button issue, as well as the random reboots.
I paid to get this done in a shop, but it seems you can do this yourself.
Sorry i can't post links - hope this makes sense
youtube com/watch?v=T5zPvP4btDA
Of course, your problem might be different
Giuann said:
Hello everybody,
got this mobile a few months ago, latest Android officially available release, only thing I did was rooting and adding some software, I use it as a second device mostly to check email and online services, I use my other smartphone as a phone and for calendars, phonebook and notes.
I noticed that the device all of a sudden restarts without me doing anything, my son (who uses Android since longer than me but who doesn't really know much about it...) said it could be the heat (it's always in the shade) or too many options on (wi-fi in primis) but I checked and there are just a few apps running (mail, phone, phonebook, sometimes Instagram), what can I check to find how does it restart without any notice or action from me?
Thank you
Click to expand...
Click to collapse
Dear Giuann
What you are experiencing is know as SOD (silence of death) on our Android World
If your phone is rooted and you have custom Kernel then it would be due to the kernel... change your kernel to stock or a more stable one as per your device.
If you have a stock kernel... then clean your cache.. etc.. or better reflash stock ROM...
alternately use Betterbattary stats to identify if you have any rogue application which is causing issues...
I have experience this issue when I did rooting.. re root it with the correct method....
I did only root it as to install software I download from the internet, everything is as it originally was, ROM is the stock one.
Which are the steps to perform to clean the cache and to check if some app is making the OS crash?
Thank you
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Helhound0 said:
Hi!.
I've been having this annoying problem with Galaxy Wearable app for the last three days where the app crashes on launch every time. I've been trying to fix it all this time and i have tried different remedies that didn't help at all. I haven't the slightest clue what's wrong and i don't know where to ask for help so i figured i ask for it here first. I'll post a logcat if anyone is willing to help.
Here's what i've tried so far:
1. Cleared cache - Didn't fix the issue
2. Cleared storage - Didn't fix the issue
3. Complete reinstall of the Wearable app and services - Didn't fix the issue
4. Removed the Samsung account - Didn't fix the issue
5. Resetting the watch and setting it back up again - Didn't fix the issue
6. Tried 3 and 5 together - Didn't fix the issue
7. Did a clean install of ROM (Havoc 2.8) - Fixed the issue but it came back in about an hour
9. Rolled back to the previous build of Havoc (2.7) - Same as above, problem came back after some time
10. Dirty flashed 2.8 - Same
11. Restored to 2.8 and uninstalled a bunch of apps that i thought might be clashing with the Wearable app - Didn't fix the issue
ANY help would be much appreciated. I'm starting to think something is wrong with the watch itself.
EDIT: Never mind, i found what's going on. It's Samsung Pay that's making the app crash. I uninstalled it on a whim and now it works!!! Mods, kindly delete this thread.
Click to expand...
Click to collapse
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
oxygenes said:
How much memory your phone got? Try to close all other apps and then try. I have the same behave with other apps on my Moto phone.
Click to expand...
Click to collapse
I got 3 gigs and not even half of it being used at idle. And i don't really do memory intensive stuff on my phone anyway. The issue was definitely Samsung Pay. if anyone has this issue where you're running Pie and are rooted with any version of magisk, uninstall Pay. It's been a few days and i haven't had this issue repeat even once.
shmaque said:
Yep had the same exact problem the other day after upgrading to Android 10. There's another thread in here where I found the same issue (it's throwing a java ClassNotFound exception on mine). It's especially nefarious because they sideload the pay plugin so you won't see it if you're uninstalling via the play store, and it's not sorted alphabetically with the other Samsung apps so you might not even see it if you're searching manually.
I say nefarious because depending on how bad the crash is (background task vs UI), they may not be able to even push an automatic fix since they're not using the play store. Seems like a pretty terrible approach to me.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I just uninstalled Pay from the app list in settings and rebooted. If there is a sneaky sideloaded plugin somewhere, it doesn't seem to be interfering with the Wearables app anymore.
And I guess you're right about this being a terrible approach. But Pay isn't even supported where i currently live so my question is WHY even sideload it on a device being used in an unsupported region... Such a waste of resources.
I've updated with OTA stable update and it's seemed to mess things up. Now I can't attach attachments in any app, open dual apps, it comes up with complete action using and it's blank. It seems to make the phone useless now.
Even when trying to send things it doesn't want to attach it
I too have big problems after updating to Android 11 on the Global Mi10T Pro., but it's version 12.1.1.xxx for me.
Apps like GMail, Maps etc work ok. Many others like Chrome, Brave etc just hang. Gestures no longer work. Settings is unreliable.
PC Suite won't connect - it says I need to update my device.
I wonder whether I have to try a Factory Reset - but that's a pain with no proper backup of all the apps and their state.
EEA version 12.1.2.0 - CRAP!!!
@madnlooney: enable MIUI optimizations in developer options and you will solve problems.
My bugs: at once part of touchscreen where green phone is (for answering calls) just stops working. And it is not working in any app, in screen test app.... until reboot. And it happens randomly... I think this will be my last xiaomi device. I had mi max 3 for over 2 years without resets and stuff, worked like a charm (eu rom). I broke screen (waiting new screen atm).
additional problem (happened on previous versions): mobile data just stop working. I have to turn it off and than on again. I am using both SIM slots (private+work).
Now i have big problem with this since i am on a business trip outside my country and I have problems with phone (and factory reset is out of options, since I have AND USE bank app (among others - work apps), so no go). When I return I will ditch it and buy other brand...
This phone had problems on Android 10 and has problems now too. between mi max3 and this i had poco x3nfc and had problems with it too - I think xiaomi cant keep up with huge amount of models that puts to market.
has anyone maybe some solution to my problems?
cickvoa said:
has anyone maybe some solution to my problems?
Click to expand...
Click to collapse
Custom roms. Most of the apps will work out of the box if you don't root your device. Few of the banking apps that don't work can be solved with magiskhide...
Thanks, bit as I mentioned, not possible ATM, I cant open bootloader and I dont have access to bank, since i am >1500km out of my country.
Considering that is 2021, it looks like i am ditching xiaomi (after 7 years).
cickvoa said:
EEA version 12.1.2.0 - CRAP!!!
@madnlooney: enable MIUI optimizations in developer options and you will solve problems.
Click to expand...
Click to collapse
That worked. I did have that switched off. I think for split APK install
on my side.. i have few problems with apps.. basically when i press the app button they open for 2-4 seconds the close.. no errors or something. they just randomly close..
miui optimasation is on.
kismetmookz said:
on my side.. i have few problems with apps.. basically when i press the app button they open for 2-4 seconds the close.. no errors or something. they just randomly close..
miui optimasation is on.
Click to expand...
Click to collapse
Update android webview in play store, whole internet talks about that today...
madnlooney said:
That worked. I did have that switched off. I think for split APK install
Click to expand...
Click to collapse
If we enable that, how to install split apk files? is there a solution for that too?
dual apps are miui thing, nothing to do with miui optimization
Well, EEA version 12.1.2.0 - is CRAP indeed!!!
It has been a childish attempt like: Hurray we are on android 11 too...!!!
First, they have not checked the main feature of a phone... To make and end Phone calls....
The "end" button does not respond sometimes. Randomly.
I've seen this reported in several discussions and no response from support.
Second, after the update to 12.1.2.0 SECOND SPACE broke..!!
The option to add and remove files disappeared.
A bad surprise, as the only option given, for the data you had saved in second space is to DELETE..
The import export option for files just vanished.
We can only hope that Miui 12.5 will make the Mi 10t Pro a descent Phone as it is an excellent hardware.
What I hate with this v12 is, (not sure if it was same with the previous ones) to be forced to use the mi search. If someone knows how to revert it back to Google search, will be greatly appreciated.
And if any Xioami staff or responsible seeing this message, i need to tell this. ’I don't have to use your crappy search *hit, and noone can force me to do something for a device I paid for. You have all the stupid ’features' and ads in a single thing. And the recommendations, ohh, will make me vomit...
Before you recommend me what to search for, let me recommend you something first. Go and learn why Google is doing the best with keeping the apps pure and simple. When I want to search for the best wines to drink for dinner, you're forcing me to see the turtle copulation video. What a smart software.
As I said before, if someone can help me to delete this useless app to the ground, will appreciate a lot.