Database Info

[Rom] EXPERIMENTAL AOSP Gingerbread for CDMA Desire *New Build 12/27 w/ GPS*

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?

Building Android from source for Nexus S

EDIT: Oops, I meant to put this in General section. Sorry!!!
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
The first one is that there is of course no Google Apps. I understand why, but is there a good source for them? Or do the ones for CM7 work?
Second, I get the regular Android boot animation, not the cool Nexus S one. Is that normal?
Third, my Android version always says something like 3.1.x.x.x.x.x or something crazy. Is that normal? I was kind of expecting it to say GRJ22 2.3.4 or something like that.
I am trying to build full_crespo-user, FYI.

I use the normal gapps whenever I compile an aosp. Try the modded one specific for the nexus s. You would find it in the last pages of the nightlies thread.
Yes. The android marine blue animation is the default one for aosp.
The version number you are getting 3.1.xxzzxxxxxxxxxz is quite normal. This is the actual version of aosp. You can change it in your build.prop if you want to.
Good luck/
Sent from my Nexus S using Tapatalk

matt2053 said:
I just switched over from Windows to Ubuntu a couple of weeks ago. So far I'm loving it and one of the cools things I realized I could do now is build Android from source! But in doing that I have a couple of issues.
Click to expand...
Click to collapse
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?

Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
no need to pull them. anyway official binaries are available for the nexus s
http://code.google.com/android/nexus/drivers.html

Graham19 said:
I'm thinking of building Android from source as well.
This might be a stupid question, but do I want to use repo to pull down the sources from the Gingerbread branch (rather than master)?
Also, do I need to pull down proprietary files from my phone before the build?
Click to expand...
Click to collapse
Yes, pull from the gingerbread branch! Master is almost always full of bugs and not the best to build. You know you have master when the build number is pi (the 3.1.4... one mentioned earlier).
To use repo to pull down the gingerbread branch, use the repo init command as usual but add "-b gingerbread" at the end (no quotes).
Sent from my Nexus S

I would love to know more about this master vs gingerbread branch difference. I've been building from master it seems. What purposes do the different branches serve? Can someone shed some light on the Android development process?
Sent from my Nexus S using XDA App

So master basically contains everything, all versions. Master is basically all of android xD
Now, you can do a -b gingerbread to just clone the gingerbread branch, which will give u the 2.3 code for everything on android.
** Note -b can also be used for froyo, eclair, etc. **
I hope this helps!

Not development. Moved to Q&A.

I have another question so I am bumping this up:
I have successfully build Android 2.3.5 for my Nexus S. Is there anyone who might help me adding Google Nexus boot animation and Google Apps, and putting it all into a flashable zip?

I figured out the zip thanks to this awesome thread: http://forum.xda-developers.com/showthread.php?t=732957
Now my problem is the keyboard. The "suggested" words are only names from my contacts, I don't get any regular English language suggestions. Any ideas?

[REF] Github repo for SGH-I997R Source Release

Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos). (Edit: I'm starting to consider doing things a bit differently in order to allow this to stay as a relevant reference - After all there are certain "core" features like Voodoo Lagfix/Sound that have no known detrimental effects and are basically expected from any kernel used by the community.)
One thing is that most of the other ref repos are on a github "team" account - mine is on a personal account. I'm going to look into whether I can change this without breaking the fork relationships.
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r
Initramfs from Wednesday's dump is at https://github.com/Entropy512/initramfs_sgh-i997r
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Update: Merged a pull request from LinuxBozo that has a bunch of .gitignore fixes and Makefile fixes.

Good work! Looking now.

Entropy512 said:
Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos)
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r - There is nothing visible there yet as the push is still in progress. It should be done within 30 minutes or so.
I don't have an initramfs repo yet - we need an initramfs dump from a device first.
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Click to expand...
Click to collapse
Absolutely awesome news :-D
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Oh blast, hadn't even seen that kernel code was available... thanks Entropy!

A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)

Entropy512 said:
A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)
Click to expand...
Click to collapse
Defuse kernel
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

nelomen said:
Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
Initramfs, radio firmware dump, proper /system dump. Ours is incomplete.

Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo

Entropy512 said:
Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo
Click to expand...
Click to collapse
Nice!! Anything buildable yet?

ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
should be buildable since initramfs is available, tomorrow gtg's voodoo commit should be available too. this is all very exciting.

ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
A few more things got pulled in last night.
Kernel - not much
Initramfs - Working CWM - or at least it comes up, it hasn't been fully tested functionally yet
As of last night a few people have custom kernels running including myself, although some people still can't boot them. CWM wasn't working until past midnight...
Next up is voodoo - Not sure if I'll include that in the main initramfs repo or not. Maybe as a branch. It is a fairly standard mod, so it should be in a readily accessible repo

Bad news - as I said before CWM hadn't been fully tested.
Apparently, after further testing, it still does indeed have some pretty severe issues.

Sadface
10c

P1 Wookie said:
Sadface
10c
Click to expand...
Click to collapse
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.

trolls suck.
GL guys.

Entropy512 said:
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.
Click to expand...
Click to collapse
Gotta love the trolls.
Good luck guys. I know you all will figure it out

Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.

bedwa said:
Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.
Click to expand...
Click to collapse
why no use of a client?

drowningchild said:
why no use of a client?
Click to expand...
Click to collapse
Finally got it to work, had to hack a command line client.... urg.

[mods can close this thread]Lets make an ICS device configuration tree

project done...lol sorta. cm9 device tree released.
mods you may close and unpin if you feel neccesary

I had been working on it... but I sort of stopped because of school and work. I'd like it so much more if I wasn't the only one working on it because when you get stuck its hard to find someone willing to help you. You can see my stuff at github.com/mafischer
There are two empty repo's with a GB prefix, those were intednded to be for the cm7 branch I'm working on... just ignore them. The other repos are for ics.
Sent from my myTouch_4G_Slide using Tapatalk

rajzzz built icsex from scratch..he should have an overlay and all on his pc to put on github

That would be extremely helpful!
Sent from my myTouch_4G_Slide using Tapatalk

Github is far friendlier to use on Linux, in case anyone was wondering. The Windows version isn't too bad to use, however. It's just easier to run everything in terminal.

michaelmab88 said:
I had been working on it... but I sort of stopped because of school and work. I'd like it so much more if I wasn't the only one working on it because when you get stuck its hard to find someone willing to help you. You can see my stuff at github.com/mafischer
There are two empty repo's with a GB prefix, those were intednded to be for the cm7 branch I'm working on... just ignore them. The other repos are for ics.
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
ill go clone you and see if my stock rom boots. thank you

xmc wildchild22 said:
ill go clone you and see if my stock rom boots. thank you
Click to expand...
Click to collapse
lol... it won't (I mean i don't think its ready for that)
Edit: I'm don't think it'll even compile (post any compilation errors you get, or pm them to me)

i got some build\core issues...i had to fork msm commons....but ill post the actual error when i get home

This thread should be stickied so it doesn't get lost.
Request sent

nice we got it stickied (thanks gtmaster).....below is the error when building using mike's device configuration
Code:
build/core/product_config.mk:205: *** No matches for product "htc_doubleshot". Stop.
** Don't have a product spec for: 'htc_doubleshot'
** Do you have the right repo manifest?
I have the msm8660-common forked from vorbeth's sensation repo

xmc wildchild22 said:
I have the msm8660-common forked from vorbeth's sensation repo
Click to expand...
Click to collapse
As do I,
I just re-setup my ics repo using these manifests. (I killed my previous ubuntu installation after messing around with my graphics drivers; so i reinstalled the whole os and resetup the ics repo.)
---------- Post added at 08:33 PM ---------- Previous post was at 08:26 PM ----------
xmc wildchild22 said:
Update 4/22/12:
Thanks to Michaelmab88, we will start our tree based of his work in progress tree here
Click to expand...
Click to collapse
Actually its thanks to vorbeth for his progress on the opensensation tree. Mine is nothing more than a fork of his work with every instance of "Sensation" replaced with "myTouch_4g_slide" and every instance of "pyramid" replaced with "doubleshot". I wouldn't have expected it to compile.
The only additions i made were extracting the proprietary files from the doubleshot. There are many many days of code investigating ahead.

I justed fixed a path in the cm.mk file in device/htc/doubleshot/ and it started compiling. I saw some other things that need to be fixed as well.
We've got lots of work ahead of us, but you always have to start somewhere.
Hopefully we can get other devs on board and start moving the project along!

