yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Hackerlacka:
My Nexus 7 just turned off not(screen is off) responding when I press the power button. I put it in charger, no respond. I use the latest Franco kernel r57 and SmoothROM v5.0 and TWRP recovery. Please help

Edit: seem to got it working again by holding power button down for a long time and it booted up.
[Nexus 7 Original Development] krzysiekcfc:
What is the situation with the battery in this version?

Copy (cloud storage-10GB): https://copy.com/?r=hYVdRj
[Nexus 7 Original Development] Robin2:
The same happened to me, after switching governors (might be related). No problems after that.
[Nexus 7 Original Development] konradsa:
I am also back on R47 for now. Would be great if Franco could label some releases as stable and others as beta/alpha for the less adventurous of us.
[Nexus 7 Original Development] osm0sis:
This is still the slow crawl to milestone 1, after that it should be a bit more straightforward. :)
[Nexus 7 Original Development] CamoGeko:
All releases are beta until we get to Milestone. ;)

Pretty sure things are moving slowly here because he's focusing on Nexus 4 right now.
[Nexus 7 Original Development] osm0sis:
He also doesn't think there's anything wrong with the hotplug driver over here.. ;)
[Nexus 7 Original Development] ÜBER™:
I don't think there is. As it works just fine for the mako. I honestly think the governors are to blame. Or the frequencies. Maybe 102 is too low? 275-325 maybe for the first step. Can anyone reproduce the lag if their min is 400?

Sent from my Nexus 4
[Nexus 7 Original Development] FitAmp:
I think the hot plugging is fine, but its the tunables that need some tweaking

Beamed via NFC
[Nexus 7 Original Development] osm0sis:
The tunables are fine. If it's not the hotplug driver, it's the governor itself. ;)

Considering the video issue still exists at the AOSP interactive stock tunables: 98 go_hispeed_load, 1300 MHz hispeed_freq, 90 target_loads, it pretty much can't be the tunables' faults, and my lean would still be that it isn't the governor's fault either. The N4 is a powerful device, I wouldn't be surprised if it masked an underlying problem with the hotplug driver quite well.
[Nexus 7 Original Development] The Gingerbread Man:
Am I right in thinking in r56 introduced a newer interactive and r57 reverted it? So if r58 has this new hot plug driver how well would that work with the newer interactive governor?

Sent from my Galaxy Nexus
[Nexus 7 Original Development] ÜBER™:
Actually r5x introduced the new interactive and hotplug driver, r56 reverted it, and r57 has the fixed hotplug driver in it (helped smooth out the UI).
[Nexus 7 Original Development] The Gingerbread Man:
I don't have my device on me to test right now (at work) but increasing the lowest step I feel wouldn't be good as there are times battery could be wasted using the device for basic tasks like mp3 but I do feel maybe adding 250mhz step might be a good idea as its nicely between 400 and 100.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] ÜBER™:
Im pretty sure its just the min frequency is too low, maybe even 192 and then a 250 step?
[Nexus 7 Original Development] osm0sis:
Or the previously proposed freq lock for media playback like other kernels have done. I can't reproduce the issue at 475 MHz so that'd be fine.

I don't think adding steps would make a difference if the governor doesn't think the load is high enough to use them. Worth mentioning we're back to stock stepping too, so really, causality should be pretty narrow.

I think y'all missed my edit: ;)
[Nexus 7 Original Development] The Gingerbread Man:
I don't think 102 is too low as if I recall the stock n7 has 102 step and Franco reworked the steps to match the original speeds as having them at regular intervals causes lag like 100 300 500 700 etc But yes adding in a 250(ish)MHz step is definatly what I'm suggesting :)

Sent from my Galaxy Nexus
[Nexus 7 Original Development] ÜBER™:
Actually it goes as low as 51, but during media playback it is at 400+ which is when it kicks into the real cores instead of using the low power virtual core which is 350, 275, 102, 51 i think.. im not sure of the exact freqs.. but you get the point. It uses these when nothing is being done like reading a book, not playing a video.
[Nexus 7 Original Development] osm0sis:
N7 has a 51 MHz step that franco removed since he felt that was too low; that's the only difference in the table. Though of course there's the whole huge difference of us only using the G cores over here where stock has the LP.

---------- Post added at 02:55 PM ---------- Previous post was at 02:52 PM ----------

Very, very good point. Perhaps the G-cores just don't like running this low, since they never would by design. A frequency lock at 475 (where they'd normally run) for media playback seems like the best option here to me, since there's no guarantee that adding an intermediate step would even get used, considering it's already deciding to drop to the lowest as it is.
[Nexus 7 Original Development] The Gingerbread Man:
The more I think about it a frequency lock for media does seems like the best solution theoretically, we certainly have given him some work for this weekend lol

