yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
I've never had any problem with Google Play Music screen off streaming playback with r298.

Could the difference be local files vs. streaming? I don't see why that would make a difference. I don't even have WIFI_PM-Fast enabled.

My max screen off is 537 and my global min is 384, and I recommend those to everyone for both power savings without interfering with race-to-idle, and UI smoothness, respectively.

I even went ahead and undervolted 384 for a little extra savings and I'm sitting on about 0.1%/hr idle drain and 96% deep sleep overnight when I checked it this morning after 7.5 hours.
[Samsung Galaxy Nexus] Chairizkuro:
Thanks for your prompt response. I've tried both kernels 384 and 512 (also with with performance OC configurations), but the problem still remains. It's got to be something with the GPU tweaks in the kernel. Trinity 384 and 512 both work fine for this game.
[Samsung Galaxy Nexus] tetrakinitis:
+1. This game have the best graphics i've ever seen in mobile and we pay for that (6.75€). But i love franco.Kernel more than a game and i don't want to change it. I want them both! :D. Franco please do your magic and fix it! ;)
[Samsung Galaxy Nexus] slvrarrow:
Mine's local playback... The Ricky Gervais Show to be precise! Very low bitrate. Kicked mostly when browsing or opening youtube app - even before you click on a video to view, which is when music auto pauses (annoyingly)
[Samsung Galaxy Nexus] waylo:
Hi osm0sis,

Just wanted to confirm per your signature you're running the stock 4.1.2 ROM?
[Samsung Galaxy Nexus] osm0sis:
Correct sir, and I'm looking forward to the OTA this week. ;)

I went over 4hrs screen on time today for the first time too, which I'm pretty happy about. My total time on battery was only 14h but at 0.1%/hr idle drain last night I'm hoping to get in the 4hr club proper with 1d time on battery one of these days. :good:

---------- Post added at 07:23 PM ---------- Previous post was at 07:07 PM ----------

In other news, it looks like Franco merged some of the code changes for r300 to his Github already if anyone wants to take a look before he releases it:

https://github.com/franciscofranco/Tuna_JB_pre1/commits/4.1 :D
[Samsung Galaxy Nexus] The Gingerbread Man:
I bet he made more changes on that long ass flight from Europe to USA ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Astug:
Can't wait for it! Just to satisfy my pointless need to see a higher version number on my phone.
[Samsung Galaxy Nexus] WarByte:
Hello guys, been reading a lot and testing a lot through the day and I can't find info about what's going on so I am going to describe it just in case you have a solution.

Clean flash of Minco v5, setup the basic things, all works great, I can take a picture and it shows up in root explorer, I see a thumbnail and all in gallery. I flash 298 (happens with 295 as well). then I reboot, take a picture and it shows up in root explorer but no thumbnail, and it cannot be opened by anything else but the gallery. I noticed the permissions read rw------, while others read rw-rw-rw. Now if I change one of the files to rw-rw-rw manually, then the others inmediately reflect the changes, if not the condition remains.

Another curious thing is if I don't try to open any image and then I reboot, all looks fine after that, if I take pictures again, then the same thing happens. I reproduced this in AOKP and Xenon as well.

Tried clearing some apps data like storage, wiping cache, dalvik, fixing permissions. None worked so far.

Any ideas? Thanks in advance for any information.
[Samsung Galaxy Nexus] The Gingerbread Man:
I would take your phone back to 100% stock, lock and unlock your boot loader then when you get a custom recovery again go for full wipe (system, cache, data inc int SD) there is something weird going on but I don't know the exact cause but that should fix it if you start off with a completely fresh clean device

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mixtapes08:
Flash the latest bootloader.img

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] WarByte:
I'm a little reluctant about going 100% stock (laziness mostly and because it doesn't seem to be a general problem on the phone specific to flashing), but I'll try if that helps. I am also on the latest bootloader as well, tried flashing again just in case, used different recoveries, went almost all the way to stock except locking bootloader.

It strikes me as strange as it only happens when I flash franco's (and only on 4.1.x, I'd say specific to 4.1.2 since I dont recall having this problem before but I havent confirmed), all other kernels don't appear to present this. I also tried flashing another kernel once this happens and it is not reversible. Just as a note, I can to back to my nandroid backup and all works normally, it only happens when I flash this kernel and the effect appears to be inmediate whether it is a clean rom install or not. Reproduced it exactly the same way and also discarded other kernels as flashing them didn't cause this. Not saying it is the kernel fault, I agree something weird must be going on, that is why I chose minco as it has milestone 6 there already but got similar results after updating the kernel . I'll keep trying and reading just in case, not critical, but I'm curious enough as to find the real cause for this.

