Database Users

Done with Bonsai, what ROM is considered the next best?

I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie

Syndicate is THE best imo
PS: make sure to enable journaling right after flashing it.

Best ROM
As I'm sure you've read before, every phone acts differently. Most people seem to gravitate towards ACS or Bonsai. For me, ACS was buggy and Bonsai was, while extremely fast, the worst on battery life.
I personally have had the most luck with the current MidNight ROM and more recently Simply AOSP. Even though there seem to be hundreds of threads on tweaks and hacks, most don't seem to take well to my phone. The big ones (No CIQ, for example) seem to be included in about everything now.
Give 'em a go, see what works. I can safely recommend the two above.

Yup id go with Srf 1.1.1 (1.11?) Best imo
Sent from my SPH-D700

Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Bonsai 4.1.1
SRF 1.1.1
Midnight series
Frankenstein
Urban Fury
ACE 2.0
Supernova 3
All are great ROMs
Not sure how to get the other CWM back. I like Bonsai's recovery But, if you use Quickboot and boot into recovery it takes you to CWM and not the Bonsai recovery.
Maybe you got a bad download of the Bonsai 4.1.1? Did you try to reflash it after all the FCs? Did you post in the Bonsai forum or Bonsai thread here?
You could always Odin back to stock and just start fresh that way also. Then just root with One click and get your CWM that way.
2 rules I follow about ROMs
1. No ETAs lol
2. YMMV
Everything with our phones...is phone dependent, they are completely different from the next Epic
Edit:
Sorry to the Devs that I didnt list ROMs from! These were the ones that were just on my sd card right now!

Sturmie said:
I have been running Bonsai 3.0.1 on my wife's Epic for a while now and TRIED to update to 4.0.x a while back, but got a TON of FCs and lock-ups. So, the other day, I saw the official 4.1.1 ROM was out and tried that...even did the suggested "factory reset" within Android. Well, Bonsai overwrote CWM with that new custom recovery they have and I'm still getting FCs and lock-ups. Went back to 3.0.1, but was looking to get a new/updated ROM put on...what is generally considered the best ROM out there for the Epic? Also, what is the best way to get ClockWork recovery back?
I run Cyanogen 7 on my EVO and love it, but noticed that CM7 for the Epic is still in beta with a lot of key features (camera) not working yet.
I know that no one wants to read another "what is the best ROM" thread, but I'd really appreciate some help here...thanks!
Sturmie
Click to expand...
Click to collapse
Use Odin Flash back to stock ECO5 rom.
You can then Flash back to clockwork using odin following the thread instructions for the specific rom you want to work with.
I like ACS Swiss Cheese it works great as long as when you are in a stock rom you get a lock for the gps before installing swiss cheese. There are several threads that explain load order for it to install correctly. I have had it running for near month now with no problems.

Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.

Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
You should use Titanium Back and backup your information using nanroid to avoid FC errors. If just remember there newest Rom is only compatible with there own kernel. If you try another Kernel with it your won't get the stellar battery life. I am using a combination of Bonsai and anonymous gingerbread and it is working out well with me. I ran Bonsai and back up all my information on Bonsai then I flashed gingerbread and recovered the Bonsai Rom on top of it.

Sturmie said:
Thanks for the replies...I've been looking at Syndicate's ROM...seems to have a lot of people liking it at the moment.
As for Bonsai, I MAY give 4.1.1 another shot since I've been using MyBackup Pro to restore all of her APK+APP DATA, which may have caused some problems. I did have 4.1.1 working when I flashed it OVER top of 3.0.1, but the battery life was horrible...I'm talking 1/2 of what it was with 3.0.1. So, I tried a clean wipe/reset and gave 4.1.1 another shot...that's when I had all the FCs and freezes.
Click to expand...
Click to collapse
I would definitely go e it another shot. Try using the enable_journal zip in the Bonsai Downloads section first, then flash the ROM. That should help you avoid the FC issues until you get the installation errors ironed out.
Sent from my SPH-D700 using Tapatalk

I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.

lattiboy said:
I had the same issues with my first Bonsai install, but then I ODINd back to STOCK EB13, used Bonsai One click root, wiped 3x, and installed. It is now totally flawless. Give that a shot, it only takes about 30 minutes total.
Click to expand...
Click to collapse
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.

