Related
Example:
http://www.cyrket.com/package/com.google.android.stardroid
As a developer, I am sick of the stream of spammorhea from users who are downrating apps that are crashing not due to poorly written code but because the user installed A2SD. You install and use A2SD at your own peril. If you are using A2SD and you experience force closes when non-A2SD users are not, I guarantee you 99% of the time it is because you are using A2SD.
DO NOT REPORT CRASHES OR FORCE CLOSES TO APP DEVELOPERS IF YOU ARE USING A2SD.
Developers have enough on their plate without having to troubleshoot the problems of users who are using extremely non-compliant Android environments. Uninstall A2SD and try again, go read a book, or shoot yourself in the head, but ffs do not report your crashes.
or like the people that rate 1 star on an app that says for cupcake only and they don't have cupcake. and complain it don't work.
one thing i just noticed since you posted the sky map app, i'm assuming your saying that program won't run with apps2sd. i have apps2sd and when i click on the app in my app list it pops up saying program not installed (guessing since running off sd). but i put it on my desktop and ran it it worked. any explanation.
whoops
this thread just forced closed, no apps to sd...???
supremeteam256 said:
any explanation.
Click to expand...
Click to collapse
That's part of the problem. Some folks are using symlink version, others are using unionfs version. Some have just /data/apps moved, some have dalvik-cache moved, some people move entire /data. Worse than the fact that A2SD mod is inconsistent with the standard android environment, each user's A2SD environment itself is also inconsistent with other A2SD users.
This kind of unorganized and mostly untested hack is a huge freaking headache for developers. Hackers generally release hacks as-is. That means that they usually don't need to have the hack thoroughly tested before release (part of the reason being they let the community do the testing). On the other hand, app developers, for the most part, have to provide support for their products. This support makes presuppositions about the user's Android environment, such as the security of the /system folder, the location of dalvik-cache, etc.
When taking a device outside of the boundaries of the official Android environment (that is to say by rooting and installing unsanctioned hacks), a user needs to understand that he/she may be causing program instability. Inexperienced users who install A2SD and other experimental hacks and then improperly attribute crashes to downloaded apps are hurting both the hacking community as well as the app community.
I concur. 90% of recent posts are newbies with no linux experience complaining about A2SD not working. It's no wonder JF stopped being involved on the forum.
I'm running JF v1.5 with my apps and dalvik-cache moved to sd (not data though) and just downloaded that star app. Works perfectly fine. I didn't use an app to move my a2sd though, I did it through adb.
While I understand the poster's frustration this topic could/should simply be narrowed down to a rant about people rating apps based on user error or poor judgment.
The large volume of rooted/apps to sd users in the android community is directly proportional to the poorly thought out memory amounts of the G1 phone. So in this case there will continue to be a lot more average joes to contend with.
So, before the Newbs are burned at the stake remember this is a symptom of a problem created by the very progenitors of the Android platform, they are responsible for the hordes of ill equipped G1 toting Linux newbs.
wyseman76 said:
The large volume of rooted/apps to sd users in the android community is directly proportional to the poorly thought out memory amounts of the G1 phone. So in this case there will continue to be a lot more average joes to contend with.
Click to expand...
Click to collapse
Seems like you're confusing proportionality with causality. However, sure I completely agree that a lot of the hacks on the xda-dev forums are a result of hackers wanting to fill in the gaps of stock Android. Necessity is the mother of invention, as it were. To that extent, I am not against the unsanctioned development of hacks for Android. In fact, I wholeheartedly support it. Android's openness (despite root-jails for carrier branded phones) is one of its unique strengths.
What I am railing against is newbies who jump right into a hack without reading the instructions and hackers who release hacks without enough testing or carefully written and concise documentation. That's somewhat like giving a loaded gun to a toddler. (Sorry for the melodramatic and cliche simile.)
i agree totally- i try and mark those kind of messages as spam on the market,.... i wonder how people actually rooted their phones if they are unwilling to read a bit more info.....
I've run both the symlink version of A2SD and the unionfs version. I set up both from command line, not the apps. I have no issues at all with Google Sky Map or indeed any other programs at the moment.
Personally, I blame the A2SD apps for the problems other users are having.
Hi,
I use 5.02h R4 app2sd with the above method and no problems with force closes with 65 apps installed.
It helps to use a class 6 card also.
Just used basic command lines, no scripts.
DOHCtor said:
I'm running JF v1.5 with my apps and dalvik-cache moved to sd (not data though) and just downloaded that star app. Works perfectly fine. I didn't use an app to move my a2sd though, I did it through adb.
Click to expand...
Click to collapse
DOHCtor said:
I'm running JF v1.5 with my apps and dalvik-cache moved to sd (not data though) and just downloaded that star app. Works perfectly fine. I didn't use an app to move my a2sd though, I did it through adb.
Click to expand...
Click to collapse
I used the script and have everything moved to my sdcard. The result after installation of the app was an error message stating Sky Map wasn't installed. I then decided to reboot and the app worked fine.
Just an addition to my post, I moved everything to SD - dalvik-cache, /data/data etc and no problems at all.
The browser force-closed on me, where can I rate it 1*?
I have a feeling that a lot of the crashes/force closes are due to the speed of the SD card. Let's face it the OS expects a certain read speed and the SD cards can't quite keep up (class 6 works most of the time). When the OS issues a command and it doesn't execute in a given amount of time it assumes the app has crashed and posts a message asking if you want to force close it. Of course the correct answer is to hit wait.
It would be nice if the OS hackers could find out where this time limit is set and tweak it to be a bit more forgiving. This would probably solve a whole lot of problems people are seeing.
JaboJG said:
I've run both the symlink version of A2SD and the unionfs version. I set up both from command line, not the apps. I have no issues at all with Google Sky Map or indeed any other programs at the moment.
Personally, I blame the A2SD apps for the problems other users are having.
Click to expand...
Click to collapse
I am using JS 1.5, and I created the Symbolic Links using the Terminal Emulator. I moved Apps and Apps-Private. And Removed the respective folders from System. 95% of my apps work as is, I think I had to remove a couple for cupcake reasons, no biggie.
That SKY Program didn't work for me. I am going to try reinstalling it, and see what happeneds. Otherwise someone here said they also moved Dalvik-Cache, I may try that. I was assuming this was always a Cupcake Compatibility problem.
Edit: Using Class 6 MicroSD Formatted 7.5Gb FAT32 / 450MB Ext2
Just throwing in a my 2 cents. I have no problems with A2SD. Only issue that i've had is with open home, seemed like it slowed everything down. Never force closed just seemed slower than when it was ran normally.
Rekna said:
I have a feeling that a lot of the crashes/force closes are due to the speed of the SD card. Let's face it the OS expects a certain read speed and the SD cards can't quite keep up (class 6 works most of the time). When the OS issues a command and it doesn't execute in a given amount of time it assumes the app has crashed and posts a message asking if you want to force close it. Of course the correct answer is to hit wait.
It would be nice if the OS hackers could find out where this time limit is set and tweak it to be a bit more forgiving. This would probably solve a whole lot of problems people are seeing.
Click to expand...
Click to collapse
I don't think this is always the issue though. Specifically with this App on my phone. Wait will do nothing. As soon as you launch the App, it come up with Force Close Immediately. Almost like it expected to find data / something, somewhere and didn't so it had to close.
I dunno if this is a possibility with Symbolic Links, but maybe it saw the Symbolic Link and instead of following it, saw it wasn't a directory and crashed? While it was looking, or trying to store cache data perhaps?
I must say, trying to go to appstosd was one of the biggest headaches Ive ever experienced hugely because of the problems listed here. I have been through just about problem you can experience with appstosd and because I wanted to understand what was going on I finally figured it all out and have been able to run appstosd flawlessly for days now. All you need is to accept trial and error and BACK EVERYTHING UP!!!
Update 03/08/11
NotEnoughSpace has finally graduated to the Android Marketplace!
Beta testers can currently get it at its "thank you" price of $0.99.
I will set the regular price in a week so hurry
*** *** *** ***
Note #1: your phone needs to be ROOTED to use this application.
Note #2: so far, only tested on Droid Incredible and HTC Desire.
From the built-in help:
About this application
This application's goal is to help you understand and possibly work around a common vexation of using Android; i.e. these messages:
"not enough space"
"Low on space. Application data space is low."
What is happening?
You've checked your phone's vitals and it appears that it has plenty of space left, both internal storage and SD Card storage. So, what's happening?
Android allows your applications to store their data, primarily, in a dedicated partition whose size happens to be much smaller than even the phone's internal storage space. Generally south of 150 MBs.
This is the partition that fills up so quickly and that Android has been complaining about.
And the help goes on and on so I'll stop here.
The short version
Using this application, you can see which applications use up most of your phone's data space and decide what to do with them.
You can also move the biggest directories to the phone's SD Card.
Additionally, you can use the app to cleanup the Dalvik cache but it's not the app's primary function.
Please, help test it!
I will gladly welcome any constructive criticism; I expect most of it to be along the lines of "The tool is not quite accurate" and that's what I wish to address first.
To create a debug report (these are very important):
Simply select the "Debug" menu and follow the on-screen instructions.
The whole email business is so that you can copy/paste from a desktop client.
The .apk can be downloaded from nexus.zteo.com/projects/beta/
Update 12/04/10
The application should now display correct stats for phones/ROMs that use Busybox. If you have already tested it and it said "NaN" please try it again.
This should be interesting, maybe kinda Android GpartED?
cyansmoker said:
Using this application, you can see which applications use up most of your phone's data space and decide what to do with them.
You can also move the biggest directories to the phone's SD Card.
Click to expand...
Click to collapse
Curious, does this mean you can move and symlink data, or are you talking about Froyo Apps2SD?
teorouge said:
This should be interesting, maybe kinda Android GpartED?
Click to expand...
Click to collapse
Obviously not, he's managing what's there, he's not partitioning anything.. Did you read?
khaytsus said:
Obviously not, he's managing what's there, he's not partitioning anything.. Did you read?
Click to expand...
Click to collapse
Come on, what's the matter dude? I did read, and from what I read I thought whole partition handling was the only thing this app would be missing. Single files is a good start, but making that "kinda GpartED" would be killer. Though I fear you should be in bootloader/recovery to work on those, don't know how Android deals with them (i.e. in Windows you have programs you can change partitions size "on the fly" with). Now that I elaborated more, are you still angry?
This application would be genius. I'm wondering however, will the phone still be able to access that data once it is moved off of the system memory and onto the SD Card? And is it possible to actually partition the /data/data section so that it will use more than the allowed 150mb that it has, like open it up so that instead of it being partitioned to a small amount, it just roams free with the rest of the 748mb or whatever that is in the system memory.
A promising app, thanks.
Navigon, however, doesn't like its data to be moved to SD card. Even after moving it back with the app, it FCs (Android 2.1). I think I have to reinstall. So be careful if you're trying to do the same.
Edit: After reinstalling the .apk (without doing anything with the maps), Navigon works again. The packet installer didn't ask me if I wanted to replace the existing installation (as is otherwise usual in such a case).
Edit2: There seems to be a general problem. The next app I tried was mediaU. It has a large database which I moved (using NES) to the SD card. It also FCed after having moved its database, and restoring to the old location (again using NES) also didn't succeed. No error message during restore, but app still won't run.
Phone: Galaxy 3, Android 2.1 (original ROM).
mizch said:
A promising app, thanks.
Navigon, however, doesn't like its data to be moved to SD card. Even after moving it back with the app, it FCs (Android 2.1). I think I have to reinstall. So be careful if you're trying to do the same.
Edit: After reinstalling the .apk (without doing anything with the maps), Navigon works again. The packet installer didn't ask me if I wanted to replace the existing installation (as is otherwise usual in such a case).
Edit2: There seems to be a general problem. The next app I tried was mediaU. It has a large database which I moved (using NES) to the SD card. It also FCed after having moved its database, and restoring to the old location (again using NES) also didn't succeed. No error message during restore, but app still won't run.
Phone: Galaxy 3, Android 2.1 (original ROM).
Click to expand...
Click to collapse
Tonight I'm gonna try for sure and report back, this does look promising! Did you succeed with some apps?
teorouge said:
Did you succeed with some apps?
Click to expand...
Click to collapse
K9 seemed to work. However, I had to reflash for another reason, and now K9 reports its lib as being in the standard location (reported by NES). For now, I have stopped testing NotEnoughSpace so I can not say more.
mizch said:
K9 seemed to work. However, I had to reflash for another reason, and now K9 reports its lib as being in the standard location (reported by NES). For now, I have stopped testing NotEnoughSpace so I can not say more.
Click to expand...
Click to collapse
eh? K9 has native use of the SD card if you enable it... Why would you use this on it?
Thanks for doing this testing, guys.
I will install these apps and test them myself.
teorouge: you moved the database/ directory, is that it?
mizch: so, you re-installed K9 after reflashing, right?
Everybody: what about the "free space" numbers reported by the app? Do they seem correct to you? I had to use a dedicated algo to compute them, taking block size in account, and I've had reports of fairly surprising discrepancies.
Free space doesn't seem to update after moving, though I see the difference in the Titanium Backup count: tried for a couple of apps (G Earth and well... don't remember!) and it did move everything, free up space on /data and I can still use those apps. Still afraid to move many apps, just moving one at the time and test.
I just tested it out on my Droid 1, which is running CM6.1RC5 (Not sure if thats relevant or not), and it doesnt seem to work very well on my phone. All apps came back as 4KB, at the top it showed this... Total:261.8MB Used:NaNKB Free: 259.1MB Database NaNKB Files: NaNKB Preferences:NaNKB Cache:NaNKB.
Heres the debug report: 1:/dev/block/mtdblock6 268032 224572 43460 84% /data
2:62855 /data/data
3:4096/0/265352
Sorry - never mind; found the info in FAQ.txt after downloading
cyansmoker said:
Note #1: your phone needs to be ROOTED to use this application.
Note #2: so far, only tested on Droid Incredible and HTC Desire.
From the built-in help:
About this application
This application's goal is to help you understand and possibly work around a common vexation of using Android; i.e. these messages:
"not enough space"
"Low on space. Application data space is low."
What is happening?
You've checked your phone's vitals and it appears that it has plenty of space left, both internal storage and SD Card storage. So, what's happening?
Android allows your applications to store their data, primarily, in a dedicated partition whose size happens to be much smaller than even the phone's internal storage space. Generally south of 150 MBs.
This is the partition that fills up so quickly and that Android has been complaining about.
And the help goes on and on so I'll stop here.
The short version
Using this application, you can see which applications use up most of your phone's data space and decide what to do with them.
You can also move the biggest directories to the phone's SD Card.
Additionally, you can use the app to cleanup the Dalvik cache but it's not the app's primary function.
Please, help test it!
I will gladly welcome any constructive criticism; I expect most of it to be along the lines of "The tool is not quite accurate" and that's what I wish to address first.
To create a debug report:
Simply select the "Debug" menu and follow the on-screen instructions.
The whole email business is so that you can copy/paste from a desktop client.
The .apk can be downloaded from nexus.zteo.com/projects/beta/
Click to expand...
Click to collapse
Do you have more details about this program anywhere? I went to the download page but see no further info...
Help Section Typo
Under A Quick user guide in your user guide(?) that prompts when you run the apk for the first time there is a typo in the last sentence:
You can touch any application to explore its content and figure out what is taking up some much space.
Click to expand...
Click to collapse
So far I havent run into any issues with the apk...
Not to burst anyones bubble, but Choose Install Location has been doing this in a comprehensive way for weeks. http://www.appbrain.com/app/choose-install-location-free/com.beidl.chooseloc
Free Memory?
bdt1995 said:
I just tested it out on my Droid 1, which is running CM6.1RC5 (Not sure if thats relevant or not), and it doesnt seem to work very well on my phone. All apps came back as 4KB, at the top it showed this... Total:261.8MB Used:NaNKB Free: 259.1MB Database NaNKB Files: NaNKB Preferences:NaNKB Cache:NaNKB.
Click to expand...
Click to collapse
I'm having the same problem as bdt1995. Running CM 6.1 RC1.. the only difference is the total memory is 196.2 and the free is:194.3 MB cuz I'm using a Nexus.. CM6 might be the problem?
bdt1995 said:
I just tested it out on my Droid 1, which is running CM6.1RC5 (Not sure if thats relevant or not), and it doesnt seem to work very well on my phone. All apps came back as 4KB, at the top it showed this... Total:261.8MB Used:NaNKB Free: 259.1MB Database NaNKB Files: NaNKB Preferences:NaNKB Cache:NaNKB.
Heres the debug report: 1:/dev/block/mtdblock6 268032 224572 43460 84% /data
2:62855 /data/data
3:4096/0/265352
Click to expand...
Click to collapse
Same here (total 196.2MB, Free 194.3MB, all apps 4KB), system details in my sig. Using apps2sdext, over 200 apps.
Debug info:
Code:
1:/dev/block/mtdblock5 200960 112144 88816 56% /data
2:96070 /data/data
3:4096/0/198951
Same problem as above with Cyanogen 6.02, However it looks promising.
I Think that moving data to standard SD can leads to security issue, because SD can be readed and written by any apps. Should be better if the app recognize /EXT partition, if exist, and move data here.
i'd like to try it and i get my lil sis to try it also she gets this problem a lot i have the droid incredible and my sis has the droid eris.
bdt1995, rnh16, britoso, mmorselli:
Thanks for the debug info. Indeed Cyanogen is a tad "exotic" for NES at this point.
Please download the latest version of NES -- I just uploaded it. It contains an extra debug line which should allow me to make it work so please paste your debug output here one more time.
JerseyFF:
Oops, thanks.
lhinsz:
Because it is a beta version, it hasn't been released yet and all the information you may need is contained in the Help screen. I tried to make it comprehensive.
BigNate:
Should work with HTC devices, yes. Could you or you sister paste her phone's debug screen here?
Zandog:
I do not think that both apps share the same goal so no lives should be lost (Seriously, not much of a bubble to burst?)
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!
I'm aware, that only a few of my comrades in
XDA'a
R
M
Y may be aware of this issue, and change since the migration to android 11. To help illustrate to you I recently, thru google takeout, downloaded my 45+gb gp music library, all to which it's destiny was sd card storage (as chosen thru my Chrome Browser settings). After all files were unzipped and transferred , the available storage space on my sd card hadn't charged! So yes, my sd card is OK too, as affirmation to one of the replies I received earlier stating since gaining Android 11 rhey hadn't seen any changes. And by ok, you nust mean the sd card doesn't unmount itself at will, or randomly throw-up an error msg like, "sd file corruption detected," just for giggles!
As stated earlier, only a handful of folks I know over on discord's SamCentral are aware of this change, so there's been little discussion of file allocation tables & tweaks, i.e., formatting FAT 32(or that's the current default)idk...this isn't my field but imo, I think they're saying currently everything is being shifted to external stg. '0' which is the common ground for all or most of Android O/S's, thus "arming" their decision with the "no purchase necessary" routine. Fact is, most folks don't require more than half-a-gig or more of on-board mobile device storage. "The needs of the many, outweigh the needs of the few, or the one."(RIP Mr. Spock, Leonard Nimoy). So,, if this smells like a patch of sorts to you, why haven't we heard anything, and when can some of us expect to get our money's worth for our sd card purchase(mine, 256gb = $100, in Spring of '19). Some of the "fake-news" spreaders over there(lol) are saying the most recent samsung shifts to Microsoft based apps/services & cross-syncing is the root of the cause, and they're probably getting closer to plotting a solution now that the big hill has been championed(ref. to And. 11 + One UI 3.0-no project completion)! I miss the functionality of not being able to use an interface I paid for!
(If any of this I've shared here fact-cks.out to be valid, and I become a hero of sorts, does this mean I may gain some of that XDA "street-cred" and snag a couple of likes)?!
tarHeel71 said:
This actually was a thought of mine shortly after being sworn-in as a beta-tester for Samsung's One UI 3.0h-no, last fall.
Is there a different format process for my sd card now with Android 11(and if so, why was I not consulted)?
Any guidance or insight on my query would be great. Carry on!
Click to expand...
Click to collapse
I updated to 11 and UI 3.0 about a week ago and not having any issues with my sdcard. Only problem I have is that my battery usage as more than doubled even after a FDR.
tarHeel71 said:
This actually was a thought of mine shortly after being sworn-in as a beta-tester for Samsung's One UI 3.0h-no, last fall.
Is there a different format process for my sd card now with Android 11(and if so, why was I not consulted)?
Any guidance or insight on my query would be great. Carry on!
Click to expand...
Click to collapse
What exactly is the issue here? Not formatted? Can't see specific data? I went through the whole beta and now on release and my SD card is "exactly" the same as before with the exception that some apps can't see other apps' directories which is a "feature" from Google.
Compusmurf said:
What exactly is the issue here? Not formatted? Can't see specific data? I went through the whole beta and now on release and my SD card is "exactly" the same as before with the exception that some apps can't see other apps' directories which is a "feature" from Google.
Click to expand...
Click to collapse
The real obvious missing link to me was, for instance, when I'm signed in and surfin on my browser(Chrome, Samsung Internet, etc) and I save/download a file, it doesn't actually get saved on the physical sd card like it did before, rather, the o/s leaves the file in a limbo state of sorts, with whatever browser app!? I got my n20u1_5G back in 9/20, so while on Q if I saved, d/led a file i.e., using Chrome, I would go thru my Files then sd, then Android, then data, then find chrome(com.google.shrome), and there she is!
But, since beta school, whilst on 11, I do my Lil routine(as b-4), and when I goto Android then data, there's nothing, no app files(google or Samsung, as there were b-4)!? I hope I'm explaining the deal well enough here, as I couldn't be alone with this issue! Anyone using a stg card knows what I'm saying that isn't to be seen anymore! I'm using the same 250gb (high-end) Samsung card as b4, when I purchased my handset thru b-buy.com last fall(see jpg).
(Sorry 4 delay in my reply)☠
"Android, then data, then find chrome(com.google.shrome), and there she is!"
BINGO. Yeah, that's NOT happening any more. Those folders are now SECURED from any other apps viewing them. Only the owning app can view. The files are probably there, nice and safe.
Right now I know of 3 ways to view them. Total commander file manager in the app store filed the appropriate request to google for "total access" and you can view them if you hook your phone up to a computer. The 3rd way is quite a bit uglier requiring you to make an activity to a legacy file manager that google accidentally left in android 11 but hid. I'd have to dig around a lot to find those instructions again.
It's called "SCOPED STORAGE"... Go read about it and cry.... I know I did.
So, NO, you aren't going nutz based on this. However, that doesn't preclude other ways to go nutz!!!!
Compusmurf said:
"Android, then data, then find chrome(com.google.shrome), and there she is!"
BINGO. Yeah, that's NOT happening any more. Those folders are now SECURED from any other apps viewing them. Only the owning app can view. The files are probably there, nice and safe.
Right now I know of 3 ways to view them. Total commander file manager in the app store filed the appropriate request to google for "total access" and you can view them if you hook your phone up to a computer. The 3rd way is quite a bit uglier requiring you to make an activity to a legacy file manager that google accidentally left in android 11 but hid. I'd have to dig around a lot to find those instructions again.
It's called "SCOPED STORAGE"... Go read about it and cry.... I know I did.
So, NO, you aren't going nutz based on this. However, that doesn't preclude other ways to go nutz!!!!
Click to expand...
Click to collapse
Thanks for the reply...I've heard bits/pieces in talks with geek friends, and I appreciate your expertise here on this topic! But, why aren't the bytes getting gobbled -up(like when viewing sd card stg. available from the pull--down menu or from device care app)? I downloaded nearly 45 gb of audio files to my sd card, with absolutely no change there, but you see the stg reduction to internal storage. For what benefit, to them , google? Or just more of the ongoing sparing the two of 'em are constantly a part of! lol/smh