yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] republitarian:
Have u tried lazy governor. My 192 wasn't running until I set it on lazy
[Samsung Galaxy Nexus] gknnn':
Dude i love your work but please update your app its full with Bugs since some Versions
[Samsung Galaxy Nexus] metalspring:
...I'm sure it would help if you were actually being specific with whatever "bugs" you're experiencing...and Franco DOES update his app quite often already
[Samsung Galaxy Nexus] yyz71:
So this what I did to get 192 to stick!!! Uninstalled Francos app and reinstalled it again and that seem to do the trick:confused: This has nothing to do with rom I'm using!!! It's the app it self.. That problem didn't occur before the app update, It was only after the update 192 slot didn't stick... Here you go it sticks now :)
[Samsung Galaxy Nexus] isinisterx:
Can anyone comment on the battery life with tablet mode rom and this kernal?
[Samsung Galaxy Nexus] giugiu:
You can use tasker or similar apps to do that. I think it would be too much work for franco to add such a feature. Plus there are 1000 apps to play music. You cannot detect when music is played.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] giugiu:
I bet the bugs you are (trying to) pointing out are features or behaviors of the app which are explained in notes/help.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Sveke:
Is the built in ROM control of your ROM set at 384?

Disregard I see you fixed it
[Samsung Galaxy Nexus] neederishelp:
Small request for us OCD theme users, would it be possible to make it so that there could be a widget background color chooser?

Thanks
[Samsung Galaxy Nexus] gknnn':
Its very lagy when set colors multiples, don't saves governor and cpu speed after boot and than when i set some times it sets back automatic so i must go again to app and set it new.

I'm on newest CM9. No changes by my self and no i never opend the CM9 Power settings.

The poor english is an gift from me :p

read on top ;)
[Samsung Galaxy Nexus] superbobup:
I don't think many non-cm users have these issue...going to guess it's an issue with the CM9 build you're using
[Samsung Galaxy Nexus] franciscofranco:
Unless you can reproduce those bugs in a stable rom I'll call it CM9 derp, all of that works for me flawlessly.
[Samsung Galaxy Nexus] Serious_Beans:
Its laggy when setting color multipliers for me too, I am positive its just cm9, because it doesn't happen on any other rom. The CPU settings stick for me though.
[Samsung Galaxy Nexus] dawgpound6985:
For the people with the laggy color settings and colors not sticking on reboot with CM9, try updating your Superuser binaries using the Superuser app. For some reason, when you flash new nightlies, the binaries don't play well until you update them on CM9. Has to be done after every nightly flash. Only happened recently but can't remember which build.
[Samsung Galaxy Nexus] johno168:
Thank you so much! Works perfectly now.. I went to superuser app>settings(wrench)>update binary>update anyway.

EDIT: Colours set on boot too! Thank you very much.
[Samsung Galaxy Nexus] franciscofranco:
See? Not everything bad that happens in a device is my kernel or my app issue, tendency that some users try to spam on this thread :) Glad to see your **** fixed, always good to see a happy user!
[Samsung Galaxy Nexus] johno168:
LOL should put that up as a fix for CM9 users! I believe in you franco!
[Samsung Galaxy Nexus] nikulogical:
Anyone on r160 having issues with the twitter app force closing whenever opened? I'm trying to figure out what changes I made to my device that caused this.
[Samsung Galaxy Nexus] aquavalanche:
First of all, I wonder.. did touch screen also controlled by kernel?

if yes, sometimes I got a bit of "malfunction" of multi touch.. it's like the 2nd touch will not be read unless the 1st touch move a bit.. sometimes the issue gone after restart, and also sometimes return after restart..

