yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mistermojorizin:
on r156 384, core is back to normal (8xxmv), mpu is great! (790mv), but IVA is still stuck at 970, which means iva is still running at the higher clock speed at idle instead of dropping down to the lower step.
[Samsung Galaxy Nexus] justinjustin234:
that means i need to apply the values if i reboot?
[Samsung Galaxy Nexus] psyren:
On r156, 384 GPU, hot plug gov, min CPU 728, SR on, Liquid 1.35. Having heat issues. Phone is quite warm after a few rounds of Draw Something. Franco app says current temp is 53c, so I estimate previous temp was in the 60s.
[Samsung Galaxy Nexus] tcchuin:
weird, either smartreflex/ manual uv doesn't work on my phone...

how can i provide a log or whatever to help in this?=x

using the tablet hybrid rom
[Samsung Galaxy Nexus] hotnikkelz:
Great battery life on 154 nightly. Best I've had, even better than 121. Franco be popping nightlies like crazy. Did I miss 155?
[Samsung Galaxy Nexus] drawde40599:
Do you not have his app? Its explained right in his app. And btw u have answered ur own question,
[Samsung Galaxy Nexus] Hanny:
since 154 (and also 156), i cant really tell the accurate temperature values but upon general usage (i touch my phone like whole day), whatsapp web browsing gta etc, the temperature really DOES decreased which is not as warm as before :) its all my feel from my fingertips

phone setup in sig

thanks franco :D im so happy to flash new kernels everyday and will report if necessary ;)

init.d
[Samsung Galaxy Nexus] Sveke:
Yup, set on boot gets rookies in trouble.
[Samsung Galaxy Nexus] BlindWolf8:
I have it installed and was messing with the min CPU frequency and set on boot so I guess I'll have to look in the changelog. I've been using the 384 GPU and was just wondering about the CPU. Thanks!
[Samsung Galaxy Nexus] Bavilo:
Is there a fix for Fifa 12? Apparently it's working fine with other kernels...
[Samsung Galaxy Nexus] kylebarendrick:
My wifi connection has been unreliable at work on r156 today. I don't know if this is related to the kernel changes or just a bad day at the office. Otherwise, I've had no issues.
[Samsung Galaxy Nexus] justinjustin234:
i have his app but can't find the explanation...
[Samsung Galaxy Nexus] franciscofranco:
Ok now that's some reliable and important feedback. How are you measuring unreliable? Shuts down, bad connection speed, random crashes? Happened since r156?
[Samsung Galaxy Nexus] Sveke:
156 is running like a Kenyon in a marathon.

Well done!

I Don't give a **** but my phone won't use 1036 slot either. Just pointing it out.
[Samsung Galaxy Nexus] jnr21:
Franco my kernal doesn't work, you already know what's the problem cos you have crystal ball...FIX IT!!

...

...

...

Just kidding, everything is butter smooth and no issues. I donated something. Thank you Franco.
[Samsung Galaxy Nexus] sago62:
no nespresso, no party.....
[Samsung Galaxy Nexus] kylebarendrick:
Apps have been (sometimes) unable to connect for data even though I am connected to the network. They work fine if I switch to 4G. I'll see if it is better on r154 when I get back from lunch.
[Samsung Galaxy Nexus] Metallice:
Custom r156 running at a constant, nice and cool 40 degrees with min/max both at 1650. This is ridiculous. :)

View attachment 1041059

Edit: Crept up to 45 degrees playing asphalt, but no further. Temperature is amazing on this new build.
[Samsung Galaxy Nexus] Flukester69:
Wow, even when playing games? That is impressive.
[Samsung Galaxy Nexus] nklenchik:
Then use the other kernels...
[Samsung Galaxy Nexus] The Gingerbread Man:
Nightly 156 is using 1036 CPU speed. I love these kernels espicially the sound mods. No issues so far and for 'nightly' id consider it very stable. Great work!
[Samsung Galaxy Nexus] javi3k:
yep i have to say that r156 is the coolest kernel ive ever had my temp are 34-40 and max 45 :o ive never had that before always jumping from 44-54 im gonna continue testing and doing some uv for better baterry life
[Samsung Galaxy Nexus] mistermojorizin:
could I try your version of it? either here or by pm. thanks, enjoyed your mods in the past
[Samsung Galaxy Nexus] Sveke:
I'd be interested as well.
[Samsung Galaxy Nexus] kylebarendrick:
I'm not convinced my wifi issues are r156 related. I flashed back to M3 (since that is easiest from the app) and it "feels" about the same. I think the wifi at work just sucks today. I ran speedtest from the same spot with both kernels. r156 gave me 1141kbps download and 549 upload. M3 gave me 1223/726. Both results are pretty slow.
[Samsung Galaxy Nexus] jnr21:
Check your inbox :)
[Samsung Galaxy Nexus] franciscofranco:
Yes please. If it works fine with r154 I will have to increase wifi voltage from 1.75V to 1.8V (stock kernel is 2.0V). Thanks, I will wait for further feedback.
[Samsung Galaxy Nexus] Bavilo:
What kind of answer is that? Its a problem with the Kernel...It should be looked at....
[Samsung Galaxy Nexus] kylebarendrick:
I replied above - the behavior was about the same on M3 (easier to flash from the app) as on r156, so I don't think the kernel is causing it.
[Samsung Galaxy Nexus] Sveke:
Switched my Franco app logo to something more appropriate. :)
[Samsung Galaxy Nexus] franciscofranco:
Oh yes I didnt see your post by the time I replied. Ok then it makes some sense that is not kernel related :) always a relief for me when that happens.
[Samsung Galaxy Nexus] franciscofranco:
Uninstall Fifa and install it again.
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm sorry for asking perhaps maybe a booby sounding question and this time I did search but nothing helpful really came up.

