yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] fossean:
Thanks for the 3G driver fixes in A31!

Instead of spending ~90% @ 102MHz when screen off, now device is mainly in deep sleep.

The problem with kernel wakelocks caused by baseband_xmm_power is much improved, although it is still top of the wakelock list at between 10-30%. Of course, I don't know what the baseline ought to be and this could be the optimal behaviour.

Before testing A31, I was just about to give up on 3G and try flashing a Grouper ROM. Haven't had time to check battery life, but it should be a lot better.
[Nexus 7 Android Development] Stuphologist:
Why not?
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Seevers are up i think
[Nexus 7 Android Development] EvanA:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Nope still down here...

Sent from my AOSPA 3.+ and m-kernel a31 Nexus 7
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

For me works
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Considering 75 people have already downloaded it before I was even able to post the link..... I'm pretty sure goo is working now...

Sent from my Nexus 7
[Nexus 7 Android Development] sjknight413:
Not here, it's being extremely erratic loading the countdown and it won't start the download once the ten seconds is up, guess we're waiting a bit longer :)
[Nexus 7 Android Development] metalgearhathaway:
Someone who has it could upload to te forum in a post, it is small enough to be attached!
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Please don't. Just wait a little bit.

Sent from my Nexus 7
[Nexus 7 Android Development] metalgearhathaway:
OK, my bad :)
[Nexus 7 Android Development] carlz0206:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Popstyle B
[Nexus 7 Android Development] metalgearhathaway:
goo downloads working again, got my kernel, cheers :)
[Nexus 7 Android Development] zachf714:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Thanks :)
[Nexus 7 Android Development] sjknight413:
A32 running great here.

Still getting that annoying 'stickiness' in homescreen scrolling after unlocking though. Got it with every kernel + ROM combination so far. Anyone know how to get rid of it?
[Nexus 7 Android Development] Southrice:
what happens if you flash this on an older bootloader? say 3.43?
[Nexus 7 Android Development] johnnyman25:
+1.i have same thing plus when i scrolling via homescreens and cpu dropped on 102mhz then if i scroll again it lags a little.this happens only in landscape mode.in orizontial mode its butter smooth.also i tried every kernel+ ROM combinations.
[Nexus 7 Android Development] Sveke:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Me too. Pisses me off, my GNex is way smoother than my N7. Wtf!

Sent from my Galaxy Nexus
[Nexus 7 Android Development] johnnyman25:
yeah man. it's sad. cant understand why in horizontial mode its butter smooth and in landscape its.i have stock settings in trickster app.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Obviously because the GNex doesn't hotplug. Two cores running constantly. Setting touch_min_cores to two will help.

Sent from my Nexus 7
[Nexus 7 Android Development] davisac:
Hey Metalice I was just looking over some threads on xda and I saw FIOPS scheduler mentioned. It sounded interesting but I wasn't able to find much about it (Google either) so I was wondering if you knew anything about it? or if it was anything to add to the kernel.

Here's what was written about it: "Relatively new. No I/O seek time, ( potentially better for performance), balanced read/write times, one of the smarter I/O schedulers"
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Its good for ssd or flash devices. (Fair in out performance scheduler)

It is still (somewhat) new, which is a reason why you can't find to much info about it around the interwebzzzzz
[Nexus 7 Android Development] Leonhan:
I've edited the value to 2 using text editor(im using root explorer), but everytime I reboot, it goes back to 0. Of course I did save changes and exit, but what gives?@.@
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

It's a sysfs file. Use init.d if you want it set at boot.

Sent from my Nexus 7
[Nexus 7 Android Development] davisac:
I was testing out some different schedulers to see how they each did and thought someone might be interested so I put it in a Google Docs spreadsheet.

I just tested the ones Metallice recomended in this post for now but I'll add the others later tonight or tomorrow.

I tested them for three runs each then switched to the next scheduler. Read ahead buffer @ 2048 for all the tests. CPU @ 102-1000 using default touchdemand in a32. FSYNC off and GPU @ 484. Everything else stock a32 kernel.

