yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] franciscofranco:
Its made that the second core will come online very easily, and when the load drops a little it will hotplug it right away. So that you get fast extra smoothness but battery savings by offlining it quickly. Something like that.
[Nexus 7 Original Development] RootTheMachine:
Trickstermod and the kernel app are both showing the first core stuck at 1300 MHz. CPU load is very low, but it stays at full speed. It occasionally drops down, but immediately goes back to full. Changing settings or rebooting doesn't help it.
[Nexus 7 Original Development] osm0sis:
Franco, buddy.. you released r58's zip without the safer updater-script I emailed you. :(

Please when you've got a minute get back to me. :good:

That's just because you're in a graphic System Monitor and ondemand is very touchy. It's not actually at 1300 MHz the whole time, but I think maybe it is a bit too touchy the way Franco's got it tweaked right now.. If you go to the f.Ku Device Monitor you'll still see it's constantly shooting from 102 MHz to 1300 MHz, back and forth on that one core. No wonder Franco can't reproduce the lag on it. ;)
[Nexus 7 Original Development] franciscofranco:
Don't worry about that. While you're watching the live CPU freq the app is reading continuously from a file using a BufferedReader which is like an extra thread doing the job. That burns a few CPU cycles and shows you a faux frequency on a faux load. Something like that. Don't stress about it.
[Nexus 7 Original Development] franciscofranco:
I'll include them in the next one, I had already everything prepared before you sent me the files!
[Nexus 7 Original Development] bagl0312:
I found that with R58, when listening to a streaming radio with tunein, the sound stops periodically for rebuffering.

It looks like there is a too aggressive power saving mode for wifi when the screen is off.

I tried also r47 and this rebuffering does not happen.

Could somebody check?

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Original Development] guidocioni:
Hi, I know this is a dumb question but is normal that 2 of the cores are always offline no matter what cpu load I get? What is the parameters for choosing the wake behavior for cores?

Ok I got some strange settings in the app.. Someone could address me to the post explaining how to set the hotplug controls? I can't find that.

Inviato dal mio Nexus 7 con Tapatalk 2

---------- Post added at 10:47 AM ---------- Previous post was at 10:38 AM ----------

Have you tried switching on wifi pm fast? I think that's for improving wifi on screen off..

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Original Development] The Gingerbread Man:
Stick it your microwave at home and reheat for a tasty snack later ;)

Perhaps look into the WiFi sleep options under the advanced WiFi settings and switch modes, otherwise as someone else said try WiFi pm fast mode from within francos app

I suggest you clear all data for the Franco app and reboot. You don't really need to mess with the hot plug values Franco has pre configured it for us. Franco said he made it easy for cpu1 to turn on so it might that what ever your doing the load on the CPU is still too high to drop down to running on 1core.
[Nexus 7 Original Development] tibere86:
Enable WiFi PM Fast. It's disabled by default.
[Nexus 7 Original Development] poondog:
Wrong :P

Its the same as what's in the flash able zip, just simple img format for users to flash it with fast boot

Same present just wrapped differently
[Nexus 7 Original Development] bagl0312:
Enabling WiFi PM Fast the rebuffering is still present, but less frequently.

I am wondering why I don't have to play with these settings on r47, where tunein just works flawlessly with default settings (and WiFI PM Fast disabled).
[Nexus 7 Original Development] The Gingerbread Man:
Just fluke really, nothing to do with WiFi has changed to my knowledge. You could blame your router for slower internet speed or an increased bit rate from tunein using larger data packets or blame atmospheric conditions or turbulant weather and solar storms.

The other thing which could be causing the pausing is the same thing which is causing issues for YouTube, see if raising your min CPU speed to 475 and test for a while and report back in a bit.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] bagl0312:
Raising min CPU speed to 475 does not help, so this at least excludes that it is the same thing causing lags with youtube.

I am now trying extensively with r47, and no problems so far...
[Nexus 7 Original Development] poondog:
Try change your governor as afaik nothing changed with WiFi recently

Was it working with anything after r50 when Francisco changed the hotplugging?
[Nexus 7 Original Development] khaytsus:
What he asked was why two cores are always offline, not online. I have the same question, I just hadn't asked it. I've never seen core 2 and 3 (of 0-3) come online since installing this kernel.

I assume with hotplug they'll come online if the load is high enough, but I'm too a bit confused about the settings related to quad mode etc.
[Nexus 7 Original Development] bagl0312:
Tried also r57 and it has the same rebuffering problem (governor was interactive by default).

