yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Metallice:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

For one thing current readings are broken in MKernel if that's what youre using. Like completely broken. Need to fix it.

Second, how can you monitor current draw during deep sleep using an app? That just seems impossible to do without having the CPU active.

Edit: or maybe it is working... 475MHz at homescreen -600ish, 340MHz -300ish.

Not that these results are worth crap or mean anything anyway.

Edit2: I guess it can do deep sleep current. How does it do that without waking the CPU? No clue. Maybe calculating using before and after and time.

-6mA on mkernel with wifi on. Also it shouldn't change with LP/noLP because the cpus should be off/in low power states.

Sent from my Nexus 7
[Nexus 7 Original Development] TheByteSmasher:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Franco, I've had the same issue, but I can say with certainty that it doesn't occur on stock kernel.

Sent from my Nexus 7
[Nexus 7 Original Development] blipp:
First off, sorry for not getting a last_ksmg, but something happened that prevented it.

My N7 was at 16% battery and i was about to plug it in. I woke it up, then i guess right when it ticked down to 15%, it just lost the rest of its charge, went to 0% and shut off. I plugged it in, it booted up, then like a minute later the screen turned off and now all i see is, the best way i can describe it, is a static effect. I can see the backlight on, but it wont boot (at least if it is the screen isnt changing) and when i unplug it it goes black, probably since it has no charge.

Im not entirely sure this is a kernel issue, but i was on stock 4.2.1 and the only different thing i had was this kernel.

Again, sorry about no log, i know theres probably nothing to do without it.

Im going to see if i can flash back to complete stock and see if it gets fixed.
[Nexus 7 Original Development] osm0sis:
That's just a dead battery. JB4.2.x brought issues with charging the N7 from dead. That "static" effect is what's known as a "pixel party" ;)

Here's the related fix for charging it if you haven't gotten that far yet: http://www.droid-life.com/2012/12/27/fix-nexus-7-refusing-to-charge-try-this-trick/
[Nexus 7 Original Development] blipp:
I knew it had problems when it discharged completely, the thing that just worried me was the instant jump from working fine with 16% battery to a dead battery. I never let it get that low, i usually charge at around 20%, sometimes sooner than that.

Im trying that trick, but the bootloader screen isnt even showing up. I had it plugged in to my computer waiting for the factory image to download, holding down the power button now and then and it just booted up, but since it wasnt getting enough power it just shut off again and wont show anything on the screen again. :/

Ill try and see if i can get it to boot again, thanks. Sorry for the off topic then.

Edit: ok, finally got into the bootloader and did the trick and now have the charging screen. Never letting it drop below 20% again, that's for sure! :) back to kernel stuff!
[Nexus 7 Original Development] drose6102:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I had the same thing happen to me a long time ago before the figured out a fix. I freaked out and thought having fsync off and it dying corrupted something and I flashed the factory image. Wiped the internal memory by accident too, I was not a happy camper. Learned my lesson, well some what, I usually charge it at 10% and leave fsync on. Good to hear you faired better :)
[Nexus 7 Original Development] RootTheMachine:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Man, this latest build is fast. Like night and day compared to r39.
[Nexus 7 Original Development] bjcrj:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

What he said:thumbup:

Big thanks to everyone for testing all the variables and to Franco for listening. Great community and great dev makes for a great kernel!
[Nexus 7 Original Development] djdunn:
Depends really when the write process gets interrupted. If it gets interupted before it gets passed to the ext4's journal when the system comes back online its just not there cause it never make the transition from ram to flash memory. If it made it to ext4's journal correctly fsck can be run to replay the journal and fix any missing/corrupt files that are in the journal, remember the journal is not a backup and cannot recover the entire partition. But fsck might be able to repair the files still but it will move them to /.lost-and-found on the root of the filesystem.

