yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Nephilim:
I left a message to Sean Hoyt, one of the main developers for LiquidSmooth over on their G+ Community, hopefully he can provide some insight that will help with the read-only stuck tunables for at least LiquidSmooth. I know that not all roms are having this problem. :)
[Samsung Galaxy Nexus] osm0sis:
If you know what file the color control source is in you should be able to look for safety_enabled in there and just default it to 0 yourself. :)

Tinkering like that's about the extent of my C skills haha. ;)

I'll go looking for the touchboost. :good:

Edit: [MENTION=4608636]bsmitty83[/MENTION] They were pretty recent. :cowboy:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/8b95f8c567cb3ea2d950effc1ad10583116ac0bd

https://github.com/franciscofranco/Tuna_JB_pre1/commit/367db9ed9e3a79ef0805a270de97fe683d224547
[Samsung Galaxy Nexus] vfmmeo:
For the moment, there's a ownership issue:

root@maguro:/sys/devices/system/cpu/cpufreq/interactive # ls -la
-rw-rw-rw- system system 4096 2014-02-12 20:50 above_hispeed_delay
-rw-rw-rw- system system 4096 2014-02-12 20:50 boost
-rw-rw-rw- system system 4096 2014-02-12 20:50 boostpulse
-rw-rw-rw- system system 4096 2014-02-12 20:50 boostpulse_duration
-rw-rw-rw- system system 4096 2014-02-12 20:50 go_hispeed_load
-rw-rw-rw- system system 4096 2014-02-12 20:50 hispeed_freq
-rw-rw-rw- system system 4096 2014-02-12 20:50 io_is_busy
-rw-rw-rw- system system 4096 2014-02-12 20:50 min_sample_time
-rw-rw-rw- system system 4096 2014-02-12 20:50 target_loads
-rw-rw-rw- system system 4096 2014-02-12 20:50 timer_rate
-rw-rw-rw- system system 4096 2014-02-12 20:50 timer_slack
root@maguro:/sys/devices/system/cpu/cpufreq/interactive # cd ..
root@maguro:/sys/devices/system/cpu/cpufreq # cd smartass/
root@maguro:/sys/devices/system/cpu/cpufreq/smartass # ls -la
-rw-rw-rw- root root 4096 2014-02-12 20:55 awake_ideal_freq
-rw-rw-rw- root root 4096 2014-02-12 20:55 debug_mask
-rw-rw-rw- root root 4096 2014-02-12 20:55 down_rate_us
-rw-rw-rw- root root 4096 2014-02-12 20:55 max_cpu_load
-rw-rw-rw- root root 4096 2014-02-12 20:55 min_cpu_load
-rw-rw-rw- root root 4096 2014-02-12 20:55 ramp_down_step
-rw-rw-rw- root root 4096 2014-02-12 20:55 ramp_up_step
-rw-rw-rw- root root 4096 2014-02-12 20:55 sample_rate_jiffies
-rw-rw-rw- root root 4096 2014-02-12 20:55 sleep_ideal_freq
-rw-rw-rw- root root 4096 2014-02-12 20:55 sleep_wakeup_freq
-rw-rw-rw- root root 4096 2014-02-12 20:55 up_rate_us
root@maguro:/sys/devices/system/cpu/cpufreq/smartass #

But it takes no sense. all files are writable :-S

Brilliant. If you try to set any tunable via shell (ADB), tunables are sticked, but shell hangs...
[Samsung Galaxy Nexus] bsmitty83:
Thanks I found the color control, its set to false now :good:
[Samsung Galaxy Nexus] osm0sis:
It shouldn't really matter whether they're root or system since they're 666 perms. :confused:

I think smartass is just a piece of sh*t.
[Samsung Galaxy Nexus] vfmmeo:
Correct. But maybe is a clue.

More funny is the shell hang thing :D
[Samsung Galaxy Nexus] Hetalk:
Well, just finished reading the last few (a lot, in fact) pages, just got to report that the latest dirty sr kernel (from the op) has been working pretty well with latest omnimetal

Also, I see the ramdisk version and I'm gonna try it out on omnimetal, as of now.

Keep up the good work guys :good:

