Related
All I have done here is compiled gingerbread from source by following the guide in the cyanogenmod wiki. I am not developing this, just compiling.
Odd_Sam said it best: "Just so everyone understands, this is a rom based off the developmental source code of CyanogenMod 7. OP is not a developer and has no plans to fix any issues that come up. This is more or less a sneak preview of CM 7. OP is just compiling the public source code for CM 7. Treat these "releases" as a "nightly" build. And just for clarification these builds will be experimental so do not report bugs in this thread or anywhere else. CM devs know what does and does not work."
3d acceleration, video camera and network location do not work.
Grab it here: http://ipfreelytech.net/android/update-cm-7-BravoC-1222710-gps.zip
google apps: http://ipfreelytech.net/android/gingerbread-gapps-hdpi-20101221.zip
it seems that its closer to AOSP than CM at this point, while I compiled it with the cyanogen bits, it seems there aren't many cyanogen commits for gingerbread yet, so things like the power control widgets in the notification bar and the cyanogenmod settings menu are missing.
The 3d acceleration is due to a missing library and will likely not be fixed until after the N1 gingerbread OTA drops.
I haven't posted any newer builds because there is more stuff broken compared to this build.
Nice, thanks, will try it right now marry Christmas
looking through the rom, it seems that its closer to AOSP than it CM at this point, while I compiled it with the cyanogen bits, it seems there simply aren't many cyanogen commits for gingerbread yet, so things like the power control widgets in the notification bar and the cyanogenmod settings menu are missing.
installing google apps results in boot loop.
you gonna make one for GSM Desire ?
I do not have a gsm desire for testing, and secondly there are ALREADY gingerbread roms for the gsm desire. I mainly did this because I was tired of CDMA being left out of the gingerbread fun.
if you want gingerbread on your GSM desire go here: http://forum.xda-developers.com/showthread.php?t=829734
if you want to you can do a build yourself the way I did, I followed this guide: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Bravo
when you do the repo init change -b froyo to -b gingerbread
wackymix said:
you gonna make one for GSM Desire ?
Click to expand...
Click to collapse
I just compiled myself this morning to I didn't pull down yours yet but if you want to add some working gApps I put together an update.zip for it.
http://www.4shared.com/file/If_iDTQq/ginger_gApps.html
cool, thanks.
navalynt said:
I just compiled myself this morning to I didn't pull down yours yet but if you want to add some working gApps I put together an update.zip for it.
http://www.4shared.com/file/If_iDTQq/ginger_gApps.html
Click to expand...
Click to collapse
bah, I wanted cyanogen gingerbread for gsm
Great work,
So cynogen is back with boom on Xmas.
Sent from my HTC Desire
you GSM users are not missing anything. While I built this as a CM build, at this point its pretty much straight AOSP. besides the boot logo the only thing cyanogen about it is the kernel. I changed the thread title to better reflect that.
I am familiar with compiling cyanogenmod, never tried doing straight AOSP and couldn't find a guide, so thats why the build is as it is.
The cdma crowd had nothing at all in the way of a gingerbread rom posted here or elsewhere i could find on the internets.
You are doing awesome bud even trying to bring something together for the cdma crowd bro! You need to add IN BIG letters on the thread post, NOT FOR GSM YOU HAVE YOUR OWN, ****ERS!!!!!!!! LMFAO!!!!!!!
Merry Christmas every body!!!!!!
Sent from my Desire CDMA using XDA App
Great work, thanks and Merry Christmas!
Gingerbread
Thanks, downloading now.
CM 7
Great work with the update! I couldn't get my contacts to sync. I attempted to import the contacts in vCard to no avail. I didn't play around with it much but look forward to future updates. Happy holidays!
i was trying to figure out how to attempt this.......glad to see someone dev for cdma.
Thanks for trying tip bring us a new rom,i wish others devs would do so too, what we cdma guys only have have 3 roms at the moment and the are all based on CM I believe. I would like to see oxygen and or villain ports to cdma
Just saying lol
Good to see the CDMA Desire get a gingerbread ROM.
I felt like I was getting left out :O
Question though.... are you going to be fixing the issues like 3D Acceleration, or did you just compile this?
So just so everyone understands, this is a rom based off the developmental source code of CyanogenMod 7. OP is not a developer and has no plans to fix any issues that come up. This is more or less a sneak preview of CM 7. OP is just compiling the public source code for CM 7. Treat these "releases" as a "nightly" build. And just for clarification these builds will be experimental so do not report bugs in this thread or anywhere else. CM devs know what does and does not work.
Thank you, I tried very hard to get that point across, but I suspect people don't always read everything. Nightly is exactly what they are, every night I sync the repo and build.
Edited the OP to include a quote of your post.
Odd_Sam said:
So just so everyone understands, this is a rom based off the developmental source code of CyanogenMod 7. OP is not a developer and has no plans to fix any issues that come up. This is more or less a sneak preview of CM 7. OP is just compiling the public source code for CM 7. Treat these "releases" as a "nightly" build. And just for clarification these builds will be experimental so do not report bugs in this thread or anywhere else. CM devs know what does and does not work.
Click to expand...
Click to collapse
ipfreelytech said:
Thank you, I tried very hard to get that point across, but I suspect people don't always read everything. Nightly is exactly what they are, every night I sync the repo and build.
Edited the OP to include a quote of your post.
Click to expand...
Click to collapse
Are you compiling this on 32 bit or 64 bit?
PUREGANDROID
About
PUREGANDROID ( Pure Google Android) is a pure android os as google intended.
It uses a CM7 base but most if not all CM7 is removed. This is my first rom and I could not remove all CM7 but I will remove more in the Future (cyanogenmod in setting ( Please I need some help on this) and the RenderFX widget( can't locate it)
UPDATE:
I have posted a beta to see if you guys like it it was built from CM and AOSP sources. I just have to compile kernel and change lockscreen.
NEW WEBSITE
macaddict.tk
DOWNLOAD
http://dl.dropbox.com/u/27168952/DOWNLOADS/PURG3.oBETA.zip
HOW TO FLASH
*USE CWR
1. wipe all user data
2. wipe cache
3. install from SDCARD
4. Select rom
5 reboot
About:
Uses Google stock launcher
Includes all google apps
Has North America GPS FIX
Uses a CM7 Kernel (for it to be stable)
Wants in Future
Ablsolutly no CM7
pure google
overclock to 1.5 or 1.8
Changes in 2.2
New aosp settings menu and more cygen removed
Lockscreen still needs editing
NOTICE
I TAKE NO RESPONSIBILITY FOR LOSS OF DATA OR AND DAMAGES.
I'm confused.
How can it be based on CM7 yet have all the CM7 removed ?
Sent using XDA Premium running MIUI version in OP
symonc said:
I'm confused.
How can it be based on CM7 yet have all the CM7 removed ?
Sent using XDA Premium running MIUI version in OP
Click to expand...
Click to collapse
I was thinking the same thing.
OP You should start with aosp source and fix that if you want as pure as google android as you can get.
By the way you your picture you have up there is not stock launcher it's adw launcher. And the rotary lock screen is not stock either. Sorry.
Sent from my Incredible using Tapatalk
I have the stock launcher installed in this version that screenshot is old. The Google lockscreen is included but not set as default ( trying to learn how to do this). I have remove Most of the CM stuff except for somethings i need to learn ( edit settings.apk to remove The CM settings ( which will not open when clicked on). All the apps on this rom come from a aosp rom for the DroidX( except for Terminal, Rom Manager, and File Explorer (which is very useful). All traces that i can remove so far have been removed.
haha dicks, just rippin him apart and the rom hasnt even been out for a day LOL
I applaud the effort. Congrats on your first rom and look forward to see the improvement. As far as removing apps, one thing I do is find it in Titanium then see what the file is named, then you can remove it out of the app folder.
Like stated above, you should work with a pure aosp base and you won't have to worry about any of that CM7 stuff. In my opinion, I think aosp is about as smooth as it gets when it comes to UI. I'm sure people would love to have a pure aosp ROM around here since there aren't any yet that I'm aware of.
Good luck with everything and if you need any help just ask.
I'll give a shot. I love loading new roms. Thanks and good luck.
The problem is that I remove CMparts.apk and cyanogenMod settings is still in my settings menu (like a ghost menu ( it won't open). I need someway to edit setting.apk to remove this from the settings menu but im not skilled enough to do this any help would be apreciated.
Also The RenderFX widget is unable to be found (If someone has a location or what file it is in please tell me)
tell me how it is please!!!!!
OP There is a lot more to removing cm then you are thinking. Cm is not just the addition off apps but also modification of all what is android. If you want aosp start with aosp
Sent from my Incredible using Tapatalk
Ok I tried it and honestly it looks just like cm7. I don't know about creating roms but it seems that this is cm7 renamed and the boot screen changed. I would seek advice on properly creating roms and start over. Good luck.
cpbeats said:
Ok I tried it and honestly it looks just like cm7. I don't know about creating roms but it seems that this is cm7 renamed and the boot screen changed. I would seek advice on properly creating roms and start over. Good luck.
Click to expand...
Click to collapse
It's because it is. I will gladly offer my help to the OP. Hit me up if you like OP @linuxmotion or pm.
Sent from my Incredible using Tapatalk
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
nerdkiller14 said:
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
Click to expand...
Click to collapse
You might want to check with @DOAlaboratories. He was working on an AOSP ROM, but hasn't updated his thread in a while.
http://forum.xda-developers.com/showthread.php?t=999988
nerdkiller14 said:
If I were to create this from a aosp rom I first need to get my hand on one. I need to get drivers (I have no Idea on how to do drivers). And what kernel would I use. also what drivers would i need and don't need (screen, mix, speaker, touchscreen, bluetooth,wifi?)
Also would you want to make this rom with me?
Click to expand...
Click to collapse
Building from source ie. google. You can google ginger bread aosp and it will bring up this or from Git. You are going to have to build a kernel from source as well. You take the drivers that inspire already has. Its alot of trial and error to see what works and what doesn't.
Is there anywhere that has all the information necessary to build a rom compiled into one handy area?
Sent from my HTC Desire HD using XDA App
Google is your friend if you want to learn how to compile asop. You can check out the android source site http://source.android.com/ or the developer sitehttp://developer.android.com/
Sent from my Incredible using Tapatalk
I have found a outdated 2.3.1 Asop rom for Desire HD (camera not working and USB mass storage not working ). Also If any one has any idea of how to copy CM7's drivers for USB and CAMERA I would love to hear from you!!!
Also How can I update this rom to 2.3.3 without having to recompile from ANDROID-SDK
I'm gonna take a crack at building from AOSP tonight. Gonna use the kernel and proprietary files from CM7. If it doesn't boot though, I don't have the patience to start looking into the kernel and framework to fix it. Wish me luck!
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!
More information is listed at the site below
http://androidforums.com/triumph-al...-files-7-09-2012-5-30-pm-mst.html#post4641932
Just love the fact that we're basically redoing this whole phone. Lol.
Yeah I am slowly getting there with the device files. I will be updating the post each time I push back up to github and what works and doesn't.
I am stopping work on this with the gingerbread branch and now going to use the new gb-branch-7.2 branch as it was finally released on June 16th I forgot to check back.
http://www.cyanogenmod.com/category/blog
I will be updating the WX435 github during the day.
Edit: Update is done!
I believe this is the best way to go about doing this! If we can get by on base cm7 code then staying updated with the latest from cm7 shouldn't be a problem. Also it in therory should make cm9/ aokp etc easier to iron out all the bugs!
Whenever I get my laptop set back up to build, I'm going to work on picking out the best suited branch to start with from Code Aurora and try to get a vanilla froyo kernel based off the code Aurora sources working. Then from there try and apply those changes to the newer kernels off code Aurora.
It maybe a good idea to try to contact Motorola and see if they wont give us the branch and possibly even commit tag where they forked there kernel from cause I'm pretty sure they started making cchanges to a code Aurora branch on there kernel source. Just which one and where they forked it from is the question. That way we can apply the Motorola source over top that and get the exact changes moto made to the kernel!
If anyone else has anything to add to this or any insights pleas let us know!!
Sent from my Triumph using Tapatalk
Hey g60 if you cab get some logcats on some of the stuff that ain't working right ill look at em and see what I can find!
Sent from my Triumph using Tapatalk
b_randon14 said:
Hey g60 if you cab get some logcats on some of the stuff that ain't working right ill look at em and see what I can find!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
The stuff that is not working has not been added into the device files yet. There is a lot of missing code and lib files. Once I implement more of the changes and stuff isn't working I will holler at you, I have been really focused on fixing the video drivers. I want them playing all formats as perfect as possible before I start adding more stuff. :good:
Hey on the default.xml under the github remote you just have .. so it causes problems when trying to repo sync. Didn't know if you knew it was like that or not!
It should work fine, I just did a repo sync. Make sure you are running the right branch as CM7 changed it from "gingerbread"
repo init -u git://github.com/WX435/android.git -b gb-release-7.2
I just went back in and deleted my folder, then ran repo init again, copying directly from here and it still did the same thing when I tried to run repo sync.
Hop on IRC
b_randon14 said:
I just went back in and deleted my folder, then ran repo init again, copying directly from here and it still did the same thing when I tried to run repo sync.
Click to expand...
Click to collapse
I just looked at it myself. Under remote it shows "..", shouldn't it be git://github.com/
dsmryder said:
I just looked at it myself. Under remote it shows "..", shouldn't it be git://github.com/
Click to expand...
Click to collapse
Nope this is correct it works fine. There are changes CM Team did.
https://github.com/CyanogenMod/android/blob/gb-release-7.2/default.xml
g60madman said:
Nope this is correct it works fine. There are changes CM Team did.
https://github.com/CyanogenMod/android/blob/gb-release-7.2/default.xml
Click to expand...
Click to collapse
So with that, would you have to setup all of your own remotes?
I thought that was to have a Pre-entry for "git remote"?
If you're having issues with the .. in the manifest, see the comments on this commit from cm/android/ where this was originally introduced. The solution is in there:
https://github.com/CyanogenMod/android/commit/89acec784fd50305cc55d05ecb3416fcd7c3eb0e
Yeah i fixed mine by deleting the .repo folder, curling the latest repo into myh ~/bin folder, then pulling the repo in again.
Man I was surprised. I finally got my cm7-bROM repo setup on my new Linux mint install and finally got everything updated from upstream and added some more open commits from gerrit and built it and to my surprise, it built fine with no errors a d I flashed it and it worked great! I figured it would blow up where it had been over a month or two since I had synced and built my ROM and with all the 7.2 release stuff I thought for sure it wouldn't build and add I was building on Linux mind that I had never built on!
Hey g60 you need any help with the device files? I noticed you ain't even got the triumph device repo in the manifest anymore. If you need me to help with anything my box is up and running great! I built my rom in like 47 minutes first time and I was using ccache so hopefully the next build will be faster!
I am digging into my stock code Aurora kernel nor booting. I thought it built fine but I noticed there were some warning spit out by the linker during the build and I tried with linaro and the included 4.4.3 with aosp and it did the sane thing so I'm gonna try to get the bottom of those warnings because I think that may have something to do with it!
Ill post the pastebin of the warning up in the kernel thread later!
Sent from my Triumph using Tapatalk
No updates for a while, still nothing works?
I have been really busy and have had maybe had 1-2 hours to work on the device files in the last 6 days. I should have some more time this week so will see what I can get out.
headset does not register on boot if plugged in
Click to expand...
Click to collapse
Pretty sure this bug was in all CM7 builds before. I also experiences the same thing with MIUI rom.
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.
jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind
androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.