yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
I'm gonna release r166 in about 15 minutes. I got some confirmations from Greg White (the sdcard binary hack author) that raising the wi-fi voltage back to stock 2.0V it fixed all the signal problems he was having. Just gotta prepare everything for release, stay tuned.
[Samsung Galaxy Nexus] 88888:
Thanks, Franco, cannot wait 166...
[Samsung Galaxy Nexus] franciscofranco:
r166

* Wi-fi voltage back to stock - this should fix the signal issues from the last builds because it seems this might be connection to some power rail related to the GSM/CDMA chip - thanks Greg for sharing your experience with me

* GENTLE_FAIR_SLEEPERS by default

* HID devices drivers added again to the kernel

* A small OMAP patch to fix a bug in the DVFS interface
[Samsung Galaxy Nexus] galakanokis:
I think the echo command that Franco posted has fixed my data drops on 165.

I was getting drops quite frequently from wake to the middle of using the phone. Quite often my phone would come up with an indicator that my call forwarding was enabled (I have never touched this on this phone) and I would noticed no wifi/data/and an "x" in my signal icon. Sometime it would come back on its own other times required a reboot. After doing the echo first thing this morning after three drops in an hour I have not had a single one in 7 hours.

I also tested other ROM/kernel/radio configs and my common denominator was the 162-165 kernels. I also played with various voltage settings and min clock speeds with not luck.

Phone is running great right now with no issues.

Thanks Franco your work is appreciated. I wish I had you on the cappy that I had for years!

Of course, took me an hour and a half to get that post out and he has fix already. Thanks Franco, fantastic support.
[Samsung Galaxy Nexus] BigBake88:
Franco, haven't the wifi voltages been your own custom voltages for a while now? Why all of the sudden do you think this is happening?
[Samsung Galaxy Nexus] franciscofranco:
Nop, I only started to decrease that voltage since r156 and before that I never seen a signals/wifi problems like we've been seeing in the last 2 or 3 nightlies. I want this stable, even if that means not undervolting something. I can't afford 10% of my user base (that is pretty big at this point) to have instability what so ever.
[Samsung Galaxy Nexus] AdamZA:
Guys, would just like to ask a question - I know that it doesn't belong in this thread really but I know so many of you will be able to answer it.

I've always made sure not to overcharge my phone/tablet/camera etc to prevent from lowering the capacity of the battery and preserving it for longer. I know the latest batteries are designed to prevent that damage from occurring but I've still never left my phone to charge overnight for example even though it'd be so much more convenient for me to do so.

Just wondering whether you guys think it's safe to leave our Galaxy Nexus' to charge overnight and trust that the battery isn't being damaged? Is overcharging a thing of the past now?

Thanks
[Samsung Galaxy Nexus] chlehqls:
I wouldn't worry about it. Unless you're planning to keep this phone for the next two years or so with the same battery, it more or less won't be a big issue. Plus, replacement batteries will be relatively cheap by the time your battery is showing signs of decline.

This is where replaceable batteries come in handy. :D
[Samsung Galaxy Nexus] franciscofranco:
Just let it charge and don't over think or complicate what is easy. Just a free tip.
[Samsung Galaxy Nexus] simms22:
truth.

chances are that your battery will far outlive the life of your phone anyways, even if you somehow reduce the life of the battery. ive been charging my battery until full, even over charging it, on my g1's, og droid, nexus one, nexus s, and galaxy nexus.. and all my batteries are still good(except my og droid, but thats just because it fell out of my backpack and i lost it).
[Samsung Galaxy Nexus] LifeInAnalog:
... Just flashed r166...I've never had such bad battery life and data drops, I'm going back to r165!

...just kidding.

r166 flashed and fingers crossed.
[Samsung Galaxy Nexus] stunndd:
Could just be a fluke but for the past 15 minutes or so since flashing 166 I've been getting a consistent 4g signal where I'd hardly ever get one.

But either way thank you for all your hard work and trying to keep all of us happy.
[Samsung Galaxy Nexus] EnIXmA:
Getting 4 bars in my basement as opposed to one. Wow r166
[Samsung Galaxy Nexus] leos0000:
R166 really super fast :)
[Samsung Galaxy Nexus] craz6r:
cm9 20120516

kernel 163

BaseBand XXLA2 - came back to this radio because RIL didn't match

Tmobile

So far excellent battery, maybe one data issue with other radio where the bars are all gray. I just flashed back to this radio.
[Samsung Galaxy Nexus] opethrocks:
How do i check to see if my baseband matches my RIL?
[Samsung Galaxy Nexus] celyst:
Use GetRIL from Play Store.
[Samsung Galaxy Nexus] LifeInAnalog:
.. GetRil.. In the Play Store
[Samsung Galaxy Nexus] gknnn':
**battery_franco**

