My girlfriend wanted Jellybean on her vivid, so we set her up with CM 10. She isn't a heavy phone user, so most of it works just fine for her.
However, she's run into a problem where occasionally the phone reboots when she tries to make a phone call. No amount of power down, power back on seems to fix the issue. It does seem to go away in time, but will eventually come back.
Any suggestions on this? The ROM she is using is the unofficial Cyanogen one by H8rift and team.
Thanks for any help!
Related
Im running ZenHeroFX 2.1 Lite ROM with 710 Darchstar kernel... my phone is so annoying with it. At times it is lightning fast and everything works perfectly. And other times, (often but not always) during and after recharging from a low battery (ie. <15%) the touchscreen becomes super laggy.
For instance, while clicking on an icon on my homescreen, it will light up but not start the app. Rather, it will freeze for a sec or two and then as if I held the icon it would try to move it around the screen. Or when dialing a number the numbers would show up literally 20 seconds or so after the keypress.
Today the same thing happened but after a few minutes of this the touchscreen became totally unresponsive. I realized tho, that I could use the menu, home search, back and power keys and the phone responded almost at normal speed. But I was unable to enter any type or anything else involving the touch screen. After several reboots and one long reboot after clearing the cache, it finally is back to normal. This happens to me every few days or so, however, and is very annoying. Any suggestions as to why this is and/or how to stop it?
Change roms buddy. Sounds like your having a ****ty time with that one
Best very is to go with cyanogen. Have yet to have a problem with it not have I found a faster rom. My 2 cents
Sent from my HERO200 using XDA App
I fell in love with Konikub's Pure Hero rom but after the discovery of the bug in Toasts BFS #89 kernel that force closed the phone from time to time i had to reconsider. I know they make the updated kernel for roms that had that issue but without BFS the speed of the rom just isn't the same even overclocked. That is until i revisited Froyo after the first shrewd attempts back in the day lol. Let me tell u Darch and team r a dedicated group of talented individuals who know what they r doing when it comes to ROM development. His CyanogenMod 6 though it's still in the final testing stages is way good enough as an everyday ROM for me. It's fast without the complexity of BFS and is customizable to all ends. If u love senseless roms then u will love CM 6.
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
Hello!
I'm running Beanstalk 4.4 and the latest Meeow kernel. My phone works well (mostly) and has great battery life. It also drops calls ALL the time. Like all the time between 5s and 2mins.
I also have a problem whereby the screen is kinda screwed for touch. Like a touch is already registered and stuck on rendering the phone useless until a reboot. Probably not related. Can live with that even.
But the call dropping is way bad. I've installed ROM from fresh and tried latest kernels. Don't really notice when it started.
Any one have ideas pls? Thanks!
i
bonstio said:
Hello!
I'm running Beanstalk 4.4 and the latest Meeow kernel. My phone works well (mostly) and has great battery life. It also drops calls ALL the time. Like all the time between 5s and 2mins.
I also have a problem whereby the screen is kinda screwed for touch. Like a touch is already registered and stuck on rendering the phone useless until a reboot. Probably not related. Can live with that even.
But the call dropping is way bad. I've installed ROM from fresh and tried latest kernels. Don't really notice when it started.
Any one have ideas pls? Thanks!
Click to expand...
Click to collapse
so it s Bug of this custom ROM and u should ask to solve from its developers.
if u wanna check ur hardware is fine u must back to stock ROM or install trustful & famous rom like CyanogenMod & etc
if ur phone works fine with them so previous rom wasn't good enough
:good:
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Cellulario said:
I have been using CM11 for a while now and I am experiencing frequents hangs and hiccups. In particular the systems doesn't seem to be able to handle an installation, what I mean is that whenever I install or update an app the system hangs like if it can't handle a multitasking session, the systems freezes. Also, I ofent have my device frozen and I can't turn it on, the screen stays black for long periods, in the order of 5 minuts or more. I'd say this ROM is not functional. Is there anyone else who is experiencing the same problems? I am not sure whether the ROM is not working properly because of some setting I changed but well... I was thinking about going back to stock or to re-format and start over with a fresh CM11 because it might also be that I did something wrong. Any comment or suggestion, personal experiences? is CM11 working on your xperia sp's?
Click to expand...
Click to collapse
It did start lagging after a few weeks and for me the recent button took forever (3 secs ! thats a lot since it never took that much long) to open recent menu. So I reinstalled it not knowing whether it was my fault or CM and to my surprise after a few weeks it did it again and I switched to PAC rom. Never looked back. IMO pac rom is the best experience of kitkat on sp.
I've been using this outstanding phone for more than a year now. It's awesome.
since i have some feature that i would like to keep i am Not using the official miui (neither global, dev or chinese) but trying different roms in the last few weeks(MSM, Epic, Lineage etc..).
I just cant seem to figure out what makes the phone reboot when i'm climbing on my bike(v twin -F800st if it matters at all) and sometimes when charging it. Maybe the heat is the problem( i dont think so as i couldn't see any trouble with it on the last year at all).
Some Roms make me experience this more than others(MSM) and some less(Epic).
Is there any way to log for the reason of the reboots?
Tried a few different Kernels as well but didn't change anything.
Mi Max 2(oxygen), currently on Epic rom, nougat 7.1.1 miui 10.
Any help would be much appreciated.
eeebbr said:
I've been using this outstanding phone for more than a year now. It's awesome.
since i have some feature that i would like to keep i am Not using the official miui (neither global, dev or chinese) but trying different roms in the last few weeks(MSM, Epic, Lineage etc..).
I just cant seem to figure out what makes the phone reboot when i'm climbing on my bike(v twin -F800st if it matters at all) and sometimes when charging it. Maybe the heat is the problem( i dont think so as i couldn't see any trouble with it on the last year at all).
Some Roms make me experience this more than others(MSM) and some less(Epic).
Is there any way to log for the reason of the reboots?
Tried a few different Kernels as well but didn't change anything.
Mi Max 2(oxygen), currently on Epic rom, nougat 7.1.1 miui 10.
Any help would be much appreciated.
Click to expand...
Click to collapse
Sounds daft but when you're mounting your bike are you accidentally pressing the power button too long on the phone, use to happen to me on my car windscreen mount. As for the reboots during charging that is weird
definetly not the situation here.
The fact that this phone screen is rather big and the kavpower(https://www.amazon.com/Kapaver-Xiaomi-Cover-Premium-Rugged/dp/B0747RJ5RL) case shows the part above the vol up button which i can mount the phone pretty easily being far away from the power button...
Also, it doesn't always goes off instantly. sometimes i can ride for 10-15 mins and than a extensive reboot session starts.
As soon as i pull it of the bike, it usually just stops this frenzy.
Thats wh im so eager to find a way to find th reboot reason.
can you attach the logcats?
First assumption here would be the overclocking or under volting .. so stick with a stock kernel or near stock rom / ie miui global or xiaomi.eu or mi-globe.. and see if the reboots disappear .. if it goes away try introducing one thing at a time .. a kernel then a rom and so on