yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sway40:
Give him some time dude, cm10 is still brand new.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Here's a post from a new guy who put it in Q&A since he hasn't reached the minimum post # for the Dev forum yet. I thought it was helpful and a nice read so I'm reposting it here for everyone's benefit.

If only all our new users would take the initiative and become so well read! :laugh:
[Samsung Galaxy Nexus] fronc:
What do 5-10 correspond to? (5 = 1.0, 6 = 1.2, 7 = 1.4... ?). Can we enter non integers? I was hoping to try out 1.1 if possible. Can I do 5.5?
[Samsung Galaxy Nexus] agaruba:
Getting some wakelocks from audio out and power manager service. Anyone else experiencing this? Franco runs impressively until this happens, then it's battery buffet for my phone.
[Samsung Galaxy Nexus] ceejay83:
do you use pgm? think power manager service is related to it
[Samsung Galaxy Nexus] despard:
I think you were listening to music??
[Samsung Galaxy Nexus] joshndroid:
Running at 729Mhz feels as smooth as 1.4 yewww
[Samsung Galaxy Nexus] splus:
If anyone's interested in governors and governor control parameters there are really good few posts by droidphile at http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] splus:
When I got my GNex I was happy it would charge from empty to full in just one hour on ICS 4.0.1.

I'm noticing now it takes full two and half hours to charge it with the same wall charger.

I'm on stock bigxie JB ROM with Franco r220 BTW.

Is this normal or is there something wrong with ROM/kernel charging or with my charger/battery?
[Samsung Galaxy Nexus] sway40:
I would say charger, maybe battery but I doubt it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] LNJ:
Maybe charging mah is set lower in the kernel.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] provolinoo:
tested Franco Kernel 220 on CM10, it doesn't go over the animation screen... bootloop :(
[Samsung Galaxy Nexus] KemikalElite:
Check Settings > About phone > Status and make sure battery status is AC and not USB. I know that with certain kernels and cheaper low end chargers the system can falsely detect the charger as a usb port instead of a wall outlet. If this is the case, try enabling the usb fast charge option if possible.

It could also be the amps on the charger. Apparently amp ratings affect charging speed. Because my kindle fire tablet has a larger battery (tablets have about double mAh in the battery) it has a slightly higher amp rating than my samsung phone chargers. One time I tried charging the tablet with my samsung charger and it took like four hours. I switched back to the stock tablet charger and it was at normal speed again.

So in that case: Tablet charger + Phone = Super fast charge method

Thanks for the warning. I was just about to flash this before the page reloaded.
[Samsung Galaxy Nexus] sam razzy:
No guys... every new guys who bought their nexus gets confused even seeing the thread title.. They doesn't know which is a new version ... after seeing the thread title date 5th June .. I tot first tat was the old version ... after reading the op I got into clear conclution... so guys.. whenever a new guy ask abt which version.. tell him first to read the op properly... even tell him which is the new version.. bcoz every new member without much knowledge will learn something from u... ;) EVERY XDA GUY WAS A NOOB wn they joined from beginning...: P so help him... ;)

This is not offensive... I jus want to help all d guys... but not trollers...

sent from jElly Belly NeXus PrimE
[Samsung Galaxy Nexus] LNJ:
In the SGS2 forums, whenever an update is out, the thread is edited with the date of the new release. That way you know there's something new released.

Some threads here are done that way but not all.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] bat0nas:
Hi,

Just updated to JB.

Is this r220 any good already? Flash it or still wait till something stable?

