yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] tsx2004:
New to the Nexus 7 and the kernel.

I just flash smooth ROM and r38. Do i need to tweak any setting for the kernel? Thanks in advance. Had been searching couple pages back. The kernel governor is now set as ondemand. Is interactive better?
[Nexus 7 Original Development] Mac of York:
So far I have been running franco's defaults and I haven't had any issues. I usually go with what he sets and it is smooth.
[Nexus 7 Original Development] TheByteSmasher:
huh?

Minus the boost too, right? :confused:
[Nexus 7 Original Development] osm0sis:
Yeah, at some point Franco said to never touch the boost tunable. So we pretty much just pretend it isn't there. :p
[Nexus 7 Original Development] johnnyman25:
i have one crash while using chrome.i use interactive governor.whats better?ondemand or interactive?
[Nexus 7 Original Development] siscim23:
I unplugged my N7 on Thursday morning while running r37. Flashed r38 Thursday night. Haven't had to plug it in until last night, and I still had 15% left. 2.5 days of decent usage. Had about 5 hours screen on time, but listened to music quite a bit so screen was off. Great kernel
[Nexus 7 Original Development] Spacemonkie4207:
Flashed yesterday, using default settings. Very smooth but I did have a SOD last night. Shut off over night.
[Nexus 7 Original Development] lovejoy777:
Hi Franco I,m currently running your 361 on my Gnex and loving it (thankyou). I have a nexus 7 with slimbean 4.2beta2 & ubuntu 13.04 using multi rom bootloader.

just wandering if you will be supporting this multi-rom project by making your kernels compatible. here is the link from multiroms thread that he says to pass to kernel devs.

Link: http://xdaforums.com/showpost.php?p=34897653&postcount=244

I have no idea if its a quick job or if there's more to it.

No probs if its to much work or your too busy, I just thought I would ask, as I would love to use your kernel again on my nexus7.

thanks again

Steve
[Nexus 7 Original Development] Mac of York:
I prefer interactive but I don't use Chrome.
[Nexus 7 Original Development] johnnyman25:
why interactive?its more battery friendly?
[Nexus 7 Original Development] denzel09:
interactive is default governor in stock rom
[Nexus 7 Original Development] xator91:
I have franco kernel on Galaxy Nexus and Nexus 7 too. There is a way to add on Nexus 7 an option to boost charging on USB and AC Power? Because the charging time is too slow thanks franco
[Nexus 7 Original Development] xateeq:
I am on r38 from past 3 days. No issues to report.

Sent from my Nexus 7
[Nexus 7 Original Development] joaquinf:
USB Charging rate for the n7 is terribly slow and always will be, to the point that adding USB fast charge is worthless. To ensure the optimal charging rate when connected to the wall use the 2A wall charger included with the tablet, if you use a 1A charger included with the phone it will take twice the time to charge.

Check this
[Nexus 7 Original Development] 1pop23:
Yes you can. Make sure you have fast boot on your computer. Put your device into the bootloader

Reboot bootloader

Then run this command

Fastboot flash boot /'path to boot.img'/boot.img
[Nexus 7 Original Development] osm0sis:
It's faster than most other governors out there yet also balanced for decent battery life. Try it for awhile at defaults then give it a spin with franco's "magic" GN Governor tunables:

60000

65

45000

15000

:good:
[Nexus 7 Original Development] xator91:
Yes. i'm using the 2A Wall charger.. but is slow :(
[Nexus 7 Original Development] osm0sis:
I've also found the HP Touchpad charger with a good gauged cable to work excellently, possibly faster than stock OEM charger and cable. See my post in the charger thread for links:

http://xdaforums.com/showpost.php?p=33061220&postcount=121
[Nexus 7 Original Development] joaquinf:
Yup, they look fine.
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
Just curious since we're talking about chargers: can you use the 2A charger with other devices such as the Gnex? Will it charge faster? Or would that damage it?

Sent from my Nexus 7
[Nexus 7 Original Development] osm0sis:
Amperage is a max. So the charger only supplies what is requested of it, and the GN will only draw/request 1A like it's charger. No damage possible if things are all working like they should.
[Nexus 7 Original Development] joaquinf:
Interesting. I've read/seen a different theory. Check the video below and please share your thoughts.

[YOUTUBE]v-lnhaCtodE[/YOUTUBE]

Thanks
[Nexus 7 Original Development] puffel86:
osmosis is right. the charger only supplies what is requested from the device. so using an 2A charger with 1A device is ok because the device will be supplied with 1A.
[Nexus 7 Original Development] osm0sis:
Oh yeah, that video with the guy saying stuff about f.K having different voltaged builds. haha. Clearly they fact check before they post. ;)