I tested using AndroBench, hopefully it's reputable.

Link to the Spreadsheet

Here's the benchmark results @ 2048 read ahead:
[Nexus 7 Android Development] Leonhan:
Sorry for being a noob but how do I do that.?
[Nexus 7 Android Development] EvanA:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Put this in an /etc/init.d file (call it something like 85_Somename) and set the file permissions to 755.

#!/system/bin/sh

echo 2 > /sys/devices/system/cpu/cpufreq/touchdemand/touch_min_cores

Sent from my AOSPA 3.+ and m-kernel a31 Nexus 7
[Nexus 7 Android Development] azoller1:
i keep getting some random reboots? wiped caches
[Nexus 7 Android Development] bervin:
Why haven't you got your recognized dev status yet metal?

Sorry for the OT
[Nexus 7 Android Development] Nosferatu.:
a30 with LiquidSmooth ROM and plenty of goofing around on the device I think the battery life was acceptable. Randomly today "Google Services" popped up as biggest usage but I got nothing in BBStats or CPU Spy. Over 90% of deep sleep so it's all good.

just over 65 hours with over 4 and a half hours of screen time on one charge cycle.

I'd likely charge it every night when going to bed but it's great to know there's plenty of overhead. :cool:
[Nexus 7 Android Development] Metallice:
I dunno. Don't know how... Don't really care.
[Nexus 7 Android Development] FitAmp:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

I respect that.

Not developing for a silly "status"

Good job to you sir :)
[Nexus 7 Android Development] prestige777:
I cant get the 1700 slot to work on the last three kernel builds, any idea why it wont go in to it? It just freezes and reboots every other slot works. I'm using 1900 for the time being even though its broken supposedly. Thanks for the great kernels.

I attached the last_ksmg if you have time to look at it.
[Nexus 7 Android Development] Leonhan:
Is it safe to have two cpu tuners (trickstermod, setcpu) installed? I installed setcpu just to change the touch_min_cores and set it on boot.
[Nexus 7 Android Development] fossean:
Unfortunately the bug seemed to return after I left it overnight. This is currently a common problem with stock kernel and every custom kernel afaik. I guess we need to wait for a fix to roll out. Until then, I may just flash a Grouper ROM + M-kernel ;)

Note that device was in airplane mode, with screen off nearly entire time. Running A32.
[Nexus 7 Android Development] Nico_60:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Why don't you change it with a script as explained previously ?
[Nexus 7 Android Development] johnnyman25:
if i change touch_min_cores to 2 the battery usage will take a hit?
[Nexus 7 Android Development] ximmox:
AW: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

It might, definitely won't improve.

Instead of asking for every new feature that Metallice introduces, try it for yourself. :rolleyes:
[Nexus 7 Android Development] Leonhan:
Well, tinkering with the root parts of the device seems pretty daunting for someone who doesn't know anything about coding.xD But I just want to know if there are any negatives when I install 2 cpu tuners.
[Nexus 7 Android Development] S3tArtist:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

There is always posibility of settings to crossover with 2 apps doing the same thing.

I think it's better to use only one. Trickster.
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

1700 is never stable for me, i tried all possible combinations. Only Metallice can make something for this ;)
[Nexus 7 Android Development] adstraylight:
I am also getting freezes and reboots at 1700, but then it's only in the last two releases that 1600 has been stable for me, so it could be that this is the limit for my particular device.

I know that battery life is important, but it seems that maybe people are obsessing about it? Unless you're planning on a desert trek with nothing more than a solar charger, does it really matter whether you charge every day, or two or three?

