yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Thanks buddy. :) I'm still waiting to hear what Franco thinks on the matter. That and adding the custom launcher lmk exclusion to the f.Ku boot service would clean up that script nicely. :cowboy:

No need to fastboot if you have f.Ku. ;)

Read the second half of this post:

http://xdaforums.com/showpost.php?p=34400301&postcount=33112
[Samsung Galaxy Nexus] Savant:
Or trickster mod and do the something and put it in a kernel backup folder and click restore and reboot. Profit..
[Samsung Galaxy Nexus] easyrider77:
wasn't sure how to delte the post, so I just put this.

I posted in the wrong spot sorry. Delete it if needed
[Samsung Galaxy Nexus] Savant:
It happens so don't worry about it.
[Samsung Galaxy Nexus] allcity187:
I was on tiny kernel, just installed r318 wifi speeds are much faster, I'm on wpa. Thanks Franco, you are the man, glad to see you making kernels for 4.2.
[Samsung Galaxy Nexus] hshaikh:
I'm running r318 with rooted odexed 4.2 ROM. I noticed the launcher stutters so etimes when going from appdrawer to home. Any one else see this
[Samsung Galaxy Nexus] Savant:
I realize when you get sods now its when the phone overheats. Screen goes blank now and doesn't want to wake up or reboot like it used too.

---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------

Try nova because stock launcher has problems ATM.
[Samsung Galaxy Nexus] momomok:
Just asking out of curiosity, does the new "Wi-Fi optimisation" option in 4.2 requires kernel support? or is it merely a software stuff?
[Samsung Galaxy Nexus] bboran:
i cant fastboot flash the r318 it gives this error;
[Samsung Galaxy Nexus] hshaikh:
All 4.2 stock launchers have issues?
[Samsung Galaxy Nexus] jeetS:
Sweet, can't wait. Im too lazy to learn to fasboot

love your kernels:good:
[Samsung Galaxy Nexus] Savant:
From the posts I seen it depends on the ROM. People apparently don't have lag on bigxies ROM but mixed results so who knows.
[Samsung Galaxy Nexus] JBNex:
Thank you:)
[Samsung Galaxy Nexus] joaquinf:
Wow the new drivers are really good. I'm having 3 signal bars on my room where I normally got 1. Huge improvement Francisco.

Thanks :)
[Samsung Galaxy Nexus] shawnaye:
Quick question. R318 can't be used with 4.1.2 right?

Missing those 3.4 wifi drivers. Not really wanting to update to 4.2 yet cause there's still bugs laying around.
[Samsung Galaxy Nexus] Savant:
No you can't use it until your on 4.2.
[Samsung Galaxy Nexus] osm0sis:
Yup I have that micro lag in that exact situation. Only lag on the whole thing though, much better than stock kernel that way. The slight jitter isn't worth downgrading over.

Good question! Been wondering about that option myself. I wonder if it makes the cell radio low power when connected, or makes wifi low power when the connection is idle. Those were my two guesses.
[Samsung Galaxy Nexus] jsyl:
Random reboots/crashes on r318
[Samsung Galaxy Nexus] kyokeun1234:
Could you be more detailed? This can happen because of various reason.
[Samsung Galaxy Nexus] scarmon25:
So far running 318 on MMuzzys ToroPlus 4.2 and crazy enough I've seen a decrease in battery consumption. I would have figured the raised GPU and CPU would have caused it to drain quicker. But so far it is running cooler then it was and battery is slowing down. Even when I'm on 3g instead of WiFi. So whatever you're doing Franco it is in the right direction.
[Samsung Galaxy Nexus] nuwan32:
Same situation for me actually, still on 4.1.2 and waiting for a stable release of paranoid android and would love to have the new drivers again, but ah well, is Franco's choice to continue with 4.2 only. don't wanna bother him for something this little.
[Samsung Galaxy Nexus] jsyl:
I'm not sure what the cause is
[Samsung Galaxy Nexus] gianton:
Running rock stable here.
[Samsung Galaxy Nexus] scarmon25:
One thing I have found on the 4.2 318. If I go into the gamma adjust and try and turn the green value down it wigs out and turns the whole screen green. I can adjust blue and red just fine. I tried this without any contrast or other color settings being used. It didn't matter. It still happened after resetting data in the Franco Kernel Updater app. Not sure what to make of it to be honest.
[Samsung Galaxy Nexus] rodnar77:
Running 318...

