yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] gummie:
That's odd, I just used r300 384MHz and my phone starts to heat up abnormally (real hot at upper left most of the phone when back facing front) when I play NFSMW. The Graphics is astonishing compared to when I use stock CM Kernel or Trinity Kernel w/ 384MHz GPU Clock. Problem is its too laggy, cant stir well due to the extreme reflections now present in the game (somewhat can be compared to SGS3 Graphics).

Edit: Switch back to Trinity 384MHz (latest stable) and all came back to normal again. "Normal" no more SGS3 like Graphics :bummer:
[Samsung Galaxy Nexus] nuwan32:
This problem was started before and still no fix was found. For some reason using Franco kernel causes the game to use higher quality graphics which lag. And the heating is normal specially when gaming, is normal to go up to 70 degrees Celsius and this isn't damaging
[Samsung Galaxy Nexus] gummie:
But I Love that Graphics :puppy eyes:

Thanks! I just got hold of Galaxy Nexus couple of days ago so I was ages late here :D Anyway thanks again, for a while I was frantic and immediately force FCing the game and go somewhere cold at the office just to reboot at recovery and flash anything that I found (Trinity Stable 384MHz). Is that not really damaging? Ill be devastated if my device just give up on me now :crying:
[Samsung Galaxy Nexus] kanded:
It happens to me. Played nfs, suddenly forceclose, also when i tried the temple run.
[Samsung Galaxy Nexus] franciscofranco:
Force closes have nothing to do with the Kernel, its userspace stuff. Something is very wrong in your rom, sorry.
[Samsung Galaxy Nexus] llevo3:
f.Ku 8.0.7 in AndroidPIT
[Samsung Galaxy Nexus] :
+1
[Samsung Galaxy Nexus] nuwan32:
flashing is not damaging and Franco kernel and other kernels have thermal throttling, as long as you don't disable that your phone will automatically shut down if it reaches critical temp. So have fun until then :)
[Samsung Galaxy Nexus] Godra:
My voltages are really high:

192 MHz -1000 mV

384 MHz - 1025 mV

537 MHz - 900 mV

729 MHz - 1150 mV

1036 MHz - 1225 mV

1228 MHz - 1250 mV

1305 MHz - 1275 mV

...

Any ideas? Its kinda weird that 192 MHz slot has higher voltage then 537 MHz, isnt it? Im runnig Minco v5 ROM and I updated franco.kernel to r300 nightly build trough franco app. Thanks in advance
[Samsung Galaxy Nexus] tzyn:
Smartreflex will do the job (undervolt). These values are just the top level where Smartreflex start the calibration. So the real voltage is not so high.
[Samsung Galaxy Nexus] bartolinio:
whether it comes to reduction from 3.86$ to 3.21$? :)
[Samsung Galaxy Nexus] F_T_B:
OK, one thing that I noticed with the latest (315) kernel for Android 4.2.

TricksterMod no longer recognizes the color profile, whereas it did before. Trinity's kernel doesn't have the same issue by the way.
[Samsung Galaxy Nexus] osm0sis:
Reduction "of" $3.86 to $3.21 (ie. from $7.07 regular), OR reduction "from" $3.86 to $3.21 (ie. 54¢ off)?

Either way, ZOMG SAVINGS! :cyclops::victory::laugh:

I do because I like to have Device Monitor working, but it doesn't matter since I put them all below their SR calibrated voltages. :good:
[Samsung Galaxy Nexus] gianton:
Thanks mate
[Samsung Galaxy Nexus] JBNex:
There's a bug with saving and loading color profiles. Mine currently is 135-135-200. But when I save it and load it, to preview the profile and its settings, it displays as 135-135-135. The blue adjustments are off.
[Samsung Galaxy Nexus] malaroth:
Thanks for everything Franco! Do you have a US carrier yet there in Cali? Curious as to how that might affect changes via lte builds

