yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] duowing:
I had the same thing happen to me today. Although it will be a little harder to pin as I just updated to the 2012-05-29 build of CM9 along with 173 nightly today. I left wifi on then went out of range. When I checked my phone later it still had a mobile connection, but no data. I had to switch airplane mode on then off to get it back. I also rebooted a couple times and each time I got weird carrier names. AT&T@@@. One time I just got @@@, something else, then finally rebooted again and got the normal HOME that I get for Straight Talk. Not sure if this is a kernel or ROM issue, or maybe Straight Talk was just being wonky. I'm back on WiFi now at home so I'll let it go out of range later and see if it does the same thing. Otherwise I encountered no issues with 169.
[Samsung Galaxy Nexus] RayGarden:
Kernel Leftovers

http://www.xda-developers.com/andro...l-leftovers-on-the-international-galaxy-note/

What about Leftovers on Gnex? Maybe this is helpful Francisco?
[Samsung Galaxy Nexus] duowing:
I was looking at the zip files that Franco's kernels come in and they seem to wipe most if not all of this stuff anyway.
[Samsung Galaxy Nexus] bat0nas:
Hi,

Few questions:

1) I recall here was a guy who tested minimum stable volts for each frequency.

Did he end up with kind of table with minimal UV values?

2) I see in the newest version that Franco divided now cpu cores into different menus. But I can't turn one or another core off.

Maybe some other settings (governor or whatever) are blocking my ability to turn off one core?

3) Is there a way to bring volts to default values after I tested the undervolting?

4) Do I understand correctly that Lazy governor is max battery saving? If not, which one? (I don't care about the performance).

5) For instance:

- I set max CPU to 900MHz (or what is a value)

- I undervolted

- I set Lazy governor (or whatever is best)

- I set power saver mode

- I got rid of biggest wakelocks and set my apps not to connect to internet

- I configured in my ROM to switch to 2G when screen is off

What are additional things I must do?

Thanks!!
[Samsung Galaxy Nexus] nodstuff:
Actually if some suggests something new/useful Francisco considers it.

If it has been asked a million times and the answer is the same every time then you can understand why he doesn't care.
[Samsung Galaxy Nexus] davidsavenberg:
173 is wonderful! Great work, it was just a matter of timme!

Skickat från min Galaxy Nexus via Tapatalk 2
[Samsung Galaxy Nexus] SupWiz17:
I was having weird issues with the carrier text on the latest cm9 also. After a few reboots I got it straight but I thought it was odd also.
[Samsung Galaxy Nexus] duowing:
Alright I'm just going to assume it's a CM9 thing. Looking at the changelog for CM9 a rather large list of changes have been merged into the builds for the 0527 and 0529 builds.
[Samsung Galaxy Nexus] willl03:
Something went wrong between 16x and 173, Franco you say you did all you can to fix the signal loss but 160 and below are fine, and so is leankernel. I hope you manage to find the solution so I can move back to your releases
[Samsung Galaxy Nexus] neverhappy:
Does the built-in hotplug disable core 1 with screen off regardless of the scaling governor or power mode selected (I see power save instantly kills core 1)? I did a search, but did not find the info I was looking for with respect to the built-in hotplug, governor scaling and power mode usability. Sorry if this has been beaten to death. If there is a link to a location that explains how to use these in tandem, could someone forward it? I get incredible battery life with power save power mode, but I do not want core 1 off all the time. Understanding the governor and power mode usability would be a big help. Thanks in advance.
[Samsung Galaxy Nexus] drawde40599:
UGLC1

Those of u using UGLC1 radio I just got the ril added to getril.apk , hopefully helps some of u with data drops...
[Samsung Galaxy Nexus] daddymatt:
Captain Obvious, don't let the door hit your butt. :-p
[Samsung Galaxy Nexus] Lambetts:
Haha, not really relevant but, thanks anyway.

That's some funny **** man!! Haha.

