Database Info

[RESEARCH] 30FPS issue~[Epson panels fixed]~still work to do

Okay, let's try not to get this thread cluttered up with off-topic speculation like the last one. Starting with what we know already:
There is a ~30 frames per second cap on 2D and 3D rendering. This can be established both visually (play Doodle Jump) and through a benchmark.
If you boot a Nexus One 2.2 ROM, the animation seems to run at 60FPS for a while. This, however, is not totally certain.
This seems to be a software cap, not a hard cap. However, an HTC product representative says otherwise. Jury's still out, apparently.
There is speculation that the cap might be due to the HDMI out on the graphics chip.
Kernel source is being released "soon".
There is touch sensing lag, but this seems to be unrelated.
This issue affects all EVO hardware builds and all EVO ROMs currently.
HTC claims that the cap is by design to improve battery life.
If there is anything else that you have to add that has reasonable evidence backing it up, please do.
EDITED BY TOASTCFH:
Issue of 30fps has been resolved on the devices with Epson pannels through the work done on the kernel reverse engineered kernel source provided in the thread below. for more information and source code for the fix/fixes. also a update.zip can be found on the OP for Fresh 0.3 containing a boot.img containing the kernel compiled with the fps fix.
{KERNEL-SOURCE} GoDmOdE-EVO-2.6.29 {Make Shift Kernel}
enjoy
END OF EDIT

Correct me if I'm wrong but while running fps2d, aren't there slight flashes where the fps jumps over 30? That in and of itself should prove that the cap isn't hardware based.

Krandor311 said:
Correct me if I'm wrong but while running fps2d, aren't there slight flashes where the fps jumps over 30? That in and of itself should prove that the cap isn't hardware based.
Click to expand...
Click to collapse
Very true! I'm not versed very well in the actual mechanics of the hardware, but that does sound like a good sign.

well, a good idea to see if it's a hardware cap or whether it's with the kernel is to try using toast's ported incredible kernel? since the incredible doesn't have the 30fps issue, and assuming it's software(kernel) based, then we shoudln't have that problem.
someone willing to try? sorry, i can't do this on my evo at the moment

I would try if I had the kernel made for me in zip format to flash. Since I have one of the I/O devices I would be able to try but I dont know how to make the kernel to flash.

This thread is gonna get merged...

timgt said:
I would try if I had the kernel made for me in zip format to flash. Since I have one of the I/O devices I would be able to try but I dont know how to make the kernel to flash.
Click to expand...
Click to collapse
Try one of the overclock builds. They are using toast's source. I want to think this has been tried before.
EDIT:
Seems it was tried on these builds:
RvU Rom: On android central
AOSP Rom: Avalaunch's AOSP Rom
FroYo Rom : Avalaunch's FroYo Rom
http://forum.xda-developers.com/showpost.php?p=6769032&postcount=88

Vinny75 said:
Try one of the overclock builds. They are using toast's source. I want to think this has been tried before.
Click to expand...
Click to collapse
I'm pretty sure it has and still has the same issues the board files for the evo are in there though not the incredibles

I don't think it is firmware. The RUU for the EVO and Incredible both contain the same tp_amtel224_16ab.img which may be the firmware for the Amtel 224 touchscreen controller. (http://forum.xda-developers.com/showthread.php?t=704640)