Sourcerized, Milestoned6, just missing the Cheetos and Redbull. http://teamsourcery.com/Images/teambanner.png FTW Keep the Magic alive!!
[Samsung Galaxy Nexus] yellowdie:
Well he's getting the N4, soooooo I think LTE is out... :/ lol
[Samsung Galaxy Nexus] osm0sis:
Speaking of which, Franco, maybe you could fix Device Monitor so that when SR is disabled it just grabs the corresponding voltage from the voltage table instead of showing "0"? Pretty please? :D
[Samsung Galaxy Nexus] joeb3786:
BUT...BUT IT HAS AN LTE CHIP!

how long after he begins pushing kernels for the N4 do you think someone will ask if he can activate it?

Wait... I see he has already begun, and doesn't even have the phone yet!
[Samsung Galaxy Nexus] nuwan32:
it was already reported that the blue takes on the red value. Just hold on I'm sure it'll be fixed very soon :)
[Samsung Galaxy Nexus] zephiK:
It's the radio that would turn lte on. And no one has made a custom radio. Kernel has nothing to do with turning lte on
[Samsung Galaxy Nexus] hshaikh:
I'm not the greatest with phone hacking. I wanted a new kernel for 4.2 since stock seemed kind of laggy. I was using Franco before on 4.1. So I figured out how to put the r 315 and it runs great And fast. I noticed there is no 1.2 GHz. I ussualy don't like to oc or tinker with too many settings. Is this stable and OK on battery life. Or should I go down to 1 ghz
[Samsung Galaxy Nexus] malaroth:
OK sorry for the stupid question .

**edit I was more going towards toro, toroplus etc when I misspoke

Sourcerized, Milestoned6, just missing the Cheetos and Redbull. http://teamsourcery.com/Images/teambanner.png FTW Keep the Magic alive!!
[Samsung Galaxy Nexus] joaquinf:
Read this post regarding that chip
[Samsung Galaxy Nexus] chickentuna:
franco has removed the 1.2 step bec there's just little difference between the voltages of the 2 steps(i think 25mV difference). If i recalled it correctly he said that he would rather run it faster at 1.3ghz instead of 1.2ghz 25mV diff. in voltages won't affect the battery life too much which I agree and perfectly makes sense. Up to you if you're gonna underclock but i suggest you try 1.3ghz first
[Samsung Galaxy Nexus] EDNYLaw:
Franco made the 1.2 slot redundant by using the same voltage for the 1.3 slot. Since the 4460 is actually clocked at 1.5 GHz, running at 1.3 is technically underclocking the processor. Going to 1 GHZ will reduce battery consumption somewhat but you may take a hit on performance. Try both and figure out what works best for your usage and silcon. Certainly you will not damage your device by using the 1.3 slot.
[Samsung Galaxy Nexus] mihkohuy:
Getting error when flash the img in.....
[Samsung Galaxy Nexus] hshaikh:
OK I will try 1.3 for a while. I didn't know it used practically the same voltage as 1.2. So is this change going to be permanent from now on in all future versions
[Samsung Galaxy Nexus] osm0sis:
Yep. That's the idea. Also 512GPU will likely be the only option, since Franco made it so that every device is able to run it, and again voltage difference isn't extreme.
[Samsung Galaxy Nexus] joeb3786:
I'm very well aware of how not-possible it is to "turn LTE on"... I was merely joking about the fact that many users think Franco is a robot phone-god-jesus-superstar that can perform hardware mods on their phone by updating the kernel :D
[Samsung Galaxy Nexus] zephiK:
Hard to tell sarcasm in text :p
[Samsung Galaxy Nexus] pdppdp:
Might sound stupid but I can't figure it out on my own. I'm running 4.2 all stock but rooted. Franco kernel isn't ready for 4.2, right?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] reflexr:
Hm maybe you should read a few pages back. There's a kernel for 4.2 from Franco

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Observe: A folder named JB-4.2 on franco's build site...

minooch.com/franciscofranco/Galaxy%20Nexus/JB/JB-4.2/

What does it all mean!??! :silly:
[Samsung Galaxy Nexus] rodnar77:
thanks for keeping us updated... i am using 315... bigxie 4.2... i leave everything as it comes with stock kernel...

runs smooth and great... long battery...

WIFI and mobile connections have no issues...

