yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] varadparulekarofficial:
If looking to buy a phone from developer point of view, of course, nothing can beat the development on a nexus device..

Otherwise I strongly feel that Samsung knows how to make use of that big screen estate while Google does nothing to make that 5.96 inch useful..

Its really pitiful to see how lollipop looks like on Nexus 9, everything is blowned up for the 9 inch panel..
[Samsung Galaxy Nexus] RW-1:
Me too, (frustrating as all get out) of course that said, it was all tips and rumors, the only real thing seen was the coming soon on the VZ site itself.

Now on the surface it would appear that it comes after the GS6 ?

At least now I can plan on a wipe and install of smittys homebuilt with R11 on Sat morning :)

As far as my comments as to why to get one, it also depends on what you are coming from (IMO) , I'm a one phone wonder, and for me the last 3 years its been me and my GNex (sorry Arrow ... :) )

Any upgrade now would be fantastic in terms of hardware, but now staying on VZ means what was said before - nexus to be unlocked (without trying various hacks, etc.) AND if on edge I don't have to shell out the whole thing at once ...

Yes, I also agree that Google hasn't yet done anything to take advantage of the screen, I don't like samsung either, with the GNex as an exception - why they couldn't see making a larger version with current HW - damn thing would sell like an iPhone! :) That said, Apple didn't really do anything for the larger phone either, nor the pads, most apps were just scaled up until the dev's redid them.

I'm hopeful that in future releases Google will likely take what they see out there and incorporate into the OS, as they have done in the past.
[Samsung Galaxy Nexus] cujo6801:
This one's for Leonard Nimoy

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Rushead:
That'll make more than just your ears pointy
[Samsung Galaxy Nexus] :
hi, when I try to flash the kernel R11 on the CM , the phone locks on bootanimation just before it ends the animation ( when the face turns and goes down , I do not know how to describe it ) . It all works fine if I leave the stock kernel . What can it be?
[Samsung Galaxy Nexus] RW-1:
I'm now on the homebrew 2-15 with included R11.

Just why do we get the bot animation speed changes? I also on first boot had it lock up twice, requiring a batt pull, but got into the OS on the thrid. I'm now playing with settings, CPU runs about 67, trying lowering voltages slowly to manage.
[Samsung Galaxy Nexus] bsmitty83:
See this

http://xdaforums.com/showthread.php?p=58882808

I think its different with my kernel vs stock because I used gzip for the compression , maybe I'll try xz for the next version .
[Samsung Galaxy Nexus] jguerdat:
I installed Rom Toolbox Lite and disabled the boot animation to "fix" this. The animation stops but the system is still working - my GN is used only as a bedside clock and will finish booting as well as start the clock so I know the display is stuck but everything is (mostly) working. Unfortunately, there's no way to access the desktop or apps. Disabling the boot animation allows the boots to work fine.
[Samsung Galaxy Nexus] :
I solved following the guide that has linked bsmitty..

Not even started, crashed just before the end of the animation.
[Samsung Galaxy Nexus] RW-1:
Hmmm .... [taps pen on desk repeatedly] Hmmmmm ......
[Samsung Galaxy Nexus] cowsquad:
Are you getting The nexus 6 man
[Samsung Galaxy Nexus] RW-1:
I plan on it, when it finally arrives on VZ, Neph and I been awaitin ...

I think if it has 5.1, that would be great, but think it would be a day one ota myself ...

Thinking about a supcase for it:

http://www.amazon.com/SUPCASE-Google-Unicorn-Premium-Motorola/dp/B00OHFGUDU
[Samsung Galaxy Nexus] cujo6801:
That's the case I'm getting for it

Sent from the "DOG" pound
[Samsung Galaxy Nexus] RW-1:
Amen to that, it does look like the best, but going clear/black to see "Nexus" or black/black ?
[Samsung Galaxy Nexus] cujo6801:
I was thinking clear/black

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Nephilim:
No case for me, I've had 2 Gnex's in the span of owning this device and have not had so much as a scratch, no way I'm covering up how slick the N6 looks.
[Samsung Galaxy Nexus] nikodr:
Nephilim i am still on r6 on fml with your settings on trickstermod is it worth going to r11?
[Samsung Galaxy Nexus] zzpianoman:
How do you feel about the fact that it's not going to have a removable battery?
[Samsung Galaxy Nexus] cowsquad:
The only disadvantage I am thinking about is that i will be giving my unlimited data up :(

---------- Post added at 07:42 PM ---------- Previous post was at 07:16 PM ----------

Really. I totally didnt know that. Oh man that is going to suck
[Samsung Galaxy Nexus] Nephilim:
I'm still on r6 with the last official FML also. Haven't had any time to update. ;)
[Samsung Galaxy Nexus] TheMan0790:
I will say this - I am on latest CM12 build with r11 and his settings. My phone is the best it has ever been on Lollipop with this combination. Loving the performance of this kernel version and settings.
[Samsung Galaxy Nexus] RW-1:
I've been off unlimited data for at least since I got the wife a GS5, as we have 10Gb currently, I've watched the usage, I've hardly busted 4Gb in a month, and that's for both phones, even playing ingress heavily and Play music.

