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

High Load in cm10 and Roms based on it?

Hello,
I have noticed, that the load* (not the CPU%) under several CM10 (or higher) based roms is very high, i.e. >2.
This is true for PACMAN, JellyBam and the CM10 nightly.
Can someone please have a check by activating the CPU-Stat-Overlay and post the line that looks like 2.7/3.0/2.0?
Is this a known problem? I once had a nightly of CM10 on the Phone, which ran very well. I do not think, that it had this problem...
I do not have this Problem with OptimusRS which is based on the Official ICS. Here, the load is lower by a factor of 10.
*in contrast to the CPU usage (%), the load also captures if the system is blocked by something other than the CPU (I/O, ...)
Greetings,
Hendrik

Mine says 1.15/1.18/2.25
Using PacMan 19.3 rom

svvv said:
Mine says 1.15/1.18/2.25
Using PacMan 19.3 rom
Click to expand...
Click to collapse
Well, that's quite high, still.
Was that after the device was ideling??
When I have not used the phone for 15 min, I get 0.02/0.02/0.02.
Your values show that your phone is really busy (values > 1 means that it is over-loaded).
Are you happy with the responsivenes of the phone?
Greetings,
Hendrik

henfri123 said:
Well, that's quite high, still.
Was that after the device was ideling??
When I have not used the phone for 15 min, I get 0.02/0.02/0.02.
Your values show that your phone is really busy (values > 1 means that it is over-loaded).
Are you happy with the responsivenes of the phone?
Greetings,
Hendrik
Click to expand...
Click to collapse
I kept my device idle for 5 mins then checked all three vr above 1. But my mobile seems to be smooth when runnning single app but while multitasking device becomes very slow.

svvv said:
I kept my device idle for 5 mins then checked all three vr above 1. But my mobile seems to be smooth when runnning single app but while multitasking device becomes very slow.
Click to expand...
Click to collapse
The first value is now, the second 5 minutes ago, the last 15 minutes ago.
So, your device/your Rom seems to have the same problem I experienced.
I am surprised, I am the first to complain?!
Greetings,
Hendrik

henfri123 said:
The first value is now, the second 5 minutes ago, the last 15 minutes ago.
So, your device/your Rom seems to have the same problem I experienced.
I am surprised, I am the first to complain?!
Greetings,
Hendrik
Click to expand...
Click to collapse
I come back to CM-Based rom today...and i noticed that in Jellybam and also Bernie's rom the CPU usage is really high...the cpu stays every time at the higher frequence and the back of the phone is really hot! I noticed this problem also with MIUI rom that are also CM Based, i need to change kernel for trying correctly Bernie rom! With Pesach kernel for CM10.1 the thing seems good..but the phone stucks ever at the minimum frequence...and it never go on deep sleep!
Is really strange! I tried bernie's also when it came out some time ago but it hadn't this problem! I think that is a recent problem!

Install wakelock to see who do that. put wifi to sleep when screen is off. Uninstall the programs that you do not need.
Take a look here
http://forum.xda-developers.com/showthread.php?p=42778421
Sent from my LG-P920 using xda app-developers app

Well, I suspect the obstacle might be the CPU driver - I don't know if LG have ever used Texas Instruments' default values or just made them up by themselves although I suspect it would be the latter since I have used Tegra 2 based phone before (hacked, of course), and it's surprisingly smooth so there may be explanation somewhere in either second-stage BIOS or in the kernel for the 3D phone and no I am not pointing the finger at any developers here as there are variables that have to be checked down.
Sent from my XT907 using xda premium

Dr. Mario said:
Well, I suspect the obstacle might be the CPU driver - I don't know if LG have ever used Texas Instruments' default values or just made them up by themselves although
Click to expand...
Click to collapse
I don't understand, what you are saying...
For me, it is not yet clear, whether this problem exists on every phone, and whether it is on every rom.
When I started using CM10, I did not have this impression. Does someone have an old version on CM10 and could check?
What about the others? What are your LOADs?
There must be more users...
Greetings,
Hendrik

