Database Info

[Q] Which ROM for a stable flash/torch app?

I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?

tmar89 said:
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
Click to expand...
Click to collapse
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.

anactoraaron said:
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
Click to expand...
Click to collapse
No, I mean with the aftermarket ROMs, do any others besides CM 10 have issues with the flash or toggle? I have no problems with the stock Blaze 4G torch

I'm on the latest CM10 Nightly and the included Torch works fine.

LBN1 said:
I'm on the latest CM10 Nightly and the included Torch works fine.
Click to expand...
Click to collapse
Thanks, I'm going to try the stable CM10

tmar89 said:
Thanks, I'm going to try the stable CM10
Click to expand...
Click to collapse
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.

anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
dammit.. and I just flashed and loaded my apps and settings..

anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
Why do you say that the stable build isn't that stable? I've been running it and it works fine for me. It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.

keiichidono said:
It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
Click to expand...
Click to collapse
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.

anactoraaron said:
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
Click to expand...
Click to collapse
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?

keiichidono said:
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
Click to expand...
Click to collapse
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.

anactoraaron said:
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
Click to expand...
Click to collapse
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?

keiichidono said:
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
Click to expand...
Click to collapse
Racings unofficial AOKP + lightning zap = WIN
Snappy snappy, stable(no reboots period), best battery life for any jelly bean ROM I've tried, and the built-in toggle torch works perfectly.
just my 2 cents
Sent from my AOKP Blaze

[Q] TF101 SODs with no-name CM nightly builds

I've installed the CM no-name nightly builds ROM by josteink from this thread around April 25th.
For a few days, everything worked beautifully, but after that, every time the tablet goes to sleep it won't wake back up. Every single time.
I've tried both the standard and the linaro version,changed the OC settings, upgraded to every new build, even uninstalled any app installed after that date, it still won't wake up.
Has anybody experienced this? How can I troubleshoot it?

I have the same problem, did the same steps to no avail. The ROM is awesome but I get SODs all the time. Even with a clean install and no messing around. The EOS one also has the same problem. The most stable one is the revolution HD.

gongolino said:
I've installed the CM no-name nightly builds ROM by josteink from this thread around April 25th.
For a few days, everything worked beautifully, but after that, every time the tablet goes to sleep it won't wake back up. Every single time.
I've tried both the standard and the linaro version,changed the OC settings, upgraded to every new build, even uninstalled any app installed after that date, it still won't wake up.
Has anybody experienced this? How can I troubleshoot it?
Click to expand...
Click to collapse
Might just be your tablet doesn't like something, I assume you've flashed the Kat kernel too though right? Without that I doubt everything will work properly.
I've never had a RR on EOS or Noname yet, and only 1 SOD which was largely my fault.

I am getting sod's on mine also with EOS build 116 and KK 103. I may have to jump back to build 113 or just before that. Cleared cache/system/davalik with same issues on newest current build with dock. Team EOS Rocks but having some issues as of late. I have no experience with joesteinks roms but what gapps you running?

I have the same problem with this Rom. Many SOD overall days.
Now install EOS and no problems with SOD. But i can't use opendroid with this rom.
What is the problem with noname rom?
No solution for this terrible SOD?
Thanks for you feedback.

I got a very stable no name build. 2013-06-24 standard Using interactive governor, with min 456mhz and max 1400mhz. IO scheduler row.

The new katkiss 4.3 ROM is great. I recommend everyone d to try it.
http://forum.xda-developers.com/showthread.php?t=2392087

Any Katkiss fans?

CROMI-X vs. CM11 vs. Omni Rom vs CMB vs PA vs PAC

CROMI-X 5.2.4 vs Cyanogen Mod 11 nightlies vs Omni Rom 4.4.2 vs CMB beta vs Paranoid Android 3.6 vs PAC- Man 3.99
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

I'm sticking with Omni. Smoothest and kitkat. Tried cm11 and cromi-x 5.2 with various kernels
Sent from my ASUS TF700T running OmniROM on Kit Kat!

CalPolyRock said:
I'm sticking with Omni. Smoothest and kitkat. Tried cm11 and cromi-x 5.2 with various kernels
Sent from my ASUS TF700T running OmniROM on Kit Kat!
Click to expand...
Click to collapse
Do you have any benchmarks?