[MENTION=4244313]MBQ_[/MENTION] All the best on your app development. Let me know if you want me to test it.

Edit: Hate to say this, but I'm missing the inbuilt touchwake already. [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] blukutuxxx:
Edit: submit button touched accidentally, sorry:banghead:
[Samsung Galaxy Nexus] Nephilim:
I prefer Interactive but I'm trying to apease everyone lol.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] metalspring:
Btw, [MENTION=4608636]bsmitty83[/MENTION], I've been trying to get a linaro 4.7 toolchain built that is truly optimized for the gnex ;)

Finally got one to compile, have to test now lol

The main issues with the 4.7 toolchain [MENTION=3685904]ak[/MENTION] linked to is its set to be optimized for kernel version 3.4 and hard float

the cortex-a9 and neon optimizations it had are good for our device though obviously, but we are still (sadly) stuck on linux kernel 3.0.101 and hard float doesnt do anything, also this means the toolchain can always be up to date :)
[Samsung Galaxy Nexus] oli20021978:
Thank God the first kernel in 4.4 with working tcm ( the free one too)

Thank you for your work and the community for the support.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] AJ Bryant:
I get random lock screen freezes when using Bluetooth devices to listen to music and using the Touch Wake feature. It usually happens when I use the volume controls to change the song then use the touch wake feature to wake my device. I can't type in my PIN or make the Power Menu show up. I eventually have to take the battery out. It could be a problem with the music player too; I'm not 100% sure.
[Samsung Galaxy Nexus] Shambola:
Any news about wifi / Hotspot issue? I hate to be on the "latest -1" version! (I don't want to be an "official supporter of the vintage release" lol)
[Samsung Galaxy Nexus] poo706:
So, I'm confused. If we're going with neph's settings, should target_loads for interactive ideally be 85 or that long string that trickster represents as 0?

[poo]
[Samsung Galaxy Nexus] vfmmeo:
I set target_loads to 85. But look at me: I'm a junior member lol.
[Samsung Galaxy Nexus] Nephilim:
Did you read the OP on my thread? If you can set it, set it to 80 or 85. If it's stuck at 0 don't worry. ;)

It's a strange bug.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] poo706:
Apparently I didn't read well enough. Thanks for the clarification. Although you're dirtyv settings imply that you should go with 0, else 85.

[poo]
[Samsung Galaxy Nexus] Nephilim:
Only because more people seem to be stuck on 0 than are able to change it. ;)

No big deal. :)

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] David 617:
Is there any way to get WiFi Tether to work?

(Is it gonna be fixed in the future, or is this gonna be a side affect of new WiFi drivers. )
[Samsung Galaxy Nexus] juju2011:
I can tether just fine one 2.10 try it and see, it might work for you.
[Samsung Galaxy Nexus] Rushead:
Are you sure it's not a rom issue?

Sent from a flashead cracker.
[Samsung Galaxy Nexus] bsmitty83:
Which 2.10 ? Cause smittyV has the old drivers still I believe . I built that one late at night on 2/9 , and the dirtyV's late 2/10 .
[Samsung Galaxy Nexus] David 617:
Haven't flashed it yet. I think I saw it in the OP or somewhere.
[Samsung Galaxy Nexus] juju2011:
I'm using the the ramdisk sr version
[Samsung Galaxy Nexus] dbt816:
It's a kernel issue. I'm running Vanir nightlies and it works fine with the Vanir kernel...load DirtyV and it doesn't. Same on a couple of other ROMs. Apparently it couldn't be fixed until there was a working ramdisk. Soon hopefully!
[Samsung Galaxy Nexus] robbnsade:
What do you have your settings set to? I can't get it to work for the life of me :confused: PM if needed ... Don't want to get too far off track

Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
[Samsung Galaxy Nexus] juju2011:
Bah I think it was because I've been dirty flashing kernel updates for a while. I just clean installed latest carbon nightly with ramdiskSR and it isn't working anymore

