yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] crypticc:
Er, the same link you got the non caf one. look for "CM latest" in the glitch page
[Nexus 7 (2013) Android Development] spajdr:
10/25 deb still doesnt boot.

10/26 deb also doesnt boot.
[Nexus 7 (2013) Android Development] pantmunu:
Sorry if its already been asked ..Di I need to flash gaaps everytime I install this ROM or its it backed up automatically ...
[Nexus 7 (2013) Android Development] rubene66:
i did a full wipe and i still have problems with aosp browser it become unresponsive and force close all the time can not use it even in beta 2 chrome work fine
[Nexus 7 (2013) Android Development] pantmunu:
OK just flashed the new version and enabling pie controls with force close the system ui .
[Nexus 7 (2013) Android Development] teh roxxorz:
You need to flash gapps. Unless you previously moved them to data and just restore with titanium backup.
[Nexus 7 (2013) Android Development] uprightbass360:
Awesome PRIME! Thanks for doing this, really looking forward to giving this a spin ( and ATOM once you get that out). I ran ATOM for quite a while on grouper, and it flew, I can only imagine what its going to do on RAZOR.
[Nexus 7 (2013) Android Development] PrimeDirective:
Sorry, this is not replicateable. Pie functions perfectly on my device. You need to give me more steps on how you caused this please. Also make sure you do a clean flash for the sake of providing accurate bug reports since this is a public beta.
[Nexus 7 (2013) Android Development] sirbanger:
Love this ROM, thanks Prime.

Will be ready as my daily driver once the thumbnail issue (all thumbs distorted) is fixed and the app switcher in different DPI's is fixed (currently with 240 DPI the app switched icons are distorted and the close all apps button is sort of cut off on the top right corner of app switcher)

Can't wait to see how this evolves :)

Edit: Plus it would be nice if transparent Nav bar would work. I can only get it to work for like 5 seconds after turning off expanded desktop view, then it reverts to opaque.
[Nexus 7 (2013) Android Development] PrimeDirective:
As far as the layout issue.. I'm not really seeing anything that stands out. I dont know if anything can be done about that anyways since it probably involves the size of the images not being correct for those dpis and having them force fit into a container of a different size. It's honestly pretty low on my priority list because of the other bugs introduced with the 4.3 merge. The thumbnail issue is known. I have a feeling it's related to compiler optimizations in libjpg-turbo repo. To test changes of this nature you need to rebuild the intermediate host files and part of the tool chain from scratch which takes a lot more time than compiling a simple Java change. Since it takes me about 40 minutes to do this I can only work on it passively for now but eventually it will be fixed.

I appreciate the feedback. The navbar transparency issue is probably an easy fix. I'll try to have it done by the next build.
[Nexus 7 (2013) Android Development] DroidIt!:
Hey Prime, been using your ROM for a couple days and am very impressed overall. Just about tried every ROM released for the n7 and I think this is the smoothest and most snappy ROM. Everything works good for me outside of known issues, the only thing I noticed was that busybox won't install. I have busybox pro from the market and every time I try to run it, it freezes at a different point in the loading process. Once it got to 50% loaded, another time 27% loaded, etc. I've never had this problem before, any ideas what the issue could be?
[Nexus 7 (2013) Android Development] PrimeDirective:
this rom comes with busybox and we include extra tools then the versions available in the market. do you actually use busybox? are you interested in testing/developing for vanir? but other than that was that busybox package you installed updated for the security changes to 4.3? If you think this ROM is snappy wait until you try ATOM. It uses this as a base but contains additional optimizations and upstream commits that are being tested for vanir. i got the original N7 over 7000 in quadrant with ATOM 4.2.2 on it which is nearly double stock value.
[Nexus 7 (2013) Android Development] DroidIt!:
Hey Prime, OK wasn't aware of that fact. No, no developing :), just sometimes use terminal command line on device. I'll dump busybox then. Really looking forward to further developments, I hit approx 24,500 in antutu with CM and stock kernel. Great ROM, looking forward to the next release :thumbup:
[Nexus 7 (2013) Android Development] JesseTron:
It's the kernel. Release 6 has some issues. Not the ROM.
[Nexus 7 (2013) Android Development] rubene66:
I really want to use this rom is very fast but was getting some force close system ui and aosp browser dont work well i am running cm 10.2 with jessy kernel and i have no problems
[Nexus 7 (2013) Android Development] Ronde90:
Hi. The only problems that I seem to be encountering is when using any app, sometimes the rom freezes for a bit. The other is that contact pictures are distorted when displayed. Other than that everything is running good! Thanks for the awesome work!
[Nexus 7 (2013) Android Development] PrimeDirective:
you probably need to change your kernel or kernel settings. I've been using vanir 4.3 on it since the day it came in the mail and have not experienced freezes.
[Nexus 7 (2013) Android Development] PrimeDirective:
this source is in the public beta stage. it says beta in the title actually. when the issues are resolved then it will not say beta ;)
[Nexus 7 (2013) Android Development] PrimeDirective:
it took me nearly all night but i fixed the thumbnail issue.