This. Path of least resistance for Bonsai is definitely ODIN'ing EB13. And 4.1.1 has great battery life in my experience.
Atm, the biggest deciding factor on ROM's to use has to be whether you want to stay on Froyo or do you want to be on Gingerbread.
hayzooos said:
From what I've read, coming from EB13 is the best way to go. Even if you Odin EC05, it still seems to have problems. Their dev, Randy, knows the ins and outs of why, so I would suggest Odining EB13, rooting with with their unlocker, then flashing their newest ROM.
I personally use SRF 1.1.1 w/ the Genocide 1.0 kernel, and don't have any major complaints outside bluetooth being wonky after each restart. For me, SRF is stable enough where I don't need to reboot but once a week, if that, unless I'm changing things around.
Click to expand...
Click to collapse

I would also suggest using Titanium Backup and MyBackUp root sparingly. Not that they don't work but it seems many users troubles always start with restoring old data from Titanium/MBR. I have also found SMS Backup & Restore to be a good option for those wanting to save and restore your txts over using TB/MBR which seems to foul things up when restoring txts.

Don't install any data from previous roms unless it was done by Bonsai during the install. Totally avoid any system data. Old saying: garbage in garbage out...
Sent from Bonsai 7.1.1.1

Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!

digiblur said:
Looks like I'm not the only one that continues to have issues with Bonsai... everytime I flash Bonsai updates my phone goes wonky and I have to start over again with a factory reset.
After factory resetting to fix my microphone while in a call...now my Slacker will not advance to the next song by itself.
Really looking hard at SRF at this point!
Click to expand...
Click to collapse
You didn't need to reflash to fix the mic, it's a setting in VooDoo.

try EC05 Plus out, quick stable, and good on battery life...

I use Bonsai /w journaling. It is the only ROM that has stayed stable for weeks. Others go bonkers at some point especially w/o jounaling. No offense to ACS but I have yet to have one of their ROMs start and stay stable. Baked stuff is 2nd closest.

Acs srf 1.1.1
Sent from my SPH-D700 using XDA Premium App

I have been on Urban Fury since launch day (March 29 I think) You get 1 FC on the wallpaper app on install and that's it. I have been beta testing themes and kernels and have NEVER had data corruption or force closes other than the one on boot. It comes with Genocide kernel and Wifi Tether 3 pre 14 works great. That being said, all of the ROMs are good. Its just a matter of what you and your phone like the best
Sent from my SPH-D700 using XDA Premium App

Sleep of Death (SOD)

Hello All,
Here's my 2 cents on SODs and killing of it (even if only temporary)
I am currently on @Anti's Asylum ROM. Previous to that, I was on CM9 ver 7.
Had been plagues by SODs and had almost given up and was about to flash Samsung Stock ROM.
I was on Stunner previous to CM9. Once I was on CM9 and loving it, I came across this nasty looking creature called SOD for the first time in my life.
Threads suggested I should flash GB ROM back and do a clean install. @AndroidIndian was kind enough to walk me through all the steps and I did everything I had to. Then flashed CM9 back. Guess what, those SODDIN SODs were still there.
So, apologetically, I posted that I had to betray my brethren here and go back to Samsung Stock.
Then, @Tremorone PMed me to try @Anti's asylum, built on CM9 code. He said since I was trying to hold on to an AOSP thing, I should try it at leas once. In one last ditch effort, I did the right thing - flashed Asylum ROM over the CM9 ver 7.
Now, the interesting bit:
Initially, I was on XXLPT Modem (the latest one). Overnight, there was no SOD and I was a happy bunny. Next morning I got a long call (about 20 mins). Once the call was over, SOD !!!! Figured it HAD to be a modem.
So, I did the following:
1) I flashed LP5 Modem through Mobile Odin. SODs were less but the lockscreen froze up once.
2) Being the impatient prick that I am, after a while I flashed LB2 Modem via CWM Recovery.
SODs has drastically gone down on that. No SODs in the last 7 hours as a matter of fact.
I don't know if it's the ROM, LB2 via CWM or the combination of Steps 1 and 2 above, but seems like it has more or less solved the problem. Of course, it is still early days and I need to observe for a couple days more.
To everyone suffering at the hands of the SOD demon, I would suggest why not try Step 1, let the ROM settle, and then proceed with Step 2 (as above).
There's no harm in trying, right? And if it solves it, nothing more beautiful than it. Then you can go CM flash happy as soon as new builds start being avaialble.
Thanks to @Abhisahara for helping me keep the faith.
All the best SODding off the SOD.
Cheers.

