yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Epedemic:
I experienced a graphical glitch just now... But opposed to the last version. this one happened after i hung up on a call... Also it stopped ****ing up after the screen turned off, meaning that when i pressed power to turn on the screen again, everything was ok.. On the last kernel i had to reboot the phone before i was rid of the problem...
[Samsung Galaxy Nexus] dwang:
Running the OC version at 1.2ghz for 12 hours. No graphical glitches so far.

I'm running a stock rom and getting quadrant scores of about 2500.
[Samsung Galaxy Nexus] franciscofranco:
So anyone got graphic glitches with this one? I still don't ****ing know what can cause this and its so damn hard to figure without having the Nexus damnit.
[Samsung Galaxy Nexus] kabauterman:
yes still issues with the boot.img u posted
[Samsung Galaxy Nexus] franciscofranco:
Be more specific please. How that happens? In what environment etc... I'm still trying to figure out wtf does that.
[Samsung Galaxy Nexus] stickjohnonaah:
Just an fyi mike has a working kernel for lte now. So if you wanna check that one out it should work great
[Samsung Galaxy Nexus] DvTonder:
Have been running your original Dec 9th kernel now since release at 1.4 with no issues. Thank you.
[Samsung Galaxy Nexus] bigxie:
Still getting artifacts too. Seems mostly when waking the phone.

Like someone said earlier though, just locking the phone for a few moments and unlocking clears the artifacts, unlike before, when we needed a restart.
[Samsung Galaxy Nexus] franciscofranco:
Ok, thanks.

I followed my changes from the point that people started to get artifacts and I still can't find the culprit, it just doesn't make sense. I'll compiled another one. Can you come to G+ chat so we can test it out since you get artifacts quite regularly?
[Samsung Galaxy Nexus] rabhw:
I can confirm that the artifacts I was getting were mostly when waking the phone. Happened other times, but waking the phone triggered it most consistently.
[Samsung Galaxy Nexus] bigxie:
Thanks, I've added you to my circles.

BTW, your link in your sig changed my language to Portuguese, lol :D
[Samsung Galaxy Nexus] GchildT:
Ok...

We're gonna need people to donate to FranciscoFranco so he can get a Galaxy Nexus. We can expect him to dev for this device without having one.

C'mon Guys!
[Samsung Galaxy Nexus] Aiuspaktyn:
Same problem, with fastboot fleshed 13.1 boot.img and now all ok!
[Samsung Galaxy Nexus] jan-willem3:
I am also on bigxie's rom (V8) works fine for me. Data is the same as 13 a bit worser then 12. For the rest 0 issues and feels a bit faster
[Samsung Galaxy Nexus] slg60:
Running bigxie with 14 downloaded in 10 o'clock absolutely No Problems!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] ro_explorer:
I'm clueless then :) it will get fixed eventually.
[Samsung Galaxy Nexus] MattSkeet:
Can anyone upload 13.1 please ?
[Samsung Galaxy Nexus] Homer314:
Same here :(
[Samsung Galaxy Nexus] ljwnow:
Still, on AOKP build 20, no way to undervolt.
[Samsung Galaxy Nexus] slg60:
No data crashes Nov Stucks in Boot Logo stable ans fast For me. I have my own UV settings!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
**** happens sometimes, this was just out of my control, I couldn't predict this result. Hopefully it will be fixed really soon.
[Samsung Galaxy Nexus] Jerommeke:
After the bootloop (stuck at Google-logo) I flashed the kernel again, then the latest AOKP and GAPPS and now all is fine :)
[Samsung Galaxy Nexus] Nebucatnetzer:
To the guys with problems. Do you had anything set other than the stock settings. Profiles, uv oc?
[Samsung Galaxy Nexus] Homer314:
From franco app i set hotplug, no oc and lower uv settings + 25mv

---------- Post added at 12:05 AM ---------- Previous post was at 12:03 AM ----------