Loosing recently changed settings sounds normal for this sort of thing. It really depends on what step of the write process and what kind of lockup or kernel panic occurs to say exactly how a file breaks. But you run the same risk with fsync on too and would be possible to say if fsync would have been able to prevent the damage as fsync is only a workaround, i dont wanc to say fix because it works as intended, but its only a work around for only 1 step of a multiple step process
[Nexus 7 Original Development] Wynnded:
Geezus, no wonder I'm not a dev, that really made my head spin...:eek:
[Nexus 7 Original Development] djdunn:
I cant tell much, mkernel does sleep eventually at -6mAh same as franco but it idles higher with screen on by -60mAh at 330 compared to francos at -260ish

Mkernel definitly goes to deep sleep without a magnet, francos seems to not. But imo with the data im seeing so far francos is better on the battery life, but mkernels overclocked too

But even so it seems to be almost just as good perhaps.

Its very difficult to make a direct comparison.

So my official results are unconclusive comparing the LP core to downclocking like franco does now.

Does anybody know the last franco that used the lp core r31?
[Nexus 7 Original Development] SupWiz17:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

How do you get the device to go to deep sleep with a magnet?
[Nexus 7 Original Development] djdunn:
The covers that do auto sleep wake function use a magnet. If you hold pretty much any magnet by the bottom left corner it puts it to deep sleep if you take it away it wakes up
[Nexus 7 Original Development] ÜBER™:
LOL NO.

Deep sleep is a state of the processor.. which it is inherently "off" or "in deep sleep"

NOT Just when the screen goes off does it go into "deep sleep"

okay..

/end of rant :)
[Nexus 7 Original Development] djdunn:
I realize that, perhaps im not being that clear or need to read about it more, the android api is new and unfamiliar to me

I have noticed it goes deep sleep with the magnet switch but not the power button with francos kernels, i see it with differences in power draw and the timer on cpu spy
[Nexus 7 Original Development] sjknight413:
Bumping this, tried flashing r40 today and the same thing happened, can't see all this speed many users are reporting.
[Nexus 7 Original Development] exzacklyright:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I still have lag. Recent apps... always has lag for me!

Sent from my Nexus 7
[Nexus 7 Original Development] neo-X:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Are you running stock Franco settings? Tried clearing app data and cache and rebooting?

MiNCO Galaxy Nexus
[Nexus 7 Original Development] sjknight413:
Yep running stock and I have tried wiping the dalvik cache after wiping but to no avail.
[Nexus 7 Original Development] neo-X:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Not dalvik, the actual app data...either in the apps menu or in settings>apps>Franco>clear data

MiNCO Galaxy Nexus
[Nexus 7 Original Development] sjknight413:
Oh I don't use the app, like I said I just leave all the settings stock.
[Nexus 7 Original Development] neo-X:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Tried another ROM? It could be CM.

MiNCO Galaxy Nexus
[Nexus 7 Original Development] sjknight413:
Yeah I have thought about that possibility but it doesn't seem to be happening to anybody else.

And to be honest I wouldn't know what rom to move to, there are way to many to decide and I like cm's nightly updates and their faithfulness to stock.

Oh well if it can't be fixed then no worries, thanks for the help anyways! :)
[Nexus 7 Original Development] neo-X:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Try MiNCO!

Also, I've been hearing about this trim problems etc...could it be that? Nothing to lose I guess. Try lag fix (fstrim) by grilled monkey and see how you go

MiNCO Galaxy Nexus
[Nexus 7 Original Development] jsn:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I had the same sluggish performance until I tried 'Forever Gone' from the market.

It worked like magic! It also had some positive effects on my Galaxy Nexus, just not as huge as on my N7.

I never expected it to make such big difference, but it did!
[Nexus 7 Original Development] fozzie:
That won't do anything anymore, as Franco's added it to the kernel i.e. /cache & /data are mounted with the 'discard' option.
[Nexus 7 Original Development] k29er:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Getting more battery drain with r40. Full charge with one hour of streaming video took battery to 81%. That would be 5 hours to dead. R38 and high-speed at 900 was smooth and would still be above 90% battery for the same stream time.
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I would check gsam battery monitor.

Something isn't right. My battery is steller on 40

Sent from my Galaxy Nexus
[Nexus 7 Original Development] osm0sis:
Nah I think that just keeps it from getting worse, fstrim and/or forever gone are still needed to clear out the crap that's already been left behind.
[Nexus 7 Original Development] joaquinf:
Did you flashed r40 already?? how does it feels to you?

