yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Reviz:
My experience:

- Slim ICS 3.8 + r166 = OK

- Slim ICS 3.8 + r169 = NO SIGNAL

Now i'm on a trinity.
[Samsung Galaxy Nexus] droidgren:
I had the same problem, but a reboot fixed the problem.
[Samsung Galaxy Nexus] emd2009:
What's your rom of choice?
[Samsung Galaxy Nexus] jnr21:
I had signal drops with r166 and r169 but i didn't use 192mhz freq.
[Samsung Galaxy Nexus] theneighbor:
Check out the battery life on r169
[Samsung Galaxy Nexus] billouetaudrey:
And time screen on?
[Samsung Galaxy Nexus] franciscofranco:
Users with data drops please test this: https://www.box.com/s/7fm7y8y1m02vflv9sp3z

fastboot flash boot boot.img

It says #172 but this ain't labeled a true nightly version, I just need a quick test to see if we get that **** fixed once and for all.
[Samsung Galaxy Nexus] theneighbor:
Screen on..not much but this is still better than I've ever had...obviously Wi-Fi and limited screen on help
[Samsung Galaxy Nexus] billouetaudrey:
I post it on french forum and inform you ;)
[Samsung Galaxy Nexus] Benji1983:
you can get better battery live with deleting facebook app and friendcaster

facebook app has too many processes are running ^^

greetz benji
[Samsung Galaxy Nexus] nikulogical:
I just force close it when I'm done with itm
[Samsung Galaxy Nexus] sotoskawasaki:
Although I never experienced any data drops, I really wish that the issue is resolved. I can understand how frustrating it can be.

On another note, how is not having any warning during compile beneficial? From what I know on programming if you have an error then the source code will never be compiled. But having a few warning almost every time poses any threads and the program almost every time works as it should. So while I understand that in some occasions might not work as it should, I fail to see how this affects performance of battery time. I guess you are right. It is mostly for geeks.... :)
[Samsung Galaxy Nexus] metalspring:
Odd, I downloaded it and it says its called download.bin...do I just rename it to boot.img?
[Samsung Galaxy Nexus] Benji1983:
thats also a good way ^^
[Samsung Galaxy Nexus] jnr21:
Redownload it. It should be boot.img.

Edit: Or get it from my dropbox http://dl.dropbox.com/u/14648160/boot.img
[Samsung Galaxy Nexus] ferris2375:
Screw benchmark scores, the phone is clearly faster when overclocked. I went from 1.2 to 1.4 and the difference is obvious.

Still waiting for this kernel to support OC. :)
[Samsung Galaxy Nexus] Vangelis13:
If you're on 3/4g and in an area with bad coverage your phone will eat the battery as it just did.. Kernel works fine now, many of us have confirmed.
[Samsung Galaxy Nexus] DarthPiggie:
Does this kernel have GPU OC support?
[Samsung Galaxy Nexus] JCUK89:
Hey guys,

is it still recommended to delete that file in /system/lib/egl as it was in the earlier builds of this kernel? Thanks...
[Samsung Galaxy Nexus] inffy:
Was there somekind of point in your post?
[Samsung Galaxy Nexus] aron7awol:
Left my phone off the charger again last night with wifi on.

Lost 7% battery (91% to 84%) in 8 hours. Device was awake for about 1 hour out of the 8. This is much much better than my previous test, where the device was awake over 2 hours out of 8 and lost 25% battery.

Also, drain was consistently between 8 mA and 17 mA throughout the night. Nice work Francisco!
[Samsung Galaxy Nexus] MFD00M:
I had a similar experience....went to bed with 88% battery left and it dropped 7% in about 7 hrs. Battery usage showed my phone was "awake" with screen off two points into the night. Sorry, for some reason i cannot get my phone to take screen shots.

I checked better battery stats for wakelocks but i cannot for the life of me figure out what any of it means. Might as well be in a different language for me.

