I've noticed a few CM7 ROMs popping up for the Droid Eris, and wanted to take a shot at compiling a ROM. Unfortunately, the Droid Eris isn't a supported device in the Cyanogenmod downloads, as far as I can tell. Which source is being used for these ROMs? is it a generic source, or is it different for each device?
ryurabbit said:
I've noticed a few CM7 ROMs popping up for the Droid Eris, and wanted to take a shot at compiling a ROM. Unfortunately, the Droid Eris isn't a supported device in the Cyanogenmod downloads, as far as I can tell. Which source is being used for these ROMs? is it a generic source, or is it different for each device?
Click to expand...
Click to collapse
This link should help, it's the cyanogenmod link to the newest nightly build which is RC1, it's the same build that Workshed based him GB rom on.
http://download.cyanogenmod.com/?type=RC&device=heroc
And here is the link to the newest "experimental" builds.
http://download.cyanogenmod.com/?type=nightly&device=heroc
To find these easily just go to www.cyanogenmod.com and at the top right of the website, click on "Devices" and then find the HTC Hero (CDMA) and click on that. Hope this all helps !
OKAY! so we ARE using the Hero CDMA build! Thanks alot :3 topic can be locked now.
ryurabbit said:
OKAY! so we ARE using the Hero CDMA build! Thanks alot :3 topic can be locked now.
Click to expand...
Click to collapse
workshed is not using the Hero CDMA build for GSB. He is compiling directly from source. If you look at the source, there are vendor trees for official devices included in the source. workshed has a vendor tree for the Eris that he uses with the source to build his ROM.
Take a look at EasyDev and how it works. It will give you an idea of what's going on.
tazz is taking the Hero CDMA build and making it work for the Eris. The two devices are so close, that porting from the HeroC pretty much always works well.
could I compile this in 32-bit linux? or would it have to be 64?
ryurabbit said:
could I compile this in 32-bit linux? or would it have to be 64?
Click to expand...
Click to collapse
64 only from now on is my understanding...
ryurabbit said:
could I compile this in 32-bit linux? or would it have to be 64?
Click to expand...
Click to collapse
gnarlyc said:
64 only from now on is my understanding...
Click to expand...
Click to collapse
Yes, if I recall correctly it was from 2.3 (Gingerbread) on that requires 64-bit Linux to compile.
I was just checking cause the CM Wiki had instructions for building on 32, but whenever I'd try to compile, it'd error out. So I wound up switching to 64-bit.
Related
Since we now have kernal source any of you's think. We will be getting an official cm base rom. Me particular. I like cm7 any ideas ?
justin lamantia said:
Since we now have kernal source any of you's think. We will be getting an official cm base rom. Me particular. I like cm7 any ideas ?
Click to expand...
Click to collapse
CM isn't supporting the msm8660 for cm7 that's why it took me so long to get it running and my cm9 will be merged once GSM is fixed
sportsstar89 said:
CM isn't supporting the msm8660 for cm7 that's why it took me so long to get it running and my cm9 will be merged once GSM is fixed
Click to expand...
Click to collapse
Thanks. Unfortunately I knew that I was hoping for some good neWS for cm7. Btw ur work isssss great.
I have had experiences with gentoo and wish to try my hands at developing my own AOKP rom for a chinese tablet that is unsupported.
I am currently syncing my repo and wish to understand more before I proceed.
What will be the easiest way to get Android running if I compile AOKP? Given that the tablet runs ICS at the moment, will it work if I compile AOKP and port the existing kernel over?
I have also gotten my hands on the source codes for the tablet.
Do you have a device tree?
If not, first you should create one.
Then only you can compile android.
adil_ said:
Do you have a device tree?
If not, first you should create one.
Then only you can compile android.
Click to expand...
Click to collapse
I highly doubt that there is an existing device tree. Now comes the noob question: How can I check if there is an existing device tree???
Anyway, I have been extensively reading up on building android and gotten the AOKP sources and original manufacturer source. Am I right to say that as long as I can compile AOKP, I should be able to boot using an existing kernel??
As for the the two sources, should I copy over the original devices and hardware folder to the AOKP source before I build so as to ensure a compatible build???
tobyhund said:
I highly doubt that there is an existing device tree. Now comes the noob question: How can I check if there is an existing device tree???
Click to expand...
Click to collapse
Google.
Anyway, I have been extensively reading up on building android and gotten the AOKP sources and original manufacturer source. Am I right to say that as long as I can compile AOKP, I should be able to boot using an existing kernel??
Click to expand...
Click to collapse
No it is not right to say. While it is possible you will probably need to do extensive debugging along the way.
As for the the two sources, should I copy over the original devices and hardware folder to the AOKP source before I build so as to ensure a compatible build???
Click to expand...
Click to collapse
Depends on what source you are talking about. What source do you have exactly?
You could try my thread here: http://forum.xda-developers.com/showthread.php?t=1935162
It does have some nice links to.
As stated in the cm 10.1 dev thread lets keep the general CM discussions here instead of cluttering the dev thread.
Great idea - now we can have all the misguided, misinformed speculation we want as to what hurdles have yet to be cleared before the DNA gets official CM nightly support
jk
Haha, exactly.
Actually, I think efforts might soon be underway to port straight AOSP as well I hope what I've heard (I can't give details, so please don't ask) comes to fruition.
That'd be great. I've been trying to learn more about programming and the build system so I can start helping out with some of it. I've setup ubuntu and sync and build cm every couple of days and I've been messing with building aokp since its based on cm.
AOKP, PA, PAC ROMs me want
Also some AOSP kernels as well
Sent from my TF300T using Tapatalk 2
I made a few changes and aokp started to build but I came across an error and haven't had time to look into it. If I get it built I'll try to learn some more about git and upload the source
skynet11 said:
Actually, I think efforts might soon be underway to port straight AOSP as well I hope what I've heard (I can't give details, so please don't ask) comes to fruition.
Click to expand...
Click to collapse
Why pure aosp as opposed to CM?
123421342 said:
Why pure aosp as opposed to CM?
Click to expand...
Click to collapse
Because a lot of popular ROMs out there are based on AOSP rather than on CM. Besides, there's always room for both right?
I'd love to try pure AOSP. I've always had HTC devices so I never got the pure Android experience.
123421342 said:
Why pure aosp as opposed to CM?
Click to expand...
Click to collapse
because I want android and not all the stuff that comes with CM, if I want themes and mods ill do them myself
Does anyone have any resources that break down the build process?
I'm pretty excited for the 10.1 rom to become a daily driver. Once it's complete I hope to see possible other roms that are desensed... I'm sick of sense! I want some unadulterated android (or close to it)!
why would you want an aosp kernel? how are they better?
atishpatel2012 said:
why would you want an aosp kernel? how are they better?
Click to expand...
Click to collapse
Sense kernels won't work on aosp and the stock one they included in CM can't be overclocked or undervolted.
Nowak4G said:
Sense kernels won't work on aosp and the stock one they included in CM can't be overclocked or undervolted.
Click to expand...
Click to collapse
The kernel we are using right now is our stock kernel with cm commits. It doesn't include overclock or any other features because they could cause more bugs. Better to work all the bugs out of cm before you start doing things that could introduce more. Cplamer has already said that he has run a custom kernel with cm on his DNA so it is definitely going to happen. Just have to wait or build your own kernel unfortunately.
amathophobia said:
The kernel we are using right now is our stock kernel with cm commits. It doesn't include overclock or any other features because they could cause more bugs. Better to work all the bugs out of cm before you start doing things that could introduce more. Cplamer has already said that he has run a custom kernel with cm on his DNA so it is definitely going to happen. Just have to wait or build your own kernel unfortunately.
Click to expand...
Click to collapse
The other reason is because they're making so many changes to cm right now to get it working that a new kernel would have to be released for every update. I believe T1gartist has been running cm oc'd with a custom kernel as well
Sent from my Nexus 7 using Tapatalk 2
If you have the source it's not hard to add overclocking.
I'm not a dev or anything but I built AOKP
TheDanimal said:
I'm not a dev or anything but I built AOKP
Click to expand...
Click to collapse
Can u upload the build.
I wud like to test it out.
What all features are working ? Are all" Whats Working" features CM10.1 working for it ?
Sorry for asking all these questions.
BTW, u should create a new thread in Orig. Android Dev. with AOKP build :victory:
Hello, I'm searching for totally clean ROM. That means ROM builded from source code without any improvements or Google Edition ROM. Is it possible to build this ROM? And what do I need? And what cloud be barrier? Thanks for reply.
Whats the problem with CM?
Sent from my HTC Desire X using xda app-developers app
banan1 said:
Hello, I'm searching for totally clean ROM. That means ROM builded from source code without any improvements or Google Edition ROM. Is it possible to build this ROM? And what do I need? And what cloud be barrier? Thanks for reply.
Click to expand...
Click to collapse
You would need, command and skills on coding, Ubuntu or any linux os, and a source.
micu13 said:
Whats the problem with CM?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
there is already a project and it aint anywhere near completion maybe or perhaps hes not fond of cm
Sent from my HTC Desire X using xda app-developers app
I dont have any problem with CM. But I think that it is a little bit unstable. I don't know anything about android development, but at first I think that it works like windows or linux. You have OS and drivers and together it works well. Where is problem with build clean android rom + add drivers?
banan1 said:
I dont have any problem with CM. But I think that it is a little bit unstable. I don't know anything about android development, but at first I think that it works like windows or linux. You have OS and drivers and together it works well. Where is problem with build clean android rom + add drivers?
Click to expand...
Click to collapse
It's not exactly like you said. And for clean rom, its name is AOSP. And when our CM will be bugfree also an AOSP rom, or like you name it a clean rom, will be available.
xpirt
great. So now I'm waiting for AOSP rom. Can I donate somebody for support in development?
banan1 said:
great. So now I'm waiting for AOSP rom. Can I donate somebody for support in development?
Click to expand...
Click to collapse
Atis112 is the man
xpirt
Hey guys, I'm compiling SlimKat for this device right now, and since I don't own the device, I'll need testers...so, who's interested in the fun?
pandasa123 said:
Hey guys, I'm compiling SlimKat for this device right now, and since I don't own the device, I'll need testers...so, who's interested in the fun?
Click to expand...
Click to collapse
I always like the fun....pm me
pandasa123 said:
Hey guys, I'm compiling SlimKat for this device right now, and since I don't own the device, I'll need testers...so, who's interested in the fun?
Click to expand...
Click to collapse
I am also in..let me know when ready for testing.
Kernel!?
How is it possible without xiaomi releasing the kernel source?
sivasagaru said:
How is it possible without xiaomi releasing the kernel source?
Click to expand...
Click to collapse
People have ported cm11. Use their boot.img
....i having such a difficult time with this...there are so many build errors because of the lack of cm kernel source...
pandasa123 said:
....i having such a difficult time with this...there are so many build errors because of the lack of cm kernel source...
Click to expand...
Click to collapse
Cm posts all their kernel source. Slim roms require a custom kernel. I build slim for a few devices and cm kernels seldom work so without the kernel source for the device it may not be an option.
I'm in! haha been using SlimKat on my i9100G so quite some times already
pandasa123 said:
....i having such a difficult time with this...there are so many build errors because of the lack of cm kernel source...
Click to expand...
Click to collapse
download the caf kernel sources (can't remember which tag. 3.5.2.2?), map the kernel source from the device config as usual.
then make bootimage (which will install the headers),
finally, remove the configs for source built kernel, and map the dt image and zImage
the compiling is making it further and further...hopefully it won't break
BUILD FINISHED! http://forum.xda-developers.com/xiaomi-mi-3/orig-development/rom-slimkat-t2846759
I'm pretty sure I can build OmniROM. Anyone interested in that? (High chance of it not working though)
don't worry Just do it
pandasa123 said:
I'm pretty sure I can build OmniROM. Anyone interested in that? (High chance of it not working though)
Click to expand...
Click to collapse
Did I just read Omni Rom ? 200 % up for it !! let it boot or not .. But I'll test for sure
TheDj408 said:
Did I just read Omni Rom ? 200 % up for it !! let it boot or not .. But I'll test for sure
Click to expand...
Click to collapse
Lol I'm trying to get enough money for a small server. My laptop is super full (see SIG). But I want to build omni and 2 other ROMs for the cancro.
I would advise all to read this. Action will be taken in the next few days.
http://forum.xda-developers.com/xiaomi-mi-3/orig-development/attention-devs-t2848736
zelendel said:
I would advise all to read this. Action will be taken in the next few days.
http://forum.xda-developers.com/xiaomi-mi-3/orig-development/attention-devs-t2848736
Click to expand...
Click to collapse
Ok guys, I am petitioning Xiaomi. Help me keep some development alive.
https://www.change.org/petitions/xiaomi-release-mi3-kernel-source
LET'S GO!