Mackis said:
Do you have any benchmarks?
Click to expand...
Click to collapse
I used to play with benchmarks, trying out Hunds' & _that's various kernels. But, as most people say, benchmarks don't matter in the long run.
I used to match some of the same benchmarks posted in those threads, but things would still feel slugglish over time or during transitions.
I don't want to wait a few seconds for my keyboard to pop up every time, of for me to switch back to the home screen.
So for me, I want a tablet (and phone) that I don't have to reboot every day. I want it to wake up instantly. Keyboard pop up instantly. Multitask smoothly.
CM11 & Omni seem to do that, while Cromi-X seems to lag no matter that I try or whatever sbdags & co do to tweak the hell out of 4.2.x. Sure, a the IO lag has a lot to do with it, and if I'm downloading a big file or have something installing in the background I will always have lag with this tablet.
But, for now, I'm on Omni and pretty happy. If not, I'd say CM11 is very smooth too.

deadlocked007 said:
So it's just me who finds omni rom extremely laggy? What kernel and mods and stuff are you using???
Click to expand...
Click to collapse
I have found all the cm11 based ROMs very laggy so far. They don't seem to be optimised for the tf700t yet. Maybe need a bit more time?
---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------
CalPolyRock said:
I used to play with benchmarks, trying out Hunds' & _that's various kernels. But, as most people say, benchmarks don't matter in the long run.
I used to match some of the same benchmarks posted in those threads, but things would still feel slugglish over time or during transitions.
I don't want to wait a few seconds for my keyboard to pop up every time, of for me to switch back to the home screen.
So for me, I want a tablet (and phone) that I don't have to reboot every day. I want it to wake up instantly. Keyboard pop up instantly. Multitask smoothly.
CM11 & Omni seem to do that, while Cromi-X seems to lag no matter that I try or whatever sbdags & co do to tweak the hell out of 4.2.x. Sure, a the IO lag has a lot to do with it, and if I'm downloading a big file or have something installing in the background I will always have lag with this tablet.
But, for now, I'm on Omni and pretty happy. If not, I'd say CM11 is very smooth too.
Click to expand...
Click to collapse
I've made a lot of improvements in CROMi-X 5.3 to combat the lag when something is using the disk in the background. It's a lot better now than it was on the last few versions.

There's never going to be a definite answer on this. How do you define "lag"?
What are you looking for in your rom?
How do you use your tablet?
You just have to try them all and decide for yourself...
I'm always like: ???????????? when someone reports lag on CROMi-X. I just don't get it, because I don't have it.....
I tried CM 10.2 and CM 11 on this tablet and I found them to be slower and (to me more importantly) a hell of a lot buggier than CROMi-X!
But again: I guess not only beauty but also lag and performance is in the eye of the beholder....

sbdags said:
I have found all the cm11 based ROMs very laggy so far. They don't seem to be optimised for the tf700t yet. Maybe need a bit more time?
---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------
I've made a lot of improvements in CROMi-X 5.3 to combat the lag when something is using the disk in the background. It's a lot better now than it was on the last few versions.
Click to expand...
Click to collapse
@sbdags did an amazing job with 4.2. So did hunds and _that. No disrespect. Just after running 4.2 for a long time, I'd like to run something newer as long as it's responsive. I don't care about benchmarks as I said before.
I'm hoping sbdags have the chance to do the same with 4.3 or 4.4 if Asus releases it for the 700, or 701 and then back port to the 700.
Sent from my SGH-M919 using Tapatalk

CalPolyRock said:
@sbdags did an amazing job with 4.2. So did hunds and _that. No disrespect. Just after running 4.2 for a long time, I'd like to run something newer as long as it's responsive. I don't care about benchmarks as I said before.
I'm hoping sbdags have the chance to do the same with 4.3 or 4.4 if Asus releases it for the 700, or 701 and then back port to the 700.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Newer and frankenrom'd doesn't translate into "better" IMHO.. But everybody rolls differently...
sbdags released his beta for the TF701 on 4.3 already. There won't be much porting back though - Tegra4 framework is just too different. But I bet the roms for the Tf701 will be even better because he has so much experience with tweaking the Asus roms

