Hi Guys,
Let me present to you my first published app in google play. it is both free and ad-free and requires no permissions.
Trimmer allows you to trim your device NAND chip manually, which may improve your device storage speed significantly.
it supports lollipop as well and I am going to add more features to this app in future so stay tuned
In order to use this app your device should be rooted and your device NAND chip should support TRIM command.
Let me know what you think and send me your suggestions for next update.
Here is a short explanation about what this app does :
Almost all Android devices use NAND chips for data storage. Because of how NAND chips work, they may become significantly slow after some time. Trimming would help to restore NAND Chips performance to their initial value. Although Android 4.3+ supports trim natively, users have no control over this process and Android doesnt trim the storage as much as it is supposed to do, which results in slow storage performance and thus laggy devies. Trimmer enables you to trim your device manually if you feel it has become laggy.
Trimmer incorporates a well-known fstrim utility which is a part of Linux kernel tools. This utility trims memory devices which support TRIM operation.
Click to expand...
Click to collapse
Download : Google Play
If you liked my app, please dont forget to rate it 5 stars. your stars will give me motivation to spend more time developing and add more features to this app.
Sounds interesting!
Would also be nice to put trimming as startup operation in init.d, can the fstrim binary be called directly by a shell?
A question: when i connect my device to a PC as usb storage to remove files from SD card, then the freed space is not reported by system till next reboot; does trimming fix also this (reporting right free space)?
[must-ask-question]Does this app perform potentially dangerous operations on filesystems?[/must-ask-question]
Publiuss said:
Sounds interesting!
Would also be nice to put trimming as startup operation in init.d, can the fstrim binary be called directly by a shell?
A question: when i connect my device to a PC as usb storage to remove files from SD card, then the freed space is not reported by system till next reboot; does trimming fix also this (reporting right free space)?
[must-ask-question]Does this app perform potentially dangerous operations on filesystems?[/must-ask-question]
Click to expand...
Click to collapse
putting trimming in init.d is not good enough. init.d only runs at startup while device storage needs to be trimmed more than that. at least once or twice per week based on usage.
yes, you can install busybox which includes fstrim and call it from shell.
great idea,good work.thx
fifthelement said:
putting trimming in init.d is not good enough. init.d only runs at startup while device storage needs to be trimmed more than that. at least once or twice per week based on usage.
yes, you can install busybox which includes fstrim and call it from shell.
Click to expand...
Click to collapse
Ehm... I reboot quite often than twice per week...
I have questions, why I will need press trim now everytime when I open the trimmer apps? It is normal... Is not stick/set on boot. Thanks in advance.
bbivan said:
I have questions, why I will need press trim now everytime when I open the trimmer apps? It is normal... Is not stick/set on boot. Thanks in advance.
Click to expand...
Click to collapse
Trim has nothing to do with boot. last time my phone was rebooted was few months ago, while some devices need to be trimmed once or twice weekly to keep optimal performance. I may add a feature in future to schedule the Trim automatically without the need of trimming manually.
fifthelement said:
Trim has nothing to do with boot. last time my phone was rebooted was few months ago, while some devices need to be trimmed once or twice weekly to keep optimal performance. I may add a feature in future to schedule the Trim automatically without the need of trimming manually.
Click to expand...
Click to collapse
Wow, uptime warrior! :laugh:
However, rated 5* on playstore!
Publiuss said:
Wow, uptime warrior! :laugh:
However, rated 5* on playstore!
Click to expand...
Click to collapse
Thanks buddy for rating
I have a GPE HTC One m7 and I only reboot it when I want to flash something like a new ROM or Kernel. otherwise it is pretty stable and there are no reboots.
I guess your devices are unstable
significantly improved with my devices...
S3 i9300 - 4.4.4 Kitkat
S2 i9100 - 5.0.2 Lollipop
Note N7000 - 4.1.2 JB with trim kernel support
Thanks buddy...
I'm a bit puzzled about what the app actually does.
If this NAND issue really is a problem to IO performance, why isn't this taken care of by the native android system?
No disrespect to your App! You'll have to excuse my ignorance here... If it actually solves such a problem, it great!
CyanMod-X said:
significantly improved with my devices...
S3 i9300 - 4.4.4 Kitkat
S2 i9100 - 5.0.2 Lollipop
Note N7000 - 4.1.2 JB with trim kernel support
Thanks buddy...
Click to expand...
Click to collapse
You're welcome Enjoy.
Please could you add support to trim /efs and /preload?
Sent from my GT-I9100 using Tapatalk
/system needs attention on the screen layout.
RovG said:
Please could you add support to trim /efs and /preload?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I am not sure if trimming /efs and /preload has any effect on the performance of the device and AFAIK only some Samsung devices have these partitions.
trimming is only effective for the partitions which are written to frequently.
RovG said:
/system needs attention on the screen layout.
Click to expand...
Click to collapse
I will update the layout for small screen devices in next update.
Rated 5 stars for the great effort!
Automatic trim stopped
For a few weeks the automatic trim worked flawless and I got a notification it had done it's job.
Since a few days it stopped automatic trimming. Manually it still does it's job.
Any ideas ??
Hi ..sorry for Noob question. ... I've note n7000 rooted with Omnirom. I never tried lagfix fearing the famous brickbug issue. Can I use this app without fear?
I searched for a solution following the failure of my previous fstrim solution after updating to 5.1.1 on my Nexus 7 2012, and found your work. Thank you for very much for your work.
WarriorMax said:
Hi ..sorry for Noob question. ... I've note n7000 rooted with Omnirom. I never tried lagfix fearing the famous brickbug issue. Can I use this app without fear?
Click to expand...
Click to collapse
Same question here with the Samsung Galaxy S2 (i9100) - can I safely use this app without "superbricking" my phone sooner or later?
[E]: http://forum.xda-developers.com/and...roject-brickbug-aftermath-recovering-t2823051
Apparently it's probably to use the app if you are running a current ROM.
Related
ok, first check out the changelog for the latest version of TB:
What's in this version:
1. • Can backup/restore external app data (/Android/data/ on SD card). Very useful for "SwiftKey X" and many other apps! Enabled by default with 32MB upper limit. Can use a label to select which external data to include.
2. • Added self-test to detect WAL bug and refuse DB conversion on SGS2 stock ROMs. This is *essential* because these ROMs get crazy and delete DB files! Our apologies to those who got bitten. When Samsung fixes this awful bug, TB will detect it.
3. • Bugfixes.
4. • Big translation updates.
Click to expand...
Click to collapse
So I sent them this:
I noticed the mention of the "WAL bug" that deletes DB files. I was wondering what this was? I think I marriage experiencecit on the Sidekick, a Samsung phone. would it cause some apps to randomly disappear?
Click to expand...
Click to collapse
and got back this:
We're truly sorry about this issue. Yes, today we discovered a terrible bug in the SGS2 stock ROM, which explains what happened. Titanium Backup has converted your databases to WAL fine, but the SGS2 stock ROM itself does not support WAL properly: instead of opening the WAL databases, it will silently erase them and then claim that the open has succeeded!
Before allowing any conversion to WAL, Titanium Backup performed a verification, which we have tested and properly fails on older ROMs. On the SGS2 though, the verification passes because the test database is fine after the conversion - well yes it's fine, but it's empty.
We have improved the WAL testing code and we will release an updated version as quickly as possible. The new version has been tested well on SGS2 and detects the problem properly (ie: it prevents conversion to WAL format). This only applies to stock ROMs though, as CyanogenMod (for example) does not contain the buggy Samsung code and fully supports WAL without issues.
If you have no backups of the erased databases, we're very sorry to confirm that it cannot be recovered, unfortunately. Please accept our deepest apologies for this issue. If you would like a refund, please let us know because we stand behind our product.
Click to expand...
Click to collapse
I will, therefore, be posting a bounty for he who first gets (real) stock android up and running on this phone. check the dev board soon for details.
I'm so paranoid about my ICS (although I have no problems) I created a small application to check if we have the famous chip bug and as root makes the reading test on the memory to verify that we have not damaged.
Do not be too critical of the appearance. It's just a quick prototype to verify that we are without memory corruption.
I hope you find it useful: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Vinagre said:
I'm so paranoid about my ICS (although I have no problems) I created a small application to check if we have the famous chip bug and as root makes the reading test on the memory to verify that we have not damaged.
Do not be too critical of the appearance. It's just a quick prototype to verify that we are without memory corruption.
I hope you find it useful: play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Click to expand...
Click to collapse
What does it do, and how exactly does it go about verifying?
I do not mean to be a skeptic, but I am typically cautious if an app is asking for root permissions.
Mmmm be nice if this is true
Btw link doesn't work
Root permissions are for memory read. I use "dd ..." command.
Vinagre said:
Root permissions are for memory read. I use "dd ..." command.
Click to expand...
Click to collapse
it would basically attempt to read the entire emmc ,and if at any point it fails or lock up the phone then that means we have damage.
just so we are clear ,having bad sectors is normal wear and tear ,this would only indicate that it's more prone to locking up when wiping from LPY ,not that anyone should attempt such a thing anyway.
brockyneo said:
Btw link doesn't work
Click to expand...
Click to collapse
The link is partial, without http:. I am young at forum for links :-(
You can search into play store.
Looks like a good app, but crashes whenever I rotate the screen or touch the screen while its running on CM9 6/9. I'll try not touching my phone at all when its running to see if it will pass.
No freezing for me!
Doesn't this do the same as Chainfire's Got Brickbug app?
Edit: Aha, no it's not.
So, whenever it gets to about 4.8 GB it goes really fast from this point to 15 GB in under 1 second. I have more than 4.8 GB stored on my card - about 11 GB. What does this mean? Is my emmc good or not?
Edit: Fail. My mistake... OMG..
Edit2: It has currently used 360 seconds.
Edit3: It's done checking.. Now what? Do we get a message if it's damaged?
I have a bad Chip but no damage
Sent from my GT-N7000 using xda premium
75 seconds.
Why it does not show any message if there's damage or not ?
lol more than 800 seconds here, didn't get a message so I presume it's still ok.
Nice
Nice app...I have an Insane chip, but no damage at all...check took about 80 secs....ufff....I feel more relieved now!...
Thanks !
Passed, took 615s.
Why does it ask SU permissions so many times during the test .
Vinagre said:
I'm so paranoid about my ICS (although I have no problems) I created a small application to check if we have the famous chip bug and as root makes the reading test on the memory to verify that we have not damaged.
Do not be too critical of the appearance. It's just a quick prototype to verify that we are without memory corruption.
I hope you find it useful: play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Click to expand...
Click to collapse
If you so paranoid... install paranoidandroid lol
OK - so I have a damaged chip and I live in the US (imported the phone). Now what?
Why not just give us the terminal command so that we can see the error messages, if any?
Why would it take longer on some devices?
Mine took about exactly 104 seconds on the German LPY and checked 15388672 (k?)
After I do a fresh install of cromi on my tablet, it's just excellent, fluid and smooth. After a while, the performance seems to detoriate. It has done so for about every version I tried and the same goes for my phone (An i9300 running slimkat). So my question is this: What makes an android device inherently slower? Is there a way to see what apps may slow down the performance?
vonVaffel said:
After I do a fresh install of cromi on my tablet, it's just excellent, fluid and smooth. After a while, the performance seems to detoriate. It has done so for about every version I tried and the same goes for my phone (An i9300 running slimkat). So my question is this: What makes an android device inherently slower? Is there a way to see what apps may slow down the performance?
Click to expand...
Click to collapse
That is a very good question...:good: I have the same question but I can not find a solid answer for it. I hope that some developers or experts can give us a good definition of it...
This is what I know but I may be totally off and wrong, haha..
When you first install the new ROM, all your partitions are new and clean. When you write something to your data partition, it is most of the case, it just writes data to a clean blocks without erasing the blocks. After a while, most of your blocks are dirty even though they are unused or available for writing. This is the part that users see the degradation. When a new data is writing to the available and dirty blocks, first the kernel has to erase the block before writing to it. The erase process takes a lot longer than the write process according to my research...:crying: On our tf700, writing to the internal sd or mmc is very slow already. On top of that, the erasing process has to be done before writing the new data to your internal sd. If you do the math, the performance of the writing will degrade more than twice comparing the new installation..:crying: I believe that google noticed this issue so they implemented the fsTRIM on the newer kernel source to tackle this problem..:good:
However, when you are using the fsTRIM, you have to sacrifice some slightly performance loss and you don't notice performance degradation over time.. During the normal usage, I can not tell the differences if the fsTRIM is on or off but I did see the small performance loss with a bench test.. In short, I know both _that and hund's kernel support the fsTRIM but it is disable as a default. You can try to enable it to see if it is solving your degraded problem....Good luck...:fingers-crossed:
Another method is to use the lagfix manually once a week or more frequently...
Usually I reboot to recovery, wipe cache (don't need to do dalvik), reboot back to ROM and everything is quick again.
I don't know why this works though.
sbdags said:
Usually I reboot to recovery, wipe cache (don't need to do dalvik), reboot back to ROM and everything is quick again.
I don't know why this works though.
Click to expand...
Click to collapse
Thanks sbdags for the information...
LetMeKnow said:
This is what I know but I may be totally off and wrong, haha..
Click to expand...
Click to collapse
Mostly correct.
LetMeKnow said:
When a new data is writing to the available and dirty blocks, first the kernel has to erase the block before writing to it.
Click to expand...
Click to collapse
It's the controller in the eMMC that does that. The peculiarities of flash memory - no way to directly overwrite data, need to erase in large blocks before writing, can't write to the same location too often or it wears out - are all hidden by a small (and not very smart, in our case) controller. The kernel sees a block device that it can use like a mechanical hard drive.
LetMeKnow said:
Another method is to use the lagfix manually once a week or more frequently...
Click to expand...
Click to collapse
This depends how much data is written and how much space is free. If you have 10 GB free and you run lagfix once, you won't benefit from running it again until after 10 GB have been written to flash. Random writes cost more than their real size (see above, overwrites must be simulated by rewriting larger blocks), sequential writes translate to about their actual size written to flash.
_that said:
Mostly correct.
It's the controller in the eMMC that does that. The peculiarities of flash memory - no way to directly overwrite data, need to erase in large blocks before writing, can't write to the same location too often or it wears out - are all hidden by a small (and not very smart, in our case) controller. The kernel sees a block device that it can use like a mechanical hard drive.
This depends how much data is written and how much space is free. If you have 10 GB free and you run lagfix once, you won't benefit from running it again until after 10 GB have been written to flash. Random writes cost more than their real size (see above, overwrites must be simulated by rewriting larger blocks), sequential writes translate to about their actual size written to flash.
Click to expand...
Click to collapse
Thanks _that for sharing the information and time...:good:
I take the mostly correct and hate the least incorrect....:crying: Every time I talk to you. It seems like there is a language barrier. Oh yeah, it is called an Android language, hehe... I will loose a few days researching and trying to understand what you are saying...:silly: However, I feel like that I understand android a bit more in the end and thanks for that....
Now it is time for me to bang my head on the keyboard for the next few days...:crying:
Thanks for the insightful information guys, you are frickin awesome! . I thought the lagfix app was removed from CROMI, since the trim function was no longer needed after 4.2. I might be wrong about this, but in any case I have LagFix premium which can trim partitions on a schedule, and I take it that it doesn't do any harm at least?
vonVaffel said:
Thanks for the insightful information guys, you are frickin awesome! . I thought the lagfix app was removed from CROMI, since the trim function was no longer needed after 4.2. I might be wrong about this, but in any case I have LagFix premium which can trim partitions on a schedule, and I take it that it doesn't do any harm at least?
Click to expand...
Click to collapse
I personally like the "discard" mounting option on Cromi x.. It is just my personal preference...:laugh: I don't recall that the lagfix was a problem for me but I heard some issued stories about it but could not remember now, sorry...
vonVaffel said:
Thanks for the insightful information guys, you are frickin awesome! . I thought the lagfix app was removed from CROMI, since the trim function was no longer needed after 4.2. I might be wrong about this, but in any case I have LagFix premium which can trim partitions on a schedule, and I take it that it doesn't do any harm at least?
Click to expand...
Click to collapse
CROMI is based off ASUS' stock firmware, hence it is still Android 4.2.1 (and will likely stay that way forever since ASUS does not update the tf700 anymore). As TRIM is only available in Android 4.3 onward, Lagfix is still a relevant. As far as I know, some people reported data corruption from using Lagfix, but I personally haven't had any issue. Your mileage may vary though.
As for performance degradation, I am also quite interested in knowing why. One of the key strength of Linux over Windows is that Linux does not have this performance degradation over time and most Linux users will happily attest to this statement. Apparently, Google has somehow removed that strength when they made Android. Many people who choose iOS over Android will also cite this performance degradation as a factor since iOS does not suffer from this problem as well, if at all. At this point, I am just going to blame Dalvik VM for all this inefficiency. If you look at Windows Phone 8 (made by the same company that brought you Windows) and iOS, both run native machine code instead of a virtual machine and they don't have any drop in performance over time. Practically, a HTC HD7 with WP7 can still compete with current Android handsets in terms of UI smoothness and exhibit no stuttering nonewhatsoever, except when you started using intensive apps, but that is definitely a hardware limitation.
huy_lonewolf said:
As TRIM is only available in Android 4.3 onward, Lagfix is still a relevant.
Click to expand...
Click to collapse
"Trim" is a kernel feature and is activated by using the ext4 mount option "discard", which has been in the kernel since 2010.
Expanding a bit on the issue at hand, I'm curious about two types of apps:
First one is twilight. It's much like the f.lux or redshift program for PCs making the screen red at nighttime, so that falling asleep is supposedly easier. Now I enjoy using this on any type of screen I'm in front of after dark, but the downside to this is that it makes both my tablet and phone really laggy. My phone (i9300) isn't as affected by the performance as the tf700 is, but I wonder why this sort of app slows the device down?
Second app is SwiftKey. I love this keyboard app for its functionality and its predictions. However not being a native English speaker, I also write a lot of Norwegian so I have two word lists installed. My issue is that the keyboard seems slow and sluggish in its response, and sometimes it takes forever to actually write something down. Is this related to using two dictionares instead of one? I really love this app and would like to keep on using it, as no other keyboard seems as good to me.
vonVaffel said:
Expanding a bit on the issue at hand, I'm curious about two types of apps:
First one is twilight. It's much like the f.lux or redshift program for PCs making the screen red at nighttime, so that falling asleep is supposedly easier. Now I enjoy using this on any type of screen I'm in front of after dark, but the downside to this is that it makes both my tablet and phone really laggy. My phone (i9300) isn't as affected by the performance as the tf700 is, but I wonder why this sort of app slows the device down?
Second app is SwiftKey. I love this keyboard app for its functionality and its predictions. However not being a native English speaker, I also write a lot of Norwegian so I have two word lists installed. My issue is that the keyboard seems slow and sluggish in its response, and sometimes it takes forever to actually write something down. Is this related to using two dictionares instead of one? I really love this app and would like to keep on using it, as no other keyboard seems as good to me.
Click to expand...
Click to collapse
I also use f.lux on all our laptops. Never heard of twillight. I highly recommend and have used Lux Dash (location based sunset setting etc) for what seems like forever on Kindle Fire, Note, Note 2 and TF700 and it can even dim down to pretty much all black if you want it to. I never experienced any slow-down because of it on the Infinity.
Just last week I read about two apps that slow down the posters Infinity and one of them was Swiftkey and there was no mention of your dual language setting and I suspect it's not a dual language issue. I've used Danish & English (and briefly Spanish for Duolingo app so 3 at the same time) and also noticed it being very unresponsive, but haven't noticed any diffence with 1, 2, or 3 languages. Now it solely resides on my Note 2. Should be easy to test though, just by disabling one language and see if it makes a difference.
I can't remember what the other app was though. It was some post or article about lowering RAM usage by, among other things, using Titanium to change certain downloadable system apps (Gmail, Dropbox etc) into user apps and then using Greenify. Hopefully Greenify will work on this new Cromi-KK ROM I just installed, but that's on tomorrow's To Do List. Note: Greenify can only do system apps (paid version) with Xposed installer and Xposed doesn't work with KitKat.
Hope that was somewhat useful and not a complete waste of your time :silly:
Not sure if I need to create a new thread, or post here, but I'm at a loss. I feel like I've wasted a ton of money on this thing. I bought the TF700 over the Galaxy 10.1 thinking it had better specs and was going to be a great product from ASUS. First problem I had was "phantom touches" and had to send it in for repair. Now it's utterly useless. It SUPER slow, so slow that I'd rather throw it in the trash than deal with it. I've tried Clean Master, but it never seemed to help performance. I installed CROMBI-kk and it's still has poor performance. I've set the wallpaper to black (none), removed all widgets, and installed maybe 2 apps so far. I also tried LagFix but it says it doesn't have permission to modify the directories (or something like that). I've ensured that Root is enabled under Developer Options.
My old Incredible (v1) runs better than this. I really don't know what to do. It's very frustrating. I even wasted the money on the keyboard attachment but in combination with the lag, I can't even bear to use it. I downloaded 2048 and swipes are slow, and once the tiles move, sometimes it takes a couple of seconds for the numbers to merge.
Is there ANYTHING I can do? I've looked through the suggestions. Am I missing something? Does EVERYONE have this problem with their TF700? I wrote ASUS about it and basically said "since you unlocked the device, we would have to replace the mainboard for $300 (parts + labor) in order to undergo any out-of-warranty diagnostics." The only reason I unlocked it was because I've heard that the performance problems were due to the ASUS software, so I thought installing a custom ROM would be the answer to my problem.
Any idea if this is a hardware issue, or something that can be fixed in the software?
briandichiara said:
Not sure if I need to create a new thread, or post here, but I'm at a loss. I feel like I've wasted a ton of money on this thing. I bought the TF700 over the Galaxy 10.1 thinking it had better specs and was going to be a great product from ASUS. First problem I had was "phantom touches" and had to send it in for repair. Now it's utterly useless. It SUPER slow, so slow that I'd rather throw it in the trash than deal with it. I've tried Clean Master, but it never seemed to help performance. I installed CROMBI-kk and it's still has poor performance. I've set the wallpaper to black (none), removed all widgets, and installed maybe 2 apps so far. I also tried LagFix but it says it doesn't have permission to modify the directories (or something like that). I've ensured that Root is enabled under Developer Options.
My old Incredible (v1) runs better than this. I really don't know what to do. It's very frustrating. I even wasted the money on the keyboard attachment but in combination with the lag, I can't even bear to use it. I downloaded 2048 and swipes are slow, and once the tiles move, sometimes it takes a couple of seconds for the numbers to merge.
Is there ANYTHING I can do? I've looked through the suggestions. Am I missing something? Does EVERYONE have this problem with their TF700? I wrote ASUS about it and basically said "since you unlocked the device, we would have to replace the mainboard for $300 (parts + labor) in order to undergo any out-of-warranty diagnostics." The only reason I unlocked it was because I've heard that the performance problems were due to the ASUS software, so I thought installing a custom ROM would be the answer to my problem.
Any idea if this is a hardware issue, or something that can be fixed in the software?
Click to expand...
Click to collapse
Something is not right mate.
Confirm what boot loader you are on please, which recovery and how you updated the ROM then we can get you setup so experience your tab like never before
sbdags said:
Something is not right mate.
Confirm what boot loader you are on please, which recovery and how you updated the ROM then we can get you setup so experience your tab like never before
Click to expand...
Click to collapse
I followed the instructions in the thread, using twrp-2.6.3-that3_Signed.zip and cm-11.0-20140322-CROMBikk4.4.2-tf700t_Signed.zip. I had already unlocked it a while back with the intention of installing a ROM but never did until yesterday, But I had TWRP 2.3.3.3 installed.
I booted up the tablet, plugged it into the computer, copied over TWRP 2.6.3 (zip) and CROMBI-kk (zip) onto internal storage. Powered down and powered back in into RCK (recovery). First thing I did was an advanced wipe, wiping everything except for the SD card and internal storage. Then installed TWRP from the zip on the storage. Rebooted Recovery. Did the same advanced wipe (x2), then installed the CROMBI zip from within recovery, pretty much leaving all the defaults for the install except for I chose Google Experience Launcher (not sure why, never tried it I guess). That's pretty much it. It installed fine, didn't seem to have any errors or anything odd. Booted up fine, went through the setup process on first boot. Setup 1 Google Account, and installed a few apps (mainly just Chrome and 2048). Other apps installed by ROM were: AdAway, Google+ (for auto-backup), Maps, Hangouts, and I installed SwiftKey. Most everything else seems to be stock.
As far as bootloader, not really sure. When I do the volume-down+power boot, I see Key driver not found.. Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.14.8-20130514" A03. I can get into Terminal Command from TWRP so if I need to run any commands to find out any information, let me know.
Thanks for your response and willingness to help!
briandichiara said:
I followed the instructions in the thread, using twrp-2.6.3-that3_Signed.zip and cm-11.0-20140322-CROMBikk4.4.2-tf700t_Signed.zip. I had already unlocked it a while back with the intention of installing a ROM but never did until yesterday, But I had TWRP 2.3.3.3 installed.
I booted up the tablet, plugged it into the computer, copied over TWRP 2.6.3 (zip) and CROMBI-kk (zip) onto internal storage. Powered down and powered back in into RCK (recovery). First thing I did was an advanced wipe, wiping everything except for the SD card and internal storage. Then installed TWRP from the zip on the storage. Rebooted Recovery. Did the same advanced wipe (x2), then installed the CROMBI zip from within recovery, pretty much leaving all the defaults for the install except for I chose Google Experience Launcher (not sure why, never tried it I guess). That's pretty much it. It installed fine, didn't seem to have any errors or anything odd. Booted up fine, went through the setup process on first boot. Setup 1 Google Account, and installed a few apps (mainly just Chrome and 2048). Other apps installed by ROM were: AdAway, Google+ (for auto-backup), Maps, Hangouts, and I installed SwiftKey. Most everything else seems to be stock.
As far as bootloader, not really sure. When I do the volume-down+power boot, I see Key driver not found.. Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.14.8-20130514" A03. I can get into Terminal Command from TWRP so if I need to run any commands to find out any information, let me know.
Thanks for your response and willingness to help!
Click to expand...
Click to collapse
OK I don't quite understand your advanced wipe decisions. Also what is 2048?
You need to make sure you are at least wiping /data. It may be worth loading CROMBi-kk to microsd and doing a full format on internal which will do data and the whole internal sd - it'll take about 90 mins+ so nmake sure you have enough juice.
The will eliminate any remnants and left overs.
Your bootloader *should* be fine although it is slightly old as the latest one is 10.6.1.14.10 but I don't think that causes any issues. Also make sure you choose _that's kernel in the installer and it doesn't hurt to disable journaling, disable fsync and enable the 2 GPU options.
Finally after it boots go to settings, about tablet and click the build number 7 times to enable developer settings. Then go into developer settings, enable power menu, root and set your 3 animation settings to 0.5x or zero. Last but not least change the runtime from dalvik to art and then let it reboot.
Let it settle. How does it feel now?
sbdags said:
OK I don't quite understand your advanced wipe decisions. Also what is 2048?
Click to expand...
Click to collapse
In the past, I've read to do multiple wipes, but the items I'm wiping should be all except the SD_CARD and Internal Storage. 2048 is a little number game: http://gabrielecirulli.github.io/2048/ (https://play.google.com/store/apps/details?id=com.digiplex.game)
sbdags said:
You need to make sure you are at least wiping /data. It may be worth loading CROMBi-kk to microsd and doing a full format on internal which will do data and the whole internal sd - it'll take about 90 mins+ so nmake sure you have enough juice.
Click to expand...
Click to collapse
When I get some free time, I'll come back and give this a shot. Thanks for all your help.
sbdags said:
Your bootloader *should* be fine although it is slightly old as the latest one is 10.6.1.14.10 but I don't think that causes any issues. Also make sure you choose _that's kernel in the installer and it doesn't hurt to disable journaling, disable fsync and enable the 2 GPU options.
Click to expand...
Click to collapse
I'll make a note of this as well when I go back through this. I'm not sure where I had the choice of kernel in the installer, but I'll make sure I choose _that's. I don't know what those other options are, but again, will keep an eye out for them.
sbdags said:
Finally after it boots go to settings, about tablet and click the build number 7 times to enable developer settings. Then go into developer settings, enable power menu, root and set your 3 animation settings to 0.5x or zero. Last but not least change the runtime from dalvik to art and then let it reboot.
Click to expand...
Click to collapse
Thank you for all this information. When I get some time, I'll give these steps a shot and hopefully be much happier with my tablet. Thanks again!
Fire are so cheap, that's great,but it's so slow even for normal task.
Long time ago,I have found the performance Bottleneck
Of fire is RAM,not CPU,at least for daily normal use like browser web.when I open more than 3 app like chrome videos music play store,the fire become so slow even get stuck, that's really bad.so the problem is It run out of RAM.it only has 1.7G ram for hd 10 and 1.4g for hd 7 or 8. That's really small today.here is solution I found , it's amazing efficient,really make your fire usable even you run many many apps simultaneously.
One word is "swap".
Swap can make you disk storage to be used as RAM,we know disk is slower than RAM,but as I have test, it's OK,you can do it. : )
First get your fire rooted
Next download a terminal I recommend termux,a powerful tool.
Open temux,now you can run many Linux command on you ,run following command:
su
dd if=/dev/zero of=swap bs=200m count=20
mkswap swap
swapon swap
you will creat 200m*20 about 3.5G ram,also,it takes up the same amount storage,but it worth.
to check if you turn on swap run follow command:
exit
free -m
You'll see you ram status include swap
if you dont ru su before,you dont need exit command beacause you are normal user
swap make big diff experience on you fire, now try it
i can run firefox snd chrome and many app at same time at a acceptable speed.amazing!!!
you will
This is my first share on XDA,I think it's really useful, hope help you too : )
iuyals said:
Fire are so cheap, that's great,but it's so slow even for normal task.
Long time ago,I have found the performance Bottleneck
Of fire is RAM,not CPU,at least for daily normal use like browser web.when I open more than 3 app like chrome videos music play store,the fire become so slow even get stuck, that's really bad.so the problem is It run out of RAM.it only has 1.7G ram for hd 10 and 1.4g for hd 7 or 8. That's really small today.here is solution I found , it's amazing efficient,really make your fire usable even you run many many apps simultaneously.
One word is "swap".
Swap can make you disk storage to be used as RAM,we know disk is slower than RAM,but as I have test, it's OK,you can do it. : )
First get your fire rooted
Next download a terminal I recommend termux,a powerful tool.
Open temux,now you can run many Linux command on you ,run following command:
su
dd if=/dev/zero of=swap bs=200m count=20
mkswap swap
swapon swap
you will creat 200m*20 about 3.5G ram,also,it takes up the same amount storage,but it worth.
to check if you turn on swap run follow command:
exit
free -m
You'll see you ram status include swap
if you dont ru su before,you dont need exit command beacause you are normal user
swap make big diff experience on you fire, now try it
i can run firefox snd chrome and many app at same time at a acceptable speed.amazing!!!
you will
Click to expand...
Click to collapse
Yes, adding a static swap file and adjusting 'swappiness' can make a huge difference in responsiveness, especially when multitasking and after wake from extended sleep when many apps attempt to resync. The file does not need to be large and can be placed in the cache partition if desired.
My recommendations:
- 256MB static swap file
- set swappiness to 10
- leave ZRAM swap intact if present
- (optional) set ZRAM priority higher than static file to favor ZRAM storage
Also no need to use obsecure terminal commands. The free app Apps2SD easily handed swap file creation and management.
Davey126 said:
Yes, adding a static swap file and adjusting 'swappiness' can make a huge difference in responsiveness, ...
My recommendations:
- 256MB static swap file
- set swappiness to 10
- leave ZRAM swap intact if present
- (optional) set ZRAM priority higher than static file to favor ZRAM storage
Also no need to use obsecure terminal commands. The free app Apps2SD easily handed swap file creation and management.
Click to expand...
Click to collapse
Which "Apps2SD" does one download? There are quite a few apps with similar name "App2SD".
Is this the one ?
https://www.apps2sd.info/features
https://play.google.com/store/apps/...rce=Website&utm_medium=Home&utm_campaign=Home
Thank you.
Dan_firehd said:
Which "Apps2SD" does one download? There are quite a few apps with similar name "App2SD".
Is this the one ?
https://www.apps2sd.info/features
https://play.google.com/store/apps/...rce=Website&utm_medium=Home&utm_campaign=Home
Thank you.
Click to expand...
Click to collapse
Yep - that's the pup.
{interesting: name varies depending on entry point; author calls it "Apps2SD" but is posted as "App2SD" in the Play Store}
Oh, thanks so much,you introduce me zram, which a More amazing concept,as I have test,it has better performance than swap,now I change to zram,thx,it's better to my disk
its so good to share,bc i get a better one : )
Does anyone know the PROS and CONS, as far as ZRAM is concerned, between Apps2SD and RAMExpander?
See the following post about RAMExpander:
https://forum.xda-developers.com/hd8-hd10/general/best-optimization-hack-experience-t3730239
Thanks.
Dan_firehd said:
Does anyone know the PROS and CONS, as far as ZRAM is concerned, between Apps2SD and RAMExpander?
See the following post about RAMExpander:
https://forum.xda-developers.com/hd8-hd10/general/best-optimization-hack-experience-t3730239
Thanks.
Click to expand...
Click to collapse
Apples and oranges. Apps2SD is simply a tool that provides GUI for defining and managing static swap files. RAMExpander appears to do the same thing with predefined (and excessive IMO) values. ZRAM is a seperate beast that is best left alone unless one is familiar with Virtual Memory Management and the various interactions that take place between tuneables.
-- I accidentally posted in the wrong thread, sry --
Davey126 said:
Yes, adding a static swap file and adjusting 'swappiness' can make a huge difference in responsiveness, especially when multitasking and after wake from extended sleep when many apps attempt to resync. The file does not need to be large and can be placed in the cache partition if desired.
My recommendations:
- 256MB static swap file
- set swappiness to 10
- leave ZRAM swap intact if present
- (optional) set ZRAM priority higher than static file to favor ZRAM storage
Also no need to use obsecure terminal commands. The free app Apps2SD easily handed swap file creation and management.
Click to expand...
Click to collapse
Is this (attachment) ok?
Oco said:
Is this (attachment) ok?
Click to expand...
Click to collapse
That works! Don't expect miracles. Still a low resource gizmo; reading/writting to static swap is magnitudes slower than memory based zram. But it does allow the OS to swap when needed without thrashing. Setting swappiness to 10 encourages the retention of processes in memory while reducing the chance of exhusting available swap space. If that happens the device will become a complete dog due to thrashing on slow file based swap; a reboot will fix things up.
Davey126 said:
That works! Don't expect miracles. Still a low resource gizmo; reading/writting to static swap is magnitudes slower than memory based zram. But it does allow the OS to swap when needed without thrashing. Setting swappiness to 10 encourages the retention of processes in memory while reducing the chance of exhusting available swap space. If that happens the device will become a complete dog due to thrashing on slow file based swap; a reboot will fix things up.
Click to expand...
Click to collapse
Thanks, is this the same for fire 8 and fire 7?
Oco said:
Thanks, is this the same for fire 8 and fire 7?
Click to expand...
Click to collapse
Yep with caveats. Haven't messed with Fire 8 (2018) virtual memory as stock settings/performance are adequate for my current needs. Wake lag on the HD 8 is non-existent with my app portfolio which was the driver for adding a static swap file on the Fire 7. As a general rule I avoid turning knobs and dials unless there is a benefit that offsets the effort and potential side-effects.
Davey126 said:
Yep with caveats. Haven't messed with Fire 8 (2018) virtual memory as stock settings/performance are adequate for my current needs. Wake lag on the HD 8 is non-existent with my app portfolio which was the driver for adding a static swap file on the Fire 7. As a general rule I avoid turning knobs and dials unless there is a benefit that offsets the effort and potential side-effects.
Click to expand...
Click to collapse
Agreed. While I have no experience with other Fire tabs, the Fire 8 HD 2018 is way better than I expected after reading some of the threads in this forum. I have now disabled the major bloats but find no big difference in either speed or battery drain.
Hi guys. I am late to this thread, of course.
Can anyone tell me how to root the fire 7 9th gen which runs on version 7.3.1.8?
I see that the fire 7 can run way faster because of the methods above but my device can't be rooted because it seems it can't be rooted by where I looked to root it.
All Fire tablets are entry-level that aren't intended for multitasking.
AmznUser444 Dev said:
All Fire tablets are entry-level that aren't intended for multitasking.
Click to expand...
Click to collapse
I see. So you are saying that they can't be rooted? Like the version I have right now? Just wanting to change the swap.
Animate Blade said:
Hi guys. I am late to this thread, of course.
Can anyone tell me how to root the fire 7 9th gen which runs on version 7.3.1.8?
I see that the fire 7 can run way faster because of the methods above but my device can't be rooted because it seems it can't be rooted by where I looked to root it.
Click to expand...
Click to collapse
Try kingroot.
kwanbis said:
Try kingroot.
Click to expand...
Click to collapse
Does it work? Did you have experience of it? I'll see though and come back With some info on it.
Animate Blade said:
Does it work? Did you have experience of it? I'll see though and come back With some info on it.
Click to expand...
Click to collapse
I just flashed LineageOS 12.1 on my two FireHD10. The first one I had blocked the OTA updates so I was able to install TWRP following this guide:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire HD 10 2017 (suez)
Read this whole guide before starting. This is for the 7th gen Fire HD10 (suez). Current version: amonet-suez-v1.1.2.zip NOTE: This process does not require you to open your device, but should something go horribly wrong, be prepared to do...
forum.xda-developers.com
But for the second one, I had forgotten to block the OTA updates so the first step which requires root was not working. I used kingroot to root it first and then followed the guide I posted above.
I did the soft brick to downgrade and then I installed LineageOS 12.1
[discontinued][ROM][unlocked][suez] Lineage-12.1 [05 MAY 2020]
Disclaimer /* * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. * Please do some research if you have any concerns about features included * in the products...
forum.xda-developers.com
I did it 2 or 3 days ago.
so I got a Sky Devices Elite OctaX from the government for free w/ Service, but the thing acts like it's rooted, but it iisn't all. Anytime I put a game on it, it thinks it's rooted and boots me out of the game. I checked all the usual culprits like if Developer mode was on (it wasn't), if USB Debugging was on (it wasn't) and other things that potentially could trip the program into thinning it's rooted. I don't know what to do with this tablet at this point: I don't know how to install TWRP to install a new rom on it to use as loophole, mainly because there is no supported version for it; same with it adding Magisk as well, so any "safe" rooting ways are out of the question and now im left with the "One Button" methods, sadly.
so Does anyone have any advice as to what to do with the tablet?
A device's Android is rooted when SU binary ( either as part of BusyBox or as part of ToyBox or as standalone ) is present in Android's filesystem and made executable.
It's easy for any app to detect the presence of an executable SU binary.
xXx yYy said:
A device's Android is rooted when SU binary ( either as part of BusyBox or as part of ToyBox or as standalone ) is present in Android's filesystem and made executable.
It's easy for any app to detect the presence of an executable SU binary.
Click to expand...
Click to collapse
so what are my options to get around this? It's a REALLY good tablet, but this has soured me on it, and I demand a refund... despite it getting it for free.
I don't know if this is allowed, but im bumping to see if anyone has an answer to help me with this.
Ramses83 said:
I don't know if this is allowed, but im bumping to see if anyone has an answer to help me with this.
Click to expand...
Click to collapse
If unsure just review the XDA Forum Rules; in case of your question please refer to rule no. 5. Affirmative, you're allowed to bump your question once every 24 hours.
Regards
Oswald Boelcke
Senior Moderator
Bless you good sir
bumping for justice!!
bumping till we can get this done! I believe in you all!
I still believe in you! bumping for hope!
bump
morning bump!
evening bump
Bumping with a result from root beer
bump
bump
still need help with the device.... I've made some advancements, like the reason why it keeps turning off apps is because it has insufficient memory... which is weird since it should have enough memory to run stuff.... im just confused, I think putting in a lower end rom would fix it... maybe. I don't know
Each Android smartphone comes with a fixed amount of RAM. It is part of the phone’s motherboard and it's not configurable by ROM settings. Also Android OS itself takes from this inbuilt RAM ~600 MB, hence device's available RAM is always far lower. So switching to another ROM - as intended - doesn't solve memory problems you may have, IMO.
In Android, each app's program runs in a self-contained VM that is by default assigned a certain amount of RAM ( read: heap ) - typically 128 / 256 MB. This amount is defined in Android's system file called build.prop. To this app-reserved RAM must be added the RAM required by an app's data.
E.g. games like Need for Speed: No Limits or PUBG Mobile can use between 800 MB and 1152 MB in total.
I either have the same tablet or the non elite version, but on mine there is an engineer mode app the opens with a shortcut launcher. There is an adb shell executor that executes commands not as shell but as system so I imagine you can use that to get done what you're trying to do.