Edit

Out of thanks but cheers Os and Uber that was helpful!

Sent from my Galaxy Nexus
[Nexus 7 Original Development] CamoGeko:
Perhaps we should just use Ondemand for now? ;)
[Nexus 7 Original Development] osm0sis:
ondemand doesn't "fix" it either. :(;)
[Nexus 7 Original Development] CamoGeko:
Ah so it kinda half fixes it then. ;)
[Nexus 7 Original Development] Exostenza:
If the stock clock of the n7 is 1.3ghz and Franco is supposed to run stock why does it set the cpu to 1.2ghz?
[Nexus 7 Original Development] osm0sis:
Wha? It's exactly 1300 MHz.
[Nexus 7 Original Development] fozzie:
It doesn't.
[Nexus 7 Original Development] Gspin96:
I didn't know that. Is it a lack in the kernel or this is intended? And if intended, why? :silly:
[Nexus 7 Original Development] ÜBER™:
Because franco felt that it was using more energy to switch over to the main cores than to just leave it running with the regular cores at a lower frequency and voltage.
[Nexus 7 Original Development] glava34:
Anyone else having serious problems with YouTube?
[Nexus 7 Original Development] Robin2:
Seriously.. All the posts above you address this issue.
[Nexus 7 Original Development] osm0sis:
Hilarious. :laugh:
[Nexus 7 Original Development] Metallice:
There's a reason why faux and I have locked the min to 340MHz during audio playback for months now...

Otherwise on demand gave stuttering... But it was never an issue with interactive so it may be a different issue entirely.
[Nexus 7 Original Development] poondog:
I am having problems too actually its lagging sometimes

And I +1 to the frequency lock idea, I think that will help
[Nexus 7 Original Development] lollyjay:
This issue has been discussed here for the past 3 to 5 days. Temporary solution s include setting governor to Ondemand.

Nexus 7 WiFi 32Gb | PA 3.15 25-Mar2013 | Nova Prime | Franco-Kernel r57

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Original Development] osm0sis:
Which isn't really a solution, in that it doesn't entirely get rid of the lag/audio distortion, it just makes it useable.

The only legit workaround I've found so far is to set the min to 475 MHz.

P.S. markj was just kidding. You'll notice he's been heavily involved in the discussion the whole time. ;)
[Nexus 7 Original Development] lollyjay:
Ondemand alone has completely overcome YouTube lag with my configuration.

Nexus 7 WiFi 32Gb | PA 3.15 25-Mar2013 | Nova Prime | Franco-Kernel r57

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Original Development] The Gingerbread Man:
Did you test lower than 340mhz?
[Nexus 7 Original Development] osm0sis:
It is there with ondemand at otherwise kernel defaults. It's just mostly gone so you have to try harder to make it show up. Which I did, and it did. ;)

I haven't been able to reproduce it at 475 MHz min at all on any governor. :)
[Nexus 7 Original Development] Metallice:
Any lower and you would get YouTube audio stuttering. The issue wouldn't occur on interactive since it would hover around 340MHz anyway.

Again not sure if it is related to your issues.
[Nexus 7 Original Development] osm0sis:
It might be, since people are seeing interactive drop it down to 102 MHz and one core. ondemand being a partial workaround makes sense that way too since it can be a bit more aggressive with scaling under reasonable load.
[Nexus 7 Original Development] lollyjay:
Nope, no problems whatsoever, even on HD.:D

Nexus 7 WiFi 32Gb | PA 3.15 25-Mar2013 | Nova Prime | Franco-Kernel r57

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Original Development] osm0sis:
Well lucky you then. :rolleyes: Others can still reproduce it. ;)
[Nexus 7 Original Development] The Gingerbread Man:
The difference in mhz could be the difference between you allowing the LP core to work and Franco disabling it, I read fauxs OP and couldn't see if it was enabled / disabled. I guess without the LP core enabled looks like we will have to go with 475mhz as I can't see Franco enabling the LP core anytime soon. I'm just looking forwards to the next build now as Os seems to have found a solution to this problem using 475 so hopefully Franco can add this frequency lock in for media processes without too much difficultly.
[Nexus 7 Original Development] osm0sis:
Franco could easily add another step. The LP core was disabled before Franco reduced the number of steps. Only issue with that is how interactive is choosing 102 over 475. Even if we had 275 or something in there, interactive might still just drop down to 102.
[Nexus 7 Original Development] The Gingerbread Man:
Going by what Metallice said about him and Faux using 340mhz for media processes without lag occurring I think if a new step were to be added that would be a good choice as any lower the lag may persist. But if a 475 freq lock were added adding a 340 step would be kinda pointless. I'd be inclined to say see how adding a 340 step works and if lag is still the for youtube then remove it and use the freq lock insteasd
[Nexus 7 Original Development] Gspin96:
But, if the frequency isn't high enough, shouldn't the CPU usage go to 100% and, by consequence, the governor ramp up the frequency?

