Related
I just rooted my Nexus yesterday to Cyans mod. I ve rooted before (tons of ROMS on my G1) so Im not a complete noobie. The ROM runs absolutely perfect and smooth EXCEPT for when I try to record video. Every time, and I do mean every time I try to record a video, the phone freezes for like 3 secs, and then reboots.
Camera shoots photos fine, and this is the only problem I have, but it is becoming a problem, considering I just bought the phone I searched the forms for this problem, and used multiple search strings and found no results.
Has anyone ran into this problem, and if so have you found a fix for it?
**MODS..I deeply apologize if this is in the wrong section.I worked a 10 hour shift and am half asleep while writing this. Please feel free to move if you see fit**
**EDIT..ok..NOT COOL...I just tried to watch a video, and that also no longer works. Anyone know of a fix for this?
Same issue here. Meh...
Ended up switching to Froyo. Hope Cyanogen keeps up.
drpfenderson said:
Same issue here. Meh...
Ended up switching to Froyo. Hope Cyanogen keeps up.
Click to expand...
Click to collapse
If you've flashed the 'Froyo' radio then you'll have to downgrade it before video will work, or move (back) to Froyo.
If you haven't changed radio then I have no idea!
same here. the test video i took when i got the (ph)one was amazing quality so i'm looking forward to this working again!
If you guys were EVER on Froyo. It updated your radio. If you then went back to CM builds, you will need to downgrade your radio to the eclair radios in order for the camcorder to work properly.
The phone hasnt been on Froyo (that I know of), so thats not causing my problem. I tried to flash the prerelease before I was rooted, but it was US only and didnt work. I didnt however update my radio when I flashed to Cyan, but I was told this wasnt causing the problem. At this point, anything to get my cam and videos working again!
Would be awesome if Cyan, the man himself, could hook us up with a fix or some advice on this one!
Dai323 said:
The phone hasnt been on Froyo (that I know of), so thats not causing my problem. I tried to flash the prerelease before I was rooted, but it was US only and didnt work. I didnt however update my radio when I flashed to Cyan, but I was told this wasnt causing the problem. At this point, anything to get my cam and videos working again!
Would be awesome if Cyan, the man himself, could hook us up with a fix or some advice on this one!
Click to expand...
Click to collapse
if you attempted to flash the froyo stock update, it included the new radio. its very possible that it successfully flashed your radio, but failed to install the froyo ROM. you can easily check if you have the new radio by going into your settings and checking the baseband version. i bet you are on the new froyo radio, which is known to break video with all 2.1 ROM's. and vice versa, the old radio breaks camcorder on 2.2 ROMs.
so each time you jump between a 2.1 and 2.2 ROM, you have to flash the associated radio as well.
GOOD POINT BRO. I will check this now...
**EDIT** that was it..I must have went to Froyo radio unknowingly. I flashed the stock Nexus radio, and vids and video recording are now working just fine.
Hope this thread helps the others. I foolishly searched "cant record videos" and found nothing, when I should have searched "cant play videos", as there are many threads on that one.
Again, thanks for your help!! Didnt expect a solution so quickly!!
It also seemed to give me 3g problems when I just flashed back, but I ll deal with that one tomorrow after work
Same issue
I have a n1 with 5.0.7.1 and my phone also reboots upon trying to launch the camcorder feature. I'm going to try out the new 5.0.8 test3 with 720p hack add-on and see how that goes.
htctouch1313 said:
I have a n1 with 5.0.7.1 and my phone also reboots upon trying to launch the camcorder feature. I'm going to try out the new 5.0.8 test3 with 720p hack add-on and see how that goes.
Click to expand...
Click to collapse
Any luck? I recently upgraded to CyanogenMod 5.0.8 and immediately after updating I noticed the change. I can watch videos in Gallery just fine, but trying to record (or open Settings) in the camcorder mode causes the phone to hang and then reboot.
I never once tried to get anywhere near Froyo. I'm still waiting for CM6. Any advice on how to restore video functionality? Should I downgrade to the previous version of CyanogenMod? Is that even possible?
As I said, I highly doubt this is a Froyo issue, but it's clearly related to upgrading to CM 5.0.8.
ronocdh said:
Any luck? I recently upgraded to CyanogenMod 5.0.8 and immediately after updating I noticed the change. I can watch videos in Gallery just fine, but trying to record (or open Settings) in the camcorder mode causes the phone to hang and then reboot.
I never once tried to get anywhere near Froyo. I'm still waiting for CM6. Any advice on how to restore video functionality? Should I downgrade to the previous version of CyanogenMod? Is that even possible?
As I said, I highly doubt this is a Froyo issue, but it's clearly related to upgrading to CM 5.0.8.
Click to expand...
Click to collapse
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
prettyboy85712 said:
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
Click to expand...
Click to collapse
I am not aware of ever having modified any "radio" functionality on my Nexus One. I bought the phone retail at the beginning of May, so it had stock 2.1. About a week later I flashed via USB to whatever version of CyanogenMod was current then. (I'm sorry and embarrassed I can't be more specific.) Everything worked flawlessly.
Then about three days ago, I downloaded the CyanogenMod Updater app from the Marketplace and used that to move to CM 5.0.8. I also performed a backup with Titanium, from which I restored after updating to CM 5.0.8. Since this was done, I my phone freezes and reboots whenever I try to record video. I mentioned the Titanium backup because perhaps the Restore System Data feature resulted in broken settings. But I do recall seeing "720p video" in the changelog to CM 5.0.8, so I'm guessing that's probably the culprit.
I don't understand how the radio would be affecting my camera, but I'm willing to try anything. If we assume that somehow the CM update did change my radio settings, how would I go about correcting that? Should I just wait for CM6, or is this radio problem likely to persist if I don't address it specifically? Is regressing to an earlier version of CM an option?
prettyboy85712 said:
So, to be perfectly clear, did you or did you not update your radio before flashing 5.0.8?
Click to expand...
Click to collapse
D'oh. This was clearly it. Because I got CM 5.0.8 via the CyanogenMod Updater app, I did not see that I was supposed to update the radio to Froyo independently of installing CM.
I tracked down the radio image (the Full Update Guide has all the info, for any interested persons) and flashed with that, and sure enough, I know have smooth 720p video recording.
Thank you so much for bluntly and persistently calling my attention to the radio image issue. I'm going to go back to playing with my favorite toy now. =)
Hi guys,
I have now succesfully unlocked, rooted, downgraded from HBOOT 2.02.0002, S-OFF'ed, installed BlackRose 2.02.0002 and a custom ROM.
MIUIv4.0 seemed to have a lot of glitches with apps (Touch Input and Maps) crashing frequently, no mobile network despite entering APN etc (do I need a certain version based on my provider?), and no WiFi. I have then installed Nik's Codename Vivo app, which works well except the WiFi and I have to reapply Swiftkey on boot. Otherwise the experience is incredibly smooth and Google Now seems very promising.
I've learned a lot in the process, and it's been fun flashing both through CMD prompt and through recovery. I was so proud the first time my laptop told my phone to do something hacker-ish. Continuing off the success, I'd like to play more around with the phone so I want your input on what I can/should do next? There's probably a lot of things I don't know that I don't know.
I have been doing some stuff in Tasker, which was fun. I am eg. now reminded of anniversaries and my Spotify app opens whenever I plug in my headphones. What I know that I don't know here is that I'd like to make something cool with Tasker and Ivona, I just don't really know where to start?
Any other ideas? Anything regarding tasker, customization (how does launchers exactly work? i tried a few back in the days and they seemed to slow performance a lot?) , flashing radios (are they any different? if so, how?) and whatever else, really. I'd really like to learn the full limits of what can be done both on an Incredible S and android, before eventually moving to another phone and perhaps WP8 so I can truly appreciate the differences.
I'd also like to take the opportunity to ask if anyone has ideas as to how I get the WiFi to work? I did flash the JB WiFi fix and it didn't work.
Lastly, if anyone is sitting on an Incredible S, have updated the software to the newest version and would like to mess around with it, feel free to ask away though I'm no expert. Also, I bought 4ext for downgrading but used Revolutionary for upgrading. How would I go about making 4ext interface my recovery screen again?
This is quite addictive, and I am now frequently checking for updates from Nik doing Codename on a different kernel, anything on CM10 and other stuff. So I'd also like to say thanks for a great community. Phew, I guess this post is a bit all over the place.
There are lot of stuffs present on Main Android development forum of xda..that will help you..
and for anything else you wanna know Google is your friend...
As for replacing the Revolutionary/CWM recovery with 4EXT Touch, you can simply flash the new recovery image in FASTBOOT USB mode using the command:
fastboot flash recovery [recovery.img file]
Miui v4 is still very buggy at the moment. I run the 2.4.20 GB build which I find far more stable and quicker. No Google now, however.
Never had an issue with Wi-Fi on codename, but found that my data never turned back on after I turned office Wi-Fi.
Have you downloaded Titanium backup yet? A must if you plan on flashing a lot of ROMs. Otherwise SetCPU to overclock your processor, and AdAway to get rid of those adverts in apps.
tpbklake said:
As for replacing the Revolutionary/CWM recovery with 4EXT Touch, you can simply flash the new recovery image in FASTBOOT USB mode using the command:
fastboot flash recovery [recovery.img file]
Click to expand...
Click to collapse
Thanks I'll try that out, downloading the recovery file now
Edit: Worked, cheers!
CyanideJack said:
Miui v4 is still very buggy at the moment. I run the 2.4.20 GB build which I find far more stable and quicker. No Google now, however.
Never had an issue with Wi-Fi on codename, but found that my data never turned back on after I turned office Wi-Fi.
Have you downloaded Titanium backup yet? A must if you plan on flashing a lot of ROMs. Otherwise SetCPU to overclock your processor, and AdAway to get rid of those adverts in apps.
Click to expand...
Click to collapse
Sweet. Well, the WiFi just never really boots up. I press "on" and it just starts loading, eventually the indicator will be switched to on, though with no colour filling (usually ON is highlighted in cyan)
I have an app called AdFree - is it any different from AdAway? I've yet to try overclocking, so I'll make sure to check it out, thanks!
Also,
For ur current rom, y dont u use nik project x? It has literally no bugs and it is android 4.0.3 and sense 4.0...
As for radios, they control all the bluetooth, wifi and gps signals, so if u flash a custom radio, u can get either really good reception or really bad. That depends on the radio. Beware as flashing a custom radio has a high chance of bricking so flash only if confident.
Have Fun!
(Insert Disclaimer)
Sent from my HTC Incredible S
Piccilino said:
Also,
For ur current rom, y dont u use nik project x? It has literally no bugs and it is android 4.0.3 and sense 4.0...
As for radios, they control all the bluetooth, wifi and gps signals, so if u flash a custom radio, u can get either really good reception or really bad. That depends on the radio. Beware as flashing a custom radio has a high chance of bricking so flash only if confident.
Have Fun!
(Insert Disclaimer)
Sent from my HTC Incredible S
Click to expand...
Click to collapse
Thanks a lot for your reply!
I flashed Codename because it was a jellybean ROM and because to my understanding getting as close to pure android as possible would enhance the performance of my phone. Though I guess with a custom rom (Codename) it's not pure android anyway.
If the radio controls WiFi and GPS, can my WiFi problems be due to a suboptimal radio in the codename rom?
I won't be able to use Google Now with Project X, will I?
Splintre said:
Thanks a lot for your reply!
I flashed Codename because it was a jellybean ROM and because to my understanding getting as close to pure android as possible would enhance the performance of my phone. Though I guess with a custom rom (Codename) it's not pure android anyway.
If the radio controls WiFi and GPS, can my WiFi problems be due to a suboptimal radio in the codename rom?
I won't be able to use Google Now with Project X, will I?
Click to expand...
Click to collapse
Codename is pure android 4.1 JB with a few tweaks on top.
The majority of bugs in all the JB based ROMs are due to the fact that we don't have the right kernel for jellybean ROMs available for our devices yet. People far smarter than me are working on it, but it's slow going.
As far as I'm aware Google now didn't come with Project X.
AdAway is the same as AdFree, but is better in my opinion.
Hello everyone,
Yesterday I decided to flash an updated ROM of 4.3 to my One. After flashing it (happens with new ROM, or after flashing a new custom kernel... logo2menu, you know), a message appears ALWAYS on-screen:
com.phone.android has stopped working
This message repeats a hundred times. I can't type anything without the message popping up. I reached the launcher, but I have no Phone signal and the WiFi is not working. It's like the phone wants to wake up the Phone Antenna but it crashes to do it.
I've read that I had to flash the boot.img from the ROM I wish to flash, and I don't know if that causes the problem...
Any help would be perfect.
Thank you in advance.
=====================================================================================
SOLVED!
Well, after my vacation, took my One and did a bit of research. I know everything about this problem now.
The problem is only in GE ROMS. Why? 4.3 GE hasn't listed my MVNO yet (known error by Android and by 'Pepephone'). So, as soon the mobile goes on, Android tries to connect to the SIM, but as it's not listed amongst the companies, the phone crashes. I had to flash a file with the APN, then add it manually. Ta-Da! It works.
Attached the ZIP file to flash in Recovery.
- Install 4.3 GE Rom.
- Flash the Fix.
- Start and complete the Install Wizard.
- Inside the APN config, manually introduce Pepephone's APN
o NAME: Pepephone
o APN: gprsmov.pepephone.com
o MCC: 214
o MNC: 06
Sorry to bump the thread, but currently I have a HTC One with no phone and it's really important for me to solve this asap. I'm going on vacation tomorrow and I need my phone
raulongo said:
Sorry to bump the thread, but currently I have a HTC One with no phone and it's really important for me to solve this asap. I'm going on vacation tomorrow and I need my phone
Click to expand...
Click to collapse
Are you using a custom kernel that matches, exactly, the 4.3 custom rom you are using? If it is a GE 4.3 based rom, you need a GE 4.3 custom kernel (check out ElementalX). If it is a Sense 4.3 base rom, well that update just came out yesterday and there are no custom kernels for it yet.
dgtiii said:
Are you using a custom kernel that matches, exactly, the 4.3 custom rom you are using? If it is a GE 4.3 based rom, you need a GE 4.3 custom kernel (check out ElementalX). If it is a Sense 4.3 base rom, well that update just came out yesterday and there are no custom kernels for it yet.
Click to expand...
Click to collapse
It happens with EVERY 4.3 GE Rom, stock kernel. I was in 4.2.2 GE (Android Revolution) and Installed 4.3 and gave me that error all the time without upgrading the Kernel... I'm pretty lost.
raulongo said:
It happens with EVERY 4.3 GE Rom, stock kernel. I was in 4.2.2 GE (Android Revolution) and Installed 4.3 and gave me that error all the time without upgrading the Kernel... I'm pretty lost.
Click to expand...
Click to collapse
It sounds like there is an incompatibility with the new base. I would reflash the rom, doing a full wipe in the process
dgtiii said:
It sounds like there is an incompatibility with the new base. I would reflash the rom, doing a full wipe in the process
Click to expand...
Click to collapse
Full wipe means to wipe/factory reset in ClockWork Recovery before flashing? I already did that like dozen times, but still, same error I don't know why I'm the only one with this problem...
raulongo said:
Full wipe means to wipe/factory reset in ClockWork Recovery before flashing? I already did that like dozen times, but still, same error I don't know why I'm the only one with this problem...
Click to expand...
Click to collapse
The Roms I've used have an option for full wipe during the install in Aroma, but I guess doing it in CWM does the same thing. Are you theming the phone app by any chance? Something isn't playing nice with the 4.3 base, that's what you have to track down. Maybe go back to 4.2 while you sort it out
dgtiii said:
The Roms I've used have an option for full wipe during the install in Aroma, but I guess doing it in CWM does the same thing. Are you theming the phone app by any chance? Something isn't playing nice with the 4.3 base, that's what you have to track down. Maybe go back to 4.2 while you sort it out
Click to expand...
Click to collapse
Yup, did it inside the installer and outside it, but always same result. I'm back now into 4.2.2 Sense AR Rom and the phone works great, but I hate Sense.
Could it be the baseband firmware?
raulongo said:
Yup, did it inside the installer and outside it, but always same result. I'm back now into 4.2.2 Sense AR Rom and the phone works great, but I hate Sense.
Could it be the baseband firmware?
Click to expand...
Click to collapse
Firmware could be the case, was just thinking that.
My advice tho, you have a working phone, and with your vacation tomorrow, I would leave it as is for now
dgtiii said:
Firmware could be the case, was just thinking that.
My advice tho, you have a working phone, and with your vacation tomorrow, I would leave it as is for now
Click to expand...
Click to collapse
Thank you for your help. I will investigate a bit more as soon as I'm back.
raulongo said:
Thank you for your help. I will investigate a bit more as soon as I'm back.
Click to expand...
Click to collapse
Sounds good, you're welcome. Enjoy your vacation!
I have the exact same problem. I've literally tried everything. I have S-Off-ed my phone and installed a custom kernel but even that does not fix the problem. All custom 4.3 Google Edition Roms crash after I install them. It works fine if I use the Stock 4.3 ROM.
Kernel
Sent from my HTC One using XDA Premium HD app
dgtiii said:
Sounds good, you're welcome. Enjoy your vacation!
Click to expand...
Click to collapse
A little update. I've got Cyanogen 10.2 working perfectly in my phone. It's running 4.3, so now, I understand even less. Why CM works and the other ROMs doesn't?
The night is long... Hahah.
CM 10.2 works flawlessly "without" bugs. I don't understand why CM 10.2 (JB 4.3) works and the other 4.3 GE does not. Something is not right, or maybe I'm missing some step, but it's really strange...
raulongo said:
Hello everyone,
Yesterday I decided to flash an updated ROM of 4.3 to my One. After flashing it (happens with new ROM, or after flashing a new custom kernel... logo2menu, you know), a message appears ALWAYS on-screen:
com.phone.android has stopped working
This message repeats a hundred times. I can't type anything without the message popping up. I reached the launcher, but I have no Phone signal and the WiFi is not working. It's like the phone wants to wake up the Phone Antenna but it crashes to do it.
I've read that I had to flash the boot.img from the ROM I wish to flash, and I don't know if that causes the problem...
Any help would be perfect.
Thank you in advance.
Click to expand...
Click to collapse
If you simply need a working phone, return to stock for your vacation, and then start from scratch re-flashing the GE firmware, kernels and rom. If anything is sense on the phone, incompatibility issues will happen.
kibmikey1 said:
If you simply need a working phone, return to stock for your vacation, and then start from scratch re-flashing the GE firmware, kernels and rom. If anything is sense on the phone, incompatibility issues will happen.
Click to expand...
Click to collapse
Finally found a solution to the crash. It was related to a weird combination between GE 4.3 and my mobile network operator, Pepephone. Known bug by Android and Pepephone.
Solution at the first post.
Hello everyone, I am new to this forum but have been rooting androids for years now. I have an issue now that I have never seen before. I have my HTC One rooted, S-OFF, firmware updated, everything as it should be. Heres the problem. Whenever I try to install a rom, (Insert coin, Renovate, etc.) the install goes totally fine. However, whenever I go to reboot into the system, it just hangs at the first splashscreen. The one with the green HTC logo and the powered by android at the bottom. It has sat for 5 minutes before I decided to turn it off. Anyone know a fix to this? thanks,
Parker.
PS. All of these are Aroma install roms, if that matters.
Have you tried flashing a regular Ron without AROMA, like the stock Rooted rom?
Based on the touchscreen issues with AROMA and thus phone, are you certain that you are flashing the correct carrier?
AarSyl said:
Have you tried flashing a regular Ron without AROMA, like the stock Rooted rom?
Based on the touchscreen issues with AROMA and thus phone, are you certain that you are flashing the correct carrier?
Click to expand...
Click to collapse
I've run into this on the 4.4.3 and 4.4.4 ROMs on my S-On HK edition. When the screen does go out after several minutes, I hit the power button and the phone works normally. I'm guessing that it has to do with old firmware being used with the 4.4.3+ ROM bases. I'm going to do Sunshine S-Off today so I can update my firmware and see if that makes a difference.
I have not tried a non aroma rom, that might just be my next step. I know for a fact it is the correct carrier rom, all the ones I have flashed are universal
I will try to do the power button thing you mentioned, thanks for the tip.
After work I will try all of these!
parkerskouson13 said:
I have not tried a non aroma rom, that might just be my next step. I know for a fact it is the correct carrier rom, all the ones I have flashed are universal
I will try to do the power button thing you mentioned, thanks for the tip.
After work I will try all of these!
Click to expand...
Click to collapse
Just got S-Off and upgraded the firmware to the latest. The problem has been solved for me. Boots right up now.
Which firmware did you upgrade to? I tried to upgrade to 2.22xxx and it didn't fix anything for me.
My title was abit too long, cause it was copied from a reddit post I made on Cyanogenmod's reddit. R/s means "Receive or Send"
I tried going to Cyanogenmod's Reddit, asking for help with this issue, but there was no luck at all, one user did respond to me and tried to help me out, but hasn't responded for the past 3 days. Looking around for more help, I was directed here to ask. If at all, I'm doing something wrong, can you please tell me.
FYI: My Nexus 6 is using Cyanogenmod 13.0 NIGHTLY, running 6.0.1
Besides that, the reddit post is basically this:
"Please direct me in the correct area, at the moment I don't see much to go to for some help, but I felt like making post.
After a while, I've been using Bell Canada on my phone without any issues, but I never tried voicemails or calls. Recently, trying to get into my telegram account cause they won't send a SMS (For what ever reason), the app offered to call my phone, waiting for the timer to tick down before they call my phone, it just shut it's self off.
I was aware of my phone crashing due to voice mails, cause before I activated my sim card, I had a voicemail that wouldn't go away, trying to view it, the phone would crash. I was hoping this would've been fixed after a couple updates, but it doesn't seem like it was fixed at all. I can't even tell if this issue is my problem (the phone/sim card) or cyanogenmod.
If anyone knows any fixes for this, I'd be really happy, because currently my phone is useless to most things I'd use it for, other than SMS."
On the reddit post, the user that was replying to it did mention something about c-apps not being compatible with Cyanogenmod 13.0 and told me to try to uninstall it, but when I tried to uninstall it through adb, apparently such a directory doesn't exist. I do hope I can get some help here, because I'm currently on a plan with unlimited text and calls, paying alot of money for it, but one feature is completely useless.
--Something I want to add, I tried the same sim card in my HTC One M7 running Android 5.1 with Cyanogenmod 12, calls worked perfectly fine with it.
Please do correct me if I'm doing something wrong, but reading the forum rules, I don't see anything about "bumping", so... Here's my bump.
I haven't had a reply for 5 days now, the possible answer to why my topic wasn't replied to, is most likely because noone knows how to fix this or why this might be happening.
But, I do wish I could get a post or something to show that people do see this, or maybe a post telling me that my issue has a unknown fix.
Edit; I see this rule #5, but, I don't know if that applies to bumping, I don't know how else I could explain my issue. I've explained it the best I've could.
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Darth said:
I'm on Bell, and no issues. I don't use CM or CM based Roms though, so the simple way to know if it's rom related is to flash stock, or another non CM based rom.
Other than that, not sure at else to tell you.
Click to expand...
Click to collapse
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
MoonieHorse said:
I do feel it might be rom related, because as I said in the post, I tried this with my HTC one m7, with cyanogenmod 12 nightly, not 13, and it worked.
I don't know any other Roms for Nexus 6 and cyanogenmod is the only one I know how to set up.
Click to expand...
Click to collapse
Look in the Nexus 6 Android Development and Nexus 6 Original Android Development subforums, there are tons of options available.
Read over this- [HOW-TO] The Nexus 6 All-In-One Beginner's Guide. A brief guide to clean flashing ROMs. Using TWRP, wipe everything except internal storage (system, data, cache, dalvik). Flash the ROM and then gapps package (some ROMs based on stock don't require gapps so look in the thread). There you go, you have a clean flash of a new ROM.
If you have issues with CM13, try ROMs based off of AOSP like Chroma, Pure Nexus, Dirty Unicorns, AOSiP, etc...
Darth said:
The procedure to flash any rom is nearly the same. Or use fastboot to flash a stock image.
Just do a nandroid backup before flashing another rom, to be safe. And pic an aosp rom, not cm based.
Click to expand...
Click to collapse
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
MoonieHorse said:
I'll keep this in mind for the near future then. I don't really want to flash a different rom on my phone cause of... Well, the known risks of doing so aka possibly turning your phone into a brick or losing all the data.
What I'll do is, I'll hold on abit with Cyanogenmod, see if they release any fixes and go from there, maybe even bump them about said issues to see if this is known or not.
Thank you for your help though, I'm sure I'd come back here again if I needed some help again.
Click to expand...
Click to collapse
You will not "brick" flashing a rom. You can have issues, sure, but that's what the nandroid backup is for.
Honestly, if you're that worried, I'd restore the stock image and not tinker with it.
But if you leave it as is, I doubt you'll fix your issue.