with my IT duties, I'm wifi at home, office, and most clients (since I set them up I have the pwds :) )

Unless you were torrenting or watching movies over your mobile data connection, tethering to aPC, which I've also done on occasion to my laptop, I haven't missed unlimited at all.

As to the battery - Well - GS6 - non removable. they are all running that way, so ... in my mind I'd alreay had the mindset that a smartphone would require strategic charger locations - home, car, desk at work, it's a fact of life.

Removable only assisted me in batt pulls, and I had the extended on my GNex. All in all - I'll live. I'm sure ifixit would have a breakdown if one really needed to tear into it to replace, but could get that done under warranty if need be.

I just want to know I may be able to get the 64Gb version on edge, still awaiting, 8 days to go! :)
[Samsung Galaxy Nexus] bsmitty83:
I Updated the OP with new FML builds

justt a few minor cherry-picks I made as I'm getting my feet wet building roms

I added back the advanced reboot menu in developer options ,

selinux status is shown under settings/about_phone ,

the rom is using dlmalloc ,

and the rom will only keep up to 36 apps in recent tab , instead of infinite ( 100 actually )

enjoy , hope they work well for everyone
[Samsung Galaxy Nexus] osm0sis:
What kernel should we use, the bundled one or R11? Anything new kernel-wise? :) :good:
[Samsung Galaxy Nexus] bsmitty83:
R11 is the included kernel , Ive been messing with ROM's and am kinda working on a update for the kernel now .
[Samsung Galaxy Nexus] zzpianoman:
The default for recents is actually 100, not infinite - but it certainly does seem like it!

Kudos for bringing down this limit to a much more sane 30. I've added a build.prop config option in my ROM to bring this into userspace, so maybe others will want to cherry pick once I get it pushed to github.
[Samsung Galaxy Nexus] trzesickipiotr:
Hi

I still get some occasional reboots on R11, but this time I don't have any specific logs in last_kmsg.

The only thing that I've noticed in last_kmsg is:

[17042.752899] _event_notify: remoteproc: ipu has crashed
[17042.753051] rpmsg_rproc_error: Fatal error in ipu
[17042.753356] rpmsg_rproc_error: Fatal error in ipu
[17042.753540] rpmsg_reset_work: reseting virtio device 4
[17042.754089] rpmsg_resmgr rpmsg13: Enter rprm_remove
[17042.756103] rpmsg_reset_work: reseting virtio device 5
[17042.756652] rpmsg_resmgr rpmsg15: Enter rprm_remove
[17042.757537] rproc_reset_poolmem: invalid pool
[17042.758026] omap-rproc omap-rproc.1: stopped remote processor ipu
[17042.760559] omap-rproc omap-rproc.1: powering up ipu

Can it be related to undervolting VAUX3_6030 or VMMC?

PT
[Samsung Galaxy Nexus] RW-1:
Kewl! Going to flash it shortly, going to dirty from the last one, see how that goes as I don't mod it at all.

7 days Neph, 7 days hehehe ..... (5 if you don't count weekends)

UPDATE: That didn't go well, FC's all over, reverted to my backup made just before trying the DF ... :)

Will CF later ...
[Samsung Galaxy Nexus] XlAfbk:
any chance for dt2w/s2w in this kernel?
[Samsung Galaxy Nexus] cujo6801:
Who are these guys?

Never heard of them..

[MENTION=4981826]AOKP_ROM[/MENTION]: Life happens, but we are never done! http://aokp.co/blog/down-but-not-out

Sent from the "DOG" pound
[Samsung Galaxy Nexus] bsmitty83:
Im not sure . I haven't been able to port showp1984's version, which is what you want for dt2w , s2w etc . I haven't given up but its not at the top of my list either
[Samsung Galaxy Nexus] shadowam:
Really happy to know you are trying to port it! Some of us have bad power buttons and dt2w/s2w really helps :)
[Samsung Galaxy Nexus] RW-1:
https://www.youtube.com/watch?v=qRC4Vk6kisY
[Samsung Galaxy Nexus] cujo6801:
Now that's funny....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] RW-1:
Thanks, one of my daughters Favorites, was appropriate. :)
[Samsung Galaxy Nexus] cujo6801:
I'm having a really good hair day.... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] aditya.jazzmaster:
[MENTION=4608636]bsmitty83[/MENTION]

