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).
Related
Hi i got upset with the official cm9 nightlies not really being nightlies because they dont have a build server yet. So i decided in the mean time i would just pump out some nightlies myself untill their build servers are up and running. So these builds are completely unsupported from cm with no modifications by me they are just like the official cm9 nightlies and are updated with the latest source before every build. If anybody has an ftp server and would let me use it for a bit that would be cool.
Code:
Normal Discalimer applies. I am not responsible for any damages occuring to your device because of use of this rom or thermonuclear war and blah blah blah
I will start building around the same time every day 5:00 PM EST
Nightlies:
FTP Server is here thanks Korumera
How to install:
1. If coming from different rom wipe system,data,cache.
2. Install rom in recovery
3. Flash gapps
4. Reboot
5. ?????
6. Profit!
Since my Transformer is bricked all donations are extremely appreciated and go into my new TF fund
Add-ons:
GAPPS
Love me some CM9 so far!
Cheers to you!
Hammerfest said:
Love me some CM9 so far!
Cheers to you!
Click to expand...
Click to collapse
Back to you as well had some free time today to set up my build environment now I'm working on AOKP for our Transformers
Sent from my Transformer using xda premium
I hope this one works. The one I dowloaded from Cyanogen mod site nearly bricked me and took ages to get it up and running again,lol.
Thanks dev/uploader
sportsstar89 said:
Back to you as well had some free time today to set up my build environment now I'm working on AOKP for our Transformers
Sent from my Transformer using xda premium
Click to expand...
Click to collapse
That sounds great right there. TIA.
baseballfanz said:
That sounds great right there. TIA.
Click to expand...
Click to collapse
I'm attempting my first build from source as we speak lol
sportsstar89 said:
Back to you as well had some free time today to set up my build environment now I'm working on AOKP for our Transformers
Sent from my Transformer using xda premium
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=jPmb0F00YPE
LightningXCE said:
http://www.youtube.com/watch?v=jPmb0F00YPE
Click to expand...
Click to collapse
Don't get to excited just yet it failed making the ota package and i'm not familiar with how to use the blob tools
Edit: Got it to flash bootlops the VM aborts while trying to load the audio policy from the HAL driver
sportsstar89 said:
Don't get to excited just yet it failed making the ota package and i'm not familiar with how to use the blob tools
Edit: Got it to flash bootlops the VM aborts while trying to load the audio policy from the HAL driver
Click to expand...
Click to collapse
That's still progress, awesome man, I'd love to see AOKP on our transformer
username235 said:
That's still progress, awesome man, I'd love to see AOKP on our transformer
Click to expand...
Click to collapse
Yea well this is a very unfortunate situation i might have bricked my tf heres my thread anybody else fix this http://forum.xda-developers.com/showthread.php?t=1540883
so the question is : is this working?
keyra74 said:
so the question is : is this working?
Click to expand...
Click to collapse
Yes it Is
Sent from my HTC Amaze 4G using xda premium
the thing is this is being compiled from the androidroot.mobi page on github which was updated 2 weeks ago so no real point in nightly when there is no change.
pashinator said:
the thing is this is being compiled from the androidroot.mobi page on github which was updated 2 weeks ago so no real point in nightly when there is no change.
Click to expand...
Click to collapse
1. You still get the updated trebuchet and all the functionality the device pages are just so you can compile it for your device its no like the actually cm its just like the libs and stuff
Installed this ROM. It work and work... fluidity and smooth.
The camera also work well.
Thanks
sportsstar89 said:
Don't get to excited just yet it failed making the ota package and i'm not familiar with how to use the blob tools
Edit: Got it to flash bootlops the VM aborts while trying to load the audio policy from the HAL driver
Click to expand...
Click to collapse
I had a booting AOKP build, but it had problems:
- No screen rotation
- Several GUI bugs
- Slow
- No WiFi or BT (drivers, firmwares were in place)
About the OTA error: you need to modify the script what creates our OTA package, it's in the device tree. You need to add the -no_assert flag to it (functionality-wide), as while CM9 does not use it, AOKP does. And because the device tree was made for CM9, Bumble-Bee, RaYmAn, and the other guys who worked on the device tree did not add this function to this very script.
The exact patch:
https://github.com/hillbillyhacker8...mmit/9ba2af252ec8a70cda9242ca97038e2b3a71c541
Also I'd suggest using hillbillyhacker86's AOKP branch of this device tree. He did some pretty good work there.
---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------
pashinator said:
the thing is this is being compiled from the androidroot.mobi page on github which was updated 2 weeks ago so no real point in nightly when there is no change.
Click to expand...
Click to collapse
If he compiled using the official CM device tree, without MANUALLY checking out the AndroidRoot tree (CM already merged it, and now updates are sent to CyanogenMod/android_device_asus_tf101). There were some updates to it, plus also CM merged some more updates in the main trees, so we get those too.
fonix232 said:
I had a booting AOKP build, but it had problems:
- No screen rotation
- Several GUI bugs
- Slow
- No WiFi or BT (drivers, firmwares were in place)
About the OTA error: you need to modify the script what creates our OTA package, it's in the device tree. You need to add the -no_assert flag to it (functionality-wide), as while CM9 does not use it, AOKP does. And because the device tree was made for CM9, Bumble-Bee, RaYmAn, and the other guys who worked on the device tree did not add this function to this very script.
The exact patch:
https://github.com/hillbillyhacker8...mmit/9ba2af252ec8a70cda9242ca97038e2b3a71c541
Also I'd suggest using hillbillyhacker86's AOKP branch of this device tree. He did some pretty good work there.
---------- Post added at 07:31 PM ---------- Previous post was at 07:24 PM ----------
If he compiled using the official CM device tree, without MANUALLY checking out the AndroidRoot tree (CM already merged it, and now updates are sent to CyanogenMod/android_device_asus_tf101). There were some updates to it, plus also CM merged some more updates in the main trees, so we get those too.
Click to expand...
Click to collapse
Yep ill try it as soon as I fix my tf if you could take a look at my thread in q&a and give any ideas that would be awesome
Sent from my HTC_Amaze_4G using xda premium
I have installed your ROM and everything is working smooth and fine. I only missed YouTube and google maps. I put that back with app extractor. Really like this ROM. I hope you will keep it updated.
Edit: I hope you get your FT fixed soon.
Seen there is an official nightly for today but can't find any change log or anyone talking about. Anyone tried yet? I would but away from my tablet.
Sent from my GT-I9100 using xda premium
New nightly is up
This thread is no longer active. Jomeister plans to continue work on Evervolv. He will open a new thread for that purpose.
Introduction
The purpose of this thread is to coordinate work on the AOSP-based Evervolv 2.2 ROM for Skyrocket (and its sister, T989).
Skyrocket is not an officially supported ROM by Evervolv, but we have fully integrated device and vendor directories in their tree. Therefore we get fixes from the main tree and also have the ability to push fixes to Evervolv's tree. This is something we could never do when we worked directly off the Code Aurora source.
Our desire is to give the dev community a single codebase to coalesce around. Hopefully, with more devs working on the same project, we can progress faster towards AOSP.
To build, follow the instructions here (choose ev_skyrocket-eng at the lunch menu):
https://github.com/Evervolv/android
Or, the short, short version:
Run "repo status" and make sure you have no local mods.
Run "repo sync" and make sure it completes without error.
Run "rm -rf out" to remove any old compiled stuff
Run ". build/envsetup.sh" to set up your environment
Run "lunch ev_skyrocket-eng" to select the target
Run "make -j4 otapackage" (adjust -j option to match your # of processors)
What works:
2D/3D graphics, hw accel of gui, bluetooth, gps, nfc, wifi, sdcard (int+ext), MTP/PTP over USB
What doesn't work:
audio, calls, camera, cell data, sms, anything else you can think of
Issues are being managed on Github:
https://github.com/Evervolv/android_device_samsung_skyrocket/issues
Want a ROM link?
Then follow the instructions to build a ROM! The point, at this time, is to get devs involved in the process. The ROM is not ready for anyone to try out or use at this point. There are many problems left to solve.
Want to help?
Are you a dev with a Skyrocket and a burning desire to get AOSP for your phone? Please, check out Evervolv and start debugging! The Github Issues link above is a great starting point.
Jomeister and RaverX3X graciously agreed to join forces here. We hope other devs join too!
Current Dev Contributors:
jomeister15
RaverX3X
topprospect
Credit and Thanks:
Xboarder56 for the original Evervolv Skyrocket device tree
romracer for the unsecure mods to the ICS kernel
Changes Log:
04/11/12: Posted succint build instructions
04/11/12: Fixed unstable-ness of GUI (link)
04/06/12: Build now boots on its own boot.img (link)
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
BaconStep said:
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
yes because google has released 4.0.4 sources and ota updates to nexus.
wali01x said:
yes because google has released 4.0.4 sources and ota updates to nexus.
Click to expand...
Click to collapse
Sweet!
Sent from my GT-P7510 using XDA Premium HD app
Looks great, will try building/debugging when I get my Ubuntu box up again!
Sent from my SAMSUNG-SGH-I727 using XDA
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
giant420 said:
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
Click to expand...
Click to collapse
No stupid questions here. A fully compiled ROM like the ICS leak obscures a lot of the details about how to build the ROM from scratch. You have to reverse engineer a lot of what Samsung did to compile AOSP, plus how to avoid pulling in too much Samsung bloat code. Hope that helps.
more or less were going to keep as much samsung out of it as we possibly can . Yes u can kang in stuff from the leak but then that actually causes more issues in the long run then doing it right the first time ;P.
bsbachert said:
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
Click to expand...
Click to collapse
I think we as a community should still continue working on things such as CM9 and AOKP in addition to Evervolv, just to give people as many options as possible. The good thing that Evervolv device trees are very similar to those required by CM9 and AOKP, so with a few hacks here and there I'm sure we can get those building as well. I don't know about the other devs, but I definitely have enough time to collaborate on multiple projects, as long as I'm not the sole carrier.
ur killing me. I finally managed to get media server to stay up for msm8660 audio pulled from the leak with jos isotope a4 with some other libs and bins. acdb pulling audio policy was still a problem though.
This is definitely for the better though. I was uncomfortable with all those Samsung libs bins and blobs, especially after staring at them under IDA. like raver said it woulda been a nightmare later on.
This is great though, everyone on the same pile should make this go a lot faster.
im very excited for this.
What's IDA?
Sent from my SGH-T989 using XDA
Wow. This build is going to b epic! Can't wait guys. Nice work so far
LawStud3nt said:
What's IDA?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Interactive_Disassembler
crazy what u can find in those blobs. helps a lot for debugging though
all I know is I love evervolv on my nexus one its super baller... Thanks to all 3 of you guys
Sent from my SAMSUNG-SGH-I727 using xda premium
Any updates? Got ants in my pants waiting for this one!
softballjunkee13 said:
Any updates? Got ants in my pants waiting for this one!
Click to expand...
Click to collapse
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
topprospect said:
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
OK...enjoy the holiday as well!
So here's the story. I built cm9 for the dream/sapphire using files from various devices, one of which is the hero. So out of boredom I built it for the heroc too. I cannot test it or confirm it works.
Info:
Cm9 code from the middle of may (android 4.0.4)
Device and vendor files from github.com/TeamICS
And... that's it.
It should hopefully boot and mostly work. Not sure about audio working. haven't done anything for the camera
http://www.mediafire.com/?je85olw5k6rj7jn - test0
thank you tvall, i hope you saw i gave you credit for the port that i did, ill try this out and let you know
---------- Post added at 08:55 PM ---------- Previous post was at 08:32 PM ----------
from initial testing:
everything works as it should, except for camera (which you already mentioned) and no usb mass storage
with *edit* stagefright and its associated libs from eligorom or the port of cm9 i posted, we should be able to have working video playback
also ill have to retrace my steps as its been a few since i did it but the kernel i included with cm9 and eligorom has minfrees already set at boot, when i remember what i changed ill post it here
im not sure about camera, i think in /lib/hw we need the camera.msm7k.so and probably for good measure the associated libs from eligorom
thank you tvall, you are a god among men
Thank you for testing. We should work together on this (especially since I don't have a hero)
id be proud to work along side you. i have no experience with building from source or even knowing what to do with the source, but i think im pretty resourceful when it comes to tweaking and stuff like that
i did replace the stagefright lib and associated libs from eligorom and software video playback is working with quickpic. i replaced camera stuff and no go on that, but i know there is a way to fix it.
edit: an idea for you if you have the time to look at it (about camera) http://review.cyanogenmod.com/#/c/13317/ and http://forum.xda-developers.com/showthread.php?t=1624018
whoshotjr2006 said:
id be proud to work along side you. i have no experience with building from source or even knowing what to do with the source, but i think im pretty resourceful when it comes to tweaking and stuff like that
i did replace the stagefright lib and associated libs from eligorom and software video playback is working with quickpic. i replaced camera stuff and no go on that, but i know there is a way to fix it.
edit: an idea for you if you have the time to look at it (about camera) http://review.cyanogenmod.com/#/c/13317/ and http://forum.xda-developers.com/showthread.php?t=1624018
Click to expand...
Click to collapse
I don't have internet at home currently.. so.. feel free to mess with this rom while I'm gone. I'll look into the camera when I can
Would love to see this work out! Great work dudes
Sent from my HERO200 using xda premium
scataldo721 said:
Would love to see this work out! Great work dudes
Sent from my HERO200 using xda premium
Click to expand...
Click to collapse
I plan on making this the best rom I can, but I don't have a heroc, so I might not do too well (donations are much appreciated!). Developing blindly is difficult.
If you ever need a tester ill gladly be one PM me!
Sent from my HERO200 using xda premium
Anyone interested in aokp?
nice work will try . Thanks for your contribution .
tvall said:
Anyone interested in aokp?
Click to expand...
Click to collapse
Differences between that and CM9?
Shakes27 said:
Differences between that and CM9?
Click to expand...
Click to collapse
I've never actually used aokp. It has a lot more ui customization. And unicorns. Seriously, unicorns.
tvall said:
I've never actually used aokp. It has a lot more ui customization. And unicorns. Seriously, unicorns.
Click to expand...
Click to collapse
No joke on the unicorns? GIMME NOW!
Sent from my SPH-D710 using XDA
So.. I built aokp for the g1. The heroc doesn't want to finish building... but it can probably be fixed
tvall said:
So.. I built aokp for the g1. The heroc doesn't want to finish building... but it can probably be fixed
Click to expand...
Click to collapse
One of the main reasons to use the cm9 base is the fixes for msm7x27 and armv6. You'll have to port over or use the cm repos for the framework and dalvik.
Shelnutt2 said:
One of the main reasons to use the cm9 base is the fixes for msm7x27 and armv6. You'll have to port over or use the cm repos for the framework and dalvik.
Click to expand...
Click to collapse
Already did all the dalvik changes. Won't even build without that.
tvall said:
Already did all the dalvik changes. Won't even build without that.
Click to expand...
Click to collapse
I'm not sure what your errors are, but it might be easier to just change the device to armv5-te (I think its -te) instead of armv6j. I know before cm posted sources we could build the aosp with armv5 and a few fixes. Check the TEAMICS_FIXES repo and look under the old fixes you might still need them for AOSP.
Shelnutt2 said:
I'm not sure what your errors are, but it might be easier to just change the device to armv5-te (I think its -te) instead of armv6j. I know before cm posted sources we could build the aosp with armv5 and a few fixes. Check the TEAMICS_FIXES repo and look under the old fixes you might still need them for AOSP.
Click to expand...
Click to collapse
The errors are related to selinux, which is weird because I built for the dream with a similar device folder without that error... I'll work on it later.
just figured i'd check in.
havnt had alot of time here lately, but hopefully here soon i will. here are the stagefright libs that allow for software playback of video files. tvall please try these out on your g1, see if it works for you. i use quickpic to play media files in ics, its the lightest player i can find.
attached stagefrightlibs below (not flashable, just a folder, push lib files with adb anybody who wants to try these)
upon looking at your kernel, i think we are going to have to go through both my eligorom kernel and your kernel and match them up, with your rom and my kernel usb mass storage pops up, but unmounts the sdcard instead of working correctly. im looking into it right now, probably a really easy fix. also alot of minfree stuff is absent in your default kernel, so we will have to figure that one out too.
when i get a chance, ill package up my kernel into a flashable zip, but for now its attached as a non flashable one for reference only.
edit: wow i said kernel 6 times lol
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.
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/system.img.gz md5sum: 29a6c707d25520c28528b502bb190c7e
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
jimbridgman said:
Here is the system image from MY SGS 3, I thought one of our other devs might want to turn this into a ROM. I would do it, but I am a little swamped at the moment with after hours android dev work.
If someone has not taken a stab at it by the time I am back in here more "permanently", I will make my attempt at porting it over. You will need to grab a script that they use for CM, to grab the files off of your phone, also here is a good reference on porting as well.
SGS3 ROM to port:
https://dl.dropbox.com/u/45576654/system.img
Porting guide, a very nice one at that:
http://forum.xda-developers.com/showthread.php?t=1512319
Have some fun.
Click to expand...
Click to collapse
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
EDIT: i assume the gs3 is GSM correct?
lkrasner said:
I might take it on (you know me, that means I will try and fail and leave it dead most likely), but how the hell will we even get it to boot without at least an ics kernel? will we just have to wait until we get the update?
Click to expand...
Click to collapse
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
It is in the system.img file I posted.... just mount it as an iso and you can pull out /system/app and grab the Svoice.apk from there.
kc92iyngr said:
Can you post the built in apps of sgs3 eg: s voice.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
jimbridgman said:
Try kexec, That is how the cyanogenmod team is "dual booting" for testing roms... who cares if it is just one proc for a test boot.... Once you can POC it with a 2.3.6 kernel, then you know you are on the right track, and can do a test flash. The only real issue you might have is that the source seems incomplete to me.
I know this because I tried to compile it and had all kinds of issues with missing pieces. I have successfully compiled two kernels that I am testing on my SGS 3 at the moment (one overclocked, the other under volted).
Just make sure you go and grab the arm-abi tool kit, this is the one I use, from
codesourcery:
http://www.mentor.com/embedded-software/codesourcery
All you need is the light version. It might take some work, but you may be able to merge the ICS kernel code (it is posted as a sticky higher up ^^^) with the MB/ME865 kernel to get what is missing. There are some how-tos out there to do it.
Yes the AT&T version is GSM(HSPA+)<E
Click to expand...
Click to collapse
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
lkrasner said:
I'll pull them out for you later today, I am about to tear this apart. it is downloading crazy slow though. I'm on an island in Vermont, so as you might imagine, my internet is not fantastic.
---------- Post added at 01:59 PM ---------- Previous post was at 01:46 PM ----------
Am I right that is SHOULD boot on a stock ICS kernel, like what came from that leak, if so, I can have someone that is running that test it out, and make sure the system is right, then I can build a kernel to run with kexec until we can get a real update.
I am new to porting and sort of to kernel building so tell me if this process sounds right for this.
1. fix up the gs3 system with our proprietary files -thats easy, I know how to do that
2. have someone that is running an ics kernel test it if possible
3. if that works it means I just need a stock ics kernel to run in kexec, which shouldn't be too hard because we should be able to use the me865 source and modify it to work with mb865. If it does not work, kernel building starts from scratch, which is were I will have to do some more research, and any help from you or others would be helpful.
My other question is how do we even load the new kernel with kexec? wouldn't we need this to boot first, then we can swap the kernel? Or is there a way to load up both at the same time?
I think I will set up a WIP thread for this if you don't mind. feel free to PM me if you don't want to post stuff here.
Thank you so much for all your help, and have fun with your new toy
Click to expand...
Click to collapse
Yeah I think that is a good start. Take a look at this link, the guys from team epic that do cyanogenmod ports have come up with a way to use kexec to test booting thier kernel and roms. You might PM one of them, I have not gotten to that point yet, plus these guys are working on the Sprint version, of the SGS3, but I am sure they can explain how they are doing this with kexec. These guys are on XDA, I have chatted with them on a couple issues I was having.
http://www.epiccm.org/
Oh, P.S.
Here is how to compile the "stock MB/ME865" kernel:
1. How to Build
- get Toolchain
From android git server , codesourcery and etc ..
- arm-eabi-4.4.3
- edit Makefile
edit "CROSS_COMPILE" to right toolchain path(You downloaded).
EX) CROSS_COMPILE= $(android platform directory you download)/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ex) CROSS_COMPILE=/usr/local/toolchain/arm-eabi-4.4.3/bin/arm-eabi- // check the location of toolchain
$ export ARCH=arm
$ make m2_att_defconfig
$ make
2. Output files
- Kernel : arch/arm/boot/zImage
- module : drivers/*/*.ko
3. How to Clean
$ make clean
Just make sure the toolkit is pointed to the install of the codesourcery toolkit I linked in the above post.
P.P.S
Your defconfig might be another pointer name, that you will have to find out for sure. You know the one above called m2_att_defconfig.
For the beginners don't try the rom,you might kill your phone!
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Glad to see you back around here, but lets not even give anything towards JB until we get ICS. if you are interested in helping with that, send me a PM, I have made some progress with cm9 (as in it boots fine, and i have some ideas for the radio).
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
Yay! Cogeary's back! Good to see you around again...
Sent from my phone's mind
cogeary said:
I'd like to give this a try as well . Thanks a lot for all the help!
If/when we get this to work, do you think a JB port won't be too far behind? How big are the differences between stock ICS and JB kernels?
Click to expand...
Click to collapse
ICS to JB is going to be a much smaller kernel jump, but there will be a HUGE performance increase due to project butter which is now officially part of Jelly Bean.
The key to running something like this is to get a kernel compiled and running with kexec, even though it is just 1 proc, it is a good way to get started. Ports will be much easier if you do some merging of the changed code in newer kernels and do merged kernel. There are instructions for doing a kernel that is merged from 2 sources to get a complete kernel.
Now this will just work for testing and porting, and the actual ICS or JB install from at least a leak will be needed to actually run the port, but you can get ahead of the game by doing what I have mentioned.
Well going to give this a go in a few days doing some maintenance on my computer but will get back with something (hope not a bricked phone) .....
(off topic ranting)
Hate to say it at this rate what getting close to a year since Ics release Jb might just be a pipe dream..... Think I am growing grey hairs waiting for something to give here..... Without bootloader unlock I feel so useless (Yea I could make a recovery image with all the bells and whistles but I got bigger plans).....
Downloaded so I could tinker with some files. Thanks for sharing.
Sent from my SAMSUNG-SGH-I997 using xda premium
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
sure, no problem, give me a bit, my internet is slower than hell where I am right now.
EDIT: of course I didn't add it to dropbox originally, so now it is uploading to google drive. It just hit 1%
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
cogeary said:
Lol. Just my luck for the dropbox account to be temporarily shut down when my download's on 99%.
Well I guess I'll just sit here and wait. Unless anyone wants to be so kindly awesome enough to mirror it?
Click to expand...
Click to collapse
I uploaded it to my Drive right away after downloading - try this for SGSIII ICS: https://docs.google.com/open?id=0B-CZ8hXV8qOiVGtjOHZ3ZEg5eFU
P.S. - I also have a JB dump there, if anyone's interested: https://docs.google.com/open?id=0B-CZ8hXV8qOiSkc3QkE1Y0ZsRkU
EDIT: make that 2 jelly beans: https://docs.google.com/open?id=0B-CZ8hXV8qOiS2QtcG41QUh4R1k
...I was pretty active during the I/O hype last week...
jimbridgman said:
Yeah I got the dreaded e-mail from dropbox last night....
I will see what I can come up with for a hosting solution for this. I will update the OP once I have something.
Click to expand...
Click to collapse
Why not try Filedropper or Mediafire?
MagicXB said:
Why not try Filedropper or Mediafire?
Click to expand...
Click to collapse
I am actually trying to get my recognized developer cert on here and get free premium access to xdafilehost, that all the recognized devs get access to.
We will see if I get it or not. If not I have other options, but things like filedropper will not do, I already looked into it