OT/ Are you still facing the issue you mentioned about the same data to be cleared is reported on fstrim after doing the trim? i do, and i don't feel any difference at all after running the app.
[Nexus 7 Original Development] osm0sis:
Feels okay. A little snappier. Not as dramatic as everyone hyped it up to be. :p

Yeah fstrim reports the same, their instructions kind of say that's normal though. But now that Franco has -discard in the mount options you should only need to run fstrim and/or Forever Gone once just to clear the extra trim garbage from the flash memory. Then you can uninstall both and forget it was ever a problem.
[Nexus 7 Original Development] joaquinf:
LOL for me it's definitely an improvement over any of the previous versions (i dare to say even 4.1.x kernels) and the

majority

of the lag is gone. In most of the situations that lags or stuttering were present now it runs >70% smoother and gaming experience has been vastly improved. I do agree that there are still some random slowdowns and hiccups but that's the fun part, if there wasn't room for improvement it would be boring, and hopefuly 4.2.2 will bring some performance improvements too. In the meantime we can still playing around with the tunetables and see if we can come up with something better

Thanks for the fstrim info :)
[Nexus 7 Original Development] puffel86:
Can i run fstrim on all partitions? when i open the app there are 3 partitions to choose from./system/data/cache...so can i run it in all partitions or maybe is that bad for the system partition?
[Nexus 7 Original Development] osm0sis:
They say don't run it on system unless you know what you're doing, which is wise because system is read only so generally hasn't gotten many writes, even if you are running root and mucking about. So no.
[Nexus 7 Original Development] kingoanklebreakn:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I don't know exactly what I lost but it would corrupt something in the data partition to the point where the only thing that would fix it is a wipe. After that, I just started keeping it on.
[Nexus 7 Original Development] Sveke:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Thanks.
[Nexus 7 Original Development] JDCFH:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Can I flash this over trinity kernel?

Or do I need do something else first?
[Nexus 7 Original Development] bjcrj:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

You can flash over.
[Nexus 7 Original Development] franciscofranco:
I can still make it better with some or my latest improvements on Mako's hotplug driver :)
[Nexus 7 Original Development] Mutalisk:
AW: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Aaand the runparts for init.d and the patched powerhal :)

Please?

Great kernel, since the last release best battery life I ever had! :thumbup:
[Nexus 7 Original Development] franciscofranco:
Patched powerhal for what? Stock powerHAL for this device works fine out of the box.
[Nexus 7 Original Development] joaquinf:
That sounds great :) i've been trying (not very thoroughly though) a couple of different tuneables combos but i think that our 15/96/1/45/15 is currently the one that feels smoother, almost every other combo immediately unleash the ui lag and stuttering :(
[Nexus 7 Original Development] osm0sis:
For people who want to underclock the max and not have it be reset when the screen turns off, same idea as the GN one. :)

---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------

I'm still wondering if going back to the exact values for the stock steps would help.. like 102, 340, 760, etc.

https://www.dropbox.com/s/vj6irk7w24iu0bq/2013-01-11 20.37.53.png
[Nexus 7 Original Development] ÜBER™:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I too would like to see stock freq steps. If for no other reason that they look cooler ;)
[Nexus 7 Original Development] joaquinf:
This is worth a try IMO

Francisco, what are your thoughts on this?
[Nexus 7 Original Development] osm0sis:
target_loads would definitely be a welcome addition to the Governor Control in f.Ku. Not so sure it tangibly helped anything during our testing though. But hey, if franco adds it to f.Ku that'll make it easier for us to mess around with it and do further testing. :D
[Nexus 7 Original Development] joaquinf:
I agree with you :) However, i still don't know if lowering that value will affect negatively due to the new patches, that's why i asked to Francisco what does he think about it
[Nexus 7 Original Development] djdunn:
I agree and think it might be a good idea, these processors are designed for performance and efficiency. with as much money as they spent to develop the tegra 3, id hope they didnt pull those stepping frequencies from that blackhole between their balls and tailbone.