WiFi great on corporate WiFi and no problems at home either.

Great signal too.. Thanks again
[Samsung Galaxy Nexus] mohaimed:
how do i flash the new 318 for 4.2? zip file would have been much more easier.
[Samsung Galaxy Nexus] momomok:
1. Fastboot flash boot boot-r318.img

2. Put the downloaded .img file into kernel_backup folder and use the restore feature of FKU to flash it

Sent from my Nexus Prime
[Samsung Galaxy Nexus] IgnorantNerd:
Very happy with my WiFi strength on 318. I don't think I've ever seen full signal bars before this version. Great work Franco!
[Samsung Galaxy Nexus] franciscofranco:
Thats how green always worked on this panel, sorry theres nothing I that I know to fix it, thats how it is.
[Samsung Galaxy Nexus] vivmar:
Is this the correct way for flash this kernel via adb?

fastboot flash boot boot.img

thx
[Samsung Galaxy Nexus] Culex316:
No, that's a fastboot command

with adb, you first type in "reboot bootloader" and then when you're at the screen with the android lying on it's back and it's stomach open, you type in "fastboot flash boot boot.img (or however the kernel file is called)"
[Samsung Galaxy Nexus] syncopy:
Haha! :good:
[Samsung Galaxy Nexus] malaroth:
The strength of the wifi signal is definitely superior. I can access my neighbors apartment which is 75 yards or more away. Smooth page transitions no noticeable lag or stutters. If I can make it to my dad's tomorrow I'll try out all wifi bands and encryption.
[Samsung Galaxy Nexus] RayGarden:
Running Nova Launcher Prime with MoDaCo JR8 (4.2) without any stuttering. Using the Stock Kernel from Google that came with this ROM.
[Samsung Galaxy Nexus] malaroth:
Using standard apex launcher no problems
[Samsung Galaxy Nexus] mDroidd:
Rock stable and fast as butter - just as always.

Thanks for the 4.2 update - previous kernels really were ****.

Sent from my Galaxy Nexus running Android 4.2 JB
[Samsung Galaxy Nexus] splus:
Wifi tethering is not working on r318.

That's a bummer because everything else works real good... Battery life is so much better than any kernel on JB 4.1.

Reverting to previous version because I really need wifi tethering.

Stock bigxie JB 4.2 rom, btw.
[Samsung Galaxy Nexus] sago62:
does anyone have a link for R318 flash cwm? thanks
[Samsung Galaxy Nexus] aR_ChRiS:
You're like the 1 millionth person to have asked this, and no, Franco will not release zip versions for testing kernels, so LEARN HOW TO FASTBOOT/USE THE APP TO FLASH THE KERNEL.
[Samsung Galaxy Nexus] Godra:
Is NFS MW lag solved in 4.2 kernel versions?
[Samsung Galaxy Nexus] kitecarl:
I have fairly consistent music stutter on r318, for example when listening to Spotify with screen on browsing the web, Tapatalk or JustReader. The r315 release seemed a bit smoother to me (highly unscientific!). Cheers
[Samsung Galaxy Nexus] chrisgtl:
@franco

#318 is working flawless on my WPA2 network at home but

will not

connect to our WEP wifi at work.
[Samsung Galaxy Nexus] joliv:
There it is...

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/

---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/

---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------

R318... some magic started to happen.

Thanks FF.

---------- Post added at 10:03 AM ---------- Previous post was at 10:00 AM ----------

