yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Antob125:
The creator of AOKP, Roman posted this on G+ and was wondering if anyone knew if it will break anything with kernel.

Roman Birg

1 hour ago · Desktop · Public

I experienced the signal bug a few times today so I thought I'd look and see what I can find. So far I've seen two solutions that could work.

1. Script that needs to be run at every reboot

su

echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp

2. Raise minimum frequency to 700mhz.

I'm going to implement the first fix in ROM Control and see if it works. I'll post a flashable RC for toro and maguro builds for testing.

UPDATE:

aokp maguro build 31 flashable test fix: http://dl.dropbox.com/u/87565/AOK/aokp_maguro_b31_signaltestfix.zip

aokp toro build 31 flashable test fix:

http://dl.dropbox.com/u/87565/AOK/aokp_toro_b31_signaltestfix.zip

Let me know if this fixes the issue if you try one of these. Also, make SURE you are on build 31, or you might run into issues.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] darrendm:
Thanks for posting Romans post. Hoping issues will be fixed
[Samsung Galaxy Nexus] kashix:
Posted this issue before but was unable to get a solution. When I'm running AOKP with franco kernel with his app. The colors setting in AOKP performance isn't able to overwrite those in the app. Is there a way for me to use AOKP's to control the colors and gamma setting instead of the application overriding it? Any help would be appreciated!
[Samsung Galaxy Nexus] Remoteconcern:
It doesn't break anything kernel-wise, but this switch is already available in franco's app.

I never get the signal bug so I don't know if it works, though.
[Samsung Galaxy Nexus] rafi300:
I have been running fully stock Aokp b31 and this is amazing ! No changes , and stock 1750mah battery.
[Samsung Galaxy Nexus] paratox:
wrong thread! please report in aokp or faux kernel thread. not here!
[Samsung Galaxy Nexus] raubkatze:
Nicely. But sorry why here and not in AOKP thread?

I think most of us tried using stock rom's kernels) But for me it's really no smooth and has less performance.
[Samsung Galaxy Nexus] daralph:
Just a question is touchwake(like in glados) planned to be featured in a future release, i would love to see this coming to franco.kernel..
[Samsung Galaxy Nexus] franciscofranco:
Most likely not, sorry.
[Samsung Galaxy Nexus] marshy73:
My apologies if this has been asked but I can't find it.

I'm on AOKP nightly 31 and Franco Nightly 133. CPUSpy is telling me that Deep Sleep CPU state is not available.

Is this suppose to be the case?
[Samsung Galaxy Nexus] raubkatze:
I'm on Skankwich CM9 with r131. No problem here:
[Samsung Galaxy Nexus] Ninsassin:
Hello, I was wonder what people's Core Voltages/IVA Voltages are?

I have 974mV IVA and 1088mA Core. I feel like my battery might be defective and is just always draining regardless of the software.
[Samsung Galaxy Nexus] bendirkss:
I'm running stock
[Samsung Galaxy Nexus] marshy73:
Ok its weird. After posting here. I left phone alone. Upon return, i checked cpuspy again and i see this. Now it says i have deepsleep state but its not going into deepsleep.
[Samsung Galaxy Nexus] kashix:
try to reboot and leave it alone, see does it changes. Otherwise, my guess would be that something is preventing it from deepsleep.
[Samsung Galaxy Nexus] rene_r:
Use the app BetterBatteryStats to find out why your phone isn't entering deep sleep.

br

rene_r
[Samsung Galaxy Nexus] raubkatze:
Set CPU frequency to stock values and choose ondemand governor. There are almost the same values on CV tab now. Such is the way of Smartreflex)

But you can always disable it and use your current stock or undervolted values.
[Samsung Galaxy Nexus] nklenchik:
Reboot your phone and it should fix it.

