yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] malaroth:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Just curious... what governor and i/o scheduler are you using on r46?

Franco r364
[Nexus 7 Original Development] nealkoy:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Interactive and deadline for me with the same problem with wifi on coming from deep sleep.
[Nexus 7 Original Development] aeroseek:
I'm also using interactive/deadline combo with "winning" tuneables and i/o tweaks.
[Nexus 7 Original Development] malaroth:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Check the winning tunable to make sure the mix up got fixed... writes_starved should be 6 and fifo_batches should be. Those got mixed up and I don't have my n7 yet to see if it was fixed. Deadline interactive is correct. You should wind up with values of 351/3500 6 writes_starved and fifo_batch 1 front_merges 1

Franco r364

---------- Post added at 09:08 AM ---------- Previous post was at 09:06 AM ----------

Row tunables are coming. They need more test time before we let them loose

Franco r364
[Nexus 7 Original Development] aeroseek:
Yup they are correct. I set them via init.d
[Nexus 7 Original Development] Puzzlegirl:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Looking forward to trying out the Row tunables then - thanks for all your testing :thumbup: Hope you get your N7 soon.

I have the correct deadline tunables and as I said, don't have any problem with slow touch response.
[Nexus 7 Original Development] aeroseek:
Do you also have wifi sleep policy set to something other than "always"?
[Nexus 7 Original Development] Puzzlegirl:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