definetly....and yea nice find, i just merged that in with mine

Honestly, I think this thread needs to be moved to the development section... It should get more exposure, not to mention it's dev work
Lol, request sent
EDIT: Where the heck are tbalden and rajzzz? We need to get them in on this...

haha Lets move it to theme and apps! tbalden is mainly a rootz user because virtuous moved there.....so he checks here occationally. rajzz haas school like me and is probably busy doing something.

gtmaster303 said:
Lol, request sent
Click to expand...
Click to collapse
Damn you .
I was thinking this was dev, but since it was just getting off the ground I wasn't sure if it belonged over thar yet... Seems like you guys are making some headway, keep it up!

arrrghhh said:
Damn you .
I was thinking this was dev, but since it was just getting off the ground I wasn't sure if it belonged over thar yet... Seems like you guys are making some headway, keep it up!
Click to expand...
Click to collapse
Gonna make you work for it
Yea, I didn't expect this thread to explode into a dev thread either. Yet here we are. great work guys!

guys check my github as well as michael's for status updates. We made a lot of progress today

Hey guys, great work! I was actually starting to look into it, too.
I started to try and just compile the pyramid tree (following this guide), but I ran into problems:
Code:
Error: bad barrier type -- `dmb st'
As far as I understand it means it's not using the correct binutils?!? I mean, I've been compiling Android hundreds of times, just never for ARM, only x86 - so can anyone point me to a solution?
Stefan
P.S.: Are you planning to compile the kernel as well? Because I saw that the pyramid kernel project has made some quite nice progress, with overclocking/undervolting during runtime and other nice features.
---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------
michaelmab88 said:
Actually its thanks to vorbeth for his progress on the opensensation tree. Mine is nothing more than a fork of his work with every instance of "Sensation" replaced with "myTouch_4g_slide" and every instance of "pyramid" replaced with "doubleshot". I wouldn't have expected it to compile.
The only additions i made were extracting the proprietary files from the doubleshot. There are many many days of code investigating ahead.
Click to expand...
Click to collapse
I think the proprietary files should not be in any public repo (danger of being sued by HTC or kicked out by Github). For the pyramid there's a shell script which pulls them of the original device via adb.
Stefan

Well i need proprietary-files because its the reference file on what extract-files.sh and setup-makefiles.sh work with. Why would the sue me? I wont be focusing on any errors until all the required stuff is in (but thanks for the feedback).

CM-10.1

I'm posting this here because I need some help from other devs. I'm in the process of porting ubuntu touch for you guys but I
m having a hard time getting the cm-10.1 kernel built (booting). I'm wondering if any of you other guys have been working on cm-10.1 and have a gotten a successfully booting kernel/ROM. If not, let's team up and see what we can come up with to get the blaze bumped up to the latest version.
So with that said, let's share our notes, findings, and issues...
I was able to get a booting kernel (just not the ROM) by doing a backwards merge with my jellybean LZ kernel (downloaded my kernel to my repo and merged with cm 10.1 sources). I'm thinking that this may be the way to go to get us rolling on cm 10.1

thomas.raines said:
I'm posting this here because I need some help from other devs. I'm in the process of porting ubuntu touch for you guys but I
m having a hard time getting the cm-10.1 kernel built (booting). I'm wondering if any of you other guys have been working on cm-10.1 and have a gotten a successfully booting kernel/ROM. If not, let's team up and see what we can come up with to get the blaze bumped up to the latest version.
So with that said, let's share our notes, findings, and issues...
I was able to get a booting kernel (just not the ROM) by doing a backwards merge with my jellybean LZ kernel (downloaded my kernel to my repo and merged with cm 10.1 sources). I'm thinking that this may be the way to go to get us rolling on cm 10.1
Click to expand...
Click to collapse
I have been working on it for a couple weeks... we can not seem to get a booting kernel... once we get a kernel, porting ubuntu phone looks to be a breeze... any help will be greatly appreciated.. Ericmm was working on it too but I have not been in touch with him lately..

Racing19969 said:
I have been working on it for a couple weeks... we can not seem to get a booting kernel... once we get a kernel, porting ubuntu phone looks to be a breeze... any help will be greatly appreciated.. Ericmm was working on it too but I have not been in touch with him lately..
Click to expand...
Click to collapse
I already have the Ubuntu ROM portion made. It's the kernel that is getting me stopped...lol
I know eric has been really busy lately and has about 500 projects going on as well. I'm taking a off the wall approach to it tonight and I will let you know how it turns out, and if all goes well, I'll update my repo...

thomas.raines said:
I already have the Ubuntu ROM portion made. It's the kernel that is getting me stopped...lol
I know eric has been really busy lately and has about 500 projects going on as well. I'm taking a off the wall approach to it tonight and I will let you know how it turns out, and if all goes well, I'll update my repo...
Click to expand...
Click to collapse
Your not alone, ericmm, dr4stic, uberpinguin and racing have all been working at it. If you need help, hit uberpinguin up on IrC.freenode.net at #Cyanogenmod or #cyanogenmod-dev. He's been trying to get help from somebody that has more experience with kernels. Pm dr4stic or beast mode, that's the best way to reach them. Dr4stic only pops in bout once a week. Good luck and if you need a tester. I gotcha:good:

Yep, the ubuntu part is easy. have had that since the day it was released... The kernel is where we are all stumped for some reason...
I am guessing that sooner or later one of us will figure it out... by then source will get released.. ha ha.. would be great if you could figure it out..
thanks for any info you can pass on..

possible help
Check into the galaxy exhibit 4g forums and get ahold of smartguy044! Great kernel creator!!! He created the first operating 3.0 overclock/ under/over volt kernel to work on the exhibit 4g and to my knowledge the only one! Possibly a great dev by the name of camcory could help also! Great devs and great guys

I think i got it!!!!!!!!!!!
Ok, I think I found the underlying issue!
Although the ROM didn't boot, the kernel sure did cuz I got a logcat...Lots of egl errors (/system/lib/egl/***) Which tells me that the kernel at least booted. We can work the hardware errors off as we go. However, with what I did, was a bit "dirty", so if you other devs (rancing, dr4stic, eric) could check this against yours, we might be able to come up with a definitive fix and have official cm-10.1. Now I wold like to say in concern with the ROM not booting, I do not have cm-10.1 repo on my computer, and I really don't want to because my android partition only has about 20gb left on it which is what I use for ccache. Instead, I used my ubuntu repo.
Here's what I did:
First, I add my jellybean branch of the lz kernel and synced it
I then added Cyanogenmod's cm-10.1 branch to my git config file:
Code:
git remote add Cyanogenmod https://github.com/CyanogenMod/android_kernel_samsung_msm8660-common.git
git pull Cyanogenmod cm-10.1
Then I built the ubuntu ROM using brunch t769 command
After it was finished, I pushed it to the phone, flashed and rebooted.
I got nothing...lol So I restored from my nandroid backup...
I diffed the defconfig for the skyrocket between jb and cm10.1, and found a few differences. So I made note of them and then check the defconfig of the t769 for those diffs. I added the missing ones, changed the differences, and removed the ones that was suppose to be there. I ran make clean then brunch t769, pushed it to the phone and rebooted and saw this:
Code:
I/cm ( 345): ____ _ _ ____ _ _ ____ ____ ____ _ _ _ _ ____ ___
I/cm ( 348): | \_/ |__| |\ | | | | __ |___ |\ | |\/| | | | \
I/cm ( 350): |___ | | | | \| |__| |__] |___ | \| | | |__| |__/
I/cm ( 356): Welcome to Android 4.2.1 / CyanogenMod-10.1-20130228-UNOFFICIAL-t769
Along with a sleuth of errors.
Now, I'm sure your asking what are the diffs thomas?
Entries to add or change:
Code:
# Linux/arm 3.0.60 Kernel Configuration
# CONFIG_MSM_SLEEP_STATS_DEVICE is not set
# CONFIG_MSM_CPU_PWRCTL is not set
# CONFIG_ARM_ERRATA_764369 is not set
# CONFIG_ARM_ERRATA_775420 is not set
CONFIG_ARM_FLUSH_CONSOLE_ON_RESTART=y
CONFIG_SYNC=y
CONFIG_SW_SYNC=y
# CONFIG_SW_SYNC_USER is not set
# CONFIG_LIBRA_SDIOIF is not set
# CONFIG_FRAMEBUFFER_CONSOLE is not set
CONFIG_ANDROID_LOW_MEMORY_KILLER_AUTODETECT_OOM_ADJ_VALUES=y
# CONFIG_HARDLOCKUP_DETECTOR_NMI is not set
CONFIG_HARDLOCKUP_DETECTOR_OTHER_CPU=y
CONFIG_HARDLOCKUP_DETECTOR=y
Entries to be removed:
Code:
# CONFIG_SHAPE_TOUCH is not set
CONFIG_FB_MSM_VSYNC_SYSFS=y
CONFIG_FB_MSM_HDMI_MSM_PANEL_HDCP_SUPPORT=y
# CONFIG_USB_UAS is not set
Now, I could be way off base with this, but that's why I need some of you other devs to test it in a cleaner way.
sync cm-10.1 source without merging
diff defconfig and make necessary changes
Build with cm-10.1 ROM resources
Boot and keep fingers crossed
Report back
Later today/this evening, I will post my logcat from boot to bootloop so we can diffs those as well...
If necessary, I will remove my ubuntu repo and pull cm stuff, but I would really not like to since syncing ubuntu took 4 days...lol
**EDIT** I meant to mention, I think the first line, Linux/arm 3.0.60 Kernel Configuration, could be the biggest issue since I have ran into a similar issue sometime back when I was porting ICS to the SGS4G...

I will make the changes you listed and run a build on cm10.1 source. will let you know how I make out...
Update: Using the changes listed above the kernel will not build...
arch/arm/mach-msm/board-msm8x60_celox.c:16531: error: 'hdmi_panel_power' undeclared here (not in a function)
make[1]: *** [arch/arm/mach-msm/board-msm8x60_celox.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....
will keep trying

Racing19969 said:
I will make the changes you listed and run a build on cm10.1 source. will let you know how I make out...
Update: Using the changes listed above the kernel will not build...
arch/arm/mach-msm/board-msm8x60_celox.c:16531: error: 'hdmi_panel_power' undeclared here (not in a function)
make[1]: *** [arch/arm/mach-msm/board-msm8x60_celox.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....
will keep trying
Click to expand...
Click to collapse
Oops...I removed the entire struct entry (from }; to the next }) for now... you might have some libcopybit errors, something about mpd4_overlay, and pow too...since I'm away from my computer I can't tell you exactly what I did, but when I get to it, I'll post it... you can find the libcopybit and pow fix on github via Google...but the overlay one I just remove the line(s)I think...I'm sure we'll need to add them back in, but I'm just trying to get this to boot first...Lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Here's the fix for libcopybit:
https://github.com/UnicornButter/ha...mmit/d40e33e88aae9c0c9c9839d69b44ad828dc18d84
And the pow error:
https://github.com/aokpx/platform_bionic/commit/edd30e9e0b66b2604f3a94346e67422d619b0558
and the mdp4_overlay.c
I'm just removed the entries that were throwing the error. Around lines 3641 and 3657 (after you delete the first entry). I want to say for the one at/near 3641 it was only 1 line and the second entry near 3657 it was 3 lines
I know the mdp4_overlay.c error is definitely NOT a fix, but I was honestly a bit stumped so I just went around it for now. It could also be the cause of egl (since this is a video driver) not working/loading properly which would cause the ROM to not boot...
**EDIT**
Ok, here is the full booting logcat... I started it while the samsung screen was on and it stopped when the phone rebooted. Before this, there was nothing. The phone would be on for about 2 or 3 minutes after the samsung was displayed and the it would turn off... So, I would say this is progress. I'm taking a little break for tonight. Feel free to rummage thru it and see what you guys can figure out. Please post anything helpful for the good of the community.
cm-10.1 partial boot

@thomas , I posted a link to this page to uberpinguin, maybe he can help as well.

I regressed...sorta
I compared the defconfig with that of a known booting device and saw many differences. So I thought I would merge the 2 defconfigs together and now it doesn't boot. However, I did not get any of the build errors, like the board-msm8X60_celox.c or the mdp4_overlay whatever. So, I am going to think of this as progression with minor regression...lol
So, I think if we can figure out what really needs to be in the defconfig and fix thes disply/egl errors, we will have cm-10.1 running.

thomas.raines said:
I regressed...sorta
I compared the defconfig with that of a known booting device and saw many differences. So I thought I would merge the 2 defconfigs together and now it doesn't boot. However, I did not get any of the build errors, like the board-msm8X60_celox.c or the mdp4_overlay whatever. So, I am going to think of this as progression with minor regression...lol
So, I think if we can figure out what really needs to be in the defconfig and fix thes disply/egl errors, we will have cm-10.1 running.
Click to expand...
Click to collapse
You can't just go combining defconfigs, they're different for a reason
The T989 is the general model i used as the first port and the differences from it to ours is a matter of driver selection. Their builds work (obviously) and ours don't. I've got a build environment going, have been pouring over the source differences, and have attempted a few things but progress is definitely stalled.
UberPinguin has had more time than I to delve deeper and I've been following his progress closely. Just to give you a peek behind the curtain, he's got a pretty sophisticated debugging set up going trying to figure out exactly why this thing crashes He's added debugging just about everywhere and still can't find the hold up.
Anyone looking to get this working, I wish the whole community luck on this. This one is an all hands-on thing.
(and yes, i'm alive, and sorry I've been so missing...)

To what dr4stic said he's right defconfig merges won't work for us because the blaze is different even if similar to the other msm8660.
Also, I've been working on this for over a month now with racing and we're at the same spot we were back then. I'm sure with dr4stic and uber and even CM helping we might get something booting.
As for the kernel well that's been the only thing holding back any rom from being released I had a 4.2.2 ROM running on the old kernel but no point on releasing that if we have to fix so much so I'm working on this as well on my free time. Hopefully I can come up with something to help out the big guys upstream (dr4stic and Uber)
Sent from my Galaxy Nexus using xda premium

Beastmode said:
To what dr4stic said he's right defconfig merges won't work for us because the blaze is different even if similar to the other msm8660.
Also, I've been working on this for over a month now with racing and we're at the same spot we were back then. I'm sure with dr4stic and uber and even CM helping we might get something booting.
As for the kernel well that's been the only thing holding back any rom from being released I had a 4.2.2 ROM running on the old kernel but no point on releasing that if we have to fix so much so I'm working on this as well on my free time. Hopefully I can come up with something to help out the big guys upstream (dr4stic and Uber)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah,I know I over did it with the defconfig...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Outside the Box?
Have you guy's thought about talking to Morfic (Trinity Kernels) or Jellette? They don't have a Blaze but if someone had an extra dev Blaze for Them to work with, They may be game.
Morfic:http://forum.xda-developers.com/member.php?u=1122306 >
Jellette: http://forum.xda-developers.com/member.php?u=2967115 > Both of these guy's have a lot of experience with Samsung Devices and Kernels.......just a thought

thomas.raines said:
Yeah,I know I over did it with the defconfig...
Click to expand...
Click to collapse
I forgot to mention why I mentioned it... there are, absolutely, a number of drivers on the other devices that would keep a kernel from booting up on ours. The MHL adapters immediately come to mind (anything having to do with HDMI really), and I believe a few others might have the same effect as well. The kernel simply won't boot.
Just wanted to make sure you didn't end up on a wild goose chase.
I'm spending the weekend downloading new kernel sources and diffing them to all hell, see if something's changed for the other devices that should've changed for us. Too many custom files... this is annoying...

One question.. What is the problem as of now. Is it still not booting??
Sent from my Nexus 5 with Key Lime Orange Mango Beef Tuna Pie

a case of beer to the person who can get ubuntu on our phone

Well the T-Mobile Galaxy S2 received Jelly Bean today. Official from sammy mobile. Is that like our device? If so lol. Head over to their forums.
Sent from my Nexus 5 with Key Lime Orange Mango Beef Tuna Pie

im_awesome_right? said:
Well the T-Mobile Galaxy S2 received Jelly Bean today. Official from sammy mobile. Is that like our device? If so lol. Head over to their forums.
Sent from my Nexus 5 with Key Lime Orange Mango Beef Tuna Pie
Click to expand...
Click to collapse
That's awesome, were next. They got their security update before us, we just got ours. My best guestimate is in late may early June.