If it gets the frequency down is because 475mhz is too much, right? Then, shouldn'this be solved just by adding an intermediate frequency where it can settle?

PS: I seem to get more noob every day :eek:
[Nexus 7 Original Development] osm0sis:
There is a calculation it does to decide if the load is worth the ramp and that's also based on what the step is, so it's definitely worth a try. Lowering the step should make it more likely for it to get used as the one above 102.
[Nexus 7 Original Development] romeo26222:
sorry I am new to all these android stuff, but I have a small question

does the kernel makes any different of the video codecs, I mean when I used faux kernel I can't run H264 encoded videos - I am using mxplayer pro -

but when I use this kernel I can run all types of videos,

regards
[Nexus 7 Original Development] SertaGE:
I'm trying franco r57 but my device restarting sometimes. What can I do? (I'm using stock rom)
[Nexus 7 Original Development] osm0sis:
Try flashing my emergency reset zip (link in my sig), it will help if there are f.Ku settings or init.d scripts to blame.
[Nexus 7 Original Development] bagoes.s:
After updated lags when running many social media & messenger, but I see RAM have many space 400 mb with low traffic data.
[Nexus 7 Original Development] fozzie:
The kernel doesn't do anything with the video codecs.
[Nexus 7 Original Development] jnocomski:
No color and gamma tweaks on Nexus 7?
[Nexus 7 Original Development] FitAmp:
No...

Not yet atleast

Beamed via NFC
[Nexus 7 Original Development] dj_ghosie:
Is there a cwm version available?
[Nexus 7 Original Development] ÜBER™:
Nope but if you buy his kernel app or use the free one you can auto flash from the app.

Sent From My Toro+ via White Tapatalk
[Nexus 7 Original Development] Ronaldo Forenucci:
Just bought the app to try the kernel. 3 questions:

1. When I first went into settings, I noticed an option to disable some sort of log for better, but minimal performance/battery. I did so, but now I can't see that option anymore. Does it disappear after checking that option?

2. Tegra Smart Dimmer: It was unchecked when I opened up the app, but it says it's enabled by default? Does checking that option use Smart Dimmer, or turn it off?

3. In the Voltage settings, I see a bunch of repeated freq's, is this normal?

Thanks,

RF

#1 Disregard, Logger settings came back after a reboot.

PS: Install went smooth as silk. Worked great for us kernel noobs!
[Nexus 7 Original Development] ÜBER™:
When unchecked smart dimmer is off and vice versa

And yes that is normal.. same thing happens in the Trinity kernel however i think Franco is going to fix this later.. its a kernel bug i presume.
[Nexus 7 Original Development] Ronaldo Forenucci:
Thanks Uber. I bought the app and tried this kernel because of your awesome battery life post. What settings are you using? Have you under-volted? Right now I'm at ondemand/balanced, 100Mhz/1200Mhz but haven't touched the voltages yet.

Thanks

RF
[Nexus 7 Original Development] ÜBER™:
Im going to update my doc for my N7 kernel settings. Im on 200/1300 the "stock" voltages with Interactive/Balanced it seems to be a great combo. Im at 8% with 6H44Min screen on time left. So i estimate around 7H20min at ~1%. Ill post it up when its drained but that has been my greatest amount yet since moving to Franco from Trinity. :good:
[Nexus 7 Original Development] cwc3:
Would like to be able to change the scheduler sometime in the near future with your paid app. Nitpicking, I know. Also looking forward to the voltage table being figured out, something I also noticed on Faux's. I believe Motley's has it working though if you wanted to use that as a reference.

Love this kernel for how clean it is. Not going to name any names, but this is how I see a lot of other kernels:
[Nexus 7 Original Development] Ronaldo Forenucci:
Sounds good...it would be much appreciated.

I seem to be having a problem getting the max CPU setting to 'stick'. When I choose 1200, it changes to 1200...but when I go back into the app, it's at 1300 again. This isn't after a reboot, just backing out of the app, watching a YouTube Video, and then going back into the app.

RF
[Nexus 7 Original Development] ÜBER™:
LMAO! :laugh: thats too funny. I love this kernel as well very clean.. very similar to stock but with minor tweaks.
[Nexus 7 Original Development] ÜBER™:
Oh here is my final display time.

