yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metalspring:
yeah I think it takes anywhere from 30 minutes to an hour to compile a kernel, if it doesn't error out that is, not to mention it's nowhere as easy as compiling a ROM because of all the options you need to run through to even get it to build let alone boot, run and run right and smoothly for that matter

Not to mention always watching for useful changes in your sources and then repo syncing and/or git cloning, then compiling with those changes and see if it will build and run as good as or better than your previous compile

It probably takes Franco the good part of an entire day to get a kernel that's worth releasing as a nightly let alone a milestone release, not to mention he releases 2 kernel versions for every nightly- 384 gpu and 512 gpu...
[Samsung Galaxy Nexus] Neejay:
ROM? Kernel? 163, nope, no glitches here. (384 GPU)
[Samsung Galaxy Nexus] SeanHacker:
this is a kernel thread. not a rom thread.

I haven't seen this issue you're talking about.
[Samsung Galaxy Nexus] metalspring:
what gpu speed are you running? if your phone can't handle 512 gpu and the voltage for it then it will mess up the screen, otherwise the only graphics glitch you might see is after a reboot if you use the omap 4 gamma setting and that's only for a second when it applies
[Samsung Galaxy Nexus] iGoogleNexus:
=\ trying to flash the lastest nightly but it doesn't load... tried clicking the link via here but it doesn't load lol can someone post an alternative link? :D

- Google
[Samsung Galaxy Nexus] metalspring:
His server must be down or he somehow messed something up in the kernel and put downloads on hold till its fixed?

Most likely the first one since 163 seems to be running too well to have an issue :p
[Samsung Galaxy Nexus] aper3caper:
Anyone else's phone not going into deep sleep on 163. 162 was running like a dream but it seems like 163 won't sleep for me. I'm running LiquidSmooth 1.4 and BetterBatteryStats is reporting a suspend_backoff kernel wakelock that seems to be keeping the phone awake. Any ideas on what that might be?
[Samsung Galaxy Nexus] metalspring:
Mine deep sleeps just fine and I'm also on liquid 1.4 with r163
[Samsung Galaxy Nexus] FatherD:
Using AOKP and 163, did get some early signal issues, but a full shutdown and restart sorted it - no recurrence! Deep sleep working! No screen glitches!

384gpu / CPU 192—1228mhz / SR on.
[Samsung Galaxy Nexus] nodstuff:
Same here, all good.

Ls 1.4 r163.

Smooth as butter! :)

We might not see Francisco around here much today, the kernel source for the note are out!

No doubt he's looking at them right now!! :D
[Samsung Galaxy Nexus] sotoskawasaki:
Could you be kind enough and explain what servicemanager is and how resetting it would help the signal?

And on another note why setting the min Cpu freq to 729 will stop the signal drops? This shouldn't need to happen. It means that there is something wrong...

Thanks
[Samsung Galaxy Nexus] aper3caper:
Hmmmm... You guys are right. Switched back to 162 for comparison and I'm still not sleeping. And I'm still getting a very high suspend_backoff wakelock. I wonder what could have happened between flashing 163 and now...
[Samsung Galaxy Nexus] giugiu:
Change download path.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] macellaio:
Yes, he did choose those slots for a reason. Don't quote me, but I'm guessing 38.4mHz is the frequency of the oscillator?
[Samsung Galaxy Nexus] franciscofranco:
Nah not yet, not in the mood for looking at yet another kernel source for a few hours ;)
[Samsung Galaxy Nexus] elban:
how do you get 900 in 2D? I never got more than 300 :-(
[Samsung Galaxy Nexus] macellaio:
Unless you're doing some hardcore processing while your screen is off, it doesn't matter. You'll probably spend 90% or more of the time at your lowest frequency anyway. I've tried 384 and 729 and didn't notice any difference. Francisco set the default to be 729 and that's good enough for me.
[Samsung Galaxy Nexus] metalspring:
Do you have force gpu rendering checked under developer options? That raises benchmark scores drastically especially 2d and 3d scores
[Samsung Galaxy Nexus] elban:
thanks, that was it :-)

I used to have it disabled because some applications had graphic glitches.
[Samsung Galaxy Nexus] -star-:
I had never any issues with this kernel, but after the move to milestone 3 I'm facing extrem high mpu temperatures.

At the moment I'm using the nightly 162 with 384 MHz gpu, but the temperature problem still exists with around 50°C till 60°C or is it normal?
[Samsung Galaxy Nexus] Stretlow:
I get this with CM9
[Samsung Galaxy Nexus] drawde40599:
Same set up, deep sleep for last 9 hours 163 -512