Will try flashing Smitty v and see if it works then dirty flash over and it still works
[Samsung Galaxy Nexus] osm0sis:
Broken Wi-Fi tether is a 3.4 backported Wi-Fi driver issue. Always has been. Smitty mentioned there might be a ramdisk fix? I don't know what it is though.
[Samsung Galaxy Nexus] ak:
For a working tether i think is necessary a modification to rom side if dirtyV have the latest bcmdhd. ;)
[Samsung Galaxy Nexus] metalspring:
I think that would be updating the hostapd file? I just remember someone working on it before needing to update the hostapd file for everything to work
[Samsung Galaxy Nexus] metalspring:
[MENTION=4608636]bsmitty83[/MENTION], [MENTION=3685904]ak[/MENTION] I was just going through the menuconfig for the latest dirtyv-sr kernel source and noticed this isnt turned on in the config-

Device Drivers > Misc devices > Android kernel panic diagnostics driver

I dont think its really important but I'm just curious, would that be the option to enable last_kmsg for any kernel related random reboots?
[Samsung Galaxy Nexus] Charmacas:
[MENTION=1143630]osmosis[/MENTION] with your newest ramdisk modification of the DirtyV kernel I've got a lot of stutters. I am back to normal DirtyV and everything's fine.
[Samsung Galaxy Nexus] bsmitty83:
No I don't have a fix ATM , aosp linked a fix a while ago but not sure I can use it I might revert for now and maybe try 3.1 or something .
[Samsung Galaxy Nexus] sajty:
Good idea.Broken tethering is quite a pain...:)
[Samsung Galaxy Nexus] metalspring:
I know someone worked on updating the wifi driver to the latest upstream aosp version (3.4?) and had a fix for the wifi tethering over in the 3.4 kernel development thread

Edit- [MENTION=4608636]bsmitty83[/MENTION] here http://xdaforums.com/showthread.php?p=47947668&highlight=wifi#post47947668

Kind of funny but you posted on there right after that post too lol
[Samsung Galaxy Nexus] bsmitty83:
Haha sweet I forgot about that . I'll try it out today . I just set up teamviewer on my phone so I can compile away from home
[Samsung Galaxy Nexus] metalspring:
Wait say what??? Compile away from home? Now THAT sounds like something I could use between compiling 3 roms, various kernels and now toolchains (which btw, I'm going to test the kernel I made with my custom dirtyv gnex optimized toolchain now lol)

Can you throw me a link to that teamviewer thing?
[Samsung Galaxy Nexus] bsmitty83:
Team viewer on play store . follow the link on the site to download the .deb on Linux , and connect . its crazy easy

https://play.google.com/store/apps/details?id=com.teamviewer.teamviewer.market.mobile

Sent from my SCH-I605
[Samsung Galaxy Nexus] Shambola:
Especially if you have a wifi-only tablet... ;)
[Samsung Galaxy Nexus] metalspring:
Hey, it works lol. Little tough to navigate, but works well enough, great find

Also, I finally got to test my custom toolchain and the kernel compiled with it and it works :)

Still testing to see if theres any performance increase or not, but would you want a copy of the toolchain I made and/or how to make it?

(its fairly easy to make btw, and *should* be perfectly optimized for dirtyv since I used your kernel source to make it lol)
[Samsung Galaxy Nexus] David 617:
You can also use teamviewer from a desktop client or web browser (if you can't run the client for some reason.)

login.teamviewer.com

teamviewer.com
[Samsung Galaxy Nexus] bsmitty83:
You know I do :D
[Samsung Galaxy Nexus] fauntelroy:
You guys sure are crazy (in the good ways though :D)

Such dedication very rare in here, but don't make this disturbed your real life to much guys,

Salute for you :thumbup:
[Samsung Galaxy Nexus] DevVorteX:
I'm guessing team view is more user friendly, but what's wrong with good ol ssh? :)

Install screen, so you're session persists on logout, and you can build all day from any where.
[Samsung Galaxy Nexus] poo706:
+1 Although, tmux instead of screen. Connectbot is a great SSH terminal for Android. For remote desktop, I was already running VNC servers on my various PCs, and was using the free android-vnc-viewer. It got the job done, but was a little clunky. Then I picked up Jump Desktop from Amazon's free app of the day, normally $10. Holy crap, you want to talk about a vnc client done right!

