I'm one. As for any aosp ROM you can use the sprint code base to build from and we just need to switch to our APN and maybe look through the framework where it sets the mmscurl and change it to virgins so MMS will work without having to edit it manually after flashing.
Right now I'm working on getting my kernel source patched up to the latest 3.0.x source and I'm gonna start adding features from the siyahkernel.
But all the aosp based sprint ROMs should work with a little tweaking. And if we fork their s out race code and make the few edits for it to work on vm , it will make it super easy to stay current with the latest releases!
One thing to remember about this phone is it is hardware speaking identical to the sprint epic 4g touch and boost sgs2.
The only difference is on the software side. On stock Samsung based ROMs there are slight differences in the framework and some of the system apps dealing with activation and voicemail and if course the sprint apps as opposed to the VM added apps. And then of course the APN and mmsc URL are different.
On aosp ROMs the only issues would be with the APN and MMS settings as it is aosp based and not tainted by sprint or Samsung.
So fotunatly a lot of development work has already been done and adapting that work to the few changes needing to be made for virgin mobile won't be to difficult.
So then porting over roms shouldn't be to hard then. Wouldn't say Paranoid Android port over with editing the build prop & a few other minimal changes ?
Good luck can't want to see what you guys can do maybe you two can port over kobridges fL 16 stock jb Rom next works good the way it is so fare but still waiting for something to fail.
I'm not a dev but I'd love to help in anyway possible, I'd also like to learn how to build ROM's and port them. This phone is amazing and I know we can get some badass things going on for it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.