I'm on LS 1.35 btw..
[Samsung Galaxy Nexus] johno168:
Its LS bug. Franco and i have had this convo. Use another rom. Others with LS(like me) have this bug. Devs don't seem to be looking into it since not everyone has it.
[Samsung Galaxy Nexus] sotoskawasaki:
It's not your CPU that can't handle it, it's your GPU. Two very different things.
[Samsung Galaxy Nexus] tkrewinkel:
Checked and no problem running the r160. Try clear data and login again
[Samsung Galaxy Nexus] nikulogical:
Fixed it after uninstalling 3 times. Weird.
[Samsung Galaxy Nexus] leos0000:
Hey guys...Wich governor its the best on r160 ?
[Samsung Galaxy Nexus] jeetS:
lol ^ stupid canadians…..oh wait..

the governor choice totally depends on the user, that question has been asked hundreds of times in this thread…And I'm not exaggerating
[Samsung Galaxy Nexus] leos0000:
What ? Im Russian dude...So i live in Canada...лошара
[Samsung Galaxy Nexus] spinkick:
I get about 2 - 2.5 hours of screen time out of my LTE phone. I get good signal but its mostly because I use it for a ton of push email, push gmail, calendaring etc.
[Samsung Galaxy Nexus] BrUhNiGGs:
I'm running AOKP 36 and is anyone getting a bit of screen responsiveness issues? Not sure if it has to do with the kernel. Tried 384gpu and 512gpu and get this issue. Just sometimes as I swipe to different screens on my launcher and swipe back fast it is very delayed and laggy. This happened after I ended a call and the only thing that gets the screen responsiveness back to normal was to lock the phone and turn it back on. Just seeing if anyone comes across this issue I would like to know so if I'm not the only one. Thanks.

Nova launcher and both apex give me this issue so it can't be the launcher. Also Liquid did the same.
[Samsung Galaxy Nexus] rmcsc:
It was just a suggestion. Jeez. Just trying to help out.

This is hilarious.

Franco: yesterday I hit nearly 12 hours of phone use, a bit over 4 hours of screen on time. That's great. Much better than stock kernel. I appreciate your work.
[Samsung Galaxy Nexus] jetdite:
Hello Franco,

Could you consider finding a solution for this issue? Lags caused by just simple toast notifications like this are unbelievable. For me, they are just the result of unbalanced CPU priorities.

This issue really makes experience from apps like NotifierPro suck.

Sorry if it is not kernel-related.
[Samsung Galaxy Nexus] Benji1983:
+1 here is the same especially in the lower screen on the dock side ^^

another thing is i got lags (graphic and speed with #160 384 and 512 gpu, with the r999 all is fine why :-) ?

greetz benji
[Samsung Galaxy Nexus] spaceman860:
r160 is exactly the same as r999

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] aquavalanche:
Cool.. it's nice to hear just the ROM bug.. thanks!

Anyway, do franco kernel give us extra option to preserve more juice?
[Samsung Galaxy Nexus] Benji1983:
i know but its so lags --> 160 , 999 --> lagfree
[Samsung Galaxy Nexus] superbobup:
You realize that them being the same --> there's no possible way it can be kernel related? Or that there even is lag?
[Samsung Galaxy Nexus] Lambetts:
Hey guys.

What arrived guys using for CPU temp?

Thanks.
[Samsung Galaxy Nexus] jamiescott23:
What is your governor? And other settings? Could you please share?
[Samsung Galaxy Nexus] ChosSimbaOne:
I've just tested tethering on the train with a Lenovo T420 running W7 Ent.

USB = Not working. The computer is constatly identifying my network, never getting internet access.

Bluetooth = Working

Wifi = Working

I'm running the CM9 Nightly from 5/16.

Kernel setting: 729/1228 Ondemand, Hotplug off.

Greate Kernel otherwise, loving the battery life and performance it's providing. Keep up the good work.

Might be a ROM issue, seems that many have reported it in CM9 nightly thread.
[Samsung Galaxy Nexus] jcmm11:
Not a ROM issue. Already known, I reported it a few pages back (didn't know Bluetooth status, so that's new info). Franco is aware and says it will definitely be fixed, especially since he uses tethering a lot.
[Samsung Galaxy Nexus] zenzip:
having 6% of drain battery in 33minutes....

Screen on 2 minutes, sync on, wifi on, hotplug off, 384-1228 ondemand....