Im still unsure about the lp core also especially after using mkernel for a bit. I know they overclock a lot and those power draw numbers are very close considering.

Then again stock kernel though not horrible seems is definitly not as good. So taking that into account i dont know about any of the above. Maybe we could sweet talk franco into reverting the hotplug and frequency stepping tables in a special test release in order to get a good comparison of the lp core.

Then again it might be less apples and oranges and more like comparing florida and california oranges.
[Nexus 7 Original Development] qsec:
Sv: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Is it just me or is scrolling in Tapatalk blurring the text on r40?

Tapatalked.
[Nexus 7 Original Development] 1pop23:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

That would be a tapatalk problem
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
Yea the Tapatalk app has horrible scrolling. I always have to make sure not to use it when testing out a kernel or performance setting, as it is ****ty no matter what I try and is really depressing.
[Nexus 7 Original Development] franciscofranco:
Can anyone do a CFBench with stock settings on r40 please?
[Nexus 7 Original Development] davisac:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

This work?
[Nexus 7 Original Development] franciscofranco:
Great. So with my latest hotplug driver changes CFbench scores were:

Native Score: 20518

Java Score: 6093

Overall Score: 11863

Since we're messing with CPU stuff only this benchmark is very accurate to detect differences. As we can see that is a very nice boost.
[Nexus 7 Original Development] davisac:
Sounds good Franco.
[Nexus 7 Original Development] fozzie:
Here's mine, in case you needed a second opinion.

Edit: Just remembered that this isn't the stock settings; I'd increased the GPU to 484 MHz. The second grab is with it at the stock 416 MHz.
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Hi guys! I've been helping Francisco with testing some different governor configs and I have to say that it feels great, much more snappy and smoother. I'm running a test version which should be out in the next hours :)

After some trial and error I think I've found a sweet spot and here are the cfbench results :

native 21533

java5888

total 12146

Here is my configuration in case you are interested in contributing. Please run cfbench with the following tuneables to see how the test version compares to r41 and share your results :cool:
[Nexus 7 Original Development] jsn:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

One more benchmark:

Using performance:

18107,5843,10748

Using interactive (60,95,15,15):

20303,5922,11674

All using row and westwood.
[Nexus 7 Original Development] ÜBER™:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

My scores with r40, with the values suggested.
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Here's mine
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Guys please try target loads = 70 and go hispeed load = 85
[Nexus 7 Original Development] ÜBER™:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40
[Nexus 7 Original Development] jsn:
It seems the scores are a bit lower.

I'm using fKu, I'm guessing your suggested values are for a different tuning-app?

Last scores: 20303,5922,11674

Current scores: 18821,5939,11091
[Nexus 7 Original Development] ÜBER™:
Dont understand why mine are so low.. :S
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Stock settings I got 11,xxx and with two runs of your suggested I got 10,xxx within 200 points of each other.

Sent from my Galaxy Nexus

---------- Post added at 12:33 AM ---------- Previous post was at 12:30 AM ----------

You can use the trickster mod app to change the target load its free. Normally I use fku but for the sake of testing I cleared its data and froze it.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] ÜBER™:
Anybody have any clue as to why my Java memory scores are 4000 less than everybody elses? :confused:
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Thanks for the input guys. I think we have a winner here. The second set of values were lower because the first one was more aggressive. However, using the second values on the test version gives much more higher scores on cfbench than r40

:cool:
[Nexus 7 Original Development] osm0sis:
target_loads of 70 + g_h_l 85 should increase the frequency to keep load low. How is that less aggressive than t_l 80 and g_h_l 90? :confused:
[Nexus 7 Original Development] SupWiz17:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Is r41 a test kernel that I can't find or are you guys calling it r41 when you take r40 and tweak the tuneables?
[Nexus 7 Original Development] ÜBER™:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Read.. It's a test kernel.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] osm0sis:
Nah, it's real. But only joaquin and franco have it currently. ;)
[Nexus 7 Original Development] djdunn:
Testing is a good thing :P
[Nexus 7 Original Development] SupWiz17:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Ok I was searching through the thread and couldn't find a link for the kernel and was so confused lol
[Nexus 7 Original Development] joaquinf:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I don't really know, I asked Francisco and he said that lol. I know that lower values on ghl are more aggressive but I don't really know how it works in conjunction with tl