I should also note that i was on wifi the entire time, and i am running 7.1 kernel on demand with Toro AOKP build 11.
[Samsung Galaxy Nexus] franciscofranco:
Yes, it's overclocked.

No, just edit egl.cfg, search, thats been answered.

Thats fine, 7% in 7 hours is normal, no leakage.
[Samsung Galaxy Nexus] MFD00M:
Yeah, no complaints here. This kernel really smoothed out my phone and made it noticeably snappier. Again, great work!

I guess my real question was how do I identify partial and/or kernel wakelocks, if there was any?
[Samsung Galaxy Nexus] aron7awol:
The benchmark scores on this kernel at 1.2 GHz are indeed impressive, almost entirely due to its huge I/O advantage over other kernels. CPU-wise, all of the kernels are pretty much the same, but there's a huge difference between 1.2 and 1.35, especially during CPU-intensive tasks like web browsing. There's no doubt this kernel would be much faster with the 1.35 GHz step, and the difference in battery life would probably be negligible given the small amount of time the device spends at the highest speed step.
[Samsung Galaxy Nexus] idkwhothatis123:
I'm not trying to be that guy, but do you expect to include a CPU oc anytime soon? I understand 1.4 & 1.42 are temperamental for most people (not me thankfully) so I'm assuming the 1.35 step would be implemented.

I love the 7.1 btw, its fluid as all get-out. Thanks for a your hard work.
[Samsung Galaxy Nexus] gsxraddict:
+1 to this its very smooth at 1.2 not denying that extra speed step to 1.35 at least would be exceptional. I can't run 1.4 so not too concerned with that high.
[Samsung Galaxy Nexus] GchildT:
Yes,

If the ROM you are using has this file included either delete it or edit the EGL.cfg.

-Remove the "0 0 Android" line. (usually line 1)

---------- Post added at 10:07 AM ---------- Previous post was at 10:02 AM ----------

CPU overclock to 1.4GHz was shown to have minimal benefit. The last OC kernel was stable @ 1.4GHz on my device.

Current Kernel @ 1.2Ghz: Antutu - 6285 Quadrant - 3029

Last OC Kernel @ 1.4Ghz (4.0.1) Antutu - 6935 Quadrant - 3021

There is a slight performance increase, but not enough to warrant an OC.
[Samsung Galaxy Nexus] aron7awol:
What would you consider enough to warrant an OC?

Edit: Looking at your benchmark results, you saw a 10% increase in your AnTuTu score, which is made up of a lot more than just CPU tests, with a 16.7% OC. That's about what I would expect. The fact that your Quadrant score didn't show any improvement is more of an example of how crappy Quadrant is than anything else. I definitely noticed a difference anecdotally when I ran at 1.35 for an extended period of time.
[Samsung Galaxy Nexus] dario3040:
Keep in mind that 4.0.3 is faster, i don't know if it translates too well in benchmarks, but it is definitely faster.
[Samsung Galaxy Nexus] Enhanced:
Happy to report that with 9 hours idle (yes I sleep for 9 hours :)) I lost 5%. This is the same as stock.

Now I have normal battery life with great performance. Can't ask for anything else.

Thanks Franco!
[Samsung Galaxy Nexus] aron7awol:
I'm fairly sure the current GPU OC isn't working. In my testing, it didn't appear to be working in any of the kernels I tried.

I did see this quote from faux123 last night:
[Samsung Galaxy Nexus] jkoljo:
I am having some issues with MTP in the latest 7_1 nightly. The connection is pretty unstable, I have not modified my PC in any way. I also tried another PC, same issue. Then I tried nightly #5, everything worked great.

The issue is that my explorer.exe either crashes while waiting for my GNex, or it says that device malfunctioned.
[Samsung Galaxy Nexus] franciscofranco:
He's right, coolbho's gpu oc wasn't enough. What I did was enable the gpu OPP then in the gpu files I changed the clock to the desired, so I'm fairly sure mine is working.