berndblb said:
There's never going to be a definite answer on this. How do you define "lag"?
What are you looking for in your rom?
How do you use your tablet?
You just have to try them all and decide for yourself...
I'm always like: ???????????? when someone reports lag on CROMi-X. I just don't get it, because I don't have it.....
I tried CM 10.2 and CM 11 on this tablet and I found them to be slower and (to me more importantly) a hell of a lot buggier than CROMi-X!
But again: I guess not only beauty but also lag and performance is in the eye of the beholder....
Click to expand...
Click to collapse
Have you watched the Google's 2012 I/O keynote where Google introduced Android 4.1 and Project Butter? Google has clearly defined what they perceive as lag in Android as situations where the UI's frame rate drops below 60 fps and you can clearly see stutter in animation, which is why Google also introduced Systrace to profile app performance. If the frame rate drops significantly below 60 fps (which I always encounter in the stock app drawer), you will see things like transition effect stutters when swiping between pages or the laggy fly-in effect when you open the app drawer. If you have a Nexus 10 to compare, the difference in terms of frame rate is so apparent that it is almost impossible not to notice. If someone had a high-end camera that can capture 60 fps or 120fps videos like the one Google used to demo Android 4.1, we could easily capture all these instances of lags on videos and had a more scientific discussion. To me, the Nexus 10 is the gold standard of 10-inch tablet performance and I have yet to see another non-Nexus 10-inch tablet (besides the iPad, if I may) that deliver the same level of performance, regardless of ROMs being used.
Moreover, not to discount the work that the xda community has put into improving performance, there are simply too many ways that you can make an Android device drop frames here and there. Even powerful devices like the Note 3 can fail to deliver constant 60 fps UI frame rate. I'm sure with the right combination of widgets and apps, you can also make the Nexus 10 stutter. Or simply, you can just fill up 90% of the internal storage and watch how the performance degrades. To be honest, it is much harder to believe that there is no lag at all, regardless of devices and ROMs that you use. Even Google said that Project Butter is not perfect and still an ongoing effort.
Lastly, workload can also dramatically affect performance and make instances of lags more noticeable, so your usage pattern is a factor. Personally, even on CROMI-X, my tablet could become really laggy if I used it for my work like the other day, even with only 3 apps in my recent apps list: Adobe Reader to read a big pdf file (a 100-page annual report of a company, with a lot of text and images), the stock Browser to research relevant information with around 10 tabs, one being facebook desktop site (seriously, the facebook desktop site is really terrible on Android), Merriam Webster Dictionary app to look up certain words, all in landscape mode. In that scenario, my tf700 performed just like a big slide show.

+1 all the way.
BUT reg the Nexus: No external storage - no deal. For me......

berndblb said:
+1 all the way.
BUT reg the Nexus: No external storage - no deal. For me......
Click to expand...
Click to collapse
I am in the same boat as you, which is why I am very excited to see more of those Google Play Edition devices. I highly doubt that there will ever be a Google Play Edition Transformer tablet, but it would be fantastic to have one.