Nah but about the "supercharging" thing, from what I've read in both of the big N7 charger threads (All-In-One in Accessories and Solved Charging in General), using a higher amperage charger shouldn't charge it any faster, since the device will still draw the same. My guess is that what they're confusing as supercharging is just the phone being able to draw the full 1.0A on the better gauged tablet cable and amped charger whereas using the phone's stock charger and cable it might be cutting a bit lower. Lowering the impedance with a large gauged cable is always the thing that makes the most difference, regardless of charger, so switching to the tablet (or any better gauged) cable on the 1.0A phone charger might still allow the phone to charge just as fast as switching to both the better gauged tablet cable and amped charger.

Again, this is just what I remember from reading on this a few months back, so I encourage people to go read some of the very knowledgeable posts in those threads and I'm sure they'll verify or improve on my explanation.
[Nexus 7 Original Development] xI mEzMeRiZe Ix:
I was only asking because I don't want to worry about having two different chargers whenever I need to charge. If the N7 charger won't damage my gnex, great. I'm not too concerned with the charging speed, but faster is always better :thumbup:

Sent from my Nexus 7
[Nexus 7 Original Development] puffel86:
In antutu the integer and floatpoint cpu scores are much lower with franco's r38 kernel compared to older versions of the kernel.

Does anybody can confirm that?

Is there a fault which causes this performance drops or what's causing it? I don't think my N7 is faulty. :confused:
[Nexus 7 Original Development] johnnyman25:
i use trickster mod cuz i dont have credits in my card to buy franco's app. can u tell where this settings belong too?e.g min_sample_time,target_loads,timer_rate.etc.thx!! :)
[Nexus 7 Original Development] mustbepbs:
Something must be broken. Quick, let's pester Franco about his kernel because this guy's benchmark score was lower than previous versions! Something must be horribly wrong! We can't stand for this injustice! We deserve better!
[Nexus 7 Original Development] joaquinf:
Thanks for your explanation man :) i'm always looking forward to your well detailed posts

Check here
[Nexus 7 Original Development] puffel86:
lol i only want to know if it's normal with the new r38 kernel and if others have the same drops in cpu scores from antutu.

i think the drops are really huge...from 3000 to 2000 points is a big difference or not?

otherwise the battery performance seems to be really good with the new kernel. :victory:
[Nexus 7 Original Development] Mac of York:
Benchmarks truly mean very little... You shouldn't run them. How does your device run for what you want it to do? I feel that mine is very zippy and I've never done a benchmark in my life. And I never will.
[Nexus 7 Original Development] drewski_1:
My Razr Maxx definitely charges faster on the N7 charger vs the Motorola. Sound like it was designed to take more if available?

---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------

Interesting. I'll have to try a different cable :D
[Nexus 7 Original Development] puffel86:
I know benchmarks are not the real world, but i thought there is a little problem in the kernel which causes these huge drops? Maybe something prevents the N7 to get the full power out of the tegra cpu? Only Francisco will know it? Maybe it's not a bug, it's a feature?

But all in all my N7 runs good with r38 and the battery seems to last long.
[Nexus 7 Original Development] kenkiller:
But we don't care about benchmarks. We care about what you mentioned that is good. BENCHMARKS SUCKS.
[Nexus 7 Original Development] bjcrj:
Which interactive governor settings would be best for battery? Stock or gnex? Thanks.
[Nexus 7 Original Development] dotnetnightmare:
I found positive results using francos settings 60000, 65, 1000, 45000, 15000 as well as setting the gpu to 484 and the companion core to 666. When using m-kernel it used 666. This feels snappier and is visibly better on graphic intense live wallpaper.
[Nexus 7 Original Development] icepuente:
This kernel doesn't use LP core. He modified the other four cores to scale from 100-1300. Switching clusters is supposedly a heavy operation.
[Nexus 7 Original Development] sjknight413:
Yeah but doesn't the companion core draw a lot less power whilst running? Which is a fair bit of time on any other kernel.

Any way to reenable it? Don't like the thought of it sitting there going to waste!

EDIT: Also why would Franco put in a function to change the lp core frequency if it is offline by default?
[Nexus 7 Original Development] icepuente:
He stated that NVIDIA included a companion core merely for marketing purposes. I have been running this kernel for a while now and notice around the same and even better battery life. Franco implemented efficient hotplugging to efficiently handle the 4 main cores. You cannot reenable the function. The application still shows the frequency because Franco hasn't bothered to remove it yet.
[Nexus 7 Original Development] TheByteSmasher:
Although generally the device draws about 750ma.

