I have recreated the romer tool. The purpose of this tool is to replace certain files to make D2 roms work on the droid 2 global. To use simply install my file after installing a droid 2 rom via recovery. This version is designed for ginger-blur based roms such as apex and liberty. Do not flash over aosp roms such as cyanogenmod and liquid. I am currently working on creating a aosp romer tool. Do not use on froyo eaither, as this will temporarily brick your phone. I have tested on both apex and liberty, and sensors,gsm,data, and phone are all working. Please enjoy
Disclaimer: I am not responsible for what you do to your phone. If your phones does not do what you like, becomes 100% useless, or explodes killing your wife and children, it is not my fault. I can garauntee that my file is safe, and works perfectly for what it is designed. Make sure to check before you flash a d2 rom that it does not contain a d2 kernel. This could permanently brick your phone! Just be careful
Download v2.2:
http://dl.dropbox.com/u/46535328/D2G-GingerBlur-Romerv2.2.zip
Thanks:
Thanks goes to fabolous for apex , which is were the majority of the files for my romer comes from.
ChangeLog:
V1.0: original, based off of GRD Rommer.
V2.0:completely remade with no more GRD remains.
V2.1:Liberty tweaks put in build.prop.
V2.2:moto boot logo and boot animation added. I can remove this if it is disliked.
Comments:
Has anyone tested out the aosp romer. I would be happy to fix things or add things as people like. I will gladly update this if anyone wants, I have just been working on other things. I have been taking a look at cm source code, and app development. Also eaither one of these will work on Droid X roms. Haptic feed back will not work though.
P.S. If you download this, and enjoy it, please press the thanks button.
**********************************************************************************************************************
This section is for my romer tool having to do with porting the new 2nd init roms or anything that is based off cyanogenmod 7 or aosp that is originaly designed for the droid 2 or Droid X. I have tested it and can approve that it will work for miui,liquid, and cm. I am not liable if this does anything negative to your phone. To use just flash over an aosp rom for the droid x or droid 2 and enjoy on your global. For now the only thing that does not work is gsm. If i can fix it I certainly will.
Thanks: I thank revnumbers for his cyanogenmod builds, as this is were I took the proprietary files for the d2g from.
Comments:
If any of you want me to add something, or try to fix something, please post and I will see what I can do.
Download/Aosp Romer V1.1:
http://dl.dropbox.com/u/46535328/D2G-Aosp-Romer_V1.1.zip
Thanks:
Thanks goes to RevNumbers for his cyanogenmod 7 build, which is were the majority of the files come from.
Change log:
V1.0: Original, fixes phone,cdma data,keyboard,camera,sensors,etc...
V1.1:Fixes su/root permission error.
Comments:
Don't worry if the phone does not receive signal immediately. It takes it a minute.
I accidently set the permissions for su binary wrong. V1.1 fixes this.
! I would HIGHLY not recomend using anything built of of the D2G's romer !
The reason for that is because that method of porting is considered vastly inferior AND because it had many bugs in it because of it. The romer team from Get R Done also had a lot of strife in it and a lack of knowledge. A straight update of the files will not work well.
It needs redone, not updated.
Thanks for the advice aceoyame . I have tested it, and it works, but I do not know what problems may arise from it. I will work on redoing it
also, if you have the time could you describe the problems into more depth of what is wrong with team get-r-done's flashing process. I am not quite as well educated in the art of writing an updater script as you are I am sure.
Well the biggest issue with a romer vs natively porting is that you have too many files that are for one type of rom vs working for others. The romer will only do Gingerblur based as you have it (that's if sensors and everything else works). It will not do any aosp based roms (liquid, CM, MIUI, etc.) The libs are way too different. If you wanted you could make an AOSP romer and Gingerblur romer. Just pointing out the flaws in it.
Thanks for replying ace. I natively ported liberty on another forum. The reason why I made this is so people can just flash it over any liberty gb rom, instead of me having to make an update for each individual version. I have only tested it on liberty, and on liberty sensors,backlights,gsm,phone,keyboard,and data are all working. I would guess that would apply to any gingerblur based rom. I knew that it would not work on cm,liquid, and miui, and did not really care since thanks to you and other devs we already have those roms made for are phone. This is for those roms that only exist on the d2 and not the d2g
Well grats on fixing the sensors then! Rewriting the romer is something we've been wanting to do but could never get around to it. If it is 100% bug free on liberty than it should work for any gingerblur rom. You got sensors to work which was the big issue with the GRD one then you at least fixed something! I would just test the hell out of it and if it works then you probably hammered out any bugs they had with it. An AOSP one would be nice for the other roms. Feel free to put this on Rootzwiki and the other forums.
Thanks, I will make a asop version when I get the time.
Related
I had hear about cyanogenmod earlier and even tried to install it once when I was a rank noob without much luck. In my recent explorations of kernels and cifs I found myself at the cm site. It seemed pretty organized and I thought it might be interesting to have another go at it. I followed the instructions and installed it and it worked flawlessly. I restored my apps from Titanium backup and I'm up and running. I did some research in our forum and that, combined with some of my own observations, makes me wonder about the relationship between CM and some of the other roms like Vegan Ginger (which I really like) I get the impression that some or even all of our roms here are derivatives of CM that have been tweaked further by our devs. Is this correct? What is the difference between Vegan Ginger for example and CM7? I'm really puzzled because the kernels and the basic look and feel seem very similar. Someone even remarked that all of our roms are derivatives of CM. I'd be interested to know some of the background and the pedigrees of the various roms and their relationship with CM.
Cyanogenmod is one of the more known and talented group of Android ROM developers, developing for many devices and being a large team of dedicated coders, artist, etc...
They have taken the stock AOSP code and have modified, enhanced and added features far beyond the stock code. Most ROMs you see that have these additions are because they are forked from Cyanogenmod's github and then edited to look like their own (different graphic images, different text wording, etc..).
CyanogenMod was also one of the only ROM devs that I know of that got a Cease & Desist letter from Google early on and created the separated config of installing the rom.zip and Gapps.zip (Rom image and Google Apps).
As for how Vegan-Ginger relates...
Project Moving to Gingerbread
January 12, 2011 14 Comments
Just a quick update for everyone so you know where we stand at this point. Because of all the issues I have had trying to reverse engineer fixes into VEGAn, we have decided to move away from the actual VEGA system image. We have decided to move the project to a MODIFIED CyanogenMod 7 (aka Gingerbread) ROM with “inspiration from VEGA”. This will allow us to not only fix issues more easily but our work would also directly benefit the CM7 camp as well. This would give also give everyone the choice of a completely stock gingerbread like ROM as well.
THERE IS NO ETA AS OF YET FOR A RELEASE. When there is one…. you all will be the first to know! Exciting Times Ahead.
-GoJimi
Extreme GingerNerd
Click to expand...
Click to collapse
A few of Sony Ericsson's newest devices are queued up to get CyanogenMod Custom ROM. Thanks to recent code submitted by Diogo Ferreira, the bits needed to bring my favorite custom ROM to three smartphones in the Xperia family:
- Xperia Play: r.cyanogenmod.com/#change,7126
- Xperia Neo: r.cyanogenmod.com/#change,7128
- Xperia Arc: r.cyanogenmod.com/#change,7127
Currently the code to add these phones to the CyanogenMod family is awaiting approval to be merged into the CyanogenMod repository. Once that's done we can expect nightly builds to follow not long after.
From that point it's just a matter of time before Release Candidates and a Final Build is available.
Source: http://r.cyanogenmod.com/#q,status:open,n,z
Via: http://pocketnow.com/android/sony-xperia-play-neo-and-arch-getting-cyanogenmod-custom-rom
Woohoo! I am getting a bit sick of my SE ROM, I want a Cyanogen!
very nice, i wasn't expecting official nightlies for our play's
Great!!!!!!!!!
Official CM7 on my Xperia Play is Very very Great
Come on!!!!!!!!
I'd like to hear word from the FreeXperia team. Are they maintaining CM7 officially?
At any rate, I already ROM Manager ready for action ^^
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
RacecarBMW said:
This is only for plays that are bootloader unlockable right? Any progress on unlocking the bootloader on simlocked phones?
Click to expand...
Click to collapse
We're making progress on CDMA phones.
The problem is that simlocked phones don't have RCK_H key so there's nothing to crack the unlock key from. But as said, I'll check it, I have some people willing to test.
Looks as though it has now been merged. Really looking forward 2 flashing nightlies. Cyanogen best mod by a looooooonnnnggggg stretch.
And just in time so that Verizon users can join the party
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
deovferreira said:
Hi, I am Diogo Ferreira (submitter of these patches)
I think you'd be happy to know that they are now already merged and in a buildable state with nightlies following soon.
This is not an alternative to FreeXperia work, it is FreeXperia work. We've been all working together to make this happen.
I'd be happy to answer questions you might have.
Click to expand...
Click to collapse
Hi Diogo. Glad to hear from you. Does this mean Xperias will be listed on CM homepage under supported devices, and will get official forum's section?
Given that most of the features worked already in the betas (great job by the FX folks), the main question for the Play resides on the camera. What's the status on that?
And for those people who have ROM Manager Premium, will the nightlies come through it as well?
No ETAS on camera. It will be done when it's done but we're looking into it.
As for nightlies, they should be available soon.
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Mills00013 said:
deovferreira, is the team making an official kernel as well to compliment the nightly builds? If we are using ROM Manager, then CWM Recovery is essential, and it would be great to have a kernel that had this built in, like the FreeXperia's team does now.
Also, will the ROM be generic for all users? I had quite a few issues with the radio yesterday on my CDMA Play when I tried FreeXperia's latest build. I just wanted to make sure that builds would support all versions of the play, not just the R800i.
Click to expand...
Click to collapse
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
deovferreira said:
What is on CM today is on par with what we did for FreeXperia, the kernel has a builtin recovery. You'll see instructions on this soon when nightlies start to hit.
Click to expand...
Click to collapse
Awesome. The only reason I asked is because of how its different from other devices. The kernel always has to be flashed with fastboot. So I just didn't know how the updates would work or anything like that. I assume we just flash one to start the process and go downhill from there.
deovferreira said:
As for CDMA, I am not aware what the differences are. I support a CDMA device (desire-cdma) but it is a PITA since I have no real way to test. What would be good is if someone steps up and tried to maintain a play-cdma port, I imagine the differences would be fairly minimal.
Click to expand...
Click to collapse
I agree completely. It appears that the kernel was working fine, there is just something in the CM build that was preventing the radio from working correctly. Logcat was telling me that it detected a CDMA mode and enabled it but then the phone module would crash. It was late when I started looking into it though and didn't do a lot of research, but I imagine that someone has encountered this with a CDMA port from a GSM cousin before. I'll do some more investigation this evening.
The boot will always have to be flashed separately using fastboot due to the way the sony ericsson bootloaders transforms the boot image on flashing. System updates will be done using the recovery, as usual. At some point the kernel and system may get out of sync, the symptom would be wifi failing to enable, at which point people would have to flash a new kernel.
As for CDMA, the RIL libraries should be different as should some settings in build.prop.
Awesome. I'll see what I can do this evening, and maybe even pump out a working build from the source for CDMA users.
Guys, stay calm.
this is FreeXperia CM7 "just" as official CM
So that is what you all wanted.
We worked over some time now with Diogo, all of us 3 ( Diogo, jerpela and me) have commited our changes, put them together and worked together.
All will be good See it as a surprise
I'm working for over 1 month now everyday on camera support. For now nothing new, but new knowledge
currently i'm looking into camera for new 4.x Firmware release, maybe SE changed something in a good way for us...
Best Regards
Bin4ry
Team FreeXperia
Ok I just read the thread and maybe I missed it, my xperia play is from Rogers. Will I be able to install cm 7?
Sent from my Play, with XDA Premium.
As of 8/25/12, this project is officially discontinued. All information below is for archival purposes only and will not be supported henceforth.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
INTRODUCTION
Now that Fattire has lifted his request that everyone build their own zips, I've decided to make available the nightly builds I've been generating. I've got an OS X system cranking out a new build every night at midnight, so there will always be an up to date zip available!
Credit for this rom goes to Fattire, Dalingrin, keyodi, nemith, arcee and the the other hard working people over in the development thread, as well as the the CyanogenMod developers and anyone who's done work on the Nook Color. I wish I could list everyone by name but there's so many great people who've made contributions I can't even begin to do so. I'm just building zips from the source; we'd be nowhere without the contributions these great developers have made to this community.
As nighty builds, these zips may not always work. I'll try to remove any zip found to be broken, but you know the drill: All files provided here are to be installed at your own risk. I'm making built zips available, but no warranty is expressed or implied by the hosting of said zips. I'll provide what support I'm able to, but that doesn't mean that there aren't potentially unknown bugs. If you have questions, you should check the development thread or try the #NookColor IRC channnel on irc.freenode.net.
As posted by Fattire slightly further down, anyone feeling adventurous should definitely consider building from source rather than downloading the built zips. Here's his two cents:
fattire said:
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
Click to expand...
Click to collapse
However, if you're not quite sold on setting up a development environment but you still want to try the goodness that is Ice Cream Sandwich, proceeed on down to the...
DOWNLOADS
Without further ado: The Ice Cream Sandwich zips!
Ice Cream Sandwich Nightly Builds.
The rom does not include the google apps, so you can/should flash the lastest version of those, which is available here.
Finally, I've hosted a few flashable zip files to make small tweaks to the rom. These are all located in the misc. folder on my server. Below is an explanation of each zip and its purpose.
MISC FOLDER INFO
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Secondly, if you prefer the old bootanimation from the galaxy nexus, you can also flash the fix-bootanimation.zip located in the Misc. folder, which replace the new CM9 animation it with Homer_S_xda's fixed version. Thanks to Homer for the fix!
NOTES ON INSTALLING TO SD
I've fixed Verygreen's sd installer image to work with ICS -- you should no longer have to flash SP1 first, or rename the gapps to gapps-gb. If you test out this image, please let me know how it works for you! More recently, Leapinlar has stepped up in helping to fix the image further, increasing its size to allow for the larger size of the new nightlies. Thanks to him for his help -- It's available for download here. Huge thanks to Verygreen for helping me to figure out what needed to be fixed -- in the words of HacDan, "He's not just super helpful, he's a genius". Once you've got the new image, you can use Verygreen's original instructions from his thread on SD Installs, replacing "cm7" with "cm9" where necessary.
IN CONCLUSION
Please remember to thank the developers working on this project, as they've done seriously awesome things for us in an amazingly short amount of time. If you have questions/comments specifically regarding my zips, please post them here, but if you have more general questions regarding Ice Cream Sandwich on the NC you may want to head on over to the development thread. Finally, if you're really enjoying the rom I'd strongly recommend that you try setting up a build environment and building your own zips -- even though I'm making prebuilt ones available they're no substitute for the experience gained by getting familiar with the build process yourself, and Fattire has done a great job of making it an extremely accessible and rewarding project.
Thank you!!!!
What bugs can we expect as far YouTube, flash player. Boot loop . A breakdown of what to expect and not to expect. I don't expect anything but like to know for flashing
And you can build too!
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
So awesome!
Youtube missing in latest gapps ?
I installed the latest nightly with the gapps and found youtube app is missing ?
Thanks for sharing! I love nook color devs community! You did an awesome job!
Brilliant work! I upgraded from CM7 and all my existing apps that ive checked worked no problem, it kept all my settings too! Speed-wise I would say its very close to CM7, i use ADW EX in preference to trebuchet, and it just flies!
One thing ive noticed is that NFS shift doesnt behave properly when using the tilt sensor to steer, its axis sensor wants the tablet to be in portrait orientation when the screen is in landscape. Hard to know if its the games fault or the sensor. If thats all there is to complain about this early in the development then the future looks promising
rajazeeshan said:
I installed the latest nightly with the gapps and found youtube app is missing ?
Click to expand...
Click to collapse
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Dual boot ?
I currently have a dual boot environment setup so I can boot into stock (primary boot partition is currently CM7). Does anyone know if this still supports that ? Anything specific I'd have to do with the install then ?
TIA
Thanks a bunch for hosting these nightlies.....let the fun begin!
I just want to point out for the sd-card users using verigreens 1.3 boot image to setup cm7 to run off of sd card and retain stock for various reasons.
That process will also work for ICS/cm9. Currently, you need to flash update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip first. It's found in the ics/cm9 dev. thread: http://forum.xda-developers.com/showthread.php?t=1370873
Then, flash Samiam's nightly builds otherwise you will get stuck in a boot loop right now.
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
I'm gonna stay on cm7 for a while. But I love the progress were seeing with ics.. thanks guys
pavlos46 said:
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
Click to expand...
Click to collapse
What version of the gapps did you have where the wifi location worked? If you link me to that I can see if there's something missing from my gapps zip.
YouTube is incompatible from the market. Actually, it appears any device I have that runs ICS is listed as incompatible.
youtube app missing in gapps
Samiam303 said:
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Click to expand...
Click to collapse
Unfortunately thats not the case when I search market it doesn't list YouTube app and when I
Google it takes me to mobile YouTube app in market that is not compatible with this device.
I salute you all dev. gurus.
Hat off and thanks for the ICS
Awesome thanks so much!
Hey,
awesome awesome work, thank you very much!
I have a slight problem with the GApps, though: I came from update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs and just updated over that with some ics-apps installed. Unfortunately, I do not remember which ones.
Now after the update all my apps are there, but the home screen wiped (not so bad), but my Google Account vanished and I cannot add a new one. Neither in the Settings, nor by opening GMail, Talk, whatever. These will just crash.
Any suggestions?
Thanks again for all your work and energy, I really appreciate that.
Greetz,
Felix
ZenoGia said:
Awesome thanks so much!
Click to expand...
Click to collapse
+1 .
THIS THREAD IS DEPRECATED.
This project has move down, out of the alpha stage, to here:
http://forum.xda-developers.com/showthread.php?t=1950453
This thread is here for documentation purposes only! There are better builds at the new link, more detailed instructions, and support. Please direct your attention there! Thank you.
Warning! Flashing this may/will delete your /efs, which will causes major issues if you ever decide to return back to stock, so make sure you make a backup! If you don't know how, frankly you shouldn't flash this, as you need at least some experience just in case something goes wrong.
Team SuperNOva:
Oisis (helped us get over the final issue)
Zaclimon (first kernel dev, did a LOT of the preliminary work)
Neyodmium (helped us sort out that SGS sources that CAN be used for the 4.0, and helped pinpoint what needed to be replaced/fixed)
Me, hanthesolo (Rom dev, I will be providing updates, support, and other smaller things, so they can concentrate on the kernel, while I fix up the ROM)
The Back Story:
Firstly, excuse my cheesy biblical writing, I just have always wanted to write something in that format .
In the beginning (march 2012), there was hanthesolo. He saw the Galaxy Player forums, and all that he saw was good. This man started creating new work for the Gplayer forums, a and gained a small following. There was just one issue that concerned him: NO ICS!
In light of this, this man created a thread, to collect all ICS development, into one easy-to-read forum. Other began to follow him, zaclimon, Ijimaniac, and several others. Ideas flew fast and furious, but hope was waning quickly. A kernel would have to be created from scratch, a monumental task that had not been undertaken by any man so far.
All was quiet for awhile, and people began to slowly fade out, until only hanthesolo and zaclimon remained, slowly trading ideas and guesses over several weeks. Then a new disciple arrived: neyodmium. This korean (?) developer brought a different kind of kernel experience to the trio, and development began in earnest, with zaclimon and neyodmium trading work, while hanthesolo contributed where he could. One unsurmountable issue arose: this magnificient kernel, the likes of which had never lit up these forums before, would merely boot into recovery, not into Android.
Then Oisis came around, hearing our desperate cries for help. Like a moses, he guided his flock in the right direction, squashing issue after issue, until a monumental day arrived: August 13, 2012. On this day, ICS was finally created in Cyanogen's own image, and it was good.
Then increased development began, with hanthesolo squashing CM9 bugs, while zaclimon, neyodmium, and Oisis working feverishly on the kernel.
But an issue occurred, a wrench in the works. Thine enemy's name is GL, SuperNOva. GL would not cooperate, acting as a barrier between usable ICS, and frustrated efforts to fix it. But one day, the magical variable was flipped, and the builds booted! About this time there was a github mishap involving a bad I9000 push that stopped things for about a week, but that's another story.
What happens next? I dunno, but I will update this story when it happens .
NOTE: This does NOT represent anyone's political or religious standpoint, or the way anyone is viewed. It was created as a humorous way to explain our situation to users.
The fix list:
ROM:
Bluetooth (should be easy)
HW acceleration (easy, just neds to be implemented)
Camera (will take awhile)
Kernel:
HW acceleration (Oisis is working on it)
Drm manager (needs to be fixed before market can be used!)
US home button
Boot to recovery (very annoying when trying to flash builds)
Camera (?)
Changelog:
Build#1:
Initial release, basically everything is broken.
Build#2 changelog:
Finally fixed bootlooping that was plaguing our github
fixed ALL GL crashing and oddness
Fixed/improved sound (if it was broken)
Fixed Browser (slow, but usable)
Waiting on a new kernel to readd GL and/or HW acceleration.
FM radio! Just download the spirit FM app, you can find it for free on XDA
Build#3 changelog:
Fixed av codecs (videos should play just fine now, as well as youtube)
General code cleanup and optimizations
Build #3.5:
Performance improvements and some code cleanup.
Download links:
Build#1:
CM9: http://www.broken-arrow.pl/oisis/aokp/YPG1-CM9-OiSiS-build-02.zip
Kernel: http://zhshibenzhu.host22.com/tuchuang/cm9_kernel.tar
Build#2:
CM9: http://www.mediafire.com/download.php?lu33uubm6der2j9
Kernel: Flash the one above.
Build#3:
http://www.mediafire.com/download.php?96yk0e3y8cqzj1b
New kernel: http://forum.xda-developers.com/attachment.php?attachmentid=1298676&d=1346633739
Build #3.5: http://www.mediafire.com/download.php?oscyfde4w364dj6
Install instructions:
Special thanks to daniel644 for the video and his high praises of me .
If you get stuck in recovery, flash a GB kernel, it will boot into recovery, simply hit "reboot". When it bootloops, boot into download and flash the CM9 kernel.
Resources:
Manifest.xml (so you can just simple "repo sync" instead of git pulling every time we have a new commit):http://forum.xda-developers.com/attachment.php?attachmentid=1278615&d=1345762041
Wiki link (please help improve it!): http://forum.xda-developers.com/wiki/YP-G1
Github repo: https://github.com/TeamSupernovaSGP
NOTE: this is just the modded files. You need to full CM9 source before you can compile!
Contact us at: [email protected]
Please only emails us with valid questions or useful support!
port kernel 3.x from Galaxy S to SGP4.0 should be easy, coz hardware parts are almost the same, but SGP5.0 conpoments arent the same, the way for SGP5.0's 3.x kernel should be harder.
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Would it not be easier to port over a rom, as the hardware is the same? It would at least be more helpful, because if we could create a guide, we could port other roms over very quickly!
Sent From my Galaxy Player running StratusRom using XDA
klin1344 said:
tdmcode actually has a booting CM9 build. I believe that wifi and sound work, but nothing else. His vendor tree and device tree are here:
https://github.com/tdm/android_vendor_samsung_ypg1/tree/ics-cm
https://github.com/tdm/android_device_samsung_ypg1/tree/ics-cm
He just never released it as it is still not very functional.
Maybe it would be easier to just take his source and try and fix the issues and make it fully working. Because getting an AOSP bringup to boot is most of the work; the rest should be easier to do.
Click to expand...
Click to collapse
I built it and I will test to see if it works (I'll use the newest kernel from cm7)
I am going out on a limb here...could we use the cm7 kerbel to help port a workable ics kernel for a galaxy s port? Once thats done cooking up a working rom should be easy and quick.
Sent From my Galaxy Player running StratusRom using XDA
One thing
Ambitious project hanthesolo
one thing: could i suggest that the title of this thread should be Operation: ICS for Galaxy Player 4.0 or something?
Okay, I may rename it. ICS is far more feasible than you think. Once we get a working kernel running (which will be soon) we can port ics over from the galaxy s (which would be best, as once it boots most features would work). I hope by the time school starts up ics will be functional as a daily driver. I may not be able to help a ton, as most of this revolves around making a working kernel, but I will try to help where I can.
Sent From my Galaxy Player running StratusRom using XDA
I can't get it to boot. (stuck at samsung logo) I think it would be better to build it from source instead of porting over.
Its stuck at the samsung logo because the kernel probably didnt work. It has happened to me before, we need to compile an ics kernel. The galaxy s one almost works, we just need to find out what makes it fail to boot.
Sent From my Galaxy Player running StratusRom using XDA
We can use the BML/STL partition layout in waiting for yaffs2. We can use entrophy's device tree as base for it(we can ask for help from him too)
https://github.com/Entropy512/android_device_samsung_infuse4g
Thanks for looking into that zaclimon! I will pm him and see if he would be interested. I willxupdate the opxwoth info from various people/sies as I get it.
Sent From my Galaxy Player running StratusRom using XDA
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
rozelle25 said:
Would a tablet kernel made from scratch to run ICS do anything or does it need to be more kosher with Samsung and their device tree?
Click to expand...
Click to collapse
I dont quite understand what you mean. Can you elaborate please?
Sent From my Galaxy Player running StratusRom using XDA
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
minipot said:
Hey I've been looking at this situation too and science coming back after q long time in the Xperia play forum I decided I wanted to help I found this guide about compelling ics http://www.freeyourandroid.com/guide/compile-ics but 1 problem I need to find the device and vendor tree on github but I've never used githubn before so need some help with that so if I can help please let me know
Click to expand...
Click to collapse
If it was that easy, webwould have ics today on our devices. The reason its been so difficult is that we need to combine/port githubs to create a working kerbel, which is a lot harder than it sounds. Thanks for the link! I will put it in the op.
Sent From my Galaxy Player running StratusRom using XDA
Im guessing u mean we could make a rom using that but first we need a kernel that qill work with it
Yeah. Porting a rom is easy, but getting a working kernel is not. Once we get a working kernel we can port as many roms as we please.
Sent From my Galaxy Player running StratusRom using XDA
Well I don't think it is that hard if we base ourselves from other devices trees like entrophy's one. I think he removed RFS from his initramfs which leaves him only ext4. Then he used a script that would convert the partitions to ext4 when installing CM9. I think it is the same things than with the mmc partitions (I think this is a part of why the 5.0 got ICS sonner than 4.0)
EDIT: And I think it's better to build it from source the first time. (instead of porting for the case of CM9 for example.)
Yeah, I was just talking comparatively. Has anyone begun working on this yet? I have been researching a LOT (the best thing I can do to help right now), but since my knowledge is limited on kernels, i cant help with that riht now
Sent From my Galaxy Player running StratusRom using XDA
So it has been a long time in the works and feels like have been working on this forever. First it was an AOSP Rom, then Caf and at some point both. For now the Rom is AOSP 5.1.1 based.
Is still not 100% but have decided to just go ahead and post the Rom and improve and update.
If you have seen the Test Flight CM based version that had been posted with the Starship Kernel the overall theme is pretty much the same.
The mission now is to first go over a few parts of the theme that bug me or did not translate well in the CM to AOSP Transition such as lightening up some text so is easier to read with darker backgrounds. Second mission is go over every APK one by one and fine tune the theme and add in any extra features. Will post an update as each APK has been completed. Most of the work is done in some form or another but have spent ages nitpicking everything to death and have an external drive filled with already completed images, Colour XML's and lots of uncommitted features so updates will come rather quickly. Honestly at this point am just going to start with the APK's in Alphabetical order so if you like the Rom and theme but a few particular things bug you just let me know and I will not mind jumping ahead. Also with each Rom update not only expect app and theme improvements but kernel and other system enhancements as most are already lined up and just need to be tested in the Rom's new incarnation. It has probably seen some better days but with my constant picking and changing have gone back and forth with so many things I think its best to just post so Starship is out there and now start finalizing. What is currently posted is bare bones themed and featuring a Kernel I have also spent almost a year working on. If you had used the Kit-Kat version of Starship then already know how fast the Rom will be improved and updated based on legitimate feedback. I know I am making things out like this is an incomplete Rom but have been using and been very happy with what is posted as my daily. Yes still need to improve a few things but the truth is I am never happy with anything I do and would have kept changing direction until Android N.
Until next time keep looking up!!
Installing
This version was not compiled using the new block based zip format so will take a bit longer when flashing the Rom. Just a warning for anyone who may think something is wrong. It Just takes a minute longer to flash.
Otherwise besides first performing the usual Wipe of Caches, System and Data also recommend flashing the Rom first, Gapps second and SuperSU last.
Downloads
Starship Rom
https://www.androidfilehost.com/?fid=24052804347762130
G-Apps
I recommend using the Banks 5.21.15 version of Gapps and have posted a link below. I don’t like reposting someone else’s work but just now discovered the 6.17.15 version seems glichy during the set-up wizard sometimes needing to be in landscape mode when making a selection so have reposted the version used during testing. Have also posted a link to the 6.17.15 version but found for example during the restore option selecting done will only register the selection in landscape mode.
BaNkS-dynamic-gapps-L-5-21-15
https://www.androidfilehost.com/?fid=24052804347762124
BaNkS-dynamic-gapps-L-6-17-15
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
SuperSU
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Kernel
I will continue keeping a separate thread for Starship Kernels that may update faster than the Rom so can keep a look out here.
http://forum.xda-developers.com/goo...t/kernel-starship-kernels-01-08-2014-t2997470
In staying with the Rules will find Source for the Kernel that is included here
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Starship Github
https://github.com/Starship-Android
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Screen Shots