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?
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..
I heard that this forum is a master transplant CM7 ROM, I would like to ask about the current progress
What is difficult to solve the problem?
Can provide the current ROM, I would like to try
Want to provide,
Thank you
I want to start by saying THANK YOU FOR MIUI!!!! You are awesome. And they have got cm7 booting up on xt720 but only if you flash motoroi 2.2.1. But the touch screen is not working. If I were you I'd get with Mioze7Ae. He's the Guy to talk to about it. There is a thread with the ROM download in it in the general thread.
oyang06 said:
I heard that this forum is a master transplant CM7 ROM, I would like to ask about the current progress
What is difficult to solve the problem?
Can provide the current ROM, I would like to try
Want to provide,
Thank you
Click to expand...
Click to collapse
stlifey made a port of CM7 to XT701. That is here:
http://forum.xda-developers.com/showthread.php?t=1064090
If download links are dead there, let me know and I can mirror/reupload.
I think this is the main development page for the XT701 CM7, but the forum seems to be down for maintenance right now:
http://bbs.gfan.com/android-1297281-1-1.html
It doesn't work on XT720 yet. This is where things stand:
Using Milestone XT720 2.1 sbf
If you use a Milestone XT720 sbf, then it doesn't boot. I've been modifying it and have gotten it to go further with adb logcat working to get some messages out. This is the latest version I've been testing that makes it the furthest before rebooting:
http://www.multiupload.com/ULWN2ERP02
The radio panics and panic_daemon shuts down the phone. If you modify the init scripts, you can disable panic_daemon. Then it will boot to the point that zygote tries to start but has a library link problems so I've changed too many libraries .
From Korean Motoroi XT720 2.2 sbf
sktjdgns1189 figured out that if you flash the Korean Motoroi 2.2 sbf, root, install OpenRecovery, and apply the XT701 update without any modifications it boots up, but the digitizer doesn't work. You can do some things like long press the camera button to get the camera to come up and you can take pictures. See
http://forum.xda-developers.com/showthread.php?t=1118236
Eventually it will crash and reboot. The bad news is that for some reason after you flash the the Motoroi sbf on Milestone XT720, you can't use volume-up to enter OpenRecovery. So you have to use adb ("reboot openrecovery") to get back into OpenRecovery. But I haven't been able to get adb to startup. So that means you're back to sbf for the next try. I can't figure out why the touch screen doesn't work.
sktjdgns1189 has also figured out how to get the battery notification working:
http://forum.xda-developers.com/showthread.php?t=1124927
Edit: Forgot to mention that we're now pretty sure that sktjdgns1189 has a Motoroi XT720 based on his photos. I've reproduced most of his results on a Milestone XT720.
easye420 said:
I want to start by saying THANK YOU FOR MIUI!!!! You are awesome.
Click to expand...
Click to collapse
+1. Very fantastic work on MIUI. Great to see you looking into CM7 as well.
its going to be on android 2.3 right?
eejin2 said:
its going to be on android 2.3 right?
Click to expand...
Click to collapse
If someone gets CM7 working then yes that is Android 2.3
Thank you Oyang06 for Miui rom and I wait CM7
Sent from my XT720 using XDA Premium App
Looks like stlifey plans to release CM 7.1 for XT701 this weekend.
Off topic: Does anyone know what all the "ah"s that Google Translate adds means? I think wiktionary suggests "啊" == surprised+"!"? Also, does anyone know a good place to look up those four-character idioms? There's one about hunters that comes up a lot. Just curious.
lols. ah is like "oh". for idioms maybe you can copy to google then add "english meaning"
khankuan said:
lols. ah is like "oh". for idioms maybe you can copy to google then add "english meaning"
Click to expand...
Click to collapse
I see! The google translated posts just seem a little strange because I guess "ah" and "oh" would come at the front of the expression in English. It can seem like reading threads where everyone is talking about Candlejack and then sudde
Haha, just post here if you need any translations awaiting patiently for CM7 Gingerbread XDXD
i can help a little with the translations too, haha. SOOOOO EXCITED FOR GINGERBREAD. i like the stock look of cm7 and of course the turning off crt animation of 2.3. CANT WAIT!
do you think we can get 2.3 miui running on our phone?
eejin2 said:
i can help a little with the translations too, haha. SOOOOO EXCITED FOR GINGERBREAD. i like the stock look of cm7 and of course the turning off crt animation of 2.3. CANT WAIT!
Click to expand...
Click to collapse
Yeah, gingerbread is much more attractive than 2.2 and below all around. Plus it's supposed to be faster (and CM is supposed to be even faster) and have other goodies... would be so fantastic to see this for the XT720.
if you want to use adb
just use 2nd-init (default.prop : ro.secure=0, ro.debuggable=1, persist.service.adb.enable=1, persist.factory.allow_adb=1)
(and some code in init.mapphone_umts.rc (it for adb on bootup))
then you can use logcat/dmesg and etc even on bootup
wait and sad
CM7 would be a dream come true.
Best of luck guys, I will be watching
Wish I would know how to contribute to this happening... would make me feel better knowing I was making some progress. Well, hope this goal is attainable.
Dexter_nlb said:
Cyanogen from Milestone could easily be ported, like i did htc sense like on milstone... the issue is requirements and added extra button and fm radio.
but the rest would work from a milestone release.. fairly easy to do.
Click to expand...
Click to collapse
I don't wanna sound arrogant and I really appreciate what you guys are doing, but am I missing something?
My take on that is their talking about milestone not milestone xt720.
Sent from my XT720 using XDA Premium App
mchlbenner said:
My take on that is their talking about milestone not milestone xt720.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
No, Dexter posted that in his XT720 thread. I saw that the other day and was considering mentioning it, but I'm sure Mio and others are doing everything already.
Here's the post Dexter is responding to:
"From my understanding of the situation, Cyanogen is out of the question, for now. Dexter's roms are modifications of the official MOTOROI XT720 2.2 (KR) for our handsets. Due to the bootloader lock placed on the phone by Motorola, we can't compile our own systems based on the android sources.
Anybody correct me if I'm wrong with my situation assessment. "
Click to expand...
Click to collapse
Though if Dexter feels it's so simple I wish he would elaborate for the benefit of our devs, just in case he knows something they don't.
11/22/11 Update: Added "reboot bml8 recovery" patch for ROM Manager suppport.
11/8/11 Update: Updated keyfix kernel with the EI22 initramfs. Also, Samsung has placed the previous official (and now labeled EI22) source tarball on their opensource site.
10/24/11 Update: It appears that Samsung has removed the "official" Epic GB source tarball from their website. I've mirrored it for anyone interested in the original release. For anyone actually looking to build with the sources, you're probably better off using Rodderik's GitHub
10/19/11 Update: As everyone's found out by now, Samsung released official Epic GB sources last night. There's not that many changes to our device in the official source tree compared to the previous, but a few appear to be subtlely important (see abbreviated deltas). It still needs some work to get into a buildable state, but it does appear to work great on EH17!
I've updated most of my patches for GB, conveniently packaged together. I've also uploaded a new EH17 kernel that works on stock (rfs) EH17 ROMs and includes the keyboard fixes with optimized values, along with userdebug and kexec support. Feel free to give it a try.
Meanwhile Rodderik is updating his GitHub repo to include all these patches for folks to clone from, stay tuned.
Happy hacking!
So apparently when Samsung released the kernel sources to the Mesmerize's Gingerbread update a month-and-a-half ago, that source tree contained almost-buildable kernel sources for our device as well.
I've patched the sources (removed modemctl definition, added tfsr driver, compile right camera driver) to build for the Epic. I've also built a custom EH17 kernel combining these sources with the EH17 initramfs. It's essentially stock EH17 with ro.debugging=1, adbd always-spawning during recovery, and testkey signature verification. I'll get to porting over some other patches (like the dropped key fix) soon.
As for compatibility with EH17, the source tree itself appears to have been checked out on 8/30 and looks to include everything EH17 does. I ran "strings Image | sort -u" on both kernels to make sure there weren't any obvious strings/symbol differences between them. The ones that remain appear to be minor, but legitimate fixes.
Thanks to jt1134 & Rodderik for pointing out that the Mesmerize source released contained Epic code, and Tortel & ugothakd for testing.
GitHub repo, thanks Rodderik!
To build:
Grab SCH-I500_USCC_Opensource_Update3.zip SPH-D700_GB_Opensource.zip from opensource.samsung.com, extract.
Run "make mrproper" to get rid of atlas (Mesmerize) config junk.
Patch to complete Epic support.
Build with EH17 initramfs as usual, use victory_8G_defconfig for kernel configuration.
Mirror links:
Official GB sources: SPH-D700_GB_Opensource.zip (originally posted on opensource.samsung.com, since removed.)
Epic GB source patches: kernel-GB-3a-patches.tar.gz
Source-compiled, keyboard fix EI22 kernel: kernel-GB-3a.tar.md5
(URLs for Mesmerize tree patches removed, although they're still valid.)
Flashed this yesterday(11/13). Working good so far.
Edit: Oh, and first! Sorry iSaint
Sent from my SPH-D700 using Tapatalk
HAHAHAHA! Epic. I love you guys!
Yeah, um, I love you. <3 lol.
No. I was first. I tested it lol
[edit] actually, tortel was first. but that was before i got on board.
Hmmmm...who would of known part of our kernel source was right under our noses
Sent from my SPH-D700 using xda premium
It just occurred to me that, with this finding a lot of good can happen, as well as ICS tomorrow. Depending on timezone I should say.
Sweet. Hopefully this'll help cm7
Heart just stopped beating LOL!
What about stratosphere then?
Oh well nice work!
Sent from my SPH-D700
winning
bet samsung was just watching and waiting to see how long it took one of you/us to figure it out, lol.
this is wonderful news
Ceelos09 said:
Hmmmm...who would of known part of our kernel source was right under our noses
Click to expand...
Click to collapse
Ideally there would be one Samsung Android kernel source tree that would contain code for our device as well as all their others. However, I've been checking somewhat recently and code for Epic never appered in the GT-I9000 sources (which have been updated recently) nor in the Stratosphere ones.
It didn't occur to me to check the Mesmerize sources sooner, but as the only US device with an official GB release (still?) it shouldn't have been much of a surprise. It's also worth nothing that there appears to be GB sources for the Indulge in there as well. I'm not sure of their buildability though.
GREAT work mkasick.... everyone be SURE to thank him!
SWEET !!!
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I'm not sure, JT helped Decad3nce with CM 7 though and they both hacked the EH17 kernel to work for this. So hopefully it's something Decad3nce can use.
He said he was moving so he probably won't be back until tomorrow.
Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
The main CM7 people are Decad3nce and jt and they haven't been on irc today.
this is exactly what we been needing...THANK YOU VERY MUCH mkasick!! You rock my friend!
Downloading now - going to see if I can compile a bootable kernel
Sent from my CyanogenMODed Epic
Neckberg said:
Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I believe JT was the one who discovered the Mesmerize sources were pertinent to us. He might've been able to compile something, but at least Rodderik was stuck on the missing tfsr driver without the right debugging bits.
I discovered this worked somewhat haphazardly when Rodderik mentioned the Mesmerize sources to me. They booted the first time with EH17 on SD, but wouldn't boot from flash. Since I was able to get it to boot off SD, debugging was a good deal easier.
In any event, it's a drop-in replacement for the current kernel used by the Epic CM7 build, so I'm sure they'll make good use of it sooner or later.
Actually what I'm curious about is if the reboot problems still persist with this. I haven't had one yet, but they haven't been a problem with stock EH17 on my device either.
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.