Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
MacZzang said:
Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
Click to expand...
Click to collapse
There are a lot of useful porting guides on the Chef Central sub forum on XDA. There's bound to be an AOKP guide there somewhere. Shouldn't be too hard considering we have CM9 mostly working thanks to locerra and aorth.
Sent from my SPH-L710 using xda premium
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
MacZzang said:
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
Click to expand...
Click to collapse
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Ceelos09 said:
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
MacZzang said:
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
Click to expand...
Click to collapse
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Ceelos09 said:
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Click to expand...
Click to collapse
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
MacZzang said:
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
Click to expand...
Click to collapse
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Ceelos09 said:
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
MacZzang said:
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
Click to expand...
Click to collapse
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what I got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Ceelos09 said:
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what u got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
MacZzang said:
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
Click to expand...
Click to collapse
You might wanna port mainly from the Galaxy S2, seeing as how we have more in common with them hardware wise.
And no. I'm about to start my college classes next month at DeVry. Gonna do their Computer Engineering course. I don't know much but as soon as class kicks in, I'm hoping it'll kick start my development here on XDA. For the time being, I usually lurk around n help. Maybe learn a thing or two by reading a random thread or guide.
Sent from my SPH-L710 using xda premium
Well things don't look so good from my end... I've put together about 16 different roms and they all won't go past the boot screen. And the galaxy s2 roms kept giving me the same fatal error... I'm hitting a wall here I don't know what to do.. I'm guessing we just have to get our hands dirty with this one.. I'm doing some reading on python and c hopefully I can figure this out...
So ur a student? That's cool I wanted to learn program and computer engineering before I got into university
Sweet God Almighty, if we got AOKP on this thing I... I... well... I think I might just cry for joy. :crying:
Hahahaha yeah same here I love AOKP based roms, they have more options! And aokp has a unicorn! But sadly we have been trying here for a few days and well I'm not really a Dec I'm just following porting guides and tutorials around xda trying out different things here and there hoping we can get passed the boot screen. Would definitely appreciate your help
Been having some trouble setting my build environment up, so I'm currently seeking some help from others who have experience building AOKP from source. Hopefully they can guide me through it and I find what I did wrong
Sent from my SPH-L710 using xda premium
AOKP == CM
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Aorth u broke my heart man I actually had lots of hope that this can be pulled off... so you're saying this is impossible to do? I like aokp because if the rom control menu I feel it has more options and customization. But cm9 is great too. Thank you so much for all the hard work u have put into bringing cm9 to our awesome tabs
Ceelos09 said:
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah I saw the Yamaha audio thingie too...? What's the problem? Is that a driver thing or something else? From the way you both mentioned it I'm guessing its something serious.. ?
Sent from my GT-P6200 using xda premium
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Curious, what can CM do feature wise that AOKP can't?
I can think of quite a few that AOKP can do that CM can't.
Posted from my Galaxy S III.
Related
This thread is no longer active. Jomeister plans to continue work on Evervolv. He will open a new thread for that purpose.
Introduction
The purpose of this thread is to coordinate work on the AOSP-based Evervolv 2.2 ROM for Skyrocket (and its sister, T989).
Skyrocket is not an officially supported ROM by Evervolv, but we have fully integrated device and vendor directories in their tree. Therefore we get fixes from the main tree and also have the ability to push fixes to Evervolv's tree. This is something we could never do when we worked directly off the Code Aurora source.
Our desire is to give the dev community a single codebase to coalesce around. Hopefully, with more devs working on the same project, we can progress faster towards AOSP.
To build, follow the instructions here (choose ev_skyrocket-eng at the lunch menu):
https://github.com/Evervolv/android
Or, the short, short version:
Run "repo status" and make sure you have no local mods.
Run "repo sync" and make sure it completes without error.
Run "rm -rf out" to remove any old compiled stuff
Run ". build/envsetup.sh" to set up your environment
Run "lunch ev_skyrocket-eng" to select the target
Run "make -j4 otapackage" (adjust -j option to match your # of processors)
What works:
2D/3D graphics, hw accel of gui, bluetooth, gps, nfc, wifi, sdcard (int+ext), MTP/PTP over USB
What doesn't work:
audio, calls, camera, cell data, sms, anything else you can think of
Issues are being managed on Github:
https://github.com/Evervolv/android_device_samsung_skyrocket/issues
Want a ROM link?
Then follow the instructions to build a ROM! The point, at this time, is to get devs involved in the process. The ROM is not ready for anyone to try out or use at this point. There are many problems left to solve.
Want to help?
Are you a dev with a Skyrocket and a burning desire to get AOSP for your phone? Please, check out Evervolv and start debugging! The Github Issues link above is a great starting point.
Jomeister and RaverX3X graciously agreed to join forces here. We hope other devs join too!
Current Dev Contributors:
jomeister15
RaverX3X
topprospect
Credit and Thanks:
Xboarder56 for the original Evervolv Skyrocket device tree
romracer for the unsecure mods to the ICS kernel
Changes Log:
04/11/12: Posted succint build instructions
04/11/12: Fixed unstable-ness of GUI (link)
04/06/12: Build now boots on its own boot.img (link)
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
BaconStep said:
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
yes because google has released 4.0.4 sources and ota updates to nexus.
wali01x said:
yes because google has released 4.0.4 sources and ota updates to nexus.
Click to expand...
Click to collapse
Sweet!
Sent from my GT-P7510 using XDA Premium HD app
Looks great, will try building/debugging when I get my Ubuntu box up again!
Sent from my SAMSUNG-SGH-I727 using XDA
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
giant420 said:
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
Click to expand...
Click to collapse
No stupid questions here. A fully compiled ROM like the ICS leak obscures a lot of the details about how to build the ROM from scratch. You have to reverse engineer a lot of what Samsung did to compile AOSP, plus how to avoid pulling in too much Samsung bloat code. Hope that helps.
more or less were going to keep as much samsung out of it as we possibly can . Yes u can kang in stuff from the leak but then that actually causes more issues in the long run then doing it right the first time ;P.
bsbachert said:
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
Click to expand...
Click to collapse
I think we as a community should still continue working on things such as CM9 and AOKP in addition to Evervolv, just to give people as many options as possible. The good thing that Evervolv device trees are very similar to those required by CM9 and AOKP, so with a few hacks here and there I'm sure we can get those building as well. I don't know about the other devs, but I definitely have enough time to collaborate on multiple projects, as long as I'm not the sole carrier.
ur killing me. I finally managed to get media server to stay up for msm8660 audio pulled from the leak with jos isotope a4 with some other libs and bins. acdb pulling audio policy was still a problem though.
This is definitely for the better though. I was uncomfortable with all those Samsung libs bins and blobs, especially after staring at them under IDA. like raver said it woulda been a nightmare later on.
This is great though, everyone on the same pile should make this go a lot faster.
im very excited for this.
What's IDA?
Sent from my SGH-T989 using XDA
Wow. This build is going to b epic! Can't wait guys. Nice work so far
LawStud3nt said:
What's IDA?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Interactive_Disassembler
crazy what u can find in those blobs. helps a lot for debugging though
all I know is I love evervolv on my nexus one its super baller... Thanks to all 3 of you guys
Sent from my SAMSUNG-SGH-I727 using xda premium
Any updates? Got ants in my pants waiting for this one!
softballjunkee13 said:
Any updates? Got ants in my pants waiting for this one!
Click to expand...
Click to collapse
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
topprospect said:
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
OK...enjoy the holiday as well!
Alot of people have been asking me how i ported Slim ICS, soooo...i made a tutorial on how i port AOSP ICS roms...this is a general tutorial that should be just enough to get the port to boot. your port will not be flawless and it will probably have some major bugs that need fixing which are usually fixed by libs.
This should work with all AOSP ICS roms except those formated in a MTD file system (MTD is not supported by the infuse)...but for best compatibilty use a similar phone like the galaxy s...also before porting if you plan on uploading it you must get permission first!!! Dont make the same mistake i made with slim...
http://www.youtube.com/watch?v=loFHhYf0ca4
Guide:
***DISCLAIMER***
i am not responsible to any damdge caused to your phone by following this tutorial, you are doing this at your own risk. Before beginning you can not be afraid to mess with system file, to experiment, to get boot loops or even completely destroy your phone-for the infuse this is highly unlikely
if you fear bootloops or bricking a phone than you should not follow this tutorial
this guide should work for all phones and all AOSP roms, however every rom is different so some may require extra steps which you will be on your own for...this should be enough to get you to boot up though.
***END OF DISCLAIMER***
if you have any questions please feel free to comment bellow, dont message me on youtube i probably wont answer...if you do comment i may or may not help you, but maybe somebody else will. i have a busy life, and am constantly busy with the infuse and can not spend the time to address everyones issues...but by commenting maybe some one will help.
TOOLS/PROGRAMS NEEDED:
1) 7zip or other archive program
2) text editor, for windows i would use notepad++
STEPS:
1) download CM9 for your device or other AOSP based ics rom ***This is your base rom, you will use this to replace files in the rom you want to port***
What ever firmware your base is is the firmware you will be able to port...EX: 4.0.4 base=4.0.4 port
***for this tut i will be using CM9 4.0.4 for the infuse found here: http://forum.xda-developers.com/showthread.php?t=1601844 ***
2) download rom you want ported ***it can be from any phone, but for best compatibilty/least amount of bugs use a rom from a similar device, since i have an infuse i will use a Galaxy S ICS rom"
3) open up the CM9 or whatever base rom you are using with 7zip (dont extract it just view the archive...for 7zip right click rom, go to 7zip option and choose view archive)
4) delete the following folders in the system folder: app, framework, media, and fonts
5) open up the rom you want to port and use the app, framework, media, and fonts folder to replace the ones you just deleted in the cm9 base
6) copy libandroid_runtime.so *located in /system/lib/* from the rom you want to port into the cm9 base (you are replacing the one already in there) keep a copy of the one in CM9...if it doesnt boot up put the CM9 one back in
OPTIONAL/NOT NEEDED to make the rom run
a) go to build.prop and change the name of the rom
b) change the name of the CM9 base zip to whatever you are porting
7) place the rom on your sd card and flash...if you get bootloops do a logcat
If your rom is unresponsive/not working right you may need to replace some stuff in the /system/lib/ with stuff from the rom you are porting (just compare the rom you are porting with cm9 and whenever you see something missing in the CM9 base or dif size switch it over BUT keep a backup of the unresponsive one that booted...this part is all trial and error) i can not help you with this part...you are on your own, but feel free to comment and i may try and help or someone else may try and help
Also logcats will help in diagnosing problems...
please dont pm me for help, comment on this thread and if i have time i will try and help...or someone else will. im really busy, im a junior in highschool, so i have homework monday-friday, not to mention that my 92 year old great aunt is moving in with us as she can no longer take care of her self alone so i will be busy taken her to appointments and what not.
If i could i would help each and every one of you guys...but i just dont have the time to help everyone so if we can restrict the questions and answers to here hopefully we can limit the amount of questions asked.
Saved for Q&As...
just in case...
Thank you very much MG for your hardwork and dedication. This guide will actually help and inspire many of us to bring ICS flavours on Infuse. :thumbup:
Only a HS junior? My god what was I doing when I was your age? Definitely not porting Android roms.
Sent from my Samsung Infuse running AOKP.
i was bumping school to join computer class
ndhanta said:
i was bumping school to join computer class
Click to expand...
Click to collapse
Hmm I believe we were smoking cigs and talking about girls. But then in those days we didn't have computers or cell phones
Rom Aeon v 1.3.1
oldbbman said:
Hmm I believe we were smoking cigs and talking about girls. But then in those days we didn't have computers or cell phones
Rom Aeon v 1.3.1
Click to expand...
Click to collapse
Although oldbbman is more seasoned than me...I do remember those days...now I jjust dip Copenhagen and still talk about the girls...MILFs....
bigjoe2675 said:
Although oldbbman is more seasoned than me...I do remember those days...now I jjust dip Copenhagen and still talk about the girls...MILFs....
Click to expand...
Click to collapse
Lol
Luckily I didn't know then what I know now or I would probably have more kids then I have now.
Now back on topic. Porting ics Tom's is getting bigger on this forum
:thumbup::thumbup::thumbup:
Rom Aeon v 1.3.1
Believe me...for a while I wasn't making the smartest choices...wasn't hanging around the right crowd and was leading my life down the wrong path...doing these ports and developing has helped me turn my life around and make better choices, I love the challange and I lobe figuring things out...always have
Sent from my SGH-I997 using XDA
Btw...you guys should see a new port by me tomorrow...maybe even tonight, and I have received permission this time...
Sent from my SGH-I997 using XDA
ndhanta said:
Thank you very much MG for your hardwork and dedication. This guide will actually help and inspire many of us to bring ICS flavours on Infuse. :thumbup:
Here are steps for port which are with the Youtube video of MG2195. (It also deserves to be here).
TOOLS/PROGRAMS NEEDED:
1) 7zip or other archive program
2) text editor, for windows i would use notepad++
STEPS:
1) download CM9 for your device or other AOSP based ics rom ***This is your base rom, you will use this to replace files in the rom you want to port***
What ever firmware your base is is the firmware you will be able to port...EX: 4.0.4 base=4.0.4 port
***for this tut i will be using CM9 4.0.4 for the infuse found here: http://forum.xda-developers.com/showthread.php?t=1601844 ***
2) download rom you want ported ***it can be from any phone, but for best compatibilty/least amount of bugs use a rom from a similar device, since i have an infuse i will use a Galaxy S ICS rom"
3) open up the CM9 or whatever base rom you are using with 7zip (dont extract it just view the archive...for 7zip right click rom, go to 7zip option and choose view archive)
4) delete the following folders in the system folder: app, framework, media, and fonts
5) open up the rom you want to port and use the app, framework, media, and fonts folder to replace the ones you just deleted in the cm9 base
6) copy libandroid_runtime.so *located in /system/lib/* from the rom you want to port into the cm9 base (you are replacing the one already in there) keep a copy of the one in CM9...if it doesnt boot up put the CM9 one back in
OPTIONAL/NOT NEEDED to make the rom run
a) go to build.prop and change the name of the rom
b) change the name of the CM9 base zip to whatever you are porting
7) place the rom on your sd card and flash...if you get bootloops do a logcat.
If your rom is unresponsive/not working right you may need to replace some stuff in the /system/lib/ with stuff from the rom you are porting (just compare the rom you are porting with cm9 and whenever you see something missing in the CM9 base or dif size switch it over BUT keep a backup of the unresponsive one that booted...this part is all trial and error) i can not help you with this part...you are on your own, but feel free to comment and i may try and help or someone else may try and help
Also logcats will help in diagnosing problems.
Click to expand...
Click to collapse
Your right should be here...I'll add to the op
Sent from my SGH-I997 using XDA
mg2195 said:
Btw...you guys should see a new port by me tomorrow...maybe even tonight, and I have received permission this time...
Sent from my SGH-I997 using XDA
Click to expand...
Click to collapse
Now we can see more and more Android 4.x.x. in the Development section.
Nice work. Thanks for sharing with the community.
Sent from my SGH-I997 using xda premium
mg2195 said:
Alot of people have been asking me how i ported Slim ICS, soooo...i made a tutorial on how i port AOSP ICS roms...this is a general tutorial that should be just enough to get the port to boot. your port will not be flawless and it will probably have some major bugs that need fixing which are usually fixed by libs.
im a junior in highschool, so i have homework monday-friday.
Click to expand...
Click to collapse
Good job..thanks for sharing.
Now I can't say I never learned anything about tech from a high schooler..
Um that is a wise statement
Hey mg. I have your v1.0 slim ics and the ns tools fix. How would i combine them? Thanks in advance
I was going through the files and if I just put the apk in the system/app it would be alright?
isaiahe97 said:
Hey mg. I have your v1.0 slim ics and the ns tools fix. How would i combine them? Thanks in advance
I was going through the files and if I just put the apk in the system/app it would be alright?
Click to expand...
Click to collapse
yep, that would fix it
you may want to warn those about the mtd partition system while porting since i ve ran into several of them
GoSooners345 said:
you may want to warn those about the mtd partition system while porting since i ve ran into several of them
Click to expand...
Click to collapse
Yeah...ive been looking for another rom to port as the one i last did was just discontinued by the original dev, out of the three ive tried so far all have been mtd file system...will add to OP/title that it doesnt work with mtd file systems...
Hi all! This is my first attempt at a rom, so there are definetly going to be bugs.
This rom was ported from the galaxy nexus stock rom
Ill just post the bugs im aware of, and add to the list when people post them.
Bugs:
All bugs in 7/22 cm10 build for infuse 4g
USB mounting isnt working at all
Maybe debugging too
use power control app for widget toggles
First boot will give tts error, just ignore
Flash instructions:
Must be on ICS ROM!
Wipe data/cache
Wipe davlik-cache
Install zip from sdcard
Reboot
Please post any feed back, and again this is my first rom so thanks for trying it out!
Download:
http://www.mediafire.com/?88sb0g4x6umc766
Thanks:
•Scott, Nun, Yuma, JT, Araemo, PoX, Entropy, and everyone else who helped create the cm10 rom I used to port from
•Elitemovil for the gnex rom
•iall5star for porting it to galaxy s
•mg2915 for his tutorial on how to port roms
Yesss more Jelly
slicingtaco said:
Yesss more Jelly
Click to expand...
Click to collapse
Thanks another JB rom..congrats bro..
slicingtaco said:
Yesss more Jelly
Click to expand...
Click to collapse
Never can have to many jelly beans lol.
I'll give it a try and see how it compares to CM10. Might b a few days tho bc I just flashed the new CM10 build and it's running pretty smooth.
Does this have "Project Butter" included?
Sent from my SGH-I997 using xda app-developers app
No it does not have project butter I'm unaware of what that is, but if you know where to point me to I can try and make a version with that included
Sent from my jelly bean infused infuse
Yummy...glad to see more JB roms popping up
Sent from my SGH-I997 using xda premium
vkumar2695 said:
Yummy...glad to see more JB roms popping up
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
You heard the man you can never have to many jelly beans. Lots and lots of treats
Sent from my SAMSUNG-SGH-I997 using xda premium
thanks Mate...i think it will be a Impressive rom...cheer！
okay quick question..... has anyone tried this yet??
if so please post your experience here
no i won try it myself... i have too much customization made to just flash another rom for now
supernewbdev said:
No it does not have project butter I'm unaware of what that is, but if you know where to point me to I can try and make a version with that included
Sent from my jelly bean infused infuse
Click to expand...
Click to collapse
If you just Google "Project Butter", you'll find a ton of links about it. They will prob do a better job explaining than I will but I can try.
From what I understand, project butter was one of the major changes Google made from ics to jb. It is meant to make the phone quicker and more responsive by making some tweaks to GPU rendering I think and some other things. The team that released Cm10 for the infuse tried to include the code but it caused stability issues on our phone. It did make the phone seem "snappier" but it would randomly freeze so they had to remove the code.
I'm sure there is a lot better information to b found on the web.
Sent from my SGH-I997 using xda app-developers app
raghul said:
okay quick question..... has anyone tried this yet??
if so please post your experience here
no i won try it myself... i have too much customization made to just flash another rom for now
Click to expand...
Click to collapse
I just tried to flash it a couple times but couldn't get past the Samsung Logo. I tried once straight from CM10 and then once after first flashing an ics rom to get blue ics recovery.
Could just b user error but I used the same method as I always do. Full wipes then install. Maybe it was a bad download. I didn't do a MD5 check.
Sent from my SGH-I997 using xda app-developers app
benbos_06 said:
I just tried to flash it a couple times but couldn't get past the Samsung Logo. I tried once straight from CM10 and then once after first flashing an ics rom to get blue ics recovery.
Could just b user error but I used the same method as I always do. Full wipes then install. Maybe it was a bad download. I didn't do a MD5 check.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
You're right, I had posted the wrong file for download. Please use the updated link!
Sent from my jelly bean infused infuse
supernewbdev said:
You're right, I had posted the wrong file for download. Please use the updated link!
Sent from my jelly bean infused infuse
Click to expand...
Click to collapse
LMFAO:silly:
Just food for thought... CM10 is still in the early development stages.. Its probably a bad idea to start "porting" other ROMs since the actual files that are MEANT for our phone are still being worked on. For project butter, it involves updating the PVR drivers. JT had ported the code over from the crespo kernel to update the PVR drivers, but something seemed to conflict with it as it had random freeze ups. The reason this hasnt been fixed yet, is it is a HUGE change.. Literally hundreds of lines of kernel codes are changed/removed/added so its not a simply thing to pinpoint. Entropy is taking a look this weekend as he found some things to be a mess.
Also, you might want to give some credit in your OP... ALOT of people including myself worked incredibly hard to bring CM10 to the infuse, so its the least you could do for using it as your base.
First off, congrats on getting the port to work, but I have to agree with pretty much everything Scott said. Unfortunately what you mention trying to accomplish is going to take more than just zipping a few files over the top of an existing ROM.
As a good rule of thumb it is always advisable to get permission from the original source if you are going to use it in your build, and from the sounds of Scott's post this hasn't happened. We all like new things and all are trying to improve or phone experience, but it is important to be respectful of the time and effort of those that have come before.
Food for thought as you continue your endeavors and best of luck to you.
Sent from my SGH-I997 using Tapatalk
scott.hart.bti said:
Just food for thought... CM10 is still in the early development stages.. Its probably a bad idea to start "porting" other ROMs since the actual files that are MEANT for our phone are still being worked on. For project butter, it involves updating the PVR drivers. JT had ported the code over from the crespo kernel to update the PVR drivers, but something seemed to conflict with it as it had random freeze ups. The reason this hasnt been fixed yet, is it is a HUGE change.. Literally hundreds of lines of kernel codes are changed/removed/added so its not a simply thing to pinpoint. Entropy is taking a look this weekend as he found some things to be a mess.
Also, you might want to give some credit in your OP... ALOT of people including myself worked incredibly hard to bring CM10 to the infuse, so its the least you could do for using it as your base.
Click to expand...
Click to collapse
A perfect way to put it you two.
Yuma75 said:
First off, congrats on getting the port to work, but I have to agree with pretty much everything Scott said. Unfortunately what you mention trying to accomplish is going to take more than just zipping a few files over the top of an existing ROM.
As a good rule of thumb it is always advisable to get permission from the original source if you are going to use it in your build, and from the sounds of Scott's post this hasn't happened. We all like new things and all are trying to improve or phone experience, but it is important to be respectful of the time and effort of those that have come before.
Food for thought as you continue your endeavors and best of luck to you.
Sent from my SGH-I997 using Tapatalk
Click to expand...
Click to collapse
Sent from my SGH-I997 using xda app-developers app
scott.hart.bti said:
Just food for thought... CM10 is still in the early development stages.. Its probably a bad idea to start "porting" other ROMs since the actual files that are MEANT for our phone are still being worked on. For project butter, it involves updating the PVR drivers. JT had ported the code over from the crespo kernel to update the PVR drivers, but something seemed to conflict with it as it had random freeze ups. The reason this hasnt been fixed yet, is it is a HUGE change.. Literally hundreds of lines of kernel codes are changed/removed/added so its not a simply thing to pinpoint. Entropy is taking a look this weekend as he found some things to be a mess.
Also, you might want to give some credit in your OP... ALOT of people including myself worked incredibly hard to bring CM10 to the infuse, so its the least you could do for using it as your base.
Click to expand...
Click to collapse
I apologize, like I said this is my first port/ROM. If you could tell me who to give the proper credits to, I will put then in the OP. And thank you for the information about project butter
Sent from my jelly bean infused infuse
Yuma75 said:
First off, congrats on getting the port to work, but I have to agree with pretty much everything Scott said. Unfortunately what you mention trying to accomplish is going to take more than just zipping a few files over the top of an existing ROM.
As a good rule of thumb it is always advisable to get permission from the original source if you are going to use it in your build, and from the sounds of Scott's post this hasn't happened. We all like new things and all are trying to improve or phone experience, but it is important to be respectful of the time and effort of those that have come before.
Food for thought as you continue your endeavors and best of luck to you.
Sent from my SGH-I997 using Tapatalk
Click to expand...
Click to collapse
Yes I know that now, I didn't really know that I should get permission for the cm10 too but I did get it for the ROM I ported. Who else worked on the cm10 ROM with you and Scott?
Sent from my jelly bean infused infuse
supernewbdev said:
I apologize, like I said this is my first port/ROM. If you could tell me who to give the proper credits to, I will put then in the OP. And thank you for the information about project butter
Sent from my jelly bean infused infuse
Click to expand...
Click to collapse
Great Job in getting the Port on it's feet!
edit: Apologize for upsetting those that didn't understand me, or for me not being clear...
I wouldn't mind helping test out at all, send me a PM or just tell me what's up in a post on here.
-U.S Army 18x-
Thanks to the encouragement of blindndumb, I've decided to personally make a cm10 rom too. This CM10 Rom also acts as my base for my PA.
So... Yea. As Usual,
Double Thanks for cnote74 for making the kernel too for me as my computer is the most old fashion one :-/
And also 0.0 for teaching me how to port
And also blindndumb for the camera patch
And also ...Awesome... for the amazing AwesomeBeatsv3
And also hdorius for supporting me all the way till now
And also ParanoidAndroid For even making this rom possible
(YES I LOVE THE 2 WORDS AND ALSO )
Flashing Instructions ( Very Important -> You must be on cm10 )
1. Make Sure You're On The Latest CWM Or 4EXT Recovery
2. Make A Backup
3. Wipe Cache and Dalvik
4. Flash ROM ×Still requesting permission before uploading×
5. Flash Gapps ×http://goo.im/gapps/gapps-jb-20120726-signed.zip×
6. Reboot and Enjoy
When will it be released?
It will be released as soon as i get the permissions from other dev and at the same time thanking blindndumb,hdorius and cnote74 for helping me through this difficult times and making it a big success
Why create this thread if you haven't got the rom to release yet?
Sent from my Desire HD using Tapatalk 2
any new info for this rom camera work ! or camcorder work full on this rom ?
kee going great from you
mrbubba999 said:
Why create this thread if you haven't got the rom to release yet?
Sent from my Desire HD using Tapatalk 2
Click to expand...
Click to collapse
I am able to release it right now just need to get the permissions and the links would be up instant. Camera works but camcorder doesn't work for me.
Camera for non samsung sensor, for dhd with omniVision sensor?
Gradjevinac said:
Camera for non samsung sensor, for dhd with omniVision sensor?
Click to expand...
Click to collapse
Huh? o.o
simahu said:
Huh? o.o
Click to expand...
Click to collapse
Multiple sensor vendors for the Camera exist. Just because it is an HTC phone does not mean you have an HTC camera(omnivision or Samsung) You need to know this stuff man:silly:
I can understand if people want to make there own roms. And i really appreciate it if they share the work with the community. But before you do this, you should learn something about how to do this stuff!
Sent from my Desire HD using xda app-developers app
Sorry but I wont be going anywhere near anything you release and I use that term loosely. You appear to be jumping from one genuine developer's rom's to another trying to cobble up your own rom. Just reading your previous posts clearly shows your technical abilities are rather lacking.
Should maybe also add, non or unofficial CM10 rom as well to the title.
IDK
WR
Stop me if i am wrong... But if you compiled CM10 from source then why do you have to wait for permission???? What CM10 rom are you using as a base then??? Jellytime is the only one i know of to boot and run with CM10, and we all know you will not get permission from Random
Guys,
I have already requested a mod take a look at this. I find it weird that his computer cannot compile a kernel but it can compile a rom. Even on my custom built with a 6 core AMD Phenom with 16 GB of RAM it takes about an hour to an hour and a half to compile from source. That would require at least 2 days time on his machine with a melted core. We will see if this is legit. Let the mods take care of this
menditsa said:
Sorry but I wont be going anywhere near anything you release and I use that term loosely. You appear to be jumping from one genuine developer's rom's to another trying to cobble up your own rom. Just reading your previous posts clearly shows your technical abilities are rather lacking.
Click to expand...
Click to collapse
Let me take a peek at this. He thanked people for compliling the kernel and then thanked multiple other people... so he took a bunch of other peoples work and crunched them into one... something seems alittle fishy is all I say. And yes its pretty clean on my part that he doesn't seem to know what he's doing. (Don't get me wrong I'm no where near being a dev but it just seems like he's trying to make himself popular for making one) idk.That's my input so ill just see where this goes. Goodluck
Sent from my Inspire 4G using xda premium
Thread Closed.
Placeholder threads for "coming soon" ROMs are not allowed. Neither are ROMs that use other peoples work without permission.
Note to OP, I you wish to use randomblame's kernel, compile it yourself, its not that hard and there is nothing in the GPL that prevents you from doing so.
So I found a tool on XDA that allows me to put the ROM of choice to be ported and the base ROM. I'm trying to port Paranoid Android 2.00 since we don't have it, and now that we have somewhat steady CM10 nightlies I *should* be able to use it as a base. (The tool is called RomPorter)
So I went ahead and compiled a ROM, but I'm not sure if I should flash. I mean if it was this easy to port ROM's wouldn't we have ROM's just popping up everywhere? I used the HTC One X International version's PA 2.00 as the input ROM btw. I have some coding experience in Java but if it's this easy to port without any coding required why hasn't it been done yet? Just curious. I looked at the CM9 guide to porting PA and I have to make a linux portal and all those things. Basically my main question is, will this work? I don't want to flash and end up hard bricking my phone. I went and checked the build.prop, and framework and it all seemed like a hybrid of CM10 nightly and Paranoid Android 2.00 but is there something I'm missing?
Thanks a lot guys! I'm tired of just being somebody who stands on the side and waits for things to get ported or created. I'm taking a heavy load in college but I want to try and port something at least to contribute.
Using the international base could cause a brick unless you ported an evita kernel too. The international one x has a different partition layout as well.
Read read read, check, double check and triple check. When your confident its possibly bootable, sure that it is not harmful THEN flash it to your device first. Ports are always going to start with bugs. Don't expect perfection, expect a WIP. Importantly, have fun learning. Most importantly , FIRST FLASH IS ALWAYS YOURS :beer::beer:
Added People port roms all the time for themselves. Now posting one on xda and maintaining a thread with dozens-hundreds of followers is a WHOLE DIFFERENT STORY
I just want to try it but I'm afraid it'll brick. I mean what's the worst case scenario? Boot loop then restore to my nandroid? Or being stuck with a brick forever? I don't have a backup phone at the moment lol. Maybe I should invest in one.
If you flash something that overwrites hboot you're hard bricked. That's what I meant by different partition layout.
Here's a easier start for jb paranoid Android port.....dload the HTC evo 4g lte jb paranoid port rom, unzip it, delete the included boot.img, use a hox boot.img from a hox jb rom to replace it with. Zip it and flash it.(use the one XL cm10 boot.img) It will give u a bootable port of jb paranoid Android. Then like most ports, you will start fixing bugs. Camera and wifi won't work, you will need to fix those for sure. But a lot will work so start with priority bug fix#1 and keep on goin
Added: paranoid android rom I would consider the land of the brave for first time porting. U may encounter fixes to be harder than some less modified roms.
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Shaddy-Z. said:
I understand now what the scare was. But when taking the Evo LTE ROM and pushing our own boot.img it'll allow me to at least get it started to see what I need to get going and fix! That's a fantastic idea. I'm going to head over there now and see what ROM's they have. I mean technically we share very similar devices internally right? I haven't looked into the Evo specs much.
Click to expand...
Click to collapse
make sure you pull out any radio images you find in the roms you look at.
Could I push the ones from a cm10 nightly?
No idea. Probably. Or just don't include one.
getting in contact with the developer for the Evo PA ROM. Hopefully this goes somewhere.
Don't we already have a pa rom? You've inspired me though. I'm going to look at porting roms too.
The PA ROM is still ICS, and the biggest killer is that the multi-touch fix is not incorporated because the ROM was cooked pre kernel release unfortunately. The latest update the dev was supposed to release didn't boot and I don't know what happened after that.
And do it! The more devs the better. I want some variety in this little community.
By the way, PARANOIDANDROID 2.00 is not out yet. The last OFFICIAL release is 1.992: Changelog. As for the port, I would love to port roms to our device, since it is my primary device.
I already port ROMs from the i9100 to i777(SGSII Internation to AT&T US Version), but this is a VERY simple operation. And you can use a pre-made program to port by ktoonsez called Flashaholics, but it is only for porting to the i777. I hope we eventually get that far but these 2 devices are far more similar that the One X/OneXL or Evo LTE/One XL.
Just use the latest paranoid rom with the latest cm10 boot.img. I did it a few times when I had my hox. And gunny is right. Either pull the radio or flash a hox radio after u flash ur port and u will get signal with working talk, text. 3g should work too, mms won't, streaming video will be iffy. Just run thru the major stuff, write down what's broken, prioritize it, then always make a nandroid of your previous build so u can revert back if fixes make things worse
---------- Post added at 01:09 AM ---------- Previous post was at 01:03 AM ----------
He's gonna work off a unofficial paranoidandroid jb 4.1 from the evo lte. It'll boot but there will be plenty of fixing to do. I think its for his use/learning, not sure if he plans on putting it up on forums
I don't plan on uploading it to the forums unless I get the features working. I'm off all day tomorrow so I'll probably give it a shot to see what I can do.
I also realized PA is not 2.00 after I posted that, buts its still a JB Paranoid ROM so it'll do for now while I learn.
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
stnguyen09 said:
It's really good seeing someone (who isn't a regular dev that I know of?) taking such initiative and asking the right questions and such in order to get some dev'ing underway.
Great job! :good:
Click to expand...
Click to collapse
Thanks! I appreciate it So I got a little ahead of myself and tried it tonight, I'm slowly following a guide and I THOUGHT I was doing everything correctly but it won't flash after "Verifying system partition size" and I got an error. This seems to be a common problem that leads to the updater script, so I'm going to take a look at it when I get up. Could just be a syntax error, or maybe I'm just building it wrong I'm kinda tired
U can always nab the updater script from cm10 hox also. Its been a while and I forgot to mention that. I had the same issue with the evo rooms and that did the trick:beer:
I tried: using the ports updater, the base, and a collaboration of the two and it still didn't go through. Maybe its something else ? I'll try it again to double check.