It's normal? it's too hig consumption....

Don't have issue with wakelocks....in 33minutes the phone was 30min in deepsleep mode!!! why 6% of drain?
[Samsung Galaxy Nexus] ChosSimbaOne:
Coolio :-) sound like it is gonna be a great milestone.. Btw had 2 % drain during the night, ie 7 hours of sleep :-)
[Samsung Galaxy Nexus] Vangelis13:
Anyone has a colour setting that comes close to Trinity's white? I can't for my life get even close. Or any other setting suggestion that takes the fckng beige away..
[Samsung Galaxy Nexus] schizophrenia:
something like that happened to me before.. for few hours period

high drain while the phone sleep nicely.

and honestly i still can't find the reason

please let me know if you know why
[Samsung Galaxy Nexus] yyz71:
So I guess we don't need updates then!!!!

Sent from M5
[Samsung Galaxy Nexus] franciscofranco:
r161

* Increased wi-fi voltage from 1.8V to 1.825V for stability purposes

* Merged the latest init:calibrate.c changes from kernel 3.4

* Attempt to fix USB tether not working for some users (I believe its a CM9 nightly issue, but nevertheless lets just make sure its not my derp)

* Disable GENTLE_FAIR_SLEEPERS for testing purposes

* Add back screen_off_max_freq sysfs entry. By default it caps at 729mhz on screen_off, but you can change it in this file /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq

* Added special compiler flags for some extra bits of performance

* OMAP4 DSS errata i733 workaround
[Samsung Galaxy Nexus] kompressorgpl:
WOW!!!! R161 allready??? Now that's what I call a quality service (from Portugal off course!!!) :p
[Samsung Galaxy Nexus] sotoskawasaki:
Franco can you explain or point me somewhere to understand what screen_off_max_freq is and how it will affect the device? What should the recommended frequencies be?
[Samsung Galaxy Nexus] metalspring:
It's kinda self explanatory...it sets the maximum CPU speed while the screen is off...similar to a setcpu style profile

It just makes it so the CPU doesn't ramp up to the highest slot whenever something runs while the screen is off (like an app syncing or market downloading an app update) it should help with battery
[Samsung Galaxy Nexus] sotoskawasaki:
Yes you are right. The sysfs kind of tricked me. While its a clever technique to save battery there are occasions that it might have a negative impact. If for example you are installing a big game and the screen goes off going to a lower freq would make the process go longer and could drain more battery. That's a fast thought... It follows the same principal as having the min freq to 729 and not 384 mhz. But of course I might be wrong...
[Samsung Galaxy Nexus] metalspring:
Hmm not sure, however I notice that most things you do (downloading, apps, etc) really only use higher frequencies to LAUNCH apps and services, otherwise the CPU sits nicely on the lowest speed...my 192 slot is used way way more than any other besides deep sleep, and that's without wakelocks
[Samsung Galaxy Nexus] sotoskawasaki:
Again, that makes sense...I guess testing is the only way to see that behavior.
[Samsung Galaxy Nexus] dpaine88:
The stock gnex kernel has it set at 700mhz Max screen off. I had no idea Francisco disabled it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vomer:
Thanks franco. Loving the power modes too! Any chance for auto switch between power modes based on usage? (Example: If headphone plugged in - switch to music)?
[Samsung Galaxy Nexus] nodstuff:
On the nexus s screen_off_Max_freq (SOMF) was used to actually ramp the CPU to maximum speed to ensure it got through whatever task it had as quickly as possible so it could get back into deep sleep and in that way it saved battery, I.e. the race to idle principle.