Hint: Flashable with FF updater - just move downloaded kernel to ...kernel_backups.
[Samsung Galaxy Nexus] Edrill:
r318 uses newer WIFI drivers which are known to be WEP-unfriendly.
[Samsung Galaxy Nexus] The Gingerbread Man:
Can you change your works security type on their WiFi routers? I don't want to loose these WiFi drivers again :p

Sent from my Galaxy Nexus

---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------

Francos app now pushed to 8.0.8 in play store :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] exmatproton:
Hey, with the newest FKU app, the dutch language is not properly translated. It is translating to the Czech language. Cannot read it... .. .
[Samsung Galaxy Nexus] safendi:
Wifi work, is perfect

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] chrisgtl:
Unfortunately not no - it isn't possible for us to move onto WPA yet as some of our laboratory equipment can only run on WEP network.

In all honesty I have very good data signal at work so wouldn't be too fussed about not having wifi.
[Samsung Galaxy Nexus] dehein:
Can some more people confirm that wifi tethering is not working? Or USB tethering?

Still can't believe that people still use wep to secure wifi. In some scenarios it seems the cheapest solution. But it still would take only 5 minutes of preparation and 4 hours of waiting to know the password.
[Samsung Galaxy Nexus] CADude:
I wouldn't even trust using my work's wifi for personal stuff on my phone anyway...

I can't wait to use these Wifi drivers since my home has a good signal but there's some Wifi deadspots using the Galaxy Nexus but not my laptop.
[Samsung Galaxy Nexus] dehein:
Me too. But I'm still waiting for pa to come out stable
[Samsung Galaxy Nexus] ak:
With the new drivers wifi tethering doesn't work. :good:
[Samsung Galaxy Nexus] sergeroyal:
TWRP?

Can I flash it using TWRP ?
[Samsung Galaxy Nexus] Khizar:
how do you expect to flash a img file using twrp? the ffu app way that joliv told you is the simplest way to flash the kernel
[Samsung Galaxy Nexus] sergeroyal:
Well thought that by replacing the img file from an older version (like r300) will do ... would'nt it ?
[Samsung Galaxy Nexus] Khizar:
hmm.. i would just flash the img file if i were you, there must be reason if franco decided to make them img format instead of zip ;)
[Samsung Galaxy Nexus] sergeroyal:
Yup well just was a bit lazy to open the nexus toolkit ... nwy flashed it using fastboot and working fine . Thanks
[Samsung Galaxy Nexus] chrisgtl:
My phone is for work lol.
[Samsung Galaxy Nexus] malaroth:
For a Lil more info using wifi tether for root users by Mueller buxton and lemon off play store in the log start ap and configure ap fail where everything else is green
[Samsung Galaxy Nexus] Khrushy:
It works. That's what I tend to do because it means I don't need to be at my PC with ADB on it, and I can download straight to the phone to flash.

The reason Franco doesn't release zip files is he wants people who use clearly labelled TEST kernels to at least have the smarts to install them via a slightly roundabout route. If you can't handle that, you shouldn't be testing bleeding edge kernels :P
[Samsung Galaxy Nexus] gianton:
WiFi tethering is not working on r318 here too.
[Samsung Galaxy Nexus] tetrakinitis:
+1. r318

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] The Gingerbread Man:
Ssshhhhhh we want to keep these drivers

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] marshy73:
Hi Franco

I'm not implying its a kernel issue but just seeking advice.

I pushed in 315 and encountered app installation/update error on playstore. Not knowing the cause, tried clearing all cache and fixing permission without success. So i flashed back stock 4.2 kernel. Problem solved.

318 came and i pushed in yet again i encounter this app installation/update error. You mentioned its a userspace issue. Apologies but I'm not familiar with this matter. I've not yet flashed back stock 4.2 kernel again but hope to seek your advise on this matter.

