yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ChosSimbaOne:
Sorry if this is a stupid question, but i just rooted my GNex, and can't seem to find any install info in OP. is the Zip flashable or should it be installed via fastboot? Thanks :-)
[Samsung Galaxy Nexus] ro_explorer:
It is flashable through CWM. You need to put first CWM using fastboot (read the tutorials).
[Samsung Galaxy Nexus] ChosSimbaOne:
Great :-) I'm assuming it is the same procedure as for HTC Hero, first flash rom, then flash kernel, and of course wipe data/factory before each?

Another question when flashing new radio, should i do that before ROM flash or after or in same flash sequnce? Is the newest Radio for Europe GSM hero XXKL1?

Thanks :-)
[Samsung Galaxy Nexus] yyz71:
12 is so much better that's why I never updated yet.
[Samsung Galaxy Nexus] :
Hi,

I am currently testing the nightly #13,no issues :)

For me,like someone else said above,transitions/animations are more smooth than previous nightlies (very noticiable in Home/App drawer/Home).

Seems the gpu overclock do nothing,with nightly #12,without gpu overclock,my benchs were the same as before nightlies with gpu overclock+a little lag in Home/App drawer/Home,but with the last nightly (always without gpu overclock),transitions/animations are more smoother (more speed).

And no lag in lockscreen!

You improve something,but what... :D?

Perhaps it's a little short but I did not notice a bad battery drain,deep sleep is ok for me,running AOKP build 19.

Antutu benchmark give me always about 7040-7080,but the smoother UI is very noticiable ;)

Thanks! :)
[Samsung Galaxy Nexus] ro_explorer:
To ensure you have on your phone what you want, the correct flash order is: rom - gapps - radio - kernel - wipe dalvik - wipe cache

Wiping /data (factory reset) is only required is you move from one rom to another and the developer is asking explicitly for this and in this case, this should be the first flash step.
[Samsung Galaxy Nexus] :
Re,

Further to my previous post,

Expect the smoother UI (in any case for me than the previous nightlies),here two benchs:

The improvement is really noticeable especially in UI :)

PS:yes i like benchs :D,battery drain is good for me so I test the perfs :D

A little beer for your (always) hard work: 7L727307AF3131430 :cool: ;):)
[Samsung Galaxy Nexus] ChosSimbaOne:
Thanks for the help. Have Flashed AOKP Milestone 2 - XXKL1 radio and Franco.kernel#13 now. It is booting, looking forward to check it out :-) Thanks for the help :-)
[Samsung Galaxy Nexus] apratomo:
Worse than #12, vbus_tuna_otg gave big wake lock
[Samsung Galaxy Nexus] Elganja:
checkout StabilityTest in the market. It will allow you to do a "Scaling Stability Test" that will test all different clock speeds (it alternates among them evenly)

I find that 1125, 975, 875 (1200,920,700) work very nicely with no ill effects.. i.e. no lag, crashes, etc...
[Samsung Galaxy Nexus] ellesshoo:
Lulz, so you haven't even updated and tried #13 but you're proclaiming #12 is "so much better". It's this kind of unsound logic, rumor, and anecdotal experiences that too many people post that obscures the reality and makes it even harder for a dev to get to the bottom of true issues.

I'm not saying 13 is definitively better and bug free vs 12. But I'm at least running it through its paces, on a very stock-like and common rom. My initial impression is very positive. It can't be asked of users to test kernels while strictly conforming to the tenants of scientific method but not even flashing a build and reporting how it compares to the previous is ridiculous.

I'm not saying the following to you, it's more of an observation/rant about xda in general:

I'd be willing to bet that if I and someone else who has posted that #13 was great had been the first 2 posts after Franco's release posting that the majority of the following posts would be positive about 13. It's just the way this place works.

There was a Nexus S kernel dev that got so sick of this kind of obscuring of reality and users being completely incapable of properly testing that once he reached a build that had been deemed rock solid stable by the masses he re-released it about a day later, 100% unchanged just increased the build # by +1, and as usual the response from users was "this one is so much faster!", "I'm getting FC's all the time", or "my phone randomly reboots on the new version".

If I had a dollar for every post/reply that went something like the following, I'd be Scrooge McDuck wealthy:

User: build X broke something, now x, y, and z don't work anymore.

Dev: what rom are you on?

User: Right now, SuPeR_PiMpS ICS Obscure Bling Ultra HD Beta2 but yesterday I was on Tricky_Dicks MegaSpeed eXtreme HD Orphan ROM nightly #17.

Dev:... ummm OK, any mods I should know about?