So my question is would it be better to set it to the Max clock speed now or to leave it at 729 seeing that the CPU in the gnex is a lot more capable than the one in the nexus s.
[Samsung Galaxy Nexus] metalspring:
Btw Franco there is still one annoying bug with your kernel app, whenever auto flashing or downloading the progress popup disappears if the screen rotates...it still flashes or downloads but it would be nice to still see the progress popup to be sure it is downloading
[Samsung Galaxy Nexus] phewizzo:
Is anyone having problems downloading the 384 gpu version of 161?? I tried from the site and app and its unsuccessful.
[Samsung Galaxy Nexus] meeek:
I think i found a bug with the Franco app and the increase sound volume setting. It keeps turning itself off after notifications but the weird part is it shows that it's set to 3, so to fix it i have to set it to 0 and back to 3. Also this setting doesn't always stick after reboots. I'm running r160 on aokp m5
[Samsung Galaxy Nexus] leos0000:
Work perfect r161 512 mhz on aokp 36 .... no bugs ...very fast and stable
[Samsung Galaxy Nexus] leos0000:
And franco app work perfect too.thanks franco
[Samsung Galaxy Nexus] Arcadia310:
I turned the gamma all the way up to 400 for red, blue, and green just for the hell of it and the screen actually looks really good lol. Will having it on these settings hurt the screen at all?
[Samsung Galaxy Nexus] franciscofranco:
Thats a bug in the kernel interface, not the app.
[Samsung Galaxy Nexus] Hanny:
franco, as you said you have "add back" the screen_off_max_freq on r161 but in the past (r160 and even before), the phone acted relatively slower upon screen off too. (while transferring files through airdroid, downloading huge apps from google play, downloading giant gameloft data, it shows significant difference on the speed of file transfer - file writing in other words)

so, did you ever "put away" the screen_off_max_freq or my observation is because of another reason? im just curious and sorry if i seem stupid.

well, my settings are almost always 384/1344 hotplug-gov [generic hotplug off], but (r160 and before) the slow down is still there with interactive governor. (tested with airdroid transferring 300mb files, it just speeds up when i turn on the screen and vice versa)

yes the vivid colors are attractive but it exactly hurts and you will get burn-in extremely soon. avoid that!
[Samsung Galaxy Nexus] spaceman860:
Franco possible bug when plugging the phone to the charger or unplugging it the screen doesn't turn on anymore

Edit on r161

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] Hanny:
^confirm this :) not happening on 160
[Samsung Galaxy Nexus] andQlimax:
if i understood correclty screen_off_max_freq mean that now on the 161 u can limit the max frequency (default 729mhz) when the screen is off..

instead with 160 and before there where no limit when the screen was off, the limit was ur max cpu frequency, for example 1228mhz
[Samsung Galaxy Nexus] Hanny:
thanks for your quick reply.

yes i also examine that in the way you explained but im exactly wondering, if there were no limit on r160 and before, my observed slow downs when screen off shouldnt occur, right? generic hotplug was off and my results are the same with either hotplug or interactive governor.
[Samsung Galaxy Nexus] six_dfx:
r161 here, screen turns on as usual when phone is unplugged from charger.

another observation: since r161 (or was it 160?), my phone goes to deep sleep while charging, before that it stayed at the lowest freq when plugged.
[Samsung Galaxy Nexus] nodstuff:
The transfer speed doesn't have anything to do with SOMF, its because wifi goes into low power mode on screen off.

Not sure how to turn on WIFI_PM_FAST.

---------- Post added at 04:47 PM ---------- Previous post was at 04:46 PM ----------

Seriously?!

Is that even important??
[Samsung Galaxy Nexus] jcurtis369:
To some people it might be. Just because you dont care about that feature doesnt mean nobody cares about that feature.
[Samsung Galaxy Nexus] Hanny:
oh... got it! thanks :cool:
[Samsung Galaxy Nexus] sruel3216:
Franco or anybody,

im trying to change the max screen off. i noticed the current value for 729600 is obviously for 729 slot. what is the value for 384 and 192? 384xxx and 192xxx?