No offence intended btw, I do think this kernel gives a great balance of performance vs longevity, and I suppose it's a case of each to their own, I just think that the conversation is rather skewed toward this one aspect of what is a multi purpose enhancement for our devices.
[Nexus 7 Android Development] porkovich:
My device sleep very well with latest 30/31 kernels. Now there is a problem from time to time where the MEDIA SERVER is running in the background, keeping the device at 102mhz ... maybe it's a background process that is preventing it from sleeping properly.
[Nexus 7 Android Development] Cryingmoose:
on a31 I could run an Antutu benchmark at 1.9ghz (set in trickster mod) and get ~15300 score

on a32 setting it to 1.7ghz and running Antutu causes a reboot as soon as I start the test.

(on latest PA)
[Nexus 7 Android Development] IRX120:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

i get freezes and reboots at stock 1300 mhz, on trinity kernel running stok 1.7 workes fine. on the a26 build with 555LP its useable but freeses after a while, anything higher than LP555 freezes my device, is there a way to bump the volatges a little before flashing?
[Nexus 7 Android Development] acidspider:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Where can I find this version of trickster mod? U can edit touch demand gov?
[Nexus 7 Android Development] davisac:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

IDK why it's doing that but if you're only getting ~15300 @ 1900 I wouldn't run it that high. I was getting that score too @1500 cpu.
[Nexus 7 Android Development] johnnyman25:
Απ: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

+1
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Tester build. Will be available in about a week.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] element800:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Sorry for being offtopic but what's that theme or rom ;p? Ty ;)
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

The only difference between the 1.9GHz in a31 and 1.7GHz is the increased voltage for 1.9GHz.

1.7GHz reboots for me too unless I increase the voltage beforehand.

Sent from my Nexus 7
[Nexus 7 Android Development] zachf714:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

So the problem with 1700 is that there is not enough power going into the CPU to run so it kills the system and shuts down :)
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Metal what is right voltage for 1.7 GHz without reboots?
[Nexus 7 Android Development] MetalPainis:
AW: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

No idea, why do you ask me? ;)

sent from a Paranoid Nexus 7 via Tapatalk HD
[Nexus 7 Android Development] denzel09:
R: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

To you? Are you crazy?
[Nexus 7 Android Development] madlive:
That is tablet dependent mate, the exact sweetspot differs from cpu batch.
[Nexus 7 Android Development] Metallice:
He was joking dude...
[Nexus 7 Android Development] zachf714:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

I thought it was funny :) i found a30 to have a better balance of speed and battery than a32 so I'm going to stick with it thanks for your work.... I might try to help with the kernel Deforce Atty some point with foxes and such :)
[Nexus 7 Android Development] Southrice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Is trickster still not working?
[Nexus 7 Android Development] davisac:
Metallice said there's an update coming in around a week.
[Nexus 7 Android Development] acidspider:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

It was never broken. It just doesnt support the new tweaks yet for new govenor (touchdemand) however it has been said an update is due for the app next week
[Nexus 7 Android Development] sert00:
it's not working only for the touchdemand sysfs..all the rest you can use without problem.final test releases rolled out today,touchdemand stuffs already coded and tested,official release expected in a week

rom is an old PA,theme is "frosty" from Vicino..HERE

in mine i can go with 1700 without problem and without further overvolting..not the same with 1900,where it works after a little OV (i'm with 31 yet,downloading now 32)
[Nexus 7 Android Development] Stuphologist:
You submit an application. There's an explanation here.

Interestingly, all the links seem to be broken.

Dave
[Nexus 7 Android Development] bervin:
Did you set the kernel to be at 340mhz min freq when playing music? I can't seem to bring the min freq down when playing music
[Nexus 7 Android Development] davisac:
I asked him that about a29 or a30 and he said yes.

http://xdaforums.com/showpost.php?p=36595920&postcount=2572
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

You could try reading the changelog. I dunno maybe around the a20 region in the second post :)

Sent from my Galaxy Nexus
[Nexus 7 Android Development] davisac:
Does anyone have 51mhz working for them? I tried setting it a couple times in Trickster and after each reboot my other settings stayed but that reset to 102mhz.
[Nexus 7 Android Development] VenomTheCat:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