Cheers for the laughs.
[Samsung Galaxy Nexus] 1cewolf:
Well, I've tried 172 for a day and it seems to have cured my data drops on AOKP B37. Battery life is incredible as well. I was playing around with Tasker for about an hour earlier today, ~45 minutes on-screen time, and battery life was only down to 90% when I finished.

Franco, you're damn good at what you do :D
[Samsung Galaxy Nexus] nikulogical:
It shows up in the app but won't download it. I just changed it manually.
[Samsung Galaxy Nexus] danielvc:
Yes, get your phone a wheelchair too ;-)
[Samsung Galaxy Nexus] mistermojorizin:
this is very strange, and I need help. I think i really messed up my phone.

i was setting up 173, and when I went to set the undervolt settings for my GPU that i've been running on the last few builds, my phone reboot, and since i've turned it back on, things have been really messed up.

the screen alternates between high and low brightness on its own based on what i'm doing - auto brightness is off. For example if I lower the notification bar, the brightness dims and if i go back to the home screen it gets really bright. on top of that, there's purple tint now, and banding. thing's i've never had on my phone. the top and bottom row of pixels are also brighter than the rest now.

i've changed kernels, tried the reset kernel, restored a nandroid, and wiped data and started over, but nothing has helped.

it gets worse. the purple tint is present on the bootloader screen now, and there is thin green line at the top of the phone on the bootloader, recovery, and during boot animation - actually it comes and goes based on the recovery screen i'm on and which boot animation i try. it's the same row of pixels that's acting really bright on the home screen.

i don't know what to do at this point. short of reverting it back to locked stock, but i have a feeling that might not even help me.

i really need some community help here please.

the settings I tried to use were very close to what smart reflex sets the GPU at on its own. 835, 968 and 1150
[Samsung Galaxy Nexus] wlee2:
Franco Kernal 169 173

Flashed those 2 kernals and i have issues hearing the caller over the earpiece..

this was louder on 165 does anyone know if i am missing something or is there a way to make it louder?

Sorry if it is posted somewhere i read the last 3 pages didnt find what i was after.
[Samsung Galaxy Nexus] Lambetts:
+1

Yeah, unfortunately most of the time with this kernel, calls are pretty bad. Not so much volume, more so choppy-ness. Might be the rom, but if I try another kernel, for testing, it seems to clear up. Weird.
[Samsung Galaxy Nexus] metalspring:
Does the galaxy nexus predict battery % or does it go by the actual voltage?

I've noticed several times when I have the screen off for awhile the battery % actually goes up 1-3% (no it's not on the charger or USB)

For example before I turned the screen off my battery read 73%, then when I turned it on after about 30 minutes it read 75%
[Samsung Galaxy Nexus] superbobup:
There's always some "prediction", though it's not really the right word. The chip probably calculates the voltage and then uses a table to map that voltage to a visual battery % for the user. The change in batt % you are talking about seems to be a consequence of the way the chip calculates the battery %. For example, after heavy gaming for a long time, the battery may change over time to a steady value even after you exit the game and stop using the phone. Same thing happens during charging
[Samsung Galaxy Nexus] :
Why does it still not safe the color multiplers....

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Lambetts:
Thanks for that man. I asked this a little while ago and didn't get much back.

Thanks for your constructive, mature and clear response mate. :-) you've just helped a lot of people understand this. Makes sense to me.

Cheers.
[Samsung Galaxy Nexus] BigBake88:
Lol :p
[Samsung Galaxy Nexus] funkyblue04:
What is the difference between 384gpu and 512? Which one is best for battery:?
[Samsung Galaxy Nexus] mistermojorizin:
its definitly somehow related to the color multipliers. when the screen decides to turn it's own brightness up, i open franco's app, and the color multipliers indicate that they are set OVER 400 - like 500 and 700. so weird.
[Samsung Galaxy Nexus] CaspaTheGhost:
173 seems good to me so far... Getting the best work day life since getting the phone...