also if i set in the app max 1228 and min 729 but set screen off to say 192, will it use the 192 for screen off or do i have to have 192 set as the min in the app also?
[Samsung Galaxy Nexus] superbobup:
I'm not sure if "WiFi Power Management" in the Franco app turns it to PM_FAST but it is supposed to boost WiFi when screen is off
[Samsung Galaxy Nexus] six_dfx:
Every report of unexpected behavior is important, because as benign as it might seem, it could be caused by a much worse problem that could go mostly undetected until it blows off your phone ... well i'm exagerating it but this is the idea :)
[Samsung Galaxy Nexus] nodstuff:
Setting screen_off_Max_freq to 192mhz is a bad idea, the faster a task is done while the screen is off will save you more battery. Limiting it to 192mhz just means the CPU has to stay out of deep sleep for longer meaning more battery use.

192mhz task takes 10 seconds CPU awake

1228mhz task takes 1 second awake.

The CPU deep sleeps faster when the task is finished faster.

---------- Post added at 05:08 PM ---------- Previous post was at 05:05 PM ----------
[Samsung Galaxy Nexus] sruel3216:
i mainly want to do it for music
[Samsung Galaxy Nexus] Dsmforlife92:
So what kernel do you recommend milestone or 161 nightly
[Samsung Galaxy Nexus] zenzip:
milestone for stability, lastest nightly for newest features and often for best performance and battery life.
[Samsung Galaxy Nexus] drawde40599:
Next time u have any type of deep sleep issue try flashing the 4.0.3-4.0.4 reset kernel ( Google it, it will be 1st or 2nd find ) or fastboot the stock boot.img then flash the Franco kernel, its fixed every single time I had d sleep problem .....
[Samsung Galaxy Nexus] franciscofranco:
But If you click the power button it turns on right?
[Samsung Galaxy Nexus] jcmm11:
Franco, I have good news and not so good news :)

1) USB tether now works again. Thanks (and it's not a ROM issue, or at least not strictly CM9. I'm running Liquid at the moment)