No idea about that, I don't have a windows machine to test it and I havent changed any USB ****.
[Samsung Galaxy Nexus] Theshawty:
This data drop issue many seem to have, myself included, is this because of too low voltage for the radio? Maybe smartreflex turns the voltage down too low so it isn't sufficient to keep the radio going at full strength?

I may just be blabbering here, but this is what I read someplace else on another forum. Please correct me where I'm wrong.
[Samsung Galaxy Nexus] The Nexus Project:
I've abandoned 169 due to data drops

Sent from my i9250 (GSM) Galaxy Nexus
[Samsung Galaxy Nexus] drawde40599:
Only English, looks like, but Google it there must be a easy way to add a language
[Samsung Galaxy Nexus] renna1992:
will give this a try, thanks
[Samsung Galaxy Nexus] Reviz:
I rebooted twice then installed the trinity because i had to go out.

:(
[Samsung Galaxy Nexus] franciscofranco:
Until I get feedback from the kernel linked on last page theres nothing else I can do. I cant reproduce the data losses.
[Samsung Galaxy Nexus] renna1992:
works fine till now for me but i think we should wait at least a day or something?
[Samsung Galaxy Nexus] franciscofranco:
Yes, but some users got drops pretty soon after kernel flash thats why I said that.
[Samsung Galaxy Nexus] Flukester69:
GetRIL solved problem with data drops for me. Installed radio to match my RIL. Wish I knew about this app before.
[Samsung Galaxy Nexus] renna1992:
yeah i was one of them, so i thought its a good thing till here :D
[Samsung Galaxy Nexus] nodstuff:
Would sr be dropping core voltage a little too low??

Doesn't uv'ing core cause data drops??

Although if that is indeed true I'm pretty sure you already know all that! :D
[Samsung Galaxy Nexus] drawde40599:
Y didn't u just go back to last version that worked for u? I Don't understand y if u like this kernel u leave ....?
[Samsung Galaxy Nexus] willl03:
Had no signal on 169 using slimics 3.8, signal was lost a minute after boot and impossible to get back. I tried glashing franco 133, my regerence kernel, and the problem persisted. Had to do a full wipe, installed liquidsmooth 1.4 , franco 133 and modem just in case. Been good all day, 133 is still a beast!
[Samsung Galaxy Nexus] robto:
mmm .... similar process to this:

http://xdaforums.com/showpost.php?p=23305473&postcount=195
[Samsung Galaxy Nexus] eddie_gordo:
Hi there...

OMAP4 Gamma interface doesn't seem to be working for me. I was using nightly #162 and it was all good, now I've updated to #169 (512) and no matter what value I set on the OMAP4 Gamma interface, the screen just looks the same. Is it just me or is this something that you are aware? :)

Colors Multipliers and the RGB values work fine though.

Thanks and keep up the good work Francisco! :)
[Samsung Galaxy Nexus] mingkee:
Found a major problem on 169 with stock ROM:

Screen becomes totally yellow on maximum brightness.
[Samsung Galaxy Nexus] TheSobadef:
I was having signal issues on r165 and when I switched to airplane mode, I'd have to reset my phone entirely to get a signal again. r166 fixed that with the return to stock wifi voltage and r169 has been bug-free with outstanding battery life.
[Samsung Galaxy Nexus] Culex316:
I also have the stock ROM, turned up my brightness and yet the screen does not become ""totally yellow'' for me.

