Related
I have finally, successfully, gotten jt1134's device tree and Froyo framework all configured for the Mesmerize. This is a Vanilla Froyo (no Cyanogenmod) build and works enough to play around with (= But, I should warn you, this isn't a terribly stable build, so don't freak out if something acts weird d= Also, I'm not responsible for any harm you may do to your devices..
It's late and I have an 8:00 am tomorrow so I haven't tested everything out yet, but what is working and not working should be similar to what jt1134 has listed over in his Fascinate thread. Here's what I've tried though:
Working:
Phone
SMS
GPS
WiFi
Not Working:
Data?
Bluetooth
Camera
sdcard?
Oh, and it may randomly 'boot loop' a few times.. don't freak out though.
For this to work you need to be using the Mesmerize Froyo kernel I recently posted. To get everything setup just download the ROM and the Kernel and put them on your sdcard. Boot into recovery and make a backup. Wipe your data and cache partition. Flash the ROM. Flash the Kernel. Reboot. Froyo! If you're going to try to adopt this ROM for everyday use (good luck), make sure you grab the GApps package and flash that last.
I haven't got a Mesmerize device tree on github yet, but you can find the alterations to the kernel up. Really, you should look at jt's source/github because that's where all the dirty work is done (= Also, some of his work is under ModADroid on github.
Download Links:
Mesmerize Vanilla Froyo ROM: http://dl.dropbox.com/u/464066/Mesmerize/ROMs/froyo_mesmerize_0122.zip
Mesmerize Froyo Voodoo Kernel: http://dl.dropbox.com/u/464066/Mesmerize/Kernels/0123_mesmerize_voodoo5.zip
I'll post a link to a nonvoodoo kernel when I get one compiled.
Froyo GApps: http://goo-inside.me/google-apps/gapps-hdpi-20101114-signed.zip
Be careful!! This kernel is named the same as jt's Voodoo Sound 2.1 Kernel that he released yesterday. You may want to rename one of the two if you plan on using both. The ROM will bootloop or freeze at the lockscreen if you mistakenly use a 2.1 kernel (=
Source:
http://github.com/jt1134
http://github.com/dcow
Credits:
jt1134 <-- for all the SCH-I500 framework work
punk-kaos <-- for his contributions to the SCH-I500 framework
phidelt82 <-- for keeping me company late at night (not like that.. ..) and for letting me bounce ideas off of him, calling me out when I'm being stupid, and flashing whatever I throw at him (=
Enjoy!
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.
cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
dcow90 said:
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.
Click to expand...
Click to collapse
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.
be glad to help test things once you get a little bit more stable with this.
Sent from my SCH-I500 using Tapatalk
phidelt82 said:
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.
Click to expand...
Click to collapse
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..
dcow90 said:
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..
Click to expand...
Click to collapse
I think it has to do with the mounting. It looked the same as the other init.rc's that I was looking at, but it was all running together at that point last night. I'll dig into it some more tonight and look at the mounting of the base init file and see what I can come up with. Hopefully something will jump out.
Dont pull bin/vold from a prebuilt image, make sure you're building the aosp version. Also, make sure you are pulling prebuilt/vold.fstab from my device repo.
Android uses the vold daemon and fstab files to manage sdcard mounts, not a simple mount command like the ones used in init.rc for other partitions.
Sent from my SCH-I500 using XDA App
Thank you guys for all the hard work!
Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize
co6alt said:
Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize
Click to expand...
Click to collapse
No, you also need to revert to a 2.1 kernel as well. I mean 2.1 will boot on this kernel, but I can't say that it will work perfectly, and I found my scdard still didn't after a restore until I reverted kernels.
So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize
co6alt said:
So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize
Click to expand...
Click to collapse
What you should do is download jt1134's Mesmerize Voodoo5 w/ Voodoo Sound kernel and flash it. You should then take a backup in perfect working order. If you want to play with 2.2, wipe, flash the rom, then kernel. When you're done, wipe, restore the backup, then flash the previous kernel.
Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize
co6alt said:
Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize
Click to expand...
Click to collapse
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=
dcow90 said:
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=
Click to expand...
Click to collapse
Sweet waiting for a few more things to be functioning before I try using it. Thought maybe about trying to tomorrow but only as a test.
Edit: I just flashes the ROM and Kernel last night 0 problems booting and starting up phone was basically functioning then when I installed the Froyo Gapps I couldn't use the phone anymore because no data connection couldn't get passed the google account setup but seemed to work.
The only thing that was weird is before I installed the gapps zip while playing around the phone kept going back to the silver Android logo seeming as if it was restarting and going back to the lock screen but I managed to test the Phone, called 611 got US Cellular so that works!
Thanks again for your work I definitely and looking forward to this.
Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>
Yoder808 said:
Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>
Click to expand...
Click to collapse
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!
bdemartino said:
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!
Click to expand...
Click to collapse
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.
Yoder808 said:
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.
Click to expand...
Click to collapse
Samsung could have rolled out an firmware update but from what I've read they leave it up to the carriers to decide when they roll out updates.. especially OTAs since its on their end. US Cellular does spend a large amount of time testing their phones before releasing anything because their still small business orientated. That said, they easily could have rolled something out for us much earlier than this, as far as the small business goes they could have released it un-supported to commercial users and told business' not to load it yet plus not shipped any phones with it.. at least we'd have the option then..
Sorry if this has been asked, but I checked a lit of the q&a but is there any hope or any developers working on ICS for us? And because I don't know much why is it hard to port to the sgs 4g?
Sent from my SGH-T959V using XDA App
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
OK sorry, like I said I don't know much and just was curious. Thank you for the info tho
Sent from my SGH-T959V using XDA App
tehgyb said:
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
Click to expand...
Click to collapse
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
How about building a Gingerbread Kernel ( CM7 based )
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
mccabet said:
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
Click to expand...
Click to collapse
Oh trust me, devs are looking at cm7. I know I am, like its a big New York steak!
But its going to be a while, unless you can employee me to work on it. Otherwise... Gotta pay the bills before I have fun.
Sent from my SGH-T959V using xda premium
I know that and realize other priorities make everyones time valuable. I am trying to get up to speed and just need a little bit of help getting the base kernel to build. I have successfully built the CM7 in the past for the captivate, but this is the first time for an raw, untouch source release from samsung.
Thanks for your input.
Also, just to note. There are multiple kernel devs here.
Still waiting for drhonk to release some Bali goodness.
My kernel has a different goal and approach from drhonk's. Search the op of my kernel thread for 'plan'.
As usual, all code is GPL and is available on github (see my signature), so if you want to learn or help out, start with the source.
Sent from my SGH-T959V using xda premium
finch8423 said:
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
Click to expand...
Click to collapse
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
krylon360 said:
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
Click to expand...
Click to collapse
Yea, don't sweat this quite yet, Krylon360
I say we work on the cwm that converts to ext4 like epic4g, like you'd suggested in irc. I already have some code and tests in place to convert to mtd. It's just not in any kind of stable/usable/releasable form yet. It's still early code.
When (hopefully soon) I get time, and hopefully an email back from chipworks about some info I need, I'm going to get u-boot rolling. It's hard for me to explain all the benefits of this now, but some snippets:
fastboot mode (say, flash an mtd partition like: fastboot flash <partition name> <file>)
android usb gadget support (adbd) in u-boot (say to have early console access at the bootloader), and plenty of other goodies.
many other things I just don't have time to list, on top of the fact that we can now control the bootloader...
doing the auto conversion is cake. it's just a bit inside init.rc that tells it to run a script in /sbin, that script is just a quick conversion to ext4. as long as /system, /data, and /cache have the ext4 mounting bit in init.rc, and the ext4.ko is in /lib/modules, it should would just fine.
I'll get the script while Im at work tomorrow.
Krylon360,
you mentioned the initramfs being combined with the zimage. Can you shed some light on how this is done?
bhundven,
Thank you for your help. I will be checking out your source to look over and looking at your forum. Thanks Again!
I know everyone has prob said this. But I'm willing to test betas and such for the sgs4g. Let me know if I can. Thanks
Sent from my SGH-T959V using XDA App
See page 19 for the seventh build.
Good job! Nice and clean in a new topic. KUTGW!
Sent from my HTC Desire using XDA App
Freaging sweet!
(sorry for spam but this is exciting)
Excellent stuff.
So will that mean close to full HWA?
If we're running any of the ICS builds which have the hardware hacks, this applies, right?
texasice said:
@ those who flashed Chaosz-X new kernel you need to remove this line from build.prop
Code:
ro.config.disable_hw_accel=true
Click to expand...
Click to collapse
@rootSU: I think it does, because it scores almost the same as GB Sense ROMs, and it gets pretty decent FPS at Quadrant (certainly smooth enough), so I think it works fine.
@pnw: haven't tested that, but you can give it a try, it seems pretty logical that it would help
Can't wait for the 3.0 kernel
Sent from my HTC Desire using XDA App
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash...
sent from my HTC desire using xda premium
mattmanwrx said:
I flashed this on the p2 build, but my wifi would not turn on... I reverted back to my nandroid right before the flash...
sent from my HTC desire using xda premium
Click to expand...
Click to collapse
chaoz tried including the wifi module you use in the kernel in the system/lib folder? can't find it there on the newest kernel. This messed things up for tristan earlier
Oh crap, forgot to supply the bcr4329.ko indeed.
I'm going to try to get a running 3.0 by tonight, if I don't have it finished this evening, I'll upload the WiFi module from the build (using 2 different OS's to work on, Linux for compiling, and Windows for everything else, and working in Win is much easier for me ;p)
Edit: beginning with the really lame methods of getting 3.0 to run, first attempt is done I think, just copied over files, and modified some of them, nothing really special, starting compiling in 5 minutes.
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
*child said:
I flashed over p2 with the camera fix and the camera no longer works. Should I reapply the camera fix?
Click to expand...
Click to collapse
But does your wifi work? It didn't work for me...
Not too sure about the camera... it should work... as the added is just libs... the kernel does look at the libs, but doubt it would make a difference... just my guess...
sent from my HTC desire using xda premium
Wifi did not for me. Camera worked but I didn't test it extensively.
Sent from HTC Desire
Camera and wifi doesnt work But HW ac. is fine more speed
Wi-Fi also does not work
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
texasice said:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
Click to expand...
Click to collapse
cant wait 3.0 kernel for n1
texasice said:
Chaosz-X first of all, thanks for the work you've done so far. I believe i can port it over to the n1 using the zip you uploaded. Second, please learn git so you can push your changes to github. (i know you said you hate git but, youre developing a kernel; in comparison git is way easier to understand) It will be much easier for other devs to follow your progress, and port your changes to other qsd8k devices badly in need of hwa.
Click to expand...
Click to collapse
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?
Some devs are crossing strange lines - 4 sure . Hope you get it done for our Nexus ONE my friend
cheers
sweet..kernel 3.0!!
waiting ..waiting..
bunnahabhain said:
How could he even develop a linux kernel if he is better in using windows? Dont you have to be a kernel dev to do those things?
Some devs are crossing strange lines - 4 sure . Hope you get it done for our Nexus ONE my friend
cheers
Click to expand...
Click to collapse
People start with windows at a young age
Sent from my HTC Desire using xda premium
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!
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.