ROM : RasCream

KERNEL # : 165

GSM/VERIZON/SPRINT ( 3G/4G/.... ) : GSM

BATTERY TYPE : 2000

BATTERY LIFE/SCREEN ON : 10h 4m / 8h 8m screen on

BRIGHTNESS : 50% on day, at night full down

MINFREQ: 192 / MAX FREQ: 1036 / GOV: ondemand

SMART REFLEX Y/N: Y

HOTPLUG: its automatic / CPUMODE: Dualcore / POWERMODE: Powersave

APPROXIMATE AMMOUNT OF DATA USED ON WIFI/3G: not looked

WIFI/BT/GPS/NFC ON ? : most time WIFI (when wifi than no mobile data), NO BT/GPS/NFC

OTHER SETTINGS:

SMART USAGE DESCRIPTION: Normal use much texting some tapatalk and surfing

NOTE: I just changed the ROM like you said on G+
[Samsung Galaxy Nexus] rogersnm:
As far as I know the power mode overrides your CPU Mode/CPU Freq/Governor settings so when you're in power save mode the settings you actually use are Single Core/192-1036/Lazy.
[Samsung Galaxy Nexus] gknnn':
no first i set the power save and then i change the other things so i overwrite the stock power save setting.
[Samsung Galaxy Nexus] stellaryt:
Signal is stronger than before here.:D
[Samsung Galaxy Nexus] rogersnm:
You would have to do that every time you boot as it defaults to the power save settings on boot.
[Samsung Galaxy Nexus] CCaaNN:
I had some heat issue with165 and while typing,i had some sensitive problems.i dont know proper word maybe :D but touch response was not as good as other kernels with 165.now trying 166and looks like doesnt have this sense problem
[Samsung Galaxy Nexus] Treatcon:
Makes sense, my signal loss problems were getting better as every time you increased the WiFi voltage. At the time I didn't put 2 and 2 together. I thought it may have been newer releases of AOKP. Will give it a few days and report back. Thank you.
[Samsung Galaxy Nexus] Diger36:
Double post.....
[Samsung Galaxy Nexus] Diger36:
No you don't, I do exactly the same and it stays on boot. Try it, you'll see.
[Samsung Galaxy Nexus] Bonvaz:
+1.
[Samsung Galaxy Nexus] rogersnm:
I did, it didn't :(
[Samsung Galaxy Nexus] gknnn':
do you set "Set CPU settings on boot"?

Dont set power mode on boot, only set CPU settings on boot :)
[Samsung Galaxy Nexus] rogersnm:
Yep, I had that checked. I just tried again and it seems to work now, it might have been a bug with an older version of the updater app (I last tried a couple of weeks back)

(or maybe I was just doing it wrong xD)

It does raise another question though; If you don't set the power mode on boot, and you override the governor, number of cores and cpu freq, what changes does it actually make?
[Samsung Galaxy Nexus] CaspaTheGhost:
Had a couple of SODs on r166, both whilst on charge and in between a bit of Boid use. I've switched to 384 as for the first time in as long as I can remember I've had a few artifacts on boot with 512...

I'll grab logs if I get SODs on 384...

Can't test the wifi changes until Monday when I'm back in the office.

Battery test will be tomorrow as I'll be recovering from tonight and therefore indoors all day!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] xyzulu:
So far for me.. 166 is going well.. no data drops, battery is not to bad as well.
[Samsung Galaxy Nexus] marshy73:
Just a report that myself and another friend on 166 still experience Data drop. Now observing if it's frequency of occurrence is better or worse off than pre 166
[Samsung Galaxy Nexus] renna1992:
i have data drops with 166 too.

latest european baseband, rascarlo rom.
[Samsung Galaxy Nexus] Claus1221:
+1 to the signal improvements on #166. The signal now switches between 3 and 4 bars, I've never had 4 bars close to my desktop.
[Samsung Galaxy Nexus] Lambetts:
Peeps,

Getting laggy pattern unlock? Asked first in AOKP thread and they mentioned its a kernel issue? Which I though was strange. Any settings that could cause this? Even something in the Franco app? Only happened like half a day after flashing M3... again. Haha. Still seeing which build works the best, unfortunately still get choppy calls....

Also my battery stats graph is pretty weird. Like goes up a few percent every now and again, like its trying to adjust...

Is it best to after wiping batt stats to give it a few days? I'm assuming so.

AOKP M5

Franco M3