Thanks for the attention and ideas.
[Samsung Galaxy Nexus] osm0sis:
Sounds like ramdisk. Flash stock kernel, reboot. Flash Franco's. If that doesn't work then completely wipe is your best next step forward.
[Samsung Galaxy Nexus] hotnikkelz:
Can you post a link to stock rom please...not an img, but a zip cuz I'm noob :)
[Samsung Galaxy Nexus] osm0sis:
The real stock zips all contain images. ;)

Follow the ROM link in my sig. You've gotta learn fastboot sometime.
[Samsung Galaxy Nexus] WarByte:
I imagined something like that as well, didn't try based on the assumption that franco's had it's own ramdisk and it was replaced when flashed anyways. I'll try though. Thanks! By the way, thanks to you and yellowdie and all who participated in the famous 5 pages testing, all that knowledge came useful trying to setup other kernels as a temporary replacement :) not the same expeerience but def. helps a lot.
[Samsung Galaxy Nexus] whitedragonz83:
Osmosis/Yellow,

Have you guys been finding any improved settings for interactive governor controls vs the default r298? I know you two seem to be constantly trying to optimize, and was curious.
[Samsung Galaxy Nexus] a5pe4:
Never seen anything like that
[Samsung Galaxy Nexus] willl03:
512mhz GPU or LSD
[Samsung Galaxy Nexus] The Gingerbread Man:
This is what I'm using and seems good so far

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
The actual gov control stuff, no. We think that one's pretty awesomely nailed down at 60/65/45/15. There's a few other things up our sleeves that we're playing with that may or may not be integrated into future builds. One of the changes for r300 is going to be the input_boost_freq, hispeed_freq, and max screen off freq defaults. But you'll need to wait until r300's released to get the full inside scoop there. Boss Man's in Cali now and starting his new job, so life is gonna get busy and kernel stuff is gonna slow down a little bit for him--not stop, just slow down. So releases won't be quite as often as we're all used to. But honestly, there's not a ton more left to tweak and change. r300 is frakin' close to perfect. lol A few nights ago, I had 2% battery drain in 11 hours of idle--flippin' amazing. :) So let that whet your appetite and Franco will release it when he's ready.

:):D:laugh::good:
[Samsung Galaxy Nexus] Ridho1:
The new franco.kernel updater can not set "single core mode" in powersave mode. :(
[Samsung Galaxy Nexus] Charmacas:
Franco said he did not implement it because it doesn't give any battery improvement and it is unstable.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] asim0:
AOKP LWP?

More serious did you ever change the Developers options in settings?

Sent from teh void
[Samsung Galaxy Nexus] Charmacas:
Hey Franco,

I've got an input for you as an addition to some other comment. He said your links in the "About me" section are not clickable. You can shorten your G+ URL by going to www.gplus.to and register your desired domain. ;)

By the way: We were at Praia Grande this summer and of course also visited Lisbon. ;)

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
That's what I've settled on for governor control too! Great minds. ;) Franco and yellowdie like hispeed/input_boost freqs at 729/537, but I find those too low and laggy for average use. Seems like for best balance of performance and battery usage was 1036/729 for the governor control freqs, and then 537 for screen off max like you. Then my min-max are 384-1536, since I also found 192 too low and laggy, especially for the jittery scrolling in stock Browser.
[Samsung Galaxy Nexus] The Gingerbread Man:
I just find these values slightly better to ensure its smooth sailing all round and good for scrolling through stuff, do use the 192 slot though so I best of it all really I guess. Tip for you os you might wanna convert to chrome because as of 4.2 its replacing the old browser, plus you can links to PC or from PC back to phone :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Schneewitzchen:
Dont know if its adressed, got a force close of the app.

Start fku then go to franco.kernel updater,

immediately switch back to home of fku and open leankernel updater...then the app closes.

Can someone confirm this?
[Samsung Galaxy Nexus] Kurre:
I just tried this several times..and I want able to reproduce it. You could try clearing app data?

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] Shadow-Nexus:
So I did a little test yesterday to see how much battery could I get with 3g on all the time and I got petty good results look

View attachment 1477119View attachment 1477120