Thanks...
[Samsung Galaxy Nexus] Langduscher:
Don't have much time so bear with me... is r318 compatible with 4.1.2?:)
[Samsung Galaxy Nexus] malaroth:
No. 4.2 only
[Samsung Galaxy Nexus] gianton:
LOL, yes definitely new wifi drivers are like day and night, but as this is a test build it's wise to mention what's working and not.
[Samsung Galaxy Nexus] CheesieOnion:
On r315 I had problems with USB. If the screen got locked, the USB connection dissapeared, but that's solved now. Wi-Fi works fine at my home with WPA2 PSK security and it also works good on school wich uses WPA/WPA2 PSK.
[Samsung Galaxy Nexus] osm0sis:
How did you flash it? Did you use some moron's zip? The faulty sdcard binary is my guess here. This is why you don't use zips from older versions people.

---------- Post added at 08:37 AM ---------- Previous post was at 08:36 AM ----------

Nothing is simpler than using Franco's app to flash it. It's been explained a hundred times in the last 20 pages.
[Samsung Galaxy Nexus] marshy73:
For 318, i followed some advice here to place the .img file into the backup kernel folder. Then do a kernel restore from within FKU app.
[Samsung Galaxy Nexus] osm0sis:
But you used a zip for 315 or before? The sdcard binary is a system file so it's a one-shot deal. Once it's replaced it's replaced.
[Samsung Galaxy Nexus] jsminnis:
For people not willing to read back and wondering how to flash via fastboot Here ya go.

Download boot.img

Boot phone into bootloader

Plug phone into computer

Open a cmd window where the boot.img is located

Enter this code into cmd window: fastboot devices (to make sure you have a connection between phone and computer)

Then this code: fastboot flash boot boot-r318.img (or the name of the boot.img you have)

* for this to work you must have working adb and fastboot intstalled on your computer.
[Samsung Galaxy Nexus] marshy73:
Well yes. 315 was a zip.

Is there a way to resolve this to be able to use Franco Kernel?
[Samsung Galaxy Nexus] jsminnis:
also, is it just me or is fsync disabled by default, can't this be dangerous. Otherwise, wifi works good here on 318.

Gotta say, I was starting to not like the rom I was on because of the lag, franco kernel took all the lag away, So Snappy now. Thank you Franco.
[Samsung Galaxy Nexus] malaroth:
Simply placing r318-boot.img into your kernel_backup folder let's Franco updater see the file as a backup. Choose restore backup of said file "flashes" 318.
[Samsung Galaxy Nexus] leontine:
+1

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Astug:
+1
[Samsung Galaxy Nexus] schukje:
+1

grtz from holland
[Samsung Galaxy Nexus] osm0sis:
Yes. So it's your fault since we have repeatedly (seriously, like 4 times a day) been saying not to do that for this very reason:

Even though I said I'd refuse, I'm feeling kind as **** today, so I'll knock another stock sdcard cwm zip up when I have the chance. ;)
[Samsung Galaxy Nexus] lovelymobile:
Hi, I installed the kernel R318 and I can not more 'to connect to the wifi network that is secured with WEP.

With the release of R315 and R313 worked fine.

Congratulations for your work

greetings

Simone
[Samsung Galaxy Nexus] G-DannY:
+1. Lost quite whole day trying to connect to a WEP wifi, now realized that the problem is the security thanks to this report.
[Samsung Galaxy Nexus] six_dfx:
Speaking about this, it would be a really nice feature if FKU could make a backup of the stock sdcard binary, power.tuna.so and anything it touches in /system, so people like me who like to run stock ROM could reverse to the stock files in order to use the official OTA without trying & copying from the factory image every time an assert fails in the update.
[Samsung Galaxy Nexus] klobkelosh:
Same here, wifi hot spot broken on r318
[Samsung Galaxy Nexus] teniente_dan:
Is there any way to play gta iii using this kernel on 4.2?

I'd try the zip that is on the first post but ir didn't work at all and i had to do a full wipe to be able to use the phone again

Thanks