I know I know I must read the all thousand thread posts, but common.... :(
[Samsung Galaxy Nexus] sam razzy:
Yea ... as I know.. its a milestone 4 or stable release date ... so may b Franco doesn't change name for experimental build.... correct me if m wrong

sent from jElly Belly NeXus PrimE
[Samsung Galaxy Nexus] Ringo.C:
Will there be a JB kernel for ICS with 512mHz GPU :confused:
[Samsung Galaxy Nexus] morfic:
That would eat up too much time, franco updates on milestones, other than that you know he releases new kernels all the time.
[Samsung Galaxy Nexus] dimmanramone:
If I remember well from reading the thread daily, there is not going to be a new release for ICS at all.

Maybe is time to install JB ;)
[Samsung Galaxy Nexus] Ringo.C:
Yeah, I'm just waiting for AOKP JB release
[Samsung Galaxy Nexus] dimmanramone:
Ok, there are always other ROMs that you can try before AOKP JB release ;)
[Samsung Galaxy Nexus] MattSkeet:
Does volume boos work on jb r220 ? I don't see(hear) any difference ....
[Samsung Galaxy Nexus] BrUhNiGGs:
Damn the past two releases for JB is causing my phone to have random reboots every 2 minutes if I clock it up to 1.4ghz and up...my phone can usually go up to 1.5 or 1.6 but now it can't on JB.
[Samsung Galaxy Nexus] bongostl:
Does Franco know that his kernel won't boot on cm10?

Trinity and ek both boot find
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't think he does, your only the 3rd person to report it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] provolinoo:
LOL :D
[Samsung Galaxy Nexus] daggerxXxsin:
I experienced the same thing. But these are just alpha builds of cm10 so it might not be the kernel's fault.
[Samsung Galaxy Nexus] zyonee:
Just guessing here, but seeing as this kernel has its own ramdisk (uses boot.img), it overwrites whatever ramdisk is included from CM10, which could possibly break things if CM10 deviates too much from stock JB. Many other kernels use Koush's anykernel updater, meaning it flashes the kernel and uses the existing ramdisk.

Iirc, franco's view is that people might start blaming the kernel for things that the ramdisk breaks, thus he includes his own ramdisk that has been tested with this kernel. My guess is that this kernel might work if you use the kernel but not the ramdisk from it. How to do so is slightly beyond my abilities.

Just my two cents. :)
[Samsung Galaxy Nexus] sg1969:
just reading the 4-5 last pages would be enough.... if only it wasn't full of posts by people asking the same **** over and over.....

yes, 220 works very well, been running for 2 days without any problems and it's very smooth
[Samsung Galaxy Nexus] andrew53517:
My phone isn't deep sleeping on the lasted JB kernel on EOS ROM. I reflashed the kernel too.

Edit: weird, now it is two hours later...
[Samsung Galaxy Nexus] andrew53517:
Delete
[Samsung Galaxy Nexus] TEK112:
Open up maps let it get a lock on you. Close it and swipe it away under running apps. Turn off screen for 30 seconds and when it wakes you should see deep sleep. You should only have to do it once, but you may need to do it each boot. Just keep an eye on it using cpuspy.
[Samsung Galaxy Nexus] Edwrib:
PowerManager is because you was charging.

Audio is the touch sounds.
[Samsung Galaxy Nexus] sitaramp:
I had a SOD over night on r220 jelly bean on modaco Jr 4.1.1 ROM.

Here is the last_kmsg if it helps:

http://pastebin.com/RmJDg61Y
[Samsung Galaxy Nexus] bat0nas:
Hi,

So is current r220 release better than JB stock kernel or not?
[Samsung Galaxy Nexus] mikeandjaimie:
Only applies to headphone jack, and not speaker, and and yes I notice the difference but not as much as ics it seems
[Samsung Galaxy Nexus] timbck2:
220 has been completely stable for me... As far as I'm concerned it's like a milestone release.
[Samsung Galaxy Nexus] mikeandjaimie:
Iirc quite a few devs said they WOULD NOT support CM stuff anymore cause they were ****ing with **** that broke stuff for everyone else BUT their ROM. Not to mention it's in a super early pre-alpha state! IMHO franco is doing a great job and it's not his fault they decided to screw with **** nor should he have to rewrite anything to cater to a single rom that goes against the rest of the community generated roms... I used to be a diehard cm fan, but not lately with some choices they made
[Samsung Galaxy Nexus] bigeyes0x0:
Can we stop the CM hate? Did any of you recently newborn CM haters read the entire thread and see its actual conclusion and how CM team propose a fix for incident like what happened in the future. Personally I was on the side of condemning them, but being reasonable and knowing when to get over it is important, too.