Today I will try the same settings but with WiFi on instead of data
[Samsung Galaxy Nexus] franciscofranco:
Hey guys. Already living in Mountain View and started to work today. It was a very tiring trip from Lisbon to San Francisco, but all is well. Hope everyone is doing ok over here. r300 should be hitting sometime later today after I go check the views around here, its a lovely place!
[Samsung Galaxy Nexus] joaquinf:
Great news Francisco, enjoy your trip and the best of luck in your new job
[Samsung Galaxy Nexus] Shadow-Nexus:
So you are working with Google?!?!?!
[Samsung Galaxy Nexus] morfic:
He works on clown cars.
[Samsung Galaxy Nexus] willl03:
Welcome to 'Merica
[Samsung Galaxy Nexus] Savant:
I always wondered who did that.
[Samsung Galaxy Nexus] RoscoeDpG:
Nice! welcome to Cali! because there is no place like cali its the place to be :p and CANT wait for r300! and 4.2 also not to far away man this is gonna be nice couple days lol
[Samsung Galaxy Nexus] billykxda:
Welcome to the States Francisco.

You'll love it here.

-bk
[Samsung Galaxy Nexus] franciscofranco:
I'm gonna go visit Google in some minutes, its 2 miles from where I'm staying, but no, I'm here www.cloudcar.com

Thanks for the warm welcomes everyone!
[Samsung Galaxy Nexus] bradm23:
You should release r300 while standing in front of Google.... Just saying ;)
[Samsung Galaxy Nexus] Kocai:
I'm somewhat puzzled that not a lot of people here can achieve 4hr screen on time easily considering you guys have good mobile internet connection. On good days, I can easily get 24hr with 3hr + screen on. And believe me, my definition of good days is super slow compared to what you guys have. Add the factor that my signal strength most of the time is between -75dBm to -85dBm, you guys theoretically should have better battery life than me. However I don't use Google Now at all...
[Samsung Galaxy Nexus] RoscoeDpG:
Another nice thing about u in cali is most of ur releases I will be awake for lol we r on same time zone now
[Samsung Galaxy Nexus] SpecRek9:
Haha that would have been awesone :)
[Samsung Galaxy Nexus] osm0sis:
Yeah 24h and 3h screen is my usual. I don't use Google Now either and have Latitude settings off. My phone sleeps like a baby. Franco's latest is pushing it even farther, which is great for me, but then again we don't all have an extended battery. I think I'm doing petty good with a regular. ;)

Oh no. I used to be 4 hours ahead of Franco. Now I'll have to get used to being 4 hours behind! :p
[Samsung Galaxy Nexus] Kocai:
I don't have an extended battery as well :) All I'm trying to say is you guys could have better battery life than me in a 3rd world country :)

You know you're in Indonesia when you want to show a cool app in your phone & suddenly there's no internet connection.

https://mobile.twitter.com/lifejoy/status/179248221632208896
[Samsung Galaxy Nexus] CADude:
Interesting. I can see why they would hire you. Seems that you could play a role in creating mobile computing for cars using the Linux kernel. I'm right next to you in Palo Alto. I'll be sure to wave at you if I see you in traffic on the 101. Best of luck in the startup.
[Samsung Galaxy Nexus] gaich:
Nice, imagine a car powered by Franko kernel!:laugh:
[Samsung Galaxy Nexus] thegtfusion:
Off topic:

http://www.androidpolice.com/2012/1...is-rolling-out-to-the-galaxy-nexus-right-now/

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Oh my god. I wants it. Someone needs to grab the OTA URLs ASAP!
[Samsung Galaxy Nexus] yellowdie:
Won't you be one of the first to get it being on Stock and all?
[Samsung Galaxy Nexus] osm0sis:
OTA rollouts are random, even within the ROM. takju is first but we still need someone who's "first in line" to get the URL for us, otherwise we have to wait it out for the rollout to reach us. The clear framework trick works because it gives you a new "number" which may or may not put you closer to the front of the line where the rollout is occurring. But I don't feel like ****ing up my Play account at the moment. ;)
[Samsung Galaxy Nexus] yellowdie:
That's redoncklus.
[Samsung Galaxy Nexus] SpecRek9:
Are our devices eligible to receive OTA? Since we are using a custom recovery and kernel at least
[Samsung Galaxy Nexus] osm0sis:
Not eligible to apply normally until we revert those (and radio) to stock, but we still receive and download.

Can always flash it in custom recovery, then you only need to revert the kernel and any changes/mods to system files. And of course that way you can just download the OTA zip and do it yourself rather than wait to receive it; this is how most people on stock do it. That's why efrant has a pretty awesome thread with all of the OTA URLs in it. :)
[Samsung Galaxy Nexus] yellowdie:
I still think running stock is like using Internet Explorer... :p But it's obviously just personal preference. I like Chrome or Firefox, and I like custom ROMs for their extra functions and customizability. But I will admit that Google is get much, much closer to an incredible Stock. The new 4.2 settings panel is gonna be great! :D
[Samsung Galaxy Nexus] osm0sis:
Stock's been incredible since ICS and I enjoy the simplicity and applying the fresh OTAs hot off the wire. I can get all the extra functionality I need from apps or root apps at most. :) I also think Internet Explorer is great since IE9, but that's a whole other topic. :p
[Samsung Galaxy Nexus] Hungry Man:
ROM's just provide features. It's the kernel that's going to make the big differences for battery life and performance. In my opinion find a ROM that works for you and don't worry about it until the next big Android release.
[Samsung Galaxy Nexus] SpecRek9:
For anyone running takju, If anyone finds it for yakju please share.