Enviado desde mi Galaxy Nexus usando Tapatalk 2
[Samsung Galaxy Nexus] Savant:
The new WiFi driver isn't compatible with wep its been mentioned for a few pages now.
[Samsung Galaxy Nexus] hshaikh:
a couple of us have noticed micro lag in the 4.2 launcher. is it possible to fix this is future builds
[Samsung Galaxy Nexus] dehein:
Why are you even using wep at work? Is it because of some wifi repeaters?
[Samsung Galaxy Nexus] yellowdie:
Franco, you would release the epic 3.4 drivers when I am spending the weekend at my grandparents house without wifi here... Thanks a lot, you torturer. Lol :silly::eek:
[Samsung Galaxy Nexus] bigfnjoe96:
Changed my router security WPA-2. Wi-Fi is now running. So far everything seems good.

Thanks for all the help & Happy Thanksgiving

Sent from my Nexus running Jellybean
[Samsung Galaxy Nexus] G-DannY:
yes, it's because of repeaters. Also is not a wifi that I can manage to change to wpa.
[Samsung Galaxy Nexus] osm0sis:
Unless you made your own zip/used some other idiot's after we explicitly said not to, sdcard won't get touched for the JB 4.2 kernel. It was only replaced if you installed via a cwm zip that was based on franco's JB 4.1.x kernel or earlier (and you weren't smart enough to remove the sdcard binary).

power.tuna.so is replaced by a script in franco's kernel, and I agree it would be nice if it was backed up. Neither have anything to do with f.Ku though.

It's still early days for the JB 4.2 kernel and franco knows about the issue.
[Samsung Galaxy Nexus] jeetS:
I did this. Had too pull the battery to get the phone to boot but all is working well now :)
[Samsung Galaxy Nexus] osm0sis:
Alright... I can barely even explain this again...

PSA: DO NOT FLASH OLD FRANCO CWM ZIPS WITH THE NEW KERNEL - THE SDCARD FILE INSIDE THE ZIP WILL BREAK JB 4.2

If you somehow did this to yourself despite all previous warnings and countless reexplanations, you must extract the stock JOP40C/D sdcard binary from the yakju/takju factory image's system.img (instructions at the top of this post) and put it in /system/bin/. That should fix whatever weird sdcard problems you're having with the Play Store or whatever since you failed to follow directions. :good:

Also here is a recovery flashable zip. This is for people running stock ROM, and will install the stock power.tuna.so, but as power.tuna.so.fkbak so that you have something to easily go back to in order to meet the asserts (file checks) when an OTA drops down the line. If you are not on stock ROM you do not need this file. :good:

To all those smart enough to follow directions and read back a few pages on a regular basis: I apologize to your eyes. :p

Edit: r325+ has my script to backup the stock power.tuna.so (also to .fkbak) before replacing it, so if you use stock ROM and used f.K builds before r325 then you should also extract power.tuna.so from stock, and use it to replace power.tuna.so.fkbak since pre-r325 already replaced the stock one, thus your backup is incorrect.

[sdcard binary and power.tuna.so attachments replaced with instructions on how to extract them yourself in case anyone still needs them. ]
[Samsung Galaxy Nexus] F_T_B:
WTF... fastboot flash boot inserthefuc*ingkernelnamehere.img and it's done. That's all. It's just as easy to load a new kernel.

PS: OTA updates are overrated. With Android 4.2 that OTA zip file was leaked almost instantly, so why wait to receive it at "random"?
[Samsung Galaxy Nexus] tetrakinitis:
Franco any solution for the nfs most wanted?

Sent from my SmoothCriminal™
[Samsung Galaxy Nexus] osm0sis:
You sir, also need to read back a few pages. ;) But here is a concise explanation:

Some people are terribly reliant on CWM and toolkits, all while having little knowledge of how a CWM zip actually works and never bothering to look inside to see what's there. So they think they're being clever by dropping new kernel boot images into Franco's old zips without realizing that's not the only thing the zip does. Franco's old cwm zips also install an sdcard binary which has been known since day one in this thread to **** up JB 4.2.

