yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] osm0sis:
Very good recap. :)

NVidia had 2 implementations of their auto-hotplugging that we've tried, the one that comes in stock which Franco found inefficient, so he tried their more experimental CPUQuiet one which was better but possibly causing issues with some, and now he's trying _thalamus'. I think you're right about it not working well with the LP core, and when it tried that was causing the issues I've seen people mention other dev's were also having with _thalamus' auto-hotplugging, like SODs. So then, by the looks of it, to get around this and not have us idling at 400MHz Franco modded the 4 main cores to be able to scale all the way down to 100MHz. Pretty clever.

We could definitely use some more hard data on how it's working versus the previous implementations we've tried though. :good:
[Nexus 7 Original Development] xateeq:
Thanks, That explains a lot.
[Nexus 7 Original Development] The Gingerbread Man:
Thanks great explanation as always! I'm back to stock for the moment, purely for the sake of seeing what its like, I know Franco does awesome work. I did find while on stock kernel a 51mz slot, that's crazy low and lowest on Franco is 100mz so this 51mz slot must be the lp core I guess.

Edit

I just unset my set on boot for CPU settings and rebooted and selected the 51mz slot and it shows its selected in the menu where you choose the speed but not on the main page for frequency and voltages, 100mz remain there and 51mz is now unused. Guess I'll have to wipe Franco app data and uninstall it to get 51mz back

Edit 2

51mz working now :thumbup:
[Nexus 7 Original Development] spaceman860:
@Franco on r38 5 hours screen time 5 days since last charged still got 15% left :D

Sent from my Nexus 7
[Nexus 7 Original Development] ÜBER™:
Actually on stock.. anything under 400 is the LP core. ;)
[Nexus 7 Original Development] osm0sis:
Yeah we had 51MHz at the beginning but Franco took it out for some reason, felt it was too low or something. I was also always intrigued he went for the 100MHz steps rather than the stock frequency table.
[Nexus 7 Original Development] kapitanbasa:
i've tried most of the "bestseller" kernels...all of 'em seem to break my favorite game's graphics...NFS Most Wanted. But with franco r38...NFS is behaving uber fine.

the last time i tried francokernel was when he was still churning out kernels for my old optimus p500.

am now a returning fan. thanks for this.
[Nexus 7 Original Development] N@th_OC:
51Mhz was'nt stable. It was causing SOD and other problem.
[Nexus 7 Original Development] Metallice:
Neither of this things are true. For one, Franco's didn't decide to remove LP support. He switched to a hotplug driver that doesn't support the LP core because he had good results with it on the N4.

No evidence? And what evidence do you have? Physics shouldn't up for debate. I don't understand why it is. Leakage matters. The only "proper comparisons" are based on stressing the CPU to the point where the LP never comes into play. That's why battery benchmarks show little difference.

Are you going to try to argue that ARM's big.LITTLE is a gimmick too? Yeah.. because they probably don't know what they are doing. Dual A7s Quad A15s will soon become the standard... for a reason. I would say the default 475 max by nvidia is pretty weak and usleess, but an LP overclock helps emulate this big.LITTLE style.

Sent from my Nexus 7

---------- Post added at 11:19 PM ---------- Previous post was at 11:14 PM ----------

Thalamus doesnt support LP core. That wasn't the reason for any issues. Additionally, this is exactly what morfic did a while back. Thalamus doesn't support LP core, so he lowered the G mins to 102MHz. He ultimately decided to switch back to Tegra autohotplug though.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Wasn't aware of most of that. Thanks. :good:

Interesting to hear that morfic decided to try it awhile back, dropped it, and then franco still went for it. Either way, what I said about it being an experiment still stands, and people need to chill the **** out about it, regardless of knowledge level. ;)
[Nexus 7 Original Development] Metallice:
No clue why he decided to switch back. Probably something to do with SODs, but that was probably unrelated considering Franco hasn't had that issue (I think)

Sent from my Nexus 7
[Nexus 7 Original Development] drose6102:
Does this look normal for Wi-Fi of during sleep or is maps causing it to turn on all the time. Stock r38
[Nexus 7 Original Development] ÜBER™:
Do you even use maps? If not.. GET RID OF IT. Its pointless. And a battery hog.
[Nexus 7 Original Development] drose6102:
I rarely use it. I feel like an idiot now but thank you, I froze it with titanium. I should have done that from the start
[Nexus 7 Original Development] ronedogg:
I love this kernel. I tested out a bunch and this has the best mixture of battery life and performance in my opinion.