View attachment 1093787

View attachment 1093788

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aron7awol:
Ok, was this a recent change? I can test again.
[Samsung Galaxy Nexus] brian6685:
You guys using this with aokp, cm9, stock? Just curious on which rom it works best with or all about the same
[Samsung Galaxy Nexus] beekay201:
i asked what VDD core and VDD mpu a while ago. nobody awnsered. i guess nobody knew. great the guys found out about it.

/me sent this from a i9250 using Tapatalk
[Samsung Galaxy Nexus] jkoljo:
Okay. How about the better /sdcard r/w speeds in 7_1 nightly? Maybe the problem came hand in hand with that tweak..? At least I am getting much faster speeds in #7_1 than #5 for example, and then in #7_1 the connection is unstable. So maybe it throws some read faults..?

I tried copying a 2 gb file with #7_1 kernel four times, and every time it failed. I even rebooted twice between the trials. Then I flashed #5 and it worked immediately. Then I rebooted, again with #5, and it still works. So there must be something wrong with 7_1..
[Samsung Galaxy Nexus] loudaccord:
I'm curious how this latest kernel would compare to OTA 4.0.3 kernel performance and battery. If I had more time, I'd run the numbers lol
[Samsung Galaxy Nexus] franciscofranco:
Indeed, that makes some sense. Try to remount the partitions with nomblk_io_submit and see if it works.
[Samsung Galaxy Nexus] Redflea:
I've seen significant problems with connectivity even on stock...inability to copy files and connection problems. The Samsung drivers seem to be pretty crappy...
[Samsung Galaxy Nexus] sirj00:
Francisco you knocked it out of the ball park with this kernel.

9 hours on idle lost 3% and i'm going on 15 hrs and still have

60% battery left. Streaming pandora on 3g for 6 hrs. Superb

Job that needs to be commended with a donation.

This kernel is smooth on all facets of actions regardless of what

is being used. Absolutely perfect.

Although having the ability to pc the cpu would be a added bonus.

Thank you Again and a job well done. Looks like i'm done shopping

Around for any other kernels or roms.
[Samsung Galaxy Nexus] loudaccord:
I don't see how this kernel is going to get much better. I have pretty good battery life and everything seems quick.

What else is there to do with this?
[Samsung Galaxy Nexus] MFD00M:
USB OTG would be cool, not sure if this kernel supports it already or not. Haven't tested it.

Would be nice to be able to pop in a thumb drive to back up my pics and such
[Samsung Galaxy Nexus] lynxboy:
No such thing as perfection!

Regards.
[Samsung Galaxy Nexus] jkoljo:
The support is there, working great :)
[Samsung Galaxy Nexus] grinch247:
Is there any way to get setcpu to report cpu temps versus battery temp?
[Samsung Galaxy Nexus] Redflea:
Thanks for reposting this...commented the line out with	#. I can't thread search from Tapatalk, I presume this has to be repeated after each ROM flash/upgrade.
[Samsung Galaxy Nexus] Enhanced:
I just did this and when I rebooted my phone, it wouldn't get passed the boot animation. *shrugs*

Just did a Nandroid restore so all is good.
[Samsung Galaxy Nexus] akellar:
What was the benefit to this?

Sent from my Galaxy Nexus using Xparent Blue Tapatalk
[Samsung Galaxy Nexus] alanhsu:
I did mine and it booted just fine.

I am on MCR Ir8 Rom
[Samsung Galaxy Nexus] Redflea:
Don't know, away from my computer and Tapatalk doesn't have thread search. it was posted as a recommended edit.
[Samsung Galaxy Nexus] GchildT:
That shouldn't happen unless you delete the whole file. Did you change permissions on it?
[Samsung Galaxy Nexus] ttlycnfuzd:
From what I have read - and I may be wrong - it has to do with forcing the system to always use hardware rendering for everything. By removing the software rendering, it makes all graphics render through the GPU vs the CPU, thereby saving battery.