CM10 only load the values which are in the kernel which you can install separately, and some kernels have better CPU values. Not to mention there is 410 MB assigned to CPU.
However in some case, BIOS is what make or break this phone (BIOS boots up first and displays red or silver LG logo depending on whether BIOS is unlocked or not, and is responsible for loading Linux kernel, thus booting Android OS up). So it's hard to say but I might want to try assemble the BIOS on my own and see if problem persists in some OS images (FYI, BIOS development is much harder than Android OS development).
Sent from my XT907 using xda premium

Hello,
I think, it is worth to go back to an older CM10 Version, because I am quite sure, that it was better there.
What really surprises me is, that I am the first and more or less only one to complain. For me, PACMAN and JellyBam were unusable, CM10 was also quite bad.
Greetings,
Hendrik

henfri123 said:
Hello,
I think, it is worth to go back to an older CM10 Version, because I am quite sure, that it was better there.
What really surprises me is, that I am the first and more or less only one to complain. For me, PACMAN and JellyBam were unusable, CM10 was also quite bad.
Greetings,
Hendrik
Click to expand...
Click to collapse
You're not the only one...some days ago i went back to CM-Based roms and i noticed that they never go in deep sleep! And the phone goes hot...the only rom where i hadn't this problems is the Baked Blackbean by kidkoala...also MIUI roms have this problem!