Thats like crippling it :p
[Samsung Galaxy Nexus] raubkatze:
It's simply brutal)
[Samsung Galaxy Nexus] 6jaipur6:
Have you solve your problem? I have same configuration and same problem don't enter in deep sleep.
[Samsung Galaxy Nexus] marshy73:
Unfortunately no. Even after reboots.
[Samsung Galaxy Nexus] franciscofranco:
Next app update will have core and iva undervolt interfaces. I should ve had added it already.
[Samsung Galaxy Nexus] darkmanx2g:
I'm getting much better battery life on r130 gpu512. Hitting 4+ on screen time. With r133 im averaging 3. I'm sure milestone will be perfect tho.
[Samsung Galaxy Nexus] Serious_Beans:
Dude something is really messed up with this kernel. Its wayyyy to smooth and feature packed and worst of all!!! The battery won't drain fast enough. This is the worst kernel ever.
[Samsung Galaxy Nexus] nklenchik:
Is this later today perhaps?
[Samsung Galaxy Nexus] franciscofranco:
No. Visiting my GF today so no coding.
[Samsung Galaxy Nexus] Remoteconcern:
I'm assuming your GF is your Galaxy Note? ;)
[Samsung Galaxy Nexus] kashix:
obviously not. :D
[Samsung Galaxy Nexus] vomer:
Ha! what is this elusive creature you talk of?
[Samsung Galaxy Nexus] droidholic:
I have to agree....I thought it was just me. Used 133 and the leakage was just too much for me. I went back to 130 gpu512 like you. On 130, I got just a little over 5 hours of screen time(4G entirely), which is the highest I have gotten out of the different kernels I have tried.

Franco, whatever you did on 130 was amazing!
[Samsung Galaxy Nexus] RensoreK:
How on earth does ANYONE get over 3.15 hours on the Galaxy Nexus without an extended battery? Screen on 0% brightness?? I tend to use autobrightness and never get past that. Pics or it didn't happen I would say!
[Samsung Galaxy Nexus] endymion2k5:
First i would like to thank francisco for this amazing kernel, i totally love it, all the effort that goes into it and into the application (which i baught out of respect and for support) well done!

Im sorry if this question has been asked before, havent read all posts (try to do it daily, missing a few each day, quietly without responding ;))

Is there any difference in voltages when we compare the 384 mhz gpu to the 512 mhz gpu? I do not play any intense games that require the 512 mhz, yet it feels smoother then the 384 mhz. Im very keen on saving any battery power and gaining a few more hours of battery life. Does it make any difference? (read some posts about people not being able to run 512 mhz on the new 133 nightly, i have no problems so far and i do not notice any artefacts, altho i generaly do not play any games, artefacts might come once used heavily and under stress?)

Thanks in advance
[Samsung Galaxy Nexus] pewpewbangbang:
This was with r121 and liquidsmooth 1.25. Hotplug governor, auto brightness, no default UV but I'm sure smartflex was on. I don't have Franco app but yea.

I'm trying out r133 right now and slim ICS
[Samsung Galaxy Nexus] raubkatze:
Already posted ) http://xdaforums.com/showpost.php?p=24748626&postcount=12072
[Samsung Galaxy Nexus] dwang:
r133 is more responsive than r130, which means its probably spending more time at the higher speeds, so that's probably what is contributing to the shorter battery life.

I can also confirm that I'm getting worse battery life. I was able to get over 5 hours of screen on time w r130, but only about 4 hours with r133. But the increased responsiveness of r133 is worth it IMO as I always carry a spare battery in my wallet.

Deep sleep seems fine however. I only got 3% battery drain overnight for 8 hours.
[Samsung Galaxy Nexus] pewpewbangbang:
doesn't compare to mine :p but you have more standby
[Samsung Galaxy Nexus] palisaide:
Just wanted to share something interesting that I encountered yesterday when attempting to flash #133. First off, I've been using Francisco's kernel since nightly 8 and have never had any issues with SOD or anything. I've always used 512 MHz GPU builds since they have been available and have never had any issues (I sometimes got some artifacts with Smartreflex enabled, so I usually had it disabled). However, yesterday when I flashed the 512 build of #133, I could never get past the bootloader (Google) screen. The screen goes blank for about 10 seconds before rebooting. I tried flashing: 1) using the app; 2) in CWM recovery; and 3) flashing boot.img over adb. Every time I got the same results. I thought that possibly some init.d scripts were causing issues, so I removed them all and still could not get the phone to boot.