Same thing with r58 with ondemand governor (default)

So I believe all kernels after r50 have the same problem with streaming audio when screen is off.

If somebody else can try to listen to a streaming radio with TuneIn and check if he sees the same problem would be maybe useful

-----------------------------------------------------------------------

I forgot to say that I am on stock 4.2.2 ROM
[Nexus 7 Original Development] ectodroid:
Same happens to me with tune in radio, reverted back to r47. Works perfect again.
[Nexus 7 Original Development] GedBlake:
I've been listening to TuneIn for the past hour or so without problems... running r58.

r58 is the first of the the r50's in which I have had no problems...It just works!

Rgrds,

Ged.
[Nexus 7 Original Development] osm0sis:
Francisco, I just had a thought.. Would dyninteractive maybe do a better job ramping over here? Or are you considering that a failed experiment.
[Nexus 7 Original Development] franciscofranco:
Thanks for the feedback on the TuneIn weird rebuffering on screen on. I might be too aggressively choosing to enter deep_sleep when it shouldn't and if that is the case then its my fault. I will take a look.

I dunno, I never tried including that patch again on Grouper. I can try though.
[Nexus 7 Original Development] lollyjay:
I know you need to investigate the problems, but just reporting that all is working perfectly with my configuration. I'm happy. :D

Nexus 7 WiFi 32Gb | PA 3.15 13-Apr2013 | Nova Prime | Franco-Kernel r58

Nook Color | PA 2.99 | Nova Prime
[Nexus 7 Original Development] osm0sis:
Thanks! :)

Adding that lower step between 102 and 475 would also be a good low-effort thing to try and see if it resolves the problems on normal interactive. Maybe somewhere in the ballpark of 290 MHz first, since that's half way.
[Nexus 7 Original Development] spidertop:
Hi franco. Is it feasible to raise a little the USB charging current ?

Actual Ampere is not enough to keep in charge during GPS navigation in the car.

It goes down 1% each hour, approximately

Thanks a lot for your work :)

Alternative: set USB charging current in franco app :)

Inviato dal mio GT-N7100 con Tapatalk 2
[Nexus 7 Original Development] canofale:
No problems streaming TuneIn here. I'm running stock with r58. Tried using it with WiFi Optimization checked and unchecked, no difference. For the record I haven't had any of the problems expressed in the last 30 pages of this thread. No stuttering no buffering no glitching, nothing. I have preformed all the same tests and run all the same apps. Lucky maybe? I do keep things lean and clean, maybe that helps.
[Nexus 7 Original Development] osm0sis:
Hey fellas. Here's a bit of fun to play with until Francisco has time to try out those ideas/give us a new build to play with! ;)

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] -- Misc./Batch Tools, Flashable Zips, Scripts, etc. that I've created.

Still working on the second post but there's lots to read in the first until I get it done. :)

Check out the N7 BootUnlocker Script thread especially. I'm pretty proud of that.

There's a new version of the f.Ku Emergency Reset Zip up now too. :good:
[Nexus 7 Original Development] Jonnyredcorn:
I'm still running r47 as I have had zero issues especially with video playback that some of you guys have been experiencing with r50+. Have most of these issues been resolved? I have the paid Franco app but don't really know enough about modifying kernels to mess with any of it except picking governor's & I/O(I'm using Interactive & row).
[Nexus 7 Original Development] LOVE ME PLEASE:
Is there any on screen delay in v r58?...thanks!
[Nexus 7 Original Development] Mechanisms:
I still experience them on YouTube with Interactive governor and CPU min frequency at 200 MHz. I haven't tested it with Ondemand governor, according to Franco's changelog there shouldn't be any lag any with Ondemand.

For those, like me, who still want interactive and no YouTube lag just set the CPU min frequency to 457MHz; this has solved it for me (I have a Tasker profile that does this by detecting YouTube and when I exit the app the frequency is set back to 200 MHz. Great workaround for now...)
[Nexus 7 Original Development] Jonnyredcorn:
Any reason why you set your minimum frequency to 200mhz? Wouldn't that hurt your battery life? Also what /I/O scheduler are you using? Are you under-volted at all?

Sent from my Nexus 7
[Nexus 7 Original Development] Mechanisms:
Sorry not 200 MHz but 102 MHz, the default min frequency.

I am undervolted cause I noticed the tablet was a bit hot at times so I have been trying to undervolt and it seems to help. I think it's -75 mV.