User: oh yea, forgot to mention that. I'm running a 1% battery mod I patched, a custom DPI, a theme I patched in, undervolting -100mV, overclocked to 1.35ghz, random_dude's free ram scripts, and I'm using the latest Korean radio that apparently was leaked to another user.

Dev: ... <crickets> ...

Bless your patience Franco.
[Samsung Galaxy Nexus] franciscofranco:
You know what is vbus_tuna_otg? It's a wakelong that was held during the time you had your phone connected to your computer. It's released once you unplug it.
[Samsung Galaxy Nexus] aimetti:
battery seems to be draining faster than normal. kind of a noob at this

but are these wakelocks normal?

powermanagerservice 10.3%

gps-lock 8.4%

(havent used my gps)
[Samsung Galaxy Nexus] dwang:
People really are idiots. There I said it. Of course I don't mean any of the people here. :rolleyes:

Same crap w the screen being scratched easily threads. One or two guys report it and now everybody thinks the screen is easy to scratch. Lol
[Samsung Galaxy Nexus] The Gingerbread Man:
My tapatalk keeps unsubsribing me from this thread, is someone trying to drop me hint here? :rolleyes::p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] justibasa:
I wouldn't want to see that. We all know we're responsible for our own actions. Those that want to blame the dev need to be tied up so we can all take turns kicking them in the b*lls. Or make a separate kernal just for retards.

Don't like me........BITE ME!!!
[Samsung Galaxy Nexus] shawnaye:
AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

I WANNA DIE READING ALL THE POSTS ABOUT BENCHMARKS EVERYWHERE IN XDA!!

Can't seem to avoid them recently..

Even light browsing on Xylon and i found this comment : Flash from leankernel (stock xylon kernel) to francokernel using xylon ROM. Quadrant score passed from 2000 to 2900 without any over clocking.

WHY? Why do people think that benchmarks are so important!!
[Samsung Galaxy Nexus] peikojose:
I use paid Franco app but I don't see ROW anywhere... Where can I enable it ?
[Samsung Galaxy Nexus] shawnaye:
dude, the thing is some people don't know they're responsible for their own actions.

they complain about crap like SOD's and Heating issues when they are clearly not on stock settings.

and the thing is.. i'd bet they don't even search the thread first.

Omg i'm getting so frustrated, i'm gonna just leave xda for the night before i get another infraction.
[Samsung Galaxy Nexus] osm0sis:
Possibly but when I increase the range it definitely isn't as smooth as it is using our "magic" tunables, so we'd have to work them out again for different maxes perhaps? That's sort of why I bumped my hsf and ibf in my settings. I guess I'll wait and see if anything improves once Francisco adds ibf back in to the mix.

I know yellowdie also worked out custom tunables for the Power Modes for when f.Ku gets updated to support governor control via PM. So it'd be interesting to see if those would help too.

Right but you've still got to leave something in there for the benchers. 1.7GHz would definitely work for them while still being reasonably stable.
[Samsung Galaxy Nexus] shawnaye:
Custom kernel settings> IO Scheduler.

make sure you're on anything above 358 if i'm not wrong.
[Samsung Galaxy Nexus] sk8oldschool74:
Cause they want to find a reason to *****....:D:D:D

sent from my AK and xylon intoxicated g nexus!!!!
[Samsung Galaxy Nexus] justibasa:
Lol. I know how you feel. Some people kids.

Don't like me........BITE ME!!!
[Samsung Galaxy Nexus] timbck2:
First question, doesn't that need to be rwxr-xr-x perms since it's a script? Second question, should everyone do this? Are there any drawbacks?
[Samsung Galaxy Nexus] osm0sis:
Isn't that only necessary for the new hw revisions of the GN with the new EMMC chip? There was an applink to the Play Store someone posted awhile back to see if you have an effected device.

Also yes, init.d scripts and dir should be rwxr-xr-x. Easiest way is to do them all at once in terminal with chmod -R 755 /system/etc/init.d

Edit: asshole/awhile. My autocorrect is dangerous since I added all the swear words to my Personal Dictionary. :laugh:
[Samsung Galaxy Nexus] timbck2:
I am assuming you aren't calling me an asshole and that was just an auto correct typo. :rolleyes: I ran "Got Brickbug" and it said it was unknown whether my chip has the problem or not. My GN is not a newer one, I got it in Feb. 2011 iirc.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
You are making me laugh tonight keep the jokes rolling :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] _chanstar_:
If you don't see IO Scheduler in Custom Kernel Settings, do this:

--Install SuperSU and provide permissions