ughhhh!!!

time for bed.
[Nexus 7 (2013) Android Development] DroidIt!:
Just in general so you know, it's pretty universally frowned upon to ask for an ETA anywhere on xda. All these roms, kernels, mods, etc come at the expense of each devs freetime and they provide all this goodness for free. So just out of respect for the dev, please don't ask for an ETA :)

from my Viped out one x
[Nexus 7 (2013) Android Development] PrimeDirective:
no.
[Nexus 7 (2013) Android Development] Raverbunny:
Just gonna have to wait for deb, no need to post about non working builds.

Primedirective said on G+ he's taking a break (well deserved too) so don't be surprised if this thread goes unanswered for a while.

Besides as was pointed out to myself before, this thread is for flo, deb builds are not supported officially, they just get posted on Vanir mirror.
[Nexus 7 (2013) Android Development] samuel0213:
The latest version has a little bug, the memo useage bar on the enhanced recent panel always display free ram 0mb
[Nexus 7 (2013) Android Development] gunfromsako:
Has anyone running vanir played dead trigger 2? It kept freezing on me so I restored stock imgs and it plays fine... I was on stock kernel for vanir.
[Nexus 7 (2013) Android Development] phillysmako:
I've flashed the caf version of glitch and the cmlatest18 glitch kernel and neither boot anyone have any idea what version of glitch I flash
[Nexus 7 (2013) Android Development] Marescallus:
I think that's the same version. Flash the non-CAF version.
[Nexus 7 (2013) Android Development] phillysmako:
Yeah but doesn't vanir use cm kernel
[Nexus 7 (2013) Android Development] Marescallus:
Did you try both versions?
[Nexus 7 (2013) Android Development] phillysmako:
I haven't tried the non caf version yet..... shouldi try an aosp kernel like Franco or elemental with the color fix
[Nexus 7 (2013) Android Development] Marescallus:
I just tried the latest non-CAF version of Faux kernel, and it didn't work.

Edit: I just tried the latest CAD version of Faux kernel, and it didn't work either. So neither have worked.
[Nexus 7 (2013) Android Development] Marescallus:
I think this ROM can't have a kernel flashed that changes the ramdisk anymore. I think, I'm not entirely sure. I just remember reading that somewhere.
[Nexus 7 (2013) Android Development] Ronde90:
I have been playing it non stop on vanir and it works great for me. Maybe a clean install will help solve the freezing issue?