You flashed the custom rom from fastboot ? Which is the command please ?

Thanks

EDIT: from fastboot i flashed my "custom stock" kernel (bugless beast) and now the phone boot.
[Samsung Galaxy Nexus] ro_explorer:
All stock in my case, except 350 min freq.
[Samsung Galaxy Nexus] Vangelis13:
Check my previous post a couple of posts back
[Samsung Galaxy Nexus] Mrc527:
Running fine here, with #14. But when i try to load the cifs module i get:

cifs: Unknown symbol _GLOBAL_OFFSET_TABLE_ (err 0)

Anyone has the same?
[Samsung Galaxy Nexus] Nebucatnetzer:
Mine was 100%stock because I wanted to try how it performs. So it looks like it was caused totally random. Was one of you guys able to get it working with the new builds?

Btw my Wifi is behaving strange. First the signal strength was really bad suddenly lost the signal then it reconnected immediately and now I'm having two bars. I didn't move was just writing the text above.
[Samsung Galaxy Nexus] red 90:
Franco, just wanted to say keep up the good work!!! It's very much appreciated. Everyone that loads up these kernels/roms/radios etc.. knows that it's a work in progress with the potential of bugs.

I just bought the app!!! It's awesome!!!
[Samsung Galaxy Nexus] modstorm:
Running good on AOKP 20 but I cant UV as much and I noticed that I scored slightly lower in benchmarks...is it just me?
[Samsung Galaxy Nexus] Manya3084:
Using the latest kang cm9 I get constant boot loops .

I fully wiped, re-flashed, got the phone to boot, but in the middle of setting up my Google account, phone froze and restarted back into boot looping again.

Sorry Franco but something is a miss. Unless this kang cm9 is rubbish, but it plays good with all other kernels.
[Samsung Galaxy Nexus] aimetti:
Working fine on aokp as well
[Samsung Galaxy Nexus] cmoG530:
Have a link? I googled it and it's down.
[Samsung Galaxy Nexus] ToMeRv32:
I would like to get the download link too.

I'll flash it if you are sure it's better.
[Samsung Galaxy Nexus] mixtapes08:
Can anyone share the stock interactive settings of franco osmod version. I want to apply it on other kernels..

-3StarsAndaSun
[Samsung Galaxy Nexus] :
I'll send ot to you ni hangouts mate.
[Samsung Galaxy Nexus] dehosti:
My battery drains about 1% per minute on screen with 3G on. is this normal?

I am using r378.

I just charger and in 3 hours my battery is 50%.

Just using xda and g+ with 3G
[Samsung Galaxy Nexus] osm0sis:
It's the only one available now because it was the favorite from the testing: http://d-h.st/users/osm0sis/osmod

Or if that's somehow too long for you: http://v.ht/osmod ;)

Also it seems I need to clarify that it's not my kernel again. It's franco.Kernel r378, and I altered the bundled ramdisk with some settings that will hopefully make it into the next official build. Interactive is exactly the same on them both. But yes, it feels faster than "original recipe" r378, otherwise what's the point? :p

Flash my Kernel Emergency Reset Zip so you're running proper kernel defaults.

Then my only other recommended setting which isn't a default is TCP Congestion Avoidance to westwood, and to use one of the schedulers which has our finalized tunables: row or cfq.
[Samsung Galaxy Nexus] ToMeRv32:
Well, if it's better - why not? :p

I'll flash it now.

Oh its img.. Can I flash it throw my phone? I'm not near my pc now..
[Samsung Galaxy Nexus] osm0sis:
If you're running f.Ku it's insanely easy to put it in /sdcard/kernel_backups/ and flash it via the Backup/Restore function. Otherwise you can do the same with Flash Image GUI, or, rename to boot.img and place it in the official r378 zip with a good zip app.

---------- Post added at 02:03 PM ---------- Previous post was at 01:19 PM ----------

