yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] franciscofranco:
Just pushed r50 with a bunch of goodies:

* Backported my new Hotplug driver from my Mako kernel. Its completely 100% written from scratch

* Also added possibility to tweak the load thresholds here: /sys/class/misc/tegra_hotplug_control/

first_level -> load threshold to online all cores. Default is 90% system load.

second_level -> load threshold to online 1 core at a time. Default is 50% system load.

third_level -> load threshold to offline all cores. Default is 30% system load.

* Pushed interactive to its newest version

* Kernel boots with IO winning values from the usual suspects, thanks guys

Let me know if this version has fixed the random freezes from the latest one. Any constructive feedback is appreciated.
[Nexus 7 Original Development] NoobieExtraordinare:
Just switched from trinity to r48 a few hours ago and now to r50 . Probably not very helpful but quadrant score dropped from 5441 to 4869. Interactive / row in both cases and didn't change anything else. Tapatalk hd seems to have a bug that crashes the app while trying to attach images.
[Nexus 7 Original Development] franciscofranco:
I don't really cater for bencharmarks at all.
[Nexus 7 Original Development] NoobieExtraordinare:
Figured as much. :cool:
[Nexus 7 Original Development] zaclimon:
Hmm so far, The lockscreen delay seems to be fixed and the UV interface seems not fixed yet as I tried to put -300mV and it didn't froze up on me... :eek:
[Nexus 7 Original Development] franciscofranco:
My UV code doesn't allow for <600mV values!
[Nexus 7 Original Development] zaclimon:
Oh hmm I don't understand that one. So from what you're saying, your code shouldn't allow a uv farther then 600 mv right? I've tried to uv it by 300 and it didn't work unless that I can actually uv it by 300? :confused:
[Nexus 7 Original Development] franciscofranco:
Means that if you try to input a value lower than 600 it won't save that value. But I agree that this UV business is kinda messy. I have to re-write it all from scratch (kernel wise).
[Nexus 7 Original Development] Trewyy:
My device only froze once I asked it to GIVE ME power. ie. 100mhz was set at less than 0mV

I think the kernel wins the award for the best under volt at -800mV ;)

Trewyy <3
[Nexus 7 Original Development] zaclimon:
Oh thanks for the explanation, however even when u drop it by 100, I don't notice any perceivable difference. Oh well, it can be my device too the problem.
[Nexus 7 Original Development] Culex316:
I just experienced some weird random freezes on r50 running stock rom so I had to go back to r48 which was working perfectly for me. It was during web browsing with a few tabs open and when I opened the app drawer.
[Nexus 7 Original Development] trailblazerz11:
Main problem I had with r48 was delayed screen on. Fixed in r50 and quite smooth everywhere else, have had some lag spikes but not sure its kernel related
[Nexus 7 Original Development] amangbulits:
using r50 very nice and absolutely fast kernel great work thanks
[Nexus 7 Original Development] poondog:
So do I, maybe for a few seconds then its back to normal. Would a log cat or something be useful or not? Obviously I don't know when it will happen :P

Very impressive kernel though, it's smooth as !
[Nexus 7 Original Development] H84:
I dont get how to set max core, to ex only use 2 cores instead of 4. ?

Skickat från min Nexus 7 via Tapatalk 2
[Nexus 7 Original Development] Puzzlegirl:
I had a problem with r50 initially when I was updating apps in the Play Store. I have System Monitor running and saw that the CPU was at 100% and only one core was active. It didn't quite freeze, but it was extremely slow! I cleared the data in Franco's app and the other cores came to life. Everything has been smooth sailing since then and it's great without that lag when switching on :)
[Nexus 7 Original Development] Voda_Smart_2:
I had the same problem but I was using Maps, CPU was on 100MHz only when I succed to check.
[Nexus 7 Original Development] fozzie:
Same here; device was really laggy, only a single core active at 102MHz. After a reboot though, all has been ok.
[Nexus 7 Original Development] slebit:
Same lag for me. It lasted for about 30 seconds, and then it stopped.
[Nexus 7 Original Development] The Gingerbread Man:
I haven't had chance to try the new build properly yet but try Puzzlegirl's advice and clear the Franco app data and reboot. Report back after having completed this and given some time to play wit your device and tell us if that helped or not. I cant get to my n7 for another 7 hours or so

Sent from my Galaxy Nexus
[Nexus 7 Original Development] Shano56:
Woo! Thanks for the update Franco. I will test when I get home after work :)
[Nexus 7 Original Development] sjknight413:
All seems smooth and fast here, no lag at all!

One thing though, are we meant to be able to tweak hotplug parameters in fku?