I am using the 180, 192, 200 RGB settings and -4, 0 ,5 gamma values and OMAP4 gamma interface is stock (I haven't touched it)
[Samsung Galaxy Nexus] mistermojorizin:
unofficial r172 seems to use higher voltages, runs hotter, and benchmarks worse. i mean i hope it solves peoples problems and everything, but i hope it's gonna go back to being lower voltage, lower temps, and higher benchmarks like 169

---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------

it happens when you turn the multipliers up. try going over 260 on the blue and brightness at 100% to reporoduce the problem.
[Samsung Galaxy Nexus] franciscofranco:
Regarding voltages I only increased vddmin to stock 830mV and 192mhz slot to 900mV, but SR calibrates to 840mV. The rest is unchanged in terms of voltage.
[Samsung Galaxy Nexus] Culex316:
Just tried it and see what you mean, but what's the benefit of setting it higher than the recommended settings (180, 192, 200)?
[Samsung Galaxy Nexus] sotoskawasaki:
Excuse me for the stupid question and sorry if it has already answered but does using color multipliers and color gamma values consumes more battery?
[Samsung Galaxy Nexus] gknnn':
i got a question: Is the Screen off max for example 192 also set when screen off at a call?
[Samsung Galaxy Nexus] franciscofranco:
If the screen is off it's off.
[Samsung Galaxy Nexus] gknnn':
Thanks for the fast answer!
[Samsung Galaxy Nexus] mistermojorizin:
400 @ 100% gives you much better usability outside, especially on a sunny day.

400 @ 0% arguably gives you the same usability and better battery life than recommended settings @ 30%. arguably
[Samsung Galaxy Nexus] nodstuff:
Also anything over 210 increases the risk of screen burn in, pixels dying etc.
[Samsung Galaxy Nexus] dracon6ai:
That's what warranties are for. Been running 350+ for 2+ months now with no ill effects and once I see one all I'll need to do is make a simple call to get a replacement device. Being able to see my screen perfectly in any condition is well worth the risk.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] fatappel:
So today was a bright sunny day in new york and my screen kept automatically turning yellow when using outside due to the known blue multiplier issue with r169. Back to r160 which has been nothing short of magic. Looking forward to the next test kernel release. Thanks.
[Samsung Galaxy Nexus] :
Wiped my rom an installed it again....runs great ! Really fast but still doesnt save the colormultiplers !
[Samsung Galaxy Nexus] mistermojorizin:
@ 0 brightness it won't burn in anything.

and i only keep on high brightness for short bursts in situations when i'm out in the sun. so i doubt that is long enough to burn in.

anyway, that's not the point. I mean thanks for the warning, it might help people that don't know that, but it's about a functionality that's not functioning right.
[Samsung Galaxy Nexus] franciscofranco:
#4.9

Galaxy Nexus changes only:

* Changed how we see cpu0 and cpu1 working instead of choosing a single or dual core mode. It's now simpler and very straight forward. We can also see them change of state according to the chosen power mode

* Added the options to download the .zip packages of Imoseyon's LeanKernel to the sdcard instead of having only the Auto-flash option

* Minor fixes across the app
[Samsung Galaxy Nexus] wedz:
RIL

My opinion regarding this RIL & data drop stuff is that I'm sure there is some need to have separate RILs, but I don't believe this can be a reason for the data drops.

After all, this is application layer related framework, and it would be strange to somehow tie this to actual operation of radio. Moreover, it would be silly design from Android team to make some kind of dependencies to propertiary code (of baseband, that is), that they actually probably don't even understand fully, nor have code for.

Sure enough, RIL is used to command radio, maybe there are some interfaces which might not work in certain situations, but to cause these basic data drops... that would be strange.

Still, this is just an educated guess, I'll be happy to be stand corrected.
[Samsung Galaxy Nexus] jeetS:
Experianced a data drop today on 169... havent had one in months... flashed back to 162 (the last one I had on my SD card)
[Samsung Galaxy Nexus] neverhappy:
Guess I'm loosing my mind...

Went to the Play store to check for updated franco kernel updater app and it says it is not compatible with my galaxy Nexus?? First time I have seen this.
[Samsung Galaxy Nexus] FC1032:
169 is showing two problems with me.

*at highest brightness, the screen becomes yellow (mentioned). I lowered the multipliers and that's fixed.

*omap gamma interface doesn't do anything. :(

Also, the colour settings don't stick after reboots... but that's been here a while.
[Samsung Galaxy Nexus] franciscofranco:
Both bugs are already fixed on my local build.

As for the multipliers humm, they stick for me.
[Samsung Galaxy Nexus] FC1032:
Thanks for the reply, think I'll try to see if its just my app acting up.