[poo]
[Samsung Galaxy Nexus] osm0sis:
I noticed this at first too. I think it's the governor permissions fixer script. It seems to settle down after a few minutes. I guess I'll remove it again.. :confused:
[Samsung Galaxy Nexus] vfmmeo:
And if you are crazy enough to compile under Windows, you can also install openssh 4Win in order to work with a Windows shell via ssh.
[Samsung Galaxy Nexus] poo706:
Nah, straight up cygwin is my MO.

[poo]
[Samsung Galaxy Nexus] metalspring:
Ubuntu beats windows hands down lol, although I prefer openSUSE myself (too bad there are never any guides to building android on that though, so I'm left with ubuntu)
[Samsung Galaxy Nexus] vfmmeo:
Same here. My box runs Mageia. If you tink openSUSE has lack of guides, try with mageia. I must set up a Debian KVM virtual machine to make this stuff work.
[Samsung Galaxy Nexus] ray1234:
A noob question - will this kernal work with 4.3 roms?
[Samsung Galaxy Nexus] vfmmeo:
AFAIK it's a 4.4-only kernel.
[Samsung Galaxy Nexus] Sik-1:
Yes but you have to use the any-kernel format zip
[Samsung Galaxy Nexus] Shambola:
## START OT

Me too (as a client). For a certain period I even paid license for SLED. Not bad also Mint....

(server side i use RHEL. My job is to administer a farm of >100 JBoss servers on RHEL)

## STOP OT
[Samsung Galaxy Nexus] bsmitty83:
ok if anyone wants to try this rom out , i changed some things to try to get wifi AP working with 3.4 drivers

so if you flash this to test , make sure you flash my latest kernel with newer drivers after you flash rom

its vanir stock kernel , vanir 2-13 rom

https://www.dropbox.com/s/z3ds5hk487vsbdj/vanir_toro_4.4.2.021314.zip
[Samsung Galaxy Nexus] poo706:
Oh for compiling, yes, Ubuntu all the way. I was just saying I liked cygwin best for implementing SSH on Windows. Arch is my preferred distro when not building android.

[poo]
[Samsung Galaxy Nexus] metalspring:
Btw [MENTION=3685904]ak[/MENTION] [MENTION=4608636]bsmitty83[/MENTION], [MENTION=2838735]aosp[/MENTION], which of these do you think works better for the gnex?

mfpu=neon

mfpu=vfp3

Everything I've been able to find seems to contradict

One thing says neon is actually neon-vfpv3 so it enables both, but then some things say vfpv3 is better or at least neon is pointless????

http://shukra.cedt.iisc.ernet.in/emsys/docs/codesourcery/html/getting-started/sec-armfloat.html

https://wiki.debian.org/ArmHardFloatPort/VfpComparison#NEON

https://lkml.org/lkml/2011/10/3/254
[Samsung Galaxy Nexus] Charmacas:
Did anyone try DirtyV-SR4.1 in comparison to the newest? I still feel it's the fast release so far. :)

Any +1's here?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] qtoo941:
I am omnimetal user and i was using 2/10 super ram version with [MENTION=4544860]osm0sis[/MENTION]'s ramdisk but after some time of using my phone is becoming somehow laggy - i cannot really explain it. So i went back to normal 2/10 DirtyV SR and till now everything is perfect. No lag and my battery life is very good with Interactive/Fiops settings. In my opinion V5 and 2/10 are best versions so far :D
[Samsung Galaxy Nexus] David 617:
Thank you. DLing now.

Should I flash 2-10 from the OP, or the ramdisk one that Osmosis posted a bit back?
[Samsung Galaxy Nexus] sajty:
Now,i did two things:

1) i wrote the script directly at my phone,not copying from Windows

2) i set "sleep" to 75,because Trickster has grace period set to 60

