[Q] No official CM11 dev for i717...why? - AT&T Samsung Galaxy Note I717

cm is developing cm11 nightlies for old devices such as the Samsung Captivate i897 (captivatemtd) but not for our i717s? what gives?
seriously though, i'd love an informative answer. i can't make sense of it on my own.

The way that I got it was that the folks who WERE doing the CM10.1 stuff started in on 10.2 and then then their test device died.
Since there's no way to test, no more "official" builds.
-blaine

Related

[Q] Noob(ish) question about Android development

I own the AT&T GS2 (i777) and a Captivate. I read a lot of posts about how we can't have a working i777 ICS build because to have one functional, we need either [a] the source for i9100 (or i777 I presume) or a leaked/released firmware from Samsung running ICS.
It sounds totally fair. But then I go to the Captivate forum and there are 2 separate builds in progress with ICS. Having run the builds from teamhacksung I can see how almost everything is functioning without any problems. (Amazing job btw).
So it seems like there is probably one other way of getting everything to work with a new release of Android that doesn't involve the options a and b mentioned above. Can any one enlighten me on what that is?

New ROMs?

Just out of curiosity, is anyone working on a new ROM for out G-tabs. It's been over two months since a truly new one has been posted.I'm not complaining about what has been accomplished. I'm just observing other devices getting fresh builds, enhancements and even ICS for several. Is out device too long in the tooth for consistent updates? I have donated to some developers so I do support all of the great work on this device. I'm just curious. Please don't take offense to my inquiry.
Have you looked at the ICS build for the GTab that Team DRH is piloting over at Slatedroid?
No I haven't. Ill head over and check that out. Thanks!
You should also check out teamdrh.com
Sent from my Desire HD using Tapatalk
What's the status of cm7 and gtab support? I notice they haven't done nightly builds since november for the smb_a1002 device...
When I get some spare time I'll boot up my build vm and try making some new roms based on stock cm7.

Using RomControl from AOKP in cm9?

Hello all,
I've been trying for the longest to port AOKP to Galaxy tab 7 plus, and so far I have gotten nowhere. The devs in our forums aren't interested in porting AOKP to our device. But there is a fully functional cm9 build working. I'm mainly trying to port AOKP for its customization options "RomControl" so is there a way to at least bring the romcontrol menu to a working cm9 rom?
MacZzang said:
Hello all,
I've been trying for the longest to port AOKP to Galaxy tab 7 plus, and so far I have gotten nowhere. The devs in our forums aren't interested in porting AOKP to our device. But there is a fully functional cm9 build working. I'm mainly trying to port AOKP for its customization options "RomControl" so is there a way to at least bring the romcontrol menu to a working cm9 rom?
Click to expand...
Click to collapse
Doubtful, as the RC package relies upon a whole mess of framework and other changes to make it tick. I think you'd be better of picking off the pieces of CM9 that work and bringing those into the AOKP tree rather than going the other way. Figure out what the CM9 build has that your AOKP build doesn't (I imagine largely the device-specific tree) and see if you can bring those items into your build.
Its a driver issue. something is ring with the audio driver. I've tried compiling tens of roms and nothing gets passed the boot screen. I've made lots of logcats and they all came back with the same fatal error with the audio driver I'm guessing?
The problem is I'm not a dev at all.. I'm just following guides I see here on xda or any other forums. But I can't get any kinda real help I've been at this for more than a month and nothing so far. and like I said the devs in our section aren't interested in porting aokp they think cm is better. And there are only two devs we are seriously lacking devs too. That's another problem...

[Q] Which ROMs are still actively updated?