Sent from my Nexus 4

---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------

If you're a little electrically inclined, check out the thread in my Sig to make a cable that'll charge as fast as the device (any) will allow within the limits of the source, even from pc USB. Or herehttp://xdaforums.com/showthread.php?t=1984838

Sent from my Nexus 4
[Nexus 7 Original Development] xateeq:
But why ?

I think LP core is the best thing in Tegra 3.
[Nexus 7 Original Development] nazz.rule:
Coming from an old device(600MHz,single core), I agree with you.:D
[Nexus 7 Original Development] poondog:
It's not performance, its a battery debate isn't it?

I am personally fine with the new implementation, battery life is the same/similar to me

I'm not taking sides here, but I am using the kernel and loving it :D I've underclocked it to 1100mhz and it still flies

A bit off topic but was there any official word from Franco about the entropy tweaks? Sorry if this has been asked before :)

Sent from my Infected ViperVivo
[Nexus 7 Original Development] neo-X:
Yeah I'm keen to find out what Franco thinks about these entropy things

Galaxy Nexus MiNCO
[Nexus 7 Original Development] osm0sis:
Franco said on the GN side he'd try them out and report back with his findings. Right now he's in Vegas though so understandably he might be a bit AFK. ;)
[Nexus 7 Original Development] CharliesTheMan:
What I would give to be there. Financially Vegas and CES wasn't possible this year but next year I will be there. Anybody want to buy a kidney?

Anyone have a link to a good thread discussing the entropy tweaks? Now I'm curious.
[Nexus 7 Original Development] osm0sis:
I think someone posted the link to the Seeder thread a few pages back and I quoted what Google had to say about it shortly after so you could search my posts to find it if you like. :)
[Nexus 7 Original Development] DemosZevasa:
One of the CM devs said that all it does realistically is constantly using the CPU so the CPU is always in an active state. Equivalent to setting your governor to performance.
[Nexus 7 Original Development] osm0sis:
Yeah that's what Google said too; placebo or just elevating the CPU freq so of course it feels faster.

There were some sysfs tweaks someone posted in the GN thread that someone thought might be what Seeder is doing, or might be separate entropy tweaks. Those were what Franco was going to test out, so I'm still interested to hear his results.
[Nexus 7 Original Development] Keitaro:
Short post by XDA http://www.xda-developers.com/andro...-other-devices-with-seeder-entropy-generator/

174+ pages http://xdaforums.com/showthread.php?t=1987032

18+ pages http://xdaforums.com/showthread.php?t=2077086
[Nexus 7 Original Development] TheByteSmasher:
I'd love to be at CES also, but I am going top get the new Seagate Wireless Pro... 1TB Wi-Fi drive! OK, back on topic... r38 freeze. I'll attach last_kmsg right after I open this in a browser. :eek:

Here http://db.tt/HfXesDdr

Sent from my Nexus 7
[Nexus 7 Original Development] FitAmp:
Same here :thumbup:
[Nexus 7 Original Development] puffel86:
Regarding to this thread and the today updated results:

http://xdaforums.com/showthread.php?t=1889571

I tested a little bit with my n7. Something seems to be wrong with my n7 when running franco's r38.

I only get 11500 points in antutu with r38, but i think normal would be 13000-13500.

So i tested with stock kernel and got 12800 points and tested with m-kernel (@1,3ghz max) and got 13200 points. With deactivated logs and interactive governor i got 13400 with m-kernel. My n7 runs stock 4.2.1

So something is wrong with my n7 when running r38.

Nobody else experienced this?
[Nexus 7 Original Development] siscim23:
-sigh-

Does your battery last longer with franco kernel? Does performance feel poor to you? If you feel it performs great and has better battery life, what do benchmarks mean?
[Nexus 7 Original Development] puffel86:
On default settings r38 is a little bit choppi for me. Some stuttering in the ui is noticeable. So I have to increase the highspeed_freq to 1000 then it feels ok. But stock and m-kernel (@1,3ghz) both seems to be smoother to me than r38, especially with default settings.

Maybe there is really a little issue with the kernel on some devices? With older versions of franco's kernel it was smoother on my n7.
[Nexus 7 Original Development] joaquinf:
Hi guys!