aaaaand...its working!Dont know,which of those 2 things helped,but its working.Thanks for your effort.
[Samsung Galaxy Nexus] osm0sis:
Your script conflicted with Trickster. I'm almost certain. Clear app data next time. Trickster is tricky. ;) :good:
[Samsung Galaxy Nexus] GilGameshn1:
Back you up ...
[Samsung Galaxy Nexus] osm0sis:
PSA: If you flashed the original 2.10 directly over my ramdisk version then you're still using my ramdisk so any difference you think you're seeing is only placebo. :p
[Samsung Galaxy Nexus] David 617:
Lol. Shhh! Don't tell anyone ;)
[Samsung Galaxy Nexus] qtoo941:
Wooow ;o I don't know if its placebo or no but day and a half passed since i cleaned cache and dalvik and flashed original 2/10 kernel and I truly think that my phone is somehow smoother.
[Samsung Galaxy Nexus] Charmacas:
Just to let everyone know: I know the ramdisk thingy and always reflashed the whole rom and after that the kernel again. ;)
[Samsung Galaxy Nexus] qtoo941:
Oh god no, I gotta wait for new version of Omni :D
[Samsung Galaxy Nexus] metalspring:
I think I almost have the optimized kernel toolchain set up perfectly, then I need to add a few more things to my source then I can make new builds :)

Btw, if I'm right about soft float vs softvfp then softvfp should always be used since it's compatible with things that need soft float and allows for mpfu optimization (like what our gnex uses mpfu=neon), soft float actually disables any mpfu optimization

Does that sound about right?
[Samsung Galaxy Nexus] milojoseph:
off topic has anyone tried the qualcomm dalvik optimization on their phone??/
[Samsung Galaxy Nexus] Castro27:
I'm new to this kernel so I'm sorry if this's been asked before (I've also searched it but no luck). Is fastchaging working? It's enabled on trickster but android shows that it's charging through USB. Is this normal?
[Samsung Galaxy Nexus] poo706:
I used it for a while. Unscientifically speaking, it didn't seem to make that big of a difference.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
Yes all is well , you now get to do both . its working
[Samsung Galaxy Nexus] milojoseph:
Its working... bsmitty did black magic on the kernel to allow it to fast charge your phone while connecting to the computer. RARE

---------- Post added at 04:46 PM ---------- Previous post was at 04:45 PM ----------

Ok ok.... thanks.
[Samsung Galaxy Nexus] Nephilim:
osm0sis, I would just like to chime in and say that the most recent ramdisk version of the DirtyV SR kernel has caused no lags or any other issues for me whatsoever. It is running perfect. This also includes WiFi and 4G/LTE.

....again, no issues at all. ;)
[Samsung Galaxy Nexus] piterdemon:
I dont know why but with You setting i have big battery drain on 2g with disabled data connection, no apps draining battery, just nothing doing with phone and battery drain is high

Wytapatano z Galaxy Nexus CM11
[Samsung Galaxy Nexus] Nephilim:
Have you been using them by "set on boot" since v6? Try going into settings/app/trickster mod, then wipe data and reboot. After that manually re-enter my settings, that may clear up the problem. I am getting the same battery and performance I always have so I don't really understand some of the people that are having battery drain issues.

I believe you guys, just don't really know what the cause could be.

I'll help in whatever way I am able to though. ;)
[Samsung Galaxy Nexus] metalspring:
I must be missing it somewhere but where is the version with osm0sis's ramdisk?
[Samsung Galaxy Nexus] Nephilim:
I don't remember which page it's on but it's the "cwm DirtyV SR 2/10 ramdisk" here in my Drive:

https://drive.google.com/folderview?id=0B_HqOdvKZoQheGJYMlpjZmZTT0k&usp=sharing

---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------

The one upside to being on Verizon is that I have not even seen 2G since I got my Gnex, I live in a pretty big city so I barely even see 3G. :p
[Samsung Galaxy Nexus] piterdemon:
I live in Gdańsk in Poland (~500 thousend ppl) there is no 3G problem to avoid it but on 2G i always have full signal

Wytapatano z Galaxy Nexus CM11
[Samsung Galaxy Nexus] qtoo941:
http://xdaforums.com/showpost.php?p=50225237&postcount=2839
[Samsung Galaxy Nexus] bsmitty83:
Working on f2fs at the moment , waiting for the weekend to mess with dirtyV . priority on WiFi .
[Samsung Galaxy Nexus] adoboyo:
I wanna flash 2/10 with the latest liquid build.