As for the OTAs, you're missing something here too. Waiting has nothing to do with it; no matter what way you get the OTA it has to pass the asserts (file checks) coded in the OTA update script. Even if you download and flash it with CWM you have to pass the asserts. They are important since often the OTAs don't include full files, only patches, so original files are needed to make sure the correct data within the files is patched to the updated versions.
[Samsung Galaxy Nexus] aR_ChRiS:
I think this has something to do with the app rather than the kernel itself, since ages ago Franco said that it's the app that reads the kernel, then 'thinks' that we have a high end device to run the top notch graphics.
[Samsung Galaxy Nexus] Mac Boy:
I found the simplest solution was to paste the boot.img file in the kernel backup folder created by Francisco's app. Then you use the restore kernel function in the app.

No fastboot required.;)
[Samsung Galaxy Nexus] six_dfx:
Nope actually I'm still running stock 4.2 kernel and waiting for franco to release the usual nightlies thru FKU ... but I do admire your patience with the rotten zip drama whiners :)

I was talking about the official OTA file, it won't apply after restoring the factory boot.img because either FKU or something in initrd overwrites files in /system, including bin/sdcard, so I just thought it would be nice to have some way in FKU to automatically restore the few touched files in /system to their stock state so the OTA works.
[Samsung Galaxy Nexus] reaper000:
No WiFi tethering here either
[Samsung Galaxy Nexus] hshaikh:
i noticed that when running r315 i was getting 3300 on quadrant, and not on r318 i get just over 3000
[Samsung Galaxy Nexus] osm0sis:
Yup. We're talking about the same thing. :) It's /sbin/fixtunapower.sh replacing power.tuna.so on every boot, as I explained it before, and the sdcard binary from the old franco.Kernel zips. Those are what would make the JZO54K to JOP40C OTA fail, and I'm trying to make sure people are prepared next time. Going forward the sdcard binary won't be included if franco makes zips again in the future, and I'm still hoping franco will include my fix to his script which would create a backup of the power.tuna.so file (to .fkbak) if one didn't already exist. That would at least sort out all the new JB 4.2 users who haven't already moved from stock kernel back to franco, leaving just the early adopters who use stock ROM, who should use my .fkbak zip above.

Yeah, and I'm basically at my wits end with this zip ****. I still love everyone else, but my patience is really being pushed for these newbs who can't read and think they're being clever by ****ing around with the old zips.
[Samsung Galaxy Nexus] F_T_B:
Dear sir,

I'm aware of the SD Card issue, I remember reading about it a while back and I'm fairly certain one of you "big" fellas pointed it out that it screws Android 4.2.

In fact I had that problem as well, which is why I suggested fastboot. It's reliable like a hammer, but not fairly "elegant". I honestly don't know why there are so many questions about CWM or TWRP flashable zips. Fastboot is one of the first things that I learned about with the Nexus.

As for the OTA, simply flashing back an untouched kernel in zip form should do the trick. There are ways to circumvent various limitations...

---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------

**** happens. If Antutu scores are down then you have a better reason to doubt the kernel. Quadrant is a POS, it could give a 10,000 score for a Nexus One...
[Samsung Galaxy Nexus] hshaikh:
ok il switch to antutu from now on
[Samsung Galaxy Nexus] osm0sis:
If you reread my response to you you'll see that "circumventing various limitations" could result in an unworking system since the patches would be applied to non-stock files, and clearly the kernel isn't the only thing being changed (power.tuna.so/sdcard binary) so your solution is incorrect, fastboot or not. Unless you're suggesting fastboot flashing system.img, but I don't think you are.
[Samsung Galaxy Nexus] Kurre:
If you really care about benchmark stuff over the user experience, this might not be the right kernel for you.. :p

Just drop out those apps and enjoy the Franco's magic... :D

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] hotakyi:
Swapping the kernel back and forth for the game is what I'm doing:(