Awesome work as usual :)
[Samsung Galaxy Nexus] CaspaTheGhost:
Wow, a great improvement for me today. Basically the same performance I get at home so wifi fixed at work for me.

The early reboot was flashing r169.

View attachment 1091602

View attachment 1091603

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BigBake88:
Still cannot see update in play store for Franco's newest update? Am I the only one? :confused:
[Samsung Galaxy Nexus] xyzulu:
Just install it again from play.google.com You'll then have the updated version installed.
[Samsung Galaxy Nexus] dpaine88:
So I do plan to do my own research but curious if anyone else more knowledgeable than me has any technical input.

From setting the Max freq to 1334 instead of 1228 is there 1) a noticeable speed diff and 2) a noticeable battery dip?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] BigBake88:
Thanks. Two min after I wrote that, the update popped up! :)
[Samsung Galaxy Nexus] Hanny:
Hi franco. Thanks for your attempt to fix the data drops for us annoying unfortunate users to satisfy not only the general but also the most of us :) Thanks

Since my SIM card reinsert, i did not encounter any signal/data drops (until now) for 18 hours. Quick info - im with 169 and my baseband/RIL mismatch.

So I assume wifi increased voltage has solved my problem but my phone just need a clean reconnection with the carrier's signal? I cant say i confirm that. However, I guess I will still need to experiment with my assumption for one more days so I cant stop it and flash your unofficial r172 yet.

Also, I have not used 192mhz slot for some time so I guess the 192 OPP table "fix" isnt applicable in my case. But the vddmin might be.

If during my experiment with 169 + SIM reinsert and i got one single signal/data drop, I will immediately flash unofficial 172 and test it out.

Should you instruct me to cut the experiment (cuz it maybe useless from your perspective) and try the 172 right now, I'll do so. :) Thank you franco

EDIT: whooops, got a data FREEZE 30 mins after typing the above. (icon is here, signal is full, color is blue but NO internet until i turn off and on mobile data.

flashing unofficial r172 right now and will report back!

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

For the performance, no one can prove it as you use different apps and you have different background services. But of course in theory there are certain speed increase (but not "significant") when overclocking. So in this case, benchmark might satisfy your curiosity (just curiosity. it doesnt mean real performance)

But for the battery, it is reported that there are quite a big difference between 1036 and 1344. Not much users have compared 1228 and 1344, though. Thats why franco puts 1036 but not 1228 as max if you switch to balanced power mode. :) hope i solved your question.
[Samsung Galaxy Nexus] Lambetts:
Hey guys.

Can I get a r163 stock gpu zip? I've looked but I can only seem to find 384 and the 512.

Thanks guys.
[Samsung Galaxy Nexus] dpaine88:
Only milestones have stock gpu

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Lambetts:
Yeah I thought so. Was just reading a post Franco made and basically that 384 is a waste of time, so confused why there's only 384 and 512.in his builds. :-)

Any way I can do this myself? With the app even? I'm happy with 308 (307.2)

Thanks again.
[Samsung Galaxy Nexus] Hanny:
Hi, only milestone builds will provide you a stock GPU frequency. Yes, only and will never ever forever change. Same for the reversed question - (Can i get 512 gpu on milestone?)

If you would like stock GPU over all the changes made since M3 to now, you may simply go for M3. However 384 will not harm your device as much as you are aware of. Just my personal suggestion :)
[Samsung Galaxy Nexus] willl03:
384mhz is the stock speed of hour graphic card hardware, only lowered by google to 300mhz. No harm in running 384mhz, slightly better performance for minimal battery consumption like 12h up time vs 12h5min up time
[Samsung Galaxy Nexus] Culex316:
I set my min to 192mhz, max to 1228 mhz and put ondemand and (with my extended battery which has 2600Mah capacity), I am at 64% with 2h 47min screentime and have been on battery for 13h 27 min and on wifi and performance is great so I believe ondemand is the best balanced governor imo...interactive drained my battery more