Eventually, I tried flashing the 384 build and everything worked fine. I'm not complaining, and it appears as though I am the only one who is having this problem, I am just confused as to why all previous builds worked fine with GPU @ 512 (or at least they booted). I am running Axi0m PZ M1, but I doubt this has anything to do with it as it seems like the kernel doesn't even get fully loaded before the phone starts bootlooping.

Correct me if I'm wrong, but there are no way to get any logs in this situation, right? dmesg will only show the logs for the most recent boot and it appears as though logcat hasn't even started before the phone reboots. I'd like to keep running at 512 since my phone did not seem to have any problems until this build. Any advice would be appreciated. Thanks!
[Samsung Galaxy Nexus] raubkatze:
For me r133 is better.

About 10,5 h after charge, 1,5 h screen on - left 63%
[Samsung Galaxy Nexus] RensoreK:
"No secrets) You can get 4+ or 5+ hours using

2000mAh

battery. But using 1750mAh I had 3+ hours lightly:"

As stated before, without an extended battery you can usually expect to hit ~3.15 hrs... Not 4+ or 5+ as some people say.
[Samsung Galaxy Nexus] Stretlow:
What Rom you running at the moment pal?
[Samsung Galaxy Nexus] latiszm:
I have the exact same issue. Think it has to do with Franco lowering voltages for the GPU.
[Samsung Galaxy Nexus] stupidslow02gt:
I hit 4.15+ on a stock battery everyday.
[Samsung Galaxy Nexus] raubkatze:
Doesn't compare a priori )

On my mind one can compare devices with the same batteries inside one cellular network or max inside country. For example my old blackberry 9000 works in Russia about a day but in Europe (eg in Germany) it lives 1,5-2 day... Networks is better - less battery drain.
[Samsung Galaxy Nexus] RensoreK:
http://xdaforums.com/showpost.php?p=24714637&postcount=11945

<-- I Think it has something to do with with new voltages on this kernel. Some devices can handle the changes, franco could comment in more detail on it when he gets around.

---------- Post added at 01:46 PM ---------- Previous post was at 01:44 PM ----------

Can you post screenshots of that? Battery usage, screen on time and tell us users what kernel settings you are using and what ROM?
[Samsung Galaxy Nexus] pewpewbangbang:
Did you look at my post and screen shots? That was with stock battery
[Samsung Galaxy Nexus] raubkatze:
Hmm... Screenshots are exactly from device with stock battery. But one can easily to get 4+h on stock battery but only at the expense of standby time.
[Samsung Galaxy Nexus] mistermojorizin:
testing 133 -

with conservative governor and generic hotplug DISabled, the gpu voltage stays at 848mva

with any other governor, or hotplug enabled, it jumps up to 1012mva or so
[Samsung Galaxy Nexus] yoshi161:
My screen-on time is over 7h with r133.

first 4h with almost ebookdroid and few email and internet browsing (49%/4h)

last 3h with normal use (50%/3h)

brightness: 0% (except 10min auto)

3G network and sync on

wifi off

franco kernel r133 GPU 384Mhz

battery size is 1750mA

rom is liquid ics 1.25

stock setting with interactive governer

Before r130, my record was 6h with 3G data off.

I think r133's screen-on time would be over 9h without 3G data.

r133 extended over 30-50% screen-on battery life.

screenshot is attached.
[Samsung Galaxy Nexus] raubkatze:
By the way your screenshots are not visible

I wrote about - http://xdaforums.com/showpost.php?p=24761954&postcount=12104

And Franco wrote about update - http://xdaforums.com/showpost.php?p=24764982&postcount=12110
[Samsung Galaxy Nexus] RensoreK:
I don't think you posted any screenshots, I see nothing on your last 10 or so posts.
[Samsung Galaxy Nexus] pewpewbangbang:
Damn must be because I liked from my gmail.