What's this smartreflex all about? Reading in the app it says about disabling stops it working from calibrating the voltages, so this means its automaticly undervolting to some degree?
[Samsung Galaxy Nexus] chakra:
Google is your friend

Answer: TI’s SmartReflex™ Power and Performance Management Technologies reduce power consumption and optimize performance. SmartReflex technologies are a broad range of intelligent and adaptive hardware and software techniques that dynamically control voltage, frequency and power based on device activity, modes of operation and temperature. Key features include:

The SmartReflex technologies approach is a holistic, aggressive way of reducing power while optimizing performance.

SmartReflex technologies cross traditional boundary lines in systems, coordinating multiple processing cores.

SmartReflex technologies alleviate chip-level leakage power dissipation at deep sub-micron process geometries.

SmartReflex technologies go well beyond traditional device power management techniques and feature plans for next-generation solutions.

TI has shipped hundreds of millions of devices with SmartReflex technologies.
[Samsung Galaxy Nexus] Flukester69:
LOL! How about just clear cache and data? No need to uninstall. It's probably gpu acceleration anyhow.
[Samsung Galaxy Nexus] dpaine88:
Just popping in to report record low temps. On Wifi but awful signal at 120dbm.

temps between 30-35 just browsing Tapatalk.

running 384-1060 OnDemand

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CerB:
R156...... it's magic

Sendt fra min Galaxy Nexus med Tapatalk2
[Samsung Galaxy Nexus] CaspaTheGhost:
Early days on 156 so I'll report back tomorrow; but temperature wise, after running up the stairs I've just used it to cool my heated brow...

Gave Lazy a go again whilst on 154, definitely agree that Ondemand is the governor of choice. Been my choice for a while and today reconfirmed that...

Still rocking 729 min...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] brianisme:
I've gotten two SoDs today running r156.

Stock ICS IMM76I

192/1228

ondemand

SR on

no UV

hotplug off

Will try @ 384
[Samsung Galaxy Nexus] Bavilo:
Its not working....and I don't have acceleration turned on.........
[Samsung Galaxy Nexus] jnr21:
Your phone can't handle 192mhz min frequency.
[Samsung Galaxy Nexus] olivercervera:
Hi Franco! I would know if 36-42°C is a normal temperature (using nothing, only frano.kernel app). I did not changed nothing, I have the milestone3. If I use the phone the temperature it's 45-50°C
[Samsung Galaxy Nexus] tcchuin:
mpu underclock isn't working for me on r156 nor r154.

working perfectly on r152 though.
[Samsung Galaxy Nexus] drawde40599:
Yep!! Stock android 4.0.4 kernel acts exactly the same way and that is exactly what my phone also dose . Even on charger now 156 don't get over 51°c love it!!! Call 156 milestone 4 and take a break Franco!!!
[Samsung Galaxy Nexus] Angelakaro:
Today i flashed milestone 3 kernel: the first 2 boots were a disaster: lags,bugs etc. I restarted my phone and now it's incredible! Smooth,fast and without problems of any kind. Unfortunately,there's still some annoying stuff (belonging to last official update):

live wallpapers lags, heavy games sometimes lag (i know that GPU is untouched)

battery duration isn't so better,but quiet better than that with the official kernel

However,very good work!
[Samsung Galaxy Nexus] dpaine88:
I got some burn in today on my screen, its was the lock screen lock circle. 10 seconds and it's was gone.