Nothing is showing up under hotplug control!

Edit: wow this is seriously smooth! Francos kernels have never been this smooth for me :)
[Nexus 7 Original Development] fozzie:
Nope. Command line only for now.
[Nexus 7 Original Development] polik1:
I have two quick questions. Runnging latest franco.Kernel r50 with franco.Kernel updater (paid).

1) Does undervolting really work?

2) Is there an app I can check live voltage? System Monitor built in franco.Kernel updater doesn't have this feature.
[Nexus 7 Original Development] sjknight413:
Ah, I spoke to soon.

Just had chrome lock up on me and cause extreme lag for about thirty seconds until it eventually fc'ed. Never happened before!

Edit: and again, seems to be chrome causing issues. I have logging disabled so I can't grab a log unfortunately.
[Nexus 7 Original Development] Gspin96:
I got extreme lag after 1-2 minutes playing Dragon Fly or Jetpack Joyride on r50. That lag is not present in r48 so i reverted to it (also, I don't get any screen-on lag on r48, it lights the screen in less-than-one-second).
[Nexus 7 Original Development] Shano56:
He has yet to push the update to the fku app. You just gotta wait for him to update, then you will be able to change values via gui :)
[Nexus 7 Original Development] nereis:
A word of warning with r50...

I just had the device lockup and decided to power off, flashed back to m-kernel and all the sudden Slim Bean 3.0 hard reset itself. I am not blaming this on Franco's kernel but just wanted to share this experience.
[Nexus 7 Original Development] puffel86:
I flashed r50 today and had some problems. I had an freeze in chrome...after some time i got a black screen and later the colored x showed up. Looked like an reboot but it was so slow that i had to hard reset.

And after that i had some really bad slowdowns. One was in firefox beta, one in temple run 2 and one was starting modern combat 4...but in this cases i could open the taskmanager and kill the apps and then it was normal. That seems to be a bug with these slowdows.
[Nexus 7 Original Development] NoobieExtraordinare:
Delayed screen on issue in r50 still there especially if you have a few background apps.

---------- Post added at 11:10 AM ---------- Previous post was at 10:37 AM ----------

Multiple crashes and lots of lag on 50. As cores came on and speeds were throttled, system and ui became completely unresponsive. Didn't crash this time but took a while to recover. I was watching a streaming video on chrome. I didn't back up r48, gotta figure out how to reflash it.

Also, I have the Franco app (paid version) the and the hot plug control menu is a blank. Is this by design?
[Nexus 7 Original Development] Ronaldo Forenucci:
Get Kernels here:

http://minooch.com/franciscofranco/Nexus7/4.2/

Place .img file in kernel_backups and use FKU to flash back. After a ROM update, you can also use it to back up the Stock Kernel (if the ROM uses it as default)...it is called boot-#1.img.

Please get Franco any logs that you can if you have problems.

RF
[Nexus 7 Original Development] GedBlake:
Fastboot flashed r50 a couple of hours ago... all appeared well, until I ran Temple Run 2. This immediately caused serious lag to the point of nearly locking up the device. Fortunately, I managed to 'Force stop' it... subsequently Temple Run 2 ran OK... for a while, and then lag began to creep in again; less serious than the first time, but still significant.

Anyway, I'm back on r47... and all is good again:).

Rgrds,

Ged.
[Nexus 7 Original Development] jomaxwel:
r50 has some issues with freezing here to. Twice while watching YouTube videos and once on lock screen while streaming audio via Bluetooth.