About franco kernel does not work with CM10, it's technically wrong, because it's the ramdisk that does not work with CM10, not the kernel (zImage) itself. Just use unpackbootimg to unpack franco boot.img and create a new boot.img from franco's zImage with cm10 ramdisk. It should work.
[Samsung Galaxy Nexus] 15israellai:
Franco...I can't help complimenting you. Last time when I tried 1.8GHz (I think it was 210) my phone "died" pretty awfully. But now I'm running this frequency quite stably, no reboots yet. Awesome!

Blazing on my Nexus Prime

Edit: Got the first reboot almost immediately after this post :P Good luck!
[Samsung Galaxy Nexus] MS.:
1.8GHz for daily use? You either don't understand the risks or you just hate your phone more than anything else on earth.
[Samsung Galaxy Nexus] dyndragon:
See. This is useful. Thanks, I didn't know what was happening and if I was doing something wrong. I was just looking for verification that I wasn't doing anything wrong.
[Samsung Galaxy Nexus] BigBake88:
If the phone can be kept relatively cool, is it still really bad for daily use?
[Samsung Galaxy Nexus] TEK112:
Odds are that you will never own the phone long enough to see the damage. However, while not immediately damaging, it is not good to run that close to the max.
[Samsung Galaxy Nexus] franciscofranco:
Even if I'm not a CM supporter I'm gonna try and make the ramdisk compatible with their rom. I think its wrong to force users choose roms because I don't personally support CyanogenMod. I won't provide troubleshooting or support if something breaks, but I'll make it compatible.
[Samsung Galaxy Nexus] kmakiki:
Thanks Franco! Even though I am moreso looking forward to the AOKP release...
[Samsung Galaxy Nexus] Marcb:
I don't understand why people overclock to such high frequencies... you guys have performance problems?

Even stock my phone runs smoothly... why overclock like that?
[Samsung Galaxy Nexus] franciscofranco:
For e-peen + internet points.
[Samsung Galaxy Nexus] Marcb:
I think so too...

It's totally useless to do that...
[Samsung Galaxy Nexus] dwang:
for games...

overclocking the cpu and gpu will increase performance for 3d games such as nova 3 and modern combat.
[Samsung Galaxy Nexus] TEK112:
This all the way... Just like screenies of benchmarks.
[Samsung Galaxy Nexus] dyndragon:
You da man Franco.

Thanks very much. I look forward to your next build (hopefully?) so I can go back to the Franco goodness again.
[Samsung Galaxy Nexus] Marcb:
I really don't think so...

There's not a single game that doesn't run well on stock frequencies or 384mhz GPU and maybe 1200-1500MHz CPU...

And Jelly Bean optimized gaming a lot...
[Samsung Galaxy Nexus] dwang:
modern combat 3 runs better with oc gpu and cpu. 512 gpu oc gives an 8 fps increase in performance via nenamarks, that directly translates to better performance with modern combat 3.

nova 3 currently doesn't run on jb, but once that is fixed, i'm sure we'll see similar performance improvements.
[Samsung Galaxy Nexus] MS.:
1. If thermal throttling is enabled then most likely you'll be able to keep it at reasonable temps, but... In CPU intensive apps thermal throttling usually kicks in even without any overclock and with 1,8GHz (and +0.2V) it will reduce CPU speed in no time.

Then here's my question: what's the point to overclock CPU if it will automatically downclock itself once CPU intensive app is launched? I'm not talking about 1-2min. length benchies, i mean real gaming or watching full length HD movies.

2. If thermal throttling is disabled, you will see some gain in performance, but then phone will shut down once it reaches +110C (feel free to correct me here). Is +110C ok for your phone? Definitely no.
[Samsung Galaxy Nexus] blackout23:
I flashed r220 on my 4.1.1 yakju 5 hours ago. Everything looks good so far.

