Database Users

[Q] Adding Eris to CyanogenMod Supported Devices?

Here's what Cyanogen said on the Official CyanogenMod Forums.
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.

I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.
We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.

+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.

Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?
Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.

The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.
The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.
I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.
This comes up every so often. I guess one of us can find out what we would need to do at least...

Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.
The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.

Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.
I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."
And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
Cyanogen said:
There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.
An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.
We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for them, and we also spend much time making all of these (sometimes not so pretty) changes co-exist together without breaking other devices. The more eyes on your code, the better it will be.
That said, as much as we’d like it to be, the CMSGS project is not yet an official part of CyanogenMod. There are also a number of other unofficial ports out there which haven’t been submitted to us that we’d love to include. If you’re interested, stop by #cyanogenmod-dev on Freenode. If you didn’t get it from our mirror network or the CM forums, don’t expect it to be up to our standards.
The biggest thing to keep in mind when porting to a new device is to think about how your change is going to affect other devices. This is the biggest reason why we aren’t supporting Samsung devices other than the Nexus S yet. Don’t change hardcoded default values just to suit your device. Use the configuration options available, or add new ones with the original values as defaults. Do a build for another unrelated device after you make your changes (it helps to have another device to test with, of course) and verify it as well. Android was made for this, so do it right.
Like I’ve said so many times before, CyanogenMod is all about the community. And our community can help you too. I’d love to see more of these ports contributed to the project- it’s only going to make things better. We’ve grown from just a mod to what I’d call an “Android distribution” and we need to keep our standards high.
Click to expand...
Click to collapse

Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft

hallstevenson said:
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
Click to expand...
Click to collapse
+1 10 char......

A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices
https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn

Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. Thanks, guys!

It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.

Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,

Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)

gnarlyc said:
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
Click to expand...
Click to collapse
I thought it was a girl

tazzpatriot said:
I thought it was a girl
Click to expand...
Click to collapse
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0

refthemc said:
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
Click to expand...
Click to collapse
nope still a girl
http://www.youtube.com/watch?v=vwIa2S0YQs4

FYI: http://twitter.com/cyanogen/status/45246447385452544
@cyanogen said:
@Algamer we don't officially support the eris, it would be nice if someone doing the porting joined up with us though
about 8 hours ago via web in reply to Algamerhttp://twitter.com/Algamer/status/45235578886815744http://twitter.com/Algamer/status/45235578886815744
Click to expand...
Click to collapse

I think OUR devs are doing just fine. Why change now?
wildstang83

wildstang83 said:
I think OUR devs are doing just fine. Why change now?
wildstang83
Click to expand...
Click to collapse
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...
Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."
Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.

Hackability?

Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...

aliander said:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
Click to expand...
Click to collapse
almost everything is open.CM10.1 took less than a month to move from alpha to nightly.The other AOSP and AOKP roms took just days.It's an open device with source available!!

hackarchive said:
almost everything is open.CM10.1 took less than a month to move from alpha to nightly.The other AOSP and AOKP roms took just days.It's an open device with source available!!
Click to expand...
Click to collapse
Thanks for the fast reply!
Could you give me some details on what is open/working and what gives us trouble?
I assume that the sound part is difficult to get by, as they claim to have some Dirac HD licensed - given I don't know Dirac HD and their licensing policy...

aliander said:
Hi there!
Currently thinking of grabbing a Oppo Find 5, but I won't make the same mistake again I did with the Galaxy S2 - updates, quite no doc/source for custom ROMs etc.
So, how open is the Oppo?
I see, that CM has landed, but how much is open sourced or are at least the interfaces docuemented?
Thanks for clarification!
Didn't find much on that subject...
Click to expand...
Click to collapse
Do note that two former GS2 CM maintainers have this device, and we both like it.
The real key is that it's Qualcomm-based (qcom has excellent documentation), and Oppo doesn't deviate far from Qualcomm's CAF reference sources.
We also now have access to a technical contact who can answer some questions for us - many of the camera issues in CM should have been improved last weekend thanks to a tip from Oppo.
For me right now, the big question is how hard it is to get to the UART port of the device, since I think I'm going to need it for an upcoming effort.

Dev Needed/Mod/Request