--Download BusyBox and Smart Install binaries to system/xbin

This should also enable the option to change TCP.
[Samsung Galaxy Nexus] osm0sis:
Sorry! My Personal dictionary is all curse words, android lingo and terminal commands, and gesture typing seems to prefer suggesting them! Every time I try to write "stock" it auto-suggests "****". :p
[Samsung Galaxy Nexus] arzbhatia:
r361 is undoubtedly the best thing ever. Great work Franco! :)

(Greetings from the Xylon team)
[Samsung Galaxy Nexus] RevengeFNF:
Can we still change the voltages with your app?
[Samsung Galaxy Nexus] osm0sis:
No.

Hardcoded

.
[Samsung Galaxy Nexus] mrdevil_25:
R361 is amazing.

I had a 0% battery drain in 6 hours of idle.

as i am writing this, battery went down to 99% after 6 h 53 min of idle.

auto sync off, wifi on

running on latest AOKP official build 4.2.1
[Samsung Galaxy Nexus] peikojose:
Ok, I'm trying ROW.

BTW, are these the stock settings?

I/O = Deadline

Governor = Interactive

Thanks.
[Samsung Galaxy Nexus] shawnaye:
Uhmm, IO Scheduler is completely different from TCP, dude.

:confused::confused::confused:

Guess some people still don't understand what hardcoded means.

Hardcoded = http://dictionary.reference.com/browse/hard-coded

---------- Post added at 02:42 AM ---------- Previous post was at 02:42 AM ----------

yep.
[Samsung Galaxy Nexus] _chanstar_:
Yes.
[Samsung Galaxy Nexus] nikulogical:
What type of screen on time are you guys getting with r360/361

Sent from my Paranoid Maguro
[Samsung Galaxy Nexus] allgsmnetwork:
I'm sorry but I had to placebo effect for battery and temperature :( the battery drains quickly and the temperature is high arrive almost immediately at 30 ° / 33 ° at 1536 MHz for the rest performace and sound is ok!

Sorry again :o
[Samsung Galaxy Nexus] malaroth:
Hardcoded

That doesn't just mean it's hard to change them right? I mean... if... if I ... LOL osm0sis gotta love the personal dictionary. And Franco awesome work on this! Swapping to 361 now from test r360

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] _chanstar_:
"also". Just giving advice plus extra broskie. IO Scheduler is clearly visible if all modules were looked at within the app. If IO Scheduler was questioned, I assumed TCP would be questioned as well down the rode. Just going above and beyond. :good:
[Samsung Galaxy Nexus] shawnaye:
alright.....:rolleyes::rolleyes:
[Samsung Galaxy Nexus] F_T_B:
Please do explain why benchmarks are meaningless when comparing two versions of the same kernel. I'd really like to know that, considering it makes absolutely no sense to dismiss such a comparison based on what someone else said.

The way I see it benchmarks work as baselines for the same user and scenario, not as actual reference points between different users and scenarios.

You get x points with kernel Y version 1 and x - 100 with kernel Y version 2. Now what does that tell you -- that benchmarks are pointless?
[Samsung Galaxy Nexus] Khrushy:
Just throwing it out there, but when I'm using 1536max (which is always nowadays) I just reduced the timers to 10,000 / 30,000, but left hsf at 729 and ibf at 537 (can't test ibf ATM anyway).

I assume it's something to do with the ramp up time, but I've always found using lower boost freqs smoother. When I use 1036 hsf the initial launcher scroll delay is noticeably worse.

I'll have a bit more of a play with lowering the max freq to see if I also have the same experience you just mentioned.
[Samsung Galaxy Nexus] osm0sis:
I explained this to you before. 30 degrees Celsius is normal operating temperature.:rolleyes:

Well as far as repeating someone else's opinion goes, I certainly think that Franco's would be one people should value... Regardless, I believe the reasons are that benchmarks are arbitrary and don't reflect the real world difference. For example something as simple as turning off fsync doesn't result in that much of a difference to the feel of your device but benchmarking apps see that and immediately give you thousands of points.:eek:
[Samsung Galaxy Nexus] F_T_B:
You do have a point but let's think of something less synthetic. For instance computing the nth pi decimal is a good indicator of performance for the processor, while running a video benchmark and noticing the FPS is a good indicator of GPU performance.
[Samsung Galaxy Nexus] shawnaye:
Yes, doing that to see the performance is GOOD, and that's what a benchmark SHOULD be for.

But benchmarks become horrendously redundant when people start mentioning arbitrary numbers like 2000>2900.