It propelled my stock e-peenes from around 2300 (GNex is listed at 2571 in ResultsBrowser) to 3000 without

any overclocking. Quadrant Score that is. Basically only major improvement was the I/O score which almost doubled.

Device feels even more responsive now I have to say. Won't even bother with undervolting and overclocking as long

as battery is just as good as with stock kernel.

Only thing I might try out is other scaling governors. Are there any resources on how they all work based on what logic?

I'm familiar with ondemand and performance from using linux but can't quite figure out where the difference between

interactive and ondemand is (sounds like they do pretty much the same judging from the name).
[Samsung Galaxy Nexus] laureanop:
Oozing class as usual

"the relentless pursuit of the perfect rom "
[Samsung Galaxy Nexus] muhsli:
someone posted this before.. good read!

http://xdaforums.com/showthread.php?t=1369817
[Samsung Galaxy Nexus] BigBake88:
Need a little help here fellas. I am having a ton of kernel wakelocks, and I do not understand. Never had these before to this extent. Checked to see if anything was running in the background and didn't find anything. BBS said I have 12 min screen time, but phone was awake over 2 hrs and I was down to 87%. Any ideas or suggestions? Anyone else experiencing this? BTW, I am running Beta 3 Rootzboat 4.1.1. Thanks!
[Samsung Galaxy Nexus] TEK112:
What is the percentage of time without signal? Settings - battery - cell standby
[Samsung Galaxy Nexus] BigBake88:
Hey thank you for the response. It is virtually nothing 1%...I also had an 11 minute wake lock for the NFC and I do not even have that turned on haha. I'm confused why I have so many 'USB" wakelocks...
[Samsung Galaxy Nexus] TEK112:
Those numbers may be normal. What is the total runtime of your phone?

For instance, I have been going for 8hrs and my wakelocks are:

1hr 47 min modem usb gpio

1hr 39 wlan

1hr 16min modem usb suspend

54s of nfc

Download cpuspy from the market and see what your deep sleep looks like.
[Samsung Galaxy Nexus] stark_br:
Franco, can u give me an explanation?

I dont know if its been discussed before, but here it goes.

The Gnex and S2 have the same CPU (cortex A9). Why the frequencies on S2 start on 200mhz and gnex on 384mhz? I mean, it would be nice if we could set min freq on 200mhz, doesnt it? Because gnex has these "weird" freq table....

Tks boss :thumbup:

PS: I've searched but found nothing.
[Samsung Galaxy Nexus] TEK112:
Same architecture, different model. The SII is a OMAP 4430, while the GNex is a 4460. Two different processors with the same GPU, although the SII GPU natively runs at 300MHz-ish while the GNex runs at 384MHz.

You have to look at voltages. If the 200MHz step requires 1025mV to run and the 384MHz step can run at 1025mV, it would make sense to go with the higher frequency since the amount of power required is the same.
[Samsung Galaxy Nexus] BigBake88:
Yikes that seems very high! I guess I am not the only one having an issue with the kernel wakelocks! Can some other people comment on what their kernel wakelocks are? Maybe this is something Franco should look into if/when he gets a chance. That runtime with the screenshot was around 4 hrs. Deep sleep is working, but does not seem anywhere near as good as Francos kernels usually are.
[Samsung Galaxy Nexus] TEK112:
It's all relative. What I do know is that I am at 50% battery with 1hr on screen time. For me this is good usage. I started stock with 1.5hrs of on screen time and rooted with many more bells and whistles on JB, I am getting over 2hrs consistently.

The numbers looking large is probably because I constantly flip my phone on and off every couple of minutes. I work in a radiology department and the walls in many areas are lined to block radiation, in turn blocking cell service. Therefore, I am constantly check to make sure I didn't miss anything. Those wakelocks are my own fault.
[Samsung Galaxy Nexus] stark_br:
Tks.

