yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rodnar77:
i tend to agree becuase i actually didnt have any issues at all until 264.... then none of them worked until 251??? who knows... there is a glitch in the matrix?!
[Samsung Galaxy Nexus] SpOuK-3-:
This r666_test fixed my issues with wifi... Thanks franco!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
No one can claim a kernel or a rom can be perfect. Hell sometimes I even got problems with the stuff I add and create, but most of the times I don't. Like I said before 99% of the problems that users report are just user errors, misbehavioring apps, beta/alpha/WIP roms with broken code.

This is how I test my kernels:

1 - I merge something important or that can possibly hit the **** fan

2 - I test the device for a little while, benchmark, run ADB, runs some shell commands, browse through stuff, copy/move/delete files, check conncetivities, Wi-Fi, BT, data

3 - Then I exchange back to my main device - Galaxy S3 and handle the Galaxy Nexus to my sister (shes a average joe kind of user). She tests the device for as long as I ask her to. She uses Wi-Fi, sms and calls a lot, and even games.

4 - After a while I ask her if she hit any **** fan, how was the performance, battery etc

5 - I handle my kernels to minooch as well, he tests stuff that none of you test, so be thankful to him that most of the kernels are major bug free

6 - After all this I release the kernels if they get the quality brand from me

Whats the secret candle for me not hitting any problems? I use a stable rom, minco, and I don't use badly coded apps, apps that leave tons of processes running in the background etc. Like I said before a few times, I control the device, and not the device that controls me. Treat your device like you should treat a lady and it will work as it should for you.
[Samsung Galaxy Nexus] ÜBER™:
I think you meant.. did the **** hit the fan not the **** fan xD LOL.
[Samsung Galaxy Nexus] meanwhile:
Btw #666 works great for me. WiFi problems gone and quite happy with performance too.

Sent from microwave
[Samsung Galaxy Nexus] mariachi202:
Just in case some of the users forgot what's the name of this thread, I wanted to issue a reminder: Galaxy Nexus ANDROID DEVELOPMENT. I implore you to take notice of the words in capitals.

Your friendly neighborhood GNexMan.
[Samsung Galaxy Nexus] mike216:
I've been using Francos kernels for years now and never heard of any phone dying, this is the one rare time in life it happened and with a huge following it just happened to happen here.

More then likely just bought a bad phone and it choose today to take a ****!

It really sucks I'm sure and I do feel bad for the user.

Your far safer using Francos kernels for the massive amount of experience! That's a lot of trial and error ;)

Sent from my OGparanoid CM D2tmo
[Samsung Galaxy Nexus] ILLIPINO:
Samesies! Thanks for this awesome kernel
[Samsung Galaxy Nexus] franciscofranco:
Just get me the logs and I can look and see if its kernel derp or random crap :)
[Samsung Galaxy Nexus] mike216:
Sorry Franco for maybe the way I worded it! I'm doing great my response was to the one user who reported his phone dying. I was trying to make the point that I've been using your kernel for years and have never heard of such a thing until now.

99.99999% of the time I never have any issues I see others report.

I was also saying that you have a huge following and reports of odd happenings are bound to pop up sooner or later. Most likely it would have nothing to do with the kernel but when you have thousands of users your going to see something odd sooner or later! It's all good bud! I'm enjoying my experience :thumbup:
[Samsung Galaxy Nexus] thegtfusion:
Heh franco, i have a couple of questions for you. Can i have your email? As you dont do private messaging...
[Samsung Galaxy Nexus] franciscofranco:
franciscofranco.1990@gmail.com
[Samsung Galaxy Nexus] Icecoldmeat:
r264 fixed the wifi for me :)
[Samsung Galaxy Nexus] _george:
Last two were giving me issues with Wi-Fi not connecting after getting home from work, when I checked the Wi-Fi it still had all the WAPs from Sydney uni campus only a reboot would fix it.

On 264 today everything else is the same, will check when I get home if the issue is sorted for me.