An example would be the SSD in my laptop, i do a benchmark and get a different result, every single time. The numbers are never the same.

I just hate people saying oh, benchmark of this kernel is crap, is something wrong?

Oh benchmark of xyz kernel is better, why is francos so low? :confused:

IT HAS TO STOP.
[Samsung Galaxy Nexus] osm0sis:
Yes, I agree with you, those are valid tests, but we don't need a benchmarking app assigning arbitrary values to judge those. Or shouldn't. That's why benchmark comparisons have never really been welcomed in this thread; because they're random. Dance outside in the rain and your quadrant score changes, right? ;)
[Samsung Galaxy Nexus] F_T_B:
Franco's scores are never low from my experience, arguably the best kernel for those who like great benchmark scores. And it's fast in real life as well.

I do find it worthwhile to verify the validity of scores per component, meaning GPU per GPU and so on. The total is clearly not an indicative of component performance, more likely an overall estimate which is unreliable at best to know which part suffers and which one works good.

However a single test is pointless. I say do 10, eliminate the best and the worst and average the remaining eight. That's more accurate in my book.

Hey Quadrant is an appreciated benchmark although it produces rather inconsistent results for the low scale it has, which is rather curious to say the least. I keep wondering why all the "reputable" websites run it and then use it as a comparison tool, even though some are foolish enough to say "Quadrant is not yet "optimized for Android 4.x" for instance. Seems silly.
[Samsung Galaxy Nexus] malaroth:
If you look at Franco's thermal throttle setting it is set to cut the phone off at 110°C... so you have quite a way to go from 30°C before you're in danger

JBSourcery 4.1 Franco 358 FTW! Keep the Magic alive!
[Samsung Galaxy Nexus] timbck2:
No offense taken, since it was obvious what happened! :cool:
[Samsung Galaxy Nexus] osm0sis:
Yeah 110°C is the hardware safety limit where it shuts down if the throttle is disabled. I believe the throttle kicks in at 70°C.

I don't think I've ever seen my device below 26°C and that's when it was deep sleeping. Normal operating is 30°C at least, and hot off the charger it's 45°C easily. So all nice and normal. ;)

---------- Post added at 04:26 PM ---------- Previous post was at 04:07 PM ----------

Whoops, in all the confusion with my phone's pottymouth I forgot to mention that my device is from Feb/12 and is fine so I'm sure yours is good too. The date for the ones which are effected is later in 2012.

Here's the app I was thinking of: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check

I think it's the same buggy chip fw that makes the phone lag when the sdcard gets full.
[Samsung Galaxy Nexus] franciscofranco:
Hey osmosis, hows r361 for you? Milestone worthy?
[Samsung Galaxy Nexus] joaquinf:
Definitely Francisco 361 is by far the most smooth experience I've had on a phone and battery life is stellar.

First 4.2 milestone IMHO
[Samsung Galaxy Nexus] osm0sis:
Hell yeah Boss Man! Working great, up there with the epic r2xx 'reference' kernels of the past. ;) I was hoping to have input_boost_freq back and screen off min first, but hey, why not? :D
[Samsung Galaxy Nexus] franciscofranco:
Great :)
[Samsung Galaxy Nexus] yellowdie:
Totally agree with all three points. :) :D
[Samsung Galaxy Nexus] The Gingerbread Man:
I'll beat you today my friend ;) (no homo lol):p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I think you missed the 1d in his. :laugh:
[Samsung Galaxy Nexus] The Gingerbread Man:
Hmm, I dunno which would end up best, iv been at work 9 hours shift, now I'm home I'll be on my phone more and already dropped 10% since my screen shot due to music (streaming Google play). My screen on time will be 3+ hours though over 12+ hour off charger when I sleep. He will have better stand by time than me though and I charge my phone every night as I need it for work.

Note to Franco

Is there any chance of a revert back to the ezekeel music headphone boost? That way it could be turned off for those who didn't want it and for those who do we can choose the level of boost. I know you gave it your best shot but I feel the ezekeel method worked better overall and I'm more than happy to switch to loud and back for some calls to be heard.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
You definitely have a great batt life there. Things with 361 has been great both battery and performance wise. I find myself using my gnex much less since I have my Nexus 7 (in which I can easily get 7 hours of screen on time with latest Franco kernel :p) that's why my screen on time wasn't that high, however, I feel that this latest release is a step forward on the right direction. My gnex can easily beat my n7 in ui smoothness anytime.

I want to thanks Francisco, osmosis, yellowdie and all who have contributed to this thread.

Keep up the good work guys. Thanks