Could any of the color settings in the app be causing this?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] audibalso:
fifa 12 doesn't work for me either but i tried it on imoseyon 3.4 and it didn't work either. Even deleted the monster 1.5gb file download from my sd card. Then reinstalled fifa, had fifa redownload the monster file again. and still nothing. I'm not sure what the issue is but I didn't care enough to look further. good luck
[Samsung Galaxy Nexus] dpaine88:
Just a simple poll to those running OnDemand are you using 384mhz or 729mhz as a minimum? I keep flipping between the two and am curious to what others are running.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sveke:
192 here....running smooth
[Samsung Galaxy Nexus] dpaine88:
never mind...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sveke:
Not experiencing that
[Samsung Galaxy Nexus] axne1:
Going as good as expected...

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] nikulogical:
I'm getting same battery with on demand and interactive. Performance however is much better with interactive. Using 192/1344 for both.
[Samsung Galaxy Nexus] lynxboy:
Honestly, I have to laugh at all these temperature 'issues'. I don't study Psychology, but it still fascinates me, especially how it is displayed via social networks and forums.

Basically, trawl back over the thread and you will find that towards the end of last year, nobody really complained about temperatures or their phone getting too hot. It was a non issue. Then came the change; Franco's app began to display the information regarding CPU temps. All it took was one or two users to create the avalanche and state that their temps were too high, and it suddenly became another 'issue' affecting the user base. "OMFG my CPU is idling at 40 degrees, wait, is that 42 degrees, holy **** Franco this kernel is baking!!", "Y my phone so hot Franco?", "new nightly is running nice and cold". So not only do we want speed, stability and increased battery life; we now want COLD. Forget ColorControl, we want CoolerControl.

One of the things that brings a wry smile to my face, is the 'bug' reports. Users are quick to state what game was played or how long they were browsing, but there is one massive fail with these reports. What is the temperature where you are?! Lol!! If Salah078 in Dubai is complaining his phone is idling at 45 degrees, it comes as no surprise when it is 50degrees (this is Celsius we talking Yankees) outside. Xdauser553 is happy that the new kernel is cooler, and is also happy that his AC system has been fixed. Obviously ambient temperature isn't at fault all the time, but it has a massive effect. Go put your Nexus in the fridge and read the temps.

I had to bring this up, because even I am now checking the temperature of my CPU every now and then, feeling slightly panicked if it's 'too high'. Damn you XDA. It's the same with battery percentages. Take the ability to display battery percentage/info out of the Android OS and watch the sudden improvement in battery life for phones everywhere. No more sweating after losing 4% in 3mins.

Finally, if your phone gets too hot it will simply throttle the CPU in an attempt to cool down, or simply shutdown if it is an extreme situation. Don't sweat if it the temp reading looks too high. <=== See what I did there?!

Regards.
[Samsung Galaxy Nexus] Jan Rune:
Hi Francisco,

Nice work on this kernel. I love the batteryperformance and it fixed my Copilot problem for the AOKP ROM.

I dont have a tool chain for compiling. So i wonder if you could possible add USB CDC support(FTDI) for your kernel?

Aplausos

Jan
[Samsung Galaxy Nexus] Metallice:
Francisco, I hope I'm not being a bother, but could you consider modifying opp4xxx_data.c so that the 192 mpu slot has a different "OPP fuse" or whatever than the 384 slot? Currently they both are using OMAP_44XX_CONTROL_FUSE_OPP50. You'd also have to add the new opp to control.h. it seems this lets SmartReflex calibrate the 192mhz slot seperate from the 384 slot.

As it is now r156 calibrates my 384 and 192 as 770mv. When I make the change, my 384mhz gets calibrated to 770mv, while my 192mhz gets calibrated to 710mv. Running this now, and it works perfectly with no SODs or reboots so far.
[Samsung Galaxy Nexus] franciscofranco:
Not bother at all, please keep suggestions coming if you feel they are of value :) Ok chief, I'll test them now.

EDIT: Yes indeed, 192mhz calibrated to 710mV with a new FUSE OPP.
[Samsung Galaxy Nexus] dpaine88:
Now that's what I call user input!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Metallice:
Awesome. What baffles me is that I've tried setting my 192mhz slot down that low manually before only to have it instantly reboot anytime I went below 740. It almost seems like the 384 fuse opp was limiting how far I could manually undervolt the 192mhz slot. Either way 710mv stable all day from SR makes me quite happy :)
[Samsung Galaxy Nexus] dpaine88:
Since 1228 and 1344 both use the same voltage, should they both have the same battery drain?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nklenchik:
No, naturally 1344 will use more power. Someone posted this a while ago but there's a formula that's involved
[Samsung Galaxy Nexus] dpaine88:
Thanks for the quick reply

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Metallice:
I did. Its PV^2. (Frequency)*(voltage)^2.
[Samsung Galaxy Nexus] franciscofranco:
Makes sense having the opp limiting it. I wonder how many devices are tolerant to this low voltage. Since I have a 10k margin and 700 mV min I wonder how much we could lower it without crashing.
[Samsung Galaxy Nexus] triStateMindgate:
That's like getting something like this...