Well, I think I'm a lucky guy. I had never one SOD since I own a note. I have nearly the same flashing history like you. Flashed also many modems . I can't imagine why the devices are so different. The same thing I noticed with my old HD2. I hope you will find the reason/way to solve this f******* SOD issue
Gesendet von meinem GT-N7000 mit Tapatalk 2

I'm the same after flashing cm9 I had one screen of death on the lb2 modem.. I flashed lp6 just because.. After that I used cm9 for a week with not one sod before flashing ics official
Sent from my superior Nokia 3210 using XDA Premium Plus Legacy Edition

My SODs stopped after I flashed .19 Stunner with LP5 kernel and LP6 modem. I haven't had one since then (**knock on wood**). I am on stock ICS now with the new modem, not CF-root kernel though. Strange how variables are always so different though.

Hmm,
I've flashed several modems since being plagued by the SODs. I'm on CM9 nightlies and am using LP6 from LB2. The SODs have gone down with the newer modem since I was getting 5 or 6 a day! But, I still get at least one or two a day now. I'll try with the latest LPT or LR1 and see if these make any improvements.
They are a bit of a mystery though since there never seems to be any consistency to what is actually causing the sleeps.

I always flashed modems through Mobile Odin and flashed every single modem available for note, but still had SODs.
So I wiped everything and reinstalled the ROM and did not restore data and I did not have SOD.
I have data backed up on Google, it restored my apps (through play store), contacts and wifi access points, so I was kind of OK, since I did not lose out much. But thats just me!

I tried LB2 ,LA4 ,LPY Modems ,and had one SOD in two weeks time while on CM9 build#3 and LA4 modem.
LB2 modem iks very good and I'm using it right now with the latest nightly with no SODs what so ever.

I've flashed modems using CWM and still get the SODs. I'm beginning to think these are not directly related to the modem. I did a clean install of GB from Imilka's CM9 (Chinese leak) then Chainfire's rooted kernal and then on to the CM9 nightly. I didn't copy any system data but I did use TB to resinstall my apps (against advice I know). I had no SODs on Imilka's rom but they appeared following install of CM9 nightly.
I guess I'll try a clean install again but I hate having reconfig my phone everytime since I change so many things via Apex, Minimalistic Text and Folder Organiser apps.
I'm hoping though that we'll get to a nice update on CM9 that will resolve the problem eventually.

I think SOD is WIFI related (not just modem). Since upgrading to ICS, different ROMs, I had many of them on all ROMs and modems, until I set my WIFI to never sleep and disabled any battery saver trying to make it sleep when screen off. That solved it for me. Then started testing battery savers, most of them brought SOD again, until I tried battery defender, which seem to work without SODs.

Had lots of SODs in the past on CM9, none for 3 days since I installed nightly 20120515 and LPT modem. Fingers crossed

[CM11] Stable to nightly

I have just installed my first ROM on my Nexus 4 being CyanogenMod 11 (the stable release).
The thing is, in "about phone" I only have "system updates". While a mate of mine has a lot of nightlies showing up there. For me it just shows a normal system update as it was on a normal unrooted phone.
----
My question is: is there a way to go from this stable release to a nightly release so that I'm able to keep updating to nightlies without erasing everything and configuring all over? (like just flash a nightly and it's fixed)
In other words, can I flash the latest nightly over my stable release and continue there without wiping anything?
Any advice is helpful!

Foxnov1990 said:
I have just installed my first ROM on my Nexus 4 being CyanogenMod 11 (the stable release).
The thing is, in "about phone" I only have "system updates". While a mate of mine has a lot of nightlies showing up there. For me it just shows a normal system update as it was on a normal unrooted phone.
----
My question is: is there a way to go from this stable release to a nightly release so that I'm able to keep updating to nightlies without erasing everything and configuring all over? (like just flash a nightly and it's fixed)
In other words, can I flash the latest nightly over my stable release and continue there without wiping anything?
Any advice is helpful!
Click to expand...
Click to collapse
Yes, just flash over it. (dirty flashing is what they call it) I would make a nandroid backup first, just in case.
Sent with my Nexus® 10 minus 3

Berrydroidcafe said:
Yes, just flash over it. (dirty flashing is what they call it) I would make a nandroid backup first, just in case.
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Was kinda scared to do it because I read several contradicting statements.
So thank you for pushing me into that direction!
I did it and now not only the nightly is on there but also the option to update to newer nightlies. Thank you!