Hello,
is there anything new on this topic?
Can anyone using CM10 or higher confirm, that he does NOT have this problem?
(to check:
Settings-->Developer Settings (very bottom) --> Display CPU Usage (far down)
let the phone rest some Minutes.
An Overlay is shown. The first three lines are of interest
--> Are the values low, around 0.1? --> no Problem, all good.
--> Are the values high, around 1 or higher --> you have the Problem.
Greetings,
Hendrik

HTC Desire S REBIRTH Project

Hi in this thread we will focus on getting Desire S back to life/still alive. So here we go:
ACTIVE ROM DEVELOPMENT THREADS:​

Recoveries and Miscallenious
ACTIVE RECOVERY DEVELOPEMENTS:​
4ext
Links for radio/hboot are in my sig so...

Hardware repairs
Ok so here we go. Basically you should follow the video I have found on youtube. I did. There are few comments on my side though:
I changed the body using only Torx T5 and Philips 00x40 screwdrivers. They are like 2$ each (I think, I am not in USA)
when it says unscrew four T5 screws I recommend getting rid of philips 00x40 screw too, instead of doing it later
at about 2:00 it says lift SIM and card reader. In the movie it goes like *snap* and gone. Real life experience is that this is glued. You will have to steadily and slowly pull it, watching the glue slowly going off.
after you remove the back cover there will be a piece of tape underneath it. take it off and apply on new body. Otherwise backlit buttons migh flash through between body and battery cover.
speaking about tape... I though my sound control buttons were not working due to their tape being used. Also my power button was collapsed. AFTER REPLACING THE BODY WITH NEW BUTTONS, EVERYTHING WORKS FLAWLESSLY! The phone also has this nice soft feeling to it. I bought my saga used and I have it for a year so in many places the paint was just scratched off.
​
There will be also my movie ETA 09/06/2014

Requests and guides
Here I will take requests for guides/stuff regarding saga. Whatever U need just ask and I will try to develop.
REQUESTS:
MDDI panel kernel (Flinny said we need a person with MDDI panel and enough kernel knowledge to compile it for the new framebuffef)
GUIDES:

Optimization
Settings Optimilization
Minimum and Maximum CPU Frequency
These are the values between which your cpu will scale it's clockspeed. The lower is Min value the less battery your phone should consume when not bothered. Max value is the border of how high you will let you CPU go.
The higher it goes the more battery it eats. Many people say it improves the performance, some that it doesn't. Too high values can cause freezes so don't be surprised when that happens
HTC Desire S values:
Min 245-368
Max 1024-1401
Experimental 1516-1804 (usually causing issues)
U can also try using ART runtime. On my phone it makes everything run little better
Rest of Performance settings don't do any good IMHO. U are welcome to prove me wrong though. I will also make bareboning list but not feeling like it right now so maybe in the evening/tomorrow.

F.A.Q.
F.A.Q.
[Q]: How may I help saving saga?
[A]: Use this lovely picture as your signature picture

ART
Hi it's my first post here in the forum.
I have a Desire S and used a long time 4.04.
In the last 7 month i tried different cm10.1 and cm11 rom from devil kin.
i like'd the cm10.1 but after i switched to cm11 from 08022014 i was absolutely happy with the performance and the battery stats.
Awesome rom over all.Now i switched to the newest one and tried also the ART.
The Battery stats are ok with the newer roms but the one from 08022014 are the best for me.
A few apps don't work with art.Titanium Backup and others.
Then i restored my Backup with dalvik.
Have anyone the same problem with art
Michael

moschman said:
Hi it's my first post here in the forum.
I have a Desire S and used a long time 4.04.
In the last 7 month i tried different cm10.1 and cm11 rom from devil kin.
i like'd the cm10.1 but after i switched to cm11 from 08022014 i was absolutely happy with the performance and the battery stats.
Awesome rom over all.Now i switched to the newest one and tried also the ART.
The Battery stats are ok with the newer roms but the one from 08022014 are the best for me.
A few apps don't work with art.Titanium Backup and others.
Then i restored my Backup with dalvik.
Have anyone the same problem with art
Michael
Click to expand...
Click to collapse
ART is still in development. That's why it's in the developers settings So yes some apps have trouble working on it. Can you please tell us what apps? BTW I was using twrp on art and it was running just fine. Are you on stock superuser or did you install supersu?
Sent from my Desire S using Tapatalk

VnnAmed said:
ART is still in development. That's why it's in the developers settings So yes some apps have trouble working on it. Can you please tell us what apps? BTW I was using twrp on art and it was running just fine. Are you on stock superuser or did you install supersu?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
I use 4ext 1.0.0.6 RC1 with stock super user.The Titamium App produce a error after reboot during my tests.Not only when i open it.
I only test it for a short time.
ART works a little bit smoother but sometimes it lags.
I will stay on Dalvik.It works better for me at the moment.In which partition store the ART the cache files?
michael

someone should finally make MDDI kernel

moschman said:
I use 4ext 1.0.0.6 RC1 with stock super user.The Titamium App produce a error after reboot during my tests.Not only when i open it.
I only test it for a short time.
ART works a little bit smoother but sometimes it lags.
I will stay on Dalvik.It works better for me at the moment.In which partition store the ART the cache files?
michael
Click to expand...
Click to collapse
Frankly i have no idea. But if you wanna wipe them then standard recovery wipe does the trick so maybe in the same as dalvik
441Excelsior said:
someone should finally make MDDI kernel
Click to expand...
Click to collapse
That's true. Sadly right now i don't have skills required to even try to compile one. I don't really think anyone would be able though if Flinny didn't make one so far
Sent from my Desire S using Tapatalk

moschman said:
Hi it's my first post here in the forum.
I have a Desire S and used a long time 4.04.
In the last 7 month i tried different cm10.1 and cm11 rom from devil kin.
i like'd the cm10.1 but after i switched to cm11 from 08022014 i was absolutely happy with the performance and the battery stats.
Awesome rom over all.Now i switched to the newest one and tried also the ART.
The Battery stats are ok with the newer roms but the one from 08022014 are the best for me.
A few apps don't work with art.Titanium Backup and others.
Then i restored my Backup with dalvik.
Have anyone the same problem with art
Michael
Click to expand...
Click to collapse
Titanium Backup 100% works with ART.
Sent from my Nexus 5

MarlX said:
Titanium Backup 100% works with ART.
Sent from my Nexus 5
Click to expand...
Click to collapse
That's my experience too.
HARDWARE post updated.

Have you installed the apps after switching to Art?i habe tried to switch with all my installed apps.i think that's the reason i've problems with it.
Gesendet von meinem Desire S mit Tapatalk

moschman said:
Have you installed the apps after switching to Art?i habe tried to switch with all my installed apps.i think that's the reason i've problems with it.
Gesendet von meinem Desire S mit Tapatalk
Click to expand...
Click to collapse
Theoretically it makes no difference. Practically I always barebone, switch to ART then install aps
BTW. about MDDI kernel. Flinny said we need a person with MDDI panel and enough kernel knowledge to compile it for the new framebuffer.

VnnAmed said:
Theoretically it makes no difference. Practically I always barebone, switch to ART then install aps
BTW. about MDDI kernel. Flinny said we need a person with MDDI panel and enough kernel knowledge to compile it for the new framebuffer.
Click to expand...
Click to collapse
In the next days i will test it with ART again.With clean Installation.I hope it works for me.
I have my desire S in daily use and I cannot stay to long with errors in a rom.I'm on S-ON and must always flash boot.img
so i can do this only at homeBut i will try all new roms from devil kin.

Interesting thread. However, it is a known fact that AOSP ROMs have markedly worse battery life than Sense ROMs (e.g., on SVHD I can manage 2 days with moderate use, on a recent AOSP build I'd be happy to last 8 hours, even after dimming the brightness and such). Has this issue been resolved yet? (It might possibly be related to wifi, because I observe the same behavior if under Sense I tick the 'enable best performance' setting under wifi?)

First time i have the same problems.switch to fix destination in c'lock fixed the Problem.also check if Google now is off
Gesendet von meinem Desire S mit Tapatalk

VnnAmed said:
BTW. about MDDI kernel. Flinny said we need a person with MDDI panel and enough kernel knowledge to compile it for the new framebuffer.
Click to expand...
Click to collapse
I have MDDI device but no kernel development knowledge

Aquous said:
Interesting thread. However, it is a known fact that AOSP ROMs have markedly worse battery life than Sense ROMs (e.g., on SVHD I can manage 2 days with moderate use, on a recent AOSP build I'd be happy to last 8 hours, even after dimming the brightness and such). Has this issue been resolved yet? (It might possibly be related to wifi, because I observe the same behavior if under Sense I tick the 'enable best performance' setting under wifi?)
Click to expand...
Click to collapse
I also believe that . That's the reason I'm sticking with Blackout Rom (I found out battery lasts more than SVHD - maybe I'm wrong),
Did anyone lately done an actual comparison with CM11 and Sense in terms of battery life? My last tests were almost a year ago so maybe things got better ...

Why is there so much hype towards ROMs and kernels?

Hi all
i had my OPO for 2 months now
and i decided to root my phone and try some custom ROMs and kernels since they're so popular , so last month i rooted my phone and take a spin on those famous ROMs and kernels ( partly is also the touchscreen issue and random reboots are driving me nuts ) i won't specify what ROM or kernel i am using though
first impressions when i had a new ROMs is that , there's nothing much that is different i though things would be faster snappier with a new kernel built in but ...my OPO did not , my phone did get more stable but it did suffer from multigesture issue once and force rebooted 3 times in the span of 1 month , but the biggest issue is that my phone keeps getting systemui has stopped working , multitasking button gets bugged one too many times , wallpapers constantly missing when i unlock my phone and animations are very clunky
so yesterday i decided to go back to stock just to remind myself how stock feels , using NANdroid backup i restored everything and...
stock 44s feels so much better compared to custom ROMs which begs the question
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents

I think if varies for the phones and locations, but I was getting some pretty beastly battery life, smooth/fast experience with vanir and Franco. For some reason I just didn't like stock and was not getting as great battery life. I've tried many things and some are good, but there are better (to me at least). I'm just running Lollipop now and can't seem to go back to kk.
It all comes down to ones preference really...
Sent from my A0001 using XDA Free mobile app

wait , isn't cm12 for OPO currently a little unstable? i really wanted to give it a shot but i fear that it is too unstable for a daily driver

Working fine for me; I don't think it is to the point where it can't be a daily driver. I'm really liking it so far, the Lollipop experience feels really nice and smooth.
Check comments from others on the threads to see the kind of issues they're having. Devs are doing daily builds so as days pass it gets better and better.
Sent from bacon with lollipop!

tohno said:
Hi all
i had my OPO for 2 months now
and i decided to root my phone and try some custom ROMs and kernels since they're so popular , so last month i rooted my phone and take a spin on those famous ROMs and kernels ( partly is also the touchscreen issue and random reboots are driving me nuts ) i won't specify what ROM or kernel i am using though
first impressions when i had a new ROMs is that , there's nothing much that is different i though things would be faster snappier with a new kernel built in but ...my OPO did not , my phone did get more stable but it did suffer from multigesture issue once and force rebooted 3 times in the span of 1 month , but the biggest issue is that my phone keeps getting systemui has stopped working , multitasking button gets bugged one too many times , wallpapers constantly missing when i unlock my phone and animations are very clunky
so yesterday i decided to go back to stock just to remind myself how stock feels , using NANdroid backup i restored everything and...
stock 44s feels so much better compared to custom ROMs which begs the question
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
Click to expand...
Click to collapse
Sounds like you didn't do any kernel configurations at all to experience changes.
On AK, with Synapse and UKM, you can change numerical values to configure how the phone handles processes. Default kernel settings aren't optimum for every phone.
My settings consist of: slim (300-2457), CPU boost driver (10ms, 1574MHz, 30ms, 1190MHz), CPU Volt (-35mV), I/O sio @ 1536KB read ahead, drop caches, laptop mode, Vibrator at 25, Fast Charge at 1500mA, C1 (Retention) disabled, 120 second Wifi Scan interval.
With those settings, it makes a HUGE difference compared to stock, as well as fix bugs (screen artifact/tearing) before they were fixed on the latest firmware, and increases battery life by 1.5 times stock.

tohno said:
Hi all
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
Click to expand...
Click to collapse
I have the same questioning but without any problems that you had/have/ My phone works perfectly ( crossing fingers ) and i've had it since July. I always used to ROM my S3-S4-S5 to get a new feel of the phone, but with the Oppo i don't see the reason to. Maybe it's because CM is pretty near pure stock Android, and that's what we get when we switch ROMs on big brands.

tohno said:
Hi all
i had my OPO for 2 months now
why do people deviate from stock ROM on OPO ? stock cm is pretty sweet , I understand rooting the phone to get xposed etc but custom ROMs just don't feel right on the OPO ...so is it just me ?
still props to all the devs out there , no offense just my 2 cents
Click to expand...
Click to collapse
OP, it is not just you. Folks who mess about with custom ROMS, as the other posts here share, do so because they can customize the total phone experience, leaving things off, and putting other items on, to their liking. Giving that the background OS is stable, and the apps a person selects are stable, there should be little to no difference in 'performance', overall, due to the apps. However, you may get performance differences because there are less TSR's currently running in your system, so more memory is available, etc, which can make mainline apps run faster.
So many reasons to do custom apps.
As you said, and I agree, CM is a nice, generally smooth OS/ROM. I am coming from an LG G3, which I like very much, but to customize (remove all the junk), and fine tune (remove Google calling home = less battery live, etc), it take's some time to setup those conditions. With CM, most of the junk is not present at the onset (AT&T largely). Much more clean. I would like Google to be disassociated from CM completely, so that it is an add on only, providing better control of the base CM. I would like this in an official CM ROM/official variation.
That is the reason I have/am switching over to the OnePlus. I have tried a few custom ROMs as well, and the stock CM seems to have the best stability, reliability and consistency, to date. I suspect that will change when a large update comes out, such as L, and a great amount of energy goes into that development. I just changed from 38 to 44 last night on three OPO's. It took 5 minutes, or so, a piece, and all of the data/previous apps, setup etc, stayed with the updates, making for an all too easy update.
Awesome. Next will be "L". I will wait for the CM official, as that will likely be the most stable, as I suspect it is getting the most attention from the CM team, at this time. CM is a pretty nice OS.

[Q] Why is my N5 so slow ?

I can't really put my finger in the cause, it seems to follow all N roms (though most are based on LOS, so..)
Sometimes the device crawls to a standstill, until i'm able to close all open apps, and then it gets snappy again.
I would consider this device at least as fast as my M7, but although the One is slower in general than the N5, it never gets slower...
I don't have weird apps installed, the most crazy ones are the Facebook messenger and chrome, the rest is google apps and whatsapp...

mine is showing same behaviour since a few days ago, ive enabled sync and enabled cm email, others things ive done is installing tumblr, i think some apps that works on 2nd plane arent managed well with ram autokill and somewhat with persistent services.
ill clean flash and disable sync forever [emoji14]
other thing ive noticed is other storage is permanent oversized and the phone cant really know whar is this
Pure CAF @ crLOS14.1

Is it insanely hot when it slows down? If that's the case it's overheating for some reason.

I used to have that problem last year. I kind of fixed it after I formated the memory while I was trying to have F2FS. I knew i'd lost everything in the memory so I did a backup and trough TWRP changed the partition to F2FS and it helped a lot. A friend's tab had the same problem and he fixed it that way

SuicideFlasher said:
Is it insanely hot when it slows down? If that's the case it's overheating for some reason.
Click to expand...
Click to collapse
No... It stalls, it really seems iowait...

daedric said:
No... It stalls, it really seems iowait...
Click to expand...
Click to collapse
Or maybe it went out of memory? Although I doubt it. One thing that comes to mind is mpdecision, sometimes it shuts down all cores except 0 and won't switch them back online, forcing you to do it manually or somehow wake it up. Have you tried keeping tabs on your cores with a monitor app? Anything mpdecision-rated in logcat when the crawls happen?

I was on Catacalysm until nougat, which can be considered stock. didn't have speed issues then.
when I flashed nougat all 3 roms i flashed had annoying lag which was not acceptable.
eventually me and other users discovered it was happening because of the memory filling up.
apparently the phone needs quite a bit of free memory to work well. tweaking memory management through kernel editor solved it for me.
I can't tell for sure if that's your issue but u can give it a try.

What I do is that I clean flash about every six months, generally upgrading to a higher version of android (stopped after 6.0.1 tho cuz of xposed), after backing my media. Once I restore that after the flash, I always have more space available than pre flash and it feels a lot faster. Might be a placebo, might not. But is it stupid if it works?

pingu11 said:
What I do is that I clean flash about every six months, generally upgrading to a higher version of android (stopped after 6.0.1 tho cuz of xposed), after backing my media. Once I restore that after the flash, I always have more space available than pre flash and it feels a lot faster. Might be a placebo, might not. But is it stupid if it works?
Click to expand...
Click to collapse
Problem is, i'm starting to believe it's tied to N7.x

yossi_s1 said:
I was on Catacalysm until nougat, which can be considered stock. didn't have speed issues then.
when I flashed nougat all 3 roms i flashed had annoying lag which was not acceptable.
eventually me and other users discovered it was happening because of the memory filling up.
apparently the phone needs quite a bit of free memory to work well. tweaking memory management through kernel editor solved it for me.
I can't tell for sure if that's your issue but u can give it a try.
Click to expand...
Click to collapse
Your findings are consistent with mine, it seems the device is running out of memory and is trying to swap out heavy apps to make do, namely chrome and facebook. While it's doing that, it's slow as hell. I've also had launcher re-start, like if the OOM had it killed.
Which settings did you tweak ? LowMemoryKiller ?

Yep, LMK set to exterminate.
I wonder what the original configuration was, not only for LMK but also CPU gov etc, Because honestly I think that even after tweaks it was still better on stock.
In general nougat doesn't really add much for me, M was great, I was in a hurry to upgrade because I had play services battery drain bug on M. That was terrible.
Also I noticed mine is thermal throttling really quickly, I don't know if its normal or not. I've been thinking about improving cooling with a mod but at this point my N5 is on its way out. In november I'll close 4 years with it and I'll get a new device (maybe 1+5?)

Memory issue
daedric said:
I can't really put my finger in the cause, it seems to follow all N roms (though most are based on LOS, so..)
Sometimes the device crawls to a standstill, until i'm able to close all open apps, and then it gets snappy again.
I would consider this device at least as fast as my M7, but although the One is slower in general than the N5, it never gets slower...
I don't have weird apps installed, the most crazy ones are the Facebook messenger and chrome, the rest is google apps and whatsapp...
Click to expand...
Click to collapse
It's all because of memory,
3/4 cores are going offline and online regularly, but sometimes​ cores won't go online which create frizzing untill cores get online,
For solution you should be first root then install kernel editor you like and edit core to performance or high performance,
That solved my problems.

daedric said:
I can't really put my finger in the cause, it seems to follow all N roms (though most are based on LOS, so..)
Sometimes the device crawls to a standstill, until i'm able to close all open apps, and then it gets snappy again.
I would consider this device at least as fast as my M7, but although the One is slower in general than the N5, it never gets slower...
I don't have weird apps installed, the most crazy ones are the Facebook messenger and chrome, the rest is google apps and whatsapp...
Click to expand...
Click to collapse
What gapps are you using? Using pico or Beans mini will let you put most of your Google apps on the user partition and not the system partition. You could also try an AOSP based ROM instead of a LOS based ROM like Krexus, Pure Nexus or Tesla

Char_G said:
What gapps are you using? Using pico or Beans mini will let you put most of your Google apps on the user partition and not the system partition. You could also try an AOSP based ROM instead of a LOS based ROM like Krexus, Pure Nexus or Tesla
Click to expand...
Click to collapse
Using pico or Beans mini will let you put most of your Google apps on the user partition and not the system partition.
Click to expand...
Click to collapse
And the advantage would be ?
You could also try an AOSP based ROM instead of a LOS based ROM like Krexus, Pure Nexus or Tesla
Click to expand...
Click to collapse
I tried PureNexus, but it hasn't been update recently. I also suspect of a bug in LOS, since it seems to follow all roms, no matter the builder or kernel.

daedric said:
And the advantage would be ?
I tried PureNexus, but it hasn't been update recently. I also suspect of a bug in LOS, since it seems to follow all roms, no matter the builder or kernel.
Click to expand...
Click to collapse
Using small gapps packages frees up space in /system, I never use full gapps packages on my Nexus 5 and I've never experienced this slow down you're having.
Pure Nexus just updated on May 13th, Tesla updated today. If you choose to flash one of them, be sure to wipe system in advanced wipe as well as data and caches before flashing
Pure Nexus https://www.androidfilehost.com/?fid=6733682732989
Tesla
https://www.androidfilehost.com/?fid=529152257862726717&_utm_source=1-2-2

I don't think the suggestions in the last few comments will help. I'm pretty sure it's mainly a memory management settings issue.
if you want here's my profile in synapse (kernel settings editor you can find on google play). I'm currently testing it for a few days and it seems good so far but I still need to test it under really heavy load.
I'm running nitrogenOS with the kernel that comes with it. if you run something else you may have to tweak it a little.
https://www.dropbox.com/s/1zh08kbh8hoyprl/test2.tgz?dl=0