Req- Samsung had finally released source code for my note variant. Would like a hand porting x-note rom to it properly. My model is the SM-N900J (aka scl22). If the rom could be ported with the civ kernel it would be even better. Thanks for looking. http://opensource.samsung.com/
GNote3

dan.kels.r said:
Req- Samsung had finally released source code for my note variant. Would like a hand porting x-note rom to it properly. My model is the SM-N900J (aka scl22). If the rom could be ported with the civ kernel it would be even better. Thanks for looking. http://opensource.samsung.com/
GNote3
Click to expand...
Click to collapse
Probably better asking the X-Note dev's if they'd help you tbh.

Not trying to be a d*** but anytime I ask either directly or in a thread it never gets responded to. I know they are busy with their work and life so no biggy.
GNote3

Probably due to the bricking incident, and the new X-Note 8.0 -- umm in all honesty can't really do a lot as it's their ROM and people will be reluctant to touch it, also, the J models are a nightmare to play around with, I get what you are saying though.. see once 8.0 comes out if the devs may be a bit more willing to help out.

Ok sounds good. The rom actually runs pretty decent on my phone. But I have to flash an old omega rom fix to get Wi-Fi/camera to work and then I get the roaming triangle even tho I'm not roaming. Would live to be able to use that civ kernel. It's smooth but no camera
GNote3

Screw this piece of **** phone that no dev wants to f with. Fn snm900j. Bout to sell it and get a nexus
GNote3

I mean the damn source code is out now so it should be nothing to port for somebody that knows what they are doing
GNote3

[Q] What's the deal with CM11

So I see sai dev saying that he wants CM11. People say it's hard to do, he says someone can do it. Then, he opens a thread about CM12 then just says delete. THEN, he opens a thread saying he has made CM11 for the TN7 but we have to wait a month for it to actually come out. It comes out, people complain, then BAM. The thread is closed for him not having the kernel source code. He creates another thread. BAM. Closed, no kernel source code. THEN he "makes" (more like renames old zip file to tn7 roms" an AOPK ROM. I think we all know why the thread was closed. My point is, IS a NON-FAKE NON-BUGGY version of CM11 coming, or will we just have to wait for official device support? Or, is it just not coming at ALL? Im very confused. I know these roms are most likely trolls, but seriously, whats up with this? Thanks for noticing. :good:

Sai Dev seems like a random troll to me, so I would just ignore everything he posts. Seen the AOKP thread? Yeah, bull**** again.
Considering the total lack of unofficial ROMs for the TN7, I think it's highly unlikely that CM11 is going to hit the device. It's even less likely that it will be officially supported by CM.
I honestly don't understand why there's zero interest in the device, but that's just how it is. Maybe it's because the TN7 wasn't really advertised anywhere, maybe it's the confusing mess of a Git server nVidia operates, which makes porting CM etc. that much more tedious. I still have some faint hope that the upcoming Lollipop release will put the tablet back into some developers minds, CM12 would be neat to have.
But hey, we're running almost stock android here, so it's not like we have to suffer some resource hungry UI or a boatload of ****ty preinstalled apps.

AcoQ said:
Sai Dev seems like a random troll to me, so I would just ignore everything he posts. Seen the AOKP thread? Yeah, bull**** again.
Considering the total lack of unofficial ROMs for the TN7, I think it's highly unlikely that CM11 is going to hit the device. It's even less likely that it will be officially supported by CM.
I honestly don't understand why there's zero interest in the device, but that's just how it is. Maybe it's because the TN7 wasn't really advertised anywhere, maybe it's the confusing mess of a Git server nVidia operates, which makes porting CM etc. that much more tedious. I still have some faint hope that the upcoming Lollipop release will put the tablet back into some developers minds, CM12 would be neat to have.
But hey, we're running almost stock android here, so it's not like we have to suffer some resource hungry UI or a boatload of ****ty preinstalled apps.
Click to expand...
Click to collapse
I agree with the fact he's a troll, and I doubt now that we will have support for CM. But, I do agree, we dont have Touchwiz or crap like that, right?

Verizon Note 7 Port ROM - Project turned over to the community!