No, it's on Always. I don't have the Wifi Optimisation on though.
[Nexus 7 Original Development] Gspin96:
I wanted to try undervolting. Started by lowering the voltage for 1300MHz (in this post, if I don't specify a frequency, it will be 1300MHz) by -25mV and repeated this various times. Seeing it still stable after a lot of steps, I decided to crash it and set the voltage to 600mV (using Pimp my ROM). Nothing happened. Doubting that it was getting undervolted at all, i used franco.kernel updater app. Nothing. Set voltage to 100 (which is -1025mV) and I played temple run with not even a little hang. This made me think that the voltages aren't applied at all (independently of the app I'm using to undervolt).

I checked the UV_mV_table file, and the values are written correctly in it, like:

1300 600
1000 600
700 600
400 600
100 600

(this is one of the sets of voltages I tried via pimp my rom).

Strange enough, if i use the editor built in ES File Manager the values are not correctly saved (e.g., I write "1300 1075" and it saves "1300 1300", and, each time I try to save, one of the values below gets wrongly changed), but this could be app's problem. More strange is that the same happens if I try to echo the new values into this file via ADB. If instead I use the editor built into CM File Manager, when I tap the "save" button the system hangs and the device gets restarted, even if no change was made to the voltages.

In the end, I still didn't manage to crash the cpu by undervolting it. Does this happen to anyone else?
[Nexus 7 Original Development] aeroseek:
The problem surfaces when wifi is set to turn off during deep sleep. If set on "always", works flawlessly.
[Nexus 7 Original Development] malaroth:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Mine is always on, optimization on.

Franco r364
[Nexus 7 Original Development] Puzzlegirl:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Oh right, well I never use that option. If I'm leaving the device for a while I just turn off wifi via quick settings. I haven't noticed that wifi being on Always uses a lot of battery anyway.
[Nexus 7 Original Development] aeroseek:
Yup that's what I've done in the past....but being lazy I wanted to have it automated lol
[Nexus 7 Original Development] johnnyman25:
Απ: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Does native OTG mount works for u guys?i cant get it work..

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.2 & Franco Kernel r46
[Nexus 7 Original Development] irminsul:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Install stickmount
[Nexus 7 Original Development] swedkg:
r46 seems to be working fine with 4.2.2 on the 3G version
[Nexus 7 Original Development] johnnyman25:
Απ: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

With stickmount it works but i want native OTG mount like other kernels.is it possible?this is the best kernel for me. :)

Sent from my Nexus 7 using Taptalk HD

Dirty Root Box v1.2 & Franco Kernel r46
[Nexus 7 Original Development] irminsul:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

It won't work till Franco implements it :) I'm used to use stick mount, not everyone uses otg, less code in the kernel keeps the kernel lean.

You could ask Franco if he'll implement it.
[Nexus 7 Original Development] joaquinf:
Hi guys. Just a heads up about the 4.2.2 stock kernel settings. Bluetooth issue has been indeed fixed and everything seems quite snappy.
[Nexus 7 Original Development] NicoGa:
Can you also provide us with a screenshot of the "specifics" tab to see if cpuquiet is there ?
[Nexus 7 Original Development] joaquinf:
Sure.
[Nexus 7 Original Development] element800:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Can we use r46 on 4.2.2?
[Nexus 7 Original Development] joaquinf:
This should answer your question
[Nexus 7 Original Development] swedkg:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Yes, it seems fine so far, and very battery friendly.
[Nexus 7 Original Development] element800:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Think it'll be better to wait for an update ;)
[Nexus 7 Original Development] N@th_OC:
It will work but you will lose all stuff 4.2.2 brought to us.

Most part of bluetooth and audio fixes are located on the kernel.

So it's useless.

Kernel sources for 4.2.2 are not yet released but it will be very soon.

I'll wait for that before flashing 4.2.2
[Nexus 7 Original Development] dareino:
Deja vu all over again!

How did Codefire already update their ROM??
[Nexus 7 Original Development] trailblazerz11:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Kernel sources have not been released but seems rest of 4.2.2 has been pushed to aosp
[Nexus 7 Original Development] osm0sis:
Yeah it always seems to take them an extra few hours or days to push the kernel sources for some reason..
[Nexus 7 Original Development] Khant:
Those having problem with touch not being registering sometimes should try seeder http://xdaforums.com/showthread.php?t=1987032

I decided to give it a try after I got a bit of touch response problem on stock 4.2.2 as well.

I think it keeps the CPU awake so the touch is more responsive. I don't know how to play with kernel settings to keep cpu awake more, so seeder is the best option for me. i'm sure some of you will know a better way than this.
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Oh no you didn't
[Nexus 7 Original Development] Aumkar:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Is there any reason as to why my Wi-Fi direct isn't working to transfer files to a note 2? Tried all the apps. Nothing works. Any suggestions peeps?
[Nexus 7 Original Development] JohnMacky:
Hi, I'm planning to try the new 4.2.2 stock. Just wondering if this kernel will work on stock 4.2.2 if I update? Thanks
[Nexus 7 Original Development] TheByteSmasher:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

One of the big changes in 4.2.2 is kernel... So 1. Don't do it until Franco can make it compatible 2. You'll lose like half of the 4.2.2 goodness.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
New interactive tunables ahoy. Now there's a go_maxspeed_load, and it seems they renamed target_loads to sustain_load.
[Nexus 7 Original Development] JohnMacky:
I recently updated to 4.2.2

Could I use the interactive control settings posted here in the forums to use to the stock kernel 4.2.2? Thanks
[Nexus 7 Original Development] dabeeeenster:
I'm getting errors trying to upgrade from Franco kernel to 4.2.2 - should it work out the box or do I need to do anything special?
[Nexus 7 Original Development] -star-:
AW: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Franco kernel installed and you trying to upgrade o the official update? That won't work, because your boot image is modified. Flash the stock kernel back and maybe the stock system if something is changed on it.
[Nexus 7 Original Development] joaquinf:
I noticed that too, but actually i have a vague memory of seeing that on the stock 4.2.1 kernel too (and i'm pretty sure that with trinity too) so maybe we were running some interactive tuneables that never made it to the update :confused:

Maybe francisco can give us a heads up.

No. Different parameters. And stock tuneables are running on pair (if not slightly better) with our magic values so i guess that we would need to test again from there.
[Nexus 7 Original Development] malaroth:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Aargh damn the unluck of not having an n7 yet! I'm itching to finish tweaking and now interactive tweaks! Betcha I could get deadline and ROW even more sweet. Hopefully soon, in the meantime I'll wait for the Gnex updates to roll out and go from there

Franco r364
[Nexus 7 Original Development] Metallice:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

The android common 3.4 kernel was updated 33 hours ago and still uses the same parameter names for interactive (which is the interactive Franco and I use)

Remember the stock tegra interactive is very different from the android common interactive with things like exponential scaling, tegra hotplug locking, etc.

These new parameter names are probably just the awkward result of merging the new target load based interactive patches into this custom governor.

Unless Franco goes back to the tegra specific interactive the parameters shouldn't change in his kernel.

Personally if the new tegra interactive has this new load based scaling and all the other patches merged/hacked in, I see no reason not to use it in M-kernel. (After I remove that dumb exponential scaling of course)
[Nexus 7 Original Development] TheByteSmasher:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

OK, I've been here long enough to know the N7 IPS display is different from the N4, but I don't understand enough of the internals to know why we can't color/gamma correct it. My N4 makes the N7 look washed out and kinda crappy... does anyone know of a fix?

Sent from my Nexus 4 or 7
[Nexus 7 Original Development] ÜBER™:
AFAIK nobody has found the values that modify it.. which there is the likelihood of not being any.
[Nexus 7 Original Development] siscim23:
From what I understand, Asus just didn't allow for color/gamma adjustment when they made the drivers.
[Nexus 7 Original Development] ashclepdia:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

I'm still keeping my fingers crossed someone will figure out SOME way to adjust screens

look at the N4 for instance. they weren't able to adjust those colors until recently when after they changed it on an official update, devs went back thru and found the codes changed and were able to use that to get them the ability to make custom adjustments(from what I understand anyways)

I'm hoping tegra(Nvidida) or Google will end up doing something like that for us and someone catches it. would be GREAT
[Nexus 7 Original Development] osm0sis:
That's what I've been saying. :)

They already have changed the colors between JZO54K and JOP40C, so there must be a way.

Edit: Anyone notice that the new stock interactive defaults are basically our winning settings? 15000 / 0 / 90 / 1000 MHz / 1 / 45000 / 30000; is someone from nVidia following the thread here and ganking our tweaks? What's more likely, that, or us predicting the future? :p

P.S. I made a francenstock grouper = stock JDQ39 + franco's ramdisk if anyone wants to play around with stock before Francisco releases a new build:

http://www.sendspace.com/filegroup/SEtis71UnXju7TN4ip0XFQ
[Nexus 7 Original Development] Metallice:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Interactive didn't change at all according to new source :/

Who was it that was claiming it did?

Sustain load and go maxspeed load still refer to exponential scaling as always... so they didn't update interactive to the new kind.
[Nexus 7 Original Development] Remoteconcern:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

My 100% stock settings are not like that at all. Probably some saved app data or something.
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Thats what I thought. I knew ive had seen those tuneables on stock 4.2.1.
[Nexus 7 Original Development] malaroth:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Hey, imitation is the highest sort of praise. If they did see the winning tunable and came to the conclusion that we were right, it'd only make sense implement it. The better the device runs, the more likely someone will buy. Credit for it would be nice but it is an open forum

Franco r364
[Nexus 7 Original Development] Metallice:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Umm the never changed them... so your "winning" tunables ended up being pretty much the stock values...

Edit: oh wait maybe they changed the ramdisk... need to check that... although I doubt it.

Edit2: nope no ramdisk changes
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

I posted some screenshots of the interactive stock tuneables yesterday and they are definitely not the same as out winning values. On the other side, stock kernel is running damn smooth, I can't wait for Franco :)
[Nexus 7 Original Development] Metallice:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Argh well why are people saying they are??? You guys are confusing.
[Nexus 7 Original Development] adame09:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

I got high battery drain today on this kernel my tablet was charged fully this morning at 6am and by 12pm it was on 20% without even using it once and when I tried to turn it on it was an sod

Sent from my HTC Sensation XE
[Nexus 7 Original Development] osm0sis:
Hmm my mistake I guess. Not sure how it happened considering I reset the f.Ku app data and nothing's set on boot, but there you go.
[Nexus 7 Original Development] N@th_OC:
I have the same problem.

I cleared franco app data and let nothing set at boot.

But some settings like those tunables or gpu frequency was still set after i flash 4.2.2

It's not the first time i notice this problem with franco app.
[Nexus 7 Original Development] franciscofranco:
4.2.2 kernel only has 3 changes:

https://android.googlesource.com/kernel/tegra/+/110f581ded86c64c0a3ce4884daf3046a6395b2e

https://android.googlesource.com/kernel/tegra/+/8722d5e9b3d4bc96d433148d05334823631a645b

https://android.googlesource.com/kernel/tegra/+/05b777c19883248ea341945a243ddb64859cd3e7

I'll release an update in a few minutes containing that.
[Nexus 7 Original Development] N@th_OC:
Sorry, i know this question was ask before, but i never saw the answer.

Will you implement OTG fixe in the next release?

Another thing, some of us have seen in your app, even after clearing data and uncheck all things set i boot.

When you update to 4.2.2 or any other Rom. Some settings are still randomly stick.

Like governors tuneable or gpu frequency.

Thanks for all man!
[Nexus 7 Original Development] franciscofranco:
There is an OTG fix?

Thanks for the heads up!
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Hahaha your confusion confuses me

Noob!

:p

He meant that we currently don't have the ability to natively mount usb storage without an app like stick mount.
[Nexus 7 Original Development] osm0sis:
Awesome! Please remember the read_ahead_kb of 512. :)