Yesterday i got a jawbone jambox and i am very surprised/dissapointed about the terrible bluetooth stack quality on 4.2.1 :( When i play music on the Google Music app is impossible to get a decent playback there is major stuttering every 3 seconds, same goes to youtube or basically

any

content streamed from the internet. With local stored content is not that bad but as soon as i start using the wifi connection the suttering comes back. With games there is major lag/delay between what is shown on the screen and the sound that comes out of the speakers :(

This issue has been reported already on the google code forum (issue 39633) but there hasn't been any official word from Google. There are also some xda threads reporting the issue (check here ). The thing is that this issue wasn't present in 4.1.x and on my Galaxy nexus i have no problem whatsoever on 4.2.1 :confused::confused:

I know that this is probably not the right time to report something because of the CES but i hope that Francisco can take a look at the bluetooth stack and maybe try to fix Google's **** again. If there is anything i can do to help i'll gladly offer myself as a tester :)

Thanks guys :)
[Nexus 7 Original Development] TheByteSmasher:
@ JOAQUINF I also have a JamBox. I use volume+. It has a Bluetooth section, in it I choose echo/delay value of 2 and it seems to sync my video and audio. World's most of the time, but I don't know why.

Sent from my Nexus 4
[Nexus 7 Original Development] rumirand:
Hi there.

First of all, thank you franco for this awesome kernel. It delivers great performance and good battery life without the "hax" crap.

I'm using franco r38 right now on 4.2.1 stock rom. I've a problem tough:

When I'm using aDownloader (or any other IO "intensive" app), I'm getting freezes. They occur only when the app is running in background. Using r38 with stock settings. I've checked last_kmesg and I got whis:

[ 315.950415] host1x host1x: .android.chrome: syncpoint id 22 (3d) stuck waiting 71215, timeout=2147483047
[ 315.950565] host1x host1x: id 8 (disp0_a) min 3451 max 3453
[ 315.950644] host1x host1x: id 12 (csi_vi_1) min 22 max 0
[ 315.950780] host1x host1x: id 13 (vi_isp_0) min 25 max 25
[ 315.950856] host1x host1x: id 15 (vi_isp_2) min 22 max 0
[ 315.950994] host1x host1x: id 18 (2d_0) min 8209 max 8211
[ 315.951070] host1x host1x: id 19 (2d_1) min 44 max 0
[ 315.951203] host1x host1x: id 20 (disp0_b) min 3451 max 3453
[ 315.951279] host1x host1x: id 22 (3d) min 71186 max 71250
[ 315.951356] host1x host1x: id 24 (disp0_c) min 3451 max 3453
[ 315.951492] host1x host1x: id 26 (vblank0) min 18760 max 0
[ 315.951573] host1x host1x: waitbase id 1 val 44
[ 315.951707] host1x host1x: waitbase id 3 val 5649
[ 320.680383] mmc1: Timeout waiting for hardware interrupt.
[ 320.680519] sdhci: =========== REGISTER DUMP (mmc1)===========
[ 320.680598] sdhci: Sys addr: 0x00000000 | Version: 0x00000002
[ 320.680735] sdhci: Blk size: 0x00007040 | Blk cnt: 0x00000000
[ 320.680814] sdhci: Argument: 0xa5000040 | Trn mode: 0x00000003
[ 320.680949] sdhci: Present: 0x03df0000 | Host ctl: 0x00000012
[ 320.681025] sdhci: Power: 0x0000000d | Blk gap: 0x00000000
[ 320.681160] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[ 320.681235] sdhci: Timeout: 0x0000000e | Int stat: 0x00000000
[ 320.681369] sdhci: Int enab: 0x02ff000b | Sig enab: 0x02fc000b
[ 320.681445] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[ 320.681579] sdhci: Caps: 0xe7ffd080 | Caps_1: 0x00002077
[ 320.681654] sdhci: Cmd: 0x0000353a | Max curr: 0x00969696
[ 320.681787] sdhci: Host ctl2: 0x00000001
[ 320.681861] sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0xa580a010
[ 320.681991] sdhci: ===========================================

39 Corrected bytes, 0 unrecoverable blocks

Not sure how to solve this.

Thanks!
[Nexus 7 Original Development] TheByteSmasher:
Same issue with me. But my kmsg shows a different ending... http://db.tt/HfXesDdr

Sent from my Nexus 7
[Nexus 7 Original Development] joaquinf:
Cool man, thanks. I'll try it :)

Edit: which version are you using? The one posted on the play store? It says that isn't compatible with jellybean and the latest alpha posted on the forums site isn't compatible with Nexus devices :confused:
[Nexus 7 Original Development] TheByteSmasher:
This is off topic-ish... Continued via P.M.