Thanks for the great kernel and support.
[Samsung Galaxy Nexus] thegtfusion:
Thanks. I sent you an email ;)
[Samsung Galaxy Nexus] osm0sis:
Hi Franco, I got a couple signal drops last night in my house so I made another logcat for you to check out (didn't have the chance to upload it until now). Does it look like a normal drop, or something else that could be fixed? I chopped out all the dalvik, etc. crap.

[log removed]
[Samsung Galaxy Nexus] rodnar77:
666 Wi-Fi test seems to be working OK. 2 hours so far... will double verify when I get home...
[Samsung Galaxy Nexus] Langduscher:
Just a WOW-post for the partipcipation from the dev in our way to improvement :cool:
[Samsung Galaxy Nexus] gizmoid:
Stock ROM, stock kernel, last update your app from GPlay and result is stronger signal for at least one bar on WiFi? I don't know how and why but I enjoy in it. :)
[Samsung Galaxy Nexus] suquet.paul:
Where did my kernel backup go?

Before I flashed franco kernel I made a backup of my stock kernel. After a few weeks I wanted to try Lean kernel, so I made a backup of my current franco kernel. I flashed lean and by the time I was back; my stock kernel backup image is gone! Where did it go? How can I flash back to stock?

Thank you.
[Samsung Galaxy Nexus] Pkt_Lnt:
Franco app only keeps one backup, so the one before the last backup is gone. You can get your stock kernel back by reflashing your ROM, wipe cache and dalvik is all.
[Samsung Galaxy Nexus] osm0sis:
For future reference, you can also rename them with a file explorer and keep as many kernel images as you want in there.
[Samsung Galaxy Nexus] franciscofranco:
What? My app keeps as many backups as you make. If you want to make 100 it will save 100. As soon as the app is uninstalled all the backups go kaboom.
[Samsung Galaxy Nexus] THE_KINGDOM:
Never used a nightly of Franco since the milestone 5, but just put r264 512GPU and suddenly phone is always having frozen screen and I have to restart to fix it. Any ideas? Is this anything to do with the 512 GPU?
[Samsung Galaxy Nexus] Pkt_Lnt:
For me, it had only ever kept one named .img. I have tried it many times. Now I download zips from the app to have backups.

Here is that directory again after saving again.

Galaxy Nexus / Tapatalk 2
[Samsung Galaxy Nexus] nuwan32:
Milestone 5 is 384mhz gpu so your chip probably can't handle 512mhz. Try flashing r264 384mhz
[Samsung Galaxy Nexus] franciscofranco:
A piece of advice, try to give a name to the backup image, thats why the dialog box appears when you click the Backup preference.
[Samsung Galaxy Nexus] Pkt_Lnt:
Duh, did I ever miss the obvious on that one. :o
[Samsung Galaxy Nexus] RayGarden:
1 Word - "RESPECT!". No judgements, no misbehaved comments. I just love your work :good:
[Samsung Galaxy Nexus] scarmon25:
Yeah its statements like that which make me happy I bought the Franco kernel app when I got the GNex. There's a ton if apps out there and I am certain the other devs work is as amazing as this is. But this kernel just seems to work. And the app makes life so much easier.
[Samsung Galaxy Nexus] ac3theone:
Another reason why the updater app should be able to take you back to the stock kernel if the user wants to. I requested to have this feature recently. It can save users a lot of time.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] despard:
Hi Franco, with the new 264 nightly my GN seems to get a little bit more Wi-Fi related wakelocks than before, should I run it for few more days to testify or what can I do for you?
[Samsung Galaxy Nexus] franciscofranco:
The purpose of the app is not to provide a stock kernel, thus I do not agree with that addition. I added the backup feature so users can backup whatever kernel they want, that is enough in my book.

r264 wifi driver is the same as r248.
[Samsung Galaxy Nexus] osm0sis:
It does "provide" that option if the user places the stock boot.img in the kernel_backups directory, and that's easily done. I've got the boot.img from Google's Factory Images in there just in case, click the ROM link in my sig for them.

I also keep the stock boot.img cwm flashable zipped in case I ever get into trouble and can't fully boot (I've got my bootloader relocked using Bootlocker so fastboot wouldn't save me at that point ;)).
[Samsung Galaxy Nexus] julianlyle:
It would be a good addition.

Enviado desde mi Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Franco has already given us all the tools we need to do so, see my post above yours.
[Samsung Galaxy Nexus] ac3theone:
@Franco what's your take on this?

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

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rodnar77:
Confirmed, 666 is working great WRT Wi-Fi. Three different locations, Wi-Fi connects no problem.

Thanks Franco...
[Samsung Galaxy Nexus] nnnnr14:
*facepalm* how do you do it osm0sis... you never flame people..

-tapped from my paradigm Franco kernel Galaxy nexus
[Samsung Galaxy Nexus] rosswaa:
not long been using the franco kernel but really liking it atm,

have a HUGE gub though, if the headset volume boost is enabled my music in poweramp cuts out. i listen to alot of music at work and this has bugged the hell out of me as i like music nice and loud :D

does anyone else get this?

please fix if possible, thanks:good:
[Samsung Galaxy Nexus] joeyfong:
@franco, any update about the sound control?
[Samsung Galaxy Nexus] wisefreakz:
@Franciscofranco and who else felt offended by my post informing my phone died 4 hours after applyin r264:

To make things "more" clear, i did not blame Francisco nor his Kernel. I think like most users on XDA are aware that doing what we do can result in a bricked phone.

However, i felt in my rights to report the situation here as i use Francisco`s Kernel / App.

Again, i said it was a "coincidence"... that`s all. I'm not mad as i assumed the risk of applying kernel`s, rom, etc.

I, like many others in this thread, uses Francisco`s kernel for a long time and never had a problem.

So... Francisco, all my respect for your work mate!!!

Peace.

W.F
[Samsung Galaxy Nexus] gadget_lova:
r666_test didn't fix my WIFI problem.

I use wifi with WPA/WPA2 PSK security. I can't connect to it with my GNex while my other device can.. :(
[Samsung Galaxy Nexus] haxor:
Using franco app and kernel using JB stock give me some tips to good battery like ! Thanks in advanced :)
[Samsung Galaxy Nexus] The Gingerbread Man:
I tested going out of WiFi range on 264 going a quick drive and upon return WiFi connected back up just fine as expected. I know this has been answered but figured I'd share too.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Mayday_XL:
How can i deaktivate the battery life extender ?
[Samsung Galaxy Nexus] The Gingerbread Man:
Try 264 its the latest.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ÜBER™:
Its not in use/effects anything unless you change the default number.

Sent From My Toro+ via White Tapatalk
[Samsung Galaxy Nexus] Mayday_XL:
Default is 100 but my phones loads only till 99%.
[Samsung Galaxy Nexus] djjonastybe:
franco why haven't you undervolted VAUX3 and VUSIM to 2900mv and 2000mv ?

I see some kernels do that I wonder why you don't.
[Samsung Galaxy Nexus] Pete7ate:
We actually have a job.
[Samsung Galaxy Nexus] irizwan:
I think whe you do 100 it's only cosmetic in reality our battery only charges till 94-96% if i remember correctly =)
[Samsung Galaxy Nexus] The Gingerbread Man:
You could try removing the charger and plug it back in to get your extra 1%

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sachilleas:
What's the best colour settings to use inorder to avoid burn ins?
[Samsung Galaxy Nexus] drawde40599:
Stock or just Stay under 200, "they" say, but I never have and my screen is fine

17

20

20

170

180

205

Trinity -5

My settings .....

Search this thread or Google and u will find a Google drive document with 100. + settings from other users
[Samsung Galaxy Nexus] The Gingerbread Man:
Well the general advice is to keep colour multipliers at no mor than 200 but I reckon a little over won't hurt, just don't use all set to 400. To find what works for you best look here http://xdaforums.com/showthread.php?t=1790325

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Because its 100% not necessary and does nothing beneficial, proven over and over again and agn + with every phone being different some may not be able to handle it . Search this thread u can read 100's of pages on uv

---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------

Ya that happens once in a while to me also ,just reboot or unplug and plug back in, it happens maybe once in every 10 charges to me.

---------- Post added at 12:37 AM ---------- Previous post was at 12:32 AM ----------

http://db.tt/sKYtKiqW just put in his backup folder and a copy in sdcard and Done ;)
[Samsung Galaxy Nexus] Kurre:
Are you sure that you're talking about the same matter? Since those VAUX3 and VUSIM are (at least AFAIK) related to the display regulator voltages..And it seems that you're talking about processor undervolting ? Because I haven't seen any discussion about those display voltages in this thread..at least not a 100's of pages..;)

Can't really say if those values would help us to reduce batterydrain..But who knows..it would be nice to try..:rolleyes: maybe Franco has some pro-opinions about this matter.. :D
[Samsung Galaxy Nexus] djjonastybe:
There might be an advantage: heat reduction. If it's not battery life at least this can be considered.

Have you ever noticed the big heat dissipation in the right top of our phone, where the Front camera is located?

Not to mention our screen uses about up to 70% off all power, at least here it does.

I am just wondering if we need to put all that juice in it... TI has decreased from 3.3v to 3.1v before, 3.1v is the max volts that should be put into the lcd. So I think we can go lower, much lower.

In the V = I * R solution, if you increase V (voltage), I (amperage) has to increase since resistance is staying the same (not assuming resistance increase from temperature increase).
[Samsung Galaxy Nexus] andQlimax:
I agree with that..im saying that since i had the htc desire...why we undervolt the cpu? we should first undervolt the display (if possible) :)
[Samsung Galaxy Nexus] franciscofranco:
I already went there long ago. It does more harm than good, users reported problems once in a while. Reducing display voltage is not a good idea on my book.
[Samsung Galaxy Nexus] gadget_lova:
I've come from milestone 5 when this wifi bug suddenly surfaced in my phone, then I try #264 with no success, then r666_test with still no success.
[Samsung Galaxy Nexus] sachilleas:
I believe that using r248 wifi drivers in latest nightly is the best way to go! Best wifi drivers so far, excellent signal.
[Samsung Galaxy Nexus] djjonastybe:


Do you remember when that was and symptoms i may be looking for?

2800 and 1800 works fine so far. I only had a camera module that refused to be loaded when opening the camera app. Its probably nothing
[Samsung Galaxy Nexus] Kappa Lamda:
Well after two charges with r264 I notice a little bit more battery drain than r251 I had...

With 264 and 8 hours with 44min screen on I have 78% battery left but with 251 9 hours 1h+ screen on 80% battery.... noticeable difference!

Both kernel were with 512gpu and same use. Web,mail,talk, one two calls and auto brightness,2g and wifi and of course same version of rom(cna 3.5.0)

I think i'll stick to 251 for now! Never had wifi connection problems anyway...
[Samsung Galaxy Nexus] franciscofranco:
Its probably the difference between the wifi drivers, nothing major changed in between.
[Samsung Galaxy Nexus] franciscofranco:
I dont remember when it was, but it caused dmesg to be spamed with SYNC_LOST warnings in the omap dsm drivers (panel stuff).
[Samsung Galaxy Nexus] RayGarden:
Battery Life #264 is bad

With #251, the Battery Life was the best i ever experienced. Now with #264 it is much worse. Maybe 75% of #251.

Never experienced WIFI problems with all the Nightlies by the way.

Batt Stats report gives a huge wakelock on "Good Signal"? I don't get it. I only have used 3G today.
[Samsung Galaxy Nexus] RevengeFNF:
Here im with 8h20m with only 15m screen on(10m of them playing Temple Run on the Bathroom lol).

I have 92% battery left. Great Battery in Deep Sleep :D
[Samsung Galaxy Nexus] drawde40599:
Search the thread, when Franco was playing with UV on EVERYTHING is tword the beginning, I've been using this kernel since before Franco had his galaxy nexus I've read every page of this thread, ( I live in Alaska its cold outside ;))so yes we are talking about same thjng :)

---------- Post added at 07:48 AM ---------- Previous post was at 07:45 AM ----------

My battery is the same with both those builds still getting 3.5 -4 hours
[Samsung Galaxy Nexus] Kurre:
You're absolutely right, I'll stand corrected ;) you have clearly been following this thread much longer time than me :p
[Samsung Galaxy Nexus] PianoJazz:
Wipe Dalvik and Cache Before? After? Both?

One thing I've never quite understood: When flashing, should the cache and Dalvik be wiped before the flash, after, or both? I've always played it extra cautious and done it both before and after, but if some of it's unnecessary, I'd like to know.

Also (again probably being too careful), should I also fix permissions, as long as I'm in Recovery?

Thanks.
[Samsung Galaxy Nexus] nuwan32:
You don't need to do this between kernel flashes only ROM and you always do before not after. Also most ROMs automatically do this so you don't need to worry
[Samsung Galaxy Nexus] drawde40599:
http://xdaforums.com/showthread.php?t=1367341
[Samsung Galaxy Nexus] mixtapes08:
You don't need to wipe anything when flashing kernels unless it has init.d files in it. that can be Easily deleted using some root file explorers.

Sent from my Nexus Prime™
[Samsung Galaxy Nexus] franciscofranco:
Just flash and forget.
[Samsung Galaxy Nexus] Hanny:
hey mate you're on the "others" screen in bbstats which just reports you the time your phone is spent on having good signal, deep sleep and such

to check wakelocks you have to choose "partial wakelocks" in the first pulldown bar and there are never "good signal" wakelocks.

cheers ;)
[Samsung Galaxy Nexus] RayGarden:
Thanks mate....i really didn't know. Keep on learning.....so to speak :good:

this is the result. can you say, this is a normal behaviour?
[Samsung Galaxy Nexus] Kurre:
Those screenshots look a little out of order..are you using maps latitude which is logging your location? I'd suggest you to disable (double check for those ones) it if you really don't need it. And also make a bbs log by charging your phone, unplugging it and leaving it untouched for a couple of hours, then your own actions doesn't affect the results.

Also you could try posting to the bbs thread, as there is many skilled guys to help to with these suckers (stubborn wakelocks) ;)
[Samsung Galaxy Nexus] spaceman860:
This app is better then BBS for battery info GSam Battery Monitor

https://play.google.com/store/apps/details?id=com.gsamlabs.bbm

Sent from my BAKED Nexus
[Samsung Galaxy Nexus] franciscofranco:
Alright just divided the interactive governor into 2, one normal with static settings, and another called dynamic interactive. This will suite everyones taste. Also fixed the bug where logcat was spammed with error messages warning that boostpulse couldnt be found. Gotta love Googles permission changes on JB. Testing the changes for proper release later today.
[Samsung Galaxy Nexus] c6comp:
Hi I am having a bit of trouble on your latest r264 nightly. Its sort of like a data drop but not really. The phone will occasionally, after being idle for a while, get "stuck" on 3g and will never establish an hsdpa/h+ connection. When this happens you can either toggle airplane mode or go into *#*#4636#*#* and reselect wcdma preferred/only (doesn't make a difference on either, still gets stuck) and the phone will instantly go back to hsdpa.

Is this just T-Mobiles network being **** or is it a bug in the kernel/radio? I am on the UGLH1 radio and the RIL is correct as well.
[Samsung Galaxy Nexus] J-Hop2o6:
Hey, this is pretty nice. It's like a more informative Google Battery Stats.

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

Try the radio i'm using (check sig). T-Mobile is running great in/around Seattle :good:
[Samsung Galaxy Nexus] barrist:
NICE. Always went back to 246 (the release before dynamic interactive). worked best with my phone i felt.
[Samsung Galaxy Nexus] emd2009:
explain to me the differences and pros and cons of static interactive and dynamic interactive?
[Samsung Galaxy Nexus] GeekMcLeod:
I'm sure, when it's released, he will give you key differences of the 2. I could be wrong, but don't see why he wouldn't once they are out.
[Samsung Galaxy Nexus] franciscofranco:
The dynamic interactive is what we have now being the interactive, just called different. Normal Interactive will be back to static tunables and users will be able to chose what they want best for themselves without having the governor overriding them all the time.
[Samsung Galaxy Nexus] franciscofranco:
r268:

* Merge some patches from Google's android-3.4 branch

* Separate Interactive governor into 2: one called Dynamic Interactive that changes its tunables by itself according to system load (its what we had in the latest nightlies since r246) and normal Interactive with static tunables where users can change the values if they want to

* Dynamic Interactive won't play well with the app, I have to update the app code for users to see what tunables the governor is using so don't cry if you don't see any values when you tap Governor Control

* Some other small changes visible on my github
[Samsung Galaxy Nexus] osm0sis:
Thanks for r268 Franco! Question though: the default governor is back to being interactive, and not dyninteractive? Easily set back to dyn, of course, but I thought you would have kept that as the default, since it would be perfect for the new user/non-tweakoholic. ;)

Also, is there any chance of you including 1536Mhz in Smartreflex again? It seems extremely stable at that frequency now (which is why I think you took it out before) but it would be great to get some of the SR benefits running it as well.
[Samsung Galaxy Nexus] nnnnr14:
Hmm can wifi pm_fast be used to boost tethering speeds?

-tapped from my paradigm Franco kernel Galaxy nexus
[Samsung Galaxy Nexus] c6comp:
I flashed that radio after clearing the cache and it made absolutely no difference. It is neither better nor worse. Any other ideas? There is nothing abnormal in logcat that I can see.
[Samsung Galaxy Nexus] franciscofranco:
I prefer to set interactive as default like it comes from Google :)

If I do that 1536Mhz will run in the same voltage that 1228Mhz and it will crash!
[Samsung Galaxy Nexus] franciscofranco:
The command is in the second post.
[Samsung Galaxy Nexus] osm0sis:
Oh seriously? I thought you had 1420Mhz running with SR, so I thought 1536Mhz as one step higher could be worked in as well.. I guess I was mistaken!

Thanks for the info.
[Samsung Galaxy Nexus] silentus:
best kernel ever
[Samsung Galaxy Nexus] kyokeun1234:
The newest nightly looks promising... any bugs found yet?

Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
[Samsung Galaxy Nexus] nnnnr14:
:what: who's this guy!!?!??? Jp but all good on my end. My phone hasn't even heated up and I've been playing a little games and watching some YouTube which normally my phone skyrockets as soon as I open the apps.

-tapped from my paradigm Franco kernel Galaxy nexus
[Samsung Galaxy Nexus] KJW979:
268 running great, no issues. Smooth as can be, as always your kernels are the best out there.
[Samsung Galaxy Nexus] rodnar77:
268 is a OK..... no issues yet..... awesome thanks against ....
[Samsung Galaxy Nexus] mixtapes08:
R268 Seems like a milestone kernel for me:) thanks dude

Sent from my Nexus Prime™