The rest are default values...
[Nexus 7 Original Development] Gspin96:
Hmm.. did you try setting lower and lower voltages? (not less than 600mV anyway) . The uV interface should be still broken as far as i know, since (atleast on r57) i can set voltage to 625mV across all board without crashes, and franco didn't mention a fix for this r58's changelog. Undervolt isn't a main concern to me anyway as of now ;).
[Nexus 7 Original Development] osm0sis:
Yeah UV is still broken so that's placebo unfortunately. ;)

Screen on wait/lag is confirmed resolved in r5x. Guess it was _thalamus'hotplug driver all along.

Now we've just got this YouTube/video playback **** on to contend with.. Good news is Francisco pulled some crazy brilliant dev work over on the N4 last night and raised framerates on games by like 6 fps and sounds like incorporated dynamic interactive tunables into the hotplug driver? Soo can't wait until that gets ported over! :D
[Nexus 7 Original Development] leventccc:
I was using r47 for a long time with no problems and battery life is great. I'll be going on a trip and I need the best battery possible, even though I'm happy with the r47, if the r58 is better on the battery basis, I will switch. Can someone who used r47 and now using r58 tell his opinion?
[Nexus 7 Original Development] Luigiesin:
R58 working fine here with YouTube and such.... Nice!

Sent from my Nexus 7 \m/

ROM: PA 3.15

Kernel: Franco r58
[Nexus 7 Original Development] NinetoFive:
I finally stopped getting video lag on R57 by changing to ondemand so I'm hesitant to change what ain't broke.

yet, i like shiny new toys.

Is there any harm in going to R58 and changing the governor back to ondemand?
[Nexus 7 Original Development] timbck2:
That's a great workaround until Franco gets to the bottom of the issue (which I personally am not seeing, by the way). Tasker is a powerful app, and this is just the kind of thing it's good for.

Sent from my grouper or toro

---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------

I believe the charging amperage is a hardware thing, not something Franco can tweak in the kernel.

Sent from my grouper or toro
[Nexus 7 Original Development] Vision81:
I keep trying the new releases but r47 is still king imo.
[Nexus 7 Original Development] bassie1995:
He should be able to change the amps, it was done on the SGS and SGS III at least.
[Nexus 7 Original Development] osm0sis:
Oh cool. I didn't realize a Nexus 7 was the same as a Galaxy SIII. :rolleyes::p
[Nexus 7 Original Development] brainvision:
Hi boys..

Sorry if the question is been already asked.. I'm following regularly this thread and I read all the last 3 pages, but I don't understand if is it normal that after setting the 1000 MHz limit the System Monitor goes on showing 1300 peaks and after a while Franco app itself shows again 1300 MHz as option enabled.. :banghead:

I don't think this is the 'normal' behaviour, isn't it?

PAC 22.1.0 / r47

{ brvsn ~ PACman 22.1.0 on Nexus 7 ~ Tapatalk2 }
[Nexus 7 Original Development] ÜBER™:
Not the kernels fault. Roms fault. You'll need a powerhal fix.

Sent from my Nexus 4
[Nexus 7 Original Development] brainvision:
Actually it seems I find a partial solution.. When I installed the kernel I did't give root permission to AOKP Performance Control built-in application.. Now I tried to enable root permission for it, too, and now it seems that the peak stays to 1000, even if Franco app after a while shows 1300 into Voltages and Frequencies menu! Really strange, also System Monitor stays on 1000 limit!

