yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dpaine88:
As for the app goes..

Is the "Sound Control"- "Increase max sound volume"

is that just for headphones or for the phone speaker as well?
[Samsung Galaxy Nexus] franciscofranco:
Headphones as far as I know. Speaker is on the OS side. Next Liquid rom will have speakers volume increased for Maguro and Toro.
[Samsung Galaxy Nexus] samizad:
Damn. I really like Liquid but I can't use it because it only has English language support.
[Samsung Galaxy Nexus] jcmm11:
+1 on this. Phone definitely being much warmer than usual. This is with 512. Might try 384 to see if that cools it down somewhat. Phone running fine though, at least so far. Obviously need more time to know for certain. Bamf 1.2, interactive governor, go_hispeed_load tweaked to 85, 384->1344, hispeed_freq 1344, genetic hotplug off
[Samsung Galaxy Nexus] nikulogical:
Why do you a lot of people keep generic hot plug off when using something other than hot plug governor? I was under the impression that generic hot plug couldn't really hinder performance or battery it could only decrease sleep drain
[Samsung Galaxy Nexus] spinkick:
we keep it off because we look at the screen and turn it off and on a lot so turning on and off the cpu like that uses more power than it saves.
[Samsung Galaxy Nexus] ch33kybutt:
Please do correct me if I'm wrong, but I believe that SR class 3 is only for devices based on OMAP343X ...

arch / arm / mach-omap2 / smartreflex-class3.c

/* Smartreflex Class3 init API to be called from board file */
static int __init sr_class3_init(void)
{
/* Enable this class only for OMAP343x */
if (!cpu_is_omap343x())
return -EINVAL;

pr_info("SmartReflex Class3 initialized\n");
return sr_register_class(&class3_data);
}
late_initcall(sr_class3_init);
[Samsung Galaxy Nexus] franciscofranco:
Why they want it to run only on 343X I don't know. According to Ezekeel by TI's errata SR1.5 should run better on our device, but I think this SR3 is worth a try. Personally I don't like automatic voltage scaling by software like SR1.5.
[Samsung Galaxy Nexus] nklenchik:
I haven't seen any real battery drain issues. I've been playing music for a good 2 hours too.

Tomorrow I'll be in a ****ty signal area...won't really help for testing :o
[Samsung Galaxy Nexus] Gahh Its Lee:
So you don't use sr??? I'm curious to know this one.
[Samsung Galaxy Nexus] franciscofranco:
I do, but doesn't mean I like it :)
[Samsung Galaxy Nexus] AdrianE46:
Since flashing 138 i get these weird screen artefacts, like points or tiny squares of different colours. Can't get a screenshot though as they come and go. Not a big issue as they are rare, but still a bug. I'm on 512 gpu now. Gonna try 384 tomorrow and see if there's a difference.
[Samsung Galaxy Nexus] SupWiz17:
Flashing 384 will fix it for you. Your phone just cant handle the overclocking of the gpu at that speed.
[Samsung Galaxy Nexus] Gahh Its Lee:
Sounds good lol. I guess that's how it goes sometimes. This kernel is running great. Seriously quick. My battery life seems tolerable too which is a first. Is the BLX working for you?
[Samsung Galaxy Nexus] dpaine88:
Is there any point in overclocking the GPU? From what I have heard there is almost no performance improvement..
[Samsung Galaxy Nexus] milander:
Try it and find out yourself :)

Sent from Galaxy Nexus using Tapatalk 2
[Samsung Galaxy Nexus] BrUhNiGGs:
I know what you mean. I had some little black square that showed up in Temple Run that sometimes comes and goes.

Man, my phone gets VERY hot when I play The Sims Freeplay or any other game. Maybe I should go to 384 GPU.
[Samsung Galaxy Nexus] Gahh Its Lee:
Yea if you get artifacts you should go to the lower clock it'll fix it.
[Samsung Galaxy Nexus] schizophrenia:
same here having artifacts on r138 512 GPU

it runs perfectly on r135 with 512

