[DEV][Discussion] CM10.1 "hackfest"-like ROM sources

[DEV][Discussion] CM10.1 "hackfest"-like ROM sources - T-Mobile LG G2x

Please do not spam this thread with useless questions, thank you posts etc.
You can use (or create) a thread in the general section for that.
I will subscribe to this thread and have a look every now and then if my assistance is needed - but if this thread gets too cluttered with non-development related crap I'll stop doing so.
I found something nice accidently.
The Motorola Atrix - another T2 phone without an ICS release - got pretty well working CM10 and CM10.1 ROMs (w/o hwa of course).
What they did is similiar to the "hackfest" CM10 by benee (based on arcee's CM9 port), but they worked even further.
Here's the manifest:
https://github.com/epinter/android/tree/cm-10.1-olympus
What needs to get done:
Setting up the P999 device tree according to this repo:
https://github.com/epinter/android_device_motorola_olympus/commits/cm-10.1
The most interesting part in here is the BoardConfig.
The hackfest CM10 P990 repo might help here as well - I don't think the P999 ones still exist.
https://github.com/tonypp/android_device_lge_p990/tree/hackfest_cm10
https://github.com/tonypp/android_device_lge_star-common/tree/hackfest_cm10
The commits just need to get merged into the P999 one (+ the storage paths need to get adapted.
I think Mazout360 has a hackfest kernel repo (which lacks proper commit authorship, but better than nothing).
With this working and some compile fixes you should already get it booting. :good:
Thanks to the Atrix guys it's not too much or too hard work.
Without owning a P999 I won't work on it, this would be too messy. But I will at least follow this thread and see if I can do some quick help.
But if some devs are still interested this is a v ery good starting point.
Note: This is totally unrelated to the work adampk and Mazout are doing to use the P990 ICS release to get CM10/CM10.1 working on the P999.
We're talking about a no-hwa release here, same as hackfest (read: all CM9 / CM10 ROMs with working signal) - but more stable and up-to-date.

tonyp said:
Please do not spam this thread with useless questions, thank you posts etc.
You can use (or create) a thread in the general section for that.
I will subscribe to this thread and have a look every now and then if my assistance is needed - but if this thread gets too cluttered with non-development related crap I'll stop doing so.
I found something nice accidently.
The Motorola Atrix - another T2 phone without an ICS release - got pretty well working CM10 and CM10.1 ROMs (w/o hwa of course).
What they did is similiar to the "hackfest" CM10 by benee (based on arcee's CM9 port), but they worked even further.
Here's the manifest:
https://github.com/epinter/android/tree/cm-10.1-olympus
What needs to get done:
Setting up the P999 device tree according to this repo:
https://github.com/epinter/android_device_motorola_olympus/commits/cm-10.1
The most interesting part in here is the BoardConfig.
The hackfest CM10 P990 repo might help here as well - I don't think the P999 ones still exist.
https://github.com/tonypp/android_device_lge_p990/tree/hackfest_cm10
https://github.com/tonypp/android_device_lge_star-common/tree/hackfest_cm10
The commits just need to get merged into the P999 one (+ the storage paths need to get adapted.
I think Mazeout360 has a hackfest kernel repo (which lacks proper commit authorship, but better than nothing).
With this working and some compile fixes you should already get it booting. :good:
Thanks to the Atrix guys it's not too much or too hard work.
Without owning a P999 I won't work on it, this would be too messy. But I will at least follow this thread and see if I can do some quick help.
But if some devs are still interested this is a v ery good starting point.
Note: This is totally unrelated to the work adampk and Mazeout are doing to use the P990 ICS release to get CM10/CM10.1 working on the P999.
We're talking about a no-hwa release here, same as hackfest (read: all CM9 / CM10 ROMs with working signal) - but more stable and up-to-date.
Click to expand...
Click to collapse
Well, guess I'm on it.
Will try this tomorrow, thanks!
EDIT : After my first try, it didn't compile directly. It seems like they didn't update their specific sources with newer CM changes. I'll work on this

Related

[Froyo][Old Radio] How to run CyanogenMod 6 nightly builds on 32b/32a [Links]

Just so we're clear, I have simply collected some links to help people use the CM6 nightly builds. I had NO part in the creation of this software and I take no credit for it. No one asked me to collect this information, and if anyone has a problem with it being available they can PM me and I'll remove it.
All of this information is present throughout this Cyanogenmod forum thread. I've just brought it together to make sense of it.
NIGHTLY BUILDS ARE PRE-TEST BUILDS AND ARE NOT GUARANTEED TO DO ANYTHING AT ALL, I NOR THE CYANOGENMOD TEAM ARE NOT RESPONSIBLE FOR ANYTHING YOU DO WITH THIS INFO! THIS IS *ONLY* FOR PEOPLE WHO WANT TO TRY AN INCOMPLETE AND UNSTABLE CM6 FROYO ROM.
This is for Dream/Sapphire (Magic) and Old Radio ONLY. Don't flash this sort of thing unless you really know what you're doing.
Since I am just collating the information I probably won't be able to help you troubleshoot. I have flashed the latest nightly myself and it runs, but it's very unstable.
Anyway, long waiver done, here's the info:
The nightly builds can be found here. You'll probably want the latest .zip. These builds are created by the CyanogenMod team, if you want up-to-the-minute news I'd suggest following Cyanogen, Wesgarner, ChrisSoyars, and Koush on twitter.
Early 32A port kernels can be found here. You'll want the .zip that corrosponds to the nightly build you downloaded. These are being developed by bcrook (aka 'bcrook88' on Twitter)
Google Apps can be flashed from this. Not sure where they're from or who made them available. It flashed fine for me, but GMaps FCs whenever it's opened, very unstable. This version of google apps has also been suggested as more complete and better, but I haven't tried it myself.

Very much OT, but are you actually running the SPL 1.76.2007 together with the old radio, as your sig seems to indicate?

I think by old radio, he means the one that comes with dangerSPL, the one ripped from the engineering Magics? (i'm not sure where it came from) rather than that new one that someone found in an HTC rom, and everyone flashed.

Oops, nope my sig is wrong. Should be HBOOT 1.33.2010

Also if you feel like compiling , there is a wiki article here http://wiki.cyanogenmod.com/index.php/Compile_for_dream
Edit: Sorry its only for the dream :-(

Thanks, flashing now. Any update on what works/doesn't work?

I haven't spent much time with it yet, but 3G works. I would imagine Wifi, GPS and Camera are the usual culprits to be broken, but I haven't tried them yet. You can always check the check-ins and bug tracker that the Cyanogenmod team uses to see what they're working on.

decepticon said:
Thanks, flashing now. Any update on what works/doesn't work?
Click to expand...
Click to collapse
Main known issues with nightly builds include GPS/Maps FC, camera and video broken, voice input FC..But speed is insane for pre-test build..Can't wait for CM6

I have a quick question, and it may seem dumb. But im kinda stuck.
I understand how to update the spl to what is required, but where can i get the radio 3.22.23.18 ? i cant seem to find it anywhere and thats the only problem im having.
i can load up this rom and its great, i just dont get a signal lol.
thanks.

I'm not using an unusual radio version or anything. Just use this tool to change your radio (relatively) safely: http://forum.xda-developers.com/showthread.php?t=677045

Couple more things, u can actually flash pershoots 32a .34 kernels on top of this and they run fine. Also if frf83-mdpi apps are giving users issues, ive ported frf91 gapps to mdpi and so far havent heard complaints and im running it as well so it shud b gud.
Link

[Q] ASOP Sidekick 4G ROM?

Am I the only one who is unhappy with the slim pickings of ROMs that are available for the SK4G?
Does anyone know anything about an ASOP ROM?

It's AOSP (Android Open Source Project) and you're not the only one not happy with the current SK4G options. I personally want MIUI or CM7, but seeing as we're currently stuck with Froyo, we'll have to see what the devs can cook up.
Sent from my SGH-T839 using XDA App

For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.

sduvick said:
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
Click to expand...
Click to collapse
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App

ayoteddy said:
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And so anticipation had set in, i can't wait ayoteddy. im very excited. SMX was great, and SMGC was awesome, and now with this? whewwww. think i better go lay down, lol.

I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.

Thank you for joining the Sidekick 4G section , & we welcome you but if you want you could pause the game's for the ROM if anything & Question 1 is a no & Question 2 no cause they have to be compiled with the 2.3 kernel .
- Said by Sduvick
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse

Revolution, thanks for relaying my responses.
jmpz, I tried building the source before, but was unable to build it completely, but that was possibly because of some errors with my dependencies. The kernel compiles fine from source, you just need to pull initramfs, or you can get it from Dr. Honk's github.

Thank you for your answers.
So, can anyone enumerate the list of drivers which we should extract from kernel?
I can name these:
1) Keyboard
2) Mic
3) 2 speakers
4) buttons
5) front camera
6) rear camera
7) trackpoint
8) lcd
9) digitizer
10) 3.5 jack
Please correct me and add missing
If I understanding it rightly the key problem is getting proprietary drivers from the kernel. Right?

