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?
NOTE: THIS ROM IS NOT CURRENTLY USABLE! DO NOT FLASH IF YOU DO NOT KNOW WHAT YOU ARE DOING
Ladies and gentlemen of XDA, I present to you ICS on the TF101! This ROM is currently very much still in development, and is not usable in it's current state, but it boots! This is more or less a proof of concept at the moment.
What's not working:
Display has a green overlay most of the time
Touchscreen
Wifi
Camera
HW Acceleration
Pretty much everything else
What does work:
adb
Boots to launcher
Touchpad on the dock (currently only method of input)
To install:
Download the system blob from http://mirror.mostoftheinternet.com/android/ROM/tf101/system-AOSP-20111230.blob.bz2
Boot into recovery
Do factory reset
Mount /sdcard using the menu
Use adb to transfer the blob to the device
Code:
adb push system-AOSP-20111230.blob.bz2 /sdcard/blob.bz2
Enter device shell
Code:
adb shell
Decompress blob and apply
Code:
bzcat /sdcard/blob.bz2 | dd of=/dev/block/mmcblk0p4
Reboot and wait for it to install
Done!
If you are able to contribute at all, please let me know. The Git repo for this is at https://github.com/Deathisfatal/android_device_asus_tf101/tree/cm9.
Dev notes:
Most of the random crashes (and the green colour) seem to be caused by an issue with the graphics
Eventually, I plan to move to CM9 once they move closer to release
Screenshot! (yay, green...)
http://mirror.mostoftheinternet.com/images/ics.png
this
is
sex
Congrats
Sent from my MyTouch_4G_Slide using xda premium
Are you going to setup a repository for this? I was actually planning on starting a port of my own but I would love the opportunity to jump in and work with you.
Already have, forgot to add it to the post
Thanks for the support, guys.
Nice to finally see even an early build as this, well done i`ll be keeping an eye on this thread
Deathisfatal said:
Eventually, I plan to move to CM9 once they move closer to release
Click to expand...
Click to collapse
This would make my day! If we manage to get CM9 to start working, I would love to help try or try to be the main man behind porting MIUI (English Site). I've helped a decent bit with porting it to my phone (Samsung Epic 4G). From everything i've seen so far the kernels of CM7 and MIUI are pretty much interchangeable, so it should be a fairly easy transition if CM9 functions. I don't know squat about kernels, so i wouldn't be of any help there though.
UH i had this like 3 weeks ago, but didn't post cuz it sucked so much.
Here's mine, no green stuff either.
I also didn't post it because it's a straight up kang of the Iconia guys' but whatever.
LOL
Thanks to OP for your hard work...
www.scienceprousa.com/jcarrz1/icstest.zip just flash in clockwork but don't expect much...........
Mind sharing your vendor files, jcarrz1?
Deathisfatal said:
Mind sharing your vendor files, jcarrz1?
Click to expand...
Click to collapse
Nope cause it's a straight-up kang of the iconia guys'. And they took their source down because n00bs b crazy.
I really admire that you actually have a device tree and stuff, I'm too inexperienced to do that.
Nice!
jcarrz1
Maybe this may help? https://github.com/CyanogenMod/android_device_asus_tf101
Was going to start an ICS port today as well so I'll be forking your branch and hopefully helping out. Glad we are going to get some progress on this!
arayray said:
Maybe this may help? https://github.com/CyanogenMod/android_device_asus_tf101
Click to expand...
Click to collapse
My original code is a fork of that. Their repo is pretty incomplete.
Was going to start an ICS port today as well so I'll be forking your branch and hopefully helping out. Glad we are going to get some progress on this!
Click to expand...
Click to collapse
Excellent!
Deathisfatal said:
My original code is a fork of that. Their repo is pretty incomplete.
Click to expand...
Click to collapse
Yeah its pretty outdated... Lets get a community effort here..
Good to see a start on this, a bit later than expected!
Sent from my Transformer TF101 using xda premium
For the graphics drivers, as the tf101 uses the same SOC as the xoom, it might be possible to pull the tegra2 drivers from google's wingray aosp sources (found here)
First of all for your work
You know what i dont get is this
http://phandroid.com/2011/11/27/asus-transformer-not-prime-gets-early-ics-port/
where is bumbledroids work?(this was november still)
i am a total retard when it comest od developing but if you ever need any beta tester i have loads of experience on rooting/romming devices an am in possesion of a SBK1 asus transformer with keyboard.
looking forward to giving it a go
Sent from my Lumia 800 using XDA Windows Phone 7 App
Are you compiling against AOSP or CM9?
telsk said:
First of all for your work
You know what i dont get is this
http://phandroid.com/2011/11/27/asus-transformer-not-prime-gets-early-ics-port/
where is bumbledroids work?(this was november still)
i am a total retard when it comest od developing but if you ever need any beta tester i have loads of experience on rooting/romming devices an am in possesion of a SBK1 asus transformer with keyboard.
Click to expand...
Click to collapse
Right, and if the cyanogenMod device tree for tf101 is by bumbledroid then why doesn't touch work yet?
jcarrz1
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.
Andromadus - Test Builds
To start with here you will find test versions of ROMs built by me from the Andromadus github repo http://github.com/Andromadus, think of them along the same concept as nightly builds just not every night These are development ROM's, if you want to run bleeding edge development ROM's and at least know how to use adb and logcat then you might find something of interest here. If you require something that works 100% of the time all of the time then this might not be for you. That said you can always give it a try and if it doesn't work restore your previous nandroid backup!
What IS Andromadus?
Initially it was a group of people who got together to make ICS work on the HTC Desire Z because nobody else seemed to want to support devices with physical hardware keyboards/trackpads. Whilst the idea stays the same It has grown slightly to support some other hardware and some of the work we have done is now used in many other devices. Andromadus builds of CM10 or CM10.1 are basically CM sources with a few additional tweaks or additions to support our phones.
1. New versions will be added as and when I feel there are enough changes to warrant one, don’t ask when the next version is coming.
2. If we decide to release a "Stable" version of these roms they will be published in another Andromadus thread.
Direct all your queries with release versions to that thread and in the same vain do not discuss these releases anywhere but here.
3. I will do as best I can to answer questions but if you don't get an answer from me I'm sure somebody else will be along to help. Help each other and I have more time to spend fixing things!
4. Don't ask for what's changed since the previous version, have a look at the recent submits on the Andromadus github if you want to know or wait for the mini changelogs when I post a new release.
5. If there is something in particular to test it'll be mentioned!
6. As always if you didn't wipe between installations then at least verify that the problem exists on a clean install before posting here. Nandroid/superwipe/install/check at the end of the day you can always restore your nandroid if the problem is reproducible on a clean installation. If you can't be bothered to try this then I really can't be bothered to try to help you :>
7. All that said ensure you make a nandroid/backup before hand. I take no responsibility for what you do to your phone with these ROM.
8. Whilst I can't stop you I would rather these builds were not used as a base for any ROM/MOD/ETC. The source is all available if you want to do your own builds with which you can do whatever you like.
9. Tell us what works/what's worse/what's better but don't ***** when something breaks or isn't fixed yet, report it and move on.
10. Sometimes people forget that we do this for fun, for ourselves, and sometimes your super important issue is way down on our personal list of things to be fixed.
If you ignore any of the above you will in turn be ignored.
Now that's all out of the way as always have fun
As usual you need to flash the ROM then GAPPS.
Checkout http://andromadus.flinny.org for links/files/previous changelog's
This a team/community effort, I'll not list everyone who has helped along the way here that list is in the beta thread but I will say thanks to all of them again and obviously anyone that has been missed.
Current Version changelog
CM10 build 133
There was an issue with the backup tool in the last build that will break gapps and your account's etc when flashing this build, the solution is to re-flash gapps at the same time as the rom and you should be fine. This build should fix it so that the next build will work as it should
Changes.
Synced with CM - Again not many changes upstream.
Basically everything relevant to our phones up to the 4th of February in the following has been merged
http://review.cyanogenmod.org/#/q/status:merged+branch:jellybean,n,z
Kernel updated to Andromadus Current - 3.0.62
might need this
First
Its Awsome, Running it since last 3 days
Great
And maybe I didn't go to sleep. Maybe
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
I get one more rom to base..
BTW my camera fix can be a temp fix for camera
Great :good:
- EDIT -
Wait ! Does It Says Kernel 3
the camera issue atm is kernel, i dont think it will help your fix, you can try...
Edit:
Yeah, it says kernel 3
Yup, this ROM is based off the kernel 3 source by Andromadus. Who needs HTC?
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
Woah?! I thought i was in the wrong section for a moment! Great work!
Alternative upload than goo.im?
What the HELL!? Superkid is back, with Kernel 3!
Does I understand it right, that this is a real Kernel 3 compiled for desire s? Not a port? From wich source?
Unbelievable!! Will testing right now!
Andromadus team took the primou source and changed it to work with our device
Guys, remember, its all on alpha/beta.. kernel and rom!
After all, is the first aosp rom with kernel 3 for saga
Is the jerkiness normal? I flashed over CM10. Will a full wipe fix it?
Sent from my Desire S using Tapatalk 2
Good job man! Keep it up!
Iztipkano sa Dizajr S BRE!
Nice
Nice!
The third JB Rom.
I MUST try it!
But I need my cam. So if this work I will flash it.
Source of kernel released :
http://forum.xda-developers.com/showthread.php?p=29552861#post29552861
https://github.com/Flemmard/htc7x30-3.0
have fun and push fixes!
My congrats on that Rom.
I have a little Problem with play store...my apps arent there and bought Jones are like not bought.
Other than that.....
WOW
Sent from my Desire S using xda app-developers app
Guss one of the legends is back.........with a bang working his magic.......
Sent from my HTC Desire S using xda premium
dan-fish said:
Is the jerkiness normal? I flashed over CM10. Will a full wipe fix it?
Sent from my Desire S using Tapatalk 2
Click to expand...
Click to collapse
You can try.
This is because the kernel 3 is not optimized yet
Tapatalked from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!!!
The first Kernel 3,:good:,thanks
OMG!!! Kernel 3... That's cool.
Must be a tremendous amount of work by the dev.
Thx to dev and superkid. :good:
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.