Related
Android 4.3 Update Brings TRIM to All Nexus Devices
The Android framework will send out a “start idle maintenance window” event that the MountService listens for, and then invokes vold to fstrim filesystems when a few conditions have been met – the device hasn’t been touched for over an hour, no idle maintenance window event has been sent in 24 hours, and the device is either off-charger with 80% battery or on-charger with 30% battery. The goal is to have fstrim run roughly once every 24 hours if you’re in the habit of plugging the device in to charge every night.
Click to expand...
Click to collapse
Finally Google, you hear us out! Thanks.
Great review from anandtech as always: #fstrim #trim #vold #android #nexus
http://www.anandtech.com/show/7185/android-43-update-brings-trim-to-all-nexus-devices
I really wish Google will also implement the Moto X's Flash Friendly File System aka f2fs on next version of Android to improve random write IOPS and overall system responsiveness.
http://www.anandtech.com/show/7235/moto-x-review/9
-------------
Dear All,
I've been curious after reading Anandtech articles regarding Asus Nexus 7 storage performance and how it compared to other Asus Tablet and Galaxy Nexus. Using Androbench app from Google Play as their tool, I managed to get the result of my Galaxy Nexus after it being used to watch tv series this last three week, and to my surprise, the performance was slowed down perhaps because all the capacity has been used and overwritten and thus having this write amplification effect on flash memory and ssd.
I don't know how to TRIM a eMMC storage on Galaxy Nexus, neither have the knowledge of app or tweak to TRIM, thus I reset to factory image since it formated six partition and restore each to a clean slate with the bootloader, radio, system, userdata, boot, and recovery images. So here's the result I found as per attached. The results were quite shocking though not so significant but it seemed the flashing of the images did restore the storage performance back to normal.
Now I wonder if Linux kernel on Android Jelly Bean supports or will support automatic trimming the eMMC in the near future so it will restore the eMMC (storage) write performance when idling, or is there a tool or adb command to trigger the TRIM command so we don't have to do the backup and restore when resetting to Google factory image?
Resources:
Anandtech: Exploring the Relationship Between Spare Area and Performance Consistency in Modern SSDs
Anandtech: Asus Nexus 7 Storage Performance
Anandtech: SSD Anthology
Anandtech: Performance Over Time and TRIM
Wikipedia: TRIM
Debian Linux SSD Optimization
Impact of ext4′s discard option on my SSD
Android on eMMC: Optimizing for Performance
LINARO: Intro to eMMC - Effectiveness of TRIM
I found bug reported on Android Open Source Project with Issues ID 37258. The screenshots of their Androbench app results were scary, reach below 1Mbps for sequential write (recall the USB1.1 performance?).
Please vote for this issues if you're having similar slow down experience after using your sdcard's capacity to the max. There are already more than 200 people vote for this issue. The more people vote the more chance AOSP developer would hear us out. To vote, click the star icon below add comment section on bottom of this following Android Open Source Issues page:
Nexus 7 Poor Write Speeds After Using Almost All Storage Capacity
Galaxy Nexus GSM Poor Write Speeds After Using Almost All Storage Capacity
Galaxy Nexus Storage Performance Over Time & TRIM
Current work around:
fifthelement said:
There is a much better app than lagfix to trim manually. free, ad-free with schedules and lollipop support : https://play.google.com/store/apps/details?id=com.fifthelement.trimmer
Click to expand...
Click to collapse
use AuxLV's LagFix (fstrim) app from Google Play weekly. (highly recommended) :good:
use backfromthestorm fstrim init.d to fstrim on each reboot flashed using CWM recovery, no crontab yet, but much appreciated. (highly recommended) :good:
use your storage wisely, keeping your free space available at 25% available or more to avoid significant slow write degradation. (highly recommended) :good:
return to stock or format /system, /data/, and /cache could help your eMMC storage performance back to normal. (recommended)
mounting the /data partition with discard option and secured erase the free space. (proceed with CAUTION since there's bug brick on some eMMC chip, you may want to check your eMMC chip first using "Got Brickbug ?" app by Chainfire.)
using kernel with fsync off. (NOT recommended)
Keeping your storage at 25% available will make the storage sub-system performance more consistent on SSD, I believe eMMC using same NAND chipset as in SSD less the controller.
Galaxy Nexus eMMC chip list:
VYL00M (insignificant effect)
V3U00M (significant effect)
My take on Galaxy Nexus 16GB storage performance (eMMC VYL00M rev. 0x25):
Return to stock factory image and filling up the storage with 4GB space available:
SW from 7.53MBps to 5.46MBps ~ 27% loss
RW from 0.24MBps to 0.22MBps ~ 8% loss
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before and after filling up to 389MB space available:
SW from 7.53MBps to 3.91MBps ~ 48% loss
RW from 0.24MBps to 0.23MBps ~ 4% loss
Delete some files to make 4GB space available, and reboot:
SW from 3.91MBps to 6.96MBps ~ 78% gain
RW is the same on 0.23MBps ~ no gain/loss
My take on Nexus 4 16GB storage performance:
Before and after filling up the storage (coming from 5GB and filling it up to 1.2GB space available):
SW from 10 MBps to 4 MBps ~ 60% loss
RW from 1 MBps to 0.39 MBps ~ 61% loss
Did a reboot and the performance is getting better (1.2GB space available, deleted some files left with 2.2GB space available but the performance is more less the same):
SW from 4 MBps to 9.89 MBps ~ 147% gain
RW from 0.39 MBps to 0.51 MBps ~ 31% gain
Using the fstrim app (LagFix for Nexus 7 and HTC One X) and reboot (2.2GB space available):
SW from 9.89 MBps to 9.9 MBps ~ 0.1% gain
RW from 0.51 MBps to 1.07 MBps ~ 110% gain
I attached the cwm packages just for backups. Original scripts are written by backfromthestorm. :good:
Credits (notify me if I forgot to add you here):
ph4zrd
AuxLV
backfromthestrom
JPBeard21
markop90
alangrig
BrianDigital
---
quick thought on samsung eMMC brick bug and how fstrim prolong nand chipset lifespan:
the eMMC brick bug on samsung devices might be related with its own ssd department too. more info about this firmware bug in anandtech site here.
Earlier Samsung told us that all review samples including our three shipped with a pre-production firmware that had a bug in it causing the failures (retail units were shipped with a newer firmware without the bug). At the time we didn't know what exactly was wrong in the firmware, but now we do. When the drive was issued a secure erase command, it would clear all table mapping information at the Address Translation Layer (ATL) but not at the Host Interface Layer (HIL). The data in both layers needs to be up-to-date for the drive operate properly, so when a write request came in, the controller wasn't able to map the data correctly, which caused the firmware to hang. An SSD obviously can't operate without a functioning firmware so from a user's standpoint, it looked like the drive had completely died even though only its firmware was broken.
Click to expand...
Click to collapse
me myself often wonder how come almost all review sites told us to trim in order to prolong the nand chipset lifespan and improve performance. i think i finally found a link to confirm that trim/fstrim does improve nand chipset lifespan by reducing the write amplification.
without trim: storage is nearly full (used, free, and mark as deleted block), and you need to write a bunch of new files which exceed the free available block, the system must do this cycle: read the mark as deleted blocks, erase the mark as deleted blocks, modify the free available block, and write the new files.
with trim: storage is nearly full (used, trully free available), and you need to write a bunch of new files, the system just do this cycle: write the new files, hence less write amplification, longer lifespan and much faster write performance.
the trim command and secure erase are somehow very well explained in this write amplification article on wikipedia here.
TRIM is a SATA command that enables the operating system to tell an SSD what blocks of previously saved data are no longer needed as a result of file deletions or using the format command. When an LBA is replaced by the OS, as with an overwrite of a file, the SSD knows that the original LBA can be marked as stale or invalid and it will not save those blocks during garbage collection. If the user or operating system erases a file (not just remove parts of it), the file will typically be marked for deletion, but the actual contents on the disk are never actually erased. Because of this, the SSD does not know the LBAs that the file previously occupied can be erased, so the SSD will keep garbage collecting them.
The introduction of the TRIM command resolves this problem for operating systems which support it like Windows 7, Mac OS (latest releases of Snow Leopard, Lion, and Mountain Lion, patched in some cases), and Linux since 2.6.33. When a file is permanently deleted or the drive is formatted, the OS sends the TRIM command along with the LBAs that are no longer containing valid data. This informs the SSD that the LBAs in use can be erased and reused. This reduces the LBAs needing to be moved during garbage collection. The result is the SSD will have more free space enabling lower write amplification and higher performance.
The actual benefit of the TRIM command depends upon the free user space on the SSD. If the user capacity on the SSD was 100 GB and the user actually saved 95 GB of data to the drive, any TRIM operation would not add more than 5 GB of free space for garbage collection and wear leveling. In those situations, increasing the amount of over-provisioning by 5 GB would allow the SSD to have more consistent performance because it would always have the additional 5 GB of additional free space without having to wait for the TRIM command to come from the OS.
Click to expand...
Click to collapse
resources:
http://www.anandtech.com/show/6503/second-update-on-samsung-ssd-840840-pro-failures
http://en.wikipedia.org/wiki/TRIM
---
Factory reset via stock recovery, and then use LagFix app or cwm flashable fstrim for optimizing io performance:
AuxLV has made this wonderful app to fstrim your NAND/eMMC storage so it will restore the write performance back to normal after having slow down issues on sequential write and random write due to usage over time. Tested on Nexus 4 and it worked, yay! Do note that this app contains ads from doubleagent and admob as some reported on the original thread.
Take a look at AuxLV LagFix (fstrim) original thread here. AuxLV LagFix (fstrim) FAQs here.
There are two versions of LagFix:
LagFix (fstrim) Premium version - no ads + ability to auto-run trimming on specified schedule. The best choise!
LagFix (fstrim) Free version - trims your memory with one click, has ads, no schedule.
Click to expand...
Click to collapse
backfromthestorm also compiled a flashable script to do fstrim using CWM recovery. take a look at his post here or download the fstrim CWM packages as follows:
fstrim for /system, /data. and /cache here (works on Nexus 4 too!)
fstrim for /data and /cache here
fstrim on reboot here
It seems there's a typo inside the above fstrim init.d script. here's a fix from JPBeard21:
https://www.box.com/shared/l5afni1mxe1wpb2ubw3s
i'm wondering too
Sent from my Galaxy Nexus using xda app-developers app
My sequential write is down to 2.27mb/sec
Never reset my phone to stock and my numbers are all much better than yours. Using Faux kernel with FIOPS scheduler
Looks like someone has been changing ROMs without doing a factory reset...
Sent from my Nexus 7 using xda premium
Teezekel said:
Interesting
Click to expand...
Click to collapse
kizakiyuria said:
i'm wondering too
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah, i never thought this would happen. Hehe
peachpuff said:
My sequential write is down to 2.27mb/sec
Click to expand...
Click to collapse
Whoa, did you frequent use your storage with lots of small and big file sizes?
I guess you do a lot of write-delete-write cycle like me. I get new hobby to watch 720p movies and hdtv series on this gnex, and total Bit written in my storage were over 16GB, hence the flash memory or nand's write amplication occured and slowed down both sequential and random write speed.
Sdobron said:
Never reset my phone to stock and my numbers are all much better than yours. Using Faux kernel with FIOPS scheduler
Click to expand...
Click to collapse
Now that is awesome! Stock kernel didn't have this tweak on storage performance. hope they will add this feature on next build.
Sent from my Galaxy Nexus
Soldier-2Point0 said:
Looks like someone has been changing ROMs without doing a factory reset...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would point to how much free space is left rather than that wiping everytime a rom is changed....
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:26 AM ----------
Sdobron said:
Never reset my phone to stock and my numbers are all much better than yours. Using Faux kernel with FIOPS scheduler
Click to expand...
Click to collapse
Is fsync turned off in faux?
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Is fsync turned off in faux?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Is fsync enabled by default on stock kernel? That explains the slow performance on write but with safer data.
Sent from my Galaxy Nexus
Disregard
There is absolutely no point at all in doing this. The increase is so small that its just a waste of time.
Sent from my Galaxy Nexus using xda app-developers app
chrone said:
Is fsync enabled by default on stock kernel? That explains the slow performance on write but with safer data.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes it is enabled in stock setups, turning it off just leaves the stuff in ram it also tricks benchmarking tests with inaccurate data since its not doing the writing
To the op my stock gnex has results more akin to the after trim results how much storage do you have free
Sent from my Nexus 7 using Tapatalk 2
GldRush98 said:
First off, trim is a command, and more specifically an ATA command. It has nothing to do with eMMC storage. There is no such thing for eMMC.
Second off, eMMC doesn't really need to be trim'ed like SSD's do. The eMMC 4.5 spec did include a discard sub-operation, but it is really not beneficial, especially on our low storage capacity mobile devices.
Click to expand...
Click to collapse
thanks for the heads up. unfortunately a lot of nexus 7 users report slow performance once their sdcard was fulled with data and the regression was pretty much down to below 1Mbps for sequential write. take a look the bugs reported on android open source project.
Smokeey said:
There is absolutely no point at all in doing this. The increase is so small that its just a waste of time.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
same as the above.
BrianDigital said:
Yes it is enabled in stock setups, turning it off just leaves the stuff in ram it also tricks benchmarking tests with inaccurate data since its not doing the writing
To the op my stock gnex has results more akin to the after trim results how much storage do you have free
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
oh okay, nice to know that.
the available storage left around 3-5gb i guess?
forgot to check when it's down to 5Mbps sequential write. i watched supernatural season 1 to season 6 using gnex before reset to factory image, and the total amount of the serial was more less 42Gb, thus frequent copy-watch-delete thing.
care to vote for bug fix on android open source project as follows? more than 200 people voted this bug to be fix or this feature to be implemented. hope google will listen.
the bug report link, to vote on this following link, click the star button below add comment section at bottom of adroind open source project but report page:
https://code.google.com/p/android/issues/detail?id=37258
Same issue here... If my free space goes below 3gb the phone begins to slow down horribly... Until I factory-reset it....
Random writes <0.50 mb/s on androbench
BrianDigital said:
I would point to how much free space is left rather than that wiping everytime a rom is changed....
Sent from my Nexus 7 using Tapatalk 2
---------- Post added at 05:28 AM ---------- Previous post was at 05:26 AM ----------
Is fsync turned off in faux?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm pretty sure I recall reading it's off but I'm not 100% sure...
I usually have about 1 or 2 movies (~700MB or ~1.6GB) on my phone at a time and never had any problems. One day, I felt ambitious to watch a few movies and pretty much got my GNex to under 3GB. Since then, it hasn't been the same.
What I have
GSM Galaxy Nexus
yakjuxw
4.1.1 stock
Unlocked and Rooted
Baseband version I9250XXLF1
Kernel Version 3.0.31-g6fb96c9
Build Number JRO03C.I9250XWLH2
What I've tried
Clearing up movies, camera pictures/videos
Uninstalling recent apps
Clearing app/browser caches
AndroBench Results with 8.14GB available
Sequential Read = 1.97 MB/s
Sequential Write = 0.14 MB/s
Random Read = 0.39 MB/s, 101.47 IOPS(4K)
Random Write = 0.0 MB/s, 1.76 IOPS(4K)
EDIT: Converted from Yakjuxw to yakju using this and now running stock 4.1.2. Now my AndroBench is
26.93 MB/s
12.21 MB/s
8.98 MB/s
0.52 MB/s
markop90 said:
Same issue here... If my free space goes below 3gb the phone begins to slow down horribly... Until I factory-reset it....
Random writes <0.50 mb/s on androbench
Click to expand...
Click to collapse
zero_x3 said:
I usually have about 1 or 2 movies (~700MB or ~1.6GB) on my phone at a time and never had any problems. One day, I felt ambitious to watch a few movies and pretty much got my GNex to under 3GB. Since then, it hasn't been the same.
What I have
GSM Galaxy Nexus
yakjuxw
4.1.1 stock
Unlocked and Rooted
Baseband version I9250XXLF1
Kernel Version 3.0.31-g6fb96c9
Build Number JRO03C.I9250XWLH2
What I've tried
Clearing up movies, camera pictures/videos
Uninstalling recent apps
Clearing app/browser caches
AndroBench Results with 8.14GB available
Sequential Read = 1.97 MB/s
Sequential Write = 0.14 MB/s
Random Read = 0.39 MB/s, 101.47 IOPS(4K)
Random Write = 0.0 MB/s, 1.76 IOPS(4K)
This last AndroBench test is just horrible.
Click to expand...
Click to collapse
same boat here. reset to factory image does format the sdcard and the performance is back to normal again. i hope they do fix this on next build to trigger a command something like TRIM on SSD without having the need to reset to factory image periodically. please vote at the bottom page of page one for Android dev to hear us out regarding this problem. this happens on Nexus 7 as well.
Mounting the relevant partitions with ext4's discard option (as I suggested on code.google.com/p/android/issues/detail?id=39154) seems to fix the problem. You may then fill the filesystem with zeros using dd and simply delete the created file afterwards.
How do you guys regard these results?:
Sent from my Galaxy Nexus using xda premium
I had this problem, and remounting data and cache with discard option on every boot solved this.
alangrig said:
How do you guys regard these results?:
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It's normal.
When your sequential write speed is way below 7MBps then something is not right. The random write will be affected too.
Sent from my Galaxy Nexus
I have found out that some phones are slow because of a bug in Android 4.2. I have a way to determine if you have the bug.
1. Download Androbench: https://play.google.com/store/apps/details?id=com.andromeda.androbench2
2. Execute the test (just press on test all)
3. Is the "random write" speed under 2 MB/s? Then you have the bug.
A possible solution for it is (it is a solution for the Nexus 7 but since it is the same bug it may or may not work on the Galaxy Nexus):
1. Fill up the storage completely
2. Format it
It could be fixed. Let me know if it works.
Sent from my Galaxy Nexus using XDA Premium HD app
https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix use this
send via Samsung Galaxy Nexus with Tapatalk 4 Beta
My random write speed is 0.2 MB/s whether I use the lagfix or not. Running PA 3.65 and AK SKL256. This is pathetic.. :crying:
jaizero said:
My random write speed is 0.2 MB/s whether I use the lagfix or not. Running PA 3.65 and AK SKL256. This is pathetic.. :crying:
Click to expand...
Click to collapse
0.16MB/s before "lagfix", 0.16MB/s after "lagfix".
Edit: I will try the OP's fix later tonight when I get home.
Edit2: By "lagfix" I meant "Lagfix Free" the fstrim implementation on Android mentioned by DJxSpeedy above.
I thought this issue was due to flash degredation?
I have issues with my gnex. Keeps freezing and turning off whenever I do anything really. Gets quite hot as well.
Tried 2 resets and it gets better but comes back again shortly.
Sending it to Samsung for warranty fix.
The nexus 7 does lag and slowdown at times. But a reboot usually solves it. That or freeing up space. I got about 6 gigs free now from the 32GB.
Sent from my HTC One using xda premium
voyager_s said:
I have issues with my gnex. Keeps freezing and turning off whenever I do anything really. Gets quite hot as well.
Tried 2 resets and it gets better but comes back again shortly.
Sending it to Samsung for warranty fix.
The nexus 7 does lag and slowdown at times. But a reboot usually solves it. That or freeing up space. I got about 6 gigs free now from the 32GB.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I was getting Random Write speeds of 0.17 MB/sec through AndroBench. I just tried LagFix right now and it did NOT fix it for me. Post-LagFix, AndroBench reported 0.15 MB/sec. No wonder my phone has been insanely slow. Sigh...
Mine gets realy hot, too. Even if I underclock the phone's CPU and GPU, it still gets hot around the top half of the phone (both sides).
With dynamic fsync enabled in Trickster Mod my random write jumps from 0.2 MB/s to an astonishing 290.14 MB/s. Not sure if these are erroneous due to caching or not. But, that is a significant increase.
Edit: With dynamic fsync enabled I have seen significant increases throughout the benchmark.. Any ideas on why this is occurring?
jaizero said:
With dynamic fsync enabled in Trickster Mod my random write jumps from 0.2 MB/s to an astonishing 290.14 MB/s. Not sure if these are erroneous due to caching or not. But, that is a significant increase.
Edit: With dynamic fsync enabled I have seen significant increases throughout the benchmark.. Any ideas on why this is occurring?
Click to expand...
Click to collapse
I'm not an expert in that area, but I have to wonder if there is caching going on. That number seems too good to be true. However, if true, that is an awesome number.
Sent from my Galaxy Nexus using Tapatalk 2
jaizero said:
With dynamic fsync enabled in Trickster Mod my random write jumps from 0.2 MB/s to an astonishing 290.14 MB/s. Not sure if these are erroneous due to caching or not. But, that is a significant increase.
Edit: With dynamic fsync enabled I have seen significant increases throughout the benchmark.. Any ideas on why this is occurring?
Click to expand...
Click to collapse
Yeah, don't trust it as it doesn't really speed up your storage. Any fsync off/dynamic fsync on benchmarks can be disclaimed as not being real speeds. Both these features disable the fsync function to maintain filesystem integrity. Dynamic fsync actually enables fsync when the screen is on and disables it when the screen is off.
About the OP's report. 2MB/s is amazing for random writes at Androbench's default 4KB. I barely get that on my HTC One which has a faster emmc chip in it in the Galaxy Nexus. 0.2MB/s is more common for the Galaxy Nexus so 0.15 is actually not that far off. There is a whole thread dedicated to fstrim and the lag issue and it mentions lagfix is more detail. 2MB/s is impossible with Androbench's default settings so I don't think slow random write speeds are the only reason for Android 4.2.2 lag. I actually looked into that thread in December and some testing and research concluded that the I/O isn't the only reason and a fresh install won't improve it that much unless you have the emmc performance bug where it slows down a lot when the storage fills up.
I think you have your description of dynamic fsync reversed. When the screen is off, fsync is on. Screen on, fsync off. I think Trickstermod describes it as when enabled and screen on, fsync operation is asynchronous, screen off it is commited synchronously. But I may be wrong, you are a great kernel developer so you know you're stuff.
tiny4579 said:
About the OP's report. 2MB/s is amazing for random writes at Androbench's default 4KB. I barely get that on my HTC One which has a faster emmc chip in it in the Galaxy Nexus. 0.2MB/s is more common for the Galaxy Nexus so 0.15 is actually not that far off. <snip> I actually looked into that thread in December and some testing and research concluded that the I/O isn't the only reason and a fresh install won't improve it that much unless you have the emmc performance bug where it slows down a lot when the storage fills up.
Click to expand...
Click to collapse
I do agree with this. I only get 0.16MB/s and my phone is as snappy as ever. The only time I notice slowdowns are with app updates (way slower than my wife's Galaxy S3) and backups (again the S3 is way faster). Which, to me, is indicative of slow media. I am always on the latest CM stable. (10.1.2 as I write this.) I use no other mods at this time.
---------- Post added at 12:42 PM ---------- Previous post was at 12:38 PM ----------
As I posted the previous post. I did remember that if I let apps run default my Nexus bogs like crazy. Much more so than the S3. I use Greenify (I previously used Autostarts) to keep this in check.
mrgnex said:
I have found out that some phones are slow because of a bug in Android 4.2. I have a way to determine if you have the bug.
1. Download Androbench: https://play.google.com/store/apps/details?id=com.andromeda.androbench2
2. Execute the test (just press on test all)
3. Is the "random write" speed under 2 MB/s? Then you have the bug.
A possible solution for it is (it is a solution for the Nexus 7 but since it is the same bug it may or may not work on the Galaxy Nexus):
1. Fill up the storage completely
2. Format it
It could be fixed. Let me know if it works.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I just ran this test on my Galaxy Note 8 running stock rooted Android 4.1.2. And got a result of 1.42mb/s random write. So there seems to be more to this than Android 4.2
Sent from my GT-N5110 using xda app-developers app
t1.8matt said:
I think you have your description of dynamic fsync reversed. When the screen is off, fsync is on. Screen on, fsync off. I think Trickstermod describes it as when enabled and screen on, fsync operation is asynchronous, screen off it is commited synchronously. But I may be wrong, you are a great kernel developer so you know you're stuff.
Click to expand...
Click to collapse
That's what i said. Dynamic fsync disables fsync - off - with the screen on and enables it - on - once the screen is on. The regular fsync is a manual toggle.
Dynamic fsync from faux is off by default in my kernel so fsync would function normally with this off.
Sent from my HTC One using Tapatalk 2
ahh, got ya.
Is this ok with the default settings?
tiny4579 said:
Yeah, don't trust it as it doesn't really speed up your storage. Any fsync off/dynamic fsync on benchmarks can be disclaimed as not being real speeds. Both these features disable the fsync function to maintain filesystem integrity. Dynamic fsync actually enables fsync when the screen is on and disables it when the screen is off.
About the OP's report. 2MB/s is amazing for random writes at Androbench's default 4KB. I barely get that on my HTC One which has a faster emmc chip in it in the Galaxy Nexus. 0.2MB/s is more common for the Galaxy Nexus so 0.15 is actually not that far off. There is a whole thread dedicated to fstrim and the lag issue and it mentions lagfix is more detail. 2MB/s is impossible with Androbench's default settings so I don't think slow random write speeds are the only reason for Android 4.2.2 lag. I actually looked into that thread in December and some testing and research concluded that the I/O isn't the only reason and a fresh install won't improve it that much unless you have the emmc performance bug where it slows down a lot when the storage fills up.
Click to expand...
Click to collapse
Actually, the HTC One has also been known to have this issue.
Well I got higher than 2 MB/s so I thought that a speed below that would couse the lag. Apparantly I am wrong. I have read it somewhere but it seems theyre wrong. At random write I het around 200 MB/s and random read around 10 MB/s.
Sent from my Galaxy Nexus using XDA Premium HD app
Try Forever Gone: https://play.google.com/store/apps/details?id=com.kovit.p.forevergone
Increased performance on my Nexus 7 by a ton. It's still running on my Galaxy Nexus, but I expect the same results
Both my gnex and my N7 are fast. I'm starting to think it's all user side problems.
Sent from my Nexus 7 using xda premium
VERSION 3.5
"My phone is flying!" - vgomez916
"My phone is lighting quick now, Like I said this thing is really flyin. Thanks"- zackandethan
"This mod is sickkk. phone is flying, on 3g i'm getting 1-2 mbs speed. Thanks for the mod Goddly."- Nyckrs
"My speeds are way up too. 100-200 kbs up to 850kbs now. Download and upload. Same time of the day, same location"- g_ding84
"4G speed jumped to 8.9MB. Incredible!"- xNicoyAx
Stock MF9 , with busybox workaround. http://forum.xda-developers.com/showthread.php?t=1933849 ~~ POST #2 ~~ thanks - devoureddreams-
This tweak pack Originated in the Epic 4G Touch Forums, been tested, and has improved-
Battery Life, User battery life may vary, depending on a varitey of things, widgets, radios, etc., etc.,
network speed
GPS lock
system performance, Increased app load speed, etc.
Browser upgrades
wifi_wait (Kobridge)
memory tweaks (Modded Kobridge, Mine)
test screenstate (screen off = deep sleep, Phakker, Improved)
Init.d test script (Exit_Only)
battery stats format (Exit_Only)
and more
V1.2
added Kobridge, read ahead script
added script for working Cron (Exit_Only)
added an option for NO Undervolt. (more universal)
cleaned up things.
v 1.3
stripped undervolt till a new kernel pops up.
cleaned up scripts, non working parts
added Kobridge 41 tweaks, modded for less conflicts , thanks Kobridge
and a few small touches
Version 2.1 Crossbreeder
]Added newest Crossbreeder to install package
Slightly modded GPS settings.
changed updater script to be compatible with the S4 and all other rooted Android devices
Version 3.0.2 ~
~added more init.d low memory tweaks
~added a few more small kernel tweaks
~swapped out the stock browser for my modded variation
~added a browser cache script (hoping to load browser pages quicker)
~added delay to the larger scripts (to speed up boot times)
~New~ Version 3.5
~Fixed loss of root issue
~added newest release of crossbreeder 12-4
~added a few new kernel tweaks
~cleaned up
Infromation About CrossBreeder-
- This is a new take at Android lag reduction. It's lightweight and won't consume battery. Users have reported drastic improvements in usability and even benchmark scores. It will show noticeable improvements - Android devices from Donut to Froyo to Gingerbread to Honeycomb to ICS and Jellybean.
- This is a combination of 5 different methodologies to reduce Android lag.
- Removal of DNS lag . A lot of the lag in a lot of apps, apart from the GUI lag, is due to slow DNS querying, specially on the mobile network.
- CrossBreeder now runs a caching, parallelising DNS client on the device. So now most of your DNS queries will be served from the cache and if not found, the query will be sent in in round robin fashion to multiple DNS servers including Google DNS, OpenDNS and your home router and the reply will be served to you, hot.
- This speeds up network access and networked apps, like Browsers of course, and Tapatalk, Gmail and thousands of others drastically. And removes a lot of the lag where it was due to DNS querying. This will not increase your network or download speed but pages will load much faster.
- This will future proof your devices as more and more apps start using HTML5 and/or reside completely as web pages or the like.-
I Just thought, there are some great developers in our forum, with great tweaks, geared for their own specific purpose, and i thank them. I HAVE asked for permission to use these tweaks, to make a pack of the best, from the best taking a few of those great tweaks and putting them in one lightweight package. Now , I did NOT create any tweak in this pack. That is why introductions and thanks are in order.
ALL THANKS TO THESE GUYS
Exit_Only - For being the mad scientist of the "tweak" in general
Kobridge - Having used your tweaks in various roms and knowing how great they work :good:
Phakker - For the use of his Infamous, screenstate tweak
G_Ding84 - For being one h*ll of a rom maker , teacher, and one of the most helpful guys youll meet on any forum
idcrisis - For the use of his CrossBreeder Mod found here -
http://forum.xda-developers.com/showthread.php?t=2113150
Without these guys we wouldnt be where we are now, as a forum, or a community.
Gentlemen- On behalf of the users of this tweak , and every E4GT owner out there.... *BOWS* I thank you....
I am in no way responsible for your equipment, flash at your own risk
Download ComaDose version you prefer, from the downloads section, and put on root of phone
Boot into custom recovery
Flash ComaDose
Reboot to rom (flash stock kernel) or reboot system etc.
This is a .zip file, can be flashed with CWM recovery, put on root of phones storage, boot into recovery & flash.
Issues with repack and new Custom Recovery kernels-
Now Ive heard it works for some people on repacks, and ive heard of battery drain, and GPS taking along time to lock on others. But the best results i get, are out of the "stock" Leak kernels.
Conflicting issues with new Custom Recovery modded and released updated version
~NEW~ComaDose V3.5
http://d-h.st/22v
md5: faae873f493540cd68e58f5ddc9ac79a
ComaDose V2.1 W/ Crossbreeder V. 7.2.13
View attachment 2149730
Mirror #1
http://www.androidfilehost.com/?fid=23060877490004661
ComaDose_removal.zip (Uninstaller)
View attachment 2149687
Mirror #1
http://www.androidfilehost.com/?fid=23060877490004662
Whats under this button??
If you guys like my work and have a little jingle floating around, dont hesitate to toss a beer (or coffee ) my way through the "donate to me" under my avatar. THANKS GUYS!
Test Init.d With The "21 Test-init.d" script
-THINGS YOU NEED-
Rom Toolbox (free or pro)
Root Access (superuser access) for Rom Toolbox
ComaDose Already Flashed
-Steps-
After ComaDose flash, if you want to check if your init.d is functioning properly you can check it with the 21 test init.d script...
After flash the test init.d script has already ran (on startup) now thwe sole purpose of this script is to show whether or not init.d
is properly functioning.
When this script is ran (executed) as all scripts in init.d are upon startup, it creates a file in the /data folder.
so why dont we take a look for it?
Using Rom Toolbox, go to the "root browser" tab (upon first startup youll be prompted to SuperUser permissions, Allow this)
Once in Root Browser youll be in the root of your device by default. ( / )
Click on the "Data" folder..
In the /Data folder, were looking for "Exit Only Init.d" file
if you see this file, your init.d is working and all scripts are running ...
If you dont see this file after reboot (post flash) you can execute the "21 test Init " script manually...
back out to the root of the phone, go into "system", then into "etc" then into the "init.d" folder and locate the "21_testinit.d" script, press on it , bringing up this menu.
press the "open as" tab, bringing up this menu...
then press the "script file" option..
Then you want to press the "execute Script" option, making sure the "execute as root option is checked, as shown below.
which will then execute the script using init.d support to do so.. looking like this
after its executed, go back into /data and find the "Exit Only Init.d" file if its there your init.d is working.....
If its as good as it sounds, this'll surely be one of my favorites. Trying this out.
Good to see you on here! I used your tweaks when I was on the E4GT. This is good stuff people!
Sent from my SPH-L710 using XDA
Soap said:
If its as good as it sounds, this'll surely be one of my favorites. Trying this out.
Click to expand...
Click to collapse
give it a try
s9amme said:
Good to see you on here! I used your tweaks when I was on the E4GT. This is good stuff people!
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
this is the best working version yet enjoy
Nice. Giving this a try
Sent from my SPH-L710 using xda premium
Goddly said:
this is the best working version yet enjoy
Click to expand...
Click to collapse
Is it for stock kernel only, or will it play nice with KT as well?
:fingers-crossed:
orlzzt said:
Is it for stock kernel only, or will it play nice with KT as well?
:fingers-crossed:
Click to expand...
Click to collapse
Same question but with dkp?
Sent from my SPH-L710 using xda premium
_Epic said:
Same question but with dkp?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Its not kernel sensitive , nothing in this relates to kernel. should be 100% compatible, only thing you need to be rooted, (busybox etc) Crossbreeder is awesome. has add block etc. for those who want to shut off certain aspects of crossbreeder there are terminal commands you can find those in his thread...
Goddly said:
Its not kernel sensitive , nothing in this relates to kernel. should be 100% compatible, only thing you need to be rooted, (busybox etc) Crossbreeder is awesome. has add block etc. for those who want to shut off certain aspects of crossbreeder there are terminal commands you can find those in his thread...
Click to expand...
Click to collapse
Thank you! Will be flashing it in a few.
Sent from my SPH-L710 using xda premium
I'll give it a go!
Sent from my SPH-L710 using xda app-developers app
You will not be disappointed.
Sent from my SPH-D710 using Tapatalk 2
Goddly said:
You will not be disappointed.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
12 hours in, and I must say I am impressed! Definitely helps with reducing lag and with screen times. My battery is much better today, but being on my wi-fi instead of that nebulistic vortex that is Universal Studios Orlando will always improve battery. Will follow the OP instructions and do a full cycle, then report back.
Thanks to @Goddly for the lovely treat!
This is no joke guys... ive spent countless hours on this mod . I run this myself and know it's results. Just trying to share the wealth.
Sent from my SPH-D710 using Tapatalk 2
Will this work if I'm not on touchwiz? I'm currently running slimbean
Sent from my SPH-L710 using xda premium
shehroze3 said:
Will this work if I'm not on touchwiz? I'm currently running slimbean
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
it will, if you see the file in /data "Exit Only init.d" .. FILE not folder. then your init.d is working correctly..
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Seems to be doing well for me except for one problem, it seems to conflict with adaway? I restored a backup from right before I flashed this and adaway worked fine, but with the mod adaway says disabled every time and resets to that when I try to enable it, which requires a reboot.
Any ideas why? Potential fix?
Sent from my SPH-L710 using xda premium
therenegadenail said:
Seems to be doing well for me except for one problem, it seems to conflict with adaway? I restored a backup from right before I flashed this and adaway worked fine, but with the mod adaway says disabled every time and resets to that when I try to enable it, which requires a reboot.
Any ideas why? Potential fix?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Crossbreeder has its own ad block brother. try uninstalling adaway, if you find you want or need adaway as opposed to the ad block in CBreeder, there are terminal commands that can be used to disable ad blocking in Crossbreeder.. lemme know ill give you the disable terminal command.
looks good, will i need to uninstall crossbreeder before i flash this
edit: cant wait, i will uninstall and flash!
Let me introduce myself first. I have been developing software for Windows for almost 20 years. I love to tweak and tinker. That is what drew me to the Android platform. With that said, here are my findings:
I own a T989. I love the phone. I have tried numerous tweaks and scripts etc out there. In the end I found some very minor tweaks that I have done manually that make a noticeable difference in performance and a battery life.
The biggest increase in performance and battery life that I had noticed was going from a stock rom to CM 10. I am currently on CM 10.2 (and eagerly awaiting a stable version of CM 11).
With that said I noticed that if I changed just a few minor things CM 10.2 runs considerably faster.
Here is what I have done:
1. Disabled ZRAM completely. I have noticed that my phone boots faster with it disabled. I noticed that multitasking was not as good with it disabled but the phone seemed much snappier.
2. Changed Min Free values. I used the Performance Control app for this. My settings are currently as follows:
Foreground Applications: 16 mb
Visible Applications 18 mb
Secondary Server: 23 mb
Hidden Applications 42 mb
Content Providers 49 mb
Empty Applications 56 mb
This seemed to help a lot with multitasking and now it multitasks fast and the phone is much snappier and less laggy. So far my phone is very stable and fast.
3. Set SD Card Read Ahead to 2048.
4. I also left KSM disabled and left Allow purging of assets disabled.
That's it. My phone is rock solid stable and fast with these settings. I also noticed that my battery lasts about 15% longer. Even better than just switching to CyanogenMod 10.2 alone.
Let me know if it works for you.
I would absolutely love to try this, but I don't understand majority of what you wrote. I'm familiar with cyan though..
Sent from my SGH-T989 using xda premium
What is it that you don't understand? Maybe I can help.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Here http://forum.xda-developers.com/showthread.php?t=2401988
*MEGA 4.4.2*GS2 4.4.2*2SHAYNEZ*
---------- Post added at 06:51 AM ---------- Previous post was at 06:48 AM ----------
How do you disable zram entirely is what I'm wondering ?
*MEGA 4.4.2*GS2 4.4.2*2SHAYNEZ*
Disabling ZRAM is CM is easy. Under the performance menu just go to Memory Management > ZRAM. Select Disable. Reboot.
Oh I'm running slimkat on my i9205 mega and downloaded the performance apk. And I'm running beanstalk on my t989
*MEGA 4.4.2*GS2 4.4.2*2SHAYNEZ*
I updated the OP with new Min Free settings. I noticed that it wasn't as stable as I thought. After using it heavily all day I updated some apps in the Play Store and the launcher hung and everything was slow until I rebooted.
I then changed it to the new values above and used it very heavily. I made sure at least 18 apps were open then reinstalled those same apps from the Play Store (I uninstalled them first). So far no problems.
Moderator: Please delete this post. I accidentally double posted.
Is there a way to disable ZRAM on a rooted stock T989 running 4.1.2?
Thanks in advance,
rabilancia
As far as I know the stock ROM doesn't have ZRAM.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
waresoft said:
As far as I know the stock ROM doesn't have ZRAM.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this then then me??
MR.GALAXY S²
waresoft said:
Let me introduce myself first. I have been developing software for Windows for almost 20 years. I love to tweak and tinker. That is what drew me to the Android platform. With that said, here are my findings:
I own a T989. I love the phone. I have tried numerous tweaks and scripts etc out there. In the end I found some very minor tweaks that I have done manually that make a noticeable difference in performance and a battery life.
The biggest increase in performance and battery life that I had noticed was going from a stock rom to CM 10. I am currently on CM 10.2 (and eagerly awaiting a stable version of CM 11).
With that said I noticed that if I changed just a few minor things CM 10.2 runs considerably faster.
Here is what I have done:
1. Disabled ZRAM completely. I have noticed that my phone boots faster with it disabled. I noticed that multitasking was not as good with it disabled but the phone seemed much snappier.
2. Changed Min Free values. I used the Performance Control app for this. My settings are currently as follows:
Foreground Applications: 16 mb
Visible Applications 18 mb
Secondary Server: 23 mb
Hidden Applications 42 mb
Content Providers 49 mb
Empty Applications 56 mb
This seemed to help a lot with multitasking and now it multitasks fast and the phone is much snappier and less laggy. So far my phone is very stable and fast.
3. Set SD Card Read Ahead to 2048.
4. I also left KSM disabled and left Allow purging of assets disabled.
That's it. My phone is rock solid stable and fast with these settings. I also noticed that my battery lasts about 7% longer. Even better than just switching to CyanogenMod 10.2 alone.
Let me know if it works for you.
Click to expand...
Click to collapse
Running JMT8 right now, and this has been one of the best posts I've seen on this forum. All roms I ever flashed would be snappy for the first couple days then slow to a crawl after a month. This has brought this phone back to life and prevent me from having to flash all the time. I wasn't able to do the ZRAM disable since I don't think I have that settings, but I updated the min-free settings and have seen noticable improvements. Thanks!
waresoft said:
1. Disabled ZRAM completely. I have noticed that my phone boots faster with it disabled. I noticed that multitasking was not as good with it disabled but the phone seemed much snappier.
Click to expand...
Click to collapse
Thank you so much! My lag is completely gone after disabling zram.
urBMidol said:
http://forum.xda-developers.com/showthread.php?t=2411161 flash this n be oh so happy ???
MR.GALAXY S²
Click to expand...
Click to collapse
What does this do exactly?
Will SD Card Read Ahead 2048 not reduce the life of the SD? (and by a lot since my current ROM was 200% less.)
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Zram has been disabled in the latest night lies just a fyi
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
bobiscool07 said:
Will SD Card Read Ahead 2048 not reduce the life of the SD? (and by a lot since my current ROM was 200% less.)
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No. In writing a lot over time can possibly reduce the life of the SD. I don't believe that reading will.
waresoft said:
No. In writing a lot over time can possibly reduce the life of the SD. I don't believe that reading will.
Click to expand...
Click to collapse
I been rokcN 4096 n my exSD is cool I guess is there a way to test it
HERCULES S²
hatememarkz said:
I been rokcN 4096 n my exSD is cool I guess is there a way to test it
HERCULES S²
Click to expand...
Click to collapse
I use ROM Toolbox to benchmark. 2048 usually yields better results overall.
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
waresoft said:
I use ROM Toolbox to benchmark. 2048 usually yields better results overall.
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox
Click to expand...
Click to collapse
Bro got that not a noob u tried okj yet
HERCULES S²
Hi all.
This thread is for random builds and development. There is no agenda other than to keep the Kindle Fire alive for the few of us that remain. This thread is not meant to support any specific ROM. I hope this is okay with the forum administrators.
With that said, please join in. We're all in this together.
Cm-12.1 2015-10-15
I made a public viewable folder on my Google Drive for Android stuff here https://drive.google.com/folderview?id=0B7BjC3Ky49TVcjdZQlpHYV9JWXc&usp=sharing
I uploaded a build of CM-12.1. The file name is weird so I will explain (in case you care):
cm-12.1-20151015-UNOFFICIAL-kad-rsm-O3-mo3-wifi-otterx.zip:
kad = kernel compiled with ArchiDroid toolchain
rsm = ROM compiled with SaberMod toolchain
O3 = almost all compiled with -O3
mo3 = more optimization, specifically as much of JustArchi's compiler flags as would work. The '3' is my third attempt to add more optimizations.
wifi = hack to make wifi work without doing a clean install, that is, there is a script, fix-mac.sh, which I think only gets run with a clean install. My hack was simply to copy the file that the wifi driver wants to the name that it wants. This should allow either dirty or clean flashing.
Suggestions:
* Change the animation duration levels in Developer Options to 0.3x or less.
* Use the Noop I/O scheduler for regular things like reading a book (that's why you bought a kindle, right) or browsing the web.
* Use the Deadline I/O scheduler for interactive things like playing a game.
* If you like Gapps, I suggest OpenGapps or TK Gapps. I have not tried this ROM with Gapps.
* You will need to get a third party program to change kernel settings. I like Kernel Adiutor.
The issues:
* Don't use the brightness slider in quicksettings. If you do use it, the status bar goes away and leaves the top part of the quicksettings panel in its place. I suggest disabling the slider and using the brightness control in the status bar settings. I'm not sure if this is a new bug or the result of too much optimization.
* There are no app snapshots in the recents switcher. This may be internal to Android as a way to save memory for low RAM devices, or it may be a bug in CM.
* The Kindle Fire just doesn't have enough RAM (or rather Android is just too freakishly bloated). Attempting to run memory intensive apps will likely result in them crashing or running slowly because the RAM they are using is being swapped to ZRAM. You may be able to adjust the ZRAM size and get better results.
There you have it. I hope you find it useful.
Ah. I just realize this thread. Going to try the 12.1 now
Sent from my Nexus 5 using Tapatalk
@pfederighi. Running fine and fast on the first boot. I clean flashed it without gapps.
After I flash Pico opengapps, it's rather slow now, but probably adjusting things. I'm going to use this for a while and see.
I M using privacy guard to block wake up and keep wake permission for (almost) all apps, since I don't use app that need to do that. Been set it up like that since ur cm11. Gave me very good battery life.
Will post some screenshot later
Thanks for this
Sent from my Nexus 5 using Tapatalk
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Battery life looks good.
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Here you go. It's getting faster now.
Is there any downside of using higher zram? Default it 60mb, I change it to 1gb. Using noop as suggested. Low memory killer should be okay I think, but previous cm11 use much lower than this (120mb). Although I changed it to around 100mb too.
View attachment 3514625View attachment 3514626View attachment 3514627
Edit. Oh one more thing. I try out the brightness slider, working just fine on mine. Ur issue probably because of dirty flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
kev716 said:
Hello,
I'm following your instructions but when I start Kernel Adiutor I get the message No root available. I tried installing SuperSU but it fails when trying to update its binary. Any suggestions?
Click to expand...
Click to collapse
U don't need supersu. There's su app built in. Try installing Adiutor again, I remember I had that issue too, but I re open it, and it ask superuser request.
Su setting is on developer options. It's enabled by default.
Did u open kernel Adiutor and supersu from notification panel? (the one that tell us that xxx app is installed). I did, and it give that error. starting the app from home screen and app drawer works fine. Dunno if it's related to notification panel one, or u just need to open it twice.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
pfederighi said:
I tried increasing ZRAM to 100 MB, I think, and found some things crashed, like the Amazon Underground and Monument Valley apps. I think there wasn't enough real RAM to allocate that much for ZRAM. I changed it back to 60 MB and both of those apps worked again, though slowly.
I'm not sure if I had KSM (kernel samepage merging) enabled. If I didn't, I probably should have. KSM can free up quite a bit of RAM, at the cost of CPU. Though, one can change the parameters for KSM and perhaps find a nice compromise.
Click to expand...
Click to collapse
I don't use that many app, so dunno have experience with crashing. I use 1gb zram since ur cm11, although I don't see any benefit. No crashes though.
I'll try 256mb later then.
I thought swap is remmended at 2x ram on Linux?
Sent from my Nexus 5 using Tapatalk
dokie80 said:
I thought swap is remmended at 2x ram on Linux?
Click to expand...
Click to collapse
Indeed, but that is swap to disk. ZRAM is the method of allocating an area of RAM that is treated as a compressed disk and using it as a swap file system. It is a way of using limited RAM more efficiently, at the expense of CPU time, but it is still using RAM. So, on our device, 100 MB is eaten up by graphics buffers and proprietary firmware. Another ~300 MB is eaten up by Lollipop itself. This leaves us with ~100 MB for user programs, which is not a lot. If you allocate ZRAM at 60 MB, that leaves 40 MB of regular RAM + ~120 MB compressed on the ZRAM drive for programs. This gives us more memory to work with, but effectively 75% of it is compressed, which means every time it's read, it needs to be decompressed, and every time it's written, it needs to be compressed. The memory manager of linux does a great job of making it efficient, but it still slows down the system.
If Android were to actually swap to disk, which it can do, it would wear out the solid state media very quickly because there are a limited number of writes before the media no longer works. There have been great advances in the field of solid state technology such as Intel's and Micron's new 3D XPoint (it's awesome, check it out). So, in the near future this may no longer be an issue, but it doesn't help our old devices.
If you really do need the memory, you can make a swap file on an externally powered USB hard disk, mount the drive, and then issue a `swapon path_to_your_swap_file` from the terminal. I've done it before. It's painfully slow, but it works.
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Thanks for the explanation.
Cmiiw, so zram is on the ram itself?
So if I'm not using many apps at the same time, probably better to use zero zram? Assuming the free RAM is enough for the app.
about KSM, does it mean that with KSM enable, ram that is used for the system can be put on zram (compressed)? And by that, does it mean that zram is used only for user apps?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Regarding not using ZRAM:
From what I understand, yes, if you have enough RAM without using ZRAM, then it's generally better to not use it.
Regarding KSM:
KSM compares the specified number (default 100) of RAM pages per check. If it finds that any RAM pages are identical, it merges them to a single copy-on-write page (that is, they will remain merged until a process attempts to write to it, at which point it'll be copied back to separate pages). Since there are often many read-only pages that happen to be identical, it tends to be very effective.
It runs at the specified interval (default 500ms). I've found that increasing the interval to 750ms or even 1000ms significantly reduces system load with no appreciable difference in the amount of RAM freed.
Because for some CPU & RAM intensive programs I've noticed slightly worse performance with KSM running, I have sometimes run KSM for a few seconds to free up the RAM, disabled it, and then run said program. It seems to work rather well. I suppose I could also have left it running and just increased the sleep interval to a higher amount, say 10000ms.
In general, KSM will free up about 10% of the total RAM, which in my experience is true.
CM-11.0
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
dokie80 said:
Cm10.x is better in performance, but imo, the sound is better/louder on cm11-12.
But no privacy guard on JB, right? I can't get similar battery life on JB, even using deep sleep apps. Unless you can bring privacy guard to cm10, I'll stick on 11+
What cm-11 quirks are you talking about?
Thanks for this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
pfederighi said:
I've uploaded another CM-11 build. The kernel is compiled with ArchiDroid, the ROM with Uber. I think it is slightly faster than the previously posted all SaberMod build. It still suffers from all the regular CM-11 quirks on our device. The direct link: https://drive.google.com/open?id=0B7BjC3Ky49TVVGF3TFJ0ckJzYjA
Try as I might, I have failed to find a solution for the annoying wpa_supplicant error. That is, about every 2 seconds, `logcat` will spit out the following: "E/wpa_supplicant( 490): recvfrom(ctrl_iface): Try again". The 490 is the process ID number, yes?. I've found various references online, but no solutions. Does anyone know what the issue is or how to fix it?
And now for something completely different:
Is there anyone who would be interested in a CM-10.2 OtterX build? Since the general consensus is that CM-10.2 was noticeably faster than CM-11 (I remember it being so), I thought it'd be a good challenge to convert it, but only if there's a desire for it. Please let me know.
Click to expand...
Click to collapse
I would be interested in a 10.2 build.
And of course thx for all your interest in keeping this device alive. Great little tablet.
pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I don't remember facing those issues. About have to press button several time to wake up, sometimes it just need 1-3 secs for the screen to wake, probably because of low cpu clock too.
I remember using 10.x that has privacy guard, but it's different from 11.x. As long I can block wake up and keep wake, I'm sold.
As the sound,
Anyway, since you re offering otterx version, I definitely will test it out, since it's easy and won't require a pc.
Thanks
Sent from my Nexus 5 using Tapatalk
pfederighi said:
CM-11 quirks include things like (it's possible some of these are specific to using a different kernel than the original or using optimizing toolchains):
* Sometimes when you press the Recents button on the navbar it'll come up saying there are no open apps, even when there are apps open.
* Sometimes the clock/weather/upcoming alarms/upcoming events part of the lock screen doesn't appear when waking up the KF.
* Sometimes you have to press the power button more than once to get the KF to wake up.
* Sometimes pressing the power button doesn't work and you may have to plug the KF in to get it to wake up.
* Certain apps, like any Netflix version after 3.0, just don't like the ROM.
I always had good battery life with CM-10.x, even with gapps installed. As for privacy guard, I'll look into it. All of this is as time permits. Edit: It looks like privacy guard is a part of CM-10.2. At least there are a lot of references to it being in 10.2.
Click to expand...
Click to collapse
I thought CM11 had more free ram than CM10?
VTCruzer said:
I thought CM11 had more free ram than CM10?
Click to expand...
Click to collapse
10 is faster, much more responsive than 11. For free RAM I'm not sure, but AFAIK, free RAM can be set using minfree. More free RAM doesn't mean it will run faster, it just mean less crash on apps and more capable on running apps that need high ram.
@pfederighi already explain about the zram. Using that, we can get more free RAM, but will use More cpu to decompress the zram when accessed. So, probably not faster than without using zram.
If we really want to compare the ram, I suggest to compare the usage (system), not the free one.
Sent from my Nexus 5 using Tapatalk
I too would be very interested in a 10.2 build for otterx