nope, the key problem is trying to build the system entirely, without any errors, which may be easier with someone following a stock designed build environment. I don't use Ubuntu which is what has the listed dependencies for every tutorial I can find. You can get the drivers out of Dr. Honk's voodoo kernel ramdisk here: http://forum.xda-developers.com/showthread.php?t=1145139
There shouldn't be any problems if you just set up a build environment following the directions in any of the tutorials, then add the platform from the samsung source.

I'm a linuxoid - so these tutorial are for me. Thank you for the link.
By the way, drivers are in Linux Kernel, so I don't think that I need to use Samsung Platform from the source. Instead I wanna use platform from AOSP or Cyanogen. Correct me if I'm wrong.
I think that grabbing drivers from kernel source from samsung would be enough to build the rom.

jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
I 100% support your efforts. I want Cyanogen on the SK4G badly, but I'm not sure what kind of help a non-programmer like me could do, but do have some experience with flashing phones and such, so if there is anything you need let me know.
If you do get rolling heavily on this, I'd be willing to donate monetarily to your efforts.

If anyone can get CyanogenMod 7 on the Sidekick they would definetely get a donation from me. Id be thrilled. Glad to see its going to be worked on.
Sent from my Sidekick 4G using XDA Premium App!

maybe there's hope after all...

So, on a whim I decided to download and peruse the Update1 ICS sources for the T989. This turned out to be interesting because it seems there are more things in the Update1 sources for the APEX40 architecture than there were in the first T989 ICS sources. There's stuff in there that I had to hack into the original sources (poorly, cuz it didn't work)...
Any other devs take a look at this and try hacking a build out of it?
I might give it a run this weekend. At the very least it's a sign that there's been progress... and it would seem that the samsung devs are also basing the both devices on the same codebase.
That's also a good sign that the JB release will have some support for us as well. The biggest issue would be the cam drivers...