From user: tochiba

4.2 OTA file!!

http://android.clients.google.com/p....signed-takju-JOP40C-from-JZO54K.e587de13.zip
[Samsung Galaxy Nexus] osm0sis:
Flashing now. :D:D
[Samsung Galaxy Nexus] RoscoeDpG:
This is why i love petes bugless beast has the feel of stock but just the right tweaks to get it right
[Samsung Galaxy Nexus] Culex316:
It's safe to say that the current JB Franco Kernel will work with this new OTA, as long as it isn't a major version update, correct?

Maybe there are also some new kernel commits on the AOSP JB repository for 4.2?
[Samsung Galaxy Nexus] mixtapes08:
Seems like the ota is still 3.0 kernel...

-GNex
[Samsung Galaxy Nexus] aimcr7:
Yes, confirmed we still at 3.0.31 kernel :(
[Samsung Galaxy Nexus] chickentuna:
4.2 ota is up and r300 later. This is definitely a good day

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] gianton:
All the best in your new life/job mate!
[Samsung Galaxy Nexus] osm0sis:
Hmm Franco's patched power.tuna.so made the OTA fail its asserts, even after moving the backup his script makes to the original name.

So I think there's a little oversight in Franco's boot script for that file. It always moves it to .bak ... meaning that even when the patched one is there it's backing that up on every boot and the original file is lost. So we're going to need a file exists check added to the boot script to make sure it doesn't copy once the backup already exists. Maybe name it .fkbak to be completely clear.
[Samsung Galaxy Nexus] shawnaye:
Sigh, if only there was a new radio that came with 4.2...
[Samsung Galaxy Nexus] justme1988:
How do we use this 4.2 ota? Need to be on stock rom and then?
[Samsung Galaxy Nexus] osm0sis:
Ask and ye shall receive. It's LH1 now. ;)
[Samsung Galaxy Nexus] CADude:
There is definitely a new baseband in the OTA. Somebody just has to pull it and make a flashable zip.
[Samsung Galaxy Nexus] osm0sis:
On it. ;)

Attached them here: http://xdaforums.com/showthread.php?p=34045210#post34045210

We should probably direct all radio-related discussion to that thread from now on, too. :good:
[Samsung Galaxy Nexus] Culex316:
Do I have to disable custom recovery for the flash to succeed?
[Samsung Galaxy Nexus] osm0sis:
You should take that question to the OTA thread, sir. And no, so long as you apply it from in your custom recovery. Read efrant's very informative OP over there for all the details. :)

---------- Post added at 04:18 AM ---------- Previous post was at 03:36 AM ----------

Stuck on bootanimation with franco.Kernel doesn't seem promising. :p It's been about 5 min. I'm battery pulling and trying again.

Edit: Nope. No dice. Looks like I'm back to hideous hideous stock, and looks like r300 will have to wait a little longer. ;)

Definitely a couple things to be pulled from the new stock kernel though. Transitions are laggier than franco.Kernel (where they were buttery smooth in 4.1.2), but paging through the app drawer doesn't have any initial lag/stick getting moving, paging through widgets seems improved, and there is no hiccup scrolling down fast through the Accounts section of Settings anymore with stock. :good:

Ugh, and I just need to say, I hate the new lockscreen.. :mad:
[Samsung Galaxy Nexus] gianton:
How do you like the new stock notification toggles?
[Samsung Galaxy Nexus] osm0sis:
One extra step to get to general Settings is already annoying me, and they're not customizable. :(

j4velin's excellent Notification Toggle app definitely still has a place on my phone.

I also hate the new clock app. There is red lettering in it out of nowhere, it's not Holo at all; basically Metro, with all the emphasis on text. They're throwing the visual unity they acheived with ICS right out the ****ing window again with JB 4.1 and now even moreso with 4.2...
[Samsung Galaxy Nexus] johno168:
Its like you know what I'm thinking.
[Samsung Galaxy Nexus] chickentuna:
Ugh I miss franco kernel right now, currently running 4.2 and I'm close to going back to 4.1.2
[Samsung Galaxy Nexus] Charmacas:
What exactly do you feel? What makes the difference? Speed? Battery draining?
[Samsung Galaxy Nexus] chickentuna:
1. No usb fast charge, cannot change colors/gamma(stock colors are boring), no tweaking of governors and voltage. Basically those you would want to do on a custom kernel.