From ffolkes
i've been working on this all day. literally. about 9 hours straight.
this is what i've found. changing the mddi clk_rate to anything but 384000000 results in it getting set to 117965000 according to dmesg. now 384/20 = 19.2 which is precisely the frequency of TCXO. seems a bit odd. it's also exactly half of the other clock defined, GLOBAL_PLL at 768mhz. PLL1 (core) is also 768. another clock is defined, AXI at 128mhz, that acronym is mentioned in the video/gpu drivers. not sure if that's related to that clock, or just some video thing i'm not familiar with and completely unrelated.
changing PMDH_CLK (in devices.c) to OFF | MINMAX or just MINMAX *AND* changing the mddi freq to anything higher than 384000000 results in dmesg saying mddi was set to 235930000 (instead of 117965000) but i still get the same 30fps id get if it was at 384000000. so when you think about it, this means mddi can't be capping it, otherwise i'd see a difference between 235930000 and 384000000. but they're exactly the same fps. it HAS to be happening elsewhere.
i've also found removing the adreno200 drivers from /system/lib/egl results in a silky smooth sprint boot animation, the gui flickers crazily, but fps2d still shows 29. perhaps this is what people were seeing with the froyo boot animation looking smooth.
you know, this 29fps thing is very specific...ntsc is 29.97fps. coincidence? i really don't think so. fps2d always averages out to 29, not 30.
i also tried removing all the hdmi code in the board files, that didn't change anything.
i find it very unlikely this is hardware limited though. the gpu is on die with the cpu, so unless htc had qualcomm make them a custom chip, it's all software controlled. there's nothing to suggest the gpu has its own crystal on the pcb. i mean, if we can completely control the cpu frequency via software, the same stands to reason with the gpu.
if it was something hdmi hardware related, it should be able to be disabled in the kernel and the evo wouldn't even know it was there, just like with the sensors that don't work.
it appears the evo uses a SIL9022A for hdmi, which makes no mention of requiring any change to the lcd frame rate. (http://www.siliconimage.com/products...t.aspx?pid=150)
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showpost.php?p=6854074&postcount=664

I did a little experiment to see if the restriction was in user-space or the kernel:
- First I set up my machine like I described in the "Getting a wider set of development tools on the phone" thread
- Then I wrote a little program (attached) that suspends the phone compositing manager and wrote to the frame buffer device directly.
The conclusion: Even when writing straight to /dev/graphics/fb0, talking straight to the kernel, there's a 30fps limit.

halfline said:
I did a little experiment to see if the restriction was in user-space or the kernel:
- First I set up my machine like I described in the "Getting a wider set of development tools on the phone" thread
- Then I wrote a little program (attached) that suspends the phone compositing manager and wrote to the frame buffer device directly.
The conclusion: Even when writing straight to /dev/graphics/fb0, talking straight to the kernel, there's a 30fps limit.
Click to expand...
Click to collapse
So does this hint that it's a board driver issue and not a hardware issue? Is the fps being sent to fb0 already at 30fps? Sorry, just trying to understand. Been working on this issue for days too.

AssassinsLament said:
So does this hint that it's a board driver issue and not a hardware issue? Is the fps being sent to fb0 already at 30fps? Sorry, just trying to understand. Been working on this issue for days too.
Click to expand...
Click to collapse
I think it would be very strange if it were a hardware issue, but this test unfortunately doesn't help answer that question.
As far as I can tell, the way drawing works on the phone is... Every app communicates with this "system_server" compositor process. That compositor is what sends the drawing to the framebuffer device. The individual apps use shared memory to share what they want drawn with the compositor.
The question I was trying to answer was. Is the system_server compositor limiting the framerate, or is it the kernel? My program takes the compositor out of the picture, and just does some very fast drawing straight to the framebuffer device as quickly as possible. It measures the framerate at which the drawing is getting processed by the kernel. If I let it run for a while the output is like:
30 frames in last second, 29.7 average fps, total time 102 seconds
which leads me to believe it's definitely not the compositor (or say userspace libraries) imposing the 30fps framerate.

halfline said:
I think it would be very strange if it were a hardware issue, but this test unfortunately doesn't help answer that question.
As far as I can tell, the way drawing works on the phone is... Every app communicates with this "system_server" compositor process. That compositor is what sends the drawing to the framebuffer device. The individual apps use shared memory to share what they want drawn with the compositor.
The question I was trying to answer was. Is the system_server compositor limiting the framerate, or is it the kernel? My program takes the compositor out of the picture, and just does some very fast drawing straight to the framebuffer device as quickly as possible. It measures the framerate at which the drawing is getting processed by the kernel. If I let it run for a while the output is like:
30 frames in last second, 29.7 average fps, total time 102 seconds
which leads me to believe it's definitely not the compositor (or say userspace libraries) imposing the 30fps framerate.
Click to expand...
Click to collapse
Ok, thanks. Here is what I've tried so far:
I've taken the full stock HTC Incredible source (similar device), and just put in 9 board supersonic files into it, changed the makefile to compile those supersonic specific files and the kernel boots and everything is fine, but its still capped at 30fps. The HTC Incredible does not have the 30fps issue, so it's 1) code that I can't find in those 9 board supersonic files, or 2) Hardware capped.
That's my best thoughts for now on it