Also, I just saw that Omni rom has implemented the multi window feature into its builds. It looks really cool and seems to work well. Does anyone know if there are any plans of implementing that feature into vanir? Thanks.
[Nexus 7 (2013) Android Development] natezire71:
It's in our Gerrit... hopefully Nuke will merge it soon. We didn't want to put it into Vanir since it's still technically not finished yet--even for OmniROM.
[Nexus 7 (2013) Android Development] DroidIt!:
Asked Prime about this myself once and he said custom kernels in general aren't supported anymore. So even if you do flash a custom and it does work, still might want to watch for any unusual behaviors or possible battery drain. The impression I got was that goes for ANY custom kernel with Vanir.
[Nexus 7 (2013) Android Development] natezire71:
It's because Nuke is using CM's proprietary code now. I talked to him about it and he doesn't really care. It sucks, because Toro can't use custom kernels either
[Nexus 7 (2013) Android Development] DroidIt!:
Ah, ok good to know. That's too bad, for the first time I picked a custom kernel over a rom because I like the kernel so much. :(
[Nexus 7 (2013) Android Development] natezire71:
I don't blame you. Dave (PrimeD) and I hate that Vanir is starting take CM's proprietary code. Nuke won't listen to us--so... Yeah. :|
[Nexus 7 (2013) Android Development] DroidIt!:
Well, last time I used the ROM was about a month or so ago. When I was using it it ran really good, just I personally like to have control of cpu freqs, zram, I/o schedulers and such. They don't have a bad product from what I experienced, but to me that's kind of cutting out a major part of being able to root. Well, enough about that, it's their ROM and I don't wanna be rude to anybody in their own thread, so jus chalk it up as a difference of opinions I suppose. Who knows maybe they'll change their minds in the future, they did it once. :)
[Nexus 7 (2013) Android Development] natezire71:
No, be rude. Nuke (pretty much the self proclaimed King of Vanir) has decided to go an alternate route and not use AOSP code. This means custom kernels don't work. Go to Google Plus and tell Nuke in the Vanir group that you hate not being able to use custom kernels. He won't listen to Prime or I. He doesn't care. If enough users told them this, he'd have to listen. Please do this. The stock kernel is good, but I prefer other kernels too.
[Nexus 7 (2013) Android Development] DroidIt!:
:) In that case, might need to join the G+ community and show some support. To bad he doesn't listen to his own team. Anybody else reading this if you felt this was your favorite rom or if it still is, please join the G+ community and show support for the team. :good:

---------- Post added at 03:10 PM ---------- Previous post was at 02:59 PM ----------

Oh, located here https://plus.google.com/u/0/communities/111378032131473754160 Just hit the big red "Join Community" button ;)
[Nexus 7 (2013) Android Development] Raverbunny:
Why bother? Unless you're gonna praise their work you generally get ignored. Its their rom after all and they can do with it as they see fit. I joined G+ so I could ask a simple question and all I got was animosity.
[Nexus 7 (2013) Android Development] DroidIt!:
They're gonna love the question I just left them then :D Like Nate said, if we get enough numbers in there though, we can make a change. Screw them and their animosity. Mostly I want to do this because I know what it's like to have a good team. I'm lucky. I beta test for the :) for the :) and the dev we have in their is a great guy and is always asking for more input from us. That's primarily how he decides what he's gonna do next, listen to us and take feedback from the community. That's the way it should be. Sounds like this guy almost abuses his team or just ignores them altogether. I don't know about you, but that would suck just about any enjoyment I could ever get from something like this. I felt like it was really none of my business until one of the team just told me to join the G+ community and make some noise. That just tells me how bad the situation really is. Soooo, I'm gonna make some noise :D Feel free to leave any additional comments under what I started in the G+ community. We should support the guys that care about the community, not indulge somebody they're clearly not happy with.....my take on it :)
[Nexus 7 (2013) Android Development] Raverbunny:
I hear you mate, I got used to a team that appreciate feedback (Icecold team, great guys) but Vanir seems not to area bout the end users so much, yet without people to use their rom, they have nothing so I can't figure that one out.

Don't even know why I keep coming to this thread, I haven't used Vanir since my grouper days, never had a working build on deb. Hell , I even tried my hands at compiling myself, but couldn't work out why it doesn't boot (not really surprising considering I had no previous experience at rom compiling, I did manage to compile stock aosp so I know my build environment is working at least).
[Nexus 7 (2013) Android Development] DroidIt!:
I like coming to the thread just to check on how things are progressing with the ROM. Every once in awhile I'll try a new build with a custom kernel just to see if things have changed. I don't want to not come here, this really was my favorite ROM. It was right there with the fastest and slickest AOSP ROMs. So, I'll keep coming back and seeing what develops on more than one front now. :)
[Nexus 7 (2013) Android Development] MidnightDevil:
Too bad custom kernel aren't supported any longer, vanir is one of my favourite roms, but I'm afraid that's about til change :/
[Nexus 7 (2013) Android Development] DroidIt!:
Hang on for a couple days. The conversation in G+ kind of went astray and think I actually may inadvertantly got an answer on that. Kind of got off the central issue of the ROM being CM based and not aosp but I didn't want to alienate everybody in there so that I didn't get any answers from anybody at all. Need to try to think of a different angle for that one.
[Nexus 7 (2013) Android Development] natezire71:
Thank you guys. I really appreciate you helping out. I figured if Nuke wouldn't listen to me, he'd start to listen to users. What's the point of making Vanir if nobody uses it? I like using this ROM; oddly enough, I've been on Vanir for about a year now. It's scary, lol. This kernel issue has really gotten me ticked though. I appreciate the user support!
[Nexus 7 (2013) Android Development] DroidIt!:
Well, getting lively again :) You guys really should join the G+ community and voice your thoughts about Vanir being cm and not aosp. I have a good foothold in their and a good conversation is going about it. If you join, look for the name Kevin in there. It's already got over 30 comments total. :D