thanks again..
[Samsung Galaxy Nexus] hshaikh:
yes i have that issue. thats honestly the only bug i noticed. i know there is that adb thing but i have never used that. so il live with no fast charge until franco makes a mainstream version
[Samsung Galaxy Nexus] franciscofranco:
Here's r318. USB craps on r315 should be fixed. I strongly need Wi-Fi feedback please: http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2/boot-r318.img
[Samsung Galaxy Nexus] mak81:
Hi, how i can unistall franco kernel and replace it with the stock one of 4.1.2??

Thank's a lot
[Samsung Galaxy Nexus] bunnahabhain:
FKU doesn't load my saved color profiles... Is that issue affecting anyone else?

Just purchased BTW. My phone like totally new. Awesome APP! Thanks a ton!
[Samsung Galaxy Nexus] F_T_B:
Just flash the stock kernel with fastboot flash boot boot.img -- boot.img is the name of the stock kernel which you can extract from the factory images posted on Google's site. Or you can search for it on XDA.
[Samsung Galaxy Nexus] duduzinho15:
wifi don't work :(
[Samsung Galaxy Nexus] smelian:
great kernel

is there any problem thats we can control the color with ?

like voodoo or anything els cuz i want change the setting for color but i dont know how?, want easy way
[Samsung Galaxy Nexus] chakra:
Yes Franco's Kernel updater app in the market. Not only will you be supporting the developer of this great kernel, but it has setting to control the kernel including color.

https://market.android.com/details?...t=W251bGwsMSwyLDEsImNvbS5mcmFuY28ua2VybmVsIl0.
[Samsung Galaxy Nexus] franciscofranco:
This made me laugh. Developers work their asses off and people like you want the easy way without working a bit? How about I start to slack and not work too because its the "easy way"? This pissed me off a bit.
[Samsung Galaxy Nexus] smelian:
lool sorry u miss understand me what i mean is there any app to control the color or i need to change the settings from system files

btw some one told me about your app in market and i just bought it you deserve the money for your great work . will try it now
[Samsung Galaxy Nexus] zephiK:
You should really read the changelog before you ask questions,
[Samsung Galaxy Nexus] BrandonPrice31:
I installed SETCPU then read this thread so I uninstalled it. Will my settings from SETCPU stick or I'm fine and they are gone and everything will run as if I didn't have it installed?
[Samsung Galaxy Nexus] johantheolive:
I'm pretty sure setcpu is dependent on the application so if it's uninstalled you should be fine.
[Samsung Galaxy Nexus] nic85:
What s the problem with setcpu?

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] zephiK:
Nothing's wrong with SetCPU. Franco Kernel app has the feature to overclock, set governor. So there isn't really a need for TWO apps that does the same thing as it might interfere with each other.

@BrandonPrice: No you should be fine. Johan is right, it should be dependent on the app. Glad to see that you got root/custom ROM up and running :)
[Samsung Galaxy Nexus] johantheolive:
I had my phone on one night without setcpu and the next with, having a screen off profile limiting the cpu to 350mhz. Both ways I was down 2-3% in the morning.
[Samsung Galaxy Nexus] nic85:
Ok i use setcpu because i haven t franco's app yet

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] deezid:
Don't use too high values, black clipping (which produces banding, artifacts in images/videos etc.) will be even worse... :(
[Samsung Galaxy Nexus] BrandonPrice31:
The only thing I wish now would be for the ability to undervolt etc.

Also, do you guys have any recommendations of any apps that are root dependendent that I might want to have a look at?
[Samsung Galaxy Nexus] Thracks:
The kernel is already undervolted, and Franco does not want to deal with all the support issues that crop up when you give userland access to undervolting.

Imoseyon and Faux both have great, UV-ready kernels if that's your bag.
[Samsung Galaxy Nexus] BrandonPrice31:
Makes sense!

