Originally Posted by ptmax13
Can anyone help me with this..
I have stock 4.2.1 with franco kernel and stock recovery. Rooted and unlocked bootloader.
Obviously I cannot update via OTA the traditional way...
If I flash the zip of the 4.2.2 OTA update (via custom recovery), will I brick my phone?
If yes, how can I return to stock kernel, so that I can update to 4.2.2? (any links would be great!)
sorry for the noob question....
All your questions have already been answered in the OTA thread over the last couple days, so go have a bit of a read: http://forum.xda-developers.com/show....php?t=1419170
And no, you won't brick anything. Read the OTA thread OP so you'll know what you're doing and won't worry.
Originally Posted by 5pace
renaud (Developer of Fugu kernel) said this:
So, I guess you know whats the problem now.
Ah, that explains why the N7 f.K boots and the GN f.K doesn't; no PVR. Interesting.
Kernel sources dropped today so hopefully Google haven't made it too hard to merge. 4.1 -> 4.2 was a pain in the ass if I recall correctly and Francisco basically had to start from scratch.
While we wait for boss man to do his magic, I've tweaked stock kernel a bit.
Stock apparently has TCP Congestion Avoidance Algorithms now, but only cubic (Linux default) and reno. I switched it to reno for fun. Disabled Content Adaptive Brightness too since I can't do any of my other color tweaks with stock kernel.
Interactive is still the old version, so the original "magic" tunables are still fantastic. Oddly enough Google has disabled input_boost by default, I wonder why.. Anyway for those with poor memories:
60000 / 0 / 65 / 700 MHz / 1 / 45000 / 15000
Our newer tunables also work well, possibly better:
15000 / 0 / 95 / 700 MHz / 1 / 45000 / 15000
Then I switched to deadline from the Google default of cfq. Even though deadline isn't default the default tunables for it have changed. writes_starved is 2, fifo_batch is 16, and front_merges is enabled. malaroth's new values still feel smoother:
350 / 3500 / 6 / 1 / 1
Stock read_ahead_kb is 128, so I tried that at 512 again, but this felt worse. Feels like 128 or 256 is the sweet spot.
No way to set the IO Scheduler tunables on boot with f.Ku or stock (since there's no init.d), but I might try combining Franco's ramdisk with stock zImage later today to see if I can get that to work. Francenstock.
Stock vfs_cache_pressure is 100; LMK minfree is now 8099,10132,12165,14213,16245,20295; adj 0,1,2,4,9,15. Can someone compare those to f.K r364?