384Mhz is actually the speed the GPU in the Nexus is originally supposed to run at, it was just underclocked to 304Mhz and set as the "'stock"' speed...
[Samsung Galaxy Nexus] Lambetts:
Thanks for your responses. :-)

I don't mind either way really. The GN is 'stock' 380mhz and 1.5mhz. For sure.

I just was reading what Franco mentioned, that it does use a little more power for almost no performance boost. Just what I read.

Or, maybe Franco could add what glados has in his app, the choice to change to either 3 (307.2, 384, 512). Just an idea. Would be pretty cool.
[Samsung Galaxy Nexus] nodstuff:
He got rid of on the fly gpu speed change because it was causing problems for some people.

Having different nightlies solved that.
[Samsung Galaxy Nexus] BigBake88:
See but I don't understand this. If someone is having issues with a certain gpu clock speed, wouldn't it make more sense to just change the setting in the app as opposed to flashing a different kernel?
[Samsung Galaxy Nexus] nodstuff:
The code to allow on the fly gpu speed change was what was causing problems I think.
[Samsung Galaxy Nexus] BigBake88:
Hmm...well ezeekel has it in his app, and I have not heard of issues in his app. So, it can be done. Just my 2 cents :p
[Samsung Galaxy Nexus] nodstuff:
It was in Franco's app too, but he got rid of it.

Is it that hard to pick a gpu speed and flash that kernel?

Seriously?
[Samsung Galaxy Nexus] metalspring:
Yes it causes issues...francos kernel is the only one I can run 512 gpu on even with the same voltages and his is the only one with a set gpu speed at 512 rather than a selectable 512 gpu slot
[Samsung Galaxy Nexus] vomer:
Are signal issues gone from 169?
[Samsung Galaxy Nexus] BigBake88:
For someone who can run either 512 or 384 with no issues, it would be nice to pick the option in the app depending on that days usage, rather than flashing a different kernel. No, I'm not being lazy or picky, just makes more sense to me...unless there is no way possible to code the app to allow for on the fly gpu clock w no issues. Love the kernel, Franco. I ain't going anywhere :D
[Samsung Galaxy Nexus] willl03:
Worse than ever for me on SlimICS, had to wipe and reflash all to get it working again.. holding to 160 until it's 100% fixed, great release
[Samsung Galaxy Nexus] jnr21:
No signal/data drops with #172 (flashed when it was released), i will report again later.
[Samsung Galaxy Nexus] :
No drops for me either on #172.. All good for 5+hrs..
[Samsung Galaxy Nexus] Lambetts:
+1 Just saying. :-)
[Samsung Galaxy Nexus] mistermojorizin:
multipliers are good. Release the cracken!
[Samsung Galaxy Nexus] ranasrule:
172 ??? Where did u guys get that ? All I see is 169 on the website:confused:
[Samsung Galaxy Nexus] parkson:
Running r169 384 on aokp b37 with 7xx-12xx mhz conservative gov for old time's sake and must say I've never felt conservative so snappy and smooth before.

What are thoughts on upping screen off max freq to 1036? Worse for battery?

*edit* Also, I find these color settings best, if anyone is looking for a nice starting point. I adjust them with the franco.kernel app, which can be found in the play store.

Color multipliers:

R:150

G:160

B:210

R,G,B: 0,0,0

Gamma: 1.0 (none/default)

I find this gives me the best "true" color without oversaturation, like many happen to enjoy. The white is perfect in my eyes. No cream color and not "so white that it looks blue (overcompensating?). Hope you enjoy it as much as I do.

Thanks for your work, Franco!
[Samsung Galaxy Nexus] jnr21:
Read few pages back. It's just test kernel, franco's attempt to solve data drop bug.
[Samsung Galaxy Nexus] ranasrule:
are gamma settings also fixed ?
[Samsung Galaxy Nexus] franciscofranco:
No kernel interface to change gpu clock on the fly = no app interface to change gpu clock on the fly. Been answered 20 million times already.