Do you have any recommendations of apps that are root required that I can get from the 'market. (New to the scene)
[Samsung Galaxy Nexus] Redflea:
The one limitation of the FK app for over/underclocking is that you have to use it to set an init.d file that only takes affect after reboot...if you want to change clock settings in a session w/out rebooting or having to have them set on boot, you'll need something like SetCPU.
[Samsung Galaxy Nexus] zephiK:
http://xdaforums.com/showthread.php?t=1441216&page=3
[Samsung Galaxy Nexus] Redflea:
We've been asked by Franco and mods to stay on topic - discuss Franco's kernel and his app, not other root apps, radios, bootloaders, etc.
[Samsung Galaxy Nexus] franciscofranco:
That will be added in the next version.
[Samsung Galaxy Nexus] Sayan1987:
Reading through changelog i don't understand if kernel is set by default on hotplug on or hotplug off..

And in any case,which is better?
[Samsung Galaxy Nexus] franciscofranco:
Mine is connected just fine to my company's Wi-Fi network. I need more info than just "wifis nu vorks" :)
[Samsung Galaxy Nexus] osm0sis:
You need to explain. Saying it doesn't work is useless. It works fine for me on 2.4GHz, WPA2-TKIP at work, so something is different for you. What band, freq range, and security?
[Samsung Galaxy Nexus] duduzinho15:
here thw wifi conect but don't transfer data :S//// 2.4GHz, WPA2 PSK
[Samsung Galaxy Nexus] osm0sis:
I'm browsing this forum from it as I type this... not sure what's up on your end. Reboot?

Edit: Ah I see you already did. :good:
[Samsung Galaxy Nexus] duduzinho15:
I restart my modem and now the conection is normaly :D
[Samsung Galaxy Nexus] franciscofranco:
/facepalm

Glad its working though ;)
[Samsung Galaxy Nexus] Pakobis:
Hi Mister, have you a zip version about r318?... :rolleyes:
[Samsung Galaxy Nexus] Edrill:
Both, 2.4Ghz & 5Ghz connecting perfectly fine on r318. Both networks are using WPA2-AES.
[Samsung Galaxy Nexus] Pakobis:
ok... i'll flash it when come back home... thanks in advance ;)
[Samsung Galaxy Nexus] darthchilli:
I keep on getting the couldnt install on USB error form playstore with R318

going back to 315
[Samsung Galaxy Nexus] franciscofranco:
Sorry, thats nothing to do with the kernel... really pisses me off that when someone has an userspace problem the kernel is always to blame...one thing has nothing to do with the other.
[Samsung Galaxy Nexus] osm0sis:
Most repeat Play Store errors can be resolved by removing your Google account and readding it.

I hear ya. ;)

---------- Post added at 03:43 PM ---------- Previous post was at 03:38 PM ----------

Franco, I see you've still got that random zram stuff in fixtunapower.sh - I thought you said including that was a mistake from something at your job?

Also, could you please add that bb line to backup the original power.tuna.so before it copies? That way at least those on stock who flash it on a new install will have something to restore to when they want to flash OTAs down the line.

http://xdaforums.com/showpost.php?p=34224182&postcount=32763
[Samsung Galaxy Nexus] chrisgtl:
318 running here with no wifi issues.

but then again 315 wifi ran flawlessly for me....

rasbean build 0 rom.
[Samsung Galaxy Nexus] darthchilli:
sorry for the frustration

I may like to add that its only the Franco updater thats been giving me an issue.

so yes i understand your frustration with my comment, but at the same time, play nice dammit

I tried readding accounts and such, no go..

yet when i purchased the app last night, it installed absolutely fine

anyawys, its not the kernel i get it

back to r318

seems to be all the paid apps that i purchased isnt pushing through correctly
[Samsung Galaxy Nexus] F_T_B:
Francisco, can you explain why your color profile no longer shows up in Trickster Mod with build 318? Did you not implement your magic colors in the 4.2 Kernel?
[Samsung Galaxy Nexus] franciscofranco:
It wasn't specifically directed you, just a general comment. Try to clean markets cache and reboot.