Is there way that wake gesture (xposed) can implemented in this kernel (KK version too)?

http://xdaforums.com/xposed/modules/app-wake-gestures-v1-1-t2768266

Thanks
[Samsung Galaxy Nexus] shadowam:
Also, maybe this can help you with the dt2w/s2w implementation for our Gnexus [MENTION=4608636]bsmitty83[/MENTION], and without Xposed! :D

http://xdaforums.com/showpost.php?p=58909955&postcount=34
[Samsung Galaxy Nexus] bsmitty83:
Well , they are both one in the same as I see it , as well as both require showp's s2w/dt2w code , which is mainly , if not exclusively on msm based devices . I really wish bponury would opensouce his s2w code from his old app that isn't available anymore.

But yes , basically this is what I'm trying to port , its just our touchscreens are a lot different than the others . the closest I've found with working gesture wake is the note 2 , but still there are major differences to work through .
[Samsung Galaxy Nexus] RW-1:
Wow, so 5.1 hits AOSP, MW has a build ready to drop any minute now.

VZ will have the N6 on thurs for web and dirfill, stores next week (boo). but ...

comcast/xfinity has a $200 gift card promo - go thru them to add the N6 on edge or contract and get the gift card, that sounds like my deal!

.... and my GNex gets 5.1 to finally replace my OG droid as a desk music player/clock radio hehehe ....
[Samsung Galaxy Nexus] osm0sis:
Found a difference; the R11 bundled with the FML 3/4 Homebrew has zram enabled again. ;)

Found a bit of time to rewrite a bunch of my Synapse interface as conditional and added support for all the controls from KitKat on various kernels (franco.Kernel, Fancy Kernel, DirtyV - in my various osmods) and hopefully future proofed any feature removal issues on Full_Auto. So, if you like my version of the Synapse interface over apbaxel's Universal Kernel Manager version then this should work on any recent GN kernel now. :cowboy:

https://github.com/osm0sis/GN-Synapse-Injector

http://v.ht/osmods

Enjoy! Let me know if you encounter any issues so I can fix them. :good:
[Samsung Galaxy Nexus] bsmitty83:
I did add the option back in but its still not stable , I won't be removing it again .

Since I'm going to order a new phone tomorrow , I'll probably update this kernel one more time , then use my gnex to work on a 3.4 kernel .
[Samsung Galaxy Nexus] smiskkissen:
Want to make an init.d script with [MENTION=2853378]Nephilim[/MENTION] 's settings. Can I just update the parameters in the script [MENTION=3317173]büscher[/MENTION] did for DirtyV?

http://www.mediafire.com/view/x147ukwy22el5x9/98_nephilims_settings_for_dirtyv.txt

Also is the Lowmemorykiller whitelist script still needed? If so, does it need to be changed?

http://www.mediafire.com/view/yj51ejl65lmdsdb/97lmk_whitelist.txt
[Samsung Galaxy Nexus] bsmitty83:
The script should all be OK except for the GPU freq and governors , and you can use the whitelist for lmk , i added it to this kernel as well [emoji1]
[Samsung Galaxy Nexus] osm0sis:
Ah cool, I've been meaning to rewrite the Synapse interface for those. :)
[Samsung Galaxy Nexus] bsmitty83:
I guess I should mention that R11 will work on all LP builds , except old FML builds .

so anything but FML 5.0.2 will work now as all are using the same audio setups .

sorry for the confusion , which seems to be a speciality of mine lmao
[Samsung Galaxy Nexus] rambhanushali20:
It doesnot work in 5.1... Got Bootloop.
[Samsung Galaxy Nexus] bsmitty83:
It most definitely works Sir .
[Samsung Galaxy Nexus] cujo6801:
Worked for me as well...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] RW-1:
Audio also working for me with R11, which is why I asked Smitty to clarify on it for all of you hehehe ....