Running flawless so far testing full day now ...
[Samsung Galaxy Nexus] jcurtis369:
I was having this problem too and i was running aokp. Try switching to one of franco's nightlies thats what fixed it for me.

I havent tried r163 yet but i can say that r162 w/ 512gpu is a beast. Great battery life and is super smooth and my phone stays cool :D
[Samsung Galaxy Nexus] The Gingerbread Man:
It controls radio functions, its just a command to turn reset it. Works better if you have signal issues better than just a reboot. Not exactly sure how it works just a piece of knowledge I picked up along my journey through android.

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] nklenchik:
Great screen on time on r163. 1 hour of use and I'm at 83%...I may actually be able to push 3.5+ if this keeps up.
[Samsung Galaxy Nexus] papepo:
Francisco could put temperature control in next build?

Thanks
[Samsung Galaxy Nexus] castaway1:
try check this

http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] celyst:
Already faced this loss of signal 3 times on the new r163 kernel... The second time I was on wifi and I toggled airplane mode, then a bunch of messages came in on Whatsapp, and immediately after that it broke again - Wifi shows it's locked on but Whatsapp messages can't be sent out. I'm sure it's a kernel problem since the only thing I've changed over the last few weeks is the kernel, been using the same radio (UGLC1) for a long time.
[Samsung Galaxy Nexus] andQlimax:
Was the same problem happening also on 162 for u?

I have no drops anyway..

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] jericho7:
I don't know if this has been asked yet but is there any explanation as to why 512gpu was unusable for a lot of us before the last few nightlies but can now be used without too many issues? When 512gpu first came out my device would barely make it 15secs past the lock screen before rebooting, now I only get artifacts and slowdowns when playing games (and sometimes no artifacts), I'm thinking whatever caused this can maybe be tweaked a bit more to reduce the artifacts in games
[Samsung Galaxy Nexus] celyst:
Not that I can remember, even if there was, it wasn't so often. In a span of about 6 hours, my signal has dropped 3 times. The worst was the second time, when after toggling airplane mode, it worked for like 5 seconds, then died immediately after that.

I've gone back to r156, which was working great for me and I believe was giving me excellent battery drain on idle too.
[Samsung Galaxy Nexus] drawde40599:
If ur on a 4.0.4 rom I would / u should try a 4.0.4 radio see if issue go away, I got the best signal speed off of original 4.0.2 radio kk1 I think it was, then I was forced to upgrade due to.signal loss ....
[Samsung Galaxy Nexus] leets4uc3:
Franco. Would it be possible to change your widget color to black tint instead blue? It would make my phone look much cleaner :)

If not that's fine! 163 owns. You have done a sensational job!
[Samsung Galaxy Nexus] aper3caper:
Sorry for the off topic but I thought I'd give everyone an update on my situation. Did a full wipe and reinstall of LS 1.4 with 162 kernel and still no deep sleep. Also, still getting that suspend_backoff wakelock. Anyone have any info on that wakelock? I've never seen it before today. Yesterday LS 1.4 and 162 were running great and I actually hit a record with battery life. 1d 7h total and 3h screen time on stock GSM battery. Today, I'm already down to 50% and have only been off the charger for a few hours.
[Samsung Galaxy Nexus] celyst:
LOL? UGLC1 is already from 4.0.4... in fact, it's the latest baseband - thread here: http://xdaforums.com/showthread.php?t=1405345

Logically speaking, since I've been using the same baseband for a while already, and the only thing that's been changing recently is the kernel, the kernel is the cause of my recent issues. So either UGLC1 works well with an older kernel, or I should use another baseband with the newer kernel, or maybe it's just some weird bug.

Either way, I want my phone connection to work well, so I'll just return to a previous version of the kernel that works well for my phone :).
[Samsung Galaxy Nexus] superbobup:
Did you try disabling SR? Also, there was a servicemanager terminal command 4 pages back that fixed it for a few people. Try those out, it may help

On another note, lock screen lag with auto brightness is gone on 163 for me. I only started using it on 162 but 163 is noticeably faster unlocking. Thanks, Franco
[Samsung Galaxy Nexus] drawde40599:
Oops; ) I didn't c the C, I thought it was the other 4.0.3 my bad, is that an official radio? What phone / update is it for / come with? Canadan?

Edit; ). U no what I have tried that radio also and it was no good for me, I agree use what works but if u can't update anymore ( kernel ) u may want look into .... anyways thanks; )
[Samsung Galaxy Nexus] celyst:
I rebooted my phone the first time, think that should be identical to restarting the servicemanager through terminal. Did not try disabling SR cos I would like it enabled since it should help with saving battery.