I am not sure if this is allowed or frowned upon but here goes.

What are the chances of this kernel having otg with charging capabilities implemented? I tested a kernel for cm10 that had this feature and it was nice. But I ended up back on Franco for obvious reasons.

Thanks for your time and hard work.

Sent from my Toaster using a fork
[Nexus 7 Original Development] JDCFH:
Getting sod still on R38 using interactive governor... Not as bad as it was on R37 but just still not 100%
[Nexus 7 Original Development] dotnetnightmare:
Please stop bullying. Second account or not does not open the door for you to discriminate against this member. Francos "experiment" is on a "stable kernel" and is advertised as such to users who paid for his "Franco Kernel Updater". I can and will ask any question I have regarding this experiment in my stable kernel.
[Nexus 7 Original Development] joaquinf:
Dear dotnetnightmare:

Osm0sis is one of the most (if not the most) person willing to help anyone looking for help. Even those who don't want to read a thing and expect to be spoon-fed. So don't try to be smart with him.

There is no bulliying nor discrimination in here, stop playing the victim. Man up

Franco can do anything he wants because he can. Is his kernel, his time, and his work that he shares with us for fun. Experiment or not he can name it the way he wants.

Nobody is advertising anything here. If you or anyone here bought the app is because we want to support francisco. This is not a product, service or any sort of membership that you pay for. This is open source and supporting doesn't give you any rights nor any responsibility from francisco with you.

You can ask any question, sure, just keep in mind that this is no support forum or costumer service line. We all are here because we enjoy learning new things and this is a hobby. We help because we want and anything you do to your phone is your responsibility.

Kind regards
[Nexus 7 Original Development] osm0sis:
Thanks Joaquin. I just want to add that in no way is a nightly considered stable. If you want stable then continue to wait for a milestone.
[Nexus 7 Original Development] sedohunta:
I got SoD too on r38 (albeit only once), so I am back to r31 (rock solid imo). To me r31 battery consumption also seems better than r38, but I have to admit I did not actually measure this.
[Nexus 7 Original Development] Sveke:
I know its old now but this was great!

Osmosis is very helpful even to us guys that know exactly what we're doing, like me.

I don't even know what to say about the thanking yourself from a second account. Da fuq? That's special sauce right there.
[Nexus 7 Original Development] formicae:
SOD this morning, only my second one since maybe r31. last_kmsg attached if you want to take a look, franco.
[Nexus 7 Original Development] ÜBER™:
If anybody cares these are the values I've decided to stay on. I didn't like the gnex magic variables. They kept my CPU up too long and I feel these ones work better. But just my opinion.

Sent from my Nexus 7
[Nexus 7 Original Development] 1pop23:
gonna try out your values. I feel with the magic the battery usage is a bit high. Ive been trying to find the perfect blend of battery and performace
[Nexus 7 Original Development] TheByteSmasher:
@Franco will row work on the N7? If so, any chance of it in r39?

Sent from my Nexus 4
[Nexus 7 Original Development] djdunn:
A big battery saver for those who see google maps using up cpu cycle, and waking their N7 up.

I found that disabling wifi and mobile network location seems to be the biggest cause of the battery usage for my google maps. I may be wrong but I believe this option attempt to determine location by using googles database of wifi networks they collected with their google camera streetview cars. The other option for the gps seems to turn on when something actually needs it and not background like the wifi and mobile networks seem to do.

Doing this lets me keep maps off my battery list without neutering google now and other aps that seem to want location access.

I might be wrong and google now might background some gps. But if it does its only a few second a day <20 seconds.
[Nexus 7 Original Development] dotnetnightmare:
Ass-U-Me

You can all revel in how smart u are. Who verified that the account similarly named with a "v2" was not his wifes account? Who took the time to go through all his posts in an effort to discredit him? This is my last post in the Franco kernel, best left for you high school children.
[Nexus 7 Original Development] osm0sis:
The moderator it was reported to did. Have a great day. ;)
[Nexus 7 Original Development] davisac:
Well bye.
[Nexus 7 Original Development] Death&co:
Hi all,

I flashed my first kernel a few days ago and while I was happy to see the insane performance difference in it, I couldn't jusitfy the crazy battery drain I got from it. I read around and saw that this was recommended for battery saving.

Reading the OP it stats "Instructions:

Download the boot image from the download link, reboot to the bootloader and enter this command: fastboot flash boot name_of_the_image.img"

I'm not sure if I quite follow this. Will I be able to install this kernel by downloading the zip file and just flashing it with TWRP?

I apologize in advance but I'm quite new to all of this.
[Nexus 7 Original Development] davisac:
Go ahead and do that. It's what I always do.
[Nexus 7 Original Development] ÜBER™:
Just flashing a kernel doesn't make everything all peachy. Its up to you to configure it afterwards. Look back a page I have the gov parameters that I felt were best for me. Give them a try they are a little more battery friendly and just as smooth.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] Death&co:
Cool thanks guys, have it installed nicely now. Trying out your settings ÜBER, thank you! Should I make sure to check off just the governoror cpu settings as well for when it boots up?
[Nexus 7 Original Development] ÜBER™:
No mark those to set at boot. Otherwise you'll have to redo it every time you reboot.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] davisac:
Thanks for the settings UBER. Been running the magic settings so I'll give these a try. Trying out some undervolting at the same time so between the two should have good battery life. :good:
[Nexus 7 Original Development] ÜBER™:
I have -100mv on every step. :)

Sent from my Galaxy Nexus
[Nexus 7 Original Development] timbck2:
Bye.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] davisac:
That's what I tried too. I just ran Stability Test's scaling test for 50 runs @ ~60 min. Thanks again.
[Nexus 7 Original Development] TheByteSmasher:
So, does anyone know if row scheduler will work on N7? And if Franco has mentioned he'll implement it?

Sent from my Nexus 7
[Nexus 7 Original Development] ÜBER™:
Why? :)

Sent from my Galaxy Nexus
[Nexus 7 Original Development] osm0sis:
I've found that Stability Test to be pretty useless for voltage testing. On my GN I had them set to known borderline voltages that I could reproduce a hang and reboot with after about 15min normal usage, and Stability Test didn't trigger it. Too bad, since it would be nice to have a way to force an issue when your voltages are borderline. :(
[Nexus 7 Original Development] davisac:
OK well I guess I'll just have to give it some real world usage.

I'm out of thanks for today though sorry. Didn't realize there was a limit on them.
[Nexus 7 Original Development] TheByteSmasher:
Because it's great on the N4 and I want to try it on the N7

Sent from my Nexus 7
[Nexus 7 Original Development] ÜBER™:
How do you know? :) Do you even know what it does? :p

Sent from my Galaxy Nexus
[Nexus 7 Original Development] nodstuff:
I did.

I did.

Goodbye.

Proof:

After I posted here telling people about what he was doing, I reported him to the mods when I became sure enough that something fishy was up, I also mailed the user in question and confronted him about it. He mailed me with some bullsh*t story that he made that account for his friend because his friend couldn't make one and for some reason they were thanking all of his posts, good friend. :rolleyes:

The mods obviously thought it was worthy of action because they deleted the fake account.

So now you can f*ck right off with your stupid posts and insults and stay away from this thread.
[Nexus 7 Original Development] TheByteSmasher:
Yes, it prioritizes reads over writes... playfulness aside, I don't wanna clog with nonsense. I just want to know if it can work with the N7 (I think it can) and if Franco will implement it like he did the N4. ;)

Sent from my Nexus 7
[Nexus 7 Original Development] ÜBER™:
Just pulling your leg, like when people ask if this kernel as ZRAM :D.
[Nexus 7 Original Development] osm0sis:
We've also had ROW on the GN for a few builds now, and r1 of Franco's new N10 kernel even has ROW in it, so I think it's a safe bet that the N7 will be getting it in the next build as well. ;)
[Nexus 7 Original Development] The Gingerbread Man:
I reckon Franco kernel for the galaxy nexus is smoother than the n7 version but then there has been 323 more builds and is ultra optimised :D
[Nexus 7 Original Development] osm0sis:
Yeah I agree. Those latest interactive patches from Google's Todd Poyner made a world of difference on my GN too. Even fixed the JB4.2.x lock screen lag for me and made it more responsive with swiping to the camera widget. Not nearly the same effect on the N7 but my guess is the governor tunables are the key to that.
[Nexus 7 Original Development] drose6102:
R38 is running great. No issues only happiness. Thanks again Uber for suggesting to remove Google maps. No more wake lock issues and I rarely used it anyway. And as always thank you Franco for your hard work.
[Nexus 7 Original Development] 1pop23:
I've been running this kernel

