yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] tariq_devil:
is the wifi detection error fixed in this? my Nexus 7 does detect any wifi or ad hoc network, first time ti detects but later it doesnt and the connection drops, so is it rectified in your kernel?
[Nexus 7 Original Development] cmg5461:
Wonderful kernel!

Very customizable
[Nexus 7 Original Development] morfic:
Basemark ES 2.0 Free Taiji.

It's demanding and unlike nena2 you won't hit vsync. Limits.

This allows GPU evaluation even at stock

Panel clocks.

It's also not as lengthy as other GPU benchmarks, yet the result is useful.
[Nexus 7 Original Development] CharliesTheMan:
What rom are you running and what version of the kernel?
[Nexus 7 Original Development] espionage724:
I was messing with wifi tethering on a Galaxy Prevail trying to get my Nexus 7 to connect. It didn't see the wifi the first few apps I tried, and finally it found the wifi for FoxFi, but couldn't connect. Possibly related...

Also, would it be possible to get USB Tethering kernel support?

http://xdaforums.com/showthread.php?p=30261507#post30261507

I tested the Wired Tether 1.4 app with the latest stable kernel, and it mentioned no kernel support :/
[Nexus 7 Original Development] simms22:
have you tried the prevails native wifi tether? i almost exclusively tether my n7 to my galaxy nexus without issue, even when i was on motleys kernel. all worked as it was supposed to work. installing wired tether on the n7 will get you nowhere since it does not support reverse tethering. youd have to install wireless tether on the prevail. its not a kernel issue, its a its not supported issue.
[Nexus 7 Original Development] espionage724:
I don't think I noticed a native option on the prevail, however, it's also using a custom kernel/ROM. I'll have to look into that later.

I don't want to do reverse tethering though. If I understand what reverse tethering is, it's if I want to have my Nexus 7 use my Computer's internet connection. I want it the other way around though (My computer use the Nexus 7's internet connection).

On my SGT7 + GB or ICS, if I enabled usb tethering, it would create a NDIS network device on Windows, and then work fine from there. I imagine a similar event occurs on compatible JB-based devices, but I have no personal experience with this.

wired-tether has http://code.google.com/p/android-wi...kernel-update_usbtether_r3.zip&can=2&q=Kernel on the downloads page. Upon opening it, there appears to be a su file in /system/bin and a wlan.ko in /system/lib/modules. Not entirely sure if this would work on JB or not, but if I did flash this, what's the worse that can happen? If I bootloop, could I just enter recovery and delete the file with ADB?
[Nexus 7 Original Development] simms22:
the nexus seven does not have a 2g/3g/4g radio, you cant tether something else to it. you can only tether the nexus seven to something else.
[Nexus 7 Original Development] espionage724:
The prevail and computer don't have relation to each other.

When I took my desktop computer to my friend's house, I would use my SGT7's USB Tethering feature to share my tab's internet connection (my friend's Wifi) to my desktop (his router was downstairs, we were upstairs). My SGT7 only had Wifi as well, and did not have a SIM card or anything at the time, and this worked fine (in other words, my SGT7 was functioning as a wifi-only tablet). I wanted to do the same with my Nexus 7. In short, I want my Nexus 7 to function as a WLAN adapter for my desktop.