I believe it came with the official 4.0.4 update, according to the thread.
[Samsung Galaxy Nexus] Diger36:
Having the same problems here. Rebooted, tried su command a couple of pages back, airplane mode, disable sr. Nothing send to work. Had the same issues some builds back but didn't have thren in a while. Certainly not the previous two builds. Anyway, now I have signal but continuous blue bars although I do gave access to the play store. I think I'll try a wipe.

Edit: wiped cache, have blue bars back, let's see how this goes from here..
[Samsung Galaxy Nexus] superbobup:
It may save battery, but this way you can test and see if it's truly a problem with 163 or if it has to do with this whole SR business :)

If you really want to, you can always set the UV values to whatever SR calibrates it too and then disable SR. This way you will still have the same voltage but with SR disabled.

And, though restarting _may_ be the same thing, there's also no harm in trying the command, right?

Also, I'm running UGLC1 with 163 and I've not had any signal issues yet
[Samsung Galaxy Nexus] Diger36:
I doubt it is radio related as I am having tree same problems on XXLA2. I doubt that it is kernel related too. Although it is the only thing I changed, there are not many reports of the problem here so it must be something on my side.
[Samsung Galaxy Nexus] Serious_Beans:
163 is great. Really smooth and battery is perfect.

And 2.5hrs screen time :) best results I've had for a long time.
[Samsung Galaxy Nexus] Diger36:
Where did you read about a 1212 build?
[Samsung Galaxy Nexus] andQlimax:
if with "last few pages" u mean the December posts..then yes, there was a 1212
[Samsung Galaxy Nexus] Serious_Beans:
I'm an idiot, I was like in the middle of this thread lmao. Thought I was near the end and I got confused. >_< I fixed my post lmao
[Samsung Galaxy Nexus] celyst:
I've also read that kernel usually doesn't affect signal, as that's usually connected with the baseband. But since I've changed nothing except the kernel, I can only assume it's the kernel...

I think for now I will stay with r156 as it worked well for me. I don't want to spend too much time troubleshooting as well.
[Samsung Galaxy Nexus] kekko986:
Hi Franco! Is it possibile to implement an after-installation option to change gpu oc,like leankernel one? Maybe changing it by franco.kernel app or by cmd in terminal (like leankernel)? Thx for your work!﻿
[Samsung Galaxy Nexus] dpaine88:
Just download the other one..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CaspaTheGhost:
Franco has said on numerous occasions that live GPU OC won't be implemented as it leads to his email inbox being raped by people with issues. His compromise is to have the two nightly variants so users can try both and make their own decision on which to use.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] :
Since 162 the phome doesnt save my colormultipler settings....

Any help here ?

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] Diger36:
Went back to 162. Wiped the lot but kept getting data drop problems. Maybe I can try a clean install tomorrow. I really want to run r 163 for the fast and battery friendly performance.
[Samsung Galaxy Nexus] beama:
Same here :(
[Samsung Galaxy Nexus] Lambetts:
Getting terrible battery unfortunately.

r163 384gpu
[Samsung Galaxy Nexus] BigBake88:
What does terrible battery mean? You couldn't have had it installed for more than a few hours...
[Samsung Galaxy Nexus] drawde40599:
Ya 163 is killing my battery, my phone use dose not change from day to day use on weekdays and I'm about 20% lower than what 160-162 was giving me, I'll give it few battery charge cycles but normally I don't have to . It is running very smooth / fast, I don't feel its much faster than 160 - 162, about the same on full power mode .... my results so far ( 512 gpu) liquid 1.4
[Samsung Galaxy Nexus] apsis:
Nightly 163 gives me a lot of Data drops and i had 1 Reboot and 2 SOD's within 3 hours. Same Settings/Undervolting/Governor/Governor Settings ... in Francos Kernel app as i had with Nightly 162, but i didnt have this issues on Nightly 162 with exactly the same config.

I went back to Nightly 162 and everything works again, no SOD's or Reboots for over 2 Hours now and not a single Data Drop.

I'm not complaining, i appreciate your work and Nightly 162 works well for me. But just want to point out that a few people seem to have issues on 163 which didnt appear on earlier versions.

best regards
[Samsung Galaxy Nexus] drawde40599:
163 been out since yesterday
[Samsung Galaxy Nexus] franciscofranco:
Thanks for all the reports :)
[Samsung Galaxy Nexus] yyz71:
No worries :D Good work as always....
[Samsung Galaxy Nexus] Culex316:
I too second the quicker battery drain with 163. and it's definitely noticeable for me too since I also ended up with about 20% less capacity than normal at the end of my work day
[Samsung Galaxy Nexus] Culex316:
but thank you anyways your kernels are the best!
[Samsung Galaxy Nexus] ZachPatterson:
update-cm-9-20120522-NIGHTLY-maguro-signed.zip + franco.kernel 163 nightly @ 512MHz GPU + Jellyfish S3 Live wallpaper and Crappy signal all day..