Also, please again consider changing that line of your .zip updater-script from

package_extract_file("boot.img", "/dev/block/mmcblk0p2");

to

package_extract_file("boot.img", "/dev/block/platform/sdhci-tegra.3/by-name/LNX");

I keep thinking about that guy who flashed this on his N4 and ruined his sh*t. :(

Edit: Since I know your intention in the GN zip with extracting those empty folders was to create init.d, may I also suggest (for all your zips)...

run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/sh", "-c", "mkdir /system/etc/init.d");
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
unmount("/system");

:D
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][10 FEB] franco.Kernel - r46

Poor guy that was sad. Remember the one in the gnex thread claiming that his kernel version of didn't change after flashing the zip.... And he had a n4 :facepalm:
[Nexus 7 Original Development] osm0sis:
Exactly! That guy got lucky that the GN zips have the architecture-specific by-name mountpoint or he could have been in the same boat. I only want the same relative safety for the N7 zips. :fingers-crossed:
[Nexus 7 Original Development] franciscofranco:
Here we go r47 compatible with 4.2.2 and 4.2.1. Included the new 3 patches, auto OTG mounting on the ramdisk and merged the latest changes on the hotplug driver from Mako. And with this one the Nexus family is complete with 4.2.2 kernels :)

And osmosis I forgot all that stuff, I PROMISE I will add them on r48.
[Nexus 7 Original Development] osm0sis:
Haha, thank you!! :D