No something is very wrong there. Screen on is about 20%/h on average for most people/normal usage.
[Samsung Galaxy Nexus] tylerdurden83:
One quick silly doubt, this is only necessary if we are not doing a wipe when changing a rom, right?
[Samsung Galaxy Nexus] dehosti:
What can be the problem?

I really dont know what is happen. I made clean install of paranoid android rom, I tried lean kernel, ak kernel and now franco kernel. Always wipping correctly.

In 10 minutes my battery when the screen is on drains about 8%, and this happens only when I am using 3G.

I use whatsapp, xda, g+, a little of facebook when the screen is on.

When the screen is off the drains happens normally, maybe 1 or 2% per hour.

With 3G and data off the battery drains normally.

My settings with kernel are always interective (384MHz - 1228MHz) with row and westwood.

I dont know if can be a problem but I use some uccw widget with weather, time, battery, date.
[Samsung Galaxy Nexus] ToMeRv32:
So 3g is your problem. Maybe you don't have a reception? My battery drain is also really horrible when using 3g, but not that much..
[Samsung Galaxy Nexus] osm0sis:
Correct. If things are already starting fresh then it should be fine. Never hurts though, since there is often ROM interference in the form of init.d scripts and userinit.d scripts, so if you want to be sure you're feeling how the kernel actually performs you're better off disabling them.

Depends on your definition of "wiping correctly" - AK kernel installs a number of scripts and modules (not to mention all the add-on zips to revert the wifi drivers, etc. if you used those), so it's possible that one of them is left behind and now wreaking havoc. Flash the Kernel Emergency Reset Zip from my sig, see if that clears out whatever's causing the trouble. If not, then maybe dirty flash of your ROM again. If all else fails, wipe and clean flash your ROM.

Or hell, since it's only on 3G then your signal/reception could just be THAT bad. Maybe you need to try a different radio.
[Samsung Galaxy Nexus] dehosti:
I flashed your emergency zip but I am charging, I will test if worked when my phone complete charging.

I will try what you said,

Thank you for your time.
[Samsung Galaxy Nexus] tylerdurden83:
Thanks for the quick response. Can I ask you one last thing? Using your kernel img will I get your color profile? I can't seem to find a good one...
[Samsung Galaxy Nexus] osm0sis:
I just use Franco's default, so yes, that's what you'll get.

For a bazillion other options check the GN Collaborative Optimal Color Settings thread and G-Doc:

http://xdaforums.com/showthread.php?t=1790325

---------- Post added at 04:04 PM ---------- Previous post was at 03:51 PM ----------

Also, 1-2%/h idle drain is kinda crappy. You should look into your wakelocks with an app like BetterBatteryStats (available free for xda users, find the thread, then definitely consider getting the paid version to support chamonix; awesome dev).

Good idle drain should be 0.7%/h or less. I'm at 0.4% right now.
[Samsung Galaxy Nexus] tylerdurden83:
I checked that, none satisfied me a lot, actually some look abismall to me... Thanks anyways tho!
[Samsung Galaxy Nexus] osm0sis:
You tried all 300+ ?! :p

Some will look abysmal, since there is such variation in both panels, panel defects/tints, and personal taste. Trying ones not intended for your panel variation will look bad, usually too red or too blue/green. Someone guestimated there were 5-6 different panel types based on what we were seeing in the Collaborative Settings thread, so theoretically you should be able to find something that works for you in there if you keep looking.
[Samsung Galaxy Nexus] dehosti:
My battery is worst than I tought LOL.