Foxnov1990 said:
Was kinda scared to do it because I read several contradicting statements.
So thank you for pushing me into that direction!
I did it and now not only the nightly is on there but also the option to update to newer nightlies. Thank you!
Click to expand...
Click to collapse
No problem. Just a side note, it's usually a good idea to wipe cache and dalvik before flashing the new nightly. Doing a backup also. That new nightly sometime breaks things.
Sent with my Nexus® 10 minus 3

Berrydroidcafe said:
No problem. Just a side note, it's usually a good idea to wipe cache and dalvik before flashing the new nightly. Doing a backup also. That new nightly sometime breaks things.
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
I'll surely keep that in mind for the next time I'm updating to a newer release.
Because ye, thats the risk of sticking to nightlies though. But I've "broken" my nexus so many times that I'm sure I can handle it.
Just for this, after recovering the afternoon I had no intention of doing that again for this

CM11 M4 snapshot.

Anyone try this yet? Impressions?
Sent from my Nook HD CM11.

I tried it last night. I flashed over the 3-6 nightly and had many force closes and network issues. I did not try and do a clean flash.

On an attempt to just hit update and go it got stuck in a reboot loop. Attempting a clean install results in network seen but not connecting. Rolling back to 10.1.3.
Edit now it seems no matter what version I try installing networking is hosed. I feel kinda stupid here guys.
Edit: Had to go through reflashing cwm-5 the m4 rom, gapps, and all that as if I wee going from 10.2 rather than update 'just working' Most annoyed.

I should have left well enough lone. I had installed the 3/8 nightly and it was working great.
Then I saw the 3/8 snapshot and decided to install it.
The Snapshot seems to be no good. It throws errors when logging in and I also lost WiFi.
I have re-installed the 3/8 Nightly and am a happy camper again.

In fairness leaving well enough alone would have left you with B&N's stock environment. We tinker, it's what we do.

I gave this a shot myself and got a bunch of fc's. Went back to the last nightly. From what I heard the M should be more stable so much for that.
Sent from my SCH-I545 using xda app-developers app

I updated from 01/18 to the M4 and it has been very stable.
See http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for important considerations in switching between the two branches snapshot/stable and nightlies of CM11. The blog explains why going from some of the most recent nightlies to M4 might be a downgrade and as such can cause the problems reported above.

I don't know if I just have bad luck (or a bad device), but I haven't had a single official CM11 build without random reboots and screen flashing / flickering. Anyone else here?

You should not flash the m4 if your nightly is newer than 20140308 otherwise you will get FC's.

adwait.bhandari said:
You should not flash the m4 if your nightly is newer than 20140308 otherwise you will get FC's.
Click to expand...
Click to collapse
Not true.
M4 was taken from the nightly branch on 2/28. If you have flashed a nightly to your device newer than 2/28, you will be downgrading if you flash M4 afterwards - resulting in unpredictable results.
Based on this thread, the results will be WiFi issues and possible boot issues.
If you want to switch to the monthly builds, do not take anymore nightly builds, and wait until April to take the M5. If you want to stick with the nightly s, then do not flash the monthly's.

pyrofool said:
I tried it last night. I flashed over the 3-6 nightly and had many force closes and network issues. I did not try and do a clean flash.
Click to expand...
Click to collapse
need to do wipe data/factory reset and not restore the old data. otherwise, "android.process.acore stopped unexpectedly" for me.

I guess I got lucky. I dirty flashed m4 over 10.1.3 stable and everything is running perfectly. I wasn't expecting it, but m4 is much speedier than 10.1.3, only downside is battery life seems to be not as good.

Beware!
There was a post I found a while back on the official Cyanogemod site that went into details about Nightlies, Milestones, Release Candidates, and Stable Releases. What would be most important for users of CM11 at this time which was explained in the post is that you either stick with updating from nightly to nightly OR milestone to milestone. If you're on a nightly and you update to a milestone snapshot, you risk damaging and messing up the OS. Vice-versa as well and should also apply to RCs and Stables. Nightlies are bleeding edge and have the latest code while a milestone snapshot is more stable, but has older cold. So going from nightly to milestone snapshot would be one heck of a messy downgrade.
srry for dis messy post btw qq

CM11 Vs Latest CM12 Bacon Nigthly