One last thing.. I see you have 360 instead of malaroth's 350 for read_expire in the deadline tunables. ;)

Edit: Hmm.. And UV is definitely still broken.. :(
[Nexus 7 Original Development] franciscofranco:
I didn't have time to check that, sorry!
[Nexus 7 Original Development] osm0sis:
That's okay! Just making sure you knew. :)

Thanks for all the work Francisco. How was the visit from your lady friend? Was it her first time in the States?

I've never been on the west coast. I'd love to check out Cali some time. :good:
[Nexus 7 Original Development] franciscofranco:
It was great :) we had tons of fun around here. You should, Silicon Valley is a pretty damn nice place to live.
[Nexus 7 Original Development] swedkg:
Re: [KERNEL][GPL][N7][15 FEB] franco.Kernel - r47

Sorry if this will sound funny to you and please forgive my ignorance, but are there any restrictions of the file sizes that can be copied on the ramdisk?
[Nexus 7 Original Development] wejgomi:
kernel

Something's wrong with hotplugging on r47. No matter how low the load, 2nd core seems to be always on. Also had some reboots after flashing but guess thats related with my UV. Wejgomi
[Nexus 7 Original Development] ROFLkopter:
Re: [KERNEL][GPL][N7][15 FEB] franco.Kernel - r47

How much you undervolted by?

Sent From My Awesome AOSPA3.+/franco.Kernel Powered Nexus 7 With XDA Premium
[Nexus 7 Original Development] Remoteconcern:
Re: [KERNEL][GPL][N7][15 FEB] franco.Kernel - r47

That's the new hot plug behaviour I think. Supposed to be like that.
[Nexus 7 Original Development] yangers:
Can I use flash gui to install this kernel?
[Nexus 7 Original Development] Hussainally:
Yes I do that .works well
[Nexus 7 Original Development] yangers:
Did you have to rename the img to recovery.img?
[Nexus 7 Original Development] Jubakuba:
Endless SOD's on the last two.

Literally, without exception, if my screen is off (stock settings) it will SOD within an hour.