5.1 is much more stable memory wise than 5.0, (with all those commits, who'd have guessed? :) ) Looking at 4G/3G handoffs yet. Cant play utube videos ... but overall a pleasant experience.

So, VZ ... I'm laughing right now, so it was as I figured on another thread, those that thought order today, get tomorrow, not. Pre-order and goes out the 18th to arrive same as in store launch day.

It's not as bad, because I expect it from VZ, but how Google mucks up their N launches is just astounding. But heck, going to go by the corp store I've got friends at on Sat anyway, might score one early anyways, we'll see, or at least play with one in hand for an hour ...
[Samsung Galaxy Nexus] RW-1:
Darn, not playing video locally or on utube, I went back to the R10 kernel just to try that, and no sound, now I'm reflashing the R11 from the OP ...

Weird, ok, after the flash, I'm good again ....
[Samsung Galaxy Nexus] wbedard:
[MENTION=4608636]bsmitty83[/MENTION] ,

As you have time, would you be willing to put up a brief post explaining how to convert your kernel so that SELinux is enforcing. I'm pretty sure I have all the required tools (Android Image Kitchen, etc) and I have searched far and wide for any posts explaining this process. I feel like I'm missing something pretty obvious at this point.

R/

wbedard
[Samsung Galaxy Nexus] aosp:
./mkbootimg --kernel kernel --ramdisk ramdisk.cpio.gz --cmdline 'console=ttyFIQ0 androidboot.console=ttyFIQ0 cgroup_disable=memory mem=1G vmalloc=256M omap_wdt.timer_margin=30 no_console_suspend androidboot.selinux=enforcing selinux=1' --base 0x80000000 --pagesize 2048 -o new.img
[Samsung Galaxy Nexus] bsmitty83:
In a terminal or adb , type "su" , "then setenforce 1"

or if you need to convert it do what [MENTION=2838735]aosp[/MENTION] wrote in the last post
[Samsung Galaxy Nexus] wbedard:
If I understand you correctly, you're describing how to switch the SELinux mode once the device has already booted. While I understand that I could insert such a command (or similar) into an init script (or use the app so popular these days), what I am really looking for is a method (such as what aosp posted...) to convert your kernel so that SELinux is configured as "enforcing" at boot-time. Thanks for your post...please do let me know if I missed something in what you said!

R/

wbedard

---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------

Thanks, aosp...that's perfect! I believe I can work with that...:>)

R/

wbedard
[Samsung Galaxy Nexus] RW-1:
2nd time today, it locked up for some reason (beofre that I lose sound for certain things, noticed right now my phone rang and no ringtone ...), batt pull, and on the reboot locks on animation, but the third time I restart it it begins a whole app optimization again, though I hadn't made any changes to warrent it. FYI ... R11
[Samsung Galaxy Nexus] RW-1:
Well, I ordered my N6 on edge, thru comcast for the $200 gift card a moment ago, I couldn't pass that up. Having it shipped to my IT office so someone will sign for it, can't wait! :)

Now to order my case ...
[Samsung Galaxy Nexus] wbedard:
Hi [MENTION=2838735]aosp[/MENTION] ,

Whenever you have the time, I'd like to follow-up with you on your suggestion for repacking the Full_Auto kernel with SELinux in enforcing mode. Thus far, I have been unable to create a kernel image using the above command that didn't boot-loop on my device. I have tried using AIK on Windows, "abootimg" under Linux and just about every reasonable permutation of the mkbootimg command I can think of. Prior to your suggestion, I had been using the same approach but with a smaller cmdline parameter that only included the SELinux elements. I haven't done enough research to understand how this mechanism works with the CMDLINE parameter that is built into the kernel at compile time. All of the kernels that I have built that used the smaller, selinux-relevant cmdline have booted fine but with SELinux in permissive mode, like the cmdline parameter was ignored. All of the kernels I have built using the much longer cmdline string have boot-looped nearly immediately upon device startup.

I would be curious to know if you have done this successfully yourself and, if so, what sort of environment and toolset you used. Thanks in advance for help with this!

R/

wbedard
[Samsung Galaxy Nexus] TheMan0790:
Hey Smitty. I know you said you were going to push out maybe 1 more update before moving to your N6. Question: is anyone else taking up the reins of continuing development with your kernel? Curious, since I imagine Ziyan will continue to push kernel-specific commits and it would be cool to see some of these commits added to your kernel.

PS: In no way am I suggesting people avoid Ziyan's kernel if they use CM12. Just asking for the sake of choice for our Nexus :)
[Samsung Galaxy Nexus] bsmitty83:
I'll still be working on the nexus , but I want to try getting a 3.4 kernel out . i will always maintain this kernel , but I won't be spending as much time on it developing stuff
[Samsung Galaxy Nexus] nikodr:
I posted to the seperate section of kernel 3.4 development asking the status but i didnt see a response. Happy to know that such a talented kernel developer will work along with others on 3.4
[Samsung Galaxy Nexus] TheMan0790:
You're the man! Thanks dude! I appreciate all the work you do
[Samsung Galaxy Nexus] aosp:
Have you tried without cgroup_disable=memory?

