Strange issue with kitkat builds. I'm using quantum and my wife is using collective. She came to me a few days ago when her phone wouldn't hang up. Everything works normally but the phone will not hang up. Reboot was how we got out of the call. Then yesterday the same thing happened to my phone. Then today hers again.
Anyone else have this problem with cm11 builds?
Related
I've got a Verizon G'NEX and I flashed DroidViscious's 4.1.1v1 rom with Franco's kernel about a month ago and everything was smooth sailing up until last week. I've been experiencing random instances of my screen freezing for about 10 seconds followed by my device rebooting. Upon startup right after a reboot I can enter my pattern lock and then it freezes immediately after and reboots (I can tell it's responsive during the unlocking of the pattern because of the haptic feedback). This will happen several times before I'm able to get back to the homescreen without it freezing.
I thought there was a problem with the rom since it was an older build Jelly Bean so I wiped the device and flashed the latest build of Pete's BuglessBeast using his default kernel hoping that would solve the problem. Unfortunately it didn't. I'm still experiencing these random freezes and reboots and the only way I can get it to boot without freezing is to pull the battery out for a couple of minutes and try again.
I'm wondering if the device is thinking it's getting too hot so it shuts down but I don't really have any way of knowing (it happens a lot when I'm in the car or when the phone is charging). Anyone have any ideas on what the problem is and how to resolve it? Or any ideas on how I can debug the problem myself? It's happening fairly often now when I need my phone the most.
The phone isn't even a year old so if relock the bootloader and return it to stock it should be covered under warranty still if there's a hardware issue.
Well, this problem seems to be exclusive to Jelly Bean. I reverted back to ICS and everything seems to be fine. Is anyone else having this problem with Jelly Bean roms?
yeah I get alot of random reboots and some freezes here and there. not sure what it is. but i have to gsm version gnex.
Ever since I flashed CM 10.1 I have been getting freezes, like 3 times a day. I would be listening to music then it freezes but the music is still playing and I have to do a battery pull. Also if I don't use my phone for hours when I take it out of my pocket, after a while it just freezes on me. I have tried re flashing 10.1, 10.1 rc3, pacman. I'm thinking about a TW rom, would the freezes stop? Also i used to have dirty unicorn 7/20 version and I had no freezes. This was maybe 2 weeks ago. I also even tried to not overclock/unvolt/underclock at all and I still got freezes, this literally never happened to my phone before, except maybe if I overclocked too high and it reboots on its own.
oshinqwe said:
Ever since I flashed CM 10.1 I have been getting freezes, like 3 times a day. I would be listening to music then it freezes but the music is still playing and I have to do a battery pull. Also if I don't use my phone for hours when I take it out of my pocket, after a while it just freezes on me. I have tried re flashing 10.1, 10.1 rc3, pacman. I'm thinking about a TW rom, would the freezes stop? Also i used to have dirty unicorn 7/20 version and I had no freezes. This was maybe 2 weeks ago. I also even tried to not overclock/unvolt/underclock at all and I still got freezes, this literally never happened to my phone before, except maybe if I overclocked too high and it reboots on its own.
Click to expand...
Click to collapse
Same boat here. I'm pretty sure it's from the latest kernel release.
Sent from my SPH-D710 using XDA Premium 4 mobile app
I was running the SGH-i747M with CWM 6.0.4.7 and testing out some 4.4.2 ROMs, I got another phone to play with now and I gave this one to my girlfriend but she doesn't like nightlies so I was trying to install a 4.2.2 or 4.3.1 stable ROM and they won't work. I read online that it might be due to the CWM being too new because it's support is for Android 4.4.x. So I downgraded CWM and that didn't work either. I ended up convincing her that nightlies aren't that bad and shes currently running Carbon but she hates flashing the new nightlies so I do it for her every few days or so. I've noticed though that this phone is acting up really weird since I tried to downgrade CWM and then install the current one again. Sometimes it reboots at random, I gave the phone to her with BAM 2.0 RC2 (I know, shame on me), and that was horrid, so I tried CyanogenMod and that was "okay" but she said it's boring and she wants more features, so I switched it to Carbon because that's what I'm running on my SGH-i317M and she seems to like that, but it's still acting really weird.
When I was using the SGH-i747M while I was waiting for the new display to come in the mail for my SGH-i317M, I was running BAM and the only thing was it was a battery hog, and ocasionally I would get a "blame tyler" error for some things but it was never repeatable, I switched to Carbon and I was running completely stable on the nightlies, I used it for my day to day and not one problem, after switching over to my SGH-i317M now running CarbonROM, still flawless, not a single problem, fast, good battery life, signal strength is always good, but the phone I was on, running the same ROM, is now glitchy as hell and she's talking about getting an iPhone 5S now.. guys you gotta help me here, I just got her to give up her iPhone 4 for this S3 I gave her, I need this phone working, it is a critical situation lol.
The camera app will take one picture, then the screen will freeze and when I close the app, it opens right back up with the same picture, when I completely close the app, it opens up saying can not conect to camera and the only solution is to reboot the phone. It randomly reboots on it's own some times, the battery doesn't last more then a few hours (between 2 to 3 hours depending on use and when I was using it on Carbon, I got 30 hours off of a single charge once, but the average was around 20 hours of use before it would die) and she was telling me while she's on high brightness but never full brightness, the phone gets really hot so there's something wrong from when I flashed an old CWM using Odin, and then flashed it back to the current one.
So how can I do some kind of full wipe everything and make everything better procedure? Does this exist yet? Is it a real thing?
I'm thinking some kind of recovery wipe, completely wipe everything except the boot loader so I can install a fresh copy of CWM using Odin, and then some kind of AOSP ROM that's stable but I think she likes Carbon now so we might just stick with the nightlies as long as these random force closes and random reboots stop, and the camera works, I mean, you can't instagram without a camera, so that makes this phone nearly useless for her. One picture, freezes, reboot the phone, opens picture from gallery, then hipsters it out, then shares it.. not exactly the seamless method she was looking for lol
Please help guys, I really don't want to see another iPhone laying around the house.. ugh..
Is anyone besides me still using this phone? I'm impatiently waiting for a 2015 Nexus or carrier neutral/Project Fi capable Motorola.
For the most part my phone works fine and does what I need it to do. I've been running v11 M12 since its release without any serious issues EXCEPT...
Lately I've noticed after a few days the phone will slow to a crawl. I'll open Running Apps and see a bunch of apps restarting at one time. Only a reboot will resolve the issue. I'm not running any obscure or obviously misbehaving apps and everything works fine for a few days. It doesn't appear to be 4G/WiMax related (turning it off doesn't resolve the issue).
I flashed the last milestone build, XNG3CAO1L7, without a factory reset and it seemed really buggy right away. I'm trying the latest NIGHTLY right now and it also seems a little buggy. I'd rather not factory reset, but I will if that is what it takes to resolve my issue.
Just curious about the status of anyone else running these builds. Thanks!
Hi all,
I have been using LineageOS 14.1 on my Moto G5 for the past year without any issues. However, of late, I am having problems with the audio. I can't figure out what is happening or why it is happening. What has happened is that the phone speaker is not working at all. No matter what I do, whether it is taking a call, listening to media files, or playing videos on YT or in the browser, I cannot hear anything at all. I can hear the audio if I plug in a headset. I have never had this problem before and then it suddenly popped up a few weeks ago. Thinking it was a major problem and wanting to upgrade, I wiped the ROM and installed LOS 15.1. That got the speaker working but it was giving me other issues so I went back to 14.1 about two weeks back. The speaker was working fine until today when it has died yet again. I have tried restarting but it hasn't fixed the issue. Is this a know bug? Is there any standard way of dealing with the issue? After the last time I needed to reimage my phone, I have been taking regular backups so I can do yet another reimaging and reinstall everything but I really don't want to do that. Please help.
Update: I did a factory reset, did a fresh reinstall of OS 14.1 but still no sound Please help!
aksnitd said:
Hi all,
I have been using LineageOS 14.1 on my Moto G5 for the past year without any issues. However, of late, I am having problems with the audio. I can't figure out what is happening or why it is happening. What has happened is that the phone speaker is not working at all. No matter what I do, whether it is taking a call, listening to media files, or playing videos on YT or in the browser, I cannot hear anything at all. I can hear the audio if I plug in a headset. I have never had this problem before and then it suddenly popped up a few weeks ago. Thinking it was a major problem and wanting to upgrade, I wiped the ROM and installed LOS 15.1. That got the speaker working but it was giving me other issues so I went back to 14.1 about two weeks back. The speaker was working fine until today when it has died yet again. I have tried restarting but it hasn't fixed the issue. Is this a know bug? Is there any standard way of dealing with the issue? After the last time I needed to reimage my phone, I have been taking regular backups so I can do yet another reimaging and reinstall everything but I really don't want to do that. Please help.
Click to expand...
Click to collapse
Does the sound work with the stock Nougat/Oreo?
Andrej_SK said:
Does the sound work with the stock Nougat/Oreo?
Click to expand...
Click to collapse
Hey,
I have never used the phone with the stock ROM. I bought it over a year ago and immediately installed 14.1. I can tell you the speaker was working both on the stock ROM out of the box and on 14.1 as well. It ran perfectly fine till a month ago when the speaker stopped working out of the blue. I did a factory reset and installed 15.1 and the speaker started working again. Then I went back to 14.1 a week later as mentioned. The speaker was working fine till yesterday when it conked out again. After that, I did a factory reset and reinstalled 14.1 which didn't fix it.
Sorry if I'm repeating myself too much, I'm just trying to give a clear timeline of events. Right now, I am using the phone with my handsfree. Everything other than the speaker is working. I can make calls and listen to media on my headset, just not on the speaker.
If you need me to run any diagnostics or terminal commands for testing, let me know. I would very much like to resolve this without another reinstall if possible.
Second update - I was so sure this was a software issue that I didn't even bother to check the hardware. Turns out the G5 has a contact problem with the speaker which has to be fixed by squeezing the top half of the phone to get it to make better contact. I did that and problem solved. Consider this thread closed.