I tried the batterbatterystats and nothing big was happing with my battery, I think that the problem is my 3G signal. I just saw that I use european radio in my phone and I`m from Brazil. Now I will flash a radio for my country and see if helps.
[Samsung Galaxy Nexus] osm0sis:
The XX radios are really the International/"Europa" radios, so are intended to work everywhere including the USA (they shipped it on the Play Store models, for example). That said, regional radios can work better; the UI Brazilian/"Latin America" radio UILH1 was a great radio here in Canada. Canadian/"North America" UG radios were also reported working well in Brazil, so try UGLL1 as well.

Hopefully there's another yakjuvs OTA for the GNX. I'd love to get a newer UI radio on my device again.
[Samsung Galaxy Nexus] dehosti:
I just flashed UILH1 , let`s see if works.
[Samsung Galaxy Nexus] ToMeRv32:
Hey, there is a chance that flashing another radio will really increase my battery life while using 3g??
[Samsung Galaxy Nexus] tylerdurden83:
Should do.
[Samsung Galaxy Nexus] osm0sis:
Yeah, if it somehow jives better with your cell towers/geography, then your phone doesn't have to amplify as much to establish the signal, resulting in reduced power consumption.

Edit: Okay I think we've tested out osmod long enough, and the feedback is all positive, so I wrote Francisco an email with the updated files and info on what I changed here and on grouper. :fingers-crossed:
[Samsung Galaxy Nexus] kekko986:
This latest version is so smooth..you can feel something liquid under the screen.. Like moving oil with your fingers! ?

Well done!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Edward Stanbury:
For those that are interested I have updated the settings that I use and have added screen shots of my amazing battery life :P link is in sig.
[Samsung Galaxy Nexus] Kappa Lamda:
Several BSODs the last 3 days. Rasbean 27/5 and osmod 378 fstab_sysfs_sdcard. No new apps installed, only updates!

Im using the combination rasbean/franco 378 forever and osmod version since he built it...

Dont know where these SODs come
[Samsung Galaxy Nexus] GrijzeGeest:
No problems here.

I always do a wipe cache/dalvik/system before upgrading, means you have to install gapps also, but has worked well for me.
[Samsung Galaxy Nexus] Rimher:
Might be from the ROM, since the kernel seems to have been rather stable in the past weeks. Have you tried a clean install?
[Samsung Galaxy Nexus] Kappa Lamda:
Dirty flashing for about 7-8 nightlies. No issues at all! First 5 days with 27/5 and 378 osmod absolutely no issues...

It might be the rom or an app that causing this!
[Samsung Galaxy Nexus] tylerdurden83:
Sorry for the dumb question. I flashed the reset zip, then renamed the img to boot.img, replaced with it the franco r378 img in the zip, and flashed that one too.

Now Im checking it with trickster mod.

I noticed that the tcp congestion is set on cubic rather than westwood. Maybe i misinterpreted you, but wasnt that supposed to be on westwood on your boot.img? What about the deadline scheduler, is it already set with your values on your boot.img, or do i have to edit them too? Thanks!
[Samsung Galaxy Nexus] osm0sis:
If you read what you quoted there again: "Then my only other recommended setting which isn't a default is TCP Congestion Avoidance to westwood, and to use one of the schedulers which has our finalized tunables: row or cfq."

So you see, I'm saying those aren't the defaults, so it should be no surprise that cubic pops up. That's why I'm telling you to change it to westwood. ;)

That and f.K-tuna deadline doesn't have our tweaked values hardcoded yet, so the easiest answer is just to use row or cfq until it gets added. If you really want to use deadline, then it's r_e 250 / w_e 2500 / w_s 1 / f_m 1 / f_b 8 then set on boot.
[Samsung Galaxy Nexus] dehosti:
Nice battery life.

Are you using 3G with data on all the time in this screenshots?
[Samsung Galaxy Nexus] Edward Stanbury:
thanks mate, and i used 3g for probably half of the time. and when i wasn't using 3g i disabled data and switched to 2g to save some juice and data since ive only got a 500mb data plan :( new zealand needs to catch up on the nice data deals ahha
[Samsung Galaxy Nexus] MaLiXs:
Sadly datplan are pretty expensive.. Here in canada.. The big data plan are really expensive

