Hello people I Open this post because I want to know how it's this version running on your S3 because I do dirty flash every time a version comes out I update like every 3 days my CM10 now with this latest update I notice that phone isn't smooth as previous build and screen flickers! I never had that problem before
So I would like to know your opinion if that only happnes because of dirty flash ? or It's that build really buggy and slow
Thanks!
I'm running CM10 right now and I actually did a dirty flash on top of Codename. I haven't experienced any peculiar bugginess as of yet though!
Related
Just wondering if anyone is still running this? I seen this is the last version before the 10.1 started. I want to run the CM10 because 10.1 still has some bugs.
Just some quick questions
1. Does MMS work?
2. Are there any major bugs?
Again this is for the 12/16 CM10 4.1.2 nightly.
Sent from my stock rooted Galaxy S3
im still running it and its perfect.. everything works and has great battery life.
im using the kt747 kernel with it and oc to 1.8
The latest nightly builds of CM have a FEW bugs...but still quite stable/usable. I run the 12/16 build every once in awhile, but the new nightly's are so damn smooth.
Also, give LiquidSmooth RC2 a try. Virtually bug free. The Stable release of LiquidSmooth has a few bugs, but again, still very stable.
If your going for a virtually BUG FREE AOSP Rom, I would advise LiquidSmooth RC2 with the latest BMS Kernel. Tweak it to OnDemand/Row : 126 min, 1512max, and you will be quite pleased.
Generally the CM versions up to the latest official release are very stable
As in, the latest official release was MB1 (4.1.2) so you can expect CM 4.1.2 to be very stable
Its when you go past the official release versions that you start encountering more bugs, like in CM 10.1 (4.2.1 and 4.2.2)
I just tried out Liquidsmooth. It's not a bad rom, just don't like the fact it looks like a theme.
Yeah I know CM uses a launcher as well, but overall it looks like a stock JB rom. Flashed cm10 nightly 12/16. Runs great with no issues or freezing. Once we get the official 4.2.2 I'll update to cm10.1.
Sent from my stock rooted Galaxy S3
If anyone uses cm10 (4.1.2) stable, I have the handoff update still if you want it.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
I've been using CM 10 and 10.1 nightly builds on my Verizon GNex for quite some time without issue. Yesterday I decided to try the Carbon Rom(4/22 nightly, 4/23 nightly and 1.6 Stable) and had the same issue on all.
I get no WiFi, or 3G/4G signal. If I try to launch the browser it flashes on the screen for a second and then disappears. It's basically unusable for me. I did a clean flash to make sure nothing from the CM 10.1 Rom would cause any issues but still have the same problems.
I really wanted to check out that Rom because it looks pretty nice and is supposed to be really fast.
Does anyone have any ideas of what I can try? The Rom itself installs fine, but once it's installed I have those issues.
I looked through a bunch of the forum pages for the actual Rom itself on here and didn't notice anyone else reporting these issues so I'm not sure why I'm seeing this. I've installed other Roms other than CM without issues.
Thanks,
Ben
what kernel are you using mate ? did u full wipe.?
i am not having any issues with it.. using the kernel that comes with it
Sent from my Galaxy Nexus
bdensmore said:
I've been using CM 10 and 10.1 nightly builds on my Verizon GNex for quite some time without issue. Yesterday I decided to try the Carbon Rom(4/22 nightly, 4/23 nightly and 1.6 Stable) and had the same issue on all.
I get no WiFi, or 3G/4G signal. If I try to launch the browser it flashes on the screen for a second and then disappears. It's basically unusable for me. I did a clean flash to make sure nothing from the CM 10.1 Rom would cause any issues but still have the same problems.
I really wanted to check out that Rom because it looks pretty nice and is supposed to be really fast.
Does anyone have any ideas of what I can try? The Rom itself installs fine, but once it's installed I have those issues.
I looked through a bunch of the forum pages for the actual Rom itself on here and didn't notice anyone else reporting these issues so I'm not sure why I'm seeing this. I've installed other Roms other than CM without issues.
Thanks,
Ben
Click to expand...
Click to collapse
1 question, did you flash gapps package? Because I had that problem when I just flashed Carbon ROM ... Wanted to check out if there's a file explorer in the ROM itself ...
paarthdesai said:
what kernel are you using mate ? did u full wipe.?
i am not having any issues with it.. using the kernel that comes with it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Right now I'm trying the kernel that comes with Carbon. I did do a full wipe prior to installing the Rom.
I downloaded the Xylon Rom yesterday and that installed with no problems at all. So not sure why Carbon is having these issues on my phone.
i am using ak kernel 207
i used the kernel with the rom and had no issues with it also..but ak kernel + carbon = best battery
and the pa setting added now is a icing on the cake,i dont need anything else
WiFi is not working at all, I used TWRP, wipe and advanced wipe, but still can not succeeded.
Well, I am using the latest Carbon Nightly with SmittyV Kernel (also the latest one) and it's working pretty well
Not perfect because my phone sometimes shuts down randomly and it still has some issues like when using the Carbon Active Display with the default messaging app (the "unread message" notification doesn't go away even after I reply to the message and close the app with the back button) and it sometimes freezes the phone (making me have to remove the battery to turn it off and then reboot).
Other than that I'm not having any problems with Wi-Fi. Try to install another rom then install again the carbon rom wiping everything in both flashes
Hey guys, posting to get some help with some forced reboots.
I migrated from d2att CM 10.1.3 to SlimBean 4.3 stable build1-876 with no issues, running rock solid and looks and feels great.
I've tried "updating" to the SlimBean 4.3 stable build2, CarbonRom nightlies, and the new DanKang's stable slim + optimizations with success...but I get random reboots on all of them. I'm wondering if it has something to do with going back to the CM kernel with the other roms? The DanKang kernel uses LeanKernel, I also tried independently flashing LeanKernel on top of these other builds to no success.
Currently here's what we're looking at:
SGH-I747
Baseband: i747UCDMG2
3.2.60 slimbuild kernel from Sept 14 that shipped with build.1official-876
Have tried dirty flashes and clean flashes and open to suggestions. Currently have a Dandroid of Slim that I've been going back to between trying these different roms out.
I may just have to be happy with build 1 but I would like the bluetooth fixes and the SlimCenter keeps telling me to update lol, I'm trying!
Which bootloader and modem are you running? Have you tried a odin back to stock, reroot and install custom recovery to try again? This usually resolves these kinds of issues
in fact I'm about to it myself
I believe I'm on the "new" boot_CWM_I747UCDMG2 version and
modem_CWM_I747UCDMG2 flashed from dstruct2k's bootloader and modem threads.
I have been having the same issue on SlimBean 4.3 build 2. I have TWRP 2.6.3 and the newest official modem and bootloader. I don't have any reboot issues on build 1 either. I can try to grab a bug report next time if that will help.
I've flashed at least 7 ROMs at this point, and I have experienced nothing but boot-loops, crashes, camera issues, and random reboots. Each time that I have tried a ROM, I would have to eventually switch back to stock ROM because of the bugs. So my question to you all is, is there ANY ROM out there that has no common bugs like wifi connectivity issues, gps issues, boot loops, camera issues, etc.? I really want to find a stable rom for this phone because the stock rom is unbearably laggy and I know that this phone can be a lot faster than it is acting.
Thank you so much for at least reading this, and if you can give me an extremely stable rom, then I would be very grateful
Using cm12.1 March nightly
Hello, I have recently got this phone and mine is a d2tmo, so I searched many roms and checked out their comments section, but couldn't find any official cm12.1 topics. But did find CM12.1 Rom in the official website.
download.cyanogenmod.com/?device=d2tmo&type=nightly
have been running this rom from past 1 week, I think the battery is not good enough, but overall other issues dont seem to be popping around so freuently. Yes, I recommend it as a daily driver.
P.S: just today, CM13 Nightly has been uploaded, might not be the daily driver, but happy that there's Marshmallow for this 4 year old phone.
I've been using Slimkat 9.0 (KitKat 4.4.4) for over a year now. Fast, stable, bugsfree, minimalistic, easy on battery (24hr+ on 4yr old battery!) & efficient. http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte -- try it u will love it
CyanogenMod 12.1 it's work pretty well no crashing no hung camera work fine every thing work good like offical software
you need A Gapps 5.1 (ARM micro best Choose) you can download from here :
Gapps: http://opengapps.org
cyanogenmod 12.1 ( Lolipop 5.1.1) stable : https://download.cyanogenmod.org/get/jenkins/135162/cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip
Or you can download Nightly cyanogenmod 13 but is not stable : https://download.cyanogenmod.org/?device=d2tmo&type=nightly
ahmedzetm said:
CyanogenMod 12.1 it's work pretty well no crashing no hung camera work fine every thing work good like offical software
you need A Gapps 5.1 (ARM micro best Choose) you can download from here :
Gapps: http://opengapps.org
cyanogenmod 12.1 ( Lolipop 5.1.1) stable : https://download.cyanogenmod.org/get/jenkins/135162/cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip
Or you can download Nightly cyanogenmod 13 but is not stable : https://download.cyanogenmod.org/?device=d2tmo&type=nightly
Click to expand...
Click to collapse
Been using cm12.1 nightly for last 4 months slight problems with bluetooth but dont think its the rom.
I use built in updater today and did not notice that it was cm13. system went into Update google services loop so I flashed gapps you suggested but was still unable to boot successfully .
Any thoughts? I do have nadroid backup so not urgent.
bkwas said:
Been using cm12.1 nightly for last 4 months slight problems with bluetooth but dont think its the rom.
I use built in updater today and did not notice that it was cm13. system went into Update google services loop so I flashed gapps you suggested but was still unable to boot successfully .
Any thoughts? I do have nadroid backup so not urgent.
Click to expand...
Click to collapse
I don "t think so dirty flash work
try fully wipe
and try Gapps arm micro 6.0
Finally it something that works
ahmedzetm said:
I don "t think so dirty flash work
try fully wipe
and try Gapps arm micro 6.0
Click to expand...
Click to collapse
I had been dirty flashing (without really knowing what that is) the first android 6.0 rom for the S3 and it was going swell til they switched to the cyanogen nightly and everything broke on me, random restarts, Snapchat front camera never worked. But thank you for the recommendation, I flashed it (clean flash this time) and everything works and it's my daily driver now
On my M8, I'm running the ancient CM12.1 snapshot from November 2015. I've made the decision to update to the latest CM13 nightlies but I wanted to ask about their stability and any problems I will face. Thanks for your help!
I am using CM13 now more than half a year. Throughout this period, I encountered lots of great versions and only a few with noticeable bugs. Unfortunately my device sometimes crashes and restarts (on a daily basis) - I had this issue with almost every version of CM13, so maybe it is my fault and I should do a clean flash.
You dirty flashed from 12.1?
v1n0dhn said:
You dirty flashed from 12.1?
Click to expand...
Click to collapse
I would suggest always doing a clean flash from major version changes (such as CM12 to 13).
A dirty flash may work (don't recall if its a possibility or not going CM12.1>CM13). But if you have any issues, its probably due to migrating the data, and you should clean flash.
Not sure about the CM threads on the M8, but for my other device (Samsung Tab Pro 8.4), the thread says to not even bother posting a bug report if you dirty flashed (which I tend to agree with).