http://dl.dropbox.com/u/16430541/2012_lexus_lfa.jpg

and then complaining about the fuel economy being like 10 mpg.....
[Samsung Galaxy Nexus] nachtschicht:
I flashed #6 yesterday evening and undervolted it slightly. Before nighttime I rebooted the phone, opened and closed camera (as Franco advised earlier) and put it in flight mode. After 7 hours in flight mode my battery went down from 100% to 89%.

According to System -> Battery, Deep Sleep was like 30% and Android OS like 65%, Screen took 5%.

It's still a relatively high drain, isn't it? The device is snappy and everything and I like it very much, but regarding consumption of battery I am a bit disappointed. Am I the only one who experiences this kind of battery usage?
[Samsung Galaxy Nexus] ro_explorer:
That's exactly the drain I'm getting with #6. At the current stage of development I would say this is ok. It will certainly get better over time. Be patient.

// sent from my green robot //
[Samsung Galaxy Nexus] nachtschicht:
Ah ok, so I'm not doing anything wrong (I guess) ^^

And yes, I am patient, patience is a virtue ;)
[Samsung Galaxy Nexus] merdem:
I think I am having problems with the undervolting. Gnex shouldn't be stable at these values, am I right? But otherwise great kernel, thanks for your hard work.
[Samsung Galaxy Nexus] razzbaronz:
Same here, I have it down around where you do and everything is very stable. does this mean the underclock is not working? Even if going very low/lower causes crashes?
[Samsung Galaxy Nexus] merdem:
I dont get any crashes even with these values, but maybe there is a safety feature that prevents users to set unrealistic undervolting values?
[Samsung Galaxy Nexus] MontAlbert:
Yeah I reckon there must be a safety feature... If the under volting wasn't working then why would a single step cause a reboot.??

.eg. When mine gets down to around 800 I get random reboots but at 850 it's super stable.
[Samsung Galaxy Nexus] energie:
u cant go lower then some values even if you use 0, value isnt accepted.

have been said already please read.

I have been terrible drain tonite....i was looking at Wakelocks and i found again Audioout_1 even if my lock and tape sounds are off?

anyone?
[Samsung Galaxy Nexus] merdem:
But in my case i cannot produce any instability issues with any undervolting value, for example i set my 350mhz to 800 now it is still stable
[Samsung Galaxy Nexus] jkoljo:
That is hardly a surprise because 350 mhz is so low, but try to set 800 mV @ 1200 mhz ;)

Edit: I think the UV interface is broken, I can set 600 mV at 1200 MHz and my device does not hang. So there are still some issues..
[Samsung Galaxy Nexus] Dr_Ownage:
So is UV working correctly?? i saw a lot of debate a few pages back but didnt really see an answer. I am currently running

1200Mhz - 1100mV

920Mhz - 1000mV

700Mhz - 900mV

350Mhz - 800mV

and this seems stable so far....

I flashed the nightly #6 this morning and have had HORRIBLE battery life HOWEVER! it is the first day and this should improve (fingers crossed) especially now i have some half decent UV applied.

Keep up the good work Franco
[Samsung Galaxy Nexus] skyhigh2004:
What? I hate how everyone asks for feedback about a certain rom or kernel and when someone posts feedback that isn't all" omfg this is the greatest since evar!" we are told to stop complaining. I'm not complaining just stating my findings, super smooth but super battery draining as well. Not a complaint just what happens when I use this kernel compared to others.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Hows the drain using the sock kernel? Because I already reviewed everything I changed and I theres no way in hell any of the changes I did could cause extra drain, but the fact is even I am getting too much drain...
[Samsung Galaxy Nexus] ock:
Getting the same too, stock has about 0.5%/hr battery usage even without flight mode.

But I guess Franco must be puzzled about these reports :confused:
[Samsung Galaxy Nexus] skyhigh2004:
its really weird Franco, my devices seams to sleep perfect with your kernel but just drains more while in deep sleep and use I guess. With the stock kernel on bigxie stock 4.0.3 I get about 30-32+ hours give or take a few. With any custom kernel not just yours with the exact same use I'm between 14-18+. Its quite strange. That being said when I'm at home at night and wanna play a game I flash over to your kernel so its actually smooth lol.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aron7awol:
I pulled my phone off the charger right before I went to sleep last night, it was at 100% and I had wifi on. Woke up about 8 hours later at 75%. Device was awake for about 2 hours of the 8.