XXKK6 Radio

1750mah Batt

Thanks in advance. :-)
[Samsung Galaxy Nexus] zephiK:
using any profiles? what is your lowest frequency?

set lowest frequency to ~726.. make sure u arent on 128
[Samsung Galaxy Nexus] Lambetts:
I actually did a fresh install and haven't installed the app. Wanted to see how it went without messing with it too much. What's the default? I'm assuming its your min frequency? Min is 384 -1228.

Thanks for your response.
[Samsung Galaxy Nexus] grognaz:
is it a known issue that color settings reset on reboot with cm9? and if so, is there a workaround like for the frequencies/governor?
[Samsung Galaxy Nexus] CaspaTheGhost:
Last time I checked it was 384/1228 and OnDemand.

As I said in the other thread, I'm running r166 and no lag at all.

R166 sorted the unlock lag and 729 min on Interactive guarantees no wake lag for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Theshawty:
How much more battery do you think 729 Mhz (min) will drain? If overclocking from 350-ish?
[Samsung Galaxy Nexus] mikespe:
Franco, I have a feature request for your app...any way you can put a backup feature into the app so we can backup the last known working kernel/app settings in case something goes wrong with the latest nightly? I have never had anything happen thankfully, but things can always go wrong. This way, worst case scenario we can go to recovery & flash the last know working config/kernel. Probably a lot of work on your part to construct but it could be a lifesaver for some?

Thanks for your work!
[Samsung Galaxy Nexus] dracon6ai:
Just out of curiosity, since wifi voltages are tied in radio voltages would that mean that we can over voltage it past 2.0 so it might have a chance to boost radio signal far stronger than its ever been? While also giving the chance to blow stuff up of course but that's what makes this fun :-)

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] franciscofranco:
Its not a bad idea. I know Ezekeel programmed something similar and I think its a really useful feature. I'll strongly think about it :)

I didn't say it was tied to radio voltage. I said there might be a possibility according to the info I gathered. Over volting might not be a good idea at all.
[Samsung Galaxy Nexus] stunndd:
With 166 set to power saver my phone only dropped 2% over night (6 hrs 45 min) not too bad.

And I've only had one data drop but when it came back it had quite a bit stronger signal.
[Samsung Galaxy Nexus] hotnikkelz:
I'm going to try that as I get around 8% bleeding overnight :-)
[Samsung Galaxy Nexus] ms0chez:
Really? I think that about 165. 165 was really smooth and fast. And for some reason I got better wifi signal on 165. That could just be a coincidence though. 166 is giving me some lag.

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2
[Samsung Galaxy Nexus] leos0000:
No man... for me r166 512 gpu so ****ing fast and stable good signal wi fi and all ..... i use paranoid android rom
[Samsung Galaxy Nexus] Theshawty:
If I've understood it correctly:

Power Mode makes use of both cores at 129/1344 Mhz

Power Save makes use of only one core and at a low clock

Music Mode makes use of one core and at a slightly higher clock than power save

Balanced makes use of both cores at normal clock

Correct me where I'm wrong.
[Samsung Galaxy Nexus] Timmyfoxeh:
Request for your app:

Ability to make custom profiles? That way you can easily save your clock and gov settings and switch between easily depending on what you want. Or say if you'd want to customize the existing profiles (Maybe customize the "balanced" profile and use 1228 MHz rather than 1036 for an example).
[Samsung Galaxy Nexus] franciscofranco:
Music mode its dual core 192mhz-384mhz. Single core with those low frequencies had SoD and lag all writen over it.
[Samsung Galaxy Nexus] franciscofranco:
Thats planned indeed.
[Samsung Galaxy Nexus] Theshawty:
Thank you for correcting me. :)

I take it setting to music mode when going to listen to music for several hours and then setting power save over night will save a ton of battery?
[Samsung Galaxy Nexus] Sveke:
That's impressive but what the **** were you doing for 8 hours straight on your phone, it was only up for 10 hrs?
[Samsung Galaxy Nexus] daddymatt:
Hey Franco, ive had some screen flashes since last night when I flashed 166... I'm no dev and have no idea what causes what... so I don't even know if that would be kernel related. What I mean by screen flashes is almost like a screen shot is being taken.. just a whole screen white flash.. and its not all the time.. I rebooted my phone and when I unlocked it the first time it did it. After that maybe every 6 or 7th time on unlock. If its not kernel what does it sound like to you that it could be? I'm not real sure where to start troubleshooting.. I have aokp 37 clean flashed, 512 166 (I've used 512 since 1st available with no problems), the CPU is at 12xx, on demand, no other tweaks.
[Samsung Galaxy Nexus] odin13:
And screen usage around 80% so he probably just let the phone lay on table with screen on :p

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] jkoljo:
Got a signal drop with 166, AOKP b37. All stock settings, full HSPA+ network signal before and after the drop.
[Samsung Galaxy Nexus] jnr21:
If someone have signal drops, and changing radios, frequencies etc doesn't help, i made simple workaround with tasker. It informs signal lost in statusbar, plays notification sound/vibration, writes every signal drop to log and reset network automatically.