Someone correct me if I'm off here...
[Samsung Galaxy Nexus] Mikes30000:
Color multipliers are not sticking for me either on reboot on 173.
[Samsung Galaxy Nexus] Flukester69:
Just to say I have no unexpected drops by that I do have drops when wifi connects but its livable for 30 seconds. So far this 173 is the best kernel for me now. Thanks Franco!
[Samsung Galaxy Nexus] duowing:
Well I've encountered two separate drops today. One where I was in WiFi but left WiFi turned on and went out of range. When I came back to my phone I had no data, still had cell signal though. Just about 10-15 minutes ago experienced a full connection drop, then it came back. I wiped dalvik and all that good stuff, rebooted a few times and haven't seen the wifi issue. The other drop simply could have been a hiccup in the network.
[Samsung Galaxy Nexus] BigBake88:
See pg 1756....and probably 50 other pages ;) a higher clock will always consume more battery.
[Samsung Galaxy Nexus] mini21:
Today, for the first time occurred to me this problem.

In the afternoon I installed the latest build.

I do not know how long the phone was "cut off" from the network, but a few minutes ago when I picked him - look, and the display shows that there is no connection, and "no network".

Only restart helped.

Now I began to used phone, and again for a moment signal drop down, but this time after a while his back.
[Samsung Galaxy Nexus] distho:
You should look into a radio update, I don't believe that the kernel would affect your data dropping out other than a power saving setting that you would select yourself. I had a similar problem when I first started using AOKP with no data reconnection. I updated my radio and installed the latest franco kernel and am now having no problems.
[Samsung Galaxy Nexus] ajm786:
I have GetRIL app, and I don't see this reflected anywhere.

Edit: NVM, just found it! Every time I try to download it though, it says that Download Failed. :confused:
[Samsung Galaxy Nexus] swaser18t:
Same here fail.
[Samsung Galaxy Nexus] swaser18t:
What is your set up. I get no where near that.

So far 3 signal drops today on 173. all when I'm on wifi. When I turn the screen on its x'ed out. Recovers in like 5 seconds.
[Samsung Galaxy Nexus] Lambetts:
+1

Yes indeed. This is why personally I like 307.2 (stock gpu speed) Its fine. Less power and the basically same performance as 384mhz. :-)
[Samsung Galaxy Nexus] Flukester69:
Is there a way to change the wifi driver to an older version? Is it built into kernel or radio?
[Samsung Galaxy Nexus] BigBake88:
Except Franco is going to release next milestone with 384mhz gpu, but using same voltage as stock 307! So we get more performance with no increase in battery drain! Can't wait for M4!!! :-)
[Samsung Galaxy Nexus] krex:
I used r160 for long time with stock ROM, defaults of kernel without any problem until r166. So yes I also know r160 what amazing was. r166 seemed to the first interesting nightly after this.

On r166 I got signal loss after the first phone sleep immediately, so I'm moved back. I gave a try and now I'm on r173, still with stock ROM and defaults of kernel. No Signal Alert is running for almost 10 hrs and I haven't signal loss.

What could be important, I use always clean ROM with new kernel flash. No mess from other or previous kernels...
[Samsung Galaxy Nexus] digweed4me:
Amazing 173 no data drop and Amazing battery life
[Samsung Galaxy Nexus] ajm786:
I updated to r173 from r166, and had noticeably worse battery drain. Going back to r166 to see if I can compare.
[Samsung Galaxy Nexus] bongostl:
I too noticed this.

I was going to give it another day to try before reporting...but really noticeable difference.
[Samsung Galaxy Nexus] ajm786:
Yeah, too much to handle for me. I cleared Dalvik and cache, flashed 384MHz r173 version, and it ate 10% battery within 30 min.

Back to r166 for me. It's really too bad, because I can honestly say I experienced no data drops with r173 (at least not during my time of use with it). :(
[Samsung Galaxy Nexus] franciscofranco:
r174