BTW, could you please explain me what exactly is a powerhal fix? Never heard about that.. :(

Thank thou very much..

{ brvsn ~ PACman 22.1.0 on Nexus 7 ~ Tapatalk2 }
[Nexus 7 Original Development] brfsa:
I've been using R57, and now will try R58.

All I can tell that the battery usage is amazing! Absolutely happy with R57, only issues was the occasional total system lagging, but I know it's the interactive governor issue.
[Nexus 7 Original Development] poondog:
Powerhal fix is a patched powerhal (power.grouper.so I think) that makes the frequency that you set, stay. The stock powerhal in most ROMs automatically resets the frequencies to stock (102-1300) after a while

In imoseyons leankernel rootzwiki thread there are 3 available powerhals: 1.3 (stock) 1.5ghz (set to 1.5ghz but this kernel doesn't go that far) and no freq, that does not change frequency and keeps whatever you set. I use the nofreq one to set to 1.1ghz on some kernels

Alternatively you could use an init.d script to cap frequencies, I can post mine if you want
[Nexus 7 Original Development] brainvision:
Thanks mate, I'll go soon to find the third powerhal you've stalled about to see if it solves the situation. If I have problem I'll ask for your script, it you please..

Last question.. Using the powerhal, then I'll be able to set whatever frequency I prefer, I presume.. Am I right?

Again, thanks a lot..

{ brvsn ~ PACman 22.1.0 on Nexus 7 ~ Tapatalk2 }
[Nexus 7 Original Development] Metallice:
They have the same hardware, drivers, and everything!

Seriously.

Buy actually seriously, there are ways to limit the current in the battery drivers, but no way yo raise it as farm as I can tell. Even forcing the USB cable to recognize as AC doesn't work.
[Nexus 7 Original Development] lordlad:
just encountered another 'super slowdown' on r58...touch inputs were barely responding, screen transitions took ages.....took me quite a while to go to franco's app and take a look at the system monitor and found that only one cpu is online and it is used 100% and 'stucked at the lowest frequency of 102MHz....i didn't do any undervolting and whatnot...it seems that the hotplug governor is kinda 'screwed' during that instance as the other cores were not online.

Anybody can recommend value for the hotplug control? I tried to change the Minimum CPU frequency to 475MHz for now to resolve this (battery life be damn...i want my project butter!!!) and change the value of hotplug control to low 20, medium 40, high 75. Using ondemand governor as recommended for R58.
[Nexus 7 Original Development] osm0sis:
What were you doing when that happened and on what governor?
[Nexus 7 Original Development] lordlad:
On demand governor.....surfing on chrome beta
[Nexus 7 Original Development] ChaosChris:
Same here but it happend after switching to interactive after set to ondemand cores onlines normally

Gesendet von meinem Nexus 7 mit Tapatalk 2
[Nexus 7 Original Development] osm0sis:
Good to have more evidence it still happens with ondemand. :good:
[Nexus 7 Original Development] ÜBER™:
You got the hotplug controls backwards... High should be 90, but if you want to online all four cores easily use 80. Medium should be 20 (this is what determines if it onlines another core so having it at 40... its not going to online a core very quickly), and Low should be 40.
[Nexus 7 Original Development] khaytsus:
I feel like an idiot asking this, but I keep seeing numbers for the hotplug control high, med, low, and I don't see that anywhere. I see online all cores threshold, etc, which is default to 375 etc.

Is that because I'm using 47, or am I looking in the wrong place? Wrong tool?

Thanks!
[Nexus 7 Original Development] ÜBER™:
Becuase you're using 47, 47 doesnt have the new hotplug.
[Nexus 7 Original Development] khaytsus:
Thank you, I was thinking that must be what it was, but then again, I haven't messed with kernels with a zillion knobs and switches before. Nexus 7 16G is so laggy sometimes I felt I had to try something, and honestly it's much much faster with franco's kernel with standard settings, fsync off, but figured I'd play around with more.

58 still looks a little funny for some users, so I'm holding off. :)
[Nexus 7 Original Development] ÜBER™:
Im having no issues with it, running with Rascarlos Vanilla ROM. Even on 57 with ondemand i couldn't get Youtube to do its distortions anymore. Worse case scenario, you flash back to 47. :) Go for it.
[Nexus 7 Original Development] poondog:
Yes, and it will stick

+1 r58 is fine, just having a few video issues with interactive but using on demand was fine
[Nexus 7 Original Development] khaytsus:
True, zero effort to flash it, and since it's all contained in /boot it's simple to back up the original too, that was nice.

And I was worried about stability. The stock kernel has never crashed on me, ever, so that's great. But so far, 5.5 days on this kernel and no crashes. Good stuff. :)

FYI, I'm stock rooted, as stock has always seemed good enough, just the IO lag, and this seems to have taken care of that for the most part.

The great part is that I used to have to wait about 10-15 seconds after waking it up to do anything with the tablet, as it took forever to reconnect to wifi, do some syncs, stop IO lagging etc.. Now it's maybe 5 seconds, or less.

EDIT: Hmm, it's taking 3-4 seconds to wake when I push button/open screen. I'll keep an eye on it, maybe it was just busy after the reboot with media scanning etc and was slower than normal.

EDIT2: I think it was just busy, seems okay now so far.
[Nexus 7 Original Development] swedkg:
Same here, on interactive government.

After switching off and on the screen everything was back to normal.
[Nexus 7 Original Development] JDCFH:
I had it also while playing bubble worlds...

Se GBnt from my Nexus 7 using xda app-developers app
[Nexus 7 Original Development] TheLawIX:
Edit.
[Nexus 7 Original Development] JDCFH:
Something still isn't right with this kernel for these slowdowns to happen...

Got one just now while playing vector and temple run 2
[Nexus 7 Original Development] The Gingerbread Man:
Change from interactive to on demand, that might help with some cases. We know what that issue is causing it but waiting for Franco to get some time to fix it and spamming him won't help......
[Nexus 7 Original Development] JDCFH:
This is with the on demand governor :cyclops:
[Nexus 7 Original Development] The Gingerbread Man:
Use performance then

Sent from my Galaxy Nexus
[Nexus 7 Original Development] Gspin96:
Performance governor = 300% of the time is on max CPU frequency = the batytery lasts nothing.

Read http://xdaforums.com/showthread.php?t=1856256 it's the 5th governor.
[Nexus 7 Original Development] The Gingerbread Man:
Yes I know what it does thank you. I would have suggested Wheatley but its not on n7. The lag is caused by CPU dropping to low and there not being a step up it can take, the system feels 475mhz is too fast for some stuff so chooses 102mhz and its here where the problems start. The suggestions put forwords to Franco to help fix this thing is having a 350mhz step added or a frequency lock of 475mhz for media. The only other thing I can suggest to you guys is use 475 min speed and just deal with a little extra battery use or deal with a few lags.
[Nexus 7 Original Development] JDCFH:
Or swap kernels until this issue is ironed out :good:
[Nexus 7 Original Development] The Gingerbread Man:
And then come crawling back

Sent from my Galaxy Nexus
[Nexus 7 Original Development] JDCFH:
Of course, but for now this hiccup is making using my tablet impossible.
[Nexus 7 Original Development] CamoGeko:
Impossible is nothing.

... when you're running Franco kernel.

On the same note, I haven't got any lags you speak off playing Vector. Runs as smooth as butter for me with Ondemand governor. ;)
[Nexus 7 Original Development] JDCFH:
I had it 3 times playing vector now - and the massively processor taxing Bubble World:laugh:

With all default settings and ondemand.

Its random when it happens - like the tablet reaches a state where its not fully under load so starts to clock down etc etc but when the load increases it's struggling to get back up to speed again??
[Nexus 7 Original Development] The Gingerbread Man:
Its really easy to fix as a work around if your really that bothered about your gaming experience. Just raise min CPU speed to 475mhz. Its when the system goes under this speed **** goes a little pear shaped. I know its not ideal, its not perfect but everything will work normally including all governors (interactive esp) so just do that as a work around for now if you want to stay using this kernel. The fix is slow as Franco I know is stretched for time and n4 is his main priority and maintains 4 devices.
[Nexus 7 Original Development] osm0sis:
I think 290MHz would be good to try before 350MHz as a potential fix. It's half-way between 102 and 475 (the closer to 102 it is, the more likely it'll be to get used), and it might not cause the stuttering like on other kernels since it'll be on a G core and not the LP.
[Nexus 7 Original Development] matus201:
Hey guys, I was just wondering. Does the Franco's kernel write anything into the system that is not reverted by restoring kernel backup (via Franco's app)?

I used your kernel, but had bad youtube problems, and until that is fixed I decided to go back to stock kernel. Do I have to flash the whole system? Or is the ramdisk restored to original one by restoring kernel backup?

Thanks! :)
[Nexus 7 Original Development] slyd0997:
Change from interactive to ondemand to fix YouTube issues until Francisco has time to fix. You tube works fine with on demand.
[Nexus 7 Original Development] osm0sis:
Doesn't fix it. Reduces the severity. It's written on this page and the last of the thread. Raise min to 475 if you really want to "fix" (work around) it.
[Nexus 7 Original Development] matus201:
thanks [MENTION=4357039]slyd0997[/MENTION] for the suggestion, I have tried it; YouTube still had minor stutterings. That being said, I am still looking for answer to my original question..
[Nexus 7 Original Development] osm0sis:
No there is nothing written to system. The only think f.K ever writes is a patched PowerHAL but we don't have that on the N7 (yet). You will want to flash stock kernel to restore the stock ramdisk if you're switching to a kernel that doesn't include their own, however.
[Nexus 7 Original Development] matus201:
thanks osm0sis! that's good news, franco's app is then enough of a backup to go back to stock!