I know that there's signal alert apps in play store, but with tasker you can modify things more. There might be better ways, but this works nice.

Edit: I has few bugs, i think it's better now. Link updated.

http://db.tt/oenB14gZ
[Samsung Galaxy Nexus] Theshawty:
What to do with that file?
[Samsung Galaxy Nexus] emerica243:
Min screen frequency not working? I have it st to 192mhz yet cpuspy shows no usage at 192
[Samsung Galaxy Nexus] jnr21:
Install tasker, put my file to /sdcard/tasker/profiles and then import. You may need to edit notify sound path and notify icon.
[Samsung Galaxy Nexus] Theshawty:
First I may need an actual notification sound and icon to use :p

Care to share yours?
[Samsung Galaxy Nexus] jnr21:
I'm using this sound http://db.tt/sCfRrSSJ

You can find nice icons for tasker from play store, just search "ipack", i'm using holo light ipack.
[Samsung Galaxy Nexus] BigBake88:
+1 I noticed this as well yesterday when I was playing music w screen off
[Samsung Galaxy Nexus] krex:
..or there could be a setting for a path, where we can choose for flash from nightlies previously downloaded.

It could be the same practically where we download to. And it could give possibility to rollback even more than one step if it needs, or to make comparing tests simply.

Oh, I almost forgot. Thanks for r166. It is the greatest since r160 (aka999)!
[Samsung Galaxy Nexus] aquavalanche:
regarding data drop, i still quite don't understand.. i got drop today.. my RIL and baseband is XXLA2, i already put min freq to 729mhz..

is it okay if i change the baseband to UGLC1 (not matching the RIL)?

sorry if it's a bit OOT
[Samsung Galaxy Nexus] CaspaTheGhost:
Not enough that you can notice a difference. Its my standard setup and has been for ages.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dpaine88:
Agreed

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dspcap:
I notice my signal drop when I leave my house and get out of range from wifi. Doesn't go from wifi to 3g.

I read about ten pages back and having a hard time following the conversation. Does anyone have any good suggestions?
[Samsung Galaxy Nexus] Theshawty:
So basically "full power" mode in the Franco app?

Another question. Do you think it saves a lot of battery having the "power save" mode set during night? From say 10 pm-ish to like 7 am-ish?
[Samsung Galaxy Nexus] melvie:
Had the same problem, flashed XXKK6 radio and the problem is gone!
[Samsung Galaxy Nexus] chlehqls:
Just had a random signal drop while trying to send a text to my friend. I normally don't post problems because I never usually have any, but just thought I'd report in.

Otherwise, this kernel is a beast, enough said.
[Samsung Galaxy Nexus] BrUhNiGGs:
I always get signal drops out of nowhere. Not sure what causes it but it never really used to happen as often as before. Maybe my device is defective, but the hell with that, im not going to get a Verizon Like-New replacement. Had the worst experience with that :p
[Samsung Galaxy Nexus] Theshawty:
I've heard a lot of stories about Verizon and their refurbs :p
[Samsung Galaxy Nexus] shilent:
The same seems to be happening to me. Toggling airplane mode fixes it. I'm running 165 384, which version are you on?
[Samsung Galaxy Nexus] Bavilo:
I've also gotten a few drops on r166 :(
[Samsung Galaxy Nexus] beama:
Hi im using 166 and im not sure about the data drops. Wifi is okay now, no drops, but 3g/normal signal is bad and I have some drops, or bad signal quality.
[Samsung Galaxy Nexus] duowing:
Yeah you can use UGLC1 even though it doesn't match the RIL. I'm using it on my Nexus and it seemed to improve some of my signal issues.
[Samsung Galaxy Nexus] Diger36:
Yesterday I had data drops on r163 and r165 with AOKP about every 1 - 2 hrs. Today, with r166 and Rascream: Not one single data drop.

For me the problem seems to be solved (although my network bar in the usage is almost nowhere dark green and I've been running around today so coverage shouldn't be all that bad). Anyway, didn't bother me besides a little slow data but that could have so many causes....