For awhile and love it. I'm planning on switching top sgt7 ROM and want to know if they are compatible together

Edit

Never mind just saw the front page
[Nexus 7 Original Development] joaquinf:
Woohoo! This is music to my ears! Literally. Bluetooth issues are f-ing fixed on android 4.2.2. I can't wait

"Comment 443 by mailto:ma...@google.com, Today (9 hours ago)

We have fixed the a2dp streaming stutter problem on N7. The next release should have the fix.

Sorry about the problem."

Source: http://code.google.com/p/android/issues/detail?id=39633
[Nexus 7 Original Development] poondog:
woooooohoooooooooooooooooo!!!!!!!!!!!!!!

I don't even use bluetooth lol but its good to see Goog fixing their problems :)
[Nexus 7 Original Development] Ahres:
Hey guys, i tested most of kernels for n7 out there and this is one of the best. But im missing one thing... I would like have native otg hotplug mode. If you use stickmount its battery drain and its really comfy if you just plug in and play.if i connect usb flash it looks like i conected device to pc.any tip for me? I know other kernels got this hotplug mode but i eant stay with this... I do like this Franco smoothness without oc.
[Nexus 7 Original Development] geroxx:
delete please
[Nexus 7 Original Development] 1pop23:
Indeed! One of the smoothest out there with great battery and no OC! In my opinion a little bit of tweaking is required to get all the buttery smoothness but once that's done this is a great kernel!

Have been using your settings now for a few days and the performance is much better then magic! Thank you for sharing those!

Would you recommend running with the -100mv under volt? I've been iffy on playing with those and if it doesn't do much to help battery then why mess with it?
[Nexus 7 Original Development] mnp:
What do these values actually do? I'm assuming how sensitive the CPU activity triggers are and how sensitive to change the interactive govnor is?
[Nexus 7 Original Development] ROFLkopter:
r38 and PA2.99B9.9 are running brilliantly for me! Using your settings, Uber, with -100mV(?) UV. No SOD's or anything. Games running smooth, brill battery life and no lag. I love this kernel! Who needs overclocking when your N7 runs great without it :D

Sent from my Samsung Galaxy Ace GT-S5830
[Nexus 7 Original Development] osm0sis:
Check out yellowdie's summary post from when we were working out the magic values for the GN, it explains them all pretty well: http://xdaforums.com/showpost.php?p=33161912. We still go on for a number of pages after that too, all good reading.

We should all work together to recreate that process for the N7 at some point... How about now? :p

UBER's current numbers (20k/70/30k/18k) would be a great starting point. A couple numbers to tweak off the bat would be timer_rate since Franco said it's best when that matches the max CPU freq transition latency of ~30000 or half of that at 15000, and then he said it would work better in theory if one of the others is a multiple of that, but I'll have to go back and read it again myself to see which one. :)

Edit: It's above_hispeed_delay that should be a multiple. In the end Franco made them all multiples for the finalized magic values, so we can experiment with both ways and see how it goes. :good:

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

So based on UBER's numbers let's all try 30k/70/30k/15k. Technically 30000 would be a pretty low above_hispeed_delay, resulting in more battery use, but it's sort of balanced by the higher load of 70% and lower min_sample_time so we'll leave it for now.

Bumping the hispeed_freq to 900MHz like in UBER's settings is also good, but I think we should put it back to the default 700MHz to see if we can make it smooth without that. We should also put GPU back to the default 416MHz and IO Scheduler to deadline for this reason while we test.

Edit: Here are the tunables yellowdie worked out to go with the GN Power Modes for when Franco figures out a good way to add Governor Tunables to them; I figure they could also be good jumping off points:

a_h_d	g_h_l	m_s_t	t_r

Beastly Battery	90	75	30	15
Best Balance	60	65	45	15
Slightly Speedy	45	50	60	15
Powerful Performance	45	50	90	15