I'm pretty sure that he went for 70/85 on mako too.
[Nexus 7 Original Development] osm0sis:
Madness! :p

The ****ers will be fast though. :D
[Nexus 7 Original Development] franciscofranco:
I said 70 target_loads and 65 go go hispeed load is more aggressive than 80/90.
[Nexus 7 Original Development] osm0sis:
Just flashed stock yakjuux back to my GN so I can send it off to Samsung Canada for a new screen in the morning. Just now I realized I need an alarm clock without my phone.. good thing I've got this N7 laying here. ;)

Now, let's make this the fastest ****ing alarm clock around! :D
[Nexus 7 Original Development] icepuente:
go go power rangers!! Haha just joking.

Anyway, I really appreciate all of the focus put on this kernel for the grouper as of late. I have been following the Nexus 4 thread as well as I plan to upgrade my SIII to the Nexus 4. I hate the SIII just because it isn't based on AOSP source and not many people write kernels for Sprint SIII. I was trying to cherrypick and make an imitation Franco Kernel for the SIII but gave up and decided to just wait until I buy a Nexus 4. :D
[Nexus 7 Original Development] franciscofranco:
I have a build to upload soon (joaquin tested it earlier today to make sure it was better) but my N7 is out of battery - playing too much Temple Run to test the kernel - so when its a bit charged I'll test something then release. Just a heads up ;)
[Nexus 7 Original Development] FReaKRaNT:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

@Franco, you need to update your service provider in your profile. :cool:

Cheers, FReaKRaNT
[Nexus 7 Original Development] Iced666:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

I just install this kernel. Looks rly nice and usefull.

What is the optimal gpu freq, cpu governor and io shed?

Thx for answers
[Nexus 7 Original Development] The Gingerbread Man:
Re: [KERNEL][GPL][N7][21 JAN] franco.Kernel - r40

Accidentaly thanked you there :p the stock values r40 are the best for now as we took ages to test them or look at couple of pages back
[Nexus 7 Original Development] Skyfall007:
after 35 minutes of playing angry gran run, 15% was lost.. so i will get about 4 hours of screen on.. that's horrible.. should I sent the tab as defective?

p.s: I did two cicles(0-100%)
[Nexus 7 Original Development] sjknight413:
Chill out, that's not that bad.

I find it hard to break five hours screen on when I'm not playing games so for hours screen on playing a game is fine.
[Nexus 7 Original Development] osm0sis:
OT: It's getting on my nerves how some people have apparently felt the need to give this thread a low rating. If anyone reading this hasn't rated it yet, please do so and raise it back up to where a thread full of helpful people, information and a damn fine kernel should be. :good:
[Nexus 7 Original Development] sjknight413:
I think my vote just brought it back up to five stars, Haha.
[Nexus 7 Original Development] osm0sis:
Haha thanks! But there shouldn't be only a 1 rating margin between 5 and 4 for a thread like this, so hopefully some others will also rate it and keep it high. :good:
[Nexus 7 Original Development] joaquinf:
Just an update francisco. After spending some time trying differents t_l/g_h_l set of values i had the best results with 80/90 it seems like that's the one. Batt life is fine, ui is fluid and games runs smooth. I also tested 70/85 and i couln't tell any difference so i'm leaning towards 80/90 because it could be more batt friendly.

Not to be a teaser but, as i told you yesterday, this test r41 is a hell of an improvement over r40 :) let me know if you need to do some further testing.

Keep up the good work
[Nexus 7 Original Development] osm0sis:
That's awesome. I had taken it down to 80/90 when we were testing before but it was hard to gauge the difference because we were still running 13 frequency steps. Glad to know all our ideas are paying off. :)
[Nexus 7 Original Development] poondog:
Good to know :)

AND, you're being a teaser :P I am trying to be patient