I downgraded to 4.1.2 now, then rooted. It seems so much faster. Not sure what happened with 4.2
Sent from my Nexus 7 using xda app-developers app
Sent from my Nexus 7 using xda app-developers app
the LAG thread --__--
- Thread starter androidkid311
- Start date
android 4.1 for nexus 7 3G
Hi all,
I'm experiencing all these lags on the new nexus 7 3G version. I'm running Android 4.2.1. Since i have heard Android 4.1 was lag free, I was wondering if there is any Android 4.1.2 build available for the 3G version .
Hi all,
I'm experiencing all these lags on the new nexus 7 3G version. I'm running Android 4.2.1. Since i have heard Android 4.1 was lag free, I was wondering if there is any Android 4.1.2 build available for the 3G version .
Last edited:
I think its possible to root and downgrade to 4.1.2. When I get my n7 I'm sticking with 4.1.2. I'll wait for 4.2.2.
Sent from my Galaxy Nexus using xda premium
That's not true. I think ut shipped with 4.1.1 . I remember that the upgrade to Android 4.2 popped up when I was setting up my Nexus 7 for the very first time. I have a picture of that as well. Here is the link https://plus.google.com/113260014754281263350/posts/KPXCcJ1JAZg
Good luck finding a stock ROM for it. Google seems to only provide the 4.2.1.
Factory reset did nothing for me. Full wipe and manual flash of 4.1.2 and then 4.2.1 seems to have improved performance but it still ain't like it was.
Sent from my Nexus 4 using xda app-developers app
Last edited:
How did you get Android 4.1.2 for Nexus 7 3G? If you have any link, please direct me to that page
I've compiled fstrim for Android and packaged it inside APK with nice GUI. You can find LagFix tool here. This fixes lags when you fill /data partition.
FYI in 4.2.x the nexus 7 mounts with discard in the ramdisk, and if you don't have one of the affected storage chips, the Nexus 7 kernel makes it so the discard option does nothing. So this would really serve no purpose on 4.2.x.
However, for those sticking with 4.1.x this can be benefitial for those with the affected storage chips.
Sent from my Galaxy Nexus
I'm using CM10.1 and I'm affected. This is why I made it. Maybe original kernel from Google works the way you say, but I have this issue with default from CM.
I'm glad that most people are not affected, sadly I am. I got extremely poor IO still having 9 gigs of free space (I have 16gb model). I also have it on my HOX, but I was fighting it with /data backup/format/restore from recovery. /sdcard is separate there, but not on N7. Other solutions did not help me...
It's entirely possible that CM10.1 never added the discard option to their included ramdisk. I remember for a long time after CM10.1 nightlies started being built CM had yet to update their ramdisk to include discard, and it was quite annoying at the time as they had been building for 4.2 for a while.
I figured by now they would have fixed that and added discard, but I guess they didn't.
(M-kernel of course supports CM10.1 and adds discard to to ramdisk
) Sent from my Nexus 7
FYI by chance I happened to have the 01/14 CM10.1 nightly installed; both /cache and /data are mounted with discard.
I found this blog post was rather informative, if a little dated. Seems like some measurement data might be needed - with and without the mount option in use.
cheers
I finally got my nexus 7. Second one and its flying! Got the 32GB 3/G model. I'm lucky. I was nervous when I opened it that says a lot about the QC lol. They seemed to have drastically improved it.
Sent from my Nexus 7 using xda premium
Sent from my Nexus 7 using xda premium
I have had nothing but issues with my Nexus 7 I got at launch. I have the 16gb version also. Same issue as everyone else, I loved it for a few months, no issues and had about 4 gb of space left and then bam, moved slower than a car with no tires. I have had to factory reset it 10 times at least and the same thing happens over and over. Works fine for a while and then bam, now it's moving even slower and i'm having wifi issues, will not stay connected and I have 8 gb of space left. I even deleted apps and it's still a no go. I was going to root it but I see people are having the same issue even with root.
I know one thing, I will never buy another Asus product again, I have been burned by them by 4 different tablets and will never make that mistake again. It was bad enough they lowered the price by $50 a few months after it had been out, but the problems are even worse. I see people have called Google and got no where, so i'm not even going to bother. Tempted to go buy a new 32gb one and then switch mine with that and take it back to the store and get my money back. I feel since Google/Asus screwed me, I should return the favor.
I know one thing, I will never buy another Asus product again, I have been burned by them by 4 different tablets and will never make that mistake again. It was bad enough they lowered the price by $50 a few months after it had been out, but the problems are even worse. I see people have called Google and got no where, so i'm not even going to bother. Tempted to go buy a new 32gb one and then switch mine with that and take it back to the store and get my money back. I feel since Google/Asus screwed me, I should return the favor.
give them a call, I had an issue with mine, advance replacement was sent, the whole thing went rather well
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
9Recipe for Buttery Goodness
fsync handles i/o reads/writes to and from the filesystem, zRAM is swap (basically) enabled from the kernel.
Do the OTA update to 4.1.1 if you're stock, then...
_motley's linaro-optimized kernel thread
From that thread, you need:
a) the 1.1.1 kernel of your choice
b) the 1.0.5b kernel with ramdisk (if you're already running a custom ROM with init.d support, you don't need this, nor do you need to create /system/etc/init.d in a future step)
You'll also need:
a) root
b) cwm
c) busybox (absolute must, use the JRummy installer from play store and install the latest)
d) some type of root-enabled text editor (I use root explorer)
e) a full featured cpu/sd management app (I use System Tuner)
BEYOND THIS POINT, THERE BE DRAGONS. I'm not responsible if you FUBAR your device, but if you follow my instructions to the letter, you won't
1) install cwm and root your tab (if you haven't already)
2) reboot into CWM, flash the 1.0.5b kernel with ramdisk (if you're on stock or a stock-based ROM without init.d support), then immediately flash the 1.1.1 kernel you chose (gpu overclocking is nice and all, but I haven't found a game that doesn't run perfectly with the stock GPU speed of 416MHz..Looks great on benchmarks, though)
3) reboot back into JB, fire up root explorer, remount /system rw, create a folder in /system/etc called init.d (permissions rwxr-xr-x), create a file in it called S90zRAMandSpeedTweaks (permissions rwxrwxrwx), and long-press to open it in a text editor
4) make it look like this:
It's important to leave at least one trailing line in scripts. Just trust me, it's a linux thing.Code:#/system/bin/sh #remount /data for faster i/o mount -o remount,noauto_da_alloc /data /data #disable fsync (controversial, I've been doing it for years with no real issues) echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled #set zRAM size (change the 512 to 1024 for a full 1GB of swap, I use 512 because I'm on an 8gb and space is precious) echo $((1024*1024*512)) > /sys/block/zram0/disksize #use busybox to create and activate zram0, if busybox is not in /system/xbin, modify accordingly /system/xbin/busybox mkswap /dev/block/zram0 /system/xbin/busybox swapon /dev/block/zram0
*NOTE* The above script does NOT check to see if it was successful, but if you copied it directly and installed busybox to /system/xbin then it will work. Once you reboot in a few minutes, you can check by using the command "busybox free" from a terminal emulator or adb shell
5) Save the file, delete the .bak now in that folder, and close root explorer.
6) Open System Tuner, tap on the SD option, change cache to 1024 and scheduler to deadline
7) Tap the Voltage option and hit -25 4 times and save the settings as voltage_table_uv
8) Tap the CPU option and tap Boot Settings. For CPU and SD, set the method to init.d
9) Close System Tuner and reboot your device.
10 Profit/consume butter
It seems like a lot, but it really only takes about 15 minutes if you're a complete rooting n00b, and the end result is a buttery-smooth multitasking powerhouse (that blows iOS *away*). The 100mV undervolt also greatly extends battery life. I haven't had ANY issues at -100mV, but if you do, just increase it by hitting +25 on the voltage tab of System Tuner until you have something that works for you (in fact, you might want to start at -25mV and slowly grow it to -100mV, playing games and checking for instablity along the way)
It's also worth mentioning that if you're currently completely stock, you will need to unlock your bootloader to root and install CWM, and unlocking the bootloader wipes your device (no way around it, unfortunately. Hook your N7 up to your computer and backup the entire contents of /storage/sdcard0 to make restoring your data as painless as possible)
Hope this helps7
(This is an off-topic post, and the only one I've ever created on XDA, so feel free to skip past)
You come off as very mean spirited, hostile, and pretty douchey, to be honest.
Firstly, your sig is extremely unnecessary and doesn't do much to help the idea that XDA is a great environment to come to. Whereas other members use their sig to explain their device setups in order to further the community, you use yours as a divisive tool that discourages people from taking part in it.
Secondly, I have both an iMac and a Macbook Pro. They are both great computers in and of themselves, albeit they were a bit overpriced. I'm an audio engineer that works with multiple professional audio recording/production applications, and most all of them run better on OS X than on their Windows counterparts. I would argue that has more to do with the developers of those applications putting more work into making native OS X applications and then porting them after the fact to Windows, rather than OS X being a better platform altogether. But no matter what the reason is, quite simply I need to work on the platform that is going to give me the least amount of headaches, problems, and concerns when dealing with clients, clients who are giving me money to provide a service for them. And for me, the industry I work in, the industry standard is Apple computers.
Are you going to tell me that I don't belong here, and that you are so much better than me that I don't deserve your or anybody else's help? I've been on board with Android since the G1, in fact I bought it the day it was available. I love the platform. I also love the work that I'm involved with, and love the fact that I have the luxury of not fighting with my computers when I want to get work done.
Some of us need to use Apple products in our professional lives. Get over it, and quit being so elitist about it, please. Thank you.5So the new kernel source was just recently released, which reveals a lot of information about the issue.
First change:
Code:mmc: set emmc vcore voltage to 3.0V per EE's request, set eMMC core voltage to 3.0V.
*Shrug* I'm not sure what this does. From my very limited knowledge it seems like it maybe manually sets the voltage to 3.0V if the regulator fails to or vice-versa? I dunno. May be related to low I/O.
Second change:
Code:mmc: core: new discard feature support at Samsung eMMC v4.41+. Support discard feature if MID field in the CID register is 0x15, EXT.CSD[192] (device version) is 5 and Bit 0 in the EXT.CSD[64] is 1. Also removed REQ_SECURE flag check to avoid kernel hang. This patch is released from samsung.
Here's the big one. Here's why the discard option caused hard lock ups for me and others who tried this on 4.1.1. Discard option didn't work on Samsung EMMC chips, which coincidentally, were the chips that were having the performance issues with low free space.
So that script or whatever someone posted to remount data with discard and to trigger discard? Yeah it doesn't look like it will actually do anything without a 4.1.2 kernel (unless your unaffected by the issue with a Hynix or Kingston chip instead of the Samsungs. In that case, adding discard will actually DECREASE performance based on the next change below)
Third Change:
Code:mmc: card: Bypass discard for Hynix and Kingston In order to change mount option, issuing discard request by chip to eliminate performance drop.
This causes this discard mount option to do nothing on Hynix and Kingston chips. The Kingston one is used for the 8GB chip and I would guess the Hynix is a 16GB chip that isn't as common than the Samsung chip, which explains why there were a few odd cases of people without this issue. It looks like there's a hardware issue with Samsung EMMC storage chips and the discard option is needed to prevent this problem from causing performance degradation. Using discard on the other chips interestingly enough causes performance to decrease.
(Side note: I very much doubt CM10 nightlies are using the new kernel source already. Probably 4.1.2 ROM with 4.1.1 kernel and ramdisk.)5
Good thought. I agree that Google wants to promote the use of Cloud storage. That's fine.
However, we purchased 16GB (in fact, 13GB user usable space only!) of storage space on the Nexus 7 and is it wrong that we want to use it all? It is like you paid some money to buy from Google 200GB of Cloud storage and then Google tells you that you can only use up to 180GB, otherwise your upload / download speed will be throttled????? Is this even logical?!?! Does it make sense? The answer is clearly no. There is a problem, and we are desperate to see a solution, or a workaround (no - factory reset is not a workaround).
All we are trying to find out is 1) whether the lag that we are seeing is indeed I/O related, 2) whether this is a hardware fault, and 3) whether there is a way to workaround this issue while hopefully Google is coming up with a software fix.
By the way, why would you say that people are storing "garbage" on the Nexus 7? A Gameloft game can easily chew up 2GB of storage space. Google Music isn't available in Australia, so Cloud storage isn't available. 13GB isn't much when you have a few big games and a collection of music files, plus a number of "pinned" Google Movies. No one is talking about making the device runs faster. I guess most of us would not expect the Nexus 7 would perform dramatically poorer just because the local storage is filled up. A bit slower is OK, but not from 10MB/s to 0.2MB/s...
New posts
-
-
[ROM]LineageOS 20 - Xiaomi Mi 8- Latest: DarthJabba9