* Another attempt to kill (or minimize at best) the recent surge of data losses
[Samsung Galaxy Nexus] joeyfong:
Cool, flashing
[Samsung Galaxy Nexus] ceejay83:
using a kernel for only 30 minutes isn't a good measure of battery life lol
[Samsung Galaxy Nexus] vomer:
Thanks for the effort Franco! 173 was not working for me. Let's hope foe the best!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vomer:
+1 not downloading

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] fatappel:
That was fast. I was digging 173 but didn't want to chime in prematurely without a full day of testing. Flashing 174 now. Thanks for all the updates and support franco.
[Samsung Galaxy Nexus] nikulogical:
What changed exactly? R173 and changing my til improved my signal a lot. I flashed this for the **** of it.
[Samsung Galaxy Nexus] msedek:
Yo bro is this kernel compatible with LG Optimus 2X running AOKP milestone 4?
[Samsung Galaxy Nexus] Gahh Its Lee:
Nope sorry to say. Kernels are phone specific.
[Samsung Galaxy Nexus] mistermojorizin:
Franco, have you ever seen anything like this? I'm really at a loss here.
[Samsung Galaxy Nexus] Gahh Its Lee:
My guess would be maybe something really messed up and your gpu is kinda screwed? I'm just guessing but to me it seems you f-ed it up. Hope I'm wrong.
[Samsung Galaxy Nexus] ajm786:
I'm fully aware of that. However, noticing that much battery drain in a period of 30 minutes is indeed startling.
[Samsung Galaxy Nexus] 15israellai:
http://www.androidcentral.com/android-z-what-kernel

Kernels are specific to phones because they have to include necessary drivers.

Go ahead and look for kernels in your O2X forums, I'm sure you'll find a lot.

Blazing on my Nexus Prime using xda premium
[Samsung Galaxy Nexus] chlehqls:
It's probably the battery trying to settle in after the reboot and installing of the kernel. Plus, the battery indicator is known to be wildly inconsistent a lot of times. There's too many variables that could have been impacted during your 30 minutes that I highly recommend going back to r173/174 so that you can continually to be a part of this nightly.
[Samsung Galaxy Nexus] leets4uc3:
For the people on aokp or similar roms with the startup init.d tweak, what tweaks do you have turned on? Also do you guys have gpu acceleration on?

I turned on a few init.d tweaks and got a weird drain. I don't think that was the problem tho. I flashed a few kernels and I am gunna do a fresh flash in the morning to fix everything.
[Samsung Galaxy Nexus] drawde40599:
Ur still under warranty no? Fastboot back to stock and call SAMSUNG! Get it fixed make sure you call samsung Not were u bought it ...

---------- Post added at 09:33 PM ---------- Previous post was at 09:29 PM ----------

U tested the kernel for 30 min and decided it was no good . Interesting o_O

Pulled 3.8 hours off 173 .

Running perfect here, never had the data / wifi issue

Thanks Franco!!

Wah?? 174, damit; )
[Samsung Galaxy Nexus] DildoMaster:
Is anyone else having graphics issues on the nightly builds? I keep using Temple Run to test this. On Milestone 3 everything is great but on every nightly I've tried, there's tons of screen-tearing and choppiness immediately starting with the panning sequence before the menu. The game itself suffers the same problems.

Should I be wiping the init.d folder? I tried to with estrongs with no luck (cannot be deleted error). I also tried wiping the cache and dalvik cache between switching nightly kernals but it didn't matter.

Thanks guys!
[Samsung Galaxy Nexus] Gahh Its Lee:
Your not using the 512 gpu version are you? I suspect so. If that's the case use the 384
[Samsung Galaxy Nexus] bat0nas:
What do you guys call a Signal drop?

My case with #173:

I had my bars gray (and internet was not working) and I needed to set Airplane mode ON and OFF to get my signal bars blue and get back online. Was that a signal drop?
[Samsung Galaxy Nexus] DildoMaster:
Interesting. Yes I was using the 512 version but I am fooling around with stuff a lot now because I'm getting really poor (IMO) battery life and in particular, screen time. I just came from reading this guy Willup's post here and he seems set on 512 fro good battery life.

BTW I wish I could tell you exact numbers but my battery seems to be dropping at a rate of about 1% per every minute of screen time.

It's getting late so I'm probably going to stay on milestone 3 and test Willup's "keep the min CPU at 700" idea tomorrow for a while and see how it goes. Then if I'm not happy, I'll try the 384 nightlies. Thanks!
[Samsung Galaxy Nexus] drawde40599:
Try search button its been mentioned 1000'S of times
[Samsung Galaxy Nexus] Gahh Its Lee:
The 512 version won't ever offer better battery life from what I understand. It'll just cause hickups of your phone hates it. But yea test everything. I run the lowest min and highest Max personally but my usage patterns allow my phone to not use the 1300 or whatever much unless I'm in games.
[Samsung Galaxy Nexus] DildoMaster:
While I'm up I'll try a little more, but I assume it's going to be a little hard with 1763 pages of posts. I'll update this post if I can find something to help.

---------- Post added at 06:58 AM ---------- Previous post was at 06:54 AM ----------

Hmm yes it would definitely make some sense that the battery is draining fast when my screen and therefore GPU are on. I'll definitely check up on that.

Another thing though, I'm on vacation using my now charging phone for free wireless tethering (;)) so I'm never on wifi and I've heard that being on only 3G (no 4G here or where I live for that matter) can really drain the battery too.
[Samsung Galaxy Nexus] Gahh Its Lee:
Well I have a cdma phone but I imagine its the same so yea. I can watch my battery drop like 1% every minute of few minutes easily on 3g. On 4g I just say goodbye and give up lol. You always have to remember people reporting crazy battery times use a lot of wifi
[Samsung Galaxy Nexus] T-Loop:
Signal drop is when your bars go blank (fully gray) and has X over it. That's what I'm always getting.
[Samsung Galaxy Nexus] jcmm11:
Sigh. This has been covered hundreds of times. Your phone can't handle the 512mhz hour. Install the 384 version
[Samsung Galaxy Nexus] krex:
Notification Light @ 192Mhz

Is here anybody who has notification light function (built-in or Lightflow) working on 192Mhz?

Thanks!
[Samsung Galaxy Nexus] Zflash:
Could anyone else verify, that with 174 the wifi drops alot on low signal? I just had this 3 times in 1 hour since I flashed. Going back to 173 (also about 1,5 hour) solved this issue for me. Bad luck?
[Samsung Galaxy Nexus] ragnarokx:
The Lazy governor was removed for 174? Was this intentional? I love that governor.
[Samsung Galaxy Nexus] qballe:
another attempt to make some "statistics" , I am making a little database but for now I have only 4 entry :p

here is my last battery cicle :

**battery_franco** ( please include this line )

ROM : stock google IMM76I

KERNEL # : 158

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

BATTERY TYPE : stock 1750

BATTERY LIFE/SCREEN ON : 1D 11H 7M / 2H 54M ( taken at 8% left )

BRIGHTNESS : auto

MINFREQ / MAX FREQ / GOV / : 729-1228-interactive

SMART REFLEX Y/N ( VOLTAGE IF SR OFF ) : SR ON

HOTPLUG/CPUMODE/POWERMODE: NO-dual-none

APPROXIMATE AMMOUNT OF DATA USED ON WIFI/3G: (using integrated menu under settings) 50MB on 3G

WIFI/BT/GPS/NFC ON ? :ON-OFF-OFF-OFF

OTHER SETTINGS: no

SMART USAGE DESCRIPTION: lot of google talk, 15' of video recording

NOTE:

please , if you want , try to use this template and I will collect data :p