---------- Post added at 09:41 PM ---------- Previous post was at 09:01 PM ----------

You see here's the heart of the issue and why we should try to get Vanir back to AOSP. All the custom kernel devs for the flo had AOSP based kernels because all the ROMs used to be AOSP based. Well, CM decided to go and split off to a CAF base, meaning proprietary Qualcomm based. That left from devs to choose between caf and aosp as a base for their ROMs. Some chose caf and some chose aosp. So now you have aosp, caf, deb, and flo....a lot of fragmentation for one little tablet. Now comes the kernel devs. They have a choice, they can either continue to just support aosp or they can also pick up caf if they're willing to double they're workload. If a kernel dev has the time, they might do that, but I suspect some of your favorite kernel devs may never support caf, not through laziness or anything, it just because they don't have the time. So you may never get your favorite kernel on a caf ROM ever.

Now, in comes the Vanir main dev. He decides to go and change Vanir without any input from it's team whatsoever and by extension us, the people they're supposed to be making the ROM for. Basically that dev is crapping on the whole community and mistreating the people he's supposed to be working with. In that case, why even put your ROM on xda at all. What's the point?

So that's why I'm asking as many as possible to join the G+ community page and make yourselves heard, about not just the team, but also the fragmentation and the burden that it's also unfairly dumping onto the kernel dev's. So, please join.

---------- Post added at 09:44 PM ---------- Previous post was at 09:41 PM ----------

:D Oopse, well that's a first. Some tool named Eric McCann just banned me too. If you do happen stop in the G+ community be sure to give him a special hello for me. :)
[Nexus 7 (2013) Android Development] natezire71:
I literally cannot believe he said that to you. I'm so mad at him right now. I really think everyone should stop using Vanir. I'm hoping he'll quit or everyone in the team quits. Screw Nuke. I'm sorry he banned you--just know everyone else on the Vanir team is actually really nice. Dave (Prime) is chill. He's the one who got me where I was right now; I would never have discovered the wonders of Linux without his "push".
[Nexus 7 (2013) Android Development] DroidIt!:
Wow!!!! Eric McCann is the main dev. Well, make sure you say hello :)

---------- Post added at 09:58 PM ---------- Previous post was at 09:55 PM ----------

:D Didn't know he was the main dev, that makes it even better. I got a good zinger in on him though didn't I. Don't worry about it, I'd say a whole lot more to him now that I know who that dude is :)

---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------

Makes me even more glad I said what I said, he apparently REALLY nds to hear it and a whole lot more of it.
[Nexus 7 (2013) Android Development] natezire71:
I'm Nate, lol. The guy that responded after you. I saw.
[Nexus 7 (2013) Android Development] DroidIt!:
Kevin. Glad it was Nuke. :D Jeeze man, he needs to hear what I said and a whole lot more from a lot more people apparently. He missed pissed me off so I let it rip. He's got another thing coming if he thinks I'm gonna loose any sleep over that. Glad I can't be a part of that community with him at the head. Well, did what I could though, apparently no more escapades for me on that particular page. :)
[Nexus 7 (2013) Android Development] natezire71:
Seriously though. I'm sorry he was rude to you. I wish he wasn't. I wish nobody used Vanir. I really do. If everyone stopped caring--he'd have to listen. Until then--"it's the kernel devs' faults!!11!1!one!"
[Nexus 7 (2013) Android Development] DroidIt!:
It's really too bad though, this really was one of my favorite ROMs, but yeah knowing what the main dev is like really kind of ruined it for me. Never gone off on somebody online like that before though, that was a first too. :D

---------- Post added at 10:13 PM ---------- Previous post was at 10:11 PM ----------

I'll still put out a call though. Go join the Vanir G+ page and post in the discussion I started. Go join the party and get banned by Nuke. :p

---------- Post added at 10:19 PM ---------- Previous post was at 10:13 PM ----------