I thought I read that 2/10 had some things clicked off that should be on, a bunch of pages back lol. Is this true or everything good to go from the start?
[Samsung Galaxy Nexus] Nephilim:
I'm running the 2/10 DirtyV SR with included ramdisk on the new 2/13 LiquidSmooth and it's flying, running really great!
[Samsung Galaxy Nexus] milojoseph:
i feel like im bothering people... but how come when i set BLX to 98% it wont charge past 98% to 100%. Or is that the outcome because when i set it on other kernel it would charge past Blx settings (98%) to a full 100%.....I wiped battery stats same problem.
[Samsung Galaxy Nexus] Nephilim:
I can confirm that I get 100% charge with Battery Life Extender set to 98, it should not affect the battery charging to full capacity because it does not regulate the battery life, it is merely an extender modification.

How long have you had the battery? How often do you charge and have you tried removing the charger once it hits 98% and then re-attaching it to see if it goes to 100% after awhile?

Also, don't feel like you are bothering anyone, if you are asking legitimate questions, which these are, and you are here to learn then you are not bothering anyone, you are doing what the site is meant for.... Learning.
[Samsung Galaxy Nexus] adoboyo:
Good to know, thank you. I can flash and not have to worry about settings?
[Samsung Galaxy Nexus] Kustaa:
Read this, it may help

http://www.androidpolice.com/2010/1...bump-charging-and-inconsistent-battery-drain/

Anyway, you shouldn't worry about it.
[Samsung Galaxy Nexus] Nephilim:
The new build has fully working Development Options once again, so ART works again as well.

There are a few bugs.

1. If you want to use PIE you must do a clean flash.

2. Halo is completely borked, if you use it as I do, just turn it off for this build and wait it out until the next.

If you do not care about using PIE don't worry about doing a clean flash, save time and dirty flash, I've had no issues.

Also, anyone using Google Dialer, you no longer need to. The included Dialer in LiquidSmooth is based on the Omni Dialer so it has both business search as well as business caller-id. Basically this means, no more annoying call wake-lag when you get a phone call. :)

P.S. if business search does not work properly for you upon flashing this build go into the Dialer app settings and toggle both the business look-up options off and then back on. :)

---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------

Nice find. ;)
[Samsung Galaxy Nexus] milojoseph:
Ok i left it over night to see if it would go past 98% and it didnt. and i removed charger, and recharge still the same. And i turned off the phone to charge it while its off and it said 98%.

---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------

cool i will read thx
[Samsung Galaxy Nexus] Nephilim:
Unfortunately something other than Battery Life Extender is causing this situation. Not sure what it could be though.
[Samsung Galaxy Nexus] midnightdevil66:
Will touch wake make a comeback? I love that feature.
[Samsung Galaxy Nexus] michierusama:
Mine charges 100% in external and USB charging. I wont recommend leaving the phone charging overnight.
[Samsung Galaxy Nexus] qtoo941:
[MENTION=2853378]Nephilim[/MENTION], mate i would like to ask you, why you have left in your settings 98 in battery life extender field? Why this is better than 100 ?
[Samsung Galaxy Nexus] Hetalk:
Li-ion batteries do last longer if they're not used at their extremes. So, don't charge till 100% and don't let it go down to 0%.

That's what I read and understood long time back.
[Samsung Galaxy Nexus] Nephilim:
It is more efficiant, keeping it a slight bit down from the full 100 actually improves the battery life I've found. I believe a few others have come to this same conclusion.
[Samsung Galaxy Nexus] poo706:
It had to be removed in order for the touch control module to work. I think more people wanted touch control than touch wake.

[poo]
[Samsung Galaxy Nexus] Nephilim:
It's fine to leave them sit and charge, however you are correct that it's not a good idea to let the battery reach 0, I try not to let mine go below 25% unless I am doing testing.
[Samsung Galaxy Nexus] Kustaa:
Exactly. Touch control + doubletap2wake...who needs a G2? Lol
[Samsung Galaxy Nexus] bsmitty83:
I'm just gonna switch back to the old WiFi drivers for now , I can't see a benefit when 3.0 bcmdhd works fine . I'd rather have it fully working .