I'm looking for a new ROM that will be relatively trouble-free, but is also actively supported/updated.
I love the UX/features/philosophy of SlimBeam ROM on my Note, but it does suffer from some instabilities.
Unfortunately, SlimBean for the I717 hasn't been updated in ages and is no longer in their list of supported devices. (Is it possible to run ROMs written for the Note N7000 on a Note I717?)
The I717 also does not support the newest version of CyanogenMod.
I've read thru the ROMs in the Development forums, but does anybody have info on which are still active projects and which are dead ends?
Any recommendations (for or against particular roms)?
Thanks.
Go to the AT&T Galaxy Note I717 Android Development section for what you are looking for.
cheshyre said:
I'm looking for a new ROM that will be relatively trouble-free, but is also actively supported/updated.
I love the UX/features/philosophy of SlimBeam ROM on my Note, but it does suffer from some instabilities.
Unfortunately, SlimBean for the I717 hasn't been updated in ages and is no longer in their list of supported devices. (Is it possible to run ROMs written for the Note N7000 on a Note I717?)
The I717 also does not support the newest version of CyanogenMod.
I've read thru the ROMs in the Development forums, but does anybody have info on which are still active projects and which are dead ends?
Any recommendations (for or against particular roms)?
Thanks.
Click to expand...
Click to collapse
i build slim 4.2.2 on a regular basis, your clearly looking at the 4.1.2 version in original development
all the releases i put out see regular updates actually, slim/pk/chamelon/supernexus ect..
edit: and your looking at the wrong place for cm, quincyatt is very well up in the mix with the newest cm releases, get.cm <-- thats where you find the releases
Anytime you choose a "custom" rom there's going to be bugs, or glitches, or random reboots in my opinion. But you're also going to get cool features! You'll have the ability to customize you phone more with custom roms. So it's a trade off. Only you can decide what you can live with and without. If you're looking for custom roms the dev usually updates the title with the last time he updated it. You can then read over the first post and find out what's included feature wise. Very very rarely will you find a complete list of bugs the rom has. You have to surf thru posts to see complaints, and kudos. If you're looking for stability, the i717 got an 4.1.2 JB update a week or so ago. It's the most stable thing out in my opinion. You can give it root access, debloat it, and enjoy a smooth rom if that's what you're after.
Oh and its not possible to run N7000 roms as far as I know. I'm pretty sure you'll brick your device.
I hope that info helps ya out a lil.
JamieD81 said:
i build slim 4.2.2 on a regular basis, your clearly looking at the 4.1.2 version in original development
all the releases i put out see regular updates actually, slim/pk/chamelon/supernexus ect..
Click to expand...
Click to collapse
Thanks.
I'm still on Slim-i717-3.1.0-OFFICIAL.
Do you know if 4.2.1 stable 1.0 is available anywhere for the I717?
And how stable are the 4.2.2 builds? (I've spent enough years in sw development to be cautious - Mark Twain once wrote "People who love sausage and respect the law should never watch either one being made," and the same definitely applies to software)
In my opinion the 4.2 based custom ROMs are way my stable then the 4.1.2 based ( the exception is 4.1.2 based stock ROMs) used to get a reboot every couple hours . 4.2 rarely do I see one. If you are looking for stable but don't really care about all the frills try Jamie's super nexus the first build is bullet proof pure asop like your phone is a nexus doesn't see a lot of updates but its stable.
Sent from my SAMSUNG-SGH-I717 using xda premium

The Future ROMS of our phone....Question...

As soon as the at&t 4.1.2 jelly bean update was available i had it flashed, and for the most part, im happy, not as snappy as the 4.2.2 rom releases but HDMI out works on it along with the other bells and whistles.... what i was wondering was when do we start seeing roms that are based on that att release...is it the source code that the devs are waiting on? Just curious......the devs do an amazing job, its unreal...i give them so much credit..
here's one...
So we're starting to see already.....
I'm hoping AOSP based roms actually start taking advantage of our 4.1.2 kernel soon. Granted, CM merged some stuff from it, but from what I read in the CM nightly thread, they'd have been better off with the blobs and bases they were using rather than trying to merge all the skyrocket stuff. Perhaps they think more longterm than I, though.

Categories

Resources