These should work, straight from phone

View attachment 999457
[Samsung Galaxy Nexus] pewpewbangbang:
Nvm idk what's going on can't upload......but yea

I got 3 hours 20 minutes display with over 11 hours on battery and had 40%	battery left
[Samsung Galaxy Nexus] drawde40599:
@franco

I hit 15 hours screen on time with stock battery, I'll post pictures soon as I'm done photo shopping them .... @ Franco u post all tweaks and updates to ur Google + account also right?
[Samsung Galaxy Nexus] yungboss22:
Flashed the r133 kernel (512mhz) and freeze after 5 min. Bootloop ... need to wipe all my data...... -______-'
[Samsung Galaxy Nexus] mikeandjaimie:
Standby time doesn't mean anything if you don't use your phone! I get 4+ hours screen time on stock battery all the time but I use it for everything.. I don't expect to get over 24 hrs with that much screen on, but I do make it through most days I'm away from a charging source. I've never had my phone die cause I ran outta charge.
[Samsung Galaxy Nexus] jcmm11:
I can tell you that in 133 he set the 512 voltage to be the same as the 384 voltage. The echo command he provided earlier resets the voltages to the old levels.

If you need the old voltage levels your best bet is probably an init.d script

You can also probably try an intermediate voltage level and see if your device works with a smaller undervolt even though it can't handle the full undervolt
[Samsung Galaxy Nexus] mistermojorizin:
after rebooting, the gpu values are stuck at 1000 again. unchecking all options, and rebooting, completely back to stock kernel settings (on demand, stock voltages, smartflex, etc etc) and still stuck at 1000 gpu voltage.