Send fro my Pure Franco GNex
[Samsung Galaxy Nexus] r0zj0k3r:
+1 on this issue after flashing to a default CM10.1 install
[Samsung Galaxy Nexus] osm0sis:
Played with this a few months back when I upgraded my platform tools. I think it depends on the version of adb/fastboot in use: If they're from the newest SDK, etc. then it will ask, if they're from something older then it isn't able to do the PC-side auth stuff.

If you are using the latest versions then check in %HomePath%\.android\ on your PC for the auth files (adbkey and adbkey.pub will be present). The other thing I noticed is once it's been auth'd once, it doesn't ask again. :good:
[Samsung Galaxy Nexus] r0zj0k3r:
I have latest sdk installed

I did a default fresh install of CM10.1 then instaleld latest Franco and it never prompts with the RSA key, not even initially

I guess it isn't just the RSA key feature, it also doesn't prompt for root. It just defaults to root, no 'su' command needed. You also can't deny adb root access from the su options. These are all pretty important security features that don't exist using this kernel. So if I forget to turn off adb all access to my phone is granted.

Paranoia, I know, but I do appreciate these features google/cm 10.1 have added.
[Samsung Galaxy Nexus] osm0sis:
It defaults to root once you adb shell in, yeah. That's normal and that's because if you've turned on (or left on) USB Debugging then you must be a developer. ;)

I definitely had it ask me once when I started using the latest adb with USB Debugging; pretty sure that was with franco.Kernel. Terminal Emulator doesn't default to root. Recovery is insecure of course, and starts out with root.

Anyway, could it have something to do with the default.prop item, ro.secure=0 ?

You could experiment by putting this line in an init.d script:

setprop ro.secure 1

If that works for you, then there you go... My solution is pretty easy too though, I only turn on USB Debugging when I actually need it. :)
[Samsung Galaxy Nexus] psyren:
Flashed osmod 378 kernel with Vanir's 4.2.2.1 ROM and it broke my toggle widget. Kept FCing, citing security exceptions for not having permissions to do what it's supposed to. Fixed by reverting to franco's original 378 via the updater (auto flashed latest nightly).

I've had this issue before on a different ROM. What about the kernel causes this?
[Samsung Galaxy Nexus] r0zj0k3r:
I aprreciate the response...no not a dev, a wannabe at best, but I do use adb for troubleshooting and simple tasks.

I just installed a different kernel, no other changes. Everything behaves 'normally' with regards to RSA keys and denying adb root access.

I think an easy fix for me will be to install a kernel that behaves how I like.:angel:

Franco kernels were the best I've found except for this one troubling bit!

I have ro.secure=1 I've tried messing around with that setting and a few other mentioned in this thread...no changes I can see
[Samsung Galaxy Nexus] osm0sis:
First I've heard of it. Shouldn't be anything in there I can think of that should cause that. You're going to have to give me more to troubleshoot by than that.

---------- Post added at 02:51 AM ---------- Previous post was at 02:49 AM ----------

Well we don't want to lose you over something so small. :)

default.prop is part of the ramdisk so you'd have to set ro.secure 1 on each boot. That's the only thing I can think of off the top of my head which might affect the new adb auth.

Still, it's funny that you want the kernel more secure but refuse to turn off USB Debugging when you aren't using it? That's a real security hole either way, and why it's hidden in the Developer Options in the first place. :confused:
[Samsung Galaxy Nexus] psyren:
What other info do you need?

Googling my problem, it seems I'm not alone, but it's not exactly common, either.

The FC is caused by me trying to toggle wifi on/off. The exception thrown is a security exception, and delving into the error report seems to suggest that the app/widget was trying to do something it doesn't have permission for.

This has occurred on Xylon, Xenon, Vanir, with a couple of versions of franco's kernel, with whatever widget I try (ROM toggles and directly changing it through settings has no issues). Making the widgets system apps doesn't do anything, neither does fixing permissions or uninstalling/reinstalling whatever I've been trying.

