Related
Hey guys,
I need developers who are dedicated and willing to help startup this Else Intuition port to the HTC Hero Community. Is anyone currently working on this? If not, let's get started!
Take a look at this.....
http://mobile.engadget.com/2009/10/...mobile-unveil-else-intuition-the-linux-based/
<<Video>>
http://www.youtube.com/watch?v=l6Au8mfkzbo&feature=related
interesting. is there a ROM out?
I remember looking at that last year.
anyone know of any developers willing to help port??...
No there isn't a ROM out that I know of. Still researching trying to get a source or something...lol
Dude, then why are you trying to rally devs? lol Get the source first.
This is just a youtube link lol, its impossible to even attempt porting without having anything to port.
This is still experimental so I don't think we will get our hands on it any time soon. If it really is a Linux based OS and we get the source, a port is probably possible.
Most are convinced its vaporware... you can't port anything without something to port it from.
I've been an Android user for a couple of years now, and I've built my own build environment so I can build my own ROMs, nothing fancy and for the public, just something I can do and learn more about the whole process myself in a hands-on way.
I'm not very familiar with Git, specifically cherry-picking items. I was wondering if anyone had some good resources that explain how one cherry-picks and builds that into their own ROM. I've been looking around but can't really seem to find something that explains HOW to do it and build it into a ROM, most of the posts/pages I've found say "Hey, I cherry-picked this" or "Use Git and cherry-pick it".
I'm still looking around and learning quite a bit about Git, but was wondering if anyone had a site that they preferred or would recommend for someone looking into making their own custom kangs (something other than Google).
Here you are!
http://gitref.org/
Awesome, thanks! I didn't come across that one. I've been checking out the Git Community Book and a couple other wikis, but this one's new to me. I'll check it out.
Yeah, I mean you can find all sorts of things over google, but that site is pretty good as well
I guess my main thing was (is), I used the code from Cyanogen's Gerrit Review for "cherry pick", and it looked like it grabbed what I was trying to grab, but I did a build and those commits weren't in there, so I know I'm missing a step somewhere between running the cherry pick command and building the ROM.
Oh ok, yeah even googling certain git commands such as cherry pick helps
Sent from my HTC Sensation 4G using XDA App
Guys,
I have forked some aries AOKP device and CM9 Kernel repos.
As I stare at the screen, is there any possibility of assistance.
Also, if anything, can you tell me where you guys started in order to port from aries.
I figure that this is better than trying to port a rom. (Using source)
I guess as I have stared at Acid repos, i have learned a bit, and I think I might be ready to take on such a project.
Again, any help would be appreciated. Especially from our 2 heroes, Max Fierke, and Bryan Hundven, who have helped us turn our phone's development rate in a few months from 0 to 10(based on a scale of 10).
What I plan to do is add the defconfig from the existing gb source code. Later, I will start modifying the source files to our needs.
anyone?
airfluip1 said:
anyone?
Click to expand...
Click to collapse
I'm not from team acid but try looking at vibrant/i9000 ICS source and study it as their phone is similar to ours.
-sent from an UNBRICKABLE force
I don't think we should bite off more than we can chew.
Have you tried sending the members a pm? That might be more effective.
adobrakic said:
I don't think we should bite off more than we can chew.
Click to expand...
Click to collapse
are you portraying that I can't do it.
Well, i want to learn if anything.
Also @ trolls, i am just playing with adobrakic, not being mean.
No, that's not what I was implying. If you, or other members, have the time to devote to this then great. But I feel that Max, Bryan, and the majority of other developers of our phone, are already working with a lot as it is. Perhaps our efforts should be concentrated on those ROMs at the moment. That's just my opinion, however.
Sent from my SGH-T959V using XDA
adobrakic said:
No, that's not what I was implying. If you, or other members, have the time to devote to this then great. But I feel that Max, Bryan, and the majority of other developers of our phone, are already working with a lot as it is. Perhaps our efforts should be concentrated on those ROMs at the moment. That's just my opinion, however.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Every week someone requests aokp, ics, lewas, miui, etc...
Everyone on team acid has their own skill sets and projects. We try to work together to complete big projects.
The other side is like I've said before. We all have our daily lives to live as well.
Everything we've learned about the phone is in the device tree for cm7 and our initramfs. To explain our phone would be to walk through kernel and device tree commits and by reading the source.
I'm still working hard on porting the device specific changes that make our phone work to the aosp samsung gingerbread branch. After that is done, I'm going to attempt to merge and port to the ics branch in that tree.
Raver also has some diffs for ics aosp.
So as we progress, I see no harm in anyone else trying to make their own attempts, but if we have more people help for common causes, we can reach goals faster.
If you want to help, just fork the git repo of choice, commit your changes, push your changes, and do a pull request. If the change(s) look good, we'll merge it. If not, we won't harsh you. But we will help guide you to getting your changes merged.
Sent from my SAMSUNG-SGH-I717 using xda premium
bhundven said:
Every week someone requests aokp, ics, lewas, miui, etc...
Everyone on team acid has their own skill sets and projects. We try to work together to complete big projects.
The other side is like I've said before. We all have our daily lives to live as well.
Everything we've learned about the phone is in the device tree for cm7 and our initramfs. To explain our phone would be to walk through kernel and device tree commits and by reading the source.
I'm still working hard on porting the device specific changes that make our phone work to the aosp samsung gingerbread branch. After that is done, I'm going to attempt to merge and port to the ics branch in that tree.
Raver also has some diffs for ics aosp.
So as we progress, I see no harm in anyone else trying to make their own attempts, but if we have more people help for common causes, we can reach goals faster.
If you want to help, just fork the git repo of choice, commit your changes, push your changes, and do a pull request. If the change(s) look good, we'll merge it. If not, we won't harsh you. But we will help guide you to getting your changes merged.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yep you're right bhund and completely off topic u got the Note! Lol bad ass! Lol
I've been around for a while, and flashing ROMs all the time, but I was wondering what it really takes in order to really get going with ROM development. I would really like to put together my own PAC/Rootbox/ReVolt-style ROM, but I don't really know where to get started. I have done a very small amount of Android app development, but I do have experience with Java. Does anyone have any pointers for where to get started, best practices, etc...?
Also included in this question should be this: I have a little experience with Github, but haven't really ever used it do pull requests, forking, and such, and I've only ever really used it for hosting my own projects. Is there a good guide on how to understand that type of stuff, as well as where to do builds, nightlies, and hosting? From what I've gathered from various ROM devs so far is that if you host on Goo.im, that will let you take advantage of GooManager for OTA updates, right?
drinfernoo said:
I've been around for a while, and flashing ROMs all the time, but I was wondering what it really takes in order to really get going with ROM development. I would really like to put together my own PAC/Rootbox/ReVolt-style ROM, but I don't really know where to get started. I have done a very small amount of Android app development, but I do have experience with Java. Does anyone have any pointers for where to get started, best practices, etc...?
Also included in this question should be this: I have a little experience with Github, but haven't really ever used it do pull requests, forking, and such, and I've only ever really used it for hosting my own projects. Is there a good guide on how to understand that type of stuff, as well as where to do builds, nightlies, and hosting? From what I've gathered from various ROM devs so far is that if you host on Goo.im, that will let you take advantage of GooManager for OTA updates, right?
Click to expand...
Click to collapse
As far as the github, you can fork the CM link directly for The GNote 2 as it's supported by them. If it were not you would have to fork a dev that has ported it over. Once you setup your box, ( there are numerous "how to compile custom roms" ) you can compile your rom. Easiest would be to ask somebody that has a "clean" (no customizations) CM build that you can use, and make your own mods. After that. It all counts on how good you are with coding and making your own mods. Hope this gets you started. Youtube and google are good places to start. I always refer Android Dev section for my repos and how-to's.
It takes, above all else, patience. start here
http://forum.xda-developers.com/showthread.php?t=1946481
Chasmodo dev gives me a link where you can see tons of guide and tutorials… good for noobs but also for advanced devs… I would like to compile an aosp for n5100 that is unsupported by cyano team at the moment… so I think that is too hard
http://forum.xda-developers.com/showthread.php?p=41491498
Inviato dal mio GT-N5100 con Tapatalk 2
First off I'm a new entrant to android, and I would like to build AOSP rom for our device. I have read quite a few posts on the internet about it. In one post Its said that the steps to AOSP building are 1) setting up environment
2) Syncing device tree 3) downloading the android source 4) downloading the drivers (kernal source code?)
4) building it. Is it actually that simple?
Forgive me if I'm wrong.
Lets discuss the possibility of AOSP rom for our devices.
Can some one post all the resources which we have, that will help building the rom?
Also, this thread can be a starting point for many developers out there.
kr1shna said:
First off I'm a new entrant to android, and I would like to build AOSP rom for our device. I have read quite a few posts on the internet about it. In one post Its said that the steps to AOSP building are 1) setting up environment
2) Syncing device tree 3) downloading the android source 4) downloading the drivers (kernal source code?)
4) building it. Is it actually that simple?
Forgive me if I'm wrong.
Lets discuss the possibility of AOSP rom for our devices.
Can some one post all the resources which we have, that will help building the rom?
Also, this thread can be a starting point for many developers out there.
Click to expand...
Click to collapse
Hi kr1shna.
I saw your post on another thread involving the same topic.
The fact of the matter is, with the Mate 7 and Huawei devices in general, that Huawei does not release certain sources needed for creating a custom kernel, meaning that the only ROMs that can be created for these devices have to based off the existing EMUI sources, meaning there really isn't much use in doing it at all. @gabry3795 has managed to get the GPU drivers running (reported on his thread, which can be found here), however that's as far as anyone has come. After that the only way to get the device to actually boot (as far as my very limited knowledge on these things go) is to implement Huawei's sources and files, meaning you will just eventually end up with EMUI again.
TL;DR: Huawei is a jackass when it comes to releasing sources, meaning creating custom, non EMUI-ROMs and kernels is pretty much impossible.
If you do figure it out though, rest assured you will have the praise of all of us here that's absolutely sick of EMUI. So best of luck to you, however don't get your hopes up too high.
Scruffykid said:
Hi kr1shna.
I saw your post on another thread involving the same topic.
The fact of the matter is, with the Mate 7 and Huawei devices in general, that Huawei does not release certain sources needed for creating a custom kernel, meaning that the only ROMs that can be created for these devices have to based off the existing EMUI sources, meaning there really isn't much use in doing it at all. @gabry3795 has managed to get the GPU drivers running (reported on his thread, which can be found here), however that's as far as anyone has come. After that the only way to get the device to actually boot (as far as my very limited knowledge on these things go) is to implement Huawei's sources and files, meaning you will just eventually end up with EMUI again.
TL;DR: Huawei is a jackass when it comes to releasing sources, meaning creating custom, non EMUI-ROMs and kernels is pretty much impossible.
If you do figure it out though, rest assured you will have the praise of all of us here that's absolutely sick of EMUI. So best of luck to you, however don't get your hopes up too high.
Click to expand...
Click to collapse
Thank you for the information, so buying a huawei was a bad decision. I should have got the htc m9 or a9 instead.
kr1shna said:
Thank you for the information, so buying a huawei was a bad decision. I should have got the htc m9 or a9 instead.
Click to expand...
Click to collapse
very bad decision! i have been trying to get help from huawei to release their sources for over a year but have had no luck. at this point im pretty much done and will probably just end up buying the next nexus device regardless of screen size. its sad that their are no good 6 inch phones with custom rom support.
i was going to try and pursue legal action but seeing as how the mate 7 was not legally released in the US, their is no legal recourse. im hoping someone in the EU could do some research regarding legal action against huawei in the hope of pressuring them to release source codes.