Recently I installed CyanogenMod 11.0 M1 onto my Nexus 5. Since then charging the phone has become extremely slow, can anyone suggest any fixes for this issue?
Try going back to stock. It may be an issue with CM....in fact, I'd bet it's an issue with CM
Related
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
purudaya said:
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
Click to expand...
Click to collapse
A co-worker of mine had an S3 T999 on tmobile that did this same exact thing on the stock unrooted rom. I'd say its unrelated to CM, and glad you got a replacement. It should not do it again, so CM is safe to run on it.
Not a Rom issue. Sounds like just bad luck of the draw. I am on my 3rd or 4th s3 and i haven't had a Rom kill my phone yet.
Sent from my GT-P5113 using xda premium
So I just switched to a Nexus 5 from a Galaxy S4.... loved the phone until I connected it to my Tundra OEM bluetooth system. Hard to pinpoint an exact problem, it just doesn't work right. Randomly disconnects, etc. I had zero issues with bluetooth with my GS4. Is there some fix I should be aware of? i should mention that I rooted the phone right off the bat and am running Cyanogenmod Nightly.
Try it on stock to see if you have issues. It's most likely a rom issue
Sent from my Nexus 5
I've had a similar problem on stock rom with stock, chaos, franco and arkenstone kernels so I don't think the rom or kernel is the root of the problem. It will arbitrarily not connect, it will connect but when a call comes in won't automatically go to bluetooth but go to the handset etc.
I had hoped it was fixed somehow but happened again today out of the blue. It also comes with excessive bluesleep wakelocks that impact my battery life significantly (goes from draining at .7%/hr to ~3%/hr).
Absolutely loving this rom, but does anyone know if there are bluetooth issues with the current Cyanogenmod builds? Got a wear device for christmas, and it's battery life is about half what it should be. I've seen it reported on other devices running CM because of a problem with the Bluetooth drivers. Really trying to avoid switching back. Thoughts?
Can you please specify which device and what Wear Device are you referring to ?
The transition to Lollipop has been one of the most frustrating transitions on my OPO. Battery life completely destroyed, random reboots, bluetooth glitching, screen sensitivity issues. Just horrid. Many times I have considered going back to CM11S because it was amazingly stable and the battery life was top notch.
FINALLY I have found a lollipop rom that hasn't made me want to throw my phone into the wall (I have literally thought about it several times when my screen is having a completely unusable moment).
If you are having any of the above problems, I recommend grabbing the ParanoidAndroid rom. Bluetooth finally works without a glitch, battery is acceptable (still not 11S worthy, but 2 days without a charger at least). No reboots/crashes that I was getting with CM12. No more frustration.
Has anyone else had my frustrations and been happy with PA? Anyone have any other rom suggestions?
y0bailey said:
The transition to Lollipop has been one of the most frustrating transitions on my OPO. Battery life completely destroyed, random reboots, bluetooth glitching, screen sensitivity issues. Just horrid. Many times I have considered going back to CM11S because it was amazingly stable and the battery life was top notch.
FINALLY I have found a lollipop rom that hasn't made me want to throw my phone into the wall (I have literally thought about it several times when my screen is having a completely unusable moment).
If you are having any of the above problems, I recommend grabbing the ParanoidAndroid rom. Bluetooth finally works without a glitch, battery is acceptable (still not 11S worthy, but 2 days without a charger at least). No reboots/crashes that I was getting with CM12. No more frustration.
Has anyone else had my frustrations and been happy with PA? Anyone have any other rom suggestions?
Click to expand...
Click to collapse
I haven't had any stability issues with Lollipop, apart from BSOD problems on Nameless. The battery isn't as good as KitKat, but all ROMs I've tried have preformed really well. Have you tried Exodus?
@Heisenberg
What are the requirements for Exodus (firmware, kernel, etc.)? It is based on CM, does it have CM theme engine? I am looking at the thread, but not finding any relevant (via XDA app tough) Thank you!
Edit 1: ON G+ site, I found all the info
My friends lg g2 suffers greatly from ghost touches and swipes however it didnt do this before the lollipop update. Also the charging stopped working after the update i have since then replaced both the battery and the cable in the phone yet very little progress it charges SOMETIMES however the main problem is the touchscreen rendering the device almost useless. Im wondering if its possibly a software issue because if it is his phone is rooted but no custom os and i could try and see if installing cyanogen possibly solves the problem.