Sent From My N7 via White Tapatalk
[Nexus 7 Original Development] anilpalepu:
Got more than 10hrs screen on time with r9..using rasbean jelly ROM..no underclockimg or undervolting..

used majority of the time to study by doing questions using usmle world app which requires WiFi on..WiFi always on except when screen is off..browsed a lot.. used xda app a lot..did random stuff..played Death Rally for more than half hour..listened to tuneIn radio for couple of hrs.. used flipboard every so often..

Quite happy that I can get 10hrs screen for my use..

Love the rasbean ROM.. I highly recommend it for others to try it cos honestly its snappy and I never faced any freezes or reboots ..its clean fast and slick..and thanks to Franco for the kernel.. I Don know what else I can say about r9, the snapshots speak for themself :)
[Nexus 7 Original Development] osm0sis:
You'll get even better time if you uninstall Death Rally. Fun game but even when you turn off the push notifications from the app info it still wakes up to call home fairly regularly.
[Nexus 7 Original Development] mazubo:
so funny dude! That there made my Tuesday! They try so hard.....
[Nexus 7 Original Development] :
Using r9 on Aokp III and smooth sailing! Wish you had or did a kernel for D2spr. I miss the hell outa your kernel Franco!! If you ever do decide to build for D2spr ill flash boot images immediately and report back just lemme know..[Wishful thinking]

:sly::):beer::what::D Tks for another great kernel Franco!!

Sent from my Aokp'd Grouper using Franco's r9
[Nexus 7 Original Development] ÜBER™:
I was under the impression that gs3 kernels were cross compatible just like the gnex

Sent From My Toro+ via White Tapatalk
[Nexus 7 Original Development] :
Tmo kernels work on sprint S3 but you get a rotation bug where screen flips when you go into portrait and also no lte.. Not sure what else, I ran a few Tmo kernels but the rotate bug I just couldn't bare it.:banghead:Also supposed to get lte and wanna know when its available...I wish it was like Gnex!! Spoiled I am!! Looking out for the next Nexiis though! My upgrade is 3/13..

Sent from my BlackBean IV D2spr using KT747 kernel
[Nexus 7 Original Development] stezo2k:
Loving this kernel, works nicely with Glazed Jellybean

Strangely v1 caused my Nexus to bootloop but this ones fine, it may be that I erased cache?

The battery life is awesome :D
[Nexus 7 Original Development] franciscofranco:
Here goes r12:

* Some merges from android-3.4

* Increase priority of Interactive governor Kernel thread. Now it will have more priority than user land (rom stuff) threads. This will increase interactivity by a very nice margin.

* Add an Interactive governor entry allowing users to change which frequency the device ramps to when a finger touch is detected. By default it ramps to 1000Mhz. Path is: /sys/devices/system/cpu/cpufreq/interactive/input_boost_freq. The app will be updated later to feature this entry

* Some other small patches - check github
[Nexus 7 Original Development] ÜBER™:
Gracias muchacho :D

Sent From My N7 via White Tapatalk
[Nexus 7 Original Development] ricardowec:
Francisco:

Don't know what your 'magic' is but I am amazed at the numbers I just saw: antuantu at more than 12000 and quadrant lose to 5000 all at 1.3000hz... congratulations... hope battery is not hurt.

Cheers

Sent using The Beast via Tapatalk 2
[Nexus 7 Original Development] poondog:
No problems here with anything supported by stock that I throw at it

But honestly I never had problems on any other kernel too including that one

Delete the social network apps :D

Should not really be a problem with the kernel, but having more free ram generally doesn't mean much anyway as android kills stuff it doednt need when its running low on space

No, not now at least
[Nexus 7 Original Development] franciscofranco:
Spent last couple of hours on Groupers kernel, heres the result:

r58:

* Youtube lag should be fixed

* Sync Hotplug driver changes with mako version

* Changed to Ondemand as I could reproduce the Youtube lag with interactive 100% of the times but not with Ondemand. Also tweaked Ondemands tunables a little bit for more responsiveness

* Cleaned some of the old GPU OC code

* Correct the min_rate of the G cluster, it was mistakenly 100MHz and it should be 102MHz - fixed

* Hardcode ROW IO scheduler tunables

* Some cleanups on the tegra drivers
[Nexus 7 Original Development] guidocioni:
I've tested the r58 and playing with song pop cause the device to became infinitely slow!! I had to reboot.. Never happened before

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Nexus 7 Original Development] franciscofranco:
Logs would be helpful... I've been throwing everything at my grouper and I found no such thing no matter what I tried.
[Nexus 7 Original Development] guidocioni:
Maybe interactive was the culprit.. I was getting lags also when nothing was opened.. I'll try on demand right now!

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Original Development] osm0sis:
Fransisco,