[MENTION=4544860]osm0sis[/MENTION]
[Samsung Galaxy Nexus] wbedard:
Hi [MENTION=2838735]aosp[/MENTION],

Yes, I actually tried to rebuild the kernel using the same cmdline parameter that bsmitty has in the kernel KConfig on Github (which doesn't include the cgroup... parameter). I think that this is either a workflow or toolset problem, which is why I used different toolsets under different OS's with different cmdline strings to accomplish this task. Alternately, I did find some mention where the standard mkbootimg tool might be configured with a maximum allowed size for the cmdline string. I haven't reviewed the source to confirm that but it might be an issue.

Honestly, Google didn't highlight many instances where repackaging kernels with new cmdlines was successful. It's probably something so trivially simple or amazingly stupid that a "face-palm" will almost certainly be in order. I really wish that [MENTION=4608636]bsmitty83[/MENTION] would provide some documentation to go along with his recent commit that "provides the option of running the kernel in enforcing mode...". I have to believe that commit was based on input from someone who knows how to do this.

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
I don't know what documentation your looking for . before I had added a commit that forced the kernel to run in permissive mode , with no runtime option for changing it . now I removed that and set it permissive through the command line. Hence the allow setting it to enforcing mode is back . there is no kernel commit that allows you to change it at boot time . I could remove that and let the ROM set it , but as for pulling apart the image and modifying it like you are trying to do , I have no idea . I compile my zimage from source only .

ps . heres the commit I reverted to allow manually setting selinux again https://github.com/bsmitty83/Kernel_Tuna_AOSP/commit/e9130dd0dee8222d72be94dac6e998420554966c

and heres where its set to permissive on boot

https://github.com/bsmitty83/Kernel_Tuna_AOSP/commit/8336ec21a8693a2ab81f302efc4382a37e7364ee

these were based on nobodys input but myself , I dont run my roms enforcing , and as this is my kernel , thats how i had it set , if you need it set enforcing at boot the simplest solution would be to grab the source and compile a version yourself for your needs , as I cant accomodate everyone
[Samsung Galaxy Nexus] wbedard:
Well, given your clarification, I guess there's no particular reason why I should be "expecting" such documentation... ? I didn't read too far back in the commit history and more assumed based on the wording that you reverted an overly limiting commit based on user feedback. I now understand that were just proactively making your kernel more flexible for "power-users". I just hope one of them will see this thread and share some of their expertise!

Thanks for the clarification. While I would ask if you could simply build a version of the kernel with SELinux in enforcing mode, it addresses an admittedly short-term testing need of mine in support of XPosed/XPrivacy. I'm far more excited about your efforts in helping with the 3.4 kernel effort. ☺

R/

wbedard
[Samsung Galaxy Nexus] bsmitty83:
will do I'll compile it shortly
[Samsung Galaxy Nexus] bsmitty83:
I added R12 to the downloads section

I removed the extra unused fb so the usable ram should be ~750mb

added [MENTION=3390093]MWisBest[/MENTION] 's offmode charging workaround

that is all ;)

enjoy , time for me to go grocery shopping ( ahh the joys of being a married father lol )
[Samsung Galaxy Nexus] cartman333:
Yeeeeeah new build :D gonna flash right now, a lot has passed since the last build, can i ask for a changelog perhaps? :)
[Samsung Galaxy Nexus] dbt816:
Wow... I just loaded R12 (no dalvik/cache wipe) on top of the latest 5.1 FML, which had been running great with R11. It booted up to the "To start Android, enter your password" screen that was reported earlier. :confused:
[Samsung Galaxy Nexus] bsmitty83:
not sure worked ok for me

i changed nothing between the 2 versions that affect the filesystem

you using f2fs ?
[Samsung Galaxy Nexus] bsmitty83:
heres R12 with SElinux set enforcing at boot

it wont recognize your sim card , so be forewarned

Use the link , not the attachment

View attachment Full_Auto_R12-Ak_Enforcing.zip
[Samsung Galaxy Nexus] dbt816:
Yeah, f2fs on data and cache. Trying to redo with a clean install now.
[Samsung Galaxy Nexus] bsmitty83:
thats interesting , it must be something with f2fs , although I haven't changed anything , so it must be Rom side , something different in 5.1 , idk .
[Samsung Galaxy Nexus] dbt816:
Just wiped system, cache, dalvik, and data... reinstalled FML 5.1, FML 5.1 GApps, SuperSU, and R12.... booted right back to the password screen. Tried downgrading to R11, same thing. I'd agree that it's a ROM issue.
[Samsung Galaxy Nexus] wbedard:
Wow, thank you so much for this! No worries on the SIM card issue. My GNex is just a testing device...WiFi only.

R/

wbedard