Edit: pics or didn't happened?
[Samsung Galaxy Nexus] calinoii:
You guys seem to be so happy with the new kernel,why the hell do I need to experience that stuttering from time to time:( It makes my nexus feel awfull,and it makes me too:(
[Samsung Galaxy Nexus] The Gingerbread Man:
Honestly I never knew the screen on for the n7 was so much!

And for you personally here ya go,y estimation about time of charger and even on time will be correct when my phone dies

Sent from my Galaxy Nexus

---------- Post added at 12:39 AM ---------- Previous post was at 12:19 AM ----------

Did you ever try changing from deadline to another governor? Me and osmosis helped you about as much as we could yesterday, there must of been something which helped from one of us there

Sent from my Galaxy Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ashclepdia:
The nexus 7 screen on time is amazing!

I've reached 9.5 hrs before!

Not having cellular radios goes helluva long ways Lol
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm thinking of getting one, first I need to get some descent transport sorted for my commute to work ie; something with an engine as I cycle currently and I'm hoping in April to receive a tax rebate so I might treat my self then or a nexus 4 it's hard to decide between the two :rolleyes: as an of topic question (as if I'm not of topic enough already lol) does the Franco kernel for the n7 work on the one with gsm radio too?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
I've been helping him for weeks now between his Q&A thread, PMs (which I don't usually do), and here. I've fixed his problem 5 times and then it mysteriously returns. My only guess at this point is he's doing something wrong (like not taking my advice to narrow down the rogue app) or his device is on its last legs..

Check this **** out: http://xdaforums.com/showthread.php?t=2055260
[Samsung Galaxy Nexus] smileyanz:
Thought that was coming just had to be a milestone!!!:D:thumbup:
[Samsung Galaxy Nexus] The Gingerbread Man:
Lol :rolleyes: well i guess in that case something is lost in translation or the only other thing I can think of is unless (and he should of tried this if he actually follows the thread) is by trying that app which you linked to about having a defective chip (EMMC or something). I tried and passed and memory passed :cool:

Sent from my Galaxy Nexus

---------- Post added at 01:12 AM ---------- Previous post was at 12:57 AM ----------

OK he is either ultimate troll or has hardware issues, it's hard to tell...

Sent from my Galaxy Nexus

---------- Post added at 01:19 AM ---------- Previous post was at 01:12 AM ----------

Honest serious question guys, is it only me here using tapatalk and this thread keeps unsubscribing it's self. I have had to add this thread at least 15 times today. Is a greater force dropping me a hint :confused:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] markop90:
Yes sorry, must set execution permission too, thank you for correcting me :)

Inviato dal mio iPad con Tapatalk HD
[Samsung Galaxy Nexus] osm0sis:
YES. Do it. :D We need more cool people who know how to help themselves and others over in the N7 thread. It sure does work. Haven't heard of any issues with it yet, only reports of success that it works. And r38 (the current build) is the best yet. I think we're edging closer to M1 over there. :good:
[Samsung Galaxy Nexus] joaquinf:
Yep it's happened to me too. I thought it was because of the beta version for tablets so I ended up using Tapatalk 2 again. But apparently is a general issue with Tapatalk :confused:

---------- Post added at 08:39 PM ---------- Previous post was at 08:33 PM ----------

Hahahaha you've made my night Os. Am I cool enough to offer my help over the n7 thread? :p
[Samsung Galaxy Nexus] osm0sis:
Dude, that's why I was pumped you were getting your RMA'd N7. I keep telling yellowdie to get one too, and with The Gingerbread Man we could have the whole franco.Kernel Support Team®. :D I've had enough ridiculous arguments with mouthy people in that thread about stupid **** like Flash support. :rolleyes:
[Samsung Galaxy Nexus] The Gingerbread Man:
So something to make you laugh, a guy where I work decided he wanted to root his n7 (of course at the time he didn't tell me) and what did he go and try and use? Some kind of s3 flasher, to make it better he then went and paid to get it fixed! The next day he told me about his predicament and I told him I own a galaxy nexus which of course he thought I had a nexus 4 and I told him it's the older model and said I could of fixed that for free, guess what phone he has, an iPhone 4 :rolleyes:

When money allows my transport is sorted I'll be getting one or the other, which I don't know, I might hold or for the next nexus phone on key lime pie and get the n7 when I get this money which I'm owed back which will probably be April some time

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Hahahaha that sounds like a great idea. I'll gladly help as part of the support team. Mouthy people seems to be a common thing these days huh? I've added quite a few people to my "special list" from different threads over the past month