Dunno, never used that app. And no I didn't.
[Samsung Galaxy Nexus] nuwan32:
Go into /data/app and /data/data and delete any left over app data or odex files for that app. You need to know the app's com. Whatever name. Should install fine after you remove all traces of it
[Samsung Galaxy Nexus] gianton:
No WiFi problems on r318, also USB turning off when screen off fixed.
[Samsung Galaxy Nexus] bazzawhite:
Just installed 318. Phone didn't reboot and I was worried for a sec but pulling the battery out and back fixed it. Haven't tested WiFi but the kernel feels a lot smoother than 313.
[Samsung Galaxy Nexus] cyberon:
R318 working fine on stock odexed 4.2. No wifi or usb issues here.
[Samsung Galaxy Nexus] franciscofranco:
Ok nice feedbacks about the Wi-Fi. Its the 3.4 kernel Wi-Fi drivers by the way ;)
[Samsung Galaxy Nexus] jackie_jagger:
could someone give me instructions on how do I flash the latest 4.2 kernels? I usually just flash them via cwm, seeing as there isn't a .zip could someone link me to the instructions - it would be mighty helpful.

Thanks
[Samsung Galaxy Nexus] nuwan32:
Awesome! So does it not support wep? I honestly don't care since nobody should still use wep but just wondering :D
[Samsung Galaxy Nexus] franciscofranco:
No idea, still haven't got a bad feedback, so I hope WEP is working fine now.
[Samsung Galaxy Nexus] gianton:
Is it me or the WiFi on r318 is the best so far? It feels like it loads data a lot faster, same router of course.
[Samsung Galaxy Nexus] franciscofranco:
Yep, mine gets much stronger Wi-Fi signal, specially when in places I had 0 bars now I have consistently 1 and its stable.
[Samsung Galaxy Nexus] Edrill:
Oh good, so it's not just me then! Wifi seems quite zippy now, compared to before. Signal strength is quite good, and download speeds seem to have improved a lot over 313 and 315.
[Samsung Galaxy Nexus] asim0:
Guess I just found my next phone...

Sent from teh void
[Samsung Galaxy Nexus] bboran:
how you guys flashing the this .img file kernels? I dont know "fastbooting" procudure..
[Samsung Galaxy Nexus] Puzzlegirl:
Strong wifi signal here in places where it was practically non-existant before. PGM2 (Slide to wake) app shows as not being supported by the kernel any more.
[Samsung Galaxy Nexus] Rimher:
Wifi seems to be pretty good right now! But on stock signal was even more consistent. Smoothest kernel to date
[Samsung Galaxy Nexus] EDNYLaw:
here Enjoy!
[Samsung Galaxy Nexus] zephiK:
anyone getting r318 working with PGM? its missing the module for me.
[Samsung Galaxy Nexus] HuMpS 97 DoHc:
i had to uninstall and reinstall PGM and its working now.
[Samsung Galaxy Nexus] galakanokis:
Finally got around to trying out 4.2 and now of course your latest kernel. r318 definitely makes wifi much better, stronger reception for sure. Glad you went to the newer drivers.