i don't quite understand how the new version of the app will change things. since the kernel is supposed to work with or without the app.
[Samsung Galaxy Nexus] jnr21:
You don't need to wipe data, just flash other kernel (r133 384mhz version)
[Samsung Galaxy Nexus] yungboss22:
Nothing to do , wipe was the only solution :(
[Samsung Galaxy Nexus] palisaide:
If that ever happens in the future, you can always extract the boot.img file from another kernel .zip and flash it with fastboot:

fastboot flash boot boot.img
[Samsung Galaxy Nexus] schizophrenia:
WiFi Direct

not sure if it's totally off topic. Is the WiFi direct working for anyone?
[Samsung Galaxy Nexus] latiszm:
Is it possible to make a flashable zip with the 512Mhz GPU voltages Franco suggested? I cant even boot, so its kinda hard to change them through adb :(
[Samsung Galaxy Nexus] BrUhNiGGs:
Temple Run is choppy at times and lags when I turn or jump sometimes. Going to try 384 and see if it persists. And what is suggested voltage values for 512 MHz GPU?
[Samsung Galaxy Nexus] pewpewbangbang:
Here's what I was getting with r121 and LiquidSmooth v1.25 (Probably one of the best ROMs for battery life.....want to try Gummy when it releases)

View attachment 999597

View attachment 999598
[Samsung Galaxy Nexus] michi_1983:
hey guys,

is anybody else having the issue that if you receive a call the ringtone appears but you just cant pick up the call, screen stays black, with 133 nightly?

greetz
[Samsung Galaxy Nexus] ChongoDroid:
nandroid

Sent from my francoPhone
[Samsung Galaxy Nexus] raubkatze:
Agree but not quite.

In standby device gets mail, syncs with google and social networks etc etc. It doesn't sleep. And therefore It loses charge anyway.

In quoted post I meant that the longer is on screen the less total time of work.
[Samsung Galaxy Nexus] stupidslow02gt:
Ok before I explain exactly how I achieve 4.15+ hours of screen on time with a stock battery EVERYDAY, I would like to say one thing. One of the most commonly overlooked things that smartphone users do not realize is that setting your brightness to auto, and then sitting directly under a halogen light while you're at work all day is essentially using your phone on full brightness. The phone thinks you're standing out in the sun and turns the screen up to compensate. I now use the toggle in my rom to drop brightness almost all the way down when I'm sitting directly under a light source like that. If I need it all the way dark because I'm in bed for the night, or all the way bright because I'm out in the sun, I turn on auto brightness. I have a toggle right there from my notification bar (cm9). This single solution alone is how I started to get over 4+ screen on time.

Anyway here are some tips I have for extending your screen on time:

First off, SCREW the Facebook app. It will idle at 23-78% CPU load for no apparent reason when you multi task away from it, it is also a huge CPU, memory, and battery hog while you're using it because it is a poorly written app. I still have the app because I like to use the widget but I NEVER open it. I use the mobile site to actually use facebook.

Check partial wakelocks whenever you flash a new rom or kernel. You never know what mistakes may have been made and you need to keep an eye on that. One partial wakelock can destroy your battery.

At work, I didn't realize it, but I sit in an area that nets me 1-0 bars of service all day long. I didn't really mind before, but now that I know that I lose 10% throughout the day just by having poor service, I stay in airplane mode when I want to conserve. Its ok though because I have a microcell laying around and Im going to install it under my desk LOL

Here is one more commonly overlooked thing. When your phone is on a 3G network, all texts and MMS will be transmitted over 3G, not 2G, even if you are on wifi. This is crucial for text-heavy users. I always leave my phone on 2G networks only unless I absolutely need to use 3g. That way all my texts will go over the less battery hungry network.

So here are my stats currently:

Latest cm9 nightly 4/11/2012

Franco Kernel r122 (384)

Processor clocks 384-1344

5% and auto brightness - switching when needed 2g network only

wifi all day

Latest 4.04 radio and bootloader

chrome browser (no flash)

I will post screenshots if requested.
[Samsung Galaxy Nexus] kashix:
didn't take me very long to read all that but still, screenshots please. :D
[Samsung Galaxy Nexus] mikespe:
Buy a flip phone...problem solved! I bought a smartphone to actually USE it's features! I get almost 4hrs screen time WITHOUT doing what you do. WIFI whenever I'm home, auto brightness is ON, 4g is OFF, GPS is OFF, all notifications are OFF except email & texts.....doing this I get anywhere from 3.5-4hours of screen ON TIME and about 18+ hours on a charge. During this time I may listen to mp3's or stream Sirius radio, surf the web, text, email, etc....if I did what you did I couldn't justify having a $300 smartphone & $30/month for data...get a flip phone & save TONS!
[Samsung Galaxy Nexus] stupidslow02gt:
I don't see what screenshots will do other than prove what I've just said. You don't believe me? :D
[Samsung Galaxy Nexus] franciscofranco:
Whoa I cant even take a day off... The ability to undervolt iva and gpu was in the kernel since ezekeel released the mod, but I never talked about it to save my ass from "omg sod, fix nao" posts.

Next app version will have an ui interface to change the voltages.

And now Im gonna drink with my girlfriend. Have fun people.
[Samsung Galaxy Nexus] kashix:
please get into the state of Ballmer Peak ;) better coding for XDA community :p
[Samsung Galaxy Nexus] Moz007:
Don't forget to try the last nightly on her phone !
[Samsung Galaxy Nexus] chakra:
Have fun, how do you have the time for a girlfriend :) JK. You deserve a day to yourself, or you and her that is.
[Samsung Galaxy Nexus] bendirkss:
2G rather than 3G
[Samsung Galaxy Nexus] nikulogical:
I've ran every nightly since 512 gpu was implemented and this is the first time I had artifacts on my screen.
[Samsung Galaxy Nexus] lukasb9000:
Same for me!

And the app stabilitytest gives me gpu errors when I do the cou + gpu test;

back to r130 512 for now
[Samsung Galaxy Nexus] nikulogical:
My artifacts haven't come back but I'm getting g stutters in games which has never happened.
[Samsung Galaxy Nexus] nikulogical:
oh the tweak franco posted earlier seems to have fixed the stuttering/artifact issue with 512 gpu
[Samsung Galaxy Nexus] xHausx:
Easy now fellas, there's no point in getting all worked up over trivial things from people you're never going to meet.