I'm back on Verizon after switching to Sprint back in 2008. So I recently picked up a mint condition Verizon Note 4 so I could have a little fun building a new Note 7 port ROM. Many of you may know me as the creator of the Ultimate Note 7 ROM for the Sprint Note 4. I'm here to tell all of you that I've been working on a new Ultimate Note 7 ROM for the Verizon Note 4. It is nearly ready for public beta release! With the experience I have porting Samsung Touchwiz ROM's. I figured it is long overdue for the Verizon Note 4 users. My port ROM has official and original Verizon Note 7 framework, apps, etc. So instead of trying to make international port ROM's work, which is no simple task unless you know what you're doing, get ready for a true Verizon compatible Note 7 ROM. Those of you who still have your Verizon Note 4 and want to get more life and use from it with a fresh look and feel, look for a new ROM thread soon.
I need a few reliable and knowledgeable testers. If you can help troubleshoot and test the rom, please install Telegram app on your PC and your phone and join my Hybrid Port ROM's group so you can have access to the the test ROM and join the rest of us who are ready to get this thing going. See you there!

Why not a Note 8 ROM or Oreo ROM? Just curious. Forgive me, I wouldn't know of any technical constraints.

i cant wait thanks man

JOSHSKORN said:
Why not a Note 8 ROM or Oreo ROM? Just curious. Forgive me, I wouldn't know of any technical constraints.
Click to expand...
Click to collapse
The S8 and N8 ROM's are Nougat 7.0. The N4 has been cut off at Android 6.0 and doesn't have official Samsung Nougat 7.0 kernel source, therefore the Snapdragon N4 can't run Android 7.0. ROM's. If this was possible we would have a lot of excited dev's continuing to build 7.0 TouchWiz ROM's for the N4. Unfortunately Marshmallow 6.0 is all we have for the N4 so the N7 Marshmallow software and perhaps some ported S8/N8 apps is as good as it gets for the N4. What i'm doing is building a solid N7 base ROM for the Verizon N4. Once it's ready I will upload it as a stock base rom. Other dev's can use my base to build out custom ROM's with mods, ROM control, Xposed, etc, etc. This will eliminate the need to fix any network related features. It will all work as it should. International N7 port ROM's are not compatible with the U.S. CDMA carrier's features. This is why we need a true Verizon N7 base rom. I know it's a little late and many people have upgraded to newer phones but if there's still users here wanting to run a proper Verizon N7 ROM, this will be it.
With this said, I welcome any and all testers and dev's to pitch in and help test and troubleshoot minor bugs. PM me if you're interested in helping with this. The ROM is 100% complete and operational but I'm working on minor bugs with a few system apps.

tx_dbs_tx said:
The S8 and N8 ROM's are Nougat 7.0. The N4 has been cut off at Android 6.0 and doesn't have official Samsung Nougat 7.0 kernel source, therefore the Snapdragon N4 can't run Android 7.0. ROM's. If this was possible we would have a lot of excited dev's continuing to build 7.0 TouchWiz ROM's for the N4. Unfortunately Marshmallow 6.0 is all we have for the N4 so the N7 Marshmallow software and perhaps some ported S8/N8 apps is as good as it gets for the N4. What i'm doing is building a solid N7 base ROM for the Verizon N4. Once it's ready I will upload it as a stock base rom. Other dev's can use my base to build out custom ROM's with mods, ROM control, Xposed, etc, etc. This will eliminate the need to fix any network related features. It will all work as it should. International N7 port ROM's are not compatible with the U.S. CDMA carrier's features. This is why we need a true Verizon N7 base rom. I know it's a little late and many people have upgraded to newer phones but if there's still users here wanting to run a proper Verizon N7 ROM, this will be it.
With this said, I welcome any and all testers and dev's to pitch in and help test and troubleshoot minor bugs. PM me if you're interested in helping with this. The ROM is 100% complete and operational but I'm working on minor bugs with a few system apps.
Click to expand...
Click to collapse
I realize the Note 4 has been cut off at Android 6.0, but how are devs able to come up with a 7.1.2 ROM for it? User hsbadr has three: LineageOS, ResurrectionRemix. and EmotionOS (this one seems to be discontinued). I haven't used any of his ROMs for quite some time, because they seem a bit buggy, to me, but that's beside the point I'm getting at. How is he able to make a 7.0 ROM and others can't seem to? That said, why wouldn't an 8.0 ROM be possible?