I am new to this kernel but on r47 I had issues with deep sleep as well. It would power down to lowest setting but would not go into deep sleep for 10+ hours of being left be. I think my search for a kernel continues. :(
[Nexus 7 Original Development] nealkoy:
same reported lag experienced when playing youtube vids making operation problematic . clearing franco app and reboot made no difference .

changed governor to ondemand... so far lag not experienced with the same usage...

Sent from my HTC One X+
[Nexus 7 Original Development] xonone:
I have also had this problem plus lag / sound problems with winulator running both c3 and sc1. Not as bad as last update tho.
[Nexus 7 Original Development] sjknight413:
Aha! so it looks like the new interactive patches Franco pushed are the culprit!
[Nexus 7 Original Development] timbck2:
Extreme lag with r50 here as well, with several apps. I was using interactive governor, I'll try later with ondemand.

Sent from my toro or grouper
[Nexus 7 Original Development] simonb255:
Getting a lot of lag playing videos on r50
[Nexus 7 Original Development] osm0sis:
Those who can easily reproduce the lag try ondemand so we can confirm whether it's the interactive patches or the hotplug driver.
[Nexus 7 Original Development] johnnyman25:
Tapatalk HD crashes for me to when I try to attach images. This happens after last update of Tapatalk.

Sent from my awesome Nexus 7 using Dirty Root Box v2.5 & M-Kernel a46
[Nexus 7 Original Development] xonone:
Anyone else having problems rebooting / shutting off? my nexus keeps freezing when I try to reboot.
[Nexus 7 Original Development] H84:
Minne works like a charm, did a clean flash even the kernel eraser script

No lag here

Skickat från min Nexus 7 via Tapatalk 2
[Nexus 7 Original Development] franciscofranco:
Its probably interactive, again. Will push r51 in 10m with that stuff reverted.
[Nexus 7 Original Development] franciscofranco:
Done.
[Nexus 7 Original Development] Shano56:
Too bad the new patches didn't work out. Thanks for the quick fix!
[Nexus 7 Original Development] arhung:
Thank you Franco, downloading....
[Nexus 7 Original Development] franciscofranco:
No biggie, I'm more interested in my hotplug driver to work as nicely as its been working on Mako.
[Nexus 7 Original Development] rene_r:
After upgrading to r51 hot plug control in Franco kernel updater shows an empty page. I already cleared the settings from the fku. Also cleared cache and davlik cache and rebooted. Reverted back to r47 solves the problem.

Br
[Nexus 7 Original Development] ÜBER™:
Its not a problem..:silly:
[Nexus 7 Original Development] rene_r:
How would you call it? A feature?!
[Nexus 7 Original Development] sjknight413:
Battery life seems really bad on r50/r51.

Barely hitting 4 hours screen on with a full charge.
[Nexus 7 Original Development] ÜBER™:
Its intention. He just added a new hot plug driver... And is reworking the hot plug control for the app. So yeah... Its not a problem.

Sent from my Nexus 4
[Nexus 7 Original Development] rene_r:
OK thx, I thought he changed only something internally which would not affect his fku.

Br
[Nexus 7 Original Development] sjknight413:
Just got a massive lag spike on r51 when changing volume whilst watching a YouTube video. Locked up for about 20 seconds
[Nexus 7 Original Development] ÜBER™:
Lol if he changed something internally then the app won't detect it thus the empty page. :)

Sent from my Nexus 4
[Nexus 7 Original Development] franciscofranco:
Locked up you mean the tablet completely freezed?

Just tried and no lockup. Can you change your IO schedule to noop and let me know if you can reproduce it please?
[Nexus 7 Original Development] sjknight413:
Yeah as in the same sort of lockup I was getting on r50.

Ironically it just locked up completely when I opened the recent apps menu to switch to fku and change the scheduler, it's still frozen now so I'm going to have to hard reset it.

It isn't reproduceable, it seems to happen randomly all over the place but I'll change to noop and see if it happens again.
[Nexus 7 Original Development] osm0sis:
Those aren't our winning deadline settings actually Francisco, we had to go back on them since nomerges 2 was such a bad idea. row is our only finalized one right now, then hopefully cfq by Monday. Stop by and check out our progress. We miss you. :)

I stayed on r50 and waited for the crippling lag to start.. Then (slowly) changed my governor to ondemand and it instantly resolved. So r51 should be fine if interactive was the culprit. Upgrading to test shortly after I make sure the lag won't come back on r50 with ondemand.
[Nexus 7 Original Development] simonb255:
Had some lag with Netflix on r51 switched to on demand and it solved the problem
[Nexus 7 Original Development] sjknight413:
I know my logless reports probably aren't helping you but my nexus just had another freakout.

Locked the device, it wouldn't switch back on for twenty seconds or so and when it did systemUI restarted itself with no fc.

Edit: I'm on row instead of deadline now too.
[Nexus 7 Original Development] franciscofranco:
****, so it might be those values. Can you post me here the winning values for ROW for the N7? I'm at work at the moment I don't have much time to check the googlegroup. Just post them here and I'll update the kernel with the correct values.
[Nexus 7 Original Development] The Gingerbread Man:
echo 100 > /sys/block/mmcblk0/queue/iosched/hp_read_quantum;

echo 75 > /sys/block/mmcblk0/queue/iosched/rp_read_quantum;

echo 5 > /sys/block/mmcblk0/queue/iosched/hp_swrite_quantum;

echo 4 > /sys/block/mmcblk0/queue/iosched/rp_swrite_quantum;

echo 4 > /sys/block/mmcblk0/queue/iosched/rp_write_quantum;

echo 3 > /sys/block/mmcblk0/queue/iosched/lp_read_quantum;

echo 12 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum;

echo 10 > /sys/block/mmcblk0/queue/iosched/read_idle;

echo 25 > /sys/block/mmcblk0/queue/iosched/read_idle_freq;
[Nexus 7 Original Development] franciscofranco:
Ok just pushed r52 ROW I/O as default using the values Gingerbread Man just posted. If you still have any lockups let me know how, what you were doing so that I can reproduce them.
[Nexus 7 Original Development] sjknight413:
lp_swrite_quantum doesn't go to 12, it keeps reverting to 2
[Nexus 7 Original Development] fozzie:
I think there's an error in those settings.

You may have missed my post earlier today about them.

http://xdaforums.com/showthread.php?p=39956460
[Nexus 7 Original Development] franciscofranco:
The N4 has a newer ROW driver, so some tunables are different.
[Nexus 7 Original Development] fozzie:
Ah ok, I see that now. (I didn't see anything device specific in osm0sis's script). Ta.
[Nexus 7 Original Development] osm0sis:
Entirely intended. Some are input values that resolve to the appropriate outcome values on both the GN and N7.

---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------

Yeah didn't know they'd renamed some tunables, ****ing stupid thing to do if you ask me. fozzie I'd love your help on making sure our values also resolve correctly on the N4. I'll PM you shortly if you're willing to help. :D
[Nexus 7 Original Development] fozzie:
Yeah sure. Anytime.
[Nexus 7 Original Development] mikespe:
Forgive me if this has been asked a million times already but can this kernel be used for Tilapia (3g model)? I only ask because the Franco app states it's downloading the Grouper version and I just want to confirm before messing with it

Thanks!
[Nexus 7 Original Development] franciscofranco:
Yeah works fine!
[Nexus 7 Original Development] FitAmp:
So r52 should be fine since it has proper values?

Just a bit confused (not enough sleep :p)

Nexus 7/Rasbeanjelly/M-kernel
[Nexus 7 Original Development] osm0sis:
So far so good! Flying with our winning row values and Francisco's new hotplug driver. :)
[Nexus 7 Original Development] FitAmp:
Great ! Flashing now :)