(Everything but go_hispeed_load would be multiplied by 1000 to get the correct number of milliseconds. So 60/65/45/15 would really be 60000/65/45000/15000. You'll also note that Best Balance is the same as the GN "Magic" Tunables.)

So please report back how that works and try to adjust them according to those rules (especially yellowdie's notes on what higher/lower values of each do) and see if you can make it any better. :)
[Nexus 7 Original Development] g.lamprou:
Is Franco kernel works on nexus 7 3g ?
[Nexus 7 Original Development] davisac:
If you search the thread other people have reported it as working.
[Nexus 7 Original Development] Sayan1987:
Osmosis, can i use your great knowledge and patience to ask you a thing? (i know i'm in the wrong thread, sorry)

I switched from franco kernel to leankernel on my galaxy nexus, and i wanted to replicate your gn magic setting for governor control, but looking at what you say in your signature, using trickster app i don't know where to apply your 60000 / 65 / 45000 / 15000; 729 MHz hsf

Can you tell me where precisely input every single value? I mean, for example, when you say 65 you mean go hispeed load?15000 stands for?

Feel free to pm me if you dont wanna go offtopic..

Greatly waiting for your help, thanks in advance.
[Nexus 7 Original Development] osm0sis:
a_h_d	g_h_l	m_s_t	t_r

Best Balance	60	65	45	15

It's really easy to figure out if you look at your possibilities and compare them to the acronyms. g_h_l is go_hispeed_load like you guessed, etc. :good:

Also all explained very clearly in that post of yellowdie's that I linked. ;)
[Nexus 7 Original Development] g.lamprou:
Ok i have see it thanx !
[Nexus 7 Original Development] Sayan1987:
OK but you gave only 4 values, you didn't mention about:

-boostpulse duration

-hispeed freq

-target loads

-timer slack

What do you suggest?
[Nexus 7 Original Development] osm0sis:
Leave them as they are. We only tweaked the 4 mentioned since they're the ones Franco has in f.Ku, and if they're tweaked correctly you don't need to mess with the frequencies or anything else. The current performance on the GN with the magic values is proof of that.

As for hispeed_freq in my settings..

Take a wild guess. :rolleyes:

If you have any more questions take them to the GN thread but please try to logically reason through it first. You've already derailed things here so that my attempt to kick off tunables testing will be a page old. :(
[Nexus 7 Original Development] irminsul:
I will help to test tunables. Maybe it's handy to simultaneously test them, like all values are used by all, after X time evaluate and choose the values that can be adjusted, test again, etc.
[Nexus 7 Original Development] osm0sis:
Awesome. The only trick will be gauging battery life. I can definitely say 30k/70/30k/15k feels pretty smooth, I'll have to do some more testing to see how it compares to 60k/65/45k/15k (magic values) though. UBER was saying he found the magic values to be smooth but used more battery, so what we want is something roughly as smooth but a little better tuned for battery savings. Maybe he can tell us how the tweaked values stack up? :)
[Nexus 7 Original Development] ÜBER™:
Testing them now. I did have a slight issue yesterday I've been meaning to mention. I was watching Hulu+, it was playing smooth for like 3 mins and then would hiccup constantly. Making the video unwatchable. I tried it on my gnex and it was perfectly fine. I even upped the low frequency to 400 and it was still stuttering? Anybody else have this issue?

Sent from my Nexus 7
[Nexus 7 Original Development] poondog:
Does hulu have its own player or does it use the stock android gallery player? I have been watching videos on mine, using your values but have the boost thing set to 700MHz. Videos play at 700MHz and no stutters at all.
[Nexus 7 Original Development] ÜBER™:
Uh own player its its own app. :) its also a streaming player.

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Sounds like an IO Scheduler thing. You still using bfq? I'd definitely try it with deadline instead since franco patched it to prefer reads over writes. It will also be interesting to see if the row scheduler helps once franco adds it.

Remember for testing we're setting GPU and hispeed_freq (and I suppose scheduler too) back to stock to hopefully make things more even. :)
[Nexus 7 Original Development] ÜBER™:
There's only noop and deadline and I tried it with both. I'm not sure if its the app or the kernel..

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Whoops. Was looking at the wrong section of your settings page. Try clearing cache on that app?
[Nexus 7 Original Development] ÜBER™:
Have, wiped data and reinstalled. Same issue.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] osm0sis:
Tried it with stock kernel?
[Nexus 7 Original Development] ÜBER™:
I haven't, have to redownload the flash able for it. But I am planning on it.

Sent from my Nexus 7
[Nexus 7 Original Development] Mr. Steve:
I had this exact same problem after I changed the wifi policy. I ended up just changing it back to the default "always" option.
[Nexus 7 Original Development] Sultan.Alkhuzaie:
I am now on AOKP PUB with Franco kernel

What is the best CPU settings for this kernel