Hey, i just want to know your opinions about why is better CM11S or why is better the latest CM12 Bacon Nightly ( cm-12-20150128-NIGHTLY-bacon)

I'm not trying to be a spoiler, but seriously, when it's so easy to do a nandroid backup and flash CM12, why not just try it? The only slight hassle is having to flash the old firmware if you decide to go back, but even that's not hard if you know how to use fasboot / recovery / flash ROMs.
And to answer your question, it's better because it's Lollipop, a step forward.
Bottom line: there is only one way for you to know.

As the above post said try it but myself i went back to cm11 as i tried every cm12 rom plus different kernals and my device would still be awake in wakelock app went back to mahdi rom with ak kernal and all good. still early stages for cm12 and cant wait to go back but will wait for a while

pro4ever said:
As the above post said try it but myself i went back to cm11 as i tried every cm12 rom plus different kernals and my device would still be awake in wakelock app went back to mahdi rom with ak kernal and all good. still early stages for cm12 and cant wait to go back but will wait for a while
Click to expand...
Click to collapse
Your problems have nothing to do with the cm12 nightlies "early stage".
Using cm12 since unofficial builds in december. There were some problems,
but not the battery life. It is the same as on cm11 for me.

Thats good news for you but since going back to cm11 my device goes deep sleep im happy

AcmE85 said:
Your problems have nothing to do with the cm12 nightlies "early stage".
Using cm12 since unofficial builds in december. There were some problems,
but not the battery life. It is the same as on cm11 for me.
Click to expand...
Click to collapse
Agreed. I had some wakelock issues in a build back in December or early January, but none since.

May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz

pro4ever said:
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
Click to expand...
Click to collapse
I use official CM12 nightlies with stock kernel and no mods. I dirty flash, but clear cache / ART cache with every nightly.

pro4ever said:
May i ask you guys acme85 and cafekampuchia what cm12 rom they have been using and kernal plz
Click to expand...
Click to collapse
Official CM12 Nightlies with stock kernel.
If you ask me ALL kernels are overrated in terms of battery life, but that is just my opinion (after some testing).
It is funny though how some users with custom kernels are undervolting and underclocking their
devices and yet never achieve the same battery life I get with all stock.
Some even claim that there device is more fluid than stock with kernel x or y. :laugh:
If you are into multirom or perhaps display color calibration then sure, a custom kernel is the way to go.
btw, I don't use greenify, I don't block play services wake permissions, I don't use the facebook app.

AcmE85 said:
Official CM12 Nightlies with stock kernel.
If you ask me ALL kernels are overrated in terms of battery life, but that is just my opinion (after some testing).
It is funny though how some users with custom kernels are undervolting and underclocking their
devices and yet never achieve the same battery life I get with all stock.
Some even claim that there device is more fluid than stock with kernel x or y. :laugh:
If you are into multirom or perhaps display color calibration then sure, a custom kernel is the way to go.
btw, I don't use greenify, I don't block play services wake permissions, I don't use the facebook app.
Click to expand...
Click to collapse
Tnx for both your replys I've always used cm 12 with custom kernels. Will try with stock and see how it goes

I reverted back to stock 44S after trying CM12 in Nov, was too unstable back then. Seems people are getting stable experience from CM12 now, think I am gonna flashing it later today
Thanks all!

I've gone from 11s to 12 to 11 again. Cm12 is stable but does have a few annoying bugs. The one that annoyed me the most was the audio buzzing bug. Many say enable the phone to always have 2 cores on, but that never fixed my issue. Buzzing always happened. Then there was the proximity issue which van be fixed by flashing a new firmware and modem but my phone doesn't take the modem. Lost lte and signal kept dropping every 3 minutes. Also had an issue when I was in a call, I often was a unable to hear the person. Only had to enable speaker and then Disable it again. That was the icing on the cake so I went back to cm11s. Now here I can say that battery life is almost identical. Just ever so slightly better on lollipop for me. The system is not as smooth specially with scrolling. I have scroll lag on instagram and Facebook again (minimal but noticeable) system, for a stock rom, isn't really too stable. Had the phone crash on me and when I turned it back on, it asked me to re set up the device but data was still in tac. So yeah. That's pretty much it.
Sent from my A0001 using Tapatalk

Have tried CM12 nightly, and back to 44s because one game that I like didn't run smooth . I think ART cause this, been trying on CM12 unofficial builds also, same result. Maybe the game hasn't updated for lollipop yet.