dr4stic said:
So, on a whim I decided to download and peruse the Update1 ICS sources for the T989. This turned out to be interesting because it seems there are more things in the Update1 sources for the APEX40 architecture than there were in the first T989 ICS sources. There's stuff in there that I had to hack into the original sources (poorly, cuz it didn't work)...
Any other devs take a look at this and try hacking a build out of it?
I might give it a run this weekend. At the very least it's a sign that there's been progress... and it would seem that the samsung devs are also basing the both devices on the same codebase.
That's also a good sign that the JB release will have some support for us as well. The biggest issue would be the cam drivers...
Click to expand...
Click to collapse
I'll take a look at it and see if the required drivers are in the kernel. If they are, I think the 989 kernel may boot with the correct kernel settings.
I do have a contact who's been working on the framework for ICS but needs a kernel.

[Q] JB MIUI For Galaxy S 4G

Hey guys, I have been looking for a jb miui ROM for this device and i cant find one, i know there are some ics miui ROMs, but i would really like a jb miui ROM.
There is one for the vibrant, can I use it for my Galaxy s 4G or can anyone port it to our device?
Vibrant MIUI JB ROM:
http://forum.xda-developers.com/showthread.php?t=2289234
Thanks

i'll build it when miui comes out with miui 4.2

airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
Thank you i will be looking forward to it.

Beast said he would do it.
sent from me

that's been in my queue for a while along with aokp aries and paranoid android.

airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2313073

Just because there are some homebrew ports doesn't mean that MIUI is 4.2 yet.
http://en.miui.com/download.html
Official Downloads
Author : MIUI Developer Team
Kernel : Android 4.1
Latest update : 3.6.21
Download : http://www.miui.com/download.html
Language : Chinese and English
Click to expand...
Click to collapse

Why does it matter ? We use unofficial ROMs anyway...
sent from me