I wrote it up on the Group too, so please check that. :good:
[Nexus 7 Original Development] hs058052:
good :)

Now your application is more friendly. have the changelogs on the new version and the previous one.
[Nexus 7 Original Development] Trewyy:
I'm no developer, but these studders seem to be solved if you just changed the minimum frequency to 475MHz.

After all, 100MHz is literally the speed of a computer in the 1980s. Either that, or adjust your hot plug driver to leave 100MHz far more frequently.
[Nexus 7 Original Development] lollyjay:
475mentioned numerous times here, and all agree that it works.

Nexus 7 WiFi 32Gb | PA 3.15 25-Mar2013 | Nova Prime | Franco-Kernel r57

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Original Development] Trewyy:
Yea that's kind of the reason I pointed it out - I was just recommending to Franco he change the defaults, like many other people have.
[Nexus 7 Original Development] The Gingerbread Man:
I'm hoping for either a new CPU step around 350mhz or a media frequency lock at 475mhz if 350mhz is still too low and the system favours 102mhz.
[Nexus 7 Original Development] GedBlake:
r58 running liquid smooth on my N7... I've thrown everything I can at it... Temple Run 2 (which for me, is the acid test... previous r50's always fell at this first hurdle) - and then YouTube, MX player, BBC iPlayer Media Player, BBC iPlayer via Adobe Flash in the AOSP browser, ITV player, IMDB (watching movie trailers).

All running rock solid, without any discernible lag (indeed, the 'mineshaft' sections in Temple Run 2, feel less 'jerky' than with r48).

Switching from the default ON DEMAND setting to INTERACTIVE (using my current ROMs own SETTINGS>>PERFORMANCE>>PROCESSOR option)...

...and I find a bit of lag ('stuttering') creeping in... but only VERY occasionally... back on ON DEMAND and all is solid again.

So for me, and so far, r58 is 'a keeper' and is now my own personal 'user milestone', just as r48 has been of recent...

------

Just a question though... What are the putative benefits of INTERACTIVE over ON DEMAND?

I get a general sense that INTERACTIVE is preferable... has something to do with battery performance?

------

Anyway... great stuff, Franco... thanks, and all here who have helped to facilitate this kernel.

Rgrds,

Ged.
[Nexus 7 Original Development] osm0sis:
Yep. Interactive is generally better for battery since ondemand can be too aggressive and simple.
[Nexus 7 Original Development] ktkr:
Just for reference, on my nexus 7 faux123 kernel uses 370mhz and m-kernel uses 340mhz minimum and both work well.
[Nexus 7 Original Development] BurnRubber90:
Edit.. Stupid mistake.
[Nexus 7 Original Development] qualitymove13:
Am I right in thinking that the Hotplug control steps need to be swapped so second_level = 50 and third_level = 25? They are the other way around at install.
[Nexus 7 Original Development] franciscofranco:
Second level is 25, third is 50, thats correct.
[Nexus 7 Original Development] galaningenieros:
That does not seem logic, reading the explanation in fku, third is lowest level to offline all Cores. Maybe you should modify the text in your app.
[Nexus 7 Original Development] ÜBER™:
Its logical.. this is how it works as explained by franco.

Medium_load: 25, when the cpu load hits 25% it will online a core, dump the monitroing and when it reads another 25% (50% total load) then it onlines the next core in succession. Etc.

Low_load: 50 when the load goes back under 50% it will offline any onlined cores.
[Nexus 7 Original Development] SGWUser:
I first looked at the app and it looked to be like galaningenieros said, after that I read ÜBER™'s post and that seems more logical, and indeed the description the app gives is kinda weird then.
[Nexus 7 Original Development] ashik992:
best kernel in my opinion....

Loved those words while installing..

"Installing a virus

23%...

50%...

77%... There's no escape now, allyourbasearebelongtous!

100%

Had you freaked out hein?!"

Welcome.. !!!

And thank you so so so so much much for a great kernel like this...

====================================================================
[Nexus 7 Original Development] k29er:
I am very confused. One core is on all the time? So at 25% two cores are on and 50% three and 75% all are online but still not at 1300 MHz because its not at go-hispeed load yet nor target load?

And if it goes up a core at 50% and back down at 50% would that not make it switch between the two all the time?
[Nexus 7 Original Development] markeithst:
Someone may have already asked but what is the boot loader IMG for?