i know it will runs fine on 384 GPU yes but I will therefore lose the extra performance
[Samsung Galaxy Nexus] nikulogical:
No artifact or stuttering issues here with r138 512mhz. Battery drain seems quicker but it not enough time to tell for sure.
[Samsung Galaxy Nexus] BrUhNiGGs:
Well, im not necessarily seeing artifacts ALL the time with the 512 GPU. It has happened to me only twice and that was with r135. Not a big issue, but we'll see how it goes with r138. Just played Temple Run and so far so good.

And by the way Franco, are you aware with the BLX issue on your app? My percentage always goes to 100% instead of the valued 96%
[Samsung Galaxy Nexus] schizophrenia:
i usually use Nenamark2 as a benchmark for seeing Artifacts or not

on Nenamark2

r130 512mHz (and everything before) - no artifacts

r133 512mHz - heavy artifacts

r133 512mHz (with tweaked voltage) - no artifacts

r135 512mHz - no artifacts

r138 512mHz - heavy artifacts
[Samsung Galaxy Nexus] BrUhNiGGs:
Yeah I just ran nenamark2 and saw no artifacts at all. It seems the only issue I have with 512 GPU is the temp when playing heavy games.
[Samsung Galaxy Nexus] DaLoona:
Nevermind my previous post here, below explained it already, silly me :o

Keep up the great work :cool:
[Samsung Galaxy Nexus] bigeyes0x0:
And if you read the changelog, that would have solved it as well.
[Samsung Galaxy Nexus] drawde40599:
how the hell

how someone could just download and install anything on any device without reading what the hell it is just blows my mind o_O !!!

**** 138 its fast !! reminds me of 110
[Samsung Galaxy Nexus] GibMcFragger:
Its like those terms of service nobody reads before clicking "ACCEPT" when they install software, lol.

Swyped from my GNex on CM9.
[Samsung Galaxy Nexus] drawde40599:
Funny
[Samsung Galaxy Nexus] bigeyes0x0:
Well I actually read MS Windows TOS once because I was bored then. I shouldn't have done that, it didn't elevate my boredom only made it worse lol.
[Samsung Galaxy Nexus] DidierSchnee:
Does anybody know what BTLowPower Kernel Wakelock means?

im on stock rom with franco.kernel r135

THX
[Samsung Galaxy Nexus] Bosio91:
I noticed that in the Franco.kernel widget, at first the temperature is always showing as 0.0°C/x.x°G (first screenshot), and after I touch it it changes to the actual temp. In °C, and another value for the °F (second screenshot).

Is this normal?

Thanks for the help, and cheers for the amazing kernel you created Franco!
[Samsung Galaxy Nexus] drawde40599:
here u go http://www.google.com/search?rlz=1C....,cf.osb&fp=98d5445c5607bd30&biw=1366&bih=667
[Samsung Galaxy Nexus] Metallice:
If your getting artifacts on the new build its not because you can't handle the high clock gpu. It means your phone doesn't like the decreased vsaum and vaux3 (or whatever) regulator voltages Franco introduced.

Our phones' ability to tolerate these voltages obviously varies greatly as I have them set even lower. I'm also using this 138 with Lazy governor and SIO scheduler added in and I'm loving it. Great work Franco.
[Samsung Galaxy Nexus] Bosio91:
I can't get the first screenshot to show on my first post for some reason...

Nevertheless, as I say, the Temperature values BEFORE I touch the widget are 0.0ºC/32.0ºF
[Samsung Galaxy Nexus] DidierSchnee:
well thx for the google link, didn't know that there is something like a search engine.

no answers, just questions.
[Samsung Galaxy Nexus] schizophrenia:
yup I know

thanks for confirming too

unfortunately I can't and dont know where to tweak the voltage

hence I lose the extra performance
[Samsung Galaxy Nexus] GibMcFragger:
Lol. I can imagine.

Swyped from my GNex on CM9.
[Samsung Galaxy Nexus] raubkatze:
r138 (512).