Just testing out the rest but it is fast and smooth, didn't expect anything less.
[Samsung Galaxy Nexus] gianton:
Working fine here.
[Samsung Galaxy Nexus] zephiK:
Confirmed. Just uninstalled, restored app only and works.
[Samsung Galaxy Nexus] llevo3:
+1
[Samsung Galaxy Nexus] F_T_B:
That explains it why it says "Unknown" color profile instead of franco (yes, you're famous with TricksterMod). All is well after applying yours, feel right and familiar.
[Samsung Galaxy Nexus] q711179:
Download, place in kernel backup folder then install via franko kernel updater. If you are not comfortable with this wait as these are still in testing mode and not for general release yet.
[Samsung Galaxy Nexus] hshaikh:
Dammit. I just flashed 315 yesterday. What do you guys say is 318 worth it.
[Samsung Galaxy Nexus] scarmon25:
Running 318 and it seems really stable and smooth. WiFi networks are working for me. Everything else seems good. Have to test the disconnect/reconnect on the WiFi part later.
[Samsung Galaxy Nexus] F_T_B:
I have a question. Now that 512MHz is the default value for GPU Freq, is the same "safe implementation" used in R300? Meaning, 512MHz is supposed to safe on R318 for Android 4.2, but is it just as OK to use with R300? Any changes in between?
[Samsung Galaxy Nexus] Savant:
Great **** this kernel ones great on rasbean 4.2 the latest test kernel ermahgerd heaven . my WiFi feels great like it should be on this phone. Thanks Franco and everyone who was apart of creating this kernel.
[Samsung Galaxy Nexus] kyokeun1234:
Works amazing with stock deodexed! As always, this kernel is why I love you so much! Keep it up!
[Samsung Galaxy Nexus] bigfnjoe96:
Wi-Fi not working for me on r318. Tried restarting router. Put WEP info in all over. No luck. :(

Sent from my Nexus running Jellybean
[Samsung Galaxy Nexus] Savant:
The new kernel won't work with wep so you'll have to change your router security to use it. You would want to since WPA is more secure and then you can feel the speed of the new kernel.
[Samsung Galaxy Nexus] osm0sis:
Yup. It's been safe for ages. :)

Fuuuuuh.. :(

Don't get used to the new drivers people..
[Samsung Galaxy Nexus] bigfnjoe96:
Thanks for the heads-up on the kernel Wi-Fi issue. I'll see about switching to WPA

Sent from my Nexus running Jellybean
[Samsung Galaxy Nexus] Savant:
Yeah try it and let me know how it works for you since its working wonders here. No problems and no buffering while streaming movies. :D

---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------

Yes get used to them people because they are better and make the nexus runs like it should be . :cool:
[Samsung Galaxy Nexus] osm0sis:
WPA2+AES is the standard. It's the only combo that's within spec for N-band+ speeds (so the best for throughput). WEP is a lot less secure by comparison.

If you have access to the router it's definitely worth changing. :):good:

I wish you were right. ;) Unfortunately compatibility trumps awesomeness unless Franco's changed his thinking since the last time we tried these Wi-Fi drivers.. :(
[Samsung Galaxy Nexus] F_T_B:
Thanks for clearing that up. Though I have to ask whether there is a difference between 512Mhz R300 and 512MHz R318, apart from the obvious.
[Samsung Galaxy Nexus] Savant:
My Linksys loves WPA setting and runs like a champ.

---------- Post added at 07:59 PM ---------- Previous post was at 07:56 PM ----------

There is plenty , driver changes, USB tweaks and others.
[Samsung Galaxy Nexus] osm0sis:
Just the obvious: r300 is the culmination of all the work into the final JB 4.1.x-based kernel. And r301+ is a new work in progress for JB 4.2.x. Franco's brilliant though, and even though he basically had to start from scratch merging things in, it's almost back to where it was. :D
[Samsung Galaxy Nexus] The Gingerbread Man:
So this means even if I flash stock kernel when next round of ota comes round it won't install right? I'm running stock 4.2 ROM rooted with Franco 318 now, stock baseband and even recovery for now...

Sent from my Galaxy Nexus

---------- Post added at 12:41 AM ---------- Previous post was at 12:40 AM ----------

Btw no problem with the WiFi here I'm glad to see these drivers back :D:thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] crea78:
I just bought the updated app on the Play store. Franco, when do you expect we can flash the new kernels for 4.2 using your app? Right now, we cannot do anything with it ATM.
[Samsung Galaxy Nexus] franciscofranco:
Oh you can't? Updating kernels is just a tiny thing in the app, the rest does much more. I'll have time today and tomorrow before thanksgiving to try and make the kernel worth my standards before I call it ready for general release.
[Samsung Galaxy Nexus] osm0sis:
Correct. You'll have to find a way to get the stock power.tuna.so file back in order to pass the OTA asserts (file checks). This is why I think my simple change to his script (which replaces the file) to have it make a backup if there isn't already a backup would be a friendly thing to do. :p
[Samsung Galaxy Nexus] The Gingerbread Man:
Of course you can flash it with the app, thats how iv done it with the last 3 releases for 4.2. Its been explained tons of tons, put the .img in kernel back up folder on your sd then restore it in the app.

Well if this works as a democracy I vote for this idea haha :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Culex316:
Call volume is low in r318 (compared to past builds)
[Samsung Galaxy Nexus] crea78:
Well, I haven't installed one of the testing kernels for 4.2 yet, so I could fastboot but waiting for more "stable" builds before trying them out again.