It was working for me but I found that when it my n7 doesn't go into deep sleep as much fore some reason

Also try setting a delay of 30 that might help
[Nexus 7 Android Development] zachf714:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Isn't the deep sleep or lp/lower usage core set at 666mhz so Shu not just set your lie at half of that :)
[Nexus 7 Android Development] prestige777:
Finally got it stable at 1350Mv what is yours stable at?
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

1300mV. Not that it matters for any device other than mine.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] VenomTheCat:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

No idea what you just said :&
[Nexus 7 Android Development] zachf714:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Set your lowest clock speed to half of 666mhz :)
[Nexus 7 Android Development] prestige777:
Thanks, I went back to a-31 and bumped the voltage up to 1425Mv on 1900mhz its smooth as glass. The higher I went on the 1700 slot the more stable it got, but I figured I might as well use the 1900 slot, I don't know if 1700 would use less power at 1400Mv than 1900, I doubt it.
[Nexus 7 Android Development] dmmbbs:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Hi Metalice, could you please continue developing a kernel version with LP core close to 500 MHz like you did previously as 550/555 MHz? NVIDIA Tegra3 documentation says the LP core consumes less power than the main cores upto frequencies closer to 500 MHz. I am stuck at a25 because of this.
[Nexus 7 Android Development] carlz0206:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

A31 was running great for me,flashed a32 last night and this morning i left my tablet at home in airplane mode(using n7 3g) and when i went home i was surprised to see the battery drain from 100 to just only 83.ive used a 31 for 2 days and never experienced this.heres what i found in betterbatstats

And heres the Android OS drain

Not complaining or anything just giving feedback and maybe hoping someone know a fix,thanks for sharing your work,gonna try this again tommorow and if it still exist maybe ill try again a31 if it still the same

Xylon 16 1/18 tilapia

M- kernel A32
[Nexus 7 Android Development] ace-user:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

touchdemand seems more battery consuming than ondemand...is this normal?
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Why?

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

1900 in a31 is actually only 1700 so I don't know why you would go back or why you "might as well use the 1900 slot".

If 1900 was actually 1900, then of course 1700 would use less power at 1400mV than 1900 at 1400mV. It would use about (1700/1900) times the power.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Of course. It's not like touchdemand causes the frequency to decrease when you touch the screen. Just look at the parameters for it.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

No. Do you really think that I would continue to clock it that high if the physics making the LP core efficient *magically* disappeared above a certain frequency?

Also that's not at all what Nvidia says nor does that make any logical or physical sense. Nvidia only says the lp core saves power and goes up to 500MHz because on stock... that's... what... it... does.

Third, the nvidia sources themselves include support for LP frequencies up 620 for SOC Speedo ID 4. (Not that any Tegra 3 actually uses this)

Believe it or not I'm not *entirely* clueless here.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

On airplane mode? Weird. But truthfully nothing changed in a32 from a31 could possibly affect that. There were some changes to 3g starting in a31 though.

A32 did two things - added a mount point for the cifs manager fix, and removed the 1900MHz slot.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] carlz0206:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Gonna continue with a32 for another day and ifnthe batt drain still exist gonna go back to a31 and report back whatever results i get
[Nexus 7 Android Development] Nosferatu.:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Off topic but what theme is that?

Sent from my Nexus 7
[Nexus 7 Android Development] carlz0206:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Popstyle blue in the playstore
[Nexus 7 Android Development] Nosferatu.:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Sweet! Any reason why it says missing assets for your screen resolution when I set the theme? It also shows the circular switches as oval in shape. PM me so we don't go off topic in this thread. Thanks!

Sent from my Nexus 7
[Nexus 7 Android Development] dmmbbs:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