I think it has to do with the htc lock screen. The lockscreen is difficult to remove in custom roms (i haven't seen anybody do it yet) and when you run fps2d with the screen off you get 60 fps (or like 57)

Hey... you guys do know that720p LCD HDTVs display at 30Hz right? Newer ones do 240 and whatnot, but if you have an LCD monitor that's high def (like our evos), play with the refresh rate... just saying

Tilde88 said:
Hey... you guys do know that720p LCD HDTVs display at 30Hz right? Newer ones do 240 and whatnot, but if you have an LCD monitor that's high def (like our evos), play with the refresh rate... just saying
Click to expand...
Click to collapse
I don't think any one here knows that. At least anyone that has done their homework.
-Roger

hibby50 said:
when you run fps2d with the screen off you get 60 fps (or like 57)
Click to expand...
Click to collapse
If that is true, wouldn't this be evidence that it is not hardware capped?

roghaj said:
I don't think any one here knows that. At least anyone that has done their homework.
-Roger
Click to expand...
Click to collapse
I don't know what thats supposed to mean so ill ignore it...
How about trying the straight to kernel test on avalaunchs' froyo v8 with the OC revision flashed? seems like something different... custom kernel, overclocked, and the cameras not working could be a plus for the benchmark... hopefully hdmi is dead too....

Does anyone know if the hd2 has this issue doesn't it have the exact same screen and alot of the same hardware as the evo just different OS

Sense 3.0 Speed in Sensation vs EVO 3D

I checked the below video from Androidcentral.com
http://www.youtube.com/watch?v=cMioPBv4PbI&feature=player_embedded
Looks like the EVO 3D got better handling on graphics speed. Is this because of the extra RAM? I just bought sensation and i still see some lag in overall touch and scroll experience. Its not bad but not very good either considering the beast hardware. Hope this can be solved by ROM chefs or by HTC themselves when they release a patch or something...

It is a sexy device ,the speed is pretty good for me I really don't get lag ,the data problems could just be some peoples service area ,but overall I'm loving the phone

sundar_amn said:
I checked the below video from Androidcentral.com
http://www.youtube.com/watch?v=cMioPBv4PbI&feature=player_embedded
Looks like the EVO 3D got better handling on graphics speed. Is this because of the extra RAM? I just bought sensation and i still see some lag in overall touch and scroll experience. Its not bad but not very good either considering the beast hardware. Hope this can be solved by ROM chefs or by HTC themselves when they release a patch or something...
Click to expand...
Click to collapse
Yep there are a number of people experiencing this with the Sensation including me. I'm getting mine exchanged but I have a feeling this is going to be an issue until we get an OTA

I have no doubt that there is much performance to be gained from these devices.

The ram isn't the reason. Probably just coding, I wouldn't worry about it.

For those of you who are familiar with HTC, do updates usually improve the speed and smoothness of the phone? And how about battery?

topkop said:
For those of you who are familiar with HTC, do updates usually improve the speed and smoothness of the phone? And how about battery?
Click to expand...
Click to collapse
Yes and yes. Normally.

If they don't the community here certainly will.

I saw that video yesterday and it gave me hope. Like many of you have said, I doubt it's the memory memory that's causing the lag. I'm sure with a few tweaks here and there they can speed up sense 3.0 on this device.

Im really very curious as to what is causing people lag. Mine is butter smooth and currently lag free

madwolf27 said:
Im really very curious as to what is causing people lag. Mine is butter smooth and currently lag free
Click to expand...
Click to collapse
Like the Evo 3D on the video?

Who actually cares, though? The phone flies as it is and the next OTA will only improve that. Just enjoy the phone and stop comparing it to everything else

The difference is obvious and I haven't seen any Sensation that smooth on any video.
I'm pretty sure it's not the ram that causes lag. If it was ram Desire S Sense 3.0 port wouldn't have been so smooth like on that video.
http://www.youtube.com/watch?v=NmiQs2SIKU8

Pretty sure the 1.34.401.1 ROM runs better from what I've heard so the next OTAs to come out will prob address the issue

I'm more than sure the evo 3D is just running a updated version of sense than ours. Stop stressing people.. Sheesh.
Sent from my HTC Pyramid using the XDA Premium App.

I think its more to do with the screen (panel) and its refreshing rate and rendering speeds. Evo 3D screen might be totally different from sensartion as its a 3D display. I could be wrong and i wish i am wrong. I am hoping for a OTA or custom Rom solve this... still sensation is a better device and i am loving it...

What bloatware does the Evo 3D have loaded onto it? At least those of us on T-Mobile US are stuck with an anti-malware engine that we can't uninstall. It can't be helping.

_kansei_ said:
What bloatware does the Evo 3D have loaded onto it? At least those of us on T-Mobile US are stuck with an anti-malware engine that we can't uninstall. It can't be helping.
Click to expand...
Click to collapse
What app is that? ill uninstall it NOW. Yes i'm on TMOUSA.

I don't think it's a RAM issue at all. I think it's one of two issues. Either it's all of the bloatware that starts up automatically every time you try to close it and some of which is not just running in the background. It is running in the foreground such as QIK video chat. I have never even used it before but it constantly want to run in the foreground. The other reason is that Sense 3.0 might not be fully optimized yet.
Here is why I think the bloatware is causing the issues. After I use a app that restarts everything (Fast Reboot) the system will be showing about 300mb of free memory is available. If you wait 30 minutes, the system then says less than 150mb of free memory available. I really do think that some of the bloatware is causing performance issues and memory leaks.
What is also weird is that I have had 4 Sensations with the same exact apps on them. I have noticed a difference in speed between all 4 of them. The one that I have now is the quickest and there is no stutter at all. The second one I had was lagging so bad that I just returned it for another. This tells me it's all software related.

Mine doesn't really lag but I can't get that carousel effect anymore. I've learned that if the phone works well keep it cuz you never know what kind of crappy replacement you might get

ICS Video Playback not as good as GB?

Hi, I've noticed with ICS Roms the video playback is very jerky and low quality compared to GB which could play the same video files smoothly. I am talking about a 720p movie but I get the same thing with the recorded videos from the phone's camera.
Any ideas as to why this is and how it can be improved?
I'm currently running Insert Coin 5.1.1, Sensation XE, latest firmware 3.32.
PS I've also noticed the fruit ninja seems kind of pixelated on ICS so i'm guessing it's a general graphics issue with the whole OS.

even i am on the same rom........and i noticed that while playing video the screen gets dim itself even when on full brightness and auto brightness off

Is the force gpu turned on in dev settings? I personally think its equal if not better.. (also talking 720p mkv's)
Sent from my HTC Sensation using xda premium

I just tried forcing GPU, didn't help much if at all.
I remember watching the same movie when I first got my phone and looking at the quality in awe, now that I'm on ICS I'm disappointed.
Hopefully someone will know how to fix.

itsReggie said:
I just tried forcing GPU, didn't help much if at all.
I remember watching the same movie when I first got my phone and looking at the quality in awe, now that I'm on ICS I'm disappointed.
Hopefully someone will know how to fix.
Click to expand...
Click to collapse
Been using VI ICS for a while now and watched a few mins of Cowboys and Aliens and Transformers3 without issues.
For me, I think playback is a bit smoother than GB. Could be a placebo though lol.

I was just browsing around and saw that theres an app called System Tuner that tells you if the second core is running...found out that the second core on my phone was disabled!
I enabled it and success! my video played so smoothly it was beautiful once again
So it's probably a kernel issue rather than ICS issue. (can't remember whether i chose OC Kernel or Stock)

Possible I/O lagfix (from nexus 7/OneX forums)

http://forum.xda-developers.com/showthread.php?t=2104326
Hi,
Saw this on reddit this morning, as no one's posted it yet I'd just like to offer it up as another potential lag-fixer.
The source of the problem is that internal storage is not properly TRIMmed when needed. You can find lots of information on XDA - http://forum.xda-developers.com/show....php?t=1971852 and http://forum.xda-developers.com/show....php?t=1929021 for example. It is also well-known fact that running fstrim Linux tool from time to time fixes the issue until internal memory runs out of free blocks. Other solutions like mounting with -discard or disabling fsync may be dangerous.
LagFix is a user-friendly implementation of fstrim utility. It allows you to select which partitions to trim (you should leave defaults unless you know what you are doing) and run the process easily.
Please note that fstrim output depends on kernel and device. It works fine unless you see errors. You might see big amounts of bytes, zero amount or repeating amount. All are fine! Read fstrim manual to understand why all these outputs are valid.
It is also advised to reboot your device after the TRIM process so that kernel could reinitialize block data.
App is free and is available in Play Market. Current version is 1.0.
P.S. If your ROM mounts /data with -discard then this app is NOT needed! Mounting with -discard causes brickbug on some devices, so I DO NOT advise using -discard.
Click to expand...
Click to collapse
Link on Play: https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix
I applied it on my rooted, locked tf700 and, well, nothing bad happened. I am on the .25 update, which I feel made overall app-opening a little smoother, so I can't tell if this makes any noticeable difference, but it certainly doesn't seem slower after applying it. The dev says that if you run androbench after applying the fix i/o read should be higher, if anyone could run a few benchmarks of before/after it would be appreciated! I've never really placed much faith in benchmarks so didn't bother doing it myself.
Hope this benefits someone!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

I downloaded and installed it. Ran it, rebooted. It did trim, but the jury is still out on whether this actually helps or not. It's too freshly booted to really judge the effects properly, so I'll have it settle in and report back.
It didn't break my 700 -- that's a good thing to start with.

MartyHulskemper said:
I downloaded and installed it. Ran it, rebooted. It did trim, but the jury is still out on whether this actually helps or not. It's too freshly booted to really judge the effects properly, so I'll have it settle in and report back.
It didn't break my 700 -- that's a good thing to start with.
Click to expand...
Click to collapse
Yeah, I was reluctant to be the first one to try it on an infinity... But it worked out for the better, I think. Now I don't know if the .25 jb update or this is to thank for the better performance. It should hope up till the 4.2 update at least! Quite pleased with the .25 update
Sent from my Galaxy Nexus using Tapatalk 2

Just tried it. Could be my imagination, but my tablet seems snappier.

I am not convinced that it will have any effect: TF700's Hynix eNAND flash is eMMC 4.41 compliant, which does not have DISCARD command, the equivalent of SATA's TRIM command. The DISCARD command is supported in eMMC 4.51 compliant flash but I don't know if the Kingston flash in Nexus 7 is eMMC 4.51 compliant. Even if it does TRIM the TF700, probably it will have little effect if you have alot of free space left as it does not affect the garbage collection significantly. One would hope that TRIM should already be done dynamically within the file management software as it would reduce write amplification factor, hence improve write speed performance?

Kraka said:
I am not convinced that it will have any effect: TF700's Hynix eNAND flash is eMMC 4.41 compliant, which does not have DISCARD command, the equivalent of SATA's TRIM command.
Click to expand...
Click to collapse
According to the spec, eMMC 4.41 supports TRIM - what's the difference between TRIM and DISCARD?
I read that eMMC 4.41 also supports "background operation" and "high priority interrupt" - these sound much more interesting related to lag than TRIM. Do you have any idea if these features are already used in the TF700's Linux kernel (or even at all in any kernel)?

faq in op link said:
Which devices are affected?
It is known by now, that Nexus S, Galaxy Nexus, Nexus 7, Nexus 4, Nexus 10 and HTC One X need regular trimming. It is also believed that all pre-ICS devices used different memory and they do NOT need it nor support it. Pre-ICS support will be dropped in version 1.2. Other 4.0+ devices? Well, test it! And report if it really helps - your device will be added to the list.
How to properly test it?
Use AndroBench app before using LagFix and after. You only need micro test. Look for Sequential Write values. Reading from memory is NOT affected, because reading does not involve writting and only writting triggers search party for free memory blocks.
Click to expand...
Click to collapse
For anyone looking for early confirmation of impact.
I think I'll give this a try. I have some hefty typing lag. I thought one of the first updates had gotten rid of it, but it came back, it was just temporarily relieved by the fresh reboot then. If it does help, it'll probably be a month before I confirm anything, just to avoid giving/having false hope . Thanks for posting op hope it works.
Edit, sorry, just noticed OP already mentioned androbench.
Edit 2: Saw no change in my androbench write speed. Sequential write was something over 5MB/s, random write was .15MB/s both before and after running it, and again after rebooting. lagfix claimed to have trimmed successfully. If anything, it felt more laggy for a while after running it. I'm an OS update or two behind FWIW, just installed Jelly Bean a month or so ago. I like to let everyone else test the updates before I install them. I'll probably run another bench this evening. :shrug:

fsTRIM = AWESOME fix - on CROMI, OCed kernel, fsync disabled
I just download the fsTRIM app and it worked with CROMI, OCed kernel, and fsync disabled. Will seem laggy right after runnng it, just reboot as soon as you do and things will be deffinitely running smoother and slightly faster now. Noticing less keyboard latency even as I type this out. I suggest trying it out.
UPDATE - Seriously try this **** out. Keyboard typing is radically smoother in browser, evernote, and google drive. Less latency between multi touch gestures ive set up in GMD Gesture Control as well. App opening is still instantaneous. Loading big web pages is definitely quicker. Will time boot and other things and update again soon.
Update - Opening large files and youtube is faster. large pdfs load faster. everything is really....snappy, and.....smooth.....best of both worlds. things were already pretty snappy and smooth with CROMI, didnt think they could get better but it has. I time everything as well to compare. I could barely time it after this fix as everything is basically instantaneous. Havent tried writing/moving large files on internal storage yet, will test soon, this is distracting me from my homework too much lol.

It works for me I can now download files and move them without having my tablet unusable until it's done.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Just installed this.
Will give it a go...

lucius.zen said:
...
Click to expand...
Click to collapse
You posted the same content in two other thread sof you own making, and in this one. One helluva way to get to 2000 posts without interjecting anything actually useful. Neitehr is this post, I will mention myself, but please keep a lower profile next time.

So far I haven't noticed any difference at all. I'll give it the rest of the day and if I don't feel there is any change I'll just uninstall.

A couple of apps to help with lag!

Here are a couple of apps, both free that should make a difference in system performance. They've made a difference for me. Both require root.
The 1st allows you to set fstrim to run on a schedule... You can google on fstrim and a popular app called "lagfix" however trimmer is also free and allows scheduling a weekly run which is only available in the pay version of lagfix. It also is ad free unlike lagfix.
https://play.google.com/store/apps/details?id=com.fifthelement.trimmer
The 2nd app is called sEFix and it points to an xda thread that discusses how it handles "lag reduction" in it's description.
https://play.google.com/store/apps/details?id=com.zdvdev.sef&hl=en
Hope someone finds these useful.

Thank you for that. Can you please give some advice hot to set the Treshold in sEFix?
Stock Rom + xposed

wallah said:
Thank you for that. Can you please give some advice hot to set the Treshold in sEFix?
Stock Rom + xposed
Click to expand...
Click to collapse
I slid mine all the way to the right...I was quite pleased with the result. For trimmer you'll probably have to reboot to see the most effect. I let trimmer run weekly.
If someone tries the apps and likes the results please reply back to let folks know. In the discussion I read gamers were especially happy with the FPS increase they saw when using sEFix.

Thank you, I will follow your instructions ?
Stock Rom + xposed

I have +140 apps according to AR optimizing cache after a cache wipe in TWRP.
My phone (6939y, stock, TWRP, rooted, partitions resized) is never slow.
Why did yours become as slow to decide a tune-up is neccesary?
Verstuurd vanaf mijn 6039Y met Tapatalk

CK0y0TE said:
I have +140 apps according to AR optimizing cache after a cache wipe in TWRP.
My phone (6939y, stock, TWRP, rooted, partitions resized) is never slow.
Why did yours become as slow to decide a tune-up is neccesary?
Verstuurd vanaf mijn 6039Y met Tapatalk
Click to expand...
Click to collapse
Android 5.0.2 is known for excessive lag..thats the whole reason android 5.1.1 came out so quickly. If you are lucky enough not to NOTICE IT great for you! Using the dalvik runtime for xposed vs the art runtime is also known to add lag. I've left my idol 3 sitting in sleep for several hours only to find when it's woken it's at a crawl till I do a reboot. I have 12 different android devices(tablets, phones, android tv etc) all running a similar set of apps and that doesn't occur with any of the others...then again none of them are on android 5.0.2. Speed of the external microsd as well as readahead cache can also cause slowdowns....in fact it's almost impossible to nail down ALL the possible causes of slowdowns.
I have to wonder about folks who jump into a conversation they are not involved in just to say "Doesn't happen to me. What are YOU doing wrong?"

After 2 days using sefix and trimmer have to say I'm not sure if it really works or it's placebo. Seems like it is a improvement but I get the same results with sefix on 256 or 1024 threshold..
Sent from hell

Nikola Jovanovic said:
After 2 days using sefix and trimmer have to say I'm not sure if it really works or it's placebo. Seems like it is a improvement but I get the same results with sefix on 256 or 1024 threshold..
Sent from hell
Click to expand...
Click to collapse
Trimmer only runs weekly...it's more of a housekeeping issue. If you read the thread behind sefix it explains what it does which is solve a problem with random number generation (/dev/urandom) that can cause lag as apps wait on results...the program corrects the situation. If 256 is giving you the same entropy generation as 512 or 1024 then use whatever suits you but I can tell a difference in ui responsiveness....especially when hitting the button and having it come out of sleep..pulling down the notification bar etc.

That's obvious but no fps changes or loading times in games for me.
Sent from hell

Nikola Jovanovic said:
That's obvious but no fps changes or loading times in games for me.
Sent from hell
Click to expand...
Click to collapse
Did you try one of the games mentioned in the xda thread? The game would have to use /dev/urandom to get an increase in fps I would think. (I'm not a gamer) It's not a global fix to all games. Given the ui improvement and so far *knocks on wood* no battery drain as a result of running it I've been running it for several day's so far with nothing but positive results. On the other hand it's not really my job to "sell" you on it since I don't make a thing whether you choose to use it or not.

It sounds stupid that Google don't fix this things like entropy pool(it's not permanent fix though) or battery drains that come from location services, facebook, ui, media server, active radio even when phone sleeps, etc..
Sent from hell

What about the audio skipping? I haven't found a fix yet i use apollo player

On stock 0.1 firmware no skips, but heard the other users have it.
Sent from hell

gecko702 said:
What about the audio skipping? I haven't found a fix yet i use apollo player
Click to expand...
Click to collapse
If you are referring to the skipping while listening through bluetooth that's not caused by lag and this won't do anything for it. I don't have any skipping when listening through speakers. A cause for that might be a slow microsd card if you are listening to music from it....you can try moving some music to the internal storage and see if it still skips to eliminate that possibility.

famewolf said:
If you are referring to the skipping while listening through bluetooth that's not caused by lag and this won't do anything for it. I don't have any skipping when listening through speakers. A cause for that might be a slow microsd card if you are listening to music from it....you can try moving some music to the internal storage and see if it still skips to eliminate that possibility.
Click to expand...
Click to collapse
Hmmm i see you got a point besides this microsd is from way back 2012 so i might as well upgrade to a samsung one then

gecko702 said:
Hmmm i see you got a point besides this microsd is from way back 2012 so i might as well upgrade to a samsung one then
Click to expand...
Click to collapse
Not sure where you are located but here in USA I've seen plenty of deals for a 64GB around $17-20 US and $50 for the 128GB. Rather annoying since I paid $70 for my 128GB not very long ago.

Yeah i know i haven't taken care of buying another sd card lmao its a sandisk so its pretty slow I know amazon has good deals now

Man, thanks for these apps, they helped sooo much!
Sent from my 6039H using XDA Free mobile app

Thank you for the apps !

On the stock rom there was big need for apps like this.. Sefix, fstrim.. Now I do manually input fstrim comm whene I feel like it, but on cm12 no real need for them. As I said, must have when you're on stock.
sent from Hell