I had an unusual issue where I made a backup when I was having this issue before flashing another ROM to try. The new ROM still had the same issue (with FK), but upon restoring the backup, the issue wasn't there anymore...

I have no idea what's going on. My best guess would be that it has something to do with an insecure boot .img? I remember someone saying once that the flash process between FKU and recovery wasn't exactly the same, so perhaps something different got changed. Previously, I'd download the FK zips to my phone and flash them manually in recovery, but these days I auto-flash.
[Samsung Galaxy Nexus] tylerdurden83:
Ah i see, I thought that you meant that those weren't defaults on franco's, but they were on your modded boot.img! Sorry for the confusion (English isn't my first language, I try my best..) and thanks for the clarification and patience, you are an exemplary member!
[Samsung Galaxy Nexus] r0zj0k3r:
I do really appreciate what you guys do. I can't thank you enough.

Typically I use adb for push/pull and retrieving logs for devs!

I don't refuse to turn it off, I might forget. These are security features built into the kernel for a reason, I'm more confused that they don't exist with the Franco kernel.
[Samsung Galaxy Nexus] osm0sis:
Very weird sounding indeed. No the security of the boot img shouldn't have anything to do with that. Works fine here with the Notification Toggle app. There was never really a difference between zips and direct flashing other than Franco used to have a cleaner script in there. It isn't necessary though and shouldn't be related (also my Kernel Emergency Reset Zip covers the same sort of stuff now ;)).

My best suggestion is to clear data+cache on the widget in Apps > All downloaded apps, and if it requires root, give it fresh permissions. If that doesn't work, maybe uninstall and reinstall the widget might help.

Yeah, I'm really not sure. I recall it working but I'm not 100% sure. I'll have to delete my %HomePath%\.android\ folder and experiment with it again. Maybe tomorrow though, it's getting late here. :)

No worries, sir! If you hadn't told me I never would have guessed you weren't fluent. Your English is excellent! :good:
[Samsung Galaxy Nexus] psyren:
I think I tried all those options in the past. I've never used any toggle widgets that required root :p
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't know if you guys over here know about this but there's a new beta app in testing if you look over in the nexus 4 thread you can find details of how to join up for testing.

http://xdaforums.com/showpost.php?p=41953984&postcount=33154
[Samsung Galaxy Nexus] xFuGiToiDx:
Loving the overall smoothness with row, but it seems it drains my battery faster than deadline..
[Samsung Galaxy Nexus] lippol94:
It does. Try cfq. I fell in love with it, great battery and high performance!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] xFuGiToiDx:
I have tried already tried cfq and bfq as well but it seemed slightly laggy compared to deadline and row
[Samsung Galaxy Nexus] dratif:
Man i have to admit no one cooks a nexus kernel like francisco franco...i feel tje smoothness after flashing this kernel.r378
[Samsung Galaxy Nexus] lippol94:
Well, we all thank Franco for his hard work, but you really can't forget Franco Team.

Past few releases have been possibile thanks to them and their so much time spent on finding the perfect values for each I/O Scheduler and Interactive tunables.

Short, we <3 you Franco Team :)
[Samsung Galaxy Nexus] J-Hop2o6:
Wish Franco & Team we're over here at the HTC One section :( But we have some good ppl over there tho.
[Samsung Galaxy Nexus] whitedragonz83:
Franco had NOOP as default on some recent N4 nightlies and I started to try it myself on our GNex. It's been almost a week I think and honestly, it doesn't feel that bad. Occasionally, I think CFQ/Deadline/Row would have provided a little more fluidity to some UI interactions, but I've not had a single lockup, or barely a hiccup, which would occur on occasion with other schedulers during high write times.

Has anyone else been experimenting with NOOP?

I am curious what others thought about it with r378-Osmod.
[Samsung Galaxy Nexus] dratif:
Couldn't agree more:)