CMB
I switched from CROMi-X to CMB (http://forum.xda-developers.com/showthread.php?t=2577165) a couple of days ago and I am really happy with it.
@lj50036 has done a great job and so far I haven't had any issues/sluggishness although it is based off CM11. The dock works like a charm as well
The only thing that did not work was being able to use ART on CMB for me.

[Q] CM 11 with ION by sultanxda stability problems

installed newest
(date 27.1.2014 with GAPPS modular mini from: http://forum.xda-developers.com/showthread.php?t=2530073)
did full wipe (factory reset, system, cache) as in info
have some major problems with stability, looks like system degrades quickly after leaving screen off mode
After restart I can set up everything fine, can use network, launch apps, change system settings etc
but after first turning off and turning on lock screen starts to show first problems, dots (I'm using pattern unlock) sometimes start to activate on their own, not always but sometimes this happens, but I'm still able to logon...
after second 'screen off' and 'screen on' I'm having big problems trying to unlock screen - sometime dot's don't react to touches, sometimes they do not end connecting after taking away finger from screen...
after third off/on I'm unable to pass unlock screen - it becomes unresponsive, dots start to connect randomly, sometime even 'emergency calls' gets activated...
what can cause this? full phone restart appears to fix problems for short time, but after few off/on have problems agains...
this did not happen in builds from few months ago
tried to set higher min cpu frequency to 384MHz but that doesn't help
other things that I chaged are:
- cpu governor -> badass
- i/o -> noop
- active 'allow purging of assets'
anyone got ideas what could cause this? and how to fix
phone:
htc sensation xe, unlocked
hboot 1.29, radio 11.24a.3504.31_m
can provide other info if needed

It's easy to be fixed, install stock rom.

nlooooo said:
It's easy to be fixed, install stock rom.
Click to expand...
Click to collapse
thank you, very helpful

What firmware are you on? Did you experience any of these problems on any other rom?
You say the dots connect themselves. As if the touchscreen is used? Sounds somehow like a broken digitizer.

zodi79 said:
thank you, very helpful
Click to expand...
Click to collapse
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.

nlooooo said:
Do you know how many threads like yours have been opened recently? Is it that hard to search and why do you expect flawless rom?
When will people learn, it's unofficial, it's custom, it's a new android version tied to the old hardware with the old drivers, it will, probably never be perfect.
Click to expand...
Click to collapse
I must have missed all of these threads. There were some threads about cm11 but they had other issues.

This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Sent from my Nexus 5 using xda app-developers app

Sultanxda said:
This phone is 3 years old and you're using Badass. Since you want more performance, set your CPU governor to Ondemand and set I/O scheduler to BFQ or SIO.
Click to expand...
Click to collapse
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.

zodi79 said:
ok, will try
atm had to move back to previous cm 10.1 based on 4.2.2 prepared few months ago, it appears to work much better but still have some stability issues. Doesn't look like problem with touch screen as most (now like 97%) it works flawlessly... yeah, not 100% so it could be hardware problem, just that didn't happen before
and yeah, I know these are unstable, beta like, etc roms - I like to test new features on my sens xe and one prepared by sultanxda is atm the best for me, keep up great work and thank you for time spent working on this rom.
Click to expand...
Click to collapse
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.

first of all - sorry for misinformation but I found cause of my problems with interface... looks like minimal amount of water must have got under the cover when I few days ago applied new screen protection, yesterday I got this idea of what could cause this sudden problems... few hours phone stayed on the room heater (not too hot ofc) and touch screen problems are gone! yeah, tbh I love this phone and was very angry thinking I'd have to replace it, now I don't have to
back to rom - atm back to your (sultan) rom based on CM 11 with update from 29.1.2014, it has some small problems but I like to test new features
problems I've found so far:
- less responsive and smooth
- launcher3 doesn't allow to create new home screens on the left, had to create new to the right then make some rearangments before I got things right
- some widget resize problems under launcher3
- other small problems all I can live with
but I like more available memory and better battery life, going to test ART soon
and it is good that messanging is back, hangouts is just... not for me

Why cant i find my phone contacts on SIM ??? Its say no contacts found? When i import some numbers from vCard from SD why cant i move them to SIM???

cm10.2 - cm11
Sultanxda said:
Why not try my CM10.2 ROM? CM10.2 is far more stable than CM11, and, personally, CM10.2 feels smoother than CM11.
Click to expand...
Click to collapse
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.

romadd said:
funny ... i tried a lot of rom and i dont have real problem except with your latest rom ([ROM][Android 4.3.1][Camera works] CM10.2 with ION [Jan 30, 2014]) : lags, reboot , ...
Now i use your latest rom on CM11 ([ROM][Android 4.4.2][Camera works] CM11 with ION [Jan 29, 2014]), realy good no problem, thank's for all.
Click to expand...
Click to collapse
I tested it for 3 hours and it was working well

Sultanxda said:
I tested it for 3 hours and it was working well
Click to expand...
Click to collapse
I had fresh install, but configured cpu clock speed 1674 mhz (maybe the problem ?)
And i had the same symptom describe by Firehawk989 http://forum.xda-developers.com/showpost.php?p=49938883&postcount=3341
Any way i run already with your CM11 and it seem more stable for me except a little problem
http://forum.xda-developers.com/showpost.php?p=49353701&postcount=1
This is another story

What's the best ROM to speed up an ailing Galaxy Tab 2??

I bought my dad a Galaxy Tab 2 a few years ago and although he barely uses it, it seems to have slowed to a crawl even whilst using it's most basic functions! (I've tried a full factory reset and it's still ridiculously slow - 20+ seconds just to load up the Play Store for example!)
Is there a generally regarded "fastest" (lightweight?) custom ROM out there that I could put on for him to extend the usability a bit?
Thanks...

slimkat slimlp builds are one of the most lightest and speed efficient roms.
Aosp builds are the minimalist builds, pure stock android experience.
Omni builds are good too, with little more features and oc kernel.
Generally CyanogenMod would get the latest updates(with bugs fixes and improvements) and then other rom will follow.
Then there is candy rom with most features than others.
Marshmallow builds are still in development.
Lollipop builds are near stable now.
Kitkat builds won't get more stability than it has already got.
Choose according to your dad requirements.

Thanks for the reply!
I went with Cyanogenmod in the end (10.1.3 just because it looked to be the most recent that was "stable" rather than "nightly" - not sure what the difference is!?!?)
Result - amazing!!!!!
The difference in speed is like night and day!!
Thanks again...

stevep94 said:
Thanks for the reply!
I went with Cyanogenmod in the end (10.1.3 just because it looked to be the most recent that was "stable" rather than "nightly" - not sure what the difference is!?!?)
Result - amazing!!!!!
The difference in speed is like night and day!!
Thanks again...
Click to expand...
Click to collapse
Thanks for the recommendation. Even I'm thinking of downgrading the device from cm13. It simply isn't worth the lag.
I might try some of the other lighter builds mentioned in the previous post first though.
What kind of benchmark tests does one run to know which rom is optimized for a device?
Sent from my Moto E using XDA-Developers mobile app

Try dhollmen 4.4.4 rom
It has got lightening speed