See http://www.nvidia.com/content/PDF/tegra_white_papers/tegra-whitepaper-0911b.pdf especially pages 5 and 6.
[Nexus 7 Android Development] dems86:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Is Soc speedo ID like my snapdragon S4's classification of fast in my US gs3, which in turn sets the voltages slightly lower compared to nominal and slow class? There is a terminal command to find out what class chip you have in the gs3, is a there something similar for tegra3 on the N7?
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

No. There are all kinds of IDs with tegra. The comparable one to what you're referring to would be the CPU process ID or "variant" which is based on voltage tolerance and on stock decreases voltage for the top slots by 25mV for each increasing variant number.

I added a sysfs file that tells you yours. Don't know it off hand.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Thanks. I've read it before. All they say is that the LP consumes less power for 0-500MHz than the other cores. Also that a low power chip would consume more at higher frequencies than a high power process due to the previously defined FV^2 which is obvious. Voltage requirements for a low power core to run at 1.3GHz would be enormous.

However i don't change the voltage so the consumption increase from 500 to 666 is only (666/500)x. Likewise, this means the line for cpu A on the graph on page 5 wouldn't increase as dramatically and would level off by the nature of the formula and the logarithmic scaling being employed by the graph.

If I were to raise the voltage to lets say 1300mV, than it is entirely possible that the LP would consume more than the G cores by the squaring which could overcome the benefits of low leakage. That's still only an if and you'd have to ask Nvidia.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

That said it might be better to stop at 620MHz as that is what Nvidia has the limit for the LP set as in their source. Then again, they have 620 running at 1200mV where as I have 666MHz running at 1150mV so the power use is probably not too different. Too lazy to actually do the math right now.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] thisguy23:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

OK great to know, but how does all this info add up when we disable lp and clock the g cores down to 100 and under volt them. Say 100mHz @625mv. If the lp 100mHz sits at 950mv would the g core use less?

I know you must feel like banging your head on a wall but a good portion of us just don't know about any of this. You're much more of an expert than us. But if we were talking about lighting a scene for a movie... Well, I could have some input there!

Thank you for all your hard work and patience with and for us!

Edit: Nm. I answered my own question. Looking at the chart in the white paper the lp core has more HP at lower frequencies than the g cores do and lp uses less power to function. So Nvidia is right. And my radical thinking of disabling lp to use less and get more is wrong.
[Nexus 7 Android Development] Metallice:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Frequency and voltage aren't the only factors to power consumption. Power consumption is only PROPORTIONAL to FV^2.

What makes the LP more battery friendly is that is a low leakage process. This benefit however becomes less important at higher frequencies once F and V start climbing faster and faster. At a certain point the G cores become better because the voltage difference increases as the frequency goes up eventually becoming greater than the leakage benefits.

Edit: which is demonstrated by the graph in the white paper.

Sent from my Galaxy Nexus
[Nexus 7 Android Development] HamsterHam:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

When ocing, do I just set a higher mpu voltage number for that particular setting or should I offset them all. Trying to get 1700MHz to work but currently it freezes.
[Nexus 7 Android Development] knitler:
Man im 2 version behind, time to update!
[Nexus 7 Android Development] EvanA:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Just set the voltage for 1700 MHz.

Sent from my AOSPA 3.+ and m-kernel a31 Nexus 7
[Nexus 7 Android Development] HamsterHam:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

I increased it to 1350 and it still freezes when running antutu. Do I need to raise the 1600 voltage as well then?

EDIT: 1425 and still freezing. If I go any higher does it matter? Is there a limit I should stick to?
[Nexus 7 Android Development] siddesu:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

Has anyone seen any dramatic changes in battery life after upgrading from 31 to 32? I am seeing a pretty big change, and since I have only switched kernels, I'd like to compare experiences.

In my case it was a good change - I am seeing quite a significant increase.
[Nexus 7 Android Development] EvanA:
Re: [KERNEL][3G+WIFI][4.2.1] M-Kernel - a32

If you're all the way to 1425 I'd say your device can't handle 1700. Mine can't either.

Sent from my AOSPA 3.+ and m-kernel a31 Nexus 7