Related
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
lonehunter65 said:
So I just installed the Holics Rom yesterday and I love it! The only problem seems to be that it crashes very often. I've had to battery-pull it probably 8-10 times in the past 24 hours. It seems to happen most often when I lock the screen and then try to open it up quickly. Any one else run into this problem? Or could this be a problem with the AOSP locksreen?
Also, side question about the AOSP ICS lockscreen, is it customizable with widgets and shortcuts? It is beautiful, but I may switch back if I can't add shortcuts or get my music to pop up while locked.
Click to expand...
Click to collapse
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Miniloaf said:
Yes, I've been getting this issue on Holics pretty often during screen wake-up. I'm running 1.2 but had the same issue on 1.0 and 1.1. It will occasionally freeze when waking up with the power button. It also freezes when the screen attempts to turn back on after a call. It's very frustrating, bucause it's a very good rom, but this issue is driving me crazy.
I may have also had this issue on my stock rom with faux123 kernel. Maybe the Faux123 code is to blame. My lock screen is the ring by the way, so I don't think it's the AOSP lockscreen.
The phone never freezes randomly, it's always when the screen is waking up / trying to wake up. I have a feeling it may have to do with the single core 192 UC from the faux rom, unless the holics rom did away with that.
Click to expand...
Click to collapse
Do you know if devs are aware of this problem or working on it at all?
That's the only reason why I switched to DeSensed. It got annoying after a while.
I have been using 1.2 since it came out, and I have not experienced any random reboots or issues. I am using his kernel and am S-ON.
Sent from my HTC PH39100 using xda premium
I'm s-on and I've flashed with wcx recovery. Ive tried different methods of flashing the boot.img. Flashing it before and flashing the sd card copy afterward. I have also tried flashing either before or after. I did not select any UV. I chose the nonsense version of the install and am running apex launcher pro. I selected vram during install and disabled s2w. My CPU range is 384-1512 on setCPU, I am not running any profiles. I do use juicedefender ultimate and avast full time. I also have adaway installed. I can post a list of my other installed apps too if that would be relevant. Does any of this raise a red flag? Would the sense version of the Rom be more stable? Can anyone recommend another kernel if you believe that may be an issue? Any help would be appreciated as I do not have enough posts to state this problem in the dev forum.
Not sure what is going on. I experienced it on stock rom, and I'm also experiencing it on Android Revolution HD Rom.
It seems like whenever the phone is tasked by an app opening or closing, I experience a random reboot.
Anyone know whats causing it?
Yeap me too, but only after closing final fantasy IV.. Dunno what's the deal here
°° no rest for the wiCKed °°
anyone?
S_Dot said:
anyone?
Click to expand...
Click to collapse
Me, too, but I didn't catch any regularity, yet.
I am on stock ROM.
One time a had a crash report from htc, but most times I only realize it, because I have to re-enter my pin.
Today I realised, that long-pressing the power-button does restart the phone without any other input.
Maybe it's that?
I'm using developer edition and have been suffered from heavily random reboot.
The phone rarely rebooted (2 or 3 times) while I was using it but just kept rebooting if I left it idle (5 reboots in 20 mins). I cannot reproduce the reboot because it was so random. One day, it just kept me annoying by rebooting itself more than a dozen time. The other day it just went super smooth and stable. This reboot has been happening on both completely stock and custom (Rom, kernel).
Anyone got a clue?
If you know a certain action is causing the reboot get a logcat, there's an app called catlog on the play store. Press record, repeat the action, after it reboots get the logcat and post it here
Sent from my Tricked out HTC One
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Sylpher said:
Same issue here! I'm using TrickDroid though. Has anyone tried this with 4.2.2 to see if it still happens?
Click to expand...
Click to collapse
I'm using Android Revolution ROM on 4.2.2., same thing. It happens once in a blue moon, and it's only on wake when I hit the power button. The whole phone freezes and reboots.
Is everyone here on the Developer's Edition?
I'm having the same issue, dev edition stock except recovery, and root. Some days it reboots, other days its fine. Not exactly sure whats up w/ that
Sent from my HTC One
I'm gonna go ahead and bump this, seeing as I'm facing the same issue on my 2 day old device.
At first I thought it was a problem with 4.1.2, but even after upgrading to 4.2.2 the issue is still there.
ViperOne 2.1.0 the same trouble
Hello,
I confirm the same problem on ViperOne ROM. I have tried out ElementalX 3.4 and Bulletproof kernels. But it seems to be kernel independent.
I attached the log, my configuration is as described in my signature except that I use Bulletproof kernel right now.
It is quite frustrating cause I just wanted to play a movie on my TV using Hama MHL cable, but everytime I connect my phone to the adapter the phone reboots, then it gets stuck on HTC logo, then I have to reboot it manually holding power button. I am also experiencing a reboot right after phone boots up.
This is such a serious issue that I am thinking of going back to stock kernel, but I am not sure if it will help
Any hints?
EDIT: I just installed stock kernel, but still the same, really does not seem to be a problem of the kernel
EDIT2: still trying to find the out whats the problem, I did a clean reinstallation of everything, even w/o using Titanium Backup, well, MHL still causes reboots
Since I got the Fire about 1.5 months ago, music apps have never worked flawlessly on this tablet. The system will randomly freeze, music will loop the past half second for about 20 seconds and reboot. It has occurred on stock, CM, and Slim roms so it is not specific to Amazon's terrible FireOS. What I have learned is that the tablet will never crash if the screen is on, only when the screen is off. It seems to happen only after a period of time (variable between 2 minutes to 30 minutes) of the screen being off. It also seems related to battery usage since I also never noticed crashing when the tablet is plugged in. I have been able to increase the time between crashes significantly in the past by installing the music player as a system app so it could also be a problem with cache/permissions. I have tried full wipes so I don't think its an issue with dirty flashing. Anyone else encountering this issue?
Can anyone direct me to a guide on troubleshooting a kernel crash? (Logging it) I assume that's what is going on here. I tried looking for the /proc/last_kmsg but it doesn't exist.
Anyone? Tablet still constantly crashing despite trying various roms after factory reset and full wipe.
I played with the kernel adiutor to prevent low memory killing which fixed the problem, but now the tablet becomes unresponsive with chrome open. Seems like it only has enough memory to run one or two apps at a time (chrome being so intensive). For the cause of the crash, I believe it was related to Spotify being killed by android memory manager and somehow it crashed the kernel when trying to kill Spotify with the screen off.
Same issue here, I messed around with the kernel settings trying to find a solution. I believe the issue is caused by the hotplug governor turning off CPU cores while the screen is off with the music app, somehow this is causing the CPU to lock up. In Kernel Adiutor, go to CPU > CPU Governor Tunables and change 'is_cpu_hotplug_disable' from 0 to 1 and set it to apply on boot. So far this has worked for me.
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
SpGG said:
Hi there,
I have a C6903 with 16GB of storage. Baseband 8974-AAAAANAZQ-10270045-39. It ran fine under CM12.1 from last year. I recently updated to a CM12.1 nightly from August of this year. After that I started having problems with random crashes.
The phone would either freeze during operating, not responding to any input. I had to hard reset by holding the power button for a long time. This shuts the phone down. Then I start it and it boots up. Or the crash happens, when I am not using the phone, resulting in a black screen and an unresponsive phone. The fix is the same, shutting the phone down with a long press on the power button and then starting it up.
I switched from CM12.1 to AOSP Jaguar LP 5.1.1 from August (I haven't updated to September yet). I was crash free for three weeks, but now I am back with the same crashes. I found four crash logs in /data/anr, but I can't make much sense of them. I have them attached to the post.
The change in behavior when I install a new rom makes me think this could be software related, but getting the same crashes with two very different roms makes it look like a hardware issue.
What do you guys think? I don't want to go back to stock for testing, because I value privacy a lot and XPrivacy is so much work to set up right, IMHO. I like the privacy managers included with Jaguar or CM12.1 a lot. They are so much easier to use. But if I have to, I will go back to stock. Any other ideas? Can anyone interpret the crash logs? Is there anything useful there? Should I test something else?
Please help. Thank you for reading this post.
Click to expand...
Click to collapse
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
optimumpro said:
Your attachments show only general info about OS, but nothing related to freezing/crashes. Based on the fact that you were problem free on Jaguar for about 3 weeks, you might have the following:
You installed an app or mode that's causing this; you might have set up something in Kernel Adiutor (such as cpu voltage or what have you) that's causing problems; you might have restricted something in wakeblocker or an app like Xprivacy or any other Xposed module. Just think of what you did at the end of the 3-week-period. In Kernel Adiutor, untick apply on boot and reboot, so that default values could be loaded. If that doesn't help, disable wakeblocker...
Click to expand...
Click to collapse
I didn't change anything. Same thing when I went for a new nightly of cm12.1 I did nothing out of the ordinary. Since I did not have new problems since the above mentioned, I didn't delve any further. Today I had another, interesting issue. No one was able to call the phone and I wasn't able to call out, even though the network showed up as fine with full bars. This lasted for several hours. I went into flight mode and back out of flight mode and the issue was fixed. Several SMS arrived about calls missed. And again, I have no idea if this was caused by the hardware, an issue with the software or even the network.
And that is the frustrating thing: How can I find out who the culprit is? Are there good system crash diagnostic tools? Because so far I haven't seen anything.
Hi all, lurker here.
I've been having an issue with my OP3T that hasn't really phased me until now. From time to time my phone would lock up and crash (phone shuts down unexpectedly). I would have to manually reboot the phone by holding the power down button.
I am running on OOS Beta 10, rooted with Magisk 13, EX Kernel and whatnot. This has happened prior to being on beta channel and root as well. I've read somewhere that this is a hardware issue that arises from SD821 clocking up to max Freq which causes the crash but I think even with the custom kernel and underclocking I am still experiencing lock ups.
If there is a log I can provide for you guys I can post it, just don't know which one.
Thanks.
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch ?
pitrus- said:
I too was experiencing lockups and reboots, turned out to be caused by Substratum theme engine, removed it and now phone works like a watch
Click to expand...
Click to collapse
I don't have Substratum installed
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
shivagajavelli said:
Yes , am also facing similar issue...
I am getting a blank black screen.,that confusing me that it get locked up or does it switched off...
I think the problem is in beta system updates....
Click to expand...
Click to collapse
Damnn, i've got the same problem.. blank screen with white light notif then off, when 3T not get random shutdown they give me random restart every 2-3mins, aarrgggghhh really annoying!
same problem with my devices
And then whats the solution for these problem? Arrggghhh
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
Anyway which kernel?
I have the same with stock and beta OOS, stock and bluspark kernel. Never rooted. I though that maybe i just press power button in my pocket but then it happend on the desk as well.
Similar issue, sometimes black screen with unresponsive buttons (they do vibrate), sometimes I can unlock it via fingerprint to the home screen but touch is unresponsive, only appswitch via recents button works but can't exit the app with home button, sometimes it just reboots.
Never had these issues from dirty flashing from open betas but now when I started clean these things began lol. Seems more laggy too.
dhuynh94 said:
I've tried wiping system and reflashing OOS, with custom kernel and root. The problem hasn't come up (yet) so try that maybe.
Click to expand...
Click to collapse
I just clean flashed all stock, pure without UBL, root but still same. Then tried to UBL, MAGISK + Franco Kernel, and still the same condition...
Ahhh i hate this phone! Really sucks
Hmm yeah I've had another crash but this just happened during boot.
Still have no idea what the possible cause is. Not aure why it's just us few that are experiencing this.
Maybe faulty hardware? Who knows
I used to have this problem when running the open betas for the 3t, I moved over to RR and there hasn't been any problems especially after the latest update
Edit. Also when turning on the phone the bootanimation (the two dots spinning around the thingy) it would freeze constantly, also fixed after moving to RR
My phone was crashed few times when using cameraMX application. I do not know reason, maybe last update fault? I have simple question, why we have beta version? Where is stable
Yeh I've had it freeze on multiple accounts while booting up. It would crash while the two dots are spinning and would need a hard reset.
Many times it would crash when entering my PIN for smart lock or lock screen as well..
Issue seems to have popped up again., after flashing OOS OB 14.
Most frequent symptom is after entering pin or unlocking device, at random times it would lock up Android and crash (shut down, not reboot). So I have to boot my device again by holding down power button.