2) New bug. I lose adb connection when the screen goes off. :( (confirmed that this didn't happen in 160)

(Fairly simple workaround for the moment, just force screen to stay on when charging. But it still shouldn't happen)

In any case thanks for all your work on this. I know what's involved and you do a great job.
[Samsung Galaxy Nexus] franciscofranco:
Check scaling_available_frequencies file in the same directory and you will see the values.
[Samsung Galaxy Nexus] franciscofranco:
Do you have another cable that you can test that up? I had one cable that did that, when I changed to another one it was alright. Not saying its your cable ****, but before I go goose chasing that would be nice to know.
[Samsung Galaxy Nexus] franciscofranco:
Yes its PM_FAST, I have to rename that option, its a bit confusing right now.
[Samsung Galaxy Nexus] dracon6ai:
I'm on r161 right now (384 gpu) and I just noticed that the last 1 hour and 20mins on idle my battery dropped 1%. And I'm on 4g atm (working). I am freaking shocked. I usually drop 4-5% an hr on idle since I got a ton of stuff constantly syncing for work. Running the Lazy power control now also btw. Awesome job Franco!

Laziness is nothing more than the habit of resting before one gets tired!

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] sruel3216:
get the same thing. yest it turns on when clicking the button
[Samsung Galaxy Nexus] franciscofranco:
Which rom are you using?
[Samsung Galaxy Nexus] Hanny:
yes, it is not a sleep of death, but the matter of automatically turning on the screen when there are changes of charging state.

also, i have more observations about this - it is actually not "malfunctioned" at all, however the reaction is a lot slower since r161

in the past when the charging state changes (plug/unplug), the screen turns on within 3 seconds. now it turns on automatically but after 8-10 seconds.

tested with hotplug-gov and interactive-gov, same results. generic hotplug off. procedure is manually turning off the screen, wait for 10-30 seconds, and change the charging state.

however, no matter how short i wait after manually off screen, i mean, even i plug/unplug the cable immediately after the screen is off, i still have to wait 7-10 seconds for it to turn on by itself. so i dont think it is related to whether the phone is in its deep sleep state.

edit: i am not certain, but it is observed that the phone takes longer time (8-10sec) to auto on screen when PLUGGING (uncharged -> charging)

than that of UNPLUGGING (charging -> uncharged) - this one takes the fastest 3-5 seconds, but sometimes it takes around 10 seconds too.
[Samsung Galaxy Nexus] Dsmforlife92:
What is the gpu speed on 161 nightly
[Samsung Galaxy Nexus] nodstuff:
You can pick between the 384mhz version and the 512mhz version.
[Samsung Galaxy Nexus] spaceman860:
+1 aokp 36

Sent from my Gnex {GSM}
[Samsung Galaxy Nexus] sruel3216:
axiom patient zero 2.5. 160 turned on when unplugged and plugged in
[Samsung Galaxy Nexus] jcmm11:
Tried with another cable. Same thing. "adb devices" returns normally showing a connected device. If I'm in shell at the time it locks up and becomes non-responsive. If I try to initiate a pull or push it just sits there and I need to ctrl-c out.

Oh, I'm also getting the "screen doesn't turn on" when disconnecting from charger thing (turns on fine when connecting to charger).

None of the above is major. Easy workarounds for everything. Just mildly annoying.

Thanks again.

Edit: confirm that the screen does come on after a delay, as posted above.
[Samsung Galaxy Nexus] slayp00n:
superuser
[Samsung Galaxy Nexus] franciscofranco:
Ok that feedback is interesting. I'll see what I can do.
[Samsung Galaxy Nexus] qballe:
guys, an idea !

is it possible to set up a template to report battery life feedback ? maybe "hasing" the post for a quick search , an example :

**battery_franco**

ROM :

KERNEL # :

BATTERY LIFE/SCREEN ON :

BRIGHTNESS :

MINFREQ / MAX FREQ / GOV /

SMART REFLEX Y/N ( VOLTAGE IF SR OFF )

HOTPLUG/CPUMODE/POWERMODE

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

WIFI/BT/GPS/NFC ON ? :

OTHER SETTINGS:

SMART USAGE DESCRIPTION:

NOTE:

it should be easy to read, helpfull for franco, and it would be easy get some statistics.

for example mine :

me 2 cent :D

feel FREE to change the template :) and sorry for my english :D

Marco
[Samsung Galaxy Nexus] franciscofranco:
Interesting my screen turns on 2 secs after I plug the usb cable in.

EDIT: In fact I lose adb on screen off. Pretty annoying. Gotta find out what ****ed up.
[Samsung Galaxy Nexus] gknnn':
Same here no problems.

Are you planning to let the screen off setting in the kernel if it works fine for us?

When yes include to set it into your app?
[Samsung Galaxy Nexus] franciscofranco:
Adding the setting in this very moment to the app.
[Samsung Galaxy Nexus] wily5150:
how to setup this kernel

I just purchased the kernel updater for this kernel. I was wondering how to use it, and what are the best settings? Thanks
[Samsung Galaxy Nexus] gknnn':
Mr super fast :)

Depending on your usage I like 729MHz to 1228 with Hotplug governor, Hotplug on and SR on
[Samsung Galaxy Nexus] zenzip:
good!

this is mine, and maybe I've some problem about my batterylife

ROM : AOKP milestone 5

KERNEL # : #161

BATTERY LIFE/SCREEN ON : 18h-20h / 1h 50m

BRIGHTNESS : 70%

MINFREQ / MAX FREQ / GOV / : 384 - 1228 - ondemand

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

HOTPLUG/CPUMODE/POWERMODE : no-dualcore-none

APPROXIMATE AMMOUNT OF DATA USED ON WIFI/3G : 60% WIFI - 40% 3G

WIFI/BT/GPS/NFC ON ? : often on/off/off/off

OTHER SETTINGS: no

NOTE ON YOUR OWN USAGE PATTERN: a lot of gtalk, what's app, facebook client, and surfing

SMART USAGE DESCRIPTION : sugarsync every 1hrs but only on wifi, all google services, haxsync, what's app, beautifull widgets, sync always on, no games

---------- Post added at 09:39 PM ---------- Previous post was at 09:37 PM ----------

franco not recommended to use hotplug with hotplug governor... ;)
[Samsung Galaxy Nexus] leos0000:
R161 work perfect on miui latest.... the best kernel forever