http://forum.xda-developers.com/showthread.php?t=991276
Found that a couple days ago and was wondering if anyone has tried it or if most developers use something similar as a base.
I've tried it with Jermaine151's Minimalist ROM...and honestly I really don't notice any differences with how things run. My cousin, who has the OG Droid, swears by it.
localceleb said:
http://forum.xda-developers.com/showthread.php?t=991276
Found that a couple days ago and was wondering if anyone has tried it or if most developers use something similar as a base.
Click to expand...
Click to collapse
Kernel devs use a released kernel as a base, not a script. A kernel dev worth his salt has already made memory tweaks according to how he feels the system should run. I'm not sure what that script is supposed to fix or how lag and slow draw times are related to memory. Motorola devices are seriously challenged in that department, but HTC's are some of the best out there. I'm not sure where he came up with the idea that no-op IO queuing was as good as deadline. That's couldn't be more wrong. That also makes me question his other tweaks. Basically, if you're running a custom kernel, especially something like the seriously modified ziggy or AOSP kernels, I'd avoid this.
RMarkwald said:
I've tried it with Jermaine151's Minimalist ROM...and honestly I really don't notice any differences with how things run. My cousin, who has the OG Droid, swears by it.
Click to expand...
Click to collapse
Did you get the feeling it was really aimed at Motorola devices, too?
loonatik78 said:
Did you get the feeling it was really aimed at Motorola devices, too?
Click to expand...
Click to collapse
Yeah I did. I kinda figured that running a custom ROM/kernel combo would be ideal instead of running that script, just because the devs have tweaked/maximized their performance already.
I don't know if that's the case with a Moto device, as I have the Xoom but never owned the phone. My cousin swears by it on his OG Droid, and pointed it out to me.
Like you said, I think with HTC devices you won't really notice much, if any differences. I haven't personally.
RMarkwald said:
Yeah I did. I kinda figured that running a custom ROM/kernel combo would be ideal instead of running that script, just because the devs have tweaked/maximized their performance already.
I don't know if that's the case with a Moto device, as I have the Xoom but never owned the phone. My cousin swears by it on his OG Droid, and pointed it out to me.
Like you said, I think with HTC devices you won't really notice much, if any differences. I haven't personally.
Click to expand...
Click to collapse
Well, like I said, I'm suspect simply because he thinks no-op is a good IO scheduler. It kinda tells me he doesn't know his ass from a hole in the ground. No-op assumes mechanical storage mediums. Deadline is MUCH better for solid state storage, and all the rest of the schedulers are improvements that may or may not be better, depending on how you use your device.
I know deadline is better...but not all phones have deadline available.
I'm no guru on the topic and I go by what I read and read threads about the topic.
I don't take credit for the non-supercharger tweaks as they aren't mine and include links that I used as resources.
Yes I do say noop or deadline would be preferred over other common options on most devices. But the main thing is that both would be faster than what most people have configured - cfq.
btw, this thread seemed convincing that noop is performs very well on android
http://forum.xda-developers.com/showthread.php?t=948001
So forgive me for not consulting you first.
Oh, also...
NOOP scheduler is best used with solid state devices such as flash memory or in general with devices that do not depend on mechanical movement to access data (meaning typical "hard disk" drive technology consisting of seek time primarily, plus rotational latency). Such non-mechanical devices do not require re-ordering of multiple I/O requests, a technique that groups together I/O requests that are physically close together on the disk, thereby reducing average seek time and the variability of I/O service time.[2]
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Noop_scheduler
But then again, you probably would have given me wrong information.
PS. So it seems that you're not all the bright either
zeppelinrox said:
I know deadline is better...but not all phones have deadline available.
I'm no guru on the topic and I go by what I read and read threads about the topic.
I don't take credit for the non-supercharger tweaks as they aren't mine and include links that I used as resources.
Yes I do say noop or deadline would be preferred over other common options on most devices. But the main thing is that both would be faster than what most people have configured - cfq.
btw, this thread seemed convincing that noop is performs very well on android
http://forum.xda-developers.com/showthread.php?t=948001
So forgive me for not consulting you first.
Oh, also...
http://en.wikipedia.org/wiki/Noop_scheduler
But then again, you probably would have given me wrong information.
PS. So it seems that you're not all the bright either
Click to expand...
Click to collapse
Yes. I'm aware of all that. The shortcoming of no-op is that it doesn't take into account demands of data. Some data should be fetched before other data, thus requiring a re-ordering of requests. It is best used on solid-state devices, but not THE best choice for them, necessarily. One might assume no-op to be roughly on par with deadline if some course assumptions about solid-state are made. No-op would be ideal on the SCSI5 array I built because a storage subsystem controller is re-ordering the data and caching it to memory. The latency times on that memory are exceeding low, as are write operations. In fact, the controller would send write-confirm commands back to the system even before data was actually written to disk to allow for more I/O operations. NAND solid-state is a different creature though. Read latency is certainly fast, however write latency is much, much slower in comparison. Because of this, simply throwing read and write commands at the storage subsystem wastes a lot of time since reads must wait on lengthy writes. Deadline holds significant advantage over no-op because it will suspend writes operations to ensure read request deadlines are met. In short, it mitigates some of the shortfall that comes with the NANDs lengthy write times. That's why I say it's significantly better.
I see.
That's very informative indeed.
Perhaps I can determine of a user has deadline available and if so, use that and if not, use noop
zeppelinrox said:
I see.
That's very informative indeed.
Perhaps I can determine of a user has deadline available and if so, use that and if not, use noop
Click to expand...
Click to collapse
I've never professed to be a software guy by any stretch of the imagination. I will never be able to do what you and many, many others do with software, code, Linux, scripting... and of that. I just don't understand that stuff. I'm very much the hardware geek though. Column address strobes? Sense amps? I get that kind of talk. Looking at a script? It might as well be in Sumerian.
zeppelinrox said:
I know deadline is better...but not all phones have deadline available.
I'm no guru on the topic and I go by what I read and read threads about the topic.
I don't take credit for the non-supercharger tweaks as they aren't mine and include links that I used as resources.
Yes I do say noop or deadline would be preferred over other common options on most devices. But the main thing is that both would be faster than what most people have configured - cfq.
btw, this thread seemed convincing that noop is performs very well on android
http://forum.xda-developers.com/showthread.php?t=948001
So forgive me for not consulting you first.
Oh, also...
http://en.wikipedia.org/wiki/Noop_scheduler
But then again, you probably would have given me wrong information.
PS. So it seems that you're not all the bright either
Click to expand...
Click to collapse
I forgot... I also wanted to explain that XDA thread a little.
It looks like he's basing his times on sequential writes, reads, then erases. Were that similar to real world use, his results would be valid, but seldom does anything work like that. Without knowing the specific IC of the flash drive in use, certain features of it can only be guessed at. Unless it's a virgin device or written to 0's, chances are writes are also going to come in conjunction with erases, which are a completely different process, and just as lengthy as writes. Because of how NAND works, larger erases and writes can be accomplished much faster by the address block rather than on a file by file basis. This is because NAND can only address blocks at a time. It has no random access capability for pages or bytes, either reading or writing. In short, his test demonstrates an ideal circumstance, one that is RARELY the circumstance of the real world.
I ran his V6 Supercharger script, Kick Ass Kernel Tweaks, and the 3G turbocharger tweaks in build.prop....
noticed NO difference whatsoever...
Actually, that isn't true. The one thing that seemed to work was the part about making the home launcher "hard to kill", that actually seemed to work. I was having issues with Sense restarting itself, and this alleviated that issue. I noticed that even if I tried to manually stop sense, I couldn't kill it. Two weeks later I removed all trace of the V6 scripts and haven't had any issues since, no idea why, although now I can manually kill the Sense process and have it restart again.
Anyways... no, there was no performance increase whatsoever.
bast525 said:
I ran his V6 Supercharger script, Kick Ass Kernel Tweaks, and the 3G turbocharger tweaks in build.prop....
noticed NO difference whatsoever...
Actually, that isn't true. The one thing that seemed to work was the part about making the home launcher "hard to kill", that actually seemed to work. I was having issues with Sense restarting itself, and this alleviated that issue. I noticed that even if I tried to manually stop sense, I couldn't kill it. Two weeks later I removed all trace of the V6 scripts and haven't had any issues since, no idea why, although now I can manually kill the Sense process and have it restart again.
Anyways... no, there was no performance increase whatsoever.
Click to expand...
Click to collapse
I was curious as to the Sense launcher restarting itself, and if this would fix/have an impact on that issue. Thanks for the info!
anyone that gave loonatik a hard time on this site seriously needs to reconsider, this guy knows his stuff.
loonatik78 said:
I forgot... I also wanted to explain that XDA thread a little.
It looks like he's basing his times on sequential writes, reads, then erases. Were that similar to real world use, his results would be valid, but seldom does anything work like that. Without knowing the specific IC of the flash drive in use, certain features of it can only be guessed at. Unless it's a virgin device or written to 0's, chances are writes are also going to come in conjunction with erases, which are a completely different process, and just as lengthy as writes. Because of how NAND works, larger erases and writes can be accomplished much faster by the address block rather than on a file by file basis. This is because NAND can only address blocks at a time. It has no random access capability for pages or bytes, either reading or writing. In short, his test demonstrates an ideal circumstance, one that is RARELY the circumstance of the real world.
Click to expand...
Click to collapse
I did think that the noop result was too good in relation to the other results.
I would not think that it was that much faster (since deadline is better) so I was somewhat surprised.
Thanks for elaborating
On the Sensation, the Supercharger script gave me no speed increase. It did fix my launcher redraws though. The only thing this script helped me with is multitasking, switching between apps constantly was smoother, and more often they didn't get killed by Android's task manager.
On the Nexus S though, it did make a good amount of difference in the operation of the phone.
I think, on the faster phones, like the SGS2 and the Sensation, it only helps with multitasking..
Well I initially came up with it because of the launcher redraw issue... everything else was gravy... well... a whole lotta gravy...
I don't think SuperSmoother sounds as cool so I'll stick with SuperCharger anyway lol
Related
I thought I'd put this together given the amount of questions and apparent lack of knowledge on what you're getting yourself into with overclocking. While it's a one-click-wonder with SetCPU and JuiceDefender, it's not that simple when it comes to what it's actually doing to the phone.
The first thing you need to know is this:
All devices are not created equal!
Even when they come off the production line together they may not be capable of even getting close to each other with an overclock. This is down to numerous variables, the most important of which is the processor itself. Processors are manufactured in batches from something called a wafer (basically a big chunk of silicon), that batch is then tested to a maximum stable speed and then marketed at a slightly lower speed for the sake of rock solid stability. Dual/multicore processors may have a faulty core disabled and be marketed as something else (hence AMD's Tri-Core processors). This is the reason overclocking works, and the long and the short of it is just because Person A can get 1.3Ghz running stable, doesn't mean Person B can.
So, now we know that whingeing that my Desire can get 1300Mhz but yours crashes every time you go above 1100Mhz is irrelevant, we can move on to the risks. Overclocking is dangerous. That's not an exaggeration, so let me reiterate...
Overclocking is dangerous, You can potentially kill your phone stone dead.
But yet again it's not that simple. Yes, in very rare cases a processor will just go bang and give up, but most of the time other things will happen, behind the scenes, that you won't know about until it's too late.
The basic premise of overclocking is to get a faster processor clock speed. A small jump can probably be attained just by upping the speed itself and be perfectly stable. Going higher is where the problems start. If you start getting crashes/freezes/reboots then the next step is to increase the voltage to the processor to make it more stable, but more voltage means more heat, and excess heat is bad. This can either cook the processor as a whole or a group of transistors. This is more of a problem on a device like the Desire as where do you put the extra cooling?
Another problem is that more voltage can fry an IC track, and/or arc across to a track it shouldn't be on. This could do nothing, but it could also kill a single transistor on the processor or other chips in the device, or maybe multiple transistors and it can also lock them open or closed. This takes us back to random reboots, freezes, and crashes - but this time it can't be fixed.
Then theres a twist. Undervolting can also break things. A transistor is either on or off, and if it doesn't get enough power one of three things can happen - it can work fine, it can not work at all, or it can continually switch until it breaks (what an example? go and flick a light switch on and off until it stops - and it might not be the bulb that goes). If it decides not to work when other parts think it should, guess what happens.
So, bear this in mind when overclocking. If you start getting ANY issues test at stock speed. If you still have issues and/or you kill your phone, it's your own fault.
Mods - I've put this here as it's the place most people seem to ask about OCing, please move it if i'm wrong...
Nicely written and informative. Users must always take their own responsibility when trying to do something "out-of-spec" with their device. I didn't know undervolting could break things though.
It's far far less common and it's not the actual undervolting that causes the issue - it's the power requirements of the device. If you're unfortunate enough to have something keep tripping - it's kind of like when a PSU goes and keeps clicking, there's not quite enough power to flick to On permanently so it just ticks at you till you turn it off or it gives up completely. 9 times out of 10 you'd be fine, but theres always that chance.
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
My phone freezed several times a day with defrost. But no freez with MIUI/OpenDesire. I dont know why but Defrost §$%#s my phone
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
It can be that it is your ext3 partition if you have one...i had a user with freezes...and i did not know what it was...i say him...make all new...he flasht a original rom...root again with unrevoked...flasht my rom again and it was the same...freezes...so he formated the card...and maked a new ext3 and now he have no more problems with freezes
with kind regards..Alex
Good write up. Hopefully people will actually read this and understand the risks before they start pushing zip files with overclocked/undervolted kernels. Personally I've never overclocked any mobile device since I'm not comfortable with the risks that may lead to long term damages.
great job! thumbs up! vote for sticky or linking this in one of the stickys
i'm familiar with overclocking since i've been doing it to my PCs for years. i'm wondering if aosp roms push the phone harder or something than sense based ones?
reason i ask is i've tried a few aosp roms (open desire, defrost etc) and all the various kernels i've tried cause a reboot after a while - 30 mins, upto a few hours. now, i tried richard trips sense kernel and OCd with that no problems at all. very weird
p,s all Ocing was on the relatively small 1113mhz.
With all these tweaks, ROMS, and kernels out there to completely customize your Evo or whatever phone you have. My question is, how to make sure to you don't over do it.
I know that I will look at signatures and see what posters have done to their evos...and try some of those things myself. You can see my signature to see what I've done too.
I am a noob, but I have almost graduated to the next level (whatever that may be). There might be several people like myself who sees all these tweaks and tweaks out themselves in excitement over what you can do to your new toy.
I get the feeling that some tweaks (kernels, CPU governors, ROMS) can often have functions that can overlap and actually worsen performance rather then improve.
As a request to all those who have conquered the realm of the Evo and aid us lowly lifeforms in modding our phones, can you help us figure out what is just right, not enough, or too much? Besides, too much of a good thing can be bad...
We can start off with my Evo. Been using Linpack as a reference for performance, and have averaged 36.5 MFLOPS on single thread. How does this stack up?
Interesting, and i am by no means an expert, but here some things I have found out.
Don't use Collins ph battery tweak and Setcpu together. Your CPU will peg and kill your battery life.
Setcpu with a Screenoff profile is unnecessary if you have the kernel governor set to smartass. Smartass sets the cpu to 384 with the screenoff anyway.
Don't let your daughter take your EVO in the tub. That limits performance as well.
Add in that benchmark apps, like Linpack, are worthless.
You couldn't hit "too much". Believe me, there are people who flash things daily. Some several times a day. And think about how many mod flashes a dev does to his phone?
I meant running at once...
HipKat said:
Add in that benchmark apps, like Linpack, are worthless.
You couldn't hit "too much". Believe me, there are people who flash things daily. Some several times a day. And think about how many mod flashes a dev does to his phone?
Click to expand...
Click to collapse
Too many things running at once. I figure these phones can handle a lot given the roms people float between...
And you have to remember that all phones are different and that just because I can do something that works great on my phone doesn't mean it will do anything for yours. Or make it worse... Just sayin'
Sent from my PC36100 using xda premium
This question is also hard to answer because peoples taste varies so much.
A good example is myself, I like Sense, but I could care less if it is version 1, 2, or 3, I just want it to work good with no problems. I have never seen a theme that I liked better than stock with just a nice photo as a background. In fact, I could really care less what it looks like as long as everything works well when I want to use it. On the other hand, I have almost no use for any of the bloat apps that came with the phone. I remove almost all of them, Including Facebook, the stock browser, the calender and all Sprint specific apps. But I do have a lot of apps on my phone, about 141 user apps, last time I checked for a total of 264 total apps, including the system apps I have left.
I run Fresh 4.2 rom, that I have modified by removing the aforementioned Sprint bloat and built in apps that I don't want or need. I like Flipz rom's the best because they are stable, reliable, and not updated every day, because no update is needed. Plus he removes the CIQ, which runs all the time in the background. I run a kernel that gives me the best performance and responsiveness, with no-sbc and features like HDMI mirroring and 5-point multi-touch, but other than that pretty much stock (trying out various kernels now so can't say which one I will end up going with). The only other mods I have done is I have changed the splash screen, because the white one would wake up my wife when I would boot my phone in bed at night. I also made a battery indicator mod that reads percentage and is easier to see. And I am running the V6 script to eliminate the Sense reloads when exiting apps.
Works for me, but I am sure a lot of guys/girls wouldn't like it at all. So, in the end, it really doesn't matter what I am running, unless someone else has the same tastes as me. And isn't that really the point?
I think I do a lot for my phone. But not too much. Everything in my sig + setcpu, chainfire 3d, juice defender etc
Deck's + SZ + SuperCharger script + ViperMod script.
Journeyman83 said:
As a request to all those who have conquered the realm of the Evo and aid us lowly lifeforms in modding our phones, can you help us figure out what is just right, not enough, or too much? Besides, too much of a good thing can be bad...
Click to expand...
Click to collapse
How much becomes too much the day you bork your phone when you tweaked something you shouldn't have tweaked, and then turn to the forums for help, only to get an attitude at the people who are trying to help you fix your own f'up. That is when it becomes too much.
wfrandy said:
I run a kernel that gives me the best performance and responsiveness, with no-sbc and features like HDMI mirroring and 5-point multi-touch, but other than that pretty much stock ...
Click to expand...
Click to collapse
Just curious about which kernel you're referring to here ... thanks.
Nothing is to much as long as you are comfortable with the mods. Nand restore if you mess something up. If you need any help pm me ill help ya.
Sent from my PC36100 using XDA App
Hi,
i was wondering which effects the Supercharger script may have on the Desire. I am currently on Sandvolt's ICS Rom, and I read about some people using this. As I don't know that much about technical details of memory management and the original thread on it is a bit confusing, i'd like to know if the Rom really runs faster with it, if it is just some placebo effect or if it even might make the system more unstable.
Do you mean the zRam function in the evervolv toolbox. If so then i tried 18% and used the antutu benchmark before (2783 score with 0%) and after (2648 score with 18%) by just changing the percentage setting. So no cigar for zRam.
I don't know much about the technical nitty gritty of ROMs, Kernels, Mem management etc either, but I can say that yes, Supercharger really does work. I installed on my phone yesterday and, although the changes are subtle and hard to quantify, there is definitely a smoothness to my phone now that wasn't there before.
If you are expecting stars to fall from the sky, or your fingers to burn from the blazing heat of the extra speed, you will be disappointed. But you will notice everything running just that little more fluidly.
Thanks, i just wanted to know if it works and didn't expect it to make my Desire as fast as todays high-end phones. Which options do you recommend?
muellersmattes said:
Thanks, i just wanted to know if it works and didn't expect it to make my Desire as fast as todays high-end phones. Which options do you recommend?
Click to expand...
Click to collapse
I tried it, i think it was option 6 (not sure and can't give it a tru now).
It worked, I did not see much more smoothness as it already was smooth, but it stopped random reboot.
I started one for g4 plus now for g5 plus .
Cosmic os 2.1 unofficial
Elemental x kernel over clocked
What benchmark program are you using?
username8611 said:
What benchmark program are you using?
Click to expand...
Click to collapse
Antutu
PureNexus using ElementalX stock CPU speeds and GPU governor, CFQ, custom CPU governor settings
Lineage OMS with ElementalX kernel stock CPU speed and governor. ZEN with custom readahead.
This is kind of useless, benchmark comparison means nothing if it is not on the same device with same set of apps installed.
Sent from my LG G5 using XDA Labs
suhridkhan said:
This is kind of useless, benchmark comparison means nothing if it is not on the same device with same set of apps installed.
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
That doesn't make any sense. Devices are manufactured to a certain tolerance and winning the "silicon lottery" doesn't make a device faster, it makes it more overclockable. Device to device, stock for stock, the difference should be at most a few thousand points from each other. It should be pretty obvious to kill all background apps and processes before benchmarking so apps installed don't matter either. If Facebook is too important to kill for 10 minutes then that person shouldn't worry about benchmarking.
Device to device are obviously going to vary. But a varience of 10k+ points is a pretty good indicator of one set up running slightly better than the other and it's interesting to compare what is the most optimized settings. I can play with my CPU governor all day and get repeatable results +/- 500 - 1000 points. Both me and my wife had a Nexus 5 and with identical settings we both benchmarked very similar. To say it is a useless test is ignorant. If people look at this as a pissing match to see who's "better" then yeah, I see this being a dumb and useless thread. But I think most people who do this want to know what settings, ROM, and kernel are best optimized for performance.
Edit: https://www.phonearena.com/phones/Motorola-Moto-G5-Plus_id10398/benchmarks
63,191
https://www.youtube.com/watch?v=345eKlssdH8
62,769
http://www.fonearena.com/blog/214719/moto-g5-plus-review.html
62,893
https://www.pcmag.com/review/352573/motorola-moto-g5-plus
63,845
http://www.guidingtech.com/65986/moto-g5-plus-vs-redmi-note-4/
62,896
5 different devices, all tested stock within right around 1,000 points of each other.
username8611 said:
That doesn't make any sense. Devices are manufactured to a certain tolerance and winning the "silicon lottery" doesn't make a device faster, it makes it more overclockable. Device to device, stock for stock, the difference should be at most a few thousand points from each other. It should be pretty obvious to kill all background apps and processes before benchmarking so apps installed don't matter either. If Facebook is too important to kill for 10 minutes then that person shouldn't worry about benchmarking.
Device to device are obviously going to vary. But a varience of 10k+ points is a pretty good indicator of one set up running slightly better than the other and it's interesting to compare what is the most optimized settings. I can play with my CPU governor all day and get repeatable results +/- 500 - 1000 points. Both me and my wife had a Nexus 5 and with identical settings we both benchmarked very similar. To say it is a useless test is ignorant. If people look at this as a pissing match to see who's "better" then yeah, I see this being a dumb and useless thread. But I think most people who do this want to know what settings, ROM, and kernel are best optimized for performance.
Edit: https://www.phonearena.com/phones/Motorola-Moto-G5-Plus_id10398/benchmarks
63,191
https://www.youtube.com/watch?v=345eKlssdH8
62,769
http://www.fonearena.com/blog/214719/moto-g5-plus-review.html
62,893
https://www.pcmag.com/review/352573/motorola-moto-g5-plus
63,845
http://www.guidingtech.com/65986/moto-g5-plus-vs-redmi-note-4/
62,896
5 different devices, all tested stock within right around 1,000 points of each other.
Click to expand...
Click to collapse
Thank you for taking the time to write a long response. But, I believe you may have just proved my point. I believe the test results of different roms should be well within 'around 1,000 points of each other'. Unless-
a. the rom is very poorly optimized - score would be lower.
b. the kernel is overclocked - score could be slightly higher.
c. user error (lots of background apps).
suhridkhan said:
Thank you for taking the time to write a long response. But, I believe you may have just proved my point. I believe the test results of different roms should be well within 'around 1,000 points of each other'. Unless-
a. the rom is very poorly optimized - score would be lower.
b. the kernel is overclocked - score could be slightly higher.
c. user error (lots of background apps).
Click to expand...
Click to collapse
I really don't know how else to explain this to you. OP got a lower score than me, yet is overclocked. So it stands to reason that either "a. the rom is very poorly optimized - score would be lower" or "b. the kernel is overclocked - score could be slightly higher" or "c. user error (lots of background apps)" is the reason for it. But wait, the performance should be slightly higher for an overclock except that it isn't. That's the whole reason to benchmark. Another possibility is that since I've heard ElementalX is currently having overclock issues, it may be reverting to its nominal frequency, which I believe is 1.4Ghz. How would this person have known that if not for comparing benchmarks? According to you, they can't compare to stock benchmarks because it's a different set of apps installed and a different ROM and in fact can't compare it to anyone because it's a different device, albeit the same model.
Benchmarks show performance differences, regardless of whether or not they are large enough to even notice on a day to day basis. It shows technical differences and if you think technical differences mean jack squat, then why are you even commenting in this thread? It's the same theory when you throw a car on a dyno. You're going to notice small differences between each run, but when you have two of the same model cars with the same engine, and one consistently puts out 30HP more than the other, there's probably a reason for it.
To reiterate what I said in my first reply, for people who want to compare optimization between different ROMs, kernels, and technical settings such as CPU governors and schedulers, benchmarking is not useless. Not in this method of testing and not across identical devices with different software. The baseline or "stock vs stock" comparison shows that the benchmark is measuring with an adequate amount of accuracy and that multiple devices in stock form are performing equally before being modified. Just because it doesn't mean anything to you doesn't mean that it means nothing at all.
I did some research and things like backround apps running in airplane mode scripts like lightning blade. all these things make a difference. I was running kernel over clocked in interactive mode with lightning script. If I set to performance my score was significantly higher I was hoping this would give users a better way to set up and optimize their device not to compare roms running same device. Yes at first I thought about that then realized it wouldn't make a lot of sense. Im hoping some of u guys will hop on board and help test kernel roms and other mods so maybe we can get the best out of our device thanks guys.
I've seen the Pixel 3 and later models have gained full F2FS filesystem support since F2FS implemented native support for file-based encryption.
Is this possible with our device, or did I miss something? Is anyone else looking for this to be implemented?
All flash devices seem to benefit long term from F2FS. It also gets repetitive having to run fstrim in terminal manually on a weekly basis for EXT4. A part of me says I'm nitpicking cause everything functions perfectly on this device. But I see even greater potential here with F2FS.
I get that some people get excited about new filesystems and see benchmarks and buy into it totally, but
i tested f2fs on my previous device, Galaxy Note 4 (and before that S4), and i was never convinced it did
anything look good in synthetic benchmarks. In every day use i couldnt have told you the difference.
But then one difference i can tell you, is that once you've had your first corrupt fs using f2fs, you'll quickly
retreat to the safety of ext4...ive never had a corrupt fs under ext4....
So i guess youre now going to say, "but newer devices use f2fs, so it cant be that unsafe" to which im going
to answer "yes, but theyve since tuned down or disabled some of the flags/features that people used to use to get
inflated synthetic benchmarks, so its no faster in real world than ext4"
And like i said, i could never tell the difference in real world usage between the two....
Also im pretty sure that on stock RM you dont need to manually run fstrim, i assume that would run on schedule
or during idle
Plus TWRP for the Pixel 2/2XL doesnt support formatting partitions in f2fs, so theres that
73sydney said:
I get that some people get excited about new filesystems and see benchmarks and buy into it totally, but
i tested f2fs on my previous device, Galaxy Note 4 (and before that S4), and i was never convinced it did
anything look good in synthetic benchmarks. In every day use i couldnt have told you the difference.
But then one difference i can tell you, is that once you've had your first corrupt fs using f2fs, you'll quickly
retreat to the safety of ext4...ive never had a corrupt fs under ext4....
So i guess youre now going to say, "but newer devices use f2fs, so it cant be that unsafe" to which im going
to answer "yes, but theyve since tuned down or disabled some of the flags/features that people used to use to get
inflated synthetic benchmarks, so its no faster in real world than ext4"
And like i said, i could never tell the difference in real world usage between the two....
Also im pretty sure that on stock RM you dont need to manually run fstrim, i assume that would run on schedule
or during idle
Plus TWRP for the Pixel 2/2XL doesnt support formatting partitions in f2fs, so theres that
Click to expand...
Click to collapse
Totally agreed on this tried it on nexus 7 2012 and Galaxy Nexus back in the day never was convinced and the downsides are way to much. Ext4 is overall more mature and the available toolkits are much better. If anyone wants to read about it goto the arch wiki, they had a comprehensive write-up on the different file systems.
EXT4 is indeed mature but it was also designed to run on spinning rust. Therefore it will always be a patchwork to keep it running efficiently on flash storage (scripts to run routine fstrim's)
@ReVo_007 you say look up the wiki on each file system; well if anyone were to do that they would realize f2fs is the optimal filesystem for flash storage since it is designed specifically for flash storage, including maximizing the life by distributing writes evenly across all data blocks and increasing read-write performance by building a cache of all data blocks, as well retaining the original read-write performance.
I hope to see f2fs on our device, the performance boost alone would be worth it, especially with apps that rely heavily on cache like Chromium.
I've tested f2fs on many devices, and actually the faster your processor the more it shines because the cache can run more efficiently, especially with native compression enabled. My desktop PC on Fedora 34 runs great, my cheap modded chromebook runs as fast as a high end one ever since I formatted all Fedora partitions as f2fs, a fun project of mine.
ThunderThighs said:
EXT4 is indeed mature but it was also designed to run on spinning rust. Therefore it will always be a patchwork to keep it running efficiently on flash storage (scripts to run routine fstrim's)
@ReVo_007 you say look up the wiki on each file system; well if anyone were to do that they would realize f2fs is the optimal filesystem for flash storage since it is designed specifically for flash storage, including maximizing the life by distributing writes evenly across all data blocks and increasing read-write performance by building a cache of all data blocks, as well retaining the original read-write performance.
I hope to see f2fs on our device, the performance boost alone would be worth it, especially with apps that rely heavily on cache like Chromium.
I've tested f2fs on many devices, and actually the faster your processor the more it shines because the cache can run more efficiently, especially with native compression enabled. My desktop PC on Fedora 34 runs great, my cheap modded chromebook runs as fast as a high end one ever since I formatted all Fedora partitions as f2fs, a fun project of mine.
Click to expand...
Click to collapse
There is no "performance boost" under real world conditions, in test on previous devices where f2fs WAS available the was only a difference in synthetic benchmarks, which is what everyone gets a boner about...the difference isnt enough for me to give up the stability of ext4
fstrims are handled by the OS in modern Android versions, no scripts needed...
on this device if youre not gaming, you'll do more by disabling swap than changing the fs to f2fs...
73sydney said:
There is no "performance boost" under real world conditions, in test on previous devices where f2fs WAS available the was only a difference in synthetic benchmarks, which is what everyone gets a boner about...the difference isnt enough for me to give up the stability of ext4
fstrims are handled by the OS in modern Android versions, no scripts needed...
on this device if youre not gaming, you'll do more by disabling swap than changing the fs to f2fs...
Click to expand...
Click to collapse
Just because you didn't notice anything and experienced instability on a 4+ year old device doesn't mean the entire filesystem is garbage.
I experience quite the opposite on my desktop PC and OnePlus One, infact not only do apps open faster, the system boots faster, large file transfers are 25% faster, and fstrim isn't ever needed.
BTW, android does have a scheduled fstrim but I've found its only ran on a monthly basis and this is unacceptable for how heavily I use my device.
You're also forgetting about the main draw to F2FS is the proven increase in service life of flash storage it's deployed on.
I never said the "filesystem is garbage", please dont assign words to me i never said, typical fanboy move, and a tired one at that
also, top tip, the entire slew of devs is not just waiting here for you to tell them whats not suitable for your usage and ready to jump
btw modern android does fstrim daily at idle, usually at night when youre all tucked up dreaming about how f2fs is the answer to every perceived issue
i have an S2 that still works, only ever had EXT fs on it...now a decade old, with far inferior flash memory on it, how much more life do you expect to have?
ive yet to meet anyone who has said to me "i just upgraded my phone because the flash finally died on it", theyre usually aspirational techno-numptie sheeple who think they need a new phone every 6 months, because giant skivvy told them they did. Apple really IS the root of all evil in modern tech
sorry but i have to debunk bunkum where i see it
If youre detemined to run fstrim more than the scheduled amount, feel free to give the following magisk module ive cooked just for you (and anyone else reading this) a crack
Only active file is fstrim.sh which will be written to /data/adb/service.d/fstrim.sh so its executed at boot
It merely checks the date of the /data/system/last-fstrim and if its been more than 24 hours, it will start an fstrim on /data, /cache/ and /system
Code:
removed due to ungratefulness
Please note: As this only executes after boot complete, it may take some time to start depending on system processes and other service scripts
And then theres always this (ad free) if you want even more control, or just want an app to do what my module does on a daily basis
Trimmer (fstrim) - Apps on Google Play
Trim your device NAND chip manually and fix lags.
play.google.com
You might also want to read this post:
mFSTRIM: A REAL, FOSS fstrim utility for Android, no root necessary
Hey XDA! I actually just posted about another app called Buoy, but over my spring break I went ham and made four apps and I wanted to show off two of them to get some feedback. So here's mFSTRIM! What is fstrim? So you know how hard drives get...
forum.xda-developers.com
MOD EDIT: Quote removed since post removed.
1) Not a sketchy 3rd party script, and i posted the content of it for safety&clarity. If thats sketchy you will probably hate most modules and zip files on XDA
2) If you can do it in a terminal why are you even raising an issue with fstrim? Feel free to enter the commands manually every time you need them, just to avoid taking any assistance offered....
3) I dont have a vendetta against anything, im merely giving an opinion, based on known facts - that you dont like facts is not my problem.
4) Ive given you more than a few links to apps etc to get you actual improvements without waiting for f2fs which will likely never come, because as already highlighted its not as simple as just adding ti to a kernel, youre welcome
MOD EDIT: A sentence repeating a portion of the deleted post and answering it deleted. Go and look elsewhere for help is my suggestion, you dont appear to want to take any advice given here....
I literally dont care what fs you use, that you even think that is troubling, you made that an issue, not me....
Accept the assistance offered or not, no one cares, but insulting me and the entire forum is unlikely to win you any further help
ThunderThighs said:
I've seen the Pixel 3 and later models have gained full F2FS filesystem support since F2FS implemented native support for file-based encryption.
Is this possible with our device, or did I miss something? Is anyone else looking for this to be implemented?
All flash devices seem to benefit long term from F2FS. It also gets repetitive having to run fstrim in terminal manually on a weekly basis for EXT4. A part of me says I'm nitpicking cause everything functions perfectly on this device. But I see even greater potential here with F2FS.
Click to expand...
Click to collapse
F2FS is designed with flash storage in mind. However, EXT4 is used because it has been proven to be more robust. In other words, the chances of corrupting your data are far smaller on EXT4 than on F2FS. Which is why, unless Google changed it for the Pixel 3 and onward, they use EXT4 for their partitions.
Is it possible on the Pixel 2 XL? Anything is possible, but if you want it, you're going to have to do the work yourself. The developers on the forum haven't implemented it in their ROMs, and they likely have a very good reason behind it. Ask them, and I'm sure they'll tell you.
Now, you claim F2FS is better than EXT4. Do you have empirical data to back that up, or is it simply your opinion? If the former, show your data so everyone can make an informed decision. If the latter, that's something you are entitled to, but your right to express that opinion stops when it starts trampling on the opinions of others.
MOD EDIT: Unnecessary comments removed.