As for the prevail; when I'm out traveling elsewhere, I may want to setup a hotspot or something on there, so that I can share it's 3G connection with my Nexus 7.
[Nexus 7 Original Development] simms22:
i understand what you are saying now. after googling it for a few minutes, i can safely say that i cant find any info about it for the nexus 7(RNDIS or NDIS) except your xda thread, sorry :(
[Nexus 7 Original Development] CharliesTheMan:
If I'm picturing it right, you're basically using the Nexus 7 (or wanting to use it) like a wifi access point/range extender to get wifi your device receives to other devices nearby.

I think I remember reading a post or thread somewhere that this can be done, I know we did it on the rom that I helped with (Team Wookie, Transformer Prime) and I remember seeing someone discussing it on the nexus 7.

I can't promise anything but I have a couple of good buddies (one of those that will know some about it is Motley) that are devs and might can shed some light on the situation, and I'll gather any information I can from the others too and whatever I can gather I'll pass on to you.
[Nexus 7 Original Development] brizey:
My experience is that the heat comes from the cpu. When I do benches with the 1.7/600 kernel, the temp shoots up during the CPU part then falls during graphics tests.

I ran the whole gpl bench and it stayed in the upper 50's for the whole test.

Edit: Although I wonder if the gpu is physically far enough away from the sensor that it only gets a muted reading when the gpu is carrying the load.

from my Nexus 7 using xda premium
[Nexus 7 Original Development] _motley:
Hey guys, my thinking is that it would at least need to be integrated into the ROM for it to work. It probably isn't there by default because we only have the OTG port. Not an expert on this, so I don't know if it will work with an OTG port or not.

Edit: also just to note, the kernel already has CONFIG_NETFILTER=y and CONFIG_IP_NF_IPTABLES=y, so we are good there.

For Grouper, most device trees I have looked at only have this:

Part of /android_device_asus_grouper/overlay/frameworks/base/core/res/res/values/config.xml:

<!-- List of regexpressions describing the interface (if any) that represent tetherable USB interfaces. If the device doesn't want to support tething over USB this should be empty. An example would be "usb.*" -->
<string-array translatable="false" name="config_tether_usb_regexs">
</string-array>

From ramdisk in /android_device_asus_grouper/init.grouper.usb.rc:

on init
write /sys/class/android_usb/android0/iSerial ${ro.serialno}

Now, for example, here is the Asus Prime:

Part of /android_device_asus_grouper/overlay/frameworks/base/core/res/res/values/config.xml:

<!-- List of regexpressions describing the interface (if any) that represent tetherable USB interfaces. If the device doesn't want to support tething over USB this should be empty. An example would be "usb.*" -->
<string-array translatable="false" name="config_tether_usb_regexs">
[COLOR="red"] <item>"rndis0"</item>[/COLOR]
</string-array>

From ramdisk in /android_device_asus_tf201/ramdisk/init.cardhu.usb.rc:

on init
write /sys/class/android_usb/android0/iSerial $ro.serialno
[COLOR="Red"]write /sys/class/android_usb/android0/f_rndis/manufacturer ASUS
write /sys/class/android_usb/android0/f_rndis/vendorID 0B05
write /sys/class/android_usb/android0/f_rndis/wceis 1

[/COLOR]
[Nexus 7 Original Development] harrynghiem:
Hello guys,

I want to do undervolt and UC. So i have tried Setcpu, voltage control. But they did not working for this kernel. Please advise what is app to do undervolt.

Thks in advance
[Nexus 7 Original Development] CharliesTheMan:
System tuner works with undervolting this kernel and reads the voltage accurately.
[Nexus 7 Original Development] tariq_devil:
Sorry for my last repeated query. :(

I flashed the motley_anykernel_nexus7_1.1.0_NoGPUOC_build_214 this kernel and my adhoc connectivity issue is solved, i havnt tried it on wifi. Performance is quite good and its butter smooth, running my stock rom flawlessly. But i have one problem, whenever i turn off the screen, the connectivity shuts off and i have to unlock the screen or wake up the screen to reconnect, i guess the wifi goes to sleep whenever i turn off the screen. Well, i turned off the wifi sleep policy in advanced but still the problem persists and i cant download big games like TDKR and Asphalt 7. Is there any solution?
[Nexus 7 Original Development] _motley:
Hi, you may want to use kernel v1.1.1 instead since it is labeled as stable, but there won't be any difference in WiFi performance. The kernel WiFi driver hasn't been changed in this kernel, i.e. all code for the broadcom driver is the same as stock.

If you have your WiFi policy set to "always on", it shouldn't be a problem with large downloads when the screen turns off. I have downloaded several large games and haven't had a problem, however for some games the servers are slow and it can take awhile if many are downloading at the same time.
[Nexus 7 Original Development] CharliesTheMan:
This is definitely a settings issue unless you're running profiles or power saving apps or some kind of task killer combo app.

I'll look at my settings in a few minutes and give you some stuff to try.

Important: you should REALLY be running version 1.1.1, just a lil sidenote.
[Nexus 7 Original Development] t_007_v2:
I went into settings / developers options and selected stay awake "screen will never sleep while charging" when downloading from play.

TDKR is a demanding game and works best with the 520gpu kernel. I've been playing TDKR at 1.5 with the 520gpu and it's silky smooth.
[Nexus 7 Original Development] :
I flashed #177 last night.. (using Liquid JB) Woke up 8 hours later and it was @ 100%! Really like the feel of it too! Tks!
[Nexus 7 Original Development] tariq_devil:
I am on stock rom which i got with Nexus 7, i got cwm latest recovery, and i am on motley kernel non OC one. still my wifi isnt detected and ad doc connection drops as soon as i turn off the screen.

---------- Post added at 07:27 PM ---------- Previous post was at 06:57 PM ----------

i face this problem since i bought it, first night the wifi worked flawlessly, but the next day i was not able to even detect my wifi. then i flashed my N7 with custom rom too but it was not able to detect. then i reverted back to stock rom and same cwm & rooted it. Still my wifi at home isnt detected by it, once it was detected when i resetted my modem but next time again it cant even detect my wifi. i dont know whats the issue. what should i flash and what should i try?

---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------

ok i am waiting for it.
[Nexus 7 Original Development] phonic:
Is anyone having issues where the sound stops working? I never had a problem prior to the latest kernel, but it might be a specific app breaking things.

Basically, every so often, generally after playing Order and Chaos, I lose all sound out of my speakers. When I raise/lower the volume, it shows it being adjusted, but nothing happens. The first time it happened, a reboot fixed it. Then when it happened again, turning the sound all the way down (ie: mute) and back up resolved it. It's happened 3-4 more times, and that has always worked. Sound works fine in the game and after I close it, but when the tablet suspends and comes back, that is when the problem usually occurs.

My hunch is that the game is somehow breaking it, as that was the only thing I've installed since earlier versions of the kernel, but I figured I would ask to see if others are experiencing the same problem.
[Nexus 7 Original Development] foxorroxors:
I had this problem but since swapping to a different rom it hasn't happened using latest motley...

Anyone noticed slower reads when turning off fsync?
[Nexus 7 Original Development] randroid123:
I'm having this issue using stock kernel + latest BAMF... Though it is a very infrequent occurrence
[Nexus 7 Original Development] phonic:
I am on stock ROM with motley's 1.1.1 kernel. Outside of some OC and UV (plus root obviously), everything is pretty much stock.
[Nexus 7 Original Development] AZImmortal:
_motley: I was wondering if this kernel had the option to force AC charging?

http://xdaforums.com/showthread.php?t=1564973
[Nexus 7 Original Development] katestar:
hi _motley, I don't know about other people but I really don't want to go to 600mhz gpu clock speed as it just seems too high. But, I would love something a little higher than 520. Maybe something like 540-550mhz? As in something in between 520 and 600 so it is a big enough of an increase to show noticeable improvements, but small enough that it doesn't get uncomfortably hot like 600mhz seems to. What do you think please? :)
[Nexus 7 Original Development] espionage724:
Hmm, so it would seem the ASUS Prime supports RNDIS? If so, could the code be easily ported over to the grouper?
[Nexus 7 Original Development] NoTnERb:
alright, so I don't know what I'm doing wrong but when i run the zram as a script with su and boot, it doesn't work. Moving it to init.d and setting permissions as 755, reboot, no good as well. I'm on paranoidandroid. any help would be appreciated, it's 2am here so I just might be sleepy and doing something wrong.

edit: nvm, got it to work
[Nexus 7 Original Development] czater:
I have strange issue...after night (8-9h) battery status is 16% (like when i go sleep) but after 10-15s use suddenly is going to 14% (2% down) :/ It happen 2 times and always 2% down (first 74% and 16%) :/ i dont know if this is important but it was on one full battery charge. wtf?
[Nexus 7 Original Development] danielsf:
Just applied a bit of tape to one of the wifi grounding bits on the inside cover and my flickers gone. Would you consider lowering the max low brightness so it is easier to read in the dark like Clemsyn's Elite Kernel please? As now that there is a way for users to fix the flickering. Also, I have never herd about fsync before, I have Google'd it. But I was hoping you could expand on more about it, as in how likely is it to corrupt the data? What kind of corruption are we talking about, the occasion file (like music, photo etc) being corrupted or could it ever make the device in unbootable by corrupting system files and would have to flash a new rom to fix it? Could it completely brick the device? You have said it increases battery, but will it increase performance? Sorry about the questions, your probably fed up of seeing me in your thread :p I have done some research and understand a little about it, but I just need to make sure I understand the risks properly.

Anyway, I have been running this kernel on three different nexus 7's (replacements due to screen lift and out the box broken speaker.) and it has being flawlessly fantastic, thank you very much :)
[Nexus 7 Original Development] evonc:
Make sure you're not on the performance governor as it will force the device to run at the fastest speed draining battery faster. You can change it by using setcpu/system tuner or if you're running a custom ROM under the performance tab in settings.
[Nexus 7 Original Development] hopscotchjunkie:
I don't think that's too unusual, and I think it's related to how this cpu handles deep sleep. The Tegra 3 One X does exactly the same thing - battery stats aren't updated at all during deep sleep, then once you wake the device they catch up to where they should be (which shows as no drain at all for hours followed by a sudden drop of a couple of % to the correct level).

If you're seeing continuous rapid drain after waking the device (not just a one-off drop) then you might have a different issue.
[Nexus 7 Original Development] czater:
no, no continuous, just after unlock ;o I thought it isn't normal but if it is... so after ~12h sleep ~2% battery go down, it isn't bad? :D
[Nexus 7 Original Development] leelaa:
Have a look in settings/performance i think there is a zram option there.
[Nexus 7 Original Development] _motley:
Nice to see that the wifi grounding fix is working. I might give it a try, although I really don't notice it too much on my tablet. I'll implement the lower brightness setting to see what the difference is. Android (ROMs) also has the capability to specify the low end brightness level, so I am not sure if this will work on stock or just on ROMs that allow customization of these levels (CM10 is one that I have used).

As far as fsysc = off, the ultimate risk would be corrupting the /data partition and having to format it. You would lose all your user data in this case, but it still won't brick the device since you would still be able to still get into recovery/fastboot. When you do a regular data wipe (like when switching between ROMs), you retain all of your downloads, pictures, files etc. If the ext4 /data partition becomes corrupted, you would lose it all and would have to format /data and do a complete restore. So, if you run this way all the time, it is best to backup your data often and sync important files to the cloud so you don't lose much if anything.

Having fsync off defintiely improves battery and i/o performance. I run this way quite a bit, but I wouldn't recommend my mother to do so:laugh:

Glad to hear the kernel has been working nicely for you.

I wouldn't worry too much about it. I haven't changed anything in the kernel source that would affect the "battery remaining" algorithm.

Yeah, it is quite amazing!

Not yet, but I started researching what I need to do back some time ago. At this point, I contacted Chad to see if he had any pointers or existing code for our SMB347/BQ27541, but I haven't heard back from him after the initial contact. Not sure if anyone else has kernel support yet, but I think morfic was working on it too from looking at his git. Hopefully we'll have something soon if it's doable.

This is certainly doable. What would be helpful would be to have some sort of a real world test that shows that this is actually beneficial/necessary for us in certain scenarios. Like a game that doesn't work on this kernel, but does work on clemsyn's 600GPU kernel. This needs to be done outside of many of the benchmark tests, since most of the ones being used aren't showing the real story of GPU performance. There are a few benchmark apps that are decent that have been mentioned back a few pages in this thread that are useful. Now that we have bumped up the pixel clock (some kernels are setting this very high), we aren't really seeing the improvements that many think we are. If a quarter of the frames are refreshed twice, then there really is no benefit of seeing 100fps on a quadrant test vs 75fps...its just using extra power and the likelihood of having strange artifacts/colors increases. That said, the pixel clock can be a limiter to raw GPU power and increasing can be justified to a certain extent.
[Nexus 7 Original Development] TheChaoticLlama:
Brilliant kernel. Very good performance without having to compensate battery life. Also, Nenamark went from 55.7 fps with stock kernel to 65.2 fps with 520 GPU overclock. Games seem to be completely lag free (well, the ones I've tried GTA, Dead Trigger etc). It would be cool if you could lower minimum brightness.

Thanks for all your hard work. :)
[Nexus 7 Original Development] criscan:
Its the same thing to me...thank you.
[Nexus 7 Original Development] meatlocker:
Add me to the list. _motley, your kernel is consistently stabler and more reliable than all of the others. Thanks for your diligence and hard work on all our behalves.
[Nexus 7 Original Development] noneabove:
If you've got the GPU over clocked.. my only concern is, if an app were runnable smoothly at stock speed, would the GPU ramp up anyways and therefore use more power and generate more heat? Not sure what the gpu's governor is, just curious what happens
[Nexus 7 Original Development] TheChaoticLlama:
With stock I experienced slight stuttering when a lot is going on in a game, Dead Trigger for example. The 520 OC completely abolishes the stutter and leaves the game running beautifully. Heat does not become unbearable but is fairly worm when playing for extended times, as expected. When doing things like browsing, reading, watching films etc the device stays nice and cool, this kernel is excellent. Well worth the time it takes to flash. :)
[Nexus 7 Original Development] foxorroxors:
While turning fsync off I have noticed that its smoother while moving to different areas where before it would stutter while loading these areas. Can't say he noticed the battery lasting any longer tho. I still get 5 hours constant gaming.
[Nexus 7 Original Development] mishko:
I've experienced similar hick-ups in D.T, but WITH the motley-kernel (484mhz-version) installed. Can't recall experiencing this with the stock kernel. Maybe I should try the 520mhz version?
[Nexus 7 Original Development] espionage724:
I may recommend switching the governor in use. I don't think I had that stuttering in DT when using OnDemand, but interactive is default
[Nexus 7 Original Development] czater:
For me stuttering is when i use ondemand....interactive is better in my opinion.
[Nexus 7 Original Development] luke05dee:
I have to ask, why do you increase the pixel clock? Like if you have it set so you can only go to 60fps, I have read that it save considerable power and heat as there are no wasted frames being drawn. Plus anything over 60fps is useless due to our eyes not being able to notice anything higher. Overclocking the gpu is great as in a lot of games you can feel the difference, but why does the fps in say quadrant go over 60fps? I guess it is good for benchmarks, but I thought drawing more than 60fps wastes power and caping it to 60fps even with a gpu overclock is better on battery and heat, like how the galaxy s2 & s3 is capped at 60fps. Like maybe we could try a version whose gpu fps is capped at 60fps to see if there is better battery and heat, but gpu is still at 520mhz. We could use gpu tests like Basemark es2 which never gets close to 60fps even with the overclock to measure performance. I am sorry to be a pain, I have just been taught in the past that drawing anything over 60fps is a complete waste of power, and it should be capped at that and if you want to measure gpu performance you should use apps like basemark es2 which stress the gpu but never even get close to the cap. What do you think motley please?
[Nexus 7 Original Development] mishko:
I was using interactive. I’ll try the other governors, or go back to stock.

Skickat från min Nexus 7 via Tapatalk 2
[Nexus 7 Original Development] espionage724:
Some people can argue this. While gaming on my PC, I'd rather have my FPS uncapped, which is why I get like 100 FPS in certain games, even though my refresh rate is only 60Hz.

Not sure how Android handles vsync, or if it's even enabled, but vsync in most cases introduces input lag, which may be able to be reduced with Triple Buffering, but this takes more GPU power, and at any point you drop below 60 FPS, in most cases you'll be immediately dropped to either 45 or 30 FPS.

I personally like just running at 520Mhz on the GPU, since this is what the Tegra 3 was designed to run at anyway (I think). Shouldn't damage hardware or push heat past safe limits either. I don't mind the cap at 60 FPS too much, but what if it could be unrestricted? I don't know if there "has" to be a cap on how much FPS you can get, but I'd be interested in trying a build that has no such restriction :)
[Nexus 7 Original Development] hanthesolo:
Yeah, well I believe he's more interested in capping it to improve battery life a decent amount than getting 100% awesome game performance. It would be nice though if motely made a capped version at the highest clock, but then again that's ANOTHER kernel build he has to make before releasing :).
[Nexus 7 Original Development] Hotcooler:
Quick question. If I want to control voltages from init.d script, will this sort of lines suffice to do that?

echo '1540mhz 1125 mV' > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

Or do I need to write values to every core separately?

Edit 1: Also I'm sort of worried that it actualy rock solid stable at 1000mv @ 1.5ghz, but crashes under load at 1237@1.6. Sort of hard to believe it actually working on 1 volt there...

Edit 2: Ok there's probably a minimum voltage set somwhere... I absolutely do not believe it can be stable at 900mv@1.5ghz@520mhz. So... I did somewhat of a search and could not find anything... enlighten me please about what is going on here.

Edit 3: seems like it was some sort of a bug, and it stopped reading the values. 900mv insta freeze. same with 1 volt. So it can only do 1.1v stable, still not that bad.

Edit 4: Figured out the correct line for init.d