Like I said, really the whole reason I went in there in the first place is because I wouldn't want to be stepped on in my team either and you have to draw the line somewhere. We're all human with feelings, didn't see what gave him the right to abuse his position like that. Well, hopefully you guys get something sorted and get that dude out of there somehow, one way or another.
[Nexus 7 (2013) Android Development] natezire71:
Well, he banned me too. He banned me from the ROM I've been using for a year now. I've only really developed here and there for it--but wow. I guess I'm looking for another ROM then. To IceCold it is.
[Nexus 7 (2013) Android Development] DroidIt!:
Are you serious!? Well,sad to say it, but yeah you might be better off. It's sad though that someone could ruin something for you that you cared about though.

---------- Post added at 10:54 PM ---------- Previous post was at 10:52 PM ----------

Ice cold is good. Also using slim myself right now.
[Nexus 7 (2013) Android Development] natezire71:
Ice Cold was made to not have issues with custom kernels; that's why I wanted to use it.
[Nexus 7 (2013) Android Development] DroidIt!:
I had good luck with Ice Cold and faux and Slim and faux (see a pattern here? :) )
[Nexus 7 (2013) Android Development] PrimeDirective:
eric mccann wasn't the main dev by any sense of the means.. at least until i quit vanir. We all shared responsibilities. DHO and Dan Trifan (are the other 2 core devs) but DHO is now a full time doctor and Dan hasn't had much time. He's since apologized for acting like a **** and it seems has had a change of attitude towards developers/contributors so i may be back to vanir for 4.4.

as far as custom kernels go it's a ****ed up thing what CM is doing to AOSP. I have a feeling they're trying to solidify a market niche so they're trying to make AOSP as incompatible as possible to get more developer support since well they based their company around making money off of open source and developer contributions. it's ****ed up. i cannot stress how much i dispise CM for what they are doing. A lot of ROM developers are torn between thinking they have to use CM for "compatibility" to non-aosp devices or supporting AOSP and risk not having the skill required to get a functional device tree and kernel support. personally i say **** CM entirely. it's pretty obvious that device trees and support can be made for any device they have.
[Nexus 7 (2013) Android Development] DroidIt!:
Hey Prime, glad you're on. I was thinking about it and really wanted to apologize for posting all this stuff in your thread. That's a first for me too. :( So if you wanna go ahead and wipe my posts, that would be cool with me. Don't want any of this to reflect badly on you. It's all under your name, so feel free. :)

from my Viped out OneX
[Nexus 7 (2013) Android Development] PrimeDirective:
i'm not at all worried about it.
[Nexus 7 (2013) Android Development] DroidIt!:
Btw, Dan was really pretty nice through the whole thing, he was the only sane voice in the whole mess. It was Eric was the real issue. He went after me and Nate.

from my Viped out OneX

---------- Post added at 11:52 PM ---------- Previous post was at 11:46 PM ----------

So quit kind of? :)

from my Viped out OneX
[Nexus 7 (2013) Android Development] styr:
Ok,1st of all i`m Dan and it seems that your post got deleted from G+, again, something i`d rather not comment, but i`m still willing to try to get to the bottom of that.

This is the change that needs to go into the ramdisk (for the kernels that use a custom ramdisk) to make vanir (and other roms that use the CM telephony commits) go past the init phase and start the boot process.

I`ve also checked Faux CAF compatible kernel`s source, but there are alot of CAF commits there to be able to pinpoint things. As i said on G+, i don`t have a flo, or another CAF device for that matter so i can`t test things, if you are willing to help and get me some logs(logcat and dmesg) to see where the boot process crashes i can investigate further.
[Nexus 7 (2013) Android Development] DroidIt!:
Hey Dan, sorry it turned into that, but.....like I told Dave, Eric made it into a personal attack against myself and Nate, so....well, I guess we'll leave it there. I did appreciate your level head and also you coming here, that just speaks to what kind of person you are, thank you for that. Um, it's going to be an extremely long day here for me at work, about now and won't get home until about 9p tonight, so today will be a no go for me. But this evening, I can download Vanir. Is there a version you'd like me to download so it'd make it easier or wouldn't it really matter? But yeah I can test and get logs and all that good stuff. If you could let me know and I'd be happy to help. Again thanks for coming. :)

from my Viped out OneX
[Nexus 7 (2013) Android Development] styr:
Just get the lasetst nightly, and there is no rush, it`s gonna be a long asynchronous process since we`re on different time zones (gmt+2 here) :D