I've cleaned the thread up so please be respectful to Franco by keeping it friendly here.
[Samsung Galaxy Nexus] ChongoDroid:
I'm getting some nasty lag in the app drawer of the latest apex launcher. Tried the 384gpu and it was even worse, so back to 512.. phew thought my phone couldn't handle it for a sec.

Sent from my francoPhone
[Samsung Galaxy Nexus] sishgupta:
Ive been hearing this is an apex thing. Nova users not experiencing this
[Samsung Galaxy Nexus] drawde40599:
No happens with nova also, its the 512 gpu its acting different on everyone's phone....cause I tried both launchers. Cm9 launcher working fine for me tho....
[Samsung Galaxy Nexus] TwinkyOfHope:
I'm also using the latest apex launcher, are you getting choppiness when using the home button to get to the main screen?
[Samsung Galaxy Nexus] BrUhNiGGs:
I've always experienced choppiness and lag after going to drawer and back out to the home screens. When swiping through screens it lags for a few and then back to normal. Happened with every kernel I've tried. Never really tried Nova so I can't confirm if its just an Apex problem but it could be

Edit: I just tried nova and it lags when swiping screens after pressing home button from app drawer. It could be the fly in and fly out effect that causes this
[Samsung Galaxy Nexus] leelaa:
It must be, i allways disable them and literally have 0 lag.
[Samsung Galaxy Nexus] spaceman860:
R133 512gpu aokp b31

729/1344 CPU

Interactive governor with generic hot plug

Wifi always on

Auto brightness

Stock battery

after 9 hours of sleep lost 4% then all day of use 19h 13m 5h screen on

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] Flukester69:
I get similar results using BAMF Paradigm 1.2 and Foxhound 0.4, no hot plug but with custom voltages, stock battery.
[Samsung Galaxy Nexus] nikulogical:
is there a way you can tell if generic hotplug is working if its enabled though terminal?
[Samsung Galaxy Nexus] pewpewbangbang:
Can't see your screenshots. Uploading via XDA app doesn't seem to work.

And yea.....do we need the Franco app to have things like generic hot plug, smartflex, etc...enabled?

Would I get better battery life having MIN cpu set at 729? I'm hearing mixed things, like voltages are the same.....but won't it undervolt a lot lot more on 384mhz than 729mhz?
[Samsung Galaxy Nexus] rob151515:
Yeah, same here though IMO it's in someway related to the softkey glow animations. I'm running CM9 and have applied a mod which almost disables the animations (shortens the animation time length) and the lag is gone for me.
[Samsung Galaxy Nexus] franciscofranco:
Excessive battery drain should be fixed in the next nightly, I'm running tests in my device as we speak. Although wifi on doesn't really count as having the device sleeping.
[Samsung Galaxy Nexus] Andrmgic:
Sweet.

I'm looking forward to testing it out :)

Thanks for all of your hard work!
[Samsung Galaxy Nexus] triStateMindgate:
Yup, best combo iv'e tried so far.
[Samsung Galaxy Nexus] beekay201:
LOL *facepalm* yeah sure, i'm a liar.
[Samsung Galaxy Nexus] offenberg:
Merry xmas btw ;)
[Samsung Galaxy Nexus] StuMcBill:
Any way to get this working with GTA 3?

Seems Mega snappy on nightly 4!

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] offenberg:
Are you saying GTA 3 doesnt work with this kernel?
[Samsung Galaxy Nexus] StuMcBill:
Doesn't with me. It worked on MoDaCo kernel but it doesn't launch on Franco kernel.

I think it was reported that it was something to do with the SD card read / write patch.

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] beekay201:
also with matr1x 1.5. read a few pages back, find francisco's awnser on that. tip: also related to IML74K.
[Samsung Galaxy Nexus] jhericurls:
20th December - nightly #2

* Hacked sdcard binary to fix the huge CPU usage when using the /media partition - credits to DebauchedSloth

This updated has stopped GTA from working.