Database Users

Partial Freeze, details included. Please assist.

Hi,
I'm using the ESSential ROMs. Got an ELFin. got plenty of free memoty.
Doing any of the following actions might cause the phone to freeze partially: accessing contacts, replying to sms, trying to initiate a call.
Partially means that I'd still be able to acess "programs" and run most programs, then exit then rerun etc. However the "background" will not update. At this stage it's not possible to access contacts/message/call. At some point though, it might all get stuck. To remove the partial freeze, I have to soft reset twice. Once is never enough. Removing the battery/power off is basically the same.
Once it's partially frozen, task manager will not work properly and will freeze at about 20% before calculating the full CPU utilization.
Thanks for any help!

oo no replies. Is there anything else which I could add to assist you in providing some ideas? Thanks.

Why do not you make hard reset?
If it does not work out, change the ROM.

I have, the problem still persists after two ROM changes. I was hoping someone encountered a similar problem and managed to solve it...

Well I changed the ROM to Onyx and it works OK now

CAB request!

Can somebody with the know how make a little program which litterally only performs one task: kills the process services.exe.
The reason for this is it is the cause of many soft resets in a day. Sometimes not even fixing the slowdown anyway and causing the famous black screen of death.
But as soon as i go to sktools and use the processes tool and kill the process phone goes back to being how it should! However because the phone goes into major slowdown it takes ages for the sktools processes program to load and then hard to select services from the list because of the lagging etc so it would be nice just to have a link that i could put on my quick links and when phone goes to melt down just press this magic button which saves the phone being hurled at a wall!
It needs to be called Meltdown Override or something!
This is a serious request as it would make HD2 use a much more pleasant experience!
Many thanks

This is pretty easy to do AFAIK...
If nobody else does it, I can do it when I have some more free time ...

I would appreciate this so much!
I think I may even use AEB to assign it to a long press of the back key or something

But, does services.exe auto-starts again? Because you could have some problems if you kill it and don't start it again...

Yer it does straight away but not running at 90% + CPU.

I find it unlikely that services.exe is really the culprit here, but rather a service installed on your phone that is misbehaving. If you find out which service is causing the problem, and then uninstall or disable it....
curing the disease, rather than treating the symptoms.

X1-owner said:
I find it unlikely that services.exe is really the culprit here, but rather a service installed on your phone that is misbehaving. If you find out which service is causing the problem, and then uninstall or disable it....
curing the disease, rather than treating the symptoms.
Click to expand...
Click to collapse
This guy is right...

Ive only just installed a new ROM voda UK 1.72 so I have next to no programs installed at the moment so I don't see what could cause it.
The main time this happens is when left charging over night and when you go to use it in the morning it's completely screwed. Soft reset doesnt fix it it just goes to black screen of death so then u have to take the battery cover off and reset again. The only thing i have found to get it to a useable state again is to kill process services.exe, and then its fine again. Once by doing that it stopped weather update and text messaging from working but atleast when i then did a soft reset things where still fine and those two things worked again and no laggy phone.
I kno it seems stupid to just kill a process and not find the problem but i cant see what the problem could be considering how recently i hard reset the phone (which i did 3 times in total to see if it got rid of the problem).

Just forget that ROM and go back to a working one? Seems easy to me... don't always need to have the latest or highest version number, just something that works... If 1.72 doesn't work for you, don't use it!

I would if it wasn't for the fact that after doing the annoying procedure in the morning of killing process "services.exe" then soft reseting, it runs the quickest i have ever been able to use the device on any ROM before it

You know that services.exe is one of the main parts of your phone-funcionality (calls, sms, etc.)?
As you said you experience it in most cases in the morning... Have u got GAlarm installed?
If yes --> Did you check the RegKey MidnightWakeup=True and change it to false?
My Girlfriends TD2 had the same issue. CPU usage by services.exe was often around 70-90% until i applied this change...

Services.exe is just like svchost on a windows-machine, it just hosts a bunch of services. So most likely its a service that has gone crazy.

Unable to wake - have to pull battery

Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these

bryon13 said:
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
Click to expand...
Click to collapse
Are you running setcpu? Mine was doing this when I would lower the speed with a screen off profile. I just uninstalled setcpu for now. I don't think the kernel supports it anyway.
Sent from my SGH-T959 using XDA App

