I can’t post this in the original thread because one needs 10 posts to participate in the development related sections of the forum. So I have to report my problem here.
I'm currently running the jan31 build of CM and have had the Sleep of Death with every build of this ROM, especially reproducable when the phone has been on the charger for several hours. It justs sits there, the notification LED works, but it can’t be waked up. I have to press the power button for 15 or so seconds to forcibly reboot the device.
Even the "Wake my Android Pro" app on default values (wake up every 29 minutes) wasn’t able to fix this. I can fully prevent the SoD using the "Wake Lock" app and setting PARTAL_WAKE_LOCK, however this drains the battery massively.
I have done a full wipe before switching from stock to CM and did another full wipe before going to the jan31 build, however the problem persists.
Nobody else in the main thread seems to be affected by this problem.
This is on a German Moto G XT1032.
Any ideas?
Does nobody have an idea, or can forward this to the developer via the official thread?
Hi Guys, I need your inputs;
here are the intermittent problems I am experiencing.... this is both on custom rom and stock rom
1. apps crashing
2. play store closing
3. device restarts itself
4. prompts in the screen that a process has stopped / closed
5. opening some app restarts the device
6. device Freezing up
7. UI Freezing up
8. RANDOM REBOOTS
play store issues:
- app not signed
- error 960
Is there any complete hardware diagnostics I can use? I have used like 5 custom rom and the problem never goes away.
aside from these; I also need your ideas,
Battery power seems to be decent.
anyone can share experience and tips?
anyone?
anyone have ideas?
guys, need inputs
need inputs guys
Greetings;
I don't know if you've solved your problem...
But for what i read you didn't even performed a search. Most likely the Same reason why no one answered to you all this time...
What is your Device Manufaturer and Model?
Hi there,
My First post on the forum. First of all a big hand for all the developers.
I’ve installed [ROM][KK][4.4.4][KTU84Q] CyanogenMod 11.0 (20140910-UNOFFICIAL) on my Samsung Galaxy Wonder i8150. Everything works perfect accept the application Viber. This app causes a freeze at the lock screen (or at the home screen when I’m quick enough with entering my sim lock code.
After the first reboot following the first installation of this the screen freezes completely. Can’t do anything, the phone reboots after a little while and goes into a loop
I’ve done several reinstalls of the ROM. The freeze only appears after installing this specific app.
I’m a new users so unfortunately I’m not permitted to post to the development-related forums.
I can’t imagine that I’m the only one who is using this app. Is anybody else experiencing this problem
TIA
Prior to 5.1.1, every time the phone was idle for a short period of time the lock screen would appear and, when I was home, SmartLock left it unlocked, most of the time, but it always appeared. Since upgrading to 5.1.1, the lock screen rarely appears anymore and, when I’m away from home, since the lock screen rarely appears anymore, my phone is often unlocked and unlocked without a lock screen and having my phone unlocked is a big security issue . I don’t know if this is related to 5.1.1 or, perhaps, a recent Google Play Services update (since Google Play Services is responsible for so many things nowadays, I assume it’s suspect).
Anyone else have this issue/know of a possible fix? Thanks.
Bump. Is no one else having this issue? The lock screen for everyone works perfectly on 5.1.1?
Yes, since 2 weeks ago. Any solution?
None that I know of—I still have the problem.
Just chiming in to say this issue appears to be largely resolved since Android 6.0.
BinkXDA said:
Just chiming in to say this issue appears to be largely resolved since Android 6.0.
Click to expand...
Click to collapse
Resolved? Apparently not that largely. Such issue started 24 hours ago on my 6.0.1 device. Unable to lock screen despite pattern (or whatever chosen) is correctly set. No "smart lock" option is used, BTW; Though lock screen often appears but only when shutting down and restart the phone, not by rebooting it. Looked exhaustively for a common fix, but everyone suggests the same old, clear caches, credentials and device administrator thing.That is NOT working here. Safe mode says nothing's wrong with apps causing the flaw either. Yes, I'm rooted, on Xposed and all that stuff, as always. Probably it is related somehow; however, issue has never ever showed on any other device I had, and I had two previous on 6.0.1 as well. If anyone has a different hint on the subject, well it'll be well appreciated.
Sent from my Moto G4 Plus using XDA Labs
Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.