2. The smoothness. Although stock kernel was smooth there were some lags while scrolling especially on Settings, you would definitely notice the difference between stock and franco's kernel. On franco it's just smooth nothing else.

On battery, i cannot comment on that just yet. It's still plugged in and I was rebooting the device a couple of times earlier when I installed 4.2. So battery readings is not really accurate right now.

I personally think 4.2 is good even better once it's compatible with franco kernel

P.S. I was excited about the toggles. Turns out that it's just shortcut to settings. Like when you tap wi-fi instead of turning it ON it will take you directly to WiFi settings and you need to enable it there which is retarded if you ask me. WTF is google thinking?
[Samsung Galaxy Nexus] danielvc:
the colours are: blehhhh.
[Samsung Galaxy Nexus] fuske:
Same reaction for me! Went back to 4.1.2. I'll just wait for cm10 with franco's kernel on 4.2
[Samsung Galaxy Nexus] Charmacas:
What are your colour setting recommendations? Is there a thread on xda where the optimal colour setting is being discussed? :)
[Samsung Galaxy Nexus] Bl4ck3urn:
have a look at http://xdaforums.com/showthread.php?t=1790325
[Samsung Galaxy Nexus] tetrakinitis:
Check here https://docs.google.com/spreadsheet/lv?key=0AmUsanWh1BpZdENqZ0FPQmRnUEs3SHBON1VsU3BmN0E. I'm using arzbhatia presets. Search in the doc. The best so far!
[Samsung Galaxy Nexus] ciprianruse88:
Off topic...

I think I'm gonna be sick...In my country (fuc.ing Romania) the Nexus 4 is in pre-order with the price of 520 euros:( .I don't understand why google isn't expanding the play store in all the countries.Someone should start shipping nexus 4 from countries where they can buy it from google play store to us where the stores are ripping us off with their enormous prices
[Samsung Galaxy Nexus] gianton:
LG should loose their partnership with Google, €599,00 EUR in Greek stores is simply a rip off!

Sorry for the off topic.

---------- Post added at 03:47 PM ---------- Previous post was at 03:44 PM ----------

I'm not sure if it's safe for our screen to run settings above 200 for the long run.
[Samsung Galaxy Nexus] Charmacas:
Could you please explain this? :)
[Samsung Galaxy Nexus] fuske:
Did also read about the above 200 burn in..

but i tried the settings.. and wow! Great!

And in the topic mention earlier about the optimal color settings, no one has experienced burn in.. yet
[Samsung Galaxy Nexus] gianton:
Anything above 200-220+ for Red, Green, Blue is going to get the screen burn in and do some damage.

This is what I've been informed and read, several times.
[Samsung Galaxy Nexus] :
Nightly 298 is not working on Android 4.2. The device never leaves the screen with the "X"
[Samsung Galaxy Nexus] chickentuna:
yes it doesn't work. osmosis has posted a few pages back. Use stock no custom kernels working yet
[Samsung Galaxy Nexus] mpokwsths:
Corrected. Also, everything is proportional and everything is a matter of usage. One could say that Google's 200/200/200 is too much and we should decrease it. Also another person with 400/400/400 that uses the phone with autobrightness mainly indoors (so that the screen rarely goes bright) will get burn-in much later than someone else with 150/150/150 that uses the phone (with autobrightness) mainly outdoors with sunlight or at full brightness. Everything depends on the use of the phone...
[Samsung Galaxy Nexus] gianton:
Makes sence, but better be safe than sorry. Specially if you're going to keep the device for a couple of years.
[Samsung Galaxy Nexus] Culex316:
Man, not being able to use franco's kernel with the new 4.2 Jelly Bean is a bummer..I will downgrade just because of that..I love his kernel more than any new ROM updates lol.
[Samsung Galaxy Nexus] SpecRek9:
I just saw r300 512GPU out :)
[Samsung Galaxy Nexus] fuske:
and 384GPU ! Running it already :)
[Samsung Galaxy Nexus] c0mrade2:
I'm using 135-135-205, all RGB gamma to 0, -5 Trinity Contrast and 1.4 OMAP gamma and it's just perfect.
[Samsung Galaxy Nexus] franciscofranco:
r300 is out, have fun.
[Samsung Galaxy Nexus] ajm786:
Thanks franco!

Did you have any chance to look into the audio issue that I reported last week?