Thanks Franco!
[Samsung Galaxy Nexus] Treatcon:
Almost 12 hours and no signal drops yet! I have better GSM and data signals as well! Looks very promising so far. I setup LightFlo to notify me of network signal loss just so I can see and track when/if it happens. Thanks for all your work Franco!
[Samsung Galaxy Nexus] agaruba:
Using the utility, my changes to the colour of the screen revert every reboot. The gamma stays the same but not the others. Is anyone else experiencing this?
[Samsung Galaxy Nexus] mazubo:
+1 here
[Samsung Galaxy Nexus] The Gingerbread Man:
Do a nandroid back up before flashing, if goes tits up restore boot img

Sent from my Paranoid Nexus
[Samsung Galaxy Nexus] beama:
Here too
[Samsung Galaxy Nexus] BrUhNiGGs:
Yup, had one for my OG Droid and everything was just messed up. My gnex is only 1 month old and I guess I got the bad batch. I'm still going to keep it for 2 years. I can live with the data drops until something magical can happen. Verizon's refurbs are TERRIBLE.
[Samsung Galaxy Nexus] Puzzlegirl:
Yes, me too.
[Samsung Galaxy Nexus] CaspaTheGhost:
Again, I don't think it will make loads of difference as it will be sleeping most of the time.

This is how today is going so far, been out for the last hour otherwise at home on Wi-Fi.

View attachment 1086620

View attachment 1086621

Mine all stick fine. Weird.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kylebarendrick:
Last few builds I've had quite a bit of lag in the launcher (nova) and the phone was getting very hot to the touch. Both are much better with r166. Four what that's worth...
[Samsung Galaxy Nexus] nodstuff:
I'm sure Francisco is busy watching the Eurovision!! ;)
[Samsung Galaxy Nexus] PrimeDirective:
what is the echo command to adjust gamma in init.d? also, someone recommended i try out 1.4. what are other's personal preferences?
[Samsung Galaxy Nexus] glennv17:
Not much use without a bug report or anything, but I had probably the weirdest bug since using this kernel. I auto-flashed 166 over 165 from franco's app, then after the phone rebooted I went into settings. I received an MMS, so I brought down the notification bar to view it but as I clicked it, the phone completely froze, put on a weird mix of the current screen and then rebooted. I'd be ok if that was the end of it... but after it rebooted, everything in my messages had deleted itself! All texts, all MMS (including the one I never saw).

I backed them up only two nights ago but it was still very odd and frustrating. Has anyone ever had this happen?
[Samsung Galaxy Nexus] wallendiaz:
Hi guys I would like to know some good CPU undervolt setting for NIGHTLY - 166, someone can help me??
[Samsung Galaxy Nexus] skdinesh:
So far no issues with r166. I checked and had an RIL Baseband mismatch to reverted back to XXLA2. Kernel is very responsive, especially switching between apps, closing launching stuff.

Experienced 5% battery drop over 8 hours of sleep which is very acceptable to me, especially now that the Wifi voltage is back to default. :)

Thank you Franco, Greg White and all the others who contributed. :)

Btw, I'm still wondering what the difference is auto flashing the kernel and using recovery? Why does the recovery mode optimise apps and state 'Android is upgrading' but auto flash doesn't?
[Samsung Galaxy Nexus] 6jaipur6:
Me too but i'm on cm9 Paranoid and I read about this is a cm9 rom problem.
[Samsung Galaxy Nexus] xyzulu:
As am I, good questions.
[Samsung Galaxy Nexus] Serious_Beans:
Anyone still having high temps? I'm around 44c idle and around 55c just browsing the web. Seems a little high to me, the back of the phone is pretty warm.
[Samsung Galaxy Nexus] SeanHacker:
its not really a question anyone can answer for you. all devices are not made equally. what may work for some, may not work for you. so you just need to do some trial and error to figure out what settings your device can handle and agrees with. :D
[Samsung Galaxy Nexus] drawde40599:
Franco app ur reading that from? Its normal, bout same as me, fyi, stock Rom and kernel get hotter than that; )
[Samsung Galaxy Nexus] dpaine88:
Yea I get about 60C+ browsing the web on 4G LTE

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] andrew53517:
I just can't win on the battery front no matter what I do :(

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] BigBake88:
I disagree. 55c does not sound crazy high, especially if doing some heavy browsing and playing games, but 44c with the phone just sitting there sounds high to me. IMO, phone should be below 40c when idling. Overall though, I haven't seen my phone get higher than 50c in a long time. Franco's kernels have been running really cool as of late
[Samsung Galaxy Nexus] swaser18t:
For some reason I can't send pictures on 166. Says not active in network I could on 165