JOSHSKORN said:
I realize the Note 4 has been cut off at Android 6.0, but how are devs able to come up with a 7.1.2 ROM for it? User hsbadr has three: LineageOS, ResurrectionRemix. and EmotionOS (this one seems to be discontinued). I haven't used any of his ROMs for quite some time, because they seem a bit buggy, to me, but that's beside the point I'm getting at. How is he able to make a 7.0 ROM and others can't seem to? That said, why wouldn't an 8.0 ROM be possible?
Click to expand...
Click to collapse
You're talking about AOSP ROM's. Those ROM's are open source from Google, not Samsung Touchwiz ROM's. Big difference. The kernels they build are not compatible with Samsung Touchwiz ROM's

bmhbmh715 said:
i cant wait thanks man
Click to expand...
Click to collapse
+1

Thanks for this!

Would there be anyway you could make it to use normal bootanimation.zip?

tx_dbs_tx said:
Those of you who still have your Verizon Note 4 and want to get more life and use from it with a fresh look and feel, look for a new ROM thread soon.
Click to expand...
Click to collapse
Hello, I am still rocking the note 4 Verizon. And I will be keeping it as long as devoted members such as yourself put out great roms! That being said I would like to be a beta tester if you so need one. I have a little knowledge in troubleshooting and the like, mostly my expertise is in repairing and building phones. I have a whole closet that's devoted to phone parts repair, and computer systems repair. My last few phones I have held on to until the dev section went quiet, note 2, Moto atrix, moto bionic... they were awesome with deodexed/rooted roms... I am addicted to flashing new roms to find the right balance between performance and battery...
By the way, one slight request, when all said and done fixing most of the bugs, don't forget to make sure the rom has a kernel that is compatible with extended batterys. Most of us holding out with our outdated note 4, usually have those huge batteries hanging off the back...lol

getyroks said:
By the way, one slight request, when all said and done fixing most of the bugs, don't forget to make sure the rom has a kernel that is compatible with extended batterys. Most of us holding out with our outdated note 4, usually have those huge batteries hanging off the back...lol
Click to expand...
Click to collapse
No worries. I'm using the Flashpoint kernel and there's also an extended battery version. It's based on Verizon N4 QI2 so it's good to go.

OH MY GLOB!
I still have my Verizon Note 4, can't wait for this rom ???

tx_dbs_tx said:
No worries. I'm using the Flashpoint kernel and there's also an extended battery version. It's based on Verizon N4 QI2 so it's good to go.
Click to expand...
Click to collapse
I just figured you would build your own kernel. Yes, flashpoint is the best in my opinion, as of right now.

getyroks said:
I just figured you would build your own kernel. Yes, flashpoint is the best in my opinion, as of right now.
Click to expand...
Click to collapse
I really don't mess with kernels. That's not really my forte. If needed, I would just ask someone to build one. But since there's already one available and it happens to be from Verizon source I will use it and give credit. But I may request a new kernel from the latest source once I get the rom ready.

tx_dbs_tx said:
I really don't mess with kernels. That's not really my forte. If needed, I would just ask someone to build one. But since there's already one available and it happens to be from Verizon source I will use it and give credit. But I may request a new kernel from the latest source once I get the rom ready.
Click to expand...
Click to collapse
I think I may have the CQL1 source kernel ready. I've been running it since Tues and was thinking of posting it soon. If you, or anyone else, wants to try it out you can download it here.
The source code is here for those interested.
The changes are the same as the ones for the 910F beta kernel that was posted the other day.
Change Log:
Backported the 3.18 Linux version of Interactive Governor
Add patch for USB fast charge
Add Sound Controls- so far this hasn't negatively impacted anything but it's definitely the change I'm most concerned about and will probably make a separate version without this in the future. Be careful with this. Had my earbuds in and it gets very loud.
LED fade control
Completely reworked the thermal temperature control. So far the temperature has been throttling down pretty good when it goes above the set temp. I've been setting mine on the lowest setting.
Added zswap control
Extended Battery patch is included
On a personal note, I'm very excited to see a port rom that's not built with an international firmware. If there's anything I can help with let me know. My skills are somewhat limited but every now and again I can get lucky.