Sure, with same amout of energy, of course we should use the higher freq.

As it said, if we could run below 384, it would require less power...righ? Is this possible to be implemented as S2 also can run @ 100mhz?
[Samsung Galaxy Nexus] mariachi202:
Even though you turn off NFC, there's still a process running in the background. Try freezing it.

Right on the spot. I only have a grudge against your claim that the GNex and S2 have the same gpu.
[Samsung Galaxy Nexus] TEK112:
They both have the PowerVR SGX540.

edit: Depends on which version you have. Refer here for more details:

http://en.wikipedia.org/wiki/Samsung_Galaxy_S_II#Processor

CPU

1.2 GHz dual-core ARM Cortex-A9 (GT-I9100 & GT-I9100G)

1.5 GHz dual-core Qualcomm Scorpion (GT-I9210)

GPU

ARM Mali-400 MP (GT-I9100)

PowerVR SGX540 (GT-I9100G)

Qualcomm Adreno 220 (GT-I9210)
[Samsung Galaxy Nexus] BigBake88:
I believe the S2 has a Mali-400, but more powerful than the Gnex GPU.
[Samsung Galaxy Nexus] mariachi202:
Check your sources, the S2 has a more capable Mali GPU.

The GNex has the GPU as the original Galaxy S i9000, which is the PowerVR.
[Samsung Galaxy Nexus] TEK112:
You both missed my edits.

It depends on which SII you have.
[Samsung Galaxy Nexus] BigBake88:
Thanks! How do I freeze it? I just went into settings and "Force stopped" the NFC service. Can you list some of your Kernel Wakelocks you have today and the amount of time it has spent? It would be much appreciated.
[Samsung Galaxy Nexus] brenopapito:
Noob Question

Custom kernels can prevent new OTA updates?
[Samsung Galaxy Nexus] TEK112:
Not that I know of, but I could be wrong. However, the OTA will probably wipe out your custom kernel and may unroot the phone.
[Samsung Galaxy Nexus] brenopapito:
Ok !

Let's flash!

:D
[Samsung Galaxy Nexus] six_dfx:
It's not the same amount actually, power consumption grows linearly with frequency if the voltage is unchanged, so in your case 200MHz would still consume nearly half of 384.
[Samsung Galaxy Nexus] The Gingerbread Man:
It will download but not flash. To ota you need a 100% stock rom and matching compentents for the build (radio, boot loader, recovery). Making a nandroid of stock ROM is always a good idea but you can always grab factory images from google and flash that

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] brenopapito:
Nice to know, tks for the info!
[Samsung Galaxy Nexus] mariachi202:
You can use Rom Toolbox or Titanium Backup to freeze apps and services.
[Samsung Galaxy Nexus] TEK112:
That is a static power equation you are thinking about. It does not include sleep and race to idle power and many other variables involving long term power that are almost incalculable. It is more efficient to go with the higher clock when possible when voltage stays the same.

edit: I am not talking about true energy equations. I am talking power consumption with a focus on linux based kernels.
[Samsung Galaxy Nexus] agaruba:
No idea what pgm is

And earlier in the day but for a very short time so makes me wonder about the huge audio out use
[Samsung Galaxy Nexus] franciscofranco:
PGM is an app for slide2wake. You can find it in the market.

Those audio out seem to be caused by the sounds when you touch something on the screen.
[Samsung Galaxy Nexus] BigBake88:
@Franco do you have any unusual kernel wake locks for extended periods of time?
[Samsung Galaxy Nexus] Lambetts:
Hey guys.

I'm hearing some people using the latest JB kernel with ICS 4.0.4...and getting great results. Is this possible??

Thanks guys. Just thought JB is for JB and ICS is for ICS .....sort of makes sense. Haha.
[Samsung Galaxy Nexus] Flukester69:
I've been using it since it was released. I have zero problems with it. I run it with BlackICE.
[Samsung Galaxy Nexus] Antob125:
R200 is jb kernel for ics

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Lambetts:
Oh ok. Thanks man.