That's like saying that since a car, airplane, and weed-whacker all run on gas, you should just put the same stuff in each. Actually, the unofficial ROMS is a more tenuous connection than my gas connection. It's more like saying that since a bullet train, horse, and diesel bus all run on fuel, the fuel which goes into each shouldn't matter. It's all fuel.
Hey, you could (please don't) use an unofficial Vibrant ROM too. That's unofficial. What's the difference? The difference is that it won't work. And might brick your phone. That's bad.
Our only current Aries kernel is 4.2.2 and still has issues. MIUI is still 4.1.2 and would introduce an entirely new set of issues tied into GPS, Bluetooth, and so forth if/when a 4.1.2 Aries kernel was compiled. Does that make it impossible? No. But it means that as the build impetus - when MIUI is 4.2 - has not happened yet... it's not a great use of time yet. Unless one of the devs wants it. In which case, MIUI being not-updated is something they don't need to be hammered over the head with.

http://forum.xda-developers.com/showthread.php?t=2313073
4.2.2?

Port. If YOU see source linked from that page so our devs could actually do something useful to build that...

Hi Theraze
I have to disagree with you.
Port is not a dirty word and most of our ROMs are actually ports and not built from source. Furthermore, MIUI ROM is usually ported and not built from source and only recently did Xiaomi open their sources for the public. Even more than that, both MIUI versions brought to us by Beast were ports from Nexus and not built from source.
Now, regarding the incompatibility between kernel & OS - if it works on Nexus, I assume the adjustments were made, so one can enjoy both 4.2.2 & MIUI benefits. There is no logical reason why it couldn't be ported to our beloved device.
sent from me

I'm not saying it can't be done. I'm saying that our build-from-source dev who asked you to let him know when it hit 4.2 hasn't had his request met.
Does that mean that someone (him or another dev) CAN'T port it? Nope. But it makes it a lot less likely that air can just pull the source in and compile it using the Aries bits if the buildable MIUI is still only 4.1.2 and our Aries is 4.2.2 instead.
Again, I think we're agreeing on the general bits... yes, this is possible. But airfluip1 asked to be notified when buildable MIUI was 4.2.2 and that's when he said he'd build it. Not port it.

I don't care if a ROM is ported or built from source.
I will try to play with porting it myself.

Request for Collaborators: Merging the CM11 ROMs into one "official" one

Hi,
I see at least 3 different CM11 roms based on kitkat:
* http://forum.xda-developers.com/showthread.php?t=2524961 [ROM] CyanogenMod 11.0 | Android 4.4.2 KitKat [KANG] [May-6]+[NIGHTLIES]
* http://forum.xda-developers.com/showthread.php?t=2530073 [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 25, 2014]
* http://forum.xda-developers.com/showthread.php?t=2692278 [UnORom][3.4Kernel] CM-11 Android 4.4.4 [Stable v2.0][29 July][Final]
All more or less unmaintained as far as I can see - please correct me if I'm wrong!
What are the remaining difficulties to get a official CM11 ROM out of these? Then a lot more infrastructure from CM could be used - e.g. development tools, build machines & downloads. If the problem is to get a build machine on which 3-5 persons could would together over the Internet - I'll spend a vserver on my own dedicated server if there is a serious effort to bring up an official CM11 ROM.
If there are rather tiny things I could try(!) to help - I have almost no experience with android system development, but with Linux and development (C, Java, embedded devices,...) in general.
Two links for the rough procedure:
* http://wiki.cyanogenmod.org/w/Doc:_porting_intro - the hard part, but luckily almost done (isn't it?)
* http://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port - the final
Wiki-entry: http://wiki.cyanogenmod.org/w/Pyramid_Info

+1 for uptodate pure CM11 rom for sensation. I hope someone will join to you.

I think Flemmard's variant of CM is ready to be official!

official CM11 to Sensation!!!! We need it

+1

+1 It would be great thing for senny to so see official CM11 because many developers left us.

I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.

scanferr said:
I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.
Click to expand...
Click to collapse
Flemmards CM use KK drivers.

+1 for me too.

It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.

Thats very sad, why they all leaving, i dont understand that. How's Ivanich latest 08/27 rom? Better than Sultan 07/25?
greetz

macicgangsta said:
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.
Click to expand...
Click to collapse
bilal don't support our device anymore.

Inf1n1te said:
...Ideas?
Click to expand...
Click to collapse
The good thing is that all the great developers left us with good ROMs.
I think it is difficult to replace the devs. I can't fix the bugs they didn't fix until now, but I would like to try to keep at least one of the Cyanogenmod ROMs updated with upstream. I think in a month or two I will have time to start with that (if no one else is doing it until then).
@mifritscher: I think the lack of a build (or at least download-) server was a problem for devs here and then. So yes, your offer could be very helpful! Thanks for that!

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
Sensation is a 3 year old device. i think as the devs have moved on to other devices, so should we. though our sensation has a lot of potential, i dont think devs will work on an android L port or making CM11 official. though there is hope with ivanich & bilal_liberty

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
[....]
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
I can give storage space and bandwidth if it's useful, please contact me to discuss the details.

I can build but i dont know how to make a device tree so if someone can do the device trees i can do the builds

I don't know if we have everything working as on stock, also I don't know if the rom would pass cts.
But even if everything works, I don't think there's anyone around who has enough time to maintain an official build.
But at this point there's only one cm which is still updated and that's ivanich's one. Where's the difference in having an official build?

Where to go from here?
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?

cynamun said:
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?
Click to expand...
Click to collapse
Except for official slimkat all available and maintained roms are part of DevB so just click here in forum in the dev:db bar on roms.

Database Info

welcome