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!
Related
Hello everyone,
I just recently bought a new G tablet and first thing im going to do is install clockworkmod. Then going to load a custom rom on it. Based on what i have read they two custom roms people mostly use. Vegan and Tnt Lite. Im trying to get feedback from people who have used both roms to get an idea which one is better with this tablet. Im looking for something that is fast and can play most games that are made for the tegra 2 processor. Flash has to work, Market has to work and something to edit word and excel document. Any info would be greatly appreciated. Thanks in advance.
Also i know this device has a build in 16gb memory. When you flash a rom on it will it erase all your saved files like pics and documents? When i flash my driod 1 everything is on my external sd card but this is build in so not sure if you flash will it erase everything on the 16 gb internal memory? Let me know thx.
Gemni69,
I don't know anything thing about you or your skills, but I have been telling a lot of
new G-Tablet owners to slow down and learn before getting too far into modding.
The G-Tablet with the stock software that is available now (3588) is not bad. And with apps it can be fairly good.
But the mods all come with risks, tradeoffs and sometimes even catastrophes. You need to read this site on the things you are interested in untils you thoroughly understand what you are doing.
Too many people are jumping in and trying to do too much too fast and are winding
up in trouble. As you read further, you'll see.
Stock will go a long was for you with apps you like added -- until you are ready to
make some advanced decisions.
Good luck and enjoy.
Rev
Gemni69 said:
Hello everyone,
I just recently bought a new G tablet and first thing im going to do is install clockworkmod. Then going to load a custom rom on it. Based on what i have read they two custom roms people mostly use. Vegan and Tnt Lite. Im trying to get feedback from people who have used both roms to get an idea which one is better with this tablet. Im looking for something that is fast and can play most games that are made for the tegra 2 processor. Flash has to work, Market has to work and something to edit word and excel document. Any info would be greatly appreciated. Thanks in advance.
Also i know this device has a build in 16gb memory. When you flash a rom on it will it erase all your saved files like pics and documents? When i flash my driod 1 everything is on my external sd card but this is build in so not sure if you flash will it erase everything on the 16 gb internal memory? Let me know thx.
Click to expand...
Click to collapse
Flashing a ROM generally will not harm what is stored on the internal sdcard. However, since you can use a microsd or usb drive to backup the information that would be safest.
As for which ROM is best for your needs... read, read, read. Then try them out. I prefer the TnT path for it's stability and friendliness to media consumption. I've got friends who swear that gaming is best on VEGAn. There are caveats on both. I'm not sure that either comes with anything for editing Office docs but I think the GAdam ROM includes QuickOffice but it's been a while since I looked at it.
Thank for the feedback guys. I will keep that in mind.
I was wondering what kinda battery does this device have. Do i have to fully charge it and then drain it 2 or 3 times for it to fully understand the batteries limits or it doesnt matter?
Also when i was reading the step to flash a rom it states this
Step 7.
Navigate down to “mounts and storage” using the volume buttons. When that is highlighted press the home button to select it.
Step 8.
We want to mount “/system” and “/data”, so if it says “mount /system” that means system is not mounted yet.
Highlight “mount /system” and press the home button. The line should change to read “unmount /system”
Next, highlight “mount /data” and press the home button. The line should change to “unmount /data”
After the first line reads “unmount /system” and the second line reads “unmount /data” you’re done with this step, press the back button to go back to the main menu.
I have a driod 1 and i flash custom roms on it all the time. I have never had to do this step on my driod. Is this step necessary for the tablet? Do i have to do this step every time i load a rom? Usually i just clear the data and cache and the just load the rom zip file. Is this not the case with the tablet?
Just want to be on the safe side and do everything right.
Thanks in advance for the feedback.
K J Rad said:
Flashing a ROM generally will not harm what is stored on the internal sdcard. However, since you can use a microsd or usb drive to backup the information that would be safest.
As for which ROM is best for your needs... read, read, read. Then try them out. I prefer the TnT path for it's stability and friendliness to media consumption. I've got friends who swear that gaming is best on VEGAn. There are caveats on both. I'm not sure that either comes with anything for editing Office docs but I think the GAdam ROM includes QuickOffice but it's been a while since I looked at it.
Click to expand...
Click to collapse
Not sure where you read that... I've never had to do it. The process you're familiar with sounds fine. Make sure to read the specific threads for the ROMs for any special procedures and prerequisites.
I got those steps from the linky below
http://forum.xda-developers.com/showthread.php?t=865245
Also what is the battery life like on the tablet?
Any special procedures i have to do to get the most out of the battery life?
K J Rad said:
Not sure where you read that... I've never had to do it. The process you're familiar with sounds fine. Make sure to read the specific threads for the ROMs for any special procedures and prerequisites.
Click to expand...
Click to collapse
Gemni69 said:
Also what is the battery life like on the tablet?
Click to expand...
Click to collapse
12 hours yesterday (about 6 hours of use) with 30% last week. This is running the custom rom Vegan 5.
stock
I'm still running stock + enhancement. I haven't had any problems, though I don't do any document work on my tab. I use my tab for tinkering and surfing, and of course watching movies.
Have fun with your new toy!
Gemni69 said:
I got those steps from the linky below
http://forum.xda-developers.com/showthread.php?t=865245
Also what is the battery life like on the tablet?
Any special procedures i have to do to get the most out of the battery life?
Click to expand...
Click to collapse
Ahh... well I started modding from stock so I downloaded and setup everything to nvflash a factory load. Didn't see a need to backup something I never intended to install again but YMMV. The mounting system and data never seemed necessary either since the update scripts in the .zip usually take care of it.
Battery life has been great and I haven't had to do anything special. There are lots of folks that recommend things like bump charging to maximize your charge but for my uses that hasn't been necessary. I do run it down to about empty every few weeks but that's normally because I forget to charge it...
Hello,
Here is my no longer new wipe tool, inspired by the G2x Scrubber.
The Nullifier.
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does the action of the root word to something else. It also formats *all* the partitions afterward and *new* checks for, and repairs any errors on them.
6 Oct: This tool is now depreciated and succeded by the G2x AIO wipe tool.
New 2 August:
Updated to 3.1, now fully customizeable by partition. Still haven't gotten around to making status bars, it's going to take a little bit to work out the best implementation.
New 28 July: I've been working on wrapping my head around the infamous AROMA installer and have at least made some progress in understanding it. As alot of people in the past had wanted to have the option to choose which to wipe, and how many times. We're not there yet. Yet. I just wanted to give those interested something new to chew on while I work out how to break it down function by function. Currently I have it made so that you have one installer which allows you to choose between a single and dual wipe.
New 26 March: The Cache Nullifier I edited the script down to just do a single pass Nullification then format and error check. This will work on the G2x, O2x and su660.
26 April update: Changed the commands so that it writes ext4 file system instead of ext3 when it formats and created an error check zip, mostly just because it could prove to be useful. I tried a couple of different sign programs to sign these properly but in testing signature verification fails still.
Minor update 1 March: swapped out the binaries on the 2.0.6 releases so they're the same as the older versions, added an ext4 cache nullifier, and fixed the code on the dual-wipe as I was sober when that one was revised as it had errors which would prevent it from running.
Some brief need to knows:
1. This is a little lengthy process so please bear with it. The longest wipe is on /data which will take about 7 minutes. Obviously, make sure you have plenty of battery life before running it or are charging.
2. You *must not* power off your phone without first installing a new ROM or restoring a nandroid after you use this. See post here:
http://forum.xda-developers.com/showpost.php?p=23998091&postcount=125
3. I will provide help, support, etc., but I am not, nor is anyone else involved with this, responsible for any problems you may have in the extremely unlikely event that you do.
old links:
Depreciated
Direct link to 3.1:
Depreciated
Thanks to da-pharoah for being my main beta tester who stuck with me all the way, even after bricking his phone and getting the progress bar pinned down as best as possible.
Additional thanks to anyone who contributed (you know who you are).
Nullifier Q and A:
Q: Will this harm my phone in any way or brick it?
A: No, the incident with Pharaoh's phone was an unexpected problem brought about from the source-file I was using at the time causing CWM and Android to think the phone was encrypted. I no longer use that source-file.
Q: Why not just format everything?
A: Because a format isn't intended to erase data, though, to a degree, does so. This script is intended to and will wipe out the data and leave a clean set of partitions for a ROM to be installed to.
Q: (Submitted by Cargohook) Would it be idiotic or fruitless to run this and then restore a nandroid backup? I mean, would that defeat the purpose?
A: I highly doubt it would be a waste of your time. On an educated hunch, when you restore a nandroid all CWM does is format the partitions then load the data from the nandroid to those partitions; back to square 1 with old data being left behind.
Q: Why don't I get a message about formatting /boot?
A: Because it doesn't format /boot. Why? In testing I found that it doesn't need it. It's all a matter of how Android uses boot.img and how it's copied.
Q: Does this wipe internal or external SD? (added because it keeps getting asked)
A: In a word, no.
Q: Will using this cause nand-failure or make my phone unusable if used too much?
A: In my opinion, no. In other's, yes. By my experience I have never encountered such a problem. To give you a better answer, please see Overground's post on that subject here: http://forum.xda-developers.com/showpost.php?p=25257903&postcount=327
(Thanks for the objective opinion overground)
(More to come as need be)
Reserved just in case. (I knew there was a reason for me reserving this)
Changelog for 3.1:
Now you can select one, two or no wipes per partition, a long-requested feature.
Changelog for 3.0.5:
1. Obviously this is now AROMA based.
2. The scripting for the progress bar is different due to AROMA, so for now we have no status bar progress. I'm waiting to see if someone can explain what Amarullz means in his explanation since I can't make heads or tails of it. Otherwise all the old functionality is the exact same.
Changelog: (old)
1. Added progress bar.
It's not 100% accurate, but sadly it's impossible to get it 100%, even after tons of testing.
2. Fixed format issue with /cache.
Thanks Overground for showing us a better format command to use
and to my tester/protogee Pharoah, who added the unmount command which made CWM less pissed at me.
3. Added a model check just in case someone doesn't know what they're getting ahold of and turn their phone's internals into something resembeling Chernobyl's Reactor Number Four.
4. Removed unneeded mount command in dual wipe script which was causing problems.
Plans for the future:
Create a menu system so that the user has a choice of what to wipe, and single vs dual wipes, or no wipe at all.
This is coming along well, I decided to keep it more straight-forward versus making a system of menus, so once it's thoroughly tested it'll be released
Hopefully a time-based progress bar is still possible, if not I guess it's time to find someone who likes math to figure out the percentage of each operation.
Cool, will try in a second.
How long am I looking at here?
IRASadPanda said:
Cool, will try in a second.
How long am I looking at here?
Click to expand...
Click to collapse
Wow deja vu!
But maybe like 12-14 minutes. Didn't time exactly but that's a good estimate..
Волк said:
4. I will provide help, support, etc., but I, nor anyone else involved with this, is responsible for any problems you may have in the extremely unlikely event that you do.
(you know who you are).
Click to expand...
Click to collapse
You need to change that so that it says "I am not, nor is anyone else involved in this, responsible for any problems....etc."
The way it's worded right now makes it look like you're claiming responsibility, which could get ugly.
No, it'll be a little longer than that since it wipes each partition twice. The big one is /data since it's 1.5GB.
@IRASadpanda: I guess I should make it a little simpler.
Волк said:
No, it'll be a little longer than that since it wipes each partition twice. The big one is /data since it's 1.5GB.
Click to expand...
Click to collapse
Thanks for the new tool I have to wipe now!
and thats why he is a dev on team hellfire
i know a regular "format" of a nand flash just breaks the links to the data stored in the cells and doesn't actually overwrite the data, but won't doing this often wear out the flash card
Why does the data wipe take 7 min?
Sent from my PG41200 using xda premium
wyldkard said:
Why does the data wipe take 7 min?
Sent from my PG41200 using xda premium
Click to expand...
Click to collapse
Because it's actually making sure everything is wiped.
Worked like a freaking charm! Thanks! Start it... let it do its thing, right at the "oh ****, something is wrong" moment it will move on... let it work...
Sent from my LG-P999 using xda premium
Yea, the time I mentioned is actually the time. I got the time straight from CWM's log.
dang just when i got my phone all setup with HFS 1.4, could have used this a few days ago
nice work man!!! downloading now!!
Thanks for you're hard work!
Sent from my LG-P999 using xda premium
Congratulations!
Nice job Volk, glad to see all your hard work pay off. Keep up the good work
Let it run and it cleaned it all up running way faster you rock!!!!!!"
Sent from my LG-P999 using xda premium
Thanks! Also, thank da-pharaoh as well, he did most of the testing on it once my initial tests were done, and even helped with those.
Question: Would it be idiotic or fruitless to run this and then restore a nandroid backup? I mean, would that defeat the purpose?
Sent from my LG-P999 using xda premium
So everyone (including me) has noticed that the transformer slows down when doing i/o. I originally thought this was a hardware issue (slow memory? slow bus?) but from various threads it sounds like third party os fix the issue. So I have two questions:
Can someone explain what the asus kernel does wrong (or how third party kernels) fix the issue ?
Why asus cannot copy the fixes from third party kernels into their kernel (I presume this is a kernel issue and not support software around the kernel but maybe that presumption is incorrect; maybe it is a driver issue or maybe there really is a hardware issue?)
jake21 said:
So everyone (including me) has noticed that the transformer slows down when doing i/o. I originally thought this was a hardware issue (slow memory? slow bus?)
Click to expand...
Click to collapse
Random write of small blocks to the internal eMMC is slow. Flash memory has huge erase blocks (typically a couple of megabytes) and large write blocks. Writing 4KB is a relatively slow process.
jake21 said:
but from various threads it sounds like third party os fix the issue.
Click to expand...
Click to collapse
They can't fix it, they can only work around the issue by tweaking the kernel's caching parameters. Or, in the extreme case, disabling the fsync system call. Usually, an application calls fsync to ensure data has been written to the disk, so that even in case of a following crash or unexpected power loss the data on the medium is consistent. And normally fsync waits until the write command has completed. If you disable fsync, the app no longer has to wait, therefore no more lag. The data still resides in the RAM and is eventually written to the card by the background cache flush thread.
Downside of disabling fsync: If the tablet crashes in the wrong moment, you may in the worst case lose all your data, run into a bootloop, etc.
If this is true, how come with original release ICS 4.0.3 everything runs smooth and fast. I installed latest Jelly Bean 4.1 and slow real bad, i downgraded back to ICS 4.03 and it is fast again. Is it a driver issue. It can't be hardware.
Thanks
_that said:
Random write of small blocks to the internal eMMC is slow. Flash memory has huge erase blocks (typically a couple of megabytes) and large write blocks. Writing 4KB is a relatively slow process.
They can't fix it, they can only work around the issue by tweaking the kernel's caching parameters. Or, in the extreme case, disabling the fsync system call. Usually, an application calls fsync to ensure data has been written to the disk, so that even in case of a following crash or unexpected power loss the data on the medium is consistent. And normally fsync waits until the write command has completed. If you disable fsync, the app no longer has to wait, therefore no more lag. The data still resides in the RAM and is eventually written to the card by the background cache flush thread.
Downside of disabling fsync: If the tablet crashes in the wrong moment, you may in the worst case lose all your data, run into a bootloop, etc.
Click to expand...
Click to collapse
Ok I can understand the issue with fsync and small writes but then all tablets would have this issue (unless the infinity used particularly poor chioce of hardware). Also does this indicate if writes were disabled in (for example) browsers then they would be silky smooth ?
-
It would be nice if the tablet could mark certain directories as critical and flush those faster than other directories (perhaps abusing the meaning of the sticky bit on the directory). Certain non critical data can avoid having immediate flush (though if andriod apps are calling fsync explicitly there might be some stickyness in changing the behavior of the api). Anyways is my understanding correct that you are indicating that Asus used a particularly poor choice of eMMC or tweaked the kernel to flush more frequently ?
_that said:
Random write of small blocks to the internal eMMC is slow. Flash memory has huge erase blocks (typically a couple of megabytes) and large write blocks. Writing 4KB is a relatively slow process.
They can't fix it, they can only work around the issue by tweaking the kernel's caching parameters. Or, in the extreme case, disabling the fsync system call. Usually, an application calls fsync to ensure data has been written to the disk, so that even in case of a following crash or unexpected power loss the data on the medium is consistent. And normally fsync waits until the write command has completed. If you disable fsync, the app no longer has to wait, therefore no more lag. The data still resides in the RAM and is eventually written to the card by the background cache flush thread.
Downside of disabling fsync: If the tablet crashes in the wrong moment, you may in the worst case lose all your data, run into a bootloop, etc.
Click to expand...
Click to collapse
gordo2000 said:
If this is true, how come with original release ICS 4.0.3 everything runs smooth and fast. I installed latest Jelly Bean 4.1 and slow real bad, i downgraded back to ICS 4.03 and it is fast again. Is it a driver issue. It can't be hardware.
Click to expand...
Click to collapse
I didn't see a big performance difference between ICS and JB, even though JB should be even faster after all the "Project Butter" work. What is slow for you on JB?
---------- Post added at 07:35 PM ---------- Previous post was at 07:30 PM ----------
jake21 said:
Ok I can understand the issue with fsync and small writes but then all tablets would have this issue (unless the infinity used particularly poor chioce of hardware). Also does this indicate if writes were disabled in (for example) browsers then they would be silky smooth ?
Click to expand...
Click to collapse
Many people said the TF700's eMMC is slower than good microSD cards, and that can be reproduced with benchmarks.
To check how the browser performs if it doesn't have to write to the eMMC, install Browser2RAM, which moves the browser cache to a ramdisk. In my experience, there is still lag on some pages - so not all slowdowns seem to be I/O-related. It would be interesting to find out the real cause of this.
There may be another I/O situation except random writes: large writes which block small reads from another process. HPI should help here, but I think the 3.1 kernel doesn't support it yet.
_that said:
I didn't see a big performance difference between ICS and JB, even though JB should be even faster after all the "Project Butter" work. What is slow for you on JB?
---------- Post added at 07:35 PM ---------- Previous post was at 07:30 PM ----------
Many people said the TF700's eMMC is slower than good microSD cards, and that can be reproduced with benchmarks.
To check how the browser performs if it doesn't have to write to the eMMC, install Browser2RAM, which moves the browser cache to a ramdisk. In my experience, there is still lag on some pages - so not all slowdowns seem to be I/O-related. It would be interesting to find out the real cause of this.
There may be another I/O situation except random writes: large writes which block small reads from another process. HPI should help here, but I think the 3.1 kernel doesn't support it yet.
Click to expand...
Click to collapse
Agreed. However, even with Browser2Ram, I'm betting that there is still some i/o with the emmc that cannot be hijacked by broser2ram, and therein lies the problem. If nothing else, using RAM like that may force the tablet (b/c of screwy coding) to start paging data to...yup, you guessed it, emmc ... a lot sooner than it actually needs to.
Has anyone tried B2R along with dev settings to kill apps ASAP that are not in use? Perhaps this could lengthen the time before paging starts to occur?
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
Overall, everything runs smooth on ICS 4.0.3. Browser, opening app, games, there is no hick ups when watching movies, that happen alot on JB 4.1.1. The whole OS is smoth redrawing. On JB, there is always a wait few seconds to open application folders or closing it. I did reformat to default but no help.
_that said:
I didn't see a big performance difference between ICS and JB, even though JB should be even faster after all the "Project Butter" work. What is slow for you on JB?
---------- Post added at 07:35 PM ---------- Previous post was at 07:30 PM ----------
Many people said the TF700's eMMC is slower than good microSD cards, and that can be reproduced with benchmarks.
To check how the browser performs if it doesn't have to write to the eMMC, install Browser2RAM, which moves the browser cache to a ramdisk. In my experience, there is still lag on some pages - so not all slowdowns seem to be I/O-related. It would be interesting to find out the real cause of this.
There may be another I/O situation except random writes: large writes which block small reads from another process. HPI should help here, but I think the 3.1 kernel doesn't support it yet.
Click to expand...
Click to collapse
johnlgalt said:
Agreed. However, even with Browser2Ram, I'm betting that there is still some i/o with the emmc that cannot be hijacked by broser2ram, and therein lies the problem.
Click to expand...
Click to collapse
Not all I/O automatically leads to problems. The latest version of Browser2RAM only redirects the browser cache, it does not affect browser settings, bookmarks, etc. - which is usually a good thing.
johnlgalt said:
If nothing else, using RAM like that may force the tablet (b/c of screwy coding) to start paging data to...yup, you guessed it, emmc ... a lot sooner than it actually needs to.
Click to expand...
Click to collapse
No. Paging does not occur *to* the eMMC (no swap space is configured on the TF700), but only *from* the eMMC, to fetch pages of executable files. While it is true that the ramdisk for the cache uses some memory, it would only make a difference if you have lots of background apps competing for RAM.
A first step to see how much I/O happens is to watch the output of "iostat".
Thanks for the heads up. So, why does it still cause pauses and the like then?
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
johnlgalt said:
So, why does it still cause pauses and the like then?
Click to expand...
Click to collapse
Good question. It's time to find out.
Arm yourself with multiple adb shells and watch the output of iostat, top, free, or whatever else you can think of that displays interesting metrics. Then do something that causes lag and see if you notice a specific pattern.
(I am currently away from my main PC, and the SSD in my laptop decided yesterday it no longer wants to read ntkrnlpa.exe - so no adb for me right now)
I'll need a bit more specifics - I know adb well enough and can shell, but these other ... executables you're mentioning are new to me.
I'm on vacation in Hawaii, and have a Windows 7 based laptop that I can use, so I can do this no problem - but not today. About to go see some sights before going on a Lava Boat tour at 4 PM local, which means I'll be bushed when I get back - plus I'm fighting a nasty ear infection that aches something awful.
AFAIK, though, I have no real plans for tomorrow or Friday, so I can take some time and investigate.
Also, FWIW: I'm rooted but have not (yet) unlocked my bootloader - mainly b/c I purchased the 64 GB version of the tablet and it is a C50, so I'm hoping something 'breaks' enough for me to get a replacement (c70? C90 even? )- and hoping even more that it is running something under ICS .30 so I can nvflash a backup and not have to worry about goofing things up when I *do* unlock the bootloader.
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
iostat and top are standard unix utilities. They would only be useful if run on the phone so I must presume andriod has versions. A bit of 'googling' and htere appears to be a developer's kit that includes stuff like iostat. If hte switches are the norm then something like "iostat -x 2" will produce nice output of performance of each 'disk'. top is a tool that shows cpu usage.
-
I've not done any developing for andriod (maybe I should bite hte bullet?) so have never tried to use adb or similar but i've done a bit of system development on linux (though I very rarely muck with the kernel; i prefer to work one layer above the kernel).
johnlgalt said:
I'll need a bit more specifics - I know adb well enough and can shell, but these other ... executables you're mentioning are new to me.
Click to expand...
Click to collapse
If you haven't done it yet, install BusyBox on your TF700. Then just open one or more command windows on your PC, run adb shell in each, and run "iostat 1" in one window, "top" in another, and maybe also adb logcat in yet another window.
That gives you up-to-date statistics about I/O and processes which currently use CPU time. Then try to use your tablet normally, and when it lags, watch the output on your PC if you see a big number of writes or a process eating CPU.
But don't forget to enjoy your vacation.
_that said:
If you haven't done it yet, install BusyBox on your TF700. Then just open one or more command windows on your PC, run adb shell in each, and run "iostat 1" in one window, "top" in another, and maybe also adb logcat in yet another window.
That gives you up-to-date statistics about I/O and processes which currently use CPU time. Then try to use your tablet normally, and when it lags, watch the output on your PC if you see a big number of writes or a process eating CPU.
But don't forget to enjoy your vacation.
Click to expand...
Click to collapse
Awesome. Busybox already installed here, so this should be easy enough.
And I never forget to enjoy ... anything. lol
Sent from my ASUS Transformer Infinity TF700 running Android JB (rooted) via Tapatalk
_that said:
Good question. It's time to find out.
Arm yourself with multiple adb shells and watch the output of iostat, top, free, or whatever else you can think of that displays interesting metrics. Then do something that causes lag and see if you notice a specific pattern.
(I am currently away from my main PC, and the SSD in my laptop decided yesterday it no longer wants to read ntkrnlpa.exe - so no adb for me right now)
Click to expand...
Click to collapse
hey fellas, have you seen chainfire's app : PerfMon
http://www.xda-developers.com/android/perfmon-floats-your-devices-performance-on-screen/
real time stats including io reads/writes to both mmcblk0/mmcblk1... :good:
ps: i have always loved "android status" aswell ... oldy but a goody
https://play.google.com/store/apps/details?id=com.AndroidStatus&hl=en
I've been having this phone for a year, and I've finally had the guts to go ahead and root the phone. I now have super user application. I have also installed Link2sd and linked all the big apps to a separate ext2 partition in my SD.
My question is , now since I've rooted this, what all options are there for me to explore and try out, in making this phone better. I've seen about various Cyanogen Mods, CM 7, CM9, CM10. But they all seem to have some issues. But sometimes even simple issues may be blown out of proportion. I just need some feed back on how bad the issues are, or how good the mods are actually. Basically I want to know if the impact of these certain issues will hinder me in enjoying my android experience. And i couldn't think of a better place to put these questions to.
Summary:
1) What options are present to make my device better, now since I've rooted it?
2) What kind of serious issues are there with the CM versions, and whether i can enjoy the phone despite these.
PS: One more thing. in Link2SD , despite linking those Apps to the ext partition, the internal memory only has 75 MB left, and some portion of it is reduced everytime I install a new app. is it a bug, or I've done something wrong?
I was afraid of rooting first too, but now that I rooted it, it totally worth it. First, I installed hexgore's stock plus rom with some modifications and used it for almost a year, then I decided to try out cm9. It was a lot better, and had almost zero problems (everything was working except the front-facing camera). Yesterday I installed cm10, and it is even better than cm9 I recommend you to install cm 10.
For making your phone better, you can install One Power Guard, Total Commander (give it root permissions instead of java), Cache Cleaner and Super Backup. These are the rooted apps I use/have used in the past.
Your "problem" with link2SD is not a bug, it is how it is supposed to work. It links the apk, the dalvik-cache and the cache, but it does NOT link the app's private data, which then is stored on your phone's internal storage. And that is taking up space.
Have fun with your rooted chacha!
Thanks
Thanks for your suggestion, I have decided to give CM10 a shot. Now, can u please send some link of a guide to follow, in order to flash CM10 in my HTC ChaCha. Also, a guide to revert back to the current ROM in case I fall into some issue with CM10.
Also, I wanted to know, is there any improvement in the battery? Mine is a year old and lasts for about 11 hours max. Anything that can improve this would be of great help.
I had earlier gone through a post on modifying a system file with a # sign in front of a line which makes the battery better, but I was unable to figure out how to edit a system file(I've located it using Astro file manager).
And I cant post there, since the forum rules say that the user must be at least 10 posts old to post in the dev section.
Any help is deeply appreciated.
Thanks in advance
Issue with backlight and prediction
archacha said:
I was afraid of rooting first too, but now that I rooted it, it totally worth it. First, I installed hexgore's stock plus rom with some modifications and used it for almost a year, then I decided to try out cm9. It was a lot better, and had almost zero problems (everything was working except the front-facing camera). Yesterday I installed cm10, and it is even better than cm9 I recommend you to install cm 10.
Your "problem" with link2SD is not a bug, it is how it is supposed to work. It links the apk, the dalvik-cache and the cache, but it does NOT link the app's private data, which then is stored on your phone's internal storage. And that is taking up space.
Have fun with your rooted chacha!
Click to expand...
Click to collapse
Heyy!
I took ur advice and installed it, and there is almost no problem for me, I never use much of the front camera anyway. The thing is, the Keyboard backlight doesnt work when the brightness is on automatic. is there a work around?
Also, the prediction, as I mentioned in another thread, does not work good. there is no prediction as a matter of fact, no options come out for me to select.
One more thing is that I am unable to see a list of users to select from that and send messages to. I have to type in the name of each user and add it manually. Any work around or apps available to solve it?
Hi, I've installed several CM: from 7 to 10.1, lately many 10.1 nightlies and I've been using the Nexus S for years.
Right now I've installed SlimBean, build 6, thinking that my phone needed a clean up and a better ROM.
The problem is: the phone is normal after a reboot but after 3 days of being used without reboot it becomes unresponsive, laggish and the free RAM is always on 22 MB with plenty of services that keeps restarting.
By unresponsive and laggish means that sometimes I browse internet (under Wi-Fi or 3G, no difference) and even with the standard browser everything freezes up. Sometimes takes me 10 minutes to get the page and be able to quit the browser, sometimes screen goes of, BLD stays on if I push the power button but nothing appears for minutes and then it probably reboots.
Now on Slim Bean it seems a little better but the performance degradation are very similar.
Since other guys are installing CM 10.1 nightlies etc and are not experiencing my problems I thought it was a problem on my apps. I use:
Faceboook
WhatsApp
Skype only when I have to call, it's NEVER always on
All Google Apps
Cyandelta for getting the latest nightly
Titanium Backup
ROM Manager
Rarely: Chrome/Firefox/Dolphin (since browsing destroys perfomances permanently after browsing. Chrome is particularly slow)
When I told, in the other forum, what I use some guys said that they use way more stuff and they are not experiencing problems.
Please note: I've managed to reinstall CM 10.1 with a full wipe (data-factory, cache, format /system, dalvik from the recovery) and I did the same to try SlimBean following step by step instructions.
Now: I think that maybe there's a problem with some junk in my phone. I've of course run an Antivirus (AVAST) several times in order to exclude some malware and I've found nothing.
By browsing root, folder /, I've found:
/proc - 179 elements
/proc/irq: 159 elements old, some new (updated in these days) but all similar with empty files
The name of the folders is like: /proc/irc/11 to /proc/irc/164
Opening those files doesn't give me much information. Note I'm graduated in engeneering but I'm not pro android developer nor I do the developer for work, even tough I can understand part of this stuff
Also in proc there are other elements with empy files:
/proc/1
/proc/2
...
/proc/15289
Here's my question: since the full wipe raccomended in the ROM update/fresh install procedure has been done step by step, several times, and the phone is still experiencing the same problems (different ROM with different Kernels also), is it possibe that I've installed something that needs to be deleted in order to get the phone less laggish/unusable?
I see that if I access the recovery I can format the following folders:
/data
/system
/cache
/boot
Is there something else that I can do about other folders like, for example, act on cleaning/formatting the /proc folder or something?
What's safe to do? Is there any tool that I can use or a procedure to get the phone fully clean up and then reinstall a fresh ROM?
Thanks in advance for your time
you can't wipe it any better. if you delete some folders you can actually brick your phone. before flashing format /system /data and /cache, that's all you can do. the slow downs are probably caused by a lack of RAM, 4.2 is hungry for RAM and our phone has only 512MB. I tried a lot of 4.2 roms and all of them slow down and stutter after a few days of usage. 4.1 uses ram more efficiently and therefore is faster when you multitask. I use cm10 latest nightly and there are almost no slowdowns, i had my phone running for a month without a reboot. 4.1 is best suited for our phone, no wonder google refused to officialy update it to 4.2, the hardware is just too old.
ka'cipeder said:
you can't wipe it any better. if you delete some folders you can actually brick your phone. before flashing format /system /data and /cache, that's all you can do. the slow downs are probably caused by a lack of RAM, 4.2 is hungry for RAM and our phone has only 512MB. I tried a lot of 4.2 roms and all of them slow down and stutter after a few days of usage. 4.1 uses ram more efficiently and therefore is faster when you multitask. I use cm10 latest nightly and there are almost no slowdowns, i had my phone running for a month without a reboot. 4.1 is best suited for our phone, no wonder google refused to officialy update it to 4.2, the hardware is just too old.
Click to expand...
Click to collapse
Thank you... it's somehow the only explaination possible...
But I wonder: if it's true, why is everybody forcing 4.2.2 on this phone? There are plenty of ROMs... has nobody noticed the problem?
Nuclear_Geko said:
Thank you... it's somehow the only explaination possible...
But I wonder: if it's true, why is everybody forcing 4.2.2 on this phone? There are plenty of ROMs... has nobody noticed the problem?
Click to expand...
Click to collapse
Everyone is forcing it just because it's the latest version. The same will be when 4.3 gets out, people will install it just to have it, even if it's not stable. Most of the people notice the problem but ignore it just for the goodies that 4.2 provides. Some ignore it so they can tell their friends that they have the latest android. Some don't use many apps so the problem is not noticable.
ka'cipeder said:
Everyone is forcing it just because it's the latest version. The same will be when 4.3 gets out, people will install it just to have it, even if it's not stable. Most of the people notice the problem but ignore it just for the goodies that 4.2 provides. Some ignore it so they can tell their friends that they have the latest android. Some don't use many apps so the problem is not noticable.
Click to expand...
Click to collapse
Honestly the most strange thing is that there's a CyanogenMOD for this...
I don't think they would push it if it doesn't work properly... or am I wrong?