What I'm really asking is I tried m4 on aokp m6 and the USB mounting feature isn't supported in m4. It crashes settings / storage indefinitely. Anyone had any luck with any other Franco build with that?

Thanks guys.
[Samsung Galaxy Nexus] franciscofranco:
Thats because CM decided once more to introduce some strange **** in the ramdisk and Milestone 4 doesn't have that change yet. Flash r196.
[Samsung Galaxy Nexus] osm0sis:
Actually some of those aren't quite correct apparently... here's another good post from our lurker over in Q&A ;):

Proper explanations of hispeed_freq and input_boost are in nemo's previous post.
[Samsung Galaxy Nexus] Lambetts:
Gotcha. Thanks Franco.

I just flashed r200. Everything seems to work now. :)

I thought that's what it was.

Only thing is screen off freq wont go lower than min freq. No biggy really. Probably part of the JB kernel I'm guessing.

Thanks man.
[Samsung Galaxy Nexus] franciscofranco:
Err.. of course it won't go lower than min freq... that seems... kinda... obvious :p
[Samsung Galaxy Nexus] derPianist:
But not for me....

Example:

You are rockin' Franco's awesome kernel with MINIMUM 729 MHz & MAXIMUM 1228 MHz

But now you want that your phone only runs till MAXIMUM 384 MHz with Screen Off.

Those values should be independent, I think.

That is for me... kinda... obvious :p

via Google Galaxy Nexus
[Samsung Galaxy Nexus] TheInVisibleGoD:
You should want that your phone reach deepsleep kicker... so choosing a screen off frequency lower than your min freq is not very obvious or even clever to do so... no offense!

Just my 2 cents... ;)
[Samsung Galaxy Nexus] foxehkins:
With under volting do you guys notice a performance decrease at all? I've never delved into it but I've been thinking about learning more depending on the pros and cons.
[Samsung Galaxy Nexus] thuynh022:
Anyone have issues with Pandora playback on headphones? Mine repeatedly stops playing while using headphones.

Edit: I noticed when I plug in my headphones and the Google now pops up playback is fine. But, if it doesn't pop up, Pandora keeps thinking I unplugged my headphones.
[Samsung Galaxy Nexus] d1pham:
I'm running AOKP Build 12 + Franco Nightly 9.0. Default governor. No overclock. Did not toggle CPU1 off during screen down feature. I have not experienced the SOD. With the minimum set to 350 or 750 no SOD. Kernel seems to be running just fine.
[Samsung Galaxy Nexus] aron7awol:
I've never had any lag waking up the device previously, always running interactive governor. I am definitely noticing a much longer period of time for the lockscreen to appear on #9, so one of the changes created this lag. I'll test 9.1 now...

Update: The lag is definitely there in #9.1 too. I just flashed back to #8 to double check and it is very noticeably faster. To me, #8 and interactive is the perfect combo. Wakes instantly, no lag whatsoever anywhere, and fantastic battery life.
[Samsung Galaxy Nexus] sirj00:
Franco on this latest build. what is the minimum set at. 350 or 700 by default.

By the way, I have not experienced one single hiccup with any of your kernels.

Fantastic.

Updating my kernel my phone crashed and I lost all my data on the phone.

I purchased your kernel updater last wk but now I can't find it again on the market to install.

Thanks Franco
[Samsung Galaxy Nexus] drawde40599:
SoD

SoD I notice only happens to me during phone calls, while on #9, 9.1 last 3 calls went threw fine, but I did notice seems very slow to wake up when pulled away from ear, when OC 1350, 1200 seems fine conservative gov ....
[Samsung Galaxy Nexus] ro_explorer:
how do you tell there is lag when waking up?

I saw some description today that you don;t see the whole ripple effect of the unlock circle. If this is the way of checking then ... I don't have that lag. I'm pushing power and there it is .. the screen is waking up and the whole ripple animation is visible. Almost instantaneous.