Biggest kernel wakelocks:

wlan_rx_wake

mipi_link

radio-interface

alarm_rtc
[Samsung Galaxy Nexus] franciscofranco:
Why would anyone leave wifi on during the night? I already said few pages back that the extra drain caused by wifi is because I gave it a stronger signal.

Anyway I'm testing different options and alternatives for the battery drain, the problem must be somewhere, I'm just trying to find where...
[Samsung Galaxy Nexus] jhericurls:
Because Wi-Fi uses less power than mobile data. Also most people schedule their downloads during the night.
[Samsung Galaxy Nexus] aron7awol:
Well, I always leave my phone on the charger overnight so I normally don't care at all if wifi is using a little extra juice. I did that test last night just to get an idea of how much battery would be used with the device sleeping and on wifi. I know you set wifi to pm:fast and that it uses some extra power. My post was meant to share my information, it wasn't a complaint about the kernel.

I also tried to do some simple testing yesterday to try to quantify the battery savings while undervolted, but there was a lot of noise in the data so I couldn't come to any conclusions. I was trying to measure current draw with Battery Monitor, but I think the values it reports are an estimate, and not a particularly accurate one. I'll have to revise my testing methodology. Also, there are some reports that UV doesn't seem to be working, right? That could explain my results somewhat as well. I'll keep everyone posted on my results.

I'd still like to hear your thoughts as to why lower frequencies cause the device to wake up more often, btw...
[Samsung Galaxy Nexus] Sveke:
When I switched to on demand it went to the 1036 slot.

So only in interactive does it not go to 1036...for me at least

And again, it's running beautifully so I don't care, just pointing it out
[Samsung Galaxy Nexus] nklenchik:
Same here, but I think Interactive is still snappier
[Samsung Galaxy Nexus] Sveke:
Agreed. I see no difference in battery life either so I'm sticking with interactive
[Samsung Galaxy Nexus] Metallice:
Well the hope is that if they aren't tolerant to this low voltage, SmartReflex won't set them that low... But who knows what will actually happen. Also, as you said, If it is calibrating our devices to 710mV that means SR is hitting the 700 min limit... I'm going to try lowering the MPU min to see what happens.

EDIT:

Set the min in voltage.h to 670mV and it calibrated to 690mV. Looks like 680mV is the absolute minimum my phone can handle at 192mhz (according to SmartReflex).
[Samsung Galaxy Nexus] dpaine88:
since it's the Voltage squared it seems like the power consumption would be very minimal.

I remember way back around nightly #7, people were saying 729mhz used less battery than 384mhz for 4 good reasons, can't remember what they were.

based on that formula, 729 would use nearly 2x as power

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sveke:
I have an hour and a half screen on time with 60% battery left on Verizon(USA) cdma.

For those with GSM and not familiar with cdma, that's Epic!!!
[Samsung Galaxy Nexus] dpaine88:
not hating at all but that comes out to 3 hours 30 minutes which is more towards good than epic...

still great stats regardless just saying like 5 hours would be epic.

what's your min max gov?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sveke:
Anything over 2 hrs is epic for me. Seeing 3 hrs is rare.

194-1228 interactive
[Samsung Galaxy Nexus] Gahh Its Lee:
I have a Verizon gnex and I get like 2 hours no matter what. Idk that I've ever hit 3 hours even
[Samsung Galaxy Nexus] Sveke:
Normally this is what I see too.
[Samsung Galaxy Nexus] Metallice:
Since its also running at a higher voltage, 729mhz would actually use OVER 2x the power. (Actually, I don't know how dual core factors in... it might be over 4x the power.)

The argument for 700 min is that it will complete tasks faster and allow the phone to reach deep idle faster, while providing a snappier experience. To me that argument doesn't make sense. Lol but math doesn't always work out when it comes to real world use :D
[Samsung Galaxy Nexus] dpaine88:
Now I do have the ext battery but before that I could hit 4hrs screen time.

granted this was with most activities requiring screen on so low amounts of phone calls and Google maps etc.

I think the number one thing people forget when judging screen time is phone calls and Google maps navigation

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sveke:
Agreed, I talk on the phone a lot for work. Avg at least an hour of calls per charge too
[Samsung Galaxy Nexus] dpaine88:
That Def explains it for you since calls require power and don't count screen on

Sent from my Galaxy Nexus