Looks smooth and has great performance. Benchmark results are same as on r135. No artifacts, screen lags and any issues but for the last hour I lost 5% when screen is off. It's no good for me. I had 0.9%/h on the average using r135 (512).
[Samsung Galaxy Nexus] drawde40599:
I'm not sure what u said?? But after reading for a few, looks like rouge app, or possible radio issue?? I'm not showing it on 138 as a issue so most likely not this kernel, could be wrong but i dont have that issue ....

---------- Post added at 10:43 PM ---------- Previous post was at 10:36 PM ----------

Mine showing temp just fine don't have to touch it
[Samsung Galaxy Nexus] DidierSchnee:
im saying that i already used google and that there are no answers to my question only that it has something to do with bluetooth, but BT is deactivated on my nexus.

so i thought why not ask this question here, firstly because im using franco.kernel and secondly the guys here are the specialists.

btw im still on r135

edit: Bluetooth is broken completly, i cant activate it! a restart did the trick
[Samsung Galaxy Nexus] drawde40599:
beast!!

138 running great!! Way fast stock, over locked and interactive is a beast!!! Don't no about battery yet, but I own a charger so who cares!!! Very smooth on this one
[Samsung Galaxy Nexus] raubkatze:
Good advice... I own a charger too but periodically I simply can't use it because I have not power receptacle nearby.
[Samsung Galaxy Nexus] rubino90:
my noob question for user new smartflex system i tap or not in the lastest page of paid app franco? if i tap i looser my undervolt?
[Samsung Galaxy Nexus] maniac2403:
Yes, if you enable Smart Reflex, you loose the under volt's you set. Just disable Smart Reflex to get them back.
[Samsung Galaxy Nexus] rubino90:
many thanks friend ;) the new 138 is smooooothhh thanks franco
[Samsung Galaxy Nexus] raubkatze:
Abnormal 5% battery drain was solved with reboot.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] maisi:
Getting heavy artifacts when playing games on b138-512 , I've never had any artifacts before so this might be related to SR 3?
[Samsung Galaxy Nexus] SubyWill:
My phone is FLYING on 138. I'll see how battery life is with more time.
[Samsung Galaxy Nexus] BrainShutdown:
Same here :(
[Samsung Galaxy Nexus] Theshawty:
Use 135 instead. 138 is more experimental.
[Samsung Galaxy Nexus] EsPeHil:
Holy hell. #138 seems a lot smoother. At least in regular menu and homescreen scrolling. (Nova launcher. Previously I was getting random jittering.)
[Samsung Galaxy Nexus] Razer(x):
Need reports about battery, wasn't so good in previous release.

Also i would like to have a non-OC version
[Samsung Galaxy Nexus] raubkatze:
Went back to r135. Unfortunately I'm not happy with r138. Yes, it's smooth and quick but:

1. battery drain is larger than on r135 (doesn't matter screen on or off)

2. min cpu temp is 37˚C. An average temp when for example I'm using browser (not playing) is 49-51˚C. Device is really hot like frying pan.

3. I used maps only 1 minute and now I have 2h 12m "gps-lock" in kernel wakelocks. My battery charge melts before your eyes...
[Samsung Galaxy Nexus] asim0:
Hi franco, i'd like to know if a milestone is coming soon (not pushing, m2 is as stable as can be)

Also, I read the thread from time to time to keep me updated, and I feel like reading the same comments over and over about battery, voltage, smoothness, gpu clock and governors; I know you take care of the feedback of the community, and you often hit the thanks button too; but i feel like this thread is not an efficient way of collecting user experience feedback, so I'd like to know have you thought of automating the process?

I was thinking of a little survey available via your app with say 20 questions about rom used, parameters, and then user experience feedback on 'smoothness', battery graphical glitches.... also usage time since kernel flashed (interseting and would incite people to use the phone a certain amount of time, avoiding reporting battery drain after 5min use...)

I know you app can send crach reports, but for user experience something like this could be useful with such a large user base; also would help choose features for bug-free milestones;

Anyway just my two cents, keep up the good work
[Samsung Galaxy Nexus] grumphy:
+1

I support the suggestion!

And of course I express my appreciation for the great work so far!
[Samsung Galaxy Nexus] JcMalta:
#138 Running hot?

All Franco kernels have been great and have never had any trouble with any nightly build before...

#138 seems to be running hot ..... just 40 minutes of "surfing" new sites etc. (Google Chrome beta) .. then I noticed the top/back (near the camera) getting quite warm .... checked the app ..... it reported 56C (ambient around 18C)

I have never paid attention to heat/temperature before so I cannot say if this is "good or bad" .... but it is certainly the first time I have noticed my Gnex getting warm....

I am running Bamf 1.2

Franco #138, 512GPU (flawless) ... 1228/384 ondemand + generic hotplug.
[Samsung Galaxy Nexus] Aztriltus:
Did anybody benchmark their phone by playing Temple Run?

I would like to report my findings on r138.

First of all, I'm on CM9 latest nightly with hotplug governor 384-1036mhz.

I rebooted my phone and all the voltages were back to default, with SmartReflex enabled. I played Temple Run v1.02 and during the first transition from the play button to the screen turning into the other direction, there was 3 pauses of lag. Maybe 0.5s of lag each. I continued playing and I saw some artifacts (trees in temple run have melted spots). Moreover, during the game play, there were a few sudden drop in frame rates to about 1-2fps and it returned to normal in 0.5s. It seemed like a sudden freeze.

Secondly, I switched off SmartReflex, still keeping the voltages stock. In addition, I force closed temple run and ran it again. Likewise, the initial transition had 3 short pauses. As I continued playing, there were no signs of artifacts but there are still drop in frame rates. However, this is different from the first because the frame rate dropped to about 10-30fps. The game is still running, just that it sorts of slow-mo for 1-2s each time it occurs.

Lastly, I did my usual undervolting for everything; CPU, IVA, CORE. Temple run was force closed and once again, there were 3 short pauses at the initial transition. This time, there were no lags or artifacts during gameplay. Although I still witness a really slight lag of about 0.05s (I'm just guessing :D), it was very very negligible.

If you have noticed, there were short pauses after the start of temple run. It does not occur if I replayed the game without force closing temple run. Does anyone of you experience the same thing? I can't say for sure about r135 on my phone though.

Moreover, I got no idea why my undervolted values are better than stock values despite disabling SmartReflex. On the other hand, SmartReflex just made everything worse for my phone ;o Seems like the VAUX and stuffs may be linked to it?

Okay. Now on the battery life. (take this with a pinch of salt since I've only tried for a full day)

r138 gave me 30minutes of screen on time by using 12% of my battery. Theoretically, I would have gotten 4hrs with 4% left and I'm sure that would happen since it was constant for 1.5hrs. It was through the use of texting/whatsapp, some ScrambleWithFriends, DrawSomething, browsing and franco app. Other useful info includes autobrightness, CM9, hotplug 384-1036mhz, no smartreflex, BLX 96%, generic hotplug off, autosync off, 3G on throughout. I just like hotplug 384-1036mhz ;)

One more thing, Franco with CM9 is definitely smoother + more responsive + better battery than Liquid 1.25 (I've tried Liquid for 1 month+) I hope this helps ;)
[Samsung Galaxy Nexus] RensoreK:
When you get jittering does restarting the SystemUI smooth things out? (Kill the SystemUI process, or in your ROM change any setting that causes SystemUI to restart such as enabling {then disabling} horizontal recents) you will notice everything smooths out again, I don't think its a kernel issue but more of a system issue, happens on any launcher, any ROM.
[Samsung Galaxy Nexus] franciscofranco:
Thank you all for the feedback. Some make sense, some doesn't. Specially the hot part. 50% says it's cooler, other 50% says its warmer, now hows that for debugging :p
[Samsung Galaxy Nexus] myrdog:
Great idea. Will really help out with some of the repetitive post-release clutter in this thread too. That or even just a wiki page that's managed by the community to allow posting of known problems with the build and a more extensive FAQ. Frankly the OP FAQ doesn't really have anything I've seen to be a FAQ in the last 50 or so pages.
[Samsung Galaxy Nexus] franciscofranco:
Yes it's a great idea. I'll work on that.
[Samsung Galaxy Nexus] raubkatze:
I noticed temperature issue on r138 (512) + AOKP b32

1228

729

no UV

interactive governor

generic hotplug off

SR on
[Samsung Galaxy Nexus] SkaDiZ:
+1 on this... After i flash b138, everything fine until i started to play defender 2 for about 1 hour then i notice artifacts become weird for about 30 sec then back to normal... This artifacts doesn't stay long and seldom appear.. I guess would be the Smartreflex 3 that playing with the voltage... Back to b135 that work perfectly on 512mhz.. Hope this help..

BTW, i did notice the temperature slightly high too...
[Samsung Galaxy Nexus] audibalso:
He mentioned that he was close, next week tops.
[Samsung Galaxy Nexus] j0h4n:
My phone runs smoother but also a bit hotter with 138.

Franco have you considered to add the ability to auto-flash like the 5-10 most recent nightlys?? It would be a realy nice feature if someone would have to revert to a older nightly form the most recent, if the most recent is experimental like this last one(138).
[Samsung Galaxy Nexus] jhericurls:
Battery life for 138 seems to be about the same.

70% battery, 6 hrs on time, 1hr 15 mins screen time.

#130 is still the best for battery life for me.
[Samsung Galaxy Nexus] The Nexus Project:
A setting to save profiles similar to set cpu would be cool

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] Langduscher:
+1

r138 is supersuperfast :eek: :D - yet batterylife is about the same as r135 : ):cool:

Running the 512mhz kernel, no problems (no 512mhz kernel has ever given me probs)

Also temp seems to be roighly the same as it was. Not noticably warmer anyway.
[Samsung Galaxy Nexus] franciscofranco:
That would take a lot of work, it aint viable for me.

Maybe. It's an idea.
[Samsung Galaxy Nexus] WesMantooth:
Latest nightly is quite smooth but I also notice the increased temperatures. Currently, with my phone sitting idle @ stock 1228/384 the CPU temperature is 43 degrees Celsius.
[Samsung Galaxy Nexus] drawde40599:
settle in

@Franco should u not let a new kernel flash " settle in for couple days before judging battery? Or is this a myth?
[Samsung Galaxy Nexus] mgear356:
2nd that.. i notice the increase in temperatures
[Samsung Galaxy Nexus] nklenchik:
Phone runs from 36C to 40C consistently. Not too bad
[Samsung Galaxy Nexus] GibMcFragger:
Third that. It's smoother but definitely warmer. My phone gets quite warm now with any kind of usage. It never did on any previous build.

Swyped from my GNex on CM9.
[Samsung Galaxy Nexus] franciscofranco:
r139:

STILL EXPERIMENTAL BUILD

* Reverted lowmemorykiller patch that was possibly causing one or two FC or some lag issues

* Reverted extreme VAUX3 and VUSIM voltages to reduce artifacts

* Added new Sync Framework from Google's android-omap-3.0 repo - I suggest you read the commits from my repo to understand what is it

* Added more interactive governor patches from android-omap-3.0

* Added more relevant OMAP4 patches from omapzoom

Builds are going to be shorter now because I want to rule out bugs/errors/problems as fast as possible for Milestone 3.
[Samsung Galaxy Nexus] raubkatze:
Thanks for great work! Now flashing.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jefbuan:
thanks..running 139 with 512 without artifacts when playing temple run
[Samsung Galaxy Nexus] WesMantooth:
Just flashed 139, temperatures are still quite high. After rebooting during kernel install, I hit a high of 63C while loading various start up items. Other then that, it's quite snappy and seems stable.
[Samsung Galaxy Nexus] franciscofranco:
Thats normal my GN gets hot if I do that. Let it rest for a while.
[Samsung Galaxy Nexus] raubkatze:
r139 (512) works fine - no artifacts, no lags. There is no issues with "gps-lock" wakelock so far. Waiting for battery discharging report.
[Samsung Galaxy Nexus] giugiu:
With 138 I had 1.4% /h in idle (3g, 3 mails push, various sync) instead 2.8%/h of 133. (battery monitor widget). Best ever so far.

Now testing 139.

Great job franco.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] sago62:
With 139, the interactive, hotplug, gpu512, cpu384_1228 ... I put the phone in charge .... and it is locked Pull off the battery ..
[Samsung Galaxy Nexus] sago62:
With 139, the interactive, hotplug, gpu512, cpu384_1228 ... I put the phone in charge.... and it is locked Pull off the battery ..
[Samsung Galaxy Nexus] nklenchik:
Do you mean a SOD? I have Liquid and sometimes the power button is flaky, I have to use the volume buttons to unlock.
[Samsung Galaxy Nexus] franciscofranco:
Dont use hotplug and see if it locks up again.
[Samsung Galaxy Nexus] sago62:
Yes, sod .... You could not in any way to unlock ... Now it works ... We see
[Samsung Galaxy Nexus] raubkatze:
An hour after flashing. I'm still on 11% - no battery drain at all... CPU temp is 32˚C - it's a larger than on r135 but I'll test further as it's not enough for conclusion.

AOKP b32

autobrightness

512 GPU OC

1228

729

no UV

interactive governor

Generic Hotplug is off

SR is on

---------- Post added at 09:00 PM ---------- Previous post was at 08:50 PM ----------

I tried to use the same settings. No SoD.
[Samsung Galaxy Nexus] mistermojorizin:
i've stuck with r135 because i've been seeing the lowest cpu temps i've ever seen, figured it's good for performance and longevity of the phone.

here's what's weird -

when first installing it, the core/iva voltage stays static at 1012mV or so. it does not deviate from that number for hours.

after running it for 12 hours or so without reboot, the voltage goes down to 848mV, but is dynamic - going up to 1012mV for brief periods of time when the MPU clock speed increases. it is mostly at 848mV now.

if I reboot the phone, it gets "stuck" at 1012mV again. I am happy with it now, but scared to reboot it.

this is all with conservative governor, or conservative+generic hotplug. If i use hotplug governor, the clock and voltage constantly goes up and down, up and down for no reason.

so I'm very happy with it right now - got 848mV on all 3 measures, on conservative + generic hotplug, no other modifications from stock. But i am avoiding rebooting it because i know that it won't stick to this voltage if I reboot. Would love to see m3 come from this branch, but with more consistantly staying at that low voltage. battery is very good for me, and temps are really low, around 33 celcius.
[Samsung Galaxy Nexus] Gahh Its Lee:
http://xdaforums.com/showthread.php?t=1608194

Can this even be real? 2.1 ghz oc?
[Samsung Galaxy Nexus] brmayhem:
R135 seems to be the most stable for me so far. Lower temps and most importantly, no artifacts @512. R138 and 139 give me plenty of slow downs and 512 is a no go in those versions.

r135

AOKP 29

50% brightness

512 GPU

384

1228

No hot plug

Interactive
[Samsung Galaxy Nexus] franciscofranco:
If all the conditions are met and if one has the best chip from the best silicon in the world then yes. The screenshot doesnt lie.
[Samsung Galaxy Nexus] Gahh Its Lee:
I never trust screen shots of ridiculous claims honestly. Almost went to glados but man your kernel is just the best it beats every one I've ever tried.

Edit I'm getting serious lag on the xda app but only on the xda app. Any ideas?
[Samsung Galaxy Nexus] wolfy:
Hi Franco, the latest releases are awesome.

Couple of observations.

AOKP b32.

interactive governor.

No artifacts on r138 512 MHz gpu ran fast and stable.

R139 512 MHz felt slower scrolls seemed to stutter more. This is subjective of course I could not find any significant differences in benchmark scores.
[Samsung Galaxy Nexus] raubkatze:
On my mind r139 is not worse. And for example NenaMark2 and CF-Bench agreed with me -)
[Samsung Galaxy Nexus] Moz007:
I don't know if it's linked with the kernel but i have an issue when i launch gta3...
[Samsung Galaxy Nexus] raubkatze:
What build and with which GPU OC (if it's nightly) do you use?