Still got half my battery left...and the app switcher and overall responsiveness is definitely faster.

Awesome work Franco!
[Samsung Galaxy Nexus] andQlimax:
I'm going to hit my usual 4 hours screen time and my battery at 10%..

I would say not worst than 162 at all

In addition with 163 every micro lags is gone..this phone fly now lol. So I prefer 163.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Serious_Beans:
Yeah seriously there is absolutely no lag. This is the most lag free and smooth experience I've ever had on an android phone. Amazing work. Time to get an extended battery :D
[Samsung Galaxy Nexus] metalspring:
On r163, 5 hours music playing with screen off, almost 1.25 hours screen on time at 50% battery and badassbattery stats says I should have over 2 hours left

Not bad Franco, not bad at ALL
[Samsung Galaxy Nexus] raycaster3:
(Running 163 512gpu)

Weird to hear that ppl are having drain issues with 163 as I am actually here to report that I'm getting some of the best battery I've had since coming over to this device. I've gotten quite a bit more out of my phone so far today than usual and have used it the same as I always do. Thanks again
[Samsung Galaxy Nexus] Dave778:
#162 i was getting 3-4 signal bars #163 I am getting 1-2 signal bars

Anyone else getting a weaker signal?
[Samsung Galaxy Nexus] metalspring:
Kernel should not effect signal and I'm getting the same signal strength as always
[Samsung Galaxy Nexus] holyzombiejesus:
I honestly think franco could make no changes at all and people would still be posting on here going "ZOMG BESTEST KERNEL EVAR!!!!111". In fact, after releasing hundreds of kernels over 3+ devices, I wouldn't be surprised if he's done it before just for the laughs.

163 is working quite well - very snappy and certainly better battery drain over stock. I loved your work on the p500 and I'm glad to see you doing great work on the Nexus as well franco, bravo.
[Samsung Galaxy Nexus] Vangelis13:
He has done it. :p
[Samsung Galaxy Nexus] Dave778:
I just flashed back to #162 & my signal is back to 3-4 bars. Dunno why this is happening but on #163 I get only 1-2 signal bars.
[Samsung Galaxy Nexus] andQlimax:
Maybe u only needed a reboot.. try again 163..its quite strange that ur signal is influenced by the kernel

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Dave778:
same thing. Did i mention im on a AWS provider that has weak signal to begin w. Thats why I'm so eager to milk as much signal as I can. Im using UGLC1 radio w AOKP #36 & Franco #163. Givin my ****ty provider I get better signal w #162 :(

but #163 is smoother :(
[Samsung Galaxy Nexus] raycaster3:
That would be an interesting experiment. I tested kernels quite often for TDJ on mytouch4g, sensation and sgh-t989, and I'm here to tell you haters will hate and fan boys will love whatever is released. Thank goodness there are some who can report issues and real results. While "best battery life since I came over to this device" sounds trite, it literally is what I'm experiencing as there have been builds that have been quite battery hungry. I just know what to expect from my setup and have a good idea what to look for. Guess I'm getrin a little long-winded, just not a fan of being considered a blind follower.
[Samsung Galaxy Nexus] nklenchik:
Coming back to Franco's kernel and using his recommended color settings...

Does the screen look a bit green? Has anyone mastered the color settings? lol
[Samsung Galaxy Nexus] :
Im using

Red 215

Green 225

Blue 300

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] neos_83:
Haha that would make a good meme
[Samsung Galaxy Nexus] franciscofranco:
I already done that experiment a few times, I always take a few beers and have a god damn laugh for a few hours ;)
[Samsung Galaxy Nexus] metalspring:
I would definitely not use those settings...high color multipliers risks screen burn in, I think I heard anything over 210 is not good

Why raise them up when you can calibrate them lower the same way and just have a darker screen which can be adjusted via brightness?
[Samsung Galaxy Nexus] Razer(x):
Actually i really loved trynity kernel colours, even if i don't know rgb and gamma values. White was really white
[Samsung Galaxy Nexus] metalspring:
I would definitely laugh if 163 was really the same as 162 lol
[Samsung Galaxy Nexus] Razer(x):
Franco, what about adding some color presets? like the one in voodoo app for example
[Samsung Galaxy Nexus] minooch:
Hi everyone,