Nexus 7/Rasbeanjelly/M-kernel
[Nexus 7 Original Development] swift2989:
Don't want to overstep my boundaries Franco but would it be to much to incorporate the frandom module into this kernel

Sent from my Epic Touch armed with a Jellybean army to kill you Apple!
[Nexus 7 Original Development] TheNerd:]:
Dang Its only been a couple days since I checked this thread and its already on r52. Im on r48. Is there any difference from r48 and the latest version?
[Nexus 7 Original Development] _Johnito_:
Franco, your new avatar is very disturbing ! Where are you ??

---------- Post added at 01:49 AM ---------- Previous post was at 01:47 AM ----------

Skim the last 3/4 pages (5 minutes max) and find out all details.
[Nexus 7 Original Development] Lozzo:
Ahh, I didn't realise that. Makes sense. :)

Cheers!
[Nexus 7 Original Development] ashclepdia:
Am i the only one who's wifi icon in status bar stopped showing the signal level since updating to r9?

I still have full connection, I'm tethered to my Gnex, but right now it shows empty on the icon.

Doesn't bother me at all since i KNOW I'm connected. Just figured I'd mention it.

I've not changed anything else except for the kernel. If it isn't the kernel update that caused it I'm not sure what it could be since i haven't changed anything for a long while now lol.

EDIT::::

almost immediatly after posing this, the wifi icon filled up to full and is displaying fine now. Go figure lol. Ignore this :D
[Nexus 7 Original Development] spaceman860:
Its working fine here reboot your n7 that sometimes happens when setting a theme or system ui change

Sent from my BAKED N7
[Nexus 7 Original Development] ashclepdia:
Yea i hadn't changed any of that, not sure why it was happening, it's fine now tho. Was like that for a while. Not sure what happened, guess my nexus 7 saw i posted about it so it fixed itself lmao
[Nexus 7 Original Development] leelaa:
Franco, any chance you can give it another go with panel voltage increase?
[Nexus 7 Original Development] JRJ442:
I personally can't wait to see Trinity Contrast and color multipliers ported over. The screen will be so pretty then :)
[Nexus 7 Original Development] franciscofranco:
Difficult explanation. Its not an app bug I assure you, its just how we fetch voltages/frequencies from the kernel. I'll try to come up with a good explanation later on without involving 2349823948234 buzz words.

Hmm thats very odd. What app version are you using? Well the only way to flash the boot.img is to push it to the partition manually via Terminal app.