No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App

bryon13 said:
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
let us know how it goes... If you experienced any unable to wakes after the reset...

Seems to be working fine. I'm not sure what the problem WAS, but the reset seems to have fixed it.
Root and busybox were still intact. Had to re-do the lag fix. (Method 1)
I'll update if I get the issue again.
My phone is just so...VIBRANT

Samething happened to me yesterday morning. Woke up found my phone wouldn't go back up. I thought it was dead, until I pulled the battery. I haven't Root hack it or installed SetCPU.
Sorry to throw this issue in this topic, but anyone have any problem with the phone rotating sideway for WEB and Messaging? I thought when I first got it, it worked.. now it doesnt..

There is probably a common app here or something causing this because I don't ever recall hearing this type of issue with the Vibrant before this thread.

I had the same thing happen to me and found after much trial and error that when I pulled my SD card out I was then able to wake the phone up. Apparently there was some problem with my SD (I was using it with my previous phone..MT3G) that was causing the Media scanning process to get stuck.
I ended up backing up what I needed from the SD and reformatting it. Since then I haven't had any issues. We may or amy not have the same root cause but hopefully this does help.

I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT

bryon13 said:
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
I am almost 100% SETCPU is the problem..
My phone would not come out of sleep.. I had to pull the battery and when I turned it on it would say "auto update of time and date".. That made me think the phone lost its internal battery and the phone was bad..
It started doing it right after I configured SETCPU... I installed the program last Thursday but never clicked on it.. I set it for on demand and that is when it started not coming out of sleep..
So I removed SETCPU and it still would not come out of sleep..
So I did a wipe all user data and it started working fine.. I installed SETCPU and it was still working fine.. I setup SETCPU for performance and it started messing up again and not coming out of sleep..
So, I wiped all user data again last night and it has been working perfectly since.. So I do not plan on reinstalling SETCPU...

[Active Notification] Sometimes It Doesn't Work At All

Today I've the problem again, the notification simply doesn't work, it looks like the sensor is failing or something because I took it out of the pocket, as usual, and it doesn't light on... having to use the power button again...
It happened other time, some weeks after I bought it... complaining with the technical support on Moto Care, without results, so I've factory reset and wipe everything, and it works...
So, my first guess is that the cache of Active Notification may have some guilty on that, but I can't find the app from it to clean and check if it works. Does anyone knows what app is it?
I'm not gonna to factory reset this time, it simply not useful as a solution.
Does anyone have/had this problem?
Regards,

It happened to be one time. I found the solution to be simply disabling Active Notifications and then re-enabling it.

Julianocas said:
It happened other time, some weeks after I bought it... complaining with the technical support on Moto Care, without results, so I've factory reset and wipe everything, and it works...
Click to expand...
Click to collapse
If a factory reset fixes it, it's probably not a sensor issue. It's possible that an app you've installed is interfering with it somehow - do you have any kind of root apps, or apps that play with system resources (like process managers/Greenify/etc.), or apps that control notifications?

I've noticed this on 4.4 a few times, as well as the lag on unlocking from AN a few times, too. Then again, I'm still on the leak, so that may have something to do with it.

Case maybe? Make sure the screen is clean. That proximity sensor is sensitive.

I think I found the problem.
The app management of what will show on active notification... don't active any of those that did not come checked after a reset. I did check some "Google's" for active notification.

Finding Cause for Sleep of Death (SOD)

6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.

I use gravity box but not greenify. I use Recently instead of greenify with no problems. Not sure what Amplify is but I use the XML hack to raise headphone volume. Hope this helps.

RRuszczyk said:
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
Click to expand...
Click to collapse
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.

blitzkriegger said:
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
Click to expand...
Click to collapse
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.

RRuszczyk said:
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
Click to expand...
Click to collapse
Then try to capture a system-wide log instead. This article may help. Do the logcat after you have experienced the bug. I'm sure it will point out what's causing the issue.
Other than taking the logcat approach you can try eliminating possible culprits. If you suspect it may either be amplify or gb then temporarily disable each module within xposed then observe if the problem persists.