Thanks Kevin. What I want to do is get the stockish base N7 ROM done then see if there's somebody who wants to take it to the next level and add mods, rom control etc, etc. I know a lot of people like the custom mods, xposed, etc but these days I really don't care for that stuff as long as everything works as it should i'm happy. So if you know of someone who could take on that task once I get the base ROM finished, then that would be great for everyone who wants the custom stuff. And I can take a break. I'll pm some of you once the test build is ready. We'll need to test the basic functions like bluetooth NFC, wifi, etc. It should all work because i've ported these roms before so I know what all i have to do. I'll get the test rom ready as soon as i can as time permits. I'm going over framework getting it debugged and making sure it's a smooth and zippy as i can make it.

tx_dbs_tx said:
Thanks Kevin. What I want to do is get the stockish base N7 ROM done then see if there's somebody who wants to take it to the next level and add mods, rom control etc, etc. I know a lot of people like the custom mods, xposed, etc but these days I really don't care for that stuff as long as everything works as it should i'm happy. So if you know of someone who could take on that task once I get the base ROM finished, then that would be great for everyone who wants the custom stuff. And I can take a break. I'll pm some of you once the test build is ready. We'll need to test the basic functions like bluetooth NFC, wifi, etc. It should all work because i've ported these roms before so I know what all i have to do. I'll get the test rom ready as soon as i can as time permits. I'm going over framework getting it debugged and making sure it's a smooth and zippy as i can make it.
Click to expand...
Click to collapse
I don't use xposed anymore... too much of a hassle to get through some apps that look for it and are diabled from xposed...
Couple brainstorming requests, or something... lol
the people Edge should work properly... I've had so many TW roms that are half done and people Edge is boinked..
Something with note 7 roms and task manager is buggy on note 4...
There is a fingerprint work around for ported roms, if we could get a good, understandable write up to make that work, that would be appreciated.
TW launcher should be themeable... some ports I've tried have that boinked as well.
The brightness on some ports has an issue with not dimming, or high brightness when in sunlight and darkness...
Mostly stock feel and look is quite nice though.

getyroks said:
I don't use xposed anymore... too much of a hassle to get through some apps that look for it and are diabled from xposed...
Couple brainstorming requests, or something... lol
the people Edge should work properly... I've had so many TW roms that are half done and people Edge is boinked..
Something with note 7 roms and task manager is buggy on note 4...
There is a fingerprint work around for ported roms, if we could get a good, understandable write up to make that work, that would be appreciated.
TW launcher should be themeable... some ports I've tried have that boinked as well.
The brightness on some ports has an issue with not dimming, or high brightness when in sunlight and darkness...
Mostly stock feel and look is quite nice though.
Click to expand...
Click to collapse
All of the things you mentioned will be working, except fingerprint scanner. That is a lot harder to pull off and will be the very last thing on the to-do list. If it could be made to work other dev's would have figured it out by now without the N4 settings apk swap trick. But i will definitely try my best to get the fingerprint scanner working with my verizon N7 ROM. With Kevin's custom kernel this will be an amazing ROM for the Verizon N4! It's coming along great. It's raining all day today so i'm inside hammering away on the ROM.

tx_dbs_tx said:
All of the things you mentioned will be working, except fingerprint scanner. That is a lot harder to pull off and will be the very last thing on the to-do list. If it could be made to work other dev's would have figured it out by now without the N4 settings apk swap trick. But i will definitely try my best to get the fingerprint scanner working with my verizon N7 ROM. With Kevin's custom kernel this will be an amazing ROM for the Verizon N4! It's coming along great. It's raining all day today so i'm inside hammering away on the ROM.
Click to expand...
Click to collapse
I kniw it's tricky with the fingerprint, I was just suggesting an easy unified post of HOW to do it on this new rom you're making

getyroks said:
I kniw it's tricky with the fingerprint, I was just suggesting an easy unified post of HOW to do it on this new rom you're making
Click to expand...
Click to collapse
Well it's never been accomplished by anyone as far as I know. I started working on the fingerprint scanner fix for my sprint UN7 ROM but I abandoned it due to the complexity and the time it takes to do it. It wasn't worth the amount of time and work. This is why it hasn't already been done. We'll see how it goes but I seriously doubt fingerprint scanner will be working on initial release. it's probably my biggest negative on running the N7 port ROM. I use fingerprint lockscreen even though it's the swipe method.