Related
I'm looking for beta testers for a new App2SD implementation that does not require your MicroSD card to be partitioned which is potentially unsafe and can result in a loss of your data. If you'd like to test this new implementation before it's release here on XDA shoot me an email at [email protected] with what firmware and version you're using.
More information will be released after I get a few positive beta tests out of the way.
loopback device, eh?
I tried that a while back but never could get the loopback driver to load early enough in the boot process reliably.
Hope you have better luck than I did.
As [email protected] pointed out to me a while ago, this is not a good idea for security reasons. If your loopback file sits on the FAT partition, it is accessible by all of the apps, it can be read, overwritten and deleted by a rogue app bypassing the entire android security model. If this is what you intend to do, it's probably not "safer".
Hey, shot you an email. Ready to try it out. But only for beta.
Hit me up, I have no apps to lose.
But security? Idk just let me know whats up.
what happens when you mount the SD card to your computer?
I'd like to try it, but i don't yet have a class6 sd card. Is that necessary?
i'd be willing to give this a shot. I have no data to lose as well.
southsko said:
what happens when you mount the SD card to your computer?
Click to expand...
Click to collapse
That's true. Won't all your apps disappear when you mount the SD?
This smells fishy not many app developers with 1 post can this be someone testing their new exploit/virus?No offense to original poster im just sayin....???
Edit:Sorry to OP clearly not a virus,and good luck on getting it stable I will gladly donate to your cause partitioning is a pain!
don't be a jackass, many people have had great ideas and decided to come to XDA to share them. just because you are a complete idiot who can't program does not mean that the OP is too.
@@OP
you are playing with fire my dear friend. i don't think that mounting your apps on the FAT32 partition is a good idea at all. not only because it would allow any program to access and write without asking android permission first, but because it would allow people to mount the SDcard and steal paid apps even easier. i beg of you please rethink your idea
I imagine the phone would be crashing when the phone is mounted to the computer. lol. just kidding. =]
tubaking182 said:
don't be a jackass, many people have had great ideas and decided to come to XDA to share them. just because you are a complete idiot who can't program does not mean that the OP is too.
Click to expand...
Click to collapse
WTF?Just came back to edit my post and put that its for real cause like I should have done first I found this http://noderat.com/loop2sd/.But as for your insults who the hell are you?How the f**k do you know what I can or can not do?I was posting in the first place to start trying be more active in the forums no reason for you to be a **** anyways,I was tryin to help people not get what I thought may have been a virus was that really that bad?
i'm not sure that is 100% true. when i mount my phone(apps2sd) my phone decides to mount the ext2 partion and the FAT32 partition, i am using ubuntu so my computer is able to read the partition, but my phone doesn't crash(i've yet to try running an app while mounted though)
Android can acces the sdcard while mounted.
Try terminal emulator.
crotalusfreak said:
This smells fishy not many app developers with 1 post can this be someone testing their new exploit/virus?No offense to original poster im just sayin....???
Click to expand...
Click to collapse
Well, take it from someone who has many posts and 15 years of unix experience, it is a bad idea.
Most of the devs here had this same idea, but as I mention in my previous post, this is opening yourself up to many bad security issues. To all those who answer, "I have no data to lose", that's fine as a beta tester. But what's the point in beta testing something that cannot be safely used by anyone who does have data (or apps) to lose?
I should point out to those who perhaps do not realize some the consequences of my original post, that it is not just a potential data loss problem, but a potential arbitrary code execution vulnerability. If an application manages to replace the loopback file with a new loopback file, it could inject altered common applications. If this succeeds, it means that previously trusted applications which have been granted privileges (or root using the various su apps) at install time, could be replaced with trojan versions which can have complete control over your system... steal your passwords... reflash your bootloader and literally install a permanent trojan... brick your phone... <insert other scary things besides data loss here>.
It's your phone, do what you want. I just figured that I would re-post that this not a new idea, but one that has been rejected by those of us with unix experience who realize the consequences. If you are just messing around, go ahead, it's not likely to hurt your phone. But, as a general method to build upon and be depended on, this should not have a future. If this becomes common practice, it is highly likely that exploits will be written to take advantage of this vulnerability.
So, if you are asking yourself if something is fishy, yes something is: it's a logical idea which seems great on the surface, but it has an unfortunate flaw.
Note: I am not suggesting malicious intent on the OP's part, just that they may not have thought of the consequences of suggesting this as a common method to do apps2sd. And if the OP (or someone else) is able to point out a method to avoid the things I warn against I will happily retract my statements (if I agree that this method would indeed work) since this method has some obvious benefits. However sadly, I think that is highly unlikely.
maxisma said:
Android can acces the sdcard while mounted.
Try terminal emulator.
Click to expand...
Click to collapse
No it can't. It can only access the empty mountpoint.
If you want to do this, there IS a way to make it work SAFELY....
Find the functions that control sdcard mounting and unmounting and FIX it so that it will mount an ext2 first partition. Then forget about the whole loopback thing as thats not going to do anyone any good... If you do it like this, then unionfs it, then unmounting the sdcard should safely vanish the apps that are stored on the card (leaving the internally stored apps), might crash the launcher, but that'll restart immediately and won't even error out.
A second step in the right direction would be to find the place where programs are detected from, which currently looks in /data/app, /data/app-private, /system/app, so it can clearly handle loading software from multiple locations -- add in a new path. Or maybe link app-private to /sdcard... A little more challenging would be to allow it look in multiple locations for thing that are ALL currently in /data/data and /data/dalvik-cache.
And then when its done, submit a patch for the source.
Wow what a response. Here's a few key bulletpoints:
I'm not a forum poster, not the kinda person for it but I have been on XDA Dream since I got my pre-launch G1 as a CSR.
There are potential security flaws with the current ext2 method of a2sd, and bypassing root to mount the ext2 partition is possible.
a2sd is not stable in any format, so it's a use at your own risk until android improves kinda deal.
I'm not cool enough to write a virus, but thank you for the ego boost
Anybody using a third-party firmware is not safe nor secure. If you're reading this forum you're not safe nor secure. The idea of homebrew roms is to add extra features that are not in Android to begin with and with that comes security risks. No ROM is ever perfect but I'd trust a Google or T-Mobile rom with my security before any homebrew-anything.So yes it's use at your own risk
This has the same results for mounting on a PC as MarcusMaximus's a2sd.sh
This doesn't really make it any easier to steal paid apps, it's always been easy and always will be but this doesn't change it.
If you guys have other questions shoot me an email, like I said I don't really do much forum-posting (never had much of anything to say, maybe this'll change all that)
[email protected]
JakeEv said:
I'd like to try it, but i don't yet have a class6 sd card. Is that necessary?
Click to expand...
Click to collapse
The faster the better but I've done it with the stock card that came in the G1 as well as a Class 6.
id try it since i can not get apps2sd to work.
[email protected]
using JF 1.51
So I check my Xoom out this morning and Boom "Low on Space 'Tablet storage space is getting low'. It is impossible that I filled all of the space. I looked at my breakup and i have about 6Gb of music and it says the rest is completely full due to applications. I look at my applications but I only have about 3GB worth of application and data attributed to saves (manually counting). For the most part, besides the stock honeycomb apps, these apps are the same that I have on my Droid1. Which has much smaller storage. Somehow some app is taking up all the space (which i can't identify), the OS is corrupted, or I have a virus. Everything else has been pretty mainstream applications.
I have the OTA update and my Xoom has never been rooted.
Is anyone else having this problem?
A lot of people got this issue. It is being discussed in the Motorola official Xoom forum. But still no one know what's the root cause.
Sent from my Nexus S using XDA App
gogol said:
A lot of people got this issue. It is being discussed in the Motorola official Xoom forum. But still no one know what's the root cause.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. I guess its good to know I'm not the only one. Hopefully it gets fixed soon.
The link to the issue on the moto forums is
https://supportforums.motorola.com/thread/46601?start=0&tstart=30
Hi Everyone,
For those users not yet experiencing this but wants to see whats going on, I made a video. There is also a way to check to see if this is occurring to you by checking out your internal storage on the Xoom.
http://www.youtube.com/watch?v=tWFeq0Qj3iA
Is there anyone else experiencing this issue on their Xoom?
It happened to me last night while playing WordFeud. I get the two line message "Low on space" and "Tablet storage space is getting low"
There is no way that I am using 25 gig in applications.
Thanks,
Dan
My initial guess is that it is Application specific. My xoom has 628Mb for Applications. I think maybe some app that each of you is using is continuing to pull in data and not deleting it over time. Maybe something like a news stream or something else. I would chat with the others having this problem and see what similar apps you have.
Just a thought. Sounds odd, I agree.. but.. a place to start. Maybe akin to a memory leak.
Thanks for the quick reply, eaglecomm. Your suggestion makes sense. In looking around a little this morning, I see that some people thought it might be the Google Body app, which I had installed. I uninstalled it, but it didn't make a difference.
It turns out that there is a fix coming in the next update.
The thread is at the Motorola Owners Forum titled 'XOOM Storage is Full' problem - 47 apps takes up 27 GB?
Since I am a new member here, I cannot post the actual link.
I thought I would post this info for any other Xoom owners that are have this concern.
I am glad to see it is being addessed.
Thanks,
Dan
My Xoom is not indicating that it is low on storage, but the applications do seem to be taking up an inordinate amount of space. Funky little bug.
On a positive note, it is good to know that the functionality of this device will only get better over time.
Tombstones
Are any of you able to look at the sizes of the files in /data/tombstones? I had the same problem and did some digging and found a tombstone file that is 19 GB. It appears to have been generated by a browser crash. If any of you are having the problem can you open a terminal and go to /data/tombstones and find the biggest file and type cat (name of biggest file) and tell us the name of the process (listed after pid). You may need to be rooted and may need busybox for cat to work. I doubt it's only the browser... I'm curious to know if it's a honeycomb thing with how it tombstones app crashes.
Have you tried using a cache cleaner ? I use 1 Tap Cleaner and Fast Cache Cleaner .
Try using DiskUsage to view what is using up your storage. If you're rooted it gives you even more options to view specific folders. If you've ever used WinDirStat then this is the closest thing android has to it that I've found.
https://market.android.com/details?id=com.google.android.diskusage
Although Moto is promising an update "soon" to fix this, the problem has been getting reported on for over 45 days now. Some people were hit with this early and some more recently - like myself. This one was sort of the last straw for me. I had to do a factory reset on mine (in Settings) in order to resolve this issue; which hasn't reared its ugly head again since. However, between that mess, and no SD card, SMS, etc, I finally got fed up and rooted mine so that I could use the Tiamat kernel and at least add a 32 GB SD card in the slot provided. Rooting also allowed for Clockwork Recovery (which I love) so making modifications is much easier. If and when Motorizon decides to provide us with the 4G update, then I'll flash it back to stock. However, in the right here and now, I needed a tablet for my work and didn't have the luxury to sit around with my hands tied and wait for Moto to finally have pity on us and provide what they hyped us with. The XOOM has become too integral a part of my work and home life. The product answered a lot of needs - some I didn't even realize that I had. I'll just have to do the extra step now of flashing back to stock when (and if) update time finally comes around. Until then, I'm moving forward and I've got WORK to do!! Yippee kyy-yaayyyy!!
I have this problem and looked in my folders trying to find large files using ES File Explorer. I have found a repeating set of folders here:
/sys/module/usbhid/drivers/hid:generic-usb/module/drivers/hid:generic-usb/module
These folders keep going and going and going. I tried to look at the properties of the sys/module folder but the file size kept going and going and going. I ran it all night and it was still running in the morning at 1.25GB and counting. Is it safe to delete the repeating set of folders? Does anyone know what these folders are used for?
Deanne
DeanneJensen said:
I have this problem and looked in my folders trying to find large files using ES File Explorer. I have found a repeating set of folders here:
/sys/module/usbhid/drivers/hid:generic-usb/module/drivers/hid:generic-usb/module
These folders keep going and going and going. I tried to look at the properties of the sys/module folder but the file size kept going and going and going. I ran it all night and it was still running in the morning at 1.25GB and counting. Is it safe to delete the repeating set of folders? Does anyone know what these folders are used for?
Deanne
Click to expand...
Click to collapse
Looks to me like a recursive bug where the folder or device is continually being created inside itself, it would cause everything from unstable os to complete unresponsiveness and even filling up the storage.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
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!
Couple notes:
- Root didn't survive the update. SuperSU's survival mode failed. I did not have to roll back root to update though.
- Powered by Android appears on the start up.
- Gamestreaming connectivity was lost; you'll have to reauthenticate to your PC.
Anyone find anything else "unlisted"?
Shield RAM's ROOT method appears to work fine with this update.
KitKat SD card fix has to be reapplied.
I was hoping this would fix the emulator slowdowns, but has not. The CPU fix impacts battery life and would rather the device work as intended without doing a "fix". Exception being the sd card fix, since that is a Must.
rushless said:
I was hoping this would fix the emulator slowdowns, but has not. The CPU fix impacts battery life and would rather the device work as intended without doing a "fix". Exception being the sd card fix, since that is a Must.
Click to expand...
Click to collapse
what Emulator slowdowns do you mean?
darkuni said:
Shield RAM's ROOT method appears to work fine with this update.
KitKat SD card fix has to be reapplied.
Click to expand...
Click to collapse
I am new to the SHIELD community, could you please link me to the fix and maybe explain in a few words what this fix fixes? Thanks
Martin-Doc said:
I am new to the SHIELD community, could you please link me to the fix and maybe explain in a few words what this fix fixes? Thanks
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
Essentially, KitKat prevents apps from WRITING to the SD card unless the app is the one that created the folder to begin with.
So let's say you have:
\sdcard\roms\n64
... on your SD card where you keep all your Nintendo 64 roms (insert standard piracy disclaimer here).
Your N64 emulator can no longer WRITE to that folder. Why does this bite? Well most emulators use the rom folder to unpack ZIPped roms, store save states, configuration per game - that sort of thing. Suddenly, after installing KitKat - these emulators start acting weird or outright crashing because they can't write where they used to be able to.
You could have a folder of .DOC files in
\sdcard\docs\
Your Polaris Office could open the files there, but if you edit them, you can't save them back.
You can extrapolate this to just about every app.
The KitKat fix linked above will make it work the way it used to work - so you don't have to change, update, or alter anything.
It does require ROOT access of course.
nex86 said:
what Emulator slowdowns do you mean?
Click to expand...
Click to collapse
All of the Broglia emulators slow down. He says it is the Nvidia update, but all I know is they play better than Retroarch and the other options. Better performance and options. They play great as if with 4.2.
Shield does what I need, so no harm no foul as is
Would like console mode though.
oh you mean like snes9xEX?
I will try that one out later.
nex86 said:
oh you mean like snes9xEX?
I will try that one out later.
Click to expand...
Click to collapse
yeah snes9x is one of the best emulators out for SNES imo.
I tried Snes9Xex, MD,emu and GBA.emu and have no slowdown at all, works perfect for me.
I do notice some slight skipping though when camera scrolls in game, but maybe that's just me..
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.