dd if=/dev/block/mmcblk0p2 of=path_of_image/boot-r9.img bs=4096
[Nexus 7 Original Development] ricardowec:
Last one.. as a matter of fact ..I flashed another kernel just to see if your app was clashing with the EOS kernel.. and the same thing,

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] toanau:
Just curious when u use Franco app to install his kernel does it wipe cache or does it matter?
[Nexus 7 Original Development] ricardowec:
Cont'd from my previous post.. how can I DL r9 without a PC. The app keeps on rebooting my N7.. just to make it clear it is the latest version of your app

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] espionage724:
Awesome :)
[Nexus 7 Original Development] franciscofranco:
In the first Tab of the app does it say that your device is supported? The link to download boot-r9.img is in the OP, just download it to your device and run the command I posted last page.
[Nexus 7 Original Development] bigeyes0x0:
@franco: May I ask about your UV sysfs? Why is it different than the one on GNex or motley's? Yours is totally different than the normal "freq_nummhz: vol" and why does it have multiple entries per frequency slot like below?

1300 1200
1300 1175
1300 1175
1300 1150
1300 1125
1300 1100
1300 1075
1300 1050
1300 1025
1200 1000
1150 975
1050 950
860 900
860 875
700 850
700 825
520 800
520 775

It made my app crash, I fixed it but it's still weird to see something like this. Is it a bug? Do you plan to make it compatible or is there something about this format that I don't know?
[Nexus 7 Original Development] DJLamontagneIII:
Bought the app today and just have to say great job this kernel is smooth :D
[Nexus 7 Original Development] duyquang27:
This kernel is good. Still smooth when I change to power save in ur app, battery good too.

But i think it not for gaming. I got some lag when play modern combat 3.

And in ur app, Setting tab, i saw CPU core 1,2,3 is offline, how do i active it, nothing happen when i touch it.
[Nexus 7 Original Development] jamesst20:
Benchmarks of this kernel beats over 500+ in benchmarks then Stock/Faux kernel :P
[Nexus 7 Original Development] ricardowec:
I think I pinned the issue to System Tuner app. For some reason it does not get along well with your app. Either of the two can be present but not both. Now, this was not the case with previous versions of your app. I recovered past versions of System Tuner with same result: reboot

Anyway,I got your MAGIC up and running.... waiting for you to make up your mind and don't send me to read the OP if i ask for OC.

Cheers

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] jarjar124:
My settings for some reason r not sticking on the Franco app.
[Nexus 7 Original Development] mssam:
think he's got an update coming for it...
[Nexus 7 Original Development] :
r9 on Aokp v2 all good. Settings stick fine on your app on my end. Set to boot, reboot and they stick fine on my end.

(Edit)

I did try & run antutu just now and seems min wont go past 1000, says cant set min higher than max but max is 1500.. No biggy iz just gonna run it to death for a few and see what I can crank out.:sly:
[Nexus 7 Original Development] k29er:
R52, wow, that's fast and smooth. Hope battery life is good and I'm set.
[Nexus 7 Original Development] osm0sis:
Best I've seen the screen-on wait time since JB4.2 arrived too. Sometimes takes an extra press of the power button, but it's like 1 press instead of 10 and, when it does register the press on that second try, it pretty much instantly turns on now. :good:
[Nexus 7 Original Development] Antob125:
So no need for init.d file correct?

Sent from my Galaxy Nexus
[Nexus 7 Original Development] timbck2:
Hmmm. The screen-on delay isn't any better than it was just r48 for me; it still takes 3-5 seconds to come on when I press the power button.
[Nexus 7 Original Development] osm0sis:
Francisco only has row in there, so if you want to use any other scheduler with our test values, 950iosettings is still required.

Really? Damn. I realized the second-press thing for me was just the fact that the first press was counteracting my new magnet cover - still getting used to it. :p

So honestly, best I've seen the issue since we started with JB4.2 and _thalamus' hotplug driver as markj suggested might be related. Meaning switching to Francisco's might be why I find it almost as good as JB4.1.x now. Do you have any lockscreen widgets or anything else that could complicate the issue? Many users are reporting issues with lockscreen widgets slowing things down in weird ways; the Play Store download+install lag/freeze, for example.

Once it's on if I turn it off and on, off and on, rapid fire a few times, then the wait time gets worse and worse. Probably also the lockscreen widget interface to blame, so be aware of that for your testing. First try is much improved for me now though.
[Nexus 7 Original Development] timbck2:
Now that I've played around with it some more, it does seem a lot better than it was in r48. I don't have any lock screen widgets (just the default clock). I guess that time I said it was slow was just a fluke.

Sent from my grouper or toro
[Nexus 7 Original Development] FitAmp:
My screen is always on instantly with 1 press :p

Nexus 7/Rasbeanjelly/Franco.Kernel