Sent from my Nexus 4
[Nexus 7 Original Development] nagle3092:
Here's a video of an issue I got running r38, now it started on r31 as well. I rolled back to the stock kernel to see if it will happen again.

https://www.youtube.com/watch?v=dVvZq-STt5U&feature=youtube_gdata_player
[Nexus 7 Original Development] dotnetnightmare:
It has to be said, so I will step up and be the hated one. Nvidia marketed the companion core as a means to deliver speeds up to 1.7g on one core and 1.5g with all 4 cores. The one core handles lower functions like audio and video. When the load increases, the governor will add cores as needed. Intelligent load handling, increasing battery life without impacting performance. This "marketing gimic" is working so well Nvidia is implementing it in Tegra 4. Does Nvidia have a reputation for being a *gimic"? Nvidia is the industry leader! Several users have pointed out low bench mark scores and heard "long battery life". The impact on performance is measurable. I don't care what you can "feel", testing is conclusive! I "feel" Franco should not have deliberately changed Nvidia's technology without disclosing ALL his alterations in the first paragragh under "what's new". I do not know Franco well enough to say "he's smarter than the team of engineers at Nvidia, and can alter the core functionality of Tegra 3 to make it better than Nvidia could. We are not talking frequency or voltages, but removal of, or crippling a feature with no disclosure to us. I am back to M-core a26 for now. I throw myself to the wolves, you.
[Nexus 7 Original Development] osm0sis:
Franco's never been good at updating the OP, if you've used his kernel for any amount of time you should know that. ;) As always if you want to know what's going on follow the nightly changelogs as he posts them; that's where all the info has always been, and that's where your "full disclosure" is. There should be no need for histrionics from either side. He's experimenting with something here, that's how progress is made, in fact, that's what XDA is all about, and if he didn't see decent results on his own device it never would have made it to us.
[Nexus 7 Original Development] dotnetnightmare:
I truly meant no disrespect to Franco. I truthfully wanted to state what others & I are thinking. It's out in the open now for users to respond. I love Xda & discussion is what makes us learn. Please keep up the hard work Franco.
[Nexus 7 Original Development] icepuente:
You truly meant no disrespect and yet you are indeed disrespecting him anyway. Disabling the LP core does not in anyway decrease the performance of the tablet. The LP core was intended to function alone without the cooperation of the other cores. If we were to predict how the tablet would perform with your logic, the tablet would actually have poorer battery life and better performance. Franco's kernel still intelligently handles the multi-core architecture of the Tegra 3, activating cores when the load is present. He is constantly tuning the hotplug driver to be as efficient as possible, only activating cores when it is truly needed and also when interacting with the device to give it a smoother and fluid appearance. As for the benchmarks, people will always compare each kernel version. What has to be considered however is that not all benchmarks are created equal. Throttling, the benchmark application used, and governor settings must all be accounted for and often differ between different benchmarks. That is the primary reason why most benchmarks are disregarded. Benchmarks are truly useless. My personal opinion having used all of the revisions for this kernel is truly I do not notice any difference at all in regards to battery life, performance, or stability with my device.
[Nexus 7 Original Development] mihovil13:
Hi guys, this is the only fully working kernel with PA2.99

OTG works perfectly, no reboots at all, Adobe flash works great with 1080p videos.

I've set GPU to 500 MHz, so as companion core, great battery life, smooth performance even though scroll is not butter as it is.

But I'm thinking of tweaking build.prop, that windowsmgr line makes butter every where :)

Great job indeed.
[Nexus 7 Original Development] Metallice:
That's not how the companion core works :/ you're describing Tegra EDP.

Sent from my Galaxy Nexus

---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------

The LP core doesn't run independently. It just silently takes over. The LP core cannot run without the G cores off and vise versa. They do not function alone, but work together to trade off load from one to another before turning off.

Sent from my Galaxy Nexus
[Nexus 7 Original Development] icepuente:
Thanks! I knew that but I phrased it incorrectly.
[Nexus 7 Original Development] drewski_1:
Wow. Just wow. :confused:
[Nexus 7 Original Development] TheByteSmasher:
Odd issue r38.

Kmsg http://db.tt/3hqCPmiH

Open recent programs, swipe all away, reopen recent programs and they all still exist, rinse repeat. Stock Rom. It only occurs sometimes. I'm not all exactly sure what the kernel controls so if this can't be kernel related, please don't flame, explain. Thanks

Sent from my Nexus 7
[Nexus 7 Original Development] irminsul:
That's not kernel related but a 4.2 issue. Try swyping recent apps and while in recent apps change orientation. You will see them coming back. 4.2 has some bugs.