Just a quick apology for the issues that happen last night with my server. I'm stilling looking as to why it took an extended toilet break. & a thank you for anyone who posted a mirror. Was a shame that I caused some of you, to miss out on flashing Franco's awesome kernel.

Cheers,

Minooch

EDIT: I just found out that my host restarted the server - Apologies again
[Samsung Galaxy Nexus] nklenchik:
I actually just raised the blue gamma... As it turns out I can't really tell how blue white is :p
[Samsung Galaxy Nexus] Bonvaz:
Yeah but over 210 is more bright the screen,and is useful imho..I have to ask if anyone is really sure about this theory of screen damage with color over 210..because I only heard people say" I heard someone say....."..... franco do you know anything about that? Oh,163 is great ;)
[Samsung Galaxy Nexus] suprafreak1000:
LOL epic
[Samsung Galaxy Nexus] metalspring:
From cmplus's (ch33kybutts kernel) script for kernel settings-

The 2100000000 would be shortened to 210 in francos app

(btw thanks Franco for making setting these values easier than messing with those big numbers)
[Samsung Galaxy Nexus] SupWiz17:
Have had horrible battery life today. Dunno yet if it's bad signal or something keeping the phone awake but I'm gonna give it some more time. The only thing I noticed with r163 is that I got artifacts again with this nightly and that hasn't happened in a while.
[Samsung Galaxy Nexus] nklenchik:
I wish we had a 1.3. That would be absolutely perfect if you ask me
[Samsung Galaxy Nexus] EnhancerFIN:
Now it´s my time to cry :/

I´ve been using nightly 141 of this kernel, gpu 512mhz version of it. Today I updated my phone with the latest cm9 nightly, it wen´t fine. Then I updated the kernel using the kernel updater, used the auto-flash to flash the latest nightly, and chose gpu 512mhz version as earlier.

Phone rebooted after flashing the kernel, had few graphic glitches, rebooted again and started boot looping. I wen´t to recovery to flash the cm9 again, but the recovery crashes also with these graphic glitches on the screen. I´m also unable to restore my nandroid for the same reason, the recovery crashes. I adb pushed a lower mhz gpu version of the kernel to my sd card, successfully flashed that via recovery but no help, still unable to boot, reflash cm9 or restore a nandroid.

Is my only choice to use factory image to wipe entire phone? Or is there a way of doing the same without wiping the sdcard? I have everything else backed up from the sd about a week ago, but I would need to get the nandroid I made today out from the phone, so I could restore it after using the factory image.

Please help :/
[Samsung Galaxy Nexus] metalspring:
It would be nice if Franco used the actual values instead of those though I can see why he simplified it. By the way the "real" values are 0-10, with 5 being a gamma of 1...so basically 1.2=6, 1.4= 7, etc.
[Samsung Galaxy Nexus] nklenchik:
Haha I know it's like that in Glados control... Otherwise a 6.5 would suffice well
[Samsung Galaxy Nexus] metalspring:
Try flashing another kernel via fastboot , I'd suggest leankernel since all it is is the boot.img, which you just extract and flash that (if you don't know the commands then use one of the galaxy nexus tool kits)

you can also try reflashing the recovery via fastboot or even switch recoveries at least temporarily (team win recovery for example)

Otherwise you may need to go to stock, since Franco has fsync disabled any unexpected reboot may cause data loss which can possibly ruin a recovery or rom (or both?) Shouldn't be permanent though
[Samsung Galaxy Nexus] willl03:
Not sure if rom or kernel, but after a day of usage of 163 my phone powered off because the battery was dead, when I plugged it in and tried to start it again the phone was stuck on boot animation (it kept going forever). I pulled battery, cleared caches, flashed other franco kernels, and the problem continued. Doing a full wipe / factory reset fixed the problem

I ran 190mhz min freq for the first time and it ran well so I set it on boot in Rom control - performance. Could my phone be able to run 190mhz well but not be able to boot it?

I'm running Liquid 1.4.. tempted to try CM9 in case this is rom related

Any clue what could cause the problem at this point in the booting process?
[Samsung Galaxy Nexus] metalspring:
This could also be an issue with fsync making you lose rom data somewhere, but try to reboot with 192 set at boot on full battery to see if it will boot

I just had mine power off on liquid 1.4 too and then power back on with no issues at 192