CPUQuiet > Balanced is the fix, correct (switched to faux since the last two have been bad...but I just want to see if that fixes before returning to faux again)?
[Nexus 7 Original Development] irminsul:
Didn't franco mentioned he lowered the voltages by 25mv?Why don't you raise them by 25, to see if the issues going away?
[Nexus 7 Original Development] sotoskawasaki:
Even if that was the problem, there is no UnderVolt interface in the Kernel. So he cant change the voltage. Nevertheless -25mV is such a small amount that in no way could cause issues.
[Nexus 7 Original Development] franciscofranco:
I need logs, otherwise theres nothing I can do.
[Nexus 7 Original Development] osm0sis:
Franco is there any chance we would be able to get the 50MHz step back in a future build? I was getting crazy battery life with that as my minimum.
[Nexus 7 Original Development] jazzespresso:
Hi Franco,

First thank you for this kernel.

I have Nexus 7, and of course $25 google play store credit;)

so I went ahead bought your app - franco.Kernel updater- from play store. you know, had to spend $25 credit somehow :)

Anyway, if I use your app and flash the kernel, I am all set, right? I don't need to do any additional configuration such as voltages change like others talking here? voltage changes thingy, I am so confused on that...

all I want is a kernel, flash it, and done with it, and let the kernel do its magic without any additional config change or modifications :)

thanks
[Nexus 7 Original Development] Testingchip:
That's it. I flashed r7 last night before bed and haven't had any problems yet.
[Nexus 7 Original Development] Lozzo:
All seems OK here so far, good work. Remind me to go and buy your updater app with my free Play credit.. :D

One thing I have noticed though, is that it occasionally leaves 2 CPU cores active whilst idle.

Looking at things in system tuner, when this happens, core 0 and 1 will be enabled at idle, and both will stay in sync with each other, frequency wise, but never drop back to a single core. If I then change the CPUQuiet govenor from runnable to balanced and then back to runnable again, it'll go back to a single core whilst idle, with the other cores coming online and offline as needed, as usual, until a second core gets "stuck" online again.

Which logs would you need in order to see this behaviour?
[Nexus 7 Original Development] Lozzo:
Haha. And, amusingly enough, a SOD. :D Just picked it up to have a read, last time I had it on was 5pm ish (currently 7.20 here) and nowt.

Attached kmsg in post. Quite a large one, last time I looked at last_kmsg it was only a couple of paragraphs.
[Nexus 7 Original Development] cassius_20:
Hmm, even though I tried setting 51 as my min on r6, it'll still revert back to 100. Haven't tried r7 yet; I'm assuming r7 does not have a 51 step at all?
[Nexus 7 Original Development] gapone:
I have SODS too but changing cpuquiet to balanced fixes it. This is with the latest r7. I have to change cpuquiet to balanced every time I reboot because both of set on boot settings doesn't work for cpuquiet governor. Power mode set on boot doesn't work either when I tried to use balanced... After reboot max frequency is back to 1.3ghz. Franco please fix this...
[Nexus 7 Original Development] osm0sis:
It shows as 100Mhz on r6 but I believe it actually used the 51Mhz step as shown in the Min Freq menu. r7 does not display the step at all so truly defaults to 100Mhz. :(
[Nexus 7 Original Development] ysagas:
Franco,

Any chance we can get USB fast charge on the nexus 7?

I love it on my galaxy nexus but is not available for the n7.

Thank you!
[Nexus 7 Original Development] franciscofranco:
Nah, 50Mhz is really too low for my taste. I removed it from my One X kernel as well. The chance of having a SoD is much bigger with such low frequency. You won't notice any battery difference using 50 or 100.

You don't even need my app to be all set, you just get a big array of options and settings to use + easy to update the kernel using it. But yes, you just flash the kernel and are set and good to go :)

Thanks for the feedback I didn't observe that behaviour, but by your description it should be pretty easy to reproduce. Just use Balanced then, you should be fine.

Thanks. Try to change to Balanced.

CPUQuiet governor is not meant to be set on boot, so theres nothing to fix there. Max frequency is back to 1,3Ghz on reboot because the PowerHAL that Google added does that little trick. I'll have to compile one from source and change it in order to fix that stupid behaviour.

I don't know if that is possible, but I can look.
[Nexus 7 Original Development] ricardowec:
Francisco

Just installed r7. My CPU does not go bellow 400 MHz.. is that normal . Using EOS rom.

Cheers

Sent using The Beast via Tapatalk 2